summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
Diffstat (limited to 'docs')
-rw-r--r--docs/Samba-Developers-Guide.pdf13506
-rw-r--r--docs/Samba-HOWTO-Collection.pdf31140
-rw-r--r--docs/announce3
-rw-r--r--docs/docbook/.cvsignore2
-rw-r--r--docs/docbook/Makefile.in22
-rwxr-xr-xdocs/docbook/configure2257
-rw-r--r--docs/docbook/configure.in2
-rw-r--r--docs/docbook/devdoc/dev-doc.xml5
-rw-r--r--docs/docbook/global.ent2
-rw-r--r--docs/docbook/manpages/.cvsignore2
-rw-r--r--docs/docbook/manpages/profiles.1.sgml86
-rw-r--r--docs/docbook/manpages/rpcclient.1.xml2
-rw-r--r--docs/docbook/projdoc/AccessControls.xml219
-rw-r--r--docs/docbook/projdoc/AdvancedNetworkAdmin.xml27
-rw-r--r--docs/docbook/projdoc/Bugs.xml43
-rw-r--r--docs/docbook/projdoc/Compiling.xml168
-rw-r--r--docs/docbook/projdoc/DOMAIN_MEMBER.xml282
-rw-r--r--docs/docbook/projdoc/passdb.xml319
-rw-r--r--docs/docbook/projdoc/printer_driver2.xml2
-rw-r--r--docs/docbook/smbdotconf/printing/printcommand.xml2
-rw-r--r--docs/docbook/smbdotconf/printing/totalprintjobs.xml22
-rw-r--r--docs/docbook/smbdotconf/smb.conf.5.xml14
-rw-r--r--docs/docbook/xslt/db2latex/VERSION.xml6
-rw-r--r--docs/docbook/xslt/db2latex/abstract.mod.xsl6
-rw-r--r--docs/docbook/xslt/db2latex/admonition.mod.xsl6
-rw-r--r--docs/docbook/xslt/db2latex/authorgroup.mod.xsl6
-rw-r--r--docs/docbook/xslt/db2latex/biblio.mod.xsl6
-rw-r--r--docs/docbook/xslt/db2latex/block.mod.xsl6
-rw-r--r--docs/docbook/xslt/db2latex/book-article.mod.xsl10
-rw-r--r--docs/docbook/xslt/db2latex/bridgehead.mod.xsl6
-rw-r--r--docs/docbook/xslt/db2latex/callout.mod.xsl6
-rw-r--r--docs/docbook/xslt/db2latex/citation.mod.xsl6
-rw-r--r--docs/docbook/xslt/db2latex/common/common.xsl4
-rw-r--r--docs/docbook/xslt/db2latex/common/l10n.xsl2
-rw-r--r--docs/docbook/xslt/db2latex/component.mod.xsl6
-rw-r--r--docs/docbook/xslt/db2latex/dedication.mod.xsl6
-rw-r--r--docs/docbook/xslt/db2latex/dingbat.mod.xsl6
-rw-r--r--docs/docbook/xslt/db2latex/docbook.xsl4
-rw-r--r--docs/docbook/xslt/db2latex/email.mod.xsl6
-rw-r--r--docs/docbook/xslt/db2latex/errors.mod.xsl4
-rw-r--r--docs/docbook/xslt/db2latex/example.mod.xsl6
-rw-r--r--docs/docbook/xslt/db2latex/figure.mod.xsl6
-rw-r--r--docs/docbook/xslt/db2latex/font.mod.xsl6
-rw-r--r--docs/docbook/xslt/db2latex/footnote.mod.xsl6
-rw-r--r--docs/docbook/xslt/db2latex/formal.mod.xsl6
-rw-r--r--docs/docbook/xslt/db2latex/glossary.mod.xsl6
-rw-r--r--docs/docbook/xslt/db2latex/graphic.mod.xsl6
-rw-r--r--docs/docbook/xslt/db2latex/html.mod.xsl4
-rw-r--r--docs/docbook/xslt/db2latex/index.mod.xsl6
-rw-r--r--docs/docbook/xslt/db2latex/info.mod.xsl6
-rw-r--r--docs/docbook/xslt/db2latex/inline.mod.xsl6
-rw-r--r--docs/docbook/xslt/db2latex/keywords.mod.xsl6
-rw-r--r--docs/docbook/xslt/db2latex/labelid.mod.xsl6
-rw-r--r--docs/docbook/xslt/db2latex/latex.mapping.xsl6
-rw-r--r--docs/docbook/xslt/db2latex/lists.mod.xsl6
-rw-r--r--docs/docbook/xslt/db2latex/mathelem.mod.xsl6
-rw-r--r--docs/docbook/xslt/db2latex/mathml/mathml.content.constsymb.mod.xsl4
-rw-r--r--docs/docbook/xslt/db2latex/mathml/mathml.content.functions.mod.xsl4
-rw-r--r--docs/docbook/xslt/db2latex/mathml/mathml.content.mod.xsl4
-rw-r--r--docs/docbook/xslt/db2latex/mathml/mathml.content.token.mod.xsl4
-rw-r--r--docs/docbook/xslt/db2latex/mathml/mathml.mod.xsl4
-rw-r--r--docs/docbook/xslt/db2latex/mathml/mathml.presentation.mod.xsl4
-rw-r--r--docs/docbook/xslt/db2latex/mediaobject.mod.xsl6
-rw-r--r--docs/docbook/xslt/db2latex/msgset.mod.xsl4
-rw-r--r--docs/docbook/xslt/db2latex/normalize-scape.mod.xsl6
-rw-r--r--docs/docbook/xslt/db2latex/para.mod.xsl6
-rw-r--r--docs/docbook/xslt/db2latex/part-chap-app.mod.xsl14
-rw-r--r--docs/docbook/xslt/db2latex/pi.mod.xsl6
-rw-r--r--docs/docbook/xslt/db2latex/preamble.mod.xsl6
-rw-r--r--docs/docbook/xslt/db2latex/preface.mod.xsl6
-rw-r--r--docs/docbook/xslt/db2latex/procedure.mod.xsl6
-rw-r--r--docs/docbook/xslt/db2latex/qandaset.mod.xsl6
-rw-r--r--docs/docbook/xslt/db2latex/refentry.mod.xsl6
-rw-r--r--docs/docbook/xslt/db2latex/revision.mod.xsl6
-rw-r--r--docs/docbook/xslt/db2latex/sections.mod.xsl6
-rw-r--r--docs/docbook/xslt/db2latex/set.mod.xsl6
-rw-r--r--docs/docbook/xslt/db2latex/sgmltag.mod.xsl6
-rw-r--r--docs/docbook/xslt/db2latex/synop-oop.mod.xsl4
-rw-r--r--docs/docbook/xslt/db2latex/synop-struct.mod.xsl4
-rw-r--r--docs/docbook/xslt/db2latex/table.mod.xsl6
-rw-r--r--docs/docbook/xslt/db2latex/texmath.mod.xsl6
-rw-r--r--docs/docbook/xslt/db2latex/vars.mod.xsl12
-rw-r--r--docs/docbook/xslt/db2latex/verbatim.mod.xsl6
-rw-r--r--docs/docbook/xslt/db2latex/xref.mod.xsl6
-rw-r--r--docs/docbook/xslt/lists.mod.xsl4
-rw-r--r--docs/docbook/xslt/table.mod.xsl6
-rw-r--r--docs/faq/FAQ-Config.html16
-rw-r--r--docs/faq/FAQ-Printing.html16
-rw-r--r--docs/faq/clientapp.html250
-rw-r--r--docs/faq/errors.html314
-rw-r--r--docs/faq/general.html439
-rw-r--r--docs/faq/install.html502
-rw-r--r--docs/faq/samba-faq.html351
-rw-r--r--docs/htmldocs/Samba-Developers-Guide.html9941
-rw-r--r--docs/htmldocs/Samba-HOWTO-Collection.html9515
-rw-r--r--docs/htmldocs/ads.html386
-rw-r--r--docs/htmldocs/advancednetworkmanagement.html555
-rw-r--r--docs/htmldocs/appendixes.html278
-rw-r--r--docs/htmldocs/browsing-quick.html514
-rw-r--r--docs/htmldocs/bugreport.html397
-rw-r--r--docs/htmldocs/cups-printing.html2773
-rw-r--r--docs/htmldocs/cvs-access.html298
-rw-r--r--docs/htmldocs/diagnosis.html824
-rw-r--r--docs/htmldocs/domain-security.html317
-rw-r--r--docs/htmldocs/findsmb.1.html307
-rw-r--r--docs/htmldocs/groupmapping.html276
-rw-r--r--docs/htmldocs/groupprofiles.html568
-rw-r--r--docs/htmldocs/improved-browsing.html532
-rw-r--r--docs/htmldocs/install.html951
-rw-r--r--docs/htmldocs/integrate-ms-networks.html1160
-rw-r--r--docs/htmldocs/interdomaintrusts.html451
-rw-r--r--docs/htmldocs/introduction.html425
-rw-r--r--docs/htmldocs/introsmb.html659
-rw-r--r--docs/htmldocs/lmhosts.5.html215
-rw-r--r--docs/htmldocs/msdfs.html320
-rw-r--r--docs/htmldocs/net.8.html545
-rw-r--r--docs/htmldocs/nmbd.8.html821
-rw-r--r--docs/htmldocs/nmblookup.1.html467
-rw-r--r--docs/htmldocs/nt4migration.html356
-rw-r--r--docs/htmldocs/oplocks.html208
-rw-r--r--docs/htmldocs/optional.html905
-rw-r--r--docs/htmldocs/other-clients.html248
-rw-r--r--docs/htmldocs/p1346.html917
-rw-r--r--docs/htmldocs/p18.html438
-rw-r--r--docs/htmldocs/p3106.html391
-rw-r--r--docs/htmldocs/p544.html388
-rw-r--r--docs/htmldocs/pam.html643
-rw-r--r--docs/htmldocs/pdb-mysql.html288
-rw-r--r--docs/htmldocs/pdb-xml.html184
-rw-r--r--docs/htmldocs/pdbedit.8.html671
-rw-r--r--docs/htmldocs/policymgmt.html758
-rw-r--r--docs/htmldocs/portability.html126
-rw-r--r--docs/htmldocs/printing.html1485
-rw-r--r--docs/htmldocs/profilemgmt.html1753
-rw-r--r--docs/htmldocs/pwencrypt.html434
-rw-r--r--docs/htmldocs/rpcclient.1.html871
-rw-r--r--docs/htmldocs/samba-bdc.html374
-rw-r--r--docs/htmldocs/samba-howto-collection.html1188
-rw-r--r--docs/htmldocs/samba-ldap-howto.html986
-rw-r--r--docs/htmldocs/samba-pdc.html2890
-rw-r--r--docs/htmldocs/samba.7.html428
-rw-r--r--docs/htmldocs/securitylevels.html374
-rw-r--r--docs/htmldocs/servertype.html368
-rw-r--r--docs/htmldocs/smb.conf.5.html22593
-rw-r--r--docs/htmldocs/smbcacls.1.html460
-rw-r--r--docs/htmldocs/smbclient.1.html1747
-rw-r--r--docs/htmldocs/smbcontrol.1.html444
-rw-r--r--docs/htmldocs/smbd.8.html807
-rw-r--r--docs/htmldocs/smbmnt.8.html197
-rw-r--r--docs/htmldocs/smbmount.8.html480
-rw-r--r--docs/htmldocs/smbpasswd.5.html342
-rw-r--r--docs/htmldocs/smbpasswd.8.html663
-rw-r--r--docs/htmldocs/smbsh.1.html551
-rw-r--r--docs/htmldocs/smbspool.8.html232
-rw-r--r--docs/htmldocs/smbstatus.1.html257
-rw-r--r--docs/htmldocs/smbtar.1.html375
-rw-r--r--docs/htmldocs/smbumount.8.html145
-rw-r--r--docs/htmldocs/speed.html469
-rw-r--r--docs/htmldocs/swat.8.html486
-rw-r--r--docs/htmldocs/swat.html233
-rw-r--r--docs/htmldocs/testparm.1.html331
-rw-r--r--docs/htmldocs/testprns.1.html265
-rw-r--r--docs/htmldocs/type.html405
-rw-r--r--docs/htmldocs/unix-permissions.html979
-rw-r--r--docs/htmldocs/vfs.html145
-rw-r--r--docs/htmldocs/vfstest.1.html502
-rw-r--r--docs/htmldocs/wbinfo.1.html408
-rw-r--r--docs/htmldocs/winbind.html1886
-rw-r--r--docs/htmldocs/winbindd.8.html999
-rw-r--r--docs/manpages/findsmb.1145
-rw-r--r--docs/manpages/lmhosts.5130
-rw-r--r--docs/manpages/net.8624
-rw-r--r--docs/manpages/nmbd.8372
-rw-r--r--docs/manpages/nmblookup.1297
-rw-r--r--docs/manpages/pdbedit.8406
-rw-r--r--docs/manpages/rpcclient.1908
-rw-r--r--docs/manpages/samba.7139
-rw-r--r--docs/manpages/smb.conf.59669
-rw-r--r--docs/manpages/smbcacls.1328
-rw-r--r--docs/manpages/smbclient.11311
-rw-r--r--docs/manpages/smbcontrol.1317
-rw-r--r--docs/manpages/smbd.8438
-rw-r--r--docs/manpages/smbmnt.8113
-rw-r--r--docs/manpages/smbmount.8363
-rw-r--r--docs/manpages/smbpasswd.5222
-rw-r--r--docs/manpages/smbpasswd.8424
-rw-r--r--docs/manpages/smbsh.1249
-rw-r--r--docs/manpages/smbspool.8146
-rw-r--r--docs/manpages/smbstatus.1158
-rw-r--r--docs/manpages/smbtar.1199
-rw-r--r--docs/manpages/smbumount.869
-rw-r--r--docs/manpages/swat.8239
-rw-r--r--docs/manpages/testparm.1175
-rw-r--r--docs/manpages/testprns.1135
-rw-r--r--docs/manpages/vfstest.1266
-rw-r--r--docs/manpages/wbinfo.1266
-rw-r--r--docs/manpages/winbindd.8492
-rw-r--r--docs/textdocs/README.jis149
198 files changed, 80269 insertions, 76433 deletions
diff --git a/docs/Samba-Developers-Guide.pdf b/docs/Samba-Developers-Guide.pdf
index 9dcb2a1825..897074783c 100644
--- a/docs/Samba-Developers-Guide.pdf
+++ b/docs/Samba-Developers-Guide.pdf
@@ -1,10999 +1,2533 @@
-%PDF-1.4
-5 0 obj
-<< /S /GoTo /D (chapter.1) >>
-endobj
-8 0 obj
-(1 Definition of NetBIOS Protocol and Name Resolution Modes)
-endobj
-9 0 obj
-<< /S /GoTo /D (section.1.1) >>
-endobj
-12 0 obj
-(1.1 NETBIOS)
-endobj
-13 0 obj
-<< /S /GoTo /D (section.1.2) >>
-endobj
-16 0 obj
-(1.2 BROADCAST NetBIOS)
-endobj
-17 0 obj
-<< /S /GoTo /D (section.1.3) >>
-endobj
-20 0 obj
-(1.3 NBNS NetBIOS)
-endobj
-21 0 obj
-<< /S /GoTo /D (chapter.2) >>
-endobj
-24 0 obj
-(2 Samba Architecture)
-endobj
-25 0 obj
-<< /S /GoTo /D (section.2.1) >>
-endobj
-28 0 obj
-(2.1 Introduction)
-endobj
-29 0 obj
-<< /S /GoTo /D (section.2.2) >>
-endobj
-32 0 obj
-(2.2 Multithreading and Samba)
-endobj
-33 0 obj
-<< /S /GoTo /D (section.2.3) >>
-endobj
-36 0 obj
-(2.3 Threading smbd)
-endobj
-37 0 obj
-<< /S /GoTo /D (section.2.4) >>
-endobj
-40 0 obj
-(2.4 Threading nmbd)
-endobj
-41 0 obj
-<< /S /GoTo /D (section.2.5) >>
-endobj
-44 0 obj
-(2.5 nbmd Design)
-endobj
-45 0 obj
-<< /S /GoTo /D (chapter.3) >>
-endobj
-48 0 obj
-(3 The samba DEBUG system)
-endobj
-49 0 obj
-<< /S /GoTo /D (section.3.1) >>
-endobj
-52 0 obj
-(3.1 New Output Syntax)
-endobj
-53 0 obj
-<< /S /GoTo /D (section.3.2) >>
-endobj
-56 0 obj
-(3.2 The DEBUG\(\) Macro)
-endobj
-57 0 obj
-<< /S /GoTo /D (section.3.3) >>
-endobj
-60 0 obj
-(3.3 The DEBUGADD\(\) Macro)
-endobj
-61 0 obj
-<< /S /GoTo /D (section.3.4) >>
-endobj
-64 0 obj
-(3.4 The DEBUGLVL\(\) Macro)
-endobj
-65 0 obj
-<< /S /GoTo /D (section.3.5) >>
-endobj
-68 0 obj
-(3.5 New Functions)
-endobj
-69 0 obj
-<< /S /GoTo /D (subsection.3.5.1) >>
-endobj
-72 0 obj
-(3.5.1 dbgtext\(\))
-endobj
-73 0 obj
-<< /S /GoTo /D (subsection.3.5.2) >>
-endobj
-76 0 obj
-(3.5.2 dbghdr\(\))
-endobj
-77 0 obj
-<< /S /GoTo /D (subsection.3.5.3) >>
-endobj
-80 0 obj
-(3.5.3 format\137debug\137text\(\))
-endobj
-81 0 obj
-<< /S /GoTo /D (chapter.4) >>
-endobj
-84 0 obj
-(4 Coding Suggestions)
-endobj
-85 0 obj
-<< /S /GoTo /D (chapter.5) >>
-endobj
-88 0 obj
-(5 Samba Internals)
-endobj
-89 0 obj
-<< /S /GoTo /D (section.5.1) >>
-endobj
-92 0 obj
-(5.1 Character Handling)
-endobj
-93 0 obj
-<< /S /GoTo /D (section.5.2) >>
-endobj
-96 0 obj
-(5.2 The new functions)
-endobj
-97 0 obj
-<< /S /GoTo /D (section.5.3) >>
-endobj
-100 0 obj
-(5.3 Macros in byteorder.h)
-endobj
-101 0 obj
-<< /S /GoTo /D (subsection.5.3.1) >>
-endobj
-104 0 obj
-(5.3.1 CVAL\(buf,pos\))
-endobj
-105 0 obj
-<< /S /GoTo /D (subsection.5.3.2) >>
-endobj
-108 0 obj
-(5.3.2 PVAL\(buf,pos\))
-endobj
-109 0 obj
-<< /S /GoTo /D (subsection.5.3.3) >>
-endobj
-112 0 obj
-(5.3.3 SCVAL\(buf,pos,val\))
-endobj
-113 0 obj
-<< /S /GoTo /D (subsection.5.3.4) >>
-endobj
-116 0 obj
-(5.3.4 SVAL\(buf,pos\))
-endobj
-117 0 obj
-<< /S /GoTo /D (subsection.5.3.5) >>
-endobj
-120 0 obj
-(5.3.5 IVAL\(buf,pos\))
-endobj
-121 0 obj
-<< /S /GoTo /D (subsection.5.3.6) >>
-endobj
-124 0 obj
-(5.3.6 SVALS\(buf,pos\))
-endobj
-125 0 obj
-<< /S /GoTo /D (subsection.5.3.7) >>
-endobj
-128 0 obj
-(5.3.7 IVALS\(buf,pos\))
-endobj
-129 0 obj
-<< /S /GoTo /D (subsection.5.3.8) >>
-endobj
-132 0 obj
-(5.3.8 SSVAL\(buf,pos,val\))
-endobj
-133 0 obj
-<< /S /GoTo /D (subsection.5.3.9) >>
-endobj
-136 0 obj
-(5.3.9 SIVAL\(buf,pos,val\))
-endobj
-137 0 obj
-<< /S /GoTo /D (subsection.5.3.10) >>
-endobj
-140 0 obj
-(5.3.10 SSVALS\(buf,pos,val\))
-endobj
-141 0 obj
-<< /S /GoTo /D (subsection.5.3.11) >>
-endobj
-144 0 obj
-(5.3.11 SIVALS\(buf,pos,val\))
-endobj
-145 0 obj
-<< /S /GoTo /D (subsection.5.3.12) >>
-endobj
-148 0 obj
-(5.3.12 RSVAL\(buf,pos\))
-endobj
-149 0 obj
-<< /S /GoTo /D (subsection.5.3.13) >>
-endobj
-152 0 obj
-(5.3.13 RIVAL\(buf,pos\))
-endobj
-153 0 obj
-<< /S /GoTo /D (subsection.5.3.14) >>
-endobj
-156 0 obj
-(5.3.14 RSSVAL\(buf,pos,val\))
-endobj
-157 0 obj
-<< /S /GoTo /D (subsection.5.3.15) >>
-endobj
-160 0 obj
-(5.3.15 RSIVAL\(buf,pos,val\))
-endobj
-161 0 obj
-<< /S /GoTo /D (section.5.4) >>
-endobj
-164 0 obj
-(5.4 LAN Manager Samba API)
-endobj
-165 0 obj
-<< /S /GoTo /D (subsection.5.4.1) >>
-endobj
-168 0 obj
-(5.4.1 Parameters)
-endobj
-169 0 obj
-<< /S /GoTo /D (subsection.5.4.2) >>
-endobj
-172 0 obj
-(5.4.2 Return value)
-endobj
-173 0 obj
-<< /S /GoTo /D (section.5.5) >>
-endobj
-176 0 obj
-(5.5 Code character table)
-endobj
-177 0 obj
-<< /S /GoTo /D (chapter.6) >>
-endobj
-180 0 obj
-(6 The smb.conf file)
-endobj
-181 0 obj
-<< /S /GoTo /D (section.6.1) >>
-endobj
-184 0 obj
-(6.1 Lexical Analysis)
-endobj
-185 0 obj
-<< /S /GoTo /D (subsection.6.1.1) >>
-endobj
-188 0 obj
-(6.1.1 Handling of Whitespace)
-endobj
-189 0 obj
-<< /S /GoTo /D (subsection.6.1.2) >>
-endobj
-192 0 obj
-(6.1.2 Handling of Line Continuation)
-endobj
-193 0 obj
-<< /S /GoTo /D (subsection.6.1.3) >>
-endobj
-196 0 obj
-(6.1.3 Line Continuation Quirks)
-endobj
-197 0 obj
-<< /S /GoTo /D (section.6.2) >>
-endobj
-200 0 obj
-(6.2 Syntax)
-endobj
-201 0 obj
-<< /S /GoTo /D (subsection.6.2.1) >>
-endobj
-204 0 obj
-(6.2.1 About params.c)
-endobj
-205 0 obj
-<< /S /GoTo /D (chapter.7) >>
-endobj
-208 0 obj
-(7 NetBIOS in a Unix World)
-endobj
-209 0 obj
-<< /S /GoTo /D (section.7.1) >>
-endobj
-212 0 obj
-(7.1 Introduction)
-endobj
-213 0 obj
-<< /S /GoTo /D (section.7.2) >>
-endobj
-216 0 obj
-(7.2 Usernames)
-endobj
-217 0 obj
-<< /S /GoTo /D (section.7.3) >>
-endobj
-220 0 obj
-(7.3 File Ownership)
-endobj
-221 0 obj
-<< /S /GoTo /D (section.7.4) >>
-endobj
-224 0 obj
-(7.4 Passwords)
-endobj
-225 0 obj
-<< /S /GoTo /D (section.7.5) >>
-endobj
-228 0 obj
-(7.5 Locking)
-endobj
-229 0 obj
-<< /S /GoTo /D (section.7.6) >>
-endobj
-232 0 obj
-(7.6 Deny Modes)
-endobj
-233 0 obj
-<< /S /GoTo /D (section.7.7) >>
-endobj
-236 0 obj
-(7.7 Trapdoor UIDs)
-endobj
-237 0 obj
-<< /S /GoTo /D (section.7.8) >>
-endobj
-240 0 obj
-(7.8 Port numbers)
-endobj
-241 0 obj
-<< /S /GoTo /D (section.7.9) >>
-endobj
-244 0 obj
-(7.9 Protocol Complexity)
-endobj
-245 0 obj
-<< /S /GoTo /D (chapter.8) >>
-endobj
-248 0 obj
-(8 Tracing samba system calls)
-endobj
-249 0 obj
-<< /S /GoTo /D (chapter.9) >>
-endobj
-252 0 obj
-(9 NT Domain RPC's)
-endobj
-253 0 obj
-<< /S /GoTo /D (section.9.1) >>
-endobj
-256 0 obj
-(9.1 Introduction)
-endobj
-257 0 obj
-<< /S /GoTo /D (subsection.9.1.1) >>
-endobj
-260 0 obj
-(9.1.1 Sources)
-endobj
-261 0 obj
-<< /S /GoTo /D (subsection.9.1.2) >>
-endobj
-264 0 obj
-(9.1.2 Credits)
-endobj
-265 0 obj
-<< /S /GoTo /D (section.9.2) >>
-endobj
-268 0 obj
-(9.2 Notes and Structures)
-endobj
-269 0 obj
-<< /S /GoTo /D (subsection.9.2.1) >>
-endobj
-272 0 obj
-(9.2.1 Notes)
-endobj
-273 0 obj
-<< /S /GoTo /D (subsection.9.2.2) >>
-endobj
-276 0 obj
-(9.2.2 Enumerations)
-endobj
-277 0 obj
-<< /S /GoTo /D (subsubsection.9.2.2.1) >>
-endobj
-280 0 obj
-(9.2.2.1 MSRPC Header type)
-endobj
-281 0 obj
-<< /S /GoTo /D (subsubsection.9.2.2.2) >>
-endobj
-284 0 obj
-(9.2.2.2 MSRPC Packet info)
-endobj
-285 0 obj
-<< /S /GoTo /D (subsection.9.2.3) >>
-endobj
-288 0 obj
-(9.2.3 Structures)
-endobj
-289 0 obj
-<< /S /GoTo /D (subsubsection.9.2.3.1) >>
-endobj
-292 0 obj
-(9.2.3.1 VOID *)
-endobj
-293 0 obj
-<< /S /GoTo /D (subsubsection.9.2.3.2) >>
-endobj
-296 0 obj
-(9.2.3.2 char)
-endobj
-297 0 obj
-<< /S /GoTo /D (subsubsection.9.2.3.3) >>
-endobj
-300 0 obj
-(9.2.3.3 UTIME)
-endobj
-301 0 obj
-<< /S /GoTo /D (subsubsection.9.2.3.4) >>
-endobj
-304 0 obj
-(9.2.3.4 NTTIME)
-endobj
-305 0 obj
-<< /S /GoTo /D (subsubsection.9.2.3.5) >>
-endobj
-308 0 obj
-(9.2.3.5 DOM\137SID \(domain SID structure\))
-endobj
-309 0 obj
-<< /S /GoTo /D (subsubsection.9.2.3.6) >>
-endobj
-312 0 obj
-(9.2.3.6 STR \(string\))
-endobj
-313 0 obj
-<< /S /GoTo /D (subsubsection.9.2.3.7) >>
-endobj
-316 0 obj
-(9.2.3.7 UNIHDR \(unicode string header\))
-endobj
-317 0 obj
-<< /S /GoTo /D (subsubsection.9.2.3.8) >>
-endobj
-320 0 obj
-(9.2.3.8 UNIHDR2 \(unicode string header plus buffer pointer\))
-endobj
-321 0 obj
-<< /S /GoTo /D (subsubsection.9.2.3.9) >>
-endobj
-324 0 obj
-(9.2.3.9 UNISTR \(unicode string\))
-endobj
-325 0 obj
-<< /S /GoTo /D (subsubsection.9.2.3.10) >>
-endobj
-328 0 obj
-(9.2.3.10 NAME \(length-indicated unicode string\))
-endobj
-329 0 obj
-<< /S /GoTo /D (subsubsection.9.2.3.11) >>
-endobj
-332 0 obj
-(9.2.3.11 UNISTR2 \(aligned unicode string\))
-endobj
-333 0 obj
-<< /S /GoTo /D (subsubsection.9.2.3.12) >>
-endobj
-336 0 obj
-(9.2.3.12 OBJ\137ATTR \(object attributes\))
-endobj
-337 0 obj
-<< /S /GoTo /D (subsubsection.9.2.3.13) >>
-endobj
-340 0 obj
-(9.2.3.13 POL\137HND \(LSA policy handle\))
-endobj
-341 0 obj
-<< /S /GoTo /D (subsubsection.9.2.3.14) >>
-endobj
-344 0 obj
-(9.2.3.14 DOM\137SID2 \(domain SID structure, SIDS stored in unicode\))
-endobj
-345 0 obj
-<< /S /GoTo /D (subsubsection.9.2.3.15) >>
-endobj
-348 0 obj
-(9.2.3.15 DOM\137RID \(domain RID structure\))
-endobj
-349 0 obj
-<< /S /GoTo /D (subsubsection.9.2.3.16) >>
-endobj
-352 0 obj
-(9.2.3.16 LOG\137INFO \(server, account, client structure\))
-endobj
-353 0 obj
-<< /S /GoTo /D (subsubsection.9.2.3.17) >>
-endobj
-356 0 obj
-(9.2.3.17 CLNT\137SRV \(server, client names structure\))
-endobj
-357 0 obj
-<< /S /GoTo /D (subsubsection.9.2.3.18) >>
-endobj
-360 0 obj
-(9.2.3.18 CREDS \(credentials + time stamp\))
-endobj
-361 0 obj
-<< /S /GoTo /D (subsubsection.9.2.3.19) >>
-endobj
-364 0 obj
-(9.2.3.19 CLNT\137INFO2 \(server, client structure, client credentials\))
-endobj
-365 0 obj
-<< /S /GoTo /D (subsubsection.9.2.3.20) >>
-endobj
-368 0 obj
-(9.2.3.20 CLNT\137INFO \(server, account, client structure, client credentials\))
-endobj
-369 0 obj
-<< /S /GoTo /D (subsubsection.9.2.3.21) >>
-endobj
-372 0 obj
-(9.2.3.21 ID\137INFO\1371 \(id info structure, auth level 1\))
-endobj
-373 0 obj
-<< /S /GoTo /D (subsubsection.9.2.3.22) >>
-endobj
-376 0 obj
-(9.2.3.22 SAM\137INFO \(sam logon/logoff id info structure\))
-endobj
-377 0 obj
-<< /S /GoTo /D (subsubsection.9.2.3.23) >>
-endobj
-380 0 obj
-(9.2.3.23 GID \(group id info\))
-endobj
-381 0 obj
-<< /S /GoTo /D (subsubsection.9.2.3.24) >>
-endobj
-384 0 obj
-(9.2.3.24 DOM\137REF \(domain reference info\))
-endobj
-385 0 obj
-<< /S /GoTo /D (subsubsection.9.2.3.25) >>
-endobj
-388 0 obj
-(9.2.3.25 DOM\137INFO \(domain info, levels 3 and 5 are the same\)\))
-endobj
-389 0 obj
-<< /S /GoTo /D (subsubsection.9.2.3.26) >>
-endobj
-392 0 obj
-(9.2.3.26 USER\137INFO \(user logon info\))
-endobj
-393 0 obj
-<< /S /GoTo /D (subsubsection.9.2.3.27) >>
-endobj
-396 0 obj
-(9.2.3.27 SH\137INFO\1371\137PTR \(pointers to level 1 share info strings\))
-endobj
-397 0 obj
-<< /S /GoTo /D (subsubsection.9.2.3.28) >>
-endobj
-400 0 obj
-(9.2.3.28 SH\137INFO\1371\137STR \(level 1 share info strings\))
-endobj
-401 0 obj
-<< /S /GoTo /D (subsubsection.9.2.3.29) >>
-endobj
-404 0 obj
-(9.2.3.29 SHARE\137INFO\1371\137CTR)
-endobj
-405 0 obj
-<< /S /GoTo /D (subsubsection.9.2.3.30) >>
-endobj
-408 0 obj
-(9.2.3.30 SERVER\137INFO\137101)
-endobj
-409 0 obj
-<< /S /GoTo /D (section.9.3) >>
-endobj
-412 0 obj
-(9.3 MSRPC over Transact Named Pipe)
-endobj
-413 0 obj
-<< /S /GoTo /D (subsection.9.3.1) >>
-endobj
-416 0 obj
-(9.3.1 MSRPC Pipes)
-endobj
-417 0 obj
-<< /S /GoTo /D (subsection.9.3.2) >>
-endobj
-420 0 obj
-(9.3.2 Header)
-endobj
-421 0 obj
-<< /S /GoTo /D (subsubsection.9.3.2.1) >>
-endobj
-424 0 obj
-(9.3.2.1 RPC\137Packet for request, response, bind and bind acknowledgement)
-endobj
-425 0 obj
-<< /S /GoTo /D (subsubsection.9.3.2.2) >>
-endobj
-428 0 obj
-(9.3.2.2 Interface identification)
-endobj
-429 0 obj
-<< /S /GoTo /D (subsubsection.9.3.2.3) >>
-endobj
-432 0 obj
-(9.3.2.3 RPC\137Iface RW)
-endobj
-433 0 obj
-<< /S /GoTo /D (subsubsection.9.3.2.4) >>
-endobj
-436 0 obj
-(9.3.2.4 RPC\137ReqBind RW)
-endobj
-437 0 obj
-<< /S /GoTo /D (subsubsection.9.3.2.5) >>
-endobj
-440 0 obj
-(9.3.2.5 RPC\137Address RW)
-endobj
-441 0 obj
-<< /S /GoTo /D (subsubsection.9.3.2.6) >>
-endobj
-444 0 obj
-(9.3.2.6 RPC\137ResBind RW)
-endobj
-445 0 obj
-<< /S /GoTo /D (subsubsection.9.3.2.7) >>
-endobj
-448 0 obj
-(9.3.2.7 RPC\137ReqNorm RW)
-endobj
-449 0 obj
-<< /S /GoTo /D (subsubsection.9.3.2.8) >>
-endobj
-452 0 obj
-(9.3.2.8 RPC\137ResNorm RW)
-endobj
-453 0 obj
-<< /S /GoTo /D (subsection.9.3.3) >>
-endobj
-456 0 obj
-(9.3.3 Tail)
-endobj
-457 0 obj
-<< /S /GoTo /D (subsection.9.3.4) >>
-endobj
-460 0 obj
-(9.3.4 RPC Bind / Bind Ack)
-endobj
-461 0 obj
-<< /S /GoTo /D (subsection.9.3.5) >>
-endobj
-464 0 obj
-(9.3.5 NTLSA Transact Named Pipe)
-endobj
-465 0 obj
-<< /S /GoTo /D (subsection.9.3.6) >>
-endobj
-468 0 obj
-(9.3.6 LSA Open Policy)
-endobj
-469 0 obj
-<< /S /GoTo /D (subsubsection.9.3.6.1) >>
-endobj
-472 0 obj
-(9.3.6.1 Request)
-endobj
-473 0 obj
-<< /S /GoTo /D (subsubsection.9.3.6.2) >>
-endobj
-476 0 obj
-(9.3.6.2 Response)
-endobj
-477 0 obj
-<< /S /GoTo /D (subsection.9.3.7) >>
-endobj
-480 0 obj
-(9.3.7 LSA Query Info Policy)
-endobj
-481 0 obj
-<< /S /GoTo /D (subsubsection.9.3.7.1) >>
-endobj
-484 0 obj
-(9.3.7.1 Request)
-endobj
-485 0 obj
-<< /S /GoTo /D (subsubsection.9.3.7.2) >>
-endobj
-488 0 obj
-(9.3.7.2 Response)
-endobj
-489 0 obj
-<< /S /GoTo /D (subsection.9.3.8) >>
-endobj
-492 0 obj
-(9.3.8 LSA Enumerate Trusted Domains)
-endobj
-493 0 obj
-<< /S /GoTo /D (subsubsection.9.3.8.1) >>
-endobj
-496 0 obj
-(9.3.8.1 Request)
-endobj
-497 0 obj
-<< /S /GoTo /D (subsubsection.9.3.8.2) >>
-endobj
-500 0 obj
-(9.3.8.2 Response)
-endobj
-501 0 obj
-<< /S /GoTo /D (subsection.9.3.9) >>
-endobj
-504 0 obj
-(9.3.9 LSA Open Secret)
-endobj
-505 0 obj
-<< /S /GoTo /D (subsubsection.9.3.9.1) >>
-endobj
-508 0 obj
-(9.3.9.1 Request)
-endobj
-509 0 obj
-<< /S /GoTo /D (subsubsection.9.3.9.2) >>
-endobj
-512 0 obj
-(9.3.9.2 Response)
-endobj
-513 0 obj
-<< /S /GoTo /D (subsection.9.3.10) >>
-endobj
-516 0 obj
-(9.3.10 LSA Close)
-endobj
-517 0 obj
-<< /S /GoTo /D (subsubsection.9.3.10.1) >>
-endobj
-520 0 obj
-(9.3.10.1 Request)
-endobj
-521 0 obj
-<< /S /GoTo /D (subsubsection.9.3.10.2) >>
-endobj
-524 0 obj
-(9.3.10.2 Response)
-endobj
-525 0 obj
-<< /S /GoTo /D (subsection.9.3.11) >>
-endobj
-528 0 obj
-(9.3.11 LSA Lookup SIDS)
-endobj
-529 0 obj
-<< /S /GoTo /D (subsubsection.9.3.11.1) >>
-endobj
-532 0 obj
-(9.3.11.1 Request)
-endobj
-533 0 obj
-<< /S /GoTo /D (subsubsection.9.3.11.2) >>
-endobj
-536 0 obj
-(9.3.11.2 Response)
-endobj
-537 0 obj
-<< /S /GoTo /D (subsection.9.3.12) >>
-endobj
-540 0 obj
-(9.3.12 LSA Lookup Names)
-endobj
-541 0 obj
-<< /S /GoTo /D (subsubsection.9.3.12.1) >>
-endobj
-544 0 obj
-(9.3.12.1 Request)
-endobj
-545 0 obj
-<< /S /GoTo /D (subsubsection.9.3.12.2) >>
-endobj
-548 0 obj
-(9.3.12.2 Response)
-endobj
-549 0 obj
-<< /S /GoTo /D (section.9.4) >>
-endobj
-552 0 obj
-(9.4 NETLOGON rpc Transact Named Pipe)
-endobj
-553 0 obj
-<< /S /GoTo /D (subsection.9.4.1) >>
-endobj
-556 0 obj
-(9.4.1 LSA Request Challenge)
-endobj
-557 0 obj
-<< /S /GoTo /D (subsubsection.9.4.1.1) >>
-endobj
-560 0 obj
-(9.4.1.1 Request)
-endobj
-561 0 obj
-<< /S /GoTo /D (subsubsection.9.4.1.2) >>
-endobj
-564 0 obj
-(9.4.1.2 Response)
-endobj
-565 0 obj
-<< /S /GoTo /D (subsection.9.4.2) >>
-endobj
-568 0 obj
-(9.4.2 LSA Authenticate 2)
-endobj
-569 0 obj
-<< /S /GoTo /D (subsubsection.9.4.2.1) >>
-endobj
-572 0 obj
-(9.4.2.1 Request)
-endobj
-573 0 obj
-<< /S /GoTo /D (subsubsection.9.4.2.2) >>
-endobj
-576 0 obj
-(9.4.2.2 Response)
-endobj
-577 0 obj
-<< /S /GoTo /D (subsection.9.4.3) >>
-endobj
-580 0 obj
-(9.4.3 LSA Server Password Set)
-endobj
-581 0 obj
-<< /S /GoTo /D (subsubsection.9.4.3.1) >>
-endobj
-584 0 obj
-(9.4.3.1 Request)
-endobj
-585 0 obj
-<< /S /GoTo /D (subsubsection.9.4.3.2) >>
-endobj
-588 0 obj
-(9.4.3.2 Response)
-endobj
-589 0 obj
-<< /S /GoTo /D (subsection.9.4.4) >>
-endobj
-592 0 obj
-(9.4.4 LSA SAM Logon)
-endobj
-593 0 obj
-<< /S /GoTo /D (subsubsection.9.4.4.1) >>
-endobj
-596 0 obj
-(9.4.4.1 Request)
-endobj
-597 0 obj
-<< /S /GoTo /D (subsubsection.9.4.4.2) >>
-endobj
-600 0 obj
-(9.4.4.2 Response)
-endobj
-601 0 obj
-<< /S /GoTo /D (subsection.9.4.5) >>
-endobj
-604 0 obj
-(9.4.5 LSA SAM Logoff)
-endobj
-605 0 obj
-<< /S /GoTo /D (subsubsection.9.4.5.1) >>
-endobj
-608 0 obj
-(9.4.5.1 Request)
-endobj
-609 0 obj
-<< /S /GoTo /D (subsubsection.9.4.5.2) >>
-endobj
-612 0 obj
-(9.4.5.2 Response)
-endobj
-613 0 obj
-<< /S /GoTo /D (section.9.5) >>
-endobj
-616 0 obj
-(9.5 \134\134MAILSLOT\134NET\134NTLOGON)
-endobj
-617 0 obj
-<< /S /GoTo /D (subsection.9.5.1) >>
-endobj
-620 0 obj
-(9.5.1 Query for PDC)
-endobj
-621 0 obj
-<< /S /GoTo /D (subsubsection.9.5.1.1) >>
-endobj
-624 0 obj
-(9.5.1.1 Request)
-endobj
-625 0 obj
-<< /S /GoTo /D (subsubsection.9.5.1.2) >>
-endobj
-628 0 obj
-(9.5.1.2 Response)
-endobj
-629 0 obj
-<< /S /GoTo /D (subsection.9.5.2) >>
-endobj
-632 0 obj
-(9.5.2 SAM Logon)
-endobj
-633 0 obj
-<< /S /GoTo /D (subsubsection.9.5.2.1) >>
-endobj
-636 0 obj
-(9.5.2.1 Request)
-endobj
-637 0 obj
-<< /S /GoTo /D (subsubsection.9.5.2.2) >>
-endobj
-640 0 obj
-(9.5.2.2 Response)
-endobj
-641 0 obj
-<< /S /GoTo /D (section.9.6) >>
-endobj
-644 0 obj
-(9.6 SRVSVC Transact Named Pipe)
-endobj
-645 0 obj
-<< /S /GoTo /D (subsection.9.6.1) >>
-endobj
-648 0 obj
-(9.6.1 Net Share Enum)
-endobj
-649 0 obj
-<< /S /GoTo /D (subsubsection.9.6.1.1) >>
-endobj
-652 0 obj
-(9.6.1.1 Request)
-endobj
-653 0 obj
-<< /S /GoTo /D (subsubsection.9.6.1.2) >>
-endobj
-656 0 obj
-(9.6.1.2 Response)
-endobj
-657 0 obj
-<< /S /GoTo /D (subsection.9.6.2) >>
-endobj
-660 0 obj
-(9.6.2 Net Server Get Info)
-endobj
-661 0 obj
-<< /S /GoTo /D (subsubsection.9.6.2.1) >>
-endobj
-664 0 obj
-(9.6.2.1 Request)
-endobj
-665 0 obj
-<< /S /GoTo /D (subsubsection.9.6.2.2) >>
-endobj
-668 0 obj
-(9.6.2.2 Response)
-endobj
-669 0 obj
-<< /S /GoTo /D (section.9.7) >>
-endobj
-672 0 obj
-(9.7 Cryptographic side of NT Domain Authentication)
-endobj
-673 0 obj
-<< /S /GoTo /D (subsection.9.7.1) >>
-endobj
-676 0 obj
-(9.7.1 Definitions)
-endobj
-677 0 obj
-<< /S /GoTo /D (subsection.9.7.2) >>
-endobj
-680 0 obj
-(9.7.2 Protocol)
-endobj
-681 0 obj
-<< /S /GoTo /D (subsection.9.7.3) >>
-endobj
-684 0 obj
-(9.7.3 Comments)
-endobj
-685 0 obj
-<< /S /GoTo /D (section.9.8) >>
-endobj
-688 0 obj
-(9.8 SIDs and RIDs)
-endobj
-689 0 obj
-<< /S /GoTo /D (subsection.9.8.1) >>
-endobj
-692 0 obj
-(9.8.1 Well-known SIDs)
-endobj
-693 0 obj
-<< /S /GoTo /D (subsubsection.9.8.1.1) >>
-endobj
-696 0 obj
-(9.8.1.1 Universal well-known SIDs)
-endobj
-697 0 obj
-<< /S /GoTo /D (subsubsection.9.8.1.2) >>
-endobj
-700 0 obj
-(9.8.1.2 NT well-known SIDs)
-endobj
-701 0 obj
-<< /S /GoTo /D (subsection.9.8.2) >>
-endobj
-704 0 obj
-(9.8.2 Well-known RIDS)
-endobj
-705 0 obj
-<< /S /GoTo /D (subsubsection.9.8.2.1) >>
-endobj
-708 0 obj
-(9.8.2.1 Well-known RID users)
-endobj
-709 0 obj
-<< /S /GoTo /D (subsubsection.9.8.2.2) >>
-endobj
-712 0 obj
-(9.8.2.2 Well-known RID groups)
-endobj
-713 0 obj
-<< /S /GoTo /D (subsubsection.9.8.2.3) >>
-endobj
-716 0 obj
-(9.8.2.3 Well-known RID aliases)
-endobj
-717 0 obj
-<< /S /GoTo /D (chapter.10) >>
-endobj
-720 0 obj
-(10 Samba Printing Internals)
-endobj
-721 0 obj
-<< /S /GoTo /D (section.10.1) >>
-endobj
-724 0 obj
-(10.1 Abstract)
-endobj
-725 0 obj
-<< /S /GoTo /D (section.10.2) >>
-endobj
-728 0 obj
-(10.2 Printing Interface to Various Back ends)
-endobj
-729 0 obj
-<< /S /GoTo /D (section.10.3) >>
-endobj
-732 0 obj
-(10.3 Print Queue TDB's)
-endobj
-733 0 obj
-<< /S /GoTo /D (section.10.4) >>
-endobj
-736 0 obj
-(10.4 ChangeID and Client Caching of Printer Information)
-endobj
-737 0 obj
-<< /S /GoTo /D (section.10.5) >>
-endobj
-740 0 obj
-(10.5 Windows NT/2K Printer Change Notify)
-endobj
-741 0 obj
-<< /S /GoTo /D (chapter.11) >>
-endobj
-744 0 obj
-(11 Samba WINS Internals)
-endobj
-745 0 obj
-<< /S /GoTo /D (section.11.1) >>
-endobj
-748 0 obj
-(11.1 WINS Failover)
-endobj
-749 0 obj
-<< /S /GoTo /D (chapter.12) >>
-endobj
-752 0 obj
-(12 The Upcoming SAM System)
-endobj
-753 0 obj
-<< /S /GoTo /D (section.12.1) >>
-endobj
-756 0 obj
-(12.1 Security in the 'new SAM')
-endobj
-757 0 obj
-<< /S /GoTo /D (section.12.2) >>
-endobj
-760 0 obj
-(12.2 Standalone from UNIX)
-endobj
-761 0 obj
-<< /S /GoTo /D (section.12.3) >>
-endobj
-764 0 obj
-(12.3 Handles and Races in the new SAM)
-endobj
-765 0 obj
-<< /S /GoTo /D (section.12.4) >>
-endobj
-768 0 obj
-(12.4 Layers)
-endobj
-769 0 obj
-<< /S /GoTo /D (subsection.12.4.1) >>
-endobj
-772 0 obj
-(12.4.1 Application)
-endobj
-773 0 obj
-<< /S /GoTo /D (subsection.12.4.2) >>
-endobj
-776 0 obj
-(12.4.2 SAM Interface)
-endobj
-777 0 obj
-<< /S /GoTo /D (subsection.12.4.3) >>
-endobj
-780 0 obj
-(12.4.3 SAM Modules)
-endobj
-781 0 obj
-<< /S /GoTo /D (section.12.5) >>
-endobj
-784 0 obj
-(12.5 SAM Modules)
-endobj
-785 0 obj
-<< /S /GoTo /D (subsection.12.5.1) >>
-endobj
-788 0 obj
-(12.5.1 Special Module: sam\137passdb)
-endobj
-789 0 obj
-<< /S /GoTo /D (subsection.12.5.2) >>
-endobj
-792 0 obj
-(12.5.2 sam\137ads)
-endobj
-793 0 obj
-<< /S /GoTo /D (section.12.6) >>
-endobj
-796 0 obj
-(12.6 Memory Management)
-endobj
-797 0 obj
-<< /S /GoTo /D (section.12.7) >>
-endobj
-800 0 obj
-(12.7 Testing)
-endobj
-801 0 obj
-<< /S /GoTo /D (chapter.13) >>
-endobj
-804 0 obj
-(13 LanMan and NT Password Encryption)
-endobj
-805 0 obj
-<< /S /GoTo /D (section.13.1) >>
-endobj
-808 0 obj
-(13.1 Introduction)
-endobj
-809 0 obj
-<< /S /GoTo /D (section.13.2) >>
-endobj
-812 0 obj
-(13.2 How does it work?)
-endobj
-813 0 obj
-<< /S /GoTo /D (section.13.3) >>
-endobj
-816 0 obj
-(13.3 The smbpasswd file)
-endobj
-817 0 obj
-<< /S /GoTo /D (chapter.14) >>
-endobj
-820 0 obj
-(14 Modules)
-endobj
-821 0 obj
-<< /S /GoTo /D (section.14.1) >>
-endobj
-824 0 obj
-(14.1 Advantages)
-endobj
-825 0 obj
-<< /S /GoTo /D (section.14.2) >>
-endobj
-828 0 obj
-(14.2 Loading modules)
-endobj
-829 0 obj
-<< /S /GoTo /D (subsection.14.2.1) >>
-endobj
-832 0 obj
-(14.2.1 Static modules)
-endobj
-833 0 obj
-<< /S /GoTo /D (subsection.14.2.2) >>
-endobj
-836 0 obj
-(14.2.2 Shared modules)
-endobj
-837 0 obj
-<< /S /GoTo /D (section.14.3) >>
-endobj
-840 0 obj
-(14.3 Writing modules)
-endobj
-841 0 obj
-<< /S /GoTo /D (subsection.14.3.1) >>
-endobj
-844 0 obj
-(14.3.1 Static/Shared selection in configure.in)
-endobj
-845 0 obj
-<< /S /GoTo /D (chapter.15) >>
-endobj
-848 0 obj
-(15 RPC Pluggable Modules)
-endobj
-849 0 obj
-<< /S /GoTo /D (section.15.1) >>
-endobj
-852 0 obj
-(15.1 About)
-endobj
-853 0 obj
-<< /S /GoTo /D (section.15.2) >>
-endobj
-856 0 obj
-(15.2 General Overview)
-endobj
-857 0 obj
-<< /S /GoTo /D (chapter.16) >>
-endobj
-860 0 obj
-(16 Notes to packagers)
-endobj
-861 0 obj
-<< /S /GoTo /D (section.16.1) >>
-endobj
-864 0 obj
-(16.1 Versioning)
-endobj
-865 0 obj
-<< /S /GoTo /D (section.16.2) >>
-endobj
-868 0 obj
-(16.2 Modules)
-endobj
-869 0 obj
-<< /S /GoTo /D [870 0 R /Fit ] >>
-endobj
-872 0 obj <<
-/Length 241
-/Filter /FlateDecode
->>
-stream
-xJ19&g$9'snEhX|{']KA!æ !ƒºÈd Ť,ÀÌÓ®C"r
-tg7c2endstream
-endobj
-870 0 obj <<
-/Type /Page
-/Contents 872 0 R
-/Resources 871 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 881 0 R
->> endobj
-873 0 obj <<
-/D [870 0 R /XYZ 85.039 786.531 null]
->> endobj
-874 0 obj <<
-/D [870 0 R /XYZ 85.039 766.606 null]
->> endobj
-871 0 obj <<
-/Font << /F20 877 0 R /F21 880 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-884 0 obj <<
-/Length 1042
-/Filter /FlateDecode
->>
-stream
-xVK6-4{Kf`S,m$HtP (V$g8Gg?9 :YN`y#68<OY-,Isï»,?³×«ÁõE[S>Wd|<\E(Yr%cd$+e45g1< GPX> }$^{iKL .#?S\`&JY 3k&g5Q:n[>< .Bh;o0,p?Ôdß´= ºÑ
- µÓ}‘p=gÄg`¶˜?– «¿í퀡ݘ£$Ϫ¡/æn«fK3h÷½(dÓzŽÞû¶ÉÜ®ñ
-úÜbL1?Cs>JTy.*
-^;+j}~O+^
-s67O>5^~endstream
-endobj
-883 0 obj <<
-/Type /Page
-/Contents 884 0 R
-/Resources 882 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 881 0 R
-/Annots [ 897 0 R 901 0 R 902 0 R 904 0 R ]
->> endobj
-897 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [428.769 653.951 539.579 665.943]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://devel.samba.org/)>>
->> endobj
-901 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [84.043 640.401 108.944 652.394]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://devel.samba.org/)>>
->> endobj
-902 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [227.588 640.401 309.793 652.394]
-/Subtype/Link/A<</Type/Action/S/URI/URI(mailto:jelmer@samba.org)>>
->> endobj
-904 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [97.376 584.489 299.821 596.481]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.fsf.org/licenses/gpl.txt)>>
->> endobj
-885 0 obj <<
-/D [883 0 R /XYZ 85.039 786.531 null]
->> endobj
-889 0 obj <<
-/D [883 0 R /XYZ 85.039 740.382 null]
->> endobj
-896 0 obj <<
-/D [883 0 R /XYZ 85.039 709.447 null]
->> endobj
-903 0 obj <<
-/D [883 0 R /XYZ 85.039 626.133 null]
->> endobj
-882 0 obj <<
-/Font << /F35 888 0 R /F36 892 0 R /F15 895 0 R /F37 900 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-907 0 obj <<
-/Length 1430
-/Filter /FlateDecode
->>
-stream
-xIs8
-}9BHg6Kw0K1c;%6
-:tHD4qw:0a}mwsþ^ÇúxšL V=35
-s}6YH_w3C_1'cW[X~%.6PBZ6`ro/.B{u
-D>wu2¬Kg~5UvMP-6<; 6Z2_L<#@]yW"JO|w:dR]'xz Li8 {<7 <,@~)NfPfCI2a36Mx ~3xF$dWj M to2zm!
-74!&jQ! O-8\hQJamF~5lz]xAHgOw 9AU%K# |3T@B$,sqd
-&G
-endobj
-906 0 obj <<
-/Type /Page
-/Contents 907 0 R
-/Resources 905 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 881 0 R
-/Annots [ 910 0 R 911 0 R 912 0 R 913 0 R 914 0 R 915 0 R 916 0 R 917 0 R 918 0 R 919 0 R 920 0 R 921 0 R 922 0 R 923 0 R 924 0 R 925 0 R 926 0 R 927 0 R 928 0 R 929 0 R 930 0 R 931 0 R 932 0 R 933 0 R 934 0 R 935 0 R 936 0 R 937 0 R 938 0 R 939 0 R 940 0 R 941 0 R 942 0 R 943 0 R 944 0 R 945 0 R 946 0 R 947 0 R 948 0 R 949 0 R ]
->> endobj
-910 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [531.586 631.159 539.579 640.727]
-/Subtype /Link
-/A << /S /GoTo /D (chapter.1) >>
->> endobj
-911 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [532.132 617.61 539.579 626.632]
-/Subtype /Link
-/A << /S /GoTo /D (section.1.1) >>
->> endobj
-912 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [532.132 604.06 539.579 613.083]
-/Subtype /Link
-/A << /S /GoTo /D (section.1.2) >>
->> endobj
-913 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [532.132 590.511 539.579 599.534]
-/Subtype /Link
-/A << /S /GoTo /D (section.1.3) >>
->> endobj
-914 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [525.586 566.053 539.579 575.621]
-/Subtype /Link
-/A << /S /GoTo /D (chapter.2) >>
->> endobj
-915 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 552.504 539.579 561.527]
-/Subtype /Link
-/A << /S /GoTo /D (section.2.1) >>
->> endobj
-916 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 538.955 539.579 547.977]
-/Subtype /Link
-/A << /S /GoTo /D (section.2.2) >>
->> endobj
-917 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 525.405 539.579 534.428]
-/Subtype /Link
-/A << /S /GoTo /D (section.2.3) >>
->> endobj
-918 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 511.856 539.579 520.879]
-/Subtype /Link
-/A << /S /GoTo /D (section.2.4) >>
->> endobj
-919 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 498.307 539.579 507.33]
-/Subtype /Link
-/A << /S /GoTo /D (section.2.5) >>
->> endobj
-920 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [525.586 473.849 539.579 483.417]
-/Subtype /Link
-/A << /S /GoTo /D (chapter.3) >>
->> endobj
-921 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 460.299 539.579 469.322]
-/Subtype /Link
-/A << /S /GoTo /D (section.3.1) >>
->> endobj
-922 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 446.75 539.579 455.773]
-/Subtype /Link
-/A << /S /GoTo /D (section.3.2) >>
->> endobj
-923 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 433.201 539.579 442.224]
-/Subtype /Link
-/A << /S /GoTo /D (section.3.3) >>
->> endobj
-924 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 419.652 539.579 428.675]
-/Subtype /Link
-/A << /S /GoTo /D (section.3.4) >>
->> endobj
-925 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 406.103 539.579 415.125]
-/Subtype /Link
-/A << /S /GoTo /D (section.3.5) >>
->> endobj
-926 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 392.553 539.579 401.576]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.3.5.1) >>
->> endobj
-927 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 379.004 539.579 388.027]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.3.5.2) >>
->> endobj
-928 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 365.455 539.579 374.478]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.3.5.3) >>
->> endobj
-929 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [525.586 340.997 539.579 350.565]
-/Subtype /Link
-/A << /S /GoTo /D (chapter.4) >>
->> endobj
-930 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [525.586 316.538 539.579 326.107]
-/Subtype /Link
-/A << /S /GoTo /D (chapter.5) >>
->> endobj
-931 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 302.989 539.579 312.012]
-/Subtype /Link
-/A << /S /GoTo /D (section.5.1) >>
->> endobj
-932 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 289.44 539.579 298.463]
-/Subtype /Link
-/A << /S /GoTo /D (section.5.2) >>
->> endobj
-933 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 275.891 539.579 284.914]
-/Subtype /Link
-/A << /S /GoTo /D (section.5.3) >>
->> endobj
-934 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 262.342 539.579 271.364]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.5.3.1) >>
->> endobj
-935 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 248.792 539.579 257.815]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.5.3.2) >>
->> endobj
-936 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 235.243 539.579 244.266]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.5.3.3) >>
->> endobj
-937 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 221.694 539.579 230.717]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.5.3.4) >>
->> endobj
-938 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 208.145 539.579 217.168]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.5.3.5) >>
->> endobj
-939 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 194.596 539.579 203.618]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.5.3.6) >>
->> endobj
-940 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 181.046 539.579 190.069]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.5.3.7) >>
->> endobj
-941 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 167.497 539.579 176.52]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.5.3.8) >>
->> endobj
-942 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 153.948 539.579 162.971]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.5.3.9) >>
->> endobj
-943 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 140.399 539.579 149.422]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.5.3.10) >>
->> endobj
-944 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 126.85 539.579 135.872]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.5.3.11) >>
->> endobj
-945 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 113.3 539.579 122.323]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.5.3.12) >>
->> endobj
-946 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 99.751 539.579 108.774]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.5.3.13) >>
->> endobj
-947 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 86.202 539.579 95.225]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.5.3.14) >>
->> endobj
-948 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 72.653 539.579 81.676]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.5.3.15) >>
->> endobj
-949 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 59.104 539.579 68.127]
-/Subtype /Link
-/A << /S /GoTo /D (section.5.4) >>
->> endobj
-908 0 obj <<
-/D [906 0 R /XYZ 85.039 786.531 null]
->> endobj
-909 0 obj <<
-/D [906 0 R /XYZ 85.039 656.613 null]
->> endobj
-905 0 obj <<
-/Font << /F20 877 0 R /F15 895 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-952 0 obj <<
-/Length 2006
-/Filter /FlateDecode
->>
-stream
-xI{8 Z&i>Ri& S2€Ûäߏ>I5)f3XzcsYA`P7WujS?8ng{f&]#WfT;A-zO<SmBWC,ujs~56(z-F?XBf!J ~j"CF2bXf/y[[RY3F;k&8Pb -0!i:CqLt`&zL t@c¡[̆Î^¨(&æÆ­Õ@2Su&#@ -/ EYQu|ly>3žcÝ[©‡Zlpe A_n|3mHx#mLLf 0B<==0[}}8a`(ze5YLK{e?7
-nr4Wq6g Wf+Z8`c58p)P Z4Tg% QC6K#kw-nBTr^0^o9 .M s%wcufr`T##?S!yG9M_}]6 #V2^:M`0,
-By / eR()(bi9DG8LNeWTO~RQ_=
-8b ]d‰[Ê"
-/N3pB+GlisMkH;TJ;>#AQbZ]0wV'X dpDC=\~^ sm~ ~ ?
- !TXbvg^2[PT#YH ?
-n]0qSq_BUTFut~:P.<K6J0m$/$Nq,y JRXcx[-S=2.9Lt#>Õ³ óJTNyrVq
-Gi%>;ZaJR
-Y3TTt8~B
-endobj
-951 0 obj <<
-/Type /Page
-/Contents 952 0 R
-/Resources 950 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 881 0 R
-/Annots [ 957 0 R 958 0 R 959 0 R 960 0 R 961 0 R 962 0 R 963 0 R 964 0 R 965 0 R 966 0 R 967 0 R 968 0 R 969 0 R 970 0 R 971 0 R 972 0 R 973 0 R 974 0 R 975 0 R 976 0 R 977 0 R 978 0 R 979 0 R 980 0 R 981 0 R 982 0 R 983 0 R 984 0 R 985 0 R 986 0 R 987 0 R 988 0 R 989 0 R 990 0 R 991 0 R 992 0 R 993 0 R 994 0 R 995 0 R 996 0 R 997 0 R 998 0 R 999 0 R 1000 0 R 1001 0 R 1002 0 R 1003 0 R 1004 0 R 1005 0 R ]
->> endobj
-957 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 754.651 539.579 763.674]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.5.4.1) >>
->> endobj
-958 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 741.102 539.579 750.125]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.5.4.2) >>
->> endobj
-959 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 727.553 539.579 736.575]
-/Subtype /Link
-/A << /S /GoTo /D (section.5.5) >>
->> endobj
-960 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [525.586 703.094 539.579 712.663]
-/Subtype /Link
-/A << /S /GoTo /D (chapter.6) >>
->> endobj
-961 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 689.545 539.579 698.568]
-/Subtype /Link
-/A << /S /GoTo /D (section.6.1) >>
->> endobj
-962 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 675.996 539.579 685.019]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.6.1.1) >>
->> endobj
-963 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 662.447 539.579 671.469]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.6.1.2) >>
->> endobj
-964 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 648.897 539.579 657.92]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.6.1.3) >>
->> endobj
-965 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 635.348 539.579 644.371]
-/Subtype /Link
-/A << /S /GoTo /D (section.6.2) >>
->> endobj
-966 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 621.799 539.579 630.822]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.6.2.1) >>
->> endobj
-967 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [525.586 597.341 539.579 606.909]
-/Subtype /Link
-/A << /S /GoTo /D (chapter.7) >>
->> endobj
-968 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 583.792 539.579 592.814]
-/Subtype /Link
-/A << /S /GoTo /D (section.7.1) >>
->> endobj
-969 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 570.242 539.579 579.265]
-/Subtype /Link
-/A << /S /GoTo /D (section.7.2) >>
->> endobj
-970 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 556.693 539.579 565.716]
-/Subtype /Link
-/A << /S /GoTo /D (section.7.3) >>
->> endobj
-971 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 543.144 539.579 552.167]
-/Subtype /Link
-/A << /S /GoTo /D (section.7.4) >>
->> endobj
-972 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 529.595 539.579 538.618]
-/Subtype /Link
-/A << /S /GoTo /D (section.7.5) >>
->> endobj
-973 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 516.046 539.579 525.068]
-/Subtype /Link
-/A << /S /GoTo /D (section.7.6) >>
->> endobj
-974 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 502.496 539.579 511.519]
-/Subtype /Link
-/A << /S /GoTo /D (section.7.7) >>
->> endobj
-975 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 488.947 539.579 497.97]
-/Subtype /Link
-/A << /S /GoTo /D (section.7.8) >>
->> endobj
-976 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 475.398 539.579 484.421]
-/Subtype /Link
-/A << /S /GoTo /D (section.7.9) >>
->> endobj
-977 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [525.586 450.94 539.579 460.508]
-/Subtype /Link
-/A << /S /GoTo /D (chapter.8) >>
->> endobj
-978 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [525.586 426.481 539.579 436.05]
-/Subtype /Link
-/A << /S /GoTo /D (chapter.9) >>
->> endobj
-979 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 412.932 539.579 421.955]
-/Subtype /Link
-/A << /S /GoTo /D (section.9.1) >>
->> endobj
-980 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 399.383 539.579 408.406]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.9.1.1) >>
->> endobj
-981 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 385.834 539.579 394.857]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.9.1.2) >>
->> endobj
-982 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 372.285 539.579 381.307]
-/Subtype /Link
-/A << /S /GoTo /D (section.9.2) >>
->> endobj
-983 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 358.735 539.579 367.758]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.9.2.1) >>
->> endobj
-984 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 345.186 539.579 354.209]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.9.2.2) >>
->> endobj
-985 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 331.637 539.579 340.66]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.9.2.2.1) >>
->> endobj
-986 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 318.088 539.579 327.111]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.9.2.2.2) >>
->> endobj
-987 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 304.539 539.579 313.561]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.9.2.3) >>
->> endobj
-988 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 290.989 539.579 300.012]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.9.2.3.1) >>
->> endobj
-989 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 277.44 539.579 286.463]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.9.2.3.2) >>
->> endobj
-990 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 263.891 539.579 272.914]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.9.2.3.3) >>
->> endobj
-991 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 250.342 539.579 259.365]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.9.2.3.4) >>
->> endobj
-992 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 236.793 539.579 245.815]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.9.2.3.5) >>
->> endobj
-993 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 223.243 539.579 232.266]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.9.2.3.6) >>
->> endobj
-994 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 209.694 539.579 218.717]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.9.2.3.7) >>
->> endobj
-995 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 196.145 539.579 205.168]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.9.2.3.8) >>
->> endobj
-996 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 182.596 539.579 191.619]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.9.2.3.9) >>
->> endobj
-997 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 169.047 539.579 178.069]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.9.2.3.10) >>
->> endobj
-998 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 155.497 539.579 164.52]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.9.2.3.11) >>
->> endobj
-999 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 141.948 539.579 150.971]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.9.2.3.12) >>
->> endobj
-1000 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 128.399 539.579 137.422]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.9.2.3.13) >>
->> endobj
-1001 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 114.85 539.579 123.873]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.9.2.3.14) >>
->> endobj
-1002 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 101.301 539.579 110.323]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.9.2.3.15) >>
->> endobj
-1003 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 87.751 539.579 96.774]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.9.2.3.16) >>
->> endobj
-1004 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 74.202 539.579 83.225]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.9.2.3.17) >>
->> endobj
-1005 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 60.653 539.579 69.676]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.9.2.3.18) >>
->> endobj
-953 0 obj <<
-/D [951 0 R /XYZ 85.039 786.531 null]
->> endobj
-950 0 obj <<
-/Font << /F58 956 0 R /F15 895 0 R /F20 877 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-1008 0 obj <<
-/Length 1848
-/Filter /FlateDecode
->>
-stream
-x][s8~W3E$MII.8\C(Mfl};GGAMPS0
-484k1_8+v
-_!"V66SDiIs‰Ù˜á•NW /]bP5}b_|hŒC[g@?u
- H?Jv5"qSO: "XOo JI:\y,uct{f(3P`
-#XpqodIn8Nq: {u<b/S{P]wî,dƒüØÌڔ-jD339j9e12&Q4p4Zy<9''ek5!}{) ij
-$}f÷c,†lóÏO,o_BcKc^
-endobj
-1007 0 obj <<
-/Type /Page
-/Contents 1008 0 R
-/Resources 1006 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 881 0 R
-/Annots [ 1010 0 R 1011 0 R 1012 0 R 1013 0 R 1014 0 R 1015 0 R 1016 0 R 1017 0 R 1018 0 R 1019 0 R 1020 0 R 1021 0 R 1022 0 R 1023 0 R 1024 0 R 1025 0 R 1026 0 R 1027 0 R 1028 0 R 1029 0 R 1030 0 R 1031 0 R 1032 0 R 1033 0 R 1034 0 R 1035 0 R 1036 0 R 1037 0 R 1038 0 R 1039 0 R 1040 0 R 1041 0 R 1042 0 R 1043 0 R 1044 0 R 1045 0 R 1046 0 R 1047 0 R 1048 0 R 1049 0 R 1050 0 R 1051 0 R 1052 0 R 1053 0 R 1054 0 R 1055 0 R 1056 0 R 1057 0 R 1058 0 R 1059 0 R 1060 0 R 1061 0 R ]
->> endobj
-1010 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 754.651 539.579 763.674]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.9.2.3.19) >>
->> endobj
-1011 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 741.102 539.579 750.125]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.9.2.3.20) >>
->> endobj
-1012 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 727.553 539.579 736.575]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.9.2.3.21) >>
->> endobj
-1013 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 714.003 539.579 723.026]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.9.2.3.22) >>
->> endobj
-1014 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 700.454 539.579 709.477]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.9.2.3.23) >>
->> endobj
-1015 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 686.905 539.579 695.928]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.9.2.3.24) >>
->> endobj
-1016 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 673.356 539.579 682.379]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.9.2.3.25) >>
->> endobj
-1017 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 659.807 539.579 668.829]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.9.2.3.26) >>
->> endobj
-1018 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 646.257 539.579 655.28]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.9.2.3.27) >>
->> endobj
-1019 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 632.708 539.579 641.731]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.9.2.3.28) >>
->> endobj
-1020 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 619.159 539.579 628.182]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.9.2.3.29) >>
->> endobj
-1021 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 605.61 539.579 614.633]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.9.2.3.30) >>
->> endobj
-1022 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 592.061 539.579 601.083]
-/Subtype /Link
-/A << /S /GoTo /D (section.9.3) >>
->> endobj
-1023 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 578.511 539.579 587.534]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.9.3.1) >>
->> endobj
-1024 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 564.962 539.579 573.985]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.9.3.2) >>
->> endobj
-1025 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 551.413 539.579 560.436]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.9.3.2.1) >>
->> endobj
-1026 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 537.864 539.579 546.887]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.9.3.2.2) >>
->> endobj
-1027 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 524.315 539.579 533.337]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.9.3.2.3) >>
->> endobj
-1028 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 510.765 539.579 519.788]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.9.3.2.4) >>
->> endobj
-1029 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 497.216 539.579 506.239]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.9.3.2.5) >>
->> endobj
-1030 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 483.667 539.579 492.69]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.9.3.2.6) >>
->> endobj
-1031 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 470.118 539.579 479.141]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.9.3.2.7) >>
->> endobj
-1032 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 456.569 539.579 465.591]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.9.3.2.8) >>
->> endobj
-1033 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 443.019 539.579 452.042]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.9.3.3) >>
->> endobj
-1034 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 429.47 539.579 438.493]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.9.3.4) >>
->> endobj
-1035 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 415.921 539.579 424.944]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.9.3.5) >>
->> endobj
-1036 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 402.372 539.579 411.395]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.9.3.6) >>
->> endobj
-1037 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 388.823 539.579 397.845]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.9.3.6.1) >>
->> endobj
-1038 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 375.273 539.579 384.296]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.9.3.6.2) >>
->> endobj
-1039 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 361.724 539.579 370.747]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.9.3.7) >>
->> endobj
-1040 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 348.175 539.579 357.198]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.9.3.7.1) >>
->> endobj
-1041 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 334.626 539.579 343.649]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.9.3.7.2) >>
->> endobj
-1042 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 321.077 539.579 330.099]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.9.3.8) >>
->> endobj
-1043 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 307.527 539.579 316.55]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.9.3.8.1) >>
->> endobj
-1044 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 293.978 539.579 303.001]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.9.3.8.2) >>
->> endobj
-1045 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 280.429 539.579 289.452]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.9.3.9) >>
->> endobj
-1046 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 266.88 539.579 275.903]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.9.3.9.1) >>
->> endobj
-1047 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 253.331 539.579 262.354]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.9.3.9.2) >>
->> endobj
-1048 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 239.781 539.579 248.804]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.9.3.10) >>
->> endobj
-1049 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 226.232 539.579 235.255]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.9.3.10.1) >>
->> endobj
-1050 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 212.683 539.579 221.706]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.9.3.10.2) >>
->> endobj
-1051 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 199.134 539.579 208.157]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.9.3.11) >>
->> endobj
-1052 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 185.585 539.579 194.608]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.9.3.11.1) >>
->> endobj
-1053 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 172.036 539.579 181.058]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.9.3.11.2) >>
->> endobj
-1054 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 158.486 539.579 167.509]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.9.3.12) >>
->> endobj
-1055 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 144.937 539.579 153.96]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.9.3.12.1) >>
->> endobj
-1056 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 131.388 539.579 140.411]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.9.3.12.2) >>
->> endobj
-1057 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 117.839 539.579 126.862]
-/Subtype /Link
-/A << /S /GoTo /D (section.9.4) >>
->> endobj
-1058 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 104.29 539.579 113.312]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.9.4.1) >>
->> endobj
-1059 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 90.74 539.579 99.763]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.9.4.1.1) >>
->> endobj
-1060 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 77.191 539.579 86.214]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.9.4.1.2) >>
->> endobj
-1061 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 63.642 539.579 72.665]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.9.4.2) >>
->> endobj
-1009 0 obj <<
-/D [1007 0 R /XYZ 85.039 786.531 null]
->> endobj
-1006 0 obj <<
-/Font << /F58 956 0 R /F15 895 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-1064 0 obj <<
-/Length 1717
-/Filter /FlateDecode
->>
-stream
-x]w8+|pa@\NM7um&6oNHIMD'eG@./=G0nsWNmr^zkz+dN7j#}{ozs=j|6E h\0GpV}7<kC$]GJ^=3K9pCXnyL sg9p<}-zmyC}< ' w,YhAl+b &vVL.N`u^ bY]e`D'D lp` V w }7fdrdRH$_G>?Kg|9v D)Vo.ag%t!‰0*yˆ*)ŒJT%Y\[R)nI};}-iLHxZ6-p}fY9\U}8RbrM
--:[n]B1-nb/mAsf\hKZehq `}I&w:26#OxX{nB/l|,{dV&P.ZM;A`H)KM'^;YyUrM^Y9QB0
-R-3Wb9M7W>u4:Mf@';BFnXf*LeW6g0Yw}@2W9 1r &6}vfOx+/ -"w!endstream
-endobj
-1063 0 obj <<
-/Type /Page
-/Contents 1064 0 R
-/Resources 1062 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 881 0 R
-/Annots [ 1066 0 R 1067 0 R 1068 0 R 1069 0 R 1070 0 R 1071 0 R 1072 0 R 1073 0 R 1074 0 R 1075 0 R 1076 0 R 1080 0 R 1081 0 R 1082 0 R 1083 0 R 1084 0 R 1085 0 R 1086 0 R 1087 0 R 1088 0 R 1089 0 R 1090 0 R 1091 0 R 1092 0 R 1093 0 R 1094 0 R 1095 0 R 1096 0 R 1097 0 R 1098 0 R 1099 0 R 1100 0 R 1101 0 R 1102 0 R 1103 0 R 1104 0 R 1105 0 R 1106 0 R 1107 0 R 1108 0 R 1109 0 R 1110 0 R 1111 0 R 1112 0 R 1113 0 R 1114 0 R 1115 0 R 1116 0 R 1117 0 R 1118 0 R ]
->> endobj
-1066 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 754.651 539.579 763.674]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.9.4.2.1) >>
->> endobj
-1067 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 741.102 539.579 750.125]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.9.4.2.2) >>
->> endobj
-1068 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 727.553 539.579 736.575]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.9.4.3) >>
->> endobj
-1069 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 714.003 539.579 723.026]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.9.4.3.1) >>
->> endobj
-1070 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 700.454 539.579 709.477]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.9.4.3.2) >>
->> endobj
-1071 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 686.905 539.579 695.928]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.9.4.4) >>
->> endobj
-1072 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 673.356 539.579 682.379]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.9.4.4.1) >>
->> endobj
-1073 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 659.807 539.579 668.829]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.9.4.4.2) >>
->> endobj
-1074 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 646.257 539.579 655.28]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.9.4.5) >>
->> endobj
-1075 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 632.708 539.579 641.731]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.9.4.5.1) >>
->> endobj
-1076 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 619.159 539.579 628.182]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.9.4.5.2) >>
->> endobj
-1080 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 605.61 539.579 614.633]
-/Subtype /Link
-/A << /S /GoTo /D (section.9.5) >>
->> endobj
-1081 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 592.061 539.579 601.083]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.9.5.1) >>
->> endobj
-1082 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 578.511 539.579 587.534]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.9.5.1.1) >>
->> endobj
-1083 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 564.962 539.579 573.985]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.9.5.1.2) >>
->> endobj
-1084 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 551.413 539.579 560.436]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.9.5.2) >>
->> endobj
-1085 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 537.864 539.579 546.887]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.9.5.2.1) >>
->> endobj
-1086 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 524.315 539.579 533.337]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.9.5.2.2) >>
->> endobj
-1087 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 510.765 539.579 519.788]
-/Subtype /Link
-/A << /S /GoTo /D (section.9.6) >>
->> endobj
-1088 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 497.216 539.579 506.239]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.9.6.1) >>
->> endobj
-1089 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 483.667 539.579 492.69]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.9.6.1.1) >>
->> endobj
-1090 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 470.118 539.579 479.141]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.9.6.1.2) >>
->> endobj
-1091 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 456.569 539.579 465.591]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.9.6.2) >>
->> endobj
-1092 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 443.019 539.579 452.042]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.9.6.2.1) >>
->> endobj
-1093 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 429.47 539.579 438.493]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.9.6.2.2) >>
->> endobj
-1094 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 415.921 539.579 424.944]
-/Subtype /Link
-/A << /S /GoTo /D (section.9.7) >>
->> endobj
-1095 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 402.372 539.579 411.395]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.9.7.1) >>
->> endobj
-1096 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 388.823 539.579 397.845]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.9.7.2) >>
->> endobj
-1097 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 375.273 539.579 384.296]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.9.7.3) >>
->> endobj
-1098 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 361.724 539.579 370.747]
-/Subtype /Link
-/A << /S /GoTo /D (section.9.8) >>
->> endobj
-1099 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 348.175 539.579 357.198]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.9.8.1) >>
->> endobj
-1100 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 334.626 539.579 343.649]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.9.8.1.1) >>
->> endobj
-1101 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 321.077 539.579 330.099]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.9.8.1.2) >>
->> endobj
-1102 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 307.527 539.579 316.55]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.9.8.2) >>
->> endobj
-1103 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 293.978 539.579 303.001]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.9.8.2.1) >>
->> endobj
-1104 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 280.429 539.579 289.452]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.9.8.2.2) >>
->> endobj
-1105 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 266.88 539.579 275.903]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.9.8.2.3) >>
->> endobj
-1106 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [525.586 242.422 539.579 251.99]
-/Subtype /Link
-/A << /S /GoTo /D (chapter.10) >>
->> endobj
-1107 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 228.872 539.579 237.895]
-/Subtype /Link
-/A << /S /GoTo /D (section.10.1) >>
->> endobj
-1108 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 215.323 539.579 224.346]
-/Subtype /Link
-/A << /S /GoTo /D (section.10.2) >>
->> endobj
-1109 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 201.774 539.579 210.797]
-/Subtype /Link
-/A << /S /GoTo /D (section.10.3) >>
->> endobj
-1110 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 188.225 539.579 197.248]
-/Subtype /Link
-/A << /S /GoTo /D (section.10.4) >>
->> endobj
-1111 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 174.676 539.579 183.698]
-/Subtype /Link
-/A << /S /GoTo /D (section.10.5) >>
->> endobj
-1112 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [525.586 150.217 539.579 159.786]
-/Subtype /Link
-/A << /S /GoTo /D (chapter.11) >>
->> endobj
-1113 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 136.668 539.579 145.691]
-/Subtype /Link
-/A << /S /GoTo /D (section.11.1) >>
->> endobj
-1114 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [525.586 112.21 539.579 121.778]
-/Subtype /Link
-/A << /S /GoTo /D (chapter.12) >>
->> endobj
-1115 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 98.661 539.579 107.683]
-/Subtype /Link
-/A << /S /GoTo /D (section.12.1) >>
->> endobj
-1116 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 85.111 539.579 94.134]
-/Subtype /Link
-/A << /S /GoTo /D (section.12.2) >>
->> endobj
-1117 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 71.562 539.579 80.585]
-/Subtype /Link
-/A << /S /GoTo /D (section.12.3) >>
->> endobj
-1118 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 58.013 539.579 67.036]
-/Subtype /Link
-/A << /S /GoTo /D (section.12.4) >>
->> endobj
-1065 0 obj <<
-/D [1063 0 R /XYZ 85.039 786.531 null]
->> endobj
-1062 0 obj <<
-/Font << /F58 956 0 R /F15 895 0 R /F43 1079 0 R /F20 877 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-1121 0 obj <<
-/Length 1144
-/Filter /FlateDecode
->>
-stream
-xZMsHWpfeJMEY'Ve0YKhA*~Aea*3 h^w(1(BEEF%{ÂÌi¹ԓ„j…Sz/(1Jb{oAULnYnUuzMBIxz_R/zD[' J
-w~;}\I^P2NPPb\nMZIXj)4`(Mf#xP3 T <tn`&)#gNW;57x7 7[OA(NxAŒ’‡pnŒî <Z(
-}B3c|H "A|=~B'mq}CHfQru8
-QV
-hf
-5V,#%q;uj{:/IE';u
-endobj
-1120 0 obj <<
-/Type /Page
-/Contents 1121 0 R
-/Resources 1119 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 1148 0 R
-/Annots [ 1123 0 R 1124 0 R 1125 0 R 1126 0 R 1127 0 R 1128 0 R 1129 0 R 1130 0 R 1131 0 R 1132 0 R 1133 0 R 1134 0 R 1135 0 R 1136 0 R 1137 0 R 1138 0 R 1139 0 R 1140 0 R 1141 0 R 1142 0 R 1143 0 R 1144 0 R 1145 0 R 1146 0 R 1147 0 R ]
->> endobj
-1123 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 754.651 539.579 763.674]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.12.4.1) >>
->> endobj
-1124 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 741.102 539.579 750.125]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.12.4.2) >>
->> endobj
-1125 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 727.553 539.579 736.575]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.12.4.3) >>
->> endobj
-1126 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 714.003 539.579 723.026]
-/Subtype /Link
-/A << /S /GoTo /D (section.12.5) >>
->> endobj
-1127 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 700.454 539.579 709.477]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.12.5.1) >>
->> endobj
-1128 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 686.905 539.579 695.928]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.12.5.2) >>
->> endobj
-1129 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 673.356 539.579 682.379]
-/Subtype /Link
-/A << /S /GoTo /D (section.12.6) >>
->> endobj
-1130 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 659.807 539.579 668.829]
-/Subtype /Link
-/A << /S /GoTo /D (section.12.7) >>
->> endobj
-1131 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [525.586 635.348 539.579 644.917]
-/Subtype /Link
-/A << /S /GoTo /D (chapter.13) >>
->> endobj
-1132 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 621.799 539.579 630.822]
-/Subtype /Link
-/A << /S /GoTo /D (section.13.1) >>
->> endobj
-1133 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 608.25 539.579 617.273]
-/Subtype /Link
-/A << /S /GoTo /D (section.13.2) >>
->> endobj
-1134 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 594.701 539.579 603.724]
-/Subtype /Link
-/A << /S /GoTo /D (section.13.3) >>
->> endobj
-1135 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [525.586 570.242 539.579 579.811]
-/Subtype /Link
-/A << /S /GoTo /D (chapter.14) >>
->> endobj
-1136 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 556.693 539.579 565.716]
-/Subtype /Link
-/A << /S /GoTo /D (section.14.1) >>
->> endobj
-1137 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 543.144 539.579 552.167]
-/Subtype /Link
-/A << /S /GoTo /D (section.14.2) >>
->> endobj
-1138 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 529.595 539.579 538.618]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.14.2.1) >>
->> endobj
-1139 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 516.046 539.579 525.068]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.14.2.2) >>
->> endobj
-1140 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 502.496 539.579 511.519]
-/Subtype /Link
-/A << /S /GoTo /D (section.14.3) >>
->> endobj
-1141 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 488.947 539.579 497.97]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.14.3.1) >>
->> endobj
-1142 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [525.586 464.489 539.579 474.057]
-/Subtype /Link
-/A << /S /GoTo /D (chapter.15) >>
->> endobj
-1143 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 450.94 539.579 459.963]
-/Subtype /Link
-/A << /S /GoTo /D (section.15.1) >>
->> endobj
-1144 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 437.39 539.579 446.413]
-/Subtype /Link
-/A << /S /GoTo /D (section.15.2) >>
->> endobj
-1145 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [525.586 412.932 539.579 422.5]
-/Subtype /Link
-/A << /S /GoTo /D (chapter.16) >>
->> endobj
-1146 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 399.383 539.579 408.406]
-/Subtype /Link
-/A << /S /GoTo /D (section.16.1) >>
->> endobj
-1147 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [526.677 385.834 539.579 394.857]
-/Subtype /Link
-/A << /S /GoTo /D (section.16.2) >>
->> endobj
-1122 0 obj <<
-/D [1120 0 R /XYZ 85.039 786.531 null]
->> endobj
-1119 0 obj <<
-/Font << /F58 956 0 R /F15 895 0 R /F20 877 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-1151 0 obj <<
-/Length 2942
-/Filter /FlateDecode
->>
-stream
-x]o8"X+"nk\t^[u%/%o7_h[n{(p87_x1K ..Yqx
-.P04$N| 'F_x=u.
-.b"Nixo4ISMBf2kW;\/k#?oazfT,yNm?/BeLjYvusw8,_+0$;/{; r 0
-
-*sOzM\3yf~(% okB|`hpw:&aq|
-M"@M! QmQ-R(U/NrUj$
-CFq=auHJLdP[:.8OG`~&.WEEXaCX2yS"Sy@b^3pqYBD~ap"@*_#^<=*""dQ&v:vZ*hi/$=+-4,
-o13!HTZvH=.B C#* 6È)x“6øÍPdThF19OAJR(q)_x$a3pQj~!*D"Ir{1$5z6DJe%{(V"V#63$Rxf3"_3w k]s0Kb!bHK(j[*tWxQpj[K:94"!c,'P|9 vue
-`piAI%5
-JAngX- :i=,.~uDM9:$,Thnx^TtRh/dsW35:S.(5hvr}'t\^v.4RTURc O"j Z J4UFVn\@^>/_S&*Q(<i@BZiv;I,qSM0-A $qF_SyEI1x *F]?b|]z,+4VIkl
-$&
-8>pH:f~hh|~
-y58eoJb`1\0`XCRqxWC(rus`Hq_nr(e'GALUejEce/bbx%%-es44L@ld_ GQB]}(0z}eC>*uK-wWO $ '+jgU6yf"4: 3(y%kBB$`55Bu3.Ccn
-8,'MX 9hA0](0]ii9t *]1F=BxkjrL0
-LWXBk &9PcwA2l9^ :W
-endobj
-1150 0 obj <<
-/Type /Page
-/Contents 1151 0 R
-/Resources 1149 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 1148 0 R
->> endobj
-1152 0 obj <<
-/D [1150 0 R /XYZ 85.039 786.531 null]
->> endobj
-6 0 obj <<
-/D [1150 0 R /XYZ 85.039 766.606 null]
->> endobj
-1153 0 obj <<
-/D [1150 0 R /XYZ 85.039 651.298 null]
->> endobj
-10 0 obj <<
-/D [1150 0 R /XYZ 85.039 651.298 null]
->> endobj
-1154 0 obj <<
-/D [1150 0 R /XYZ 85.039 622.563 null]
->> endobj
-14 0 obj <<
-/D [1150 0 R /XYZ 85.039 240.295 null]
->> endobj
-1155 0 obj <<
-/D [1150 0 R /XYZ 85.039 211.559 null]
->> endobj
-1149 0 obj <<
-/Font << /F20 877 0 R /F15 895 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-1158 0 obj <<
-/Length 2860
-/Filter /FlateDecode
->>
-stream
-xZ_o[( "8=9U](PKRq;vIJt4(wZf|Y^q?fq \Wa<=7zK<oW /ys=7
-sZ]_ss{|8Ws}}YVox=,f;_k^wPenR=N@ ?v=_sgo g0\?If @Z1<g!wp 7Qqh0U@nu}7/sVVxf4XtVE2]:-6[$|o#'/ZgM/88>Ywa+AL!w-T=K> WE,d_H0*JC+txmL
-jw?=? o}T+QG!Pt<<:wx;"X}^bJVF,S"qgQ' <jM9
-jY2]7i]=4I3(},rt)]?Gk9V
-{GYG:rc[lT!O/5~}yK, "Z&vv%Cz[ ':K&D(;5%HynFR>%wC?IIFPc%@HiUxhGG| )Zx:
-!.^Fw{$z*` ;ys^¾9G/Mlvfu;fwU\hzx7m9)#/T&bQx AAuvZWCR\h;hklG,y3G ia'07t~`2(v* 6cTWf^b27Mqp
-ll| #D9X93l*ZcxGgI)1jvZYbWlaO< vrOS}{wqDH8W#G@/.lr
-?g%s6QvZ>tz6G+|-rcc4AyvGs8jtrOT(}gNTP$;r $ jx<Z`~qiÍÙÃUr|T@L10 #lOYn\SRzNyEv 0$6s³¡á„\‘1æ±ëwÜ3û ÈÀå\ƵåaÂùMh1&D)&j
-5\[KK_;-Z slG#& l`8adzjP2#oj2^Z
-24NjlEmw7L:)HQe!y$Xn7VaZq OkDZ<^/8tv
-XD{09 i7VbUI*Q8EKw~-W-eh3 @3p6g)UZ(!^1)4WiqGM"9 t"J:A_i0o=~OFj_*}~6'wUAaQS!. $0q pa,vA4jd@cftD
-(rQcCgcKT mn*E_T
-88^=<J=80{$` 6:5Mj8e@XBayS--w__4/_S-fK.N}-}*psB+Mû/)=—p!o»£DOi{Z[# G2qX_l";p>'ztS3UJ
-95S]UP8"~;`HUvi*_D5ipnj% Rp@.#28
-f]L!qa>iQ`
-z+],*ld4mg6nSD T:
-PE? Rv^ 193tu24g{endstream
-endobj
-1157 0 obj <<
-/Type /Page
-/Contents 1158 0 R
-/Resources 1156 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 1148 0 R
->> endobj
-1159 0 obj <<
-/D [1157 0 R /XYZ 85.039 786.531 null]
->> endobj
-18 0 obj <<
-/D [1157 0 R /XYZ 85.039 766.606 null]
->> endobj
-1160 0 obj <<
-/D [1157 0 R /XYZ 85.039 744.844 null]
->> endobj
-1156 0 obj <<
-/Font << /F58 956 0 R /F20 877 0 R /F15 895 0 R /F40 1163 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-1166 0 obj <<
-/Length 2761
-/Filter /FlateDecode
->>
-stream
-xYY7~Ÿ_¡7·€™Nb
-QgYx|"^K{PJ-,~Z^iSWb?+_t0$2Zl#6}m42a8v9]q](z 6va*{JzU
-
-O7v$u`%,IQx>JxRe{H"vYTy'ud%3& Dxd5@<xbv,koxgW^d @{E!SW7 vU]}alrEZ.6:lZhTSd=zVr +H[8OoGa
-Q>-$Ng^67\/I@n'IZ8]ar {J<"<b~!nx#T8fv(j9[UIëãtá^üqjÞs«´Ú1§«TrO@` ~ b* 5P{YBm'2abB+9\PLKU'{o7cw@<a,w2Q7
-!"ytZ3`sU%edg~es0%\F(lW2e ?:
- n/ J9*w@NuIFfRW_ I{ a\S9t"-R3DîÄp„¾ûŽÔ‘4;=P#c+Gfmwsy>X@1j-U 79V&STvPZ&} {bMvSe)8]$L+628#Ct[LnbI vBSP|d"oŒÌ˜ sK7OOTM+'>ub?Go$Cwh_S~+̪1h¶"ÆÎQo11tZ[9; ;̼á ÍyM"27?liClI`/7,6`o?.y$#H5;^q*u.v`GC|iGV,b s0 m02 A=83'|?s%%Rendstream
-endobj
-1165 0 obj <<
-/Type /Page
-/Contents 1166 0 R
-/Resources 1164 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 1148 0 R
->> endobj
-1167 0 obj <<
-/D [1165 0 R /XYZ 85.039 781.388 null]
->> endobj
-22 0 obj <<
-/D [1165 0 R /XYZ 85.039 761.463 null]
->> endobj
-1168 0 obj <<
-/D [1165 0 R /XYZ 85.039 671.062 null]
->> endobj
-26 0 obj <<
-/D [1165 0 R /XYZ 85.039 671.062 null]
->> endobj
-1169 0 obj <<
-/D [1165 0 R /XYZ 85.039 642.326 null]
->> endobj
-1170 0 obj <<
-/D [1165 0 R /XYZ 85.039 578.536 null]
->> endobj
-1171 0 obj <<
-/D [1165 0 R /XYZ 85.039 544.592 null]
->> endobj
-1172 0 obj <<
-/D [1165 0 R /XYZ 85.039 519.956 null]
->> endobj
-30 0 obj <<
-/D [1165 0 R /XYZ 85.039 485.484 null]
->> endobj
-1173 0 obj <<
-/D [1165 0 R /XYZ 85.039 456.08 null]
->> endobj
-34 0 obj <<
-/D [1165 0 R /XYZ 85.039 277.719 null]
->> endobj
-1174 0 obj <<
-/D [1165 0 R /XYZ 85.039 248.314 null]
->> endobj
-1175 0 obj <<
-/D [1165 0 R /XYZ 85.039 227.962 null]
->> endobj
-1176 0 obj <<
-/D [1165 0 R /XYZ 85.039 191.291 null]
->> endobj
-1177 0 obj <<
-/D [1165 0 R /XYZ 85.039 157.953 null]
->> endobj
-1178 0 obj <<
-/D [1165 0 R /XYZ 85.039 92.669 null]
->> endobj
-1164 0 obj <<
-/Font << /F20 877 0 R /F15 895 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-1181 0 obj <<
-/Length 3267
-/Filter /FlateDecode
->>
-stream
-xn7]_!-/x7ÉÈIij>}Ho]dsfZ
-0!bXw+ _xY~yqQ\nr+#L Kq#-./Pn_w]}&c/6y^x7Ww7M?wPC_u$~x_.+ e{&Y*\+m &Hpah+N+~Rd'_R 5}I;\m'7
-xQ{6&i<{
-;ByPS 14!c9 SH#qW5V[kNutEF_6aql_ pI@'W4 08/yQYIfp]'kC~j'H@!"y~&l~YWm#Hh VX0@2.Pa q/L&FF"p(te!PzAFN0==#yl\$>r]
-x=@<=Z0A o[7(+U$mLL})gA<:w2pUxts8>U5pu{ N2mh4)`
-
-v21X6J
-&]rUH%8iPan>(ED(X[vx%\83rr'
-XNZ!Lò_¤ÙÏkêq¾«^ '$‘á<@7-dKt3 `)nN-e$+G0
-#)' 9/4# 2.R1hT*I(Na 9}Il5/R~^
-6?.%ed",e%my)ibdu1
-t
-'J >L 8~*bOM*z9
-+'v*Rg/C)f){B T+xToN3n!~JT[D'^.7jjHwlaT')V\4cF|c=NQw;ÿg”4D7b@\y)]wa 2Y):=z2/
-DC"j"5Wã¤Ù©ÇŸ° ÌC|9FKwLE3BZ&
-X$L[MDT6G*j9EW<k9KP$V`[>`8CvE;|YEdMt&DI
-E1RO.VL ncFm_p/Cn\Or6JZqJ<'b;l*ziq#rdbQ 9(Js ¡{Zi-m8oU7[_ "wtBP;hF%;!BluE_|uC8 x¶¼5›–’enw¬:¡+­§†ç¹ ¨Õ-ƇäGjT`k\*cdy??8ED7<q.yrSqIUtJKeOk fq%nkD)VS&SLr)-ZiF
- 1 bq]^ZX0æÜVcJj;_#
-/)wexCQlIBN"5J+Q7l'j-NP[s3_q4I~@$) (b7z ~N%auJ=; JrtB?nbj'U jA$izDn2uOqs lN eL Id}
-endobj
-1180 0 obj <<
-/Type /Page
-/Contents 1181 0 R
-/Resources 1179 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 1148 0 R
->> endobj
-1182 0 obj <<
-/D [1180 0 R /XYZ 85.039 781.388 null]
->> endobj
-1183 0 obj <<
-/D [1180 0 R /XYZ 85.039 761.463 null]
->> endobj
-1184 0 obj <<
-/D [1180 0 R /XYZ 85.039 732.472 null]
->> endobj
-38 0 obj <<
-/D [1180 0 R /XYZ 85.039 684.451 null]
->> endobj
-1185 0 obj <<
-/D [1180 0 R /XYZ 85.039 652.925 null]
->> endobj
-42 0 obj <<
-/D [1180 0 R /XYZ 85.039 393.269 null]
->> endobj
-1186 0 obj <<
-/D [1180 0 R /XYZ 85.039 363.865 null]
->> endobj
-1179 0 obj <<
-/Font << /F58 956 0 R /F15 895 0 R /F20 877 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-1189 0 obj <<
-/Length 1818
-/Filter /FlateDecode
->>
-stream
-xXYoF~)p<@A(i(";E{gvvyT\8)lh99|j3E0|O&nm,i{c{Y`eN-.etcqLcgszF3nfsn8os|~GCv~X/2$E.X>fv2N^{#2kF2?<?8gŽ+Úën‚ú‚þõ¤%aƒôÅÌòn±0Ê;jCj"V\K6tKbr†™¢šÖÔV:U\c7 H]$'P9g:3[Kv]/A{czE yT=DheU.D"PSjjJ+LM\|~x}4‰ËëE7O=h-KI6T?CIc771b@EN"AE2zfyV*\7ZO8`*JGo4 }&!!s MB4RTvq.#
-t+dC 1GsI1QBiF9KDZT<I 1Y#zo\ Ifw@pJjCwx
-*>A tnGuJ$.Z4!7bX7i,sTIvdF6x[Oq+ 2qWj4A}u4D 7F sDNq; F]0) 4d=,{q=!Eg>Kd )TNr>M3^8z {Y:Og<Bvh>F|GR`[s|Y?]Au/1Um6fJMuAR\W-oBzG2+Ws.3]?R$MuQV\
-[%J>K0y6eg,¤f 5¾o¼áˆÝ"j«_ „ñ ¶•#„×e®¼Š*ÔY ;cYqNPQjEM w8J!j@Q|$4wl$krskN#Q'&DC`O4&&enyOB|? (.<L )p WlHA A-iR!@fJc&OP!
-endobj
-1188 0 obj <<
-/Type /Page
-/Contents 1189 0 R
-/Resources 1187 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 1148 0 R
->> endobj
-1190 0 obj <<
-/D [1188 0 R /XYZ 85.039 781.388 null]
->> endobj
-46 0 obj <<
-/D [1188 0 R /XYZ 85.039 761.463 null]
->> endobj
-1191 0 obj <<
-/D [1188 0 R /XYZ 85.039 667.044 null]
->> endobj
-50 0 obj <<
-/D [1188 0 R /XYZ 85.039 667.044 null]
->> endobj
-1192 0 obj <<
-/D [1188 0 R /XYZ 85.039 639.536 null]
->> endobj
-1193 0 obj <<
-/D [1188 0 R /XYZ 85.039 351.388 null]
->> endobj
-1194 0 obj <<
-/D [1188 0 R /XYZ 85.039 328.872 null]
->> endobj
-1195 0 obj <<
-/D [1188 0 R /XYZ 85.039 292.807 null]
->> endobj
-1196 0 obj <<
-/D [1188 0 R /XYZ 85.039 201.94 null]
->> endobj
-1187 0 obj <<
-/Font << /F20 877 0 R /F15 895 0 R /F37 900 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-1199 0 obj <<
-/Length 2079
-/Filter /FlateDecode
->>
-stream
-xYYoF~ 
-Y+}JZ'qGEZdc\Tmsvofo.7OBW<N<7Hz?<yKWD!n=]= 'T6o_<qube'%/^xOL:\<^pzz)]|};n&; K~& e'CoMHw /&4zj#n2)*½•]/–~âÔ øóÿèõüÏl¿Xz- =bWUQkrU[Nf
-;eI|KafmQWl2u-K-C$?Ju0<cPDNj@%ky#r0hD*" VÞ²¹²¯¬kc…¢Ì^Üԃdmu®xµíðԁ…@iFt9r 9`O{p~ O7^]XHe 4vEn i[zp(3>,K7 pXhb54y'B;/uSO`øOnlo0z!qAV4,Z>jWjo
-e =@Vg&vg<Ak|eMosj4:_W/iL)D;&.Otv!tR#8\.5L['y*t eb*2FT&=Dsb5cg<De4d%N[F8vl|_5p2^id-Dy/{!X-WNB[`tw%\,&=|hOZ0Sxe2} ai?,BPI{o]q:PCNY8:!8jbP1Cjeo"e((O`hCOx-TVwSPZ<W><
-3~g}:vhpÖ]«Å"}OE>A %t2Bwa S[P8&d7Rx I?2C _RX}j4m QaE@5;j&7J Wd7hMZPLl .T]_UnSc8"H=fU@2FBQ{6 j]--<"HUp"-Av*j)Vs.qQ-*Dk?JNJ1Pisj2[7,ZwCwiE=I:D%Y >R;em
-endobj
-1198 0 obj <<
-/Type /Page
-/Contents 1199 0 R
-/Resources 1197 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 1202 0 R
->> endobj
-1200 0 obj <<
-/D [1198 0 R /XYZ 85.039 781.388 null]
->> endobj
-54 0 obj <<
-/D [1198 0 R /XYZ 85.039 707.104 null]
->> endobj
-1201 0 obj <<
-/D [1198 0 R /XYZ 85.039 674.781 null]
->> endobj
-1197 0 obj <<
-/Font << /F58 956 0 R /F15 895 0 R /F20 877 0 R /F37 900 0 R /F43 1079 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-1205 0 obj <<
-/Length 1639
-/Filter /FlateDecode
->>
-stream
-xko6P` X
-)R&}0E [-DWQ+NBxw-
-}
-B0Y+qC,+?8s#Y&%_o>.;B[c'B{
-}Ò,-v26°­Ê9J49]M( M+TbTb&VQ"iiYb.3z:}3%;]§…úÑ=¾"ÐJÀ0&èZ z)o6;I+5m`C}Z ^B;Q:Vx-J;u6PGAm}/d*Ll5HM,oDO%7y7&oV.Ad:;;7`*)up@ F
-xHU}1RbR!3 m[{mJ oV#<fHt
-endobj
-1204 0 obj <<
-/Type /Page
-/Contents 1205 0 R
-/Resources 1203 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 1202 0 R
->> endobj
-1206 0 obj <<
-/D [1204 0 R /XYZ 85.039 781.388 null]
->> endobj
-58 0 obj <<
-/D [1204 0 R /XYZ 85.039 665.791 null]
->> endobj
-1207 0 obj <<
-/D [1204 0 R /XYZ 85.039 635.59 null]
->> endobj
-62 0 obj <<
-/D [1204 0 R /XYZ 85.039 383.634 null]
->> endobj
-1208 0 obj <<
-/D [1204 0 R /XYZ 85.039 351.312 null]
->> endobj
-1203 0 obj <<
-/Font << /F58 956 0 R /F37 900 0 R /F15 895 0 R /F20 877 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-1211 0 obj <<
-/Length 2161
-/Filter /FlateDecode
->>
-stream
-xY68 (R($-C8-Xl"K>I^g?~$6i 3r?58xf^PxczaSg/_Xyn%Hfy=i2Z;L(vfxD97?<qnKof8w@&(?~KP$*I -ýbôfôcDžç̘W]h u07MU]rn;/&4Y/EZo,}Y~%Tek'nNb.jnN5BHF= Jn4ye\-0b+R ;+pv m8  n|8M4l.z-{
-%,&S9Dk^—}Øióe¶äóÉԏ¬¨&ð9¸ÄêÌ ·Éi «m›?+QYI:i,tv F .\ &b;4OF|W{R< 6li@c/;e&(DZkq6PU%21U<"sw~
-
-_'1(%=:ihp_y:]xz)-YH^'ez,hgX-l7(ZH
-_W'*osk[bKe|/@R&-k$d)Wo eV[T"Fyj.qO8= !GqyA3
-V/N
-!%t2›`»kÑ¡'±q
-ÉUEgxo# ¾e%ºµÍ† ìá©t7WO'þ>¡RoDw- ytxeuAbm9dZ)"|uyU'|
-ITWdu^ ..pGk&%:eD\d\xd9m+9·ÕÕ¡dlô™/¤ƒKv[m"+
-&/(-R|)f|
-endobj
-1210 0 obj <<
-/Type /Page
-/Contents 1211 0 R
-/Resources 1209 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 1202 0 R
->> endobj
-1212 0 obj <<
-/D [1210 0 R /XYZ 85.039 781.388 null]
->> endobj
-1213 0 obj <<
-/D [1210 0 R /XYZ 85.039 634.111 null]
->> endobj
-1214 0 obj <<
-/D [1210 0 R /XYZ 85.039 611.596 null]
->> endobj
-1215 0 obj <<
-/D [1210 0 R /XYZ 85.039 577.652 null]
->> endobj
-66 0 obj <<
-/D [1210 0 R /XYZ 85.039 529.631 null]
->> endobj
-1216 0 obj <<
-/D [1210 0 R /XYZ 85.039 500.895 null]
->> endobj
-70 0 obj <<
-/D [1210 0 R /XYZ 85.039 500.895 null]
->> endobj
-1217 0 obj <<
-/D [1210 0 R /XYZ 85.039 476.914 null]
->> endobj
-74 0 obj <<
-/D [1210 0 R /XYZ 85.039 407.713 null]
->> endobj
-1218 0 obj <<
-/D [1210 0 R /XYZ 85.039 386.459 null]
->> endobj
-78 0 obj <<
-/D [1210 0 R /XYZ 85.039 303.709 null]
->> endobj
-1219 0 obj <<
-/D [1210 0 R /XYZ 85.039 282.454 null]
->> endobj
-1209 0 obj <<
-/Font << /F58 956 0 R /F37 900 0 R /F15 895 0 R /F20 877 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-1222 0 obj <<
-/Length 3244
-/Filter /FlateDecode
->>
-stream
-xksf!RDMs$L$%Hb">Nv~}Kb,$O<?ZL<<,wWd#\'1 < =?y{ __]$4&kB_2g$7f66H]-fT^=?q8H&p;1O0;
- i -Pb`<"l-z=<%c
-{ZQu?Y?-[y ,KU™Ñ”Åf; §|’ÃôBZy >K}xU !nXS uF
-(++l8=fcg#V pkuA2)`
+%PDF-1.3
+%
+1 0 obj<</Producer(htmldoc 1.8.22 Copyright 1997-2002 Easy Software Products, All Rights Reserved.)/CreationDate(D:20030115164419+0600)/Title(SAMBA Developers Guide)/Creator(Modular DocBook HTML Stylesheet Version 1.77)>>endobj
+2 0 obj<</Type/Encoding/Differences[ 32/space/exclam/quotedbl/numbersign/dollar/percent/ampersand/quotesingle/parenleft/parenright/asterisk/plus/comma/minus/period/slash/zero/one/two/three/four/five/six/seven/eight/nine/colon/semicolon/less/equal/greater/question/at/A/B/C/D/E/F/G/H/I/J/K/L/M/N/O/P/Q/R/S/T/U/V/W/X/Y/Z/bracketleft/backslash/bracketright/asciicircum/underscore/grave/a/b/c/d/e/f/g/h/i/j/k/l/m/n/o/p/q/r/s/t/u/v/w/x/y/z/braceleft/bar/braceright/asciitilde 128/Euro 130/quotesinglbase/florin/quotedblbase/ellipsis/dagger/daggerdbl/circumflex/perthousand/Scaron/guilsinglleft/OE 145/quoteleft/quoteright/quotedblleft/quotedblright/bullet/endash/emdash/tilde/trademark/scaron/guilsinglright/oe 159/Ydieresis/space/exclamdown/cent/sterling/currency/yen/brokenbar/section/dieresis/copyright/ordfeminine/guillemotleft/logicalnot/hyphen/registered/macron/degree/plusminus/twosuperior/threesuperior/acute/mu/paragraph/periodcentered/cedilla/onesuperior/ordmasculine/guillemotright/onequarter/onehalf/threequarters/questiondown/Agrave/Aacute/Acircumflex/Atilde/Adieresis/Aring/AE/Ccedilla/Egrave/Eacute/Ecircumflex/Edieresis/Igrave/Iacute/Icircumflex/Idieresis/Eth/Ntilde/Ograve/Oacute/Ocircumflex/Otilde/Odieresis/multiply/Oslash/Ugrave/Uacute/Ucircumflex/Udieresis/Yacute/Thorn/germandbls/agrave/aacute/acircumflex/atilde/adieresis/aring/ae/ccedilla/egrave/eacute/ecircumflex/edieresis/igrave/iacute/icircumflex/idieresis/eth/ntilde/ograve/oacute/ocircumflex/otilde/odieresis/divide/oslash/ugrave/uacute/ucircumflex/udieresis/yacute/thorn/ydieresis]>>endobj
+3 0 obj<</Type/Font/Subtype/Type1/BaseFont/Courier/Encoding 2 0 R>>endobj
+4 0 obj<</Type/Font/Subtype/Type1/BaseFont/Courier-Bold/Encoding 2 0 R>>endobj
+5 0 obj<</Type/Font/Subtype/Type1/BaseFont/Courier-Oblique/Encoding 2 0 R>>endobj
+6 0 obj<</Type/Font/Subtype/Type1/BaseFont/Times-Roman/Encoding 2 0 R>>endobj
+7 0 obj<</Type/Font/Subtype/Type1/BaseFont/Times-Bold/Encoding 2 0 R>>endobj
+8 0 obj<</Type/Font/Subtype/Type1/BaseFont/Times-Italic/Encoding 2 0 R>>endobj
+9 0 obj<</Type/Font/Subtype/Type1/BaseFont/Times-BoldItalic/Encoding 2 0 R>>endobj
+10 0 obj<</Type/Font/Subtype/Type1/BaseFont/Helvetica/Encoding 2 0 R>>endobj
+11 0 obj<</Type/Font/Subtype/Type1/BaseFont/Helvetica-Bold/Encoding 2 0 R>>endobj
+12 0 obj<</Type/Font/Subtype/Type1/BaseFont/Symbol>>endobj
+13 0 obj<</Subtype/Link/Rect[72.0 684.0 197.9 697.0]/Border[0 0 0]/Dest[524 0 R/XYZ 0 734 0]>>endobj
+14 0 obj<</Subtype/Link/Rect[108.0 670.8 174.9 683.8]/Border[0 0 0]/Dest[524 0 R/XYZ 0 696 0]>>endobj
+15 0 obj<</Subtype/Link/Rect[72.0 644.4 112.9 657.4]/Border[0 0 0]/Dest[526 0 R/XYZ 0 734 0]>>endobj
+16 0 obj<</Subtype/Link/Rect[72.0 618.0 409.3 631.0]/Border[0 0 0]/Dest[532 0 R/XYZ 0 734 0]>>endobj
+17 0 obj<</Subtype/Link/Rect[108.0 604.8 173.7 617.8]/Border[0 0 0]/Dest[532 0 R/XYZ 0 672 0]>>endobj
+18 0 obj<</Subtype/Link/Rect[108.0 591.6 237.6 604.6]/Border[0 0 0]/Dest[532 0 R/XYZ 0 201 0]>>endobj
+19 0 obj<</Subtype/Link/Rect[108.0 578.4 200.3 591.4]/Border[0 0 0]/Dest[534 0 R/XYZ 0 705 0]>>endobj
+20 0 obj<</Subtype/Link/Rect[72.0 552.0 219.9 565.0]/Border[0 0 0]/Dest[536 0 R/XYZ 0 734 0]>>endobj
+21 0 obj<</Subtype/Link/Rect[108.0 538.8 181.6 551.8]/Border[0 0 0]/Dest[536 0 R/XYZ 0 696 0]>>endobj
+22 0 obj<</Subtype/Link/Rect[108.0 525.6 244.6 538.6]/Border[0 0 0]/Dest[536 0 R/XYZ 0 529 0]>>endobj
+23 0 obj<</Subtype/Link/Rect[108.0 512.4 199.0 525.4]/Border[0 0 0]/Dest[536 0 R/XYZ 0 335 0]>>endobj
+24 0 obj<</Subtype/Link/Rect[108.0 499.2 200.3 512.2]/Border[0 0 0]/Dest[538 0 R/XYZ 0 734 0]>>endobj
+25 0 obj<</Subtype/Link/Rect[108.0 486.0 186.2 499.0]/Border[0 0 0]/Dest[538 0 R/XYZ 0 434 0]>>endobj
+26 0 obj<</Subtype/Link/Rect[72.0 459.6 252.9 472.6]/Border[0 0 0]/Dest[540 0 R/XYZ 0 734 0]>>endobj
+27 0 obj<</Subtype/Link/Rect[108.0 446.4 214.6 459.4]/Border[0 0 0]/Dest[540 0 R/XYZ 0 696 0]>>endobj
+28 0 obj<</Subtype/Link/Rect[108.0 433.2 223.8 446.2]/Border[0 0 0]/Dest[542 0 R/XYZ 0 734 0]>>endobj
+29 0 obj<</Subtype/Link/Rect[108.0 420.0 247.6 433.0]/Border[0 0 0]/Dest[544 0 R/XYZ 0 734 0]>>endobj
+30 0 obj<</Subtype/Link/Rect[108.0 406.8 245.2 419.8]/Border[0 0 0]/Dest[544 0 R/XYZ 0 514 0]>>endobj
+31 0 obj<</Subtype/Link/Rect[108.0 393.6 194.2 406.6]/Border[0 0 0]/Dest[546 0 R/XYZ 0 734 0]>>endobj
+32 0 obj<</Subtype/Link/Rect[126.0 380.4 193.8 393.4]/Border[0 0 0]/Dest[546 0 R/XYZ 0 700 0]>>endobj
+33 0 obj<</Subtype/Link/Rect[126.0 367.2 192.0 380.2]/Border[0 0 0]/Dest[546 0 R/XYZ 0 602 0]>>endobj
+34 0 obj<</Subtype/Link/Rect[126.0 354.0 244.5 367.0]/Border[0 0 0]/Dest[546 0 R/XYZ 0 491 0]>>endobj
+35 0 obj<</Subtype/Link/Rect[72.0 327.6 216.8 340.6]/Border[0 0 0]/Dest[548 0 R/XYZ 0 734 0]>>endobj
+36 0 obj<</Subtype/Link/Rect[72.0 301.2 202.8 314.2]/Border[0 0 0]/Dest[552 0 R/XYZ 0 734 0]>>endobj
+37 0 obj<</Subtype/Link/Rect[108.0 288.0 213.7 301.0]/Border[0 0 0]/Dest[552 0 R/XYZ 0 696 0]>>endobj
+38 0 obj<</Subtype/Link/Rect[108.0 274.8 209.1 287.8]/Border[0 0 0]/Dest[552 0 R/XYZ 0 568 0]>>endobj
+39 0 obj<</Subtype/Link/Rect[108.0 261.6 224.7 274.6]/Border[0 0 0]/Dest[554 0 R/XYZ 0 705 0]>>endobj
+40 0 obj<</Subtype/Link/Rect[126.0 248.4 223.5 261.4]/Border[0 0 0]/Dest[554 0 R/XYZ 0 630 0]>>endobj
+41 0 obj<</Subtype/Link/Rect[126.0 235.2 222.2 248.2]/Border[0 0 0]/Dest[554 0 R/XYZ 0 571 0]>>endobj
+42 0 obj<</Subtype/Link/Rect[126.0 222.0 245.8 235.0]/Border[0 0 0]/Dest[554 0 R/XYZ 0 513 0]>>endobj
+43 0 obj<</Subtype/Link/Rect[126.0 208.8 222.2 221.8]/Border[0 0 0]/Dest[554 0 R/XYZ 0 455 0]>>endobj
+44 0 obj<</Subtype/Link/Rect[126.0 195.6 219.8 208.6]/Border[0 0 0]/Dest[554 0 R/XYZ 0 383 0]>>endobj
+45 0 obj<</Subtype/Link/Rect[126.0 182.4 228.4 195.4]/Border[0 0 0]/Dest[554 0 R/XYZ 0 325 0]>>endobj
+46 0 obj<</Subtype/Link/Rect[126.0 169.2 225.9 182.2]/Border[0 0 0]/Dest[554 0 R/XYZ 0 266 0]>>endobj
+47 0 obj<</Subtype/Link/Rect[126.0 156.0 244.5 169.0]/Border[0 0 0]/Dest[554 0 R/XYZ 0 208 0]>>endobj
+48 0 obj<</Subtype/Link/Rect[126.0 142.8 242.1 155.8]/Border[0 0 0]/Dest[554 0 R/XYZ 0 149 0]>>endobj
+49 0 obj<</Subtype/Link/Rect[126.0 129.6 256.2 142.6]/Border[0 0 0]/Dest[556 0 R/XYZ 0 734 0]>>endobj
+50 0 obj<</Subtype/Link/Rect[126.0 116.4 253.7 129.4]/Border[0 0 0]/Dest[556 0 R/XYZ 0 675 0]>>endobj
+51 0 obj<</Subtype/Link/Rect[126.0 103.2 235.1 116.2]/Border[0 0 0]/Dest[556 0 R/XYZ 0 617 0]>>endobj
+52 0 obj<</Subtype/Link/Rect[126.0 90.0 232.6 103.0]/Border[0 0 0]/Dest[556 0 R/XYZ 0 558 0]>>endobj
+53 0 obj<</Subtype/Link/Rect[126.0 76.8 257.4 89.8]/Border[0 0 0]/Dest[556 0 R/XYZ 0 500 0]>>endobj
+54 0 obj<</Subtype/Link/Rect[126.0 63.6 254.9 76.6]/Border[0 0 0]/Dest[556 0 R/XYZ 0 428 0]>>endobj
+55 0 obj[13 0 R
+14 0 R
+15 0 R
+16 0 R
+17 0 R
+18 0 R
+19 0 R
+20 0 R
+21 0 R
+22 0 R
+23 0 R
+24 0 R
+25 0 R
+26 0 R
+27 0 R
+28 0 R
+29 0 R
+30 0 R
+31 0 R
+32 0 R
+33 0 R
+34 0 R
+35 0 R
+36 0 R
+37 0 R
+38 0 R
+39 0 R
+40 0 R
+41 0 R
+42 0 R
+43 0 R
+44 0 R
+45 0 R
+46 0 R
+47 0 R
+48 0 R
+49 0 R
+50 0 R
+51 0 R
+52 0 R
+53 0 R
+54 0 R]endobj
+56 0 obj<</Subtype/Link/Rect[72.0 684.0 202.8 697.0]/Border[0 0 0]/Dest[552 0 R/XYZ 0 734 0]>>endobj
+57 0 obj<</Subtype/Link/Rect[108.0 670.8 244.9 683.8]/Border[0 0 0]/Dest[556 0 R/XYZ 0 370 0]>>endobj
+58 0 obj<</Subtype/Link/Rect[126.0 657.6 202.4 670.6]/Border[0 0 0]/Dest[556 0 R/XYZ 0 220 0]>>endobj
+59 0 obj<</Subtype/Link/Rect[126.0 644.4 210.0 657.4]/Border[0 0 0]/Dest[558 0 R/XYZ 0 441 0]>>endobj
+60 0 obj<</Subtype/Link/Rect[108.0 631.2 217.7 644.2]/Border[0 0 0]/Dest[560 0 R/XYZ 0 734 0]>>endobj
+61 0 obj<</Subtype/Link/Rect[72.0 604.8 205.8 617.8]/Border[0 0 0]/Dest[562 0 R/XYZ 0 734 0]>>endobj
+62 0 obj<</Subtype/Link/Rect[108.0 591.6 201.5 604.6]/Border[0 0 0]/Dest[562 0 R/XYZ 0 696 0]>>endobj
+63 0 obj<</Subtype/Link/Rect[126.0 578.4 260.4 591.4]/Border[0 0 0]/Dest[562 0 R/XYZ 0 423 0]>>endobj
+64 0 obj<</Subtype/Link/Rect[126.0 565.2 289.5 578.2]/Border[0 0 0]/Dest[562 0 R/XYZ 0 259 0]>>endobj
+65 0 obj<</Subtype/Link/Rect[126.0 552.0 266.6 565.0]/Border[0 0 0]/Dest[564 0 R/XYZ 0 652 0]>>endobj
+66 0 obj<</Subtype/Link/Rect[108.0 538.8 157.8 551.8]/Border[0 0 0]/Dest[564 0 R/XYZ 0 240 0]>>endobj
+67 0 obj<</Subtype/Link/Rect[126.0 525.6 223.2 538.6]/Border[0 0 0]/Dest[566 0 R/XYZ 0 665 0]>>endobj
+68 0 obj<</Subtype/Link/Rect[72.0 499.2 246.5 512.2]/Border[0 0 0]/Dest[568 0 R/XYZ 0 734 0]>>endobj
+69 0 obj<</Subtype/Link/Rect[108.0 486.0 181.6 499.0]/Border[0 0 0]/Dest[568 0 R/XYZ 0 696 0]>>endobj
+70 0 obj<</Subtype/Link/Rect[108.0 472.8 176.1 485.8]/Border[0 0 0]/Dest[568 0 R/XYZ 0 595 0]>>endobj
+71 0 obj<</Subtype/Link/Rect[108.0 459.6 195.4 472.6]/Border[0 0 0]/Dest[568 0 R/XYZ 0 216 0]>>endobj
+72 0 obj<</Subtype/Link/Rect[108.0 446.4 173.7 459.4]/Border[0 0 0]/Dest[570 0 R/XYZ 0 692 0]>>endobj
+73 0 obj<</Subtype/Link/Rect[108.0 433.2 163.9 446.2]/Border[0 0 0]/Dest[570 0 R/XYZ 0 458 0]>>endobj
+74 0 obj<</Subtype/Link/Rect[108.0 420.0 183.8 433.0]/Border[0 0 0]/Dest[572 0 R/XYZ 0 734 0]>>endobj
+75 0 obj<</Subtype/Link/Rect[108.0 406.8 194.8 419.8]/Border[0 0 0]/Dest[572 0 R/XYZ 0 566 0]>>endobj
+76 0 obj<</Subtype/Link/Rect[108.0 393.6 186.2 406.6]/Border[0 0 0]/Dest[572 0 R/XYZ 0 438 0]>>endobj
+77 0 obj<</Subtype/Link/Rect[108.0 380.4 219.2 393.4]/Border[0 0 0]/Dest[572 0 R/XYZ 0 178 0]>>endobj
+78 0 obj<</Subtype/Link/Rect[72.0 354.0 253.5 367.0]/Border[0 0 0]/Dest[576 0 R/XYZ 0 734 0]>>endobj
+79 0 obj<</Subtype/Link/Rect[72.0 327.6 212.9 340.6]/Border[0 0 0]/Dest[580 0 R/XYZ 0 734 0]>>endobj
+80 0 obj<</Subtype/Link/Rect[108.0 314.4 181.6 327.4]/Border[0 0 0]/Dest[580 0 R/XYZ 0 696 0]>>endobj
+81 0 obj<</Subtype/Link/Rect[126.0 301.2 188.3 314.2]/Border[0 0 0]/Dest[582 0 R/XYZ 0 626 0]>>endobj
+82 0 obj<</Subtype/Link/Rect[126.0 288.0 185.3 301.0]/Border[0 0 0]/Dest[582 0 R/XYZ 0 516 0]>>endobj
+83 0 obj<</Subtype/Link/Rect[108.0 274.8 218.9 287.8]/Border[0 0 0]/Dest[582 0 R/XYZ 0 394 0]>>endobj
+84 0 obj<</Subtype/Link/Rect[126.0 261.6 179.2 274.6]/Border[0 0 0]/Dest[582 0 R/XYZ 0 360 0]>>endobj
+85 0 obj<</Subtype/Link/Rect[126.0 248.4 214.6 261.4]/Border[0 0 0]/Dest[584 0 R/XYZ 0 718 0]>>endobj
+86 0 obj<</Subtype/Link/Rect[126.0 235.2 198.1 248.2]/Border[0 0 0]/Dest[584 0 R/XYZ 0 235 0]>>endobj
+87 0 obj<</Subtype/Link/Rect[108.0 222.0 283.7 235.0]/Border[0 0 0]/Dest[604 0 R/XYZ 0 428 0]>>endobj
+88 0 obj<</Subtype/Link/Rect[126.0 208.8 216.8 221.8]/Border[0 0 0]/Dest[604 0 R/XYZ 0 366 0]>>endobj
+89 0 obj<</Subtype/Link/Rect[126.0 195.6 185.3 208.6]/Border[0 0 0]/Dest[606 0 R/XYZ 0 567 0]>>endobj
+90 0 obj<</Subtype/Link/Rect[126.0 182.4 171.2 195.4]/Border[0 0 0]/Dest[614 0 R/XYZ 0 531 0]>>endobj
+91 0 obj<</Subtype/Link/Rect[126.0 169.2 249.5 182.2]/Border[0 0 0]/Dest[614 0 R/XYZ 0 407 0]>>endobj
+92 0 obj<</Subtype/Link/Rect[126.0 156.0 286.4 169.0]/Border[0 0 0]/Dest[616 0 R/XYZ 0 548 0]>>endobj
+93 0 obj<</Subtype/Link/Rect[126.0 142.8 231.7 155.8]/Border[0 0 0]/Dest[616 0 R/XYZ 0 140 0]>>endobj
+94 0 obj<</Subtype/Link/Rect[126.0 129.6 256.5 142.6]/Border[0 0 0]/Dest[618 0 R/XYZ 0 492 0]>>endobj
+95 0 obj<</Subtype/Link/Rect[126.0 116.4 303.5 129.4]/Border[0 0 0]/Dest[618 0 R/XYZ 0 145 0]>>endobj
+96 0 obj<</Subtype/Link/Rect[126.0 103.2 231.1 116.2]/Border[0 0 0]/Dest[620 0 R/XYZ 0 586 0]>>endobj
+97 0 obj<</Subtype/Link/Rect[126.0 90.0 207.6 103.0]/Border[0 0 0]/Dest[620 0 R/XYZ 0 301 0]>>endobj
+98 0 obj<</Subtype/Link/Rect[126.0 76.8 243.3 89.8]/Border[0 0 0]/Dest[622 0 R/XYZ 0 734 0]>>endobj
+99 0 obj<</Subtype/Link/Rect[126.0 63.6 250.0 76.6]/Border[0 0 0]/Dest[622 0 R/XYZ 0 249 0]>>endobj
+100 0 obj[56 0 R
+57 0 R
+58 0 R
+59 0 R
+60 0 R
+61 0 R
+62 0 R
+63 0 R
+64 0 R
+65 0 R
+66 0 R
+67 0 R
+68 0 R
+69 0 R
+70 0 R
+71 0 R
+72 0 R
+73 0 R
+74 0 R
+75 0 R
+76 0 R
+77 0 R
+78 0 R
+79 0 R
+80 0 R
+81 0 R
+82 0 R
+83 0 R
+84 0 R
+85 0 R
+86 0 R
+87 0 R
+88 0 R
+89 0 R
+90 0 R
+91 0 R
+92 0 R
+93 0 R
+94 0 R
+95 0 R
+96 0 R
+97 0 R
+98 0 R
+99 0 R]endobj
+101 0 obj<</Subtype/Link/Rect[72.0 684.0 212.9 697.0]/Border[0 0 0]/Dest[580 0 R/XYZ 0 734 0]>>endobj
+102 0 obj<</Subtype/Link/Rect[108.0 670.8 301.4 683.8]/Border[0 0 0]/Dest[624 0 R/XYZ 0 413 0]>>endobj
+103 0 obj<</Subtype/Link/Rect[126.0 657.6 259.8 670.6]/Border[0 0 0]/Dest[626 0 R/XYZ 0 665 0]>>endobj
+104 0 obj<</Subtype/Link/Rect[126.0 644.4 241.5 657.4]/Border[0 0 0]/Dest[626 0 R/XYZ 0 273 0]>>endobj
+105 0 obj<</Subtype/Link/Rect[126.0 631.2 267.5 644.2]/Border[0 0 0]/Dest[628 0 R/XYZ 0 531 0]>>endobj
+106 0 obj<</Subtype/Link/Rect[126.0 618.0 232.3 631.0]/Border[0 0 0]/Dest[628 0 R/XYZ 0 165 0]>>endobj
+107 0 obj<</Subtype/Link/Rect[126.0 604.8 234.2 617.8]/Border[0 0 0]/Dest[630 0 R/XYZ 0 353 0]>>endobj
+108 0 obj<</Subtype/Link/Rect[108.0 591.6 269.6 604.6]/Border[0 0 0]/Dest[632 0 R/XYZ 0 734 0]>>endobj
+109 0 obj<</Subtype/Link/Rect[126.0 578.4 220.7 591.4]/Border[0 0 0]/Dest[632 0 R/XYZ 0 658 0]>>endobj
+110 0 obj<</Subtype/Link/Rect[126.0 565.2 208.8 578.2]/Border[0 0 0]/Dest[634 0 R/XYZ 0 734 0]>>endobj
+111 0 obj<</Subtype/Link/Rect[108.0 552.0 267.5 565.0]/Border[0 0 0]/Dest[636 0 R/XYZ 0 705 0]>>endobj
+112 0 obj<</Subtype/Link/Rect[126.0 538.8 226.2 551.8]/Border[0 0 0]/Dest[636 0 R/XYZ 0 577 0]>>endobj
+113 0 obj<</Subtype/Link/Rect[126.0 525.6 240.6 538.6]/Border[0 0 0]/Dest[638 0 R/XYZ 0 734 0]>>endobj
+114 0 obj<</Subtype/Link/Rect[108.0 512.4 346.9 525.4]/Border[0 0 0]/Dest[638 0 R/XYZ 0 433 0]>>endobj
+115 0 obj<</Subtype/Link/Rect[126.0 499.2 203.0 512.2]/Border[0 0 0]/Dest[638 0 R/XYZ 0 400 0]>>endobj
+116 0 obj<</Subtype/Link/Rect[126.0 486.0 190.8 499.0]/Border[0 0 0]/Dest[640 0 R/XYZ 0 734 0]>>endobj
+117 0 obj<</Subtype/Link/Rect[126.0 472.8 201.2 485.8]/Border[0 0 0]/Dest[640 0 R/XYZ 0 385 0]>>endobj
+118 0 obj<</Subtype/Link/Rect[108.0 459.6 193.9 472.6]/Border[0 0 0]/Dest[640 0 R/XYZ 0 128 0]>>endobj
+119 0 obj<</Subtype/Link/Rect[126.0 446.4 235.8 459.4]/Border[0 0 0]/Dest[642 0 R/XYZ 0 633 0]>>endobj
+120 0 obj<</Subtype/Link/Rect[126.0 433.2 238.8 446.2]/Border[0 0 0]/Dest[644 0 R/XYZ 0 665 0]>>endobj
+121 0 obj<</Subtype/Link/Rect[72.0 406.8 250.1 419.8]/Border[0 0 0]/Dest[648 0 R/XYZ 0 734 0]>>endobj
+122 0 obj<</Subtype/Link/Rect[108.0 393.6 170.0 406.6]/Border[0 0 0]/Dest[648 0 R/XYZ 0 696 0]>>endobj
+123 0 obj<</Subtype/Link/Rect[108.0 380.4 307.2 393.4]/Border[0 0 0]/Dest[648 0 R/XYZ 0 621 0]>>endobj
+124 0 obj<</Subtype/Link/Rect[108.0 367.2 216.6 380.2]/Border[0 0 0]/Dest[648 0 R/XYZ 0 361 0]>>endobj
+125 0 obj<</Subtype/Link/Rect[108.0 354.0 358.2 367.0]/Border[0 0 0]/Dest[652 0 R/XYZ 0 692 0]>>endobj
+126 0 obj<</Subtype/Link/Rect[108.0 340.8 309.3 353.8]/Border[0 0 0]/Dest[652 0 R/XYZ 0 630 0]>>endobj
+127 0 obj<</Subtype/Link/Rect[72.0 314.4 240.4 327.4]/Border[0 0 0]/Dest[658 0 R/XYZ 0 734 0]>>endobj
+128 0 obj<</Subtype/Link/Rect[108.0 301.2 200.3 314.2]/Border[0 0 0]/Dest[658 0 R/XYZ 0 696 0]>>endobj
+129 0 obj<</Subtype/Link/Rect[72.0 274.8 263.3 287.8]/Border[0 0 0]/Dest[660 0 R/XYZ 0 734 0]>>endobj
+130 0 obj<</Subtype/Link/Rect[108.0 261.6 248.5 274.6]/Border[0 0 0]/Dest[660 0 R/XYZ 0 696 0]>>endobj
+131 0 obj<</Subtype/Link/Rect[108.0 248.4 236.0 261.4]/Border[0 0 0]/Dest[662 0 R/XYZ 0 639 0]>>endobj
+132 0 obj<</Subtype/Link/Rect[108.0 235.2 291.6 248.2]/Border[0 0 0]/Dest[662 0 R/XYZ 0 498 0]>>endobj
+133 0 obj<</Subtype/Link/Rect[108.0 222.0 162.7 235.0]/Border[0 0 0]/Dest[662 0 R/XYZ 0 198 0]>>endobj
+134 0 obj<</Subtype/Link/Rect[126.0 208.8 210.9 221.8]/Border[0 0 0]/Dest[662 0 R/XYZ 0 165 0]>>endobj
+135 0 obj<</Subtype/Link/Rect[126.0 195.6 224.7 208.6]/Border[0 0 0]/Dest[664 0 R/XYZ 0 734 0]>>endobj
+136 0 obj<</Subtype/Link/Rect[126.0 182.4 224.1 195.4]/Border[0 0 0]/Dest[664 0 R/XYZ 0 596 0]>>endobj
+137 0 obj<</Subtype/Link/Rect[108.0 169.2 197.8 182.2]/Border[0 0 0]/Dest[664 0 R/XYZ 0 485 0]>>endobj
+138 0 obj<</Subtype/Link/Rect[126.0 156.0 287.3 169.0]/Border[0 0 0]/Dest[664 0 R/XYZ 0 451 0]>>endobj
+139 0 obj<</Subtype/Link/Rect[126.0 142.8 196.9 155.8]/Border[0 0 0]/Dest[664 0 R/XYZ 0 366 0]>>endobj
+140 0 obj<</Subtype/Link/Rect[108.0 129.6 230.8 142.6]/Border[0 0 0]/Dest[664 0 R/XYZ 0 229 0]>>endobj
+141 0 obj<</Subtype/Link/Rect[108.0 116.4 165.8 129.4]/Border[0 0 0]/Dest[666 0 R/XYZ 0 489 0]>>endobj
+142 0 obj<</Subtype/Link/Rect[72.0 90.0 313.7 103.0]/Border[0 0 0]/Dest[668 0 R/XYZ 0 734 0]>>endobj
+143 0 obj<</Subtype/Link/Rect[108.0 76.8 187.1 89.8]/Border[0 0 0]/Dest[668 0 R/XYZ 0 696 0]>>endobj
+144 0 obj<</Subtype/Link/Rect[108.0 63.6 216.2 76.6]/Border[0 0 0]/Dest[668 0 R/XYZ 0 568 0]>>endobj
+145 0 obj[101 0 R
+102 0 R
+103 0 R
+104 0 R
+105 0 R
+106 0 R
+107 0 R
+108 0 R
+109 0 R
+110 0 R
+111 0 R
+112 0 R
+113 0 R
+114 0 R
+115 0 R
+116 0 R
+117 0 R
+118 0 R
+119 0 R
+120 0 R
+121 0 R
+122 0 R
+123 0 R
+124 0 R
+125 0 R
+126 0 R
+127 0 R
+128 0 R
+129 0 R
+130 0 R
+131 0 R
+132 0 R
+133 0 R
+134 0 R
+135 0 R
+136 0 R
+137 0 R
+138 0 R
+139 0 R
+140 0 R
+141 0 R
+142 0 R
+143 0 R
+144 0 R]endobj
+146 0 obj<</Subtype/Link/Rect[72.0 684.0 313.7 697.0]/Border[0 0 0]/Dest[668 0 R/XYZ 0 734 0]>>endobj
+147 0 obj<</Subtype/Link/Rect[108.0 670.8 220.7 683.8]/Border[0 0 0]/Dest[670 0 R/XYZ 0 718 0]>>endobj
+148 0 obj[146 0 R
+147 0 R]endobj
+149 0 obj<</S/URI/URI(http://devel.samba.org/)>>endobj
+150 0 obj<</Subtype/Link/Rect[139.5 617.8 243.7 630.8]/Border[0 0 0]/A 149 0 R>>endobj
+151 0 obj<</S/URI/URI(mailto:jelmer@samba.org)>>endobj
+152 0 obj<</Subtype/Link/Rect[347.9 617.8 434.4 630.8]/Border[0 0 0]/A 151 0 R>>endobj
+153 0 obj<</S/URI/URI(http://www.fsf.org/licenses/gpl.txt)>>endobj
+154 0 obj<</Subtype/Link/Rect[72.0 565.0 223.3 578.0]/Border[0 0 0]/A 153 0 R>>endobj
+155 0 obj<</Subtype/Link/Rect[80.2 525.4 351.6 538.4]/Border[0 0 0]/Dest[532 0 R/XYZ 0 734 0]>>endobj
+156 0 obj<</Subtype/Link/Rect[124.5 512.2 171.2 525.2]/Border[0 0 0]/Dest[532 0 R/XYZ 0 672 0]>>endobj
+157 0 obj<</Subtype/Link/Rect[124.5 499.0 230.8 512.0]/Border[0 0 0]/Dest[532 0 R/XYZ 0 201 0]>>endobj
+158 0 obj<</Subtype/Link/Rect[124.5 485.8 196.0 498.8]/Border[0 0 0]/Dest[534 0 R/XYZ 0 705 0]>>endobj
+159 0 obj<</Subtype/Link/Rect[80.2 472.6 170.7 485.6]/Border[0 0 0]/Dest[536 0 R/XYZ 0 734 0]>>endobj
+160 0 obj<</Subtype/Link/Rect[124.5 459.4 182.2 472.4]/Border[0 0 0]/Dest[536 0 R/XYZ 0 696 0]>>endobj
+161 0 obj<</Subtype/Link/Rect[124.5 446.2 245.8 459.2]/Border[0 0 0]/Dest[536 0 R/XYZ 0 529 0]>>endobj
+162 0 obj<</Subtype/Link/Rect[124.5 433.0 199.1 446.0]/Border[0 0 0]/Dest[536 0 R/XYZ 0 335 0]>>endobj
+163 0 obj<</Subtype/Link/Rect[124.5 419.8 200.3 432.8]/Border[0 0 0]/Dest[538 0 R/XYZ 0 734 0]>>endobj
+164 0 obj<</Subtype/Link/Rect[124.5 406.6 185.6 419.6]/Border[0 0 0]/Dest[538 0 R/XYZ 0 434 0]>>endobj
+165 0 obj<</Subtype/Link/Rect[80.2 393.4 203.1 406.4]/Border[0 0 0]/Dest[540 0 R/XYZ 0 734 0]>>endobj
+166 0 obj<</Subtype/Link/Rect[124.5 380.2 212.2 393.2]/Border[0 0 0]/Dest[540 0 R/XYZ 0 696 0]>>endobj
+167 0 obj<</Subtype/Link/Rect[124.5 367.0 223.2 380.0]/Border[0 0 0]/Dest[542 0 R/XYZ 0 734 0]>>endobj
+168 0 obj<</Subtype/Link/Rect[124.5 353.8 245.8 366.8]/Border[0 0 0]/Dest[544 0 R/XYZ 0 734 0]>>endobj
+169 0 obj<</Subtype/Link/Rect[124.5 340.6 242.1 353.6]/Border[0 0 0]/Dest[544 0 R/XYZ 0 514 0]>>endobj
+170 0 obj<</Subtype/Link/Rect[124.5 327.4 193.6 340.4]/Border[0 0 0]/Dest[546 0 R/XYZ 0 734 0]>>endobj
+171 0 obj<</Subtype/Link/Rect[168.8 314.2 211.2 327.2]/Border[0 0 0]/Dest[546 0 R/XYZ 0 700 0]>>endobj
+172 0 obj<</Subtype/Link/Rect[168.8 301.0 210.6 314.0]/Border[0 0 0]/Dest[546 0 R/XYZ 0 602 0]>>endobj
+173 0 obj<</Subtype/Link/Rect[168.8 287.8 261.9 300.8]/Border[0 0 0]/Dest[546 0 R/XYZ 0 491 0]>>endobj
+174 0 obj<</Subtype/Link/Rect[80.2 274.6 170.7 287.6]/Border[0 0 0]/Dest[548 0 R/XYZ 0 734 0]>>endobj
+175 0 obj<</Subtype/Link/Rect[80.2 261.4 155.4 274.4]/Border[0 0 0]/Dest[552 0 R/XYZ 0 734 0]>>endobj
+176 0 obj<</Subtype/Link/Rect[124.5 248.2 216.8 261.2]/Border[0 0 0]/Dest[552 0 R/XYZ 0 696 0]>>endobj
+177 0 obj<</Subtype/Link/Rect[124.5 235.0 207.3 248.0]/Border[0 0 0]/Dest[552 0 R/XYZ 0 568 0]>>endobj
+178 0 obj<</Subtype/Link/Rect[124.5 221.8 225.9 234.8]/Border[0 0 0]/Dest[554 0 R/XYZ 0 705 0]>>endobj
+179 0 obj<</Subtype/Link/Rect[168.8 208.6 237.8 221.6]/Border[0 0 0]/Dest[554 0 R/XYZ 0 630 0]>>endobj
+180 0 obj<</Subtype/Link/Rect[168.8 195.4 237.2 208.4]/Border[0 0 0]/Dest[554 0 R/XYZ 0 571 0]>>endobj
+181 0 obj<</Subtype/Link/Rect[168.8 182.2 259.5 195.2]/Border[0 0 0]/Dest[554 0 R/XYZ 0 513 0]>>endobj
+182 0 obj<</Subtype/Link/Rect[168.8 169.0 236.0 182.0]/Border[0 0 0]/Dest[554 0 R/XYZ 0 455 0]>>endobj
+183 0 obj<</Subtype/Link/Rect[168.8 155.8 234.1 168.8]/Border[0 0 0]/Dest[554 0 R/XYZ 0 383 0]>>endobj
+184 0 obj<</Subtype/Link/Rect[168.8 142.6 241.5 155.6]/Border[0 0 0]/Dest[554 0 R/XYZ 0 325 0]>>endobj
+185 0 obj<</Subtype/Link/Rect[168.8 129.4 239.6 142.4]/Border[0 0 0]/Dest[554 0 R/XYZ 0 266 0]>>endobj
+186 0 obj<</Subtype/Link/Rect[168.8 116.2 257.7 129.2]/Border[0 0 0]/Dest[554 0 R/XYZ 0 208 0]>>endobj
+187 0 obj<</Subtype/Link/Rect[168.8 103.0 255.8 116.0]/Border[0 0 0]/Dest[554 0 R/XYZ 0 149 0]>>endobj
+188 0 obj<</Subtype/Link/Rect[174.2 89.8 268.7 102.8]/Border[0 0 0]/Dest[556 0 R/XYZ 0 734 0]>>endobj
+189 0 obj<</Subtype/Link/Rect[174.2 76.6 266.8 89.6]/Border[0 0 0]/Dest[556 0 R/XYZ 0 675 0]>>endobj
+190 0 obj<</Subtype/Link/Rect[174.2 63.4 248.2 76.4]/Border[0 0 0]/Dest[556 0 R/XYZ 0 617 0]>>endobj
+191 0 obj[150 0 R
+152 0 R
+154 0 R
+155 0 R
+156 0 R
+157 0 R
+158 0 R
+159 0 R
+160 0 R
+161 0 R
+162 0 R
+163 0 R
+164 0 R
+165 0 R
+166 0 R
+167 0 R
+168 0 R
+169 0 R
+170 0 R
+171 0 R
+172 0 R
+173 0 R
+174 0 R
+175 0 R
+176 0 R
+177 0 R
+178 0 R
+179 0 R
+180 0 R
+181 0 R
+182 0 R
+183 0 R
+184 0 R
+185 0 R
+186 0 R
+187 0 R
+188 0 R
+189 0 R
+190 0 R]endobj
+192 0 obj<</Subtype/Link/Rect[174.2 721.0 246.4 734.0]/Border[0 0 0]/Dest[556 0 R/XYZ 0 558 0]>>endobj
+193 0 obj<</Subtype/Link/Rect[174.2 707.8 269.9 720.8]/Border[0 0 0]/Dest[556 0 R/XYZ 0 500 0]>>endobj
+194 0 obj<</Subtype/Link/Rect[174.2 694.6 268.0 707.6]/Border[0 0 0]/Dest[556 0 R/XYZ 0 428 0]>>endobj
+195 0 obj<</Subtype/Link/Rect[124.5 681.4 243.0 694.4]/Border[0 0 0]/Dest[556 0 R/XYZ 0 370 0]>>endobj
+196 0 obj<</Subtype/Link/Rect[168.8 668.2 222.8 681.2]/Border[0 0 0]/Dest[556 0 R/XYZ 0 220 0]>>endobj
+197 0 obj<</Subtype/Link/Rect[168.8 655.0 228.0 668.0]/Border[0 0 0]/Dest[558 0 R/XYZ 0 441 0]>>endobj
+198 0 obj<</Subtype/Link/Rect[124.5 641.8 220.7 654.8]/Border[0 0 0]/Dest[560 0 R/XYZ 0 734 0]>>endobj
+199 0 obj<</Subtype/Link/Rect[80.2 628.6 158.5 641.6]/Border[0 0 0]/Dest[562 0 R/XYZ 0 734 0]>>endobj
+200 0 obj<</Subtype/Link/Rect[124.5 615.4 199.7 628.4]/Border[0 0 0]/Dest[562 0 R/XYZ 0 696 0]>>endobj
+201 0 obj<</Subtype/Link/Rect[168.8 602.2 277.8 615.2]/Border[0 0 0]/Dest[562 0 R/XYZ 0 423 0]>>endobj
+202 0 obj<</Subtype/Link/Rect[168.8 589.0 307.5 602.0]/Border[0 0 0]/Dest[562 0 R/XYZ 0 259 0]>>endobj
+203 0 obj<</Subtype/Link/Rect[168.8 575.8 284.6 588.8]/Border[0 0 0]/Dest[564 0 R/XYZ 0 652 0]>>endobj
+204 0 obj<</Subtype/Link/Rect[124.5 562.6 156.6 575.6]/Border[0 0 0]/Dest[564 0 R/XYZ 0 240 0]>>endobj
+205 0 obj<</Subtype/Link/Rect[168.8 549.4 241.2 562.4]/Border[0 0 0]/Dest[566 0 R/XYZ 0 665 0]>>endobj
+206 0 obj<</Subtype/Link/Rect[80.2 536.2 196.0 549.2]/Border[0 0 0]/Dest[568 0 R/XYZ 0 734 0]>>endobj
+207 0 obj<</Subtype/Link/Rect[124.5 523.0 182.2 536.0]/Border[0 0 0]/Dest[568 0 R/XYZ 0 696 0]>>endobj
+208 0 obj<</Subtype/Link/Rect[124.5 509.8 176.7 522.8]/Border[0 0 0]/Dest[568 0 R/XYZ 0 595 0]>>endobj
+209 0 obj<</Subtype/Link/Rect[124.5 496.6 196.0 509.6]/Border[0 0 0]/Dest[568 0 R/XYZ 0 216 0]>>endobj
+210 0 obj<</Subtype/Link/Rect[124.5 483.4 174.9 496.4]/Border[0 0 0]/Dest[570 0 R/XYZ 0 692 0]>>endobj
+211 0 obj<</Subtype/Link/Rect[124.5 470.2 162.7 483.2]/Border[0 0 0]/Dest[570 0 R/XYZ 0 458 0]>>endobj
+212 0 obj<</Subtype/Link/Rect[124.5 457.0 182.5 470.0]/Border[0 0 0]/Dest[572 0 R/XYZ 0 734 0]>>endobj
+213 0 obj<</Subtype/Link/Rect[124.5 443.8 196.0 456.8]/Border[0 0 0]/Dest[572 0 R/XYZ 0 566 0]>>endobj
+214 0 obj<</Subtype/Link/Rect[124.5 430.6 187.4 443.6]/Border[0 0 0]/Dest[572 0 R/XYZ 0 438 0]>>endobj
+215 0 obj<</Subtype/Link/Rect[124.5 417.4 218.6 430.4]/Border[0 0 0]/Dest[572 0 R/XYZ 0 178 0]>>endobj
+216 0 obj<</Subtype/Link/Rect[80.2 404.2 204.9 417.2]/Border[0 0 0]/Dest[576 0 R/XYZ 0 734 0]>>endobj
+217 0 obj<</Subtype/Link/Rect[80.2 391.0 164.8 404.0]/Border[0 0 0]/Dest[580 0 R/XYZ 0 734 0]>>endobj
+218 0 obj<</Subtype/Link/Rect[124.5 377.8 182.2 390.8]/Border[0 0 0]/Dest[580 0 R/XYZ 0 696 0]>>endobj
+219 0 obj<</Subtype/Link/Rect[168.8 364.6 206.3 377.6]/Border[0 0 0]/Dest[582 0 R/XYZ 0 626 0]>>endobj
+220 0 obj<</Subtype/Link/Rect[168.8 351.4 203.9 364.4]/Border[0 0 0]/Dest[582 0 R/XYZ 0 516 0]>>endobj
+221 0 obj<</Subtype/Link/Rect[124.5 338.2 219.5 351.2]/Border[0 0 0]/Dest[582 0 R/XYZ 0 394 0]>>endobj
+222 0 obj<</Subtype/Link/Rect[168.8 325.0 196.6 338.0]/Border[0 0 0]/Dest[582 0 R/XYZ 0 360 0]>>endobj
+223 0 obj<</Subtype/Link/Rect[168.8 311.8 233.2 324.8]/Border[0 0 0]/Dest[584 0 R/XYZ 0 718 0]>>endobj
+224 0 obj<</Subtype/Link/Rect[168.8 298.6 216.7 311.6]/Border[0 0 0]/Dest[584 0 R/XYZ 0 235 0]>>endobj
+225 0 obj<</Subtype/Link/Rect[124.5 285.4 283.7 298.4]/Border[0 0 0]/Dest[604 0 R/XYZ 0 428 0]>>endobj
+226 0 obj<</Subtype/Link/Rect[168.8 272.2 234.1 285.2]/Border[0 0 0]/Dest[604 0 R/XYZ 0 366 0]>>endobj
+227 0 obj<</Subtype/Link/Rect[168.8 259.0 204.5 272.0]/Border[0 0 0]/Dest[606 0 R/XYZ 0 567 0]>>endobj
+228 0 obj<</Subtype/Link/Rect[168.8 245.8 189.2 258.8]/Border[0 0 0]/Dest[614 0 R/XYZ 0 531 0]>>endobj
+229 0 obj<</Subtype/Link/Rect[168.8 232.6 264.4 245.6]/Border[0 0 0]/Dest[614 0 R/XYZ 0 407 0]>>endobj
+230 0 obj<</Subtype/Link/Rect[168.8 219.4 302.0 232.4]/Border[0 0 0]/Dest[616 0 R/XYZ 0 548 0]>>endobj
+231 0 obj<</Subtype/Link/Rect[168.8 206.2 247.3 219.2]/Border[0 0 0]/Dest[616 0 R/XYZ 0 140 0]>>endobj
+232 0 obj<</Subtype/Link/Rect[168.8 193.0 271.4 206.0]/Border[0 0 0]/Dest[618 0 R/XYZ 0 492 0]>>endobj
+233 0 obj<</Subtype/Link/Rect[168.8 179.8 319.7 192.8]/Border[0 0 0]/Dest[618 0 R/XYZ 0 145 0]>>endobj
+234 0 obj<</Subtype/Link/Rect[168.8 166.6 246.7 179.6]/Border[0 0 0]/Dest[620 0 R/XYZ 0 586 0]>>endobj
+235 0 obj<</Subtype/Link/Rect[174.2 153.4 223.1 166.4]/Border[0 0 0]/Dest[620 0 R/XYZ 0 301 0]>>endobj
+236 0 obj<</Subtype/Link/Rect[174.2 140.2 256.4 153.2]/Border[0 0 0]/Dest[622 0 R/XYZ 0 734 0]>>endobj
+237 0 obj<</Subtype/Link/Rect[174.2 127.0 263.8 140.0]/Border[0 0 0]/Dest[622 0 R/XYZ 0 249 0]>>endobj
+238 0 obj<</Subtype/Link/Rect[124.5 113.8 300.8 126.8]/Border[0 0 0]/Dest[624 0 R/XYZ 0 413 0]>>endobj
+239 0 obj<</Subtype/Link/Rect[168.8 100.6 275.4 113.6]/Border[0 0 0]/Dest[626 0 R/XYZ 0 665 0]>>endobj
+240 0 obj<</Subtype/Link/Rect[168.8 87.4 256.4 100.4]/Border[0 0 0]/Dest[626 0 R/XYZ 0 273 0]>>endobj
+241 0 obj<</Subtype/Link/Rect[168.8 74.2 283.6 87.2]/Border[0 0 0]/Dest[628 0 R/XYZ 0 531 0]>>endobj
+242 0 obj<</Subtype/Link/Rect[168.8 61.0 244.8 74.0]/Border[0 0 0]/Dest[628 0 R/XYZ 0 165 0]>>endobj
+243 0 obj[192 0 R
+193 0 R
+194 0 R
+195 0 R
+196 0 R
+197 0 R
+198 0 R
+199 0 R
+200 0 R
+201 0 R
+202 0 R
+203 0 R
+204 0 R
+205 0 R
+206 0 R
+207 0 R
+208 0 R
+209 0 R
+210 0 R
+211 0 R
+212 0 R
+213 0 R
+214 0 R
+215 0 R
+216 0 R
+217 0 R
+218 0 R
+219 0 R
+220 0 R
+221 0 R
+222 0 R
+223 0 R
+224 0 R
+225 0 R
+226 0 R
+227 0 R
+228 0 R
+229 0 R
+230 0 R
+231 0 R
+232 0 R
+233 0 R
+234 0 R
+235 0 R
+236 0 R
+237 0 R
+238 0 R
+239 0 R
+240 0 R
+241 0 R
+242 0 R]endobj
+244 0 obj<</Subtype/Link/Rect[168.8 721.0 245.5 734.0]/Border[0 0 0]/Dest[630 0 R/XYZ 0 353 0]>>endobj
+245 0 obj<</Subtype/Link/Rect[124.5 707.8 261.7 720.8]/Border[0 0 0]/Dest[632 0 R/XYZ 0 734 0]>>endobj
+246 0 obj<</Subtype/Link/Rect[168.8 694.6 239.3 707.6]/Border[0 0 0]/Dest[632 0 R/XYZ 0 658 0]>>endobj
+247 0 obj<</Subtype/Link/Rect[168.8 681.4 223.8 694.4]/Border[0 0 0]/Dest[634 0 R/XYZ 0 734 0]>>endobj
+248 0 obj<</Subtype/Link/Rect[124.5 668.2 264.4 681.2]/Border[0 0 0]/Dest[636 0 R/XYZ 0 705 0]>>endobj
+249 0 obj<</Subtype/Link/Rect[168.8 655.0 243.6 668.0]/Border[0 0 0]/Dest[636 0 R/XYZ 0 577 0]>>endobj
+250 0 obj<</Subtype/Link/Rect[168.8 641.8 257.3 654.8]/Border[0 0 0]/Dest[638 0 R/XYZ 0 734 0]>>endobj
+251 0 obj<</Subtype/Link/Rect[124.5 628.6 345.7 641.6]/Border[0 0 0]/Dest[638 0 R/XYZ 0 433 0]>>endobj
+252 0 obj<</Subtype/Link/Rect[168.8 615.4 220.4 628.4]/Border[0 0 0]/Dest[638 0 R/XYZ 0 400 0]>>endobj
+253 0 obj<</Subtype/Link/Rect[168.8 602.2 210.0 615.2]/Border[0 0 0]/Dest[640 0 R/XYZ 0 734 0]>>endobj
+254 0 obj<</Subtype/Link/Rect[168.8 589.0 217.9 602.0]/Border[0 0 0]/Dest[640 0 R/XYZ 0 385 0]>>endobj
+255 0 obj<</Subtype/Link/Rect[124.5 575.8 193.2 588.8]/Border[0 0 0]/Dest[640 0 R/XYZ 0 128 0]>>endobj
+256 0 obj<</Subtype/Link/Rect[168.8 562.6 251.9 575.6]/Border[0 0 0]/Dest[642 0 R/XYZ 0 633 0]>>endobj
+257 0 obj<</Subtype/Link/Rect[168.8 549.4 254.4 562.4]/Border[0 0 0]/Dest[644 0 R/XYZ 0 665 0]>>endobj
+258 0 obj<</Subtype/Link/Rect[85.8 536.2 200.3 549.2]/Border[0 0 0]/Dest[648 0 R/XYZ 0 734 0]>>endobj
+259 0 obj<</Subtype/Link/Rect[130.0 523.0 170.0 536.0]/Border[0 0 0]/Dest[648 0 R/XYZ 0 696 0]>>endobj
+260 0 obj<</Subtype/Link/Rect[130.0 509.8 308.4 522.8]/Border[0 0 0]/Dest[648 0 R/XYZ 0 621 0]>>endobj
+261 0 obj<</Subtype/Link/Rect[130.0 496.6 217.0 509.6]/Border[0 0 0]/Dest[648 0 R/XYZ 0 361 0]>>endobj
+262 0 obj<</Subtype/Link/Rect[130.0 483.4 360.7 496.4]/Border[0 0 0]/Dest[652 0 R/XYZ 0 692 0]>>endobj
+263 0 obj<</Subtype/Link/Rect[130.0 470.2 306.3 483.2]/Border[0 0 0]/Dest[652 0 R/XYZ 0 630 0]>>endobj
+264 0 obj<</Subtype/Link/Rect[85.8 457.0 189.3 470.0]/Border[0 0 0]/Dest[658 0 R/XYZ 0 734 0]>>endobj
+265 0 obj<</Subtype/Link/Rect[130.0 443.8 199.0 456.8]/Border[0 0 0]/Dest[658 0 R/XYZ 0 696 0]>>endobj
+266 0 obj<</Subtype/Link/Rect[85.8 430.6 211.0 443.6]/Border[0 0 0]/Dest[660 0 R/XYZ 0 734 0]>>endobj
+267 0 obj<</Subtype/Link/Rect[130.0 417.4 245.6 430.4]/Border[0 0 0]/Dest[660 0 R/XYZ 0 696 0]>>endobj
+268 0 obj<</Subtype/Link/Rect[130.0 404.2 234.2 417.2]/Border[0 0 0]/Dest[662 0 R/XYZ 0 639 0]>>endobj
+269 0 obj<</Subtype/Link/Rect[130.0 391.0 289.8 404.0]/Border[0 0 0]/Dest[662 0 R/XYZ 0 498 0]>>endobj
+270 0 obj<</Subtype/Link/Rect[130.0 377.8 162.7 390.8]/Border[0 0 0]/Dest[662 0 R/XYZ 0 198 0]>>endobj
+271 0 obj<</Subtype/Link/Rect[174.2 364.6 228.3 377.6]/Border[0 0 0]/Dest[662 0 R/XYZ 0 165 0]>>endobj
+272 0 obj<</Subtype/Link/Rect[174.2 351.4 240.8 364.4]/Border[0 0 0]/Dest[664 0 R/XYZ 0 734 0]>>endobj
+273 0 obj<</Subtype/Link/Rect[174.2 338.2 239.0 351.2]/Border[0 0 0]/Dest[664 0 R/XYZ 0 596 0]>>endobj
+274 0 obj<</Subtype/Link/Rect[130.0 325.0 194.8 338.0]/Border[0 0 0]/Dest[664 0 R/XYZ 0 485 0]>>endobj
+275 0 obj<</Subtype/Link/Rect[174.2 311.8 305.9 324.8]/Border[0 0 0]/Dest[664 0 R/XYZ 0 451 0]>>endobj
+276 0 obj<</Subtype/Link/Rect[174.2 298.6 215.5 311.6]/Border[0 0 0]/Dest[664 0 R/XYZ 0 366 0]>>endobj
+277 0 obj<</Subtype/Link/Rect[130.0 285.4 229.6 298.4]/Border[0 0 0]/Dest[664 0 R/XYZ 0 229 0]>>endobj
+278 0 obj<</Subtype/Link/Rect[130.0 272.2 165.1 285.2]/Border[0 0 0]/Dest[666 0 R/XYZ 0 489 0]>>endobj
+279 0 obj<</Subtype/Link/Rect[85.8 259.0 259.0 272.0]/Border[0 0 0]/Dest[668 0 R/XYZ 0 734 0]>>endobj
+280 0 obj<</Subtype/Link/Rect[130.0 245.8 187.8 258.8]/Border[0 0 0]/Dest[668 0 R/XYZ 0 696 0]>>endobj
+281 0 obj<</Subtype/Link/Rect[130.0 232.6 215.6 245.6]/Border[0 0 0]/Dest[668 0 R/XYZ 0 568 0]>>endobj
+282 0 obj<</Subtype/Link/Rect[130.0 219.4 218.9 221.4]/Border[0 0 0]/Dest[670 0 R/XYZ 0 718 0]>>endobj
+283 0 obj[244 0 R
+245 0 R
+246 0 R
+247 0 R
+248 0 R
+249 0 R
+250 0 R
+251 0 R
+252 0 R
+253 0 R
+254 0 R
+255 0 R
+256 0 R
+257 0 R
+258 0 R
+259 0 R
+260 0 R
+261 0 R
+262 0 R
+263 0 R
+264 0 R
+265 0 R
+266 0 R
+267 0 R
+268 0 R
+269 0 R
+270 0 R
+271 0 R
+272 0 R
+273 0 R
+274 0 R
+275 0 R
+276 0 R
+277 0 R
+278 0 R
+279 0 R
+280 0 R
+281 0 R
+282 0 R]endobj
+284 0 obj<</S/URI/URI(http://lxr.linux.no/source/Documentation/CodingStyle)>>endobj
+285 0 obj<</Subtype/Link/Rect[72.0 499.0 310.3 512.0]/Border[0 0 0]/A 284 0 R>>endobj
+286 0 obj<</S/URI/URI(http://www.fsf.org/prep/standards_toc.html)>>endobj
+287 0 obj<</Subtype/Link/Rect[72.0 472.6 263.0 485.6]/Border[0 0 0]/A 286 0 R>>endobj
+288 0 obj[285 0 R
+287 0 R]endobj
+289 0 obj<</S/URI/URI(http://mailhost.cb1.com/~lkcl/cifsntdomain.txt)>>endobj
+290 0 obj<</Subtype/Link/Rect[226.0 637.0 433.6 650.0]/Border[0 0 0]/A 289 0 R>>endobj
+291 0 obj<</S/URI/URI(http://ntbugtraq.rc.on.ca/SCRIPTS/WA.EXE?A2=ind9708;L=ntbugtraq;O=A;P=2935)>>endobj
+292 0 obj<</Subtype/Link/Rect[72.0 386.2 451.3 399.2]/Border[0 0 0]/A 291 0 R>>endobj
+293 0 obj<</S/URI/URI(http://mailhost.cb1.com/~lkcl/crypt.html)>>endobj
+294 0 obj<</Subtype/Link/Rect[72.0 359.8 250.6 372.8]/Border[0 0 0]/A 293 0 R>>endobj
+295 0 obj<</S/URI/URI(mailto:linus@incolumitas.se)>>endobj
+296 0 obj<</Subtype/Link/Rect[244.7 333.4 317.4 346.4]/Border[0 0 0]/A 295 0 R>>endobj
+297 0 obj<</S/URI/URI(http://samba.org/cgi-bin/mfs/01/digest/1997/97aug/0391.html)>>endobj
+298 0 obj<</Subtype/Link/Rect[72.0 307.0 346.5 320.0]/Border[0 0 0]/A 297 0 R>>endobj
+299 0 obj<</S/URI/URI(http://mailhost.cb1.com/~lkcl/crypt.txt)>>endobj
+300 0 obj<</Subtype/Link/Rect[72.0 280.6 242.0 293.6]/Border[0 0 0]/A 299 0 R>>endobj
+301 0 obj[290 0 R
+292 0 R
+294 0 R
+296 0 R
+298 0 R
+300 0 R]endobj
+302 0 obj<</Dests 303 0 R>>endobj
+303 0 obj<</Kids[304 0 R]>>endobj
+304 0 obj<</Limits[(aen1008)(wins)]/Names[(aen1008)305 0 R(aen1019)306 0 R(aen103)307 0 R(aen1040)308 0 R(aen1053)309 0 R(aen1100)310 0 R(aen1127)311 0 R(aen1138)312 0 R(aen1177)313 0 R(aen1208)314 0 R(aen128)315 0 R(aen1365)316 0 R(aen1388)317 0 R(aen1399)318 0 R(aen1445)319 0 R(aen151)320 0 R(aen1571)321 0 R(aen1574)322 0 R(aen1588)323 0 R(aen159)324 0 R(aen1649)325 0 R(aen1688)326 0 R(aen1693)327 0 R(aen1704)328 0 R(aen1744)329 0 R(aen1755)330 0 R(aen179)331 0 R(aen1799)332 0 R(aen181)333 0 R(aen1819)334 0 R(aen184)335 0 R(aen1842)336 0 R(aen1854)337 0 R(aen188)338 0 R(aen1898)339 0 R(aen1939)340 0 R(aen1943)341 0 R(aen1962)342 0 R(aen1973)343 0 R(aen1977)344 0 R(aen1988)345 0 R(aen2001)346 0 R(aen2003)347 0 R(aen2006)348 0 R(aen2025)349 0 R(aen2027)350 0 R(aen2030)351 0 R(aen2054)352 0 R(aen2056)353 0 R(aen2063)354 0 R(aen2071)355 0 R(aen2075)356 0 R(aen2102)357 0 R(aen2130)358 0 R(aen2134)359 0 R(aen2165)360 0 R(aen2193)361 0 R(aen2232)362 0 R(aen2240)363 0 R(aen2259)364 0 R(aen2267)365 0 R(aen2275)366 0 R(aen2294)367 0 R(aen2306)368 0 R(aen2316)369 0 R(aen2327)370 0 R(aen2335)371 0 R(aen2339)372 0 R(aen2346)373 0 R(aen2359)374 0 R(aen2363)375 0 R(aen2370)376 0 R(aen2382)377 0 R(aen2386)378 0 R(aen2390)379 0 R(aen24)380 0 R(aen2425)381 0 R(aen2460)382 0 R(aen2468)383 0 R(aen2519)384 0 R(aen2550)385 0 R(aen2562)386 0 R(aen2568)387 0 R(aen2603)388 0 R(aen2623)389 0 R(aen2627)390 0 R(aen2638)391 0 R(aen2654)392 0 R(aen2656)393 0 R(aen2699)394 0 R(aen2709)395 0 R(aen2716)396 0 R(aen2724)397 0 R(aen2726)398 0 R(aen2761)399 0 R(aen2812)400 0 R(aen2815)401 0 R(aen2829)402 0 R(aen284)403 0 R(aen2847)404 0 R(aen288)405 0 R(aen2896)406 0 R(aen2899)407 0 R(aen2925)408 0 R(aen2959)409 0 R(aen2962)410 0 R(aen3033)411 0 R(aen3054)412 0 R(aen3071)413 0 R(aen3075)414 0 R(aen3086)415 0 R(aen3088)416 0 R(aen3091)417 0 R(aen3095)418 0 R(aen3098)419 0 R(aen3100)420 0 R(aen3103)421 0 R(aen3107)422 0 R(aen3121)423 0 R(aen3147)424 0 R(aen3151)425 0 R(aen3162)426 0 R(aen317)427 0 R(aen320)428 0 R(aen323)429 0 R(aen326)430 0 R(aen329)431 0 R(aen332)432 0 R(aen335)433 0 R(aen338)434 0 R(aen341)435 0 R(aen344)436 0 R(aen347)437 0 R(aen35)438 0 R(aen350)439 0 R(aen353)440 0 R(aen356)441 0 R(aen359)442 0 R(aen362)443 0 R(aen365)444 0 R(aen371)445 0 R(aen39)446 0 R(aen4)447 0 R(aen406)448 0 R(aen420)449 0 R(aen451)450 0 R(aen472)451 0 R(aen484)452 0 R(aen495)453 0 R(aen515)454 0 R(aen530)455 0 R(aen54)456 0 R(aen540)457 0 R(aen544)458 0 R(aen552)459 0 R(aen557)460 0 R(aen563)461 0 R(aen571)462 0 R(aen575)463 0 R(aen579)464 0 R(aen584)465 0 R(aen65)466 0 R(aen652)467 0 R(aen688)468 0 R(aen695)469 0 R(aen70)470 0 R(aen702)471 0 R(aen704)472 0 R(aen717)473 0 R(aen719)474 0 R(aen739)475 0 R(aen775)476 0 R(aen777)477 0 R(aen780)478 0 R(aen783)479 0 R(aen786)480 0 R(aen789)481 0 R(aen8)482 0 R(aen814)483 0 R(aen817)484 0 R(aen832)485 0 R(aen843)486 0 R(aen850)487 0 R(aen86)488 0 R(aen861)489 0 R(aen884)490 0 R(aen911)491 0 R(aen918)492 0 R(aen92)493 0 R(aen941)494 0 R(aen960)495 0 R(aen987)496 0 R(architecture)497 0 R(codingsuggestions)498 0 R(debug)499 0 R(internals)500 0 R(netbios)501 0 R(ntdomain)502 0 R(parsing)503 0 R(printing)504 0 R(pwencrypt)505 0 R(sam)506 0 R(samba-developers-guide)507 0 R(samba-developers-guide.html)508 0 R(smbpasswdfileformat)509 0 R(tracing)510 0 R(unix-smb)511 0 R(wins)512 0 R]>>endobj
+305 0 obj<</D[592 0 R/XYZ 0 734 0]>>endobj
+306 0 obj<</D[592 0 R/XYZ 0 639 0]>>endobj
+307 0 obj<</D[540 0 R/XYZ 0 696 0]>>endobj
+308 0 obj<</D[592 0 R/XYZ 0 439 0]>>endobj
+309 0 obj<</D[592 0 R/XYZ 0 292 0]>>endobj
+310 0 obj<</D[594 0 R/XYZ 0 626 0]>>endobj
+311 0 obj<</D[594 0 R/XYZ 0 345 0]>>endobj
+312 0 obj<</D[594 0 R/XYZ 0 251 0]>>endobj
+313 0 obj<</D[596 0 R/XYZ 0 639 0]>>endobj
+314 0 obj<</D[596 0 R/XYZ 0 413 0]>>endobj
+315 0 obj<</D[542 0 R/XYZ 0 734 0]>>endobj
+316 0 obj<</D[600 0 R/XYZ 0 679 0]>>endobj
+317 0 obj<</D[600 0 R/XYZ 0 438 0]>>endobj
+318 0 obj<</D[600 0 R/XYZ 0 344 0]>>endobj
+319 0 obj<</D[602 0 R/XYZ 0 639 0]>>endobj
+320 0 obj<</D[544 0 R/XYZ 0 734 0]>>endobj
+321 0 obj<</D[604 0 R/XYZ 0 428 0]>>endobj
+322 0 obj<</D[604 0 R/XYZ 0 366 0]>>endobj
+323 0 obj<</D[606 0 R/XYZ 0 567 0]>>endobj
+324 0 obj<</D[544 0 R/XYZ 0 514 0]>>endobj
+325 0 obj<</D[610 0 R/XYZ 0 734 0]>>endobj
+326 0 obj<</D[610 0 R/XYZ 0 467 0]>>endobj
+327 0 obj<</D[610 0 R/XYZ 0 378 0]>>endobj
+328 0 obj<</D[610 0 R/XYZ 0 283 0]>>endobj
+329 0 obj<</D[612 0 R/XYZ 0 639 0]>>endobj
+330 0 obj<</D[612 0 R/XYZ 0 545 0]>>endobj
+331 0 obj<</D[546 0 R/XYZ 0 734 0]>>endobj
+332 0 obj<</D[612 0 R/XYZ 0 213 0]>>endobj
+333 0 obj<</D[546 0 R/XYZ 0 700 0]>>endobj
+334 0 obj<</D[614 0 R/XYZ 0 705 0]>>endobj
+335 0 obj<</D[546 0 R/XYZ 0 602 0]>>endobj
+336 0 obj<</D[614 0 R/XYZ 0 531 0]>>endobj
+337 0 obj<</D[614 0 R/XYZ 0 407 0]>>endobj
+338 0 obj<</D[546 0 R/XYZ 0 491 0]>>endobj
+339 0 obj<</D[616 0 R/XYZ 0 548 0]>>endobj
+340 0 obj<</D[616 0 R/XYZ 0 140 0]>>endobj
+341 0 obj<</D[618 0 R/XYZ 0 734 0]>>endobj
+342 0 obj<</D[618 0 R/XYZ 0 586 0]>>endobj
+343 0 obj<</D[618 0 R/XYZ 0 492 0]>>endobj
+344 0 obj<</D[618 0 R/XYZ 0 433 0]>>endobj
+345 0 obj<</D[618 0 R/XYZ 0 339 0]>>endobj
+346 0 obj<</D[618 0 R/XYZ 0 145 0]>>endobj
+347 0 obj<</D[618 0 R/XYZ 0 115 0]>>endobj
+348 0 obj<</D[620 0 R/XYZ 0 734 0]>>endobj
+349 0 obj<</D[620 0 R/XYZ 0 586 0]>>endobj
+350 0 obj<</D[620 0 R/XYZ 0 556 0]>>endobj
+351 0 obj<</D[620 0 R/XYZ 0 501 0]>>endobj
+352 0 obj<</D[620 0 R/XYZ 0 301 0]>>endobj
+353 0 obj<</D[620 0 R/XYZ 0 271 0]>>endobj
+354 0 obj<</D[620 0 R/XYZ 0 203 0]>>endobj
+355 0 obj<</D[622 0 R/XYZ 0 734 0]>>endobj
+356 0 obj<</D[622 0 R/XYZ 0 675 0]>>endobj
+357 0 obj<</D[622 0 R/XYZ 0 475 0]>>endobj
+358 0 obj<</D[622 0 R/XYZ 0 249 0]>>endobj
+359 0 obj<</D[622 0 R/XYZ 0 190 0]>>endobj
+360 0 obj<</D[624 0 R/XYZ 0 639 0]>>endobj
+361 0 obj<</D[624 0 R/XYZ 0 413 0]>>endobj
+362 0 obj<</D[626 0 R/XYZ 0 665 0]>>endobj
+363 0 obj<</D[626 0 R/XYZ 0 515 0]>>endobj
+364 0 obj<</D[626 0 R/XYZ 0 367 0]>>endobj
+365 0 obj<</D[626 0 R/XYZ 0 273 0]>>endobj
+366 0 obj<</D[626 0 R/XYZ 0 135 0]>>endobj
+367 0 obj<</D[628 0 R/XYZ 0 652 0]>>endobj
+368 0 obj<</D[628 0 R/XYZ 0 531 0]>>endobj
+369 0 obj<</D[628 0 R/XYZ 0 354 0]>>endobj
+370 0 obj<</D[628 0 R/XYZ 0 260 0]>>endobj
+371 0 obj<</D[628 0 R/XYZ 0 165 0]>>endobj
+372 0 obj<</D[630 0 R/XYZ 0 734 0]>>endobj
+373 0 obj<</D[630 0 R/XYZ 0 665 0]>>endobj
+374 0 obj<</D[630 0 R/XYZ 0 353 0]>>endobj
+375 0 obj<</D[630 0 R/XYZ 0 281 0]>>endobj
+376 0 obj<</D[630 0 R/XYZ 0 213 0]>>endobj
+377 0 obj<</D[632 0 R/XYZ 0 734 0]>>endobj
+378 0 obj<</D[632 0 R/XYZ 0 658 0]>>endobj
+379 0 obj<</D[632 0 R/XYZ 0 600 0]>>endobj
+380 0 obj<</D[532 0 R/XYZ 0 672 0]>>endobj
+381 0 obj<</D[632 0 R/XYZ 0 347 0]>>endobj
+382 0 obj<</D[634 0 R/XYZ 0 734 0]>>endobj
+383 0 obj<</D[634 0 R/XYZ 0 622 0]>>endobj
+384 0 obj<</D[634 0 R/XYZ 0 264 0]>>endobj
+385 0 obj<</D[636 0 R/XYZ 0 705 0]>>endobj
+386 0 obj<</D[636 0 R/XYZ 0 577 0]>>endobj
+387 0 obj<</D[636 0 R/XYZ 0 492 0]>>endobj
+388 0 obj<</D[636 0 R/XYZ 0 239 0]>>endobj
+389 0 obj<</D[638 0 R/XYZ 0 734 0]>>endobj
+390 0 obj<</D[638 0 R/XYZ 0 675 0]>>endobj
+391 0 obj<</D[638 0 R/XYZ 0 581 0]>>endobj
+392 0 obj<</D[638 0 R/XYZ 0 433 0]>>endobj
+393 0 obj<</D[638 0 R/XYZ 0 400 0]>>endobj
+394 0 obj<</D[640 0 R/XYZ 0 734 0]>>endobj
+395 0 obj<</D[640 0 R/XYZ 0 385 0]>>endobj
+396 0 obj<</D[640 0 R/XYZ 0 128 0]>>endobj
+397 0 obj<</D[642 0 R/XYZ 0 633 0]>>endobj
+398 0 obj<</D[642 0 R/XYZ 0 603 0]>>endobj
+399 0 obj<</D[642 0 R/XYZ 0 351 0]>>endobj
+400 0 obj<</D[644 0 R/XYZ 0 665 0]>>endobj
+401 0 obj<</D[644 0 R/XYZ 0 594 0]>>endobj
+402 0 obj<</D[644 0 R/XYZ 0 407 0]>>endobj
+403 0 obj<</D[552 0 R/XYZ 0 696 0]>>endobj
+404 0 obj<</D[644 0 R/XYZ 0 141 0]>>endobj
+405 0 obj<</D[552 0 R/XYZ 0 568 0]>>endobj
+406 0 obj<</D[648 0 R/XYZ 0 696 0]>>endobj
+407 0 obj<</D[648 0 R/XYZ 0 621 0]>>endobj
+408 0 obj<</D[648 0 R/XYZ 0 361 0]>>endobj
+409 0 obj<</D[652 0 R/XYZ 0 692 0]>>endobj
+410 0 obj<</D[652 0 R/XYZ 0 630 0]>>endobj
+411 0 obj<</D[658 0 R/XYZ 0 696 0]>>endobj
+412 0 obj<</D[660 0 R/XYZ 0 696 0]>>endobj
+413 0 obj<</D[662 0 R/XYZ 0 639 0]>>endobj
+414 0 obj<</D[662 0 R/XYZ 0 498 0]>>endobj
+415 0 obj<</D[662 0 R/XYZ 0 198 0]>>endobj
+416 0 obj<</D[662 0 R/XYZ 0 165 0]>>endobj
+417 0 obj<</D[664 0 R/XYZ 0 734 0]>>endobj
+418 0 obj<</D[664 0 R/XYZ 0 596 0]>>endobj
+419 0 obj<</D[664 0 R/XYZ 0 485 0]>>endobj
+420 0 obj<</D[664 0 R/XYZ 0 451 0]>>endobj
+421 0 obj<</D[664 0 R/XYZ 0 366 0]>>endobj
+422 0 obj<</D[664 0 R/XYZ 0 229 0]>>endobj
+423 0 obj<</D[666 0 R/XYZ 0 489 0]>>endobj
+424 0 obj<</D[668 0 R/XYZ 0 696 0]>>endobj
+425 0 obj<</D[668 0 R/XYZ 0 568 0]>>endobj
+426 0 obj<</D[670 0 R/XYZ 0 718 0]>>endobj
+427 0 obj<</D[554 0 R/XYZ 0 705 0]>>endobj
+428 0 obj<</D[554 0 R/XYZ 0 630 0]>>endobj
+429 0 obj<</D[554 0 R/XYZ 0 571 0]>>endobj
+430 0 obj<</D[554 0 R/XYZ 0 513 0]>>endobj
+431 0 obj<</D[554 0 R/XYZ 0 455 0]>>endobj
+432 0 obj<</D[554 0 R/XYZ 0 383 0]>>endobj
+433 0 obj<</D[554 0 R/XYZ 0 325 0]>>endobj
+434 0 obj<</D[554 0 R/XYZ 0 266 0]>>endobj
+435 0 obj<</D[554 0 R/XYZ 0 208 0]>>endobj
+436 0 obj<</D[554 0 R/XYZ 0 149 0]>>endobj
+437 0 obj<</D[556 0 R/XYZ 0 734 0]>>endobj
+438 0 obj<</D[532 0 R/XYZ 0 201 0]>>endobj
+439 0 obj<</D[556 0 R/XYZ 0 675 0]>>endobj
+440 0 obj<</D[556 0 R/XYZ 0 617 0]>>endobj
+441 0 obj<</D[556 0 R/XYZ 0 558 0]>>endobj
+442 0 obj<</D[556 0 R/XYZ 0 500 0]>>endobj
+443 0 obj<</D[556 0 R/XYZ 0 428 0]>>endobj
+444 0 obj<</D[556 0 R/XYZ 0 370 0]>>endobj
+445 0 obj<</D[556 0 R/XYZ 0 220 0]>>endobj
+446 0 obj<</D[534 0 R/XYZ 0 705 0]>>endobj
+447 0 obj<</D[524 0 R/XYZ 0 696 0]>>endobj
+448 0 obj<</D[558 0 R/XYZ 0 441 0]>>endobj
+449 0 obj<</D[560 0 R/XYZ 0 734 0]>>endobj
+450 0 obj<</D[562 0 R/XYZ 0 696 0]>>endobj
+451 0 obj<</D[562 0 R/XYZ 0 423 0]>>endobj
+452 0 obj<</D[562 0 R/XYZ 0 259 0]>>endobj
+453 0 obj<</D[564 0 R/XYZ 0 652 0]>>endobj
+454 0 obj<</D[564 0 R/XYZ 0 240 0]>>endobj
+455 0 obj<</D[566 0 R/XYZ 0 665 0]>>endobj
+456 0 obj<</D[536 0 R/XYZ 0 696 0]>>endobj
+457 0 obj<</D[568 0 R/XYZ 0 696 0]>>endobj
+458 0 obj<</D[568 0 R/XYZ 0 595 0]>>endobj
+459 0 obj<</D[568 0 R/XYZ 0 216 0]>>endobj
+460 0 obj<</D[570 0 R/XYZ 0 692 0]>>endobj
+461 0 obj<</D[570 0 R/XYZ 0 458 0]>>endobj
+462 0 obj<</D[572 0 R/XYZ 0 734 0]>>endobj
+463 0 obj<</D[572 0 R/XYZ 0 566 0]>>endobj
+464 0 obj<</D[572 0 R/XYZ 0 438 0]>>endobj
+465 0 obj<</D[572 0 R/XYZ 0 178 0]>>endobj
+466 0 obj<</D[536 0 R/XYZ 0 529 0]>>endobj
+467 0 obj<</D[580 0 R/XYZ 0 696 0]>>endobj
+468 0 obj<</D[582 0 R/XYZ 0 626 0]>>endobj
+469 0 obj<</D[582 0 R/XYZ 0 516 0]>>endobj
+470 0 obj<</D[536 0 R/XYZ 0 335 0]>>endobj
+471 0 obj<</D[582 0 R/XYZ 0 394 0]>>endobj
+472 0 obj<</D[582 0 R/XYZ 0 360 0]>>endobj
+473 0 obj<</D[584 0 R/XYZ 0 718 0]>>endobj
+474 0 obj<</D[584 0 R/XYZ 0 688 0]>>endobj
+475 0 obj<</D[584 0 R/XYZ 0 515 0]>>endobj
+476 0 obj<</D[584 0 R/XYZ 0 235 0]>>endobj
+477 0 obj<</D[584 0 R/XYZ 0 205 0]>>endobj
+478 0 obj<</D[584 0 R/XYZ 0 151 0]>>endobj
+479 0 obj<</D[586 0 R/XYZ 0 734 0]>>endobj
+480 0 obj<</D[586 0 R/XYZ 0 665 0]>>endobj
+481 0 obj<</D[586 0 R/XYZ 0 611 0]>>endobj
+482 0 obj<</D[526 0 R/XYZ 0 734 0]>>endobj
+483 0 obj<</D[586 0 R/XYZ 0 411 0]>>endobj
+484 0 obj<</D[586 0 R/XYZ 0 356 0]>>endobj
+485 0 obj<</D[586 0 R/XYZ 0 235 0]>>endobj
+486 0 obj<</D[586 0 R/XYZ 0 141 0]>>endobj
+487 0 obj<</D[588 0 R/XYZ 0 734 0]>>endobj
+488 0 obj<</D[538 0 R/XYZ 0 734 0]>>endobj
+489 0 obj<</D[588 0 R/XYZ 0 639 0]>>endobj
+490 0 obj<</D[588 0 R/XYZ 0 465 0]>>endobj
+491 0 obj<</D[588 0 R/XYZ 0 265 0]>>endobj
+492 0 obj<</D[588 0 R/XYZ 0 197 0]>>endobj
+493 0 obj<</D[538 0 R/XYZ 0 434 0]>>endobj
+494 0 obj<</D[590 0 R/XYZ 0 665 0]>>endobj
+495 0 obj<</D[590 0 R/XYZ 0 518 0]>>endobj
+496 0 obj<</D[590 0 R/XYZ 0 279 0]>>endobj
+497 0 obj<</D[536 0 R/XYZ 0 734 0]>>endobj
+498 0 obj<</D[548 0 R/XYZ 0 734 0]>>endobj
+499 0 obj<</D[540 0 R/XYZ 0 734 0]>>endobj
+500 0 obj<</D[552 0 R/XYZ 0 734 0]>>endobj
+501 0 obj<</D[532 0 R/XYZ 0 734 0]>>endobj
+502 0 obj<</D[580 0 R/XYZ 0 734 0]>>endobj
+503 0 obj<</D[562 0 R/XYZ 0 734 0]>>endobj
+504 0 obj<</D[648 0 R/XYZ 0 734 0]>>endobj
+505 0 obj<</D[668 0 R/XYZ 0 734 0]>>endobj
+506 0 obj<</D[660 0 R/XYZ 0 734 0]>>endobj
+507 0 obj<</D[524 0 R/XYZ 0 734 0]>>endobj
+508 0 obj<</D[524 0 R/XYZ 0 734 0]>>endobj
+509 0 obj<</D[670 0 R/XYZ 0 718 0]>>endobj
+510 0 obj<</D[576 0 R/XYZ 0 734 0]>>endobj
+511 0 obj<</D[568 0 R/XYZ 0 734 0]>>endobj
+512 0 obj<</D[658 0 R/XYZ 0 734 0]>>endobj
+513 0 obj<</Type/Pages/Count 80/Kids[514 0 R
+516 0 R
+518 0 R
+520 0 R
+522 0 R
+524 0 R
+526 0 R
+528 0 R
+530 0 R
+532 0 R
+534 0 R
+536 0 R
+538 0 R
+540 0 R
+542 0 R
+544 0 R
+546 0 R
+548 0 R
+550 0 R
+552 0 R
+554 0 R
+556 0 R
+558 0 R
+560 0 R
+562 0 R
+564 0 R
+566 0 R
+568 0 R
+570 0 R
+572 0 R
+574 0 R
+576 0 R
+578 0 R
+580 0 R
+582 0 R
+584 0 R
+586 0 R
+588 0 R
+590 0 R
+592 0 R
+594 0 R
+596 0 R
+598 0 R
+600 0 R
+602 0 R
+604 0 R
+606 0 R
+608 0 R
+610 0 R
+612 0 R
+614 0 R
+616 0 R
+618 0 R
+620 0 R
+622 0 R
+624 0 R
+626 0 R
+628 0 R
+630 0 R
+632 0 R
+634 0 R
+636 0 R
+638 0 R
+640 0 R
+642 0 R
+644 0 R
+646 0 R
+648 0 R
+650 0 R
+652 0 R
+654 0 R
+656 0 R
+658 0 R
+660 0 R
+662 0 R
+664 0 R
+666 0 R
+668 0 R
+670 0 R
+672 0 R
+]>>endobj
+514 0 obj<</Type/Page/Parent 513 0 R/Contents 515 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+515 0 obj<</Filter/FlateDecode/Length 93 >>stream
+x+2T0
+endobj
+516 0 obj<</Type/Page/Parent 513 0 R/Contents 517 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F5 7 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>/Annots 55 0 R>>endobj
+517 0 obj<</Filter/FlateDecode/Length 2523 >>stream
+x[moG_SRv}?%hlm,)'zCrf]%HyHYUsJng<7wMR-&y;=xLgn3p+4/ 5iF$LbmRD1TAOzM)g lh1rB-k(eXb$ynd- KI"ee@N2J`Y(@=2G.*12lA&}k
+4kHR6@s3p4% 9,LuP2P#<",X:U@ 91Kc¶–5la|••IkVN9R)i19 [3 @&,"+#`z-ZJREg4 3(S<B$-^81_Z"i1 k0Xh
+HZL
+qDFR@2p%d(,V12%v^N92rK-RV]3)='sD@
+ZLSp2e~S@ e4
+pZ^ uCne+,Y0$-:D
+zROa;$.p3+g F | "g/YyY")I^X
+cf tPq`*g &
+d4*fg tB53©ÒphwĄð,ÔA)3'M
+zaIj$9b O!
+vpLO O CRf'UR/32PAQs#)K"@=rzRg CzR,9 Ts)XP
+zTI]$F(/(Q.RQF"3E$D)R<S%Q3_XB9
+yF,R,L`!<O cD<:Eby-p,wHeRE\9_Znd\w}~XR%Z#yYFb. :#"LPjYw$aHl
+1i`(UUeibFp7G,(/SXj._3w;)hnN_a1C<mv~hRytyr?/ZZ}?26jMXm9QQK@ik0)/mQ*HPO1B}||V/0m6#5V;.?_]/UvEy>~Sr|lB(=h<;$4 PM0lj{pMo(t;gzKuaa~m/+93ZQolcj$&8)Qj 5 qróÓöF<>?(\m*MgSC!5;rUqAm`6h4}t†Ü¸|žç§X bDISG;K<((q>;ZR4&BCx?v%,.4k4] 3<uOR_Vz5e(xW^D>n`d3e q)1s]TS;uRmR^Nlho/? -B5hb)Îò’fœ «zÐUUU$
+};,12a}6 1bZ&)G5n7&Toi\=R{c T_C{6^,
+z^ dTR`^~ tcUx^Un~6O19\U5?$?(SÜÎê´¥'7`o–gÿ<ûá¿ñ'endstream
+endobj
+518 0 obj<</Type/Page/Parent 513 0 R/Contents 519 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F5 7 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>/Annots 100 0 R>>endobj
+519 0 obj<</Filter/FlateDecode/Length 3034 >>stream
+x[MsGWm=GYUlgcENn`jwL*Jn=,.k|V|uOr|W&]eE7qg3WY8WY[M
+#'!&,*|A
+&4p53nb`?¸*I!'5jZR)d a M T0p9L4lK
+$jaX i"L91wbeSQ%t4!r\PbZ3++ P.@L
+Ym<C%ePqP:h$D`Q`:
+WD`rk"*g !eP$4p3IPZ]O34`WREqR0AQ}V@ Z64h]U.FB
+a.D@"ym\+& M8)g yre RY,'sYIa%FPVMv tIh))H*aaLx:9D&¹À¹Ü#–•´vÀ›X$j1 m@`8TFVFZ0sph&.Evs5bX4.Y"-%5C<)w!s202C B)fBp-QcEP!RH`dDHyBjr
+RX9)9Qb2^q|iHA' LpGx@C<%)%qjZ"KO9M=QB]9QYix7Jyv1ESfw|/ngY%z?!HVb^\~=ú JA^dly?&8o0f=S`#u`hd1&]_<kzB[s>v>|{qs&G549fdcsq
+z ;=ZbHz[ \\#xT8<N/ ^ME.Z{QOYhNB.GNrrHu9X< /<GbOR9?Ä"†p†|šë¾ÿ¶ç»j¼œ©/L^O%P{J7X~)'Y@6jGb7x”ßG
+endobj
+520 0 obj<</Type/Page/Parent 513 0 R/Contents 521 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F5 7 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>/Annots 145 0 R>>endobj
+521 0 obj<</Filter/FlateDecode/Length 3464 >>stream
+x[rI}W>X/0H@F#I!=Y-EuKeeeD1K*2.Q'W$*/%(Qj:lf%M'+F5Sh4&I` `a/4=[ 6mFii:*1 q: i1Xr?,`j L s(i1-2M` &))M&nP:d@ZnlTE5,t6` Rh+S3v^v Lqn
+JZnZ aP 87Ie
+=(
+ Y^Ah83 Z _K8a I( `!I0YZfq\3J20QVL$!! L(JZL24((5,46hk0Xv|Ak1X",T T*i1~5,cJhe{a5jFJX^h58^/"$IeRuO>/@"B2 8I9+HS i1XWLUZ IhRe D D8ab.O(E"i,/L2]N=%0]Q.["VDZnq`1%eeXr[()0rS^yJZ 1l a;,6+<l0J5j,*=)aQzyCL|TJ
+UECN C3KTv-TFnHIq6m,MS:oU:{CewlrKEz^]}WXM=zu8s]' r zo^b~-%=scG!nVv~p)hIWI|jngBfMtcn)G#{8.Czc;;MGelP_,7.v%«i¬0%‹bÜküîýø=ëå¥Â-öèonÇHprx$F \m 2/]I*#/ I{h%| lH7Jw>=/{P6kXWmzj//fHRI-w5;snuePC;HL3}.p'}q~rt8/Gp;cl'BE&dK~O9YG1}hQa;o< 56nTF\B#vKk~!8QjCu,K*
+Y?@Pty} ;z7$^/K©”‚(nJ> "$YsnIFMG+jS3TZsf|7JeFzR#uN|>]W1o(h 8&p~filv* , Yv5cvnVxOg& T=)a3F0O375 ´|09z.u4: x߶j¿Ïß^:Ô 7\Õ¼€¨RDu|k
+!3 #`tN/N’2v(WwAP+e-%<=}SkSI .>gW 6s:yfJZH1oF4x}g\W;D`S)ia@tX Kh
+$(iI0pMwXZ "!+Cll'n%:daLxqGND.}9Bo*?qi^ h|@HT%j4kq:zCHnfjS-]vY+u7EQP\_\Q"vz9c,[9>jGjn=-`v~jtz[298s_>-/@)3
+endobj
+522 0 obj<</Type/Page/Parent 513 0 R/Contents 523 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F5 7 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>/Annots 148 0 R>>endobj
+523 0 obj<</Filter/FlateDecode/Length 385 >>stream
+xSr@s4}Qz$X0bL3"~A
+,_A@`RY(;pU
+4"X#-H1aR3Fe$Ny)4n^%8 d-<]BcLeNd4;\:6Lfc M})KR%g8k  t)S=*\L4]`QoSM:5dVOsp|TOCJ4Fm})j}VhFn- .gx<v
+Sm/'cx.9m] )NxpB<yO
+endobj
+524 0 obj<</Type/Page/Parent 513 0 R/Contents 525 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+525 0 obj<</Filter/FlateDecode/Length 155 >>stream
+x}0 E|a iH6"~\Y,#? CPu,!d+c1pdoPYpiM5;&vOW[\WEjz%`>Šñ`؊9šÒ°7~endstream
+endobj
+526 0 obj<</Type/Page/Parent 513 0 R/Contents 527 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F6 8 0 R/F7 9 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>/Annots 191 0 R>>endobj
+527 0 obj<</Filter/FlateDecode/Length 1731 >>stream
+xWRH}+mIUd]rITaTd{l++iYlQi4OI@aLdI$N4R*O|/PA Iq:ž‘ï…bÏÔ h<Á¾¤(òâ0åÀ’â¬!s„æ(EVb` qX$a\R0 &r6N\D
+RE~ bw0#l$X
+r\wlbu3P
+&6DV05`woNX7bF1Rh9 `8nu (`O"K9r"\Q?"[#t1(sqyX}H1 ]A'4( }Ac g~HAVPONsLz*p[80">?zpg0p 0p0Hb`jvrs5
+/ql)dqz9oL-7X! ,O23;S{]TmqMqAxt}3A zDg2mZCBZzEKhKU&3TQiPTZS@nQjZ.\_jq}04TiJ]+X":7FU4veuk A5:mCF}(UK_F#]zE,thAj63wC%M T.t`TI=*C »V'*JU[z?:erL-+> EVU
+zlE /o.1 W|!zTKySm2Az+ZgwW&q ulIE3fKµÊ«|w”¹úðqJDCV*zR.ZK%p6HAjtF]#WS?s#@d*PZ/[ {`'6Gmapb|H>)7kbZT?<nl$f_JywWCwXlq$'c}-j}d_XJ/,Q)G3znX(-<U`#q23_jRg4rvf-i@v02zuzC
+/
+n qIdWn{olttma_DV7G7ëñ·F:z?CrhcBc+5=P+Z3KOKr/06Z!`|PZcSy6=^'F4uSc(a+'%Vendstream
+endobj
+528 0 obj<</Type/Page/Parent 513 0 R/Contents 529 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F6 8 0 R/F8 10 0 R>>/XObject<<>>>>/Annots 243 0 R>>endobj
+529 0 obj<</Filter/FlateDecode/Length 2012 >>stream
+xuXrH}WB_T,/(BWciv(3g'0YhT3?_?~&S7kdG6 lyI)6)TXHMB/1id
+ $)f pRt:EH(
+U %CO2, 0U%d$^43 ‰Ôlœ{™bsę‘Ô/ÌP hUI 9NAD=`Tf4*$:IH
+:!+V er5. 5XDUnX6@5( q0 l* A*N ~P=N}l($N.+shPQABO8NfocLqmY#($RX="SptHC*TX8OXxKXmSp
+u"%HlAzsUyx B -U$g#yYCeD3/Rs9EFc,Au8 ) ym8fHaUC#{QHf}( HbUCnN x"Gv1OG(h5q[ "G+40X[/^hXcnd>
+DUaFw eu
+p5X !IEdc vda,#,NlX]e-cfyfe(/d>Re.E$.c$
+R#3t0te+1vA1(9E.MlRq! pP9_ -~!&4S <r|XPP8.B&=1bR39rXxQP8.L%&8#-k9=#F9v5wKM pF*.
+Zw0r@xgbgfOD,W("W7ng9B *a|*{33e[~{3/}fg>}R v}k<m nY v*1C:L=xvU]h+¤­¥⹩7U2\=o‰êXbrMh>5CU) R7M[#vh]94]{5U1i?$p``0C̆eÞz•”£35,óÌ]=\\ßÏM|ikpMzn^|}wO]G~j6GIinuT(z{Up}Yv]o\_
+piw1(nn7+L,8[v:v
+w sKD@[rZc]_dMm4 +
+tZ16GCw5sDFHDN°òU{$C6Qo(~~acuVDSXr8suqMezBD$ J3~Ha7PJoj*;=GV1gNb(:F ; r?R/#70^("u~6f~}5
+O_{)6S":=}nqsO<~]W~? WvS[CmjMS8 35:&{-2n7x7\ g6.YJO<a;c1< "endstream
+endobj
+530 0 obj<</Type/Page/Parent 513 0 R/Contents 531 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F6 8 0 R/F8 10 0 R>>/XObject<<>>>>/Annots 283 0 R>>endobj
+531 0 obj<</Filter/FlateDecode/Length 1845 >>stream
+x}XMoFWifM`$f#*%{wdM
+.ULx2c-?Q\`R dG'--k0X.-k0$:-px
+ 9ZE,fEYgVG$:TZL+Yi`65l2`#hbia,?8aP"I<[5,! {]6LXrI44o *H@zHLC&BE vHbJI8J9*6'F=0C<i1XkVcMq8@lybf`#]b)#n]H:uPE$# b 6twt$
+4Wn,HZ '5l5,rE:`qyY6/4H7eHMZPS,CwY'=FL^Qb:{+ENV=8jxHpT2R1N%lC`3`.:wU&"Zvg}+ g x)".0LpwNv@z7 Oc JKñ]+Òxx9GHU/q*njHb%5,V#J\AN=bfsם+ðPjf>yD2_R^2_gPAd\ev~#]Z4{rOVgH%8 ng_n)\<
+zxU? `2VVm>upy[dv_!C{L=[W{wCom+eVM'5jqp1rY$;C6A }>kI\]n
+u6k{pj=t>)L'dYs\!Y3K r/F$3VmS/j7lM.z#?P%N 7ucT]uWZz[uA[6GK,w yXj8Hb,{vo'. ?mo,RVZ;]LY>Gqp$P7w~LM/*J=+)ErHEYBDJ
+endobj
+532 0 obj<</Type/Page/Parent 513 0 R/Contents 533 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+533 0 obj<</Filter/FlateDecode/Length 1571 >>stream
+xWRH}+-c!O@`U,8*4'Hef== lr[4f:9(;8g}FRrt>dL&g9c1\D02QrJjNG:%o4L$}VS p)R0@5M) CYp]1M[HPNSWy^w>gGj96t6K'T[=jWZf%d{y01fv@VJ2Ia~8oP}kToC'+h:" q; q%i#IHg^yL281hKvv 6895\n+X{P!ZH#6)~Xs*Lh$r.E<kVoXuE{4!Je=t% Le
+@1|@^:O;|8P*u##
+%PCl h
+!Gy.
+5wjoN  "KtUHTZ^7*QtvsX~} 6MÔ#‘
+·µcêÑãï¢T
+0Uk4TR8/CYM[Q7xW:qe(Y]v5b{+z#WS;P{3{'
+I!jXHcXq]nw,e
+t2Ks g^Fz]w'|S=KY}83llendstream
+endobj
+534 0 obj<</Type/Page/Parent 513 0 R/Contents 535 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+535 0 obj<</Filter/FlateDecode/Length 1468 >>stream
+xV]o6}{J8x nndhŠŠ¸HFRvw.)9a(x?9\sRZLzN:$/f?U:xp9˜Q&GrAg2p{ FdR8O<8~C)NY2C4NhuZJOk"6d&L9iVe/4[RUkS3jB8D]:ZJZ<k vt+[+, - ,;4Dhz*OF/%5@#!C{ z#Q#6T!i"}BaO2%JG!dY;RRw]>Q3p8pJd`_?ji3U[ r]).Dht=)yA#cQd!RL}23(LkYN nUqWv<+b8äp®TG4  i-~vnW#]yy|FP@};DzYjpA[Ezt! &
+HpQ
+yuO%(7B$K0VS^xVk%vqOh9QC :T+,rQ*Gl/`"-T3t7 dWE}28_i;7Bc|us~ACyD%x, MU>Yp#[SQ<Pbz}A#\+bDM-{p1IbYuk=WA0P!Lmx;2qejT6 'D}v:
+#Vy:j* qd=vPFN'2r1-|-{WL09"^:G4 x7'P|.
+ 5An_M;], n-Ek WCWWgI\p=w~q/M5endstream
+endobj
+536 0 obj<</Type/Page/Parent 513 0 R/Contents 537 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+537 0 obj<</Filter/FlateDecode/Length 1660 >>stream
+xW]o8|KDu^yhC|K(TI %Ha"wwfvvRfw)s9e3Ygw9~2}q5<2D;YgM~RmQ5+%|^y};_\-9Llh\6)\5FYd~ct/c
+/AE^V6eZ5R ]Ht&%:!
+WZ {V:Di]fUknkLZ\-&n%$"nu3w6D5Rop?[mSDF/O]=?!K%"gG)VQz5 /@&;oT*(wg/k~OP#mb|^*V)wy0Y54!t=]}88%@8#8Zol7 * JXdTA\PX<=|}<Ox]3hb~-Tg!/gi|}E'|Hb4PM@!tEA2?\-x. ?:t.:cU ,@Q!YXP
+: brR>LPlNdGl"c")Mubak{Yn'4Q% |adq h|+of6S0=T
+c[v8J l (2 bu^&L:{1=  sW yh0(Z_z C+a'P;v?7J9b0%j9,IxJQk&FBBOb)ar#U! "Y1W0dd0`
+Q o~W:`$fzGMzl?aR9S5)i,<ydxTy3ow$i}S Y?' )l(endstream
+endobj
+538 0 obj<</Type/Page/Parent 513 0 R/Contents 539 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+539 0 obj<</Filter/FlateDecode/Length 1662 >>stream
+xuWnF}W °Xql/"MRXA`X#i#r]Z,D M3g n U|.oyi/f_hqK l, vsZWWuA]`S[% \'fzg#|T2MsIeh)R#u>$S#B- +nkru`lb28&JQ#m|$#xhgo.WIp@J6mOvSLbej0$Dlp[L#S#qO3G?pr})w>T{`f\BTjF Z=LaB`xmce=xI!%DK$@<T|g`Ys)Jvt
+8
+q_nKSGRzBg2S|x~t&x%+Ғ©äªGvsY})lu/$
+MIJTomCZedgY
+
+G<k6di)y\^K
+,/lQendstream
+endobj
+540 0 obj<</Type/Page/Parent 513 0 R/Contents 541 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+541 0 obj<</Filter/FlateDecode/Length 1191 >>stream
+xVmo6_q
+~; -GLK}?jpK1Nf.6nV!<<!N$8W4qr8hU\&j6mïû qO# vrXjc}lLVYvp i # Q`mSFm.D“‚¾péëÃG^piCU`KV/;[!) j C81.==5 Mw2PI"/26<@#Ezh!?OS+6>w^*P%
+W&;I\fBhd C+T7e4`:\A8gá°Á#È<NdjU` kM,RDhYS?vq.`, p>b_{RŽcƒtñÏøÿ¯GR`noDMbn1ZTTZ,VGIg
+=&MemRE] <u#3X')yK# )i;1 :iZR (TIsi4#b5zLëSr0Z"endstream
+endobj
+542 0 obj<</Type/Page/Parent 513 0 R/Contents 543 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+543 0 obj<</Filter/FlateDecode/Length 1137 >>stream
+xV]o6|X(ErO .(=}$Yu"}g)g'uC";;;;^D!~# rLI F`D%ey~FNS0y2 W~,NQ$>E`OF))CLV\4 hZME!M4S|'#@rj#]X[F"(CVtIs'c|AzŽAWBU."kuQ&*YdEJRV;h/CuUJ-P5dQ?e}Z (H0ig+gjcS|ov3z30}M\t.*u]:^Xv4{ <X?]8Q3ng+ `D[
+N0'Cs+@Z%n (¿ÀÞ,wf…Í°¶zû,»UlU)9,J$(s",|k\L<[dsQ0EUz
+ fOiCt!~ T"FgZaK,AnVa`³ÎvÌƔº"†5t.Üj|­Ð.ÿ™ýpR9. wUu߃ÃK$uu hOwwdnv/4v<A>?&3Dj%b
+endobj
+544 0 obj<</Type/Page/Parent 513 0 R/Contents 545 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+545 0 obj<</Filter/FlateDecode/Length 1174 >>stream
+xVkF?b8`+G
+I9RF8&f{3#M)/\}Cp3uo/7y yDq]=$=<a[\'}5ŽÈÃüè`8ü<ê}T$(-STBgUz`TJ 9EMD_dp Aa&8 |g9OREJFaVRD8Me$k"RMaeT%2
+rY"4Ei&.2&%U# [UW#K% LxN]fMF> 8}Z.+SSxgP.~hq\?i(W9p,+_P;l6v'>?u¯O_tR!kkZG!(c>['sQUOpN;o:4
+
+B)@!Y|6<'FWk\`;' $2f ke}Q}iW;7t+qvdL4EU J `lXg)$ML'Yl[k7!tE%.o1
+,@X-rQi&L7I%lK* v~E}Qd`uG/#d=n5"<"_*5cgO"4,6Mk4U'Z$<S`hA/:O?'@MW90t3r]g=6@~ <Xc(! [4R+K[tshe- #VaczC_;4!V
+endobj
+546 0 obj<</Type/Page/Parent 513 0 R/Contents 547 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+547 0 obj<</Filter/FlateDecode/Length 836 >>stream
+xUn0+
+uhHK P]rb,}nKé=¢!V>tVMM;@1G~5M\v©*Ú‘«ãýžø”ï Ey;MzO+OnZ mMb>_hk[
+
+^aE.!zqvq-O1}C1 zLs l0 0 Vu63zV5N?d>f6
+–sŲԠB/<1ZV+Gc/aw>fOBefcu2
+endobj
+548 0 obj<</Type/Page/Parent 513 0 R/Contents 549 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>/Annots 288 0 R>>endobj
+549 0 obj<</Filter/FlateDecode/Length 1893 >>stream
+xWn6}W lv|CYwo, lj1H IuOs Æh]È:uêÔ)êëєÎðoJtqEe{tVGCWMq1\igMofgG[:?yW74S5 eAwRfI~>(kX|IiZ|z~Sc&P$J[I=BPQNK^d$B# *%_]:#Bm^v*n<a"pl=^$+=5+z/+ZlzIDJ2$.PxcwZDoiCb/l,uA,VasBH $8^yPn2],@-)Zi}{k0&Ok`86¶H]rZ+QJKAw[ D:lYJZ-@HDYk``} ekA"-`N~&<=+vmJ9Q`O/f3w. $[X
+QUhn#I[9O=a#m wC:#nJ% TX(>uS$N;Iz;T w=R# mFoJ2 O^-$\9^KJ3uVS RNHSa'Ps[sA
+L06_CLb^ M+ W` mn3 l/r0ªT 1=›Š.N-z Avzol+Hl^ 8._x%@O nv]OCl]jE2 {y{m'F]g 01We&8y ]a6Q m
+%.z+<64VF*Hs~ikNM%T\>i*gLBZ9ArpTjr=t;6d *ª£œ€VOsY6F!Uz\rA`'U:q<uq0d3ha5lKo!USxr>^MjT$tO$<Q~#I#0d(C1B0>9h2K3:E]n~]k{h'G);5ú>G:>+kH4@~z{7ns</6qgP1WZ~O^ *={g<>pqfLL'jk'caK}*`FwD[kSs2 z9f}aR1T`^/1(@{IG%k]kIm+my) ZW e0h/ @ {\brA~zc2JG
+PaQ!/18Kh@o3sSvp A )xEwx ;`hp
+endobj
+550 0 obj<</Type/Page/Parent 513 0 R/Contents 551 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F8 10 0 R>>/XObject<<>>>>>>endobj
+551 0 obj<</Filter/FlateDecode/Length 1709 >>stream
+xmWas8_
+y<$gQ,}]fL7
+:BZuOhmeiiK,>c+n .Od[a!du0v)HpaKIhiiHa=,W=>'JN$D[%k$y@'p@?SM:SJ[MC4X e@ -{$N={]|_~m^uDZTFtK[-z}6sI93(jG_J"Fn&oD0B45]H@1>u>irt@:X8"LGfUmaQT]0Q2
+g::;~PFG-)
+bûB*e'Vj}9wN{r@Q7Jh:AJ$c-R>prM4x;@dD6AJ7PcU !8
+49mb0|W:^<),opa%5W hOKlcìNK > *JD( >'C5]5`dG"$j];N05}xrtd}, ;vmQg`Gb.@f*-n'aGmfjSC^5`1! s_urn%L|0l)'WXDFXmNi# b;I%caaQg/VPrTl3W3'tO
+RG?oj^<%6qP(LxGK
+endobj
+552 0 obj<</Type/Page/Parent 513 0 R/Contents 553 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+553 0 obj<</Filter/FlateDecode/Length 1910 >>stream
+x}XNH}+J<1-R6ha%$^nm3jcl`S)]V3_QR\FX kM']&6)a%$g]2{Un-*s
+;'E4e4j?M canl]Mn<y4YJOjkOp )dlp'SV.5\J4GhXM*v/^dvaRkoxrI1 jT_',O]ngaT-TM]d+=R[#)&Wbw:'Q LVcc G>@vZ:`XVpYR,lIi#@A,azJ[mu
+`u,
+.j/94O.+lGxaQq[ EA2>,2E0Gk^Tk;-#3~O.k
+5i:rm*EA6[ [t[]"5*v(]HJaG;B2`!4 &'Z @ff1se^2laU?\w wY{B3 HEBtZ-j:yt.mp`-SkJQ, t AHCh1` Qo
+%-zbjekCV#}IP+ 9w(_NRn}x VRXKI[E&
+-\>u#3r;snp,)
+6/nM]2/;`ZDuK
+endobj
+554 0 obj<</Type/Page/Parent 513 0 R/Contents 555 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+555 0 obj<</Filter/FlateDecode/Length 662 >>stream
+xUMs0+vr)68i;L?p{"5V 2d}W qHH0H'~
+]xkQE<#1tES"2!Bg?iEc\*N\*TA 7NPBQŒœ:^E-(,Oxb"0sT(sFUTd8@2#"j Y1LLZ;CU)QQk+vH
+endobj
+556 0 obj<</Type/Page/Parent 513 0 R/Contents 557 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+557 0 obj<</Filter/FlateDecode/Length 968 >>stream
+xVr6}WIX )>mz&N]Kf2 JhI@8us<I={v,/dLaLY5=(M\
+pG Z
+gvb' A>-z|~vMqQGV.csDAnld Tb%yN0#.s$ ikbTQ`3=Q(<7G
+Œy„BKxtc6eNR8<p)4m2=B,-y|vD>X!4VC)^V;y
+endobj
+558 0 obj<</Type/Page/Parent 513 0 R/Contents 559 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+559 0 obj<</Filter/FlateDecode/Length 1562 >>stream
+xW]oF|X6`1,Kr) $AZ -Z0SyUw>(VJgSSV1&dJS
+goh2ug ZscZgu.m16SeI$+þÙ­ä‡f#qyÓÖZ$W(Kd
+(rlL5b\UkÊ%–šL4g)KLOxW]ß&sޏ‹¬$Ü9Š­¨E%%d J_nsv+Yg2.}}WtV[IO;ù„SWHU*Dvc2q~l%l6ti6L)"YuIfJe #^xwV 8@/T)Z5h
+Åù ?¬>ÑGrv57Y[IP`
+%|3jdTjO!`<"v5z2O 70]QZ\k>= 
+
+]EGFs0z1;a[c1C#FMN'f#_f!nAA&p7M6Em*^f(1L%kkXG]Y`81WnM'&,%Q=;a&qqZ~5Twfyvw|903 ^duhCjM21Y8[xP3)A#AX|={L!ePA9>e3PB4Hl X;'9m$yr;hN!l0;(8v=^z pB{
+>G6T`~.6A
+R
+endobj
+560 0 obj<</Type/Page/Parent 513 0 R/Contents 561 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+561 0 obj<</Filter/FlateDecode/Length 550 >>stream
+xTMo0 W]$]YvEX#e klXaG1zBH#'Pg19Fhu]P4d!5Px@Ql`jW5X^vxUBw~RgԖ 5·ŒÕ}e{8ÑÕh*-J|=ri@5zX!w*%
+sC0%Xk*{mAPwg@S0T"7`5kzNXx5O)^FrU`}{}^Hn4}I% 4JX%_% ;w47 h8(ECviP/lD;5`Sd/I%dAuKw}8\,sa_V_+'/4c Ei D,M3ky
+endobj
+562 0 obj<</Type/Page/Parent 513 0 R/Contents 563 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+563 0 obj<</Filter/FlateDecode/Length 1254 >>stream
+xVn6+.m VL1AE mHH%|},?&ysoWc{L MWdDY2OSiZtt&#ZkeN3U+'j*]zWqpyz&S}{"bM)82Oe{0Vj/9 iOn-k< /+5
+Kp<M+fNUI>b;[(#H2 -5Ath},Jox/&lIRui+
+'# t*)kl*~sL![
+2UUFm4:S0kaFatu~=<|hQmq&:9j
+
+endobj
+564 0 obj<</Type/Page/Parent 513 0 R/Contents 565 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+565 0 obj<</Filter/FlateDecode/Length 1000 >>stream
+xV]oF}W7PCHMVYV<
+i*ZVJP  PK,UG2RW!C,edpi42>K_b]*NQZBH@+&E!R2.dBZ"&#u^"H#i\E(JT 1T*A\"
+x'}x4o~ozF_E[1:Q8rXd.iId:o?|\-}II:W<gD
+4d=XTFRZLiaJR+QT"5$4 eJhf`1d%}zsiNk9!b|*j"3mx, GYbcx)t<L)muU))Y|f*699P\iVX~z*tC{$JN
+G7Q;y8K~zCwZIce<`+B)JvkC9DhMPaBL?|!X#(bL1PV[e~fAoxHO_#~{T
+endobj
+566 0 obj<</Type/Page/Parent 513 0 R/Contents 567 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+567 0 obj<</Filter/FlateDecode/Length 527 >>stream
+x}S0s[X7 !CAe{]j\`CJU)7bD3(by2z;&\,Xq 2GYR8e4PN5J5Qjwv\j8n(r{ IcaYBcR"jy)7s,|=3"|m3#:%K=N#A JKV'"^Cig (k}Quo=oa0=Xq7=@! ph+=
+<JUbfiJ&KXPlM O}du;&}IicatvhTìâØ*‡^÷Ö;¡œMNa~VR5z
+S[\T+]cF^5'AC-%FtN *d//%Vdogy-eS6|Z;]MgM9:qendstream
+endobj
+568 0 obj<</Type/Page/Parent 513 0 R/Contents 569 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+569 0 obj<</Filter/FlateDecode/Length 1712 >>stream
+xW]o6}00\%v8k
+fC6,|8n)9n\C:W)Ot0eU:gmMm}@Tk .d^9g-Op6?+ijWPUpBZX|''ym++B .\Kgr}-wN8:;Xs4 {
+N1R
+^==7:}[m\vu~
+z ^®ž¡¢ùj¡Kac UI oX=q5pQ_@T2wq;4oƒ4Éi†´ Kx-8i
+4z”ãPf=S89C
+KD2I8R,XjfLo0@s"6XR7!Nhf:{
+6Qf c.h
+"3P< N9KkXk|c=}K=[Z``YEXR.$
+endobj
+570 0 obj<</Type/Page/Parent 513 0 R/Contents 571 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+571 0 obj<</Filter/FlateDecode/Length 1643 >>stream
+x}Wn8}W i(^E&BI"URr`8H$r.g<?SZjAEs2&X\z3|*nK/n&lSZW^$Lh]k / M^Sju/sR]:/F-0%UVoe*UZ?
+5VN GF(>nh`992e6~g].fl-ZI<um+]!29o3 l2Zl%Kv= 0~+\Yl3&!p->pPz/sc[e;VL?}|J!s'gQE#9bQ\ff;[$p&E yVf.U,:0%tV3cW+
+O52Qd`Eos`dI^z[22Cpe:|<m`_NP45S%|Gn?{MAw!7y  o5n{v)|s9Kgm`CO (>! Ha)%?3h F8 mlY6L?HL
+R #KDXo2<xy QE|G$MVi8zf,36tyZ"106@^jD+Q@FX j0=Qh-8'3
+P{,$|B@k<t,[su@J!ÞÃx¦"*xî6Ì€W8)Z E AUXyP#i>í¸…sç+UrC6:==1K*Tw¬XqT {m
+%°ÆFW >I1:
-=I " a "cJvEN{b92q8M=;ZHY`C­C@qa(eCdl?2(Q
- Uqv;XCbbLL{A(OYL!apUtl_,e},;j'h6*2{!qJh)
- XC8aM2S=4c[!kb @!IX0.{8p $edQuliaq\|kcqVt{Y'd^g"Y)EUxua8m"9gLY}T8Ey h$
-!$%( t.! -*M|<wNa1vE+Q0h+T X a,:Fd*KnhVk!Hnekx06+Ó2BgLrno8
-Qd1@C)I_cM-P c14lrz
-V|w\t'd%uC/0!3 bnWDPKID?|7a;#UiK&o5c<jy_bv>Xs„ÂF
-{CBcq* D6]t A`qQ$
-E>9`<dwyaI[CF>LD^aZ
-^
-<yBTc*`z`8R}W>~VX+f#54}YQK/1"
-k-(62lg >yf3=Q{~z.q;uq?X%q9cao !^'bJ JaH,2H0%sh@IA1) f o WWEs8 JR)0}rv-d
-JݚýȝfÏå”JR!U-:rt.1h9u gn'\aP?K2W è #[¸0`«"-7IT`"U#{UB .q] B8pvJKOx_$ -IgJ*r}> q5BT\)_8F*-B\%cb2E#H?Y.,RAh0l _qh eA-%4l=JOJDVd v)@;p5F97? <r2@ei*q#@L[F(-ZA*p2"R08-*Jv}IV!/ZXSZIxk} =; Ij~zc3O#\msi:
-ªlî¼µÍIj>q?] ^a P*bk]3=/6{?? 2$ /
-?-$#^flendstream
-endobj
-1221 0 obj <<
-/Type /Page
-/Contents 1222 0 R
-/Resources 1220 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 1202 0 R
-/Annots [ 1225 0 R 1226 0 R ]
->> endobj
-1225 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [94.952 477.953 394.76 489.945]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://lxr.linux.no/source/Documentation/CodingStyle)>>
->> endobj
-1226 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [94.952 464.403 337.488 476.396]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.fsf.org/prep/standards_toc.html)>>
->> endobj
-1223 0 obj <<
-/D [1221 0 R /XYZ 85.039 781.388 null]
->> endobj
-82 0 obj <<
-/D [1221 0 R /XYZ 85.039 761.463 null]
->> endobj
-1224 0 obj <<
-/D [1221 0 R /XYZ 85.039 667.044 null]
->> endobj
-1227 0 obj <<
-/D [1221 0 R /XYZ 85.039 309.189 null]
->> endobj
-1228 0 obj <<
-/D [1221 0 R /XYZ 85.039 273.125 null]
->> endobj
-1229 0 obj <<
-/D [1221 0 R /XYZ 85.039 250.609 null]
->> endobj
-1230 0 obj <<
-/D [1221 0 R /XYZ 85.039 216.666 null]
->> endobj
-1231 0 obj <<
-/D [1221 0 R /XYZ 85.039 180.601 null]
->> endobj
-1232 0 obj <<
-/D [1221 0 R /XYZ 85.039 155.964 null]
->> endobj
-1233 0 obj <<
-/D [1221 0 R /XYZ 85.039 119.293 null]
->> endobj
-1234 0 obj <<
-/D [1221 0 R /XYZ 85.039 70.285 null]
->> endobj
-1220 0 obj <<
-/Font << /F20 877 0 R /F15 895 0 R /F37 900 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-1237 0 obj <<
-/Length 3357
-/Filter /FlateDecode
->>
-stream
-xZKs8W*sozv`XH I/Vl\.@uywU3| =|C#zs}Qz{ne ".~s.wRNI:^~|mW3;jg'n+g<We-<{e0Rn*yegGPixWR0ro!u4aSFn}sm=<b+xgsxjz EJU=?{1es)o}?.Mju781K%Z ud\"Q>J%#6 +5Nvih(]1EWm6aCixi{qD~Fi}K?51 D?T~k= 3]Yl-Pw/U)Ct,TYh.V@XF8%n j#a'@a@Y#\~4F1oG/Days-6X( `_w EI1P wRn
-~yY#uEKN#[edcK^EY?,E<?h"
-]#Iw\*X"P q+D+-j+]SFVdR'G9A<bt{U SI {8+@,=s97YS.Z<
-7uOZ"lT9y+6i;\dGz I0HqC$LL
-k@fX.,c%-M#_h;tsq8Kl
-~s$+9w`9Shf%'*>'A|V?_C. Qy`Í
-ûþWE{qU0sc?"_
-B|
-<zaxS&~}r#>|<Z+LD(.V@c)Nu,}L:c3@#+ëSodU<\Epf/A@N *);iF 'P7IA)M
- [i`ZY|m`+2a
-6T dTSsH"kbv*O-Frf1GS+C0U5z*I%K9~Sf?t|-+[M7YDGGX|IQ&SI'zdqK-]|&Alo6\Vd75:~3+'-?K#Hw5MNQ
-%™sÍۇl¯Ú*V!r|.e`UQX%#fd!9.?6D-?nySF%
-QCY`
-RIF2XT%fN!3uAT<rb3a9[i!(E@T"|<,@jlbC Nqok=edx},Aig"B/qbM@aLp^5_a<>K -O]xyGvu;soU%$@@0 'd|N/+{ A_"@
-Q  8tA\"L7^32HoF dEG</5#fRUck!
-Ga8HpB$<<~|Ro
-J6d5bg;,ag3(dTjA7><tnNp l(
-:+R54Iumc&MNN"'4FJI5zO5bNP*@p)]7X+?WhL > Pfi'S`E W <HH&.r#/1SBYM48~;53TDI1B9
-[Odm%Nq+->`rLbI<VyIN+aZ]ccHO4_S|`b8)rf9W+fYs ~kN-J 'B5llM!X'1]SsWáÿo±ÿÁ«ÚaàÆ*œž<t|xx¬D4;.Ykendstream
-endobj
-1236 0 obj <<
-/Type /Page
-/Contents 1237 0 R
-/Resources 1235 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 1202 0 R
->> endobj
-1238 0 obj <<
-/D [1236 0 R /XYZ 85.039 781.388 null]
->> endobj
-1239 0 obj <<
-/D [1236 0 R /XYZ 85.039 761.463 null]
->> endobj
-1240 0 obj <<
-/D [1236 0 R /XYZ 85.039 730.35 null]
->> endobj
-1241 0 obj <<
-/D [1236 0 R /XYZ 85.039 694.286 null]
->> endobj
-1242 0 obj <<
-/D [1236 0 R /XYZ 85.039 658.221 null]
->> endobj
-1243 0 obj <<
-/D [1236 0 R /XYZ 85.039 622.156 null]
->> endobj
-1244 0 obj <<
-/D [1236 0 R /XYZ 85.039 599.641 null]
->> endobj
-1245 0 obj <<
-/D [1236 0 R /XYZ 85.039 562.97 null]
->> endobj
-1246 0 obj <<
-/D [1236 0 R /XYZ 85.039 516.083 null]
->> endobj
-1247 0 obj <<
-/D [1236 0 R /XYZ 85.039 491.446 null]
->> endobj
-1248 0 obj <<
-/D [1236 0 R /XYZ 85.039 468.931 null]
->> endobj
-1249 0 obj <<
-/D [1236 0 R /XYZ 85.039 432.26 null]
->> endobj
-1250 0 obj <<
-/D [1236 0 R /XYZ 85.039 396.801 null]
->> endobj
-1251 0 obj <<
-/D [1236 0 R /XYZ 85.039 374.286 null]
->> endobj
-1252 0 obj <<
-/D [1236 0 R /XYZ 85.039 326.793 null]
->> endobj
-1253 0 obj <<
-/D [1236 0 R /XYZ 85.039 274.452 null]
->> endobj
-1254 0 obj <<
-/D [1236 0 R /XYZ 85.039 225.444 null]
->> endobj
-1255 0 obj <<
-/D [1236 0 R /XYZ 85.039 148.731 null]
->> endobj
-1235 0 obj <<
-/Font << /F58 956 0 R /F15 895 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-1258 0 obj <<
-/Length 3217
-/Filter /FlateDecode
->>
-stream
-xZYs8~p51cv2LQvfhT
-1 ')P%e@wpvdN`L:&+rs`<j,=iQ_UrK»Ëzc×í›×·t¦oùãïиr›Øãìó +-ˆÊ¨”œå‚ðÛæ¦r’ÚÑÙ££SIH$^h(Z[p?I%DuwzXT~]bdrt(O {&/YY3X»ì©üt2+±¢ Ç"1#7¡Œª±Š8]Ãý97ëtMzV!
-e.j $]z$,"SPm:*xAn/ *?.D$G}s}=Rnp|=<C o|Cg5aPb=U; hgJC4Lle0'
-hw$G#OJPj7s22gL(-dySZ-7c (pD"\wa>K#O]$qML4&mtWVpp.b /1O:A@H1B"åY~\HpqF.v7lkYS[Y@Cc(OP-Jf1qˁSZ'-  7'YIF 4x %@z[+7eYaBvrlF@,i,^:&^i#FCV[iKAy5o*"L SW:0.Sy&,#LWU 7d0\SgwH QEVy 3`CE{-pHG?3%9A({yioLR&pK#WQtuR=;dG182
-F>``n&tF
-%@GoiB)t
-:aPg/*+ZNt0ËàÓde_!ûcþ-Ø£Ëß× =÷²s×
-ýͪR<E*QPz_8y!~ KFJPh
-oH.ILJg]{!WE')'<|q2G3S0KKepwb
-$sfc}Kr*2M>acQ@7@" Ymd~htZ0;n]T}&2C B3 3ls,jaN
-::~_7rAuPQ44Wgl]-U
-[_i7zgK03/NxgakK L9G,^~lFqrwCECfg =p4*wUC="B~xAF!B`\~]v[,~?@KB):i_?G$t5I9@\j UG;_Yz&r.iVM&fx7j=Rdw {Wzte)jm|m  `Hh <).4Eda&uZWNe9Wendstream
-endobj
-1257 0 obj <<
-/Type /Page
-/Contents 1258 0 R
-/Resources 1256 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 1202 0 R
->> endobj
-1259 0 obj <<
-/D [1257 0 R /XYZ 85.039 781.388 null]
->> endobj
-86 0 obj <<
-/D [1257 0 R /XYZ 85.039 761.463 null]
->> endobj
-1260 0 obj <<
-/D [1257 0 R /XYZ 85.039 671.655 null]
->> endobj
-90 0 obj <<
-/D [1257 0 R /XYZ 85.039 671.655 null]
->> endobj
-1261 0 obj <<
-/D [1257 0 R /XYZ 85.039 640.13 null]
->> endobj
-94 0 obj <<
-/D [1257 0 R /XYZ 85.039 543.278 null]
->> endobj
-1262 0 obj <<
-/D [1257 0 R /XYZ 85.039 516.663 null]
->> endobj
-1263 0 obj <<
-/D [1257 0 R /XYZ 85.039 494.657 null]
->> endobj
-1264 0 obj <<
-/D [1257 0 R /XYZ 85.039 459.047 null]
->> endobj
-1265 0 obj <<
-/D [1257 0 R /XYZ 85.039 418.185 null]
->> endobj
-1266 0 obj <<
-/D [1257 0 R /XYZ 85.039 400.499 null]
->> endobj
-1267 0 obj <<
-/D [1257 0 R /XYZ 85.039 370.476 null]
->> endobj
-1268 0 obj <<
-/D [1257 0 R /XYZ 85.039 339.847 null]
->> endobj
-1269 0 obj <<
-/D [1257 0 R /XYZ 85.039 281.905 null]
->> endobj
-1270 0 obj <<
-/D [1257 0 R /XYZ 85.039 218.59 null]
->> endobj
-1256 0 obj <<
-/Font << /F20 877 0 R /F15 895 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-1273 0 obj <<
-/Length 2079
-/Filter /FlateDecode
->>
-stream
-xYIsFW|
--}Nf+>|W&o5}?0dz)M5 wTO;a`sbeg9\FoZ j:MU`sA2[<WsffE(]MCo9nx5sTf|'c
-}w\xB<Lq Ds6Z.q4 J†8©›ãAQ(" 9`YY/0*N*8W@U[K|2&~)q;0{0\hpku`X'uS@#6RKah9uo5
-C'/FWNvm#,e{m"IP("$$m^ >}Z\(\`qp9'%C" z8_P ZYDR i`lBQ`zF]yPa'‰X. 9`m)U"7
-\bF<
-endobj
-1272 0 obj <<
-/Type /Page
-/Contents 1273 0 R
-/Resources 1271 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 1289 0 R
->> endobj
-1274 0 obj <<
-/D [1272 0 R /XYZ 85.039 781.388 null]
->> endobj
-1275 0 obj <<
-/D [1272 0 R /XYZ 85.039 761.463 null]
->> endobj
-1276 0 obj <<
-/D [1272 0 R /XYZ 85.039 678.275 null]
->> endobj
-1277 0 obj <<
-/D [1272 0 R /XYZ 85.039 653.638 null]
->> endobj
-98 0 obj <<
-/D [1272 0 R /XYZ 85.039 619.166 null]
->> endobj
-1278 0 obj <<
-/D [1272 0 R /XYZ 85.039 589.762 null]
->> endobj
-102 0 obj <<
-/D [1272 0 R /XYZ 85.039 550.188 null]
->> endobj
-1279 0 obj <<
-/D [1272 0 R /XYZ 85.039 526.206 null]
->> endobj
-106 0 obj <<
-/D [1272 0 R /XYZ 85.039 498.26 null]
->> endobj
-1280 0 obj <<
-/D [1272 0 R /XYZ 85.039 476.399 null]
->> endobj
-110 0 obj <<
-/D [1272 0 R /XYZ 85.039 447.846 null]
->> endobj
-1281 0 obj <<
-/D [1272 0 R /XYZ 85.039 426.592 null]
->> endobj
-114 0 obj <<
-/D [1272 0 R /XYZ 85.039 398.645 null]
->> endobj
-1282 0 obj <<
-/D [1272 0 R /XYZ 85.039 376.784 null]
->> endobj
-118 0 obj <<
-/D [1272 0 R /XYZ 85.039 335.288 null]
->> endobj
-1283 0 obj <<
-/D [1272 0 R /XYZ 85.039 313.427 null]
->> endobj
-122 0 obj <<
-/D [1272 0 R /XYZ 85.039 285.481 null]
->> endobj
-1284 0 obj <<
-/D [1272 0 R /XYZ 85.039 263.62 null]
->> endobj
-126 0 obj <<
-/D [1272 0 R /XYZ 85.039 235.067 null]
->> endobj
-1285 0 obj <<
-/D [1272 0 R /XYZ 85.039 213.813 null]
->> endobj
-130 0 obj <<
-/D [1272 0 R /XYZ 85.039 185.866 null]
->> endobj
-1286 0 obj <<
-/D [1272 0 R /XYZ 85.039 164.005 null]
->> endobj
-134 0 obj <<
-/D [1272 0 R /XYZ 85.039 135.452 null]
->> endobj
-1287 0 obj <<
-/D [1272 0 R /XYZ 85.039 114.198 null]
->> endobj
-138 0 obj <<
-/D [1272 0 R /XYZ 85.039 86.251 null]
->> endobj
-1288 0 obj <<
-/D [1272 0 R /XYZ 85.039 64.39 null]
->> endobj
-1271 0 obj <<
-/Font << /F58 956 0 R /F15 895 0 R /F20 877 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-1292 0 obj <<
-/Length 1935
-/Filter /FlateDecode
->>
-stream
-xYms7_t~
- 0$/tb3]to>'teyvR|+d8_jCPa¹Ï?Not{h,£(ö&#î]¼<C/A
-> 'R*pVF!5 L'`]Q,& pxuz){*`vqSA(^(|[I
-0]f[rvf~
-}Em rMQb(I@;/leJ:C,%(.u27l+/
- 5 0~E&jMs"vzUem' ðÂhè*&P`IH`2S
-%mA`M1[|G;_ r(]3oQ Yz<#"af{3Zo36Mp'\.:bA.H.ot 
-qHXe'nLNQdO
-q)\Z2 9o\v.cvBw - [M@r#uKU+F^z32.}Y*JH`AAheZl}g*%01Nj]wu|w/b}
- `q~r?BB8 g JXkax\xBj'N~]9)](NE]y|IwxG
-$SBxtJfQzjF6ol=#-dp@U-zYE=J(]ucxQ{1=6o/×w‚sG~e =SPU+Y`a:4m^p$ d{
-*`ck2TchoLïJ~
-u^|Ų‡¨qÂ8ÿñ0ŽÏSˆ@SlH2*5u|i?3/H*` =k>U@Pn>Y+3HX x~<r*z/Cvco2`PMs:- r# endstream
-endobj
-1291 0 obj <<
-/Type /Page
-/Contents 1292 0 R
-/Resources 1290 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 1289 0 R
->> endobj
-1293 0 obj <<
-/D [1291 0 R /XYZ 85.039 781.388 null]
->> endobj
-142 0 obj <<
-/D [1291 0 R /XYZ 85.039 761.463 null]
->> endobj
-1294 0 obj <<
-/D [1291 0 R /XYZ 85.039 740.47 null]
->> endobj
-146 0 obj <<
-/D [1291 0 R /XYZ 85.039 712.523 null]
->> endobj
-1295 0 obj <<
-/D [1291 0 R /XYZ 85.039 690.662 null]
->> endobj
-150 0 obj <<
-/D [1291 0 R /XYZ 85.039 651.288 null]
->> endobj
-1296 0 obj <<
-/D [1291 0 R /XYZ 85.039 627.306 null]
->> endobj
-154 0 obj <<
-/D [1291 0 R /XYZ 85.039 599.359 null]
->> endobj
-1297 0 obj <<
-/D [1291 0 R /XYZ 85.039 577.498 null]
->> endobj
-158 0 obj <<
-/D [1291 0 R /XYZ 85.039 538.124 null]
->> endobj
-1298 0 obj <<
-/D [1291 0 R /XYZ 85.039 514.142 null]
->> endobj
-162 0 obj <<
-/D [1291 0 R /XYZ 85.039 473.593 null]
->> endobj
-1299 0 obj <<
-/D [1291 0 R /XYZ 85.039 442.067 null]
->> endobj
-166 0 obj <<
-/D [1291 0 R /XYZ 85.039 295.167 null]
->> endobj
-1300 0 obj <<
-/D [1291 0 R /XYZ 85.039 276.295 null]
->> endobj
-1301 0 obj <<
-/D [1291 0 R /XYZ 85.039 253.152 null]
->> endobj
-1302 0 obj <<
-/D [1291 0 R /XYZ 85.039 230.637 null]
->> endobj
-1303 0 obj <<
-/D [1291 0 R /XYZ 85.039 208.121 null]
->> endobj
-1304 0 obj <<
-/D [1291 0 R /XYZ 85.039 185.606 null]
->> endobj
-1305 0 obj <<
-/D [1291 0 R /XYZ 85.039 163.09 null]
->> endobj
-1306 0 obj <<
-/D [1291 0 R /XYZ 85.039 140.575 null]
->> endobj
-1307 0 obj <<
-/D [1291 0 R /XYZ 85.039 118.059 null]
->> endobj
-1308 0 obj <<
-/D [1291 0 R /XYZ 85.039 81.388 null]
->> endobj
-1290 0 obj <<
-/Font << /F58 956 0 R /F20 877 0 R /F15 895 0 R /F37 900 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-1311 0 obj <<
-/Length 3054
-/Filter /FlateDecode
->>
-stream
-xZYoF~`q;o `2D[L$KRx~a{0/ fuwQWV
-":J_n+2(XVz<,Wn@c%JeX)n^hZW6,6 ~f,S( Kv@Y9(:,ic/r3g;YdpaGsw[S pQ({rmCP$\{Y@?pkYUN02bSsx-{{Kes/5 7Xw,4pf{=fTPfY<XgTml6S_!(J+Ew OLu(x$kZWx24J=ww(ü㦫jÚR4%%PgT2z{UN9 j>
-IPs!-n, 2WEu+[k3QM!cWG}%9&;oJ&7a'?>/F[
-n-OX+/Xkh,'¶œN&vh0zd]K M
-{]o^9r_u OE:6,ro6djyV.*Y|M*G2X%
-tBk#71*o.dHiR0KT<_}Qj/SY9n *|<; $J
-:<~J2T :Y¸¨Š=°;¯G dreqX-B-fk1B&)MLfD(v'+$EaJV C0z ajM-=6p[P_dD+Ix[bP =w`
-h%;a"8 PR1n&[.: 3L
-I@yGR^?*[bcl_Yj&'6Y-'Nm' <#'lPD;v7-ulY#1v8GpRJmy4yJ<kTC'^~?WA=gMjx >endstream
-endobj
-1310 0 obj <<
-/Type /Page
-/Contents 1311 0 R
-/Resources 1309 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 1289 0 R
->> endobj
-1312 0 obj <<
-/D [1310 0 R /XYZ 85.039 781.388 null]
->> endobj
-1313 0 obj <<
-/D [1310 0 R /XYZ 85.039 727.362 null]
->> endobj
-1314 0 obj <<
-/D [1310 0 R /XYZ 85.039 693.418 null]
->> endobj
-1315 0 obj <<
-/D [1310 0 R /XYZ 85.039 628.134 null]
->> endobj
-1316 0 obj <<
-/D [1310 0 R /XYZ 85.039 605.618 null]
->> endobj
-1317 0 obj <<
-/D [1310 0 R /XYZ 85.039 569.553 null]
->> endobj
-1318 0 obj <<
-/D [1310 0 R /XYZ 85.039 519.333 null]
->> endobj
-170 0 obj <<
-/D [1310 0 R /XYZ 85.039 436.16 null]
->> endobj
-1319 0 obj <<
-/D [1310 0 R /XYZ 85.039 415.167 null]
->> endobj
-1320 0 obj <<
-/D [1310 0 R /XYZ 85.039 391.419 null]
->> endobj
-1321 0 obj <<
-/D [1310 0 R /XYZ 85.039 355.354 null]
->> endobj
-1322 0 obj <<
-/D [1310 0 R /XYZ 85.039 281.369 null]
->> endobj
-1309 0 obj <<
-/Font << /F58 956 0 R /F15 895 0 R /F20 877 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-1325 0 obj <<
-/Length 985
-/Filter /FlateDecode
->>
-stream
-xMs6<"I]u:=$9@$q"
-bAZTh{3:P0n^D,)
-wsBwGy/Ü(d"î|mºÌW?f/$I< ZSf~ y7[s9?'HY%8]\;!KDC;dIyxu/utG &b>r)r1$9eI&Cj [)xdJ^[LV.ZjT1 aOW!n{+%
-o\KjO*j] ? Oc=P{g5t5=gWoh8.7@Sc<&1_[9Ij 9e&Ho'Hiz H910rBN&aD8hg!9K!H AL+uCF+:@EV«¬£éB <c#z2m:w-H-ugECrhKDs<H#udFFp
-yx_jHZI+w
-VPFiJ!h$)Le4hÜSF^qDW3R?]YKDd!o';9jc@bc3bzoSk×פ²á̱ÿV%R{cU|E!J&
-{_ O-\L.MEc&mj>EK789fVMY=* 'P&"/^
-endobj
-1324 0 obj <<
-/Type /Page
-/Contents 1325 0 R
-/Resources 1323 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 1289 0 R
->> endobj
-1326 0 obj <<
-/D [1324 0 R /XYZ 85.039 781.388 null]
->> endobj
-174 0 obj <<
-/D [1324 0 R /XYZ 85.039 761.463 null]
->> endobj
-1327 0 obj <<
-/D [1324 0 R /XYZ 85.039 739.701 null]
->> endobj
-1328 0 obj <<
-/D [1324 0 R /XYZ 85.039 705.131 null]
->> endobj
-1329 0 obj <<
-/D [1324 0 R /XYZ 85.039 680.494 null]
->> endobj
-1330 0 obj <<
-/D [1324 0 R /XYZ 85.039 660.099 null]
->> endobj
-1331 0 obj <<
-/D [1324 0 R /XYZ 85.039 635.463 null]
->> endobj
-1332 0 obj <<
-/D [1324 0 R /XYZ 85.039 612.341 null]
->> endobj
-1333 0 obj <<
-/D [1324 0 R /XYZ 85.039 590.432 null]
->> endobj
-1334 0 obj <<
-/D [1324 0 R /XYZ 85.039 567.916 null]
->> endobj
-1335 0 obj <<
-/D [1324 0 R /XYZ 85.039 544.794 null]
->> endobj
-1336 0 obj <<
-/D [1324 0 R /XYZ 85.039 522.885 null]
->> endobj
-1337 0 obj <<
-/D [1324 0 R /XYZ 85.039 500.369 null]
->> endobj
-1323 0 obj <<
-/Font << /F58 956 0 R /F20 877 0 R /F15 895 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-1340 0 obj <<
-/Length 2148
-/Filter /FlateDecode
->>
-stream
-xYKo0El`J"G/3s" E#+0J$/I1)
-_|sI)xIA[/1;`@bv/# f(mWLe!"jUi,NBzPE~sLPsY -5\Sni~qc5MYOx&H2i-w Kay(4GG:x[Eln V:"4]C]8E)C}Nx;t P~</U9}ev~Q\/!+~/8,+!'
-8laj2Z'1kK<&/Fkx}Gr:g!=hw-@wn#&Lk:^q]plmkP"8,NWTf,8>Hz';G<t$hT] w/{lP\m<Uyr mq-/K&g9E
-P.tlsWAiU:,:DN
-vr A1$Ì#ÙëA /@4}3{ #+Zdj6"KG:C<}qGqM0d{j+04c&_pD
->vZ=0<s o/dgltJs6D|MvJK@TfY$X<<LKHsi*Az3X~ @j|0Q\@F)*Mp_hG&` O,\"- A'- Gxk+4JW$<[}LELGU5H
-yQgYbGl6B6Q R#':
-7u3UY0r[7V@r:U825k& t~UJlw T~z!7$_L+X&VP($yyU
-~D|(|\aYKv]w O 0rx&^P+ -Hbg¸E3._CbJo+5[<uBuqÔþ.U)káŠF:E:A !5 u`_s )!& ~qw0_5UR|?W? Oa2JP!KLB\R6LCn1MwKOoL/fz9aI%^dnC:t/UOt5 :gKWEj]hS$qb+O'2IÛendstream
-endobj
-1339 0 obj <<
-/Type /Page
-/Contents 1340 0 R
-/Resources 1338 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 1289 0 R
->> endobj
-1341 0 obj <<
-/D [1339 0 R /XYZ 85.039 781.388 null]
->> endobj
-178 0 obj <<
-/D [1339 0 R /XYZ 85.039 761.463 null]
->> endobj
-1342 0 obj <<
-/D [1339 0 R /XYZ 85.039 671.062 null]
->> endobj
-182 0 obj <<
-/D [1339 0 R /XYZ 85.039 671.062 null]
->> endobj
-1343 0 obj <<
-/D [1339 0 R /XYZ 85.039 639.536 null]
->> endobj
-1344 0 obj <<
-/D [1339 0 R /XYZ 85.039 605.028 null]
->> endobj
-1345 0 obj <<
-/D [1339 0 R /XYZ 85.039 583.119 null]
->> endobj
-1346 0 obj <<
-/D [1339 0 R /XYZ 85.039 559.997 null]
->> endobj
-1347 0 obj <<
-/D [1339 0 R /XYZ 85.039 537.482 null]
->> endobj
-1348 0 obj <<
-/D [1339 0 R /XYZ 85.039 473.53 null]
->> endobj
-1349 0 obj <<
-/D [1339 0 R /XYZ 85.039 453.135 null]
->> endobj
-1350 0 obj <<
-/D [1339 0 R /XYZ 85.039 430.62 null]
->> endobj
-186 0 obj <<
-/D [1339 0 R /XYZ 85.039 356.148 null]
->> endobj
-1351 0 obj <<
-/D [1339 0 R /XYZ 85.039 334.951 null]
->> endobj
-1352 0 obj <<
-/D [1339 0 R /XYZ 85.039 289.156 null]
->> endobj
-1353 0 obj <<
-/D [1339 0 R /XYZ 85.039 264.519 null]
->> endobj
-1354 0 obj <<
-/D [1339 0 R /XYZ 85.039 228.455 null]
->> endobj
-1355 0 obj <<
-/D [1339 0 R /XYZ 85.039 191.784 null]
->> endobj
-190 0 obj <<
-/D [1339 0 R /XYZ 85.039 159.092 null]
->> endobj
-1356 0 obj <<
-/D [1339 0 R /XYZ 85.039 137.896 null]
->> endobj
-1338 0 obj <<
-/Font << /F20 877 0 R /F15 895 0 R /F43 1079 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-1359 0 obj <<
-/Length 1295
-/Filter /FlateDecode
->>
-stream
-xWYoF~H#ryCcM4iEiY0E<s,) qa$)+J86pBiB\-Hdbe]~}ujP8n>:8} 97~@7 )t[wB%[X|\|os\_B,9t4c>^`. Y5o?Eg^RGS>%$n0C-uUKmU
-\#Px\ _$O'+2qqur#w$,B|M5U-YN[Dim>IgmCjnx UQTr0 wxT,8,7g@IB
- -Z?&nG@mW7CQ; k wZ4°d÷âzO0SK5$}, UP1RxA0\DCð€¬D.<P(Oiib@{>8|m32ft\1Ç¡y]!
-¦Æ!\À ëŸ=,I~'
-G/SIYaA`zD0!=,'rU{T3^#8$\ v{i;Ml{„õú¡ÄœÔF7PzR
-Ö9kÆýАO~Bo=? A&4&Ght}kM`wlPM& PloKFLq#`|<)lFT=pf~F:OG&<uQ5G6TuTwGtDp\@ P~<e~bQ0 4?y$?Tftq`2*(PqNlZa
-ji.LD;*tMZ_0
-endobj
-1358 0 obj <<
-/Type /Page
-/Contents 1359 0 R
-/Resources 1357 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 1289 0 R
->> endobj
-1360 0 obj <<
-/D [1358 0 R /XYZ 85.039 781.388 null]
->> endobj
-194 0 obj <<
-/D [1358 0 R /XYZ 85.039 536.7 null]
->> endobj
-1361 0 obj <<
-/D [1358 0 R /XYZ 85.039 516.567 null]
->> endobj
-1357 0 obj <<
-/Font << /F58 956 0 R /F37 900 0 R /F15 895 0 R /F43 1079 0 R /F20 877 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-1364 0 obj <<
-/Length 1373
-/Filter /FlateDecode
->>
-stream
-xWKs6Wf*S"
-*ga/wN~RJ?f IR~B?wgD8d2~MkzEDE_F[>8Y=3eb)T$w9:K[QX*/i%]  E^dZDqm>*T~%K 63wíh¹×å2ßvX`iT& D2){+C GLFlXu
-BT>ucXG%5Y
-y|s-pTe:Zf
-n,#6k=C(>xb`^Gf+,@$v
-k]RK l2++Lafoi%8^,zqpÈ]i ¼ÇÖÅ*F1fh3]U&2o060;D 4?@.I`e<=\KiB8G:Bo x%C7 T;id<Ic
-o?g&2D+aendstream
-endobj
-1363 0 obj <<
-/Type /Page
-/Contents 1364 0 R
-/Resources 1362 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 1372 0 R
->> endobj
-1365 0 obj <<
-/D [1363 0 R /XYZ 85.039 781.388 null]
->> endobj
-198 0 obj <<
-/D [1363 0 R /XYZ 85.039 667.913 null]
->> endobj
-1366 0 obj <<
-/D [1363 0 R /XYZ 85.039 636.387 null]
->> endobj
-1367 0 obj <<
-/D [1363 0 R /XYZ 85.039 497.28 null]
->> endobj
-1368 0 obj <<
-/D [1363 0 R /XYZ 85.039 474.158 null]
->> endobj
-1369 0 obj <<
-/D [1363 0 R /XYZ 85.039 452.249 null]
->> endobj
-1370 0 obj <<
-/D [1363 0 R /XYZ 85.039 418.305 null]
->> endobj
-202 0 obj <<
-/D [1363 0 R /XYZ 85.039 355.182 null]
->> endobj
-1371 0 obj <<
-/D [1363 0 R /XYZ 85.039 334.592 null]
->> endobj
-1362 0 obj <<
-/Font << /F58 956 0 R /F15 895 0 R /F37 900 0 R /F20 877 0 R /F43 1079 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-1375 0 obj <<
-/Length 3268
-/Filter /FlateDecode
->>
-stream
-x]=b@q2I,@[wH+z=@F Qf}l9)P,"p8o:y/y(W2Y|Dfd+\egt)OqVli7O4^yxbZ?S ?ET/-pInao
-!D0R#`M;A5q<^E1G{rwK _.d^y";7 =v<h7|-9r`
- Y@rHyDJeVf24B|gGbSfe% r}"8äS
-;Ya &`k0Ebe#! oVIg(jLY-$Ip[2<-8mluzbµ²ïðVG H)+C-TJ P+LP:xyEl3t'~WlB,'6Xy~35‰~ùû¯È Àžà@Nv3CeEMb#z+-VM&Mwex-l
-'BQx^6v oQm?zUxtC :&z4I M=NIb_,m=.G 6hyz6TCt%{nDeqd $Yf 4P"K
-DW U;vAi&'bBXb>w:Nq(sf6o'aC t]
-v")lwqhL;dd9i1!3+m3d
-z^i2P -";iPPLA2Xj>#:J2'-~>QR 'l\O l\^-eUGbq{-03z{BkWsM~s#_sA:&t4riL!!^=EKWL7]stZYN:M<z;L'j2Yf*B"nQp|j8_\r1<u`) 'p 8],=)[.d9 O[a`bpr`A
-ABep0 eoO?R
-Y $FfA5na@I7u?h2V`_'x5usT)^ +UfGtN=Wk- *V180tn&B2c mGm v}? @B79T 5;IZI!@}`"%tO]i,x&M&>QO%|6<<>~qã…z‹¡H.o1UL$TB=,taZuOè† p³l ™´•
-®
-¿§Š|ÅbÈ~´UHs3[i\(/>SR6*4;sO6[Ua m_T7@T4sW2X!}W m[7,
-a! )^F,dE<M 2,{v>@bwg^fae,_
-gVC cHtkGG\.`u^*t&?àû†|åí™ÚP '8]$Go+V w79f_X3UA]$x It@Bd`$)t xA
-sA.Ui/:jpcHr10 9(ft9y+eJz;.8 E=Ocgo%
-endobj
-1374 0 obj <<
-/Type /Page
-/Contents 1375 0 R
-/Resources 1373 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 1372 0 R
->> endobj
-1376 0 obj <<
-/D [1374 0 R /XYZ 85.039 781.388 null]
->> endobj
-206 0 obj <<
-/D [1374 0 R /XYZ 85.039 761.463 null]
->> endobj
-1377 0 obj <<
-/D [1374 0 R /XYZ 85.039 671.062 null]
->> endobj
-210 0 obj <<
-/D [1374 0 R /XYZ 85.039 671.062 null]
->> endobj
-1378 0 obj <<
-/D [1374 0 R /XYZ 85.039 642.326 null]
->> endobj
-214 0 obj <<
-/D [1374 0 R /XYZ 85.039 569.569 null]
->> endobj
-1379 0 obj <<
-/D [1374 0 R /XYZ 85.039 542.954 null]
->> endobj
-218 0 obj <<
-/D [1374 0 R /XYZ 85.039 212.156 null]
->> endobj
-1380 0 obj <<
-/D [1374 0 R /XYZ 85.039 183.358 null]
->> endobj
-1373 0 obj <<
-/Font << /F20 877 0 R /F15 895 0 R /F40 1163 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-1383 0 obj <<
-/Length 3686
-/Filter /FlateDecode
->>
-stream
-xZKsFWtY0e<,y-f$@Q $hmT% 4r'2I=7HEu1\/<1 Ir)W?}| pw4Nyh9<v{w
-/#?u>]~tq3?0?/~}r?]L`^=q@*<^m7u~4,1n=aAHp4ixN (85kVoq"a6#X:n8YVv/qI\9%L@C4r0ROH_q'.U$kAI+5i\.
-4j nyQ@V%,
-e/,zx|78`xBs#Sv<lb#\e1k6 uFe7{m>6@'~:>cOi59|gU79fr*<2k^S2V-.`RNx8Z|yl"qyk-FHj"]kDlTyuNI4r{DEKUv )$AsldtvC/v@q\< 7<gM ]mU/bWGs+d0_t`Zc"y<|{3Yj/&]6V#* j@ukhZ,
-D%,
-w7=K~jmVsyJFDAAwNgMb{2 \e+-tZ2wt\N<"r%L$k3B{IS$t.+@</eM w/p-R6(1`S^(~eJ[{e/ \"#@cAG?1;eUt>lbwh$#cjh^z.rb`ESnHk"rqFIY.p#W8XgZ&
-v8E]!F*Bi(R/"kn%? 0/?H>n?VhF7<gCUs 0 *u}'X=CU k
-)e'^2\ x-_8_0nnN|(=<]ƒÂ­ú®¯±£øzt†HD8aq&)|tq}L4faGW| W.'W >T#/7P~)r3,
-BR(!"<x[C9y8tOESJw{`2`g%m
-(5>5R3J dSAx(uh;3$jt3$.'),g N8o`fBXu5c@[fyF -ufa@`(zZjTuuvJf$/iP
-NA+$1 91y0I)pb%sU32XmzMxJ4L +yt{>
-'d!<B$NyexU<P
-ctK)lH#ln4W8Ph4ál°ðcÔ行À¤ ±‹9õù0ÖR-d(;6taxCg%!?
-lnldNA;nLMLN 7AMp8s C*~e4t K]XvLHf~_ [.c9S4A.\]Y1VT/M"n<<l {roS\e%OF}Y: RG*p?u-;(0,Q*cA`7OA|gT }cm@ uT= \nY&/:(yegyz#>DBdjY^dF
-`E#aG=)7a1<Th;vPl^M#zYv2wI%c,^œn{¡ëÌ_ ÀãE`4KA»â\i {iÙ¶ªvøˆE=Q>/tZ*0=$Sa7z3|vU5 ra)0GXVfj|91]WnGMB []!21Z8{IVQx &4-{qP>GRaAMk~rE/m`gUu %|hlV_‹A!`*I2a cuY)*!a;k/RcYRQi,! pi-c`6`oBXa©jHT9s{-v~|qh
-l†ñ¹ÊNZe')$G/$Je\'O+6:nYi qBA2+3<Z Wq7`*%AG.aJ5db^$vcr ]7knFB\? |[}754J|w:70adkf/og72uIxywwg89eFA;?qMZIp Fw3j:s;a~]^S_Js#L>#Tv pRzF'V FF; 4$<w}2eyyc|sh"m/][M.oYJ:FS (
-tT~U=IX}/] 0c5s[¥á°ðEe:Z=V;&fK;Oq<;qX"[l0^&HFRfgt } |>B`UEg)i&IV wMxpXQ`B |[vai 1>NLH
-endobj
-1382 0 obj <<
-/Type /Page
-/Contents 1383 0 R
-/Resources 1381 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 1372 0 R
->> endobj
-1384 0 obj <<
-/D [1382 0 R /XYZ 85.039 781.388 null]
->> endobj
-222 0 obj <<
-/D [1382 0 R /XYZ 85.039 761.463 null]
->> endobj
-1385 0 obj <<
-/D [1382 0 R /XYZ 85.039 739.701 null]
->> endobj
-226 0 obj <<
-/D [1382 0 R /XYZ 85.039 547.122 null]
->> endobj
-1386 0 obj <<
-/D [1382 0 R /XYZ 85.039 515.597 null]
->> endobj
-230 0 obj <<
-/D [1382 0 R /XYZ 85.039 242.391 null]
->> endobj
-1387 0 obj <<
-/D [1382 0 R /XYZ 85.039 212.987 null]
->> endobj
-1381 0 obj <<
-/Font << /F58 956 0 R /F20 877 0 R /F15 895 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-1390 0 obj <<
-/Length 3974
-/Filter /FlateDecode
->>
-stream
-xZYoG~!2s/ H$yCjC<3yXY]]] .} .dGe(/ rM=t4w?K~qy!w?7zYE^6,nNtxWowu+|~Kw? s?8wx3%?<(ED$\^b/arZ3zRXa8u,I|nZ^/hlxQ{foW?' a0O$'G-krC-1t;zxD!g>=P/_:F@MiBO'" ¦ôђHQb:zH
-'_mRqup9!hl!r
-SD/]= =KZ*|n?r8= %" 4P "HVOR9{Sv#L2_0M/u=a}
-b y*`y' 1-Q4sQpnuG
-X!== I;pIwbtglUm5EQxUĘ8:SE\Q|.E!@5g1r|>6hKa@,Ó6©¢ü@4 ;+[3x#W"K,6<WL{Er%C:9nOYQp*n13À¡î¹Âˆž7Û£üiWuuqS&puM9 $\~-F+,xfneuB
-ja,~),ugO©S ;h4wF|K
-Mpt["c[b1*i*)j!p=*QtQ7t(qvu*H%Me<q NgZY:
-gWY=!;FgMIueQ"{pJ*j~!wz=ayrP5<'k
-y8>HO78~b#:Q&%zil.g†ÆŠ¿x?Ûßh|¬x<Ð&#¸rÂ×Y_n7Dg"a<Ybcm/oQH%lLF|Gxws/fMW
-bZqRYv0&L2jh6#Fœ~çhaã<:N#:_ExQ=
-endobj
-1389 0 obj <<
-/Type /Page
-/Contents 1390 0 R
-/Resources 1388 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 1372 0 R
->> endobj
-1391 0 obj <<
-/D [1389 0 R /XYZ 85.039 781.388 null]
->> endobj
-234 0 obj <<
-/D [1389 0 R /XYZ 85.039 761.463 null]
->> endobj
-1392 0 obj <<
-/D [1389 0 R /XYZ 85.039 736.911 null]
->> endobj
-238 0 obj <<
-/D [1389 0 R /XYZ 85.039 641.966 null]
->> endobj
-1393 0 obj <<
-/D [1389 0 R /XYZ 85.039 613.231 null]
->> endobj
-242 0 obj <<
-/D [1389 0 R /XYZ 85.039 391.432 null]
->> endobj
-1394 0 obj <<
-/D [1389 0 R /XYZ 85.039 362.028 null]
->> endobj
-1388 0 obj <<
-/Font << /F58 956 0 R /F20 877 0 R /F15 895 0 R /F40 1163 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-1397 0 obj <<
-/Length 434
-/Filter /FlateDecode
->>
-stream
-xRMS0W(,$K#Pw`88:6jN` {}+&BY1XA};BPEC$#GgRp+,V#$+lvJ) LS@$%_^cn1,`ivD]^<dd{?\'
-G-}Dpe }Z&:V<jkrM~`NSd+zmk0ci B/+eh*7SlU%"b CNT{!k¬µ#äÅà^`¦U<y+-1+0'kM{-+| z<z\:wv_~@%l@)vTG I}xnv<:?=~lq 
-endobj
-1396 0 obj <<
-/Type /Page
-/Contents 1397 0 R
-/Resources 1395 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 1372 0 R
->> endobj
-1398 0 obj <<
-/D [1396 0 R /XYZ 85.039 781.388 null]
->> endobj
-1395 0 obj <<
-/Font << /F58 956 0 R /F15 895 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-1401 0 obj <<
-/Length 3331
-/Filter /FlateDecode
->>
-stream
-x]~vr2VD"izA.9)^d[k+KDew}eSpiu[awZz};0;%3t\*#cQZ%w';X/iEU 42YeA_-C,*(OZP/ou[d%1Y*S@ry/Kd]"we E^cZRiqBqsakm- Rhg#PH2By s:CD&)gEA<:nc, iw<0t;JvN SmW{G1W1p6o'vqvdm7x/+L  . p'>-#á4
-l‹=Oa
-]eLV2?{;]|$HH*K#Bs `d~n3t+dz%sOsE`K|5e$n`?
-- ^/Ud/nTbQr'*jTP"r7mNgfl8Pir`4xm}<d-J"%$xYFW~px.d!7%qK 2OFu0x~YM`w>^0 $QU&_95pwCO7o|]l#$td
-
-HB3KI!u[@i P+XNv,/z8 %<==M|cd}>JG9gk*h p`qEs~
- })8,-^f\KK!<8 '
-pviMh8D8v|e
-*}pWQc
-G`^[%PYDRd'<\2BhD0A.aG< $rL1`8au#crg !.9w<{lDyIf*ILA$'_fvaB)L.\7Q"c#B5% ,GFs9'6%'lkh?WZ"@5 |u w^I#+,4{MkfF%#q'5/0St9\DS?.yiW{J:[Wjkc^4H*=2Ab*kKRH4 h&O< 6wxL)E |WWhSny2[Lw B-tQNhIcB3
-N4_O5 " Xj
-C3
-endobj
-1400 0 obj <<
-/Type /Page
-/Contents 1401 0 R
-/Resources 1399 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 1372 0 R
->> endobj
-1402 0 obj <<
-/D [1400 0 R /XYZ 85.039 781.388 null]
->> endobj
-246 0 obj <<
-/D [1400 0 R /XYZ 85.039 761.463 null]
->> endobj
-1403 0 obj <<
-/D [1400 0 R /XYZ 85.039 667.044 null]
->> endobj
-1399 0 obj <<
-/Font << /F20 877 0 R /F15 895 0 R /F61 1406 0 R /F37 900 0 R /F62 1409 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-1412 0 obj <<
-/Length 819
-/Filter /FlateDecode
->>
-stream
-xUmo0_#5mL`[Aj)# KAN>s>?0 (O(fcwtuE@aNd2$4q6I;2:N8(I:xaLF<SN=FN1,|=g8@9=P7g xki]:B@
-n g|z1pBAK4cq aC!'] jq#,^X2C
-{6S[;`1TNp!I{QIV.*/2f]Y@HYs Do3l2`[#fd*A]muw4ImWHsmz'<)W(%plzyrPaTkj{Z'Yv2XHfh[ qG{)e:)8 +,/Nuz4yFZ+t;K #gDSJ/[).CI8FWEuO%=& W?&_n&1`*#I>½ÏÌ:ŒFu,U*J>{27[C5b.VZbJJV }DfXUCDVxSa4L`i:P,k}kY݉xEWw-5 r|3xDVcO >cPp"{xi|Wz9<=5Yl#u9J:\#W48y}hugZºK#oendstream
-endobj
-1411 0 obj <<
-/Type /Page
-/Contents 1412 0 R
-/Resources 1410 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 1414 0 R
->> endobj
-1413 0 obj <<
-/D [1411 0 R /XYZ 85.039 781.388 null]
->> endobj
-1410 0 obj <<
-/Font << /F58 956 0 R /F15 895 0 R /F37 900 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-1417 0 obj <<
-/Length 3435
-/Filter /FlateDecode
->>
-stream
-xks~&_
- TvTK4uHx0xH
-&Axej3j/y55d@G} bD >% IH`Aw%Z_5i:W|)=@G8\W0Cf9#X(9h;vi"l$)jE"#>$`*B4pD95FG3CZf|YuÆð­nd±Îُ\km¤ëGYrD
-;lh,B ]O{m'Bf'oTJq7}S`Doq
-erV3uMB<HsaH
-WyfNow8hg8-?/||*n1/>e7f9~'ForH %-c&L3X
- ~}9G\Zvnt7C0:?-LNrL'Ag7uuN :_FIWD0x)4 4^pTY~ ,w mGG:0b]PN%#0Q4#XJy$u;N@=wzS~&7h~SBD@.;Vw.Q
-gb"r316_eG-]4 S
-#0 ;LC{1?Tq_º½x Ûtxa„ŒÑ y*;˜E
-J$(
-3V-
-`7 NrXXq
-endobj
-1416 0 obj <<
-/Type /Page
-/Contents 1417 0 R
-/Resources 1415 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 1414 0 R
-/Annots [ 1421 0 R 1422 0 R 1423 0 R 1424 0 R 1425 0 R 1426 0 R 1427 0 R ]
->> endobj
-1421 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [365.77 614.001 539.579 625.993]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://mailhost.cb1.com/~lkcl/cifsntdomain.txt)>>
->> endobj
-1422 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [84.043 600.754 177.671 612.444]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://mailhost.cb1.com/~lkcl/cifsntdomain.txt)>>
->> endobj
-1423 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [94.952 410.763 520.758 422.755]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://ntbugtraq.rc.on.ca/SCRIPTS/WA.EXE?A2=ind9708;L=ntbugtraq;O=A;P=2935)>>
->> endobj
-1424 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [94.952 397.213 326.033 409.206]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://mailhost.cb1.com/~lkcl/crypt.html)>>
->> endobj
-1425 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [281.346 383.967 357.854 395.657]
-/Subtype/Link/A<</Type/Action/S/URI/URI(mailto:linus@incolumitas.se)>>
->> endobj
-1426 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [94.952 370.115 435.348 382.108]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://samba.org/cgi-bin/mfs/01/digest/1997/97aug/0391.html)>>
->> endobj
-1427 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [94.952 356.566 320.306 368.558]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://mailhost.cb1.com/~lkcl/crypt.txt)>>
->> endobj
-1418 0 obj <<
-/D [1416 0 R /XYZ 85.039 781.388 null]
->> endobj
-250 0 obj <<
-/D [1416 0 R /XYZ 85.039 761.463 null]
->> endobj
-1419 0 obj <<
-/D [1416 0 R /XYZ 85.039 673.255 null]
->> endobj
-254 0 obj <<
-/D [1416 0 R /XYZ 85.039 673.255 null]
->> endobj
-1420 0 obj <<
-/D [1416 0 R /XYZ 85.039 644.52 null]
->> endobj
-1428 0 obj <<
-/D [1416 0 R /XYZ 85.039 221.223 null]
->> endobj
-1429 0 obj <<
-/D [1416 0 R /XYZ 85.039 197.66 null]
->> endobj
-1430 0 obj <<
-/D [1416 0 R /XYZ 85.039 177.43 null]
->> endobj
-1431 0 obj <<
-/D [1416 0 R /XYZ 85.039 155.989 null]
->> endobj
-1432 0 obj <<
-/D [1416 0 R /XYZ 85.039 108.661 null]
->> endobj
-1415 0 obj <<
-/Font << /F20 877 0 R /F15 895 0 R /F37 900 0 R /F43 1079 0 R /F36 892 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-1435 0 obj <<
-/Length 2548
-/Filter /FlateDecode
->>
-stream
-xr6_K x>%qMQ;}h
-{I^Dj!a(+ (R
-
- ewS|I;ToK0ox!e#&78f=~DM 8$1#\ ;.-J]^7K#kgVw}{[I6<\,{L,M;6
-x>`]7{xoM.9&.HTqgLu!
-T^(|N}
-OxlM 8'QN_/.xw
-]AMsP<SvZ{9&e L9~ )=d|(.H-qe=lyK#--i""k"mGq\Lj7Q3Xg@&˜€b{s&„2ú¶/ՃƒÈò4u¨ÊÏÙX9&xFq)=ze8p(;LOA7#%oK+~at]cEvz ToyNO^u_P V<r+J#`2q#(h'
-}1g{5,D:9Wf
-q?;Nc<AT(?p X=@XvUhMX{>gJJ\iqdk>E~=(*(E=z dF^b9bfWo'F4a M;GH Ftf`8$
-P >E;}K"3@O =M9endstream
-endobj
-1434 0 obj <<
-/Type /Page
-/Contents 1435 0 R
-/Resources 1433 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 1414 0 R
->> endobj
-1436 0 obj <<
-/D [1434 0 R /XYZ 85.039 781.388 null]
->> endobj
-258 0 obj <<
-/D [1434 0 R /XYZ 85.039 761.463 null]
->> endobj
-1437 0 obj <<
-/D [1434 0 R /XYZ 85.039 743.459 null]
->> endobj
-262 0 obj <<
-/D [1434 0 R /XYZ 85.039 644.976 null]
->> endobj
-1438 0 obj <<
-/D [1434 0 R /XYZ 85.039 626.104 null]
->> endobj
-266 0 obj <<
-/D [1434 0 R /XYZ 85.039 499.35 null]
->> endobj
-1439 0 obj <<
-/D [1434 0 R /XYZ 85.039 472.735 null]
->> endobj
-270 0 obj <<
-/D [1434 0 R /XYZ 85.039 472.735 null]
->> endobj
-1440 0 obj <<
-/D [1434 0 R /XYZ 85.039 451.742 null]
->> endobj
-1441 0 obj <<
-/D [1434 0 R /XYZ 85.039 456.225 null]
->> endobj
-1442 0 obj <<
-/D [1434 0 R /XYZ 85.039 404.49 null]
->> endobj
-1443 0 obj <<
-/D [1434 0 R /XYZ 85.039 368.425 null]
->> endobj
-1444 0 obj <<
-/D [1434 0 R /XYZ 85.039 334.482 null]
->> endobj
-1445 0 obj <<
-/D [1434 0 R /XYZ 85.039 203.572 null]
->> endobj
-1433 0 obj <<
-/Font << /F58 956 0 R /F20 877 0 R /F15 895 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-1448 0 obj <<
-/Length 1182
-/Filter /FlateDecode
->>
-stream
-xXRH+RLHM" ke - UrU} ( S
-#"r> f0D~>HeDSfI>;Xjitw|jg]D|XwLAJM :ODI7_S $q"fhN5^ F&^M8XX)6y,z=SBd[O.{v
-c57T[DiW~h pfKaj.e
-ƒþ¬µýÚý®P( f&7jQl#hi7T3Ip9c>-0
-w <0MY,`T)10CD@ 45omTf, ]=f5V )mvc!e# )%Q,\[ufz67!]g'QEP J"nY lHe=/T*oZ,1ins6 [$F|g@Du±ÑË&ç÷_]€ð˜¶4 G
-6~d;3W#{mOr +w#endstream
-endobj
-1447 0 obj <<
-/Type /Page
-/Contents 1448 0 R
-/Resources 1446 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 1414 0 R
->> endobj
-1449 0 obj <<
-/D [1447 0 R /XYZ 85.039 781.388 null]
->> endobj
-274 0 obj <<
-/D [1447 0 R /XYZ 85.039 761.463 null]
->> endobj
-1450 0 obj <<
-/D [1447 0 R /XYZ 85.039 743.459 null]
->> endobj
-278 0 obj <<
-/D [1447 0 R /XYZ 85.039 743.459 null]
->> endobj
-1451 0 obj <<
-/D [1447 0 R /XYZ 85.039 720.743 null]
->> endobj
-282 0 obj <<
-/D [1447 0 R /XYZ 85.039 600.999 null]
->> endobj
-1452 0 obj <<
-/D [1447 0 R /XYZ 85.039 580.404 null]
->> endobj
-286 0 obj <<
-/D [1447 0 R /XYZ 85.039 368.476 null]
->> endobj
-1453 0 obj <<
-/D [1447 0 R /XYZ 85.039 347.483 null]
->> endobj
-290 0 obj <<
-/D [1447 0 R /XYZ 85.039 347.483 null]
->> endobj
-1454 0 obj <<
-/D [1447 0 R /XYZ 85.039 326.889 null]
->> endobj
-294 0 obj <<
-/D [1447 0 R /XYZ 85.039 298.074 null]
->> endobj
-1455 0 obj <<
-/D [1447 0 R /XYZ 85.039 277.48 null]
->> endobj
-298 0 obj <<
-/D [1447 0 R /XYZ 85.039 248.665 null]
->> endobj
-1456 0 obj <<
-/D [1447 0 R /XYZ 85.039 228.071 null]
->> endobj
-302 0 obj <<
-/D [1447 0 R /XYZ 85.039 182.98 null]
->> endobj
-1457 0 obj <<
-/D [1447 0 R /XYZ 85.039 165.113 null]
->> endobj
-1446 0 obj <<
-/Font << /F58 956 0 R /F20 877 0 R /F15 895 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-1460 0 obj <<
-/Length 1316
-/Filter /FlateDecode
->>
-stream
-xYKo6WVH[vznco/r;h c47qf(3sbI(O(f3u3_;JPGJz?(cQ<hA6t?|6| Lno} >wn[Ktw`Ÿ;”ð$vž M Kg)O;ok-fN8$~%$lF#:oB1y z>s1IJ?~lF*i|n]eY&WrU(eQ@8l`Q%$$x8nf.%!r&”Ͻ vW 'aru8^NE\-d0
-+PuKIIDKD2!\gC P?eDUM|G_pp4[c3BG]V>jhV+F)me~P&}jUNPCz/.i:O 2Ap\
-WSQOFsUd`k%Qt(bR>5&;1M76LV=D$#u`\s‰Ë•Ú/vA=/35A%Bh<`_YflT^ U/]uzT4p' ?\!OsLdt+jVy>#F hin 6m$S5Cq|0<+Ð8Ð?_x„oð,ýËÀ˜D`
-F{W sov^%W,LcZj{@6Q xB.WyO NBI`/9QpN88v8"3Kg=T. A`*p-F+'k]iQRKI}jM{R)LU4kt o==w%Vh)`DB4D@B.ns*Nendstream
-endobj
-1459 0 obj <<
-/Type /Page
-/Contents 1460 0 R
-/Resources 1458 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 1414 0 R
->> endobj
-1461 0 obj <<
-/D [1459 0 R /XYZ 85.039 781.388 null]
->> endobj
-306 0 obj <<
-/D [1459 0 R /XYZ 85.039 761.463 null]
->> endobj
-1462 0 obj <<
-/D [1459 0 R /XYZ 85.039 740.731 null]
->> endobj
-310 0 obj <<
-/D [1459 0 R /XYZ 85.039 587.122 null]
->> endobj
-1463 0 obj <<
-/D [1459 0 R /XYZ 85.039 563.801 null]
->> endobj
-314 0 obj <<
-/D [1459 0 R /XYZ 85.039 534.986 null]
->> endobj
-1464 0 obj <<
-/D [1459 0 R /XYZ 85.039 514.392 null]
->> endobj
-318 0 obj <<
-/D [1459 0 R /XYZ 85.039 431.318 null]
->> endobj
-1465 0 obj <<
-/D [1459 0 R /XYZ 85.039 407.996 null]
->> endobj
-322 0 obj <<
-/D [1459 0 R /XYZ 85.039 345.317 null]
->> endobj
-1466 0 obj <<
-/D [1459 0 R /XYZ 85.039 324.117 null]
->> endobj
-326 0 obj <<
-/D [1459 0 R /XYZ 85.039 283.347 null]
->> endobj
-1467 0 obj <<
-/D [1459 0 R /XYZ 85.039 262.753 null]
->> endobj
-330 0 obj <<
-/D [1459 0 R /XYZ 85.039 199.468 null]
->> endobj
-1468 0 obj <<
-/D [1459 0 R /XYZ 85.039 178.873 null]
->> endobj
-1458 0 obj <<
-/Font << /F58 956 0 R /F20 877 0 R /F15 895 0 R /F36 892 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-1471 0 obj <<
-/Length 1990
-/Filter /FlateDecode
->>
-stream
-xZ[s8~`a/Or)-fu&B:#Yt.+aE a28Khy93T56=P:"r'g#H 1?=8:wkSPs| 'GxQ8\#d =g(V&HF"ru#NGK}]GH'kvHZ75#hXy7/5#~`h8&5?u]:En.p\A/jZ(nYG14U(GNClFkK3Ul_#(+Kz.2vC,OfY~a!j BjRaSWYV
-B@iBVy\A*4N^RCB8Gg>-9
-! k!
-yL[w5qx1P
-|Bh#MR7e>[F.08$MM>K
- ycsg
-\K_s:tm L~\l:X-f6#
-endobj
-1470 0 obj <<
-/Type /Page
-/Contents 1471 0 R
-/Resources 1469 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 1414 0 R
->> endobj
-1472 0 obj <<
-/D [1470 0 R /XYZ 85.039 781.388 null]
->> endobj
-334 0 obj <<
-/D [1470 0 R /XYZ 85.039 761.463 null]
->> endobj
-1473 0 obj <<
-/D [1470 0 R /XYZ 85.039 740.731 null]
->> endobj
-338 0 obj <<
-/D [1470 0 R /XYZ 85.039 593.908 null]
->> endobj
-1474 0 obj <<
-/D [1470 0 R /XYZ 85.039 572.708 null]
->> endobj
-342 0 obj <<
-/D [1470 0 R /XYZ 85.039 534.363 null]
->> endobj
-1475 0 obj <<
-/D [1470 0 R /XYZ 85.039 513.769 null]
->> endobj
-346 0 obj <<
-/D [1470 0 R /XYZ 85.039 348.645 null]
->> endobj
-1476 0 obj <<
-/D [1470 0 R /XYZ 85.039 325.323 null]
->> endobj
-350 0 obj <<
-/D [1470 0 R /XYZ 85.039 224.255 null]
->> endobj
-1477 0 obj <<
-/D [1470 0 R /XYZ 85.039 200.933 null]
->> endobj
-1469 0 obj <<
-/Font << /F58 956 0 R /F20 877 0 R /F15 895 0 R /F36 892 0 R /F43 1079 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-1480 0 obj <<
-/Length 1880
-/Filter /FlateDecode
->>
-stream
-xZKo8WVibEc/EGylviFm;E(|G"!g" vo7=d^
-eu{׺K/>;Ahzg{.OG2 sDvo2EQG*>\tBdjA=ShD^m1ÙÜŒ¶£”kí}†*`äVo]i(N0nW0X\K5V2`+jx%}ViRM pcaB?,Or-*an+nPUf<k2ZEURvPT@9u~
-9'Q"cbR) }
-[yV)%N&+qQ8'NHp?Vq#F|adZFe
-
-..E[^ -@sr=
-!r =6p&)>$&C`b"KMpGaI1Oz/t ]:OK!=1,d!<;I?^\ ní2_yíS\SLoJNxBS5<3s{G TvSISQ`<On strv 5NeFApct Lp N~4g8*_&eHG2Æ¡™FQR`l^?YY%qO5)J2;PE.h+Cg`MyG gXFa#f8Mh4^u5€dN1cU?` `7_`?
-iQUilD@kk `dO6>*@54.`BWg%4vG5YFq$k2jS0R~5v7T/J7kUqG 1Dg+@AyAH2N4 w4p/G3 Lh-
-&qjn^ ^\!Xh!³«žuqüž>îgqš¬_z*|¹´9r
-endobj
-1479 0 obj <<
-/Type /Page
-/Contents 1480 0 R
-/Resources 1478 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 1487 0 R
->> endobj
-1481 0 obj <<
-/D [1479 0 R /XYZ 85.039 781.388 null]
->> endobj
-354 0 obj <<
-/D [1479 0 R /XYZ 85.039 761.463 null]
->> endobj
-1482 0 obj <<
-/D [1479 0 R /XYZ 85.039 740.731 null]
->> endobj
-358 0 obj <<
-/D [1479 0 R /XYZ 85.039 621.561 null]
->> endobj
-1483 0 obj <<
-/D [1479 0 R /XYZ 85.039 600.361 null]
->> endobj
-362 0 obj <<
-/D [1479 0 R /XYZ 85.039 539.126 null]
->> endobj
-1484 0 obj <<
-/D [1479 0 R /XYZ 85.039 517.925 null]
->> endobj
-366 0 obj <<
-/D [1479 0 R /XYZ 85.039 372.869 null]
->> endobj
-1485 0 obj <<
-/D [1479 0 R /XYZ 85.039 350.456 null]
->> endobj
-370 0 obj <<
-/D [1479 0 R /XYZ 85.039 249.785 null]
->> endobj
-1486 0 obj <<
-/D [1479 0 R /XYZ 85.039 227.372 null]
->> endobj
-1478 0 obj <<
-/Font << /F58 956 0 R /F20 877 0 R /F36 892 0 R /F43 1079 0 R /F15 895 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-1490 0 obj <<
-/Length 1505
-/Filter /FlateDecode
->>
-stream
-xYr6}W-dDp%}V.4rj}q<Z-N%!)N
-P[C,#e7O0^Z
-k.T$
-1*&R|keqKC
-8v Z
-i]DreIXqo-7F3qg <=|~3)t-
-ut%hKaJ7MuqY+DU5PS/
-xL".roBXG4 nN!x/$5
-l{#N5wF´‹ä¯F {7 kuXE.o8ô-K>Rxvµß¬뉻Ïû£ž4˒¼¡õT<5%8v I=gM0L<u6TFjOOL /-%COJuyWCER+oR:okm[H`7S 4A ${wP)u.-m *4endstream
-endobj
-1489 0 obj <<
-/Type /Page
-/Contents 1490 0 R
-/Resources 1488 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 1487 0 R
->> endobj
-1491 0 obj <<
-/D [1489 0 R /XYZ 85.039 781.388 null]
->> endobj
-374 0 obj <<
-/D [1489 0 R /XYZ 85.039 688.087 null]
->> endobj
-1492 0 obj <<
-/D [1489 0 R /XYZ 85.039 666.886 null]
->> endobj
-378 0 obj <<
-/D [1489 0 R /XYZ 85.039 404.883 null]
->> endobj
-1493 0 obj <<
-/D [1489 0 R /XYZ 85.039 381.562 null]
->> endobj
-382 0 obj <<
-/D [1489 0 R /XYZ 85.039 318.277 null]
->> endobj
-1494 0 obj <<
-/D [1489 0 R /XYZ 85.039 297.682 null]
->> endobj
-1488 0 obj <<
-/Font << /F58 956 0 R /F20 877 0 R /F15 895 0 R /F36 892 0 R /F37 900 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-1497 0 obj <<
-/Length 1360
-/Filter /FlateDecode
->>
-stream
-xY]s8}Wvg,iK@%; `6a{$&$o]{$S?j8,4`r!|nQ18q<U? &e3Xf?w*}u:Las=svahLZ\0"8qk9Z4$+NK7$.+,[0Z657.fv"ckD%^Lb +`oz tjRLoTn >LJiB-F<QrE'8LG-
-JS241:vB
-L<.{gi+$A uu,@oR !d'/WtR:?@LQ \de
-TB8f Lb0,{CS#>#)% 8^XXmC<F+p~-btY`2]:&?8=+3q>B[{
-0 6z0RUG2xlLDMVN?j>'9KHi$O_~W.Wo<|
-^U5vendstream
-endobj
-1496 0 obj <<
-/Type /Page
-/Contents 1497 0 R
-/Resources 1495 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 1487 0 R
->> endobj
-1498 0 obj <<
-/D [1496 0 R /XYZ 85.039 781.388 null]
->> endobj
-386 0 obj <<
-/D [1496 0 R /XYZ 85.039 761.463 null]
->> endobj
-1499 0 obj <<
-/D [1496 0 R /XYZ 85.039 740.731 null]
->> endobj
-390 0 obj <<
-/D [1496 0 R /XYZ 85.039 567.596 null]
->> endobj
-1500 0 obj <<
-/D [1496 0 R /XYZ 85.039 544.274 null]
->> endobj
-1495 0 obj <<
-/Font << /F58 956 0 R /F20 877 0 R /F15 895 0 R /F36 892 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-1503 0 obj <<
-/Length 1584
-/Filter /FlateDecode
->>
-stream
-xZKs6WS
-p ~g&Kkh$
-tCQ6Ù¿¡´¸ùÍpÄ)ý ›Èãi^7(ù¨¼m
->2+¡ô4ÓÑ|£y=ªä…Mgh8eD *,Ke^S^JS;.1 ;qHV `m~.sBreP*${P2G@:*>wZ^1m-zE#dhh`N,;7pLd:i!4P bB0VAsf!S(@ I=L¾Ú–&„9=1ȃ³¦.­9—VIM{H^E}LT'EvU< pH 
-Z*03tvS\zX<
-endobj
-1502 0 obj <<
-/Type /Page
-/Contents 1503 0 R
-/Resources 1501 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 1487 0 R
->> endobj
-1504 0 obj <<
-/D [1502 0 R /XYZ 85.039 781.388 null]
->> endobj
-394 0 obj <<
-/D [1502 0 R /XYZ 85.039 372.262 null]
->> endobj
-1505 0 obj <<
-/D [1502 0 R /XYZ 85.039 351.668 null]
->> endobj
-398 0 obj <<
-/D [1502 0 R /XYZ 85.039 125.402 null]
->> endobj
-1506 0 obj <<
-/D [1502 0 R /XYZ 85.039 104.202 null]
->> endobj
-1501 0 obj <<
-/Font << /F58 956 0 R /F20 877 0 R /F15 895 0 R /F36 892 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-1509 0 obj <<
-/Length 1839
-/Filter /FlateDecode
->>
-stream
-x[S8_gjU 4\B-`C2 I_ZI
-sibVi+CX'P d5 baXmTpZ=Bl\E"$Jw:iToc tr\;lo-kg8>+_qg#&HYp+tW[%xYH$(KqQ!*]O>\8MXrPYC~j6\p )T_iLLIyaQ%
-ni#ARc!
-,3A E0QXss#J'depF<^4v^e}!x(^rhG8{G
-2Q>0&-h?2Sej6LW z j NQT;`V1|} \!+AFJxr}}Gj)A6MQ:[x3UmI9/r{T?qw =FX"]sb^^i@';LK]n6tJDk!X@/\y
-ue|<(E1vcmz\3(Yh-N1)z$gHd%6Xq4q}4Nw`p=)N{ ttI]'I!(x{4L]LOy'xh^H=3l@RM{r®¡ #õB)3B #VcZNRv6LX?
-V2'Gn<9`f3+EByhe8"hQ&+"$ -= 3?wQ[|G5NQBUhq#D
-[21W.*(P'i_LL?jztaxk2gn<endstream
-endobj
-1508 0 obj <<
-/Type /Page
-/Contents 1509 0 R
-/Resources 1507 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 1487 0 R
->> endobj
-1510 0 obj <<
-/D [1508 0 R /XYZ 85.039 781.388 null]
->> endobj
-402 0 obj <<
-/D [1508 0 R /XYZ 85.039 761.463 null]
->> endobj
-1511 0 obj <<
-/D [1508 0 R /XYZ 85.039 743.459 null]
->> endobj
-406 0 obj <<
-/D [1508 0 R /XYZ 85.039 457.432 null]
->> endobj
-1512 0 obj <<
-/D [1508 0 R /XYZ 85.039 438.958 null]
->> endobj
-1507 0 obj <<
-/Font << /F58 956 0 R /F20 877 0 R /F15 895 0 R /F40 1163 0 R /F36 892 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-1515 0 obj <<
-/Length 2890
-/Filter /FlateDecode
->>
-stream
-xZYsF~`j-fQZ"!kdPo38P\J%13I:p="Rdq `
-|,P gGg(rHFB*?
-CK o7X0b^Vsd_E$wv~V6SD
-<7#Fclb^6)yi0 77
-iujU%|LyaOs<$EBJ6jLMauUYh6~NCDJ
-AF;Z1VJ^)K IOM @:Yrv*-n
- "[n m"$m4zx3-7Fz6N$n<t=(?alN3
-R<n7jcF
-<`B6^XuFbA-JY>6+pI ;<G($da+>}W|d^",UE$#,q(
-wU_.G0Ol
-<Z6N
-`u<R~^K C?}B\)J8iOA^K8_uEVAo*&J<b`&[pRY2mF@{>cSMqXG<_Y~KCK9
-NNv63h‰»œÛ¥ç9¯¶ò〜ύãÁGM*{~}h
-[vJx
-`%vdR3px}cS7&
-Zis="+l.q$,yER N
-h&#P>J$5-+dkE{% x%OP=>A5A=W
-Bx6'($%Uf+=YN#<OQ6R{N, V]r7rm$}0Yf
-6D9v,&MUm4k}/jaYe~*#f@fi2GAgr7
-8al9udRBj`TL<:4N*Z^a_xTaI'v4u4gSTC`.'k®Èu`¶J
-:^D8PP2oFqT2nE16e]o- p[MWu[O*f9l;s%PJO*z~)~B&endstream
-endobj
-1514 0 obj <<
-/Type /Page
-/Contents 1515 0 R
-/Resources 1513 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 1487 0 R
->> endobj
-1516 0 obj <<
-/D [1514 0 R /XYZ 85.039 781.388 null]
->> endobj
-410 0 obj <<
-/D [1514 0 R /XYZ 85.039 410.554 null]
->> endobj
-1517 0 obj <<
-/D [1514 0 R /XYZ 85.039 381.755 null]
->> endobj
-414 0 obj <<
-/D [1514 0 R /XYZ 85.039 353.62 null]
->> endobj
-1518 0 obj <<
-/D [1514 0 R /XYZ 85.039 332.423 null]
->> endobj
-1513 0 obj <<
-/Font << /F58 956 0 R /F20 877 0 R /F15 895 0 R /F43 1079 0 R /F37 900 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-1521 0 obj <<
-/Length 2651
-/Filter /FlateDecode
->>
-stream
-xZ[wH~+7} C@3gKq4\oUW,I`8_[bD>*`*La[f<K?b8xd|n8RJy1ŽÂ0òŽÇ”ÿ÷Û7ώŽ)ýîäÅ¿N;S49|),T @Zvk1REn$-%Ch/Hx w1= ~)ti469[ VWgV6B6^r9+"` \P=5VYPd21 _<;9B9 a'Qc^'u3FD"H?YYgXb6{=^c(Su9DIw;Uc.q \h<*,TlE`+&)7yNfiUMV0mdd*1S+eTa[,Lp=I! (]}2 #-#uA %YS"*(djWTz>Ab+_=]+HD`12 ">r\}YfuB RLkPjTGs:GQV.6B.tjGV#_Mh:fH{gb+XYQl^am>$)gXH&XIU A*o|W6&<:"ÉÀº<Ôöb’ØùÁN?r) (
-X~ddK5LYRndp 3TiTbk;uMI&pb+RQ9qREf%@v& 1:!qrdmmVUk-4K/S$UicA*T$i,AIoF]tK#)_>po{LK5w9\b5?^F:kpOz]Aq;i{<]k9 `'g(v|cV D7UL6%}^@;/xGȄ/ 2Š÷—óT9T5AEHDB].zmLLT+#4mHIS?B\W
-T5t?rD!*:1q>W2+h5v1_U2?K\ 3nS\bìà…«¾ùÈw¸ò¨ù ;! áà|³ö ÔØE{GaK'sL5020thT7Z l$
-nzHjid"J5 '`NCJI_>c=g}R##|@{%PFU%I$YOfYU~:LV_Pb}s0S3 "!C{n^Z56J_4`G!:tRI}p=s
-)Z7cVth
-endobj
-1520 0 obj <<
-/Type /Page
-/Contents 1521 0 R
-/Resources 1519 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 1525 0 R
->> endobj
-1522 0 obj <<
-/D [1520 0 R /XYZ 85.039 781.388 null]
->> endobj
-418 0 obj <<
-/D [1520 0 R /XYZ 85.039 601.341 null]
->> endobj
-1523 0 obj <<
-/D [1520 0 R /XYZ 85.039 580.348 null]
->> endobj
-422 0 obj <<
-/D [1520 0 R /XYZ 85.039 277.822 null]
->> endobj
-1524 0 obj <<
-/D [1520 0 R /XYZ 85.039 257.834 null]
->> endobj
-1519 0 obj <<
-/Font << /F58 956 0 R /F15 895 0 R /F43 1079 0 R /F37 900 0 R /F20 877 0 R /F36 892 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-1528 0 obj <<
-/Length 1854
-/Filter /FlateDecode
->>
-stream
-xYYoF~07{r6>y%Z&*QH9}g/(s1j1JSXGB- G7'B F+e4~?8:>øŒ1/B? w:2|8|wj~}<z}><z;H)7?ka"1"Q`HpfyN|'hW~#x/ +>U<N R$j6+1XoSEr *rNQK^a.f)^=% 'd
-bN\ unjL\NulM6^g< ?2Hd$4xqs]u[K33Vg9aLp}b|x , *@ 2OL28$8T N$uF*dU*o1/ ("GXF
-(]p lbT!|<v,s`6yHm,n-AO@l
-yrjO~Uh/XVfEkPB}=`mh0G-N_'$Y"
-lSpv e
-g/V**@Sv$8'xl¸/åÁ·1&=0¸†–‹¾Ji0Y vf9U v9
-fmc^+%FUbJ,=(xG+U^)uM|k[6/[KZH EU|f)~xyK@YM;*{{l UQlmQff<b!!A\[aGJ$[xfp
-aVu]6%[WC*-.*k ]a4r]@  4[UU(irZ2Jg-UtgOWv]M
-v(:oBH-wrNlx?U7@Q$,0{H8dT/B34.`u91* Z$ ^$^A$> %PC=|7Vp1\vL(endstream
-endobj
-1527 0 obj <<
-/Type /Page
-/Contents 1528 0 R
-/Resources 1526 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 1525 0 R
->> endobj
-1529 0 obj <<
-/D [1527 0 R /XYZ 85.039 781.388 null]
->> endobj
-426 0 obj <<
-/D [1527 0 R /XYZ 85.039 761.463 null]
->> endobj
-1530 0 obj <<
-/D [1527 0 R /XYZ 85.039 743.459 null]
->> endobj
-430 0 obj <<
-/D [1527 0 R /XYZ 85.039 635.092 null]
->> endobj
-1531 0 obj <<
-/D [1527 0 R /XYZ 85.039 614.498 null]
->> endobj
-434 0 obj <<
-/D [1527 0 R /XYZ 85.039 551.405 null]
->> endobj
-1532 0 obj <<
-/D [1527 0 R /XYZ 85.039 528.689 null]
->> endobj
-438 0 obj <<
-/D [1527 0 R /XYZ 85.039 281.19 null]
->> endobj
-1533 0 obj <<
-/D [1527 0 R /XYZ 85.039 262.717 null]
->> endobj
-442 0 obj <<
-/D [1527 0 R /XYZ 85.039 197.503 null]
->> endobj
-1534 0 obj <<
-/D [1527 0 R /XYZ 85.039 179.03 null]
->> endobj
-1526 0 obj <<
-/Font << /F58 956 0 R /F20 877 0 R /F15 895 0 R /F37 900 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-1537 0 obj <<
-/Length 2527
-/Filter /FlateDecode
->>
-stream
-xZmo8_at?}XHJbCuM{@[IkiYNpR!@De83gHS
- Y6,N
-F~<Q~!C/'O@IŒ/iÊxú~øò?Ïߍ_"­õЉQt~Sn{O'-"#LqO'?D
-ghK,N''mI"c3`,Rdc@6=z 3+If.(fLflV_fj Q 7 1p]^30B/K+EJBJ=b`2q]t&q
-@>|`ILtr.9l:*Ö<²‚|:Åáòê{^_å³z*œ\sß9¼¿yÁk¼’qah­wôeœˆá,P]*a3nB% B?v&8mBb^s=y,wODI~ b}O9djN .)qJ:=6
-yY]kY_WH0vWZx/;jO9HgX p(w#i|w_/~a kz7`B3b^0qz>6E:p0s6 MhOɯ;‚' /0AT}bg[ 
-E+2p|_e7uY_uq4?Q(` ]5}Tz=UM")zssyG
- #iF7>]
-{QMwn|T"clXu"xi=zOi4Z]5B_iVL2cX1@a~fuJ?`f@xKa[qH FNMg+_s:AO9}5t{ ?IA <P1/gG*2/H!AmE0Y:
-v^cLX~|^kf:
-w?|DGT:%t4z]|. mg(1
-g8s+L74Um-^¿'E\lG)dI#“«(Êrú¦P+pMQN>=:;>/e3+kLyrYqs-PVnXmJ6
-dR<K
-ju%])OwàëŒÄ*HzI^OpTnML}&,:e $W=1`kQ,.o#=_jHQ zhTy=,z: [X"++"o_2{K09`|@`~q-{iox2<[K  jwk3I'<53< !5{U$>d\wQJ"F=#wo m+.] .V6<|:a15/%khQB=`{gdY\z[|(i8+
-<7Ik'^{A3dyx eUC` B,;w<:n] >$t&E= 1on#TY:
- rTyr\$Y7fpHwOE: z2V'wN UodNs4l3e_^B\TJoA1v{~?p(.6Mä÷ëÐØÝa÷‡ÿýB*endstream
-endobj
-1536 0 obj <<
-/Type /Page
-/Contents 1537 0 R
-/Resources 1535 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 1525 0 R
->> endobj
-1538 0 obj <<
-/D [1536 0 R /XYZ 85.039 781.388 null]
->> endobj
-446 0 obj <<
-/D [1536 0 R /XYZ 85.039 643.264 null]
->> endobj
-1539 0 obj <<
-/D [1536 0 R /XYZ 85.039 622.67 null]
->> endobj
-450 0 obj <<
-/D [1536 0 R /XYZ 85.039 486.952 null]
->> endobj
-1540 0 obj <<
-/D [1536 0 R /XYZ 85.039 469.084 null]
->> endobj
-454 0 obj <<
-/D [1536 0 R /XYZ 85.039 336.481 null]
->> endobj
-1541 0 obj <<
-/D [1536 0 R /XYZ 85.039 317.609 null]
->> endobj
-458 0 obj <<
-/D [1536 0 R /XYZ 85.039 240.984 null]
->> endobj
-1542 0 obj <<
-/D [1536 0 R /XYZ 85.039 217.002 null]
->> endobj
-1535 0 obj <<
-/Font << /F58 956 0 R /F20 877 0 R /F15 895 0 R /F43 1079 0 R /F36 892 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-1545 0 obj <<
-/Length 1726
-/Filter /FlateDecode
->>
-stream
-xZmo6_a&5K$[h7m? d;ov-
-$_N]n( „Œð0쎦Ú½†7fO u4z-.DQ^#s?<t{sGs>4'ees:\DOs]wJ
-L S;O:]sIO(qJPDH Qh kc2s`}2'g.s-t<INM1TCN3XT
-&[D]~
-
-'6wF/n&@|=MeDQ#y./MY\9|=6KgSCc-Ge<FHx^qg3O)Yk{2>`*XenWy0b ppZoz0H<F^7HS<>h?oIDrXOKai Gkk'aL.BldRl*:Wl$|c<R"XQP|DN$%I] !B3ccT }N7IlV)v#T=h6(Pg ."'922ZLfr"-[xIYr,9h.1n[E}>&i1P +,f@hp@n&=fV 1{XpTJ;G*#'1-nFF4L qL5g I:'HS7%ESVBCwf8xB823eb|GxQN91;4$iX;W<;]92_
- Qpw8$8Omi&C|92_YI^XVfQk[Jx[/k Q._Z)~ 4t!O^gBX!Kco"i$/~ i2x8bm2p`Wfo%[W Zxe"f]}[[F*o.Ou&\x 8hB0*Q(+(q%DTMxRuX;fs]"YgyesYQ ]M#MMN }i,i8%AM,XHX?mp78A} NZRn^tti mp&D:
-T$ ?c9
-endobj
-1544 0 obj <<
-/Type /Page
-/Contents 1545 0 R
-/Resources 1543 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 1525 0 R
->> endobj
-1546 0 obj <<
-/D [1544 0 R /XYZ 85.039 781.388 null]
->> endobj
-462 0 obj <<
-/D [1544 0 R /XYZ 85.039 493.545 null]
->> endobj
-1547 0 obj <<
-/D [1544 0 R /XYZ 85.039 470.227 null]
->> endobj
-466 0 obj <<
-/D [1544 0 R /XYZ 85.039 97.038 null]
->> endobj
-1548 0 obj <<
-/D [1544 0 R /XYZ 85.039 73.72 null]
->> endobj
-1543 0 obj <<
-/Font << /F58 956 0 R /F20 877 0 R /F43 1079 0 R /F15 895 0 R /F36 892 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-1551 0 obj <<
-/Length 1323
-/Filter /FlateDecode
->>
-stream
-xXmOF~*^"PrG$;_}TwfA
-gv3$TVJYGK%Nzo%! B/wNSB!q Pv?2i9sFh
-#/=JDhS<)DzSg]HfBrEt2lr7$8 s\)}^O
-"pB<"pH[ Vyt%1zaS}1n6aS Hta_r??MM3]bb:'Z(C:-\poHH
-O]0He}9\8:&X2K Pzp$l.vA=:=2s2;h\6q9]oZ]0\S#Wb3eXSDD?6"KRv/Txe0iZ543CXw0 P?-
-\M^Li]HK[sh9 6$eKh"q9"w@YbB.(4?\jBs !Rj#{:4?$\|80qq(kQYk~M3qQC6PRnbdAQy 6I>y$D¹AB
-endobj
-1550 0 obj <<
-/Type /Page
-/Contents 1551 0 R
-/Resources 1549 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 1525 0 R
->> endobj
-1552 0 obj <<
-/D [1550 0 R /XYZ 85.039 781.388 null]
->> endobj
-470 0 obj <<
-/D [1550 0 R /XYZ 85.039 761.463 null]
->> endobj
-1553 0 obj <<
-/D [1550 0 R /XYZ 85.039 741.337 null]
->> endobj
-474 0 obj <<
-/D [1550 0 R /XYZ 85.039 645.559 null]
->> endobj
-1554 0 obj <<
-/D [1550 0 R /XYZ 85.039 622.843 null]
->> endobj
-478 0 obj <<
-/D [1550 0 R /XYZ 85.039 568.877 null]
->> endobj
-1555 0 obj <<
-/D [1550 0 R /XYZ 85.039 545.559 null]
->> endobj
-482 0 obj <<
-/D [1550 0 R /XYZ 85.039 517.707 null]
->> endobj
-1556 0 obj <<
-/D [1550 0 R /XYZ 85.039 497.113 null]
->> endobj
-486 0 obj <<
-/D [1550 0 R /XYZ 85.039 440.419 null]
->> endobj
-1557 0 obj <<
-/D [1550 0 R /XYZ 85.039 420.43 null]
->> endobj
-490 0 obj <<
-/D [1550 0 R /XYZ 85.039 223.846 null]
->> endobj
-1558 0 obj <<
-/D [1550 0 R /XYZ 85.039 202.853 null]
->> endobj
-494 0 obj <<
-/D [1550 0 R /XYZ 85.039 202.853 null]
->> endobj
-1559 0 obj <<
-/D [1550 0 R /XYZ 85.039 180.137 null]
->> endobj
-498 0 obj <<
-/D [1550 0 R /XYZ 85.039 154.203 null]
->> endobj
-1560 0 obj <<
-/D [1550 0 R /XYZ 85.039 131.487 null]
->> endobj
-1549 0 obj <<
-/Font << /F58 956 0 R /F20 877 0 R /F15 895 0 R /F43 1079 0 R /F36 892 0 R /F37 900 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-1563 0 obj <<
-/Length 1264
-/Filter /FlateDecode
->>
-stream
-xYKoFW,kr-Fbk!zz I}gv(YI( "'0|2TEiG/QfigE3}4#L.7GI=KRl@n/'Wf*qY iGŌVe{w~Bc:U5KSmWBg%"Ij OGuqJ3jXh+jGLJshWl]S)$eL;$L|Z|^-rU^#I&mR:NKheR ( M
-9 6y '+/Wke{(De#!s8OqiIq}Sx}Hw5:m1G$Rc9|bZ1)YXf"1n4Nk`PosLm_r&eW9ECaIHv,\6"?{v'^bSr]a`&%!}b!G)S
-#PyCq
-N!NQ(E2WZ r9[SdEd1a$A1*RLz xMR!! '!R7
-[A1ekf1)_8)s+D8]I=0_Ce gfL=Fw&c|* /7{endstream
-endobj
-1562 0 obj <<
-/Type /Page
-/Contents 1563 0 R
-/Resources 1561 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 1525 0 R
->> endobj
-1564 0 obj <<
-/D [1562 0 R /XYZ 85.039 781.388 null]
->> endobj
-502 0 obj <<
-/D [1562 0 R /XYZ 85.039 761.463 null]
->> endobj
-1565 0 obj <<
-/D [1562 0 R /XYZ 85.039 741.134 null]
->> endobj
-506 0 obj <<
-/D [1562 0 R /XYZ 85.039 741.134 null]
->> endobj
-1566 0 obj <<
-/D [1562 0 R /XYZ 85.039 720.743 null]
->> endobj
-510 0 obj <<
-/D [1562 0 R /XYZ 85.039 694.05 null]
->> endobj
-1567 0 obj <<
-/D [1562 0 R /XYZ 85.039 671.334 null]
->> endobj
-514 0 obj <<
-/D [1562 0 R /XYZ 85.039 517.119 null]
->> endobj
-1568 0 obj <<
-/D [1562 0 R /XYZ 85.039 496.126 null]
->> endobj
-518 0 obj <<
-/D [1562 0 R /XYZ 85.039 496.126 null]
->> endobj
-1569 0 obj <<
-/D [1562 0 R /XYZ 85.039 473.41 null]
->> endobj
-522 0 obj <<
-/D [1562 0 R /XYZ 85.039 432.64 null]
->> endobj
-1570 0 obj <<
-/D [1562 0 R /XYZ 85.039 412.046 null]
->> endobj
-526 0 obj <<
-/D [1562 0 R /XYZ 85.039 347.893 null]
->> endobj
-1571 0 obj <<
-/D [1562 0 R /XYZ 85.039 324.575 null]
->> endobj
-530 0 obj <<
-/D [1562 0 R /XYZ 85.039 295.965 null]
->> endobj
-1572 0 obj <<
-/D [1562 0 R /XYZ 85.039 275.37 null]
->> endobj
-1561 0 obj <<
-/Font << /F58 956 0 R /F20 877 0 R /F15 895 0 R /F36 892 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-1575 0 obj <<
-/Length 1193
-/Filter /FlateDecode
->>
-stream
-xZsF[Nuoq8`H_? 7L {$a&C0n.f?Pa(fD7: v~zPoU1J 5 77g~
-!|C0b7^_0no; $R ssK1C0\ST()igc>UI!zmC2k}9A3Fx*E~P2QY\HR J$7uH@w
-Bcq|v7Z\nPy[Caïdªæãy–Lf5 6.+3%` XX"!D1
-D]5WzxgTd+%->P&K-ptIzQQ[;9Q:sofE"A 3Ogjn= ²i‚0ÁêÝmÖZc-7S
-"JE 1d6 FI9:~(=B> 2(T]Wy3CGuI>KjOp$C E<w'/Aq@HngD6'+wab(n5Ae7wmXU`,&1V%LRDC,N*j28?~a[d{c
-o-5R3.|L\4$j6NNpw)7Uj<p1a{ ~ >zP,qmL2PY"K^dO-V# n|B]b?Tf o힣I \P%* \T7<ZrV>+BdiyUmY|46zT1 %T1 "VmilOnOE7luO632Zw9^34m9;sOy.PE 3io8_ 4Q%la!endstream
-endobj
-1574 0 obj <<
-/Type /Page
-/Contents 1575 0 R
-/Resources 1573 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 1581 0 R
->> endobj
-1576 0 obj <<
-/D [1574 0 R /XYZ 85.039 781.388 null]
->> endobj
-534 0 obj <<
-/D [1574 0 R /XYZ 85.039 761.463 null]
->> endobj
-1577 0 obj <<
-/D [1574 0 R /XYZ 85.039 741.337 null]
->> endobj
-538 0 obj <<
-/D [1574 0 R /XYZ 85.039 564.607 null]
->> endobj
-1578 0 obj <<
-/D [1574 0 R /XYZ 85.039 541.289 null]
->> endobj
-542 0 obj <<
-/D [1574 0 R /XYZ 85.039 512.678 null]
->> endobj
-1579 0 obj <<
-/D [1574 0 R /XYZ 85.039 492.084 null]
->> endobj
-546 0 obj <<
-/D [1574 0 R /XYZ 85.039 315.615 null]
->> endobj
-1580 0 obj <<
-/D [1574 0 R /XYZ 85.039 295.626 null]
->> endobj
-1573 0 obj <<
-/Font << /F58 956 0 R /F20 877 0 R /F15 895 0 R /F36 892 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-1584 0 obj <<
-/Length 1995
-/Filter /FlateDecode
->>
-stream
-xYYsF~`eSep+c.NFdr
-
-$'K6.lIYôU6
-.mR,*g+pU0p8Dp%z;J$[l0P"eh$ fUF_!/.7" 6(fg38I"`? zpW 7o rFh#2v:.w#3ktuMdp?wvVka'M8TR[fN9-8&+i^-;G$Nkt{uUnunC`L'Cm7V9ZugN2 wa-.|~B4V NWb{D#tÙ»Bsc #v~&C7O):~&N.zy 3n"v ( @ADw3g% qoxd<`$*&y6#E
- 3?SzBq{kR5tRa{%NjP 2KR
-sFpm=Iq!D
- z
-xfOAlX6s)}Z}G[p
-L:'ECuY"~(7^,3w Z`7Zkr@dY6H^/AghGqhs>= i|c:hXr~YOLg Oo* 
-?=@- cr0U(:;j!;pe+G
-endobj
-1583 0 obj <<
-/Type /Page
-/Contents 1584 0 R
-/Resources 1582 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 1581 0 R
->> endobj
-1585 0 obj <<
-/D [1583 0 R /XYZ 85.039 781.388 null]
->> endobj
-550 0 obj <<
-/D [1583 0 R /XYZ 85.039 761.463 null]
->> endobj
-1586 0 obj <<
-/D [1583 0 R /XYZ 85.039 736.911 null]
->> endobj
-554 0 obj <<
-/D [1583 0 R /XYZ 85.039 356.436 null]
->> endobj
-1587 0 obj <<
-/D [1583 0 R /XYZ 85.039 335.239 null]
->> endobj
-558 0 obj <<
-/D [1583 0 R /XYZ 85.039 238.63 null]
->> endobj
-1588 0 obj <<
-/D [1583 0 R /XYZ 85.039 218.642 null]
->> endobj
-562 0 obj <<
-/D [1583 0 R /XYZ 85.039 114.582 null]
->> endobj
-1589 0 obj <<
-/D [1583 0 R /XYZ 85.039 94.594 null]
->> endobj
-1582 0 obj <<
-/Font << /F58 956 0 R /F20 877 0 R /F15 895 0 R /F43 1079 0 R /F36 892 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-1592 0 obj <<
-/Length 1994
-/Filter /FlateDecode
->>
-stream
-xr6]_R
-Ah\'mI4v<0mqlQ
-b$RMf, id440Q4MW9&!2m4UR2^\:;7/yF~uo~q>{/ wtd4R8&57-O'bbk;qe+vXb<=[+']z'M=+ou&uFwpM0"5)\Yb}_^,|li=)
-'I| ^:I
-::/ :u:g=D
-
-endobj
-1591 0 obj <<
-/Type /Page
-/Contents 1592 0 R
-/Resources 1590 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 1581 0 R
->> endobj
-1593 0 obj <<
-/D [1591 0 R /XYZ 85.039 781.388 null]
->> endobj
-566 0 obj <<
-/D [1591 0 R /XYZ 85.039 761.463 null]
->> endobj
-1594 0 obj <<
-/D [1591 0 R /XYZ 85.039 743.459 null]
->> endobj
-570 0 obj <<
-/D [1591 0 R /XYZ 85.039 658.326 null]
->> endobj
-1595 0 obj <<
-/D [1591 0 R /XYZ 85.039 637.732 null]
->> endobj
-574 0 obj <<
-/D [1591 0 R /XYZ 85.039 528.809 null]
->> endobj
-1596 0 obj <<
-/D [1591 0 R /XYZ 85.039 508.821 null]
->> endobj
-578 0 obj <<
-/D [1591 0 R /XYZ 85.039 422.153 null]
->> endobj
-1597 0 obj <<
-/D [1591 0 R /XYZ 85.039 401.16 null]
->> endobj
-582 0 obj <<
-/D [1591 0 R /XYZ 85.039 275.38 null]
->> endobj
-1598 0 obj <<
-/D [1591 0 R /XYZ 85.039 254.785 null]
->> endobj
-586 0 obj <<
-/D [1591 0 R /XYZ 85.039 190.894 null]
->> endobj
-1599 0 obj <<
-/D [1591 0 R /XYZ 85.039 170.905 null]
->> endobj
-590 0 obj <<
-/D [1591 0 R /XYZ 85.039 104.632 null]
->> endobj
-1600 0 obj <<
-/D [1591 0 R /XYZ 85.039 83.435 null]
->> endobj
-1590 0 obj <<
-/Font << /F58 956 0 R /F20 877 0 R /F36 892 0 R /F15 895 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-1603 0 obj <<
-/Length 1646
-/Filter /FlateDecode
->>
-stream
-xXYoF~[%(GN,9/i`0m Hr)eqQEcvVqm(
-l+yk[GOME<O/t;z>|5 |om4rrx<&w!L
-e|}sPE3O0LDQF1U5_&[.tE"i:mi6fbý³äÃ&)ÊÃ$Rtjc6 ]Vd2|y[(2MNONw[& D0xu'DpuANxId/Eo /Gyr['? dfFR Tu*0]&"soV}`<ø2ôf›U`P&B8[VEBGLJF
-)P Y +Cw@X9U4^i)yX2< joqn`h6u,T|C%@ / h
-3 i5aekx<f9">}OrvMcIhHY\.+OFgPNSpig&Os+mK—Òp7€8ÍR$Zr"r2[JH+4ZfWYZq™å+°*P2ytu@
-=Rn)|QCXcE? -1'`AZi 5fIQ8.-&tG,Iev.kfEZq[Prd_CivH6aS\pz>^L_9kp]'x(#
-bV 8v)V&2JK;3$d$4Dld9eP`S3fiJH/'%}i2
-,lW9BdEu`'rR3"; Bv##y$#AJ]WX\U9`pkA~{-kUOP5o0YdW|\d+&*h-:45C2t
-{7d)[{/e|5|+C"IShw#[Q#N;Y@VJ:x2.
-%=,}N8ug@
-Il@U{sJY,P4%1[C@X6^"\mc`b;(SPD
-qO#W\g;4.
-;Mv=f
-:endstream
-endobj
-1602 0 obj <<
-/Type /Page
-/Contents 1603 0 R
-/Resources 1601 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 1581 0 R
->> endobj
-1604 0 obj <<
-/D [1602 0 R /XYZ 85.039 781.388 null]
->> endobj
-594 0 obj <<
-/D [1602 0 R /XYZ 85.039 761.463 null]
->> endobj
-1605 0 obj <<
-/D [1602 0 R /XYZ 85.039 741.337 null]
->> endobj
-598 0 obj <<
-/D [1602 0 R /XYZ 85.039 707.744 null]
->> endobj
-1606 0 obj <<
-/D [1602 0 R /XYZ 85.039 685.028 null]
->> endobj
-602 0 obj <<
-/D [1602 0 R /XYZ 85.039 338.256 null]
->> endobj
-1607 0 obj <<
-/D [1602 0 R /XYZ 85.039 314.938 null]
->> endobj
-606 0 obj <<
-/D [1602 0 R /XYZ 85.039 273.465 null]
->> endobj
-1608 0 obj <<
-/D [1602 0 R /XYZ 85.039 252.87 null]
->> endobj
-610 0 obj <<
-/D [1602 0 R /XYZ 85.039 219.277 null]
->> endobj
-1609 0 obj <<
-/D [1602 0 R /XYZ 85.039 196.561 null]
->> endobj
-614 0 obj <<
-/D [1602 0 R /XYZ 85.039 119.598 null]
->> endobj
-1610 0 obj <<
-/D [1602 0 R /XYZ 85.039 87.276 null]
->> endobj
-1601 0 obj <<
-/Font << /F58 956 0 R /F20 877 0 R /F15 895 0 R /F37 900 0 R /F36 892 0 R /F43 1079 0 R /F40 1163 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-1613 0 obj <<
-/Length 1314
-/Filter /FlateDecode
->>
-stream
-xYKS8W]i[{caf!#sb9b-<P& *gVw
-,Bi?
-f0D?zO_T0J4A. vzOXji>=bho4:}|-K"a`
-
-V0pcZH*d8zU>.ps^5Sejt9XF'BrogEUA#gK{$Fsgy8"RIs
-NVIEj=B 8G<
-8v>,JL
-tUJd^R3jl=5XUELh)w \D4iL"bJAjU"‹×†ØÝ¥{²äÇç>|î뎣6S\0Zf.dWta?T ~^,b?m%,`Mh>xh mBUlS =8u!Fg}tN^#:4n/O9k~7#2@4iZf){s1Zm
-+.bgU4u05W;;/R,'Y&\IgL}e] M **TiP^J>EU(()GPfYs[2{,eZ q+KQwMTYYULQ.Xf5d frT0$-uXg2šuW g}u8*u8rGx,0X8vq>FHX_&j.wd35[,8!,+[$
-endobj
-1612 0 obj <<
-/Type /Page
-/Contents 1613 0 R
-/Resources 1611 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 1581 0 R
->> endobj
-1614 0 obj <<
-/D [1612 0 R /XYZ 85.039 781.388 null]
->> endobj
-618 0 obj <<
-/D [1612 0 R /XYZ 85.039 761.463 null]
->> endobj
-1615 0 obj <<
-/D [1612 0 R /XYZ 85.039 741.134 null]
->> endobj
-622 0 obj <<
-/D [1612 0 R /XYZ 85.039 698.974 null]
->> endobj
-1616 0 obj <<
-/D [1612 0 R /XYZ 85.039 678.379 null]
->> endobj
-626 0 obj <<
-/D [1612 0 R /XYZ 85.039 482.122 null]
->> endobj
-1617 0 obj <<
-/D [1612 0 R /XYZ 85.039 459.406 null]
->> endobj
-630 0 obj <<
-/D [1612 0 R /XYZ 85.039 260.422 null]
->> endobj
-1618 0 obj <<
-/D [1612 0 R /XYZ 85.039 239.831 null]
->> endobj
-634 0 obj <<
-/D [1612 0 R /XYZ 85.039 170.573 null]
->> endobj
-1619 0 obj <<
-/D [1612 0 R /XYZ 85.039 149.978 null]
->> endobj
-1611 0 obj <<
-/Font << /F58 956 0 R /F20 877 0 R /F36 892 0 R /F15 895 0 R /F43 1079 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-1622 0 obj <<
-/Length 1654
-/Filter /FlateDecode
->>
-stream
-xZMs6WVS$\2$Jj890"mqBQ*I9q~}wRDN-qX
-Xpt s"DPVdc")]9s3]&ife66z'ay(p$ k`lQ\:_OR /E16LSg`1d=7$rut w,d![:bU-'?b,#+=e{0(.w^H]U9
-RJg1zK{(zYM9Yzi !$plb**kS8 4+5vh?@N4hFAvSJ&y &
-UaD[u ÏÛ¸Ý*ö'gÉUa- ?2";c HP_8M5C5}"hxleZI5`v %)M
-4!guLI8!%W]Z4k
-Z4c)DYJN yuAEbU{/CW`4{0iXdzeys_Z70M$;b}!QLM 1AR913l5ZSML]jk
-xzN9WTe ,J2lr'q^li5U-vr?Say=4]o,Qo^+!SiV3Xae)g/)+sEk4:oERig^9T|dXq\3 TlsImZ8fieXT|9/_fveb$n}m!l$w'G*r,WFGQ¢o뜅e'k<“9ύ;rãÃqÿ6Ó
-w¤Œe[€6qøâaX%p<O|dE}SeR3E'sd*VT!Ml'PTlTV/l{DqRB:&XM-+W`xc
-5] ^>TFCa
-_}if›ìí š]¹eRjg;KrAl=LXMss YinY7Wqe?dC/"W|/:S ^`%elg}4 Px7{)
-endobj
-1621 0 obj <<
-/Type /Page
-/Contents 1622 0 R
-/Resources 1620 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 1581 0 R
->> endobj
-1623 0 obj <<
-/D [1621 0 R /XYZ 85.039 781.388 null]
->> endobj
-638 0 obj <<
-/D [1621 0 R /XYZ 85.039 591.485 null]
->> endobj
-1624 0 obj <<
-/D [1621 0 R /XYZ 85.039 568.769 null]
->> endobj
-642 0 obj <<
-/D [1621 0 R /XYZ 85.039 411.417 null]
->> endobj
-1625 0 obj <<
-/D [1621 0 R /XYZ 85.039 379.891 null]
->> endobj
-646 0 obj <<
-/D [1621 0 R /XYZ 85.039 314.138 null]
->> endobj
-1626 0 obj <<
-/D [1621 0 R /XYZ 85.039 293.145 null]
->> endobj
-650 0 obj <<
-/D [1621 0 R /XYZ 85.039 235.379 null]
->> endobj
-1627 0 obj <<
-/D [1621 0 R /XYZ 85.039 215.391 null]
->> endobj
-1620 0 obj <<
-/Font << /F58 956 0 R /F20 877 0 R /F15 895 0 R /F36 892 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-1630 0 obj <<
-/Length 1888
-/Filter /FlateDecode
->>
-stream
-xZ[o6~C">4Bm9$8t$D/~X7„Œð0ìNfv r F2^87a;A:c}s}=u ,\A%NAJxvEEGHN~uZQkh;\vm]NF+}=j7">1JIaRtdNEC0YDHv a> so&K="@hMI r zP8s` :|0 GDU I7:'+]\S" }R%F`kpM YgV
-~W
-
-xNvkOE\W">U)&MahkA
-:Lhn6+a ;Nt6 Ðo‘=ÇC4E mJ)ZNQzmd8af
- 6-FXhp}MBsOHj\m(?0(|ai+k+#Ch>
-endobj
-1629 0 obj <<
-/Type /Page
-/Contents 1630 0 R
-/Resources 1628 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 1638 0 R
->> endobj
-1631 0 obj <<
-/D [1629 0 R /XYZ 85.039 781.388 null]
->> endobj
-654 0 obj <<
-/D [1629 0 R /XYZ 85.039 761.463 null]
->> endobj
-1632 0 obj <<
-/D [1629 0 R /XYZ 85.039 741.337 null]
->> endobj
-658 0 obj <<
-/D [1629 0 R /XYZ 85.039 609.877 null]
->> endobj
-1633 0 obj <<
-/D [1629 0 R /XYZ 85.039 588.884 null]
->> endobj
-662 0 obj <<
-/D [1629 0 R /XYZ 85.039 557.961 null]
->> endobj
-1634 0 obj <<
-/D [1629 0 R /XYZ 85.039 537.366 null]
->> endobj
-666 0 obj <<
-/D [1629 0 R /XYZ 85.039 476.315 null]
->> endobj
-1635 0 obj <<
-/D [1629 0 R /XYZ 85.039 453.599 null]
->> endobj
-670 0 obj <<
-/D [1629 0 R /XYZ 85.039 343.455 null]
->> endobj
-1636 0 obj <<
-/D [1629 0 R /XYZ 85.039 311.93 null]
->> endobj
-674 0 obj <<
-/D [1629 0 R /XYZ 85.039 311.93 null]
->> endobj
-1637 0 obj <<
-/D [1629 0 R /XYZ 85.039 293.727 null]
->> endobj
-1628 0 obj <<
-/Font << /F58 956 0 R /F20 877 0 R /F15 895 0 R /F36 892 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-1641 0 obj <<
-/Length 1313
-/Filter /FlateDecode
->>
-stream
-xWo6_EFeUU`2g+CUbltqawgDÄýñÄs‚ɤŸU==OKqG~KzG:÷“%’äwÖôËYn>A``8OW?]^z>^,eb:(@ßzw÷n?7>ô\'ˆ'ý¬]Njã~Õ £À‰Â@^ >dh$^~}>=Dxcg < f &Ax`h]]V?t4C3t?Vb)MaG3rB_fl%`B=y¹³¿ïbÇñ¢{Ûl]ÇÝۗyŽûifO,<RDaJGA=r+WEJf;bf6S!X#c';\tC!6CAQ uzI$-r^Em Pe?$vEYo$Aa@G $@9UZ/B
-bx* orN~s74A2hF>/pr!V1:=l2$N`m7!B#gX1|L$ymTear*II`_VDx!HRR.qe7n7uruH@>H(F/JXUcJ2yIQ1VwS]4^%uAL ;BH2=
-endobj
-1640 0 obj <<
-/Type /Page
-/Contents 1641 0 R
-/Resources 1639 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 1638 0 R
->> endobj
-1642 0 obj <<
-/D [1640 0 R /XYZ 85.039 781.388 null]
->> endobj
-678 0 obj <<
-/D [1640 0 R /XYZ 85.039 761.463 null]
->> endobj
-1643 0 obj <<
-/D [1640 0 R /XYZ 85.039 743.459 null]
->> endobj
-682 0 obj <<
-/D [1640 0 R /XYZ 85.039 102.539 null]
->> endobj
-1644 0 obj <<
-/D [1640 0 R /XYZ 85.039 81.546 null]
->> endobj
-1639 0 obj <<
-/Font << /F58 956 0 R /F20 877 0 R /F37 900 0 R /F15 895 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-1647 0 obj <<
-/Length 2019
-/Filter /FlateDecode
->>
-stream
-xY[w6~[K
-)Dw+"1~QU!+q1!^Y+!U}$(-A_/O5[IE;n7~'-/)h-{2s
-8Jce@4yMvS^
-|u} .^p,d|f-S:ARE Rg$WuOzzRW(V5f@jSQpuDEFUxmy|j5CA;-r/uU>A {
-<Y4=]"-ROD'U|) +G/ JfbZi\KZ1; l=$wMG>tw F^s&}@&SE1
-endobj
-1646 0 obj <<
-/Type /Page
-/Contents 1647 0 R
-/Resources 1645 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 1638 0 R
->> endobj
-1648 0 obj <<
-/D [1646 0 R /XYZ 85.039 781.388 null]
->> endobj
-686 0 obj <<
-/D [1646 0 R /XYZ 85.039 585.174 null]
->> endobj
-1649 0 obj <<
-/D [1646 0 R /XYZ 85.039 556.439 null]
->> endobj
-690 0 obj <<
-/D [1646 0 R /XYZ 85.039 440.216 null]
->> endobj
-1650 0 obj <<
-/D [1646 0 R /XYZ 85.039 421.95 null]
->> endobj
-694 0 obj <<
-/D [1646 0 R /XYZ 85.039 421.95 null]
->> endobj
-1651 0 obj <<
-/D [1646 0 R /XYZ 85.039 401.356 null]
->> endobj
-698 0 obj <<
-/D [1646 0 R /XYZ 85.039 203.603 null]
->> endobj
-1652 0 obj <<
-/D [1646 0 R /XYZ 85.039 185.736 null]
->> endobj
-1645 0 obj <<
-/Font << /F58 956 0 R /F15 895 0 R /F20 877 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-1655 0 obj <<
-/Length 1530
-/Filter /FlateDecode
->>
-stream
-x[[sF}WVi&}W}K\R
-xLj+ c8Ng%5)Ui,#U6/)
-vz__*d4nMzo?ZN !168V;twW$R S;
-UQ>h z$Y6-SEEbBc6gST#!rb(;=)PqAr8 9rjnI'HC'.hUU|<v<$u|4&LV$xpa`G'] |hJf+FEGo*E80:TR.GOyr V`J\70'seBL*2X
-";
-/]d0PP
-~AElRS'86m
-Xm9 gI=/ w=_%` Q6!+qz*z ?a~L@E6wk}t'%w"$cS67~<Chmn}l:{)=\Ur~Ui7xog{#FrSUi`)#U026Firy
-/HxU!XNbB M!P,M\unU^A[5 5j
-/S,v{}}#wwpq8;- |'3zcPZq k 09`%aRo1_yS](Tx-uz[[R#y'yhej"yq5;lZIpáõ|z¡ˆaø-»ÄÃǒ/c
-£{ÿ3ŽöZ*[ hs(Rendstream
-endobj
-1654 0 obj <<
-/Type /Page
-/Contents 1655 0 R
-/Resources 1653 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 1638 0 R
->> endobj
-1656 0 obj <<
-/D [1654 0 R /XYZ 85.039 781.388 null]
->> endobj
-702 0 obj <<
-/D [1654 0 R /XYZ 85.039 619.934 null]
->> endobj
-1657 0 obj <<
-/D [1654 0 R /XYZ 85.039 601.668 null]
->> endobj
-706 0 obj <<
-/D [1654 0 R /XYZ 85.039 557.183 null]
->> endobj
-1658 0 obj <<
-/D [1654 0 R /XYZ 85.039 538.71 null]
->> endobj
-710 0 obj <<
-/D [1654 0 R /XYZ 85.039 494.225 null]
->> endobj
-1659 0 obj <<
-/D [1654 0 R /XYZ 85.039 473.63 null]
->> endobj
-714 0 obj <<
-/D [1654 0 R /XYZ 85.039 417.718 null]
->> endobj
-1660 0 obj <<
-/D [1654 0 R /XYZ 85.039 399.244 null]
->> endobj
-1653 0 obj <<
-/Font << /F58 956 0 R /F20 877 0 R /F15 895 0 R /F36 892 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-1663 0 obj <<
-/Length 2581
-/Filter /FlateDecode
->>
-stream
-xF}B)`ys8u8 ERcIkc`R3,\/fI Mgm`7J (p0Y]%oC7ho}o{n([["cuW5Clp8/i/5nYNQ^#p$7S*t0>V|07 p6llzr[~;Ci{ vrmE6qr$w)9lvhwxH!GNzUg+7A|s z7+t@ ._|ZDj@{^MGaFu (GtK^OOF2U+S
-*a&Kt2 EpsD(9ldQ/:s]UÄâ;H0`
+>C_lri6 P 6%\^Xe[{KEdK>N+K^~Lk^Wobmts</ <[.fsu>7BPendstream
+endobj
+572 0 obj<</Type/Page/Parent 513 0 R/Contents 573 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+573 0 obj<</Filter/FlateDecode/Length 1775 >>stream
+x}W]O;}çWR*AJ MJ|^U*TJ]oe^B=3U*3g
+
+(MV k=hTsrbpzHR- #yl|kzu~FibEREqq$rvPU[
++x,Eot8Z,'wP5Mx ]=[ pIM6 TnpM2^Bj8 OkT#5Y1vG-K8zi7<U.{,2qEf^l] s&hAEYt~EBP*Kk]Õ9†lÀ¦X lkxxZeAo<nf,[2BUdUp$2C i(vYS)U;%y*T$2eH Ô^U<+LH)e*m$Hp<.]_b"7A !T]HNHZf!6'Z%9L
+e/ 0%!vC @[CX 75`
+.9tN Agol~8[_VRh2 :8;;!vRd(
+c4o0Ty8U0XS4=^AN RlXMmL3SqB:d{a*ArYG!Et#phTU5Q{ T5 ^FOy %
+& :.5(P s71LVd5hrg/Xd 4*-2NtvcBnKkZ7duH_
+.^ fA eiZ`nD$0&tyH J]o+)<u1\/k|2Wt| a'T;[U9`|%ZUKL9Q{Q+6wQid M'6 \v
+G=}x@ 7?N`oTsv4+fMH0cj
+endobj
+574 0 obj<</Type/Page/Parent 513 0 R/Contents 575 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F8 10 0 R>>/XObject<<>>>>>>endobj
+575 0 obj<</Filter/FlateDecode/Length 1041 >>stream
+xmUn6+4lv9&I`C.4HJR6_7j M9oyw4~^z4Kf/-7k|^1yI9 Ym SET|[<Xg P# JRrk~Mc] Fi5d~)SUug4029@%RUm}]PT'J )*Y*+QuQ+`/IRo}$)K9=(])T‹U@{TrTj@;P%Y$ycUS`3[H3o* DG^'5
+#' e+{L[  (
+M r)CYG$Ot=2.sr‹¤h
+ÍU g Ls;Hh8-
+~I&"?|B{q&x-2tWo k|hvCqIU:[u(c>qX\<9@;"|bjDA1H`tDS(`BJ  \[bV
+IagZiaatE,dt URJ8 >< Oa/&0&)\N>0 !"-jJC#;f
+}t9Qft2OVnVz4}d]`J
+xdWpN(8lJHJ' H.BTNMf%a@<Q#UH|kse^mFccOendstream
+endobj
+576 0 obj<</Type/Page/Parent 513 0 R/Contents 577 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F5 7 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+577 0 obj<</Filter/FlateDecode/Length 1533 >>stream
+xWko6_q 8NZ`u Mx %Q6‰ÔH*%)?H}sbJ^/(/>.^}zK JY\x2|V4^Z\ 9QgyYS.\}9Mf<jTH[IG[#o0tf<K2}{O
+O;\
+d8$+!b,`kgr
+"ls?=18r!>} B34z d
+EZk P#P8,
+1.! 9h-HnA^T uH+McIIcLcbk5eSn
+Q~~Iben,o_|1Aafl\endstream
+endobj
+578 0 obj<</Type/Page/Parent 513 0 R/Contents 579 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F8 10 0 R>>/XObject<<>>>>>>endobj
+579 0 obj<</Filter/FlateDecode/Length 815 >>stream
+xTn8|W,
+9G,Vg3Z[2í\G
+Up^ [*v"?'IrpJl#Uz[.hHw@H[m&7YR$ ¤3&ô€¡y¨¨QO}l{hBKxkÙ·ž…£äЙþ¤÷lÙmGXrsGer]lH}kz \!+`i W58}I `ZA;TTk]uA\ dU;
+B >_Ju?6%wfWr{V$,F|w2:ae6zaSizjWU-OO)~:x~F/ &I~2fhl5TaB#H>j8B^]GGQendstream
+endobj
+580 0 obj<</Type/Page/Parent 513 0 R/Contents 581 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F6 8 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>/Annots 301 0 R>>endobj
+581 0 obj<</Filter/FlateDecode/Length 1651 >>stream
+xWmOGK@w>l„*BbWi*Kr{3K{;;` ^m^yfu/.?F]l_%GQ~DvUS8z|6Ev=E'8K'x+>KhHIt^·+>}¾ÆéÑ1n5w7r{xÏöô†G2g?::~= >{?FPF9 Ohg_,EQDwS`J4/_e2l^vGpx$í­ÉëÌ+£››G$qsTr2=;Rznl))yC5+KMx4Q%f+IwHijO~)IK-Ñ¥No$~"-L3[af388eie."iH"kd ,x ] 2<  ^5uE}D8CJ/
+6dn@
+Ol dn )9dlP);JsTPHOwT8a,2Z@V.:s, !T2:-@xy*Z:vš
+´„Ô“MJ4Mf
+2=mXJFfU~iwj!
+(SpQ8A!cbpd`Qt@WkFeZu
+lIU^ _#E(Lt>.wt>vONoO?z[3ôÑҗÅÎ3ØÝ Õ±o@RiM
+xo8[Nt\]M8h(EM)n%41@drXJZY=-f, Uiu]K>m:sdK%W0*`6jY?
+5fO<|0mle2C Lq  l,,Zp@ S$LKvVv?G24 u|X[%RU!U3WgRX%j HZ<T{6=j)*xTt>E" LhiiwWB-lRcv9 Z2pURJb c!H8 @8,(( t$T*JG>
+endobj
+582 0 obj<</Type/Page/Parent 513 0 R/Contents 583 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+583 0 obj<</Filter/FlateDecode/Length 1753 >>stream
+xWMs8WtN[)ORe;D$I v4~_+R_7s54xFE}54]99M| K=&igsZ "PhPF´5d7ôªœ¶­§ZmuA5>(<YGl>*\Z^s H;-),vNGo;6X5{\1E6h:XZ3 \R9}Vj&683m]U{ 9i/vO*g.F|"L8LdwM[0HE9%WvO{xV.9
+|?Zv,a>6~cs<WNa'm@k^LOxAjm_}pfSV0]-tz++C =.Rtq |^k Bo,w&fh@>i/KAn >DL.za'CF }E&+nQvl
+N#V}ioX
+eh WFsUJloY\!{hC<BONv  De[HEe/KZ'OmJ{:<@Ue )cNGD5AepmKe,TK<s4l$H&=<9`poH5 +'b}d=DUzk0;"biae"P.4/i2+>2g,u\h8bzœ»0–8“‚.–ôÀÈfékI{,~{>l?qX<th;dt|Z~"]Su5@^f_zvd|<8FK']p i6toy40E+` 9"^Ewn6aPi} %x!32@6v=]
+jMTNo0 #FGProG*>E>^J`"4
+VDb />8
+l0oEL':E-GD5- |i[R
+endobj
+584 0 obj<</Type/Page/Parent 513 0 R/Contents 585 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F6 8 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+585 0 obj<</Filter/FlateDecode/Length 537 >>stream
+xoo0SK;qxn+Lc(s3AO%nY"w*U=?s ?
+ ,'! 3 ;`!'|2:=+f<C8
+2&% ?Rjf?:Q#)jyw T^(w OX,
+endobj
+586 0 obj<</Type/Page/Parent 513 0 R/Contents 587 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F6 8 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+587 0 obj<</Filter/FlateDecode/Length 701 >>stream
+xUr0+t
+6>|\I> e o\pLT@@ }_<}e>D) (9
+C\|:^^GF[# ,V' d*X yZA%doH<5a#In1l{~R6XEXoImKrZ#0Rh  1|:A~iH|(]VJ~spa=2OgtOMr(2P+*JWFmnrkw5”%ʜ–ZF`|V;iV%bVwPw(QU)!(6D_+{K~<a:G{zZf|C-kK2263U"D'Aqx&U%ERqd>v+q$e^ niq(e?kMWQv\wdnpYW
+U7 WJQti_-7 M‹va4ËbO{-b:ce
+S!, ^]?u6HafQ?c-\A0o'2Qx+W>?endstream
+endobj
+588 0 obj<</Type/Page/Parent 513 0 R/Contents 589 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F6 8 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+589 0 obj<</Filter/FlateDecode/Length 683 >>stream
+xVr0}+tjN_N(c,"iIKagw}r ^
+hzTRJlkt]\pu/(?.8]XLe|?si3/]al 'AE&)JOf)T6RDk6<VXwC5YuoIY2]H|9Z9Gz:KN0 qwBL.qR5_
+> _ N?+CO-endstream
+endobj
+590 0 obj<</Type/Page/Parent 513 0 R/Contents 591 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F6 8 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+591 0 obj<</Filter/FlateDecode/Length 765 >>stream
+xV]O0}& I=1PR62M-K4w"x@H{s=}.y /:] a/tC=*nZnBOEqJ~qo`2Bd nM(m J)J)C,L^
+1Oi0
+L>A825prn2PK%$"5Q*_a ~Hz<.iWB
+XxH4hy0/T4LJCZ`e] Öb:~¿¡0p}·çzÇ.œ__ÝNl?Q &$7$[MYryp($kL$Z5"L3UN&{zYm@(1dH-'9J"vV6)#9kt BF59E
+tpJimMr5Wla
+c3l(lx
+ hPL7A
+~hN'7ÁßȒþÜÔÿOLcbo//p0
+sEgR$hxQ^DX[ OW}QFa~J^`#mendstream
+endobj
+592 0 obj<</Type/Page/Parent 513 0 R/Contents 593 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F6 8 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+593 0 obj<</Filter/FlateDecode/Length 762 >>stream
+xVQo0~WcA,Lh;[IvBckS9 &/4P$wO-l:sMZe ^.>X\vv>8st=#@ !=[)Q"jNbA$`u\. ~^L:N)->Hg&A6R”¡T|jL!!SKf'cgX-Y-,cD*),SnZJ&  Ut(i"926<0Jr V< c?(In.}TV3LIaME
+B HO5>@WI!VN'C[&OoZ)$,$aQ@0k@F6/de3X21Yp>L`
+FV&qK[i\{vP*6sq5,Q}cnj<7UX0T7f. fD@S1aj)-g<f<6Od$0+ )"bU7t$j)8WSVy8h8-
+endobj
+594 0 obj<</Type/Page/Parent 513 0 R/Contents 595 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F6 8 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+595 0 obj<</Filter/FlateDecode/Length 766 >>stream
+xVo0~HI iMJ$xKlf'}g'
+A
+">s ^
+1xN` Zw4q 4z;6G(u/dz cT:Nn&=vHEAN
->@$
-B8"; 17}Dobòà‘D38>6ix' &s8kF4Uj^\^E,=GG6hRqbZ3! *(IgrR\!%=HhcVS^D~#2&8;leiS`(HNJ\OEIHv{Lw7`tv}UY6dyThOiyr?x6| tFT6Bf!j<$XNn7I/z[w)hG$):By[HK#G;SL,S];mnxB:FGen)d|#.rGQ=}9S$+#I'$VHWH8TI|hDF*p -/gB
-A*/,|LrGI7$p o0Ptq`w60Q\tH Di"Lr4=&è£A-of(r4i6|Opeh; 3:/|&
-A2hI.O{fq)J9 GSL/K?*G&)j"Rik|]<ZqVG5jlbP]-HIpa,`
-]oH+ Uzi|$S;-QFf ^JL:7N;0a.<CY/lhG) <:
-endobj
-1662 0 obj <<
-/Type /Page
-/Contents 1663 0 R
-/Resources 1661 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 1638 0 R
->> endobj
-1664 0 obj <<
-/D [1662 0 R /XYZ 85.039 781.388 null]
->> endobj
-718 0 obj <<
-/D [1662 0 R /XYZ 85.039 761.463 null]
->> endobj
-1665 0 obj <<
-/D [1662 0 R /XYZ 85.039 667.044 null]
->> endobj
-722 0 obj <<
-/D [1662 0 R /XYZ 85.039 667.044 null]
->> endobj
-1666 0 obj <<
-/D [1662 0 R /XYZ 85.039 642.326 null]
->> endobj
-726 0 obj <<
-/D [1662 0 R /XYZ 85.039 596.667 null]
->> endobj
-1667 0 obj <<
-/D [1662 0 R /XYZ 85.039 567.263 null]
->> endobj
-730 0 obj <<
-/D [1662 0 R /XYZ 85.039 276.116 null]
->> endobj
-1668 0 obj <<
-/D [1662 0 R /XYZ 85.039 248.593 null]
->> endobj
-1661 0 obj <<
-/Font << /F20 877 0 R /F15 895 0 R /F37 900 0 R /F43 1079 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-1671 0 obj <<
-/Length 2359
-/Filter /FlateDecode
->>
-stream
-xks6~&_Je" Rss7v9v]:v24 YlPH],H9jg,
-L-h[P|fF9`J @YH1DpkmBTrZ^~~1B9oGENFD0lQ}m(H* oYo|$q)g;
-3}sRd!X!#|$x
-_%
-5i+:z6<az 2CN 7$MiD)&HS p64IE+I+>}G2G8+`c*dK([@k3KDfC&tt:hK1!$mYpVo,Lu6|;@&6e}
-^$HN.#$]%_- lr ^tRHh EW
-/]}ja_`r)j]9N#bendstream
-endobj
-1670 0 obj <<
-/Type /Page
-/Contents 1671 0 R
-/Resources 1669 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 1638 0 R
->> endobj
-1672 0 obj <<
-/D [1670 0 R /XYZ 85.039 781.388 null]
->> endobj
-1673 0 obj <<
-/D [1670 0 R /XYZ 85.039 366.469 null]
->> endobj
-1674 0 obj <<
-/D [1670 0 R /XYZ 85.039 331.425 null]
->> endobj
-1675 0 obj <<
-/D [1670 0 R /XYZ 85.039 298.502 null]
->> endobj
-1676 0 obj <<
-/D [1670 0 R /XYZ 85.039 274.583 null]
->> endobj
-1677 0 obj <<
-/D [1670 0 R /XYZ 85.039 252.785 null]
->> endobj
-1678 0 obj <<
-/D [1670 0 R /XYZ 85.039 66.98 null]
->> endobj
-1669 0 obj <<
-/Font << /F58 956 0 R /F37 900 0 R /F15 895 0 R /F40 1163 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-1681 0 obj <<
-/Length 2714
-/Filter /FlateDecode
->>
-stream
-xrF`"X U9cQ 
-\G`*P r>7m_´Au^w^cn8"/h9t#6["` 7LAg*zc^uT$_H
-bGjhaQX\F;`sH]"a
-wQ",M]sxYxPE>U\>%}@x+wUj#rxL&qIx BED). H.E _, RLIc0B[fhu1"=M`FMQ|.\25I~@4j}Y_V?v,Z`-’ZCk8~LUQ~0"z+K`<|9B0A#r-ivHH86b_pnx]#'YL;>Z=e\uy|YG2JU
-P5]Q-e9fzd*v'6*$HL?`#@I(
-g
-hL}1c^R-Krw I.^Aay*xpV"l!V~b8.bj().Y`Th76{^Lx9kW6[
-y+O+)G)ùƨîÔxVv(UuT!q1r? *J
-J|«X`q!MO+ ThK6N3>7Pv# =OSy74x(q<(6
-xHU Fe,m!v6\V#l7BuRm\..(K-n$">7m¨Nh>;zo<\pNE?6Up Kendstream
-endobj
-1680 0 obj <<
-/Type /Page
-/Contents 1681 0 R
-/Resources 1679 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 1687 0 R
->> endobj
-1682 0 obj <<
-/D [1680 0 R /XYZ 85.039 781.388 null]
->> endobj
-1683 0 obj <<
-/D [1680 0 R /XYZ 85.039 761.463 null]
->> endobj
-1684 0 obj <<
-/D [1680 0 R /XYZ 85.039 743.967 null]
->> endobj
-734 0 obj <<
-/D [1680 0 R /XYZ 85.039 548.428 null]
->> endobj
-1685 0 obj <<
-/D [1680 0 R /XYZ 85.039 519.63 null]
->> endobj
-738 0 obj <<
-/D [1680 0 R /XYZ 85.039 489.767 null]
->> endobj
-1686 0 obj <<
-/D [1680 0 R /XYZ 85.039 460.172 null]
->> endobj
-1679 0 obj <<
-/Font << /F58 956 0 R /F15 895 0 R /F20 877 0 R /F43 1079 0 R /F37 900 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-1690 0 obj <<
-/Length 2655
-/Filter /FlateDecode
->>
-stream
-xZoBN:E_|HmPrA"W{a}('n"]73XY3L',p`/V~sk/Xd-r~6wg
-bLfo/q.v5[_x/|0v >D40alVN ^s'z1 pc:c<{7}Y#- e/I
-u>{D50Rt'8CrFg
-ck)|M*nU($fu}%U^v[J{o%YUQU#VQl;P $JLmngLQW<OvBi'QRf<,eXrG /?*eyk}RyW%AfeO<*WKmrxFQ4:Dy]]4^hL3[+^W7BKGaTB@I<Ow%J! <DKpg?b1e%Ÿèè¤u¢6LY_?8+QzKWMuF[Y cleE@G :Kr›<MQ>'>U4D.F"4X6@E/HuQ~(B{7w\.F wlzSKR6('SKz}LDxWCi i,C=CJR+zN_`.?Z#7jN2\p4n_LgNj1NKE(vC|FUu7HJ 8y=žà}b`ä!™HD dt>}32\u )m-1sMU~j^Kz:7w`xOIIP -4)+^EL{,  dt"Se}rdSigv8}^EL4*7y [HDCq[h6W*?Q'X> S%);*Dr%zPah7Av_X+6twJN$X9q kEK svZXghb
-C)XD'2XFhD):@:zfLU:am/_ }P#ItPP}K^"u8~Ve8\pjMQG(2]Q_!H'X|d,"n}I}p
-`RpgsZ>\`fn]p($^ #o,<xot1^nxU8UHY&k.G\%ITw.|]Z'M.%@*tml@Ci9m"ZjhrP,6 tx>2mBHT `^;
-Uq7Q`0RBRYHQ<4\ZmpN 2 0Dg""}E*"/JV sb
-cC-$!=:$Mo}8!VowY_I)0-u+Íöþž~
-À·¾¯š¦êïõ!¼h×ÁàNva\$A8@_mUIC+6th[u_g\ZpC.C,(r,-wX.l1xFEMRn}`"Zm7c6tJ3&3k¾ã5˜ñ¬¢ý“*K9aendstream
-endobj
-1689 0 obj <<
-/Type /Page
-/Contents 1690 0 R
-/Resources 1688 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 1687 0 R
->> endobj
-1691 0 obj <<
-/D [1689 0 R /XYZ 85.039 781.388 null]
->> endobj
-1688 0 obj <<
-/Font << /F58 956 0 R /F37 900 0 R /F15 895 0 R /F43 1079 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-1694 0 obj <<
-/Length 1547
-/Filter /FlateDecode
->>
-stream
-xYKs6W(DA3@QDTbYN: v~-F(@y?<>L/.$ti !@Ga l>fn&S{W ;b;> &a<=Wfy:Hs;&@
- XXr9lY#,t\Dc$aThw7}kv|<<|Z'9m3y \
->t9~%)3ll!>RVbxfP-aI=1F|iK7;kzEx4: MHa0* rILBPCt3I @0~H 3KE!&{hgn}OfnL8a3RwO 7:^ó¬Ò)Âðƒ~)Ⴓ€‹fí=ÃDW2U\';
->SY)2jTQynW'
-Hh-0ysXfKLpBU\mAbT~_QCL<e^~^wm~0LV;UqJM`uZ("E"xcQR6N[BV_' "_i]Z$uRV
-8q2Pd5h
-rq7ru l!Wx+ ,KKz]eRi Rx6zw4Gf +)cH~0hD]65I}GUL:NVu5reUI8t*YR'f<7Ù‚ãÿÙPZ=_ ˆNzL U<-'‰%¹Âendstream
-endobj
-1693 0 obj <<
-/Type /Page
-/Contents 1694 0 R
-/Resources 1692 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 1687 0 R
->> endobj
-1695 0 obj <<
-/D [1693 0 R /XYZ 85.039 781.388 null]
->> endobj
-1692 0 obj <<
-/Font << /F58 956 0 R /F43 1079 0 R /F15 895 0 R /F37 900 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-1698 0 obj <<
-/Length 2082
-/Filter /FlateDecode
->>
-stream
-xXKoHW k1l6)$LI%J""eWv`WV
-S 6T<Q\>´Øæ 6Œ½%q
-û¥…UJ]aYReR1
-qt9JFj +|/XL )KrEGYP+xz`4p@R
-fC.|L$Y}^9~u%Ro'L#1:%H|wb>[Tfxu] -,J03]qaSU
-|u$m$@eI!m\P 3rXq+QqF 7L7
-F\+YT9&d-::]<rK{Grr`rLvu i!G-ky!>K R(-`4lh+<:qO=`sQRJ<GNq $|: ={G;bqx}a4E
-G/x2a ci?;5R?JGaJE+<:jhqd?
-endobj
-1697 0 obj <<
-/Type /Page
-/Contents 1698 0 R
-/Resources 1696 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 1687 0 R
->> endobj
-1699 0 obj <<
-/D [1697 0 R /XYZ 85.039 781.388 null]
->> endobj
-742 0 obj <<
-/D [1697 0 R /XYZ 85.039 761.463 null]
->> endobj
-1700 0 obj <<
-/D [1697 0 R /XYZ 85.039 671.062 null]
->> endobj
-746 0 obj <<
-/D [1697 0 R /XYZ 85.039 671.062 null]
->> endobj
-1701 0 obj <<
-/D [1697 0 R /XYZ 85.039 642.326 null]
->> endobj
-1696 0 obj <<
-/Font << /F20 877 0 R /F15 895 0 R /F37 900 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-1704 0 obj <<
-/Length 3531
-/Filter /FlateDecode
->>
-stream
-xZsDe,$>^sZh5I}N3&,b]* /b?P4 }e"/Bc}fpfGgI:=G\"(?I_08|:SI}zgjzEx^.i?_e$ka<2!~|][S`q5soeR/syrOk,~ \a
-UCSLpivzEIanIGiF? !w xbP ,&yTg59Q>M*)t%r%%izO xm$Fbii^?="mG|BkmL%n_DD}bm;ffW[BaZvojZw6>HIeQ7s=T+&eEZ zQ
-qzf%iV&yHg(QQ+pX!\"<|v
-RHcAmMq9N.%mYwY7Q8Rkh
-Fq 7
-[rqJzmQJ\{^XB`rfKZ>"N|p$PX OQxS2s ~eG7 @/xS6M{I hd@zIn\Qzh.F|\Z
-`T8GMq*<.7aoQ$ E5@y_z
-X30&WQ(8`J Ty #Ia
-baQ%=K@91?Wr XF`@!6k4$#Wc/IUxMVWYYdfI3[tA
->HY.=e'-eRk/$XZ#'d)+P ZBH0a5O.QL="$?NI8Alxt^@Ivi;^NxRMfG
-s-zUGnpT@g Kn\ FCH`
-!aOk`Gue/,c Q7Q*X1X 27"f$ $u d0&T[CXV8K.yle9-WX=\5#wx:b #\[K Zqel[3 !S)J# 9
-?GEM!huz^k!<k*7FP=8H`mV!Q>M1am@I*dEbjZ%P_G%"Jd=hVEJK>\IjgS:IFI
-G*5ðÌÇð€c––œÔZ+pycN{Y!t;0s6XjG,G`,`\9tq:#G. [-UM=|+^pA{P>xSt6/c+F R?g?&x|S~UfTGHJ. coGU{S` 2ollFGs4<T'I^o8lr#.-}#zV[a`5>1o$w[-NNip1dBRsuKL8P4U!Ij(h2>2 x9{xHV~Z1@9 *E{9 R>HaSNE&4*78pwl*/j y Q{ybKC)gY*O#$#<|XMkE4F%1{)?,_g%%xf1Wh@5_CoDj [$ -TnX\X~ HQ\j?hMzEQ0xH[? endstream
-endobj
-1703 0 obj <<
-/Type /Page
-/Contents 1704 0 R
-/Resources 1702 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 1687 0 R
->> endobj
-1705 0 obj <<
-/D [1703 0 R /XYZ 85.039 781.388 null]
->> endobj
-750 0 obj <<
-/D [1703 0 R /XYZ 85.039 761.463 null]
->> endobj
-1706 0 obj <<
-/D [1703 0 R /XYZ 85.039 669.62 null]
->> endobj
-754 0 obj <<
-/D [1703 0 R /XYZ 85.039 669.62 null]
->> endobj
-1707 0 obj <<
-/D [1703 0 R /XYZ 85.039 642.113 null]
->> endobj
-1702 0 obj <<
-/Font << /F20 877 0 R /F15 895 0 R /F37 900 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-1710 0 obj <<
-/Length 3398
-/Filter /FlateDecode
->>
-stream
-xZ[s6~L-M:tw>@"-qM
-I=7DNf,8
-H]]^cj&4K?s eVt+7TXp`"u 8d8wmVeq 9nv7?5,BNsQ;9=n[h=rw_^wq9w&3I)STQ<9HsO{^ø9yßðX^[%R9x *RDwM~{\Y
-[^, wy
-rK1G?s<4|Jt$pa$tit}GX ITZ$xY|O[O[<5Bc;id(sSzT
-)Y[$(Pf KHlK]sƒè›öž•/ð-±¿iŽ'ÌãBd(Fui bKFqp
-8-Od´r>ËÇLey>X&ExumEq}"3!}>
-_L4 ~L~%=@
-&/IOmscZT /Mna.X''6""W50)=*Xr9o+s5=kxtK!Mn{ddr\ZrlMeVl01klfz-?423a'h8<F\CH7HIW*8Ny}ORTha!FYf[EK /LVQ [SmK,tiwA E@SgZ;(L0rHE%trzaR P=yS&}#iA-m3!Y#2!HEZ*&?[<Ey[bF#O&Q^ A(AljU%a %P;_cArn*1ojQ9(C#ct‚[ Ò~0Š3t›¾“ôNe4c-^-tm 8 g^>\.6+B4«îPwfuYYvX_X/ ql|:k8f{+b\<OS)_&PX6<\{N`~?G-Y{=E"z?@-\ S\8
-f _7J1 iDHFWTaIt:HCJVY{V3MxQZwC$T* :-1|.Z|`DSx) `)Y6mn-Ci
-U17gSe[!#)}@v8U8SeRjBD#:*mDdS! _l"":aMb0E8%~o"xSlY9HZYP z`A)<Ro'JdT`.Y=9"BzBmXi@qIHigwM)Rd:2~T|r<as;I(#9 !4P;(Bl#?Y4
-PjAeFT<r_TE8* TMr-4+e 9l}$F!l QFUJ}PqZw-š°ïôu{lþÓ7ýÑfX8:Yp[o{pBV<88@1m3~f<D
-_RJIIN8_*[Kk*)-L$K]L`g&SVc}^VlbrDFy1B
-[EE'dnxg }-_;
-eM"JB`=z^*)Bww$*1[F P$[k@W/28"o h8=!h}Z<: #nhHqBO@Q^9:7g9 G)4ÙÁwØõ<mG?Gos"
-IcGav FOf+:eVoZL
-endobj
-1709 0 obj <<
-/Type /Page
-/Contents 1710 0 R
-/Resources 1708 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 1687 0 R
->> endobj
-1711 0 obj <<
-/D [1709 0 R /XYZ 85.039 781.388 null]
->> endobj
-758 0 obj <<
-/D [1709 0 R /XYZ 85.039 761.463 null]
->> endobj
-1712 0 obj <<
-/D [1709 0 R /XYZ 85.039 739.701 null]
->> endobj
-762 0 obj <<
-/D [1709 0 R /XYZ 85.039 626.296 null]
->> endobj
-1713 0 obj <<
-/D [1709 0 R /XYZ 85.039 599.682 null]
->> endobj
-766 0 obj <<
-/D [1709 0 R /XYZ 85.039 341.05 null]
->> endobj
-1714 0 obj <<
-/D [1709 0 R /XYZ 85.039 309.525 null]
->> endobj
-770 0 obj <<
-/D [1709 0 R /XYZ 85.039 309.525 null]
->> endobj
-1715 0 obj <<
-/D [1709 0 R /XYZ 85.039 288.997 null]
->> endobj
-774 0 obj <<
-/D [1709 0 R /XYZ 85.039 246.837 null]
->> endobj
-1716 0 obj <<
-/D [1709 0 R /XYZ 85.039 227.965 null]
->> endobj
-778 0 obj <<
-/D [1709 0 R /XYZ 85.039 104.306 null]
->> endobj
-1717 0 obj <<
-/D [1709 0 R /XYZ 85.039 83.313 null]
->> endobj
-1708 0 obj <<
-/Font << /F58 956 0 R /F20 877 0 R /F15 895 0 R /F43 1079 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-1720 0 obj <<
-/Length 3034
-/Filter /FlateDecode
->>
-stream
-xZ[s~L~j;IEkTI*?{HITs:
-G\A'd^tSgJ8yACqwuZFFWN1GjjXRBõƝšd¡ƒ4<ÒvII%)2sKw@'G6jEm9XÇÔ]ìèæ[…Ã=†(r¤IYrk[?1SGzf:m[>M;tb77?mkv`3]/68?%ie y,{3mHPA`\   6ZU~
-Y \+AB@&^#5Xu9f*k3|N 8$øµí’Ñþd0¡[€©ŸŠ‚ŒÛò‡žil͝ǼëTNLOT":f4{m# o(v8DLADD 6hC8s]5 7 $SQ1U#;vh)60cVij2Jws`k"iU2QmE1^3Cn,*DY3i
-#?, "GBK(~@E<_=9lHdzEI@Y >!H)ItP"nO0m =95;UdJFkuRJ{AB~SL=g'vl oDzR/B<l I'8^yFVX$
-ikl74,"q )C,y#j6csy9z]WiGPQ}9R*-` z <Fm~h #8&}oz1K;o\: MmU>_/&7!^B"?N[" G%G03dG/ncd{fyS;{D'C`sz
-73|.UQGV)7l~ u/
-poFZx\H`s7=Bl\<)CGJdKV 8
-Bk*)(. A8HsU$x6mX?>#-(YPpfbf$KFeDQY c +"J'z)%. .l(HW
-`wzxwJ4o~+\{~MVrezWU_+u{
-endobj
-1719 0 obj <<
-/Type /Page
-/Contents 1720 0 R
-/Resources 1718 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 1726 0 R
->> endobj
-1721 0 obj <<
-/D [1719 0 R /XYZ 85.039 781.388 null]
->> endobj
-782 0 obj <<
-/D [1719 0 R /XYZ 85.039 704.845 null]
->> endobj
-1722 0 obj <<
-/D [1719 0 R /XYZ 85.039 678.231 null]
->> endobj
-786 0 obj <<
-/D [1719 0 R /XYZ 85.039 678.231 null]
->> endobj
-1723 0 obj <<
-/D [1719 0 R /XYZ 85.039 654.913 null]
->> endobj
-790 0 obj <<
-/D [1719 0 R /XYZ 85.039 598.597 null]
->> endobj
-1724 0 obj <<
-/D [1719 0 R /XYZ 85.039 580.332 null]
->> endobj
-794 0 obj <<
-/D [1719 0 R /XYZ 85.039 466.321 null]
->> endobj
-1725 0 obj <<
-/D [1719 0 R /XYZ 85.039 437.523 null]
->> endobj
-1718 0 obj <<
-/Font << /F58 956 0 R /F15 895 0 R /F20 877 0 R /F37 900 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-1729 0 obj <<
-/Length 1589
-/Filter /FlateDecode
->>
-stream
-xWYoF~CSE\y(8jZ$"i0\9HQ3;7Zih)pkz)&6sXS|H^8-3i|,q8/Bv<B#38mZ/./>jq }*^^&x}/@4~X^[Erz\b=H!;[GsWbVGW"Y,Yk$uWYI]U'7guJ[b~6je_ZEkU?du\\.3oZ2<e.ZQD5Xz5pv5?8?.n.}HxF;5Qih]e1VE-^Ph*yucdG@fNhf,m[O3'0d3C8FJk( YFT/ J_\IV)u+u]:T\uDYw
-ÇÆ=ûÇÑ¡’¸«HCYvMF\e^jLf[0P,_pI&"cS].5Ι1@451N)|C{ ](@K'=C;VU%0Z*/
-,| J<k)T[e&X nUw>
-&LwayC* rr!h-t/If WO<gM:3dURwc#;u_7q(RqdsFIW YrXRZ>F~;<F=L<7y7lbe:EdZ.y~M"ggv$7rQ`4zdP2A>^;pwJsi/.d?:S@IPe!%žcã`ÆÃÖTFh6MZ<(n$P~..m,7:Lu1d4*Np)jy$~I':! >
-}Sk]UF4:pr8.BGN$?9g?D&\endstream
-endobj
-1728 0 obj <<
-/Type /Page
-/Contents 1729 0 R
-/Resources 1727 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 1726 0 R
->> endobj
-1730 0 obj <<
-/D [1728 0 R /XYZ 85.039 781.388 null]
->> endobj
-798 0 obj <<
-/D [1728 0 R /XYZ 85.039 679.868 null]
->> endobj
-1731 0 obj <<
-/D [1728 0 R /XYZ 85.039 648.343 null]
->> endobj
-1727 0 obj <<
-/Font << /F58 956 0 R /F37 900 0 R /F20 877 0 R /F15 895 0 R /F61 1406 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-1734 0 obj <<
-/Length 3176
-/Filter /FlateDecode
->>
-stream
-xZKWLTHKCT§ÖÞ­ÌlÙ©l‘#1–H,O
-UN{Lw@hH*y5[n5 d(T
-`l}t/ šE| @=#'@@sy}tK(+C3:.n[eT X>q<rV 7_dP
-˜ã«x™] 52Ü=9p‹ÿƒ‡µl|±Mfx{a8cE j_t0}+`S+t#G%Jr
- c:J0q +<TA/LN#<dsDZ2jkP"/4.Tjc[jlE&0uxH& }tz?dhKZ.o2
-?9iuw+ _idKLIZJ
-oB:vc[žq¶Ûº‚ÎøòxºÀ©«¹VJG` ~-?#Xr|;[*v t|
-_}U
-endobj
-1733 0 obj <<
-/Type /Page
-/Contents 1734 0 R
-/Resources 1732 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 1726 0 R
->> endobj
-1735 0 obj <<
-/D [1733 0 R /XYZ 85.039 781.388 null]
->> endobj
-802 0 obj <<
-/D [1733 0 R /XYZ 85.039 761.463 null]
->> endobj
-1736 0 obj <<
-/D [1733 0 R /XYZ 85.039 667.044 null]
->> endobj
-806 0 obj <<
-/D [1733 0 R /XYZ 85.039 667.044 null]
->> endobj
-1737 0 obj <<
-/D [1733 0 R /XYZ 85.039 642.326 null]
->> endobj
-810 0 obj <<
-/D [1733 0 R /XYZ 85.039 542.47 null]
->> endobj
-1738 0 obj <<
-/D [1733 0 R /XYZ 85.039 515.856 null]
->> endobj
-1732 0 obj <<
-/Font << /F20 877 0 R /F15 895 0 R /F37 900 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-1741 0 obj <<
-/Length 3475
-/Filter /FlateDecode
->>
-stream
-xko~0Q$w
-\:#gY@|;^x4@i*NWF~: eFp q8; ?[r]~oK*L{yxp ykYd)WQ~+-/_Z|R:Q'?% I<;}vy~=c9:)XG<}H8
-8a<vpbYumzWS0|h{nW5D[^ oXC[b^;}kzCyqTS6O;e^`@$!s"<
-
-9/.JnM^-[86).bK%H- j9^,a8G 0p{&t0 0 )id]RxUevu=S x#*pN?DVQthu_t*Kx<etK*M SIpRo
-?ESa0<$
-e P|,z`e%SA%jY,m?P;XP (xJBwlkr %wOsg
-7t%D#4ayo*;;! 3,*cP6*2ZB3HX|&~A|#>=P 0ZHH
-)r*Y1fd#a(*]Nr=eS:B=PLzpddUWagdWG&JPi,  k1WLW#cy]9zV<+_@DS?"W
-_Vx}n~XEsW-z[}mx5#}{ZLqf[[ i*u))J?cR9#o$\mFR%5\3IT C]S$&f=c%
-SYZp/$WK9M]*Fi1~,4l2cuyHSExE^YZ]àÂ&ƒU'O-PuYcyg6kT 29lk8v&V4(9(H &{~5 |Ks)/`H) (,CL:ÕA8XQ
-9C|, 'f x3SC^#<+L Q-7NRqmh\Gw3{R=aL R
-Q|Cs2|pQ2Ndp"B q?t^+y
-@j s p1ThBFlHB1/ kEYYVO4F]=0 ?#a],_pJT ;s0iR-Dp)+DCiN(N@om#
-endobj
-1740 0 obj <<
-/Type /Page
-/Contents 1741 0 R
-/Resources 1739 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 1726 0 R
->> endobj
-1742 0 obj <<
-/D [1740 0 R /XYZ 85.039 781.388 null]
->> endobj
-814 0 obj <<
-/D [1740 0 R /XYZ 85.039 761.463 null]
->> endobj
-1743 0 obj <<
-/D [1740 0 R /XYZ 85.039 736.911 null]
->> endobj
-1744 0 obj <<
-/D [1740 0 R /XYZ 85.039 736.911 null]
->> endobj
-1739 0 obj <<
-/Font << /F58 956 0 R /F20 877 0 R /F15 895 0 R /F37 900 0 R /F61 1406 0 R /F40 1163 0 R /F36 892 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-1747 0 obj <<
-/Length 831
-/Filter /FlateDecode
->>
-stream
-xUn8}WF
-)R[Nu2bT{\J~Hr<{O°|ô”󐾉dš é}é]Ý$¹¯dT/RfCjQfY.>%fs70 b._8wzmn<u9Q}tGHLhGS.=4&RQ *@a*1luX<tS [?}qmA r#-(XT~+U&rv} B\1-.UOvok'dVj
-;/WpNv#B>]E3.MzV}(bFNiN(
-8%'uR=J' u<omv`O'l*I]D9Tb}]U
-; 46u}^,Q;Dd
-endobj
-1746 0 obj <<
-/Type /Page
-/Contents 1747 0 R
-/Resources 1745 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 1726 0 R
->> endobj
-1748 0 obj <<
-/D [1746 0 R /XYZ 85.039 781.388 null]
->> endobj
-1745 0 obj <<
-/Font << /F58 956 0 R /F15 895 0 R /F36 892 0 R /F37 900 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-1751 0 obj <<
-/Length 2215
-/Filter /FlateDecode
->>
-stream
-xYY~v ez;y8"y]-%)CC,`x 0`5kuKQ,}rGJ~=P ER{+[?hC#6\ofNz)vw<.D~2I_x~8OHmYW>ft={(YL
-]UaG'wf
-BQD{6('*[\,r.F&0Z2wiGhp,iD;8FO u.Le-Io}sn.k| jdgaLe -uin'3wf#/MYJ$Ou h5vx6XhJY7Ea#BxYs>w5
-kbr2D4eS(b>': z+%*.!~YNVxmW$Y+|_~~c
-G2zIAjun>0q"J rWbr% (<9e(S ]*4l4Dk[ K f5)8 4G0g.6[_XhaufT(;h d1R9EAtvrpX'X`u/o$k'C}ykDEHy<=mpAvS W:P`
-ae9/g:MvYn(w#!$UhZb9@Y-SM78CjJMzEMXwRJN[>'(tvCnevsWy <k
-QtkfY#'ljICs r~W_x;E=P%HdJ"Y6 
-X;*dEF*H®R?v{_x7~iL
-V4#i&T3il#Rg>4#-g|vkF@-'j7tL{
-j-.iv ~4sx) gX<`MC^eh@þk@n,R}^C{Lt
-R/Eq%+/0=tJQ-Sq7; uI #v-1Pv+:'K4 !9|
-*k3-a~g,z*x ^lVT__?PP*e!Ly 0u $Qnl_tZJS&uR: |FS77 VxJ Pi0lWQBFFWfNC"8&}q@km$ zMk%m)*e([e0a?;of/Mknl
-9?5yf~ zzNXk(R'RX%f2G ]Rs+$?nFp7%
-:Qy5rsY|"pIqbHwO%}5WKTPdutTL c=M@>2P4^}<Q"
-On}j~a~4y"5G{J(M_
-endobj
-1750 0 obj <<
-/Type /Page
-/Contents 1751 0 R
-/Resources 1749 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 1726 0 R
->> endobj
-1752 0 obj <<
-/D [1750 0 R /XYZ 85.039 781.388 null]
->> endobj
-818 0 obj <<
-/D [1750 0 R /XYZ 85.039 761.463 null]
->> endobj
-1753 0 obj <<
-/D [1750 0 R /XYZ 85.039 671.912 null]
->> endobj
-822 0 obj <<
-/D [1750 0 R /XYZ 85.039 671.912 null]
->> endobj
-1754 0 obj <<
-/D [1750 0 R /XYZ 85.039 640.387 null]
->> endobj
-826 0 obj <<
-/D [1750 0 R /XYZ 85.039 486.212 null]
->> endobj
-1755 0 obj <<
-/D [1750 0 R /XYZ 85.039 457.414 null]
->> endobj
-830 0 obj <<
-/D [1750 0 R /XYZ 85.039 328.278 null]
->> endobj
-1756 0 obj <<
-/D [1750 0 R /XYZ 85.039 309.406 null]
->> endobj
-834 0 obj <<
-/D [1750 0 R /XYZ 85.039 163.931 null]
->> endobj
-1757 0 obj <<
-/D [1750 0 R /XYZ 85.039 145.06 null]
->> endobj
-1749 0 obj <<
-/Font << /F20 877 0 R /F15 895 0 R /F37 900 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-1760 0 obj <<
-/Length 2380
-/Filter /FlateDecode
->>
-stream
-xY[s~g5[bgªÈ5év2IT
-W;x=U$mo lSmqOE@\4]h(pMCxSbfSe:~9NwY-x;Ud$
-Fi2#GUA^:{U/6´,¾ÝeèÈv}ÑrùB&c,+^] %)L V5#8U;ief4XfV21kG[bV68HEGZFz<EZI ?C~Q*(x}Vl4+/47) <
-OI o[H: = vra?-q_&H/ {[@mg:VXAEvYE皲™¶QNa"(T}^HZHQU$%Oyr[&N/e2yq$-M\XfGA5u{r'LZ8*hyTTp;M4T6d6%Y*iwjvP85 M9* =-c6ac**\m^JI%|2 i qczo
-;/}H WvOC
-H"JS6@/
-AmW9CfxPVi-O0PIrk\^
-;;<iMk"~Em]ZR7z
-Z7XQ}}f LH")urjE/A:
-4
-endobj
-1759 0 obj <<
-/Type /Page
-/Contents 1760 0 R
-/Resources 1758 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 1764 0 R
->> endobj
-1761 0 obj <<
-/D [1759 0 R /XYZ 85.039 781.388 null]
->> endobj
-838 0 obj <<
-/D [1759 0 R /XYZ 85.039 761.463 null]
->> endobj
-1762 0 obj <<
-/D [1759 0 R /XYZ 85.039 736.911 null]
->> endobj
-842 0 obj <<
-/D [1759 0 R /XYZ 85.039 431.136 null]
->> endobj
-1763 0 obj <<
-/D [1759 0 R /XYZ 85.039 407.154 null]
->> endobj
-1758 0 obj <<
-/Font << /F58 956 0 R /F20 877 0 R /F15 895 0 R /F37 900 0 R /F61 1406 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-1767 0 obj <<
-/Length 1953
-/Filter /FlateDecode
->>
-stream
-xY[D~ÚÌzn¾
-E--YHXZ/®ž-–:Š‚«r!ƒÃݝ[•9ŽÄÁÏ|Ã`}(ófñòæÇÙw7Ã[Œåƒh¡cýÀ¤Ô"•vH4BhLL7+BhX[ 0HGliN7b LCw|(-Q^p=w[Gsl0h7|$w~+x)%#( $k`u$vZC<XF=26pu[3\1ZvF+\h79/"] vG(q5xb*VnXxXhQ;xYLte^ Ҝ½ÃE1+-U[>gk Kexc=/~UcG!EYe9reN5
-rxU8,upHe1<7ZH7+ZFL8
-&9+u..IKT#]NA&Q+&drP@K4I4~J! _R-"_
-Rrk+74~{V^u]>
-P`"dANR4mWv o{%0{%9`g
-3W5XVA4f<+w\o.7,4m}|Wv[zj'HPb!#9UNXaXMYsS6Pb>JAi*34v O 2H{#0\3\=_a
-y
-
-C!vTH^q?-0N
-endobj
-1766 0 obj <<
-/Type /Page
-/Contents 1767 0 R
-/Resources 1765 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 1764 0 R
->> endobj
-1768 0 obj <<
-/D [1766 0 R /XYZ 85.039 781.388 null]
->> endobj
-846 0 obj <<
-/D [1766 0 R /XYZ 85.039 761.463 null]
->> endobj
-1769 0 obj <<
-/D [1766 0 R /XYZ 85.039 667.044 null]
->> endobj
-850 0 obj <<
-/D [1766 0 R /XYZ 85.039 667.044 null]
->> endobj
-1770 0 obj <<
-/D [1766 0 R /XYZ 85.039 642.326 null]
->> endobj
-854 0 obj <<
-/D [1766 0 R /XYZ 85.039 569.569 null]
->> endobj
-1771 0 obj <<
-/D [1766 0 R /XYZ 85.039 542.954 null]
->> endobj
-1765 0 obj <<
-/Font << /F20 877 0 R /F15 895 0 R /F37 900 0 R /F40 1163 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-1774 0 obj <<
-/Length 1029
-/Filter /FlateDecode
->>
-stream
-xVn6+P&Ej*M@jMmY4;P*ywGz“ÅR|fZ,/js/[Z(E6]Q02Wq{&R2If"}IwSjQAhDL)0Zs9?_~RiRR™ëø¶6m¥±É}mRsu_ *n+D22N5#$
-f |7 (Dn9\n ||ZYnHn`MzSS2W6vp,wu{l=s@\YeUIv98b= 12{#6 V
-endobj
-1773 0 obj <<
-/Type /Page
-/Contents 1774 0 R
-/Resources 1772 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 1764 0 R
->> endobj
-1775 0 obj <<
-/D [1773 0 R /XYZ 85.039 781.388 null]
->> endobj
-858 0 obj <<
-/D [1773 0 R /XYZ 85.039 761.463 null]
->> endobj
-1776 0 obj <<
-/D [1773 0 R /XYZ 85.039 667.044 null]
->> endobj
-862 0 obj <<
-/D [1773 0 R /XYZ 85.039 667.044 null]
->> endobj
-1777 0 obj <<
-/D [1773 0 R /XYZ 85.039 639.536 null]
->> endobj
-866 0 obj <<
-/D [1773 0 R /XYZ 85.039 532.636 null]
->> endobj
-1778 0 obj <<
-/D [1773 0 R /XYZ 85.039 503.901 null]
->> endobj
-1772 0 obj <<
-/Font << /F20 877 0 R /F15 895 0 R /F37 900 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-1779 0 obj <<
-/Type /Encoding
-/Differences [ 0 /Gamma/Delta/Theta/Lambda/Xi/Pi/Sigma/Upsilon/Phi/Psi/Omega/alpha/beta/gamma/delta/epsilon1/zeta/eta/theta/iota/kappa/lambda/mu/nu/xi/pi/rho/sigma/tau/upsilon/phi/chi/psi/omega/epsilon/theta1/pi1/rho1/sigma1/phi1/arrowlefttophalf/arrowleftbothalf/arrowrighttophalf/arrowrightbothalf/arrowhookleft/arrowhookright/triangleright/triangleleft/zerooldstyle/oneoldstyle/twooldstyle/threeoldstyle/fouroldstyle/fiveoldstyle/sixoldstyle/sevenoldstyle/eightoldstyle/nineoldstyle/period/comma/less/slash/greater/star/partialdiff/A/B/C/D/E/F/G/H/I/J/K/L/M/N/O/P/Q/R/S/T/U/V/W/X/Y/Z/flat/natural/sharp/slurbelow/slurabove/lscript/a/b/c/d/e/f/g/h/i/j/k/l/m/n/o/p/q/r/s/t/u/v/w/x/y/z/dotlessi/dotlessj/weierstrass/vector/tie/psi 129/.notdef 160/space/Gamma/Delta/Theta/Lambda/Xi/Pi/Sigma/Upsilon/Phi/Psi 171/.notdef 173/Omega/alpha/beta/gamma/delta/epsilon1/zeta/eta/theta/iota/kappa/lambda/mu/nu/xi/pi/rho/sigma/tau/upsilon/phi/chi/psi/tie 197/.notdef]
->> endobj
-1408 0 obj <<
-/Length1 777
-/Length2 1024
-/Length3 532
-/Length 1589
-/Filter /FlateDecode
->>
-stream
-xRiTWE9(Q(!A "HEEVP,bj-X,K1Z(X"Rbuz<}}EH'B@?l.x @aeMB!|uss
- 88 $oBD
-X{&I.S
-IT$A@)!b JbO ' !
-!)(H $&u |#*c1Nl:*C A)N!o} TNuC(N' OakLDJas8\HcIRF< PJ
-85CtLP E[}{\O+R}^/.>]S.vg>y=fi0,YQeywz4o2j6:\6sT4AE0Wz0^{welG|P7!+aj|Zn"*0~2{_DwYid#f ;4(v
-Y!u|_K_m{@{2] ^ bfQPTF%~]yUcdw42Mo4/S{+Q ]8m.yu R[R,<s`KsM1.0QNg Y;GGG[`|| uHGL$$[XBO$ En 8n=3F&e 6ã³&Êڃ?iÔb.5Ä \7lDQ CkZ:}~O65ET%WS1;?-d^Nediye,k. YD694T(R]
-g.2?`K|/xeU=6aT13m|q1eC5L9_+2tEZ_f}W"Jc!Vtrr!m{>?weV$rKY}OjeYNqj;+W {6h>3+.SG5wuoFÅkΦ¬-ó9%‹/㨴™üQ7>5Y4mxjn~3XJ,ASB\cDk}?XB [Ic)"WdYpq\ufÍ¿xó¤¤ñƒ_™KiL.? ..m&x6z] ZP ^d}~yg,f5]Uoa&L'fc<8|_0O0($)B*$.BZendstream
-endobj
-1409 0 obj <<
-/Type /Font
-/Subtype /Type1
-/Encoding 1779 0 R
-/FirstChar 62
-/LastChar 62
-/Widths 1780 0 R
-/BaseFont /LIRIPZ+CMMIB10
-/FontDescriptor 1407 0 R
->> endobj
-1407 0 obj <<
-/Ascent 694
-/CapHeight 686
-/Descent -194
-/FontName /LIRIPZ+CMMIB10
-/ItalicAngle -14
-/StemV 113
-/XHeight 444
-/FontBBox [-15 -250 1216 750]
-/Flags 4
-/CharSet (/greater)
-/FontFile 1408 0 R
->> endobj
-1780 0 obj
-[894 ]
-endobj
-1781 0 obj <<
-/Type /Encoding
-/Differences [ 0 /Gamma/Delta/Theta/Lambda/Xi/Pi/Sigma/Upsilon/Phi/Psi/Omega/ff/fi/fl/ffi/ffl/dotlessi/dotlessj/grave/acute/caron/breve/macron/ring/cedilla/germandbls/ae/oe/oslash/AE/OE/Oslash/suppress/exclam/quotedblright/numbersign/dollar/percent/ampersand/quoteright/parenleft/parenright/asterisk/plus/comma/hyphen/period/slash/zero/one/two/three/four/five/six/seven/eight/nine/colon/semicolon/exclamdown/equal/questiondown/question/at/A/B/C/D/E/F/G/H/I/J/K/L/M/N/O/P/Q/R/S/T/U/V/W/X/Y/Z/bracketleft/quotedblleft/bracketright/circumflex/dotaccent/quoteleft/a/b/c/d/e/f/g/h/i/j/k/l/m/n/o/p/q/r/s/t/u/v/w/x/y/z/endash/emdash/hungarumlaut/tilde/dieresis/suppress 129/.notdef 160/space/Gamma/Delta/Theta/Lambda/Xi/Pi/Sigma/Upsilon/Phi/Psi 171/.notdef 173/Omega/ff/fi/fl/ffi/ffl/dotlessi/dotlessj/grave/acute/caron/breve/macron/ring/cedilla/germandbls/ae/oe/oslash/AE/OE/Oslash/suppress/dieresis 197/.notdef]
->> endobj
-1405 0 obj <<
-/Length1 1358
-/Length2 7588
-/Length3 532
-/Length 8432
-/Filter /FlateDecode
->>
-stream
-xe\\!K`in]ht Np'hp\
-æ 7`úË&3
-âèà °YcrCj ¶þ³¸¼«ƒƒ:ü»ü_ú¯q ØÎÁó2 `¨« PX`j
-8`(|?u8m= B
-?pG~e&A$7.'j7|[/ \Op];mpn ܆û?È×õü ÿûVHKC<y-a@Ossr)O  |~G-]a0__"7[/(\X Oi)(EaAiUn
-ZCt(VqbYyu[we/
-6Q
-i5r|x. UlQxK+2ui
-&?jFj"b$sB mmq7qâI~63j49^k.23tUwbobXSTb c <C(Qjzq/jkt1)KX(/<]<T 2Ky-El(d;UUv\%|j(D8%I]y9TA0DibfA-6m
- 0-mh$'fP$fw]sVu}mLW@fy$x)J 'Uw
-IUd?{E»bV9zEEx?Ga(jNdZpshgFd$}&aY-N=l7g>SiC'fWiB.òº>™Ê͏<ô¿
-{…Â
-£ß"÷ê4Ï¿'¦ê ŒVwv@A~q"y9AwrGF(IV|o_õ4†®3è;ˆ$Š_‘ÛM lH
-F~"]mrJIV!fcM>Ah3,Q|gAhs5^j4~BD.=eD3]K 3qV4OV9*cF
-glbtE} Z0xUd5Ve!uL$_W^>BYhJq6B_ &pM|k;4W&U+wPzktqG `R_M#JT)+MzmVE<`?1EE\dQl¯§‡s^ˆ³A)/qzNP)W L Y::]YM{<+|IvXgV3DD~m06jL}=f^HUwU)*lu}fG"!,Z6HZx  &?a!"X3(iW}.~4Ebz(2sCdC$2uL)l?XAcvUC
-ra9 !"m4+V7 mD f !TNh[QTTYI V'?~1CdQrL:,o%0pY8}UV^dn#[5lt3(<J".+\"[/zXW>DP>"TM" E(m"uxr_89H"G:Buk/(
-%ùl 䶄©á¿=ÿaêà×+"³šfnÅ£;¥¿Hp5lDLm>?90ywk *f;P~SVglLl(1qrM (j
-ea9y2B]'cojD#`&<e-/cy-MJH@(X!5N{>KpDs70M yHJ
-]k~}{z$ShTZch8&8`.)pLR6- WA;N:5) C
-MytfAq8gu
-))d^D3L!C*I;]]1`v>"L)9
-ioX2:yo~H5X #
-AwMW )D
-D(x4s]r>0x8*TFm]Jo!F-K}j4DQx8k$l`?;xBtH^"07l'(o$VNV:T;HM8\q{}@yi³??FXPmF1t7FHIH(X>]+5<AC\BuIiozZLjdG-pZpu!eW;@RF-lz\t<2q56V 1N)2x{J*TNqh}- fO_ZFYn9"B11T "g*k:OxNWCd)Tz
-W,
-.$kbj!~\hotG?L, @_ðMy>V2LqWw})RW!pIc =;
-4¼eza»+5¾ê??8çELNWq:H^l ;wREc;U?k{1bqJTYZy@YFJO7l0f"@`G4hQ<f[Ug4fx?REoZClI8|p[x+c`g-|GT .=i~t]U< FcQ57]Ob9t@/GUqkZSMHg)Gab FgS$9Wt(:!_z:CG|cy8g½Û2F-gcQW<
-)3 leWBJ.Kcft| q-P}$]~i,M."#LF8'W55kg^#dSO:=pUV%EZ,K=¤Çˆ-·®´&»FNG4 8!k/Lk2-FSL H\CVrV"E (ceI.|R7G"8<x\Pll|~uw<>E)|,z!
-x*|T6MB %db\A
-4.#r<SC~hzmN[<ilAN QJX d. }q<xg.7
-endobj
-1406 0 obj <<
-/Type /Font
-/Subtype /Type1
-/Encoding 1781 0 R
-/FirstChar 38
-/LastChar 121
-/Widths 1782 0 R
-/BaseFont /ESTQDQ+CMBX10
-/FontDescriptor 1404 0 R
->> endobj
-1404 0 obj <<
-/Ascent 694
-/CapHeight 686
-/Descent -194
-/FontName /ESTQDQ+CMBX10
-/ItalicAngle 0
-/StemV 114
-/XHeight 444
-/FontBBox [-301 -250 1164 946]
-/Flags 4
-/CharSet (/ampersand/hyphen/period/slash/zero/one/two/three/five/six/seven/eight/semicolon/equal/D/I/P/a/b/c/d/e/f/h/i/k/l/m/n/o/p/r/s/t/u/v/w/y)
-/FontFile 1405 0 R
->> endobj
-1782 0 obj
-[894 0 0 0 0 0 0 383 319 575 575 575 575 575 0 575 575 575 575 0 0 319 0 894 0 0 0 0 0 0 882 0 0 0 0 436 0 0 0 0 0 0 786 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 559 639 511 639 527 351 0 639 319 0 607 319 958 639 575 639 0 474 454 447 639 607 831 0 607 ]
-endobj
-1162 0 obj <<
-/Length1 793
-/Length2 1151
-/Length3 532
-/Length 1728
-/Filter /FlateDecode
->>
-stream
-xRiTS2j=,iF !D(rKr/^n i
- DA p*RX$0M RIHCz
-k FvI- Yh5rd)kI0tj,VfzVBBa`WDCP\O0
-MWB7%GGyS9QtdO?c$6Dr;%Mk&Fr)8
-sJFZX xlo
-UhqF"m{+i
-&krUl MGvu76%# %zZm6Xz.Y3.~9e`z_<o[>_I)Ys'i:,v_CC%31[tuA(VY/Oz;I`,0R*pB1&`))\.`~$?$,V=Xf/j k #;~)h/9i-7+3b=}dzxTk_^6OcR'r.p\c:o{:+A%Gb<M JM9uËórmŪ`çڂ™I%Mn }:jb\ob|qC?DGx/ mAro6kS>'?[fDK;^^],<SQ2yozF[1P2miEqt!{<G6v{t%ojM 1s~q,o]HQe`= 'hPs ^zX\R%O]Qssq{A;dUI +wg)o7bX-V/qgg F+&vMhvzKIM:e5u.p(1<%V5;kUWb5-|s
-WQQ1;/eEX`Z*.ymS7n]x+tjT4÷\¬,¶ÿ$FF+n'oY5,k8n*knA;7xYu1Bx}sw_\"CE=a~
-endobj
-1163 0 obj <<
-/Type /Font
-/Subtype /Type1
-/Encoding 1779 0 R
-/FirstChar 60
-/LastChar 62
-/Widths 1783 0 R
-/BaseFont /EUEUQC+CMMI10
-/FontDescriptor 1161 0 R
->> endobj
-1161 0 obj <<
-/Ascent 694
-/CapHeight 683
-/Descent -194
-/FontName /EUEUQC+CMMI10
-/ItalicAngle -14
-/StemV 72
-/XHeight 431
-/FontBBox [-32 -250 1048 750]
-/Flags 4
-/CharSet (/less/greater)
-/FontFile 1162 0 R
->> endobj
-1783 0 obj
-[778 0 778 ]
-endobj
-1784 0 obj <<
-/Type /Encoding
-/Differences [ 0 /minus/periodcentered/multiply/asteriskmath/divide/diamondmath/plusminus/minusplus/circleplus/circleminus/circlemultiply/circledivide/circledot/circlecopyrt/openbullet/bullet/equivasymptotic/equivalence/reflexsubset/reflexsuperset/lessequal/greaterequal/precedesequal/followsequal/similar/approxequal/propersubset/propersuperset/lessmuch/greatermuch/precedes/follows/arrowleft/arrowright/arrowup/arrowdown/arrowboth/arrownortheast/arrowsoutheast/similarequal/arrowdblleft/arrowdblright/arrowdblup/arrowdbldown/arrowdblboth/arrownorthwest/arrowsouthwest/proportional/prime/infinity/element/owner/triangle/triangleinv/negationslash/mapsto/universal/existential/logicalnot/emptyset/Rfractur/Ifractur/latticetop/perpendicular/aleph/A/B/C/D/E/F/G/H/I/J/K/L/M/N/O/P/Q/R/S/T/U/V/W/X/Y/Z/union/intersection/unionmulti/logicaland/logicalor/turnstileleft/turnstileright/floorleft/floorright/ceilingleft/ceilingright/braceleft/braceright/angbracketleft/angbracketright/bar/bardbl/arrowbothv/arrowdblbothv/backslash/wreathproduct/radical/coproduct/nabla/integral/unionsq/intersectionsq/subsetsqequal/supersetsqequal/section/dagger/daggerdbl/paragraph/club/diamond/heart/spade/arrowleft 129/.notdef 161/minus/periodcentered/multiply/asteriskmath/divide/diamondmath/plusminus/minusplus/circleplus/circleminus 171/.notdef 173/circlemultiply/circledivide/circledot/circlecopyrt/openbullet/bullet/equivasymptotic/equivalence/reflexsubset/reflexsuperset/lessequal/greaterequal/precedesequal/followsequal/similar/approxequal/propersubset/propersuperset/lessmuch/greatermuch/precedes/follows/arrowleft/spade 197/.notdef]
->> endobj
-1078 0 obj <<
-/Length1 795
-/Length2 667
-/Length3 532
-/Length 1237
-/Filter /FlateDecode
->>
-stream
-xSU uLOJu+53Rp 44P03RUu.JM,sI,IR04Tp,MW04U002225RUp/,L(Qp)2WpM-LNSM,HZRQZZTeh\rg^Z9D8
-@'T*qJB74'/1d<80s3s**s JKR|SRBY.Ykhg`l
-,vHM ,IPHK)N;|`{8;zkC,WRY`P "øÀP*P6300*B+2t#S3J.`
-L 2RR+R+./jQ
-*[mF%s_-j(ls~g|K~#&g]p_!GrnM`v^Dl>Z`,&7{eY/-pp3LXc:sOy1#u,U)MPPQSi_]7`tlx~FqéFI8>
-vMO7J]8fv_7xht*B5j0 9'5$?7(
-endobj
-1079 0 obj <<
-/Type /Font
-/Subtype /Type1
-/Encoding 1784 0 R
-/FirstChar 15
-/LastChar 110
-/Widths 1785 0 R
-/BaseFont /HCAMJO+CMSY10
-/FontDescriptor 1077 0 R
->> endobj
-1077 0 obj <<
-/Ascent 750
-/CapHeight 683
-/Descent -194
-/FontName /HCAMJO+CMSY10
-/ItalicAngle -14
-/StemV 85
-/XHeight 431
-/FontBBox [-29 -960 1116 775]
-/Flags 4
-/CharSet (/bullet/backslash)
-/FontFile 1078 0 R
->> endobj
-1785 0 obj
-[500 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 500 ]
-endobj
-955 0 obj <<
-/Length1 1351
-/Length2 8100
-/Length3 532
-/Length 8939
-/Filter /FlateDecode
->>
-stream
-xUXܶ®)îNqHBqww+
-'^
-4uAeLB
-hAA@g6$ k@-99 sg
-d#E{Ka \P')
-*TN=
-
-.
-k70[=e a9#pÒ)XyBlOPJW 97j].S 7XI X.MhªäWFN`*g-B&AN.5Y/5f;Kf}<]KX9=owDPFoe<]Yym@b wwaaiAHyphmK@tLYow>%wC Sw&K%i}]-R?G!^sb%[h|mx<dMIBE"?y|-"XE'A27B,{hw J2'7SwA[X%su<mM@f+&na.. rL]ox$Op%-L]fRlk"$L{6p$C 2yDUv+?p~E*-^(P ))f%9*yP(_ 3zZ9 %Mgdki4}Ioxk2^Upq,*q_b|zXun{
-\`TG+eWªÃ{½}óûr½ŸˆÓÞöHX_8WKGt inQ JDIl^(;kG^(~O p"sJL-)S" 3A\Q
-~A4:VqZH6&"û·9io钧ëüÉPW_3QF8-<f4i?0q"
-(/v% ^|oNqU]= nl?Hii!Y;Q"G6-|=jOP!<^en+()?= §DK
-A0**&jMnz-rH Hj#a0@yFZKgZb8K@CZ^C9A9bf2O+n(s-oTtRdQ
-yEL)#2Y~|g!|zB_4},s.9eZKWò8˜0«¬>}`GAqVD5>r ;7[?;(sXDp0; > _GQ
-P53!TC[~,/,~^}Qz)3ajM,SB#UH=GKIS&!8=;“ãA#$pj ~0.R$ _4fTKZ^D-1g<OB2g47=8'V:AG^NU5Ik%KuYyBECH|G\7Gdd]UN&n5,1D
-?:-qRugOwfG2[#4v.~F~c]'p/?Mv,_wQ=:\<Y.Q[vdZ Q?ÌO.u_d nL4OJ0I|sgx~Mh'\H#q& nIJ3'^{ioe6B[cs
-O[zt h$PR8GLfR:^3,))9p!b3f"
-rTe22a9 ZK/GM61Dò¤Ÿoþ¢?qî^¶$çS2mYd5e RC!@3tIm r:öÇÏV JyQCpRY*gy-E 5}3&x,5doQjG_1c1%@iXzwMb|N)F,( e1di'*oiª1'{£÷‘–’UXIOOIY,B>-E+TL%,[N"+bo
-Vpf+U Mx0-dlgpd®Òhï{}ïFfK8/4~]iRYVM
-5iiC/N!1K.= z
-)J^cZ=}3s7KR7V/h!2 gd5BQ
-gsy\two42U2vLxJ aNft*E}fO5ZK$z:`UPLn*-LQbjCu<;tdj|t0>;Sudx~5]g~=?HM*]{5<ML%q?_gKK<jQ.~v+y1+ X>Az2|=hgI,AuYxLT$Q.T45RWif%01i"#~\ 9:5 uTx|)`${z_RA8iLt|7KH*FWSnR <h96r9Sy'XoY~ jeUQYw*5dBCqUhG}n7: ,LbXr}J _:{6,ü:Q?t
-7~hW%h5Om^j0qm& eFm9]oWy$:1f[y(H/ ^D>s"pxbPY668Yr>hn3~zsH;G!>LzC&=P] nisDu
-%vktv/|~O>z>^"Dh|
-ä…ÿ‡"ˆ²`mêÍ\§ÿ;D/zEDX\`Y]
-/NoY*}x^>.3.~v~[$FS: 7 "V);I FDVDtezBH0SDXdN#sy&S'fQYIqf~}pG%JjCSIYC;L$
->*BhOQT
-.v^{q*1*`]Ox%EkP=O*,#=- ^U]O
-&GgcsCFn\{R68EKc:N |K+˜ø*¿oáŒuùÖb .ßL÷iA,ajw#*)L}$3:FZ/w:jf#*
-'|sl?[M**F$]\"y/|
-$oD t=.]G5[+b&[`+JQh#f>(M>b56[+1C{Ou
-!eoqZTuR5Rw*QPD]gWVS8Jbtm6<BJijLf"o_Uk|x$n-lkFHEX[:Lcb[,w>:3lu=tP)Ii?r;%uKvUb09QUW@T-%>I=sh!if r^6GQ(JP~$WŊcÜ Ÿ Ï!íÿ*>Ç
-[ ªÖÑJ@q ^c6,as>VVO`"Ybv,Vwa]&}:=}]lgZj==,E8Rv+rst& !i&w4{S++<{yG?Sn< MYIM\ H|fU8(KBfo?o˜±nq¾Ö¦!Á‡‹{Ö~°»)ÿèoy‘’ê?•¨Î/™Ãð~ý3"4Ì4jƒõ PUf,'xlZsH#@Rl'OEH.9aWNP}w]qu K>S(Ibvl?1e<10_W]5q=;cNk=fcg [iIY84JdAg}Yy
-^="Z< v|1$Qe].^AEHd9W
-=^
-BTl;x/Nzp^qWJg{A j.vZx.(H-! AlRpU|%C_/
-m9ui
-m`Wr 4-x/;E/6_94%wU=J-}xBfww
-F[Z. 0Ha,I3l >S8(g(-H yiU]wg1O
-endobj
-956 0 obj <<
-/Type /Font
-/Subtype /Type1
-/Encoding 1781 0 R
-/FirstChar 36
-/LastChar 116
-/Widths 1786 0 R
-/BaseFont /QZIHLU+CMSL10
-/FontDescriptor 954 0 R
->> endobj
-954 0 obj <<
-/Ascent 694
-/CapHeight 683
-/Descent -194
-/FontName /QZIHLU+CMSL10
-/ItalicAngle -9
-/StemV 79
-/XHeight 431
-/FontBBox [-62 -250 1123 750]
-/Flags 4
-/CharSet (/dollar/quoteright/period/zero/one/two/three/four/five/six/seven/eight/nine/A/B/C/D/E/F/G/H/I/L/M/N/O/P/R/S/T/U/W/X/Y/e/n/o/s/t)
-/FontFile 955 0 R
->> endobj
-1786 0 obj
-[500 0 0 278 0 0 0 0 0 0 278 0 500 500 500 500 500 500 500 500 500 500 0 0 0 0 0 0 0 750 708 722 764 681 653 785 750 361 0 0 625 917 750 778 681 0 736 556 722 750 0 1028 750 750 0 0 0 0 0 0 0 0 0 0 0 444 0 0 0 0 0 0 0 0 556 500 0 0 0 394 389 ]
-endobj
-1787 0 obj <<
-/Type /Encoding
-/Differences [ 0 /Gamma/Delta/Theta/Lambda/Xi/Pi/Sigma/Upsilon/Phi/Psi/Omega/arrowup/arrowdown/quotesingle/exclamdown/questiondown/dotlessi/dotlessj/grave/acute/caron/breve/macron/ring/cedilla/germandbls/ae/oe/oslash/AE/OE/Oslash/visiblespace/exclam/quotedbl/numbersign/dollar/percent/ampersand/quoteright/parenleft/parenright/asterisk/plus/comma/hyphen/period/slash/zero/one/two/three/four/five/six/seven/eight/nine/colon/semicolon/less/equal/greater/question/at/A/B/C/D/E/F/G/H/I/J/K/L/M/N/O/P/Q/R/S/T/U/V/W/X/Y/Z/bracketleft/backslash/bracketright/asciicircum/underscore/quoteleft/a/b/c/d/e/f/g/h/i/j/k/l/m/n/o/p/q/r/s/t/u/v/w/x/y/z/braceleft/bar/braceright/asciitilde/dieresis/visiblespace 129/.notdef 160/space/Gamma/Delta/Theta/Lambda/Xi/Pi/Sigma/Upsilon/Phi/Psi 171/.notdef 173/Omega/arrowup/arrowdown/quotesingle/exclamdown/questiondown/dotlessi/dotlessj/grave/acute/caron/breve/macron/ring/cedilla/germandbls/ae/oe/oslash/AE/OE/Oslash/visiblespace/dieresis 197/.notdef]
->> endobj
-899 0 obj <<
-/Length1 2210
-/Length2 14292
-/Length3 532
-/Length 15508
-/Filter /FlateDecode
->>
-stream
-xUXp[pw8{`w ]5+Y<<15GLEQ tcdeb#W`e!eebaCw8%L
-)hMI-](;)ÀÂÌþŸ'ÿä$eº;˜ýÓf+àŸ0)³…£½½©ËŸ7)³ÀÅ
-jö¿$ë
-ðøËÔXf,'Hh?swK `Q.=bq2by
-O}Y 4]qa}yAt-pkh45=jiir''UN g $
-`?UkJ
-3dg4Kd QJ~+UqftpSd|}  Lcw&cbq&Dw;.%Qxd,_ieE;n
-PHs0öß߈1¾Àâø5ŸÀUvC}Q&@ P|kB%tzds,ldd
-yI=5RA[Sh@ g^&$FG
-y"NW!@6W_w0o:.@6u,'E QPUd_g{>BK`b:_z(xB(^ j@| v
-^ ofN_bH}h?QoZ?;PL0qs^P-Y_6u|G5^^}qc$@)r'G2r)o|u +2)ÿ¡ 0RV6t#NrA&
-5J}N,/Ír–"ñ¢æÆñðËŊùÂ3œzåT1BqO$-[  JN677"B7
-}1CertdYx<" ?8]hR:$>TI ~yÖÔ0 :u»Ú/(DB$ba:E'V)If#"6uSYJa1ipw9lTQZ L :U}S_6 y[}@{}\@WA>8îò«â×Âq榥ܦ¥âK/\ZBAr!
-7
-5f!?jwQH{5#7T}" :ij!.RYR ?$xx<6%urP3i+Bcwv#B'Z x&3W'mv?-&
-}jy7]5uU6e5 
-V)5E{]Yw<s)[fQR#
-5XY_wDwmPvCL8.TV(MSn`e=xsY_Q`Xp*w 87Ba3[ = 
-n!"eN9^r){ h\au:VC:*3L Im\gYDkh-Q;n@Jk`,W_)[4) G,L`~{0tONKv9>1g$Hx,phy~AR4N(~KOn]APSNu*=b#SROjCYgLNX+
-` <5©”(pªÚAyf rJ >!q#\vF!;1Iu(x#LC]8t> ,gL~r d-Gp6??xh5[D+)}ID{3j~<Orq ^]5lE>te,
-o\YSgT ?#|V,]X~D]O7%}O {QH p_hTJ1)~Þô5°M9y@kWIH#pVxcjZ&4.l 2&wFMqK,qAa a+g+r3S.\1A|flub ,^o1aM'Q#{q&_Btf6?-UHVD ;r%]{ XWS"T~3aNdw]U{ fdLB§¾Jq}5$/"IAHQ''74IWo;`msaR$j>#%?qZK,NZtQFVb
-R<\:#(?=R;/2"/$JC< NxJ,e_|W/2C|{U=)C,e[mM, Q ,KYJoA4J\|l=Y[M{q4#OH!"hW ' IMZ/!DOu +&
-qA5-Qae"y1U.o]qs Gh}aE5o ;uG !euoN
-LOJ};|WuvOy&ck|Z-cZv L@+j.0SY.-+.`38JgYDUf.hlT[ (ha
-RJ:{.{<4'MR;O _'a(JRxRh $:WLGt08S~28NtgPMW*%@C[6/Ym6f\ozemx¨Ã‰È0e_ÊØÒŸ®mPW:N}-d_x?z£ì1$Α n~sáMHDon2_qCHp%E>B2H '&kRS[7 _6Zþd³÷0ÒhøÕÑ/"E`!mw^0h
-`Z_zM>gydyeqC%~Q 2b@O[v,\9> oIS{=m$);GD:, $V*.Xw\LHw/Gj*(1+*1J.ST1lG}'/i>1jmN
-ñ˪6½¿Ò>K3 ]*)\**oSm! _]D]m~E(}'k-] M-%,g$isn(eFzkD{yL:I=YRpK<fZw=ff Y.2(,~ 'PD@u2"I;? dr*=V_cAe`O6UVh~_\:4,t0p.~sA!A)rv4c()ehT=8b%;$k[zJNjV zM~5IW|1]e ;Ce.T&B7;zJ ‹ ŠB"|u>>Sll6 lu,s:M!.
-8W*&Itk(_5=wYu!3gyV6X~#<e
-}EvF
-z/8;_``[c<>)i!_@vR'!~q
-a Tt>#wn%= )9iI!43PpbopXsZS!:=A'?m#2
-ol\-L ShXUke[h|T.pX<YT>0B8Wn|%:p‘¾è€*CEIcP^!;Yx1giM:9T5Nz]mAnQ`{ t%7 _/yY`oZo_uV0,#YKKd;) ^
-+-+P$z
-R8@t@kfr.Y,Sp7#`
-3ee(j.?d5@rlRB<wiY+!u+d!eTb^AWu=v7S1U8*4Y+/uj_{@`'-kie4
-W[TE,c2,WWK !q*^YXfN'y ,L1KR3+jiDH3 07+M22*- pRa
-Kq5!+Hw5~L.sLl_QY zn '(lmu1Ql=WV06RpoqwJ#SUFn+sL>.1yH9JOc#Ij 1$HNeGfP`wm=}r wyJ?DAcwZ:j^ 21gV[q'd)__lRjcnzhS(WI^}xL~
-\lm@h#;jz'q:`I0.jTf->~J.m_£þ;åk¢d§k³·ëk7•–ɶEc^)~c]d
-
-}Ea-aH/*Sz|^4s7-6 `'r.' Epm 1Y@K}9tYx<Y}z
-[6}3DexST7 UHg)bHi'gtS -<jF*,d^=z2[e[+2jKe*Gw;îCGc/HYmDb{M`;+3lqkr/,Cm)iY|=qu.x/G:dw YbEYH-1~N '
-X?x#- U+a%eV%-Te>ZMXUL:~9CE'79D>S/isä §Ÿ\;£nüøØvšú}÷A@Ux B)Kb9
-¼.?5C'`9@^P&k^NX}wfDF9x"#K$fjih<a~-)4(39T =C*L|!~=6>@/y8QWR5]Wr+dJ kkG+eDI$B*{m5qa! 7
- }mó“Ϊøòçæ—
-»”÷/j틒:ãn´ï¦Ð¼q$~'Jp1` ru
-^SVZ%I\M',y ~|*<8dwVG)pP1(GJs g 2Vk%=RMFRf!O2`p9 r2sb `OyhRK< 7I~z]U-  ||2uW=~}REUY(29A\NsjES3 %dLMO<lN;-^$Oq| /DjiUh -fC: 1Rq`fG;"G7
-'+<63Jd-i[aVf^8>Zhw &B7~qOiC3)U'G4V*(CPI0{}7+O
-Sdi9u_wB"m~: 9q$e;mGazu*'(."N5hM-eu]Bo-26$sD#1<Xv
-zy*~tHG%/7C(C `I0 C-sog INpAVBL,vu$2hB{;N`s1EG;Di</.2u_R^$lp^ä4p̑?x™ÅGzw#=EM-]&|Ðfù)‚¤Ô€e9ƒu9}ºo ³3üþU m&{{ /bTY9A+y"VZw>x
-2|BA*` Ez;A@8':BB\8Y$X#
-EW *)|5W8/02|O}$xKF.}=96 >T =`G;…Þ
-ȁOYkYNB9mM»íÁžËj`Gq~ µ4°ÄÖqŒÌ•=€¬“îI%
-Cb#FA >!d9'81 r0
-30X(cy.[;JQu5q2 [yxjTNDQQJX i h(j%,^&>Zdub^\1JO$*sG> >+#b_8|. eVV{+ |K_/D @%L4u]P(cgUpwZ!4'
-F!\s~6.?F#l6m` 9p= lIBB^vU&3"nh( B)ojLs/|UP.Z 6GgfB9&ÜsÔà FBIS&/d ^`yPe`U7JE6(O/j2hKC.Xccp!NU7/-S Q0t3R
-:Cg\n|"KkAqn F640:S#R8ljQu
-ft[z{k{h9~WDN/V(858GXpc$VC]/rfw$<}]k$udVwY3yY;,e\YBINz."_z(P]YBN0t!p_l7b6
-Q3 jafJ4]Tn;
-Wk?dJc_S V^\3Q'91!Ijv!d*.|>2Ekw[@XP~ G6fy6J]}6DG$\GGSr-UQw=Vk+ [5.lDmBLed> SvTKT%rk Y,DssxTE*2;/'vM^n2I
-76$tcL]Kpe?'09:!t
-endstream
-endobj
-900 0 obj <<
-/Type /Font
-/Subtype /Type1
-/Encoding 1787 0 R
-/FirstChar 34
-/LastChar 126
-/Widths 1788 0 R
-/BaseFont /XOUGVB+CMTT10
-/FontDescriptor 898 0 R
->> endobj
-898 0 obj <<
-/Ascent 611
-/CapHeight 611
-/Descent -222
-/FontName /XOUGVB+CMTT10
-/ItalicAngle 0
-/StemV 69
-/XHeight 431
-/FontBBox [-4 -235 731 800]
-/Flags 4
-/CharSet (/quotedbl/numbersign/dollar/percent/ampersand/quoteright/parenleft/parenright/asterisk/plus/comma/hyphen/period/slash/zero/one/two/three/four/five/six/seven/eight/nine/colon/semicolon/less/equal/greater/question/A/B/C/D/E/F/G/H/I/K/L/M/N/O/P/R/S/T/U/V/W/X/Y/bracketleft/backslash/bracketright/underscore/a/b/c/d/e/f/g/h/i/j/k/l/m/n/o/p/q/r/s/t/u/v/w/x/y/z/braceleft/bar/braceright/asciitilde)
-/FontFile 899 0 R
->> endobj
-1788 0 obj
-[525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 0 525 525 525 525 525 525 525 525 525 0 525 525 525 525 525 525 0 525 525 525 525 525 525 525 525 0 525 525 525 0 525 0 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 ]
-endobj
-894 0 obj <<
-/Length1 2181
-/Length2 16529
-/Length3 532
-/Length 17761
-/Filter /FlateDecode
->>
-stream
-xstFmV4Xm6'm4¶ÑØn¬Fz>gXc]9 *@XT^IB`lag+f !ff!
-v
-6tB?6`gc p$38TM&.6UX@;D 8J
-
-:J*)Z:y:Le&?K%nklgbakFAlh<=@b'b&5 vGkClj_# - + ?Y m).v
-##aHChT9y50
- T;M!*foSp4^LPeH
-HP4;j<y/'^lt;rL+s`/5Ayj9byE78j%E'yIdAc
-J2/@_
-\th*2^prZRO{'Rc'Q>'d%ka^pRPNTG{?|pEA;1GO^Um5>}Y, at>hbj;"b9w($NQe8}*'s.&cSb$0|St{a-tZ7K4Y,/cT;SX4f $ap;@#K
-pUkJ<>+S 9Pn6-qn]1o]w3Zb
->> 1 f^wj%VMXwbU;[Q6jmIK9EU!O1Pf.>1d?e;y3/X#!^*:S iSgwhxp6@PqkkC&} K)iI)dz_eCY1swy40{ I/wk;Q]uO&jVB&he(@tVvb!Pp^HX H_I_J .f(?wa>1Gf"/$
-9LX~lgFD wv}4j{~
-&mfC!k|eXv,"% /)W5[JkKivk~'HPYB{UN\0P
-WDm8Y/E`P`z| ?F
-i`'qW_un:-)W/%x"-'C!O"LOJ9CO {"S)otz+f;9jQEP v`?& %rp+%6L7)
-LPhV_pQAJ.4 kl:*?Uv8w%~8!eu&8WOl-* *l<NV{h2(Bb,%!p>a6
--L_U?FwpwirG J)u]=5@&6oe{swo<Pv3<&v2C~)jt[KsL5 KS'n3<8'(MGWpj7SsT~f(nI14ep1^fnB:.ZWo8t+tq-{-M$hZt~j:"aZ SXH* Tmvz=Qe P1}h\ /5[%X5hX_^LJ*JTvOE7/B^k$lD&DxgJy7GYg_sIg!/_&7e34ahW7+`Cn-'HÊ«±daT]Z{sr.=+7?V gOvDIms5M0wjC(.)c{<nX/~A3yr2LB`qAZ'-}WaO?[@Wl9m1[]5!l8,vGD+FGL"zGLj"LgFuOb'}uttb]b5N};}\jR! a?xSg]pQ~V}G~6\Zx9I3|=
-[l}[UE1\r<Gbcw+55}uc#wW3 TuC)";($8~`=}II
-f 'AB ed)Y(h¦ŠˆéØ ¨nžðn™ä®gD/4 _D_ RF}>!esM 9K|z
-@M'Ua6PJ;p$k%1*!EOLi],_?ibDM(UlJ??\ )2-,NU'p/_qq>wJvh=Z$+ =?Bv[]j Pibu( !/GAmZv: ^:kaœ-
-iq¿bËrE$%Vr*#Xpz%o7D}dy[f6,0 FL\
-SqchÀ&—ô²²¤žú˹;s¶I
-;nui_ DG1-f}P`?X-\Al){52 v* f_ .>o?
-yH
-u^ W9I#7ICE)%tA
-85=Aou*0lv!&N?r%;^3-px/OaExi}7Q(!>nd7,$E`= iqpBOQVCM {'8o( l!8u =j*'NPf z,J+9"Z!e_ z3(S
-;"Hbt ¬õoÁ¦±løƒP^)B=1A -"J&Zu\wo hRivF<Z'x, q `BxNJoiLL;7.k0H4S¸ÚII70`1Zu/?9Q2[>$&~!Yz?/s1h6K^:I<u+_!| &kNg}\&x#P /BWP$
-Bkn8[l&`q1TXU4ff(gzI/I!St}PF6y@<C;TrB*b5xq%VOd4Ԁ1¸~þ…¸RqQ?cKN?WX#+ \/s@, K(zl"x>
-N(Zu[*T^wu 0T7% eqYaR# u mE|ijRuL7 c JI35!o;9TPweW
-v9Sc+n F[7AU,8f"'jfDUAxW%An.39i$W$>ZKT)Xo4n+P7lCtBys7 ?I\kSQl!&yPV+1ˆìÀ×/íÞçhÝ=¿åÞ.å >·­šJ[nBieBSz?jn0O4x\{?A?:jY3N < ZtfMQuVjZFwwE>}5&R q"t>m_Vg/v/{W I#[ )Y_ mxZ\~S3,3jtrQN}E-D
-'$#kM u*QWo1FN?8@~2(dOgFF#~vQJX~oQ]`O'/YaOT09:SRqa_Q0(/064 v4!T}8y;{7;S;#AXc*>IRiz/cHge ~V2`CgI0qx-9B$}3æ–H9La
-9JHH$kDu`[v2FMQ UP$!sZCi$R'kQSHrP^)]M1}K(m&5ef?d
-`?-byvJb{x!^,uDHWB)t+{#ybp&&VJ39T
-%!P/WBjt{/&1SOoj2{+fni:"(Rxv,(^BND$[[M&qRX!IºžÍ·çi¬Ç#hy#ƒ¾£Dv|ba_mMj-( Uv**v!$qH_="Y
-lBR.X(dz+MlqO04D9- -A%PFR&[Qh^2IXfb{}e#e9sCX3.oW S9vp ;3DH @$1Z!/E(%Qxn{ SM TQs Eqj
-4.HRpa/+19UUl63WUd0?Yq-[H&thWH"rLU6If_&pYQeey<E5R %K$vj ?j=MzS+om"?01 <s uh=c.a LYigc%.n] |K&;!#<g~0FeKYp'zf48jf$[2N:1Tx':9,a9th"K+e;P6  jaP~D_<6/z|O-;J>[0R-N:6
-HmlG1$?FMLOsk Qo}^%iB'joJp?!
-c+:Yj
-;F"&8;e)/>rV69t%
-U,!#H+taATWCK`0;C/XmhrL*,5Y&dDLP~,!iF{,n:I X$$s8Y‘[(ÖR(<CRLE~o?gK% kjDend2
-AX0\(B{1y;7^"*zLkCL9$ v:HI,,tTF7XuDc
-'bKMMVi =c{*2C|}]$<.C1RaPtT,j.aR)@cP#2H»M~`W9Q_u4eOrnOFjgüê>€ƒ úõîcŒ¦išåpêˆA+D![Ahh_"I-a97qWh<$}K P~^Evn@HsP-a}?XN9!bS-k+EgR>
-B[~·Æ[·v§_ƒËÄø‹-$ú€Ð &ëòҟˆñnSq-YlJi<(U
-I^--w'*,FR`xJ U+^<!"Uc?wYg Dvk.>;M s~;J
-g In:vzXCYK!d2&H5g'
-/6ebkJPq7)OrbP^B&80IM3qYZ RjrhQ7p#s]kj|UuMbis-$]
- m1J+yxUAe*N7ËÞ¨ 4²l«ý[§õýw‘¿.H`n1{Bn@E:v~Dt
-g2hKwZfR)ytMW Oz->k`bmp=e?J </Bdq!M0(~Z.'4s1l;%'z4C)z
- qD b$-!wF+mXxvYYK6hLYN$N)gIuEU`U2bVgY?f"f(hsgDZ$*JMS/o`nzjT3?? Z@(=)qUpOHk9w/QW)cUbI xTPa(cev}ëq¼å̈^çøðŽ9Œ!x_×ïŠ_ŒÐãM;$F,v ;>d/ 3^d9F{-B_S'J4EGx>tuz!C=<$I^9keV1&+v-
-nU@oK6a]zm.eV7eD9Xr`kA$*]7Rb4kfk-osU`Z7Kc$/@,LiozjNIA}=^++fSu@qiR`-xAD
-<).aC'A~TzW|kb(lGok$05SvPCB&Q)'zwfGf:V"»!ƒ5-Œªü>†n®ø©J6u7r(V<ODu57:{*'&Ub 4#((V& |F{^>3<w*eG5ÕÝŠa5ô÷àägƒs&|ªÔ|“ßã!º,=#¬“ë'dÊq¡p„:¡Üƒæí ©òÅa¹Â“ÂDMhO3nN3n3Ye:ER*| A wTjPne`, S4wXS_x.rPA+6~i/zp fs~C'S
-6 Z3oSeNv}2E
-H(?oI$r$iEFWN~qDP :7^8}LpvN(E]c7Z,^
-Is
- KwT5vau /yo\HY0/! mHoY@ (J$ ^ A`NB4Wdxhmq/qM3jS^497&M:VPn‘è"°Ÿ çaZ~c;D@ ¹ƒÛ§á(jo ñ„†ÑíÇ{)T=vW0+,FSW-wTdsP)3k|$+1}f0 _8D`Z&V[bu4]n`0` s]2]&d*>C/-P,'VÛӉŠF >N+Ptae ntQyvMPj
-3"gTl[vg!$U6>}<Q&
-tpmS.5O\
-0"]0vSZh'ocj2:TgZ/!ni+}ÿˆªóÐ~dÿñ©§Q48ehZK?SavSAzT&gkP
--}™çd®cC'KsDDA5mPBr2
-Ux+\CfK1Zz;%C1bL/h
- /K =yh@~paZ*h?S
-0b]8K9"g)|c-Sb4'¢—B)4aAIZ" ${8vK+K D%^Ok6==,HLj0Vb3pck!e8\Y]6 u%
-uY 'uEZ~ 7 DR}2f|:/9e}d!%_GL[#Bn:9kg/f-yS:w xK;]1O{0 eXPsPsr9Li\K ^|e[
-;~2W*1k%se4"]+qk0L0GaK2V9/QEj2fg
-QE J7/nl4YUW0)GY1<o&[8jy.7Rmom gg4g6.g!^Qze<4m)l?E\´1ï@ ps 5$x.8±™‚`ßgwº[ÅXc*+9et.w}~$RV5x\ÔΡ² ¹k2uäõ¹!yl'/h:÷‹ÑÑ÷ ®i™AhL6lpyQbBk2/qU.b'`Lok L1!aRFc(M,}5\(([")>;v(\D}SsCr{"hG7)K,.!ejDAo #4 [d!i&jü<XLggn TnP'>%+4GM]a"<)Sm qyf B X;pH;daxu=o)7 0QqX'!=GJ zx.+hBt#iy[D 2 u"z2O&?LNr6}jL@D)/!{1BE8dNxh93@v.L @3()%2X)%(vHP%sÁ#;ù“xë` ‹Òmҁ—~T"4 œ+<ø¼½{ñÀ{z¿ïoòáñÝGFRFi$oD~AtIuB!R^~! IQ
-B_ {(c8 <=/#,{(jw95;R?GE~'|fe(
-]>CPsR}'9x)JH2hHP"p{Jf8%2AN{c} d4?MyBmu7%M% RAEq:Ho1m~S~
-^$>yX A"&-;k5:^\A2p6`]Xd5Kh[$bxa~+4@OM|c9Fs;r+j`h>'O:S`3q;d 4Åç|‚îÜ>fŠ"ϛ-15âz–U2cL%{SDjWU<Q4o"e%CD NgeZ%%2%-| -?'`!h?i.~|KjxwP]m;2wDw.4)FO5.Kg
-:_ G_"(7Z!{xP/zrqUë«8ÜoGnAbo,C!2,.*?KZ )Pyz$%< hz\:. qmk;cpM4+"bi?G2Fm1}F@u P LJvk#l)A,=eZe_]BiPN C% `z bsrWPG_!
-E&wA( ^iZ 4p!GCHT7/&W0o#RgmF`vz@8i0\n-r"%|JX%d,'=,~i~OF\X7\2rk #h>Jžq[À¯›ÿoñ'…Š7†¼YuADbn:\oy'YSr>_}5Tro+9juhU`/y7x\buMNrk98~%KKV`i;%|o^A^C;,<xKF;O,G]~.1 __17oW%Q)Ey+r/%
-: N4.ibgt|I{8|w~UK1v;xeIi0%U_o9k/L3f‚b“>jÿ“5K:83.sx-U(bU+[9,ayh,Q"sUUw7N4?rU\]vKs{csL]Sr+gD\ *{..KR^q \:1jZMgr_6 ]X7e Wi|WF?mXI1Us3e9#,v\vMY7ÜMsVV$8.c=U~U:zE|S] 0q{!45<S]N[?ÿëtyÞÒ8ͅ/Z1XTJ+w
-endobj
-895 0 obj <<
-/Type /Font
-/Subtype /Type1
-/Encoding 1781 0 R
-/FirstChar 11
-/LastChar 124
-/Widths 1789 0 R
-/BaseFont /INZPWR+CMR10
-/FontDescriptor 893 0 R
->> endobj
-893 0 obj <<
-/Ascent 694
-/CapHeight 683
-/Descent -194
-/FontName /INZPWR+CMR10
-/ItalicAngle 0
-/StemV 69
-/XHeight 431
-/FontBBox [-251 -250 1009 969]
-/Flags 4
-/CharSet (/ff/fi/fl/ffi/exclam/quotedblright/numbersign/dollar/percent/quoteright/parenleft/parenright/asterisk/plus/comma/hyphen/period/slash/zero/one/two/three/four/five/six/seven/eight/nine/colon/semicolon/equal/question/at/A/B/C/D/E/F/G/H/I/J/K/L/M/N/O/P/Q/R/S/T/U/V/W/X/Y/Z/bracketleft/bracketright/a/b/c/d/e/f/g/h/i/j/k/l/m/n/o/p/q/r/s/t/u/v/w/x/y/z/emdash)
-/FontFile 894 0 R
->> endobj
-1789 0 obj
-[583 556 556 833 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 278 500 833 500 833 0 278 389 389 500 778 278 333 278 500 500 500 500 500 500 500 500 500 500 500 278 278 0 778 0 472 778 750 708 722 764 681 653 785 750 361 514 778 625 917 750 778 681 778 736 556 722 750 750 1028 750 750 611 278 0 278 0 0 0 500 556 444 556 444 306 500 556 278 306 528 278 833 556 500 556 528 392 394 389 556 528 722 528 528 444 0 1000 ]
-endobj
-1790 0 obj <<
-/Type /Encoding
-/Differences [ 0 /Gamma/Delta/Theta/Lambda/Xi/Pi/Sigma/Upsilon/Phi/Psi/Omega/ff/fi/fl/ffi/ffl/dotlessi/dotlessj/grave/acute/caron/breve/macron/ring/cedilla/germandbls/ae/oe/oslash/AE/OE/Oslash/suppress/exclam/quotedblright/numbersign/sterling/percent/ampersand/quoteright/parenleft/parenright/asterisk/plus/comma/hyphen/period/slash/zero/one/two/three/four/five/six/seven/eight/nine/colon/semicolon/exclamdown/equal/questiondown/question/at/A/B/C/D/E/F/G/H/I/J/K/L/M/N/O/P/Q/R/S/T/U/V/W/X/Y/Z/bracketleft/quotedblleft/bracketright/circumflex/dotaccent/quoteleft/a/b/c/d/e/f/g/h/i/j/k/l/m/n/o/p/q/r/s/t/u/v/w/x/y/z/endash/emdash/hungarumlaut/tilde/dieresis/suppress 129/.notdef 160/space/Gamma/Delta/Theta/Lambda/Xi/Pi/Sigma/Upsilon/Phi/Psi 171/.notdef 173/Omega/ff/fi/fl/ffi/ffl/dotlessi/dotlessj/grave/acute/caron/breve/macron/ring/cedilla/germandbls/ae/oe/oslash/AE/OE/Oslash/suppress/dieresis 197/.notdef]
->> endobj
-891 0 obj <<
-/Length1 1836
-/Length2 14873
-/Length3 532
-/Length 15918
-/Filter /FlateDecode
->>
-stream
-xS|ÛIm;VGmFV'Xokz/:SUs<sLTH i Mli
-u1g{ sw
-rSA>g,>5v8?3 gi/tjW_i/ta~w_i/a3OŽ᧠§¿ð³jÎá§+—¿ðӕë_øéÊí¯£ÿéÊý/ütåñ~ºòüþߗ»-ãç¦eú<2ŸÙ
-ò0<enš2ä•Ñ™ŽÈHPMf*}3kx #{EXUc$vDsq| ;U9 T ;0VY5 GtK
-+rHxs1lY* ntc3 âËÀò»¥p– ÎwBu2AA'c`LKUXr sV~iBk@LPIoS:^MczESbP]n8?VN2'L|x.!5Kia vBtC5';):Zhb * 4424xfqKE[ +Vj
-
-5>0osa.:%"m7..R m<O&3[1D9Q&2<U",`uE5B;/s?t@vP3fr4F
-Q!wM="];Y_(E91Ñþ2¯úõîó¢ÎɽVYTT}Csosg]H.L+
-j{½Øhz´ëœÜBT=JrTr=Q74g^?z\3H_6jqSnzH)GbB5obiC4~[g} uDUjoV-
-U*OB$f;  U8:ele;v4B58{ZH|Rs/;#O~=h :t #2svK
-)|5r~zB2Ja.vw Cdk[n~SUiqmyWv[B Z±þI3{;[iC;5a
-IXm* 5X1_
-2-X@Y|P.)Qb)p619/#@ANyUlIS_<b!EPj÷ܙ9ÞÚ8›_ØF2¢–ÈU 'O489QasL&X3Ru|uPR~qVe++KbA'r}Ax`?(
-dxc'_mo]89|>WV/bUKZj!}1Fy `^aW-L00ww,'$-JP,;s,JsOf5A?L~KöuI;u`XHzArlK=jTg%6s0N_on), _%G2g1I~vsGG)DOk(@@Wtj1_A,weJZfHy_F }n(1R
-'Zy~. {N>sTtbr ezZ<X
-;>9PE4E`wpyd e^*}[:3^){R!e`'v(ZS} *)$90znO.
-NC9&Zbfwwp \ÒøöŠÉÃLZBmvSy.BNN÷‹§ì©d-$}œG)KoBvJB+$3un |!fmrsH9mv';
-.,$+_MS6sLI,^ênzUlex*UO4# [u2y{O;~5s1ria]zB43^
-)lfqn?0m>M-{.I]@>|a[ w0
-[! 5t@eTWN3A6omNt lUnd/U"@]<t6IpV4|;ttqm{WnG 0>þ/'“W*4us"4bsD|
-1WfhuzXxh1lLj?7=FE-ݖ¢5tÓz<|W\7:sv#'Pgr1F
-1y:1eOJ P+,\bxj!)L-9Rs^G
-Yspk1';<w5}4` #TEJ~ l} J4|:"a EWU[DL:h1YoCc "I"GjJ@xLX4kwJs;[8>y.v&N)g|4. $lw!qX@:h+uoRzNh Nb;SJb!Bf^joKOc1*6L[SX+~MYy%e2WQYN*
-LU5#"X&K,:5w`Lr`y k|po 0D5i2Vk
-VWm
-'GV:bJIK8iv1BR  7z]NbjX0m:vtNN "v_D+s[zaSkMA `a5jm KV t+õ¸ú{BVI2=*fG61iL/O_6]@?+UobfV2[.>1`EG ~AT~NkGu'G?}z*&C:SvK[xk<d
-v9Le
-btzN>nCI
-s3
-_p!l >OVw[(c
-wo9&EDD&Upg7dpr$d"¯‰D[BsHum5fv(G0w^CI' Hb5xK97}!J/-M
-hY "2~AWy|i [SI/E{RqEu7]c{-9.pe%:>_9Ik++t)r jæ•à£—º
-Ðvpxò „oæªÉȵoʊ<®Ðtjvq壯RspiQ5B{N, 'wztFe (<0
-A
-b3@o4;nmL0A7>Fo!0(Phus&|>byB^džUE%LD cM!P\c
-&
-ogD#,Lb+iESZX4Et!,m(-Z`Mp?h#8^j8&S`#?V@/<aTR*\G"rHqtZc8WC%`tU`DPmw7<IKr| |8xUDz ( "R`SIAD
-'NE23(p0[p z!] `W1p=|"%m<:EB:aEY(z{r ;z>?L%GYP !wbhCZIT\GaJ$\uI4__FV!|9jT/ M O\w`qr1lgQhI6@FEnR^wc0[ht t56~GYT}}H9g1 $m>)GDvaB;^:SK&{W.b\2e<?TfS+m$VVH.Q
-j-+|xZVP(S}8k"tt1V3Qon ;<$x-'N9A#J&q6ZsQW-H`}WAuUP
-5G7B!PW\?a&o4j2HRcqIRZ3B)f Q,v[DdyY13^ DBd2%AT+<rlY)
-bi=xUmR=dLv;E ,C$M !
-} S lQ<DkdJfBNRxz> 8d1w!&f;h tyD_Yyi%L W|jy1T;DR
-|82 |Z)E!8?/@N *|`<,nM]=SjDD`q"
-Q6yZ&iTr(Y+<jUg5tm4f\qr+@vA~_x?*H faiIIt8"0|sl)Ts GsI]8KZ?͓y4'!óL[L,zpw@oPW(wckhz}:/9Wp!a'P.z3;<cif5\ X &SNm/K=@ m$TD4; hsH&.}Nx{I¸76¯Tj]Q.d .TS.eAYi.`^T:-L) tIBAqP 1lb9p9o,yReJ{[) *q/N3u||XUw$Y
-(Q^E1’6¹&ží}¶4î9¿5Ք«g滒ò0Š­AcSna{Vc[Y5@m" 91M+ gqdp4mt;!-,M~|C\;6y>^-{,Z+ @Qte'r-;(Ob6Z;w(,>K~4}5 nW^v#$Q\"t\u@)&Q5wmRM;lRtttBF+Pp.qiFIw]Y_]J' 6]td(C(2,6+M3xZ*MgJXRO)G*0jLHQzg%PI%~8'$I
-pytMWO Dn 
->Myq¨VD"c8SwM&X=_Tj5mW/|k;P^"'*b@!9 7f E$1
-_SCSRLWQ[fh*f_tTEyp7*Adp%ElPY]*CT/i(n
-Œ<ìAEIk9saKa.Utg`KYAK&RBKm:mG\;B$\jh>6S'D1~ cU( vbg@[[ptGrhU/X8ocHg\I_(-E\+V ,{sTW<{Qy
-{X5=JYNw@A*v/sdq59DUkhE+(X`c
-0RAG-Y,3@eQ?=B'2e-o#aFUQZ"V9zn\ nBRs
-XMsikYGBZ;2N\o!kX.OB,EoecF
-tµ’Ä(hÛ)%RK<r>5 f4Q7.I<Cw)5 Q&x>vMIXU2]b"rjeV>MpR/).9xc!DvgB)@!r VsRO_%&M^!&"NEi|qt.<
-`*Uk_Fm*gy2b!HtWm-}X:+:md(E\Uam:c0W.c]l:*ROF3(W(rg-9m]/TeREMNYxGp(+m.lXqHD%,2lMt,M[0e_ |Q"@x37
-+hF@S^pJ]Ih~Vvw-Ju ;,hh<GSL/ ^5[,@ECuô_‘Bhb
-v\ 0
-h Ah E||?g).UQaG}K=if>z&Dss9 XYUCSA
-^ v/C7b<.z~U
-z@R[StV&mZ&C" 7A}.i9zG1[&lsfzM%N x|Xw&B Ohm1o+0O)hF
-LM`j=FS$kf@Rw¯ ¤îxqÝO[MJ;o@@,I;5l-y
-endobj
-892 0 obj <<
-/Type /Font
-/Subtype /Type1
-/Encoding 1790 0 R
-/FirstChar 11
-/LastChar 122
-/Widths 1791 0 R
-/BaseFont /SNTQWX+CMTI10
-/FontDescriptor 890 0 R
->> endobj
-890 0 obj <<
-/Ascent 694
-/CapHeight 683
-/Descent -194
-/FontName /SNTQWX+CMTI10
-/ItalicAngle -14
-/StemV 68
-/XHeight 431
-/FontBBox [-163 -250 1146 969]
-/Flags 4
-/CharSet (/ff/fi/fl/quotedblright/numbersign/quoteright/parenleft/parenright/plus/comma/hyphen/period/slash/zero/one/two/four/five/six/colon/semicolon/question/A/B/C/D/E/F/G/I/L/M/N/O/P/Q/R/S/T/U/V/X/Y/a/b/c/d/e/f/g/h/i/k/l/m/n/o/p/q/r/s/t/u/v/w/x/y/z)
-/FontFile 891 0 R
->> endobj
-1791 0 obj
-[613 562 588 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 514 818 0 0 0 307 409 409 0 767 307 358 307 511 511 511 511 0 511 511 511 0 0 0 307 307 0 0 0 511 0 743 704 716 755 678 653 774 0 386 0 0 627 897 743 767 678 767 729 562 716 743 743 0 743 743 0 0 0 0 0 0 0 511 460 460 511 460 307 460 511 307 0 460 256 818 562 511 511 460 422 409 332 537 460 664 464 486 409 ]
-endobj
-1792 0 obj <<
-/Type /Encoding
-/Differences [ 0 /Gamma/Delta/Theta/Lambda/Xi/Pi/Sigma/Upsilon/Phi/Psi/Omega/arrowup/arrowdown/quotesingle/exclamdown/questiondown/dotlessi/dotlessj/grave/acute/caron/breve/macron/ring/cedilla/germandbls/ae/oe/oslash/AE/OE/Oslash/suppress/exclam/quotedblright/numbersign/dollar/percent/ampersand/quoteright/parenleft/parenright/asterisk/plus/comma/hyphen/period/slash/zero/one/two/three/four/five/six/seven/eight/nine/colon/semicolon/less/equal/greater/question/at/A/B/C/D/E/F/G/H/I/J/K/L/M/N/O/P/Q/R/S/T/U/V/W/X/Y/Z/bracketleft/quotedblleft/bracketright/circumflex/dotaccent/quoteleft/a/b/c/d/e/f/g/h/i/j/k/l/m/n/o/p/q/r/s/t/u/v/w/x/y/z/endash/emdash/hungarumlaut/tilde/dieresis/suppress 129/.notdef 160/space/Gamma/Delta/Theta/Lambda/Xi/Pi/Sigma/Upsilon/Phi/Psi 171/.notdef 173/Omega/arrowup/arrowdown/quotesingle/exclamdown/questiondown/dotlessi/dotlessj/grave/acute/caron/breve/macron/ring/cedilla/germandbls/ae/oe/oslash/AE/OE/Oslash/suppress/dieresis 197/.notdef]
->> endobj
-887 0 obj <<
-/Length1 850
-/Length2 2165
-/Length3 532
-/Length 2768
-/Filter /FlateDecode
->>
-stream
-xRy<N)5(Ecy%[eK)XQC1bwg*%!NGZ -[SP9}|y?eEk[ ,rM!:K@8<Fh
-cDY>CX'
-L6 )$zR0%s~+-'0 LdN
-M6\?b.B M #IIa4W eiOY^pM/2y2FGE­›¶÷04v^$´I"[Dm
-/Ktx}K4hD9nJ=yvqXdYS5 n \'0~..Kcxv;Md0q-'*FFdU&f7O*&`.F)z<wHaZ&53xZ:C3]pbo|
-V@?R8r~3a\lK_BM/~yO& )KRcUqw*?*|i",asJSVXn/NduOUm<1;G+OO_@q6 TpkZqRVtV]ZXy=a 2KO{SLf
-79/U.]h":.anVt:}WzLvUn%;qmilpQbry.`B=J!W-*h2d+;V#zEgftothl`jT,-8QfyO#UPCÝw„eTM0>2>o<~e6MsknG-.
-,Fd ^}endstream
-endobj
-888 0 obj <<
-/Type /Font
-/Subtype /Type1
-/Encoding 1792 0 R
-/FirstChar 65
-/LastChar 116
-/Widths 1793 0 R
-/BaseFont /TBPDHW+CMCSC10
-/FontDescriptor 886 0 R
->> endobj
-886 0 obj <<
-/Ascent 514
-/CapHeight 683
-/Descent 0
-/FontName /TBPDHW+CMCSC10
-/ItalicAngle 0
-/StemV 72
-/XHeight 431
-/FontBBox [14 -250 1077 750]
-/Flags 4
-/CharSet (/A/a/b/c/r/s/t)
-/FontFile 887 0 R
->> endobj
-1793 0 obj
-[814 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 613 580 591 0 0 0 0 0 0 0 0 0 0 0 0 0 0 602 458 591 ]
-endobj
-879 0 obj <<
-/Length1 969
-/Length2 3492
-/Length3 532
-/Length 4169
-/Filter /FlateDecode
->>
-stream
-xy<C%d"DN2ndc03[(C$H,!Bd })B%~S=wzs|KTa&wBqDiLa2
-Fd="nF7KfD8,:r(&Iz-tw(#!v\>w}|L2~&C%C=^>8vs[yU9)$Hb%za8*G
-H 8ihj3[(Z.UN\5w`rh#~.*1(%{ou=_G?Qc^c^xrqD 4H*0.gTx<s7b\9X/Qp3
-FI,Ip){zZm°öÞ§I6VPS?REf
-Ot$/b\n3NY*UG}•Ì¸Äí2|\0/u°ÏhŒªuçðNd0oe@^vqka|"UM>MhqjviRF|x{R/10Vmv31ZG b{IruP7?Y 8v^wuy4IsG~dFQ+{0k[_<2MuhTjkf3Om/u>XYYp0!h)&K 0@5H5_xbW4$02 b%J>mz>6gPVZ4" Q]jˆ>ð£Ff]>R(<jt,&S]v]99l^2g/w+}xV@TtU`f4w]FDM%939"N\_E~8uHpV'#b;ASv =6+ Q!e-6wY9
- 2~R){)GudR2F}Lc1 .U{RxAo~Ycze[it_:eLG1.BOTzg]k__>rO|^w6
-^[r)4]jd%;^u&XUo4FO,y1\=<J*+6SAH<H6pW$g
-E$MOqbg]2{!mmg`1)7Bo[=|Sbv5p,/alXxg;(%S
-\|06A4k"Sp~;'q?\Sh_IdLf+TK@+j;c^!fBDM/-gPi,c3 2d5}
-.rx)Of"YZu"(w}'y.
-X]rYTs<i\uFT[C/ bHOnP,0~EiXY]&{Hp4A'cs$i=o+`B| gÉÜß®³ÒY)b7?9,G*^?m>Z~O&W.Zo E
-)~ <P\C
-z#!Yo[WEUKa8o>iNqGMwg)uY2s%wr:0<$z!{Zox(nJ$E9r{P4$0sw?g<? N]
-][xj)ci^8@O,{|v<-!0^;B3k;|k,7po|p(`8kzi38w}>v [[76WT[<Wk0%a
-xeI qeNpTWh0_]oy[:+~ FExP7Fslldz
-aCZdAd(X7Bt,^=='iV[v($Oq7kP~.}6iY]jx6wogt1AW"nPU5[lqAG4 _*ߦԥ|pž¼
-endobj
-880 0 obj <<
-/Type /Font
-/Subtype /Type1
-/Encoding 1781 0 R
-/FirstChar 48
-/LastChar 121
-/Widths 1794 0 R
-/BaseFont /PORZYW+CMR12
-/FontDescriptor 878 0 R
->> endobj
-878 0 obj <<
-/Ascent 694
-/CapHeight 683
-/Descent -194
-/FontName /PORZYW+CMR12
-/ItalicAngle 0
-/StemV 65
-/XHeight 431
-/FontBBox [-34 -251 988 750]
-/Flags 4
-/CharSet (/zero/one/two/three/A/B/M/S/T/a/e/m/s/t/y)
-/FontFile 879 0 R
->> endobj
-1794 0 obj
-[490 490 490 490 0 0 0 0 0 0 0 0 0 0 0 0 0 734 693 0 0 0 0 0 0 0 0 0 0 897 0 0 0 0 0 544 707 0 0 0 0 0 0 0 0 0 0 0 0 490 0 0 0 435 0 0 0 0 0 0 0 816 0 0 0 0 0 386 381 0 0 0 0 517 ]
-endobj
-876 0 obj <<
-/Length1 1972
-/Length2 11871
-/Length3 532
-/Length 12951
-/Filter /FlateDecode
->>
-stream
-xUX\]h;
- \w` Hp <;wwS:ns=s&WRe6%@NLXy",
-4
-00v,lq5#ll_C.@G,I
-^ufh`7s
-G -
-Vdj$
-e98OIWbgq{3U^3ECCo8cm}m*
-hsR>Y=%bZ g
-oBU&VF_5Y.-SM'†qËè:õØ\<¿céo L>fxSVp#:T[
-kU"OjRd|<zwF)6nMRC[0^'v]q~/8?-t]69g!pKS=tB*)RGe'<]V[oI
-1|:Ca"fm=9Wn#Re|/MGnH:Q`D.$NOG 0UQ(l$o6eJ)\?N^,6.z"36|*oKooS& ^oP}{rl3K |Mk&@~acWvW-4~Unc54%P rwSRt0h?wE* <.?X@M>d@s#'zrpOJ?|4TNKPK|`7`RK(6SeNQP5.kr
-SHO&}|5&YG)#CE`eY)RCTdpQK/%_EQvSTJbgb.CN\v17>
- kB
-h&nf+mv3R?h7V0;t$'J@%b¦Çûڍq$)©Â°ÖÑõë6M"9=LC5t ]u9P$}60d!"Gn,,:XzC4L DAxz+I-0a+AzdmRseSc2Br2Z,mJ~2vzhjO (fK'?oe+[W"rl#[J@{hNBfg7dK} =dA(ecl8{%'_3jHP9m?Omx(2} *c%$cXY
-p/ O#jQQ>:?|K4ü|{"c©Ü|h3KWra3Ax8
-D-b|0E]WjB8C+F}rVpa!V SC!Ge1Ia_1zy:(+^@Ls3-~X/^FdQc,J8-Ry)ka`KNi`uQ!#:!z'x2y*!m.wB>5j. )0GAsxz .c;-#j`TX[tinP9MZOC9H0e2xAVaQ&mT4>Sµ•Ÿ³ÛQ,6gP.l . P7@c#~Y{<Xzho(j0@}rp
-4MHVQmnAC*TZirpS5O@GA(q@V
-4V%JfwSuC[r} k1j;r]Q/g7$I@ R X_YM2c>R~h;cbE 9*Ete%5aVJd5Q:_;2h:\`PX|JXtV[xf]sl!iK
-Asj+geUgãöêO3UyuVr$OgdiyD+|
- -/S-"'L ;^osb<"|0Oh"jnA rP`_tE[A6c1
-ac/Kvic?}jDmy_0xF]z 8eb]g`WI~sj; ,E[(DKAB{ +;M
-nGaVxqS_GA6|p#$3~~93h67SE{uR@ qQF EM(v3t
-acIR;5aqApKov&cH.W:8G{*E"OkP6i:k6
-R|"h|q8$5ff3[>]\fd)n}!_#${f+yol"Wfu)o~Kp] _ PI]_n_T{7rur­‡×Œ<,P+8\e!$pc>5~(*<bt!I)+|:<7w9(Uv]2()+E.<A)WoV`n`)
-nw0iY vmd#A}&Ek<e2(s7#4U <aVH*pHn:Ü-–ò¬<Æü÷î“4KQ*Mu^3?'.Ô•ÛEgW=%(E_|NjPEnI5%RV1o-5XA+%4((ll|kk,-2IY/loggoyöÆÊKS`n\
-Gk2KE&2rbdW0AEnh.$o-~PBrUC"w  `|
-]] -|
-TNl3iw.V))67eGLF3qT3l7;&C?u91X>wjZNE 8-I%I<7QC5OGA73yN}&ND>:^*Ye_f"w*p[8MTc"l|8*,p&S3l]<P_t3*!g5% y,z-9SLX9K<|i|C-i0LbZYbmM&c/[oyb5 e'|>k$p [/!#_dU&` ;B5u!Š8ï©!ýdÉîD_W:jh`"Pu% WTFzuNcbV
-{<Tm*2mO:! !U/>.;]J;Z$Tj2qlomQ"IaA_=>3<4x.7$b|tPa)PNB$'M|{
-(aqH6 AM7|Fi!Hx&cbgv5 K9w6jThork'm<# 4(8BmpXU% |g=@zhx'LJL q6ZwdyU@9FN;gX-z $/cBDv"rW>}9&V*k3#jDzHwC*Et/U(XfX>]`dKlYY1<U|rxc =,%LU 4e=[Qamld";t?@+2d:dp;hl[qQ=UFcu4E
-ai<ZuS5wD- 7@yT&/~}o1|im d('|x9v:iT:i&[uOeQT7Ve57LmLFL}!lo
-6&-/xZ.B] WxN: L
-SS<({e
-J
-HvE QtYn]\#y$a#N+]Nf 6}=/o?f ;5gj*eCYtP~x9bta:,
-WRb#^SS#c$tZp^O0k[>9j6QIRtmG9Q0h< AxI:nEU;I-r>Yy!w||ZLQn+/Z.F'Dvyy.@%o+ no:MLj)%GY
-q0oKW/JcU!6n8wI[C
-GKp<y$%\@FJ 7[[-h/b\K WgI4$HCo40áè\ò2i/ˆ?æãÏ햇£âqïƒ{7<¿†<ÑÅ-ß½Av:o,p/\7BP4@2*dCIQzeudT;w- (H}y\{61}n_gd2+fRujEV^D96 6Fc7ÍSl-Zr:i 7l$P[BiS
-P.mq 1)GvpY|<;((du}
-v$\1Hj,
-y%dVkV*(wHa+'$cPJ8nNs?v1`ó"Âñõю¬Î X~7/6pxK
-R
-mH[]Xc+98
- UX3 #=@6 M'[&
-q+dFBc5v|}ljJ5~J6Qf!0'EÜð'+Iu "}Ltp
-}MgyQcLoebt<&!4 1i=5:[RXmI/xa GP@ ~b jUWuH A#Y h^wh< 1
-r nJv:S1(-K#vStf-
-}3<;b?=)!aJSA
-b %Wql A">Dk[H_D6QpL_pB#?nKL%| n\4gBQM=n'u,nNL).C+1 B Ee8½O&sIo^Rn3ee8??:i5ca'ZoQUi"rRGQ{0S@ O*PPc8(?]3 ~w%lgHn
-Cvf J03.(7/R44"Mam'B|cj$ <ms%)W2H|G4g^a)/ToAPCWs]^'=R[.-0K?.7pECo=6(cr>,U@N(DeNmnelrV& >)>e6a./n Cc89m]81Q\~02qC^&en}ZF.U(K$gE0/V~v;8_h~7e-Afrc-Iz`#=-ifiC
-~X/uf}#k*?ADr";2j2d @nSff/b
-Yr%9y[sCbpz5+mdTI7c3zídt‡¯€a…TE*/f1{p8&E\X=y_!Rf/F(R'Vu#OwLM Nh59_^%"kYK gs~7^%ls.# # j-.)`!n4i;@qc\`?MYo_@[sBbVe,_+[ @6VHendstream
-endobj
-877 0 obj <<
-/Type /Font
-/Subtype /Type1
-/Encoding 1781 0 R
-/FirstChar 11
-/LastChar 122
-/Widths 1795 0 R
-/BaseFont /JXXTGO+CMSSBX10
-/FontDescriptor 875 0 R
->> endobj
-875 0 obj <<
-/Ascent 694
-/CapHeight 694
-/Descent -194
-/FontName /JXXTGO+CMSSBX10
-/ItalicAngle 0
-/StemV 136
-/XHeight 458
-/FontBBox [-71 -250 1099 780]
-/Flags 4
-/CharSet (/ff/fi/fl/quotedblright/quoteright/parenleft/parenright/asterisk/plus/comma/hyphen/period/slash/zero/one/two/three/four/five/six/seven/eight/nine/colon/question/A/B/C/D/E/F/G/H/I/J/K/L/M/N/O/P/Q/R/S/T/U/V/W/X/Y/bracketleft/a/b/c/d/e/f/g/h/i/j/k/l/m/n/o/p/q/r/s/t/u/v/w/x/y/z)
-/FontFile 876 0 R
->> endobj
-1795 0 obj
-[642 586 586 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 558 0 0 0 0 306 428 428 550 856 306 367 306 550 550 550 550 550 550 550 550 550 550 550 306 0 0 0 0 519 0 733 733 703 794 642 611 733 794 331 519 764 581 978 794 794 703 794 703 611 733 764 733 1039 733 733 0 343 0 0 0 0 0 525 561 489 561 511 336 550 561 256 286 531 256 867 561 550 561 561 372 422 404 561 500 744 500 500 476 ]
-endobj
-881 0 obj <<
-/Type /Pages
-/Count 6
-/Parent 1796 0 R
-/Kids [870 0 R 883 0 R 906 0 R 951 0 R 1007 0 R 1063 0 R]
->> endobj
-1148 0 obj <<
-/Type /Pages
-/Count 6
-/Parent 1796 0 R
-/Kids [1120 0 R 1150 0 R 1157 0 R 1165 0 R 1180 0 R 1188 0 R]
->> endobj
-1202 0 obj <<
-/Type /Pages
-/Count 6
-/Parent 1796 0 R
-/Kids [1198 0 R 1204 0 R 1210 0 R 1221 0 R 1236 0 R 1257 0 R]
->> endobj
-1289 0 obj <<
-/Type /Pages
-/Count 6
-/Parent 1796 0 R
-/Kids [1272 0 R 1291 0 R 1310 0 R 1324 0 R 1339 0 R 1358 0 R]
->> endobj
-1372 0 obj <<
-/Type /Pages
-/Count 6
-/Parent 1796 0 R
-/Kids [1363 0 R 1374 0 R 1382 0 R 1389 0 R 1396 0 R 1400 0 R]
->> endobj
-1414 0 obj <<
-/Type /Pages
-/Count 6
-/Parent 1796 0 R
-/Kids [1411 0 R 1416 0 R 1434 0 R 1447 0 R 1459 0 R 1470 0 R]
->> endobj
-1487 0 obj <<
-/Type /Pages
-/Count 6
-/Parent 1797 0 R
-/Kids [1479 0 R 1489 0 R 1496 0 R 1502 0 R 1508 0 R 1514 0 R]
->> endobj
-1525 0 obj <<
-/Type /Pages
-/Count 6
-/Parent 1797 0 R
-/Kids [1520 0 R 1527 0 R 1536 0 R 1544 0 R 1550 0 R 1562 0 R]
->> endobj
-1581 0 obj <<
-/Type /Pages
-/Count 6
-/Parent 1797 0 R
-/Kids [1574 0 R 1583 0 R 1591 0 R 1602 0 R 1612 0 R 1621 0 R]
->> endobj
-1638 0 obj <<
-/Type /Pages
-/Count 6
-/Parent 1797 0 R
-/Kids [1629 0 R 1640 0 R 1646 0 R 1654 0 R 1662 0 R 1670 0 R]
->> endobj
-1687 0 obj <<
-/Type /Pages
-/Count 6
-/Parent 1797 0 R
-/Kids [1680 0 R 1689 0 R 1693 0 R 1697 0 R 1703 0 R 1709 0 R]
->> endobj
-1726 0 obj <<
-/Type /Pages
-/Count 6
-/Parent 1797 0 R
-/Kids [1719 0 R 1728 0 R 1733 0 R 1740 0 R 1746 0 R 1750 0 R]
->> endobj
-1764 0 obj <<
-/Type /Pages
-/Count 3
-/Parent 1798 0 R
-/Kids [1759 0 R 1766 0 R 1773 0 R]
->> endobj
-1796 0 obj <<
-/Type /Pages
-/Count 36
-/Parent 1799 0 R
-/Kids [881 0 R 1148 0 R 1202 0 R 1289 0 R 1372 0 R 1414 0 R]
->> endobj
-1797 0 obj <<
-/Type /Pages
-/Count 36
-/Parent 1799 0 R
-/Kids [1487 0 R 1525 0 R 1581 0 R 1638 0 R 1687 0 R 1726 0 R]
->> endobj
-1798 0 obj <<
-/Type /Pages
-/Count 3
-/Parent 1799 0 R
-/Kids [1764 0 R]
->> endobj
-1799 0 obj <<
-/Type /Pages
-/Count 75
-/Kids [1796 0 R 1797 0 R 1798 0 R]
->> endobj
-1800 0 obj <<
-/Type /Outlines
-/First 7 0 R
-/Last 859 0 R
-/Count 16
->> endobj
-867 0 obj <<
-/Title 868 0 R
-/A 865 0 R
-/Parent 859 0 R
-/Prev 863 0 R
->> endobj
-863 0 obj <<
-/Title 864 0 R
-/A 861 0 R
-/Parent 859 0 R
-/Next 867 0 R
->> endobj
-859 0 obj <<
-/Title 860 0 R
-/A 857 0 R
-/Parent 1800 0 R
-/Prev 847 0 R
-/First 863 0 R
-/Last 867 0 R
-/Count -2
->> endobj
-855 0 obj <<
-/Title 856 0 R
-/A 853 0 R
-/Parent 847 0 R
-/Prev 851 0 R
->> endobj
-851 0 obj <<
-/Title 852 0 R
-/A 849 0 R
-/Parent 847 0 R
-/Next 855 0 R
->> endobj
-847 0 obj <<
-/Title 848 0 R
-/A 845 0 R
-/Parent 1800 0 R
-/Prev 819 0 R
-/Next 859 0 R
-/First 851 0 R
-/Last 855 0 R
-/Count -2
->> endobj
-843 0 obj <<
-/Title 844 0 R
-/A 841 0 R
-/Parent 839 0 R
->> endobj
-839 0 obj <<
-/Title 840 0 R
-/A 837 0 R
-/Parent 819 0 R
-/Prev 827 0 R
-/First 843 0 R
-/Last 843 0 R
-/Count -1
->> endobj
-835 0 obj <<
-/Title 836 0 R
-/A 833 0 R
-/Parent 827 0 R
-/Prev 831 0 R
->> endobj
-831 0 obj <<
-/Title 832 0 R
-/A 829 0 R
-/Parent 827 0 R
-/Next 835 0 R
->> endobj
-827 0 obj <<
-/Title 828 0 R
-/A 825 0 R
-/Parent 819 0 R
-/Prev 823 0 R
-/Next 839 0 R
-/First 831 0 R
-/Last 835 0 R
-/Count -2
->> endobj
-823 0 obj <<
-/Title 824 0 R
-/A 821 0 R
-/Parent 819 0 R
-/Next 827 0 R
->> endobj
-819 0 obj <<
-/Title 820 0 R
-/A 817 0 R
-/Parent 1800 0 R
-/Prev 803 0 R
-/Next 847 0 R
-/First 823 0 R
-/Last 839 0 R
-/Count -3
->> endobj
-815 0 obj <<
-/Title 816 0 R
-/A 813 0 R
-/Parent 803 0 R
-/Prev 811 0 R
->> endobj
-811 0 obj <<
-/Title 812 0 R
-/A 809 0 R
-/Parent 803 0 R
-/Prev 807 0 R
-/Next 815 0 R
->> endobj
-807 0 obj <<
-/Title 808 0 R
-/A 805 0 R
-/Parent 803 0 R
-/Next 811 0 R
->> endobj
-803 0 obj <<
-/Title 804 0 R
-/A 801 0 R
-/Parent 1800 0 R
-/Prev 751 0 R
-/Next 819 0 R
-/First 807 0 R
-/Last 815 0 R
-/Count -3
->> endobj
-799 0 obj <<
-/Title 800 0 R
-/A 797 0 R
-/Parent 751 0 R
-/Prev 795 0 R
->> endobj
-795 0 obj <<
-/Title 796 0 R
-/A 793 0 R
-/Parent 751 0 R
-/Prev 783 0 R
-/Next 799 0 R
->> endobj
-791 0 obj <<
-/Title 792 0 R
-/A 789 0 R
-/Parent 783 0 R
-/Prev 787 0 R
->> endobj
-787 0 obj <<
-/Title 788 0 R
-/A 785 0 R
-/Parent 783 0 R
-/Next 791 0 R
->> endobj
-783 0 obj <<
-/Title 784 0 R
-/A 781 0 R
-/Parent 751 0 R
-/Prev 767 0 R
-/Next 795 0 R
-/First 787 0 R
-/Last 791 0 R
-/Count -2
->> endobj
-779 0 obj <<
-/Title 780 0 R
-/A 777 0 R
-/Parent 767 0 R
-/Prev 775 0 R
->> endobj
-775 0 obj <<
-/Title 776 0 R
-/A 773 0 R
-/Parent 767 0 R
-/Prev 771 0 R
-/Next 779 0 R
->> endobj
-771 0 obj <<
-/Title 772 0 R
-/A 769 0 R
-/Parent 767 0 R
-/Next 775 0 R
->> endobj
-767 0 obj <<
-/Title 768 0 R
-/A 765 0 R
-/Parent 751 0 R
-/Prev 763 0 R
-/Next 783 0 R
-/First 771 0 R
-/Last 779 0 R
-/Count -3
->> endobj
-763 0 obj <<
-/Title 764 0 R
-/A 761 0 R
-/Parent 751 0 R
-/Prev 759 0 R
-/Next 767 0 R
->> endobj
-759 0 obj <<
-/Title 760 0 R
-/A 757 0 R
-/Parent 751 0 R
-/Prev 755 0 R
-/Next 763 0 R
->> endobj
-755 0 obj <<
-/Title 756 0 R
-/A 753 0 R
-/Parent 751 0 R
-/Next 759 0 R
->> endobj
-751 0 obj <<
-/Title 752 0 R
-/A 749 0 R
-/Parent 1800 0 R
-/Prev 743 0 R
-/Next 803 0 R
-/First 755 0 R
-/Last 799 0 R
-/Count -7
->> endobj
-747 0 obj <<
-/Title 748 0 R
-/A 745 0 R
-/Parent 743 0 R
->> endobj
-743 0 obj <<
-/Title 744 0 R
-/A 741 0 R
-/Parent 1800 0 R
-/Prev 719 0 R
-/Next 751 0 R
-/First 747 0 R
-/Last 747 0 R
-/Count -1
->> endobj
-739 0 obj <<
-/Title 740 0 R
-/A 737 0 R
-/Parent 719 0 R
-/Prev 735 0 R
->> endobj
-735 0 obj <<
-/Title 736 0 R
-/A 733 0 R
-/Parent 719 0 R
-/Prev 731 0 R
-/Next 739 0 R
->> endobj
-731 0 obj <<
-/Title 732 0 R
-/A 729 0 R
-/Parent 719 0 R
-/Prev 727 0 R
-/Next 735 0 R
->> endobj
-727 0 obj <<
-/Title 728 0 R
-/A 725 0 R
-/Parent 719 0 R
-/Prev 723 0 R
-/Next 731 0 R
->> endobj
-723 0 obj <<
-/Title 724 0 R
-/A 721 0 R
-/Parent 719 0 R
-/Next 727 0 R
->> endobj
-719 0 obj <<
-/Title 720 0 R
-/A 717 0 R
-/Parent 1800 0 R
-/Prev 251 0 R
-/Next 743 0 R
-/First 723 0 R
-/Last 739 0 R
-/Count -5
->> endobj
-715 0 obj <<
-/Title 716 0 R
-/A 713 0 R
-/Parent 703 0 R
-/Prev 711 0 R
->> endobj
-711 0 obj <<
-/Title 712 0 R
-/A 709 0 R
-/Parent 703 0 R
-/Prev 707 0 R
-/Next 715 0 R
->> endobj
-707 0 obj <<
-/Title 708 0 R
-/A 705 0 R
-/Parent 703 0 R
-/Next 711 0 R
->> endobj
-703 0 obj <<
-/Title 704 0 R
-/A 701 0 R
-/Parent 687 0 R
-/Prev 691 0 R
-/First 707 0 R
-/Last 715 0 R
-/Count -3
->> endobj
-699 0 obj <<
-/Title 700 0 R
-/A 697 0 R
-/Parent 691 0 R
-/Prev 695 0 R
->> endobj
-695 0 obj <<
-/Title 696 0 R
-/A 693 0 R
-/Parent 691 0 R
-/Next 699 0 R
->> endobj
-691 0 obj <<
-/Title 692 0 R
-/A 689 0 R
-/Parent 687 0 R
-/Next 703 0 R
-/First 695 0 R
-/Last 699 0 R
-/Count -2
->> endobj
-687 0 obj <<
-/Title 688 0 R
-/A 685 0 R
-/Parent 251 0 R
-/Prev 671 0 R
-/First 691 0 R
-/Last 703 0 R
-/Count -2
->> endobj
-683 0 obj <<
-/Title 684 0 R
-/A 681 0 R
-/Parent 671 0 R
-/Prev 679 0 R
->> endobj
-679 0 obj <<
-/Title 680 0 R
-/A 677 0 R
-/Parent 671 0 R
-/Prev 675 0 R
-/Next 683 0 R
->> endobj
-675 0 obj <<
-/Title 676 0 R
-/A 673 0 R
-/Parent 671 0 R
-/Next 679 0 R
->> endobj
-671 0 obj <<
-/Title 672 0 R
-/A 669 0 R
-/Parent 251 0 R
-/Prev 643 0 R
-/Next 687 0 R
-/First 675 0 R
-/Last 683 0 R
-/Count -3
->> endobj
-667 0 obj <<
-/Title 668 0 R
-/A 665 0 R
-/Parent 659 0 R
-/Prev 663 0 R
->> endobj
-663 0 obj <<
-/Title 664 0 R
-/A 661 0 R
-/Parent 659 0 R
-/Next 667 0 R
->> endobj
-659 0 obj <<
-/Title 660 0 R
-/A 657 0 R
-/Parent 643 0 R
-/Prev 647 0 R
-/First 663 0 R
-/Last 667 0 R
-/Count -2
->> endobj
-655 0 obj <<
-/Title 656 0 R
-/A 653 0 R
-/Parent 647 0 R
-/Prev 651 0 R
->> endobj
-651 0 obj <<
-/Title 652 0 R
-/A 649 0 R
-/Parent 647 0 R
-/Next 655 0 R
->> endobj
-647 0 obj <<
-/Title 648 0 R
-/A 645 0 R
-/Parent 643 0 R
-/Next 659 0 R
-/First 651 0 R
-/Last 655 0 R
-/Count -2
->> endobj
-643 0 obj <<
-/Title 644 0 R
-/A 641 0 R
-/Parent 251 0 R
-/Prev 615 0 R
-/Next 671 0 R
-/First 647 0 R
-/Last 659 0 R
-/Count -2
->> endobj
-639 0 obj <<
-/Title 640 0 R
-/A 637 0 R
-/Parent 631 0 R
-/Prev 635 0 R
->> endobj
-635 0 obj <<
-/Title 636 0 R
-/A 633 0 R
-/Parent 631 0 R
-/Next 639 0 R
->> endobj
-631 0 obj <<
-/Title 632 0 R
-/A 629 0 R
-/Parent 615 0 R
-/Prev 619 0 R
-/First 635 0 R
-/Last 639 0 R
-/Count -2
->> endobj
-627 0 obj <<
-/Title 628 0 R
-/A 625 0 R
-/Parent 619 0 R
-/Prev 623 0 R
->> endobj
-623 0 obj <<
-/Title 624 0 R
-/A 621 0 R
-/Parent 619 0 R
-/Next 627 0 R
->> endobj
-619 0 obj <<
-/Title 620 0 R
-/A 617 0 R
-/Parent 615 0 R
-/Next 631 0 R
-/First 623 0 R
-/Last 627 0 R
-/Count -2
->> endobj
-615 0 obj <<
-/Title 616 0 R
-/A 613 0 R
-/Parent 251 0 R
-/Prev 551 0 R
-/Next 643 0 R
-/First 619 0 R
-/Last 631 0 R
-/Count -2
->> endobj
-611 0 obj <<
-/Title 612 0 R
-/A 609 0 R
-/Parent 603 0 R
-/Prev 607 0 R
->> endobj
-607 0 obj <<
-/Title 608 0 R
-/A 605 0 R
-/Parent 603 0 R
-/Next 611 0 R
->> endobj
-603 0 obj <<
-/Title 604 0 R
-/A 601 0 R
-/Parent 551 0 R
-/Prev 591 0 R
-/First 607 0 R
-/Last 611 0 R
-/Count -2
->> endobj
-599 0 obj <<
-/Title 600 0 R
-/A 597 0 R
-/Parent 591 0 R
-/Prev 595 0 R
->> endobj
-595 0 obj <<
-/Title 596 0 R
-/A 593 0 R
-/Parent 591 0 R
-/Next 599 0 R
->> endobj
-591 0 obj <<
-/Title 592 0 R
-/A 589 0 R
-/Parent 551 0 R
-/Prev 579 0 R
-/Next 603 0 R
-/First 595 0 R
-/Last 599 0 R
-/Count -2
->> endobj
-587 0 obj <<
-/Title 588 0 R
-/A 585 0 R
-/Parent 579 0 R
-/Prev 583 0 R
->> endobj
-583 0 obj <<
-/Title 584 0 R
-/A 581 0 R
-/Parent 579 0 R
-/Next 587 0 R
->> endobj
-579 0 obj <<
-/Title 580 0 R
-/A 577 0 R
-/Parent 551 0 R
-/Prev 567 0 R
-/Next 591 0 R
-/First 583 0 R
-/Last 587 0 R
-/Count -2
->> endobj
-575 0 obj <<
-/Title 576 0 R
-/A 573 0 R
-/Parent 567 0 R
-/Prev 571 0 R
->> endobj
-571 0 obj <<
-/Title 572 0 R
-/A 569 0 R
-/Parent 567 0 R
-/Next 575 0 R
->> endobj
-567 0 obj <<
-/Title 568 0 R
-/A 565 0 R
-/Parent 551 0 R
-/Prev 555 0 R
-/Next 579 0 R
-/First 571 0 R
-/Last 575 0 R
-/Count -2
->> endobj
-563 0 obj <<
-/Title 564 0 R
-/A 561 0 R
-/Parent 555 0 R
-/Prev 559 0 R
->> endobj
-559 0 obj <<
-/Title 560 0 R
-/A 557 0 R
-/Parent 555 0 R
-/Next 563 0 R
->> endobj
-555 0 obj <<
-/Title 556 0 R
-/A 553 0 R
-/Parent 551 0 R
-/Next 567 0 R
-/First 559 0 R
-/Last 563 0 R
-/Count -2
->> endobj
-551 0 obj <<
-/Title 552 0 R
-/A 549 0 R
-/Parent 251 0 R
-/Prev 411 0 R
-/Next 615 0 R
-/First 555 0 R
-/Last 603 0 R
-/Count -5
->> endobj
-547 0 obj <<
-/Title 548 0 R
-/A 545 0 R
-/Parent 539 0 R
-/Prev 543 0 R
->> endobj
-543 0 obj <<
-/Title 544 0 R
-/A 541 0 R
-/Parent 539 0 R
-/Next 547 0 R
->> endobj
-539 0 obj <<
-/Title 540 0 R
-/A 537 0 R
-/Parent 411 0 R
-/Prev 527 0 R
-/First 543 0 R
-/Last 547 0 R
-/Count -2
->> endobj
-535 0 obj <<
-/Title 536 0 R
-/A 533 0 R
-/Parent 527 0 R
-/Prev 531 0 R
->> endobj
-531 0 obj <<
-/Title 532 0 R
-/A 529 0 R
-/Parent 527 0 R
-/Next 535 0 R
->> endobj
-527 0 obj <<
-/Title 528 0 R
-/A 525 0 R
-/Parent 411 0 R
-/Prev 515 0 R
-/Next 539 0 R
-/First 531 0 R
-/Last 535 0 R
-/Count -2
->> endobj
-523 0 obj <<
-/Title 524 0 R
-/A 521 0 R
-/Parent 515 0 R
-/Prev 519 0 R
->> endobj
-519 0 obj <<
-/Title 520 0 R
-/A 517 0 R
-/Parent 515 0 R
-/Next 523 0 R
->> endobj
-515 0 obj <<
-/Title 516 0 R
-/A 513 0 R
-/Parent 411 0 R
-/Prev 503 0 R
-/Next 527 0 R
-/First 519 0 R
-/Last 523 0 R
-/Count -2
->> endobj
-511 0 obj <<
-/Title 512 0 R
-/A 509 0 R
-/Parent 503 0 R
-/Prev 507 0 R
->> endobj
-507 0 obj <<
-/Title 508 0 R
-/A 505 0 R
-/Parent 503 0 R
-/Next 511 0 R
->> endobj
-503 0 obj <<
-/Title 504 0 R
-/A 501 0 R
-/Parent 411 0 R
-/Prev 491 0 R
-/Next 515 0 R
-/First 507 0 R
-/Last 511 0 R
-/Count -2
->> endobj
-499 0 obj <<
-/Title 500 0 R
-/A 497 0 R
-/Parent 491 0 R
-/Prev 495 0 R
->> endobj
-495 0 obj <<
-/Title 496 0 R
-/A 493 0 R
-/Parent 491 0 R
-/Next 499 0 R
->> endobj
-491 0 obj <<
-/Title 492 0 R
-/A 489 0 R
-/Parent 411 0 R
-/Prev 479 0 R
-/Next 503 0 R
-/First 495 0 R
-/Last 499 0 R
-/Count -2
->> endobj
-487 0 obj <<
-/Title 488 0 R
-/A 485 0 R
-/Parent 479 0 R
-/Prev 483 0 R
->> endobj
-483 0 obj <<
-/Title 484 0 R
-/A 481 0 R
-/Parent 479 0 R
-/Next 487 0 R
->> endobj
-479 0 obj <<
-/Title 480 0 R
-/A 477 0 R
-/Parent 411 0 R
-/Prev 467 0 R
-/Next 491 0 R
-/First 483 0 R
-/Last 487 0 R
-/Count -2
->> endobj
-475 0 obj <<
-/Title 476 0 R
-/A 473 0 R
-/Parent 467 0 R
-/Prev 471 0 R
->> endobj
-471 0 obj <<
-/Title 472 0 R
-/A 469 0 R
-/Parent 467 0 R
-/Next 475 0 R
->> endobj
-467 0 obj <<
-/Title 468 0 R
-/A 465 0 R
-/Parent 411 0 R
-/Prev 463 0 R
-/Next 479 0 R
-/First 471 0 R
-/Last 475 0 R
-/Count -2
->> endobj
-463 0 obj <<
-/Title 464 0 R
-/A 461 0 R
-/Parent 411 0 R
-/Prev 459 0 R
-/Next 467 0 R
->> endobj
-459 0 obj <<
-/Title 460 0 R
-/A 457 0 R
-/Parent 411 0 R
-/Prev 455 0 R
-/Next 463 0 R
->> endobj
-455 0 obj <<
-/Title 456 0 R
-/A 453 0 R
-/Parent 411 0 R
-/Prev 419 0 R
-/Next 459 0 R
->> endobj
-451 0 obj <<
-/Title 452 0 R
-/A 449 0 R
-/Parent 419 0 R
-/Prev 447 0 R
->> endobj
-447 0 obj <<
-/Title 448 0 R
-/A 445 0 R
-/Parent 419 0 R
-/Prev 443 0 R
-/Next 451 0 R
->> endobj
-443 0 obj <<
-/Title 444 0 R
-/A 441 0 R
-/Parent 419 0 R
-/Prev 439 0 R
-/Next 447 0 R
->> endobj
-439 0 obj <<
-/Title 440 0 R
-/A 437 0 R
-/Parent 419 0 R
-/Prev 435 0 R
-/Next 443 0 R
->> endobj
-435 0 obj <<
-/Title 436 0 R
-/A 433 0 R
-/Parent 419 0 R
-/Prev 431 0 R
-/Next 439 0 R
->> endobj
-431 0 obj <<
-/Title 432 0 R
-/A 429 0 R
-/Parent 419 0 R
-/Prev 427 0 R
-/Next 435 0 R
->> endobj
-427 0 obj <<
-/Title 428 0 R
-/A 425 0 R
-/Parent 419 0 R
-/Prev 423 0 R
-/Next 431 0 R
->> endobj
-423 0 obj <<
-/Title 424 0 R
-/A 421 0 R
-/Parent 419 0 R
-/Next 427 0 R
->> endobj
-419 0 obj <<
-/Title 420 0 R
-/A 417 0 R
-/Parent 411 0 R
-/Prev 415 0 R
-/Next 455 0 R
-/First 423 0 R
-/Last 451 0 R
-/Count -8
->> endobj
-415 0 obj <<
-/Title 416 0 R
-/A 413 0 R
-/Parent 411 0 R
-/Next 419 0 R
->> endobj
-411 0 obj <<
-/Title 412 0 R
-/A 409 0 R
-/Parent 251 0 R
-/Prev 267 0 R
-/Next 551 0 R
-/First 415 0 R
-/Last 539 0 R
-/Count -12
->> endobj
-407 0 obj <<
-/Title 408 0 R
-/A 405 0 R
-/Parent 287 0 R
-/Prev 403 0 R
->> endobj
-403 0 obj <<
-/Title 404 0 R
-/A 401 0 R
-/Parent 287 0 R
-/Prev 399 0 R
-/Next 407 0 R
->> endobj
-399 0 obj <<
-/Title 400 0 R
-/A 397 0 R
-/Parent 287 0 R
-/Prev 395 0 R
-/Next 403 0 R
->> endobj
-395 0 obj <<
-/Title 396 0 R
-/A 393 0 R
-/Parent 287 0 R
-/Prev 391 0 R
-/Next 399 0 R
->> endobj
-391 0 obj <<
-/Title 392 0 R
-/A 389 0 R
-/Parent 287 0 R
-/Prev 387 0 R
-/Next 395 0 R
->> endobj
-387 0 obj <<
-/Title 388 0 R
-/A 385 0 R
-/Parent 287 0 R
-/Prev 383 0 R
-/Next 391 0 R
->> endobj
-383 0 obj <<
-/Title 384 0 R
-/A 381 0 R
-/Parent 287 0 R
-/Prev 379 0 R
-/Next 387 0 R
->> endobj
-379 0 obj <<
-/Title 380 0 R
-/A 377 0 R
-/Parent 287 0 R
-/Prev 375 0 R
-/Next 383 0 R
->> endobj
-375 0 obj <<
-/Title 376 0 R
-/A 373 0 R
-/Parent 287 0 R
-/Prev 371 0 R
-/Next 379 0 R
->> endobj
-371 0 obj <<
-/Title 372 0 R
-/A 369 0 R
-/Parent 287 0 R
-/Prev 367 0 R
-/Next 375 0 R
->> endobj
-367 0 obj <<
-/Title 368 0 R
-/A 365 0 R
-/Parent 287 0 R
-/Prev 363 0 R
-/Next 371 0 R
->> endobj
-363 0 obj <<
-/Title 364 0 R
-/A 361 0 R
-/Parent 287 0 R
-/Prev 359 0 R
-/Next 367 0 R
->> endobj
-359 0 obj <<
-/Title 360 0 R
-/A 357 0 R
-/Parent 287 0 R
-/Prev 355 0 R
-/Next 363 0 R
->> endobj
-355 0 obj <<
-/Title 356 0 R
-/A 353 0 R
-/Parent 287 0 R
-/Prev 351 0 R
-/Next 359 0 R
->> endobj
-351 0 obj <<
-/Title 352 0 R
-/A 349 0 R
-/Parent 287 0 R
-/Prev 347 0 R
-/Next 355 0 R
->> endobj
-347 0 obj <<
-/Title 348 0 R
-/A 345 0 R
-/Parent 287 0 R
-/Prev 343 0 R
-/Next 351 0 R
->> endobj
-343 0 obj <<
-/Title 344 0 R
-/A 341 0 R
-/Parent 287 0 R
-/Prev 339 0 R
-/Next 347 0 R
->> endobj
-339 0 obj <<
-/Title 340 0 R
-/A 337 0 R
-/Parent 287 0 R
-/Prev 335 0 R
-/Next 343 0 R
->> endobj
-335 0 obj <<
-/Title 336 0 R
-/A 333 0 R
-/Parent 287 0 R
-/Prev 331 0 R
-/Next 339 0 R
->> endobj
-331 0 obj <<
-/Title 332 0 R
-/A 329 0 R
-/Parent 287 0 R
-/Prev 327 0 R
-/Next 335 0 R
->> endobj
-327 0 obj <<
-/Title 328 0 R
-/A 325 0 R
-/Parent 287 0 R
-/Prev 323 0 R
-/Next 331 0 R
->> endobj
-323 0 obj <<
-/Title 324 0 R
-/A 321 0 R
-/Parent 287 0 R
-/Prev 319 0 R
-/Next 327 0 R
->> endobj
-319 0 obj <<
-/Title 320 0 R
-/A 317 0 R
-/Parent 287 0 R
-/Prev 315 0 R
-/Next 323 0 R
->> endobj
-315 0 obj <<
-/Title 316 0 R
-/A 313 0 R
-/Parent 287 0 R
-/Prev 311 0 R
-/Next 319 0 R
->> endobj
-311 0 obj <<
-/Title 312 0 R
-/A 309 0 R
-/Parent 287 0 R
-/Prev 307 0 R
-/Next 315 0 R
->> endobj
-307 0 obj <<
-/Title 308 0 R
-/A 305 0 R
-/Parent 287 0 R
-/Prev 303 0 R
-/Next 311 0 R
->> endobj
-303 0 obj <<
-/Title 304 0 R
-/A 301 0 R
-/Parent 287 0 R
-/Prev 299 0 R
-/Next 307 0 R
->> endobj
-299 0 obj <<
-/Title 300 0 R
-/A 297 0 R
-/Parent 287 0 R
-/Prev 295 0 R
-/Next 303 0 R
->> endobj
-295 0 obj <<
-/Title 296 0 R
-/A 293 0 R
-/Parent 287 0 R
-/Prev 291 0 R
-/Next 299 0 R
->> endobj
-291 0 obj <<
-/Title 292 0 R
-/A 289 0 R
-/Parent 287 0 R
-/Next 295 0 R
->> endobj
-287 0 obj <<
-/Title 288 0 R
-/A 285 0 R
-/Parent 267 0 R
-/Prev 275 0 R
-/First 291 0 R
-/Last 407 0 R
-/Count -30
->> endobj
-283 0 obj <<
-/Title 284 0 R
-/A 281 0 R
-/Parent 275 0 R
-/Prev 279 0 R
->> endobj
-279 0 obj <<
-/Title 280 0 R
-/A 277 0 R
-/Parent 275 0 R
-/Next 283 0 R
->> endobj
-275 0 obj <<
-/Title 276 0 R
-/A 273 0 R
-/Parent 267 0 R
-/Prev 271 0 R
-/Next 287 0 R
-/First 279 0 R
-/Last 283 0 R
-/Count -2
->> endobj
-271 0 obj <<
-/Title 272 0 R
-/A 269 0 R
-/Parent 267 0 R
-/Next 275 0 R
->> endobj
-267 0 obj <<
-/Title 268 0 R
-/A 265 0 R
-/Parent 251 0 R
-/Prev 255 0 R
-/Next 411 0 R
-/First 271 0 R
-/Last 287 0 R
-/Count -3
->> endobj
-263 0 obj <<
-/Title 264 0 R
-/A 261 0 R
-/Parent 255 0 R
-/Prev 259 0 R
->> endobj
-259 0 obj <<
-/Title 260 0 R
-/A 257 0 R
-/Parent 255 0 R
-/Next 263 0 R
->> endobj
-255 0 obj <<
-/Title 256 0 R
-/A 253 0 R
-/Parent 251 0 R
-/Next 267 0 R
-/First 259 0 R
-/Last 263 0 R
-/Count -2
->> endobj
-251 0 obj <<
-/Title 252 0 R
-/A 249 0 R
-/Parent 1800 0 R
-/Prev 247 0 R
-/Next 719 0 R
-/First 255 0 R
-/Last 687 0 R
-/Count -8
->> endobj
-247 0 obj <<
-/Title 248 0 R
-/A 245 0 R
-/Parent 1800 0 R
-/Prev 207 0 R
-/Next 251 0 R
->> endobj
-243 0 obj <<
-/Title 244 0 R
-/A 241 0 R
-/Parent 207 0 R
-/Prev 239 0 R
->> endobj
-239 0 obj <<
-/Title 240 0 R
-/A 237 0 R
-/Parent 207 0 R
-/Prev 235 0 R
-/Next 243 0 R
->> endobj
-235 0 obj <<
-/Title 236 0 R
-/A 233 0 R
-/Parent 207 0 R
-/Prev 231 0 R
-/Next 239 0 R
->> endobj
-231 0 obj <<
-/Title 232 0 R
-/A 229 0 R
-/Parent 207 0 R
-/Prev 227 0 R
-/Next 235 0 R
->> endobj
-227 0 obj <<
-/Title 228 0 R
-/A 225 0 R
-/Parent 207 0 R
-/Prev 223 0 R
-/Next 231 0 R
->> endobj
-223 0 obj <<
-/Title 224 0 R
-/A 221 0 R
-/Parent 207 0 R
-/Prev 219 0 R
-/Next 227 0 R
->> endobj
-219 0 obj <<
-/Title 220 0 R
-/A 217 0 R
-/Parent 207 0 R
-/Prev 215 0 R
-/Next 223 0 R
->> endobj
-215 0 obj <<
-/Title 216 0 R
-/A 213 0 R
-/Parent 207 0 R
-/Prev 211 0 R
-/Next 219 0 R
->> endobj
-211 0 obj <<
-/Title 212 0 R
-/A 209 0 R
-/Parent 207 0 R
-/Next 215 0 R
->> endobj
-207 0 obj <<
-/Title 208 0 R
-/A 205 0 R
-/Parent 1800 0 R
-/Prev 179 0 R
-/Next 247 0 R
-/First 211 0 R
-/Last 243 0 R
-/Count -9
->> endobj
-203 0 obj <<
-/Title 204 0 R
-/A 201 0 R
-/Parent 199 0 R
->> endobj
-199 0 obj <<
-/Title 200 0 R
-/A 197 0 R
-/Parent 179 0 R
-/Prev 183 0 R
-/First 203 0 R
-/Last 203 0 R
-/Count -1
->> endobj
-195 0 obj <<
-/Title 196 0 R
-/A 193 0 R
-/Parent 183 0 R
-/Prev 191 0 R
->> endobj
-191 0 obj <<
-/Title 192 0 R
-/A 189 0 R
-/Parent 183 0 R
-/Prev 187 0 R
-/Next 195 0 R
->> endobj
-187 0 obj <<
-/Title 188 0 R
-/A 185 0 R
-/Parent 183 0 R
-/Next 191 0 R
->> endobj
-183 0 obj <<
-/Title 184 0 R
-/A 181 0 R
-/Parent 179 0 R
-/Next 199 0 R
-/First 187 0 R
-/Last 195 0 R
-/Count -3
->> endobj
-179 0 obj <<
-/Title 180 0 R
-/A 177 0 R
-/Parent 1800 0 R
-/Prev 87 0 R
-/Next 207 0 R
-/First 183 0 R
-/Last 199 0 R
-/Count -2
->> endobj
-175 0 obj <<
-/Title 176 0 R
-/A 173 0 R
-/Parent 87 0 R
-/Prev 163 0 R
->> endobj
-171 0 obj <<
-/Title 172 0 R
-/A 169 0 R
-/Parent 163 0 R
-/Prev 167 0 R
->> endobj
-167 0 obj <<
-/Title 168 0 R
-/A 165 0 R
-/Parent 163 0 R
-/Next 171 0 R
->> endobj
-163 0 obj <<
-/Title 164 0 R
-/A 161 0 R
-/Parent 87 0 R
-/Prev 99 0 R
-/Next 175 0 R
-/First 167 0 R
-/Last 171 0 R
-/Count -2
->> endobj
-159 0 obj <<
-/Title 160 0 R
-/A 157 0 R
-/Parent 99 0 R
-/Prev 155 0 R
->> endobj
-155 0 obj <<
-/Title 156 0 R
-/A 153 0 R
-/Parent 99 0 R
-/Prev 151 0 R
-/Next 159 0 R
->> endobj
-151 0 obj <<
-/Title 152 0 R
-/A 149 0 R
-/Parent 99 0 R
-/Prev 147 0 R
-/Next 155 0 R
->> endobj
-147 0 obj <<
-/Title 148 0 R
-/A 145 0 R
-/Parent 99 0 R
-/Prev 143 0 R
-/Next 151 0 R
->> endobj
-143 0 obj <<
-/Title 144 0 R
-/A 141 0 R
-/Parent 99 0 R
-/Prev 139 0 R
-/Next 147 0 R
->> endobj
-139 0 obj <<
-/Title 140 0 R
-/A 137 0 R
-/Parent 99 0 R
-/Prev 135 0 R
-/Next 143 0 R
->> endobj
-135 0 obj <<
-/Title 136 0 R
-/A 133 0 R
-/Parent 99 0 R
-/Prev 131 0 R
-/Next 139 0 R
->> endobj
-131 0 obj <<
-/Title 132 0 R
-/A 129 0 R
-/Parent 99 0 R
-/Prev 127 0 R
-/Next 135 0 R
->> endobj
-127 0 obj <<
-/Title 128 0 R
-/A 125 0 R
-/Parent 99 0 R
-/Prev 123 0 R
-/Next 131 0 R
->> endobj
-123 0 obj <<
-/Title 124 0 R
-/A 121 0 R
-/Parent 99 0 R
-/Prev 119 0 R
-/Next 127 0 R
->> endobj
-119 0 obj <<
-/Title 120 0 R
-/A 117 0 R
-/Parent 99 0 R
-/Prev 115 0 R
-/Next 123 0 R
->> endobj
-115 0 obj <<
-/Title 116 0 R
-/A 113 0 R
-/Parent 99 0 R
-/Prev 111 0 R
-/Next 119 0 R
->> endobj
-111 0 obj <<
-/Title 112 0 R
-/A 109 0 R
-/Parent 99 0 R
-/Prev 107 0 R
-/Next 115 0 R
->> endobj
-107 0 obj <<
-/Title 108 0 R
-/A 105 0 R
-/Parent 99 0 R
-/Prev 103 0 R
-/Next 111 0 R
->> endobj
-103 0 obj <<
-/Title 104 0 R
-/A 101 0 R
-/Parent 99 0 R
-/Next 107 0 R
->> endobj
-99 0 obj <<
-/Title 100 0 R
-/A 97 0 R
-/Parent 87 0 R
-/Prev 95 0 R
-/Next 163 0 R
-/First 103 0 R
-/Last 159 0 R
-/Count -15
->> endobj
-95 0 obj <<
-/Title 96 0 R
-/A 93 0 R
-/Parent 87 0 R
-/Prev 91 0 R
-/Next 99 0 R
->> endobj
-91 0 obj <<
-/Title 92 0 R
-/A 89 0 R
-/Parent 87 0 R
-/Next 95 0 R
->> endobj
-87 0 obj <<
-/Title 88 0 R
-/A 85 0 R
-/Parent 1800 0 R
-/Prev 83 0 R
-/Next 179 0 R
-/First 91 0 R
-/Last 175 0 R
-/Count -5
->> endobj
-83 0 obj <<
-/Title 84 0 R
-/A 81 0 R
-/Parent 1800 0 R
-/Prev 47 0 R
-/Next 87 0 R
->> endobj
-79 0 obj <<
-/Title 80 0 R
-/A 77 0 R
-/Parent 67 0 R
-/Prev 75 0 R
->> endobj
-75 0 obj <<
-/Title 76 0 R
-/A 73 0 R
-/Parent 67 0 R
-/Prev 71 0 R
-/Next 79 0 R
->> endobj
-71 0 obj <<
-/Title 72 0 R
-/A 69 0 R
-/Parent 67 0 R
-/Next 75 0 R
->> endobj
-67 0 obj <<
-/Title 68 0 R
-/A 65 0 R
-/Parent 47 0 R
-/Prev 63 0 R
-/First 71 0 R
-/Last 79 0 R
-/Count -3
->> endobj
-63 0 obj <<
-/Title 64 0 R
-/A 61 0 R
-/Parent 47 0 R
-/Prev 59 0 R
-/Next 67 0 R
->> endobj
-59 0 obj <<
-/Title 60 0 R
-/A 57 0 R
-/Parent 47 0 R
-/Prev 55 0 R
-/Next 63 0 R
->> endobj
-55 0 obj <<
-/Title 56 0 R
-/A 53 0 R
-/Parent 47 0 R
-/Prev 51 0 R
-/Next 59 0 R
->> endobj
-51 0 obj <<
-/Title 52 0 R
-/A 49 0 R
-/Parent 47 0 R
-/Next 55 0 R
->> endobj
-47 0 obj <<
-/Title 48 0 R
-/A 45 0 R
-/Parent 1800 0 R
-/Prev 23 0 R
-/Next 83 0 R
-/First 51 0 R
-/Last 67 0 R
-/Count -5
->> endobj
-43 0 obj <<
-/Title 44 0 R
-/A 41 0 R
-/Parent 23 0 R
-/Prev 39 0 R
->> endobj
-39 0 obj <<
-/Title 40 0 R
-/A 37 0 R
-/Parent 23 0 R
-/Prev 35 0 R
-/Next 43 0 R
->> endobj
-35 0 obj <<
-/Title 36 0 R
-/A 33 0 R
-/Parent 23 0 R
-/Prev 31 0 R
-/Next 39 0 R
->> endobj
-31 0 obj <<
-/Title 32 0 R
-/A 29 0 R
-/Parent 23 0 R
-/Prev 27 0 R
-/Next 35 0 R
->> endobj
-27 0 obj <<
-/Title 28 0 R
-/A 25 0 R
-/Parent 23 0 R
-/Next 31 0 R
->> endobj
-23 0 obj <<
-/Title 24 0 R
-/A 21 0 R
-/Parent 1800 0 R
-/Prev 7 0 R
-/Next 47 0 R
-/First 27 0 R
-/Last 43 0 R
-/Count -5
->> endobj
-19 0 obj <<
-/Title 20 0 R
-/A 17 0 R
-/Parent 7 0 R
-/Prev 15 0 R
->> endobj
-15 0 obj <<
-/Title 16 0 R
-/A 13 0 R
-/Parent 7 0 R
-/Prev 11 0 R
-/Next 19 0 R
->> endobj
-11 0 obj <<
-/Title 12 0 R
-/A 9 0 R
-/Parent 7 0 R
-/Next 15 0 R
->> endobj
-7 0 obj <<
-/Title 8 0 R
-/A 5 0 R
-/Parent 1800 0 R
-/Next 23 0 R
-/First 11 0 R
-/Last 19 0 R
-/Count -3
->> endobj
-1801 0 obj <<
-/Names [(CodingSuggestions) 1224 0 R (Doc-Start) 874 0 R (Item.1) 1170 0 R (Item.10) 1193 0 R (Item.100) 1441 0 R (Item.101) 1442 0 R (Item.102) 1443 0 R (Item.103) 1444 0 R (Item.104) 1445 0 R (Item.105) 1673 0 R (Item.106) 1674 0 R (Item.107) 1675 0 R (Item.108) 1676 0 R (Item.109) 1677 0 R (Item.11) 1194 0 R (Item.110) 1678 0 R (Item.111) 1683 0 R (Item.112) 1684 0 R (Item.12) 1195 0 R (Item.13) 1196 0 R (Item.14) 1213 0 R (Item.15) 1214 0 R (Item.16) 1215 0 R (Item.17) 1227 0 R (Item.18) 1228 0 R (Item.19) 1229 0 R (Item.2) 1171 0 R (Item.20) 1230 0 R (Item.21) 1231 0 R (Item.22) 1232 0 R (Item.23) 1233 0 R (Item.24) 1234 0 R (Item.25) 1239 0 R (Item.26) 1240 0 R (Item.27) 1241 0 R (Item.28) 1242 0 R (Item.29) 1243 0 R (Item.3) 1172 0 R (Item.30) 1244 0 R (Item.31) 1245 0 R (Item.32) 1246 0 R (Item.33) 1247 0 R (Item.34) 1248 0 R (Item.35) 1249 0 R (Item.36) 1250 0 R (Item.37) 1251 0 R (Item.38) 1252 0 R (Item.39) 1253 0 R (Item.4) 1175 0 R (Item.40) 1254 0 R (Item.41) 1255 0 R (Item.42) 1263 0 R (Item.43) 1264 0 R (Item.44) 1265 0 R (Item.45) 1266 0 R (Item.46) 1267 0 R (Item.47) 1268 0 R (Item.48) 1269 0 R (Item.49) 1270 0 R (Item.5) 1176 0 R (Item.50) 1275 0 R (Item.51) 1276 0 R (Item.52) 1277 0 R (Item.53) 1301 0 R (Item.54) 1302 0 R (Item.55) 1303 0 R (Item.56) 1304 0 R (Item.57) 1305 0 R (Item.58) 1306 0 R (Item.59) 1307 0 R (Item.6) 1177 0 R (Item.60) 1308 0 R (Item.61) 1313 0 R (Item.62) 1314 0 R (Item.63) 1315 0 R (Item.64) 1316 0 R (Item.65) 1317 0 R (Item.66) 1318 0 R (Item.67) 1320 0 R (Item.68) 1321 0 R (Item.69) 1322 0 R (Item.7) 1178 0 R (Item.70) 1328 0 R (Item.71) 1329 0 R (Item.72) 1330 0 R (Item.73) 1331 0 R (Item.74) 1332 0 R (Item.75) 1333 0 R (Item.76) 1334 0 R (Item.77) 1335 0 R (Item.78) 1336 0 R (Item.79) 1337 0 R (Item.8) 1183 0 R (Item.80) 1344 0 R (Item.81) 1345 0 R (Item.82) 1346 0 R (Item.83) 1347 0 R (Item.84) 1348 0 R (Item.85) 1349 0 R (Item.86) 1350 0 R (Item.87) 1352 0 R (Item.88) 1353 0 R (Item.89) 1354 0 R (Item.9) 1184 0 R (Item.90) 1355 0 R (Item.91) 1367 0 R (Item.92) 1368 0 R (Item.93) 1369 0 R (Item.94) 1370 0 R (Item.95) 1428 0 R (Item.96) 1429 0 R (Item.97) 1430 0 R (Item.98) 1431 0 R (Item.99) 1432 0 R (Packaging) 1776 0 R (SMBPASSWDFILEFORMAT) 1744 0 R (architecture) 1168 0 R (chapter*.4) 909 0 R (chapter.1) 6 0 R (chapter.10) 718 0 R (chapter.11) 742 0 R (chapter.12) 750 0 R (chapter.13) 802 0 R (chapter.14) 818 0 R (chapter.15) 846 0 R (chapter.16) 858 0 R (chapter.2) 22 0 R (chapter.3) 46 0 R (chapter.4) 82 0 R (chapter.5) 86 0 R (chapter.6) 178 0 R (chapter.7) 206 0 R (chapter.8) 246 0 R (chapter.9) 250 0 R (debug) 1191 0 R (id2733755) 1192 0 R (id2733820) 1154 0 R (id2733904) 1155 0 R (id2733935) 1160 0 R (id2733972) 1201 0 R (id2734187) 1185 0 R (id2734254) 1186 0 R (id2734448) 1207 0 R (id2734494) 1208 0 R (id2734600) 1216 0 R (id2734608) 1217 0 R (id2734627) 1218 0 R (id2734650) 1219 0 R (id2734703) 1169 0 R (id2786615) 1173 0 R (id2786652) 1174 0 R (id2800686) 1261 0 R (id2800712) 1262 0 R (id2800990) 1351 0 R (id2801045) 1343 0 R (id2801174) 1278 0 R (id2801187) 1279 0 R (id2801201) 1280 0 R (id2801215) 1281 0 R (id2801228) 1282 0 R (id2801244) 1283 0 R (id2801258) 1284 0 R (id2801273) 1285 0 R (id2801287) 1286 0 R (id2801302) 1287 0 R (id2801316) 1288 0 R (id2801330) 1294 0 R (id2801345) 1295 0 R (id2801359) 1296 0 R (id2801374) 1297 0 R (id2801389) 1298 0 R (id2801404) 1299 0 R (id2801439) 1300 0 R (id2801591) 1319 0 R (id2801677) 1327 0 R (id2801816) 1380 0 R (id2801840) 1385 0 R (id2801877) 1378 0 R (id2801899) 1379 0 R (id2801946) 1356 0 R (id2802010) 1361 0 R (id2802109) 1366 0 R (id2802179) 1371 0 R (id2802404) 1386 0 R (id2802466) 1387 0 R (id2802496) 1392 0 R (id2802521) 1393 0 R (id2802567) 1394 0 R (id2802753) 1420 0 R (id2802908) 1668 0 R (id2802951) 1666 0 R (id2802967) 1667 0 R (id2803176) 1437 0 R (id2803211) 1438 0 R (id2803249) 1439 0 R (id2803257) 1440 0 R (id2803333) 1450 0 R (id2803340) 1451 0 R (id2803415) 1452 0 R (id2803546) 1453 0 R (id2803553) 1454 0 R (id2803565) 1455 0 R (id2803576) 1456 0 R (id2803589) 1457 0 R (id2803602) 1462 0 R (id2803695) 1463 0 R (id2803709) 1464 0 R (id2803765) 1465 0 R (id2803808) 1466 0 R (id2803836) 1467 0 R (id2803878) 1468 0 R (id2803964) 1473 0 R (id2804058) 1474 0 R (id2804085) 1475 0 R (id2804172) 1476 0 R (id2804242) 1477 0 R (id2804342) 1482 0 R (id2804420) 1483 0 R (id2804461) 1484 0 R (id2804543) 1485 0 R (id2804596) 1486 0 R (id2804767) 1492 0 R (id2804871) 1493 0 R (id2804910) 1494 0 R (id2805054) 1499 0 R (id2805167) 1500 0 R (id2805730) 1505 0 R (id2805825) 1506 0 R (id2805868) 1511 0 R (id2806037) 1512 0 R (id2806504) 1517 0 R (id2806516) 1518 0 R (id2806618) 1523 0 R (id2806809) 1524 0 R (id2806942) 1530 0 R (id2806969) 1531 0 R (id2807008) 1532 0 R (id2807149) 1533 0 R (id2807189) 1534 0 R (id2807339) 1539 0 R (id2807412) 1540 0 R (id2807492) 1541 0 R (id2807538) 1542 0 R (id2807718) 1547 0 R (id2807884) 1548 0 R (id2807897) 1553 0 R (id2807967) 1554 0 R (id2808010) 1555 0 R (id2808024) 1556 0 R (id2808063) 1557 0 R (id2808117) 1558 0 R (id2808125) 1559 0 R (id2808137) 1560 0 R (id2808209) 1565 0 R (id2808216) 1566 0 R (id2808229) 1567 0 R (id2808319) 1568 0 R (id2808326) 1569 0 R (id2808353) 1570 0 R (id2808385) 1571 0 R (id2808399) 1572 0 R (id2808498) 1577 0 R (id2808595) 1578 0 R (id2808610) 1579 0 R (id2808723) 1580 0 R (id2808821) 1586 0 R (id2808983) 1587 0 R (id2809015) 1588 0 R (id2809085) 1589 0 R (id2809118) 1594 0 R (id2809149) 1595 0 R (id2809218) 1596 0 R (id2809265) 1597 0 R (id2809305) 1598 0 R (id2809347) 1599 0 R (id2809381) 1600 0 R (id2809396) 1605 0 R (id2809423) 1606 0 R (id2809495) 1607 0 R (id2809510) 1608 0 R (id2809537) 1609 0 R (id2809587) 1610 0 R (id2809604) 1615 0 R (id2809619) 1616 0 R (id2809745) 1617 0 R (id2809866) 1618 0 R (id2809894) 1619 0 R (id2810078) 1624 0 R (id2810192) 1625 0 R (id2810238) 1626 0 R (id2810259) 1627 0 R (id2810384) 1632 0 R (id2810458) 1633 0 R (id2810472) 1634 0 R (id2810513) 1635 0 R (id2810575) 1636 0 R (id2810583) 1637 0 R (id2810745) 1643 0 R (id2810826) 1644 0 R (id2810875) 1649 0 R (id2810915) 1650 0 R (id2810923) 1651 0 R (id2811049) 1652 0 R (id2811230) 1657 0 R (id2811245) 1658 0 R (id2811293) 1659 0 R (id2811353) 1660 0 R (id2811596) 1701 0 R (id2811836) 1685 0 R (id2811849) 1686 0 R (id2812158) 1738 0 R (id2812288) 1737 0 R (id2812322) 1707 0 R (id2812453) 1712 0 R (id2812488) 1713 0 R (id2812557) 1714 0 R (id2812564) 1715 0 R (id2812580) 1716 0 R (id2812608) 1717 0 R (id2812630) 1722 0 R (id2812637) 1723 0 R (id2812655) 1724 0 R (id2812694) 1725 0 R (id2812785) 1731 0 R (id2812874) 1743 0 R (id2813064) 1755 0 R (id2813097) 1756 0 R (id2813131) 1770 0 R (id2813150) 1771 0 R (id2813325) 1754 0 R (id2813533) 1757 0 R (id2813561) 1762 0 R (id2813621) 1763 0 R (id2813840) 1777 0 R (id2813873) 1778 0 R (internals) 1260 0 R (modules) 1753 0 R (netbios) 1153 0 R (ntdomain) 1419 0 R (page.1) 873 0 R (page.10) 1167 0 R (page.11) 1182 0 R (page.12) 1190 0 R (page.13) 1200 0 R (page.14) 1206 0 R (page.15) 1212 0 R (page.16) 1223 0 R (page.17) 1238 0 R (page.18) 1259 0 R (page.19) 1274 0 R (page.2) 885 0 R (page.20) 1293 0 R (page.21) 1312 0 R (page.22) 1326 0 R (page.23) 1341 0 R (page.24) 1360 0 R (page.25) 1365 0 R (page.26) 1376 0 R (page.27) 1384 0 R (page.28) 1391 0 R (page.29) 1398 0 R (page.3) 908 0 R (page.30) 1402 0 R (page.31) 1413 0 R (page.32) 1418 0 R (page.33) 1436 0 R (page.34) 1449 0 R (page.35) 1461 0 R (page.36) 1472 0 R (page.37) 1481 0 R (page.38) 1491 0 R (page.39) 1498 0 R (page.4) 953 0 R (page.40) 1504 0 R (page.41) 1510 0 R (page.42) 1516 0 R (page.43) 1522 0 R (page.44) 1529 0 R (page.45) 1538 0 R (page.46) 1546 0 R (page.47) 1552 0 R (page.48) 1564 0 R (page.49) 1576 0 R (page.5) 1009 0 R (page.50) 1585 0 R (page.51) 1593 0 R (page.52) 1604 0 R (page.53) 1614 0 R (page.54) 1623 0 R (page.55) 1631 0 R (page.56) 1642 0 R (page.57) 1648 0 R (page.58) 1656 0 R (page.59) 1664 0 R (page.6) 1065 0 R (page.60) 1672 0 R (page.61) 1682 0 R (page.62) 1691 0 R (page.63) 1695 0 R (page.64) 1699 0 R (page.65) 1705 0 R (page.66) 1711 0 R (page.67) 1721 0 R (page.68) 1730 0 R (page.69) 1735 0 R (page.7) 1122 0 R (page.70) 1742 0 R (page.71) 1748 0 R (page.72) 1752 0 R (page.73) 1761 0 R (page.74) 1768 0 R (page.75) 1775 0 R (page.8) 1152 0 R (page.9) 1159 0 R (parsing) 1342 0 R (printing) 1665 0 R (pwencrypt) 1736 0 R (rpc-plugin) 1769 0 R (sam) 1706 0 R (section*.1) 889 0 R (section*.2) 896 0 R (section*.3) 903 0 R (section.1.1) 10 0 R (section.1.2) 14 0 R (section.1.3) 18 0 R (section.10.1) 722 0 R (section.10.2) 726 0 R (section.10.3) 730 0 R (section.10.4) 734 0 R (section.10.5) 738 0 R (section.11.1) 746 0 R (section.12.1) 754 0 R (section.12.2) 758 0 R (section.12.3) 762 0 R (section.12.4) 766 0 R (section.12.5) 782 0 R (section.12.6) 794 0 R (section.12.7) 798 0 R (section.13.1) 806 0 R (section.13.2) 810 0 R (section.13.3) 814 0 R (section.14.1) 822 0 R (section.14.2) 826 0 R (section.14.3) 838 0 R (section.15.1) 850 0 R (section.15.2) 854 0 R (section.16.1) 862 0 R (section.16.2) 866 0 R (section.2.1) 26 0 R (section.2.2) 30 0 R (section.2.3) 34 0 R (section.2.4) 38 0 R (section.2.5) 42 0 R (section.3.1) 50 0 R (section.3.2) 54 0 R (section.3.3) 58 0 R (section.3.4) 62 0 R (section.3.5) 66 0 R (section.5.1) 90 0 R (section.5.2) 94 0 R (section.5.3) 98 0 R (section.5.4) 162 0 R (section.5.5) 174 0 R (section.6.1) 182 0 R (section.6.2) 198 0 R (section.7.1) 210 0 R (section.7.2) 214 0 R (section.7.3) 218 0 R (section.7.4) 222 0 R (section.7.5) 226 0 R (section.7.6) 230 0 R (section.7.7) 234 0 R (section.7.8) 238 0 R (section.7.9) 242 0 R (section.9.1) 254 0 R (section.9.2) 266 0 R (section.9.3) 410 0 R (section.9.4) 550 0 R (section.9.5) 614 0 R (section.9.6) 642 0 R (section.9.7) 670 0 R (section.9.8) 686 0 R (subsection.12.4.1) 770 0 R (subsection.12.4.2) 774 0 R (subsection.12.4.3) 778 0 R (subsection.12.5.1) 786 0 R (subsection.12.5.2) 790 0 R (subsection.14.2.1) 830 0 R (subsection.14.2.2) 834 0 R (subsection.14.3.1) 842 0 R (subsection.3.5.1) 70 0 R (subsection.3.5.2) 74 0 R (subsection.3.5.3) 78 0 R (subsection.5.3.1) 102 0 R (subsection.5.3.10) 138 0 R (subsection.5.3.11) 142 0 R (subsection.5.3.12) 146 0 R (subsection.5.3.13) 150 0 R (subsection.5.3.14) 154 0 R (subsection.5.3.15) 158 0 R (subsection.5.3.2) 106 0 R (subsection.5.3.3) 110 0 R (subsection.5.3.4) 114 0 R (subsection.5.3.5) 118 0 R (subsection.5.3.6) 122 0 R (subsection.5.3.7) 126 0 R (subsection.5.3.8) 130 0 R (subsection.5.3.9) 134 0 R (subsection.5.4.1) 166 0 R (subsection.5.4.2) 170 0 R (subsection.6.1.1) 186 0 R (subsection.6.1.2) 190 0 R (subsection.6.1.3) 194 0 R (subsection.6.2.1) 202 0 R (subsection.9.1.1) 258 0 R (subsection.9.1.2) 262 0 R (subsection.9.2.1) 270 0 R (subsection.9.2.2) 274 0 R (subsection.9.2.3) 286 0 R (subsection.9.3.1) 414 0 R (subsection.9.3.10) 514 0 R (subsection.9.3.11) 526 0 R (subsection.9.3.12) 538 0 R (subsection.9.3.2) 418 0 R (subsection.9.3.3) 454 0 R (subsection.9.3.4) 458 0 R (subsection.9.3.5) 462 0 R (subsection.9.3.6) 466 0 R (subsection.9.3.7) 478 0 R (subsection.9.3.8) 490 0 R (subsection.9.3.9) 502 0 R (subsection.9.4.1) 554 0 R (subsection.9.4.2) 566 0 R (subsection.9.4.3) 578 0 R (subsection.9.4.4) 590 0 R (subsection.9.4.5) 602 0 R (subsection.9.5.1) 618 0 R (subsection.9.5.2) 630 0 R (subsection.9.6.1) 646 0 R (subsection.9.6.2) 658 0 R (subsection.9.7.1) 674 0 R (subsection.9.7.2) 678 0 R (subsection.9.7.3) 682 0 R (subsection.9.8.1) 690 0 R (subsection.9.8.2) 702 0 R (subsubsection.9.2.2.1) 278 0 R (subsubsection.9.2.2.2) 282 0 R (subsubsection.9.2.3.1) 290 0 R (subsubsection.9.2.3.10) 326 0 R (subsubsection.9.2.3.11) 330 0 R (subsubsection.9.2.3.12) 334 0 R (subsubsection.9.2.3.13) 338 0 R (subsubsection.9.2.3.14) 342 0 R (subsubsection.9.2.3.15) 346 0 R (subsubsection.9.2.3.16) 350 0 R (subsubsection.9.2.3.17) 354 0 R (subsubsection.9.2.3.18) 358 0 R (subsubsection.9.2.3.19) 362 0 R (subsubsection.9.2.3.2) 294 0 R (subsubsection.9.2.3.20) 366 0 R (subsubsection.9.2.3.21) 370 0 R (subsubsection.9.2.3.22) 374 0 R (subsubsection.9.2.3.23) 378 0 R (subsubsection.9.2.3.24) 382 0 R (subsubsection.9.2.3.25) 386 0 R (subsubsection.9.2.3.26) 390 0 R (subsubsection.9.2.3.27) 394 0 R (subsubsection.9.2.3.28) 398 0 R (subsubsection.9.2.3.29) 402 0 R (subsubsection.9.2.3.3) 298 0 R (subsubsection.9.2.3.30) 406 0 R (subsubsection.9.2.3.4) 302 0 R (subsubsection.9.2.3.5) 306 0 R (subsubsection.9.2.3.6) 310 0 R (subsubsection.9.2.3.7) 314 0 R (subsubsection.9.2.3.8) 318 0 R (subsubsection.9.2.3.9) 322 0 R (subsubsection.9.3.10.1) 518 0 R (subsubsection.9.3.10.2) 522 0 R (subsubsection.9.3.11.1) 530 0 R (subsubsection.9.3.11.2) 534 0 R (subsubsection.9.3.12.1) 542 0 R (subsubsection.9.3.12.2) 546 0 R (subsubsection.9.3.2.1) 422 0 R (subsubsection.9.3.2.2) 426 0 R (subsubsection.9.3.2.3) 430 0 R (subsubsection.9.3.2.4) 434 0 R (subsubsection.9.3.2.5) 438 0 R (subsubsection.9.3.2.6) 442 0 R (subsubsection.9.3.2.7) 446 0 R (subsubsection.9.3.2.8) 450 0 R (subsubsection.9.3.6.1) 470 0 R (subsubsection.9.3.6.2) 474 0 R (subsubsection.9.3.7.1) 482 0 R (subsubsection.9.3.7.2) 486 0 R (subsubsection.9.3.8.1) 494 0 R (subsubsection.9.3.8.2) 498 0 R (subsubsection.9.3.9.1) 506 0 R (subsubsection.9.3.9.2) 510 0 R (subsubsection.9.4.1.1) 558 0 R (subsubsection.9.4.1.2) 562 0 R (subsubsection.9.4.2.1) 570 0 R (subsubsection.9.4.2.2) 574 0 R (subsubsection.9.4.3.1) 582 0 R (subsubsection.9.4.3.2) 586 0 R (subsubsection.9.4.4.1) 594 0 R (subsubsection.9.4.4.2) 598 0 R (subsubsection.9.4.5.1) 606 0 R (subsubsection.9.4.5.2) 610 0 R (subsubsection.9.5.1.1) 622 0 R (subsubsection.9.5.1.2) 626 0 R (subsubsection.9.5.2.1) 634 0 R (subsubsection.9.5.2.2) 638 0 R (subsubsection.9.6.1.1) 650 0 R (subsubsection.9.6.1.2) 654 0 R (subsubsection.9.6.2.1) 662 0 R (subsubsection.9.6.2.2) 666 0 R (subsubsection.9.8.1.1) 694 0 R (subsubsection.9.8.1.2) 698 0 R (subsubsection.9.8.2.1) 706 0 R (subsubsection.9.8.2.2) 710 0 R (subsubsection.9.8.2.3) 714 0 R (tracing) 1403 0 R (unix-smb) 1377 0 R (wins) 1700 0 R]
-/Limits [(CodingSuggestions) (wins)]
->> endobj
-1802 0 obj <<
-/Kids [1801 0 R]
->> endobj
-1803 0 obj <<
-/Dests 1802 0 R
->> endobj
-1804 0 obj <<
-/Type /Catalog
-/Pages 1799 0 R
-/Outlines 1800 0 R
-/Names 1803 0 R
-/PageMode /UseOutlines /URI<</Base()>> /ViewerPreferences<<>>
-/OpenAction 869 0 R
-/PTEX.Fullbanner (This is pdfTeX, Version 3.14159-1.10a)
->> endobj
-1805 0 obj <<
-/Producer (pdfTeX-1.10a)
-/Author()/Title()/Subject()/Creator(LaTeX with hyperref package)/Producer(pdfTeX-1.10a)/Keywords()
-/Creator (TeX)
-/CreationDate (D:20030501010600)
->> endobj
+gH)R2JQWU"kkd4E
+B#2`)0 }wq"Jz+IUUy~cD\SJ(k4
+T
+/q'>%QE)mD`m5Il8$gHT3aHB)Fu}/kZ :;bö1ô-¸@Po vj#}(H^nfr4a3V>ot Q cM=.zGyM < D )U9E:>@CJ]
+ -)zdz}\ b`4hQZZfBi"
+l5MvW]:)PL&tH~2 P||x[þÛm KJR*kQs 9kaoS#VT*x[!}'g?qXW\w}+ "dqc~LIendstream
+endobj
+596 0 obj<</Type/Page/Parent 513 0 R/Contents 597 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F6 8 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+597 0 obj<</Filter/FlateDecode/Length 686 >>stream
+xVMo@+Vm%"i9@`z UaKwA$-*d _z ;@:~ ^m;np]S
+b
+8'xup="T,}2,gm=$ib"a0p Q\aeJ&rN 9?
+O r 1|T^5#
+',yk(dDÐ8ý'êzLdArZ 5Y, cqU;04WeOjD`_)F}*s)W,1R%^>pQNFW0(\E
+7q[7 y*endstream
+endobj
+598 0 obj<</Type/Page/Parent 513 0 R/Contents 599 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F6 8 0 R/F8 10 0 R>>/XObject<<>>>>>>endobj
+599 0 obj<</Filter/FlateDecode/Length 551 >>stream
+xo0+m$PVXj%P?w&Vx8 _
+;*`G;O:[
+cb0b?Fglendstream
+endobj
+600 0 obj<</Type/Page/Parent 513 0 R/Contents 601 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F6 8 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+601 0 obj<</Filter/FlateDecode/Length 694 >>stream
+xUS@~_)W>F<h}Najap~< ll`\' >8-|
+i}la8t
++V!
+u#yu1l%s59
+[{+wclCKZ^}2~sUTM`JDvnG_b4mkx-LPDUP`:9nSBWLw?&_G%LX{
+nw.z3b)1=Z`g~_FM"J9n@,J8%GtX)+4H8V&=_V^,MnQo\v|Ezx$~-CyCv4vQ"n
+endobj
+602 0 obj<</Type/Page/Parent 513 0 R/Contents 603 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F6 8 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+603 0 obj<</Filter/FlateDecode/Length 888 >>stream
+xV[H~Wdd mO6‚PScNf]D8_}:UF6`fd
+ik:L ]3gpdj
+Lp>=b//f`-:ygd)TR4wURH \.LTHG
+9Z1LeIx%*BctU=v.Y fjmk{%`&n|Db{"C5_dfUhW*lb<E+
+FWfET@_*L P`=-XR!; #g9( ]!0," y _DCNef[j )()_F,uY6no
+\dA!¶‚R
+9?hE1(Pr;58C7FCn33ur&e
+$;6t8m<KKV /[%x |6
+:;b`[^viim>Q ;1mVdv6rE8
+7~Q!}aO^~RE7Ia-1 zOKV[57+mv7W&: F[rf/ h|âFaopkz&,-nN{Y=l]ߚÝ{,¥Õä;1Á]_'¦¡üw`ÿjh -â E¯­¡tßé¨Äm.ÐÂÍ:&Iltv
+2f6bwXRlwLE,ox9 b)L-YljU`ydt?Rendstream
+endobj
+604 0 obj<</Type/Page/Parent 513 0 R/Contents 605 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F6 8 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+605 0 obj<</Filter/FlateDecode/Length 1261 >>stream
+xVRH}+[XlGqU [X$3uU q}Nb$oSG|/b l%)/:hdY&9 4&~oNu=p.IjW)ii.2wIE`{M"NF/Gpz#p0i7PF4TZJQt:I9zYubi?oQYj~'b-etJ43@a*Vbu9K,XJE\"
+aa(tm?
+cfV*h
+IwB5k@xL)wdP~^b];EABp)E<PJYK\zg&z$S@Z{p <J%={Gied[gZZi puI<I6-,F-é§6÷ xlӃ€Ø e‡êL8l*Ur@>1aJB#Z50WKg'rI b
+Nyph'~'[oÇÐñZX
+y'kmjnt3.@
+UWpYDJuG .G[BiJCpYN!cT0e,O2P¡€OY iC ^\4mg!nr1\8>]\I[mqabeQxU~ KQek%Ai;% nmkw'DjE -:*tLpA gzByiLq(?|,QX +X23&Ei|#`Xks V`cp{_{E?A$ o.GGt"~{v3ly]qv`#â;݄CN,endstream
+endobj
+606 0 obj<</Type/Page/Parent 513 0 R/Contents 607 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F5 7 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+607 0 obj<</Filter/FlateDecode/Length 944 >>stream
+xV6}WL>8@f8n>fV&C]N
+AmXE3g );QDm/c?d<}T40p<4'lJThc_|m3%$\$P-9YEviiSOvnw7wF{2e@sP:7H*KY,SQ8n-¹¥9ÛòœxNKNK,?3\l 56"|"iKe,]-fq_3<:x#++xO\rdhnTjA(~2r
+LsZjE\P~_4tP;3K2
+DEAZRj&h(i%$hhg8:(xT1c# yd* U[;xm%pI^w~{(v[/
+QdM^u\/TSbZXBu* \sZ&M!x}@G;K <{@QsfWS$VxNnjjxt)h,uNS<[^QzZ2AM+uMI#X|dZ5f=VÃ?fótüc[Çæ7¶òjÍoÙ'ôߞkƒÞ=ëëòð¬ÅÏC7y"+%1kHyjNf;8[Y<\>YB>
+endobj
+608 0 obj<</Type/Page/Parent 513 0 R/Contents 609 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F5 7 0 R/F8 10 0 R>>/XObject<<>>>>>>endobj
+609 0 obj<</Filter/FlateDecode/Length 506 >>stream
+xU0-f7C<HN#E^hG`bfCZ,ffH.QEuo:CH#X'Pv^HrYJ
+gPH
+:(}UE ; \E 7-0YW4[ZD7,A^a\V`h.}'â?ê HLCEPrR$D,_GY{J *3)ÔFdu~Ar>\lO,StHliu|A?
+05YxhRI??:i9Z.NHN:J.KlT4'N9V ^40p;6rhY#
+k!Q>@GuEÞ›
+endobj
+610 0 obj<</Type/Page/Parent 513 0 R/Contents 611 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F6 8 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+611 0 obj<</Filter/FlateDecode/Length 985 >>stream
+xVMo6W URq*isHM)
+Zlm%' )ffm
+wz'S
+|y%
+ t8#A*1OC[*U#NV)}AZ[klxD"eYdEPdU[y:"$(?%|bk;p,UlLmT
+ 2@`N7 mjs<oqK wHDB>/U2trqkUHP5h%V
+âå0ôZe7GM6U/RcH UZDisq<|vml 9Y`KCEg^Ljc#$04'WL /~9 yO!1gN~}Wp:!g[+7?l5r<0+d ."zPNJe .  )vA,sZI"zd'$q]X1u8.SyaBg>>E=pV?GT-T1fdY @tD@lT[(.n193+WmoPL&@>Udj,M:uêbqÒ•ç¹;–ÄëÙåì_´mhîÓ ÅtM|HVY>F"IV2;\^$
+hz?½MJmUl8acmCEj:,D$(QBb_Q#Fendstream
+endobj
+612 0 obj<</Type/Page/Parent 513 0 R/Contents 613 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F6 8 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+613 0 obj<</Filter/FlateDecode/Length 804 >>stream
+xVN@+vHiiDRU{¸µ½fwƒ¾¾ob’‚ By3f{x4OQs|u4 ?-)v'/a< ~00&
+endobj
+614 0 obj<</Type/Page/Parent 513 0 R/Contents 615 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F6 8 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+615 0 obj<</Filter/FlateDecode/Length 1020 >>stream
+xVr6}W/rbK))}x&Q\3-Id{ vT(rgpR#GnzaR4MfS\rpD/=OgW7Mh88glJqF}AHLVda,$UT_r)G@V\29%Qd^YQQoR'9oBs0Dq0
+f]_4Ro"jVE<Xtwd?eclLXAÂ%Õ.å È*-MZa
+-nO/[J$Y¡«ÃÍ0‘ «Ear<'LrFKVC)>$J*5e%+e+]tq<sHC9Hm;g'gmw%P X1.s6`QgpP g$;cþ—«µ¤ô?¾w2ÃÀ¸gȧ„zþy˜”©ÊÂHW,6W) kER'16 "QbZ
+=#8Rr#qr}M0F;)BVE
+[Jl~GBQ*&^32%B4=RJiFÅxiû9D-t$O[5KlX~qSe1L?ww õ·@ M9 '88Q3UnZa~Wl3Lc"[L`p6E/fRendstream
+endobj
+616 0 obj<</Type/Page/Parent 513 0 R/Contents 617 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F6 8 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+617 0 obj<</Filter/FlateDecode/Length 812 >>stream
+xUo0_qIBH-[%d d;;҂4röó»»wÏ/ z»zÐ ^4æ@~{)Rp]—¹: ß?D0
+RhOf}n02!$\K:.$SÞa6C` bkojz Y2A YMp 7 9Af nFUHU %)bj=fq c | 6<7S!"Fs U1SP
+K~$,^Z[GVi_\[~{+ Kc%:Ôë\ªÊe¿këŠõêo0Í*HegbF6]eZ[~wecar?8o^zm[:
+'nE!*H7rAZ&{fq(P]yU8tmm df86ng&2F_*V#I4$b)+Jaw}=a~u\{>_eIW7CW3=e~0JVmQ 4endstream
+endobj
+618 0 obj<</Type/Page/Parent 513 0 R/Contents 619 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F6 8 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+619 0 obj<</Filter/FlateDecode/Length 703 >>stream
+xT[o0~WixqvcjwOHIH ^48u@(\}A/A2oxv;"!qgJ2, ^H.C@=2Pvºû”7>w€R,T4;$ P7go-aL6VE,r2
+E©Ö£´V[~zHKhAgIJFe|e93S0FG@.7SK#Expx%RgJ D:r
+W*8^\%P"by^Þ÷çCHl0Or!
+sUm,|$dUo|[QRa#W\/pu:sv/OP 4|)%o+pdtJ.d0
+Ib<o>endstream
+endobj
+620 0 obj<</Type/Page/Parent 513 0 R/Contents 621 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F6 8 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+621 0 obj<</Filter/FlateDecode/Length 527 >>stream
+xTMo0 W=1mk4IA=8R*C_?umHy Ir3iNRHyc: >1s1Y9;yS
+rpk
+;/ p+5a 3ñÓ¢û뢜}œý8-Ëendstream
+endobj
+622 0 obj<</Type/Page/Parent 513 0 R/Contents 623 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F6 8 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+623 0 obj<</Filter/FlateDecode/Length 588 >>stream
+xn@sTk@9i-9vÓÞ$‘…a¬ÐKX`?$&ReYB93=8g[lgNaY8L &i?]8{.=`6+zp!ze=s`2fd>?N03CSYtYY eJDPA*ThKI]{!7hv~MfJTS $Uek(qxxAT7"UJlA$
+GeZaA^cZ)^W?p nAiVA)~' rc CVaLKL Lr]zF)5 X`paX wJ[&*XG={A>U[
+n[hG(UHQ`Y[&dA
+CT G)}t? |Of?N\WQ<} !ccG`i8Em;h#[u Nendstream
+endobj
+624 0 obj<</Type/Page/Parent 513 0 R/Contents 625 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F6 8 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+625 0 obj<</Filter/FlateDecode/Length 903 >>stream
+xooH)FU_$xMj \p285oIpKHE <gM/B
+jKReS#tGI@-Dl1e?ö[5Ìa܈ùZ>2Jpl`:ºœ~¾¿~ü´­šIG)R!;bb}3\KOvc_.u2EK"S K63sg([H.<+Rr)*YTw; f dB5k2U]k/†,жWJ[L@
+2/W 8BAEH$Y8\Cu$V@*8GCZ{2>E$bz^S? @MX%J}2SFk tJ#p5^5o>Ng uyQ"37?:/ e4 (pwmaYP*)K7Hib3Yv-v]JRoqI!4$h{EO]"U!
+a)`
+wmy# Sv]-Oa^pj\HZvUDJntha#Luu-Kv<8|^&xtu|>!]Gb0=JoR^/02Vhuh{-Me~0hRKG{\kendstream
+endobj
+626 0 obj<</Type/Page/Parent 513 0 R/Contents 627 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F6 8 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+627 0 obj<</Filter/FlateDecode/Length 933 >>stream
+xV8~ MBBm{WSu`f6V:!o>eA1RQ $$ :˜Í²a8Ix#
+rY^^E.VaB
+CXru -!~}Mo q5,>b,V+xu|(Z@&jADPK#%*G4RPFve5J,^l6/f
+vXNJ
+evR (m &v's%S7L-3cZ]P2SNmTXk[JhvUSNiL#LFTln}Y""ZYUp/8Fc%zJGN
+endobj
+628 0 obj<</Type/Page/Parent 513 0 R/Contents 629 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F6 8 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+629 0 obj<</Filter/FlateDecode/Length 920 >>stream
+xVrF}+W,Y, yVN(Ok<jg$n681|+ai|$ 0 sBoP$N&#4'Riv:p&n
+ 8UuqJwE/_ +JHoƒÀêj&`]™9hÔY
+T\&8{-k6
+%.w!<N'0m^KUw,'439Rkhmu$F~
+(4zPYP:=C ^JY#&
+"%i'g<#_K`3V mnc/}3'xF]p4
+WPUG?e\2|0('e=gFCuME: w85Rt=iai=láÚÉe³q3¿Ïzîîø9*¼¤®qF G];yDf<a|FRDr0iqQ>>_~kO2iٕpõ®¢J#O
+endobj
+630 0 obj<</Type/Page/Parent 513 0 R/Contents 631 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F6 8 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+631 0 obj<</Filter/FlateDecode/Length 758 >>stream
+xUMo@W/c*:j{,VxYMZw[D=Ujd o>r`@ X
+sQ/i(&Wzhl_q<F;+AiQa0GZ@`a (-IY(mPi
+<cDi-lO&g`6s7:Bm8ZdcuF6,I=g DcoE'-Nendstream
+endobj
+632 0 obj<</Type/Page/Parent 513 0 R/Contents 633 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F6 8 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+633 0 obj<</Filter/FlateDecode/Length 659 >>stream
+xUQo0~Wc+Ai+ <iJBLcCCRa "}_ a[6k9)r cx`h/sO}x OmXt:3 G@?hr= .7<Sxz.[XI*S$<$i
+Tdbr#2MPVIOv4;g2FK ?L5 L35Df6Ao<xGMzfYhd21oTV/mj7[?B <Qe"&S;7Kj% MI!8-RLv<
+~X?oTsa[}aQcLJu QT#6a'R& V Qz
+P)e aFt"c5G>-|` JhMTz<=?~G=T:|]_`{m7žG:PX' Tyf'YGW\ 93Nr{|ir2?qv?=;
+m"o<[)'^s,E5n?X8bendstream
+endobj
+634 0 obj<</Type/Page/Parent 513 0 R/Contents 635 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F6 8 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+635 0 obj<</Filter/FlateDecode/Length 608 >>stream
+xUo0
+C/QnS6&)6~g 4TiK*_{w~ !/t3rlgG!%e}@1U2z!dXAA8= [+$0?
+endobj
+636 0 obj<</Type/Page/Parent 513 0 R/Contents 637 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F6 8 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+637 0 obj<</Filter/FlateDecode/Length 755 >>stream
+xUMs0+H:c\:.3 it2Xr%9 ]Bca` +=vKo"!Eu\!#z:pA8t];|u]"
+@&][U\\(-P`u80M@iL'<c Sl 2/!)\%*kCqr}][I^<Op)0$o$FA5t!;Ld?B3$,jJXW*S!h~mH_\6e{vuBT 1Q&}<z`;M{@w/v6-/J]Q8=7/G]RRyQB 4.rzzz{-Qu|tZ) b%71})hQK <Z(AH1J6:4oBS)AW^SfNU"EF^sN\YpYcl"wK.'
+cfadao1!endstream
+endobj
+638 0 obj<</Type/Page/Parent 513 0 R/Contents 639 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F6 8 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+639 0 obj<</Filter/FlateDecode/Length 914 >>stream
+xVQ8~>@X &*m&PV+8nÁ¦²ÊýúÉ]Ú,«S7f#l80#{>q |v[q WW /-xG )8[L&m1%Wb+_vZn;;)w-8ip
+2t0HMXw&^~3AIu8õu¹Š'C(YvI0mlU)% {>r/e&j,[-aX[O hq1r@
+o^dwjTn*!ih1Int65 CYRr AZCfRz[›¢õ[@msD#GuZGicFnw7Y98Jy2-dUI3^mT<29+"1nb5pRx2M R0FiAvy!1
+(j7$W|p
+E%FA.Ji1Rh%ce[.i|›­3hžÚ]q3`§M#2&S~g@h=C97g"5]
+8vRi{AH 3O/Ww
+0
+Kx$CzjE<2raendstream
+endobj
+640 0 obj<</Type/Page/Parent 513 0 R/Contents 641 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+641 0 obj<</Filter/FlateDecode/Length 1362 >>stream
+xVr6|WFN(Ve]<(Lz_*(0IBEfN;u98= > i&'t:&Y SM'x?hQwg4QFoBb$£–:?Ž¿#|Da? .iTA$iQd9z@1rBKTNUfO~0} 0 IE2_8O 4\JIT%BS(R$Uz# }ix!eouIuVf=%Jt!yi9$"w$S$SQ+ jnIHI;3:B:}L&D2v@QufNw68l&-eehvlIl2:fojchUï…|ØY*CHK@ Aa
+9L!z^ P fLF_-NS DY X+OlRsn:HBt
+\ >TY2 2K'd+h,/ZYuAuKö?h½RRmyyjop'@ lo#q
+|QwZClsUvºST`W_hUVh]^zJnCcs@Sk H3
+Y2L|/OQcjjUqo_ %DhY!r[t;LlF
+')g3>!>o:endstream
+endobj
+642 0 obj<</Type/Page/Parent 513 0 R/Contents 643 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F6 8 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+643 0 obj<</Filter/FlateDecode/Length 659 >>stream
+xmo0)%f7NBZUjd&!M^0#['wNn% |3I>~U.LEABV-9Y>jE \A\)=a)no~Z2u^F,(dk
+5f,3`4 | ~Lg,"iJI]Yw&Q/=n
+ UFfcgMD1`JUSs7U}~1%4RNWj`Bv6Fe$~Ik)m [rWglT`Ntrhq\p
+endobj
+644 0 obj<</Type/Page/Parent 513 0 R/Contents 645 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F5 7 0 R/F6 8 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+645 0 obj<</Filter/FlateDecode/Length 553 >>stream
+xUn@}+X22 K\Zl$%qkl;kLJb B3s
+): Vj 20¿ëø)8lê€Å,|<0lGO(~4d@)¬ÎÂ5`eMp,iY*K*'77L2$JZ %ETU;K_%iI 6NKA=b)UaTl[[g`{K]2DUyIã´â]ˆì⢄|<)ïyßëB^
+,<YD.]bg7949}=/~Qg=d~9/Ev&=F7gq=NFv
+g;bgqH9Gp']AFkHZ /]aK
+lk}] t&!wU<4+z=`nww<w`T%k.[%zipsZA[_endstream
+endobj
+646 0 obj<</Type/Page/Parent 513 0 R/Contents 647 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F5 7 0 R/F8 10 0 R>>/XObject<<>>>>>>endobj
+647 0 obj<</Filter/FlateDecode/Length 324 >>stream
+x_K0)|hL4I}I>2Pu0 6B8rD@qE %8#e, b"Kt%.
+endobj
+648 0 obj<</Type/Page/Parent 513 0 R/Contents 649 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F8 10 0 R/F9 11 0 R/Fc 12 0 R>>/XObject<<>>>>>>endobj
+649 0 obj<</Filter/FlateDecode/Length 1454 >>stream
+xWMs6W%Zv{1!(m ("! 
+1Jt^Y3$\.Zv_<8<!E1K^[!}|lFIzl:NEmg"SQ':kntFn^U8jqzD
+[A`oH!D#L\:WJ:@*nTV{0kG-{,Y}U
+ wVHEBh"C"uI+ rêF!a.@ocC DJr1 iQL_dh`G 2BT0]'Y*o5>."t>)S\MOtG8V
+d)
+ ZVY-$5dh<G6KZ
+Q/|"iq^5I bp'rDL`FA]!!i{Yuj[b
+G'iNz~3Sb,
+d1biz ePZ`24wh/(*eDBC g@Jzz78][sJmX|
+~.0]|~ - :5PcR8l{ey7YJ*N"YA @$0n&&q#tZ>tX"79l\! tV*U`@Z8ELw9
+0[QPQ2uPDU1 v7dwo]J l%&v/`%,!8oQ
+endobj
+650 0 obj<</Type/Page/Parent 513 0 R/Contents 651 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F2 5 0 R/F4 6 0 R/F8 10 0 R>>/XObject<<>>>>>>endobj
+651 0 obj<</Filter/FlateDecode/Length 1640 >>stream
+xWnF}W dIQ$')ZZ%&
+d9$9sA^))G[{mzC)nKJVQ
+=UwC6T4c'N3sC;{[
+
+5*ta;´¼-©o[Þ¾Š™¯æóÒ"‚ªB#-*X6/
+Y\ 8yn!'Sa\y,2TXbU_7kt0P^^NNk
+I8{P|]1h'3f&P;BsUD ,k])3o).AKx m NE:-1gu
+1yac79U%
+R+u`CL om^XuFd| V@?U{<mNw)TJKT6G5,^#V}{x`fg3# YKJp \L=G7$  ^+V'q>*48k%bYP=r|J^K^:!cC\
+3 RBh6j),qfM&_kEn
+'#C\Oq%VM,Kj|'$r/{aw7 }up~xrb+r{}3>q4Ss1]bHBlA5hendstream
+endobj
+652 0 obj<</Type/Page/Parent 513 0 R/Contents 653 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F8 10 0 R/F9 11 0 R/Fc 12 0 R>>/XObject<<>>>>>>endobj
+653 0 obj<</Filter/FlateDecode/Length 1508 >>stream
+xWoGb>$5gpTJ*TrM[{g}11""776M([zg;ZItvb}JsBV1)=hr!*]{y2IM.I +9mTUEI_*\JVSQN!Q [92RI'_dVf)CL+J:A uf/p2lsjR.yMJ C-UqCfAW\!
+IDY2\S)P:@
+LW<\d;CY3NyK1W + ,vewL}\bF9 h nB17.8ø ãëí“Ð̈́Þj½—^Zo"7oaPR*`y\-:5_]h'uV2` SÝ*á¡»‘„ÍigD/X9?ZG0 F~
+Z;!o./&]"fyO@)A
+^ ,([sOjIbo?{o
+& \^W "={_endstream
+endobj
+654 0 obj<</Type/Page/Parent 513 0 R/Contents 655 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F8 10 0 R/Fc 12 0 R>>/XObject<<>>>>>>endobj
+655 0 obj<</Filter/FlateDecode/Length 1693 >>stream
+xX]o6}
+[37oze~}3_]L/_MF0 T :VK%2&aq { cxKaj%N.e,LZ&Búʁ
+nìšç9`L1"u&@
+$aTX=3\B: </-)zumZDRQK 5W{~+3.,0d
+mEsKKt7KI.+nnH+D+<eo.M<e+-Ef">04,4Ldv$O?B<s(LtdPL lt"6O{@OGDb t/E+Z9Vjk%R!*w !k6qmPvp!T 2^j6AC
+x–M,,;c@";t7f<ld-!cNXE
+LX<*a=[kR=
+
+Esx5@/E ;,~YpZ:uD#=//q2+ "vt&~evE
+c*rB]HTU, GSE7)lt7Lg_œžgð’a·)‰ó D\|coO~&bRzVN:6sV&PUV?M^OBnlo.q+U:K%44xd'$Xj (qSi4_Ix3bn9N4'wkx%-+z[E7ñ0¥ÚR;
++C1?
+ r}TP(+@p3#Gh#3<iAƒ§ƒ°QxoHC \^+3k~0wo8J. \g #Ž•¸¾b¿°q¸¡Ç<Ô<·v½+0gód8…Ce0 M<Mbendstream
+endobj
+656 0 obj<</Type/Page/Parent 513 0 R/Contents 657 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F8 10 0 R/Fc 12 0 R>>/XObject<<>>>>>>endobj
+657 0 obj<</Filter/FlateDecode/Length 304 >>stream
+x5n0E@"ib C\~}'<dydgg7dYp$3q*)FB,`!f`T"A<Q*8(Fe1fNo jG7!~"+ITu_OQ\ev$jK_\v'5TBRÞñÌÙ3Ÿ#ºþñµx].°RgGe^NVCF(d$ Y[xde3f>h57*1IJ&:>v8endstream
+endobj
+658 0 obj<</Type/Page/Parent 513 0 R/Contents 659 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+659 0 obj<</Filter/FlateDecode/Length 1223 >>stream
+xVmO687´¥k˕øPv/S 6>i%v=NhZ9o:QZ~?JF4<\N.hy%az#+QyiOV Ani1E> 0`#,0Rs;#$R&Hj2NReG'J,T3yC5_ZSWLC9i' On%PG1?-J*cJ-(pY*h:3E qXQ*a1q'R =:k+&Co_n~Ln)M3vN&n”v9|cu´Íîå󜦟?ßÜ}šO|+0Oxy8'U=,7 {yc9yo&]Od7)9UV$$'d(h-
+Q}=j}- [`w7; &|UK3# mW2+-3R:@*; sj = ^#-P ME1A36j0i#U.Dl
+s^X_W9*
+B-qj,osZ2.:M&\X.h2iq[;^B{i:M[ 2yqlhÎí'4"¼ïÁÇsC,lftLgh\3m[7xPe*EKVV*9|>"/;$!FZ^S„þÆíèeËg‡…×@#t!S0\a
+aqBPtsÃáÌé‡äÖ¬l±‹îZW0
+8pPnMIHf'$7dZ%
+LIq
+luLUn1JaH/3èÂPeck ib‚o²“ObxG9Eyz%t0{UsD)rCz}v
+[V{O* {=*tMl86\Ja2Mpmi40_[ueendstream
+endobj
+660 0 obj<</Type/Page/Parent 513 0 R/Contents 661 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+661 0 obj<</Filter/FlateDecode/Length 1633 >>stream
+xW]O*I}WAtd_\]0wLH3S@_g%fctS! 7]\Q^6;:Jxruf oh8lTfE?ihbxL]\G0r;>M9o;,dr;K.i8lWr0e<@+O[T+iO:dxj<cTN>9{O5R.L9m$ /R@*D-GGkXsdF7^
+4j[*ސgÂ*iÎ}mG.,huAOa`ip*asA4mb#C:~.z5$YUz+JPe'GDvv\[8<X]CWA|()&HfTsWKiS(| 6„6Xj#Z sIP JaMFL]{P{`D/%~'|3"yJ>[FD0"8cZ-P>d`s#B7zUzjZPG`{!l&c&Lx8S ,ffTyed*@Zi-oT#]E%L"^9aZhT#,),a#0 V013 4MR
+ cw4Fr
+endobj
+662 0 obj<</Type/Page/Parent 513 0 R/Contents 663 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F8 10 0 R/F9 11 0 R/Fc 12 0 R>>/XObject<<>>>>>>endobj
+663 0 obj<</Filter/FlateDecode/Length 1678 >>stream
+xVn8|WVlMs>D)RGRq7KN-rwvfv=4dh6^ 8Iu<78u0nJ1-k<>"<<<v0d pZ
+YcV"GQ3Z2A:#4U2= .VBr(5kaVp~2i.TH
+l ?8Xd5 o qK<YUJeGVVQZ#MVC'e\0; mSN6 e\`QV?K$Y?7S(N'ÐVZ<IZI#*wx|/NSrCg;(SZ-'\aTq_\K/t- W/i V0=xOrZ '4prWQ<q#Sp;
+_qf73R( hk;]Diy-z&t.~\&BP$-->/24j?V/vOeñ€ÕÂ5¦ µÎ¢Ð;U=@:P:~[`\WW F2`,UkSdP@4fsN MX+95MN7I>b:)=Wzd#K+SvñÏmËÔúœZBJ+YKHS W9
+W@I=a^d9Is`*c d
+U%p/m%VR[V+aYhkU~$(Un<5[Pl#]BXn38z+NWG pMÀm‘^”ž¸<h‡ºµ|ë´·Üò€î0Ch
+'Da*pXA,aG#.rvi{9yoe>)%E`9cP)w|PHN Tx#nM6 O[>WVa5pH>,c$?
+ýHEXG9`]M?;^k]rd[K?
+RdQ{Ls  %=.:B"^(< 3vWBwmSG,+R%Wd3[;P </?dPzCy[L
+~9E8 L$`4 Kd6G/q58G<
+=(\we fq>Lfs@/9i~zz\/HxS`
+g$d] uTJ:h*ivX6Rz\_)mm K@
+Z3\kNE4Ob'pkZZFi"j#X&KK`VS*<d%7 v7*$Y*@KBtaLY <^3a{c·Ø$V2cB-A(^U>e\\ºE53ok+t>+:qN-endstream
+endobj
+664 0 obj<</Type/Page/Parent 513 0 R/Contents 665 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+665 0 obj<</Filter/FlateDecode/Length 1820 >>stream
+x}W]o8|7'+vron;hp=@_ D%RGRv|fIjIj;;;;fDC|L0ÒýlŽ§üï­¤2|0½¿ÏÞú`2™gÓ·>=>þzâÃòæýï4šÒ²D~(CZq6}]"w84(8t*Gz]V^XeZG[J}k7w5WZ:2oXWKv]`4_hgDnQZV^JœyõÈÔÐ×
+çdÁ¿ˆªÂ£©Þsr}’2TRw2p*N
+9' t(Jg *M'1uu$Qw@- 0ithoTAr94d-O<LF1v $%
+\/{2nr:9l) c-@x0^$)Y 4Sw'Z2J
+e0T}(I;z,PGb>[uQd(
+18b<rc\VN`Q3^gX%zQIHOt+`-0?&JN?©C1i
+#MCp|(MyuuB!HXVV0QExK AE:1.z-hF _bM=]I3bitr'DF%UczLB?4SH,4G
+&S]| 7vP@8 /@/@/]R7?dGdb9|4``#>iyendstream
+endobj
+666 0 obj<</Type/Page/Parent 513 0 R/Contents 667 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F5 7 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+667 0 obj<</Filter/FlateDecode/Length 1196 >>stream
+xVNF}+RB$&JB-1}m1l:b
+!;s93u4>~4i4CM'Xkrcr*_G'# (Lj<PFkc_UM8gtV Gp%9ScxL<-gwE8R<.U{p/$~z~0Egno/d#zru^\QYIYtrq?R:p,yC  45L%[dIGk<_o_[~[MZN[6 5IT&e]^? $YM8e_rXp(liRJM7suD"$I^t5r^d49@&ub) 1/eZx5ni;@ Hft`L
+yP"ipT"I;iR9*$L_nY6JGl=)70~[tH1GR)_8x GJ{i
+t;[DZhH<:~Ocg=Whu,(X)LvE.m
+Xdl`
+kA je\dXKa&q"T5;~ W e<^L\H)^4$(
+:*Re@Q/WLS00
+TXmONg`0l\]4nVNR!P8+qyv)Q_)\PrJ|NIE`vP y=eFfAjBS.e F]7r.y
+fQP! RQ-=*oWJmh%7/u0Z0%i]dh<V50@8C;@.<x>P.endstream
+endobj
+668 0 obj<</Type/Page/Parent 513 0 R/Contents 669 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+669 0 obj<</Filter/FlateDecode/Length 1654 >>stream
+xW]o7|÷¯X% <
+y(;Bwv;Ig@aO$wvvv`FhNtyjzAs|>:x88yEgXa%a)Go*Fiv>?,)[>6rl;>#M]]zAY^z6^/&V+M~km#¹U
+GF&4(.$d 9w| @,gePupG
+wP+8!<8>km09(>6f$.)kB2aQ
+%U -5wV!:
+6vXEy.g C-e|1\ 7_A P[
+45&.7(Dc*:l"GY8zgztC $1Pt5 ,0`<kl"nY#FK={oLA&PzhnUz7B<IfN#9^1oGrgZyHx r=
+RFs;MvD< sCy$%Z4.pF1FEI[7
+=G4{ aE7mQ|,{pR:L~2g2&Nk<kPQ
+S71QF"O%£C-G52a K0dS]ZVica4pze*"!k_4> QLj==hE1 ^f+'b:yJsoKb:/
+endobj
+670 0 obj<</Type/Page/Parent 513 0 R/Contents 671 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F1 4 0 R/F2 5 0 R/F4 6 0 R/F5 7 0 R/F6 8 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+671 0 obj<</Filter/FlateDecode/Length 1549 >>stream
+xWnF}W Xl4uaIZi\yX+ik..II 'u^3z0 i: ,tGo$-g4|#ItJp`0yGWlvnZTp7F\M" -k r8pTN; imNI9
+WRRX 8v%zi!-P@GlzdN
+ dDspEi%ae_
++
+ooh\$dKdO
+`(1%%iSFD.DX >?j|4j;b7HG:l]$Epq7Z$AUTG'X` KtBv^{A|:E9W.2wN>AmS4<#/5*y)(b$RsV]B+DOBX7Fpe% :e* V2w$0Vo0=
+tVOP5_r'?/Tr~Ø kiàGU?gqr~s*+/eL>( faw< R-nKVEO-7l|_#N6w3u@j cjU\-T,@2_x Q\_m<|3q,WNBjDaU [üàsx¾·\¡Ï[_z-bøèVY4P)8Lc*QNO&&rg
+
+&3976i([vF_;/VnS3vXf3001d*I T
+&a~#+rzxKe_@?}VIh_ q4=G73zVp,.sR};4L1u~tendstream
+endobj
+672 0 obj<</Type/Page/Parent 513 0 R/Contents 673 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F5 7 0 R/F6 8 0 R/F8 10 0 R>>/XObject<<>>>>>>endobj
+673 0 obj<</Filter/FlateDecode/Length 816 >>stream
+xm[oH +*k;(-Pa$0/9%F~14!`D~c'!)c6r2[I`E4!Ffh
+~u\i=H9(=|S9+-\SwsksXGZ n4JG-I_/=^>1&}H <6pd-dm/Lht305XmHtFqUFw'~UFX'7rG?h|O4x+Rta;
+;O5Jn)#9dq[/W{UYO^G&\N*1P+(H<!:,:;Whmm*To
+T $2vBVePFl
+uEnKw d{<^#g{]5R6g"h_t,}9S 9y%_jP-t f47r6yJb (ZKû?gyI!sGuW?;-O,+E/AC9$`L&Mq:~,#f.
+1219nG{K5gl
+[#U>KBa"z)d*yC8'!L?-vntMMvLE9\xv{tt!<}[' ent;'dHvM4 Wj?}endstream
+endobj
+674 0 obj<</Count 16/First 675 0 R/Last 801 0 R>>endobj
+675 0 obj<</Parent 674 0 R/Title(Table of Contents)/Dest[516 0 R/XYZ 0 756 0]/Next 676 0 R>>endobj
+676 0 obj<</Parent 674 0 R/Count -1/First 677 0 R/Last 677 0 R/Title(SAMBA Developers Guide)/Dest[524 0 R/XYZ 0 786 0]/Prev 675 0 R/Next 678 0 R>>endobj
+677 0 obj<</Parent 676 0 R/Title(SAMBA Team)/Dest[524 0 R/XYZ 0 762 0]>>endobj
+678 0 obj<</Parent 674 0 R/Title(Abstract)/Dest[526 0 R/XYZ 0 786 0]/Prev 676 0 R/Next 679 0 R>>endobj
+679 0 obj<</Parent 674 0 R/Count -3/First 680 0 R/Last 682 0 R/Title(Chapter 1. Definition of NetBIOS Protocol and Name Resolution Modes)/Dest[532 0 R/XYZ 0 786 0]/Prev 678 0 R/Next 683 0 R>>endobj
+680 0 obj<</Parent 679 0 R/Title(1.1. NETBIOS)/Dest[532 0 R/XYZ 0 738 0]/Next 681 0 R>>endobj
+681 0 obj<</Parent 679 0 R/Title(1.2. BROADCAST NetBIOS)/Dest[532 0 R/XYZ 0 254 0]/Prev 680 0 R/Next 682 0 R>>endobj
+682 0 obj<</Parent 679 0 R/Title(1.3. NBNS NetBIOS)/Dest[534 0 R/XYZ 0 758 0]/Prev 681 0 R>>endobj
+683 0 obj<</Parent 674 0 R/Count -5/First 684 0 R/Last 688 0 R/Title(Chapter 2. Samba Architecture)/Dest[536 0 R/XYZ 0 786 0]/Prev 679 0 R/Next 689 0 R>>endobj
+684 0 obj<</Parent 683 0 R/Title(2.1. Introduction)/Dest[536 0 R/XYZ 0 762 0]/Next 685 0 R>>endobj
+685 0 obj<</Parent 683 0 R/Title(2.2. Multithreading and Samba)/Dest[536 0 R/XYZ 0 581 0]/Prev 684 0 R/Next 686 0 R>>endobj
+686 0 obj<</Parent 683 0 R/Title(2.3. Threading smbd)/Dest[536 0 R/XYZ 0 387 0]/Prev 685 0 R/Next 687 0 R>>endobj
+687 0 obj<</Parent 683 0 R/Title(2.4. Threading nmbd)/Dest[538 0 R/XYZ 0 786 0]/Prev 686 0 R/Next 688 0 R>>endobj
+688 0 obj<</Parent 683 0 R/Title(2.5. nbmd Design)/Dest[538 0 R/XYZ 0 487 0]/Prev 687 0 R>>endobj
+689 0 obj<</Parent 674 0 R/Count -5/First 690 0 R/Last 694 0 R/Title(Chapter 3. The samba DEBUG system)/Dest[540 0 R/XYZ 0 786 0]/Prev 683 0 R/Next 698 0 R>>endobj
+690 0 obj<</Parent 689 0 R/Title(3.1. New Output Syntax)/Dest[540 0 R/XYZ 0 762 0]/Next 691 0 R>>endobj
+691 0 obj<</Parent 689 0 R/Title(3.2. The DEBUG\(\) Macro)/Dest[542 0 R/XYZ 0 786 0]/Prev 690 0 R/Next 692 0 R>>endobj
+692 0 obj<</Parent 689 0 R/Title(3.3. The DEBUGADD\(\) Macro)/Dest[544 0 R/XYZ 0 786 0]/Prev 691 0 R/Next 693 0 R>>endobj
+693 0 obj<</Parent 689 0 R/Title(3.4. The DEBUGLVL\(\) Macro)/Dest[544 0 R/XYZ 0 567 0]/Prev 692 0 R/Next 694 0 R>>endobj
+694 0 obj<</Parent 689 0 R/Count -3/First 695 0 R/Last 697 0 R/Title(3.5. New Functions)/Dest[546 0 R/XYZ 0 786 0]/Prev 693 0 R>>endobj
+695 0 obj<</Parent 694 0 R/Title(3.5.1. dbgtext\(\))/Dest[546 0 R/XYZ 0 766 0]/Next 696 0 R>>endobj
+696 0 obj<</Parent 694 0 R/Title(3.5.2. dbghdr\(\))/Dest[546 0 R/XYZ 0 655 0]/Prev 695 0 R/Next 697 0 R>>endobj
+697 0 obj<</Parent 694 0 R/Title(3.5.3. format_debug_text\(\))/Dest[546 0 R/XYZ 0 543 0]/Prev 696 0 R>>endobj
+698 0 obj<</Parent 674 0 R/Title(Chapter 4. Coding Suggestions)/Dest[548 0 R/XYZ 0 786 0]/Prev 689 0 R/Next 699 0 R>>endobj
+699 0 obj<</Parent 674 0 R/Count -5/First 700 0 R/Last 721 0 R/Title(Chapter 5. Samba Internals)/Dest[552 0 R/XYZ 0 786 0]/Prev 698 0 R/Next 722 0 R>>endobj
+700 0 obj<</Parent 699 0 R/Title(5.1. Character Handling)/Dest[552 0 R/XYZ 0 762 0]/Next 701 0 R>>endobj
+701 0 obj<</Parent 699 0 R/Title(5.2. The new functions)/Dest[552 0 R/XYZ 0 621 0]/Prev 700 0 R/Next 702 0 R>>endobj
+702 0 obj<</Parent 699 0 R/Count -15/First 703 0 R/Last 717 0 R/Title(5.3. Macros in byteorder.h)/Dest[554 0 R/XYZ 0 758 0]/Prev 701 0 R/Next 718 0 R>>endobj
+703 0 obj<</Parent 702 0 R/Title(5.3.1. CVAL\(buf,pos\))/Dest[554 0 R/XYZ 0 683 0]/Next 704 0 R>>endobj
+704 0 obj<</Parent 702 0 R/Title(5.3.2. PVAL\(buf,pos\))/Dest[554 0 R/XYZ 0 624 0]/Prev 703 0 R/Next 705 0 R>>endobj
+705 0 obj<</Parent 702 0 R/Title(5.3.3. SCVAL\(buf,pos,val\))/Dest[554 0 R/XYZ 0 566 0]/Prev 704 0 R/Next 706 0 R>>endobj
+706 0 obj<</Parent 702 0 R/Title(5.3.4. SVAL\(buf,pos\))/Dest[554 0 R/XYZ 0 507 0]/Prev 705 0 R/Next 707 0 R>>endobj
+707 0 obj<</Parent 702 0 R/Title(5.3.5. IVAL\(buf,pos\))/Dest[554 0 R/XYZ 0 436 0]/Prev 706 0 R/Next 708 0 R>>endobj
+708 0 obj<</Parent 702 0 R/Title(5.3.6. SVALS\(buf,pos\))/Dest[554 0 R/XYZ 0 377 0]/Prev 707 0 R/Next 709 0 R>>endobj
+709 0 obj<</Parent 702 0 R/Title(5.3.7. IVALS\(buf,pos\))/Dest[554 0 R/XYZ 0 319 0]/Prev 708 0 R/Next 710 0 R>>endobj
+710 0 obj<</Parent 702 0 R/Title(5.3.8. SSVAL\(buf,pos,val\))/Dest[554 0 R/XYZ 0 261 0]/Prev 709 0 R/Next 711 0 R>>endobj
+711 0 obj<</Parent 702 0 R/Title(5.3.9. SIVAL\(buf,pos,val\))/Dest[554 0 R/XYZ 0 202 0]/Prev 710 0 R/Next 712 0 R>>endobj
+712 0 obj<</Parent 702 0 R/Title(5.3.10. SSVALS\(buf,pos,val\))/Dest[556 0 R/XYZ 0 786 0]/Prev 711 0 R/Next 713 0 R>>endobj
+713 0 obj<</Parent 702 0 R/Title(5.3.11. SIVALS\(buf,pos,val\))/Dest[556 0 R/XYZ 0 728 0]/Prev 712 0 R/Next 714 0 R>>endobj
+714 0 obj<</Parent 702 0 R/Title(5.3.12. RSVAL\(buf,pos\))/Dest[556 0 R/XYZ 0 669 0]/Prev 713 0 R/Next 715 0 R>>endobj
+715 0 obj<</Parent 702 0 R/Title(5.3.13. RIVAL\(buf,pos\))/Dest[556 0 R/XYZ 0 611 0]/Prev 714 0 R/Next 716 0 R>>endobj
+716 0 obj<</Parent 702 0 R/Title(5.3.14. RSSVAL\(buf,pos,val\))/Dest[556 0 R/XYZ 0 553 0]/Prev 715 0 R/Next 717 0 R>>endobj
+717 0 obj<</Parent 702 0 R/Title(5.3.15. RSIVAL\(buf,pos,val\))/Dest[556 0 R/XYZ 0 481 0]/Prev 716 0 R>>endobj
+718 0 obj<</Parent 699 0 R/Count -2/First 719 0 R/Last 720 0 R/Title(5.4. LAN Manager Samba API)/Dest[556 0 R/XYZ 0 423 0]/Prev 702 0 R/Next 721 0 R>>endobj
+719 0 obj<</Parent 718 0 R/Title(5.4.1. Parameters)/Dest[556 0 R/XYZ 0 273 0]/Next 720 0 R>>endobj
+720 0 obj<</Parent 718 0 R/Title(5.4.2. Return value)/Dest[558 0 R/XYZ 0 494 0]/Prev 719 0 R>>endobj
+721 0 obj<</Parent 699 0 R/Title(5.5. Code character table)/Dest[560 0 R/XYZ 0 786 0]/Prev 718 0 R>>endobj
+722 0 obj<</Parent 674 0 R/Count -2/First 723 0 R/Last 727 0 R/Title(Chapter 6. The smb.conf file)/Dest[562 0 R/XYZ 0 786 0]/Prev 699 0 R/Next 729 0 R>>endobj
+723 0 obj<</Parent 722 0 R/Count -3/First 724 0 R/Last 726 0 R/Title(6.1. Lexical Analysis)/Dest[562 0 R/XYZ 0 762 0]/Next 727 0 R>>endobj
+724 0 obj<</Parent 723 0 R/Title(6.1.1. Handling of Whitespace)/Dest[562 0 R/XYZ 0 476 0]/Next 725 0 R>>endobj
+725 0 obj<</Parent 723 0 R/Title(6.1.2. Handling of Line Continuation)/Dest[562 0 R/XYZ 0 312 0]/Prev 724 0 R/Next 726 0 R>>endobj
+726 0 obj<</Parent 723 0 R/Title(6.1.3. Line Continuation Quirks)/Dest[564 0 R/XYZ 0 705 0]/Prev 725 0 R>>endobj
+727 0 obj<</Parent 722 0 R/Count -1/First 728 0 R/Last 728 0 R/Title(6.2. Syntax)/Dest[564 0 R/XYZ 0 293 0]/Prev 723 0 R>>endobj
+728 0 obj<</Parent 727 0 R/Title(6.2.1. About params.c)/Dest[566 0 R/XYZ 0 718 0]>>endobj
+729 0 obj<</Parent 674 0 R/Count -9/First 730 0 R/Last 738 0 R/Title(Chapter 7. NetBIOS in a Unix World)/Dest[568 0 R/XYZ 0 786 0]/Prev 722 0 R/Next 739 0 R>>endobj
+730 0 obj<</Parent 729 0 R/Title(7.1. Introduction)/Dest[568 0 R/XYZ 0 762 0]/Next 731 0 R>>endobj
+731 0 obj<</Parent 729 0 R/Title(7.2. Usernames)/Dest[568 0 R/XYZ 0 647 0]/Prev 730 0 R/Next 732 0 R>>endobj
+732 0 obj<</Parent 729 0 R/Title(7.3. File Ownership)/Dest[568 0 R/XYZ 0 269 0]/Prev 731 0 R/Next 733 0 R>>endobj
+733 0 obj<</Parent 729 0 R/Title(7.4. Passwords)/Dest[570 0 R/XYZ 0 745 0]/Prev 732 0 R/Next 734 0 R>>endobj
+734 0 obj<</Parent 729 0 R/Title(7.5. Locking)/Dest[570 0 R/XYZ 0 511 0]/Prev 733 0 R/Next 735 0 R>>endobj
+735 0 obj<</Parent 729 0 R/Title(7.6. Deny Modes)/Dest[572 0 R/XYZ 0 786 0]/Prev 734 0 R/Next 736 0 R>>endobj
+736 0 obj<</Parent 729 0 R/Title(7.7. Trapdoor UIDs)/Dest[572 0 R/XYZ 0 619 0]/Prev 735 0 R/Next 737 0 R>>endobj
+737 0 obj<</Parent 729 0 R/Title(7.8. Port numbers)/Dest[572 0 R/XYZ 0 491 0]/Prev 736 0 R/Next 738 0 R>>endobj
+738 0 obj<</Parent 729 0 R/Title(7.9. Protocol Complexity)/Dest[572 0 R/XYZ 0 231 0]/Prev 737 0 R>>endobj
+739 0 obj<</Parent 674 0 R/Title(Chapter 8. Tracing samba system calls)/Dest[576 0 R/XYZ 0 786 0]/Prev 729 0 R/Next 740 0 R>>endobj
+740 0 obj<</Parent 674 0 R/Count -8/First 741 0 R/Last 777 0 R/Title(Chapter 9. NT Domain RPC's)/Dest[580 0 R/XYZ 0 786 0]/Prev 739 0 R/Next 780 0 R>>endobj
+741 0 obj<</Parent 740 0 R/Count -2/First 742 0 R/Last 743 0 R/Title(9.1. Introduction)/Dest[580 0 R/XYZ 0 762 0]/Next 744 0 R>>endobj
+742 0 obj<</Parent 741 0 R/Title(9.1.1. Sources)/Dest[582 0 R/XYZ 0 679 0]/Next 743 0 R>>endobj
+743 0 obj<</Parent 741 0 R/Title(9.1.2. Credits)/Dest[582 0 R/XYZ 0 569 0]/Prev 742 0 R>>endobj
+744 0 obj<</Parent 740 0 R/Count -3/First 745 0 R/Last 747 0 R/Title(9.2. Notes and Structures)/Dest[582 0 R/XYZ 0 447 0]/Prev 741 0 R/Next 748 0 R>>endobj
+745 0 obj<</Parent 744 0 R/Title(9.2.1. Notes)/Dest[582 0 R/XYZ 0 426 0]/Next 746 0 R>>endobj
+746 0 obj<</Parent 744 0 R/Title(9.2.2. Enumerations)/Dest[584 0 R/XYZ 0 771 0]/Prev 745 0 R/Next 747 0 R>>endobj
+747 0 obj<</Parent 744 0 R/Title(9.2.3. Structures)/Dest[584 0 R/XYZ 0 288 0]/Prev 746 0 R>>endobj
+748 0 obj<</Parent 740 0 R/Count -12/First 749 0 R/Last 760 0 R/Title(9.3. MSRPC over Transact Named Pipe)/Dest[604 0 R/XYZ 0 481 0]/Prev 744 0 R/Next 761 0 R>>endobj
+749 0 obj<</Parent 748 0 R/Title(9.3.1. MSRPC Pipes)/Dest[604 0 R/XYZ 0 419 0]/Next 750 0 R>>endobj
+750 0 obj<</Parent 748 0 R/Title(9.3.2. Header)/Dest[606 0 R/XYZ 0 620 0]/Prev 749 0 R/Next 751 0 R>>endobj
+751 0 obj<</Parent 748 0 R/Title(9.3.3. Tail)/Dest[614 0 R/XYZ 0 584 0]/Prev 750 0 R/Next 752 0 R>>endobj
+752 0 obj<</Parent 748 0 R/Title(9.3.4. RPC Bind / Bind Ack)/Dest[614 0 R/XYZ 0 460 0]/Prev 751 0 R/Next 753 0 R>>endobj
+753 0 obj<</Parent 748 0 R/Title(9.3.5. NTLSA Transact Named Pipe)/Dest[616 0 R/XYZ 0 601 0]/Prev 752 0 R/Next 754 0 R>>endobj
+754 0 obj<</Parent 748 0 R/Title(9.3.6. LSA Open Policy)/Dest[616 0 R/XYZ 0 193 0]/Prev 753 0 R/Next 755 0 R>>endobj
+755 0 obj<</Parent 748 0 R/Title(9.3.7. LSA Query Info Policy)/Dest[618 0 R/XYZ 0 545 0]/Prev 754 0 R/Next 756 0 R>>endobj
+756 0 obj<</Parent 748 0 R/Title(9.3.8. LSA Enumerate Trusted Domains)/Dest[618 0 R/XYZ 0 198 0]/Prev 755 0 R/Next 757 0 R>>endobj
+757 0 obj<</Parent 748 0 R/Title(9.3.9. LSA Open Secret)/Dest[620 0 R/XYZ 0 639 0]/Prev 756 0 R/Next 758 0 R>>endobj
+758 0 obj<</Parent 748 0 R/Title(9.3.10. LSA Close)/Dest[620 0 R/XYZ 0 354 0]/Prev 757 0 R/Next 759 0 R>>endobj
+759 0 obj<</Parent 748 0 R/Title(9.3.11. LSA Lookup SIDS)/Dest[622 0 R/XYZ 0 786 0]/Prev 758 0 R/Next 760 0 R>>endobj
+760 0 obj<</Parent 748 0 R/Title(9.3.12. LSA Lookup Names)/Dest[622 0 R/XYZ 0 301 0]/Prev 759 0 R>>endobj
+761 0 obj<</Parent 740 0 R/Count -5/First 762 0 R/Last 766 0 R/Title(9.4. NETLOGON rpc Transact Named Pipe)/Dest[624 0 R/XYZ 0 465 0]/Prev 748 0 R/Next 767 0 R>>endobj
+762 0 obj<</Parent 761 0 R/Title(9.4.1. LSA Request Challenge)/Dest[626 0 R/XYZ 0 718 0]/Next 763 0 R>>endobj
+763 0 obj<</Parent 761 0 R/Title(9.4.2. LSA Authenticate 2)/Dest[626 0 R/XYZ 0 326 0]/Prev 762 0 R/Next 764 0 R>>endobj
+764 0 obj<</Parent 761 0 R/Title(9.4.3. LSA Server Password Set)/Dest[628 0 R/XYZ 0 584 0]/Prev 763 0 R/Next 765 0 R>>endobj
+765 0 obj<</Parent 761 0 R/Title(9.4.4. LSA SAM Logon)/Dest[628 0 R/XYZ 0 218 0]/Prev 764 0 R/Next 766 0 R>>endobj
+766 0 obj<</Parent 761 0 R/Title(9.4.5. LSA SAM Logoff)/Dest[630 0 R/XYZ 0 406 0]/Prev 765 0 R>>endobj
+767 0 obj<</Parent 740 0 R/Count -2/First 768 0 R/Last 769 0 R/Title(9.5. \\\\MAILSLOT\\NET\\NTLOGON)/Dest[632 0 R/XYZ 0 786 0]/Prev 761 0 R/Next 770 0 R>>endobj
+768 0 obj<</Parent 767 0 R/Title(9.5.1. Query for PDC)/Dest[632 0 R/XYZ 0 711 0]/Next 769 0 R>>endobj
+769 0 obj<</Parent 767 0 R/Title(9.5.2. SAM Logon)/Dest[634 0 R/XYZ 0 786 0]/Prev 768 0 R>>endobj
+770 0 obj<</Parent 740 0 R/Count -2/First 771 0 R/Last 772 0 R/Title(9.6. SRVSVC Transact Named Pipe)/Dest[636 0 R/XYZ 0 758 0]/Prev 767 0 R/Next 773 0 R>>endobj
+771 0 obj<</Parent 770 0 R/Title(9.6.1. Net Share Enum)/Dest[636 0 R/XYZ 0 630 0]/Next 772 0 R>>endobj
+772 0 obj<</Parent 770 0 R/Title(9.6.2. Net Server Get Info)/Dest[638 0 R/XYZ 0 786 0]/Prev 771 0 R>>endobj
+773 0 obj<</Parent 740 0 R/Count -3/First 774 0 R/Last 776 0 R/Title(9.7. Cryptographic side of NT Domain Authentication)/Dest[638 0 R/XYZ 0 486 0]/Prev 770 0 R/Next 777 0 R>>endobj
+774 0 obj<</Parent 773 0 R/Title(9.7.1. Definitions)/Dest[638 0 R/XYZ 0 466 0]/Next 775 0 R>>endobj
+775 0 obj<</Parent 773 0 R/Title(9.7.2. Protocol)/Dest[640 0 R/XYZ 0 786 0]/Prev 774 0 R/Next 776 0 R>>endobj
+776 0 obj<</Parent 773 0 R/Title(9.7.3. Comments)/Dest[640 0 R/XYZ 0 437 0]/Prev 775 0 R>>endobj
+777 0 obj<</Parent 740 0 R/Count -2/First 778 0 R/Last 779 0 R/Title(9.8. SIDs and RIDs)/Dest[640 0 R/XYZ 0 181 0]/Prev 773 0 R>>endobj
+778 0 obj<</Parent 777 0 R/Title(9.8.1. Well-known SIDs)/Dest[642 0 R/XYZ 0 686 0]/Next 779 0 R>>endobj
+779 0 obj<</Parent 777 0 R/Title(9.8.2. Well-known RIDS)/Dest[644 0 R/XYZ 0 718 0]/Prev 778 0 R>>endobj
+780 0 obj<</Parent 674 0 R/Count -5/First 781 0 R/Last 785 0 R/Title(Chapter 10. Samba Printing Internals)/Dest[648 0 R/XYZ 0 786 0]/Prev 740 0 R/Next 786 0 R>>endobj
+781 0 obj<</Parent 780 0 R/Title(10.1. Abstract)/Dest[648 0 R/XYZ 0 762 0]/Next 782 0 R>>endobj
+782 0 obj<</Parent 780 0 R/Title(10.2. Printing Interface to Various Back ends)/Dest[648 0 R/XYZ 0 674 0]/Prev 781 0 R/Next 783 0 R>>endobj
+783 0 obj<</Parent 780 0 R/Title(10.3. Print Queue TDB's)/Dest[648 0 R/XYZ 0 414 0]/Prev 782 0 R/Next 784 0 R>>endobj
+784 0 obj<</Parent 780 0 R/Title(10.4. ChangeID & Client Caching of Printer Information)/Dest[652 0 R/XYZ 0 745 0]/Prev 783 0 R/Next 785 0 R>>endobj
+785 0 obj<</Parent 780 0 R/Title(10.5. Windows NT/2K Printer Change Notify)/Dest[652 0 R/XYZ 0 683 0]/Prev 784 0 R>>endobj
+786 0 obj<</Parent 674 0 R/Count -1/First 787 0 R/Last 787 0 R/Title(Chapter 11. Samba WINS Internals)/Dest[658 0 R/XYZ 0 786 0]/Prev 780 0 R/Next 788 0 R>>endobj
+787 0 obj<</Parent 786 0 R/Title(11.1. WINS Failover)/Dest[658 0 R/XYZ 0 762 0]>>endobj
+788 0 obj<</Parent 674 0 R/Count -7/First 789 0 R/Last 800 0 R/Title(Chapter 12. The Upcoming SAM System)/Dest[660 0 R/XYZ 0 786 0]/Prev 786 0 R/Next 801 0 R>>endobj
+789 0 obj<</Parent 788 0 R/Title(12.1. Security in the 'new SAM')/Dest[660 0 R/XYZ 0 762 0]/Next 790 0 R>>endobj
+790 0 obj<</Parent 788 0 R/Title(12.2. Standalone from UNIX)/Dest[662 0 R/XYZ 0 692 0]/Prev 789 0 R/Next 791 0 R>>endobj
+791 0 obj<</Parent 788 0 R/Title(12.3. Handles and Races in the new SAM)/Dest[662 0 R/XYZ 0 551 0]/Prev 790 0 R/Next 792 0 R>>endobj
+792 0 obj<</Parent 788 0 R/Count -3/First 793 0 R/Last 795 0 R/Title(12.4. Layers)/Dest[662 0 R/XYZ 0 251 0]/Prev 791 0 R/Next 796 0 R>>endobj
+793 0 obj<</Parent 792 0 R/Title(12.4.1. Application)/Dest[662 0 R/XYZ 0 231 0]/Next 794 0 R>>endobj
+794 0 obj<</Parent 792 0 R/Title(12.4.2. SAM Interface)/Dest[664 0 R/XYZ 0 786 0]/Prev 793 0 R/Next 795 0 R>>endobj
+795 0 obj<</Parent 792 0 R/Title(12.4.3. SAM Modules)/Dest[664 0 R/XYZ 0 649 0]/Prev 794 0 R>>endobj
+796 0 obj<</Parent 788 0 R/Count -2/First 797 0 R/Last 798 0 R/Title(12.5. SAM Modules)/Dest[664 0 R/XYZ 0 537 0]/Prev 792 0 R/Next 799 0 R>>endobj
+797 0 obj<</Parent 796 0 R/Title(12.5.1. Special Module: sam_passdb)/Dest[664 0 R/XYZ 0 517 0]/Next 798 0 R>>endobj
+798 0 obj<</Parent 796 0 R/Title(12.5.2. sam_ads)/Dest[664 0 R/XYZ 0 419 0]/Prev 797 0 R>>endobj
+799 0 obj<</Parent 788 0 R/Title(12.6. Memory Management)/Dest[664 0 R/XYZ 0 281 0]/Prev 796 0 R/Next 800 0 R>>endobj
+800 0 obj<</Parent 788 0 R/Title(12.7. Testing)/Dest[666 0 R/XYZ 0 542 0]/Prev 799 0 R>>endobj
+801 0 obj<</Parent 674 0 R/Count -3/First 802 0 R/Last 804 0 R/Title(Chapter 13. LanMan and NT Password Encryption)/Dest[668 0 R/XYZ 0 786 0]/Prev 788 0 R>>endobj
+802 0 obj<</Parent 801 0 R/Title(13.1. Introduction)/Dest[668 0 R/XYZ 0 762 0]/Next 803 0 R>>endobj
+803 0 obj<</Parent 801 0 R/Title(13.2. How does it work?)/Dest[668 0 R/XYZ 0 621 0]/Prev 802 0 R/Next 804 0 R>>endobj
+804 0 obj<</Parent 801 0 R/Title(13.3. The smbpasswd file)/Dest[670 0 R/XYZ 0 771 0]/Prev 803 0 R>>endobj
+805 0 obj<</Type/Catalog/Pages 513 0 R/PageLayout/SinglePage/Outlines 674 0 R/OpenAction[524 0 R/XYZ null null 0]/PageMode/UseOutlines/PageLabels<</Nums[0<</P(title)>>1<</S/r>>5<</S/D/St 1/P()>>6<</S/D/St 2/P()>>9<</S/D/St 5/P()>>11<</S/D/St 7/P()>>13<</S/D/St 9/P()>>17<</S/D/St 13/P()>>19<</S/D/St 15/P()>>24<</S/D/St 20/P()>>27<</S/D/St 23/P()>>31<</S/D/St 27/P()>>33<</S/D/St 29/P()>>67<</S/D/St 63/P()>>72<</S/D/St 68/P()>>73<</S/D/St 69/P()>>77<</S/D/St 73/P()>>]>>>>endobj
xref
-0 1806
-0000000001 65535 f
-0000000002 00000 f
-0000000003 00000 f
-0000000004 00000 f
-0000000000 00000 f
-0000000009 00000 n
-0000074011 00000 n
-0000409878 00000 n
-0000000054 00000 n
-0000000130 00000 n
-0000074134 00000 n
-0000409806 00000 n
-0000000177 00000 n
-0000000207 00000 n
-0000074258 00000 n
-0000409720 00000 n
-0000000255 00000 n
-0000000295 00000 n
-0000077595 00000 n
-0000409647 00000 n
-0000000343 00000 n
-0000000378 00000 n
-0000080860 00000 n
-0000409522 00000 n
-0000000424 00000 n
-0000000463 00000 n
-0000080984 00000 n
-0000409448 00000 n
-0000000511 00000 n
-0000000546 00000 n
-0000081297 00000 n
-0000409361 00000 n
-0000000594 00000 n
-0000000641 00000 n
-0000081420 00000 n
-0000409274 00000 n
-0000000689 00000 n
-0000000726 00000 n
-0000085541 00000 n
-0000409187 00000 n
-0000000774 00000 n
-0000000811 00000 n
-0000085665 00000 n
-0000409113 00000 n
-0000000859 00000 n
-0000000893 00000 n
-0000087973 00000 n
-0000408987 00000 n
-0000000939 00000 n
-0000000982 00000 n
-0000088097 00000 n
-0000408913 00000 n
-0000001030 00000 n
-0000001070 00000 n
-0000090917 00000 n
-0000408826 00000 n
-0000001118 00000 n
-0000001160 00000 n
-0000093073 00000 n
-0000408739 00000 n
-0000001208 00000 n
-0000001253 00000 n
-0000093196 00000 n
-0000408652 00000 n
-0000001301 00000 n
-0000001346 00000 n
-0000096049 00000 n
-0000408541 00000 n
-0000001394 00000 n
-0000001430 00000 n
-0000096173 00000 n
-0000408467 00000 n
-0000001483 00000 n
-0000001519 00000 n
-0000096297 00000 n
-0000408380 00000 n
-0000001572 00000 n
-0000001607 00000 n
-0000096421 00000 n
-0000408306 00000 n
-0000001660 00000 n
-0000001712 00000 n
-0000100587 00000 n
-0000408217 00000 n
-0000001758 00000 n
-0000001797 00000 n
-0000109575 00000 n
-0000408089 00000 n
-0000001843 00000 n
-0000001879 00000 n
-0000109699 00000 n
-0000408015 00000 n
-0000001927 00000 n
-0000001968 00000 n
-0000109822 00000 n
-0000407928 00000 n
-0000002016 00000 n
-0000002056 00000 n
-0000113070 00000 n
-0000407799 00000 n
-0000002104 00000 n
-0000002149 00000 n
-0000113194 00000 n
-0000407721 00000 n
-0000002203 00000 n
-0000002244 00000 n
-0000113319 00000 n
-0000407629 00000 n
-0000002298 00000 n
-0000002339 00000 n
-0000113443 00000 n
-0000407537 00000 n
-0000002393 00000 n
-0000002439 00000 n
-0000113568 00000 n
-0000407445 00000 n
-0000002493 00000 n
-0000002534 00000 n
-0000113693 00000 n
-0000407353 00000 n
-0000002588 00000 n
-0000002629 00000 n
-0000113818 00000 n
-0000407261 00000 n
-0000002683 00000 n
-0000002725 00000 n
-0000113942 00000 n
-0000407169 00000 n
-0000002779 00000 n
-0000002821 00000 n
-0000114067 00000 n
-0000407077 00000 n
-0000002875 00000 n
-0000002921 00000 n
-0000114192 00000 n
-0000406985 00000 n
-0000002975 00000 n
-0000003021 00000 n
-0000114317 00000 n
-0000406893 00000 n
-0000003076 00000 n
-0000003124 00000 n
-0000116740 00000 n
-0000406801 00000 n
-0000003179 00000 n
-0000003227 00000 n
-0000116864 00000 n
-0000406709 00000 n
-0000003282 00000 n
-0000003325 00000 n
-0000116989 00000 n
-0000406617 00000 n
-0000003380 00000 n
-0000003423 00000 n
-0000117114 00000 n
-0000406525 00000 n
-0000003478 00000 n
-0000003526 00000 n
-0000117239 00000 n
-0000406447 00000 n
-0000003581 00000 n
-0000003629 00000 n
-0000117364 00000 n
-0000406317 00000 n
-0000003678 00000 n
-0000003723 00000 n
-0000117489 00000 n
-0000406238 00000 n
-0000003777 00000 n
-0000003813 00000 n
-0000121927 00000 n
-0000406159 00000 n
-0000003867 00000 n
-0000003905 00000 n
-0000123591 00000 n
-0000406081 00000 n
-0000003954 00000 n
-0000003998 00000 n
-0000126860 00000 n
-0000405949 00000 n
-0000004045 00000 n
-0000004084 00000 n
-0000126985 00000 n
-0000405831 00000 n
-0000004133 00000 n
-0000004173 00000 n
-0000127549 00000 n
-0000405752 00000 n
-0000004227 00000 n
-0000004275 00000 n
-0000127926 00000 n
-0000405659 00000 n
-0000004329 00000 n
-0000004384 00000 n
-0000129713 00000 n
-0000405580 00000 n
-0000004438 00000 n
-0000004488 00000 n
-0000131602 00000 n
-0000405462 00000 n
-0000004537 00000 n
-0000004567 00000 n
-0000131978 00000 n
-0000405397 00000 n
-0000004621 00000 n
-0000004661 00000 n
-0000135764 00000 n
-0000405264 00000 n
-0000004708 00000 n
-0000004753 00000 n
-0000135889 00000 n
-0000405185 00000 n
-0000004802 00000 n
-0000004838 00000 n
-0000136014 00000 n
-0000405092 00000 n
-0000004887 00000 n
-0000004920 00000 n
-0000136139 00000 n
-0000404999 00000 n
-0000004969 00000 n
-0000005007 00000 n
-0000140317 00000 n
-0000404906 00000 n
-0000005056 00000 n
-0000005089 00000 n
-0000140442 00000 n
-0000404813 00000 n
-0000005138 00000 n
-0000005169 00000 n
-0000140567 00000 n
-0000404720 00000 n
-0000005218 00000 n
-0000005252 00000 n
-0000145032 00000 n
-0000404627 00000 n
-0000005301 00000 n
-0000005338 00000 n
-0000145157 00000 n
-0000404534 00000 n
-0000005387 00000 n
-0000005423 00000 n
-0000145282 00000 n
-0000404455 00000 n
-0000005472 00000 n
-0000005515 00000 n
-0000149905 00000 n
-0000404361 00000 n
-0000005562 00000 n
-0000005610 00000 n
-0000156487 00000 n
-0000404228 00000 n
-0000005657 00000 n
-0000005694 00000 n
-0000156612 00000 n
-0000404110 00000 n
-0000005743 00000 n
-0000005779 00000 n
-0000159990 00000 n
-0000404031 00000 n
-0000005833 00000 n
-0000005866 00000 n
-0000160115 00000 n
-0000403952 00000 n
-0000005920 00000 n
-0000005953 00000 n
-0000160240 00000 n
-0000403820 00000 n
-0000006002 00000 n
-0000006046 00000 n
-0000160364 00000 n
-0000403741 00000 n
-0000006100 00000 n
-0000006131 00000 n
-0000162351 00000 n
-0000403609 00000 n
-0000006185 00000 n
-0000006223 00000 n
-0000162476 00000 n
-0000403530 00000 n
-0000006282 00000 n
-0000006327 00000 n
-0000162601 00000 n
-0000403451 00000 n
-0000006386 00000 n
-0000006431 00000 n
-0000162726 00000 n
-0000403332 00000 n
-0000006485 00000 n
-0000006521 00000 n
-0000162851 00000 n
-0000403253 00000 n
-0000006580 00000 n
-0000006614 00000 n
-0000162976 00000 n
-0000403160 00000 n
-0000006673 00000 n
-0000006705 00000 n
-0000163100 00000 n
-0000403067 00000 n
-0000006764 00000 n
-0000006797 00000 n
-0000163225 00000 n
-0000402974 00000 n
-0000006856 00000 n
-0000006890 00000 n
-0000165031 00000 n
-0000402881 00000 n
-0000006949 00000 n
-0000007012 00000 n
-0000165156 00000 n
-0000402788 00000 n
-0000007071 00000 n
-0000007113 00000 n
-0000165281 00000 n
-0000402695 00000 n
-0000007172 00000 n
-0000007232 00000 n
-0000165406 00000 n
-0000402602 00000 n
-0000007291 00000 n
-0000007372 00000 n
-0000165531 00000 n
-0000402509 00000 n
-0000007431 00000 n
-0000007484 00000 n
-0000165656 00000 n
-0000402416 00000 n
-0000007544 00000 n
-0000007613 00000 n
-0000165781 00000 n
-0000402323 00000 n
-0000007673 00000 n
-0000007736 00000 n
-0000168275 00000 n
-0000402230 00000 n
-0000007796 00000 n
-0000007858 00000 n
-0000168400 00000 n
-0000402137 00000 n
-0000007918 00000 n
-0000007979 00000 n
-0000168525 00000 n
-0000402044 00000 n
-0000008039 00000 n
-0000008128 00000 n
-0000168650 00000 n
-0000401951 00000 n
-0000008188 00000 n
-0000008252 00000 n
-0000168775 00000 n
-0000401858 00000 n
-0000008312 00000 n
-0000008390 00000 n
-0000171173 00000 n
-0000401765 00000 n
-0000008450 00000 n
-0000008525 00000 n
-0000171298 00000 n
-0000401672 00000 n
-0000008585 00000 n
-0000008648 00000 n
-0000171423 00000 n
-0000401579 00000 n
-0000008708 00000 n
-0000008799 00000 n
-0000171548 00000 n
-0000401486 00000 n
-0000008859 00000 n
-0000008958 00000 n
-0000171673 00000 n
-0000401393 00000 n
-0000009018 00000 n
-0000009098 00000 n
-0000173696 00000 n
-0000401300 00000 n
-0000009158 00000 n
-0000009237 00000 n
-0000173821 00000 n
-0000401207 00000 n
-0000009297 00000 n
-0000009347 00000 n
-0000173946 00000 n
-0000401114 00000 n
-0000009407 00000 n
-0000009472 00000 n
-0000175823 00000 n
-0000401021 00000 n
-0000009532 00000 n
-0000009619 00000 n
-0000175948 00000 n
-0000400928 00000 n
-0000009679 00000 n
-0000009740 00000 n
-0000178036 00000 n
-0000400835 00000 n
-0000009800 00000 n
-0000009894 00000 n
-0000178161 00000 n
-0000400742 00000 n
-0000009954 00000 n
-0000010036 00000 n
-0000180504 00000 n
-0000400649 00000 n
-0000010096 00000 n
-0000010150 00000 n
-0000180629 00000 n
-0000400570 00000 n
-0000010210 00000 n
-0000010260 00000 n
-0000184037 00000 n
-0000400437 00000 n
-0000010309 00000 n
-0000010363 00000 n
-0000184162 00000 n
-0000400358 00000 n
-0000010417 00000 n
-0000010454 00000 n
-0000187330 00000 n
-0000400226 00000 n
-0000010508 00000 n
-0000010540 00000 n
-0000187455 00000 n
-0000400147 00000 n
-0000010599 00000 n
-0000010693 00000 n
-0000189840 00000 n
-0000400054 00000 n
-0000010752 00000 n
-0000010804 00000 n
-0000189965 00000 n
-0000399961 00000 n
-0000010863 00000 n
-0000010906 00000 n
-0000190090 00000 n
-0000399868 00000 n
-0000010965 00000 n
-0000011010 00000 n
-0000190215 00000 n
-0000399775 00000 n
-0000011069 00000 n
-0000011114 00000 n
-0000190339 00000 n
-0000399682 00000 n
-0000011173 00000 n
-0000011218 00000 n
-0000193369 00000 n
-0000399589 00000 n
-0000011277 00000 n
-0000011322 00000 n
-0000193493 00000 n
-0000399510 00000 n
-0000011381 00000 n
-0000011426 00000 n
-0000193618 00000 n
-0000399417 00000 n
-0000011480 00000 n
-0000011510 00000 n
-0000193743 00000 n
-0000399324 00000 n
-0000011564 00000 n
-0000011609 00000 n
-0000195987 00000 n
-0000399231 00000 n
-0000011663 00000 n
-0000011714 00000 n
-0000196112 00000 n
-0000399099 00000 n
-0000011768 00000 n
-0000011809 00000 n
-0000197950 00000 n
-0000399020 00000 n
-0000011868 00000 n
-0000011903 00000 n
-0000198075 00000 n
-0000398941 00000 n
-0000011962 00000 n
-0000011998 00000 n
-0000198200 00000 n
-0000398809 00000 n
-0000012052 00000 n
-0000012099 00000 n
-0000198325 00000 n
-0000398730 00000 n
-0000012158 00000 n
-0000012193 00000 n
-0000198450 00000 n
-0000398651 00000 n
-0000012252 00000 n
-0000012288 00000 n
-0000198574 00000 n
-0000398519 00000 n
-0000012342 00000 n
-0000012397 00000 n
-0000198699 00000 n
-0000398440 00000 n
-0000012456 00000 n
-0000012491 00000 n
-0000198824 00000 n
-0000398361 00000 n
-0000012550 00000 n
-0000012586 00000 n
-0000200619 00000 n
-0000398229 00000 n
-0000012640 00000 n
-0000012681 00000 n
-0000200744 00000 n
-0000398150 00000 n
-0000012740 00000 n
-0000012775 00000 n
-0000200869 00000 n
-0000398071 00000 n
-0000012834 00000 n
-0000012870 00000 n
-0000200993 00000 n
-0000397939 00000 n
-0000012925 00000 n
-0000012961 00000 n
-0000201118 00000 n
-0000397860 00000 n
-0000013021 00000 n
-0000013057 00000 n
-0000201242 00000 n
-0000397781 00000 n
-0000013117 00000 n
-0000013154 00000 n
-0000201366 00000 n
-0000397649 00000 n
-0000013209 00000 n
-0000013251 00000 n
-0000201491 00000 n
-0000397570 00000 n
-0000013311 00000 n
-0000013347 00000 n
-0000203187 00000 n
-0000397491 00000 n
-0000013407 00000 n
-0000013444 00000 n
-0000203312 00000 n
-0000397373 00000 n
-0000013499 00000 n
-0000013542 00000 n
-0000203437 00000 n
-0000397294 00000 n
-0000013602 00000 n
-0000013638 00000 n
-0000203562 00000 n
-0000397215 00000 n
-0000013698 00000 n
-0000013735 00000 n
-0000206061 00000 n
-0000397083 00000 n
-0000013784 00000 n
-0000013840 00000 n
-0000206186 00000 n
-0000396965 00000 n
-0000013894 00000 n
-0000013941 00000 n
-0000206311 00000 n
-0000396886 00000 n
-0000014000 00000 n
-0000014035 00000 n
-0000206435 00000 n
-0000396807 00000 n
-0000014094 00000 n
-0000014130 00000 n
-0000208946 00000 n
-0000396675 00000 n
-0000014184 00000 n
+0 806
+0000000000 65535 f
+0000000015 00000 n
+0000000243 00000 n
+0000001809 00000 n
+0000001883 00000 n
+0000001962 00000 n
+0000002044 00000 n
+0000002122 00000 n
+0000002199 00000 n
+0000002278 00000 n
+0000002361 00000 n
+0000002438 00000 n
+0000002520 00000 n
+0000002579 00000 n
+0000002680 00000 n
+0000002782 00000 n
+0000002883 00000 n
+0000002984 00000 n
+0000003086 00000 n
+0000003188 00000 n
+0000003290 00000 n
+0000003391 00000 n
+0000003493 00000 n
+0000003595 00000 n
+0000003697 00000 n
+0000003799 00000 n
+0000003901 00000 n
+0000004002 00000 n
+0000004104 00000 n
+0000004206 00000 n
+0000004308 00000 n
+0000004410 00000 n
+0000004512 00000 n
+0000004614 00000 n
+0000004716 00000 n
+0000004818 00000 n
+0000004919 00000 n
+0000005020 00000 n
+0000005122 00000 n
+0000005224 00000 n
+0000005326 00000 n
+0000005428 00000 n
+0000005530 00000 n
+0000005632 00000 n
+0000005734 00000 n
+0000005836 00000 n
+0000005938 00000 n
+0000006040 00000 n
+0000006142 00000 n
+0000006244 00000 n
+0000006346 00000 n
+0000006448 00000 n
+0000006550 00000 n
+0000006651 00000 n
+0000006751 00000 n
+0000006851 00000 n
+0000007161 00000 n
+0000007262 00000 n
+0000007364 00000 n
+0000007466 00000 n
+0000007568 00000 n
+0000007670 00000 n
+0000007771 00000 n
+0000007873 00000 n
+0000007975 00000 n
+0000008077 00000 n
+0000008179 00000 n
+0000008281 00000 n
+0000008383 00000 n
+0000008484 00000 n
+0000008586 00000 n
+0000008688 00000 n
+0000008790 00000 n
+0000008892 00000 n
+0000008994 00000 n
+0000009096 00000 n
+0000009198 00000 n
+0000009300 00000 n
+0000009402 00000 n
+0000009503 00000 n
+0000009604 00000 n
+0000009706 00000 n
+0000009808 00000 n
+0000009910 00000 n
+0000010012 00000 n
+0000010114 00000 n
+0000010216 00000 n
+0000010318 00000 n
+0000010420 00000 n
+0000010522 00000 n
+0000010624 00000 n
+0000010726 00000 n
+0000010828 00000 n
+0000010930 00000 n
+0000011032 00000 n
+0000011134 00000 n
+0000011236 00000 n
+0000011338 00000 n
+0000011439 00000 n
+0000011539 00000 n
+0000011639 00000 n
+0000011964 00000 n
+0000012066 00000 n
+0000012169 00000 n
+0000012272 00000 n
+0000012375 00000 n
+0000012478 00000 n
+0000012581 00000 n
+0000012684 00000 n
+0000012787 00000 n
+0000012890 00000 n
+0000012993 00000 n
+0000013096 00000 n
+0000013199 00000 n
+0000013302 00000 n
+0000013405 00000 n
+0000013508 00000 n
+0000013611 00000 n
+0000013714 00000 n
+0000013817 00000 n
+0000013920 00000 n
+0000014023 00000 n
+0000014125 00000 n
0000014228 00000 n
-0000209071 00000 n
-0000396596 00000 n
-0000014287 00000 n
-0000014322 00000 n
-0000209196 00000 n
-0000396517 00000 n
-0000014381 00000 n
-0000014417 00000 n
-0000209321 00000 n
-0000396385 00000 n
-0000014471 00000 n
-0000014520 00000 n
-0000209445 00000 n
-0000396306 00000 n
-0000014579 00000 n
-0000014614 00000 n
-0000209569 00000 n
-0000396227 00000 n
-0000014673 00000 n
-0000014709 00000 n
-0000209694 00000 n
-0000396095 00000 n
-0000014763 00000 n
-0000014802 00000 n
-0000211843 00000 n
-0000396016 00000 n
-0000014861 00000 n
-0000014896 00000 n
-0000211968 00000 n
-0000395937 00000 n
-0000014955 00000 n
-0000014991 00000 n
-0000212093 00000 n
-0000395819 00000 n
-0000015045 00000 n
-0000015085 00000 n
-0000212218 00000 n
-0000395740 00000 n
-0000015144 00000 n
-0000015179 00000 n
-0000212342 00000 n
-0000395661 00000 n
-0000015238 00000 n
-0000015274 00000 n
-0000212467 00000 n
-0000395529 00000 n
-0000015323 00000 n
-0000015381 00000 n
-0000214325 00000 n
-0000395411 00000 n
-0000015435 00000 n
-0000015474 00000 n
-0000214450 00000 n
-0000395332 00000 n
-0000015533 00000 n
-0000015568 00000 n
-0000214575 00000 n
-0000395253 00000 n
-0000015627 00000 n
-0000015663 00000 n
-0000214700 00000 n
-0000395135 00000 n
-0000015717 00000 n
-0000015752 00000 n
-0000214825 00000 n
-0000395056 00000 n
-0000015811 00000 n
-0000015846 00000 n
-0000216997 00000 n
-0000394977 00000 n
-0000015905 00000 n
-0000015941 00000 n
-0000217122 00000 n
-0000394845 00000 n
-0000015990 00000 n
-0000016040 00000 n
-0000217247 00000 n
-0000394727 00000 n
-0000016094 00000 n
-0000016134 00000 n
-0000217372 00000 n
-0000394648 00000 n
-0000016193 00000 n
-0000016228 00000 n
-0000219764 00000 n
-0000394569 00000 n
-0000016287 00000 n
-0000016323 00000 n
-0000219889 00000 n
-0000394451 00000 n
-0000016377 00000 n
-0000016422 00000 n
-0000220014 00000 n
-0000394372 00000 n
-0000016481 00000 n
-0000016516 00000 n
-0000220139 00000 n
-0000394293 00000 n
-0000016575 00000 n
-0000016611 00000 n
-0000220264 00000 n
-0000394161 00000 n
-0000016660 00000 n
-0000016730 00000 n
-0000220388 00000 n
-0000394082 00000 n
-0000016784 00000 n
-0000016821 00000 n
-0000222204 00000 n
-0000393989 00000 n
-0000016875 00000 n
-0000016909 00000 n
-0000222329 00000 n
-0000393910 00000 n
-0000016963 00000 n
-0000016997 00000 n
-0000224851 00000 n
-0000393792 00000 n
-0000017046 00000 n
-0000017083 00000 n
-0000224976 00000 n
-0000393674 00000 n
-0000017137 00000 n
-0000017178 00000 n
-0000225100 00000 n
-0000393595 00000 n
-0000017237 00000 n
+0000014331 00000 n
+0000014434 00000 n
+0000014537 00000 n
+0000014640 00000 n
+0000014742 00000 n
+0000014845 00000 n
+0000014947 00000 n
+0000015050 00000 n
+0000015153 00000 n
+0000015256 00000 n
+0000015359 00000 n
+0000015462 00000 n
+0000015565 00000 n
+0000015668 00000 n
+0000015771 00000 n
+0000015874 00000 n
+0000015977 00000 n
+0000016080 00000 n
+0000016183 00000 n
+0000016284 00000 n
+0000016385 00000 n
+0000016486 00000 n
+0000016855 00000 n
+0000016957 00000 n
+0000017060 00000 n
+0000017093 00000 n
+0000017148 00000 n
+0000017235 00000 n
0000017290 00000 n
-0000225224 00000 n
-0000393516 00000 n
-0000017349 00000 n
-0000017395 00000 n
-0000227245 00000 n
-0000393398 00000 n
-0000017449 00000 n
-0000017490 00000 n
-0000227370 00000 n
-0000393319 00000 n
-0000017549 00000 n
-0000017597 00000 n
-0000227494 00000 n
-0000393226 00000 n
-0000017656 00000 n
-0000017705 00000 n
-0000227618 00000 n
-0000393147 00000 n
-0000017764 00000 n
-0000017814 00000 n
-0000230703 00000 n
-0000393014 00000 n
-0000017862 00000 n
-0000017909 00000 n
-0000230828 00000 n
-0000392935 00000 n
-0000017959 00000 n
-0000017992 00000 n
-0000230953 00000 n
-0000392842 00000 n
-0000018042 00000 n
-0000018106 00000 n
-0000231078 00000 n
-0000392749 00000 n
-0000018156 00000 n
-0000018198 00000 n
-0000237538 00000 n
-0000392656 00000 n
-0000018248 00000 n
-0000018323 00000 n
-0000237662 00000 n
-0000392577 00000 n
-0000018373 00000 n
-0000018433 00000 n
-0000245224 00000 n
-0000392444 00000 n
-0000018481 00000 n
-0000018524 00000 n
-0000245349 00000 n
-0000392379 00000 n
-0000018574 00000 n
-0000018612 00000 n
-0000249371 00000 n
-0000392246 00000 n
+0000017377 00000 n
+0000017444 00000 n
+0000017530 00000 n
+0000017632 00000 n
+0000017735 00000 n
+0000017838 00000 n
+0000017941 00000 n
+0000018043 00000 n
+0000018146 00000 n
+0000018249 00000 n
+0000018352 00000 n
+0000018455 00000 n
+0000018558 00000 n
0000018660 00000 n
-0000018706 00000 n
-0000249495 00000 n
-0000392167 00000 n
-0000018756 00000 n
-0000018806 00000 n
-0000253383 00000 n
-0000392074 00000 n
-0000018856 00000 n
-0000018901 00000 n
-0000253508 00000 n
-0000391981 00000 n
-0000018951 00000 n
-0000019008 00000 n
-0000253633 00000 n
-0000391849 00000 n
-0000019058 00000 n
-0000019089 00000 n
-0000253757 00000 n
-0000391770 00000 n
-0000019144 00000 n
-0000019182 00000 n
-0000253882 00000 n
-0000391677 00000 n
-0000019237 00000 n
-0000019277 00000 n
-0000254007 00000 n
-0000391598 00000 n
-0000019332 00000 n
-0000019370 00000 n
-0000257545 00000 n
-0000391466 00000 n
-0000019420 00000 n
-0000019456 00000 n
-0000257670 00000 n
-0000391387 00000 n
-0000019511 00000 n
-0000019567 00000 n
-0000257795 00000 n
-0000391308 00000 n
-0000019622 00000 n
-0000019659 00000 n
-0000257920 00000 n
-0000391215 00000 n
-0000019709 00000 n
-0000019751 00000 n
-0000260013 00000 n
-0000391136 00000 n
-0000019801 00000 n
-0000019833 00000 n
-0000263707 00000 n
-0000391003 00000 n
-0000019881 00000 n
-0000019937 00000 n
-0000263832 00000 n
-0000390924 00000 n
-0000019987 00000 n
-0000020024 00000 n
-0000263957 00000 n
-0000390831 00000 n
-0000020074 00000 n
-0000020116 00000 n
-0000267922 00000 n
-0000390752 00000 n
-0000020166 00000 n
-0000020209 00000 n
-0000271955 00000 n
-0000390619 00000 n
-0000020257 00000 n
-0000020287 00000 n
-0000272080 00000 n
-0000390540 00000 n
-0000020337 00000 n
-0000020372 00000 n
-0000272205 00000 n
-0000390408 00000 n
-0000020422 00000 n
-0000020462 00000 n
-0000272330 00000 n
-0000390329 00000 n
-0000020517 00000 n
-0000020558 00000 n
-0000272455 00000 n
-0000390250 00000 n
-0000020613 00000 n
-0000020654 00000 n
-0000275325 00000 n
-0000390132 00000 n
-0000020704 00000 n
-0000020744 00000 n
-0000275450 00000 n
-0000390067 00000 n
-0000020799 00000 n
-0000020865 00000 n
-0000277921 00000 n
-0000389934 00000 n
-0000020913 00000 n
-0000020957 00000 n
-0000278046 00000 n
-0000389855 00000 n
-0000021007 00000 n
-0000021037 00000 n
-0000278171 00000 n
-0000389776 00000 n
-0000021087 00000 n
-0000021128 00000 n
-0000279705 00000 n
-0000389657 00000 n
-0000021176 00000 n
-0000021217 00000 n
-0000279830 00000 n
-0000389578 00000 n
-0000021267 00000 n
-0000021302 00000 n
-0000279955 00000 n
-0000389499 00000 n
-0000021352 00000 n
-0000021384 00000 n
-0000021757 00000 n
-0000021998 00000 n
-0000021436 00000 n
-0000021876 00000 n
-0000021937 00000 n
-0000386543 00000 n
-0000373304 00000 n
-0000386377 00000 n
-0000372870 00000 n
-0000368418 00000 n
-0000372707 00000 n
-0000387416 00000 n
-0000024306 00000 n
-0000023205 00000 n
-0000022083 00000 n
-0000024062 00000 n
-0000368072 00000 n
-0000365019 00000 n
-0000367907 00000 n
-0000024123 00000 n
-0000363188 00000 n
-0000346984 00000 n
-0000363024 00000 n
-0000345060 00000 n
-0000327014 00000 n
-0000344897 00000 n
-0000024184 00000 n
-0000023368 00000 n
-0000326048 00000 n
-0000310254 00000 n
-0000325884 00000 n
-0000023539 00000 n
-0000023709 00000 n
-0000024245 00000 n
-0000023880 00000 n
-0000032730 00000 n
-0000025927 00000 n
-0000024417 00000 n
-0000032608 00000 n
-0000032669 00000 n
-0000026378 00000 n
-0000026530 00000 n
-0000026683 00000 n
-0000026836 00000 n
-0000026990 00000 n
-0000027142 00000 n
-0000027296 00000 n
-0000027450 00000 n
-0000027604 00000 n
-0000027758 00000 n
-0000027911 00000 n
-0000028063 00000 n
-0000028217 00000 n
-0000028370 00000 n
-0000028524 00000 n
-0000028678 00000 n
-0000028832 00000 n
-0000028991 00000 n
-0000029150 00000 n
-0000029309 00000 n
-0000029461 00000 n
-0000029613 00000 n
-0000029767 00000 n
-0000029920 00000 n
-0000030074 00000 n
-0000030233 00000 n
-0000030392 00000 n
-0000030551 00000 n
-0000030710 00000 n
-0000030869 00000 n
-0000031028 00000 n
-0000031187 00000 n
-0000031345 00000 n
-0000031504 00000 n
-0000031664 00000 n
-0000031823 00000 n
-0000031981 00000 n
-0000032140 00000 n
-0000032298 00000 n
-0000032456 00000 n
-0000043285 00000 n
-0000034901 00000 n
-0000032815 00000 n
-0000043224 00000 n
-0000308649 00000 n
-0000299425 00000 n
-0000308485 00000 n
-0000035430 00000 n
-0000035589 00000 n
-0000035748 00000 n
-0000035902 00000 n
-0000036054 00000 n
-0000036208 00000 n
-0000036367 00000 n
-0000036526 00000 n
-0000036684 00000 n
-0000036838 00000 n
-0000036997 00000 n
-0000037149 00000 n
-0000037303 00000 n
-0000037457 00000 n
-0000037611 00000 n
-0000037765 00000 n
-0000037919 00000 n
-0000038073 00000 n
-0000038227 00000 n
-0000038380 00000 n
-0000038534 00000 n
+0000018763 00000 n
+0000018866 00000 n
+0000018969 00000 n
+0000019072 00000 n
+0000019175 00000 n
+0000019278 00000 n
+0000019381 00000 n
+0000019484 00000 n
+0000019586 00000 n
+0000019688 00000 n
+0000019791 00000 n
+0000019894 00000 n
+0000019997 00000 n
+0000020100 00000 n
+0000020203 00000 n
+0000020306 00000 n
+0000020409 00000 n
+0000020512 00000 n
+0000020615 00000 n
+0000020718 00000 n
+0000020821 00000 n
+0000020924 00000 n
+0000021026 00000 n
+0000021127 00000 n
+0000021228 00000 n
+0000021557 00000 n
+0000021660 00000 n
+0000021763 00000 n
+0000021866 00000 n
+0000021969 00000 n
+0000022072 00000 n
+0000022175 00000 n
+0000022278 00000 n
+0000022380 00000 n
+0000022483 00000 n
+0000022586 00000 n
+0000022689 00000 n
+0000022792 00000 n
+0000022895 00000 n
+0000022998 00000 n
+0000023100 00000 n
+0000023203 00000 n
+0000023306 00000 n
+0000023409 00000 n
+0000023512 00000 n
+0000023615 00000 n
+0000023718 00000 n
+0000023821 00000 n
+0000023924 00000 n
+0000024027 00000 n
+0000024129 00000 n
+0000024231 00000 n
+0000024334 00000 n
+0000024437 00000 n
+0000024540 00000 n
+0000024643 00000 n
+0000024746 00000 n
+0000024849 00000 n
+0000024952 00000 n
+0000025055 00000 n
+0000025158 00000 n
+0000025261 00000 n
+0000025364 00000 n
+0000025467 00000 n
+0000025570 00000 n
+0000025673 00000 n
+0000025776 00000 n
+0000025879 00000 n
+0000025982 00000 n
+0000026085 00000 n
+0000026188 00000 n
+0000026291 00000 n
+0000026394 00000 n
+0000026497 00000 n
+0000026599 00000 n
+0000026700 00000 n
+0000026801 00000 n
+0000027226 00000 n
+0000027329 00000 n
+0000027432 00000 n
+0000027535 00000 n
+0000027638 00000 n
+0000027741 00000 n
+0000027844 00000 n
+0000027947 00000 n
+0000028050 00000 n
+0000028153 00000 n
+0000028256 00000 n
+0000028359 00000 n
+0000028462 00000 n
+0000028565 00000 n
+0000028668 00000 n
+0000028770 00000 n
+0000028873 00000 n
+0000028976 00000 n
+0000029079 00000 n
+0000029182 00000 n
+0000029285 00000 n
+0000029387 00000 n
+0000029490 00000 n
+0000029592 00000 n
+0000029695 00000 n
+0000029798 00000 n
+0000029901 00000 n
+0000030004 00000 n
+0000030107 00000 n
+0000030210 00000 n
+0000030313 00000 n
+0000030416 00000 n
+0000030519 00000 n
+0000030622 00000 n
+0000030725 00000 n
+0000030828 00000 n
+0000030930 00000 n
+0000031033 00000 n
+0000031136 00000 n
+0000031239 00000 n
+0000031568 00000 n
+0000031652 00000 n
+0000031738 00000 n
+0000031812 00000 n
+0000031898 00000 n
+0000031931 00000 n
+0000032009 00000 n
+0000032096 00000 n
+0000032202 00000 n
+0000032288 00000 n
+0000032360 00000 n
+0000032446 00000 n
+0000032505 00000 n
+0000032592 00000 n
+0000032683 00000 n
+0000032769 00000 n
+0000032840 00000 n
+0000032926 00000 n
+0000032991 00000 n
+0000033025 00000 n
+0000033059 00000 n
+0000036406 00000 n
+0000036449 00000 n
+0000036492 00000 n
+0000036535 00000 n
+0000036578 00000 n
+0000036621 00000 n
+0000036664 00000 n
+0000036707 00000 n
+0000036750 00000 n
+0000036793 00000 n
+0000036836 00000 n
+0000036879 00000 n
+0000036922 00000 n
+0000036965 00000 n
+0000037008 00000 n
+0000037051 00000 n
+0000037094 00000 n
+0000037137 00000 n
+0000037180 00000 n
+0000037223 00000 n
+0000037266 00000 n
+0000037309 00000 n
+0000037352 00000 n
+0000037395 00000 n
+0000037438 00000 n
+0000037481 00000 n
+0000037524 00000 n
+0000037567 00000 n
+0000037610 00000 n
+0000037653 00000 n
+0000037696 00000 n
+0000037739 00000 n
+0000037782 00000 n
+0000037825 00000 n
+0000037868 00000 n
+0000037911 00000 n
+0000037954 00000 n
+0000037997 00000 n
+0000038040 00000 n
+0000038083 00000 n
+0000038126 00000 n
+0000038169 00000 n
+0000038212 00000 n
+0000038255 00000 n
+0000038298 00000 n
+0000038341 00000 n
+0000038384 00000 n
+0000038427 00000 n
+0000038470 00000 n
+0000038513 00000 n
+0000038556 00000 n
+0000038599 00000 n
+0000038642 00000 n
0000038685 00000 n
-0000038836 00000 n
-0000038990 00000 n
-0000039149 00000 n
-0000039308 00000 n
-0000039462 00000 n
-0000039621 00000 n
-0000039780 00000 n
-0000039943 00000 n
-0000040107 00000 n
-0000040266 00000 n
-0000040430 00000 n
-0000040593 00000 n
-0000040757 00000 n
+0000038728 00000 n
+0000038771 00000 n
+0000038814 00000 n
+0000038857 00000 n
+0000038900 00000 n
+0000038943 00000 n
+0000038986 00000 n
+0000039029 00000 n
+0000039072 00000 n
+0000039115 00000 n
+0000039158 00000 n
+0000039201 00000 n
+0000039244 00000 n
+0000039287 00000 n
+0000039330 00000 n
+0000039373 00000 n
+0000039416 00000 n
+0000039459 00000 n
+0000039502 00000 n
+0000039545 00000 n
+0000039588 00000 n
+0000039631 00000 n
+0000039674 00000 n
+0000039717 00000 n
+0000039760 00000 n
+0000039803 00000 n
+0000039846 00000 n
+0000039889 00000 n
+0000039932 00000 n
+0000039975 00000 n
+0000040018 00000 n
+0000040061 00000 n
+0000040104 00000 n
+0000040147 00000 n
+0000040190 00000 n
+0000040233 00000 n
+0000040276 00000 n
+0000040319 00000 n
+0000040362 00000 n
+0000040405 00000 n
+0000040448 00000 n
+0000040491 00000 n
+0000040534 00000 n
+0000040577 00000 n
+0000040620 00000 n
+0000040663 00000 n
+0000040706 00000 n
+0000040749 00000 n
+0000040792 00000 n
+0000040835 00000 n
+0000040878 00000 n
0000040921 00000 n
-0000041085 00000 n
-0000041249 00000 n
-0000041413 00000 n
-0000041577 00000 n
-0000041741 00000 n
-0000041906 00000 n
-0000042070 00000 n
-0000042235 00000 n
-0000042401 00000 n
-0000042566 00000 n
-0000042732 00000 n
-0000042896 00000 n
-0000043060 00000 n
-0000054473 00000 n
-0000045312 00000 n
-0000043383 00000 n
-0000054410 00000 n
-0000045914 00000 n
-0000046080 00000 n
-0000046246 00000 n
-0000046412 00000 n
-0000046578 00000 n
-0000046744 00000 n
-0000046910 00000 n
-0000047076 00000 n
-0000047242 00000 n
-0000047407 00000 n
-0000047573 00000 n
-0000047739 00000 n
-0000047904 00000 n
-0000048059 00000 n
-0000048219 00000 n
-0000048379 00000 n
-0000048544 00000 n
-0000048709 00000 n
-0000048874 00000 n
-0000049039 00000 n
-0000049204 00000 n
-0000049368 00000 n
-0000049533 00000 n
-0000049698 00000 n
-0000049858 00000 n
-0000050017 00000 n
-0000050177 00000 n
-0000050337 00000 n
-0000050502 00000 n
-0000050667 00000 n
-0000050827 00000 n
-0000050992 00000 n
-0000051157 00000 n
-0000051317 00000 n
-0000051481 00000 n
-0000051646 00000 n
-0000051806 00000 n
-0000051970 00000 n
-0000052135 00000 n
-0000052296 00000 n
-0000052462 00000 n
-0000052628 00000 n
-0000052789 00000 n
-0000052955 00000 n
-0000053121 00000 n
-0000053282 00000 n
-0000053447 00000 n
-0000053613 00000 n
-0000053768 00000 n
-0000053927 00000 n
-0000054089 00000 n
-0000054252 00000 n
-0000065016 00000 n
-0000056357 00000 n
-0000054559 00000 n
-0000064953 00000 n
-0000056941 00000 n
-0000057106 00000 n
-0000057271 00000 n
-0000057431 00000 n
-0000057596 00000 n
-0000057761 00000 n
-0000057921 00000 n
-0000058086 00000 n
-0000058251 00000 n
-0000058410 00000 n
-0000058575 00000 n
-0000298991 00000 n
-0000297468 00000 n
-0000298825 00000 n
-0000058740 00000 n
-0000058894 00000 n
-0000059054 00000 n
+0000040964 00000 n
+0000041007 00000 n
+0000041050 00000 n
+0000041093 00000 n
+0000041136 00000 n
+0000041179 00000 n
+0000041222 00000 n
+0000041265 00000 n
+0000041308 00000 n
+0000041351 00000 n
+0000041394 00000 n
+0000041437 00000 n
+0000041480 00000 n
+0000041523 00000 n
+0000041566 00000 n
+0000041609 00000 n
+0000041652 00000 n
+0000041695 00000 n
+0000041738 00000 n
+0000041781 00000 n
+0000041824 00000 n
+0000041867 00000 n
+0000041910 00000 n
+0000041953 00000 n
+0000041996 00000 n
+0000042039 00000 n
+0000042082 00000 n
+0000042125 00000 n
+0000042168 00000 n
+0000042211 00000 n
+0000042254 00000 n
+0000042297 00000 n
+0000042340 00000 n
+0000042383 00000 n
+0000042426 00000 n
+0000042469 00000 n
+0000042512 00000 n
+0000042555 00000 n
+0000042598 00000 n
+0000042641 00000 n
+0000042684 00000 n
+0000042727 00000 n
+0000042770 00000 n
+0000042813 00000 n
+0000042856 00000 n
+0000042899 00000 n
+0000042942 00000 n
+0000042985 00000 n
+0000043028 00000 n
+0000043071 00000 n
+0000043114 00000 n
+0000043157 00000 n
+0000043200 00000 n
+0000043243 00000 n
+0000043286 00000 n
+0000043329 00000 n
+0000043372 00000 n
+0000043415 00000 n
+0000043458 00000 n
+0000043501 00000 n
+0000043544 00000 n
+0000043587 00000 n
+0000043630 00000 n
+0000043673 00000 n
+0000043716 00000 n
+0000043759 00000 n
+0000043802 00000 n
+0000043845 00000 n
+0000043888 00000 n
+0000043931 00000 n
+0000043974 00000 n
+0000044017 00000 n
+0000044060 00000 n
+0000044103 00000 n
+0000044146 00000 n
+0000044189 00000 n
+0000044232 00000 n
+0000044275 00000 n
+0000044318 00000 n
+0000044361 00000 n
+0000044404 00000 n
+0000044447 00000 n
+0000044490 00000 n
+0000044533 00000 n
+0000044576 00000 n
+0000044619 00000 n
+0000044662 00000 n
+0000044705 00000 n
+0000044748 00000 n
+0000044791 00000 n
+0000044834 00000 n
+0000044877 00000 n
+0000044920 00000 n
+0000044963 00000 n
+0000045006 00000 n
+0000045049 00000 n
+0000045092 00000 n
+0000045135 00000 n
+0000045178 00000 n
+0000045221 00000 n
+0000045264 00000 n
+0000045307 00000 n
+0000045350 00000 n
+0000046037 00000 n
+0000046195 00000 n
+0000046362 00000 n
+0000046552 00000 n
+0000049149 00000 n
+0000049340 00000 n
+0000052448 00000 n
+0000052639 00000 n
+0000056177 00000 n
+0000056368 00000 n
+0000056827 00000 n
+0000056985 00000 n
+0000057214 00000 n
+0000057414 00000 n
0000059219 00000 n
-0000059384 00000 n
-0000059544 00000 n
-0000059709 00000 n
-0000059874 00000 n
-0000060029 00000 n
-0000060189 00000 n
-0000060353 00000 n
-0000060518 00000 n
-0000060678 00000 n
-0000060843 00000 n
-0000061007 00000 n
-0000061162 00000 n
-0000061322 00000 n
-0000061482 00000 n
-0000061642 00000 n
-0000061797 00000 n
-0000061957 00000 n
-0000062122 00000 n
-0000062287 00000 n
-0000062446 00000 n
-0000062611 00000 n
-0000062776 00000 n
-0000062940 00000 n
-0000063093 00000 n
-0000063249 00000 n
-0000063405 00000 n
-0000063561 00000 n
-0000063717 00000 n
-0000063873 00000 n
-0000064027 00000 n
-0000064183 00000 n
-0000064336 00000 n
-0000064491 00000 n
-0000064645 00000 n
-0000064799 00000 n
-0000070703 00000 n
-0000066354 00000 n
-0000065129 00000 n
-0000070640 00000 n
-0000066714 00000 n
-0000066875 00000 n
-0000067036 00000 n
-0000067197 00000 n
-0000067353 00000 n
-0000067514 00000 n
-0000067675 00000 n
-0000067831 00000 n
-0000067987 00000 n
-0000068141 00000 n
-0000068297 00000 n
-0000068452 00000 n
-0000068608 00000 n
-0000068762 00000 n
-0000068918 00000 n
-0000069074 00000 n
-0000069235 00000 n
-0000069396 00000 n
-0000069552 00000 n
-0000069712 00000 n
-0000069866 00000 n
-0000070021 00000 n
-0000070176 00000 n
-0000070328 00000 n
-0000070484 00000 n
-0000387536 00000 n
-0000074382 00000 n
-0000073825 00000 n
-0000070802 00000 n
-0000073948 00000 n
-0000074071 00000 n
-0000074195 00000 n
-0000074319 00000 n
-0000077719 00000 n
-0000077409 00000 n
-0000074468 00000 n
-0000077532 00000 n
-0000077656 00000 n
-0000295566 00000 n
-0000293552 00000 n
-0000295401 00000 n
-0000081795 00000 n
-0000080674 00000 n
-0000077832 00000 n
-0000080797 00000 n
-0000080921 00000 n
-0000081045 00000 n
-0000081108 00000 n
-0000081171 00000 n
-0000081234 00000 n
-0000081358 00000 n
-0000081481 00000 n
-0000081544 00000 n
-0000081607 00000 n
-0000081670 00000 n
-0000081733 00000 n
-0000085789 00000 n
-0000085229 00000 n
-0000081881 00000 n
-0000085352 00000 n
-0000085415 00000 n
-0000085478 00000 n
-0000085602 00000 n
-0000085726 00000 n
-0000088472 00000 n
-0000087787 00000 n
-0000085888 00000 n
-0000087910 00000 n
-0000088034 00000 n
-0000088158 00000 n
-0000088221 00000 n
-0000088284 00000 n
-0000088347 00000 n
-0000088410 00000 n
-0000091041 00000 n
-0000090731 00000 n
-0000088571 00000 n
-0000090854 00000 n
-0000090978 00000 n
-0000387661 00000 n
-0000093320 00000 n
-0000092887 00000 n
-0000091167 00000 n
-0000093010 00000 n
-0000093134 00000 n
-0000093257 00000 n
-0000096545 00000 n
-0000095674 00000 n
-0000093432 00000 n
-0000095797 00000 n
-0000095860 00000 n
-0000095923 00000 n
-0000095986 00000 n
-0000096110 00000 n
-0000096234 00000 n
-0000096358 00000 n
-0000096482 00000 n
-0000101214 00000 n
-0000099982 00000 n
-0000096657 00000 n
-0000100524 00000 n
-0000100648 00000 n
-0000100135 00000 n
-0000100334 00000 n
-0000100711 00000 n
-0000100774 00000 n
-0000100837 00000 n
-0000100900 00000 n
-0000100963 00000 n
-0000101026 00000 n
-0000101089 00000 n
-0000101152 00000 n
-0000106005 00000 n
-0000104751 00000 n
-0000101313 00000 n
-0000104874 00000 n
-0000104937 00000 n
-0000105000 00000 n
-0000105062 00000 n
-0000105125 00000 n
-0000105188 00000 n
-0000105251 00000 n
-0000105314 00000 n
-0000105376 00000 n
-0000105439 00000 n
-0000105502 00000 n
-0000105565 00000 n
-0000105627 00000 n
-0000105690 00000 n
-0000105753 00000 n
-0000105816 00000 n
-0000105879 00000 n
-0000105942 00000 n
-0000110449 00000 n
-0000109389 00000 n
-0000106091 00000 n
-0000109512 00000 n
-0000109636 00000 n
-0000109760 00000 n
-0000109883 00000 n
-0000109946 00000 n
-0000110009 00000 n
-0000110072 00000 n
-0000110135 00000 n
-0000110198 00000 n
-0000110261 00000 n
-0000110324 00000 n
-0000110387 00000 n
-0000114439 00000 n
-0000112695 00000 n
-0000110535 00000 n
-0000112818 00000 n
-0000112881 00000 n
-0000112944 00000 n
-0000113007 00000 n
-0000113131 00000 n
-0000113256 00000 n
-0000113380 00000 n
-0000113505 00000 n
-0000113630 00000 n
-0000113755 00000 n
-0000113880 00000 n
-0000114004 00000 n
-0000114129 00000 n
-0000114254 00000 n
-0000114378 00000 n
-0000387786 00000 n
-0000118116 00000 n
-0000116554 00000 n
-0000114538 00000 n
-0000116677 00000 n
-0000116802 00000 n
-0000116926 00000 n
-0000117051 00000 n
-0000117176 00000 n
-0000117301 00000 n
-0000117426 00000 n
-0000117551 00000 n
-0000117614 00000 n
-0000117677 00000 n
-0000117740 00000 n
+0000059391 00000 n
+0000061477 00000 n
+0000061649 00000 n
+0000063568 00000 n
+0000063735 00000 n
+0000065380 00000 n
+0000065547 00000 n
+0000067089 00000 n
+0000067256 00000 n
+0000068990 00000 n
+0000069157 00000 n
+0000070893 00000 n
+0000071069 00000 n
+0000072334 00000 n
+0000072510 00000 n
+0000073721 00000 n
+0000073897 00000 n
+0000075145 00000 n
+0000075312 00000 n
+0000076222 00000 n
+0000076413 00000 n
+0000078380 00000 n
+0000078537 00000 n
+0000080320 00000 n
+0000080487 00000 n
+0000082471 00000 n
+0000082638 00000 n
+0000083374 00000 n
+0000083550 00000 n
+0000084592 00000 n
+0000084759 00000 n
+0000086395 00000 n
+0000086562 00000 n
+0000087186 00000 n
+0000087362 00000 n
+0000088690 00000 n
+0000088866 00000 n
+0000089940 00000 n
+0000090107 00000 n
+0000090708 00000 n
+0000090875 00000 n
+0000092661 00000 n
+0000092828 00000 n
+0000094545 00000 n
+0000094712 00000 n
+0000096561 00000 n
+0000096718 00000 n
+0000097833 00000 n
+0000098018 00000 n
+0000099625 00000 n
+0000099791 00000 n
+0000100680 00000 n
+0000100880 00000 n
+0000102605 00000 n
+0000102781 00000 n
+0000104608 00000 n
+0000104784 00000 n
+0000105395 00000 n
+0000105571 00000 n
+0000106346 00000 n
+0000106522 00000 n
+0000107279 00000 n
+0000107455 00000 n
+0000108294 00000 n
+0000108470 00000 n
+0000109306 00000 n
+0000109491 00000 n
+0000110331 00000 n
+0000110507 00000 n
+0000111267 00000 n
+0000111433 00000 n
+0000112058 00000 n
+0000112243 00000 n
+0000113011 00000 n
+0000113187 00000 n
+0000114149 00000 n
+0000114334 00000 n
+0000115669 00000 n
+0000115854 00000 n
+0000116872 00000 n
+0000117038 00000 n
+0000117618 00000 n
0000117803 00000 n
-0000117866 00000 n
-0000117928 00000 n
-0000117991 00000 n
-0000118054 00000 n
-0000122240 00000 n
-0000121363 00000 n
-0000118228 00000 n
-0000121486 00000 n
-0000121549 00000 n
-0000121612 00000 n
-0000121675 00000 n
-0000121738 00000 n
-0000121801 00000 n
-0000121864 00000 n
-0000121988 00000 n
-0000122051 00000 n
-0000122114 00000 n
-0000122177 00000 n
-0000124346 00000 n
-0000123405 00000 n
-0000122339 00000 n
-0000123528 00000 n
-0000123653 00000 n
-0000123716 00000 n
-0000123779 00000 n
-0000123842 00000 n
-0000123905 00000 n
-0000123968 00000 n
-0000124031 00000 n
-0000124094 00000 n
-0000124157 00000 n
-0000124220 00000 n
-0000124283 00000 n
-0000128051 00000 n
-0000126674 00000 n
-0000124445 00000 n
-0000126797 00000 n
-0000126922 00000 n
-0000127047 00000 n
-0000127110 00000 n
-0000127173 00000 n
-0000127236 00000 n
-0000127299 00000 n
-0000127362 00000 n
-0000127424 00000 n
-0000127487 00000 n
-0000127611 00000 n
-0000127674 00000 n
-0000127737 00000 n
-0000127800 00000 n
-0000127863 00000 n
-0000127988 00000 n
-0000129836 00000 n
-0000129527 00000 n
-0000128151 00000 n
-0000129650 00000 n
-0000129773 00000 n
-0000132103 00000 n
-0000131416 00000 n
-0000129962 00000 n
-0000131539 00000 n
-0000131664 00000 n
-0000131727 00000 n
-0000131789 00000 n
-0000131852 00000 n
-0000131915 00000 n
-0000132040 00000 n
-0000387911 00000 n
-0000136264 00000 n
-0000135578 00000 n
-0000132229 00000 n
-0000135701 00000 n
-0000135826 00000 n
-0000135951 00000 n
-0000136076 00000 n
-0000136201 00000 n
-0000140692 00000 n
-0000140131 00000 n
-0000136364 00000 n
-0000140254 00000 n
-0000140379 00000 n
-0000140504 00000 n
-0000140629 00000 n
-0000145407 00000 n
-0000144846 00000 n
-0000140791 00000 n
-0000144969 00000 n
-0000145094 00000 n
-0000145219 00000 n
-0000145344 00000 n
-0000146221 00000 n
-0000146035 00000 n
-0000145520 00000 n
-0000146158 00000 n
-0000150030 00000 n
-0000149719 00000 n
-0000146307 00000 n
-0000149842 00000 n
-0000149967 00000 n
-0000292953 00000 n
-0000284233 00000 n
-0000292787 00000 n
-0000283051 00000 n
-0000281175 00000 n
-0000282885 00000 n
-0000151243 00000 n
-0000151057 00000 n
-0000150157 00000 n
-0000151180 00000 n
-0000388036 00000 n
-0000157049 00000 n
-0000154858 00000 n
-0000151342 00000 n
-0000156424 00000 n
-0000156549 00000 n
-0000156674 00000 n
-0000155056 00000 n
-0000155250 00000 n
-0000155444 00000 n
-0000155666 00000 n
-0000155854 00000 n
-0000156030 00000 n
-0000156237 00000 n
-0000156736 00000 n
-0000156799 00000 n
-0000156861 00000 n
-0000156923 00000 n
-0000156986 00000 n
-0000160803 00000 n
-0000159804 00000 n
-0000157175 00000 n
-0000159927 00000 n
-0000160052 00000 n
-0000160177 00000 n
-0000160301 00000 n
-0000160426 00000 n
-0000160489 00000 n
-0000160552 00000 n
-0000160614 00000 n
-0000160677 00000 n
-0000160740 00000 n
-0000163349 00000 n
-0000162165 00000 n
-0000160902 00000 n
-0000162288 00000 n
-0000162413 00000 n
-0000162538 00000 n
-0000162663 00000 n
-0000162788 00000 n
-0000162913 00000 n
-0000163038 00000 n
-0000163162 00000 n
-0000163286 00000 n
-0000165906 00000 n
-0000164845 00000 n
-0000163448 00000 n
-0000164968 00000 n
-0000165093 00000 n
-0000165218 00000 n
-0000165343 00000 n
-0000165468 00000 n
-0000165593 00000 n
-0000165718 00000 n
-0000165843 00000 n
-0000168900 00000 n
-0000168089 00000 n
-0000166018 00000 n
-0000168212 00000 n
-0000168337 00000 n
-0000168462 00000 n
-0000168587 00000 n
-0000168712 00000 n
-0000168837 00000 n
-0000171798 00000 n
-0000170987 00000 n
-0000169026 00000 n
-0000171110 00000 n
-0000171235 00000 n
-0000171360 00000 n
-0000171485 00000 n
-0000171610 00000 n
-0000171735 00000 n
-0000388161 00000 n
-0000174071 00000 n
-0000173510 00000 n
-0000171924 00000 n
-0000173633 00000 n
-0000173758 00000 n
-0000173883 00000 n
-0000174008 00000 n
-0000176073 00000 n
-0000175637 00000 n
-0000174196 00000 n
-0000175760 00000 n
-0000175885 00000 n
-0000176010 00000 n
-0000178286 00000 n
-0000177850 00000 n
-0000176185 00000 n
-0000177973 00000 n
-0000178098 00000 n
-0000178223 00000 n
-0000180754 00000 n
-0000180318 00000 n
-0000178398 00000 n
-0000180441 00000 n
-0000180566 00000 n
-0000180691 00000 n
-0000184286 00000 n
-0000183851 00000 n
-0000180880 00000 n
-0000183974 00000 n
-0000184099 00000 n
-0000184223 00000 n
-0000187580 00000 n
-0000187144 00000 n
-0000184412 00000 n
-0000187267 00000 n
-0000187392 00000 n
-0000187517 00000 n
-0000388286 00000 n
-0000190463 00000 n
-0000189654 00000 n
-0000187719 00000 n
-0000189777 00000 n
-0000189902 00000 n
-0000190027 00000 n
-0000190152 00000 n
-0000190276 00000 n
-0000190401 00000 n
-0000193868 00000 n
-0000193183 00000 n
-0000190575 00000 n
-0000193306 00000 n
-0000193431 00000 n
-0000193555 00000 n
-0000193680 00000 n
-0000193805 00000 n
-0000196234 00000 n
-0000195801 00000 n
-0000193994 00000 n
-0000195924 00000 n
-0000196049 00000 n
-0000196173 00000 n
-0000198949 00000 n
-0000197764 00000 n
-0000196360 00000 n
-0000197887 00000 n
-0000198012 00000 n
-0000198137 00000 n
-0000198262 00000 n
-0000198387 00000 n
-0000198512 00000 n
-0000198636 00000 n
-0000198761 00000 n
-0000198886 00000 n
-0000201615 00000 n
-0000200433 00000 n
-0000199088 00000 n
-0000200556 00000 n
-0000200681 00000 n
-0000200806 00000 n
-0000200930 00000 n
-0000201055 00000 n
-0000201180 00000 n
-0000201303 00000 n
-0000201428 00000 n
-0000201553 00000 n
-0000203687 00000 n
-0000203001 00000 n
-0000201727 00000 n
-0000203124 00000 n
-0000203249 00000 n
-0000203374 00000 n
-0000203499 00000 n
-0000203624 00000 n
-0000388411 00000 n
-0000206559 00000 n
-0000205875 00000 n
-0000203799 00000 n
-0000205998 00000 n
-0000206123 00000 n
-0000206248 00000 n
-0000206372 00000 n
-0000206497 00000 n
-0000209818 00000 n
-0000208760 00000 n
-0000206685 00000 n
-0000208883 00000 n
-0000209008 00000 n
-0000209133 00000 n
-0000209258 00000 n
-0000209383 00000 n
-0000209506 00000 n
-0000209631 00000 n
-0000209756 00000 n
-0000212591 00000 n
-0000211657 00000 n
-0000209930 00000 n
-0000211780 00000 n
-0000211905 00000 n
-0000212030 00000 n
-0000212155 00000 n
-0000212280 00000 n
-0000212404 00000 n
-0000212529 00000 n
-0000214950 00000 n
-0000214139 00000 n
-0000212744 00000 n
-0000214262 00000 n
-0000214387 00000 n
-0000214512 00000 n
-0000214637 00000 n
-0000214762 00000 n
-0000214887 00000 n
-0000217497 00000 n
-0000216811 00000 n
-0000215076 00000 n
-0000216934 00000 n
-0000217059 00000 n
-0000217184 00000 n
-0000217309 00000 n
-0000217434 00000 n
-0000220512 00000 n
-0000219578 00000 n
-0000217609 00000 n
-0000219701 00000 n
-0000219826 00000 n
-0000219951 00000 n
-0000220076 00000 n
-0000220201 00000 n
-0000220326 00000 n
-0000220449 00000 n
-0000388536 00000 n
-0000222453 00000 n
-0000222018 00000 n
-0000220624 00000 n
-0000222141 00000 n
-0000222266 00000 n
-0000222391 00000 n
-0000225349 00000 n
-0000224665 00000 n
-0000222565 00000 n
-0000224788 00000 n
-0000224913 00000 n
-0000225038 00000 n
-0000225161 00000 n
-0000225286 00000 n
-0000227743 00000 n
-0000227059 00000 n
-0000225448 00000 n
-0000227182 00000 n
-0000227307 00000 n
-0000227432 00000 n
-0000227556 00000 n
-0000227680 00000 n
-0000231203 00000 n
-0000230517 00000 n
-0000227855 00000 n
-0000230640 00000 n
-0000230765 00000 n
-0000230890 00000 n
-0000231015 00000 n
-0000231140 00000 n
-0000234318 00000 n
-0000233756 00000 n
-0000231316 00000 n
-0000233879 00000 n
-0000233942 00000 n
-0000234005 00000 n
-0000234068 00000 n
-0000234131 00000 n
-0000234194 00000 n
-0000234257 00000 n
-0000237787 00000 n
-0000237226 00000 n
-0000234431 00000 n
-0000237349 00000 n
-0000237412 00000 n
-0000237475 00000 n
-0000237600 00000 n
-0000237724 00000 n
-0000388661 00000 n
-0000240835 00000 n
-0000240649 00000 n
-0000237913 00000 n
-0000240772 00000 n
-0000242762 00000 n
-0000242576 00000 n
-0000240948 00000 n
-0000242699 00000 n
-0000245474 00000 n
-0000245038 00000 n
-0000242875 00000 n
-0000245161 00000 n
-0000245286 00000 n
-0000245411 00000 n
-0000249619 00000 n
-0000249185 00000 n
-0000245573 00000 n
-0000249308 00000 n
-0000249433 00000 n
-0000249556 00000 n
-0000254131 00000 n
-0000253197 00000 n
-0000249718 00000 n
-0000253320 00000 n
-0000253445 00000 n
-0000253570 00000 n
-0000253694 00000 n
-0000253819 00000 n
-0000253944 00000 n
-0000254069 00000 n
-0000258045 00000 n
-0000257359 00000 n
-0000254244 00000 n
-0000257482 00000 n
-0000257607 00000 n
-0000257732 00000 n
-0000257857 00000 n
-0000257982 00000 n
-0000388786 00000 n
-0000260138 00000 n
-0000259827 00000 n
-0000258157 00000 n
-0000259950 00000 n
-0000260075 00000 n
-0000264081 00000 n
-0000263521 00000 n
-0000260264 00000 n
-0000263644 00000 n
-0000263769 00000 n
-0000263894 00000 n
-0000264018 00000 n
-0000268110 00000 n
-0000267736 00000 n
-0000264180 00000 n
-0000267859 00000 n
-0000267984 00000 n
-0000268047 00000 n
-0000269361 00000 n
-0000269175 00000 n
-0000268263 00000 n
-0000269298 00000 n
-0000272579 00000 n
-0000271769 00000 n
-0000269473 00000 n
-0000271892 00000 n
-0000272017 00000 n
-0000272142 00000 n
-0000272267 00000 n
-0000272392 00000 n
-0000272517 00000 n
-0000275575 00000 n
-0000275139 00000 n
-0000272678 00000 n
-0000275262 00000 n
-0000275387 00000 n
-0000275512 00000 n
-0000388911 00000 n
-0000278296 00000 n
-0000277735 00000 n
-0000275701 00000 n
-0000277858 00000 n
-0000277983 00000 n
-0000278108 00000 n
-0000278233 00000 n
-0000280080 00000 n
-0000279519 00000 n
-0000278409 00000 n
-0000279642 00000 n
-0000279767 00000 n
-0000279892 00000 n
-0000280017 00000 n
-0000280179 00000 n
-0000283261 00000 n
-0000283286 00000 n
-0000293287 00000 n
-0000295779 00000 n
-0000295810 00000 n
-0000299208 00000 n
-0000308973 00000 n
-0000309235 00000 n
-0000326633 00000 n
-0000345608 00000 n
-0000346035 00000 n
-0000363628 00000 n
-0000364009 00000 n
-0000368279 00000 n
-0000373105 00000 n
-0000387016 00000 n
-0000389009 00000 n
-0000389134 00000 n
-0000389260 00000 n
-0000389340 00000 n
-0000389422 00000 n
-0000409988 00000 n
-0000424113 00000 n
-0000424154 00000 n
-0000424194 00000 n
-0000424425 00000 n
+0000118862 00000 n
+0000119038 00000 n
+0000119916 00000 n
+0000120092 00000 n
+0000121186 00000 n
+0000121371 00000 n
+0000122257 00000 n
+0000122442 00000 n
+0000123219 00000 n
+0000123395 00000 n
+0000123996 00000 n
+0000124172 00000 n
+0000124834 00000 n
+0000125019 00000 n
+0000125996 00000 n
+0000126172 00000 n
+0000127179 00000 n
+0000127355 00000 n
+0000128349 00000 n
+0000128534 00000 n
+0000129366 00000 n
+0000129542 00000 n
+0000130275 00000 n
+0000130451 00000 n
+0000131133 00000 n
+0000131309 00000 n
+0000132138 00000 n
+0000132314 00000 n
+0000133302 00000 n
+0000133469 00000 n
+0000134905 00000 n
+0000135090 00000 n
+0000135823 00000 n
+0000136008 00000 n
+0000136635 00000 n
+0000136801 00000 n
+0000137199 00000 n
+0000137385 00000 n
+0000138913 00000 n
+0000139088 00000 n
+0000140802 00000 n
+0000140988 00000 n
+0000142570 00000 n
+0000142746 00000 n
+0000144513 00000 n
+0000144680 00000 n
+0000145058 00000 n
+0000145234 00000 n
+0000146531 00000 n
+0000146707 00000 n
+0000148414 00000 n
+0000148591 00000 n
+0000150343 00000 n
+0000150510 00000 n
+0000152404 00000 n
+0000152589 00000 n
+0000153859 00000 n
+0000154035 00000 n
+0000155763 00000 n
+0000155975 00000 n
+0000157598 00000 n
+0000157782 00000 n
+0000158672 00000 n
+0000158728 00000 n
+0000158827 00000 n
+0000158980 00000 n
+0000159059 00000 n
+0000159162 00000 n
+0000159360 00000 n
+0000159454 00000 n
+0000159571 00000 n
+0000159670 00000 n
+0000159830 00000 n
+0000159929 00000 n
+0000160053 00000 n
+0000160167 00000 n
+0000160281 00000 n
+0000160379 00000 n
+0000160543 00000 n
+0000160647 00000 n
+0000160766 00000 n
+0000160888 00000 n
+0000161010 00000 n
+0000161146 00000 n
+0000161246 00000 n
+0000161358 00000 n
+0000161468 00000 n
+0000161592 00000 n
+0000161749 00000 n
+0000161854 00000 n
+0000161971 00000 n
+0000162129 00000 n
+0000162233 00000 n
+0000162350 00000 n
+0000162472 00000 n
+0000162589 00000 n
+0000162706 00000 n
+0000162824 00000 n
+0000162942 00000 n
+0000163064 00000 n
+0000163186 00000 n
+0000163310 00000 n
+0000163434 00000 n
+0000163553 00000 n
+0000163672 00000 n
+0000163796 00000 n
+0000163907 00000 n
+0000164064 00000 n
+0000164163 00000 n
+0000164264 00000 n
+0000164371 00000 n
+0000164530 00000 n
+0000164669 00000 n
+0000164780 00000 n
+0000164911 00000 n
+0000165024 00000 n
+0000165153 00000 n
+0000165243 00000 n
+0000165408 00000 n
+0000165507 00000 n
+0000165616 00000 n
+0000165730 00000 n
+0000165839 00000 n
+0000165946 00000 n
+0000166056 00000 n
+0000166169 00000 n
+0000166281 00000 n
+0000166387 00000 n
+0000166519 00000 n
+0000166676 00000 n
+0000166811 00000 n
+0000166907 00000 n
+0000167003 00000 n
+0000167159 00000 n
+0000167253 00000 n
+0000167367 00000 n
+0000167466 00000 n
+0000167633 00000 n
+0000167733 00000 n
+0000167841 00000 n
+0000167947 00000 n
+0000168068 00000 n
+0000168195 00000 n
+0000168312 00000 n
+0000168435 00000 n
+0000168566 00000 n
+0000168683 00000 n
+0000168795 00000 n
+0000168913 00000 n
+0000169019 00000 n
+0000169187 00000 n
+0000169297 00000 n
+0000169417 00000 n
+0000169542 00000 n
+0000169657 00000 n
+0000169760 00000 n
+0000169922 00000 n
+0000170024 00000 n
+0000170122 00000 n
+0000170284 00000 n
+0000170387 00000 n
+0000170495 00000 n
+0000170677 00000 n
+0000170777 00000 n
+0000170887 00000 n
+0000170984 00000 n
+0000171120 00000 n
+0000171224 00000 n
+0000171328 00000 n
+0000171495 00000 n
+0000171591 00000 n
+0000171731 00000 n
+0000171849 00000 n
+0000171998 00000 n
+0000172121 00000 n
+0000172284 00000 n
+0000172372 00000 n
+0000172538 00000 n
+0000172651 00000 n
+0000172772 00000 n
+0000172905 00000 n
+0000173048 00000 n
+0000173149 00000 n
+0000173265 00000 n
+0000173366 00000 n
+0000173514 00000 n
+0000173630 00000 n
+0000173727 00000 n
+0000173845 00000 n
+0000173940 00000 n
+0000174103 00000 n
+0000174203 00000 n
+0000174321 00000 n
+0000174427 00000 n
trailer
-<<
-/Size 1806
-/Root 1804 0 R
-/Info 1805 0 R
->>
+<</Size 806/Root 805 0 R/Info 1 0 R/ID[<37e21dd5bf11a0bb7770129df9f0d2ea><37e21dd5bf11a0bb7770129df9f0d2ea>]>>
startxref
-424621
+174907
%%EOF
diff --git a/docs/Samba-HOWTO-Collection.pdf b/docs/Samba-HOWTO-Collection.pdf
index 9798599637..449b529f39 100644
--- a/docs/Samba-HOWTO-Collection.pdf
+++ b/docs/Samba-HOWTO-Collection.pdf
@@ -1,24496 +1,6694 @@
-%PDF-1.4
-5 0 obj
-<< /S /GoTo /D (part.1) >>
-endobj
-8 0 obj
-(I General Installation)
-endobj
-9 0 obj
-<< /S /GoTo /D (chapter.1) >>
-endobj
-12 0 obj
-(1 Introduction to Samba)
-endobj
-13 0 obj
-<< /S /GoTo /D (section.1.1) >>
-endobj
-16 0 obj
-(1.1 Background)
-endobj
-17 0 obj
-<< /S /GoTo /D (section.1.2) >>
-endobj
-20 0 obj
-(1.2 Terminology)
-endobj
-21 0 obj
-<< /S /GoTo /D (section.1.3) >>
-endobj
-24 0 obj
-(1.3 Related Projects)
-endobj
-25 0 obj
-<< /S /GoTo /D (section.1.4) >>
-endobj
-28 0 obj
-(1.4 SMB Methodology)
-endobj
-29 0 obj
-<< /S /GoTo /D (section.1.5) >>
-endobj
-32 0 obj
-(1.5 Additional Resources)
-endobj
-33 0 obj
-<< /S /GoTo /D (section.1.6) >>
-endobj
-36 0 obj
-(1.6 Epilogue)
-endobj
-37 0 obj
-<< /S /GoTo /D (section.1.7) >>
-endobj
-40 0 obj
-(1.7 Miscellaneous)
-endobj
-41 0 obj
-<< /S /GoTo /D (chapter.2) >>
-endobj
-44 0 obj
-(2 How to Install and Test SAMBA)
-endobj
-45 0 obj
-<< /S /GoTo /D (section.2.1) >>
-endobj
-48 0 obj
-(2.1 Obtaining and installing samba)
-endobj
-49 0 obj
-<< /S /GoTo /D (section.2.2) >>
-endobj
-52 0 obj
-(2.2 Configuring samba)
-endobj
-53 0 obj
-<< /S /GoTo /D (subsection.2.2.1) >>
-endobj
-56 0 obj
-(2.2.1 Editing the smb.conf file)
-endobj
-57 0 obj
-<< /S /GoTo /D (subsubsection.2.2.1.1) >>
-endobj
-60 0 obj
-(2.2.1.1 Test your config file with testparm)
-endobj
-61 0 obj
-<< /S /GoTo /D (subsection.2.2.2) >>
-endobj
-64 0 obj
-(2.2.2 SWAT)
-endobj
-65 0 obj
-<< /S /GoTo /D (section.2.3) >>
-endobj
-68 0 obj
-(2.3 Try listing the shares available on your server)
-endobj
-69 0 obj
-<< /S /GoTo /D (section.2.4) >>
-endobj
-72 0 obj
-(2.4 Try connecting with the unix client)
-endobj
-73 0 obj
-<< /S /GoTo /D (section.2.5) >>
-endobj
-76 0 obj
-(2.5 Try connecting from a DOS, WfWg, Win9x, WinNT, Win2k, OS/2, etc... client)
-endobj
-77 0 obj
-<< /S /GoTo /D (section.2.6) >>
-endobj
-80 0 obj
-(2.6 What If Things Don't Work?)
-endobj
-81 0 obj
-<< /S /GoTo /D (part.2) >>
-endobj
-84 0 obj
-(II Server Configuration Basics)
-endobj
-85 0 obj
-<< /S /GoTo /D (chapter.3) >>
-endobj
-88 0 obj
-(3 Nomenclature of Server Types)
-endobj
-89 0 obj
-<< /S /GoTo /D (section.3.1) >>
-endobj
-92 0 obj
-(3.1 Stand Alone Server)
-endobj
-93 0 obj
-<< /S /GoTo /D (section.3.2) >>
-endobj
-96 0 obj
-(3.2 Domain Member Server)
-endobj
-97 0 obj
-<< /S /GoTo /D (section.3.3) >>
-endobj
-100 0 obj
-(3.3 Domain Controller)
-endobj
-101 0 obj
-<< /S /GoTo /D (subsection.3.3.1) >>
-endobj
-104 0 obj
-(3.3.1 Domain Controller Types)
-endobj
-105 0 obj
-<< /S /GoTo /D (chapter.4) >>
-endobj
-108 0 obj
-(4 Samba as Stand-Alone Server)
-endobj
-109 0 obj
-<< /S /GoTo /D (section.4.1) >>
-endobj
-112 0 obj
-(4.1 User and Share security level)
-endobj
-113 0 obj
-<< /S /GoTo /D (subsection.4.1.1) >>
-endobj
-116 0 obj
-(4.1.1 User Level Security)
-endobj
-117 0 obj
-<< /S /GoTo /D (subsection.4.1.2) >>
-endobj
-120 0 obj
-(4.1.2 Share Level Security)
-endobj
-121 0 obj
-<< /S /GoTo /D (subsection.4.1.3) >>
-endobj
-124 0 obj
-(4.1.3 Server Level Security)
-endobj
-125 0 obj
-<< /S /GoTo /D (subsubsection.4.1.3.1) >>
-endobj
-128 0 obj
-(4.1.3.1 Configuring Samba for Seemless Windows Network Integration)
-endobj
-129 0 obj
-<< /S /GoTo /D (subsubsection.4.1.3.2) >>
-endobj
-132 0 obj
-(4.1.3.2 Use MS Windows NT as an authentication server)
-endobj
-133 0 obj
-<< /S /GoTo /D (subsection.4.1.4) >>
-endobj
-136 0 obj
-(4.1.4 Domain Level Security)
-endobj
-137 0 obj
-<< /S /GoTo /D (subsubsection.4.1.4.1) >>
-endobj
-140 0 obj
-(4.1.4.1 Samba as a member of an MS Windows NT security domain)
-endobj
-141 0 obj
-<< /S /GoTo /D (subsection.4.1.5) >>
-endobj
-144 0 obj
-(4.1.5 ADS Level Security)
-endobj
-145 0 obj
-<< /S /GoTo /D (chapter.5) >>
-endobj
-148 0 obj
-(5 Samba as an NT4 or Win2k Primary Domain Controller)
-endobj
-149 0 obj
-<< /S /GoTo /D (section.5.1) >>
-endobj
-152 0 obj
-(5.1 Prerequisite Reading)
-endobj
-153 0 obj
-<< /S /GoTo /D (section.5.2) >>
-endobj
-156 0 obj
-(5.2 Background)
-endobj
-157 0 obj
-<< /S /GoTo /D (section.5.3) >>
-endobj
-160 0 obj
-(5.3 Configuring the Samba Domain Controller)
-endobj
-161 0 obj
-<< /S /GoTo /D (section.5.4) >>
-endobj
-164 0 obj
-(5.4 Creating Machine Trust Accounts and Joining Clients to the Domain)
-endobj
-165 0 obj
-<< /S /GoTo /D (subsection.5.4.1) >>
-endobj
-168 0 obj
-(5.4.1 Manual Creation of Machine Trust Accounts)
-endobj
-169 0 obj
-<< /S /GoTo /D (subsection.5.4.2) >>
-endobj
-172 0 obj
-(5.4.2 "On-the-Fly" Creation of Machine Trust Accounts)
-endobj
-173 0 obj
-<< /S /GoTo /D (subsection.5.4.3) >>
-endobj
-176 0 obj
-(5.4.3 Joining the Client to the Domain)
-endobj
-177 0 obj
-<< /S /GoTo /D (section.5.5) >>
-endobj
-180 0 obj
-(5.5 Common Problems and Errors)
-endobj
-181 0 obj
-<< /S /GoTo /D (subsection.5.5.1) >>
-endobj
-184 0 obj
-(5.5.1 I cannot include a '\044' in a machine name)
-endobj
-185 0 obj
-<< /S /GoTo /D (subsection.5.5.2) >>
-endobj
-188 0 obj
-(5.5.2 I get told "You already have a connection to the Domain...." or "Cannot join domain, the credentials supplied conflict with an existing set.." when creating a machine trust account.)
-endobj
-189 0 obj
-<< /S /GoTo /D (subsection.5.5.3) >>
-endobj
-192 0 obj
-(5.5.3 The system can not log you on \(C000019B\)....)
-endobj
-193 0 obj
-<< /S /GoTo /D (subsection.5.5.4) >>
-endobj
-196 0 obj
-(5.5.4 The machine trust account for this computer either does not exist or is not accessible.)
-endobj
-197 0 obj
-<< /S /GoTo /D (subsection.5.5.5) >>
-endobj
-200 0 obj
-(5.5.5 When I attempt to login to a Samba Domain from a NT4/W2K workstation, I get a message about my account being disabled.)
-endobj
-201 0 obj
-<< /S /GoTo /D (section.5.6) >>
-endobj
-204 0 obj
-(5.6 Domain Control for Windows 9x/ME)
-endobj
-205 0 obj
-<< /S /GoTo /D (subsection.5.6.1) >>
-endobj
-208 0 obj
-(5.6.1 Configuration Instructions: Network Logons)
-endobj
-209 0 obj
-<< /S /GoTo /D (chapter.6) >>
-endobj
-212 0 obj
-(6 Samba Backup Domain Controller to Samba Domain Control)
-endobj
-213 0 obj
-<< /S /GoTo /D (section.6.1) >>
-endobj
-216 0 obj
-(6.1 Prerequisite Reading)
-endobj
-217 0 obj
-<< /S /GoTo /D (section.6.2) >>
-endobj
-220 0 obj
-(6.2 Background)
-endobj
-221 0 obj
-<< /S /GoTo /D (section.6.3) >>
-endobj
-224 0 obj
-(6.3 What qualifies a Domain Controller on the network?)
-endobj
-225 0 obj
-<< /S /GoTo /D (subsection.6.3.1) >>
-endobj
-228 0 obj
-(6.3.1 How does a Workstation find its domain controller?)
-endobj
-229 0 obj
-<< /S /GoTo /D (subsection.6.3.2) >>
-endobj
-232 0 obj
-(6.3.2 When is the PDC needed?)
-endobj
-233 0 obj
-<< /S /GoTo /D (section.6.4) >>
-endobj
-236 0 obj
-(6.4 Can Samba be a Backup Domain Controller to an NT PDC?)
-endobj
-237 0 obj
-<< /S /GoTo /D (section.6.5) >>
-endobj
-240 0 obj
-(6.5 How do I set up a Samba BDC?)
-endobj
-241 0 obj
-<< /S /GoTo /D (subsection.6.5.1) >>
-endobj
-244 0 obj
-(6.5.1 How do I replicate the smbpasswd file?)
-endobj
-245 0 obj
-<< /S /GoTo /D (subsection.6.5.2) >>
-endobj
-248 0 obj
-(6.5.2 Can I do this all with LDAP?)
-endobj
-249 0 obj
-<< /S /GoTo /D (chapter.7) >>
-endobj
-252 0 obj
-(7 Samba as a ADS domain member)
-endobj
-253 0 obj
-<< /S /GoTo /D (section.7.1) >>
-endobj
-256 0 obj
-(7.1 Setup your smb.conf)
-endobj
-257 0 obj
-<< /S /GoTo /D (section.7.2) >>
-endobj
-260 0 obj
-(7.2 Setup your /etc/krb5.conf)
-endobj
-261 0 obj
-<< /S /GoTo /D (section.7.3) >>
-endobj
-264 0 obj
-(7.3 Create the computer account)
-endobj
-265 0 obj
-<< /S /GoTo /D (subsection.7.3.1) >>
-endobj
-268 0 obj
-(7.3.1 Possible errors)
-endobj
-269 0 obj
-<< /S /GoTo /D (section.7.4) >>
-endobj
-272 0 obj
-(7.4 Test your server setup)
-endobj
-273 0 obj
-<< /S /GoTo /D (section.7.5) >>
-endobj
-276 0 obj
-(7.5 Testing with smbclient)
-endobj
-277 0 obj
-<< /S /GoTo /D (section.7.6) >>
-endobj
-280 0 obj
-(7.6 Notes)
-endobj
-281 0 obj
-<< /S /GoTo /D (chapter.8) >>
-endobj
-284 0 obj
-(8 Samba as a NT4 or Win2k domain member)
-endobj
-285 0 obj
-<< /S /GoTo /D (section.8.1) >>
-endobj
-288 0 obj
-(8.1 Joining an NT Domain with Samba 3.0)
-endobj
-289 0 obj
-<< /S /GoTo /D (section.8.2) >>
-endobj
-292 0 obj
-(8.2 Why is this better than security = server?)
-endobj
-293 0 obj
-<< /S /GoTo /D (part.3) >>
-endobj
-296 0 obj
-(III Advanced Configuration)
-endobj
-297 0 obj
-<< /S /GoTo /D (chapter.9) >>
-endobj
-300 0 obj
-(9 Samba / MS Windows Network Browsing Guide)
-endobj
-301 0 obj
-<< /S /GoTo /D (section.9.1) >>
-endobj
-304 0 obj
-(9.1 What is Browsing?)
-endobj
-305 0 obj
-<< /S /GoTo /D (section.9.2) >>
-endobj
-308 0 obj
-(9.2 Discussion)
-endobj
-309 0 obj
-<< /S /GoTo /D (section.9.3) >>
-endobj
-312 0 obj
-(9.3 How Browsing Functions)
-endobj
-313 0 obj
-<< /S /GoTo /D (subsection.9.3.1) >>
-endobj
-316 0 obj
-(9.3.1 Setting up WORKGROUP Browsing)
-endobj
-317 0 obj
-<< /S /GoTo /D (subsection.9.3.2) >>
-endobj
-320 0 obj
-(9.3.2 Setting up DOMAIN Browsing)
-endobj
-321 0 obj
-<< /S /GoTo /D (subsection.9.3.3) >>
-endobj
-324 0 obj
-(9.3.3 Forcing samba to be the master)
-endobj
-325 0 obj
-<< /S /GoTo /D (subsection.9.3.4) >>
-endobj
-328 0 obj
-(9.3.4 Making samba the domain master)
-endobj
-329 0 obj
-<< /S /GoTo /D (subsection.9.3.5) >>
-endobj
-332 0 obj
-(9.3.5 Note about broadcast addresses)
-endobj
-333 0 obj
-<< /S /GoTo /D (subsection.9.3.6) >>
-endobj
-336 0 obj
-(9.3.6 Multiple interfaces)
-endobj
-337 0 obj
-<< /S /GoTo /D (subsection.9.3.7) >>
-endobj
-340 0 obj
-(9.3.7 Use of the Remote Announce parameter)
-endobj
-341 0 obj
-<< /S /GoTo /D (subsection.9.3.8) >>
-endobj
-344 0 obj
-(9.3.8 Use of the Remote Browse Sync parameter)
-endobj
-345 0 obj
-<< /S /GoTo /D (section.9.4) >>
-endobj
-348 0 obj
-(9.4 WINS - The Windows Internetworking Name Server)
-endobj
-349 0 obj
-<< /S /GoTo /D (subsection.9.4.1) >>
-endobj
-352 0 obj
-(9.4.1 Setting up a WINS server)
-endobj
-353 0 obj
-<< /S /GoTo /D (subsection.9.4.2) >>
-endobj
-356 0 obj
-(9.4.2 WINS Replication)
-endobj
-357 0 obj
-<< /S /GoTo /D (subsection.9.4.3) >>
-endobj
-360 0 obj
-(9.4.3 Static WINS Entries)
-endobj
-361 0 obj
-<< /S /GoTo /D (section.9.5) >>
-endobj
-364 0 obj
-(9.5 Helpful Hints)
-endobj
-365 0 obj
-<< /S /GoTo /D (subsection.9.5.1) >>
-endobj
-368 0 obj
-(9.5.1 Windows Networking Protocols)
-endobj
-369 0 obj
-<< /S /GoTo /D (subsection.9.5.2) >>
-endobj
-372 0 obj
-(9.5.2 Name Resolution Order)
-endobj
-373 0 obj
-<< /S /GoTo /D (section.9.6) >>
-endobj
-376 0 obj
-(9.6 Technical Overview of browsing)
-endobj
-377 0 obj
-<< /S /GoTo /D (subsection.9.6.1) >>
-endobj
-380 0 obj
-(9.6.1 Browsing support in samba)
-endobj
-381 0 obj
-<< /S /GoTo /D (subsection.9.6.2) >>
-endobj
-384 0 obj
-(9.6.2 Problem resolution)
-endobj
-385 0 obj
-<< /S /GoTo /D (subsection.9.6.3) >>
-endobj
-388 0 obj
-(9.6.3 Browsing across subnets)
-endobj
-389 0 obj
-<< /S /GoTo /D (subsubsection.9.6.3.1) >>
-endobj
-392 0 obj
-(9.6.3.1 How does cross subnet browsing work ?)
-endobj
-393 0 obj
-<< /S /GoTo /D (chapter.10) >>
-endobj
-396 0 obj
-(10 User information database)
-endobj
-397 0 obj
-<< /S /GoTo /D (section.10.1) >>
-endobj
-400 0 obj
-(10.1 Introduction)
-endobj
-401 0 obj
-<< /S /GoTo /D (section.10.2) >>
-endobj
-404 0 obj
-(10.2 Important Notes About Security)
-endobj
-405 0 obj
-<< /S /GoTo /D (subsection.10.2.1) >>
-endobj
-408 0 obj
-(10.2.1 Advantages of SMB Encryption)
-endobj
-409 0 obj
-<< /S /GoTo /D (subsection.10.2.2) >>
-endobj
-412 0 obj
-(10.2.2 Advantages of non-encrypted passwords)
-endobj
-413 0 obj
-<< /S /GoTo /D (section.10.3) >>
-endobj
-416 0 obj
-(10.3 The smbpasswd Command)
-endobj
-417 0 obj
-<< /S /GoTo /D (section.10.4) >>
-endobj
-420 0 obj
-(10.4 Plain text)
-endobj
-421 0 obj
-<< /S /GoTo /D (section.10.5) >>
-endobj
-424 0 obj
-(10.5 TDB)
-endobj
-425 0 obj
-<< /S /GoTo /D (section.10.6) >>
-endobj
-428 0 obj
-(10.6 LDAP)
-endobj
-429 0 obj
-<< /S /GoTo /D (subsection.10.6.1) >>
-endobj
-432 0 obj
-(10.6.1 Introduction)
-endobj
-433 0 obj
-<< /S /GoTo /D (subsection.10.6.2) >>
-endobj
-436 0 obj
-(10.6.2 Encrypted Password Database)
-endobj
-437 0 obj
-<< /S /GoTo /D (subsection.10.6.3) >>
-endobj
-440 0 obj
-(10.6.3 Supported LDAP Servers)
-endobj
-441 0 obj
-<< /S /GoTo /D (subsection.10.6.4) >>
-endobj
-444 0 obj
-(10.6.4 Schema and Relationship to the RFC 2307 posixAccount)
-endobj
-445 0 obj
-<< /S /GoTo /D (subsection.10.6.5) >>
-endobj
-448 0 obj
-(10.6.5 Configuring Samba with LDAP)
-endobj
-449 0 obj
-<< /S /GoTo /D (subsubsection.10.6.5.1) >>
-endobj
-452 0 obj
-(10.6.5.1 OpenLDAP configuration)
-endobj
-453 0 obj
-<< /S /GoTo /D (subsubsection.10.6.5.2) >>
-endobj
-456 0 obj
-(10.6.5.2 Configuring Samba)
-endobj
-457 0 obj
-<< /S /GoTo /D (subsection.10.6.6) >>
-endobj
-460 0 obj
-(10.6.6 Accounts and Groups management)
-endobj
-461 0 obj
-<< /S /GoTo /D (subsection.10.6.7) >>
-endobj
-464 0 obj
-(10.6.7 Security and sambaAccount)
-endobj
-465 0 obj
-<< /S /GoTo /D (subsection.10.6.8) >>
-endobj
-468 0 obj
-(10.6.8 LDAP specials attributes for sambaAccounts)
-endobj
-469 0 obj
-<< /S /GoTo /D (subsection.10.6.9) >>
-endobj
-472 0 obj
-(10.6.9 Example LDIF Entries for a sambaAccount)
-endobj
-473 0 obj
-<< /S /GoTo /D (section.10.7) >>
-endobj
-476 0 obj
-(10.7 MySQL)
-endobj
-477 0 obj
-<< /S /GoTo /D (subsection.10.7.1) >>
-endobj
-480 0 obj
-(10.7.1 Creating the database)
-endobj
-481 0 obj
-<< /S /GoTo /D (subsection.10.7.2) >>
-endobj
-484 0 obj
-(10.7.2 Configuring)
-endobj
-485 0 obj
-<< /S /GoTo /D (subsection.10.7.3) >>
-endobj
-488 0 obj
-(10.7.3 Using plaintext passwords or encrypted password)
-endobj
-489 0 obj
-<< /S /GoTo /D (subsection.10.7.4) >>
-endobj
-492 0 obj
-(10.7.4 Getting non-column data from the table)
-endobj
-493 0 obj
-<< /S /GoTo /D (section.10.8) >>
-endobj
-496 0 obj
-(10.8 XML)
-endobj
-497 0 obj
-<< /S /GoTo /D (chapter.11) >>
-endobj
-500 0 obj
-(11 UNIX Permission Bits and Windows NT Access Control Lists)
-endobj
-501 0 obj
-<< /S /GoTo /D (section.11.1) >>
-endobj
-504 0 obj
-(11.1 Viewing and changing UNIX permissions using the NT security dialogs)
-endobj
-505 0 obj
-<< /S /GoTo /D (section.11.2) >>
-endobj
-508 0 obj
-(11.2 How to view file security on a Samba share)
-endobj
-509 0 obj
-<< /S /GoTo /D (section.11.3) >>
-endobj
-512 0 obj
-(11.3 Viewing file ownership)
-endobj
-513 0 obj
-<< /S /GoTo /D (section.11.4) >>
-endobj
-516 0 obj
-(11.4 Viewing file or directory permissions)
-endobj
-517 0 obj
-<< /S /GoTo /D (subsection.11.4.1) >>
-endobj
-520 0 obj
-(11.4.1 File Permissions)
-endobj
-521 0 obj
-<< /S /GoTo /D (subsection.11.4.2) >>
-endobj
-524 0 obj
-(11.4.2 Directory Permissions)
-endobj
-525 0 obj
-<< /S /GoTo /D (section.11.5) >>
-endobj
-528 0 obj
-(11.5 Modifying file or directory permissions)
-endobj
-529 0 obj
-<< /S /GoTo /D (section.11.6) >>
-endobj
-532 0 obj
-(11.6 Interaction with the standard Samba create mask parameters)
-endobj
-533 0 obj
-<< /S /GoTo /D (section.11.7) >>
-endobj
-536 0 obj
-(11.7 Interaction with the standard Samba file attribute mapping)
-endobj
-537 0 obj
-<< /S /GoTo /D (chapter.12) >>
-endobj
-540 0 obj
-(12 Configuring Group Mapping)
-endobj
-541 0 obj
-<< /S /GoTo /D (chapter.13) >>
-endobj
-544 0 obj
-(13 Printing Support)
-endobj
-545 0 obj
-<< /S /GoTo /D (section.13.1) >>
-endobj
-548 0 obj
-(13.1 Introduction)
-endobj
-549 0 obj
-<< /S /GoTo /D (section.13.2) >>
-endobj
-552 0 obj
-(13.2 Configuration)
-endobj
-553 0 obj
-<< /S /GoTo /D (subsection.13.2.1) >>
-endobj
-556 0 obj
-(13.2.1 Creating [print\044])
-endobj
-557 0 obj
-<< /S /GoTo /D (subsection.13.2.2) >>
-endobj
-560 0 obj
-(13.2.2 Setting Drivers for Existing Printers)
-endobj
-561 0 obj
-<< /S /GoTo /D (subsection.13.2.3) >>
-endobj
-564 0 obj
-(13.2.3 Support a large number of printers)
-endobj
-565 0 obj
-<< /S /GoTo /D (subsection.13.2.4) >>
-endobj
-568 0 obj
-(13.2.4 Adding New Printers via the Windows NT APW)
-endobj
-569 0 obj
-<< /S /GoTo /D (subsection.13.2.5) >>
-endobj
-572 0 obj
-(13.2.5 Samba and Printer Ports)
-endobj
-573 0 obj
-<< /S /GoTo /D (section.13.3) >>
-endobj
-576 0 obj
-(13.3 The Imprints Toolset)
-endobj
-577 0 obj
-<< /S /GoTo /D (subsection.13.3.1) >>
-endobj
-580 0 obj
-(13.3.1 What is Imprints?)
-endobj
-581 0 obj
-<< /S /GoTo /D (subsection.13.3.2) >>
-endobj
-584 0 obj
-(13.3.2 Creating Printer Driver Packages)
-endobj
-585 0 obj
-<< /S /GoTo /D (subsection.13.3.3) >>
-endobj
-588 0 obj
-(13.3.3 The Imprints server)
-endobj
-589 0 obj
-<< /S /GoTo /D (subsection.13.3.4) >>
-endobj
-592 0 obj
-(13.3.4 The Installation Client)
-endobj
-593 0 obj
-<< /S /GoTo /D (section.13.4) >>
-endobj
-596 0 obj
-(13.4 Diagnosis)
-endobj
-597 0 obj
-<< /S /GoTo /D (subsection.13.4.1) >>
-endobj
-600 0 obj
-(13.4.1 Introduction)
-endobj
-601 0 obj
-<< /S /GoTo /D (subsection.13.4.2) >>
-endobj
-604 0 obj
-(13.4.2 Debugging printer problems)
-endobj
-605 0 obj
-<< /S /GoTo /D (subsection.13.4.3) >>
-endobj
-608 0 obj
-(13.4.3 What printers do I have?)
-endobj
-609 0 obj
-<< /S /GoTo /D (subsection.13.4.4) >>
-endobj
-612 0 obj
-(13.4.4 Setting up printcap and print servers)
-endobj
-613 0 obj
-<< /S /GoTo /D (subsection.13.4.5) >>
-endobj
-616 0 obj
-(13.4.5 Job sent, no output)
-endobj
-617 0 obj
-<< /S /GoTo /D (subsection.13.4.6) >>
-endobj
-620 0 obj
-(13.4.6 Job sent, strange output)
-endobj
-621 0 obj
-<< /S /GoTo /D (subsection.13.4.7) >>
-endobj
-624 0 obj
-(13.4.7 Raw PostScript printed)
-endobj
-625 0 obj
-<< /S /GoTo /D (subsection.13.4.8) >>
-endobj
-628 0 obj
-(13.4.8 Advanced Printing)
-endobj
-629 0 obj
-<< /S /GoTo /D (subsection.13.4.9) >>
-endobj
-632 0 obj
-(13.4.9 Real debugging)
-endobj
-633 0 obj
-<< /S /GoTo /D (chapter.14) >>
-endobj
-636 0 obj
-(14 CUPS Printing Support)
-endobj
-637 0 obj
-<< /S /GoTo /D (section.14.1) >>
-endobj
-640 0 obj
-(14.1 Introduction)
-endobj
-641 0 obj
-<< /S /GoTo /D (section.14.2) >>
-endobj
-644 0 obj
-(14.2 Configuring smb.conf for CUPS)
-endobj
-645 0 obj
-<< /S /GoTo /D (section.14.3) >>
-endobj
-648 0 obj
-(14.3 CUPS - RAW Print Through Mode)
-endobj
-649 0 obj
-<< /S /GoTo /D (section.14.4) >>
-endobj
-652 0 obj
-(14.4 CUPS as a network PostScript RIP)
-endobj
-653 0 obj
-<< /S /GoTo /D (section.14.5) >>
-endobj
-656 0 obj
-(14.5 Windows Terminal Servers \(WTS\) as CUPS clients)
-endobj
-657 0 obj
-<< /S /GoTo /D (section.14.6) >>
-endobj
-660 0 obj
-(14.6 Setting up CUPS for driver download)
-endobj
-661 0 obj
-<< /S /GoTo /D (section.14.7) >>
-endobj
-664 0 obj
-(14.7 Sources of CUPS drivers / PPDs)
-endobj
-665 0 obj
-<< /S /GoTo /D (subsection.14.7.1) >>
-endobj
-668 0 obj
-(14.7.1 cupsaddsmb)
-endobj
-669 0 obj
-<< /S /GoTo /D (section.14.8) >>
-endobj
-672 0 obj
-(14.8 The CUPS Filter Chains)
-endobj
-673 0 obj
-<< /S /GoTo /D (section.14.9) >>
-endobj
-676 0 obj
-(14.9 CUPS Print Drivers and Devices)
-endobj
-677 0 obj
-<< /S /GoTo /D (subsection.14.9.1) >>
-endobj
-680 0 obj
-(14.9.1 Further printing steps)
-endobj
-681 0 obj
-<< /S /GoTo /D (section.14.10) >>
-endobj
-684 0 obj
-(14.10 Limiting the number of pages users can print)
-endobj
-685 0 obj
-<< /S /GoTo /D (section.14.11) >>
-endobj
-688 0 obj
-(14.11 Advanced Postscript Printing from MS Windows)
-endobj
-689 0 obj
-<< /S /GoTo /D (section.14.12) >>
-endobj
-692 0 obj
-(14.12 Auto-Deletion of CUPS spool files)
-endobj
-693 0 obj
-<< /S /GoTo /D (chapter.15) >>
-endobj
-696 0 obj
-(15 Unified Logons between Windows NT and UNIX using Winbind)
-endobj
-697 0 obj
-<< /S /GoTo /D (section.15.1) >>
-endobj
-700 0 obj
-(15.1 Abstract)
-endobj
-701 0 obj
-<< /S /GoTo /D (section.15.2) >>
-endobj
-704 0 obj
-(15.2 Introduction)
-endobj
-705 0 obj
-<< /S /GoTo /D (section.15.3) >>
-endobj
-708 0 obj
-(15.3 What Winbind Provides)
-endobj
-709 0 obj
-<< /S /GoTo /D (subsection.15.3.1) >>
-endobj
-712 0 obj
-(15.3.1 Target Uses)
-endobj
-713 0 obj
-<< /S /GoTo /D (section.15.4) >>
-endobj
-716 0 obj
-(15.4 How Winbind Works)
-endobj
-717 0 obj
-<< /S /GoTo /D (subsection.15.4.1) >>
-endobj
-720 0 obj
-(15.4.1 Microsoft Remote Procedure Calls)
-endobj
-721 0 obj
-<< /S /GoTo /D (subsection.15.4.2) >>
-endobj
-724 0 obj
-(15.4.2 Microsoft Active Directory Services)
-endobj
-725 0 obj
-<< /S /GoTo /D (subsection.15.4.3) >>
-endobj
-728 0 obj
-(15.4.3 Name Service Switch)
-endobj
-729 0 obj
-<< /S /GoTo /D (subsection.15.4.4) >>
-endobj
-732 0 obj
-(15.4.4 Pluggable Authentication Modules)
-endobj
-733 0 obj
-<< /S /GoTo /D (subsection.15.4.5) >>
-endobj
-736 0 obj
-(15.4.5 User and Group ID Allocation)
-endobj
-737 0 obj
-<< /S /GoTo /D (subsection.15.4.6) >>
-endobj
-740 0 obj
-(15.4.6 Result Caching)
-endobj
-741 0 obj
-<< /S /GoTo /D (section.15.5) >>
-endobj
-744 0 obj
-(15.5 Installation and Configuration)
-endobj
-745 0 obj
-<< /S /GoTo /D (subsection.15.5.1) >>
-endobj
-748 0 obj
-(15.5.1 Introduction)
-endobj
-749 0 obj
-<< /S /GoTo /D (subsection.15.5.2) >>
-endobj
-752 0 obj
-(15.5.2 Requirements)
-endobj
-753 0 obj
-<< /S /GoTo /D (subsection.15.5.3) >>
-endobj
-756 0 obj
-(15.5.3 Testing Things Out)
-endobj
-757 0 obj
-<< /S /GoTo /D (subsubsection.15.5.3.1) >>
-endobj
-760 0 obj
-(15.5.3.1 Configure and compile SAMBA)
-endobj
-761 0 obj
-<< /S /GoTo /D (subsubsection.15.5.3.2) >>
-endobj
-764 0 obj
-(15.5.3.2 Configure nsswitch.conf and the winbind libraries on Linux and Solaris)
-endobj
-765 0 obj
-<< /S /GoTo /D (subsubsection.15.5.3.3) >>
-endobj
-768 0 obj
-(15.5.3.3 NSS Winbind on AIX)
-endobj
-769 0 obj
-<< /S /GoTo /D (subsubsection.15.5.3.4) >>
-endobj
-772 0 obj
-(15.5.3.4 Configure smb.conf)
-endobj
-773 0 obj
-<< /S /GoTo /D (subsubsection.15.5.3.5) >>
-endobj
-776 0 obj
-(15.5.3.5 Join the SAMBA server to the PDC domain)
-endobj
-777 0 obj
-<< /S /GoTo /D (subsubsection.15.5.3.6) >>
-endobj
-780 0 obj
-(15.5.3.6 Start up the winbindd daemon and test it!)
-endobj
-781 0 obj
-<< /S /GoTo /D (subsubsection.15.5.3.7) >>
-endobj
-784 0 obj
-(15.5.3.7 Fix the init.d startup scripts)
-endobj
-785 0 obj
-<< /S /GoTo /D (subsubsection.15.5.3.8) >>
-endobj
-788 0 obj
-(15.5.3.8 Configure Winbind and PAM)
-endobj
-789 0 obj
-<< /S /GoTo /D (section.15.6) >>
-endobj
-792 0 obj
-(15.6 Limitations)
-endobj
-793 0 obj
-<< /S /GoTo /D (section.15.7) >>
-endobj
-796 0 obj
-(15.7 Conclusion)
-endobj
-797 0 obj
-<< /S /GoTo /D (chapter.16) >>
-endobj
-800 0 obj
-(16 Advanced Network Manangement)
-endobj
-801 0 obj
-<< /S /GoTo /D (section.16.1) >>
-endobj
-804 0 obj
-(16.1 Configuring Samba Share Access Controls)
-endobj
-805 0 obj
-<< /S /GoTo /D (subsection.16.1.1) >>
-endobj
-808 0 obj
-(16.1.1 Share Permissions Management)
-endobj
-809 0 obj
-<< /S /GoTo /D (subsubsection.16.1.1.1) >>
-endobj
-812 0 obj
-(16.1.1.1 Windows NT4 Workstation/Server)
-endobj
-813 0 obj
-<< /S /GoTo /D (subsubsection.16.1.1.2) >>
-endobj
-816 0 obj
-(16.1.1.2 Windows 200x/XP)
-endobj
-817 0 obj
-<< /S /GoTo /D (section.16.2) >>
-endobj
-820 0 obj
-(16.2 Remote Server Administration)
-endobj
-821 0 obj
-<< /S /GoTo /D (section.16.3) >>
-endobj
-824 0 obj
-(16.3 Network Logon Script Magic)
-endobj
-825 0 obj
-<< /S /GoTo /D (subsection.16.3.1) >>
-endobj
-828 0 obj
-(16.3.1 Adding printers without user intervention)
-endobj
-829 0 obj
-<< /S /GoTo /D (chapter.17) >>
-endobj
-832 0 obj
-(17 System and Account Policies)
-endobj
-833 0 obj
-<< /S /GoTo /D (section.17.1) >>
-endobj
-836 0 obj
-(17.1 Creating and Managing System Policies)
-endobj
-837 0 obj
-<< /S /GoTo /D (subsection.17.1.1) >>
-endobj
-840 0 obj
-(17.1.1 Windows 9x/Me Policies)
-endobj
-841 0 obj
-<< /S /GoTo /D (subsection.17.1.2) >>
-endobj
-844 0 obj
-(17.1.2 Windows NT4 Style Policy Files)
-endobj
-845 0 obj
-<< /S /GoTo /D (subsubsection.17.1.2.1) >>
-endobj
-848 0 obj
-(17.1.2.1 Registry Tattoos)
-endobj
-849 0 obj
-<< /S /GoTo /D (subsection.17.1.3) >>
-endobj
-852 0 obj
-(17.1.3 MS Windows 200x / XP Professional Policies)
-endobj
-853 0 obj
-<< /S /GoTo /D (subsubsection.17.1.3.1) >>
-endobj
-856 0 obj
-(17.1.3.1 Administration of Win2K / XP PoliciesInstructions)
-endobj
-857 0 obj
-<< /S /GoTo /D (section.17.2) >>
-endobj
-860 0 obj
-(17.2 Managing Account/User Policies)
-endobj
-861 0 obj
-<< /S /GoTo /D (subsection.17.2.1) >>
-endobj
-864 0 obj
-(17.2.1 With Windows NT4/200x)
-endobj
-865 0 obj
-<< /S /GoTo /D (subsection.17.2.2) >>
-endobj
-868 0 obj
-(17.2.2 With a Samba PDC)
-endobj
-869 0 obj
-<< /S /GoTo /D (section.17.3) >>
-endobj
-872 0 obj
-(17.3 System Startup and Logon Processing Overview)
-endobj
-873 0 obj
-<< /S /GoTo /D (chapter.18) >>
-endobj
-876 0 obj
-(18 Desktop Profile Management)
-endobj
-877 0 obj
-<< /S /GoTo /D (section.18.1) >>
-endobj
-880 0 obj
-(18.1 Roaming Profiles)
-endobj
-881 0 obj
-<< /S /GoTo /D (subsection.18.1.1) >>
-endobj
-884 0 obj
-(18.1.1 Samba Configuration for Profile Handling)
-endobj
-885 0 obj
-<< /S /GoTo /D (subsubsection.18.1.1.1) >>
-endobj
-888 0 obj
-(18.1.1.1 NT4/200x User Profiles)
-endobj
-889 0 obj
-<< /S /GoTo /D (subsubsection.18.1.1.2) >>
-endobj
-892 0 obj
-(18.1.1.2 Windows 9x / Me User Profiles)
-endobj
-893 0 obj
-<< /S /GoTo /D (subsubsection.18.1.1.3) >>
-endobj
-896 0 obj
-(18.1.1.3 Mixed Windows 9x / Me and Windows NT4/200x User Profiles)
-endobj
-897 0 obj
-<< /S /GoTo /D (subsubsection.18.1.1.4) >>
-endobj
-900 0 obj
-(18.1.1.4 Disabling Roaming Profile Support)
-endobj
-901 0 obj
-<< /S /GoTo /D (subsection.18.1.2) >>
-endobj
-904 0 obj
-(18.1.2 Windows Client Profile Configuration Information)
-endobj
-905 0 obj
-<< /S /GoTo /D (subsubsection.18.1.2.1) >>
-endobj
-908 0 obj
-(18.1.2.1 Windows 9x / Me Profile Setup)
-endobj
-909 0 obj
-<< /S /GoTo /D (subsubsection.18.1.2.2) >>
-endobj
-912 0 obj
-(18.1.2.2 Windows NT4 Workstation)
-endobj
-913 0 obj
-<< /S /GoTo /D (subsubsection.18.1.2.3) >>
-endobj
-916 0 obj
-(18.1.2.3 Windows 2000/XP Professional)
-endobj
-917 0 obj
-<< /S /GoTo /D (subsection.18.1.3) >>
-endobj
-920 0 obj
-(18.1.3 Sharing Profiles between W9x/Me and NT4/200x/XP workstations)
-endobj
-921 0 obj
-<< /S /GoTo /D (subsection.18.1.4) >>
-endobj
-924 0 obj
-(18.1.4 Profile Migration from Windows NT4/200x Server to Samba)
-endobj
-925 0 obj
-<< /S /GoTo /D (subsubsection.18.1.4.1) >>
-endobj
-928 0 obj
-(18.1.4.1 Windows NT4 Profile Management Tools)
-endobj
-929 0 obj
-<< /S /GoTo /D (subsubsection.18.1.4.2) >>
-endobj
-932 0 obj
-(18.1.4.2 Side bar Notes)
-endobj
-933 0 obj
-<< /S /GoTo /D (subsubsection.18.1.4.3) >>
-endobj
-936 0 obj
-(18.1.4.3 moveuser.exe)
-endobj
-937 0 obj
-<< /S /GoTo /D (subsubsection.18.1.4.4) >>
-endobj
-940 0 obj
-(18.1.4.4 Get SID)
-endobj
-941 0 obj
-<< /S /GoTo /D (section.18.2) >>
-endobj
-944 0 obj
-(18.2 Mandatory profiles)
-endobj
-945 0 obj
-<< /S /GoTo /D (section.18.3) >>
-endobj
-948 0 obj
-(18.3 Creating/Managing Group Profiles)
-endobj
-949 0 obj
-<< /S /GoTo /D (section.18.4) >>
-endobj
-952 0 obj
-(18.4 Default Profile for Windows Users)
-endobj
-953 0 obj
-<< /S /GoTo /D (subsection.18.4.1) >>
-endobj
-956 0 obj
-(18.4.1 MS Windows 9x/Me)
-endobj
-957 0 obj
-<< /S /GoTo /D (subsubsection.18.4.1.1) >>
-endobj
-960 0 obj
-(18.4.1.1 How User Profiles Are Handled in Windows 9x / Me?)
-endobj
-961 0 obj
-<< /S /GoTo /D (subsection.18.4.2) >>
-endobj
-964 0 obj
-(18.4.2 MS Windows NT4 Workstation)
-endobj
-965 0 obj
-<< /S /GoTo /D (subsection.18.4.3) >>
-endobj
-968 0 obj
-(18.4.3 MS Windows 200x/XP)
-endobj
-969 0 obj
-<< /S /GoTo /D (chapter.19) >>
-endobj
-972 0 obj
-(19 Interdomain Trust Relationships)
-endobj
-973 0 obj
-<< /S /GoTo /D (section.19.1) >>
-endobj
-976 0 obj
-(19.1 Trust Relationship Background)
-endobj
-977 0 obj
-<< /S /GoTo /D (section.19.2) >>
-endobj
-980 0 obj
-(19.2 Native MS Windows NT4 Trusts Configuration)
-endobj
-981 0 obj
-<< /S /GoTo /D (subsection.19.2.1) >>
-endobj
-984 0 obj
-(19.2.1 NT4 as the Trusting Domain \(ie. creating the trusted account\))
-endobj
-985 0 obj
-<< /S /GoTo /D (subsection.19.2.2) >>
-endobj
-988 0 obj
-(19.2.2 NT4 as the Trusted Domain \(ie. creating trusted account's password\))
-endobj
-989 0 obj
-<< /S /GoTo /D (section.19.3) >>
-endobj
-992 0 obj
-(19.3 Configuring Samba NT-style Domain Trusts)
-endobj
-993 0 obj
-<< /S /GoTo /D (subsection.19.3.1) >>
-endobj
-996 0 obj
-(19.3.1 Samba-3 as the Trusting Domain)
-endobj
-997 0 obj
-<< /S /GoTo /D (subsection.19.3.2) >>
-endobj
-1000 0 obj
-(19.3.2 Samba-3 as the Trusted Domain)
-endobj
-1001 0 obj
-<< /S /GoTo /D (chapter.20) >>
-endobj
-1004 0 obj
-(20 PAM Configuration for Centrally Managed Authentication)
-endobj
-1005 0 obj
-<< /S /GoTo /D (section.20.1) >>
-endobj
-1008 0 obj
-(20.1 Samba and PAM)
-endobj
-1009 0 obj
-<< /S /GoTo /D (subsection.20.1.1) >>
-endobj
-1012 0 obj
-(20.1.1 PAM Configuration in smb.conf)
-endobj
-1013 0 obj
-<< /S /GoTo /D (subsection.20.1.2) >>
-endobj
-1016 0 obj
-(20.1.2 Password Synchronisation using pam\137smbpass.so)
-endobj
-1017 0 obj
-<< /S /GoTo /D (subsubsection.20.1.2.1) >>
-endobj
-1020 0 obj
-(20.1.2.1 Password Synchonisation Configuration)
-endobj
-1021 0 obj
-<< /S /GoTo /D (subsubsection.20.1.2.2) >>
-endobj
-1024 0 obj
-(20.1.2.2 Password Migration Configuration)
-endobj
-1025 0 obj
-<< /S /GoTo /D (subsubsection.20.1.2.3) >>
-endobj
-1028 0 obj
-(20.1.2.3 Mature Password Configuration)
-endobj
-1029 0 obj
-<< /S /GoTo /D (subsubsection.20.1.2.4) >>
-endobj
-1032 0 obj
-(20.1.2.4 Kerberos Password Integration Configuration)
-endobj
-1033 0 obj
-<< /S /GoTo /D (section.20.2) >>
-endobj
-1036 0 obj
-(20.2 Distributed Authentication)
-endobj
-1037 0 obj
-<< /S /GoTo /D (chapter.21) >>
-endobj
-1040 0 obj
-(21 Stackable VFS modules)
-endobj
-1041 0 obj
-<< /S /GoTo /D (section.21.1) >>
-endobj
-1044 0 obj
-(21.1 Introduction and configuration)
-endobj
-1045 0 obj
-<< /S /GoTo /D (section.21.2) >>
-endobj
-1048 0 obj
-(21.2 Included modules)
-endobj
-1049 0 obj
-<< /S /GoTo /D (subsection.21.2.1) >>
-endobj
-1052 0 obj
-(21.2.1 audit)
-endobj
-1053 0 obj
-<< /S /GoTo /D (subsection.21.2.2) >>
-endobj
-1056 0 obj
-(21.2.2 extd\137audit)
-endobj
-1057 0 obj
-<< /S /GoTo /D (subsection.21.2.3) >>
-endobj
-1060 0 obj
-(21.2.3 recycle)
-endobj
-1061 0 obj
-<< /S /GoTo /D (subsection.21.2.4) >>
-endobj
-1064 0 obj
-(21.2.4 netatalk)
-endobj
-1065 0 obj
-<< /S /GoTo /D (section.21.3) >>
-endobj
-1068 0 obj
-(21.3 VFS modules available elsewhere)
-endobj
-1069 0 obj
-<< /S /GoTo /D (subsection.21.3.1) >>
-endobj
-1072 0 obj
-(21.3.1 DatabaseFS)
-endobj
-1073 0 obj
-<< /S /GoTo /D (subsection.21.3.2) >>
-endobj
-1076 0 obj
-(21.3.2 vscan)
-endobj
-1077 0 obj
-<< /S /GoTo /D (chapter.22) >>
-endobj
-1080 0 obj
-(22 Hosting a Microsoft Distributed File System tree on Samba)
-endobj
-1081 0 obj
-<< /S /GoTo /D (section.22.1) >>
-endobj
-1084 0 obj
-(22.1 Instructions)
-endobj
-1085 0 obj
-<< /S /GoTo /D (subsection.22.1.1) >>
-endobj
-1088 0 obj
-(22.1.1 Notes)
-endobj
-1089 0 obj
-<< /S /GoTo /D (chapter.23) >>
-endobj
-1092 0 obj
-(23 Integrating MS Windows networks with Samba)
-endobj
-1093 0 obj
-<< /S /GoTo /D (section.23.1) >>
-endobj
-1096 0 obj
-(23.1 Name Resolution in a pure Unix/Linux world)
-endobj
-1097 0 obj
-<< /S /GoTo /D (subsection.23.1.1) >>
-endobj
-1100 0 obj
-(23.1.1 /etc/hosts)
-endobj
-1101 0 obj
-<< /S /GoTo /D (subsection.23.1.2) >>
-endobj
-1104 0 obj
-(23.1.2 /etc/resolv.conf)
-endobj
-1105 0 obj
-<< /S /GoTo /D (subsection.23.1.3) >>
-endobj
-1108 0 obj
-(23.1.3 /etc/host.conf)
-endobj
-1109 0 obj
-<< /S /GoTo /D (subsection.23.1.4) >>
-endobj
-1112 0 obj
-(23.1.4 /etc/nsswitch.conf)
-endobj
-1113 0 obj
-<< /S /GoTo /D (section.23.2) >>
-endobj
-1116 0 obj
-(23.2 Name resolution as used within MS Windows networking)
-endobj
-1117 0 obj
-<< /S /GoTo /D (subsection.23.2.1) >>
-endobj
-1120 0 obj
-(23.2.1 The NetBIOS Name Cache)
-endobj
-1121 0 obj
-<< /S /GoTo /D (subsection.23.2.2) >>
-endobj
-1124 0 obj
-(23.2.2 The LMHOSTS file)
-endobj
-1125 0 obj
-<< /S /GoTo /D (subsection.23.2.3) >>
-endobj
-1128 0 obj
-(23.2.3 HOSTS file)
-endobj
-1129 0 obj
-<< /S /GoTo /D (subsection.23.2.4) >>
-endobj
-1132 0 obj
-(23.2.4 DNS Lookup)
-endobj
-1133 0 obj
-<< /S /GoTo /D (subsection.23.2.5) >>
-endobj
-1136 0 obj
-(23.2.5 WINS Lookup)
-endobj
-1137 0 obj
-<< /S /GoTo /D (chapter.24) >>
-endobj
-1140 0 obj
-(24 Securing Samba)
-endobj
-1141 0 obj
-<< /S /GoTo /D (section.24.1) >>
-endobj
-1144 0 obj
-(24.1 Introduction)
-endobj
-1145 0 obj
-<< /S /GoTo /D (section.24.2) >>
-endobj
-1148 0 obj
-(24.2 Using host based protection)
-endobj
-1149 0 obj
-<< /S /GoTo /D (section.24.3) >>
-endobj
-1152 0 obj
-(24.3 Using interface protection)
-endobj
-1153 0 obj
-<< /S /GoTo /D (section.24.4) >>
-endobj
-1156 0 obj
-(24.4 Using a firewall)
-endobj
-1157 0 obj
-<< /S /GoTo /D (section.24.5) >>
-endobj
-1160 0 obj
-(24.5 Using a IPC\044 share deny)
-endobj
-1161 0 obj
-<< /S /GoTo /D (section.24.6) >>
-endobj
-1164 0 obj
-(24.6 NTLMv2 Security)
-endobj
-1165 0 obj
-<< /S /GoTo /D (section.24.7) >>
-endobj
-1168 0 obj
-(24.7 Upgrading Samba)
-endobj
-1169 0 obj
-<< /S /GoTo /D (chapter.25) >>
-endobj
-1172 0 obj
-(25 Unicode/Charsets)
-endobj
-1173 0 obj
-<< /S /GoTo /D (section.25.1) >>
-endobj
-1176 0 obj
-(25.1 What are charsets and unicode?)
-endobj
-1177 0 obj
-<< /S /GoTo /D (section.25.2) >>
-endobj
-1180 0 obj
-(25.2 Samba and charsets)
-endobj
-1181 0 obj
-<< /S /GoTo /D (section.25.3) >>
-endobj
-1184 0 obj
-(25.3 Conversion from old names)
-endobj
-1185 0 obj
-<< /S /GoTo /D (section.25.4) >>
-endobj
-1188 0 obj
-(25.4 Japanese charsets)
-endobj
-1189 0 obj
-<< /S /GoTo /D (chapter.26) >>
-endobj
-1192 0 obj
-(26 File and Record Locking)
-endobj
-1193 0 obj
-<< /S /GoTo /D (section.26.1) >>
-endobj
-1196 0 obj
-(26.1 Discussion)
-endobj
-1197 0 obj
-<< /S /GoTo /D (section.26.2) >>
-endobj
-1200 0 obj
-(26.2 Samba Opportunistic Locking Control)
-endobj
-1201 0 obj
-<< /S /GoTo /D (section.26.3) >>
-endobj
-1204 0 obj
-(26.3 MS Windows Opportunistic Locking and Caching Controls)
-endobj
-1205 0 obj
-<< /S /GoTo /D (subsection.26.3.1) >>
-endobj
-1208 0 obj
-(26.3.1 Workstation Service Entries)
-endobj
-1209 0 obj
-<< /S /GoTo /D (subsection.26.3.2) >>
-endobj
-1212 0 obj
-(26.3.2 Server Service Entries)
-endobj
-1213 0 obj
-<< /S /GoTo /D (section.26.4) >>
-endobj
-1216 0 obj
-(26.4 Persistent Data Corruption)
-endobj
-1217 0 obj
-<< /S /GoTo /D (section.26.5) >>
-endobj
-1220 0 obj
-(26.5 Additional Reading)
-endobj
-1221 0 obj
-<< /S /GoTo /D (part.4) >>
-endobj
-1224 0 obj
-(IV Troubleshooting)
-endobj
-1225 0 obj
-<< /S /GoTo /D (chapter.27) >>
-endobj
-1228 0 obj
-(27 The samba checklist)
-endobj
-1229 0 obj
-<< /S /GoTo /D (section.27.1) >>
-endobj
-1232 0 obj
-(27.1 Introduction)
-endobj
-1233 0 obj
-<< /S /GoTo /D (section.27.2) >>
-endobj
-1236 0 obj
-(27.2 Assumptions)
-endobj
-1237 0 obj
-<< /S /GoTo /D (section.27.3) >>
-endobj
-1240 0 obj
-(27.3 The tests)
-endobj
-1241 0 obj
-<< /S /GoTo /D (section.27.4) >>
-endobj
-1244 0 obj
-(27.4 Still having troubles?)
-endobj
-1245 0 obj
-<< /S /GoTo /D (chapter.28) >>
-endobj
-1248 0 obj
-(28 Analysing and solving samba problems)
-endobj
-1249 0 obj
-<< /S /GoTo /D (section.28.1) >>
-endobj
-1252 0 obj
-(28.1 Diagnostics tools)
-endobj
-1253 0 obj
-<< /S /GoTo /D (section.28.2) >>
-endobj
-1256 0 obj
-(28.2 Installing 'Network Monitor' on an NT Workstation or a Windows 9x box)
-endobj
-1257 0 obj
-<< /S /GoTo /D (section.28.3) >>
-endobj
-1260 0 obj
-(28.3 Useful URL's)
-endobj
-1261 0 obj
-<< /S /GoTo /D (section.28.4) >>
-endobj
-1264 0 obj
-(28.4 Getting help from the mailing lists)
-endobj
-1265 0 obj
-<< /S /GoTo /D (section.28.5) >>
-endobj
-1268 0 obj
-(28.5 How to get off the mailinglists)
-endobj
-1269 0 obj
-<< /S /GoTo /D (chapter.29) >>
-endobj
-1272 0 obj
-(29 Reporting Bugs)
-endobj
-1273 0 obj
-<< /S /GoTo /D (section.29.1) >>
-endobj
-1276 0 obj
-(29.1 Introduction)
-endobj
-1277 0 obj
-<< /S /GoTo /D (section.29.2) >>
-endobj
-1280 0 obj
-(29.2 General info)
-endobj
-1281 0 obj
-<< /S /GoTo /D (section.29.3) >>
-endobj
-1284 0 obj
-(29.3 Debug levels)
-endobj
-1285 0 obj
-<< /S /GoTo /D (section.29.4) >>
-endobj
-1288 0 obj
-(29.4 Internal errors)
-endobj
-1289 0 obj
-<< /S /GoTo /D (section.29.5) >>
-endobj
-1292 0 obj
-(29.5 Attaching to a running process)
-endobj
-1293 0 obj
-<< /S /GoTo /D (section.29.6) >>
-endobj
-1296 0 obj
-(29.6 Patches)
-endobj
-1297 0 obj
-<< /S /GoTo /D (part.5) >>
-endobj
-1300 0 obj
-(V Appendixes)
-endobj
-1301 0 obj
-<< /S /GoTo /D (chapter.30) >>
-endobj
-1304 0 obj
-(30 How to compile SAMBA)
-endobj
-1305 0 obj
-<< /S /GoTo /D (section.30.1) >>
-endobj
-1308 0 obj
-(30.1 Access Samba source code via CVS)
-endobj
-1309 0 obj
-<< /S /GoTo /D (subsection.30.1.1) >>
-endobj
-1312 0 obj
-(30.1.1 Introduction)
-endobj
-1313 0 obj
-<< /S /GoTo /D (subsection.30.1.2) >>
-endobj
-1316 0 obj
-(30.1.2 CVS Access to samba.org)
-endobj
-1317 0 obj
-<< /S /GoTo /D (subsubsection.30.1.2.1) >>
-endobj
-1320 0 obj
-(30.1.2.1 Access via CVSweb)
-endobj
-1321 0 obj
-<< /S /GoTo /D (subsubsection.30.1.2.2) >>
-endobj
-1324 0 obj
-(30.1.2.2 Access via cvs)
-endobj
-1325 0 obj
-<< /S /GoTo /D (section.30.2) >>
-endobj
-1328 0 obj
-(30.2 Accessing the samba sources via rsync and ftp)
-endobj
-1329 0 obj
-<< /S /GoTo /D (section.30.3) >>
-endobj
-1332 0 obj
-(30.3 Verifying Samba's PGP signature)
-endobj
-1333 0 obj
-<< /S /GoTo /D (section.30.4) >>
-endobj
-1336 0 obj
-(30.4 Building the Binaries)
-endobj
-1337 0 obj
-<< /S /GoTo /D (subsection.30.4.1) >>
-endobj
-1340 0 obj
-(30.4.1 Compiling samba with Active Directory support)
-endobj
-1341 0 obj
-<< /S /GoTo /D (subsubsection.30.4.1.1) >>
-endobj
-1344 0 obj
-(30.4.1.1 Installing the required packages for Debian)
-endobj
-1345 0 obj
-<< /S /GoTo /D (subsubsection.30.4.1.2) >>
-endobj
-1348 0 obj
-(30.4.1.2 Installing the required packages for RedHat)
-endobj
-1349 0 obj
-<< /S /GoTo /D (section.30.5) >>
-endobj
-1352 0 obj
-(30.5 Starting the smbd and nmbd)
-endobj
-1353 0 obj
-<< /S /GoTo /D (subsection.30.5.1) >>
-endobj
-1356 0 obj
-(30.5.1 Starting from inetd.conf)
-endobj
-1357 0 obj
-<< /S /GoTo /D (subsection.30.5.2) >>
-endobj
-1360 0 obj
-(30.5.2 Alternative: starting it as a daemon)
-endobj
-1361 0 obj
-<< /S /GoTo /D (chapter.31) >>
-endobj
-1364 0 obj
-(31 Migration from NT4 PDC to Samba-3 PDC)
-endobj
-1365 0 obj
-<< /S /GoTo /D (section.31.1) >>
-endobj
-1368 0 obj
-(31.1 Planning and Getting Started)
-endobj
-1369 0 obj
-<< /S /GoTo /D (subsection.31.1.1) >>
-endobj
-1372 0 obj
-(31.1.1 Objectives)
-endobj
-1373 0 obj
-<< /S /GoTo /D (subsubsection.31.1.1.1) >>
-endobj
-1376 0 obj
-(31.1.1.1 Domain Layout)
-endobj
-1377 0 obj
-<< /S /GoTo /D (subsubsection.31.1.1.2) >>
-endobj
-1380 0 obj
-(31.1.1.2 Server Share and Directory Layout)
-endobj
-1381 0 obj
-<< /S /GoTo /D (subsubsection.31.1.1.3) >>
-endobj
-1384 0 obj
-(31.1.1.3 Logon Scripts)
-endobj
-1385 0 obj
-<< /S /GoTo /D (subsubsection.31.1.1.4) >>
-endobj
-1388 0 obj
-(31.1.1.4 Profile Migration/Creation)
-endobj
-1389 0 obj
-<< /S /GoTo /D (subsubsection.31.1.1.5) >>
-endobj
-1392 0 obj
-(31.1.1.5 User and Group Accounts)
-endobj
-1393 0 obj
-<< /S /GoTo /D (subsection.31.1.2) >>
-endobj
-1396 0 obj
-(31.1.2 Steps In Migration Process)
-endobj
-1397 0 obj
-<< /S /GoTo /D (section.31.2) >>
-endobj
-1400 0 obj
-(31.2 Migration Options)
-endobj
-1401 0 obj
-<< /S /GoTo /D (subsection.31.2.1) >>
-endobj
-1404 0 obj
-(31.2.1 Planning for Success)
-endobj
-1405 0 obj
-<< /S /GoTo /D (subsection.31.2.2) >>
-endobj
-1408 0 obj
-(31.2.2 Samba Implementation Choices)
-endobj
-1409 0 obj
-<< /S /GoTo /D (chapter.32) >>
-endobj
-1412 0 obj
-(32 Portability)
-endobj
-1413 0 obj
-<< /S /GoTo /D (section.32.1) >>
-endobj
-1416 0 obj
-(32.1 HPUX)
-endobj
-1417 0 obj
-<< /S /GoTo /D (section.32.2) >>
-endobj
-1420 0 obj
-(32.2 SCO Unix)
-endobj
-1421 0 obj
-<< /S /GoTo /D (section.32.3) >>
-endobj
-1424 0 obj
-(32.3 DNIX)
-endobj
-1425 0 obj
-<< /S /GoTo /D (section.32.4) >>
-endobj
-1428 0 obj
-(32.4 RedHat Linux Rembrandt-II)
-endobj
-1429 0 obj
-<< /S /GoTo /D (section.32.5) >>
-endobj
-1432 0 obj
-(32.5 AIX)
-endobj
-1433 0 obj
-<< /S /GoTo /D (subsection.32.5.1) >>
-endobj
-1436 0 obj
-(32.5.1 Sequential Read Ahead)
-endobj
-1437 0 obj
-<< /S /GoTo /D (section.32.6) >>
-endobj
-1440 0 obj
-(32.6 Solaris)
-endobj
-1441 0 obj
-<< /S /GoTo /D (subsection.32.6.1) >>
-endobj
-1444 0 obj
-(32.6.1 Locking improvements)
-endobj
-1445 0 obj
-<< /S /GoTo /D (subsection.32.6.2) >>
-endobj
-1448 0 obj
-(32.6.2 Winbind on Solaris 9)
-endobj
-1449 0 obj
-<< /S /GoTo /D (chapter.33) >>
-endobj
-1452 0 obj
-(33 Samba and other CIFS clients)
-endobj
-1453 0 obj
-<< /S /GoTo /D (section.33.1) >>
-endobj
-1456 0 obj
-(33.1 Macintosh clients?)
-endobj
-1457 0 obj
-<< /S /GoTo /D (section.33.2) >>
-endobj
-1460 0 obj
-(33.2 OS2 Client)
-endobj
-1461 0 obj
-<< /S /GoTo /D (subsection.33.2.1) >>
-endobj
-1464 0 obj
-(33.2.1 How can I configure OS/2 Warp Connect or OS/2 Warp 4 as a client for Samba?)
-endobj
-1465 0 obj
-<< /S /GoTo /D (subsection.33.2.2) >>
-endobj
-1468 0 obj
-(33.2.2 How can I configure OS/2 Warp 3 \(not Connect\), OS/2 1.2, 1.3 or 2.x for Samba?)
-endobj
-1469 0 obj
-<< /S /GoTo /D (subsection.33.2.3) >>
-endobj
-1472 0 obj
-(33.2.3 Are there any other issues when OS/2 \(any version\) is used as a client?)
-endobj
-1473 0 obj
-<< /S /GoTo /D (subsection.33.2.4) >>
-endobj
-1476 0 obj
-(33.2.4 How do I get printer driver download working for OS/2 clients?)
-endobj
-1477 0 obj
-<< /S /GoTo /D (section.33.3) >>
-endobj
-1480 0 obj
-(33.3 Windows for Workgroups)
-endobj
-1481 0 obj
-<< /S /GoTo /D (subsection.33.3.1) >>
-endobj
-1484 0 obj
-(33.3.1 Use latest TCP/IP stack from Microsoft)
-endobj
-1485 0 obj
-<< /S /GoTo /D (subsection.33.3.2) >>
-endobj
-1488 0 obj
-(33.3.2 Delete .pwl files after password change)
-endobj
-1489 0 obj
-<< /S /GoTo /D (subsection.33.3.3) >>
-endobj
-1492 0 obj
-(33.3.3 Configure WfW password handling)
-endobj
-1493 0 obj
-<< /S /GoTo /D (subsection.33.3.4) >>
-endobj
-1496 0 obj
-(33.3.4 Case handling of passwords)
-endobj
-1497 0 obj
-<< /S /GoTo /D (subsection.33.3.5) >>
-endobj
-1500 0 obj
-(33.3.5 Use TCP/IP as default protocol)
-endobj
-1501 0 obj
-<< /S /GoTo /D (subsection.33.3.6) >>
-endobj
-1504 0 obj
-(33.3.6 Speed improvement)
-endobj
-1505 0 obj
-<< /S /GoTo /D (section.33.4) >>
-endobj
-1508 0 obj
-(33.4 Windows '95/'98)
-endobj
-1509 0 obj
-<< /S /GoTo /D (subsection.33.4.1) >>
-endobj
-1512 0 obj
-(33.4.1 Speed improvement)
-endobj
-1513 0 obj
-<< /S /GoTo /D (section.33.5) >>
-endobj
-1516 0 obj
-(33.5 Windows 2000 Service Pack 2)
-endobj
-1517 0 obj
-<< /S /GoTo /D (section.33.6) >>
-endobj
-1520 0 obj
-(33.6 Windows NT 3.1)
-endobj
-1521 0 obj
-<< /S /GoTo /D (chapter.34) >>
-endobj
-1524 0 obj
-(34 SWAT - The Samba Web Admininistration Tool)
-endobj
-1525 0 obj
-<< /S /GoTo /D (section.34.1) >>
-endobj
-1528 0 obj
-(34.1 SWAT Features and Benefits)
-endobj
-1529 0 obj
-<< /S /GoTo /D (subsection.34.1.1) >>
-endobj
-1532 0 obj
-(34.1.1 Enabling SWAT for use)
-endobj
-1533 0 obj
-<< /S /GoTo /D (subsection.34.1.2) >>
-endobj
-1536 0 obj
-(34.1.2 Securing SWAT through SSL)
-endobj
-1537 0 obj
-<< /S /GoTo /D (subsection.34.1.3) >>
-endobj
-1540 0 obj
-(34.1.3 The SWAT Home Page)
-endobj
-1541 0 obj
-<< /S /GoTo /D (subsection.34.1.4) >>
-endobj
-1544 0 obj
-(34.1.4 Global Settings)
-endobj
-1545 0 obj
-<< /S /GoTo /D (subsection.34.1.5) >>
-endobj
-1548 0 obj
-(34.1.5 Share Settings)
-endobj
-1549 0 obj
-<< /S /GoTo /D (subsection.34.1.6) >>
-endobj
-1552 0 obj
-(34.1.6 Printers Settings)
-endobj
-1553 0 obj
-<< /S /GoTo /D (subsection.34.1.7) >>
-endobj
-1556 0 obj
-(34.1.7 The SWAT Wizard)
-endobj
-1557 0 obj
-<< /S /GoTo /D (subsection.34.1.8) >>
-endobj
-1560 0 obj
-(34.1.8 The Status Page)
-endobj
-1561 0 obj
-<< /S /GoTo /D (subsection.34.1.9) >>
-endobj
-1564 0 obj
-(34.1.9 The View Page)
-endobj
-1565 0 obj
-<< /S /GoTo /D (subsection.34.1.10) >>
-endobj
-1568 0 obj
-(34.1.10 The Password Change Page)
-endobj
-1569 0 obj
-<< /S /GoTo /D (chapter.35) >>
-endobj
-1572 0 obj
-(35 Samba performance issues)
-endobj
-1573 0 obj
-<< /S /GoTo /D (section.35.1) >>
-endobj
-1576 0 obj
-(35.1 Comparisons)
-endobj
-1577 0 obj
-<< /S /GoTo /D (section.35.2) >>
-endobj
-1580 0 obj
-(35.2 Socket options)
-endobj
-1581 0 obj
-<< /S /GoTo /D (section.35.3) >>
-endobj
-1584 0 obj
-(35.3 Read size)
-endobj
-1585 0 obj
-<< /S /GoTo /D (section.35.4) >>
-endobj
-1588 0 obj
-(35.4 Max xmit)
-endobj
-1589 0 obj
-<< /S /GoTo /D (section.35.5) >>
-endobj
-1592 0 obj
-(35.5 Log level)
-endobj
-1593 0 obj
-<< /S /GoTo /D (section.35.6) >>
-endobj
-1596 0 obj
-(35.6 Read raw)
-endobj
-1597 0 obj
-<< /S /GoTo /D (section.35.7) >>
-endobj
-1600 0 obj
-(35.7 Write raw)
-endobj
-1601 0 obj
-<< /S /GoTo /D (section.35.8) >>
-endobj
-1604 0 obj
-(35.8 Slow Logins)
-endobj
-1605 0 obj
-<< /S /GoTo /D (section.35.9) >>
-endobj
-1608 0 obj
-(35.9 Client tuning)
-endobj
-1609 0 obj
-<< /S /GoTo /D [1610 0 R /Fit ] >>
-endobj
-1612 0 obj <<
-/Length 244
-/Filter /FlateDecode
->>
-stream
-xOK09&dw ]E[z;h yyo24^scR+o!Y5RH$SSd:$op]mFr5yn'5hmc;> {w_r"OA0jB@
-A"e%j~l7q
-endobj
-1610 0 obj <<
-/Type /Page
-/Contents 1612 0 R
-/Resources 1611 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 1621 0 R
->> endobj
-1613 0 obj <<
-/D [1610 0 R /XYZ 85.039 786.531 null]
->> endobj
-1614 0 obj <<
-/D [1610 0 R /XYZ 85.039 766.606 null]
->> endobj
-1611 0 obj <<
-/Font << /F20 1617 0 R /F21 1620 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-1624 0 obj <<
-/Length 1386
-/Filter /FlateDecode
->>
-stream
-xWMs6 WxrYyfH"%Y3\zCVlmd#x
-J?,n~IYGe\,wu?UV0-K>@V~gmZ$j;e'Ah V,h M1ijq`
-([Od%yMGhj=n:8x8/ '>:1\k~\joIi7
-@u2o,#D$  ,UH.R%u{fyvBJ!+:igq'#TM3>e>"{]e.z^n0
-Ue6,RGn<O-7U3f(k!!]owL?YL.w$JdG XEEHKZ:zAu$MIj$\
-:hzav=^oiI)wlQ$O/8$; Swx: /EVglwCZ. 4eh^1Ww†œ…âR35!)G.N_ysM H@5pV?E:\a49P.~ENGu$l?>q'/vA,[?/RN\;Azk-5MEn3k<-^5<C/!D4599,t8z/a0X1q8+gSB_L|=CJ55,HH%wL$*8#TvV!<xeDw:\=+PBc?9nS3|2&k% #Fo8=Sed:bBJD0j;&1[-A&l >c2=!=8qM;p[:hFB_"9Mun/fc5 k{ Z2v_5
-`'E*Q Eendstream
-endobj
-1623 0 obj <<
-/Type /Page
-/Contents 1624 0 R
-/Resources 1622 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 1621 0 R
-/Annots [ 1629 0 R 1633 0 R 1634 0 R 1635 0 R ]
->> endobj
-1629 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [210.406 523.32 332.67 535.312]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.samba.org/)>>
->> endobj
-1633 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [138.346 509.468 215.702 522.369]
-/Subtype/Link/A<</Type/Action/S/URI/URI(mailto:jelmer@samba.org)>>
->> endobj
-1634 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [220.377 509.468 289.612 522.369]
-/Subtype/Link/A<</Type/Action/S/URI/URI(mailto:jht@samba.org)>>
->> endobj
-1635 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [304.619 509.468 410.324 522.369]
-/Subtype/Link/A<</Type/Action/S/URI/URI(mailto:jerry@samba.org)>>
->> endobj
-1625 0 obj <<
-/D [1623 0 R /XYZ 85.039 786.531 null]
->> endobj
-1622 0 obj <<
-/Font << /F15 1628 0 R /F35 1632 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-1638 0 obj <<
-/Length 554
-/Filter /FlateDecode
->>
-stream
-xT0>1Ri­¶]zÚî
-RNYbFpq&
-0wLCA$Sm|=WKTL+IN.1X)_TJ 3$!m>6m:|[S&y%3wia|=|@#Nh
-Qi9kdM!D3;'xZSy$:j|=7
-,5NT%Q#@`?oK(Um %<7vfw
-N=V:6P~s{~9Z5zS83g;5N7WNr#Wp2; C~Y{XG7Wúõ¸ØZf(d<q+D(b+l;h5.ku!U 5wendstream
-endobj
-1637 0 obj <<
-/Type /Page
-/Contents 1638 0 R
-/Resources 1636 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 1621 0 R
-/Annots [ 1643 0 R ]
->> endobj
-1643 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [156.148 704.616 341.202 715.741]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.fsf.org/licenses/gpl.txt)>>
->> endobj
-1639 0 obj <<
-/D [1637 0 R /XYZ 85.039 786.531 null]
->> endobj
-1636 0 obj <<
-/Font << /F56 1642 0 R /F15 1628 0 R /F35 1632 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-1646 0 obj <<
-/Length 1747
-/Filter /FlateDecode
->>
-stream
-xZ[sF~[LD,OISwj)D2@qs! u/]w`V'N}W Nf>0B**)eW|z2h[ =Zq48x÷:Üs}_t´r0úÛ9ÎÒ2N6 }RhWe9s5$;0J5y4;'iQ=s&Qd L 2`>OVE&noKa1+-n=][b
-/2 5m\v v.h,`6uj6j4I3l|)Pom+Bt;BQ/lJ.)tI4./=Q6! .D@) h$&,`\"T{~JEW ,gWFiC v``<M
-6NU
-R/ hb{~nae'6x= rLb!`&'I ]
-<RS>ay88sN~Goqe+;KoLG|l0H _m_dC<]MK"aqpI0.;do_ljs_a&ZG h q91DejQT5tRVv!b vFXv,p<6R.lSr!aJ]fb@<t s%[tLx~9d6Yé’dþ¾Üow•lë½jQ3iV=?in^mpC)qf>-T^v)"
-U &*!GzMc9 k6C"QJ I>D.W/%[/bpMV} 1E{6)}l2~-CL_[ktx>R<$oL.WFeFF_
-\Y1shEMjdp]y"<n;;8K>Ydc P
-Z'UmWy_R.endstream
-endobj
-1645 0 obj <<
-/Type /Page
-/Contents 1646 0 R
-/Resources 1644 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 1621 0 R
-/Annots [ 1649 0 R 1650 0 R 1651 0 R 1652 0 R 1653 0 R 1654 0 R 1655 0 R 1656 0 R 1657 0 R 1658 0 R 1659 0 R 1660 0 R 1661 0 R 1662 0 R 1663 0 R 1664 0 R 1665 0 R 1666 0 R 1667 0 R 1668 0 R 1669 0 R 1670 0 R 1671 0 R 1672 0 R 1673 0 R 1674 0 R 1675 0 R 1676 0 R 1677 0 R 1678 0 R 1679 0 R 1680 0 R 1681 0 R 1682 0 R ]
->> endobj
-1649 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [497.163 617.124 512.306 627.419]
-/Subtype /Link
-/A << /S /GoTo /D (part.1) >>
->> endobj
-1650 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [498.314 592.666 512.306 602.234]
-/Subtype /Link
-/A << /S /GoTo /D (chapter.1) >>
->> endobj
-1651 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 579.116 512.306 588.139]
-/Subtype /Link
-/A << /S /GoTo /D (section.1.1) >>
->> endobj
-1652 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 565.567 512.306 574.59]
-/Subtype /Link
-/A << /S /GoTo /D (section.1.2) >>
->> endobj
-1653 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 552.018 512.306 561.041]
-/Subtype /Link
-/A << /S /GoTo /D (section.1.3) >>
->> endobj
-1654 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 538.469 512.306 547.492]
-/Subtype /Link
-/A << /S /GoTo /D (section.1.4) >>
->> endobj
-1655 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 524.92 512.306 533.942]
-/Subtype /Link
-/A << /S /GoTo /D (section.1.5) >>
->> endobj
-1656 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 511.37 512.306 520.393]
-/Subtype /Link
-/A << /S /GoTo /D (section.1.6) >>
->> endobj
-1657 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 497.821 512.306 506.844]
-/Subtype /Link
-/A << /S /GoTo /D (section.1.7) >>
->> endobj
-1658 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [498.314 473.363 512.306 482.931]
-/Subtype /Link
-/A << /S /GoTo /D (chapter.2) >>
->> endobj
-1659 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 459.814 512.306 468.837]
-/Subtype /Link
-/A << /S /GoTo /D (section.2.1) >>
->> endobj
-1660 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 446.265 512.306 455.287]
-/Subtype /Link
-/A << /S /GoTo /D (section.2.2) >>
->> endobj
-1661 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 432.715 512.306 441.738]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.2.2.1) >>
->> endobj
-1662 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 419.166 512.306 428.189]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.2.2.1.1) >>
->> endobj
-1663 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 405.617 512.306 414.64]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.2.2.2) >>
->> endobj
-1664 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 392.068 512.306 401.091]
-/Subtype /Link
-/A << /S /GoTo /D (section.2.3) >>
->> endobj
-1665 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 378.519 512.306 387.541]
-/Subtype /Link
-/A << /S /GoTo /D (section.2.4) >>
->> endobj
-1666 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 351.42 512.306 360.443]
-/Subtype /Link
-/A << /S /GoTo /D (section.2.5) >>
->> endobj
-1667 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 337.871 512.306 346.894]
-/Subtype /Link
-/A << /S /GoTo /D (section.2.6) >>
->> endobj
-1668 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [497.163 299.378 512.306 309.672]
-/Subtype /Link
-/A << /S /GoTo /D (part.2) >>
->> endobj
-1669 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [498.314 274.919 512.306 284.488]
-/Subtype /Link
-/A << /S /GoTo /D (chapter.3) >>
->> endobj
-1670 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 261.37 512.306 270.393]
-/Subtype /Link
-/A << /S /GoTo /D (section.3.1) >>
->> endobj
-1671 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 247.821 512.306 256.844]
-/Subtype /Link
-/A << /S /GoTo /D (section.3.2) >>
->> endobj
-1672 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 234.272 512.306 243.295]
-/Subtype /Link
-/A << /S /GoTo /D (section.3.3) >>
->> endobj
-1673 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 220.723 512.306 229.745]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.3.3.1) >>
->> endobj
-1674 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [498.314 196.264 512.306 205.833]
-/Subtype /Link
-/A << /S /GoTo /D (chapter.4) >>
->> endobj
-1675 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 182.715 512.306 191.738]
-/Subtype /Link
-/A << /S /GoTo /D (section.4.1) >>
->> endobj
-1676 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 169.166 512.306 178.189]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.4.1.1) >>
->> endobj
-1677 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 155.617 512.306 164.64]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.4.1.2) >>
->> endobj
-1678 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 142.068 512.306 151.09]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.4.1.3) >>
->> endobj
-1679 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 114.969 512.306 123.992]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.4.1.3.1) >>
->> endobj
-1680 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 101.42 512.306 110.443]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.4.1.3.2) >>
->> endobj
-1681 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 87.871 512.306 96.894]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.4.1.4) >>
->> endobj
-1682 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 60.772 512.306 69.795]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.4.1.4.1) >>
->> endobj
-1647 0 obj <<
-/D [1645 0 R /XYZ 85.039 786.531 null]
->> endobj
-1648 0 obj <<
-/D [1645 0 R /XYZ 85.039 656.613 null]
->> endobj
-1644 0 obj <<
-/Font << /F20 1617 0 R /F15 1628 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-1685 0 obj <<
-/Length 2278
-/Filter /FlateDecode
->>
-stream
-x[oFB(T4 6iCHK<K#2q.ivX}P=#6t6 \<l8[ \<`z3;!s 2lL58x?md,m 9X}c0c0+^BkrH:u,iSY=4s;Zv8<p4BX%_YK:1}Yj\8 }KwgCBz' i{{Zw>
-()%i2 Z/)U4Z_$_EiFK:_CdEI%4bD|oPEA}56)"hl9U?vkM ~OXYsIn?R lwnb@W5^l}tp_X_lU R!:L dR2-
-=MN
-7 tk J
-:_i>4&?yyA}_XGu9_t@ht QE5O]<j?j3xj01( fmWt6Ok5D]/t\\f~?f$J6C
-ro@(Jm5@0LN\
-6@AW 2H AWO4i7N]e_°ÞŠ©d?LeGM%>R YI`:SIq50c}2-UT_A+EI<ifCe"7EsI;k\t'"yq|sOU|]9NTC98==?w*w[T\?bw+D|O
-Ga}!r:%x~fp>r@FgT@45%HV)tg^(bW[I<V{-?"lUzmvc>v6wnn.7A9kc$*M3_!vDE50qS;:EL1)n43N.wE%QcUad2$N5>fa&"I4<!QzcR@-Jgha]h1_>X!)<5YB_S)(]DGQ'"(x '/ r^PrJl,2.Mj9(?q2q7Q&F0MP&G&S.tC|w
-endobj
-1684 0 obj <<
-/Type /Page
-/Contents 1685 0 R
-/Resources 1683 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 1621 0 R
-/Annots [ 1690 0 R 1691 0 R 1692 0 R 1693 0 R 1694 0 R 1695 0 R 1696 0 R 1697 0 R 1698 0 R 1699 0 R 1700 0 R 1701 0 R 1702 0 R 1703 0 R 1704 0 R 1705 0 R 1706 0 R 1707 0 R 1708 0 R 1709 0 R 1710 0 R 1711 0 R 1712 0 R 1713 0 R 1714 0 R 1715 0 R 1716 0 R 1717 0 R 1718 0 R 1719 0 R 1720 0 R 1721 0 R 1722 0 R 1723 0 R 1724 0 R 1725 0 R 1726 0 R 1727 0 R 1728 0 R ]
->> endobj
-1690 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 754.651 512.306 763.674]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.4.1.5) >>
->> endobj
-1691 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [498.314 730.193 512.306 739.761]
-/Subtype /Link
-/A << /S /GoTo /D (chapter.5) >>
->> endobj
-1692 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 716.643 512.306 725.666]
-/Subtype /Link
-/A << /S /GoTo /D (section.5.1) >>
->> endobj
-1693 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 703.094 512.306 712.117]
-/Subtype /Link
-/A << /S /GoTo /D (section.5.2) >>
->> endobj
-1694 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 689.545 512.306 698.568]
-/Subtype /Link
-/A << /S /GoTo /D (section.5.3) >>
->> endobj
-1695 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 675.996 512.306 685.019]
-/Subtype /Link
-/A << /S /GoTo /D (section.5.4) >>
->> endobj
-1696 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 662.447 512.306 671.469]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.5.4.1) >>
->> endobj
-1697 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 648.897 512.306 657.92]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.5.4.2) >>
->> endobj
-1698 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 635.348 512.306 644.371]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.5.4.3) >>
->> endobj
-1699 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 621.799 512.306 630.822]
-/Subtype /Link
-/A << /S /GoTo /D (section.5.5) >>
->> endobj
-1700 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 608.25 512.306 617.273]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.5.5.1) >>
->> endobj
-1701 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 567.602 512.306 576.625]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.5.5.2) >>
->> endobj
-1702 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 554.053 512.306 563.076]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.5.5.3) >>
->> endobj
-1703 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 526.955 512.306 535.978]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.5.5.4) >>
->> endobj
-1704 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 499.856 512.306 508.879]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.5.5.5) >>
->> endobj
-1705 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 486.307 512.306 495.33]
-/Subtype /Link
-/A << /S /GoTo /D (section.5.6) >>
->> endobj
-1706 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 472.758 512.306 481.781]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.5.6.1) >>
->> endobj
-1707 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [498.314 448.3 512.306 457.868]
-/Subtype /Link
-/A << /S /GoTo /D (chapter.6) >>
->> endobj
-1708 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 434.75 512.306 443.773]
-/Subtype /Link
-/A << /S /GoTo /D (section.6.1) >>
->> endobj
-1709 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 421.201 512.306 430.224]
-/Subtype /Link
-/A << /S /GoTo /D (section.6.2) >>
->> endobj
-1710 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 407.652 512.306 416.675]
-/Subtype /Link
-/A << /S /GoTo /D (section.6.3) >>
->> endobj
-1711 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 394.103 512.306 403.126]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.6.3.1) >>
->> endobj
-1712 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 380.554 512.306 389.576]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.6.3.2) >>
->> endobj
-1713 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 367.004 512.306 376.027]
-/Subtype /Link
-/A << /S /GoTo /D (section.6.4) >>
->> endobj
-1714 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 353.455 512.306 362.478]
-/Subtype /Link
-/A << /S /GoTo /D (section.6.5) >>
->> endobj
-1715 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 339.906 512.306 348.929]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.6.5.1) >>
->> endobj
-1716 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 326.357 512.306 335.38]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.6.5.2) >>
->> endobj
-1717 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [498.314 301.899 512.306 311.467]
-/Subtype /Link
-/A << /S /GoTo /D (chapter.7) >>
->> endobj
-1718 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 288.349 512.306 297.372]
-/Subtype /Link
-/A << /S /GoTo /D (section.7.1) >>
->> endobj
-1719 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 274.8 512.306 283.823]
-/Subtype /Link
-/A << /S /GoTo /D (section.7.2) >>
->> endobj
-1720 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 261.251 512.306 270.274]
-/Subtype /Link
-/A << /S /GoTo /D (section.7.3) >>
->> endobj
-1721 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 247.702 512.306 256.725]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.7.3.1) >>
->> endobj
-1722 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 234.153 512.306 243.175]
-/Subtype /Link
-/A << /S /GoTo /D (section.7.4) >>
->> endobj
-1723 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 220.603 512.306 229.626]
-/Subtype /Link
-/A << /S /GoTo /D (section.7.5) >>
->> endobj
-1724 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 207.054 512.306 216.077]
-/Subtype /Link
-/A << /S /GoTo /D (section.7.6) >>
->> endobj
-1725 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [498.314 182.596 512.306 192.164]
-/Subtype /Link
-/A << /S /GoTo /D (chapter.8) >>
->> endobj
-1726 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 169.047 512.306 178.069]
-/Subtype /Link
-/A << /S /GoTo /D (section.8.1) >>
->> endobj
-1727 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 155.497 512.306 164.52]
-/Subtype /Link
-/A << /S /GoTo /D (section.8.2) >>
->> endobj
-1728 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [497.163 117.004 512.306 127.299]
-/Subtype /Link
-/A << /S /GoTo /D (part.3) >>
->> endobj
-1686 0 obj <<
-/D [1684 0 R /XYZ 85.039 786.531 null]
->> endobj
-1683 0 obj <<
-/Font << /F62 1689 0 R /F15 1628 0 R /F20 1617 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-1731 0 obj <<
-/Length 2156
-/Filter /FlateDecode
->>
-stream
-x\RV}WQ~*\!RL&I d+%}>7F $]@k}9ko9v%w>#a7t9K3<;u{~N9~i/^MM]|' | ~I23JqgE]}UA IKIÏ ¹O8=Q4<QRoL.^pî ôÇO^M~=z7? ü¥xÊ}ñ›"WKu1ql=_UW~!(_UE.~$`'E$N?#FBO
-PL|ìr4…WL\>S{R(B5FD¨Ôç,Ýñ­DFtX k2UR)?{y+ 6$yMQ<zBw=I6QEbB.E)| *5+~BNTjfT(W3pj'l
-< P//U7N&J`L3R5fp(7rC 7Gr=J4æ“ìG[2_
-Agye'=<vd"+`fQ+AipcxI^eI]&9/xyiC0_35't9Vq7KdY*^Z R>d
-/@5l]/h'x3'LS lO1Lu4TfmmHY$Bga9:8XbXv7
-YBqd'Qvje@8,BZkq9X9l6|w>Lq6L.Bg:3D9Knr$i5R]gDBY1 0@He\bi3!Z\5GE; _˜®©O7?Bn#So#
-KTL[ P\$2lMw0`g^D6W97[Y$6oA87Tn=[PMiMxH."ciXBk==KPZ-D`[kdSUZbk,Iz$rzZU<ngQchEx[hB-
-'XiK-f$mK9A0w%`O&**
-8B[#0s:lWUB'UVc*_ ;-
-endobj
-1730 0 obj <<
-/Type /Page
-/Contents 1731 0 R
-/Resources 1729 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 1621 0 R
-/Annots [ 1733 0 R 1734 0 R 1735 0 R 1736 0 R 1737 0 R 1738 0 R 1739 0 R 1740 0 R 1741 0 R 1742 0 R 1743 0 R 1744 0 R 1745 0 R 1746 0 R 1747 0 R 1748 0 R 1749 0 R 1750 0 R 1751 0 R 1752 0 R 1753 0 R 1754 0 R 1755 0 R 1756 0 R 1757 0 R 1758 0 R 1759 0 R 1760 0 R 1761 0 R 1762 0 R 1763 0 R 1764 0 R 1765 0 R 1766 0 R 1767 0 R 1768 0 R 1769 0 R 1770 0 R 1771 0 R 1772 0 R 1773 0 R 1774 0 R 1775 0 R 1776 0 R 1777 0 R 1778 0 R 1779 0 R 1780 0 R 1781 0 R 1782 0 R ]
->> endobj
-1733 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [498.314 754.651 512.306 764.219]
-/Subtype /Link
-/A << /S /GoTo /D (chapter.9) >>
->> endobj
-1734 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 741.102 512.306 750.125]
-/Subtype /Link
-/A << /S /GoTo /D (section.9.1) >>
->> endobj
-1735 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 727.553 512.306 736.575]
-/Subtype /Link
-/A << /S /GoTo /D (section.9.2) >>
->> endobj
-1736 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 714.003 512.306 723.026]
-/Subtype /Link
-/A << /S /GoTo /D (section.9.3) >>
->> endobj
-1737 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 700.454 512.306 709.477]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.9.3.1) >>
->> endobj
-1738 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 686.905 512.306 695.928]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.9.3.2) >>
->> endobj
-1739 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 673.356 512.306 682.379]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.9.3.3) >>
->> endobj
-1740 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 659.807 512.306 668.829]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.9.3.4) >>
->> endobj
-1741 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 646.257 512.306 655.28]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.9.3.5) >>
->> endobj
-1742 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 632.708 512.306 641.731]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.9.3.6) >>
->> endobj
-1743 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 619.159 512.306 628.182]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.9.3.7) >>
->> endobj
-1744 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 605.61 512.306 614.633]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.9.3.8) >>
->> endobj
-1745 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 592.061 512.306 601.083]
-/Subtype /Link
-/A << /S /GoTo /D (section.9.4) >>
->> endobj
-1746 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 578.511 512.306 587.534]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.9.4.1) >>
->> endobj
-1747 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 564.962 512.306 573.985]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.9.4.2) >>
->> endobj
-1748 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 551.413 512.306 560.436]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.9.4.3) >>
->> endobj
-1749 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 537.864 512.306 546.887]
-/Subtype /Link
-/A << /S /GoTo /D (section.9.5) >>
->> endobj
-1750 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 524.315 512.306 533.337]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.9.5.1) >>
->> endobj
-1751 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 510.765 512.306 519.788]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.9.5.2) >>
->> endobj
-1752 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 497.216 512.306 506.239]
-/Subtype /Link
-/A << /S /GoTo /D (section.9.6) >>
->> endobj
-1753 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 483.667 512.306 492.69]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.9.6.1) >>
->> endobj
-1754 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 470.118 512.306 479.141]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.9.6.2) >>
->> endobj
-1755 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 456.569 512.306 465.591]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.9.6.3) >>
->> endobj
-1756 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 443.019 512.306 452.042]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.9.6.3.1) >>
->> endobj
-1757 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [498.314 418.561 512.306 428.129]
-/Subtype /Link
-/A << /S /GoTo /D (chapter.10) >>
->> endobj
-1758 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 405.012 512.306 414.035]
-/Subtype /Link
-/A << /S /GoTo /D (section.10.1) >>
->> endobj
-1759 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 391.463 512.306 400.486]
-/Subtype /Link
-/A << /S /GoTo /D (section.10.2) >>
->> endobj
-1760 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 377.914 512.306 386.936]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.10.2.1) >>
->> endobj
-1761 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 364.364 512.306 373.387]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.10.2.2) >>
->> endobj
-1762 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 350.815 512.306 359.838]
-/Subtype /Link
-/A << /S /GoTo /D (section.10.3) >>
->> endobj
-1763 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 337.266 512.306 346.289]
-/Subtype /Link
-/A << /S /GoTo /D (section.10.4) >>
->> endobj
-1764 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 323.717 512.306 332.74]
-/Subtype /Link
-/A << /S /GoTo /D (section.10.5) >>
->> endobj
-1765 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 310.168 512.306 319.19]
-/Subtype /Link
-/A << /S /GoTo /D (section.10.6) >>
->> endobj
-1766 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 296.618 512.306 305.641]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.10.6.1) >>
->> endobj
-1767 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 283.069 512.306 292.092]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.10.6.2) >>
->> endobj
-1768 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 269.52 512.306 278.543]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.10.6.3) >>
->> endobj
-1769 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 255.971 512.306 264.994]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.10.6.4) >>
->> endobj
-1770 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 242.422 512.306 251.444]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.10.6.5) >>
->> endobj
-1771 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 228.872 512.306 237.895]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.10.6.5.1) >>
->> endobj
-1772 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 215.323 512.306 224.346]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.10.6.5.2) >>
->> endobj
-1773 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 201.774 512.306 210.797]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.10.6.6) >>
->> endobj
-1774 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 188.225 512.306 197.248]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.10.6.7) >>
->> endobj
-1775 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 174.676 512.306 183.698]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.10.6.8) >>
->> endobj
-1776 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 161.126 512.306 170.149]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.10.6.9) >>
->> endobj
-1777 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 147.577 512.306 156.6]
-/Subtype /Link
-/A << /S /GoTo /D (section.10.7) >>
->> endobj
-1778 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 134.028 512.306 143.051]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.10.7.1) >>
->> endobj
-1779 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 120.479 512.306 129.502]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.10.7.2) >>
->> endobj
-1780 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 106.93 512.306 115.952]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.10.7.3) >>
->> endobj
-1781 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 93.38 512.306 102.403]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.10.7.4) >>
->> endobj
-1782 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 79.831 512.306 88.854]
-/Subtype /Link
-/A << /S /GoTo /D (section.10.8) >>
->> endobj
-1732 0 obj <<
-/D [1730 0 R /XYZ 85.039 786.531 null]
->> endobj
-1729 0 obj <<
-/Font << /F62 1689 0 R /F20 1617 0 R /F15 1628 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-1785 0 obj <<
-/Length 2200
-/Filter /FlateDecode
->>
-stream
-x\KoFWT,$wOEj7&p#.@KLDU>wf_$&~HmY0`Q$m3cI>\~C7?Y f^>3 ee
-O)$[|({72—…ïòOG??T5{.7aX_]'_CsHnbZw0ys>I8q~)<8/8PSu,zu `8ml~mRM,|W^}`VWw~DguC
-&"%AHQ>cir.gpj)UgY
-
-){I4M?[3j RP5̓ "Ðá%7P
-A*:|V88{wsK|`]
-;*Y J4p,ZX+2cn7h!B930!J/zlZ-Rmj*"F1#h&^:
-F-TWkt?9
-aeGz.BLN?)UiUX {v!vl:p~! iUt'Rj3~f) xb@q.6j<fW*{R9_ L 0l Xg"?7V9' Mzf7S\H4U]%uKF}Wab<D^0W0VMG>2*Y<`ÌþŠ‘Ìvä“ĶZ q'8kO{1|N?D{oD{(ST"-v SQXD $@Duo4e:%85o@!u$@lf;)iS9%2KtcDA{'lYuB WzK2 /8wp08|"]2~wc_6m/
-Q|=s#KI*M'M<?DB}yS;iGz
-Q7(8¢¬OyRY:mO7dTA~/LlöÃöwžÕxíðº2Æ]‹Û¿µ¾—‘ßÿãÔöendstream
-endobj
-1784 0 obj <<
-/Type /Page
-/Contents 1785 0 R
-/Resources 1783 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 1836 0 R
-/Annots [ 1787 0 R 1788 0 R 1789 0 R 1790 0 R 1791 0 R 1792 0 R 1793 0 R 1794 0 R 1795 0 R 1796 0 R 1797 0 R 1798 0 R 1799 0 R 1800 0 R 1801 0 R 1802 0 R 1803 0 R 1804 0 R 1805 0 R 1806 0 R 1807 0 R 1808 0 R 1809 0 R 1810 0 R 1811 0 R 1812 0 R 1813 0 R 1814 0 R 1815 0 R 1816 0 R 1817 0 R 1818 0 R 1819 0 R 1820 0 R 1821 0 R 1822 0 R 1823 0 R 1824 0 R 1825 0 R 1826 0 R 1827 0 R 1828 0 R 1829 0 R 1830 0 R 1831 0 R 1832 0 R 1833 0 R 1834 0 R 1835 0 R ]
->> endobj
-1787 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [498.314 754.651 512.306 764.219]
-/Subtype /Link
-/A << /S /GoTo /D (chapter.11) >>
->> endobj
-1788 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 741.102 512.306 750.125]
-/Subtype /Link
-/A << /S /GoTo /D (section.11.1) >>
->> endobj
-1789 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 727.553 512.306 736.575]
-/Subtype /Link
-/A << /S /GoTo /D (section.11.2) >>
->> endobj
-1790 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 714.003 512.306 723.026]
-/Subtype /Link
-/A << /S /GoTo /D (section.11.3) >>
->> endobj
-1791 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 700.454 512.306 709.477]
-/Subtype /Link
-/A << /S /GoTo /D (section.11.4) >>
->> endobj
-1792 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 686.905 512.306 695.928]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.11.4.1) >>
->> endobj
-1793 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 673.356 512.306 682.379]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.11.4.2) >>
->> endobj
-1794 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 659.807 512.306 668.829]
-/Subtype /Link
-/A << /S /GoTo /D (section.11.5) >>
->> endobj
-1795 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 646.257 512.306 655.28]
-/Subtype /Link
-/A << /S /GoTo /D (section.11.6) >>
->> endobj
-1796 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 632.708 512.306 641.731]
-/Subtype /Link
-/A << /S /GoTo /D (section.11.7) >>
->> endobj
-1797 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [498.314 608.25 512.306 617.818]
-/Subtype /Link
-/A << /S /GoTo /D (chapter.12) >>
->> endobj
-1798 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [498.314 583.792 512.306 593.36]
-/Subtype /Link
-/A << /S /GoTo /D (chapter.13) >>
->> endobj
-1799 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 570.242 512.306 579.265]
-/Subtype /Link
-/A << /S /GoTo /D (section.13.1) >>
->> endobj
-1800 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 556.693 512.306 565.716]
-/Subtype /Link
-/A << /S /GoTo /D (section.13.2) >>
->> endobj
-1801 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 543.144 512.306 552.167]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.13.2.1) >>
->> endobj
-1802 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 529.595 512.306 538.618]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.13.2.2) >>
->> endobj
-1803 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 516.046 512.306 525.068]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.13.2.3) >>
->> endobj
-1804 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 502.496 512.306 511.519]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.13.2.4) >>
->> endobj
-1805 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 488.947 512.306 497.97]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.13.2.5) >>
->> endobj
-1806 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 475.398 512.306 484.421]
-/Subtype /Link
-/A << /S /GoTo /D (section.13.3) >>
->> endobj
-1807 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 461.849 512.306 470.872]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.13.3.1) >>
->> endobj
-1808 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 448.3 512.306 457.322]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.13.3.2) >>
->> endobj
-1809 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 434.75 512.306 443.773]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.13.3.3) >>
->> endobj
-1810 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 421.201 512.306 430.224]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.13.3.4) >>
->> endobj
-1811 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 407.652 512.306 416.675]
-/Subtype /Link
-/A << /S /GoTo /D (section.13.4) >>
->> endobj
-1812 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 394.103 512.306 403.126]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.13.4.1) >>
->> endobj
-1813 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 380.554 512.306 389.576]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.13.4.2) >>
->> endobj
-1814 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 367.004 512.306 376.027]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.13.4.3) >>
->> endobj
-1815 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 353.455 512.306 362.478]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.13.4.4) >>
->> endobj
-1816 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 339.906 512.306 348.929]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.13.4.5) >>
->> endobj
-1817 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 326.357 512.306 335.38]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.13.4.6) >>
->> endobj
-1818 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 312.808 512.306 321.83]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.13.4.7) >>
->> endobj
-1819 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 299.258 512.306 308.281]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.13.4.8) >>
->> endobj
-1820 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 285.709 512.306 294.732]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.13.4.9) >>
->> endobj
-1821 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [498.314 261.251 512.306 270.819]
-/Subtype /Link
-/A << /S /GoTo /D (chapter.14) >>
->> endobj
-1822 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 247.702 512.306 256.725]
-/Subtype /Link
-/A << /S /GoTo /D (section.14.1) >>
->> endobj
-1823 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 234.153 512.306 243.175]
-/Subtype /Link
-/A << /S /GoTo /D (section.14.2) >>
->> endobj
-1824 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 220.603 512.306 229.626]
-/Subtype /Link
-/A << /S /GoTo /D (section.14.3) >>
->> endobj
-1825 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 207.054 512.306 216.077]
-/Subtype /Link
-/A << /S /GoTo /D (section.14.4) >>
->> endobj
-1826 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 193.505 512.306 202.528]
-/Subtype /Link
-/A << /S /GoTo /D (section.14.5) >>
->> endobj
-1827 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [499.405 179.956 512.306 188.979]
-/Subtype /Link
-/A << /S /GoTo /D (section.14.6) >>
->> endobj
-1828 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 166.407 512.306 175.429]
-/Subtype /Link
-/A << /S /GoTo /D (section.14.7) >>
->> endobj
-1829 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 152.857 512.306 161.88]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.14.7.1) >>
->> endobj
-1830 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 139.308 512.306 148.331]
-/Subtype /Link
-/A << /S /GoTo /D (section.14.8) >>
->> endobj
-1831 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 125.759 512.306 134.782]
-/Subtype /Link
-/A << /S /GoTo /D (section.14.9) >>
->> endobj
-1832 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 112.21 512.306 121.233]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.14.9.1) >>
->> endobj
-1833 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 98.661 512.306 107.683]
-/Subtype /Link
-/A << /S /GoTo /D (section.14.10) >>
->> endobj
-1834 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 85.111 512.306 94.134]
-/Subtype /Link
-/A << /S /GoTo /D (section.14.11) >>
->> endobj
-1835 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 71.562 512.306 80.585]
-/Subtype /Link
-/A << /S /GoTo /D (section.14.12) >>
->> endobj
-1786 0 obj <<
-/D [1784 0 R /XYZ 85.039 786.531 null]
->> endobj
-1783 0 obj <<
-/Font << /F62 1689 0 R /F20 1617 0 R /F15 1628 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-1839 0 obj <<
-/Length 2113
-/Filter /FlateDecode
->>
-stream
-x\rH}+7`YI:oÀåTe K2LE $|;`*UA8gtO+v?vwLmwMhCeV7{m =S7m6(Qt>rLR|ov eoeACMQuk-Z]WG2}c&u!/"_d;f(`k,;GOaIoW.8c*\t <?:-d(]%R6 !~myGg1$&+WKs6+Xmg56
-.AU2"b` spa(58pp(D|9 ]'AFRs^  Ò!]é.€¼eŽ˜mÚ^° Iv#FQ%VTFu?8v[f:Y])q(+ sx'aR <Y |7* BWP2FEnxq_" @ XO=:G0;DH(t8 /3U\tHz*H(,y6)5dBP^E`
-Cg')v*!F`iC/ru\aDqc?5 )ATNU(J<8BO-mkgi.K9"%b1k+3)!7|D<y1#<-&Z$EUynRC?bcCcèë˜`ŒÁ
-vR OLMTD$6HyJRi g33=U_'y?~,CUF X T~_*MI{853axce0c;7mry;
-W XSc*EV52[[9gyUX0i:5,>Y.Jz3^9kSwP/MyY+Iz3 ono%I5bE/3 N_t =p}c^5<BY3>OBUaF6FW1vÙm%ªßPVX, 'd(Rv&z){C=sN?Z;T3JowH^N,s+E<Km%Dz<gd%.P{&P*Gu X+&jjYMBXv/)OL7-*cH09rFA%k@%uw RvyXjW.#
-vv?{[&_(vBGo M3<>T7Sy[Kw1DD2<)0U{|\Ej} {rB;[}V'QAPQp>Yj~S$'5S&=
-{
-endobj
-1838 0 obj <<
-/Type /Page
-/Contents 1839 0 R
-/Resources 1837 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 1836 0 R
-/Annots [ 1841 0 R 1842 0 R 1843 0 R 1844 0 R 1845 0 R 1846 0 R 1847 0 R 1848 0 R 1849 0 R 1850 0 R 1851 0 R 1852 0 R 1853 0 R 1854 0 R 1855 0 R 1856 0 R 1857 0 R 1858 0 R 1859 0 R 1860 0 R 1861 0 R 1862 0 R 1863 0 R 1864 0 R 1865 0 R 1866 0 R 1867 0 R 1868 0 R 1869 0 R 1870 0 R 1871 0 R 1872 0 R 1873 0 R 1874 0 R 1875 0 R 1876 0 R 1877 0 R 1878 0 R 1879 0 R 1880 0 R 1881 0 R 1882 0 R 1883 0 R 1884 0 R 1885 0 R ]
->> endobj
-1841 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [492.314 754.651 512.306 764.219]
-/Subtype /Link
-/A << /S /GoTo /D (chapter.15) >>
->> endobj
-1842 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 741.102 512.306 750.125]
-/Subtype /Link
-/A << /S /GoTo /D (section.15.1) >>
->> endobj
-1843 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 727.553 512.306 736.575]
-/Subtype /Link
-/A << /S /GoTo /D (section.15.2) >>
->> endobj
-1844 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 714.003 512.306 723.026]
-/Subtype /Link
-/A << /S /GoTo /D (section.15.3) >>
->> endobj
-1845 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 700.454 512.306 709.477]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.15.3.1) >>
->> endobj
-1846 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 686.905 512.306 695.928]
-/Subtype /Link
-/A << /S /GoTo /D (section.15.4) >>
->> endobj
-1847 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 673.356 512.306 682.379]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.15.4.1) >>
->> endobj
-1848 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 659.807 512.306 668.829]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.15.4.2) >>
->> endobj
-1849 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 646.257 512.306 655.28]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.15.4.3) >>
->> endobj
-1850 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 632.708 512.306 641.731]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.15.4.4) >>
->> endobj
-1851 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 619.159 512.306 628.182]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.15.4.5) >>
->> endobj
-1852 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 605.61 512.306 614.633]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.15.4.6) >>
->> endobj
-1853 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 592.061 512.306 601.083]
-/Subtype /Link
-/A << /S /GoTo /D (section.15.5) >>
->> endobj
-1854 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 578.511 512.306 587.534]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.15.5.1) >>
->> endobj
-1855 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 564.962 512.306 573.985]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.15.5.2) >>
->> endobj
-1856 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 551.413 512.306 560.436]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.15.5.3) >>
->> endobj
-1857 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 537.864 512.306 546.887]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.15.5.3.1) >>
->> endobj
-1858 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 510.765 512.306 519.788]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.15.5.3.2) >>
->> endobj
-1859 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 497.216 512.306 506.239]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.15.5.3.3) >>
->> endobj
-1860 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 483.667 512.306 492.69]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.15.5.3.4) >>
->> endobj
-1861 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 470.118 512.306 479.141]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.15.5.3.5) >>
->> endobj
-1862 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 456.569 512.306 465.591]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.15.5.3.6) >>
->> endobj
-1863 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 443.019 512.306 452.042]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.15.5.3.7) >>
->> endobj
-1864 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 429.47 512.306 438.493]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.15.5.3.8) >>
->> endobj
-1865 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 415.921 512.306 424.944]
-/Subtype /Link
-/A << /S /GoTo /D (section.15.6) >>
->> endobj
-1866 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 402.372 512.306 411.395]
-/Subtype /Link
-/A << /S /GoTo /D (section.15.7) >>
->> endobj
-1867 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [492.314 377.914 512.306 387.482]
-/Subtype /Link
-/A << /S /GoTo /D (chapter.16) >>
->> endobj
-1868 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 364.364 512.306 373.387]
-/Subtype /Link
-/A << /S /GoTo /D (section.16.1) >>
->> endobj
-1869 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 350.815 512.306 359.838]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.16.1.1) >>
->> endobj
-1870 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 337.266 512.306 346.289]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.16.1.1.1) >>
->> endobj
-1871 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 323.717 512.306 332.74]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.16.1.1.2) >>
->> endobj
-1872 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 310.168 512.306 319.19]
-/Subtype /Link
-/A << /S /GoTo /D (section.16.2) >>
->> endobj
-1873 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 296.618 512.306 305.641]
-/Subtype /Link
-/A << /S /GoTo /D (section.16.3) >>
->> endobj
-1874 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 283.069 512.306 292.092]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.16.3.1) >>
->> endobj
-1875 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [492.314 258.611 512.306 268.179]
-/Subtype /Link
-/A << /S /GoTo /D (chapter.17) >>
->> endobj
-1876 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 245.062 512.306 254.084]
-/Subtype /Link
-/A << /S /GoTo /D (section.17.1) >>
->> endobj
-1877 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 231.512 512.306 240.535]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.17.1.1) >>
->> endobj
-1878 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 217.963 512.306 226.986]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.17.1.2) >>
->> endobj
-1879 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 204.414 512.306 213.437]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.17.1.2.1) >>
->> endobj
-1880 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 190.865 512.306 199.888]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.17.1.3) >>
->> endobj
-1881 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 177.316 512.306 186.338]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.17.1.3.1) >>
->> endobj
-1882 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 163.766 512.306 172.789]
-/Subtype /Link
-/A << /S /GoTo /D (section.17.2) >>
->> endobj
-1883 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 150.217 512.306 159.24]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.17.2.1) >>
->> endobj
-1884 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 136.668 512.306 145.691]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.17.2.2) >>
->> endobj
-1885 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 123.119 512.306 132.142]
-/Subtype /Link
-/A << /S /GoTo /D (section.17.3) >>
->> endobj
-1840 0 obj <<
-/D [1838 0 R /XYZ 85.039 786.531 null]
->> endobj
-1837 0 obj <<
-/Font << /F62 1689 0 R /F20 1617 0 R /F15 1628 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-1888 0 obj <<
-/Length 2242
-/Filter /FlateDecode
->>
-stream
-x\[sH~WY}i*d<[NeyAy~2È6,ÀIPI;ND1
-Fi+j`C36#)p~I$
-Uk}Jg>uh(:k_I\2[E(`=iZw1smy.<Z(L^{!p"$axpu$(:$-N84`fF.Y:\]9K|6?<
-?D<5)xy*sAC|zkLZ]mOôÒ)ªßUjDbcdofJ3lM3I3XsXE
-If7FX#Xsg!5]F\c10;jR/
-3&qh~p@_
- MQj3 SNbk$WVzV}0.z{Z#Xo!+a/O m|/ah3!_
-6?XSHLYi œ>ˆŒú„AF 5 s=C+Q5I)eH;P@yijyV[rIP5
-sJ^1XH#ciS{cjc, gFg6fHM$
-vRn98ϮSL*hWZ^WF5Gch;SBY1wM8tyF`W'y[\5yzp=uSrM7k<fXU
-H3c"w\$t(s1+0.
-rHrHzBIbLr,bp6L{up°—Ž¿'m~YS -5}
-endobj
-1887 0 obj <<
-/Type /Page
-/Contents 1888 0 R
-/Resources 1886 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 1836 0 R
-/Annots [ 1890 0 R 1891 0 R 1892 0 R 1893 0 R 1894 0 R 1895 0 R 1896 0 R 1897 0 R 1898 0 R 1899 0 R 1900 0 R 1901 0 R 1902 0 R 1903 0 R 1904 0 R 1905 0 R 1906 0 R 1907 0 R 1908 0 R 1909 0 R 1910 0 R 1911 0 R 1912 0 R 1913 0 R 1914 0 R 1915 0 R 1916 0 R 1917 0 R 1918 0 R 1919 0 R 1920 0 R 1921 0 R 1922 0 R 1923 0 R 1924 0 R 1925 0 R 1926 0 R 1927 0 R 1928 0 R 1929 0 R 1930 0 R 1931 0 R 1932 0 R 1933 0 R 1934 0 R 1935 0 R 1936 0 R ]
->> endobj
-1890 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [492.314 754.651 512.306 764.219]
-/Subtype /Link
-/A << /S /GoTo /D (chapter.18) >>
->> endobj
-1891 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 741.102 512.306 750.125]
-/Subtype /Link
-/A << /S /GoTo /D (section.18.1) >>
->> endobj
-1892 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 727.553 512.306 736.575]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.18.1.1) >>
->> endobj
-1893 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 714.003 512.306 723.026]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.18.1.1.1) >>
->> endobj
-1894 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 700.454 512.306 709.477]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.18.1.1.2) >>
->> endobj
-1895 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 673.356 512.306 682.379]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.18.1.1.3) >>
->> endobj
-1896 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 659.807 512.306 668.829]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.18.1.1.4) >>
->> endobj
-1897 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 646.257 512.306 655.28]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.18.1.2) >>
->> endobj
-1898 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 632.708 512.306 641.731]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.18.1.2.1) >>
->> endobj
-1899 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 619.159 512.306 628.182]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.18.1.2.2) >>
->> endobj
-1900 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 605.61 512.306 614.633]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.18.1.2.3) >>
->> endobj
-1901 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 578.511 512.306 587.534]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.18.1.3) >>
->> endobj
-1902 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 564.962 512.306 573.985]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.18.1.4) >>
->> endobj
-1903 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 551.413 512.306 560.436]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.18.1.4.1) >>
->> endobj
-1904 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 537.864 512.306 546.887]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.18.1.4.2) >>
->> endobj
-1905 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 524.315 512.306 533.337]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.18.1.4.3) >>
->> endobj
-1906 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 510.765 512.306 519.788]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.18.1.4.4) >>
->> endobj
-1907 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 497.216 512.306 506.239]
-/Subtype /Link
-/A << /S /GoTo /D (section.18.2) >>
->> endobj
-1908 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 483.667 512.306 492.69]
-/Subtype /Link
-/A << /S /GoTo /D (section.18.3) >>
->> endobj
-1909 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 470.118 512.306 479.141]
-/Subtype /Link
-/A << /S /GoTo /D (section.18.4) >>
->> endobj
-1910 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 456.569 512.306 465.591]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.18.4.1) >>
->> endobj
-1911 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 443.019 512.306 452.042]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.18.4.1.1) >>
->> endobj
-1912 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 429.47 512.306 438.493]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.18.4.2) >>
->> endobj
-1913 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 415.921 512.306 424.944]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.18.4.3) >>
->> endobj
-1914 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [492.314 391.463 512.306 401.031]
-/Subtype /Link
-/A << /S /GoTo /D (chapter.19) >>
->> endobj
-1915 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 377.914 512.306 386.936]
-/Subtype /Link
-/A << /S /GoTo /D (section.19.1) >>
->> endobj
-1916 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 364.364 512.306 373.387]
-/Subtype /Link
-/A << /S /GoTo /D (section.19.2) >>
->> endobj
-1917 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 350.815 512.306 359.838]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.19.2.1) >>
->> endobj
-1918 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 323.717 512.306 332.74]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.19.2.2) >>
->> endobj
-1919 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 310.168 512.306 319.19]
-/Subtype /Link
-/A << /S /GoTo /D (section.19.3) >>
->> endobj
-1920 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 296.618 512.306 305.641]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.19.3.1) >>
->> endobj
-1921 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 283.069 512.306 292.092]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.19.3.2) >>
->> endobj
-1922 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [492.314 258.611 512.306 268.179]
-/Subtype /Link
-/A << /S /GoTo /D (chapter.20) >>
->> endobj
-1923 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 245.062 512.306 254.084]
-/Subtype /Link
-/A << /S /GoTo /D (section.20.1) >>
->> endobj
-1924 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 231.512 512.306 240.535]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.20.1.1) >>
->> endobj
-1925 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 217.963 512.306 226.986]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.20.1.2) >>
->> endobj
-1926 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 204.414 512.306 213.437]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.20.1.2.1) >>
->> endobj
-1927 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 190.865 512.306 199.888]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.20.1.2.2) >>
->> endobj
-1928 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 177.316 512.306 186.338]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.20.1.2.3) >>
->> endobj
-1929 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 163.766 512.306 172.789]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.20.1.2.4) >>
->> endobj
-1930 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 150.217 512.306 159.24]
-/Subtype /Link
-/A << /S /GoTo /D (section.20.2) >>
->> endobj
-1931 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [492.314 125.759 512.306 135.327]
-/Subtype /Link
-/A << /S /GoTo /D (chapter.21) >>
->> endobj
-1932 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 112.21 512.306 121.233]
-/Subtype /Link
-/A << /S /GoTo /D (section.21.1) >>
->> endobj
-1933 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 98.661 512.306 107.683]
-/Subtype /Link
-/A << /S /GoTo /D (section.21.2) >>
->> endobj
-1934 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 85.111 512.306 94.134]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.21.2.1) >>
->> endobj
-1935 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 71.562 512.306 80.585]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.21.2.2) >>
->> endobj
-1936 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 58.013 512.306 67.036]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.21.2.3) >>
->> endobj
-1889 0 obj <<
-/D [1887 0 R /XYZ 85.039 786.531 null]
->> endobj
-1886 0 obj <<
-/Font << /F62 1689 0 R /F20 1617 0 R /F15 1628 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-1939 0 obj <<
-/Length 1980
-/Filter /FlateDecode
->>
-stream
-x\rJ,B,TSyY •A}n OX8U=AT[i&-}G=ks>zo &<SonthYwtk><} KjOZgzcm>^,n@xn)qN $Q}+5us? ^q`}i Y~IyQW0DS';_z
-u ]W8104>&/. ]I&@d_~FY +}QZ
-/vF/=zxMHE2jrir'vh#
-:"FRQ-t :R[p`mAv?ym^brxl3 vCc?x.!<mI8uQzk> 16rTM(>S,I
-L{p.^myFFxUr` FiV%tJ6<B]"k+'JP`E<B99WL6h{plp+³+}T9f:5iR(rHeWqYNxA\b*J!#o0h%dd@*-bc+% B8[ #\R 6+RSJ=q }QX|dTR;o"j9{\I@_c)Q4QiA #=1qz16oZn.R[R5McM
-^yDUJjA^peU5<W&in!@XJn[32N2Qu6W(G6K<Wf>8~,osa8endstream
-endobj
-1938 0 obj <<
-/Type /Page
-/Contents 1939 0 R
-/Resources 1937 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 1836 0 R
-/Annots [ 1941 0 R 1942 0 R 1943 0 R 1944 0 R 1945 0 R 1946 0 R 1947 0 R 1948 0 R 1949 0 R 1950 0 R 1951 0 R 1952 0 R 1953 0 R 1954 0 R 1955 0 R 1956 0 R 1957 0 R 1958 0 R 1959 0 R 1960 0 R 1961 0 R 1962 0 R 1963 0 R 1964 0 R 1965 0 R 1966 0 R 1967 0 R 1968 0 R 1969 0 R 1970 0 R 1971 0 R 1972 0 R 1973 0 R 1974 0 R 1975 0 R 1976 0 R 1977 0 R 1978 0 R 1979 0 R 1980 0 R 1981 0 R 1982 0 R 1983 0 R 1984 0 R 1985 0 R 1986 0 R ]
->> endobj
-1941 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 754.651 512.306 763.674]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.21.2.4) >>
->> endobj
-1942 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 741.102 512.306 750.125]
-/Subtype /Link
-/A << /S /GoTo /D (section.21.3) >>
->> endobj
-1943 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 727.553 512.306 736.575]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.21.3.1) >>
->> endobj
-1944 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 714.003 512.306 723.026]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.21.3.2) >>
->> endobj
-1945 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [492.314 689.545 512.306 699.113]
-/Subtype /Link
-/A << /S /GoTo /D (chapter.22) >>
->> endobj
-1946 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 675.996 512.306 685.019]
-/Subtype /Link
-/A << /S /GoTo /D (section.22.1) >>
->> endobj
-1947 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 662.447 512.306 671.469]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.22.1.1) >>
->> endobj
-1948 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [492.314 637.988 512.306 647.557]
-/Subtype /Link
-/A << /S /GoTo /D (chapter.23) >>
->> endobj
-1949 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 624.439 512.306 633.462]
-/Subtype /Link
-/A << /S /GoTo /D (section.23.1) >>
->> endobj
-1950 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 610.89 512.306 619.913]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.23.1.1) >>
->> endobj
-1951 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 597.341 512.306 606.364]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.23.1.2) >>
->> endobj
-1952 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 583.792 512.306 592.814]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.23.1.3) >>
->> endobj
-1953 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 570.242 512.306 579.265]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.23.1.4) >>
->> endobj
-1954 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 556.693 512.306 565.716]
-/Subtype /Link
-/A << /S /GoTo /D (section.23.2) >>
->> endobj
-1955 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 543.144 512.306 552.167]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.23.2.1) >>
->> endobj
-1956 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 529.595 512.306 538.618]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.23.2.2) >>
->> endobj
-1957 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 516.046 512.306 525.068]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.23.2.3) >>
->> endobj
-1958 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 502.496 512.306 511.519]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.23.2.4) >>
->> endobj
-1959 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 488.947 512.306 497.97]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.23.2.5) >>
->> endobj
-1960 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [492.314 464.489 512.306 474.057]
-/Subtype /Link
-/A << /S /GoTo /D (chapter.24) >>
->> endobj
-1961 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 450.94 512.306 459.963]
-/Subtype /Link
-/A << /S /GoTo /D (section.24.1) >>
->> endobj
-1962 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 437.39 512.306 446.413]
-/Subtype /Link
-/A << /S /GoTo /D (section.24.2) >>
->> endobj
-1963 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 423.841 512.306 432.864]
-/Subtype /Link
-/A << /S /GoTo /D (section.24.3) >>
->> endobj
-1964 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 410.292 512.306 419.315]
-/Subtype /Link
-/A << /S /GoTo /D (section.24.4) >>
->> endobj
-1965 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 396.743 512.306 405.766]
-/Subtype /Link
-/A << /S /GoTo /D (section.24.5) >>
->> endobj
-1966 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 383.194 512.306 392.217]
-/Subtype /Link
-/A << /S /GoTo /D (section.24.6) >>
->> endobj
-1967 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 369.645 512.306 378.667]
-/Subtype /Link
-/A << /S /GoTo /D (section.24.7) >>
->> endobj
-1968 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [492.314 345.186 512.306 354.754]
-/Subtype /Link
-/A << /S /GoTo /D (chapter.25) >>
->> endobj
-1969 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 331.637 512.306 340.66]
-/Subtype /Link
-/A << /S /GoTo /D (section.25.1) >>
->> endobj
-1970 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 318.088 512.306 327.111]
-/Subtype /Link
-/A << /S /GoTo /D (section.25.2) >>
->> endobj
-1971 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 304.539 512.306 313.561]
-/Subtype /Link
-/A << /S /GoTo /D (section.25.3) >>
->> endobj
-1972 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 290.989 512.306 300.012]
-/Subtype /Link
-/A << /S /GoTo /D (section.25.4) >>
->> endobj
-1973 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [492.314 266.531 512.306 276.099]
-/Subtype /Link
-/A << /S /GoTo /D (chapter.26) >>
->> endobj
-1974 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 252.982 512.306 262.005]
-/Subtype /Link
-/A << /S /GoTo /D (section.26.1) >>
->> endobj
-1975 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 239.433 512.306 248.456]
-/Subtype /Link
-/A << /S /GoTo /D (section.26.2) >>
->> endobj
-1976 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 225.883 512.306 234.906]
-/Subtype /Link
-/A << /S /GoTo /D (section.26.3) >>
->> endobj
-1977 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 212.334 512.306 221.357]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.26.3.1) >>
->> endobj
-1978 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 198.785 512.306 207.808]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.26.3.2) >>
->> endobj
-1979 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 185.236 512.306 194.259]
-/Subtype /Link
-/A << /S /GoTo /D (section.26.4) >>
->> endobj
-1980 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 171.687 512.306 180.71]
-/Subtype /Link
-/A << /S /GoTo /D (section.26.5) >>
->> endobj
-1981 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [490.587 133.194 512.306 143.488]
-/Subtype /Link
-/A << /S /GoTo /D (part.4) >>
->> endobj
-1982 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [492.314 108.735 512.306 118.303]
-/Subtype /Link
-/A << /S /GoTo /D (chapter.27) >>
->> endobj
-1983 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 95.186 512.306 104.209]
-/Subtype /Link
-/A << /S /GoTo /D (section.27.1) >>
->> endobj
-1984 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 81.637 512.306 90.66]
-/Subtype /Link
-/A << /S /GoTo /D (section.27.2) >>
->> endobj
-1985 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 68.088 512.306 77.11]
-/Subtype /Link
-/A << /S /GoTo /D (section.27.3) >>
->> endobj
-1986 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 54.538 512.306 63.561]
-/Subtype /Link
-/A << /S /GoTo /D (section.27.4) >>
->> endobj
-1940 0 obj <<
-/D [1938 0 R /XYZ 85.039 786.531 null]
->> endobj
-1937 0 obj <<
-/Font << /F62 1689 0 R /F15 1628 0 R /F20 1617 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-1989 0 obj <<
-/Length 2082
-/Filter /FlateDecode
->>
-stream
-x\YsH~Wf9t¶w§r°ÆΦ*Ƀ
-Ðq€ Ã:ª ;'Y0Z k:f  8I88\ixL<)T
-0"0!4QvN I]lH%
-`Raspc +hE(P][{{hC$Jf9<^KRK9<yC*ADH w6(4}`$4Pa\DKGn-=3,k38X S4:iSUS*AO
-5N/ @p,{$oQ=O]#fM{42YyFWElq)66 .iI,~;@N_ov:P&A&\8uw=E]P:&]JT8@Fa{v2
-s2|d
-vxh'6nt"Y8Jug%zt<{2 "mor+ B36WefTAE_ 1AX a7M7\@2V{UV(31!vI];hAOTE#W"aóì^%u;wíep]Š²ÿH ³¾ÙKKXbWEbFklY(
-UU)QGE~P*Vk,WBSÐ`„;U%c<9'Mx YWI%6 o'$?{MyB*P!3]p2C{WJ>~Fl' | ;~
-XWJduv SiŠÉw®G
-qu! -RLc2H:wz)F1nUvFmZs%cAL;J@v5]bUVb/&I*d2
-dWD_h1M uR<Le}K{Wlw /ab i@XYvvk.H=6}U>mqr:eFPr^xhb=
-endobj
-1988 0 obj <<
-/Type /Page
-/Contents 1989 0 R
-/Resources 1987 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 1836 0 R
-/Annots [ 1991 0 R 1992 0 R 1993 0 R 1994 0 R 1995 0 R 1996 0 R 1997 0 R 1998 0 R 1999 0 R 2000 0 R 2001 0 R 2002 0 R 2003 0 R 2004 0 R 2005 0 R 2006 0 R 2007 0 R 2008 0 R 2009 0 R 2010 0 R 2011 0 R 2012 0 R 2013 0 R 2014 0 R 2015 0 R 2016 0 R 2017 0 R 2018 0 R 2019 0 R 2020 0 R 2021 0 R 2022 0 R 2023 0 R 2024 0 R 2025 0 R 2026 0 R 2027 0 R 2028 0 R 2029 0 R 2030 0 R 2031 0 R 2032 0 R 2033 0 R 2034 0 R 2035 0 R 2036 0 R ]
->> endobj
-1991 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [492.314 754.651 512.306 764.219]
-/Subtype /Link
-/A << /S /GoTo /D (chapter.28) >>
->> endobj
-1992 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 741.102 512.306 750.125]
-/Subtype /Link
-/A << /S /GoTo /D (section.28.1) >>
->> endobj
-1993 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 714.003 512.306 723.026]
-/Subtype /Link
-/A << /S /GoTo /D (section.28.2) >>
->> endobj
-1994 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 700.454 512.306 709.477]
-/Subtype /Link
-/A << /S /GoTo /D (section.28.3) >>
->> endobj
-1995 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 686.905 512.306 695.928]
-/Subtype /Link
-/A << /S /GoTo /D (section.28.4) >>
->> endobj
-1996 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 673.356 512.306 682.379]
-/Subtype /Link
-/A << /S /GoTo /D (section.28.5) >>
->> endobj
-1997 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [492.314 648.897 512.306 658.466]
-/Subtype /Link
-/A << /S /GoTo /D (chapter.29) >>
->> endobj
-1998 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 635.348 512.306 644.371]
-/Subtype /Link
-/A << /S /GoTo /D (section.29.1) >>
->> endobj
-1999 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 621.799 512.306 630.822]
-/Subtype /Link
-/A << /S /GoTo /D (section.29.2) >>
->> endobj
-2000 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 608.25 512.306 617.273]
-/Subtype /Link
-/A << /S /GoTo /D (section.29.3) >>
->> endobj
-2001 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 594.701 512.306 603.724]
-/Subtype /Link
-/A << /S /GoTo /D (section.29.4) >>
->> endobj
-2002 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 581.151 512.306 590.174]
-/Subtype /Link
-/A << /S /GoTo /D (section.29.5) >>
->> endobj
-2003 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 567.602 512.306 576.625]
-/Subtype /Link
-/A << /S /GoTo /D (section.29.6) >>
->> endobj
-2004 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [490.587 529.109 512.306 539.404]
-/Subtype /Link
-/A << /S /GoTo /D (part.5) >>
->> endobj
-2005 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [492.314 504.651 512.306 514.219]
-/Subtype /Link
-/A << /S /GoTo /D (chapter.30) >>
->> endobj
-2006 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 491.102 512.306 500.124]
-/Subtype /Link
-/A << /S /GoTo /D (section.30.1) >>
->> endobj
-2007 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 477.552 512.306 486.575]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.30.1.1) >>
->> endobj
-2008 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 464.003 512.306 473.026]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.30.1.2) >>
->> endobj
-2009 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 450.454 512.306 459.477]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.30.1.2.1) >>
->> endobj
-2010 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 436.905 512.306 445.928]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.30.1.2.2) >>
->> endobj
-2011 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 423.356 512.306 432.378]
-/Subtype /Link
-/A << /S /GoTo /D (section.30.2) >>
->> endobj
-2012 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 409.806 512.306 418.829]
-/Subtype /Link
-/A << /S /GoTo /D (section.30.3) >>
->> endobj
-2013 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 396.257 512.306 405.28]
-/Subtype /Link
-/A << /S /GoTo /D (section.30.4) >>
->> endobj
-2014 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 382.708 512.306 391.731]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.30.4.1) >>
->> endobj
-2015 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 369.159 512.306 378.182]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.30.4.1.1) >>
->> endobj
-2016 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 355.61 512.306 364.632]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.30.4.1.2) >>
->> endobj
-2017 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 342.06 512.306 351.083]
-/Subtype /Link
-/A << /S /GoTo /D (section.30.5) >>
->> endobj
-2018 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 328.511 512.306 337.534]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.30.5.1) >>
->> endobj
-2019 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 314.962 512.306 323.985]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.30.5.2) >>
->> endobj
-2020 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [492.314 290.504 512.306 300.072]
-/Subtype /Link
-/A << /S /GoTo /D (chapter.31) >>
->> endobj
-2021 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 276.955 512.306 285.977]
-/Subtype /Link
-/A << /S /GoTo /D (section.31.1) >>
->> endobj
-2022 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 263.405 512.306 272.428]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.31.1.1) >>
->> endobj
-2023 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 249.856 512.306 258.879]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.31.1.1.1) >>
->> endobj
-2024 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 236.307 512.306 245.33]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.31.1.1.2) >>
->> endobj
-2025 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 222.758 512.306 231.781]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.31.1.1.3) >>
->> endobj
-2026 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 209.209 512.306 218.231]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.31.1.1.4) >>
->> endobj
-2027 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 195.659 512.306 204.682]
-/Subtype /Link
-/A << /S /GoTo /D (subsubsection.31.1.1.5) >>
->> endobj
-2028 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 182.11 512.306 191.133]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.31.1.2) >>
->> endobj
-2029 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 168.561 512.306 177.584]
-/Subtype /Link
-/A << /S /GoTo /D (section.31.2) >>
->> endobj
-2030 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 155.012 512.306 164.035]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.31.2.1) >>
->> endobj
-2031 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 141.463 512.306 150.485]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.31.2.2) >>
->> endobj
-2032 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [492.314 117.004 512.306 126.573]
-/Subtype /Link
-/A << /S /GoTo /D (chapter.32) >>
->> endobj
-2033 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 103.455 512.306 112.478]
-/Subtype /Link
-/A << /S /GoTo /D (section.32.1) >>
->> endobj
-2034 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 89.906 512.306 98.929]
-/Subtype /Link
-/A << /S /GoTo /D (section.32.2) >>
->> endobj
-2035 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 76.357 512.306 85.379]
-/Subtype /Link
-/A << /S /GoTo /D (section.32.3) >>
->> endobj
-2036 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 62.807 512.306 71.83]
-/Subtype /Link
-/A << /S /GoTo /D (section.32.4) >>
->> endobj
-1990 0 obj <<
-/D [1988 0 R /XYZ 85.039 786.531 null]
->> endobj
-1987 0 obj <<
-/Font << /F62 1689 0 R /F20 1617 0 R /F15 1628 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2039 0 obj <<
-/Length 2007
-/Filter /FlateDecode
->>
-stream
-x\[oH~WV#wJjw'XLi=g.
-c1 AKh ".{Hc3dOobA#3g {S'J.z#&NVD-\c4L5E)@(|^hD j+B&B;4HzQbmaRwW}y}`RKi"u(7Q<eUZ =[KOb ]Hm Z I0X=>u,eM+;/JT8Vlk(ZJ% jNP@n)F$w:kb<l8HTb 5[G!S|1“÷݌¶}ÒR;h)uMmLe 1cdE-S[tKZ8b `.kj#ge?)0Z`^~@}am L3q9br
-pRcQH<}rfo/5^'N@B~XB2Ww`C(8JM6baPqXt! Wz=tyb0/\?I{-2|AYZ=@>"|\X\]v Sa>|vn$}F&ZK8:`20 .!NpbCl0`5
-O6QZwCl JLk5;r)`];\8JnPL%PZsPOc d!tK/?(0Lendstream
-endobj
-2038 0 obj <<
-/Type /Page
-/Contents 2039 0 R
-/Resources 2037 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 1836 0 R
-/Annots [ 2041 0 R 2042 0 R 2043 0 R 2044 0 R 2045 0 R 2046 0 R 2047 0 R 2048 0 R 2049 0 R 2050 0 R 2051 0 R 2052 0 R 2053 0 R 2054 0 R 2055 0 R 2056 0 R 2057 0 R 2058 0 R 2059 0 R 2060 0 R 2061 0 R 2062 0 R 2063 0 R 2064 0 R 2065 0 R 2066 0 R 2067 0 R 2068 0 R 2069 0 R 2070 0 R 2071 0 R 2072 0 R 2073 0 R 2074 0 R 2075 0 R 2076 0 R 2077 0 R 2078 0 R 2079 0 R 2080 0 R 2081 0 R 2082 0 R 2083 0 R 2084 0 R 2085 0 R ]
->> endobj
-2041 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 754.651 512.306 763.674]
-/Subtype /Link
-/A << /S /GoTo /D (section.32.5) >>
->> endobj
-2042 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 741.102 512.306 750.125]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.32.5.1) >>
->> endobj
-2043 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 727.553 512.306 736.575]
-/Subtype /Link
-/A << /S /GoTo /D (section.32.6) >>
->> endobj
-2044 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 714.003 512.306 723.026]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.32.6.1) >>
->> endobj
-2045 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 700.454 512.306 709.477]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.32.6.2) >>
->> endobj
-2046 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [492.314 675.996 512.306 685.564]
-/Subtype /Link
-/A << /S /GoTo /D (chapter.33) >>
->> endobj
-2047 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 662.447 512.306 671.469]
-/Subtype /Link
-/A << /S /GoTo /D (section.33.1) >>
->> endobj
-2048 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 648.897 512.306 657.92]
-/Subtype /Link
-/A << /S /GoTo /D (section.33.2) >>
->> endobj
-2049 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 621.799 512.306 630.822]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.33.2.1) >>
->> endobj
-2050 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 594.701 512.306 603.724]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.33.2.2) >>
->> endobj
-2051 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 567.602 512.306 576.625]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.33.2.3) >>
->> endobj
-2052 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 554.053 512.306 563.076]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.33.2.4) >>
->> endobj
-2053 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 540.504 512.306 549.527]
-/Subtype /Link
-/A << /S /GoTo /D (section.33.3) >>
->> endobj
-2054 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 526.955 512.306 535.978]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.33.3.1) >>
->> endobj
-2055 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 513.406 512.306 522.428]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.33.3.2) >>
->> endobj
-2056 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 499.856 512.306 508.879]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.33.3.3) >>
->> endobj
-2057 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 486.307 512.306 495.33]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.33.3.4) >>
->> endobj
-2058 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 472.758 512.306 481.781]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.33.3.5) >>
->> endobj
-2059 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 459.209 512.306 468.232]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.33.3.6) >>
->> endobj
-2060 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 445.66 512.306 454.682]
-/Subtype /Link
-/A << /S /GoTo /D (section.33.4) >>
->> endobj
-2061 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 432.11 512.306 441.133]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.33.4.1) >>
->> endobj
-2062 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 418.561 512.306 427.584]
-/Subtype /Link
-/A << /S /GoTo /D (section.33.5) >>
->> endobj
-2063 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 405.012 512.306 414.035]
-/Subtype /Link
-/A << /S /GoTo /D (section.33.6) >>
->> endobj
-2064 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [492.314 380.554 512.306 390.122]
-/Subtype /Link
-/A << /S /GoTo /D (chapter.34) >>
->> endobj
-2065 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 367.004 512.306 376.027]
-/Subtype /Link
-/A << /S /GoTo /D (section.34.1) >>
->> endobj
-2066 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 353.455 512.306 362.478]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.34.1.1) >>
->> endobj
-2067 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 339.906 512.306 348.929]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.34.1.2) >>
->> endobj
-2068 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 326.357 512.306 335.38]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.34.1.3) >>
->> endobj
-2069 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 312.808 512.306 321.83]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.34.1.4) >>
->> endobj
-2070 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 299.258 512.306 308.281]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.34.1.5) >>
->> endobj
-2071 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 285.709 512.306 294.732]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.34.1.6) >>
->> endobj
-2072 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 272.16 512.306 281.183]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.34.1.7) >>
->> endobj
-2073 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 258.611 512.306 267.634]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.34.1.8) >>
->> endobj
-2074 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 245.062 512.306 254.084]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.34.1.9) >>
->> endobj
-2075 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 231.512 512.306 240.535]
-/Subtype /Link
-/A << /S /GoTo /D (subsection.34.1.10) >>
->> endobj
-2076 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [492.314 207.054 512.306 216.622]
-/Subtype /Link
-/A << /S /GoTo /D (chapter.35) >>
->> endobj
-2077 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 193.505 512.306 202.528]
-/Subtype /Link
-/A << /S /GoTo /D (section.35.1) >>
->> endobj
-2078 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 179.956 512.306 188.979]
-/Subtype /Link
-/A << /S /GoTo /D (section.35.2) >>
->> endobj
-2079 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 166.407 512.306 175.429]
-/Subtype /Link
-/A << /S /GoTo /D (section.35.3) >>
->> endobj
-2080 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 152.857 512.306 161.88]
-/Subtype /Link
-/A << /S /GoTo /D (section.35.4) >>
->> endobj
-2081 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 139.308 512.306 148.331]
-/Subtype /Link
-/A << /S /GoTo /D (section.35.5) >>
->> endobj
-2082 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 125.759 512.306 134.782]
-/Subtype /Link
-/A << /S /GoTo /D (section.35.6) >>
->> endobj
-2083 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 112.21 512.306 121.233]
-/Subtype /Link
-/A << /S /GoTo /D (section.35.7) >>
->> endobj
-2084 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 98.661 512.306 107.683]
-/Subtype /Link
-/A << /S /GoTo /D (section.35.8) >>
->> endobj
-2085 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [493.95 85.111 512.306 94.134]
-/Subtype /Link
-/A << /S /GoTo /D (section.35.9) >>
->> endobj
-2040 0 obj <<
-/D [2038 0 R /XYZ 85.039 786.531 null]
->> endobj
-2037 0 obj <<
-/Font << /F62 1689 0 R /F15 1628 0 R /F20 1617 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2088 0 obj <<
-/Length 226
-/Filter /FlateDecode
->>
-stream
-xmP;O1 WdL?\*C6p!C*s@SGg2LRM. y)G@ A+?@ eMD5HQ B %mg4$i{}NNg%eud=#@.;|P,nr87
-=Lp. \@(ndhbz MlYendstream
-endobj
-2087 0 obj <<
-/Type /Page
-/Contents 2088 0 R
-/Resources 2086 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2090 0 R
->> endobj
-2089 0 obj <<
-/D [2087 0 R /XYZ 85.039 786.531 null]
->> endobj
-6 0 obj <<
-/D [2087 0 R /XYZ 85.039 547.583 null]
->> endobj
-2086 0 obj <<
-/Font << /F20 1617 0 R /F15 1628 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2093 0 obj <<
-/Length 3344
-/Filter /FlateDecode
->>
-stream
-x]o=0
-:X4)^
-T>$Zb-*OwK>X;/FE:J8/wV~z FnE0Ya^¤áÅ0ˆÜÌ#ŒñüÝõ}à]ž›$áÅü‰0ç«9¾;ƱçLSz0j0 =guX*aFX83\W;]aLu0q?WJ Kf+]N8up8rV%VQ8: A(Wg+`SVBa^U!< K;nA KA\]d42bq2 F(av0sG
-_sPMnDKo (P-a
-HV94/Pwy=Zjc !H*.p"sb8C
-7Dj cZ[cen!0JNC(s–päóº® |¼ynà¦Ù7CI`a)p^W"4g#$kp-(D5WPOy]w)F#Kgt]^oL v>$<j?`pW2Q4]^&j?hk
-e;;ly,|.
-2
-0
-S88;qQ9Qq
-BNz8tBhK4K`^3rfcf]pbl6j-Q`WL\nHK.!} 'hF}i-{?^R0K86l;| g2s@n(.
-*PQyeH9<7 }TD
-`
-4-_rÏñ.¯Ý4­°z©ê†QaGKx+Rn`@~jt Ia#+RJk c* gYq 0Xlby
--6LK9kFLH.EVnSKC:i|={ /hUHR-@hLa9pN#FZwS
-]"{|Xhe}{{zV4
-ha
-} R{@9' k W6"4o±û‚z«sÚ09ºÙ»XX3[<mC` )Z@c_Zu>dBM.oLS-1$Î_x<(^þ›fq,5“““>‹‰òNu|Tua.#2 gõUZ( +$y
-\A2rnu%%eQA /[E+|IqoMlR`tVFQdZPXufV}q'{8#o7vy6_VfqB@BEEty¸~/ΐ’”“òýR,75@RD!)jS2~_Z+j!SQK;.;=Di²x) ÛJ%!}eMBS)^*u'Y4=AEK
-VXRY'u^<Zk 
-IAua¸€mS/~[bzi.Xrbs
-endobj
-2092 0 obj <<
-/Type /Page
-/Contents 2093 0 R
-/Resources 2091 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2090 0 R
->> endobj
-2094 0 obj <<
-/D [2092 0 R /XYZ 85.039 786.531 null]
->> endobj
-2095 0 obj <<
-/D [2092 0 R /XYZ 85.039 766.606 null]
->> endobj
-10 0 obj <<
-/D [2092 0 R /XYZ 85.039 766.606 null]
->> endobj
-2096 0 obj <<
-/D [2092 0 R /XYZ 85.039 676.914 null]
->> endobj
-14 0 obj <<
-/D [2092 0 R /XYZ 85.039 563.765 null]
->> endobj
-2100 0 obj <<
-/D [2092 0 R /XYZ 85.039 534.36 null]
->> endobj
-18 0 obj <<
-/D [2092 0 R /XYZ 85.039 193.665 null]
->> endobj
-2101 0 obj <<
-/D [2092 0 R /XYZ 85.039 164.26 null]
->> endobj
-2091 0 obj <<
-/Font << /F20 1617 0 R /F65 2099 0 R /F15 1628 0 R /F41 2104 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2107 0 obj <<
-/Length 3436
-/Filter /FlateDecode
->>
-stream
-xZWHWqY^,iY)@`69[#v_wKa.<?w4 mGtb;oNvy*g$¹Ž;ñh¶Ùâ7ëò_ïïf?Ÿ}ß·\ûlESvZ><\n(f
-;8p
-I)+GXMya\¾Dyfz+(Rx!/
-` @oxyfZdU}vd,C{DK7 ^3k~C +V$?$_xq_Kl* bE[m]
-A)EZ@. Og1"i#+Id;F(-LD2hDlE!dK%KP}(V0uS<SV<zP]5O I0',Rc&f^l4Z@owMseaK+er7y
-N5V66 Fj%sO!oX_70wB iIV+2W]V.W|[h1k0$M:
-KoUfSXW
-T/?Q]QQ
-XjTL j%)( 1W:6"uEbS@RG7+\W
->+#Sm$| 1oXxDJJQ26[(]wC03<Gj4OvKnS3p 1i/1W #;_gh +: &
-{nv&[G IGiBpzO Y U(HXO5-#g<9((;)A)= %y]b$W[TWi J
->$Mb>. y2]!S Ul@m{B{=a@&{^0Dmxz< 5G_eHSI&T,
-~b\b.Aj80#1_u,wM:o6 ~=.q?I!vu_?s9;IiJP'N9~&}fhaB_Z]=' c/4=Itz'_3i&)e`zCfuFvRzG]d)=*X<){ =?~~bUmq+mB-n~AG]VJ{J]THkk~mJvH8*{[+8r6'-6j2G=kf{hG{6!i4RDN"*>nv4k&4( B,Jv "oX+`Ugmé+#[þ2L6U}VRJEA402lY7}(J8pkLG:J?\qDub;,W* xn 4#VQ{o?| HUO5#K!(uyuG:&&\7H ,Wa65* 7ScJ| iD+|%QDD!^R thx|IA0*_n-UlZ#@(:ngOHc-t*reendstream
-endobj
-2106 0 obj <<
-/Type /Page
-/Contents 2107 0 R
-/Resources 2105 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2090 0 R
->> endobj
-2108 0 obj <<
-/D [2106 0 R /XYZ 85.039 786.531 null]
->> endobj
-22 0 obj <<
-/D [2106 0 R /XYZ 85.039 159.815 null]
->> endobj
-2109 0 obj <<
-/D [2106 0 R /XYZ 85.039 131.017 null]
->> endobj
-2105 0 obj <<
-/Font << /F62 1689 0 R /F41 2104 0 R /F15 1628 0 R /F20 1617 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2112 0 obj <<
-/Length 3359
-/Filter /FlateDecode
->>
-stream
-xrF`j*0x:'Y,Yk2!"A0
-;]GÚ*u5jè»ýj#l?‘âVW7[?(sUWUkdG
-^f-n5jdkdIuZ3*+xbLI2"zpj* ~.'"Z;l0Fqa) R49
-WuN`}oqEYM12opx3vI
-++H3xgShG'
-1>3Ml4s]Qj/,r]cÑθ/ôh¸ŒâݔÓ……”b¼¥:-PfFh#:e9 fs
-8K5Y;`!3+}(f^Q_N" [Pt-){Ha G]B^l\
-'Sb]5q1FqeS/$NG/rS|=&
-C<G-[ioT(P0J*+5(
-r#egyUt-<2 PB[g:6$xYSJ[#iS5|u3.^Ee:{LLj@i_[jNM)cxp~ U<{69.a_!P
-rF1/xrK{qGqveX(\dyWZ&OrOF2=W7xS#RCLn)H}Z
-1+ <X
-; ]{'|MZg<& H)
-uozoBDE[6J=:^BVJ1""Q/0o7M1+R7mZMj>"ybK|I|n>>0
-/:0/^ 565 !y# #\B?O
-U!oYBlg[vl uiGRg`KP"M/6}alzI?&)ro'f=ath&v~{v^unx(:˜*sÉendstream
-endobj
-2111 0 obj <<
-/Type /Page
-/Contents 2112 0 R
-/Resources 2110 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2090 0 R
-/Annots [ 2116 0 R 2117 0 R ]
->> endobj
-2116 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [138.589 74.246 402.992 85.935]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://hr.uoregon.edu/davidrl/cifs.txt)>>
->> endobj
-2117 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [138.589 52.241 385.241 63.93]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://afr.com/it/2002/10/01/FFXDF43AP6D.html)>>
->> endobj
-2113 0 obj <<
-/D [2111 0 R /XYZ 85.039 786.531 null]
->> endobj
-26 0 obj <<
-/D [2111 0 R /XYZ 85.039 541.704 null]
->> endobj
-2114 0 obj <<
-/D [2111 0 R /XYZ 85.039 512.906 null]
->> endobj
-30 0 obj <<
-/D [2111 0 R /XYZ 85.039 116.921 null]
->> endobj
-2115 0 obj <<
-/D [2111 0 R /XYZ 85.039 90.912 null]
->> endobj
-2110 0 obj <<
-/Font << /F62 1689 0 R /F15 1628 0 R /F41 2104 0 R /F20 1617 0 R /F65 2099 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2120 0 obj <<
-/Length 3225
-/Filter /FlateDecode
->>
-stream
-xZ[o8~RQw MhnnRlMl#q(+X`5yxD|J24lKN8OV'F>(pN} z;99'9$t}z4<RhErr=rcXYW#e]"oMßâèùè·É—“÷“ÎÒcßöC$>BUN,<W}7c?B a_ /GEBP`Pe y*+Al]
-0 _|g&S%"c5ZqI5CBQCjys!&LBbTI%
-fhUuCi.UYQa2T|AZ(Et@d%?VIxMCQ:8q-efX2x1DU%Pqk0 NR-.AAX9noz5Q`~u o^sH5:2p8rQAk%V#*{lKN]g]Z2-S+_c#DxTxKH0gyE,z)TR ];y@Y9 {q8F F$ONx $]^y'TriPWz_y~
-G(C/-H[I4Q}^v6I|2 #jI0 _hsd ]xC> l!H>*&Oq;t @2|\xKql&u^qlNb 1-7
-2(Xu!N*nA1U\rOIN2FpSr
-rU`R<zdDRn^s"Q:Be!i>D8>2 ?$L%OE4dU,g]O4[
-$12'*WMZ< @rsU G*u1dTIo5};
-ck;^?|[4VLAcJA.g/`` {F hZ%s19$.0`+b}d){w(a6hx<B~;I3Xc9PKM¾Åܨ®ä–ì’Â#ë?±±ÊÇð;ÓµI5`}_?SdsYnQZfdw @sY=NT=4]EcsA_\1
-y\xy2Ca8BÆz5Ý?Î ‰PdkPRAJ,1Xbp(è¾ÓSzkb t68}|Ld5u3&| qaX]fXn'.z)W@Zt%8<Q5}CG0KD
-/@f6/`pB3|Yom:S.^N^b4\}i et~OZiPy^^DoMt8v_t |7b
-q=0mseM2SQb8Z;;n)elJueO[
-R=<b[9va];VgG-Nx
-endobj
-2119 0 obj <<
-/Type /Page
-/Contents 2120 0 R
-/Resources 2118 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2090 0 R
-/Annots [ 2122 0 R 2123 0 R 2124 0 R 2125 0 R 2126 0 R 2127 0 R 2128 0 R 2129 0 R 2130 0 R 2132 0 R ]
->> endobj
-2122 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [138.589 752.53 357.484 764.219]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://ubiqx.org/cifs/)>>
->> endobj
-2123 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [138.589 730.014 328.405 741.704]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://samba.anu.edu.au/cifs/docs/what-is-smb.html)>>
->> endobj
-2124 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [138.589 707.499 370.677 719.188]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.linux-mag.com/1999-05/samba_01.html)>>
->> endobj
-2125 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [138.589 684.983 289.975 696.673]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.tldp.org/HOWTO/SMB-HOWTO.html)>>
->> endobj
-2126 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [138.589 661.861 309.786 674.763]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.phrack.org/phrack/60/p60-0x0b.txt)>>
->> endobj
-2127 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [138.589 639.952 358.538 651.641]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.linux-mag.com/1999-09/samba_01.html)>>
->> endobj
-2128 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [138.589 617.436 379.598 629.126]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://hr.uoregon.edu/davidrl/samba/)>>
->> endobj
-2129 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [138.589 594.921 460.925 606.61]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.linux-mag.com/2001-05/smb_01.html)>>
->> endobj
-2130 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [138.589 572.405 350.768 584.095]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.linux-mag.com/2002-02/samba_01.html)>>
->> endobj
-2132 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [131.316 229.148 458.066 240.837]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://hr.uoregon.edu/davidrl/boot.txt)>>
->> endobj
-2121 0 obj <<
-/D [2119 0 R /XYZ 85.039 786.531 null]
->> endobj
-34 0 obj <<
-/D [2119 0 R /XYZ 85.039 556.962 null]
->> endobj
-2131 0 obj <<
-/D [2119 0 R /XYZ 85.039 527.558 null]
->> endobj
-38 0 obj <<
-/D [2119 0 R /XYZ 85.039 213.705 null]
->> endobj
-2133 0 obj <<
-/D [2119 0 R /XYZ 85.039 187.09 null]
->> endobj
-2118 0 obj <<
-/Font << /F62 1689 0 R /F41 2104 0 R /F65 2099 0 R /F15 1628 0 R /F20 1617 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2136 0 obj <<
-/Length 2385
-/Filter /FlateDecode
->>
-stream
-xX/'V$,IqI-{(|mV I}EYk/-XCj8of&I&IQM0Y7Jv0[:1,}D~v>-?EQNgq{uTycOM<"l|[WP3
-}+(Dy(K1 #_ma
-eL j-ZEnDn+*W>at
-Caq
-- ]r-#}gg9hsvM@?ÊÒ¡ry ”˃›ÊÍw;‰þ—yWAHxb mxs.6)oCB
-qnOJ>ZO9E?)7<:qJ!,!ekvA0WWH, orYp6h [9\m+6X6!%_:n6w]Zs:
-{>BOSCm-L9
-D^$P<6%+h `4NEb|) U<a$K}[h,l"l|uC)A% xT6@
-I'.!1A{%#><osOIvc!MpSeRE/%Jpr_ (b/1O!,0FyJJ$NP,FpdD8u
-H2?l'v#&4iFg-~2e"aZI%=u88r-Z>)%[(]~p,1X ==S)-,ixOk!Cq [B5#Z+( lmYW'%g%xR"R`
-<J"}WJ`-UDr
-6+;/|W`ucP"E:?~1 8(+9V{}}l b [@@m
- Xu!/V,b^v~Ss#Hd-:vvt'jSFRrv2 ' !Vves $ZY1pg0%s^P4s~`n.Y9.(L Q
-%%A
-K4
-[4v_2 0
-eS*:
-+
-@C%
-endobj
-2135 0 obj <<
-/Type /Page
-/Contents 2136 0 R
-/Resources 2134 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2090 0 R
-/Annots [ 2140 0 R 2141 0 R 2144 0 R ]
->> endobj
-2140 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [313.377 617.253 415.127 628.943]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://samba.org/)>>
->> endobj
-2141 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [367.537 603.704 509.276 615.394]
-/Subtype /Link
-/A << /S /GoTo /D (compiling) >>
->> endobj
-2144 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [182.558 186.729 260.642 198.418]
-/Subtype /Link
-/A << /S /GoTo /D (securing-samba) >>
->> endobj
-2137 0 obj <<
-/D [2135 0 R /XYZ 85.039 786.531 null]
->> endobj
-42 0 obj <<
-/D [2135 0 R /XYZ 85.039 766.606 null]
->> endobj
-2138 0 obj <<
-/D [2135 0 R /XYZ 85.039 676.205 null]
->> endobj
-46 0 obj <<
-/D [2135 0 R /XYZ 85.039 676.205 null]
->> endobj
-2139 0 obj <<
-/D [2135 0 R /XYZ 85.039 644.68 null]
->> endobj
-50 0 obj <<
-/D [2135 0 R /XYZ 85.039 588.261 null]
->> endobj
-2142 0 obj <<
-/D [2135 0 R /XYZ 85.039 558.857 null]
->> endobj
-54 0 obj <<
-/D [2135 0 R /XYZ 85.039 490.063 null]
->> endobj
-2143 0 obj <<
-/D [2135 0 R /XYZ 85.039 468.867 null]
->> endobj
-58 0 obj <<
-/D [2135 0 R /XYZ 85.039 172.46 null]
->> endobj
-2145 0 obj <<
-/D [2135 0 R /XYZ 85.039 151.866 null]
->> endobj
-2134 0 obj <<
-/Font << /F20 1617 0 R /F15 1628 0 R /F35 1632 0 R /F56 1642 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2150 0 obj <<
-/Length 2895
-/Filter /FlateDecode
->>
-stream
-xk
-!h
-x\rN.plB($JbM
-I|>Z>$E- 3Z$m'a&3WJ0Ww;v|C(o_<\{: o|y yB03e* pw3|}OW/=flv3Y?]9G{;JkO_Z*<'j31SÚnèH[90
-gRKRt?OJ<Y@6ceZS w0: 2Y
-??VNU *f?eZafq
-D~(HD4Yhi~gtP|x!Cd'8 r%P[<mE+YaeS{x"1X"bvRl"Mz
-/.C7 I[.@e G;=UÙùdtI!dX"[MIv(ss-4 {O8p;BK8LYz'HW qfo$)-i*,%s_2 Y!ERj\L4rf<==<fPoX*$9>$5;ZL]-h-"z}]X}USVU *&6~x)*Za_
-3j;Gs)`SxN o#+&rY['zL=R FHsB`F.G?\VahlRHs"o,c R?f|;tCc15g=VX*rO
-LpBmcE$ 621BNf\@&7 Np]
--@+v3@uY|;.:FIyw5;9M->HCtӁòG|'_`ê(¢Á4hÛp”\óì*1ÉSnX2wicZcLBnF? M,p6w :)~6,e :cr1 m(8 -9j^##
-r<>yv
-8%)}6K((n FsTkÏK<iT
-=¢N*) 'j~8=e IqO>Ci6X [hC6b% QpM 5Ku#P4h-QFb8 Q%?(F#t)BuEj%ahQr;6@i.E| 9:hD@~Ue1n^ :S!]t%%zaNh D~ +h$Ed Cu &k*%3|{8:e![db|#d]HBg$`_k$`q9(2!C#7?FH^9[ANFS&P97(\kuMtTL*I;~A"C >lUc7=)k(a ^daN2;o;kD/8HE+Oz nA lo[d0)'|d)'|QK Vpj4gLb^nnp6m1$HwdQJGT&~l(S6-B1pYl0+/Y¹J"
-' :v3a;&6Aqw^8GPUl5msj'H4O>5!f`n0e~qNNDmz#[G-©Ø'• Ôec*?4n­(FLtR`zZKlg*vm8E4|.(tT&9QcS8N4B_soj@o0jN:B QavÉôøºk÷V/[\Pp
-iVpOS}B^i06O ('^|i{9o\B`k'gVV /d[YA2q=g/6ng%s4j+iSv .L`o;y/g2;a"]7|SPMJc5E)!]U.Kl yGB500).v7^=;]q2-y`{C'neA aN'i("k>k:L@*k><7s[v
-endobj
-2149 0 obj <<
-/Type /Page
-/Contents 2150 0 R
-/Resources 2148 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2162 0 R
-/Annots [ 2160 0 R 2161 0 R ]
->> endobj
-2160 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [293.723 140.375 341.14 152.065]
-/Subtype /Link
-/A << /S /GoTo /D (diagnosis) >>
->> endobj
-2161 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [225.07 126.826 427.223 138.516]
-/Subtype /Link
-/A << /S /GoTo /D (problems) >>
->> endobj
-2151 0 obj <<
-/D [2149 0 R /XYZ 85.039 786.531 null]
->> endobj
-62 0 obj <<
-/D [2149 0 R /XYZ 85.039 766.606 null]
->> endobj
-2152 0 obj <<
-/D [2149 0 R /XYZ 85.039 748.602 null]
->> endobj
-66 0 obj <<
-/D [2149 0 R /XYZ 85.039 610.22 null]
->> endobj
-2153 0 obj <<
-/D [2149 0 R /XYZ 85.039 578.694 null]
->> endobj
-70 0 obj <<
-/D [2149 0 R /XYZ 85.039 453.924 null]
->> endobj
-2154 0 obj <<
-/D [2149 0 R /XYZ 85.039 425.126 null]
->> endobj
-74 0 obj <<
-/D [2149 0 R /XYZ 85.039 313.904 null]
->> endobj
-2155 0 obj <<
-/D [2149 0 R /XYZ 85.039 266.376 null]
->> endobj
-78 0 obj <<
-/D [2149 0 R /XYZ 85.039 183.05 null]
->> endobj
-2159 0 obj <<
-/D [2149 0 R /XYZ 85.039 154.252 null]
->> endobj
-2148 0 obj <<
-/Font << /F62 1689 0 R /F20 1617 0 R /F15 1628 0 R /F35 1632 0 R /F56 1642 0 R /F41 2104 0 R /F38 2158 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2167 0 obj <<
-/Length 238
-/Filter /FlateDecode
->>
-stream
-xmPN1+\- JTHSQ
-~dkg !r d "w 0|{lh<G1)!{(vbSGj}{NvN'JL^ Mk}<V
-dQim\K$=_sua?U{>52T+ /k3Pv8f``6s\~]endstream
-endobj
-2166 0 obj <<
-/Type /Page
-/Contents 2167 0 R
-/Resources 2165 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2162 0 R
->> endobj
-2168 0 obj <<
-/D [2166 0 R /XYZ 85.039 786.531 null]
->> endobj
-82 0 obj <<
-/D [2166 0 R /XYZ 85.039 547.583 null]
->> endobj
-2165 0 obj <<
-/Font << /F20 1617 0 R /F15 1628 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2171 0 obj <<
-/Length 2514
-/Filter /FlateDecode
->>
-stream
-xYK60$mY n l GC?^=bXH ~"lOQ.;gqsC(]hl/+OC7<g9v87Z\c}K^\+]0=GCJfx3tYow7Fe;U%}S j'C%vEVj jdU7H"
-}-v~%7QR2QbGq)it0|(aA?q} +QE%;d[MX|7u7L#;r9ONctb[}{hqrWxWOlR}1v<0{*tVAi;Yt.÷O#Cykx\, 5 a'gY*ztbbYC?W#[ 8t6LJ%U 0XGv?xba^Ypd=
-2_L a36R] 'H";E88cZ>(jR&<ys +F?;A#,l1v»S`a*S]U#D grV>(vZ
-*9MREYYh6)U
--#B zsÇû‘Êf*  5qo˜Ppc$8
-$e‘¢Ø¨JD7þ6¥".qÆÛïä/ñQ8
-V{+o&P)s3~A9fD$'}p%,r 5 + h]"]/R5)vkl
-" tx 3\A|B| MWIA
-g3\fvvbf}(s hGz|%.*p0)290
-Fz#mo}-HSG.$`j9%0DY,( 75 ~c **yx\l#d[NuD==L|_vS`uE9w_(/JVU^$uCVs€O1M
-8raMp"bVk÷ïÏ˪i0£œ½±S*K|g}TY`S #
-endobj
-2170 0 obj <<
-/Type /Page
-/Contents 2171 0 R
-/Resources 2169 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2162 0 R
->> endobj
-2172 0 obj <<
-/D [2170 0 R /XYZ 85.039 786.531 null]
->> endobj
-2173 0 obj <<
-/D [2170 0 R /XYZ 85.039 766.606 null]
->> endobj
-86 0 obj <<
-/D [2170 0 R /XYZ 85.039 766.606 null]
->> endobj
-2174 0 obj <<
-/D [2170 0 R /XYZ 85.039 672.773 null]
->> endobj
-90 0 obj <<
-/D [2170 0 R /XYZ 85.039 454.238 null]
->> endobj
-2175 0 obj <<
-/D [2170 0 R /XYZ 85.039 425.503 null]
->> endobj
-94 0 obj <<
-/D [2170 0 R /XYZ 85.039 111.192 null]
->> endobj
-2176 0 obj <<
-/D [2170 0 R /XYZ 85.039 82.457 null]
->> endobj
-2169 0 obj <<
-/Font << /F20 1617 0 R /F15 1628 0 R /F41 2104 0 R /F56 1642 0 R /F65 2099 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2179 0 obj <<
-/Length 3161
-/Filter /FlateDecode
->>
-stream
-xr6_F
-Y)oWe7n`y{9†):Þê騿¥×´îpÇA,G@4 R.b7E]†hx IyZ`.^vQ=P-|y/xKUF|Ty@7'@_R+- n R-!oGjsM;
-ad>-slf(m$QFXMMph-^b>&RbhXJD@6'+h w@l
-:
-uk\`ud{V0Z[uf
-=Pa]3M,yeNa=/M6QR-zE0{E07:Y}fJZeM 0qhWj>v ³7„†«šõ6†Žì¬É––b~:òCskD+ QC`*@@*9*)bsnH29Q\)90 0x;eLu8aš–§vÈ´U)rtCB&h%u,q@F.&k"hF
-5bkq5uL
- N<b"B)@LDYZ+"`z7AT} M:iN]u .lG
-a*xÁ¾“
-¡’Ñ+štÒ¤|ˆ…Xx!J~`NvR!*z{G/ @i $QrBu1/-L 5yz}uTd eaSHSS N7=
-+w 9~9bI_GGZ=T'
-@!/vwRSTO Otcc#a W YR w`_b) a'L 6lrU2-(1SY%yU3q++k[\=]b&$-1\OO56%PSl" eYv~
-4^f 4] ?r/ N*h.N1Eoeendstream
-endobj
-2178 0 obj <<
-/Type /Page
-/Contents 2179 0 R
-/Resources 2177 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2162 0 R
->> endobj
-2180 0 obj <<
-/D [2178 0 R /XYZ 85.039 786.531 null]
->> endobj
-98 0 obj <<
-/D [2178 0 R /XYZ 85.039 601.595 null]
->> endobj
-2181 0 obj <<
-/D [2178 0 R /XYZ 85.039 574.98 null]
->> endobj
-102 0 obj <<
-/D [2178 0 R /XYZ 85.039 516.946 null]
->> endobj
-2182 0 obj <<
-/D [2178 0 R /XYZ 85.039 495.75 null]
->> endobj
-2177 0 obj <<
-/Font << /F62 1689 0 R /F15 1628 0 R /F65 2099 0 R /F20 1617 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2185 0 obj <<
-/Length 2830
-/Filter /FlateDecode
->>
-stream
-x_1RU#7sqjSsq8_
-oGU?+2,VNp>7cM+ G
-yX=w0aauMDpzbe](/fEGE! vr.E[D^hkHD#' R~/uD$O
-Iq
--2“h.ÃCgxLfEjw"
-m} }hEufQ!<Y.W?NoV33TW_HF&1$S-[|)eoGFt
-0">z4eKc:CS qL' 5r(Cqa]BA[#@`
-@Zg'XWDT5F} (Y(@By[Pso"1,=6
-aq@Kg"&5" ]u%&M!+m pBf I|(WqFTt{Hg-]Eendstream
-endobj
-2184 0 obj <<
-/Type /Page
-/Contents 2185 0 R
-/Resources 2183 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2162 0 R
->> endobj
-2186 0 obj <<
-/D [2184 0 R /XYZ 85.039 786.531 null]
->> endobj
-106 0 obj <<
-/D [2184 0 R /XYZ 85.039 766.606 null]
->> endobj
-2187 0 obj <<
-/D [2184 0 R /XYZ 85.039 676.735 null]
->> endobj
-110 0 obj <<
-/D [2184 0 R /XYZ 85.039 644.816 null]
->> endobj
-2188 0 obj <<
-/D [2184 0 R /XYZ 85.039 615.412 null]
->> endobj
-114 0 obj <<
-/D [2184 0 R /XYZ 85.039 508.283 null]
->> endobj
-2189 0 obj <<
-/D [2184 0 R /XYZ 85.039 484.966 null]
->> endobj
-2190 0 obj <<
-/D [2184 0 R /XYZ 85.039 397.416 null]
->> endobj
-2191 0 obj <<
-/D [2184 0 R /XYZ 85.039 374.7 null]
->> endobj
-118 0 obj <<
-/D [2184 0 R /XYZ 85.039 222.665 null]
->> endobj
-2192 0 obj <<
-/D [2184 0 R /XYZ 85.039 202.075 null]
->> endobj
-2183 0 obj <<
-/Font << /F20 1617 0 R /F15 1628 0 R /F65 2099 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2196 0 obj <<
-/Length 3291
-/Filter /FlateDecode
->>
-stream
-x]}'D*Mnm"Oo/R-][Cr87VS,(_YZm7j#Q2#Xi?HbwIR<~ssEmfFywCz›,òî>¼½½ûáÇïx NJ)w I4|`2 (V/|#?X,<Wj:L0FYU<s+S ~s3~So}iiOuS}`qv*~:
-aL9;++PvK$~(?*I`:,6Q
-8:rOw<Rh^ Yu`Ff=\*K&!hJgFh
-uÁØõÈ ¡¬5§àÚí]Ž¾¼’‰êÝâÚ–ðe«ƒÎë‚:ôMW& =W-rzM;#ù÷ß^ƒÀÝ  YOU,e#cMnx4ACQnC( qWbd`74Q
-c {mVVWhCfhd*Uu Gb h10
-QsF1f3lR
-EO'2m7[{%-`y].\Iu"#;'s]Zp>4&KE- u`_Jg?B l!$7ul==10F D C#F&dgm8AH 8
-{ ,0IH e' [*K:<\4WVjq\)q!$SF$?|B =T&%(#u2`ElyN&mx
-]\['! 90S
-$x,9 6AX{(Hz-2 *_iH4k
-bW1'b7 =[ @-t-
-\
-B;f62 2c'{ MTl8X*3
-Cos=J=?€{£Z4M .{Oj;>xGgGYw^TA"K%3/6h 0V&XGgC!8R^MTDeS4m^Fs
-*\IB e2BfoLt {6!:f B{*z,De87&566lvV%P,d<TXDi.K5X[f*$3-`V0f%dNr<F)K){/t2w<KTh~W;pph4m
-;. k@4\g}O~\ZJ\@w *2qJCSN0 E)cw4j"©×šêD[dUi`@9n%BR+%,DCsr[ [lR>w[|~bDc|HOu1:] !BD?R:h P_)s&W_`endstream
-endobj
-2195 0 obj <<
-/Type /Page
-/Contents 2196 0 R
-/Resources 2194 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2162 0 R
->> endobj
-2193 0 obj <<
-/Type /XObject
-/Subtype /Form
-/FormType 1
-/PTEX.FileName (./xslt/figures/note.pdf)
-/PTEX.PageNumber 1
-/PTEX.InfoDict 2209 0 R
-/Matrix [1 0 0 1 0 0]
-/BBox [0 0 27 27]
-/Resources <<
-/ProcSet [ /PDF ]
-/ExtGState <<
-/R4 2210 0 R
->>>>
-/Length 2211 0 R
-/Filter /FlateDecode
->>
-stream
-xeU9,Ge@@Q !%bd(d(
-$T)_acG=1Fl]tqu5<8:\;<q;.\i2c~eqc=7+g ctaL1cacum QOì-¡{wñ¨¼&kñÄÞ
-¨9xcH
-igC6u&\ GTMKlFyu|?%iKNq{v*JE]8hp0R$(+ nN
-q^>> .13!3SAih^(<mlL7
-2"E9~
-n*1xp&X\D0}#X>#^V|2i9r)`Xh&hbHe"
-rGX58Ot$yB5/vpo`kAr 4N.4
-endobj
-2209 0 obj
-<<
-/Producer (AFPL Ghostscript 6.50)
->>
-endobj
-2210 0 obj
-<<
-/Type /ExtGState
-/Name /R4
-/TR /Identity
-/OPM 1
-/SM 0.02
-/SA true
->>
-endobj
-2211 0 obj
-1049
-endobj
-2197 0 obj <<
-/D [2195 0 R /XYZ 85.039 786.531 null]
->> endobj
-122 0 obj <<
-/D [2195 0 R /XYZ 85.039 686.185 null]
->> endobj
-2198 0 obj <<
-/D [2195 0 R /XYZ 85.039 662.868 null]
->> endobj
-126 0 obj <<
-/D [2195 0 R /XYZ 85.039 231.018 null]
->> endobj
-2208 0 obj <<
-/D [2195 0 R /XYZ 85.039 213.279 null]
->> endobj
-2194 0 obj <<
-/Font << /F62 1689 0 R /F15 1628 0 R /F56 1642 0 R /F35 1632 0 R /F20 1617 0 R /F70 2201 0 R /F71 2204 0 R /F18 2207 0 R /F41 2104 0 R >>
-/XObject << /Im1 2193 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2214 0 obj <<
-/Length 2999
-/Filter /FlateDecode
->>
-stream
-xnF_!+>&=]$-QaTxlJiH# En[
-H^^_{8Y3TAsTÆÀcPg'BDd)SDEO?AWIu.W Rn6eQu/'o\HI#h\Vfib^S+YH)Zw lYW <EO #qqs(0|/Es)*xD¼h#P~CR Z~(0 =CH(&vy#%n]![8l;x+.G$L5
-i|b0}4i?y o< 4>{$7%!aF]-}aBvaF" d1U|= R$!8x.GkCM
-pb-a# 8/abW3`Q M]6U %
-;7:ÔƒÓQKG3ei(~9C, gI[Z1d BK]T3^/y]<l?s^g[Rd`YyVNDq\FV>
-4nh=Rt
-{ 10`?*N@XFRQnklA`sx}[lp<HYKqCLD]C
-And6{F
-D7#)&l2 kt0f@tah25ZM 8w?~, ^r*hI(%\7oN<XI8 g9QTK:x4bZ1
-!O=;6/e}~ ÈíU U Sh&1"\d.N4hKu1csC5p<~t2Z00Ufd4y(gOm ln+7:K-3$<m 2u{X{jUoO%w_,\",m A?*f]Pz0%zrrW^TIPq$ 89Td1MOP*ek2>gtaqlI}pA}#qmfk=zBX8 Lny  yAqi;L9V& uhWGn[;+xuM@.K0/I$n 6We:H)s,ex>LYKuDleX*MAuK3\xn7PO/$;l)?LV2,fD 4 !p>1o).|R|=[Qn . ](}Re~zs=>>)\5:H_Q+;-"\M3SwNE/|Yh^ÍÄÃ+q¹¤q]™¦‘‹‰iå¤c"åèN}%trRw2\47DCL.*[2=-z{ Z;vB VM:x=
-]WGoinrgbeR8[23T
-gXxcn0_E{<!u|#l{Y-L(
-^ 7S"P{xt
-43\ j.8;nK i7o6_MN(n".n~poxsF 6n\? Y'1(o52lqAtQ
-endobj
-2213 0 obj <<
-/Type /Page
-/Contents 2214 0 R
-/Resources 2212 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2217 0 R
->> endobj
-2215 0 obj <<
-/D [2213 0 R /XYZ 85.039 786.531 null]
->> endobj
-130 0 obj <<
-/D [2213 0 R /XYZ 85.039 173.977 null]
->> endobj
-2216 0 obj <<
-/D [2213 0 R /XYZ 85.039 155.503 null]
->> endobj
-2212 0 obj <<
-/Font << /F62 1689 0 R /F41 2104 0 R /F15 1628 0 R /F35 1632 0 R /F65 2099 0 R /F20 1617 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2220 0 obj <<
-/Length 2987
-/Filter /FlateDecode
->>
-stream
-xZmoF_!8**k~PMZ9-QTI}mE98p]#$ ]O8PrwM60
-o^?FDynH~xtvw:*g~Gg~.vIaR.~xDni&+ i2y4.Pag 9,P|3IGV3_+'k@|wS?q<NO-kh)Vy]OE,)g\'| OVuH7UeZqgM$P" hlq[LN=S0 #'+ X[r,Z2Ts(5|.=R(t@_k&?P8p,;t]/czGqKg$6l49+[]ef<mSY-4tNYDyU#.T hb%j
-<bAz+1yp=X|(K9<}i{[*-z)$k:UzhhDvC_tO:)KB>c7pE=x=f`s4l4G4(Vh9,!M"!08sGFxI[t20,
-e"U9A:AZcG/4!"{vl?rV(Mti\'BcIm|"22g)E,|6DotR
-[{cKt7r\y8#, l,7X*8~m$= aN)ya\
-1gze#GAb}mGsqs0]FA
-*x:^0exg
-*T
-(nje ZT"OIsDMG
-3,\D]k1dB.KK 6?f
-s^x4[_*v!)*FiREmIUy(<CMi}B9<Q s.KQpWI%F| #eW3 ]"9NCq, 8*K
-Au-_fg|i
-Q,/:<|]h#F>lgh[?65F'?
-vv 3(D$P)3?M [<(~<xnh`" JAx~r.sAu?i")(JJ}g3Eu8:,UIHPc5:oUC=K_x}}+HQZnV*rv~yK>r^"RadU":h`wG' 4nJendstream
-endobj
-2219 0 obj <<
-/Type /Page
-/Contents 2220 0 R
-/Resources 2218 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2217 0 R
-/Annots [ 2224 0 R ]
->> endobj
-2224 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [191.71 117.821 283.127 129.511]
-/Subtype /Link
-/A << /S /GoTo /D (winbind) >>
->> endobj
-2221 0 obj <<
-/D [2219 0 R /XYZ 85.039 786.531 null]
->> endobj
-134 0 obj <<
-/D [2219 0 R /XYZ 85.039 604.89 null]
->> endobj
-2222 0 obj <<
-/D [2219 0 R /XYZ 85.039 581.572 null]
->> endobj
-138 0 obj <<
-/D [2219 0 R /XYZ 85.039 525.863 null]
->> endobj
-2223 0 obj <<
-/D [2219 0 R /XYZ 85.039 505.269 null]
->> endobj
-142 0 obj <<
-/D [2219 0 R /XYZ 85.039 103.552 null]
->> endobj
-2225 0 obj <<
-/D [2219 0 R /XYZ 85.039 82.356 null]
->> endobj
-2218 0 obj <<
-/Font << /F62 1689 0 R /F15 1628 0 R /F20 1617 0 R /F65 2099 0 R /F35 1632 0 R /F56 1642 0 R /F41 2104 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2229 0 obj <<
-/Length 1834
-/Filter /FlateDecode
->>
-stream
-xXIo8W(cF$e:hd:@"+-$;sHa|oO:q <8Q@K'&?&PCB%<?:F""/(.s'P;{/>soj*t:a<;yjmySj´HU:0|~.jiOS2o~|'81t-4 D6/kC>is*AaY0q%](y<R#=03tAWEM }m6<=hS%90W%I*tp*]LOe I*}@j3 L?`c,"$"9!9
-q~=xD`$_</7bQT~D2t#%i ^";^pg#7!]TE}LiIk-:k,ES3!1
-Kxn)(5zqdA/:B9fPgo" `0=3cTiKQ _t@Rq bW?,f)/V/{|UU %! q%9':tWf ksDmb,ql`\a5*):I âWzeOhO]cxi=l40G`nysskio)*Ydr963qS}Sei$d(th6!G
-s]a
-7# f3wwBL[Lp{ rea46S7i5p{{&KgO`=q,|O> &zy?NbIT EMf\Nn'S <1cgO */D`AH.HQ|s$:DO|6J:W pv M4GY
-h1:f>kg"2}@
-hxin-i H m%Ec
-[Wzxsf{P#Q.q/.S|[7;2T?Ji,rg~?^&3m?&23S|W5e[\fE
-[_h->b-s}ubQW?.XkGRV%o5rvV8_,B^)R=Vf<T\Z,5/b1~<9(%z mj]<lyBe]s(}`KE
-LcUxW?p]Bm@y/#jc.OZZxm,8s[) )w,fxazg
-?zGY2o{-]Ç{Î3ûª)†Oxiq,@OGM@bCh{7))%VBhj3endstream
-endobj
-2228 0 obj <<
-/Type /Page
-/Contents 2229 0 R
-/Resources 2227 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2217 0 R
->> endobj
-2230 0 obj <<
-/D [2228 0 R /XYZ 85.039 786.531 null]
->> endobj
-146 0 obj <<
-/D [2228 0 R /XYZ 85.039 766.606 null]
->> endobj
-2231 0 obj <<
-/D [2228 0 R /XYZ 85.039 651.298 null]
->> endobj
-150 0 obj <<
-/D [2228 0 R /XYZ 85.039 651.298 null]
->> endobj
-2232 0 obj <<
-/D [2228 0 R /XYZ 85.039 619.773 null]
->> endobj
-154 0 obj <<
-/D [2228 0 R /XYZ 85.039 549.805 null]
->> endobj
-2233 0 obj <<
-/D [2228 0 R /XYZ 85.039 520.401 null]
->> endobj
-2227 0 obj <<
-/Font << /F20 1617 0 R /F15 1628 0 R /F35 1632 0 R /F41 2104 0 R /F70 2201 0 R /F18 2207 0 R >>
-/XObject << /Im1 2193 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2236 0 obj <<
-/Length 1982
-/Filter /FlateDecode
->>
-stream
-xio~-E8mC+rm!
-8eQ 3+w?w<m_g}w#g
-i3N@7##.|;.Ú>fê;ö|t¶rÃ[Ýf ­FEUt+L-PMUE jX1zr%cTonDnW6un&SK:Xm=zSM d &uoJJ*43#3 # m
-*q&F[]jF CLm@,vD`&5#AD=1hVM0LI{ 7+y0Ep*I:uj$I;Z.\fN/=R'dJ
-iHI*AJPrQrGdE59im
-M?yqXO\BbIJ
-b7`VnrX7JjDI4TTI/ jc}XGE @-v#PS@\9CqO^?@C6%'&=ý}5½]M(/[bg5[}T4B\M
-R2IJ)V7 0$}0@I#K(U|(Gn;`ZKm(\yO&[t_n.c3Rmw(JXu\`/a.S-PEbE3
-iB/lx"wiiZp>dgl 8G aIMtyos{GOZ]HVJUM sRu ,.&H5CuTh ;UUu&KBV}R});(Ba +~dcQYmM C^Th8Gn <2 Mi+O6uv$z [{]:9Cu/:SSV:EEzNN7k3; Y#}t]!O?5isU-Zxj;o8c#)$f:gll#E+}
-CqBO{TVB g +JSitTPqT
-endobj
-2235 0 obj <<
-/Type /Page
-/Contents 2236 0 R
-/Resources 2234 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2217 0 R
->> endobj
-2237 0 obj <<
-/D [2235 0 R /XYZ 85.039 786.531 null]
->> endobj
-2238 0 obj <<
-/D [2235 0 R /XYZ 85.039 664.759 null]
->> endobj
-2239 0 obj <<
-/D [2235 0 R /XYZ 85.039 642.243 null]
->> endobj
-2240 0 obj <<
-/D [2235 0 R /XYZ 85.039 619.728 null]
->> endobj
-158 0 obj <<
-/D [2235 0 R /XYZ 85.039 532.653 null]
->> endobj
-2241 0 obj <<
-/D [2235 0 R /XYZ 85.039 503.249 null]
->> endobj
-2234 0 obj <<
-/Font << /F62 1689 0 R /F15 1628 0 R /F65 2099 0 R /F20 1617 0 R /F35 1632 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2244 0 obj <<
-/Length 1910
-/Filter /FlateDecode
->>
-stream
-xXo6_E>PmvE$Jl+)z})@$gf pfev@a4kHz]}zsMXGw7"bnK\~={RW7j_^y?+;X~Uy^vE 0 yzw_g?Vi:<Kwy5E|KIM@]p
-rfLJ80M]R5TyWs%H!07O*58jmJ(Ko.0MX\l21V7(!"rM$7GB]ZTuS)P]Jn<
-fs`X(qh 
-endobj
-2243 0 obj <<
-/Type /Page
-/Contents 2244 0 R
-/Resources 2242 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2217 0 R
-/Annots [ 2246 0 R ]
->> endobj
-2246 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [177.134 169.832 306.43 181.522]
-/Subtype /Link
-/A << /S /GoTo /D (passdb) >>
->> endobj
-2245 0 obj <<
-/D [2243 0 R /XYZ 85.039 786.531 null]
->> endobj
-2242 0 obj <<
-/Font << /F62 1689 0 R /F35 1632 0 R /F70 2201 0 R /F18 2207 0 R /F15 1628 0 R /F41 2104 0 R >>
-/XObject << /Im1 2193 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2250 0 obj <<
-/Length 3101
-/Filter /FlateDecode
->>
-stream
-xZ[s~IbeFW!N'$av%
-"i9>}4Z@r*v.=3=_wS$t=.$rC_NPxN .VD>8/_.N.8q*s w;\Lr.[z4?y//}ruu |õ
-Îÿ¸úõäùÊâ}¸A'>z su,*M nh'NsWhQ,U~8Gk
-9_ FvmTqBUUHioc?5?Cl#S4y>R.bB Uwkh`e=8W;vw:MSsI-UHBm*bnlbaxCOS V9)_T,
-22'3)7c&W#([;P3$Thv? >;GyU\/= )FQ J"T|uO L`;7
- kùVm,?BZz1
-]8g:<@>"9PsD2PYsW%%tm>!:%"3n1=_ +thu 6 |3
-`00L 5u<=Tt"N(aVV{
-\zrE5LXw(hR*a{IPŠ¨ÄË#ŒȯäKBe"5e)!o.OMv`V]MY.z<% }!\_l}1x` L?]H*?kPj(
-M_D+=H'.`EnU#&YK=9;T>Ao!
-` CrW'6Q
-endobj
-2249 0 obj <<
-/Type /Page
-/Contents 2250 0 R
-/Resources 2248 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2217 0 R
-/Annots [ 2253 0 R ]
->> endobj
-2253 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [258.165 167.281 329.551 178.97]
-/Subtype /Link
-/A << /S /GoTo /D (passdb) >>
->> endobj
-2251 0 obj <<
-/D [2249 0 R /XYZ 85.039 786.531 null]
->> endobj
-162 0 obj <<
-/D [2249 0 R /XYZ 85.039 766.606 null]
->> endobj
-2252 0 obj <<
-/D [2249 0 R /XYZ 85.039 726.911 null]
->> endobj
-2248 0 obj <<
-/Font << /F62 1689 0 R /F20 1617 0 R /F15 1628 0 R /F41 2104 0 R /F65 2099 0 R /F35 1632 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2256 0 obj <<
-/Length 3364
-/Filter /FlateDecode
->>
-stream
-xZYoV~<B!qt(m1%b-*I9\$:uTw9w;wZBO*I%fQ8g:#SNLA"¹ZOW}J)s?r.pT{g+s_i&
-&hHH­l}tyôïnžÓ3^5Á"_Ë(14$ÐÈg§L4<.-OCB[| T
--Nz1 5f(
-" U&9ATM7JV* $t ^D2TW9q6"&lCY &v"@E+8| lq7 .kxi+O#q)*GJ. çù .ÂÕmQs_{2i6naE h9W7`ZJ:
-- .knrU.#iWv \ t?6A&xpr 2L@y0~P95 y%wVXSY9*^-pBmyR5wMg=jAR#Nx`^ kxZGb9#e`D4DH3
-`b9( 7)3)A( i|2
-Gs2rsv 45mW9$:2v
-oWq2ToÆ+EA#TAE "a7hJAX_hVetgf;{»Ôm±ÈÖa !ђÛ` ®GC&F'y8yR"ePuBEz<:gCSC
-*:G3R]S,Yk'EW%({U+&k]yY pQY%hp_`%6Y,GE.z$q|u 1V= b!D.]$_% 6/$&PmzX9\* O<R>Zuvqm,Ew3*`aKxIaGEwx&M q i$I@4t*j~d#):GP.>Z EAt@|_&"y*R%HMtI8A2T ,02&DP#@SQv=` RX1CjJ`mb(qb5m:Dol`? z'=F:²#ÚƉ4Ý?{ÏUO
-8*hpp2lq:}^l!4M Rd!zJ%PhtInv!au q_lJBqxqQiIa(J|5xIND8NG7›… \˜rj$՗ªzcވA^UFaa}8x",Bwji1olI%IG1l6qHr hC7 ];[18.Wj9uULqA4E ^VrZJa vd<;ih0 ge+<=?g\OzpWaXo(o6"@*1gRrNeFDC+K~",Okjl63>8_B/|U
-Cq5)mCykWeUY)Iv/:/*/b]PuH69bc1*zd/S";?Fx2O Wîšý8âvÉÏúku” à‹ÝW!t(5-axJwU !] :| B<J(TH#*.B
-mD)?)P`28"XqseEkmLG8!& V k\ Qk^%-e]u*K/>iF'#z
-!~ IucM$yP3#]^tSr WVbO1iSG,Qj\_G;}Ar6_@LSH35mÚ¾æ0{KHx>|'D_{fvK)2n`h3\x)2CDG4d%":?$ k c\tQ_6%m,~orlgO3 #vàÀˆ8€ìpK&J0br9q
-UR?'
-[\:5 yP6Gz@%,&H).'XE2-mSJ\4Qn\K[5V N>t.o>1^W;7UA'My /"_²¢ìË@|dWVt G>J ^2 4d`<2h"WG(Om v#BKq1f
-b=|45 =Tn@4# endstream
-endobj
-2255 0 obj <<
-/Type /Page
-/Contents 2256 0 R
-/Resources 2254 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2260 0 R
-/Annots [ 2259 0 R ]
->> endobj
-2259 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [369.053 65.818 448.095 78.72]
-/Subtype/Link/A<</Type/Action/S/URI/URI(file:smbpasswd.8.html)>>
->> endobj
-2257 0 obj <<
-/D [2255 0 R /XYZ 85.039 786.531 null]
->> endobj
-166 0 obj <<
-/D [2255 0 R /XYZ 85.039 410.406 null]
->> endobj
-2258 0 obj <<
-/D [2255 0 R /XYZ 85.039 391.534 null]
->> endobj
-2254 0 obj <<
-/Font << /F62 1689 0 R /F70 2201 0 R /F18 2207 0 R /F35 1632 0 R /F15 1628 0 R /F41 2104 0 R /F20 1617 0 R /F56 1642 0 R >>
-/XObject << /Im1 2193 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2264 0 obj <<
-/Length 3104
-/Filter /FlateDecode
->>
-stream
-xowZani6Ng4?-qH:ha0{}wGj80P,a3%x~HO~:lw7S7'n'T9^]q.n5g
-( <vp,9` XBV@V$^j8u-JZ
-xB:L !VX@jkS@Ez6u__bGYnCR38 _v/AEA4|0F< ndq&$X'kv EG{O o/E
-¦þ‰¥ÜÜA.p2J6Jw
-m4{d& _J f80pD(BYy[r|qde[Q)* oVq310>6Qx:]1H` \#hv;Et':G'eW[WBSbR4ysA^:u,/e[{n;|I6(;mzB
-9gCBD*%AQhlg4=p~f [|P<Q
-Qxl).,_<L{88U-mom{TN>[9kQF"[ 'A=2qm6 5.D>e|JU
- :GY7ltLa\k`_v-7Y"d|C&SAf,/; 7"KP\Ww{*C w:<ORSh6n2RIXA@H57绦>oîŠòÁº=®´ç‹üá¼Üa¢IKnD#px=4wyw7(0m#
-R0x6u|(|-Vt]VL|XuX\r(%%M<5' |#Il;[\
-#IFlcOo
-uF&x(iWl`~$J$co}Xe b$9y6
-sgt4`5+2 XS[>,/|@u R(|i/z-y3A}Aml zY!^^j9IG>6e:.pFa}0~8xQ]'v8wsNralgZviI 0 }N
-Ys;T~á™—ÂܚñÜ%gþ[ºˆcԁޅh‹ U2Q1O>-~]=gpoendstream
-endobj
-2263 0 obj <<
-/Type /Page
-/Contents 2264 0 R
-/Resources 2262 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2260 0 R
-/Annots [ 2267 0 R ]
->> endobj
-2261 0 obj <<
-/Type /XObject
-/Subtype /Form
-/FormType 1
-/PTEX.FileName (./xslt/figures/warning.pdf)
-/PTEX.PageNumber 1
-/Matrix [1 0 0 1 0 0]
-/BBox [0 0 31 31]
-/Resources <<
-/ProcSet [ /PDF ]
->>
-/Length 557
-/Filter [/FlateDecode]
->>
-stream
-xmIn1 EOPwu$Ig06V5 osO #h8:5?[IL~F PYdzZ8f(E#@xoL [
-
-6\>RgbW¹j[†›
-W{6;F])/Mu;pk;dh<EAwNtD](;rL Ttw_ =]=uS"yl-kHsreOvg<7t,e;/IB&(Y,kR'^ m" ^hW9AVy/f"Fy-Sng \d}B$w1.&COVX9gE{< P)!ZL~'UXLcXs~BLONZ_[.*]3Q!-endstream
-endobj
-2267 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [206.053 412.867 277.427 424.557]
-/Subtype/Link/A<</Type/Action/S/URI/URI(file:smb.conf.5.html#ADDUSERSCRIPT)>>
->> endobj
-2265 0 obj <<
-/D [2263 0 R /XYZ 85.039 786.531 null]
->> endobj
-170 0 obj <<
-/D [2263 0 R /XYZ 85.039 513.624 null]
->> endobj
-2266 0 obj <<
-/D [2263 0 R /XYZ 85.039 494.956 null]
->> endobj
-174 0 obj <<
-/D [2263 0 R /XYZ 85.039 296.432 null]
->> endobj
-2268 0 obj <<
-/D [2263 0 R /XYZ 85.039 273.114 null]
->> endobj
-2262 0 obj <<
-/Font << /F62 1689 0 R /F35 1632 0 R /F15 1628 0 R /F70 2201 0 R /F18 2207 0 R /F20 1617 0 R /F41 2104 0 R /F65 2099 0 R >>
-/XObject << /Im2 2261 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2271 0 obj <<
-/Length 3087
-/Filter /FlateDecode
->>
-stream
-xkoF`1\yiOvmE$6TT(] JL8/Dqh3YBA8v
-k'>?O
-(A\jh#iY& U(-fJaChX nHf5xJsEXŒ3|æE`VKTl >`v,99`nb;óÂÈzhêç2¯P h@=xEgd@^?>Y #%¢˜ÊͦîËb“–hQ?W0J fz B#:v'ws`$ 3,=ZTox[wy{mF:l/hLD7;l#H|/3239::sgp>\wf?:5~M
-$VD 6\=xpq.b8 +"PP¹O¾õ=›'BDYjZmMH&h%(7=XYf\ðë~£C\0*\*:b6_84`Dp][7G |n+wW] | I$k2Dk7nbcybPP1.0HLg#J7A= 81D"uBW7Pm}Aa3mx%KZc+;kh!ZZan\{2V]]f<t<M(cW=CMv%Wn@)6"C]6S !~y3pksnF,!G]+9R]!K7 iõœvÔޟ9)ÆcWjwCvZJiEVgx 5$4p9@{.!`G*ô:rEj%Vr2Z
-mccz)$eUjyLdk2)jXJ+SRmlF99;tE`Z&![vad>SdKhm1-MaqJ-LP*4uYRv3KCVWC&*RMY9|UcGQp!?N(Hg8n1Û¡mm¢ù爃®-\¡7 S ^z<<n,-Ka*a\n z'5;pT0tOp
-{@s AMM+!Ddwx*-6Z6J ;TLu
-6a$"}AQtb<uEK\f<m)
-|M%(~LGBbGUsSS!,*YJ?p] ?8
-p:H;sJ8QV +JJcPfn'\Ry\;W ^s*)0%#lYlUo[=?SWgs*bUl|!K]8XS,gJ\rm[Hrgl I{=-O=9oH;:rn;P4[B+HM1kdW7s -uy_Zzn h^]:bEQ;:F0v n~LSml)
-¥$uLeL;<Y<3U <2C\ZSaPfU<H`MCHRI#M6Oy7XEL 5kq-.u4J?tRBIj*9&5G|qIq)oZ7*{INmXxw?Phnu,ZsO$ Uv2",l4O!g{@*+D~h?[W8rõlM0 KCXuDW:F,IFOri~{hyT*$S[RJeTX=G 
-^Yl?]p5V8U@P 3_g=.M_{cDF>@@wendstream
-endobj
-2270 0 obj <<
-/Type /Page
-/Contents 2271 0 R
-/Resources 2269 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2260 0 R
-/Annots [ 2273 0 R ]
->> endobj
-2273 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [428.788 626.203 512.306 637.893]
-/Subtype /Link
-/A << /S /GoTo /D (domain-member) >>
->> endobj
-2272 0 obj <<
-/D [2270 0 R /XYZ 85.039 786.531 null]
->> endobj
-178 0 obj <<
-/D [2270 0 R /XYZ 85.039 597.211 null]
->> endobj
-2274 0 obj <<
-/D [2270 0 R /XYZ 85.039 570.597 null]
->> endobj
-182 0 obj <<
-/D [2270 0 R /XYZ 85.039 570.597 null]
->> endobj
-2275 0 obj <<
-/D [2270 0 R /XYZ 85.039 548.939 null]
->> endobj
-186 0 obj <<
-/D [2270 0 R /XYZ 85.039 450.922 null]
->> endobj
-2276 0 obj <<
-/D [2270 0 R /XYZ 85.039 401.83 null]
->> endobj
-190 0 obj <<
-/D [2270 0 R /XYZ 85.039 278.375 null]
->> endobj
-2277 0 obj <<
-/D [2270 0 R /XYZ 85.039 256.514 null]
->> endobj
-2269 0 obj <<
-/Font << /F62 1689 0 R /F15 1628 0 R /F41 2104 0 R /F65 2099 0 R /F20 1617 0 R /F35 1632 0 R /F56 1642 0 R /F38 2158 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2281 0 obj <<
-/Length 3613
-/Filter /FlateDecode
->>
-stream
-xZo4IK*EDI%R!ffN;;;;;=]/LCzW4+_1CoWMksS/.ey>n0tbwt3O=4r G?N#AI
-
-#j2Xd|4
+%PDF-1.3
+%
+1 0 obj<</Producer(htmldoc 1.8.22 Copyright 1997-2002 Easy Software Products, All Rights Reserved.)/CreationDate(D:20030328000013-0100)/Title(SAMBA Project Documentation)/Creator(Modular DocBook HTML Stylesheet Version 1.7)>>endobj
+2 0 obj<</Type/Encoding/Differences[ 32/space/exclam/quotedbl/numbersign/dollar/percent/ampersand/quotesingle/parenleft/parenright/asterisk/plus/comma/minus/period/slash/zero/one/two/three/four/five/six/seven/eight/nine/colon/semicolon/less/equal/greater/question/at/A/B/C/D/E/F/G/H/I/J/K/L/M/N/O/P/Q/R/S/T/U/V/W/X/Y/Z/bracketleft/backslash/bracketright/asciicircum/underscore/grave/a/b/c/d/e/f/g/h/i/j/k/l/m/n/o/p/q/r/s/t/u/v/w/x/y/z/braceleft/bar/braceright/asciitilde 128/Euro 130/quotesinglbase/florin/quotedblbase/ellipsis/dagger/daggerdbl/circumflex/perthousand/Scaron/guilsinglleft/OE 145/quoteleft/quoteright/quotedblleft/quotedblright/bullet/endash/emdash/tilde/trademark/scaron/guilsinglright/oe 159/Ydieresis/space/exclamdown/cent/sterling/currency/yen/brokenbar/section/dieresis/copyright/ordfeminine/guillemotleft/logicalnot/hyphen/registered/macron/degree/plusminus/twosuperior/threesuperior/acute/mu/paragraph/periodcentered/cedilla/onesuperior/ordmasculine/guillemotright/onequarter/onehalf/threequarters/questiondown/Agrave/Aacute/Acircumflex/Atilde/Adieresis/Aring/AE/Ccedilla/Egrave/Eacute/Ecircumflex/Edieresis/Igrave/Iacute/Icircumflex/Idieresis/Eth/Ntilde/Ograve/Oacute/Ocircumflex/Otilde/Odieresis/multiply/Oslash/Ugrave/Uacute/Ucircumflex/Udieresis/Yacute/Thorn/germandbls/agrave/aacute/acircumflex/atilde/adieresis/aring/ae/ccedilla/egrave/eacute/ecircumflex/edieresis/igrave/iacute/icircumflex/idieresis/eth/ntilde/ograve/oacute/ocircumflex/otilde/odieresis/divide/oslash/ugrave/uacute/ucircumflex/udieresis/yacute/thorn/ydieresis]>>endobj
+3 0 obj<</Type/Font/Subtype/Type1/BaseFont/Courier/Encoding 2 0 R>>endobj
+4 0 obj<</Type/Font/Subtype/Type1/BaseFont/Courier-Bold/Encoding 2 0 R>>endobj
+5 0 obj<</Type/Font/Subtype/Type1/BaseFont/Courier-Oblique/Encoding 2 0 R>>endobj
+6 0 obj<</Type/Font/Subtype/Type1/BaseFont/Times-Roman/Encoding 2 0 R>>endobj
+7 0 obj<</Type/Font/Subtype/Type1/BaseFont/Times-Bold/Encoding 2 0 R>>endobj
+8 0 obj<</Type/Font/Subtype/Type1/BaseFont/Times-Italic/Encoding 2 0 R>>endobj
+9 0 obj<</Type/Font/Subtype/Type1/BaseFont/Times-BoldItalic/Encoding 2 0 R>>endobj
+10 0 obj<</Type/Font/Subtype/Type1/BaseFont/Helvetica/Encoding 2 0 R>>endobj
+11 0 obj<</Type/Font/Subtype/Type1/BaseFont/Helvetica-Bold/Encoding 2 0 R>>endobj
+12 0 obj<</Type/Font/Subtype/Type1/BaseFont/Helvetica-Oblique/Encoding 2 0 R>>endobj
+13 0 obj<</Type/Font/Subtype/Type1/BaseFont/Helvetica-BoldOblique/Encoding 2 0 R>>endobj
+14 0 obj<</Type/Font/Subtype/Type1/BaseFont/Symbol>>endobj
+15 0 obj<</Type/XObject/Subtype/Image/ColorSpace/DeviceGray/Interpolate true/Filter/FlateDecode/Width 24/Height 24/BitsPerComponent 8/Length 250 >>stream
+xUQ+1kGl;2"c#X$G`Iw(qO%sN o$•¦š™àQ4FQz'`/~L,vuGo ujc\XI3+cEdJk{Q[^XRo8zu(d*Gs(y xYg({E {_3^Sd8æ„×<##~æ­•$:sð»›0B39dendstream
+endobj
+16 0 obj<</Type/XObject/Subtype/Image/ColorSpace[/Indexed/DeviceRGB 53<0800001000001800002100002900003100004200004A00005200005A00006B00007300007B00008400008C0000940000947B7B9C52529C5A5A9C7B7BA50000A53939A54A4AA58484A59494A5A5A5AD0000AD3131AD9494B50000B52929B59C9CB5A5A5B5B5B5BD0000BDADADC60000C61010C61818C6C6C6CE0000CE2929D60000D62929D6D6D6DE0000DEDEDEE70000E72121EF0808EFEFEFF70000F7F7F7FFFFFF>]/Interpolate true/Filter/FlateDecode/Width 24/Height 24/BitsPerComponent 8/Length 223 >>stream
+xUQ0 58@4wo%wR+8C+N"]*W ,D1|i"%~0)1lN!31T4H<<~Z>yn.H>LKb'4Y}-?f&tA{27L}On4KI" PBhG]z$>.mcoendstream
+endobj
+17 0 obj<</Subtype/Link/Rect[72.0 684.0 223.5 697.0]/Border[0 0 0]/Dest[1493 0 R/XYZ 0 734 0]>>endobj
+18 0 obj<</Subtype/Link/Rect[108.0 670.8 174.9 683.8]/Border[0 0 0]/Dest[1493 0 R/XYZ 0 696 0]>>endobj
+19 0 obj<</Subtype/Link/Rect[72.0 644.4 112.9 657.4]/Border[0 0 0]/Dest[1495 0 R/XYZ 0 734 0]>>endobj
+20 0 obj<</Subtype/Link/Rect[72.0 618.0 175.0 631.0]/Border[0 0 0]/Dest[1503 0 R/XYZ 0 734 0]>>endobj
+21 0 obj<</Subtype/Link/Rect[72.0 591.6 131.9 604.6]/Border[0 0 0]/Dest[1505 0 R/XYZ 0 734 0]>>endobj
+22 0 obj<</Subtype/Link/Rect[72.0 565.2 277.3 578.2]/Border[0 0 0]/Dest[1509 0 R/XYZ 0 734 0]>>endobj
+23 0 obj<</Subtype/Link/Rect[108.0 552.0 264.4 565.0]/Border[0 0 0]/Dest[1509 0 R/XYZ 0 696 0]>>endobj
+24 0 obj<</Subtype/Link/Rect[108.0 538.8 211.9 551.8]/Border[0 0 0]/Dest[1509 0 R/XYZ 0 595 0]>>endobj
+25 0 obj<</Subtype/Link/Rect[126.0 525.6 262.9 538.6]/Border[0 0 0]/Dest[1509 0 R/XYZ 0 506 0]>>endobj
+26 0 obj<</Subtype/Link/Rect[126.0 512.4 184.7 525.4]/Border[0 0 0]/Dest[1511 0 R/XYZ 0 705 0]>>endobj
+27 0 obj<</Subtype/Link/Rect[108.0 499.2 328.6 512.2]/Border[0 0 0]/Dest[1511 0 R/XYZ 0 528 0]>>endobj
+28 0 obj<</Subtype/Link/Rect[108.0 486.0 282.2 499.0]/Border[0 0 0]/Dest[1511 0 R/XYZ 0 360 0]>>endobj
+29 0 obj<</Subtype/Link/Rect[108.0 472.8 478.0 485.8]/Border[0 0 0]/Dest[1511 0 R/XYZ 0 193 0]>>endobj
+30 0 obj<</Subtype/Link/Rect[108.0 459.6 253.9 472.6]/Border[0 0 0]/Dest[1513 0 R/XYZ 0 652 0]>>endobj
+31 0 obj<</Subtype/Link/Rect[126.0 446.4 199.0 459.4]/Border[0 0 0]/Dest[1513 0 R/XYZ 0 511 0]>>endobj
+32 0 obj<</Subtype/Link/Rect[126.0 433.2 190.2 446.2]/Border[0 0 0]/Dest[1513 0 R/XYZ 0 426 0]>>endobj
+33 0 obj<</Subtype/Link/Rect[72.0 406.8 435.9 419.8]/Border[0 0 0]/Dest[1517 0 R/XYZ 0 734 0]>>endobj
+34 0 obj<</Subtype/Link/Rect[108.0 393.6 175.5 406.6]/Border[0 0 0]/Dest[1517 0 R/XYZ 0 565 0]>>endobj
+35 0 obj<</Subtype/Link/Rect[108.0 380.4 313.1 393.4]/Border[0 0 0]/Dest[1519 0 R/XYZ 0 734 0]>>endobj
+36 0 obj<</Subtype/Link/Rect[108.0 367.2 326.2 380.2]/Border[0 0 0]/Dest[1519 0 R/XYZ 0 412 0]>>endobj
+37 0 obj<</Subtype/Link/Rect[108.0 354.0 187.1 367.0]/Border[0 0 0]/Dest[1519 0 R/XYZ 0 234 0]>>endobj
+38 0 obj<</Subtype/Link/Rect[108.0 340.8 425.7 353.8]/Border[0 0 0]/Dest[1521 0 R/XYZ 0 388 0]>>endobj
+39 0 obj<</Subtype/Link/Rect[108.0 327.6 232.3 340.6]/Border[0 0 0]/Dest[1523 0 R/XYZ 0 705 0]>>endobj
+40 0 obj<</Subtype/Link/Rect[72.0 301.2 250.1 314.2]/Border[0 0 0]/Dest[1525 0 R/XYZ 0 734 0]>>endobj
+41 0 obj<</Subtype/Link/Rect[108.0 288.0 181.6 301.0]/Border[0 0 0]/Dest[1525 0 R/XYZ 0 696 0]>>endobj
+42 0 obj<</Subtype/Link/Rect[108.0 274.8 268.7 287.8]/Border[0 0 0]/Dest[1525 0 R/XYZ 0 449 0]>>endobj
+43 0 obj<</Subtype/Link/Rect[126.0 261.6 295.0 274.6]/Border[0 0 0]/Dest[1527 0 R/XYZ 0 402 0]>>endobj
+44 0 obj<</Subtype/Link/Rect[126.0 248.4 334.7 261.4]/Border[0 0 0]/Dest[1527 0 R/XYZ 0 269 0]>>endobj
+45 0 obj<</Subtype/Link/Rect[108.0 235.2 246.4 248.2]/Border[0 0 0]/Dest[1527 0 R/XYZ 0 163 0]>>endobj
+46 0 obj<</Subtype/Link/Rect[108.0 222.0 169.1 235.0]/Border[0 0 0]/Dest[1529 0 R/XYZ 0 362 0]>>endobj
+47 0 obj<</Subtype/Link/Rect[108.0 208.8 149.2 221.8]/Border[0 0 0]/Dest[1529 0 R/XYZ 0 273 0]>>endobj
+48 0 obj<</Subtype/Link/Rect[108.0 195.6 156.0 208.6]/Border[0 0 0]/Dest[1529 0 R/XYZ 0 198 0]>>endobj
+49 0 obj<</Subtype/Link/Rect[126.0 182.4 207.9 195.4]/Border[0 0 0]/Dest[1529 0 R/XYZ 0 165 0]>>endobj
+50 0 obj<</Subtype/Link/Rect[126.0 169.2 207.9 182.2]/Border[0 0 0]/Dest[1531 0 R/XYZ 0 573 0]>>endobj
+51 0 obj<</Subtype/Link/Rect[126.0 156.0 265.9 169.0]/Border[0 0 0]/Dest[1533 0 R/XYZ 0 734 0]>>endobj
+52 0 obj<</Subtype/Link/Rect[126.0 142.8 405.0 155.8]/Border[0 0 0]/Dest[1533 0 R/XYZ 0 622 0]>>endobj
+53 0 obj<</Subtype/Link/Rect[126.0 129.6 293.8 142.6]/Border[0 0 0]/Dest[1533 0 R/XYZ 0 251 0]>>endobj
+54 0 obj<</Subtype/Link/Rect[126.0 116.4 307.8 129.4]/Border[0 0 0]/Dest[1537 0 R/XYZ 0 438 0]>>endobj
+55 0 obj<</Subtype/Link/Rect[126.0 103.2 276.9 116.2]/Border[0 0 0]/Dest[1537 0 R/XYZ 0 247 0]>>endobj
+56 0 obj<</Subtype/Link/Rect[126.0 90.0 351.5 103.0]/Border[0 0 0]/Dest[1539 0 R/XYZ 0 543 0]>>endobj
+57 0 obj<</Subtype/Link/Rect[126.0 76.8 345.0 89.8]/Border[0 0 0]/Dest[1541 0 R/XYZ 0 533 0]>>endobj
+58 0 obj<</Subtype/Link/Rect[108.0 63.6 163.3 76.6]/Border[0 0 0]/Dest[1543 0 R/XYZ 0 708 0]>>endobj
+59 0 obj[17 0 R
+18 0 R
+19 0 R
+20 0 R
+21 0 R
+22 0 R
+23 0 R
+24 0 R
+25 0 R
+26 0 R
+27 0 R
+28 0 R
+29 0 R
+30 0 R
+31 0 R
+32 0 R
+33 0 R
+34 0 R
+35 0 R
+36 0 R
+37 0 R
+38 0 R
+39 0 R
+40 0 R
+41 0 R
+42 0 R
+43 0 R
+44 0 R
+45 0 R
+46 0 R
+47 0 R
+48 0 R
+49 0 R
+50 0 R
+51 0 R
+52 0 R
+53 0 R
+54 0 R
+55 0 R
+56 0 R
+57 0 R
+58 0 R]endobj
+60 0 obj<</Subtype/Link/Rect[72.0 684.0 250.1 697.0]/Border[0 0 0]/Dest[1525 0 R/XYZ 0 734 0]>>endobj
+61 0 obj<</Subtype/Link/Rect[126.0 670.8 192.0 683.8]/Border[0 0 0]/Dest[1543 0 R/XYZ 0 674 0]>>endobj
+62 0 obj<</Subtype/Link/Rect[126.0 657.6 248.2 670.6]/Border[0 0 0]/Dest[1543 0 R/XYZ 0 576 0]>>endobj
+63 0 obj<</Subtype/Link/Rect[126.0 644.4 207.3 657.4]/Border[0 0 0]/Dest[1543 0 R/XYZ 0 478 0]>>endobj
+64 0 obj<</Subtype/Link/Rect[126.0 631.2 371.9 644.2]/Border[0 0 0]/Dest[1545 0 R/XYZ 0 417 0]>>endobj
+65 0 obj<</Subtype/Link/Rect[126.0 618.0 330.5 631.0]/Border[0 0 0]/Dest[1545 0 R/XYZ 0 266 0]>>endobj
+66 0 obj<</Subtype/Link/Rect[108.0 604.8 215.9 617.8]/Border[0 0 0]/Dest[1545 0 R/XYZ 0 129 0]>>endobj
+67 0 obj<</Subtype/Link/Rect[126.0 591.6 192.0 604.6]/Border[0 0 0]/Dest[1547 0 R/XYZ 0 734 0]>>endobj
+68 0 obj<</Subtype/Link/Rect[126.0 578.4 181.0 591.4]/Border[0 0 0]/Dest[1547 0 R/XYZ 0 649 0]>>endobj
+69 0 obj<</Subtype/Link/Rect[72.0 552.0 177.1 565.0]/Border[0 0 0]/Dest[1549 0 R/XYZ 0 734 0]>>endobj
+70 0 obj<</Subtype/Link/Rect[72.0 525.6 131.9 538.6]/Border[0 0 0]/Dest[1551 0 R/XYZ 0 734 0]>>endobj
+71 0 obj<</Subtype/Link/Rect[72.0 499.2 268.1 512.2]/Border[0 0 0]/Dest[1555 0 R/XYZ 0 734 0]>>endobj
+72 0 obj<</Subtype/Link/Rect[108.0 486.0 213.4 499.0]/Border[0 0 0]/Dest[1555 0 R/XYZ 0 523 0]>>endobj
+73 0 obj<</Subtype/Link/Rect[108.0 472.8 234.2 485.8]/Border[0 0 0]/Dest[1555 0 R/XYZ 0 249 0]>>endobj
+74 0 obj<</Subtype/Link/Rect[108.0 459.6 210.7 472.6]/Border[0 0 0]/Dest[1557 0 R/XYZ 0 679 0]>>endobj
+75 0 obj<</Subtype/Link/Rect[126.0 446.4 266.5 459.4]/Border[0 0 0]/Dest[1557 0 R/XYZ 0 590 0]>>endobj
+76 0 obj<</Subtype/Link/Rect[72.0 420.0 412.8 433.0]/Border[0 0 0]/Dest[1559 0 R/XYZ 0 734 0]>>endobj
+77 0 obj<</Subtype/Link/Rect[72.0 393.6 390.1 406.6]/Border[0 0 0]/Dest[1563 0 R/XYZ 0 734 0]>>endobj
+78 0 obj<</Subtype/Link/Rect[108.0 380.4 219.2 393.4]/Border[0 0 0]/Dest[1563 0 R/XYZ 0 672 0]>>endobj
+79 0 obj<</Subtype/Link/Rect[108.0 367.2 181.0 380.2]/Border[0 0 0]/Dest[1563 0 R/XYZ 0 584 0]>>endobj
+80 0 obj<</Subtype/Link/Rect[108.0 354.0 316.1 367.0]/Border[0 0 0]/Dest[1565 0 R/XYZ 0 734 0]>>endobj
+81 0 obj<</Subtype/Link/Rect[108.0 340.8 430.0 353.8]/Border[0 0 0]/Dest[1567 0 R/XYZ 0 665 0]>>endobj
+82 0 obj<</Subtype/Link/Rect[126.0 327.6 351.2 340.6]/Border[0 0 0]/Dest[1569 0 R/XYZ 0 665 0]>>endobj
+83 0 obj<</Subtype/Link/Rect[126.0 314.4 380.5 327.4]/Border[0 0 0]/Dest[1571 0 R/XYZ 0 734 0]>>endobj
+84 0 obj<</Subtype/Link/Rect[126.0 301.2 297.4 314.2]/Border[0 0 0]/Dest[1571 0 R/XYZ 0 524 0]>>endobj
+85 0 obj<</Subtype/Link/Rect[108.0 288.0 261.4 301.0]/Border[0 0 0]/Dest[1571 0 R/XYZ 0 175 0]>>endobj
+86 0 obj<</Subtype/Link/Rect[108.0 274.8 252.8 287.8]/Border[0 0 0]/Dest[1575 0 R/XYZ 0 565 0]>>endobj
+87 0 obj<</Subtype/Link/Rect[108.0 261.6 243.6 274.6]/Border[0 0 0]/Dest[1577 0 R/XYZ 0 560 0]>>endobj
+88 0 obj<</Subtype/Link/Rect[108.0 248.4 292.9 261.4]/Border[0 0 0]/Dest[1581 0 R/XYZ 0 283 0]>>endobj
+89 0 obj<</Subtype/Link/Rect[126.0 235.2 350.0 248.2]/Border[0 0 0]/Dest[1583 0 R/XYZ 0 283 0]>>endobj
+90 0 obj<</Subtype/Link/Rect[126.0 222.0 424.2 235.0]/Border[0 0 0]/Dest[1585 0 R/XYZ 0 504 0]>>endobj
+91 0 obj<</Subtype/Link/Rect[108.0 208.8 431.0 221.8]/Border[0 0 0]/Dest[1593 0 R/XYZ 0 415 0]>>endobj
+92 0 obj<</Subtype/Link/Rect[72.0 182.4 512.6 195.4]/Border[0 0 0]/Dest[1597 0 R/XYZ 0 734 0]>>endobj
+93 0 obj<</Subtype/Link/Rect[108.0 169.2 219.2 182.2]/Border[0 0 0]/Dest[1597 0 R/XYZ 0 672 0]>>endobj
+94 0 obj<</Subtype/Link/Rect[108.0 156.0 181.0 169.0]/Border[0 0 0]/Dest[1597 0 R/XYZ 0 597 0]>>endobj
+95 0 obj<</Subtype/Link/Rect[108.0 142.8 359.1 155.8]/Border[0 0 0]/Dest[1597 0 R/XYZ 0 225 0]>>endobj
+96 0 obj<</Subtype/Link/Rect[126.0 129.6 382.3 142.6]/Border[0 0 0]/Dest[1599 0 R/XYZ 0 734 0]>>endobj
+97 0 obj<</Subtype/Link/Rect[126.0 116.4 269.0 129.4]/Border[0 0 0]/Dest[1599 0 R/XYZ 0 609 0]>>endobj
+98 0 obj<</Subtype/Link/Rect[108.0 103.2 391.8 116.2]/Border[0 0 0]/Dest[1599 0 R/XYZ 0 524 0]>>endobj
+99 0 obj<</Subtype/Link/Rect[108.0 90.0 268.1 103.0]/Border[0 0 0]/Dest[1599 0 R/XYZ 0 323 0]>>endobj
+100 0 obj<</Subtype/Link/Rect[126.0 76.8 327.6 89.8]/Border[0 0 0]/Dest[1601 0 R/XYZ 0 541 0]>>endobj
+101 0 obj<</Subtype/Link/Rect[126.0 63.6 282.4 76.6]/Border[0 0 0]/Dest[1601 0 R/XYZ 0 390 0]>>endobj
+102 0 obj[60 0 R
+61 0 R
+62 0 R
+63 0 R
+64 0 R
+65 0 R
+66 0 R
+67 0 R
+68 0 R
+69 0 R
+70 0 R
+71 0 R
+72 0 R
+73 0 R
+74 0 R
+75 0 R
+76 0 R
+77 0 R
+78 0 R
+79 0 R
+80 0 R
+81 0 R
+82 0 R
+83 0 R
+84 0 R
+85 0 R
+86 0 R
+87 0 R
+88 0 R
+89 0 R
+90 0 R
+91 0 R
+92 0 R
+93 0 R
+94 0 R
+95 0 R
+96 0 R
+97 0 R
+98 0 R
+99 0 R
+100 0 R
+101 0 R]endobj
+103 0 obj<</Subtype/Link/Rect[72.0 684.0 282.8 697.0]/Border[0 0 0]/Dest[1603 0 R/XYZ 0 734 0]>>endobj
+104 0 obj<</Subtype/Link/Rect[108.0 670.8 317.6 683.8]/Border[0 0 0]/Dest[1603 0 R/XYZ 0 551 0]>>endobj
+105 0 obj<</Subtype/Link/Rect[108.0 657.6 319.4 670.6]/Border[0 0 0]/Dest[1603 0 R/XYZ 0 444 0]>>endobj
+106 0 obj<</Subtype/Link/Rect[108.0 644.4 197.8 657.4]/Border[0 0 0]/Dest[1603 0 R/XYZ 0 267 0]>>endobj
+107 0 obj<</Subtype/Link/Rect[108.0 631.2 239.4 644.2]/Border[0 0 0]/Dest[1605 0 R/XYZ 0 580 0]>>endobj
+108 0 obj<</Subtype/Link/Rect[108.0 618.0 253.4 631.0]/Border[0 0 0]/Dest[1605 0 R/XYZ 0 264 0]>>endobj
+109 0 obj<</Subtype/Link/Rect[126.0 604.8 218.6 617.8]/Border[0 0 0]/Dest[1605 0 R/XYZ 0 202 0]>>endobj
+110 0 obj<</Subtype/Link/Rect[108.0 591.6 224.7 604.6]/Border[0 0 0]/Dest[1607 0 R/XYZ 0 734 0]>>endobj
+111 0 obj<</Subtype/Link/Rect[108.0 578.4 228.1 591.4]/Border[0 0 0]/Dest[1607 0 R/XYZ 0 645 0]>>endobj
+112 0 obj<</Subtype/Link/Rect[108.0 565.2 152.9 578.2]/Border[0 0 0]/Dest[1607 0 R/XYZ 0 570 0]>>endobj
+113 0 obj<</Subtype/Link/Rect[72.0 538.8 329.3 551.8]/Border[0 0 0]/Dest[1609 0 R/XYZ 0 734 0]>>endobj
+114 0 obj<</Subtype/Link/Rect[108.0 525.6 299.9 538.6]/Border[0 0 0]/Dest[1609 0 R/XYZ 0 672 0]>>endobj
+115 0 obj<</Subtype/Link/Rect[108.0 512.4 288.0 525.4]/Border[0 0 0]/Dest[1611 0 R/XYZ 0 494 0]>>endobj
+116 0 obj<</Subtype/Link/Rect[108.0 499.2 307.9 512.2]/Border[0 0 0]/Dest[1611 0 R/XYZ 0 405 0]>>endobj
+117 0 obj<</Subtype/Link/Rect[72.0 472.8 198.2 485.8]/Border[0 0 0]/Dest[1615 0 R/XYZ 0 734 0]>>endobj
+118 0 obj<</Subtype/Link/Rect[72.0 446.4 131.9 459.4]/Border[0 0 0]/Dest[1617 0 R/XYZ 0 734 0]>>endobj
+119 0 obj<</Subtype/Link/Rect[72.0 420.0 354.3 433.0]/Border[0 0 0]/Dest[1623 0 R/XYZ 0 734 0]>>endobj
+120 0 obj<</Subtype/Link/Rect[108.0 406.8 167.0 419.8]/Border[0 0 0]/Dest[1623 0 R/XYZ 0 672 0]>>endobj
+121 0 obj<</Subtype/Link/Rect[108.0 393.6 333.2 406.6]/Border[0 0 0]/Dest[1623 0 R/XYZ 0 439 0]>>endobj
+122 0 obj<</Subtype/Link/Rect[126.0 380.4 200.6 393.4]/Border[0 0 0]/Dest[1623 0 R/XYZ 0 311 0]>>endobj
+123 0 obj<</Subtype/Link/Rect[126.0 367.2 227.1 380.2]/Border[0 0 0]/Dest[1625 0 R/XYZ 0 441 0]>>endobj
+124 0 obj<</Subtype/Link/Rect[126.0 354.0 218.6 367.0]/Border[0 0 0]/Dest[1625 0 R/XYZ 0 303 0]>>endobj
+125 0 obj<</Subtype/Link/Rect[126.0 340.8 238.7 353.8]/Border[0 0 0]/Dest[1625 0 R/XYZ 0 157 0]>>endobj
+126 0 obj<</Subtype/Link/Rect[108.0 327.6 387.9 340.6]/Border[0 0 0]/Dest[1627 0 R/XYZ 0 339 0]>>endobj
+127 0 obj<</Subtype/Link/Rect[126.0 314.4 279.1 327.4]/Border[0 0 0]/Dest[1629 0 R/XYZ 0 266 0]>>endobj
+128 0 obj<</Subtype/Link/Rect[126.0 301.2 247.6 314.2]/Border[0 0 0]/Dest[1631 0 R/XYZ 0 734 0]>>endobj
+129 0 obj<</Subtype/Link/Rect[126.0 288.0 211.2 301.0]/Border[0 0 0]/Dest[1633 0 R/XYZ 0 459 0]>>endobj
+130 0 obj<</Subtype/Link/Rect[126.0 274.8 218.0 287.8]/Border[0 0 0]/Dest[1633 0 R/XYZ 0 361 0]>>endobj
+131 0 obj<</Subtype/Link/Rect[126.0 261.6 224.1 274.6]/Border[0 0 0]/Dest[1633 0 R/XYZ 0 224 0]>>endobj
+132 0 obj<</Subtype/Link/Rect[108.0 248.4 528.7 261.4]/Border[0 0 0]/Dest[1635 0 R/XYZ 0 670 0]>>endobj
+133 0 obj<</Subtype/Link/Rect[108.0 235.2 503.4 248.2]/Border[0 0 0]/Dest[1635 0 R/XYZ 0 126 0]>>endobj
+134 0 obj<</Subtype/Link/Rect[126.0 222.0 376.8 235.0]/Border[0 0 0]/Dest[1639 0 R/XYZ 0 734 0]>>endobj
+135 0 obj<</Subtype/Link/Rect[126.0 208.8 442.5 221.8]/Border[0 0 0]/Dest[1639 0 R/XYZ 0 484 0]>>endobj
+136 0 obj<</Subtype/Link/Rect[126.0 195.6 356.0 208.6]/Border[0 0 0]/Dest[1639 0 R/XYZ 0 132 0]>>endobj
+137 0 obj<</Subtype/Link/Rect[108.0 182.4 187.1 195.4]/Border[0 0 0]/Dest[1641 0 R/XYZ 0 263 0]>>endobj
+138 0 obj<</Subtype/Link/Rect[72.0 156.0 418.2 169.0]/Border[0 0 0]/Dest[1643 0 R/XYZ 0 734 0]>>endobj
+139 0 obj<</Subtype/Link/Rect[108.0 142.8 450.2 155.8]/Border[0 0 0]/Dest[1643 0 R/XYZ 0 672 0]>>endobj
+140 0 obj<</Subtype/Link/Rect[108.0 129.6 324.6 142.6]/Border[0 0 0]/Dest[1643 0 R/XYZ 0 537 0]>>endobj
+141 0 obj<</Subtype/Link/Rect[108.0 116.4 236.6 129.4]/Border[0 0 0]/Dest[1643 0 R/XYZ 0 369 0]>>endobj
+142 0 obj<</Subtype/Link/Rect[108.0 103.2 297.7 116.2]/Border[0 0 0]/Dest[1645 0 R/XYZ 0 705 0]>>endobj
+143 0 obj<</Subtype/Link/Rect[126.0 90.0 232.0 103.0]/Border[0 0 0]/Dest[1645 0 R/XYZ 0 471 0]>>endobj
+144 0 obj<</Subtype/Link/Rect[126.0 76.8 257.1 89.8]/Border[0 0 0]/Dest[1645 0 R/XYZ 0 228 0]>>endobj
+145 0 obj<</Subtype/Link/Rect[108.0 63.6 306.9 76.6]/Border[0 0 0]/Dest[1647 0 R/XYZ 0 718 0]>>endobj
+146 0 obj[103 0 R
+104 0 R
+105 0 R
+106 0 R
+107 0 R
+108 0 R
+109 0 R
+110 0 R
+111 0 R
+112 0 R
+113 0 R
+114 0 R
+115 0 R
+116 0 R
+117 0 R
+118 0 R
+119 0 R
+120 0 R
+121 0 R
+122 0 R
+123 0 R
+124 0 R
+125 0 R
+126 0 R
+127 0 R
+128 0 R
+129 0 R
+130 0 R
+131 0 R
+132 0 R
+133 0 R
+134 0 R
+135 0 R
+136 0 R
+137 0 R
+138 0 R
+139 0 R
+140 0 R
+141 0 R
+142 0 R
+143 0 R
+144 0 R
+145 0 R]endobj
+147 0 obj<</Subtype/Link/Rect[72.0 684.0 418.2 697.0]/Border[0 0 0]/Dest[1643 0 R/XYZ 0 734 0]>>endobj
+148 0 obj<</Subtype/Link/Rect[108.0 670.8 397.6 683.8]/Border[0 0 0]/Dest[1647 0 R/XYZ 0 287 0]>>endobj
+149 0 obj<</Subtype/Link/Rect[108.0 657.6 389.7 670.6]/Border[0 0 0]/Dest[1651 0 R/XYZ 0 652 0]>>endobj
+150 0 obj<</Subtype/Link/Rect[72.0 631.2 466.2 644.2]/Border[0 0 0]/Dest[1653 0 R/XYZ 0 734 0]>>endobj
+151 0 obj<</Subtype/Link/Rect[108.0 618.0 207.9 631.0]/Border[0 0 0]/Dest[1653 0 R/XYZ 0 672 0]>>endobj
+152 0 obj<</Subtype/Link/Rect[108.0 604.8 250.4 617.8]/Border[0 0 0]/Dest[1655 0 R/XYZ 0 148 0]>>endobj
+153 0 obj<</Subtype/Link/Rect[108.0 591.6 275.8 604.6]/Border[0 0 0]/Dest[1657 0 R/XYZ 0 705 0]>>endobj
+154 0 obj<</Subtype/Link/Rect[72.0 565.2 407.8 578.2]/Border[0 0 0]/Dest[1659 0 R/XYZ 0 734 0]>>endobj
+155 0 obj<</Subtype/Link/Rect[108.0 552.0 184.7 565.0]/Border[0 0 0]/Dest[1659 0 R/XYZ 0 672 0]>>endobj
+156 0 obj<</Subtype/Link/Rect[126.0 538.8 184.7 551.8]/Border[0 0 0]/Dest[1661 0 R/XYZ 0 652 0]>>endobj
+157 0 obj<</Subtype/Link/Rect[72.0 512.4 210.7 525.4]/Border[0 0 0]/Dest[1663 0 R/XYZ 0 734 0]>>endobj
+158 0 obj<</Subtype/Link/Rect[108.0 499.2 187.1 512.2]/Border[0 0 0]/Dest[1663 0 R/XYZ 0 696 0]>>endobj
+159 0 obj<</Subtype/Link/Rect[108.0 486.0 194.5 499.0]/Border[0 0 0]/Dest[1663 0 R/XYZ 0 317 0]>>endobj
+160 0 obj<</Subtype/Link/Rect[126.0 472.8 233.2 485.8]/Border[0 0 0]/Dest[1663 0 R/XYZ 0 127 0]>>endobj
+161 0 obj<</Subtype/Link/Rect[126.0 459.6 317.9 472.6]/Border[0 0 0]/Dest[1667 0 R/XYZ 0 531 0]>>endobj
+162 0 obj<</Subtype/Link/Rect[126.0 446.4 310.8 459.4]/Border[0 0 0]/Dest[1669 0 R/XYZ 0 734 0]>>endobj
+163 0 obj<</Subtype/Link/Rect[126.0 433.2 374.4 446.2]/Border[0 0 0]/Dest[1669 0 R/XYZ 0 363 0]>>endobj
+164 0 obj<</Subtype/Link/Rect[126.0 420.0 265.6 433.0]/Border[0 0 0]/Dest[1671 0 R/XYZ 0 184 0]>>endobj
+165 0 obj<</Subtype/Link/Rect[108.0 406.8 225.6 419.8]/Border[0 0 0]/Dest[1673 0 R/XYZ 0 692 0]>>endobj
+166 0 obj<</Subtype/Link/Rect[126.0 393.6 237.8 406.6]/Border[0 0 0]/Dest[1673 0 R/XYZ 0 590 0]>>endobj
+167 0 obj<</Subtype/Link/Rect[126.0 380.4 304.7 393.4]/Border[0 0 0]/Dest[1673 0 R/XYZ 0 466 0]>>endobj
+168 0 obj<</Subtype/Link/Rect[126.0 367.2 245.8 380.2]/Border[0 0 0]/Dest[1673 0 R/XYZ 0 381 0]>>endobj
+169 0 obj<</Subtype/Link/Rect[126.0 354.0 258.0 367.0]/Border[0 0 0]/Dest[1673 0 R/XYZ 0 283 0]>>endobj
+170 0 obj<</Subtype/Link/Rect[108.0 340.8 176.8 353.8]/Border[0 0 0]/Dest[1675 0 R/XYZ 0 397 0]>>endobj
+171 0 obj<</Subtype/Link/Rect[126.0 327.6 213.4 340.6]/Border[0 0 0]/Dest[1675 0 R/XYZ 0 363 0]>>endobj
+172 0 obj<</Subtype/Link/Rect[126.0 314.4 283.7 327.4]/Border[0 0 0]/Dest[1677 0 R/XYZ 0 429 0]>>endobj
+173 0 obj<</Subtype/Link/Rect[126.0 301.2 267.7 314.2]/Border[0 0 0]/Dest[1679 0 R/XYZ 0 665 0]>>endobj
+174 0 obj<</Subtype/Link/Rect[126.0 288.0 318.8 301.0]/Border[0 0 0]/Dest[1679 0 R/XYZ 0 485 0]>>endobj
+175 0 obj<</Subtype/Link/Rect[126.0 274.8 242.1 287.8]/Border[0 0 0]/Dest[1681 0 R/XYZ 0 734 0]>>endobj
+176 0 obj<</Subtype/Link/Rect[126.0 261.6 262.9 274.6]/Border[0 0 0]/Dest[1681 0 R/XYZ 0 394 0]>>endobj
+177 0 obj<</Subtype/Link/Rect[126.0 248.4 261.1 261.4]/Border[0 0 0]/Dest[1683 0 R/XYZ 0 718 0]>>endobj
+178 0 obj<</Subtype/Link/Rect[126.0 235.2 241.8 248.2]/Border[0 0 0]/Dest[1683 0 R/XYZ 0 633 0]>>endobj
+179 0 obj<</Subtype/Link/Rect[126.0 222.0 228.4 235.0]/Border[0 0 0]/Dest[1683 0 R/XYZ 0 535 0]>>endobj
+180 0 obj<</Subtype/Link/Rect[72.0 195.6 242.2 208.6]/Border[0 0 0]/Dest[1685 0 R/XYZ 0 734 0]>>endobj
+181 0 obj<</Subtype/Link/Rect[108.0 182.4 187.1 195.4]/Border[0 0 0]/Dest[1685 0 R/XYZ 0 696 0]>>endobj
+182 0 obj<</Subtype/Link/Rect[108.0 169.2 290.8 182.2]/Border[0 0 0]/Dest[1685 0 R/XYZ 0 463 0]>>endobj
+183 0 obj<</Subtype/Link/Rect[108.0 156.0 240.0 169.0]/Border[0 0 0]/Dest[1689 0 R/XYZ 0 276 0]>>endobj
+184 0 obj<</Subtype/Link/Rect[108.0 142.8 277.0 155.8]/Border[0 0 0]/Dest[1701 0 R/XYZ 0 546 0]>>endobj
+185 0 obj<</Subtype/Link/Rect[126.0 129.6 253.7 142.6]/Border[0 0 0]/Dest[1701 0 R/XYZ 0 404 0]>>endobj
+186 0 obj<</Subtype/Link/Rect[108.0 116.4 330.4 129.4]/Border[0 0 0]/Dest[1705 0 R/XYZ 0 177 0]>>endobj
+187 0 obj<</Subtype/Link/Rect[108.0 103.2 349.4 116.2]/Border[0 0 0]/Dest[1713 0 R/XYZ 0 362 0]>>endobj
+188 0 obj<</Subtype/Link/Rect[108.0 90.0 289.3 103.0]/Border[0 0 0]/Dest[1715 0 R/XYZ 0 527 0]>>endobj
+189 0 obj[147 0 R
+148 0 R
+149 0 R
+150 0 R
+151 0 R
+152 0 R
+153 0 R
+154 0 R
+155 0 R
+156 0 R
+157 0 R
+158 0 R
+159 0 R
+160 0 R
+161 0 R
+162 0 R
+163 0 R
+164 0 R
+165 0 R
+166 0 R
+167 0 R
+168 0 R
+169 0 R
+170 0 R
+171 0 R
+172 0 R
+173 0 R
+174 0 R
+175 0 R
+176 0 R
+177 0 R
+178 0 R
+179 0 R
+180 0 R
+181 0 R
+182 0 R
+183 0 R
+184 0 R
+185 0 R
+186 0 R
+187 0 R
+188 0 R]endobj
+190 0 obj<</Subtype/Link/Rect[72.0 684.0 431.7 697.0]/Border[0 0 0]/Dest[1719 0 R/XYZ 0 734 0]>>endobj
+191 0 obj<</Subtype/Link/Rect[108.0 670.8 170.0 683.8]/Border[0 0 0]/Dest[1719 0 R/XYZ 0 672 0]>>endobj
+192 0 obj<</Subtype/Link/Rect[108.0 657.6 187.1 670.6]/Border[0 0 0]/Dest[1719 0 R/XYZ 0 544 0]>>endobj
+193 0 obj<</Subtype/Link/Rect[108.0 644.4 239.1 657.4]/Border[0 0 0]/Dest[1719 0 R/XYZ 0 231 0]>>endobj
+194 0 obj<</Subtype/Link/Rect[126.0 631.2 211.8 644.2]/Border[0 0 0]/Dest[1721 0 R/XYZ 0 560 0]>>endobj
+195 0 obj<</Subtype/Link/Rect[108.0 618.0 227.5 631.0]/Border[0 0 0]/Dest[1721 0 R/XYZ 0 409 0]>>endobj
+196 0 obj<</Subtype/Link/Rect[126.0 604.8 312.1 617.8]/Border[0 0 0]/Dest[1721 0 R/XYZ 0 294 0]>>endobj
+197 0 obj<</Subtype/Link/Rect[126.0 591.6 319.4 604.6]/Border[0 0 0]/Dest[1723 0 R/XYZ 0 734 0]>>endobj
+198 0 obj<</Subtype/Link/Rect[126.0 578.4 254.3 591.4]/Border[0 0 0]/Dest[1723 0 R/XYZ 0 635 0]>>endobj
+199 0 obj<</Subtype/Link/Rect[126.0 565.2 312.4 578.2]/Border[0 0 0]/Dest[1723 0 R/XYZ 0 194 0]>>endobj
+200 0 obj<</Subtype/Link/Rect[126.0 552.0 292.8 565.0]/Border[0 0 0]/Dest[1725 0 R/XYZ 0 560 0]>>endobj
+201 0 obj<</Subtype/Link/Rect[126.0 538.8 226.5 551.8]/Border[0 0 0]/Dest[1725 0 R/XYZ 0 383 0]>>endobj
+202 0 obj<</Subtype/Link/Rect[108.0 525.6 265.4 538.6]/Border[0 0 0]/Dest[1725 0 R/XYZ 0 245 0]>>endobj
+203 0 obj<</Subtype/Link/Rect[126.0 512.4 213.4 525.4]/Border[0 0 0]/Dest[1725 0 R/XYZ 0 143 0]>>endobj
+204 0 obj<</Subtype/Link/Rect[126.0 499.2 220.1 512.2]/Border[0 0 0]/Dest[1727 0 R/XYZ 0 533 0]>>endobj
+205 0 obj<</Subtype/Link/Rect[126.0 486.0 244.6 499.0]/Border[0 0 0]/Dest[1727 0 R/XYZ 0 264 0]>>endobj
+206 0 obj<</Subtype/Link/Rect[108.0 472.8 183.5 485.8]/Border[0 0 0]/Dest[1743 0 R/XYZ 0 555 0]>>endobj
+207 0 obj<</Subtype/Link/Rect[108.0 459.6 182.9 472.6]/Border[0 0 0]/Dest[1743 0 R/XYZ 0 335 0]>>endobj
+208 0 obj<</Subtype/Link/Rect[72.0 433.2 268.2 446.2]/Border[0 0 0]/Dest[1745 0 R/XYZ 0 734 0]>>endobj
+209 0 obj<</Subtype/Link/Rect[108.0 420.0 231.7 433.0]/Border[0 0 0]/Dest[1745 0 R/XYZ 0 696 0]>>endobj
+210 0 obj<</Subtype/Link/Rect[108.0 406.8 253.4 419.8]/Border[0 0 0]/Dest[1745 0 R/XYZ 0 463 0]>>endobj
+211 0 obj<</Subtype/Link/Rect[108.0 393.6 216.8 406.6]/Border[0 0 0]/Dest[1747 0 R/XYZ 0 734 0]>>endobj
+212 0 obj<</Subtype/Link/Rect[108.0 380.4 241.5 393.4]/Border[0 0 0]/Dest[1747 0 R/XYZ 0 381 0]>>endobj
+213 0 obj<</Subtype/Link/Rect[126.0 367.2 336.8 380.2]/Border[0 0 0]/Dest[1749 0 R/XYZ 0 734 0]>>endobj
+214 0 obj<</Subtype/Link/Rect[108.0 354.0 245.8 367.0]/Border[0 0 0]/Dest[1753 0 R/XYZ 0 332 0]>>endobj
+215 0 obj<</Subtype/Link/Rect[108.0 340.8 315.8 353.8]/Border[0 0 0]/Dest[1755 0 R/XYZ 0 388 0]>>endobj
+216 0 obj<</Subtype/Link/Rect[108.0 327.6 290.1 340.6]/Border[0 0 0]/Dest[1757 0 R/XYZ 0 407 0]>>endobj
+217 0 obj<</Subtype/Link/Rect[108.0 314.4 270.5 327.4]/Border[0 0 0]/Dest[1759 0 R/XYZ 0 718 0]>>endobj
+218 0 obj<</Subtype/Link/Rect[108.0 301.2 281.8 314.2]/Border[0 0 0]/Dest[1759 0 R/XYZ 0 300 0]>>endobj
+219 0 obj<</Subtype/Link/Rect[108.0 288.0 276.6 301.0]/Border[0 0 0]/Dest[1761 0 R/XYZ 0 520 0]>>endobj
+220 0 obj<</Subtype/Link/Rect[108.0 274.8 221.7 287.8]/Border[0 0 0]/Dest[1761 0 R/XYZ 0 432 0]>>endobj
+221 0 obj<</Subtype/Link/Rect[72.0 248.4 241.6 261.4]/Border[0 0 0]/Dest[1763 0 R/XYZ 0 734 0]>>endobj
+222 0 obj<</Subtype/Link/Rect[108.0 235.2 267.8 248.2]/Border[0 0 0]/Dest[1763 0 R/XYZ 0 696 0]>>endobj
+223 0 obj<</Subtype/Link/Rect[108.0 222.0 211.3 235.0]/Border[0 0 0]/Dest[1763 0 R/XYZ 0 385 0]>>endobj
+224 0 obj<</Subtype/Link/Rect[126.0 208.8 181.0 221.8]/Border[0 0 0]/Dest[1763 0 R/XYZ 0 351 0]>>endobj
+225 0 obj<</Subtype/Link/Rect[126.0 195.6 190.8 208.6]/Border[0 0 0]/Dest[1763 0 R/XYZ 0 215 0]>>endobj
+226 0 obj<</Subtype/Link/Rect[126.0 182.4 193.8 195.4]/Border[0 0 0]/Dest[1765 0 R/XYZ 0 560 0]>>endobj
+227 0 obj<</Subtype/Link/Rect[108.0 169.2 282.1 182.2]/Border[0 0 0]/Dest[1765 0 R/XYZ 0 430 0]>>endobj
+228 0 obj<</Subtype/Link/Rect[126.0 156.0 211.5 169.0]/Border[0 0 0]/Dest[1765 0 R/XYZ 0 315 0]>>endobj
+229 0 obj<</Subtype/Link/Rect[126.0 142.8 184.0 155.8]/Border[0 0 0]/Dest[1767 0 R/XYZ 0 734 0]>>endobj
+230 0 obj<</Subtype/Link/Rect[72.0 116.4 252.6 129.4]/Border[0 0 0]/Dest[1769 0 R/XYZ 0 734 0]>>endobj
+231 0 obj<</Subtype/Link/Rect[72.0 90.0 255.6 103.0]/Border[0 0 0]/Dest[1771 0 R/XYZ 0 734 0]>>endobj
+232 0 obj<</Subtype/Link/Rect[108.0 76.8 190.8 89.8]/Border[0 0 0]/Dest[1771 0 R/XYZ 0 696 0]>>endobj
+233 0 obj<</Subtype/Link/Rect[108.0 63.6 197.8 76.6]/Border[0 0 0]/Dest[1771 0 R/XYZ 0 449 0]>>endobj
+234 0 obj[190 0 R
+191 0 R
+192 0 R
+193 0 R
+194 0 R
+195 0 R
+196 0 R
+197 0 R
+198 0 R
+199 0 R
+200 0 R
+201 0 R
+202 0 R
+203 0 R
+204 0 R
+205 0 R
+206 0 R
+207 0 R
+208 0 R
+209 0 R
+210 0 R
+211 0 R
+212 0 R
+213 0 R
+214 0 R
+215 0 R
+216 0 R
+217 0 R
+218 0 R
+219 0 R
+220 0 R
+221 0 R
+222 0 R
+223 0 R
+224 0 R
+225 0 R
+226 0 R
+227 0 R
+228 0 R
+229 0 R
+230 0 R
+231 0 R
+232 0 R
+233 0 R]endobj
+235 0 obj<</Subtype/Link/Rect[72.0 684.0 255.6 697.0]/Border[0 0 0]/Dest[1771 0 R/XYZ 0 734 0]>>endobj
+236 0 obj<</Subtype/Link/Rect[108.0 670.8 175.2 683.8]/Border[0 0 0]/Dest[1771 0 R/XYZ 0 189 0]>>endobj
+237 0 obj<</Subtype/Link/Rect[108.0 657.6 175.8 670.6]/Border[0 0 0]/Dest[1773 0 R/XYZ 0 639 0]>>endobj
+238 0 obj<</Subtype/Link/Rect[108.0 644.4 174.6 657.4]/Border[0 0 0]/Dest[1773 0 R/XYZ 0 458 0]>>endobj
+239 0 obj<</Subtype/Link/Rect[108.0 631.2 174.6 644.2]/Border[0 0 0]/Dest[1773 0 R/XYZ 0 383 0]>>endobj
+240 0 obj<</Subtype/Link/Rect[108.0 618.0 177.0 631.0]/Border[0 0 0]/Dest[1773 0 R/XYZ 0 215 0]>>endobj
+241 0 obj<</Subtype/Link/Rect[108.0 604.8 189.3 617.8]/Border[0 0 0]/Dest[1775 0 R/XYZ 0 734 0]>>endobj
+242 0 obj<</Subtype/Link/Rect[108.0 591.6 188.7 604.6]/Border[0 0 0]/Dest[1775 0 R/XYZ 0 605 0]>>endobj
+243 0 obj<</Subtype/Link/Rect[108.0 578.4 196.0 591.4]/Border[0 0 0]/Dest[1775 0 R/XYZ 0 530 0]>>endobj
+244 0 obj<</Subtype/Link/Rect[72.0 552.0 266.9 565.0]/Border[0 0 0]/Dest[1779 0 R/XYZ 0 734 0]>>endobj
+245 0 obj<</Subtype/Link/Rect[108.0 538.8 190.6 551.8]/Border[0 0 0]/Dest[1779 0 R/XYZ 0 696 0]>>endobj
+246 0 obj<</Subtype/Link/Rect[108.0 525.6 200.6 538.6]/Border[0 0 0]/Dest[1779 0 R/XYZ 0 423 0]>>endobj
+247 0 obj<</Subtype/Link/Rect[126.0 512.4 223.8 525.4]/Border[0 0 0]/Dest[1781 0 R/XYZ 0 734 0]>>endobj
+248 0 obj<</Subtype/Link/Rect[126.0 499.2 243.6 512.2]/Border[0 0 0]/Dest[1781 0 R/XYZ 0 635 0]>>endobj
+249 0 obj<</Subtype/Link/Rect[126.0 486.0 219.8 499.0]/Border[0 0 0]/Dest[1781 0 R/XYZ 0 564 0]>>endobj
+250 0 obj<</Subtype/Link/Rect[126.0 472.8 195.4 485.8]/Border[0 0 0]/Dest[1781 0 R/XYZ 0 492 0]>>endobj
+251 0 obj<</Subtype/Link/Rect[108.0 459.6 216.8 472.6]/Border[0 0 0]/Dest[1781 0 R/XYZ 0 328 0]>>endobj
+252 0 obj<</Subtype/Link/Rect[72.0 433.2 207.1 446.2]/Border[0 0 0]/Dest[1785 0 R/XYZ 0 734 0]>>endobj
+253 0 obj<</Subtype/Link/Rect[108.0 420.0 187.1 433.0]/Border[0 0 0]/Dest[1785 0 R/XYZ 0 696 0]>>endobj
+254 0 obj<</Subtype/Link/Rect[108.0 406.8 255.3 419.8]/Border[0 0 0]/Dest[1785 0 R/XYZ 0 621 0]>>endobj
+255 0 obj<</Subtype/Link/Rect[108.0 393.6 247.6 406.6]/Border[0 0 0]/Dest[1785 0 R/XYZ 0 405 0]>>endobj
+256 0 obj<</Subtype/Link/Rect[108.0 380.4 203.6 393.4]/Border[0 0 0]/Dest[1785 0 R/XYZ 0 150 0]>>endobj
+257 0 obj<</Subtype/Link/Rect[108.0 367.2 242.1 380.2]/Border[0 0 0]/Dest[1787 0 R/XYZ 0 596 0]>>endobj
+258 0 obj<</Subtype/Link/Rect[108.0 354.0 212.5 367.0]/Border[0 0 0]/Dest[1787 0 R/XYZ 0 290 0]>>endobj
+259 0 obj<</Subtype/Link/Rect[72.0 327.6 213.5 340.6]/Border[0 0 0]/Dest[1789 0 R/XYZ 0 734 0]>>endobj
+260 0 obj<</Subtype/Link/Rect[108.0 314.4 272.0 327.4]/Border[0 0 0]/Dest[1789 0 R/XYZ 0 696 0]>>endobj
+261 0 obj<</Subtype/Link/Rect[108.0 301.2 219.5 314.2]/Border[0 0 0]/Dest[1789 0 R/XYZ 0 397 0]>>endobj
+262 0 obj<</Subtype/Link/Rect[72.0 274.8 144.7 287.8]/Border[0 0 0]/Dest[1791 0 R/XYZ 0 734 0]>>endobj
+263 0 obj<</Subtype/Link/Rect[72.0 248.4 181.1 261.4]/Border[0 0 0]/Dest[1795 0 R/XYZ 0 734 0]>>endobj
+264 0 obj<</Subtype/Link/Rect[108.0 235.2 162.7 248.2]/Border[0 0 0]/Dest[1795 0 R/XYZ 0 655 0]>>endobj
+265 0 obj<</Subtype/Link/Rect[108.0 222.0 178.9 235.0]/Border[0 0 0]/Dest[1795 0 R/XYZ 0 408 0]>>endobj
+266 0 obj<</Subtype/Link/Rect[108.0 208.8 160.2 221.8]/Border[0 0 0]/Dest[1795 0 R/XYZ 0 293 0]>>endobj
+267 0 obj<</Subtype/Link/Rect[108.0 195.6 260.5 208.6]/Border[0 0 0]/Dest[1797 0 R/XYZ 0 228 0]>>endobj
+268 0 obj<</Subtype/Link/Rect[108.0 182.4 152.3 195.4]/Border[0 0 0]/Dest[1799 0 R/XYZ 0 734 0]>>endobj
+269 0 obj<</Subtype/Link/Rect[126.0 169.2 262.3 182.2]/Border[0 0 0]/Dest[1799 0 R/XYZ 0 700 0]>>endobj
+270 0 obj<</Subtype/Link/Rect[72.0 142.8 271.5 155.8]/Border[0 0 0]/Dest[1801 0 R/XYZ 0 734 0]>>endobj
+271 0 obj<</Subtype/Link/Rect[108.0 129.6 215.5 142.6]/Border[0 0 0]/Dest[1801 0 R/XYZ 0 668 0]>>endobj
+272 0 obj<</Subtype/Link/Rect[108.0 116.4 182.0 129.4]/Border[0 0 0]/Dest[1801 0 R/XYZ 0 461 0]>>endobj
+273 0 obj<</Subtype/Link/Rect[126.0 103.2 514.3 116.2]/Border[0 0 0]/Dest[1801 0 R/XYZ 0 427 0]>>endobj
+274 0 obj<</Subtype/Link/Rect[126.0 90.0 519.5 103.0]/Border[0 0 0]/Dest[1803 0 R/XYZ 0 734 0]>>endobj
+275 0 obj<</Subtype/Link/Rect[126.0 76.8 470.9 89.8]/Border[0 0 0]/Dest[1803 0 R/XYZ 0 523 0]>>endobj
+276 0 obj<</Subtype/Link/Rect[126.0 63.6 440.7 76.6]/Border[0 0 0]/Dest[1803 0 R/XYZ 0 408 0]>>endobj
+277 0 obj[235 0 R
+236 0 R
+237 0 R
+238 0 R
+239 0 R
+240 0 R
+241 0 R
+242 0 R
+243 0 R
+244 0 R
+245 0 R
+246 0 R
+247 0 R
+248 0 R
+249 0 R
+250 0 R
+251 0 R
+252 0 R
+253 0 R
+254 0 R
+255 0 R
+256 0 R
+257 0 R
+258 0 R
+259 0 R
+260 0 R
+261 0 R
+262 0 R
+263 0 R
+264 0 R
+265 0 R
+266 0 R
+267 0 R
+268 0 R
+269 0 R
+270 0 R
+271 0 R
+272 0 R
+273 0 R
+274 0 R
+275 0 R
+276 0 R]endobj
+278 0 obj<</Subtype/Link/Rect[72.0 684.0 271.5 697.0]/Border[0 0 0]/Dest[1801 0 R/XYZ 0 734 0]>>endobj
+279 0 obj<</Subtype/Link/Rect[108.0 670.8 248.2 683.8]/Border[0 0 0]/Dest[1803 0 R/XYZ 0 151 0]>>endobj
+280 0 obj<</Subtype/Link/Rect[126.0 657.6 333.5 670.6]/Border[0 0 0]/Dest[1803 0 R/XYZ 0 118 0]>>endobj
+281 0 obj<</Subtype/Link/Rect[126.0 644.4 332.5 657.4]/Border[0 0 0]/Dest[1805 0 R/XYZ 0 626 0]>>endobj
+282 0 obj<</Subtype/Link/Rect[126.0 631.2 316.3 644.2]/Border[0 0 0]/Dest[1805 0 R/XYZ 0 475 0]>>endobj
+283 0 obj<</Subtype/Link/Rect[126.0 618.0 282.1 631.0]/Border[0 0 0]/Dest[1805 0 R/XYZ 0 377 0]>>endobj
+284 0 obj<</Subtype/Link/Rect[126.0 604.8 296.5 617.8]/Border[0 0 0]/Dest[1805 0 R/XYZ 0 292 0]>>endobj
+285 0 obj<</Subtype/Link/Rect[108.0 591.6 206.7 604.6]/Border[0 0 0]/Dest[1805 0 R/XYZ 0 207 0]>>endobj
+286 0 obj<</Subtype/Link/Rect[108.0 578.4 267.8 591.4]/Border[0 0 0]/Dest[1807 0 R/XYZ 0 626 0]>>endobj
+287 0 obj<</Subtype/Link/Rect[72.0 552.0 246.2 565.0]/Border[0 0 0]/Dest[1809 0 R/XYZ 0 734 0]>>endobj
+288 0 obj<</Subtype/Link/Rect[108.0 538.8 291.9 551.8]/Border[0 0 0]/Dest[1809 0 R/XYZ 0 655 0]>>endobj
+289 0 obj<</Subtype/Link/Rect[126.0 525.6 213.4 538.6]/Border[0 0 0]/Dest[1809 0 R/XYZ 0 621 0]>>endobj
+290 0 obj<</Subtype/Link/Rect[126.0 512.4 273.9 525.4]/Border[0 0 0]/Dest[1809 0 R/XYZ 0 510 0]>>endobj
+291 0 obj<</Subtype/Link/Rect[108.0 499.2 337.1 512.2]/Border[0 0 0]/Dest[1811 0 R/XYZ 0 494 0]>>endobj
+292 0 obj<</Subtype/Link/Rect[108.0 486.0 226.9 499.0]/Border[0 0 0]/Dest[1811 0 R/XYZ 0 353 0]>>endobj
+293 0 obj<</Subtype/Link/Rect[108.0 472.8 256.8 485.8]/Border[0 0 0]/Dest[1813 0 R/XYZ 0 613 0]>>endobj
+294 0 obj<</Subtype/Link/Rect[126.0 459.6 265.0 472.6]/Border[0 0 0]/Dest[1813 0 R/XYZ 0 458 0]>>endobj
+295 0 obj<</Subtype/Link/Rect[126.0 446.4 313.3 459.4]/Border[0 0 0]/Dest[1815 0 R/XYZ 0 639 0]>>endobj
+296 0 obj<</Subtype/Link/Rect[72.0 420.0 204.0 433.0]/Border[0 0 0]/Dest[1817 0 R/XYZ 0 734 0]>>endobj
+297 0 obj<</Subtype/Link/Rect[108.0 406.8 187.1 419.8]/Border[0 0 0]/Dest[1817 0 R/XYZ 0 696 0]>>endobj
+298 0 obj<</Subtype/Link/Rect[108.0 393.6 188.0 406.6]/Border[0 0 0]/Dest[1817 0 R/XYZ 0 423 0]>>endobj
+299 0 obj<</Subtype/Link/Rect[108.0 380.4 190.5 393.4]/Border[0 0 0]/Dest[1817 0 R/XYZ 0 282 0]>>endobj
+300 0 obj<</Subtype/Link/Rect[108.0 367.2 195.4 380.2]/Border[0 0 0]/Dest[1819 0 R/XYZ 0 613 0]>>endobj
+301 0 obj<</Subtype/Link/Rect[108.0 354.0 267.8 367.0]/Border[0 0 0]/Dest[1819 0 R/XYZ 0 260 0]>>endobj
+302 0 obj<</Subtype/Link/Rect[108.0 340.8 166.4 353.8]/Border[0 0 0]/Dest[1819 0 R/XYZ 0 159 0]>>endobj
+303 0 obj<</Subtype/Link/Rect[72.0 314.4 225.7 327.4]/Border[0 0 0]/Dest[1821 0 R/XYZ 0 734 0]>>endobj
+304 0 obj<</Subtype/Link/Rect[108.0 301.2 187.1 314.2]/Border[0 0 0]/Dest[1821 0 R/XYZ 0 696 0]>>endobj
+305 0 obj<</Subtype/Link/Rect[108.0 288.0 190.2 301.0]/Border[0 0 0]/Dest[1821 0 R/XYZ 0 529 0]>>endobj
+306 0 obj<</Subtype/Link/Rect[108.0 274.8 156.0 287.8]/Border[0 0 0]/Dest[1821 0 R/XYZ 0 199 0]>>endobj
+307 0 obj<</Subtype/Link/Rect[126.0 261.6 186.2 274.6]/Border[0 0 0]/Dest[1821 0 R/XYZ 0 165 0]>>endobj
+308 0 obj<</Subtype/Link/Rect[126.0 248.4 186.2 261.4]/Border[0 0 0]/Dest[1823 0 R/XYZ 0 734 0]>>endobj
+309 0 obj<</Subtype/Link/Rect[126.0 235.2 186.2 248.2]/Border[0 0 0]/Dest[1823 0 R/XYZ 0 530 0]>>endobj
+310 0 obj<</Subtype/Link/Rect[126.0 222.0 186.2 235.0]/Border[0 0 0]/Dest[1825 0 R/XYZ 0 626 0]>>endobj
+311 0 obj<</Subtype/Link/Rect[126.0 208.8 186.2 221.8]/Border[0 0 0]/Dest[1825 0 R/XYZ 0 475 0]>>endobj
+312 0 obj<</Subtype/Link/Rect[126.0 195.6 186.2 208.6]/Border[0 0 0]/Dest[1825 0 R/XYZ 0 351 0]>>endobj
+313 0 obj<</Subtype/Link/Rect[126.0 182.4 186.2 195.4]/Border[0 0 0]/Dest[1827 0 R/XYZ 0 734 0]>>endobj
+314 0 obj<</Subtype/Link/Rect[126.0 169.2 186.2 182.2]/Border[0 0 0]/Dest[1827 0 R/XYZ 0 371 0]>>endobj
+315 0 obj<</Subtype/Link/Rect[126.0 156.0 186.2 169.0]/Border[0 0 0]/Dest[1829 0 R/XYZ 0 705 0]>>endobj
+316 0 obj<</Subtype/Link/Rect[126.0 142.8 197.2 155.8]/Border[0 0 0]/Dest[1829 0 R/XYZ 0 515 0]>>endobj
+317 0 obj<</Subtype/Link/Rect[126.0 129.6 197.2 142.6]/Border[0 0 0]/Dest[1829 0 R/XYZ 0 377 0]>>endobj
+318 0 obj<</Subtype/Link/Rect[108.0 116.4 226.9 129.4]/Border[0 0 0]/Dest[1829 0 R/XYZ 0 239 0]>>endobj
+319 0 obj[278 0 R
+279 0 R
+280 0 R
+281 0 R
+282 0 R
+283 0 R
+284 0 R
+285 0 R
+286 0 R
+287 0 R
+288 0 R
+289 0 R
+290 0 R
+291 0 R
+292 0 R
+293 0 R
+294 0 R
+295 0 R
+296 0 R
+297 0 R
+298 0 R
+299 0 R
+300 0 R
+301 0 R
+302 0 R
+303 0 R
+304 0 R
+305 0 R
+306 0 R
+307 0 R
+308 0 R
+309 0 R
+310 0 R
+311 0 R
+312 0 R
+313 0 R
+314 0 R
+315 0 R
+316 0 R
+317 0 R
+318 0 R]endobj
+320 0 obj<</S/URI/URI(http://www.samba.org/)>>endobj
+321 0 obj<</Subtype/Link/Rect[185.6 631.0 289.8 644.0]/Border[0 0 0]/A 320 0 R>>endobj
+322 0 obj<</S/URI/URI(mailto:jerry@samba.org)>>endobj
+323 0 obj<</Subtype/Link/Rect[72.0 617.8 148.4 630.8]/Border[0 0 0]/A 322 0 R>>endobj
+324 0 obj<</S/URI/URI(mailto:jelmer@samba.org)>>endobj
+325 0 obj<</Subtype/Link/Rect[160.3 617.8 246.8 630.8]/Border[0 0 0]/A 324 0 R>>endobj
+326 0 obj<</S/URI/URI(http://www.fsf.org/licenses/gpl.txt)>>endobj
+327 0 obj<</Subtype/Link/Rect[72.0 565.0 223.3 578.0]/Border[0 0 0]/A 326 0 R>>endobj
+328 0 obj<</Subtype/Link/Rect[78.4 499.0 170.1 512.0]/Border[0 0 0]/Dest[1501 0 R/XYZ 0 205 0]>>endobj
+329 0 obj<</Subtype/Link/Rect[116.2 485.8 259.9 498.8]/Border[0 0 0]/Dest[1509 0 R/XYZ 0 734 0]>>endobj
+330 0 obj<</Subtype/Link/Rect[160.5 472.6 302.9 485.6]/Border[0 0 0]/Dest[1509 0 R/XYZ 0 696 0]>>endobj
+331 0 obj<</Subtype/Link/Rect[160.5 459.4 248.5 472.4]/Border[0 0 0]/Dest[1509 0 R/XYZ 0 595 0]>>endobj
+332 0 obj<</Subtype/Link/Rect[160.5 446.2 367.0 459.2]/Border[0 0 0]/Dest[1511 0 R/XYZ 0 528 0]>>endobj
+333 0 obj<</Subtype/Link/Rect[160.5 433.0 316.3 446.0]/Border[0 0 0]/Dest[1511 0 R/XYZ 0 360 0]>>endobj
+334 0 obj<</Subtype/Link/Rect[160.5 419.8 503.0 432.8]/Border[0 0 0]/Dest[1511 0 R/XYZ 0 193 0]>>endobj
+335 0 obj<</Subtype/Link/Rect[160.5 406.6 287.8 419.6]/Border[0 0 0]/Dest[1513 0 R/XYZ 0 652 0]>>endobj
+336 0 obj<</Subtype/Link/Rect[116.2 393.4 410.5 406.4]/Border[0 0 0]/Dest[1517 0 R/XYZ 0 734 0]>>endobj
+337 0 obj<</Subtype/Link/Rect[160.5 380.2 211.5 393.2]/Border[0 0 0]/Dest[1517 0 R/XYZ 0 565 0]>>endobj
+338 0 obj<</Subtype/Link/Rect[160.5 367.0 348.1 380.0]/Border[0 0 0]/Dest[1519 0 R/XYZ 0 734 0]>>endobj
+339 0 obj<</Subtype/Link/Rect[160.5 353.8 360.7 366.8]/Border[0 0 0]/Dest[1519 0 R/XYZ 0 412 0]>>endobj
+340 0 obj<</Subtype/Link/Rect[160.5 340.6 220.1 353.6]/Border[0 0 0]/Dest[1519 0 R/XYZ 0 234 0]>>endobj
+341 0 obj<</Subtype/Link/Rect[160.5 327.4 458.7 340.4]/Border[0 0 0]/Dest[1521 0 R/XYZ 0 388 0]>>endobj
+342 0 obj<</Subtype/Link/Rect[160.5 314.2 268.4 327.2]/Border[0 0 0]/Dest[1523 0 R/XYZ 0 705 0]>>endobj
+343 0 obj<</Subtype/Link/Rect[116.2 301.0 237.6 314.0]/Border[0 0 0]/Dest[1525 0 R/XYZ 0 734 0]>>endobj
+344 0 obj<</Subtype/Link/Rect[160.5 287.8 218.2 300.8]/Border[0 0 0]/Dest[1525 0 R/XYZ 0 696 0]>>endobj
+345 0 obj<</Subtype/Link/Rect[160.5 274.6 302.9 287.6]/Border[0 0 0]/Dest[1525 0 R/XYZ 0 449 0]>>endobj
+346 0 obj<</Subtype/Link/Rect[160.5 261.4 280.6 274.4]/Border[0 0 0]/Dest[1527 0 R/XYZ 0 163 0]>>endobj
+347 0 obj<</Subtype/Link/Rect[160.5 248.2 205.7 261.2]/Border[0 0 0]/Dest[1529 0 R/XYZ 0 362 0]>>endobj
+348 0 obj<</Subtype/Link/Rect[160.5 235.0 184.0 248.0]/Border[0 0 0]/Dest[1529 0 R/XYZ 0 273 0]>>endobj
+349 0 obj<</Subtype/Link/Rect[160.5 221.8 190.8 234.8]/Border[0 0 0]/Dest[1529 0 R/XYZ 0 198 0]>>endobj
+350 0 obj<</Subtype/Link/Rect[160.5 208.6 196.9 221.6]/Border[0 0 0]/Dest[1543 0 R/XYZ 0 708 0]>>endobj
+351 0 obj<</Subtype/Link/Rect[160.5 195.4 250.6 208.4]/Border[0 0 0]/Dest[1545 0 R/XYZ 0 129 0]>>endobj
+352 0 obj<</Subtype/Link/Rect[82.1 182.2 170.4 195.2]/Border[0 0 0]/Dest[1547 0 R/XYZ 0 539 0]>>endobj
+353 0 obj<</Subtype/Link/Rect[116.2 169.0 252.5 182.0]/Border[0 0 0]/Dest[1555 0 R/XYZ 0 734 0]>>endobj
+354 0 obj<</Subtype/Link/Rect[160.5 155.8 248.2 168.8]/Border[0 0 0]/Dest[1555 0 R/XYZ 0 523 0]>>endobj
+355 0 obj<</Subtype/Link/Rect[160.5 142.6 269.6 155.6]/Border[0 0 0]/Dest[1555 0 R/XYZ 0 249 0]>>endobj
+356 0 obj<</Subtype/Link/Rect[160.5 129.4 247.9 142.4]/Border[0 0 0]/Dest[1557 0 R/XYZ 0 679 0]>>endobj
+357 0 obj<</Subtype/Link/Rect[116.2 116.2 392.8 129.2]/Border[0 0 0]/Dest[1559 0 R/XYZ 0 734 0]>>endobj
+358 0 obj<</Subtype/Link/Rect[116.2 103.0 367.1 116.0]/Border[0 0 0]/Dest[1563 0 R/XYZ 0 734 0]>>endobj
+359 0 obj<</Subtype/Link/Rect[160.5 89.8 257.0 102.8]/Border[0 0 0]/Dest[1563 0 R/XYZ 0 672 0]>>endobj
+360 0 obj<</Subtype/Link/Rect[160.5 76.6 217.0 89.6]/Border[0 0 0]/Dest[1563 0 R/XYZ 0 584 0]>>endobj
+361 0 obj<</Subtype/Link/Rect[160.5 63.4 353.3 76.4]/Border[0 0 0]/Dest[1565 0 R/XYZ 0 734 0]>>endobj
+362 0 obj[321 0 R
+323 0 R
+325 0 R
+327 0 R
+328 0 R
+329 0 R
+330 0 R
+331 0 R
+332 0 R
+333 0 R
+334 0 R
+335 0 R
+336 0 R
+337 0 R
+338 0 R
+339 0 R
+340 0 R
+341 0 R
+342 0 R
+343 0 R
+344 0 R
+345 0 R
+346 0 R
+347 0 R
+348 0 R
+349 0 R
+350 0 R
+351 0 R
+352 0 R
+353 0 R
+354 0 R
+355 0 R
+356 0 R
+357 0 R
+358 0 R
+359 0 R
+360 0 R
+361 0 R]endobj
+363 0 obj<</Subtype/Link/Rect[160.5 721.0 467.3 734.0]/Border[0 0 0]/Dest[1567 0 R/XYZ 0 665 0]>>endobj
+364 0 obj<</Subtype/Link/Rect[160.5 707.8 299.2 720.8]/Border[0 0 0]/Dest[1571 0 R/XYZ 0 175 0]>>endobj
+365 0 obj<</Subtype/Link/Rect[160.5 694.6 288.8 707.6]/Border[0 0 0]/Dest[1575 0 R/XYZ 0 565 0]>>endobj
+366 0 obj<</Subtype/Link/Rect[160.5 681.4 280.9 694.4]/Border[0 0 0]/Dest[1577 0 R/XYZ 0 560 0]>>endobj
+367 0 obj<</Subtype/Link/Rect[160.5 668.2 326.4 681.2]/Border[0 0 0]/Dest[1581 0 R/XYZ 0 283 0]>>endobj
+368 0 obj<</Subtype/Link/Rect[160.5 655.0 459.7 668.0]/Border[0 0 0]/Dest[1593 0 R/XYZ 0 415 0]>>endobj
+369 0 obj<</Subtype/Link/Rect[116.2 641.8 485.4 654.8]/Border[0 0 0]/Dest[1597 0 R/XYZ 0 734 0]>>endobj
+370 0 obj<</Subtype/Link/Rect[160.5 628.6 257.0 641.6]/Border[0 0 0]/Dest[1597 0 R/XYZ 0 672 0]>>endobj
+371 0 obj<</Subtype/Link/Rect[160.5 615.4 217.0 628.4]/Border[0 0 0]/Dest[1597 0 R/XYZ 0 597 0]>>endobj
+372 0 obj<</Subtype/Link/Rect[160.5 602.2 396.4 615.2]/Border[0 0 0]/Dest[1597 0 R/XYZ 0 225 0]>>endobj
+373 0 obj<</Subtype/Link/Rect[160.5 589.0 430.3 602.0]/Border[0 0 0]/Dest[1599 0 R/XYZ 0 524 0]>>endobj
+374 0 obj<</Subtype/Link/Rect[160.5 575.8 304.1 588.8]/Border[0 0 0]/Dest[1599 0 R/XYZ 0 323 0]>>endobj
+375 0 obj<</Subtype/Link/Rect[116.2 562.6 266.6 575.6]/Border[0 0 0]/Dest[1603 0 R/XYZ 0 734 0]>>endobj
+376 0 obj<</Subtype/Link/Rect[160.5 549.4 356.7 562.4]/Border[0 0 0]/Dest[1603 0 R/XYZ 0 551 0]>>endobj
+377 0 obj<</Subtype/Link/Rect[160.5 536.2 357.9 549.2]/Border[0 0 0]/Dest[1603 0 R/XYZ 0 444 0]>>endobj
+378 0 obj<</Subtype/Link/Rect[160.5 523.0 233.2 536.0]/Border[0 0 0]/Dest[1603 0 R/XYZ 0 267 0]>>endobj
+379 0 obj<</Subtype/Link/Rect[160.5 509.8 274.2 522.8]/Border[0 0 0]/Dest[1605 0 R/XYZ 0 580 0]>>endobj
+380 0 obj<</Subtype/Link/Rect[160.5 496.6 291.3 509.6]/Border[0 0 0]/Dest[1605 0 R/XYZ 0 264 0]>>endobj
+381 0 obj<</Subtype/Link/Rect[160.5 483.4 260.7 496.4]/Border[0 0 0]/Dest[1607 0 R/XYZ 0 734 0]>>endobj
+382 0 obj<</Subtype/Link/Rect[160.5 470.2 262.3 483.2]/Border[0 0 0]/Dest[1607 0 R/XYZ 0 645 0]>>endobj
+383 0 obj<</Subtype/Link/Rect[160.5 457.0 188.3 470.0]/Border[0 0 0]/Dest[1607 0 R/XYZ 0 570 0]>>endobj
+384 0 obj<</Subtype/Link/Rect[116.2 443.8 308.7 456.8]/Border[0 0 0]/Dest[1609 0 R/XYZ 0 734 0]>>endobj
+385 0 obj<</Subtype/Link/Rect[160.5 430.6 335.3 443.6]/Border[0 0 0]/Dest[1609 0 R/XYZ 0 672 0]>>endobj
+386 0 obj<</Subtype/Link/Rect[160.5 417.4 322.8 430.4]/Border[0 0 0]/Dest[1611 0 R/XYZ 0 494 0]>>endobj
+387 0 obj<</Subtype/Link/Rect[160.5 404.2 345.7 417.2]/Border[0 0 0]/Dest[1611 0 R/XYZ 0 405 0]>>endobj
+388 0 obj<</Subtype/Link/Rect[85.7 391.0 190.2 404.0]/Border[0 0 0]/Dest[1613 0 R/XYZ 0 641 0]>>endobj
+389 0 obj<</Subtype/Link/Rect[121.8 377.8 331.4 390.8]/Border[0 0 0]/Dest[1623 0 R/XYZ 0 734 0]>>endobj
+390 0 obj<</Subtype/Link/Rect[166.0 364.6 202.4 377.6]/Border[0 0 0]/Dest[1623 0 R/XYZ 0 672 0]>>endobj
+391 0 obj<</Subtype/Link/Rect[166.0 351.4 367.4 364.4]/Border[0 0 0]/Dest[1623 0 R/XYZ 0 439 0]>>endobj
+392 0 obj<</Subtype/Link/Rect[166.0 338.2 420.2 351.2]/Border[0 0 0]/Dest[1627 0 R/XYZ 0 339 0]>>endobj
+393 0 obj<</Subtype/Link/Rect[166.0 325.0 532.1 338.0]/Border[0 0 0]/Dest[1635 0 R/XYZ 0 670 0]>>endobj
+394 0 obj<</Subtype/Link/Rect[144.0 311.8 173.9 324.8]/Border[0 0 0]/Dest[1635 0 R/XYZ 0 670 0]>>endobj
+395 0 obj<</Subtype/Link/Rect[166.0 298.6 536.9 311.6]/Border[0 0 0]/Dest[1635 0 R/XYZ 0 126 0]>>endobj
+396 0 obj<</Subtype/Link/Rect[166.0 285.4 223.1 298.4]/Border[0 0 0]/Dest[1641 0 R/XYZ 0 263 0]>>endobj
+397 0 obj<</Subtype/Link/Rect[121.8 272.2 394.0 285.2]/Border[0 0 0]/Dest[1643 0 R/XYZ 0 734 0]>>endobj
+398 0 obj<</Subtype/Link/Rect[166.0 259.0 483.2 272.0]/Border[0 0 0]/Dest[1643 0 R/XYZ 0 672 0]>>endobj
+399 0 obj<</Subtype/Link/Rect[166.0 245.8 360.0 258.8]/Border[0 0 0]/Dest[1643 0 R/XYZ 0 537 0]>>endobj
+400 0 obj<</Subtype/Link/Rect[166.0 232.6 270.2 245.6]/Border[0 0 0]/Dest[1643 0 R/XYZ 0 369 0]>>endobj
+401 0 obj<</Subtype/Link/Rect[166.0 219.4 332.5 232.4]/Border[0 0 0]/Dest[1645 0 R/XYZ 0 705 0]>>endobj
+402 0 obj<</Subtype/Link/Rect[166.0 206.2 341.7 219.2]/Border[0 0 0]/Dest[1647 0 R/XYZ 0 718 0]>>endobj
+403 0 obj<</Subtype/Link/Rect[166.0 193.0 438.5 206.0]/Border[0 0 0]/Dest[1647 0 R/XYZ 0 287 0]>>endobj
+404 0 obj<</Subtype/Link/Rect[166.0 179.8 428.8 192.8]/Border[0 0 0]/Dest[1651 0 R/XYZ 0 652 0]>>endobj
+405 0 obj<</Subtype/Link/Rect[121.8 166.6 437.7 179.6]/Border[0 0 0]/Dest[1653 0 R/XYZ 0 734 0]>>endobj
+406 0 obj<</Subtype/Link/Rect[166.0 153.4 243.3 166.4]/Border[0 0 0]/Dest[1653 0 R/XYZ 0 672 0]>>endobj
+407 0 obj<</Subtype/Link/Rect[166.0 140.2 286.4 153.2]/Border[0 0 0]/Dest[1655 0 R/XYZ 0 148 0]>>endobj
+408 0 obj<</Subtype/Link/Rect[166.0 127.0 309.9 140.0]/Border[0 0 0]/Dest[1657 0 R/XYZ 0 705 0]>>endobj
+409 0 obj<</Subtype/Link/Rect[121.8 113.8 386.0 126.8]/Border[0 0 0]/Dest[1659 0 R/XYZ 0 734 0]>>endobj
+410 0 obj<</Subtype/Link/Rect[166.0 100.6 221.3 113.6]/Border[0 0 0]/Dest[1659 0 R/XYZ 0 672 0]>>endobj
+411 0 obj<</Subtype/Link/Rect[121.8 87.4 198.8 100.4]/Border[0 0 0]/Dest[1663 0 R/XYZ 0 734 0]>>endobj
+412 0 obj<</Subtype/Link/Rect[166.0 74.2 223.8 87.2]/Border[0 0 0]/Dest[1663 0 R/XYZ 0 696 0]>>endobj
+413 0 obj<</Subtype/Link/Rect[166.0 61.0 231.1 74.0]/Border[0 0 0]/Dest[1663 0 R/XYZ 0 317 0]>>endobj
+414 0 obj[363 0 R
+364 0 R
+365 0 R
+366 0 R
+367 0 R
+368 0 R
+369 0 R
+370 0 R
+371 0 R
+372 0 R
+373 0 R
+374 0 R
+375 0 R
+376 0 R
+377 0 R
+378 0 R
+379 0 R
+380 0 R
+381 0 R
+382 0 R
+383 0 R
+384 0 R
+385 0 R
+386 0 R
+387 0 R
+388 0 R
+389 0 R
+390 0 R
+391 0 R
+392 0 R
+393 0 R
+394 0 R
+395 0 R
+396 0 R
+397 0 R
+398 0 R
+399 0 R
+400 0 R
+401 0 R
+402 0 R
+403 0 R
+404 0 R
+405 0 R
+406 0 R
+407 0 R
+408 0 R
+409 0 R
+410 0 R
+411 0 R
+412 0 R
+413 0 R]endobj
+415 0 obj<</Subtype/Link/Rect[166.0 721.0 260.4 734.0]/Border[0 0 0]/Dest[1673 0 R/XYZ 0 692 0]>>endobj
+416 0 obj<</Subtype/Link/Rect[166.0 707.8 213.4 720.8]/Border[0 0 0]/Dest[1675 0 R/XYZ 0 397 0]>>endobj
+417 0 obj<</Subtype/Link/Rect[121.8 694.6 229.0 707.6]/Border[0 0 0]/Dest[1685 0 R/XYZ 0 734 0]>>endobj
+418 0 obj<</Subtype/Link/Rect[166.0 681.4 223.8 694.4]/Border[0 0 0]/Dest[1685 0 R/XYZ 0 696 0]>>endobj
+419 0 obj<</Subtype/Link/Rect[166.0 668.2 325.6 681.2]/Border[0 0 0]/Dest[1685 0 R/XYZ 0 463 0]>>endobj
+420 0 obj<</Subtype/Link/Rect[166.0 655.0 277.2 668.0]/Border[0 0 0]/Dest[1689 0 R/XYZ 0 276 0]>>endobj
+421 0 obj<</Subtype/Link/Rect[166.0 641.8 314.8 654.8]/Border[0 0 0]/Dest[1701 0 R/XYZ 0 546 0]>>endobj
+422 0 obj<</Subtype/Link/Rect[166.0 628.6 367.1 641.6]/Border[0 0 0]/Dest[1705 0 R/XYZ 0 177 0]>>endobj
+423 0 obj<</Subtype/Link/Rect[166.0 615.4 382.9 628.4]/Border[0 0 0]/Dest[1713 0 R/XYZ 0 362 0]>>endobj
+424 0 obj<</Subtype/Link/Rect[166.0 602.2 324.1 615.2]/Border[0 0 0]/Dest[1715 0 R/XYZ 0 527 0]>>endobj
+425 0 obj<</Subtype/Link/Rect[121.8 589.0 405.0 602.0]/Border[0 0 0]/Dest[1719 0 R/XYZ 0 734 0]>>endobj
+426 0 obj<</Subtype/Link/Rect[166.0 575.8 206.0 588.8]/Border[0 0 0]/Dest[1719 0 R/XYZ 0 672 0]>>endobj
+427 0 obj<</Subtype/Link/Rect[166.0 562.6 223.8 575.6]/Border[0 0 0]/Dest[1719 0 R/XYZ 0 544 0]>>endobj
+428 0 obj<</Subtype/Link/Rect[166.0 549.4 273.9 562.4]/Border[0 0 0]/Dest[1719 0 R/XYZ 0 231 0]>>endobj
+429 0 obj<</Subtype/Link/Rect[166.0 536.2 260.4 549.2]/Border[0 0 0]/Dest[1721 0 R/XYZ 0 409 0]>>endobj
+430 0 obj<</Subtype/Link/Rect[166.0 523.0 303.8 536.0]/Border[0 0 0]/Dest[1725 0 R/XYZ 0 245 0]>>endobj
+431 0 obj<</Subtype/Link/Rect[166.0 509.8 218.9 522.8]/Border[0 0 0]/Dest[1743 0 R/XYZ 0 555 0]>>endobj
+432 0 obj<</Subtype/Link/Rect[166.0 496.6 218.9 509.6]/Border[0 0 0]/Dest[1743 0 R/XYZ 0 335 0]>>endobj
+433 0 obj<</Subtype/Link/Rect[121.8 483.4 253.1 496.4]/Border[0 0 0]/Dest[1745 0 R/XYZ 0 734 0]>>endobj
+434 0 obj<</Subtype/Link/Rect[166.0 470.2 265.9 483.2]/Border[0 0 0]/Dest[1745 0 R/XYZ 0 696 0]>>endobj
+435 0 obj<</Subtype/Link/Rect[166.0 457.0 290.1 470.0]/Border[0 0 0]/Dest[1745 0 R/XYZ 0 463 0]>>endobj
+436 0 obj<</Subtype/Link/Rect[166.0 443.8 254.0 456.8]/Border[0 0 0]/Dest[1747 0 R/XYZ 0 734 0]>>endobj
+437 0 obj<</Subtype/Link/Rect[166.0 430.6 278.1 443.6]/Border[0 0 0]/Dest[1747 0 R/XYZ 0 381 0]>>endobj
+438 0 obj<</Subtype/Link/Rect[166.0 417.4 280.0 430.4]/Border[0 0 0]/Dest[1753 0 R/XYZ 0 332 0]>>endobj
+439 0 obj<</Subtype/Link/Rect[166.0 404.2 348.7 417.2]/Border[0 0 0]/Dest[1755 0 R/XYZ 0 388 0]>>endobj
+440 0 obj<</Subtype/Link/Rect[166.0 391.0 323.1 404.0]/Border[0 0 0]/Dest[1757 0 R/XYZ 0 407 0]>>endobj
+441 0 obj<</Subtype/Link/Rect[166.0 377.8 309.0 390.8]/Border[0 0 0]/Dest[1759 0 R/XYZ 0 718 0]>>endobj
+442 0 obj<</Subtype/Link/Rect[166.0 364.6 318.5 377.6]/Border[0 0 0]/Dest[1759 0 R/XYZ 0 300 0]>>endobj
+443 0 obj<</Subtype/Link/Rect[171.5 351.4 315.7 364.4]/Border[0 0 0]/Dest[1761 0 R/XYZ 0 520 0]>>endobj
+444 0 obj<</Subtype/Link/Rect[171.5 338.2 257.7 351.2]/Border[0 0 0]/Dest[1761 0 R/XYZ 0 432 0]>>endobj
+445 0 obj<</Subtype/Link/Rect[121.8 325.0 228.4 338.0]/Border[0 0 0]/Dest[1763 0 R/XYZ 0 734 0]>>endobj
+446 0 obj<</Subtype/Link/Rect[166.0 311.8 305.6 324.8]/Border[0 0 0]/Dest[1763 0 R/XYZ 0 696 0]>>endobj
+447 0 obj<</Subtype/Link/Rect[166.0 298.6 246.7 311.6]/Border[0 0 0]/Dest[1763 0 R/XYZ 0 385 0]>>endobj
+448 0 obj<</Subtype/Link/Rect[166.0 285.4 317.5 298.4]/Border[0 0 0]/Dest[1765 0 R/XYZ 0 430 0]>>endobj
+449 0 obj<</Subtype/Link/Rect[121.8 272.2 236.3 285.2]/Border[0 0 0]/Dest[1769 0 R/XYZ 0 734 0]>>endobj
+450 0 obj<</Subtype/Link/Rect[121.8 259.0 242.4 272.0]/Border[0 0 0]/Dest[1771 0 R/XYZ 0 734 0]>>endobj
+451 0 obj<</Subtype/Link/Rect[166.0 245.8 227.4 258.8]/Border[0 0 0]/Dest[1771 0 R/XYZ 0 696 0]>>endobj
+452 0 obj<</Subtype/Link/Rect[166.0 232.6 232.6 245.6]/Border[0 0 0]/Dest[1771 0 R/XYZ 0 449 0]>>endobj
+453 0 obj<</Subtype/Link/Rect[166.0 219.4 210.6 232.4]/Border[0 0 0]/Dest[1771 0 R/XYZ 0 189 0]>>endobj
+454 0 obj<</Subtype/Link/Rect[166.0 206.2 210.0 219.2]/Border[0 0 0]/Dest[1773 0 R/XYZ 0 639 0]>>endobj
+455 0 obj<</Subtype/Link/Rect[166.0 193.0 209.4 206.0]/Border[0 0 0]/Dest[1773 0 R/XYZ 0 458 0]>>endobj
+456 0 obj<</Subtype/Link/Rect[166.0 179.8 211.2 192.8]/Border[0 0 0]/Dest[1773 0 R/XYZ 0 383 0]>>endobj
+457 0 obj<</Subtype/Link/Rect[166.0 166.6 213.1 179.6]/Border[0 0 0]/Dest[1773 0 R/XYZ 0 215 0]>>endobj
+458 0 obj<</Subtype/Link/Rect[166.0 153.4 224.1 166.4]/Border[0 0 0]/Dest[1775 0 R/XYZ 0 734 0]>>endobj
+459 0 obj<</Subtype/Link/Rect[166.0 140.2 222.8 153.2]/Border[0 0 0]/Dest[1775 0 R/XYZ 0 605 0]>>endobj
+460 0 obj<</Subtype/Link/Rect[171.5 127.0 232.0 140.0]/Border[0 0 0]/Dest[1775 0 R/XYZ 0 530 0]>>endobj
+461 0 obj<</Subtype/Link/Rect[121.8 113.8 255.0 126.8]/Border[0 0 0]/Dest[1779 0 R/XYZ 0 734 0]>>endobj
+462 0 obj<</Subtype/Link/Rect[166.0 100.6 224.6 113.6]/Border[0 0 0]/Dest[1779 0 R/XYZ 0 696 0]>>endobj
+463 0 obj<</Subtype/Link/Rect[166.0 87.4 233.5 100.4]/Border[0 0 0]/Dest[1779 0 R/XYZ 0 423 0]>>endobj
+464 0 obj<</Subtype/Link/Rect[166.0 74.2 250.3 87.2]/Border[0 0 0]/Dest[1781 0 R/XYZ 0 328 0]>>endobj
+465 0 obj<</Subtype/Link/Rect[121.8 61.0 196.3 74.0]/Border[0 0 0]/Dest[1785 0 R/XYZ 0 734 0]>>endobj
+466 0 obj[415 0 R
+416 0 R
+417 0 R
+418 0 R
+419 0 R
+420 0 R
+421 0 R
+422 0 R
+423 0 R
+424 0 R
+425 0 R
+426 0 R
+427 0 R
+428 0 R
+429 0 R
+430 0 R
+431 0 R
+432 0 R
+433 0 R
+434 0 R
+435 0 R
+436 0 R
+437 0 R
+438 0 R
+439 0 R
+440 0 R
+441 0 R
+442 0 R
+443 0 R
+444 0 R
+445 0 R
+446 0 R
+447 0 R
+448 0 R
+449 0 R
+450 0 R
+451 0 R
+452 0 R
+453 0 R
+454 0 R
+455 0 R
+456 0 R
+457 0 R
+458 0 R
+459 0 R
+460 0 R
+461 0 R
+462 0 R
+463 0 R
+464 0 R
+465 0 R]endobj
+467 0 obj<</Subtype/Link/Rect[166.0 721.0 223.8 734.0]/Border[0 0 0]/Dest[1785 0 R/XYZ 0 696 0]>>endobj
+468 0 obj<</Subtype/Link/Rect[166.0 707.8 292.5 720.8]/Border[0 0 0]/Dest[1785 0 R/XYZ 0 621 0]>>endobj
+469 0 obj<</Subtype/Link/Rect[166.0 694.6 284.9 707.6]/Border[0 0 0]/Dest[1785 0 R/XYZ 0 405 0]>>endobj
+470 0 obj<</Subtype/Link/Rect[166.0 681.4 240.3 694.4]/Border[0 0 0]/Dest[1785 0 R/XYZ 0 150 0]>>endobj
+471 0 obj<</Subtype/Link/Rect[166.0 668.2 280.0 681.2]/Border[0 0 0]/Dest[1787 0 R/XYZ 0 596 0]>>endobj
+472 0 obj<</Subtype/Link/Rect[166.0 655.0 249.7 668.0]/Border[0 0 0]/Dest[1787 0 R/XYZ 0 290 0]>>endobj
+473 0 obj<</Subtype/Link/Rect[121.8 641.8 203.9 654.8]/Border[0 0 0]/Dest[1789 0 R/XYZ 0 734 0]>>endobj
+474 0 obj<</Subtype/Link/Rect[166.0 628.6 311.1 641.6]/Border[0 0 0]/Dest[1789 0 R/XYZ 0 696 0]>>endobj
+475 0 obj<</Subtype/Link/Rect[166.0 615.4 257.4 628.4]/Border[0 0 0]/Dest[1789 0 R/XYZ 0 397 0]>>endobj
+476 0 obj<</Subtype/Link/Rect[85.1 602.2 138.6 615.2]/Border[0 0 0]/Dest[1789 0 R/XYZ 0 178 0]>>endobj
+477 0 obj<</Subtype/Link/Rect[121.8 589.0 172.2 602.0]/Border[0 0 0]/Dest[1795 0 R/XYZ 0 734 0]>>endobj
+478 0 obj<</Subtype/Link/Rect[166.0 575.8 198.1 588.8]/Border[0 0 0]/Dest[1795 0 R/XYZ 0 655 0]>>endobj
+479 0 obj<</Subtype/Link/Rect[166.0 562.6 213.7 575.6]/Border[0 0 0]/Dest[1795 0 R/XYZ 0 408 0]>>endobj
+480 0 obj<</Subtype/Link/Rect[166.0 549.4 194.4 562.4]/Border[0 0 0]/Dest[1795 0 R/XYZ 0 293 0]>>endobj
+481 0 obj<</Subtype/Link/Rect[166.0 536.2 296.5 549.2]/Border[0 0 0]/Dest[1797 0 R/XYZ 0 228 0]>>endobj
+482 0 obj<</Subtype/Link/Rect[166.0 523.0 185.9 536.0]/Border[0 0 0]/Dest[1799 0 R/XYZ 0 734 0]>>endobj
+483 0 obj<</Subtype/Link/Rect[121.8 509.8 257.1 522.8]/Border[0 0 0]/Dest[1801 0 R/XYZ 0 734 0]>>endobj
+484 0 obj<</Subtype/Link/Rect[166.0 496.6 252.2 509.6]/Border[0 0 0]/Dest[1801 0 R/XYZ 0 668 0]>>endobj
+485 0 obj<</Subtype/Link/Rect[166.0 483.4 217.3 496.4]/Border[0 0 0]/Dest[1801 0 R/XYZ 0 461 0]>>endobj
+486 0 obj<</Subtype/Link/Rect[166.0 470.2 281.8 483.2]/Border[0 0 0]/Dest[1803 0 R/XYZ 0 151 0]>>endobj
+487 0 obj<</Subtype/Link/Rect[166.0 457.0 241.6 470.0]/Border[0 0 0]/Dest[1805 0 R/XYZ 0 207 0]>>endobj
+488 0 obj<</Subtype/Link/Rect[166.0 443.8 301.9 456.8]/Border[0 0 0]/Dest[1807 0 R/XYZ 0 626 0]>>endobj
+489 0 obj<</Subtype/Link/Rect[121.8 430.6 231.7 443.6]/Border[0 0 0]/Dest[1809 0 R/XYZ 0 734 0]>>endobj
+490 0 obj<</Subtype/Link/Rect[166.0 417.4 325.5 430.4]/Border[0 0 0]/Dest[1809 0 R/XYZ 0 655 0]>>endobj
+491 0 obj<</Subtype/Link/Rect[166.0 404.2 373.1 417.2]/Border[0 0 0]/Dest[1811 0 R/XYZ 0 494 0]>>endobj
+492 0 obj<</Subtype/Link/Rect[166.0 391.0 262.9 404.0]/Border[0 0 0]/Dest[1811 0 R/XYZ 0 353 0]>>endobj
+493 0 obj<</Subtype/Link/Rect[166.0 377.8 292.8 390.8]/Border[0 0 0]/Dest[1813 0 R/XYZ 0 613 0]>>endobj
+494 0 obj<</Subtype/Link/Rect[121.8 364.6 193.2 377.6]/Border[0 0 0]/Dest[1817 0 R/XYZ 0 734 0]>>endobj
+495 0 obj<</Subtype/Link/Rect[166.0 351.4 223.8 364.4]/Border[0 0 0]/Dest[1817 0 R/XYZ 0 696 0]>>endobj
+496 0 obj<</Subtype/Link/Rect[166.0 338.2 224.7 351.2]/Border[0 0 0]/Dest[1817 0 R/XYZ 0 423 0]>>endobj
+497 0 obj<</Subtype/Link/Rect[166.0 325.0 225.9 338.0]/Border[0 0 0]/Dest[1817 0 R/XYZ 0 282 0]>>endobj
+498 0 obj<</Subtype/Link/Rect[166.0 311.8 234.4 324.8]/Border[0 0 0]/Dest[1819 0 R/XYZ 0 613 0]>>endobj
+499 0 obj<</Subtype/Link/Rect[166.0 298.6 305.0 311.6]/Border[0 0 0]/Dest[1819 0 R/XYZ 0 260 0]>>endobj
+500 0 obj<</Subtype/Link/Rect[166.0 285.4 203.6 298.4]/Border[0 0 0]/Dest[1819 0 R/XYZ 0 159 0]>>endobj
+501 0 obj<</Subtype/Link/Rect[121.8 272.2 213.7 285.2]/Border[0 0 0]/Dest[1821 0 R/XYZ 0 734 0]>>endobj
+502 0 obj<</Subtype/Link/Rect[166.0 259.0 223.8 272.0]/Border[0 0 0]/Dest[1821 0 R/XYZ 0 696 0]>>endobj
+503 0 obj<</Subtype/Link/Rect[166.0 245.8 224.4 258.8]/Border[0 0 0]/Dest[1821 0 R/XYZ 0 529 0]>>endobj
+504 0 obj<</Subtype/Link/Rect[166.0 232.6 191.4 245.6]/Border[0 0 0]/Dest[1821 0 R/XYZ 0 199 0]>>endobj
+505 0 obj<</Subtype/Link/Rect[166.0 219.4 263.5 232.4]/Border[0 0 0]/Dest[1829 0 R/XYZ 0 239 0]>>endobj
+506 0 obj[467 0 R
+468 0 R
+469 0 R
+470 0 R
+471 0 R
+472 0 R
+473 0 R
+474 0 R
+475 0 R
+476 0 R
+477 0 R
+478 0 R
+479 0 R
+480 0 R
+481 0 R
+482 0 R
+483 0 R
+484 0 R
+485 0 R
+486 0 R
+487 0 R
+488 0 R
+489 0 R
+490 0 R
+491 0 R
+492 0 R
+493 0 R
+494 0 R
+495 0 R
+496 0 R
+497 0 R
+498 0 R
+499 0 R
+500 0 R
+501 0 R
+502 0 R
+503 0 R
+504 0 R
+505 0 R]endobj
+507 0 obj<</Subtype/Link/Rect[80.2 631.0 223.9 644.0]/Border[0 0 0]/Dest[1509 0 R/XYZ 0 734 0]>>endobj
+508 0 obj<</Subtype/Link/Rect[124.5 617.8 266.9 630.8]/Border[0 0 0]/Dest[1509 0 R/XYZ 0 696 0]>>endobj
+509 0 obj<</Subtype/Link/Rect[124.5 604.6 212.5 617.6]/Border[0 0 0]/Dest[1509 0 R/XYZ 0 595 0]>>endobj
+510 0 obj<</Subtype/Link/Rect[168.8 591.4 279.1 604.4]/Border[0 0 0]/Dest[1509 0 R/XYZ 0 506 0]>>endobj
+511 0 obj<</Subtype/Link/Rect[168.8 578.2 199.0 591.2]/Border[0 0 0]/Dest[1511 0 R/XYZ 0 705 0]>>endobj
+512 0 obj<</Subtype/Link/Rect[124.5 565.0 331.0 578.0]/Border[0 0 0]/Dest[1511 0 R/XYZ 0 528 0]>>endobj
+513 0 obj<</Subtype/Link/Rect[124.5 551.8 280.3 564.8]/Border[0 0 0]/Dest[1511 0 R/XYZ 0 360 0]>>endobj
+514 0 obj<</Subtype/Link/Rect[124.5 538.6 467.0 551.6]/Border[0 0 0]/Dest[1511 0 R/XYZ 0 193 0]>>endobj
+515 0 obj<</Subtype/Link/Rect[124.5 525.4 251.8 538.4]/Border[0 0 0]/Dest[1513 0 R/XYZ 0 652 0]>>endobj
+516 0 obj<</Subtype/Link/Rect[168.8 512.2 216.4 525.2]/Border[0 0 0]/Dest[1513 0 R/XYZ 0 511 0]>>endobj
+517 0 obj<</Subtype/Link/Rect[168.8 499.0 206.9 512.0]/Border[0 0 0]/Dest[1513 0 R/XYZ 0 426 0]>>endobj
+518 0 obj<</Subtype/Link/Rect[80.2 485.8 374.5 498.8]/Border[0 0 0]/Dest[1517 0 R/XYZ 0 734 0]>>endobj
+519 0 obj<</Subtype/Link/Rect[124.5 472.6 175.5 485.6]/Border[0 0 0]/Dest[1517 0 R/XYZ 0 565 0]>>endobj
+520 0 obj<</Subtype/Link/Rect[124.5 459.4 312.1 472.4]/Border[0 0 0]/Dest[1519 0 R/XYZ 0 734 0]>>endobj
+521 0 obj<</Subtype/Link/Rect[124.5 446.2 324.7 459.2]/Border[0 0 0]/Dest[1519 0 R/XYZ 0 412 0]>>endobj
+522 0 obj<</Subtype/Link/Rect[124.5 433.0 184.1 446.0]/Border[0 0 0]/Dest[1519 0 R/XYZ 0 234 0]>>endobj
+523 0 obj<</Subtype/Link/Rect[124.5 419.8 422.7 432.8]/Border[0 0 0]/Dest[1521 0 R/XYZ 0 388 0]>>endobj
+524 0 obj<</Subtype/Link/Rect[124.5 406.6 232.4 419.6]/Border[0 0 0]/Dest[1523 0 R/XYZ 0 705 0]>>endobj
+525 0 obj<</Subtype/Link/Rect[80.2 393.4 201.6 406.4]/Border[0 0 0]/Dest[1525 0 R/XYZ 0 734 0]>>endobj
+526 0 obj<</Subtype/Link/Rect[124.5 380.2 182.2 393.2]/Border[0 0 0]/Dest[1525 0 R/XYZ 0 696 0]>>endobj
+527 0 obj<</Subtype/Link/Rect[124.5 367.0 266.9 380.0]/Border[0 0 0]/Dest[1525 0 R/XYZ 0 449 0]>>endobj
+528 0 obj<</Subtype/Link/Rect[168.8 353.8 309.9 366.8]/Border[0 0 0]/Dest[1527 0 R/XYZ 0 402 0]>>endobj
+529 0 obj<</Subtype/Link/Rect[168.8 340.6 353.4 353.6]/Border[0 0 0]/Dest[1527 0 R/XYZ 0 269 0]>>endobj
+530 0 obj<</Subtype/Link/Rect[124.5 327.4 244.6 340.4]/Border[0 0 0]/Dest[1527 0 R/XYZ 0 163 0]>>endobj
+531 0 obj<</Subtype/Link/Rect[124.5 314.2 169.7 327.2]/Border[0 0 0]/Dest[1529 0 R/XYZ 0 362 0]>>endobj
+532 0 obj<</Subtype/Link/Rect[124.5 301.0 148.0 314.0]/Border[0 0 0]/Dest[1529 0 R/XYZ 0 273 0]>>endobj
+533 0 obj<</Subtype/Link/Rect[124.5 287.8 154.8 300.8]/Border[0 0 0]/Dest[1529 0 R/XYZ 0 198 0]>>endobj
+534 0 obj<</Subtype/Link/Rect[168.8 274.6 226.5 287.6]/Border[0 0 0]/Dest[1529 0 R/XYZ 0 165 0]>>endobj
+535 0 obj<</Subtype/Link/Rect[168.8 261.4 226.5 274.4]/Border[0 0 0]/Dest[1531 0 R/XYZ 0 573 0]>>endobj
+536 0 obj<</Subtype/Link/Rect[168.8 248.2 282.7 261.2]/Border[0 0 0]/Dest[1533 0 R/XYZ 0 734 0]>>endobj
+537 0 obj<</Subtype/Link/Rect[168.8 235.0 421.1 248.0]/Border[0 0 0]/Dest[1533 0 R/XYZ 0 622 0]>>endobj
+538 0 obj<</Subtype/Link/Rect[168.8 221.8 309.9 234.8]/Border[0 0 0]/Dest[1533 0 R/XYZ 0 251 0]>>endobj
+539 0 obj<</Subtype/Link/Rect[168.8 208.6 325.8 221.6]/Border[0 0 0]/Dest[1537 0 R/XYZ 0 438 0]>>endobj
+540 0 obj<</Subtype/Link/Rect[168.8 195.4 294.3 208.4]/Border[0 0 0]/Dest[1537 0 R/XYZ 0 247 0]>>endobj
+541 0 obj<</Subtype/Link/Rect[168.8 182.2 369.5 195.2]/Border[0 0 0]/Dest[1539 0 R/XYZ 0 543 0]>>endobj
+542 0 obj<</Subtype/Link/Rect[168.8 169.0 363.1 182.0]/Border[0 0 0]/Dest[1541 0 R/XYZ 0 533 0]>>endobj
+543 0 obj<</Subtype/Link/Rect[124.5 155.8 160.9 168.8]/Border[0 0 0]/Dest[1543 0 R/XYZ 0 708 0]>>endobj
+544 0 obj<</Subtype/Link/Rect[168.8 142.6 209.4 155.6]/Border[0 0 0]/Dest[1543 0 R/XYZ 0 674 0]>>endobj
+545 0 obj<</Subtype/Link/Rect[168.8 129.4 269.3 142.4]/Border[0 0 0]/Dest[1543 0 R/XYZ 0 576 0]>>endobj
+546 0 obj<</Subtype/Link/Rect[168.8 116.2 225.3 129.2]/Border[0 0 0]/Dest[1543 0 R/XYZ 0 478 0]>>endobj
+547 0 obj<</Subtype/Link/Rect[168.8 103.0 391.8 116.0]/Border[0 0 0]/Dest[1545 0 R/XYZ 0 417 0]>>endobj
+548 0 obj<</Subtype/Link/Rect[168.8 89.8 350.3 102.8]/Border[0 0 0]/Dest[1545 0 R/XYZ 0 266 0]>>endobj
+549 0 obj<</Subtype/Link/Rect[124.5 76.6 214.6 89.6]/Border[0 0 0]/Dest[1545 0 R/XYZ 0 129 0]>>endobj
+550 0 obj<</Subtype/Link/Rect[168.8 63.4 209.4 76.4]/Border[0 0 0]/Dest[1547 0 R/XYZ 0 734 0]>>endobj
+551 0 obj[507 0 R
+508 0 R
+509 0 R
+510 0 R
+511 0 R
+512 0 R
+513 0 R
+514 0 R
+515 0 R
+516 0 R
+517 0 R
+518 0 R
+519 0 R
+520 0 R
+521 0 R
+522 0 R
+523 0 R
+524 0 R
+525 0 R
+526 0 R
+527 0 R
+528 0 R
+529 0 R
+530 0 R
+531 0 R
+532 0 R
+533 0 R
+534 0 R
+535 0 R
+536 0 R
+537 0 R
+538 0 R
+539 0 R
+540 0 R
+541 0 R
+542 0 R
+543 0 R
+544 0 R
+545 0 R
+546 0 R
+547 0 R
+548 0 R
+549 0 R
+550 0 R]endobj
+552 0 obj<</Subtype/Link/Rect[168.8 721.0 199.6 734.0]/Border[0 0 0]/Dest[1547 0 R/XYZ 0 649 0]>>endobj
+553 0 obj[552 0 R]endobj
+554 0 obj<</S/URI/URI(http://samba.org/)>>endobj
+555 0 obj<</Subtype/Link/Rect[165.5 637.0 260.5 650.0]/Border[0 0 0]/A 554 0 R>>endobj
+556 0 obj[555 0 R]endobj
+557 0 obj<</S/URI/URI(http://www.openldap.org/)>>endobj
+558 0 obj<</Subtype/Link/Rect[169.5 721.0 285.9 734.0]/Border[0 0 0]/A 557 0 R>>endobj
+559 0 obj<</S/URI/URI(http://iplanet.netscape.com/directory)>>endobj
+560 0 obj<</Subtype/Link/Rect[223.9 707.8 387.9 720.8]/Border[0 0 0]/A 559 0 R>>endobj
+561 0 obj<</S/URI/URI(http://www.ora.com/)>>endobj
+562 0 obj<</Subtype/Link/Rect[112.6 681.4 202.0 694.4]/Border[0 0 0]/A 561 0 R>>endobj
+563 0 obj<</S/URI/URI(http://www.unav.es/cti/ldap-smb/ldap-smb-3-howto.html)>>endobj
+564 0 obj<</Subtype/Link/Rect[125.1 615.4 267.5 628.4]/Border[0 0 0]/A 563 0 R>>endobj
+565 0 obj<</S/URI/URI(http://samba.idealx.org/)>>endobj
+566 0 obj<</Subtype/Link/Rect[243.7 602.2 287.3 615.2]/Border[0 0 0]/A 565 0 R>>endobj
+567 0 obj<</S/Launch/F(#ENCRYPTPASSWORDS)>>endobj
+568 0 obj<</Subtype/Link/Rect[212.8 530.6 332.5 543.6]/Border[0 0 0]/A 567 0 R>>endobj
+569 0 obj<</S/URI/URI(http://www.padl.com/)>>endobj
+570 0 obj<</Subtype/Link/Rect[284.3 95.0 380.9 108.0]/Border[0 0 0]/A 569 0 R>>endobj
+571 0 obj[558 0 R
+560 0 R
+562 0 R
+564 0 R
+566 0 R
+568 0 R
+570 0 R]endobj
+572 0 obj<</S/Launch/F(samba-patches@samba.org)>>endobj
+573 0 obj<</Subtype/Link/Rect[393.7 651.4 519.4 664.4]/Border[0 0 0]/A 572 0 R>>endobj
+574 0 obj<</S/Launch/F(jerry@samba.org)>>endobj
+575 0 obj<</Subtype/Link/Rect[72.0 638.2 148.4 651.2]/Border[0 0 0]/A 574 0 R>>endobj
+576 0 obj<</S/Launch/F(jerry@samba.org)>>endobj
+577 0 obj<</Subtype/Link/Rect[271.2 425.0 350.4 438.0]/Border[0 0 0]/A 576 0 R>>endobj
+578 0 obj[573 0 R
+575 0 R
+577 0 R]endobj
+579 0 obj<</S/Launch/F(#LDAPSSL)>>endobj
+580 0 obj<</Subtype/Link/Rect[108.0 260.6 141.3 273.6]/Border[0 0 0]/A 579 0 R>>endobj
+581 0 obj<</S/Launch/F(#LDAPSERVER)>>endobj
+582 0 obj<</Subtype/Link/Rect[108.0 247.4 156.6 260.4]/Border[0 0 0]/A 581 0 R>>endobj
+583 0 obj<</S/Launch/F(#LDAPADMINDN)>>endobj
+584 0 obj<</Subtype/Link/Rect[108.0 234.2 170.9 247.2]/Border[0 0 0]/A 583 0 R>>endobj
+585 0 obj<</S/Launch/F(#LDAPSUFFIX)>>endobj
+586 0 obj<</Subtype/Link/Rect[108.0 221.0 155.4 234.0]/Border[0 0 0]/A 585 0 R>>endobj
+587 0 obj<</S/Launch/F(#LDAPFILTER)>>endobj
+588 0 obj<</Subtype/Link/Rect[108.0 207.8 151.1 220.8]/Border[0 0 0]/A 587 0 R>>endobj
+589 0 obj<</S/Launch/F(#LDAPPORT)>>endobj
+590 0 obj<</Subtype/Link/Rect[108.0 194.6 147.4 207.6]/Border[0 0 0]/A 589 0 R>>endobj
+591 0 obj<</S/Launch/F(smb.conf.5.html)>>endobj
+592 0 obj<</Subtype/Link/Rect[186.9 168.2 243.1 181.2]/Border[0 0 0]/A 591 0 R>>endobj
+593 0 obj[580 0 R
+582 0 R
+584 0 R
+586 0 R
+588 0 R
+590 0 R
+592 0 R]endobj
+594 0 obj<</S/Launch/F(ENCRYPTION.html)>>endobj
+595 0 obj<</Subtype/Link/Rect[72.0 99.0 176.8 112.0]/Border[0 0 0]/A 594 0 R>>endobj
+596 0 obj[595 0 R]endobj
+597 0 obj<</S/Launch/F(Samba-PDC-HOWTO.html)>>endobj
+598 0 obj<</Subtype/Link/Rect[72.0 65.0 176.7 78.0]/Border[0 0 0]/A 597 0 R>>endobj
+599 0 obj[598 0 R]endobj
+600 0 obj<</Subtype/Link/Rect[80.2 631.0 216.5 644.0]/Border[0 0 0]/Dest[1555 0 R/XYZ 0 734 0]>>endobj
+601 0 obj<</Subtype/Link/Rect[124.5 617.8 212.2 630.8]/Border[0 0 0]/Dest[1555 0 R/XYZ 0 523 0]>>endobj
+602 0 obj<</Subtype/Link/Rect[124.5 604.6 233.6 617.6]/Border[0 0 0]/Dest[1555 0 R/XYZ 0 249 0]>>endobj
+603 0 obj<</Subtype/Link/Rect[124.5 591.4 211.9 604.4]/Border[0 0 0]/Dest[1557 0 R/XYZ 0 679 0]>>endobj
+604 0 obj<</Subtype/Link/Rect[168.8 578.2 284.6 591.2]/Border[0 0 0]/Dest[1557 0 R/XYZ 0 590 0]>>endobj
+605 0 obj<</Subtype/Link/Rect[80.2 565.0 356.8 578.0]/Border[0 0 0]/Dest[1559 0 R/XYZ 0 734 0]>>endobj
+606 0 obj<</Subtype/Link/Rect[80.2 551.8 331.1 564.8]/Border[0 0 0]/Dest[1563 0 R/XYZ 0 734 0]>>endobj
+607 0 obj<</Subtype/Link/Rect[124.5 538.6 221.0 551.6]/Border[0 0 0]/Dest[1563 0 R/XYZ 0 672 0]>>endobj
+608 0 obj<</Subtype/Link/Rect[124.5 525.4 181.0 538.4]/Border[0 0 0]/Dest[1563 0 R/XYZ 0 584 0]>>endobj
+609 0 obj<</Subtype/Link/Rect[124.5 512.2 317.3 525.2]/Border[0 0 0]/Dest[1565 0 R/XYZ 0 734 0]>>endobj
+610 0 obj<</Subtype/Link/Rect[124.5 499.0 431.3 512.0]/Border[0 0 0]/Dest[1567 0 R/XYZ 0 665 0]>>endobj
+611 0 obj<</Subtype/Link/Rect[168.8 485.8 369.2 498.8]/Border[0 0 0]/Dest[1569 0 R/XYZ 0 665 0]>>endobj
+612 0 obj<</Subtype/Link/Rect[168.8 472.6 400.6 485.6]/Border[0 0 0]/Dest[1571 0 R/XYZ 0 734 0]>>endobj
+613 0 obj<</Subtype/Link/Rect[168.8 459.4 316.0 472.4]/Border[0 0 0]/Dest[1571 0 R/XYZ 0 524 0]>>endobj
+614 0 obj<</Subtype/Link/Rect[124.5 446.2 263.2 459.2]/Border[0 0 0]/Dest[1571 0 R/XYZ 0 175 0]>>endobj
+615 0 obj<</Subtype/Link/Rect[124.5 433.0 252.8 446.0]/Border[0 0 0]/Dest[1575 0 R/XYZ 0 565 0]>>endobj
+616 0 obj<</Subtype/Link/Rect[124.5 419.8 244.9 432.8]/Border[0 0 0]/Dest[1577 0 R/XYZ 0 560 0]>>endobj
+617 0 obj<</Subtype/Link/Rect[124.5 406.6 290.4 419.6]/Border[0 0 0]/Dest[1581 0 R/XYZ 0 283 0]>>endobj
+618 0 obj<</Subtype/Link/Rect[168.8 393.4 368.0 406.4]/Border[0 0 0]/Dest[1583 0 R/XYZ 0 283 0]>>endobj
+619 0 obj<</Subtype/Link/Rect[168.8 380.2 444.1 393.2]/Border[0 0 0]/Dest[1585 0 R/XYZ 0 504 0]>>endobj
+620 0 obj<</Subtype/Link/Rect[124.5 367.0 423.7 380.0]/Border[0 0 0]/Dest[1593 0 R/XYZ 0 415 0]>>endobj
+621 0 obj<</Subtype/Link/Rect[80.2 353.8 449.4 366.8]/Border[0 0 0]/Dest[1597 0 R/XYZ 0 734 0]>>endobj
+622 0 obj<</Subtype/Link/Rect[124.5 340.6 221.0 353.6]/Border[0 0 0]/Dest[1597 0 R/XYZ 0 672 0]>>endobj
+623 0 obj<</Subtype/Link/Rect[124.5 327.4 181.0 340.4]/Border[0 0 0]/Dest[1597 0 R/XYZ 0 597 0]>>endobj
+624 0 obj<</Subtype/Link/Rect[124.5 314.2 360.4 327.2]/Border[0 0 0]/Dest[1597 0 R/XYZ 0 225 0]>>endobj
+625 0 obj<</Subtype/Link/Rect[168.8 301.0 401.0 314.0]/Border[0 0 0]/Dest[1599 0 R/XYZ 0 734 0]>>endobj
+626 0 obj<</Subtype/Link/Rect[168.8 287.8 287.0 300.8]/Border[0 0 0]/Dest[1599 0 R/XYZ 0 609 0]>>endobj
+627 0 obj<</Subtype/Link/Rect[124.5 274.6 394.3 287.6]/Border[0 0 0]/Dest[1599 0 R/XYZ 0 524 0]>>endobj
+628 0 obj<</Subtype/Link/Rect[124.5 261.4 268.1 274.4]/Border[0 0 0]/Dest[1599 0 R/XYZ 0 323 0]>>endobj
+629 0 obj<</Subtype/Link/Rect[168.8 248.2 345.7 261.2]/Border[0 0 0]/Dest[1601 0 R/XYZ 0 541 0]>>endobj
+630 0 obj<</Subtype/Link/Rect[168.8 235.0 300.5 248.0]/Border[0 0 0]/Dest[1601 0 R/XYZ 0 390 0]>>endobj
+631 0 obj<</Subtype/Link/Rect[80.2 221.8 230.6 234.8]/Border[0 0 0]/Dest[1603 0 R/XYZ 0 734 0]>>endobj
+632 0 obj<</Subtype/Link/Rect[124.5 208.6 320.7 221.6]/Border[0 0 0]/Dest[1603 0 R/XYZ 0 551 0]>>endobj
+633 0 obj<</Subtype/Link/Rect[124.5 195.4 321.9 208.4]/Border[0 0 0]/Dest[1603 0 R/XYZ 0 444 0]>>endobj
+634 0 obj<</Subtype/Link/Rect[124.5 182.2 197.2 195.2]/Border[0 0 0]/Dest[1603 0 R/XYZ 0 267 0]>>endobj
+635 0 obj<</Subtype/Link/Rect[124.5 169.0 238.2 182.0]/Border[0 0 0]/Dest[1605 0 R/XYZ 0 580 0]>>endobj
+636 0 obj<</Subtype/Link/Rect[124.5 155.8 255.3 168.8]/Border[0 0 0]/Dest[1605 0 R/XYZ 0 264 0]>>endobj
+637 0 obj<</Subtype/Link/Rect[168.8 142.6 239.0 155.6]/Border[0 0 0]/Dest[1605 0 R/XYZ 0 202 0]>>endobj
+638 0 obj<</Subtype/Link/Rect[124.5 129.4 224.7 142.4]/Border[0 0 0]/Dest[1607 0 R/XYZ 0 734 0]>>endobj
+639 0 obj<</Subtype/Link/Rect[124.5 116.2 226.3 129.2]/Border[0 0 0]/Dest[1607 0 R/XYZ 0 645 0]>>endobj
+640 0 obj<</Subtype/Link/Rect[124.5 103.0 152.3 116.0]/Border[0 0 0]/Dest[1607 0 R/XYZ 0 570 0]>>endobj
+641 0 obj<</Subtype/Link/Rect[80.2 89.8 272.7 102.8]/Border[0 0 0]/Dest[1609 0 R/XYZ 0 734 0]>>endobj
+642 0 obj<</Subtype/Link/Rect[124.5 76.6 299.3 89.6]/Border[0 0 0]/Dest[1609 0 R/XYZ 0 672 0]>>endobj
+643 0 obj<</Subtype/Link/Rect[124.5 63.4 286.8 76.4]/Border[0 0 0]/Dest[1611 0 R/XYZ 0 494 0]>>endobj
+644 0 obj[600 0 R
+601 0 R
+602 0 R
+603 0 R
+604 0 R
+605 0 R
+606 0 R
+607 0 R
+608 0 R
+609 0 R
+610 0 R
+611 0 R
+612 0 R
+613 0 R
+614 0 R
+615 0 R
+616 0 R
+617 0 R
+618 0 R
+619 0 R
+620 0 R
+621 0 R
+622 0 R
+623 0 R
+624 0 R
+625 0 R
+626 0 R
+627 0 R
+628 0 R
+629 0 R
+630 0 R
+631 0 R
+632 0 R
+633 0 R
+634 0 R
+635 0 R
+636 0 R
+637 0 R
+638 0 R
+639 0 R
+640 0 R
+641 0 R
+642 0 R
+643 0 R]endobj
+645 0 obj<</Subtype/Link/Rect[124.5 721.0 309.7 734.0]/Border[0 0 0]/Dest[1611 0 R/XYZ 0 405 0]>>endobj
+646 0 obj[645 0 R]endobj
+647 0 obj<</S/Launch/F(smb.conf.5.html)>>endobj
+648 0 obj<</Subtype/Link/Rect[153.2 599.8 225.8 612.8]/Border[0 0 0]/A 647 0 R>>endobj
+649 0 obj[648 0 R]endobj
+650 0 obj<</S/Launch/F(smb.conf.5.html)>>endobj
+651 0 obj<</Subtype/Link/Rect[318.5 674.2 423.3 687.2]/Border[0 0 0]/A 650 0 R>>endobj
+652 0 obj<</S/Launch/F(#NETBIOSNAME)>>endobj
+653 0 obj<</Subtype/Link/Rect[93.6 601.8 158.4 612.8]/Border[0 0 0]/A 652 0 R>>endobj
+654 0 obj<</S/Launch/F(#WORKGROUP)>>endobj
+655 0 obj<</Subtype/Link/Rect[93.6 591.0 142.2 602.0]/Border[0 0 0]/A 654 0 R>>endobj
+656 0 obj<</S/Launch/F(#OSLEVEL)>>endobj
+657 0 obj<</Subtype/Link/Rect[93.6 558.6 136.8 569.6]/Border[0 0 0]/A 656 0 R>>endobj
+658 0 obj<</S/Launch/F(#PERFERREDMASTER)>>endobj
+659 0 obj<</Subtype/Link/Rect[93.6 547.8 180.0 558.8]/Border[0 0 0]/A 658 0 R>>endobj
+660 0 obj<</S/Launch/F(#DOMAINMASTER)>>endobj
+661 0 obj<</Subtype/Link/Rect[93.6 537.0 163.8 548.0]/Border[0 0 0]/A 660 0 R>>endobj
+662 0 obj<</S/Launch/F(#LOCALMASTER)>>endobj
+663 0 obj<</Subtype/Link/Rect[93.6 526.2 158.4 537.2]/Border[0 0 0]/A 662 0 R>>endobj
+664 0 obj<</S/Launch/F(#SECURITYEQUALSUSER)>>endobj
+665 0 obj<</Subtype/Link/Rect[93.6 493.8 136.8 504.8]/Border[0 0 0]/A 664 0 R>>endobj
+666 0 obj<</S/Launch/F(#ENCRYPTPASSWORDS)>>endobj
+667 0 obj<</Subtype/Link/Rect[93.6 461.4 185.4 472.4]/Border[0 0 0]/A 666 0 R>>endobj
+668 0 obj<</S/Launch/F(#DOMAINLOGONS)>>endobj
+669 0 obj<</Subtype/Link/Rect[93.6 429.0 163.8 440.0]/Border[0 0 0]/A 668 0 R>>endobj
+670 0 obj<</S/Launch/F(#LOGONPATH)>>endobj
+671 0 obj<</Subtype/Link/Rect[93.6 396.6 147.6 407.6]/Border[0 0 0]/A 670 0 R>>endobj
+672 0 obj<</S/Launch/F(#LOGONDRIVE)>>endobj
+673 0 obj<</Subtype/Link/Rect[93.6 364.2 153.0 375.2]/Border[0 0 0]/A 672 0 R>>endobj
+674 0 obj<</S/Launch/F(#LOGONHOME)>>endobj
+675 0 obj<</Subtype/Link/Rect[93.6 353.4 147.6 364.4]/Border[0 0 0]/A 674 0 R>>endobj
+676 0 obj<</S/Launch/F(#LOGONSCRIPT)>>endobj
+677 0 obj<</Subtype/Link/Rect[93.6 310.2 158.4 321.2]/Border[0 0 0]/A 676 0 R>>endobj
+678 0 obj<</S/Launch/F(#PATH)>>endobj
+679 0 obj<</Subtype/Link/Rect[93.6 267.0 115.2 278.0]/Border[0 0 0]/A 678 0 R>>endobj
+680 0 obj<</S/Launch/F(#READONLY)>>endobj
+681 0 obj<</Subtype/Link/Rect[93.6 256.2 142.2 267.2]/Border[0 0 0]/A 680 0 R>>endobj
+682 0 obj<</S/Launch/F(#WRITELIST)>>endobj
+683 0 obj<</Subtype/Link/Rect[93.6 245.4 147.6 256.4]/Border[0 0 0]/A 682 0 R>>endobj
+684 0 obj<</S/Launch/F(#PATH)>>endobj
+685 0 obj<</Subtype/Link/Rect[93.6 202.2 115.2 213.2]/Border[0 0 0]/A 684 0 R>>endobj
+686 0 obj<</S/Launch/F(#READONLY)>>endobj
+687 0 obj<</Subtype/Link/Rect[93.6 191.4 142.2 202.4]/Border[0 0 0]/A 686 0 R>>endobj
+688 0 obj<</S/Launch/F(#CREATEMASK)>>endobj
+689 0 obj<</Subtype/Link/Rect[93.6 180.6 153.0 191.6]/Border[0 0 0]/A 688 0 R>>endobj
+690 0 obj<</S/Launch/F(#DIRECTORYMASK)>>endobj
+691 0 obj<</Subtype/Link/Rect[93.6 169.8 169.2 180.8]/Border[0 0 0]/A 690 0 R>>endobj
+692 0 obj<</S/Launch/F(ENCRYPTION.html)>>endobj
+693 0 obj<</Subtype/Link/Rect[108.0 104.2 200.6 117.2]/Border[0 0 0]/A 692 0 R>>endobj
+694 0 obj[651 0 R
+653 0 R
+655 0 R
+657 0 R
+659 0 R
+661 0 R
+663 0 R
+665 0 R
+667 0 R
+669 0 R
+671 0 R
+673 0 R
+675 0 R
+677 0 R
+679 0 R
+681 0 R
+683 0 R
+685 0 R
+687 0 R
+689 0 R
+691 0 R
+693 0 R]endobj
+695 0 obj<</S/Launch/F(smbpasswd.8.html)>>endobj
+696 0 obj<</Subtype/Link/Rect[72.0 295.4 138.6 308.4]/Border[0 0 0]/A 695 0 R>>endobj
+697 0 obj[696 0 R]endobj
+698 0 obj<</S/Launch/F(#ADDUSERSCRIPT)>>endobj
+699 0 obj<</Subtype/Link/Rect[420.0 638.2 486.9 651.2]/Border[0 0 0]/A 698 0 R>>endobj
+700 0 obj[699 0 R]endobj
+701 0 obj<</S/URI/URI(http://www.microsoft.com/ntserver/management/deployment/planguide/prof_policies.asp)>>endobj
+702 0 obj<</Subtype/Link/Rect[139.8 492.2 387.6 505.2]/Border[0 0 0]/A 701 0 R>>endobj
+703 0 obj[702 0 R]endobj
+704 0 obj<</S/URI/URI(ftp://ftp.microsoft.com/Softlib/MSLFILES/NEXUS.EXE)>>endobj
+705 0 obj<</Subtype/Link/Rect[285.2 615.4 540.0 628.4]/Border[0 0 0]/A 704 0 R>>endobj
+706 0 obj<</S/URI/URI(ftp://ftp.microsoft.com/Softlib/MSLFILES/SRVTOOLS.EXE)>>endobj
+707 0 obj<</Subtype/Link/Rect[230.8 575.8 505.8 588.8]/Border[0 0 0]/A 706 0 R>>endobj
+708 0 obj<</S/URI/URI(http://www.tcpdump.org/)>>endobj
+709 0 obj<</Subtype/Link/Rect[349.4 183.8 455.4 196.8]/Border[0 0 0]/A 708 0 R>>endobj
+710 0 obj<</S/URI/URI(http://www.ethereal.com/)>>endobj
+711 0 obj<</Subtype/Link/Rect[424.5 170.6 536.6 183.6]/Border[0 0 0]/A 710 0 R>>endobj
+712 0 obj[705 0 R
+707 0 R
+709 0 R
+711 0 R]endobj
+713 0 obj<</S/URI/URI(http://samba.org)>>endobj
+714 0 obj<</Subtype/Link/Rect[233.5 311.8 308.1 324.8]/Border[0 0 0]/A 713 0 R>>endobj
+715 0 obj<</S/URI/URI(http://www.skippy.net/linux/smb-howto.html)>>endobj
+716 0 obj<</Subtype/Link/Rect[144.0 259.0 346.1 272.0]/Border[0 0 0]/A 715 0 R>>endobj
+717 0 obj<</S/URI/URI(http://bioserve.latrobe.edu.au/samba)>>endobj
+718 0 obj<</Subtype/Link/Rect[179.7 232.6 342.3 245.6]/Border[0 0 0]/A 717 0 R>>endobj
+719 0 obj<</S/URI/URI(http://samba.org/cifs/)>>endobj
+720 0 obj<</Subtype/Link/Rect[282.1 219.4 378.7 232.4]/Border[0 0 0]/A 719 0 R>>endobj
+721 0 obj<</S/URI/URI(http://mailhost.cb1.com/~lkcl/ntdom/)>>endobj
+722 0 obj<</Subtype/Link/Rect[241.5 206.2 408.5 219.2]/Border[0 0 0]/A 721 0 R>>endobj
+723 0 obj<</S/URI/URI(ftp://ftp.microsoft.com/developr/drg/CIFS/)>>endobj
+724 0 obj<</Subtype/Link/Rect[277.5 193.0 469.1 206.0]/Border[0 0 0]/A 723 0 R>>endobj
+725 0 obj<</S/URI/URI(http://samba.org)>>endobj
+726 0 obj<</Subtype/Link/Rect[358.2 140.2 432.8 153.2]/Border[0 0 0]/A 725 0 R>>endobj
+727 0 obj<</S/URI/URI(http://www.samba-tng.org/)>>endobj
+728 0 obj<</Subtype/Link/Rect[298.4 100.6 422.8 113.6]/Border[0 0 0]/A 727 0 R>>endobj
+729 0 obj[714 0 R
+716 0 R
+718 0 R
+720 0 R
+722 0 R
+724 0 R
+726 0 R
+728 0 R]endobj
+730 0 obj<</S/URI/URI(http://lists.samba.org/)>>endobj
+731 0 obj<</Subtype/Link/Rect[132.8 351.4 227.8 364.4]/Border[0 0 0]/A 730 0 R>>endobj
+732 0 obj<</S/URI/URI(http://lists.samba.org/mailman/roster/samba-ntdom)>>endobj
+733 0 obj<</Subtype/Link/Rect[306.3 338.2 328.0 351.2]/Border[0 0 0]/A 732 0 R>>endobj
+734 0 obj[731 0 R
+733 0 R]endobj
+735 0 obj<</S/Launch/F(Samba-PDC-HOWTO.html)>>endobj
+736 0 obj<</Subtype/Link/Rect[210.4 613.0 317.8 626.0]/Border[0 0 0]/A 735 0 R>>endobj
+737 0 obj[736 0 R]endobj
+738 0 obj<</S/Launch/F(smb.conf.5.html)>>endobj
+739 0 obj<</Subtype/Link/Rect[191.8 573.4 264.4 586.4]/Border[0 0 0]/A 738 0 R>>endobj
+740 0 obj<</S/Launch/F(#SECURITY)>>endobj
+741 0 obj<</Subtype/Link/Rect[166.4 547.0 216.8 560.0]/Border[0 0 0]/A 740 0 R>>endobj
+742 0 obj<</S/Launch/F(#WORKGROUP)>>endobj
+743 0 obj<</Subtype/Link/Rect[143.5 481.0 207.4 494.0]/Border[0 0 0]/A 742 0 R>>endobj
+744 0 obj<</S/Launch/F(#ENCRYPTPASSWORDS)>>endobj
+745 0 obj<</Subtype/Link/Rect[222.0 401.8 316.8 414.8]/Border[0 0 0]/A 744 0 R>>endobj
+746 0 obj<</S/Launch/F(#PASSWORDSERVER)>>endobj
+747 0 obj<</Subtype/Link/Rect[186.0 362.2 279.2 375.2]/Border[0 0 0]/A 746 0 R>>endobj
+748 0 obj[739 0 R
+741 0 R
+743 0 R
+745 0 R
+747 0 R]endobj
+749 0 obj<</S/Launch/F(net.8.html)>>endobj
+750 0 obj<</Subtype/Link/Rect[218.7 694.6 247.7 707.6]/Border[0 0 0]/A 749 0 R>>endobj
+751 0 obj<</S/Launch/F(#SECURITYEQUALSSERVER)>>endobj
+752 0 obj<</Subtype/Link/Rect[275.2 319.8 351.3 332.8]/Border[0 0 0]/A 751 0 R>>endobj
+753 0 obj<</S/Launch/F(winbind.html)>>endobj
+754 0 obj<</Subtype/Link/Rect[151.1 267.0 219.5 280.0]/Border[0 0 0]/A 753 0 R>>endobj
+755 0 obj[750 0 R
+752 0 R
+754 0 R]endobj
+756 0 obj<</S/URI/URI(http://www.linuxworld.com)>>endobj
+757 0 obj<</Subtype/Link/Rect[438.0 668.2 495.1 681.2]/Border[0 0 0]/A 756 0 R>>endobj
+758 0 obj<</S/URI/URI(http://www.linuxworld.com/linuxworld/lw-1998-10/lw-10-samba.html)>>endobj
+759 0 obj<</Subtype/Link/Rect[72.0 655.0 186.6 668.0]/Border[0 0 0]/A 758 0 R>>endobj
+760 0 obj[757 0 R
+759 0 R]endobj
+761 0 obj<</Subtype/Link/Rect[85.8 631.0 295.4 644.0]/Border[0 0 0]/Dest[1623 0 R/XYZ 0 734 0]>>endobj
+762 0 obj<</Subtype/Link/Rect[130.0 617.8 166.4 630.8]/Border[0 0 0]/Dest[1623 0 R/XYZ 0 672 0]>>endobj
+763 0 obj<</Subtype/Link/Rect[130.0 604.6 331.4 617.6]/Border[0 0 0]/Dest[1623 0 R/XYZ 0 439 0]>>endobj
+764 0 obj<</Subtype/Link/Rect[177.0 591.4 243.0 604.4]/Border[0 0 0]/Dest[1623 0 R/XYZ 0 311 0]>>endobj
+765 0 obj<</Subtype/Link/Rect[177.0 578.2 282.6 591.2]/Border[0 0 0]/Dest[1625 0 R/XYZ 0 441 0]>>endobj
+766 0 obj<</Subtype/Link/Rect[177.0 565.0 269.4 578.0]/Border[0 0 0]/Dest[1625 0 R/XYZ 0 303 0]>>endobj
+767 0 obj<</Subtype/Link/Rect[177.0 551.8 295.8 564.8]/Border[0 0 0]/Dest[1625 0 R/XYZ 0 157 0]>>endobj
+768 0 obj<</Subtype/Link/Rect[130.0 538.6 384.2 551.6]/Border[0 0 0]/Dest[1627 0 R/XYZ 0 339 0]>>endobj
+769 0 obj<</Subtype/Link/Rect[174.2 525.4 294.6 538.4]/Border[0 0 0]/Dest[1629 0 R/XYZ 0 266 0]>>endobj
+770 0 obj<</Subtype/Link/Rect[174.2 512.2 261.3 525.2]/Border[0 0 0]/Dest[1631 0 R/XYZ 0 734 0]>>endobj
+771 0 obj<</Subtype/Link/Rect[174.2 499.0 226.8 512.0]/Border[0 0 0]/Dest[1633 0 R/XYZ 0 459 0]>>endobj
+772 0 obj<</Subtype/Link/Rect[174.2 485.8 233.5 498.8]/Border[0 0 0]/Dest[1633 0 R/XYZ 0 361 0]>>endobj
+773 0 obj<</Subtype/Link/Rect[174.2 472.6 238.4 485.6]/Border[0 0 0]/Dest[1633 0 R/XYZ 0 224 0]>>endobj
+774 0 obj<</Subtype/Link/Rect[130.0 459.4 528.8 472.4]/Border[0 0 0]/Dest[1635 0 R/XYZ 0 670 0]>>endobj
+775 0 obj<</Subtype/Link/Rect[130.0 446.2 500.9 459.2]/Border[0 0 0]/Dest[1635 0 R/XYZ 0 126 0]>>endobj
+776 0 obj<</Subtype/Link/Rect[174.2 433.0 393.6 446.0]/Border[0 0 0]/Dest[1639 0 R/XYZ 0 734 0]>>endobj
+777 0 obj<</Subtype/Link/Rect[174.2 419.8 455.6 432.8]/Border[0 0 0]/Dest[1639 0 R/XYZ 0 484 0]>>endobj
+778 0 obj<</Subtype/Link/Rect[174.2 406.6 377.1 419.6]/Border[0 0 0]/Dest[1639 0 R/XYZ 0 132 0]>>endobj
+779 0 obj<</Subtype/Link/Rect[130.0 393.4 187.1 406.4]/Border[0 0 0]/Dest[1641 0 R/XYZ 0 263 0]>>endobj
+780 0 obj<</Subtype/Link/Rect[85.8 380.2 358.0 393.2]/Border[0 0 0]/Dest[1643 0 R/XYZ 0 734 0]>>endobj
+781 0 obj<</Subtype/Link/Rect[130.0 367.0 447.2 380.0]/Border[0 0 0]/Dest[1643 0 R/XYZ 0 672 0]>>endobj
+782 0 obj<</Subtype/Link/Rect[130.0 353.8 324.0 366.8]/Border[0 0 0]/Dest[1643 0 R/XYZ 0 537 0]>>endobj
+783 0 obj<</Subtype/Link/Rect[130.0 340.6 234.2 353.6]/Border[0 0 0]/Dest[1643 0 R/XYZ 0 369 0]>>endobj
+784 0 obj<</Subtype/Link/Rect[130.0 327.4 296.5 340.4]/Border[0 0 0]/Dest[1645 0 R/XYZ 0 705 0]>>endobj
+785 0 obj<</Subtype/Link/Rect[174.2 314.2 251.2 327.2]/Border[0 0 0]/Dest[1645 0 R/XYZ 0 471 0]>>endobj
+786 0 obj<</Subtype/Link/Rect[174.2 301.0 276.3 314.0]/Border[0 0 0]/Dest[1645 0 R/XYZ 0 228 0]>>endobj
+787 0 obj<</Subtype/Link/Rect[130.0 287.8 305.7 300.8]/Border[0 0 0]/Dest[1647 0 R/XYZ 0 718 0]>>endobj
+788 0 obj<</Subtype/Link/Rect[130.0 274.6 402.5 287.6]/Border[0 0 0]/Dest[1647 0 R/XYZ 0 287 0]>>endobj
+789 0 obj<</Subtype/Link/Rect[130.0 261.4 392.8 274.4]/Border[0 0 0]/Dest[1651 0 R/XYZ 0 652 0]>>endobj
+790 0 obj<</Subtype/Link/Rect[85.8 248.2 401.7 261.2]/Border[0 0 0]/Dest[1653 0 R/XYZ 0 734 0]>>endobj
+791 0 obj<</Subtype/Link/Rect[130.0 235.0 207.3 248.0]/Border[0 0 0]/Dest[1653 0 R/XYZ 0 672 0]>>endobj
+792 0 obj<</Subtype/Link/Rect[130.0 221.8 250.4 234.8]/Border[0 0 0]/Dest[1655 0 R/XYZ 0 148 0]>>endobj
+793 0 obj<</Subtype/Link/Rect[130.0 208.6 273.9 221.6]/Border[0 0 0]/Dest[1657 0 R/XYZ 0 705 0]>>endobj
+794 0 obj<</Subtype/Link/Rect[85.8 195.4 350.0 208.4]/Border[0 0 0]/Dest[1659 0 R/XYZ 0 734 0]>>endobj
+795 0 obj<</Subtype/Link/Rect[130.0 182.2 185.3 195.2]/Border[0 0 0]/Dest[1659 0 R/XYZ 0 672 0]>>endobj
+796 0 obj<</Subtype/Link/Rect[174.2 169.0 202.1 182.0]/Border[0 0 0]/Dest[1661 0 R/XYZ 0 652 0]>>endobj
+797 0 obj<</Subtype/Link/Rect[85.8 155.8 162.8 168.8]/Border[0 0 0]/Dest[1663 0 R/XYZ 0 734 0]>>endobj
+798 0 obj<</Subtype/Link/Rect[130.0 142.6 187.8 155.6]/Border[0 0 0]/Dest[1663 0 R/XYZ 0 696 0]>>endobj
+799 0 obj<</Subtype/Link/Rect[130.0 129.4 195.1 142.4]/Border[0 0 0]/Dest[1663 0 R/XYZ 0 317 0]>>endobj
+800 0 obj<</Subtype/Link/Rect[174.2 116.2 254.3 129.2]/Border[0 0 0]/Dest[1663 0 R/XYZ 0 127 0]>>endobj
+801 0 obj<</Subtype/Link/Rect[174.2 103.0 337.1 116.0]/Border[0 0 0]/Dest[1667 0 R/XYZ 0 531 0]>>endobj
+802 0 obj<</Subtype/Link/Rect[174.2 89.8 331.3 102.8]/Border[0 0 0]/Dest[1669 0 R/XYZ 0 734 0]>>endobj
+803 0 obj<</Subtype/Link/Rect[174.2 76.6 386.9 89.6]/Border[0 0 0]/Dest[1669 0 R/XYZ 0 363 0]>>endobj
+804 0 obj<</Subtype/Link/Rect[174.2 63.4 287.3 76.4]/Border[0 0 0]/Dest[1671 0 R/XYZ 0 184 0]>>endobj
+805 0 obj[761 0 R
+762 0 R
+763 0 R
+764 0 R
+765 0 R
+766 0 R
+767 0 R
+768 0 R
+769 0 R
+770 0 R
+771 0 R
+772 0 R
+773 0 R
+774 0 R
+775 0 R
+776 0 R
+777 0 R
+778 0 R
+779 0 R
+780 0 R
+781 0 R
+782 0 R
+783 0 R
+784 0 R
+785 0 R
+786 0 R
+787 0 R
+788 0 R
+789 0 R
+790 0 R
+791 0 R
+792 0 R
+793 0 R
+794 0 R
+795 0 R
+796 0 R
+797 0 R
+798 0 R
+799 0 R
+800 0 R
+801 0 R
+802 0 R
+803 0 R
+804 0 R]endobj
+806 0 obj<</Subtype/Link/Rect[130.0 721.0 224.4 734.0]/Border[0 0 0]/Dest[1673 0 R/XYZ 0 692 0]>>endobj
+807 0 obj<</Subtype/Link/Rect[174.2 707.8 255.8 720.8]/Border[0 0 0]/Dest[1673 0 R/XYZ 0 590 0]>>endobj
+808 0 obj<</Subtype/Link/Rect[174.2 694.6 327.6 707.6]/Border[0 0 0]/Dest[1673 0 R/XYZ 0 466 0]>>endobj
+809 0 obj<</Subtype/Link/Rect[174.2 681.4 263.8 694.4]/Border[0 0 0]/Dest[1673 0 R/XYZ 0 381 0]>>endobj
+810 0 obj<</Subtype/Link/Rect[174.2 668.2 276.6 681.2]/Border[0 0 0]/Dest[1673 0 R/XYZ 0 283 0]>>endobj
+811 0 obj<</Subtype/Link/Rect[130.0 655.0 177.4 668.0]/Border[0 0 0]/Dest[1675 0 R/XYZ 0 397 0]>>endobj
+812 0 obj<</Subtype/Link/Rect[174.2 641.8 232.0 654.8]/Border[0 0 0]/Dest[1675 0 R/XYZ 0 363 0]>>endobj
+813 0 obj<</Subtype/Link/Rect[174.2 628.6 302.9 641.6]/Border[0 0 0]/Dest[1677 0 R/XYZ 0 429 0]>>endobj
+814 0 obj<</Subtype/Link/Rect[174.2 615.4 287.0 628.4]/Border[0 0 0]/Dest[1679 0 R/XYZ 0 665 0]>>endobj
+815 0 obj<</Subtype/Link/Rect[174.2 602.2 339.2 615.2]/Border[0 0 0]/Dest[1679 0 R/XYZ 0 485 0]>>endobj
+816 0 obj<</Subtype/Link/Rect[174.2 589.0 260.7 602.0]/Border[0 0 0]/Dest[1681 0 R/XYZ 0 734 0]>>endobj
+817 0 obj<</Subtype/Link/Rect[174.2 575.8 282.7 588.8]/Border[0 0 0]/Dest[1681 0 R/XYZ 0 394 0]>>endobj
+818 0 obj<</Subtype/Link/Rect[174.2 562.6 279.7 575.6]/Border[0 0 0]/Dest[1683 0 R/XYZ 0 718 0]>>endobj
+819 0 obj<</Subtype/Link/Rect[174.2 549.4 259.8 562.4]/Border[0 0 0]/Dest[1683 0 R/XYZ 0 633 0]>>endobj
+820 0 obj<</Subtype/Link/Rect[174.2 536.2 246.4 549.2]/Border[0 0 0]/Dest[1683 0 R/XYZ 0 535 0]>>endobj
+821 0 obj<</Subtype/Link/Rect[85.8 523.0 193.0 536.0]/Border[0 0 0]/Dest[1685 0 R/XYZ 0 734 0]>>endobj
+822 0 obj<</Subtype/Link/Rect[130.0 509.8 187.8 522.8]/Border[0 0 0]/Dest[1685 0 R/XYZ 0 696 0]>>endobj
+823 0 obj<</Subtype/Link/Rect[130.0 496.6 289.6 509.6]/Border[0 0 0]/Dest[1685 0 R/XYZ 0 463 0]>>endobj
+824 0 obj<</Subtype/Link/Rect[130.0 483.4 241.2 496.4]/Border[0 0 0]/Dest[1689 0 R/XYZ 0 276 0]>>endobj
+825 0 obj<</Subtype/Link/Rect[130.0 470.2 278.8 483.2]/Border[0 0 0]/Dest[1701 0 R/XYZ 0 546 0]>>endobj
+826 0 obj<</Subtype/Link/Rect[174.2 457.0 274.2 470.0]/Border[0 0 0]/Dest[1701 0 R/XYZ 0 404 0]>>endobj
+827 0 obj<</Subtype/Link/Rect[130.0 443.8 331.1 456.8]/Border[0 0 0]/Dest[1705 0 R/XYZ 0 177 0]>>endobj
+828 0 obj<</Subtype/Link/Rect[130.0 430.6 346.9 443.6]/Border[0 0 0]/Dest[1713 0 R/XYZ 0 362 0]>>endobj
+829 0 obj<</Subtype/Link/Rect[130.0 417.4 288.1 430.4]/Border[0 0 0]/Dest[1715 0 R/XYZ 0 527 0]>>endobj
+830 0 obj<</Subtype/Link/Rect[85.8 404.2 369.0 417.2]/Border[0 0 0]/Dest[1719 0 R/XYZ 0 734 0]>>endobj
+831 0 obj<</Subtype/Link/Rect[130.0 391.0 170.0 404.0]/Border[0 0 0]/Dest[1719 0 R/XYZ 0 672 0]>>endobj
+832 0 obj<</Subtype/Link/Rect[130.0 377.8 187.8 390.8]/Border[0 0 0]/Dest[1719 0 R/XYZ 0 544 0]>>endobj
+833 0 obj<</Subtype/Link/Rect[130.0 364.6 237.9 377.6]/Border[0 0 0]/Dest[1719 0 R/XYZ 0 231 0]>>endobj
+834 0 obj<</Subtype/Link/Rect[174.2 351.4 230.5 364.4]/Border[0 0 0]/Dest[1721 0 R/XYZ 0 560 0]>>endobj
+835 0 obj<</Subtype/Link/Rect[130.0 338.2 224.4 351.2]/Border[0 0 0]/Dest[1721 0 R/XYZ 0 409 0]>>endobj
+836 0 obj<</Subtype/Link/Rect[174.2 325.0 330.7 338.0]/Border[0 0 0]/Dest[1721 0 R/XYZ 0 294 0]>>endobj
+837 0 obj<</Subtype/Link/Rect[174.2 311.8 334.9 324.8]/Border[0 0 0]/Dest[1723 0 R/XYZ 0 734 0]>>endobj
+838 0 obj<</Subtype/Link/Rect[174.2 298.6 269.9 311.6]/Border[0 0 0]/Dest[1723 0 R/XYZ 0 635 0]>>endobj
+839 0 obj<</Subtype/Link/Rect[174.2 285.4 330.4 298.4]/Border[0 0 0]/Dest[1723 0 R/XYZ 0 194 0]>>endobj
+840 0 obj<</Subtype/Link/Rect[174.2 272.2 312.0 285.2]/Border[0 0 0]/Dest[1725 0 R/XYZ 0 560 0]>>endobj
+841 0 obj<</Subtype/Link/Rect[174.2 259.0 244.5 272.0]/Border[0 0 0]/Dest[1725 0 R/XYZ 0 383 0]>>endobj
+842 0 obj<</Subtype/Link/Rect[130.0 245.8 267.8 258.8]/Border[0 0 0]/Dest[1725 0 R/XYZ 0 245 0]>>endobj
+843 0 obj<</Subtype/Link/Rect[174.2 232.6 232.0 245.6]/Border[0 0 0]/Dest[1725 0 R/XYZ 0 143 0]>>endobj
+844 0 obj<</Subtype/Link/Rect[174.2 219.4 237.5 232.4]/Border[0 0 0]/Dest[1727 0 R/XYZ 0 533 0]>>endobj
+845 0 obj<</Subtype/Link/Rect[174.2 206.2 261.3 219.2]/Border[0 0 0]/Dest[1727 0 R/XYZ 0 264 0]>>endobj
+846 0 obj<</Subtype/Link/Rect[130.0 193.0 182.9 206.0]/Border[0 0 0]/Dest[1743 0 R/XYZ 0 555 0]>>endobj
+847 0 obj<</Subtype/Link/Rect[130.0 179.8 182.9 192.8]/Border[0 0 0]/Dest[1743 0 R/XYZ 0 335 0]>>endobj
+848 0 obj<</Subtype/Link/Rect[85.8 166.6 217.1 179.6]/Border[0 0 0]/Dest[1745 0 R/XYZ 0 734 0]>>endobj
+849 0 obj<</Subtype/Link/Rect[130.0 153.4 229.9 166.4]/Border[0 0 0]/Dest[1745 0 R/XYZ 0 696 0]>>endobj
+850 0 obj<</Subtype/Link/Rect[130.0 140.2 254.1 153.2]/Border[0 0 0]/Dest[1745 0 R/XYZ 0 463 0]>>endobj
+851 0 obj<</Subtype/Link/Rect[130.0 127.0 218.0 140.0]/Border[0 0 0]/Dest[1747 0 R/XYZ 0 734 0]>>endobj
+852 0 obj<</Subtype/Link/Rect[130.0 113.8 242.1 126.8]/Border[0 0 0]/Dest[1747 0 R/XYZ 0 381 0]>>endobj
+853 0 obj<</Subtype/Link/Rect[174.2 100.6 354.8 113.6]/Border[0 0 0]/Dest[1749 0 R/XYZ 0 734 0]>>endobj
+854 0 obj<</Subtype/Link/Rect[130.0 87.4 244.0 100.4]/Border[0 0 0]/Dest[1753 0 R/XYZ 0 332 0]>>endobj
+855 0 obj<</Subtype/Link/Rect[130.0 74.2 312.7 87.2]/Border[0 0 0]/Dest[1755 0 R/XYZ 0 388 0]>>endobj
+856 0 obj<</Subtype/Link/Rect[130.0 61.0 287.1 74.0]/Border[0 0 0]/Dest[1757 0 R/XYZ 0 407 0]>>endobj
+857 0 obj[806 0 R
+807 0 R
+808 0 R
+809 0 R
+810 0 R
+811 0 R
+812 0 R
+813 0 R
+814 0 R
+815 0 R
+816 0 R
+817 0 R
+818 0 R
+819 0 R
+820 0 R
+821 0 R
+822 0 R
+823 0 R
+824 0 R
+825 0 R
+826 0 R
+827 0 R
+828 0 R
+829 0 R
+830 0 R
+831 0 R
+832 0 R
+833 0 R
+834 0 R
+835 0 R
+836 0 R
+837 0 R
+838 0 R
+839 0 R
+840 0 R
+841 0 R
+842 0 R
+843 0 R
+844 0 R
+845 0 R
+846 0 R
+847 0 R
+848 0 R
+849 0 R
+850 0 R
+851 0 R
+852 0 R
+853 0 R
+854 0 R
+855 0 R
+856 0 R]endobj
+858 0 obj<</Subtype/Link/Rect[130.0 721.0 273.0 734.0]/Border[0 0 0]/Dest[1759 0 R/XYZ 0 718 0]>>endobj
+859 0 obj<</Subtype/Link/Rect[130.0 707.8 282.5 720.8]/Border[0 0 0]/Dest[1759 0 R/XYZ 0 300 0]>>endobj
+860 0 obj<</Subtype/Link/Rect[135.5 694.6 279.7 707.6]/Border[0 0 0]/Dest[1761 0 R/XYZ 0 520 0]>>endobj
+861 0 obj<</Subtype/Link/Rect[135.5 681.4 221.7 694.4]/Border[0 0 0]/Dest[1761 0 R/XYZ 0 432 0]>>endobj
+862 0 obj<</Subtype/Link/Rect[85.8 668.2 192.4 681.2]/Border[0 0 0]/Dest[1763 0 R/XYZ 0 734 0]>>endobj
+863 0 obj<</Subtype/Link/Rect[130.0 655.0 269.6 668.0]/Border[0 0 0]/Dest[1763 0 R/XYZ 0 696 0]>>endobj
+864 0 obj<</Subtype/Link/Rect[130.0 641.8 210.7 654.8]/Border[0 0 0]/Dest[1763 0 R/XYZ 0 385 0]>>endobj
+865 0 obj<</Subtype/Link/Rect[174.2 628.6 199.6 641.6]/Border[0 0 0]/Dest[1763 0 R/XYZ 0 351 0]>>endobj
+866 0 obj<</Subtype/Link/Rect[174.2 615.4 208.8 628.4]/Border[0 0 0]/Dest[1763 0 R/XYZ 0 215 0]>>endobj
+867 0 obj<</Subtype/Link/Rect[174.2 602.2 212.4 615.2]/Border[0 0 0]/Dest[1765 0 R/XYZ 0 560 0]>>endobj
+868 0 obj<</Subtype/Link/Rect[130.0 589.0 281.5 602.0]/Border[0 0 0]/Dest[1765 0 R/XYZ 0 430 0]>>endobj
+869 0 obj<</Subtype/Link/Rect[174.2 575.8 231.4 588.8]/Border[0 0 0]/Dest[1765 0 R/XYZ 0 315 0]>>endobj
+870 0 obj<</Subtype/Link/Rect[174.2 562.6 202.0 575.6]/Border[0 0 0]/Dest[1767 0 R/XYZ 0 734 0]>>endobj
+871 0 obj<</Subtype/Link/Rect[85.8 549.4 200.3 562.4]/Border[0 0 0]/Dest[1769 0 R/XYZ 0 734 0]>>endobj
+872 0 obj<</Subtype/Link/Rect[85.8 536.2 206.4 549.2]/Border[0 0 0]/Dest[1771 0 R/XYZ 0 734 0]>>endobj
+873 0 obj<</Subtype/Link/Rect[130.0 523.0 191.4 536.0]/Border[0 0 0]/Dest[1771 0 R/XYZ 0 696 0]>>endobj
+874 0 obj<</Subtype/Link/Rect[130.0 509.8 196.6 522.8]/Border[0 0 0]/Dest[1771 0 R/XYZ 0 449 0]>>endobj
+875 0 obj<</Subtype/Link/Rect[130.0 496.6 174.6 509.6]/Border[0 0 0]/Dest[1771 0 R/XYZ 0 189 0]>>endobj
+876 0 obj<</Subtype/Link/Rect[130.0 483.4 174.0 496.4]/Border[0 0 0]/Dest[1773 0 R/XYZ 0 639 0]>>endobj
+877 0 obj<</Subtype/Link/Rect[130.0 470.2 173.4 483.2]/Border[0 0 0]/Dest[1773 0 R/XYZ 0 458 0]>>endobj
+878 0 obj<</Subtype/Link/Rect[130.0 457.0 175.2 470.0]/Border[0 0 0]/Dest[1773 0 R/XYZ 0 383 0]>>endobj
+879 0 obj<</Subtype/Link/Rect[130.0 443.8 177.1 456.8]/Border[0 0 0]/Dest[1773 0 R/XYZ 0 215 0]>>endobj
+880 0 obj<</Subtype/Link/Rect[130.0 430.6 188.1 443.6]/Border[0 0 0]/Dest[1775 0 R/XYZ 0 734 0]>>endobj
+881 0 obj<</Subtype/Link/Rect[130.0 417.4 186.8 430.4]/Border[0 0 0]/Dest[1775 0 R/XYZ 0 605 0]>>endobj
+882 0 obj<</Subtype/Link/Rect[135.5 404.2 196.0 417.2]/Border[0 0 0]/Dest[1775 0 R/XYZ 0 530 0]>>endobj
+883 0 obj<</Subtype/Link/Rect[85.8 391.0 219.0 404.0]/Border[0 0 0]/Dest[1779 0 R/XYZ 0 734 0]>>endobj
+884 0 obj<</Subtype/Link/Rect[130.0 377.8 188.6 390.8]/Border[0 0 0]/Dest[1779 0 R/XYZ 0 696 0]>>endobj
+885 0 obj<</Subtype/Link/Rect[130.0 364.6 197.5 377.6]/Border[0 0 0]/Dest[1779 0 R/XYZ 0 423 0]>>endobj
+886 0 obj<</Subtype/Link/Rect[174.2 351.4 241.8 364.4]/Border[0 0 0]/Dest[1781 0 R/XYZ 0 734 0]>>endobj
+887 0 obj<</Subtype/Link/Rect[174.2 338.2 262.2 351.2]/Border[0 0 0]/Dest[1781 0 R/XYZ 0 635 0]>>endobj
+888 0 obj<</Subtype/Link/Rect[174.2 325.0 236.6 338.0]/Border[0 0 0]/Dest[1781 0 R/XYZ 0 564 0]>>endobj
+889 0 obj<</Subtype/Link/Rect[174.2 311.8 212.7 324.8]/Border[0 0 0]/Dest[1781 0 R/XYZ 0 492 0]>>endobj
+890 0 obj<</Subtype/Link/Rect[130.0 298.6 214.3 311.6]/Border[0 0 0]/Dest[1781 0 R/XYZ 0 328 0]>>endobj
+891 0 obj<</Subtype/Link/Rect[85.8 285.4 160.3 298.4]/Border[0 0 0]/Dest[1785 0 R/XYZ 0 734 0]>>endobj
+892 0 obj<</Subtype/Link/Rect[130.0 272.2 187.8 285.2]/Border[0 0 0]/Dest[1785 0 R/XYZ 0 696 0]>>endobj
+893 0 obj<</Subtype/Link/Rect[130.0 259.0 256.5 272.0]/Border[0 0 0]/Dest[1785 0 R/XYZ 0 621 0]>>endobj
+894 0 obj<</Subtype/Link/Rect[130.0 245.8 248.9 258.8]/Border[0 0 0]/Dest[1785 0 R/XYZ 0 405 0]>>endobj
+895 0 obj<</Subtype/Link/Rect[130.0 232.6 204.3 245.6]/Border[0 0 0]/Dest[1785 0 R/XYZ 0 150 0]>>endobj
+896 0 obj<</Subtype/Link/Rect[130.0 219.4 244.0 232.4]/Border[0 0 0]/Dest[1787 0 R/XYZ 0 596 0]>>endobj
+897 0 obj<</Subtype/Link/Rect[130.0 206.2 213.7 219.2]/Border[0 0 0]/Dest[1787 0 R/XYZ 0 290 0]>>endobj
+898 0 obj<</Subtype/Link/Rect[85.8 193.0 167.9 206.0]/Border[0 0 0]/Dest[1789 0 R/XYZ 0 734 0]>>endobj
+899 0 obj<</Subtype/Link/Rect[130.0 179.8 275.1 192.8]/Border[0 0 0]/Dest[1789 0 R/XYZ 0 696 0]>>endobj
+900 0 obj<</Subtype/Link/Rect[130.0 166.6 221.4 179.6]/Border[0 0 0]/Dest[1789 0 R/XYZ 0 397 0]>>endobj
+901 0 obj[858 0 R
+859 0 R
+860 0 R
+861 0 R
+862 0 R
+863 0 R
+864 0 R
+865 0 R
+866 0 R
+867 0 R
+868 0 R
+869 0 R
+870 0 R
+871 0 R
+872 0 R
+873 0 R
+874 0 R
+875 0 R
+876 0 R
+877 0 R
+878 0 R
+879 0 R
+880 0 R
+881 0 R
+882 0 R
+883 0 R
+884 0 R
+885 0 R
+886 0 R
+887 0 R
+888 0 R
+889 0 R
+890 0 R
+891 0 R
+892 0 R
+893 0 R
+894 0 R
+895 0 R
+896 0 R
+897 0 R
+898 0 R
+899 0 R
+900 0 R]endobj
+902 0 obj<</S/Launch/F(ENCRYPTION.html)>>endobj
+903 0 obj<</Subtype/Link/Rect[174.0 562.6 270.6 575.6]/Border[0 0 0]/A 902 0 R>>endobj
+904 0 obj<</S/Launch/F(#PASSWORDLEVEL)>>endobj
+905 0 obj<</Subtype/Link/Rect[72.0 300.6 153.0 311.6]/Border[0 0 0]/A 904 0 R>>endobj
+906 0 obj<</S/Launch/F(#USERNAMELEVEL)>>endobj
+907 0 obj<</Subtype/Link/Rect[72.0 289.8 147.6 300.8]/Border[0 0 0]/A 906 0 R>>endobj
+908 0 obj[903 0 R
+905 0 R
+907 0 R]endobj
+909 0 obj<</S/Launch/F(winbind.html)>>endobj
+910 0 obj<</Subtype/Link/Rect[503.4 161.0 544.6 174.0]/Border[0 0 0]/A 909 0 R>>endobj
+911 0 obj<</S/Launch/F(winbind.html)>>endobj
+912 0 obj<</Subtype/Link/Rect[72.0 147.8 115.4 160.8]/Border[0 0 0]/A 911 0 R>>endobj
+913 0 obj[910 0 R
+912 0 R]endobj
+914 0 obj<</S/Launch/F(#SECURITYMASK)>>endobj
+915 0 obj<</Subtype/Link/Rect[490.3 75.0 531.2 88.0]/Border[0 0 0]/A 914 0 R>>endobj
+916 0 obj<</S/Launch/F(#SECURITYMASK)>>endobj
+917 0 obj<</Subtype/Link/Rect[72.0 61.8 98.3 74.8]/Border[0 0 0]/A 916 0 R>>endobj
+918 0 obj[915 0 R
+917 0 R]endobj
+919 0 obj<</S/Launch/F(#CREATEMASK)>>endobj
+920 0 obj<</Subtype/Link/Rect[353.4 655.0 416.3 668.0]/Border[0 0 0]/A 919 0 R>>endobj
+921 0 obj<</S/Launch/F(#FORCESECURITYMODE)>>endobj
+922 0 obj<</Subtype/Link/Rect[421.5 602.2 520.5 615.2]/Border[0 0 0]/A 921 0 R>>endobj
+923 0 obj<</S/Launch/F(#FORCECREATEMODE)>>endobj
+924 0 obj<</Subtype/Link/Rect[353.4 523.0 445.1 536.0]/Border[0 0 0]/A 923 0 R>>endobj
+925 0 obj<</S/Launch/F(smb.conf.5.html)>>endobj
+926 0 obj<</Subtype/Link/Rect[72.0 259.0 144.6 272.0]/Border[0 0 0]/A 925 0 R>>endobj
+927 0 obj[920 0 R
+922 0 R
+924 0 R
+926 0 R]endobj
+928 0 obj<</S/URI/URI(http://rsync.samba.org/)>>endobj
+929 0 obj<</Subtype/Link/Rect[118.1 89.0 222.3 102.0]/Border[0 0 0]/A 928 0 R>>endobj
+930 0 obj[929 0 R]endobj
+931 0 obj<</S/Launch/F(#OBEYPAMRESTRICTIONS)>>endobj
+932 0 obj<</Subtype/Link/Rect[235.4 659.0 332.9 672.0]/Border[0 0 0]/A 931 0 R>>endobj
+933 0 obj<</S/Launch/F(#ENCRYPTPASSWORDS)>>endobj
+934 0 obj<</Subtype/Link/Rect[338.7 579.8 449.4 592.8]/Border[0 0 0]/A 933 0 R>>endobj
+935 0 obj[932 0 R
+934 0 R]endobj
+936 0 obj<</S/URI/URI(http://www.microsoft.com/NTServer/nts/downloads/winfeatures/NTSDistrFile/AdminGuide.asp)>>endobj
+937 0 obj<</Subtype/Link/Rect[72.0 586.6 183.5 599.6]/Border[0 0 0]/A 936 0 R>>endobj
+938 0 obj<</S/Launch/F(#HOSTMSDFS)>>endobj
+939 0 obj<</Subtype/Link/Rect[342.3 507.4 398.6 520.4]/Border[0 0 0]/A 938 0 R>>endobj
+940 0 obj<</S/Launch/F(#MSDFSROOT)>>endobj
+941 0 obj<</Subtype/Link/Rect[357.9 494.2 412.3 507.2]/Border[0 0 0]/A 940 0 R>>endobj
+942 0 obj[937 0 R
+939 0 R
+941 0 R]endobj
+943 0 obj<</S/URI/URI(http://imprints.sourceforge.net)>>endobj
+944 0 obj<</Subtype/Link/Rect[143.7 544.6 280.3 557.6]/Border[0 0 0]/A 943 0 R>>endobj
+945 0 obj<</S/URI/URI(http://msdn.microsoft.com/)>>endobj
+946 0 obj<</Subtype/Link/Rect[218.6 518.2 341.1 531.2]/Border[0 0 0]/A 945 0 R>>endobj
+947 0 obj<</S/URI/URI(http://support.microsoft.com/support/kb/articles/Q189/1/05.ASP)>>endobj
+948 0 obj<</Subtype/Link/Rect[72.0 333.4 355.9 346.4]/Border[0 0 0]/A 947 0 R>>endobj
+949 0 obj[944 0 R
+946 0 R
+948 0 R]endobj
+950 0 obj<</S/Launch/F(#WRITELIST)>>endobj
+951 0 obj<</Subtype/Link/Rect[89.1 445.0 131.9 458.0]/Border[0 0 0]/A 950 0 R>>endobj
+952 0 obj<</S/Launch/F(smb.conf.5.html)>>endobj
+953 0 obj<</Subtype/Link/Rect[162.7 431.8 264.1 444.8]/Border[0 0 0]/A 952 0 R>>endobj
+954 0 obj<</S/Launch/F(#GUESTOK)>>endobj
+955 0 obj<</Subtype/Link/Rect[160.6 405.4 228.6 418.4]/Border[0 0 0]/A 954 0 R>>endobj
+956 0 obj<</S/Launch/F(#MAPTOGUEST)>>endobj
+957 0 obj<</Subtype/Link/Rect[501.3 291.5 536.7 304.5]/Border[0 0 0]/A 956 0 R>>endobj
+958 0 obj<</S/Launch/F(#MAPTOGUEST)>>endobj
+959 0 obj<</Subtype/Link/Rect[94.2 278.3 174.1 291.3]/Border[0 0 0]/A 958 0 R>>endobj
+960 0 obj[951 0 R
+953 0 R
+955 0 R
+957 0 R
+959 0 R]endobj
+961 0 obj<</S/Launch/F(#PRINTERADMIN)>>endobj
+962 0 obj<</Subtype/Link/Rect[448.5 680.0 515.8 693.0]/Border[0 0 0]/A 961 0 R>>endobj
+963 0 obj[962 0 R]endobj
+964 0 obj<</S/Launch/F(rpcclient.1.html)>>endobj
+965 0 obj<</Subtype/Link/Rect[233.6 664.6 379.3 677.6]/Border[0 0 0]/A 964 0 R>>endobj
+966 0 obj<</S/Launch/F(#SHOWADDPRINTERWIZARD)>>endobj
+967 0 obj<</Subtype/Link/Rect[108.0 254.6 253.8 267.6]/Border[0 0 0]/A 966 0 R>>endobj
+968 0 obj<</S/Launch/F(#ADDPRINTERCOMMAND)>>endobj
+969 0 obj<</Subtype/Link/Rect[451.1 228.2 558.1 241.2]/Border[0 0 0]/A 968 0 R>>endobj
+970 0 obj<</S/Launch/F(#DELETEPRINTERCOMMAND)>>endobj
+971 0 obj<</Subtype/Link/Rect[186.6 109.4 305.2 122.4]/Border[0 0 0]/A 970 0 R>>endobj
+972 0 obj<</S/Launch/F(#ADDPRINTERCOMMAN)>>endobj
+973 0 obj<</Subtype/Link/Rect[197.9 83.0 304.9 96.0]/Border[0 0 0]/A 972 0 R>>endobj
+974 0 obj[965 0 R
+967 0 R
+969 0 R
+971 0 R
+973 0 R]endobj
+975 0 obj<</S/Launch/F(#ENUMPORTSCOMMAND)>>endobj
+976 0 obj<</Subtype/Link/Rect[448.6 721.0 555.0 734.0]/Border[0 0 0]/A 975 0 R>>endobj
+977 0 obj<</S/URI/URI(http://imprints.sourceforge.net/)>>endobj
+978 0 obj<</Subtype/Link/Rect[297.8 632.6 437.4 645.6]/Border[0 0 0]/A 977 0 R>>endobj
+979 0 obj[976 0 R
+978 0 R]endobj
+980 0 obj<</S/URI/URI(http://www.linuxprinting.org/printer_list.cgi)>>endobj
+981 0 obj<</Subtype/Link/Rect[72.0 322.2 267.3 335.2]/Border[0 0 0]/A 980 0 R>>endobj
+982 0 obj<</S/URI/URI(http://www.linuxprinting.org/show_printer.cgi?recnum=75104)>>endobj
+983 0 obj<</Subtype/Link/Rect[72.0 243.0 348.6 256.0]/Border[0 0 0]/A 982 0 R>>endobj
+984 0 obj<</S/URI/URI(http://www.linuxprinting.org/show_driver.cgi?driver=ljet4)>>endobj
+985 0 obj<</Subtype/Link/Rect[72.0 190.2 330.9 203.2]/Border[0 0 0]/A 984 0 R>>endobj
+986 0 obj[981 0 R
+983 0 R
+985 0 R]endobj
+987 0 obj<</S/URI/URI(http://www.linuxprinting.org/cupsomatic)>>endobj
+988 0 obj<</Subtype/Link/Rect[72.0 631.0 252.9 644.0]/Border[0 0 0]/A 987 0 R>>endobj
+989 0 obj<</S/URI/URI(http://www.linuxprinting.org/execution.cgi?driver=ljet4&printer=75104&.submit=Show+execution+details)>>endobj
+990 0 obj<</Subtype/Link/Rect[72.0 485.8 546.7 498.8]/Border[0 0 0]/A 989 0 R>>endobj
+991 0 obj<</S/URI/URI(http://www.linuxprinting.org/cups-doc.html)>>endobj
+992 0 obj<</Subtype/Link/Rect[72.0 298.1 268.0 311.1]/Border[0 0 0]/A 991 0 R>>endobj
+993 0 obj<</S/URI/URI(http://www.linuxprinting.org/kpfeifle/LinuxKongress2002/Tutorial/)>>endobj
+994 0 obj<</Subtype/Link/Rect[72.0 245.3 371.4 258.3]/Border[0 0 0]/A 993 0 R>>endobj
+995 0 obj[988 0 R
+990 0 R
+992 0 R
+994 0 R]endobj
+996 0 obj<</S/URI/URI(http://www.cups.org/software.html)>>endobj
+997 0 obj<</Subtype/Link/Rect[157.8 460.9 314.9 473.9]/Border[0 0 0]/A 996 0 R>>endobj
+998 0 obj[997 0 R]endobj
+999 0 obj<</S/URI/URI(http://www.cups.org/software.html)>>endobj
+1000 0 obj<</Subtype/Link/Rect[246.1 231.6 403.2 244.6]/Border[0 0 0]/A 999 0 R>>endobj
+1001 0 obj[1000 0 R]endobj
+1002 0 obj<</S/URI/URI(mailto:jtrostel@snapserver.com)>>endobj
+1003 0 obj<</Subtype/Link/Rect[197.9 199.0 310.1 212.0]/Border[0 0 0]/A 1002 0 R>>endobj
+1004 0 obj[1003 0 R]endobj
+1005 0 obj<</S/URI/URI(http://samba.org/)>>endobj
+1006 0 obj<</Subtype/Link/Rect[151.1 372.2 262.3 385.2]/Border[0 0 0]/A 1005 0 R>>endobj
+1007 0 obj[1006 0 R]endobj
+1008 0 obj<</S/Launch/F(winbindd.8.html)>>endobj
+1009 0 obj<</Subtype/Link/Rect[306.3 157.8 363.4 170.8]/Border[0 0 0]/A 1008 0 R>>endobj
+1010 0 obj<</S/Launch/F(#WINBINDSEPARATOR)>>endobj
+1011 0 obj<</Subtype/Link/Rect[99.0 87.8 190.8 98.8]/Border[0 0 0]/A 1010 0 R>>endobj
+1012 0 obj<</S/Launch/F(#WINBINDUID)>>endobj
+1013 0 obj<</Subtype/Link/Rect[99.0 66.2 158.4 77.2]/Border[0 0 0]/A 1012 0 R>>endobj
+1014 0 obj[1009 0 R
+1011 0 R
+1013 0 R]endobj
+1015 0 obj<</S/Launch/F(#WINBINDGID)>>endobj
+1016 0 obj<</Subtype/Link/Rect[99.0 712.2 158.4 723.2]/Border[0 0 0]/A 1015 0 R>>endobj
+1017 0 obj<</S/Launch/F(#WINBINDENUMUSERS)>>endobj
+1018 0 obj<</Subtype/Link/Rect[99.0 690.6 196.2 701.6]/Border[0 0 0]/A 1017 0 R>>endobj
+1019 0 obj<</S/Launch/F(#WINBINDENUMGROUP)>>endobj
+1020 0 obj<</Subtype/Link/Rect[99.0 679.8 201.6 690.8]/Border[0 0 0]/A 1019 0 R>>endobj
+1021 0 obj<</S/Launch/F(#TEMPLATEHOMEDIR)>>endobj
+1022 0 obj<</Subtype/Link/Rect[99.0 658.2 185.4 669.2]/Border[0 0 0]/A 1021 0 R>>endobj
+1023 0 obj<</S/Launch/F(#TEMPLATESHELL)>>endobj
+1024 0 obj<</Subtype/Link/Rect[99.0 647.4 174.6 658.4]/Border[0 0 0]/A 1023 0 R>>endobj
+1025 0 obj[1016 0 R
+1018 0 R
+1020 0 R
+1022 0 R
+1024 0 R]endobj
+1026 0 obj<</S/URI/URI(http://www.css.tayloru.edu/~elorimer/databasefs/index.php)>>endobj
+1027 0 obj<</Subtype/Link/Rect[97.1 272.5 360.6 285.5]/Border[0 0 0]/A 1026 0 R>>endobj
+1028 0 obj<</S/URI/URI(mailto:elorimer@css.tayloru.edu)>>endobj
+1029 0 obj<</Subtype/Link/Rect[84.8 246.1 144.7 259.1]/Border[0 0 0]/A 1028 0 R>>endobj
+1030 0 obj[1027 0 R
+1029 0 R]endobj
+1031 0 obj<</S/URI/URI(http://www.openantivirus.org/)>>endobj
+1032 0 obj<</Subtype/Link/Rect[97.1 691.0 233.0 704.0]/Border[0 0 0]/A 1031 0 R>>endobj
+1033 0 obj[1032 0 R]endobj
+1034 0 obj<</S/URI/URI(http://www.unicode.org/)>>endobj
+1035 0 obj<</Subtype/Link/Rect[340.5 505.0 422.1 518.0]/Border[0 0 0]/A 1034 0 R>>endobj
+1036 0 obj[1035 0 R]endobj
+1037 0 obj<</Subtype/Link/Rect[85.8 670.6 136.2 683.6]/Border[0 0 0]/Dest[1795 0 R/XYZ 0 734 0]>>endobj
+1038 0 obj<</Subtype/Link/Rect[130.0 657.4 162.1 670.4]/Border[0 0 0]/Dest[1795 0 R/XYZ 0 655 0]>>endobj
+1039 0 obj<</Subtype/Link/Rect[130.0 644.2 177.7 657.2]/Border[0 0 0]/Dest[1795 0 R/XYZ 0 408 0]>>endobj
+1040 0 obj<</Subtype/Link/Rect[130.0 631.0 158.4 644.0]/Border[0 0 0]/Dest[1795 0 R/XYZ 0 293 0]>>endobj
+1041 0 obj<</Subtype/Link/Rect[130.0 617.8 260.5 630.8]/Border[0 0 0]/Dest[1797 0 R/XYZ 0 228 0]>>endobj
+1042 0 obj<</Subtype/Link/Rect[130.0 604.6 149.9 617.6]/Border[0 0 0]/Dest[1799 0 R/XYZ 0 734 0]>>endobj
+1043 0 obj<</Subtype/Link/Rect[174.2 591.4 279.7 604.4]/Border[0 0 0]/Dest[1799 0 R/XYZ 0 700 0]>>endobj
+1044 0 obj<</Subtype/Link/Rect[85.8 578.2 221.1 591.2]/Border[0 0 0]/Dest[1801 0 R/XYZ 0 734 0]>>endobj
+1045 0 obj<</Subtype/Link/Rect[130.0 565.0 216.2 578.0]/Border[0 0 0]/Dest[1801 0 R/XYZ 0 668 0]>>endobj
+1046 0 obj<</Subtype/Link/Rect[130.0 551.8 181.3 564.8]/Border[0 0 0]/Dest[1801 0 R/XYZ 0 461 0]>>endobj
+1047 0 obj<</Subtype/Link/Rect[174.2 538.6 533.6 551.6]/Border[0 0 0]/Dest[1801 0 R/XYZ 0 427 0]>>endobj
+1048 0 obj<</Subtype/Link/Rect[174.2 525.4 536.9 538.4]/Border[0 0 0]/Dest[1803 0 R/XYZ 0 734 0]>>endobj
+1049 0 obj<</Subtype/Link/Rect[174.2 512.2 490.2 525.2]/Border[0 0 0]/Dest[1803 0 R/XYZ 0 523 0]>>endobj
+1050 0 obj<</Subtype/Link/Rect[174.2 499.0 459.3 512.0]/Border[0 0 0]/Dest[1803 0 R/XYZ 0 408 0]>>endobj
+1051 0 obj<</Subtype/Link/Rect[130.0 485.8 245.8 498.8]/Border[0 0 0]/Dest[1803 0 R/XYZ 0 151 0]>>endobj
+1052 0 obj<</Subtype/Link/Rect[174.2 472.6 351.5 485.6]/Border[0 0 0]/Dest[1803 0 R/XYZ 0 118 0]>>endobj
+1053 0 obj<</Subtype/Link/Rect[174.2 459.4 351.2 472.4]/Border[0 0 0]/Dest[1805 0 R/XYZ 0 626 0]>>endobj
+1054 0 obj<</Subtype/Link/Rect[174.2 446.2 332.5 459.2]/Border[0 0 0]/Dest[1805 0 R/XYZ 0 475 0]>>endobj
+1055 0 obj<</Subtype/Link/Rect[174.2 433.0 301.4 446.0]/Border[0 0 0]/Dest[1805 0 R/XYZ 0 377 0]>>endobj
+1056 0 obj<</Subtype/Link/Rect[174.2 419.8 316.3 432.8]/Border[0 0 0]/Dest[1805 0 R/XYZ 0 292 0]>>endobj
+1057 0 obj<</Subtype/Link/Rect[130.0 406.6 205.6 419.6]/Border[0 0 0]/Dest[1805 0 R/XYZ 0 207 0]>>endobj
+1058 0 obj<</Subtype/Link/Rect[130.0 393.4 265.9 406.4]/Border[0 0 0]/Dest[1807 0 R/XYZ 0 626 0]>>endobj
+1059 0 obj<</Subtype/Link/Rect[85.8 380.2 195.7 393.2]/Border[0 0 0]/Dest[1809 0 R/XYZ 0 734 0]>>endobj
+1060 0 obj<</Subtype/Link/Rect[130.0 367.0 289.5 380.0]/Border[0 0 0]/Dest[1809 0 R/XYZ 0 655 0]>>endobj
+1061 0 obj<</Subtype/Link/Rect[174.2 353.8 232.0 366.8]/Border[0 0 0]/Dest[1809 0 R/XYZ 0 621 0]>>endobj
+1062 0 obj<</Subtype/Link/Rect[174.2 340.6 290.0 353.6]/Border[0 0 0]/Dest[1809 0 R/XYZ 0 510 0]>>endobj
+1063 0 obj<</Subtype/Link/Rect[130.0 327.4 337.1 340.4]/Border[0 0 0]/Dest[1811 0 R/XYZ 0 494 0]>>endobj
+1064 0 obj<</Subtype/Link/Rect[130.0 314.2 226.9 327.2]/Border[0 0 0]/Dest[1811 0 R/XYZ 0 353 0]>>endobj
+1065 0 obj<</Subtype/Link/Rect[130.0 301.0 256.8 314.0]/Border[0 0 0]/Dest[1813 0 R/XYZ 0 613 0]>>endobj
+1066 0 obj<</Subtype/Link/Rect[174.2 287.8 282.4 300.8]/Border[0 0 0]/Dest[1813 0 R/XYZ 0 458 0]>>endobj
+1067 0 obj<</Subtype/Link/Rect[174.2 274.6 333.8 287.6]/Border[0 0 0]/Dest[1815 0 R/XYZ 0 639 0]>>endobj
+1068 0 obj<</Subtype/Link/Rect[85.8 261.4 157.2 274.4]/Border[0 0 0]/Dest[1817 0 R/XYZ 0 734 0]>>endobj
+1069 0 obj<</Subtype/Link/Rect[130.0 248.2 187.8 261.2]/Border[0 0 0]/Dest[1817 0 R/XYZ 0 696 0]>>endobj
+1070 0 obj<</Subtype/Link/Rect[130.0 235.0 188.7 248.0]/Border[0 0 0]/Dest[1817 0 R/XYZ 0 423 0]>>endobj
+1071 0 obj<</Subtype/Link/Rect[130.0 221.8 189.9 234.8]/Border[0 0 0]/Dest[1817 0 R/XYZ 0 282 0]>>endobj
+1072 0 obj<</Subtype/Link/Rect[130.0 208.6 198.4 221.6]/Border[0 0 0]/Dest[1819 0 R/XYZ 0 613 0]>>endobj
+1073 0 obj<</Subtype/Link/Rect[130.0 195.4 269.0 208.4]/Border[0 0 0]/Dest[1819 0 R/XYZ 0 260 0]>>endobj
+1074 0 obj<</Subtype/Link/Rect[130.0 182.2 167.6 195.2]/Border[0 0 0]/Dest[1819 0 R/XYZ 0 159 0]>>endobj
+1075 0 obj<</Subtype/Link/Rect[85.8 169.0 177.7 182.0]/Border[0 0 0]/Dest[1821 0 R/XYZ 0 734 0]>>endobj
+1076 0 obj<</Subtype/Link/Rect[130.0 155.8 187.8 168.8]/Border[0 0 0]/Dest[1821 0 R/XYZ 0 696 0]>>endobj
+1077 0 obj<</Subtype/Link/Rect[130.0 142.6 188.4 155.6]/Border[0 0 0]/Dest[1821 0 R/XYZ 0 529 0]>>endobj
+1078 0 obj<</Subtype/Link/Rect[130.0 129.4 155.4 142.4]/Border[0 0 0]/Dest[1821 0 R/XYZ 0 199 0]>>endobj
+1079 0 obj<</Subtype/Link/Rect[174.2 116.2 203.6 129.2]/Border[0 0 0]/Dest[1821 0 R/XYZ 0 165 0]>>endobj
+1080 0 obj<</Subtype/Link/Rect[174.2 103.0 203.6 116.0]/Border[0 0 0]/Dest[1823 0 R/XYZ 0 734 0]>>endobj
+1081 0 obj<</Subtype/Link/Rect[174.2 89.8 203.6 102.8]/Border[0 0 0]/Dest[1823 0 R/XYZ 0 530 0]>>endobj
+1082 0 obj<</Subtype/Link/Rect[174.2 76.6 203.6 89.6]/Border[0 0 0]/Dest[1825 0 R/XYZ 0 626 0]>>endobj
+1083 0 obj<</Subtype/Link/Rect[174.2 63.4 203.6 76.4]/Border[0 0 0]/Dest[1825 0 R/XYZ 0 475 0]>>endobj
+1084 0 obj[1037 0 R
+1038 0 R
+1039 0 R
+1040 0 R
+1041 0 R
+1042 0 R
+1043 0 R
+1044 0 R
+1045 0 R
+1046 0 R
+1047 0 R
+1048 0 R
+1049 0 R
+1050 0 R
+1051 0 R
+1052 0 R
+1053 0 R
+1054 0 R
+1055 0 R
+1056 0 R
+1057 0 R
+1058 0 R
+1059 0 R
+1060 0 R
+1061 0 R
+1062 0 R
+1063 0 R
+1064 0 R
+1065 0 R
+1066 0 R
+1067 0 R
+1068 0 R
+1069 0 R
+1070 0 R
+1071 0 R
+1072 0 R
+1073 0 R
+1074 0 R
+1075 0 R
+1076 0 R
+1077 0 R
+1078 0 R
+1079 0 R
+1080 0 R
+1081 0 R
+1082 0 R
+1083 0 R]endobj
+1085 0 obj<</Subtype/Link/Rect[174.2 721.0 203.6 734.0]/Border[0 0 0]/Dest[1825 0 R/XYZ 0 351 0]>>endobj
+1086 0 obj<</Subtype/Link/Rect[174.2 707.8 203.6 720.8]/Border[0 0 0]/Dest[1827 0 R/XYZ 0 734 0]>>endobj
+1087 0 obj<</Subtype/Link/Rect[174.2 694.6 203.6 707.6]/Border[0 0 0]/Dest[1827 0 R/XYZ 0 371 0]>>endobj
+1088 0 obj<</Subtype/Link/Rect[174.2 681.4 203.6 694.4]/Border[0 0 0]/Dest[1829 0 R/XYZ 0 705 0]>>endobj
+1089 0 obj<</Subtype/Link/Rect[179.8 668.2 214.6 681.2]/Border[0 0 0]/Dest[1829 0 R/XYZ 0 515 0]>>endobj
+1090 0 obj<</Subtype/Link/Rect[179.8 655.0 214.6 668.0]/Border[0 0 0]/Dest[1829 0 R/XYZ 0 377 0]>>endobj
+1091 0 obj<</Subtype/Link/Rect[130.0 641.8 227.5 654.8]/Border[0 0 0]/Dest[1829 0 R/XYZ 0 239 0]>>endobj
+1092 0 obj[1085 0 R
+1086 0 R
+1087 0 R
+1088 0 R
+1089 0 R
+1090 0 R
+1091 0 R]endobj
+1093 0 obj<</S/URI/URI(http://www.thursby.com/)>>endobj
+1094 0 obj<</Subtype/Link/Rect[91.9 621.8 131.3 634.8]/Border[0 0 0]/A 1093 0 R>>endobj
+1095 0 obj<</S/URI/URI(http://www.umich.edu/~rsug/netatalk/)>>endobj
+1096 0 obj<</Subtype/Link/Rect[72.0 503.0 109.3 516.0]/Border[0 0 0]/A 1095 0 R>>endobj
+1097 0 obj<</S/URI/URI(http://www.cs.mu.oz.au/appletalk/atalk.html)>>endobj
+1098 0 obj<</Subtype/Link/Rect[130.7 503.0 154.8 516.0]/Border[0 0 0]/A 1097 0 R>>endobj
+1099 0 obj<</S/URI/URI(http://www.eats.com/linux_mac_win.html)>>endobj
+1100 0 obj<</Subtype/Link/Rect[72.0 476.6 258.1 489.6]/Border[0 0 0]/A 1099 0 R>>endobj
+1101 0 obj<</S/URI/URI(http://carol.wins.uva.nl/~leeuw/samba/warp.html)>>endobj
+1102 0 obj<</Subtype/Link/Rect[325.6 367.8 544.5 380.8]/Border[0 0 0]/A 1101 0 R>>endobj
+1103 0 obj[1094 0 R
+1096 0 R
+1098 0 R
+1100 0 R
+1102 0 R]endobj
+1104 0 obj<</S/URI/URI(ftp://ftp.microsoft.com/BusSys/Clients/LANMAN.OS2/)>>endobj
+1105 0 obj<</Subtype/Link/Rect[72.0 661.0 319.2 674.0]/Border[0 0 0]/A 1104 0 R>>endobj
+1106 0 obj<</S/URI/URI(http://carol.wins.uva.nl/~leeuw/lanman.html)>>endobj
+1107 0 obj<</Subtype/Link/Rect[340.6 661.0 538.7 674.0]/Border[0 0 0]/A 1106 0 R>>endobj
+1108 0 obj<</S/URI/URI(ftp://ftp.cdrom.com/pub/os2/network/ndis/)>>endobj
+1109 0 obj<</Subtype/Link/Rect[173.1 538.6 363.5 551.6]/Border[0 0 0]/A 1108 0 R>>endobj
+1110 0 obj<</S/URI/URI(http://carol.wins.uva.nl/~leeuw/samba/fix.html)>>endobj
+1111 0 obj<</Subtype/Link/Rect[220.2 450.2 429.3 463.2]/Border[0 0 0]/A 1110 0 R>>endobj
+1112 0 obj[1105 0 R
+1107 0 R
+1109 0 R
+1111 0 R]endobj
+1113 0 obj<</S/Launch/F(smb.conf.5.html)>>endobj
+1114 0 obj<</Subtype/Link/Rect[218.7 321.4 274.9 334.4]/Border[0 0 0]/A 1113 0 R>>endobj
+1115 0 obj[1114 0 R]endobj
+1116 0 obj<</S/Launch/F(smb.conf.5.html)>>endobj
+1117 0 obj<</Subtype/Link/Rect[493.6 487.4 549.8 500.4]/Border[0 0 0]/A 1116 0 R>>endobj
+1118 0 obj[1117 0 R]endobj
+1119 0 obj<</S/URI/URI(http://samba.org/)>>endobj
+1120 0 obj<</Subtype/Link/Rect[258.0 683.8 325.3 696.8]/Border[0 0 0]/A 1119 0 R>>endobj
+1121 0 obj<</S/URI/URI(http://samba.org/samba/cvs.html)>>endobj
+1122 0 obj<</Subtype/Link/Rect[343.3 525.8 489.7 538.8]/Border[0 0 0]/A 1121 0 R>>endobj
+1123 0 obj<</S/URI/URI(http://samba.org/cgi-bin/cvsweb)>>endobj
+1124 0 obj<</Subtype/Link/Rect[135.9 333.4 283.2 346.4]/Border[0 0 0]/A 1123 0 R>>endobj
+1125 0 obj<</S/URI/URI(http://www.cyclic.com/)>>endobj
+1126 0 obj<</Subtype/Link/Rect[391.6 225.8 498.2 238.8]/Border[0 0 0]/A 1125 0 R>>endobj
+1127 0 obj[1120 0 R
+1122 0 R
+1124 0 R
+1126 0 R]endobj
+1128 0 obj<</S/URI/URI(ftp://pserver.samba.org/pub/unpacked)>>endobj
+1129 0 obj<</Subtype/Link/Rect[72.0 434.6 238.8 447.6]/Border[0 0 0]/A 1128 0 R>>endobj
+1130 0 obj<</S/URI/URI(http://rsync.samba.org/)>>endobj
+1131 0 obj<</Subtype/Link/Rect[452.6 421.4 543.4 434.4]/Border[0 0 0]/A 1130 0 R>>endobj
+1132 0 obj[1129 0 R
+1131 0 R]endobj
+1133 0 obj<</S/Launch/F(samba@samba.org)>>endobj
+1134 0 obj<</Subtype/Link/Rect[311.8 650.2 398.3 663.2]/Border[0 0 0]/A 1133 0 R>>endobj
+1135 0 obj<</S/URI/URI(mailto:samba-technical@samba.org)>>endobj
+1136 0 obj<</Subtype/Link/Rect[126.4 637.0 258.8 650.0]/Border[0 0 0]/A 1135 0 R>>endobj
+1137 0 obj<</S/URI/URI(http://samba.org/samba/)>>endobj
+1138 0 obj<</Subtype/Link/Rect[161.5 439.0 270.3 452.0]/Border[0 0 0]/A 1137 0 R>>endobj
+1139 0 obj<</S/Launch/F(Diagnosis.html)>>endobj
+1140 0 obj<</Subtype/Link/Rect[185.0 337.4 229.3 350.4]/Border[0 0 0]/A 1139 0 R>>endobj
+1141 0 obj[1134 0 R
+1136 0 R
+1138 0 R
+1140 0 R]endobj
+1142 0 obj<</S/URI/URI(mailto:samba@samba.org)>>endobj
+1143 0 obj<</Subtype/Link/Rect[164.2 180.2 250.8 193.2]/Border[0 0 0]/A 1142 0 R>>endobj
+1144 0 obj<</S/URI/URI(http://samba.org/samba)>>endobj
+1145 0 obj<</Subtype/Link/Rect[233.0 167.0 338.7 180.0]/Border[0 0 0]/A 1144 0 R>>endobj
+1146 0 obj[1143 0 R
+1145 0 R]endobj
+1147 0 obj<</Dests 1148 0 R>>endobj
+1148 0 obj<</Kids[1149 0 R]>>endobj
+1149 0 obj<</Limits[(16)(winbind)]/Names[(16)1150 0 R(17)1151 0 R(3)1152 0 R(32)1153 0 R(4)1154 0 R(8)1155 0 R(9)1156 0 R(ads)1157 0 R(aen103)1158 0 R(aen108)1159 0 R(aen1104)1160 0 R(aen111)1161 0 R(aen1130)1162 0 R(aen1149)1163 0 R(aen1157)1164 0 R(aen1165)1165 0 R(aen1173)1166 0 R(aen1180)1167 0 R(aen1216)1168 0 R(aen1229)1169 0 R(aen1232)1170 0 R(aen1242)1171 0 R(aen1278)1172 0 R(aen1282)1173 0 R(aen1290)1174 0 R(aen1293)1175 0 R(aen1296)1176 0 R(aen1299)1177 0 R(aen130)1178 0 R(aen1304)1179 0 R(aen1321)1180 0 R(aen1325)1181 0 R(aen1343)1182 0 R(aen1350)1183 0 R(aen1360)1184 0 R(aen1375)1185 0 R(aen1385)1186 0 R(aen1389)1187 0 R(aen139)1188 0 R(aen1397)1189 0 R(aen1402)1190 0 R(aen1405)1191 0 R(aen1427)1192 0 R(aen1482)1193 0 R(aen1485)1194 0 R(aen1503)1195 0 R(aen1517)1196 0 R(aen153)1197 0 R(aen1539)1198 0 R(aen1555)1199 0 R(aen1571)1200 0 R(aen158)1201 0 R(aen1582)1202 0 R(aen1590)1203 0 R(aen1602)1204 0 R(aen1614)1205 0 R(aen1619)1206 0 R(aen1627)1207 0 R(aen1632)1208 0 R(aen1635)1209 0 R(aen1647)1210 0 R(aen1657)1211 0 R(aen1685)1212 0 R(aen169)1213 0 R(aen1693)1214 0 R(aen1710)1215 0 R(aen1717)1216 0 R(aen1722)1217 0 R(aen1727)1218 0 R(aen1748)1219 0 R(aen1752)1220 0 R(aen1763)1221 0 R(aen177)1222 0 R(aen1783)1223 0 R(aen1798)1224 0 R(aen1812)1225 0 R(aen1819)1226 0 R(aen1841)1227 0 R(aen1905)1228 0 R(aen1926)1229 0 R(aen1970)1230 0 R(aen1977)1231 0 R(aen1997)1232 0 R(aen2032)1233 0 R(aen2058)1234 0 R(aen2080)1235 0 R(aen2088)1236 0 R(aen21)1237 0 R(aen2123)1238 0 R(aen2139)1239 0 R(aen2150)1240 0 R(aen2180)1241 0 R(aen2188)1242 0 R(aen2192)1243 0 R(aen2202)1244 0 R(aen2205)1245 0 R(aen2209)1246 0 R(aen2231)1247 0 R(aen2233)1248 0 R(aen2249)1249 0 R(aen2258)1250 0 R(aen2266)1251 0 R(aen2294)1252 0 R(aen2305)1253 0 R(aen2317)1254 0 R(aen2320)1255 0 R(aen2323)1256 0 R(aen234)1257 0 R(aen2343)1258 0 R(aen2348)1259 0 R(aen2403)1260 0 R(aen241)1261 0 R(aen2442)1262 0 R(aen2449)1263 0 R(aen2519)1264 0 R(aen26)1265 0 R(aen2608)1266 0 R(aen2623)1267 0 R(aen267)1268 0 R(aen2685)1269 0 R(aen2689)1270 0 R(aen2702)1271 0 R(aen2709)1272 0 R(aen2713)1273 0 R(aen2718)1274 0 R(aen2722)1275 0 R(aen2725)1276 0 R(aen273)1277 0 R(aen2741)1278 0 R(aen2749)1279 0 R(aen2753)1280 0 R(aen2756)1281 0 R(aen2761)1282 0 R(aen2774)1283 0 R(aen2788)1284 0 R(aen279)1285 0 R(aen2799)1286 0 R(aen2818)1287 0 R(aen2851)1288 0 R(aen2867)1289 0 R(aen2878)1290 0 R(aen2918)1291 0 R(aen2920)1292 0 R(aen2940)1293 0 R(aen2950)1294 0 R(aen2956)1295 0 R(aen2973)1296 0 R(aen3006)1297 0 R(aen3013)1298 0 R(aen3023)1299 0 R(aen3033)1300 0 R(aen3038)1301 0 R(aen3046)1302 0 R(aen3055)1303 0 R(aen3060)1304 0 R(aen3095)1305 0 R(aen31)1306 0 R(aen310)1307 0 R(aen3114)1308 0 R(aen3132)1309 0 R(aen3142)1310 0 R(aen315)1311 0 R(aen3151)1312 0 R(aen3169)1313 0 R(aen3172)1314 0 R(aen318)1315 0 R(aen3190)1316 0 R(aen3199)1317 0 R(aen320)1318 0 R(aen3201)1319 0 R(aen3209)1320 0 R(aen3246)1321 0 R(aen3253)1322 0 R(aen3257)1323 0 R(aen3265)1324 0 R(aen3320)1325 0 R(aen3326)1326 0 R(aen3333)1327 0 R(aen3338)1328 0 R(aen3343)1329 0 R(aen3346)1330 0 R(aen3351)1331 0 R(aen3355)1332 0 R(aen3359)1333 0 R(aen3362)1334 0 R(aen340)1335 0 R(aen3410)1336 0 R(aen3420)1337 0 R(aen3443)1338 0 R(aen3447)1339 0 R(aen3450)1340 0 R(aen3453)1341 0 R(aen3458)1342 0 R(aen3539)1343 0 R(aen3542)1344 0 R(aen3549)1345 0 R(aen3558)1346 0 R(aen3565)1347 0 R(aen3574)1348 0 R(aen3588)1349 0 R(aen3597)1350 0 R(aen36)1351 0 R(aen3626)1352 0 R(aen3632)1353 0 R(aen3636)1354 0 R(aen3665)1355 0 R(aen3671)1356 0 R(aen3673)1357 0 R(aen369)1358 0 R(aen3691)1359 0 R(aen3700)1360 0 R(aen3702)1361 0 R(aen3717)1362 0 R(aen3726)1363 0 R(aen3730)1364 0 R(aen374)1365 0 R(aen3740)1366 0 R(aen3742)1367 0 R(aen3747)1368 0 R(aen3752)1369 0 R(aen3756)1370 0 R(aen3761)1371 0 R(aen3764)1372 0 R(aen3780)1373 0 R(aen3807)1374 0 R(aen3809)1375 0 R(aen3814)1376 0 R(aen3817)1377 0 R(aen3822)1378 0 R(aen3850)1379 0 R(aen3856)1380 0 R(aen386)1381 0 R(aen388)1382 0 R(aen3884)1383 0 R(aen3894)1384 0 R(aen3923)1385 0 R(aen3946)1386 0 R(aen3956)1387 0 R(aen3962)1388 0 R(aen3979)1389 0 R(aen3989)1390 0 R(aen3992)1391 0 R(aen4)1392 0 R(aen4015)1393 0 R(aen4020)1394 0 R(aen4030)1395 0 R(aen4032)1396 0 R(aen4038)1397 0 R(aen4044)1398 0 R(aen405)1399 0 R(aen4059)1400 0 R(aen4064)1401 0 R(aen4070)1402 0 R(aen4078)1403 0 R(aen4104)1404 0 R(aen4121)1405 0 R(aen4129)1406 0 R(aen4135)1407 0 R(aen4140)1408 0 R(aen433)1409 0 R(aen438)1410 0 R(aen458)1411 0 R(aen50)1412 0 R(aen528)1413 0 R(aen536)1414 0 R(aen538)1415 0 R(aen544)1416 0 R(aen554)1417 0 R(aen571)1418 0 R(aen576)1419 0 R(aen58)1420 0 R(aen584)1421 0 R(aen586)1422 0 R(aen592)1423 0 R(aen600)1424 0 R(aen629)1425 0 R(aen635)1426 0 R(aen64)1427 0 R(aen641)1428 0 R(aen644)1429 0 R(aen705)1430 0 R(aen710)1431 0 R(aen73)1432 0 R(aen748)1433 0 R(aen790)1434 0 R(aen8)1435 0 R(aen833)1436 0 R(aen874)1437 0 R(aen883)1438 0 R(aen89)1439 0 R(aen898)1440 0 R(aen946)1441 0 R(aen990)1442 0 R(appendixes)1443 0 R(browsing-quick)1444 0 R(bugreport)1445 0 R(compiling)1446 0 R(cups-printing)1447 0 R(diagnosis)1448 0 R(domain-security)1449 0 R(groupmapping)1450 0 R(groupprofiles)1451 0 R(improved-browsing)1452 0 R(install)1453 0 R(integrate-ms-networks)1454 0 R(introduction)1455 0 R(msdfs)1456 0 R(optional)1457 0 R(other-clients)1458 0 R(pam)1459 0 R(passdb)1460 0 R(portability)1461 0 R(printing)1462 0 R(samba-bdc)1463 0 R(samba-howto-collection)1464 0 R(samba-howto-collection.html)1465 0 R(samba-pdc)1466 0 R(securing-samba)1467 0 R(securitylevels)1468 0 R(servertype)1469 0 R(speed)1470 0 R(type)1471 0 R(unicode)1472 0 R(unix-permissions)1473 0 R(vfs)1474 0 R(winbind)1475 0 R]>>endobj
+1150 0 obj<</D[1615 0 R/XYZ 0 734 0]>>endobj
+1151 0 obj<</D[1617 0 R/XYZ 0 734 0]>>endobj
+1152 0 obj<</D[1503 0 R/XYZ 0 734 0]>>endobj
+1153 0 obj<</D[1791 0 R/XYZ 0 734 0]>>endobj
+1154 0 obj<</D[1505 0 R/XYZ 0 734 0]>>endobj
+1155 0 obj<</D[1549 0 R/XYZ 0 734 0]>>endobj
+1156 0 obj<</D[1551 0 R/XYZ 0 734 0]>>endobj
+1157 0 obj<</D[1603 0 R/XYZ 0 734 0]>>endobj
+1158 0 obj<</D[1513 0 R/XYZ 0 652 0]>>endobj
+1159 0 obj<</D[1513 0 R/XYZ 0 511 0]>>endobj
+1160 0 obj<</D[1581 0 R/XYZ 0 283 0]>>endobj
+1161 0 obj<</D[1513 0 R/XYZ 0 426 0]>>endobj
+1162 0 obj<</D[1583 0 R/XYZ 0 283 0]>>endobj
+1163 0 obj<</D[1585 0 R/XYZ 0 504 0]>>endobj
+1164 0 obj<</D[1585 0 R/XYZ 0 307 0]>>endobj
+1165 0 obj<</D[1585 0 R/XYZ 0 133 0]>>endobj
+1166 0 obj<</D[1587 0 R/XYZ 0 575 0]>>endobj
+1167 0 obj<</D[1587 0 R/XYZ 0 439 0]>>endobj
+1168 0 obj<</D[1591 0 R/XYZ 0 734 0]>>endobj
+1169 0 obj<</D[1591 0 R/XYZ 0 171 0]>>endobj
+1170 0 obj<</D[1593 0 R/XYZ 0 734 0]>>endobj
+1171 0 obj<</D[1593 0 R/XYZ 0 415 0]>>endobj
+1172 0 obj<</D[1597 0 R/XYZ 0 672 0]>>endobj
+1173 0 obj<</D[1597 0 R/XYZ 0 597 0]>>endobj
+1174 0 obj<</D[1597 0 R/XYZ 0 225 0]>>endobj
+1175 0 obj<</D[1599 0 R/XYZ 0 734 0]>>endobj
+1176 0 obj<</D[1599 0 R/XYZ 0 609 0]>>endobj
+1177 0 obj<</D[1599 0 R/XYZ 0 524 0]>>endobj
+1178 0 obj<</D[1517 0 R/XYZ 0 565 0]>>endobj
+1179 0 obj<</D[1599 0 R/XYZ 0 323 0]>>endobj
+1180 0 obj<</D[1601 0 R/XYZ 0 541 0]>>endobj
+1181 0 obj<</D[1601 0 R/XYZ 0 390 0]>>endobj
+1182 0 obj<</D[1603 0 R/XYZ 0 551 0]>>endobj
+1183 0 obj<</D[1603 0 R/XYZ 0 444 0]>>endobj
+1184 0 obj<</D[1603 0 R/XYZ 0 267 0]>>endobj
+1185 0 obj<</D[1605 0 R/XYZ 0 580 0]>>endobj
+1186 0 obj<</D[1605 0 R/XYZ 0 264 0]>>endobj
+1187 0 obj<</D[1605 0 R/XYZ 0 202 0]>>endobj
+1188 0 obj<</D[1519 0 R/XYZ 0 734 0]>>endobj
+1189 0 obj<</D[1607 0 R/XYZ 0 734 0]>>endobj
+1190 0 obj<</D[1607 0 R/XYZ 0 645 0]>>endobj
+1191 0 obj<</D[1607 0 R/XYZ 0 570 0]>>endobj
+1192 0 obj<</D[1609 0 R/XYZ 0 672 0]>>endobj
+1193 0 obj<</D[1611 0 R/XYZ 0 494 0]>>endobj
+1194 0 obj<</D[1611 0 R/XYZ 0 405 0]>>endobj
+1195 0 obj<</D[1615 0 R/XYZ 0 696 0]>>endobj
+1196 0 obj<</D[1623 0 R/XYZ 0 672 0]>>endobj
+1197 0 obj<</D[1519 0 R/XYZ 0 412 0]>>endobj
+1198 0 obj<</D[1623 0 R/XYZ 0 439 0]>>endobj
+1199 0 obj<</D[1623 0 R/XYZ 0 311 0]>>endobj
+1200 0 obj<</D[1625 0 R/XYZ 0 441 0]>>endobj
+1201 0 obj<</D[1519 0 R/XYZ 0 234 0]>>endobj
+1202 0 obj<</D[1625 0 R/XYZ 0 303 0]>>endobj
+1203 0 obj<</D[1625 0 R/XYZ 0 157 0]>>endobj
+1204 0 obj<</D[1627 0 R/XYZ 0 339 0]>>endobj
+1205 0 obj<</D[1629 0 R/XYZ 0 266 0]>>endobj
+1206 0 obj<</D[1631 0 R/XYZ 0 734 0]>>endobj
+1207 0 obj<</D[1633 0 R/XYZ 0 459 0]>>endobj
+1208 0 obj<</D[1633 0 R/XYZ 0 361 0]>>endobj
+1209 0 obj<</D[1633 0 R/XYZ 0 224 0]>>endobj
+1210 0 obj<</D[1635 0 R/XYZ 0 670 0]>>endobj
+1211 0 obj<</D[1635 0 R/XYZ 0 126 0]>>endobj
+1212 0 obj<</D[1639 0 R/XYZ 0 734 0]>>endobj
+1213 0 obj<</D[1521 0 R/XYZ 0 388 0]>>endobj
+1214 0 obj<</D[1639 0 R/XYZ 0 484 0]>>endobj
+1215 0 obj<</D[1639 0 R/XYZ 0 132 0]>>endobj
+1216 0 obj<</D[1641 0 R/XYZ 0 523 0]>>endobj
+1217 0 obj<</D[1641 0 R/XYZ 0 377 0]>>endobj
+1218 0 obj<</D[1641 0 R/XYZ 0 263 0]>>endobj
+1219 0 obj<</D[1643 0 R/XYZ 0 672 0]>>endobj
+1220 0 obj<</D[1643 0 R/XYZ 0 537 0]>>endobj
+1221 0 obj<</D[1643 0 R/XYZ 0 369 0]>>endobj
+1222 0 obj<</D[1523 0 R/XYZ 0 705 0]>>endobj
+1223 0 obj<</D[1645 0 R/XYZ 0 705 0]>>endobj
+1224 0 obj<</D[1645 0 R/XYZ 0 471 0]>>endobj
+1225 0 obj<</D[1645 0 R/XYZ 0 228 0]>>endobj
+1226 0 obj<</D[1647 0 R/XYZ 0 718 0]>>endobj
+1227 0 obj<</D[1647 0 R/XYZ 0 287 0]>>endobj
+1228 0 obj<</D[1651 0 R/XYZ 0 652 0]>>endobj
+1229 0 obj<</D[1653 0 R/XYZ 0 672 0]>>endobj
+1230 0 obj<</D[1655 0 R/XYZ 0 148 0]>>endobj
+1231 0 obj<</D[1657 0 R/XYZ 0 705 0]>>endobj
+1232 0 obj<</D[1659 0 R/XYZ 0 672 0]>>endobj
+1233 0 obj<</D[1661 0 R/XYZ 0 652 0]>>endobj
+1234 0 obj<</D[1663 0 R/XYZ 0 696 0]>>endobj
+1235 0 obj<</D[1663 0 R/XYZ 0 317 0]>>endobj
+1236 0 obj<</D[1663 0 R/XYZ 0 127 0]>>endobj
+1237 0 obj<</D[1503 0 R/XYZ 0 696 0]>>endobj
+1238 0 obj<</D[1667 0 R/XYZ 0 531 0]>>endobj
+1239 0 obj<</D[1669 0 R/XYZ 0 734 0]>>endobj
+1240 0 obj<</D[1669 0 R/XYZ 0 363 0]>>endobj
+1241 0 obj<</D[1671 0 R/XYZ 0 184 0]>>endobj
+1242 0 obj<</D[1673 0 R/XYZ 0 692 0]>>endobj
+1243 0 obj<</D[1673 0 R/XYZ 0 590 0]>>endobj
+1244 0 obj<</D[1673 0 R/XYZ 0 466 0]>>endobj
+1245 0 obj<</D[1673 0 R/XYZ 0 381 0]>>endobj
+1246 0 obj<</D[1673 0 R/XYZ 0 283 0]>>endobj
+1247 0 obj<</D[1675 0 R/XYZ 0 397 0]>>endobj
+1248 0 obj<</D[1675 0 R/XYZ 0 363 0]>>endobj
+1249 0 obj<</D[1677 0 R/XYZ 0 429 0]>>endobj
+1250 0 obj<</D[1679 0 R/XYZ 0 665 0]>>endobj
+1251 0 obj<</D[1679 0 R/XYZ 0 485 0]>>endobj
+1252 0 obj<</D[1681 0 R/XYZ 0 734 0]>>endobj
+1253 0 obj<</D[1681 0 R/XYZ 0 394 0]>>endobj
+1254 0 obj<</D[1683 0 R/XYZ 0 718 0]>>endobj
+1255 0 obj<</D[1683 0 R/XYZ 0 633 0]>>endobj
+1256 0 obj<</D[1683 0 R/XYZ 0 535 0]>>endobj
+1257 0 obj<</D[1525 0 R/XYZ 0 696 0]>>endobj
+1258 0 obj<</D[1685 0 R/XYZ 0 696 0]>>endobj
+1259 0 obj<</D[1685 0 R/XYZ 0 463 0]>>endobj
+1260 0 obj<</D[1689 0 R/XYZ 0 276 0]>>endobj
+1261 0 obj<</D[1525 0 R/XYZ 0 449 0]>>endobj
+1262 0 obj<</D[1701 0 R/XYZ 0 546 0]>>endobj
+1263 0 obj<</D[1701 0 R/XYZ 0 404 0]>>endobj
+1264 0 obj<</D[1705 0 R/XYZ 0 177 0]>>endobj
+1265 0 obj<</D[1509 0 R/XYZ 0 696 0]>>endobj
+1266 0 obj<</D[1713 0 R/XYZ 0 362 0]>>endobj
+1267 0 obj<</D[1715 0 R/XYZ 0 527 0]>>endobj
+1268 0 obj<</D[1527 0 R/XYZ 0 402 0]>>endobj
+1269 0 obj<</D[1719 0 R/XYZ 0 672 0]>>endobj
+1270 0 obj<</D[1719 0 R/XYZ 0 544 0]>>endobj
+1271 0 obj<</D[1719 0 R/XYZ 0 231 0]>>endobj
+1272 0 obj<</D[1721 0 R/XYZ 0 560 0]>>endobj
+1273 0 obj<</D[1721 0 R/XYZ 0 409 0]>>endobj
+1274 0 obj<</D[1721 0 R/XYZ 0 294 0]>>endobj
+1275 0 obj<</D[1723 0 R/XYZ 0 734 0]>>endobj
+1276 0 obj<</D[1723 0 R/XYZ 0 635 0]>>endobj
+1277 0 obj<</D[1527 0 R/XYZ 0 269 0]>>endobj
+1278 0 obj<</D[1723 0 R/XYZ 0 194 0]>>endobj
+1279 0 obj<</D[1725 0 R/XYZ 0 560 0]>>endobj
+1280 0 obj<</D[1725 0 R/XYZ 0 383 0]>>endobj
+1281 0 obj<</D[1725 0 R/XYZ 0 245 0]>>endobj
+1282 0 obj<</D[1725 0 R/XYZ 0 143 0]>>endobj
+1283 0 obj<</D[1727 0 R/XYZ 0 533 0]>>endobj
+1284 0 obj<</D[1727 0 R/XYZ 0 264 0]>>endobj
+1285 0 obj<</D[1527 0 R/XYZ 0 163 0]>>endobj
+1286 0 obj<</D[1727 0 R/XYZ 0 126 0]>>endobj
+1287 0 obj<</D[1729 0 R/XYZ 0 614 0]>>endobj
+1288 0 obj<</D[1729 0 R/XYZ 0 210 0]>>endobj
+1289 0 obj<</D[1731 0 R/XYZ 0 632 0]>>endobj
+1290 0 obj<</D[1731 0 R/XYZ 0 485 0]>>endobj
+1291 0 obj<</D[1733 0 R/XYZ 0 353 0]>>endobj
+1292 0 obj<</D[1733 0 R/XYZ 0 327 0]>>endobj
+1293 0 obj<</D[1735 0 R/XYZ 0 292 0]>>endobj
+1294 0 obj<</D[1737 0 R/XYZ 0 272 0]>>endobj
+1295 0 obj<</D[1737 0 R/XYZ 0 206 0]>>endobj
+1296 0 obj<</D[1739 0 R/XYZ 0 652 0]>>endobj
+1297 0 obj<</D[1741 0 R/XYZ 0 692 0]>>endobj
+1298 0 obj<</D[1743 0 R/XYZ 0 555 0]>>endobj
+1299 0 obj<</D[1743 0 R/XYZ 0 335 0]>>endobj
+1300 0 obj<</D[1745 0 R/XYZ 0 696 0]>>endobj
+1301 0 obj<</D[1745 0 R/XYZ 0 463 0]>>endobj
+1302 0 obj<</D[1747 0 R/XYZ 0 734 0]>>endobj
+1303 0 obj<</D[1747 0 R/XYZ 0 381 0]>>endobj
+1304 0 obj<</D[1749 0 R/XYZ 0 734 0]>>endobj
+1305 0 obj<</D[1753 0 R/XYZ 0 332 0]>>endobj
+1306 0 obj<</D[1509 0 R/XYZ 0 595 0]>>endobj
+1307 0 obj<</D[1529 0 R/XYZ 0 362 0]>>endobj
+1308 0 obj<</D[1755 0 R/XYZ 0 388 0]>>endobj
+1309 0 obj<</D[1757 0 R/XYZ 0 407 0]>>endobj
+1310 0 obj<</D[1759 0 R/XYZ 0 718 0]>>endobj
+1311 0 obj<</D[1529 0 R/XYZ 0 273 0]>>endobj
+1312 0 obj<</D[1759 0 R/XYZ 0 300 0]>>endobj
+1313 0 obj<</D[1761 0 R/XYZ 0 520 0]>>endobj
+1314 0 obj<</D[1761 0 R/XYZ 0 432 0]>>endobj
+1315 0 obj<</D[1529 0 R/XYZ 0 198 0]>>endobj
+1316 0 obj<</D[1763 0 R/XYZ 0 696 0]>>endobj
+1317 0 obj<</D[1763 0 R/XYZ 0 385 0]>>endobj
+1318 0 obj<</D[1529 0 R/XYZ 0 165 0]>>endobj
+1319 0 obj<</D[1763 0 R/XYZ 0 351 0]>>endobj
+1320 0 obj<</D[1763 0 R/XYZ 0 215 0]>>endobj
+1321 0 obj<</D[1765 0 R/XYZ 0 560 0]>>endobj
+1322 0 obj<</D[1765 0 R/XYZ 0 430 0]>>endobj
+1323 0 obj<</D[1765 0 R/XYZ 0 315 0]>>endobj
+1324 0 obj<</D[1767 0 R/XYZ 0 734 0]>>endobj
+1325 0 obj<</D[1771 0 R/XYZ 0 696 0]>>endobj
+1326 0 obj<</D[1771 0 R/XYZ 0 449 0]>>endobj
+1327 0 obj<</D[1771 0 R/XYZ 0 189 0]>>endobj
+1328 0 obj<</D[1773 0 R/XYZ 0 639 0]>>endobj
+1329 0 obj<</D[1773 0 R/XYZ 0 458 0]>>endobj
+1330 0 obj<</D[1773 0 R/XYZ 0 383 0]>>endobj
+1331 0 obj<</D[1773 0 R/XYZ 0 215 0]>>endobj
+1332 0 obj<</D[1775 0 R/XYZ 0 734 0]>>endobj
+1333 0 obj<</D[1775 0 R/XYZ 0 605 0]>>endobj
+1334 0 obj<</D[1775 0 R/XYZ 0 530 0]>>endobj
+1335 0 obj<</D[1531 0 R/XYZ 0 573 0]>>endobj
+1336 0 obj<</D[1779 0 R/XYZ 0 696 0]>>endobj
+1337 0 obj<</D[1779 0 R/XYZ 0 423 0]>>endobj
+1338 0 obj<</D[1781 0 R/XYZ 0 734 0]>>endobj
+1339 0 obj<</D[1781 0 R/XYZ 0 635 0]>>endobj
+1340 0 obj<</D[1781 0 R/XYZ 0 564 0]>>endobj
+1341 0 obj<</D[1781 0 R/XYZ 0 492 0]>>endobj
+1342 0 obj<</D[1781 0 R/XYZ 0 328 0]>>endobj
+1343 0 obj<</D[1785 0 R/XYZ 0 696 0]>>endobj
+1344 0 obj<</D[1785 0 R/XYZ 0 621 0]>>endobj
+1345 0 obj<</D[1785 0 R/XYZ 0 405 0]>>endobj
+1346 0 obj<</D[1785 0 R/XYZ 0 150 0]>>endobj
+1347 0 obj<</D[1787 0 R/XYZ 0 596 0]>>endobj
+1348 0 obj<</D[1787 0 R/XYZ 0 290 0]>>endobj
+1349 0 obj<</D[1789 0 R/XYZ 0 696 0]>>endobj
+1350 0 obj<</D[1789 0 R/XYZ 0 397 0]>>endobj
+1351 0 obj<</D[1509 0 R/XYZ 0 506 0]>>endobj
+1352 0 obj<</D[1795 0 R/XYZ 0 655 0]>>endobj
+1353 0 obj<</D[1795 0 R/XYZ 0 408 0]>>endobj
+1354 0 obj<</D[1795 0 R/XYZ 0 293 0]>>endobj
+1355 0 obj<</D[1797 0 R/XYZ 0 228 0]>>endobj
+1356 0 obj<</D[1799 0 R/XYZ 0 734 0]>>endobj
+1357 0 obj<</D[1799 0 R/XYZ 0 700 0]>>endobj
+1358 0 obj<</D[1533 0 R/XYZ 0 734 0]>>endobj
+1359 0 obj<</D[1801 0 R/XYZ 0 668 0]>>endobj
+1360 0 obj<</D[1801 0 R/XYZ 0 461 0]>>endobj
+1361 0 obj<</D[1801 0 R/XYZ 0 427 0]>>endobj
+1362 0 obj<</D[1803 0 R/XYZ 0 734 0]>>endobj
+1363 0 obj<</D[1803 0 R/XYZ 0 523 0]>>endobj
+1364 0 obj<</D[1803 0 R/XYZ 0 408 0]>>endobj
+1365 0 obj<</D[1533 0 R/XYZ 0 622 0]>>endobj
+1366 0 obj<</D[1803 0 R/XYZ 0 151 0]>>endobj
+1367 0 obj<</D[1803 0 R/XYZ 0 118 0]>>endobj
+1368 0 obj<</D[1805 0 R/XYZ 0 626 0]>>endobj
+1369 0 obj<</D[1805 0 R/XYZ 0 475 0]>>endobj
+1370 0 obj<</D[1805 0 R/XYZ 0 377 0]>>endobj
+1371 0 obj<</D[1805 0 R/XYZ 0 292 0]>>endobj
+1372 0 obj<</D[1805 0 R/XYZ 0 207 0]>>endobj
+1373 0 obj<</D[1807 0 R/XYZ 0 626 0]>>endobj
+1374 0 obj<</D[1809 0 R/XYZ 0 655 0]>>endobj
+1375 0 obj<</D[1809 0 R/XYZ 0 621 0]>>endobj
+1376 0 obj<</D[1809 0 R/XYZ 0 510 0]>>endobj
+1377 0 obj<</D[1809 0 R/XYZ 0 425 0]>>endobj
+1378 0 obj<</D[1809 0 R/XYZ 0 317 0]>>endobj
+1379 0 obj<</D[1811 0 R/XYZ 0 494 0]>>endobj
+1380 0 obj<</D[1811 0 R/XYZ 0 353 0]>>endobj
+1381 0 obj<</D[1533 0 R/XYZ 0 251 0]>>endobj
+1382 0 obj<</D[1533 0 R/XYZ 0 221 0]>>endobj
+1383 0 obj<</D[1813 0 R/XYZ 0 613 0]>>endobj
+1384 0 obj<</D[1813 0 R/XYZ 0 458 0]>>endobj
+1385 0 obj<</D[1815 0 R/XYZ 0 639 0]>>endobj
+1386 0 obj<</D[1817 0 R/XYZ 0 696 0]>>endobj
+1387 0 obj<</D[1817 0 R/XYZ 0 423 0]>>endobj
+1388 0 obj<</D[1817 0 R/XYZ 0 282 0]>>endobj
+1389 0 obj<</D[1819 0 R/XYZ 0 613 0]>>endobj
+1390 0 obj<</D[1819 0 R/XYZ 0 260 0]>>endobj
+1391 0 obj<</D[1819 0 R/XYZ 0 159 0]>>endobj
+1392 0 obj<</D[1493 0 R/XYZ 0 696 0]>>endobj
+1393 0 obj<</D[1821 0 R/XYZ 0 696 0]>>endobj
+1394 0 obj<</D[1821 0 R/XYZ 0 529 0]>>endobj
+1395 0 obj<</D[1821 0 R/XYZ 0 199 0]>>endobj
+1396 0 obj<</D[1821 0 R/XYZ 0 165 0]>>endobj
+1397 0 obj<</D[1823 0 R/XYZ 0 734 0]>>endobj
+1398 0 obj<</D[1823 0 R/XYZ 0 530 0]>>endobj
+1399 0 obj<</D[1535 0 R/XYZ 0 339 0]>>endobj
+1400 0 obj<</D[1825 0 R/XYZ 0 626 0]>>endobj
+1401 0 obj<</D[1825 0 R/XYZ 0 475 0]>>endobj
+1402 0 obj<</D[1825 0 R/XYZ 0 351 0]>>endobj
+1403 0 obj<</D[1827 0 R/XYZ 0 734 0]>>endobj
+1404 0 obj<</D[1827 0 R/XYZ 0 371 0]>>endobj
+1405 0 obj<</D[1829 0 R/XYZ 0 705 0]>>endobj
+1406 0 obj<</D[1829 0 R/XYZ 0 515 0]>>endobj
+1407 0 obj<</D[1829 0 R/XYZ 0 377 0]>>endobj
+1408 0 obj<</D[1829 0 R/XYZ 0 239 0]>>endobj
+1409 0 obj<</D[1537 0 R/XYZ 0 438 0]>>endobj
+1410 0 obj<</D[1537 0 R/XYZ 0 247 0]>>endobj
+1411 0 obj<</D[1539 0 R/XYZ 0 543 0]>>endobj
+1412 0 obj<</D[1509 0 R/XYZ 0 161 0]>>endobj
+1413 0 obj<</D[1541 0 R/XYZ 0 533 0]>>endobj
+1414 0 obj<</D[1543 0 R/XYZ 0 708 0]>>endobj
+1415 0 obj<</D[1543 0 R/XYZ 0 674 0]>>endobj
+1416 0 obj<</D[1543 0 R/XYZ 0 576 0]>>endobj
+1417 0 obj<</D[1543 0 R/XYZ 0 478 0]>>endobj
+1418 0 obj<</D[1545 0 R/XYZ 0 417 0]>>endobj
+1419 0 obj<</D[1545 0 R/XYZ 0 266 0]>>endobj
+1420 0 obj<</D[1511 0 R/XYZ 0 705 0]>>endobj
+1421 0 obj<</D[1545 0 R/XYZ 0 129 0]>>endobj
+1422 0 obj<</D[1547 0 R/XYZ 0 734 0]>>endobj
+1423 0 obj<</D[1547 0 R/XYZ 0 649 0]>>endobj
+1424 0 obj<</D[1549 0 R/XYZ 0 696 0]>>endobj
+1425 0 obj<</D[1555 0 R/XYZ 0 523 0]>>endobj
+1426 0 obj<</D[1555 0 R/XYZ 0 249 0]>>endobj
+1427 0 obj<</D[1511 0 R/XYZ 0 528 0]>>endobj
+1428 0 obj<</D[1557 0 R/XYZ 0 679 0]>>endobj
+1429 0 obj<</D[1557 0 R/XYZ 0 590 0]>>endobj
+1430 0 obj<</D[1563 0 R/XYZ 0 672 0]>>endobj
+1431 0 obj<</D[1563 0 R/XYZ 0 584 0]>>endobj
+1432 0 obj<</D[1511 0 R/XYZ 0 360 0]>>endobj
+1433 0 obj<</D[1565 0 R/XYZ 0 734 0]>>endobj
+1434 0 obj<</D[1567 0 R/XYZ 0 665 0]>>endobj
+1435 0 obj<</D[1495 0 R/XYZ 0 734 0]>>endobj
+1436 0 obj<</D[1569 0 R/XYZ 0 665 0]>>endobj
+1437 0 obj<</D[1571 0 R/XYZ 0 734 0]>>endobj
+1438 0 obj<</D[1571 0 R/XYZ 0 524 0]>>endobj
+1439 0 obj<</D[1511 0 R/XYZ 0 193 0]>>endobj
+1440 0 obj<</D[1571 0 R/XYZ 0 175 0]>>endobj
+1441 0 obj<</D[1575 0 R/XYZ 0 565 0]>>endobj
+1442 0 obj<</D[1577 0 R/XYZ 0 560 0]>>endobj
+1443 0 obj<</D[1789 0 R/XYZ 0 178 0]>>endobj
+1444 0 obj<</D[1517 0 R/XYZ 0 734 0]>>endobj
+1445 0 obj<</D[1817 0 R/XYZ 0 734 0]>>endobj
+1446 0 obj<</D[1809 0 R/XYZ 0 734 0]>>endobj
+1447 0 obj<</D[1685 0 R/XYZ 0 734 0]>>endobj
+1448 0 obj<</D[1821 0 R/XYZ 0 734 0]>>endobj
+1449 0 obj<</D[1609 0 R/XYZ 0 734 0]>>endobj
+1450 0 obj<</D[1769 0 R/XYZ 0 734 0]>>endobj
+1451 0 obj<</D[1779 0 R/XYZ 0 734 0]>>endobj
+1452 0 obj<</D[1745 0 R/XYZ 0 734 0]>>endobj
+1453 0 obj<</D[1509 0 R/XYZ 0 734 0]>>endobj
+1454 0 obj<</D[1623 0 R/XYZ 0 734 0]>>endobj
+1455 0 obj<</D[1501 0 R/XYZ 0 205 0]>>endobj
+1456 0 obj<</D[1659 0 R/XYZ 0 734 0]>>endobj
+1457 0 obj<</D[1613 0 R/XYZ 0 641 0]>>endobj
+1458 0 obj<</D[1801 0 R/XYZ 0 734 0]>>endobj
+1459 0 obj<</D[1653 0 R/XYZ 0 734 0]>>endobj
+1460 0 obj<</D[1525 0 R/XYZ 0 734 0]>>endobj
+1461 0 obj<</D[1795 0 R/XYZ 0 734 0]>>endobj
+1462 0 obj<</D[1663 0 R/XYZ 0 734 0]>>endobj
+1463 0 obj<</D[1597 0 R/XYZ 0 734 0]>>endobj
+1464 0 obj<</D[1493 0 R/XYZ 0 734 0]>>endobj
+1465 0 obj<</D[1493 0 R/XYZ 0 734 0]>>endobj
+1466 0 obj<</D[1563 0 R/XYZ 0 734 0]>>endobj
+1467 0 obj<</D[1785 0 R/XYZ 0 734 0]>>endobj
+1468 0 obj<</D[1559 0 R/XYZ 0 734 0]>>endobj
+1469 0 obj<</D[1555 0 R/XYZ 0 734 0]>>endobj
+1470 0 obj<</D[1771 0 R/XYZ 0 734 0]>>endobj
+1471 0 obj<</D[1547 0 R/XYZ 0 539 0]>>endobj
+1472 0 obj<</D[1789 0 R/XYZ 0 734 0]>>endobj
+1473 0 obj<</D[1643 0 R/XYZ 0 734 0]>>endobj
+1474 0 obj<</D[1763 0 R/XYZ 0 734 0]>>endobj
+1475 0 obj<</D[1719 0 R/XYZ 0 734 0]>>endobj
+1476 0 obj<</Type/Pages/Count 177/Kids[1477 0 R
+1479 0 R
+1481 0 R
+1483 0 R
+1485 0 R
+1487 0 R
+1489 0 R
+1491 0 R
+1493 0 R
+1495 0 R
+1497 0 R
+1499 0 R
+1501 0 R
+1503 0 R
+1505 0 R
+1507 0 R
+1509 0 R
+1511 0 R
+1513 0 R
+1515 0 R
+1517 0 R
+1519 0 R
+1521 0 R
+1523 0 R
+1525 0 R
+1527 0 R
+1529 0 R
+1531 0 R
+1533 0 R
+1535 0 R
+1537 0 R
+1539 0 R
+1541 0 R
+1543 0 R
+1545 0 R
+1547 0 R
+1549 0 R
+1551 0 R
+1553 0 R
+1555 0 R
+1557 0 R
+1559 0 R
+1561 0 R
+1563 0 R
+1565 0 R
+1567 0 R
+1569 0 R
+1571 0 R
+1573 0 R
+1575 0 R
+1577 0 R
+1579 0 R
+1581 0 R
+1583 0 R
+1585 0 R
+1587 0 R
+1589 0 R
+1591 0 R
+1593 0 R
+1595 0 R
+1597 0 R
+1599 0 R
+1601 0 R
+1603 0 R
+1605 0 R
+1607 0 R
+1609 0 R
+1611 0 R
+1613 0 R
+1615 0 R
+1617 0 R
+1619 0 R
+1621 0 R
+1623 0 R
+1625 0 R
+1627 0 R
+1629 0 R
+1631 0 R
+1633 0 R
+1635 0 R
+1637 0 R
+1639 0 R
+1641 0 R
+1643 0 R
+1645 0 R
+1647 0 R
+1649 0 R
+1651 0 R
+1653 0 R
+1655 0 R
+1657 0 R
+1659 0 R
+1661 0 R
+1663 0 R
+1665 0 R
+1667 0 R
+1669 0 R
+1671 0 R
+1673 0 R
+1675 0 R
+1677 0 R
+1679 0 R
+1681 0 R
+1683 0 R
+1685 0 R
+1687 0 R
+1689 0 R
+1691 0 R
+1693 0 R
+1695 0 R
+1697 0 R
+1699 0 R
+1701 0 R
+1703 0 R
+1705 0 R
+1707 0 R
+1709 0 R
+1711 0 R
+1713 0 R
+1715 0 R
+1717 0 R
+1719 0 R
+1721 0 R
+1723 0 R
+1725 0 R
+1727 0 R
+1729 0 R
+1731 0 R
+1733 0 R
+1735 0 R
+1737 0 R
+1739 0 R
+1741 0 R
+1743 0 R
+1745 0 R
+1747 0 R
+1749 0 R
+1751 0 R
+1753 0 R
+1755 0 R
+1757 0 R
+1759 0 R
+1761 0 R
+1763 0 R
+1765 0 R
+1767 0 R
+1769 0 R
+1771 0 R
+1773 0 R
+1775 0 R
+1777 0 R
+1779 0 R
+1781 0 R
+1783 0 R
+1785 0 R
+1787 0 R
+1789 0 R
+1791 0 R
+1793 0 R
+1795 0 R
+1797 0 R
+1799 0 R
+1801 0 R
+1803 0 R
+1805 0 R
+1807 0 R
+1809 0 R
+1811 0 R
+1813 0 R
+1815 0 R
+1817 0 R
+1819 0 R
+1821 0 R
+1823 0 R
+1825 0 R
+1827 0 R
+1829 0 R
+]>>endobj
+1477 0 obj<</Type/Page/Parent 1476 0 R/Contents 1478 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+1478 0 obj<</Filter/FlateDecode/Length 94 >>stream
+x+2T0
+
+endobj
+1479 0 obj<</Type/Page/Parent 1476 0 R/Contents 1480 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F5 7 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>/Annots 59 0 R>>endobj
+1480 0 obj<</Filter/FlateDecode/Length 3822 >>stream
+x[rG}WLe==WiKl|'EYI_~n4Co[Ttx4@c&}JG //*F2GE2~d2g2q”v`E`Ir<I 4Œ ɤ£AqEJGT9YZaP )1 ht$yTXa.LQ0J* @]:e2`1`a(Z "{e 7lNT:&ThUJd4qf:g,$} k0Qm"D<]I1-")[x i @c`$-ii k0: k0Xng=]d`Es<PMTT&H(p#aA4BH:,Ib/+ g
+-=sBy't`lYG` 91rB,!@ITZ Jig"k0XU58-erwATs"r2JzeHWT5cKLD`RMYiug
+@` vTX~)Z 6A' vVP,Pf`+:nqf>y9' 8a0-?I ,JvyA2m[6r~Tb#="k.J{0g+} DU<'+g`PE9Q+iYQ%1E`r`qd4s 30((9G%wTD%g\5DF)D@8F5,|3`(|Jk0XV`awX$-*Je1/JX"wZD}j!Y@2"8b=rRD`>"G#r OB $iF- +U3
+h+b=,P"tXY'pqb cEAIU~l(-B0Z}$J"q RR(xIFJ"K
+%1B=K"DX98> y!j0NdNw:2shD!I*m
+:PP]r'd7.8?dd 8sZcKI"-<0@d ;Z'"-2&Ue"GBO`("`8,k13[ Qk0tv#@&h!<CS D!DN !B! 7y
+G):\,.B @ *gX oD.B,}GO)y14zGu18+e iMjy%Mi BF9Ni[gCb!#Bq141t\
+b?NX8y;'kLmoIgg7"x6_E D~?gO?W\bi;Na\M,rP=6xCv]o&lrYN9~O+/Fuv0Y/
+)G{T_~7~bBSGKgv;|5c5y<]_6@h'Oh^tmOKqq"wg_'yp9-dJmc{Pu2Lw%41Jg#U^AV"h}-|8JxP !/^7f9%#[
+(l^A D7Yp{f& Xdu}W$godd$: zo_um]WN:h pLZB}p{x4FNe+??~' zni MX~FP\ `Se3EQ!5{ v4Qu^2>O]u?Z!%8JM%!q^v]`T9o;E RvI}U~uQ/MU~U~nF_h=;¤5>Jk;t> -_E^//>C(p5 ^x _?swZ
+endobj
+1481 0 obj<</Type/Page/Parent 1476 0 R/Contents 1482 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F5 7 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>/Annots 102 0 R>>endobj
+1482 0 obj<</Filter/FlateDecode/Length 4352 >>stream
+x[]o[}C<$RJlR>((C!8=gvwf.Imi 8<<;W?)/~Um6?{9oyV {E;_n1;mT `G
+rRd#@60rE1Y\m0WJ0V=4rZ%e`3lq`
+7R}:8\ ss <H>"`C s
+ sj8F
+tK\oOyD CUE1!
+N4Ul;arlXXaXi+bIXj?aCqë0,)¯hßÊzL;cu`i}
+EbYT"s3:c.I` Lb) &E\Jznu\.c =ix63a0TA.)1Xb`*6aZgNQ68[P9n!^I1m.`@?cxM(s!
+Ygy0=RPP:3Sg=*XvYq9
+(
+`qx=@Mf8qIettf3KhS1;
+r(;)v^lV
+?,HT u
+^]kc*57H.6p5Sp7.<OVhR4Y/UuJ^"J.Zu&NDyVa*]NFz.G:?Ap?N=Z-oC.kJ5e
+\Ngty^;G!C\Hoz2FQ~k:1^]2 ^_aB\.').4~ {7>+y=2(%=\7|A!;ym_s3A% hB#jwwcp}zA_Njy\yE%Z/}mr+r4OwRW#pQ'BoLtwco_gom-6Lvu2gbxSLN7WuVQttko
+z
+FHcWwu>LNuL;‰×˜Íímq¸¾æU6YFS;dv]Cp{p>G `!-Jwukz*m2g*{B*JAU\_O%'JvE-8h=],C3/Q;$G@-\BvbAbm< h
+/mB^X ptjb'c#Buj~&V;>Eaa@ {\zlGyyI5,Tjrc(}}k4u
+endobj
+1483 0 obj<</Type/Page/Parent 1476 0 R/Contents 1484 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F5 7 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>/Annots 146 0 R>>endobj
+1484 0 obj<</Filter/FlateDecode/Length 4279 >>stream
+x[vG+zYHfs1hdbe2[-"[#N~.PUmtz
+]%v*$cNe,8-aFLgtÙÒieøt#׊c¨Œ#㕍íAE I`Kq Wr.KNt-c8gU)**=q }v
+OJf#qA j"w% 3jKXLzG 3}m;[$C\h7ch;.rphgAQlC'6)c!%,
+-H,ab3cM.
+q</
+@
+W`M\>dP}S%,o$0X#0&<()a4 >)b hC )t6 Z(>A_U=nPF.G~U31`6tD7Vw¹Ë ÝÉXTT+jl@tvEqdN2lmMXb(Gg`g``Dm c EOx_b /\Y`qzV#L._iUGP'71XD,XYg +ng Cy!j21,-a x3aLX`X"`5U
+9$mh8JC$7 \2n-d`Cdx/ZVMF5[-J!:8UR(]ZhRPsDdçª)ˆ´Œsg$¢NBz fo4kWy6 |'hvVHL#trU#4 ty5bU .H<yZ!oa9]38)c|y&RS72/pD  *P XmETVNl\a__-kI"wsU"ItAm{y>ZLd 9CJ(J~~t3P+[hÛ¾]ˆÔqYOl>kVoww`\tf ;H$c}6v> 7$yMsu+38S?VLRw#9[C:-3qd wf~?z=ZQT'y6kw9Pcun_q"E27N$|8`]w`1Yp=fy5]g)i0 55~%5Z,Fu0Td ^]V%2mN?%S/ql(* 7:+! R`bs,=:QFfA9? 9*65 :>JCJ\x5lQNgAV%!+OEFqw#bo~}:[j']:7!`|m8”ÖŽííMGf>[ iG;i+#M~ZO4Eypz..Vf(iI2 ow0\m2!n,jw4 ePT0 ]y bJ. $*my/ °´i³Õ|û~X y~|xCf?.\?y;_]BoRY j ñæ$Ovgv/<|S%iw[>Qf77jW S$(P;GX2 PByQ
+YE6:td:b- u
+W . t<xZm\<-iN~ EQEw, _<29o;&$j{1zXPPiUQ bXj}zofG,t!|,sbcEid|TG^M"7w6Fp_EhL!,^92zW  . B/]{"w\MU LAF6Km$
+#-M-tj\6x[in]*se5 F|]nrM
+%=V*O:#z~üû õœà,¨žóë‹ÿIOz=\pL=]X*.JY|=~ww:v9d6?p Ad~\_ \ulhU<3mQ7H:}XLo:]V^IZ;&H
+endobj
+1485 0 obj<</Type/Page/Parent 1476 0 R/Contents 1486 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F5 7 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>/Annots 189 0 R>>endobj
+1486 0 obj<</Filter/FlateDecode/Length 3969 >>stream
+x[r }WCp=SD)Kt)U< Krm.)
+C`VA(?I`5aXd0:;c2T;dCa2{,s ``\P]I)XQX)C3a2EMg0E)KqUu)(h\E8KFNe`vv`:aHmf%RyL(aËS& #@&rqB,s,Yw[2pYJ`_ee6k)s=Ez[jli7OyeD20 xr.VAzAQcUF.dp!z 6oc=[W :`^*~iJ<XJmi)y~pdg@ Tl8
+"TYxs{FqbF5IOj9<di4%TM#.CB8$tX- DK0i1M¸,ki ’cÚª EuO-) X8*$
+\S JzLVbkuc$Z{aR7Ng,K6#@\*oDz pUulYIfv#:z "m(8a)96X1EK3"pYFE[P`iuLAgEC\
+$cLw*cy2+@n e3cgt@a{
+%)?EN*q#e`J \Kq8"$=
+e8h[9Y$11[LzŒ(!$ßýŒ3¹­g
+ê|Å9 ’rT(/q sBL.~~w_Mb/
+EN} ewI cTz1l%Q 4e ?kz/WXL4MM/gH7,|ND'K zu!"<|Gs|Cg:f]8+mOQ+K}oXQiÖÙÞÍXz-tn35_EEeO~s^~ /.I 2%t"IT4]nb[kW;E0_Bd:l)M8Axow 
+,4M.ogQ
+0.ctNWJ!}/8' °~_^nçÓ>z?2UT!Q3J#))HN8; !E"EX7BD,I\1 ^-F
+=w8\ur9rR 1\X8PC;G:8+qlZ"U SNp>!I^M{X wQ3F|tC)5Zya/M(T'G|v0{[ip '}Ai\!=?n ?@uE~
+j3;@jA*>-\Qip9M5EVCpHB<y`V4 F~(@eKxUm
+5Z`[\?V\i.?C#f#;-*Goc',Xf&W>^Fh7sJ 0D1Z1jp5ww>( `hEg+3`%O|?{sFX5
+|x5Q!|S$y`WejuP35yf'ww= 2CyH+yE>&~eS>z
+X%m%dsoYc>-!;u&*i79fqMXkµC~rmnɋû9:¬^)ÄÞÈA9c<*i3l.W‰4êƒþAj<I'G)2+u3-(o3#fWp55, I"2aB}!
+m]):{?a<V1=N_jP% TO$9q :m0*~y_ljaAZ 86q 6*SR.)uZFiKI*iYm/|$yt=_M:wQco] tPvoOix?7p*2}uL6{vI|mtOl%w\y4';i\OS=^D;=ҧӜWZU7BMT6Q =BGW ]VeH>2PB:[vR`^nmE8QB&*2;p >/G25QU -.xJ9>9/-WO@'n &D&$<V
+Z9ßVf#IV<vM-+YgS G;bDWB9N6*} p|9~_ j#^5
+u}q^W'A{i2tDqk#w~oC"~xt~0?lY>aW@aGAI_COt R]3.N_??Mgmrh hx|f?{;endstream
+endobj
+1487 0 obj<</Type/Page/Parent 1476 0 R/Contents 1488 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F5 7 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>/Annots 234 0 R>>endobj
+1488 0 obj<</Filter/FlateDecode/Length 3503 >>stream
+x[Ms9½çW1{:m9&I^RDR{ay
+LCNe1< EIi!ch 6\S)g ,lU,V9&/y@C6`RaYVT5IKDbIErMDM<Gn@`rm-["A 9/HiY1h+k14dE DbEs(OJ%-HX k0XLm+r2zQIa c jvA1>8 Ub U5lY5,`eY!p80($lJZL"-R,iF[^s..$yLvhFc [CaX P]
+'") +
+D!sh $ s0{JZL#7`k
+?>` m=DRfCCh`v%I q@Iz i#i1YF4`{`y#mY)yR#\ImGVRIA=F$[34(-(` yudE$@;gEg3<mP:-(>3z'Eb`#m,>dLoi1 5,63hd 7 h[">#e`Ml[v2P@RI6kXb!vl1gNYEg*^\!lB`# #gV&›$Z*8>re")aYeYx1,+y%ejg 2SHZ ; n-[`UEn Q ^=WE *9^9(`Y"h,k0 gˊ¸ØÆ)1¨(âg H\43C"Gb`@Mh @M0Sbm{ C
+O>-g7no&~@q:-#_ +J~jp,O"`J v=[SH[5-X.a9dq[) J^7va igs~+t9T"*q¶Ü¬úév²™õ<}ÁÌÏ-ß7û
+Ôõ`ò¡øŸïZ?Je]ES_7fN$f,EE f+FU Up*~Z(~G"NZ
+48X>/?pxk?8g:g;n :8(pE~È¢ð;“Z
+3{l;V aw'%~VV:OI*|Uogzp.3q-"7CWn68^Qp5W>a eh
+endobj
+1489 0 obj<</Type/Page/Parent 1476 0 R/Contents 1490 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F5 7 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>/Annots 277 0 R>>endobj
+1490 0 obj<</Filter/FlateDecode/Length 3520 >>stream
+x[Ms¹½ûW!UBj0sJiGL9/#rdq#re{@PtB*I<F7K,dzNS|y$U$odURp663p=P6Hl^e4p]H"4S@zImRE@
+%#)BBPLHBiPJ0|/T@8W9P%E(~B&I,P54HBKWRVdB='CihCZVj
+H$pWB EhAS% ~ XIZ5%FW
+
+B+iy* 03:0r
+SN!Sm)|O!3 Kql''y"ixVXAe)\)$5B2,N!RD2>aHS @L N?a2m;9f,(2ˆÏâþÄÉǕçYj2 D9r
+xHyHB2m[)$Q5+r2.kiRN!&Cj p3` Mtcu dirq$+H.\OlXoohmQo6vo7K@,)}CE,|uoa82wwn0rutEUî+Ë|»w}· aj"eèènù/îjIcd4IUt*:JuGrZ>>`^Or/'}:-j. ?77kNXJaS-?>WS3jv3Q(F`,C\rBbG2[9
+@ Q{6v(uYa7jK86WTPJBhy_EzkS.o=-Hbs8-5S bnwL{i-B0fT1xbnRv~]/%H
+Evg{p^>\wLQyg Q1J NGN4?%BzOUl.9QvIu6#xi7ykÁ»@e6?/ic_/_tCG=:|+Gb?0e1 v6&BIuR=oJ5hPk1;{CJi_h
+2UGzJ4;lõ÷ÍZ7c%vwg
+]l+Ip j2l?(k_W?'/JzgPZ{vw!X&
+9(Sl#_|^x'hendstream
+endobj
+1491 0 obj<</Type/Page/Parent 1476 0 R/Contents 1492 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F5 7 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>/Annots 319 0 R>>endobj
+1492 0 obj<</Filter/FlateDecode/Length 3077 >>stream
+x[KsGW-y?er"LSC1!
+7cuFX1'& \MR+1YV$ul&a(zLdlND.+25cR0&M -KcS)pYKC%lY(l`yY0T(7mT
+cR.q|=VC;(N@
+Nt#=&KD",8E¸ FI!6ulM0!Km`;RC
+(XaKJ6ID.K1&E,z,*B-"u.Ia1XDaYVXzV\4E\8prE(6FYQE k4%eV#=[Pqe: 1%K. d@J8.Y%%=CXvQ[M8?pClC}cK6VA Ru"Uc~^$m-rV$
+'`Ta>hc}m1}].t=]
+-*.`n9 G>h8QkK  N]sOUFEyie+d|92AZ :?ie|8Zq6! 8ia
+5uG!'G etB ed'(,Tfuo=*:{vdjXpX}</8/h#/x_>c|ES?iG?%~_0\-UxI;z~ ~}yvendstream
+endobj
+1493 0 obj<</Type/Page/Parent 1476 0 R/Contents 1494 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+1494 0 obj<</Filter/FlateDecode/Length 159 >>stream
+xA0 g;Gz3?@H$"oN^L{k_AR s"MpA[Xlf i+A/GBhrPC8$ym'R?UsF.] jq?xy;endstream
+endobj
+1495 0 obj<</Type/Page/Parent 1476 0 R/Contents 1496 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F6 8 0 R/F7 9 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>/Annots 362 0 R>>endobj
+1496 0 obj<</Filter/FlateDecode/Length 2505 >>stream
+x}YrH+2|9rdf,RX,"=*rO$ M(+O|'_?AM(O<J
+7|YJNxhirrrX XM</,i>|4 itvYN2 l &Gj 6w?`gSoX'8" IAXaVU|sH5k"E< VaH(LY+H_HA"0hw`u`g1_XO(YY{XUK0FYq7BI{9wG6d* Pa/$
+fQ@1*i&#^6C eZ0 k0sVvwd5fgx* %E uMBNx`gU3j 6
+0Ok$H0BFlcL8UyS*aNQ%3ii 6)~jGRc* kR
+jWcU3+x:Gv;4gRQokW$ )*yf+VaU<1XEGYk2(H<D*<Xk kMt>^>XrdC~bȇ)‡Ö:àXYQCiqEV"iVaV<A)YpJ)Vasy*l(8``'
+e^~JVax,i9fNVc7a5w1q `HcPq;Vp
+P De=#A#M0Z\E!H,R* v*XT^=kN@>qNw* `FVB
+mtyX$1BK f+SZ'F6
+3Y8aD9J.Gm0*qT~38H
+q 8&JAp C2Tg89$<pF9)dBs&0&aD nR8o
+ &{:wp`(Y}&Xu?_^^=f{[wWwK@C/?LkTI5|2Ei @#$5#ZHl7l*="&G`7 =@w]$P9/y$oaurRxY#aT,*nH]uF?>$8ftUc]uIN,xU8%[Yp)_S"K:[\^^K2rx )}EpT!n W3*oW/1;/94uAqu@-/q_tyJ[&=xaSKWubgmK~U.e}ZoyX _y =d;}5e*hRh2Q1U4
+?^-R;X]zXWv4@1yt.8?k2C8 =WE/St9upMiM :x2^PrW7]}t
+!Ud-\}YwM)9>hD8NGsuydpsup#b[`zE]os[G 8F1n;)7n`v nD-EZs|ˆÝš.
+ތöða(ðþÁõ»’nMpUxh=3{;7(FF'M%)?!">[Q3=4ybk4>osW1.C(.L-
+endobj
+1497 0 obj<</Type/Page/Parent 1476 0 R/Contents 1498 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F6 8 0 R/F8 10 0 R>>/XObject<<>>>>/Annots 414 0 R>>endobj
+1498 0 obj<</Filter/FlateDecode/Length 3569 >>stream
+x[o×…ßõ+ÎS>ex+P4*bYoISe8oC
+5>QQdV`O?qX a aF8MP ; f
+]m\dNam=a++#=acC5"d3G1T[6-TSSY;FDdfj#Z3r`3ji gYz+G@tTX8ra 2eYf`fV a3hdgV5b26&}V0,!YV%hcN FF-1fUXO6agL)*&`dV5*aaNlQXd67oR U[‚„9‰T ;[n2+v:
+]^1 p,bKY
+]{V)&bX)fm(FkqQRL]caYl9})#$0u
+V0,mX(+@ m-6Il) &`X\++8@gRC5c0X8vL^848*6w? \X^c4bfV/vE#udm0u&cO
+=aV
+q(,XfLHUlI/lN>V6,Vly9&IP16sa.l v#`D o
+
+M,U JD"a63M&%>MdrfGULl4$X(y!"7Y0FFyql;#\t1V0s(a$F (VXL`.lSY!+QmSpj?c Tf[6Ej'Bmo,Eo3e
+"l\5laW|'8
+2$9XCtkpOa BYS^Y0YI3(M*#6V0,QOV5]lV03 BYaC SZ_(:1,{
+FeV0bB +IV1m2ò­Š…GNgl&v'` \ar
+6H+*1IV1.(C/k-L3NL@L-D238{#WZ +"aHX;qf[$E \-?rh"2#l=aPdV0 `XnB-*AGXL
+8N,Ql[X%A#*e
+ClY!
++0GQ‘»ËÝõ„qÈ·a›CfV1ok
+e3`Xo `+ZU V6+e[`nNX)z)ud_mogRM3g`rV3$
+%$-!`XLYs{Y\dbXz8Hq|] ie{m8aA*:*GXsaO'
+38b*(~6p%µ<:arfÃò󉲂Q/YVdl4u9s]gnLpfV0FKXYIacPU $6awwF2+8Q^b'w3Ý?Éò¨±äf6šUc2I2pr|#wW0
+kqWobX!Y]{1l.x+x,+K=j +6vT {FbdiI\g' 4.CmY.C /3a&v2uVSNg.4s1).C8JL[!rZlqS?~fa5yqoc27wV&_{Ba8/]9
+w <ng=U=pZ5]n;g]*|he. ߘåYuvMom\m}z6/fS*~C^?.4jV.\f6\}X~{,?]}&En}Kw")CvBk]rx>[`+VMX rV}UsUIY \cKVr(77,$]}m/
+E~Y"{_HKK{! <$ QmX{qmZs9qr6<-~&A#ehW5?Y:8@x<SWUzVp;j*c]pWjc|x~2k_ZSoW>^/J
+.6 6Ý$¹¹¾+BOlFO,8q)qMhdR:xmE| 5=u_mXWWW] 2U/w ꮫ¶¡{› <vÕ^¼3ÏΤ Éåcµ[û¨‘9ʸ}]nmì›ÍÁ´Ç‘òÌH ?oowoo8tzkcF C]z÷-#֜|8ìVfNOqMhAve9f0l{~V@ Lik</= {|_U[v=!;f'&#md,1z•Îå:üt}õŸpSzowq="3TH? Zm^Q\sRaIc.7y@~e`l?muhz,mvToj5K^kt6\z,i&kK/Pky3s[0[zUM;ce=7lg]%0n.?z )(,VZ6V!Cy]W~{6u3GÑsùjEw2TaH[Q;F>7]O3_VURSz`b>yL*i- : ~TV-iIbo|piG{<MmE-T 1|ww1endstream
+endobj
+1499 0 obj<</Type/Page/Parent 1476 0 R/Contents 1500 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F6 8 0 R/F8 10 0 R>>/XObject<<>>>>/Annots 466 0 R>>endobj
+1500 0 obj<</Filter/FlateDecode/Length 2428 >>stream
+x}YMWH+diXzx;4U4m[^I‘)©Ò˜™7ïõ›p(³"?*«$þs¹ÿE.], B2sHe n]%A<[Y ve ;aqs:N#8-s6+ @@**h(O"(?25 &$#."J&d2AlrULuq<bhfX3?pbl3y`X61eLKd25${`}eXe'A9N:VD
+&Q)Q5bE5Gb/>f G-[mg {AZ9 I
+p f@9JoXU2l)y k0Lm $&V%`7$ <e@5~l (>,f6c`(d $i1XqH9l4rck13`33 `SZLd1 %\ OF&
+nIeen(qZ`#6dGiHX86g +gqertHLcXY"UhW=RAS,$)tb:B:"5`g|VyGC&)1X5,Zk|vP q VGgS1a FwY ]6Sg4+':l :j;rD#F-g`y[ƒ)Š½îYZx!YY>pY9<k0Eqzb97gUldAFD<IJmUg $O y1QUrSIl'D`z`g f@5y`=czG4 1%s%5<k0mZ 1a4\c[cY%8g5,Y`.+5lupx%HD p72B* cZCb!-f4!4Tcbq`7eo+es:x (P=&gai1zmSo5lmXY j<pA
+)iqGw4<r(+RLXs]},O2;k]`{a8y9kfsh<2NUt?I&> nQ+C[CZ<< G"`xw/w!{jvuw{q6w+&ZM e~Nfy&M_9,T^+kMQ]BA \(Q2b ö݃lÎÕ_55N@MiGI`WvkYoDOqR2VG{[ h-IYxle[wGYz<Pr,-9g^ Y$s[}=!o0.7us j}Gc
+ ` lth3y1{{ /~(t=.s, ?UaM<7m>~gNy?X
+endobj
+1501 0 obj<</Type/Page/Parent 1476 0 R/Contents 1502 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F6 8 0 R/F8 10 0 R>>/XObject<<>>>>/Annots 506 0 R>>endobj
+1502 0 obj<</Filter/FlateDecode/Length 1701 >>stream
+x}XnF}WCy<$E[L(R%)'%C-9>sYyGOALa:.~3vKqs/A
+bRcaxU,"*| w)Nl:U=a exb ('N1o R'0%[Vai0uSnkBma JaO$ 376G VQad- AU* 6TH60o5ADLP0R404n~bnIÀv¥LQG lBw<<1dI?15$HU85z< }d 
+C5J9^*g2fV)OT
+R
+eFYUFZ;jl321AI{
+s$52-
+C-0 Xk
+s^txi/Te>k`8pBddXf]^Hr!4_@Do!:3endstream
+endobj
+1503 0 obj<</Type/Page/Parent 1476 0 R/Contents 1504 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+1504 0 obj<</Filter/FlateDecode/Length 113 >>stream
+x+2T0
+endobj
+1505 0 obj<</Type/Page/Parent 1476 0 R/Contents 1506 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F6 8 0 R/F7 9 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>/Annots 551 0 R>>endobj
+1506 0 obj<</Filter/FlateDecode/Length 2556 >>stream
+xYr}WtKU+ Re;dJy$
+#7:IFk0`:Xpbue-~Dfk0G)`305,gU`)[ -Yhe0%"3y[`Ym,TD$`*v`rte(MBBstV$g <g a!b ,{T`]q v<%©ˆgud ¢U@@By*
+L2
+l@Z vZNF8:q)ssvó¤ÅL,IFg=k1XyVbG9p{ CFtJl*51
+8wm -N0 vaX"^S VoA#k0&z`-f4`Yv~d-at!Y *` dT(7IjNd$s w@:W ]UPDnz
+`4(( k0X#Ya3^tfYUX H"Yhx-:&: X.5Q8g-Yn5,)pA;XASfk0]æÆX2BLX\uXY3
+wZTh"O"1e&
+\^=<5p9)NPa; 7}s2h o3FNO'dPCp)H7S4 "=y}3?pl\{0z5"8yw7>N.41sÅÀBQ@w L+Y=,jf~=TmxEg/$VU/dÝ6CQ5<M[VF2PlC!E9|])szi^ V@/&rwlo«oåöEDtehU2oO\<lKZxf@?t{U,>\_Q_;CH>=0 UgOM?9:*bI 'R]_\J#Yu/^Eui/ew>s*`)QpG5<_)mMBn>-'OJI!?Q
+?>
+ym6}};}9ihJ8oAmgP_)=z=-?u~}tYg47UkE^+kYC)WMu[¦¨Ëá,Q)|i%,fo?.O!Jpn_?]r|X2DHbsBH>$sG>uw®£*vçêtÄtu¡Onx( 2_] E3Gv&/^N"Pz c,?\fK4msY:r,"qMOm02$)sGib3!)G2tOp>_WIvrwopNr}jF@RoSgµabÌ¿gç²Zd¸>Ÿgt7‡»c¨ŒŽøÿíÓÜZ]- CW=Yq--<84-p,w(74O:~xY~;O3><DrqE9B{_NEmvv*;)4  %rPC1%zN0 x3:m p/On7 ?;;&q
+endobj
+1507 0 obj<</Type/Page/Parent 1476 0 R/Contents 1508 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F6 8 0 R/F8 10 0 R>>/XObject<<>>>>/Annots 553 0 R>>endobj
+1508 0 obj<</Filter/FlateDecode/Length 190 >>stream
+x=n0 ysc aÙ PUk+Jy &>[>«æ<JF%15b^bqp`$h'Ff8xYoEL<rb^yoìæ©ï҂×)]‡n\ËÏ4fUX*][g~;.tP%Jd[4Ul:endstream
+endobj
+1509 0 obj<</Type/Page/Parent 1476 0 R/Contents 1510 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F5 7 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>/Annots 556 0 R>>endobj
+1510 0 obj<</Filter/FlateDecode/Length 1359 >>stream
+xV]OF} 8 I6jZT;w&;*+$sg^HC i67 fKlt8
+TP8< f{q:lgoNN& FR5d6 &Q0:<8_Wg42E?kji( GZseBKik|}h|I? zÕBE$)R-U"^LZw fUM"A"/4*~VeBC^(Q6*jj+ Gvdu!9NvJ< (iMJWpPK6b(tV7TJ\]w] WcbyLJkPTQFezc?qLa0
+B~gQ<Rlk6e<40o+ cU@8m
+eX$Gd]"W-_C.XbTnWT*ciJ{OW}i!
+GSro 3.Zc9i-DW">g'
+endobj
+1511 0 obj<</Type/Page/Parent 1476 0 R/Contents 1512 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F1 4 0 R/F4 6 0 R/F5 7 0 R/F8 10 0 R/F9 11 0 R/Fa 12 0 R/Fb 13 0 R>>/XObject<<>>>>>>endobj
+1512 0 obj<</Filter/FlateDecode/Length 1379 >>stream
+xVko6_qWl e~l]}m >mH\Rrl'%Hk}{z)F4RV] !MgdD G6`X3qL;Hd~~bp34-sBY#hZV(MBjB/CIf&^Nb~vd_^>3)Gvr_ 'sRK$_O,kBnm
+]*E"@H_0"Kñ`¬B@jIyBW`PLqj1L]Lnt/t3>o|
+ {<-3UEi^vaJd *4jjTpnglNN9**K&[fi<
+)Dg]!@pWi+!S?kN]NnPK%=eP:3bhx?jCH a9]M` -=qd8RnzUvRR)d286n5,[K8\GfpQY9/'mO7o=Lt=9e" d];2b W%= E% Z<|(`I~'r^.$jH_k5_z>e08
+R4R_x9  W`L(5
+{8W-=W.#'zRQnqc?n7O.n/}
+*x"qltInK>KD%Q
+2)W!/7juOwOn%d$VrgU:*h`:{|L".?_gkEdM(P\c{?fd6}_]`endstream
+endobj
+1513 0 obj<</Type/Page/Parent 1476 0 R/Contents 1514 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F1 4 0 R/F4 6 0 R/F6 8 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+1514 0 obj<</Filter/FlateDecode/Length 1777 >>stream
+xW]o6}KS Vb4 `]1(@ITZ"UsIqn%s9z0S|Bg3fdJ9>O#dg''7>E$9-rBSZdGo^V?o/_8}>N.~E~J*k7~E+geM6ZTkcJBe2Bd'
+UJNBNcUBRpLCV*Iq
+
+ >="ACNc43kZyhKHACJK72ND?Nt`3U 7/nw,^T6z
+R*B ^#~4Yv*6qC(
+~ dN µ„¹Ø(i6K1h-J!J^_ 1J)xP/Ez2
+9'&lr1 YPuwtqn45/x.'bCmU,/-XF~b,R,..1(AP9R=Fxx<!i:|9IvLf&~e0qz[s`
+z?1"
+Q;Y 6zJlO|;
+endobj
+1515 0 obj<</Type/Page/Parent 1476 0 R/Contents 1516 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F8 10 0 R>>/XObject<<>>>>>>endobj
+1516 0 obj<</Filter/FlateDecode/Length 420 >>stream
+x]R]o0}WePH,D%[ire16".T|;#[cBvAFH(\#3^M}8F0$3T5x<P{)v}+< op^u&|}Ikj `h+/ Àóñ]MfDgkrw!e98+kpk@y@469)C<*L-$Z{5LQ :=|,ab`AowP~|.<=?V%xz]$hm/`3Y6>_zS8 D^JcgL'U}0 q{l18i$Yfi?4>U= .Vendstream
+endobj
+1517 0 obj<</Type/Page/Parent 1476 0 R/Contents 1518 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+1518 0 obj<</Filter/FlateDecode/Length 1665 >>stream
+xWMo8W zi 4Nqvov\z%bCZoHJ/ @"gsV >]ZN.hqIL]nhS\IS% VYin t+%/m3|nIyry-RJ[4|e[]V"~Q2TX5EPAj+LI8 !)TH[@ ]S9UFKYltD1KOle;<.m-aMHo%{V_'mLAk2kDYJl>|
+alTdC<iéð6ÕæákŸ•}ÁÍ§Ç‹ûÇ­EWB{Km,k[JB>eWBWb6g{d/T[9;|$ RsqH8
+[Tz-g[m)OJ>=I:
+Nmw|U8oQBGl-s%K =r6
+Zc8>$8uHC\5C|MqW5=AB_A z5za,IF87+v-CMs
+g
+>zQb1(jt = sA8Z}d#WXB+$fL)kK "9|OJbE D2SwYTjiEm$S1BHYR/#
+$?%2HE9kwYT]]8@[O
+ ;N5u*%d!#x2HV<V?w<*Pn+NaZ j>('Y)Kfch1F1T}=w431#;Kaxe6DG+&1c rDtrR}t#'
+[`~*qä3ÖML $+Cm_"(-2yK/ TBw0@ }.,`9J`Mh1
+endobj
+1519 0 obj<</Type/Page/Parent 1476 0 R/Contents 1520 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F6 8 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+1520 0 obj<</Filter/FlateDecode/Length 1414 >>stream
+xWOH_1Y$$)}
+xAL~bi48DDHi<N*F'|qpSZ`k2iD-
+7UaKEg$ m*;Z|1|~Mb)kVHCKEW)V%zH_!2%<\zN=YCCx$rk=.5Y PB AR~gJFMv ;IEJ*kGBo?/u)&:NIi{Ii0R}<69]J[]|"Ny>tVG5zUcrkuw`Jn(L"[
+
+h`I!=i(3Rh#A7<phQ(S,2m8R'^r;,@j4SB^d+>{uxc%Z ^Sr2ehYs^^VQjzAnC
+>xPK=q9G-AvSjk$k_;[m
+~D+!h%e|[9*di,b(XrkYS`-^ pHCj cPZbS6"5r5NLYMW<ieZL$V5[5^t
+PjUO{5v1nG:t?) 46I xnIAGZ.2A^g( (w
+gmlrQf_`]id0wz$rQ
+ãaà yßa¹†‚ñ ?p:a>÷œ3åƒÔ9k° µ>e"¿BIUFCV$8šAh, *cX`.M!\#a%4|paLBDm6}f{zuaoch=pi[gi ###8NB7>\uK!n t;D= Vw?^<%N%')kqfvB
+endobj
+1521 0 obj<</Type/Page/Parent 1476 0 R/Contents 1522 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F6 8 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+1522 0 obj<</Filter/FlateDecode/Length 1901 >>stream
+xXSF_/!U X~! sT{k$vHBl0f_~vfr?39?3)PO/98G
+Vd^KC=HaZ|ZheKLl46|MplmSdm^j\8;]:5QO(hU>Wbz@l/<BWMdtq7D<xSNR0U
+1m)`M7bX%C
+1vk>Ru2'qm)>@^4`:|fZ9Sn (g_}LC],}LTFlh]dL3C5y 3¡ØGa5 ]XyT 5>M[,o]7b&(S6QX.2vi^741|yVK[HC-(h6wQ`%)\43CAD pjR[}[er ]Bo%7w?MxW TK +A~qm n.
+}LL4%lEU6nzQE>=p~:5
+f `P
+j{
+nj~|
+&~J6I4:/GcP7:D.C=,: F:r^jrdF`OKZ6 &4q$^x'X6Fr!x{(h
+endobj
+1523 0 obj<</Type/Page/Parent 1476 0 R/Contents 1524 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+1524 0 obj<</Filter/FlateDecode/Length 867 >>stream
+xUmO0_qSh!)H
+&3yigAJ&[1ŽkîN/&SPa)`ei¸µø»`
+{ఐ¬àÐZ@¢ÑpW@+NF#GQWNjAJd({zzf$ZzeK!m2 `5L(W hVcn?hI+#Z)Vm-h+g=M'q04o8S#;.kB-}]1uvZ>dL^}3"1k4k-0AgN`w8^1+*dCtRvPE o$qU(#6,E3&^(pr7;xe$8>[%Uoa)0U3= o{ms)w}wRbt)5w
+endobj
+1525 0 obj<</Type/Page/Parent 1476 0 R/Contents 1526 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text/ImageB/ImageC/ImageI]/Font<</F0 3 0 R/F4 6 0 R/F5 7 0 R/F6 8 0 R/F8 10 0 R/F9 11 0 R>>/XObject<</I16 16 0 R>>>>>>endobj
+1526 0 obj<</Filter/FlateDecode/Length 1794 >>stream
+xWn8}W pjE/lÆiÙúBKD*$WgHU/(93g.&4 -4[PZ]1dA%~OJ/hL8$7xGpdA }}G1s^,oh$XKK;U:7^Mb#|',,$Y{k&+&tqhtfRI93K4yS-›92ψÄWLATA2'ŽoZJm[{& NV$&5U-,
+rX!'5D}.9{=!X{3W(K<"t,8t?;B$K R1YZ'? WeIFm\X92e0>$3F9FJY*mK
+ORd6
+E|i#Q"{tRX S_Oi/C<6O9
+B<CTr_HVL\d (SyS3I
+AC`}}[%4O+SHwW }4U**nhq3p#k} hq {j#=;3iS`1{1 Jt}f{o{VTb=V &fUÔ^{Z2mU0QnPsAhzn{Z=50\+r
+
+u/Qa( bcJYG] Ig[+8KO4qP:F47"98O}k8HXdz}Ea{ÔZy c 3&2tFdD7SnB?VItwW(/Gc U,XL
+0*R8Y,K"M'`cE2r_hH>pv1m /DCr>{¢¢µ´¹LYHkD$\A A;DC*3cgs -(#e&U{*1S4<Yyf49rd_6T _D FYv2e3c Ek1eq|d(ST;Z?
+cFKG<C],=|7jQzQt@ossS"~w-RJCaz#woy>x0NxdfVUVYlXC,?*ua
+*\4T$#q0OT0oc@U5~9S6a3G wE<QV:v€>–ƒ·Ž ìfWG;Jg~Y?^jx,Jd=ThJq&(F5S"8YMHYid2On}0FB=rG8ajj7hT0C7-X(aEV~Vh^=u(X=Zuu5&$#;|U7f;UpT
+ @am>E2^3+[|o,Yt5_|Of t' aqiX_|% endstream
+endobj
+1527 0 obj<</Type/Page/Parent 1476 0 R/Contents 1528 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F5 7 0 R/F6 8 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+1528 0 obj<</Filter/FlateDecode/Length 1464 >>stream
+xW]S6}W/7BLXN-'Zdd v:0t?9W`H i6` h<G#g<dp<GiÆšÎ'Ñp|Li0e<::Nq`@4LynJ-fFY4_n<bM:e
+G&ZY\UzJM.TAN&U~K5$FCx5rqtnXD^+rkM&(bii DgPie6^/lmXYxBKd(Jq&_}::)
+¼PH m :l#ZIWSrlD\NtU+$VF(Js[b'OO
+*v\f@cC'oR,-=PSx +'g{KpXdA(1Rj79¼•}ÉU!L[S7(*rnQe]jr\Z5 f_TH|)1E!n6@1Ni%Ñ,¢’?z+kîeñã#™„½Ž¿P5+PW9&E!9$De9 l@QXvpId|]&G_\tR]\}].4tStz2^7Nhe( ZC0 ^
+-
+m6keW/wd]`[[`|?zq/5GUCHl$ 8vH@)om@w(PXKZ5h5 MjvWq ;BIR:3yT_.em`$NJb_[:n1=2o[Y[OzFR;["NW \
+?,|p{lR +WV}
+endobj
+1529 0 obj<</Type/Page/Parent 1476 0 R/Contents 1530 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F1 4 0 R/F4 6 0 R/F5 7 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+1530 0 obj<</Filter/FlateDecode/Length 1421 >>stream
+xV]oF|X
+y1uwv%I`H/'9Ms*6'lBg =Y6C>f^/O\Pr -KB(lV[|*(V
+U+SRtTTk@'cK tF2niC]-08F^itA!8(\zQkQFZ{2kj]C
+cIY6" ^f]9A#Xr':Q55}n
+X
+rtrl3~}3?|GP1)fX7o@M2l& {k(lVvAUSmEhPWcjOgiOYF5xw~_
+zj)8sp6233As] Z}gg Puy$Oi&(&NyhF/8%<hsjh y04mRe +]KUw|zn/06D$.JW?be?I%jq$N<3zwN 4WP( -]!CH
+KX<9`
+endobj
+1531 0 obj<</Type/Page/Parent 1476 0 R/Contents 1532 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F5 7 0 R/F8 10 0 R/F9 11 0 R/Fa 12 0 R/Fc 14 0 R>>/XObject<<>>>>/Annots 571 0 R>>endobj
+1532 0 obj<</Filter/FlateDecode/Length 2094 >>stream
+xXn+
+ H M<1$psct7T7)r2@ S9zbZi2E#|r"|9FT8DSNW,8ZbuO:EsOQ4nxXP<l4>Ax6q|Y4ix/MX.{#)l.cO3.bj3V#9á >äüMFK?N _\ R& .#$O,Vkx<F"m_#i,%zjk/P1oP\22qQgi^&Qan2oi0fG$pR.W=)KGmO]}RlsiC'dAPC ,Lc62JJ00mOh5'ZO7GM"MS(v@6lMDI7. 8l>Q!T#S~_DizJ{?nP{d AM~_=?u!JT[2/pA,xNs,ptF92S:8XZPvP{K1!u; 38{=}y!=f6FO}CgW\LrT k$5G6xzl e*}-I]$H
+e[
+uxj`:V"%).H(kJERdd%[0
+[J4 nXAa\\f!8[uuna³³–ñdì©L-E
+1EdPh(L /)ci2-@@k?
+LH@moj+[YJ>efM/>5p!Qm;iQbFOd[*c,J!Ee$fN6cJGL#)b11#VfpQ`n3XK,p( HgUF>+@,?]+6{
+#~26 P g8F\9/((~^
+79Rd G@|Ko]]UE
+枥%Tr%v_]Fk^+*;5.&SW ul[d4Cz9Fzx~`Xu5Us3YeVy\QgyD_?SS+062w<q@X_
+2MV
+dw 8?>aV+l},F4]L|.^ oNendstream
+endobj
+1533 0 obj<</Type/Page/Parent 1476 0 R/Contents 1534 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F5 7 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>/Annots 578 0 R>>endobj
+1534 0 obj<</Filter/FlateDecode/Length 1818 >>stream
+xWr6}WL3cyudI-y$! 1I
+ F#ZDR&4KIfI*59R{p @)8N2% G0J
+P
+'[5NeT
+lX"m/°îžW|9t6{8&\%N^nTNlpR~${ZsI##RL'f$ vQ=]=grC
+PnOtLuP(7/8Z2zT?(n6XseY${T2;7dmkfpVibT8 pc4s(<8UAXX `tUAs".OBsgJ:Kw_ng1P5h"!J6LE *t/3{u=Az(47:dl[rFSR`APGwj[C``adr"E,*`ºÎÝ($‘OmQe2G`|!{8s`7|taB;uBko@m6P7@lCuxfZ@]8Jn.S
+=b,mbDN O-  z~HL)qWp`#rQj]4 H4B|yO9Mplpx0k fX^2Z:~c\~v
+2Pmxv_&Bvs8V](v>3S+W'39ZdB@`'4JS%ntRpB@~reS`8`<Q<AIm-jT "L:ac;va8PzR?(sK:)(BRH^[sHs h<J7T? {^~<}|G9XsF+A]S Tuc3Z!XR[h'y!u %u?/8BZa#zU wI^wc
+feM&0l?Ff:xYl% ~zOtr8V
+endobj
+1535 0 obj<</Type/Page/Parent 1476 0 R/Contents 1536 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F8 10 0 R/F9 11 0 R/Fa 12 0 R/Fc 14 0 R>>/XObject<<>>>>/Annots 593 0 R>>endobj
+1536 0 obj<</Filter/FlateDecode/Length 1226 >>stream
+xVMo8W %;|H`7&z$aK(GIf8#f) h$ͼÍý™Ð"
+ñ9À_Éig ØÚý»»͗Æ\zKrBhh[f
+xkm%2U<{[vc:[4G~gk:?-\y>\5slo~T27VRmMyLUsb%+R/Q|m4I#MjvgvBrMqJkQ#|jYmH'N9 ~NiS%il$W"oJ
+Q&Jsl[uRmvo$o)ZM?]+LN[vb_6›Ãœˆ±aÝ3¡S d0`BXZ],
+*x>p<#:p&A<?va~\ ^xX%!OT STxjSpT1|m5yVGzg+ lGBA>2{63ns"J3^:v}w{nN9ÉøK9-_R>6 V e >i&<y477 Q 0_} HJjendstream
+endobj
+1537 0 obj<</Type/Page/Parent 1476 0 R/Contents 1538 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F5 7 0 R/F6 8 0 R/F8 10 0 R/F9 11 0 R/Fa 12 0 R/Fc 14 0 R>>/XObject<<>>>>/Annots 596 0 R>>endobj
+1538 0 obj<</Filter/FlateDecode/Length 1598 >>stream
+xWn8}W Rb@K.BKT"U3|m&)s8v.~z4`DiqM4N 'c $Y@[><:bcAdLuNza2/tntI%
+1K|%~\Phx2$Jn8Bz%E,@•ç¤%
+h8¡•8cr ڋ\tEb!VhTW4e./0vuZkt\)S|gnq^64ocI/0rZ,"7~"Szet$Ac;zðïÌè³ý9æç?ïr ßí?ú@0DQ25[::'yYu$ > 
+Vq#;p`6ÆQ#@|@@@7wr)-NJIf6- R DLEv2J?`;
+@'u*K#}au¶qbŸù–™Ÿ7{øQ4=nv$]Nd<w=;/ V?#XQi4B
+ :k<!F!j `PpRnr
+ C`?^i,0e G8ta6}cgÚMOQ,[^na"OqBh5w;CBARQna58 Gz ^JGafvKBOJnB~/A:s?IznZ BSI~54 K0a%`Fc~,nM)V=\hXR=H. z`*.!LT&Pv0mnx#7{}# h5E}sn z!xI/cWU2n@9M/8~L\_&L
+kVkBPt^E=9rm_[úÂ_nâw ¼/¥faÄ\“Gou&0V5=X5iSB"lo7]|=!c8&$j?`f'Jendstream
+endobj
+1539 0 obj<</Type/Page/Parent 1476 0 R/Contents 1540 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F5 7 0 R/F8 10 0 R/F9 11 0 R/Fc 14 0 R>>/XObject<<>>>>/Annots 599 0 R>>endobj
+1540 0 obj<</Filter/FlateDecode/Length 1829 >>stream
+xX[oF~8pV)$ZI‰ãU$@#r(1!g )"kswnh@}h<Q?Y43RGO|AY4&!3 hBh2Yo,L+4]eJmm%9MJn_0n]MH~sR%2!]J#\e/sK?wz1r P,FW$uFe$XB6G Z<+dnC<~YQ9]@s.6w/(:cncCTts!p^Aöˆáàç´EdT[J<y0lx!K$\RG)4y'nuZCT#tk)y&-B%um‰t
+uˆó6ئé³Ñ%.OFvD q[:K_B/sm {!^q;CmJgH% 9(mtydx  _tB7TXB Sw|^j5CpSA$4,C,O)#<?M4*fiv)JJW`+]+YCP.n4*C:Mz{ ;zna'#X^Fqz$<bDS+Z`A_b8k ;ZL;n#0t ?;//%:p-mg<qd%F:]<
+endobj
+1541 0 obj<</Type/Page/Parent 1476 0 R/Contents 1542 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F5 7 0 R/F8 10 0 R/F9 11 0 R/Fa 12 0 R/Fc 14 0 R>>/XObject<<>>>>>>endobj
+1542 0 obj<</Filter/FlateDecode/Length 1203 >>stream
+xVo6_qUiO*! ! HR^2m&16vJ}6)mi {l7$N {>t!J|'),Y= `%q,0 Qb@l^jr(-$a
+"9d([{R\VN,4Om!ZiGJ$7a­ðÛÁVB “l£¯ˆ^ý÷…X
+}!VXe
+S/'L4<H } MA(U)gX\laN)L[FxXq}` ~~_MUZaw`VlT<g
+/+DITT'kr4Qg.c*-6v$&»·ç®'ö*?”èS"fj6P'6(O6T"< k.g=8[zOkI| M.g
+T$]Ó@)
+g*[4
+~&P<w|;g m_(Z\'cWC>}|^dzE99Qr%%+ W<!zlU&c5fRrJ=Gv4Ei/[r8+)
+endobj
+1543 0 obj<</Type/Page/Parent 1476 0 R/Contents 1544 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text/ImageB/ImageC/ImageI]/Font<</F0 3 0 R/F1 4 0 R/F4 6 0 R/F5 7 0 R/F8 10 0 R/F9 11 0 R/Fb 13 0 R>>/XObject<</I16 16 0 R>>>>>>endobj
+1544 0 obj<</Filter/FlateDecode/Length 1444 >>stream
+xWn6}WLqHl}^.v.b((DG6 )9A\OblD)eIF4)%Gk$nc$xqO,ys'M<w>Y #E9(E6'anKQLwWlv$d|vvU0upmq@;87*sU/\Bq1,4,Av%i]KUS^|wRUyw1eh(350m29<U#3 RA2QikCG8i"(9ez]jJ >FÝ҃¨mH7m^T;U%.+ !e?aRMg45 ](6w1
+m#Ts2saE*#r ~J2Q5{~@EZJDYL§³PE% MD}dtV0G!TjB&CZBw|[F(u) #`AP
+sRqd7L#[
+vAm5;|L/]ZP hmº.Ô²mþ¥¹WtMM ]IZjSa],p nA
+2WyNQ
+@g*GB9<KcO!nvya6*<'aQXOO-\Kz
+n
+g'
+M;"F"vm"g%j)]vpaUQ
+\k4e%Wk`rV^{ZCc*^!tu*4v0Lp *zBpQ; L/w
+endobj
+1545 0 obj<</Type/Page/Parent 1476 0 R/Contents 1546 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F5 7 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+1546 0 obj<</Filter/FlateDecode/Length 1237 >>stream
+xWmO8_1R6ZtwRIKgm3Ni5%gfyVz
+BfXT/0#d8l*@i4!{-<<A,O,K^Es(?hj%kbRfL j_a9"(y^+n-f*rMn\j-P#]'\D-n@:,QN1oUM= QW OJ,39
+\IfP9RkDnn
+NMdm$d=jU/U{&6P;xE|w8oX uXu-yr/A(lv[Ja3*\K?"uNwpTgK1m=7`Zpo:p7km IxI&#23e{_odendstream
+endobj
+1547 0 obj<</Type/Page/Parent 1476 0 R/Contents 1548 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F5 7 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+1548 0 obj<</Filter/FlateDecode/Length 472 >>stream
+xS]o0}WG* F&m^*Mjw5P!$K{>qdqT9V%1XYohD5x MX8Aiw<
+endobj
+1549 0 obj<</Type/Page/Parent 1476 0 R/Contents 1550 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+1550 0 obj<</Filter/FlateDecode/Length 115 >>stream
+x+2T0
+endobj
+1551 0 obj<</Type/Page/Parent 1476 0 R/Contents 1552 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F6 8 0 R/F7 9 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>/Annots 644 0 R>>endobj
+1552 0 obj<</Filter/FlateDecode/Length 3046 >>stream
+x[oG+yX89^-/"Yki
+ci<p 5lL+i$BD1,: K8:64vPq,0lfY*=qDX?H2#X1rA+)V5` !jt$IcX;f0<uy;Fy ·žÖõvªÃ#¯ë1,ŽYxaX*HaVoYst#,T
+]eJgA9XP&=XayK9uX77$<
+EkK:b: U2PfVNX7H^a1Fx fY30lim&r4u9WeaXR30Š8±4›¦«œ´»Ù9pvw“94…dÎA2X)sb) 1v^4ÓubE Sy=@%d KR;&W0,uyXa2k3@=œHdu8^vf Ç«'²†­0ƒ3Ä$»hÊd´‚¥ŸéæEGR<Dp Lz H6&$Qr
+g@8(Lz
+endobj
+1553 0 obj<</Type/Page/Parent 1476 0 R/Contents 1554 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F6 8 0 R/F8 10 0 R>>/XObject<<>>>>/Annots 646 0 R>>endobj
+1554 0 obj<</Filter/FlateDecode/Length 273 >>stream
+xUQN0+X5~$s@q@jsI]5I YC\Yv<;/&!HXmLpA/0p>b*\{H.YXbb0.1h=P_nXC*g)eK Ag7s}wDw@R
+Ch#n(!^=_pJlx^.}hv‡,›KCQ&? )Oh'8*ZfgEqendstream
+endobj
+1555 0 obj<</Type/Page/Parent 1476 0 R/Contents 1556 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F6 8 0 R/F8 10 0 R/F9 11 0 R/Fc 14 0 R>>/XObject<<>>>>>>endobj
+1556 0 obj<</Filter/FlateDecode/Length 1548 >>stream
+xWn8}W IH]Ih[]!)_^Mju~4ht=ht5ZIp0Y=.`r|E`oX{iiKkX4 Ht|'f.W
+<|_ .x ))Y"gW\4\ .tw8cJ,f7[SCvG>~? Mz>w"^o7gb81
+\8x4"QnK:| !;DRL$@AlLvJ/ ym0y Zry
+zKa H]+{ gPXD1R7P^†¿}ÁÿÔõr+<ö"@l D5ñ!1¯t¡Dh@= w` A1'#\0;a\ V75b0oe$73jMQASm/G[)\Tq: 3F/;MW UA=:e\u)<L;Wx}HQ?HOk)]hU,0xe 1uYp}\*Xkdkj*^~Gr;e
+5RDIhy,^;PExX
+= >O|:fGzxDEPwt(N@PilOu5O^5]l|yNendstream
+endobj
+1557 0 obj<</Type/Page/Parent 1476 0 R/Contents 1558 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F6 8 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+1558 0 obj<</Filter/FlateDecode/Length 1297 >>stream
+xV]O8} iG-VEZiafi$NkHN%h(-=ss4 ~|Ai9DZWgbMbì¸ÞŽ.ocšNi#bmFH06=W:7^ ;a3w7GR+$(3PJ?e"-9ixGGYhB<!9I!%9Q&={4:tBg :OuQ4M2hM[75E!SeVHaUuR*iSY1LNZ
+ xd\U>2ZbnEwR^pN8?nQUqUY#Q:3GG9ex7/SJjO>`)
+#B92k[V / ~8T Y7,1A9o
+\GwFntD:XxZn_zD\^SgZ\= 8%,# Mw>,?`tv}TD ,+GOgUTj !LP5%\^9_7]nfCmo{wW *eO'o&Z:B$pP(XC YhwA&K'w%wD0#n
+ R CPOS"h/"xuCv-]Pxv{*2>=,B1\` LfCiUV] Q9D5
+*H=k<t}:/O=L2nRN_*\p#.Y/Yn/'WI/hX!=sFIendstream
+endobj
+1559 0 obj<</Type/Page/Parent 1476 0 R/Contents 1560 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+1560 0 obj<</Filter/FlateDecode/Length 1880 >>stream
+xXMo7½ûW t -;[/.%1%7$} K{(;o5]k_/OhY
+oUszRJ
+-/>Tj
+l.0q3U7qO~|b0_+dU(n56mhH&o5v3V9w\oIL &g-Imk-5ID^@jEL~5[TtZMtHiX;m=mg3Me"z`^8p2! DFIFi4V=< WX -vI>s?z.gsP I(^BexoRWQUvw^wsawXPx4~$rMd1 A# \ # yW'c[8Ud10FF 2S
+a|)00[ RQ&w ^,N ^^" mudJL9Z-JR{8I+Qs
+0 dxinL C.GI <^7>I
+R3HJ_C8MHJl8g@v-$!a|Gq,P>YQ'\[ ^^"IO):!luFr<g
+|9G$i|`IaiB<
+D  ;/[]]
+endobj
+1561 0 obj<</Type/Page/Parent 1476 0 R/Contents 1562 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F8 10 0 R>>/XObject<<>>>>>>endobj
+1562 0 obj<</Filter/FlateDecode/Length 606 >>stream
+xTn0+>%@Hczh*z(D*|w(-b(s#aD'Y%h2~X Q6|\(k0<PVRWv?xe4N. U>XykM@+^d N
+/ hT'SedtF <br|blR| HlZUCqNaVhEA_x4@3eu5aZI3=3 e L^hjq#!2)V2er{]2]D%&NV*-E/NKG6c-`#c7xDNVZ[a!*Fdlo!+B>9HwDU^%>LQFs`eZubVvr(t0X!9h.@E&l ksRph1 Ma^$P!u|[|:\<g-_}WkdT!j>L]!IvkauFmxqHh:I1Xro2 o
+endobj
+1563 0 obj<</Type/Page/Parent 1476 0 R/Contents 1564 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F6 8 0 R/F8 10 0 R/F9 11 0 R/Fc 14 0 R>>/XObject<<>>>>/Annots 649 0 R>>endobj
+1564 0 obj<</Filter/FlateDecode/Length 1347 >>stream
+xVr6+h%G6JJ@ (aM\
+LFßåôÄ_§Éd‚×ñ|†×!~­¢,|0ãäÙó›E y:" Dvo4'Q, Gu9|G aw_;} 3%[h0z#.&!UjWETxbLAsb8K|Few$Vc8Cu_P+EqgHS \V5OKln5j3+GN\L`Iim 2D'"-tcX X])9@5Z9D[,s,wxKE!% m+yN?
+|f
+ A1L_NTr {Z?,|CRX
+D+?k(OO
+Yy?]*kdqJzcwoW#w1`i[[ Z)J(k<uOU4!Z:whc6D/h<`7w*x5a*Q XfA-aIJ7 íY*Ub$@b cuZh!ii_4 #Ru
+endobj
+1565 0 obj<</Type/Page/Parent 1476 0 R/Contents 1566 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F8 10 0 R/F9 11 0 R/Fa 12 0 R/Fc 14 0 R>>/XObject<<>>>>/Annots 694 0 R>>endobj
+1566 0 obj<</Filter/FlateDecode/Length 1494 >>stream
+xWYoF~QQ<$Jn>$X@QyX+)e~3K z!E1%xI8 RAazO}p $7 &q f7n*IM}x6 Pt :x3x(c!:^cvltD9ND8#.!
+VVkus=uv,))"e|L*qQ{v)Shg,*&" Z hYR
+!KFONOnOOJ[hEI}~g D$H7E8 xoxA?MmF(6I*agmstNJwc^;$J.h^s{%=>U+~(EMa½ŒJzaYbVc?85;6v1`q`3VKZWYiec#tV-{=5YmqI'sKu56k#Vey$\)uV7meno-r?N]> =],xl#s@,>2_a;]º…«Z:O>
+vk]L)3&
+endobj
+1567 0 obj<</Type/Page/Parent 1476 0 R/Contents 1568 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F6 8 0 R/F8 10 0 R/F9 11 0 R/Fc 14 0 R>>/XObject<<>>>>>>endobj
+1568 0 obj<</Filter/FlateDecode/Length 1847 >>stream
+xX9} p3öL {PU ]Hj=)
+c.*/'OLF33*v7lD,b'k%on4jgg9JVE^eoW_n|0e8QrAS1f^xe4zO;+\ti[0KV/nD4*GRT~^ }%&r[c=(Hr  V=Y[%l<-l#B~P'ho%}0;#%|p KP52!S
+|n qx>=x6oO6097(sS M
+%_^+
+
+,6AQwWkNtP~Ο >£É½ÑޚªâŒVM
+$\6G!2uM 7y{h{h0%6$*gBh"n `r5rAy%)D0GC)
+W(EkXCte,-duLtg65
+G:Q}u+!\F r=?Dhg{P@p^M :Rb<DTU1s%dD=ctq*vq8\ dX;;daacBC@;hy.lN!d <(t-Ag A#Uf22pxR9=8CeI?o4r‡æ¿´UBo4FV`V2]g(R6@aK
+OJ'MyT_(C.(WZ(B2Ta$ Eu
+Sm'Xr OE=qoAB5,^< nqO 0HIcR.y.H(\?t7*k)jg fk-?u&;6WHN(6 $Ia1Q
+y&Fe}
+a&-i<2ÿ#ýØTMer?y
-[o74@H;undp}K@c(gn+yY'ObG|3)k
-.Z*SkP?GPHd (,5\#K%[99Q@(…0FJ0>92;Pm HH(_L[H-;+!7 ~^ E~%/\^^
-|'$X(€¢œWeSK%X8+ èÈ6kži*ÛXU8$Sg2Cj3sM[ bLTw! #@:Opf6TobNR W&&$t'MRJ"W:aVkV}8{qJYLlQ Zrd_{#Q{Y  3 n,4w9**J*o{D)*E)YgDV{EJyf 4sM(H d1kw2S`"TtTTkcd2@cS8pHGk"@' HB<#72r;7m8q] 7qw ~t@t;$(0D,0JBp*Y5uo4QV@G1&Kb*1? d o"k4K!m]mD
-!| AF`[v:IGi 6>$^~'PYHfK14Kv#v&7#6^Q*l5m*{eYazwo/bOP'/:
-Vv^d!EX:ns}^:H>(2y&;U oMTT]vt141KJ1 sVeo"{|L
-j5kX7njKKk)34kr$"oecA|R|tk0vmf­J]PIA%*,~FZj^ H a~
-S "sWÃëc ™}ö¸+Ñ2oLnqod5 /;767Z~htK,ZZL@~iZT-zC]2c5/lK5I!pDLZ&f9,vxWT,K+ss _j23rX!]6,Q#R^\z8PoT17[Q|11M>QP4k.QWE+8[`(
-WqWa \.WQtNMSF>UP!Lt^e![+L4e'p 
-$laLMkB)^<8de1u_~TqT b[t\m 5(l2JVk4[E ZkkPi_zMM!:\ }N%yR$k ^Y x}AYgu[\=(c EaE*r4/D
-endobj
-2280 0 obj <<
-/Type /Page
-/Contents 2281 0 R
-/Resources 2279 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2260 0 R
->> endobj
-2282 0 obj <<
-/D [2280 0 R /XYZ 85.039 786.531 null]
->> endobj
-194 0 obj <<
-/D [2280 0 R /XYZ 85.039 766.606 null]
->> endobj
-2283 0 obj <<
-/D [2280 0 R /XYZ 85.039 734.654 null]
->> endobj
-198 0 obj <<
-/D [2280 0 R /XYZ 85.039 529.7 null]
->> endobj
-2284 0 obj <<
-/D [2280 0 R /XYZ 85.039 492.435 null]
->> endobj
-202 0 obj <<
-/D [2280 0 R /XYZ 85.039 449.1 null]
->> endobj
-2285 0 obj <<
-/D [2280 0 R /XYZ 85.039 418.899 null]
->> endobj
-2279 0 obj <<
-/Font << /F62 1689 0 R /F20 1617 0 R /F15 1628 0 R /F56 1642 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2288 0 obj <<
-/Length 2244
-/Filter /FlateDecode
->>
-stream
-xY[o~Jzpp
-^fggJM=S$t=N$rC~7%4p(*MtrslvBw6)GsteW<rxFgGWD;9O.W3?v.[%<pH&Mp'dzmUi:MPa\O~\0U#*~14&I0F
-G7Hdea5|6@m3?qZ+}]ek
-U5mdxVLKYl5J8ekS4&laS_`0_Y] B+t}[}Jp8'gZp0J36Dm4851-.Ev8$Aub)_+b0y1j#"3GQ]snP tR@scj4jKQm<wSaH})F
-;e#bE$df)V8pcXhYQ6#c$"a;fyKKPo0gYZH+YRGsNd0L(~,->E)^=P#*N
-Ue+,y"ZAnLS,#c!8!L` k-BPYB:<Ytx$_LduE()=&rHAG&=*=Vgl.2d{i_$DMP $OvZ_9w$`fH0<"v01U](s=g25o; U 9UBwz,sjsa 8eIA^ iVEE,jL.S[).0i>rt'76
-G&BBL¹\ξ¶æ¡N"h_XWeKLf%x"(r6-%.t| ajMjz
-j6@]4œêÜĆ+a,$]bPWBuUf^t0)N(`M.78N9Y5OHP!X(n#5%O\9"HYZAY'*:+(+lUwJ({8X|)m<F)l<<bg*[\:9he %g`IN_ke3U[3q)0XEcej$`Qc{hS;d($E*l(D}9"\kiHS(=CwG!c%#^xtvrxh+3]&Y?*t1:1G3/¤ÜÒ؋‘k™R7_/!cae7crmQA[bc G0=?>$U0Zaim?4;j#
-@Pd7( *s~njY@n 2I-akC}-\gLx
-C+T Nz^r?[negn2Y;N]/ V0nt2CIWxHU-n
-s+F^V?vR,JL*J*2FH0gr$!E, %>>
-==VoIwYxQyo~o"0Zz Ì:³™ûA\D~ug+Kedgp3?=<~A_'%6w#vg8,42endstream
-endobj
-2287 0 obj <<
-/Type /Page
-/Contents 2288 0 R
-/Resources 2286 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2260 0 R
->> endobj
-2289 0 obj <<
-/D [2287 0 R /XYZ 85.039 786.531 null]
->> endobj
-2290 0 obj <<
-/D [2287 0 R /XYZ 85.039 766.606 null]
->> endobj
-2291 0 obj <<
-/D [2287 0 R /XYZ 85.039 707.789 null]
->> endobj
-2292 0 obj <<
-/D [2287 0 R /XYZ 85.039 671.724 null]
->> endobj
-2293 0 obj <<
-/D [2287 0 R /XYZ 85.039 636.266 null]
->> endobj
-2294 0 obj <<
-/D [2287 0 R /XYZ 85.039 586.652 null]
->> endobj
-2295 0 obj <<
-/D [2287 0 R /XYZ 85.039 523.489 null]
->> endobj
-2296 0 obj <<
-/D [2287 0 R /XYZ 85.039 460.325 null]
->> endobj
-206 0 obj <<
-/D [2287 0 R /XYZ 85.039 399.93 null]
->> endobj
-2297 0 obj <<
-/D [2287 0 R /XYZ 85.039 378.733 null]
->> endobj
-2286 0 obj <<
-/Font << /F62 1689 0 R /F15 1628 0 R /F38 2158 0 R /F41 2104 0 R /F20 1617 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2300 0 obj <<
-/Length 2322
-/Filter /FlateDecode
->>
-stream
-xnF_!b
-q 1qY[AM9ZMR0CwWUw]XJQFE? ÀüãLX` 4X}$H'"Y{?x\)</WQ{K\#T{8Jkw nO 7Xy1w; ggWBGA_%
-`0OZ-);+hLyBLn1i ^;h Ha! q"4*9:"\\ bK%~hFD<-U OOY{W]23aK"DM'X:=~aX%lJr QTy e[!
-"oL}my)a/V%\m(w@ADt.;eU $4
-833<F;zd@vIA(#) W>-+&,#GW3^gTg;)6} uF:8 G)a[tIT+/XwSf<ch : RD=lB0E[
-Jc)lN|n3 bsO$ ,3(zdn´{Ý™á÷°rxxõÇ\K96.!;
-d>ec%GFO ++`^j-Qh2Y}Z^;Q$ `D<qd :Bl,e]&;:ª<팦-‚™)<¬z¹u}2HCUTm[W$
-n;&t^Šæ•g‡²µ7Q Cl\|x|-uCZ(b;i3|Iw
-
-j\|8[MvM/ZzzE'dB9H3`C ZgrOvMO1XW`(, !I%[TX\ 7qc.u1hzx 2NsM/B
- fuW&xIw+
->7t%4Dl5 Gy8+-^t4j9O1bGXR#'( '/}:yz#`
-ÖEC!b9iz]ql}$&f/6.(](iYi(~ \]v\B|^.:0RxUh%'
-??N>OZ? _}W_U tendstream
-endobj
-2299 0 obj <<
-/Type /Page
-/Contents 2300 0 R
-/Resources 2298 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2260 0 R
->> endobj
-2301 0 obj <<
-/D [2299 0 R /XYZ 85.039 786.531 null]
->> endobj
-2298 0 obj <<
-/Font << /F62 1689 0 R /F70 2201 0 R /F18 2207 0 R /F35 1632 0 R /F15 1628 0 R >>
-/XObject << /Im2 2261 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2304 0 obj <<
-/Length 2491
-/Filter /FlateDecode
->>
-stream
-xYoH_^d V$ 6r@[+?H>b;}8DCs^^dD"K$
-/wf~{*ED~yj ^1 ,<`w5 4.~K<Ifhg(]xv| *U-aFP]=r;1SfL /fSa GfuQNw{ ] b[vH']k$z" H|,5oDÕ 0 ïûÌd^}Á²®0ìJAIhZ%N^a]0%n0t)sma[V_3u3v"uÛ —zÖÍ/ëÝ F7wVbs>n\(^n(zazh
-a@iG@%v3#BMFM |hJoo!\No?>7wO=zYg_D !mFG$~#zKyjg?lp0(V|{`m:"Q<q}f%$^r[~czQ\c~j_VqPt A/vlWl xSCYkI {!Z$wcNvaOduqlYO;SV!<rCcJI+CPP7z|X5N/^~+.ljS:$ !<OH\')O{b [L$$`+ku gC7 dpTOTRlB'Axw@L^(4f\Sb$W1$t$üÎäº
-¸oj$e L3u+Ar g<4$!Tn:f]UCOXj>kI%>s )^8G+u,a=_Z
-d\s/'g9%{f;dp,\V1 'h?aw{*9L+!K4/bMcUo!~we>14  NPC)#
-q1U~PRO7la
-)08;4u8zh$9h(rUWC71lB*YL,/rtE{+h+p &[Cd;%'W2yQzFFY#)_4}{iVxTZ)XR
-3 Sl]M/=SO|-ui{ b2rIpDLh,`_T) 8 pT\0>);c4RA#/lQ
-9D
-k-d`(} c;2ieHt)V;]fc3J2„œ›ÃðŒÍ·bp¾ qìqO% HomJ {pG$y,71O^_o)4Tp1Zhjf<w`)T:V` rnmPY9} $L1q<m-,2z%nA-xwsY +upJLUm^ dlrB8ik0v`LN\qKq +Z_fK`l#?.6G?z[mAt}=X63>}5(M7,w ckYZOx% xVNR@®èñyõÄÔ¨î ”F, #nEI\/-!WqPs[Y.x7i x@+$uB`zU_Lp-;U Dl%}< Fs!yM7A'3Pz0g>nb,{ddTyG?D7529endstream
-endobj
-2303 0 obj <<
-/Type /Page
-/Contents 2304 0 R
-/Resources 2302 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2311 0 R
-/Annots [ 2308 0 R ]
->> endobj
-2308 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [380.589 592.347 489.248 604.036]
-/Subtype/Link/A<</Type/Action/S/URI/URI(file:Samba-PDC-HOWTO.html)>>
->> endobj
-2305 0 obj <<
-/D [2303 0 R /XYZ 85.039 786.531 null]
->> endobj
-210 0 obj <<
-/D [2303 0 R /XYZ 85.039 766.606 null]
->> endobj
-2306 0 obj <<
-/D [2303 0 R /XYZ 85.039 651.298 null]
->> endobj
-214 0 obj <<
-/D [2303 0 R /XYZ 85.039 651.298 null]
->> endobj
-2307 0 obj <<
-/D [2303 0 R /XYZ 85.039 619.773 null]
->> endobj
-218 0 obj <<
-/D [2303 0 R /XYZ 85.039 576.904 null]
->> endobj
-2309 0 obj <<
-/D [2303 0 R /XYZ 85.039 547.5 null]
->> endobj
-222 0 obj <<
-/D [2303 0 R /XYZ 85.039 130.562 null]
->> endobj
-2310 0 obj <<
-/D [2303 0 R /XYZ 85.039 99.037 null]
->> endobj
-2302 0 obj <<
-/Font << /F20 1617 0 R /F15 1628 0 R /F35 1632 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2314 0 obj <<
-/Length 3243
-/Filter /FlateDecode
->>
-stream
-xZYoH~0c^[n<bf(HBRq~fK ,uWW_u|Ut8
-pi?Q%r{`pW)]/-FaA>|7}i$c/48.?^]"UyeÞô×ß?1×õÝGOBIouYl~__ 0,Jdx7w3 3?#?
-F+/h{4.Ks1]H6QQG IYB= n g-nI}aK{mi`J@Z|-3v@+i?Swu-6')6[1}<+h[*qfYtK?o&+G{M=e]tL^-ugc]Ct"n>VpT,v$I89%p/5rtUgJ+=j-.P z S7fmn_xwy3^(Vz{'9 84lzæV`
-k>?5K%Ms6S2p\e" \k?a-Ezwq7
-|~aw;G|bOiUk.H*gpj2f]s#RE \
-8/vi\?<4,V8Ix;xbUq)kBmHsdBk43bTc{$t-p +wpuow/'Vt\V5S>
-Q u
-v5-rz8b-[<d^QlO)NV` v%2VdpGbWlM
-Ht=}}BzfH.pX6JS (!M9C<
-6't$D9L4WOG
-FugAJ s 6^,[`G /x)g<b2J=?&s~dg0<r#(JusoZE~sZ AWe~s
- xZ@R?c: <&sJp9)Uk3~z%CUp)W2SS@lUf:1;M j E)a
-Q
-\Q7IS$""ÞÛȶµ-WhOQWA|}N>DTtH!@vP6GL1xgMv:IX5!V;L<xLLqU.9}D9Dd07@q8xIfqX|qqXqdRO{b!j<mW7'[rqo"Z¹3nzhʶ¯X%%6%{z-w(T& nD!*X8dA?
-
- !=]VJl 3y96b-m:vC~’‘Û!rÉ>ÍM6dHVvVu
-,^q)RR@>#LaEK]wE_h#'.-%ORzb| ,foS2TZKs-,W5zu=`L3%VtK\a#"<#|,CYv#gd@1y=+.{<Z8_! FY\_ERqXR|.us@-2=a)wHg9~j;WS>>8Tu;N}{IaIy3o
-q nW`C39,>Z+)>GmOTsT\m+lQN6PXRB5av]4Cm[JLC0!b ,|f!?
-endobj
-2313 0 obj <<
-/Type /Page
-/Contents 2314 0 R
-/Resources 2312 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2311 0 R
->> endobj
-2315 0 obj <<
-/D [2313 0 R /XYZ 85.039 786.531 null]
->> endobj
-226 0 obj <<
-/D [2313 0 R /XYZ 85.039 699.735 null]
->> endobj
-2316 0 obj <<
-/D [2313 0 R /XYZ 85.039 678.741 null]
->> endobj
-230 0 obj <<
-/D [2313 0 R /XYZ 85.039 552.962 null]
->> endobj
-2317 0 obj <<
-/D [2313 0 R /XYZ 85.039 534.09 null]
->> endobj
-234 0 obj <<
-/D [2313 0 R /XYZ 85.039 461.332 null]
->> endobj
-2318 0 obj <<
-/D [2313 0 R /XYZ 85.039 416.785 null]
->> endobj
-238 0 obj <<
-/D [2313 0 R /XYZ 85.039 289.831 null]
->> endobj
-2319 0 obj <<
-/D [2313 0 R /XYZ 85.039 260.427 null]
->> endobj
-2312 0 obj <<
-/Font << /F62 1689 0 R /F15 1628 0 R /F20 1617 0 R /F41 2104 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2322 0 obj <<
-/Length 2480
-/Filter /FlateDecode
->>
-stream
-xY[o~PpEIvcE(/
-IW=!)S83gyOt2b8 o\( wC<7rK4W/ "ba/q8cg83_(n_'ly]CWa˜„ea.‘sDrt]Ox_y  I<{$&@Zz6<gfjBo w[hA*_Y |Ycp vZ:$vn+n|P< OBb2/@Kq[~qXLx;m-b:}IT2a<a]5<It)2U>GixL[?,v).)\~qHC )PCppy*z<pM 2`s%aBQ+<b;%= >,Z ~60I.skh/eiH},?4
-PG14Þ#‡ë+WR>gW<bSAoyl(ufj
-Ux9.+i0qzWWc=f&=Z¨püö–ÅN
-&G`mGDuHXl;xOvt$U8@LX<81>2<W]79:&BF:r D6FAj&I(TLK3:.X`{aH|~3V6#>agiHayol ?p*arY
->{Tg279|(? G k8:7 <n{ld<'rnkj6}ScXr)`B7pQ(JL
-NT /\{E``'P>bT
-8_E
-N@wF4M"'v#* @K\E#'c+=N%XBTYnNb!}Gp!g@rz1\03<R:pkr{9~&S~Hr$YIi`cV(j|m5&0isE|=wR;J
-J)st+V>>e5L.Za]|hOQ!lqE [r PGX^v^;ROQ5-)kxxK]ZÊãkU*E*}3.!
-Yrv"endstream
-endobj
-2321 0 obj <<
-/Type /Page
-/Contents 2322 0 R
-/Resources 2320 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2311 0 R
->> endobj
-2323 0 obj <<
-/D [2321 0 R /XYZ 85.039 781.388 null]
->> endobj
-242 0 obj <<
-/D [2321 0 R /XYZ 85.039 437.555 null]
->> endobj
-2324 0 obj <<
-/D [2321 0 R /XYZ 85.039 414.237 null]
->> endobj
-246 0 obj <<
-/D [2321 0 R /XYZ 85.039 277.233 null]
->> endobj
-2325 0 obj <<
-/D [2321 0 R /XYZ 85.039 258.361 null]
->> endobj
-2320 0 obj <<
-/Font << /F62 1689 0 R /F15 1628 0 R /F41 2104 0 R /F35 1632 0 R /F20 1617 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2328 0 obj <<
-/Length 1614
-/Filter /FlateDecode
->>
-stream
-xX[o6~bHQ@K:][,qQ]h[R*a}B^""ys?$)/5BKR%tzHz >R#2Z( bS82JNa$2I/&B)X{91]?@o[^^f^#-*&_Oafezt=uX9:Yq*) !@L/bB7%/sw5w@j;aj%yPtN
-YHH&mq+3u,vh$P<C
-Z7ZJ)7=a&4;gVLU$t_a
-w5sR
-fZqAx[WP4|2+Z((teA~T&%t*5\ 9\bxT=M}J"6{ g \~/Nw-&EK$m9U{5Z?>q_h#~>\?% Z8y^`[!!KwDqSW(3R9)Mq QCPE
-endobj
-2327 0 obj <<
-/Type /Page
-/Contents 2328 0 R
-/Resources 2326 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2311 0 R
->> endobj
-2329 0 obj <<
-/D [2327 0 R /XYZ 85.039 781.388 null]
->> endobj
-250 0 obj <<
-/D [2327 0 R /XYZ 85.039 761.463 null]
->> endobj
-2330 0 obj <<
-/D [2327 0 R /XYZ 85.039 671.062 null]
->> endobj
-254 0 obj <<
-/D [2327 0 R /XYZ 85.039 627.524 null]
->> endobj
-2331 0 obj <<
-/D [2327 0 R /XYZ 85.039 595.999 null]
->> endobj
-258 0 obj <<
-/D [2327 0 R /XYZ 85.039 236.956 null]
->> endobj
-2332 0 obj <<
-/D [2327 0 R /XYZ 85.039 210.81 null]
->> endobj
-2326 0 obj <<
-/Font << /F20 1617 0 R /F15 1628 0 R /F35 1632 0 R /F56 1642 0 R /F70 2201 0 R /F18 2207 0 R >>
-/XObject << /Im1 2193 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2335 0 obj <<
-/Length 2615
-/Filter /FlateDecode
->>
-stream
-xYKs6W\ZjrZdY;sJr%bF"=$5*hOaU&n4K$ ¤“8ñT$<p(w?\Y8twa: ts;9F3wlV/t/it90:3t@'N'
-d4lNtP>="4=Y#V)?F#T|} LUFq('$FZ{_JHG4"^w1<4n*[m_b1hy)Wi A'\TW*HO{J"SKF@rBYNg @-4ZD}zn@#S W5%ZS]m+ki=%NDz\J{2;L6<T\ VVL"MZ, CI6 [\y0e(}yiS!umT88*#
--O
-2+ifQKsC0l) QjiT~ G5{:Iymm8eK(HQR0
-m'Bab4,^sq(%_!_ZH}pAhCVa!õP?<Z¹KS^}=?Qd%\L>lRy7B_ szxU!_0qbgj¼–+>c¢ž1¨ëlÕr¸p¨Ô‹ß` ;S9}[V?UT,dkp4R4bn5Ȑ$»”w§¬4ZR1 E tOrM3bB8+Pt
-1c'8M\#}&Epz2r i0fs+ OV @RHyT*E[!Ec^+ 6uxqN)Xy N"~4u(:sjBkQ7OYzaQU 7xCG!
-T/X%qpuI@Kt6`^U6u·5ÔÃD-1yTå@_0JP~DMT7'#yWiTD4^t%y!.R /T;IH/tt)":
-%GH9c!\Zt"OepWgh=^
-t\2TLh nZnqM
-T*hUYR
-c_.T{7>d/}im+BAoa6>U_ !%#(K]E1d!N7IwN* pkpmT)/M|^&²î“,Ç£…üÐÑ<lG~r\yW^xE!GoF_L[}0W7#wX!v
-endobj
-2334 0 obj <<
-/Type /Page
-/Contents 2335 0 R
-/Resources 2333 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2311 0 R
-/Annots [ 2337 0 R 2338 0 R 2339 0 R 2340 0 R ]
->> endobj
-2337 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [489.95 435.981 512.306 447.67]
-/Subtype /Link
-/A << /S /GoTo /D (ads-test-smbclient) >>
->> endobj
-2338 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [111.316 422.432 183.828 434.121]
-/Subtype /Link
-/A << /S /GoTo /D (ads-test-smbclient) >>
->> endobj
-2339 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [214.276 422.432 356.796 434.121]
-/Subtype /Link
-/A << /S /GoTo /D (ads-create-machine-account) >>
->> endobj
-2340 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [380.57 422.432 476.48 434.121]
-/Subtype /Link
-/A << /S /GoTo /D (ads-test-server) >>
->> endobj
-2336 0 obj <<
-/D [2334 0 R /XYZ 85.039 781.388 null]
->> endobj
-262 0 obj <<
-/D [2334 0 R /XYZ 85.039 393.439 null]
->> endobj
-2341 0 obj <<
-/D [2334 0 R /XYZ 85.039 364.035 null]
->> endobj
-266 0 obj <<
-/D [2334 0 R /XYZ 85.039 274.847 null]
->> endobj
-2342 0 obj <<
-/D [2334 0 R /XYZ 85.039 253.854 null]
->> endobj
-270 0 obj <<
-/D [2334 0 R /XYZ 85.039 135.198 null]
->> endobj
-2343 0 obj <<
-/D [2334 0 R /XYZ 85.039 103.673 null]
->> endobj
-2333 0 obj <<
-/Font << /F62 1689 0 R /F70 2201 0 R /F18 2207 0 R /F15 1628 0 R /F35 1632 0 R /F20 1617 0 R >>
-/XObject << /Im1 2193 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2347 0 obj <<
-/Length 1224
-/Filter /FlateDecode
->>
-stream
-xWKoFWUQn)-M
-fmb Ÿ¸wãMR V+^*+:%V&uv ,
-v< ]
-Zx w}z$>JHTB\CpxJjIg'
-O^^~A\$P!Tc +Mo[(/d)iH%=t%3l<+'K*mIWVl%E^
-;x}jUx}J
-F[T%yJug sjb1]eJ, =^3p#5s%&2)S,@b[Xn!wpxNume{+(6 
-ywMv82.VJ;8"T~:L1Rwry*gq%0
-endobj
-2346 0 obj <<
-/Type /Page
-/Contents 2347 0 R
-/Resources 2345 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2311 0 R
->> endobj
-2348 0 obj <<
-/D [2346 0 R /XYZ 85.039 781.388 null]
->> endobj
-274 0 obj <<
-/D [2346 0 R /XYZ 85.039 693.417 null]
->> endobj
-2344 0 obj <<
-/D [2346 0 R /XYZ 85.039 661.892 null]
->> endobj
-278 0 obj <<
-/D [2346 0 R /XYZ 85.039 607.594 null]
->> endobj
-2349 0 obj <<
-/D [2346 0 R /XYZ 85.039 578.859 null]
->> endobj
-2345 0 obj <<
-/Font << /F62 1689 0 R /F15 1628 0 R /F41 2104 0 R /F20 1617 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2352 0 obj <<
-/Length 2458
-/Filter /FlateDecode
->>
-stream
-xYIoFWf4U Gv`X ,A&R7@mU[ZSgi:;KR4=T/B ]d&L0gY@o_zga>%o^QxWZ):N<7{yZ+X"U^~`&b: V^"d3%p;k *3R+kV(3Q;fy.q.
-{%=6<xOS~R
-@-T;Tw}xwzJAlb3?47V0j[?p+g1
-D[Q?4-e}qi}q# Rv:TIP&23-+Z0c[f{X^Cs/G-,(d@h0cU7o2F(S9<5|N%Vza#Ij!XViGa8uDZ>yXi0{'p8q!
-FvOGXic)-(j
-Qc7.
-)x[ "a~!H2&N8x\Fv
-?gfPD:gn*_'3HdaevaMpendstream
-endobj
-2351 0 obj <<
-/Type /Page
-/Contents 2352 0 R
-/Resources 2350 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2360 0 R
-/Annots [ 2355 0 R 2356 0 R 2357 0 R 2358 0 R 2359 0 R ]
->> endobj
-2355 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [230.917 454.294 282.431 467.195]
-/Subtype/Link/A<</Type/Action/S/URI/URI(file:smb.conf.5.html#SECURITY)>>
->> endobj
-2356 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [203.74 413.646 268.218 426.548]
-/Subtype/Link/A<</Type/Action/S/URI/URI(file:smb.conf.5.html#WORKGROUP)>>
->> endobj
-2357 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [289.289 373.301 378.732 385.294]
-/Subtype/Link/A<</Type/Action/S/URI/URI(file:smb.conf.5.html#ENCRYPTPASSWORDS)>>
->> endobj
-2358 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [250.286 345.9 339.521 358.802]
-/Subtype/Link/A<</Type/Action/S/URI/URI(file:smb.conf.5.html#PASSWORDSERVER)>>
->> endobj
-2359 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [285.619 61.367 316.703 74.268]
-/Subtype/Link/A<</Type/Action/S/URI/URI(file:net.8.html)>>
->> endobj
-2353 0 obj <<
-/D [2351 0 R /XYZ 85.039 781.388 null]
->> endobj
-282 0 obj <<
-/D [2351 0 R /XYZ 85.039 761.463 null]
->> endobj
-2278 0 obj <<
-/D [2351 0 R /XYZ 85.039 646.155 null]
->> endobj
-286 0 obj <<
-/D [2351 0 R /XYZ 85.039 646.155 null]
->> endobj
-2354 0 obj <<
-/D [2351 0 R /XYZ 85.039 614.63 null]
->> endobj
-2350 0 obj <<
-/Font << /F20 1617 0 R /F65 2099 0 R /F35 1632 0 R /F15 1628 0 R /F56 1642 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2363 0 obj <<
-/Length 3269
-/Filter /FlateDecode
->>
-stream
-xZoBThr*p(8w].pw(JBRq%)R Zwfgg~j8Q^$a %x~#=SH_ wd~ooY3{z.w?~G\W?;~p  >_ (@I\?0?^^&gJ@s[Xzha^N(aS6 \x O+p ])x):TpWl7^ky_aY}e9Y[V (}
-- zJmH-UI=j` C>UNsNpe4cTPU]q$zcNSw-x=MW as+h*e_$w {TH!.[@ZA2<5+ -hb9w-p&YCGzVusZ&I>!2Gz>+?l% XMFG'<[Y_L&dfKXuyX-]lc' 0-daSEUMfVF{ulmWpevuxWM|; s;==++]Z jD u*{+b,^n3gp5D07YAEV*K| XabKonvuKM pBDl-EDg\øèŒ åBV0* <$Llvzyl9(l  je5mV$ CNL= E3^x\)e]fek |DsVb)IA K? T
-!S
-A$\ax)Cit7xQ</Yt(KyD#Ci
-x=<{Nta=VQY^z>uzgq=SA^zZQ]x'X|
-e2Jt}-;49
-b#{Xd$q/E,y0.- L5M+X 7~]\
-$qQwq(Mlgx>\J+Xb3CV/2>kv%4r#Q:u')8wx)ynR ]
-ÝaDlkQq`RjY[ Vz1'SSjBB:hFdJ6YsCHJw f)} 3<sO3V.-^VPnqJXxp_}Þm[ÉçÚº±ì¨¨ŒÕXCY6jW ].4Ü»vFPCU$R%p5G|Th.$J`,VYVD/cn1Ce\8
-JJ<>z<)(BGw"m
-XD# 6@Ex-+)ik_}995Clw`L)M;_|z +YnL&
-A\vtlBP%][d3lc5%m0^VI{k3\}@ I@F(ig+ 5$a|P;qm|r&p3,3,HSNGA/~T YH6s2/JmZ7]8OgIAomI`=0U SX[sYU/ L0&F
-$uB2zLFB[ -}~_wm  Zomc VvuO4C:h_LioCjjrta2\Npg;:Y?u8S#$_Ãä}f±ƒƒýiÛU^Tssp?:%]@mkY
-w9^47cFg @)endstream
-endobj
-2362 0 obj <<
-/Type /Page
-/Contents 2363 0 R
-/Resources 2361 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2360 0 R
-/Annots [ 2366 0 R 2367 0 R 2368 0 R 2369 0 R ]
->> endobj
-2366 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [262.823 498.973 345.582 510.663]
-/Subtype/Link/A<</Type/Action/S/URI/URI(file:smb.conf.5.html#SECURITYEQUALSSERVER)>>
->> endobj
-2367 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [215.436 458.326 289.861 470.015]
-/Subtype/Link/A<</Type/Action/S/URI/URI(file:winbind.html)>>
->> endobj
-2368 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [201.985 140.627 255.917 153.528]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.linuxworld.com)>>
->> endobj
-2369 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [319.668 140.627 442.172 153.528]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.linuxworld.com/linuxworld/lw-1998-10/lw-10-samba.html)>>
->> endobj
-2364 0 obj <<
-/D [2362 0 R /XYZ 85.039 781.388 null]
->> endobj
-290 0 obj <<
-/D [2362 0 R /XYZ 85.039 596.451 null]
->> endobj
-2365 0 obj <<
-/D [2362 0 R /XYZ 85.039 567.047 null]
->> endobj
-2361 0 obj <<
-/Font << /F62 1689 0 R /F15 1628 0 R /F35 1632 0 R /F20 1617 0 R /F41 2104 0 R /F56 1642 0 R /F70 2201 0 R /F18 2207 0 R >>
-/XObject << /Im1 2193 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2372 0 obj <<
-/Length 234
-/Filter /FlateDecode
->>
-stream
-xmPN1 +2&C$g&lpTJ NbdPI,A>;4E:e  P^9QnjwuhZQ~;B}\tBaVy+mZdlNHqjavj]vZ;Y2:/0$>C/Yz[)B(XérVm|~c\endstream
-endobj
-2371 0 obj <<
-/Type /Page
-/Contents 2372 0 R
-/Resources 2370 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2360 0 R
->> endobj
-2373 0 obj <<
-/D [2371 0 R /XYZ 85.039 781.388 null]
->> endobj
-294 0 obj <<
-/D [2371 0 R /XYZ 85.039 542.44 null]
->> endobj
-2370 0 obj <<
-/Font << /F20 1617 0 R /F15 1628 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2376 0 obj <<
-/Length 2209
-/Filter /FlateDecode
->>
-stream
-xYo6_ZI}Kq)b mh[H+Iw>HI EKh8$7B^42o[/Bo=?,*]%2tnL*o% i{z2 DyGr7zRI'`3P6;TY!3
-lVOZ=-]KZ#l,dJXiW&Y-]uAW{"N>u}(qQ* tD,e.%%°ChW&w<</a]e Uuy]oG>a3rKa@Izg§™¿i ò^:ì¦ýRGmkc5zcY72-75E;iy_8t3w+G+f
-,e2M'+ Dk!~;nq_|34eIH`|A$g a *8OlZ/;2Y!a ?C1RA2f;FCuJ!$Ev:N"m-ORy a(aL"Id?c L98F$/0dE.Fe
-WOD_BOmQ=qNv$0wer3#M)pej%WyF|t{7UWa;,-1Xh
-;tDp8{lplTt:D4 M
-] f!9lZt e WH>G)7 `V<Bysz{(F7Q9|.
-'HwLhòß¾|¶Ò>•CBBe 5RAxss5
-aC|Ajg({@s9`R)]IQ
-5q)Y3lw'R")q"aF-Cwp^Do?Lq>`sK#<qmi%8X4HM-(G9CnXm#8G.tPL~ 9<3} )8Z2I^`3.K fZ K !o =L{78*#c!e*E~o#wv#qnr{zWML1y[
-
-
-2EXg^m U8?GGHw^0MYF11zq2/Xa8 fP"'_SG % 6/.a[VyWJl9~Q$\:?phh,.R}=\9 hF/W16nM[mM5yMK@%qM*W
-{Ubpk9<7nOFb]qMah_C f^2eS>y
-_a(-bvf*b(\CctzW!1D^ER@<x=endstream
-endobj
-2375 0 obj <<
-/Type /Page
-/Contents 2376 0 R
-/Resources 2374 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2360 0 R
->> endobj
-2377 0 obj <<
-/D [2375 0 R /XYZ 85.039 781.388 null]
->> endobj
-2378 0 obj <<
-/D [2375 0 R /XYZ 85.039 761.463 null]
->> endobj
-298 0 obj <<
-/D [2375 0 R /XYZ 85.039 761.463 null]
->> endobj
-2379 0 obj <<
-/D [2375 0 R /XYZ 85.039 642.137 null]
->> endobj
-302 0 obj <<
-/D [2375 0 R /XYZ 85.039 399.889 null]
->> endobj
-2380 0 obj <<
-/D [2375 0 R /XYZ 85.039 375.338 null]
->> endobj
-2374 0 obj <<
-/Font << /F20 1617 0 R /F15 1628 0 R /F70 2201 0 R /F18 2207 0 R /F35 1632 0 R >>
-/XObject << /Im1 2193 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2383 0 obj <<
-/Length 2630
-/Filter /FlateDecode
->>
-stream
-xr6_R
-g(7WuTx Q,pÇ~'L"S54GgB~eu()y(YkCZ}>unxZ$ l kj $*<S]5%p_%m-MnBF.) CUULc#WbewR'IUo}v=0#kEHzzr1:0°ž©w€yØ﫺=ÓnpÂÀ®ª^éý1ôƒ…òi^ãzHE>pj* =j
-Yx))sc+
-$`=Z^;TEADo?Ìcßù7OpGC@b|i0lL'|  |;YP%oPV-db'(_=3 n4i|=FuDWz,ypS7k')b
-v2KWT|O;n,d%atDk o!CHA ÒޏŽ•pH+Ec 7<$XyZ@ K58'7z!-/e)i:CdN{{[B,!3vgME [)8TJC-
-8=/C
-:*'Y1\jwE+_>w^|[2^vnvY&"[iO G"\ iN!OZ(B/*<v>{=2y>Z~b <y}hy0-hV*+m
-LEt_q \s*55e7JGVz` pxte
-  ` u.Y S(IqU6.-z@P3 8#xG^W7ubI1Oe2t<Pz(FeP Zk%s-[3j "j|2NpaKEFQR`igLmE{Ke\L,]$
-m o.5 8'W^H^U^gaG(R ]CWAnU<cn!`
-8/P?N1*XE"<'P”‘¾õƒ1V):??#SY%xeK2kvfxW>q-iCIHqFS9 HD/Eu4C,A
-¿©ó€Ì\<Ûrê4;Ìȱ]ΐAN yQ{'Bf7o!vo LE^M-6eh:Ø-y?¯Òs¾}½ºa
-endobj
-2382 0 obj <<
-/Type /Page
-/Contents 2383 0 R
-/Resources 2381 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2360 0 R
->> endobj
-2384 0 obj <<
-/D [2382 0 R /XYZ 85.039 781.388 null]
->> endobj
-306 0 obj <<
-/D [2382 0 R /XYZ 85.039 408.357 null]
->> endobj
-2385 0 obj <<
-/D [2382 0 R /XYZ 85.039 381.742 null]
->> endobj
-2381 0 obj <<
-/Font << /F62 1689 0 R /F35 1632 0 R /F15 1628 0 R /F20 1617 0 R /F56 1642 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2388 0 obj <<
-/Length 3839
-/Filter /FlateDecode
->>
-stream
-xZKsFW {c'Q6R>$9 I
-
-ltiIdvqy]aya0Ul/U ]q-nCbRLkS.g/R?$-Gy Tt-+h{f$klnkV{kZeB_ K=v=Q Xd_xP@j[Y„ô
-Imteg0R52L2~Y*rfa tb@rxHQ6p1 :#b2ï'Lpo/h8P^;v'GvBe&tRF"ae kvP.4(])[Y gzhdS+:^\pwrPvyCY#11rLO\_$5dYy26{5[cCUKaqh*/<hw}U[Bj9#[\phmO qEC^DDJ"f\5d\4›ÔÃÚæ'7£m鹨;iÓüqŒX)8((b8eWW,"7km4"j T2}X:ŽE8A q_I2 |a<Mi(tn_ <+K320ÁëUSj4h!0l?3fv4r*EqQp:J'\Hf2X$05of!qJ #Cp
-FvO<}A~9s@R
-_DO'KC7NaZxk;O )3eWI,/^#8
-qu g=?[t)$p`R(Ya;
-coRwj Y]djGCuH,NJz6Pv3W/y_{)lP!,`8sR
-DjS7<uQb&56Zr03#XMI$1PT0&X[3GQ 16O 2f
-NEL8r6B-JkGE"
-z5 rn !t7[#Y#J|@*ÌτcüþIV_I"R d\` E3 c5F$ D b0QBudTH c^'CKxr1f@r.!}#3.Z9Pw{jMgETTaSU>a:#1h ,B);r0H6DL^,vt@pZsaCZv$^ {]OH5o9cWH 9rE jnBRXuW Wo EzS3Qe[Q,Bk]<'dL"D6R, d "I/BB o"h
-(%i:dU^Xt6H
-G{0f{185|A4th]B}!6?k(EzEjg2^,g%g]KBVXO6aGk2g`I
-2U.klv3x;/KXY(F\)%ZS)^PwM{DS7kAj iL
-P L
-h\2/a ;ŠœÑ^G`"+4E(g(G~Lx.F7i]Jv*wa%x9amY3&U8 avc`,P@%H !"t|G,2%f,%yN tJf2#>B<%*"=lIQ2yel~q 'h#fTLa814g<z9qeRq14",jV3E;B
-b%<.endstream
-endobj
-2387 0 obj <<
-/Type /Page
-/Contents 2388 0 R
-/Resources 2386 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2360 0 R
->> endobj
-2389 0 obj <<
-/D [2387 0 R /XYZ 85.039 781.388 null]
->> endobj
-310 0 obj <<
-/D [2387 0 R /XYZ 85.039 610.001 null]
->> endobj
-2390 0 obj <<
-/D [2387 0 R /XYZ 85.039 580.597 null]
->> endobj
-2386 0 obj <<
-/Font << /F62 1689 0 R /F15 1628 0 R /F56 1642 0 R /F20 1617 0 R /F35 1632 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2393 0 obj <<
-/Length 2682
-/Filter /FlateDecode
->>
-stream
-x]o6=o'"Q>
-nK%.rvd[T|by
-Dp8|,pi?Y~e,Y(,D#D|b_o>-(r~w;7Ah]0-~wwu}q2w8x i3W_?[ d<8P> fk8g lwq$ X%Ja~NB=q'ASos{2MSzFhU0a{En #hG rd^)[a #25K-W@f+
-th .{l cou=
-X cVWfMhX<)^RB%~QviIG)h/kM[__8LR\Z ##Âix·e×U{=IQH~b [5U~o1'w16`XylOHFCGG;Z R"E
-JF#`/qW~Si ]Mu5h[E5*PxBJF.lds~ l{jY@ g fwQ@
-x@ P{?k<,N
-N 9AE}G94_0cwdY92K( HP?rbJ B&@kl6otj*Nw+{k'='X er*ag_]HoOZhc 8[L Le- 
-[lO*WT,j( +np4L q X\3%DB1*v[ oypQJUeT{g=8`9FC. j~I12^iyM?XttgPD tK*e H*aHJ"\u3|=JS
-/t* 8oigTrE%XKK6L a&;NfKA=rQW@=;m5WW$# Rp.;_g 9
+$ X_/XjW*YUZjaf9OFx Fd#n{kFXlW6T9%)irJ}R0;Xcd.N:Qj+]"m"ßáF f;O[s×­ta=Xzk,_@^fs ]rEf>p-DJtJ%B6qq^{=fbw{y +SCQr`tR
+endobj
+1569 0 obj<</Type/Page/Parent 1476 0 R/Contents 1570 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text/ImageB/ImageC/ImageI]/Font<</F0 3 0 R/F4 6 0 R/F5 7 0 R/F8 10 0 R/F9 11 0 R/Fa 12 0 R/Fb 13 0 R/Fc 14 0 R>>/XObject<</I16 16 0 R>>>>/Annots 697 0 R>>endobj
+1570 0 obj<</Filter/FlateDecode/Length 1636 >>stream
+xWko6_q[D8oI vm\ Dl$8$nuCx_QD}D4it:
+G4}8;:!e4b OJ7G_pB(QFte7vE4[_fY}/t)R2:KSXI\ ZN^I)uA9Y|K+_f\ %hLm{D ?
+A7Q RG$ 2~66skf0H^04ij6\QpGS~nJ4s<H;~sV*Xc#sEZ$XR$KCOiJA "u ]4wd]+X@Gy =M=GMo.o(Y^wp+6P)?")TA7Nj]^
+0v7躀v͇]Hz2M*?DZhSucC !2;{>QuP;mUV NA}[<//}Z-[Jd[.RG P't6W5,&QmQc)]1M
+q 7Z2 wo} y8PAil(" OV4@{nXy88U `6pDkT} Lnab}I:Ylt
+?h;m6Z
+^%f&kLf+y6wmwr%:_'?[(>9 QhZjSk[7lK w
+NU?? oSkk2n9ia&sr_v* A?`7N]&
+^CTzf
+=C|F[o/Hy,Zzj+9h4 ~U:1`=£?®Þ6–P7nV,=F!tp} hYT/3m_9`KzA8u&_2!!&f`d p[-`:[LgktR9 u*NO66I
+;U)qb;mRaridq ?+D
+endobj
+1571 0 obj<</Type/Page/Parent 1476 0 R/Contents 1572 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F6 8 0 R/F8 10 0 R/F9 11 0 R/Fc 14 0 R>>/XObject<<>>>>/Annots 700 0 R>>endobj
+1572 0 obj<</Filter/FlateDecode/Length 1493 >>stream
+xWkoGr[HCC>b|a$;dfs VUE3yh2Ofp4M4U85NSIx:{+etnh4;W
+nywAJ'Iu=+#EtMzIoDRimCy/auDY& v+IV.+jd]mM|}OU8"&ej]n$Ro4OI_sF%HXOd.ukSi6ZJ: Uu.I"hc$(o\!?kH!3<d-!6pm#q+d/?/}kvc#(pQQULl`,)b)[HjDF-/.28(@%ja?.%
+WeI=eR,Q Iú¦%_ï'ž&Ctp3@^y(
+F:-r1mfK12)>r.!UghÚ Ž|%ó®Ö ýH'n
+ngP/r p,
+endobj
+1573 0 obj<</Type/Page/Parent 1476 0 R/Contents 1574 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F5 7 0 R/F6 8 0 R/F8 10 0 R/Fa 12 0 R/Fc 14 0 R>>/XObject<<>>>>>>endobj
+1574 0 obj<</Filter/FlateDecode/Length 1954 >>stream
+xXmOHC=%wPPA*tR$.&gvpV*gyfF4MttBIq7:K~t2<a4ikIVq. 2RVWZT™’UTG^mgSfiJLl^Q!1`Q&kU[g2eW|vp!DgM=FQ`Df1nZlT)ZgeO-+}I?NB-KN)"$,Q
+(:|EXf3goD!ª“/w>ÃÇ-ÇÐ,z±H)K
+vbvOsJOh21~+sI`SZXVpiIj
+/3tGTxis40GL1"7wzáø.ú=îäÄõYEQ?4i-_f|B@SH2k!chPv1ˆ7u,’GKvJ
+nh £I}c#?>_REQôÀ¢Ç}©% “,Sf¹±¼,³?‰Ò8ïGakRZ:])RMrM
+E:hD~ VJ fA6C
+*\#=
+Ra#bui!O$iOXB0^q\[2tUJI u[c_;#
+`
+5 I~[yYt1*(, gik5D- |< bv m2xU"w=T\>J,yU+QsNW
+}V/)V 
+endobj
+1575 0 obj<</Type/Page/Parent 1476 0 R/Contents 1576 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F5 7 0 R/F6 8 0 R/F8 10 0 R/F9 11 0 R/Fa 12 0 R/Fc 14 0 R>>/XObject<<>>>>/Annots 703 0 R>>endobj
+1576 0 obj<</Filter/FlateDecode/Length 1953 >>stream
+xX]s};6m}Xy4MdHPBM,@FY!:pwq ~'lAYuq6Y|)^VR z.KuLTd6MfUI5V+Noh5lqX]Me|ot:uEmV_o.i2M`-VKÚd㻆
+e]C[IR5I+qtP0ypxwaKu| C(#FKvuCWt4-eVFyNx+vNwk26c=H"<A)  ]?^) f;
+ 2
+Z6u-$vBH0eiUoh #}ly9\RMX|b`
+Aa+9UQ[U|È\.ÉgšúèÂ1ÇßpŠ¬ªfäH!8<Ws%(rmwM8Sc}_AnR|(J96s2(+3 ?K.5MPLWEH0)U$@7?Z.Q67+Ts"_U5}o;Exu f@n<;P|hP htr&=
+GCV's>lh /jM[@Q^a+T 0#
+k*z2k)Rx'1%
+yO - jczJIms+c_U R{JS's' fA/q@ls K;mUO[xjh,p3 (&&
+x=@#?yZ#~~"g 1{@03a'j 6K3F~` wUS
+c>n.~ f#mendstream
+endobj
+1577 0 obj<</Type/Page/Parent 1476 0 R/Contents 1578 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F5 7 0 R/F6 8 0 R/F8 10 0 R/F9 11 0 R/Fc 14 0 R>>/XObject<<>>>>/Annots 712 0 R>>endobj
+1578 0 obj<</Filter/FlateDecode/Length 1893 >>stream
+xWr6}WP7v;i#ig T
+G(
+OXRy<>|98{v^.-c;nv1'='EJ_/s8qdt>}C'wB 8}eJG=Agi8E Jh'Ao'az*@f45*E)Gk$PzOknM 'S:'Bb[f65%G@?ehF7432aYMENx2bjzGJaD(~K&
+@Vy; EEX#qSAp@HOOl4J4'rN KG:
++iPn/=s/,POg%JS"I:Xv,mLZYP
+b>wp`l_vT`YUP)D- ^YjFWL;]P$4_PV*QETg TS[U
+8so5E5O\2([l!f/kG0p_`:\[SoN['uUnl6(j29Cm{Mp r/o w~vmgy TAG\*Sq;Vn6@3SFH|{f<68L25–rVYd(f}s5(L{:X^XQz"PkxKoZ2`h_M^i#}1$*LS*aj:(@'Qp)4H@ U?iA**Ol,(xb;ØõV$5Uq  :inÐ{²BwF+`0h
+Y{#"'ZZ8I4?jKY_3;eByNYAR^>Ppxw,5sh*8XUTEG05 JF#Y6 wTJ
+endobj
+1579 0 obj<</Type/Page/Parent 1476 0 R/Contents 1580 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F5 7 0 R/F6 8 0 R/F8 10 0 R/Fc 14 0 R>>/XObject<<>>>>/Annots 729 0 R>>endobj
+1580 0 obj<</Filter/FlateDecode/Length 1906 >>stream
+xXMsFWRRR"HI%ZR 
+b ..LS(W.39|xS/."S"%Ta=
+E[fRJ_OF4'0>j#|s':J 7v 4l}ylYQcl=js
+! /&tDc9rdpoL#wvy{gS!hvg)fd$0&EjrwQdC"@b>U@Rrm]iR*s78fy){H/PfV*Uk-0Ju~+Y,XBp9!;}W>Q9;
+vW3#|DZ
+Sb?>'qET0YH6oB)nlS!~^lS LT8`P8q
+r|@s$>Lr04-% NBw!Ñq莻J1H1T \ ?Yx ]tuu}EK+MO.)7ZLh0]~|BRaG\JyaO,'x.endstream
+endobj
+1581 0 obj<</Type/Page/Parent 1476 0 R/Contents 1582 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text/ImageB/ImageC/ImageI]/Font<</F0 3 0 R/F4 6 0 R/F5 7 0 R/F6 8 0 R/F8 10 0 R/F9 11 0 R/Fc 14 0 R>>/XObject<</I15 15 0 R>>>>/Annots 734 0 R>>endobj
+1582 0 obj<</Filter/FlateDecode/Length 2188 >>stream
+xXr}WtM^i%T0$gpg_=L1.l$0Ow{oL#3 MTQ6?_>E6tMi:foqMcvy}va%9^;v;8Vk6qqyARѪè_W{u8u=Or;)\F~}E)SezjY}h8fVe(x/EG;GS4*6WxM3OT5g6o]ǶÀ°­±ª×/8ÿX l4&%L*[Zh=C7qk
+\#4/f#d#"?
+uM&Z<:kU^9x]'IAlL`pPY*:EVc_
+WT zc;
+n|XRei9hÛÉåQ!%-'?-lTQPm
+:Ulu3L$fwG_ zZ=wM(7z=!Df@gK1@‘Rz L+\u?!!XWmJ^jxHphqC9Y 70Pf0Mnj<L 9[$@% 
+/ MF>v8*aA V bwlcŽ;G h'6xajL~G"<5 *u5S+>=ql7A )Xw0Uj26MmX
+EW4\RZfA%P ;Ur@6J=5/d6
+rBf!m?CS`]05 g5R#^XhPQ*":kohNf;=Ñ·N|T{I? su$k-ROP@4h!bEvsIo?Mj
+qsQL9e2$_:H{m$!U Z,SwEak4CZnC
+bpQ{?Â)òu„î±Ú¤JDgan$@Y5@4^0*G#t1nN[i1e dAY%=8/1]MNTK_af8W5@"y/C,i]8$8
+s ,+xvUm-Jc[oy1VU]!uO5 m' IQ.G78=F
+Q2NI{LtNCjwF^o]  k
+-k;W5Mo|y 4#Ou
+endobj
+1583 0 obj<</Type/Page/Parent 1476 0 R/Contents 1584 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text/ImageB/ImageC/ImageI]/Font<</F0 3 0 R/F4 6 0 R/F5 7 0 R/F8 10 0 R/F9 11 0 R/Fc 14 0 R>>/XObject<</I16 16 0 R>>>>>>endobj
+1584 0 obj<</Filter/FlateDecode/Length 1970 >>stream
+xXnF}WCEK,iQNV@/+rimLrgfD;HA$^vf3}=G4ÓɔÒò`˜ i|z’Ìi2Ÿñgük4å_i4Kq0#b47>X_Nh4e-3!-sv8P^g-&gB
+{g+=6)K[qtQJk6QfKe__4ev(KS{\VUF Mr }2UfWmg,y\tM(h%"~4pbt8% O,U
+!_ n9!mwp::]R^QYip7r=r^ZxBbkYnW'!dpianA[I!T+4UYOn d
+Tr60-`X5i"#n avR5i^nW(pc;
+*PNTF2=&;7TRWw q"1|.+tmPB{5{dS
+
+51al.#{0#xp}cP}r9{
+['?vkKaMpKlVMjm/qASD=zug7</2E-%t{4r$,yMdI4'?rX
+'Un --&dm?q!yxR&#'P
+hTihx ;qKluhAzW\}Y"Hgj
+1s&[79=I-<.a1|*H {Q/$A:<{|k[`bb.# U/)|)NBg4\`2 u~{}_Py# Fj2j"yyy~ZT;s~xWbu6X!L]3B4.VY2 3iO1 oJ2 FxfBhZl*MQ}% 9z0Ä¡²`‰ˆ{£)ې*œ…Xbq=ym4<'!,c lã7²*JJ@(@!^EdxzG&s/XR KM ȏ)…{,T8
+endobj
+1585 0 obj<</Type/Page/Parent 1476 0 R/Contents 1586 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text/ImageB/ImageC/ImageI]/Font<</F0 3 0 R/F4 6 0 R/F6 8 0 R/F8 10 0 R/F9 11 0 R>>/XObject<</I16 16 0 R/I15 15 0 R>>>>>>endobj
+1586 0 obj<</Filter/FlateDecode/Length 1834 >>stream
+xWioF_1uaT$ZeIP>@VQ1UK+}KJ2E;7o_B_HN`HYpJ#V/Na0Q4 BurŽéZw?šLFpGfDaH(!gxJpHwZO6S1_|CVI\+I$>HWTjKX*jci!Q]UR!)%ESVZWJ+6[^JXU.I 
+}rfa8+U6F-5ue*O{KX4u'RT>x2.ZS "-\&*Me%KKiOc0Z')8B[d2] Rb@l&X%|o$]9\ hq=tPmP2(B8)1:;'ry/ke2`mO-3vw *8UIat
+lhLV|3a)a4FL{[6zt[uW%$B' -8K:42+e7+MqMi@ekgfw Y#^W ;$r0QRKc 0UR3) QMqJ \h~w}t8?K_hfcg^kU!™ðQat* >
+es+P[nEVZ1xMr<oli~?k3#"1 eNaeJ-3 ->k+YN>LUX:^3mPq{pX%l of""_G]QFSmE'zBXJfZ N`zzL(FY!4i\CjQ0$+BBA4 F8m-#JW$9KioA.}hq 3[ny:FJwNT!!HQ*p2]eZq6R*X-S
+FKFq{-
+6v/(V@D`V`Z'IECa#`T<c5aAZe2N?5J/ ult'j(Bpq'tz}XVy7 N&u
+ [FsoA 7]b[jf9xf3Yg v]ApXz!
+w<s;% n3L9~Z{\GZs?Nz :Z^9+v{t 6ny;KgŒSdwm
+#G
+ |\5`o e,qb"<_2<QYVkZcx@3x"K iP8(? zy3q#-
+|w^LVcÅh2
+&x¢Å£lÒM
+endobj
+1587 0 obj<</Type/Page/Parent 1476 0 R/Contents 1588 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text/ImageB/ImageC/ImageI]/Font<</F0 3 0 R/F4 6 0 R/F8 10 0 R/F9 11 0 R>>/XObject<</I15 15 0 R>>>>>>endobj
+1588 0 obj<</Filter/FlateDecode/Length 1801 >>stream
+xWaoH_17q$ECW 8Rq'^'Klo]7D];n]N:*Jy1wL'hDi4|cI789M^WsGycZde:"%h‘<yq ÊªrMn#)k]FvB:it buF%N4*GU^I;3KK7UV Wis.h8>C^( -6%Abc&Dn2W<{]J"B0dU2#G?E@bO q__va<L B+Y:K{VNeU)[j^@l:"sc~<icZD
+BlQi*xtlFS
+}@mUYIYgo,S9I-Nn;m(#3 [vtbLTiC=Q'xF("( ZWFp>?aH8DSo<!
+UBhLTh93 "Dyt{,%bpG;V@a7@\x9e&*py'x{\6 /*~e)"iJ*=X[N[--<I082(1X, 3p,IDTw{Fb/am<"dA{OV!8|AXZxFQ
+1}H"UEN XhnF=("=TZ}DFv!fOG ^3c[@oTbixoIB- ,9` OL7r
+m'_pVz^)h:o_.deIU
+Ax^y&l:`9s-N G endstream
+endobj
+1589 0 obj<</Type/Page/Parent 1476 0 R/Contents 1590 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F6 8 0 R/F8 10 0 R>>/XObject<<>>>>>>endobj
+1590 0 obj<</Filter/FlateDecode/Length 1764 >>stream
+xW]oI|h%A;N)p. CEh;k13qz>tLwWWW<tqBpD':3W7g4M MJ LCMA.-mtK?.iQ[Hj4VF&7(+;:H{8|1q0dxxG?Y5^[:RqZZjWVApy!U V#1p&$jr8\bI|4FD-AFldJJUcP8^ qz&=JaOUnpYONGi{Fm{nuRW4 Lr#>\h^||E@EUmR
+ %qp`
+SU^I>U>PF>0c
+] |B 7XI
+9 hdGnw–®·fáÁÏMOU,AN-`@.A)IIMxzP[`f"_bAWt!^XFJcN/6,yArQ/TQ-=@e<ZbUp&n3E/n:/.>:N^\tV
+M"r]F^}v
+DLwq <$Tg6v˜8¾ÛÝôùéóŸÞÙþ€$dyÁ„rX) @sf`G/l;8 wwmWkW]0YR']9IhprN []x;)P%dPDxdg@}
+D/_m`[ößàŠ»]ƒÁ*`}u;ô»€‰o(>Mx4QkcyZ|.@&t {yv^\
+k.*>6.@(9;pL0t1wQT Oe /Oi25ÓV:oN8xnbtF2^a57)5Azu9/j
+endobj
+1591 0 obj<</Type/Page/Parent 1476 0 R/Contents 1592 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text/ImageB/ImageC/ImageI]/Font<</F0 3 0 R/F4 6 0 R/F8 10 0 R/F9 11 0 R>>/XObject<</I15 15 0 R/I15 15 0 R>>>>>>endobj
+1592 0 obj<</Filter/FlateDecode/Length 1923 >>stream
+xWOH_1tVJ$@VT8ZrREILl&ofm'*]+{7ofh#pBq~Fh&/v8DO_F0~4dcXM~0E|<f 19,!=,~5N"XkZ$fzF_];|j
+:g0q'~)H oWJkiOG3JV+fW
+)"-bx
+~^TCk@|M!&t!uze0P^DvWhQsB7eOkW$+JUz,13.;-X|14Y&b;EV
+8hbc^Yt7 ART $Wvu~MEz3b*St40(>ypdf#d. 3-KuSfhX^
+oC|5tQUk<9Z(o9 CMgjT|n^j t qD $>X|Xd+Tm
+j]
+KX{\ q?u "4:/[z+nk@,v ,sc‡Ç[ízuÓ ššÂÝ×ï¿|»™]þsù_S EwvnzKi$X"BY{v]%l0
+endobj
+1593 0 obj<</Type/Page/Parent 1476 0 R/Contents 1594 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text/ImageB/ImageC/ImageI]/Font<</F0 3 0 R/F4 6 0 R/F5 7 0 R/F6 8 0 R/F8 10 0 R/F9 11 0 R>>/XObject<</I16 16 0 R/I15 15 0 R/I16 16 0 R>>>>>>endobj
+1594 0 obj<</Filter/FlateDecode/Length 1889 >>stream
+x}WkS* [%T{7!<.CK#<iF;38>G0*9}ALCihBiyi48d<xBsC(qfNgS|NJ?}4|]zFqL9MfSZdSCZGh%4J?5*h+4~YI%Y4K8R{%bK2#cIX+SO%xrSfOl,Kk_GSiejwLZHS& qhytR*]h6JZ\<J5Y_!#QHAx/7ZrHP8cmHxRs\E-JI55J*Tpi2s~@Z<IŠµ27Vh -j^
+eH0 b?'tGXiFPl4EQ[n]Ri`6Brd : @5\go@'=COEt6m;DIb&68
+GU7jt5|(=u,t4jH2~\* !z>ŒÆókãüû”,ãqËJhNz+j+Q$bP~Ub/o8I '>Za8(j!C*)32p$|ZU#p:w JyHprHF~-<j%Z2XM=K9W;A,X3TLaRim5dWyj5An=3}'<]O:oDGINx,_nw7E9A 1 sS
+d gh6dx_ 8Fq4L&l!9U;7w#*&QURg6I0E@|BR RHE%1;tf _'Kw}F?a
+Sa,RhCZQXF6
+KnOz\1n_0R_,4
+1z^f)D JEa 0H0X*i2G>F7qaSK )P7Oy:6ye'nmkze2RcBT|]Qk8J\Q1Jq?j8H
+endobj
+1595 0 obj<</Type/Page/Parent 1476 0 R/Contents 1596 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F8 10 0 R>>/XObject<<>>>>>>endobj
+1596 0 obj<</Filter/FlateDecode/Length 1455 >>stream
+xWn8+pI44rMTt$*f#*IRUmE('?ggt3Zr=;]W\J*gwQR%a)%J_o'QWZtTKY7ZUVvo^"duKxr@$zQJUIG)T\x05Go.:!-rd$)4FkQXNu pq&M=I @Q,R~2|KF!*kj-kO[a*.[rd^ \|c~F^Jjnh=ikG;J_
+*%l
+Q`OO#_}a<*0=32}
+I(SptSp3' Qn
+y[:zendstream
+endobj
+1597 0 obj<</Type/Page/Parent 1476 0 R/Contents 1598 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>/Annots 737 0 R>>endobj
+1598 0 obj<</Filter/FlateDecode/Length 1504 >>stream
+xW]oJ}WTRInA<,{c{:8UUkf93tMt28>Vv38F#:L>e4Fx i4C-%-lHs|}F>i<<q`%>\&}²šÎcK ?W]LNzn]:MqO8yW2Ld Aq]L 3h])KR)R$*_ pqB.5`bJw=ke(uH02,Cl
+|:[V,RIe×üàRIp'S%#Hj!oR{}Fnh9XWaE_{DVys$IJ
+%^+l?t'
+a l$9#FE,
+`e|Ok2 W
+E4}4Q8 *4)`[jX@=38
+*T2IFU!\ +1L
+]B=rk8(Z'}  ?wdj/n?p(&|qni'u-DF
+Q6 =?JBO=eClqFgH_=YG^-XVcBQ~Q+aw~G
+5 !ikr2D7^|<3a{/ v HGEuAj)
+1vG`+6;\ N,u@ lh\t&5(-{F‡*&a–d;
+H4BJt)_ 9h.-C6zi[)9L~0q3njG(`(?;;¾žî¸/ÿðçA[X'? FQ4Oqz.|wBendstream
+endobj
+1599 0 obj<</Type/Page/Parent 1476 0 R/Contents 1600 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F8 10 0 R/F9 11 0 R/Fc 14 0 R>>/XObject<<>>>>>>endobj
+1600 0 obj<</Filter/FlateDecode/Length 1666 >>stream
+xWnH+C$ >eD$Y~V2M"0"in:H2h"iyOr:'C<_eg/g2| '>dd jwYD[;|n,sIJI-
+]}0 c p
+f. <1p{9~P^vx+ -jSu&k{7!ax}K%ksb/YnR)Z_Uvov:s`<Jb!sJ#JeY2WSRQ
+%<@76zu
+nc)6mU[b( }vh%pÚÃIDXcp)y Zo+6(5!we*;1qg!r.tVHM+gO\Si#h%,`gJ?_ BIViyw|~ *FzQcmNCR-r{{vC2 |Sl.Fd
+2Pe{?@8;Utn[j†1fV5g] uf-W-#87@
+Z1 gh8-nW8oTbp("PXr V2dmML@D9,2m3HA E]'J{y;> $Tol@=L^mfu Fdv6$am sR`eL9Io?k8de
+endobj
+1601 0 obj<</Type/Page/Parent 1476 0 R/Contents 1602 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F8 10 0 R/F9 11 0 R/Fc 14 0 R>>/XObject<<>>>>>>endobj
+1602 0 obj<</Filter/FlateDecode/Length 1126 >>stream
+xV]o6|Xb8p(h6PMQPeN"7KIN( N3<b+yB3$YG .J*,,J.WScZ|l1UN0*;[Wfm4RL)yCDR2|)WUDR9j[QUwO SZRj,-B;Y)Z'd,)2zS u-m/WpnUs[hxm0GY4edlNqs%*
+U[(8VAIWBCpC # =¨`K-(8r
+ D5Yb=l/ 4
+endobj
+1603 0 obj<</Type/Page/Parent 1476 0 R/Contents 1604 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+1604 0 obj<</Filter/FlateDecode/Length 1014 >>stream
+xU]OF}Rf'1!mH[T==)m4Z
+s=m?}h[ bLSsT$ IPd6i
+d;V%eIIZ,)
+UD<4y^fG&WRi4RZ}xhJd82Z[C2EF?c3_lCF"X#j3{"83!>q9-@JtGx62f] 4N7Ybr/0:*ePab<aGEmJ
+i/;3ADeJyX8gJw{en/tEwQd
+Ou>)K%REZ+e;ELz`8mbH4WFq
+endobj
+1605 0 obj<</Type/Page/Parent 1476 0 R/Contents 1606 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F5 7 0 R/F6 8 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+1606 0 obj<</Filter/FlateDecode/Length 1296 >>stream
+xVmo"7_1KSIJ.]:5`v 8{7U}BhY3<3_LugM~7 n?O,(]|n-{0CJn,i9V-LYZq;aNT6=n3$9OjY)=mMiIYZ*"I\$~yp&+Ij`|%F/N~iuzE
+V:GfQEc=;XJ ;\F~ 'zl*_+|X n#{dPuHDJQ20h: c6gI
+.62@);_1h\Rj ;CQp02,A9BF {XA"R"iJ/8pPP! VY:4J( -UpZ8s^G7~2aF#=ozn¿¬/p ¦¡÷¥çJ[?O@KL^\&y=sk£uƒŽ¤z…±±ÁHs<뾙†Á\X^^YDnQ `d9 aH T/.b09GQ?#7;P0x{lO b"4^i?*;eVSG wp
+xcm 9L6y e[9x.k b. b\t|s9{kx^za
+endobj
+1607 0 obj<</Type/Page/Parent 1476 0 R/Contents 1608 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F5 7 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+1608 0 obj<</Filter/FlateDecode/Length 651 >>stream
+x}_o0mlOU[:i6i4 !.o:PstEH'&(1#‰6A<8|W,p>|B"HEKPy1X
+,mD1"I
+~V.UwhP!h%xF2)hz-JHt56{hM$(Zil[dT(WJ7$,6W aM*Tt1B^J
+endobj
+1609 0 obj<</Type/Page/Parent 1476 0 R/Contents 1610 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F1 4 0 R/F4 6 0 R/F5 7 0 R/F8 10 0 R/F9 11 0 R/Fa 12 0 R/Fb 13 0 R>>/XObject<<>>>>/Annots 748 0 R>>endobj
+1610 0 obj<</Filter/FlateDecode/Length 1399 >>stream
+xWao6_q0e;i tDl%%{GR"X R{~4c(d/y$`2'#LI\fw,cG,dJY6 i+oYYww
+@<C^.4mg]_ÎúÝ4cÛñ<³í,c[¿ò»5vódÞÝí¬áyÄ>N/W7 |Y/iUdK>|{' -Zj-HXtHz¯êñG*t%Tla0qa%4}bjl#~VD wtA]h4:@3vpemSI:vAQ
+\3\E&g4IDs|=9zE8(HpNV(rp/
+.. xrR%t
+77U%}],C`p+O.@©A?, *lOq7ZV/x" sm\XZ$%@Fr6
+o*z\l_.cs
+3Gv&-ˆ ×UWMn+Bw!iTxxb0u;6
+46ZOKt|vw5b`Urt2VhP_VLIK(ldcdyPE*Wl}Kvz6!_pz2ÆZ2~VQxp8-m| -"hoC% oO
+endobj
+1611 0 obj<</Type/Page/Parent 1476 0 R/Contents 1612 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F5 7 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>/Annots 755 0 R>>endobj
+1612 0 obj<</Filter/FlateDecode/Length 1734 >>stream
+xWn7}÷WL
+[)SWX1M+N:M5oSE_soWOx!vuLJnTpw{EQñ+ â ”)½à;Ør¹1žgsí=}F6^6=h|mz0=?<7k} Zv~sB4B[xm7S (c/Lmyou&LNvnVU+ES#yEkSjBMy*plu;|CV[AIgT[WQn6h”6W
+i7Yv9Ldq4Mn~K;.X'EP*Q|&
+uNGhCD|j4M[8]di9Ó¦Amt>.RCE'}Xx~JI],^9$Q}h.~J_&-"rr;G"qPbIVZ3++ ; ,z <{bb8BjB/Os\ ")7#]qp87)Uw- $Jz^SXr4Xv @$lU x5<jkgdK^/YEZ (vR+}
+7ZGh31MSP"P`!
+6f8SkP9q<lN9FJ V93faBdX+25¶.ÀÏN{AW%,`I=>O;*TxSQyxB0G~a k`pj{6K7oeuF=:y8u,,;yoZ':8\N 1pactv*f*5 2L98JVJd.l({1 /k}|;-w\Gg_fn4868ÜÌm]cºã¤päA}F1'mJ[' "+MKP8`"uqWvzN
+châûÎ}
+µa½=R?5D"hblx#1HA5|/q4\$fp]Lh6â“C72o8Yl>@8OlK y?`endstream
+endobj
+1613 0 obj<</Type/Page/Parent 1476 0 R/Contents 1614 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F6 8 0 R/F8 10 0 R>>/XObject<<>>>>/Annots 760 0 R>>endobj
+1614 0 obj<</Filter/FlateDecode/Length 460 >>stream
+x]Rn0+1W)7N
+endobj
+1615 0 obj<</Type/Page/Parent 1476 0 R/Contents 1616 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+1616 0 obj<</Filter/FlateDecode/Length 116 >>stream
+x+2T0
+endobj
+1617 0 obj<</Type/Page/Parent 1476 0 R/Contents 1618 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F2 5 0 R/F4 6 0 R/F6 8 0 R/F7 9 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>/Annots 805 0 R>>endobj
+1618 0 obj<</Filter/FlateDecode/Length 2872 >>stream
+xZKsW!`x$~J§*•DB"b`
+L,A`3iY`3-KxjwN,qYgs4
++^1)\Z"oeL+vWkYX9K}Lj4 "5FSC U`llKv,:riq^Arb]1 vE9U vOY`Ag``W1X5cW~vbf_(~\.X,@1ZH* 0X`1(_`#QXbY1$bFY`;AX,YH#va)DWHL"Ø ŠH+` w<
+f#X`1bbXI(h]q0^p!o`3>.EV0(Qa)6 vcWd 
+v#ègäydƒÅ5CR +$.D)/9!` `Xgrd]93.,JIHC2[rsN[A/E)#5dJ#RTX`sX
+F0#Y1Xt w(thg) `G \I`q{TQ`W+f8
+K7U vpT30[ÂR1jV*cgdD.[Ab@$J7rDabp=1*XLq`I `$Gz]'O1=bD~Gjj=WHPwz(FyVBY;/%e9#9`^ab0= sT vl)"`Nl
+
+SXWwN`',4^X`WX`>f8Y,Jh7~d}h&;=|x$Vn`}/pG2FJ#RpyV0}2w?X,HN B{h ò?ªU w+ Y u=+;^`¨öñÇC##5Ze"k>TX/?y-?2@I!S&),`$iQ12BM\+AIHHtAT1X.zifSvZl&+,WIL-y0DQs"k9QB8<r156y!$iL"7m)o rvFa}h0
+A _ 9_[88 >p'~
+w]t>rG|Zz %!_nnC>\r}o%Kiy7hG6 m]^m&j[k;y ’#0ŠžLSgd-6]}dNqG_($swYEq omc(NsZn0hpV|~h8P#Q@>QFIH2#<"OwS4C]lBe?kS, 4hH`& N
+I"|_? h|Cu}H\zy180~w|leSlyvQ(H!už={^6½-žmÂÌû?ðè,TG\I4bmMpsSg9)Ox/{i8[4:(pLN3G8L~ <;>8: 5-bZ9n`F ,w_MSCUn8)vH| @V tuFVh^d2hZN2pA=u<T=)O[O?!k^hC"}H>o WEk6GxR5-#x7_/yq.äÓ²þæ#^äì&dù·¿)á¾wžÕo$Ël…‹.È,¡Ÿî®þ~õ?î‘
+>endstream
+endobj
+1619 0 obj<</Type/Page/Parent 1476 0 R/Contents 1620 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F6 8 0 R/F8 10 0 R>>/XObject<<>>>>/Annots 857 0 R>>endobj
+1620 0 obj<</Filter/FlateDecode/Length 2545 >>stream
+xYr|Wc*)%Kde+]+DBvI R}9rv_fH~"W.zw!gEB/rsE# w. 1`8H-ÆTUzx1#*lf9+` tV5g 4 " Y 2;GaPbYv,vqBsiD=`yY$Y<Ezy`yf1
+Na j6D9O<-MsKHXy1p* enD5iCs; ``z6,>iX*g$MXLxe0t5{%U4`]9K,j$H31}`Yq,k0#Z+YvdNgq@ vB{2fg0^*YfDF8Yz1rH/ G@IwK05P]deSX> A$' '.@0-H,h1XCdD-qC^`+T
+LzLRAbVFSe>TS,!Ia1R"3CS4DB$p92ce)b%\)H#\A '3&8S0,zQ I]A S15|P*']HQ<x4%5~1uxfbv3i#H#):yDIo\CJ{CL81xN9|{CpPob&9!FN"wJ$?K.g'{~Cf4a3^4b2y98+8sGGQGf@(Dbc]gCr enYN~KQfIx9'' G'G9~[nO?c"z n/"CZ#nZw \1Dd~>7 OrwOUn /}Atrqjq._6Cnkh: c\!}>m`$l6u[u.g4{IaFlN4_]0cKe/P]7rlF\;PY{<m/^<\IKpC5M%mBK\\oe|>]Knz~q*MaWCL~wk'nQrFe9M9- Jk)e4ikwM~&Hah/om%~}y9~oK6{j&CJ2] O1% |xb?vv"qy[9SUT eG>~owky@m56 >0 /wVauzhbUtssJ"zXvm -vZ-bk]XSG}n[=g P^8»ïºmžë—C'N;6|~? {;Dy_2b+o=("a7qyoח»§òC|Lo? i<k_gzyIFi&]xj*Qfxr(6-==1'N/iqq>"s#=?vwu2?3y2So_xuySn4wee.h:]Hm@/ayJ[_]uendstream
+endobj
+1621 0 obj<</Type/Page/Parent 1476 0 R/Contents 1622 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F6 8 0 R/F8 10 0 R>>/XObject<<>>>>/Annots 901 0 R>>endobj
+1622 0 obj<</Filter/FlateDecode/Length 1756 >>stream
+x}XrF+$AS#Us
+oLG6,r{IH26lRvvl*Ko&"<
+pNo}h~nc OL0Hp #:C#Ml(m(*
+DW ]*aQA.J4Rwk{! ylfeL)d˜­È±
+3â³®XY!+0^XfD` ^âS)E6_V=&QL0cU-Y)dk iffEk*L@d9@+~b@P#e6e|
+ 'O5gl31X<;fG-|HnME4+r`=pX<S" .V qEth9j Vbfz2Zx[A
+b*S8)[LV6$@Aw<T`S(*/
+!E2py3RAp Oc%4$s,.^)4YU?afMclalW/|s.glnSu)ox9AÓnËmYMHcY}+o`lz'|{v[SnkSun4 RuSG/g}/)@ojF6c9oRALPkIY}yrhyRRQWPtmwnF^ 3])4 \u]CvnG4/6Ci!s, uH'|<'3|[,go=ulF-
+endobj
+1623 0 obj<</Type/Page/Parent 1476 0 R/Contents 1624 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F1 4 0 R/F4 6 0 R/F8 10 0 R/F9 11 0 R/Fc 14 0 R>>/XObject<<>>>>>>endobj
+1624 0 obj<</Filter/FlateDecode/Length 1286 >>stream
+xVr6+DH&4n/ hH%@Hi;m<Ia*bZ%(mt[I{!Y~^RXjM->h'pJgta-iMrW %)P?z'  e%qDE(8%(E[C\)<SFjB+[[2:CR]%=@!k@1B/C\
+Eq\\TL"+u:" i8;uPl@JKT8Bac%ÛBX5_2uMSc'L3<L~cd Z8viK!m&,!~N2e1|>vpF_CVAD+G0iA8b;%N89vE9Byvvm!q8D otueB;d`1NpT ' j{A#t-=^o0rUs; =@;B*<^#Fo| /-.(9Z
+8"TwR`0S?4Ejq:8)`IoB<R5pRb@l#kz_-0wbJU=d^z f}endstream
+endobj
+1625 0 obj<</Type/Page/Parent 1476 0 R/Contents 1626 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F1 4 0 R/F4 6 0 R/F8 10 0 R/F9 11 0 R/Fc 14 0 R>>/XObject<<>>>>>>endobj
+1626 0 obj<</Filter/FlateDecode/Length 1614 >>stream
+xWn8}W uXSlnu/y%b#.IRen/h*s;g~^h3ZfIiu5M9-+<_+)/Eb6_|~s569,+d)mYa {$c)S.+L/$Uy
+R*,I%i>Rj*|){q5m$J/4NvU?IlH$tF; O\=r$"qn/Wi]
+9I L T$t+Nk{i^^=dA}FYta|B|S9Ei(7p
+kx/me`)FCp\U87)
+X%}aH}wbgEE75sZ
+uummD
+fHP% \
+}LJ8K] (KCn+;_M@k]J!pDbuUWQisA-9`AP(
+C Kw W*D0_$(ni=YqW@_/HGi 8Elg-J+ @P rp
+bcZx-@ L>]z u#Y;"1mQDgMT=GT ]OcYBj1sU#eer a}egS1C[2mZ{M2-[;N5+H\UN-c]3R
+VFMl_^[7*]<eh iq
+_NRu@y_p\`W1?(@U$n«×‘Œ/Bh3^G\rln?*xg70h0^M1 ]-Qj+~/Aendstream
+endobj
+1627 0 obj<</Type/Page/Parent 1476 0 R/Contents 1628 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F5 7 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+1628 0 obj<</Filter/FlateDecode/Length 1607 >>stream
+xW]o7|÷¯X(uP[_v%%H il7RuGIOY,yk6aX#wggwgG=G> ([u]:u}: ?+i~t9=\uM1CNX4;*2jQY4Wl~9)<`h~K:(%IR0clNKPY$|}ssV\Vzt~[#5U[<&/K[FXv8H[#
+Gn9r~% YCkcA1[uDM$i;(x{0PZMfez[f{}?suN^l~9'$ 9I+-2RH IJxT<y0mS!9*rI<:4
+ NS%X,
+mFL!cE0
+;(
+fI
+ 'bn X@Etm[KJgIVK+@zvmJ<+v +,lNf'D]krF,UILZv{Q0$gRcv;-yc<S sB03PB;jDs8%TCY'EjaUBs#7QTqNRr
+/6HsB7#\*-@XKMtNd$ zEaygQb0?nU.G@~7<0v{
+`i_qTLv+a [![q`.X SbBgX*`RaxC> awq7c$-2b sN0%=+8rH:$(*f]`GY9`k\\cD
+&+aM\SFb~SF 0b0q|uB9dX07Eax…e]lñ1®°™ïÁmÄ/.Á÷.§ýZ)V_Ahbo$o\vJ?(Jk3DGMgl.3>VhG )ixMo:/-ÒÖ›Çì÷|3 ‚R5gooQT 'Y8I2gi{z`{)L F
+endobj
+1629 0 obj<</Type/Page/Parent 1476 0 R/Contents 1630 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+1630 0 obj<</Filter/FlateDecode/Length 2027 >>stream
+xXr8}WtdT3ZR*E$
+@w>}Gc.h2> Gt6%H*zqtyDhQ%SF#Zd'<=|ym4MF%u[UEXv[|?`<^O,3IB5Q7N^JtCsix[;KFo?:CéBO*yr
+t \~vkl2/n?H w)ZXn6 /]/Pt4C l%Gv;GA[JN3PYa]s$zKElZ#_+}b7h qJ?:BaW@: c/2u<H O*F!}-8/ir  ì3²g¢àŒ%Àdä8¢}z@7H1oy^Y:>/
+%j o{YqH? jKS$D F9F1 =|L#eK*N"Lkl*R37¶‹ßw « C[F V
+(g~7/Y)N
+Zn{q
+` TJUhVhJ
+Ta0p%BzC)@` P}YJ|T<z7.|aUE/7K ;E??2h39_/pQV.q<)N+z4'pi`2ap1TNZ/K(O?)7?J6Xendstream
+endobj
+1631 0 obj<</Type/Page/Parent 1476 0 R/Contents 1632 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+1632 0 obj<</Filter/FlateDecode/Length 1698 >>stream
+xXko_18HGpQ@Vo (VRkrw%-&M;"8sPic8/U+QR%h8(}[$ *T)?%3s'x(Y+~ed9)M tn6 Gd,/ 6yt5M$M-4}cHir>#:K#:#f'3J;j&yns|_DVZ*dkDZ e]HCP]3$TK[[!5\-5]kW
+DhM ()O:a!n- $.ig|. )KEXl<E@Z(F_7'K:c7&#Q3&(P7)jP
+7 7,}9I2:Yh^£‚à
+endobj
+1633 0 obj<</Type/Page/Parent 1476 0 R/Contents 1634 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+1634 0 obj<</Filter/FlateDecode/Length 1606 >>stream
+xWn8}W MI}5X-1‰TEN~ov l9sfKviihp1rI {9h O\G`;w:DTPv^&m
+Q(0d3+ ZZ &wmy+](DR"*d8y-[M,b5’/"ÍI*IJ[DYPVbC!wSuvz Ntr =~t{m,"p7|8q
+iNL\U0n8}0= '*J4;r g Y1RM*E]{_}"i);@O|V8&c:;qE-r9m)[ MsIqISA($y
+N"^)h8}9-9
+ 8: n~BY0s;dx}7rgKo}S:6kKhG=eo}<&i`|, SL:>,T#'h@WqKAz8"ZLhW 4y
+endobj
+1635 0 obj<</Type/Page/Parent 1476 0 R/Contents 1636 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F8 10 0 R/F9 11 0 R/Fa 12 0 R>>/XObject<<>>>>>>endobj
+1636 0 obj<</Filter/FlateDecode/Length 1773 >>stream
+xXn8+.fl'0d=&J-6TKRS`$ }sei9.jIYu6Kf\-W?_>Mg6[969l[q}16?ft1%80'g`K23 &='eFZKf?eM;;?|]-X>=[wmuABT`e]Y'RBK_U*J|7N$R,'yM U"+U)G"5iQa\%2O$K32IPKRL-Áñ>¾#£ÙÔµ­º)­™;Èɖ/"sTIW 
+D\J q>A>RITTJM;WfM1OmH%'ifYSW'<@e
-B:4B7&<PZ W~O
-TA<9F>q`_D| Yf?v?)C^np6q5PY%|%J#VIz\T4{ f~s0 ÇÇW"9{E-<=hBr~\s/d8:AZ
-endobj
-2392 0 obj <<
-/Type /Page
-/Contents 2393 0 R
-/Resources 2391 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2396 0 R
->> endobj
-2394 0 obj <<
-/D [2392 0 R /XYZ 85.039 781.388 null]
->> endobj
-314 0 obj <<
-/D [2392 0 R /XYZ 85.039 720.013 null]
->> endobj
-2395 0 obj <<
-/D [2392 0 R /XYZ 85.039 698.816 null]
->> endobj
-2391 0 obj <<
-/Font << /F62 1689 0 R /F15 1628 0 R /F35 1632 0 R /F20 1617 0 R /F56 1642 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2399 0 obj <<
-/Length 2431
-/Filter /FlateDecode
->>
-stream
-xY[s~#51$.t'N!'Dj(%x7@DgL`w,vx_<l|fqlE;|<E"0J,o~H$<'7+Y~ ~/7_3uYf4}:Tekkf\]b3+uY#S?g7=g&4F%}{4Y>~=BgGhGa:FK:>yfFL13 5`0IlGlrs<vtp_`'+bf 7bKEvsz6E 2`!
-0E-[d&hv;oiREKv%oaenYB]z SU"9&)6hy+5u ;4" H
-]%i{/&'Wl\B9sTWN#j|_rN
-L-K3vH62 ni ^\
-g9Rdf%G< 2Ck)MfOt,"5#X@rU0o7ã-áÌÒE_Z48j÷tìïÞr‰ ~!„©§
-Pe(s[AIbCbS2uh v9Yci„c§„*¼ApB,^} R Rr0~Y`Iw{~]eZ[a=ÆÉÝ̀m·mœ÷àB^uRTn/?K$-+$G = Mf r,f
-n,YK">l <>F\x?^U–Êâ
-((ʟS(jaRQVl+Fp,8pUU Q}.j/—c²ÞRM|_o&x
-b#LP3
-!:bw8FKRYdr
-S}bb[M&K]$!IP"K*A\ DF3*)jTi`In)2D{ `9;~dm@t\+ruTDEI&)4TX?[@|D_FUCRI/UQ=s,KbH8)Up^4mEYA< }mZ*niSr9[wRf;)_-IQz ls7`$0}FGdJ8#U8_Ws_)-w$T_|bF0;cSz"Wz4ia\(_2+}dHkPl,Oc:
-UGx{1;~C) OT4ir5S GC2J:?@$ #IkDJW=Lv{/#JL!s+}KE%[6L+
-sXa_f'(lGpYGsW/?x}0)-kR.z!
-endobj
-2398 0 obj <<
-/Type /Page
-/Contents 2399 0 R
-/Resources 2397 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2396 0 R
-/Annots [ 2402 0 R 2403 0 R ]
->> endobj
-2402 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [354.867 309.434 512.306 321.124]
-/Subtype /Link
-/A << /S /GoTo /D (browse-force-master) >>
->> endobj
-2403 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [111.316 298.006 150.096 307.575]
-/Subtype /Link
-/A << /S /GoTo /D (browse-force-master) >>
->> endobj
-2400 0 obj <<
-/D [2398 0 R /XYZ 85.039 781.388 null]
->> endobj
-318 0 obj <<
-/D [2398 0 R /XYZ 85.039 614.89 null]
->> endobj
-2401 0 obj <<
-/D [2398 0 R /XYZ 85.039 591.572 null]
->> endobj
-322 0 obj <<
-/D [2398 0 R /XYZ 85.039 136.291 null]
->> endobj
-2404 0 obj <<
-/D [2398 0 R /XYZ 85.039 112.973 null]
->> endobj
-2397 0 obj <<
-/Font << /F62 1689 0 R /F15 1628 0 R /F56 1642 0 R /F35 1632 0 R /F20 1617 0 R /F38 2158 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2407 0 obj <<
-/Length 3603
-/Filter /FlateDecode
->>
-stream
-xZ[s~pRz
-\>rS?W uPW,8x=RM?ÞãWw|Ryp wXpU;~7~^~aqaBj\/?]a_D.(Ga\ 01Z(f.(&NB X(sd'32}ZeWA{ V=r_Xruh-"jj5m%<
-U19;%u_uc
-yLA@9f7!tqCB)
-`9* hiY=}#@J@FpsP ;sG! t",~
-T3)&YidQlc-}` O
-mFfTvQgQ.\*NAF~ i4 6N tj+ZW1FHw=Rc$Y"G-CGJ²h¼ðÚ>îݸ…1ŸÍ Ç[ <Éuæë,,T<Ma(G70aSEG7 1*æI6[A;_$C=+K<#*yeAuMt)c_}Q]d@wPTMv%{J=vgArAs54[R2yy@v>u`xnw`iH 0NX eU6t=`jq#aih/O"HT)$fnc zn9;w'<^ tZ" *3U
-f~W7$bE435 jqªGGmKS+ N$ l©¡Š¬"iáÿËû;.´2x›1ÀB7{[!MJ?&!G/=+qap[$Rp@+N#\*f)`%n Cl;w"K?,3(w; cV-h>mP¥Ý[:éJ02:F.ydc3K,9E_YD3g6ùÐ;Q8!^\{ |9LCMF9g 8*`q
-rco0<(8X"3~_$(eR6'LY"p
-I;=`)GoO(4 5&i\ ]:q;OYA`sDSI;/q@fR;[& au
-|3xh;HXm[Y*PlIt#D5ac>f.iPe&w)Cm1XOa(3v4t}(NK&P{7
-<{;I2NcGT i@=kzrR ZiZ]v
-/l0g4
-NItsE,|dLn%=B$. sPuXHJXy a,
-RyHy.
-d0vp'7] n9h(
- yq+=Nc"m--l<B*ibqKk{I7U7P&u1GK6>:9ZNz|bMZ\;9{M1Xٓ$L[]I6D,O ` (?Os-zI,22Tr&FSg^'Y>`6G{\3YJn[l? 1>Oe9^:4iU I{\L
-Ozd1BGX\lYVV~
-]5x n?KQY 0NZK{N3P #UE5zMM|v<d$w#zn_fGZm.
-/)*aYXsNd^6
-310"TOZ{vg7a2Rl`ûÂë‰ê$é8Öj
-ÓðøI<<:3A^2q"ra~l/5:xx)vOyR6>OE$u:"Ib"7s$a)-k>{ JDh+,dL,jf"W7 T@@hNs' %g,4'{]W%#r|!k7VHZ@z'<Wnr|}eIe'bŠ³^d–ÌÿT
-endobj
-2406 0 obj <<
-/Type /Page
-/Contents 2407 0 R
-/Resources 2405 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2396 0 R
->> endobj
-2408 0 obj <<
-/D [2406 0 R /XYZ 85.039 781.388 null]
->> endobj
-326 0 obj <<
-/D [2406 0 R /XYZ 85.039 437.34 null]
->> endobj
-2409 0 obj <<
-/D [2406 0 R /XYZ 85.039 414.022 null]
->> endobj
-2410 0 obj <<
-/D [2406 0 R /XYZ 85.039 204.486 null]
->> endobj
-2411 0 obj <<
-/D [2406 0 R /XYZ 85.039 168.809 null]
->> endobj
-2412 0 obj <<
-/D [2406 0 R /XYZ 85.039 93.031 null]
->> endobj
-2405 0 obj <<
-/Font << /F62 1689 0 R /F15 1628 0 R /F56 1642 0 R /F35 1632 0 R /F20 1617 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2415 0 obj <<
-/Length 2742
-/Filter /FlateDecode
->>
-stream
-xko8{~_*5+X>4^MKRn?(b %$_ e.E*r!O+BD
-$$at;adqPa:-7o?Dkb<${/_Wg\U^[_^}bMyG~zN>ha"Dp4wv
-&GBhubh7_\;X11**E=R x- =OHIVk_:q tY
- 8(rdV?Ng S+d,q
-Kh[ !<g<!w'BZi'''<XZ#EsAL$";fu'Uy?pIV98FHG\h?'vq:ryM|EeYm1id7!+%nK8u({h u%AL u JYGn3$iQg &%=Y0NAylGi-&e\~IgGs,y^|9Lr<K;O=W#NAKW|qRf@)EB#ahgp@$f<{1< 62pU
-Kg@+:hW$`C<z2W_r e{'{4xl$BpP{/pywiXQ y 7X%S%iX|~L?s&8>N &8Vc-&]fcaK! ;~wCTHsU1z{_*p f*!DH!CjO@?Qh}GS%bb
-y}JqX "m!Sx>h\i\derW,*"w]%~M"i)gA~U6BtGj5QDWXu
-D;Hgzb7t[5mW{Q !Pr U4O<O}v.})*9,3n U.pl>)8/VWW#+m\/7\ 0K>e 8P"M_v*Dr> N1_o-|z9\g]%O:^x #nLB(ysY9m"0qGK,B`Z^qo#;
-]at.v\Sh+7 -cwl;/wcZ>ls(//>o(SI?fD
-S~ &$aI MA!‡ûéáÈ=øïýȎJm:=r7w*endstream
-endobj
-2414 0 obj <<
-/Type /Page
-/Contents 2415 0 R
-/Resources 2413 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2396 0 R
->> endobj
-2416 0 obj <<
-/D [2414 0 R /XYZ 85.039 781.388 null]
->> endobj
-2417 0 obj <<
-/D [2414 0 R /XYZ 85.039 761.463 null]
->> endobj
-330 0 obj <<
-/D [2414 0 R /XYZ 85.039 692.86 null]
->> endobj
-2418 0 obj <<
-/D [2414 0 R /XYZ 85.039 673.988 null]
->> endobj
-334 0 obj <<
-/D [2414 0 R /XYZ 85.039 604.917 null]
->> endobj
-2419 0 obj <<
-/D [2414 0 R /XYZ 85.039 581.599 null]
->> endobj
-338 0 obj <<
-/D [2414 0 R /XYZ 85.039 528.401 null]
->> endobj
-2420 0 obj <<
-/D [2414 0 R /XYZ 85.039 505.084 null]
->> endobj
-342 0 obj <<
-/D [2414 0 R /XYZ 85.039 136.833 null]
->> endobj
-2421 0 obj <<
-/D [2414 0 R /XYZ 85.039 115.636 null]
->> endobj
-2413 0 obj <<
-/Font << /F62 1689 0 R /F15 1628 0 R /F20 1617 0 R /F56 1642 0 R /F35 1632 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2425 0 obj <<
-/Length 3528
-/Filter /FlateDecode
->>
-stream
-xZYsF~`VDXZJ\[ &
-*IRji_
-52tfl5-4F~][Z9ÖVE=,[ hn0\uNoaX+0~Q$Pp~Ob 1=} \(O\:jS/yhpQuEVkU[2*OIùƍH
-#{1~"H
-=i@8in5f%MmSfANFFJ?
->2 "F:Y&~Q |L;F^SlN[YWn"pMd>-G] +$n'3 }AueW ++
-^m'%)#+T`i£2Fa\5-Öyž ÓµžÕîgɅŽ†N;SdpXEuXi;',]d4(Ov3Wo5|*sY1_LOeXl.
-MF80A#B<J]W'EcRDnmTfaH+pRwwMe(pa&XglY#j !H*KFSOZif@(A8O ^VL֒˜Pm'ZUgdMqZI4)_8wj!CBFsXXb[%K.RaIWWn{7fLY/
-~;ÞÁïq™Ýc-SI
-by06Y+B{oxkWR&C^A*L!c;#_le^o5}~ X*1cT[|tb8)22a<9<TfMq[4@7]jx>ScbB1Z(smin|p|gq9-'EhT"cc} ZTM+rhikk@a8F`>YkY5W(T< d,YRRMwu4Z4N½ú %è·8ýߺjW_sZa}S P'zb;*+A=2 reiyu+ ZK'7E /JugY)ru2%mP
-:~|Zua3Q{*d[O<8L,yF}iFdD$>#%= ]B~jqNkuUoS NdJz2L)X
-3_h_2<E
-m@_dX% n:afBv!nr 4j]~|AJE8nSg*_2DP5% B%-`_WcEG;[[S}^785WA{Yx6G}/hiéìé.%ë B'/0n* I@A1&:WgClHhg&Aµáaž_ìƒÅ˚P[J t EOVeY${/lI_O5zyIKJ-XhfPtqRQ>)&)NoUHbGo`_@hYb|tR7Z
-XC&jZ>\pH@*oh 93)a
-'(I(;)n1%P0UZ5~w @(q5v90!C0CZ7&U9IA&q2¿³3µ@dendstream
-endobj
-2424 0 obj <<
-/Type /Page
-/Contents 2425 0 R
-/Resources 2423 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2396 0 R
->> endobj
-2422 0 obj <<
-/Type /XObject
-/Subtype /Form
-/FormType 1
-/PTEX.FileName (./xslt/figures/important.pdf)
-/PTEX.PageNumber 1
-/Matrix [1 0 0 1 0 0]
-/BBox [0 0 31 31]
-/Resources <<
-/ProcSet [ /PDF ]
->>
-/Length 557
-/Filter [/FlateDecode]
->>
-stream
-xmIn1 EOPwu$Ig06V5 osO #h8:5?[IL~F PYdzZ8f(E#@xoL [
-
-6\>RgbW¹j[†›
-W{6;F])/Mu;pk;dh<EAwNtD](;rL Ttw_ =]=uS"yl-kHsreOvg<7t,e;/IB&(Y,kR'^ m" ^hW9AVy/f"Fy-Sng \d}B$w1.&COVX9gE{< P)!ZL~'UXLcXs~BLONZ_[.*]3Q!-endstream
-endobj
-2426 0 obj <<
-/D [2424 0 R /XYZ 85.039 781.388 null]
->> endobj
-346 0 obj <<
-/D [2424 0 R /XYZ 85.039 665.791 null]
->> endobj
-2427 0 obj <<
-/D [2424 0 R /XYZ 85.039 636.387 null]
->> endobj
-2423 0 obj <<
-/Font << /F62 1689 0 R /F35 1632 0 R /F15 1628 0 R /F20 1617 0 R /F56 1642 0 R /F70 2201 0 R /F18 2207 0 R >>
-/XObject << /Im3 2422 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2430 0 obj <<
-/Length 3395
-/Filter /FlateDecode
->>
-stream
-xZo6_
-PE}mnzrbT|\Pm9@p8/^ /2B?"|/B.$1/[b.rbw0x5YfU@ zx7_=?C
-._.?g0/76F..S1{)&D1s0sO7iD$8fh,$H<Z[d8[oiIwhN
-q9_(4KC7"3CxI'S
-c"
-UI R\uYR ,HYdRJ L03(r@&bPfX%he-Liv1f {
-+AC8SBRQ0hL8h-UtYJ
-'WeC2x;>?@XZ:'/[U;g>o|="sL!H $5~bS!baQ*yrb4S!AYSm 74E^q7Vd
-jlE-sÂzª÷Ø>˜3f¤K4u
-gFsnJ83W
-=IhglO1l<uXs &MawS%GNNYMz
-;.=q5<DPbmaxtkS0HT2o+-$gu%>\K3Uwk'{i(S+`IpzqQEW
-6)br:tta$509|UXLD E[PBR&j[Q'X1{r#K3SX;d@"^#7irIK d9&)EE&%we':2PEfBx'@~&rG2[Ze'wF`oVF"9
- 2AW|>vxtz>v+ p
-*SOK$yvq& gzyJGW9x¹>Zshh8PGaw)cKWS80`%-(
-kYM(UQBP-r\0(d:upd*\nkDt_}YIhlÈÂ0¾úIO/LME_ nqOui#?ItK(F8If a])f9Rz6&8_S2!uQYdq%y,c|;s;edwi%
-}6_4k80"n(Z_ES *Sd
-P[@*B&=-t#50u,nwFDVt_~c==ujcdb%,gJo+2F[9!oHM1FiqC[lN^\s/H+7#j.W?F2oCLg7¸ÀÏEuYyII)JR*5,*a-]5J#/]bnuyJ1/d|Y97vQ} 7Ul|? 'gkF2nM{xPDG]E[ d'X Z8N+0I$l8TO7gN)Wj,!-GAF@eP<#8gfg;&?N?h^)=Sq12Dendstream
-endobj
-2429 0 obj <<
-/Type /Page
-/Contents 2430 0 R
-/Resources 2428 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2396 0 R
->> endobj
-2431 0 obj <<
-/D [2429 0 R /XYZ 85.039 781.388 null]
->> endobj
-350 0 obj <<
-/D [2429 0 R /XYZ 85.039 761.463 null]
->> endobj
-2432 0 obj <<
-/D [2429 0 R /XYZ 85.039 741.134 null]
->> endobj
-354 0 obj <<
-/D [2429 0 R /XYZ 85.039 125.405 null]
->> endobj
-2436 0 obj <<
-/D [2429 0 R /XYZ 85.039 102.087 null]
->> endobj
-2428 0 obj <<
-/Font << /F62 1689 0 R /F20 1617 0 R /F15 1628 0 R /F35 1632 0 R /F56 1642 0 R /F38 2158 0 R /F72 2435 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2439 0 obj <<
-/Length 3067
-/Filter /FlateDecode
->>
-stream
-xrF]_e`p[-i-8#Q
-QvR
-E(K;gU+i:N"/:mOT5 )R]3/zûZvz,& G @ 2N[<>k70PN(A<@+FXa{QQv+46BY&hF|[ hdF/!|]p)8B`S6x-/{'u17h |°¨Ø‰ºó€_Êy
-w\u7UcI TX`L|L,@v ^*s}.89%#x!&/(?9 r~bæyötɄˆã\¨ÅD[m0@&ucS-G] [Z8dÊN ,I[JrNJT\ Oy@Uemi
-D-T] B8C8yQ`41}xs459 GtA_K05iZqpG`H,1$}x%W4m'va#[}x?p~<%9&AuF
-SGU=gr
-$mR@CqRj7*j|fRtw(m% *
-'>1
-eMm
-lYJ> UnQs9s+aN\îƒÞ„O$*`ap*kSs#j%r]Zzu~cs
-&}MmjJi8vkDHs~ kBL 0U&KL b0P;P:`Rip_ <}VO
- 2E?],JJ"+e xH
-)ݗèD;R5JF[@DiS
-2WxA}4?@!A
-Y7qR7E
-wAc 3$a_}&*6 %}YPMjo{j<?Ki[>Q:v0a#m!u~ Ns
-endobj
-2438 0 obj <<
-/Type /Page
-/Contents 2439 0 R
-/Resources 2437 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2445 0 R
->> endobj
-2440 0 obj <<
-/D [2438 0 R /XYZ 85.039 781.388 null]
->> endobj
-358 0 obj <<
-/D [2438 0 R /XYZ 85.039 761.463 null]
->> endobj
-2441 0 obj <<
-/D [2438 0 R /XYZ 85.039 743.459 null]
->> endobj
-362 0 obj <<
-/D [2438 0 R /XYZ 85.039 657.234 null]
->> endobj
-2442 0 obj <<
-/D [2438 0 R /XYZ 85.039 627.83 null]
->> endobj
-366 0 obj <<
-/D [2438 0 R /XYZ 85.039 586.218 null]
->> endobj
-2443 0 obj <<
-/D [2438 0 R /XYZ 85.039 565.021 null]
->> endobj
-370 0 obj <<
-/D [2438 0 R /XYZ 85.039 145.627 null]
->> endobj
-2444 0 obj <<
-/D [2438 0 R /XYZ 85.039 124.634 null]
->> endobj
-2437 0 obj <<
-/Font << /F62 1689 0 R /F20 1617 0 R /F15 1628 0 R /F35 1632 0 R /F70 2201 0 R /F18 2207 0 R /F65 2099 0 R >>
-/XObject << /Im2 2261 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2448 0 obj <<
-/Length 2464
-/Filter /FlateDecode
->>
-stream
-xYYoH~2Qn3Yaf(HE]GuuuUK S4 T&M,a`Als* Ld21(IRa  1O<W{WwCz<qqg2'/g'3B? g f /gotv,¬ÎÂÈøQh<{8qpb 4LixF+?U)4E~E<ETU^6u>+{?aHyeru05v0@]6%P%U./vSvKDs]uuGF*MF: _,3]0V(H"
-Vd+6ZZuIgW7qô5Bq2C% hL/z14@d~wsS%GZUyOV@;QDy{]F;LO@oO$[,DPsdum+ Ei<u/>q+_8YSenoYD/@]Wdx`.Jn A#@@!G bT:SeWD
-
-{JnVr*j>lS/
-W eh9iKZbw $rBUSlO(R#u%F|w*ôCJ )9)P9{geySdI4Q
-ykA z"r.Lrk=M 96yJm 9GCrJ"yi+()|g[Qqx:&BOsz'E,KII\!T] 2#,+{q@Ja&Pm]^=`'jWS~Ir0BT8z HJH-rYL%S=g \0|a 2pq?z bS Ga7hN16Nh[E}J8Rlo[ mSa|°ÇíÝQ)RNFzo@D1Nw!Oyi6j1~s"Z[.PH`RnN M\G&X]68ENP"rCC+cK
-XN
-/59GC]QWTV18xI#$`, $D?h+o
-endobj
-2447 0 obj <<
-/Type /Page
-/Contents 2448 0 R
-/Resources 2446 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2445 0 R
->> endobj
-2449 0 obj <<
-/D [2447 0 R /XYZ 85.039 781.388 null]
->> endobj
-374 0 obj <<
-/D [2447 0 R /XYZ 85.039 351.586 null]
->> endobj
-2450 0 obj <<
-/D [2447 0 R /XYZ 85.039 320.97 null]
->> endobj
-2446 0 obj <<
-/Font << /F62 1689 0 R /F15 1628 0 R /F35 1632 0 R /F20 1617 0 R /F56 1642 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2453 0 obj <<
-/Length 3684
-/Filter /FlateDecode
->>
-stream
-xio6{~QH4"%:.&xw
- #,y$y})H:@ H>=Z"SQ\\qVhJ YF?z@7zq*WYs&Kp_|y\[y_?^.\~nw $Lzl "
-"=@;
-UQCo.n/vdB\",9Pg1@
-kM=hj4F1Jdi=uqy. m $ !rhG^-"@5&dC-i!.aq+nsURMeg$={bX]g81,t$in0N *5`8j="mgt
-`tIp=+}Td^.%kY0EDM#j!$VAZ+gIDy|_rmJR5tu]c!QxjHj%K\H;<\73zq xHX-R;Gop
-Cd*"7)MqZOC"[ c B,ugv.THKeDtE^0
-7Ij)A GyatH.Oum05Jab(NWh-wM3 3Or
-S)mppC` zyY&a'Y4V]Z yF$N_))9A(
-qZ}*'v}?a y \e#Xd#Lwo M] H|m8L#"8IwY=q5]d&\8wD|Do22%det)ÍPB '=68:Kbbr2/"]1%ayND!I:6&l9cQ1&N[Y9tX!fJl.$b ( aR1b@c#b:u;MM+=e$ $ILLszSJC>a(Q/O2A'GMfGe* Yd  gFjE(jK\eå¼ÜSX p@?kas`y#|o8DZkKw }tAe +]`^m:/<)X1pHM!mEl)$Ng[Q!V`Unw~0rB,m-'AUuF4B0rSUVy]R]9WPkE~~3?uf?"wjz":Ke%b,8`t*pys$ A}'
-pI:J]b%'fL wG# QnN"cw#9 7j*45<DY6|t{|lu)y%`1xhj3HybtjUgTs[;-BhdF q ^6v~AV//
-U~bWhx Q*\s`~`CB1& uM/vj`&9u@I`UPKi Pya
-w<M#?HM^zT*EM=KIK}Og8&5DQ\n\Y{.LcKQhlai,Pz5S\y~`_JnwVxp5a8 y`m$ 6M qnl#?)I#R*/!c c9?@
-*IX2S;a{~]#.(Dqk%1
-)6We4/uw -DV]_9¤°J: 9R 9EJmzGS63ZKhugf8`+\g]<
-g-]LntA6%pm-ì\|#lñ£“,,\ þãyÆe±Í•‡{&…?ˆ3ª4%.ÎÀSu.& cf!eXV7Fe V''/rm:/`9[[Sj;rL75;<>OUDQ 6+F\Jiu_2&Q P 
-+`M.o rf os_gkrL0dhD-%WU9EcOXr C/=wYhOc< _
-Qq`6>8~dua
-=A`hhB<
-c._xNOZ=`z~}
- 2&C1.jÝqræ~(Ê+Îá©çJGaZ|Ou>;@x
-eMMv =l<endstream
-endobj
-2452 0 obj <<
-/Type /Page
-/Contents 2453 0 R
-/Resources 2451 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2445 0 R
->> endobj
-2454 0 obj <<
-/D [2452 0 R /XYZ 85.039 781.388 null]
->> endobj
-378 0 obj <<
-/D [2452 0 R /XYZ 85.039 761.463 null]
->> endobj
-2455 0 obj <<
-/D [2452 0 R /XYZ 85.039 741.134 null]
->> endobj
-382 0 obj <<
-/D [2452 0 R /XYZ 85.039 298.591 null]
->> endobj
-2456 0 obj <<
-/D [2452 0 R /XYZ 85.039 279.719 null]
->> endobj
-2451 0 obj <<
-/Font << /F62 1689 0 R /F20 1617 0 R /F15 1628 0 R /F35 1632 0 R /F70 2201 0 R /F18 2207 0 R /F56 1642 0 R /F41 2104 0 R /F65 2099 0 R >>
-/XObject << /Im1 2193 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2459 0 obj <<
-/Length 2905
-/Filter /FlateDecode
->>
-stream
-xYoF_ry/NU-$D$%ffWD'k 3;=+3L4l9 '0NRD$xbIf_nfo y^wS:{hq4.w~?pvS \^>lp$L2CqdA$
-mYL^h,'$aXNNw\2U#8u 80-QK-&!H:Zf!4
-fj eA5oq,C):qhsl&bNle+y<t^qW[&-Jj
-C#++0 u2r#{nzw FMuu$3"Ki}w$mLU= .=),2p;UC1fH7n{Af @b`#2P8[ 
-/`DsaF&>26
-:G[9r¬–{,DK ( mIFY3c3E .o {rW[
-t$/jy^|PH
-9 Eto;_8{xLN1"+KZ+c$' Lh)nQ
-q29m\
-k/Xq!p40 Z5Fv/U[}>m}#%"w&CG3i@~PRux_`Q1emJE:-¿­SkjZSi
-endobj
-2458 0 obj <<
-/Type /Page
-/Contents 2459 0 R
-/Resources 2457 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2445 0 R
->> endobj
-2460 0 obj <<
-/D [2458 0 R /XYZ 85.039 781.388 null]
->> endobj
-386 0 obj <<
-/D [2458 0 R /XYZ 85.039 761.463 null]
->> endobj
-2461 0 obj <<
-/D [2458 0 R /XYZ 85.039 741.134 null]
->> endobj
-390 0 obj <<
-/D [2458 0 R /XYZ 85.039 484.308 null]
->> endobj
-2462 0 obj <<
-/D [2458 0 R /XYZ 85.039 461.592 null]
->> endobj
-2457 0 obj <<
-/Font << /F62 1689 0 R /F20 1617 0 R /F15 1628 0 R /F35 1632 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2465 0 obj <<
-/Length 3030
-/Filter /FlateDecode
->>
-stream
-x]ob"YE")*v6N;!-dWr$m\|v$@sA "p8on_I|8.6F^2#Z0J:8x2U8
-(_\\xppe68?G53|}_|8=;ysl^\|wd;W }4I5
-A.q/6&abXx,x +&NB X(x O:XXVA[v%7
-Fm'.06hrw0) ND17;u ]_<p4¸ñ}G/W5Ov!w\K8Xa12,65L2&f[
-vwTi~|H'L /NINHaUA^T2blPeBv]1` R6#aHB4o
-xVUl;kA#"@Z FJE =gHhE-
-Lqvs7u e`WoZt
-ti'M<)Z 7 _/OKA#&zkYb]$
-n+ 4tMC^:
-J.Tb8
-G* l";K"YiD!25Z?X M
-|p/<I|:P-UldxKhn_,'\`m5"iJOXz}).}*S[I Dw P\8:bu}6n$$oe{L!{5=;5EgRy"%me%t!Wg,exHB&lN!Kd
-N!"USh8"t3 {#?w`K2VMS[z1 zZ.uF[ :nŠ•€Ma'0/fkIx9u#i?BSC</jnppp'"IPP5#I%}%. [(.tjd)q1'@^O Xc=BHJ+F'cK
-nsnh[BWw8+Lqfu ]
-+.;qG*a+`9^:rZT;}<,y=R,C|^3b&IAmD9:G0qipQN|yJB9P*3mvJ3PGM/s¦qêÝן^œfCF | *
-K i3Ž¶êùJ1hx1g|R^ci0v+7afj_HwB'@q9P8'Dp\5]G!S*y6H0xzpEJ85/ÎƽÃBc8J@`p g.FxD*7H38 ]+<b[nH2tX[4|(3Ru<e5"W
-endobj
-2464 0 obj <<
-/Type /Page
-/Contents 2465 0 R
-/Resources 2463 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2445 0 R
->> endobj
-2466 0 obj <<
-/D [2464 0 R /XYZ 85.039 781.388 null]
->> endobj
-2463 0 obj <<
-/Font << /F62 1689 0 R /F15 1628 0 R /F35 1632 0 R /F38 2158 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2469 0 obj <<
-/Length 1658
-/Filter /FlateDecode
->>
-stream
-xYr6}W./}l'MZ+mLhlH/n;g
-4z;Kg*9qlFVL~GYH;4j
-OP9,0w\8{ZjMdy+CODWOC^nVf wg 7I30]1MwiY.WK<"MW
-:y{^eV'uvMZ1\s<3fPC,4]e}1"[n+8#c`lZpP$AWQ~4],q^]agp-\wV\aW`gl1@P)RnB1"NB:h K0Hn<Cx:iq:bYmAEdb6ZWq$"SLTrJ ChrstB li +)nni&*|h(%)nX3pS,dLZkrESr:7
-G;\ys(7hgt•TxMJ_H=KZX7a>]l{!J1C<!bhF,,t<qUp1h? e@:X\J8kn
-!(O\Q5"
-endobj
-2468 0 obj <<
-/Type /Page
-/Contents 2469 0 R
-/Resources 2467 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2445 0 R
->> endobj
-2470 0 obj <<
-/D [2468 0 R /XYZ 85.039 781.388 null]
->> endobj
-2467 0 obj <<
-/Font << /F62 1689 0 R /F35 1632 0 R /F15 1628 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2473 0 obj <<
-/Length 1215
-/Filter /FlateDecode
->>
-stream
-xW_s6 RlioIf{m:U:v.Jmk{3A
-cNa80p8 {@$ K!A8e<%sUUgmDe wcTM1kEDYA3&3zB5 #x'iuT ScI
-%?vJ0hAL;~5*evsg_
-s4/`ae'6&bje)3L&
-endobj
-2472 0 obj <<
-/Type /Page
-/Contents 2473 0 R
-/Resources 2471 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2478 0 R
->> endobj
-2474 0 obj <<
-/D [2472 0 R /XYZ 85.039 781.388 null]
->> endobj
-2475 0 obj <<
-/D [2472 0 R /XYZ 85.039 634.111 null]
->> endobj
-2476 0 obj <<
-/D [2472 0 R /XYZ 85.039 598.046 null]
->> endobj
-2477 0 obj <<
-/D [2472 0 R /XYZ 85.039 561.982 null]
->> endobj
-2471 0 obj <<
-/Font << /F62 1689 0 R /F35 1632 0 R /F15 1628 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2481 0 obj <<
-/Length 2581
-/Filter /FlateDecode
->>
-stream
-xYKW 0IvSAI`-A6HOU}$5:_Z]@nJunw|iBKcZS{frft2G%~e4.
-Jmr uzm,jxET/T5Gutfk|e3d7i$aJM !Sc55zY&Qq4lwEM^feFKQ~z+NG+D JC<JcOP73I|<h6GorR&%|5G&r||BnBS*ge^vf9]1D #(.<0wWu5c0$wuVd
-uX7`3''cHL|w?U\! X/r;H
-1 ue|g4 %nKo@</^y9<9iXe;PwAz, '45\f:><cM<gl IX6tiOt;:2;Iex)\cux7R'
- >?9wST$(#h=L@_[yu%!|c2kg<9U./ 1=?bfR1
-+rvM8C4OL~=VvO|}([3Xm7--
-x
-Ir;M.h_y| [aY`X n[/OGlsW@0s\uhpJgdv{Rq) xzL&ydyWT+J 6';lVd3 ?A&fTK.AN/d{]f.D[q $1E 
--A{SyJ p1:fh`k2
-rpbqK.# ' ,tB3k\+e/hcxg,#~Qr.rBp5srMg\b(SsX!#f:&Y$tg2?*`v0>p`YD)w%c68tVaC
--(rHd~2%-rxp8'-VxAeP"6z@&NFkWVIu'K_`:/GxfI1 s1 B!/~V2{Hev;dc!TfnmIVR94Upo ODW{hl*8*|GuW$$Z[6DO\0]7g]"bV
-guZEo7TGQrgRendstream
-endobj
-2480 0 obj <<
-/Type /Page
-/Contents 2481 0 R
-/Resources 2479 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2478 0 R
->> endobj
-2482 0 obj <<
-/D [2480 0 R /XYZ 85.039 781.388 null]
->> endobj
-394 0 obj <<
-/D [2480 0 R /XYZ 85.039 761.463 null]
->> endobj
-2247 0 obj <<
-/D [2480 0 R /XYZ 85.039 671.062 null]
->> endobj
-398 0 obj <<
-/D [2480 0 R /XYZ 85.039 671.062 null]
->> endobj
-2483 0 obj <<
-/D [2480 0 R /XYZ 85.039 642.326 null]
->> endobj
-402 0 obj <<
-/D [2480 0 R /XYZ 85.039 406.978 null]
->> endobj
-2484 0 obj <<
-/D [2480 0 R /XYZ 85.039 377.574 null]
->> endobj
-2479 0 obj <<
-/Font << /F20 1617 0 R /F15 1628 0 R /F56 1642 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2487 0 obj <<
-/Length 2038
-/Filter /FlateDecode
->>
-stream
-xnJ_#>fn{HN;+v@N~ sVjE
-MuuQ* ?a%$` 1<+p(7^j6ZyyRt8u~e"Þx‡`†á¿ë7×wï—ßW-&L8D_ iba"M"RW?*X|jFV'#ada~e&Qt )Lc"p0Rzf'dN'
-n/ ^,b H$6{us9{
-AB6L0^4
-] h(|A Oo~p?
-*ysC;DO3- '@N-ih.2m~,3<B3\WKoAu)
- @z5Kp`d(Jm]f:HEW>06OnRD(!
- Ke_SE
-endstream
-endobj
-2486 0 obj <<
-/Type /Page
-/Contents 2487 0 R
-/Resources 2485 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2478 0 R
->> endobj
-2488 0 obj <<
-/D [2486 0 R /XYZ 85.039 781.388 null]
->> endobj
-2485 0 obj <<
-/Font << /F62 1689 0 R /F70 2201 0 R /F18 2207 0 R /F71 2204 0 R /F15 1628 0 R >>
-/XObject << /Im2 2261 0 R /Im1 2193 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2491 0 obj <<
-/Length 3153
-/Filter /FlateDecode
->>
-stream
-xko>D,gQRz5-|%JfM
-Iy-hs9;;;J<S$t=D:If7wWJ0YzQSW|ù3幩—ΖBYr^|v`zx?WD;ww< o,YZXni<W?p<WcUi:]v@{yu
-3^5qEG@{nU8q>p5#q ?v|z3p]
-BzSVuxlQ=nBXIY}W&DPnP>sÀe¼ËŽå=Š>+à¸A >oP2(\3Y 7550VMv&+I08C8y41EYs`5WNl0aBUn{BA^!®Ä}évÈÈÄßÖ
-~謊u
-ÝH1z,W\,1-IE
-q+v|2I#'M-]aB?c+JuSR=9y87piu=D}]<3Mf_LAZ)o>23
-id m+q} @4f%nvYyrvkT'^=|60
-<92UpXEkS{Dc"i| F+RM| @P`1E gcE.|UHf[ Q`: kf
-N8j}endstream
-endobj
-2490 0 obj <<
-/Type /Page
-/Contents 2491 0 R
-/Resources 2489 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2478 0 R
->> endobj
-2492 0 obj <<
-/D [2490 0 R /XYZ 85.039 781.388 null]
->> endobj
-406 0 obj <<
-/D [2490 0 R /XYZ 85.039 694.591 null]
->> endobj
-2493 0 obj <<
-/D [2490 0 R /XYZ 85.039 671.274 null]
->> endobj
-410 0 obj <<
-/D [2490 0 R /XYZ 85.039 529.279 null]
->> endobj
-2494 0 obj <<
-/D [2490 0 R /XYZ 85.039 508.689 null]
->> endobj
-414 0 obj <<
-/D [2490 0 R /XYZ 85.039 420.324 null]
->> endobj
-2495 0 obj <<
-/D [2490 0 R /XYZ 85.039 390.919 null]
->> endobj
-2489 0 obj <<
-/Font << /F62 1689 0 R /F15 1628 0 R /F65 2099 0 R /F20 1617 0 R /F56 1642 0 R /F35 1632 0 R /F38 2158 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2498 0 obj <<
-/Length 3201
-/Filter /FlateDecode
->>
-stream
-xZ[oF~
-he}p$u&^GEh0iD*$E23$%t #I}|;??It'+d^xu o^$]L|Mt2&wOWw,OS17Mx4b.?W>9YU|OoB\&{E(+C7.eGpF:3-f~kn hBK
-M@j~j)TKr~?ORq,U/jT!gA{*|Z/_N”ÚpùõPH)W]kB-q;_zGg
-kqNa^Q892YWiu/!OZt6`J v_NH?s\G"4 0BMJAC Wx / -eN8GP%c5q
-+l+.Yew<=k%>|iSA
-9$fYAZ2Scqm2*+yHG!i†ýêmì$®›0Ëõ K$`KgNg0³À†‡CGH(7jGl"<5$ nUv^'R\bH, cH;g! 5wmL-apK^hLoD7LyF:ïÐb z‚O@xJNu~O
-{;r00y .54n}1,\^/A8NH{
- D8GRW31psQw&q &OmxnW[9MN-0%WIRgNN2t+)X[ap > 7  ,Lt-dJrf)G(vnx BWjFx" SI 0+aJi6&tbu/\^>dt`+H8wg x<iRf$+.vNY_L]'(0Zs4@ITGyd_{KV7| .
-,7BgCXWwFg< >FV?GCD&V7-#WtB/Î|V_kuMr5jK|<0|!sa`0}
-EeD7\izc,V%D;,4C-#p!.,cV5Q^dX-r%!(pveY !-.mUYkd?:<<}wL`u7s$ÓÞ ¯5µ­5œ3µW'7iE\<C0 M/4)a[ a]q,G^by«ë뜲 ŒÕ>ï©aØ¿‡Ã!^¤Èþ}‚Ù¤{†Yo8"[u<nNy;lvX"`X]tkhxL85Fr?} XDw~`\s"rA1HLjiOX0]; "i
-&3C\2E1~7. HV;g4 Oendstream
-endobj
-2497 0 obj <<
-/Type /Page
-/Contents 2498 0 R
-/Resources 2496 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2478 0 R
-/Annots [ 2504 0 R 2505 0 R 2506 0 R 2507 0 R 2508 0 R 2510 0 R ]
->> endobj
-2504 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [205.71 454.02 345.156 466.012]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.openldap.org/)>>
->> endobj
-2505 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [265.68 432.424 479.579 444.417]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://iplanet.netscape.com/directory)>>
->> endobj
-2506 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [171.824 409.983 267.01 421.673]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.ora.com/)>>
->> endobj
-2507 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [161.013 360.141 303.763 371.83]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.unav.es/cti/ldap-smb/ldap-smb-3-howto.html)>>
->> endobj
-2508 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [290.138 338.546 335.01 350.235]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://samba.idealx.org/)>>
->> endobj
-2510 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [268.283 275.623 403.2 287.312]
-/Subtype/Link/A<</Type/Action/S/URI/URI(file:smb.conf.5.html#ENCRYPTPASSWORDS)>>
->> endobj
-2499 0 obj <<
-/D [2497 0 R /XYZ 85.039 781.388 null]
->> endobj
-418 0 obj <<
-/D [2497 0 R /XYZ 85.039 761.463 null]
->> endobj
-2500 0 obj <<
-/D [2497 0 R /XYZ 85.039 739.701 null]
->> endobj
-422 0 obj <<
-/D [2497 0 R /XYZ 85.039 680.927 null]
->> endobj
-2501 0 obj <<
-/D [2497 0 R /XYZ 85.039 654.312 null]
->> endobj
-426 0 obj <<
-/D [2497 0 R /XYZ 85.039 595.538 null]
->> endobj
-2502 0 obj <<
-/D [2497 0 R /XYZ 85.039 568.923 null]
->> endobj
-430 0 obj <<
-/D [2497 0 R /XYZ 85.039 568.923 null]
->> endobj
-2503 0 obj <<
-/D [2497 0 R /XYZ 85.039 547.93 null]
->> endobj
-434 0 obj <<
-/D [2497 0 R /XYZ 85.039 311.161 null]
->> endobj
-2509 0 obj <<
-/D [2497 0 R /XYZ 85.039 289.965 null]
->> endobj
-2496 0 obj <<
-/Font << /F62 1689 0 R /F20 1617 0 R /F15 1628 0 R /F35 1632 0 R /F41 2104 0 R /F56 1642 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2513 0 obj <<
-/Length 3342
-/Filter /FlateDecode
->>
-stream
-xioX
-X$g%S&AHIRJRfHIv@Xq7o;r;Q(][hpF+yw
-3m' p¹Ž8Éh¾$yö›uõ~z?ó0ž(¥,˜O(gc7wo^l}|0|k181woS?QUvl7IF ?Pv+,<çxÕ
-úl¡¿ÀFaO|mkSi ymU(+B^s/m[VE&BE%D7,Hc=$| <'G8@#9:g ‰Åb Ö<jÐýî¸>ҖË>é‚X7Lj+~5cI vQxV 9|Qw7 +9"kdÎá¦øE(_MxC2]N2.e[BU49 WR=iYe8C55_16m|PPSByx_+@]c&>‹(um:ƀº6Æ'¡•š–ù‘ÅzTF8KoFh1+(Ptd2KwHU>VU)>F=ACZtn
- [;nyy]%l^5Q%t ga1,t%Mz(O -Q X7 6VpS)N=pk#d]2uSGf0xm_à"±Ɩdš7²pËߟQ [ gUS-8(:{\"-K0@IsAC+EA yK|Cfb&^`Xt`/K(V 6`+()z^}E3 %F[
-`ww7aMj{
-w>phloLwc[ Vw
-nÄ0™ÓÃá`ïÒ¬´Ác_žß…‚É@=}YIGMY8 .?jr 4:xe'QtHC4X k!
-p8
-"H-]KYWde&B0Q9qdBD?x5
-eq.z29BC4 8`hf3{\M/¸ø-aM7~Km&n@dg(@")LoJ. ^KyT]pM IQZ5 ALCk!P^5H9$p5O0)@+1@A(&j*n;&%=(DB+60eg9'kQcBZ#%s S`]~V$Ofx
- *vIAQd=EzO9/ov)KJ]K: pthl2TA`qD6}+g"D0-t.h^I0j<e&v
-$BQ%_-cjX?J=O&:*
-W${B}_pVT
-IVESW 9&|^i\[0Tv7zE.bX/77_^Lf7+A8CL=wg3áO
-=rs9T1m;8;diIbQ<NrdlS44]u]M|7 2]5$+]>'5 .v %s^M^o!kZMZ?h*6%Њpri!¨°c7>º’8¨×ÙHm]nu:~/W'[Zas `0Uw7d'^R"@Hgr]"!2b,k.h g?TRy-$c` HTGk
-U·Sy){^ uMs\jDCHw33E4{he_'#k*\Jt] VM$V"$q+
-ï›Ã·®l`Ù"îW^SVR)-@[v)G&WM.?I}dC }RB9.VdR&ZWP f
-XD C;=rIKIJ %JDuP:prjh+
-*”–Y<5\!yv~"@sJ"Rl?>b
-|=6YQ3=+>#!TL3Zs.PGp!e?gu* 8C,D'`wsm8V\xS*GM]f%h9^n]E!2 qL<z#}52j/u
-q%TT@!"u**]07 $y?Ai[mn8 O*0G.a
-endobj
-2512 0 obj <<
-/Type /Page
-/Contents 2513 0 R
-/Resources 2511 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2478 0 R
-/Annots [ 2515 0 R 2516 0 R 2518 0 R 2519 0 R 2520 0 R 2522 0 R ]
->> endobj
-2515 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [470.223 578.412 512.306 591.313]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.padl.com/)>>
->> endobj
-2516 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [111.316 564.863 187.762 577.764]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.padl.com/)>>
->> endobj
-2518 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [476.617 434.366 512.306 446.056]
-/Subtype/Link/A<</Type/Action/S/URI/URI(mailto:samba-patches@samba.org)>>
->> endobj
-2519 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [111.316 420.817 205.581 432.506]
-/Subtype/Link/A<</Type/Action/S/URI/URI(mailto:samba-patches@samba.org)>>
->> endobj
-2520 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [228.437 420.817 309.672 432.506]
-/Subtype/Link/A<</Type/Action/S/URI/URI(mailto:jerry@samba.org)>>
->> endobj
-2522 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [194.71 157.41 275.945 169.1]
-/Subtype/Link/A<</Type/Action/S/URI/URI(mailto:jerry@samba.org)>>
->> endobj
-2514 0 obj <<
-/D [2512 0 R /XYZ 85.039 781.388 null]
->> endobj
-438 0 obj <<
-/D [2512 0 R /XYZ 85.039 524.101 null]
->> endobj
-2517 0 obj <<
-/D [2512 0 R /XYZ 85.039 502.905 null]
->> endobj
-442 0 obj <<
-/D [2512 0 R /XYZ 85.039 406.548 null]
->> endobj
-2521 0 obj <<
-/D [2512 0 R /XYZ 85.039 385.351 null]
->> endobj
-2511 0 obj <<
-/Font << /F62 1689 0 R /F15 1628 0 R /F41 2104 0 R /F35 1632 0 R /F20 1617 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2525 0 obj <<
-/Length 2074
-/Filter /FlateDecode
->>
-stream
-xX[8~a
-0E{R^k.l7vz?b5~PU/fszkkV
-2<QMR8+xqhuwI_7_y'I(YMV~7Of(i\utn8gx:<w eo!>HfO^)ioaKpGL/)u^.u%kf8KpGZ$Cf#?r~:pu>R)OB6-p LNPOHCx sb'`zç“mJAJ@$2t,SttM!s4%sMYiR:)fH^n"Ec yIktX
-JxP R>Bpys,TAsj:(fL;g( 1,vnzL mLWG!or:]@3o  hya.9vyuD@ |,b_Xpm[QfE@
-3I UER,:kK-< ?^dP
-yFO:DH \3@^mrptR6b2e`5=Me@YDS1N0<eAOPXM.
-:/ qC=-ĆK!G  Z]Ma> s/`"W%s>vTEH'mUx|adL=N
-u!AB; 3Gx0U5}fh\L3|LODjB;Ad+;#&B7U
-@`WU]-t`:àž× \ëeIG}㎽¬ô¤E\Am@i/HIC34Y#]R*E27y(pg qyjp#d;L]SD 7YC|$`_b~YiST24XRM3Y>]3ÙRsTYq.WPd'y NA<w5!=F q\"~fr')-^YUt\Xi8?cH\xy~pXWxihtC{]pa/`RW5^j~ypj/\"x%Yrm?_YqTG>v6^aEzJ>:]Em1v!c'NAKo5a[(k14IiI U==-p_U hw%+U8
-±ïTXjCcUfEpkSfþ> à ®L PIC\"f"`c&y
-endobj
-2524 0 obj <<
-/Type /Page
-/Contents 2525 0 R
-/Resources 2523 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2529 0 R
->> endobj
-2526 0 obj <<
-/D [2524 0 R /XYZ 85.039 781.388 null]
->> endobj
-446 0 obj <<
-/D [2524 0 R /XYZ 85.039 667.6 null]
->> endobj
-2527 0 obj <<
-/D [2524 0 R /XYZ 85.039 644.282 null]
->> endobj
-450 0 obj <<
-/D [2524 0 R /XYZ 85.039 644.282 null]
->> endobj
-2528 0 obj <<
-/D [2524 0 R /XYZ 85.039 623.891 null]
->> endobj
-2523 0 obj <<
-/Font << /F62 1689 0 R /F15 1628 0 R /F20 1617 0 R /F35 1632 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2532 0 obj <<
-/Length 1594
-/Filter /FlateDecode
->>
-stream
-xXKo8W!23z?
-6iM{Js%JK*%5v.v/k)r8f8:]þœnÛKQ/cw'rq4n]&tcI2oz},X( zef>z|r=kxnpZwSv!D'~?;/v7A?ul%qwc8Iu#otXqQk~Wj!q#x6c(M^dW5cwCf?Q 1k)kNg> D>by'yupOvey]q|3/MQ7$$A!'\6 8F@\ w'sY90t6qGy+q6+q~[0Og(k1LY hr5?"q HZc5[@caTG?y3 yV5
-Lx[- )rseQxSV\,g%9@iG8"-KmX;!BS+}eo6 bWuR3Tu<o"Xi,x E r# mH_x! $C$pU$G'.f;;C02z6
-&)Ie;'vf HxL3Z(DUj*9WT(Z
-L.FMd RqF[GG uU .t@(77!bUfd qoTL}<GUU{&)Sb;r%2P}=:b x/V-L)h}rD\qcz5K"o"Z!VbY5E)zk-zQ^jBv{†×ƒÃÛ»Ç}áÿ ¶ß[ô×OW#8xYfpl6n8/txsAO+t@58E&M,L~RB >~@T|z[2]85fG~x f7-:bF34?cIk6FR5\@TPQj_;U WQ~C}-H;g9KNi1a"X(-I
-endobj
-2531 0 obj <<
-/Type /Page
-/Contents 2532 0 R
-/Resources 2530 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2529 0 R
-/Annots [ 2535 0 R 2536 0 R 2537 0 R 2538 0 R 2539 0 R 2540 0 R 2541 0 R 2542 0 R 2543 0 R 2544 0 R ]
->> endobj
-2535 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [138.589 577.023 352.054 589.924]
-/Subtype/Link/A<</Type/Action/S/URI/URI(file:smb.conf.5.html#PASSDBBACKEND)>>
->> endobj
-2536 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [138.589 555.113 176.46 566.803]
-/Subtype/Link/A<</Type/Action/S/URI/URI(file:smb.conf.5.html#LDAPSSL)>>
->> endobj
-2537 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [138.589 532.598 210.278 544.287]
-/Subtype/Link/A<</Type/Action/S/URI/URI(file:smb.conf.5.html#LDAPADMINDN)>>
->> endobj
-2538 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [138.589 510.082 190.036 521.772]
-/Subtype/Link/A<</Type/Action/S/URI/URI(file:smb.conf.5.html#LDAPSUFFIX)>>
->> endobj
-2539 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [138.589 487.567 187.278 499.256]
-/Subtype/Link/A<</Type/Action/S/URI/URI(file:smb.conf.5.html#LDAPFILTER)>>
->> endobj
-2540 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [138.589 465.051 185.157 476.74]
-/Subtype/Link/A<</Type/Action/S/URI/URI(file:smb.conf.5.html#LDAPPORT)>>
->> endobj
-2541 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [138.589 442.535 232.763 454.225]
-/Subtype/Link/A<</Type/Action/S/URI/URI(file:smb.conf.5.html#LDAPMACHINSUFFIX)>>
->> endobj
-2542 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [138.589 420.02 213.157 431.709]
-/Subtype/Link/A<</Type/Action/S/URI/URI(file:smb.conf.5.html#LDAPUSERSUFFIX)>>
->> endobj
-2543 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [138.589 397.504 208.46 409.194]
-/Subtype/Link/A<</Type/Action/S/URI/URI(file:smb.conf.5.html#LDAPDELETEDN)>>
->> endobj
-2544 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [249.04 371.394 306.851 384.295]
-/Subtype/Link/A<</Type/Action/S/URI/URI(file:smb.conf.5.html)>>
->> endobj
-2533 0 obj <<
-/D [2531 0 R /XYZ 85.039 781.388 null]
->> endobj
-454 0 obj <<
-/D [2531 0 R /XYZ 85.039 653.944 null]
->> endobj
-2534 0 obj <<
-/D [2531 0 R /XYZ 85.039 631.228 null]
->> endobj
-2530 0 obj <<
-/Font << /F62 1689 0 R /F35 1632 0 R /F20 1617 0 R /F15 1628 0 R /F41 2104 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2547 0 obj <<
-/Length 2685
-/Filter /FlateDecode
->>
-stream
-xnH=_aeX P<doil~l*6;s+6UPSRvG(k(-7gh;\pFn:?|z#×±c'Í džþnýöþúaþæÓx¢”²`{<™N#lZfO7wy ]z={3sGP!~@3Vq4zcq<_<?{O :QU
-./uaHZ!k7Q> O:q.qZL`Z=Ì.pb$àIZ?EyM\gL{|$M
-:@,rM9oK6p.q
-@xP
-EVm@6M2
-HP_|-~]V [#[z>5"7gY2:JK8btw|'(rR8~p
-d#5!G+^,B'S"zib bq0HCyI@gj+SVHlXlÐà‚µ¸ ‘Ws8#WÚ*ôah”ã»ʁð7=DØ~ ‘âV)N
-,NVVNA,@9^p
-V ^_oj yyPN%<n'w#UYVk]hj-/{%VpHA3m\/9mM da8F/
-YC
-%3*B5XgIMyu/IDU]X7UY52
-ZS#c[%
-W T/i<F(HC0D"Z54=w*l7v1VS>  Tnendstream
-endobj
-2546 0 obj <<
-/Type /Page
-/Contents 2547 0 R
-/Resources 2545 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2529 0 R
-/Annots [ 2551 0 R ]
->> endobj
-2551 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [367.79 127.787 439.883 140.688]
-/Subtype /Link
-/A << /S /GoTo /D (passdb) >>
->> endobj
-2548 0 obj <<
-/D [2546 0 R /XYZ 85.039 781.388 null]
->> endobj
-458 0 obj <<
-/D [2546 0 R /XYZ 85.039 477.879 null]
->> endobj
-2549 0 obj <<
-/D [2546 0 R /XYZ 85.039 454.562 null]
->> endobj
-462 0 obj <<
-/D [2546 0 R /XYZ 85.039 303.477 null]
->> endobj
-2550 0 obj <<
-/D [2546 0 R /XYZ 85.039 282.887 null]
->> endobj
-2545 0 obj <<
-/Font << /F62 1689 0 R /F35 1632 0 R /F20 1617 0 R /F15 1628 0 R /F41 2104 0 R /F65 2099 0 R /F56 1642 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2554 0 obj <<
-/Length 2542
-/Filter /FlateDecode
->>
-stream
-xn8=_adF^QZ*7Mw:Hnb t K,i$:n~eGN,6Es?1
-4dsV03!o;2W_Hw$;r|I uxytZn2oozlzžxÃ<†ÿf¯f·W="&KWg9[Dhsgg?UN|p8; i 0}Sl<Rk`4Vf>Qd0TO`4
-afMWX)/K.q;ghwY5G(D3(%
-iN \dZqx|=*{,1\r! $/I8@*Y05lê(]³nR'dj" O!ezPR"bK<7|a8We@,Ih/R^ q<Q7$*f#E"I4vRV$F!rN <Bm>3sIp|VFE *b/[x0]gkp}
- ~yR[uj'UdLmwj&]/'~O7v$yN7z,IbtVs+{v]jCI/Je m4{C|yo1Ìò‹jû²ÎªºÈ.Òäe]ÄyùGEYivvM(49::&#`$,v<aw0'={ a|h{X FW)TClq /tTb{%V,ImJ]sGY )
-L¶DGX(b&
-J9@y@t[~N.$p"t4*s A|FbDJt81^#4oE?6yi#[Tcyi8jSH]>aKL i 5N`];j<%h-oykGQo+f_q\ *JcE%m[uRVS_o_gfYjn"@Q2&
-{%O-2wA@ss7Xr/O7<XSV/iuyAzL4|' Y
-\-K|<MKs ^E$hP Bn*my=@N(PhR,æ
-žiUhNiKIK[/qZiW=R<u_l.0w04L:N9Oap&@..fLNC"Cv7
-#]Ue2nFG~u>#4FQ|sadw|fw*pe^d'8 tCK %UB_(3+-ELk(
-.{# u~&/..
-N?jV=t`#w%ds x 9R(P
-endobj
-2553 0 obj <<
-/Type /Page
-/Contents 2554 0 R
-/Resources 2552 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2529 0 R
->> endobj
-2555 0 obj <<
-/D [2553 0 R /XYZ 85.039 781.388 null]
->> endobj
-466 0 obj <<
-/D [2553 0 R /XYZ 85.039 574.243 null]
->> endobj
-2556 0 obj <<
-/D [2553 0 R /XYZ 85.039 550.925 null]
->> endobj
-2552 0 obj <<
-/Font << /F62 1689 0 R /F15 1628 0 R /F35 1632 0 R /F20 1617 0 R /F41 2104 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2559 0 obj <<
-/Length 2684
-/Filter /FlateDecode
->>
-stream
-xY[o:~0,VjRnI.>(l%$4~B@M p"GQB0|s"F+ys"
-1|vx#)X_wD)xX:zzEq"i'W@>U 'Uq4zpe6'WO>sz:^z! pH*D!dxx xO7oMlZ0U-r"5?O pHbtMY=lXn#rA<tZL67iQ.c;2Ün dU:GH
-asZ=A94p)k $
-F|%7S|'a 6I*w!9(^lU( |5<r2~A5uHF=MDw~4V$H7Z95—Eq9N aMB~nH9li"q1/%^p1]HC
-iEd(tel$YK.K+<O+$Pa,nI3n]*H+(IN7mRV-LCxsNk9
-q]eeV6mK&qqQQxxdîû=¯­µèÏ÷¼ÿ™·•ÃU!VbL06wh1iPx/{N
-@K+
-:-bt
-.8v
-N clT
-L4vv`
-Fon k#2|~L?_A`7Dqz>*!{f+?@Z=2N8ZMW4Kt9c8;Vho:T,wm/5WB3]4C~Z
-N*XgQUHxOZ,xX^)Xeo ~[Ns n)^E ,Zp_e00^nTRl$x_N_AP' l^Z.0 ;8#5B 6j6M@75 /iNL^_CB|-@~~m{*[0-x( 6ó`bbhŸ0 —ˆG Z)ta(Gn`pBU`bY$L@T+sS`G\
-J%j_l7RpGB j;'zlVwk35#lK|Ws~cI#\Ym _m7V.:[EA}5&|g+H2ïÐG÷<?Ûæx¿•©ñɏ«hî g|*«…a…Ñ4‚"Áåô܋ƒ0<×úêú\*_]_†èiñ~W7X'u#xP5 9|wyq5A%6,XzzDtlc"o\>|KeE ? V2 VKc\vb~/'xm  +2)z/?m~]0=p~~+D(rw|wendstream
-endobj
-2558 0 obj <<
-/Type /Page
-/Contents 2559 0 R
-/Resources 2557 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2529 0 R
-/Annots [ 2561 0 R ]
->> endobj
-2561 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [220.025 574.596 328.684 587.497]
-/Subtype/Link/A<</Type/Action/S/URI/URI(file:Samba-PDC-HOWTO.html)>>
->> endobj
-2560 0 obj <<
-/D [2558 0 R /XYZ 85.039 781.388 null]
->> endobj
-470 0 obj <<
-/D [2558 0 R /XYZ 85.039 309.692 null]
->> endobj
-2565 0 obj <<
-/D [2558 0 R /XYZ 85.039 289.101 null]
->> endobj
-2557 0 obj <<
-/Font << /F62 1689 0 R /F41 2104 0 R /F35 1632 0 R /F15 1628 0 R /F56 1642 0 R /F73 2564 0 R /F20 1617 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2568 0 obj <<
-/Length 1980
-/Filter /FlateDecode
->>
-stream
-xXo82PHQ8^mwq;tA[,zl{f8b'J! |cXz>OfQ<lw6
-&<?t:Y\^'&Y_-Z]|sn9sy;?~Y]qgy~8X(
-Ov'xv}cI2=)W''?RhMkVW0qb4 Wb<pnUUjD}YCwC eGmZS{NhyB)-PQ2_p5 fj0@9+[fV Qp5v }hC.Tia[7ryRh1y&Kh_6jum*WF)TW0 @c:R+w Wmn ?9;8H..s~*<LP"]a&Skj4981,/tc|n&h9Yo6kwpgi>u |v5O\VSUe^n pno0"<KF.Q(EI\Ne8kvy&TE.ZL2gi}MUGd/X Gy32H(Z
-wq/b a@L p>F
-/2
-endobj
-2567 0 obj <<
-/Type /Page
-/Contents 2568 0 R
-/Resources 2566 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2529 0 R
->> endobj
-2569 0 obj <<
-/D [2567 0 R /XYZ 85.039 781.388 null]
->> endobj
-474 0 obj <<
-/D [2567 0 R /XYZ 85.039 383.38 null]
->> endobj
-2570 0 obj <<
-/D [2567 0 R /XYZ 85.039 351.854 null]
->> endobj
-478 0 obj <<
-/D [2567 0 R /XYZ 85.039 351.854 null]
->> endobj
-2571 0 obj <<
-/D [2567 0 R /XYZ 85.039 331.326 null]
->> endobj
-482 0 obj <<
-/D [2567 0 R /XYZ 85.039 234.666 null]
->> endobj
-2572 0 obj <<
-/D [2567 0 R /XYZ 85.039 213.773 null]
->> endobj
-2566 0 obj <<
-/Font << /F62 1689 0 R /F15 1628 0 R /F35 1632 0 R /F20 1617 0 R /F56 1642 0 R /F72 2435 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2575 0 obj <<
-/Length 1515
-/Filter /FlateDecode
->>
-stream
-xXKsHWp3T-a8(uR9$9 @e2+=
-}T‘¸ó‹bŸåa—œ¯Š(?Ððˆ2…¿]úç+ú¥¿ô‹H]eyyqTP2 2SbA`jMPG28],rXp Nf+e`@Ga8 0Q& IfwG<}4 s0 š+Û2ñ…WfjF=h];PhHb abYa3RMdjvGBXInYKY8W!
-8cy&w""e2QdUA-u{<Qmi Zy Y<Y_J A hu )r\DF<^Uq=e"q 8p @(.CaRb .*ÊË5­‹
-H%]VunZm]/%<, \I(U(1C4 3x3aFQ<Ym#I}$j jL)O~ 8JHE
-a?A Z((5Fzp}u1ug<=fxA*a(##8rj}t/gKgYf|)"? }ll\x/J(çï=ÔVYY}Ou%?I']iy\MHl:_a+B_=)w~gyVI>?)neu?wma:=mE6R%x4c] Yr<V*B%i?XqnYr9G x^byS .a1<r\tG[zGzh}*endstream
-endobj
-2574 0 obj <<
-/Type /Page
-/Contents 2575 0 R
-/Resources 2573 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2577 0 R
->> endobj
-2576 0 obj <<
-/D [2574 0 R /XYZ 85.039 781.388 null]
->> endobj
-2573 0 obj <<
-/Font << /F62 1689 0 R /F35 1632 0 R /F70 2201 0 R /F18 2207 0 R /F15 1628 0 R >>
-/XObject << /Im2 2261 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2580 0 obj <<
-/Length 1873
-/Filter /FlateDecode
->>
-stream
-xXn8}W2Ivn46.vmKRbKu;R
-+a X^
-ғ~ñõÞ©[^·ïѶÜ</Í£ò¿è
-
-endobj
-2579 0 obj <<
-/Type /Page
-/Contents 2580 0 R
-/Resources 2578 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2577 0 R
->> endobj
-2581 0 obj <<
-/D [2579 0 R /XYZ 85.039 781.388 null]
->> endobj
-486 0 obj <<
-/D [2579 0 R /XYZ 85.039 666.966 null]
->> endobj
-2582 0 obj <<
-/D [2579 0 R /XYZ 85.039 645.769 null]
->> endobj
-490 0 obj <<
-/D [2579 0 R /XYZ 85.039 548.806 null]
->> endobj
-2583 0 obj <<
-/D [2579 0 R /XYZ 85.039 528.216 null]
->> endobj
-494 0 obj <<
-/D [2579 0 R /XYZ 85.039 444.234 null]
->> endobj
-2584 0 obj <<
-/D [2579 0 R /XYZ 85.039 417.619 null]
->> endobj
-2578 0 obj <<
-/Font << /F62 1689 0 R /F35 1632 0 R /F15 1628 0 R /F20 1617 0 R /F56 1642 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2587 0 obj <<
-/Length 2773
-/Filter /FlateDecode
->>
-stream
-xYYoH~Df$f83 0;DKRCRV!v fU_R
-[J Eho3+7}J~WuEfq{O?<Tr\(>/ME]kyYHKcW8[&~d5{<uhS|Gb 4o|DJ~jXP*M D]4lwY|(=Iv!a8`MO,M(3 XgH6dB t,ElNWaKw|#]µZC U
-k#koC-o
-sRxY'X
-{\N^<X[b _ --îkZSQ8Qy/p÷àсåžtïô‡¸oññ}:]d<fáºîè<`z—u®E;%
-Ki4"
-|&#_bel4~yus6
-:6}hU
-[(JloG6Nfi+WLTV0]#8umc  DA*,b<F1*Q2?J_8=Mbmw 9}h@j k #I quqlE79ð
-ñБTDr$f"}m
-#d%q
-Oim~R= k aW?#> (cjD] #?cx8fT{1<62&f2ck^C)4E0yG
-&a/%k. g{^)1}FiypIT\ 2!Ul0 c*3S S+il 1<k'xX6.`m/~'WbKvR(q>T .E@ 2r =)i{pQm [
-)/$=m>c+y\VEJ>UwG"
-endobj
-2586 0 obj <<
-/Type /Page
-/Contents 2587 0 R
-/Resources 2585 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2577 0 R
->> endobj
-2588 0 obj <<
-/D [2586 0 R /XYZ 85.039 781.388 null]
->> endobj
-498 0 obj <<
-/D [2586 0 R /XYZ 85.039 761.463 null]
->> endobj
-2589 0 obj <<
-/D [2586 0 R /XYZ 85.039 646.155 null]
->> endobj
-502 0 obj <<
-/D [2586 0 R /XYZ 85.039 646.155 null]
->> endobj
-2590 0 obj <<
-/D [2586 0 R /XYZ 85.039 596.697 null]
->> endobj
-506 0 obj <<
-/D [2586 0 R /XYZ 85.039 353.221 null]
->> endobj
-2591 0 obj <<
-/D [2586 0 R /XYZ 85.039 328.669 null]
->> endobj
-510 0 obj <<
-/D [2586 0 R /XYZ 85.039 177.406 null]
->> endobj
-2592 0 obj <<
-/D [2586 0 R /XYZ 85.039 148.002 null]
->> endobj
-2585 0 obj <<
-/Font << /F20 1617 0 R /F15 1628 0 R /F70 2201 0 R /F18 2207 0 R /F65 2099 0 R /F56 1642 0 R /F73 2564 0 R >>
-/XObject << /Im1 2193 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2595 0 obj <<
-/Length 3914
-/Filter /FlateDecode
->>
-stream
-xZYsF~P` c\3T"{-mUI Q 
-ldgx36pqp-v%/[G\.V5:r%pieDyJidʫƧDITuW Fx
-zBP {wo`meR<Lxrx{A-'i,t_D~] &&l&B&I4Am|nvZ[}B{)-1V3{:| z#V\!krQC>b9Dxj\ ]M;u>F3Fae+y Y8ve8Z<!~,&XZWnQ-bAg[C{U,rQq+YEJYY
-RF S<»+×\n¸·áZ-@bU99pPMs5Mo kv$kHha9=" k/j#%FqTQ7 Pu[I=R[}jG43 7wByM$ _`S
-Z6{"kt+elT9.bQ`BkDI
-QTVxZ@}x."oJ tL1Jx8}+da,$TI2<7i,mt[>0m=Mkn"1*d,
-#K^|$cPy Qy1/!l*7y;{%8hb5UeH9X||h,<HXGJh982{'n=P;W <=kEF'$b{]% Y6ZzKbINH[
-1_ m\ubLm=noVF|A+Sd&f)IZ5D( HJ-¾kú’›vhùQ+@f=X@3au1Q-%y(cQpO
-DO-YK4+sPvbd0HC>2|+<m[Rp0] {]h4U|#5LI,v,2#^x[tQOmAbP.itMrgiPeIn:50$3(hgCc?h`"y
-sW+[_|P3t+@R
-h&=x+N^xgF*=5( 4r54*Hr,+|N!Y"4B!KPkQd7M"znp Fqc5$i\2X <(_Txi+lP<Byj&IA)mwPu-.[^_y(W2t$ul3GZ=yE7p$
-lmBScu4{ h"CEo}l|0iH [z;xB6E SHnEh}E" .> B;4Mp @Oqp9,4PH2k;$lh NHbupEZ
-(0@g9e<}HZ L 11v<*B)<UVg
-3N
-scE
-3xY"<|u@I=ZVòØå¶X5m[vzo!gmY/^rJh|V(1<;@?"=f9t =v-yGD!d
-_
-w&P!.='0.V~XX6sMRRw5d@~
-4lXrWc ,4`;y84ss,LPa27a2~>
-J9ii!v?d9@y0WEQX:k:u6.|[>xcaSPj
-&K&$
-=-[7s3@/
-vQpw+L'o &.x[dF-x>~<*I),L}XU7dH:m~Q ~G$I2<(UC|1?g
-L<l+
-endobj
-2594 0 obj <<
-/Type /Page
-/Contents 2595 0 R
-/Resources 2593 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2577 0 R
->> endobj
-2596 0 obj <<
-/D [2594 0 R /XYZ 85.039 781.388 null]
->> endobj
-514 0 obj <<
-/D [2594 0 R /XYZ 85.039 555.81 null]
->> endobj
-2597 0 obj <<
-/D [2594 0 R /XYZ 85.039 526.406 null]
->> endobj
-518 0 obj <<
-/D [2594 0 R /XYZ 85.039 349.225 null]
->> endobj
-2598 0 obj <<
-/D [2594 0 R /XYZ 85.039 330.353 null]
->> endobj
-522 0 obj <<
-/D [2594 0 R /XYZ 85.039 96.185 null]
->> endobj
-2599 0 obj <<
-/D [2594 0 R /XYZ 85.039 74.989 null]
->> endobj
-2593 0 obj <<
-/Font << /F62 1689 0 R /F15 1628 0 R /F35 1632 0 R /F56 1642 0 R /F65 2099 0 R /F20 1617 0 R /F73 2564 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2602 0 obj <<
-/Length 3356
-/Filter /FlateDecode
->>
-stream
-xr6_5f}Kt6vD[SJRu=7D!u?u'ad,W*~])Y[\>*
-^b[,}cM>C>~7^xu| ,x"7wqX(&qAÀøÕ»…w¨•‡‘Òxª?¯~û#º^ÁɼŠBSOBU8A\F;4<_ : u y>2Q%L87G*cuBIg@l=v/`, L g^}9Z'aB\3< a
-4&
-_`su YX0V sqhw #o3 g )3M\1910
--Foti65<FP0u? @R3 3.:{R}Zm|F"N$ `=?@p'~ V7jt8FlbW^_a<cl21xK?Z aJ {MtA0 D6`Z"b mm'gm"r#06Q>Z={J<sbXc6 d @W]^
-y n&&J^lSQ:*vxclt0twj SX%-*.lOMe;^#YgyG xT%
-F\6MwSTv]'Jew2,$+5=5)g
-nZ PsUKXk(. B9cR Hcv`$A| g4B-1H m}{ 8k&Zq5
-\]/s3%IkSlOh!iO 4T<|@7xl6`}CA2RphR]Lg)!pj]L
--24P;Æ°&QU^fFP!
-&X`E&DjV7>.^4jGAEDlk#;=1 OU zUze7e!8xVV O[e@kN"8t1bCSayC 7!8iY&5|
-$YFe]SW]|c*@4 =/`H.fo+%oTUlf<U#Bu]4*4t
-a~ +'1` 2lIu%} ?e,Y|p IR;L5Kprvm)yroGgKnU%9d(P GAG)]9.8mh{=t"%.9j;MtXDd xb6UoGuTgR dPphi!‘€„U@+yNp.erYqO1 ,pVq|Zl*J Q!z&Razh5)>*<E_Kp^tFp*2@Sze9Go }pNGo\DtN@k(|x+vQTfBJOG$#%-IQOPE@%B
-endobj
-2601 0 obj <<
-/Type /Page
-/Contents 2602 0 R
-/Resources 2600 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2577 0 R
->> endobj
-2603 0 obj <<
-/D [2601 0 R /XYZ 85.039 781.388 null]
->> endobj
-526 0 obj <<
-/D [2601 0 R /XYZ 85.039 625.671 null]
->> endobj
-2604 0 obj <<
-/D [2601 0 R /XYZ 85.039 594.146 null]
->> endobj
-530 0 obj <<
-/D [2601 0 R /XYZ 85.039 184.842 null]
->> endobj
-2605 0 obj <<
-/D [2601 0 R /XYZ 85.039 138.111 null]
->> endobj
-2600 0 obj <<
-/Font << /F62 1689 0 R /F15 1628 0 R /F56 1642 0 R /F20 1617 0 R /F35 1632 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2608 0 obj <<
-/Length 3479
-/Filter /FlateDecode
->>
-stream
-xZYo6~0eiYk}H&dvvA%GR#b,V}Ulu?u^QP.Y|P_e`gf2.wDse_xr^(-Wy^,~nR->xu_/WP./Z&ge/L'l^RSd?| @`Q+UDJpUk|G,G,Lgp9Q2*4JQQ Ma kG.,[®­Õ7çK6Veq!\ YT\hF\o"D_`{]]w~w(Hzg;A~GmUQJ8R3:)UPhmr#+x@ha.mE2WZ/l-.E Gqene<
-$IN ah}lQ%Sei'&7Ymm\|UA7IMq*Qo
-'2#s4,>LP e*
-{'<`(qLAGxb*d5x$"IM]
-b
-4Gl|Pvw5~_D a & f\Q Kir6` N.I'[yfI j9aFZ -U'>JD+ÔjžËö (ä½¼ãî!¹”£MRAM/nu3A~
-GKeQ2g&:4l6q#32-Gv[_8`^u1CX)fT ^J 4kqE%+{kg
-[8bqZZy#A >\?9HPI[4WTH '·u(™ õÈ{ÊÓ4í–ïyS?(+ (SKqyf3^"h?-M NJd"nt\%H grt2Z$`f
-M'v#5IRH%S6/([:.?Xs8=@$=6tPZ=g% du/5T S#QiT(L( gr||3%8AW9]$dn]j|3 &|skGl b<I[k4au~RxW0ZX
-Q -v/,0IK2Au!oA7@K6^Q@xtlx!1§¶b3¶Û”¶0
-†W
-!\!#C
-ddaCao9 dU /ÄN? kcZpvjf
-endobj
-2607 0 obj <<
-/Type /Page
-/Contents 2608 0 R
-/Resources 2606 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2577 0 R
-/Annots [ 2610 0 R 2611 0 R 2612 0 R 2613 0 R ]
->> endobj
-2610 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [342.345 720.288 409.913 731.978]
-/Subtype/Link/A<</Type/Action/S/URI/URI(file:smb.conf.5.html#SECURITYMASK)>>
->> endobj
-2611 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [452.526 652.542 512.306 664.232]
-/Subtype/Link/A<</Type/Action/S/URI/URI(file:smb.conf.5.html#CREATEMASK)>>
->> endobj
-2612 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [111.316 598.345 206.209 610.035]
-/Subtype/Link/A<</Type/Action/S/URI/URI(file:smb.conf.5.html#FORCESECURITYMODE)>>
->> endobj
-2613 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [427.522 544.149 512.306 555.838]
-/Subtype/Link/A<</Type/Action/S/URI/URI(file:smb.conf.5.html#FORCECREATEMODE)>>
->> endobj
-2609 0 obj <<
-/D [2607 0 R /XYZ 85.039 781.388 null]
->> endobj
-534 0 obj <<
-/D [2607 0 R /XYZ 85.039 244.172 null]
->> endobj
-2614 0 obj <<
-/D [2607 0 R /XYZ 85.039 196.836 null]
->> endobj
-2606 0 obj <<
-/Font << /F62 1689 0 R /F15 1628 0 R /F56 1642 0 R /F65 2099 0 R /F35 1632 0 R /F20 1617 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2617 0 obj <<
-/Length 479
-/Filter /FlateDecode
->>
-stream
-xSMo0+1!4tJ(ll`gP/<3 .ALJ6)cdOp5E;%%<! S54|qW-~B0?yYY;+rF]gUKC]%RZnB(L&fY  -Q0 ~{4L%<3$ #\yBb1/e&hzwb
-endobj
-2616 0 obj <<
-/Type /Page
-/Contents 2617 0 R
-/Resources 2615 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2619 0 R
->> endobj
-2618 0 obj <<
-/D [2616 0 R /XYZ 85.039 781.388 null]
->> endobj
-2615 0 obj <<
-/Font << /F62 1689 0 R /F15 1628 0 R /F56 1642 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2622 0 obj <<
-/Length 2838
-/Filter /FlateDecode
->>
-stream
-x]=b> ,)@P5]phH^V"K>In}eXp8&_|a,CWj +?="Iu& gvuRads0* U* ~}TV o7 b.iq6Eq=.qU0lK:j
-~1CkoGI_L0O GY^Z
-]]"J]IgKh'/niD`)J:+ I@$oZZi6 woS/t,@8D9!,r/||$f]7
-50iW"go^E& d+*NdhEm1$Z^
-3p %d<
-zBHzM>BWrBQuksGa@_&/q![hdBy:x 'bEB("tbU0m Wku(5RMvoC*g lM}G
-{"WP-un-J,
-#R81!,9YsCs$O\35rdGB-%gza D0fU`8!6QS%[rs<8_gB+FWIk Y@&+g)+;I!Hr81/S^+(wMnkk5Es>v=DQM/[|Cwo[>RENEoF!> r+~M,~8/P5%3avd# W^<#)3G/9n22id8fgp9
-\c<5.BRq<"~F4>AV8Ce5$E%J+%T: u "">|F-/)gWNE+O)!:SH:C^1&$.j
-E9PWg[dPr e $a3`_xy=6&n}o /\b\z/F?iR)Jve.N +k3-)Zp_X87Xz8Y>19lGj8U\A]M\}xMN&'BAH5a0:!Z% hz /~gBJ@`.T|W^(:P9pb6n,rHhjb3q/3z;H}
-~*pD$7q)P.$_B1]=K<TP1d!d&+]sF
-,C9Z@d $0a:,,3>cuiyU|E<y"hQ!8S|@HEE%W{d
-endobj
-2621 0 obj <<
-/Type /Page
-/Contents 2622 0 R
-/Resources 2620 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2619 0 R
->> endobj
-2623 0 obj <<
-/D [2621 0 R /XYZ 85.039 781.388 null]
->> endobj
-538 0 obj <<
-/D [2621 0 R /XYZ 85.039 761.463 null]
->> endobj
-2624 0 obj <<
-/D [2621 0 R /XYZ 85.039 667.089 null]
->> endobj
-2625 0 obj <<
-/D [2621 0 R /XYZ 85.039 390.616 null]
->> endobj
-2626 0 obj <<
-/D [2621 0 R /XYZ 85.039 367.529 null]
->> endobj
-2627 0 obj <<
-/D [2621 0 R /XYZ 85.039 278.703 null]
->> endobj
-2620 0 obj <<
-/Font << /F20 1617 0 R /F15 1628 0 R /F56 1642 0 R /F35 1632 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2630 0 obj <<
-/Length 893
-/Filter /FlateDecode
->>
-stream
-xU[<}#k.< -]@MK%MKJm ~<4e2Se X{ *GOWDjgMV(R.hiF{{q*9+;}{p*)ygn%HJ$2?[ :`TY<@iI~]y-+‘PD2ejN?F$Pjy0M LU#.q&-JiqY(CF"#F=T*[&@#tbDqvka\u[c]:(\n>2E&3EÌyJ[TX41g;#?3MS!l]lrK6LzS>}B3_-[W;?hE ,'¤^´¸ﻲWeM\!$d!vjwk`g$JiLAurRRH
-RoKd x BQ2*N+[A%4O=2<J)r_`,xT3ea3X [#w )gr¶mª̆ÂtÃèö¾0Í®cëXpRS2s'B*1
-endobj
-2629 0 obj <<
-/Type /Page
-/Contents 2630 0 R
-/Resources 2628 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2619 0 R
->> endobj
-2631 0 obj <<
-/D [2629 0 R /XYZ 85.039 781.388 null]
->> endobj
-2628 0 obj <<
-/Font << /F62 1689 0 R /F15 1628 0 R /F56 1642 0 R /F35 1632 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2634 0 obj <<
-/Length 2762
-/Filter /FlateDecode
->>
-stream
-xYs!j9I|;>9"eD/PD'oK3&XoWz$m:lL+3?]iB " 12LR8^]4*nEwO[5NWOg+aktf[{i~@n@zTx|d9ReAt&FiuEbe[V šnS_XP-TLxGvxjqar]lA;Ti-/NM=
-R:DuF$qV)H`C,rd 2[`Y~}_*>zzoP# &X9.Y7-Y),e!rZ">!SuhFg¯j‡Ç²WiG(3s72:n/qlqU$[_; Isr0lcBS;z +<b!= E`Vr;6_<}+c#e#lt=r~@rlSaokZ&Vp6nS)D-hMY:'+[A`h+~7F24MlJ;g<{UlSmY= ]ߧ+jÒôdЄ;eÍS P&G1N:ypZ1]#=Fw.:`D~MyCgiwUuD&v'àD(c_AQMuB<oXh#L „ý棅¡ÐËðC`VrN%`~@vgo0%zV5R
-sIZf:. )7LPq]k~qqh2UT=%>c:\ BP`/\8dNEUaid$Xde1`b]5=bi^#.CvqbPk
-A3
-H8,4%l e@Tr{/q'2E:rAz0'8tse8zR+)MF] \M\tIEF7
-eP)&g})FNr)l
-@|XG}Nl2 %0UN~R(4[f{L6T/aJGL#jqJCCWeeKV*'mtLJ=}EL^WI6U6et2rnëâ‰ú¶àøýÎ6Bg6Z0s!.^:UB3~4k
-¥2pŸ]·> ‚ËüöaïøÑN!zA3f dv*;#[f;w Þۍç8×ORXlDo,.
-q`i~lB[<O0|Cu\wB
-nx9/43bd%!!%/X#?Sx."ezH=k-@P9w{"6F+o*B,d+C2@F+sFsUendstream
-endobj
-2633 0 obj <<
-/Type /Page
-/Contents 2634 0 R
-/Resources 2632 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2619 0 R
-/Annots [ 2638 0 R 2639 0 R 2640 0 R ]
->> endobj
-2638 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [297.013 519.753 476.549 532.655]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://imprints.sourceforge.net)>>
->> endobj
-2639 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [343.406 485.661 494.306 498.563]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://msdn.microsoft.com/)>>
->> endobj
-2640 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [122.225 316.898 479.305 328.89]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://support.microsoft.com/support/kb/articles/Q189/1/05.ASP)>>
->> endobj
-2635 0 obj <<
-/D [2633 0 R /XYZ 85.039 781.388 null]
->> endobj
-542 0 obj <<
-/D [2633 0 R /XYZ 85.039 761.463 null]
->> endobj
-2636 0 obj <<
-/D [2633 0 R /XYZ 85.039 669.619 null]
->> endobj
-546 0 obj <<
-/D [2633 0 R /XYZ 85.039 669.619 null]
->> endobj
-2637 0 obj <<
-/D [2633 0 R /XYZ 85.039 644.901 null]
->> endobj
-550 0 obj <<
-/D [2633 0 R /XYZ 85.039 302.385 null]
->> endobj
-2641 0 obj <<
-/D [2633 0 R /XYZ 85.039 273.284 null]
->> endobj
-2632 0 obj <<
-/Font << /F20 1617 0 R /F15 1628 0 R /F41 2104 0 R /F35 1632 0 R /F65 2099 0 R /F70 2201 0 R /F21 1620 0 R /F18 2207 0 R >>
-/XObject << /Im2 2261 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2644 0 obj <<
-/Length 2829
-/Filter /FlateDecode
->>
-stream
-x]~
-x$-4qAaERcIW!>KJ =h9;+~*\Oe$]pv o^w7?V[By(9oJ)W:IRyn;/_
-*dh(` tot^z):=~" %f
-7q‘Kx2 chJ%l(TS0E=3UY
-!jBn/-?dx!{Pc$~2\>lpe.9/h}I22=1 jZ"VP BE 3k"Gc%$F]5 uP*t2pe?Cy+CU|6d=5\7F Hgxu>aGwfCe#G~FqNx^D?JW
-hE@HG9B[T_I9CpM% F<:'viazQs~0T2SBm [B@qcRF^29%kymY8v$Z_.$-w=/6Y )epa
-f"*6&3F9FRIOk#$!/&3_%BS%)w)q%|N=_\L wçĽËú-ÂÜ8ˆ¼*y]úâ!•…+UzR55F0819H '%LE)nVl|8'*%&3[cfNj=O Hr* Y!EeÁ—‡L*
-KyWjdWen
-G(m|IK]DiC ?P9)>=5 vngNXZ6"1
-G#*cY
-.tw&$*D:}|!e+`qK@rK~j]gKaC d*$'$il'-aSiIcRabDT6xM^CRXQP qC& |?SyY8#V.2z\~9saJ!7F_!y ,xS:m)KCxE/@1$kBp`N
-?(;|| M0?}}1Fpv>iO,@}2}cg?opÛLi!
-a!Dq'g'<ne!lä ólIO50GA 2-ue{29GS|8uD } Ra(z (v8%G;sL27
-=
- 6\=0pcMO[^m?\ 2endstream
-endobj
-2643 0 obj <<
-/Type /Page
-/Contents 2644 0 R
-/Resources 2642 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2619 0 R
-/Annots [ 2647 0 R 2648 0 R 2649 0 R 2650 0 R 2651 0 R ]
->> endobj
-2647 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [145.77 354.89 191.399 364.458]
-/Subtype/Link/A<</Type/Action/S/URI/URI(file:smb.conf.5.html#WRITELIST)>>
->> endobj
-2648 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [361.036 338.614 468.425 351.515]
-/Subtype/Link/A<</Type/Action/S/URI/URI(file:smb.conf.5.html)>>
->> endobj
-2649 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [222.711 312.121 306.494 323.811]
-/Subtype/Link/A<</Type/Action/S/URI/URI(file:smb.conf.5.html#GUESTOK)>>
->> endobj
-2650 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [349.617 123.446 454.872 135.136]
-/Subtype/Link/A<</Type/Action/S/URI/URI(file:smb.conf.5.html#MAPTOGUEST)>>
->> endobj
-2651 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [155.951 109.291 180.514 122.192]
-/Subtype/Link/A<</Type/Action/S/URI/URI(file:smb.conf.5.html#MAPTOGUEST)>>
->> endobj
-2645 0 obj <<
-/D [2643 0 R /XYZ 85.039 781.388 null]
->> endobj
-554 0 obj <<
-/D [2643 0 R /XYZ 85.039 761.463 null]
->> endobj
-2646 0 obj <<
-/D [2643 0 R /XYZ 85.039 740.47 null]
->> endobj
-2642 0 obj <<
-/Font << /F62 1689 0 R /F20 1617 0 R /F15 1628 0 R /F35 1632 0 R /F56 1642 0 R /F70 2201 0 R /F18 2207 0 R >>
-/XObject << /Im1 2193 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2654 0 obj <<
-/Length 2984
-/Filter /FlateDecode
->>
-stream
-xkoFN(P
-hGDV-!Z-(R!)+.<vIJ#rvvvw3;rvD4
-Ba8Zo/p53+G¹Ž9ÑhuO(v2BX' ngdZ[]bqsPXSiK__.>}vF  Q8:(m/B_Z*<'Gj^S@8v`%G8u!{2†xµAH`JkD "'QaIhc^\5Wh*<K \0j\!u!]o.fReDjBEQ ]]Do5NZ[Bh%i5d<^<
-o4CRblS4F{ yGl!8:jv0SeKg(qñ!•¸bÉd-ã;fŠ0€ƒÁl¹§‹N7UtCVo7(n rZtt
---~:>^M|jmk `dU Yu?[8NblTHG|9(ix=>G\z#?YB=KV9@G0v7P{En}u =_nu{ ?
-y#B.,Jxt
- t`IBxn9T<`|d7=ReYxD|ÌJT/rL8 F>.:!r]3B#2)O{.(YH|9
-ym2y1 SZ4*&0))m\M$bPlJ?};$$csQF\'4tl_?8L1;qQ}jfS
-  nKcYJ@)02+5 s_uY+."T^ScBuv7}R'6YCgS:r e[B8)LB?M5kHsHRxM2GEm`^7O+01^-XL9p,r;Nta8'm7Dvm1B
-w9[D-A#$9S>)Lm:1)=L47
-`<*^8xiEa)sCW5v@{1KB>;C,w0i60@ócwîaîrç÷¨‹ØäŒjS™Â˹L ?!uJJUG]w%
-bR#^;xZP\VYsxg:YQ7sdCO +Z)+E0m1`"(p#R(MX8AiÆÄê†ßqt!žÙ˜-ZFQ:~C'^!S:B@+'B)WDgzCS%NMQ ?&7 UH?DJql=
-_O]cT0 aAve`KG]ªßR*>:k ,('b'i8{Vk|ZAciwY 6+VktW]*FqqtOckZ0%B31}m?F@b;kH\5õn½@d/4o iu$ [9gm\O D1usd8> 4|$n3gDjQvcDFcJ/mW>W> Q:aQk7a@MxMT7z0^nbT|VƝèu¾µ;ÉqþÛîùX\`T9,4OÿXk= c?o<K8G_%endstream
-endobj
-2653 0 obj <<
-/Type /Page
-/Contents 2654 0 R
-/Resources 2652 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2619 0 R
-/Annots [ 2656 0 R ]
->> endobj
-2656 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [254.042 503.917 317.277 515.606]
-/Subtype/Link/A<</Type/Action/S/URI/URI(file:smb.conf.5.html#PRINTERADMIN)>>
->> endobj
-2655 0 obj <<
-/D [2653 0 R /XYZ 85.039 781.388 null]
->> endobj
-558 0 obj <<
-/D [2653 0 R /XYZ 85.039 326.218 null]
->> endobj
-2657 0 obj <<
-/D [2653 0 R /XYZ 85.039 305.021 null]
->> endobj
-2652 0 obj <<
-/Font << /F62 1689 0 R /F15 1628 0 R /F35 1632 0 R /F70 2201 0 R /F18 2207 0 R /F41 2104 0 R /F20 1617 0 R /F65 2099 0 R >>
-/XObject << /Im2 2261 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2660 0 obj <<
-/Length 2270
-/Filter /FlateDecode
->>
-stream
-xmoH{~=RMYX0DO^OlP1
-_WR$7II
-Q (,G
-.j,iRFtWuy;) l1q f]*HtICDYhJ~GI9 6r.#!!&S83rX~H3 +uDa@.2n\1X2 u:9|A`~iÓ°ç \Ä
-•*ÈU
+1F`^H>SGF`Y#;?
+=Dn*{I`Uqg6zTjA!wghxEI#^@2v2H-[*R6 y?N%+!k,$%aPth0,dRK0HEw7WT1"MVKSFb+bbda+c qZv%=3TX6J ~4Y[]!AvB'Gahd2aVXLIC0tX50syzO2Eë<È4rÚ²2ù°‘V -MW,T)RU2=F"0
+I4y8M]#>0jii
+}B%e||Z@zmXx K8tNO'oR?z(vj @ #6Iuwq}óùö†¾5†]º3Y[!^8njOW^"Y-d>n>4endstream
+endobj
+1637 0 obj<</Type/Page/Parent 1476 0 R/Contents 1638 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F6 8 0 R/F8 10 0 R/Fa 12 0 R/Fc 14 0 R>>/XObject<<>>>>/Annots 908 0 R>>endobj
+1638 0 obj<</Filter/FlateDecode/Length 1956 >>stream
+xXQs6~2c,K!IN3~HBM,ZvAB
+v:& .Ehfj4x~tMzTlnFzs=K"[WXe ZW7vnAmvz^`<6xZI9AT+)<)&|R[/íkg±Ia+&W8K+tnhJU6XeTR~ Cc^{SNVyD~kW.^:'JT7.?,>g/E#",: ¯Œ¥ºT)" [WhuYmHWd<%x
+d$KbORO&^TjI2 h{O+3Fr'u6Zpc;ci  O_n
+(62:ds/gS
+ho <EOd
+@LI !9Gm'!96"V.
+v(C%hc*.0݉fŸÛ˜McMPwn* s)MGUN)R:ia?]gDj([8b[+x'Xo^xu.YMqi@9yy9g 2z'q 4Yh02$Ovqb!: ]ye*CP
+endobj
+1639 0 obj<</Type/Page/Parent 1476 0 R/Contents 1640 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F5 7 0 R/F8 10 0 R/F9 11 0 R/Fc 14 0 R>>/XObject<<>>>>/Annots 913 0 R>>endobj
+1640 0 obj<</Filter/FlateDecode/Length 1477 >>stream
+xWMoFW |r%YR
+`IkJFP".%Ri
+[JcUD_~vP.L6IwR+}GjF&B>Z
+|r)h7t2JRjF0{.jY*+Jg"/B>Ku:
+B[y>i$z
+~Cu
+/\a(C,{*)1Y8;n"ZpCiDE91nFb52<{kpjrQTGTb|RVu4?$I4)A=OM|?#=2{"`]* l
+")4a?=\3Wxzi?_ 3f_%M)(R9j;Dr^J;\X[P5FZtbtYKpz_pRiV &}qcwx`cL=gDa`
+_l px6v_;_thDQc
+-y'Am
+Mm
+x;Msm/ M yZL1C 9-_\w7jAI!acdMSd?-8Dendstream
+endobj
+1641 0 obj<</Type/Page/Parent 1476 0 R/Contents 1642 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F8 10 0 R/F9 11 0 R/Fc 14 0 R>>/XObject<<>>>>>>endobj
+1642 0 obj<</Filter/FlateDecode/Length 1199 >>stream
+xV[SF~W>H%Kt$}6-d:YKkDu+ÿû~{‘± î%0€iÏí»œývÒ§¾û4Š)RV &I8x1~N '0~h$z7~#JsB^<-JE5+Y". ]YUr]{Zm(>S<X/Hp|gg8S-xeúuö)QV%SRCc.6g(glZ5++up}%R/?am)/7Gbf(Rs RW2NA d]sH*W8ma~6=DJ|]G (#9Îr’¢2SQ,mv
+VN~(Eam Hz,3fdMfTvF``;V`(`"CtjP}} eU{DoKyCmhC#];.qk0<Kn
+endobj
+1643 0 obj<</Type/Page/Parent 1476 0 R/Contents 1644 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F5 7 0 R/F6 8 0 R/F8 10 0 R/F9 11 0 R/Fa 12 0 R>>/XObject<<>>>>>>endobj
+1644 0 obj<</Filter/FlateDecode/Length 1698 >>stream
+xWMo8W rru7- Emvq+*)o%NE|MsA)]^QVLz7Oiv=)~<MW'o+_"'lt[..Y` lN& Og022:xWG<;!Xfg>? uSX|iUo5!cK^ZM&#4%[[9h‡X44j]A7 Ph _~ Kj+N6K}*vAm)W3Gj9 pX kk9g$L\Ro,>BN%*jPLYDHRCPH7t]
+5~u
+~+$[<} y).l<[u"Ÿendstream
+endobj
+1645 0 obj<</Type/Page/Parent 1476 0 R/Contents 1646 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F5 7 0 R/F8 10 0 R/F9 11 0 R/Fa 12 0 R>>/XObject<<>>>>>>endobj
+1646 0 obj<</Filter/FlateDecode/Length 1688 >>stream
+xXMSH+|2&^ö²¶ØJ¼É¸Œ¥šEhgF3-Rlf_noFz(?8bt'10Lf3Z%p8]*&88>U4Co<\*^kA+) g2Bd7f*f(YCP6*¥É•µJ6{tDBL.U&uT iÓèngkÔ76nžœÒe¦¢'f`ÓÒÚà›¥ª$°Di_p&T]Cfw( DNou!M^St-31T6hd_}rp0K!rfs)L-\
+El D,P
+kk Zo7Jak!p$lUWNlS_UC!e2Z0 mtj0B7F<r+3: AZ!VIWx6X%Cx
+F\Z ArDv
+JlJln1jqY\ZY
+0cKFW[$#KjU#H["frhB@Y|QI(XBH,e =YoV$
+{i]]D#ßcò2U0<!m7^yP^-C}D_&\"h. E:olQ
+H>,( f@pYe/?/A'+[ygv)Y4DD:=*HZ'4xNn* a)U^9,DCh?|y
+@]~,}&Æ&ÁÁviÔ÷6â Å9›kh³0@]5EE:P;ny>T{. E' r)
+? O7>(#y|! mdT< ~nb(2Y00jXRmt&A$ 73Pr|4zBmmMSY]m_#2*T-_|`Lv8kbr ^au2gyAfpuoY?nx(7XGn9 nmVf$bF}]tqA;dw21fY^yeO,/!F[ZCYo [hvvmLԆU 9_) vx
+ykQžp
+†ú¨½~´<>Ûî³?ÿJ>_)^kdW?L@endstream
+endobj
+1647 0 obj<</Type/Page/Parent 1476 0 R/Contents 1648 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F5 7 0 R/F8 10 0 R/F9 11 0 R/Fa 12 0 R>>/XObject<<>>>>/Annots 918 0 R>>endobj
+1648 0 obj<</Filter/FlateDecode/Length 1633 >>stream
+xWr6+vt2c-KroJ4vk|HPBL @-
+?Kgoiu
+H >gyBx<F7}JR2IP+mTJ+k.wt]\-9{Eo%a1xwNb-3ILRE(2~;g^#8O3;M@9Jù*Í9€tüe*W[ 4TH 5RG"UT[iTs
+IIÑñ‘ra_ËEY:¥»‡'Ue
+<c>O{vBkbQR2<!\'Id{ci-Bdk+UDS+.,cyPUm&x2g}QXU~V?O\+( F2AXD%7D<h-t\3#B=uyh*`FE'
+™e½£¡ 8Òú‚äÃ^§^Bl'l?)3Xci3yL
++\Im~;jyFYznT _Y
+J.s8wXy2Y9Gd 9.*V%2"P9@J6nu!s<:+R@0XKi&JK1L&=Lb`$2X.9eF/;JtvEf(sF;5!y xWCi^FmDU3V "w8%/t[:V;75!uW1 pBm m%H !]\vyqPox] i-;6}}Id* &Pu5
+endobj
+1649 0 obj<</Type/Page/Parent 1476 0 R/Contents 1650 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F6 8 0 R/F8 10 0 R/Fa 12 0 R>>/XObject<<>>>>/Annots 927 0 R>>endobj
+1650 0 obj<</Filter/FlateDecode/Length 1305 >>stream
+xWo6~_qoqTv!}%*f+H}GhIb8;}w, tQ/$ZjTur~U,\cwmtC7u`~duIds®±»ÜôšX[ 4ilnf$e?^DvjlgWKJmY6shMY+~zvlYY%tIZNYC"|^zdd.o9N2#aH@^(^yX%Gw`urxt/GyIHW5.k-4 /5F]NY)
+*[B:Z:snEd'J0 :P/*s8 >*Q-Q; :GH[1X*[IeV{(':S]=9\u]d]CM
+; kP´.Õ~“_mëH'\k\~BUhMg'R {0]{aDAT4TcYErM9KNCg?1gUn<} F }A8x
+LY*(^J{ ~t1{wU73 j\<VMDI%E]N.t 0AhgSs
+endobj
+1651 0 obj<</Type/Page/Parent 1476 0 R/Contents 1652 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F5 7 0 R/F8 10 0 R/F9 11 0 R/Fa 12 0 R>>/XObject<<>>>>>>endobj
+1652 0 obj<</Filter/FlateDecode/Length 814 >>stream
+xOo0 DO)v%S`n"+V[$A%;K]6"|
+WrJvg9-lNw6l5^;AEA%!OS)vJ
+tY4.P뤢£[)¹¾›‚w
+B:*%*
+µ¢­p¢UA9T^vcjDg) &y*\2 Pl>S WWmtH QSVl<'R '%u0Ixp5/.jQOVV{s%u=bMrb@0F$4Z| ;LwxYBWG9xJ\lpo>Q%|CTADFBJ=DHihHqJ<#? ~bR}3:#jz=C&"0 GyV^#%Daqs:9 
+eSQjFD
+endobj
+1653 0 obj<</Type/Page/Parent 1476 0 R/Contents 1654 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F5 7 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+1654 0 obj<</Filter/FlateDecode/Length 1451 >>stream
+xW]o6}@6Z#iCO+![hDK[IC~sis^ZhZV4+f3[|Qjúòî3­¥J9o*xY~X}6WK8R{+@b"-U)27suX! JK{/i>o.+thVO*w% G{Y™Ð#ž÷·¿ÑZ4
+ir/I=j]"%X
+ yP$02 y{%a3&'*+U8g@VdzdTR9^F8Vx
+
+A^l5` 1?ƒ
+÷6|Rm6QBvQW(,/Y(WE%V@YnVI
+! -KuCdunIAWTjRuh+X !!acO@qKP
+%x)4(^HVsQR( UjLaB</APZ|_T1}I5To+!wru2*GCiLF0Wh;'BLyr^_7fK4r (MC] m%L"&}t;wlt/H VG'9)Cj(pnT=;p,I<2Uy1Xf9HQY`hmub7WUy(?\s=5>"GYObW8o$<QpPS9^hCeimHS^{'v{rq ^|;qso;FVszqcaKkay?# xQ3{
+WgxMvq>W$=7+c\q5Wendstream
+endobj
+1655 0 obj<</Type/Page/Parent 1476 0 R/Contents 1656 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F5 7 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>/Annots 930 0 R>>endobj
+1656 0 obj<</Filter/FlateDecode/Length 1633 >>stream
+xXnF}W PQ
+ rv.g wB)]P\\#:yhv;S3R~~bvMzMU%7 "9-nU6 %>^.>U_G\FQDo:2z'?rLR:i8fPw[,d*z[X}iK'TN<hSG3el.G|ALL{:m*I"iT[3u,eFQkes FNL/6BUQrbJd%D+>Le!Jp,[]ú­TOUY?Q'K=zi^]n)s-=oMrDQ,JZJuQ<XUP42IWdI.Kza:RMs\Dov`bdj}B.JkXE%~[}22=&(HeZ_!40}a8|4n xZT5B<9*_ <VeD1L:R#(:Kq F0n`7f 1y7^+Nd*12(be]mp7 \-GVQn"p:YLk34!u(r;`i1&EK!HH3i;N\3 G# AF*#:
+QR 4b=dE2.Xufx\|rfU|aDr;)dkz@^QH[_ E%_z9XL1yN\+K4ho]i3d4=ABqiM }zM"
+)sZFL'rP[ 5GAPbA@.x(BER(
+W.Y>ijC5[(&w#QZ@P&*^7#Mf;jD?c B5v2HXW;M2Q"WB(]6 ],KU6*=[efr@Vr1 42>k \z4'"O6_HwP-V-jV
+^dm#x-qq WC)X{EyEU 7k6G^2f
+o* J$kX&:cbfN}6^ qe?a+o1dpLgY4/
+endstream
+endobj
+1657 0 obj<</Type/Page/Parent 1476 0 R/Contents 1658 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F5 7 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>/Annots 935 0 R>>endobj
+1658 0 obj<</Filter/FlateDecode/Length 742 >>stream
+xTMs0W[
+endobj
+1659 0 obj<</Type/Page/Parent 1476 0 R/Contents 1660 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F1 4 0 R/F4 6 0 R/F8 10 0 R/F9 11 0 R/Fa 12 0 R>>/XObject<<>>>>/Annots 942 0 R>>endobj
+1660 0 obj<</Filter/FlateDecode/Length 1411 >>stream
+xVM6W Cs v“ºÉ!(Úuu”D[L$%);}CJdQh$97fLiSZh~KY5$/ -*ZEQt,gI2j+gm2wp:cOOqqf}O mvvM l/-M 5+'AUf3;OoV9U)_l>&4-etv^Vd4=*lp<g0FiB4WFh@
+a)W KovnU.<+ /LtT;@)WVfX%CCj'7I;k
+ sK
+
+*Mu%0t|[457jl]o"H_#p<-Q>v8N%jH(K?3wv`JM2jhEb:5W{~uO6d<LWuE>2tUC@&2HKt: 3#Z(l+p1$
+BgW-n_`BXAsj:zj9M&~Y6G"UPLc2_7 eepEnlO"ALz# 2+zzx{.A@^ XKf3.YFptvL'TG#DmUqb\(ogC<6eZbA[/vx8QzL{V&rZj;BVXBM%(uCM#.AX[VR*kS>a%,`-/:3.Qya\A"T)!m`@3uE0+~%eqLRU*E#,GKhBcR)*„K{ XQ ys&jb,Vdu{)w`?o endstream
+endobj
+1661 0 obj<</Type/Page/Parent 1476 0 R/Contents 1662 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F8 10 0 R/F9 11 0 R/Fc 14 0 R>>/XObject<<>>>>>>endobj
+1662 0 obj<</Filter/FlateDecode/Length 689 >>stream
+xuAo0 -j7v=rvEZm,y~OA ae7"d=[ ZtEsc: YfEYFrgocO 6jC<6:^W IE>I{^m_f J5ngz<Dt&yl') P(8)2:dyUO%vDuv"4,eNQxv?288-@F&he@,f7ØÇà¿C<NmKBo J -B jm=5&Q%iOPChsc E}FUxYp7e.A4OIuAuV+v&A u7QclQ<)mN
+Bn
+endobj
+1663 0 obj<</Type/Page/Parent 1476 0 R/Contents 1664 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text/ImageB/ImageC/ImageI]/Font<</F0 3 0 R/F4 6 0 R/F5 7 0 R/F6 8 0 R/F8 10 0 R/F9 11 0 R/Fa 12 0 R/Fc 14 0 R>>/XObject<</I16 16 0 R>>>>/Annots 949 0 R>>endobj
+1664 0 obj<</Filter/FlateDecode/Length 1649 >>stream
+xWMSHW5UXrn]v9Dd/z4cc
+%AwG r.P<I33m{/Ic>ZR{h k6.'
+ >^x6L+8,8Yf3Ft_QMJ}6wNq8
+jjit=(rG12AUݨfIR".B
+#Oh* 4D%EUVt)*eJC\U#3v?AZ >_XnSD)3Zsrtkh-kL 'nDu+m({>SQ&pj@fHWdbDAy[YD'kZn UEI or]@
+-2Fzf5)Wz<$, vZ(g]2Y*)W+`$HfqW+ |EM;Es! 2?&dKk3i)Sy9FY Cb:AlP.y!92GQ2,
+J R] h
+y#x~!x|s2nz,(7\[C^|icoc5z7 ?RU[th4ZFrmuA3TX,
+I\.b<
+YRVdt` TWyDb6K2*C+t,KhT~qUUHNg]N(F,iWKm`5ymg;Q 0=r5WYGz<jU[Nt{"FG k(w'{}p'8
+?-K}X`x>a5\KH&zbK&@707|w4e*xw#zRIi- &{v^=|yD&=
+m!1';v6hmI|Xo3
+]m{ 0}r`ZPhJ*'o}
+endobj
+1665 0 obj<</Type/Page/Parent 1476 0 R/Contents 1666 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text/ImageB/ImageC/ImageI]/Font<</F0 3 0 R/F4 6 0 R/F5 7 0 R/F8 10 0 R/Fa 12 0 R>>/XObject<</I15 15 0 R/I16 16 0 R>>>>/Annots 960 0 R>>endobj
+1666 0 obj<</Filter/FlateDecode/Length 1816 >>stream
+xWkoF_q[D5
+qX*^,FXdBr;CR:> xi63i6f!wi-h rYKwbA <8Op9SE3.==q;domt?[Esk>kdq̀Ññv2¶ @(w+y<9wi
+R:kT1W=©ÂfÒòÄ£µt ¬í~OW#Aq_h_Zk -hgN[.
+i dC9: vL\777K?D
+[4b.0? xLendstream
+endobj
+1667 0 obj<</Type/Page/Parent 1476 0 R/Contents 1668 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F6 8 0 R/F8 10 0 R/F9 11 0 R/Fa 12 0 R/Fc 14 0 R>>/XObject<<>>>>/Annots 963 0 R>>endobj
+1668 0 obj<</Filter/FlateDecode/Length 1715 >>stream
+xW]oF|X
+M+vCItq|j9}7+`Hyt>"{sE *-UQLzGIaV4WRlE'46wUiBeQ_/tG4[l48U^R4sg'z;T g"NamY»͞N!4qI~4?,`LK(0í¨à¾G%NUqeRul/. q`4m&Mik+j`]LL 0qlx:OEIB56*Bt{JJUO/%(ckbm18B_
+]P$,`GLm`S=9rG3uCv<]E]xH!N3drhJI1B\L2rar% Y.h9a5 T..D~ !Zr
+5gWKbc\EJa-=v'@B1|]CDo[]}Y:
+jGoh[.Jvo+W)zd4y
+"P;8EfP$#$()&k-m=P*1qTuVfex] oP,04FoJ_29wmEv
+ _#_-&5v4HH*4V0B4@ShbKU
+!hk  SfeUh
+ OYDGz|
+%r(S;#`#:h5)&'Z'GR9f.KZPG"VuUTf[T,7Zbg61}7G)@>.|
+e W "rp/_Z
+=-#,+g#&O|gIY32[d+\5#1 l_Q!]5 \KXnOwox~u
+endobj
+1669 0 obj<</Type/Page/Parent 1476 0 R/Contents 1670 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F5 7 0 R/F8 10 0 R/F9 11 0 R/Fa 12 0 R/Fc 14 0 R>>/XObject<<>>>>/Annots 974 0 R>>endobj
+1670 0 obj<</Filter/FlateDecode/Length 1800 >>stream
+xXmOH;5
+zG{C^!p&K
+@lvwg^"
+0b/ B|u^4 c.(zArkavz>GC xYP?l[4A={(bmMU]cw[cw#Orox Y13SP? v5va 6n!8m9h ^c`(8&PlelVN{=;|s 4] #0
+it`EJ E}+\7&F $<+!©sYJ^Ij$LncI
+Y6TdQDVT)eJ"bIR.s%R sh^0|}}N]MS_}b-Zr0ZVx0L7/PtS*%[lVEZ=`Y*DCu$yU+QE!1Jdk/ UF{u, WR7"qh
+,T5(`S+@R'[H.j~2DYz0YYjv182LYf
+@t{(:i5B$Mw0KmTo+e!VysXYJ\(f%bV`Z7Ac%>ka `Ki*k`B)E0etMUg]-JSg1}V- @9\U 3`7*JpYAi7]Au/eky(M$-fAe^AeN|R%O8N7q;ÌÎ_¶‘‘´Ç»Ã`„9­ån†­œ<³¿±Ü°"À!Ððpà†ÃW w`0yF3fu15o)?PPL07kpo"=K= Øm¤Z =9&x)V;W HUZT+Oi8"A7h=lS}(LDbDvc\F#0|w-#/Pbvc*/[2M)D-Uc"k(Le&]!{#C-+QsXLs!;CEJ^vZ2C8k P&\ d]w,3}uh 20Y?WŽÖTe}K5Zi 5adlw`%C0<*.e>8~Me.agSV
+endobj
+1671 0 obj<</Type/Page/Parent 1476 0 R/Contents 1672 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+1672 0 obj<</Filter/FlateDecode/Length 1149 >>stream
+xVkO8_q#V&MHe
+e<@L}}fYAd#a#7+ztEC/@AzQ:$p2@@ sa&z-wK T&$?u@gEuAH2w {&]TpEq 1@C.PgG].EU r*J]pqpLq$#03_3bO*6e+@]\_YLXy|:Ba[s'^Ssyyc&_6QSlim2v9üÎX?%09Ok`{y0fZB ut
+j:
+t.e`6/zfa?~N[@|ZM%q]8|L 0H~ ,/šP{DGFÞÅâÿ
+žý¿¸ r£á*"+}ÜUv0QIhp;H97;!S>kTH4}
+2sOFn\qW?h(( lsW)(ylvA Hv%e(mtuAYq2mzJ[$Lm[p&,am 3V
+TV'WeA$$%"1-"<Ui%1
+endobj
+1673 0 obj<</Type/Page/Parent 1476 0 R/Contents 1674 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F5 7 0 R/F6 8 0 R/F8 10 0 R/F9 11 0 R/Fa 12 0 R/Fc 14 0 R>>/XObject<<>>>>/Annots 979 0 R>>endobj
+1674 0 obj<</Filter/FlateDecode/Length 1594 >>stream
+xWMs6WQF%w=m7a&=%
++LL3-vXLXy!3rEZz<+&k<)<7@ '9v¥AM)bR@Xhr²ÊI{UWbMSg'd;'aVMJJgE[mx,Rki8ITY/AC lj%[!]&op+@cz6"Ad
+_!eekX,.{g^6{hZ*j(L}
+T],/K# HDMBqV.WXcU/K/oe yQnH"_Eu(Bqx8P%<A,h`Y(7o.kjEpVg:\h>>Z4X<mWGEb)tk#0 &,<T; ^ba p`_4JSYB59FcTU%OYqyFXZ*}f! x7PQ]]~HZJ6}I=aa}+P@{ '6lM{#az9(%4Rf{-mBE?a**=}hi Znc5!4]Z{ÞW,-S\O [\ zQYj\C.:vD,>m<k^/z-Zv6'-{Zx&B[jjeBO(e^ZTwn2P7BXGXqF>*@g~8V[T
+endobj
+1675 0 obj<</Type/Page/Parent 1476 0 R/Contents 1676 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+1676 0 obj<</Filter/FlateDecode/Length 1505 >>stream
+xWko6_qO)S`Y5kzhPBRVa}Rbs4!MFtvNi~4Hx7I4N~V= -aq>pz0Yzz,g aBd4J"=$QV /*eȴC~)v##t5U<J:]fUCp1?wW?4GQp7D+!Hd(RH2Yh;Ej*kYK<@cT
+Go! Z"H%BZM,qa•©¹ª,õˆÛ@kJ$'pJTo3REAo3:,q
+0M3(AI
+E7O s«÷ºƒÉ¾xÛ¿˜v(Ì2Å¸¯FR/A __p8ri>(*Sz0|Q9\kJtb 5
+ZB #‹rÍOx,d X'v#RV_O@Z&b`I c
+C<pXv [{bkpSH<AYY w&8W_ U(I>IT*^Ob 9\RV
+endobj
+1677 0 obj<</Type/Page/Parent 1476 0 R/Contents 1678 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+1678 0 obj<</Filter/FlateDecode/Length 1472 >>stream
+xWmOF){  %QS
+-WUaml]s9U}f6mr/;331|BJQ4hMhv8#iv30#Z,!qp{4EO]-ki I.
+QDNG*J' i.A`r
+o[~(2z#JGJTLA3$.*P2X#e^R6l@#wJ6E.|-66(YyicJ&jdJpY)
+i_CHc*lGy-m(6I tc lUVb+bWi#UÒK?XcjUMmkXpt"VY@S
+DefKH: =sY6;?ghdiTL( U)E
+OL[7HSo<:-Tuf'v '~8So.*O..g.o|M`J\>q4 c: |pq
+-|
+`<3>ozÙ€¾|æn~|Õ'®·8͎¸xi꿛¯«·¹³?e"sbáޖ÷¾¤ÂzÎnðô ÇèÞ)Ìì |…ΟZZ>);
+ #~2!DbUK#6endstream
+endobj
+1679 0 obj<</Type/Page/Parent 1476 0 R/Contents 1680 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+1680 0 obj<</Filter/FlateDecode/Length 1429 >>stream
+xWkoF_
+oJhq'Eu %REh7r6>H_Ýè€Þðæ-gáÓqŒËô|<‹gñ4¦?¹p ­§ÔÒ'I
+X1Cf1}u5UD'AbIU
+85Lp=@LE|l6Ol6)Gdq'`wTbrSØÎîÑð’Ö¡Úä+ks0wŸY>VuCN8`/ae1
+0nhavQp;9=qM[:v#/laQ} 8/1h]9[g$0$bâ{Üöí»rcGDH?w'vch{ Q@\5F+$;iLeÜJpb Rk0C9JE9pÌ.(2ãp¾V vI,tQApcNK.@aE
+xa1A 8B
+"X'0<Ir;n]8Eygo'>[kDf^7(# iJtAb~2lgg
+<T\d~!jd2y(ah~c<E;Er|T9wT/pGR,)*zB\_
+endobj
+1681 0 obj<</Type/Page/Parent 1476 0 R/Contents 1682 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+1682 0 obj<</Filter/FlateDecode/Length 1590 >>stream
+xW]OJ}WL!R^ T6ofwM~H33s;!-(vO'K<9xC988CF0N6yr_vE^aB% ofxtp{TY(wNSS\ SL/f[
+nWzFgxBSnZLgbJ{mHm7hJmU)~'M'jz$m%G%\8qNJ= 1&: /B[>"
+wS%úñêšádÉ7֖ÚMdj
+jSòÁ6ÛøFx`V2!
+&BPTo<0KeaFD|WRy2-5)ps7v@GU5;[HhtSF&}I%G\~v9]jS7Avh9Tih8@S4'&;IK*ve!6/*&I$=h^E*qM_gQYniDtG;"B}@2z5>bbYC?*KT^qvj; ¡¢èEK&5;j$+YTAwHK , p1{O3PKH 9Lnxt{{6.7Ue5l-X]LkJ5
+RnaJ C?L5sD]2HUC QJ87=X6*7X1:t`I.b=fSU0#/mYTDu~5bR$oziI
+qG@
+f1i!0%w J&sVbk=g]d]k}H[v1Lycm3 =Pg[mQ 41MIFPb$<#PKT#3%j +HMLD' e@9O&uxP\jx ~s<=S"0.Ues|Wjk4'_² /A,"@6-|W H#|k 5%g;! Cx?!N®!ïCcs]}!z
+Wjrd uki QZ"[ubr-E7g9i[hU[r8Q<Y.N 0owLendstream
+endobj
+1683 0 obj<</Type/Page/Parent 1476 0 R/Contents 1684 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+1684 0 obj<</Filter/FlateDecode/Length 671 >>stream
+xTn@|W*UIM0~tFC}<`m;wrV%YD!>LhfaRt :X yp&/%
+]w=Eb:7U]TrI@\;,lkL]
+{th`EuBfd4M>R7VqXB 2 >;UBvitrB|4(F }!
+N(C,\/#L:mG <+|65E(Aa]*u{1'={
+4Jo;PIеqà#‚*
+Ó{é.Vvp^K &
+#<c
+c>0J#0¦¾ÒéÔG .tId:~wOWLz] kh U~^1
+wP!}?endstream
+endobj
+1685 0 obj<</Type/Page/Parent 1476 0 R/Contents 1686 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F6 8 0 R/F8 10 0 R/F9 11 0 R/Fc 14 0 R>>/XObject<<>>>>>>endobj
+1686 0 obj<</Filter/FlateDecode/Length 1743 >>stream
+xWMoFWLuh,
+LJeh2;)
+/e\
+{wbg2U×
+сz©h‘ï8 –ˆLm CVu%mkqx*KBe?Jz-7lJA6]L+pm_t 6
+F6\/(Pcko{)|(fu. .6MAk3+ZoMPi; b\f?]ZAIlg!BRq7q3åрµFs ]fD=x
+qRd%xK,#y;M
+}}<u'9|a qd'd~^<D@a'`T,5$e8bXb.1cn_çî)£­ka…Ð:EH(n"he6,:]fp4MiSU?QZY[x%
+l1Vj!04,>@@@0*y)@Fg0\C3$=/d/1@JS7jtlt&RG}Zc^Jlj2 17ju
+endobj
+1687 0 obj<</Type/Page/Parent 1476 0 R/Contents 1688 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text/ImageB/ImageC/ImageI]/Font<</F0 3 0 R/F4 6 0 R/F8 10 0 R/Fc 14 0 R>>/XObject<</I15 15 0 R/I15 15 0 R/I15 15 0 R>>>>>>endobj
+1688 0 obj<</Filter/FlateDecode/Length 1981 >>stream
+xXr8|W*uDJdV98x{ LBb
+`
+&ZBZJ8'kIKUJ#" Qe47MU.je4A"yveI6L)l?/_,TGµ‘In#6c$~hSKcsyB(N]xHq:8D<q/s2NX$UH .,<g@coZ#\eM.#:Amf H]3->hFZn|8$cV`W,2gHn~=}=$BqkTj["EU-q¸ÚàLO%[U:P6cNJ{".[@^l.P=*^JcU{x^]N ku5y!MhwC@]yS>et: }yhd- Yqk\m$wg%Vh\"?YOU)ryOij*K b|(ph(s44@{+#8 N`>WI {6F?Mh*^ =PS"eK
+=2faKýœ¾ûåMf#nJR=rwJ^;+PtQ8fDd> C:: F *:)zhrc(b*6Dcm5~k#8bMWK3Z7ow_B_=bM#dQ5y+ Ý^ZwR n(* = r KsShs9xo0r`N.xwe%\!TWSJ4T4{]gThT!0jMKX-[$}a3m 4ou G|iVy( mk.c%0,H}wX? Q &Q6f+PQ/#4Zg5eU\ ndn*,/x=[d'wo42Sk
+;_U}BqaxlVY
+7xhtsak</[({OJ7?7u+?"][#_a1pK
+b--xp!w+c0p/ !_SP*w~hDMLiF^K/:Bzjx*Z"&,wlwuwd<(PtBO
+^
+Ozt{?7,+b{Z*L>_%;FD' U g(,tOM%{ o:Np6_"j-*YkmSUz Ot2 wo~qg)endstream
+endobj
+1689 0 obj<</Type/Page/Parent 1476 0 R/Contents 1690 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F8 10 0 R/F9 11 0 R/Fa 12 0 R>>/XObject<<>>>>>>endobj
+1690 0 obj<</Filter/FlateDecode/Length 1581 >>stream
+xWkoG_qE`]`W75#5mUR4ffsgBqMT[q`sw'}O([ c~VRq;ROt"],'hgKTZR%E.}@RT)AVWWY$)C\e.-eF2Oq NgoOzooo+I-QU`Z){H*|+`p6,Iv\URSa,2sGZVzA5#*ReK$jo!w&'[)Ve(2cs6, TI#'Y3JlpRd2IE2
+.x ]0mVu. .%r `*Og\3
+.^E#m,*xJ tB8r5:Ebgh`z-M'p1d4ORV(- =S]-kX]:1í9Š9jONu+¡Y,p8[l 6 mQ'p]@4Y
+Iendstream
+endobj
+1691 0 obj<</Type/Page/Parent 1476 0 R/Contents 1692 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F8 10 0 R/Fa 12 0 R>>/XObject<<>>>>>>endobj
+1692 0 obj<</Filter/FlateDecode/Length 687 >>stream
+xVo08K-i-e@"'^4iIi lJ;Mh!jv ).;m $2 [4< F! Xtlq[9~ErVK[7=2JP@@%$-
+"U s|4YpLK'\*I|97PTt6*9rz
+Z JC\M;wCwx5 k =ZE!yTyZ~f |3^BFpSi l/(rXoa8x?7zfxCFO
+PBrX<B
+?kTb G|ZEiPfo0c>1 sqK&'\j&j:L#C9s5h l-6:$h) _@=,xQ]G \qLZW:9A*G-fz~r{4n
+endobj
+1693 0 obj<</Type/Page/Parent 1476 0 R/Contents 1694 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F8 10 0 R/Fa 12 0 R>>/XObject<<>>>>>>endobj
+1694 0 obj<</Filter/FlateDecode/Length 1030 >>stream
+xWQS8~W/"^dqg(t/ 4&rI
-eu\HjJ gO550wT<*^29$')8Rf3OS(ajg-iO `i0Ln)l.;PAqWhGroÔh<èBc jA
-hl={eeiajVa8a%?UVA
-Pp$q51?1=]-^om dH
-kkdv"'KAq."Rf=vZk ij*qpp%&8)4XrQ=p5u|1 p´À¨CUp po*5s[FB(yOqt'
-0w?:K$ ]YZ'""xxz_qK [aj/.1J[P^:~>
-Rc=$;b]2$ #gz};W R}@JZ*%JQI/ l ^_NS
-~HTfIa<W+y / _#g~nCGNQ J3 1Wap3~Exvo~fy^ Z+
-8@)`Pg?/9bO~p{VWB^j ^N$+BemS}``_+pfXO{k CR^5t-
-PS >!m|u{6(2?WTendstream
-endobj
-2659 0 obj <<
-/Type /Page
-/Contents 2660 0 R
-/Resources 2658 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2664 0 R
-/Annots [ 2663 0 R ]
->> endobj
-2663 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [129.868 508.057 297.154 519.746]
-/Subtype/Link/A<</Type/Action/S/URI/URI(file:rpcclient.1.html)>>
->> endobj
-2661 0 obj <<
-/D [2659 0 R /XYZ 85.039 781.388 null]
->> endobj
-562 0 obj <<
-/D [2659 0 R /XYZ 85.039 584.243 null]
->> endobj
-2662 0 obj <<
-/D [2659 0 R /XYZ 85.039 563.046 null]
->> endobj
-2658 0 obj <<
-/Font << /F62 1689 0 R /F15 1628 0 R /F35 1632 0 R /F20 1617 0 R /F56 1642 0 R /F41 2104 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2667 0 obj <<
-/Length 2459
-/Filter /FlateDecode
->>
-stream
-xYkoF_umF#g
-n&X4JE"U1CQ'"<3EpU<
-#)Twt3OYpLtE_\^^]'J)G*1a\sl<wy= Gxj;p*FvDJZ~q#5`X? *Xq$}
-EBbqcWLj3g3v;aQM>Miw,0Do{P@
-z;NA !&(j:P+-XdG Ax7b7KaBFPDzE]g^FO/[P?5KLP6`A5;Go1vN:M(j
-r :5A#R#PS%(GVZ7%\/~BKT 0S[';iA5|71)4Uk
-gft;o1_]cb@-CPcGP4GjQCO/dHYg)Oun{GKf8I`$`uU.i._n-(ws QMi_2zhXM!{oaWm !?`qtY"y
-q]d^P!*c|DkRKAYk6; w!Fq5XTVkst+>
-;{K_{
-
-endobj
-2666 0 obj <<
-/Type /Page
-/Contents 2667 0 R
-/Resources 2665 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2664 0 R
-/Annots [ 2670 0 R 2671 0 R 2672 0 R 2673 0 R ]
->> endobj
-2670 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [138.589 638.298 286.854 651.2]
-/Subtype/Link/A<</Type/Action/S/URI/URI(file:smb.conf.5.html#SHOWADDPRINTERWIZARD)>>
->> endobj
-2671 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [167.627 600.436 275.552 612.125]
-/Subtype/Link/A<</Type/Action/S/URI/URI(file:smb.conf.5.html#ADDPRINTERCOMMAND)>>
->> endobj
-2672 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [251.271 492.042 367.484 503.732]
-/Subtype/Link/A<</Type/Action/S/URI/URI(file:smb.conf.5.html#DELETEPRINTERCOMMAND)>>
->> endobj
-2673 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [258.568 464.944 363.558 476.633]
-/Subtype/Link/A<</Type/Action/S/URI/URI(file:smb.conf.5.html#ADDPRINTERCOMMAN)>>
->> endobj
-2668 0 obj <<
-/D [2666 0 R /XYZ 85.039 781.388 null]
->> endobj
-566 0 obj <<
-/D [2666 0 R /XYZ 85.039 761.463 null]
->> endobj
-2669 0 obj <<
-/D [2666 0 R /XYZ 85.039 741.134 null]
->> endobj
-2665 0 obj <<
-/Font << /F62 1689 0 R /F20 1617 0 R /F15 1628 0 R /F35 1632 0 R /F41 2104 0 R /F56 1642 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2676 0 obj <<
-/Length 2310
-/Filter /FlateDecode
->>
-stream
-xY[oF~\cA1,nZ[Ev-$"(${nCQhaohw;IeyLDN8d-g_o[oO(S]L]O6}k1eke?]üü‹3ɀ©.ÛO#MIy/=^S>5"B;v^@?w:rkYQ/bC:6mW*Mu_½âv֕[^OY_\u.Znw\n"Ic7r.f6]y u##Nsh8)C1D/T_` _0;Fs/_qmVft6 Ox)Y[>ZhtHDvIT7B>nR-uZJ(Zj;)B}h,-@0QQ}=Xsg_P0(,AXh
-V9*
-=nY8
-e$t&rao$I5|3=Pt{OO f
-):
-J;4]
-2 )I*nA3SDcI[)=E!b}
-B.-ðRa<$|*M{sCqi*0_0$) W' 7}8 ec
-endobj
-2675 0 obj <<
-/Type /Page
-/Contents 2676 0 R
-/Resources 2674 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2664 0 R
-/Annots [ 2679 0 R 2681 0 R ]
->> endobj
-2679 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [111.316 305.015 212.606 316.704]
-/Subtype/Link/A<</Type/Action/S/URI/URI(file:smb.conf.5.html#ENUMPORTSCOMMAND)>>
->> endobj
-2681 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [457.73 218.948 613.572 231.85]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://imprints.sourceforge.net/)>>
->> endobj
-2677 0 obj <<
-/D [2675 0 R /XYZ 85.039 781.388 null]
->> endobj
-570 0 obj <<
-/D [2675 0 R /XYZ 85.039 464.617 null]
->> endobj
-2678 0 obj <<
-/D [2675 0 R /XYZ 85.039 443.624 null]
->> endobj
-574 0 obj <<
-/D [2675 0 R /XYZ 85.039 276.385 null]
->> endobj
-2680 0 obj <<
-/D [2675 0 R /XYZ 85.039 246.981 null]
->> endobj
-578 0 obj <<
-/D [2675 0 R /XYZ 85.039 178.549 null]
->> endobj
-2682 0 obj <<
-/D [2675 0 R /XYZ 85.039 157.353 null]
->> endobj
-2674 0 obj <<
-/Font << /F62 1689 0 R /F35 1632 0 R /F20 1617 0 R /F15 1628 0 R /F41 2104 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2685 0 obj <<
-/Length 2940
-/Filter /FlateDecode
->>
-stream
-xr`VWnbTm0"  @dn*~$ 9!==3=?Ff$0Mg7[/L^_~3ßs3/›-e™ÿâ\¾{}³|óy¾ÃÐñCwHw?^-
-<%2HNM&s @mBrB/0 a;L:q<*M6HMnUD H o-`cOwOtRO(2_vdSI$yFS vímHqi{`aX{t351r~*tp, s%aXKI:"N7\ih^KK
-43I^eUL]G'C
-\?{q>,%zm`U*T=s +lgI7x'6K48u_X+0iI>4Me[19t&8RWcX?
-3i9#t7gfWP'%yf/+/zGpbw
-vB4wdo(Kho6Nhwmm$v(H[%Jp'EUm+~-Q9#zML o(I2|;c|/y8~%1&z1IWAoxwb?RP32/QPV]^vbeN)
-H5$$4m;`Kc8ap t/VK%f u9MzŸ?´ÀÀãfBfgD f2WWqkY0>M8&` B+-4OdO'L*br}B ljDs[fɳ!ï4±ò¡ïqGy8KhyS?mSoz*]z*cZ|_A]i~Q_(Q#^M-`+]6enPC'?Xo)Ds,\<_6XhB3EgBPd<?;y=?8q%~?t"CBl"*8^n89 7lendstream
-endobj
-2684 0 obj <<
-/Type /Page
-/Contents 2685 0 R
-/Resources 2683 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2664 0 R
->> endobj
-2686 0 obj <<
-/D [2684 0 R /XYZ 85.039 781.388 null]
->> endobj
-582 0 obj <<
-/D [2684 0 R /XYZ 85.039 761.463 null]
->> endobj
-2687 0 obj <<
-/D [2684 0 R /XYZ 85.039 741.134 null]
->> endobj
-586 0 obj <<
-/D [2684 0 R /XYZ 85.039 672.049 null]
->> endobj
-2688 0 obj <<
-/D [2684 0 R /XYZ 85.039 650.852 null]
->> endobj
-590 0 obj <<
-/D [2684 0 R /XYZ 85.039 568.218 null]
->> endobj
-2689 0 obj <<
-/D [2684 0 R /XYZ 85.039 549.346 null]
->> endobj
-2683 0 obj <<
-/Font << /F62 1689 0 R /F20 1617 0 R /F15 1628 0 R /F65 2099 0 R /F35 1632 0 R /F41 2104 0 R /F56 1642 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2692 0 obj <<
-/Length 2286
-/Filter /FlateDecode
->>
-stream
-xkoFP8
-hE8\@[_"|DbBr.G%)JN;0wgggg=+wC:vm?Y<7`8v~,6{Bd7?o^\o\ut?~,Wuk6_n^mF;|<{gS8';$&}; |7oocZ]
-0;sA7pB/acà;Ç iú_/½Äjñ¾N`QK/?Pp xt-d+j@(B`{ `M^,pIH,O8G= T@}\`B?H;DNkpAu<& +!pb6{jO1f0:1xQ
-fR;e
-bbW&k-/ P,D t #;Kpv&x~ 0€S}X+ |^;qr9^c+vdk'h\X XDKz
-Rb{('S
-D|"!f+m(7q/sO<b#Eo%@mQ{H{M.A4u9 UkZd#Lww~oY?E;6OKwuue& )kh6%R
-wG :k|p~u|8Nyd$j%-t!9U]'!j׃ôí»<ýܕiÁ%¶â"ÓëëM| v?0UJ lMAs`l*G-)& \rjmA$cp3rE* 9qc8*qnfH0 .qGZX
-pq| HK?<v8~n`Tcvc# †r•Tv}Z3m.*?; KG8_; N&kHO|6u%} 5"9 g‹CT6' HTYzu,bjEY `%DN${r F!7D1D>\cIdY9?1>qdD/"g>}ts6g_rLendstream
-endobj
-2691 0 obj <<
-/Type /Page
-/Contents 2692 0 R
-/Resources 2690 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2664 0 R
->> endobj
-2693 0 obj <<
-/D [2691 0 R /XYZ 85.039 781.388 null]
->> endobj
-594 0 obj <<
-/D [2691 0 R /XYZ 85.039 679.868 null]
->> endobj
-2694 0 obj <<
-/D [2691 0 R /XYZ 85.039 648.343 null]
->> endobj
-598 0 obj <<
-/D [2691 0 R /XYZ 85.039 648.343 null]
->> endobj
-2695 0 obj <<
-/D [2691 0 R /XYZ 85.039 630.139 null]
->> endobj
-2690 0 obj <<
-/Font << /F62 1689 0 R /F15 1628 0 R /F20 1617 0 R /F35 1632 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2698 0 obj <<
-/Length 2253
-/Filter /FlateDecode
->>
-stream
-xks; 8Sx[im#<
-
-Z
-I=>t
-Y_^3Bm&A}TFju^!u}2y) 6lEH 3-@GO>2$h)?z~\'js$*Wf+\`UW7O4rb{!m]}(D0#dc& JW(vZUZ[G
-.KifEkc 2azZ%cU% _9g
-ow
-MB &lkT4`~>
-$@y*J!N<je@+jc%H !*2&M
-08ld&TOkX,IIcYE_a Ra5Bf7{m
-FV t}T*1¶&Åð„vÍΚP<
-~L ~<(lr*rmlV
-p'_"/=7ÂI@w]yIR5E@`9xwY!1\Oxoid+~(mU7cpa~
-endobj
-2697 0 obj <<
-/Type /Page
-/Contents 2698 0 R
-/Resources 2696 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2664 0 R
->> endobj
-2699 0 obj <<
-/D [2697 0 R /XYZ 85.039 781.388 null]
->> endobj
-602 0 obj <<
-/D [2697 0 R /XYZ 85.039 638.273 null]
->> endobj
-2700 0 obj <<
-/D [2697 0 R /XYZ 85.039 617.077 null]
->> endobj
-2696 0 obj <<
-/Font << /F62 1689 0 R /F15 1628 0 R /F38 2158 0 R /F20 1617 0 R /F35 1632 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2703 0 obj <<
-/Length 2252
-/Filter /FlateDecode
->>
-stream
-xYY~(h^xw (YZ#O]M5%jfx
-zA.O*wd'W<x :+2+45
-u7}y `b/
-Vc&`A%`
- Xyliqa`,I: w`*n;. RD@CVj
-Ol/'+ey(T_RLA6vgP%\]]<mc!<+Z bWS<
-: PiH8MY^
->Ha# {,6TrRC
-8XpEQATWda<1$jzI 9kD-h [4uH<aYIje^q8E+NFS}[]?2j5Le `R?AQd+?+@>8)VqNYW8oLm4 ]zu(t^[Z=%uR:{
-~C?p__ Mw3
- vW/zqvJI. GTMz^H9PXrwg$>>GcY~M)oO
-g ge(L~kbTyReky/lOU/',@_S 5W:fL@/!e_).\vVA J'Z
-y{}yOp<x=\A/)pcE|+Jm!7o1K
-bF.FZ'@N<6T e-
-=4>t+oqc$w[-c 02X|c^ MH^ pXAQhY&[ b*endstream
-endobj
-2702 0 obj <<
-/Type /Page
-/Contents 2703 0 R
-/Resources 2701 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2715 0 R
->> endobj
-2704 0 obj <<
-/D [2702 0 R /XYZ 85.039 781.388 null]
->> endobj
-606 0 obj <<
-/D [2702 0 R /XYZ 85.039 761.463 null]
->> endobj
-2705 0 obj <<
-/D [2702 0 R /XYZ 85.039 741.134 null]
->> endobj
-610 0 obj <<
-/D [2702 0 R /XYZ 85.039 536.885 null]
->> endobj
-2706 0 obj <<
-/D [2702 0 R /XYZ 85.039 513.567 null]
->> endobj
-2707 0 obj <<
-/D [2702 0 R /XYZ 85.039 299.114 null]
->> endobj
-2708 0 obj <<
-/D [2702 0 R /XYZ 85.039 277.353 null]
->> endobj
-2709 0 obj <<
-/D [2702 0 R /XYZ 85.039 255.592 null]
->> endobj
-2710 0 obj <<
-/D [2702 0 R /XYZ 85.039 233.831 null]
->> endobj
-2711 0 obj <<
-/D [2702 0 R /XYZ 85.039 211.464 null]
->> endobj
-2712 0 obj <<
-/D [2702 0 R /XYZ 85.039 152.04 null]
->> endobj
-2713 0 obj <<
-/D [2702 0 R /XYZ 85.039 116.73 null]
->> endobj
-2714 0 obj <<
-/D [2702 0 R /XYZ 85.039 81.419 null]
->> endobj
-2701 0 obj <<
-/Font << /F62 1689 0 R /F20 1617 0 R /F15 1628 0 R /F35 1632 0 R /F41 2104 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2718 0 obj <<
-/Length 2637
-/Filter /FlateDecode
->>
-stream
-xYKsFWjLOv9+I%9@$(&
-
-]@2
-q63Cp_R0bg~C&RuE#2c
-;:J!b
-j^3p' H14`LW2: P`Vt S!Ðná^)”랸
-åJ
-%2"[+m\k ?um
-g0=)kgjERR1BH
-N
-L\LEAKj^/3yB?)f|?7=CRs$8 =JIp
-_#v?25VD&H$(IZ66}wAJ0hhG_Wndf)_<n_V5}L=n>/rZo|
-c|y}N9Wv,>TM&7zy^On?*(p_Tq<yYendstream
-endobj
-2717 0 obj <<
-/Type /Page
-/Contents 2718 0 R
-/Resources 2716 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2715 0 R
->> endobj
-2719 0 obj <<
-/D [2717 0 R /XYZ 85.039 781.388 null]
->> endobj
-614 0 obj <<
-/D [2717 0 R /XYZ 85.039 761.463 null]
->> endobj
-2720 0 obj <<
-/D [2717 0 R /XYZ 85.039 741.134 null]
->> endobj
-618 0 obj <<
-/D [2717 0 R /XYZ 85.039 339.522 null]
->> endobj
-2721 0 obj <<
-/D [2717 0 R /XYZ 85.039 318.325 null]
->> endobj
-2716 0 obj <<
-/Font << /F62 1689 0 R /F20 1617 0 R /F15 1628 0 R /F35 1632 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2724 0 obj <<
-/Length 1502
-/Filter /FlateDecode
->>
-stream
-x6_!(B":l[wy(%WuTq9(YuM` s8>'=_N2hE`9|'$FI!u^j]J)E =wXz{vx{|Z47b~\x](x}~]3` iQ,8v[\/~0-rQyY
-ub{s*eKTdqD[2I:7770# 7L=uLrK3BN/)|Ez0WkX[>$k80fJ4YZ*?[[ yp$f\ijx{4v5mAA p'`~bjK>? h3T/%3(ks=<@@" [ 3u- Q(B^
-5ykZ>N=,4ez^JxYL%-8(\ypOJBEU>;5|x0~b+c\m6}8^ORtlm0Y({jt-6D3  Tgoeyu"tC('{p% 5X /&D<9O]4nqd13'sOmDi36~h7(ZSD~<e{I'BM;0FF ¸wƒENE_=IBE4
-i*e7*)\z9NHe#E5v+ | 2
-%W/jF??<'I kObG@sUv7]Ðw;rô쐙¸è&C@Q9k Uz|6^ilY(~ze(ux,8!mE&gBY~a4o1cd=Z>r )(cVSMHDsW'=3f.f?6X_=Mri2'p3N>>K*e_eo?E9w*0;ëáo|Ÿ#~
-.¾G[{O9qj<5 ,T-8L r/1yc +u;ZQ1e-U~v& c(Y<amP/vvqS;hS
-*KwU}FpLQS#Eg rendstream
-endobj
-2723 0 obj <<
-/Type /Page
-/Contents 2724 0 R
-/Resources 2722 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2715 0 R
->> endobj
-2725 0 obj <<
-/D [2723 0 R /XYZ 85.039 781.388 null]
->> endobj
-622 0 obj <<
-/D [2723 0 R /XYZ 85.039 639.867 null]
->> endobj
-2726 0 obj <<
-/D [2723 0 R /XYZ 85.039 618.671 null]
->> endobj
-626 0 obj <<
-/D [2723 0 R /XYZ 85.039 549.412 null]
->> endobj
-2727 0 obj <<
-/D [2723 0 R /XYZ 85.039 528.216 null]
->> endobj
-630 0 obj <<
-/D [2723 0 R /XYZ 85.039 445.408 null]
->> endobj
-2728 0 obj <<
-/D [2723 0 R /XYZ 85.039 424.212 null]
->> endobj
-2722 0 obj <<
-/Font << /F62 1689 0 R /F35 1632 0 R /F15 1628 0 R /F20 1617 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2731 0 obj <<
-/Length 2950
-/Filter /FlateDecode
->>
-stream
-xko{~P-%R
-/_z{Wl
+Ut:m|9Z`_ . }j .`[mO@_Oc~N5̖muê÷å÷ÇÌ®û«L4(CdgBU ,be
+tOGy[~Di=nrE_z]A? V^:LLw31saSwwNj~dO
+W+EICr;/xBys p'p[0b4PM/ S?6jq((w< $ !IPQNyv9 gLI!Kz"6>3_A%CYZsq`X}<|kXwY$D?hrli(QWiR&!C,4[tpaU`XVCI*,WtVb}<agI_K 3"*E%#2l678"Sb4pCt5xv!TC|4Z#oLcE^Ag.- 9{WKVw)Di"=kC>K~a"fE@@TE6J:pn/ W1A57['s]+K} %3dY>%]K8U4]hUsa6~a3%i[w%
+,X)kB0/lMVo}x!@?zqRmg_DMendstream
+endobj
+1695 0 obj<</Type/Page/Parent 1476 0 R/Contents 1696 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F8 10 0 R/Fa 12 0 R>>/XObject<<>>>>>>endobj
+1696 0 obj<</Filter/FlateDecode/Length 745 >>stream
+xVs0~/tn@z1*'O B#g&Eh6: o
+r2(%diFW*iqi9!<TzFWQo5(ZpÅÀ`åmaA % IF*IA%dCpLnL5Wckh $(nPxyI
+endobj
+1697 0 obj<</Type/Page/Parent 1476 0 R/Contents 1698 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F8 10 0 R/Fa 12 0 R>>/XObject<<>>>>>>endobj
+1698 0 obj<</Filter/FlateDecode/Length 742 >>stream
+xW_S0zNZ=gDZ+> @RH N.dw
+~E8_W@ K 'g.+'Wq_2!=SCYMWXP%9h:1qM^h+hW QmFecN=k_n_K-UTIj7VYTRrL˜²[ËêTnJUKoz],pue"4jFjqN+]J>&ocx
+iJC_5:%MY&('m`LDMuB,Om:z[%e5= 0[18a W|0yB% V0a>IK7tq5Q(8)j` Nzz3]endstream
+endobj
+1699 0 obj<</Type/Page/Parent 1476 0 R/Contents 1700 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F8 10 0 R/Fa 12 0 R>>/XObject<<>>>>>>endobj
+1700 0 obj<</Filter/FlateDecode/Length 1087 >>stream
+xW[o8~WL4+1-t->$qâŒí´Bc;t6Hhu_ yk:;38b#}y<|p;-Q}n[FA H^w
+px$EH#TL! " R)A c. H)^"(QaL#I%Tj
+ oGI0Ž!]]{ÿ.÷£+ÏdÒ)W?cQ^ }[5
+endobj
+1701 0 obj<</Type/Page/Parent 1476 0 R/Contents 1702 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F6 8 0 R/F8 10 0 R/F9 11 0 R/Fa 12 0 R/Fc 14 0 R>>/XObject<<>>>>/Annots 986 0 R>>endobj
+1702 0 obj<</Filter/FlateDecode/Length 1578 >>stream
+xWnF}W +IEZhbRR0K+*=|Q\-r93gY}R ?! SpmjIK# ?\GnSFqPuZk 5iZ9voSukqiD!n3rwoAvR[XT;6]']NOjF:q __p#p_]_M\xw7&=Q
+ockco*z$7 &^(gUNDgo3r4{zi6A.1++ck=>Q0F?:]rW V;2—î¹¼I"i*.amap10IVJ(T^M7aUZBR>JDNInHSBF"a`jcNxkCcZ8^A); mu0P!4$M(A(qT !'_zW9blxY Hkiu"o7kRGy,t ex[iA#Mav nNC(&i_6fO3(ZhDeaL2}ZS\XHW=--SQiieLRi,(]V 
+uzOR&u>#3Y<F:4-EMYLa S7_Ie
+aLbJfx+'tB@P]fxfc'smmq,y&*Z#SY.&W6QDXcVCd#4* HXSAc*}\m|w I/T._TuaO0 C!Jx1g _2H&ySj6Bh`L}#{Y2>VkQ^za9F'&ps3-Ujt>^yEzU0L00
+!R<7]C5'NFD+HBd.$A\j9z;hYD@yz
+G
+Ik<&%#r
+ @fNgg Y
+endobj
+1703 0 obj<</Type/Page/Parent 1476 0 R/Contents 1704 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text/ImageB/ImageC/ImageI]/Font<</F0 3 0 R/F4 6 0 R/F8 10 0 R/Fa 12 0 R>>/XObject<</I15 15 0 R>>>>/Annots 995 0 R>>endobj
+1704 0 obj<</Filter/FlateDecode/Length 1608 >>stream
+xWnH+
+:cn;@0H$(ca
+F77+~qq)IhzFG".
+YeIU;i/p0\0"þe#²J4T
++tl-kj-Y2&sdWD5QJi?dk{O4L0rHh'/pCdpu%J(7n_MUBmVPpjHmdDI?b2
+U+0jJvtb@!:cs$m)3/2mX2$v{Dgp@DmS]}UKRf srywSo&a$jpp8tFqeLy<_)Ue*u65q>,N'0xhveF|rhmk Z?#nHcMu$iX[NgC'Knpdf
+je^if U%o{7V}| @C7=t|,=+pAJ¹„˜¬ä/5KGT8M$g$ m{az}R@BhV"&"
+W1<,x^Ek9L CLk]H/IwTS.<U%iS? @2!n}US"
+[p}g_Z^a 5Ry_[tӂÁ?,4è ¿‹P?ksiJ o?]aas {_lcBF_uTPf)S
+HA@ovKPf:Z 8 K_;2zaNN }@s0gK2{6L&86n~nZsq<+))û´8û~ö/hÎ.Mendstream
+endobj
+1705 0 obj<</Type/Page/Parent 1476 0 R/Contents 1706 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text/ImageB/ImageC/ImageI]/Font<</F0 3 0 R/F4 6 0 R/F6 8 0 R/F8 10 0 R/F9 11 0 R/Fa 12 0 R>>/XObject<</I15 15 0 R>>>>/Annots 998 0 R>>endobj
+1706 0 obj<</Filter/FlateDecode/Length 1816 >>stream
+xWo8b/u#(ikvX h$"ea{CAmK"9of8Q=.?zA4ioHu.6|||6b?QFA*9/`h0>VggzXO#4i8]Zm¬‰KUXzUmS" '*_n$%DmunTEKK+]Xne@-al.9_<]
+{~Mxnzxpn,$rMLPci^WKt4JmmT 0nt6*=X /`D'P<_VZg8hV*u#2'%t&HpAMKg;7]z9 1&f _gW z8\6.HzA 5k9W#-Tp{}0] `Isro0fI"g2Qb'yQy6x<y_Y,zJB!l K;e7a6'PW2l" dqUOsDo>oÐÖjp,“ÙR_"ENFk
+e*(UnI,ge0&`Jd>{c
+Y&X47k6f&Wv'Jj ,QDb>),`*$<YP#\bJJB%\{E@NSLeLF>2\*D3MqM@zg_by B`* ")/;v} NgEH!fN RhLumXbU?]Z |Z(@r>CPUXZ+S&mF1v1<U}tSJ+4vze-i6T"Wi
+B=4;19DgSv]YG^>uJ Qwd1agl GNQx('N B^0s$$pP
+ g^|oQ2/~Trwcgcrk|?uL\ e
+qmwg`8?Lcp9@Shg;K*Y'h--XiHN
+&|^*_id#^k,Xr[W#iH"LR+6$<D0WB_3*$j[(;^ceYw\ <bQ:d.]o;NK%7
+endobj
+1707 0 obj<</Type/Page/Parent 1476 0 R/Contents 1708 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F8 10 0 R>>/XObject<<>>>>>>endobj
+1708 0 obj<</Filter/FlateDecode/Length 1671 >>stream
+xWmOFKa p\"RA[EEm%h`{:5!UC${vgg?:b|7<+h8HO~kMOWt-Si67 V*[{Gz>?(U%-5-gkw7xrL~]:5[?M*fiTBxRerK*]›ÑÖ6ÔªÒ'é,9a‹ 2Â_„£ïTQR$mlKZ9IQdC,^qqX"R:dàè,¢çüvt9¦gýxz‚#Ê+•áfŠ«à³¿4¶ M,q!^)1OOg 8x/z< ) zk8mvO:
+i7&qZj )TtK'p"Nj-w r!SjÔ&µu­So2 Rk^NFruk9_)m478DFv(>8E7zL'2#a \X.*jSuBE++ P@o MuU-ÀU2utʁcWY3Vm\MlDO7G E$m3 ï­ýe@\a.H
+H^2eJI}`pcZ> fU
+yI;[[rl6 D?3
+4Hz:g7b383oS7v );.lRd:L-c;vªîâ¡Îù"$¿A!0v5ES+4
+m,Z$b?9MNzk}h>#A :@oRA9_up9
+endobj
+1709 0 obj<</Type/Page/Parent 1476 0 R/Contents 1710 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F8 10 0 R>>/XObject<<>>>>/Annots 1001 0 R>>endobj
+1710 0 obj<</Filter/FlateDecode/Length 1675 >>stream
+xW]o6}f,2keXq Pm1H~R&6`h'Ls%?e;s*4Id{,(;'sjh:|xWe-V4?9E (Vr$4YQ^\V'Zk%yC;*I+cáa¥$¥‹º+%þñ²qgO "Kx~1t,?|N4YvrN4KPFé•^³‹”â,MNY~5fY?|q>N.* s#ltYRk}[
+X·h BBQ`|CJpyr[q76pj]oz†‚°C C`moe:]"HGah>{sfRhX F "P:/*••…w‡uyB l3Xilujæò"œ:ĎՃ± w`=ØÅëî˜A<P5<"&@HT_MC
+, X8(C}8W-QT3d,&+1JZ";e1r1AW rHT& <BlcobfG,EE[9 t@ukQ*F[(J 8zUgfI
+Wbz2NM9d+dw<qT P/kV
+GQX%;I~3.Y!\hW1EMNssIag4v=28a)Cms 8$l<'-U,u|3Q1s55Fv~q #%p:} 7!Hq.QAH^^^@?9j8P1Y=HXq 
+Z8@?Wcjz
+QJ ZVx,>7/wgIUqq~x+gf3Sb7\N8IO4?`Mn5Pyza'he%>Nq+(_T|w@y9Llf6?IG9.l"=g/{ tendstream
+endobj
+1711 0 obj<</Type/Page/Parent 1476 0 R/Contents 1712 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text/ImageB/ImageC/ImageI]/Font<</F0 3 0 R/F4 6 0 R/F8 10 0 R>>/XObject<</I15 15 0 R/I15 15 0 R/I15 15 0 R/I15 15 0 R/I15 15 0 R/I15 15 0 R>>>>>>endobj
+1712 0 obj<</Filter/FlateDecode/Length 1902 >>stream
+xXko_1.IqR^dIh7IaM?PE3$f[X$"53> y:O~:pqT/_66 ao t0bQG4_ K{c"-I<qi^4z,]k~{sF>; AOyz6|~};|w{IE-iO+I{?##K)u,`9IUup[[Kad0E 0UY'EAz +S)5my&at]^Sz]d$N2uUsPV,IeO+VH92Q jeQOKGR 38K8;@ >Fs0I'#G&^[7 A ymT%r{;Z)dumr
+o~Q,x+  2 6|IRX/k(-e2^_Tn GSO
+~Uh|zFW3S igUQ2P&<cI` XQzN-uF@RC16rH! ,# `%YPEmAY(f`Xn.+qq H f?d&}DRKU4F5&U`V(74F<Vev! I7O&JB/x?Xmm;Fzm*_( >x.zMD*', uV(Ko= NQKi9 5 lEaWY,N~1>@<I
+ 55! PZwbrx;R|^V52vA J-q"gA8mHos{_/Awk_tWuss$v/$H&$ A
+5]I6_M>^~
+or 
+EF0:L:%Y'4sK,%n~{8,{ 3??!bW78%mPDu##}sMaQFD=2 XHDE#+&L XgR0"nE
+^0@5
+~q~ Xaho{:?{3y i|>N |bz^avW:=>QJ?sJUAkzX6s6rH1endstream
+endobj
+1713 0 obj<</Type/Page/Parent 1476 0 R/Contents 1714 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F8 10 0 R/F9 11 0 R/Fa 12 0 R/Fc 14 0 R>>/XObject<<>>>>>>endobj
+1714 0 obj<</Filter/FlateDecode/Length 2149 >>stream
+xXo¹ýî¿b*à
+߶¶åËd4ŒùÀf¿7Ú×ÆYm7e>Z/7w'*+Z\{ZUsGM0itmf
+(+ckn HZg{81U-MMf?Vn%gOÛÇÅpêåÌùú!­LYSwTDHr&_c*V?y zd4_#WWXjR{X_#-fã)ÇLjÏI(S
+
+\UMPU,0x
+U/$:ïÁV\x (]+Ps&ah_"#<3&@;rpXQg  57X0[)fZ|wcm@SVV-B+f<5s4V,wsTXbB+rgNtY
+endobj
+1715 0 obj<</Type/Page/Parent 1476 0 R/Contents 1716 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text/ImageB/ImageC/ImageI]/Font<</F0 3 0 R/F4 6 0 R/F8 10 0 R/F9 11 0 R>>/XObject<</I16 16 0 R>>>>>>endobj
+1716 0 obj<</Filter/FlateDecode/Length 1692 >>stream
+xWkoF_` ,eKu$-#-~8GwL6)"p Q]h3Zi*arqfNWNV<6 fplE|:MrtQڋʑÓT$KJM$T+E*
+iLT!+gsEQV-3Hcq/"+]S?Mi<[ MzYrE6WW;Qn4O!>IPTkCJu PQY'U|:|-|os:h$O~oX
+Z@m:yyZ"/&+],3f>][~-JOCr/vsKA||l>-F`DExyR!K]&0W:FclE&}+qK]Cf67WD
+`.h'3:85WU[^%F`\@U,ipxX0<L-hK/.yxcv4%)-"=dy/Om|lendstream
+endobj
+1717 0 obj<</Type/Page/Parent 1476 0 R/Contents 1718 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text/ImageB/ImageC/ImageI]/Font<</F0 3 0 R/F4 6 0 R/F8 10 0 R>>/XObject<</I15 15 0 R>>>>>>endobj
+1718 0 obj<</Filter/FlateDecode/Length 943 >>stream
+xuU]F}W\]eW6`Q6m6ZP E{=R\a[!Àóq?ιç^?ŠñIh8<S2~hNY2b>}Htg xgxNmkO)ei48eq-QT]Kmu%UK%Il6SPhkVOd M{jZcALaEq6EQa[L]jNYBt#Y0]Di! pDYRj 1Q`t Oq;3v@LM-drmu]@uF8;UV(s]
+>t6T/1baFiY4v
+? l:7(S@OD5 GR9DKFK!HWr%X\]@FDqiJ'-xMU-[^ðÀèr¶5‹ä»œEn_%G*y*7b?XT~<IO<m .
+_4R|~d?9!DaH6O8I;1`~Ng b, PUTjjY~{Dr#Ps-yn'0JmI0EJe18YDlCc*x
+$0{pwi46cQleS~!Ny_k-endstream
+endobj
+1719 0 obj<</Type/Page/Parent 1476 0 R/Contents 1720 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F6 8 0 R/F8 10 0 R/F9 11 0 R/Fc 14 0 R>>/XObject<<>>>>>>endobj
+1720 0 obj<</Filter/FlateDecode/Length 1619 >>stream
+xWMoFW rrP[dYvzK08n =".%(M-6l\k. \IR\.j~5[/Skbx>y,.dF$rU5j&NWuF7V>›ºÎËÝúåúϓ 9_,aâTT>!7vSäú›_G`>7ßÔ*iâ±¥Ìçý±Å5B[m,:&wY3
+Gv6%mz%W'FRJ^ E2gpGVbY vgjgKm/™«a¨pxޘR/cF>Sx :m;+L<r&4*U rR]by%Q[Lnp'~NULvU0*oZj“Äë\Ú'X&qJdI3M3Hqf+GJ+` f=x*E R)T6%
+4~ OSLuk/H]] H^/:!xtQuJ"W;-2P*]Z<eOE7UH,/cYlt[63
+C#*a-yuD9E"$=Z]
+Rh5=-yo%LjM_(n3
+& $q-64xJjyd;U Uaf1M-@N )?MYtµØoC^3 `I) -*=: yPpvR(+Vm^=<P1J !CB~@Svj2[k-DckXfGn^MR3i-^>LX]K|;Bxyo¾ïë(I!f6}6GA+P@Th0Eks%Rm,F7k8~V06?T-E-N#Bw#JKL;-t%'p#FX4G=>(dMU"GPFnv '|J,FW@g#vKW&u÷
+(dmQL/uNagbbpWwXv PXȨ `í¥ÃhŸ q'~G[* C<1
+D!W\H%Qq`|w#CwYL:U@I##lvOvqc,c1$4eL(=bu6{L|m5&y@|81Pn*; v+ Zhcd3yqX,) EB
+=<m!IfSz%a#v<s(Webdk:b} k7oW3~w{Iru3[]-D|
+endobj
+1721 0 obj<</Type/Page/Parent 1476 0 R/Contents 1722 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F5 7 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+1722 0 obj<</Filter/FlateDecode/Length 1670 >>stream
+xWMsHWtq2Uc1GCZ Yb
+4D3_g$Q5{}2~.V'/y q6lz[,|\_,ohÏf´N'rPO8-Qrxh#65'rpGm,p],5}u2%[gv6M&nu (IVC&#UJY#FK5SyCv>0{
+r.u- c+daÒÂY}g]&lj:, GT|c[8>MzjhWtPx+g+#)4edsFuR=E)7R60NX30l{*mZ:S 1D['.
+TQPd`dQN8L%n2_)X`CNtbE;~=(7Q{ VBb z +Q$c 2CV
+.4v?%
+:C,*3)6 EWUx0Q8pb> C);5()VAl00mU@j9!'/D)}E& fork(hZxqgJw7YtvB! C[1C7T\=/xxb5
+endobj
+1723 0 obj<</Type/Page/Parent 1476 0 R/Contents 1724 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F5 7 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+1724 0 obj<</Filter/FlateDecode/Length 1761 >>stream
+xX]o6}K3 Qlq
+[lv Dl(Q%x$rv($x?=~=t3(Ñl4Ëf4½½ÁïüXIex1]goi<e [[RFlM2zP5r%++so>\_`jJq4u1sIZxIh|N QmP,o$RVozTuau^Gt1& 5xíÎÉ
+¸±ð%êàp¾œÒÈ¥è3úLzH.iW9T*Y}q"dV)5mFJVpB'57.6qDq>Qª ª-ËR_(PU\
+YD7iZ g )3y`.eLck1`YOI`AZMI%fT$SH\h
+oRQ-={G
+le.Z=vqX]_);phV>cbL/;>,X@
+`FOB9zoLpKhM\ eQ_UcU6&V)$]~ Rv.cV($<2 >c+b6}m%A[mS^@]Ia&7 r]ÅCC@C18$k$xP%&wni#Bqzh" OcB Ud>ap]#1\
+p SK`YP¦[ž<ÆÒbª”!ø{rДBw(~E$~]A2s^Uy@EF" YiDz:F:Ga;%E)bDh1yXW0Pg:#8=-~8ojp9?#~cc
+9 x\>h *#J5-^6ZXj F/ae*rM }v'/Q3p1{vZO+ b8m/{I['lphAp8|xowq7tce/m6"8'j!endstream
+endobj
+1725 0 obj<</Type/Page/Parent 1476 0 R/Contents 1726 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>/Annots 1004 0 R>>endobj
+1726 0 obj<</Filter/FlateDecode/Length 1837 >>stream
+xXQS7~çW[ !o%MBgCf:Iw#a208N~|Ñ1~Ft> qqLg'#|^s`h./NN^Gb ^wgMNqhMb}XNI~Sh:sj9u34DjTOR5;S S ),[>d]c\/_A5~G'oHl.D^I7SM6*^lW~}lXri{ I-uPlmf`k6tk+DyZ*rQ. [4YKLE=2)Ò6àŸjC@AIq
+8]16
+jN 'cAaG@Y!i }4d
+/ x/|F<oC52 *hI"gyo_ya7L{xG1Z|Fh 2*enSu"r
+,iW s>
+CMmto0CU747\?p&C8_:1Ktj 8@+>M?uDc$ ]ZM,~`q$uJ$18@`F6O4O(p95z7w+K\N'tV8@ 8-WP7$1hªþ ð9n·Ý•0 E+7V^\@]^Qv0hfM{rq}Txj@.1$A0cC]7+XM7&M].Kh88"UBZ}ü=_¯‡C0{xo8<?~) Lyu|endstream
+endobj
+1727 0 obj<</Type/Page/Parent 1476 0 R/Contents 1728 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F2 5 0 R/F4 6 0 R/F5 7 0 R/F6 8 0 R/F8 10 0 R/F9 11 0 R/Fc 14 0 R>>/XObject<<>>>>/Annots 1007 0 R>>endobj
+1728 0 obj<</Filter/FlateDecode/Length 2027 >>stream
+xXMs6WlOQf$q8vur$!5 iUo$M1N;,v}s Z().ff.7kRu4r-l]7rzh_}jmXE*{X^:bz{I9mwvY6PfMFx2)4UImU t:wdvtr5) U{c2]Rj<Nueu1| O[5U
+p_c*3 G '5U0:Y
+ngS*KO[Qy^zsTZQl-s2bI7cP<vl lP1p5=Z AIWMz$q:BXn6sZ@qZ9>Y7@EL$u\@B[4X ||)f|a+%{0Ag hLjM~z| Uzf.9gK]Geb{e1(
+N-a*Xv}bj-<H29Ora/-bi"WU6)%3jR$lT%\ ! 8>.Kd!A9OqK>t~ erfi
+U;E&p=%
+ dC1QFcN K?1 d7VNQYQijHx,*b@R{ }}t!}p!cJ7V+.jDG @BE;|RH|{#y~{rXAG=Ê$àqÔþj‰®‹ÑEn0v?$},]U8ccT}JR=I{Q,;`D,"\~1Hgh"' QR;C8Zd5@ ;;@7uGV5t]&`CZ~ ,4.MnVA "Q9?84LEzJlR$4nICv{w%=f!|t$(Vv^BFl_rqV%T"@^;tn>(o [G=:*h&p.gzd+]kb&
+@O0 :L7x< 'd\ ,arM.'u\uu wG+U&$Nz @N'nP0BjEjk&_BULZ9^( cVqw:fghG[c 
+vU3}9;I)mD } G7k.h&R2m]!aP^M&o61]?bkF)(<4
+,iwa C$z"{7iLk~q D>a{ qendstream
+endobj
+1729 0 obj<</Type/Page/Parent 1476 0 R/Contents 1730 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F1 4 0 R/F4 6 0 R/F5 7 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>/Annots 1014 0 R>>endobj
+1730 0 obj<</Filter/FlateDecode/Length 1362 >>stream
+xW]o6}@1et]>@I=R`?~÷òÖíx]“ Ž-’çžûu.ý÷(…)þ¦p•Ále3š²)\æ—ø:ϯð5Ã?# v iž>º€l^~7Êfs6ƒ4ËX d)O
+nG^4q[,cOz9JN5]rF,F= OZ5}K~9@L$u_~' TOE0 b%/0,(y2T.Wc`RSGfP.V*uT. oDb$J\%7?0fp+tk e-tO0IgXCf:}dFlZ(+cj(z*gj+BU(J
+5b*VXzi\{la8¦W^[ v<of0yi-{q")#3Qo/[ZDTXiA'¢+wU<(c*HV
+-7{JS%ZVZa{LHy!]rgWaLO'?Ž¢Wr&XI<Wz;f'jjA
+i=AM(-8?PTZL#*?n
+KaI|eizM,GPGdendstream
+endobj
+1731 0 obj<</Type/Page/Parent 1476 0 R/Contents 1732 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F5 7 0 R/F8 10 0 R/F9 11 0 R/Fa 12 0 R>>/XObject<<>>>>/Annots 1025 0 R>>endobj
+1732 0 obj<</Filter/FlateDecode/Length 1374 >>stream
+xVko6_q`&)2M( -RTI)KR$.8`H1~t b~ 9bD 4DP]X£ ֆÉ{&îi·8ESxM[L0K>x$>h%7na`p)Hv2,JZ?TkJ6RF7}=Gp7z\s^oDW(
+&RQZ^Pk
+K~% =o?TxAv EA{ZRRf2|AJnh%p54~~eUZJ2M@@WWya/9]) \jR3D"N;wqNA.4p&[K aW\\-)euR|A]#Z~zty{[gS`@qO ^k<+sDus L%QHowP!/RZ0p|D7ta=u9kNE1`?w2s10VZCy:n^0@^.yuvkjyL=oT. eBP G>ik_|mizn 9# -¼ªv¼ÕYx.rNMM^!u2s;t}i@lY*6d}/\
+SEnlLxO{enRt}w&l5>2J"[@Vi7a:-u&
+9\!'LwYiyQ[ke
+
++wBSQnwE 7LqE`b[t<Q]?%Ymv7}Lnysu-“aâkMWx
+endobj
+1733 0 obj<</Type/Page/Parent 1476 0 R/Contents 1734 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F1 4 0 R/F4 6 0 R/F5 7 0 R/F8 10 0 R/F9 11 0 R/Fa 12 0 R>>/XObject<<>>>>>>endobj
+1734 0 obj<</Filter/FlateDecode/Length 1162 >>stream
+xVmoFHp:1BN:UIwQ/nJe@JU„½³óö<óò½@?\u7(u}o
-cR!6uz6 EzF7ic+fI`Bn
-A*a-1)Kf"$4C2SmEfMZ]vQTZyoM U]ؓìååÖñIhö“«‰9¿§þ“Ts
-6$8[1RMBwz1 J=zSt))HB>1o#g *_ 4fphPB*KJxnD$7YB7mO:N:PRs5Qa>X,l
-i-<EyOo :>^&|+dt<*]xY) lv hh^h2%N syn"s$x50R@B9@} ?Hw`m5Q2Yz!U Y $l<?W hn==I#Snv=>D;t X0[itmp>S`9,bNS5];V\^`z]8 \+d, ] )Cxt,(LK!`+2 [!2<_|xˆ±&SCVV=8 6`T`v`&XqRJ:)2 rh`4.McR^#woq-CSZ,#BXUrfŸzjTi,
-uZ/s-r5kA?0:ro
-endobj
-2730 0 obj <<
-/Type /Page
-/Contents 2731 0 R
-/Resources 2729 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2715 0 R
-/Annots [ 2735 0 R ]
->> endobj
-2735 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [122.225 422.421 153.763 434.111]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.cups.org/)>>
->> endobj
-2732 0 obj <<
-/D [2730 0 R /XYZ 85.039 781.388 null]
->> endobj
-634 0 obj <<
-/D [2730 0 R /XYZ 85.039 761.463 null]
->> endobj
-2733 0 obj <<
-/D [2730 0 R /XYZ 85.039 667.044 null]
->> endobj
-638 0 obj <<
-/D [2730 0 R /XYZ 85.039 667.044 null]
->> endobj
-2734 0 obj <<
-/D [2730 0 R /XYZ 85.039 642.326 null]
->> endobj
-642 0 obj <<
-/D [2730 0 R /XYZ 85.039 379.88 null]
->> endobj
-2736 0 obj <<
-/D [2730 0 R /XYZ 85.039 350.476 null]
->> endobj
-2729 0 obj <<
-/Font << /F20 1617 0 R /F15 1628 0 R /F35 1632 0 R /F56 1642 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2739 0 obj <<
-/Length 2934
-/Filter /FlateDecode
->>
-stream
-x6}Vb )it<}X[[r$9{.$%y4I<lb^B 'g fI*CBna i!L"6e3V[Ym>/~y~b
-$I]/dW^^]ge5nyHUZzujpR:VxH{u!B;Pfp
-VvxwOOMp
-xZ*lJ3jW,QQKc¶uñö÷È×åKI)L[guv
-8a=X! vB_Q.c-AQ@
-]a1@(j$?bup@ v>nu]m'8)X>cE)M uPE1b@Hp="pbG{
-Pa%e_g@'>ta XY&AF ÖÕïBj 0m04F))rq ]RHv Li}ixokc|h:JUF,&-opb@~0!5l-+7NLf [2dA>\7xXX9R8L/g~S7Hh )r). \X!C,P,AY)<c ^Y&;:fye Btg4MHxin!~P&279hAIa6asT*;F w] ;U]f$MRYwuGV .A=o 8{aeRCpnds|(
-i9@<9rjc#-3"e/n<"Ex=F4`jG;ykQ,lR;v["LNb*6Oa 0Il 05LYS4%Hg#w|YzO0c lQ>7.J1v LVV)@ 0u:p
-NBmFPP&rR]Qym
-V\4/4'5ikv_PD/mmb%={Jo4:rINreq|al'LXl_.hD[Y28M~(% wX;]g
-O5Ejpv_+
-\Ööý©QZ dS+W {ETuwr ;vMNEw2D2yDKK5/uE1D
-OHQ7Th$vh996a= V[F>lxd7:1#яFz/
-endstream
-endobj
-2738 0 obj <<
-/Type /Page
-/Contents 2739 0 R
-/Resources 2737 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2715 0 R
->> endobj
-2740 0 obj <<
-/D [2738 0 R /XYZ 85.039 781.388 null]
->> endobj
-646 0 obj <<
-/D [2738 0 R /XYZ 85.039 704.845 null]
->> endobj
-2741 0 obj <<
-/D [2738 0 R /XYZ 85.039 675.441 null]
->> endobj
-2737 0 obj <<
-/Font << /F62 1689 0 R /F15 1628 0 R /F38 2158 0 R /F56 1642 0 R /F35 1632 0 R /F20 1617 0 R /F70 2201 0 R /F18 2207 0 R /F41 2104 0 R /F65 2099 0 R >>
-/XObject << /Im1 2193 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2744 0 obj <<
-/Length 2702
-/Filter /FlateDecode
->>
-stream
-xYmo_8
-"%)2h :T[Z%6un|mD'W!@gfj?5J"h(O'hpV0L ?
-=?p8)Kt4'gDkO{wQ3zhw>evzaqg?pgdt4=P GjvPE;M%I^SEUpb;O8up1f 9X3IwU>0D"9Ad]BQ3<Bc'7ApB(a;3]$Yc|]D:Q(fs5Jh-Ky:žóp ùoŜtµÒ:pŲ¹šr³æ~áú)jW(fDsKna }=x*@=E'IjC#/dP,^lhG2';T}vO2meEc2.s7*?:g^rx%O<o)y i&uS/H)hPpi[ $/[!G5eY>wA%9}CMTeSO ^0a*={'Q:3sM0]K
-cvJnK
-aYHRd#or,/vrk\
-kjDIVEz:0D9Ùnæ&wiéï¹8XN V28'2s DyAQTK:
-b?‘R/XItqn3b}h 3J y-9.vv/X8c^6QNGRTcT?Kr;~e:/&_wp,_lD^8!k[#EcU#8sO%P,n{8Le_C0f+)cCt -+ Q=G%>\_*M}_30`m-/(B/(4|+3FY99<2}9OROXrN+
-%>iyIED8zP%iJ^
-ciK}G<%_ZnzPd|7 U0YGg!x9:B{
-endobj
-2743 0 obj <<
-/Type /Page
-/Contents 2744 0 R
-/Resources 2742 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2715 0 R
->> endobj
-2745 0 obj <<
-/D [2743 0 R /XYZ 85.039 781.388 null]
->> endobj
-2742 0 obj <<
-/Font << /F62 1689 0 R /F15 1628 0 R /F41 2104 0 R /F35 1632 0 R /F56 1642 0 R /F38 2158 0 R /F70 2201 0 R /F18 2207 0 R >>
-/XObject << /Im1 2193 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2748 0 obj <<
-/Length 2489
-/Filter /FlateDecode
->>
-stream
-xY[o~PR0)/fFuEhSBRV;9eq7i"@t.sF;398l/Ecyq<6lE;o.Ea|lb:tgm%v2{`W_0=3ZQ/?Ý.㣬Þ~¸~wýþ f>-:Ƨ[lÿòa{ÆÝâ÷»›‹WwkMC~w{h7%lOcrd
-|O?S3}7.
-p: h|M|d$3>cv+ 7~a:F1A'-02s,OOvGcxgösC"RyNHXA.'
-tjpb)lN " yI^` =bU2PAJf
-C4bln_)D3B*e|Y|_v,M9IM<:p)Q
-H)E
-
-2KH T'
-*VaJ>rR,bVk]xhIi fb#i#R-GLCb'@N<0+#De_wt &DYJNx#:)?YNRD3¯K%yI
-
-s ]{
-(< Ce.R1B^ 0.EY`e0 rSX(
-a>jS}#JhZ6b RE±}-DDy[N\^mV.&nry
-endobj
-2747 0 obj <<
-/Type /Page
-/Contents 2748 0 R
-/Resources 2746 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2750 0 R
->> endobj
-2749 0 obj <<
-/D [2747 0 R /XYZ 85.039 781.388 null]
->> endobj
-2746 0 obj <<
-/Font << /F62 1689 0 R /F70 2201 0 R /F18 2207 0 R /F35 1632 0 R /F15 1628 0 R >>
-/XObject << /Im1 2193 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2753 0 obj <<
-/Length 3836
-/Filter /FlateDecode
->>
-stream
-xZY~_1K>YG%Q#A|fS< :&m$s-o\pnBl]:@,7o?-W[n`/WqXKzdX Ze[ooniWD>9{X73MMvR/ooG{nxP;IM7f_/C8n,_”}ÞrmŸw˕kOj SVT_N_=6u%Vfr(Mb s[X\0"lo
-%TRR&]khI828-/sM[-VP71)pw[yU-KZzcrE:R$Cf~%v}V)<D["9N-nE5.+iw;twJ3L&Ke'+k.z1mK9H
-f[.
-iZ4%cJGE8@Ud6/s ,Lj<ofY:InxtU{,$69Q^eAb3cK
-z1oeU}1.
-
-#,.U r)E/h'"}bcGxQ:z>XZ.LQp(Wdj|a¦/‰ô”Ûu¨Û|æP[:$$P[î8Ó>} Žö¯„N){SJ=8U
-H4z"WFrHVY+e EEFMdJWYyq$^}5xG 5d.*\=60]AsEq~+ <;8, 2x1*/1-d×qÍëxh[j‘2 Z5;D%`_pU ?EFW;8yK&t0&.
-C !0M]YMI} C.|1Z1ClNrb<b[>#~R
-@\1B
-CVp $nv@#@:[7H-N% <q+0
-;+kE%,P|D
-/
-q393x)0BpDtx f?}:yX7#'S?>~:dJ Mk:
-Z\!òՍdR:n#G4#1Xh/]TnO~xa)D3`V3]}R6HuB ZgBl3l7q?f tQ(U8\[ sPj1=
-Ff//L DTb]@6\:!hk-6_3{qLJ=K,M%]*z?kh. U=S|Bx>(6Kt=/`#q$U}0=gE?}8 r0|M-7>H:lv2-Y)|}Y?.^PJj!,arwSn4@ Oot s[B>Xx6,UvQJw
-.;fm6978704s?Wf '['8 !2@dc6Vk5xN`]K
-{\%E$2&X3&c/#,~NNCWR|0Q])irP_endstream
-endobj
-2752 0 obj <<
-/Type /Page
-/Contents 2753 0 R
-/Resources 2751 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2750 0 R
->> endobj
-2754 0 obj <<
-/D [2752 0 R /XYZ 85.039 781.388 null]
->> endobj
-650 0 obj <<
-/D [2752 0 R /XYZ 85.039 609.395 null]
->> endobj
-2755 0 obj <<
-/D [2752 0 R /XYZ 85.039 580.597 null]
->> endobj
-2751 0 obj <<
-/Font << /F62 1689 0 R /F15 1628 0 R /F20 1617 0 R /F56 1642 0 R /F41 2104 0 R /F35 1632 0 R /F65 2099 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2758 0 obj <<
-/Length 2415
-/Filter /FlateDecode
->>
-stream
-xYoB]X
-hk>+v
-H#{~PM;)
-DP~&xifO 8PUe_7o w
-Cnfi U#?>~
-%UEuEhTe__\{wjX3TQ8\@c4
-gL[fH|cxLh lT-W{S]Fg~3Z
- oi=L f#[YH/q
-7|2y
-s-,w,$-c-NC-NicMj #5TheUK%a*Hr"CpqL>cJh5+2Nzhz eW#Ej+.P8#@,0,W39u d[\WRg ]o)
-C)JX(urESne \N t*hGtMYPaF@ek
-w2h48pqP 2[ 9Db!Q
-2D\<bts,hOI
-.v?w&:IMu
-hN gy=w;?&0"8TD,!0vA4a"h'{@OL#Me!AOtci?n#~QA \[rm_Sy<A$-|yq53~PbK%S~XX5 :=-XRn%r}0/gt'E^Rì8§È³•â žÆA`hk30\}7Ch*gQIeDBfD
-endobj
-2757 0 obj <<
-/Type /Page
-/Contents 2758 0 R
-/Resources 2756 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2750 0 R
->> endobj
-2759 0 obj <<
-/D [2757 0 R /XYZ 85.039 781.388 null]
->> endobj
-654 0 obj <<
-/D [2757 0 R /XYZ 85.039 718.394 null]
->> endobj
-2760 0 obj <<
-/D [2757 0 R /XYZ 85.039 688.193 null]
->> endobj
-658 0 obj <<
-/D [2757 0 R /XYZ 85.039 442.883 null]
->> endobj
-2761 0 obj <<
-/D [2757 0 R /XYZ 85.039 413.479 null]
->> endobj
-2756 0 obj <<
-/Font << /F62 1689 0 R /F41 2104 0 R /F15 1628 0 R /F20 1617 0 R /F56 1642 0 R /F35 1632 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2764 0 obj <<
-/Length 2971
-/Filter /FlateDecode
->>
-stream
-xZrJ}W2in8f[cs3KX(~…=™:s¦Re5M_^{MQ Ga
-/F3ZA{8#%<#e|i:?۞çYc; #tZ3]n.IAkOny|3
-</:%,#87G#{W~fGmG65vg+El|)` o"U&j,dXZqc&TWV )tiM/Uy<V=>-|2|k:rY746e;^")+u_3&[]<>õa‹óаKA.Rj3_gc CEp?;ISyv5wyVfi PSkd{EQkO&EAlirE.9c&^lR:"~UzTJS1wkCӋ›œqÕ2i¾m(ùŠOg8l I "zym]MJ' &vE
-[&iu`n!1L0gpv):"I`%w,=:)4]]B2&9tu=M[SxI#73kD=F`+sK| \'J#VI7{MZ)q$aR2jgQ:m&\so9n
-9Ja
-e*GX9th ;ZeXHP9W`nRb CkmPNOi5I/ Mp\E~HnKnZ)@n 6L`Izg]w@et\9|\\ Il(n@xBq(<DY 7/3w ~FgûÂß1_õ3æ{2;µk-E8FeamF* SojXiK8-IuO@.:K6K+}%y<D&I@R<O^j JD-EpbÒ2”ÿ/NUNVW;u`-$Mxd^a)"'[D<|M#q2LdH~wS% uGd&E! 4u$A.W~pv~w(
-Zf=hO[.EG)&} | 7m<_8RCp0!_oPY"57wYYwo_"w%38`O{dH*_#;?K'Ni#
-v:|I/J  wP[wz4_vFbe 6 ZM1D^Xo36;ko $;endstream
-endobj
-2763 0 obj <<
-/Type /Page
-/Contents 2764 0 R
-/Resources 2762 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2750 0 R
-/Annots [ 2767 0 R 2768 0 R 2769 0 R 2770 0 R 2771 0 R 2772 0 R ]
->> endobj
-2767 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [138.589 394.756 387.717 407.658]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://wwwl.easysw.com/printpro/)>>
->> endobj
-2768 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [157.067 304.494 429.341 317.396]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://gimp-print.sourceforge.net/)>>
->> endobj
-2769 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [138.589 254.88 347.128 267.782]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.turboprint.com/)>>
->> endobj
-2770 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [138.589 218.816 508.187 231.717]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://www-124.ibm.com/developerworks/oss/linux/projects/omni/)>>
->> endobj
-2771 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [138.589 155.652 336.156 168.554]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://hpinkjet.sourceforge.net/)>>
->> endobj
-2772 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [138.589 119.588 400.551 132.489]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.linuxprinting.org/)>>
->> endobj
-2765 0 obj <<
-/D [2763 0 R /XYZ 85.039 781.388 null]
->> endobj
-662 0 obj <<
-/D [2763 0 R /XYZ 85.039 491.246 null]
->> endobj
-2766 0 obj <<
-/D [2763 0 R /XYZ 85.039 461.045 null]
->> endobj
-2762 0 obj <<
-/Font << /F62 1689 0 R /F15 1628 0 R /F35 1632 0 R /F20 1617 0 R /F41 2104 0 R /F65 2099 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2775 0 obj <<
-/Length 2593
-/Filter /FlateDecode
->>
-stream
-xY[oF~]*wR]Ikp`DUw|eN,Ds9sn0? pu #c#S(ž‹[ïæG50 }bL;"G7O'pdf:p~1W39hj)n_][oN#Gw<åþ~tsk "P``s:/-s|cy6 pZ3M?@e<)`LK*%NDy 98BpM#qBL,-P<RTN:{eKQi&:fBVMga/,$&pdZ2`9/
-lC(~HTW:x"MS84"=jcBU4=A5;# kh
-`AT1AR S?#pG6Vw='[ Ei>aM 13J> EaxpkzGqHd+^5h9 n>B m!4e($xQu.<G Sf9yniIhGebbRZbP %8*'>}
-)1Yz]°Û%B(3kC(V*
-FPkNK<XV8U;_J>LlIm.f :WKN\VFx:nCMM, fUFst]'R:9@H[xGI8= (kdzx,y3
-`}^B2oh0v)60]%X`W10x=w7E.vk]QtkC
-}|Yn[#-4_eVMt.# g2qm/$;$o(G|'d tH+_7OF:_z0K/:b)'}W\@E-DV2B S`_Iq%nH9D$DLVRgM?pj%&WnJH^'R~<?}Sx,AB-qPZc6P
-xJ{)qv~,F=-86F#s#}RLym=gM/y"¶UdWFNawJ\Y3KbcIKl7/V]:%G&~&,
- ~@\
-$ >dc] &5Tj>é£hA2F$F qhIh Iy^oujq=E[chi;??%Kb(ss%b['AkX)vayFte}hx[[Wcf dqw8 18 CdbmKv|+2 Eo!(M+anmw]6 S:n|yUj:/Ƀ¿FG_#_2')CQIfmty:W7,C{{$
-%Zcy
-R,
-endobj
-2774 0 obj <<
-/Type /Page
-/Contents 2775 0 R
-/Resources 2773 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2750 0 R
->> endobj
-2776 0 obj <<
-/D [2774 0 R /XYZ 85.039 781.388 null]
->> endobj
-666 0 obj <<
-/D [2774 0 R /XYZ 85.039 543.429 null]
->> endobj
-2777 0 obj <<
-/D [2774 0 R /XYZ 85.039 522.232 null]
->> endobj
-2773 0 obj <<
-/Font << /F62 1689 0 R /F15 1628 0 R /F56 1642 0 R /F20 1617 0 R /F35 1632 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2780 0 obj <<
-/Length 1210
-/Filter /FlateDecode
->>
-stream
-xXmo8;[BwhH4]T\8@x ]*byf3 R 1#@8W\P
-b?'[}EnjuBHQP:^ 5T$?v /5Nv:Xj7b 2 P
-E,c4  2[%P|pC~w=V7<W:@yo9#I N,C>l`}aM~4/nWncuziz,W/,f8R])\9wUFToTb?n$2
-a
-PL[>qvFUQKMC@:kL s(v.(Tyh'BJ1]HY,\ d{+¥>åގNfQ&m>Hz ntD rT
-endobj
-2779 0 obj <<
-/Type /Page
-/Contents 2780 0 R
-/Resources 2778 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2750 0 R
->> endobj
-2781 0 obj <<
-/D [2779 0 R /XYZ 85.039 781.388 null]
->> endobj
-2778 0 obj <<
-/Font << /F62 1689 0 R /F35 1632 0 R /F15 1628 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2784 0 obj <<
-/Length 2269
-/Filter /FlateDecode
->>
-stream
-xYoBuZBtS:i
-AAS+5EH*7C&M`;;;8p Sc? d72wnd)
-sOg-pm$Zf?ODBhcLtV</K\B&_w'_G5~d" nVw#5F/-^sk@;1!@']F8Pi~7]b[$R<$EB=?EQI)sTzl
-,:b5QNLg09OG5=v\%,ZG[Y[{!!HdVo%!-%h$ MM$l6& w6  zTleX=4Y`Ofv ßÑZKe,gPv
-52PRXem0G3SXRLv]bD;M`C{1@-Yx.=W?>*eR5fT}<95-Tt,uP%dgEsZ1=Eag~$taYuld V -csjx g $9?#'Z]SM8X@ ju<~Tj[288<n-ªömáØ ÎQ;MnMYe
-dgS9c
-D"[1 66}##Nh!W+OK$
-- ?n"l8jxXzAH6JNl+o3&s]L!X7^_eX.3 Tpe7AYXmmK 5?m!?J1R!K+P_1AQJxS[4qL-z'zTM/t^o`go"eyoA@US Ht4C"qIJm);
-endobj
-2783 0 obj <<
-/Type /Page
-/Contents 2784 0 R
-/Resources 2782 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2787 0 R
->> endobj
-2785 0 obj <<
-/D [2783 0 R /XYZ 85.039 781.388 null]
->> endobj
-670 0 obj <<
-/D [2783 0 R /XYZ 85.039 421.906 null]
->> endobj
-2786 0 obj <<
-/D [2783 0 R /XYZ 85.039 395.291 null]
->> endobj
-2782 0 obj <<
-/Font << /F62 1689 0 R /F35 1632 0 R /F15 1628 0 R /F65 2099 0 R /F56 1642 0 R /F20 1617 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2790 0 obj <<
-/Length 823
-/Filter /FlateDecode
->>
-stream
-xVKo@+{R<#:8!Jlj/i&<
-$.7ucKo+
-PetnPdi/7q>Ng.Ji1"hd]f~^B
-M4IZe<nsG,5n-EI#-EM@Brw4[5U[AyVIžÏʸendstream
-endobj
-2789 0 obj <<
-/Type /Page
-/Contents 2790 0 R
-/Resources 2788 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2787 0 R
->> endobj
-2791 0 obj <<
-/D [2789 0 R /XYZ 85.039 781.388 null]
->> endobj
-2788 0 obj <<
-/Font << /F62 1689 0 R /F35 1632 0 R /F15 1628 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2794 0 obj <<
-/Length 1130
-/Filter /FlateDecode
->>
-stream
-xW]s8}WxDl2a)I7/>8kd#t uuGGt4Au0m5 =[ nztTnYAq;/^u7OV,uxbx:f~?FVX`Ag[_Z}ju}-mY mT5oU{c&gX40uVL>8xdWV@D}gm<\=L>B9s>=_b~Omp40rJakz'e|<@H2U\HH<8<+vN(a33)/0f z&Gq,L,J YRFle)NT !/SNz;0ÌË-$Ò¡wڀ~=Œ‡£²%lŸ¨°,^$Â2Gg9K'U@RNq $:Ql \eC}@IeD&j#eso4]`9|V+þÄZN1qh89^#z
-nFT*_ut)³]wAVU<93vX?-vsQnl*j]61>$mzgU
-endobj
-2793 0 obj <<
-/Type /Page
-/Contents 2794 0 R
-/Resources 2792 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2787 0 R
->> endobj
-2795 0 obj <<
-/D [2793 0 R /XYZ 85.039 781.388 null]
->> endobj
-2792 0 obj <<
-/Font << /F62 1689 0 R /F35 1632 0 R /F15 1628 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2798 0 obj <<
-/Length 694
-/Filter /FlateDecode
->>
-stream
-xVMs0+R$L. F%1fb
-¸žÌôÇW $·±‹g–«·ûžðbñ–M
-d<[IHsH iA Y2{*^s=@Q{0LzXSo;,,?WGI{`Z j:)!? 9%e[>G[4J He/%_D>Moud4U'A4 H )R~h o}vJ,^"Z81[(y7ghx|ccPL?&oz' [Y% 0w~;O8Yy&i'|>P~qZiC(^Fx)%+j"&f>b\ia-}' ~v0r []*p&
--",T[yw:U,hqbfim^iNeQ
-endobj
-2797 0 obj <<
-/Type /Page
-/Contents 2798 0 R
-/Resources 2796 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2787 0 R
->> endobj
-2799 0 obj <<
-/D [2797 0 R /XYZ 85.039 781.388 null]
->> endobj
-2796 0 obj <<
-/Font << /F62 1689 0 R /F35 1632 0 R /F15 1628 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2802 0 obj <<
-/Length 874
-/Filter /FlateDecode
->>
-stream
-xVs8~`|ggr3>'tZ^&1l(t8.6vz'IZ}i%Q11aj;3QB{\+Tj2Hy;tWZhUÝ ƒÈ› cL v`@P3k>2`j_.E;"ãû~W~#}Pf>A`J1LMq!3T;dm07
-G3?Np:c9n!ww{>yu!UB{( T Q'%"nH*+O I1ijDR<K&]GF90nJ,(l8[7iUV)_ eVm`U^:=VdSUy*7Tt\nSUVE5)4oI0†mQ {s]Yy1nct.a_|;FU\CJb[C
+-RH TB|'BfD3!"mX_
+rKi'JH91
+vB@) K.0+^~YPc.,t
+IxJ& 
+1g !q!sHv$BFLA5Q/-8q21K2gJrSmj_gjN#Uiv8: | mNs 4Z494c]0sFW@m!q\rB3(+)Vn
+z9 {Ts,C
+[&CS9waD\&t)rLMe|k~{(~yx}=^.Tus 
+">EUsSfPG4|<Nz~cG.=4C,Z_N?n *aan.f<y8`$<]vy}1vffh5T$u0]Ak6c:endstream
+endobj
+1735 0 obj<</Type/Page/Parent 1476 0 R/Contents 1736 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+1736 0 obj<</Filter/FlateDecode/Length 912 >>stream
+xVmo6_6g^*ncH"l%b#H ))s(+b6"^;=
+-4wT^!+O+u<Up{!j-=w6C4!;ad9_FP+FP[.V\d@V'R;n$%`|:RV:)<#^!7^ J^3B)Ys &@(-7X"'
+ RYULm&tucZ#b5O JWMwUo$r<-*|}bxt#`*UhBMt^O)>m]ooYaU |3iU%c9LD3wFnBI
+oR[3eNljK]mOeYH&#xoendstream
+endobj
+1737 0 obj<</Type/Page/Parent 1476 0 R/Contents 1738 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F5 7 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+1738 0 obj<</Filter/FlateDecode/Length 1057 >>stream
+xV]o6}Hlmdi=d
+endobj
+1739 0 obj<</Type/Page/Parent 1476 0 R/Contents 1740 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F5 7 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+1740 0 obj<</Filter/FlateDecode/Length 1426 >>stream
+xXn8}W /N@Rt E?(h‰ŽÙPKRu{mYQAv&glBUvM7_'iufq6~wM)-V82EAx|2E>Z9[RXK:_|ey?QuuF6UfLy?RZ_JÐ6AYCvE5\EXMLrzr*TgPY_]Mi+Pvcde'C~Z8$`Pt
+I+:#!gsW 7r)Z
+z| x}M*L}I\TN3ROPV.Fb,CaeEEfVz26 -#kad}| -W
+ ^?0CSFNV^dZJ" qJM=l+Ni 
+J?CR H"LAIa2stpi`^
+ntmN%y-Hl!'i
+isiy#tWT i<jCp6q$3q3Zv n:r 4+)%#a~e)O48=T9.
+u"]bv&|,=|yR(Do)m>m/95x=}t .U]/o&X Q{{7=}fW3|g Hx;oendstream
+endobj
+1741 0 obj<</Type/Page/Parent 1476 0 R/Contents 1742 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F5 7 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+1742 0 obj<</Filter/FlateDecode/Length 1007 >>stream
+xWH}+J!4[FBQfZi%QnCGvLo1dFca}tB/
+EM5pSTzr2H% F,-9h?%8"ki^[1öÃñç³àæ—J9b 7 5_u(
+w57
+endobj
+1743 0 obj<</Type/Page/Parent 1476 0 R/Contents 1744 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F8 10 0 R/F9 11 0 R/Fc 14 0 R>>/XObject<<>>>>>>endobj
+1744 0 obj<</Filter/FlateDecode/Length 1257 >>stream
+xVn6|W`|-4M.-Q2w%RKRw%Z`m2gf =f1%`bGS/x="ZZ?ntI 9%^1mn>4r}&Q+EADQ#'*Z_*Q>}hB2esM66
+;nNw=IL|IRcol`vNIC4fHHSBiI"%J{J o U(-#9(Sjm!]C.j9/=dV rQb~gM]
+D83}A\>!&?8OT>D |"
+@A;
+"E Nv-(|Niu{`PeQ]]q^
+ _a]66phÐ1%[¤̾ ā‚<Œ·_XhAL  rfU*)]‹ç–¡vPX*+~JI,&_a9p&4\DtmtRpo i 8:;QtZ.ZSY%;XLN(>ag8)J
+endobj
+1745 0 obj<</Type/Page/Parent 1476 0 R/Contents 1746 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+1746 0 obj<</Filter/FlateDecode/Length 1599 >>stream
+xWQOH~Wx)H7(W rR^]4!1<*Jpo'S)-f4>Jz>Onv3xM|qshvEiP7[JsB+\i"nsZy X
+^_2](kdJ3<6MF[r5M#Er<'?94Y 5v-MVRVm@L2TJc(`!]Lcp*u*i pPZe-UK
+z TJnlKk2-QnM [ r
+.Dw'= }q08<{I*JkweTqY; e]:~C|+ R'!/_6VC sg=_.>~
+S-/E?}i%]>%3waME&u$1JvF5KjLz_5zXu KYP=DS#R
+T>n{lky= *Tf*b0{D;SmU.Cv*8x 5\8'*Ufr4}|99O _vnjxZUk@{!%crWs+·fÄ<1!ó¦ÁV@mmImXcGLz}0jbE 4:$T&Pee y&";8HRwQ-vv4g+h:P3M%(r^"=?} o#(#~)=(>fV 1i^
+Ju2JZ#&[j=tWr |\xRW# Jm'wZuY^sr La@$G/ ,ezzq(.(|$×ñ{.'·ãí ¼"2Ž>â˜9Ð^¦
+䝌«ÚQZ'gd91UDTd:ZcON {}g)H{On} 8YY0p}+>`m)j+cxXt9%H  zfKI2q+Z\7GbNQyX;pyvfT`KaN4!itMW
+endobj
+1747 0 obj<</Type/Page/Parent 1476 0 R/Contents 1748 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F6 8 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+1748 0 obj<</Filter/FlateDecode/Length 1709 >>stream
+xWr6|Wx:S{F-N!©M$XTidd vft3Zi::Oiq9Otq99M|p74[Vmr6Nfdi+moxfXMd'O
+[-{vkF]YTmRW)7eI;]6b;jM@\1R?lAsT9Rm[mU+{gsn)uv:)F'Zs2iyQ#
+("SxTP*xivu{4y~poU*Een8>P'x!au^:@jm*>,u/`9735{rvZUz<L6fP?
+v?y M9V9=ix:/?x
+~@O0j8+ zpZ:c S0>gFp0XB,pT?{;x<LaXEq&pq/*U*?2<]\| *Y4RoX^: tA#aC:AeS3Ex{OB])HwMc]N7?kU/\9d6zP:x`9$CI2)j(rF Btl%HNzB "^a5
+<6*0D;L".yAG"E lzU|yeŸ`P
+8\6uE?1qgQe4rd0Sap\
+@QD0]c+R]$2 AH*hbO;r#wx-jAs~-?f]3}U/_7G Zendstream
+endobj
+1749 0 obj<</Type/Page/Parent 1476 0 R/Contents 1750 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+1750 0 obj<</Filter/FlateDecode/Length 1570 >>stream
+xXn6}W[ @m
+*˜ùYDw; 1aaTqd_NALg5TRZMe36 E\T4,Tr#}r]SZ3md)T9k9
+5wYzfakjLPq
+&!J,
+ZVKSHdx5m,%Y]9L4gPr_d~K|_fC8 ;qjeKx
+endobj
+1751 0 obj<</Type/Page/Parent 1476 0 R/Contents 1752 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F8 10 0 R>>/XObject<<>>>>>>endobj
+1752 0 obj<</Filter/FlateDecode/Length 1239 >>stream
+xW[OF~8P%^_hHUBè’/HxI<g~7»Z!Ud/s? iH`yw|}ZGUR(Òþ·ïfû ,p=òq&Ç39Ώ—>ÂÀC\-%j-y{)HDJtRKy7
+EB[Ev[]t^j"#6ŠKS\V U^(TAqZjg^c;azGxt
+=BcZaTo:Ekk4Vzgp-GCzER46[&\R0BHun,rRqHSxKn.#j~{,W=qbNs."iN\~ f?xLQX` qt3NtHm0D~.T<i"X^ΒÔúl&‘Àž3MeF?wR
+(x r<ROZw5#7vy.%DrFPGMmc \n{|{&Rwh E(Cum
+]t[V T7}lqp0 6/ #*J X$8@ ^o~5As i`Y.no g56e0V2iuV% td )ch cnMaZ"}uXaf"U}fU`9#mz%#Pd" cbMy$nbS0)AZ̨ œ`Pm{bcN soM]hn"`  1|[*a
+Tl)eRSD4}MtU*g_Qat'QpxG
+endobj
+1753 0 obj<</Type/Page/Parent 1476 0 R/Contents 1754 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F5 7 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+1754 0 obj<</Filter/FlateDecode/Length 1491 >>stream
+xWnF}W he@J -Šº0VRU./
+4uj4o;sf,r4f4q<9?1_%)]F7'dq~FlFt|(VRaRQP)+d?7zTQF(k62SoVG3(YTTO[(Jo?RF@)2aIlI`S9iVi $3 ø7yŽX8-: Æ<âúQfFo$:aw~.=gt$úæZLO(hg5O/b2+"\_Lxo'4vH#lwopb7=Gm4^tc9EOued(
+A(WjEgh)5-B~U'i*!<S=R^M mn|}?- ah0@8i'0=FTbb|3#Ns
+ZOzZ/h8#+Sr4w7itGs("A)=-\V]}pfqSOrC>Lt:L[?Xd;A`/$sfU* 2AxW JKW]T]2oPMK|t,:N:lP#Nk}^ {Z`=^4[o= z[#7J$,iPH5V j]?f-
+Vj@N-bVSO$7hNd90HEq&BDeD>cd.*lGv`>r-L-4=\`U"zUA7[o6wJ@|a kL|
+z2[Hf§¼kTJ|uX)C-W(Ik~Z{&3IX_&^¥Gt*
+endobj
+1755 0 obj<</Type/Page/Parent 1476 0 R/Contents 1756 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F5 7 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+1756 0 obj<</Filter/FlateDecode/Length 1544 >>stream
+xWnF}W "l
+ T[+ihS
+ys)pII:&65'NTsN[jGBl )b 3r>.[`+RW6|'a);-HkIrBsPOy<K =RN<f]]YN`Op.$
+Whu%Hp%x} 3Gy+ ŸEm[~$n(89H?z{O""L+d
+d;8+n}_BeDaOHs~ xv`@fCK$]%czq,N=-JxrlgÉÓ¥ /Xn?Madmx:+o
+ UA0W$|z5^L|liOz}VGendstream
+endobj
+1757 0 obj<</Type/Page/Parent 1476 0 R/Contents 1758 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F5 7 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+1758 0 obj<</Filter/FlateDecode/Length 1325 >>stream
+xWKoFW | X%\nH%\KZ7KFm.4A`1’¿Ch<(OlGWJJz7>G&)1aS.&Vu,tZT$E&?tiIPp{#Q*HdX,),Fgsp!QTGn)-bE06~0qÌ¥JabS}7i}s kz8Y6kd]+YlR)W(JvLZQZPJZ)SKkz8(PHv/E
+B-Q7%QY6i"T
+O *S=/ CI(IQ93;mlzt5lw^/i+ŸJYi&6o &2ve
+;]T1%>VK+MmZWVx q:4R,QgerD
+endobj
+1759 0 obj<</Type/Page/Parent 1476 0 R/Contents 1760 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+1760 0 obj<</Filter/FlateDecode/Length 1558 >>stream
+xWMoFWLur
+?ul[}>]5_{pVIw8E;[3Gm Vp|N! xA^qXw
+~BKFc ]z]QEq P"JzWwwp!4.{XkxYmgF+c&7ew2BWA\ *WI.4hqm)MI]6IiAErAZUuK6dU
+ Ib%IR|}@+$!;Wk[ˆë¼ì¹ 
+‰‰?¢‹G/cCWuN),dB)zp=H a!3 ~RDSk( 1#MNWe
+r#S~dU
+
+fM7J4B3v= ;g+h/6*|1X0
++av`P'TRlS.Eq|kP|XuJQ8cX0XU7~%"wBqR
+A?#k5X;`Req1
+endobj
+1761 0 obj<</Type/Page/Parent 1476 0 R/Contents 1762 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+1762 0 obj<</Filter/FlateDecode/Length 938 >>stream
+xVMo8W ri
+Xd9[nr(DjEj>(EaMr7wSWL%JEF5w[<%Bd w51r$t !dBI, d3x*}cmD
+3bMCt7,&<`V4m-XmP!
+J5hSGIBr\eJ/IXRq08iDA+i
+ia)=^td `YUW\ 7| !%;Qx$AP?6N2i=lZPY}QvF ZvKjJ{ e"(e ,I?QAs3jSUu#b2W?5J2f7jG~IOG!LJx ]5p o"$Do8
+8gp*=u~d:?ZS?2<&"hC0zMM(+X:n=SsN{Q]XapKpMS
+endobj
+1763 0 obj<</Type/Page/Parent 1476 0 R/Contents 1764 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F5 7 0 R/F6 8 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+1764 0 obj<</Filter/FlateDecode/Length 1136 >>stream
+xV]o6})q}lPD\JC "^s=rUAd{%+<jWIyz,"m _5m+ o{RNfNE77jl{W\&\Fu7XADW4]oG+M<dot'9Iv</FF#T!~zrr Sh!k!rTG=IcD9
+ mhIs#4>Bg1
+9$zaE,tsxN5J}SnfD V;hxjwF9=
+endobj
+1765 0 obj<</Type/Page/Parent 1476 0 R/Contents 1766 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F6 8 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>/Annots 1030 0 R>>endobj
+1766 0 obj<</Filter/FlateDecode/Length 1271 >>stream
+xVMo8W ziK?m6E{(PeH[e  u ? -S7<KyZ3STLBZ .f?Fl)PZQI- eXlR
+NE)|l?])L0cgbt3V#"  !EvNYh
+[l2?Wj
+3}ykbbs su8OvKERVt8x
+e(Az2{(A|)Xc @vCOd7UFd.w;vW6hsFxbx/xe FRJ'endstream
+endobj
+1767 0 obj<</Type/Page/Parent 1476 0 R/Contents 1768 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>/Annots 1033 0 R>>endobj
+1768 0 obj<</Filter/FlateDecode/Length 401 >>stream
+xeQr0
+endobj
+1769 0 obj<</Type/Page/Parent 1476 0 R/Contents 1770 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F5 7 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+1770 0 obj<</Filter/FlateDecode/Length 1413 >>stream
+xWnF}WL"hhsiI
+eEI.D) ¹³3sΙ‹þ>Y?KdbtqssIW'gn)_jZ <)+9ihyOF5T?~^}<]=`>obUN?9a)W'JP>#AMN%$T-hUI*zcd%Ok(=9!,h<J[y7[I{nB,C1)f dq, N(cy$Y qp8R7B`f Mxf $?Sj[+>v
+wr%UO!ZYGxn,pVYIe"*NGi3n$07UM"R3IOkhC3Yx/Y $k::*C!(%g`^`z !‚h ;£·
+èÀIK> K.H1A0'?0C>.5RwQO[8*PiZ@/0,`OGmTF#JeSx kdL0>wqV(71HX@|ÛäACcp@8FpkpKzXx5kM$E (}1
-iNm+<Hjj~qqe=VEkRPYn?-8t *YekI_%8mTb6 EMX!6,'9SiN]UDbozuV;@tiz}"$SS5--:[T7+zRbf<wsendstream
-endobj
-2801 0 obj <<
-/Type /Page
-/Contents 2802 0 R
-/Resources 2800 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2787 0 R
->> endobj
-2803 0 obj <<
-/D [2801 0 R /XYZ 85.039 781.388 null]
->> endobj
-2800 0 obj <<
-/Font << /F62 1689 0 R /F35 1632 0 R /F15 1628 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2806 0 obj <<
-/Length 977
-/Filter /FlateDecode
->>
-stream
-xW[s6~W0CMPw^oe.d2?~68@6gtsSEh@Vm P-K w,ò²¨ÙЫ¥ß}á꽡ˆPlGX$UUP34fMI8uzfS(,YIVv
->bD}dH2-MW;<L)PL:Pe`Y<V JY_S Ele>lN-_wV+w|vWaS3i-t/UE85`
- [?cFb9*ybwvw /(z,W6$8 RJl_l_(2Un#/we
-znq.2 g<B<?^@r4D=9+;yULE
-3W&|si}([@TJ
-endobj
-2805 0 obj <<
-/Type /Page
-/Contents 2806 0 R
-/Resources 2804 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2787 0 R
->> endobj
-2807 0 obj <<
-/D [2805 0 R /XYZ 85.039 781.388 null]
->> endobj
-2804 0 obj <<
-/Font << /F62 1689 0 R /F35 1632 0 R /F15 1628 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2810 0 obj <<
-/Length 873
-/Filter /FlateDecode
->>
-stream
-xWn0}WD];sX(U YHyPa
-kf~E01<LvnNU5])P{/; %E43oR+ea, *I:Y|`E1"bPyZN 5e7F6PC~?endstream
-endobj
-2809 0 obj <<
-/Type /Page
-/Contents 2810 0 R
-/Resources 2808 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2812 0 R
->> endobj
-2811 0 obj <<
-/D [2809 0 R /XYZ 85.039 781.388 null]
->> endobj
-2808 0 obj <<
-/Font << /F62 1689 0 R /F35 1632 0 R /F15 1628 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2815 0 obj <<
-/Length 2725
-/Filter /FlateDecode
->>
-stream
-xYoBP?JK.|hHh1)2)J M}i9(]KhQ9>s8>FcMh~O$2\Q—ßÎ&®qË£³/7Ÿæ7Ÿ®±çàk|;ÃéÏ_&±2æ“çÏ®æ½cMCrh }<s,5G[h;;3?PV+ggv9ng^hy4c]S |wy;ys53^o"WvKky!q,rctOWZs?ER^;}nx'pQ-a1]_9ngmfu*<;[JN%W3ao]tiVD^02$9R~7^c"BkF.Ra2O"myA C%\<~d26+{
-z{*/G% ocV' ›OK[ ]H h!#
--1>SDbz?p+k1H}`l YsNup('a2}J6:A#Z&RNlOn2];[B0t <O1~^e}g}y+;gdMN3p
-B-\4^v2Y%KzVdzS=SivvGJjU$V=$w$X7#0# ]Q,Dq4i,3):g0zG8@.@v.x=FB9:#kv~UB(ck,m5w":[AiRyOrAQa_kw/Ej}br+yfoXcXùŒ¯ªô„žTBR1q|K|VAu*H`}V$~;s D9
-bI<%rc  y'@A+_\9yF .endstream
-endobj
-2814 0 obj <<
-/Type /Page
-/Contents 2815 0 R
-/Resources 2813 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2812 0 R
-/Annots [ 2819 0 R 2820 0 R 2821 0 R ]
->> endobj
-2819 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [122.225 376.733 381.942 388.726]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.linuxprinting.org/printer_list.cgi)>>
->> endobj
-2820 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [122.225 322.537 456.396 334.529]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.linuxprinting.org/show_printer.cgi?recnum=75104)>>
->> endobj
-2821 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [122.225 281.889 450.669 293.882]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.linuxprinting.org/show_driver.cgi?driver=ljet4)>>
->> endobj
-2816 0 obj <<
-/D [2814 0 R /XYZ 85.039 781.388 null]
->> endobj
-674 0 obj <<
-/D [2814 0 R /XYZ 85.039 585.023 null]
->> endobj
-2817 0 obj <<
-/D [2814 0 R /XYZ 85.039 556.288 null]
->> endobj
-678 0 obj <<
-/D [2814 0 R /XYZ 85.039 439.067 null]
->> endobj
-2818 0 obj <<
-/D [2814 0 R /XYZ 85.039 418.477 null]
->> endobj
-2813 0 obj <<
-/Font << /F62 1689 0 R /F35 1632 0 R /F20 1617 0 R /F15 1628 0 R /F41 2104 0 R /F65 2099 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2824 0 obj <<
-/Length 2935
-/Filter /FlateDecode
->>
-stream
-xrF]_C
-MrUj+k;Z%W$ A@f
-jbz{4khUW[n @oZkB`=p6#`-e
-y;
-9SY=#A{YqUE G[si0$iq`7)6kZn? IYUDsD
-qC1z-sKlv8"/p'y A71<A7$vzVcor \Ine;pN%v9c
-G,,2hQa.l+@DQ-DuB;h%z; vs Z:iqc S.z=_lv+cF  Bc"+
-.S8Zc/;s E(O,>j,i=qGn+0ICf3 o>k2kh/D(x)=}="M�f-Nx[T}|<4|" (T834& 
-AcM-~I
-yb@Gqv:òæ®çډò¿ª;Ïà^÷x¡öbÿm ò’ÕßÀlõ ÁA/
-\G}c_m~{v_dA`q?
-8A
-2y%1sfaX]~S%g'TK nVz>!|9}&%Sx-Yo@uzX04~`DhliV4#s1p<z!vK3O Y[I7Vq% 8CDC!fn5uL.o~q4b :v"l'Wc)W)>T=$
-4:j㋲ùÃ"‡D9T$||
-\u`j&h?TC_"FDR1T"7KJp%6YpvxW\=d5wOopgkT5VzMny"oJ ^}}kT
-yZE_y%p~?f(zdym*#{ X&7 Bt#&i;n2H99X*gr@we1/SLS{E>P?W}uKz_#mVzk5@r eA'(7L<;p {Q7&3ktzO$%Mi!3E^6#o}>6AQkN5.8b^!-WluB m/V;7&~6Y2~C;XCA'>?xN4{I4/y. `p2;fo#.83lW/'pxSkni
-+Ml_w;yy&b֋ã§óœÜ½\Ã@G__m1=~-N`xH,m r#yp51DA8#e
-Hko`@L2I$+X;!u;-kV~Y+Y@)g"=]gQ ,+E4 f~r= "Dl
-endobj
-2823 0 obj <<
-/Type /Page
-/Contents 2824 0 R
-/Resources 2822 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2812 0 R
-/Annots [ 2826 0 R 2827 0 R 2828 0 R 2829 0 R 2830 0 R ]
->> endobj
-2826 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [122.225 706.436 347.579 718.428]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.linuxprinting.org/cupsomatic)>>
->> endobj
-2827 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [122.225 570.944 512.306 582.936]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.linuxprinting.org/execution.cgi?driver=ljet4&printer=75104&.submit=Show+execution+details)>>
->> endobj
-2828 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [111.316 559.819 279.398 568.478]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.linuxprinting.org/execution.cgi?driver=ljet4&printer=75104&.submit=Show+execution+details)>>
->> endobj
-2829 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [122.225 346.095 365.259 358.087]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.linuxprinting.org/cups-doc.html)>>
->> endobj
-2830 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [122.225 318.996 496.486 330.989]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.linuxprinting.org/kpfeifle/LinuxKongress2002/Tutorial/)>>
->> endobj
-2825 0 obj <<
-/D [2823 0 R /XYZ 85.039 781.388 null]
->> endobj
-2822 0 obj <<
-/Font << /F62 1689 0 R /F15 1628 0 R /F35 1632 0 R /F70 2201 0 R /F18 2207 0 R >>
-/XObject << /Im1 2193 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2833 0 obj <<
-/Length 3056
-/Filter /FlateDecode
->>
-stream
-xZoH~_a^-E&i6{M>(b%Wo?~$JpEq(pf8Y}r'plxFl5yz}}4z8=2'w}S'O> ga86Nn u=q3k\3_-H,{L{2<5}Uhv"c^OVunftS.w|cU.^_;W.Ngo
-!8wg89{|&n'.}hC o>,/> Fx;O4R~x/t0jx[meHi^& 6jD)woNWMKP1LkB]bC,#-=}OWg;iN!jk*'&F!}M&,i ;I^#A L7ku*bw7UTI!V:!3DuzrF`WD$?%Z`|U/pdnqvqcDPh2G28[, F^GoG_h$
-iZLol[E~$@{uPRat
-MVQ:+(!
-Z
-&%* fBWIB-I$ )Uvy^DDmC.VM6H[Y'vA)i!=Satm)|
- = 'Q&4ZT_* E^es~(=INC ]O9qe5*V'@-'5Zdx< B&BV"%GT`xk5Fj0e |`fe\'~9L/d<w
->K:.8(| O3"I2RnfS*V@W+qJ1
-eg2QXv=AGeN<Q"DYkbwsVg6fu7 ~q"b&NtFLDy$Mqyqyh]NA&4m]TBiO pbl`u"<*qKQIqDkLCn[_MbmtCc!QE71rT<Kvg_)|,\(fZ
-C<+hq'*yjvJ[ ZUo P@fkTWs6NRïZDY6^zd` nE d>e74b/*v
-endobj
-2832 0 obj <<
-/Type /Page
-/Contents 2833 0 R
-/Resources 2831 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2812 0 R
-/Annots [ 2835 0 R 2836 0 R ]
->> endobj
-2835 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [351.165 473.426 512.306 485.419]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.cups.org/software.html)>>
->> endobj
-2836 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [111.316 459.574 136.217 472.476]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.cups.org/software.html)>>
->> endobj
-2834 0 obj <<
-/D [2832 0 R /XYZ 85.039 781.388 null]
->> endobj
-682 0 obj <<
-/D [2832 0 R /XYZ 85.039 171.068 null]
->> endobj
-2837 0 obj <<
-/D [2832 0 R /XYZ 85.039 142.27 null]
->> endobj
-2831 0 obj <<
-/Font << /F62 1689 0 R /F35 1632 0 R /F70 2201 0 R /F18 2207 0 R /F15 1628 0 R /F65 2099 0 R /F20 1617 0 R >>
-/XObject << /Im1 2193 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2840 0 obj <<
-/Length 2772
-/Filter /FlateDecode
->>
-stream
-xYBK)H.? !J'#-<1%$"{kr
-7,lG%(vm0@U\Nd!'_^|X*,(uw_{>]5x^~sr=Xv~pOW?2Pc$nvW~Wnf0-}7i;}M7z[9{/9`GU<ake<~ zM ;U~BK;^%e~2v/E)?(
-GZ%UgKEs%W[lr_pot0mOGR8iZRC?U!v ,dK}$7e= ?vAU+L*v3ibK/mC\L#8St)x({d_ys7G
-*,P5
-,92{&;d)p>8s vjosQf-7ZNSGgzD^ pXSA¦ÓÍ¡ñùG\&'~}2r<9N0(,~7C&vWQhJ4qY@(4 L69hwqZKq P?FA>G/x] OH|J'9?z' E+2?,pi;`k= H"9x 8nq?{ojIiì˜Ü¡Ì{&‰Da
-me2m3&;0MD4jkY$7AVz7cBh\ )&
-|b:ubuz@1XE0t%\:~5a[ HGSKi(OgP`tT h6|[9$XpM9 _MS P' 2!GqcIGt#d!{hLTrT<_ u c\x5N C9w ^#zHB 9ObJ>I*$e9 9l<t,\LL{=g01pE=ayn SjB $dN'`HI)yrti& 8w&:CD[`H- ._UL0hK1oM#®T\8f(8uZQ$O:;<YN]gJ)V}rTFvE#H>atm ]k4u&%r< `?uGglQ8&#5.a^jl_%B8@
-0Hu&N|**RdR_`#9qYID<W|R1®#·- ô`by¦<FN :5te:nL~!S0c|r&O[8do%(A|;cXfFs^'pe"b=qM3O3&h%
-Û§¦ìDX:Gúýœ@r;ITckjzG Jaq"o q veSQ)*jd92f.(RK |v%uJFF6B8Ml0/
->bg#9>u<sHE1 }1o &
-B(nwbJ& @GGtg6* (584nHNM$SG@vW;/q/y=v(
-T7N l
-oLo=C^'-
-endobj
-2839 0 obj <<
-/Type /Page
-/Contents 2840 0 R
-/Resources 2838 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2812 0 R
->> endobj
-2841 0 obj <<
-/D [2839 0 R /XYZ 85.039 781.388 null]
->> endobj
-2838 0 obj <<
-/Font << /F62 1689 0 R /F15 1628 0 R /F35 1632 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2844 0 obj <<
-/Length 2785
-/Filter /FlateDecode
->>
-stream
-xZ[F~_rX U!,n4cKFq=elC-Q#(\%(LL 
-\z<;;)4#D%Hfo'??z1dy}w2yD;xOqv^__NbM8;]?go5L^WN<7=^uvS)7c4F{d-p %HY=36]Jm&&v&S?
-aj"`IXp^;?`v^nUyq^pQF˜¨ÚõßU-L5yY-hhC }w<BqM8‚ØiE-A_qz=tg#9v\1\23+M)&jjcY@6iF;,K& T4N0;l~{gUz}eNGONzIQ&L87}c9/KSZnM8/, pX ~\&pcK_?*7kzQ ~77!P{A;Nr|*3x{n;A/>k?tC15RCQO_f+qlSxg/vC&
-*/ (4a%p86
-L'<'Ow#%Dy BHpvf4qf^ãï(¤§xÆ Âb–c×u‰¯#Áý7Ä„(à0€%qƒ=AU4N,
-hsbwhZîïW#nvdqYv# J'c2#J=lZ y>3p-MbrGwhe$Vw}yirD)`-qJ&P,%{M_;9
-Yc~#DIs&%H)reV6-5 )uQ|/ZOgZH8zmqUmU-X"NHi1r45Yi+1'd=~?;>LA6V en` B 1STs,J=8d0$Zv{Gc}=*9r|Tp;
-!K ÐP} T}[sq9iyT|;1&$E 83 X]Y|#,DgGYrVn7}OO$l0hq+H`2
-endobj
-2843 0 obj <<
-/Type /Page
-/Contents 2844 0 R
-/Resources 2842 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2812 0 R
-/Annots [ 2846 0 R ]
->> endobj
-2846 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [318.285 100.991 509.276 112.984]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.cups.org/software.html)>>
->> endobj
-2845 0 obj <<
-/D [2843 0 R /XYZ 85.039 781.388 null]
->> endobj
-2842 0 obj <<
-/Font << /F62 1689 0 R /F15 1628 0 R /F35 1632 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2850 0 obj <<
-/Length 2574
-/Filter /FlateDecode
->>
-stream
-xYmo8_aT.(vkkz [J,T\ )]  "pH<3, YHd]x;hyw!Mo/
-6gVeq^R)@,q8^H>>Z
-MgK^KHk4[9_vA 9Z34A[)Xv++J-~iK\Yc<l jrsM5,E@[+BDE0kim;ZwtEeVy!`9F#@J^>L)=s;Tf n`5&rvZ^xp" q{z y[vWB D/|*Nq@4'S!(y"+_MD}+qhq]l)^KEP}Ra*4-:@)=4=\
-H[4(DC%BLB4|~_]>~
- ~h @ cK4eRJ> ãHbbX##5:Pä@rho(tmz;. C}\65
-SoA)Kc[4
-cj7G-^n33k Ix=M.13HUR{
-6 94@! H(3@Ozh;D`6GSq$]
->=^y
-ckhAQ\RP2R*+67A>;flKKn-p$cM; BP B9#`‚Ä×b!€ 7ña˜ö›o¾%­î‘[vÖGjApBW|teG'%CjoAs;t Nnp|Y0yZ'}o0fO%t|ya#7qn?$rN[B w/N$Nz÷„ã$îqF4(T[{lsPp /|: $b,,6wz;7_uvquA_T>Qy_sYaE
- |K"{-! B;>!Am8L^;'IEpbl*i`Rt)[jz?~FP:@ VH"d^D
-i_;h+["ovE^ 8[S849f pG3=(Q$qu4'-IgvA9'j+f:^&sp57eYJZ<yc/e K2D\!n |nH' ):vM4OG^T}9ro j0MPd3|u y3ÛWg?^~KW |(PMnt@$~,[XTOnhvy?X-~2<@ bendstream
-endobj
-2849 0 obj <<
-/Type /Page
-/Contents 2850 0 R
-/Resources 2848 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2852 0 R
->> endobj
-2847 0 obj <<
-/Type /XObject
-/Subtype /Form
-/FormType 1
-/PTEX.FileName (./xslt/figures/caution.pdf)
-/PTEX.PageNumber 1
-/Matrix [1 0 0 1 0 0]
-/BBox [0 0 31 31]
-/Resources <<
-/ProcSet [ /PDF ]
->>
-/Length 557
-/Filter [/FlateDecode]
->>
-stream
-xmIn1 EOPwu$Ig06V5 osO #h8:5?[IL~F PYdzZ8f(E#@xoL [
-
-6\>RgbW¹j[†›
-W{6;F])/Mu;pk;dh<EAwNtD](;rL Ttw_ =]=uS"yl-kHsreOvg<7t,e;/IB&(Y,kR'^ m" ^hW9AVy/f"Fy-Sng \d}B$w1.&COVX9gE{< P)!ZL~'UXLcXs~BLONZ_[.*]3Q!-endstream
-endobj
-2851 0 obj <<
-/D [2849 0 R /XYZ 85.039 781.388 null]
->> endobj
-2848 0 obj <<
-/Font << /F62 1689 0 R /F35 1632 0 R /F15 1628 0 R /F70 2201 0 R /F18 2207 0 R >>
-/XObject << /Im4 2847 0 R /Im1 2193 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2855 0 obj <<
-/Length 2865
-/Filter /FlateDecode
->>
-stream
-xZm6' 8oPDm7hnA
-AkXm6ax8Cr*r$O~2bq<Zl.h=_H-!Fa]Bo$d4_<uWcI7gr|cKS?e]\{NB|obj.'
-k\=u0,
-uÎĉœwT\h2F1TO=VMx*r</?-'w(&?`BZ`tO_,^0)7AI F2(29QiLE$VLiSpj *zv]hN] 7]if,0
-h2vC5W%5405UZE^{HMl-w67"e|8-7
-@=H\B;'\ETQBe
-endobj
-2854 0 obj <<
-/Type /Page
-/Contents 2855 0 R
-/Resources 2853 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2852 0 R
->> endobj
-2856 0 obj <<
-/D [2854 0 R /XYZ 85.039 781.388 null]
->> endobj
-2853 0 obj <<
-/Font << /F62 1689 0 R /F70 2201 0 R /F18 2207 0 R /F38 2158 0 R /F15 1628 0 R >>
-/XObject << /Im1 2193 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2859 0 obj <<
-/Length 3166
-/Filter /FlateDecode
->>
-stream
-xr8PD"Sd3$oTjf4IKL(R!(~$%9l\6F4 3~YEkq<Kl #o.\pfv
-0u9# wqmwQy7I7{Ut:eU6JhvEcURu(;f;
-<Vv'mzb#a*P8#CYn#,AljZ2|y&gM=tMx%>i,JDC.[dxIDW
-S<LyD
->rbL.w50mjVu$W[+*`@nbns[vmW9X{ (NijZ7M2I[*)!o:(GZF{]CS~^F0`oX$iF5¢Ô]Ò[ò
-ú¾åø'fÃñì8Œ áف>±Kt+^L NoLRZ`C E)
-u}w} *Ro~3l":
-{Gf`
-%j:a\kMB:e d(e"ŽV8FZi!}A2n=NS|| 6e - f0035Pty
-|[ p"sdqJAB"_>q0I=GGr=Lve&8`&_;v'$1%HcYlwMk:^4U<
-T}2kcy7v;Eaf!6@
- /
-x@IqNrk|V@
-mr1VR"<{Q1GFq)HI*8mH(_55q+W@'Rb3/P{j%Rld&(mbZ PpZsTzLVUWDg 1$ ;%z gGpA:7l|GcgF9c9V*~tma^)LJcTx)hgJ:L<wl-w1Q
-`*yVh)-}ýКÓËò«9÷È-PQTD)@y${_OY(x
-endobj
-2858 0 obj <<
-/Type /Page
-/Contents 2859 0 R
-/Resources 2857 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2852 0 R
->> endobj
-2860 0 obj <<
-/D [2858 0 R /XYZ 85.039 781.388 null]
->> endobj
-686 0 obj <<
-/D [2858 0 R /XYZ 85.039 388.423 null]
->> endobj
-2861 0 obj <<
-/D [2858 0 R /XYZ 85.039 359.625 null]
->> endobj
-2857 0 obj <<
-/Font << /F62 1689 0 R /F15 1628 0 R /F20 1617 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2864 0 obj <<
-/Length 3193
-/Filter /FlateDecode
->>
-stream
-xZY~_!(Bzw;NG!MJfKX]]V3,lKfQl/g=gJV83v
-&enl5[8^to~9\_9dm2qmc]b3;-=!Zk$w
-;[tiunxTx^ [
-Z>V= GbGQRld)7 GJpcGw)|c
-] Z%(XSkAd-/BF(k3='Or9Vir1nWXzgm/cJ+V f5îúëU[.<+]y #LOsdy*0\[{ &B$ND>
-q;nkh8ta1R{H8+EiyjC|+q7Qn7SRuMuT`0F @`B6R\`YY0I)B+,]m.Hu-
-f<pHBuGk\;Jb0 wFh}eI/p Y>-M@@<]9eOfG'Li2#` =Ao3;dqms 4Gs_0> ;q&G'V&E?%""]w< h]R>h AK[hh€BDcqL>q(FyT8%;0Uw6@CJ>Q#0r.IJ^<u[@{/-P>n]BC qm*zEAI=G@2jsB(!R&(%`9Vl=I'.a_9H'B :p@(fi8S11BO$V;P餼„ÃtƋø–[u9Ԃ=9ymÏÜKp_OKUT]>ßW'w, KvkJ4øöÏAJA7riO7m.9'%001>p<Y=dBx zU6l*t9[JS~bp?&oRBKI,}qWqK[n¢côLT $jCM (fjE[;Y(hcsd]r\JGb"#0xN!;G @u*#t=$2EN_i"o E x<N'[`ByhP19/ `g3Q N;|*_%LLhY3NZ" tpDL0GI'bl^^^S -j:
-{)|_pH:%dSO&w >
-x0190:1LxP22{@\"ij<q?Rz|Tžà ÍŒÎã‹wQ=}
-i5B%XDhuQm{at~ 9b^y"Å9ˆ†ÝïQH R A
-7hu9*?@=d
-!<;O#E6rCF%3KU L{ endstream
-endobj
-2863 0 obj <<
-/Type /Page
-/Contents 2864 0 R
-/Resources 2862 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2852 0 R
->> endobj
-2865 0 obj <<
-/D [2863 0 R /XYZ 85.039 781.388 null]
->> endobj
-690 0 obj <<
-/D [2863 0 R /XYZ 85.039 469.263 null]
->> endobj
-2866 0 obj <<
-/D [2863 0 R /XYZ 85.039 437.737 null]
->> endobj
-2862 0 obj <<
-/Font << /F62 1689 0 R /F15 1628 0 R /F70 2201 0 R /F18 2207 0 R /F20 1617 0 R /F56 1642 0 R /F35 1632 0 R >>
-/XObject << /Im2 2261 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2869 0 obj <<
-/Length 1879
-/Filter /FlateDecode
->>
-stream
-xXm6 _adæ
-lÎdyŽÇþpL9YU#g2ofnl]RJ_™…¶rü´,‰Xm<E8 l,7M
-X
-[>f_lA{p>v*;V1u2uTr|nUj*2vU,@\heTX'cLiQpMc-T:x/pTYcMj&dy7|)%,a9"7
-\lFc|p:Ùnä‘Ç…}`}ëCSo^nEU^ L?dJ
-vXY<tW$PH=f4
-Wy3\DHvxIb<w0^!V[\uVc~u(zQrRrHz}914r"Qv]EEO?I<Y&o{E;visUn*>U7G
-<.ga@TX"VfytwrLui| :pY.WhQ6q1bwJ;I0g# !B0La:ibG[yE%aa]mx-_kHSbr
-mk1:5g!p^sn UTYt\B#iS^A'E?aqgC693lJv@U|Bgnd!pE`/Tm25i\,KpzTg-Y0 .m(v~3J /G
-\@GR|2tr LPMr992ZwPBXEM1Zp,W'^x~h%jn*Z.g]E|;zFX>8n}grGr3?#~<9(cgq6zE}!PmOg9z|>Ag1rVjS7
-O i1L(\Z)?MJCxq!EDC*\}fE Q;'# jb?eu1|Yg9EOO#TAMP=-S7pun J5rr;
-endobj
-2868 0 obj <<
-/Type /Page
-/Contents 2869 0 R
-/Resources 2867 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2852 0 R
->> endobj
-2870 0 obj <<
-/D [2868 0 R /XYZ 85.039 781.388 null]
->> endobj
-2867 0 obj <<
-/Font << /F62 1689 0 R /F15 1628 0 R /F35 1632 0 R /F56 1642 0 R /F70 2201 0 R /F18 2207 0 R >>
-/XObject << /Im1 2193 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2873 0 obj <<
-/Length 2539
-/Filter /FlateDecode
->>
-stream
-x>_F4Y57' 2 2m;$b($5mU,IT$@WUo>>d!B_gC 7@D(nQR_a"?oQ*D?< cizfz ~ ¨®6[¤Þ?†ÃÐO8N|B7y{zjjeC?<nwxQIg'x*De7}\e~5-k
-&FYThJUCx
-$f_x{I>_=-,fMbXFpV-Hh _Zo
-DETE
-L<$m3zb3{xi=z "M92c.qCZ/V@,rsg7MVu+{ 6Ö'{Áä\CJE5|m0R=,H7x=|] /Jbcc?pxhjI(7lWL*0}1f85 j):0~Lht,d+G K=I|q49/a$xx SE
-ix(JE9cwo(C(9a0iq/i`cM>wK8*
-W9Lz}oG~n)Gd >9 jAI|_h`9I~/R~yl[
-4^^vJWX~BRal4n2'+Ä·BV~D\T)33%'zY|#d_vaeL/3ÎmÅ7OlTwC!dPG*Pf#T Hhs
-5X_']
-dÃ*Ícv—8º¹1^r#ï*B!jdT"^9h _dySXqX21-}`lQ3e7%J>yh1(&_(xJo1B&y9<H8Mybx.$K qt(lmH2?l5ziOleRVKi_(b_2 Z ZZmk%83_%YYy`iuE<{&T^0]hlEQ
-endobj
-2872 0 obj <<
-/Type /Page
-/Contents 2873 0 R
-/Resources 2871 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2852 0 R
->> endobj
-2874 0 obj <<
-/D [2872 0 R /XYZ 85.039 781.388 null]
->> endobj
-694 0 obj <<
-/D [2872 0 R /XYZ 85.039 761.463 null]
->> endobj
-2226 0 obj <<
-/D [2872 0 R /XYZ 85.039 642.137 null]
->> endobj
-698 0 obj <<
-/D [2872 0 R /XYZ 85.039 642.137 null]
->> endobj
-2875 0 obj <<
-/D [2872 0 R /XYZ 85.039 617.419 null]
->> endobj
-702 0 obj <<
-/D [2872 0 R /XYZ 85.039 490.465 null]
->> endobj
-2876 0 obj <<
-/D [2872 0 R /XYZ 85.039 463.851 null]
->> endobj
-706 0 obj <<
-/D [2872 0 R /XYZ 85.039 132.463 null]
->> endobj
-2877 0 obj <<
-/D [2872 0 R /XYZ 85.039 105.849 null]
->> endobj
-2871 0 obj <<
-/Font << /F20 1617 0 R /F15 1628 0 R /F65 2099 0 R /F41 2104 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2880 0 obj <<
-/Length 3544
-/Filter /FlateDecode
->>
-stream
-xZYsF~P eIZ^K)*HABA+_u K-9zax:O .gyy~X_K*T
-Y?fuEP\?>1cww&80',~w{+)y](>+|ou4J |_h04oh&\{b~F8_W\t_?.*~X$li/Qg5MfT?+:G5&YM+7R[|co>F3!N4tzBt)V:lk<HjkYJj0 ly/`~E[> 4{j};n87vb'QFgzcHU¬=›y]Å#°§¦—&Þ'Ñô+£-/«jS}jxTy7v#nD17Yb+~qW|)}fIR:~sZ|m9E>Kp!4 e1{*swio5(FxXZ 7qO_feåE+W8cc'*
- 8clVG2j<9
-0~<W!4 1#yz30*y Y[3OH (_L2!bJ&h Zi#Hx@!aY&wDEJV1A %4JDnO- 5:JV|hBdtXXlhM%9;77@R;ne)v>lDX%,.@$h 65$ P0QaM5\8? e ,qb I_*04{Y\|hQxV(Ym[:F#;2Nw~X~x<v[oX<O)3RkZTX<Acy|A`@|M?Zid[#8d( &l0VvlpDBSp*bB9K5;k(u`dU!|Q1J 0/pwc|0 0SIh?m xi"''#* W[(MyQ (;G7ETUNE3NCAi
-E}pS*]oYkdq:B!FX*N('#7d <#qe5ts
-TOPQ<:6[1¡ç`³Ù蝩ÈþiHiG0vFCeMR3znyK+X +%G[BBv7q*ngGqwj.UdXP\RHz3H.m 9!'v,LyG9f( "sKfnJef>2<- KP} 1}SQ=Voe*pb
-P LsT]mXgU+J2'9Ef='I vO Y3ecUAst*QIN\@q
- ~fpG 1 , 7pW6F;qu0-RH!YUYFMRuxZ!oZmP6j8O.0
-0E4<c!|q 9k2*e\4\d =]&J| ,3,n8Vh )!%]R 4ql"RdS<n~}]5f3…Ut,Y;
-endobj
-2879 0 obj <<
-/Type /Page
-/Contents 2880 0 R
-/Resources 2878 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2885 0 R
->> endobj
-2881 0 obj <<
-/D [2879 0 R /XYZ 85.039 781.388 null]
->> endobj
-710 0 obj <<
-/D [2879 0 R /XYZ 85.039 461.534 null]
->> endobj
-2882 0 obj <<
-/D [2879 0 R /XYZ 85.039 440.943 null]
->> endobj
-714 0 obj <<
-/D [2879 0 R /XYZ 85.039 302.771 null]
->> endobj
-2883 0 obj <<
-/D [2879 0 R /XYZ 85.039 276.156 null]
->> endobj
-718 0 obj <<
-/D [2879 0 R /XYZ 85.039 204.579 null]
->> endobj
-2884 0 obj <<
-/D [2879 0 R /XYZ 85.039 185.707 null]
->> endobj
-2878 0 obj <<
-/Font << /F62 1689 0 R /F15 1628 0 R /F41 2104 0 R /F20 1617 0 R /F56 1642 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2888 0 obj <<
-/Length 3665
-/Filter /FlateDecode
->>
-stream
-xkoF/r7Izk\"z)%*$o^$%- e
-_.~-,|gGhE#4- EkZ(L0,¨¦âªÜ£-—W "RPO8[@|v0X4Hcci{;Y^ G qxp{:8FXR2gtA:
-6 <"w,_LcCkQ~mlB,r5,/1;Xj
- g3e]NF"-BtE`
-.(c8zH/+GJXs/a~/<(@k@;x<fZPZRG}WU JZ@{2
-/sr5;/_3wT>[{8Oz<yo:d#pF9 }"0hqp%%RTl+# 5yt[M65W6[®Ü3j¢ –·Ž÷m—Ö“X$IU\S' ]oj3&E/ k~vOR'{5d1'^d# p/*&vDWC]c*& k@ZhRal I k^+{aG-!:!#=9, i`i@h ? B0k3<>}L! K^HB FQ3
-W7F9-e?egu
- F:8MLyRZ#TX(kl97va#r~F|q.dUW!#Drg*Q6YccoBp|@Ss^_@}G.b}C}d |d%P.(q%$YioUWZ@)DQ@!Zho0KYSwa?L5G,ex <[/u _= A`E6W*4sAB
-@0=JG  J#.7~;IiB:({6]`$3^7{tG W%ObASlC]y$ |t%
-0NLlBkJqs[ 3qU\8F3RElGA57$$J;eQEk(g-y8 G'{Y uB"5Pjg['%g's!h|, }3p>+RBl-) Xu~A On]V2_*ZS,ZafUkO4giZqENf-2r;z. PfQ@CAP8PEOph5R*!)sZ HJc?wJoX1`_\?2+{*8l@ DE"J}APZ HJ&NvDaA_%yw:OIWM.m]j;hSSl
-Ts4_L(GG:E :Jlr| 'yB+-ìžd»nr¶ló4×üAp1{p@2d
-%$(UwDB?C@:ES 2MygQ<$xRnI\E.
- $a`}!IM|Ww)C5Pxr\&K02JSwyP~6cTQ<Vms(mh1`dGyf] D y^:&R*Zo:{C=9._=I kxuR%EFaqIwM+
->d #VkX.';fL1lm6 _TWVIuU`O5 a[u "G9;>
-
-R3??S_M"-
-3$46w<endstream
-endobj
-2887 0 obj <<
-/Type /Page
-/Contents 2888 0 R
-/Resources 2886 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2885 0 R
->> endobj
-2889 0 obj <<
-/D [2887 0 R /XYZ 85.039 781.388 null]
->> endobj
-722 0 obj <<
-/D [2887 0 R /XYZ 85.039 719.568 null]
->> endobj
-2890 0 obj <<
-/D [2887 0 R /XYZ 85.039 698.372 null]
->> endobj
-726 0 obj <<
-/D [2887 0 R /XYZ 85.039 615.564 null]
->> endobj
-2891 0 obj <<
-/D [2887 0 R /XYZ 85.039 596.692 null]
->> endobj
-730 0 obj <<
-/D [2887 0 R /XYZ 85.039 172.83 null]
->> endobj
-2892 0 obj <<
-/D [2887 0 R /XYZ 85.039 151.634 null]
->> endobj
-2886 0 obj <<
-/Font << /F62 1689 0 R /F15 1628 0 R /F20 1617 0 R /F35 1632 0 R /F56 1642 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2895 0 obj <<
-/Length 3513
-/Filter /FlateDecode
->>
-stream
-xZYoF~R@D3/-3"8[W7I 00nY]]W=Tz'z]]yèyåËøÝÈ×Ø÷juuó.
-®}ÏMzDcVo?~Z,Re'w.| w\v]oE82~5&_X uJ2`%zb'x\yJg{q5%WpY3Zj8-&5?CY/ywR9tb;~NoY_65:-=e}u v6<"oP>s):i=< #4j>v =wF%n&"tGAFVRff;Xlkq.lCTxG` R@%N@EqTbRAXB8Ww6YYwdgb|NCMSeH:_7Of+$*_3Y/u tW<hAK&(,Z_q@1sc,]=vVg_x*5/[Cp#*n\lLyf"3*eTnNUAzni=/\, +G)7 W~$p;6aGgScMU"v7r;±~âTF>5-(U!Phi2ee\c`F*"jt`pqyfo/1m5W8\{DCu/m0le E0Y-¡í5(§å#Ùèö…Gp2h7 dDimx9E*r 2!F'9,Gk2a8!p,8,Q>P>ӘÍÝ1z[sD6aL}$xP-KgyNc<!fgiChYw?y`X]!eð”Ÿàœz´7±?RJ 1cq5f'h"<N9<^ @M
-&9:AH]~6TV,2{.k`gW1}X1xRNn9737]>e2g2HhlFQHpIvs- G i e9g + kqq#iX.GksaVe|0s}m kTU]&)r PsFAGLub%/>MQv iwDX3h{ #8z8>/R@0ipnLrcr+tleH-4D4ny!evz?|=hm=@
-Owo]nabJ3UnG"Dp_$ L`Z%-n3Y>15
-$tm@{Xu a;:^BK:Bz#++Tp<0f*j+bx7j=q=TII( ^J9EY+cci Z
-`PE0 ˜ýT =zVd*?JoG x0d1`Q6]kzGS%c2]l9#pD9+ ZOnLJ`&Ol-aQnS!>
-!%-
-fAM,G{1G4P
-=f'QCBK3.>bz\g/øT},n2K0z2_Tb=
- \Dexp/Io{uUz3V(0RWA1/12h?!Xx-7~%rxS6qp oA1<~l
-!=
-7g<cM80CL/P]+`js %Q$F"2og>F'vJ2)Q+
-O#.x» øµù²ÀÿØ/ï`?±ÊsQ@EObendstream
-endobj
-2894 0 obj <<
-/Type /Page
-/Contents 2895 0 R
-/Resources 2893 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2885 0 R
-/Annots [ 2900 0 R ]
->> endobj
-2900 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [250.936 169.022 367.444 180.712]
-/Subtype/Link/A<</Type/Action/S/URI/URI(mailto:jtrostel@snapserver.com)>>
->> endobj
-2896 0 obj <<
-/D [2894 0 R /XYZ 85.039 781.388 null]
->> endobj
-734 0 obj <<
-/D [2894 0 R /XYZ 85.039 572.649 null]
->> endobj
-2897 0 obj <<
-/D [2894 0 R /XYZ 85.039 549.331 null]
->> endobj
-738 0 obj <<
-/D [2894 0 R /XYZ 85.039 371.679 null]
->> endobj
-2898 0 obj <<
-/D [2894 0 R /XYZ 85.039 350.482 null]
->> endobj
-742 0 obj <<
-/D [2894 0 R /XYZ 85.039 212.304 null]
->> endobj
-2899 0 obj <<
-/D [2894 0 R /XYZ 85.039 182.899 null]
->> endobj
-746 0 obj <<
-/D [2894 0 R /XYZ 85.039 102.678 null]
->> endobj
-2901 0 obj <<
-/D [2894 0 R /XYZ 85.039 81.685 null]
->> endobj
-2893 0 obj <<
-/Font << /F62 1689 0 R /F15 1628 0 R /F35 1632 0 R /F20 1617 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2904 0 obj <<
-/Length 3660
-/Filter /FlateDecode
->>
-stream
-xZYoF~> 8n\83
-f>"-HII / >(u2dI|EpOJ(UsVo~
-,.WD*~vbiT/Iz\_pq<O7_N}7 zz^jol/_aW?QA;3W[,UJ5~eW"M^>B;U]._/\xf u&tfn¼ñеõb‚Àîێߪ®X8XK0Kdq(a!ae\(Q8dÞ7 ªý3ÏÞ~xr€W]992{5#]eM_5zo<:uS2CtAy}6u-dx_~~"LY_-B}p ~d[pwb{ p/^w;yt+{,~%DIohnwFi(-{^4;yW=FtCOJ= +~;=mnHmc"-d~+tza=Tm\]>n0>- <kHI'\'4=?8O5g*M Yyfn0Lq*<-^3J~j4(x%!_h4GNFGj52q]Y?q M39.P j ^ey|v4qaz=(98d vpH[!0@:Wc c;z+mBX-Om);n7P!;Y 2aBsx)sr*yO7< 0ttr Ae}}H"v6 ElF_Zv r/YPil.88oARJZFsOPbPAD `vZy$";$C:&uX B)aUj<>pL'W<LÖk"FG#_Y::"\}dr0"Q=ym åxÈã=à'Ÿ<š{Ír$;?ŠyÓû¼*`—0PS8"u/m$4w@c
-A)m)inshf,9}Rq:%6ZP](GK?wOQbpO/'L)?s(G9 d5YJQx_xl`g}Ojs&bp0gB]*:7 `jbkANUI#<F~r'%y 5hB+0~n6wToP<:?M2/,13GWC%'h w m-eq:YAnhRYo/fh,1T1„xâíÖ8Ü6{ø¡ŸV}MI55S[Y]$h{(sg|Ks|~G7AvV5TOT3^8
-YVr$7CX TJI,Hc@4Q7m»jCWkI\h|bJUf+cN $2/K)qLB:!PBKiY&\!/0NYYji)"+8<kJIy'|73!gbK
-0z_s!sN2vN1p9M6x M&`g| Sq
-Ao_OZgm@w`O`RA)"o]Qp`T$ZZV
-wMB=%?,1wŒGlZiP EL$lt Ik4{aGs&[u"5FiR]I+!mbp
--aUuBW1&zfq8>x
-9-~y4)I K[<Gg -v<fF&62MqhL08 )GuRN'P@{:=Q)3+ GO01M} )%s4.DH&<u82]> XW0"bTp'3M!JpIx[F4y=$
-H9q&^.VPxȁcêÊ×|£ªY :J, [jI8g8Hc¿÷‘×UC g( $*wSj9 lTfUM8D. MgDBX>7Bj7a|L(2RL@ s$xiJ1/[y$)*ò"øæ‡â—5ç×øãlÑIz$eW T/JE0&ya`Q-^.Mm&_IO5c.Z!xv^YlpoZYkti03H,>EG V0 f439*&g1<.9X* 8_T@1`Mb4=
-endobj
-2903 0 obj <<
-/Type /Page
-/Contents 2904 0 R
-/Resources 2902 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2885 0 R
-/Annots [ 2910 0 R ]
->> endobj
-2910 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [348.805 356.06 464.335 367.749]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://samba.org/)>>
->> endobj
-2905 0 obj <<
-/D [2903 0 R /XYZ 85.039 781.388 null]
->> endobj
-750 0 obj <<
-/D [2903 0 R /XYZ 85.039 499.992 null]
->> endobj
-2906 0 obj <<
-/D [2903 0 R /XYZ 85.039 478.795 null]
->> endobj
-754 0 obj <<
-/D [2903 0 R /XYZ 85.039 235.518 null]
->> endobj
-2911 0 obj <<
-/D [2903 0 R /XYZ 85.039 212.201 null]
->> endobj
-2902 0 obj <<
-/Font << /F62 1689 0 R /F15 1628 0 R /F41 2104 0 R /F65 2099 0 R /F20 1617 0 R /F68 2909 0 R /F35 1632 0 R /F56 1642 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2914 0 obj <<
-/Length 2607
-/Filter /FlateDecode
->>
-stream
-xnF_!`"3khv">P"%D/Iu6iQjrf3VII&Q\aqC's/._?]{:38*p(_n?\_M'~-]}î¾¾yÿiªcç³
- œPBF7ZV:{8m])O-.}P.k]U?@uZV=mzskY 3g]K`au<ziD]e FEYHZ^@D`&|[!v
-hq{4;6F4voyY-r[`1rCA|G9nM W Q U (mdV7v@#!8o$?{ yH[69 nq-?J>+-Ù[”"ãñvT !w9:M!@:Z}@h%­‡“ñt‹ }ıaQX
- qy))}) eYs;3#1d+r#C:oe$) r;eBAZT{Åq?8zÚhmNtgóJtG9E_qP^c4&3VUp$\N OxWBPC5_Rnv]2j=|s(0\#E;A>yweaŽë4rLj\aa{C;N%)3@"xH
-=E1 D*l>+ih*>jc) 3rM"$FL
-@@ [JY7W\4*%S e'tj!OO<qLOToEx$HyY(SXR(h/'v4. !lm{'yxdcMwj+)$*:8",_GO FGO.*tp:
-endobj
-2913 0 obj <<
-/Type /Page
-/Contents 2914 0 R
-/Resources 2912 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2885 0 R
->> endobj
-2915 0 obj <<
-/D [2913 0 R /XYZ 85.039 781.388 null]
->> endobj
-758 0 obj <<
-/D [2913 0 R /XYZ 85.039 761.463 null]
->> endobj
-2916 0 obj <<
-/D [2913 0 R /XYZ 85.039 741.337 null]
->> endobj
-762 0 obj <<
-/D [2913 0 R /XYZ 85.039 514.594 null]
->> endobj
-2917 0 obj <<
-/D [2913 0 R /XYZ 85.039 491.879 null]
->> endobj
-766 0 obj <<
-/D [2913 0 R /XYZ 85.039 154.621 null]
->> endobj
-2918 0 obj <<
-/D [2913 0 R /XYZ 85.039 136.147 null]
->> endobj
-2912 0 obj <<
-/Font << /F62 1689 0 R /F20 1617 0 R /F15 1628 0 R /F35 1632 0 R /F56 1642 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2921 0 obj <<
-/Length 2442
-/Filter /FlateDecode
->>
-stream
-xYsBuID|N/[@;>TNhQvd.bwR=F-3OgJ8HwcG)C 7]4]c|?w`Y?<u_iW< 8t}7Ww}
-[ !ekxs8
- ;O #g+ e=hB0[m{4K_{<[tusxr:&';lG2f]"Htg)ae4q˜\;áéùºŠó¬lM6*r?CMuH<UHY
-5V0a)W
-E&rzKPlVi``Or6&{f,<5=2jO{
-`VD6Dl8C)y~d1<CBrSbKHr
-` ;FvL[lJ|-.×òÊ0ñL_rKlgKF*CxV; gc(K@fmr;/zla"_v'1)2$i
-`XEF{E *J2Q{BI'9j2hwgO>o [Q+g&r TbM/>2|mv;lNE6G;9xx0*G$x3dJ%|cD0=ejL9t0C51D\ho 
-=pj]GCDt dXa1t4oi#f6tp6"!"!Z rqR#SWzQOGMu!3U1 ,p\P'9:~#0+02bg ""/0*hRI'X .÷À4kä薡ÄÀmƒºÿ0ÊgÎÒšص÷•‡cXFq:Z2 wgm_whC[ ,D"H <86
-Z!%qm0'Yw$dz$Gcw([muP2 ¬b+ÌÓ
-ãöbçTOW^r}-ru4lTz?X8R|&Jq $[6ST{~$R%>!")l3 _)|+xqŸóƒÏW^8J RzS4B9!L W\K;P",L
-
-2r1<;<O>/x8RDv[|W'Cv3:OSK~Lø‚
-endobj
-2920 0 obj <<
-/Type /Page
-/Contents 2921 0 R
-/Resources 2919 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2885 0 R
->> endobj
-2922 0 obj <<
-/D [2920 0 R /XYZ 85.039 781.388 null]
->> endobj
-770 0 obj <<
-/D [2920 0 R /XYZ 85.039 544.417 null]
->> endobj
-2923 0 obj <<
-/D [2920 0 R /XYZ 85.039 524.428 null]
->> endobj
-774 0 obj <<
-/D [2920 0 R /XYZ 85.039 228.345 null]
->> endobj
-2924 0 obj <<
-/D [2920 0 R /XYZ 85.039 207.751 null]
->> endobj
-778 0 obj <<
-/D [2920 0 R /XYZ 85.039 109.069 null]
->> endobj
-2925 0 obj <<
-/D [2920 0 R /XYZ 85.039 88.475 null]
->> endobj
-2919 0 obj <<
-/Font << /F62 1689 0 R /F35 1632 0 R /F15 1628 0 R /F20 1617 0 R /F56 1642 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2928 0 obj <<
-/Length 2044
-/Filter /FlateDecode
->>
-stream
-xXYoF~hD"AaH) GTk)J 3|3KglxX3f25\V8r>:c";W$3?¿¸Ÿ_ýfN<32'x{{tK _^-^x's}q+aoßÀ›ÛkóÃü5(0q<+ð#Ry ;jb,qq ;hE|'lfk c^5;g[kN0m 6>5i ]c@1bwjU/v
-js;pjgnT%& nS}%6xMhXo6 \YJ+Z9.U+)UeA\O||Gu Tv^\ciq
-c/e#1}pur)dR(:p_e5jX+RgR,+Rb# SHq3h }PZ!oD6^z"6[u.]d,f_P#pcNB&c6qK;1SZV~nunj}[#ENoxn/Cy[q}-' ^A=
-X ~Z/p+UJMR C<D!uXd - p$Rs?]DeqLl%(7
-l*s"CHF~}o ÿW8PysA
-fWXu}
-l endstream
-endobj
-2927 0 obj <<
-/Type /Page
-/Contents 2928 0 R
-/Resources 2926 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2930 0 R
->> endobj
-2929 0 obj <<
-/D [2927 0 R /XYZ 85.039 781.388 null]
->> endobj
-2926 0 obj <<
-/Font << /F62 1689 0 R /F15 1628 0 R /F35 1632 0 R /F56 1642 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2933 0 obj <<
-/Length 1561
-/Filter /FlateDecode
->>
-stream
-xXmoH_!DxwNh\®'\Û%V;~3;N]NUo3<; l3x`y øøÌã®MzOB;O$yo`(Cwg O.qxLK#0PtlvX.`%0N 5G WzC0 tsG/{6a_Af< 6iEZsa-1! %#|&| npv®
-ÁÏ3"«,Ha]eylK0z$D'r09EUP KB5Q!k%
-(TQ70uze@>(&4RFZJ2y(*u<`)pxŠk´ë³KiKwT:?|XA$H Dn+>$QQ_u*/#tA[/"eh$ ;;kDaoz Wxp -`'IAh$0DSLGR
-uZ:.7?5"]MnG^W4IC+7k$hK5 ypJHE}!M"drs_;}/?TuOnAp[i)${q
-b&W&@eUfE#8(e'jZ'2REiCYz8g
-64 Up: <VQ7  u)5%Ê6ÃÚÖ&ÝfنÐáɪÇ
-;O\9zxZaN;?1nYyz>LlQ &=;{;9]M?~;Mw<uG=?e?x"S{?{c$5cq{In<zD.20m@e<5HFQzWj Ve,S,TGbG'h0Kh8RM:A NqZCL $0t>&?'uoxsaK},<~W3Ap*;mX{EMFu]M&d(T
- &|Kü¥©¸(Ë´"0´ÿ9FW'\N5UTCU04UjbLFV}z; X|%fTgM6-"6°²ì~G\f!xx4~>k\rNA~)endstream
-endobj
-2932 0 obj <<
-/Type /Page
-/Contents 2933 0 R
-/Resources 2931 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2930 0 R
->> endobj
-2934 0 obj <<
-/D [2932 0 R /XYZ 85.039 781.388 null]
->> endobj
-782 0 obj <<
-/D [2932 0 R /XYZ 85.039 761.463 null]
->> endobj
-2935 0 obj <<
-/D [2932 0 R /XYZ 85.039 741.337 null]
->> endobj
-2936 0 obj <<
-/D [2932 0 R /XYZ 85.039 741.337 null]
->> endobj
-2937 0 obj <<
-/D [2932 0 R /XYZ 85.039 741.337 null]
->> endobj
-2931 0 obj <<
-/Font << /F62 1689 0 R /F20 1617 0 R /F15 1628 0 R /F56 1642 0 R /F35 1632 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2940 0 obj <<
-/Length 1369
-/Filter /FlateDecode
->>
-stream
-xWmo6_9E#5E% fqt2Pm!R`Gtay/x.Bu=Fu.saZ~]2dO;eNJf~0~?Ì!ýëzÆûñÕ««Qxs}y= }>Jhu[-0Xk_%eï' x5¾ìßO_c0s$30PfI:i7;pn~wiut~AEh G HA|s |lzCW8c R>MVeQa8"?H|^qllz!_Y#-z4,>'$^5!Iv{<;m!\ 7l`r&)3{ z-ryTyZ|1&ywB:H]\I}<M"rµ!º»…¬íB-CW 
-JQV%$B
-;&dmg>M2J*LFt{p
-oC2:2`<=\-PQw^YeS¬•é
-¹떯§Ó7z„zÈ€Ê ê‰r”V0Pju
-$YNLTZj"?)(XGT"l4C8<XjOey!5w<hPSa65#&D>;Jg Ptvy2K_jIzPLQdZ#<TyVM]-_h>y
-ovr[o…q±« ê¬$N+ e%y$AgRJIx",*E?O<r'o/im R>Zohk;2<KG8`]haiD[\aKY~S6$|x?endstream
-endobj
-2939 0 obj <<
-/Type /Page
-/Contents 2940 0 R
-/Resources 2938 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2930 0 R
-/Annots [ 2944 0 R ]
->> endobj
-2944 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [361.189 502.381 414.575 514.071]
-/Subtype /Link
-/A << /S /GoTo /D (winbind-solaris9) >>
->> endobj
-2941 0 obj <<
-/D [2939 0 R /XYZ 85.039 781.388 null]
->> endobj
-2942 0 obj <<
-/D [2939 0 R /XYZ 85.039 519.048 null]
->> endobj
-2943 0 obj <<
-/D [2939 0 R /XYZ 85.039 519.048 null]
->> endobj
-2938 0 obj <<
-/Font << /F62 1689 0 R /F35 1632 0 R /F20 1617 0 R /F15 1628 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2948 0 obj <<
-/Length 2188
-/Filter /FlateDecode
->>
-stream
-xY[s~;{ClGXN-zNDT$UMsYJ3{9{\sYXB#Gv8B'h> GLz
-‹H;MDj$CB7,%W?^Ob<$xuXy|z ^_JOji5z;u#0ZXH`spD&"
-/ T,%{B:7Z=3S0qEOuVMs
-xi!}31
-ygt*<uJ5q 92*n2lk?hN0bJU
-c+#Lbb
-4dh_uh#[J0&6Um{
-eJG:hYlG\I+ {#arGh^<E!HZy)euSKT"c6V2m !KLfDX*K.83iˆ¥ op\ñ¸l`²l#oé]±à4ŠOLW-VyQ}FK}.hIQm\ 1c3d]@vj|` 0E1>N!ªîÞc½Öi¿CC
-(b?QgfI Af ;^Xp&`
-FR?a6XB69B{
-endobj
-2947 0 obj <<
-/Type /Page
-/Contents 2948 0 R
-/Resources 2946 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2930 0 R
->> endobj
-2949 0 obj <<
-/D [2947 0 R /XYZ 85.039 781.388 null]
->> endobj
-2950 0 obj <<
-/D [2947 0 R /XYZ 85.039 341.117 null]
->> endobj
-2951 0 obj <<
-/D [2947 0 R /XYZ 85.039 341.117 null]
->> endobj
-786 0 obj <<
-/D [2947 0 R /XYZ 85.039 283.083 null]
->> endobj
-2952 0 obj <<
-/D [2947 0 R /XYZ 85.039 262.488 null]
->> endobj
-2953 0 obj <<
-/D [2947 0 R /XYZ 85.039 84.027 null]
->> endobj
-2954 0 obj <<
-/D [2947 0 R /XYZ 85.039 84.027 null]
->> endobj
-2946 0 obj <<
-/Font << /F62 1689 0 R /F35 1632 0 R /F15 1628 0 R /F20 1617 0 R /F56 1642 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2957 0 obj <<
-/Length 1800
-/Filter /FlateDecode
->>
-stream
-xX[oH~#a
-9OLe:$.7z;/',
-R?.Vtft~y+tD8Ng3_|sOp/^XnH9k UJ
-EoV5] /,HK2Y_E.k{+2k5oNc] (S'AGuJ8! WO~ d3 ߕXa )#0O e2M !d,*0 g/s,z0 zwh .;C[BbcRe1 0iLJq~x=FX]i^`(6>6 y"/MnoEGR'X=lzWCpYW
-pyLKC'@l0>6nEViq7CfloC2H5GL@0r^&o]o0z@2M^'c= >
-.E",pJB9 m4 0:"GnYD*Xb8&3U,Ak45o`7?Y"1B? ed>q.@0+-`=* yAOE%;{q^o2 mkk%0IqZ&hF&^-=w+Xd"@Qn XMksSR<Ml.Ts+P {\,dHQ80b2ef]vhX7WE>b;Pk$R:0Z
-sWe}EWH5m~Fk|/+ gHqS!FE3ro{!,0g1<X)^Cm`&}1zpN9%(gdh [2C.}+%%%At})p?8-
-EA' 7ypiW{s'2$T ]99!, M -[#fZBIpQ^!?Ik]w|6_0?{jI<lU"#,PF.hau(w1dTelFP$v[Q<:cP# z%  4m'~B>*Q0eU#Mf&CrXS0@{
-,pwxC}?;ax I_7F`~9w\~
-endobj
-2956 0 obj <<
-/Type /Page
-/Contents 2957 0 R
-/Resources 2955 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2930 0 R
->> endobj
-2958 0 obj <<
-/D [2956 0 R /XYZ 85.039 781.388 null]
->> endobj
-2955 0 obj <<
-/Font << /F62 1689 0 R /F35 1632 0 R /F15 1628 0 R /F56 1642 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2961 0 obj <<
-/Length 1676
-/Filter /FlateDecode
->>
-stream
-xXmo6_a4 5-zM;.-EaR3Gr,;^A,Gs/<M}a~P^sgk3j,d<`(0C/ˆðûÛWo'S?}Doo|i'l'_fA!yrB3>}11g2;A&<M{l6/
-*0*V;7bD(*
- fZk\U<l
-tdeE.iVIx;DkvW phHpRCwR/ %
-fÆ
-8–cL:%j](0B4bjuN7iT
-_ucU66DwZFmV0J"K!e?pXx639' xv"(SzHyc^~7vIl^]&o3kHendstream
-endobj
-2960 0 obj <<
-/Type /Page
-/Contents 2961 0 R
-/Resources 2959 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2930 0 R
->> endobj
-2962 0 obj <<
-/D [2960 0 R /XYZ 85.039 781.388 null]
->> endobj
-2963 0 obj <<
-/D [2960 0 R /XYZ 85.039 679.517 null]
->> endobj
-2964 0 obj <<
-/D [2960 0 R /XYZ 85.039 679.517 null]
->> endobj
-2959 0 obj <<
-/Font << /F62 1689 0 R /F15 1628 0 R /F56 1642 0 R /F20 1617 0 R /F35 1632 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2967 0 obj <<
-/Length 2390
-/Filter /FlateDecode
->>
-stream
-xYYoH~@7934fAK$"<q&%bnVUW}u4eO,gO"xFFd]\X-epMLlxeqYF/77}xa;\z=wa\ngoo/fk^L
-LU+ ¡+×UA"R[kSn^_yJA`jU<?+JOnO1Z
-$H<<q|_q:A3d>w$:|#o? L't2x B,zn• $˜wÜ(6Ae; %J+XYWk]A&
-'I2GlNzOgAZ5s\UW2vM@h D&/RLbëVNH+lw<@
-}";ngkE`[bH{`'d0a}0#>nKsBDhT#g^p5@; : E%L0}wXN`8V lw#L6 PCaH+ycdw|TiyO)#4r8" }ms
-_YsU/%,1a|z-qh&NTuc>VfFjm0WH uo^nN
-wLe2S"^
-xV,qRyAHnP C:{
-y6yK^=A^m5
-=[;%0
-H0kLZ{w Db<LW? SR`0L%jh(~F<{# Fv]kdpKAXAbVB!/Qn+AyH}i6N)X%d|Qc -v=vr]L)1s.O*?"VyVyntA@"Z<KC\'X2+DpkmLx/SGN#=QjT GCm7¹xçî{ð¼eÇpH\ll c*+ A%fCE3!!wRJn ?¼‘cžûˆ±µãóŒn)ÚùT7??^C;#?U7>74+vGX+_hendstream
-endobj
-2966 0 obj <<
-/Type /Page
-/Contents 2967 0 R
-/Resources 2965 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2971 0 R
->> endobj
-2968 0 obj <<
-/D [2966 0 R /XYZ 85.039 781.388 null]
->> endobj
-790 0 obj <<
-/D [2966 0 R /XYZ 85.039 413.993 null]
->> endobj
-2969 0 obj <<
-/D [2966 0 R /XYZ 85.039 387.379 null]
->> endobj
-794 0 obj <<
-/D [2966 0 R /XYZ 85.039 144.576 null]
->> endobj
-2970 0 obj <<
-/D [2966 0 R /XYZ 85.039 117.961 null]
->> endobj
-2965 0 obj <<
-/Font << /F62 1689 0 R /F35 1632 0 R /F15 1628 0 R /F20 1617 0 R /F41 2104 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2974 0 obj <<
-/Length 2952
-/Filter /FlateDecode
->>
-stream
-x]o=o"RWb\z -AdGdl%X &9Cr83ZZ"Ib\-@~DAWIXigapuQ q.6P_(>n]U'miav*{f][-˜•4¶Ë?~¾úéa$ÔQa@]$3@TBM|x(x[Uy-SooJ[ h$ Az.y}ID}wv\P*hp/H&`de@z= ) MZb3,;3vmo@
-{2k
-dBEWS2Nq? (.U^ <#AnrmpQ# G^-48<2 40~DCFV]s)\Q-p6Cu'w?G%W*=5EeGMe|we\O9YfFaA,vmM^$<wB'RXukU &eg$tf `n@V-n}NYDT`mE, :mUk$`CL$&jßVz <6FR# 9>],/ #3'LI+(y),et=/>k_u' 5&EBf(euT7
-?H)ZGKv -+I)
-O@ Zj\@J%
-QX =[sf ^Bo $6J!0 et\#+U.(:zp\
-pi0LO'/=Y<q=wOO+&}]-(ukWAM*a
-OrBEOcb)cG}U=rb@
-5etD[CZ5+pLf[5ZieR3w+-:D'<6kT@}G%q$&8'b@Yj\tFGb
-d1')4j0z2L=Z@n  B
-c:.i
-SJh]T
-P}IkEyrDWIBj+#z@9CPFBl.r/j GpHO
-Wh-) }vPgK|9i=jVtD$K"Z;uMÊ£x<iÀÌ5<›ªï]?‰í€¡4·¾àçþ0[dz„%jZd32'*}8M'i'<6L@9(O<`7"&%I
-O!tKl@JYy g,Žâ¾Չ¯K!?@jE:AN&dM-GW:jr REqxB:j5i!}"=jN|3TfL",
-endobj
-2973 0 obj <<
-/Type /Page
-/Contents 2974 0 R
-/Resources 2972 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2971 0 R
->> endobj
-2975 0 obj <<
-/D [2973 0 R /XYZ 85.039 781.388 null]
->> endobj
-798 0 obj <<
-/D [2973 0 R /XYZ 85.039 761.463 null]
->> endobj
-2976 0 obj <<
-/D [2973 0 R /XYZ 85.039 667.044 null]
->> endobj
-802 0 obj <<
-/D [2973 0 R /XYZ 85.039 611.854 null]
->> endobj
-2977 0 obj <<
-/D [2973 0 R /XYZ 85.039 582.45 null]
->> endobj
-806 0 obj <<
-/D [2973 0 R /XYZ 85.039 364.615 null]
->> endobj
-2978 0 obj <<
-/D [2973 0 R /XYZ 85.039 343.418 null]
->> endobj
-810 0 obj <<
-/D [2973 0 R /XYZ 85.039 303.379 null]
->> endobj
-2979 0 obj <<
-/D [2973 0 R /XYZ 85.039 280.058 null]
->> endobj
-2980 0 obj <<
-/D [2973 0 R /XYZ 85.039 210.556 null]
->> endobj
-2981 0 obj <<
-/D [2973 0 R /XYZ 85.039 158.82 null]
->> endobj
-814 0 obj <<
-/D [2973 0 R /XYZ 85.039 98.425 null]
->> endobj
-2982 0 obj <<
-/D [2973 0 R /XYZ 85.039 77.224 null]
->> endobj
-2972 0 obj <<
-/Font << /F20 1617 0 R /F15 1628 0 R /F65 2099 0 R /F35 1632 0 R /F70 2201 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2985 0 obj <<
-/Length 3051
-/Filter /FlateDecode
->>
-stream
-xZ[s~9M<3nc''Ry%J"]tt<c ,vPjE(Fh;sFùéL 3l'q@cN<Zdh]|f1{;kL0.&:ORl+$[l/>r.nakv|Zr6[v2l/pq+}V_#[hw{g7Yz:u kO/l9ygh5[8Cz2U'U5*~wiU:4'%>îÏy‘¬€ÇfüÜTgm,"oPijteQo-)ePN1r= kw SOl?$93qFvU}jgiT)\A
-IY<g>x4Ih@S^xSmQF4ie+¢k)w)šf>f´~Ido%I4M\`|Y{%ê›òáDpt6AIEr?Yw!wh0]vM7i5.r>Kx(= +wGSN?N
-4tZR*weTlMR7 [<++J jYTI=,yJ?qvBE3`zZNe3Ap5/5«
-öÜ6Ì 2°F-~L{}0`sxm
-g$p*h~+9:P5Uh]B)|{gbwM+ZTt$/ut"5I¨œÈ5aìQ$r<!. JlIY'2!hvAKF: RPEcULeD
-gf mlh:t*h/aJ09{}@ i0<?i$j'&m=G!D$B~drq]8!hU?fK4bh()B<
-e6P
-~RS$ PL$
-
-aÅbªP@zPl>)sTWT,q;~ #qN71}+q]W,@40+ yiRDIs[mu!LE\n?j
-&@0}Vxbnr.1OR7
-=2urHeo@Pv  I,<x,f~Co |}AHc  g|Uma>K)M l}M@}\ "9<4
-2Y.H(]mh5U8VENF(un_{-e;C#PG_M_~5~{7gNnY)mn7mc|m>7Czs}ZlýzŸ
-endobj
-2984 0 obj <<
-/Type /Page
-/Contents 2985 0 R
-/Resources 2983 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2971 0 R
-/Annots [ 2991 0 R 2992 0 R 2993 0 R 2994 0 R ]
->> endobj
-2991 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [327.043 103.871 512.306 115.863]
-/Subtype/Link/A<</Type/Action/S/URI/URI(ftp://ftp.microsoft.com/Softlib/MSLFILES/NEXUS.EXE)>>
->> endobj
-2992 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [111.316 91.837 216.398 102.314]
-/Subtype/Link/A<</Type/Action/S/URI/URI(ftp://ftp.microsoft.com/Softlib/MSLFILES/NEXUS.EXE)>>
->> endobj
-2993 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [327.043 63.223 512.306 75.216]
-/Subtype/Link/A<</Type/Action/S/URI/URI(ftp://ftp.microsoft.com/Softlib/MSLFILES/SRVTOOLS.EXE)>>
->> endobj
-2994 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [111.316 51.189 233.58 61.667]
-/Subtype/Link/A<</Type/Action/S/URI/URI(ftp://ftp.microsoft.com/Softlib/MSLFILES/SRVTOOLS.EXE)>>
->> endobj
-2986 0 obj <<
-/D [2984 0 R /XYZ 85.039 781.388 null]
->> endobj
-2987 0 obj <<
-/D [2984 0 R /XYZ 85.039 664.726 null]
->> endobj
-2988 0 obj <<
-/D [2984 0 R /XYZ 85.039 585.892 null]
->> endobj
-2989 0 obj <<
-/D [2984 0 R /XYZ 85.039 535.672 null]
->> endobj
-818 0 obj <<
-/D [2984 0 R /XYZ 85.039 292.839 null]
->> endobj
-2990 0 obj <<
-/D [2984 0 R /XYZ 85.039 271.077 null]
->> endobj
-2983 0 obj <<
-/Font << /F62 1689 0 R /F15 1628 0 R /F65 2099 0 R /F35 1632 0 R /F38 2158 0 R /F70 2201 0 R /F18 2207 0 R /F20 1617 0 R /F41 2104 0 R >>
-/XObject << /Im2 2261 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-2997 0 obj <<
-/Length 1931
-/Filter /FlateDecode
->>
-stream
-xXr6}Wm2f"M;Nqc}H@ EeY]Rz=
-3/&]St4
-endobj
-2996 0 obj <<
-/Type /Page
-/Contents 2997 0 R
-/Resources 2995 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2971 0 R
-/Annots [ 3000 0 R ]
->> endobj
-3000 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [218.134 709.485 287.369 721.175]
-/Subtype/Link/A<</Type/Action/S/URI/URI(mailto:jht@samba.org)>>
->> endobj
-2998 0 obj <<
-/D [2996 0 R /XYZ 85.039 781.388 null]
->> endobj
-822 0 obj <<
-/D [2996 0 R /XYZ 85.039 761.463 null]
->> endobj
-2999 0 obj <<
-/D [2996 0 R /XYZ 85.039 736.911 null]
->> endobj
-2995 0 obj <<
-/Font << /F62 1689 0 R /F20 1617 0 R /F15 1628 0 R /F35 1632 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3003 0 obj <<
-/Length 1391
-/Filter /FlateDecode
->>
-stream
-xXmSF_ g^lL_\0JB:[
-Hg&qMCv}T3jC .%jahX9iP%ah61:.7S OB{#lYi]W5MWaI#\^¾¼‹&J'}y5MP>4^Zh<Wmya;qlKfkr[e[ec:d8Y{8(YOI]~k\=C!`<(/RQ|()Oz~yP)`*IU;$n*9H#vgX3CI%}P^\ =|1Y
-,^x NDy eP+*/-e=US'jD+ :c\bH`+NlE'}4gyy_Wk&{bChK[_j'v{m47}A}Z|r`wxM(!fSIl*fy>O8=\3 .D]}4 Df paP:SOQCaDThHEXkiv]V^Pr&"x4Qh0 U%L!p0)q 5<cqn1
-endobj
-3002 0 obj <<
-/Type /Page
-/Contents 3003 0 R
-/Resources 3001 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2971 0 R
->> endobj
-3004 0 obj <<
-/D [3002 0 R /XYZ 85.039 781.388 null]
->> endobj
-826 0 obj <<
-/D [3002 0 R /XYZ 85.039 95.579 null]
->> endobj
-3005 0 obj <<
-/D [3002 0 R /XYZ 85.039 74.989 null]
->> endobj
-3001 0 obj <<
-/Font << /F62 1689 0 R /F35 1632 0 R /F15 1628 0 R /F20 1617 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3008 0 obj <<
-/Length 440
-/Filter /FlateDecode
->>
-stream
-xRMO0WhKcZ Radil,'[)yf
-Pgfv6D9'0E(Je 2; %X!EyN> 5+2<q
-+a#hh[C0cOv 8>
-v< ']pP_sendstream
-endobj
-3007 0 obj <<
-/Type /Page
-/Contents 3008 0 R
-/Resources 3006 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 2971 0 R
->> endobj
-3009 0 obj <<
-/D [3007 0 R /XYZ 85.039 781.388 null]
->> endobj
-3006 0 obj <<
-/Font << /F62 1689 0 R /F35 1632 0 R /F15 1628 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3012 0 obj <<
-/Length 3611
-/Filter /FlateDecode
->>
-stream
-xZYF~_1K8ElcN"k+0z(JC <I zoTv6o eD)7
-C(Y^$n¨ÛYG#~Ymqnk\}uE|w3w3f*8/5W>)iFe}[zs 4%1U0
-r3?
-#}>W]0n)5=pec%p4jbe}M]P3=g[#wPtWy 9k\xQf ,9<2 83T6if8/xe 5 "2> Bg3?s/rrD?mx88m[o7/mZp=O<nvG.WqNVFt
-#PBk;:Y =f% :@+3 a:/{3<ZyU ?U!-7gn w-Dd
-M[G35#2s!DI/KeAlqF6:Sm7e?t",Y
-5lMlY>Oi tF_+*07 f%jYa³y#ªWt(JxYTBrv Y7o-*a$dA#\"I7wiH0h] ;1_\?I
-[\}3 W_?x|P]p<@MhJ; Ytkk^N] ÍÔÉ6kb·¬j{z âüø¢G }UM3i{ ARdzn`J=Qdg1w ~M1%HVO([*4O]g0tFr~@.,y @ ;vb]hg#?SK}E.okZbprRcKKNs(q= TaY4dF:zR}fI?v^(>DFv{.".;qa;{ E^s% %;cHEwS"1!Ogq4Yu,"B
-mj)B9Z.NkYLsuc3:`A-."_h
-SG i@0'pW56H}gu FMa3q(8xV#0 HBI'&fgqyl@|w9#A*Ht MMm`-z5RY&Tsea3w]VL'Fe <%}7V(HWrP92
-[z+?6FdEÃÌY\<kywK'0x!j
-%BkK%i:q&nRj8xcH
-%l%[#Bz+<Us8Mk|`L\ySsd}9p(I4AnPW+C,`Jf!*=ypb:S }^4?JadS9R6p.s 8v4Y,I*DLd $/182Dzyk$N<
-z PPFR=w=kV"<ywcb9s|91%Z9wu RzI6Y QX?taa4.gh^1yJ L,#g.=›\|,RxÙ?y÷Šq¤É/‹1>÷Ys I#5d/[IyV12jeeN @{|OqS^ f<xx1hXD@9lv$ps%DOjYJ*6>hw`iԞnj¯éA
-XF9+I?r, &;1 d&EzJ<'$qG"v(!I\~22ivd?0^,[Xgf"?zgLM0)(*HxdUCAS 4# y=!.0'< S8sL `S*;$P!endstream
-endobj
-3011 0 obj <<
-/Type /Page
-/Contents 3012 0 R
-/Resources 3010 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3018 0 R
-/Annots [ 3016 0 R ]
->> endobj
-3016 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [111.316 313.422 824.811 326.323]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.microsoft.com/ntserver/management/deployment/planguide/prof_policies.asp)>>
->> endobj
-3013 0 obj <<
-/D [3011 0 R /XYZ 85.039 781.388 null]
->> endobj
-830 0 obj <<
-/D [3011 0 R /XYZ 85.039 761.463 null]
->> endobj
-3014 0 obj <<
-/D [3011 0 R /XYZ 85.039 667.044 null]
->> endobj
-834 0 obj <<
-/D [3011 0 R /XYZ 85.039 667.044 null]
->> endobj
-3015 0 obj <<
-/D [3011 0 R /XYZ 85.039 639.536 null]
->> endobj
-838 0 obj <<
-/D [3011 0 R /XYZ 85.039 232.013 null]
->> endobj
-3017 0 obj <<
-/D [3011 0 R /XYZ 85.039 210.152 null]
->> endobj
-3010 0 obj <<
-/Font << /F20 1617 0 R /F15 1628 0 R /F35 1632 0 R /F65 2099 0 R /F38 2158 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3021 0 obj <<
-/Length 4053
-/Filter /FlateDecode
->>
-stream
-xZIwFWf0O@cc'$9@
-pœüú»wZNyA>@sUnNt^\}G0~1MmV ]{&vFm;k}I/)78
-g]5f8(T bvU XrDgY]vzi+<z,Xs{eRYr*L'@']ZYy`0H0cU\m]O
-A0gT| 4uygm(r}:/xi>k%"!hghD]O$PZBM~qoI@ <7CrhKS8VpZk3z+W~`eX/"\"FTW ?5N ^3RMD
-v"0%GH.->F SkF|e@ p8@<{4
-`Y96"R9C<F$0 V %8,((;ZdR4
-UhHxox Cw+LBU7[Tl3k] ow`00}*\,5+_UsBu4t( Rc<CDdVkn\ xL!HQAQ}'"ZY"!Icht(2Qn f3ZnY#uh~ZA\uX M5F/h$p0> |]BHa7R+d_
-lGt^"d}1 c8a:,]F;{,qHIzznh/'|->60k6qA* FO;[#lx,rI_or,?3+_VLb$hO1I a1$$_@6< ?L]5A9g@P#p%} 6Žö8JI&’A"jwu"q \|lY1Kk t 3/AZE An3V4(
-
-fcq:w|".
-ZcMN o Nl0],8q /mF!P+9|C,w9
-4eQDYl4(z7P9 3|!%| d brmP~8`f3)ncn|3%óÅ ¢a‚Y;N> NO|PIRp>]jtY@3<=__| q g//|"Y7vCbvfr( Sjn)j9t8!`
-< w`Byp)mh Yr>O7OKk?( iRpe T-qzrbwc6QEaQ1Y%2c5jy<k6q]HW@yhtzy:kY@-U{=9}_|Kt{@ôäÊ9{e@Sb>MY!(^s"T
-z642CSuMQ:~
-+Yp i:'#<
-~~hyI8ta$a-1mee hG en
-(:YD0@`6sTBKopgs/{X|b1 -I2Hzxh
-K&s*_VF g|aw`cjs~BqF
-t{Av)@~b-; euJnkn|}nv7 s")F) +
-w=RtM"5žµ`ƒt?´[nÀ;=¼)þ‹Ü÷‹e”¦“I}?y3
-~!. '
-endstream
-endobj
-3020 0 obj <<
-/Type /Page
-/Contents 3021 0 R
-/Resources 3019 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3018 0 R
->> endobj
-3022 0 obj <<
-/D [3020 0 R /XYZ 85.039 781.388 null]
->> endobj
-842 0 obj <<
-/D [3020 0 R /XYZ 85.039 651.216 null]
->> endobj
-3023 0 obj <<
-/D [3020 0 R /XYZ 85.039 630.626 null]
->> endobj
-846 0 obj <<
-/D [3020 0 R /XYZ 85.039 400.898 null]
->> endobj
-3024 0 obj <<
-/D [3020 0 R /XYZ 85.039 378.183 null]
->> endobj
-850 0 obj <<
-/D [3020 0 R /XYZ 85.039 270.194 null]
->> endobj
-3025 0 obj <<
-/D [3020 0 R /XYZ 85.039 246.212 null]
->> endobj
-3019 0 obj <<
-/Font << /F62 1689 0 R /F15 1628 0 R /F41 2104 0 R /F35 1632 0 R /F20 1617 0 R /F56 1642 0 R /F65 2099 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3028 0 obj <<
-/Length 3344
-/Filter /FlateDecode
->>
-stream
-xr6_5M_6V6i
-K5 % ~P&pA)5&c/Z20XMBVjyZ
-Fk+@UVAn@p,Vq{5G`¥÷\1ºG<4 :ox|B=9~
-?B<#@w%K)#·9ì$²+;öŽÕRd)Ne%;+v$KQEZAP aQw]Djb2S'A??s[g*H<"
-€³k
-¾,|Óy’<|jt»¸`ŸL*h/3C>|.qqN\hcdD.2``J@GLPR'H2EUSw^$
-J`#D}_347
-l0|8}//;2APmk{!gfH
-i8=!s -F9~?\240J9]_-s)'m^'Af´,·4åݵà. ¥KQn#\u~'5gh4RO_P8PGEU^sIBu-1tYy
-_r
-endobj
-3027 0 obj <<
-/Type /Page
-/Contents 3028 0 R
-/Resources 3026 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3018 0 R
->> endobj
-3029 0 obj <<
-/D [3027 0 R /XYZ 85.039 781.388 null]
->> endobj
-854 0 obj <<
-/D [3027 0 R /XYZ 85.039 462.134 null]
->> endobj
-3030 0 obj <<
-/D [3027 0 R /XYZ 85.039 440.933 null]
->> endobj
-3031 0 obj <<
-/D [3027 0 R /XYZ 85.039 395.802 null]
->> endobj
-3032 0 obj <<
-/D [3027 0 R /XYZ 85.039 346.794 null]
->> endobj
-3033 0 obj <<
-/D [3027 0 R /XYZ 85.039 310.73 null]
->> endobj
-3034 0 obj <<
-/D [3027 0 R /XYZ 85.039 274.665 null]
->> endobj
-3026 0 obj <<
-/Font << /F62 1689 0 R /F15 1628 0 R /F35 1632 0 R /F20 1617 0 R /F38 2158 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3037 0 obj <<
-/Length 3162
-/Filter /FlateDecode
->>
-stream
-xZYsF~[1(-y-zl  MR"st}@?Ff$0Mgmh3q8`{neOYvz|nwHOwo;m}Dq y^,xp0C_8s,}Y6/L @ELV9`x0(nGL>dU~H'!{ ,pz8#Ab7>(>|3YUkUOG3|E;<cCC_I]lWe/+kp 4tv^U
-dÌÖæ‰æ%ÄQJFq H$"K"&.^5~
-cq%uq_o6l3,}{z0d8x
-i vA+>[8H` yI2v:_`;XIhhWMYGemT~a$Jf"V"6cCVEniZ]iGe<Tu`V^uV)&4cBO}gUVV2y')z)lFq6â.’È5I`dd6:.eHOM3sL $hA>#y7l6$8&_]_
-<Na>{U7HH/Hh#~tVu
-A
-HI+ P]U{ 'Ws1*K6N/ßˋ‚sÉm/}¤­§J:syvIgOI`hZ{(k%M+Tj4o(rO)E;}C-e8tBRHKMlA=%r=Q4i._K&lDBH
-`H ^@-B-JL7z.31D DF'EtZi)}Ck^/j /Uq%M'+} )Q}\&u9}#%9vJp
-BIhH!5Zp6foUVg|.9D%
-i9D|gZ#
-@Ca@4'-zi/Ymv"W.>N0 Gz 6n|)hVn3BB <_OsX( As/a{t6,]\Bk(HG~hjDY-,8RP x
-endobj
-3036 0 obj <<
-/Type /Page
-/Contents 3037 0 R
-/Resources 3035 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3018 0 R
->> endobj
-3038 0 obj <<
-/D [3036 0 R /XYZ 85.039 781.388 null]
->> endobj
-858 0 obj <<
-/D [3036 0 R /XYZ 85.039 625.193 null]
->> endobj
-3039 0 obj <<
-/D [3036 0 R /XYZ 85.039 599.048 null]
->> endobj
-862 0 obj <<
-/D [3036 0 R /XYZ 85.039 117.402 null]
->> endobj
-3040 0 obj <<
-/D [3036 0 R /XYZ 85.039 95.541 null]
->> endobj
-3035 0 obj <<
-/Font << /F62 1689 0 R /F70 2201 0 R /F18 2207 0 R /F20 1617 0 R /F15 1628 0 R /F65 2099 0 R >>
-/XObject << /Im1 2193 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3043 0 obj <<
-/Length 2713
-/Filter /FlateDecode
->>
-stream
-xZYoH~"7d6q`13HH.I[Wd"q
-5?:(aU
-Xz'"pnF$OnxT;<ss%VUFt}RjYG&*9N` 
-'"]X]P$"T-
-i^nx
-Xe$-vLPfU&rB_xnm3x{VWU
-v, /
-I\88ab`oiGMfP
-1h-@n<b$lF>Y3}OL4.t*>2\ 8z6#;m*Wmh*nmoGj1Uz;4!6OiGx {¶êØþ’7_4XSo(NoBy^clQTh@w+]R(f*+YOnLpp+Ca4e:C}E~OQy_D 2WJl|+qD kwY)rVk"Ji@}x}'C< v?Za
-
-FA U)e-0Q<ykW2f5=Wt5b_@wK:c{Q*j!d0wCu6Ks`FA#!O4xp_'}a,
-uAz6%yg<[5vUo\t|D. 8(z(c="&_BE{B'P4o(Ahlr3cWUKl;*T q;P2k"x5r<)pDtOC /^/@C'‡¶MWH<B"qw+P+~R2< $gn¬³ã_þÆϯä‡Sj&
-C!ef jTs4T5d;hBAtWh)
-kY _ _5T)Ah>5hd7DzMY5[?2yh:yqF@[úÚ´2ŸŸ`úvüíý,,ÚjV no>N-
- `g!QBz=
-Q
-mRE?tf-)Hi3tj)1
->+N'x7)3VW,qRxZ") $CvUtNo?_bHÚ>€û‰zÿ ÚBendstream
-endobj
-3042 0 obj <<
-/Type /Page
-/Contents 3043 0 R
-/Resources 3041 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3018 0 R
->> endobj
-3044 0 obj <<
-/D [3042 0 R /XYZ 85.039 781.388 null]
->> endobj
-866 0 obj <<
-/D [3042 0 R /XYZ 85.039 708.141 null]
->> endobj
-3045 0 obj <<
-/D [3042 0 R /XYZ 85.039 687.147 null]
->> endobj
-870 0 obj <<
-/D [3042 0 R /XYZ 85.039 616.511 null]
->> endobj
-3046 0 obj <<
-/D [3042 0 R /XYZ 85.039 584.986 null]
->> endobj
-3047 0 obj <<
-/D [3042 0 R /XYZ 85.039 551.084 null]
->> endobj
-3048 0 obj <<
-/D [3042 0 R /XYZ 85.039 514.413 null]
->> endobj
-3049 0 obj <<
-/D [3042 0 R /XYZ 85.039 385.306 null]
->> endobj
-3050 0 obj <<
-/D [3042 0 R /XYZ 85.039 362.184 null]
->> endobj
-3051 0 obj <<
-/D [3042 0 R /XYZ 85.039 339.668 null]
->> endobj
-3052 0 obj <<
-/D [3042 0 R /XYZ 85.039 303.604 null]
->> endobj
-3053 0 obj <<
-/D [3042 0 R /XYZ 85.039 179.477 null]
->> endobj
-3054 0 obj <<
-/D [3042 0 R /XYZ 85.039 156.962 null]
->> endobj
-3055 0 obj <<
-/D [3042 0 R /XYZ 85.039 106.742 null]
->> endobj
-3041 0 obj <<
-/Font << /F62 1689 0 R /F15 1628 0 R /F20 1617 0 R /F35 1632 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3058 0 obj <<
-/Length 2181
-/Filter /FlateDecode
->>
-stream
-xY[o7~ׯЋÑ°os)°ÛvÛ¦Hl<%2ef~n5$yxxw.d4b0R4IEt,'(L
-!=u02Qae4QjXc p67&
-~z78 7;U`K[uO&^;0"E0G
-<#Pa&P^CyJ:/ Vp"q{Q>&i* hMPeQ(lZNB_Ln'5BlhQlfs1
-38hOB4+)4
-6?
-R+Jd4.8 EE'?PvMUm6 A`QCwV|Q 1/\IxZNU>#TinNWp~P
-.7K*%-)CAQ@iPgO+DE%b/tEWa ,glW5a‹Î!"¹%©.”
- \*¥ VvXxoH|qmZb\j 7?
-'t>\ _aXNkgN7O#Fx)[g]sp8gl0 kGG{:+ %D9`7'RjM\ i_}qG](|:GTi2]Sg&V3On%q6^dY3'dVf&8%Hq+)[Bg Iu%hr,~[ jQ x}A}+u?or %r ]0]nfyXk .dc,>2KX$|OxykBidt7n(\rhI\[.WhDgJ4:g9x"OozT/(.]2!4nU0w{W(=!NY p(s1-Y %^ 3s _9endstream
-endobj
-3057 0 obj <<
-/Type /Page
-/Contents 3058 0 R
-/Resources 3056 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3018 0 R
->> endobj
-3059 0 obj <<
-/D [3057 0 R /XYZ 85.039 781.388 null]
->> endobj
-874 0 obj <<
-/D [3057 0 R /XYZ 85.039 761.463 null]
->> endobj
-3060 0 obj <<
-/D [3057 0 R /XYZ 85.039 667.044 null]
->> endobj
-878 0 obj <<
-/D [3057 0 R /XYZ 85.039 667.044 null]
->> endobj
-3061 0 obj <<
-/D [3057 0 R /XYZ 85.039 639.536 null]
->> endobj
-882 0 obj <<
-/D [3057 0 R /XYZ 85.039 406.729 null]
->> endobj
-3062 0 obj <<
-/D [3057 0 R /XYZ 85.039 385.533 null]
->> endobj
-886 0 obj <<
-/D [3057 0 R /XYZ 85.039 343.373 null]
->> endobj
-3063 0 obj <<
-/D [3057 0 R /XYZ 85.039 322.172 null]
->> endobj
-3056 0 obj <<
-/Font << /F20 1617 0 R /F70 2201 0 R /F18 2207 0 R /F15 1628 0 R /F35 1632 0 R /F41 2104 0 R >>
-/XObject << /Im2 2261 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3066 0 obj <<
-/Length 2349
-/Filter /FlateDecode
->>
-stream
-xYo8W`q2P3KEzMwE%!Jr;Rm9Ip72r?9Ju:)tnGf~:nE82",NH" tNK>y?=0h$XWt<;%?U{{v~$kN/iO&(_ (:MFLX-n\]sf_ xbT$T+MM@$adC{n6 Z: }C\V0:"4iy'97l!Go*hJB
-NU'Lqq5DPD\*4Ct\"}
-c+SnR{|mT]V-7+bT-qn*sTf:CEIHJ|< \k_# o*p3wml1 Em>5gns:/Mn!zV=Sz]^´e/m…ÒÆ-b)ÚlÒPV0&Z$`p4LU6ViP!eTsnQ,F PQ l'v$Bo9}WhC"VC/=s-;y(*(@
-EIOz.F=B'}6pkGY w$H.q&$kx
-QpwLh,8wE
-phsbN"$mP
-#6!!c88MPqQ(/wº§8º¯Y E}^?F;[&v7W™tazð‚²Ú}Óꦭ17qBajÒqF/'Jzp
-8`7YYBd74}|<gk s)z}aQvRS\%&Q\^v~r/d ;8>\DdX$K"<kn
-#mxO\xXp3*^ 8~ocL0BY;iq :R3nla)sl kW=QiD
-.l%4R#zTNw$%#i
-&:*#W9 \xLbaa9|d`D?~
-WP"D_)ykv _$]
-}xg
-n!UC70e0|Wm%?_SK,kp1h(CUA!_oxX2y+k~N4> ;OV.Tp j Dn=5b Ar)[/BRC!Z
-xl55"gN5A* q.=:l;
-endobj
-3065 0 obj <<
-/Type /Page
-/Contents 3066 0 R
-/Resources 3064 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3071 0 R
->> endobj
-3067 0 obj <<
-/D [3065 0 R /XYZ 85.039 781.388 null]
->> endobj
-890 0 obj <<
-/D [3065 0 R /XYZ 85.039 627.355 null]
->> endobj
-3068 0 obj <<
-/D [3065 0 R /XYZ 85.039 608.404 null]
->> endobj
-894 0 obj <<
-/D [3065 0 R /XYZ 85.039 366.597 null]
->> endobj
-3069 0 obj <<
-/D [3065 0 R /XYZ 85.039 345.396 null]
->> endobj
-898 0 obj <<
-/D [3065 0 R /XYZ 85.039 239.608 null]
->> endobj
-3070 0 obj <<
-/D [3065 0 R /XYZ 85.039 216.892 null]
->> endobj
-3064 0 obj <<
-/Font << /F62 1689 0 R /F70 2201 0 R /F18 2207 0 R /F20 1617 0 R /F15 1628 0 R /F56 1642 0 R /F35 1632 0 R /F41 2104 0 R >>
-/XObject << /Im1 2193 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3074 0 obj <<
-/Length 3062
-/Filter /FlateDecode
->>
-stream
-xZYoH~
-k]k'63(0E*$eMR,°`õQ]]](]O0|sV00H^?f'or$<7lI$R;a\ çö#ü™'¹Æ”I2rnqWywgNzL|;-@N<W +x9r}L??=WW xesHUhoE[!|Wf!S{<`x"}E9Vyy3Y/2gfx^JgKj\Z`Nq.&HR\XM+,,27V[tTnhv"&VI!b:n[RWL7AALIc:131N,r>Mx GJ:EIr%FN
-Ôp tÁ´¤1ð;7è^®,ƒÈ„­Åq¼Í˜qþ©Õ´¾Yj$?" 1S0-h4(um{6o09`t] /xHBMiW
-nK*m:(i
-iHZp0=h[J(n0$7eS\xcGc.*-6P:+k@)3JW~!#%skcKvT'a,GU_B",9D\{>w"wWg@6[^ùTi Ë`I[4=xTnXsQwz!8b:b:FVCAX Ir*_4E bgU$Y*sb7)&{B?u~,-C2Z@ebypkL
-#=T$0i@j)X#Z~[?(6fyj:%[@d:>Vi6F|*(a7>T\"LE
- WSY'h 8j. %V*oYq)Mh W4+]O] SQ*8F9Lt9Q'+;NNAs!yV5smk;Nl_ ("32V[*<.S1oFX&>$ ;^v)Cj?Az_H7y<<U9%\ycARiRrz
-?
-endobj
-3073 0 obj <<
-/Type /Page
-/Contents 3074 0 R
-/Resources 3072 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3071 0 R
->> endobj
-3075 0 obj <<
-/D [3073 0 R /XYZ 85.039 781.388 null]
->> endobj
-902 0 obj <<
-/D [3073 0 R /XYZ 85.039 310.691 null]
->> endobj
-3076 0 obj <<
-/D [3073 0 R /XYZ 85.039 292.022 null]
->> endobj
-906 0 obj <<
-/D [3073 0 R /XYZ 85.039 292.022 null]
->> endobj
-3077 0 obj <<
-/D [3073 0 R /XYZ 85.039 271.025 null]
->> endobj
-3078 0 obj <<
-/D [3073 0 R /XYZ 85.039 131.177 null]
->> endobj
-3079 0 obj <<
-/D [3073 0 R /XYZ 85.039 79.598 null]
->> endobj
-3072 0 obj <<
-/Font << /F62 1689 0 R /F41 2104 0 R /F56 1642 0 R /F15 1628 0 R /F35 1632 0 R /F65 2099 0 R /F70 2201 0 R /F18 2207 0 R /F20 1617 0 R /F38 2158 0 R >>
-/XObject << /Im1 2193 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3082 0 obj <<
-/Length 3723
-/Filter /FlateDecode
->>
-stream
-xZYsF~Ed\yJD0 X
-g:NW4~iwWAL8y?e'sung:v2Wg>%3 det;Sa*? S5r9;)IeN#'PpØwÖZ\ ZW%tZ4topgX*g~:+hj.@U
-E>xr }95(/jrRLOW[lfmPʋŠŽ¼‡–C2:20^v+aA.#Z|J$yM$^2y_e|tV4kc4b< Upw+n{FANcv?Rn(TFq|hnK$r
-hVQ?b`0#~\b74%k&V -N2xTX'lZ0 &@Ex A4c@ +K@#
-tI~=<e7.z$4vV5FUB&s@X|irnFizK4--wK$cj:CrKOvGP)j%vD`}C &Knih\No, H~TjG%qXpSQ?nlqe }eQ5LIy}5 +/OeczaBåU$ZpaP?pQ'pLhCMlG|QóLH.O>dc9 l!{"4PZZoT4-X"V2LiBKat7C%3±ÞÅ"kåBS[VA(&^\EJ,RVVYdQ%)=PU|{bF;J/#j2;kN; Ca}o0Z>s0` ^<N#me2IeRcH-
-t*4[qa; zE1;iY7|Nl
- zR3h&yK6R/g#1zzidn;Í;pœv`÷Cf[926Ixwl%BRYNi/+/ZK;.b $yyz/\/>6Zib|V<Gc2k^$ PW}q' g.L 9Cx_?IIrBDKTJ;c&!lDFj$B ?hwju<iCe,WsLdIBXhup'?gh9m0 bV:4>,AN%ZaOQN_1 KW$?{ <+C`@Q+p,u]cE"q,S3BFUn$Bv8LSh(I*^jphZhpx; RP .V W,5CMJr@X1m !#!(a ebG<M%=FFqzh]hjdv)=pL+SeNqYPW+8)*Dq ?K0b?r>J7I$;TcA~wv'qi 2 m+'us>@7oN_6h$TUs*W[d%Os1\¤bâᄯMy$ 7 Q%%$YkWB|<d#-*e3, 2
-a ^y$Ra@[hW'tCjQ3|8~L;n0ý„âW#6$:
- %NXX@3Pr0'++8HB-G
-b&FJ4}\f&j2xL;Sat'|0.wFc'MYP!ðÔÍÈo¾¢Ä˱7Ty}}I_W7?= ÎP<GF
-(AMCm={! HUNG/y]43#Jfb~QW"J
-@sUA _B2%k7=-fn$YC1? )|i(W2> sb/x<r e>{!19Q.l ?Ld"8:DuWt3: 43KT=qBDihH/@c&dN)/K4F,0aL)Y+lZl7!whx
-vJni%Vq-xx`*`RxV0X#
-Hh="] w0t>XONdVz+'VRd
-endobj
-3081 0 obj <<
-/Type /Page
-/Contents 3082 0 R
-/Resources 3080 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3071 0 R
->> endobj
-3083 0 obj <<
-/D [3081 0 R /XYZ 85.039 781.388 null]
->> endobj
-3084 0 obj <<
-/D [3081 0 R /XYZ 85.039 309.34 null]
->> endobj
-3085 0 obj <<
-/D [3081 0 R /XYZ 85.039 286.293 null]
->> endobj
-3086 0 obj <<
-/D [3081 0 R /XYZ 85.039 200.764 null]
->> endobj
-3087 0 obj <<
-/D [3081 0 R /XYZ 85.039 79.638 null]
->> endobj
-3080 0 obj <<
-/Font << /F62 1689 0 R /F15 1628 0 R /F41 2104 0 R /F65 2099 0 R /F35 1632 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3090 0 obj <<
-/Length 3146
-/Filter /FlateDecode
->>
-stream
-xr]_`iJl?@$$"
-sm'q/ww:vGY~_o?_(,7/0noq~Z1gs/>-^]
-?=sn96v$kD'tVS'’=«yl•>ì ÿÄ=¾=i§ÝEi8 KÜñ…
-Ô*QZ4*BU7Q%fMb:iYQzHR2!)=mr!&{3l
-b85`X3!A2
-'v=GaLK^(m&kCqW2&WfM~#<$p2x: NY(* 26*f}uGj 9fm2] '}2t
-Z'co`
-B`B7lanv {XV!-e)kIq(8s2[n7FfW[<kO[7IxdIbH(.=gkvM
-wK]JQgSIXvPQCr?f$L3$]!dM#B2ZV@L#oP=_a|/'cOe­aÛ­è~B2%=5 FN F<|81w
-WLs;{]M7<t]J<6
-cRmX
-z"%LAfEmF"RXfl\_Vo&TFZdb0. wa9vK>RByVG IZHeM,HHsYXaX%V8B/NN[Ru):9SK2%*!XfNI-=?n6f=RKg,\~wJKI#vuA#2ISX8
-I
-m1: j[~"&5oZhMi'@B8q`"?u"FvVv3]~w>ZbO'cUukZr<x;eOh~Ws L$g R?vcLiw2p-~l{*ty0XB95vFY$
-¬š´:ãÑF-Z#(W99-[io1~`7qO@$s1Bi$$cg7N[ Xr4|\ &M~U0%&y.d/"i (a[tDoJ>LXMP!bfy7 )^sA)=ð—û›R`DY++GIWMK%tnj3.mumfqw e56or{as  6~bO}pm~ P~2?1/HxA/^
-OmDh34c*!t?S7n|T8]=V4 ov;endstream
-endobj
-3089 0 obj <<
-/Type /Page
-/Contents 3090 0 R
-/Resources 3088 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3071 0 R
->> endobj
-3091 0 obj <<
-/D [3089 0 R /XYZ 85.039 781.388 null]
->> endobj
-3092 0 obj <<
-/D [3089 0 R /XYZ 85.039 761.463 null]
->> endobj
-3093 0 obj <<
-/D [3089 0 R /XYZ 85.039 743.296 null]
->> endobj
-910 0 obj <<
-/D [3089 0 R /XYZ 85.039 603.826 null]
->> endobj
-3094 0 obj <<
-/D [3089 0 R /XYZ 85.039 585.353 null]
->> endobj
-914 0 obj <<
-/D [3089 0 R /XYZ 85.039 283.436 null]
->> endobj
-3095 0 obj <<
-/D [3089 0 R /XYZ 85.039 262.235 null]
->> endobj
-3088 0 obj <<
-/Font << /F62 1689 0 R /F15 1628 0 R /F20 1617 0 R /F35 1632 0 R /F41 2104 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3098 0 obj <<
-/Length 1139
-/Filter /FlateDecode
->>
-stream
-xWKs8 Wjf{6NfD{,$~rdf&Lf"
-~ c&@vq>Or ˆ(xJ[`wiCf{od".)I]Cl~G`'daR k%2V-K 1g@;v<:.ISEa@egzxbR*[[17W .l km<;j#X<=|UrY1h "f pbR _k{RO&\'(qOLwOoY33B]#%i. w0 T^9)mJ"lV
-\@5R:V=EWzs.k$+(A,Hi:TU1R1q<9NPvRzA~e > QYr+h4tN]&nP`su{akn[D J^6
-}n^CGC74¼%D
-_"j[%}E-/x@RSa >zoZ2:#vcWek lj0|";^"œîŽœ&Žrí+7;¿¾Ku].wA:ev E(J ]RI BATGrkM=:­ÛMC_ O~'D&o]6}Tg6{#_:$/W~i.6?vendstream
-endobj
-3097 0 obj <<
-/Type /Page
-/Contents 3098 0 R
-/Resources 3096 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3071 0 R
->> endobj
-3099 0 obj <<
-/D [3097 0 R /XYZ 85.039 781.388 null]
->> endobj
-3096 0 obj <<
-/Font << /F62 1689 0 R /F70 2201 0 R /F18 2207 0 R /F41 2104 0 R /F15 1628 0 R /F35 1632 0 R >>
-/XObject << /Im1 2193 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3102 0 obj <<
-/Length 1930
-/Filter /FlateDecode
->>
-stream
-xkoF;K/5JpUwV9<v!N/IHr'[a$Ehq HXJ8KWkIGNl e8b6^2~FEOwoK7rss#> >p.>_a*o/9}qGql;<=u:TxMY} a~|sg.=:>
-e,(u7u
-~woBh/y>O{!%-Q9M3&w]K
-vP&&V^ O<
-U]C$* RlY%iBr64hh` ?++.LQF~4G*Ft8;?rem[
-_p<K )pt80u {6ZeP)ASS8
-MWO1j]6,Vf&y70DwXy$ +Nv`nZx|k6]3]r%qkYU?Un R"/[szTz{AUt}O.UIIk?Nxz kRX-a J]|AL'C; }qg@ .FÛþNZ9%/8psL;=i`WKgkE^7-$7(Tix~{=K#eõuüˆº0ˆÆM13D[ck$Tt=;XVqDn©¨8¶ë>äÞ?à"õ‘ði0&›{ú’KY[(MV2BiiêïGI>I9QwX6srCTCbRHs5D`9/oF.w[}ABoi,YJ_S
-endobj
-3101 0 obj <<
-/Type /Page
-/Contents 3102 0 R
-/Resources 3100 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3071 0 R
->> endobj
-3103 0 obj <<
-/D [3101 0 R /XYZ 85.039 781.388 null]
->> endobj
-3100 0 obj <<
-/Font << /F62 1689 0 R /F70 2201 0 R /F41 2104 0 R /F18 2207 0 R /F15 1628 0 R >>
-/XObject << /Im1 2193 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3106 0 obj <<
-/Length 2902
-/Filter /FlateDecode
->>
-stream
-xZKsFW|XeB
-TLnY@qi Ji7LT ]:5r(mX+
-s
-(azKG}0Ml}6N /|uR oZ,@7J
-C" ~99VW;aZ&>B LLc /"H<`y|Š;øa¼_(#3¬q‘ôi8ôå¯4i·X; C qMt9U$]]A8bKYlxJx[sXwcK;h>FOasU<qAi@PuCPmixsh0D<D +_l;*m\Ia,^oahy}.,[uM^J1pc59mv/ RvRy&hdQ65UOl4AXCAet0=CNHn_lhl!í (҃<Ó_ÇCmGzC?O]H#m<kt~ \|XUG
-RV
-;%f\s}^e>|W1,0\To
-uA@Uu:Tt!(|A,}(rB\/r=Xeisef)\(!Vfz9lExt88DCX4Fr?EQ b:Nj^iuxFæ€ÿVSlendstream
-endobj
-3105 0 obj <<
-/Type /Page
-/Contents 3106 0 R
-/Resources 3104 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3111 0 R
->> endobj
-3107 0 obj <<
-/D [3105 0 R /XYZ 85.039 781.388 null]
->> endobj
-918 0 obj <<
-/D [3105 0 R /XYZ 85.039 761.463 null]
->> endobj
-3108 0 obj <<
-/D [3105 0 R /XYZ 85.039 729.511 null]
->> endobj
-922 0 obj <<
-/D [3105 0 R /XYZ 85.039 549.916 null]
->> endobj
-3109 0 obj <<
-/D [3105 0 R /XYZ 85.039 528.055 null]
->> endobj
-926 0 obj <<
-/D [3105 0 R /XYZ 85.039 459.843 null]
->> endobj
-3110 0 obj <<
-/D [3105 0 R /XYZ 85.039 439.248 null]
->> endobj
-3104 0 obj <<
-/Font << /F62 1689 0 R /F20 1617 0 R /F15 1628 0 R /F65 2099 0 R /F41 2104 0 R /F70 2201 0 R /F18 2207 0 R /F35 1632 0 R >>
-/XObject << /Im1 2193 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3114 0 obj <<
-/Length 2998
-/Filter /FlateDecode
->>
-stream
-xrF]_7U9pm<@$DL
-BGsC_^q2[
-:YjfuM
-5^C\,k5^ϖÌÁíú|ŽAlZ v=ZK'_…Û€h‘ß>2…ÄÆ3œ¸±*ã]“—kF{ognY@ `-/9J 5tv&c7 c>VKx]>"c2@MGD[2)424mUi hhtR::og)H{
-b{`h?_P`,JC9x6Fa EVc4h((F$R$4.wM9I)rZ lVTCI
-T V )l%yoW2ZP\dxXKzpEbF~^66#:e~~5ZaN}@BD9iA5><*w0)cbc?)k^Y&j"^‡žò£g3µÀ‹…ejPqf;dw($nMG
-+(y6wj;6O#/Nvfkx2 2f\"A^8mQBU346jWRQl
-Zmeo(CaJ4WKMo*xh#vVYc#}
-w/\O
-xm]'+@8.d!4~iè¸I@{ïH{S5%-n!bQ$1˜'Å1ìÙ´ßíðà ,K|KRNmHE:9(a9}NN,!}Gk]NM]cp{fTOw$j8M|d7v3Sn;$]ps-F?l 9v@YNfHi$Z!rO$T)a &c =M3:Ig
-g X.GibFt/rRh4; ZVe"w
-#Y3MN|Q$ K:BIFXe[E;,l~;
-endobj
-3113 0 obj <<
-/Type /Page
-/Contents 3114 0 R
-/Resources 3112 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3111 0 R
->> endobj
-3115 0 obj <<
-/D [3113 0 R /XYZ 85.039 781.388 null]
->> endobj
-930 0 obj <<
-/D [3113 0 R /XYZ 85.039 761.463 null]
->> endobj
-3116 0 obj <<
-/D [3113 0 R /XYZ 85.039 743.459 null]
->> endobj
-934 0 obj <<
-/D [3113 0 R /XYZ 85.039 658.326 null]
->> endobj
-3117 0 obj <<
-/D [3113 0 R /XYZ 85.039 639.853 null]
->> endobj
-938 0 obj <<
-/D [3113 0 R /XYZ 85.039 581.213 null]
->> endobj
-3118 0 obj <<
-/D [3113 0 R /XYZ 85.039 563.346 null]
->> endobj
-942 0 obj <<
-/D [3113 0 R /XYZ 85.039 422.842 null]
->> endobj
-3119 0 obj <<
-/D [3113 0 R /XYZ 85.039 393.438 null]
->> endobj
-946 0 obj <<
-/D [3113 0 R /XYZ 85.039 126.341 null]
->> endobj
-3120 0 obj <<
-/D [3113 0 R /XYZ 85.039 96.139 null]
->> endobj
-3112 0 obj <<
-/Font << /F62 1689 0 R /F20 1617 0 R /F15 1628 0 R /F41 2104 0 R /F70 2201 0 R /F18 2207 0 R >>
-/XObject << /Im1 2193 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3123 0 obj <<
-/Length 3431
-/Filter /FlateDecode
->>
-stream
-xZYoF~%@Hv.[hd-w=
-E.C|Vth .9Bj9h{`aHv<os/ FZw&+e\9"kJ>AhK'j[j-$--pSA$5 2f'(gd#FexOh|sW:i24, p{v0 !Sf ]M' I<Kou2iR(H&)C;{Lw8t ?rUk$þ ;„§9ԍ¢U(G}N>R,&xu+Kp%^,U]gv#"m8#DC  S1TB0A@"h|+M`Gv}d%8cShsq`<Qh;Q44iM
-s|*gRl>!n )kV1D]b A NX|vyUg27tlo ]Q6D'Hd5 FE'GsOtPu.&Y$@ nk|h'*#ph\uCT BxI*.3h)fv
-8SSIQ-I,Rz[wu?|a[#JyYYTJ&m4bz3|Ud3< D/FYr#WR'1JV5}3mgFE$TyZ@A=q"8$0
-^q+eO6/&Ayj
-S,
-
-<EB.q+r<AIm'r V'~j_nJuU0D ~F( |w_/*-f@} e&&` } N2
-h"[paOrrn
-mT&'bdu=m/C;mN|.3o F|RZQqR/DuI^'pi =h_u;x4EO7?L8Z`dQs%c/FM%/RcY Hfw4,L6}AW"~h)J)fwO40krT2z}4t&g4h'5wNk$7Q S:^^KtwJbK0&<9|52ZoNpT S#_p2fb>; 1CSGS/f`)8~\o)ZR2i%/{>D"VV+:JH;R9|/TO7ULzendstream
-endobj
-3122 0 obj <<
-/Type /Page
-/Contents 3123 0 R
-/Resources 3121 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3111 0 R
->> endobj
-3124 0 obj <<
-/D [3122 0 R /XYZ 85.039 781.388 null]
->> endobj
-950 0 obj <<
-/D [3122 0 R /XYZ 85.039 531.337 null]
->> endobj
-3125 0 obj <<
-/D [3122 0 R /XYZ 85.039 509.575 null]
->> endobj
-954 0 obj <<
-/D [3122 0 R /XYZ 85.039 410.893 null]
->> endobj
-3126 0 obj <<
-/D [3122 0 R /XYZ 85.039 389.032 null]
->> endobj
-958 0 obj <<
-/D [3122 0 R /XYZ 85.039 239.143 null]
->> endobj
-3127 0 obj <<
-/D [3122 0 R /XYZ 85.039 217.942 null]
->> endobj
-3121 0 obj <<
-/Font << /F62 1689 0 R /F15 1628 0 R /F70 2201 0 R /F18 2207 0 R /F20 1617 0 R /F38 2158 0 R /F35 1632 0 R /F41 2104 0 R >>
-/XObject << /Im1 2193 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3130 0 obj <<
-/Length 3180
-/Filter /FlateDecode
->>
-stream
-xkoFQ D[
-lz'Z$9ùî@ DpT8o#stA O'GckH'hH~?]@=<2 wcw
-Uxa$=N,,[A]9Qsc#H+t YwUe*7(W(49N} NegG&7_?TEy:^Ft{nTN
-63&"["rj!FxUb J9`4`tvDcG6=qM~GNox&k
-8T4
-iY
-'om0G'rWu$%ceY6/x;DEu^ehP90Ek%@~p[Pn&o?=
-0{D}RC=j*z5Hitb0b_us}g+Z UO PQqH.YgYH
-T#F
-[
-fF|(< pGlE+qn/Z!( 
-=rBd<J!;G h4wO]&KTu9\5nap`g0& [EH\iDlЭ›mÊUQg\EygmWCwdsR\ ;x7w
-`m<QY5D/">SnFdxl!#0ž´, 
-€‘´)±kN]'aEKXx!ETBq72T=->@^"'>g}}fp[0 65UOUH
-pt}2erAK5vMP!+ fx5Z"VNLU(1&b'@}$j_% )N8c=KEI%ed vxW>H/=UtNp9—ï.Φ-pypš-Ù}WQt"ka&HinJo)H)`7 i!nU|zRzq: 7p$Zh("3q:
-VKOY=p3'#!?py9tŠc)P| 0@`<M*[)Zð*ÕãQ*d/9o9H)J#6e()I[Œ2ÃˆFIc|],@g! /bD}gj' 9>0OviCb5nmLuk'0i['7
-[U>JCTM8 2m= XF=O'hqZ%AS\KmD^@ QD= zg-10 Ht=l 8LO/ :9`Z6VG8kta@Ea!];@"5Y-t"{L#H= vM!mk6GaKp.7HL7_~/>XsV.2!F; 2
-x)UQ {Y|;;R'qLUp?3-t3`#_VCkZg^wk|@c>i,wc1kro#VXPUv_pj2WJH8mqpo_v)?l&BQ|JS|S^sQDfT_O \xjR@
-endobj
-3129 0 obj <<
-/Type /Page
-/Contents 3130 0 R
-/Resources 3128 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3111 0 R
->> endobj
-3131 0 obj <<
-/D [3129 0 R /XYZ 85.039 781.388 null]
->> endobj
-962 0 obj <<
-/D [3129 0 R /XYZ 85.039 719.568 null]
->> endobj
-3132 0 obj <<
-/D [3129 0 R /XYZ 85.039 700.697 null]
->> endobj
-3133 0 obj <<
-/D [3129 0 R /XYZ 85.039 482.087 null]
->> endobj
-3134 0 obj <<
-/D [3129 0 R /XYZ 85.039 380.398 null]
->> endobj
-3135 0 obj <<
-/D [3129 0 R /XYZ 85.039 328.662 null]
->> endobj
-3136 0 obj <<
-/D [3129 0 R /XYZ 85.039 279.048 null]
->> endobj
-3128 0 obj <<
-/Font << /F62 1689 0 R /F15 1628 0 R /F20 1617 0 R /F35 1632 0 R /F41 2104 0 R /F65 2099 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3139 0 obj <<
-/Length 1713
-/Filter /FlateDecode
->>
-stream
-xnHHolB%ij51H}lOCeBa0'_MO Z!EmEv_e48.&HJ95A88 `-#1-N8z?zGo
-4l 7_*^1+Z~hN\3[VY|\
-E'Fy#q]oI WD44O+r'Wk,"4twC|1 z3 qx=E-02dJi^$jE8i4G'!(am3Jo )xsGq!;=BEUv]
-k2acŽ;Çw‡ÃÆUT+EQVnb}`)'eGrV
-RuVVw2`_lWFP_\b
-q6JlHF6YMft3T5/mÊý‹í©¨³ëòd;_pE 72
-n$2@J,Jer"Mrm(YS@qOs%madb]*@@C @c&*Ib v#KM#94acX;Xfp@#.Mzv7M_V@bp`g!ZUhCLD_ByTK(g{aP~H5JCxkPJ81
-7_;s{Hm#CMFVkRExsE/-u~ endstream
-endobj
-3138 0 obj <<
-/Type /Page
-/Contents 3139 0 R
-/Resources 3137 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3111 0 R
->> endobj
-3140 0 obj <<
-/D [3138 0 R /XYZ 85.039 781.388 null]
->> endobj
-3137 0 obj <<
-/Font << /F62 1689 0 R /F15 1628 0 R /F35 1632 0 R /F41 2104 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3143 0 obj <<
-/Length 2900
-/Filter /FlateDecode
->>
-stream
-xZ[s~xOiKcL$PJR?{HJ9g:1b,a1dq<gd #&
-5r `9)`zts7Z|ySZTw^e }Y<&3An29YdtDW&Noe:LE|L{Z;ZwvD
-'+U4f~-'*,1& +{0tRO<6{'l. Xv$}?
-[4:i$xz+&W4w%U -% ey+79= hW={j<R+[nZ~ 'TI =y­œ,­ˆJ $-b"oCE_:ha$3 ERt.4tXV3<[YBKiX.f. #¦hH{3qHQOLj^$-Fi%B6JAzmHV.|U+ w|jd)NX?5rr{:Ö{ª^80l8ÝbYSu¦ÁN`42o2"4#íhèÛÔÒpñڐFt %5y3DW-
-.EUXik2]fNE{BudF=)wzej
-n5zc AAt;P.xu^AHP)
-&9÷±‹çÒnãBJ%C.!BkKbDf,n
-FDsxJgmN1
-(y,m mA>uu.S45S~ l-$,]KY45bVxZt5
-R_q"!4JB'\`XVjkbHYAlVqE(wb4 QG7+QfNXOGwuU.'3hh803Do `Q*:PgnPoJ{ wcJ7_9HJF^-prcAP/'Zn8Q6kR(; /*z2XIjkfVh5sun ik#oo CF.7]Y#'B47(<d&o[Ab
-j@ 4d /
-4!#LY4{k&5#GtR@o M5?{=De&f" X,KZxdYkX6! |r WA|ZU,b@,VzS`D*$U1UqoCEHT b-¹8}H"FdDxTEeW8\-De ^<xy.ef
-RaBLQT S[01x %W
-endstream
-endobj
-3142 0 obj <<
-/Type /Page
-/Contents 3143 0 R
-/Resources 3141 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3111 0 R
->> endobj
-3144 0 obj <<
-/D [3142 0 R /XYZ 85.039 781.388 null]
->> endobj
-966 0 obj <<
-/D [3142 0 R /XYZ 85.039 667.608 null]
->> endobj
-3145 0 obj <<
-/D [3142 0 R /XYZ 85.039 643.626 null]
->> endobj
-3141 0 obj <<
-/Font << /F62 1689 0 R /F35 1632 0 R /F20 1617 0 R /F70 2201 0 R /F18 2207 0 R /F15 1628 0 R /F41 2104 0 R >>
-/XObject << /Im1 2193 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3148 0 obj <<
-/Length 1851
-/Filter /FlateDecode
->>
-stream
-xio6Q` -Kkdfl!ITIa "Qt=8r` ;_w Wa1nzA?:o/~Wxug„2[|rίÏîfãû^?Gn?'{7s ;Fs{n&gt8¤›ÌzÎ~êŒg{’ôC7(OzHSsQsh]w(p03\saXe?p!  G `
-âÄw
-ƒv|NOv30).;~`(0
-XFHQs'Yf1F\z0{Aqe`TQ0v/VB
-%YyhT<N`qwk]žê‡
-nuƒµÉxöáöêvb%s $N6q<XT?ejw#=v9H@< '<?sEK+H%"V'.+ PMEsX:=$&sYYBjy;dKQt/GnFTsO",;94~fpD4on
-F=L+ =c¿€:­ã1/ª]x‹Ø¡
-H:x?8k
-'Dq7EN:5I.
-GqJ$s642*f4&gT eE~6BZh2N5^ML{cZm6H+wwT9}np
-3A!79]B I%L7:.3*2IUdvy+! U<9EW^Ê''·Ñ°…t‡Ð$¾†ÄËçÄ®' SQ5^6V[6jwc|MS* =/2Z/N7Jic'=>vmz)sL ]QY,ED[@XhvS-f67;T`T</mK*_8;k`Ks*/eUWo.å ¯ìŠ6˜¬¤å›qƒÃ§^4pè* )—Jo`ho*6BTDIq:M6U7B~4 A7d!ka%^5*%@/?Uj 5g:gc"ç+B]m/#=?:wK!M&NK?+\^R4F{:3~+'i|jD
-}pkRdWv$-|4@^Z zwSPhp]^5JcTcemfujT-zc&<\M2Znz0G
-endobj
-3147 0 obj <<
-/Type /Page
-/Contents 3148 0 R
-/Resources 3146 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3150 0 R
->> endobj
-3149 0 obj <<
-/D [3147 0 R /XYZ 85.039 781.388 null]
->> endobj
-3146 0 obj <<
-/Font << /F62 1689 0 R /F41 2104 0 R /F15 1628 0 R /F35 1632 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3153 0 obj <<
-/Length 1254
-/Filter /FlateDecode
->>
-stream
-xVmo8 _a(W:>eK^nWlnbu4HQv{_A")I >Ü=›‰ÈBn043sZ|{WcpfG,2g%_}<Z}!CAh~Z}s$r? 1L&=Æ­›ô]Ûõ^ågïëwf¤pۏ=f‹(4v°f6"cÕs=a{®Ðtћõþl¬ÐžkV}E6 #XqB4 d6~Nq?
-u^^}írŸ#‘rôL+++9EWUN)&•Æ–Ôç*¼)QIT%QTP8\e!YzJfY++$ g!/hPV2#K fQ
-0\4q@h)n!./
-?ammd)":Yo{&O* (DQA "`? ()Tv| fxv 0„ð^Y<!ani2hDP}osp%WgJnCvz-u*ruu+XTOhdOR]s[(
-k% !x
-endobj
-3152 0 obj <<
-/Type /Page
-/Contents 3153 0 R
-/Resources 3151 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3150 0 R
->> endobj
-3154 0 obj <<
-/D [3152 0 R /XYZ 85.039 781.388 null]
->> endobj
-3151 0 obj <<
-/Font << /F62 1689 0 R /F35 1632 0 R /F15 1628 0 R /F65 2099 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3157 0 obj <<
-/Length 3106
-/Filter /FlateDecode
->>
-stream
-xZKs m*Dg';Njh-u EzIjlIJ
-My0W r:(Fg1(}#cgX{ V5o%]vr«`à -iŸ¹FDJ~RAwcj2GLr>?,6jg)YCXUM& i1/Jw4[]moNmJw!ggUuFwY"\/9`f<75b52Pyn]y}3Q
-3Ex;$
-K"|d^üuþÓpú)ŸÂô—‡Å2 "ï›e;“è@c)(UDI<<Qo2 d$9<W _7Y8m-!'t A#the3ssH.t/~*MX`8l| &cS@;uhix7Nuz{gi<j', =.*R(e7U%SBJsfUW{d<]G
-mUs-
-sPE`ACQq@C
-&&'s<S5K#v>Ez:`
-,s| D< p,M8
-IjH!$K|Z_8Q5RhDev+qB Uf[
-h0U& r"Tov
-dyPfsu[\AT||+l`s1 bP#G. kq:B]cc'=;ctSj49f@WS5hB;lU+_>9yg?voÔ72ñ®qó1Àâ"v{!"±̪ågÝI99$n#jz Lc:(G}*!@: bB\Wy
-Y`d'vhw'<8Sk9-x ;98Vppr
-G^8%>[R{g"2_HERcqcI8s8;"0ZtGu 5N?^uý\io¯Ö®/“|uA!yVa' e
-gWt i:`F
-j%evOv]K{K <=":;ZX_E~PD;I3Z(PAZ0kNzOj_25^u87'#Zic$fQJ0d9k4$4vbRnAh_?^ _6=<n{ Msopj<w'p|v^D J <XV=]5ki}"m#E'UFL=x3[E!Db }J_~ b.$I<k$ P y?+HJ02s- Q;4R Qg4 .yDbkY!q:h ='"EZ.xu>%& GnIpk
-q6n)nk9l7zsXS =l
-zEpW< .U-DQbHR'q!sTDZk1BEßÈé+–Èb&²ÚV`{qk*3j8 'g-4O#\ !f7MA|2Etv,S>7E:<-VFBZH8o"wClmV~7T#F$C7>{6+EqKB'jd[J4IPEa
-endobj
-3156 0 obj <<
-/Type /Page
-/Contents 3157 0 R
-/Resources 3155 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3150 0 R
->> endobj
-3158 0 obj <<
-/D [3156 0 R /XYZ 85.039 781.388 null]
->> endobj
-970 0 obj <<
-/D [3156 0 R /XYZ 85.039 761.463 null]
->> endobj
-3159 0 obj <<
-/D [3156 0 R /XYZ 85.039 667.044 null]
->> endobj
-974 0 obj <<
-/D [3156 0 R /XYZ 85.039 573.327 null]
->> endobj
-3160 0 obj <<
-/D [3156 0 R /XYZ 85.039 541.802 null]
->> endobj
-3155 0 obj <<
-/Font << /F20 1617 0 R /F15 1628 0 R /F65 2099 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3163 0 obj <<
-/Length 3027
-/Filter /FlateDecode
->>
-stream
-xZ[oF~ ";
-@Z-n(RKRQ3dy/0z~s55K# Y*7Hjs`/JVx-/~3dY|2wH_tusB9ws?u/y_)Lr{|?c"t8@6y
-©ð\8ã]'.»Ð+p‰ÌNOXRQ.>n\CVt_q)y9nIP!vbZn=
-vms(fw5|FS} Pr]vs:yJ{@5~xre,X%pl;0+M^5cp='IMFm/b7MY-*75:r2EaZ
-W9Z'{W@6LSgcѫG|#v:c
-YzT^t>i;<< A@BRZuF/)V(6hhH=am_ tnOx|?,+ [8k?S/=YVt;vqkWf#J,}wB4X
-!/4PPrpG[ _>p3UU
-yb
-m8\p6-;{ylxl#BI#BgRw_QVeza(HJYWK%Fyh>h)uJ&v-9I&%Bgc]$4"F^ q$$w&bCzZloy0cSr9^CHLx;6[$g+"_hGGYf1xl F*Q>RM:crI"JN\d'@5%Q!
-^HpqB<isS2#%6FPxEh#,F$| t6)yP L}5`,0]]B-o4fOwmT'¶g·´°=q­‘ äê—Á¡—êÔ8„H;}j! c1
-Y  LP:8*3RDO,QQ@jm*T\m#R5vI
-JsH;bKvrj8Fu13 xH)j,u|
-%A4=F7X -|g~?n*@8@8&l{9dL4%8#GNCEl:o`yFe8/ fT*TERxc(: UVTO*sh 0bxDvCUSf.Jctg]Rv[W'.'
-6U]Q)A ajgZ#nHs#[N-EL2'(yG+^5P}[tVY_.:H}`QWOM;UvZD/YF+
-a}g2|,pxi
-endobj
-3162 0 obj <<
-/Type /Page
-/Contents 3163 0 R
-/Resources 3161 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3150 0 R
->> endobj
-3164 0 obj <<
-/D [3162 0 R /XYZ 85.039 781.388 null]
->> endobj
-978 0 obj <<
-/D [3162 0 R /XYZ 85.039 761.463 null]
->> endobj
-3165 0 obj <<
-/D [3162 0 R /XYZ 85.039 736.911 null]
->> endobj
-982 0 obj <<
-/D [3162 0 R /XYZ 85.039 709.271 null]
->> endobj
-3166 0 obj <<
-/D [3162 0 R /XYZ 85.039 687.41 null]
->> endobj
-986 0 obj <<
-/D [3162 0 R /XYZ 85.039 537.42 null]
->> endobj
-3167 0 obj <<
-/D [3162 0 R /XYZ 85.039 502.217 null]
->> endobj
-990 0 obj <<
-/D [3162 0 R /XYZ 85.039 394.428 null]
->> endobj
-3168 0 obj <<
-/D [3162 0 R /XYZ 85.039 362.902 null]
->> endobj
-994 0 obj <<
-/D [3162 0 R /XYZ 85.039 242.539 null]
->> endobj
-3169 0 obj <<
-/D [3162 0 R /XYZ 85.039 219.221 null]
->> endobj
-3161 0 obj <<
-/Font << /F62 1689 0 R /F20 1617 0 R /F15 1628 0 R /F35 1632 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3172 0 obj <<
-/Length 3177
-/Filter /FlateDecode
->>
-stream
-xZ[s~!xyS^&O$OZ%6T\7D5L `?5Y+f0gNCw;qXow>\.<Tb_.(ovu{\_.”õáҍ­û՚I{af?^._tz C1>]3@.K3[%l*<xa
-l;}sjLy7ck>eJWo-6DV?KiX*tBa)m[>0 i>U,
-<r[IHl>A{y|$>h9 Z8m'%o}
-Ga8Lt 3!Z/4J2\%H =}8!v }R?x&3>% |RV*yM"M<'+dP*&`<E?"W.Sp\Xn' hyc+gW4\n>6pjP(x,nT}fO^<R.= 7keuA.;nuV|rb8Z-m_7|q`[LL_`G,Y2'@:eu5Hc}jxwfS'lm{D|} ^|?wHYno#l^4UaxdE' !m2&7.)RL[V]oo X(v=v ^r,k2CS&I|k'"}toMK` VYx,
-
-`;f/z>4`fryT nZMs*#_K@1 *o>cmsv6 .c~j+J9u!sON]pYl
-> l:F"XHtq$rwOmWi$I.-2>;Pjr 1@zY DWW)qñLL/ K,j"g/0 m yT6kz&zalOY
- .b z7+]IpkQ)Dz d$  4T3'%? 8,lQ$>4Ispf#F`hT94zWrA_&-øƉºGg2iA^&m
-Lx*y0
-h[i(tpRp!x,xSZ(|_*Rt/f| =6U.3l;Ht,Fq.sydu\1U?pTjK.r Z>`}\I
-CYQ7knF
-`I`>
-d=>e%jrKl e:oTXh F R1b`U(f jH8PfBU$Wc
-n-6
-F}/LQqm'W q _O8^d-g T! Hdhendstream
-endobj
-3171 0 obj <<
-/Type /Page
-/Contents 3172 0 R
-/Resources 3170 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3150 0 R
->> endobj
-3173 0 obj <<
-/D [3171 0 R /XYZ 85.039 781.388 null]
->> endobj
-998 0 obj <<
-/D [3171 0 R /XYZ 85.039 529.88 null]
->> endobj
-3174 0 obj <<
-/D [3171 0 R /XYZ 85.039 511.008 null]
->> endobj
-3170 0 obj <<
-/Font << /F62 1689 0 R /F15 1628 0 R /F20 1617 0 R /F35 1632 0 R /F70 2201 0 R /F18 2207 0 R >>
-/XObject << /Im1 2193 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3177 0 obj <<
-/Length 2331
-/Filter /FlateDecode
->>
-stream
-xYYF~_! ,d7s-,<yJ/G4Dx<F#IQ=HBSf'd)Vy[
-*73au9 vX-Vv> EQ;|rs4r~|w._N]a-vvRyN#BVuj>!*g[
-;ktYQ5G(W+&kpj_JGW&amiie  $U#ZAe;Kd;U";]Vb
-^eoC M&)hwqp6E!
-I/| "^w`YP5 ")QE9v:~d~>va+DfCn
-D>ZW~6Q6eKzdK!iS
-"PBgK
-s)-}?!p +K{
-K+]rn&nb #yt!Rj >{{^O ?lBi31Rn~,$;#Cj}}.B4{u&.ox-5?y2Hcj@Dw*4nh"]}/]@~'k=s_1f(RF(YY&X+58KÐéQBd_~@tP(G@A>(8}Q^1Z)B|W"0tI9
-6E'B/,Ja+Um'(rcCALN|>-Zj(vAL&[)Mg}7{M [VHt |j=5ynM5dSvKv 6)Kw5i11&yRl,<5NÛë¾kqS` `7.TW$^Jg_+.u
-TO) *
-A}W;@M!HZ 2+[~=?t2&dH-vwn.~OB;7K<t,+9#SRtHo|Kt+]/(,mjXt8;Drlo)#Y
-u[,p0()aRd)\eQ6|E ~Vc\e\)
-G/hxMyUIV)?
-n&?7 endstream
-endobj
-3176 0 obj <<
-/Type /Page
-/Contents 3177 0 R
-/Resources 3175 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3150 0 R
->> endobj
-3178 0 obj <<
-/D [3176 0 R /XYZ 85.039 781.388 null]
->> endobj
-1002 0 obj <<
-/D [3176 0 R /XYZ 85.039 761.463 null]
->> endobj
-3179 0 obj <<
-/D [3176 0 R /XYZ 85.039 642.137 null]
->> endobj
-1006 0 obj <<
-/D [3176 0 R /XYZ 85.039 642.137 null]
->> endobj
-3180 0 obj <<
-/D [3176 0 R /XYZ 85.039 617.419 null]
->> endobj
-3175 0 obj <<
-/Font << /F20 1617 0 R /F15 1628 0 R /F35 1632 0 R /F56 1642 0 R /F70 2201 0 R /F18 2207 0 R >>
-/XObject << /Im1 2193 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3183 0 obj <<
-/Length 2143
-/Filter /FlateDecode
->>
-stream
-xY6^Q8H
-\6M%C[h^ olk"L<3I
-&hM,`$& jO7>1klb 4h4rymtaumb:k7ba
-<1vP(pa<24 "L; +=h&.t)7gUkMEK[cAf7}n\, zZp(ÃóGhle
- RnXeсdž–œ&”ڏ§UY+8P @(be(+Bz kQUrlmS>^4h[7%VexQnO"PKh(k20P1x8AOk,"V@]3VO0my]9/$=A8fQ<zSvv8=6sLC\%x@a C=s4 K-O*GM}FcgXv&:Qu9D>Keog T08344[zâX[HC/XuK.-e‡,ñi÷(/T>7$vp78,NGv4TZ%xG"&;RE,MfaÀ‘Ë”~öæÜ­1ˆR=
-"}hO,;!
-m!}pL6c'P-QC7Moœ:`ÿ7Òð0Œƒ¾¦
-/€ë;iÏÙ(¼æRen;{dsyM-U^NG, #wF 8#6ijk0F&h"Qm E9UK4I|n\ z^| 3 Jh\JOtcRe*~Xu@k+
-endobj
-3182 0 obj <<
-/Type /Page
-/Contents 3183 0 R
-/Resources 3181 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3185 0 R
->> endobj
-3184 0 obj <<
-/D [3182 0 R /XYZ 85.039 781.388 null]
->> endobj
-3181 0 obj <<
-/Font << /F62 1689 0 R /F35 1632 0 R /F15 1628 0 R /F56 1642 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3188 0 obj <<
-/Length 2658
-/Filter /FlateDecode
->>
-stream
-xYYoH~ 47wO v<`"))*<o]MRc0Guuu_U?|vE)EZ-9SB(~Z ??_^_m-0eW<7T2q3^/x' ^^xv?yI5/~MZ4gXzk^&3Ud}</{9-7-qWžó¼jFg (3|6sv &M-M'p|T:gk,LvgE7Os9i'mEJ3lDCu+Z|dxZMm`0(kevM]B
-L'H*lRMydTFZE-{køDFNt4 bd#fNl
-WgI2X5E 3wx@:p°¬H [@Jz`=vEthme`{q >EvMMUBs);*vy
-  B(AB{8##C@2aEx8dEa3lJ}
-#uI$Fz}O LIH
-y}V-Gq1]!;Rpv> jbE@ t*:¢J5H5MyHUh.xEVBe#wes=u,&Du8b*Ap,hq MrDPJXCf!bvUqZ+:{,C_&&;%SpRj?vg9X D=#¯ÅÑ! Ák›T{(3mpuQ] [t{Nh`Uh0O!S )J9P3%?aZQ-r93wX0"Q2ulO0
-N m0$ ` aU FU@x}AubWVDbA?v4%Rdv\!~@f 1N32#`?]>pLPr?M@79OS)qC$j],LcT@Mfry&V*&z`BgG@@CY n` 06BJ%N l&4!eUA]u<CEc)X2| q%Q.T "03 Po>#d=$@ m4<M'.XHmYUOoFN
-Y<nB ^&^`" rX\M>NJZ &Y 0@8AAJ
-ö;Y?
-+@E3F
-7[x
-@=S)K}?(:
-b8?Oqendstream
-endobj
-3187 0 obj <<
-/Type /Page
-/Contents 3188 0 R
-/Resources 3186 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3185 0 R
-/Annots [ 3191 0 R 3192 0 R ]
->> endobj
-3191 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [294.66 181.829 400.604 193.518]
-/Subtype/Link/A<</Type/Action/S/URI/URI(file:smb.conf.5.html#OBEYPAMRESTRICTIONS)>>
->> endobj
-3192 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [366.309 100.534 485.694 112.223]
-/Subtype/Link/A<</Type/Action/S/URI/URI(file:smb.conf.5.html#ENCRYPTPASSWORDS)>>
->> endobj
-3189 0 obj <<
-/D [3187 0 R /XYZ 85.039 781.388 null]
->> endobj
-1010 0 obj <<
-/D [3187 0 R /XYZ 85.039 214.839 null]
->> endobj
-3190 0 obj <<
-/D [3187 0 R /XYZ 85.039 196.171 null]
->> endobj
-3186 0 obj <<
-/Font << /F62 1689 0 R /F35 1632 0 R /F15 1628 0 R /F70 2201 0 R /F18 2207 0 R /F20 1617 0 R /F56 1642 0 R >>
-/XObject << /Im1 2193 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3195 0 obj <<
-/Length 2220
-/Filter /FlateDecode
->>
-stream
-xX[o~%yE*q ]#rDqMrXV9sfF7iQAsrsQ`;tFG .A
-'\EC{¸Ž=u¦ƒùRgw_#-0a4f73Guu;t/x:.^d*>~]_#mG@`<gz;g;v\-_At4at:({~vHS=>/
-
-y%0^X"G ?_gRE+aU <|F$\2,
-[QIO,[^cX'RNHuBH,$1+3KV+o%:\$2V8uLqo
-sz|
-[|ql1m4Ds[JJ/c"GPV+;+GPJ$7.t)f97&[1Qj4yZ08tAZ;w\ 3>jeIN-
-{yWox7*]{qAg=.|#=*2< D aoSg
-TF
--b=I_H\o84]+N)y]g ?H{V,Tg[v8,~,Pmco.\N)c32[QS
-D
-PNL:3*m}SnmElc4HzPQ
-kYr [laPmx +dPgt8Y+'@N\T9 m7UmgeRC}Q
-endobj
-3194 0 obj <<
-/Type /Page
-/Contents 3195 0 R
-/Resources 3193 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3185 0 R
->> endobj
-3196 0 obj <<
-/D [3194 0 R /XYZ 85.039 781.388 null]
->> endobj
-1014 0 obj <<
-/D [3194 0 R /XYZ 85.039 761.463 null]
->> endobj
-3197 0 obj <<
-/D [3194 0 R /XYZ 85.039 741.134 null]
->> endobj
-3193 0 obj <<
-/Font << /F62 1689 0 R /F20 1617 0 R /F15 1628 0 R /F35 1632 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3200 0 obj <<
-/Length 1719
-/Filter /FlateDecode
->>
-stream
-xXnF}W(
-P@.AuPASe}$vi r/33g %@
-;q> Xy3z'\m6zj,-ZxvE{fOi,11}?0&c7?lbJDI`òÔÉÞénys
-ªU]MIUBj~&2)XqT,&W),~-6i y5
-m7P 6- D
-Z87p>p9  >6 *{$&37B>`E~'B0*#QN èá›ÎJ8R$7=?k)yp;&":!/e nO:;m<e@skßÔ|}d¼«¶b
-LeBo6}tDf7?SxbuT~eY8:<JjI2o
-endobj
-3199 0 obj <<
-/Type /Page
-/Contents 3200 0 R
-/Resources 3198 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3185 0 R
->> endobj
-3201 0 obj <<
-/D [3199 0 R /XYZ 85.039 781.388 null]
->> endobj
-1018 0 obj <<
-/D [3199 0 R /XYZ 85.039 612.769 null]
->> endobj
-3202 0 obj <<
-/D [3199 0 R /XYZ 85.039 592.174 null]
->> endobj
-1022 0 obj <<
-/D [3199 0 R /XYZ 85.039 363.837 null]
->> endobj
-3203 0 obj <<
-/D [3199 0 R /XYZ 85.039 341.121 null]
->> endobj
-3198 0 obj <<
-/Font << /F62 1689 0 R /F35 1632 0 R /F15 1628 0 R /F20 1617 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3206 0 obj <<
-/Length 1821
-/Filter /FlateDecode
->>
-stream
-xXYo8~0P,*":o6mf÷aÑ-ɶ®$×éþúƒRXuv\~Z'kZ20e |` @y9}<{(,3tN<qjr5=}?K) 2GcQ ^=~wyv .NGca ã©Žq6²ãp|z9}?yûvHo^\N)9}c!M ~(}ON‹À´„ž}|ül cðþõÀ2e 70¶L|Gy6a3]=ci8 nzB &8d ªYWh< UOa9 %RM
-e0@*8hv`:}hlQ|} =jMHFe>3X^mbnTX) cBB(FEaiAh"95Ohs$l*}\j aE4nW&5<T**tK~ e`hu}\!wmGm Pzztb
-:(9:9#{8i}b,LgK7 ty
-<;0MHDh SwS:cswuSu2Y#h`Ycnz1]by!@)=v) .^Y#?z'JJ;[{ E[@R
-3]myK'4}D&k's(""M :Z fp-ˆ¿´YZq,2] 8GWSCud;2x OCQpKOfUR+m /&A' xSCi$s:M/0 f<),_Q!6?&V¯æªP d`q kN o#t( T)})zCWmkaf#;D{qVOk%kMQBoAUZ kU.# m+zj,ghl`E tg\\©Š~ ˆÚÊT;p>&CONVLFO\EH. N7/qFT)Z$jRm^Y=I
-endobj
-3205 0 obj <<
-/Type /Page
-/Contents 3206 0 R
-/Resources 3204 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3185 0 R
->> endobj
-3207 0 obj <<
-/D [3205 0 R /XYZ 85.039 781.388 null]
->> endobj
-1026 0 obj <<
-/D [3205 0 R /XYZ 85.039 761.463 null]
->> endobj
-3208 0 obj <<
-/D [3205 0 R /XYZ 85.039 741.337 null]
->> endobj
-1030 0 obj <<
-/D [3205 0 R /XYZ 85.039 513 null]
->> endobj
-3209 0 obj <<
-/D [3205 0 R /XYZ 85.039 490.285 null]
->> endobj
-1034 0 obj <<
-/D [3205 0 R /XYZ 85.039 260.773 null]
->> endobj
-3210 0 obj <<
-/D [3205 0 R /XYZ 85.039 232.037 null]
->> endobj
-3204 0 obj <<
-/Font << /F62 1689 0 R /F20 1617 0 R /F15 1628 0 R /F35 1632 0 R /F56 1642 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3213 0 obj <<
-/Length 2094
-/Filter /FlateDecode
->>
-stream
-xYKF+8ET*=6nã9©h´#$,‰¡ù÷›/ Û‡£ªGfWY?5dq<3o;fJ(]0\w #|nD?9rKc<K/ tS.cKF//<|T/Il+7OMV0Ac5K91BV2IVWz*cKT 2s1tSe>N~lRv( Nx&S70Z
-rKkC 88l7vk½uH`=qr7ipKb5wL)9+hzSZy(:Ag.
->0GCZ_!1Db8isp'klyHOGS ?#3HSg]]#0;a>jWbG.t K%rW/&%|Jp cd o'v>zq|R11B 4fBo:v`QVI G+$ºCs%1t Dq)h
-JUV%&YOcyCO6¢1ð\/"E×O""Lbj:!m0qw*Oyzbv a{BF$7W<(e+2J÷‚O ^<iSa,cPs4E4!qaSFZ~M6@A@r!'/j0'R%aw[)%lei!"2Up9sr(jQl]?buV1v?t#;VZ}kCqg[ H@P&o*om)(CG& w4);0q(D9`Bu<ÕöHt]UaHiVPq ed(fuYHp**a=LEoII+pxZ (1?U<.UpP%C\A _E1&Xw
-@H*Qt*aed5*biuIIPZ~w1SJO# \c@-a Ef>{q2 dad32+gtK7rnS#{lpAF~FW/,e}n
-^D`EhJA><c TK6<G?0
-endobj
-3212 0 obj <<
-/Type /Page
-/Contents 3213 0 R
-/Resources 3211 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3185 0 R
->> endobj
-3214 0 obj <<
-/D [3212 0 R /XYZ 85.039 781.388 null]
->> endobj
-1038 0 obj <<
-/D [3212 0 R /XYZ 85.039 761.463 null]
->> endobj
-3215 0 obj <<
-/D [3212 0 R /XYZ 85.039 672.697 null]
->> endobj
-1042 0 obj <<
-/D [3212 0 R /XYZ 85.039 672.697 null]
->> endobj
-3216 0 obj <<
-/D [3212 0 R /XYZ 85.039 641.171 null]
->> endobj
-1046 0 obj <<
-/D [3212 0 R /XYZ 85.039 311.511 null]
->> endobj
-3217 0 obj <<
-/D [3212 0 R /XYZ 85.039 284.896 null]
->> endobj
-1050 0 obj <<
-/D [3212 0 R /XYZ 85.039 284.896 null]
->> endobj
-3218 0 obj <<
-/D [3212 0 R /XYZ 85.039 263.903 null]
->> endobj
-1054 0 obj <<
-/D [3212 0 R /XYZ 85.039 136.227 null]
->> endobj
-3219 0 obj <<
-/D [3212 0 R /XYZ 85.039 117.961 null]
->> endobj
-3211 0 obj <<
-/Font << /F20 1617 0 R /F15 1628 0 R /F56 1642 0 R /F35 1632 0 R /F65 2099 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3222 0 obj <<
-/Length 2021
-/Filter /FlateDecode
->>
-stream
-xZKsW:v,f*DX
-@p?Šñ£¨"$ŸŒ"QGPGahEOQt1zd.+im/qs^%["?O`??dt2r</:#T"YHD!
-
-!AI5(N>)
-Q
-o.\}.>vBj"=WKRk2Nmh-H-C?>kjZu
-@6>\mV08s ^
-{FCC`XiFF=lt(r&tuaaO}n9L
-0mUCWm;bmk`GOH%|5 mKnvz|3n:]b3JK aH+ jv{G[gm,qzwpaVRcx b{ZU¯vMp# 1Vb^n[/nvVa7MB%8C+MOs6wp~E?Mp+k suG >Of-kS
-tTi3gudaXUi QPC\eu#bhhz› ÞÃ`pmAW b>zjsiJ<Of#l!RL{;i&K{55'{5/)e@2fU Y}/ 46;G>QpILS6@ 6 1QUo;
-\S|R6(CG kgpA67K,]n9n35GOK=o1Vp
-endobj
-3221 0 obj <<
-/Type /Page
-/Contents 3222 0 R
-/Resources 3220 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3229 0 R
->> endobj
-3223 0 obj <<
-/D [3221 0 R /XYZ 85.039 781.388 null]
->> endobj
-3224 0 obj <<
-/D [3221 0 R /XYZ 85.039 758.673 null]
->> endobj
-3225 0 obj <<
-/D [3221 0 R /XYZ 257.152 764.647 null]
->> endobj
-1058 0 obj <<
-/D [3221 0 R /XYZ 85.039 619.462 null]
->> endobj
-3226 0 obj <<
-/D [3221 0 R /XYZ 85.039 599.133 null]
->> endobj
-1062 0 obj <<
-/D [3221 0 R /XYZ 85.039 360.311 null]
->> endobj
-3227 0 obj <<
-/D [3221 0 R /XYZ 85.039 341.439 null]
->> endobj
-1066 0 obj <<
-/D [3221 0 R /XYZ 85.039 223.65 null]
->> endobj
-3228 0 obj <<
-/D [3221 0 R /XYZ 85.039 197.036 null]
->> endobj
-3220 0 obj <<
-/Font << /F62 1689 0 R /F56 1642 0 R /F15 1628 0 R /F20 1617 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3232 0 obj <<
-/Length 1608
-/Filter /FlateDecode
->>
-stream
-xMoH_a2 IT&nR6 .3lvj5=a
-cUevBo jq)gf\)28 [8$b {="';+PTf`]5I(H dizE;vG[({^je5^^"I)E\Wv
-~T 1 4*C>(\ ZSW
-[g iQsG?.t1HiCN;DCdNq|Qk(Jw ^FI4t(`_q9€ž7„ä®®,×¢îDf u#I/
-V((1 OPz5Q78$x\zow
-s}!Oh-%L^hB e!';f8(nzr C<e4bmG
-=H( 2hM
-6L3e5K4@.9| VB)O <c}>G{j"
-:DNYV*Kdt89tYb7S{nk]Mk #X} 4]eL:`+V~{>j"Øgnh[]äûi«‘ð…‘ÁFAy}g X^-$~X
-endobj
-3231 0 obj <<
-/Type /Page
-/Contents 3232 0 R
-/Resources 3230 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3229 0 R
-/Annots [ 3235 0 R 3236 0 R 3238 0 R ]
->> endobj
-3235 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [141.013 726.489 469.456 738.481]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.css.tayloru.edu/~elorimer/databasefs/index.php)>>
->> endobj
-3236 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [139.346 713.243 202.339 724.811]
-/Subtype/Link/A<</Type/Action/S/URI/URI(mailto:elorimer@css.tayloru.edu)>>
->> endobj
-3238 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [141.013 527.64 309.095 539.633]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.openantivirus.org/)>>
->> endobj
-3233 0 obj <<
-/D [3231 0 R /XYZ 85.039 781.388 null]
->> endobj
-1070 0 obj <<
-/D [3231 0 R /XYZ 85.039 761.463 null]
->> endobj
-3234 0 obj <<
-/D [3231 0 R /XYZ 85.039 743.459 null]
->> endobj
-1074 0 obj <<
-/D [3231 0 R /XYZ 85.039 563.482 null]
->> endobj
-3237 0 obj <<
-/D [3231 0 R /XYZ 85.039 544.61 null]
->> endobj
-3230 0 obj <<
-/Font << /F62 1689 0 R /F20 1617 0 R /F15 1628 0 R /F35 1632 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3241 0 obj <<
-/Length 2552
-/Filter /FlateDecode
->>
-stream
-xko6
-4)mmdo^d[6@ "9rC77$i4Y7€|ÿ. m”o´†ñpî ó8òLD%fi? (?0W{Qu6#,nu+E k]3FC|{te>G`c2<guOv[WJ,SF>WB3H}3(yk2QX"ó{ނ4 ¶kX(B(aIH
-V69ïp~„wõ¹ +£ýÀ¤S!,Pf#?XHxD{( CNJh;2
-.bK+DFq|y zO6| k^&}SK[v[<#`4#/H<`[bc.B.QOY!&"hžÐ9vˆ¸À t‚Ó3ú 3P]H$m]Vq=<>`MW lZ+>^W5y'7IJzOWESH@E"=H> Rg;ÄZ 7+ 1_OY 9" qu%"8Ho|(!\T&L"%P0,"
- >TQwK!GST= : juAZVA sOv&IHy-)cL]Aa.<mnn+dd2&0y4*gA\dp>X9j|u1(Ki6f K>Iknu> D $O
-%5B qIt'bLA
-Mw{D&n9Íc~KI9#`3x}M+4fqUJ)$0BUB/ K+[2s3 \@OF7R?V;Ge6aB<gC_-BTKSQ
-s$p85"DqdA03+cql2@Q}s+d5CQrMi~,oTY)t+J ,u\' ]"
-"Ð
-‚–§mçÜ"gã­ò2çþ›_KWn)Kw2+D/[PA*S#3E"eK0+7-
-endobj
-3240 0 obj <<
-/Type /Page
-/Contents 3241 0 R
-/Resources 3239 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3229 0 R
-/Annots [ 3245 0 R 3246 0 R 3247 0 R 3248 0 R ]
->> endobj
-3245 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [465.374 560.105 512.306 571.795]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.microsoft.com/NTServer/nts/downloads/winfeatures/NTSDistrFile/AdminGuide.asp)>>
->> endobj
-3246 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [111.316 548.677 184.218 558.245]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.microsoft.com/NTServer/nts/downloads/winfeatures/NTSDistrFile/AdminGuide.asp)>>
->> endobj
-3247 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [111.316 478.81 163.483 490.499]
-/Subtype/Link/A<</Type/Action/S/URI/URI(file:smb.conf.5.html#HOSTMSDFS)>>
->> endobj
-3248 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [223.966 465.261 276.371 476.95]
-/Subtype/Link/A<</Type/Action/S/URI/URI(file:smb.conf.5.html#MSDFSROOT)>>
->> endobj
-3242 0 obj <<
-/D [3240 0 R /XYZ 85.039 781.388 null]
->> endobj
-1078 0 obj <<
-/D [3240 0 R /XYZ 85.039 761.463 null]
->> endobj
-3243 0 obj <<
-/D [3240 0 R /XYZ 85.039 642.137 null]
->> endobj
-1082 0 obj <<
-/D [3240 0 R /XYZ 85.039 642.137 null]
->> endobj
-3244 0 obj <<
-/D [3240 0 R /XYZ 85.039 617.419 null]
->> endobj
-3239 0 obj <<
-/Font << /F20 1617 0 R /F15 1628 0 R /F35 1632 0 R /F38 2158 0 R /F41 2104 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3251 0 obj <<
-/Length 1199
-/Filter /FlateDecode
->>
-stream
-xWKo8W2bE&EHr, ~AKQ$73t|'D ?L8"L'|8gJXDR!<G"S'[LV|u/>-^nv.ev}g(Pt/A.|{1r`"5lq&Z_e7G*%gx9<Cleo3_i<2MLi4v3arXk"ZB/E*DT?w%zvTM<g iK&(U#ikf2ºuƒÜgæ܃P~]2SVv_vJ+wivh-OH+[JG{v{fW;Qx!~$%-V_8T* `)beG 1D|\Ga~ 6g7_k5GRc5]t[}J¶Ú¯9HUY$U"*P2:.E
-P
-PKpU QG<knmFXLXD*F)=UUA,8GJXSH>)hNRi7Mo=Zvc N$#s+h|e|z G6'b,u%eY.M 1g6Qija1JT5x.kcZZS{CCTq'JM)S+I(q}rp" i*}[)2 U+E A
-]nF?sQ5uë¥ê‡
-,ys¢:@cO}zo^$
-jm9C/5C[WHr$"bLAo 4%4!-dYnN_iCrC.2y3qX*_*w>m'icV 2°{¿ö-Æ0÷ǧþ¿2N=.\nendstream
-endobj
-3250 0 obj <<
-/Type /Page
-/Contents 3251 0 R
-/Resources 3249 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3229 0 R
->> endobj
-3252 0 obj <<
-/D [3250 0 R /XYZ 85.039 781.388 null]
->> endobj
-1086 0 obj <<
-/D [3250 0 R /XYZ 85.039 706.019 null]
->> endobj
-3253 0 obj <<
-/D [3250 0 R /XYZ 85.039 687.147 null]
->> endobj
-3249 0 obj <<
-/Font << /F62 1689 0 R /F15 1628 0 R /F41 2104 0 R /F20 1617 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3256 0 obj <<
-/Length 2363
-/Filter /FlateDecode
->>
-stream
-xYKs8WHU i [bgv5+H^ohXHO@R=R5 ,1Y(O'lg0 % C'&];FL{AgnzO?,(I:1+f*'
->]WTz}{P<Z9OH)FD}/J\|Xie6J6ef5
- i24/I=F2./VTa>2t9K 3Kí“@0f_g[gG4i:,"bf54´Ò©ÀéZ{I .w}1\J N {WA1(pLCeQ=b1n# -){}@gnG Ot~,6P}H*=U]uM]7q
-('%(c.@jt04$uj0wxm-5]2bX|Qkx).@,Y].e] .}%wfYeIX  KR']^`"6u=u}E6C+)9d]G
-kyx3@nhgJ~>4376^T\\' 'A6Y}n vX=/B =CiKL>S-^Fesnc*-TnoIU>*W*UrZ;;fH01!' N
-A@ p" t8E "/9c]Y"dhsgeIU1=U *
-JBQ lI6eA
-`r'bT@HSaI)c~f5` Ar\l2 /|/(sr=[\PH5HF3>oE%J2i6;  G@q?R*v[@cB3qr\!;1hGo@E6MY}s&Gd}sfGflf @4CB XuOlya)&Tk+ fA0W< ,3/
-7 Bl'gM<nGx&}':60U
-~-@/J[xR~Z:N^1
-_^#1_"@v2s,W!8<Q^r9SGof,Q^o5?&Pd<)UHCj42>xyoA8eF{)w]rm= +rUf|Y|TX
-endobj
-3255 0 obj <<
-/Type /Page
-/Contents 3256 0 R
-/Resources 3254 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3229 0 R
->> endobj
-3257 0 obj <<
-/D [3255 0 R /XYZ 85.039 781.388 null]
->> endobj
-1090 0 obj <<
-/D [3255 0 R /XYZ 85.039 761.463 null]
->> endobj
-3258 0 obj <<
-/D [3255 0 R /XYZ 85.039 647.888 null]
->> endobj
-1094 0 obj <<
-/D [3255 0 R /XYZ 85.039 111.902 null]
->> endobj
-3259 0 obj <<
-/D [3255 0 R /XYZ 85.039 81.701 null]
->> endobj
-3254 0 obj <<
-/Font << /F20 1617 0 R /F15 1628 0 R /F70 2201 0 R /F18 2207 0 R /F41 2104 0 R /F35 1632 0 R >>
-/XObject << /Im1 2193 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3262 0 obj <<
-/Length 3108
-/Filter /FlateDecode
->>
-stream
-xr`0A7t A@ k
-K
-NoQZBOLWgx=o[
-q&-F@2ux)MB3mx'dM
-><!,VcQs1rxlni0D_9^
-O8/Rn(,Z>Fly)O!'R#i^]a+@hm~=&m#mIQ8$m&Z2f$I!;k T#XR-`L(3.!!2.pH p}70D*(LWZ*hkti Y2`ec&dYaJN-S|>=pCtD##|tFvk!$nRsaF[{ 2®Ãn7›ž}²½1BM]ZL0kr[~3ehbP'B5q 73jK<dwd)
-zKshFj8$åßúö£K[6w\!hvHtL6'#`Z
-.0VpLW_r&!d`Z.xKL b„. #™€&y×Ô8
-zeƒP2ndEm~h"4…ÀÔUZ^wo P(xE4 K
-.&
-1a:E Liwy B9\ 4S)OMgyQaV`[yH@
-Hc&kb/$[O(lgVx7h EXr {c?@bCaa<iA _kJVI5Ept.4XqKP<bsQ$/Dc-139pYq6 y$<C
-`SOq% S$QkVLYEW\0?yb8E)AK D[|#8FT|+zU:upd*& Q!aWKe?/M^aNY'>qG/?q+ I'r 9ScOakr7Mk?l@dhg* By< S}R%\_(g
-V_)CV nvendstream
-endobj
-3261 0 obj <<
-/Type /Page
-/Contents 3262 0 R
-/Resources 3260 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3229 0 R
->> endobj
-3263 0 obj <<
-/D [3261 0 R /XYZ 85.039 781.388 null]
->> endobj
-1098 0 obj <<
-/D [3261 0 R /XYZ 85.039 691.087 null]
->> endobj
-3264 0 obj <<
-/D [3261 0 R /XYZ 85.039 668.014 null]
->> endobj
-1102 0 obj <<
-/D [3261 0 R /XYZ 85.039 105.97 null]
->> endobj
-3265 0 obj <<
-/D [3261 0 R /XYZ 85.039 84.109 null]
->> endobj
-3260 0 obj <<
-/Font << /F62 1689 0 R /F41 2104 0 R /F35 1632 0 R /F20 1617 0 R /F15 1628 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3268 0 obj <<
-/Length 1797
-/Filter /FlateDecode
->>
-stream
-xnF F47'qrHs"rh r)7oG8 mOq~/ gN»Ž:éx6'”Yzfvm2}|{2]~I[~u%w\_;~k}w~"5`ci2~ci:^jt;{waxp;Ic8nd|G|Fv
->S
-xe1z~`j'N nW/#oV~^Yi [w'D52SU%B!Q DG5uT^K0."%tqo &
-3g*jS& 85#E!H40EaB%534bhj9%Fk 
-B&[?3S),Ej 5Tpo .ET9'Ltk;I &TWj;OZz!5óîí]Y4B[xIp;'Jd5
-5{~ipb;!;Q";dqoAlw)-ý0zijR:l*&PAeC)a6,Q6W:RI{fZ #egIa JQd!9F(À7\†&’¥†Ø ‰¸«Ü›£0¢¿&â w‰23ďÏÈ´\ô¦ç"h^V zhc"\Thk nKl$E<U,K+- U[z A2VrrcY7Fa-U<Rmi:{X2lii^C^iVF=r!-3qX 28tjm3;nÝdЄP<^hw\lxar/G4y~3b6BR2+~!4%Z$z _*-a#viON68p5g6%lUd9'9"Q?1jïpÃh´y[ãõæ©×HWCHY@dow>g$+ArGx}[xsI3lo(hEb*F9g.3~3%1S83rD&-#T/(<aO}N/`QN{?8<5qF
-endobj
-3267 0 obj <<
-/Type /Page
-/Contents 3268 0 R
-/Resources 3266 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3272 0 R
->> endobj
-3269 0 obj <<
-/D [3267 0 R /XYZ 85.039 781.388 null]
->> endobj
-1106 0 obj <<
-/D [3267 0 R /XYZ 85.039 683.504 null]
->> endobj
-3270 0 obj <<
-/D [3267 0 R /XYZ 85.039 661.643 null]
->> endobj
-1110 0 obj <<
-/D [3267 0 R /XYZ 85.039 503.514 null]
->> endobj
-3271 0 obj <<
-/D [3267 0 R /XYZ 85.039 479.532 null]
->> endobj
-3266 0 obj <<
-/Font << /F62 1689 0 R /F41 2104 0 R /F15 1628 0 R /F20 1617 0 R /F35 1632 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3275 0 obj <<
-/Length 3307
-/Filter /FlateDecode
->>
-stream
-x]s6Bn*$L.3v:nk;g^hxHw
-5n.M$|(7B]r8u,b.
-iskuW@H|~,6pœ) ¼õ&ËùÎSx]ñ¬¾6ˆ@j!l6M,dGhe= -!] d { j@0
- a:=0}O3D,CU2papJdoNy\R%'\<Avnyqu4".K F!(hF&9?$>a)4Q),7bg}?28aN;9`?gU3h #(W[b{Vq7 )œBH.nd!E>joldn:FS@)2A#mj0²äÂÈyÞp0•¨ +,úº“OVAlg<?F!o8,áH\W, r PhTB=t3s%t3H/d4B(
-f
-@Zo08'&9GhkkR {H}v(z }%|]P|VZXbv
-=N
-G[`o)h|Xq-q/Bi7TS|u:E-j[0|^ Vi¿*/ä ‡‰Ôø-ª•nµõå ŽMHv'  a'@Ho(=XE1IuÊs”Ì°~W7 -"Uxo%MogaiKl
-sMMo7+R
-7m&]XJX%9c7YyFA3|K\ LoqRn#6u4u9s; `p)%FN.XwJ*.N%L)w[<a~NaLt<(VV=%-~k(=7 ]_
-A4c:6cCX9.wDyn@euOe1]1eZfWe\}2:`o}4
-K=#W9< cW'sM aendstream
-endobj
-3274 0 obj <<
-/Type /Page
-/Contents 3275 0 R
-/Resources 3273 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3272 0 R
->> endobj
-3276 0 obj <<
-/D [3274 0 R /XYZ 85.039 781.388 null]
->> endobj
-1114 0 obj <<
-/D [3274 0 R /XYZ 85.039 610.729 null]
->> endobj
-3277 0 obj <<
-/D [3274 0 R /XYZ 85.039 563.392 null]
->> endobj
-3273 0 obj <<
-/Font << /F62 1689 0 R /F15 1628 0 R /F56 1642 0 R /F35 1632 0 R /F20 1617 0 R /F38 2158 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3280 0 obj <<
-/Length 3404
-/Filter /FlateDecode
->>
-stream
-xr8_PUxR5%%RCRQ@Rn*
-xP *w0nq4/Ms>8`YlR 0LH 6jBd |Z H-
-_~-)M$tcD696D Mb5çãZ\4e?Zx:So86(b+sqcgo_I?dyg; Lz@'b-.%/,`
-&=1;@`T9#9P M't#8n8f12m8p':fNh$I0z"2 )n$H.(/uEYd&@"z^eqBr7"JT( 6s}gY7eE8m3vXv,j/~n*q7w
- :R4R0'~X
-[L;ü9T 9k!ne#*/ .`7umK-1 B6w0Cf,&mkED8r!}l b!ZJRm($3
-\35!E]MqX4;R4cei7>n
-.ªø:m0­þ
-«V9W5<ON D7A9ÁÏ%ºÎa¢û ;b‰í3ª£$ßÅÀÈíãÿ9ÓõôÃ)¹Çá»2ž3¬c";ýã .¯;õ:çXt5GgZ<F, WK1@\;-qd(W@"0R8Kfo\g
-P'}<
-?=H6@i,,-=I` >":x- DBSY%?qiY:
-"` n8Vh{uN<'e
-MV&tlE:IW fVzUJ Bsfc.A$?\|ESO_]'8`S^bz)!ÚiÕI:R=3rdi; \ i:axH3
-endobj
-3279 0 obj <<
-/Type /Page
-/Contents 3280 0 R
-/Resources 3278 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3272 0 R
->> endobj
-3281 0 obj <<
-/D [3279 0 R /XYZ 85.039 781.388 null]
->> endobj
-1118 0 obj <<
-/D [3279 0 R /XYZ 85.039 475.077 null]
->> endobj
-3282 0 obj <<
-/D [3279 0 R /XYZ 85.039 456.811 null]
->> endobj
-1122 0 obj <<
-/D [3279 0 R /XYZ 85.039 276.834 null]
->> endobj
-3283 0 obj <<
-/D [3279 0 R /XYZ 85.039 257.962 null]
->> endobj
-3278 0 obj <<
-/Font << /F62 1689 0 R /F15 1628 0 R /F20 1617 0 R /F35 1632 0 R /F41 2104 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3286 0 obj <<
-/Length 1706
-/Filter /FlateDecode
->>
-stream
-xXmo:@d ot%jLb8r`N:$sxuz9`P75Onk|GWNs;W|jN||Oo'Y~}LoZAYgq/S>F_;p/
-!`rHPi_Sp|-5. \sa
-*Omx &
-VJk MTYb)H/Mu')U[@Lw|TNCsY RPw(]{&D}78/fMYzfH< Q
- >z_xAq"yn8GAl <;j|;;20^Oo7B
-:JqH]U=f4Iw~:
-^m)7BvbfQM3Uf(tZZ!`ZE%/h.U -6
-endobj
-3285 0 obj <<
-/Type /Page
-/Contents 3286 0 R
-/Resources 3284 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3272 0 R
->> endobj
-3287 0 obj <<
-/D [3285 0 R /XYZ 85.039 781.388 null]
->> endobj
-3284 0 obj <<
-/Font << /F62 1689 0 R /F35 1632 0 R /F15 1628 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3290 0 obj <<
-/Length 2490
-/Filter /FlateDecode
->>
-stream
-xkoF~cI)gmq E$e'+Q=`;;;; ?^/7Hzs8-Wn v\yF!n=u72_v00Ag0d:{38'7~dz{?
-(WJ0hd9X9'NDIdl~>;w0YQfO80/!.[W>?5'hjU
-:0 Q~jJm,=CK(0POaL. A4[ # WX1'84tW7 J Y%2Ac
-
-CGT{faIN|w]q#>Bg@ OJK
-7X_1v@TrQAuDNAa@^z|/¿è®îoq&$2ªeÎÀÚ­Žf،«!Ð4š2O%6\q+['
-endobj
-3289 0 obj <<
-/Type /Page
-/Contents 3290 0 R
-/Resources 3288 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3272 0 R
->> endobj
-3291 0 obj <<
-/D [3289 0 R /XYZ 85.039 781.388 null]
->> endobj
-1126 0 obj <<
-/D [3289 0 R /XYZ 85.039 532.001 null]
->> endobj
-3292 0 obj <<
-/D [3289 0 R /XYZ 85.039 511.008 null]
->> endobj
-1130 0 obj <<
-/D [3289 0 R /XYZ 85.039 427.088 null]
->> endobj
-3293 0 obj <<
-/D [3289 0 R /XYZ 85.039 404.679 null]
->> endobj
-1134 0 obj <<
-/D [3289 0 R /XYZ 85.039 269.796 null]
->> endobj
-3294 0 obj <<
-/D [3289 0 R /XYZ 85.039 246.478 null]
->> endobj
-3288 0 obj <<
-/Font << /F62 1689 0 R /F35 1632 0 R /F20 1617 0 R /F15 1628 0 R /F41 2104 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3297 0 obj <<
-/Length 390
-/Filter /FlateDecode
->>
-stream
-xRMs +8Cm2:SM !f]v{po[t bR-8Q46bskM{
-)S:@;|6EH{y&KoK*3ZF RY99[^Rg8)M.-nMpR>[]>bVJGb[JabUOSH(W5=bBl_?Lendstream
-endobj
-3296 0 obj <<
-/Type /Page
-/Contents 3297 0 R
-/Resources 3295 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3272 0 R
->> endobj
-3298 0 obj <<
-/D [3296 0 R /XYZ 85.039 781.388 null]
->> endobj
-3295 0 obj <<
-/Font << /F62 1689 0 R /F35 1632 0 R /F15 1628 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3301 0 obj <<
-/Length 2374
-/Filter /FlateDecode
->>
-stream
-xYo6_[XC,mYn{X=06m %C'~e)w
-~.OceEcw'u|aSB{bpFY+Iq0w"O_~M],3w q.G33U??l!P4{owN666{;EPuM -JLZ]IV*tTw: <r2f"Gq :Ot~3$qlwQXRe
-pŠºí¸õ ]s,gFEtEZNsxuBDEg'2-Yl{
-!­¥˜$A+Bkqg01~GFIE4qW }HJ>&E}%kpg!}TT>2Afc2U%tlB'B scU&HQ
-U^3Z_T
-S:ml=<="NT,B @=YvB^x6eP@Llu>3^^jvlCw,2<F?Il&U"cO%~R"s3 !?
-n:./ `H"LeK/03<5!V*8_Q
-qw+Irz)tPgYT \wAVG_ (&i<7Je ;TMFJo) 6n^ZD8)`bDqz^WNsK\30|X\(&",LZ{(Z:iK(6p80(V8NN_ZOc)N4: l_(es5+DgoBPrVpY$\.+
-y>,V#93_A> VJ";;79I<<?STFt m9^i$d56)R@ ?(> u-5+'{"4'c'NW\ya`~{CD]UD+%H[5a'zj>HO^$swb%T)q]dpvsu7FgU,A:W 
-(b$8%mG> E@rnBj-J(SQrGAmt{B9
-"!L7:W5?/`l_LS-bgsG0x-eNg6lKZa6O= s=5B(5e(=x^&Au*=mSL
-endobj
-3300 0 obj <<
-/Type /Page
-/Contents 3301 0 R
-/Resources 3299 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3306 0 R
->> endobj
-3302 0 obj <<
-/D [3300 0 R /XYZ 85.039 781.388 null]
->> endobj
-1138 0 obj <<
-/D [3300 0 R /XYZ 85.039 761.463 null]
->> endobj
-2147 0 obj <<
-/D [3300 0 R /XYZ 85.039 667.661 null]
->> endobj
-1142 0 obj <<
-/D [3300 0 R /XYZ 85.039 667.661 null]
->> endobj
-3303 0 obj <<
-/D [3300 0 R /XYZ 85.039 642.943 null]
->> endobj
-1146 0 obj <<
-/D [3300 0 R /XYZ 85.039 597.507 null]
->> endobj
-3304 0 obj <<
-/D [3300 0 R /XYZ 85.039 568.103 null]
->> endobj
-1150 0 obj <<
-/D [3300 0 R /XYZ 85.039 328.241 null]
->> endobj
-3305 0 obj <<
-/D [3300 0 R /XYZ 85.039 298.837 null]
->> endobj
-3299 0 obj <<
-/Font << /F20 1617 0 R /F15 1628 0 R /F56 1642 0 R /F35 1632 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3309 0 obj <<
-/Length 2319
-/Filter /FlateDecode
->>
-stream
-xkoF~PD4]Rd~p]qçrµò¡Hb%R2/TT;;;;3;?d<}Wxy5<k׋B\a>)
-&^2e~tn\6*@l;y/vu?G?{e*{{$H y1zkz.1S?q `
-'`LS)* MH *Y;tH\~ "g o Hk0+2e<kTPveMuF T <5$IwM^06('o8
-±½^Z>j1;6x
-Y{HM=E,6
- dasg=4 "UU(l!OW?ag!&*b|5}s!FGR
-KaY|gDI&YVop#!#( …ýR!Ta`-^R3x3a &29-=/Qz}nxwG6ukq,b)(m_,UP&^mdu\93u>]aalEXU$w7t 4+)uzN%a8J<>rfC5-` 7H()/[1m Fj</y=J- WiMhkY5]lx3QK^&!
-{)}@kcr) U?<9+tVp*IEzD;[@U]m&qeRmn(7]k01!<VM
-&`{h4 JeMk 1Ky<9|o?AF*Oq<!yW( QHRhw]iJfa$efn`tRjZrDp0!o ]=e!zB6 AW%h/MntQd%{&)xQWg A+8Vr S2@S@#NI-ssYyw0O,uv:]P8 csh "Za0?/ 1x0[d.YilgPt.)+N j`T7n#),(8i5Bl*<+S ,]!YlZ5m /G9b0X' rl/o%;&~5M#D{yzpbRA/I%neDe>]&-VxQ c:{2mW9 { T%d[eurf`xl|D0' b)L08B<,\qADbtQX?E= )o] [@+-jnt/?iP4!-"h }?%aE:/$px~DKoD(<]c#[T} +i(Y=DEComn~2(}[mW_] öë< ©ÀwÞ{_aðÔPhK&4_lOpF5_}` ~Nd<!G'gw/7R?7o~~a~{]]ge 5G[WCg8|||SlE^eV|}?NWR(TD4Z
-(O?rUa8`g==endstream
-endobj
-3308 0 obj <<
-/Type /Page
-/Contents 3309 0 R
-/Resources 3307 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3306 0 R
->> endobj
-3310 0 obj <<
-/D [3308 0 R /XYZ 85.039 781.388 null]
->> endobj
-1154 0 obj <<
-/D [3308 0 R /XYZ 85.039 761.463 null]
->> endobj
-3311 0 obj <<
-/D [3308 0 R /XYZ 85.039 736.911 null]
->> endobj
-1158 0 obj <<
-/D [3308 0 R /XYZ 85.039 508.6 null]
->> endobj
-3312 0 obj <<
-/D [3308 0 R /XYZ 85.039 479.196 null]
->> endobj
-1162 0 obj <<
-/D [3308 0 R /XYZ 85.039 171.71 null]
->> endobj
-3313 0 obj <<
-/D [3308 0 R /XYZ 85.039 140.185 null]
->> endobj
-3307 0 obj <<
-/Font << /F62 1689 0 R /F20 1617 0 R /F15 1628 0 R /F35 1632 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3316 0 obj <<
-/Length 941
-/Filter /FlateDecode
->>
-stream
-xVmo6 _a'Uc}eY[(\[M%g;GJr_a(ZQ"E!e6f><vZZ^bOKg3J"gerv7r9' GM^iM<Y| +svI|(Qh@E]Z +{:a[8\A#Bv9%a(?
-s@2!{
-&*:PTbNI#P*Srx!Anbb_ *;iV n7+g1)5OFE>4:
-*8Q(PEMkT}sht $68`< ,]"{LX_HZ3endstream
-endobj
-3315 0 obj <<
-/Type /Page
-/Contents 3316 0 R
-/Resources 3314 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3306 0 R
-/Annots [ 3319 0 R ]
->> endobj
-3319 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [237.716 552.867 359.98 564.86]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.samba.org/)>>
->> endobj
-3317 0 obj <<
-/D [3315 0 R /XYZ 85.039 781.388 null]
->> endobj
-1166 0 obj <<
-/D [3315 0 R /XYZ 85.039 598.573 null]
->> endobj
-3318 0 obj <<
-/D [3315 0 R /XYZ 85.039 567.047 null]
->> endobj
-3314 0 obj <<
-/Font << /F62 1689 0 R /F35 1632 0 R /F20 1617 0 R /F15 1628 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3322 0 obj <<
-/Length 2904
-/Filter /FlateDecode
->>
-stream
-xZ[~X%Ta/-Š"qÇi‘±hú0+qw…¥ÈIYsŠ”¨]#Ea3)n\&oW={:;k=3 Tht,(]zNntYjHxt.~]^,UY,Mm_y # +n:tJS p1tMV->L#ny`=2Sl¤Ñgëá²*ڔ¹v«ä)§¦•»Q 3qOp/[$5BgNK&@G%lnD"\UEqJNd-jwaEm<D iy l3QU H^'-p \n{_Y3Z 2(Zba*0SDal64VK}]:6ccgrod *P%oKp7J8q?:Tk}'Q
-p R}aRl[4!TVX:xbfavAZMmëf÷´?§7Æ°¼°Ñ‹b»ó»Pp`nc0Y;]v!qEHjD89hP_IxrE9Mj"?bA-kr$jx)8_
-iC1DW'/ld l1ga%}uk1[\z)+
-; fkK HRsK*$+1Qz4zv'y;x=z%"J=h-UejS5o85
-kd !'t0*Zsk!%,
-P‚‡6Š)fܟ En_E:A_,=7.O|sz$Qy`Ptxrg
-2HL9aa%%T)`ò•13‘ýV8z7<pr~~'sw Ã#L4[,S$4MEA7lj[e`=bc\bgT2!wz-&^>}<#m2C6X%xjA_tg}=# [|
-\8[3my[M86(;3 6* 'Mt(ll M9UTp}*d D@@6apxL6
- B L#c2` uFq@)~'3&€• my²öœ®ã̕g|ç~\…:úï iÛèŸ?KKjI VI1yjk Jgv0-O;O^l2,_|_jASrTis #&NP`s@cC0Z2'I
-®{8Qbr|B~/q<D~$
-,R#yFg&0}RR x\l$s:ddb@|_V\Y1o)I16z n]C@W=# 4A5o#?Z Z5O**w`@/D(3 }XV;3>}~u [9oxI1!_ n4pC9vps&sqFBk#à rTE8,<v2c9 ~1ÂRcp4(|
-6yO~t,Q!
-%lg<C,J L"OO' Y7l \qa@5E\3rh_qyUSmTqZ*0_$YB}9RDW~UGh*bNDCX;2ol}O`=6h jF#9KEoUleD]w.*w|/2 xR{\8cWUn;/\;endstream
-endobj
-3321 0 obj <<
-/Type /Page
-/Contents 3322 0 R
-/Resources 3320 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3306 0 R
-/Annots [ 3326 0 R ]
->> endobj
-3326 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [425.738 463.492 509.276 475.182]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.unicode.org/)>>
->> endobj
-3323 0 obj <<
-/D [3321 0 R /XYZ 85.039 781.388 null]
->> endobj
-1170 0 obj <<
-/D [3321 0 R /XYZ 85.039 761.463 null]
->> endobj
-3324 0 obj <<
-/D [3321 0 R /XYZ 85.039 666.319 null]
->> endobj
-1174 0 obj <<
-/D [3321 0 R /XYZ 85.039 666.319 null]
->> endobj
-3325 0 obj <<
-/D [3321 0 R /XYZ 85.039 642.749 null]
->> endobj
-1178 0 obj <<
-/D [3321 0 R /XYZ 85.039 355.479 null]
->> endobj
-3327 0 obj <<
-/D [3321 0 R /XYZ 85.039 326.743 null]
->> endobj
-1182 0 obj <<
-/D [3321 0 R /XYZ 85.039 144.576 null]
->> endobj
-3328 0 obj <<
-/D [3321 0 R /XYZ 85.039 117.961 null]
->> endobj
-3320 0 obj <<
-/Font << /F20 1617 0 R /F15 1628 0 R /F65 2099 0 R /F56 1642 0 R /F35 1632 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3331 0 obj <<
-/Length 1621
-/Filter /FlateDecode
->>
-stream
-xXmo6_yBMDK5-0c-Zr
-RD$m\`7/''R8O`P%bir;. 4[>>|k'Jl ce=m7ZyB4SZ@@ n)LRWM3<cO(.@auF^u9PWR- ahj1sk `u
-yDd%S)tGcbiw_/^d|7>QelD's6- T ,Wb5C(4Fx:ZZRd ]s 1}:'B0Fg8,*_qC.,:T|Qb/s$PKòXF]<Pl4 Y!Ou JWi1@kElHJu5Gr4SRȵF
-c*E8ie/`[\H\wZw~[Ns3TCMX@-Gg5BGr-tcZ"pY!(q ` QrVZVw!!]dNU#guh+7^$(IqnK,iqNt^R)k5[
-TCZiKSLYFr
-e+"R}E
-$8-400#bE+ 6TueDZ+)`i.lw5.5Xt\ol'vQj!7]C
-N7])~cO9 fEwoH%IrOV#p
-${wQdU
-FPJJ{G;l3*,ð§m‘NLa¶;cœBPiAGW,ug|$ G~r1}.'-^t7<9ewO 7gA96[qY%ob7X@)=CR?tx's&7~ONh^yD0
-endobj
-3330 0 obj <<
-/Type /Page
-/Contents 3331 0 R
-/Resources 3329 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3306 0 R
-/Annots [ 3334 0 R 3335 0 R ]
->> endobj
-3334 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [361.406 452.141 512.306 465.042]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.atmarkit.co.jp/flinux/special/samba3/samba3a.html)>>
->> endobj
-3335 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [111.316 438.895 308.034 450.887]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.atmarkit.co.jp/flinux/special/samba3/samba3a.html)>>
->> endobj
-3332 0 obj <<
-/D [3330 0 R /XYZ 85.039 781.388 null]
->> endobj
-1186 0 obj <<
-/D [3330 0 R /XYZ 85.039 717.788 null]
->> endobj
-3333 0 obj <<
-/D [3330 0 R /XYZ 85.039 688.99 null]
->> endobj
-3329 0 obj <<
-/Font << /F62 1689 0 R /F35 1632 0 R /F15 1628 0 R /F41 2104 0 R /F20 1617 0 R /F56 1642 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3338 0 obj <<
-/Length 3376
-/Filter /FlateDecode
->>
-stream
-xZmo6_ai[II1.q( ke.FyHjzE"Gp8/ W]FO]I2Uh^D0 %qb$0xmGSFqDPgZaRGa{]4\]'IiV*hIUuL
-*h}jvnx}aYh2a&NW^!: <nwDO *I7;X
- GPpTr[loh*wQgTu5<k-Gt$R&RZ;<$<,q2S&9rD3:t]Mz=n..S:L\D$3fML(3"mTFvg?6{+aZ?^-sFFNKv95+ %&
-j2YALdI-.|WrSE5Cx5/o`y,5w4?W9C%W2=L Dz[@ovf#lzEfRJ<pzw4nh/E9/?s?r62<F(y&;Dw#:o$Cb|+Cm>9z14l5.CI|e|RcbDcìµÑ
-íá$^jD MwR k~W<KÍ­®·=i|͌E]{~NDNM3QEp1d[+BG#le8Y0` Kr7R  ?A
-SfeR8*DHI@ I_Ep"eSfrRoYhb(&A/zP1F|V"Mh:GL Ess,K XAa*>IoU8 s@C QNaZ^ ay3(x{T%?@jR~t6]!iwXvR|P#mJkhLM
-'[`5-m-3"lH
-GIN@;t~a _)0C1sWDxjDd"- 77Y@?@KMrlLmv1R{:=( _Chex7:!+/D{:R=(OH!FXkğ¸¶ñ،®z’Rn#`E~*
-(;v:T<K6 jia3"Nct;T,-&T\Xxh*N0\f).b>n'=UC,8I$9#1-M N6 vZ
-iG({9&gh;7=@@jMl:zm3|Jb'9+.-'j
-|A\a@`}pqWa5keYC rBjq#rZ?oRI)Uj%+/1"\<Fh{
-8,5+]/EZCWN0&LXwL/6y|
-N([SE(G_dk+RmsHd?#kT|]m(#CC%bEQ2:; V@O b%D@35:QL?o=MB]_~.w<B;
-UQ\n/ [{\w{5t)WHTý7^¿xue¥³ÌŠ
-Ó"ÿó¬<+˜Ÿ>¼½}-¡%ÂDyE;R8xw``u\29v3p}qi];i@_}doo_!sK0JwF
-<rtk,A5v^lC5iU?Nt"LK6{zG-Nan/~*Y<
-$<L"m0-;]};0endstream
-endobj
-3337 0 obj <<
-/Type /Page
-/Contents 3338 0 R
-/Resources 3336 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3306 0 R
->> endobj
-3339 0 obj <<
-/D [3337 0 R /XYZ 85.039 781.388 null]
->> endobj
-1190 0 obj <<
-/D [3337 0 R /XYZ 85.039 761.463 null]
->> endobj
-3340 0 obj <<
-/D [3337 0 R /XYZ 85.039 667.044 null]
->> endobj
-1194 0 obj <<
-/D [3337 0 R /XYZ 85.039 667.044 null]
->> endobj
-3341 0 obj <<
-/D [3337 0 R /XYZ 85.039 642.326 null]
->> endobj
-1198 0 obj <<
-/D [3337 0 R /XYZ 85.039 192.312 null]
->> endobj
-3342 0 obj <<
-/D [3337 0 R /XYZ 85.039 160.787 null]
->> endobj
-3336 0 obj <<
-/Font << /F20 1617 0 R /F15 1628 0 R /F65 2099 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3345 0 obj <<
-/Length 3282
-/Filter /FlateDecode
->>
-stream
-xr_,$x*3;36@QO_
-~lZB?Zc~jBP$n3+ lh~u'
--DL`H#pX(|gJ'=aT2`l0}A>D*z?zÀîkÑÛë ;ɬ
-¢‹‘IyF`3,R 6i$cr&o ] n zYUSM;U $ikNLg'5ilnv#! 1ZSBz~8t-%@9h"'wgTg&)dZI:<N<Qk2vw7 M2%9 'p8_y,oc=_IZ}6",_{:
-Bp 9ykV5l`sZD Tkl.1zd}73_\".e$I\)&2
-s~0`? C9'~]w=oJUpo~{8s4$hJ
-a+jiwc01
-yC}?2;,css/L A]Iϓl¬ˆWci0CN ^5X[[b&-Ke,c7HPYWmEAz8S>xz>dhr&-%{AV9k8\$"{ndo**-A]65_6/ QS|rULeBNr
-Xd*F"!N0ICjC^a"*%KHKT^V',3hr;;X]=)r:a[Xw-}{/=iR"tw$>u$|~~`s ]}N
-Ea8nS+5C^F 8H|hXM*7yQ#7Sovz8bp/
-T.SoD`[xwcdQwp`H/T$((2ezV4#
- {>?Jntg5=<$A:"SX;kOT[l)J%U}itF8DW Xc]nr{G",|
- >M'aA8L$_{aG <9n$LDrBÀiüW<.zT0ZM.GC7r4i@Q fu!MS>@2L:c1{KO^46+6 "
-uA^xJ)*2HO(-(Kcv8x%+G9Am)7 wHP;'r>Q2n!M H6y\-!SrAlm:j'm\!+mn(!&Cbx7d_9Hl-[H#%9Czko?|TgVD.U}g~0El#*O*H~H _LZ49$-X3endstream
-endobj
-3344 0 obj <<
-/Type /Page
-/Contents 3345 0 R
-/Resources 3343 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3348 0 R
->> endobj
-3346 0 obj <<
-/D [3344 0 R /XYZ 85.039 781.388 null]
->> endobj
-1202 0 obj <<
-/D [3344 0 R /XYZ 85.039 229.428 null]
->> endobj
-3347 0 obj <<
-/D [3344 0 R /XYZ 85.039 184.88 null]
->> endobj
-3343 0 obj <<
-/Font << /F62 1689 0 R /F15 1628 0 R /F65 2099 0 R /F35 1632 0 R /F20 1617 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3351 0 obj <<
-/Length 2333
-/Filter /FlateDecode
->>
-stream
-xYYs8~#U1oWZ[UT!ktH*o
-7k/MOpM5<QuR
- tR\+)+T1U
-PLS
-z9A.
-F) qL^CBjedI8i%0Q;**a^z=x tAan+G@hJ]+¬.L|Y5[Mr)4\."UJ2CKbTYOo.W(<]U5(IY@P{ b@.m+?8o;A;f,pl "eeX0Imq#[Tt%s1 k\ (1,LR]Wmdhg=p_lh\'yMNiJ[/}R^r_\@< r@fo1 'Zr S1l^rvP%sCVbdrA A È÷@N\(T aaejY2>'>lwuC I6pps9
-9zS{8=#c4RGE:irq DUnDeK? 8TAYHFjW!G G
- }j Cft0WbS
-bmCXV(5%?w6b6Fg%HdtB`(]Xkt:B
-C
-vA3n6>a<y2}4j$gS%xDu?^
-}.V`)#Slb#7#c&M(Zr6Dpg:<y@h?,Z#KH5ZY/?H}@AA*g\/c edw*I@.Jdq< AEiH( w, OO,4î‚e5„ÙCeM _X>]Z<ZKr7d<O
-p_[omURCD3Y#&endstream
-endobj
-3350 0 obj <<
-/Type /Page
-/Contents 3351 0 R
-/Resources 3349 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3348 0 R
->> endobj
-3352 0 obj <<
-/D [3350 0 R /XYZ 85.039 781.388 null]
->> endobj
-3349 0 obj <<
-/Font << /F62 1689 0 R /F15 1628 0 R /F70 2201 0 R /F18 2207 0 R /F35 1632 0 R >>
-/XObject << /Im1 2193 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3355 0 obj <<
-/Length 2179
-/Filter /FlateDecode
->>
-stream
-xY[o~[)d\^{[I(vOhh0E*$eWewIItZ/ \JX + ]OVW&yp 5Bd6-Z{2_n_?u>4q'DWG)r|i
- dn.>\]1l:HnIx
-seX0\,Rgg50/xLs$0pD>'Cg/.6[)=?t sdJSZ0u4l.MmhH>%0X^jC+\y-tcZ4I~~^(>|]#X"q|=A<r-'erM%QW=<j]Q ,|nqem/mäð*ÄBQAs`J.Mh.Lv(EeN$Jb?±gZix^WEVQ)If+Ic|H!$'_il9&y)89 =|Hõû¾n–9CA 6C&f<#uhaZ&,4L6#01m-Hb?%p;(Yjh06G
-cRZt:G0,-
-BEIv
-A8W81@~|yZx)8`S~y*>dfmuG&X0rkHP| ET 1eU[ku13-i8D,[3oM`L>dON}>^1MT`:
- ixK2=*V(Mo6?J7 T7@T\LO0?a6LHIYt
-0|H?/9U.d EsC\0Yf=Oy]&0< -
-#rAVQ_Etu0
-U*2*w| /UzT
-.#xS]v%Gc"RFPk8C}{^j?[Q<I=9 [F)[<vYEW224 CFrF=i)AW4
-endobj
-3354 0 obj <<
-/Type /Page
-/Contents 3355 0 R
-/Resources 3353 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3348 0 R
->> endobj
-3356 0 obj <<
-/D [3354 0 R /XYZ 85.039 781.388 null]
->> endobj
-1206 0 obj <<
-/D [3354 0 R /XYZ 85.039 237.715 null]
->> endobj
-3357 0 obj <<
-/D [3354 0 R /XYZ 85.039 218.843 null]
->> endobj
-3353 0 obj <<
-/Font << /F62 1689 0 R /F35 1632 0 R /F70 2201 0 R /F18 2207 0 R /F15 1628 0 R /F41 2104 0 R /F20 1617 0 R >>
-/XObject << /Im1 2193 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3360 0 obj <<
-/Length 2111
-/Filter /FlateDecode
->>
-stream
-xX[s:~3A ‡B943  J/J8MR9L,VmXO~2x,Fb|+Gpq(W7MD2^e~qL}wLgy5d*9x8sX:k|4_O- D>c ?#I<peQnfnFZ0]GZL x3&IC|a(]ÿÔ5hÍpŒÊÿÌ`}©™6/Û:ÓÍcí§æNqL
-dÝÒ2ž-uƒã+UdUpAInt+xTr,~]NsB+1}1z}n9U; _*=Q~0cnK|U
-Iu V8oBUkvT
-O(:s_::W5R3!0@aG$m!D
-kabt{b
-T!8D 45*CWjJ[o2 {YPX4U2: ~2knQ$sSë¡@0 Dd/7EU; ^jZ$ "e)U^bu,fTmHcI+ymCB *B7r\?ub q>L|
-@w%.0&l@m;:P0N5S%OI7(5FBj@x(
-
-yþß_²>6½nO
-`
-endobj
-3359 0 obj <<
-/Type /Page
-/Contents 3360 0 R
-/Resources 3358 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3348 0 R
->> endobj
-3361 0 obj <<
-/D [3359 0 R /XYZ 85.039 781.388 null]
->> endobj
-1210 0 obj <<
-/D [3359 0 R /XYZ 85.039 761.463 null]
->> endobj
-3362 0 obj <<
-/D [3359 0 R /XYZ 85.039 743.459 null]
->> endobj
-1214 0 obj <<
-/D [3359 0 R /XYZ 85.039 261.834 null]
->> endobj
-3363 0 obj <<
-/D [3359 0 R /XYZ 85.039 232.43 null]
->> endobj
-3358 0 obj <<
-/Font << /F62 1689 0 R /F20 1617 0 R /F35 1632 0 R /F15 1628 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3366 0 obj <<
-/Length 1602
-/Filter /FlateDecode
->>
-stream
-xXYoF~w<6F[>R"
-ZdT,iJ$k99$wOC;nN_qIotpvt23$ ;z0t]IA``c]!^]/N/> M>'- +E}ccv)r~]5\NUb(4 O7>pO 8SqUg}vDqR$KZH=G:" tYJ% dc2_I:dqOG3-h j
-K`b Zmæ%oÛçóN(@UwyPti%,8*+ZaiEW$xzYb.
-K`TW|E[f!M2%8OE^3+.h3Noxk>+5K*P!Cf;`u!535,]q.d%_*‡;J(I91L
-:H*<7~6B9LXwt9E <)Iz10=NU<t*DQ]
-HZ@mbF- $ngeD!$,<I5fKe1-NG}7GY0o1Us=h+]4OieA#u :e,s[R@APKy)A&HF$e27rm=: [,l$wp1y-ZP1%@ jwUz?-8hi-AY%Ùp0„º.G3po*/
-L5
-jw'
-endobj
-3365 0 obj <<
-/Type /Page
-/Contents 3366 0 R
-/Resources 3364 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3348 0 R
-/Annots [ 3369 0 R 3370 0 R 3371 0 R 3372 0 R 3373 0 R 3374 0 R 3375 0 R ]
->> endobj
-3369 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [147.71 627.887 511.015 639.879]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://msdn.microsoft.com/library/en-us/fileio/storage_5yk3.asp)>>
->> endobj
-3370 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [365.256 600.485 512.306 613.387]
-/Subtype/Link/A<</Type/Action/S/URI/URI(=http://support.microsoft.com/default.aspx?scid=kb;en-us;Q224992)>>
->> endobj
-3371 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [111.316 587.542 167.915 599.111]
-/Subtype/Link/A<</Type/Action/S/URI/URI(=http://support.microsoft.com/default.aspx?scid=kb;en-us;Q224992)>>
->> endobj
-3372 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [367.133 560.141 512.306 572.133]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://support.microsoft.com/default.aspx?scid=kb;en-us;Q296264)>>
->> endobj
-3373 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [111.316 546.592 331.441 558.584]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://support.microsoft.com/default.aspx?scid=kb;en-us;Q296264)>>
->> endobj
-3374 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [424.405 519.493 512.306 531.486]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://support.microsoft.com/default.aspx?scid=kb;en-us;Q129202)>>
->> endobj
-3375 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [111.316 505.944 388.713 517.937]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://support.microsoft.com/default.aspx?scid=kb;en-us;Q129202)>>
->> endobj
-3367 0 obj <<
-/D [3365 0 R /XYZ 85.039 781.388 null]
->> endobj
-1218 0 obj <<
-/D [3365 0 R /XYZ 85.039 761.463 null]
->> endobj
-3368 0 obj <<
-/D [3365 0 R /XYZ 85.039 736.911 null]
->> endobj
-3364 0 obj <<
-/Font << /F62 1689 0 R /F20 1617 0 R /F15 1628 0 R /F38 2158 0 R /F35 1632 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3378 0 obj <<
-/Length 220
-/Filter /FlateDecode
->>
-stream
-xmPN0.v2"A iYI"c;P@A D5u6u(U0`eTaZx1%eI0nw)K?D*en^V`a`9 dvh(n>O0d
-?Pd1)TiG5G,..|_>iWsendstream
-endobj
-3377 0 obj <<
-/Type /Page
-/Contents 3378 0 R
-/Resources 3376 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3348 0 R
->> endobj
-3379 0 obj <<
-/D [3377 0 R /XYZ 85.039 781.388 null]
->> endobj
-1222 0 obj <<
-/D [3377 0 R /XYZ 85.039 542.44 null]
->> endobj
-3376 0 obj <<
-/Font << /F20 1617 0 R /F15 1628 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3382 0 obj <<
-/Length 2351
-/Filter /FlateDecode
->>
-stream
-xY[o6~02P+"k>Ltb:;x( r"D's%2( yxH¿Ã¨y
-ÒׄT=R !f]DS[M4c"6U\l`$T*(Y,ëÔësTK#|9DvSjyb CoyUEZ5"IW?#Ph&>
-o);H(rdjBn}l/d }pB*VWpis\)#{`^xjLCgk
-Tr*% Gh>}70w$@cESl +; n:vžP%o4dc|6UBCF&$F [~y QW#@. 8 I<8h*{v0:~F
-
-BA\6>{|r`mE<`]1Y(j]19BYRdmY-yl6\f VslJIk]7§-XeD&%E*ldN #*sr-=I[ r\/4GGCEl@cRM$J\|({_//+Y/GO|qWZAH`7T^ Ed!|FwmUG dDbSdod~f:cL9J
-+t{2pSF|9D
-_eUR_8Z0-ø=Ô{Ä8ÝÕ͵Ÿd¯åG~]&sInDxT\iP3dW3 `'16 _
-rn%-g|U}b>v(_l-dK%`C|; =]YUny;n1KN$x$
-Te020B)og'xtbk`H Jh49*1C6Zrb$s\r 3"G3u3P<mvx!j*|C 1T\HG%2Kq&zgR g#3I2-`\F!7;H `sSBHS W6BK
-"TJY{yB =~ !
-!Jdj-E5&jbMK.;&t20o'ZqU=A"^
-L"7UD
- S9J2hy@L?gsFBi.S9I{y7<D$ 0]=x5PCi
-IT
-~ X-_CX>B/$UZOjXp0~M@_1m2endstream
-endobj
-3381 0 obj <<
-/Type /Page
-/Contents 3382 0 R
-/Resources 3380 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3387 0 R
->> endobj
-3383 0 obj <<
-/D [3381 0 R /XYZ 85.039 781.388 null]
->> endobj
-3384 0 obj <<
-/D [3381 0 R /XYZ 85.039 761.463 null]
->> endobj
-1226 0 obj <<
-/D [3381 0 R /XYZ 85.039 761.463 null]
->> endobj
-2163 0 obj <<
-/D [3381 0 R /XYZ 85.039 671.926 null]
->> endobj
-1230 0 obj <<
-/D [3381 0 R /XYZ 85.039 671.926 null]
->> endobj
-3385 0 obj <<
-/D [3381 0 R /XYZ 85.039 643.191 null]
->> endobj
-1234 0 obj <<
-/D [3381 0 R /XYZ 85.039 489.45 null]
->> endobj
-3386 0 obj <<
-/D [3381 0 R /XYZ 85.039 460.046 null]
->> endobj
-3380 0 obj <<
-/Font << /F20 1617 0 R /F15 1628 0 R /F35 1632 0 R /F70 2201 0 R /F18 2207 0 R /F56 1642 0 R >>
-/XObject << /Im1 2193 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3390 0 obj <<
-/Length 3267
-/Filter /FlateDecode
->>
-stream
-xZKPA^{wvcO#Q)
-*0{hBlj%t\w
-35q(Z(QbaL.)%oE$[[qX}=65LT}9 ) ;)n'r-np-36O+*<o(7:\(1Fpm7T
-hUtML1/i<?_fFz<E^%i:}= k-5;)oq*EvéŽ@jTd%~%:8eC}K( 4?(QD
- y>9F9"+Mkb
- Ifd 2q|s>!S $pNy<~{S7xEgTb#fIZcKN@$ZN D<G^jgbOC)0Jj$ zE[|%sK "mtrq!emO
-u8<;,eJ%@yobP~x]³ê‚+;䔚MC_m
-C=U9Tju'00#XtA2w#a`l-`
- d3qTLvB:ac=+9cyjyE2}Obh?v)\`A1aA%pG*4A,F#O>b-*k \hx, q *+/ WNBl'i|,'W$$ sGC"(&T$BUO\ji
-B*w8GA%NYNr
-0fwH_y&8ms9aWx2wq)w>U.JSROh>7."@EnhrXuCHa9Z$G/BoK"M!N!8[nxG`,(B(Vb+vMDQS9Z2;za-r#OdGLH:S%8?+xa ,jGIH/|Yd) z”ôˆÔ¡’´«¼ /bhÆ<UVa-8!#H]` czætþ÷ƒX!y-`K
-v-q /~# vs;l/<af-K=8CC:"z?5I/3I'#x8"#Pv+*. CkA\quz9R `$\r03
-?LkKKZÕ q€2Fl!R$\;ÝÍzÂó"ÏÄÈáwEbF|HsDLrUoaqhÕ[¨ôéXr*eAR\P{u\w /,swd=/w??SNz1M!P<"zN1E"^TawS2\OGOZW9x&Sendstream
-endobj
-3389 0 obj <<
-/Type /Page
-/Contents 3390 0 R
-/Resources 3388 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3387 0 R
->> endobj
-3391 0 obj <<
-/D [3389 0 R /XYZ 85.039 781.388 null]
->> endobj
-1238 0 obj <<
-/D [3389 0 R /XYZ 85.039 650.648 null]
->> endobj
-3392 0 obj <<
-/D [3389 0 R /XYZ 85.039 624.034 null]
->> endobj
-3393 0 obj <<
-/D [3389 0 R /XYZ 85.039 606.001 null]
->> endobj
-3394 0 obj <<
-/D [3389 0 R /XYZ 85.039 456.354 null]
->> endobj
-3395 0 obj <<
-/D [3389 0 R /XYZ 85.039 287.653 null]
->> endobj
-3388 0 obj <<
-/Font << /F62 1689 0 R /F15 1628 0 R /F56 1642 0 R /F35 1632 0 R /F20 1617 0 R /F70 2201 0 R /F18 2207 0 R >>
-/XObject << /Im1 2193 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3398 0 obj <<
-/Length 3144
-/Filter /FlateDecode
->>
-stream
-x]o8=@>t^k|,X,|%VhM!{T5 l7i:[.|#~GvyqSg* -7\1?_$I-y~{{Bypk__//G.B? "Ma*f02~7Z8]w[
-{k
-,23H!
-" ZW>|r['pp[#zQ@)<fX9:=5eFSCxQ4&3j%C<K.q0Y9+EK:u +HX9!"e8|G D9Z~8rb
-]>ttAq<E-+K?x pJS.ul0E!;zJ'4WF~Q:/S%BAxD*U~(q l\&b`7`J0
-#E
-juS] jZ/JLjY|YsMD)jp j](g`cO>!!S+Pa>_QYICeqbz+KE(6 -EbB
-~UMB~0s"]mP[6]`C%%5*Y'^Vg®(“½‘Fim_ e '+Vx B2D-_iV'%e4yZ
-(+'-5W3djbibXy=fzx!3uT2iqKGm*{@MZ[g;hA
-i-XA #ijIwd9#aat.*)U8JpOR&[ IDj0-y8YlyF&.2PvQZ!I zH]TOPq8{K+Cftd#`$03u1J}0myôiuÛ¹=SÎ/wƒþãvÄßÂ@VT
-gS?Le)
-k?1J83}%CsDri=5`2[_r|y_
-& 8 ZAIDEobUYt}DF/vendstream
-endobj
-3397 0 obj <<
-/Type /Page
-/Contents 3398 0 R
-/Resources 3396 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3387 0 R
->> endobj
-3399 0 obj <<
-/D [3397 0 R /XYZ 85.039 781.388 null]
->> endobj
-3400 0 obj <<
-/D [3397 0 R /XYZ 85.039 165.173 null]
->> endobj
-3396 0 obj <<
-/Font << /F62 1689 0 R /F70 2201 0 R /F18 2207 0 R /F20 1617 0 R /F15 1628 0 R /F35 1632 0 R /F56 1642 0 R >>
-/XObject << /Im1 2193 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3403 0 obj <<
-/Length 3539
-/Filter /FlateDecode
->>
-stream
-xZmoF_!8D*jK.
-/p-kJTI3$Es_fwgwYK,OfQ?g;[Q'P3a77'LN&;&~_9(7?\Jk4_Rbq
-}7n~<,zX_sg1I<{$mNt;M<yn353Qw8S4wi*PbGf=vqc5o9
-|YmpltI6 /Rg^<1t'g# 4?RofUFW6K<2"^$!}O JVaCZ$,h!5GtVEP,+%5,n-LUk Uim"i<q8Q vM<y4Tw/+UL1RRT
-}/dr?h3
-$ M mwŸ.·Èå ½dÞJWs/:<e+-Bb
-C Jm]!l+3*gt_v(M-Sc!s-rEJr+lZ:XId6oou3\\C/1[ii it56w"[ke"TS+Ow:M]T rki"S)l_{YlD#P!6T4,6fg GLgUyq`H .J| MM F{{A,81omXea9c`
-xUrh1<y#tpvWhHP-~G.XwuPTp1F.P8j!ObpQX.7+nù´‡Êî»!”}äž|7¦k«8<¸h…5t§èh’¥,®K,'ll09)V_Ns{t$]1fo] smwA8C:Ä ñFI L&ZP B'j
-<lne{:=<qx$=¼Ì3>Ïÿ\¥W,|X2@ ZakI M3Cj@l2sjS
-Vs.nnÑÜ£Ö£9”§åÉUGç6]WnSJ$960li\'vz -aRyQn;k0#y&j]dW1 =?s{4-R\;#] FR5l'`Nw_j>>T # cA_4 d4[\,]<+Du?oYV{*p P+t?o^ */*cZZN1fa=T%MmQ1Sd==Qv lno4hzaqcFYiAXKX\EsD>$'f2t"&T{Mh25q<; ri),Y9tF$$$w&7'x3:I|~7_m8L*qgKX
-q$;AMS4A|DfV'C6ZFOq-6iY5A!S
-8}/\UUXd26k#5d+ +$~f[Vw&>W/&'tgigg|+Bn*Fyd8z4ucQ@!!+C
-x\g&V! CF#BU\6ccpl 9Ú(P}b%CfPFZN>,X
- 3 1c.c,iC eg9fdN;(e<v+$B' LI+´fíþ‰¿ÓÛ4“vˆBY2b[S=:.9anr3M9Nk
-}8mIx
-? H"gTZ?YD=ocQw D 7 h9>R&pVc8np*Z/<Í5÷öÈH-cz Qj6/ZS \O}My
-endobj
-3402 0 obj <<
-/Type /Page
-/Contents 3403 0 R
-/Resources 3401 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3387 0 R
->> endobj
-3404 0 obj <<
-/D [3402 0 R /XYZ 85.039 781.388 null]
->> endobj
-3405 0 obj <<
-/D [3402 0 R /XYZ 85.039 761.463 null]
->> endobj
-3406 0 obj <<
-/D [3402 0 R /XYZ 85.039 705.373 null]
->> endobj
-3407 0 obj <<
-/D [3402 0 R /XYZ 85.039 517.54 null]
->> endobj
-3408 0 obj <<
-/D [3402 0 R /XYZ 85.039 278.584 null]
->> endobj
-3409 0 obj <<
-/D [3402 0 R /XYZ 85.039 247.5 null]
->> endobj
-3410 0 obj <<
-/D [3402 0 R /XYZ 85.039 229.36 null]
->> endobj
-3411 0 obj <<
-/D [3402 0 R /XYZ 85.039 198.883 null]
->> endobj
-3412 0 obj <<
-/D [3402 0 R /XYZ 85.039 180.742 null]
->> endobj
-3413 0 obj <<
-/D [3402 0 R /XYZ 85.039 98.16 null]
->> endobj
-3401 0 obj <<
-/Font << /F62 1689 0 R /F15 1628 0 R /F56 1642 0 R /F35 1632 0 R /F70 2201 0 R /F18 2207 0 R /F38 2158 0 R /F41 2104 0 R >>
-/XObject << /Im1 2193 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3416 0 obj <<
-/Length 3796
-/Filter /FlateDecode
->>
-stream
-xZmoF_aKeb[i^CDI<SJRvovIJhp3T!SY:L3,\/-xGxi07?$
-</o7vO/~Z/4^i5S>\7/_`@PuTrm|v&^ac?_G(u-õúâÃÅ¿Ü,Üf.y”‡·%Ѓږ: ²Ì8&UaTv9hpD.H/_WXk# U+^i.<^GVS<;SN^Lfu-KF+NNp.xBkfL{{w@ 'E]Zv+Uj'll\Y6-8s"ran–Å9‡MI
-] X:C_uhfZp'YzVaD  6+;
-{9yV~sg_6]-x(J`N].CWT [Y$l{{NFK)VXH>)uxBO(Xm~5</r(d7&M0-QMLJh?7 hN VRZ\B>j fy{B_x(zDF
-U?vWz uR9JER|58 q皹@¸óU]$ "-U8zlD(E;XSk\,e?v>~x-
-&&/&ik=^uNaM+Fsw"q}]1ngibO)pO&
-y TY,)r*x !$aiU4#n
-.I/q*`b@` ]*}8 ( {X~cb:~ 9tyzzDI T*?6N>9mAJMFDgr=Y3&q^@(#QVl,f*V@3 +nle.}g,;WW)FwdMJE&u@,1 Uz*=FYxZ12 U2mJv.8fu#&NmLuCQ ]09
-{4XXB ^O-&G
-nznAuuw1Qp7bg[9IGy%L&Y\B))H'3JC
-$3<0qU2TYQ[il]#O }5x8KX=#p[#!R3(0VAg"?<K(C0Q8XY?&B&]E1P2NzY)Q/r6 ""))J&A2q1'Q_o kL'Rkwj5gNw7;nY
-BW#V$yR_$W'!D:R NPV  +,B 71#^je Áw(õe³î=|”ͪ{š:r@tG [c5I\iridq0z *0i}HnR Lw<4AHCIq=\6ZfD'?z
-TH-ç¶# =ðTmnKhD)QbO1D a'CO
-< L_ e=lp!:M6EUHd+^BrZsGtH"b k'g^6_ Vs{bQl rNn! CP<
-SPrWU0=AO(&V\)F9M
-te( ?R^wTE_e#1d[
-&L9!yulQx 
-5V}3?<|u?)EIbl]ruOPMfM1u\EGHa@@#21|6[ 8FQH9ETtBub!C.RsyYAdJu1W;]('", '*IfSew;LS\ (cf (
-.%|&q&E nDarkG;{YmP)z!K+$
-l<"vc'"r?b!<9|=(T>Is[.rI&\Ξ:>+H*F'}aRdI
-<~L~~)-gwO,[  ]Y1gf1D|0i(|:yOZO>8~Lq`&$y x~p&&,?" ):GL?zK.(<s_jD_yzwIwendstream
-endobj
-3415 0 obj <<
-/Type /Page
-/Contents 3416 0 R
-/Resources 3414 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3387 0 R
->> endobj
-3417 0 obj <<
-/D [3415 0 R /XYZ 85.039 781.388 null]
->> endobj
-3418 0 obj <<
-/D [3415 0 R /XYZ 85.039 713.704 null]
->> endobj
-3419 0 obj <<
-/D [3415 0 R /XYZ 85.039 696.17 null]
->> endobj
-3420 0 obj <<
-/D [3415 0 R /XYZ 85.039 665.087 null]
->> endobj
-3421 0 obj <<
-/D [3415 0 R /XYZ 85.039 634.003 null]
->> endobj
-3422 0 obj <<
-/D [3415 0 R /XYZ 85.039 455.971 null]
->> endobj
-3423 0 obj <<
-/D [3415 0 R /XYZ 85.039 300.691 null]
->> endobj
-3424 0 obj <<
-/D [3415 0 R /XYZ 85.039 194.759 null]
->> endobj
-3414 0 obj <<
-/Font << /F62 1689 0 R /F15 1628 0 R /F56 1642 0 R /F35 1632 0 R /F41 2104 0 R /F38 2158 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3427 0 obj <<
-/Length 410
-/Filter /FlateDecode
->>
-stream
-xRMO@c{_=$má
-1·4›î³A |hN<W<Ó~M~?+1V#dq@##3Cw7ZYoER<~Rendstream
-endobj
-3426 0 obj <<
-/Type /Page
-/Contents 3427 0 R
-/Resources 3425 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3387 0 R
-/Annots [ 3430 0 R ]
->> endobj
-3430 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [212.407 723.034 369.551 734.724]
-/Subtype /Link
-/A << /S /GoTo /D (problems) >>
->> endobj
-3428 0 obj <<
-/D [3426 0 R /XYZ 85.039 781.388 null]
->> endobj
-1242 0 obj <<
-/D [3426 0 R /XYZ 85.039 761.463 null]
->> endobj
-3429 0 obj <<
-/D [3426 0 R /XYZ 85.039 736.911 null]
->> endobj
-3425 0 obj <<
-/Font << /F62 1689 0 R /F20 1617 0 R /F15 1628 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3433 0 obj <<
-/Length 2894
-/Filter /FlateDecode
->>
-stream
-x_QJmn`N0]I# *[i-DwuNP&/OI.Un
-ha0"#<,bs;J1qW p6qP@-p /a
-I(.
-)T;tXv*za$7M5=/;g\i3MwY0$J(
-I0nEp'\
-AE\(jf(9:mB8hx9be
-N7 T/o5TTN3'!IgJkfP+q14Xn(4``CEIqGyEktQI
-Z^RzQ3
-*yg-kDRV=s"H.F TAv\/%I0w
-nu*3Pjz:p"NC -f q2/vN{)|~,3FJA9 PF]h e&I (y-B:wCR|)D_}+.}xL ]eWICZeJbW}^wG14`q&
-kdz™€±håô(†ž“™9 £TB*e {^et^{kRN'QhLjE_LgZI{<spJRy+}lRotE|Ez\r&qeiOb<_(g~tQk_#}f e,
-UNLSxR5kQ1\`K*L \n;&N5_F?I}
-endobj
-3432 0 obj <<
-/Type /Page
-/Contents 3433 0 R
-/Resources 3431 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3439 0 R
-/Annots [ 3436 0 R 3437 0 R ]
->> endobj
-3436 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [389.071 266.298 509.276 279.199]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.tcpdump.org/)>>
->> endobj
-3437 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [137.104 239.199 260.036 252.101]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.ethereal.com/)>>
->> endobj
-3434 0 obj <<
-/D [3432 0 R /XYZ 85.039 781.388 null]
->> endobj
-1246 0 obj <<
-/D [3432 0 R /XYZ 85.039 761.463 null]
->> endobj
-2164 0 obj <<
-/D [3432 0 R /XYZ 85.039 642.137 null]
->> endobj
-1250 0 obj <<
-/D [3432 0 R /XYZ 85.039 586.947 null]
->> endobj
-3435 0 obj <<
-/D [3432 0 R /XYZ 85.039 557.543 null]
->> endobj
-1254 0 obj <<
-/D [3432 0 R /XYZ 85.039 131.639 null]
->> endobj
-3438 0 obj <<
-/D [3432 0 R /XYZ 85.039 84.97 null]
->> endobj
-3431 0 obj <<
-/Font << /F20 1617 0 R /F15 1628 0 R /F56 1642 0 R /F41 2104 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3442 0 obj <<
-/Length 2826
-/Filter /FlateDecode
->>
-stream
-xZ[o8~>I4ibv[GR&=7-YXd
-#~k@ ' *V:i\o;W*_|%2y_s0 b+/u69/ ^xENLQLY]@,
-[0%/*/Gnp
-((ÙG;0r|m]@7<a/Fpx"Y*c8'E:[p34cx+rDD[<5BRKO`=* neX >(hkÐ Rgbz +6\p_21'"/ .(&@hv!i(45"4^gDs%7cipU;93 WY"efk\9g6G`:%RfX8f>}CC M:]6P~ /.CAgAS6BiH5wHYB{=:+z+PoGY)kO%gi qytP`sk0yX<tK
-x
-Ppped#<-K(oue.c%vm5![US{?E{8v|(7PizC4BIdI@Rl'>&aazwNm
-ukE_[
-E
-Bn
-.dmh2hcMVD ©0Œz0¤Î©ôèù!ãd¿‹v sÑVW2kR\>i,@O8o2Lf[`V7&*_^v.)Z
-,Zd/J]RW N% ?w:)Ww~[d A86 El V|h7ea:(P"k!F
-9d0.|me)#DXCne<6d7T?~9 `OQ{Y1$Z4y]{s8+(n*vf|mL;p_'UBj,mr K]A<),
-$"{-(KpzKT(y
-
-be8 9Dkg: xpf_W#NR9iVJAB6je:TsJ'pt=P|@5TD /G"n8q=Qvoendstream
-endobj
-3441 0 obj <<
-/Type /Page
-/Contents 3442 0 R
-/Resources 3440 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3439 0 R
-/Annots [ 3445 0 R 3446 0 R 3447 0 R 3448 0 R 3449 0 R 3450 0 R 3451 0 R ]
->> endobj
-3445 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [237.74 247.707 322.248 260.609]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://samba.org)>>
->> endobj
-3446 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [376.679 189.127 512.306 202.029]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.skippy.net/linux/smb-howto.html)>>
->> endobj
-3447 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [138.589 178.305 194.521 187.873]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.skippy.net/linux/smb-howto.html)>>
->> endobj
-3448 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [231.213 139.513 412.479 152.415]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://bioserve.latrobe.edu.au/samba)>>
->> endobj
-3449 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [291.316 117.3 419.307 129.293]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://samba.org/cifs/)>>
->> endobj
-3450 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [247.013 94.482 434.521 107.383]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://mailhost.cb1.com/~lkcl/ntdom/)>>
->> endobj
-3451 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [288.68 71.966 504.006 84.868]
-/Subtype/Link/A<</Type/Action/S/URI/URI(ftp://ftp.microsoft.com/developr/drg/CIFS/)>>
->> endobj
-3443 0 obj <<
-/D [3441 0 R /XYZ 85.039 781.388 null]
->> endobj
-1258 0 obj <<
-/D [3441 0 R /XYZ 85.039 291.595 null]
->> endobj
-3444 0 obj <<
-/D [3441 0 R /XYZ 85.039 264.98 null]
->> endobj
-3440 0 obj <<
-/Font << /F62 1689 0 R /F15 1628 0 R /F41 2104 0 R /F35 1632 0 R /F20 1617 0 R /F65 2099 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3454 0 obj <<
-/Length 3364
-/Filter /FlateDecode
->>
-stream
-xZ[6~_}5D&mMf3.[%G{niYX
-<gk"_EE^Ef~{5}wRn/yz|w_YB:p~5`]~g#_lwu$(gk CPMa'-Bh~c$ luP5Ø{’xÛkjØî+Ro;. U]wKCC O;T~ k]GT40h'p.@]YC-m8C:)o7Ls_)iXmkZ40_\_n38W~%f\f%6[DBAimUq="]{=roWuX
-e0l 09}DoYmq,;QBg%3::C3T aHQ,s VB H
-)
-'q"iTBy8$;;ov!#zSZ<:«¬…h°V(6M{2wdy
-jXDg(GyzxCAt'iv.1PfIQ&('p\V])FbQX!gq^>?Jh9gH4,Qgc)[gdh5CwjpI;([M2 %~#6n?vxT%u@MynhY50.^:g 0~I<a9
-^lXX,/.H^N JhG_}i)=A/JV
-kW;P5DHrE?G8g"w==P`jB$
-kJ^eCA07`̦‰Š8OGA=,…¤àöE7^boR]m0pjGkA2$&=Nm )l(<yRgiD*7-q:_'D/[0#BWk+nlTgLTWh#zk1r$ yinFqUd5bdC9[I
-D#db<4OYG,dzZl -1 Z wpEFY{m]>F5.g<*
-UB>s`Qv`sbqi!V|0H&
-
-gm 
-oU`Al&[?0 AjO=PUq?Wfw#M0*e0=G[(y(—í Þ`ƒ!éÊbÅ¥¿ VWCn/[2lfy.[#% .
-Adj/-Z,,@ +HvqC+BLrQ4#'y%h#co[%<swX)C#- ^^@z5 X0i_jz8#z{_S Wkjprse^k*,;y/a5LQ,&,4l R=((/)_D.b8;l?a}zN;\,x)6ZZt{P .u\{8t$'&"zW)PbTbF$k *Pb'm8Ex\rcjO7p@NJ;'"@t8\vyD"xX{Nn¥áÚ]IiwRu\f>@A,F P#.0Dw6T(XGmiO~d}>[NbRLL&_X*'v[RvU-!beY"% yHDc̝Ä5—ÑT$0u6uG|I#VAN $ETjLR:cq&T|RJ/a)e NJL X #M{2YlXkJC/4:'.?'ar&PIhWpfooej(M;2@;tRZq-\ZSn
-Pi-1j/Fo" lwrov/on@JR]VdX
-ndFy2/#6[O#fi" C@
-.T.0x}kb?S762C)~.~DBg,c0x ;3?sI$NI
-O`iL"^
-2;ybi.1]"qa[ -8CN R5 '=t
-endobj
-3453 0 obj <<
-/Type /Page
-/Contents 3454 0 R
-/Resources 3452 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3439 0 R
-/Annots [ 3457 0 R 3458 0 R 3460 0 R 3461 0 R ]
->> endobj
-3457 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [390.793 722.731 484.421 734.724]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://samba.org)>>
->> endobj
-3458 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [335.18 682.084 480.851 694.076]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.samba-tng.org/)>>
->> endobj
-3460 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [218.97 105.796 325.417 118.698]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://lists.samba.org/)>>
->> endobj
-3461 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [111.316 81.425 133.339 90.993]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://lists.samba.org/mailman/roster/samba-ntdom)>>
->> endobj
-3455 0 obj <<
-/D [3453 0 R /XYZ 85.039 781.388 null]
->> endobj
-1262 0 obj <<
-/D [3453 0 R /XYZ 85.039 761.463 null]
->> endobj
-3456 0 obj <<
-/D [3453 0 R /XYZ 85.039 736.911 null]
->> endobj
-1266 0 obj <<
-/D [3453 0 R /XYZ 85.039 163.232 null]
->> endobj
-3459 0 obj <<
-/D [3453 0 R /XYZ 85.039 133.828 null]
->> endobj
-3452 0 obj <<
-/Font << /F62 1689 0 R /F20 1617 0 R /F15 1628 0 R /F35 1632 0 R /F56 1642 0 R /F41 2104 0 R /F65 2099 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3464 0 obj <<
-/Length 2671
-/Filter /FlateDecode
->>
-stream
-x}b` pk$Qaxc#=@yPw|}"f`*u;~/~(t!/P=
-~YA}ZU +7q`Xqt
-_m8 )KC<\G
- B'H Jq;+ 4|7c#]a_z8p+n<ehBrA)XsPbEhIP# 9_)J)n/6
-á±&¯¼—ã*xѽèbÝVe VbZ2hHnKg&E%ei $~.~ nz[G0\
-A1;[gR4+`=XTtq#R.Nt`O
->:g+[HG9IVPaFLC>` Q9 'UK-rQ|+2OI.w:dL>B9tuN@JT4QZta>ej=y~bCzDkvRü5„èQN3^uC%F(]Dza)oFEKln:0
-h)$,b2Ej2{|nSxUO0Ou9)YnoC_--?cr_~$m`~
-(O|t1.`|xYp8z@ƒêq¤*Ïy2Ë_>S7=o^dk[Aw@3)s=3H!x'MW1 6:\R#u^:89Jq T 85a dGXu)Xi4,0vAkz~/Z]MZ
-P05WM
-c'FtDXg|Qk9X`$F%SLCI-
-lG`K^ 8lAJn8q|eK>PlAWn
--e]:|KpE3Y7r#XqnUZqwKP318?%1f.>-=zW/CNVhB5+7adh'VUBK&r6^ 0NOc 9m7l 7.4'29_phnd]m**9i} 
-0aF '>?k0\nBA7a|OB0~sKaRFa?znHl]Lpy47dC_lF y?>>QU#%zc8Lr^?œJeR ! #D|p= P\}`4>jl wkúm;ï~kqBvZEJ9Cm~ MOLendstream
-endobj
-3463 0 obj <<
-/Type /Page
-/Contents 3464 0 R
-/Resources 3462 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3439 0 R
-/Annots [ 3468 0 R 3469 0 R 3471 0 R ]
->> endobj
-3468 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [232.013 625.659 270.975 637.349]
-/Subtype/Link/A<</Type/Action/S/URI/URI(https://bugzilla.samba.org/)>>
->> endobj
-3469 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [341.801 435.668 475.519 447.66]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://samba.org/samba/)>>
->> endobj
-3471 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [250.165 336.599 295.309 348.288]
-/Subtype /Link
-/A << /S /GoTo /D (diagnosis) >>
->> endobj
-3465 0 obj <<
-/D [3463 0 R /XYZ 85.039 781.388 null]
->> endobj
-1270 0 obj <<
-/D [3463 0 R /XYZ 85.039 761.463 null]
->> endobj
-3466 0 obj <<
-/D [3463 0 R /XYZ 85.039 667.044 null]
->> endobj
-1274 0 obj <<
-/D [3463 0 R /XYZ 85.039 667.044 null]
->> endobj
-3467 0 obj <<
-/D [3463 0 R /XYZ 85.039 642.326 null]
->> endobj
-1278 0 obj <<
-/D [3463 0 R /XYZ 85.039 420.224 null]
->> endobj
-3470 0 obj <<
-/D [3463 0 R /XYZ 85.039 393.913 null]
->> endobj
-1282 0 obj <<
-/D [3463 0 R /XYZ 85.039 282.629 null]
->> endobj
-3472 0 obj <<
-/D [3463 0 R /XYZ 85.039 251.104 null]
->> endobj
-3462 0 obj <<
-/Font << /F20 1617 0 R /F15 1628 0 R /F35 1632 0 R /F56 1642 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3475 0 obj <<
-/Length 3450
-/Filter /FlateDecode
->>
-stream
-xZ[~_1%7TQ@<wUV}` .;s8R4Pu|m
-pP<qo!&[ oOj`VvuU68ÙÀýgl·#S=UQ[.`1@
-9N<0>n+rLD`e"+ZBkO)oG+F-N{B2++JCov<G'b3c# ?@DPVo)GNyLtXcFG?V<%hnq[v 04
-l(ap+VJ#x7v]9&O+$%6fZa$Q<Fa'_NHCI=8>Nb5
-2B&W4hEsqLJCkjcLRR>3e:L}A,s!Nl(C=g-[em"^Itr$y Qqy(S^0a\&}WthY%SpqZ!+{\\~`5z|yW /t#W[] $3\+s S_p^f/Z?I*** RyMl%oW$.Z"dom0<;q3W5j4+GY4d &BOxSLWb\±Ñ÷âÒx“î¿í~å"^.–kϬ]®çñ)Ûår«@04JgP5(\dH0V'~_]cy]skt!5gA`'i"=Kxa
-/bI )#6u#EoTyH@Cn|$f#9 d h**kB
-@|.(zh;tblM [_LX
-C-+r *u
-Q5hsjyX)QKya1Lt
-o/ XtPH"Hrgto+)>B6RZD.; OPE0h!!qP_ |H;[\0s *bRY#&\J pK<63
-/ kJ@jI&h?B%QT=0C];r†) >¹­“7ÆVCO%HuZs'y
-Z+*_GFg*j]#k,c }:pO3n$#h3?(C~YgOk"D~K}SvIELu C C4r(Df_O
-Gux>*LSRCxqW
-+%:Ip*I49=r_s)U«‚A<H] )\* vY%W:63/UfJJ.K UUsVL$DXF0
-L{,3~g4q*><Rp3<!e0\.)|c1S[1PvAvIE8D urd[2vY]p__j&0[ulJ%I/mK>C+?\jendstream
-endobj
-3474 0 obj <<
-/Type /Page
-/Contents 3475 0 R
-/Resources 3473 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3439 0 R
->> endobj
-3476 0 obj <<
-/D [3474 0 R /XYZ 85.039 781.388 null]
->> endobj
-1286 0 obj <<
-/D [3474 0 R /XYZ 85.039 596.451 null]
->> endobj
-3477 0 obj <<
-/D [3474 0 R /XYZ 85.039 569.837 null]
->> endobj
-1290 0 obj <<
-/D [3474 0 R /XYZ 85.039 268.864 null]
->> endobj
-3478 0 obj <<
-/D [3474 0 R /XYZ 85.039 237.339 null]
->> endobj
-1294 0 obj <<
-/D [3474 0 R /XYZ 85.039 142.394 null]
->> endobj
-3479 0 obj <<
-/D [3474 0 R /XYZ 85.039 113.658 null]
->> endobj
-3473 0 obj <<
-/Font << /F62 1689 0 R /F15 1628 0 R /F35 1632 0 R /F56 1642 0 R /F20 1617 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3482 0 obj <<
-/Length 211
-/Filter /FlateDecode
->>
-stream
-xm?O1 sI.Ju-j;])SDy???P,%`p_"egv,
-f hY1OK#Z7
-V0Nm'}+h_OP x0Pt{n=U}#%E7bRv^8@v=c&`I`y"Rendstream
-endobj
-3481 0 obj <<
-/Type /Page
-/Contents 3482 0 R
-/Resources 3480 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3439 0 R
->> endobj
-3483 0 obj <<
-/D [3481 0 R /XYZ 85.039 781.388 null]
->> endobj
-1298 0 obj <<
-/D [3481 0 R /XYZ 85.039 542.44 null]
->> endobj
-3480 0 obj <<
-/Font << /F20 1617 0 R /F15 1628 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3486 0 obj <<
-/Length 2668
-/Filter /FlateDecode
->>
-stream
-xYKsW|1XB^{:wSV
-Y+^\)v\**?^/}7rkZ?P/*e4(eTPHR.5{X/Huj~i}VJGTu4b&"AymNw/_zxv'8J/(U)P5C7>=W&n}4hÒòRjACAQG=pRR!-M ;H%Alg 6cZq7O-ToYvOu_8 HL~\_FrP /FJw 9?6z(3W
-@9F[
-)`OOvX)
-8fR
-3%@) Z zEM*bM3% jbmڎ)
-Ù~Ьè†"›kISNq_o^6M| V<_`W$7gqzl|7d|)yV
-fzFK,D~s}'Lja@nDu$E0|G-N@mX8;G^<1x:/|xJb@01 T /X?U`Jafx<S^yjS\]Uk.Zª¦RU9b %Y/@x>;B<')ZUK<@$_k _~t1~+'ie_^/')qY[IzG`>tXr
-J`fRXMa((Z/I=\S 6vE_v"2Y=Y*Y1
-nH4U9yB1169QU5zYek=DW}{"\F3#&(
-endobj
-3485 0 obj <<
-/Type /Page
-/Contents 3486 0 R
-/Resources 3484 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3501 0 R
-/Annots [ 3489 0 R 3492 0 R 3493 0 R 3496 0 R 3498 0 R 3499 0 R ]
->> endobj
-3489 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [316.138 654.395 386.484 666.085]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://samba.org/)>>
->> endobj
-3492 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [435.86 506.629 512.306 518.621]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://samba.org/samba/cvs.html)>>
->> endobj
-3493 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [111.316 493.079 216.398 505.072]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://samba.org/samba/cvs.html)>>
->> endobj
-3496 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [195.316 312.568 375.35 324.56]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://samba.org/cgi-bin/cvsweb)>>
->> endobj
-3498 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [481.678 208.962 512.306 220.955]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.cyclic.com/)>>
->> endobj
-3499 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [111.316 195.413 210.671 207.406]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.cyclic.com/)>>
->> endobj
-3487 0 obj <<
-/D [3485 0 R /XYZ 85.039 781.388 null]
->> endobj
-3488 0 obj <<
-/D [3485 0 R /XYZ 85.039 761.463 null]
->> endobj
-1302 0 obj <<
-/D [3485 0 R /XYZ 85.039 761.463 null]
->> endobj
-2146 0 obj <<
-/D [3485 0 R /XYZ 85.039 667.044 null]
->> endobj
-1306 0 obj <<
-/D [3485 0 R /XYZ 85.039 625.403 null]
->> endobj
-3490 0 obj <<
-/D [3485 0 R /XYZ 85.039 598.788 null]
->> endobj
-1310 0 obj <<
-/D [3485 0 R /XYZ 85.039 598.788 null]
->> endobj
-3491 0 obj <<
-/D [3485 0 R /XYZ 85.039 577.795 null]
->> endobj
-1314 0 obj <<
-/D [3485 0 R /XYZ 85.039 478.811 null]
->> endobj
-3494 0 obj <<
-/D [3485 0 R /XYZ 85.039 457.917 null]
->> endobj
-1318 0 obj <<
-/D [3485 0 R /XYZ 85.039 402.208 null]
->> endobj
-3495 0 obj <<
-/D [3485 0 R /XYZ 85.039 383.734 null]
->> endobj
-1322 0 obj <<
-/D [3485 0 R /XYZ 85.039 298.299 null]
->> endobj
-3497 0 obj <<
-/D [3485 0 R /XYZ 85.039 280.129 null]
->> endobj
-3500 0 obj <<
-/D [3485 0 R /XYZ 85.039 107.945 null]
->> endobj
-3484 0 obj <<
-/Font << /F20 1617 0 R /F15 1628 0 R /F35 1632 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3504 0 obj <<
-/Length 2531
-/Filter /FlateDecode
->>
-stream
-xkoFP!I./>'BZ(W$%6 wggg=cgf?g,h]vn/g_^\+pgb;-L[|/|/>x7wxq]hg)0V:fO
-zBdv +/'Y)luFHmhd5S^?BJ|m%cLCxZ99z,XLb8 xG 3
-N\O5
-r4X{&D
-1bY2#!W.\Z
-?[*_z(<)DQM3mK|wew+,HS> n0l*!Bd
-\p3=l9L* S:Iy`A{dB-bkrh#jJMJ48I^<WR)L 0
-ojw!tYX,)fJKI(d$DMM6Q>7a8=h/V)Ucb_MZOsmcu>_C
-;t^&mWO:8Eg>G}:
-;Lzz#6@gk7 k*LK#L5%!F
--vm]tVUZOj~=F('$y;zf.r?4GHjC-_kuÇ|cpB8aWQHl&*Bqw{
-6<>aws_w% `fUI*G+}EgVk>TD]/²•­Ü×Ï}$­¦H:u )
-9TFvfP2.QR@ [y=i8\c ]P6Okd8>Nj`@P[lXM|liv0|!d\l"S>kh[T*T*B7At})Z6-]*idB>jZ%jBF
-`HdzG [.
-endobj
-3503 0 obj <<
-/Type /Page
-/Contents 3504 0 R
-/Resources 3502 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3501 0 R
-/Annots [ 3510 0 R 3511 0 R 3512 0 R ]
->> endobj
-3510 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [487.405 435.806 512.306 447.799]
-/Subtype/Link/A<</Type/Action/S/URI/URI(ftp://pserver.samba.org/pub/unpacked)>>
->> endobj
-3511 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [111.316 421.954 296.579 434.856]
-/Subtype/Link/A<</Type/Action/S/URI/URI(ftp://pserver.samba.org/pub/unpacked)>>
->> endobj
-3512 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [334.322 409.011 431.382 420.7]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://rsync.samba.org/)>>
->> endobj
-3505 0 obj <<
-/D [3503 0 R /XYZ 85.039 781.388 null]
->> endobj
-3506 0 obj <<
-/D [3503 0 R /XYZ 85.039 761.463 null]
->> endobj
-3507 0 obj <<
-/D [3503 0 R /XYZ 85.039 707.835 null]
->> endobj
-3508 0 obj <<
-/D [3503 0 R /XYZ 85.039 544.838 null]
->> endobj
-1326 0 obj <<
-/D [3503 0 R /XYZ 85.039 479.39 null]
->> endobj
-3509 0 obj <<
-/D [3503 0 R /XYZ 85.039 449.986 null]
->> endobj
-1330 0 obj <<
-/D [3503 0 R /XYZ 85.039 341.492 null]
->> endobj
-3513 0 obj <<
-/D [3503 0 R /XYZ 85.039 309.967 null]
->> endobj
-3502 0 obj <<
-/Font << /F62 1689 0 R /F15 1628 0 R /F20 1617 0 R /F35 1632 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3516 0 obj <<
-/Length 2197
-/Filter /FlateDecode
->>
-stream
-xYoB(¾I9]|4i"(W_k)> <gYp1K3_Y6|w 7fu$ZxjK$Gs7 C'My~dyu0yif9iP7RQ'oV`_y*\dG{_,f(U2/>]iX 2gY4(J.E/Pe5bEfC¤N!K #ML#.aK4o~ 5EI±³ûÅxäülóý:w¨,W]/m';~AU'y:{"WHQbX&/i_c-Q5wJ@Ti;5
-]mSy4(km]WyhW`./wh(;6]ghc;?U&y{e2B%DY!l^hf]$_?urV[g4I>YF oI,+Bt []H`%I@ LJ$LNB%V) ?X #fWfÊÏ …Šãp
-š‚TiHx0J]87vo[a=O (U>=
-k8P5NE*}!HhP>b% 6f0XaYL.bTb>{ >Y*AW=5F9
-WYTZ9Vxz+!
-e|JZ j
- = (e#.spL<MU8:UTYw3oE <Zzrg& )#Sb)G<'nfv66cc
-cå/âÿ×{‡òöp¼hŒ··¨ÒòƒÜøs§¯m…É®—cJR-keAp,> Kf^byJ4 B Ri ?5yj8 YpCsL_+x?#[sr;dA
-W<>i"laa6`j#itUfM}OX%o;f6]pf-`c ;Q4C3Z
-_Nozk*&f~xs) ljK! &z6 M8d°endstream
-endobj
-3515 0 obj <<
-/Type /Page
-/Contents 3516 0 R
-/Resources 3514 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3501 0 R
->> endobj
-3517 0 obj <<
-/D [3515 0 R /XYZ 85.039 781.388 null]
->> endobj
-1334 0 obj <<
-/D [3515 0 R /XYZ 85.039 570.951 null]
->> endobj
-3518 0 obj <<
-/D [3515 0 R /XYZ 85.039 539.426 null]
->> endobj
-1338 0 obj <<
-/D [3515 0 R /XYZ 85.039 281.354 null]
->> endobj
-3519 0 obj <<
-/D [3515 0 R /XYZ 85.039 260.158 null]
->> endobj
-3514 0 obj <<
-/Font << /F62 1689 0 R /F15 1628 0 R /F35 1632 0 R /F20 1617 0 R /F41 2104 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3522 0 obj <<
-/Length 2248
-/Filter /FlateDecode
->>
-stream
-x"<x}az'v+^t3\vJRv-?wiYEMyv;Wv83e;oWwo:v_8_o=_ady{3CWsz~w eW7gb?9Gg;dzòNiyqxOMP}h8G2Dz[8R //\
-dKlA
-uAobTI\x\r2{E={7s/s OLm)
- 7mdhN9{a9GDm@Ldp?Y&rb\(6
-89x17 u!#4 6( ZZc
-w ]84 :M[@&D)#kAeS;h$K
-/C
-ó-3Tcwo6xBe{H!`5e 4cR99f}OTe;2Iqi)7OG}jo) Q=bwI{$Eck+rh{> n O8EO Cc)`)9M,64Y])b"XMBq]!M6\80neB S~s}$U)jg<jwF^L@v%@yid7U3n(Ba@~L
-endobj
-3521 0 obj <<
-/Type /Page
-/Contents 3522 0 R
-/Resources 3520 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3501 0 R
->> endobj
-3523 0 obj <<
-/D [3521 0 R /XYZ 85.039 781.388 null]
->> endobj
-1342 0 obj <<
-/D [3521 0 R /XYZ 85.039 719.568 null]
->> endobj
-3524 0 obj <<
-/D [3521 0 R /XYZ 85.039 698.974 null]
->> endobj
-1346 0 obj <<
-/D [3521 0 R /XYZ 85.039 624.261 null]
->> endobj
-3525 0 obj <<
-/D [3521 0 R /XYZ 85.039 601.545 null]
->> endobj
-1350 0 obj <<
-/D [3521 0 R /XYZ 85.039 450.539 null]
->> endobj
-3526 0 obj <<
-/D [3521 0 R /XYZ 85.039 419.014 null]
->> endobj
-1354 0 obj <<
-/D [3521 0 R /XYZ 85.039 282.475 null]
->> endobj
-3527 0 obj <<
-/D [3521 0 R /XYZ 85.039 261.278 null]
->> endobj
-3520 0 obj <<
-/Font << /F62 1689 0 R /F15 1628 0 R /F20 1617 0 R /F41 2104 0 R /F35 1632 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3530 0 obj <<
-/Length 2194
-/Filter /FlateDecode
->>
-stream
-xYKsW Ce;O<rm9iS.
-?=hXl-?WdDG)5: R 9A &sZ Oh|zn?Wz_Ak:rNGF/\<yr
-7H37;7 GY]q3 } ippFâAqz~
-"WcN`u
-^yaiw((8sx ;c
-!!iQ5S=v
-"P%2_rX!Xp;N\X qpb5i5:g'#q
-B8h@=#Y9S)+T6S8%<+,{ Fo2=#h,z@R:[K(_fPPY_R`DBy=7(!pO=O!0W~4fN>,f`g,`"U$yv.sq- x`tBq(y79kw>S wo2_W"?TJ5v!XQkh1|GQ}"GsY^lgG< qS
-H{p3MpxqZ=jt ;nu,CGaK<GZ6X0Pc(e_t0k,R7#xM'.HHkoWoQ#r9|O\680`':"hV@!%!oEjrno]YC\,\_N{{GJ/FZf+.\X`m|tn!cJh^7?E¼ÞPmFE#h]B+L &2!%Q5w
-#bHg7C}S`W#HySv',&y8tnVo].^iTpJ0|AefVPq?N)VOR75endstream
-endobj
-3529 0 obj <<
-/Type /Page
-/Contents 3530 0 R
-/Resources 3528 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3501 0 R
->> endobj
-3531 0 obj <<
-/D [3529 0 R /XYZ 85.039 781.388 null]
->> endobj
-1358 0 obj <<
-/D [3529 0 R /XYZ 85.039 321.713 null]
->> endobj
-3532 0 obj <<
-/D [3529 0 R /XYZ 85.039 300.516 null]
->> endobj
-3528 0 obj <<
-/Font << /F62 1689 0 R /F15 1628 0 R /F35 1632 0 R /F70 2201 0 R /F18 2207 0 R /F20 1617 0 R /F56 1642 0 R >>
-/XObject << /Im1 2193 0 R /Im2 2261 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3535 0 obj <<
-/Length 563
-/Filter /FlateDecode
->>
-stream
-xTKS0Whh4x)$N}W}~jW@8~@Rtd2'Z>Fyp7Nhtfw${h]||M*%g 6gHoAtvy@<4 df$;(JSF-'"LF3pi%2G_YM5*a(vL;3XAMqL8 V"{E0a?uB!.-iLq aHJ:&:v~ +Wq¯wá°«
-/è¸~ì„ùWDsl"PkmaS, 5~^%&Xfmf}
-M?4vt{`Y
-%/7UVuwsm#ztOxu| [^;,VuP?v)(1G,a]aoEbI58K~P$ N=2.
-[
-endobj
-3534 0 obj <<
-/Type /Page
-/Contents 3535 0 R
-/Resources 3533 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3501 0 R
->> endobj
-3536 0 obj <<
-/D [3534 0 R /XYZ 85.039 781.388 null]
->> endobj
-3533 0 obj <<
-/Font << /F62 1689 0 R /F70 2201 0 R /F18 2207 0 R /F35 1632 0 R /F15 1628 0 R >>
-/XObject << /Im1 2193 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3539 0 obj <<
-/Length 2450
-/Filter /FlateDecode
->>
-stream
-xYIoF-0bbqeIO=H/!CI(\d>o+.1 f-}Rx_x~wiQ7] 3? Bk “k7»NJ}Fwk< l|Nw*$rB
-v;w >boz-[?Lh{l:boB7L,IR#'a|&s9Vò5ø €…syäfy®àæû‚çáÖL7 NQ4@{#R|q5n)N6>'$4Z@*,N~!j7'(B9"2vws=^,5Gjn?#\YiQD`%sji%ŽŎYE`gxy~EUW=Ú{¿áïJk4 !5;8q"[ 'h#r5H%hdK(]wf{&0PHFggRbbOi`Aue FGF)LwHX
-[j*=@v`n%5;2p{ "YH J*bljJO0heIiA\fwš‹ŽÇžœ·_|4]nw¢+éP{M7Xn gn05"Fz]Ka|z%X7J-=~X+pes Mtr
-=]m H ]twqd{gT GKi{2M/*6?O? <l'h]joDe,w, hA †z•E"$SFT#"\ifvX DP$@jN+y;[9{JXHb.M[ ,k@t:y2vRhiOtJ/g^= p>kq!.hL]h#eMqm g&|G%-c]JLGSopVmYyocGT!VKt}e%ny?[ P<%LO(!D'l`NP Rh]_AG+
- yH:"Z'hQ61&FPpC
-!)3"58t (Nb08$ u!Vq ) N[4P5*afH1sT)a8Qg2}o3,5ziptk lRuEo$w5eBm#*#dAaH_!gcP/f )XJ\&S<h0N<VpV rkNd2,) Tf5n< p1h ./mB. 0 PE eQ [:B*H=p4]f1+!_d
-1yJ6*~1GE[:JU})z~Jc|ßôl=¿ÉÇOnàc“ÖV80{L{|Y/` |[r s.(ILgL7&I+ s\/zNt U~A:gN 6=LY529zVgX4 [\ )wxTSQq9\j. 4S 4fj*3|+3LDi~IO=8GNo6)l]()åt Äkv–Ï6J~L4a=6#{__‘LAd%.KsqT3~q
-[q
-CT2t_8endstream
-endobj
-3538 0 obj <<
-/Type /Page
-/Contents 3539 0 R
-/Resources 3537 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3544 0 R
->> endobj
-3540 0 obj <<
-/D [3538 0 R /XYZ 85.039 781.388 null]
->> endobj
-1362 0 obj <<
-/D [3538 0 R /XYZ 85.039 761.463 null]
->> endobj
-3541 0 obj <<
-/D [3538 0 R /XYZ 85.039 646.155 null]
->> endobj
-1366 0 obj <<
-/D [3538 0 R /XYZ 85.039 602.617 null]
->> endobj
-3542 0 obj <<
-/D [3538 0 R /XYZ 85.039 571.092 null]
->> endobj
-1370 0 obj <<
-/D [3538 0 R /XYZ 85.039 461.651 null]
->> endobj
-3543 0 obj <<
-/D [3538 0 R /XYZ 85.039 440.454 null]
->> endobj
-3537 0 obj <<
-/Font << /F20 1617 0 R /F15 1628 0 R /F65 2099 0 R /F41 2104 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3547 0 obj <<
-/Length 2662
-/Filter /FlateDecode
->>
-stream
-xZIsWHUY %7/3&5JCCK$i
-~$S\A @$ mO'q~L gOp&D!]/~yS'W4enattu7u^M?~zucwLu>V`;L{L 0q9 .~d / d{]x,3^d{14|N75g4BvMq(gZX9AY9jwV^ih5y1gnd"UX HPi KID_LgahwaN]|TZNd<kU-%)JUXFwe _uUfBmyI"mnZ"Onj.-ZD6eD%Ff.+o2}opZ\]J  TGC
-*(gm]Ps`
-don|Vxs3re!t ,J kZE?yW_5bp, KJS)aTq;1*8c
-+ak< uq2((go<eE'aI2KUg=GTo6^8b}Ya"kzsT&C{Y \Gg6`XF99KQ-PD:\anP\`kV
-yAk Aj2; q$yjxPq7$ du_8bjn@G/_^4?]4f0 d3M$q`*Cr (^fC;`sKP (Kl( ?P;b3Sam|l@O;KQWshv6EXfD&mn"nyfC8Lq2 e} Nyt}Cl y1!'LL9g oL`$Xyh#<# }:pPm+vezf^?N^xS:KSxMc@z6Fgg5;DQT& F'`(aCMpB|[W5[wj%L".Hw;`X gs(8SiL<[RJ&|Ew,uS.Hw'8^{@:^Fb2v7#]s"P=(:C y9Mcs: /eo'LdQR"`h;3Wq?*NNxCFV ^aLWH1HB12(8<)
-  J}.%nE@1Q1i0F^;=|0#_G KfK(/0>#3 LjTa;P0r+J<6|N
-GF6WoT%oTR_pZX?8/_(5s]3 ?ND\y}y_( g894$' *Z=
-+wRg "d~F}' 3vcoit_D8~lIW?9Hendstream
-endobj
-3546 0 obj <<
-/Type /Page
-/Contents 3547 0 R
-/Resources 3545 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3544 0 R
->> endobj
-3548 0 obj <<
-/D [3546 0 R /XYZ 85.039 781.388 null]
->> endobj
-1374 0 obj <<
-/D [3546 0 R /XYZ 85.039 255.509 null]
->> endobj
-3549 0 obj <<
-/D [3546 0 R /XYZ 85.039 234.914 null]
->> endobj
-3545 0 obj <<
-/Font << /F62 1689 0 R /F41 2104 0 R /F15 1628 0 R /F20 1617 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3552 0 obj <<
-/Length 3822
-/Filter /FlateDecode
->>
-stream
-xZY8~_moL_]û03*C\lBH:Ry|8E,T1[q|D "apo,"*fwDrW7_ TpX<z;Up'~u0;>q
-ip~|yP)r" myrgGhGa\M0K7nft\Xq*BEaN*q6![q{vsoxT]@4GG#3Rmvhd`qTmcw%~Bbiy8(MUP5nasL}"?r<, l!_(NCN^=A IVOLEJ{;<F~ # Pr__{\Fm?YS f3[}oY 7mr<t,CEiu¾œ±Ûéf-ƒf·¯qqV*\$ o'QfB*,Sh3E4sVD@kOc
-#^2eW"NlB*[D.:J |u]uLC2b(m|Lld'Z&`@.sZ3XUjySJe a*
-v~p?"e-v@U xXP<m^$="+sXRfd1U^F87:P\2kh6)<wm7u^VI8}zU
-@oiI @w~p geF!-J4[kLv"r=-Y8{]b-u\8+j+urm*"!qmeC'&.VIyfKzV]x*zpSQ?YJ9D18T
-o'reUm"Y.I/RAHy P&a?<K+cre u0]%w"q~b%g2NKk
-[h.Lw`9%Z"w*=8 GC\5P@kt- [3(@xhtM^p6I4#57I%lcGI$aJy<4 Te8.va#O
-402|D+ :mv
-]‰èS:'ya8#c9l1>yëÕ^z»ú1Ú8Žɚ±çš/æ&©äž×*™è°ç'¯ OyI8`']G
-ZViq0Z
-< \W($"ed4mhh[L`v$mtj4$^ f$%VOhTa3.pN!* mo}?h9=3h&SB5y~)
-(c'+!(A+NA$7^bv,$1J+_! r0
-[\ E,[$%‰"•C
-_BF P",OI$j"[=m9rI|JbTe_r1$h6lu/qz'~@9^i%;j
-N0bH IhŸ;ÙÕъ‹< t4•5ð˓µåòЪÃÃö§ŸZ&^bl@uDDDEk5S&aX54jXIC!oOw_FNX'ScB">A#qoU{BJHT>&QHIp[2ol+ |:Zj `< tb
-a6,a^/A'M}BzOYZKXa3F
-&8Ru&h-isT|*'yq~p[k{Iis }[-eChN$/$Ty"
- I
-r*Zcy'l-.nOOF]*7l:]]<9]HswG~Q^JNu:-@^
-W+%3sNc1FM#6D+{*YWr}CR;Wa$?@w?SaI7/6_-endstream
-endobj
-3551 0 obj <<
-/Type /Page
-/Contents 3552 0 R
-/Resources 3550 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3544 0 R
->> endobj
-3553 0 obj <<
-/D [3551 0 R /XYZ 85.039 781.388 null]
->> endobj
-1378 0 obj <<
-/D [3551 0 R /XYZ 85.039 626.845 null]
->> endobj
-3554 0 obj <<
-/D [3551 0 R /XYZ 85.039 604.129 null]
->> endobj
-1382 0 obj <<
-/D [3551 0 R /XYZ 85.039 250.134 null]
->> endobj
-3555 0 obj <<
-/D [3551 0 R /XYZ 85.039 229.54 null]
->> endobj
-3550 0 obj <<
-/Font << /F62 1689 0 R /F15 1628 0 R /F20 1617 0 R /F35 1632 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3558 0 obj <<
-/Length 2202
-/Filter /FlateDecode
->>
-stream
-xZnF}W(bH./O'HA}`$FfK*IwnKQm]4Epo93??dxy|YG^Kd|rdrNQ;g9=y}43?8W'A\'SfGgeoG/-B5/a'?Ž<W%'zrV/Fc~kSb'n5A`%v Xlft\V vFY*mD.^TY7*Qaaj ~u%7N*v=Q!\[$d
-LfsS&u^qMIH,I*GqwEJ"xJq>[MBMa.nYGSn%0rUvMoqKrv]qAK` %KkKKF& ÌÒk”ô>¥à€Õ@gTVp:3Gu+ME{SW+omM`b6=E<sd V^[FeN_BQ`|Wx>RQIuSVh{ 4dCx.yPS"-,\n,Mw
- )DMx.*5>B"?1zoD
-4püTh)%p%e*G 9TC:kre!^_A w4ky\eiC-b]FX/Z7<p EL&Tpg02vS.(}q-6p=g<BEBkY$p+]WqF-WSxx_5DMkX>NOlI`s"Dti%/{jc
-2h|^Z
-;35%Ni!k Hj@:?:{)so:R~ ppS[? >4UX>7G;k>A`'KfR{r$|dH[5 A}<n4e.e<uf*f?rZR!oMf o:&WS\
-4 A>k+hv3e6{+mR=Z*y..`N0>'rwqI@jR~VznOgR*[+"7{#
-endobj
-3557 0 obj <<
-/Type /Page
-/Contents 3558 0 R
-/Resources 3556 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3544 0 R
->> endobj
-3559 0 obj <<
-/D [3557 0 R /XYZ 85.039 781.388 null]
->> endobj
-1386 0 obj <<
-/D [3557 0 R /XYZ 85.039 761.463 null]
->> endobj
-3560 0 obj <<
-/D [3557 0 R /XYZ 85.039 740.731 null]
->> endobj
-1390 0 obj <<
-/D [3557 0 R /XYZ 85.039 658.326 null]
->> endobj
-3561 0 obj <<
-/D [3557 0 R /XYZ 85.039 637.732 null]
->> endobj
-1394 0 obj <<
-/D [3557 0 R /XYZ 85.039 554.721 null]
->> endobj
-3562 0 obj <<
-/D [3557 0 R /XYZ 85.039 533.524 null]
->> endobj
-3563 0 obj <<
-/D [3557 0 R /XYZ 85.039 430.743 null]
->> endobj
-3564 0 obj <<
-/D [3557 0 R /XYZ 85.039 403.615 null]
->> endobj
-3565 0 obj <<
-/D [3557 0 R /XYZ 85.039 382.984 null]
->> endobj
-3566 0 obj <<
-/D [3557 0 R /XYZ 85.039 358.584 null]
->> endobj
-3567 0 obj <<
-/D [3557 0 R /XYZ 85.039 340.444 null]
->> endobj
-3568 0 obj <<
-/D [3557 0 R /XYZ 85.039 320.419 null]
->> endobj
-3569 0 obj <<
-/D [3557 0 R /XYZ 85.039 296.019 null]
->> endobj
-3570 0 obj <<
-/D [3557 0 R /XYZ 85.039 275.388 null]
->> endobj
-3571 0 obj <<
-/D [3557 0 R /XYZ 85.039 250.988 null]
->> endobj
-3572 0 obj <<
-/D [3557 0 R /XYZ 85.039 230.357 null]
->> endobj
-3573 0 obj <<
-/D [3557 0 R /XYZ 85.039 208.447 null]
->> endobj
-3574 0 obj <<
-/D [3557 0 R /XYZ 85.039 185.932 null]
->> endobj
-3575 0 obj <<
-/D [3557 0 R /XYZ 85.039 160.925 null]
->> endobj
-3576 0 obj <<
-/D [3557 0 R /XYZ 85.039 140.294 null]
->> endobj
-3577 0 obj <<
-/D [3557 0 R /XYZ 85.039 118.385 null]
->> endobj
-3578 0 obj <<
-/D [3557 0 R /XYZ 85.039 93.379 null]
->> endobj
-3579 0 obj <<
-/D [3557 0 R /XYZ 85.039 72.748 null]
->> endobj
-3556 0 obj <<
-/Font << /F62 1689 0 R /F20 1617 0 R /F15 1628 0 R /F35 1632 0 R /F65 2099 0 R /F41 2104 0 R /F70 2201 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3582 0 obj <<
-/Length 2193
-/Filter /FlateDecode
->>
-stream
-xmo6?ax4M.a(2“è‰%y’Ü4ÿ~w<Rm)<C
-<w{7D@8L&4/'V~pLCD
-^.&/~, ,{?_0lq]gDz7.i3{`&.3{! sCog/|I/~H"M~3._&i28`<M$TPj2BkvED Xc81K '0FAF{,pRi7Xcgg>vye>eY L|Lh%a,J`4=O7|h2nE 7MYXw
-
-;`<i,V ^ X `!,MsXck,BE#]DwlHE,y$2pqke+IhJyR:`Y[oqp.?QNb
-
-
-tc18 {J$$m<nJoV5}?'A!S,{W3xttTEOAC5dDP?# aTYz"WRW6@S \gks`w6`T$j(_";=Yp5
-O^K/[r0m$zw;Dhm>8w7U&d/}m[x7zUu*
--D;/X}WRTUUT7Xu=`s*OEr~<Tv
-s.&eT}X'oazVr&%YJ~G #
-
-mAU>ul<4WX-U(-R9<zets83.&`) }KFkz"~>{6:l)okc.TqH&_: m<wnjc2
-endobj
-3581 0 obj <<
-/Type /Page
-/Contents 3582 0 R
-/Resources 3580 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3544 0 R
->> endobj
-3583 0 obj <<
-/D [3581 0 R /XYZ 85.039 781.388 null]
->> endobj
-3584 0 obj <<
-/D [3581 0 R /XYZ 85.039 761.463 null]
->> endobj
-3585 0 obj <<
-/D [3581 0 R /XYZ 85.039 741.409 null]
->> endobj
-1398 0 obj <<
-/D [3581 0 R /XYZ 85.039 686.912 null]
->> endobj
-3586 0 obj <<
-/D [3581 0 R /XYZ 85.039 657.508 null]
->> endobj
-3587 0 obj <<
-/D [3581 0 R /XYZ 85.039 602.784 null]
->> endobj
-3588 0 obj <<
-/D [3581 0 R /XYZ 285.909 608.758 null]
->> endobj
-1402 0 obj <<
-/D [3581 0 R /XYZ 85.039 442.729 null]
->> endobj
-3589 0 obj <<
-/D [3581 0 R /XYZ 85.039 421.532 null]
->> endobj
-1406 0 obj <<
-/D [3581 0 R /XYZ 85.039 164.777 null]
->> endobj
-3590 0 obj <<
-/D [3581 0 R /XYZ 85.039 143.58 null]
->> endobj
-3580 0 obj <<
-/Font << /F62 1689 0 R /F15 1628 0 R /F20 1617 0 R /F56 1642 0 R /F38 2158 0 R /F41 2104 0 R /F35 1632 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3593 0 obj <<
-/Length 2091
-/Filter /FlateDecode
->>
-stream
-xYYoF~[)y,n}R+r%-$3{Pr
-AVqgJThBENGkf04g[A
-3LJO{hm[t;G7~0a&X $xqY+tr6h\'-2D-%>mp2A\D'@ 3&Ql$!rVo^a%v1 Nj/%l<78H; z:1;fwi/}U.{”ÛÖ»dôÝëˆ>Û¢‰7LZgDE,%pC
-oE\GUt}L#z-A /pa pC}D-Z,li7.h)~g1]NM6U'8¡®Ù¡/º´ã>°]¯bÐd;ý¥²Âò ¨BaLs`;SH>V[zSi{'~`oM¹Í%z¤†Ð8Žº‹F!!$"S&*:$G5rz/kX;~
-LeC)(eGK)rz7+9K|Wf[YN.\ WmJ]a1X&;Vd1.Ò)vð¡*³ö3¦j!¡¨ [ o ŠÐ|ÍJD*g){W\JoJc9oY-_+;}Z. VWWf!2vQ;;6%Y{ DK[I%cZC#zWWF@ "
-Zg\
-=©‹Uyr`aL|1jhh5J9x! ?h)[Jo]ke
-jPH+' n-TO on)CZpq]g5zoCMK^Rz:gpVW 4s9[ >3Y^8g-o~j%F7 8q6`5_N9 Vd!54Yr*SM
-\C`(#BX+7{Md];2z/P{R/ {e5=j2u8aYF;'{N rat\_^}q
-endobj
-3592 0 obj <<
-/Type /Page
-/Contents 3593 0 R
-/Resources 3591 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3544 0 R
->> endobj
-3594 0 obj <<
-/D [3592 0 R /XYZ 85.039 781.388 null]
->> endobj
-3595 0 obj <<
-/D [3592 0 R /XYZ 85.039 758.673 null]
->> endobj
-3596 0 obj <<
-/D [3592 0 R /XYZ 263.137 764.647 null]
->> endobj
-3591 0 obj <<
-/Font << /F62 1689 0 R /F56 1642 0 R /F15 1628 0 R /F35 1632 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3599 0 obj <<
-/Length 698
-/Filter /FlateDecode
->>
-stream
-xUKs0+8Hy6QL; #W%0vHgvVLC3 `B85=tu7c"B>$b<^lA@Yw`+Mf1rkV&jaldWZL-xM4Y
-.i9-v\oOBvOvg
-endobj
-3598 0 obj <<
-/Type /Page
-/Contents 3599 0 R
-/Resources 3597 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3601 0 R
->> endobj
-3600 0 obj <<
-/D [3598 0 R /XYZ 85.039 781.388 null]
->> endobj
-3597 0 obj <<
-/Font << /F62 1689 0 R /F35 1632 0 R /F15 1628 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3604 0 obj <<
-/Length 2614
-/Filter /FlateDecode
->>
-stream
-xYoFB}0D|>&q6>Fa%R>T,9][ 73koo,=WlU^f]xa
-k~a?{U8#R <%S9m9cgivn-wz< mx^~mxn++
-y
-/3(
-5Z"k+8P
-Df0C%tx.(AI,20Y#Z%(D5_cE,H
-U7upFk-'_8&=1yAl`¡6` So3-;"kXe
- N^s-/pcg\mg.yr_:T}#t.YFN; ]fb"VG]| k3o
-Nq
-T)F
- >mm';lBj8hhFUe(\W*0f!RpVB-% 1&\COu!Vol\|f)I<{Z^ N_?pg9$)
-yE(Ed6h
-~,F;\IKG)[<~ty )bLR3=
-plNsŽpE1+)O-So6R1-%2a{RhS;a8)gn_J}RteX$w<V 4 v31p17kîlFZU;SL0n8(%t%y`!(&6P"
-E^T%S :;T_F3O}l!
-'5x%v~z_MR&}9O<PO&igQ' yQl_Cs1'lQN E.$NZ}wIiYm06tE("5Oe}~kfd/n'{ eLvVO38hm(!&Z-Pbr7 0Sl:/-YL&U-
-z
-endobj
-3603 0 obj <<
-/Type /Page
-/Contents 3604 0 R
-/Resources 3602 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3601 0 R
->> endobj
-3605 0 obj <<
-/D [3603 0 R /XYZ 85.039 781.388 null]
->> endobj
-1410 0 obj <<
-/D [3603 0 R /XYZ 85.039 761.463 null]
->> endobj
-3606 0 obj <<
-/D [3603 0 R /XYZ 85.039 667.239 null]
->> endobj
-1414 0 obj <<
-/D [3603 0 R /XYZ 85.039 612.119 null]
->> endobj
-3607 0 obj <<
-/D [3603 0 R /XYZ 85.039 585.505 null]
->> endobj
-1418 0 obj <<
-/D [3603 0 R /XYZ 85.039 377.326 null]
->> endobj
-3608 0 obj <<
-/D [3603 0 R /XYZ 85.039 350.712 null]
->> endobj
-1422 0 obj <<
-/D [3603 0 R /XYZ 85.039 263.87 null]
->> endobj
-3609 0 obj <<
-/D [3603 0 R /XYZ 85.039 237.861 null]
->> endobj
-3602 0 obj <<
-/Font << /F20 1617 0 R /F15 1628 0 R /F35 1632 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3612 0 obj <<
-/Length 1134
-/Filter /FlateDecode
->>
-stream
-xWmoH_a>lz~AZR W;;qáîÐ)’=»;;ûÌÌ3ã õü¨ILx<VQA<I rv,`%8&\•eúýþüéëååÍÜçœ#ÎðÜýžSfqr98X\y#R
-q%Q;<(j(%ujNc3 p$cGMLaJm!R)ws}QkbDgUWst 3/"fV%|Z 4[S-U=--pcTaWWy91(^XNTvT E_WE~mSe<DH 4_l'Ee :-1QQ/z rQMt5W.?o6eX/o]f6;0Mjd`TmRrLbx8S#b8\z'@Qt]f e\9A5~8N'?B
-endobj
-3611 0 obj <<
-/Type /Page
-/Contents 3612 0 R
-/Resources 3610 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3601 0 R
->> endobj
-3613 0 obj <<
-/D [3611 0 R /XYZ 85.039 781.388 null]
->> endobj
-1426 0 obj <<
-/D [3611 0 R /XYZ 85.039 153.561 null]
->> endobj
-3614 0 obj <<
-/D [3611 0 R /XYZ 85.039 124.826 null]
->> endobj
-3610 0 obj <<
-/Font << /F62 1689 0 R /F35 1632 0 R /F15 1628 0 R /F56 1642 0 R /F20 1617 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3617 0 obj <<
-/Length 2003
-/Filter /FlateDecode
->>
-stream
-xXYoF~#<}siH@YDBRV;aE73JN <id1]i%DPMbO+/?9/0}3sV"|I]~w=syvz>:=?xbo'-<b |mv[ S^uFg+$3
-7Ys7s@[) mRq Ksp%w39<Pn7)\dMkz3,jv>uJ mpbIVaWbx{txU@-j 0v(vWUgNW
-:  !jtup0\Hd YWmP~@!|S(0xYB39X&:<@æËî@~srnEM"K# 86oI<[qV37"U MLC#&Gkd% !cw8w
-|O85@z d
-U389(TT}b@^>=*#@8]Z
-]`ls&0bì>×UVE\I tn;u-`<C(qCOH} p}89d 5bopT9MB )$jJYZz&4_In8Ih3R}yem'3Mqn#Fd`8f;:6x
-QW] qLHU )YK,YZQ|9, AeC<KPp1RUd
-MAO8G@ ^@W?^hGJjeTe
-endobj
-3616 0 obj <<
-/Type /Page
-/Contents 3617 0 R
-/Resources 3615 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3601 0 R
->> endobj
-3618 0 obj <<
-/D [3616 0 R /XYZ 85.039 781.388 null]
->> endobj
-1430 0 obj <<
-/D [3616 0 R /XYZ 85.039 679.868 null]
->> endobj
-3619 0 obj <<
-/D [3616 0 R /XYZ 85.039 651.132 null]
->> endobj
-1434 0 obj <<
-/D [3616 0 R /XYZ 85.039 651.132 null]
->> endobj
-3620 0 obj <<
-/D [3616 0 R /XYZ 85.039 627.814 null]
->> endobj
-1438 0 obj <<
-/D [3616 0 R /XYZ 85.039 584.48 null]
->> endobj
-3621 0 obj <<
-/D [3616 0 R /XYZ 85.039 557.865 null]
->> endobj
-1442 0 obj <<
-/D [3616 0 R /XYZ 85.039 557.865 null]
->> endobj
-3622 0 obj <<
-/D [3616 0 R /XYZ 85.039 534.548 null]
->> endobj
-1446 0 obj <<
-/D [3616 0 R /XYZ 85.039 343.346 null]
->> endobj
-2945 0 obj <<
-/D [3616 0 R /XYZ 85.039 324.475 null]
->> endobj
-3615 0 obj <<
-/Font << /F62 1689 0 R /F15 1628 0 R /F20 1617 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3625 0 obj <<
-/Length 3010
-/Filter /FlateDecode
->>
-stream
-xrF_*
-fWV[ (`g8[d>53E-wRj?v.q_LRoEG|'nS7'{#QN1&,YvepFQ=.w5h9KI !.`j@ {fbec>#I TTA /iOarQ)b'z8+sak¬àžPAö@K\&Hi2bdi^y8!IEpdA/.y#1 bssy'B[ =+"!~
-3O*Bvu,%W3
- ROGBaz6<n8\yZ|y>c/mLptX^<lj%r dvfòg (×›¼ôš€ìÔRoQ^.RzRZ%;THdeBgv E'TWkS|EC&?cyFC">83HL+pu~- )N4,[5x@q g1|vh <$k(eEB(!Egr.!fcfSgywo>3jmpR5 A?8LVQ eLco1^%]WC/NpH[w~fk]| oOy.C>}5X$P\^>WRPMG1*^&-pSlk4g= <Xs 0@<n(l-~.f>*[tR7$6*9( B5c[OG\Tr/WHN XFRa\P\~5V?~
-
-L$pPk8l"c08A&3#`Q7g
-f<9l@NX!Nxt7USH>HwCT8S>Qo5qf=7
-S#gU iL>R.q:YY[i,@5=-syxJ F>jY
-.||-|AmO<m>V$RW6Fgh
-s LrNPp)ljc
-xq{+
-IS>
-endobj
-3624 0 obj <<
-/Type /Page
-/Contents 3625 0 R
-/Resources 3623 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3601 0 R
-/Annots [ 3629 0 R 3630 0 R 3631 0 R 3632 0 R 3633 0 R 3636 0 R ]
->> endobj
-3629 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [135.619 595.065 177.399 607.966]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.thursby.com/)>>
->> endobj
-3630 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [370.468 595.065 403.066 607.966]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.thursby.com/products/dave.html)>>
->> endobj
-3631 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [466.071 487.277 509.276 498.967]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.umich.edu/~rsug/netatalk/)>>
->> endobj
-3632 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [132.201 473.728 157.678 485.418]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.cs.mu.oz.au/appletalk/atalk.html)>>
->> endobj
-3633 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [111.316 446.327 330.942 458.319]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.eats.com/linux_mac_win.html)>>
->> endobj
-3636 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [377.921 352.358 620.096 365.26]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://carol.wins.uva.nl/~leeuw/samba/warp.html)>>
->> endobj
-3626 0 obj <<
-/D [3624 0 R /XYZ 85.039 781.388 null]
->> endobj
-1450 0 obj <<
-/D [3624 0 R /XYZ 85.039 761.463 null]
->> endobj
-3627 0 obj <<
-/D [3624 0 R /XYZ 85.039 671.062 null]
->> endobj
-1454 0 obj <<
-/D [3624 0 R /XYZ 85.039 638.952 null]
->> endobj
-3628 0 obj <<
-/D [3624 0 R /XYZ 85.039 612.337 null]
->> endobj
-1458 0 obj <<
-/D [3624 0 R /XYZ 85.039 430.884 null]
->> endobj
-3634 0 obj <<
-/D [3624 0 R /XYZ 85.039 404.572 null]
->> endobj
-1462 0 obj <<
-/D [3624 0 R /XYZ 85.039 404.572 null]
->> endobj
-3635 0 obj <<
-/D [3624 0 R /XYZ 85.039 369.631 null]
->> endobj
-3623 0 obj <<
-/Font << /F20 1617 0 R /F15 1628 0 R /F35 1632 0 R /F41 2104 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3639 0 obj <<
-/Length 3280
-/Filter /FlateDecode
->>
-stream
-xZ[o8~2P
-[(K(JX)#S/  *AK0T hA
-8&m&upP9YZsJa`MM[p 6$L5* \BB..Z-mð¹©(T=S"c:FSaGybzetEV^p9l&S)=5(t6p
-®÷÷TP:BW>=EUGtY\Bf<*z"c"I~GYC)K("]O8_f3ZmfY^9%+(`5oRF7zzkeUH7.
-6T@v V%_zI 2_jx^ J [7kQ<5;E=9{=qJ:# *oBg%#O)tdP C9w'9*h:61Ff ]19^F7X0xIl Z <Bg@p,%9F7z \nJ!jl
-jV .Qw30@_ |@7}98CHs4A O-K!~L[L"6`d\MG6txabnSt;o4eih2¬.nºq£ÐTw#3v~~ cC%o7`W_B
-R8#Eiih @6^B@#.!$SS<DG8.eg~!Å`ä”È3,F "V0D4>{ G0BFU2t'SPwnf\ ~`2&8$)$
-zpC -.r2I2yecPP!K
-yO>7) .S1~b8B3d':@% b8i&Fd4Cc!'| l7^0Q$b
-jV&;A<<aM-6<>54[=!SC1R77w';{r!B^Dm_:ILP(c }g2L89Y=<v<'*L<_pZVpzGn}äbÌþ ö¡Ì&úœ Škýÿ6÷úmǍ ¶…JSN2Kove:4O:h![RAD8<M?J=<$ik0jS "2(}!}7^wHguG8NGZEUh:= {j 4Fczb_mj]OpXVr{|r8JqO|h Xì·u?P|{C.v55c_s[WzNY{$~> ?e"¼“¾ÈYDy g^BR:mV1Ve63zmr|HIp1[9 %A`w?YIG~(G
-N /o:`~P
-endobj
-3638 0 obj <<
-/Type /Page
-/Contents 3639 0 R
-/Resources 3637 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3601 0 R
-/Annots [ 3642 0 R 3643 0 R 3644 0 R 3646 0 R ]
->> endobj
-3642 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [443.558 712.238 717.944 725.14]
-/Subtype/Link/A<</Type/Action/S/URI/URI(ftp://ftp.microsoft.com/BusSys/Clients/LANMAN.OS2/)>>
->> endobj
-3643 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [129.766 698.689 348.214 711.591]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://carol.wins.uva.nl/~leeuw/lanman.html)>>
->> endobj
-3644 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [338.851 552.836 555.269 565.737]
-/Subtype/Link/A<</Type/Action/S/URI/URI(ftp://ftp.cdrom.com/pub/os2/network/ndis/)>>
->> endobj
-3646 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [382.155 461.982 612.784 474.884]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://carol.wins.uva.nl/~leeuw/samba/fix.html)>>
->> endobj
-3640 0 obj <<
-/D [3638 0 R /XYZ 85.039 781.388 null]
->> endobj
-1466 0 obj <<
-/D [3638 0 R /XYZ 85.039 761.463 null]
->> endobj
-3641 0 obj <<
-/D [3638 0 R /XYZ 85.039 729.511 null]
->> endobj
-1470 0 obj <<
-/D [3638 0 R /XYZ 85.039 527.745 null]
->> endobj
-3645 0 obj <<
-/D [3638 0 R /XYZ 85.039 492.804 null]
->> endobj
-1474 0 obj <<
-/D [3638 0 R /XYZ 85.039 407.672 null]
->> endobj
-3647 0 obj <<
-/D [3638 0 R /XYZ 85.039 385.811 null]
->> endobj
-1478 0 obj <<
-/D [3638 0 R /XYZ 85.039 180.551 null]
->> endobj
-3648 0 obj <<
-/D [3638 0 R /XYZ 85.039 151.147 null]
->> endobj
-1482 0 obj <<
-/D [3638 0 R /XYZ 85.039 151.147 null]
->> endobj
-3649 0 obj <<
-/D [3638 0 R /XYZ 85.039 129.954 null]
->> endobj
-3637 0 obj <<
-/Font << /F62 1689 0 R /F20 1617 0 R /F15 1628 0 R /F41 2104 0 R /F35 1632 0 R /F56 1642 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3652 0 obj <<
-/Length 3198
-/Filter /FlateDecode
->>
-stream
-xZYo~
-.m,Fu4DIHZh
-, ij^NfeZ.>#Z0K=,@CTj}j?xj<s'5U~PY7< YNa|îNQe0c\k$x*OL$~{r.
- X<
-{B%rS3Q9%/w&ys@^- &x&1nU=},[G Bk p%>&tv?mE
-P9+e% / 32`&A#\k |`]=)E7?D 7`M]8uH.HmeJ--)sgCWu`w(vf^h K wRgq!`]-Zyvj9"id
-r>>8xRd2g8?@1"OmE/rvz
-! t$F8=y%qF76U$;*k j3ø`éÿÆ…>·>ÑØÁd«7
-¬c:Ο#€0þÍì‚ô[ûftÃ#‚1M 4jc*J\NqKD"e*e.kAsW:))ïü²]Ñ ƒðÇRo"-*e"[,ETHK%bBjLk$/` X r}IM]#{5zTJ=HE~
- YkuEZT 694lX<| s$_0q{x>p)Qh
-c/+)W
-w~IRRpA>21-;5`5C)X}KSCF `?HZ9nxt9A9g rJsv<$e#H6I(Ym\+p.<sj9~<xoLhrSD*1k]7+D Tp3Y9ZK8TM.Wjh6GM`X
-U3I2XF?Y`y=C_?2Aendstream
-endobj
-3651 0 obj <<
-/Type /Page
-/Contents 3652 0 R
-/Resources 3650 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3661 0 R
-/Annots [ 3657 0 R ]
->> endobj
-3657 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [394.325 421.418 452.136 434.32]
-/Subtype/Link/A<</Type/Action/S/URI/URI(file:smb.conf.5.html)>>
->> endobj
-3653 0 obj <<
-/D [3651 0 R /XYZ 85.039 781.388 null]
->> endobj
-1486 0 obj <<
-/D [3651 0 R /XYZ 85.039 708.207 null]
->> endobj
-3654 0 obj <<
-/D [3651 0 R /XYZ 85.039 684.889 null]
->> endobj
-1490 0 obj <<
-/D [3651 0 R /XYZ 85.039 575.05 null]
->> endobj
-3655 0 obj <<
-/D [3651 0 R /XYZ 85.039 553.853 null]
->> endobj
-1494 0 obj <<
-/D [3651 0 R /XYZ 85.039 471.112 null]
->> endobj
-3656 0 obj <<
-/D [3651 0 R /XYZ 85.039 449.916 null]
->> endobj
-1498 0 obj <<
-/D [3651 0 R /XYZ 85.039 380.724 null]
->> endobj
-3658 0 obj <<
-/D [3651 0 R /XYZ 85.039 358.863 null]
->> endobj
-1502 0 obj <<
-/D [3651 0 R /XYZ 85.039 290.335 null]
->> endobj
-3659 0 obj <<
-/D [3651 0 R /XYZ 85.039 269.139 null]
->> endobj
-1506 0 obj <<
-/D [3651 0 R /XYZ 85.039 158.125 null]
->> endobj
-3660 0 obj <<
-/D [3651 0 R /XYZ 85.039 127.924 null]
->> endobj
-3650 0 obj <<
-/Font << /F62 1689 0 R /F15 1628 0 R /F20 1617 0 R /F41 2104 0 R /F56 1642 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3664 0 obj <<
-/Length 2875
-/Filter /FlateDecode
->>
-stream
-xYo8_adf)Q!Mnv&}P,"[^Ino(Iq{C|H  Jd0}ex0] F7`kd0#I;jrv=c<cp4?=Fr</g0rw7L?8?8~zt6 0
-U/_ !=$ZI2X(é—G7GwX8YA14Vq
-
-cU[^J6p,m0ohNgR
-J:Jd~JW' 45vy=CoOH^5\9z-8GGhRu>m"CVv0#e4jKKM Q#
-A'(#iIxWbN28PN03XlSz8)Mkq+faxl (.a~PmdC#?>u.a$ `W d?#bA5Yr(/§“ŽÆdÄÅjhȱÀÔßò…Sp>d }9-TK91P,4/ y*eWLY-: c#U 1g56 B4hy8Nfu
-gMD#&nP3Jc<sp plLU-+a h˼¡¢
-ß<¯e´æóÃö·¡µL(u# E adYqW3( xJ\ X(%g**^eU[*}=L2:QZkvF;WN9!K SLq#eRFi0CgAL3~h`F9)aMajcDQV.wzyZ7}2,*R}' / 2\`,~U2Uf$n2</c4LHWe
-Y[)c+8 br$ lT4^.Xkcg$lj"z!d!KwGk=Nw 0rHE@,07F%RSN\tG2[L9t0Vl!x 434_she!$<5meX{L;U+ Q\Hy$KgEs|8>3j5Äéå|Ot08cRJPActi*c
-
-urSGA%<TdlbC-C25_ ke%+?F%gWPZ}| ybf~fipar'l`uog&0#=p5.^qFu1F iP{^P
-5 Ud |t;7X,sGK$R:(~(9zh[ l ;SLR(OWf\/SA07g~ j(// M }B nw~"2v6uH+h.LN'C:J <V& A
-dn6*` OtO i=7&jPwJjK1X L-z*X6It9ö+h
-1¡³šq É/â®XCnE({@55@A;jO7l  Ps.RuOA$/lm-([X7x!R]U<Ndb9-3As!f GoukH^8^{/n5=-W{Ow~
-endobj
-3663 0 obj <<
-/Type /Page
-/Contents 3664 0 R
-/Resources 3662 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3661 0 R
-/Annots [ 3673 0 R ]
->> endobj
-3673 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [148.895 332.993 206.706 345.895]
-/Subtype/Link/A<</Type/Action/S/URI/URI(file:smb.conf.5.html)>>
->> endobj
-3665 0 obj <<
-/D [3663 0 R /XYZ 85.039 781.388 null]
->> endobj
-3666 0 obj <<
-/D [3663 0 R /XYZ 85.039 761.463 null]
->> endobj
-3667 0 obj <<
-/D [3663 0 R /XYZ 85.039 743.9 null]
->> endobj
-3668 0 obj <<
-/D [3663 0 R /XYZ 85.039 721.384 null]
->> endobj
-3669 0 obj <<
-/D [3663 0 R /XYZ 85.039 698.868 null]
->> endobj
-3670 0 obj <<
-/D [3663 0 R /XYZ 85.039 675.747 null]
->> endobj
-1510 0 obj <<
-/D [3663 0 R /XYZ 85.039 579.025 null]
->> endobj
-3671 0 obj <<
-/D [3663 0 R /XYZ 85.039 555.707 null]
->> endobj
-1514 0 obj <<
-/D [3663 0 R /XYZ 85.039 498.823 null]
->> endobj
-3672 0 obj <<
-/D [3663 0 R /XYZ 85.039 472.209 null]
->> endobj
-3662 0 obj <<
-/Font << /F62 1689 0 R /F15 1628 0 R /F20 1617 0 R /F56 1642 0 R /F35 1632 0 R /F41 2104 0 R /F73 2564 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3676 0 obj <<
-/Length 762
-/Filter /FlateDecode
->>
-stream
-xUMo0 WhKilk P:NjVY?4u;`EHJ|$iN8Ie8T& +%X.=y0QNSB 5t;j=a',?;j §>›\̜þìËd<Mg}z
-&"w8 UFqBDL{3N_)D+%?FO- BCS4v g)z 8Z"%  =, "}X lx
-Vq5H\y]dM`7bX& 1-prl RrV=dNhl¾qŠ…
-endobj
-3675 0 obj <<
-/Type /Page
-/Contents 3676 0 R
-/Resources 3674 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3661 0 R
-/Annots [ 3679 0 R ]
->> endobj
-3679 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [165.346 582.508 348.339 594.198]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://support.microsoft.com/default.aspx?scid=kb;[LN];Q103765)>>
->> endobj
-3677 0 obj <<
-/D [3675 0 R /XYZ 85.039 781.388 null]
->> endobj
-1518 0 obj <<
-/D [3675 0 R /XYZ 85.039 634.486 null]
->> endobj
-3678 0 obj <<
-/D [3675 0 R /XYZ 85.039 612.724 null]
->> endobj
-3674 0 obj <<
-/Font << /F62 1689 0 R /F70 2201 0 R /F18 2207 0 R /F20 1617 0 R /F15 1628 0 R >>
-/XObject << /Im1 2193 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3682 0 obj <<
-/Length 2515
-/Filter /FlateDecode
->>
-stream
-x6X-: Ed<lkGG|E>:ZEX,]_ltV F)7
-C,*\/L$j
-B7[Çj±Þæ:ÿì¨Ð]®¢Ès^>-³Àùÿ­—+'Ί?ëC7TSl_
-x\ ^xS:B7l
-K.A!Wu'99B5pF,shGn
-c 3Jb,}Lâ$#Žý°üC<1EUKHA"f,d%'m*c=pl8[BLC ~{9?{sAB 9Ln`^o\G&lL3{%2UXLxk1Q^4O<5uC<qH,iCtkEs{piQCq&l%dE3&27;8(%w+.PcG> +4l=svAXCua<LL0  /
-x[t> C/2xV0P8[fKS>p n"$eMrv|e<*^ <}ah{oSC abV6 gX(yYB{1S%9Jw9cm(];{xT1b`Syd$?j{C15{
-0
- 9^ >pp,VRIo0 kdVMCF+\}$6 2 n"|8qMD.M _Ei'UY8~-'e±Œ«§—§ßçt<è*’¡MaHT"hGirOJ,yPNc*B
-o ,S:qM<\[`h127!"Od[
-A"0L-;18ij H(E< 
-o  /Sz-x@jA,\{~3kI\+ B': 7yfh8f V`
-q
- h<X5YOS+7}`[D5*pk_YVE z3[qi r)tlrJD ^[M6=7DG7<]4XB3J)fykAsz.k[[J!hr(V!}w4DQ(o_!M`Cnt
-"[EWJb0=`z {Iia]f rH!_2a
-endobj
-3681 0 obj <<
-/Type /Page
-/Contents 3682 0 R
-/Resources 3680 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3661 0 R
->> endobj
-3683 0 obj <<
-/D [3681 0 R /XYZ 85.039 781.388 null]
->> endobj
-1522 0 obj <<
-/D [3681 0 R /XYZ 85.039 761.463 null]
->> endobj
-3684 0 obj <<
-/D [3681 0 R /XYZ 85.039 646.155 null]
->> endobj
-1526 0 obj <<
-/D [3681 0 R /XYZ 85.039 532.75 null]
->> endobj
-3685 0 obj <<
-/D [3681 0 R /XYZ 85.039 506.136 null]
->> endobj
-1530 0 obj <<
-/D [3681 0 R /XYZ 85.039 261.65 null]
->> endobj
-3686 0 obj <<
-/D [3681 0 R /XYZ 85.039 242.982 null]
->> endobj
-3680 0 obj <<
-/Font << /F20 1617 0 R /F15 1628 0 R /F70 2201 0 R /F18 2207 0 R /F35 1632 0 R >>
-/XObject << /Im1 2193 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3689 0 obj <<
-/Length 2402
-/Filter /FlateDecode
->>
-stream
-xYo6_a'*E=8i7d bH#D]Ic &e"Crf8!#&.I8L&Q,l}NV0w0O7d$E-L(TXS!5ZZ|8>rfL=gs12.sG@zwP|NrI<AuDL'~ _Ocgqd0bvV^,mZ.QxXn!k5+U}]³|]ÖÜ\(U9).P:\j{m^c8fSn([>N{^ui
-nXe{5kQe64KMD
-$Z, %"@F22mL Umyq_-W
-J#.r38$G8>[MfnFcxa-(LMI^
-A e+M&CJ }'g1%K7PAQt))Hy~2#XdDHZ7 = sgi
-3/
- z@{
-`L8  -{2f"6\W~)0t{m6tzK;;JFbj3 /(9O4ENoh+v[vN< nz KTbsNRP3EfM8(F3_9pq)x-.5ra3G)vtCK>
- H=R/of)!g^[)nMAJ! î’T:z:3]c+BGE8/Ft }
-S:wY?9.4
-endobj
-3688 0 obj <<
-/Type /Page
-/Contents 3689 0 R
-/Resources 3687 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3661 0 R
->> endobj
-3690 0 obj <<
-/D [3688 0 R /XYZ 85.039 781.388 null]
->> endobj
-1534 0 obj <<
-/D [3688 0 R /XYZ 85.039 328.501 null]
->> endobj
-3691 0 obj <<
-/D [3688 0 R /XYZ 85.039 307.304 null]
->> endobj
-3687 0 obj <<
-/Font << /F62 1689 0 R /F35 1632 0 R /F15 1628 0 R /F65 2099 0 R /F56 1642 0 R /F20 1617 0 R /F41 2104 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3694 0 obj <<
-/Length 2890
-/Filter /FlateDecode
->>
-stream
-xZIsFWp|-+¶RqMer
-o^O)Md4%/xx4VRyz>~x=/}Os{s{ n`VN|q=Q? .~­à…?_x®Ÿ˜Ñڞ«’dT^/Sx.&M
- Ujtz#[6_  #
-)Us1`cvUfSVZ4;ZE)Vy'$Ag  z9WhiLBa^w7t/l_t;QkUFhA Xgi15@{'NB]"o1{bt"'{os0j
-B>&Fi
-'+3Zt"%\gfXaexrA"l30GKIZW ;-m%8' rBhN7`HG]uXu2I%NS h>[-;?QJS Fd}r%QRH<gDFbO!&.)Bjg|Nk(T@"|BM Wxi GrNA;%)q0bsJ Zfl@Z!_S_
- .4t>éQ_p1%v.c(K9jT1i2
-endobj
-3693 0 obj <<
-/Type /Page
-/Contents 3694 0 R
-/Resources 3692 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3661 0 R
-/Annots [ 3697 0 R ]
->> endobj
-3697 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[0 1 1]
-/Rect [386.344 563.626 509.276 576.528]
-/Subtype/Link/A<</Type/Action/S/URI/URI(http://www.ethereal.com)>>
->> endobj
-3695 0 obj <<
-/D [3693 0 R /XYZ 85.039 781.388 null]
->> endobj
-1538 0 obj <<
-/D [3693 0 R /XYZ 85.039 681.066 null]
->> endobj
-3696 0 obj <<
-/D [3693 0 R /XYZ 85.039 659.87 null]
->> endobj
-1542 0 obj <<
-/D [3693 0 R /XYZ 85.039 390.685 null]
->> endobj
-3698 0 obj <<
-/D [3693 0 R /XYZ 85.039 372.017 null]
->> endobj
-3692 0 obj <<
-/Font << /F62 1689 0 R /F35 1632 0 R /F15 1628 0 R /F20 1617 0 R /F56 1642 0 R /F70 2201 0 R /F18 2207 0 R /F71 2204 0 R /F41 2104 0 R /F65 2099 0 R >>
-/XObject << /Im1 2193 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3701 0 obj <<
-/Length 3154
-/Filter /FlateDecode
->>
-stream
-xZIsFWVYt7=q*3j|HrD$8
- q®ã¨û÷¯ï¹ùÓ¨¾æòý÷ï¡ònq§‚ï>¼ÃX#4~?~i7o'85{t[ BS(G*M0Y/ftgG",t27Fg
-AA^<j XnA
-`ELj]eq&/=PF<
-<$J:Jrrm *Vrh "vQE+p|1GMo$lz htQGP@@s@T<r
-CO3"4*>" CECVZH_X=gl$G
-u~|l< MD 18$x)hH[>Ymjftm0gVA]6I\i2 r4 A@ dB!mjveXz;4t2Hm&:!xKRL@e-1A %9T.l6ZQF_ W*um3spI u.,EATgLV~Q~!b?G/kC<)[
-^Q16&4U6]s·o]}$5* ³(™bëN4_'3V(C5g$(r'I\?v{ s2=Y i(L]S8!>"o&r@Y .Wk[D\
-)m#H]Vs:\ BH6
-~}Kanl6anNL
-0*085vHQX)[J 'mhk.-, g\vez#7y}vUHL\dr#{cIi%)o$jJ
-0K7ó(¬Y0<Z$ZbuT%<vqiHM3N'{Ug{PZ{,[,A)J:La} !c3"rNoQ_@i 5\I>!\ 9^Jd',3l1
-{K!`bHtB,ca11xv1&vH(H{sB <V4K*B[3:|uI6u,"*ZQ"q KN1K789mHD{+}xR~eqG26f^);lxK V8 AGg z$j  6!F:O'6-I-=k.Lª>^há­å\
-.IfSwe?2
-Q QP
- TFLa{<65 x `?/@imv,ECk+`EB_jo_<5J~X\\6}_q8 M" r- I@J+:(c)] mNng]csVhi O< `
-. 6o$XP[QnYkB(D zQ'y)
-yU^[h 94Lg[P|b S#)l[GI:$54+Dm
-]/!&i9cGQOR,QcQ3UG"l#-~h)}>A27M6I1pgWuL\wui)}hz\&W]R: @QdKQoN4`edlJ+ _K5u}%V v+!37NTK;FV?wh
-endobj
-3700 0 obj <<
-/Type /Page
-/Contents 3701 0 R
-/Resources 3699 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3708 0 R
->> endobj
-3702 0 obj <<
-/D [3700 0 R /XYZ 85.039 781.388 null]
->> endobj
-1546 0 obj <<
-/D [3700 0 R /XYZ 85.039 761.463 null]
->> endobj
-3703 0 obj <<
-/D [3700 0 R /XYZ 85.039 741.134 null]
->> endobj
-1550 0 obj <<
-/D [3700 0 R /XYZ 85.039 644.777 null]
->> endobj
-3704 0 obj <<
-/D [3700 0 R /XYZ 85.039 623.581 null]
->> endobj
-1554 0 obj <<
-/D [3700 0 R /XYZ 85.039 515.796 null]
->> endobj
-3705 0 obj <<
-/D [3700 0 R /XYZ 85.039 494.803 null]
->> endobj
-1558 0 obj <<
-/D [3700 0 R /XYZ 85.039 314.22 null]
->> endobj
-3706 0 obj <<
-/D [3700 0 R /XYZ 85.039 293.629 null]
->> endobj
-1562 0 obj <<
-/D [3700 0 R /XYZ 85.039 156.625 null]
->> endobj
-3707 0 obj <<
-/D [3700 0 R /XYZ 85.039 135.428 null]
->> endobj
-3699 0 obj <<
-/Font << /F62 1689 0 R /F20 1617 0 R /F15 1628 0 R /F65 2099 0 R /F56 1642 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3711 0 obj <<
-/Length 957
-/Filter /FlateDecode
->>
-stream
-xVKo8WH^<:iMI
-l4OPr |05$S%+CQ*\ln _'`A[L*p2 p`( :
-w][È<¾'[ œDpKQd0E $c30Dm=6}$Mrlq-TIV1+amjEqn2Z-Pg[aO9[YHEK.O85?Q)'Z@LBYtyFV8:hOY sgAGE{rbq90)K{G:;RfcUJHQl ptNe,^mig9T'`;>`5nZi'^=[mly 3z+bAXkPHl\L/y6y w'!ce(Bwb\K=9ge $#bq*îy |ÃÑÕÌ"”7+îÎ]«…<9ù´®—Àê4Ǧ/Ú*§É‚k‰)ÀÇ,jÑ"B<~5]'5*lqYUdl{j5*;d 1po~cx"-)~ lX 6endstream
-endobj
-3710 0 obj <<
-/Type /Page
-/Contents 3711 0 R
-/Resources 3709 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3708 0 R
->> endobj
-3712 0 obj <<
-/D [3710 0 R /XYZ 85.039 781.388 null]
->> endobj
-1566 0 obj <<
-/D [3710 0 R /XYZ 85.039 761.463 null]
->> endobj
-3713 0 obj <<
-/D [3710 0 R /XYZ 85.039 741.134 null]
->> endobj
-3709 0 obj <<
-/Font << /F62 1689 0 R /F20 1617 0 R /F15 1628 0 R /F56 1642 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3716 0 obj <<
-/Length 2860
-/Filter /FlateDecode
->>
-stream
-xZK#X03xrK%'Z)YV.!
-@`2 EefR=t
-wvf+7zXHV<w=•S}qw
- >} {5]KeDM)
-(m<n-`?gk* A(N6J z&6ku"yj$j\=/:_MP%p#'fd!H^,^,<|WvQZmQVb5*tH5VE+VH
-"n*S^m6O bgof:9:KNm=+O;cB8ie.v&%n P
-==4NPEJTa/WR. Uh.1xu"
- rn-; x >'lQ~cP4Y
-609d Vo EE {H?,5/U*
-NB-h;6`BSct5P/''(| (Dzvh?s'B_TYM+rDx.pFkvr uOSf>S}.O>^3$EO"fE` N|,Y|( P<UVGV2dPp(:sH60}*:XccsZ.R(N=THKtkY{DSO_
-X e<yyr@^"_!
-endobj
-3715 0 obj <<
-/Type /Page
-/Contents 3716 0 R
-/Resources 3714 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3708 0 R
->> endobj
-3717 0 obj <<
-/D [3715 0 R /XYZ 85.039 781.388 null]
->> endobj
-1570 0 obj <<
-/D [3715 0 R /XYZ 85.039 761.463 null]
->> endobj
-3718 0 obj <<
-/D [3715 0 R /XYZ 85.039 667.044 null]
->> endobj
-1574 0 obj <<
-/D [3715 0 R /XYZ 85.039 667.044 null]
->> endobj
-3719 0 obj <<
-/D [3715 0 R /XYZ 85.039 639.536 null]
->> endobj
-1578 0 obj <<
-/D [3715 0 R /XYZ 85.039 406.978 null]
->> endobj
-3720 0 obj <<
-/D [3715 0 R /XYZ 85.039 377.574 null]
->> endobj
-1582 0 obj <<
-/D [3715 0 R /XYZ 85.039 172.114 null]
->> endobj
-3721 0 obj <<
-/D [3715 0 R /XYZ 85.039 145.5 null]
->> endobj
-3714 0 obj <<
-/Font << /F20 1617 0 R /F15 1628 0 R /F56 1642 0 R /F35 1632 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3724 0 obj <<
-/Length 2979
-/Filter /FlateDecode
->>
-stream
-xZK-K 08 DvJl$D 
-x{}[]~ +T!{
-V^czf \pZ;~J,h/Vvu7x|6Gx~pesw% 'dbpG,q"r@F5.X3%a<HU.p+b%|X+p(LfGV)94[+jRI0J +7@F&Ulx_cc]HKxSkBb hAI4KeE}Qg*_A*88 _F^*P =7G$cH83^pfh/oXpN
-íã@k %WkW<Yv:I<)wI\')lz!Z3x60U&n uLQw^ut4rE }%pRg@csGA8L .yTAtOb3".v m']O]ZdY,',SDKub4l)$~[o*84Z(*
-g5[kPEWN0dBÇÞ''0¦CO@xYeOfsq=wf'˜äù8ðšMmbE7 ;8fR; 2v<v
-
-^HP
-cqX 2hhi^x3D;#RIL|7S6aT8 FhC`Tt%߶r®;G:o)0exip+yvN!1T]c(U d}1J<K(69K[d"w|g}=W9W#_-
-Z/}/+ =)TqWp U^Z}4\0DG5nwpwHwQ`a}J4r+û“H[ w{=
-k/u`:hIgd
- P=mr'= 2?5Ss7.X<'s>#JE)!Ne=Bqp#nQQXlf70Iq ABXs-|iy¨jø)Ž¡{ pΧ5Ke9 ?Suqp''do{>i'+-a& |T7ce13G +)\zEyBrG{W1] @Sj 3y0S1e+
-a+sILLmg9Gg<)L ao.(d{.sW<\j#Sj{y22^
-,c}cSQA``&vx\<Nx \L;-3BSj ;{>}zR3kCw1903P+EfsvJ[)Z+WD,r=$$MATcO\# hi(ATyc҃¿ üÆ^~ÃÚ5Ã*PD zW::"#u<e6b6
-"sQ
-W`m U|8H="
-((;=_76^1H*pzg! !R\uwgt&LNMTM~|@)qxg2CQr6CxVW^iäÿn
-ªØž9ú=ù" ò2«ÎÔÍI@D`w6MKlL&c-12_]O]5{X+xWh+zskgEXO/9Pcm'^AlX8[`9fXyz;BO+1V.A?|~w2- m|p^"= >jO/SpgOO~?Ns-W3%
-4RK*<Ish;No^@b5?,r#w$*9R(
-endobj
-3723 0 obj <<
-/Type /Page
-/Contents 3724 0 R
-/Resources 3722 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3708 0 R
->> endobj
-3725 0 obj <<
-/D [3723 0 R /XYZ 85.039 781.388 null]
->> endobj
-1586 0 obj <<
-/D [3723 0 R /XYZ 85.039 664.197 null]
->> endobj
-3726 0 obj <<
-/D [3723 0 R /XYZ 85.039 637.583 null]
->> endobj
-1590 0 obj <<
-/D [3723 0 R /XYZ 85.039 483.53 null]
->> endobj
-3727 0 obj <<
-/D [3723 0 R /XYZ 85.039 454.126 null]
->> endobj
-1594 0 obj <<
-/D [3723 0 R /XYZ 85.039 397.708 null]
->> endobj
-3728 0 obj <<
-/D [3723 0 R /XYZ 85.039 371.093 null]
->> endobj
-1598 0 obj <<
-/D [3723 0 R /XYZ 85.039 257.688 null]
->> endobj
-3729 0 obj <<
-/D [3723 0 R /XYZ 85.039 231.074 null]
->> endobj
-1602 0 obj <<
-/D [3723 0 R /XYZ 85.039 144.767 null]
->> endobj
-3730 0 obj <<
-/D [3723 0 R /XYZ 85.039 115.363 null]
->> endobj
-3722 0 obj <<
-/Font << /F62 1689 0 R /F15 1628 0 R /F20 1617 0 R /F56 1642 0 R /F35 1632 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3733 0 obj <<
-/Length 615
-/Filter /FlateDecode
->>
-stream
-xTMS0W( Phb8NcJ~w%'rd&^]I?A2rf,#:d e$N4A<\w$_x|@G_n$NRT'ft zv}~j<eFo&} o=ãü˜_ED3*,W8S.#`s&#HŌVzM,$D<LZq{U$`)B8hGGUMdSK^6!u 3] +< ElqkaA@;[UkX;NK!vG};|rUW t4G'
-P  .?zz 9(#N:O~q!k_ j!IK R*K>3d im0m;tt=(+*cp{tS}6m-zMJaV7N~nI1d1+Bm7±çՅÕh?Û£óaž‡ûy8óÿ>ߛ4õ ’4͘ ÏÅñs6ÌÇÿ=%Ê2‘ígíÓ(•:b
-u¦ˆþúœ>Žendstream
-endobj
-3732 0 obj <<
-/Type /Page
-/Contents 3733 0 R
-/Resources 3731 0 R
-/MediaBox [0 0 595.276 841.89]
-/Parent 3708 0 R
-/Annots [ 3736 0 R ]
->> endobj
-3736 0 obj <<
-/Type /Annot
-/Border[0 0 0]/H/I/C[1 0 0]
-/Rect [229.043 698.057 352.339 707.625]
-/Subtype /Link
-/A << /S /GoTo /D (Other-Clients) >>
->> endobj
-3734 0 obj <<
-/D [3732 0 R /XYZ 85.039 781.388 null]
->> endobj
-1606 0 obj <<
-/D [3732 0 R /XYZ 85.039 761.463 null]
->> endobj
-3735 0 obj <<
-/D [3732 0 R /XYZ 85.039 736.911 null]
->> endobj
-3731 0 obj <<
-/Font << /F62 1689 0 R /F20 1617 0 R /F15 1628 0 R >>
-/ProcSet [ /PDF /Text ]
->> endobj
-3737 0 obj <<
-/Type /Encoding
-/Differences [ 0 /Gamma/Delta/Theta/Lambda/Xi/Pi/Sigma/Upsilon/Phi/Psi/Omega/arrowup/arrowdown/quotesingle/exclamdown/questiondown/dotlessi/dotlessj/grave/acute/caron/breve/macron/ring/cedilla/germandbls/ae/oe/oslash/AE/OE/Oslash/visiblespace/exclam/quotedbl/numbersign/sterling/percent/ampersand/quoteright/parenleft/parenright/asterisk/plus/comma/hyphen/period/slash/zero/one/two/three/four/five/six/seven/eight/nine/colon/semicolon/less/equal/greater/question/at/A/B/C/D/E/F/G/H/I/J/K/L/M/N/O/P/Q/R/S/T/U/V/W/X/Y/Z/bracketleft/backslash/bracketright/asciicircum/underscore/quoteleft/a/b/c/d/e/f/g/h/i/j/k/l/m/n/o/p/q/r/s/t/u/v/w/x/y/z/braceleft/bar/braceright/asciitilde/dieresis/visiblespace 129/.notdef 160/space/Gamma/Delta/Theta/Lambda/Xi/Pi/Sigma/Upsilon/Phi/Psi 171/.notdef 173/Omega/arrowup/arrowdown/quotesingle/exclamdown/questiondown/dotlessi/dotlessj/grave/acute/caron/breve/macron/ring/cedilla/germandbls/ae/oe/oslash/AE/OE/Oslash/visiblespace/dieresis 197/.notdef]
->> endobj
-2908 0 obj <<
-/Length1 892
-/Length2 2242
-/Length3 532
-/Length 2868
-/Filter /FlateDecode
->>
-stream
-xRk8#96%|5M`0 -5s1aa`"H"J,r( *")dO[}ss_*V>TA#Z
-XdF
-
-Z RA $zL J4FxjikjkeLc}A
-#GA!
-Iq4rIh7>C{9mAslMsJXfS>S7\SrCDsSnX?I;Hb9i:Tsy%g!InI.f{mOYH|?W/NtR^bZfZrwcp? L>M0 {Ly FPbNP$X)?NB}% \-Sj"$/7{n0w42d>f eK?6M T3cphYnaQu9+uC6tCZ ;]vq`EF(/wˆZYHF%#znhl"|{?Daf)Ku
- 28|Nt`dC~IBce|G(4 Rb_nH4^Cjkm{({5pI!Y8<d+x&v36)dx%Z2K(l.K|[aT:UyfH(kjBX?QZ2eWQZR_fFn7d~'X;tL8$Y9d Xçî£èèB;U{tIVnS#z]lvkW WyJ:dPm:Y}REqc hb{bY| 8{EaöŒq™êkX:!;lx..ay[.e 2J@0p]Cs;yL1)Gb'Y!U3 -E [=mW ‚8¥Þ©c¾6Ǩí‘|°ýÈ®%NVYOo::VUL\/-5+khGPk,3 wRv=B `"b>\qho:Vf2ot}ayOL %gKn6q6&50FL%@kCpe.NkFt~]%2ePkIBìZlIB]'!:8S%Mckz?jFþ1ÂEd+NV;eV>fbq~>u|98R_$3W$;.2LYWsNV=R'-Cu;C,;N"$&{A mP%kb8cGcM +
-#OzdQJS pRcJ&0[T+nV~^+MHc:B8\H@qI/6 [L8uv=U\Lr djXd
-S'L=?N^A_]5
-R jHa[Gl[r3:wT6 *}%n.uIotgm&?%`By /,_}«©-£n"Øå‹2sÅï–ìFPjP+\x`t:^wO~ZwE+MXPsfqutäí"9d5»¾Qpj[%}LX]QB;e4>ZD T`}
-endstream
-endobj
-2909 0 obj <<
-/Type /Font
-/Subtype /Type1
-/Encoding 3737 0 R
-/FirstChar 46
-/LastChar 116
-/Widths 3738 0 R
-/BaseFont /SDMURR+CMITT10
-/FontDescriptor 2907 0 R
->> endobj
-2907 0 obj <<
-/Ascent 611
-/CapHeight 611
-/Descent -222
-/FontName /SDMURR+CMITT10
-/ItalicAngle -14
-/StemV 69
-/XHeight 431
-/FontBBox [11 -233 669 696]
-/Flags 4
-/CharSet (/period/slash/a/c/d/e/m/p/t)
-/FontFile 2908 0 R
->> endobj
-3738 0 obj
-[525 525 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 525 0 525 525 525 0 0 0 0 0 0 0 525 0 0 525 0 0 0 525 ]
-endobj
-3739 0 obj <<
-/Type /Encoding
-/Differences [ 0 /minus/periodcentered/multiply/asteriskmath/divide/diamondmath/plusminus/minusplus/circleplus/circleminus/circlemultiply/circledivide/circledot/circlecopyrt/openbullet/bullet/equivasymptotic/equivalence/reflexsubset/reflexsuperset/lessequal/greaterequal/precedesequal/followsequal/similar/approxequal/propersubset/propersuperset/lessmuch/greatermuch/precedes/follows/arrowleft/arrowright/arrowup/arrowdown/arrowboth/arrownortheast/arrowsoutheast/similarequal/arrowdblleft/arrowdblright/arrowdblup/arrowdbldown/arrowdblboth/arrownorthwest/arrowsouthwest/proportional/prime/infinity/element/owner/triangle/triangleinv/negationslash/mapsto/universal/existential/logicalnot/emptyset/Rfractur/Ifractur/latticetop/perpendicular/aleph/A/B/C/D/E/F/G/H/I/J/K/L/M/N/O/P/Q/R/S/T/U/V/W/X/Y/Z/union/intersection/unionmulti/logicaland/logicalor/turnstileleft/turnstileright/floorleft/floorright/ceilingleft/ceilingright/braceleft/braceright/angbracketleft/angbracketright/bar/bardbl/arrowbothv/arrowdblbothv/backslash/wreathproduct/radical/coproduct/nabla/integral/unionsq/intersectionsq/subsetsqequal/supersetsqequal/section/dagger/daggerdbl/paragraph/club/diamond/heart/spade/arrowleft 129/.notdef 160/space/minus/periodcentered/multiply/asteriskmath/divide/diamondmath/plusminus/minusplus/circleplus/circleminus 171/.notdef 173/circlemultiply/circledivide/circledot/circlecopyrt/openbullet/bullet/equivasymptotic/equivalence/reflexsubset/reflexsuperset/lessequal/greaterequal/precedesequal/followsequal/similar/approxequal/propersubset/propersuperset/lessmuch/greatermuch/precedes/follows/arrowleft/spade 197/.notdef]
->> endobj
-2563 0 obj <<
-/Length1 779
-/Length2 1014
-/Length3 532
-/Length 1584
-/Filter /FlateDecode
->>
-stream
-xiTWJXPBx VC% Lf`2h&J\GEPDA\pQh*.EZX Oc3{c[{ D,&ps"<.9pL6[DB n'o2s?+ DDDq T tx`XC C%$CR Qce TPr&
-\Yi2IBFScJ
-Jgf,(}S^P^pax$[we,G0{V nxZbRZnNj~7gEmKn/+!&tA.l5';Z/f'wZdk['2 {AOxW<to1#s#wn{ C8m;`vW8o5tßdv6Ž9•®|›·Ä+¢~|É1•ï!\£Šì½»‹¹µ§K2X[jn
-"&7 .R/1c0=#y0Qytf49mo3}#-7}^azpT^wC^/jQ ~N=Kj
-jr-W1++vHAZ6[E9Tv jGD]^fTugc &k<#5“„ ™qFSkJ/+fm s6}dv ®qßñþcQMïœ+²-d䅩WUsh BGqA+lEGO6 q 6_ =@5
-\qgU<rw&?R3*+%ÑqÃ`f³;ÞþÜ >‹M*K*a{4m\t3hpVoas*chq ?SnN9>q)#U
-Nnv w*@
-22;!ZnUB4buiM~ ?s~LW3k_:ir,IqJFk4.,UbHYlZ^.;abO!*]nQ|WqxvQٕh7± ;z†¨å× ©5†1Áº¨AuYG^ =s{c zø`ô<î?|˜ÿ7øO4bPBRBB&0!\\endstream
-endobj
-2564 0 obj <<
-/Type /Font
-/Subtype /Type1
-/Encoding 3739 0 R
-/FirstChar 110
-/LastChar 110
-/Widths 3740 0 R
-/BaseFont /PRGWCT+CMBSY10
-/FontDescriptor 2562 0 R
->> endobj
-2562 0 obj <<
-/Ascent 750
-/CapHeight 686
-/Descent -194
-/FontName /PRGWCT+CMBSY10
-/ItalicAngle -14
-/StemV 85
-/XHeight 444
-/FontBBox [-27 -940 1332 825]
-/Flags 4
-/CharSet (/backslash)
-/FontFile 2563 0 R
->> endobj
-3740 0 obj
-[575 ]
-endobj
-3741 0 obj <<
-/Type /Encoding
-/Differences [ 0 /Gamma/Delta/Theta/Lambda/Xi/Pi/Sigma/Upsilon/Phi/Psi/Omega/alpha/beta/gamma/delta/epsilon1/zeta/eta/theta/iota/kappa/lambda/mu/nu/xi/pi/rho/sigma/tau/upsilon/phi/chi/psi/omega/epsilon/theta1/pi1/rho1/sigma1/phi1/arrowlefttophalf/arrowleftbothalf/arrowrighttophalf/arrowrightbothalf/arrowhookleft/arrowhookright/triangleright/triangleleft/zerooldstyle/oneoldstyle/twooldstyle/threeoldstyle/fouroldstyle/fiveoldstyle/sixoldstyle/sevenoldstyle/eightoldstyle/nineoldstyle/period/comma/less/slash/greater/star/partialdiff/A/B/C/D/E/F/G/H/I/J/K/L/M/N/O/P/Q/R/S/T/U/V/W/X/Y/Z/flat/natural/sharp/slurbelow/slurabove/lscript/a/b/c/d/e/f/g/h/i/j/k/l/m/n/o/p/q/r/s/t/u/v/w/x/y/z/dotlessi/dotlessj/weierstrass/vector/tie/psi 129/.notdef 160/space/Gamma/Delta/Theta/Lambda/Xi/Pi/Sigma/Upsilon/Phi/Psi 171/.notdef 173/Omega/alpha/beta/gamma/delta/epsilon1/zeta/eta/theta/iota/kappa/lambda/mu/nu/xi/pi/rho/sigma/tau/upsilon/phi/chi/psi/tie 197/.notdef]
->> endobj
-2434 0 obj <<
-/Length1 794
-/Length2 1135
-/Length3 532
-/Length 1714
-/Filter /FlateDecode
->>
-stream
-xRkTT# PALya P^:qP0\ws *B0
-!Y (P4
-F
-( bzlu?wgwD3
- `
-8l$
-}/FvI/ [*$BfT RD/ &)(x&yO0! "_4Ig+#r.!BX( pA;|]A  70L#*1LRHt DEIvBfP!"d1‚B
-*2by
-^m M+C=aovo^8jkzo$Ztm+ae_9-vazasL V?M=<01ft!}XzsoAX}jUTz
-=MNW9 ]kYTqQ_El}K>jK.7UYZ1:3ekQO<~63¦„‘Ïö2ã
-û-×wßZ3R~DT|?u&wF!}:mF=.AG2)dpn %.9)Ñ +a?̧ìé­ÎÓºæ­¦gÚâŠÁ©¤_4ÄÛ ÒF}uOl|pL:U. -&=z|s|Hy10C"oL}b=c>K]F;&?7iz;Gx-0okImLGzRv4kbgm!k%jc,jslJx3Z';y+tK6i8;J3D%Zt1is:,mn,ky@
-jk/|LmW737[z`)H j-=lbk#\?+o9SÙj?½¿_8^dÐþL^fKG3u+vU'K W0:@sMqBaZ+ nzo.4|sA=]Y7<u`||xT*|<opZ0d,fLw }:^g=N~h+,c*JezG&&sMRyP^_4wI>My&KV%;-On=I"u=
-$'0Oendstream
-endobj
-2435 0 obj <<
-/Type /Font
-/Subtype /Type1
-/Encoding 3741 0 R
-/FirstChar 60
-/LastChar 62
-/Widths 3742 0 R
-/BaseFont /APYTPI+CMMIB10
-/FontDescriptor 2433 0 R
->> endobj
-2433 0 obj <<
-/Ascent 694
-/CapHeight 686
-/Descent -194
-/FontName /APYTPI+CMMIB10
-/ItalicAngle -14
-/StemV 113
-/XHeight 444
-/FontBBox [-15 -250 1216 750]
-/Flags 4
-/CharSet (/less/greater)
-/FontFile 2434 0 R
->> endobj
-3742 0 obj
-[894 0 894 ]
-endobj
-3743 0 obj <<
-/Type /Encoding
-/Differences [ 0 /Gamma/Delta/Theta/Lambda/Xi/Pi/Sigma/Upsilon/Phi/Psi/Omega/ff/fi/fl/ffi/ffl/dotlessi/dotlessj/grave/acute/caron/breve/macron/ring/cedilla/germandbls/ae/oe/oslash/AE/OE/Oslash/suppress/exclam/quotedblright/numbersign/dollar/percent/ampersand/quoteright/parenleft/parenright/asterisk/plus/comma/hyphen/period/slash/zero/one/two/three/four/five/six/seven/eight/nine/colon/semicolon/exclamdown/equal/questiondown/question/at/A/B/C/D/E/F/G/H/I/J/K/L/M/N/O/P/Q/R/S/T/U/V/W/X/Y/Z/bracketleft/quotedblleft/bracketright/circumflex/dotaccent/quoteleft/a/b/c/d/e/f/g/h/i/j/k/l/m/n/o/p/q/r/s/t/u/v/w/x/y/z/endash/emdash/hungarumlaut/tilde/dieresis/suppress 129/.notdef 160/space/Gamma/Delta/Theta/Lambda/Xi/Pi/Sigma/Upsilon/Phi/Psi 171/.notdef 173/Omega/ff/fi/fl/ffi/ffl/dotlessi/dotlessj/grave/acute/caron/breve/macron/ring/cedilla/germandbls/ae/oe/oslash/AE/OE/Oslash/suppress/dieresis 197/.notdef]
->> endobj
-2206 0 obj <<
-/Length1 2135
-/Length2 10250
-/Length3 532
-/Length 11406
-/Filter /FlateDecode
->>
-stream
-xUXQ hn]qwwwww$XpA33goWSELF I#++@LAMLE%
-pll?K. G(
- f"o!<l !?al,ws9Q/F}!Hn$!HR7:/I-BHD A*"B-r/"B-
-/B-J&dW}!HvdW!Hvd|!Hvd~!Hvd39
-P5#.9C+%%v~Kmr-u @on~1lY8l=jjF$4?'b sYue<"'@{*#e@+2FSx^H0-7ha1=/GSeR4[Z#yJxD% j058Wk!m3*Xw'A`AnESP|"ItGj& d1w?*y?hO$B]b|C/\GK*]X &CV<;x]^=`_>GsHf'pYwm9&gwSygB~DA:%b'5qz‚‹ ®“F%09D,V#LtS0U+g(m
-ž­¢"= ÜM@ 5m
-:CK~&GL6z,u1"8;~J~bYrX=*kh Rf¼à7nYv-t4+sbCff|€ú„çŽ|TO$f7r,'M *vc#@"^1A~8Z3t*=XK)x
-4KLG/4 [y~hKMArFRfe\n~rzo1.Q@g\o5~f/W9:'<}?l*Bj q:
-:&=vPe:kXn&w7 Zx=[k$Ig|X;Bl@md@Q 1sxs8Jg*N9t9y<jC?2>cKQZmE$yr%8hwR pk2l6#UPU.nV\6 >#Ír:ÎaäªÊJ~m.Umd7=qxhx"WvlJ0sB~IP@NoMq*--V0a(A~ 5'V"*U<qEZ
-O&qJ#!
-5 T&@
-YcW ^Jsj_6\BEyZEI'EO4:.'-{MeIKoOV7O =pI 0
-H!lOWSFemx}]A*R${sAV\X,&;K}-Am'hPZ=Y bX:Eh]+c3yaj­•Ác „¯OFbQ_];KaS`:Q'X
-Ya4]+^;]+H? v3^0 p_wLïðdÞîÃ2˜,GcG:PK¹7(Û~Ú8ÞÿªýÕÚ5ì
-evýÃÙµÍG8JdSYrM8"e=
-8'+fw!Vsl(@[YQ0:&i)ssvO j>.VlriiT2y)B?yq^~:-ù¦ºi¸…rã¿ü5“}_?‚¯8ŸÊ^Ò1žðª–å²óÒ×ir«õ8·MG(N&tytExf=,GSHQGj1!Z1j0Q `Jw-A5y62 o],Hh Lrafx= R243o6w&-m]AI /hlbr?/_fV bh WP[B/v;OW,clt$xuoX9E3JJ|j<}pL2'ZVFe#^]4L()k)@t$l29tdT&+|_};5LMPN Yjt%rj"Qy5!=-de) .#NN/yP"GA+mcp#,#4S<tssb2a#H|kh?BWC3v)YY]E"*Va2MOU'G+,,zA([<f*$zK| X:Lx\PUCdJZ%O-R [8JA17bR_n;OE<N{^(&>M]eEs
-A'R *CÞa´MP>L5#s%qy+Icc0#Vb >ng8d-OW¥ž0ĪMpRK5qO1i?!Nt w>"#>
-{xhu\¤¿¯õsúגsŠ¾Nwev|Cn"3:!7QAM/i";j&?,C}`D+vxT>\B$r U Yo6MCIYyyfm6Tr\`G=#;eiE=L|G`$.YsAcC)lQOI[E3J"ujSd}fo\Sz=p!,< >f)eLcAdP31"K"x* nQC!xw[6 QioxX:6}rM; Z_C
-pb5]5G98ZYH1wU]u2+0zs srO)N.2P"jsr+u}a
- aO+QWOEp m9kSu<NCj+UYAfo{v8rEs\WRKn v;]_t',KsTYGk3JD~ZSF.Hg',
-Q9x|S
-UIdXXjK p _a>)Qe^ob5ltRkVz#jK6F"/d$'nBx %)_Q)#;000L&>pObhGV9 :R*?wet"8\|Ox~1PI&#a /Yi[9= >$(4u
-*
-w |Y_`~&qnZo3n-
-N'6t kqD6]34l;1;Qw4*1ó
-°Øtç%¯’ûƤ·b˜JP;W@Z5hq=`;:U'0q-o2{2 'KSBC8#D6<"nAE_~G0se:vO1`UrUp?zp:du_LtLb8B6AFPo3+$GQat.^{lN-7&~u9wxyLwwr8?'B>gTN|srLYV?lT6(;]9 Qjb\*5) 5y\n\mRV{_]}A`m&nc=P/g4iRu4&]EFz{b&KM<<O3a6cK &(t0O>@f&{A:e,]|FH%cq5#5v(1gg!7d0 4YA=+Wi9VBrU[Rq*'x)4JTrQ'lar'Lp$Hxci= G`@k iv;l2^q/ w`YMwsP%!wW 8hP}` f)9,l
- $'UveB-W~>Q)(>5"=3 "rLF{!Fp Cc&
-E#[~Dlh:w->Q(A=m8Fq:-
- PlE)+QooU8ic69ÊjñJ w^W-,k5p`i1w$|p6bx%."yCia^AW} jDIxQyL2iyJ~<Avj4RG; _])wZ=.J!F
-:VLY9[S,#Vf>Ux mhao_J k#'@H!a*J)5xpB(HJ y[rS:ht?) s"j3Ef^?Ro9yhVv2vHf:æ‡ ÃЩv87éüCOHW,TFwPrz2>jx/cz<LU%%kIr;b<X\r^Fs>[8$^\D;V ;biLRYs}'
-a}ffL 1Ypp48~|/>r[oEdY\Üâ¯öa“o<A'B`aF=! Q0sy
-endobj
-2207 0 obj <<
-/Type /Font
-/Subtype /Type1
-/Encoding 3743 0 R
-/FirstChar 11
-/LastChar 123
-/Widths 3744 0 R
-/BaseFont /SEJIRW+CMSS10
-/FontDescriptor 2205 0 R
->> endobj
-2205 0 obj <<
-/Ascent 694
-/CapHeight 694
-/Descent -194
-/FontName /SEJIRW+CMSS10
-/ItalicAngle 0
-/StemV 78
-/XHeight 444
-/FontBBox [-61 -250 999 759]
-/Flags 4
-/CharSet (/ff/fi/fl/ffi/exclam/quotedblright/numbersign/dollar/percent/quoteright/parenleft/parenright/asterisk/plus/comma/hyphen/period/slash/zero/one/two/three/four/five/six/seven/eight/nine/colon/semicolon/equal/question/A/B/C/D/E/F/G/H/I/J/K/L/M/N/O/P/R/S/T/U/V/W/X/Y/bracketleft/bracketright/a/b/c/d/e/f/g/h/i/j/k/l/m/n/o/p/q/r/s/t/u/v/w/x/y/z/endash)
-/FontFile 2206 0 R
->> endobj
-3744 0 obj
-[583 536 536 814 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 319 500 833 500 833 0 278 389 389 500 778 278 333 278 500 500 500 500 500 500 500 500 500 500 500 278 278 0 778 0 472 0 667 667 639 722 597 569 667 708 278 472 694 542 875 708 736 639 0 646 556 681 688 667 944 667 667 0 289 0 289 0 0 0 481 517 444 517 444 306 500 517 239 267 489 239 794 517 500 517 517 342 383 361 517 461 683 461 461 435 500 ]
-endobj
-2203 0 obj <<
-/Length1 963
-/Length2 2491
-/Length3 532
-/Length 3136
-/Filter /FlateDecode
->>
-stream
-xy<{2PPef0,C34 cF.B!kKHR"YE!3<=>|?Q7!4*Sl1+8 k JJft$8& ZZH`F }HL`"$`x1I?W
-p|8  8 L8CB-YQ4
-5p-hTJ0@
-oB:\k 4'D~T6bjchjfm_ht 
-IEX;AM Zb`e#gP-+fttj`AC{Y*:A8E*g%¯HeDtNm.g_HjS\&YX(qf\hz[7F,>}R+ o\?7uW\uQE]d}:DIe. ;S@O}bT4C}u$qTK8b_in9/
-QoCgGO4OfIR]`f:e",l*~Q)X>~v7k=P4ùVe ,pRQ*3(Us-4rzAd'sI>G(!P~CmWN;uz
-N{6>lW4`n<
-0BHST(Tp-"KL tdJL` DZl{A Z9hwmp%GY_uKrIu;TMZt i:}-4_"|K5o0}x@G}W{eUM Un:qdg;1Ukt$'E{Ce}:"%<E!^_ãd̀ÎGhWh=8o@LA~)372Ir'_ O?;Ks+MP?w8MEw|1 UOIR 0 l(qY0$k$ Lw13f,8DuyXxV}Wc7@_k" 4_a |R*i/]N"+:*WGl9S+
-6*@5>1$?]|5`pk;n`wTb3
-xOOO(ZThY geERj=cx\h N7hUt5M%GAY"gCb20r6e.wH47`ok %qk.S <Í#IWBÞ¯ ²’˜9<ž®·öj<íšî át%¹c¶Ø‰H p$9Hz~BRr#Qv?,,^]&6M@?e3RBC+cTv^;jd8A|{JK\0?&ru)wvhÃD3+}]] 3^7+zwMGt- _3QU\ O$r]f eZShos: *u)w\O+SXy@E|-nUM<m[D5v`ve5G_0kgm_s]OlW*~|J}PC{|0wkeQ XwJLe'Ê}Û?ԋ՞„w¯[þ¹„qÐ\¢EVGk¤ü•=ºNDtDX[3pvMI"/fD_U:tyuOa \Pp$ <nd4&>B.C|(A{/:{x@J&
-Hx&msO_}VIYY,;a'TqN%aARgDR
-!CO5 ]2KhS4^^8^$i]xb)qm;W'q3MRwu?8'kiZ<(õÄËw[ãözÕfõ&müÛ aõ­)òHL96
-endobj
-2204 0 obj <<
-/Type /Font
-/Subtype /Type1
-/Encoding 3743 0 R
-/FirstChar 45
-/LastChar 118
-/Widths 3745 0 R
-/BaseFont /KNTBCK+CMSSI10
-/FontDescriptor 2202 0 R
->> endobj
-2202 0 obj <<
-/Ascent 694
-/CapHeight 694
-/Descent -194
-/FontName /KNTBCK+CMSSI10
-/ItalicAngle -12
-/StemV 80
-/XHeight 444
-/FontBBox [-97 -250 1077 759]
-/Flags 4
-/CharSet (/hyphen/S/a/c/d/e/h/l/m/n/o/r/s/v)
-/FontFile 2203 0 R
->> endobj
-3745 0 obj
-[333 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 556 0 0 0 0 0 0 0 0 0 0 0 0 0 481 0 444 517 444 0 0 517 0 0 0 239 794 517 500 0 0 342 383 0 0 461 ]
-endobj
-3746 0 obj <<
-/Type /Encoding
-/Differences [ 0 /Gamma/Delta/Theta/Lambda/Xi/Pi/Sigma/Upsilon/Phi/Psi/Omega/arrowup/arrowdown/quotesingle/exclamdown/questiondown/dotlessi/dotlessj/grave/acute/caron/breve/macron/ring/cedilla/germandbls/ae/oe/oslash/AE/OE/Oslash/suppress/exclam/quotedblright/numbersign/dollar/percent/ampersand/quoteright/parenleft/parenright/asterisk/plus/comma/hyphen/period/slash/zero/one/two/three/four/five/six/seven/eight/nine/colon/semicolon/less/equal/greater/question/at/A/B/C/D/E/F/G/H/I/J/K/L/M/N/O/P/Q/R/S/T/U/V/W/X/Y/Z/bracketleft/quotedblleft/bracketright/circumflex/dotaccent/quoteleft/a/b/c/d/e/f/g/h/i/j/k/l/m/n/o/p/q/r/s/t/u/v/w/x/y/z/endash/emdash/hungarumlaut/tilde/dieresis/suppress 129/.notdef 160/space/Gamma/Delta/Theta/Lambda/Xi/Pi/Sigma/Upsilon/Phi/Psi 171/.notdef 173/Omega/arrowup/arrowdown/quotesingle/exclamdown/questiondown/dotlessi/dotlessj/grave/acute/caron/breve/macron/ring/cedilla/germandbls/ae/oe/oslash/AE/OE/Oslash/suppress/dieresis 197/.notdef]
->> endobj
-2200 0 obj <<
-/Length1 1380
-/Length2 7269
-/Length3 532
-/Length 8111
-/Filter /FlateDecode
->>
-stream
-xe\]iFK`a`hnFASBA@wy[?3_::ZD)c +\<8yxDrrr<
-0@X8lv@ B pWtv
-q-0P.j;u- g3]x8
-
-]DIsLWJ]\dI/"i);f NqJ%7L<Ew#;6*?O<9DOyt'ATlt?D#-Hq"D!}n}J:Qu0&<FM,4uB6
-Bf U"Tk,XjN2LL[wSS]V~?P1"Q5xg e8/ gL e/
->(z,x
-*Or
-~v<YfZ it fKOZW]@x%=$WJ|?"ainn6ci48}l_mWv{!v=', v[(\Z%HA6Ud$zjAa%)?~ .(\rz=XIg/)$0d'GPb2j,H2M!-^uo#RZ *4]S?6j,
-i0I~O~&}m4
-.b1pou`Z2ui{oS ³‡CunExTomO3RY 9^D/Z[: vEf&#]T ^g1Mt*j DEw}04SqYfd.~j6kHM<6hu-`CXeye?&sUn_6n&Zh1_dUE|&+- EjiYVxxrn8{{…ƒLyS5kJJO.x_\/l KRaS3´~ôM4h8^H}u($[NT~Ikn#kX.k<&qN//^Jh=gp 
-{M#%TLZ}T;z|k1DS+t#|b?Ty dK7]-axrSH2e:
-hrq)
-qNJ8g*I+_T9pEtGh¥[™L[}FH245i~#To{.qA"2Xz4u =/Z?NENFS&u5QV ~n ukM2R0XkIcF(phk*w:CU@@#,0&u#HbW/cBvgjd`4|x 'nNVE`d4[Zz lJMtb# Mq& }h[3>7"R/w'8*?Z5s N<MExbMY.s <vs7>JJB7Ia[xX;D[*u+jEgQsyQ '[itSbgLZdJQGii%`s|k1!an*a2Zon9i<V`_EHxqyn:9kSy6d _NUgJ5'a=qG&Avsnb1t?D_DMXCqg >zV-s\Bnij_L|ZLzD6xpAEv[9}tu=X'xSHYo><) 'u3yt7S2,5Z5+t3FQMN*9#`"P<b[j*5|y><M=O"mboEwG1qVh %D4^ }bhh:FuvK|_o>Kb?^z"jS cCFa)a#WQ9#sqY%t,;rg/7W? Ik!?nX}3BZ|;B~Z}AyuCEL%(F2^ $ t*19(s 
-+5t[(?m';&*8
-{@(z?:u
-+RHh(q;:_ m]*$Q8 CG X JE5ktP|raL~d{Z+6IjFo'0 ?^U1lD"
-?I n?t=) ÊLuk3n_ t897!a7<!h'nINkz !+F)|5W3vJ<vYzY}}'u`FSSNKuL*_wI?%R!' &BM<{:ÇÇ œ¾_mid›§J7~2}zHC}w`hm^z]tb]s7_*H%':|}4F_vh~nOZRPb FCjlC}/n H9gM\6de(Bc9Zlc2SlT(@qOEyc7If5i90963ISH @N5pdQB}['OxTB:z[1+b5;A(5C_mg"@Vsgy-<[:/")?g|zy([YM6e Z$1QL.("k{T+~%p ew)7cI6
-1f]q[¶¯Fks>ek›Æ`äPo<y_bGJ0V{q/g:q
- WeL#bem_pÖ_™±jág1Y!G5(Y~ZtqG)~%÷âE
-v41^SIv9'/nFHSkX=jOjHc[GvnSDrwn)?17rTJGh@1drWSnY#5!qN<[6 .!iB%o#^:q8zWg0 b*!'|?nQyi'9=+~SHa^]]
-.
-Wp,j` =`P
-endobj
-2201 0 obj <<
-/Type /Font
-/Subtype /Type1
-/Encoding 3746 0 R
-/FirstChar 33
-/LastChar 121
-/Widths 3747 0 R
-/BaseFont /PLRCHZ+CMCSC10
-/FontDescriptor 2199 0 R
->> endobj
-2199 0 obj <<
-/Ascent 514
-/CapHeight 683
-/Descent 0
-/FontName /PLRCHZ+CMCSC10
-/ItalicAngle 0
-/StemV 72
-/XHeight 431
-/FontBBox [14 -250 1077 750]
-/Flags 4
-/CharSet (/exclam/quoteright/period/A/C/D/E/I/J/M/N/O/P/Q/R/S/T/U/W/bracketleft/bracketright/a/b/c/d/e/g/h/i/l/m/n/o/p/r/s/t/u/v/w/y)
-/FontFile 2200 0 R
->> endobj
-3747 0 obj
-[319 0 0 0 0 0 319 0 0 0 0 0 0 319 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 814 0 786 829 742 0 0 0 406 567 0 0 989 814 844 742 844 800 611 786 814 0 1106 0 0 0 319 0 319 0 0 0 613 580 591 624 558 0 641 613 302 0 0 513 747 613 636 558 0 602 458 591 613 613 836 0 613 ]
-endobj
-2157 0 obj <<
-/Length1 793
-/Length2 1151
-/Length3 532
-/Length 1728
-/Filter /FlateDecode
->>
-stream
-xRkTSWRIzX<1H b OyH!$A%UY(V@%Va
-"" a9R*uu5kswin26b %l[
-!ZG2"BJ:aoJSVN%#JDa=IpDX M4U`q\CDF\```ub&
- J L 0pF$
-7\n<kWMfDt.r })n{]kX\W03,W/iw p^7AhK=NE'>z^ Tmj9(vhQ \Kw28o~(*?Dmx l?("PrvuOU) <>\kŠ£–“ã†L¸~‰©ozŽ®;\cسùѓÛ+íÜ@ Krní ÕÚ9Šš;Ìèýã¥wìG[v}4Zc+#Ge*A-U:b$O0Kt1A;TuI 3±z¬JJ[;si90^cn(Ne {<#*odR+yYe *ttmg|ujF}gqZX58oaN**uj\Z?;PVf?rV{1e71CG8&ESqbOcxYTNU{vZk.Oe*^ps^"%*J/ ~G!K+-,xiQ( _nKV7uA{:;WoN/wVR1>m]G[5}MN<aYP#åy¿ Ñ²FD{9<f@,|1fO]J op5zxIL"Xg,+H~5n. OPa9N`9F7endstream
-endobj
-2158 0 obj <<
-/Type /Font
-/Subtype /Type1
-/Encoding 3741 0 R
-/FirstChar 60
-/LastChar 62
-/Widths 3748 0 R
-/BaseFont /FPBQOM+CMMI10
-/FontDescriptor 2156 0 R
->> endobj
-2156 0 obj <<
-/Ascent 694
-/CapHeight 683
-/Descent -194
-/FontName /FPBQOM+CMMI10
-/ItalicAngle -14
-/StemV 72
-/XHeight 431
-/FontBBox [-32 -250 1048 750]
-/Flags 4
-/CharSet (/less/greater)
-/FontFile 2157 0 R
->> endobj
-3748 0 obj
-[778 0 778 ]
-endobj
-3749 0 obj <<
-/Type /Encoding
-/Differences [ 0 /minus/periodcentered/multiply/asteriskmath/divide/diamondmath/plusminus/minusplus/circleplus/circleminus/circlemultiply/circledivide/circledot/circlecopyrt/openbullet/bullet/equivasymptotic/equivalence/reflexsubset/reflexsuperset/lessequal/greaterequal/precedesequal/followsequal/similar/approxequal/propersubset/propersuperset/lessmuch/greatermuch/precedes/follows/arrowleft/arrowright/arrowup/arrowdown/arrowboth/arrownortheast/arrowsoutheast/similarequal/arrowdblleft/arrowdblright/arrowdblup/arrowdbldown/arrowdblboth/arrownorthwest/arrowsouthwest/proportional/prime/infinity/element/owner/triangle/triangleinv/negationslash/mapsto/universal/existential/logicalnot/emptyset/Rfractur/Ifractur/latticetop/perpendicular/aleph/A/B/C/D/E/F/G/H/I/J/K/L/M/N/O/P/Q/R/S/T/U/V/W/X/Y/Z/union/intersection/unionmulti/logicaland/logicalor/turnstileleft/turnstileright/floorleft/floorright/ceilingleft/ceilingright/braceleft/braceright/angbracketleft/angbracketright/bar/bardbl/arrowbothv/arrowdblbothv/backslash/wreathproduct/radical/coproduct/nabla/integral/unionsq/intersectionsq/subsetsqequal/supersetsqequal/section/dagger/daggerdbl/paragraph/club/diamond/heart/spade/arrowleft 129/.notdef 161/minus/periodcentered/multiply/asteriskmath/divide/diamondmath/plusminus/minusplus/circleplus/circleminus 171/.notdef 173/circlemultiply/circledivide/circledot/circlecopyrt/openbullet/bullet/equivasymptotic/equivalence/reflexsubset/reflexsuperset/lessequal/greaterequal/precedesequal/followsequal/similar/approxequal/propersubset/propersuperset/lessmuch/greatermuch/precedes/follows/arrowleft/spade 197/.notdef]
->> endobj
-2103 0 obj <<
-/Length1 867
-/Length2 1181
-/Length3 532
-/Length 1804
-/Filter /FlateDecode
->>
-stream
-xUkXg]A"}o 8"$4PdKD:Ld 0*pUARuED
-4\*t"^*t
-C2"C(BWxH,!B:!
-@8"Be#oY`<)4iL
-{!= O7<$E%4ZN 8 \X9`rb$(*I3X *?Jb "8".B7oo~?E=_dJ8
-`fd0&De"
-U:pK:N [_yT^8 :STJ")@py1:hchRG39=^ # d_)i)h83>321o]~>j|I +{m}Uz4M.f ,{Wv^[2dx;6MC#jqSM)b|e3a-o1nkvA+RZ}]n1V.-g _gyh0Rn MZ_x165wqLmq"J0#0ME9' BCW '
-A?
-sVN?KecGr"j>TV,q:m;^wdGBiTI+vG
-\:BZY`s)w!l#+?[UKyhSf}mfmv^xv8&FKkw.]4m2sm(kii5No+7 ms|?TE}R/KNfmh'r[yrz20~lex79C &(endstream
-endobj
-2104 0 obj <<
-/Type /Font
-/Subtype /Type1
-/Encoding 3749 0 R
-/FirstChar 13
-/LastChar 110
-/Widths 3750 0 R
-/BaseFont /NKXQES+CMSY10
-/FontDescriptor 2102 0 R
->> endobj
-2102 0 obj <<
-/Ascent 750
-/CapHeight 683
-/Descent -194
-/FontName /NKXQES+CMSY10
-/ItalicAngle -14
-/StemV 85
-/XHeight 431
-/FontBBox [-29 -960 1116 775]
-/Flags 4
-/CharSet (/circlecopyrt/bullet/braceleft/braceright/backslash)
-/FontFile 2103 0 R
->> endobj
-3750 0 obj
-[1000 0 500 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 500 500 0 0 0 0 0 0 500 ]
-endobj
-3751 0 obj <<
-/Type /Encoding
-/Differences [ 0 /Gamma/Delta/Theta/Lambda/Xi/Pi/Sigma/Upsilon/Phi/Psi/Omega/ff/fi/fl/ffi/ffl/dotlessi/dotlessj/grave/acute/caron/breve/macron/ring/cedilla/germandbls/ae/oe/oslash/AE/OE/Oslash/suppress/exclam/quotedblright/numbersign/sterling/percent/ampersand/quoteright/parenleft/parenright/asterisk/plus/comma/hyphen/period/slash/zero/one/two/three/four/five/six/seven/eight/nine/colon/semicolon/exclamdown/equal/questiondown/question/at/A/B/C/D/E/F/G/H/I/J/K/L/M/N/O/P/Q/R/S/T/U/V/W/X/Y/Z/bracketleft/quotedblleft/bracketright/circumflex/dotaccent/quoteleft/a/b/c/d/e/f/g/h/i/j/k/l/m/n/o/p/q/r/s/t/u/v/w/x/y/z/endash/emdash/hungarumlaut/tilde/dieresis/suppress 129/.notdef 160/space/Gamma/Delta/Theta/Lambda/Xi/Pi/Sigma/Upsilon/Phi/Psi 171/.notdef 173/Omega/ff/fi/fl/ffi/ffl/dotlessi/dotlessj/grave/acute/caron/breve/macron/ring/cedilla/germandbls/ae/oe/oslash/AE/OE/Oslash/suppress/dieresis 197/.notdef]
->> endobj
-2098 0 obj <<
-/Length1 1930
-/Length2 16115
-/Length3 532
-/Length 17214
-/Filter /FlateDecode
->>
-stream
-xcxcvl6;mmc:qq<kz~?9jT]G)7c[C-#### 4)F ED
-0bebd&%sw075s"'5@ `9?3 
-OV}
-?{?%'Y?$>U< gSZ}'>MHC^?E}zC^C^TWCS]}Ou?>5Cssg1>'_C~a~b~VW1|b~z ?MY"%Co~ ?]<`+_/t~r ?]u|r ?])6U*(hILifvg 30p0q+jy8
-f(qJ&Ò¸éÎ6¹‘š§•x7ˆÁˆæ_“IU›°nc6}óöT8 Bqit 23`voL}J|V-}+lywr{& Z']: z;|.f[`R4~1g#e1dg1E=SneI>,{I}W\9 0ds6!
-W:;rnI%Fq/_'c`LJUXuM1r3<]i]7N CKA$_+' ttdz A> LyHT_gKF g<:9xdJruø@+PL<41- B{p8?R8m&.RPhfT`R W/!WSi7V^a
-<#–G7@i'l%U>ALK}C Q={B )j_PacU5 AQW2=mh;qqIGZv xN'I[g0#%tv-eCPoFSH7 engL"Yi5+T]Sme_.~)F92Ñ^™ý¸z÷~Q^-,.O~g*:!> N*Nb$J[_GKWVeskB+1:'7<%U 9XKRAHjs.= ^ q)/o-;8i
-Lj!d4tx)rDb/E>B/6'!*eP2Z}ai¡Rkv
-oq9 $ {33kPw_'#Y97/S4)(fYE,L}J>vx=Qr`Qd PJCQgGp(~?G|1xc[u4&B,^xY’
-]åшž™qkl>üLJÒð¹!ÿ¯Üê¶iD' Ul%;õÉ]>V 6_y&_ù2'X,‹õÛêƒ)÷¼qﭐùI]vy9m?+K*b%SnojBH;uyE^qwcQCrGPa_h*Z;cU/F-Ge
-<jDS;<@UX?v^TzY2f2k?c"}I`0Q|p3I*x^6X!Gym2"}k|-wvZdu[7>]C0 @00Rq$Nr*M| <G^I9uDmPWVc9C `<shnJ2 V 7#"Qe 68,/7^;<v%}n oiD2m-7>$va3nGPP4qG]rZA[s<KfQ:KDf2*_[m7gjv
-Cr-4
-~e}@ oDæV6iS$
-E0! ">^2Y ;gvk7P]wrNxa&LZE#$4~8~l]J(u)-M&bjL:%y>/0'AApk!WJ[\ ?.T r><@RH 77OT\_S^8K ~
-API9u/>ukcQP-d-0`vbRf `0"i?91tIEOcTRL }_x'PC~3/d'~(Emyd.T\-{y iN-?u~FK`oIh>6e /">(K_^*kdYsEw*fm&j=Y
- |20jO;Zu3b qru-:BEF0x&</u$%h8q59,!n=t{)B <$t>
- v6 UqTm 0:1>$X?JE70W6GlQCi:;QBV}Owje!phU3Kw[#LJ{|Zk"QN%BES4 oo*ySG^R\Ds!HE_wE]+HGVLm&`6~Fx$K'6RF6
-#+aG]%8kJ &6'2t&6e1i!,){.KL4pXC_* svt*MBj4;"qi&/*U - =fprCGle $<{)1{]K6<[t=IJM%<%gDPh x ^6HoX07'${h5HmfNuw YG8"/c Yar'!!Tr{idL9:60)}F><TlIip:!_~e{mQ8<h 7?p {y\FC !0{ lhE|/m|"
-b=BuYUR>FSnhF_ wvwO}sn y/+}iS*{@:$r~'!+\w-r7n"\#'ta#RTT/y`oAa5/ J5+n)Rj1tw*^:W0aW I~qfW3=q|Di-Mi~O ChBqfgj)|<3rHulqrweg-geO]"1]n`~_mk!|m"Uj}O}G%3:wg
-i>3<W, smg._Q ^d;`gix2|;ljs&Zq|dC#9$T.l%! QhXVo&o'rDV\Mmt$RtKJN{=;+l~3`
-4VNtM]pF N>oF 8DZ6-9NJ[DJM|a2=$.20XnRo
-+|cKd2+u-a]OQrG(H^K
-Xrw@j8y
-!|\ht }~R&IJÈ¥öÊ÷ZZ~N[VX~W8QloHtQ#nYo)~{D(QSLW@9buT/4NUS{AzCµš+wÈ)Ý%Û½¥­nì\ׯ—}O.|RspF%*OhadL%.YB:?2V5WGe:"v%V\&&Xg0
-8
-9w3 07qfGIpOzNjy#Qr7tx"!m5!=$CFam?); &]2~3"l_(qM;hl n9 RS1.ZNI5Hh,~H`-Loz,%8>°éEMTh$qNtblVVo'ZCB 5a0;V
-.w:\B8e#;WWmj^}u_ [Lwe2Aw^y92cZNv<:^nweEcP4Fr< DR=mN%H:B>rOkUt|09 0O{„Uhg'O{fF']hnFJQh9@"U.8#bQwywir9„ Ó*ˆG&rJcN!L YXuceF6RÅ»Fj o&b<9Hf;>/`g9:8'^OC3
-()
-p3D&QTWKx1y
-X!'ggnWh5)>[k }VB7~!no{HVcGK(/G`([]WL6z1,N`(
-y;a
-ZHo@#c6%R$kP=zX=cqWfbcod{+YqDF.XUGh T4' F/P zqmZh601q1Fk@4!Kp$B;OMu9@%w~
-P>I/XBAd.KmfGj!7:/V?0>\ 5VYa_g\
-k'&]# l{K.KZ#@~`-K11!nvMFh0&l`s M:2gu.dAZLex|5Vq>X{RUM1`B]Fk61"dL{:(3K&$" n6G)2\{oZmoxng=WTD%1ƒ•)p/bø•P#Q-C/Q+jJabInQC_p?bM,F1}ZV9H NO44
-T?}.J$MZ6z_4
-_UU=/Cf]@R_%2f]IBRAKV"OikTrOWL21%6pQ?E*llVc5Sq`(#cs0+DI5,q2 *m"(@E P-C>CYPwp@8
-JkSG& Cw_> P{P'27CqD QHR/ vx`g /_s )wCT"k]TpF$H4_;gt."1x@L"ZnpQ.^>zn$7 DCv-iLNBeW`4]th!]r2kd9V,}\;~
-35aq3&aSCx eJe+^Th>.Sk~Gym%D
-4&H@Z?n&r6VdIm~pu
-0om@4"_8
-DpX`3^S$8YK#)5^9Vz0$17
-p[ 
-'|#Þó æÛ~õÝæ>
-Ç-óg¢œfœØlpwÓO>@gq](lQx{y@Ct8H"'Nhv$6m}2_dh
-jE%(]f=P
-efdECy
- g(aDA^
-.KYbN8B gt~!5;x}y=0P.NTx|qD?
-=i*.H?eZ7=K 3,QuF;FR^-80AjM%x~I
-6I;XThnd(SvzxLNU\Aa>P*EOc1 G('Gw|.=tkhrl\"h7vPrhs[FCI)o+$$Z+<0n[ MfIL\a~|,yh?Mx pMqedJvyVdOUM0T$`dC']s"wn=5bYl?[3O6#J _t~<x8A¦_[¹™[ê$XX ,./jJ\FL;G)Uweq)5P2TB> qf05MgdyPr.CS)
- ['j&wjcCLT}lHGKvdmD2-;E2 Z0|EFs0-HU 5Fq_L
-O%$8DFE)j0;,NMS{ Q4w%+rLtE6@2I?aSS C?
-J
-e%vN&#bV7N,7 ai/p[>D;K~ %qt0|kuZ(eC 1(,W*|+W^O==y5NrM%31w&wF,#DG
-cEE\;Lv$\gX|(h<cqb|U-lywesz5"yaSN*l4oFHL/V:Wo(e}"/BsJ4-_/>'oT?3zl¿Ej=<t9GIL/_,b@!5`XXTX
-endobj
-2099 0 obj <<
-/Type /Font
-/Subtype /Type1
-/Encoding 3751 0 R
-/FirstChar 11
-/LastChar 123
-/Widths 3752 0 R
-/BaseFont /AKTHUD+CMTI10
-/FontDescriptor 2097 0 R
->> endobj
-2097 0 obj <<
-/Ascent 694
-/CapHeight 683
-/Descent -194
-/FontName /AKTHUD+CMTI10
-/ItalicAngle -14
-/StemV 68
-/XHeight 431
-/FontBBox [-163 -250 1146 969]
-/Flags 4
-/CharSet (/ff/fi/ffi/exclam/quotedblright/quoteright/parenleft/parenright/asterisk/comma/hyphen/period/slash/zero/two/three/four/five/eight/nine/colon/equal/question/A/B/C/D/E/F/G/H/I/J/K/L/M/N/O/P/R/S/T/U/V/W/X/Y/Z/a/b/c/d/e/f/g/h/i/j/k/l/m/n/o/p/q/r/s/t/u/v/w/x/y/endash)
-/FontFile 2098 0 R
->> endobj
-3752 0 obj
-[613 562 0 882 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 307 514 0 0 0 0 307 409 409 511 0 307 358 307 511 511 0 511 511 511 511 0 0 511 511 307 0 0 767 0 511 0 743 704 716 755 678 653 774 743 386 525 769 627 897 743 767 678 0 729 562 716 743 743 999 743 743 613 0 0 0 0 0 0 511 460 460 511 460 307 460 511 307 307 460 256 818 562 511 511 460 422 409 332 537 460 664 464 486 0 511 ]
-endobj
-1688 0 obj <<
-/Length1 1393
-/Length2 8536
-/Length3 532
-/Length 9398
-/Filter /FlateDecode
->>
-stream
-xU\Ú¶î)îŠ+NEkJ/(Z(-ROws~s0khrI[!/a\ n(@VUS
-qHp!N+XB-P{l_`
-;!LX&
-¨ChANo_Sy3;U\!p*R]B,.vUr6ZH
-~,b4fY'?"
-x;{af!.1W` :cXgH}U1Yx(0O@K+uFi!/M`7!<R s{ "8/\;T@B?#QK}mp,wRrT!:k7?`.H({WmErTQKb[mc2lZffPfv}+}Z"As~(HMNU13Y{$?78SR@}Kk"APnCo}.)tb2/}we[:Z'qP$+zVOE\NaXbZort)8x~8P;i;I#[AoEravpMNf!K.|$fFK#:&V_HT88fD;kpvW-\~vcwNY6b[*$T&2&(A~(Q!5cWoM!r`l\<>x`H s6$g- 5cGl$~drnZ+S /M7?>M( ]xL'd\ ) [*^)7;/j: 
-nc;^`VtkIN:|@LFyHLXj 4TA27y
-E rD'=$"SNtOT+UXB<^#ZB/SS'*\JÑ»‹ ’7Ô¤.Cky+e0CNJzhrh;BrYJJy)'eWRX
-HDGZ
-$bh@ U,há©PZ0qszemSe-b]'KZZ2ZgnLO[Rd}S5/5[09<(
-lO|yB7F7$&@-l*/:!0KV!K # 11\ mN|2$I|O}3}xMe*AKTNp-tUw3\U8/mP%Y!#%h`K3(~^0)EMKWG?~Pb6$&3aP2vW?y>b*UQ*M s).\<xOJ%S 2onua&o:y3(^|-|a@QOrD1c^Ly$iS[E@t{M4SD6nua#]% !m$fY:o_\G!W}!X%U1A1(i2YKoO~F%8] X9Baye,e@ar&y%E<{uYxlpSW J.C3 hP /K$):Fqb(Y6}{"ba-I5W=5pwR'Y>zHu&Dt%c{*q{t]HRL_=l=%
-hmi#s( >V|<M u }^p&)I}/>.%VDn^r1}?G0eO<.oz EjJTX Z()A
-k^SlB#( i-Lc.+HkEb_QRr"X_r72/%VGAZ|mc<xR&D-Qg\} ^DiA$R3|' _: 0OBAMIlSk!~6A{+Nf E6"|q7^"\~8G7 F@z+2<7-8\oEj%_?2dDE5X
-Ov6KWuNme4i15*Nt\@+gH:^|)R\y{E ;R9{S;A~oRE }9I+@J3bvQgOAGs
-P+8Z6-%~@hN VOeG'K2-Z&>n IG~@_=CR S4D#MILRx2b423\E$
-7A> ~V uzJ$ZXN(0(JNjRS"Z: #i^6+StF`-x%DH|E\@-RZ7f&uh,xOY<\$d{}@Wg
-HGj_|
-q#biM#'5B%.DpH#X_?azme{Qf9^yVeTNn\JePQJ[ldx+XYxDrM+%}>2UF}z$Dev+uY ?%&7lyqw6Fzcav\oMKV:#cIoJR{xZL)k=1d}NK'>i(+-qd e
-7B!fox#?.a)_o)Q{q&11rN]>63Yd-R7[FJB8~$e^eJucOg'*KS-nc`*:a}w;vsR-'yg}`}.+_-E2to'_6sc8Ih/)_ Q%|l^[cx<GBcMj$3p^Cwse?^_H"
-!~Y8]mrL/n>uH-t e&PKu_u1Yu%h@7<BFYizmB[*KR[\!mí£,-ÓÐÖßCh –ŒežÛ}î±
-\5”ƒw¬¬2+A>y:9
-=Ht~Ba }T<C X89!>6c$(3$(d0Iz{+$0t7rIo%Nh9sZ]\MJ im
-bNhZ^m'"I# `NF#BJh3o}oPD^)d
-#9fl9t T{XW'i+  iLT%Vsr uM%YN}lH% iKg6,]\/veuhXAc
-9z
-sND+-M<a C&~S|3!R3s{_)gR5fIip+yZ%$uG7qM<-_\TeH^1no
-@
-Xkr`Q?"4@uJ"uD0-5o45i]Vw:{eOV!:E?z)Au,t Wm%jn pLorT?6FKI/:Z]OJz
-fZ4Xag > =<:W +[9**-.t!rreIY" ot 6fv@tNteI"‰cîŒÕ™ÂcÁ_>Ó°j…aÎ+ú¢È¼†­G_zq0Q]AVyX.~^Tx5N`r%rAgI+2blAqmKc)W(
-Im_^ar; oG)o.H]?Sd ]cab7k;fE\;j%\*boGJnrhII"QIIGVUop$,CODtCT )U~(:mdv1dzK;jy_vhlP 6j%37h(
-tQoL]@)lJ1  -
-'L#E
-FP0 GKCk^heK^b F&q 4Y`tzmU:IA3+~y¸ÏÉóøÁþÿü?±…-Ä î ³3ƒÛ`ÿ/øú¡endstream
-endobj
-1689 0 obj <<
-/Type /Font
-/Subtype /Type1
-/Encoding 3743 0 R
-/FirstChar 36
-/LastChar 116
-/Widths 3753 0 R
-/BaseFont /FKZVHD+CMSL10
-/FontDescriptor 1687 0 R
->> endobj
-1687 0 obj <<
-/Ascent 694
-/CapHeight 683
-/Descent -194
-/FontName /FKZVHD+CMSL10
-/ItalicAngle -9
-/StemV 79
-/XHeight 431
-/FontBBox [-62 -250 1123 750]
-/Flags 4
-/CharSet (/dollar/hyphen/period/slash/zero/one/two/three/four/five/six/seven/eight/nine/A/B/C/D/E/F/G/H/I/K/L/M/N/O/P/R/S/T/U/V/W/X/Y/e/n/o/s/t)
-/FontFile 1688 0 R
->> endobj
-3753 0 obj
-[500 0 0 0 0 0 0 0 0 333 278 500 500 500 500 500 500 500 500 500 500 500 0 0 0 0 0 0 0 750 708 722 764 681 653 785 750 361 0 778 625 917 750 778 681 0 736 556 722 750 750 1028 750 750 0 0 0 0 0 0 0 0 0 0 0 444 0 0 0 0 0 0 0 0 556 500 0 0 0 394 389 ]
-endobj
-1641 0 obj <<
-/Length1 2027
-/Length2 14300
-/Length3 532
-/Length 15414
-/Filter /FlateDecode
->>
-stream
-xSxomm6glNc65hìÆö;ÿÏZiZq{t$UVc1s01t
-Vv$j^L$"vv$<BjbnnJbfmJbbni c ?fn5n4EB/$@f
-x/}YW#;pGgj
--a%T%+ D/0kWnh0y AL\.# m6r3rV65M+0Wh#mo$z5_|Z~aMO6[v0/FO ͨ?&œ)ĪœJPr6WBjk?e%T8><k#jWsU4~mI+Yf%?)3P@qZXm0u[+5Snr}{\X *H,{dD<I
-E }h_J*HsWV a%]H7CQp 4Gkb$|cqL]?M=X(tcc#4
-ur9r z3n/F XNa ,*?F3^@kja^q`GV0kMC58$qISMK'}.1a)~{M:EU@} nodB[8,ysZ7+VM *2RtopSyUa*{
-6(u/L,vC??E#
-M|Cx<4STM$&+->Mf=u'dt\{s!%;}nykz}_}[j_d fl,A|m3
-G7F8m,`c/5mE+T\X}mvQH{_BKmiz))E
-e2^C]bAv@Dtw*LQ&QR*cYjpSnRyyW7 >V0g9POmWl6Iol }[Z[2[
-)3Jw0v+}k!;p<4* Q~gjO2 Z _rniv =w,gBAe1UfXZxF8
-'ER"4u6k#q?6- UL6{z@/Rwr<Zh7>
-N4I*HZK@_qr9oNm9:/t4Yb4p>)^;N/dkZ=l*Q9.EyD\WS,:IQsBV*M |xh%5x=! z
-?%VDx#/aO5ib;T '=hb-RT{¶sEUC/6J@Q!-.(3Mi@eE^{P;R&{*f$ h?,9oC2x3I ocBre9YCvGc=^9\eu1<x22+[mR TwX8jLV<#* Q,R>j:= K1Q[*[L$kX
- 6 _)Xe>'A(i(5r .3:s,i<-8PelG` xBk:w}>&#h,  –å“8§G"^5M|n]>10!]L}(*r`Tt3,k2%n7YCp)n[ .KY-)tA
-ryNÜ÷‰œŸCtûºF & :
-?$h3q<eI;4wP~+s.NJbz
-|T'-TevH
-vopZ}UiOVJÈêøó2¾âË¢C=)(gB
-eeat`w9\xj-51ð½¹)¯g˜ëˆy%mrû˜–+€[Ç©(Ayly.) b8gV@~a3F/{xcrSroK;<Dk6? ^e Qva2\qy^7xj3'};!
-B[wn
-c;64]eLc#|mjE[]zu 'C?<~ A`i`Q~(CkxLIk#eCW[Kh A8F'-Abb=S5\_e+v29\TzuoHJ9 cT,)r6_xЭc<ÜÒ(èa%4©NBp 'VpGv aNlq1{fRgdwJ&3aU+2v4'[ Vt8<ht]gFSBŸÌZA$. BLgk/ l/W-q=TVn|KVi!k^yZ94$tzAh m7`UoP-gNTD2] m$K~dC@o
-&h2 *2X/UKqJaZ}Cd]93U ^^XpgixC-]@\1*mQJ1 F\'evf8(gd;
-r]bA>W{b!N 
-Jwý%‚‡ÕL{QosJL;p!*)_vWoj^'(h8|S`-V?]=}jP>. 6UZf|g<5>$< 2H$EI0~lC0-áª×©\§Ü+–ª›ü-¸ÛzmS`BF|9s_#6"CLyZes7\CalxCX+j-$usC~-n*dQ<bH!DyDd#]Hh}?t^(5#HV3 j~,WM#j{er`] [-E/kr.4mS'6G4d 1zdwT
-xP
-uS!)/N^KUp?Ev/@#w`sdDkO[g%312.{1` Ua~K''ObL?N02rSnX &T* $C"g&j Jw`7o$Om0>0S7555g:p \Ith5yR1!JwT=z
-YWb~Pq&TC E'ya
-]Ml2= "a$wz2_ |+rblynFVxXcW
-6D?=I[s#w\m>Fjs>71K2/{-39JYrX5buW$@/Op%!R('
-O=TDb_u0!?i+n_M ddT_DId'!l^=`NXe&B^#z-4Sg@)/<dc
-^7?_Mt"OW9g-&.e(c9KpW1%|=QC8_+0
-U N|&%n7P
-XUB&V5Pu(z{q,vF&.$as3[5Nu5l`5*8!%ecX
-(ln_Kf(FpB93]y5l-F|eTUE73m~ÄDžq#ózæNN$y{c1h7LN ZKd\
-B$y8{u%
-'-8z1g{&iNh ?cUW66>N"MR96FqF.=(m$Q$Dm>8w> ;#k
-^{:La uG4b`mD.bc .n#D 2f=O,,hBSe_G1sMx.Kkm.qN+7AWl65sypog[y-7HQ&_t4r?? )3ctg3`w7b|9ekn{1\b& @TXa2d,4R{%jRfhDN+ |Rv"Q` n\pS>m$BGL3wzN1''%Ou
-J}}{wd }Rn477 fLA7Nl0v!g0y=,;QC
- s#CledXC}9uazÚOreeF4'CC?@*Yd3c[&C^!%úûöå¬ÏjË«Ž`z¹› “¶c
-…Ö%i ³=&Ñ[liQz[hk6xz
-
-u|MNrR-P3/c<gB<4\edWxhK+mnx .}|QXv;
- J"Z>Rb:z9?IXpd {;*No\zT
-`
-+³(ü"—c Ñý,’؆©' z»~¦]àÏfH+9,3)3EwE?T\h :/g+u[X*;N+2W>iz7 fL
-imrR(Wc $6vcI1V?1%
-(:|v1Dr/"R73";fHbS7=mG±lŽk,G1E*H6!D$vHsIwo9burg)OnG~apvDeFQ
-fi!d23`o)FËõc0
-‡›^
-;Þ)?ç$x…^mnéÖ¶~Êl­Þ©ß§?š„Ra7X1n)rz,Ze z9U08o#,nS&V^S,N -!g.=vs4_7 jB0dft5aN&g¦sÝÉâ=íP`DP\JS#CRE 9>]5Vr
-<K#6t4~8S<
-h$&"~_Eq_> * sdazJ>}:!}
-|=B0 .;pS,,.Y
-k"2jPQ0gb¥Ã'2Ù&ˆ)íNW ~O;x35Ij= k&+x0K'pH$un] N]gZhu=w1'( b vLMrj`YTfRix#m!k5 W$a*/[<SIfUX5k9`C}(&!e*>lL_.H6vGBdKF^9TZ (Y9n"S%}BlB:D:7vukFlM?])*-zoee!@(y"c)R/0B%Jd,x*nr_U+F0f
-( {n!<M+Y V"}© ŽÛ…!æÉZ
-{*g#:(Fx>uf  ALL@,qnW*uJ&^WNZioH0M#_N=2b_<
---tmLZP6}=Aj( AYg2
-2ta k]l-6Ln$C$TTeX~GQ$E6Q!~sc@#d<6ef>>7%zD='(z=T*TKlÔ'P#L#[wcnM[f
-7A gA
-5@R9F 6iAAY,f+IV$aAtOnNCRP@06:*D:TRU{%_of$fjgce* 2&fF_%rd{'N"ä㞝1åuJ | }gZCb72nK4WZ[>FmcbO1Vq
-A8`W.\j"uB(JQ#r`<) v_§öÜÎæh]»í|»e~¼é8
-_2H|8N
-"UkQUcK7s3x>^Yic9N$|3B8*I .szG5D-NDBPQy"!&~HE]Jkm,à–‚uqÎ êO#XQx.~{52ivIHXo<dS0 #qebhz/,w 8t8,v\dr1ty@`Doi,F/'J%;4^c@b?v#j#ESL ![!{5uSDw$Q=6a{l?)-VIiBg
-*?[)0%Y#n+(d
-zr,RlBXmSkWQH. i!Zh>9s]~,MB#v{<a3$lxxkøöôܼeڍSs w ~cZ@|ap$7"PgW ',L[ddG~%l뚇û
-%_õ⇕9€`v=;ñé„Õ×QTDu$Lf(>1.Q2??t+M0#9P$x.$ zkt=op.Ip"y- B-w?jw7q'u3J%U887)-Y>,GR^;=\#0/(ILf0cA9!n^¦;+ÉÁò06Apme!EF#>Tky 99skBFVrvDo$V??lKy7[k+H1R=?`q>-yG qM
-|_PY 1KyA}Elly" '.dzia|O[Yv`7q2O5%BriB+,F|w@fACW5 Z?b O#k.[N#8;YN,1x7W@Iy+[x
-(WU Tss-]2v %.bi m/HM&>
-'f
-]{R$wg<mcW'nD OyP<S+FAwYC@RwjRY_oIb&K">=mG%Pe.&y~IiFg2ZFH375pbrAfrGl@CYtR%M~kfVuMd-zyv2/94 0z-JjB-s:LF91.y.,Q8W;wI6o'}&_-T_~ }{mxS<Eb3x?o0E] W3 fS):yY?7z:b31K'0M {&'h7$}TXr~t=h|sknB5~RB:e7d&nPjq.K x|'ED9,ky+]`0OMV5
-TV .+@q!.0[\nSQO7Lxg'H9.Ltg2&A9gRb*,q|(BPh,| 3ogoBõäà»zŸ†p¾6´rXK|i#T8]TS&Q gft-=LhsY ::Le{pz~,[0SXt(napOzhq@W8'|i:u(1(8&Z[+?n(jo7MHhpuT1$80_o}è8ó$©}„÷á5Õm¾:{’š…2oΕ2‡=æÔÇ0z¤NtCHq:B,?pL]mfendstream
-endobj
-1642 0 obj <<
-/Type /Font
-/Subtype /Type1
-/Encoding 3743 0 R
-/FirstChar 11
-/LastChar 124
-/Widths 3754 0 R
-/BaseFont /GUFQBT+CMBX10
-/FontDescriptor 1640 0 R
->> endobj
-1640 0 obj <<
-/Ascent 694
-/CapHeight 686
-/Descent -194
-/FontName /GUFQBT+CMBX10
-/ItalicAngle 0
-/StemV 114
-/XHeight 444
-/FontBBox [-301 -250 1164 946]
-/Flags 4
-/CharSet (/ff/fi/ffi/quotedblright/dollar/percent/quoteright/parenleft/parenright/asterisk/plus/comma/hyphen/period/slash/zero/one/two/three/four/five/six/eight/nine/colon/equal/A/B/C/D/E/F/H/I/J/K/L/M/N/O/P/R/S/T/U/V/W/X/Y/bracketleft/bracketright/a/b/c/d/e/f/g/h/i/j/k/l/m/n/o/p/q/r/s/t/u/v/w/x/y/z/endash/emdash)
-/FontFile 1641 0 R
->> endobj
-3754 0 obj
-[671 639 0 958 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 603 0 575 958 0 319 447 447 575 894 319 383 319 575 575 575 575 575 575 575 575 0 575 575 319 0 0 894 0 0 0 869 818 831 882 756 724 0 900 436 594 901 692 1092 900 864 786 0 862 639 800 885 869 1189 869 869 0 319 0 319 0 0 0 559 639 511 639 527 351 575 639 319 351 607 319 958 639 575 639 607 474 454 447 639 607 831 607 607 511 575 1150 ]
-endobj
-3755 0 obj <<
-/Type /Encoding
-/Differences [ 0 /Gamma/Delta/Theta/Lambda/Xi/Pi/Sigma/Upsilon/Phi/Psi/Omega/arrowup/arrowdown/quotesingle/exclamdown/questiondown/dotlessi/dotlessj/grave/acute/caron/breve/macron/ring/cedilla/germandbls/ae/oe/oslash/AE/OE/Oslash/visiblespace/exclam/quotedbl/numbersign/dollar/percent/ampersand/quoteright/parenleft/parenright/asterisk/plus/comma/hyphen/period/slash/zero/one/two/three/four/five/six/seven/eight/nine/colon/semicolon/less/equal/greater/question/at/A/B/C/D/E/F/G/H/I/J/K/L/M/N/O/P/Q/R/S/T/U/V/W/X/Y/Z/bracketleft/backslash/bracketright/asciicircum/underscore/quoteleft/a/b/c/d/e/f/g/h/i/j/k/l/m/n/o/p/q/r/s/t/u/v/w/x/y/z/braceleft/bar/braceright/asciitilde/dieresis/visiblespace 129/.notdef 160/space/Gamma/Delta/Theta/Lambda/Xi/Pi/Sigma/Upsilon/Phi/Psi 171/.notdef 173/Omega/arrowup/arrowdown/quotesingle/exclamdown/questiondown/dotlessi/dotlessj/grave/acute/caron/breve/macron/ring/cedilla/germandbls/ae/oe/oslash/AE/OE/Oslash/visiblespace/dieresis 197/.notdef]
->> endobj
-1631 0 obj <<
-/Length1 2318
-/Length2 15115
-/Length3 532
-/Length 16377
-/Filter /FlateDecode
->>
-stream
-xUX\v ww4X Aww^d/o9LEQd922+jh2!RQ;L]  SW
-UL^nb73T<Ldt"e"5uv6B/0qz,
->B/[9l[B_r V! V!/[} {sfX8Yqw\\v5%&&f ed4AV|+5ws%1-
- ea+I|
-+J.mJ$3 9'm bIC`rU2JWUG"CL} MQ"+t,kcNG=~4c9Hl}ElCVS+?f#;
-#'z}WGU!`AEL?an 4t7koya_O#ICB7gg'2W\M12Zc \?+TR e;#I*YQ?s3G9]>ab
-kN4=!/=Nb(z2mtl6? @SJ |}tP!QKw'dtN W;7 3qW6
-}s 7J
-\SR~?.^H_K.A~FzE9'i(KkE[Gmng 2d*i1U8oR!# /9[#1 %unX@1Du1"WYEKq!F%&gd., sóyr`\ÆFe)i, BshJc_9
-zdO6.Uc#P)_KSU]iJv.K *\_'&h0^_]'X >i8InYP\\X.-aX2 Q
-AZPR)?'^^D]cRgN3u
-X,V}>^8z <4F'3' oÚ €Atn[h^w
-'+wGP}Xb"'^i^e!mEA]g~
-iŸ(¿ÿõ¸MK$~K 6tT5Q`gN [z{@4wkNn
-UhvNS}[vzSD`YtZ%=T&'s33xw_O['#h I9F6:j %9e(u 8t-b N<6[ip)zj:yÕhªˆ£Pp<'H&)yzrLfvwpp;nU_~f2x
-7OIVAfN4
-d=&
-uH.Zf|#F&5Me3"N T6,d"TLzfsFhP4,OmW5Y4/=9GFYT#c{-2}`o;2Oz"YcrZ$]eG@lCT~9>7:Q| Nd\Bj d (u$=rZ1.b  z od7%:xRz`04|1X[t R_kVEL,jmrNo, upv`0Z]^R `K=r!0!`~{pOe4:c5cP>Z05 ^dKJX`x>&^lC};3}V.~ii!td4=gd`|AzBEx
-lT\D2>,.0q8JN5f%orJ
-WYreB 0~BK{;,
-C |:PKPyE BEeN#8C~j2E*^x o=-cp)e%'0J4!>^`|`[& HQ1Ph{v}6B u9}17Ia2AA]OU/> #Ys0=azIDu|a]aJateYn/U^Kh:tK$FdtFc"s1`&(E zcg|,t|K2;u:wHFn1)~kg>BCZzD5 nt:.<,3nGQn5 ^=Y4i"g. #/Y,N+9JcnUK wm[buVHa*lk.Pa{ }#ONV~z$~>RC iq¬@NQP_Ey-<<ÂÜ*7K
-ol ~qgy1 u im2Hf@r#h C|_nZHwK;8 l&u
-etkCi<N
-c6gXa
-jhm'DK(U?S'`=]^T
-Qf<|d-2 #cyd]"Cg_móï16akÖ5%ZV85i{ fH<P1@_h5)Z
-Flb/w^V_KB.n+! _L,M`!~a;_BAq6g"/A<8J1.<>3‡Ó}­]F) kng KS|lqcJg 4MJoZd'8WOy7Z*chw8+WTgYJ}\v O+yO'_{ 8rfJ{w ("\Gpd_875<ivG1gu)SeQ{mFBPV=CzU{& rR^XZ/c`N.^%HBAN3#mtM?
-qFl0KOu )a0Hq|u*)"~9NY!4pGxB(V oB_8afnsL\v/@C,"T-5sU1IoeNVQH<r&^Du$RK-2P$Z,{"O}=K&= ]m [i\Kl!nI'IKi_U~q4ãâíʤ4a\G`+Qd z Kl*[(0s;wm]pa0O#W`%ACt1
-Vu6
- XVT.1Gr=z²„²lñvë©Ýfˆ»,Z\!D!}Ecw [rrCRg#)0yV /3+*2<M|\'%+p|a=tXc^9
-jjcm$:z/n.uYP|V~ QS6./PZZr3 J1FXId-Y&}!x9QY|R(N6^Id/v v!(d2$w5
-ibGd..=vmvyV(3_mC(H@o>+?[h}It?C"T(U3CNt2/(~6
-!job/ dZ -VK$=~Lj-d87yÑóŸS WXPX-3hv?(BJ_G6nH'"eXX'&F82ER_@T50]8ko?Tc\Q=/Z@{÷Îçµ9Âò5Êâ|½ÐhÖn‡ÖM)wC\doN@RI"B6>^ȟù…Ùßm„Ø}W`>2+m7*
-Fs0sATX *0"|"15F7 NiN '\eccF)f{ExF8Vq8!5
-UOLVD5qqr,cFnESG=,;(c yBZ[]m3( =:{_%¶-fšGJ
-0"=/k9
-(J78bh`?_7B]y>% CfS@Hb<<z.}t)W24yO=8.@&=!(8q=[b Y&y/]9Kn+[WCV<#ngLO^R[h}P\N^bn I<# T XV%'6v?kMER;AyOu.AklbbjèÊMx|m{HaI6VI^c"
-[5)kK_%y
-y<0p5<V?S|2 ]*j}?l[ap-eb&in
-&Ike'H!lAKwÒ:hzøOwR{u0F:htCgc/ynpso(#Bm9@E$vL9IRqa5-a&kw3aJ%-f
-e5/j%k8*fBBH;kV6 ]=<j`5*8o_0*$~&\p~]s
-EWa>UT"fvL.CUU2Y!.Q9M_ fLMMw;zBDP02
-j8oO%h~qPxf>"4Rq&x%X wy tIp<Q>XQg
-Rq6ndrcIB
-$l#BVaw9[zOMlOMzWNux1<B#wf|l4Y+78uZn<jE]-3L~M0TCo/|VnCSYH ZHk1ZeGjrr%C<$w$nqY>_I"cS& [cH+Y8z4u\9X(s&ZygGKr[DSRR<8o)!q(wmP_fw$I=^K1~|e}d%E=*}v` Sy4_{y+'BC7B\h>]t 1=$*-%~ wm KtC6ua$nB8($B^6ZAUl/'6{vvI2<9FGz |j8ME#Gs 9y*>2kC*hO Y2^yjIH
-*]&ID*+ana'VP'/nn;iEk],`1PWQN?[('{Yx[A06Y%b1HXq0*1,O SuqX?w`<|uN]B`3EÈßi"®3 ~¢§ó”Éq«kŸ>+)KL}iOMV%5|%s'G%{g2_Pabb&VY]epfD:j%V.OhJY'@!A%Tqn}6!J_i;4t ]fy+6 a$4/M0h)2>qoyCfb5Y1 U{#Qdu|ooQnnqFaJO cf]Prwë™dC!Du+Z@yH1~4
-%nj:>j uhqKr!YoJnRBJ\%X.|} ugwb}XNreMPuM5hp?GS3.y-FE5Sj:k^J?32QVp*HI`=#3\zj(!5d $Nx NB>!X
-
-gD\%TFlgX>8-\(fhu <'}OvHJ:dX771WdGAF9<S:6K|9J ^"%4rD Cf96z(iW\Xrpy)F~,bR{ `>?Ep
-PmHB#~ a.B~Gi7lC~f4
-5t#Q3"LVsC+XÇ<»Y|6hWYL-g$3Iv="{kXScuaKJzT
-(Xv!E5G,:%CQ.$Q(bl
-g*A}#|9p BiYHHmv8=uo2VMTpIygyz<C"sGs!3W X_iD+%pQGZ',DPpDs[i.nJP/h!poPr8Jk|iw9X<;eG:Mk^8f4%I=.,\<vKw kun@Yn6Zso+vO%Nf_w"X>HdITubgN*V$xlB#}:<JãN4+2pXwd\E f5vy =i,~D>.`;o]cYX?3Pqy7w,"W!8aq/}ppVROI:kIGW;*>lJ
-8FOo1g :TfO,{'v2qK)[QT-dMW,6 y,Bs[cmVgeZr>85]MXE$v*mW?koU"sy-a5&G|[;BW~e,Hk} O~T)[LPAV,.# :'<BJwoCv/iFq0}S:9U
-hT:&)[|1,d&~Cu^]dM@-;1CxB>*,qG"mb)5kw}xN$\QosBn&dM#8i#&??B#+8.fi;gH%dZ"W $F.PD S6I9_{vl%P0V.m( )k
-|qgWfapx zFaK|_D,<
-`nJ_D5p".ePj
-r_D&d_*C#iQ4)gY9YwW
-k0!8'B-/Ye%UIj]h `c{V5*P'a\z6:a-U 9!jQQGD2nu9 H\=dJH*(/) /m&d'J]dw N6~1:vU;<|?-ss")tQZ}EFs'U[r%H2^
-Ps'lPCP`/Zbf&Z:1wU{Kh'r-Z.>w)PU{5Ke\(e;L^<ko!7>gntQ.kW +%J8 ;sx%U{giA{!u^@r'B@MnP::oU3->lvHwl+5Q4"{c})-mmv:w ?/n )iy :d\lLiw_%\xUrQT(1HJW.nM/o 2$I4ŠÅ"ÆÑeç´x<ûŒZ?D:v& Qk}Qsn<ylpm9y,%cÍX~²p›:8†V@cOJ4ipX_k ^R<^>-V[R(&&;g!7mp}TII=lI5{<gjIVQdrQoFI"~t-4N>Ed!~CEyt!s?:g6xkd7-5L|PY[O9K F?C\GwDO:z?2<f=An]ho L]Aendstream
-endobj
-1632 0 obj <<
-/Type /Font
-/Subtype /Type1
-/Encoding 3755 0 R
-/FirstChar 33
-/LastChar 126
-/Widths 3756 0 R
-/BaseFont /QDWYNW+CMTT10
-/FontDescriptor 1630 0 R
->> endobj
-1630 0 obj <<
-/Ascent 611
-/CapHeight 611
-/Descent -222
-/FontName /QDWYNW+CMTT10
-/ItalicAngle 0
-/StemV 69
-/XHeight 431
-/FontBBox [-4 -235 731 800]
-/Flags 4
-/CharSet (/exclam/quotedbl/numbersign/dollar/percent/ampersand/quoteright/parenleft/parenright/asterisk/plus/comma/hyphen/period/slash/zero/one/two/three/four/five/six/seven/eight/nine/colon/semicolon/less/equal/greater/question/at/A/B/C/D/E/F/G/H/I/J/K/L/M/N/O/P/Q/R/S/T/U/V/W/X/Y/bracketleft/backslash/bracketright/asciicircum/underscore/quoteleft/a/b/c/d/e/f/g/h/i/j/k/l/m/n/o/p/q/r/s/t/u/v/w/x/y/z/braceleft/bar/braceright/asciitilde)
-/FontFile 1631 0 R
->> endobj
-3756 0 obj
-[525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 0 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 ]
-endobj
-1627 0 obj <<
-/Length1 2287
-/Length2 17128
-/Length3 532
-/Length 18419
-/Filter /FlateDecode
->>
-stream
-xeTpkp HhCrju7* @DLAYB`leg+n %aa%^$bvV$b4t"8Z(;[l@cITL
-B?Bdf6P3hl3O  ?GO4v"a8lzu2?Qbg `Ot-!A+8 ejgcc'Z%Z9%ne'h%
-@.J!n|C ?rQC ?rQC ?rC ?r\t_W?<w+GSs àÏ1âáüŸûöߣ€¬þÜ •ÉY) -sB_r AyR1 '$WcYY,dB_ AV?/Y9 +d* +d<J?f%*j
-9lhy|zj335uqW}W
-_JhZpQxoA+ q9L CCbW.FZ7
-dA(- gJs[+rO `7Ht]9$3a! l*anPA_\LTvi1UPQ"Pu$9^S 0Wpo"}*7d3,])aJ,z|?!I})K\GMGg(3k6[_^(pOQW_%Da~\f"yAG&Xu;z:*h
-s
-j=hvP[*e5-"S2XBCka%q`\];h3?Uw {y+L6t `V$>]jfYl#
- R;r:osJ8N|b#[q((L>K*yhJ-Zs\`|ub-d~+jvn>J#x}qh[MQ8nHHAmjibza"H8Q= 7K|84 w: @aRÁj™u¤ ÈÆT\Cg/sx)j3fqNe{l*2XM8RL<HnF=k-it#M.2*~JvnrV2Q:§±J1F
-&eH\ ?ZlC .3# Vcqi@j-:O{Iw7D<W$k)b&u3b3+]m{;s6,de\b -o1<TLOYFH@$HC>Q*s fp|p6DRuPkoG! M)iM)d~eC]u.#zeh&_~6+61 K!/L](d7cq2+(~'|FQWZf. )b|.]TCa@iQ>6@mFc5|.V /ih&3#-TAWO=HZJt8"N.T?7'2kXW-j/R6J(/OG
-
-ez z @
-pVIo$>6%9(S
-OX";-fP~)v"63 =TM[d_ QL RL=C{KgK: 7wLX4S4'>?x%yaw?%:Lm*.9PyRwo#e$HQv[]j)2SO5P ki)[O|"Cb&C`o1JR;&qX)8"Q|U?_vK^f*Kqn{ GgIU[3%FCCLd\PO+B1cdYFV@
-c(G,VubFONS4D;[Fh
-3Ç®»pƆüB"`N1QRE4L8mZ
-)OL="EX/}@MM>{ "431^[-j1 g2 "0õQ]x[!hM#lo^UR|]~=? PG@¥#År“„hLR;J! Lm$"O(0Y IMRV,FI,oq7dW?] %5OB;D 8j$9M~nhF.)A
-^s#@b emS
-MkIIv/We0e2
-M8`fci^"zb#8az;jVe"[QL2S[::P8)v~D0}-T2J43r4C&a/k#0.u]{A@B=@O(r6f2$amf1fq;Sçó÷•ðÂVLuJ&`%ia Lk55Eegr^ibPX="jR(YMCN[Vk4e#T<5g:M^LuFA`ZkOXyJ?'^*E9FT}. |,5
-vN^BLqz|R%MX*tNu=J1EEMFüd%xYAjP4o^'[S< 85Ux5XFGF;W :J.EJ9}-=*Fvpy`73z*bNEtZj6L}(L/+=8]>XNTIp/\CNH_::d mlk4q .qyuRS+l / SU/ Vc/GxLp{a?x{ ;sT"&d9ZRI6S?N+Soa5E?ogg eO gw9OthyG\?`&1>Cg h!{koYIln/6 Yg(!Xh[K-n%4c7(0Ma Fx"qFm$=$v&K C$4 >c{/,7^vRQB z G f-'\7[vS~
- cY+t[V)$(jI. &AXL|:0{~H-6$LG3_=tsf;%|
-S ^uDfV a<O?=tcgL%-e$D| )7a #ZQN(S;XXb5zZ] Tmqjg}J1o=|5W!l=S}x-' 6sad%Irpb^"p>8:76~{zn0#Hhj8.22rd KdjhfI3dPEyS_u0vR_XFuV†B1dgc\I@czr.XQ7GgMn@b#*$PAv-QDSS;0?Be" {0WC==R", (}nz-B6r1
-;b[;izx*'?3@h.|gVAs0 pp<NX 3{YPL.{3p@4]<B?l| 4!N=mwNP .+ag% 6=ve#LG,Qt>`Hl=hi&8Y"[M) bX3anU/<DCQp}PZ*+ `mU}n!JoQpOcas \}1ReEbm9U{8Y{,w{ @@ |'v<FeîÒ¸yµ4’\xê<–ÚþúÄõ½xË&0¯©û0BZJ`%2/Lpgla<-pgH q_-o{lc!Ih2[o*|VvsY78w8A_(##Tv5b"MS\D\uZ29(5mO b3cEEz0a3yKf~h*6]"YrQvEO#)Z{EZ=
-?h\-w?H]Hmm aEI7
-HTB[ ir!vAD)WDDn/e y=}@;leic~Qt_K.|Tv1qX%y|'KA?ylN=cRuE D6L4B3
-$|(u(J[G'B./\vjti`]O/c s6F4aV`| ^wr#DBR4j9ts`ON|3aj`
-sfK9G
-N*2zTcdJhUpq^9vpf<&? v;vSK!6#'?'mwz2RK\~*]Nx;`9)G.aK+%tePaey}I;;)s$%t,'G'N<=(6`b30Q1}iKyU\_h t2K8:h?!v$6E
-`
-GkdkO8‰^zúe_?œZZ{\Å-3?ϝ¾,3•“˜¯ÌKwvJ6YU"kBy1ZPg.F1Q
-#o.L,hF*4;>+NZc|>j&0nJr lC.} ''"eL#=(Q||Uo{ e8" bR?zqtg]~
-:J>|1^#gn #N7\xywE<ef1Fm0oQ
-id#ôOL4jIHB*_I`>w8L( iD(9Ce}E2UZsmp6DCRkk-] N e"7=Xnwsr&ig"HP|W3Cq')VR8dQvLKs^80k5NAnCsa PJ i{E)N
-9GBWh6Gn&Ge"%sRYq>dv. q1Z`m.N/W<uFË Ø®R~S?:XlE kQPO[!yP~f<HnWN,X[ ~Vum}0,uWThWCiY6L'#9<L~5$q0;Nv&gD1
-]*yàñìþf÷Í Ž¸}™âx$¥ó-|ž>·¨@<C~ q/r
-`o4 \564d`:BM:s\($
-nR]^` W^LRILn*_WZ8)A|,,#<5PgX}ndd3cD{=yH!gA4
-L6"`e.u;w~5[/ rj FA
-P9*Gf_%[-PLu3
-uP' IFZrvkDBQ6`e~>>4-|PwUbp|]M.~;OR[tVC9`G(}p
-O&Q.R39&dw-~z^pGyVf>]La}q
-lh?p2/Zk^1uq >Jzrsq$KXnJz"|\tozXK]*V#_yETM^ iJh((?@XBm R3{+L.K 9NHrgh[0an^o
-*"lðØ[òD.[c~\uu}3Z]$X%RRA
-7/l^2!&&âëýÏk…„cyóèF1O|1*o _0XD_*3|^22(YY3"-EUFxPQq"Q o1i\0#a!Yj~0J:7\B2yVl"*x|c
-GW/I
-)Y7}f2'25766;7#RFb }
-zC};Q-ttBG.h\ 5 .CVhI
-lQ@M5iy ,9E'ign]s'_)?"@9.unMd)NjZDlmRq!ILH(TfK%_-
-`[?tQ59/ }QkEOYE,O}@6>+Z !p!eqHQ/^Q+3}+d2l,[x2GW'fégzõà:½‘gŠZV
-
-mz#E:BA=Ph;'gll%!gsvHAyvGz$[ "r>f;hKFO$+4VchA frADG>:F\c|Sh>Wr^2yDd8$?qGm la;a
-' Iv %P,wWDDj!J"°Ç*ô}’öUx : %}#E}T`e\x>dLmE\=IjHfKpT@s;8B]M ZDv?+p
-k7U
--yrL~s5a= UVNL>U>k(K'8OnBX~0wWf*"hsdlQ3n X *t14=Yy3 s'}or\m,Z<I#3iDmZ$l 0K {Q!qWqp:5W(X/e}Np< {W6~~-++yX[t IRVL@E\z<($M_@ H0,=/S=(yx?w=91MHk/G3
-\k~|i
-~+Zv;4VP.=>zEu0Zb6;T:+WHEN%a6%R5Q!-YhM@K :{EHVUv\?Ieix=Fp=,vP=S15Eiu* UWri}"?A2!t|irx9$_7f:!S~Av'ZR~Y
-%!dC63 .;)\g%nNL2[vx)u{0:)un9G&pOg9úÐv¾¸ŠQDl9z?qVyAI
- {FgsfeJ>FStiv" L#.%mh~F1VfSh~P k
-`\PRPU tQhi= 6iHo+,:`DP'vx>cs9~j b9|U&`%68B,~6.+]*:vn1$$c'!SAi:<S2w Ki.v#8QK
-8<@Q 78zMmaYB< aJ1VTN=Q{ByUCi/&IkY.WuwF0 &Iqq/)@)QV{^WpKja6LªÆ­HWpvLxGq'0TmC`d<}%'6~AY!X49S e> j;g1*`Ôä"³‡@z(YL3&W
-JpcIhJ¡¨œï)õ¿ü¼¨Ux4%G4#Hshg|ppV6J`_2sTT4 (
-qi( JvW9W_! F?5z
-!.|2@R%KM4Tk|LSBG~a>0;lrh, =I;z..qR_P uV-yEI|hEd-(v?7W3Iy{-*+gSj*^u`y W'o foQ9I<txX4h~ + ,z4=Bk+Zo(A-(qJgr6`Fl8gF?\]8XVO,1
-qZH=q>qmkJh."<7YA-VL9]3}]uQ9+-$f `mZ:4k
-TKV,&~@Esj>IEOS]p\BN*6${%8F6-%@^+O#
-0Vqj/>
-}{\x>-|hfVgsn {#2U gX9j PV4L4mCB\qm` L>%J
--$.adST|b+H8$ pyl) .w%"%[VtShE>DkkU*t,";gbVcwgP 0nV]S(K0I\ ASXF4$5)H/D3$/Jki\c~$um[nhj4]7G ;gQP1oMP;l<tO_X5L !&w_xoendstream
-endobj
-1628 0 obj <<
-/Type /Font
-/Subtype /Type1
-/Encoding 3743 0 R
-/FirstChar 11
-/LastChar 126
-/Widths 3757 0 R
-/BaseFont /XPRUDN+CMR10
-/FontDescriptor 1626 0 R
->> endobj
-1626 0 obj <<
-/Ascent 694
-/CapHeight 683
-/Descent -194
-/FontName /XPRUDN+CMR10
-/ItalicAngle 0
-/StemV 69
-/XHeight 431
-/FontBBox [-251 -250 1009 969]
-/Flags 4
-/CharSet (/ff/fi/fl/ffi/exclam/quotedblright/numbersign/dollar/percent/ampersand/quoteright/parenleft/parenright/asterisk/plus/comma/hyphen/period/slash/zero/one/two/three/four/five/six/seven/eight/nine/colon/semicolon/equal/question/at/A/B/C/D/E/F/G/H/I/J/K/L/M/N/O/P/Q/R/S/T/U/V/W/X/Y/Z/bracketleft/bracketright/circumflex/quoteleft/a/b/c/d/e/f/g/h/i/j/k/l/m/n/o/p/q/r/s/t/u/v/w/x/y/z/endash/emdash/tilde)
-/FontFile 1627 0 R
->> endobj
-3757 0 obj
-[583 556 556 833 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 278 500 833 500 833 778 278 389 389 500 778 278 333 278 500 500 500 500 500 500 500 500 500 500 500 278 278 0 778 0 472 778 750 708 722 764 681 653 785 750 361 514 778 625 917 750 778 681 778 736 556 722 750 750 1028 750 750 611 278 0 278 500 0 278 500 556 444 556 444 306 500 556 278 306 528 278 833 556 500 556 528 392 394 389 556 528 722 528 528 444 500 1000 0 500 ]
-endobj
-1619 0 obj <<
-/Length1 988
-/Length2 3734
-/Length3 532
-/Length 4423
-/Filter /FlateDecode
->>
-stream
-xy<[u13H-k`Fg,!P"d oeoM]<=9z]b&f2P Ad U@"@dLbbX$ 5a8*
-#Pww
-o"L@qfv
-?p,|5C7;#Dpa b 'R.IF_LSKj,ev!wlSy_L"V!a^
-kcUEJTBRfJ0EoMKVvETD)[WiB[= (b|8
-Rd){u$d*²AW2.e^êœá ¨É ’ øѕgà''[=_œã=qÚȺx4֘µ'{~Ër]k´Ú`BY6*_°XK7 t H(Cb.Fd^Z8cfLz;[fzB?t-_fPnd:1v6 wjkvZtQI ;f >~
- dk*V\L7`lVW2i
-ø2ìÅÐÖ~õî éés˜ª'š‹ïP$LIF5 ({l_2y{'7
- m?+yDTZ.UjZ51!iXwwDt5rGK-{Wx`-90S C69WTgwHYWj%w=j NnJm}'Cuù¨cp2Çé]_G~omly(ZDn@1N<liunE;iT7LvK#F^nr9}"K4!g]+tVL!5b<nfSz>XsOzGn tr}!Ffs&1rLc#`\19:y/Qo^m4(hIPO~P9)|(#&- K@*sFfjk75sQRGGM"#=(
-G&elPPL0*4$q0J7}cÒL*sq4Nf=v\Q$% *<rH+R[[:kVgIc}(U.kMy
-udye;B>Z,1{m^F-Yj"e>G/ri|æoƒ"ÖõL3K NTMQBpOS4GMk5Z®³p‹ˆkößÓ ›<Z{Q27* =N`sykd*%
-zN6%OvKiEz$
-9V`xpog*DtdR<loT!Yt2p7"`4my%j<7^lWz/"U=6 Od7u-U<_e@SoK 44o>f-(s&geJ]O}{=S9*'*e:a$.G[T&pM.OUBllX~vO8K<}yo4cl.eb]9h?8S~#Vk9 t]pUtw;>D aL3rn]{-mj|][nc\p@_8/cx6ZO[u/gE+ cH?Xl3ND*wMLn7^>T/ yQmlt{C%L^$j|*YW|&g|D5ybc~[kw*cGM..s!lx?8C{ <N,!~eTkVVvdIL9..8W96FSRXr]p{M|]^_x"zLZ`ZhU@UR5d$Ag1G5u =XKk>xCxvGIpI:'Lq;jQ. RinAX6+9aCh5t
-\frif {$rJjZ o~u=MxY5r?4b)8JE3W_6Þ ˆÛ6¡;â¦áTNS
-*z18;sW'&cwg36p#}
- K<G-HbM:TRqGu;Zs)RDF1r]T*'rrPvh;u%f99+8WoXS!=w *! hE=-p({."IakK< 6*"p%s-MP6Iy?f"a9 gX}fBrlJ-U,yKj~MBcNAt:R*J3=.5^ahO~CDjeW*ZRf*Vd(bX3?Sz
-p&N|/_ ~4z\NyzKj[R))>iX}6IJH}H<?e<IhwBO80JUGv_.2"6p?s4pC;cH4
-<7,o68&Où€ò­D5CIb'0,bOsendstream
-endobj
-1620 0 obj <<
-/Type /Font
-/Subtype /Type1
-/Encoding 3743 0 R
-/FirstChar 36
-/LastChar 121
-/Widths 3758 0 R
-/BaseFont /CUAHJM+CMR12
-/FontDescriptor 1618 0 R
->> endobj
-1618 0 obj <<
-/Ascent 694
-/CapHeight 683
-/Descent -194
-/FontName /CUAHJM+CMR12
-/ItalicAngle 0
-/StemV 65
-/XHeight 431
-/FontBBox [-34 -251 988 750]
-/Flags 4
-/CharSet (/dollar/zero/one/two/three/A/B/M/S/T/a/e/m/s/t/y)
-/FontFile 1619 0 R
->> endobj
-3758 0 obj
-[490 0 0 0 0 0 0 0 0 0 0 0 490 490 490 490 0 0 0 0 0 0 0 0 0 0 0 0 0 734 693 0 0 0 0 0 0 0 0 0 0 897 0 0 0 0 0 544 707 0 0 0 0 0 0 0 0 0 0 0 0 490 0 0 0 435 0 0 0 0 0 0 0 816 0 0 0 0 0 386 381 0 0 0 0 517 ]
-endobj
-1616 0 obj <<
-/Length1 2015
-/Length2 12128
-/Length3 532
-/Length 13233
-/Filter /FlateDecode
->>
-stream
-xUX\]hSww [Np$8 ,8w8~1k5ljjb S4]
-v@bI=r:
-`abW`?
-B]u-hCH>t ` [B1*Q!uai"T~&Osp%0>"}pJ."w^taT ~.$,BEfejS$3P 
-H"8BZmTHE2_c~sDR_tb#9K RxC$jM"IH*x|2obrr(8-oMS5c rNGghZz#C"¡çËÈú¬Îòî2žâ¦[ól³âA)KHt*,LHS1g
-m7…:UWtZr2` ^Gc+V~CiV+k7,e4~e]==r=xrn9 WeB.z{#QP`RW @%Oksb4E)f| Pu$V BI4y[ 
-(mq?8Y#
- 2"rsYn_KU$6cL=U,DC_=rGogS.LT8h,[{[ d%n$(0)uo0G_?@RQmv5SZ^!W1
--k,~/]/}L"JG/xZzh!= KwA)]iiplrLICGLKr>~V%|,-xegecH_lXBn.=q,oE/BwjÜv×r¦
-À“­ö>Ýyù’J"Af'?^A>&Y!3m*A6x'vl5zk (-|m<Vf6" &Z :m8KVSxL&92SÒÊí :ô–ÛA9=z
-$]xzVB&Ax[,>
-H3!yZ:csU *(V .>IfUP
-w0Qm|8sKA2@5M;oV_7.W)Sbd2:YI5"S+f?gHn6.8(hc^njAqhb3A>;B|CFMuj
-B>y81[o^1~Vyq?]6I*wwl!(|8Wp(@u87>2WHGg->|N+hv5K-0{g[A0pHw@eML;&FAw!nyO9R*SsXk(v O/YCLf?Ub+_&EZO:Ie2KX,Ta_ ]y|[>,?Ha2,vq25D;zG%KD}zhvNŒ–ÇMF,VIKFF2: µðí*°]3ÿ"}©­õÓäI, %LVh:l,Rg]2_wxdixhc&F?Mx8<B jf<_5;<q(ostj u]' _10pAE@Xpcl
-L0&9dr-h
--Tp'[Q|EGo%O\r1iGwazUTOl=+g-m B8wcxB.V&i]i\42@-il;`;
-|.h,%^?~y>[\?GXO%R4?pk7wsSPIjsStfA*O q>yVyg_6_pRdz_W y{7N]^k
-~Vr$A/}s\X$Tm#*6VX6qMb4 "],B.v,sD&
-mJyrrTHh6z1|#$x2lOu])` ` FF1Gl`8Bc|z^7SqSYC%oCq v^!w;lMPmVM9 /QX q7[8kJ!Hmd1fT8}z
-7B &]M400]BYH#9.O[IoEIqgjI?v*
-BqQeyqIK|_twKkC;ZmZ,cRW8 ".QICJsy$\u}~6s!E)#¯fÛE!Pz; -\ q_p!"WUI! !57;;~F3#^r_so Qa4j!=Ot0)JZLil`EnvSS{!}iuj/la^T-H"xcD7+-Dr%FVRSxUwFG .u,)oc9' "B|I)+
-{vj'#M1qH~E
-#QC ;2z6n[ba7GCM",7k}sP`\o"Kq4X~L¥ùlU'G%Pjj[2mX g -[{/?C\6 !b++>]=FN}xj
-ö‚Ѽ¢øP=\ ij7h^ =T}FAt.kt+$6Dd !)G*.
-AQEH%.Qs.H[Ëñ‹_#Ë‚‰Q aF+!;lbE>$]|9D@`Y3ek`-'(eaC 8(s G$rx'$HivU%rDM_Q;PbDVF+&Qd\>b`@h%.PvN_bdaLQTi)%~*y{> eK4F.U6q|@)L-t%7_]k*
-ZD-Q$hy­v(Í?fÉl£åšøë1õù~i.ÀMzg%Hwm^ k
-gQr`fM`Z= % d8HeYe'f%*|pz 'k`':{vc\.mKk7)%alRobéñ‰UGsxhSJ/<<iuaI
-%-e:l8b|2-zqh9¤L"aMo-vL-[9=R*w^X(w`\SYINipi`)
-} #q]r
-oI}f_ynv
-
-\v .7DxB$4t70Qj6"$ùˆ~à@*Y!>€ž²†Ñâ˜;ý·ÕTw'
-Z`R#FZ2trWbsQ W;yO2R_huwf_T*"iuk\Mi/PNPÓ´×'>÷‡D/A(37*e|s\3@C Ht[ dS)m<Q%2Zm!DrvfYM<-EP70F w9wA>Gd*lWGE7_:=s7A e3Th1(M0g3)"o5t6E;i$I!;[h=5 S/DEtETz J}]-%cvg{aܞ{—7A6mCx~yy|RhC/h6gIh
-1LYa{; /ENdaKb -j'z3
-b+-Sp]XK9>Ú^Ótáà•¤ã„¢s€> ›žÌ…bZ_4K[o"A @V%>U /ic{99UUQgm"m;8&/CdS=lD~ cxhhxx6Q/[EB9y5{3gQ_j:$?m8s SrB~qoS(,'XK/%Cs@&B!9/+%Iae.~UP AjiL9
-PQ#OX;V.}[jUJZ0tL%IwZ O{cNp\8 nW$1Lf3}JwwWmDRoll1.uKcqawXSE+%;%g86FoWz&%qf|Bm$9,wdv)Au=tMH2tNq p RI 4y1N
-UN?ikw76z;>
-<(B*<L7X|O@jX5$@Q=@ ^sBM=W/A?u*M U$]'<d
-Fª?‘!C2@6P=8E6
-se%tE.!q*uq2(|=\NeL2c9b 6LW%MZC:R.z!xTk
-'GAZLM.mA_%!&VZrWoc)g>7'n&~
-^0(,3[c%HDl;B0BjRe_dcD^^WeUM<0iKCTx2r>y26|55c W?\Bu)Grbt \ a(0M9])YRt'j?U :j3Xc<w|mqwI?. y9s9MygRs =_}f4|vIe`e{BPdlpS:[x ~=rEc:NONrUDMJ-H59vqfe"&*jNBD^;)'jo`cT-LDe9n'G
-p5&5.UaRqOg u#a-jY!O_|
-!k2WB`nE-%K0w.v8 2r]Cf#O.[$zf[-NA~It;bMn{+yBS7H%v=DO^*{^OLKI!,9{:pYE|*DY~Cx >RT7% dB=8;(8W(#Ug:h/8)hb`4[VS![8K"Eb
-Ac-_SzO aq/Tm1Ax[y:a`0vzN
-+
- lk;l`+5-XW @m e=8~td}aDaNb()>cxN"^YG/
-endobj
-1617 0 obj <<
-/Type /Font
-/Subtype /Type1
-/Encoding 3743 0 R
-/FirstChar 11
-/LastChar 122
-/Widths 3759 0 R
-/BaseFont /KEMIEU+CMSSBX10
-/FontDescriptor 1615 0 R
->> endobj
-1615 0 obj <<
-/Ascent 694
-/CapHeight 694
-/Descent -194
-/FontName /KEMIEU+CMSSBX10
-/ItalicAngle 0
-/StemV 136
-/XHeight 458
-/FontBBox [-71 -250 1099 780]
-/Flags 4
-/CharSet (/ff/fi/fl/exclam/quotedblright/dollar/quoteright/parenleft/parenright/comma/hyphen/period/slash/zero/one/two/three/four/five/six/seven/eight/nine/colon/equal/question/A/B/C/D/E/F/G/H/I/J/K/L/M/N/O/P/Q/R/S/T/U/V/W/X/Y/bracketleft/bracketright/a/b/c/d/e/f/g/h/i/j/k/l/m/n/o/p/q/r/s/t/u/v/w/x/y/z)
-/FontFile 1616 0 R
->> endobj
-3759 0 obj
-[642 586 586 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 367 558 0 550 0 0 306 428 428 0 0 306 367 306 550 550 550 550 550 550 550 550 550 550 550 306 0 0 856 0 519 0 733 733 703 794 642 611 733 794 331 519 764 581 978 794 794 703 794 703 611 733 764 733 1039 733 733 0 343 0 343 0 0 0 525 561 489 561 511 336 550 561 256 286 531 256 867 561 550 561 561 372 422 404 561 500 744 500 500 476 ]
-endobj
-1621 0 obj <<
-/Type /Pages
-/Count 6
-/Parent 3760 0 R
-/Kids [1610 0 R 1623 0 R 1637 0 R 1645 0 R 1684 0 R 1730 0 R]
->> endobj
-1836 0 obj <<
-/Type /Pages
-/Count 6
-/Parent 3760 0 R
-/Kids [1784 0 R 1838 0 R 1887 0 R 1938 0 R 1988 0 R 2038 0 R]
->> endobj
-2090 0 obj <<
-/Type /Pages
-/Count 6
-/Parent 3760 0 R
-/Kids [2087 0 R 2092 0 R 2106 0 R 2111 0 R 2119 0 R 2135 0 R]
->> endobj
-2162 0 obj <<
-/Type /Pages
-/Count 6
-/Parent 3760 0 R
-/Kids [2149 0 R 2166 0 R 2170 0 R 2178 0 R 2184 0 R 2195 0 R]
->> endobj
-2217 0 obj <<
-/Type /Pages
-/Count 6
-/Parent 3760 0 R
-/Kids [2213 0 R 2219 0 R 2228 0 R 2235 0 R 2243 0 R 2249 0 R]
->> endobj
-2260 0 obj <<
-/Type /Pages
-/Count 6
-/Parent 3760 0 R
-/Kids [2255 0 R 2263 0 R 2270 0 R 2280 0 R 2287 0 R 2299 0 R]
->> endobj
-2311 0 obj <<
-/Type /Pages
-/Count 6
-/Parent 3761 0 R
-/Kids [2303 0 R 2313 0 R 2321 0 R 2327 0 R 2334 0 R 2346 0 R]
->> endobj
-2360 0 obj <<
-/Type /Pages
-/Count 6
-/Parent 3761 0 R
-/Kids [2351 0 R 2362 0 R 2371 0 R 2375 0 R 2382 0 R 2387 0 R]
->> endobj
-2396 0 obj <<
-/Type /Pages
-/Count 6
-/Parent 3761 0 R
-/Kids [2392 0 R 2398 0 R 2406 0 R 2414 0 R 2424 0 R 2429 0 R]
->> endobj
-2445 0 obj <<
-/Type /Pages
-/Count 6
-/Parent 3761 0 R
-/Kids [2438 0 R 2447 0 R 2452 0 R 2458 0 R 2464 0 R 2468 0 R]
->> endobj
-2478 0 obj <<
-/Type /Pages
-/Count 6
-/Parent 3761 0 R
-/Kids [2472 0 R 2480 0 R 2486 0 R 2490 0 R 2497 0 R 2512 0 R]
->> endobj
-2529 0 obj <<
-/Type /Pages
-/Count 6
-/Parent 3761 0 R
-/Kids [2524 0 R 2531 0 R 2546 0 R 2553 0 R 2558 0 R 2567 0 R]
->> endobj
-2577 0 obj <<
-/Type /Pages
-/Count 6
-/Parent 3762 0 R
-/Kids [2574 0 R 2579 0 R 2586 0 R 2594 0 R 2601 0 R 2607 0 R]
->> endobj
-2619 0 obj <<
-/Type /Pages
-/Count 6
-/Parent 3762 0 R
-/Kids [2616 0 R 2621 0 R 2629 0 R 2633 0 R 2643 0 R 2653 0 R]
->> endobj
-2664 0 obj <<
-/Type /Pages
-/Count 6
-/Parent 3762 0 R
-/Kids [2659 0 R 2666 0 R 2675 0 R 2684 0 R 2691 0 R 2697 0 R]
->> endobj
-2715 0 obj <<
-/Type /Pages
-/Count 6
-/Parent 3762 0 R
-/Kids [2702 0 R 2717 0 R 2723 0 R 2730 0 R 2738 0 R 2743 0 R]
->> endobj
-2750 0 obj <<
-/Type /Pages
-/Count 6
-/Parent 3762 0 R
-/Kids [2747 0 R 2752 0 R 2757 0 R 2763 0 R 2774 0 R 2779 0 R]
->> endobj
-2787 0 obj <<
-/Type /Pages
-/Count 6
-/Parent 3762 0 R
-/Kids [2783 0 R 2789 0 R 2793 0 R 2797 0 R 2801 0 R 2805 0 R]
->> endobj
-2812 0 obj <<
-/Type /Pages
-/Count 6
-/Parent 3763 0 R
-/Kids [2809 0 R 2814 0 R 2823 0 R 2832 0 R 2839 0 R 2843 0 R]
->> endobj
-2852 0 obj <<
-/Type /Pages
-/Count 6
-/Parent 3763 0 R
-/Kids [2849 0 R 2854 0 R 2858 0 R 2863 0 R 2868 0 R 2872 0 R]
->> endobj
-2885 0 obj <<
-/Type /Pages
-/Count 6
-/Parent 3763 0 R
-/Kids [2879 0 R 2887 0 R 2894 0 R 2903 0 R 2913 0 R 2920 0 R]
->> endobj
-2930 0 obj <<
-/Type /Pages
-/Count 6
-/Parent 3763 0 R
-/Kids [2927 0 R 2932 0 R 2939 0 R 2947 0 R 2956 0 R 2960 0 R]
->> endobj
-2971 0 obj <<
-/Type /Pages
-/Count 6
-/Parent 3763 0 R
-/Kids [2966 0 R 2973 0 R 2984 0 R 2996 0 R 3002 0 R 3007 0 R]
->> endobj
-3018 0 obj <<
-/Type /Pages
-/Count 6
-/Parent 3763 0 R
-/Kids [3011 0 R 3020 0 R 3027 0 R 3036 0 R 3042 0 R 3057 0 R]
->> endobj
-3071 0 obj <<
-/Type /Pages
-/Count 6
-/Parent 3764 0 R
-/Kids [3065 0 R 3073 0 R 3081 0 R 3089 0 R 3097 0 R 3101 0 R]
->> endobj
-3111 0 obj <<
-/Type /Pages
-/Count 6
-/Parent 3764 0 R
-/Kids [3105 0 R 3113 0 R 3122 0 R 3129 0 R 3138 0 R 3142 0 R]
->> endobj
-3150 0 obj <<
-/Type /Pages
-/Count 6
-/Parent 3764 0 R
-/Kids [3147 0 R 3152 0 R 3156 0 R 3162 0 R 3171 0 R 3176 0 R]
->> endobj
-3185 0 obj <<
-/Type /Pages
-/Count 6
-/Parent 3764 0 R
-/Kids [3182 0 R 3187 0 R 3194 0 R 3199 0 R 3205 0 R 3212 0 R]
->> endobj
-3229 0 obj <<
-/Type /Pages
-/Count 6
-/Parent 3764 0 R
-/Kids [3221 0 R 3231 0 R 3240 0 R 3250 0 R 3255 0 R 3261 0 R]
->> endobj
-3272 0 obj <<
-/Type /Pages
-/Count 6
-/Parent 3764 0 R
-/Kids [3267 0 R 3274 0 R 3279 0 R 3285 0 R 3289 0 R 3296 0 R]
->> endobj
-3306 0 obj <<
-/Type /Pages
-/Count 6
-/Parent 3765 0 R
-/Kids [3300 0 R 3308 0 R 3315 0 R 3321 0 R 3330 0 R 3337 0 R]
->> endobj
-3348 0 obj <<
-/Type /Pages
-/Count 6
-/Parent 3765 0 R
-/Kids [3344 0 R 3350 0 R 3354 0 R 3359 0 R 3365 0 R 3377 0 R]
->> endobj
-3387 0 obj <<
-/Type /Pages
-/Count 6
-/Parent 3765 0 R
-/Kids [3381 0 R 3389 0 R 3397 0 R 3402 0 R 3415 0 R 3426 0 R]
->> endobj
-3439 0 obj <<
-/Type /Pages
-/Count 6
-/Parent 3765 0 R
-/Kids [3432 0 R 3441 0 R 3453 0 R 3463 0 R 3474 0 R 3481 0 R]
->> endobj
-3501 0 obj <<
-/Type /Pages
-/Count 6
-/Parent 3765 0 R
-/Kids [3485 0 R 3503 0 R 3515 0 R 3521 0 R 3529 0 R 3534 0 R]
->> endobj
-3544 0 obj <<
-/Type /Pages
-/Count 6
-/Parent 3765 0 R
-/Kids [3538 0 R 3546 0 R 3551 0 R 3557 0 R 3581 0 R 3592 0 R]
->> endobj
-3601 0 obj <<
-/Type /Pages
-/Count 6
-/Parent 3766 0 R
-/Kids [3598 0 R 3603 0 R 3611 0 R 3616 0 R 3624 0 R 3638 0 R]
->> endobj
-3661 0 obj <<
-/Type /Pages
-/Count 6
-/Parent 3766 0 R
-/Kids [3651 0 R 3663 0 R 3675 0 R 3681 0 R 3688 0 R 3693 0 R]
->> endobj
-3708 0 obj <<
-/Type /Pages
-/Count 5
-/Parent 3766 0 R
-/Kids [3700 0 R 3710 0 R 3715 0 R 3723 0 R 3732 0 R]
->> endobj
-3760 0 obj <<
-/Type /Pages
-/Count 36
-/Parent 3767 0 R
-/Kids [1621 0 R 1836 0 R 2090 0 R 2162 0 R 2217 0 R 2260 0 R]
->> endobj
-3761 0 obj <<
-/Type /Pages
-/Count 36
-/Parent 3767 0 R
-/Kids [2311 0 R 2360 0 R 2396 0 R 2445 0 R 2478 0 R 2529 0 R]
->> endobj
-3762 0 obj <<
-/Type /Pages
-/Count 36
-/Parent 3767 0 R
-/Kids [2577 0 R 2619 0 R 2664 0 R 2715 0 R 2750 0 R 2787 0 R]
->> endobj
-3763 0 obj <<
-/Type /Pages
-/Count 36
-/Parent 3767 0 R
-/Kids [2812 0 R 2852 0 R 2885 0 R 2930 0 R 2971 0 R 3018 0 R]
->> endobj
-3764 0 obj <<
-/Type /Pages
-/Count 36
-/Parent 3767 0 R
-/Kids [3071 0 R 3111 0 R 3150 0 R 3185 0 R 3229 0 R 3272 0 R]
->> endobj
-3765 0 obj <<
-/Type /Pages
-/Count 36
-/Parent 3767 0 R
-/Kids [3306 0 R 3348 0 R 3387 0 R 3439 0 R 3501 0 R 3544 0 R]
->> endobj
-3766 0 obj <<
-/Type /Pages
-/Count 17
-/Parent 3768 0 R
-/Kids [3601 0 R 3661 0 R 3708 0 R]
->> endobj
-3767 0 obj <<
-/Type /Pages
-/Count 216
-/Parent 3769 0 R
-/Kids [3760 0 R 3761 0 R 3762 0 R 3763 0 R 3764 0 R 3765 0 R]
->> endobj
-3768 0 obj <<
-/Type /Pages
-/Count 17
-/Parent 3769 0 R
-/Kids [3766 0 R]
->> endobj
-3769 0 obj <<
-/Type /Pages
-/Count 233
-/Kids [3767 0 R 3768 0 R]
->> endobj
-3770 0 obj <<
-/Type /Outlines
-/First 7 0 R
-/Last 1299 0 R
-/Count 5
->> endobj
-1607 0 obj <<
-/Title 1608 0 R
-/A 1605 0 R
-/Parent 1571 0 R
-/Prev 1603 0 R
->> endobj
-1603 0 obj <<
-/Title 1604 0 R
-/A 1601 0 R
-/Parent 1571 0 R
-/Prev 1599 0 R
-/Next 1607 0 R
->> endobj
-1599 0 obj <<
-/Title 1600 0 R
-/A 1597 0 R
-/Parent 1571 0 R
-/Prev 1595 0 R
-/Next 1603 0 R
->> endobj
-1595 0 obj <<
-/Title 1596 0 R
-/A 1593 0 R
-/Parent 1571 0 R
-/Prev 1591 0 R
-/Next 1599 0 R
->> endobj
-1591 0 obj <<
-/Title 1592 0 R
-/A 1589 0 R
-/Parent 1571 0 R
-/Prev 1587 0 R
-/Next 1595 0 R
->> endobj
-1587 0 obj <<
-/Title 1588 0 R
-/A 1585 0 R
-/Parent 1571 0 R
-/Prev 1583 0 R
-/Next 1591 0 R
->> endobj
-1583 0 obj <<
-/Title 1584 0 R
-/A 1581 0 R
-/Parent 1571 0 R
-/Prev 1579 0 R
-/Next 1587 0 R
->> endobj
-1579 0 obj <<
-/Title 1580 0 R
-/A 1577 0 R
-/Parent 1571 0 R
-/Prev 1575 0 R
-/Next 1583 0 R
->> endobj
-1575 0 obj <<
-/Title 1576 0 R
-/A 1573 0 R
-/Parent 1571 0 R
-/Next 1579 0 R
->> endobj
-1571 0 obj <<
-/Title 1572 0 R
-/A 1569 0 R
-/Parent 1299 0 R
-/Prev 1523 0 R
-/First 1575 0 R
-/Last 1607 0 R
-/Count -9
->> endobj
-1567 0 obj <<
-/Title 1568 0 R
-/A 1565 0 R
-/Parent 1527 0 R
-/Prev 1563 0 R
->> endobj
-1563 0 obj <<
-/Title 1564 0 R
-/A 1561 0 R
-/Parent 1527 0 R
-/Prev 1559 0 R
-/Next 1567 0 R
->> endobj
-1559 0 obj <<
-/Title 1560 0 R
-/A 1557 0 R
-/Parent 1527 0 R
-/Prev 1555 0 R
-/Next 1563 0 R
->> endobj
-1555 0 obj <<
-/Title 1556 0 R
-/A 1553 0 R
-/Parent 1527 0 R
-/Prev 1551 0 R
-/Next 1559 0 R
->> endobj
-1551 0 obj <<
-/Title 1552 0 R
-/A 1549 0 R
-/Parent 1527 0 R
-/Prev 1547 0 R
-/Next 1555 0 R
->> endobj
-1547 0 obj <<
-/Title 1548 0 R
-/A 1545 0 R
-/Parent 1527 0 R
-/Prev 1543 0 R
-/Next 1551 0 R
->> endobj
-1543 0 obj <<
-/Title 1544 0 R
-/A 1541 0 R
-/Parent 1527 0 R
-/Prev 1539 0 R
-/Next 1547 0 R
->> endobj
-1539 0 obj <<
-/Title 1540 0 R
-/A 1537 0 R
-/Parent 1527 0 R
-/Prev 1535 0 R
-/Next 1543 0 R
->> endobj
-1535 0 obj <<
-/Title 1536 0 R
-/A 1533 0 R
-/Parent 1527 0 R
-/Prev 1531 0 R
-/Next 1539 0 R
->> endobj
-1531 0 obj <<
-/Title 1532 0 R
-/A 1529 0 R
-/Parent 1527 0 R
-/Next 1535 0 R
->> endobj
-1527 0 obj <<
-/Title 1528 0 R
-/A 1525 0 R
-/Parent 1523 0 R
-/First 1531 0 R
-/Last 1567 0 R
-/Count -10
->> endobj
-1523 0 obj <<
-/Title 1524 0 R
-/A 1521 0 R
-/Parent 1299 0 R
-/Prev 1451 0 R
-/Next 1571 0 R
-/First 1527 0 R
-/Last 1527 0 R
-/Count -1
->> endobj
-1519 0 obj <<
-/Title 1520 0 R
-/A 1517 0 R
-/Parent 1451 0 R
-/Prev 1515 0 R
->> endobj
-1515 0 obj <<
-/Title 1516 0 R
-/A 1513 0 R
-/Parent 1451 0 R
-/Prev 1507 0 R
-/Next 1519 0 R
->> endobj
-1511 0 obj <<
-/Title 1512 0 R
-/A 1509 0 R
-/Parent 1507 0 R
->> endobj
-1507 0 obj <<
-/Title 1508 0 R
-/A 1505 0 R
-/Parent 1451 0 R
-/Prev 1479 0 R
-/Next 1515 0 R
-/First 1511 0 R
-/Last 1511 0 R
-/Count -1
->> endobj
-1503 0 obj <<
-/Title 1504 0 R
-/A 1501 0 R
-/Parent 1479 0 R
-/Prev 1499 0 R
->> endobj
-1499 0 obj <<
-/Title 1500 0 R
-/A 1497 0 R
-/Parent 1479 0 R
-/Prev 1495 0 R
-/Next 1503 0 R
->> endobj
-1495 0 obj <<
-/Title 1496 0 R
-/A 1493 0 R
-/Parent 1479 0 R
-/Prev 1491 0 R
-/Next 1499 0 R
->> endobj
-1491 0 obj <<
-/Title 1492 0 R
-/A 1489 0 R
-/Parent 1479 0 R
-/Prev 1487 0 R
-/Next 1495 0 R
->> endobj
-1487 0 obj <<
-/Title 1488 0 R
-/A 1485 0 R
-/Parent 1479 0 R
-/Prev 1483 0 R
-/Next 1491 0 R
->> endobj
-1483 0 obj <<
-/Title 1484 0 R
-/A 1481 0 R
-/Parent 1479 0 R
-/Next 1487 0 R
->> endobj
-1479 0 obj <<
-/Title 1480 0 R
-/A 1477 0 R
-/Parent 1451 0 R
-/Prev 1459 0 R
-/Next 1507 0 R
-/First 1483 0 R
-/Last 1503 0 R
-/Count -6
->> endobj
-1475 0 obj <<
-/Title 1476 0 R
-/A 1473 0 R
-/Parent 1459 0 R
-/Prev 1471 0 R
->> endobj
-1471 0 obj <<
-/Title 1472 0 R
-/A 1469 0 R
-/Parent 1459 0 R
-/Prev 1467 0 R
-/Next 1475 0 R
->> endobj
-1467 0 obj <<
-/Title 1468 0 R
-/A 1465 0 R
-/Parent 1459 0 R
-/Prev 1463 0 R
-/Next 1471 0 R
->> endobj
-1463 0 obj <<
-/Title 1464 0 R
-/A 1461 0 R
-/Parent 1459 0 R
-/Next 1467 0 R
->> endobj
-1459 0 obj <<
-/Title 1460 0 R
-/A 1457 0 R
-/Parent 1451 0 R
-/Prev 1455 0 R
-/Next 1479 0 R
-/First 1463 0 R
-/Last 1475 0 R
-/Count -4
->> endobj
-1455 0 obj <<
-/Title 1456 0 R
-/A 1453 0 R
-/Parent 1451 0 R
-/Next 1459 0 R
->> endobj
-1451 0 obj <<
-/Title 1452 0 R
-/A 1449 0 R
-/Parent 1299 0 R
-/Prev 1411 0 R
-/Next 1523 0 R
-/First 1455 0 R
-/Last 1519 0 R
-/Count -6
->> endobj
-1447 0 obj <<
-/Title 1448 0 R
-/A 1445 0 R
-/Parent 1439 0 R
-/Prev 1443 0 R
->> endobj
-1443 0 obj <<
-/Title 1444 0 R
-/A 1441 0 R
-/Parent 1439 0 R
-/Next 1447 0 R
->> endobj
-1439 0 obj <<
-/Title 1440 0 R
-/A 1437 0 R
-/Parent 1411 0 R
-/Prev 1431 0 R
-/First 1443 0 R
-/Last 1447 0 R
-/Count -2
->> endobj
-1435 0 obj <<
-/Title 1436 0 R
-/A 1433 0 R
-/Parent 1431 0 R
->> endobj
-1431 0 obj <<
-/Title 1432 0 R
-/A 1429 0 R
-/Parent 1411 0 R
-/Prev 1427 0 R
-/Next 1439 0 R
-/First 1435 0 R
-/Last 1435 0 R
-/Count -1
->> endobj
-1427 0 obj <<
-/Title 1428 0 R
-/A 1425 0 R
-/Parent 1411 0 R
-/Prev 1423 0 R
-/Next 1431 0 R
->> endobj
-1423 0 obj <<
-/Title 1424 0 R
-/A 1421 0 R
-/Parent 1411 0 R
-/Prev 1419 0 R
-/Next 1427 0 R
->> endobj
-1419 0 obj <<
-/Title 1420 0 R
-/A 1417 0 R
-/Parent 1411 0 R
-/Prev 1415 0 R
-/Next 1423 0 R
->> endobj
-1415 0 obj <<
-/Title 1416 0 R
-/A 1413 0 R
-/Parent 1411 0 R
-/Next 1419 0 R
->> endobj
-1411 0 obj <<
-/Title 1412 0 R
-/A 1409 0 R
-/Parent 1299 0 R
-/Prev 1363 0 R
-/Next 1451 0 R
-/First 1415 0 R
-/Last 1439 0 R
-/Count -6
->> endobj
-1407 0 obj <<
-/Title 1408 0 R
-/A 1405 0 R
-/Parent 1399 0 R
-/Prev 1403 0 R
->> endobj
-1403 0 obj <<
-/Title 1404 0 R
-/A 1401 0 R
-/Parent 1399 0 R
-/Next 1407 0 R
->> endobj
-1399 0 obj <<
-/Title 1400 0 R
-/A 1397 0 R
-/Parent 1363 0 R
-/Prev 1367 0 R
-/First 1403 0 R
-/Last 1407 0 R
-/Count -2
->> endobj
-1395 0 obj <<
-/Title 1396 0 R
-/A 1393 0 R
-/Parent 1367 0 R
-/Prev 1371 0 R
->> endobj
-1391 0 obj <<
-/Title 1392 0 R
-/A 1389 0 R
-/Parent 1371 0 R
-/Prev 1387 0 R
->> endobj
-1387 0 obj <<
-/Title 1388 0 R
-/A 1385 0 R
-/Parent 1371 0 R
-/Prev 1383 0 R
-/Next 1391 0 R
->> endobj
-1383 0 obj <<
-/Title 1384 0 R
-/A 1381 0 R
-/Parent 1371 0 R
-/Prev 1379 0 R
-/Next 1387 0 R
->> endobj
-1379 0 obj <<
-/Title 1380 0 R
-/A 1377 0 R
-/Parent 1371 0 R
-/Prev 1375 0 R
-/Next 1383 0 R
->> endobj
-1375 0 obj <<
-/Title 1376 0 R
-/A 1373 0 R
-/Parent 1371 0 R
-/Next 1379 0 R
->> endobj
-1371 0 obj <<
-/Title 1372 0 R
-/A 1369 0 R
-/Parent 1367 0 R
-/Next 1395 0 R
-/First 1375 0 R
-/Last 1391 0 R
-/Count -5
->> endobj
-1367 0 obj <<
-/Title 1368 0 R
-/A 1365 0 R
-/Parent 1363 0 R
-/Next 1399 0 R
-/First 1371 0 R
-/Last 1395 0 R
-/Count -2
->> endobj
-1363 0 obj <<
-/Title 1364 0 R
-/A 1361 0 R
-/Parent 1299 0 R
-/Prev 1303 0 R
-/Next 1411 0 R
-/First 1367 0 R
-/Last 1399 0 R
-/Count -2
->> endobj
-1359 0 obj <<
-/Title 1360 0 R
-/A 1357 0 R
-/Parent 1351 0 R
-/Prev 1355 0 R
->> endobj
-1355 0 obj <<
-/Title 1356 0 R
-/A 1353 0 R
-/Parent 1351 0 R
-/Next 1359 0 R
->> endobj
-1351 0 obj <<
-/Title 1352 0 R
-/A 1349 0 R
-/Parent 1303 0 R
-/Prev 1335 0 R
-/First 1355 0 R
-/Last 1359 0 R
-/Count -2
->> endobj
-1347 0 obj <<
-/Title 1348 0 R
-/A 1345 0 R
-/Parent 1339 0 R
-/Prev 1343 0 R
->> endobj
-1343 0 obj <<
-/Title 1344 0 R
-/A 1341 0 R
-/Parent 1339 0 R
-/Next 1347 0 R
->> endobj
-1339 0 obj <<
-/Title 1340 0 R
-/A 1337 0 R
-/Parent 1335 0 R
-/First 1343 0 R
-/Last 1347 0 R
-/Count -2
->> endobj
-1335 0 obj <<
-/Title 1336 0 R
-/A 1333 0 R
-/Parent 1303 0 R
-/Prev 1331 0 R
-/Next 1351 0 R
-/First 1339 0 R
-/Last 1339 0 R
-/Count -1
->> endobj
-1331 0 obj <<
-/Title 1332 0 R
-/A 1329 0 R
-/Parent 1303 0 R
-/Prev 1327 0 R
-/Next 1335 0 R
->> endobj
-1327 0 obj <<
-/Title 1328 0 R
-/A 1325 0 R
-/Parent 1303 0 R
-/Prev 1307 0 R
-/Next 1331 0 R
->> endobj
-1323 0 obj <<
-/Title 1324 0 R
-/A 1321 0 R
-/Parent 1315 0 R
-/Prev 1319 0 R
->> endobj
-1319 0 obj <<
-/Title 1320 0 R
-/A 1317 0 R
-/Parent 1315 0 R
-/Next 1323 0 R
->> endobj
-1315 0 obj <<
-/Title 1316 0 R
-/A 1313 0 R
-/Parent 1307 0 R
-/Prev 1311 0 R
-/First 1319 0 R
-/Last 1323 0 R
-/Count -2
->> endobj
-1311 0 obj <<
-/Title 1312 0 R
-/A 1309 0 R
-/Parent 1307 0 R
-/Next 1315 0 R
->> endobj
-1307 0 obj <<
-/Title 1308 0 R
-/A 1305 0 R
-/Parent 1303 0 R
-/Next 1327 0 R
-/First 1311 0 R
-/Last 1315 0 R
-/Count -2
->> endobj
-1303 0 obj <<
-/Title 1304 0 R
-/A 1301 0 R
-/Parent 1299 0 R
-/Next 1363 0 R
-/First 1307 0 R
-/Last 1351 0 R
-/Count -5
->> endobj
-1299 0 obj <<
-/Title 1300 0 R
-/A 1297 0 R
-/Parent 3770 0 R
-/Prev 1223 0 R
-/First 1303 0 R
-/Last 1571 0 R
-/Count -6
->> endobj
-1295 0 obj <<
-/Title 1296 0 R
-/A 1293 0 R
-/Parent 1271 0 R
-/Prev 1291 0 R
->> endobj
-1291 0 obj <<
-/Title 1292 0 R
-/A 1289 0 R
-/Parent 1271 0 R
-/Prev 1287 0 R
-/Next 1295 0 R
->> endobj
-1287 0 obj <<
-/Title 1288 0 R
-/A 1285 0 R
-/Parent 1271 0 R
-/Prev 1283 0 R
-/Next 1291 0 R
->> endobj
-1283 0 obj <<
-/Title 1284 0 R
-/A 1281 0 R
-/Parent 1271 0 R
-/Prev 1279 0 R
-/Next 1287 0 R
->> endobj
-1279 0 obj <<
-/Title 1280 0 R
-/A 1277 0 R
-/Parent 1271 0 R
-/Prev 1275 0 R
-/Next 1283 0 R
->> endobj
-1275 0 obj <<
-/Title 1276 0 R
-/A 1273 0 R
-/Parent 1271 0 R
-/Next 1279 0 R
->> endobj
-1271 0 obj <<
-/Title 1272 0 R
-/A 1269 0 R
-/Parent 1223 0 R
-/Prev 1247 0 R
-/First 1275 0 R
-/Last 1295 0 R
-/Count -6
->> endobj
-1267 0 obj <<
-/Title 1268 0 R
-/A 1265 0 R
-/Parent 1247 0 R
-/Prev 1263 0 R
->> endobj
-1263 0 obj <<
-/Title 1264 0 R
-/A 1261 0 R
-/Parent 1247 0 R
-/Prev 1259 0 R
-/Next 1267 0 R
->> endobj
-1259 0 obj <<
-/Title 1260 0 R
-/A 1257 0 R
-/Parent 1247 0 R
-/Prev 1255 0 R
-/Next 1263 0 R
->> endobj
-1255 0 obj <<
-/Title 1256 0 R
-/A 1253 0 R
-/Parent 1247 0 R
-/Prev 1251 0 R
-/Next 1259 0 R
->> endobj
-1251 0 obj <<
-/Title 1252 0 R
-/A 1249 0 R
-/Parent 1247 0 R
-/Next 1255 0 R
->> endobj
-1247 0 obj <<
-/Title 1248 0 R
-/A 1245 0 R
-/Parent 1223 0 R
-/Prev 1227 0 R
-/Next 1271 0 R
-/First 1251 0 R
-/Last 1267 0 R
-/Count -5
->> endobj
-1243 0 obj <<
-/Title 1244 0 R
-/A 1241 0 R
-/Parent 1227 0 R
-/Prev 1239 0 R
->> endobj
-1239 0 obj <<
-/Title 1240 0 R
-/A 1237 0 R
-/Parent 1227 0 R
-/Prev 1235 0 R
-/Next 1243 0 R
->> endobj
-1235 0 obj <<
-/Title 1236 0 R
-/A 1233 0 R
-/Parent 1227 0 R
-/Prev 1231 0 R
-/Next 1239 0 R
->> endobj
-1231 0 obj <<
-/Title 1232 0 R
-/A 1229 0 R
-/Parent 1227 0 R
-/Next 1235 0 R
->> endobj
-1227 0 obj <<
-/Title 1228 0 R
-/A 1225 0 R
-/Parent 1223 0 R
-/Next 1247 0 R
-/First 1231 0 R
-/Last 1243 0 R
-/Count -4
->> endobj
-1223 0 obj <<
-/Title 1224 0 R
-/A 1221 0 R
-/Parent 3770 0 R
-/Prev 295 0 R
-/Next 1299 0 R
-/First 1227 0 R
-/Last 1271 0 R
-/Count -3
->> endobj
-1219 0 obj <<
-/Title 1220 0 R
-/A 1217 0 R
-/Parent 1191 0 R
-/Prev 1215 0 R
->> endobj
-1215 0 obj <<
-/Title 1216 0 R
-/A 1213 0 R
-/Parent 1191 0 R
-/Prev 1203 0 R
-/Next 1219 0 R
->> endobj
-1211 0 obj <<
-/Title 1212 0 R
-/A 1209 0 R
-/Parent 1203 0 R
-/Prev 1207 0 R
->> endobj
-1207 0 obj <<
-/Title 1208 0 R
-/A 1205 0 R
-/Parent 1203 0 R
-/Next 1211 0 R
->> endobj
-1203 0 obj <<
-/Title 1204 0 R
-/A 1201 0 R
-/Parent 1191 0 R
-/Prev 1199 0 R
-/Next 1215 0 R
-/First 1207 0 R
-/Last 1211 0 R
-/Count -2
->> endobj
-1199 0 obj <<
-/Title 1200 0 R
-/A 1197 0 R
-/Parent 1191 0 R
-/Prev 1195 0 R
-/Next 1203 0 R
->> endobj
-1195 0 obj <<
-/Title 1196 0 R
-/A 1193 0 R
-/Parent 1191 0 R
-/Next 1199 0 R
->> endobj
-1191 0 obj <<
-/Title 1192 0 R
-/A 1189 0 R
-/Parent 295 0 R
-/Prev 1171 0 R
-/First 1195 0 R
-/Last 1219 0 R
-/Count -5
->> endobj
-1187 0 obj <<
-/Title 1188 0 R
-/A 1185 0 R
-/Parent 1171 0 R
-/Prev 1183 0 R
->> endobj
-1183 0 obj <<
-/Title 1184 0 R
-/A 1181 0 R
-/Parent 1171 0 R
-/Prev 1179 0 R
-/Next 1187 0 R
->> endobj
-1179 0 obj <<
-/Title 1180 0 R
-/A 1177 0 R
-/Parent 1171 0 R
-/Prev 1175 0 R
-/Next 1183 0 R
->> endobj
-1175 0 obj <<
-/Title 1176 0 R
-/A 1173 0 R
-/Parent 1171 0 R
-/Next 1179 0 R
->> endobj
-1171 0 obj <<
-/Title 1172 0 R
-/A 1169 0 R
-/Parent 295 0 R
-/Prev 1139 0 R
-/Next 1191 0 R
-/First 1175 0 R
-/Last 1187 0 R
-/Count -4
->> endobj
-1167 0 obj <<
-/Title 1168 0 R
-/A 1165 0 R
-/Parent 1139 0 R
-/Prev 1163 0 R
->> endobj
-1163 0 obj <<
-/Title 1164 0 R
-/A 1161 0 R
-/Parent 1139 0 R
-/Prev 1159 0 R
-/Next 1167 0 R
->> endobj
-1159 0 obj <<
-/Title 1160 0 R
-/A 1157 0 R
-/Parent 1139 0 R
-/Prev 1155 0 R
-/Next 1163 0 R
->> endobj
-1155 0 obj <<
-/Title 1156 0 R
-/A 1153 0 R
-/Parent 1139 0 R
-/Prev 1151 0 R
-/Next 1159 0 R
->> endobj
-1151 0 obj <<
-/Title 1152 0 R
-/A 1149 0 R
-/Parent 1139 0 R
-/Prev 1147 0 R
-/Next 1155 0 R
->> endobj
-1147 0 obj <<
-/Title 1148 0 R
-/A 1145 0 R
-/Parent 1139 0 R
-/Prev 1143 0 R
-/Next 1151 0 R
->> endobj
-1143 0 obj <<
-/Title 1144 0 R
-/A 1141 0 R
-/Parent 1139 0 R
-/Next 1147 0 R
->> endobj
-1139 0 obj <<
-/Title 1140 0 R
-/A 1137 0 R
-/Parent 295 0 R
-/Prev 1091 0 R
-/Next 1171 0 R
-/First 1143 0 R
-/Last 1167 0 R
-/Count -7
->> endobj
-1135 0 obj <<
-/Title 1136 0 R
-/A 1133 0 R
-/Parent 1115 0 R
-/Prev 1131 0 R
->> endobj
-1131 0 obj <<
-/Title 1132 0 R
-/A 1129 0 R
-/Parent 1115 0 R
-/Prev 1127 0 R
-/Next 1135 0 R
->> endobj
-1127 0 obj <<
-/Title 1128 0 R
-/A 1125 0 R
-/Parent 1115 0 R
-/Prev 1123 0 R
-/Next 1131 0 R
->> endobj
-1123 0 obj <<
-/Title 1124 0 R
-/A 1121 0 R
-/Parent 1115 0 R
-/Prev 1119 0 R
-/Next 1127 0 R
->> endobj
-1119 0 obj <<
-/Title 1120 0 R
-/A 1117 0 R
-/Parent 1115 0 R
-/Next 1123 0 R
->> endobj
-1115 0 obj <<
-/Title 1116 0 R
-/A 1113 0 R
-/Parent 1091 0 R
-/Prev 1095 0 R
-/First 1119 0 R
-/Last 1135 0 R
-/Count -5
->> endobj
-1111 0 obj <<
-/Title 1112 0 R
-/A 1109 0 R
-/Parent 1095 0 R
-/Prev 1107 0 R
->> endobj
-1107 0 obj <<
-/Title 1108 0 R
-/A 1105 0 R
-/Parent 1095 0 R
-/Prev 1103 0 R
-/Next 1111 0 R
->> endobj
-1103 0 obj <<
-/Title 1104 0 R
-/A 1101 0 R
-/Parent 1095 0 R
-/Prev 1099 0 R
-/Next 1107 0 R
->> endobj
-1099 0 obj <<
-/Title 1100 0 R
-/A 1097 0 R
-/Parent 1095 0 R
-/Next 1103 0 R
->> endobj
-1095 0 obj <<
-/Title 1096 0 R
-/A 1093 0 R
-/Parent 1091 0 R
-/Next 1115 0 R
-/First 1099 0 R
-/Last 1111 0 R
-/Count -4
->> endobj
-1091 0 obj <<
-/Title 1092 0 R
-/A 1089 0 R
-/Parent 295 0 R
-/Prev 1079 0 R
-/Next 1139 0 R
-/First 1095 0 R
-/Last 1115 0 R
-/Count -2
->> endobj
-1087 0 obj <<
-/Title 1088 0 R
-/A 1085 0 R
-/Parent 1083 0 R
->> endobj
-1083 0 obj <<
-/Title 1084 0 R
-/A 1081 0 R
-/Parent 1079 0 R
-/First 1087 0 R
-/Last 1087 0 R
-/Count -1
->> endobj
-1079 0 obj <<
-/Title 1080 0 R
-/A 1077 0 R
-/Parent 295 0 R
-/Prev 1039 0 R
-/Next 1091 0 R
-/First 1083 0 R
-/Last 1083 0 R
-/Count -1
->> endobj
-1075 0 obj <<
-/Title 1076 0 R
-/A 1073 0 R
-/Parent 1067 0 R
-/Prev 1071 0 R
->> endobj
-1071 0 obj <<
-/Title 1072 0 R
-/A 1069 0 R
-/Parent 1067 0 R
-/Next 1075 0 R
->> endobj
-1067 0 obj <<
-/Title 1068 0 R
-/A 1065 0 R
-/Parent 1039 0 R
-/Prev 1047 0 R
-/First 1071 0 R
-/Last 1075 0 R
-/Count -2
->> endobj
-1063 0 obj <<
-/Title 1064 0 R
-/A 1061 0 R
-/Parent 1047 0 R
-/Prev 1059 0 R
->> endobj
-1059 0 obj <<
-/Title 1060 0 R
-/A 1057 0 R
-/Parent 1047 0 R
-/Prev 1055 0 R
-/Next 1063 0 R
->> endobj
-1055 0 obj <<
-/Title 1056 0 R
-/A 1053 0 R
-/Parent 1047 0 R
-/Prev 1051 0 R
-/Next 1059 0 R
->> endobj
-1051 0 obj <<
-/Title 1052 0 R
-/A 1049 0 R
-/Parent 1047 0 R
-/Next 1055 0 R
->> endobj
-1047 0 obj <<
-/Title 1048 0 R
-/A 1045 0 R
-/Parent 1039 0 R
-/Prev 1043 0 R
-/Next 1067 0 R
-/First 1051 0 R
-/Last 1063 0 R
-/Count -4
->> endobj
-1043 0 obj <<
-/Title 1044 0 R
-/A 1041 0 R
-/Parent 1039 0 R
-/Next 1047 0 R
->> endobj
-1039 0 obj <<
-/Title 1040 0 R
-/A 1037 0 R
-/Parent 295 0 R
-/Prev 1003 0 R
-/Next 1079 0 R
-/First 1043 0 R
-/Last 1067 0 R
-/Count -3
->> endobj
-1035 0 obj <<
-/Title 1036 0 R
-/A 1033 0 R
-/Parent 1003 0 R
-/Prev 1007 0 R
->> endobj
-1031 0 obj <<
-/Title 1032 0 R
-/A 1029 0 R
-/Parent 1015 0 R
-/Prev 1027 0 R
->> endobj
-1027 0 obj <<
-/Title 1028 0 R
-/A 1025 0 R
-/Parent 1015 0 R
-/Prev 1023 0 R
-/Next 1031 0 R
->> endobj
-1023 0 obj <<
-/Title 1024 0 R
-/A 1021 0 R
-/Parent 1015 0 R
-/Prev 1019 0 R
-/Next 1027 0 R
->> endobj
-1019 0 obj <<
-/Title 1020 0 R
-/A 1017 0 R
-/Parent 1015 0 R
-/Next 1023 0 R
->> endobj
-1015 0 obj <<
-/Title 1016 0 R
-/A 1013 0 R
-/Parent 1007 0 R
-/Prev 1011 0 R
-/First 1019 0 R
-/Last 1031 0 R
-/Count -4
->> endobj
-1011 0 obj <<
-/Title 1012 0 R
-/A 1009 0 R
-/Parent 1007 0 R
-/Next 1015 0 R
->> endobj
-1007 0 obj <<
-/Title 1008 0 R
-/A 1005 0 R
-/Parent 1003 0 R
-/Next 1035 0 R
-/First 1011 0 R
-/Last 1015 0 R
-/Count -2
->> endobj
-1003 0 obj <<
-/Title 1004 0 R
-/A 1001 0 R
-/Parent 295 0 R
-/Prev 971 0 R
-/Next 1039 0 R
-/First 1007 0 R
-/Last 1035 0 R
-/Count -2
->> endobj
-999 0 obj <<
-/Title 1000 0 R
-/A 997 0 R
-/Parent 991 0 R
-/Prev 995 0 R
->> endobj
-995 0 obj <<
-/Title 996 0 R
-/A 993 0 R
-/Parent 991 0 R
-/Next 999 0 R
->> endobj
-991 0 obj <<
-/Title 992 0 R
-/A 989 0 R
-/Parent 971 0 R
-/Prev 979 0 R
-/First 995 0 R
-/Last 999 0 R
-/Count -2
->> endobj
-987 0 obj <<
-/Title 988 0 R
-/A 985 0 R
-/Parent 979 0 R
-/Prev 983 0 R
->> endobj
-983 0 obj <<
-/Title 984 0 R
-/A 981 0 R
-/Parent 979 0 R
-/Next 987 0 R
->> endobj
-979 0 obj <<
-/Title 980 0 R
-/A 977 0 R
-/Parent 971 0 R
-/Prev 975 0 R
-/Next 991 0 R
-/First 983 0 R
-/Last 987 0 R
-/Count -2
->> endobj
-975 0 obj <<
-/Title 976 0 R
-/A 973 0 R
-/Parent 971 0 R
-/Next 979 0 R
->> endobj
-971 0 obj <<
-/Title 972 0 R
-/A 969 0 R
-/Parent 295 0 R
-/Prev 875 0 R
-/Next 1003 0 R
-/First 975 0 R
-/Last 991 0 R
-/Count -3
->> endobj
-967 0 obj <<
-/Title 968 0 R
-/A 965 0 R
-/Parent 951 0 R
-/Prev 963 0 R
->> endobj
-963 0 obj <<
-/Title 964 0 R
-/A 961 0 R
-/Parent 951 0 R
-/Prev 955 0 R
-/Next 967 0 R
->> endobj
-959 0 obj <<
-/Title 960 0 R
-/A 957 0 R
-/Parent 955 0 R
->> endobj
-955 0 obj <<
-/Title 956 0 R
-/A 953 0 R
-/Parent 951 0 R
-/Next 963 0 R
-/First 959 0 R
-/Last 959 0 R
-/Count -1
->> endobj
-951 0 obj <<
-/Title 952 0 R
-/A 949 0 R
-/Parent 875 0 R
-/Prev 947 0 R
-/First 955 0 R
-/Last 967 0 R
-/Count -3
->> endobj
-947 0 obj <<
-/Title 948 0 R
-/A 945 0 R
-/Parent 875 0 R
-/Prev 943 0 R
-/Next 951 0 R
->> endobj
-943 0 obj <<
-/Title 944 0 R
-/A 941 0 R
-/Parent 875 0 R
-/Prev 879 0 R
-/Next 947 0 R
->> endobj
-939 0 obj <<
-/Title 940 0 R
-/A 937 0 R
-/Parent 923 0 R
-/Prev 935 0 R
->> endobj
-935 0 obj <<
-/Title 936 0 R
-/A 933 0 R
-/Parent 923 0 R
-/Prev 931 0 R
-/Next 939 0 R
->> endobj
-931 0 obj <<
-/Title 932 0 R
-/A 929 0 R
-/Parent 923 0 R
-/Prev 927 0 R
-/Next 935 0 R
->> endobj
-927 0 obj <<
-/Title 928 0 R
-/A 925 0 R
-/Parent 923 0 R
-/Next 931 0 R
->> endobj
-923 0 obj <<
-/Title 924 0 R
-/A 921 0 R
-/Parent 879 0 R
-/Prev 919 0 R
-/First 927 0 R
-/Last 939 0 R
-/Count -4
->> endobj
-919 0 obj <<
-/Title 920 0 R
-/A 917 0 R
-/Parent 879 0 R
-/Prev 903 0 R
-/Next 923 0 R
->> endobj
-915 0 obj <<
-/Title 916 0 R
-/A 913 0 R
-/Parent 903 0 R
-/Prev 911 0 R
->> endobj
-911 0 obj <<
-/Title 912 0 R
-/A 909 0 R
-/Parent 903 0 R
-/Prev 907 0 R
-/Next 915 0 R
->> endobj
-907 0 obj <<
-/Title 908 0 R
-/A 905 0 R
-/Parent 903 0 R
-/Next 911 0 R
->> endobj
-903 0 obj <<
-/Title 904 0 R
-/A 901 0 R
-/Parent 879 0 R
-/Prev 883 0 R
-/Next 919 0 R
-/First 907 0 R
-/Last 915 0 R
-/Count -3
->> endobj
-899 0 obj <<
-/Title 900 0 R
-/A 897 0 R
-/Parent 883 0 R
-/Prev 895 0 R
->> endobj
-895 0 obj <<
-/Title 896 0 R
-/A 893 0 R
-/Parent 883 0 R
-/Prev 891 0 R
-/Next 899 0 R
->> endobj
-891 0 obj <<
-/Title 892 0 R
-/A 889 0 R
-/Parent 883 0 R
-/Prev 887 0 R
-/Next 895 0 R
->> endobj
-887 0 obj <<
-/Title 888 0 R
-/A 885 0 R
-/Parent 883 0 R
-/Next 891 0 R
->> endobj
-883 0 obj <<
-/Title 884 0 R
-/A 881 0 R
-/Parent 879 0 R
-/Next 903 0 R
-/First 887 0 R
-/Last 899 0 R
-/Count -4
->> endobj
-879 0 obj <<
-/Title 880 0 R
-/A 877 0 R
-/Parent 875 0 R
-/Next 943 0 R
-/First 883 0 R
-/Last 923 0 R
-/Count -4
->> endobj
-875 0 obj <<
-/Title 876 0 R
-/A 873 0 R
-/Parent 295 0 R
-/Prev 831 0 R
-/Next 971 0 R
-/First 879 0 R
-/Last 951 0 R
-/Count -4
->> endobj
-871 0 obj <<
-/Title 872 0 R
-/A 869 0 R
-/Parent 831 0 R
-/Prev 859 0 R
->> endobj
-867 0 obj <<
-/Title 868 0 R
-/A 865 0 R
-/Parent 859 0 R
-/Prev 863 0 R
->> endobj
-863 0 obj <<
-/Title 864 0 R
-/A 861 0 R
-/Parent 859 0 R
-/Next 867 0 R
->> endobj
-859 0 obj <<
-/Title 860 0 R
-/A 857 0 R
-/Parent 831 0 R
-/Prev 835 0 R
-/Next 871 0 R
-/First 863 0 R
-/Last 867 0 R
-/Count -2
->> endobj
-855 0 obj <<
-/Title 856 0 R
-/A 853 0 R
-/Parent 851 0 R
->> endobj
-851 0 obj <<
-/Title 852 0 R
-/A 849 0 R
-/Parent 835 0 R
-/Prev 843 0 R
-/First 855 0 R
-/Last 855 0 R
-/Count -1
->> endobj
-847 0 obj <<
-/Title 848 0 R
-/A 845 0 R
-/Parent 843 0 R
->> endobj
-843 0 obj <<
-/Title 844 0 R
-/A 841 0 R
-/Parent 835 0 R
-/Prev 839 0 R
-/Next 851 0 R
-/First 847 0 R
-/Last 847 0 R
-/Count -1
->> endobj
-839 0 obj <<
-/Title 840 0 R
-/A 837 0 R
-/Parent 835 0 R
-/Next 843 0 R
->> endobj
-835 0 obj <<
-/Title 836 0 R
-/A 833 0 R
-/Parent 831 0 R
-/Next 859 0 R
-/First 839 0 R
-/Last 851 0 R
-/Count -3
->> endobj
-831 0 obj <<
-/Title 832 0 R
-/A 829 0 R
-/Parent 295 0 R
-/Prev 799 0 R
-/Next 875 0 R
-/First 835 0 R
-/Last 871 0 R
-/Count -3
->> endobj
-827 0 obj <<
-/Title 828 0 R
-/A 825 0 R
-/Parent 823 0 R
->> endobj
-823 0 obj <<
-/Title 824 0 R
-/A 821 0 R
-/Parent 799 0 R
-/Prev 819 0 R
-/First 827 0 R
-/Last 827 0 R
-/Count -1
->> endobj
-819 0 obj <<
-/Title 820 0 R
-/A 817 0 R
-/Parent 799 0 R
-/Prev 803 0 R
-/Next 823 0 R
->> endobj
-815 0 obj <<
-/Title 816 0 R
-/A 813 0 R
-/Parent 807 0 R
-/Prev 811 0 R
->> endobj
-811 0 obj <<
-/Title 812 0 R
-/A 809 0 R
-/Parent 807 0 R
-/Next 815 0 R
->> endobj
-807 0 obj <<
-/Title 808 0 R
-/A 805 0 R
-/Parent 803 0 R
-/First 811 0 R
-/Last 815 0 R
-/Count -2
->> endobj
-803 0 obj <<
-/Title 804 0 R
-/A 801 0 R
-/Parent 799 0 R
-/Next 819 0 R
-/First 807 0 R
-/Last 807 0 R
-/Count -1
->> endobj
-799 0 obj <<
-/Title 800 0 R
-/A 797 0 R
-/Parent 295 0 R
-/Prev 695 0 R
-/Next 831 0 R
-/First 803 0 R
-/Last 823 0 R
-/Count -3
->> endobj
-795 0 obj <<
-/Title 796 0 R
-/A 793 0 R
-/Parent 695 0 R
-/Prev 791 0 R
->> endobj
-791 0 obj <<
-/Title 792 0 R
-/A 789 0 R
-/Parent 695 0 R
-/Prev 743 0 R
-/Next 795 0 R
->> endobj
-787 0 obj <<
-/Title 788 0 R
-/A 785 0 R
-/Parent 755 0 R
-/Prev 783 0 R
->> endobj
-783 0 obj <<
-/Title 784 0 R
-/A 781 0 R
-/Parent 755 0 R
-/Prev 779 0 R
-/Next 787 0 R
->> endobj
-779 0 obj <<
-/Title 780 0 R
-/A 777 0 R
-/Parent 755 0 R
-/Prev 775 0 R
-/Next 783 0 R
->> endobj
-775 0 obj <<
-/Title 776 0 R
-/A 773 0 R
-/Parent 755 0 R
-/Prev 771 0 R
-/Next 779 0 R
->> endobj
-771 0 obj <<
-/Title 772 0 R
-/A 769 0 R
-/Parent 755 0 R
-/Prev 767 0 R
-/Next 775 0 R
->> endobj
-767 0 obj <<
-/Title 768 0 R
-/A 765 0 R
-/Parent 755 0 R
-/Prev 763 0 R
-/Next 771 0 R
->> endobj
-763 0 obj <<
-/Title 764 0 R
-/A 761 0 R
-/Parent 755 0 R
-/Prev 759 0 R
-/Next 767 0 R
->> endobj
-759 0 obj <<
-/Title 760 0 R
-/A 757 0 R
-/Parent 755 0 R
-/Next 763 0 R
->> endobj
-755 0 obj <<
-/Title 756 0 R
-/A 753 0 R
-/Parent 743 0 R
-/Prev 751 0 R
-/First 759 0 R
-/Last 787 0 R
-/Count -8
->> endobj
-751 0 obj <<
-/Title 752 0 R
-/A 749 0 R
-/Parent 743 0 R
-/Prev 747 0 R
-/Next 755 0 R
->> endobj
-747 0 obj <<
-/Title 748 0 R
-/A 745 0 R
-/Parent 743 0 R
-/Next 751 0 R
->> endobj
-743 0 obj <<
-/Title 744 0 R
-/A 741 0 R
-/Parent 695 0 R
-/Prev 715 0 R
-/Next 791 0 R
-/First 747 0 R
-/Last 755 0 R
-/Count -3
->> endobj
-739 0 obj <<
-/Title 740 0 R
-/A 737 0 R
-/Parent 715 0 R
-/Prev 735 0 R
->> endobj
-735 0 obj <<
-/Title 736 0 R
-/A 733 0 R
-/Parent 715 0 R
-/Prev 731 0 R
-/Next 739 0 R
->> endobj
-731 0 obj <<
-/Title 732 0 R
-/A 729 0 R
-/Parent 715 0 R
-/Prev 727 0 R
-/Next 735 0 R
->> endobj
-727 0 obj <<
-/Title 728 0 R
-/A 725 0 R
-/Parent 715 0 R
-/Prev 723 0 R
-/Next 731 0 R
->> endobj
-723 0 obj <<
-/Title 724 0 R
-/A 721 0 R
-/Parent 715 0 R
-/Prev 719 0 R
-/Next 727 0 R
->> endobj
-719 0 obj <<
-/Title 720 0 R
-/A 717 0 R
-/Parent 715 0 R
-/Next 723 0 R
->> endobj
-715 0 obj <<
-/Title 716 0 R
-/A 713 0 R
-/Parent 695 0 R
-/Prev 707 0 R
-/Next 743 0 R
-/First 719 0 R
-/Last 739 0 R
-/Count -6
->> endobj
-711 0 obj <<
-/Title 712 0 R
-/A 709 0 R
-/Parent 707 0 R
->> endobj
-707 0 obj <<
-/Title 708 0 R
-/A 705 0 R
-/Parent 695 0 R
-/Prev 703 0 R
-/Next 715 0 R
-/First 711 0 R
-/Last 711 0 R
-/Count -1
->> endobj
-703 0 obj <<
-/Title 704 0 R
-/A 701 0 R
-/Parent 695 0 R
-/Prev 699 0 R
-/Next 707 0 R
->> endobj
-699 0 obj <<
-/Title 700 0 R
-/A 697 0 R
-/Parent 695 0 R
-/Next 703 0 R
->> endobj
-695 0 obj <<
-/Title 696 0 R
-/A 693 0 R
-/Parent 295 0 R
-/Prev 635 0 R
-/Next 799 0 R
-/First 699 0 R
-/Last 795 0 R
-/Count -7
->> endobj
-691 0 obj <<
-/Title 692 0 R
-/A 689 0 R
-/Parent 635 0 R
-/Prev 687 0 R
->> endobj
-687 0 obj <<
-/Title 688 0 R
-/A 685 0 R
-/Parent 635 0 R
-/Prev 683 0 R
-/Next 691 0 R
->> endobj
-683 0 obj <<
-/Title 684 0 R
-/A 681 0 R
-/Parent 635 0 R
-/Prev 675 0 R
-/Next 687 0 R
->> endobj
-679 0 obj <<
-/Title 680 0 R
-/A 677 0 R
-/Parent 675 0 R
->> endobj
-675 0 obj <<
-/Title 676 0 R
-/A 673 0 R
-/Parent 635 0 R
-/Prev 671 0 R
-/Next 683 0 R
-/First 679 0 R
-/Last 679 0 R
-/Count -1
->> endobj
-671 0 obj <<
-/Title 672 0 R
-/A 669 0 R
-/Parent 635 0 R
-/Prev 663 0 R
-/Next 675 0 R
->> endobj
-667 0 obj <<
-/Title 668 0 R
-/A 665 0 R
-/Parent 663 0 R
->> endobj
-663 0 obj <<
-/Title 664 0 R
-/A 661 0 R
-/Parent 635 0 R
-/Prev 659 0 R
-/Next 671 0 R
-/First 667 0 R
-/Last 667 0 R
-/Count -1
->> endobj
-659 0 obj <<
-/Title 660 0 R
-/A 657 0 R
-/Parent 635 0 R
-/Prev 655 0 R
-/Next 663 0 R
->> endobj
-655 0 obj <<
-/Title 656 0 R
-/A 653 0 R
-/Parent 635 0 R
-/Prev 651 0 R
-/Next 659 0 R
->> endobj
-651 0 obj <<
-/Title 652 0 R
-/A 649 0 R
-/Parent 635 0 R
-/Prev 647 0 R
-/Next 655 0 R
->> endobj
-647 0 obj <<
-/Title 648 0 R
-/A 645 0 R
-/Parent 635 0 R
-/Prev 643 0 R
-/Next 651 0 R
->> endobj
-643 0 obj <<
-/Title 644 0 R
-/A 641 0 R
-/Parent 635 0 R
-/Prev 639 0 R
-/Next 647 0 R
->> endobj
-639 0 obj <<
-/Title 640 0 R
-/A 637 0 R
-/Parent 635 0 R
-/Next 643 0 R
->> endobj
-635 0 obj <<
-/Title 636 0 R
-/A 633 0 R
-/Parent 295 0 R
-/Prev 543 0 R
-/Next 695 0 R
-/First 639 0 R
-/Last 691 0 R
-/Count -12
->> endobj
-631 0 obj <<
-/Title 632 0 R
-/A 629 0 R
-/Parent 595 0 R
-/Prev 627 0 R
->> endobj
-627 0 obj <<
-/Title 628 0 R
-/A 625 0 R
-/Parent 595 0 R
-/Prev 623 0 R
-/Next 631 0 R
->> endobj
-623 0 obj <<
-/Title 624 0 R
-/A 621 0 R
-/Parent 595 0 R
-/Prev 619 0 R
-/Next 627 0 R
->> endobj
-619 0 obj <<
-/Title 620 0 R
-/A 617 0 R
-/Parent 595 0 R
-/Prev 615 0 R
-/Next 623 0 R
->> endobj
-615 0 obj <<
-/Title 616 0 R
-/A 613 0 R
-/Parent 595 0 R
-/Prev 611 0 R
-/Next 619 0 R
->> endobj
-611 0 obj <<
-/Title 612 0 R
-/A 609 0 R
-/Parent 595 0 R
-/Prev 607 0 R
-/Next 615 0 R
->> endobj
-607 0 obj <<
-/Title 608 0 R
-/A 605 0 R
-/Parent 595 0 R
-/Prev 603 0 R
-/Next 611 0 R
->> endobj
-603 0 obj <<
-/Title 604 0 R
-/A 601 0 R
-/Parent 595 0 R
-/Prev 599 0 R
-/Next 607 0 R
->> endobj
-599 0 obj <<
-/Title 600 0 R
-/A 597 0 R
-/Parent 595 0 R
-/Next 603 0 R
->> endobj
-595 0 obj <<
-/Title 596 0 R
-/A 593 0 R
-/Parent 543 0 R
-/Prev 575 0 R
-/First 599 0 R
-/Last 631 0 R
-/Count -9
->> endobj
-591 0 obj <<
-/Title 592 0 R
-/A 589 0 R
-/Parent 575 0 R
-/Prev 587 0 R
->> endobj
-587 0 obj <<
-/Title 588 0 R
-/A 585 0 R
-/Parent 575 0 R
-/Prev 583 0 R
-/Next 591 0 R
->> endobj
-583 0 obj <<
-/Title 584 0 R
-/A 581 0 R
-/Parent 575 0 R
-/Prev 579 0 R
-/Next 587 0 R
->> endobj
-579 0 obj <<
-/Title 580 0 R
-/A 577 0 R
-/Parent 575 0 R
-/Next 583 0 R
->> endobj
-575 0 obj <<
-/Title 576 0 R
-/A 573 0 R
-/Parent 543 0 R
-/Prev 551 0 R
-/Next 595 0 R
-/First 579 0 R
-/Last 591 0 R
-/Count -4
->> endobj
-571 0 obj <<
-/Title 572 0 R
-/A 569 0 R
-/Parent 551 0 R
-/Prev 567 0 R
->> endobj
-567 0 obj <<
-/Title 568 0 R
-/A 565 0 R
-/Parent 551 0 R
-/Prev 563 0 R
-/Next 571 0 R
->> endobj
-563 0 obj <<
-/Title 564 0 R
-/A 561 0 R
-/Parent 551 0 R
-/Prev 559 0 R
-/Next 567 0 R
->> endobj
-559 0 obj <<
-/Title 560 0 R
-/A 557 0 R
-/Parent 551 0 R
-/Prev 555 0 R
-/Next 563 0 R
->> endobj
-555 0 obj <<
-/Title 556 0 R
-/A 553 0 R
-/Parent 551 0 R
-/Next 559 0 R
->> endobj
-551 0 obj <<
-/Title 552 0 R
-/A 549 0 R
-/Parent 543 0 R
-/Prev 547 0 R
-/Next 575 0 R
-/First 555 0 R
-/Last 571 0 R
-/Count -5
->> endobj
-547 0 obj <<
-/Title 548 0 R
-/A 545 0 R
-/Parent 543 0 R
-/Next 551 0 R
->> endobj
-543 0 obj <<
-/Title 544 0 R
-/A 541 0 R
-/Parent 295 0 R
-/Prev 539 0 R
-/Next 635 0 R
-/First 547 0 R
-/Last 595 0 R
-/Count -4
->> endobj
-539 0 obj <<
-/Title 540 0 R
-/A 537 0 R
-/Parent 295 0 R
-/Prev 499 0 R
-/Next 543 0 R
->> endobj
-535 0 obj <<
-/Title 536 0 R
-/A 533 0 R
-/Parent 499 0 R
-/Prev 531 0 R
->> endobj
-531 0 obj <<
-/Title 532 0 R
-/A 529 0 R
-/Parent 499 0 R
-/Prev 527 0 R
-/Next 535 0 R
->> endobj
-527 0 obj <<
-/Title 528 0 R
-/A 525 0 R
-/Parent 499 0 R
-/Prev 515 0 R
-/Next 531 0 R
->> endobj
-523 0 obj <<
-/Title 524 0 R
-/A 521 0 R
-/Parent 515 0 R
-/Prev 519 0 R
->> endobj
-519 0 obj <<
-/Title 520 0 R
-/A 517 0 R
-/Parent 515 0 R
-/Next 523 0 R
->> endobj
-515 0 obj <<
-/Title 516 0 R
-/A 513 0 R
-/Parent 499 0 R
-/Prev 511 0 R
-/Next 527 0 R
-/First 519 0 R
-/Last 523 0 R
-/Count -2
->> endobj
-511 0 obj <<
-/Title 512 0 R
-/A 509 0 R
-/Parent 499 0 R
-/Prev 507 0 R
-/Next 515 0 R
->> endobj
-507 0 obj <<
-/Title 508 0 R
-/A 505 0 R
-/Parent 499 0 R
-/Prev 503 0 R
-/Next 511 0 R
->> endobj
-503 0 obj <<
-/Title 504 0 R
-/A 501 0 R
-/Parent 499 0 R
-/Next 507 0 R
->> endobj
-499 0 obj <<
-/Title 500 0 R
-/A 497 0 R
-/Parent 295 0 R
-/Prev 395 0 R
-/Next 539 0 R
-/First 503 0 R
-/Last 535 0 R
-/Count -7
->> endobj
-495 0 obj <<
-/Title 496 0 R
-/A 493 0 R
-/Parent 395 0 R
-/Prev 475 0 R
->> endobj
-491 0 obj <<
-/Title 492 0 R
-/A 489 0 R
-/Parent 475 0 R
-/Prev 487 0 R
->> endobj
-487 0 obj <<
-/Title 488 0 R
-/A 485 0 R
-/Parent 475 0 R
-/Prev 483 0 R
-/Next 491 0 R
->> endobj
-483 0 obj <<
-/Title 484 0 R
-/A 481 0 R
-/Parent 475 0 R
-/Prev 479 0 R
-/Next 487 0 R
->> endobj
-479 0 obj <<
-/Title 480 0 R
-/A 477 0 R
-/Parent 475 0 R
-/Next 483 0 R
->> endobj
-475 0 obj <<
-/Title 476 0 R
-/A 473 0 R
-/Parent 395 0 R
-/Prev 427 0 R
-/Next 495 0 R
-/First 479 0 R
-/Last 491 0 R
-/Count -4
->> endobj
-471 0 obj <<
-/Title 472 0 R
-/A 469 0 R
-/Parent 427 0 R
-/Prev 467 0 R
->> endobj
-467 0 obj <<
-/Title 468 0 R
-/A 465 0 R
-/Parent 427 0 R
-/Prev 463 0 R
-/Next 471 0 R
->> endobj
-463 0 obj <<
-/Title 464 0 R
-/A 461 0 R
-/Parent 427 0 R
-/Prev 459 0 R
-/Next 467 0 R
->> endobj
-459 0 obj <<
-/Title 460 0 R
-/A 457 0 R
-/Parent 427 0 R
-/Prev 447 0 R
-/Next 463 0 R
->> endobj
-455 0 obj <<
-/Title 456 0 R
-/A 453 0 R
-/Parent 447 0 R
-/Prev 451 0 R
->> endobj
-451 0 obj <<
-/Title 452 0 R
-/A 449 0 R
-/Parent 447 0 R
-/Next 455 0 R
->> endobj
-447 0 obj <<
-/Title 448 0 R
-/A 445 0 R
-/Parent 427 0 R
-/Prev 443 0 R
-/Next 459 0 R
-/First 451 0 R
-/Last 455 0 R
-/Count -2
->> endobj
-443 0 obj <<
-/Title 444 0 R
-/A 441 0 R
-/Parent 427 0 R
-/Prev 439 0 R
-/Next 447 0 R
->> endobj
-439 0 obj <<
-/Title 440 0 R
-/A 437 0 R
-/Parent 427 0 R
-/Prev 435 0 R
-/Next 443 0 R
->> endobj
-435 0 obj <<
-/Title 436 0 R
-/A 433 0 R
-/Parent 427 0 R
-/Prev 431 0 R
-/Next 439 0 R
->> endobj
-431 0 obj <<
-/Title 432 0 R
-/A 429 0 R
-/Parent 427 0 R
-/Next 435 0 R
->> endobj
-427 0 obj <<
-/Title 428 0 R
-/A 425 0 R
-/Parent 395 0 R
-/Prev 423 0 R
-/Next 475 0 R
-/First 431 0 R
-/Last 471 0 R
-/Count -9
->> endobj
-423 0 obj <<
-/Title 424 0 R
-/A 421 0 R
-/Parent 395 0 R
-/Prev 419 0 R
-/Next 427 0 R
->> endobj
-419 0 obj <<
-/Title 420 0 R
-/A 417 0 R
-/Parent 395 0 R
-/Prev 415 0 R
-/Next 423 0 R
->> endobj
-415 0 obj <<
-/Title 416 0 R
-/A 413 0 R
-/Parent 395 0 R
-/Prev 403 0 R
-/Next 419 0 R
->> endobj
-411 0 obj <<
-/Title 412 0 R
-/A 409 0 R
-/Parent 403 0 R
-/Prev 407 0 R
->> endobj
-407 0 obj <<
-/Title 408 0 R
-/A 405 0 R
-/Parent 403 0 R
-/Next 411 0 R
->> endobj
-403 0 obj <<
-/Title 404 0 R
-/A 401 0 R
-/Parent 395 0 R
-/Prev 399 0 R
-/Next 415 0 R
-/First 407 0 R
-/Last 411 0 R
-/Count -2
->> endobj
-399 0 obj <<
-/Title 400 0 R
-/A 397 0 R
-/Parent 395 0 R
-/Next 403 0 R
->> endobj
-395 0 obj <<
-/Title 396 0 R
-/A 393 0 R
-/Parent 295 0 R
-/Prev 299 0 R
-/Next 499 0 R
-/First 399 0 R
-/Last 495 0 R
-/Count -8
->> endobj
-391 0 obj <<
-/Title 392 0 R
-/A 389 0 R
-/Parent 387 0 R
->> endobj
-387 0 obj <<
-/Title 388 0 R
-/A 385 0 R
-/Parent 375 0 R
-/Prev 383 0 R
-/First 391 0 R
-/Last 391 0 R
-/Count -1
->> endobj
-383 0 obj <<
-/Title 384 0 R
-/A 381 0 R
-/Parent 375 0 R
-/Prev 379 0 R
-/Next 387 0 R
->> endobj
-379 0 obj <<
-/Title 380 0 R
-/A 377 0 R
-/Parent 375 0 R
-/Next 383 0 R
->> endobj
-375 0 obj <<
-/Title 376 0 R
-/A 373 0 R
-/Parent 299 0 R
-/Prev 363 0 R
-/First 379 0 R
-/Last 387 0 R
-/Count -3
->> endobj
-371 0 obj <<
-/Title 372 0 R
-/A 369 0 R
-/Parent 363 0 R
-/Prev 367 0 R
->> endobj
-367 0 obj <<
-/Title 368 0 R
-/A 365 0 R
-/Parent 363 0 R
-/Next 371 0 R
->> endobj
-363 0 obj <<
-/Title 364 0 R
-/A 361 0 R
-/Parent 299 0 R
-/Prev 347 0 R
-/Next 375 0 R
-/First 367 0 R
-/Last 371 0 R
-/Count -2
->> endobj
-359 0 obj <<
-/Title 360 0 R
-/A 357 0 R
-/Parent 347 0 R
-/Prev 355 0 R
->> endobj
-355 0 obj <<
-/Title 356 0 R
-/A 353 0 R
-/Parent 347 0 R
-/Prev 351 0 R
-/Next 359 0 R
->> endobj
-351 0 obj <<
-/Title 352 0 R
-/A 349 0 R
-/Parent 347 0 R
-/Next 355 0 R
->> endobj
-347 0 obj <<
-/Title 348 0 R
-/A 345 0 R
-/Parent 299 0 R
-/Prev 311 0 R
-/Next 363 0 R
-/First 351 0 R
-/Last 359 0 R
-/Count -3
->> endobj
-343 0 obj <<
-/Title 344 0 R
-/A 341 0 R
-/Parent 311 0 R
-/Prev 339 0 R
->> endobj
-339 0 obj <<
-/Title 340 0 R
-/A 337 0 R
-/Parent 311 0 R
-/Prev 335 0 R
-/Next 343 0 R
->> endobj
-335 0 obj <<
-/Title 336 0 R
-/A 333 0 R
-/Parent 311 0 R
-/Prev 331 0 R
-/Next 339 0 R
->> endobj
-331 0 obj <<
-/Title 332 0 R
-/A 329 0 R
-/Parent 311 0 R
-/Prev 327 0 R
-/Next 335 0 R
->> endobj
-327 0 obj <<
-/Title 328 0 R
-/A 325 0 R
-/Parent 311 0 R
-/Prev 323 0 R
-/Next 331 0 R
->> endobj
-323 0 obj <<
-/Title 324 0 R
-/A 321 0 R
-/Parent 311 0 R
-/Prev 319 0 R
-/Next 327 0 R
->> endobj
-319 0 obj <<
-/Title 320 0 R
-/A 317 0 R
-/Parent 311 0 R
-/Prev 315 0 R
-/Next 323 0 R
->> endobj
-315 0 obj <<
-/Title 316 0 R
-/A 313 0 R
-/Parent 311 0 R
-/Next 319 0 R
->> endobj
-311 0 obj <<
-/Title 312 0 R
-/A 309 0 R
-/Parent 299 0 R
-/Prev 307 0 R
-/Next 347 0 R
-/First 315 0 R
-/Last 343 0 R
-/Count -8
->> endobj
-307 0 obj <<
-/Title 308 0 R
-/A 305 0 R
-/Parent 299 0 R
-/Prev 303 0 R
-/Next 311 0 R
->> endobj
-303 0 obj <<
-/Title 304 0 R
-/A 301 0 R
-/Parent 299 0 R
-/Next 307 0 R
->> endobj
-299 0 obj <<
-/Title 300 0 R
-/A 297 0 R
-/Parent 295 0 R
-/Next 395 0 R
-/First 303 0 R
-/Last 375 0 R
-/Count -6
->> endobj
-295 0 obj <<
-/Title 296 0 R
-/A 293 0 R
-/Parent 3770 0 R
-/Prev 83 0 R
-/Next 1223 0 R
-/First 299 0 R
-/Last 1191 0 R
-/Count -18
->> endobj
-291 0 obj <<
-/Title 292 0 R
-/A 289 0 R
-/Parent 283 0 R
-/Prev 287 0 R
->> endobj
-287 0 obj <<
-/Title 288 0 R
-/A 285 0 R
-/Parent 283 0 R
-/Next 291 0 R
->> endobj
-283 0 obj <<
-/Title 284 0 R
-/A 281 0 R
-/Parent 83 0 R
-/Prev 251 0 R
-/First 287 0 R
-/Last 291 0 R
-/Count -2
->> endobj
-279 0 obj <<
-/Title 280 0 R
-/A 277 0 R
-/Parent 251 0 R
-/Prev 275 0 R
->> endobj
-275 0 obj <<
-/Title 276 0 R
-/A 273 0 R
-/Parent 251 0 R
-/Prev 271 0 R
-/Next 279 0 R
->> endobj
-271 0 obj <<
-/Title 272 0 R
-/A 269 0 R
-/Parent 251 0 R
-/Prev 263 0 R
-/Next 275 0 R
->> endobj
-267 0 obj <<
-/Title 268 0 R
-/A 265 0 R
-/Parent 263 0 R
->> endobj
-263 0 obj <<
-/Title 264 0 R
-/A 261 0 R
-/Parent 251 0 R
-/Prev 259 0 R
-/Next 271 0 R
-/First 267 0 R
-/Last 267 0 R
-/Count -1
->> endobj
-259 0 obj <<
-/Title 260 0 R
-/A 257 0 R
-/Parent 251 0 R
-/Prev 255 0 R
-/Next 263 0 R
->> endobj
-255 0 obj <<
-/Title 256 0 R
-/A 253 0 R
-/Parent 251 0 R
-/Next 259 0 R
->> endobj
-251 0 obj <<
-/Title 252 0 R
-/A 249 0 R
-/Parent 83 0 R
-/Prev 211 0 R
-/Next 283 0 R
-/First 255 0 R
-/Last 279 0 R
-/Count -6
->> endobj
-247 0 obj <<
-/Title 248 0 R
-/A 245 0 R
-/Parent 239 0 R
-/Prev 243 0 R
->> endobj
-243 0 obj <<
-/Title 244 0 R
-/A 241 0 R
-/Parent 239 0 R
-/Next 247 0 R
->> endobj
-239 0 obj <<
-/Title 240 0 R
-/A 237 0 R
-/Parent 211 0 R
-/Prev 235 0 R
-/First 243 0 R
-/Last 247 0 R
-/Count -2
->> endobj
-235 0 obj <<
-/Title 236 0 R
-/A 233 0 R
-/Parent 211 0 R
-/Prev 223 0 R
-/Next 239 0 R
->> endobj
-231 0 obj <<
-/Title 232 0 R
-/A 229 0 R
-/Parent 223 0 R
-/Prev 227 0 R
->> endobj
-227 0 obj <<
-/Title 228 0 R
-/A 225 0 R
-/Parent 223 0 R
-/Next 231 0 R
->> endobj
-223 0 obj <<
-/Title 224 0 R
-/A 221 0 R
-/Parent 211 0 R
-/Prev 219 0 R
-/Next 235 0 R
-/First 227 0 R
-/Last 231 0 R
-/Count -2
->> endobj
-219 0 obj <<
-/Title 220 0 R
-/A 217 0 R
-/Parent 211 0 R
-/Prev 215 0 R
-/Next 223 0 R
->> endobj
-215 0 obj <<
-/Title 216 0 R
-/A 213 0 R
-/Parent 211 0 R
-/Next 219 0 R
->> endobj
-211 0 obj <<
-/Title 212 0 R
-/A 209 0 R
-/Parent 83 0 R
-/Prev 147 0 R
-/Next 251 0 R
-/First 215 0 R
-/Last 239 0 R
-/Count -5
->> endobj
-207 0 obj <<
-/Title 208 0 R
-/A 205 0 R
-/Parent 203 0 R
->> endobj
-203 0 obj <<
-/Title 204 0 R
-/A 201 0 R
-/Parent 147 0 R
-/Prev 179 0 R
-/First 207 0 R
-/Last 207 0 R
-/Count -1
->> endobj
-199 0 obj <<
-/Title 200 0 R
-/A 197 0 R
-/Parent 179 0 R
-/Prev 195 0 R
->> endobj
-195 0 obj <<
-/Title 196 0 R
-/A 193 0 R
-/Parent 179 0 R
-/Prev 191 0 R
-/Next 199 0 R
->> endobj
-191 0 obj <<
-/Title 192 0 R
-/A 189 0 R
-/Parent 179 0 R
-/Prev 187 0 R
-/Next 195 0 R
->> endobj
-187 0 obj <<
-/Title 188 0 R
-/A 185 0 R
-/Parent 179 0 R
-/Prev 183 0 R
-/Next 191 0 R
->> endobj
-183 0 obj <<
-/Title 184 0 R
-/A 181 0 R
-/Parent 179 0 R
-/Next 187 0 R
->> endobj
-179 0 obj <<
-/Title 180 0 R
-/A 177 0 R
-/Parent 147 0 R
-/Prev 163 0 R
-/Next 203 0 R
-/First 183 0 R
-/Last 199 0 R
-/Count -5
->> endobj
-175 0 obj <<
-/Title 176 0 R
-/A 173 0 R
-/Parent 163 0 R
-/Prev 171 0 R
->> endobj
-171 0 obj <<
-/Title 172 0 R
-/A 169 0 R
-/Parent 163 0 R
-/Prev 167 0 R
-/Next 175 0 R
->> endobj
-167 0 obj <<
-/Title 168 0 R
-/A 165 0 R
-/Parent 163 0 R
-/Next 171 0 R
->> endobj
-163 0 obj <<
-/Title 164 0 R
-/A 161 0 R
-/Parent 147 0 R
-/Prev 159 0 R
-/Next 179 0 R
-/First 167 0 R
-/Last 175 0 R
-/Count -3
->> endobj
-159 0 obj <<
-/Title 160 0 R
-/A 157 0 R
-/Parent 147 0 R
-/Prev 155 0 R
-/Next 163 0 R
->> endobj
-155 0 obj <<
-/Title 156 0 R
-/A 153 0 R
-/Parent 147 0 R
-/Prev 151 0 R
-/Next 159 0 R
->> endobj
-151 0 obj <<
-/Title 152 0 R
-/A 149 0 R
-/Parent 147 0 R
-/Next 155 0 R
->> endobj
-147 0 obj <<
-/Title 148 0 R
-/A 145 0 R
-/Parent 83 0 R
-/Prev 107 0 R
-/Next 211 0 R
-/First 151 0 R
-/Last 203 0 R
-/Count -6
->> endobj
-143 0 obj <<
-/Title 144 0 R
-/A 141 0 R
-/Parent 111 0 R
-/Prev 135 0 R
->> endobj
-139 0 obj <<
-/Title 140 0 R
-/A 137 0 R
-/Parent 135 0 R
->> endobj
-135 0 obj <<
-/Title 136 0 R
-/A 133 0 R
-/Parent 111 0 R
-/Prev 123 0 R
-/Next 143 0 R
-/First 139 0 R
-/Last 139 0 R
-/Count -1
->> endobj
-131 0 obj <<
-/Title 132 0 R
-/A 129 0 R
-/Parent 123 0 R
-/Prev 127 0 R
->> endobj
-127 0 obj <<
-/Title 128 0 R
-/A 125 0 R
-/Parent 123 0 R
-/Next 131 0 R
->> endobj
-123 0 obj <<
-/Title 124 0 R
-/A 121 0 R
-/Parent 111 0 R
-/Prev 119 0 R
-/Next 135 0 R
-/First 127 0 R
-/Last 131 0 R
-/Count -2
->> endobj
-119 0 obj <<
-/Title 120 0 R
-/A 117 0 R
-/Parent 111 0 R
-/Prev 115 0 R
-/Next 123 0 R
->> endobj
-115 0 obj <<
-/Title 116 0 R
-/A 113 0 R
-/Parent 111 0 R
-/Next 119 0 R
->> endobj
-111 0 obj <<
-/Title 112 0 R
-/A 109 0 R
-/Parent 107 0 R
-/First 115 0 R
-/Last 143 0 R
-/Count -5
->> endobj
-107 0 obj <<
-/Title 108 0 R
-/A 105 0 R
-/Parent 83 0 R
-/Prev 87 0 R
-/Next 147 0 R
-/First 111 0 R
-/Last 111 0 R
-/Count -1
->> endobj
-103 0 obj <<
-/Title 104 0 R
-/A 101 0 R
-/Parent 99 0 R
->> endobj
-99 0 obj <<
-/Title 100 0 R
-/A 97 0 R
-/Parent 87 0 R
-/Prev 95 0 R
-/First 103 0 R
-/Last 103 0 R
-/Count -1
->> endobj
-95 0 obj <<
-/Title 96 0 R
-/A 93 0 R
-/Parent 87 0 R
-/Prev 91 0 R
-/Next 99 0 R
->> endobj
-91 0 obj <<
-/Title 92 0 R
-/A 89 0 R
-/Parent 87 0 R
-/Next 95 0 R
->> endobj
-87 0 obj <<
-/Title 88 0 R
-/A 85 0 R
-/Parent 83 0 R
-/Next 107 0 R
-/First 91 0 R
-/Last 99 0 R
-/Count -3
->> endobj
-83 0 obj <<
-/Title 84 0 R
-/A 81 0 R
-/Parent 3770 0 R
-/Prev 7 0 R
-/Next 295 0 R
-/First 87 0 R
-/Last 283 0 R
-/Count -6
->> endobj
-79 0 obj <<
-/Title 80 0 R
-/A 77 0 R
-/Parent 43 0 R
-/Prev 75 0 R
->> endobj
-75 0 obj <<
-/Title 76 0 R
-/A 73 0 R
-/Parent 43 0 R
-/Prev 71 0 R
-/Next 79 0 R
->> endobj
-71 0 obj <<
-/Title 72 0 R
-/A 69 0 R
-/Parent 43 0 R
-/Prev 67 0 R
-/Next 75 0 R
->> endobj
-67 0 obj <<
-/Title 68 0 R
-/A 65 0 R
-/Parent 43 0 R
-/Prev 51 0 R
-/Next 71 0 R
->> endobj
-63 0 obj <<
-/Title 64 0 R
-/A 61 0 R
-/Parent 51 0 R
-/Prev 55 0 R
->> endobj
-59 0 obj <<
-/Title 60 0 R
-/A 57 0 R
-/Parent 55 0 R
->> endobj
-55 0 obj <<
-/Title 56 0 R
-/A 53 0 R
-/Parent 51 0 R
-/Next 63 0 R
-/First 59 0 R
-/Last 59 0 R
-/Count -1
->> endobj
-51 0 obj <<
-/Title 52 0 R
-/A 49 0 R
-/Parent 43 0 R
-/Prev 47 0 R
-/Next 67 0 R
-/First 55 0 R
-/Last 63 0 R
-/Count -2
->> endobj
-47 0 obj <<
-/Title 48 0 R
-/A 45 0 R
-/Parent 43 0 R
-/Next 51 0 R
->> endobj
-43 0 obj <<
-/Title 44 0 R
-/A 41 0 R
-/Parent 7 0 R
-/Prev 11 0 R
-/First 47 0 R
-/Last 79 0 R
-/Count -6
->> endobj
-39 0 obj <<
-/Title 40 0 R
-/A 37 0 R
-/Parent 11 0 R
-/Prev 35 0 R
->> endobj
-35 0 obj <<
-/Title 36 0 R
-/A 33 0 R
-/Parent 11 0 R
-/Prev 31 0 R
-/Next 39 0 R
->> endobj
-31 0 obj <<
-/Title 32 0 R
-/A 29 0 R
-/Parent 11 0 R
-/Prev 27 0 R
-/Next 35 0 R
->> endobj
-27 0 obj <<
-/Title 28 0 R
-/A 25 0 R
-/Parent 11 0 R
-/Prev 23 0 R
-/Next 31 0 R
->> endobj
-23 0 obj <<
-/Title 24 0 R
-/A 21 0 R
-/Parent 11 0 R
-/Prev 19 0 R
-/Next 27 0 R
->> endobj
-19 0 obj <<
-/Title 20 0 R
-/A 17 0 R
-/Parent 11 0 R
-/Prev 15 0 R
-/Next 23 0 R
->> endobj
-15 0 obj <<
-/Title 16 0 R
-/A 13 0 R
-/Parent 11 0 R
-/Next 19 0 R
->> endobj
-11 0 obj <<
-/Title 12 0 R
-/A 9 0 R
-/Parent 7 0 R
-/Next 43 0 R
-/First 15 0 R
-/Last 39 0 R
-/Count -7
->> endobj
-7 0 obj <<
-/Title 8 0 R
-/A 5 0 R
-/Parent 3770 0 R
-/Next 83 0 R
-/First 11 0 R
-/Last 43 0 R
-/Count -2
->> endobj
-3771 0 obj <<
-/Names [(ADS) 2330 0 R (AdvancedNetworkManagement) 2976 0 R (Appendixes) 3488 0 R (CUPS-printing) 2733 0 R (Doc-Start) 1614 0 R (InterdomainTrusts) 3159 0 R (IntroSMB) 2096 0 R (Item.1) 2190 0 R (Item.10) 2294 0 R (Item.100) 3578 0 R (Item.101) 3579 0 R (Item.102) 3584 0 R (Item.103) 3585 0 R (Item.104) 3666 0 R (Item.105) 3667 0 R (Item.106) 3668 0 R (Item.107) 3669 0 R (Item.108) 3670 0 R (Item.11) 2295 0 R (Item.12) 2296 0 R (Item.13) 2410 0 R (Item.14) 2411 0 R (Item.15) 2412 0 R (Item.16) 2417 0 R (Item.17) 2475 0 R (Item.18) 2476 0 R (Item.19) 2477 0 R (Item.2) 2191 0 R (Item.20) 2625 0 R (Item.21) 2626 0 R (Item.22) 2627 0 R (Item.23) 2707 0 R (Item.24) 2708 0 R (Item.25) 2709 0 R (Item.26) 2710 0 R (Item.27) 2711 0 R (Item.28) 2712 0 R (Item.29) 2713 0 R (Item.3) 2238 0 R (Item.30) 2714 0 R (Item.31) 2980 0 R (Item.32) 2981 0 R (Item.33) 2987 0 R (Item.34) 2988 0 R (Item.35) 2989 0 R (Item.36) 3031 0 R (Item.37) 3032 0 R (Item.38) 3033 0 R (Item.39) 3034 0 R (Item.4) 2239 0 R (Item.40) 3047 0 R (Item.41) 3048 0 R (Item.42) 3049 0 R (Item.43) 3050 0 R (Item.44) 3051 0 R (Item.45) 3052 0 R (Item.46) 3053 0 R (Item.47) 3054 0 R (Item.48) 3055 0 R (Item.49) 3078 0 R (Item.5) 2240 0 R (Item.50) 3079 0 R (Item.51) 3084 0 R (Item.52) 3085 0 R (Item.53) 3086 0 R (Item.54) 3087 0 R (Item.55) 3092 0 R (Item.56) 3093 0 R (Item.57) 3133 0 R (Item.58) 3134 0 R (Item.59) 3135 0 R (Item.6) 2290 0 R (Item.60) 3136 0 R (Item.61) 3393 0 R (Item.62) 3394 0 R (Item.63) 3395 0 R (Item.64) 3400 0 R (Item.65) 3405 0 R (Item.66) 3406 0 R (Item.67) 3407 0 R (Item.68) 3408 0 R (Item.69) 3409 0 R (Item.7) 2291 0 R (Item.70) 3410 0 R (Item.71) 3411 0 R (Item.72) 3412 0 R (Item.73) 3413 0 R (Item.74) 3418 0 R (Item.75) 3419 0 R (Item.76) 3420 0 R (Item.77) 3421 0 R (Item.78) 3422 0 R (Item.79) 3423 0 R (Item.8) 2292 0 R (Item.80) 3424 0 R (Item.81) 3500 0 R (Item.82) 3506 0 R (Item.83) 3507 0 R (Item.84) 3508 0 R (Item.85) 3563 0 R (Item.86) 3564 0 R (Item.87) 3565 0 R (Item.88) 3566 0 R (Item.89) 3567 0 R (Item.9) 2293 0 R (Item.90) 3568 0 R (Item.91) 3569 0 R (Item.92) 3570 0 R (Item.93) 3571 0 R (Item.94) 3572 0 R (Item.95) 3573 0 R (Item.96) 3574 0 R (Item.97) 3575 0 R (Item.98) 3576 0 R (Item.99) 3577 0 R (NT4Migration) 3541 0 R (NetworkBrowsing) 2379 0 R (Other-Clients) 3627 0 R (PolicyMgmt) 3014 0 R (Portability) 3606 0 R (ProfileMgmt) 3060 0 R (SWAT) 3684 0 R (ServerType) 2174 0 R (VFS) 3215 0 R (ads-create-machine-account) 2341 0 R (ads-test-server) 2343 0 R (ads-test-smbclient) 2344 0 R (browse-force-master) 2404 0 R (bugreport) 3466 0 R (chapter*.1) 1648 0 R (chapter.1) 10 0 R (chapter.10) 394 0 R (chapter.11) 498 0 R (chapter.12) 538 0 R (chapter.13) 542 0 R (chapter.14) 634 0 R (chapter.15) 694 0 R (chapter.16) 798 0 R (chapter.17) 830 0 R (chapter.18) 874 0 R (chapter.19) 970 0 R (chapter.2) 42 0 R (chapter.20) 1002 0 R (chapter.21) 1038 0 R (chapter.22) 1078 0 R (chapter.23) 1090 0 R (chapter.24) 1138 0 R (chapter.25) 1170 0 R (chapter.26) 1190 0 R (chapter.27) 1226 0 R (chapter.28) 1246 0 R (chapter.29) 1270 0 R (chapter.3) 86 0 R (chapter.30) 1302 0 R (chapter.31) 1362 0 R (chapter.32) 1410 0 R (chapter.33) 1450 0 R (chapter.34) 1522 0 R (chapter.35) 1570 0 R (chapter.4) 106 0 R (chapter.5) 146 0 R (chapter.6) 210 0 R (chapter.7) 250 0 R (chapter.8) 282 0 R (chapter.9) 298 0 R (compiling) 2146 0 R (diagnosis) 2163 0 R (domain-member) 2278 0 R (groupmapping) 2624 0 R (id2733677) 2115 0 R (id2733814) 2109 0 R (id2733867) 2143 0 R (id2733970) 2139 0 R (id2733997) 2142 0 R (id2736665) 3190 0 R (id2736726) 3197 0 R (id2736835) 3202 0 R (id2736861) 3203 0 R (id2738692) 2131 0 R (id2738754) 2100 0 R (id2738812) 2101 0 R (id2738964) 2133 0 R (id2739101) 2175 0 R (id2788270) 3216 0 R (id2788445) 3180 0 R (id2788527) 2114 0 R (id2802059) 2145 0 R (id2802112) 2152 0 R (id2802151) 2153 0 R (id2802202) 2154 0 R (id2802305) 2155 0 R (id2802366) 2159 0 R (id2802412) 2188 0 R (id2802434) 2189 0 R (id2802598) 2176 0 R (id2802639) 2181 0 R (id2802654) 2182 0 R (id2802780) 2232 0 R (id2802804) 2233 0 R (id2802916) 2192 0 R (id2802970) 2198 0 R (id2803054) 2208 0 R (id2803230) 2216 0 R (id2803291) 2222 0 R (id2803311) 2223 0 R (id2803429) 2225 0 R (id2803493) 2309 0 R (id2803553) 2310 0 R (id2803565) 2307 0 R (id2803758) 2241 0 R (id2804059) 2252 0 R (id2804328) 2258 0 R (id2804562) 2266 0 R (id2804618) 2268 0 R (id2804725) 2274 0 R (id2804732) 2275 0 R (id2804770) 2276 0 R (id2804817) 2277 0 R (id2804868) 2283 0 R (id2804917) 2284 0 R (id2804942) 2285 0 R (id2805105) 2297 0 R (id2805216) 2331 0 R (id2805383) 2316 0 R (id2805407) 2317 0 R (id2805426) 2318 0 R (id2805460) 2319 0 R (id2805556) 2324 0 R (id2805585) 2325 0 R (id2805609) 2354 0 R (id2805766) 2332 0 R (id2805960) 2342 0 R (id2806114) 2349 0 R (id2806191) 2380 0 R (id2806514) 2365 0 R (id2806782) 2432 0 R (id2806842) 2385 0 R (id2807004) 2390 0 R (id2807131) 2395 0 R (id2807320) 2401 0 R (id2807585) 2409 0 R (id2807734) 2418 0 R (id2807751) 2419 0 R (id2807780) 2420 0 R (id2807891) 2421 0 R (id2807958) 2427 0 R (id2808132) 2591 0 R (id2808250) 2590 0 R (id2808414) 2436 0 R (id2808439) 2441 0 R (id2808469) 2442 0 R (id2808483) 2443 0 R (id2808550) 2444 0 R (id2808665) 2450 0 R (id2808712) 2455 0 R (id2808819) 2456 0 R (id2808899) 2461 0 R (id2808950) 2462 0 R (id2809295) 2483 0 R (id2809348) 2484 0 R (id2809510) 2493 0 R (id2809549) 2494 0 R (id2809583) 2495 0 R (id2809764) 2500 0 R (id2809793) 2501 0 R (id2809809) 2502 0 R (id2809816) 2503 0 R (id2809917) 2509 0 R (id2810056) 2517 0 R (id2810094) 2521 0 R (id2810204) 2527 0 R (id2810212) 2528 0 R (id2810329) 2534 0 R (id2810500) 2549 0 R (id2810537) 2550 0 R (id2810652) 2556 0 R (id2810932) 2565 0 R (id2810989) 2570 0 R (id2810996) 2571 0 R (id2811050) 2572 0 R (id2811195) 2582 0 R (id2811224) 2583 0 R (id2811268) 2584 0 R (id2811476) 2592 0 R (id2811597) 2597 0 R (id2811679) 2598 0 R (id2811783) 2599 0 R (id2811833) 2604 0 R (id2811992) 2605 0 R (id2812308) 2614 0 R (id2812430) 2680 0 R (id2812456) 2682 0 R (id2812535) 2694 0 R (id2812542) 2695 0 R (id2812694) 2637 0 R (id2812810) 2641 0 R (id2812857) 2646 0 R (id2813089) 2657 0 R (id2813187) 2662 0 R (id2813295) 2669 0 R (id2813427) 2678 0 R (id2813530) 2687 0 R (id2813550) 2688 0 R (id2813574) 2689 0 R (id2813747) 2700 0 R (id2813814) 2705 0 R (id2813856) 2706 0 R (id2813990) 2720 0 R (id2814213) 2734 0 R (id2814271) 2736 0 R (id2814297) 2755 0 R (id2814539) 2721 0 R (id2814615) 2726 0 R (id2814634) 2727 0 R (id2814659) 2728 0 R (id2814803) 2741 0 R (id2815273) 2882 0 R (id2815303) 2883 0 R (id2815332) 2884 0 R (id2815366) 2890 0 R (id2815389) 2891 0 R (id2815469) 2760 0 R (id2815510) 2761 0 R (id2815597) 2766 0 R (id2815763) 2777 0 R (id2816112) 2786 0 R (id2816498) 2817 0 R (id2816535) 2818 0 R (id2816954) 2837 0 R (id2817563) 2861 0 R (id2817669) 2866 0 R (id2817911) 2875 0 R (id2817939) 2876 0 R (id2818011) 2877 0 R (id2818101) 2978 0 R (id2818115) 2979 0 R (id2818167) 2990 0 R (id2818250) 2999 0 R (id2818334) 2977 0 R (id2818477) 2892 0 R (id2818549) 2897 0 R (id2818583) 2898 0 R (id2818611) 2899 0 R (id2818639) 2901 0 R (id2818714) 2906 0 R (id2818808) 2911 0 R (id2818885) 2916 0 R (id2819005) 2917 0 R (id2819210) 2918 0 R (id2819283) 2923 0 R (id2819398) 2924 0 R (id2819455) 2925 0 R (id2819700) 2935 0 R (id2819708) 2937 0 R (id2819844) 2943 0 R (id2819945) 2951 0 R (id2819982) 2952 0 R (id2820091) 2954 0 R (id2820315) 2964 0 R (id2820406) 2969 0 R (id2820461) 2970 0 R (id2820524) 2982 0 R (id2820685) 3062 0 R (id2820699) 3063 0 R (id2820796) 3061 0 R (id2820871) 3015 0 R (id2821084) 3005 0 R (id2821122) 3017 0 R (id2821211) 3023 0 R (id2821313) 3024 0 R (id2821336) 3025 0 R (id2821434) 3030 0 R (id2821541) 3039 0 R (id2821654) 3040 0 R (id2821674) 3045 0 R (id2821699) 3046 0 R (id2821880) 3160 0 R (id2822021) 3068 0 R (id2822117) 3069 0 R (id2822156) 3070 0 R (id2822276) 3076 0 R (id2822284) 3077 0 R (id2822555) 3094 0 R (id2822622) 3095 0 R (id2822892) 3108 0 R (id2822938) 3109 0 R (id2822956) 3110 0 R (id2823049) 3116 0 R (id2823071) 3117 0 R (id2823087) 3118 0 R (id2823121) 3119 0 R (id2823166) 3120 0 R (id2823208) 3125 0 R (id2823237) 3126 0 R (id2823276) 3127 0 R (id2823326) 3132 0 R (id2823710) 3145 0 R (id2824202) 3165 0 R (id2824215) 3166 0 R (id2824259) 3167 0 R (id2824283) 3168 0 R (id2824310) 3169 0 R (id2824406) 3174 0 R (id2825175) 3208 0 R (id2825208) 3209 0 R (id2825244) 3210 0 R (id2825412) 3244 0 R (id2825446) 3217 0 R (id2825454) 3218 0 R (id2825492) 3219 0 R (id2825530) 3224 0 R (id2825613) 3226 0 R (id2825751) 3227 0 R (id2825790) 3228 0 R (id2825812) 3234 0 R (id2825867) 3237 0 R (id2825942) 3259 0 R (id2826159) 3253 0 R (id2826228) 3282 0 R (id2826267) 3283 0 R (id2826310) 3292 0 R (id2826342) 3293 0 R (id2826354) 3294 0 R (id2826376) 3264 0 R (id2826514) 3265 0 R (id2826558) 3270 0 R (id2826601) 3271 0 R (id2826696) 3277 0 R (id2826803) 3303 0 R (id2826819) 3304 0 R (id2826920) 3313 0 R (id2826957) 3318 0 R (id2827268) 3305 0 R (id2827319) 3311 0 R (id2827361) 3312 0 R (id2827407) 3341 0 R (id2827556) 3325 0 R (id2827625) 3327 0 R (id2827715) 3328 0 R (id2827760) 3333 0 R (id2827902) 3385 0 R (id2827936) 3386 0 R (id2828069) 3342 0 R (id2828185) 3347 0 R (id2828409) 3357 0 R (id2828437) 3362 0 R (id2828517) 3363 0 R (id2828547) 3368 0 R (id2828675) 3435 0 R (id2828941) 3392 0 R (id2830051) 3429 0 R (id2830124) 3470 0 R (id2830215) 3467 0 R (id2830292) 3438 0 R (id2830434) 3444 0 R (id2830540) 3456 0 R (id2830694) 3459 0 R (id2830752) 3719 0 R (id2830777) 3490 0 R (id2830784) 3491 0 R (id2830817) 3494 0 R (id2830833) 3495 0 R (id2830910) 3472 0 R (id2831046) 3477 0 R (id2831139) 3478 0 R (id2831186) 3479 0 R (id2831225) 3543 0 R (id2831355) 3542 0 R (id2831397) 3497 0 R (id2831574) 3509 0 R (id2831615) 3513 0 R (id2831698) 3518 0 R (id2831835) 3519 0 R (id2831902) 3524 0 R (id2831933) 3525 0 R (id2831983) 3526 0 R (id2832050) 3527 0 R (id2832242) 3532 0 R (id2832373) 3608 0 R (id2832396) 3609 0 R (id2832471) 3607 0 R (id2832694) 3549 0 R (id2832748) 3554 0 R (id2832809) 3555 0 R (id2832867) 3560 0 R (id2832897) 3561 0 R (id2832922) 3562 0 R (id2833177) 3586 0 R (id2833194) 3587 0 R (id2833259) 3589 0 R (id2833331) 3595 0 R (id2833501) 3590 0 R (id2833599) 3628 0 R (id2833868) 3614 0 R (id2833905) 3619 0 R (id2833912) 3620 0 R (id2833938) 3621 0 R (id2833945) 3622 0 R (id2834033) 3686 0 R (id2834156) 3685 0 R (id2834174) 3634 0 R (id2834180) 3635 0 R (id2834263) 3641 0 R (id2834323) 3645 0 R (id2834352) 3647 0 R (id2834415) 3648 0 R (id2834422) 3649 0 R (id2834454) 3654 0 R (id2834484) 3655 0 R (id2834510) 3656 0 R (id2834541) 3658 0 R (id2834558) 3659 0 R (id2834585) 3660 0 R (id2834655) 3671 0 R (id2834672) 3672 0 R (id2834782) 3678 0 R (id2834849) 3720 0 R (id2835070) 3691 0 R (id2835143) 3696 0 R (id2835207) 3698 0 R (id2835315) 3703 0 R (id2835364) 3704 0 R (id2835413) 3705 0 R (id2835458) 3706 0 R (id2835496) 3707 0 R (id2835513) 3713 0 R (id2835738) 3721 0 R (id2835781) 3726 0 R (id2835834) 3727 0 R (id2835857) 3728 0 R (id2835914) 3729 0 R (id2835956) 3730 0 R (id2835977) 3735 0 R (install) 2138 0 R (integrate-ms-networks) 3258 0 R (introduction) 2095 0 R (locking) 3340 0 R (msdfs) 3243 0 R (optional) 2378 0 R (page.1) 1613 0 R (page.10) 1940 0 R (page.100) 2765 0 R (page.101) 2776 0 R (page.102) 2781 0 R (page.103) 2785 0 R (page.104) 2791 0 R (page.105) 2795 0 R (page.106) 2799 0 R (page.107) 2803 0 R (page.108) 2807 0 R (page.109) 2811 0 R (page.11) 1990 0 R (page.110) 2816 0 R (page.111) 2825 0 R (page.112) 2834 0 R (page.113) 2841 0 R (page.114) 2845 0 R (page.115) 2851 0 R (page.116) 2856 0 R (page.117) 2860 0 R (page.118) 2865 0 R (page.119) 2870 0 R (page.12) 2040 0 R (page.120) 2874 0 R (page.121) 2881 0 R (page.122) 2889 0 R (page.123) 2896 0 R (page.124) 2905 0 R (page.125) 2915 0 R (page.126) 2922 0 R (page.127) 2929 0 R (page.128) 2934 0 R (page.129) 2941 0 R (page.13) 2089 0 R (page.130) 2949 0 R (page.131) 2958 0 R (page.132) 2962 0 R (page.133) 2968 0 R (page.134) 2975 0 R (page.135) 2986 0 R (page.136) 2998 0 R (page.137) 3004 0 R (page.138) 3009 0 R (page.139) 3013 0 R (page.14) 2094 0 R (page.140) 3022 0 R (page.141) 3029 0 R (page.142) 3038 0 R (page.143) 3044 0 R (page.144) 3059 0 R (page.145) 3067 0 R (page.146) 3075 0 R (page.147) 3083 0 R (page.148) 3091 0 R (page.149) 3099 0 R (page.15) 2108 0 R (page.150) 3103 0 R (page.151) 3107 0 R (page.152) 3115 0 R (page.153) 3124 0 R (page.154) 3131 0 R (page.155) 3140 0 R (page.156) 3144 0 R (page.157) 3149 0 R (page.158) 3154 0 R (page.159) 3158 0 R (page.16) 2113 0 R (page.160) 3164 0 R (page.161) 3173 0 R (page.162) 3178 0 R (page.163) 3184 0 R (page.164) 3189 0 R (page.165) 3196 0 R (page.166) 3201 0 R (page.167) 3207 0 R (page.168) 3214 0 R (page.169) 3223 0 R (page.17) 2121 0 R (page.170) 3233 0 R (page.171) 3242 0 R (page.172) 3252 0 R (page.173) 3257 0 R (page.174) 3263 0 R (page.175) 3269 0 R (page.176) 3276 0 R (page.177) 3281 0 R (page.178) 3287 0 R (page.179) 3291 0 R (page.18) 2137 0 R (page.180) 3298 0 R (page.181) 3302 0 R (page.182) 3310 0 R (page.183) 3317 0 R (page.184) 3323 0 R (page.185) 3332 0 R (page.186) 3339 0 R (page.187) 3346 0 R (page.188) 3352 0 R (page.189) 3356 0 R (page.19) 2151 0 R (page.190) 3361 0 R (page.191) 3367 0 R (page.192) 3379 0 R (page.193) 3383 0 R (page.194) 3391 0 R (page.195) 3399 0 R (page.196) 3404 0 R (page.197) 3417 0 R (page.198) 3428 0 R (page.199) 3434 0 R (page.2) 1625 0 R (page.20) 2168 0 R (page.200) 3443 0 R (page.201) 3455 0 R (page.202) 3465 0 R (page.203) 3476 0 R (page.204) 3483 0 R (page.205) 3487 0 R (page.206) 3505 0 R (page.207) 3517 0 R (page.208) 3523 0 R (page.209) 3531 0 R (page.21) 2172 0 R (page.210) 3536 0 R (page.211) 3540 0 R (page.212) 3548 0 R (page.213) 3553 0 R (page.214) 3559 0 R (page.215) 3583 0 R (page.216) 3594 0 R (page.217) 3600 0 R (page.218) 3605 0 R (page.219) 3613 0 R (page.22) 2180 0 R (page.220) 3618 0 R (page.221) 3626 0 R (page.222) 3640 0 R (page.223) 3653 0 R (page.224) 3665 0 R (page.225) 3677 0 R (page.226) 3683 0 R (page.227) 3690 0 R (page.228) 3695 0 R (page.229) 3702 0 R (page.23) 2186 0 R (page.230) 3712 0 R (page.231) 3717 0 R (page.232) 3725 0 R (page.233) 3734 0 R (page.24) 2197 0 R (page.25) 2215 0 R (page.26) 2221 0 R (page.27) 2230 0 R (page.28) 2237 0 R (page.29) 2245 0 R (page.3) 1639 0 R (page.30) 2251 0 R (page.31) 2257 0 R (page.32) 2265 0 R (page.33) 2272 0 R (page.34) 2282 0 R (page.35) 2289 0 R (page.36) 2301 0 R (page.37) 2305 0 R (page.38) 2315 0 R (page.39) 2323 0 R (page.4) 1647 0 R (page.40) 2329 0 R (page.41) 2336 0 R (page.42) 2348 0 R (page.43) 2353 0 R (page.44) 2364 0 R (page.45) 2373 0 R (page.46) 2377 0 R (page.47) 2384 0 R (page.48) 2389 0 R (page.49) 2394 0 R (page.5) 1686 0 R (page.50) 2400 0 R (page.51) 2408 0 R (page.52) 2416 0 R (page.53) 2426 0 R (page.54) 2431 0 R (page.55) 2440 0 R (page.56) 2449 0 R (page.57) 2454 0 R (page.58) 2460 0 R (page.59) 2466 0 R (page.6) 1732 0 R (page.60) 2470 0 R (page.61) 2474 0 R (page.62) 2482 0 R (page.63) 2488 0 R (page.64) 2492 0 R (page.65) 2499 0 R (page.66) 2514 0 R (page.67) 2526 0 R (page.68) 2533 0 R (page.69) 2548 0 R (page.7) 1786 0 R (page.70) 2555 0 R (page.71) 2560 0 R (page.72) 2569 0 R (page.73) 2576 0 R (page.74) 2581 0 R (page.75) 2588 0 R (page.76) 2596 0 R (page.77) 2603 0 R (page.78) 2609 0 R (page.79) 2618 0 R (page.8) 1840 0 R (page.80) 2623 0 R (page.81) 2631 0 R (page.82) 2635 0 R (page.83) 2645 0 R (page.84) 2655 0 R (page.85) 2661 0 R (page.86) 2668 0 R (page.87) 2677 0 R (page.88) 2686 0 R (page.89) 2693 0 R (page.9) 1889 0 R (page.90) 2699 0 R (page.91) 2704 0 R (page.92) 2719 0 R (page.93) 2725 0 R (page.94) 2732 0 R (page.95) 2740 0 R (page.96) 2745 0 R (page.97) 2749 0 R (page.98) 2754 0 R (page.99) 2759 0 R (pam) 3179 0 R (part.1) 6 0 R (part.2) 82 0 R (part.3) 294 0 R (part.4) 1222 0 R (part.5) 1298 0 R (passdb) 2247 0 R (printing) 2636 0 R (problems) 2164 0 R (samba-bdc) 2306 0 R (samba-pdc) 2231 0 R (section*.2) 2936 0 R (section*.3) 2942 0 R (section*.4) 2950 0 R (section*.5) 2953 0 R (section*.6) 2963 0 R (section.1.1) 14 0 R (section.1.2) 18 0 R (section.1.3) 22 0 R (section.1.4) 26 0 R (section.1.5) 30 0 R (section.1.6) 34 0 R (section.1.7) 38 0 R (section.10.1) 398 0 R (section.10.2) 402 0 R (section.10.3) 414 0 R (section.10.4) 418 0 R (section.10.5) 422 0 R (section.10.6) 426 0 R (section.10.7) 474 0 R (section.10.8) 494 0 R (section.11.1) 502 0 R (section.11.2) 506 0 R (section.11.3) 510 0 R (section.11.4) 514 0 R (section.11.5) 526 0 R (section.11.6) 530 0 R (section.11.7) 534 0 R (section.13.1) 546 0 R (section.13.2) 550 0 R (section.13.3) 574 0 R (section.13.4) 594 0 R (section.14.1) 638 0 R (section.14.10) 682 0 R (section.14.11) 686 0 R (section.14.12) 690 0 R (section.14.2) 642 0 R (section.14.3) 646 0 R (section.14.4) 650 0 R (section.14.5) 654 0 R (section.14.6) 658 0 R (section.14.7) 662 0 R (section.14.8) 670 0 R (section.14.9) 674 0 R (section.15.1) 698 0 R (section.15.2) 702 0 R (section.15.3) 706 0 R (section.15.4) 714 0 R (section.15.5) 742 0 R (section.15.6) 790 0 R (section.15.7) 794 0 R (section.16.1) 802 0 R (section.16.2) 818 0 R (section.16.3) 822 0 R (section.17.1) 834 0 R (section.17.2) 858 0 R (section.17.3) 870 0 R (section.18.1) 878 0 R (section.18.2) 942 0 R (section.18.3) 946 0 R (section.18.4) 950 0 R (section.19.1) 974 0 R (section.19.2) 978 0 R (section.19.3) 990 0 R (section.2.1) 46 0 R (section.2.2) 50 0 R (section.2.3) 66 0 R (section.2.4) 70 0 R (section.2.5) 74 0 R (section.2.6) 78 0 R (section.20.1) 1006 0 R (section.20.2) 1034 0 R (section.21.1) 1042 0 R (section.21.2) 1046 0 R (section.21.3) 1066 0 R (section.22.1) 1082 0 R (section.23.1) 1094 0 R (section.23.2) 1114 0 R (section.24.1) 1142 0 R (section.24.2) 1146 0 R (section.24.3) 1150 0 R (section.24.4) 1154 0 R (section.24.5) 1158 0 R (section.24.6) 1162 0 R (section.24.7) 1166 0 R (section.25.1) 1174 0 R (section.25.2) 1178 0 R (section.25.3) 1182 0 R (section.25.4) 1186 0 R (section.26.1) 1194 0 R (section.26.2) 1198 0 R (section.26.3) 1202 0 R (section.26.4) 1214 0 R (section.26.5) 1218 0 R (section.27.1) 1230 0 R (section.27.2) 1234 0 R (section.27.3) 1238 0 R (section.27.4) 1242 0 R (section.28.1) 1250 0 R (section.28.2) 1254 0 R (section.28.3) 1258 0 R (section.28.4) 1262 0 R (section.28.5) 1266 0 R (section.29.1) 1274 0 R (section.29.2) 1278 0 R (section.29.3) 1282 0 R (section.29.4) 1286 0 R (section.29.5) 1290 0 R (section.29.6) 1294 0 R (section.3.1) 90 0 R (section.3.2) 94 0 R (section.3.3) 98 0 R (section.30.1) 1306 0 R (section.30.2) 1326 0 R (section.30.3) 1330 0 R (section.30.4) 1334 0 R (section.30.5) 1350 0 R (section.31.1) 1366 0 R (section.31.2) 1398 0 R (section.32.1) 1414 0 R (section.32.2) 1418 0 R (section.32.3) 1422 0 R (section.32.4) 1426 0 R (section.32.5) 1430 0 R (section.32.6) 1438 0 R (section.33.1) 1454 0 R (section.33.2) 1458 0 R (section.33.3) 1478 0 R (section.33.4) 1506 0 R (section.33.5) 1514 0 R (section.33.6) 1518 0 R (section.34.1) 1526 0 R (section.35.1) 1574 0 R (section.35.2) 1578 0 R (section.35.3) 1582 0 R (section.35.4) 1586 0 R (section.35.5) 1590 0 R (section.35.6) 1594 0 R (section.35.7) 1598 0 R (section.35.8) 1602 0 R (section.35.9) 1606 0 R (section.4.1) 110 0 R (section.5.1) 150 0 R (section.5.2) 154 0 R (section.5.3) 158 0 R (section.5.4) 162 0 R (section.5.5) 178 0 R (section.5.6) 202 0 R (section.6.1) 214 0 R (section.6.2) 218 0 R (section.6.3) 222 0 R (section.6.4) 234 0 R (section.6.5) 238 0 R (section.7.1) 254 0 R (section.7.2) 258 0 R (section.7.3) 262 0 R (section.7.4) 270 0 R (section.7.5) 274 0 R (section.7.6) 278 0 R (section.8.1) 286 0 R (section.8.2) 290 0 R (section.9.1) 302 0 R (section.9.2) 306 0 R (section.9.3) 310 0 R (section.9.4) 346 0 R (section.9.5) 362 0 R (section.9.6) 374 0 R (securing-samba) 2147 0 R (securitylevels) 2187 0 R (speed) 3718 0 R (subsection.10.2.1) 406 0 R (subsection.10.2.2) 410 0 R (subsection.10.6.1) 430 0 R (subsection.10.6.2) 434 0 R (subsection.10.6.3) 438 0 R (subsection.10.6.4) 442 0 R (subsection.10.6.5) 446 0 R (subsection.10.6.6) 458 0 R (subsection.10.6.7) 462 0 R (subsection.10.6.8) 466 0 R (subsection.10.6.9) 470 0 R (subsection.10.7.1) 478 0 R (subsection.10.7.2) 482 0 R (subsection.10.7.3) 486 0 R (subsection.10.7.4) 490 0 R (subsection.11.4.1) 518 0 R (subsection.11.4.2) 522 0 R (subsection.13.2.1) 554 0 R (subsection.13.2.2) 558 0 R (subsection.13.2.3) 562 0 R (subsection.13.2.4) 566 0 R (subsection.13.2.5) 570 0 R (subsection.13.3.1) 578 0 R (subsection.13.3.2) 582 0 R (subsection.13.3.3) 586 0 R (subsection.13.3.4) 590 0 R (subsection.13.4.1) 598 0 R (subsection.13.4.2) 602 0 R (subsection.13.4.3) 606 0 R (subsection.13.4.4) 610 0 R (subsection.13.4.5) 614 0 R (subsection.13.4.6) 618 0 R (subsection.13.4.7) 622 0 R (subsection.13.4.8) 626 0 R (subsection.13.4.9) 630 0 R (subsection.14.7.1) 666 0 R (subsection.14.9.1) 678 0 R (subsection.15.3.1) 710 0 R (subsection.15.4.1) 718 0 R (subsection.15.4.2) 722 0 R (subsection.15.4.3) 726 0 R (subsection.15.4.4) 730 0 R (subsection.15.4.5) 734 0 R (subsection.15.4.6) 738 0 R (subsection.15.5.1) 746 0 R (subsection.15.5.2) 750 0 R (subsection.15.5.3) 754 0 R (subsection.16.1.1) 806 0 R (subsection.16.3.1) 826 0 R (subsection.17.1.1) 838 0 R (subsection.17.1.2) 842 0 R (subsection.17.1.3) 850 0 R (subsection.17.2.1) 862 0 R (subsection.17.2.2) 866 0 R (subsection.18.1.1) 882 0 R (subsection.18.1.2) 902 0 R (subsection.18.1.3) 918 0 R (subsection.18.1.4) 922 0 R (subsection.18.4.1) 954 0 R (subsection.18.4.2) 962 0 R (subsection.18.4.3) 966 0 R (subsection.19.2.1) 982 0 R (subsection.19.2.2) 986 0 R (subsection.19.3.1) 994 0 R (subsection.19.3.2) 998 0 R (subsection.2.2.1) 54 0 R (subsection.2.2.2) 62 0 R (subsection.20.1.1) 1010 0 R (subsection.20.1.2) 1014 0 R (subsection.21.2.1) 1050 0 R (subsection.21.2.2) 1054 0 R (subsection.21.2.3) 1058 0 R (subsection.21.2.4) 1062 0 R (subsection.21.3.1) 1070 0 R (subsection.21.3.2) 1074 0 R (subsection.22.1.1) 1086 0 R (subsection.23.1.1) 1098 0 R (subsection.23.1.2) 1102 0 R (subsection.23.1.3) 1106 0 R (subsection.23.1.4) 1110 0 R (subsection.23.2.1) 1118 0 R (subsection.23.2.2) 1122 0 R (subsection.23.2.3) 1126 0 R (subsection.23.2.4) 1130 0 R (subsection.23.2.5) 1134 0 R (subsection.26.3.1) 1206 0 R (subsection.26.3.2) 1210 0 R (subsection.3.3.1) 102 0 R (subsection.30.1.1) 1310 0 R (subsection.30.1.2) 1314 0 R (subsection.30.4.1) 1338 0 R (subsection.30.5.1) 1354 0 R (subsection.30.5.2) 1358 0 R (subsection.31.1.1) 1370 0 R (subsection.31.1.2) 1394 0 R (subsection.31.2.1) 1402 0 R (subsection.31.2.2) 1406 0 R (subsection.32.5.1) 1434 0 R (subsection.32.6.1) 1442 0 R (subsection.32.6.2) 1446 0 R (subsection.33.2.1) 1462 0 R (subsection.33.2.2) 1466 0 R (subsection.33.2.3) 1470 0 R (subsection.33.2.4) 1474 0 R (subsection.33.3.1) 1482 0 R (subsection.33.3.2) 1486 0 R (subsection.33.3.3) 1490 0 R (subsection.33.3.4) 1494 0 R (subsection.33.3.5) 1498 0 R (subsection.33.3.6) 1502 0 R (subsection.33.4.1) 1510 0 R (subsection.34.1.1) 1530 0 R (subsection.34.1.10) 1566 0 R (subsection.34.1.2) 1534 0 R (subsection.34.1.3) 1538 0 R (subsection.34.1.4) 1542 0 R (subsection.34.1.5) 1546 0 R (subsection.34.1.6) 1550 0 R (subsection.34.1.7) 1554 0 R (subsection.34.1.8) 1558 0 R (subsection.34.1.9) 1562 0 R (subsection.4.1.1) 114 0 R (subsection.4.1.2) 118 0 R (subsection.4.1.3) 122 0 R (subsection.4.1.4) 134 0 R (subsection.4.1.5) 142 0 R (subsection.5.4.1) 166 0 R (subsection.5.4.2) 170 0 R (subsection.5.4.3) 174 0 R (subsection.5.5.1) 182 0 R (subsection.5.5.2) 186 0 R (subsection.5.5.3) 190 0 R (subsection.5.5.4) 194 0 R (subsection.5.5.5) 198 0 R (subsection.5.6.1) 206 0 R (subsection.6.3.1) 226 0 R (subsection.6.3.2) 230 0 R (subsection.6.5.1) 242 0 R (subsection.6.5.2) 246 0 R (subsection.7.3.1) 266 0 R (subsection.9.3.1) 314 0 R (subsection.9.3.2) 318 0 R (subsection.9.3.3) 322 0 R (subsection.9.3.4) 326 0 R (subsection.9.3.5) 330 0 R (subsection.9.3.6) 334 0 R (subsection.9.3.7) 338 0 R (subsection.9.3.8) 342 0 R (subsection.9.4.1) 350 0 R (subsection.9.4.2) 354 0 R (subsection.9.4.3) 358 0 R (subsection.9.5.1) 366 0 R (subsection.9.5.2) 370 0 R (subsection.9.6.1) 378 0 R (subsection.9.6.2) 382 0 R (subsection.9.6.3) 386 0 R (subsubsection.10.6.5.1) 450 0 R (subsubsection.10.6.5.2) 454 0 R (subsubsection.15.5.3.1) 758 0 R (subsubsection.15.5.3.2) 762 0 R (subsubsection.15.5.3.3) 766 0 R (subsubsection.15.5.3.4) 770 0 R (subsubsection.15.5.3.5) 774 0 R (subsubsection.15.5.3.6) 778 0 R (subsubsection.15.5.3.7) 782 0 R (subsubsection.15.5.3.8) 786 0 R (subsubsection.16.1.1.1) 810 0 R (subsubsection.16.1.1.2) 814 0 R (subsubsection.17.1.2.1) 846 0 R (subsubsection.17.1.3.1) 854 0 R (subsubsection.18.1.1.1) 886 0 R (subsubsection.18.1.1.2) 890 0 R (subsubsection.18.1.1.3) 894 0 R (subsubsection.18.1.1.4) 898 0 R (subsubsection.18.1.2.1) 906 0 R (subsubsection.18.1.2.2) 910 0 R (subsubsection.18.1.2.3) 914 0 R (subsubsection.18.1.4.1) 926 0 R (subsubsection.18.1.4.2) 930 0 R (subsubsection.18.1.4.3) 934 0 R (subsubsection.18.1.4.4) 938 0 R (subsubsection.18.4.1.1) 958 0 R (subsubsection.2.2.1.1) 58 0 R (subsubsection.20.1.2.1) 1018 0 R (subsubsection.20.1.2.2) 1022 0 R (subsubsection.20.1.2.3) 1026 0 R (subsubsection.20.1.2.4) 1030 0 R (subsubsection.30.1.2.1) 1318 0 R (subsubsection.30.1.2.2) 1322 0 R (subsubsection.30.4.1.1) 1342 0 R (subsubsection.30.4.1.2) 1346 0 R (subsubsection.31.1.1.1) 1374 0 R (subsubsection.31.1.1.2) 1378 0 R (subsubsection.31.1.1.3) 1382 0 R (subsubsection.31.1.1.4) 1386 0 R (subsubsection.31.1.1.5) 1390 0 R (subsubsection.4.1.3.1) 126 0 R (subsubsection.4.1.3.2) 130 0 R (subsubsection.4.1.4.1) 138 0 R (subsubsection.9.6.3.1) 390 0 R (table.21.1) 3225 0 R (table.31.1) 3588 0 R (table.31.2) 3596 0 R (troubleshooting) 3384 0 R (type) 2173 0 R (unicode) 3324 0 R (unix-permissions) 2589 0 R (winbind) 2226 0 R (winbind-solaris9) 2945 0 R]
-/Limits [(ADS) (winbind-solaris9)]
->> endobj
-3772 0 obj <<
-/Kids [3771 0 R]
->> endobj
-3773 0 obj <<
-/Dests 3772 0 R
->> endobj
-3774 0 obj <<
-/Type /Catalog
-/Pages 3769 0 R
-/Outlines 3770 0 R
-/Names 3773 0 R
-/PageMode /UseOutlines /URI<</Base()>> /ViewerPreferences<<>>
-/OpenAction 1609 0 R
-/PTEX.Fullbanner (This is pdfTeX, Version 3.14159-1.10a)
->> endobj
-3775 0 obj <<
-/Producer (pdfTeX-1.10a)
-/Author()/Title()/Subject()/Creator(LaTeX with hyperref package)/Producer(pdfTeX-1.10a)/Keywords()
-/Creator (TeX)
-/CreationDate (D:20030501010500)
->> endobj
+`FeotO=Az^"}<e|;AIge |9 cS3"hYvaPOjFnKqO
+ñu‰Ø÷º7Ö0¢–P/6e UM,Or{1)>(os(tT[o{oN>=8{i
+'7wqMe2d@?pQc`kXP7MzMvuvw~W]qy)endstream
+endobj
+1771 0 obj<</Type/Page/Parent 1476 0 R/Contents 1772 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+1772 0 obj<</Filter/FlateDecode/Length 1432 >>stream
+xV]o6}S
+N6k`-J$6]KuAs9\~9?SdMh>d __ NS%<x:fZUkquMg7Z<Uu/4_>y6.gX4vk}zsNizsvxsn=n>PT(RVT)T55pUdn[y7vhK;i;*&elT)4*0|UQm
+k4rd]M%4՚rÌÒ;Ýk'Ç1œhHQ'M) 6pj{Z2;P, &S9|U){Z>j 2:kFwX zXZl0WR|8 -p _PG/V^QD;$6>7`ESlJ@,Rg#U)frK(Ad 2""W>wxEENZON T2:]L^D=N?J iG
+c[@I03NC DBK>]$+)S_0Lq
+g\VaJjx1Kuv``
+r!9*\J c` K1n1C1sSx/wqB?!a @G =qmËW7Hx:$dSWl(gq ( {q{jo>_\gW3\qy'|'t $endstream
+endobj
+1773 0 obj<</Type/Page/Parent 1476 0 R/Contents 1774 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+1774 0 obj<</Filter/FlateDecode/Length 1324 >>stream
+xVMo6W |is!An(
+BIDjE*ME$q7*)~bZhFSZhFH6Z\z1_..7hurs~{9P6kfD)mm,gQg'KBjr$[K2eHt%4@9VU
+tOr$\fjJxhISiAF
+'
+Üé}'öÝõp7hµ\B;]¥Á µ’ûØ©h-Л–Ñ‹²4)h£JV9[%7H4{`1Ll-"$^RMsdh\[*RK/+F8*"mv-B{KYs A ~Poj
+B)4aa -xU" QkY|BGC J*R~5(-:@-OOI"y{8]]%Dhz7zq
+F9N~1;*b.A
+t'FYe .dQsb]Ggpü«ZgI!U)]#
+Fu*}I*´èe§q `×òoÇ0­~S`/>[lJ!xßU8y/
+{fNmXe>o~2i{ 9p`s!-V3Qx/b>
+endobj
+1775 0 obj<</Type/Page/Parent 1476 0 R/Contents 1776 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+1776 0 obj<</Filter/FlateDecode/Length 1474 >>stream
+xV]sF}KXA1LLZfM<"`cIMsw9 .4S>_1&<6/a0:~!:y ROB~t&2]4Spm#
+q-%wR
+6N&b/8di7+2 .vqu;I bx0p<[JxW9dijtNae96h-c9
+kr*K ûádl÷á˜ÖÂÊäó[ª%Ðö‰SO\{"hEu%oeWU&Y76k ZF+GH=slMzHA"(6vwPhjbXQ6[G"2+t8ŽÈÀƒË–7ñþŸž+™?Crm9F-Jrg< 6#T.z]`iiDzegzG*:B X'.Oj動…Xgl=|Rl.}U,LU&JZe
+^Gd| |jd4^jE^%TEk9(Ue 1Bkt\qS&UJJ:t$:n& YR[V
+4T9l!CV?>nZ=yQ2y^=<d5m1#F7Hn28A
+bZqyfTWt-SQe>5wTkBJC`"BxU4[91m}ö1¥7j'™“kµéˆÊ“‹G7
+Lz{5cq ]?%nK>tWk78Q`A44' ;Tl^
+7Q\@:$FGn<-j^~x$9O@8P"KY$`zylA&J= m=XR2U<7u T[#/M@6Du|<C;J)TgCsl <2{\F[L
+Jl>N3SXVbHh\/A<oJYM/1|q@[7;`(fL8VCdh
+ ]F<\o'osMDj7wp
+51} \o=#}9pÃ}-9 âïøú|Ol}(q|N*xa $]gZ:Xf92H wrs=?9+^8zNS[p'6<|L-qs·RY8ugýK>y4AOzqqendstream
+endobj
+1777 0 obj<</Type/Page/Parent 1476 0 R/Contents 1778 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F8 10 0 R>>/XObject<<>>>>>>endobj
+1778 0 obj<</Filter/FlateDecode/Length 888 >>stream
+xmUMSHWBjc1lr
+5KB/.mJzid~:G1MI2sS5uT$lJY E
+'%.'?X~<m{eASkgBM(c-(* `^e5WMVjNi38 ê«mY.t5Y9%
+aP}r!~D9yf?'rL~||I} lcF}úÞp`j&
+ „0M'xS
+ 8c4V|)Oi7%s\MJz:|7 D6/kQ^$}e&W Q%R,~endstream
+endobj
+1779 0 obj<</Type/Page/Parent 1476 0 R/Contents 1780 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text/ImageB/ImageC/ImageI]/Font<</F0 3 0 R/F4 6 0 R/F8 10 0 R/F9 11 0 R/Fc 14 0 R>>/XObject<</I15 15 0 R>>>>>>endobj
+1780 0 obj<</Filter/FlateDecode/Length 1459 >>stream
+xW]s6|)YyKe;$NjPH0}
+[ó6shkJ*eWI9<!HIn-IQD&SgxW.DFie+MRK$,ll]^51<A[cjXQaHr] w&S%~@ 9j
+ZjSæŸ!2ÿÀº怍¶W%&w|#Hd6WF
+j *Zw
+7R
+l8TnEX dE2X8UkpxFOmQr+q#I^
+]_mR*iO\\2Sw6i17m{[ZH['y)7,L` 
+C]A^}qSD
+|oGLyP-Gkw5`q2j L,0
+vk`RNh:kN)^X.(i
+Ì·$ò“ip9{ ©sXFo<C]`4x0y\l:;h>5)T\Hny,{u.# OK&sy=“ \åkÌ-x‹à¼'·[֕E_mvcG_-tL<?,%C-bumm2e,[kt"Iw|#BG"I<Bi'uw|VpoYy0F1 43B9Nq?Nt>h[<;D+7@%tpqt7¡bÍ7Dvf?[O;m;E _'y0:p:>tendstream
+endobj
+1781 0 obj<</Type/Page/Parent 1476 0 R/Contents 1782 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text/ImageB/ImageC/ImageI]/Font<</F0 3 0 R/F4 6 0 R/F8 10 0 R/F9 11 0 R/Fc 14 0 R>>/XObject<</I15 15 0 R>>>>>>endobj
+1782 0 obj<</Filter/FlateDecode/Length 1532 >>stream
+xW]oJ}T¤o4IoQBVT-f7K=kmnu[EM;gOzAw ?9R8z^g/J g~ <!J> Np
+h,$EI7H:[}}w qHU.HHr2kI%mUa*+t,r$ fAF
+$DRUE Z`K[JU`7Gd]CTU $%+__o~O 3._##\YRD"C &szn–âµÈWR21[,Uv-%'$r8JYW:_m\Y(\FYxvK@aHHAI[:2}'g<$# i&KP}Ub<)swjYK*3aP°Í:+å*Ѽ¯ò<1KH.?}=_On.hv.|iji)(:J0 )u9^sm.3GCC$89>` |Li
+V 
+r@/baD6g<sT-e,1nDno[&=T&I
+/zM\s,[kuZD9J o"de $f$Z^<Bb'i[
+ D;>yAueu sp[tK_^g+cP*,7!W4W%;EY2k_
+C)HH$q<h52w
+endobj
+1783 0 obj<</Type/Page/Parent 1476 0 R/Contents 1784 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text/ImageB/ImageC/ImageI]/Font<</F0 3 0 R/F4 6 0 R/F8 10 0 R/Fc 14 0 R>>/XObject<</I15 15 0 R/I15 15 0 R>>>>>>endobj
+1784 0 obj<</Filter/FlateDecode/Length 1175 >>stream
+xV]oH}W\l*jjw%^&ggsBtUAuOH1%E 0P<}~yz`XQ0dJIsz=0)xOh"m6'IY\Dhz$SLJF!`jnXr{'R/AGt*K<?>dTg) [p$z8,Rw^8@%k?JJzeC. F0%
+2Jd2y$-7HTtc;ZoQ++'HZ 8.NtMIS#II 8]B&WiTL>Q`w/LJ|aRR8eb1M u?evmb 1] :w
+#75q6|4ADj
+;oI3_zhE=<O &5iQ:OYrF0}v$DJ;g^p{@P37%Er6/02[[tJ<loNRM^e4ri*th~8x5O
+endobj
+1785 0 obj<</Type/Page/Parent 1476 0 R/Contents 1786 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+1786 0 obj<</Filter/FlateDecode/Length 1470 >>stream
+xWMo7½ûWMI"9rH04)
+BRZ\rKr-pW- ;~pffEA3,zAU{1rZf%~^.(b:?~uq 3ZmdUM0FuI*)mNkr],Ws_bJ._U2GTUc"94T$]SrzVQx2ITyqxA92mCR.Q46qJFs*s~m|h'vrD:ktF2.&e<G_qj|LF5uU>VYLRaDAqhjo-!hjM{`Ir:|=zzuJw[R.iV+$`6BNCdx N>$RmB=7I
+ NU:3H F=ZBYvlF: |xfG1,q 3sh
+
+ @
+ 8[0;r`k %ygUWV~~@Sa@[=RWe3O >u/s%3_?/Aendstream
+endobj
+1787 0 obj<</Type/Page/Parent 1476 0 R/Contents 1788 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+1788 0 obj<</Filter/FlateDecode/Length 1162 >>stream
+xVn8+@S -]b0]MgASF"5$sI~DqoV$4b|~]|P,ljhqNyN,+)mlG
+A=u- izQ*ebQ`J<<0%}Hucs)7o)YVM+Ld9UrRb!|" @l}[6M#eK4Q=!&s []0 U$zH[g
+endobj
+1789 0 obj<</Type/Page/Parent 1476 0 R/Contents 1790 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F5 7 0 R/F6 8 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>/Annots 1036 0 R>>endobj
+1790 0 obj<</Filter/FlateDecode/Length 1337 >>stream
+xVn6}W emQv_hHV I@$phs33Ñ?#Zi2 !V>xFl9=~\K.<o%i{ xH-BKZf$^VV4*#Zdq:QL@$'R%?S"[]5BJtQva%eT]l"+>S9m$J(LJV-U%MUV{t=xwX^&vx8"TR4w@(rEAuDX_]|PmdMU8FPLHHb, |/zFB #(c'#mu E&
+\_D)|Qd}P,l|cNlvp2 Q!UJ`e); |Dnt .K]YOP-M { J+,HW+OQ4#t Jq)EAfG#AUi>MZt\p.xad6)5YD9H3Hz0"c,
+endobj
+1791 0 obj<</Type/Page/Parent 1476 0 R/Contents 1792 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F6 8 0 R/F7 9 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>/Annots 1084 0 R>>endobj
+1792 0 obj<</Filter/FlateDecode/Length 2554 >>stream
+x}nH~ut"JL L=m3lh9H5IS"P2y*]n-nE3~38.OQ.vjf.O([7[!w8\p]<G C*G59= .a0NpCZ \O&XD+7W jj#Hc1HYa9Kf 5dvLU z $ px;'!'?E> A`h,b%)IE*J yJ,\2Ha+Ma5$3i6`BXaWS5x$D Z KkYY]MvHG,] *X cgaAGQj= kP_j}GYa X_AZY5 xfY. k1,vfFb<gR!3DZ`jtlXO4[,&8)[>f"_aiDXa K-T!^MZ V v-
+,`U2l0yNeYaxbbX y0 ]W5XY0.v? l5X*XU`
+eRk0y++k(FYF,GV`-E3e-eX,</dFY=2]<41R4`%Jem EDfKXai$T(k1lJ`)F_0,^)R eiU` eiR 9l0^qHPQbD3 P dWZf Fb\.JWr]Fs"#_a%U0UdE} nGys jRY;Z K,c@]#Ul0fim(
+E "#:b.*Xae ]Yi](M|@6R9E= w.I4v)H2 V5ATz)CTgy O&:U,=`Y5Yn5XQNxLr{
+z10l.-kaet cnYax v-=16>\(mu':Wp,B'-`jj3J&
+$PjFbT:Z,Fh4 PmLGZYC=0 5s+V 4+R`4nFbWnZ5 A`XVYp6@Vt|aPH=9 (3 $ z
+7) *zT0@0ym,9` j 1O)JHLabS:T e ]dS0Ors
+_Gj~zWJc0l{UCr&Ub]}=;v^~OL d|svnHM=Hr5\dm`Rq'}~U7`)gOgvl s^I"YuZ?kvUS~rc#z9C4d%jVh]C5~Rw52zgOUlBmgt/=s]_mj6]].:|m#1Vb8]·~.ê§ò²“X, "h<<$S?X d$SpuS3gV?!xx3{p_u$}od\z.4]slQn6Z=x(fHE5#<c/m^  2;V]Umwd9IY[}1b3]6lU&s<Au3bN(>oo& u!;!;>]NL$>/]CeOnW~-w Q` `mg5 k=
+endobj
+1793 0 obj<</Type/Page/Parent 1476 0 R/Contents 1794 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F6 8 0 R/F8 10 0 R>>/XObject<<>>>>/Annots 1092 0 R>>endobj
+1794 0 obj<</Filter/FlateDecode/Length 375 >>stream
+xm]O0+^P~@J=#cCi,<i{M80|8RCq 2:= O5IJNuJkR4#q!%@;ffR4#ew;f@+
+endobj
+1795 0 obj<</Type/Page/Parent 1476 0 R/Contents 1796 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+1796 0 obj<</Filter/FlateDecode/Length 1453 >>stream
+x}Vao6_q>V>uIXq° óPesH)E
+Mxz @z{SF:}m1|S+!f+(QB?
+9E Ls>bGK;
+Oe R}gQfe*Q%*yi$QS}wg`bG5BvyLmeV69?K!gl\ j1~P|`iEA`L 0`@!$-S
+8Bxz.DEp ( fE,z
+endobj
+1797 0 obj<</Type/Page/Parent 1476 0 R/Contents 1798 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F5 7 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+1798 0 obj<</Filter/FlateDecode/Length 893 >>stream
+xV]o6}H"C[?l@ E$U~:ylK+}eh1YN .INS|2zt!kZ@8)(iJk>S* ]?Rdil ϯ 6œ»`½0xª#
+8™ÎQ$l$~y(-^|Gz`j=;Y^b3+`^H5pG{5M9Qo\8j:VNK3sBhikyriTA[kG]H"4z/11]`kHZ Q7
+U!qupOJjH{i42Z=z=8 eK?%;TIL:|K7R-/1C M~YhppGVF
+HldRa7uh?uZhXi'} }XQK5S
+endobj
+1799 0 obj<</Type/Page/Parent 1476 0 R/Contents 1800 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+1800 0 obj<</Filter/FlateDecode/Length 255 >>stream
+xm1o0w~)S:1d$J+u6:`RG`M$wp:F8LC9nthI9LC]sSbC` 0p23BN.pFER:rp_iVnCW%77`ba_Ù¶ýfKd+Fjhi;>9W`::L''?cendstream
+endobj
+1801 0 obj<</Type/Page/Parent 1476 0 R/Contents 1802 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F8 10 0 R/F9 11 0 R/Fc 14 0 R>>/XObject<<>>>>/Annots 1103 0 R>>endobj
+1802 0 obj<</Filter/FlateDecode/Length 1655 >>stream
+xWn7}÷W bV]Kav+44R. %1%^=C$[
+!A%93g=9:4RoHY~r7w<wR_`o'I2x)$fp9Fx`]>c~'X7wYw^?&iw }}39`8|Jvv%u D
+fAv5Q4=}t=8Z9[2kP T2SK2K[+kx:^?Uw@_%4_WKdY_M3Y>#Lh-kj=VwrK^:OXq>)GAsn0r-E *su (W$M2fmw6/
+
+}J7
+`Rt$[ ªqÉDiu\R=?Zjz
+Xr5,ì j"ÿ–CB|tY|etzyKRo"YZd >v#ow#l=zhOaXZZq9e(A%ÄÊåõ‡éO M
+"M@#(HuA6%S{bGöUf&s (c i!]V
+C <d<etÝdA14Hn"{9pkz$`~Z*"vBd mFuB) mEkE+=}o4Ynzv$S& %F2Wj\q?|xb0!zZ s
+%]1tKW47zS0E
+o}8}g&|e8F ' >endstream
+endobj
+1803 0 obj<</Type/Page/Parent 1476 0 R/Contents 1804 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F5 7 0 R/F8 10 0 R/F9 11 0 R/Fa 12 0 R>>/XObject<<>>>>/Annots 1112 0 R>>endobj
+1804 0 obj<</Filter/FlateDecode/Length 1609 >>stream
+xWo6~_qR,GIk0,@KV"5QbE=iU[$^LtpBiˆÞ<?îá74I&xE4%1y^M&xg5"`=8{qgt(Nhtr xt'xgIo)~yI_{ ^tuJf ;98Yz~YS*5]Sj"_
+JMECoFjT5IRzSJ7M/\4(S2htc#oF0}s~+>NH^W;bk+')tS(BRjjy- 5JFhc6(H|"Z$6vO*OD^(z|O0^4{~F:L!p{-slJMgen}:tec$X'YP_UyUf
+iSu{_c44W T*Xdt)3&09H6S^&rVOP\`.A3q{;5Z vDD:m
+<F#0VYZuxB\8Z@g{&@y3t}}fsWu6k>ieC-@lGo=y%t?*>M$YWsvysTP\OB5$!! <B6BORp]c
+TiYT6MFjZ.E{RB)>7
+~> 5-83&07c@rSZ+VHOtEv[WDao3eX{1/ &d*t4@B6SKV@ÄÔù2ײxnÎqßé™/°”ÑAlBUm0F1 ^y:u/='$)Vwa&[>UB !y}B#L3]w\pgpd+K've§{DHH u0E6L;rx8yu 2^x7hX>HT{a^+fCVIAuEs!CYUF~S&ofj/@m
+endobj
+1805 0 obj<</Type/Page/Parent 1476 0 R/Contents 1806 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F5 7 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>/Annots 1115 0 R>>endobj
+1806 0 obj<</Filter/FlateDecode/Length 1632 >>stream
+xWn8}W R/K
+Cb;Ej,(H+Rq{D#\:R4QDaz:4w0b1GýÁäà ÷:ÕÏד.7yJy*õ±÷êîx⍚WIz@.1MGNeo%I'()(6yG;FF$2RYTfV$T6$YMv+U^+/3r,s[+Qq4w4"Y%1;2Ja^3BfiUi Qa;k<"-H2 0EhS <J[h sH/i )/SzG ww *)bu?no*b{3ZC/|=WH\?\NaZBdQC.. "~Lro!^Dr[NyDVd—¨·X;1ZxH#.(~nHF^]Te)']4sLP_H#2"fD6 H# 07@(R %<S$ YDta)]q
+!abPD@_6nl% g$DC`P;RY7;XB*ob(3hD0(DR-oBs:M[*~pdG- *s
+bA"D
+gSWx[8 y&aqm9ug`Z]xKzL.a*Q1;OWwW1aoY|o?w.1 F*'c;O:+$endstream
+endobj
+1807 0 obj<</Type/Page/Parent 1476 0 R/Contents 1808 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F5 7 0 R/F6 8 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>/Annots 1118 0 R>>endobj
+1808 0 obj<</Filter/FlateDecode/Length 1413 >>stream
+xVr6}WEInLn=
+YD| 1pks^^g8VIcGzOi7J5{cI5,Z
+I!m#\25MEmLE{Jr%;z6MIw3&:)UV&\MnSB:iD T"tC2mHi]Z6'-]3un mWi x368uM<XGÑJ${" CKpQmYYkA5Ud2B%9]IT5 <4AkQQKqQ&SV1%@Jxmh|LqR;')]c `SABKdT =?.ZSNHmY[%=L8f $@e,[/_W}DRm C'2%.l{8sLj#JySD\=hyz0 d< K*
+JZ5(eG sy`T\P^E"Q#gFt{}WR+w~`-[FtSi6R<8^$L.~N>afcuzy%I5{I*<@Z+I0}{xzy
+O]Cr|mUZA&^xw:IHP$Lpe<!Y A11<#Eb"q</WA*R
+b0X41lBlpV/ >Z=4agiAZ(~meugzX.lj-l2'74J>( H_?@aQuxICKd=^]a8T{x5 %/&ujqn¨>9&@_v8<
+ <M#i #K7;-3g4:qUmIv > 1';#W_l?2 t} Rendstream
+endobj
+1809 0 obj<</Type/Page/Parent 1476 0 R/Contents 1810 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F5 7 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>/Annots 1127 0 R>>endobj
+1810 0 obj<</Filter/FlateDecode/Length 1507 >>stream
+xW]o6}KS V,q<-n@Wlb@_hXKFRw.)bC$2u9^IL3nN%dwxfZ54W{*q2|"Z NV[X.w{Mw1^\nf2'vfu>1fV d51á©w7_¯£ÕØjoðeÜg1gÇá‰Í^o'7oáuF M=6&zIC_uKNSZ~j K`?~^JDEz(wnLt.rgmuo"(GY4VN14^pnB HPcU'cOUt7u.
+XLU%7
+tF;#*8$B@gTT:a`%*L4PHYs^TTe#Hg^KOgRr/¿H}&9(wexyk-,ES<$Tx
+;C1FD$åfó}:Æ …Zj^k`M^Ca)}Sk\bF |\04e$Ctv9=+ b>Vvu4`\k>hgGSP&A_|-X$EG?-
+{J (=nt&~DW)`LM4ClJ_T4|
+)<QR(?<{u<&,shtAUG4#2SMr JG8jsnsF"*xf/%5)—}Ixy1rN.HenCa5  Efp9j9|tz ?QFQrIrn" ? Qew9K%[DDkFeTV>|wnW}
+5ch||v0)a-Gh[}[r?}b.t~K {mvsawl'NH3endstream
+endobj
+1811 0 obj<</Type/Page/Parent 1476 0 R/Contents 1812 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F1 4 0 R/F4 6 0 R/F5 7 0 R/F8 10 0 R/F9 11 0 R/Fa 12 0 R>>/XObject<<>>>>/Annots 1132 0 R>>endobj
+1812 0 obj<</Filter/FlateDecode/Length 1290 >>stream
+xVM6:@%[-{&is(fDL$R!)oAHf*eS^P^-%WT~^iA-eE)3|En~v*[Zsgy|Uhqc}jbAYF)+T!m{Iy6uc+N;X+$,O0?yk{Ii[xz99#sDIE7 ?;nEjf5 &g6{A5 V
+/B,G*E*-JB ;?9$Too]$n
+]<M)QJ¸5øËuFW r!Vy.u? ` M[IfHòˆÈˆ±BXMe:f. -2FSN?4t0eb<fj(=-9gQ0o. 3lp.#oh i2/
+2 RYJ7 <}+y =3$?vz ;QgN>jj 
+bitio',ckz7i2Epv2:M%0±"hÜ£æ„+)Ý#r®zÜޛVa3_d !kr F<6 T
+endobj
+1813 0 obj<</Type/Page/Parent 1476 0 R/Contents 1814 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F1 4 0 R/F4 6 0 R/F5 7 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+1814 0 obj<</Filter/FlateDecode/Length 1462 >>stream
+xWOH_1>\#v@zZJ=N*6lw5! r 7oL~d4oF)dB'Yxz_rA`g2U>_P$]ZHRyQUqwnsx %J"kk+
+45V*:)t%7juT)xnF~#TE2q6KOVIG[UU@FZ7}!;/5N+kCkS6$H6#y+ DT@jB9oSPDxv$t5'uA4<vE2gu1.j[:I
+ &#N qD4}x;t
+yj2bLY2d@0By
+~di<Zq6LEBhIJ$$Xoq["sZ7D!xc #_996 !1Ia+LVhYy7'Sy
+.!(Z7vNSBcalE6 jRsP~/0Hq}Q 5"G08;Lc4øy(!4,oP@xAR:M| /}u&XK0R%2PCapun
+9l¡ 4ì;ºB:$*V]dWo=mjYCv(>deV =0i_M#e<yP Hg\CuHq10cX jdJ4dI;,=,H0B7M'Wc>iJ^=T7yb=-rEyf+‡±¶F9v9<V5`>7"Y%@=G T-Ne.<_.\70=;;|DK~)`cYYv a6AxF|{yLy_/&bxL'%gl.endstream
+endobj
+1815 0 obj<</Type/Page/Parent 1476 0 R/Contents 1816 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F5 7 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+1816 0 obj<</Filter/FlateDecode/Length 804 >>stream
+xUMO1½çW J3,ˆ~ ¶­ztœ kðÚ[Û äßwloÄZ$=3y3=!wv%Ty0_sAeU&z~CC\P,O~\]|DOpz%Vrs0{a-:4\u2:B![*HC)V jH fyIE,lt\z`; b;'4][T6r#:Zw*;6@ QE?)N0$}4p[ {5)H 3R{}.LOT-B F; wBJ,<Idq9Qyd&E'x P7V [ FI
+oic@ECt|my sHGCo&5wH 7!>I$p79@9q1af/]
+'ydi\&K0" b<+ te$ -%pl)i
+?V7k/EN M?t)??4KkwAxjxzM)q W+n@.&M[b*c B`^R[(pcQ3EjZ hW |dm'gA{vUCAC`M
+rPcbgyE‹Êrs}r~z—F"wpyX4qgaFv ERG(8
+C=6;endstream
+endobj
+1817 0 obj<</Type/Page/Parent 1476 0 R/Contents 1818 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F5 7 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>/Annots 1141 0 R>>endobj
+1818 0 obj<</Filter/FlateDecode/Length 1661 >>stream
+x}W]6|X(z. hI M BK+9JTI|%%O Cf7-7Y66fTrO*[ffx9ndhlM*bfX+D]mop-!S9
+QVs}inX--f+fK"'j;Zd[n;q&|P
+Cg.6i~(ldbZiC({OuHIJ>a<2<{Yw9:O
+*p^5:W"h? [ S
+<
+IAW9pi@=Mzd #$)`zNHJ5y+p9{>/\TX ^wy%CvM)VlZ
+Nw|lU3$%M$rB 6p1%[RttoM'^xRMA\3GZ8OJ. O`rk{p?6Z)DS)J*sG
+~:3u
+gc[v%K1^\H2 cr
+XNj($
+en6k 6gSGLBDvh>GnCa!4g-c~{T@HSCxy 6RL[ Ax+}A| ~lee
+F/x!hzJ{j4bY0EFa N?oo%.[hFuV!s'Zt pt<k,r lLx~D;:j\17USbF0a\^
+XZvbDI5tj&MW0
+B3h²P%^-j} `q?\4s-qXX%Ir#*H%þyH^a H~WG`6bq@
+l `+GB\ q
+oXendstream
+endobj
+1819 0 obj<</Type/Page/Parent 1476 0 R/Contents 1820 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F5 7 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+1820 0 obj<</Filter/FlateDecode/Length 1667 >>stream
+xWn7½û+¦ºTbYe)&M@
+BVV8=9]8|bZk;+G&we8&R8^"w&R<8o"MZSB7)tT*ZEvD]qmD1w|IT)Rq
+T@7{H*X|Jcu"vNFsA+
+äŠþ¾}øNVJ 7SPII-wi2.-IW])K:,Zi$I//7#u
+A!t!Ht3
+Jo~<nk0BD >S6PF+u`bbg_1æœ`›Ãã¸qà¡´ow­v"|ß
+  Ht)2iwW= b)X
+(:+c4U*82
+>^:=&DUCkLEC11jP;@.)}
+Si[X?aG02y
+­·Âö>Qf$tm$(] VFF
+r[8!19a#mq8 _+{>u9;WzW`_q8
+endobj
+1821 0 obj<</Type/Page/Parent 1476 0 R/Contents 1822 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+1822 0 obj<</Filter/FlateDecode/Length 1324 >>stream
+xVn6}W .k ^' 4 >p%bM*)y3 [3hJLlFSJI4EtN3=$u0?N?&G M(/U!FZG(wBOZO}zdFk6mtvl`QTP#ALNti)zZe|f)i9iEvhAZ=I}\&t2dS:feIHJQT]#kXIiQp/v+v@{cT8H!Woh|C0(3xHU?c3tV*
+VAJy5-
+Td4] G*jSZ5
+V.V0o@ s^@Q(7Q%_px# a6{0ZP;tU.<wBXrx&^7Et-k?ys J2(mBfWZSzut,nMB;f5mM*N>=lwnJztdU.~^T/W< >`/F&Gch07joeEe CNI-c_.zIZNFSY ~l9Z)`6 IW1-@x<b>2;7|^Q:YEoa[n>Nº^_Óf›Ðê·uœÐzCXGoJt$6 @
+BXjqR9a |>ti0{%<uR4SAc+TZ.Ss#<BH=~_l@N
+1xL
+endobj
+1823 0 obj<</Type/Page/Parent 1476 0 R/Contents 1824 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+1824 0 obj<</Filter/FlateDecode/Length 1623 >>stream
+xW[OH~WeAh>
+4=Jg)-thh4ZjrW}.}-ZF^ enUIkpt;O`Te
+V[iqq{xuKZDg^MQU_t6O×ðBj]P3|CZUQz@A%X!MAu Tt
+'L3{BIG'#g'
+endobj
+1825 0 obj<</Type/Page/Parent 1476 0 R/Contents 1826 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F5 7 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+1826 0 obj<</Filter/FlateDecode/Length 1405 >>stream
+xV]OH}W"&_oRfZi%$4IH]ZTAbs9~;Ft>` ?s9#_Ld(,?LN?Mi4Dx84?^UPFJ%C61XR*YHWo6R/d`lW$,&C&(-lwzitCF~@%j,-6<*?L-Td3/\d@T+Hr@%Z;4uF8b E[t$"kmjAEZ*;dG> dx S#tgF"qHk{X:A\#s—в–Ì=.®Χ@| :iJKY"F]CU_PRp~! #-*i*.h@(`;'dP*4<JI}|eqk5 .~rx#[.hy @$BsbJYi!LOnTe
+-O
+:CN
+vNP_,}rzz:4?Oh6:9 Z}y[<lC_q~:=dZendstream
+endobj
+1827 0 obj<</Type/Page/Parent 1476 0 R/Contents 1828 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F4 6 0 R/F5 7 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>>>endobj
+1828 0 obj<</Filter/FlateDecode/Length 1711 >>stream
+x}Wo6 ` v$[tmd
+ä -Q‰TI#)Yv%XxN;9-(NN'tv>,|ysYI+]+%>dtrBw5t;NlN8=jj
+I*p"Vinh:>|}9477+L[flOJRmMU72XT f,?l20IMwLijZK^[ieibB?'
+R5QF*#-ð„ýêsÂLPI)wda!&$:rzA^*P 4F XDf:y\#jÊT@/k7 H75lB|
+ #H.«uk…o À¦t/³=¨P6u4U}
+}!OFZ+T)7L%j]'i]X]gxJ[KsB\t,1U~9\N.V&+
+Y6Z|,v6bJWkl2<^DAo(cS"RPVs"'i7OB<>Yc?_q.d_~ED=\P'({l[UP3 C$$cz.%8aƒ·
+3f{€0—v%@gcXPY>HtW??Ph(Sf
+f-+hp'Sd+d60e5 o4 W LY Y k
+*
+'3G=PFB|
+M!$B Eb*J|;(5a_~qQqz vC/`Ux c^ _-js(P4v;}O?.{l-.tn^&m+X<><}W'/dq1álá‡å‡»“¿Nendstream
+endobj
+1829 0 obj<</Type/Page/Parent 1476 0 R/Contents 1830 0 R/MediaBox[0 0 595 792]/Resources<</ProcSet[/PDF/Text]/Font<</F0 3 0 R/F4 6 0 R/F5 7 0 R/F8 10 0 R/F9 11 0 R>>/XObject<<>>>>/Annots 1146 0 R>>endobj
+1830 0 obj<</Filter/FlateDecode/Length 1576 >>stream
+xWnF}WLiQ)9:mk+ VRbB\gfí^DH3BoH!"A0hCO'_)i0}h<}0+'`5GgC,(La(B8QLojLaHD A,/](rDb+Z8®™]¿#]ÇÁÓÛ·³¯À<ƒ óx¸Li0
+iWmgxz)EL:mP4}OO!d?mCni<EYDPT*VJWe@C XTka\3kX;6yQKdlgr6W
+De&U:_H.l1+Iv<ITo'oJ$UF!D8-(fEcOZ'058 9Ku.RI8t F?FI*2')U8S@q'J4>w=FE'@:l m5v'ZkuI\iM}K D.u"UoiJiYY8Pkd7P+d_l8 ,#
+lHq$z7
+/zOvw,<DRM e5U ~-]BgQyU' <[S-.g|>0Qx qsITQsNgph"hK-H^A.|PF+Hl Rr[@L R ?+THme]<cVkR Wgy.`_ldWZ o)2
+;
+v_^rYTCKeJM9;Sh8 m3B)-m0r0x@ZG-*(gW; !ZUfK{2P$H8Xlg4F&RYA%o) _Az^tpDx;M\d+G=BESWPND5.ðlÝ1[5Æ0¯Ðw3±îÉ Š4Ž쒾í^a
+ŽßC
+endobj
+1831 0 obj<</Count 38/First 1832 0 R/Last 2109 0 R>>endobj
+1832 0 obj<</Parent 1831 0 R/Title(Table of Contents)/Dest[1479 0 R/XYZ 0 756 0]/Next 1833 0 R>>endobj
+1833 0 obj<</Parent 1831 0 R/Count -1/First 1834 0 R/Last 1834 0 R/Title(SAMBA Project Documentation)/Dest[1493 0 R/XYZ 0 786 0]/Prev 1832 0 R/Next 1835 0 R>>endobj
+1834 0 obj<</Parent 1833 0 R/Title(SAMBA Team)/Dest[1493 0 R/XYZ 0 762 0]>>endobj
+1835 0 obj<</Parent 1831 0 R/Title(Abstract)/Dest[1495 0 R/XYZ 0 786 0]/Prev 1833 0 R/Next 1836 0 R>>endobj
+1836 0 obj<</Parent 1831 0 R/Title(I. General installation)/Dest[1503 0 R/XYZ 0 786 0]/Prev 1835 0 R/Next 1837 0 R>>endobj
+1837 0 obj<</Parent 1831 0 R/Title(Introduction)/Dest[1505 0 R/XYZ 0 786 0]/Prev 1836 0 R/Next 1838 0 R>>endobj
+1838 0 obj<</Parent 1831 0 R/Count -6/First 1839 0 R/Last 1846 0 R/Title(Chapter 1. How to Install and Test SAMBA)/Dest[1509 0 R/XYZ 0 786 0]/Prev 1837 0 R/Next 1849 0 R>>endobj
+1839 0 obj<</Parent 1838 0 R/Title(1.1. Obtaining and installing samba)/Dest[1509 0 R/XYZ 0 762 0]/Next 1840 0 R>>endobj
+1840 0 obj<</Parent 1838 0 R/Count -2/First 1841 0 R/Last 1842 0 R/Title(1.2. Configuring samba)/Dest[1509 0 R/XYZ 0 647 0]/Prev 1839 0 R/Next 1843 0 R>>endobj
+1841 0 obj<</Parent 1840 0 R/Title(1.2.1. Editing the smb.conf file)/Dest[1509 0 R/XYZ 0 559 0]/Next 1842 0 R>>endobj
+1842 0 obj<</Parent 1840 0 R/Title(1.2.2. SWAT)/Dest[1511 0 R/XYZ 0 758 0]/Prev 1841 0 R>>endobj
+1843 0 obj<</Parent 1838 0 R/Title(1.3. Try listing the shares available on your server)/Dest[1511 0 R/XYZ 0 581 0]/Prev 1840 0 R/Next 1844 0 R>>endobj
+1844 0 obj<</Parent 1838 0 R/Title(1.4. Try connecting with the unix client)/Dest[1511 0 R/XYZ 0 413 0]/Prev 1843 0 R/Next 1845 0 R>>endobj
+1845 0 obj<</Parent 1838 0 R/Title(1.5. Try connecting from a DOS, WfWg, Win9x, WinNT, Win2k, OS/2, etc... client)/Dest[1511 0 R/XYZ 0 245 0]/Prev 1844 0 R/Next 1846 0 R>>endobj
+1846 0 obj<</Parent 1838 0 R/Count -2/First 1847 0 R/Last 1848 0 R/Title(1.6. What If Things Don't Work?)/Dest[1513 0 R/XYZ 0 705 0]/Prev 1845 0 R>>endobj
+1847 0 obj<</Parent 1846 0 R/Title(1.6.1. Scope IDs)/Dest[1513 0 R/XYZ 0 564 0]/Next 1848 0 R>>endobj
+1848 0 obj<</Parent 1846 0 R/Title(1.6.2. Locking)/Dest[1513 0 R/XYZ 0 479 0]/Prev 1847 0 R>>endobj
+1849 0 obj<</Parent 1831 0 R/Count -6/First 1850 0 R/Last 1855 0 R/Title(Chapter 2. Quick Cross Subnet Browsing / Cross Workgroup Browsing guide)/Dest[1517 0 R/XYZ 0 786 0]/Prev 1838 0 R/Next 1856 0 R>>endobj
+1850 0 obj<</Parent 1849 0 R/Title(2.1. Discussion)/Dest[1517 0 R/XYZ 0 617 0]/Next 1851 0 R>>endobj
+1851 0 obj<</Parent 1849 0 R/Title(2.2. Use of the "Remote Announce" parameter)/Dest[1519 0 R/XYZ 0 786 0]/Prev 1850 0 R/Next 1852 0 R>>endobj
+1852 0 obj<</Parent 1849 0 R/Title(2.3. Use of the "Remote Browse Sync" parameter)/Dest[1519 0 R/XYZ 0 465 0]/Prev 1851 0 R/Next 1853 0 R>>endobj
+1853 0 obj<</Parent 1849 0 R/Title(2.4. Use of WINS)/Dest[1519 0 R/XYZ 0 287 0]/Prev 1852 0 R/Next 1854 0 R>>endobj
+1854 0 obj<</Parent 1849 0 R/Title(2.5. Do NOT use more than one \(1\) protocol on MS Windows machines)/Dest[1521 0 R/XYZ 0 441 0]/Prev 1853 0 R/Next 1855 0 R>>endobj
+1855 0 obj<</Parent 1849 0 R/Title(2.6. Name Resolution Order)/Dest[1523 0 R/XYZ 0 758 0]/Prev 1854 0 R>>endobj
+1856 0 obj<</Parent 1831 0 R/Count -8/First 1857 0 R/Last 1880 0 R/Title(Chapter 3. User information database)/Dest[1525 0 R/XYZ 0 786 0]/Prev 1849 0 R/Next 1883 0 R>>endobj
+1857 0 obj<</Parent 1856 0 R/Title(3.1. Introduction)/Dest[1525 0 R/XYZ 0 762 0]/Next 1858 0 R>>endobj
+1858 0 obj<</Parent 1856 0 R/Count -2/First 1859 0 R/Last 1860 0 R/Title(3.2. Important Notes About Security)/Dest[1525 0 R/XYZ 0 502 0]/Prev 1857 0 R/Next 1861 0 R>>endobj
+1859 0 obj<</Parent 1858 0 R/Title(3.2.1. Advantages of SMB Encryption)/Dest[1527 0 R/XYZ 0 455 0]/Next 1860 0 R>>endobj
+1860 0 obj<</Parent 1858 0 R/Title(3.2.2. Advantages of non-encrypted passwords)/Dest[1527 0 R/XYZ 0 322 0]/Prev 1859 0 R>>endobj
+1861 0 obj<</Parent 1856 0 R/Title(3.3. The smbpasswd Command)/Dest[1527 0 R/XYZ 0 215 0]/Prev 1858 0 R/Next 1862 0 R>>endobj
+1862 0 obj<</Parent 1856 0 R/Title(3.4. Plain text)/Dest[1529 0 R/XYZ 0 415 0]/Prev 1861 0 R/Next 1863 0 R>>endobj
+1863 0 obj<</Parent 1856 0 R/Title(3.5. TDB)/Dest[1529 0 R/XYZ 0 326 0]/Prev 1862 0 R/Next 1864 0 R>>endobj
+1864 0 obj<</Parent 1856 0 R/Count -9/First 1865 0 R/Last 1873 0 R/Title(3.6. LDAP)/Dest[1529 0 R/XYZ 0 251 0]/Prev 1863 0 R/Next 1874 0 R>>endobj
+1865 0 obj<</Parent 1864 0 R/Title(3.6.1. Introduction)/Dest[1529 0 R/XYZ 0 231 0]/Next 1866 0 R>>endobj
+1866 0 obj<</Parent 1864 0 R/Title(3.6.2. Introduction)/Dest[1531 0 R/XYZ 0 626 0]/Prev 1865 0 R/Next 1867 0 R>>endobj
+1867 0 obj<</Parent 1864 0 R/Title(3.6.3. Supported LDAP Servers)/Dest[1533 0 R/XYZ 0 786 0]/Prev 1866 0 R/Next 1868 0 R>>endobj
+1868 0 obj<</Parent 1864 0 R/Title(3.6.4. Schema and Relationship to the RFC 2307 posixAccount)/Dest[1533 0 R/XYZ 0 675 0]/Prev 1867 0 R/Next 1869 0 R>>endobj
+1869 0 obj<</Parent 1864 0 R/Title(3.6.5. Configuring Samba with LDAP)/Dest[1533 0 R/XYZ 0 303 0]/Prev 1868 0 R/Next 1870 0 R>>endobj
+1870 0 obj<</Parent 1864 0 R/Title(3.6.6. Accounts and Groups management)/Dest[1537 0 R/XYZ 0 490 0]/Prev 1869 0 R/Next 1871 0 R>>endobj
+1871 0 obj<</Parent 1864 0 R/Title(3.6.7. Security and sambaAccount)/Dest[1537 0 R/XYZ 0 300 0]/Prev 1870 0 R/Next 1872 0 R>>endobj
+1872 0 obj<</Parent 1864 0 R/Title(3.6.8. LDAP specials attributes for sambaAccounts)/Dest[1539 0 R/XYZ 0 596 0]/Prev 1871 0 R/Next 1873 0 R>>endobj
+1873 0 obj<</Parent 1864 0 R/Title(3.6.9. Example LDIF Entries for a sambaAccount)/Dest[1541 0 R/XYZ 0 586 0]/Prev 1872 0 R>>endobj
+1874 0 obj<</Parent 1856 0 R/Count -5/First 1875 0 R/Last 1879 0 R/Title(3.7. MySQL)/Dest[1543 0 R/XYZ 0 760 0]/Prev 1864 0 R/Next 1880 0 R>>endobj
+1875 0 obj<</Parent 1874 0 R/Title(3.7.1. Building)/Dest[1543 0 R/XYZ 0 740 0]/Next 1876 0 R>>endobj
+1876 0 obj<</Parent 1874 0 R/Title(3.7.2. Creating the database)/Dest[1543 0 R/XYZ 0 629 0]/Prev 1875 0 R/Next 1877 0 R>>endobj
+1877 0 obj<</Parent 1874 0 R/Title(3.7.3. Configuring)/Dest[1543 0 R/XYZ 0 531 0]/Prev 1876 0 R/Next 1878 0 R>>endobj
+1878 0 obj<</Parent 1874 0 R/Title(3.7.4. Using plaintext passwords or encrypted password)/Dest[1545 0 R/XYZ 0 470 0]/Prev 1877 0 R/Next 1879 0 R>>endobj
+1879 0 obj<</Parent 1874 0 R/Title(3.7.5. Getting non-column data from the table)/Dest[1545 0 R/XYZ 0 319 0]/Prev 1878 0 R>>endobj
+1880 0 obj<</Parent 1856 0 R/Count -2/First 1881 0 R/Last 1882 0 R/Title(3.8. Passdb XML plugin)/Dest[1545 0 R/XYZ 0 182 0]/Prev 1874 0 R>>endobj
+1881 0 obj<</Parent 1880 0 R/Title(3.8.1. Building)/Dest[1547 0 R/XYZ 0 786 0]/Next 1882 0 R>>endobj
+1882 0 obj<</Parent 1880 0 R/Title(3.8.2. Usage)/Dest[1547 0 R/XYZ 0 701 0]/Prev 1881 0 R>>endobj
+1883 0 obj<</Parent 1831 0 R/Title(II. Type of installation)/Dest[1549 0 R/XYZ 0 786 0]/Prev 1856 0 R/Next 1884 0 R>>endobj
+1884 0 obj<</Parent 1831 0 R/Title(Introduction)/Dest[1551 0 R/XYZ 0 786 0]/Prev 1883 0 R/Next 1885 0 R>>endobj
+1885 0 obj<</Parent 1831 0 R/Count -3/First 1886 0 R/Last 1888 0 R/Title(Chapter 4. Nomenclature of Server Types)/Dest[1555 0 R/XYZ 0 786 0]/Prev 1884 0 R/Next 1890 0 R>>endobj
+1886 0 obj<</Parent 1885 0 R/Title(4.1. Stand Alone Server)/Dest[1555 0 R/XYZ 0 575 0]/Next 1887 0 R>>endobj
+1887 0 obj<</Parent 1885 0 R/Title(4.2. Domain Member Server)/Dest[1555 0 R/XYZ 0 302 0]/Prev 1886 0 R/Next 1888 0 R>>endobj
+1888 0 obj<</Parent 1885 0 R/Count -1/First 1889 0 R/Last 1889 0 R/Title(4.3. Domain Controller)/Dest[1557 0 R/XYZ 0 731 0]/Prev 1887 0 R>>endobj
+1889 0 obj<</Parent 1888 0 R/Title(4.3.1. Domain Controller Types)/Dest[1557 0 R/XYZ 0 643 0]>>endobj
+1890 0 obj<</Parent 1831 0 R/Title(Chapter 5. Samba as Stand-Alone server \(User and Share security level\))/Dest[1559 0 R/XYZ 0 786 0]/Prev 1885 0 R/Next 1891 0 R>>endobj
+1891 0 obj<</Parent 1831 0 R/Count -9/First 1892 0 R/Last 1905 0 R/Title(Chapter 6. Samba as an NT4 or Win2k Primary Domain Controller)/Dest[1563 0 R/XYZ 0 786 0]/Prev 1890 0 R/Next 1906 0 R>>endobj
+1892 0 obj<</Parent 1891 0 R/Title(6.1. Prerequisite Reading)/Dest[1563 0 R/XYZ 0 738 0]/Next 1893 0 R>>endobj
+1893 0 obj<</Parent 1891 0 R/Title(6.2. Background)/Dest[1563 0 R/XYZ 0 637 0]/Prev 1892 0 R/Next 1894 0 R>>endobj
+1894 0 obj<</Parent 1891 0 R/Title(6.3. Configuring the Samba Domain Controller)/Dest[1565 0 R/XYZ 0 786 0]/Prev 1893 0 R/Next 1895 0 R>>endobj
+1895 0 obj<</Parent 1891 0 R/Count -3/First 1896 0 R/Last 1898 0 R/Title(6.4. Creating Machine Trust Accounts and Joining Clients to the Domain)/Dest[1567 0 R/XYZ 0 718 0]/Prev 1894 0 R/Next 1899 0 R>>endobj
+1896 0 obj<</Parent 1895 0 R/Title(6.4.1. Manual Creation of Machine Trust Accounts)/Dest[1569 0 R/XYZ 0 718 0]/Next 1897 0 R>>endobj
+1897 0 obj<</Parent 1895 0 R/Title(6.4.2. "On-the-Fly" Creation of Machine Trust Accounts)/Dest[1571 0 R/XYZ 0 786 0]/Prev 1896 0 R/Next 1898 0 R>>endobj
+1898 0 obj<</Parent 1895 0 R/Title(6.4.3. Joining the Client to the Domain)/Dest[1571 0 R/XYZ 0 577 0]/Prev 1897 0 R>>endobj
+1899 0 obj<</Parent 1891 0 R/Title(6.5. Common Problems and Errors)/Dest[1571 0 R/XYZ 0 228 0]/Prev 1895 0 R/Next 1900 0 R>>endobj
+1900 0 obj<</Parent 1891 0 R/Title(6.6. System Policies and Profiles)/Dest[1575 0 R/XYZ 0 617 0]/Prev 1899 0 R/Next 1901 0 R>>endobj
+1901 0 obj<</Parent 1891 0 R/Title(6.7. What other help can I get?)/Dest[1577 0 R/XYZ 0 613 0]/Prev 1900 0 R/Next 1902 0 R>>endobj
+1902 0 obj<</Parent 1891 0 R/Count -2/First 1903 0 R/Last 1904 0 R/Title(6.8. Domain Control for Windows 9x/ME)/Dest[1581 0 R/XYZ 0 335 0]/Prev 1901 0 R/Next 1905 0 R>>endobj
+1903 0 obj<</Parent 1902 0 R/Title(6.8.1. Configuration Instructions: Network Logons)/Dest[1583 0 R/XYZ 0 335 0]/Next 1904 0 R>>endobj
+1904 0 obj<</Parent 1902 0 R/Title(6.8.2. Configuration Instructions: Setting up Roaming User Profiles)/Dest[1585 0 R/XYZ 0 557 0]/Prev 1903 0 R>>endobj
+1905 0 obj<</Parent 1891 0 R/Title(6.9. DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba)/Dest[1593 0 R/XYZ 0 468 0]/Prev 1902 0 R>>endobj
+1906 0 obj<</Parent 1831 0 R/Count -5/First 1907 0 R/Last 1913 0 R/Title(Chapter 7. How to Act as a Backup Domain Controller in a Purely Samba Controlled Domain)/Dest[1597 0 R/XYZ 0 786 0]/Prev 1891 0 R/Next 1916 0 R>>endobj
+1907 0 obj<</Parent 1906 0 R/Title(7.1. Prerequisite Reading)/Dest[1597 0 R/XYZ 0 738 0]/Next 1908 0 R>>endobj
+1908 0 obj<</Parent 1906 0 R/Title(7.2. Background)/Dest[1597 0 R/XYZ 0 650 0]/Prev 1907 0 R/Next 1909 0 R>>endobj
+1909 0 obj<</Parent 1906 0 R/Count -2/First 1910 0 R/Last 1911 0 R/Title(7.3. What qualifies a Domain Controller on the network?)/Dest[1597 0 R/XYZ 0 278 0]/Prev 1908 0 R/Next 1912 0 R>>endobj
+1910 0 obj<</Parent 1909 0 R/Title(7.3.1. How does a Workstation find its domain controller?)/Dest[1599 0 R/XYZ 0 786 0]/Next 1911 0 R>>endobj
+1911 0 obj<</Parent 1909 0 R/Title(7.3.2. When is the PDC needed?)/Dest[1599 0 R/XYZ 0 662 0]/Prev 1910 0 R>>endobj
+1912 0 obj<</Parent 1906 0 R/Title(7.4. Can Samba be a Backup Domain Controller to an NT PDC?)/Dest[1599 0 R/XYZ 0 577 0]/Prev 1909 0 R/Next 1913 0 R>>endobj
+1913 0 obj<</Parent 1906 0 R/Count -2/First 1914 0 R/Last 1915 0 R/Title(7.5. How do I set up a Samba BDC?)/Dest[1599 0 R/XYZ 0 376 0]/Prev 1912 0 R>>endobj
+1914 0 obj<</Parent 1913 0 R/Title(7.5.1. How do I replicate the smbpasswd file?)/Dest[1601 0 R/XYZ 0 593 0]/Next 1915 0 R>>endobj
+1915 0 obj<</Parent 1913 0 R/Title(7.5.2. Can I do this all with LDAP?)/Dest[1601 0 R/XYZ 0 443 0]/Prev 1914 0 R>>endobj
+1916 0 obj<</Parent 1831 0 R/Count -8/First 1917 0 R/Last 1925 0 R/Title(Chapter 8. Samba as a ADS domain member)/Dest[1603 0 R/XYZ 0 786 0]/Prev 1906 0 R/Next 1926 0 R>>endobj
+1917 0 obj<</Parent 1916 0 R/Title(8.1. Installing the required packages for Debian)/Dest[1603 0 R/XYZ 0 604 0]/Next 1918 0 R>>endobj
+1918 0 obj<</Parent 1916 0 R/Title(8.2. Installing the required packages for RedHat)/Dest[1603 0 R/XYZ 0 496 0]/Prev 1917 0 R/Next 1919 0 R>>endobj
+1919 0 obj<</Parent 1916 0 R/Title(8.3. Compile Samba)/Dest[1603 0 R/XYZ 0 320 0]/Prev 1918 0 R/Next 1920 0 R>>endobj
+1920 0 obj<</Parent 1916 0 R/Title(8.4. Setup your /etc/krb5.conf)/Dest[1605 0 R/XYZ 0 633 0]/Prev 1919 0 R/Next 1921 0 R>>endobj
+1921 0 obj<</Parent 1916 0 R/Count -1/First 1922 0 R/Last 1922 0 R/Title(8.5. Create the computer account)/Dest[1605 0 R/XYZ 0 317 0]/Prev 1920 0 R/Next 1923 0 R>>endobj
+1922 0 obj<</Parent 1921 0 R/Title(8.5.1. Possible errors)/Dest[1605 0 R/XYZ 0 255 0]>>endobj
+1923 0 obj<</Parent 1916 0 R/Title(8.6. Test your server setup)/Dest[1607 0 R/XYZ 0 786 0]/Prev 1921 0 R/Next 1924 0 R>>endobj
+1924 0 obj<</Parent 1916 0 R/Title(8.7. Testing with smbclient)/Dest[1607 0 R/XYZ 0 698 0]/Prev 1923 0 R/Next 1925 0 R>>endobj
+1925 0 obj<</Parent 1916 0 R/Title(8.8. Notes)/Dest[1607 0 R/XYZ 0 623 0]/Prev 1924 0 R>>endobj
+1926 0 obj<</Parent 1831 0 R/Count -3/First 1927 0 R/Last 1929 0 R/Title(Chapter 9. Samba as a NT4 or Win2k domain member)/Dest[1609 0 R/XYZ 0 786 0]/Prev 1916 0 R/Next 1930 0 R>>endobj
+1927 0 obj<</Parent 1926 0 R/Title(9.1. Joining an NT Domain with Samba 3.0)/Dest[1609 0 R/XYZ 0 738 0]/Next 1928 0 R>>endobj
+1928 0 obj<</Parent 1926 0 R/Title(9.2. Samba and Windows 2000 Domains)/Dest[1611 0 R/XYZ 0 547 0]/Prev 1927 0 R/Next 1929 0 R>>endobj
+1929 0 obj<</Parent 1926 0 R/Title(9.3. Why is this better than security = server?)/Dest[1611 0 R/XYZ 0 458 0]/Prev 1928 0 R>>endobj
+1930 0 obj<</Parent 1831 0 R/Title(III. Optional configuration)/Dest[1615 0 R/XYZ 0 786 0]/Prev 1926 0 R/Next 1931 0 R>>endobj
+1931 0 obj<</Parent 1831 0 R/Title(Introduction)/Dest[1617 0 R/XYZ 0 786 0]/Prev 1930 0 R/Next 1932 0 R>>endobj
+1932 0 obj<</Parent 1831 0 R/Count -6/First 1933 0 R/Last 1950 0 R/Title(Chapter 10. Integrating MS Windows networks with Samba)/Dest[1623 0 R/XYZ 0 786 0]/Prev 1931 0 R/Next 1951 0 R>>endobj
+1933 0 obj<</Parent 1932 0 R/Title(10.1. Agenda)/Dest[1623 0 R/XYZ 0 738 0]/Next 1934 0 R>>endobj
+1934 0 obj<</Parent 1932 0 R/Count -4/First 1935 0 R/Last 1938 0 R/Title(10.2. Name Resolution in a pure Unix/Linux world)/Dest[1623 0 R/XYZ 0 491 0]/Prev 1933 0 R/Next 1939 0 R>>endobj
+1935 0 obj<</Parent 1934 0 R/Title(10.2.1. /etc/hosts)/Dest[1623 0 R/XYZ 0 363 0]/Next 1936 0 R>>endobj
+1936 0 obj<</Parent 1934 0 R/Title(10.2.2. /etc/resolv.conf)/Dest[1625 0 R/XYZ 0 494 0]/Prev 1935 0 R/Next 1937 0 R>>endobj
+1937 0 obj<</Parent 1934 0 R/Title(10.2.3. /etc/host.conf)/Dest[1625 0 R/XYZ 0 356 0]/Prev 1936 0 R/Next 1938 0 R>>endobj
+1938 0 obj<</Parent 1934 0 R/Title(10.2.4. /etc/nsswitch.conf)/Dest[1625 0 R/XYZ 0 210 0]/Prev 1937 0 R>>endobj
+1939 0 obj<</Parent 1932 0 R/Count -5/First 1940 0 R/Last 1944 0 R/Title(10.3. Name resolution as used within MS Windows networking)/Dest[1627 0 R/XYZ 0 392 0]/Prev 1934 0 R/Next 1945 0 R>>endobj
+1940 0 obj<</Parent 1939 0 R/Title(10.3.1. The NetBIOS Name Cache)/Dest[1629 0 R/XYZ 0 319 0]/Next 1941 0 R>>endobj
+1941 0 obj<</Parent 1939 0 R/Title(10.3.2. The LMHOSTS file)/Dest[1631 0 R/XYZ 0 786 0]/Prev 1940 0 R/Next 1942 0 R>>endobj
+1942 0 obj<</Parent 1939 0 R/Title(10.3.3. HOSTS file)/Dest[1633 0 R/XYZ 0 512 0]/Prev 1941 0 R/Next 1943 0 R>>endobj
+1943 0 obj<</Parent 1939 0 R/Title(10.3.4. DNS Lookup)/Dest[1633 0 R/XYZ 0 414 0]/Prev 1942 0 R/Next 1944 0 R>>endobj
+1944 0 obj<</Parent 1939 0 R/Title(10.3.5. WINS Lookup)/Dest[1633 0 R/XYZ 0 276 0]/Prev 1943 0 R>>endobj
+1945 0 obj<</Parent 1932 0 R/Title(10.4. How browsing functions and how to deploy stable and dependable browsing using Samba)/Dest[1635 0 R/XYZ 0 723 0]/Prev 1939 0 R/Next 1946 0 R>>endobj
+1946 0 obj<</Parent 1932 0 R/Count -3/First 1947 0 R/Last 1949 0 R/Title(10.5. MS Windows security options and how to configure Samba for seemless integration)/Dest[1635 0 R/XYZ 0 179 0]/Prev 1945 0 R/Next 1950 0 R>>endobj
+1947 0 obj<</Parent 1946 0 R/Title(10.5.1. Use MS Windows NT as an authentication server)/Dest[1639 0 R/XYZ 0 786 0]/Next 1948 0 R>>endobj
+1948 0 obj<</Parent 1946 0 R/Title(10.5.2. Make Samba a member of an MS Windows NT security domain)/Dest[1639 0 R/XYZ 0 537 0]/Prev 1947 0 R/Next 1949 0 R>>endobj
+1949 0 obj<</Parent 1946 0 R/Title(10.5.3. Configure Samba as an authentication server)/Dest[1639 0 R/XYZ 0 185 0]/Prev 1948 0 R>>endobj
+1950 0 obj<</Parent 1932 0 R/Title(10.6. Conclusions)/Dest[1641 0 R/XYZ 0 316 0]/Prev 1946 0 R>>endobj
+1951 0 obj<</Parent 1831 0 R/Count -7/First 1952 0 R/Last 1960 0 R/Title(Chapter 11. UNIX Permission Bits and Windows NT Access Control Lists)/Dest[1643 0 R/XYZ 0 786 0]/Prev 1932 0 R/Next 1961 0 R>>endobj
+1952 0 obj<</Parent 1951 0 R/Title(11.1. Viewing and changing UNIX permissions using the NT security dialogs)/Dest[1643 0 R/XYZ 0 738 0]/Next 1953 0 R>>endobj
+1953 0 obj<</Parent 1951 0 R/Title(11.2. How to view file security on a Samba share)/Dest[1643 0 R/XYZ 0 590 0]/Prev 1952 0 R/Next 1954 0 R>>endobj
+1954 0 obj<</Parent 1951 0 R/Title(11.3. Viewing file ownership)/Dest[1643 0 R/XYZ 0 422 0]/Prev 1953 0 R/Next 1955 0 R>>endobj
+1955 0 obj<</Parent 1951 0 R/Count -2/First 1956 0 R/Last 1957 0 R/Title(11.4. Viewing file or directory permissions)/Dest[1645 0 R/XYZ 0 758 0]/Prev 1954 0 R/Next 1958 0 R>>endobj
+1956 0 obj<</Parent 1955 0 R/Title(11.4.1. File Permissions)/Dest[1645 0 R/XYZ 0 524 0]/Next 1957 0 R>>endobj
+1957 0 obj<</Parent 1955 0 R/Title(11.4.2. Directory Permissions)/Dest[1645 0 R/XYZ 0 281 0]/Prev 1956 0 R>>endobj
+1958 0 obj<</Parent 1951 0 R/Title(11.5. Modifying file or directory permissions)/Dest[1647 0 R/XYZ 0 771 0]/Prev 1955 0 R/Next 1959 0 R>>endobj
+1959 0 obj<</Parent 1951 0 R/Title(11.6. Interaction with the standard Samba create mask parameters)/Dest[1647 0 R/XYZ 0 339 0]/Prev 1958 0 R/Next 1960 0 R>>endobj
+1960 0 obj<</Parent 1951 0 R/Title(11.7. Interaction with the standard Samba file attribute mapping)/Dest[1651 0 R/XYZ 0 705 0]/Prev 1959 0 R>>endobj
+1961 0 obj<</Parent 1831 0 R/Count -3/First 1962 0 R/Last 1964 0 R/Title(Chapter 12. Configuring PAM for distributed but centrally managed authentication)/Dest[1653 0 R/XYZ 0 786 0]/Prev 1951 0 R/Next 1965 0 R>>endobj
+1962 0 obj<</Parent 1961 0 R/Title(12.1. Samba and PAM)/Dest[1653 0 R/XYZ 0 738 0]/Next 1963 0 R>>endobj
+1963 0 obj<</Parent 1961 0 R/Title(12.2. Distributed Authentication)/Dest[1655 0 R/XYZ 0 201 0]/Prev 1962 0 R/Next 1964 0 R>>endobj
+1964 0 obj<</Parent 1961 0 R/Title(12.3. PAM Configuration in smb.conf)/Dest[1657 0 R/XYZ 0 758 0]/Prev 1963 0 R>>endobj
+1965 0 obj<</Parent 1831 0 R/Count -1/First 1966 0 R/Last 1966 0 R/Title(Chapter 13. Hosting a Microsoft Distributed File System tree on Samba)/Dest[1659 0 R/XYZ 0 786 0]/Prev 1961 0 R/Next 1968 0 R>>endobj
+1966 0 obj<</Parent 1965 0 R/Count -1/First 1967 0 R/Last 1967 0 R/Title(13.1. Instructions)/Dest[1659 0 R/XYZ 0 738 0]>>endobj
+1967 0 obj<</Parent 1966 0 R/Title(13.1.1. Notes)/Dest[1661 0 R/XYZ 0 705 0]>>endobj
+1968 0 obj<</Parent 1831 0 R/Count -4/First 1969 0 R/Last 1981 0 R/Title(Chapter 14. Printing Support)/Dest[1663 0 R/XYZ 0 786 0]/Prev 1965 0 R/Next 1991 0 R>>endobj
+1969 0 obj<</Parent 1968 0 R/Title(14.1. Introduction)/Dest[1663 0 R/XYZ 0 762 0]/Next 1970 0 R>>endobj
+1970 0 obj<</Parent 1968 0 R/Count -5/First 1971 0 R/Last 1975 0 R/Title(14.2. Configuration)/Dest[1663 0 R/XYZ 0 370 0]/Prev 1969 0 R/Next 1976 0 R>>endobj
+1971 0 obj<</Parent 1970 0 R/Title(14.2.1. Creating [print$])/Dest[1663 0 R/XYZ 0 180 0]/Next 1972 0 R>>endobj
+1972 0 obj<</Parent 1970 0 R/Title(14.2.2. Setting Drivers for Existing Printers)/Dest[1667 0 R/XYZ 0 583 0]/Prev 1971 0 R/Next 1973 0 R>>endobj
+1973 0 obj<</Parent 1970 0 R/Title(14.2.3. Support a large number of printers)/Dest[1669 0 R/XYZ 0 786 0]/Prev 1972 0 R/Next 1974 0 R>>endobj
+1974 0 obj<</Parent 1970 0 R/Title(14.2.4. Adding New Printers via the Windows NT APW)/Dest[1669 0 R/XYZ 0 416 0]/Prev 1973 0 R/Next 1975 0 R>>endobj
+1975 0 obj<</Parent 1970 0 R/Title(14.2.5. Samba and Printer Ports)/Dest[1671 0 R/XYZ 0 237 0]/Prev 1974 0 R>>endobj
+1976 0 obj<</Parent 1968 0 R/Count -4/First 1977 0 R/Last 1980 0 R/Title(14.3. The Imprints Toolset)/Dest[1673 0 R/XYZ 0 745 0]/Prev 1970 0 R/Next 1981 0 R>>endobj
+1977 0 obj<</Parent 1976 0 R/Title(14.3.1. What is Imprints?)/Dest[1673 0 R/XYZ 0 643 0]/Next 1978 0 R>>endobj
+1978 0 obj<</Parent 1976 0 R/Title(14.3.2. Creating Printer Driver Packages)/Dest[1673 0 R/XYZ 0 519 0]/Prev 1977 0 R/Next 1979 0 R>>endobj
+1979 0 obj<</Parent 1976 0 R/Title(14.3.3. The Imprints server)/Dest[1673 0 R/XYZ 0 434 0]/Prev 1978 0 R/Next 1980 0 R>>endobj
+1980 0 obj<</Parent 1976 0 R/Title(14.3.4. The Installation Client)/Dest[1673 0 R/XYZ 0 336 0]/Prev 1979 0 R>>endobj
+1981 0 obj<</Parent 1968 0 R/Count -9/First 1982 0 R/Last 1990 0 R/Title(14.4. Diagnosis)/Dest[1675 0 R/XYZ 0 449 0]/Prev 1976 0 R>>endobj
+1982 0 obj<</Parent 1981 0 R/Title(14.4.1. Introduction)/Dest[1675 0 R/XYZ 0 429 0]/Next 1983 0 R>>endobj
+1983 0 obj<</Parent 1981 0 R/Title(14.4.2. Debugging printer problems)/Dest[1677 0 R/XYZ 0 482 0]/Prev 1982 0 R/Next 1984 0 R>>endobj
+1984 0 obj<</Parent 1981 0 R/Title(14.4.3. What printers do I have?)/Dest[1679 0 R/XYZ 0 718 0]/Prev 1983 0 R/Next 1985 0 R>>endobj
+1985 0 obj<</Parent 1981 0 R/Title(14.4.4. Setting up printcap and print servers)/Dest[1679 0 R/XYZ 0 537 0]/Prev 1984 0 R/Next 1986 0 R>>endobj
+1986 0 obj<</Parent 1981 0 R/Title(14.4.5. Job sent, no output)/Dest[1681 0 R/XYZ 0 786 0]/Prev 1985 0 R/Next 1987 0 R>>endobj
+1987 0 obj<</Parent 1981 0 R/Title(14.4.6. Job sent, strange output)/Dest[1681 0 R/XYZ 0 447 0]/Prev 1986 0 R/Next 1988 0 R>>endobj
+1988 0 obj<</Parent 1981 0 R/Title(14.4.7. Raw PostScript printed)/Dest[1683 0 R/XYZ 0 771 0]/Prev 1987 0 R/Next 1989 0 R>>endobj
+1989 0 obj<</Parent 1981 0 R/Title(14.4.8. Advanced Printing)/Dest[1683 0 R/XYZ 0 686 0]/Prev 1988 0 R/Next 1990 0 R>>endobj
+1990 0 obj<</Parent 1981 0 R/Title(14.4.9. Real debugging)/Dest[1683 0 R/XYZ 0 588 0]/Prev 1989 0 R>>endobj
+1991 0 obj<</Parent 1831 0 R/Count -7/First 1992 0 R/Last 1999 0 R/Title(Chapter 15. CUPS Printing Support)/Dest[1685 0 R/XYZ 0 786 0]/Prev 1968 0 R/Next 2000 0 R>>endobj
+1992 0 obj<</Parent 1991 0 R/Title(15.1. Introduction)/Dest[1685 0 R/XYZ 0 762 0]/Next 1993 0 R>>endobj
+1993 0 obj<</Parent 1991 0 R/Title(15.2. CUPS - RAW Print Through Mode)/Dest[1685 0 R/XYZ 0 515 0]/Prev 1992 0 R/Next 1994 0 R>>endobj
+1994 0 obj<</Parent 1991 0 R/Title(15.3. The CUPS Filter Chains)/Dest[1689 0 R/XYZ 0 329 0]/Prev 1993 0 R/Next 1995 0 R>>endobj
+1995 0 obj<</Parent 1991 0 R/Count -1/First 1996 0 R/Last 1996 0 R/Title(15.4. CUPS Print Drivers and Devices)/Dest[1701 0 R/XYZ 0 598 0]/Prev 1994 0 R/Next 1997 0 R>>endobj
+1996 0 obj<</Parent 1995 0 R/Title(15.4.1. Further printing steps)/Dest[1701 0 R/XYZ 0 457 0]>>endobj
+1997 0 obj<</Parent 1991 0 R/Title(15.5. Limiting the number of pages users can print)/Dest[1705 0 R/XYZ 0 230 0]/Prev 1995 0 R/Next 1998 0 R>>endobj
+1998 0 obj<</Parent 1991 0 R/Title(15.6. Advanced Postscript Printing from MS Windows)/Dest[1713 0 R/XYZ 0 415 0]/Prev 1997 0 R/Next 1999 0 R>>endobj
+1999 0 obj<</Parent 1991 0 R/Title(15.7. Auto-Deletion of CUPS spool files)/Dest[1715 0 R/XYZ 0 579 0]/Prev 1998 0 R>>endobj
+2000 0 obj<</Parent 1831 0 R/Count -7/First 2001 0 R/Last 2017 0 R/Title(Chapter 16. Unified Logons between Windows NT and UNIX using Winbind)/Dest[1719 0 R/XYZ 0 786 0]/Prev 1991 0 R/Next 2018 0 R>>endobj
+2001 0 obj<</Parent 2000 0 R/Title(16.1. Abstract)/Dest[1719 0 R/XYZ 0 738 0]/Next 2002 0 R>>endobj
+2002 0 obj<</Parent 2000 0 R/Title(16.2. Introduction)/Dest[1719 0 R/XYZ 0 597 0]/Prev 2001 0 R/Next 2003 0 R>>endobj
+2003 0 obj<</Parent 2000 0 R/Count -1/First 2004 0 R/Last 2004 0 R/Title(16.3. What Winbind Provides)/Dest[1719 0 R/XYZ 0 284 0]/Prev 2002 0 R/Next 2005 0 R>>endobj
+2004 0 obj<</Parent 2003 0 R/Title(16.3.1. Target Uses)/Dest[1721 0 R/XYZ 0 613 0]>>endobj
+2005 0 obj<</Parent 2000 0 R/Count -6/First 2006 0 R/Last 2011 0 R/Title(16.4. How Winbind Works)/Dest[1721 0 R/XYZ 0 462 0]/Prev 2003 0 R/Next 2012 0 R>>endobj
+2006 0 obj<</Parent 2005 0 R/Title(16.4.1. Microsoft Remote Procedure Calls)/Dest[1721 0 R/XYZ 0 347 0]/Next 2007 0 R>>endobj
+2007 0 obj<</Parent 2005 0 R/Title(16.4.2. Microsoft Active Directory Services)/Dest[1723 0 R/XYZ 0 786 0]/Prev 2006 0 R/Next 2008 0 R>>endobj
+2008 0 obj<</Parent 2005 0 R/Title(16.4.3. Name Service Switch)/Dest[1723 0 R/XYZ 0 688 0]/Prev 2007 0 R/Next 2009 0 R>>endobj
+2009 0 obj<</Parent 2005 0 R/Title(16.4.4. Pluggable Authentication Modules)/Dest[1723 0 R/XYZ 0 247 0]/Prev 2008 0 R/Next 2010 0 R>>endobj
+2010 0 obj<</Parent 2005 0 R/Title(16.4.5. User and Group ID Allocation)/Dest[1725 0 R/XYZ 0 613 0]/Prev 2009 0 R/Next 2011 0 R>>endobj
+2011 0 obj<</Parent 2005 0 R/Title(16.4.6. Result Caching)/Dest[1725 0 R/XYZ 0 435 0]/Prev 2010 0 R>>endobj
+2012 0 obj<</Parent 2000 0 R/Count -3/First 2013 0 R/Last 2015 0 R/Title(16.5. Installation and Configuration)/Dest[1725 0 R/XYZ 0 298 0]/Prev 2005 0 R/Next 2016 0 R>>endobj
+2013 0 obj<</Parent 2012 0 R/Title(16.5.1. Introduction)/Dest[1725 0 R/XYZ 0 196 0]/Next 2014 0 R>>endobj
+2014 0 obj<</Parent 2012 0 R/Title(16.5.2. Requirements)/Dest[1727 0 R/XYZ 0 586 0]/Prev 2013 0 R/Next 2015 0 R>>endobj
+2015 0 obj<</Parent 2012 0 R/Title(16.5.3. Testing Things Out)/Dest[1727 0 R/XYZ 0 317 0]/Prev 2014 0 R>>endobj
+2016 0 obj<</Parent 2000 0 R/Title(16.6. Limitations)/Dest[1743 0 R/XYZ 0 608 0]/Prev 2012 0 R/Next 2017 0 R>>endobj
+2017 0 obj<</Parent 2000 0 R/Title(16.7. Conclusion)/Dest[1743 0 R/XYZ 0 387 0]/Prev 2016 0 R>>endobj
+2018 0 obj<</Parent 1831 0 R/Count -11/First 2019 0 R/Last 2030 0 R/Title(Chapter 17. Improved browsing in samba)/Dest[1745 0 R/XYZ 0 786 0]/Prev 2000 0 R/Next 2031 0 R>>endobj
+2019 0 obj<</Parent 2018 0 R/Title(17.1. Overview of browsing)/Dest[1745 0 R/XYZ 0 762 0]/Next 2020 0 R>>endobj
+2020 0 obj<</Parent 2018 0 R/Title(17.2. Browsing support in samba)/Dest[1745 0 R/XYZ 0 515 0]/Prev 2019 0 R/Next 2021 0 R>>endobj
+2021 0 obj<</Parent 2018 0 R/Title(17.3. Problem resolution)/Dest[1747 0 R/XYZ 0 786 0]/Prev 2020 0 R/Next 2022 0 R>>endobj
+2022 0 obj<</Parent 2018 0 R/Count -1/First 2023 0 R/Last 2023 0 R/Title(17.4. Browsing across subnets)/Dest[1747 0 R/XYZ 0 434 0]/Prev 2021 0 R/Next 2024 0 R>>endobj
+2023 0 obj<</Parent 2022 0 R/Title(17.4.1. How does cross subnet browsing work ?)/Dest[1749 0 R/XYZ 0 786 0]>>endobj
+2024 0 obj<</Parent 2018 0 R/Title(17.5. Setting up a WINS server)/Dest[1753 0 R/XYZ 0 385 0]/Prev 2022 0 R/Next 2025 0 R>>endobj
+2025 0 obj<</Parent 2018 0 R/Title(17.6. Setting up Browsing in a WORKGROUP)/Dest[1755 0 R/XYZ 0 441 0]/Prev 2024 0 R/Next 2026 0 R>>endobj
+2026 0 obj<</Parent 2018 0 R/Title(17.7. Setting up Browsing in a DOMAIN)/Dest[1757 0 R/XYZ 0 460 0]/Prev 2025 0 R/Next 2027 0 R>>endobj
+2027 0 obj<</Parent 2018 0 R/Title(17.8. Forcing samba to be the master)/Dest[1759 0 R/XYZ 0 771 0]/Prev 2026 0 R/Next 2028 0 R>>endobj
+2028 0 obj<</Parent 2018 0 R/Title(17.9. Making samba the domain master)/Dest[1759 0 R/XYZ 0 353 0]/Prev 2027 0 R/Next 2029 0 R>>endobj
+2029 0 obj<</Parent 2018 0 R/Title(17.10. Note about broadcast addresses)/Dest[1761 0 R/XYZ 0 573 0]/Prev 2028 0 R/Next 2030 0 R>>endobj
+2030 0 obj<</Parent 2018 0 R/Title(17.11. Multiple interfaces)/Dest[1761 0 R/XYZ 0 485 0]/Prev 2029 0 R>>endobj
+2031 0 obj<</Parent 1831 0 R/Count -3/First 2032 0 R/Last 2037 0 R/Title(Chapter 18. Stackable VFS modules)/Dest[1763 0 R/XYZ 0 786 0]/Prev 2018 0 R/Next 2040 0 R>>endobj
+2032 0 obj<</Parent 2031 0 R/Title(18.1. Introduction and configuration)/Dest[1763 0 R/XYZ 0 762 0]/Next 2033 0 R>>endobj
+2033 0 obj<</Parent 2031 0 R/Count -3/First 2034 0 R/Last 2036 0 R/Title(18.2. Included modules)/Dest[1763 0 R/XYZ 0 437 0]/Prev 2032 0 R/Next 2037 0 R>>endobj
+2034 0 obj<</Parent 2033 0 R/Title(18.2.1. audit)/Dest[1763 0 R/XYZ 0 417 0]/Next 2035 0 R>>endobj
+2035 0 obj<</Parent 2033 0 R/Title(18.2.2. recycle)/Dest[1763 0 R/XYZ 0 268 0]/Prev 2034 0 R/Next 2036 0 R>>endobj
+2036 0 obj<</Parent 2033 0 R/Title(18.2.3. netatalk)/Dest[1765 0 R/XYZ 0 613 0]/Prev 2035 0 R>>endobj
+2037 0 obj<</Parent 2031 0 R/Count -2/First 2038 0 R/Last 2039 0 R/Title(18.3. VFS modules available elsewhere)/Dest[1765 0 R/XYZ 0 483 0]/Prev 2033 0 R>>endobj
+2038 0 obj<</Parent 2037 0 R/Title(18.3.1. DatabaseFS)/Dest[1765 0 R/XYZ 0 368 0]/Next 2039 0 R>>endobj
+2039 0 obj<</Parent 2037 0 R/Title(18.3.2. vscan)/Dest[1767 0 R/XYZ 0 786 0]/Prev 2038 0 R>>endobj
+2040 0 obj<</Parent 1831 0 R/Title(Chapter 19. Group mapping HOWTO)/Dest[1769 0 R/XYZ 0 786 0]/Prev 2031 0 R/Next 2041 0 R>>endobj
+2041 0 obj<</Parent 1831 0 R/Count -10/First 2042 0 R/Last 2051 0 R/Title(Chapter 20. Samba performance issues)/Dest[1771 0 R/XYZ 0 786 0]/Prev 2040 0 R/Next 2052 0 R>>endobj
+2042 0 obj<</Parent 2041 0 R/Title(20.1. Comparisons)/Dest[1771 0 R/XYZ 0 762 0]/Next 2043 0 R>>endobj
+2043 0 obj<</Parent 2041 0 R/Title(20.2. Socket options)/Dest[1771 0 R/XYZ 0 502 0]/Prev 2042 0 R/Next 2044 0 R>>endobj
+2044 0 obj<</Parent 2041 0 R/Title(20.3. Read size)/Dest[1771 0 R/XYZ 0 242 0]/Prev 2043 0 R/Next 2045 0 R>>endobj
+2045 0 obj<</Parent 2041 0 R/Title(20.4. Max xmit)/Dest[1773 0 R/XYZ 0 692 0]/Prev 2044 0 R/Next 2046 0 R>>endobj
+2046 0 obj<</Parent 2041 0 R/Title(20.5. Log level)/Dest[1773 0 R/XYZ 0 511 0]/Prev 2045 0 R/Next 2047 0 R>>endobj
+2047 0 obj<</Parent 2041 0 R/Title(20.6. Read raw)/Dest[1773 0 R/XYZ 0 436 0]/Prev 2046 0 R/Next 2048 0 R>>endobj
+2048 0 obj<</Parent 2041 0 R/Title(20.7. Write raw)/Dest[1773 0 R/XYZ 0 268 0]/Prev 2047 0 R/Next 2049 0 R>>endobj
+2049 0 obj<</Parent 2041 0 R/Title(20.8. Slow Clients)/Dest[1775 0 R/XYZ 0 786 0]/Prev 2048 0 R/Next 2050 0 R>>endobj
+2050 0 obj<</Parent 2041 0 R/Title(20.9. Slow Logins)/Dest[1775 0 R/XYZ 0 658 0]/Prev 2049 0 R/Next 2051 0 R>>endobj
+2051 0 obj<</Parent 2041 0 R/Title(20.10. Client tuning)/Dest[1775 0 R/XYZ 0 583 0]/Prev 2050 0 R>>endobj
+2052 0 obj<</Parent 1831 0 R/Count -3/First 2053 0 R/Last 2059 0 R/Title(Chapter 21. Creating Group Prolicy Files)/Dest[1779 0 R/XYZ 0 786 0]/Prev 2041 0 R/Next 2060 0 R>>endobj
+2053 0 obj<</Parent 2052 0 R/Title(21.1. Windows '9x)/Dest[1779 0 R/XYZ 0 762 0]/Next 2054 0 R>>endobj
+2054 0 obj<</Parent 2052 0 R/Count -4/First 2055 0 R/Last 2058 0 R/Title(21.2. Windows NT 4)/Dest[1779 0 R/XYZ 0 476 0]/Prev 2053 0 R/Next 2059 0 R>>endobj
+2055 0 obj<</Parent 2054 0 R/Title(21.2.1. Side bar Notes)/Dest[1781 0 R/XYZ 0 786 0]/Next 2056 0 R>>endobj
+2056 0 obj<</Parent 2054 0 R/Title(21.2.2. Mandatory profiles)/Dest[1781 0 R/XYZ 0 688 0]/Prev 2055 0 R/Next 2057 0 R>>endobj
+2057 0 obj<</Parent 2054 0 R/Title(21.2.3. moveuser.exe)/Dest[1781 0 R/XYZ 0 617 0]/Prev 2056 0 R/Next 2058 0 R>>endobj
+2058 0 obj<</Parent 2054 0 R/Title(21.2.4. Get SID)/Dest[1781 0 R/XYZ 0 545 0]/Prev 2057 0 R>>endobj
+2059 0 obj<</Parent 2052 0 R/Title(21.3. Windows 2000/XP)/Dest[1781 0 R/XYZ 0 381 0]/Prev 2054 0 R>>endobj
+2060 0 obj<</Parent 1831 0 R/Count -6/First 2061 0 R/Last 2066 0 R/Title(Chapter 22. Securing Samba)/Dest[1785 0 R/XYZ 0 786 0]/Prev 2052 0 R/Next 2067 0 R>>endobj
+2061 0 obj<</Parent 2060 0 R/Title(22.1. Introduction)/Dest[1785 0 R/XYZ 0 762 0]/Next 2062 0 R>>endobj
+2062 0 obj<</Parent 2060 0 R/Title(22.2. Using host based protection)/Dest[1785 0 R/XYZ 0 674 0]/Prev 2061 0 R/Next 2063 0 R>>endobj
+2063 0 obj<</Parent 2060 0 R/Title(22.3. Using interface protection)/Dest[1785 0 R/XYZ 0 458 0]/Prev 2062 0 R/Next 2064 0 R>>endobj
+2064 0 obj<</Parent 2060 0 R/Title(22.4. Using a firewall)/Dest[1785 0 R/XYZ 0 203 0]/Prev 2063 0 R/Next 2065 0 R>>endobj
+2065 0 obj<</Parent 2060 0 R/Title(22.5. Using a IPC$ share deny)/Dest[1787 0 R/XYZ 0 649 0]/Prev 2064 0 R/Next 2066 0 R>>endobj
+2066 0 obj<</Parent 2060 0 R/Title(22.6. Upgrading Samba)/Dest[1787 0 R/XYZ 0 343 0]/Prev 2065 0 R>>endobj
+2067 0 obj<</Parent 1831 0 R/Count -2/First 2068 0 R/Last 2069 0 R/Title(Chapter 23. Unicode/Charsets)/Dest[1789 0 R/XYZ 0 786 0]/Prev 2060 0 R/Next 2070 0 R>>endobj
+2068 0 obj<</Parent 2067 0 R/Title(23.1. What are charsets and unicode?)/Dest[1789 0 R/XYZ 0 762 0]/Next 2069 0 R>>endobj
+2069 0 obj<</Parent 2067 0 R/Title(23.2. Samba and charsets)/Dest[1789 0 R/XYZ 0 449 0]/Prev 2068 0 R>>endobj
+2070 0 obj<</Parent 1831 0 R/Title(IV. Appendixes)/Dest[1791 0 R/XYZ 0 786 0]/Prev 2067 0 R/Next 2071 0 R>>endobj
+2071 0 obj<</Parent 1831 0 R/Count -5/First 2072 0 R/Last 2076 0 R/Title(Chapter 24. Portability)/Dest[1795 0 R/XYZ 0 786 0]/Prev 2070 0 R/Next 2078 0 R>>endobj
+2072 0 obj<</Parent 2071 0 R/Title(24.1. HPUX)/Dest[1795 0 R/XYZ 0 707 0]/Next 2073 0 R>>endobj
+2073 0 obj<</Parent 2071 0 R/Title(24.2. SCO Unix)/Dest[1795 0 R/XYZ 0 461 0]/Prev 2072 0 R/Next 2074 0 R>>endobj
+2074 0 obj<</Parent 2071 0 R/Title(24.3. DNIX)/Dest[1795 0 R/XYZ 0 346 0]/Prev 2073 0 R/Next 2075 0 R>>endobj
+2075 0 obj<</Parent 2071 0 R/Title(24.4. RedHat Linux Rembrandt-II)/Dest[1797 0 R/XYZ 0 280 0]/Prev 2074 0 R/Next 2076 0 R>>endobj
+2076 0 obj<</Parent 2071 0 R/Count -1/First 2077 0 R/Last 2077 0 R/Title(24.5. AIX)/Dest[1799 0 R/XYZ 0 786 0]/Prev 2075 0 R>>endobj
+2077 0 obj<</Parent 2076 0 R/Title(24.5.1. Sequential Read Ahead)/Dest[1799 0 R/XYZ 0 766 0]>>endobj
+2078 0 obj<</Parent 1831 0 R/Count -5/First 2079 0 R/Last 2092 0 R/Title(Chapter 25. Samba and other CIFS clients)/Dest[1801 0 R/XYZ 0 786 0]/Prev 2071 0 R/Next 2093 0 R>>endobj
+2079 0 obj<</Parent 2078 0 R/Title(25.1. Macintosh clients?)/Dest[1801 0 R/XYZ 0 721 0]/Next 2080 0 R>>endobj
+2080 0 obj<</Parent 2078 0 R/Count -4/First 2081 0 R/Last 2084 0 R/Title(25.2. OS2 Client)/Dest[1801 0 R/XYZ 0 513 0]/Prev 2079 0 R/Next 2085 0 R>>endobj
+2081 0 obj<</Parent 2080 0 R/Title(25.2.1. How can I configure OS/2 Warp Connect or OS/2 Warp 4 as a client for Samba?)/Dest[1801 0 R/XYZ 0 493 0]/Next 2082 0 R>>endobj
+2082 0 obj<</Parent 2080 0 R/Title(25.2.2. How can I configure OS/2 Warp 3 \(not Connect\), OS/2 1.2, 1.3 or 2.x for Samba?)/Dest[1803 0 R/XYZ 0 786 0]/Prev 2081 0 R/Next 2083 0 R>>endobj
+2083 0 obj<</Parent 2080 0 R/Title(25.2.3. Are there any other issues when OS/2 \(any version\) is used as a client?)/Dest[1803 0 R/XYZ 0 575 0]/Prev 2082 0 R/Next 2084 0 R>>endobj
+2084 0 obj<</Parent 2080 0 R/Title(25.2.4. How do I get printer driver download working for OS/2 clients?)/Dest[1803 0 R/XYZ 0 461 0]/Prev 2083 0 R>>endobj
+2085 0 obj<</Parent 2078 0 R/Count -5/First 2086 0 R/Last 2090 0 R/Title(25.3. Windows for Workgroups)/Dest[1803 0 R/XYZ 0 204 0]/Prev 2080 0 R/Next 2091 0 R>>endobj
+2086 0 obj<</Parent 2085 0 R/Title(25.3.1. Use latest TCP/IP stack from Microsoft)/Dest[1803 0 R/XYZ 0 184 0]/Next 2087 0 R>>endobj
+2087 0 obj<</Parent 2085 0 R/Title(25.3.2. Delete .pwl files after password change)/Dest[1805 0 R/XYZ 0 679 0]/Prev 2086 0 R/Next 2088 0 R>>endobj
+2088 0 obj<</Parent 2085 0 R/Title(25.3.3. Configure WfW password handling)/Dest[1805 0 R/XYZ 0 528 0]/Prev 2087 0 R/Next 2089 0 R>>endobj
+2089 0 obj<</Parent 2085 0 R/Title(25.3.4. Case handling of passwords)/Dest[1805 0 R/XYZ 0 430 0]/Prev 2088 0 R/Next 2090 0 R>>endobj
+2090 0 obj<</Parent 2085 0 R/Title(25.3.5. Use TCP/IP as default protocol)/Dest[1805 0 R/XYZ 0 345 0]/Prev 2089 0 R>>endobj
+2091 0 obj<</Parent 2078 0 R/Title(25.4. Windows '95/'98)/Dest[1805 0 R/XYZ 0 260 0]/Prev 2085 0 R/Next 2092 0 R>>endobj
+2092 0 obj<</Parent 2078 0 R/Title(25.5. Windows 2000 Service Pack 2)/Dest[1807 0 R/XYZ 0 679 0]/Prev 2091 0 R>>endobj
+2093 0 obj<</Parent 1831 0 R/Count -4/First 2094 0 R/Last 2099 0 R/Title(Chapter 26. How to compile SAMBA)/Dest[1809 0 R/XYZ 0 786 0]/Prev 2078 0 R/Next 2102 0 R>>endobj
+2094 0 obj<</Parent 2093 0 R/Count -2/First 2095 0 R/Last 2096 0 R/Title(26.1. Access Samba source code via CVS)/Dest[1809 0 R/XYZ 0 707 0]/Next 2097 0 R>>endobj
+2095 0 obj<</Parent 2094 0 R/Title(26.1.1. Introduction)/Dest[1809 0 R/XYZ 0 687 0]/Next 2096 0 R>>endobj
+2096 0 obj<</Parent 2094 0 R/Title(26.1.2. CVS Access to samba.org)/Dest[1809 0 R/XYZ 0 563 0]/Prev 2095 0 R>>endobj
+2097 0 obj<</Parent 2093 0 R/Title(26.2. Accessing the samba sources via rsync and ftp)/Dest[1811 0 R/XYZ 0 547 0]/Prev 2094 0 R/Next 2098 0 R>>endobj
+2098 0 obj<</Parent 2093 0 R/Title(26.3. Building the Binaries)/Dest[1811 0 R/XYZ 0 405 0]/Prev 2097 0 R/Next 2099 0 R>>endobj
+2099 0 obj<</Parent 2093 0 R/Count -2/First 2100 0 R/Last 2101 0 R/Title(26.4. Starting the smbd and nmbd)/Dest[1813 0 R/XYZ 0 665 0]/Prev 2098 0 R>>endobj
+2100 0 obj<</Parent 2099 0 R/Title(26.4.1. Starting from inetd.conf)/Dest[1813 0 R/XYZ 0 511 0]/Next 2101 0 R>>endobj
+2101 0 obj<</Parent 2099 0 R/Title(26.4.2. Alternative: starting it as a daemon)/Dest[1815 0 R/XYZ 0 692 0]/Prev 2100 0 R>>endobj
+2102 0 obj<</Parent 1831 0 R/Count -6/First 2103 0 R/Last 2108 0 R/Title(Chapter 27. Reporting Bugs)/Dest[1817 0 R/XYZ 0 786 0]/Prev 2093 0 R/Next 2109 0 R>>endobj
+2103 0 obj<</Parent 2102 0 R/Title(27.1. Introduction)/Dest[1817 0 R/XYZ 0 762 0]/Next 2104 0 R>>endobj
+2104 0 obj<</Parent 2102 0 R/Title(27.2. General info)/Dest[1817 0 R/XYZ 0 476 0]/Prev 2103 0 R/Next 2105 0 R>>endobj
+2105 0 obj<</Parent 2102 0 R/Title(27.3. Debug levels)/Dest[1817 0 R/XYZ 0 335 0]/Prev 2104 0 R/Next 2106 0 R>>endobj
+2106 0 obj<</Parent 2102 0 R/Title(27.4. Internal errors)/Dest[1819 0 R/XYZ 0 665 0]/Prev 2105 0 R/Next 2107 0 R>>endobj
+2107 0 obj<</Parent 2102 0 R/Title(27.5. Attaching to a running process)/Dest[1819 0 R/XYZ 0 313 0]/Prev 2106 0 R/Next 2108 0 R>>endobj
+2108 0 obj<</Parent 2102 0 R/Title(27.6. Patches)/Dest[1819 0 R/XYZ 0 211 0]/Prev 2107 0 R>>endobj
+2109 0 obj<</Parent 1831 0 R/Count -4/First 2110 0 R/Last 2124 0 R/Title(Chapter 28. The samba checklist)/Dest[1821 0 R/XYZ 0 786 0]/Prev 2102 0 R>>endobj
+2110 0 obj<</Parent 2109 0 R/Title(28.1. Introduction)/Dest[1821 0 R/XYZ 0 762 0]/Next 2111 0 R>>endobj
+2111 0 obj<</Parent 2109 0 R/Title(28.2. Assumptions)/Dest[1821 0 R/XYZ 0 581 0]/Prev 2110 0 R/Next 2112 0 R>>endobj
+2112 0 obj<</Parent 2109 0 R/Count -11/First 2113 0 R/Last 2123 0 R/Title(28.3. Tests)/Dest[1821 0 R/XYZ 0 252 0]/Prev 2111 0 R/Next 2124 0 R>>endobj
+2113 0 obj<</Parent 2112 0 R/Title(28.3.1. Test 1)/Dest[1821 0 R/XYZ 0 231 0]/Next 2114 0 R>>endobj
+2114 0 obj<</Parent 2112 0 R/Title(28.3.2. Test 2)/Dest[1823 0 R/XYZ 0 786 0]/Prev 2113 0 R/Next 2115 0 R>>endobj
+2115 0 obj<</Parent 2112 0 R/Title(28.3.3. Test 3)/Dest[1823 0 R/XYZ 0 583 0]/Prev 2114 0 R/Next 2116 0 R>>endobj
+2116 0 obj<</Parent 2112 0 R/Title(28.3.4. Test 4)/Dest[1825 0 R/XYZ 0 679 0]/Prev 2115 0 R/Next 2117 0 R>>endobj
+2117 0 obj<</Parent 2112 0 R/Title(28.3.5. Test 5)/Dest[1825 0 R/XYZ 0 528 0]/Prev 2116 0 R/Next 2118 0 R>>endobj
+2118 0 obj<</Parent 2112 0 R/Title(28.3.6. Test 6)/Dest[1825 0 R/XYZ 0 403 0]/Prev 2117 0 R/Next 2119 0 R>>endobj
+2119 0 obj<</Parent 2112 0 R/Title(28.3.7. Test 7)/Dest[1827 0 R/XYZ 0 786 0]/Prev 2118 0 R/Next 2120 0 R>>endobj
+2120 0 obj<</Parent 2112 0 R/Title(28.3.8. Test 8)/Dest[1827 0 R/XYZ 0 424 0]/Prev 2119 0 R/Next 2121 0 R>>endobj
+2121 0 obj<</Parent 2112 0 R/Title(28.3.9. Test 9)/Dest[1829 0 R/XYZ 0 758 0]/Prev 2120 0 R/Next 2122 0 R>>endobj
+2122 0 obj<</Parent 2112 0 R/Title(28.3.10. Test 10)/Dest[1829 0 R/XYZ 0 567 0]/Prev 2121 0 R/Next 2123 0 R>>endobj
+2123 0 obj<</Parent 2112 0 R/Title(28.3.11. Test 11)/Dest[1829 0 R/XYZ 0 430 0]/Prev 2122 0 R>>endobj
+2124 0 obj<</Parent 2109 0 R/Title(28.4. Still having troubles?)/Dest[1829 0 R/XYZ 0 292 0]/Prev 2112 0 R>>endobj
+2125 0 obj<</Type/Catalog/Pages 1476 0 R/PageLayout/SinglePage/Outlines 1831 0 R/OpenAction[1493 0 R/XYZ null null 0]/PageMode/UseOutlines/PageLabels<</Nums[0<</P(title)>>1<</S/r>>8<</S/D/St 1/P()>>9<</S/D/St 2/P()>>13<</S/D/St 6/P()>>14<</S/D/St 7/P()>>16<</S/D/St 9/P()>>20<</S/D/St 13/P()>>24<</S/D/St 17/P()>>36<</S/D/St 29/P()>>37<</S/D/St 30/P()>>39<</S/D/St 32/P()>>41<</S/D/St 34/P()>>43<</S/D/St 36/P()>>60<</S/D/St 53/P()>>63<</S/D/St 56/P()>>66<</S/D/St 59/P()>>69<</S/D/St 62/P()>>70<</S/D/St 63/P()>>73<</S/D/St 66/P()>>83<</S/D/St 76/P()>>88<</S/D/St 81/P()>>91<</S/D/St 84/P()>>93<</S/D/St 86/P()>>104<</S/D/St 97/P()>>121<</S/D/St 114/P()>>134<</S/D/St 127/P()>>143<</S/D/St 136/P()>>146<</S/D/St 139/P()>>147<</S/D/St 140/P()>>151<</S/D/St 144/P()>>154<</S/D/St 147/P()>>156<</S/D/St 149/P()>>157<</S/D/St 150/P()>>159<</S/D/St 152/P()>>162<</S/D/St 155/P()>>166<</S/D/St 159/P()>>170<</S/D/St 163/P()>>172<</S/D/St 165/P()>>]>>>>endobj
xref
-0 3776
-0000000001 65535 f
-0000000002 00000 f
-0000000003 00000 f
-0000000004 00000 f
-0000000000 00000 f
-0000000009 00000 n
-0000136457 00000 n
-0001055067 00000 n
-0000000051 00000 n
-0000000091 00000 n
-0000140279 00000 n
-0001054958 00000 n
-0000000136 00000 n
-0000000178 00000 n
-0000140403 00000 n
-0001054884 00000 n
-0000000226 00000 n
-0000000259 00000 n
-0000140526 00000 n
-0001054797 00000 n
-0000000307 00000 n
-0000000341 00000 n
-0000144468 00000 n
-0001054710 00000 n
-0000000389 00000 n
-0000000428 00000 n
-0000148740 00000 n
-0001054623 00000 n
-0000000476 00000 n
-0000000514 00000 n
-0000148864 00000 n
-0001054536 00000 n
-0000000562 00000 n
-0000000605 00000 n
-0000154611 00000 n
-0001054449 00000 n
-0000000653 00000 n
-0000000684 00000 n
-0000154735 00000 n
-0001054375 00000 n
-0000000732 00000 n
-0000000768 00000 n
-0000158156 00000 n
-0001054265 00000 n
-0000000814 00000 n
-0000000864 00000 n
-0000158280 00000 n
-0001054191 00000 n
-0000000912 00000 n
-0000000965 00000 n
-0000158403 00000 n
-0001054067 00000 n
-0000001013 00000 n
-0000001053 00000 n
-0000158527 00000 n
-0001053956 00000 n
-0000001106 00000 n
-0000001156 00000 n
-0000158651 00000 n
-0001053895 00000 n
-0000001214 00000 n
-0000001276 00000 n
-0000162385 00000 n
-0001053821 00000 n
-0000001329 00000 n
-0000001358 00000 n
-0000162509 00000 n
-0001053734 00000 n
-0000001406 00000 n
-0000001476 00000 n
-0000162632 00000 n
-0001053647 00000 n
-0000001524 00000 n
-0000001582 00000 n
-0000162756 00000 n
-0001053560 00000 n
-0000001630 00000 n
-0000001726 00000 n
-0000162880 00000 n
-0001053486 00000 n
-0000001774 00000 n
-0000001823 00000 n
-0000163666 00000 n
-0001053359 00000 n
-0000001866 00000 n
-0000001915 00000 n
-0000166659 00000 n
-0001053247 00000 n
-0000001961 00000 n
-0000002010 00000 n
-0000166783 00000 n
-0001053173 00000 n
-0000002058 00000 n
-0000002099 00000 n
-0000166907 00000 n
-0001053086 00000 n
-0000002147 00000 n
-0000002190 00000 n
-0000170588 00000 n
-0001052972 00000 n
-0000002238 00000 n
-0000002279 00000 n
-0000170711 00000 n
-0001052908 00000 n
-0000002333 00000 n
-0000002382 00000 n
-0000174048 00000 n
-0001052778 00000 n
-0000002429 00000 n
-0000002478 00000 n
-0000174173 00000 n
-0001052674 00000 n
-0000002527 00000 n
-0000002580 00000 n
-0000174298 00000 n
-0001052595 00000 n
-0000002634 00000 n
-0000002679 00000 n
-0000174547 00000 n
-0001052502 00000 n
-0000002733 00000 n
-0000002779 00000 n
-0000179862 00000 n
-0001052370 00000 n
-0000002833 00000 n
-0000002880 00000 n
-0000179987 00000 n
-0001052291 00000 n
-0000002939 00000 n
-0000003025 00000 n
-0000183593 00000 n
-0001052212 00000 n
-0000003084 00000 n
-0000003157 00000 n
-0000187287 00000 n
-0001052080 00000 n
-0000003211 00000 n
-0000003258 00000 n
-0000187411 00000 n
-0001052015 00000 n
-0000003317 00000 n
-0000003398 00000 n
-0000187536 00000 n
-0001051936 00000 n
-0000003452 00000 n
-0000003496 00000 n
-0000189919 00000 n
-0001051805 00000 n
-0000003543 00000 n
-0000003615 00000 n
-0000190044 00000 n
-0001051726 00000 n
-0000003664 00000 n
-0000003708 00000 n
-0000190169 00000 n
-0001051633 00000 n
-0000003757 00000 n
-0000003791 00000 n
-0000192905 00000 n
-0001051540 00000 n
-0000003840 00000 n
-0000003903 00000 n
-0000199218 00000 n
-0001051408 00000 n
-0000003952 00000 n
-0000004041 00000 n
-0000203306 00000 n
-0001051329 00000 n
-0000004095 00000 n
-0000004162 00000 n
-0000208020 00000 n
-0001051236 00000 n
-0000004216 00000 n
-0000004289 00000 n
-0000208145 00000 n
-0001051157 00000 n
-0000004343 00000 n
-0000004401 00000 n
-0000212003 00000 n
-0001051025 00000 n
-0000004450 00000 n
-0000004500 00000 n
-0000212128 00000 n
-0001050946 00000 n
-0000004554 00000 n
-0000004623 00000 n
-0000212253 00000 n
-0001050853 00000 n
-0000004677 00000 n
-0000004884 00000 n
-0000212377 00000 n
-0001050760 00000 n
-0000004938 00000 n
-0000005010 00000 n
-0000216554 00000 n
-0001050667 00000 n
-0000005064 00000 n
-0000005177 00000 n
-0000216679 00000 n
-0001050588 00000 n
-0000005231 00000 n
-0000005375 00000 n
-0000216802 00000 n
-0001050470 00000 n
-0000005424 00000 n
-0000005480 00000 n
-0000219993 00000 n
-0001050405 00000 n
-0000005534 00000 n
-0000005602 00000 n
-0000225948 00000 n
-0001050274 00000 n
-0000005649 00000 n
-0000005725 00000 n
-0000226073 00000 n
-0001050195 00000 n
-0000005774 00000 n
-0000005818 00000 n
-0000226198 00000 n
-0001050102 00000 n
-0000005867 00000 n
-0000005901 00000 n
-0000226321 00000 n
-0001049970 00000 n
-0000005950 00000 n
-0000006024 00000 n
-0000230057 00000 n
-0001049891 00000 n
-0000006078 00000 n
-0000006154 00000 n
-0000230182 00000 n
-0001049812 00000 n
-0000006208 00000 n
-0000006257 00000 n
-0000230306 00000 n
-0001049719 00000 n
-0000006306 00000 n
-0000006383 00000 n
-0000230431 00000 n
-0001049601 00000 n
-0000006432 00000 n
-0000006484 00000 n
-0000233419 00000 n
-0001049522 00000 n
-0000006538 00000 n
-0000006602 00000 n
-0000233544 00000 n
-0001049443 00000 n
-0000006656 00000 n
-0000006710 00000 n
-0000235680 00000 n
-0001049312 00000 n
-0000006757 00000 n
-0000006807 00000 n
-0000235805 00000 n
-0001049233 00000 n
-0000006856 00000 n
-0000006899 00000 n
-0000235930 00000 n
-0001049140 00000 n
-0000006948 00000 n
-0000006997 00000 n
-0000239806 00000 n
-0001049008 00000 n
-0000007046 00000 n
-0000007097 00000 n
-0000239931 00000 n
-0001048943 00000 n
-0000007151 00000 n
-0000007192 00000 n
-0000240056 00000 n
-0001048850 00000 n
-0000007241 00000 n
-0000007287 00000 n
-0000241845 00000 n
-0001048757 00000 n
-0000007336 00000 n
-0000007382 00000 n
-0000241970 00000 n
-0001048678 00000 n
-0000007431 00000 n
-0000007460 00000 n
-0000245879 00000 n
-0001048561 00000 n
-0000007507 00000 n
-0000007566 00000 n
-0000246004 00000 n
-0001048482 00000 n
-0000007615 00000 n
-0000007674 00000 n
-0000250585 00000 n
-0001048403 00000 n
-0000007723 00000 n
-0000007789 00000 n
-0000251412 00000 n
-0001048268 00000 n
-0000007833 00000 n
-0000007879 00000 n
-0000254100 00000 n
-0001048150 00000 n
-0000007926 00000 n
-0000007989 00000 n
-0000254225 00000 n
-0001048071 00000 n
-0000008038 00000 n
-0000008079 00000 n
-0000257406 00000 n
-0001047978 00000 n
-0000008128 00000 n
-0000008162 00000 n
-0000261767 00000 n
-0001047846 00000 n
-0000008211 00000 n
-0000008257 00000 n
-0000264971 00000 n
-0001047767 00000 n
-0000008311 00000 n
-0000008366 00000 n
-0000268280 00000 n
-0001047674 00000 n
-0000008420 00000 n
-0000008472 00000 n
-0000268404 00000 n
-0001047581 00000 n
-0000008526 00000 n
-0000008582 00000 n
-0000272543 00000 n
-0001047488 00000 n
-0000008636 00000 n
-0000008692 00000 n
-0000276057 00000 n
-0001047395 00000 n
-0000008746 00000 n
-0000008802 00000 n
-0000276181 00000 n
-0001047302 00000 n
-0000008856 00000 n
-0000008901 00000 n
-0000276306 00000 n
-0001047209 00000 n
-0000008955 00000 n
-0000009017 00000 n
-0000276431 00000 n
-0001047130 00000 n
-0000009071 00000 n
-0000009136 00000 n
-0000281296 00000 n
-0001046998 00000 n
-0000009185 00000 n
-0000009255 00000 n
-0000285270 00000 n
-0001046919 00000 n
-0000009309 00000 n
-0000009359 00000 n
-0000285395 00000 n
-0001046826 00000 n
-0000009413 00000 n
-0000009455 00000 n
-0000289012 00000 n
-0001046747 00000 n
-0000009509 00000 n
-0000009554 00000 n
-0000289137 00000 n
-0001046615 00000 n
-0000009603 00000 n
-0000009640 00000 n
-0000289261 00000 n
-0001046536 00000 n
-0000009694 00000 n
-0000009748 00000 n
-0000289386 00000 n
-0001046457 00000 n
-0000009802 00000 n
-0000009849 00000 n
-0000292429 00000 n
-0001046339 00000 n
-0000009898 00000 n
-0000009952 00000 n
-0000296634 00000 n
-0001046260 00000 n
-0000010006 00000 n
-0000010057 00000 n
-0000296759 00000 n
-0001046167 00000 n
-0000010111 00000 n
-0000010155 00000 n
-0000300271 00000 n
-0001046049 00000 n
-0000010209 00000 n
-0000010258 00000 n
-0000300396 00000 n
-0001045984 00000 n
-0000010317 00000 n
-0000010382 00000 n
-0000310698 00000 n
-0001045852 00000 n
-0000010430 00000 n
-0000010478 00000 n
-0000310823 00000 n
-0001045773 00000 n
-0000010528 00000 n
-0000010565 00000 n
-0000310948 00000 n
-0001045641 00000 n
-0000010615 00000 n
-0000010670 00000 n
-0000317073 00000 n
-0001045562 00000 n
-0000010725 00000 n
-0000010780 00000 n
-0000317198 00000 n
-0001045483 00000 n
-0000010835 00000 n
-0000010899 00000 n
-0000317323 00000 n
-0001045390 00000 n
-0000010949 00000 n
-0000010995 00000 n
-0000322220 00000 n
-0001045297 00000 n
-0000011045 00000 n
-0000011080 00000 n
-0000322345 00000 n
-0001045204 00000 n
-0000011130 00000 n
-0000011158 00000 n
-0000322470 00000 n
-0001045072 00000 n
-0000011208 00000 n
-0000011237 00000 n
-0000322595 00000 n
-0001044993 00000 n
-0000011292 00000 n
-0000011331 00000 n
-0000322719 00000 n
-0001044900 00000 n
-0000011386 00000 n
-0000011440 00000 n
-0000327697 00000 n
-0001044807 00000 n
-0000011495 00000 n
-0000011544 00000 n
-0000327822 00000 n
-0001044714 00000 n
-0000011599 00000 n
-0000011678 00000 n
-0000330418 00000 n
-0001044582 00000 n
+0 2126
+0000000000 65535 f
+0000000015 00000 n
+0000000247 00000 n
+0000001813 00000 n
+0000001887 00000 n
+0000001966 00000 n
+0000002048 00000 n
+0000002126 00000 n
+0000002203 00000 n
+0000002282 00000 n
+0000002365 00000 n
+0000002442 00000 n
+0000002524 00000 n
+0000002609 00000 n
+0000002698 00000 n
+0000002757 00000 n
+0000003184 00000 n
+0000003922 00000 n
+0000004024 00000 n
+0000004127 00000 n
+0000004229 00000 n
+0000004331 00000 n
+0000004433 00000 n
+0000004535 00000 n
+0000004638 00000 n
+0000004741 00000 n
+0000004844 00000 n
+0000004947 00000 n
+0000005050 00000 n
+0000005153 00000 n
+0000005256 00000 n
+0000005359 00000 n
+0000005462 00000 n
+0000005565 00000 n
+0000005667 00000 n
+0000005770 00000 n
+0000005873 00000 n
+0000005976 00000 n
+0000006079 00000 n
+0000006182 00000 n
+0000006285 00000 n
+0000006387 00000 n
+0000006490 00000 n
+0000006593 00000 n
+0000006696 00000 n
+0000006799 00000 n
+0000006902 00000 n
+0000007005 00000 n
+0000007108 00000 n
+0000007211 00000 n
+0000007314 00000 n
+0000007417 00000 n
+0000007520 00000 n
+0000007623 00000 n
+0000007726 00000 n
+0000007829 00000 n
+0000007932 00000 n
+0000008034 00000 n
+0000008135 00000 n
+0000008236 00000 n
+0000008546 00000 n
+0000008648 00000 n
+0000008751 00000 n
+0000008854 00000 n
+0000008957 00000 n
+0000009060 00000 n
+0000009163 00000 n
+0000009266 00000 n
+0000009369 00000 n
+0000009472 00000 n
+0000009574 00000 n
+0000009676 00000 n
+0000009778 00000 n
+0000009881 00000 n
+0000009984 00000 n
+0000010087 00000 n
+0000010190 00000 n
+0000010292 00000 n
+0000010394 00000 n
+0000010497 00000 n
+0000010600 00000 n
+0000010703 00000 n
+0000010806 00000 n
+0000010909 00000 n
+0000011012 00000 n
+0000011115 00000 n
+0000011218 00000 n
+0000011321 00000 n
+0000011424 00000 n
+0000011527 00000 n
+0000011630 00000 n
0000011733 00000 n
-0000011787 00000 n
-0000330541 00000 n
-0001044503 00000 n
-0000011847 00000 n
-0000011898 00000 n
-0000334540 00000 n
-0001044424 00000 n
-0000011958 00000 n
-0000012004 00000 n
-0000337917 00000 n
-0001044331 00000 n
-0000012059 00000 n
-0000012116 00000 n
-0000338042 00000 n
-0001044238 00000 n
-0000012171 00000 n
-0000012223 00000 n
-0000341134 00000 n
-0001044145 00000 n
-0000012278 00000 n
-0000012347 00000 n
-0000344535 00000 n
-0001044066 00000 n
-0000012402 00000 n
-0000012468 00000 n
-0000347065 00000 n
-0001043934 00000 n
-0000012518 00000 n
-0000012548 00000 n
-0000347189 00000 n
-0001043855 00000 n
-0000012603 00000 n
-0000012651 00000 n
-0000347314 00000 n
-0001043762 00000 n
-0000012706 00000 n
-0000012744 00000 n
-0000351664 00000 n
-0001043669 00000 n
-0000012799 00000 n
-0000012873 00000 n
-0000351789 00000 n
-0001043590 00000 n
-0000012928 00000 n
-0000012993 00000 n
-0000351914 00000 n
-0001043511 00000 n
-0000013043 00000 n
-0000013071 00000 n
-0000355209 00000 n
-0001043379 00000 n
-0000013119 00000 n
-0000013198 00000 n
-0000355334 00000 n
-0001043300 00000 n
-0000013248 00000 n
-0000013340 00000 n
-0000355459 00000 n
-0001043207 00000 n
-0000013390 00000 n
-0000013457 00000 n
-0000355584 00000 n
-0001043114 00000 n
-0000013507 00000 n
-0000013554 00000 n
-0000360077 00000 n
-0001042982 00000 n
-0000013604 00000 n
-0000013666 00000 n
-0000360201 00000 n
-0001042903 00000 n
-0000013721 00000 n
-0000013764 00000 n
-0000360326 00000 n
-0001042824 00000 n
-0000013819 00000 n
-0000013867 00000 n
-0000364230 00000 n
-0001042731 00000 n
-0000013917 00000 n
-0000013981 00000 n
-0000364355 00000 n
-0001042638 00000 n
-0000014031 00000 n
-0000014114 00000 n
-0000369138 00000 n
-0001042559 00000 n
-0000014164 00000 n
-0000014247 00000 n
-0000373360 00000 n
-0001042466 00000 n
-0000014295 00000 n
-0000014343 00000 n
-0000378699 00000 n
-0001042334 00000 n
-0000014391 00000 n
-0000014430 00000 n
-0000378824 00000 n
-0001042255 00000 n
-0000014480 00000 n
-0000014517 00000 n
-0000378949 00000 n
-0001042123 00000 n
-0000014567 00000 n
-0000014605 00000 n
-0000383311 00000 n
-0001042044 00000 n
-0000014660 00000 n
-0000014707 00000 n
-0000387076 00000 n
-0001041951 00000 n
-0000014762 00000 n
-0000014826 00000 n
-0000390130 00000 n
-0001041858 00000 n
-0000014881 00000 n
-0000014942 00000 n
-0000393924 00000 n
-0001041765 00000 n
-0000014997 00000 n
-0000015066 00000 n
-0000397165 00000 n
-0001041686 00000 n
-0000015121 00000 n
-0000015171 00000 n
-0000397290 00000 n
-0001041554 00000 n
-0000015221 00000 n
-0000015266 00000 n
-0000397415 00000 n
-0001041475 00000 n
-0000015321 00000 n
-0000015365 00000 n
-0000400877 00000 n
-0001041382 00000 n
-0000015420 00000 n
-0000015479 00000 n
-0000401002 00000 n
-0001041289 00000 n
-0000015534 00000 n
-0000015580 00000 n
-0000401127 00000 n
-0001041210 00000 n
-0000015635 00000 n
-0000015685 00000 n
-0000403963 00000 n
-0001041092 00000 n
-0000015735 00000 n
-0000015769 00000 n
-0000404088 00000 n
-0001041013 00000 n
-0000015824 00000 n
-0000015863 00000 n
-0000406849 00000 n
-0001040920 00000 n
-0000015918 00000 n
-0000015971 00000 n
-0000409623 00000 n
-0001040827 00000 n
-0000016026 00000 n
-0000016077 00000 n
-0000409748 00000 n
-0001040734 00000 n
-0000016132 00000 n
-0000016196 00000 n
-0000413408 00000 n
-0001040641 00000 n
-0000016251 00000 n
-0000016297 00000 n
-0000413533 00000 n
-0001040548 00000 n
-0000016352 00000 n
-0000016403 00000 n
-0000415543 00000 n
-0001040455 00000 n
-0000016458 00000 n
-0000016507 00000 n
-0000415668 00000 n
-0001040362 00000 n
-0000016562 00000 n
-0000016606 00000 n
-0000415793 00000 n
-0001040283 00000 n
-0000016661 00000 n
-0000016702 00000 n
-0000419441 00000 n
-0001040150 00000 n
-0000016750 00000 n
-0000016794 00000 n
-0000419566 00000 n
-0001040071 00000 n
-0000016844 00000 n
-0000016881 00000 n
-0000419691 00000 n
-0001039978 00000 n
-0000016931 00000 n
-0000016985 00000 n
-0000423132 00000 n
-0001039885 00000 n
-0000017035 00000 n
-0000017089 00000 n
-0000433674 00000 n
-0001039792 00000 n
-0000017139 00000 n
-0000017196 00000 n
-0000436639 00000 n
-0001039699 00000 n
-0000017246 00000 n
-0000017319 00000 n
-0000436764 00000 n
-0001039606 00000 n
-0000017369 00000 n
-0000017429 00000 n
-0000441445 00000 n
-0001039474 00000 n
-0000017479 00000 n
+0000011836 00000 n
+0000011938 00000 n
+0000012041 00000 n
+0000012144 00000 n
+0000012247 00000 n
+0000012350 00000 n
+0000012453 00000 n
+0000012556 00000 n
+0000012658 00000 n
+0000012760 00000 n
+0000012862 00000 n
+0000013175 00000 n
+0000013278 00000 n
+0000013382 00000 n
+0000013486 00000 n
+0000013590 00000 n
+0000013694 00000 n
+0000013798 00000 n
+0000013902 00000 n
+0000014006 00000 n
+0000014110 00000 n
+0000014214 00000 n
+0000014317 00000 n
+0000014421 00000 n
+0000014525 00000 n
+0000014629 00000 n
+0000014732 00000 n
+0000014835 00000 n
+0000014938 00000 n
+0000015042 00000 n
+0000015146 00000 n
+0000015250 00000 n
+0000015354 00000 n
+0000015458 00000 n
+0000015562 00000 n
+0000015666 00000 n
+0000015770 00000 n
+0000015874 00000 n
+0000015978 00000 n
+0000016082 00000 n
+0000016186 00000 n
+0000016290 00000 n
+0000016394 00000 n
+0000016498 00000 n
+0000016602 00000 n
+0000016706 00000 n
+0000016810 00000 n
+0000016913 00000 n
+0000017017 00000 n
+0000017121 00000 n
+0000017225 00000 n
+0000017329 00000 n
+0000017432 00000 n
0000017534 00000 n
-0000444574 00000 n
-0001039409 00000 n
-0000017589 00000 n
-0000017626 00000 n
-0000448944 00000 n
-0001039316 00000 n
-0000017676 00000 n
-0000017723 00000 n
-0000460436 00000 n
-0001039184 00000 n
-0000017773 00000 n
-0000017828 00000 n
-0000460561 00000 n
-0001039119 00000 n
-0000017883 00000 n
-0000017932 00000 n
-0000469056 00000 n
-0001039026 00000 n
-0000017983 00000 n
-0000018053 00000 n
-0000486416 00000 n
-0001038933 00000 n
-0000018104 00000 n
-0000018174 00000 n
-0000490103 00000 n
-0001038854 00000 n
-0000018225 00000 n
-0000018284 00000 n
-0000495540 00000 n
-0001038722 00000 n
-0000018332 00000 n
+0000017636 00000 n
+0000017997 00000 n
+0000018100 00000 n
+0000018204 00000 n
+0000018308 00000 n
0000018411 00000 n
-0000495665 00000 n
-0001038643 00000 n
-0000018461 00000 n
-0000018494 00000 n
-0000495790 00000 n
-0001038550 00000 n
-0000018544 00000 n
-0000018581 00000 n
-0000495915 00000 n
-0001038418 00000 n
-0000018631 00000 n
-0000018677 00000 n
-0000499967 00000 n
-0001038353 00000 n
-0000018732 00000 n
-0000018770 00000 n
-0000500092 00000 n
-0001038221 00000 n
-0000018820 00000 n
-0000018862 00000 n
-0000500217 00000 n
-0001038142 00000 n
-0000018917 00000 n
-0000018976 00000 n
-0000504404 00000 n
-0001038049 00000 n
-0000019031 00000 n
-0000019093 00000 n
-0000504529 00000 n
-0001037956 00000 n
-0000019148 00000 n
-0000019194 00000 n
-0000504654 00000 n
-0001037863 00000 n
-0000019249 00000 n
-0000019308 00000 n
-0000508888 00000 n
-0001037770 00000 n
-0000019363 00000 n
-0000019418 00000 n
-0000509013 00000 n
-0001037691 00000 n
-0000019473 00000 n
-0000019514 00000 n
-0000509138 00000 n
-0001037559 00000 n
-0000019564 00000 n
-0000019619 00000 n
-0000509263 00000 n
-0001037480 00000 n
-0000019674 00000 n
-0000019713 00000 n
-0000513616 00000 n
-0001037387 00000 n
-0000019768 00000 n
-0000019807 00000 n
-0000513741 00000 n
-0001037269 00000 n
-0000019862 00000 n
-0000019907 00000 n
-0000516912 00000 n
-0001037190 00000 n
-0000019967 00000 n
-0000020023 00000 n
-0000517037 00000 n
-0001037097 00000 n
-0000020083 00000 n
-0000020182 00000 n
-0000517162 00000 n
-0001037004 00000 n
-0000020242 00000 n
-0000020289 00000 n
-0000520126 00000 n
-0001036911 00000 n
-0000020349 00000 n
-0000020396 00000 n
-0000520251 00000 n
-0001036818 00000 n
-0000020456 00000 n
-0000020524 00000 n
-0000520376 00000 n
-0001036725 00000 n
-0000020584 00000 n
-0000020654 00000 n
-0000524885 00000 n
-0001036632 00000 n
-0000020714 00000 n
-0000020773 00000 n
-0000529906 00000 n
-0001036553 00000 n
-0000020833 00000 n
-0000020887 00000 n
-0000537324 00000 n
-0001036460 00000 n
-0000020937 00000 n
-0000020973 00000 n
-0000537449 00000 n
-0001036381 00000 n
-0000021023 00000 n
-0000021058 00000 n
-0000540923 00000 n
-0001036249 00000 n
-0000021106 00000 n
-0000021157 00000 n
-0000541048 00000 n
-0001036131 00000 n
-0000021207 00000 n
-0000021271 00000 n
-0000541172 00000 n
-0001036027 00000 n
-0000021326 00000 n
-0000021381 00000 n
-0000541297 00000 n
-0001035948 00000 n
-0000021441 00000 n
-0000021500 00000 n
-0000541547 00000 n
-0001035869 00000 n
-0000021560 00000 n
-0000021604 00000 n
-0000546151 00000 n
-0001035776 00000 n
-0000021654 00000 n
-0000021707 00000 n
-0000548879 00000 n
-0001035658 00000 n
-0000021757 00000 n
-0000021808 00000 n
-0000550778 00000 n
-0001035593 00000 n
-0000021863 00000 n
-0000021931 00000 n
-0000555957 00000 n
-0001035461 00000 n
-0000021979 00000 n
-0000022029 00000 n
-0000556082 00000 n
-0001035343 00000 n
-0000022079 00000 n
-0000022141 00000 n
-0000556207 00000 n
-0001035264 00000 n
-0000022196 00000 n
-0000022245 00000 n
-0000560782 00000 n
-0001035132 00000 n
-0000022300 00000 n
-0000022357 00000 n
-0000560907 00000 n
-0001035067 00000 n
-0000022417 00000 n
-0000022462 00000 n
-0000561032 00000 n
-0001034949 00000 n
-0000022517 00000 n
-0000022586 00000 n
-0000564926 00000 n
-0001034884 00000 n
-0000022646 00000 n
-0000022724 00000 n
-0000568861 00000 n
-0001034752 00000 n
-0000022774 00000 n
-0000022829 00000 n
-0000568986 00000 n
-0001034673 00000 n
-0000022884 00000 n
-0000022932 00000 n
-0000572263 00000 n
-0001034594 00000 n
-0000022987 00000 n
-0000023030 00000 n
-0000572388 00000 n
-0001034515 00000 n
-0000023080 00000 n
-0000023149 00000 n
-0000575644 00000 n
-0001034383 00000 n
-0000023197 00000 n
-0000023246 00000 n
-0000575769 00000 n
-0001034265 00000 n
-0000023296 00000 n
-0000023337 00000 n
-0000575894 00000 n
-0001034147 00000 n
-0000023392 00000 n
-0000023459 00000 n
-0000576019 00000 n
-0001034068 00000 n
-0000023519 00000 n
-0000023570 00000 n
-0000578933 00000 n
-0001033975 00000 n
-0000023630 00000 n
-0000023688 00000 n
-0000579058 00000 n
-0001033882 00000 n
-0000023748 00000 n
-0000023833 00000 n
-0000579183 00000 n
-0001033803 00000 n
-0000023893 00000 n
-0000023955 00000 n
-0000582838 00000 n
-0001033671 00000 n
-0000024010 00000 n
-0000024085 00000 n
-0000582963 00000 n
-0001033592 00000 n
-0000024145 00000 n
-0000024203 00000 n
-0000591351 00000 n
-0001033499 00000 n
-0000024263 00000 n
-0000024315 00000 n
-0000591476 00000 n
-0001033420 00000 n
+0000018515 00000 n
+0000018619 00000 n
+0000018723 00000 n
+0000018826 00000 n
+0000018930 00000 n
+0000019034 00000 n
+0000019137 00000 n
+0000019241 00000 n
+0000019345 00000 n
+0000019449 00000 n
+0000019553 00000 n
+0000019657 00000 n
+0000019761 00000 n
+0000019865 00000 n
+0000019969 00000 n
+0000020073 00000 n
+0000020177 00000 n
+0000020281 00000 n
+0000020385 00000 n
+0000020489 00000 n
+0000020593 00000 n
+0000020697 00000 n
+0000020801 00000 n
+0000020905 00000 n
+0000021009 00000 n
+0000021113 00000 n
+0000021217 00000 n
+0000021321 00000 n
+0000021425 00000 n
+0000021528 00000 n
+0000021632 00000 n
+0000021736 00000 n
+0000021840 00000 n
+0000021944 00000 n
+0000022048 00000 n
+0000022152 00000 n
+0000022256 00000 n
+0000022359 00000 n
+0000022712 00000 n
+0000022815 00000 n
+0000022919 00000 n
+0000023023 00000 n
+0000023127 00000 n
+0000023231 00000 n
+0000023335 00000 n
+0000023439 00000 n
+0000023543 00000 n
+0000023647 00000 n
+0000023751 00000 n
+0000023855 00000 n
+0000023959 00000 n
+0000024063 00000 n
+0000024167 00000 n
+0000024271 00000 n
0000024375 00000 n
-0000024432 00000 n
-0000598835 00000 n
-0001033327 00000 n
-0000024487 00000 n
-0000024574 00000 n
-0000598960 00000 n
-0001033209 00000 n
-0000024629 00000 n
-0000024711 00000 n
-0000599085 00000 n
-0001033130 00000 n
-0000024771 00000 n
-0000024836 00000 n
-0000602676 00000 n
-0001033037 00000 n
-0000024896 00000 n
-0000024939 00000 n
-0000602801 00000 n
-0001032944 00000 n
-0000024999 00000 n
-0000025040 00000 n
-0000602926 00000 n
-0001032865 00000 n
-0000025100 00000 n
-0000025136 00000 n
-0000603051 00000 n
-0001032772 00000 n
-0000025186 00000 n
-0000025229 00000 n
-0000603176 00000 n
-0001032679 00000 n
-0000025279 00000 n
-0000025336 00000 n
-0000607171 00000 n
-0001032561 00000 n
-0000025386 00000 n
-0000025444 00000 n
-0000607296 00000 n
-0001032443 00000 n
-0000025499 00000 n
-0000025542 00000 n
-0000607421 00000 n
-0001032378 00000 n
-0000025602 00000 n
-0000025680 00000 n
-0000611194 00000 n
-0001032285 00000 n
-0000025735 00000 n
-0000025788 00000 n
-0000616978 00000 n
-0001032206 00000 n
-0000025843 00000 n
-0000025888 00000 n
-0000624534 00000 n
-0001032073 00000 n
-0000025936 00000 n
-0000025990 00000 n
-0000624659 00000 n
-0001031994 00000 n
-0000026040 00000 n
-0000026094 00000 n
-0000628180 00000 n
-0001031862 00000 n
-0000026144 00000 n
-0000026211 00000 n
-0000628305 00000 n
-0001031783 00000 n
-0000026266 00000 n
-0000026356 00000 n
-0000628429 00000 n
-0001031704 00000 n
-0000026411 00000 n
-0000026507 00000 n
-0000628553 00000 n
-0001031586 00000 n
+0000024479 00000 n
+0000024583 00000 n
+0000024686 00000 n
+0000024790 00000 n
+0000024894 00000 n
+0000024998 00000 n
+0000025102 00000 n
+0000025206 00000 n
+0000025310 00000 n
+0000025414 00000 n
+0000025518 00000 n
+0000025622 00000 n
+0000025726 00000 n
+0000025830 00000 n
+0000025934 00000 n
+0000026037 00000 n
+0000026141 00000 n
+0000026245 00000 n
+0000026349 00000 n
+0000026453 00000 n
0000026557 00000 n
-0000026622 00000 n
-0000628678 00000 n
-0001031507 00000 n
-0000026677 00000 n
-0000026734 00000 n
-0000632363 00000 n
-0001031427 00000 n
-0000026789 00000 n
-0000026846 00000 n
-0000635258 00000 n
-0001031289 00000 n
-0000026895 00000 n
-0000026973 00000 n
-0000635384 00000 n
-0001031164 00000 n
-0000027024 00000 n
-0000027063 00000 n
-0000641538 00000 n
-0001031080 00000 n
-0000027119 00000 n
+0000026661 00000 n
+0000026765 00000 n
+0000026869 00000 n
+0000026972 00000 n
+0000027074 00000 n
0000027176 00000 n
-0000644338 00000 n
-0001030955 00000 n
-0000027232 00000 n
-0000027308 00000 n
-0000646566 00000 n
-0001030871 00000 n
-0000027369 00000 n
-0000027436 00000 n
-0000646692 00000 n
-0001030772 00000 n
-0000027497 00000 n
-0000027559 00000 n
-0000649022 00000 n
-0001030673 00000 n
-0000027620 00000 n
-0000027679 00000 n
-0000649148 00000 n
-0001030589 00000 n
-0000027740 00000 n
-0000027813 00000 n
-0000649270 00000 n
-0001030505 00000 n
-0000027864 00000 n
-0000027916 00000 n
-0000651887 00000 n
-0001030366 00000 n
-0000027965 00000 n
-0000028010 00000 n
-0000652013 00000 n
-0001030282 00000 n
-0000028061 00000 n
-0000028117 00000 n
-0000652139 00000 n
-0001030142 00000 n
-0000028168 00000 n
-0000028210 00000 n
-0000652265 00000 n
-0001030058 00000 n
-0000028266 00000 n
-0000028299 00000 n
-0000652391 00000 n
-0001029959 00000 n
-0000028355 00000 n
-0000028396 00000 n
-0000655062 00000 n
-0001029860 00000 n
-0000028452 00000 n
-0000028487 00000 n
-0000655188 00000 n
-0001029776 00000 n
-0000028543 00000 n
-0000028579 00000 n
-0000655314 00000 n
-0001029651 00000 n
-0000028630 00000 n
-0000028687 00000 n
-0000658032 00000 n
-0001029567 00000 n
-0000028743 00000 n
-0000028781 00000 n
-0000658158 00000 n
-0001029483 00000 n
-0000028837 00000 n
-0000028870 00000 n
-0000662094 00000 n
-0001029344 00000 n
-0000028919 00000 n
-0000029000 00000 n
-0000662220 00000 n
-0001029234 00000 n
-0000029051 00000 n
-0000029089 00000 n
-0000663942 00000 n
-0001029165 00000 n
-0000029145 00000 n
-0000029178 00000 n
-0000666814 00000 n
-0001029026 00000 n
-0000029227 00000 n
-0000029293 00000 n
-0000666940 00000 n
-0001028901 00000 n
-0000029344 00000 n
-0000029412 00000 n
-0000670613 00000 n
-0001028817 00000 n
-0000029468 00000 n
-0000029506 00000 n
-0000670739 00000 n
-0001028718 00000 n
-0000029562 00000 n
-0000029606 00000 n
-0000673057 00000 n
-0001028619 00000 n
-0000029662 00000 n
-0000029704 00000 n
-0000673183 00000 n
-0001028535 00000 n
-0000029760 00000 n
-0000029806 00000 n
-0000677013 00000 n
-0001028410 00000 n
-0000029857 00000 n
-0000029935 00000 n
-0000680954 00000 n
-0001028326 00000 n
-0000029991 00000 n
-0000030041 00000 n
-0000681080 00000 n
-0001028227 00000 n
-0000030097 00000 n
-0000030141 00000 n
-0000686168 00000 n
-0001028128 00000 n
-0000030197 00000 n
-0000030235 00000 n
-0000686294 00000 n
-0001028029 00000 n
-0000030291 00000 n
-0000030329 00000 n
-0000686420 00000 n
-0001027945 00000 n
-0000030385 00000 n
-0000030424 00000 n
-0000690076 00000 n
-0001027806 00000 n
-0000030473 00000 n
-0000030511 00000 n
-0000690202 00000 n
-0001027722 00000 n
-0000030562 00000 n
-0000030600 00000 n
-0000690328 00000 n
-0001027623 00000 n
-0000030651 00000 n
-0000030704 00000 n
-0000690454 00000 n
-0001027524 00000 n
-0000030755 00000 n
-0000030807 00000 n
-0000693282 00000 n
-0001027425 00000 n
-0000030858 00000 n
-0000030900 00000 n
-0000693408 00000 n
-0001027326 00000 n
-0000030951 00000 n
-0000031003 00000 n
-0000693532 00000 n
-0001027227 00000 n
-0000031054 00000 n
-0000031095 00000 n
-0000695170 00000 n
-0001027143 00000 n
-0000031146 00000 n
-0000031187 00000 n
-0000698776 00000 n
-0001027004 00000 n
-0000031236 00000 n
-0000031276 00000 n
-0000698902 00000 n
-0001026920 00000 n
-0000031327 00000 n
-0000031383 00000 n
-0000699028 00000 n
-0001026821 00000 n
-0000031434 00000 n
-0000031478 00000 n
-0000699154 00000 n
-0001026722 00000 n
-0000031529 00000 n
-0000031580 00000 n
-0000701746 00000 n
-0001026638 00000 n
-0000031631 00000 n
-0000031674 00000 n
-0000705658 00000 n
-0001026514 00000 n
-0000031723 00000 n
-0000031770 00000 n
-0000705784 00000 n
-0001026430 00000 n
-0000031821 00000 n
-0000031857 00000 n
-0000705910 00000 n
-0001026331 00000 n
-0000031908 00000 n
-0000031969 00000 n
-0000709687 00000 n
-0001026191 00000 n
-0000032020 00000 n
-0000032099 00000 n
-0000715147 00000 n
-0001026107 00000 n
-0000032155 00000 n
-0000032210 00000 n
-0000717838 00000 n
-0001026023 00000 n
-0000032266 00000 n
-0000032316 00000 n
-0000717964 00000 n
-0001025924 00000 n
-0000032367 00000 n
-0000032419 00000 n
-0000721634 00000 n
-0001025840 00000 n
-0000032470 00000 n
-0000032514 00000 n
-0000722377 00000 n
-0001025701 00000 n
-0000032559 00000 n
-0000032598 00000 n
-0000725208 00000 n
-0001025576 00000 n
-0000032647 00000 n
-0000032690 00000 n
-0000725334 00000 n
-0001025492 00000 n
-0000032741 00000 n
-0000032779 00000 n
-0000725460 00000 n
-0001025393 00000 n
-0000032830 00000 n
-0000032867 00000 n
-0000729292 00000 n
-0001025294 00000 n
-0000032918 00000 n
-0000032953 00000 n
-0000743520 00000 n
-0001025210 00000 n
-0000033004 00000 n
-0000033052 00000 n
-0000747284 00000 n
-0001025070 00000 n
-0000033101 00000 n
-0000033161 00000 n
-0000747410 00000 n
-0001024986 00000 n
-0000033212 00000 n
-0000033255 00000 n
-0000747536 00000 n
-0001024887 00000 n
-0000033306 00000 n
-0000033401 00000 n
-0000752216 00000 n
-0001024788 00000 n
-0000033452 00000 n
-0000033490 00000 n
-0000756869 00000 n
-0001024689 00000 n
-0000033541 00000 n
+0000027278 00000 n
+0000027647 00000 n
+0000027750 00000 n
+0000027854 00000 n
+0000027958 00000 n
+0000028062 00000 n
+0000028166 00000 n
+0000028270 00000 n
+0000028374 00000 n
+0000028478 00000 n
+0000028582 00000 n
+0000028685 00000 n
+0000028789 00000 n
+0000028893 00000 n
+0000028997 00000 n
+0000029101 00000 n
+0000029205 00000 n
+0000029309 00000 n
+0000029413 00000 n
+0000029516 00000 n
+0000029620 00000 n
+0000029724 00000 n
+0000029828 00000 n
+0000029932 00000 n
+0000030036 00000 n
+0000030140 00000 n
+0000030243 00000 n
+0000030347 00000 n
+0000030451 00000 n
+0000030554 00000 n
+0000030657 00000 n
+0000030761 00000 n
+0000030865 00000 n
+0000030969 00000 n
+0000031073 00000 n
+0000031177 00000 n
+0000031281 00000 n
+0000031384 00000 n
+0000031488 00000 n
+0000031592 00000 n
+0000031696 00000 n
+0000031799 00000 n
+0000031901 00000 n
+0000032003 00000 n
+0000032356 00000 n
+0000032459 00000 n
+0000032563 00000 n
+0000032667 00000 n
+0000032771 00000 n
+0000032875 00000 n
+0000032979 00000 n
+0000033083 00000 n
+0000033187 00000 n
+0000033291 00000 n
+0000033394 00000 n
+0000033498 00000 n
0000033602 00000 n
-0000756995 00000 n
-0001024605 00000 n
-0000033653 00000 n
-0000033710 00000 n
-0000760756 00000 n
-0001024480 00000 n
-0000033759 00000 n
-0000033797 00000 n
-0000760882 00000 n
-0001024396 00000 n
-0000033848 00000 n
-0000033886 00000 n
-0000761008 00000 n
-0001024297 00000 n
-0000033937 00000 n
-0000033975 00000 n
-0000761134 00000 n
-0001024198 00000 n
-0000034026 00000 n
-0000034064 00000 n
-0000765093 00000 n
-0001024099 00000 n
-0000034115 00000 n
-0000034156 00000 n
-0000765219 00000 n
-0001024000 00000 n
-0000034207 00000 n
-0000034263 00000 n
-0000765345 00000 n
-0001023916 00000 n
-0000034314 00000 n
-0000034347 00000 n
-0000766079 00000 n
-0001023791 00000 n
-0000034392 00000 n
-0000034425 00000 n
-0000770338 00000 n
-0001023666 00000 n
-0000034474 00000 n
-0000034518 00000 n
-0000770464 00000 n
-0001023541 00000 n
-0000034569 00000 n
-0000034627 00000 n
-0000770590 00000 n
-0001023457 00000 n
-0000034683 00000 n
-0000034723 00000 n
-0000770716 00000 n
-0001023332 00000 n
-0000034779 00000 n
-0000034830 00000 n
-0000770842 00000 n
-0001023248 00000 n
-0000034891 00000 n
-0000034938 00000 n
-0000770968 00000 n
-0001023164 00000 n
-0000034999 00000 n
-0000035043 00000 n
-0000774825 00000 n
-0001023065 00000 n
-0000035094 00000 n
-0000035165 00000 n
-0000774950 00000 n
-0001022966 00000 n
-0000035216 00000 n
-0000035273 00000 n
-0000777656 00000 n
-0001022826 00000 n
-0000035324 00000 n
-0000035371 00000 n
-0000777782 00000 n
-0001022716 00000 n
-0000035427 00000 n
-0000035500 00000 n
-0000780553 00000 n
-0001022632 00000 n
-0000035561 00000 n
-0000035634 00000 n
-0000780679 00000 n
-0001022548 00000 n
-0000035695 00000 n
-0000035768 00000 n
-0000780805 00000 n
-0001022423 00000 n
-0000035819 00000 n
-0000035871 00000 n
-0000780931 00000 n
-0001022339 00000 n
-0000035927 00000 n
-0000035979 00000 n
-0000783648 00000 n
-0001022255 00000 n
-0000036035 00000 n
-0000036099 00000 n
-0000787681 00000 n
-0001022115 00000 n
-0000036148 00000 n
-0000036209 00000 n
-0000787807 00000 n
-0001021990 00000 n
-0000036260 00000 n
-0000036314 00000 n
-0000787933 00000 n
-0001021865 00000 n
-0000036370 00000 n
+0000033706 00000 n
+0000033810 00000 n
+0000033914 00000 n
+0000034018 00000 n
+0000034122 00000 n
+0000034226 00000 n
+0000034329 00000 n
+0000034433 00000 n
+0000034537 00000 n
+0000034641 00000 n
+0000034745 00000 n
+0000034849 00000 n
+0000034953 00000 n
+0000035056 00000 n
+0000035160 00000 n
+0000035264 00000 n
+0000035368 00000 n
+0000035472 00000 n
+0000035576 00000 n
+0000035680 00000 n
+0000035784 00000 n
+0000035888 00000 n
+0000035992 00000 n
+0000036096 00000 n
+0000036200 00000 n
+0000036304 00000 n
0000036408 00000 n
-0000791104 00000 n
-0001021781 00000 n
-0000036469 00000 n
0000036512 00000 n
-0000795435 00000 n
-0001021682 00000 n
-0000036573 00000 n
-0000036636 00000 n
-0000795561 00000 n
-0001021583 00000 n
-0000036697 00000 n
-0000036740 00000 n
-0000798271 00000 n
-0001021484 00000 n
-0000036801 00000 n
-0000036857 00000 n
-0000798397 00000 n
-0001021400 00000 n
-0000036918 00000 n
-0000036971 00000 n
-0000798523 00000 n
-0001021316 00000 n
-0000037027 00000 n
-0000037081 00000 n
-0000802462 00000 n
-0001021191 00000 n
-0000037132 00000 n
-0000037175 00000 n
-0000802715 00000 n
-0001021107 00000 n
-0000037231 00000 n
-0000037279 00000 n
-0000802841 00000 n
-0001021023 00000 n
-0000037335 00000 n
-0000037391 00000 n
-0000809673 00000 n
-0001020883 00000 n
-0000037440 00000 n
-0000037475 00000 n
-0000809799 00000 n
-0001020799 00000 n
-0000037526 00000 n
-0000037556 00000 n
-0000809925 00000 n
-0001020700 00000 n
-0000037607 00000 n
-0000037641 00000 n
-0000810051 00000 n
-0001020601 00000 n
-0000037692 00000 n
-0000037722 00000 n
-0000811679 00000 n
-0001020502 00000 n
-0000037773 00000 n
-0000037824 00000 n
-0000814205 00000 n
-0001020362 00000 n
-0000037875 00000 n
-0000037904 00000 n
-0000814331 00000 n
-0001020293 00000 n
-0000037960 00000 n
-0000038009 00000 n
-0000814457 00000 n
-0001020168 00000 n
-0000038060 00000 n
-0000038093 00000 n
-0000814582 00000 n
-0001020084 00000 n
-0000038149 00000 n
-0000038197 00000 n
-0000814708 00000 n
-0001020000 00000 n
-0000038253 00000 n
-0000038301 00000 n
-0000819400 00000 n
-0001019860 00000 n
-0000038350 00000 n
-0000038402 00000 n
-0000819526 00000 n
-0001019776 00000 n
-0000038453 00000 n
-0000038497 00000 n
-0000819652 00000 n
-0001019636 00000 n
-0000038548 00000 n
-0000038584 00000 n
-0000819778 00000 n
-0001019552 00000 n
-0000038640 00000 n
-0000038743 00000 n
-0000824390 00000 n
-0001019453 00000 n
-0000038799 00000 n
-0000038907 00000 n
-0000824516 00000 n
-0001019354 00000 n
-0000038963 00000 n
-0000039064 00000 n
-0000824642 00000 n
-0001019270 00000 n
-0000039120 00000 n
-0000039210 00000 n
-0000824768 00000 n
-0001019130 00000 n
-0000039261 00000 n
-0000039309 00000 n
-0000824894 00000 n
-0001019046 00000 n
-0000039365 00000 n
-0000039431 00000 n
-0000828818 00000 n
-0001018947 00000 n
-0000039487 00000 n
-0000039554 00000 n
-0000828944 00000 n
-0001018848 00000 n
-0000039610 00000 n
-0000039669 00000 n
-0000829069 00000 n
-0001018749 00000 n
-0000039725 00000 n
-0000039779 00000 n
-0000829195 00000 n
-0001018650 00000 n
-0000039835 00000 n
-0000039893 00000 n
-0000829321 00000 n
-0001018566 00000 n
-0000039949 00000 n
-0000039994 00000 n
-0000829447 00000 n
-0001018426 00000 n
-0000040045 00000 n
-0000040086 00000 n
-0000833348 00000 n
-0001018357 00000 n
-0000040142 00000 n
-0000040187 00000 n
-0000833474 00000 n
-0001018258 00000 n
+0000036616 00000 n
+0000036961 00000 n
+0000037014 00000 n
+0000037101 00000 n
+0000037155 00000 n
+0000037241 00000 n
+0000037296 00000 n
+0000037383 00000 n
+0000037450 00000 n
+0000037536 00000 n
+0000037639 00000 n
+0000037743 00000 n
+0000037847 00000 n
+0000037951 00000 n
+0000038055 00000 n
+0000038159 00000 n
+0000038263 00000 n
+0000038367 00000 n
+0000038471 00000 n
+0000038575 00000 n
+0000038679 00000 n
+0000038783 00000 n
+0000038887 00000 n
+0000038991 00000 n
+0000039095 00000 n
+0000039199 00000 n
+0000039303 00000 n
+0000039407 00000 n
+0000039511 00000 n
+0000039615 00000 n
+0000039719 00000 n
+0000039823 00000 n
+0000039927 00000 n
+0000040031 00000 n
+0000040134 00000 n
0000040238 00000 n
-0000040291 00000 n
-0000835019 00000 n
-0001018174 00000 n
0000040342 00000 n
-0000040382 00000 n
-0000838086 00000 n
-0001018034 00000 n
-0000040431 00000 n
-0000040497 00000 n
-0000838212 00000 n
-0001017923 00000 n
-0000040548 00000 n
-0000040600 00000 n
-0000838337 00000 n
-0001017839 00000 n
-0000040656 00000 n
-0000040705 00000 n
-0000841290 00000 n
-0001017740 00000 n
-0000040761 00000 n
-0000040814 00000 n
-0000844924 00000 n
-0001017641 00000 n
-0000040870 00000 n
-0000040916 00000 n
-0000845049 00000 n
-0001017542 00000 n
-0000040972 00000 n
-0000041015 00000 n
-0000848825 00000 n
-0001017443 00000 n
-0000041071 00000 n
-0000041113 00000 n
-0000848951 00000 n
-0001017344 00000 n
-0000041169 00000 n
-0000041214 00000 n
-0000849077 00000 n
-0001017245 00000 n
-0000041270 00000 n
-0000041313 00000 n
-0000849203 00000 n
-0001017146 00000 n
-0000041369 00000 n
-0000041412 00000 n
-0000849328 00000 n
-0001017047 00000 n
-0000041468 00000 n
-0000041509 00000 n
-0000850808 00000 n
-0001016963 00000 n
-0000041566 00000 n
-0000041619 00000 n
-0000854177 00000 n
-0001016838 00000 n
-0000041668 00000 n
-0000041716 00000 n
-0000854303 00000 n
-0001016754 00000 n
-0000041767 00000 n
-0000041804 00000 n
-0000854429 00000 n
-0001016655 00000 n
-0000041855 00000 n
-0000041895 00000 n
-0000854555 00000 n
-0001016556 00000 n
-0000041946 00000 n
-0000041981 00000 n
-0000858041 00000 n
-0001016457 00000 n
-0000042032 00000 n
-0000042066 00000 n
-0000858167 00000 n
-0001016358 00000 n
-0000042117 00000 n
-0000042152 00000 n
-0000858292 00000 n
-0001016259 00000 n
-0000042203 00000 n
-0000042237 00000 n
-0000858418 00000 n
-0001016160 00000 n
-0000042288 00000 n
-0000042323 00000 n
-0000858544 00000 n
-0001016061 00000 n
-0000042374 00000 n
-0000042411 00000 n
-0000859860 00000 n
-0001015977 00000 n
-0000042462 00000 n
-0000042501 00000 n
-0000042880 00000 n
-0000043129 00000 n
-0000042555 00000 n
-0000043003 00000 n
-0000043066 00000 n
-0001008999 00000 n
-0000995475 00000 n
-0001008831 00000 n
-0000995006 00000 n
-0000990297 00000 n
-0000994841 00000 n
-0001009897 00000 n
-0000045598 00000 n
-0000044684 00000 n
-0000043217 00000 n
-0000045535 00000 n
-0000989262 00000 n
-0000970555 00000 n
-0000989097 00000 n
-0000044855 00000 n
-0000969537 00000 n
-0000952871 00000 n
-0000969371 00000 n
-0000045023 00000 n
-0000045195 00000 n
-0000045364 00000 n
-0000046712 00000 n
-0000046321 00000 n
-0000045686 00000 n
-0000046649 00000 n
-0000950938 00000 n
-0000935235 00000 n
-0000950772 00000 n
-0000046465 00000 n
-0000054523 00000 n
-0000048642 00000 n
-0000046814 00000 n
-0000054397 00000 n
-0000054460 00000 n
-0000049083 00000 n
-0000049233 00000 n
-0000049386 00000 n
-0000049541 00000 n
-0000049695 00000 n
-0000049850 00000 n
-0000050005 00000 n
-0000050159 00000 n
-0000050313 00000 n
-0000050468 00000 n
-0000050621 00000 n
-0000050776 00000 n
-0000050931 00000 n
-0000051091 00000 n
-0000051256 00000 n
-0000051415 00000 n
-0000051570 00000 n
-0000051725 00000 n
-0000051879 00000 n
-0000052034 00000 n
-0000052184 00000 n
-0000052337 00000 n
-0000052491 00000 n
-0000052646 00000 n
-0000052801 00000 n
-0000052961 00000 n
-0000053114 00000 n
-0000053269 00000 n
-0000053429 00000 n
-0000053588 00000 n
-0000053747 00000 n
-0000053912 00000 n
-0000054076 00000 n
-0000054234 00000 n
-0000063616 00000 n
-0000056970 00000 n
-0000054611 00000 n
-0000063553 00000 n
-0000934635 00000 n
-0000924949 00000 n
-0000934469 00000 n
-0000057456 00000 n
-0000057616 00000 n
-0000057769 00000 n
-0000057924 00000 n
-0000058079 00000 n
-0000058234 00000 n
-0000058389 00000 n
-0000058549 00000 n
-0000058708 00000 n
-0000058868 00000 n
-0000059023 00000 n
-0000059182 00000 n
-0000059342 00000 n
+0000040446 00000 n
+0000040550 00000 n
+0000040654 00000 n
+0000040758 00000 n
+0000040861 00000 n
+0000040963 00000 n
+0000041065 00000 n
+0000041386 00000 n
+0000041490 00000 n
+0000041594 00000 n
+0000041698 00000 n
+0000041802 00000 n
+0000041906 00000 n
+0000042010 00000 n
+0000042114 00000 n
+0000042218 00000 n
+0000042322 00000 n
+0000042426 00000 n
+0000042530 00000 n
+0000042634 00000 n
+0000042738 00000 n
+0000042842 00000 n
+0000042946 00000 n
+0000043050 00000 n
+0000043154 00000 n
+0000043258 00000 n
+0000043362 00000 n
+0000043466 00000 n
+0000043570 00000 n
+0000043674 00000 n
+0000043778 00000 n
+0000043882 00000 n
+0000043986 00000 n
+0000044089 00000 n
+0000044193 00000 n
+0000044297 00000 n
+0000044401 00000 n
+0000044505 00000 n
+0000044609 00000 n
+0000044713 00000 n
+0000044817 00000 n
+0000044921 00000 n
+0000045025 00000 n
+0000045129 00000 n
+0000045233 00000 n
+0000045337 00000 n
+0000045441 00000 n
+0000045545 00000 n
+0000045649 00000 n
+0000045753 00000 n
+0000045857 00000 n
+0000045961 00000 n
+0000046065 00000 n
+0000046169 00000 n
+0000046273 00000 n
+0000046377 00000 n
+0000046480 00000 n
+0000046582 00000 n
+0000046684 00000 n
+0000047109 00000 n
+0000047213 00000 n
+0000047317 00000 n
+0000047421 00000 n
+0000047525 00000 n
+0000047629 00000 n
+0000047733 00000 n
+0000047837 00000 n
+0000047941 00000 n
+0000048045 00000 n
+0000048149 00000 n
+0000048253 00000 n
+0000048357 00000 n
+0000048461 00000 n
+0000048565 00000 n
+0000048669 00000 n
+0000048773 00000 n
+0000048877 00000 n
+0000048981 00000 n
+0000049085 00000 n
+0000049189 00000 n
+0000049293 00000 n
+0000049397 00000 n
+0000049501 00000 n
+0000049605 00000 n
+0000049709 00000 n
+0000049813 00000 n
+0000049917 00000 n
+0000050021 00000 n
+0000050125 00000 n
+0000050229 00000 n
+0000050333 00000 n
+0000050437 00000 n
+0000050541 00000 n
+0000050645 00000 n
+0000050749 00000 n
+0000050853 00000 n
+0000050957 00000 n
+0000051061 00000 n
+0000051165 00000 n
+0000051269 00000 n
+0000051373 00000 n
+0000051477 00000 n
+0000051581 00000 n
+0000051685 00000 n
+0000051789 00000 n
+0000051893 00000 n
+0000051997 00000 n
+0000052101 00000 n
+0000052204 00000 n
+0000052306 00000 n
+0000052408 00000 n
+0000052833 00000 n
+0000052937 00000 n
+0000053041 00000 n
+0000053145 00000 n
+0000053249 00000 n
+0000053353 00000 n
+0000053457 00000 n
+0000053561 00000 n
+0000053665 00000 n
+0000053769 00000 n
+0000053872 00000 n
+0000053976 00000 n
+0000054080 00000 n
+0000054184 00000 n
+0000054288 00000 n
+0000054392 00000 n
+0000054496 00000 n
+0000054600 00000 n
+0000054704 00000 n
+0000054808 00000 n
+0000054912 00000 n
+0000055016 00000 n
+0000055120 00000 n
+0000055224 00000 n
+0000055328 00000 n
+0000055432 00000 n
+0000055536 00000 n
+0000055640 00000 n
+0000055744 00000 n
+0000055848 00000 n
+0000055952 00000 n
+0000056056 00000 n
+0000056160 00000 n
+0000056264 00000 n
+0000056368 00000 n
+0000056472 00000 n
+0000056576 00000 n
+0000056680 00000 n
+0000056784 00000 n
+0000056888 00000 n
+0000057217 00000 n
+0000057320 00000 n
+0000057424 00000 n
+0000057528 00000 n
+0000057632 00000 n
+0000057736 00000 n
+0000057840 00000 n
+0000057944 00000 n
+0000058048 00000 n
+0000058152 00000 n
+0000058256 00000 n
+0000058360 00000 n
+0000058463 00000 n
+0000058567 00000 n
+0000058671 00000 n
+0000058775 00000 n
+0000058879 00000 n
+0000058983 00000 n
+0000059087 00000 n
+0000059190 00000 n
+0000059294 00000 n
+0000059398 00000 n
0000059502 00000 n
-0000059662 00000 n
-0000059822 00000 n
-0000059976 00000 n
-0000060136 00000 n
-0000060287 00000 n
-0000060441 00000 n
-0000060596 00000 n
-0000060751 00000 n
-0000060911 00000 n
-0000061071 00000 n
-0000061226 00000 n
-0000061381 00000 n
-0000061541 00000 n
-0000061700 00000 n
-0000061853 00000 n
-0000062008 00000 n
-0000062161 00000 n
-0000062316 00000 n
-0000062476 00000 n
-0000062631 00000 n
-0000062786 00000 n
-0000062941 00000 n
-0000063094 00000 n
-0000063249 00000 n
-0000063403 00000 n
-0000074547 00000 n
-0000065955 00000 n
-0000063718 00000 n
-0000074484 00000 n
-0000066540 00000 n
-0000066693 00000 n
-0000066848 00000 n
-0000067003 00000 n
-0000067158 00000 n
-0000067318 00000 n
-0000067478 00000 n
-0000067638 00000 n
-0000067798 00000 n
-0000067957 00000 n
-0000068117 00000 n
-0000068277 00000 n
-0000068436 00000 n
-0000068591 00000 n
-0000068751 00000 n
-0000068911 00000 n
-0000069071 00000 n
-0000069226 00000 n
-0000069386 00000 n
-0000069546 00000 n
-0000069701 00000 n
-0000069860 00000 n
-0000070020 00000 n
-0000070180 00000 n
+0000059606 00000 n
+0000059710 00000 n
+0000059814 00000 n
+0000059918 00000 n
+0000060022 00000 n
+0000060126 00000 n
+0000060230 00000 n
+0000060334 00000 n
+0000060438 00000 n
+0000060542 00000 n
+0000060646 00000 n
+0000060750 00000 n
+0000060854 00000 n
+0000060958 00000 n
+0000061062 00000 n
+0000061166 00000 n
+0000061270 00000 n
+0000061374 00000 n
+0000061478 00000 n
+0000061581 00000 n
+0000061683 00000 n
+0000061785 00000 n
+0000062154 00000 n
+0000062258 00000 n
+0000062283 00000 n
+0000062332 00000 n
+0000062419 00000 n
+0000062444 00000 n
+0000062500 00000 n
+0000062587 00000 n
+0000062656 00000 n
+0000062743 00000 n
+0000062794 00000 n
+0000062881 00000 n
+0000062966 00000 n
+0000063053 00000 n
+0000063109 00000 n
+0000063196 00000 n
+0000063246 00000 n
+0000063333 00000 n
+0000063385 00000 n
+0000063471 00000 n
+0000063544 00000 n
+0000063600 00000 n
+0000063687 00000 n
+0000063735 00000 n
+0000063821 00000 n
+0000063869 00000 n
+0000063956 00000 n
+0000063997 00000 n
+0000064038 00000 n
+0000064125 00000 n
+0000064169 00000 n
+0000064256 00000 n
+0000064301 00000 n
+0000064388 00000 n
+0000064432 00000 n
+0000064519 00000 n
+0000064563 00000 n
+0000064650 00000 n
+0000064692 00000 n
+0000064779 00000 n
+0000064827 00000 n
+0000064914 00000 n
+0000064987 00000 n
+0000065035 00000 n
+0000065120 00000 n
+0000065145 00000 n
+0000065198 00000 n
+0000065282 00000 n
+0000065307 00000 n
+0000065410 00000 n
+0000065514 00000 n
+0000065618 00000 n
+0000065722 00000 n
+0000065826 00000 n
+0000065929 00000 n
+0000066032 00000 n
+0000066136 00000 n
+0000066240 00000 n
+0000066344 00000 n
+0000066448 00000 n
+0000066552 00000 n
+0000066656 00000 n
+0000066760 00000 n
+0000066864 00000 n
+0000066968 00000 n
+0000067072 00000 n
+0000067176 00000 n
+0000067280 00000 n
+0000067384 00000 n
+0000067488 00000 n
+0000067591 00000 n
+0000067695 00000 n
+0000067799 00000 n
+0000067903 00000 n
+0000068007 00000 n
+0000068111 00000 n
+0000068215 00000 n
+0000068319 00000 n
+0000068423 00000 n
+0000068527 00000 n
+0000068630 00000 n
+0000068734 00000 n
+0000068838 00000 n
+0000068942 00000 n
+0000069046 00000 n
+0000069150 00000 n
+0000069254 00000 n
+0000069358 00000 n
+0000069462 00000 n
+0000069566 00000 n
+0000069668 00000 n
+0000069770 00000 n
+0000069872 00000 n
+0000070241 00000 n
0000070345 00000 n
-0000070499 00000 n
-0000070655 00000 n
-0000070811 00000 n
-0000070972 00000 n
-0000071133 00000 n
-0000071289 00000 n
-0000071445 00000 n
-0000071600 00000 n
-0000071755 00000 n
-0000071916 00000 n
-0000072077 00000 n
-0000072237 00000 n
-0000072398 00000 n
-0000072559 00000 n
-0000072725 00000 n
-0000072891 00000 n
+0000070370 00000 n
+0000070418 00000 n
+0000070505 00000 n
+0000070530 00000 n
+0000070578 00000 n
+0000070665 00000 n
+0000070710 00000 n
+0000070796 00000 n
+0000070839 00000 n
+0000070925 00000 n
+0000070966 00000 n
+0000071052 00000 n
+0000071101 00000 n
+0000071187 00000 n
+0000071233 00000 n
+0000071319 00000 n
+0000071364 00000 n
+0000071450 00000 n
+0000071502 00000 n
+0000071588 00000 n
+0000071638 00000 n
+0000071724 00000 n
+0000071770 00000 n
+0000071856 00000 n
+0000071899 00000 n
+0000071985 00000 n
+0000072029 00000 n
+0000072115 00000 n
+0000072158 00000 n
+0000072244 00000 n
+0000072289 00000 n
+0000072375 00000 n
+0000072413 00000 n
+0000072499 00000 n
+0000072541 00000 n
+0000072627 00000 n
+0000072670 00000 n
+0000072756 00000 n
+0000072794 00000 n
+0000072880 00000 n
+0000072922 00000 n
+0000073008 00000 n
0000073052 00000 n
-0000073213 00000 n
-0000073374 00000 n
-0000073535 00000 n
-0000073689 00000 n
-0000073850 00000 n
-0000074011 00000 n
-0000074171 00000 n
-0000074330 00000 n
-0000085294 00000 n
-0000076930 00000 n
-0000074649 00000 n
-0000085231 00000 n
-0000077506 00000 n
-0000077660 00000 n
-0000077816 00000 n
-0000077972 00000 n
-0000078128 00000 n
-0000078284 00000 n
-0000078445 00000 n
-0000078606 00000 n
-0000078762 00000 n
-0000078917 00000 n
-0000079073 00000 n
-0000079226 00000 n
-0000079379 00000 n
-0000079535 00000 n
-0000079691 00000 n
-0000079852 00000 n
-0000080013 00000 n
-0000080174 00000 n
-0000080335 00000 n
-0000080495 00000 n
-0000080651 00000 n
-0000080812 00000 n
-0000080971 00000 n
-0000081131 00000 n
-0000081292 00000 n
-0000081448 00000 n
-0000081609 00000 n
-0000081770 00000 n
-0000081931 00000 n
-0000082092 00000 n
-0000082253 00000 n
-0000082413 00000 n
-0000082573 00000 n
-0000082734 00000 n
-0000082895 00000 n
-0000083049 00000 n
-0000083205 00000 n
-0000083361 00000 n
-0000083517 00000 n
-0000083673 00000 n
-0000083829 00000 n
-0000083985 00000 n
-0000084140 00000 n
-0000084299 00000 n
-0000084454 00000 n
-0000084609 00000 n
-0000084768 00000 n
-0000084923 00000 n
-0000085077 00000 n
-0001010022 00000 n
-0000095363 00000 n
-0000087590 00000 n
-0000085396 00000 n
-0000095300 00000 n
-0000088130 00000 n
-0000088284 00000 n
-0000088439 00000 n
-0000088594 00000 n
-0000088749 00000 n
-0000088909 00000 n
-0000089064 00000 n
-0000089224 00000 n
-0000089384 00000 n
-0000089543 00000 n
-0000089703 00000 n
-0000089863 00000 n
-0000090022 00000 n
-0000090177 00000 n
-0000090337 00000 n
-0000090497 00000 n
-0000090657 00000 n
-0000090822 00000 n
-0000090987 00000 n
-0000091152 00000 n
-0000091316 00000 n
-0000091481 00000 n
-0000091646 00000 n
-0000091811 00000 n
-0000091975 00000 n
-0000092130 00000 n
-0000092285 00000 n
-0000092439 00000 n
-0000092594 00000 n
-0000092754 00000 n
-0000092919 00000 n
-0000093083 00000 n
-0000093237 00000 n
-0000093392 00000 n
-0000093552 00000 n
-0000093706 00000 n
-0000093861 00000 n
-0000094021 00000 n
-0000094181 00000 n
-0000094346 00000 n
-0000094506 00000 n
-0000094671 00000 n
-0000094826 00000 n
-0000094985 00000 n
-0000095145 00000 n
-0000105915 00000 n
-0000097788 00000 n
-0000095465 00000 n
-0000105852 00000 n
-0000098346 00000 n
-0000098500 00000 n
-0000098655 00000 n
-0000098815 00000 n
-0000098980 00000 n
-0000099145 00000 n
-0000099310 00000 n
-0000099475 00000 n
-0000099634 00000 n
-0000099799 00000 n
-0000099964 00000 n
-0000100128 00000 n
-0000100288 00000 n
-0000100448 00000 n
-0000100613 00000 n
-0000100778 00000 n
-0000100943 00000 n
-0000101108 00000 n
-0000101263 00000 n
-0000101417 00000 n
-0000101572 00000 n
-0000101732 00000 n
-0000101897 00000 n
-0000102056 00000 n
-0000102216 00000 n
-0000102370 00000 n
-0000102525 00000 n
-0000102680 00000 n
-0000102840 00000 n
-0000102999 00000 n
-0000103153 00000 n
-0000103313 00000 n
-0000103473 00000 n
-0000103627 00000 n
-0000103782 00000 n
-0000103942 00000 n
-0000104102 00000 n
-0000104267 00000 n
-0000104432 00000 n
-0000104597 00000 n
-0000104762 00000 n
-0000104916 00000 n
-0000105070 00000 n
-0000105224 00000 n
-0000105378 00000 n
-0000105536 00000 n
-0000105694 00000 n
-0000115869 00000 n
-0000108078 00000 n
-0000106017 00000 n
-0000115806 00000 n
-0000108627 00000 n
-0000108787 00000 n
-0000108942 00000 n
-0000109102 00000 n
-0000109262 00000 n
-0000109416 00000 n
-0000109571 00000 n
-0000109731 00000 n
-0000109885 00000 n
-0000110040 00000 n
-0000110199 00000 n
-0000110359 00000 n
-0000110519 00000 n
-0000110679 00000 n
-0000110834 00000 n
-0000110994 00000 n
-0000111154 00000 n
-0000111314 00000 n
-0000111474 00000 n
-0000111633 00000 n
-0000111787 00000 n
-0000111941 00000 n
-0000112095 00000 n
-0000112250 00000 n
-0000112405 00000 n
-0000112560 00000 n
-0000112715 00000 n
-0000112870 00000 n
-0000113024 00000 n
-0000113178 00000 n
-0000113333 00000 n
-0000113488 00000 n
-0000113643 00000 n
-0000113797 00000 n
-0000113952 00000 n
-0000114107 00000 n
-0000114262 00000 n
-0000114422 00000 n
-0000114582 00000 n
-0000114737 00000 n
-0000114891 00000 n
-0000115041 00000 n
-0000115195 00000 n
-0000115349 00000 n
-0000115501 00000 n
-0000115653 00000 n
-0000125988 00000 n
-0000118134 00000 n
-0000115971 00000 n
-0000125925 00000 n
-0000118683 00000 n
+0000073138 00000 n
+0000073185 00000 n
+0000073271 00000 n
+0000073319 00000 n
+0000073406 00000 n
+0000073599 00000 n
+0000073648 00000 n
+0000073734 00000 n
+0000073759 00000 n
+0000073806 00000 n
+0000073893 00000 n
+0000073918 00000 n
+0000074033 00000 n
+0000074120 00000 n
+0000074145 00000 n
+0000074227 00000 n
+0000074314 00000 n
+0000074399 00000 n
+0000074486 00000 n
+0000074541 00000 n
+0000074628 00000 n
+0000074684 00000 n
+0000074771 00000 n
+0000074820 00000 n
+0000074868 00000 n
+0000074955 00000 n
+0000075029 00000 n
+0000075116 00000 n
+0000075184 00000 n
+0000075271 00000 n
+0000075325 00000 n
+0000075412 00000 n
+0000075480 00000 n
+0000075567 00000 n
+0000075641 00000 n
+0000075728 00000 n
+0000075776 00000 n
+0000075863 00000 n
+0000075920 00000 n
+0000076007 00000 n
+0000076088 00000 n
+0000076143 00000 n
+0000076230 00000 n
+0000076311 00000 n
+0000076398 00000 n
+0000076431 00000 n
+0000076484 00000 n
+0000076571 00000 n
+0000076596 00000 n
+0000076644 00000 n
+0000076731 00000 n
+0000076773 00000 n
+0000076860 00000 n
+0000076903 00000 n
+0000076990 00000 n
+0000077040 00000 n
+0000077127 00000 n
+0000077175 00000 n
+0000077262 00000 n
+0000077319 00000 n
+0000077362 00000 n
+0000077449 00000 n
+0000077503 00000 n
+0000077590 00000 n
+0000077635 00000 n
+0000077722 00000 n
+0000077763 00000 n
+0000077820 00000 n
+0000077907 00000 n
+0000078003 00000 n
+0000078089 00000 n
+0000078122 00000 n
+0000078225 00000 n
+0000078329 00000 n
+0000078433 00000 n
+0000078537 00000 n
+0000078641 00000 n
+0000078745 00000 n
+0000078849 00000 n
+0000078953 00000 n
+0000079057 00000 n
+0000079161 00000 n
+0000079265 00000 n
+0000079369 00000 n
+0000079473 00000 n
+0000079577 00000 n
+0000079681 00000 n
+0000079785 00000 n
+0000079889 00000 n
+0000079993 00000 n
+0000080097 00000 n
+0000080200 00000 n
+0000080304 00000 n
+0000080408 00000 n
+0000080512 00000 n
+0000080616 00000 n
+0000080720 00000 n
+0000080824 00000 n
+0000080928 00000 n
+0000081032 00000 n
+0000081136 00000 n
+0000081239 00000 n
+0000081343 00000 n
+0000081447 00000 n
+0000081551 00000 n
+0000081654 00000 n
+0000081758 00000 n
+0000081862 00000 n
+0000081965 00000 n
+0000082069 00000 n
+0000082173 00000 n
+0000082277 00000 n
+0000082381 00000 n
+0000082484 00000 n
+0000082586 00000 n
+0000082688 00000 n
+0000083057 00000 n
+0000083161 00000 n
+0000083265 00000 n
+0000083369 00000 n
+0000083473 00000 n
+0000083577 00000 n
+0000083681 00000 n
+0000083785 00000 n
+0000083889 00000 n
+0000083993 00000 n
+0000084097 00000 n
+0000084201 00000 n
+0000084305 00000 n
+0000084409 00000 n
+0000084513 00000 n
+0000084617 00000 n
+0000084720 00000 n
+0000084824 00000 n
+0000084928 00000 n
+0000085032 00000 n
+0000085136 00000 n
+0000085240 00000 n
+0000085344 00000 n
+0000085448 00000 n
+0000085552 00000 n
+0000085655 00000 n
+0000085759 00000 n
+0000085863 00000 n
+0000085967 00000 n
+0000086071 00000 n
+0000086175 00000 n
+0000086279 00000 n
+0000086383 00000 n
+0000086487 00000 n
+0000086591 00000 n
+0000086695 00000 n
+0000086799 00000 n
+0000086903 00000 n
+0000087007 00000 n
+0000087111 00000 n
+0000087215 00000 n
+0000087319 00000 n
+0000087423 00000 n
+0000087526 00000 n
+0000087630 00000 n
+0000087734 00000 n
+0000087838 00000 n
+0000087942 00000 n
+0000088046 00000 n
+0000088149 00000 n
+0000088251 00000 n
+0000088353 00000 n
+0000088778 00000 n
+0000088882 00000 n
+0000088986 00000 n
+0000089090 00000 n
+0000089194 00000 n
+0000089297 00000 n
+0000089401 00000 n
+0000089505 00000 n
+0000089609 00000 n
+0000089713 00000 n
+0000089817 00000 n
+0000089921 00000 n
+0000090025 00000 n
+0000090129 00000 n
+0000090232 00000 n
+0000090335 00000 n
+0000090439 00000 n
+0000090543 00000 n
+0000090647 00000 n
+0000090751 00000 n
+0000090855 00000 n
+0000090959 00000 n
+0000091063 00000 n
+0000091167 00000 n
+0000091271 00000 n
+0000091375 00000 n
+0000091478 00000 n
+0000091582 00000 n
+0000091686 00000 n
+0000091790 00000 n
+0000091894 00000 n
+0000091998 00000 n
+0000092102 00000 n
+0000092206 00000 n
+0000092309 00000 n
+0000092413 00000 n
+0000092517 00000 n
+0000092621 00000 n
+0000092725 00000 n
+0000092829 00000 n
+0000092933 00000 n
+0000093036 00000 n
+0000093140 00000 n
+0000093244 00000 n
+0000093605 00000 n
+0000093653 00000 n
+0000093740 00000 n
+0000093787 00000 n
+0000093873 00000 n
+0000093920 00000 n
+0000094006 00000 n
+0000094047 00000 n
+0000094092 00000 n
+0000094179 00000 n
+0000094224 00000 n
+0000094310 00000 n
+0000094343 00000 n
+0000094389 00000 n
+0000094474 00000 n
+0000094520 00000 n
+0000094603 00000 n
+0000094636 00000 n
+0000094680 00000 n
+0000094767 00000 n
+0000094818 00000 n
+0000094905 00000 n
+0000094954 00000 n
+0000095041 00000 n
+0000095089 00000 n
+0000095175 00000 n
+0000095224 00000 n
+0000095279 00000 n
+0000095365 00000 n
+0000095390 00000 n
+0000095443 00000 n
+0000095530 00000 n
+0000095580 00000 n
+0000095667 00000 n
+0000095700 00000 n
+0000095819 00000 n
+0000095905 00000 n
+0000095948 00000 n
+0000096035 00000 n
+0000096078 00000 n
+0000096165 00000 n
+0000096206 00000 n
+0000096269 00000 n
+0000096356 00000 n
+0000096414 00000 n
+0000096501 00000 n
+0000096595 00000 n
+0000096681 00000 n
+0000096722 00000 n
+0000096765 00000 n
+0000096851 00000 n
+0000096899 00000 n
+0000096986 00000 n
+0000097027 00000 n
+0000097114 00000 n
+0000097158 00000 n
+0000097245 00000 n
+0000097289 00000 n
+0000097375 00000 n
+0000097432 00000 n
+0000097478 00000 n
+0000097565 00000 n
+0000097590 00000 n
+0000097639 00000 n
+0000097726 00000 n
+0000097780 00000 n
+0000097867 00000 n
+0000097918 00000 n
+0000098005 00000 n
+0000098059 00000 n
+0000098146 00000 n
+0000098196 00000 n
+0000098281 00000 n
+0000098338 00000 n
+0000098388 00000 n
+0000098475 00000 n
+0000098539 00000 n
+0000098626 00000 n
+0000098659 00000 n
+0000098736 00000 n
+0000098822 00000 n
+0000098912 00000 n
+0000098998 00000 n
+0000099087 00000 n
+0000099173 00000 n
+0000099214 00000 n
+0000099285 00000 n
+0000099371 00000 n
+0000099503 00000 n
+0000099589 00000 n
+0000099663 00000 n
+0000099749 00000 n
+0000099846 00000 n
+0000099932 00000 n
+0000099981 00000 n
+0000100046 00000 n
+0000100133 00000 n
+0000100158 00000 n
+0000100223 00000 n
+0000100311 00000 n
+0000100338 00000 n
+0000100401 00000 n
+0000100490 00000 n
+0000100517 00000 n
+0000100567 00000 n
+0000100656 00000 n
+0000100683 00000 n
+0000100732 00000 n
+0000100821 00000 n
+0000100872 00000 n
+0000100958 00000 n
+0000101003 00000 n
+0000101089 00000 n
+0000101134 00000 n
+0000101179 00000 n
+0000101267 00000 n
+0000101318 00000 n
+0000101406 00000 n
+0000101457 00000 n
+0000101545 00000 n
+0000101595 00000 n
+0000101683 00000 n
+0000101731 00000 n
+0000101819 00000 n
+0000101882 00000 n
+0000101972 00000 n
+0000102060 00000 n
+0000102124 00000 n
+0000102212 00000 n
+0000102248 00000 n
+0000102310 00000 n
+0000102398 00000 n
+0000102425 00000 n
+0000102481 00000 n
+0000102570 00000 n
+0000102597 00000 n
+0000102701 00000 n
+0000102806 00000 n
+0000102911 00000 n
+0000103016 00000 n
+0000103121 00000 n
+0000103226 00000 n
+0000103331 00000 n
+0000103435 00000 n
+0000103540 00000 n
+0000103645 00000 n
+0000103750 00000 n
+0000103855 00000 n
+0000103960 00000 n
+0000104065 00000 n
+0000104170 00000 n
+0000104275 00000 n
+0000104380 00000 n
+0000104485 00000 n
+0000104590 00000 n
+0000104695 00000 n
+0000104800 00000 n
+0000104905 00000 n
+0000105009 00000 n
+0000105114 00000 n
+0000105219 00000 n
+0000105324 00000 n
+0000105429 00000 n
+0000105534 00000 n
+0000105639 00000 n
+0000105744 00000 n
+0000105849 00000 n
+0000105953 00000 n
+0000106058 00000 n
+0000106163 00000 n
+0000106268 00000 n
+0000106373 00000 n
+0000106478 00000 n
+0000106583 00000 n
+0000106687 00000 n
+0000106792 00000 n
+0000106897 00000 n
+0000107002 00000 n
+0000107107 00000 n
+0000107212 00000 n
+0000107316 00000 n
+0000107419 00000 n
+0000107522 00000 n
+0000107963 00000 n
+0000108068 00000 n
+0000108173 00000 n
+0000108278 00000 n
+0000108383 00000 n
+0000108488 00000 n
+0000108593 00000 n
+0000108698 00000 n
+0000108779 00000 n
+0000108835 00000 n
+0000108923 00000 n
+0000108992 00000 n
+0000109080 00000 n
+0000109156 00000 n
+0000109245 00000 n
+0000109316 00000 n
+0000109404 00000 n
+0000109484 00000 n
+0000109573 00000 n
+0000109636 00000 n
+0000109719 00000 n
+0000109807 00000 n
+0000109883 00000 n
+0000109972 00000 n
+0000110046 00000 n
+0000110135 00000 n
+0000110214 00000 n
+0000110303 00000 n
+0000110357 00000 n
+0000110406 00000 n
+0000110495 00000 n
+0000110522 00000 n
+0000110571 00000 n
+0000110660 00000 n
+0000110687 00000 n
+0000110737 00000 n
+0000110826 00000 n
+0000110890 00000 n
+0000110979 00000 n
+0000111043 00000 n
+0000111132 00000 n
+0000111187 00000 n
+0000111276 00000 n
+0000111330 00000 n
+0000111399 00000 n
+0000111487 00000 n
+0000111543 00000 n
+0000111632 00000 n
+0000111668 00000 n
+0000111717 00000 n
+0000111806 00000 n
+0000111871 00000 n
+0000111960 00000 n
+0000112016 00000 n
+0000112105 00000 n
+0000112153 00000 n
+0000112242 00000 n
+0000112296 00000 n
+0000112351 00000 n
+0000112440 00000 n
+0000112495 00000 n
+0000112584 00000 n
+0000112620 00000 n
+0000112656 00000 n
+0000112692 00000 n
+0000118297 00000 n
+0000118342 00000 n
+0000118387 00000 n
+0000118432 00000 n
+0000118477 00000 n
+0000118522 00000 n
+0000118567 00000 n
+0000118612 00000 n
+0000118657 00000 n
+0000118702 00000 n
+0000118747 00000 n
+0000118792 00000 n
0000118837 00000 n
-0000118992 00000 n
-0000119147 00000 n
-0000119302 00000 n
-0000119457 00000 n
-0000119612 00000 n
-0000119766 00000 n
-0000119921 00000 n
-0000120076 00000 n
-0000120230 00000 n
-0000120385 00000 n
-0000120540 00000 n
-0000120695 00000 n
-0000120845 00000 n
-0000120999 00000 n
-0000121154 00000 n
-0000121314 00000 n
-0000121474 00000 n
-0000121639 00000 n
-0000121804 00000 n
-0000121959 00000 n
-0000122114 00000 n
-0000122268 00000 n
-0000122428 00000 n
-0000122593 00000 n
-0000122757 00000 n
-0000122911 00000 n
-0000123071 00000 n
-0000123231 00000 n
-0000123385 00000 n
-0000123540 00000 n
-0000123700 00000 n
-0000123865 00000 n
-0000124029 00000 n
-0000124194 00000 n
-0000124359 00000 n
-0000124524 00000 n
-0000124683 00000 n
-0000124838 00000 n
-0000124998 00000 n
-0000125158 00000 n
-0000125312 00000 n
-0000125467 00000 n
-0000125620 00000 n
-0000125773 00000 n
-0000135862 00000 n
-0000128178 00000 n
-0000126090 00000 n
-0000135799 00000 n
-0000128718 00000 n
-0000128873 00000 n
-0000129033 00000 n
-0000129188 00000 n
-0000129348 00000 n
-0000129508 00000 n
-0000129662 00000 n
+0000118882 00000 n
+0000118927 00000 n
+0000118972 00000 n
+0000119017 00000 n
+0000119062 00000 n
+0000119107 00000 n
+0000119152 00000 n
+0000119197 00000 n
+0000119242 00000 n
+0000119287 00000 n
+0000119332 00000 n
+0000119377 00000 n
+0000119422 00000 n
+0000119467 00000 n
+0000119512 00000 n
+0000119557 00000 n
+0000119602 00000 n
+0000119647 00000 n
+0000119692 00000 n
+0000119737 00000 n
+0000119782 00000 n
+0000119827 00000 n
+0000119872 00000 n
+0000119917 00000 n
+0000119962 00000 n
+0000120007 00000 n
+0000120052 00000 n
+0000120097 00000 n
+0000120142 00000 n
+0000120187 00000 n
+0000120232 00000 n
+0000120277 00000 n
+0000120322 00000 n
+0000120367 00000 n
+0000120412 00000 n
+0000120457 00000 n
+0000120502 00000 n
+0000120547 00000 n
+0000120592 00000 n
+0000120637 00000 n
+0000120682 00000 n
+0000120727 00000 n
+0000120772 00000 n
+0000120817 00000 n
+0000120862 00000 n
+0000120907 00000 n
+0000120952 00000 n
+0000120997 00000 n
+0000121042 00000 n
+0000121087 00000 n
+0000121132 00000 n
+0000121177 00000 n
+0000121222 00000 n
+0000121267 00000 n
+0000121312 00000 n
+0000121357 00000 n
+0000121402 00000 n
+0000121447 00000 n
+0000121492 00000 n
+0000121537 00000 n
+0000121582 00000 n
+0000121627 00000 n
+0000121672 00000 n
+0000121717 00000 n
+0000121762 00000 n
+0000121807 00000 n
+0000121852 00000 n
+0000121897 00000 n
+0000121942 00000 n
+0000121987 00000 n
+0000122032 00000 n
+0000122077 00000 n
+0000122122 00000 n
+0000122167 00000 n
+0000122212 00000 n
+0000122257 00000 n
+0000122302 00000 n
+0000122347 00000 n
+0000122392 00000 n
+0000122437 00000 n
+0000122482 00000 n
+0000122527 00000 n
+0000122572 00000 n
+0000122617 00000 n
+0000122662 00000 n
+0000122707 00000 n
+0000122752 00000 n
+0000122797 00000 n
+0000122842 00000 n
+0000122887 00000 n
+0000122932 00000 n
+0000122977 00000 n
+0000123022 00000 n
+0000123067 00000 n
+0000123112 00000 n
+0000123157 00000 n
+0000123202 00000 n
+0000123247 00000 n
+0000123292 00000 n
+0000123337 00000 n
+0000123382 00000 n
+0000123427 00000 n
+0000123472 00000 n
+0000123517 00000 n
+0000123562 00000 n
+0000123607 00000 n
+0000123652 00000 n
+0000123697 00000 n
+0000123742 00000 n
+0000123787 00000 n
+0000123832 00000 n
+0000123877 00000 n
+0000123922 00000 n
+0000123967 00000 n
+0000124012 00000 n
+0000124057 00000 n
+0000124102 00000 n
+0000124147 00000 n
+0000124192 00000 n
+0000124237 00000 n
+0000124282 00000 n
+0000124327 00000 n
+0000124372 00000 n
+0000124417 00000 n
+0000124462 00000 n
+0000124507 00000 n
+0000124552 00000 n
+0000124597 00000 n
+0000124642 00000 n
+0000124687 00000 n
+0000124732 00000 n
+0000124777 00000 n
+0000124822 00000 n
+0000124867 00000 n
+0000124912 00000 n
+0000124957 00000 n
+0000125002 00000 n
+0000125047 00000 n
+0000125092 00000 n
+0000125137 00000 n
+0000125182 00000 n
+0000125227 00000 n
+0000125272 00000 n
+0000125317 00000 n
+0000125362 00000 n
+0000125407 00000 n
+0000125452 00000 n
+0000125497 00000 n
+0000125542 00000 n
+0000125587 00000 n
+0000125632 00000 n
+0000125677 00000 n
+0000125722 00000 n
+0000125767 00000 n
+0000125812 00000 n
+0000125857 00000 n
+0000125902 00000 n
+0000125947 00000 n
+0000125992 00000 n
+0000126037 00000 n
+0000126082 00000 n
+0000126127 00000 n
+0000126172 00000 n
+0000126217 00000 n
+0000126262 00000 n
+0000126307 00000 n
+0000126352 00000 n
+0000126397 00000 n
+0000126442 00000 n
+0000126487 00000 n
+0000126532 00000 n
+0000126577 00000 n
+0000126622 00000 n
+0000126667 00000 n
+0000126712 00000 n
+0000126757 00000 n
+0000126802 00000 n
+0000126847 00000 n
+0000126892 00000 n
+0000126937 00000 n
+0000126982 00000 n
+0000127027 00000 n
+0000127072 00000 n
+0000127117 00000 n
+0000127162 00000 n
+0000127207 00000 n
+0000127252 00000 n
+0000127297 00000 n
+0000127342 00000 n
+0000127387 00000 n
+0000127432 00000 n
+0000127477 00000 n
+0000127522 00000 n
+0000127567 00000 n
+0000127612 00000 n
+0000127657 00000 n
+0000127702 00000 n
+0000127747 00000 n
+0000127792 00000 n
+0000127837 00000 n
+0000127882 00000 n
+0000127927 00000 n
+0000127972 00000 n
+0000128017 00000 n
+0000128062 00000 n
+0000128107 00000 n
+0000128152 00000 n
+0000128197 00000 n
+0000128242 00000 n
+0000128287 00000 n
+0000128332 00000 n
+0000128377 00000 n
+0000128422 00000 n
+0000128467 00000 n
+0000128512 00000 n
+0000128557 00000 n
+0000128602 00000 n
+0000128647 00000 n
+0000128692 00000 n
+0000128737 00000 n
+0000128782 00000 n
+0000128827 00000 n
+0000128872 00000 n
+0000128917 00000 n
+0000128962 00000 n
+0000129007 00000 n
+0000129052 00000 n
+0000129097 00000 n
+0000129142 00000 n
+0000129187 00000 n
+0000129232 00000 n
+0000129277 00000 n
+0000129322 00000 n
+0000129367 00000 n
+0000129412 00000 n
+0000129457 00000 n
+0000129502 00000 n
+0000129547 00000 n
+0000129592 00000 n
+0000129637 00000 n
+0000129682 00000 n
+0000129727 00000 n
+0000129772 00000 n
0000129817 00000 n
-0000129971 00000 n
-0000130131 00000 n
-0000130291 00000 n
-0000130451 00000 n
-0000130611 00000 n
-0000130766 00000 n
-0000130926 00000 n
-0000131086 00000 n
-0000131246 00000 n
-0000131405 00000 n
-0000131565 00000 n
-0000131725 00000 n
-0000131879 00000 n
-0000132038 00000 n
-0000132193 00000 n
-0000132348 00000 n
-0000132502 00000 n
-0000132657 00000 n
-0000132817 00000 n
-0000132977 00000 n
-0000133136 00000 n
-0000133295 00000 n
-0000133455 00000 n
-0000133615 00000 n
-0000133774 00000 n
-0000133934 00000 n
-0000134094 00000 n
-0000134255 00000 n
-0000134409 00000 n
-0000134564 00000 n
-0000134719 00000 n
-0000134874 00000 n
-0000135028 00000 n
-0000135183 00000 n
-0000135338 00000 n
-0000135492 00000 n
-0000135646 00000 n
-0000136517 00000 n
-0000136271 00000 n
-0000135964 00000 n
-0000136394 00000 n
-0001010147 00000 n
-0000140649 00000 n
-0000140030 00000 n
-0000136605 00000 n
-0000140153 00000 n
-0000140216 00000 n
-0000140340 00000 n
-0000924091 00000 n
-0000906588 00000 n
-0000923925 00000 n
-0000140464 00000 n
-0000140587 00000 n
-0000905160 00000 n
-0000903069 00000 n
-0000904994 00000 n
-0000144592 00000 n
-0000144282 00000 n
-0000140765 00000 n
-0000144405 00000 n
-0000144529 00000 n
-0000148987 00000 n
-0000148148 00000 n
-0000144708 00000 n
-0000148677 00000 n
-0000148801 00000 n
-0000148925 00000 n
-0000148301 00000 n
-0000148486 00000 n
-0000154858 00000 n
-0000152423 00000 n
-0000149117 00000 n
-0000154548 00000 n
-0000152648 00000 n
-0000152818 00000 n
-0000153017 00000 n
-0000153212 00000 n
-0000153401 00000 n
-0000153594 00000 n
-0000153789 00000 n
-0000153974 00000 n
-0000154166 00000 n
-0000154672 00000 n
-0000154361 00000 n
-0000154796 00000 n
-0000158774 00000 n
-0000157454 00000 n
-0000154988 00000 n
-0000158093 00000 n
-0000158217 00000 n
-0000158341 00000 n
-0000157616 00000 n
-0000157782 00000 n
-0000158464 00000 n
-0000158588 00000 n
-0000157935 00000 n
-0000158711 00000 n
-0000770401 00000 n
-0000690139 00000 n
-0000163003 00000 n
-0000161866 00000 n
-0000158890 00000 n
-0000162322 00000 n
-0000162446 00000 n
-0000162569 00000 n
-0000162693 00000 n
-0000162817 00000 n
-0000901167 00000 n
-0000899153 00000 n
-0000901002 00000 n
-0000162940 00000 n
-0000162019 00000 n
-0000162171 00000 n
-0001010272 00000 n
-0000725271 00000 n
-0000747347 00000 n
-0000163727 00000 n
-0000163480 00000 n
-0000163161 00000 n
-0000163603 00000 n
-0000167030 00000 n
-0000166410 00000 n
-0000163815 00000 n
-0000166533 00000 n
-0000166596 00000 n
-0000166720 00000 n
-0000166844 00000 n
-0000166968 00000 n
-0000170835 00000 n
-0000170402 00000 n
-0000167160 00000 n
-0000170525 00000 n
-0000170649 00000 n
-0000170773 00000 n
-0000174672 00000 n
-0000173862 00000 n
-0000170951 00000 n
-0000173985 00000 n
-0000174110 00000 n
-0000174235 00000 n
-0000174360 00000 n
-0000174423 00000 n
-0000174486 00000 n
-0000174609 00000 n
-0000178269 00000 n
-0000180112 00000 n
-0000178146 00000 n
-0000174774 00000 n
-0000179799 00000 n
-0000179924 00000 n
-0000898554 00000 n
-0000890154 00000 n
-0000898387 00000 n
-0000888713 00000 n
-0000885289 00000 n
-0000888546 00000 n
-0000884330 00000 n
-0000872635 00000 n
-0000884164 00000 n
-0000180049 00000 n
-0000179628 00000 n
-0000179686 00000 n
-0000179776 00000 n
-0000183718 00000 n
-0000183407 00000 n
-0000180327 00000 n
-0000183530 00000 n
-0000183655 00000 n
-0001010397 00000 n
-0000187660 00000 n
-0000186930 00000 n
-0000183862 00000 n
-0000187224 00000 n
-0000187348 00000 n
-0000187473 00000 n
-0000187074 00000 n
-0000187598 00000 n
-0000495602 00000 n
-0000190294 00000 n
-0000189733 00000 n
-0000187818 00000 n
-0000189856 00000 n
-0000189981 00000 n
-0000190106 00000 n
-0000190231 00000 n
-0000193030 00000 n
-0000192530 00000 n
-0000190467 00000 n
-0000192653 00000 n
-0000192716 00000 n
-0000192779 00000 n
-0000192842 00000 n
-0000192967 00000 n
-0000195507 00000 n
-0000195151 00000 n
-0000193160 00000 n
-0000195444 00000 n
-0000195295 00000 n
-0000310760 00000 n
-0000199343 00000 n
-0000198862 00000 n
-0000195680 00000 n
-0000199155 00000 n
-0000199280 00000 n
-0000199006 00000 n
-0000203431 00000 n
-0000202932 00000 n
-0000199487 00000 n
-0000203243 00000 n
-0000203368 00000 n
-0000203076 00000 n
-0001010522 00000 n
-0000206961 00000 n
-0000208270 00000 n
-0000206817 00000 n
-0000203632 00000 n
-0000207957 00000 n
-0000208082 00000 n
-0000207774 00000 n
-0000208207 00000 n
-0000212502 00000 n
-0000211639 00000 n
-0000208471 00000 n
-0000211940 00000 n
-0000211783 00000 n
-0000212065 00000 n
-0000212190 00000 n
-0000212315 00000 n
-0000212439 00000 n
-0000245941 00000 n
-0000216925 00000 n
-0000216368 00000 n
-0000212674 00000 n
-0000216491 00000 n
-0000216616 00000 n
-0000216739 00000 n
-0000216862 00000 n
-0000220117 00000 n
-0000219366 00000 n
-0000217041 00000 n
-0000219489 00000 n
-0000219552 00000 n
-0000219615 00000 n
-0000219678 00000 n
-0000219741 00000 n
-0000219804 00000 n
-0000219867 00000 n
-0000219930 00000 n
-0000220054 00000 n
-0000222836 00000 n
-0000222650 00000 n
-0000220247 00000 n
-0000222773 00000 n
-0000226445 00000 n
-0000225567 00000 n
-0000222995 00000 n
-0000225885 00000 n
-0000226010 00000 n
-0000226135 00000 n
-0000225711 00000 n
-0000226260 00000 n
-0000226383 00000 n
-0001010647 00000 n
-0000230556 00000 n
-0000229871 00000 n
-0000226547 00000 n
-0000229994 00000 n
-0000230119 00000 n
-0000230244 00000 n
-0000230368 00000 n
-0000230493 00000 n
-0000233669 00000 n
-0000233233 00000 n
-0000230672 00000 n
-0000233356 00000 n
-0000233481 00000 n
-0000233606 00000 n
-0000236054 00000 n
-0000235494 00000 n
-0000233799 00000 n
-0000235617 00000 n
-0000235742 00000 n
-0000235867 00000 n
-0000235992 00000 n
-0000240181 00000 n
-0000238923 00000 n
-0000236227 00000 n
-0000239743 00000 n
-0000239094 00000 n
-0000239254 00000 n
-0000239416 00000 n
-0000239586 00000 n
-0000239868 00000 n
-0000239993 00000 n
-0000240118 00000 n
-0000241907 00000 n
-0000242095 00000 n
-0000241659 00000 n
-0000240354 00000 n
-0000241782 00000 n
-0000242032 00000 n
-0000246128 00000 n
-0000244750 00000 n
-0000242211 00000 n
-0000245816 00000 n
-0000246066 00000 n
-0000244930 00000 n
-0000245108 00000 n
-0000245286 00000 n
-0000245472 00000 n
-0000245654 00000 n
-0001010772 00000 n
-0000250710 00000 n
-0000249608 00000 n
-0000246258 00000 n
-0000250522 00000 n
-0000250647 00000 n
-0000249779 00000 n
-0000249969 00000 n
-0000250135 00000 n
-0000250309 00000 n
-0000251473 00000 n
-0000251226 00000 n
-0000250911 00000 n
-0000251349 00000 n
-0000254350 00000 n
-0000253851 00000 n
-0000251561 00000 n
-0000253974 00000 n
-0000254037 00000 n
-0000254162 00000 n
-0000254287 00000 n
-0000257531 00000 n
-0000257220 00000 n
-0000254509 00000 n
-0000257343 00000 n
-0000257468 00000 n
-0000261892 00000 n
-0000261581 00000 n
-0000257661 00000 n
-0000261704 00000 n
-0000261829 00000 n
-0000265096 00000 n
-0000264785 00000 n
-0000262022 00000 n
-0000264908 00000 n
-0000265033 00000 n
-0001010897 00000 n
-0000268529 00000 n
-0000267738 00000 n
-0000265226 00000 n
-0000268217 00000 n
-0000268341 00000 n
-0000267891 00000 n
-0000268054 00000 n
-0000268466 00000 n
-0000272855 00000 n
-0000272357 00000 n
-0000268673 00000 n
-0000272480 00000 n
-0000272604 00000 n
-0000272667 00000 n
-0000272730 00000 n
-0000272793 00000 n
-0000276556 00000 n
-0000275808 00000 n
-0000272985 00000 n
-0000275931 00000 n
-0000275994 00000 n
-0000276118 00000 n
-0000276243 00000 n
-0000276368 00000 n
-0000276493 00000 n
-0000280418 00000 n
-0000281421 00000 n
-0000280295 00000 n
-0000276686 00000 n
-0000281233 00000 n
-0000281358 00000 n
-0000285520 00000 n
-0000285084 00000 n
-0000281608 00000 n
-0000285207 00000 n
-0000285332 00000 n
-0000871442 00000 n
-0000869441 00000 n
-0000871276 00000 n
-0000285457 00000 n
-0000289511 00000 n
-0000288826 00000 n
-0000285678 00000 n
-0000288949 00000 n
-0000289074 00000 n
-0000289199 00000 n
-0000289323 00000 n
-0000289448 00000 n
-0001011022 00000 n
-0000292553 00000 n
-0000292243 00000 n
-0000289698 00000 n
-0000292366 00000 n
-0000292491 00000 n
-0000296884 00000 n
-0000296448 00000 n
-0000292683 00000 n
-0000296571 00000 n
-0000296696 00000 n
-0000296821 00000 n
-0000300521 00000 n
-0000300085 00000 n
-0000297099 00000 n
-0000300208 00000 n
-0000300333 00000 n
-0000300458 00000 n
-0000303934 00000 n
-0000303748 00000 n
-0000300637 00000 n
-0000303871 00000 n
-0000305975 00000 n
-0000305789 00000 n
-0000304050 00000 n
-0000305912 00000 n
-0000307748 00000 n
-0000307373 00000 n
-0000306077 00000 n
-0000307496 00000 n
-0000307559 00000 n
-0000307622 00000 n
-0000307685 00000 n
-0001011147 00000 n
-0000311073 00000 n
-0000310512 00000 n
-0000307850 00000 n
-0000310635 00000 n
-0000310885 00000 n
-0000311010 00000 n
-0000313480 00000 n
-0000313294 00000 n
-0000311175 00000 n
-0000313417 00000 n
-0000317448 00000 n
-0000316887 00000 n
-0000313653 00000 n
-0000317010 00000 n
-0000317135 00000 n
-0000317260 00000 n
-0000317385 00000 n
-0000322844 00000 n
-0000320888 00000 n
-0000317606 00000 n
-0000322157 00000 n
-0000322282 00000 n
-0000322407 00000 n
-0000322532 00000 n
-0000322657 00000 n
-0000321077 00000 n
-0000321248 00000 n
-0000321433 00000 n
-0000321600 00000 n
-0000321801 00000 n
-0000322781 00000 n
-0000321973 00000 n
-0000327947 00000 n
-0000326411 00000 n
-0000322988 00000 n
-0000327634 00000 n
-0000326600 00000 n
-0000326769 00000 n
-0000327759 00000 n
-0000326938 00000 n
-0000327117 00000 n
-0000327296 00000 n
-0000327884 00000 n
-0000327467 00000 n
-0000330666 00000 n
-0000330232 00000 n
-0000328077 00000 n
-0000330355 00000 n
-0000330478 00000 n
-0000330603 00000 n
-0001011272 00000 n
-0000334665 00000 n
-0000332457 00000 n
-0000330782 00000 n
-0000334477 00000 n
-0000334602 00000 n
-0000332682 00000 n
-0000332865 00000 n
-0000333041 00000 n
-0000333222 00000 n
-0000333402 00000 n
-0000333582 00000 n
-0000333759 00000 n
-0000333945 00000 n
-0000334128 00000 n
-0000334309 00000 n
-0000338167 00000 n
-0000337561 00000 n
-0000334795 00000 n
-0000337854 00000 n
-0000337979 00000 n
-0000338104 00000 n
-0000337705 00000 n
-0000341259 00000 n
-0000340948 00000 n
-0000338325 00000 n
-0000341071 00000 n
-0000341196 00000 n
-0000344660 00000 n
-0000344154 00000 n
-0000341389 00000 n
-0000344472 00000 n
-0000344298 00000 n
-0000868209 00000 n
-0000866336 00000 n
-0000868041 00000 n
-0000344597 00000 n
-0000347439 00000 n
-0000346879 00000 n
-0000344818 00000 n
-0000347002 00000 n
-0000347126 00000 n
-0000347251 00000 n
-0000347376 00000 n
-0000349365 00000 n
-0000349179 00000 n
-0000347583 00000 n
-0000349302 00000 n
-0001011397 00000 n
-0000352039 00000 n
-0000351478 00000 n
-0000349524 00000 n
-0000351601 00000 n
-0000351726 00000 n
-0000351851 00000 n
-0000351976 00000 n
-0000355709 00000 n
-0000355023 00000 n
-0000352169 00000 n
-0000355146 00000 n
-0000355271 00000 n
-0000355396 00000 n
-0000355521 00000 n
-0000355646 00000 n
-0000360449 00000 n
-0000359891 00000 n
-0000355896 00000 n
-0000360014 00000 n
-0000360138 00000 n
-0000360263 00000 n
-0000360387 00000 n
-0000364480 00000 n
-0000364044 00000 n
-0000360607 00000 n
-0000364167 00000 n
-0000364292 00000 n
-0000364417 00000 n
-0000369263 00000 n
-0000368170 00000 n
-0000364610 00000 n
-0000369075 00000 n
-0000368341 00000 n
-0000368523 00000 n
-0000368703 00000 n
-0000368890 00000 n
-0000369200 00000 n
-0000370153 00000 n
-0000369967 00000 n
-0000369407 00000 n
-0000370090 00000 n
-0001011522 00000 n
-0000373674 00000 n
-0000373174 00000 n
-0000370255 00000 n
-0000373297 00000 n
-0000373422 00000 n
-0000373485 00000 n
-0000373548 00000 n
-0000373611 00000 n
-0000374950 00000 n
-0000374764 00000 n
-0000373790 00000 n
-0000374887 00000 n
-0000379074 00000 n
-0000377909 00000 n
-0000375066 00000 n
-0000378636 00000 n
-0000378761 00000 n
-0000378886 00000 n
-0000378071 00000 n
-0000378251 00000 n
-0000378426 00000 n
-0000379011 00000 n
-0000383435 00000 n
-0000382185 00000 n
-0000379275 00000 n
-0000383248 00000 n
-0000383373 00000 n
-0000382365 00000 n
-0000382542 00000 n
-0000382711 00000 n
-0000382888 00000 n
-0000383068 00000 n
-0000387201 00000 n
-0000386687 00000 n
-0000383622 00000 n
-0000387013 00000 n
-0000386831 00000 n
-0000387138 00000 n
-0000390255 00000 n
-0000389753 00000 n
-0000387402 00000 n
-0000390067 00000 n
-0000390192 00000 n
-0000389897 00000 n
-0001011647 00000 n
-0000394049 00000 n
-0000392939 00000 n
-0000390399 00000 n
-0000393861 00000 n
-0000393986 00000 n
-0000393110 00000 n
-0000393298 00000 n
-0000393485 00000 n
-0000393675 00000 n
-0000397540 00000 n
-0000396584 00000 n
-0000394193 00000 n
-0000397102 00000 n
-0000397227 00000 n
-0000396737 00000 n
-0000397352 00000 n
-0000396923 00000 n
-0000397477 00000 n
-0000401252 00000 n
-0000400691 00000 n
-0000397670 00000 n
-0000400814 00000 n
-0000400939 00000 n
-0000401064 00000 n
-0000401189 00000 n
-0000404213 00000 n
-0000403777 00000 n
-0000401410 00000 n
-0000403900 00000 n
-0000404025 00000 n
-0000404150 00000 n
-0000406974 00000 n
-0000406663 00000 n
-0000404329 00000 n
-0000406786 00000 n
-0000406911 00000 n
-0000410374 00000 n
-0000409437 00000 n
-0000407104 00000 n
-0000409560 00000 n
-0000409685 00000 n
-0000409810 00000 n
-0000409873 00000 n
-0000409936 00000 n
-0000409999 00000 n
-0000410062 00000 n
-0000410125 00000 n
-0000410188 00000 n
-0000410250 00000 n
-0000410312 00000 n
-0001011772 00000 n
-0000413658 00000 n
-0000413222 00000 n
-0000410504 00000 n
-0000413345 00000 n
-0000413470 00000 n
-0000413595 00000 n
-0000415918 00000 n
-0000415357 00000 n
-0000413774 00000 n
-0000415480 00000 n
-0000415605 00000 n
-0000415730 00000 n
-0000415855 00000 n
-0000419815 00000 n
-0000419065 00000 n
-0000416034 00000 n
-0000419378 00000 n
-0000419503 00000 n
-0000419628 00000 n
-0000419209 00000 n
-0000419752 00000 n
-0000423257 00000 n
-0000422946 00000 n
-0000419931 00000 n
-0000423069 00000 n
-0000423194 00000 n
-0000426455 00000 n
-0000426269 00000 n
-0000423486 00000 n
-0000426392 00000 n
-0000429412 00000 n
-0000429226 00000 n
-0000426656 00000 n
-0000429349 00000 n
-0001011897 00000 n
-0000433799 00000 n
-0000433488 00000 n
-0000429571 00000 n
-0000433611 00000 n
-0000433736 00000 n
-0000436889 00000 n
-0000436453 00000 n
-0000433957 00000 n
-0000436576 00000 n
-0000436701 00000 n
-0000436826 00000 n
-0000441570 00000 n
-0000440085 00000 n
-0000437033 00000 n
-0000441382 00000 n
-0000441507 00000 n
-0000440274 00000 n
-0000440455 00000 n
-0000440638 00000 n
-0000440812 00000 n
-0000441023 00000 n
-0000441204 00000 n
-0000444699 00000 n
-0000444388 00000 n
-0000441714 00000 n
-0000444511 00000 n
-0000444636 00000 n
-0000446306 00000 n
-0000446120 00000 n
-0000444829 00000 n
-0000446243 00000 n
-0000449069 00000 n
-0000448758 00000 n
-0000446408 00000 n
-0000448881 00000 n
-0000449006 00000 n
-0001012022 00000 n
-0000450303 00000 n
-0000450117 00000 n
-0000449213 00000 n
-0000450240 00000 n
-0000451802 00000 n
-0000451616 00000 n
-0000450405 00000 n
-0000451739 00000 n
-0000452865 00000 n
-0000452679 00000 n
-0000451904 00000 n
-0000452802 00000 n
-0000454108 00000 n
-0000453922 00000 n
-0000452967 00000 n
-0000454045 00000 n
-0000455454 00000 n
-0000455268 00000 n
-0000454210 00000 n
-0000455391 00000 n
-0000456696 00000 n
-0000456510 00000 n
-0000455556 00000 n
-0000456633 00000 n
-0001012147 00000 n
-0000460686 00000 n
-0000459604 00000 n
-0000456798 00000 n
-0000460373 00000 n
-0000460498 00000 n
-0000460623 00000 n
-0000459766 00000 n
-0000459960 00000 n
-0000460167 00000 n
-0000465180 00000 n
-0000463846 00000 n
-0000460830 00000 n
-0000465117 00000 n
-0000464026 00000 n
-0000464214 00000 n
-0000464463 00000 n
-0000464712 00000 n
-0000464903 00000 n
-0000469180 00000 n
-0000468476 00000 n
-0000465339 00000 n
-0000468993 00000 n
-0000468629 00000 n
-0000468811 00000 n
-0000469118 00000 n
-0000472406 00000 n
-0000472220 00000 n
-0000469367 00000 n
-0000472343 00000 n
-0000475763 00000 n
-0000475374 00000 n
-0000472508 00000 n
-0000475700 00000 n
-0000475518 00000 n
-0000478643 00000 n
-0000479519 00000 n
-0000478520 00000 n
-0000475865 00000 n
-0000479456 00000 n
-0001012272 00000 n
-0000482824 00000 n
-0000482638 00000 n
-0000479692 00000 n
-0000482761 00000 n
-0000486541 00000 n
-0000486230 00000 n
-0000482983 00000 n
-0000486353 00000 n
-0000486478 00000 n
-0000490228 00000 n
-0000489917 00000 n
-0000486643 00000 n
-0000490040 00000 n
-0000490165 00000 n
-0000492561 00000 n
-0000492375 00000 n
-0000490415 00000 n
-0000492498 00000 n
-0000496040 00000 n
-0000495354 00000 n
-0000492734 00000 n
-0000495477 00000 n
-0000495727 00000 n
-0000495852 00000 n
-0000495977 00000 n
-0000500342 00000 n
-0000499781 00000 n
-0000496156 00000 n
-0000499904 00000 n
-0000500029 00000 n
-0000500154 00000 n
-0000500279 00000 n
-0001012397 00000 n
-0000504778 00000 n
-0000504218 00000 n
-0000500472 00000 n
-0000504341 00000 n
-0000504466 00000 n
-0000504591 00000 n
-0000504715 00000 n
-0000509387 00000 n
-0000508502 00000 n
-0000504908 00000 n
-0000508825 00000 n
-0000508950 00000 n
-0000509075 00000 n
-0000509200 00000 n
-0000508646 00000 n
-0000509325 00000 n
-0000513866 00000 n
-0000513244 00000 n
-0000509503 00000 n
-0000513553 00000 n
-0000513678 00000 n
-0000864265 00000 n
-0000861109 00000 n
-0000864098 00000 n
-0000513388 00000 n
-0000513803 00000 n
-0000517287 00000 n
-0000516726 00000 n
-0000514038 00000 n
-0000516849 00000 n
-0000516974 00000 n
-0000517099 00000 n
-0000517224 00000 n
-0000520500 00000 n
-0000519940 00000 n
-0000517417 00000 n
-0000520063 00000 n
-0000520188 00000 n
-0000520313 00000 n
-0000520438 00000 n
-0000522941 00000 n
-0000522755 00000 n
-0000520630 00000 n
-0000522878 00000 n
-0001012522 00000 n
-0000525136 00000 n
-0000524699 00000 n
-0000523057 00000 n
-0000524822 00000 n
-0000524947 00000 n
-0000525010 00000 n
-0000525073 00000 n
-0000527209 00000 n
-0000526716 00000 n
-0000525266 00000 n
-0000527020 00000 n
-0000527083 00000 n
-0000527146 00000 n
-0000526860 00000 n
-0000814771 00000 n
-0000530155 00000 n
-0000529594 00000 n
-0000527325 00000 n
-0000529717 00000 n
-0000529780 00000 n
-0000529843 00000 n
-0000529968 00000 n
-0000530031 00000 n
-0000530093 00000 n
-0000532352 00000 n
-0000532166 00000 n
-0000530285 00000 n
-0000532289 00000 n
-0000534537 00000 n
-0000534225 00000 n
-0000532468 00000 n
-0000534348 00000 n
-0000534411 00000 n
-0000534474 00000 n
-0000537574 00000 n
-0000537138 00000 n
-0000534667 00000 n
-0000537261 00000 n
-0000537386 00000 n
-0000537511 00000 n
-0001012647 00000 n
-0000541670 00000 n
-0000540737 00000 n
-0000537704 00000 n
-0000540860 00000 n
-0000540985 00000 n
-0000541110 00000 n
-0000541234 00000 n
-0000541359 00000 n
-0000541422 00000 n
-0000541485 00000 n
-0000541608 00000 n
-0000546276 00000 n
-0000544932 00000 n
-0000541800 00000 n
-0000545899 00000 n
-0000545962 00000 n
-0000546025 00000 n
-0000546088 00000 n
-0000546213 00000 n
-0000545103 00000 n
-0000545302 00000 n
-0000545500 00000 n
-0000545700 00000 n
-0000549004 00000 n
-0000548503 00000 n
-0000546491 00000 n
-0000548816 00000 n
-0000548941 00000 n
-0000548647 00000 n
-0000550901 00000 n
-0000550592 00000 n
-0000549120 00000 n
-0000550715 00000 n
-0000550839 00000 n
-0000551724 00000 n
-0000551538 00000 n
-0000551017 00000 n
-0000551661 00000 n
-0000556332 00000 n
-0000555518 00000 n
-0000551826 00000 n
-0000555894 00000 n
-0000556019 00000 n
-0000556144 00000 n
-0000555662 00000 n
-0000556269 00000 n
-0001012772 00000 n
-0000561157 00000 n
-0000560596 00000 n
-0000556462 00000 n
-0000560719 00000 n
-0000560844 00000 n
-0000560969 00000 n
-0000561094 00000 n
-0000565302 00000 n
-0000564740 00000 n
-0000561315 00000 n
-0000564863 00000 n
-0000564988 00000 n
-0000565051 00000 n
-0000565114 00000 n
-0000565177 00000 n
-0000565239 00000 n
-0000569110 00000 n
-0000568675 00000 n
-0000565432 00000 n
-0000568798 00000 n
-0000568923 00000 n
-0000569048 00000 n
-0000573080 00000 n
-0000572077 00000 n
-0000569283 00000 n
-0000572200 00000 n
-0000572325 00000 n
-0000572450 00000 n
-0000572513 00000 n
-0000572576 00000 n
-0000572639 00000 n
-0000572702 00000 n
-0000572765 00000 n
-0000572828 00000 n
-0000572891 00000 n
-0000572954 00000 n
-0000573017 00000 n
-0000576144 00000 n
-0000575458 00000 n
-0000573196 00000 n
-0000575581 00000 n
-0000575706 00000 n
-0000575831 00000 n
-0000575956 00000 n
-0000576081 00000 n
-0000579308 00000 n
-0000578747 00000 n
-0000576317 00000 n
-0000578870 00000 n
-0000578995 00000 n
-0000579120 00000 n
-0000579245 00000 n
-0001012897 00000 n
-0000583213 00000 n
-0000582652 00000 n
-0000579509 00000 n
-0000582775 00000 n
-0000582900 00000 n
-0000583025 00000 n
-0000583088 00000 n
-0000583151 00000 n
-0000587682 00000 n
-0000587246 00000 n
-0000583442 00000 n
-0000587369 00000 n
-0000587432 00000 n
-0000587494 00000 n
-0000587557 00000 n
-0000587620 00000 n
-0000591601 00000 n
-0000591039 00000 n
-0000587812 00000 n
-0000591162 00000 n
-0000591225 00000 n
-0000591288 00000 n
-0000591413 00000 n
-0000591538 00000 n
-0000593137 00000 n
-0000592951 00000 n
-0000591731 00000 n
-0000593074 00000 n
-0000595507 00000 n
-0000595321 00000 n
-0000593310 00000 n
-0000595444 00000 n
-0000599210 00000 n
-0000598649 00000 n
-0000595666 00000 n
-0000598772 00000 n
-0000598897 00000 n
-0000599022 00000 n
-0000599147 00000 n
-0001013022 00000 n
-0000603300 00000 n
-0000602490 00000 n
-0000599411 00000 n
-0000602613 00000 n
-0000602738 00000 n
-0000602863 00000 n
-0000602988 00000 n
-0000603113 00000 n
-0000603238 00000 n
-0000607546 00000 n
-0000606985 00000 n
-0000603473 00000 n
-0000607108 00000 n
-0000607233 00000 n
-0000607358 00000 n
-0000607483 00000 n
-0000611571 00000 n
-0000611008 00000 n
-0000607747 00000 n
-0000611131 00000 n
-0000611256 00000 n
-0000611319 00000 n
-0000611382 00000 n
-0000611445 00000 n
-0000611508 00000 n
-0000613695 00000 n
-0000613509 00000 n
-0000611715 00000 n
-0000613632 00000 n
-0000617103 00000 n
-0000616792 00000 n
-0000613811 00000 n
-0000616915 00000 n
-0000617040 00000 n
-0000619408 00000 n
-0000619222 00000 n
-0000617290 00000 n
-0000619345 00000 n
-0001013147 00000 n
-0000621045 00000 n
-0000620859 00000 n
-0000619524 00000 n
-0000620982 00000 n
-0000624784 00000 n
-0000624348 00000 n
-0000621161 00000 n
-0000624471 00000 n
-0000624596 00000 n
-0000624721 00000 n
-0000628803 00000 n
-0000627994 00000 n
-0000624886 00000 n
-0000628117 00000 n
-0000628242 00000 n
-0000628367 00000 n
-0000628490 00000 n
-0000628615 00000 n
-0000628740 00000 n
-0000632487 00000 n
-0000632177 00000 n
-0000628919 00000 n
-0000632300 00000 n
-0000632424 00000 n
-0000635510 00000 n
-0000635072 00000 n
-0000632660 00000 n
-0000635195 00000 n
-0000635321 00000 n
-0000635447 00000 n
-0000638093 00000 n
-0000637907 00000 n
-0000635683 00000 n
-0000638030 00000 n
-0001013272 00000 n
-0000641664 00000 n
-0000640948 00000 n
-0000638209 00000 n
-0000641475 00000 n
-0000641601 00000 n
-0000641101 00000 n
-0000641289 00000 n
-0000644464 00000 n
-0000644152 00000 n
-0000641851 00000 n
-0000644275 00000 n
-0000644401 00000 n
-0000646818 00000 n
-0000646380 00000 n
-0000644580 00000 n
-0000646503 00000 n
-0000646629 00000 n
-0000646755 00000 n
-0000649396 00000 n
-0000648836 00000 n
-0000646934 00000 n
-0000648959 00000 n
-0000649085 00000 n
-0000649207 00000 n
-0000649333 00000 n
-0000652517 00000 n
-0000651701 00000 n
-0000649526 00000 n
-0000651824 00000 n
-0000651950 00000 n
-0000652076 00000 n
-0000652202 00000 n
-0000652328 00000 n
-0000652454 00000 n
-0000655439 00000 n
-0000654749 00000 n
-0000652647 00000 n
-0000654872 00000 n
-0000654935 00000 n
-0000654998 00000 n
-0000655125 00000 n
-0000655251 00000 n
-0000655376 00000 n
-0001013397 00000 n
-0000658283 00000 n
-0000657244 00000 n
-0000655555 00000 n
-0000657969 00000 n
-0000658095 00000 n
-0000657406 00000 n
-0000657612 00000 n
-0000658221 00000 n
-0000657792 00000 n
-0000662346 00000 n
-0000661032 00000 n
-0000658399 00000 n
-0000662031 00000 n
-0000662157 00000 n
-0000662283 00000 n
-0000661203 00000 n
-0000661439 00000 n
-0000661675 00000 n
-0000661853 00000 n
-0000664068 00000 n
-0000663756 00000 n
-0000662476 00000 n
-0000663879 00000 n
-0000664005 00000 n
-0000667065 00000 n
-0000666628 00000 n
-0000664184 00000 n
-0000666751 00000 n
-0000666877 00000 n
-0000667003 00000 n
-0000670863 00000 n
-0000670427 00000 n
-0000667238 00000 n
-0000670550 00000 n
-0000670676 00000 n
-0000670801 00000 n
-0000673309 00000 n
-0000672871 00000 n
-0000670993 00000 n
-0000672994 00000 n
-0000673120 00000 n
-0000673246 00000 n
-0001013522 00000 n
-0000677139 00000 n
-0000676827 00000 n
-0000673439 00000 n
-0000676950 00000 n
-0000677076 00000 n
-0000681206 00000 n
-0000680768 00000 n
-0000677283 00000 n
-0000680891 00000 n
-0000681017 00000 n
-0000681143 00000 n
-0000683309 00000 n
-0000683123 00000 n
-0000681336 00000 n
-0000683246 00000 n
-0000686546 00000 n
-0000685982 00000 n
-0000683411 00000 n
-0000686105 00000 n
-0000686231 00000 n
-0000686357 00000 n
-0000686483 00000 n
-0000687333 00000 n
-0000687147 00000 n
-0000686676 00000 n
-0000687270 00000 n
-0000690580 00000 n
-0000689890 00000 n
-0000687435 00000 n
-0000690013 00000 n
-0000690265 00000 n
-0000690391 00000 n
-0000690517 00000 n
-0001013647 00000 n
-0000693657 00000 n
-0000693096 00000 n
-0000690696 00000 n
-0000693219 00000 n
-0000693345 00000 n
-0000693469 00000 n
-0000693594 00000 n
-0000695296 00000 n
-0000694795 00000 n
-0000693773 00000 n
-0000695107 00000 n
-0000695233 00000 n
-0000694939 00000 n
-0000699280 00000 n
-0000698397 00000 n
-0000695412 00000 n
-0000698713 00000 n
-0000698839 00000 n
-0000698965 00000 n
-0000698541 00000 n
-0000699091 00000 n
-0000699217 00000 n
-0000701871 00000 n
-0000701112 00000 n
-0000699410 00000 n
-0000701683 00000 n
-0000701809 00000 n
-0000701265 00000 n
-0000701474 00000 n
-0000706036 00000 n
-0000705472 00000 n
-0000702015 00000 n
-0000705595 00000 n
-0000705721 00000 n
-0000705847 00000 n
-0000705973 00000 n
-0000709812 00000 n
-0000709501 00000 n
-0000706138 00000 n
-0000709624 00000 n
-0000709750 00000 n
-0001013772 00000 n
-0000712542 00000 n
-0000712356 00000 n
-0000709942 00000 n
-0000712479 00000 n
-0000715273 00000 n
-0000714961 00000 n
-0000712701 00000 n
-0000715084 00000 n
-0000715210 00000 n
-0000718089 00000 n
-0000717652 00000 n
-0000715460 00000 n
-0000717775 00000 n
-0000717901 00000 n
-0000718027 00000 n
-0000721760 00000 n
-0000719888 00000 n
-0000718205 00000 n
-0000721571 00000 n
-0000721697 00000 n
-0000720086 00000 n
-0000720297 00000 n
-0000720510 00000 n
-0000720723 00000 n
-0000720935 00000 n
-0000721147 00000 n
-0000721359 00000 n
-0000722439 00000 n
-0000722191 00000 n
-0000721890 00000 n
-0000722314 00000 n
-0000725585 00000 n
-0000724959 00000 n
-0000722527 00000 n
-0000725082 00000 n
-0000725145 00000 n
-0000725397 00000 n
-0000725522 00000 n
-0001013897 00000 n
-0000729607 00000 n
-0000729106 00000 n
-0000725758 00000 n
-0000729229 00000 n
-0000729355 00000 n
-0000729418 00000 n
-0000729481 00000 n
-0000729544 00000 n
-0000733268 00000 n
-0000733019 00000 n
-0000729794 00000 n
-0000733142 00000 n
-0000733205 00000 n
-0000737822 00000 n
-0000737075 00000 n
-0000733455 00000 n
-0000737198 00000 n
-0000737261 00000 n
-0000737324 00000 n
-0000737387 00000 n
-0000737449 00000 n
-0000737512 00000 n
-0000737573 00000 n
-0000737635 00000 n
-0000737698 00000 n
-0000737761 00000 n
-0000742526 00000 n
-0000741900 00000 n
-0000738023 00000 n
-0000742023 00000 n
-0000742086 00000 n
-0000742149 00000 n
-0000742211 00000 n
-0000742274 00000 n
-0000742337 00000 n
-0000742400 00000 n
-0000742463 00000 n
-0000743646 00000 n
-0000743161 00000 n
-0000742670 00000 n
-0000743457 00000 n
-0000743583 00000 n
-0000743305 00000 n
-0000747660 00000 n
-0000746723 00000 n
-0000743748 00000 n
-0000747221 00000 n
-0000747473 00000 n
-0000746876 00000 n
-0000747048 00000 n
-0000747599 00000 n
-0001014022 00000 n
-0000752341 00000 n
-0000750683 00000 n
-0000747776 00000 n
-0000752153 00000 n
-0000752279 00000 n
-0000750881 00000 n
-0000751045 00000 n
-0000751236 00000 n
-0000751427 00000 n
-0000751612 00000 n
-0000751781 00000 n
-0000751965 00000 n
-0000757121 00000 n
-0000755930 00000 n
-0000752485 00000 n
-0000756806 00000 n
-0000756932 00000 n
-0000756101 00000 n
-0000756266 00000 n
-0000757058 00000 n
-0000756439 00000 n
-0000756610 00000 n
-0000761260 00000 n
-0000760031 00000 n
-0000757279 00000 n
-0000760693 00000 n
-0000760819 00000 n
-0000760945 00000 n
-0000760193 00000 n
-0000760369 00000 n
-0000761071 00000 n
-0000760540 00000 n
-0000761197 00000 n
-0000765471 00000 n
-0000764907 00000 n
-0000761376 00000 n
-0000765030 00000 n
-0000765156 00000 n
-0000765282 00000 n
-0000765408 00000 n
-0000766141 00000 n
-0000765893 00000 n
-0000765601 00000 n
-0000766016 00000 n
-0000771157 00000 n
-0000768978 00000 n
-0000766229 00000 n
-0000770212 00000 n
-0000770275 00000 n
-0000769167 00000 n
-0000770527 00000 n
-0000770653 00000 n
-0000769333 00000 n
-0000769512 00000 n
-0000770779 00000 n
-0000770905 00000 n
-0000769692 00000 n
-0000771031 00000 n
-0000769870 00000 n
-0000770041 00000 n
-0000771094 00000 n
-0001014147 00000 n
-0000775076 00000 n
-0000773871 00000 n
-0000771259 00000 n
-0000774573 00000 n
-0000774636 00000 n
-0000774699 00000 n
-0000774762 00000 n
-0000774887 00000 n
-0000774033 00000 n
-0000774218 00000 n
-0000774403 00000 n
-0000775013 00000 n
-0000777908 00000 n
-0000777470 00000 n
-0000775192 00000 n
-0000777593 00000 n
-0000777719 00000 n
-0000777845 00000 n
-0000781057 00000 n
-0000780367 00000 n
-0000778038 00000 n
-0000780490 00000 n
-0000780616 00000 n
-0000780742 00000 n
-0000780868 00000 n
-0000780994 00000 n
-0000783774 00000 n
-0000783462 00000 n
-0000781187 00000 n
-0000783585 00000 n
-0000783711 00000 n
-0000784805 00000 n
-0000784619 00000 n
-0000783975 00000 n
-0000784742 00000 n
-0000788059 00000 n
-0000787495 00000 n
-0000784964 00000 n
-0000787618 00000 n
-0000787744 00000 n
-0000787870 00000 n
-0000787996 00000 n
-0001014272 00000 n
-0000791230 00000 n
-0000790918 00000 n
-0000788175 00000 n
-0000791041 00000 n
-0000791167 00000 n
-0000795686 00000 n
-0000795249 00000 n
-0000791346 00000 n
-0000795372 00000 n
-0000795498 00000 n
-0000795624 00000 n
-0000799718 00000 n
-0000798085 00000 n
-0000795802 00000 n
-0000798208 00000 n
-0000798334 00000 n
-0000798460 00000 n
-0000798586 00000 n
-0000798649 00000 n
-0000798712 00000 n
-0000798775 00000 n
-0000798838 00000 n
-0000798901 00000 n
-0000798964 00000 n
-0000799027 00000 n
-0000799090 00000 n
-0000799153 00000 n
-0000799216 00000 n
-0000799279 00000 n
-0000799342 00000 n
-0000799405 00000 n
-0000799468 00000 n
-0000799531 00000 n
-0000799594 00000 n
-0000799656 00000 n
-0000802966 00000 n
-0000802150 00000 n
-0000799876 00000 n
-0000802273 00000 n
-0000802336 00000 n
-0000802399 00000 n
-0000802525 00000 n
-0000802588 00000 n
-0000802651 00000 n
-0000802778 00000 n
-0000802904 00000 n
-0000805609 00000 n
-0000805296 00000 n
-0000803124 00000 n
-0000805419 00000 n
-0000805482 00000 n
-0000805545 00000 n
-0000806690 00000 n
-0000806504 00000 n
-0000805725 00000 n
-0000806627 00000 n
-0001014397 00000 n
-0000810176 00000 n
-0000809487 00000 n
-0000806792 00000 n
-0000809610 00000 n
-0000809736 00000 n
-0000809862 00000 n
-0000809988 00000 n
-0000810113 00000 n
-0000811805 00000 n
-0000811493 00000 n
-0000810278 00000 n
-0000811616 00000 n
-0000811742 00000 n
-0000814834 00000 n
-0000814019 00000 n
-0000811935 00000 n
-0000814142 00000 n
-0000814268 00000 n
-0000814394 00000 n
-0000814519 00000 n
-0000814645 00000 n
-0000819904 00000 n
-0000818027 00000 n
-0000814936 00000 n
-0000819337 00000 n
-0000819463 00000 n
-0000819589 00000 n
-0000818216 00000 n
-0000818388 00000 n
-0000818578 00000 n
-0000818763 00000 n
-0000818955 00000 n
-0000819715 00000 n
-0000819841 00000 n
-0000819142 00000 n
-0000825020 00000 n
-0000823381 00000 n
-0000820020 00000 n
-0000824327 00000 n
-0000824453 00000 n
-0000823552 00000 n
-0000823750 00000 n
-0000823942 00000 n
-0000824579 00000 n
-0000824132 00000 n
-0000824705 00000 n
-0000824831 00000 n
-0000824957 00000 n
-0000829573 00000 n
-0000828443 00000 n
-0000825164 00000 n
-0000828755 00000 n
-0000828881 00000 n
-0000829006 00000 n
-0000829132 00000 n
-0000828587 00000 n
-0000829258 00000 n
-0000829384 00000 n
-0000829510 00000 n
-0001014522 00000 n
-0000833600 00000 n
-0000832659 00000 n
-0000829703 00000 n
-0000832972 00000 n
-0000833035 00000 n
-0000833098 00000 n
-0000833159 00000 n
-0000833222 00000 n
-0000833285 00000 n
-0000833411 00000 n
-0000833537 00000 n
-0000832803 00000 n
-0000835145 00000 n
-0000834601 00000 n
-0000833758 00000 n
-0000834956 00000 n
-0000835082 00000 n
-0000834745 00000 n
-0000838462 00000 n
-0000837900 00000 n
-0000835304 00000 n
-0000838023 00000 n
-0000838149 00000 n
-0000838274 00000 n
-0000838399 00000 n
-0000841416 00000 n
-0000841104 00000 n
-0000838621 00000 n
-0000841227 00000 n
-0000841353 00000 n
-0000845175 00000 n
-0000844545 00000 n
-0000841574 00000 n
-0000844861 00000 n
-0000844987 00000 n
-0000844689 00000 n
-0000845112 00000 n
-0000849454 00000 n
-0000848639 00000 n
-0000845404 00000 n
-0000848762 00000 n
-0000848888 00000 n
-0000849014 00000 n
-0000849140 00000 n
-0000849265 00000 n
-0000849391 00000 n
-0001014647 00000 n
-0000850934 00000 n
-0000850622 00000 n
-0000849584 00000 n
-0000850745 00000 n
-0000850871 00000 n
-0000854679 00000 n
-0000853991 00000 n
-0000851050 00000 n
-0000854114 00000 n
-0000854240 00000 n
-0000854366 00000 n
-0000854492 00000 n
-0000854618 00000 n
-0000858670 00000 n
-0000857855 00000 n
-0000854795 00000 n
-0000857978 00000 n
-0000858104 00000 n
-0000858229 00000 n
-0000858355 00000 n
-0000858481 00000 n
-0000858607 00000 n
-0000859986 00000 n
-0000859496 00000 n
-0000858800 00000 n
-0000859797 00000 n
-0000859923 00000 n
-0000859640 00000 n
-0000860088 00000 n
-0000864491 00000 n
-0000864672 00000 n
-0000868420 00000 n
-0000868445 00000 n
-0000871657 00000 n
-0000871688 00000 n
-0000884872 00000 n
-0000888947 00000 n
-0000889144 00000 n
-0000898871 00000 n
-0000901380 00000 n
-0000901411 00000 n
-0000905411 00000 n
-0000905639 00000 n
-0000924554 00000 n
-0000934967 00000 n
-0000951442 00000 n
-0000951852 00000 n
-0000970160 00000 n
-0000989856 00000 n
-0000995250 00000 n
-0001009493 00000 n
-0001014763 00000 n
-0001014889 00000 n
-0001015015 00000 n
-0001015141 00000 n
-0001015267 00000 n
-0001015393 00000 n
-0001015519 00000 n
-0001015618 00000 n
-0001015745 00000 n
-0001015826 00000 n
-0001015900 00000 n
-0001055177 00000 n
-0001081128 00000 n
-0001081169 00000 n
-0001081209 00000 n
-0001081441 00000 n
+0000129862 00000 n
+0000129907 00000 n
+0000129952 00000 n
+0000129997 00000 n
+0000130042 00000 n
+0000130087 00000 n
+0000130132 00000 n
+0000130177 00000 n
+0000130222 00000 n
+0000130267 00000 n
+0000130312 00000 n
+0000130357 00000 n
+0000130402 00000 n
+0000130447 00000 n
+0000130492 00000 n
+0000130537 00000 n
+0000130582 00000 n
+0000130627 00000 n
+0000130672 00000 n
+0000130717 00000 n
+0000130762 00000 n
+0000130807 00000 n
+0000130852 00000 n
+0000130897 00000 n
+0000130942 00000 n
+0000130987 00000 n
+0000131032 00000 n
+0000131077 00000 n
+0000131122 00000 n
+0000131167 00000 n
+0000131212 00000 n
+0000131257 00000 n
+0000131302 00000 n
+0000131347 00000 n
+0000131392 00000 n
+0000131437 00000 n
+0000131482 00000 n
+0000131527 00000 n
+0000131572 00000 n
+0000131617 00000 n
+0000131662 00000 n
+0000131707 00000 n
+0000131752 00000 n
+0000131797 00000 n
+0000131842 00000 n
+0000131887 00000 n
+0000131932 00000 n
+0000131977 00000 n
+0000132022 00000 n
+0000132067 00000 n
+0000132112 00000 n
+0000132157 00000 n
+0000132202 00000 n
+0000132247 00000 n
+0000132292 00000 n
+0000132337 00000 n
+0000132382 00000 n
+0000132427 00000 n
+0000132472 00000 n
+0000132517 00000 n
+0000132562 00000 n
+0000132607 00000 n
+0000132652 00000 n
+0000132697 00000 n
+0000132742 00000 n
+0000132787 00000 n
+0000132832 00000 n
+0000132877 00000 n
+0000132922 00000 n
+0000132967 00000 n
+0000134609 00000 n
+0000134770 00000 n
+0000134939 00000 n
+0000135132 00000 n
+0000139029 00000 n
+0000139223 00000 n
+0000143650 00000 n
+0000143844 00000 n
+0000148198 00000 n
+0000148392 00000 n
+0000152436 00000 n
+0000152630 00000 n
+0000156208 00000 n
+0000156402 00000 n
+0000159997 00000 n
+0000160191 00000 n
+0000163343 00000 n
+0000163504 00000 n
+0000163738 00000 n
+0000163941 00000 n
+0000166521 00000 n
+0000166696 00000 n
+0000170340 00000 n
+0000170515 00000 n
+0000173018 00000 n
+0000173193 00000 n
+0000174969 00000 n
+0000175130 00000 n
+0000175318 00000 n
+0000175521 00000 n
+0000178152 00000 n
+0000178327 00000 n
+0000178592 00000 n
+0000178795 00000 n
+0000180229 00000 n
+0000180446 00000 n
+0000181900 00000 n
+0000182097 00000 n
+0000183949 00000 n
+0000184109 00000 n
+0000184604 00000 n
+0000184774 00000 n
+0000186514 00000 n
+0000186702 00000 n
+0000188191 00000 n
+0000188370 00000 n
+0000190346 00000 n
+0000190525 00000 n
+0000191467 00000 n
+0000191696 00000 n
+0000193565 00000 n
+0000193762 00000 n
+0000195301 00000 n
+0000195498 00000 n
+0000196994 00000 n
+0000197217 00000 n
+0000199386 00000 n
+0000199589 00000 n
+0000201482 00000 n
+0000201696 00000 n
+0000202997 00000 n
+0000203229 00000 n
+0000204902 00000 n
+0000205115 00000 n
+0000207019 00000 n
+0000207227 00000 n
+0000208505 00000 n
+0000208744 00000 n
+0000210263 00000 n
+0000210451 00000 n
+0000211763 00000 n
+0000211951 00000 n
+0000212498 00000 n
+0000212659 00000 n
+0000212849 00000 n
+0000213052 00000 n
+0000216173 00000 n
+0000216348 00000 n
+0000216696 00000 n
+0000216885 00000 n
+0000218508 00000 n
+0000218696 00000 n
+0000220068 00000 n
+0000220238 00000 n
+0000222193 00000 n
+0000222353 00000 n
+0000223034 00000 n
+0000223247 00000 n
+0000224669 00000 n
+0000224883 00000 n
+0000226452 00000 n
+0000226650 00000 n
+0000228572 00000 n
+0000228837 00000 n
+0000230548 00000 n
+0000230761 00000 n
+0000232329 00000 n
+0000232536 00000 n
+0000234565 00000 n
+0000234797 00000 n
+0000236825 00000 n
+0000237038 00000 n
+0000239006 00000 n
+0000239218 00000 n
+0000241199 00000 n
+0000241453 00000 n
+0000243716 00000 n
+0000243946 00000 n
+0000245991 00000 n
+0000246222 00000 n
+0000248131 00000 n
+0000248342 00000 n
+0000250218 00000 n
+0000250387 00000 n
+0000252226 00000 n
+0000252448 00000 n
+0000254446 00000 n
+0000254697 00000 n
+0000256661 00000 n
+0000256830 00000 n
+0000258360 00000 n
+0000258554 00000 n
+0000260133 00000 n
+0000260313 00000 n
+0000262054 00000 n
+0000262243 00000 n
+0000263444 00000 n
+0000263623 00000 n
+0000264712 00000 n
+0000264909 00000 n
+0000266280 00000 n
+0000266459 00000 n
+0000267185 00000 n
+0000267417 00000 n
+0000268891 00000 n
+0000269094 00000 n
+0000270903 00000 n
+0000271087 00000 n
+0000271622 00000 n
+0000271783 00000 n
+0000271974 00000 n
+0000272186 00000 n
+0000275133 00000 n
+0000275308 00000 n
+0000277928 00000 n
+0000278103 00000 n
+0000279934 00000 n
+0000280132 00000 n
+0000281493 00000 n
+0000281691 00000 n
+0000283380 00000 n
+0000283568 00000 n
+0000285250 00000 n
+0000285429 00000 n
+0000287531 00000 n
+0000287710 00000 n
+0000289483 00000 n
+0000289662 00000 n
+0000291343 00000 n
+0000291532 00000 n
+0000293380 00000 n
+0000293593 00000 n
+0000295624 00000 n
+0000295837 00000 n
+0000297389 00000 n
+0000297578 00000 n
+0000298852 00000 n
+0000299059 00000 n
+0000300832 00000 n
+0000301030 00000 n
+0000302793 00000 n
+0000303006 00000 n
+0000304714 00000 n
+0000304917 00000 n
+0000306297 00000 n
+0000306486 00000 n
+0000307375 00000 n
+0000307563 00000 n
+0000309089 00000 n
+0000309292 00000 n
+0000311000 00000 n
+0000311203 00000 n
+0000312020 00000 n
+0000312233 00000 n
+0000313719 00000 n
+0000313899 00000 n
+0000314663 00000 n
+0000314927 00000 n
+0000316651 00000 n
+0000316897 00000 n
+0000318788 00000 n
+0000319011 00000 n
+0000320801 00000 n
+0000321024 00000 n
+0000322899 00000 n
+0000323078 00000 n
+0000324302 00000 n
+0000324534 00000 n
+0000326203 00000 n
+0000326382 00000 n
+0000327962 00000 n
+0000328141 00000 n
+0000329688 00000 n
+0000329867 00000 n
+0000331371 00000 n
+0000331550 00000 n
+0000333215 00000 n
+0000333385 00000 n
+0000334131 00000 n
+0000334329 00000 n
+0000336147 00000 n
+0000336380 00000 n
+0000338436 00000 n
+0000338625 00000 n
+0000340281 00000 n
+0000340451 00000 n
+0000341213 00000 n
+0000341383 00000 n
+0000342488 00000 n
+0000342658 00000 n
+0000343478 00000 n
+0000343648 00000 n
+0000344465 00000 n
+0000344635 00000 n
+0000345797 00000 n
+0000346020 00000 n
+0000347673 00000 n
+0000347899 00000 n
+0000349582 00000 n
+0000349827 00000 n
+0000351718 00000 n
+0000351887 00000 n
+0000353633 00000 n
+0000353818 00000 n
+0000355568 00000 n
+0000355824 00000 n
+0000357801 00000 n
+0000358000 00000 n
+0000360224 00000 n
+0000360435 00000 n
+0000362202 00000 n
+0000362403 00000 n
+0000363421 00000 n
+0000363610 00000 n
+0000365304 00000 n
+0000365483 00000 n
+0000367228 00000 n
+0000367416 00000 n
+0000369252 00000 n
+0000369447 00000 n
+0000371359 00000 n
+0000371591 00000 n
+0000373693 00000 n
+0000373906 00000 n
+0000375343 00000 n
+0000375557 00000 n
+0000377006 00000 n
+0000377213 00000 n
+0000378450 00000 n
+0000378629 00000 n
+0000379616 00000 n
+0000379804 00000 n
+0000380936 00000 n
+0000381124 00000 n
+0000382625 00000 n
+0000382813 00000 n
+0000383895 00000 n
+0000384084 00000 n
+0000385416 00000 n
+0000385586 00000 n
+0000387260 00000 n
+0000387439 00000 n
+0000389223 00000 n
+0000389402 00000 n
+0000391047 00000 n
+0000391216 00000 n
+0000392530 00000 n
+0000392718 00000 n
+0000394284 00000 n
+0000394472 00000 n
+0000396091 00000 n
+0000396279 00000 n
+0000397679 00000 n
+0000397849 00000 n
+0000399482 00000 n
+0000399652 00000 n
+0000400665 00000 n
+0000400862 00000 n
+0000402073 00000 n
+0000402277 00000 n
+0000403623 00000 n
+0000403809 00000 n
+0000404285 00000 n
+0000404473 00000 n
+0000405961 00000 n
+0000406131 00000 n
+0000407638 00000 n
+0000407808 00000 n
+0000409207 00000 n
+0000409377 00000 n
+0000410926 00000 n
+0000411095 00000 n
+0000412058 00000 n
+0000412279 00000 n
+0000413813 00000 n
+0000414034 00000 n
+0000415641 00000 n
+0000415863 00000 n
+0000417113 00000 n
+0000417292 00000 n
+0000418837 00000 n
+0000419016 00000 n
+0000420253 00000 n
+0000420457 00000 n
+0000421869 00000 n
+0000422064 00000 n
+0000424693 00000 n
+0000424869 00000 n
+0000425319 00000 n
+0000425498 00000 n
+0000427026 00000 n
+0000427214 00000 n
+0000428182 00000 n
+0000428352 00000 n
+0000428682 00000 n
+0000428878 00000 n
+0000430608 00000 n
+0000430822 00000 n
+0000432506 00000 n
+0000432701 00000 n
+0000434408 00000 n
+0000434621 00000 n
+0000436109 00000 n
+0000436304 00000 n
+0000437886 00000 n
+0000438109 00000 n
+0000439474 00000 n
+0000439671 00000 n
+0000441208 00000 n
+0000441396 00000 n
+0000442275 00000 n
+0000442479 00000 n
+0000444215 00000 n
+0000444403 00000 n
+0000446145 00000 n
+0000446324 00000 n
+0000447723 00000 n
+0000447902 00000 n
+0000449600 00000 n
+0000449779 00000 n
+0000451259 00000 n
+0000451438 00000 n
+0000453224 00000 n
+0000453428 00000 n
+0000455079 00000 n
+0000455138 00000 n
+0000455241 00000 n
+0000455406 00000 n
+0000455488 00000 n
+0000455596 00000 n
+0000455719 00000 n
+0000455831 00000 n
+0000456009 00000 n
+0000456130 00000 n
+0000456290 00000 n
+0000456408 00000 n
+0000456505 00000 n
+0000456657 00000 n
+0000456797 00000 n
+0000456975 00000 n
+0000457130 00000 n
+0000457232 00000 n
+0000457332 00000 n
+0000457541 00000 n
+0000457642 00000 n
+0000457785 00000 n
+0000457931 00000 n
+0000458047 00000 n
+0000458214 00000 n
+0000458326 00000 n
+0000458500 00000 n
+0000458603 00000 n
+0000458776 00000 n
+0000458897 00000 n
+0000459027 00000 n
+0000459153 00000 n
+0000459268 00000 n
+0000459376 00000 n
+0000459523 00000 n
+0000459628 00000 n
+0000459747 00000 n
+0000459876 00000 n
+0000460035 00000 n
+0000460169 00000 n
+0000460306 00000 n
+0000460438 00000 n
+0000460587 00000 n
+0000460719 00000 n
+0000460867 00000 n
+0000460968 00000 n
+0000461096 00000 n
+0000461214 00000 n
+0000461368 00000 n
+0000461499 00000 n
+0000461645 00000 n
+0000461746 00000 n
+0000461844 00000 n
+0000461968 00000 n
+0000462080 00000 n
+0000462257 00000 n
+0000462366 00000 n
+0000462491 00000 n
+0000462637 00000 n
+0000462739 00000 n
+0000462911 00000 n
+0000463110 00000 n
+0000463221 00000 n
+0000463336 00000 n
+0000463480 00000 n
+0000463688 00000 n
+0000463822 00000 n
+0000463976 00000 n
+0000464101 00000 n
+0000464232 00000 n
+0000464365 00000 n
+0000464496 00000 n
+0000464671 00000 n
+0000464806 00000 n
+0000464959 00000 n
+0000465104 00000 n
+0000465329 00000 n
+0000465440 00000 n
+0000465555 00000 n
+0000465748 00000 n
+0000465891 00000 n
+0000466007 00000 n
+0000466165 00000 n
+0000466322 00000 n
+0000466453 00000 n
+0000466574 00000 n
+0000466751 00000 n
+0000466885 00000 n
+0000467033 00000 n
+0000467151 00000 n
+0000467281 00000 n
+0000467451 00000 n
+0000467545 00000 n
+0000467672 00000 n
+0000467799 00000 n
+0000467895 00000 n
+0000468081 00000 n
+0000468207 00000 n
+0000468342 00000 n
+0000468475 00000 n
+0000468602 00000 n
+0000468714 00000 n
+0000468906 00000 n
+0000469004 00000 n
+0000469190 00000 n
+0000469294 00000 n
+0000469418 00000 n
+0000469540 00000 n
+0000469652 00000 n
+0000469848 00000 n
+0000469964 00000 n
+0000470088 00000 n
+0000470206 00000 n
+0000470324 00000 n
+0000470429 00000 n
+0000470618 00000 n
+0000470841 00000 n
+0000470980 00000 n
+0000471143 00000 n
+0000471280 00000 n
+0000471383 00000 n
+0000471589 00000 n
+0000471748 00000 n
+0000471896 00000 n
+0000472024 00000 n
+0000472205 00000 n
+0000472315 00000 n
+0000472430 00000 n
+0000472575 00000 n
+0000472739 00000 n
+0000472889 00000 n
+0000473107 00000 n
+0000473212 00000 n
+0000473344 00000 n
+0000473465 00000 n
+0000473672 00000 n
+0000473800 00000 n
+0000473885 00000 n
+0000474051 00000 n
+0000474155 00000 n
+0000474312 00000 n
+0000474423 00000 n
+0000474568 00000 n
+0000474710 00000 n
+0000474860 00000 n
+0000474977 00000 n
+0000475141 00000 n
+0000475252 00000 n
+0000475392 00000 n
+0000475519 00000 n
+0000475636 00000 n
+0000475775 00000 n
+0000475881 00000 n
+0000476015 00000 n
+0000476147 00000 n
+0000476292 00000 n
+0000476419 00000 n
+0000476551 00000 n
+0000476681 00000 n
+0000476806 00000 n
+0000476914 00000 n
+0000477085 00000 n
+0000477189 00000 n
+0000477324 00000 n
+0000477452 00000 n
+0000477626 00000 n
+0000477728 00000 n
+0000477878 00000 n
+0000478028 00000 n
+0000478153 00000 n
+0000478359 00000 n
+0000478459 00000 n
+0000478577 00000 n
+0000478742 00000 n
+0000478833 00000 n
+0000478994 00000 n
+0000479120 00000 n
+0000479263 00000 n
+0000479390 00000 n
+0000479530 00000 n
+0000479666 00000 n
+0000479774 00000 n
+0000479948 00000 n
+0000480054 00000 n
+0000480174 00000 n
+0000480286 00000 n
+0000480403 00000 n
+0000480505 00000 n
+0000480682 00000 n
+0000480794 00000 n
+0000480925 00000 n
+0000481049 00000 n
+0000481216 00000 n
+0000481333 00000 n
+0000481463 00000 n
+0000481603 00000 n
+0000481740 00000 n
+0000481876 00000 n
+0000482012 00000 n
+0000482149 00000 n
+0000482261 00000 n
+0000482432 00000 n
+0000482554 00000 n
+0000482714 00000 n
+0000482813 00000 n
+0000482928 00000 n
+0000483030 00000 n
+0000483191 00000 n
+0000483295 00000 n
+0000483394 00000 n
+0000483525 00000 n
+0000483700 00000 n
+0000483803 00000 n
+0000483923 00000 n
+0000484038 00000 n
+0000484152 00000 n
+0000484267 00000 n
+0000484381 00000 n
+0000484496 00000 n
+0000484614 00000 n
+0000484731 00000 n
+0000484837 00000 n
+0000485015 00000 n
+0000485118 00000 n
+0000485274 00000 n
+0000485382 00000 n
+0000485508 00000 n
+0000485628 00000 n
+0000485729 00000 n
+0000485836 00000 n
+0000486000 00000 n
+0000486104 00000 n
+0000486237 00000 n
+0000486369 00000 n
+0000486491 00000 n
+0000486620 00000 n
+0000486727 00000 n
+0000486893 00000 n
+0000487015 00000 n
+0000487125 00000 n
+0000487239 00000 n
+0000487400 00000 n
+0000487496 00000 n
+0000487610 00000 n
+0000487720 00000 n
+0000487851 00000 n
+0000487984 00000 n
+0000488085 00000 n
+0000488263 00000 n
+0000488373 00000 n
+0000488527 00000 n
+0000488696 00000 n
+0000488884 00000 n
+0000489065 00000 n
+0000489221 00000 n
+0000489387 00000 n
+0000489519 00000 n
+0000489666 00000 n
+0000489805 00000 n
+0000489939 00000 n
+0000490063 00000 n
+0000490184 00000 n
+0000490303 00000 n
+0000490473 00000 n
+0000490635 00000 n
+0000490741 00000 n
+0000490858 00000 n
+0000491009 00000 n
+0000491136 00000 n
+0000491292 00000 n
+0000491410 00000 n
+0000491540 00000 n
+0000491704 00000 n
+0000491808 00000 n
+0000491926 00000 n
+0000492044 00000 n
+0000492165 00000 n
+0000492301 00000 n
+0000492400 00000 n
+0000492555 00000 n
+0000492659 00000 n
+0000492776 00000 n
+0000492926 00000 n
+0000493026 00000 n
+0000493140 00000 n
+0000493254 00000 n
+0000493368 00000 n
+0000493482 00000 n
+0000493596 00000 n
+0000493710 00000 n
+0000493824 00000 n
+0000493938 00000 n
+0000494054 00000 n
+0000494156 00000 n
+0000494270 00000 n
trailer
-<<
-/Size 3776
-/Root 3774 0 R
-/Info 3775 0 R
->>
+<</Size 2126/Root 2125 0 R/Info 1 0 R/ID[<44d39a97f681ab9eaa30845c7407c375><44d39a97f681ab9eaa30845c7407c375>]>>
startxref
-1081637
+495224
%%EOF
diff --git a/docs/announce b/docs/announce
index 7310bdd737..f5716556ba 100644
--- a/docs/announce
+++ b/docs/announce
@@ -1,6 +1,3 @@
-This document is out of date
-
-
Announcing Samba version 2.2
============================
diff --git a/docs/docbook/.cvsignore b/docs/docbook/.cvsignore
index 052b1cf2a2..04290fcd2e 100644
--- a/docs/docbook/.cvsignore
+++ b/docs/docbook/.cvsignore
@@ -2,5 +2,3 @@ Makefile
config.cache
config.log
config.status
-samba-doc.*
-dev-doc.* \ No newline at end of file
diff --git a/docs/docbook/Makefile.in b/docs/docbook/Makefile.in
index 6dad4664fd..673db0f342 100644
--- a/docs/docbook/Makefile.in
+++ b/docs/docbook/Makefile.in
@@ -37,6 +37,7 @@ HTMLDIR=../htmldocs
MANPROJDOC = manpages
PROJDOC = projdoc
DEVDOC = devdoc
+XMLTO = @XMLTO@
SMBDOTCONFDOC = smbdotconf
PSDIR = ..
PDFDIR = ..
@@ -50,20 +51,23 @@ MANPAGES_HTML=$(patsubst %,$(HTMLDIR)/%.html,$(MANPAGES_NAMES))
all:
@echo "Supported make targets:"
@echo "manpages - Build manpages"
- @echo "pdf - Build PDF version of HOWTO Collection"
+ @echo "pdf - Build PDF version of HOWTO Collection and Developers Guide"
+ @echo "txt - Build plain text version of HOWTO Collection and Developers Guide"
@echo -n "html-single - Build single file HTML version of HOWTO Collection"
@echo " and developers guide"
- @echo "html - Build HTML version of HOWTO Collection"
+ @echo "html - Build HTML version of HOWTO Collection and Developers Guide"
@echo "htmlman - Build html version of manpages"
@echo "htmlfaq - Build html version of the FAQ"
@echo "everything - Build all of the above"
-everything: manpages pdf html-single html htmlman htmlfaq
+everything: manpages pdf html-single html htmlman htmlfaq txt
# Global rules
manpages: $(MANDIR) $(MANPAGES)
pdf: $(PDFDIR) $(PDFDIR)/Samba-HOWTO-Collection.pdf $(PDFDIR)/Samba-Developers-Guide.pdf
+hpdf: $(PDFDIR) $(PDFDIR)/Samba-HOWTO-Collection.pdf
+txt: $(TXTDIR) $(TXTDIR)/Samba-HOWTO-Collection.txt $(TXTDIR)/Samba-Developers-Guide.txt
htmlman: $(HTMLDIR) $(MANPAGES_HTML) CSS
htmlfaq: $(HTMLDIR) CSS
@$(XSLTPROC) --stringparam base.dir "$(FAQDIR)/" --stringparam root.filename samba-faq xslt/html-chunk.xsl $(FAQPROJDOC)/sambafaq.xml
@@ -72,6 +76,18 @@ html: $(HTMLDIR) CSS
@$(XSLTPROC) xslt/html-chunk.xsl $(PROJDOC)/samba-doc.xml
# Text files
+$(TXTDIR):
+ mkdir $(TXTDIR)
+
+$(TXTDIR)/Samba-HOWTO-Collection.txt: $(PROJDOC)/samba-doc.xml
+ @echo "Converting samba-doc to plain text..."
+ @$(XMLTO) txt -o $(TXTDIR) $<
+ @mv $(TXTDIR)/samba-doc.txt $(TXTDIR)/Samba-HOWTO-Collection.txt
+
+$(TXTDIR)/Samba-Developers-Guide.txt: $(DEVDOC)/dev-doc.xml
+ @echo "Converting dev-doc to plain text..."
+ @$(XMLTO) txt -o $(TXTDIR) $<
+ @mv $(TXTDIR)/dev-doc.txt $(TXTDIR)/Samba-Developers-Guide.txt
# Adobe PDF files
$(PDFDIR)/Samba-HOWTO-Collection.pdf: $(PROJDOC)/samba-doc.xml
diff --git a/docs/docbook/configure b/docs/docbook/configure
index 690e16437a..f668d8c2b6 100755
--- a/docs/docbook/configure
+++ b/docs/docbook/configure
@@ -1,287 +1,26 @@
#! /bin/sh
+
# Guess values for system-dependent variables and create Makefiles.
-# Generated by GNU Autoconf 2.57.
+# Generated automatically using autoconf version 2.13
+# Copyright (C) 1992, 93, 94, 95, 96 Free Software Foundation, Inc.
#
-# Copyright 1992, 1993, 1994, 1995, 1996, 1998, 1999, 2000, 2001, 2002
-# Free Software Foundation, Inc.
# This configure script is free software; the Free Software Foundation
# gives unlimited permission to copy, distribute and modify it.
-## --------------------- ##
-## M4sh Initialization. ##
-## --------------------- ##
-
-# Be Bourne compatible
-if test -n "${ZSH_VERSION+set}" && (emulate sh) >/dev/null 2>&1; then
- emulate sh
- NULLCMD=:
- # Zsh 3.x and 4.x performs word splitting on ${1+"$@"}, which
- # is contrary to our usage. Disable this feature.
- alias -g '${1+"$@"}'='"$@"'
-elif test -n "${BASH_VERSION+set}" && (set -o posix) >/dev/null 2>&1; then
- set -o posix
-fi
-
-# Support unset when possible.
-if (FOO=FOO; unset FOO) >/dev/null 2>&1; then
- as_unset=unset
-else
- as_unset=false
-fi
-
-
-# Work around bugs in pre-3.0 UWIN ksh.
-$as_unset ENV MAIL MAILPATH
-PS1='$ '
-PS2='> '
-PS4='+ '
-
-# NLS nuisances.
-for as_var in \
- LANG LANGUAGE LC_ADDRESS LC_ALL LC_COLLATE LC_CTYPE LC_IDENTIFICATION \
- LC_MEASUREMENT LC_MESSAGES LC_MONETARY LC_NAME LC_NUMERIC LC_PAPER \
- LC_TELEPHONE LC_TIME
-do
- if (set +x; test -n "`(eval $as_var=C; export $as_var) 2>&1`"); then
- eval $as_var=C; export $as_var
- else
- $as_unset $as_var
- fi
-done
-
-# Required to use basename.
-if expr a : '\(a\)' >/dev/null 2>&1; then
- as_expr=expr
-else
- as_expr=false
-fi
-
-if (basename /) >/dev/null 2>&1 && test "X`basename / 2>&1`" = "X/"; then
- as_basename=basename
-else
- as_basename=false
-fi
-
-
-# Name of the executable.
-as_me=`$as_basename "$0" ||
-$as_expr X/"$0" : '.*/\([^/][^/]*\)/*$' \| \
- X"$0" : 'X\(//\)$' \| \
- X"$0" : 'X\(/\)$' \| \
- . : '\(.\)' 2>/dev/null ||
-echo X/"$0" |
- sed '/^.*\/\([^/][^/]*\)\/*$/{ s//\1/; q; }
- /^X\/\(\/\/\)$/{ s//\1/; q; }
- /^X\/\(\/\).*/{ s//\1/; q; }
- s/.*/./; q'`
-
-
-# PATH needs CR, and LINENO needs CR and PATH.
-# Avoid depending upon Character Ranges.
-as_cr_letters='abcdefghijklmnopqrstuvwxyz'
-as_cr_LETTERS='ABCDEFGHIJKLMNOPQRSTUVWXYZ'
-as_cr_Letters=$as_cr_letters$as_cr_LETTERS
-as_cr_digits='0123456789'
-as_cr_alnum=$as_cr_Letters$as_cr_digits
-
-# The user is always right.
-if test "${PATH_SEPARATOR+set}" != set; then
- echo "#! /bin/sh" >conf$$.sh
- echo "exit 0" >>conf$$.sh
- chmod +x conf$$.sh
- if (PATH="/nonexistent;."; conf$$.sh) >/dev/null 2>&1; then
- PATH_SEPARATOR=';'
- else
- PATH_SEPARATOR=:
- fi
- rm -f conf$$.sh
-fi
-
-
- as_lineno_1=$LINENO
- as_lineno_2=$LINENO
- as_lineno_3=`(expr $as_lineno_1 + 1) 2>/dev/null`
- test "x$as_lineno_1" != "x$as_lineno_2" &&
- test "x$as_lineno_3" = "x$as_lineno_2" || {
- # Find who we are. Look in the path if we contain no path at all
- # relative or not.
- case $0 in
- *[\\/]* ) as_myself=$0 ;;
- *) as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
-for as_dir in $PATH
-do
- IFS=$as_save_IFS
- test -z "$as_dir" && as_dir=.
- test -r "$as_dir/$0" && as_myself=$as_dir/$0 && break
-done
-
- ;;
- esac
- # We did not find ourselves, most probably we were run as `sh COMMAND'
- # in which case we are not to be found in the path.
- if test "x$as_myself" = x; then
- as_myself=$0
- fi
- if test ! -f "$as_myself"; then
- { echo "$as_me: error: cannot find myself; rerun with an absolute path" >&2
- { (exit 1); exit 1; }; }
- fi
- case $CONFIG_SHELL in
- '')
- as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
-for as_dir in /bin$PATH_SEPARATOR/usr/bin$PATH_SEPARATOR$PATH
-do
- IFS=$as_save_IFS
- test -z "$as_dir" && as_dir=.
- for as_base in sh bash ksh sh5; do
- case $as_dir in
- /*)
- if ("$as_dir/$as_base" -c '
- as_lineno_1=$LINENO
- as_lineno_2=$LINENO
- as_lineno_3=`(expr $as_lineno_1 + 1) 2>/dev/null`
- test "x$as_lineno_1" != "x$as_lineno_2" &&
- test "x$as_lineno_3" = "x$as_lineno_2" ') 2>/dev/null; then
- $as_unset BASH_ENV || test "${BASH_ENV+set}" != set || { BASH_ENV=; export BASH_ENV; }
- $as_unset ENV || test "${ENV+set}" != set || { ENV=; export ENV; }
- CONFIG_SHELL=$as_dir/$as_base
- export CONFIG_SHELL
- exec "$CONFIG_SHELL" "$0" ${1+"$@"}
- fi;;
- esac
- done
-done
-;;
- esac
-
- # Create $as_me.lineno as a copy of $as_myself, but with $LINENO
- # uniformly replaced by the line number. The first 'sed' inserts a
- # line-number line before each line; the second 'sed' does the real
- # work. The second script uses 'N' to pair each line-number line
- # with the numbered line, and appends trailing '-' during
- # substitution so that $LINENO is not a special case at line end.
- # (Raja R Harinath suggested sed '=', and Paul Eggert wrote the
- # second 'sed' script. Blame Lee E. McMahon for sed's syntax. :-)
- sed '=' <$as_myself |
- sed '
- N
- s,$,-,
- : loop
- s,^\(['$as_cr_digits']*\)\(.*\)[$]LINENO\([^'$as_cr_alnum'_]\),\1\2\1\3,
- t loop
- s,-$,,
- s,^['$as_cr_digits']*\n,,
- ' >$as_me.lineno &&
- chmod +x $as_me.lineno ||
- { echo "$as_me: error: cannot create $as_me.lineno; rerun with a POSIX shell" >&2
- { (exit 1); exit 1; }; }
-
- # Don't try to exec as it changes $[0], causing all sort of problems
- # (the dirname of $[0] is not the place where we might find the
- # original and so on. Autoconf is especially sensible to this).
- . ./$as_me.lineno
- # Exit status is that of the last command.
- exit
-}
-
-
-case `echo "testing\c"; echo 1,2,3`,`echo -n testing; echo 1,2,3` in
- *c*,-n*) ECHO_N= ECHO_C='
-' ECHO_T=' ' ;;
- *c*,* ) ECHO_N=-n ECHO_C= ECHO_T= ;;
- *) ECHO_N= ECHO_C='\c' ECHO_T= ;;
-esac
-
-if expr a : '\(a\)' >/dev/null 2>&1; then
- as_expr=expr
-else
- as_expr=false
-fi
-
-rm -f conf$$ conf$$.exe conf$$.file
-echo >conf$$.file
-if ln -s conf$$.file conf$$ 2>/dev/null; then
- # We could just check for DJGPP; but this test a) works b) is more generic
- # and c) will remain valid once DJGPP supports symlinks (DJGPP 2.04).
- if test -f conf$$.exe; then
- # Don't use ln at all; we don't have any links
- as_ln_s='cp -p'
- else
- as_ln_s='ln -s'
- fi
-elif ln conf$$.file conf$$ 2>/dev/null; then
- as_ln_s=ln
-else
- as_ln_s='cp -p'
-fi
-rm -f conf$$ conf$$.exe conf$$.file
-
-if mkdir -p . 2>/dev/null; then
- as_mkdir_p=:
-else
- as_mkdir_p=false
-fi
-as_executable_p="test -f"
-
-# Sed expression to map a string onto a valid CPP name.
-as_tr_cpp="sed y%*$as_cr_letters%P$as_cr_LETTERS%;s%[^_$as_cr_alnum]%_%g"
-
-# Sed expression to map a string onto a valid variable name.
-as_tr_sh="sed y%*+%pp%;s%[^_$as_cr_alnum]%_%g"
-
-
-# IFS
-# We need space, tab and new line, in precisely that order.
-as_nl='
-'
-IFS=" $as_nl"
-
-# CDPATH.
-$as_unset CDPATH
-
-
-# Name of the host.
-# hostname on some systems (SVR3.2, Linux) returns a bogus exit status,
-# so uname gets run too.
-ac_hostname=`(hostname || uname -n) 2>/dev/null | sed 1q`
-
-exec 6>&1
-
-#
-# Initializations.
-#
+# Defaults:
+ac_help=
ac_default_prefix=/usr/local
-ac_config_libobj_dir=.
-cross_compiling=no
-subdirs=
-MFLAGS=
-MAKEFLAGS=
-SHELL=${CONFIG_SHELL-/bin/sh}
-
-# Maximum number of lines to put in a shell here document.
-# This variable seems obsolete. It should probably be removed, and
-# only ac_max_sed_lines should be used.
-: ${ac_max_here_lines=38}
-
-# Identity of this package.
-PACKAGE_NAME=
-PACKAGE_TARNAME=
-PACKAGE_VERSION=
-PACKAGE_STRING=
-PACKAGE_BUGREPORT=
-
-ac_unique_file="global.ent"
-ac_subst_vars='SHELL PATH_SEPARATOR PACKAGE_NAME PACKAGE_TARNAME PACKAGE_VERSION PACKAGE_STRING PACKAGE_BUGREPORT exec_prefix prefix program_transform_name bindir sbindir libexecdir datadir sysconfdir sharedstatedir localstatedir libdir includedir oldincludedir infodir mandir build_alias host_alias target_alias DEFS ECHO_C ECHO_N ECHO_T LIBS XSLTPROC PDFLATEX DOC_BUILD_DATE LIBOBJS LTLIBOBJS'
-ac_subst_files=''
+# Any additions from configure.in:
# Initialize some variables set by options.
-ac_init_help=
-ac_init_version=false
# The variables have the same names as the options, with
# dashes changed to underlines.
-cache_file=/dev/null
+build=NONE
+cache_file=./config.cache
exec_prefix=NONE
+host=NONE
no_create=
+nonopt=NONE
no_recursion=
prefix=NONE
program_prefix=NONE
@@ -290,15 +29,10 @@ program_transform_name=s,x,x,
silent=
site=
srcdir=
+target=NONE
verbose=
x_includes=NONE
x_libraries=NONE
-
-# Installation directory options.
-# These are left unexpanded so users can "make install exec_prefix=/foo"
-# and all the variables that are supposed to be based on exec_prefix
-# by default will actually change.
-# Use braces instead of parens because sh, perl, etc. also accept them.
bindir='${exec_prefix}/bin'
sbindir='${exec_prefix}/sbin'
libexecdir='${exec_prefix}/libexec'
@@ -312,9 +46,17 @@ oldincludedir='/usr/include'
infodir='${prefix}/info'
mandir='${prefix}/man'
+# Initialize some other variables.
+subdirs=
+MFLAGS= MAKEFLAGS=
+SHELL=${CONFIG_SHELL-/bin/sh}
+# Maximum number of lines to put in a shell here document.
+ac_max_here_lines=12
+
ac_prev=
for ac_option
do
+
# If the previous option needs an argument, assign it.
if test -n "$ac_prev"; then
eval "$ac_prev=\$ac_option"
@@ -322,59 +64,59 @@ do
continue
fi
- ac_optarg=`expr "x$ac_option" : 'x[^=]*=\(.*\)'`
+ case "$ac_option" in
+ -*=*) ac_optarg=`echo "$ac_option" | sed 's/[-_a-zA-Z0-9]*=//'` ;;
+ *) ac_optarg= ;;
+ esac
# Accept the important Cygnus configure options, so we can diagnose typos.
- case $ac_option in
+ case "$ac_option" in
-bindir | --bindir | --bindi | --bind | --bin | --bi)
ac_prev=bindir ;;
-bindir=* | --bindir=* | --bindi=* | --bind=* | --bin=* | --bi=*)
- bindir=$ac_optarg ;;
+ bindir="$ac_optarg" ;;
-build | --build | --buil | --bui | --bu)
- ac_prev=build_alias ;;
+ ac_prev=build ;;
-build=* | --build=* | --buil=* | --bui=* | --bu=*)
- build_alias=$ac_optarg ;;
+ build="$ac_optarg" ;;
-cache-file | --cache-file | --cache-fil | --cache-fi \
| --cache-f | --cache- | --cache | --cach | --cac | --ca | --c)
ac_prev=cache_file ;;
-cache-file=* | --cache-file=* | --cache-fil=* | --cache-fi=* \
| --cache-f=* | --cache-=* | --cache=* | --cach=* | --cac=* | --ca=* | --c=*)
- cache_file=$ac_optarg ;;
-
- --config-cache | -C)
- cache_file=config.cache ;;
+ cache_file="$ac_optarg" ;;
-datadir | --datadir | --datadi | --datad | --data | --dat | --da)
ac_prev=datadir ;;
-datadir=* | --datadir=* | --datadi=* | --datad=* | --data=* | --dat=* \
| --da=*)
- datadir=$ac_optarg ;;
+ datadir="$ac_optarg" ;;
-disable-* | --disable-*)
- ac_feature=`expr "x$ac_option" : 'x-*disable-\(.*\)'`
+ ac_feature=`echo $ac_option|sed -e 's/-*disable-//'`
# Reject names that are not valid shell variable names.
- expr "x$ac_feature" : ".*[^-_$as_cr_alnum]" >/dev/null &&
- { echo "$as_me: error: invalid feature name: $ac_feature" >&2
- { (exit 1); exit 1; }; }
- ac_feature=`echo $ac_feature | sed 's/-/_/g'`
- eval "enable_$ac_feature=no" ;;
+ if test -n "`echo $ac_feature| sed 's/[-a-zA-Z0-9_]//g'`"; then
+ { echo "configure: error: $ac_feature: invalid feature name" 1>&2; exit 1; }
+ fi
+ ac_feature=`echo $ac_feature| sed 's/-/_/g'`
+ eval "enable_${ac_feature}=no" ;;
-enable-* | --enable-*)
- ac_feature=`expr "x$ac_option" : 'x-*enable-\([^=]*\)'`
+ ac_feature=`echo $ac_option|sed -e 's/-*enable-//' -e 's/=.*//'`
# Reject names that are not valid shell variable names.
- expr "x$ac_feature" : ".*[^-_$as_cr_alnum]" >/dev/null &&
- { echo "$as_me: error: invalid feature name: $ac_feature" >&2
- { (exit 1); exit 1; }; }
- ac_feature=`echo $ac_feature | sed 's/-/_/g'`
- case $ac_option in
- *=*) ac_optarg=`echo "$ac_optarg" | sed "s/'/'\\\\\\\\''/g"`;;
+ if test -n "`echo $ac_feature| sed 's/[-_a-zA-Z0-9]//g'`"; then
+ { echo "configure: error: $ac_feature: invalid feature name" 1>&2; exit 1; }
+ fi
+ ac_feature=`echo $ac_feature| sed 's/-/_/g'`
+ case "$ac_option" in
+ *=*) ;;
*) ac_optarg=yes ;;
esac
- eval "enable_$ac_feature='$ac_optarg'" ;;
+ eval "enable_${ac_feature}='$ac_optarg'" ;;
-exec-prefix | --exec_prefix | --exec-prefix | --exec-prefi \
| --exec-pref | --exec-pre | --exec-pr | --exec-p | --exec- \
@@ -383,47 +125,95 @@ do
-exec-prefix=* | --exec_prefix=* | --exec-prefix=* | --exec-prefi=* \
| --exec-pref=* | --exec-pre=* | --exec-pr=* | --exec-p=* | --exec-=* \
| --exec=* | --exe=* | --ex=*)
- exec_prefix=$ac_optarg ;;
+ exec_prefix="$ac_optarg" ;;
-gas | --gas | --ga | --g)
# Obsolete; use --with-gas.
with_gas=yes ;;
- -help | --help | --hel | --he | -h)
- ac_init_help=long ;;
- -help=r* | --help=r* | --hel=r* | --he=r* | -hr*)
- ac_init_help=recursive ;;
- -help=s* | --help=s* | --hel=s* | --he=s* | -hs*)
- ac_init_help=short ;;
+ -help | --help | --hel | --he)
+ # Omit some internal or obsolete options to make the list less imposing.
+ # This message is too long to be a string in the A/UX 3.1 sh.
+ cat << EOF
+Usage: configure [options] [host]
+Options: [defaults in brackets after descriptions]
+Configuration:
+ --cache-file=FILE cache test results in FILE
+ --help print this message
+ --no-create do not create output files
+ --quiet, --silent do not print \`checking...' messages
+ --version print the version of autoconf that created configure
+Directory and file names:
+ --prefix=PREFIX install architecture-independent files in PREFIX
+ [$ac_default_prefix]
+ --exec-prefix=EPREFIX install architecture-dependent files in EPREFIX
+ [same as prefix]
+ --bindir=DIR user executables in DIR [EPREFIX/bin]
+ --sbindir=DIR system admin executables in DIR [EPREFIX/sbin]
+ --libexecdir=DIR program executables in DIR [EPREFIX/libexec]
+ --datadir=DIR read-only architecture-independent data in DIR
+ [PREFIX/share]
+ --sysconfdir=DIR read-only single-machine data in DIR [PREFIX/etc]
+ --sharedstatedir=DIR modifiable architecture-independent data in DIR
+ [PREFIX/com]
+ --localstatedir=DIR modifiable single-machine data in DIR [PREFIX/var]
+ --libdir=DIR object code libraries in DIR [EPREFIX/lib]
+ --includedir=DIR C header files in DIR [PREFIX/include]
+ --oldincludedir=DIR C header files for non-gcc in DIR [/usr/include]
+ --infodir=DIR info documentation in DIR [PREFIX/info]
+ --mandir=DIR man documentation in DIR [PREFIX/man]
+ --srcdir=DIR find the sources in DIR [configure dir or ..]
+ --program-prefix=PREFIX prepend PREFIX to installed program names
+ --program-suffix=SUFFIX append SUFFIX to installed program names
+ --program-transform-name=PROGRAM
+ run sed PROGRAM on installed program names
+EOF
+ cat << EOF
+Host type:
+ --build=BUILD configure for building on BUILD [BUILD=HOST]
+ --host=HOST configure for HOST [guessed]
+ --target=TARGET configure for TARGET [TARGET=HOST]
+Features and packages:
+ --disable-FEATURE do not include FEATURE (same as --enable-FEATURE=no)
+ --enable-FEATURE[=ARG] include FEATURE [ARG=yes]
+ --with-PACKAGE[=ARG] use PACKAGE [ARG=yes]
+ --without-PACKAGE do not use PACKAGE (same as --with-PACKAGE=no)
+ --x-includes=DIR X include files are in DIR
+ --x-libraries=DIR X library files are in DIR
+EOF
+ if test -n "$ac_help"; then
+ echo "--enable and --with options recognized:$ac_help"
+ fi
+ exit 0 ;;
-host | --host | --hos | --ho)
- ac_prev=host_alias ;;
+ ac_prev=host ;;
-host=* | --host=* | --hos=* | --ho=*)
- host_alias=$ac_optarg ;;
+ host="$ac_optarg" ;;
-includedir | --includedir | --includedi | --included | --include \
| --includ | --inclu | --incl | --inc)
ac_prev=includedir ;;
-includedir=* | --includedir=* | --includedi=* | --included=* | --include=* \
| --includ=* | --inclu=* | --incl=* | --inc=*)
- includedir=$ac_optarg ;;
+ includedir="$ac_optarg" ;;
-infodir | --infodir | --infodi | --infod | --info | --inf)
ac_prev=infodir ;;
-infodir=* | --infodir=* | --infodi=* | --infod=* | --info=* | --inf=*)
- infodir=$ac_optarg ;;
+ infodir="$ac_optarg" ;;
-libdir | --libdir | --libdi | --libd)
ac_prev=libdir ;;
-libdir=* | --libdir=* | --libdi=* | --libd=*)
- libdir=$ac_optarg ;;
+ libdir="$ac_optarg" ;;
-libexecdir | --libexecdir | --libexecdi | --libexecd | --libexec \
| --libexe | --libex | --libe)
ac_prev=libexecdir ;;
-libexecdir=* | --libexecdir=* | --libexecdi=* | --libexecd=* | --libexec=* \
| --libexe=* | --libex=* | --libe=*)
- libexecdir=$ac_optarg ;;
+ libexecdir="$ac_optarg" ;;
-localstatedir | --localstatedir | --localstatedi | --localstated \
| --localstate | --localstat | --localsta | --localst \
@@ -432,19 +222,19 @@ do
-localstatedir=* | --localstatedir=* | --localstatedi=* | --localstated=* \
| --localstate=* | --localstat=* | --localsta=* | --localst=* \
| --locals=* | --local=* | --loca=* | --loc=* | --lo=*)
- localstatedir=$ac_optarg ;;
+ localstatedir="$ac_optarg" ;;
-mandir | --mandir | --mandi | --mand | --man | --ma | --m)
ac_prev=mandir ;;
-mandir=* | --mandir=* | --mandi=* | --mand=* | --man=* | --ma=* | --m=*)
- mandir=$ac_optarg ;;
+ mandir="$ac_optarg" ;;
-nfp | --nfp | --nf)
# Obsolete; use --without-fp.
with_fp=no ;;
-no-create | --no-create | --no-creat | --no-crea | --no-cre \
- | --no-cr | --no-c | -n)
+ | --no-cr | --no-c)
no_create=yes ;;
-no-recursion | --no-recursion | --no-recursio | --no-recursi \
@@ -458,26 +248,26 @@ do
-oldincludedir=* | --oldincludedir=* | --oldincludedi=* | --oldincluded=* \
| --oldinclude=* | --oldinclud=* | --oldinclu=* | --oldincl=* | --oldinc=* \
| --oldin=* | --oldi=* | --old=* | --ol=* | --o=*)
- oldincludedir=$ac_optarg ;;
+ oldincludedir="$ac_optarg" ;;
-prefix | --prefix | --prefi | --pref | --pre | --pr | --p)
ac_prev=prefix ;;
-prefix=* | --prefix=* | --prefi=* | --pref=* | --pre=* | --pr=* | --p=*)
- prefix=$ac_optarg ;;
+ prefix="$ac_optarg" ;;
-program-prefix | --program-prefix | --program-prefi | --program-pref \
| --program-pre | --program-pr | --program-p)
ac_prev=program_prefix ;;
-program-prefix=* | --program-prefix=* | --program-prefi=* \
| --program-pref=* | --program-pre=* | --program-pr=* | --program-p=*)
- program_prefix=$ac_optarg ;;
+ program_prefix="$ac_optarg" ;;
-program-suffix | --program-suffix | --program-suffi | --program-suff \
| --program-suf | --program-su | --program-s)
ac_prev=program_suffix ;;
-program-suffix=* | --program-suffix=* | --program-suffi=* \
| --program-suff=* | --program-suf=* | --program-su=* | --program-s=*)
- program_suffix=$ac_optarg ;;
+ program_suffix="$ac_optarg" ;;
-program-transform-name | --program-transform-name \
| --program-transform-nam | --program-transform-na \
@@ -494,7 +284,7 @@ do
| --program-transfo=* | --program-transf=* \
| --program-trans=* | --program-tran=* \
| --progr-tra=* | --program-tr=* | --program-t=*)
- program_transform_name=$ac_optarg ;;
+ program_transform_name="$ac_optarg" ;;
-q | -quiet | --quiet | --quie | --qui | --qu | --q \
| -silent | --silent | --silen | --sile | --sil)
@@ -504,7 +294,7 @@ do
ac_prev=sbindir ;;
-sbindir=* | --sbindir=* | --sbindi=* | --sbind=* | --sbin=* \
| --sbi=* | --sb=*)
- sbindir=$ac_optarg ;;
+ sbindir="$ac_optarg" ;;
-sharedstatedir | --sharedstatedir | --sharedstatedi \
| --sharedstated | --sharedstate | --sharedstat | --sharedsta \
@@ -515,57 +305,58 @@ do
| --sharedstated=* | --sharedstate=* | --sharedstat=* | --sharedsta=* \
| --sharedst=* | --shareds=* | --shared=* | --share=* | --shar=* \
| --sha=* | --sh=*)
- sharedstatedir=$ac_optarg ;;
+ sharedstatedir="$ac_optarg" ;;
-site | --site | --sit)
ac_prev=site ;;
-site=* | --site=* | --sit=*)
- site=$ac_optarg ;;
+ site="$ac_optarg" ;;
-srcdir | --srcdir | --srcdi | --srcd | --src | --sr)
ac_prev=srcdir ;;
-srcdir=* | --srcdir=* | --srcdi=* | --srcd=* | --src=* | --sr=*)
- srcdir=$ac_optarg ;;
+ srcdir="$ac_optarg" ;;
-sysconfdir | --sysconfdir | --sysconfdi | --sysconfd | --sysconf \
| --syscon | --sysco | --sysc | --sys | --sy)
ac_prev=sysconfdir ;;
-sysconfdir=* | --sysconfdir=* | --sysconfdi=* | --sysconfd=* | --sysconf=* \
| --syscon=* | --sysco=* | --sysc=* | --sys=* | --sy=*)
- sysconfdir=$ac_optarg ;;
+ sysconfdir="$ac_optarg" ;;
-target | --target | --targe | --targ | --tar | --ta | --t)
- ac_prev=target_alias ;;
+ ac_prev=target ;;
-target=* | --target=* | --targe=* | --targ=* | --tar=* | --ta=* | --t=*)
- target_alias=$ac_optarg ;;
+ target="$ac_optarg" ;;
-v | -verbose | --verbose | --verbos | --verbo | --verb)
verbose=yes ;;
- -version | --version | --versio | --versi | --vers | -V)
- ac_init_version=: ;;
+ -version | --version | --versio | --versi | --vers)
+ echo "configure generated by autoconf version 2.13"
+ exit 0 ;;
-with-* | --with-*)
- ac_package=`expr "x$ac_option" : 'x-*with-\([^=]*\)'`
+ ac_package=`echo $ac_option|sed -e 's/-*with-//' -e 's/=.*//'`
# Reject names that are not valid shell variable names.
- expr "x$ac_package" : ".*[^-_$as_cr_alnum]" >/dev/null &&
- { echo "$as_me: error: invalid package name: $ac_package" >&2
- { (exit 1); exit 1; }; }
+ if test -n "`echo $ac_package| sed 's/[-_a-zA-Z0-9]//g'`"; then
+ { echo "configure: error: $ac_package: invalid package name" 1>&2; exit 1; }
+ fi
ac_package=`echo $ac_package| sed 's/-/_/g'`
- case $ac_option in
- *=*) ac_optarg=`echo "$ac_optarg" | sed "s/'/'\\\\\\\\''/g"`;;
+ case "$ac_option" in
+ *=*) ;;
*) ac_optarg=yes ;;
esac
- eval "with_$ac_package='$ac_optarg'" ;;
+ eval "with_${ac_package}='$ac_optarg'" ;;
-without-* | --without-*)
- ac_package=`expr "x$ac_option" : 'x-*without-\(.*\)'`
+ ac_package=`echo $ac_option|sed -e 's/-*without-//'`
# Reject names that are not valid shell variable names.
- expr "x$ac_package" : ".*[^-_$as_cr_alnum]" >/dev/null &&
- { echo "$as_me: error: invalid package name: $ac_package" >&2
- { (exit 1); exit 1; }; }
- ac_package=`echo $ac_package | sed 's/-/_/g'`
- eval "with_$ac_package=no" ;;
+ if test -n "`echo $ac_package| sed 's/[-a-zA-Z0-9_]//g'`"; then
+ { echo "configure: error: $ac_package: invalid package name" 1>&2; exit 1; }
+ fi
+ ac_package=`echo $ac_package| sed 's/-/_/g'`
+ eval "with_${ac_package}=no" ;;
--x)
# Obsolete; use --with-x.
@@ -576,110 +367,99 @@ do
ac_prev=x_includes ;;
-x-includes=* | --x-includes=* | --x-include=* | --x-includ=* | --x-inclu=* \
| --x-incl=* | --x-inc=* | --x-in=* | --x-i=*)
- x_includes=$ac_optarg ;;
+ x_includes="$ac_optarg" ;;
-x-libraries | --x-libraries | --x-librarie | --x-librari \
| --x-librar | --x-libra | --x-libr | --x-lib | --x-li | --x-l)
ac_prev=x_libraries ;;
-x-libraries=* | --x-libraries=* | --x-librarie=* | --x-librari=* \
| --x-librar=* | --x-libra=* | --x-libr=* | --x-lib=* | --x-li=* | --x-l=*)
- x_libraries=$ac_optarg ;;
+ x_libraries="$ac_optarg" ;;
- -*) { echo "$as_me: error: unrecognized option: $ac_option
-Try \`$0 --help' for more information." >&2
- { (exit 1); exit 1; }; }
+ -*) { echo "configure: error: $ac_option: invalid option; use --help to show usage" 1>&2; exit 1; }
;;
- *=*)
- ac_envvar=`expr "x$ac_option" : 'x\([^=]*\)='`
- # Reject names that are not valid shell variable names.
- expr "x$ac_envvar" : ".*[^_$as_cr_alnum]" >/dev/null &&
- { echo "$as_me: error: invalid variable name: $ac_envvar" >&2
- { (exit 1); exit 1; }; }
- ac_optarg=`echo "$ac_optarg" | sed "s/'/'\\\\\\\\''/g"`
- eval "$ac_envvar='$ac_optarg'"
- export $ac_envvar ;;
-
*)
- # FIXME: should be removed in autoconf 3.0.
- echo "$as_me: WARNING: you should use --build, --host, --target" >&2
- expr "x$ac_option" : ".*[^-._$as_cr_alnum]" >/dev/null &&
- echo "$as_me: WARNING: invalid host type: $ac_option" >&2
- : ${build_alias=$ac_option} ${host_alias=$ac_option} ${target_alias=$ac_option}
+ if test -n "`echo $ac_option| sed 's/[-a-z0-9.]//g'`"; then
+ echo "configure: warning: $ac_option: invalid host type" 1>&2
+ fi
+ if test "x$nonopt" != xNONE; then
+ { echo "configure: error: can only configure for one host and one target at a time" 1>&2; exit 1; }
+ fi
+ nonopt="$ac_option"
;;
esac
done
if test -n "$ac_prev"; then
- ac_option=--`echo $ac_prev | sed 's/_/-/g'`
- { echo "$as_me: error: missing argument to $ac_option" >&2
- { (exit 1); exit 1; }; }
+ { echo "configure: error: missing argument to --`echo $ac_prev | sed 's/_/-/g'`" 1>&2; exit 1; }
fi
-# Be sure to have absolute paths.
-for ac_var in exec_prefix prefix
-do
- eval ac_val=$`echo $ac_var`
- case $ac_val in
- [\\/$]* | ?:[\\/]* | NONE | '' ) ;;
- *) { echo "$as_me: error: expected an absolute directory name for --$ac_var: $ac_val" >&2
- { (exit 1); exit 1; }; };;
- esac
-done
+trap 'rm -fr conftest* confdefs* core core.* *.core $ac_clean_files; exit 1' 1 2 15
+
+# File descriptor usage:
+# 0 standard input
+# 1 file creation
+# 2 errors and warnings
+# 3 some systems may open it to /dev/tty
+# 4 used on the Kubota Titan
+# 6 checking for... messages and results
+# 5 compiler messages saved in config.log
+if test "$silent" = yes; then
+ exec 6>/dev/null
+else
+ exec 6>&1
+fi
+exec 5>./config.log
+
+echo "\
+This file contains any messages produced by compilers while
+running configure, to aid debugging if configure makes a mistake.
+" 1>&5
-# Be sure to have absolute paths.
-for ac_var in bindir sbindir libexecdir datadir sysconfdir sharedstatedir \
- localstatedir libdir includedir oldincludedir infodir mandir
+# Strip out --no-create and --no-recursion so they do not pile up.
+# Also quote any args containing shell metacharacters.
+ac_configure_args=
+for ac_arg
do
- eval ac_val=$`echo $ac_var`
- case $ac_val in
- [\\/$]* | ?:[\\/]* ) ;;
- *) { echo "$as_me: error: expected an absolute directory name for --$ac_var: $ac_val" >&2
- { (exit 1); exit 1; }; };;
+ case "$ac_arg" in
+ -no-create | --no-create | --no-creat | --no-crea | --no-cre \
+ | --no-cr | --no-c) ;;
+ -no-recursion | --no-recursion | --no-recursio | --no-recursi \
+ | --no-recurs | --no-recur | --no-recu | --no-rec | --no-re | --no-r) ;;
+ *" "*|*" "*|*[\[\]\~\#\$\^\&\*\(\)\{\}\\\|\;\<\>\?]*)
+ ac_configure_args="$ac_configure_args '$ac_arg'" ;;
+ *) ac_configure_args="$ac_configure_args $ac_arg" ;;
esac
done
-# There might be people who depend on the old broken behavior: `$host'
-# used to hold the argument of --host etc.
-# FIXME: To remove some day.
-build=$build_alias
-host=$host_alias
-target=$target_alias
-
-# FIXME: To remove some day.
-if test "x$host_alias" != x; then
- if test "x$build_alias" = x; then
- cross_compiling=maybe
- echo "$as_me: WARNING: If you wanted to set the --build type, don't use --host.
- If a cross compiler is detected then cross compile mode will be used." >&2
- elif test "x$build_alias" != "x$host_alias"; then
- cross_compiling=yes
- fi
-fi
-
-ac_tool_prefix=
-test -n "$host_alias" && ac_tool_prefix=$host_alias-
+# NLS nuisances.
+# Only set these to C if already set. These must not be set unconditionally
+# because not all systems understand e.g. LANG=C (notably SCO).
+# Fixing LC_MESSAGES prevents Solaris sh from translating var values in `set'!
+# Non-C LC_CTYPE values break the ctype check.
+if test "${LANG+set}" = set; then LANG=C; export LANG; fi
+if test "${LC_ALL+set}" = set; then LC_ALL=C; export LC_ALL; fi
+if test "${LC_MESSAGES+set}" = set; then LC_MESSAGES=C; export LC_MESSAGES; fi
+if test "${LC_CTYPE+set}" = set; then LC_CTYPE=C; export LC_CTYPE; fi
-test "$silent" = yes && exec 6>/dev/null
+# confdefs.h avoids OS command line length limits that DEFS can exceed.
+rm -rf conftest* confdefs.h
+# AIX cpp loses on an empty file, so make sure it contains at least a newline.
+echo > confdefs.h
+# A filename unique to this package, relative to the directory that
+# configure is in, which we can look for to find out if srcdir is correct.
+ac_unique_file=global.ent
# Find the source files, if location was not specified.
if test -z "$srcdir"; then
ac_srcdir_defaulted=yes
# Try the directory containing this script, then its parent.
- ac_confdir=`(dirname "$0") 2>/dev/null ||
-$as_expr X"$0" : 'X\(.*[^/]\)//*[^/][^/]*/*$' \| \
- X"$0" : 'X\(//\)[^/]' \| \
- X"$0" : 'X\(//\)$' \| \
- X"$0" : 'X\(/\)' \| \
- . : '\(.\)' 2>/dev/null ||
-echo X"$0" |
- sed '/^X\(.*[^/]\)\/\/*[^/][^/]*\/*$/{ s//\1/; q; }
- /^X\(\/\/\)[^/].*/{ s//\1/; q; }
- /^X\(\/\/\)$/{ s//\1/; q; }
- /^X\(\/\).*/{ s//\1/; q; }
- s/.*/./; q'`
+ ac_prog=$0
+ ac_confdir=`echo $ac_prog|sed 's%/[^/][^/]*$%%'`
+ test "x$ac_confdir" = "x$ac_prog" && ac_confdir=.
srcdir=$ac_confdir
if test ! -r $srcdir/$ac_unique_file; then
srcdir=..
@@ -689,390 +469,13 @@ else
fi
if test ! -r $srcdir/$ac_unique_file; then
if test "$ac_srcdir_defaulted" = yes; then
- { echo "$as_me: error: cannot find sources ($ac_unique_file) in $ac_confdir or .." >&2
- { (exit 1); exit 1; }; }
+ { echo "configure: error: can not find sources in $ac_confdir or .." 1>&2; exit 1; }
else
- { echo "$as_me: error: cannot find sources ($ac_unique_file) in $srcdir" >&2
- { (exit 1); exit 1; }; }
+ { echo "configure: error: can not find sources in $srcdir" 1>&2; exit 1; }
fi
fi
-(cd $srcdir && test -r ./$ac_unique_file) 2>/dev/null ||
- { echo "$as_me: error: sources are in $srcdir, but \`cd $srcdir' does not work" >&2
- { (exit 1); exit 1; }; }
-srcdir=`echo "$srcdir" | sed 's%\([^\\/]\)[\\/]*$%\1%'`
-ac_env_build_alias_set=${build_alias+set}
-ac_env_build_alias_value=$build_alias
-ac_cv_env_build_alias_set=${build_alias+set}
-ac_cv_env_build_alias_value=$build_alias
-ac_env_host_alias_set=${host_alias+set}
-ac_env_host_alias_value=$host_alias
-ac_cv_env_host_alias_set=${host_alias+set}
-ac_cv_env_host_alias_value=$host_alias
-ac_env_target_alias_set=${target_alias+set}
-ac_env_target_alias_value=$target_alias
-ac_cv_env_target_alias_set=${target_alias+set}
-ac_cv_env_target_alias_value=$target_alias
-
-#
-# Report the --help message.
-#
-if test "$ac_init_help" = "long"; then
- # Omit some internal or obsolete options to make the list less imposing.
- # This message is too long to be a string in the A/UX 3.1 sh.
- cat <<_ACEOF
-\`configure' configures this package to adapt to many kinds of systems.
-
-Usage: $0 [OPTION]... [VAR=VALUE]...
-
-To assign environment variables (e.g., CC, CFLAGS...), specify them as
-VAR=VALUE. See below for descriptions of some of the useful variables.
-
-Defaults for the options are specified in brackets.
-
-Configuration:
- -h, --help display this help and exit
- --help=short display options specific to this package
- --help=recursive display the short help of all the included packages
- -V, --version display version information and exit
- -q, --quiet, --silent do not print \`checking...' messages
- --cache-file=FILE cache test results in FILE [disabled]
- -C, --config-cache alias for \`--cache-file=config.cache'
- -n, --no-create do not create output files
- --srcdir=DIR find the sources in DIR [configure dir or \`..']
-
-_ACEOF
-
- cat <<_ACEOF
-Installation directories:
- --prefix=PREFIX install architecture-independent files in PREFIX
- [$ac_default_prefix]
- --exec-prefix=EPREFIX install architecture-dependent files in EPREFIX
- [PREFIX]
-
-By default, \`make install' will install all the files in
-\`$ac_default_prefix/bin', \`$ac_default_prefix/lib' etc. You can specify
-an installation prefix other than \`$ac_default_prefix' using \`--prefix',
-for instance \`--prefix=\$HOME'.
-
-For better control, use the options below.
-
-Fine tuning of the installation directories:
- --bindir=DIR user executables [EPREFIX/bin]
- --sbindir=DIR system admin executables [EPREFIX/sbin]
- --libexecdir=DIR program executables [EPREFIX/libexec]
- --datadir=DIR read-only architecture-independent data [PREFIX/share]
- --sysconfdir=DIR read-only single-machine data [PREFIX/etc]
- --sharedstatedir=DIR modifiable architecture-independent data [PREFIX/com]
- --localstatedir=DIR modifiable single-machine data [PREFIX/var]
- --libdir=DIR object code libraries [EPREFIX/lib]
- --includedir=DIR C header files [PREFIX/include]
- --oldincludedir=DIR C header files for non-gcc [/usr/include]
- --infodir=DIR info documentation [PREFIX/info]
- --mandir=DIR man documentation [PREFIX/man]
-_ACEOF
-
- cat <<\_ACEOF
-_ACEOF
-fi
-
-if test -n "$ac_init_help"; then
-
- cat <<\_ACEOF
-
-_ACEOF
-fi
-
-if test "$ac_init_help" = "recursive"; then
- # If there are subdirs, report their specific --help.
- ac_popdir=`pwd`
- for ac_dir in : $ac_subdirs_all; do test "x$ac_dir" = x: && continue
- test -d $ac_dir || continue
- ac_builddir=.
-
-if test "$ac_dir" != .; then
- ac_dir_suffix=/`echo "$ac_dir" | sed 's,^\.[\\/],,'`
- # A "../" for each directory in $ac_dir_suffix.
- ac_top_builddir=`echo "$ac_dir_suffix" | sed 's,/[^\\/]*,../,g'`
-else
- ac_dir_suffix= ac_top_builddir=
-fi
-
-case $srcdir in
- .) # No --srcdir option. We are building in place.
- ac_srcdir=.
- if test -z "$ac_top_builddir"; then
- ac_top_srcdir=.
- else
- ac_top_srcdir=`echo $ac_top_builddir | sed 's,/$,,'`
- fi ;;
- [\\/]* | ?:[\\/]* ) # Absolute path.
- ac_srcdir=$srcdir$ac_dir_suffix;
- ac_top_srcdir=$srcdir ;;
- *) # Relative path.
- ac_srcdir=$ac_top_builddir$srcdir$ac_dir_suffix
- ac_top_srcdir=$ac_top_builddir$srcdir ;;
-esac
-# Don't blindly perform a `cd "$ac_dir"/$ac_foo && pwd` since $ac_foo can be
-# absolute.
-ac_abs_builddir=`cd "$ac_dir" && cd $ac_builddir && pwd`
-ac_abs_top_builddir=`cd "$ac_dir" && cd ${ac_top_builddir}. && pwd`
-ac_abs_srcdir=`cd "$ac_dir" && cd $ac_srcdir && pwd`
-ac_abs_top_srcdir=`cd "$ac_dir" && cd $ac_top_srcdir && pwd`
-
- cd $ac_dir
- # Check for guested configure; otherwise get Cygnus style configure.
- if test -f $ac_srcdir/configure.gnu; then
- echo
- $SHELL $ac_srcdir/configure.gnu --help=recursive
- elif test -f $ac_srcdir/configure; then
- echo
- $SHELL $ac_srcdir/configure --help=recursive
- elif test -f $ac_srcdir/configure.ac ||
- test -f $ac_srcdir/configure.in; then
- echo
- $ac_configure --help
- else
- echo "$as_me: WARNING: no configuration information is in $ac_dir" >&2
- fi
- cd $ac_popdir
- done
-fi
-
-test -n "$ac_init_help" && exit 0
-if $ac_init_version; then
- cat <<\_ACEOF
-
-Copyright 1992, 1993, 1994, 1995, 1996, 1998, 1999, 2000, 2001, 2002
-Free Software Foundation, Inc.
-This configure script is free software; the Free Software Foundation
-gives unlimited permission to copy, distribute and modify it.
-_ACEOF
- exit 0
-fi
-exec 5>config.log
-cat >&5 <<_ACEOF
-This file contains any messages produced by compilers while
-running configure, to aid debugging if configure makes a mistake.
-
-It was created by $as_me, which was
-generated by GNU Autoconf 2.57. Invocation command line was
-
- $ $0 $@
-
-_ACEOF
-{
-cat <<_ASUNAME
-## --------- ##
-## Platform. ##
-## --------- ##
+srcdir=`echo "${srcdir}" | sed 's%\([^/]\)/*$%\1%'`
-hostname = `(hostname || uname -n) 2>/dev/null | sed 1q`
-uname -m = `(uname -m) 2>/dev/null || echo unknown`
-uname -r = `(uname -r) 2>/dev/null || echo unknown`
-uname -s = `(uname -s) 2>/dev/null || echo unknown`
-uname -v = `(uname -v) 2>/dev/null || echo unknown`
-
-/usr/bin/uname -p = `(/usr/bin/uname -p) 2>/dev/null || echo unknown`
-/bin/uname -X = `(/bin/uname -X) 2>/dev/null || echo unknown`
-
-/bin/arch = `(/bin/arch) 2>/dev/null || echo unknown`
-/usr/bin/arch -k = `(/usr/bin/arch -k) 2>/dev/null || echo unknown`
-/usr/convex/getsysinfo = `(/usr/convex/getsysinfo) 2>/dev/null || echo unknown`
-hostinfo = `(hostinfo) 2>/dev/null || echo unknown`
-/bin/machine = `(/bin/machine) 2>/dev/null || echo unknown`
-/usr/bin/oslevel = `(/usr/bin/oslevel) 2>/dev/null || echo unknown`
-/bin/universe = `(/bin/universe) 2>/dev/null || echo unknown`
-
-_ASUNAME
-
-as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
-for as_dir in $PATH
-do
- IFS=$as_save_IFS
- test -z "$as_dir" && as_dir=.
- echo "PATH: $as_dir"
-done
-
-} >&5
-
-cat >&5 <<_ACEOF
-
-
-## ----------- ##
-## Core tests. ##
-## ----------- ##
-
-_ACEOF
-
-
-# Keep a trace of the command line.
-# Strip out --no-create and --no-recursion so they do not pile up.
-# Strip out --silent because we don't want to record it for future runs.
-# Also quote any args containing shell meta-characters.
-# Make two passes to allow for proper duplicate-argument suppression.
-ac_configure_args=
-ac_configure_args0=
-ac_configure_args1=
-ac_sep=
-ac_must_keep_next=false
-for ac_pass in 1 2
-do
- for ac_arg
- do
- case $ac_arg in
- -no-create | --no-c* | -n | -no-recursion | --no-r*) continue ;;
- -q | -quiet | --quiet | --quie | --qui | --qu | --q \
- | -silent | --silent | --silen | --sile | --sil)
- continue ;;
- *" "*|*" "*|*[\[\]\~\#\$\^\&\*\(\)\{\}\\\|\;\<\>\?\"\']*)
- ac_arg=`echo "$ac_arg" | sed "s/'/'\\\\\\\\''/g"` ;;
- esac
- case $ac_pass in
- 1) ac_configure_args0="$ac_configure_args0 '$ac_arg'" ;;
- 2)
- ac_configure_args1="$ac_configure_args1 '$ac_arg'"
- if test $ac_must_keep_next = true; then
- ac_must_keep_next=false # Got value, back to normal.
- else
- case $ac_arg in
- *=* | --config-cache | -C | -disable-* | --disable-* \
- | -enable-* | --enable-* | -gas | --g* | -nfp | --nf* \
- | -q | -quiet | --q* | -silent | --sil* | -v | -verb* \
- | -with-* | --with-* | -without-* | --without-* | --x)
- case "$ac_configure_args0 " in
- "$ac_configure_args1"*" '$ac_arg' "* ) continue ;;
- esac
- ;;
- -* ) ac_must_keep_next=true ;;
- esac
- fi
- ac_configure_args="$ac_configure_args$ac_sep'$ac_arg'"
- # Get rid of the leading space.
- ac_sep=" "
- ;;
- esac
- done
-done
-$as_unset ac_configure_args0 || test "${ac_configure_args0+set}" != set || { ac_configure_args0=; export ac_configure_args0; }
-$as_unset ac_configure_args1 || test "${ac_configure_args1+set}" != set || { ac_configure_args1=; export ac_configure_args1; }
-
-# When interrupted or exit'd, cleanup temporary files, and complete
-# config.log. We remove comments because anyway the quotes in there
-# would cause problems or look ugly.
-# WARNING: Be sure not to use single quotes in there, as some shells,
-# such as our DU 5.0 friend, will then `close' the trap.
-trap 'exit_status=$?
- # Save into config.log some information that might help in debugging.
- {
- echo
-
- cat <<\_ASBOX
-## ---------------- ##
-## Cache variables. ##
-## ---------------- ##
-_ASBOX
- echo
- # The following way of writing the cache mishandles newlines in values,
-{
- (set) 2>&1 |
- case `(ac_space='"'"' '"'"'; set | grep ac_space) 2>&1` in
- *ac_space=\ *)
- sed -n \
- "s/'"'"'/'"'"'\\\\'"'"''"'"'/g;
- s/^\\([_$as_cr_alnum]*_cv_[_$as_cr_alnum]*\\)=\\(.*\\)/\\1='"'"'\\2'"'"'/p"
- ;;
- *)
- sed -n \
- "s/^\\([_$as_cr_alnum]*_cv_[_$as_cr_alnum]*\\)=\\(.*\\)/\\1=\\2/p"
- ;;
- esac;
-}
- echo
-
- cat <<\_ASBOX
-## ----------------- ##
-## Output variables. ##
-## ----------------- ##
-_ASBOX
- echo
- for ac_var in $ac_subst_vars
- do
- eval ac_val=$`echo $ac_var`
- echo "$ac_var='"'"'$ac_val'"'"'"
- done | sort
- echo
-
- if test -n "$ac_subst_files"; then
- cat <<\_ASBOX
-## ------------- ##
-## Output files. ##
-## ------------- ##
-_ASBOX
- echo
- for ac_var in $ac_subst_files
- do
- eval ac_val=$`echo $ac_var`
- echo "$ac_var='"'"'$ac_val'"'"'"
- done | sort
- echo
- fi
-
- if test -s confdefs.h; then
- cat <<\_ASBOX
-## ----------- ##
-## confdefs.h. ##
-## ----------- ##
-_ASBOX
- echo
- sed "/^$/d" confdefs.h | sort
- echo
- fi
- test "$ac_signal" != 0 &&
- echo "$as_me: caught signal $ac_signal"
- echo "$as_me: exit $exit_status"
- } >&5
- rm -f core core.* *.core &&
- rm -rf conftest* confdefs* conf$$* $ac_clean_files &&
- exit $exit_status
- ' 0
-for ac_signal in 1 2 13 15; do
- trap 'ac_signal='$ac_signal'; { (exit 1); exit 1; }' $ac_signal
-done
-ac_signal=0
-
-# confdefs.h avoids OS command line length limits that DEFS can exceed.
-rm -rf conftest* confdefs.h
-# AIX cpp loses on an empty file, so make sure it contains at least a newline.
-echo >confdefs.h
-
-# Predefined preprocessor variables.
-
-cat >>confdefs.h <<_ACEOF
-#define PACKAGE_NAME "$PACKAGE_NAME"
-_ACEOF
-
-
-cat >>confdefs.h <<_ACEOF
-#define PACKAGE_TARNAME "$PACKAGE_TARNAME"
-_ACEOF
-
-
-cat >>confdefs.h <<_ACEOF
-#define PACKAGE_VERSION "$PACKAGE_VERSION"
-_ACEOF
-
-
-cat >>confdefs.h <<_ACEOF
-#define PACKAGE_STRING "$PACKAGE_STRING"
-_ACEOF
-
-
-cat >>confdefs.h <<_ACEOF
-#define PACKAGE_BUGREPORT "$PACKAGE_BUGREPORT"
-_ACEOF
-
-
-# Let the site file select an alternate cache file if it wants to.
# Prefer explicitly selected file to automatically selected ones.
if test -z "$CONFIG_SITE"; then
if test "x$prefix" != xNONE; then
@@ -1083,1064 +486,410 @@ if test -z "$CONFIG_SITE"; then
fi
for ac_site_file in $CONFIG_SITE; do
if test -r "$ac_site_file"; then
- { echo "$as_me:$LINENO: loading site script $ac_site_file" >&5
-echo "$as_me: loading site script $ac_site_file" >&6;}
- sed 's/^/| /' "$ac_site_file" >&5
+ echo "loading site script $ac_site_file"
. "$ac_site_file"
fi
done
if test -r "$cache_file"; then
- # Some versions of bash will fail to source /dev/null (special
- # files actually), so we avoid doing that.
- if test -f "$cache_file"; then
- { echo "$as_me:$LINENO: loading cache $cache_file" >&5
-echo "$as_me: loading cache $cache_file" >&6;}
- case $cache_file in
- [\\/]* | ?:[\\/]* ) . $cache_file;;
- *) . ./$cache_file;;
- esac
- fi
+ echo "loading cache $cache_file"
+ . $cache_file
else
- { echo "$as_me:$LINENO: creating cache $cache_file" >&5
-echo "$as_me: creating cache $cache_file" >&6;}
- >$cache_file
-fi
-
-# Check that the precious variables saved in the cache have kept the same
-# value.
-ac_cache_corrupted=false
-for ac_var in `(set) 2>&1 |
- sed -n 's/^ac_env_\([a-zA-Z_0-9]*\)_set=.*/\1/p'`; do
- eval ac_old_set=\$ac_cv_env_${ac_var}_set
- eval ac_new_set=\$ac_env_${ac_var}_set
- eval ac_old_val="\$ac_cv_env_${ac_var}_value"
- eval ac_new_val="\$ac_env_${ac_var}_value"
- case $ac_old_set,$ac_new_set in
- set,)
- { echo "$as_me:$LINENO: error: \`$ac_var' was set to \`$ac_old_val' in the previous run" >&5
-echo "$as_me: error: \`$ac_var' was set to \`$ac_old_val' in the previous run" >&2;}
- ac_cache_corrupted=: ;;
- ,set)
- { echo "$as_me:$LINENO: error: \`$ac_var' was not set in the previous run" >&5
-echo "$as_me: error: \`$ac_var' was not set in the previous run" >&2;}
- ac_cache_corrupted=: ;;
- ,);;
- *)
- if test "x$ac_old_val" != "x$ac_new_val"; then
- { echo "$as_me:$LINENO: error: \`$ac_var' has changed since the previous run:" >&5
-echo "$as_me: error: \`$ac_var' has changed since the previous run:" >&2;}
- { echo "$as_me:$LINENO: former value: $ac_old_val" >&5
-echo "$as_me: former value: $ac_old_val" >&2;}
- { echo "$as_me:$LINENO: current value: $ac_new_val" >&5
-echo "$as_me: current value: $ac_new_val" >&2;}
- ac_cache_corrupted=:
- fi;;
- esac
- # Pass precious variables to config.status.
- if test "$ac_new_set" = set; then
- case $ac_new_val in
- *" "*|*" "*|*[\[\]\~\#\$\^\&\*\(\)\{\}\\\|\;\<\>\?\"\']*)
- ac_arg=$ac_var=`echo "$ac_new_val" | sed "s/'/'\\\\\\\\''/g"` ;;
- *) ac_arg=$ac_var=$ac_new_val ;;
- esac
- case " $ac_configure_args " in
- *" '$ac_arg' "*) ;; # Avoid dups. Use of quotes ensures accuracy.
- *) ac_configure_args="$ac_configure_args '$ac_arg'" ;;
- esac
- fi
-done
-if $ac_cache_corrupted; then
- { echo "$as_me:$LINENO: error: changes in the environment can compromise the build" >&5
-echo "$as_me: error: changes in the environment can compromise the build" >&2;}
- { { echo "$as_me:$LINENO: error: run \`make distclean' and/or \`rm $cache_file' and start over" >&5
-echo "$as_me: error: run \`make distclean' and/or \`rm $cache_file' and start over" >&2;}
- { (exit 1); exit 1; }; }
+ echo "creating cache $cache_file"
+ > $cache_file
fi
ac_ext=c
+# CFLAGS is not in ac_cpp because -g, -O, etc. are not valid cpp options.
ac_cpp='$CPP $CPPFLAGS'
-ac_compile='$CC -c $CFLAGS $CPPFLAGS conftest.$ac_ext >&5'
-ac_link='$CC -o conftest$ac_exeext $CFLAGS $CPPFLAGS $LDFLAGS conftest.$ac_ext $LIBS >&5'
-ac_compiler_gnu=$ac_cv_c_compiler_gnu
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
+ac_compile='${CC-cc} -c $CFLAGS $CPPFLAGS conftest.$ac_ext 1>&5'
+ac_link='${CC-cc} -o conftest${ac_exeext} $CFLAGS $CPPFLAGS $LDFLAGS conftest.$ac_ext $LIBS 1>&5'
+cross_compiling=$ac_cv_prog_cc_cross
+
+ac_exeext=
+ac_objext=o
+if (echo "testing\c"; echo 1,2,3) | grep c >/dev/null; then
+ # Stardent Vistra SVR4 grep lacks -e, says ghazi@caip.rutgers.edu.
+ if (echo -n testing; echo 1,2,3) | sed s/-n/xn/ | grep xn >/dev/null; then
+ ac_n= ac_c='
+' ac_t=' '
+ else
+ ac_n=-n ac_c= ac_t=
+ fi
+else
+ ac_n= ac_c='\c' ac_t=
+fi
# Extract the first word of "xsltproc", so it can be a program name with args.
set dummy xsltproc; ac_word=$2
-echo "$as_me:$LINENO: checking for $ac_word" >&5
-echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6
-if test "${ac_cv_path_XSLTPROC+set}" = set; then
- echo $ECHO_N "(cached) $ECHO_C" >&6
+echo $ac_n "checking for $ac_word""... $ac_c" 1>&6
+echo "configure:529: checking for $ac_word" >&5
+if eval "test \"`echo '$''{'ac_cv_path_XSLTPROC'+set}'`\" = set"; then
+ echo $ac_n "(cached) $ac_c" 1>&6
else
- case $XSLTPROC in
- [\\/]* | ?:[\\/]*)
+ case "$XSLTPROC" in
+ /*)
ac_cv_path_XSLTPROC="$XSLTPROC" # Let the user override the test with a path.
;;
+ ?:/*)
+ ac_cv_path_XSLTPROC="$XSLTPROC" # Let the user override the test with a dos path.
+ ;;
*)
- as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
-for as_dir in $PATH
-do
- IFS=$as_save_IFS
- test -z "$as_dir" && as_dir=.
- for ac_exec_ext in '' $ac_executable_extensions; do
- if $as_executable_p "$as_dir/$ac_word$ac_exec_ext"; then
- ac_cv_path_XSLTPROC="$as_dir/$ac_word$ac_exec_ext"
- echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5
- break 2
- fi
-done
-done
-
+ IFS="${IFS= }"; ac_save_ifs="$IFS"; IFS=":"
+ ac_dummy="$PATH"
+ for ac_dir in $ac_dummy; do
+ test -z "$ac_dir" && ac_dir=.
+ if test -f $ac_dir/$ac_word; then
+ ac_cv_path_XSLTPROC="$ac_dir/$ac_word"
+ break
+ fi
+ done
+ IFS="$ac_save_ifs"
;;
esac
fi
-XSLTPROC=$ac_cv_path_XSLTPROC
-
+XSLTPROC="$ac_cv_path_XSLTPROC"
if test -n "$XSLTPROC"; then
- echo "$as_me:$LINENO: result: $XSLTPROC" >&5
-echo "${ECHO_T}$XSLTPROC" >&6
+ echo "$ac_t""$XSLTPROC" 1>&6
else
- echo "$as_me:$LINENO: result: no" >&5
-echo "${ECHO_T}no" >&6
+ echo "$ac_t""no" 1>&6
fi
if test "x$XSLTPROC" = x; then
- { { echo "$as_me:$LINENO: error: \"xsltproc is required\"" >&5
-echo "$as_me: error: \"xsltproc is required\"" >&2;}
- { (exit 1); exit 1; }; }
+ { echo "configure: error: "xsltproc is required"" 1>&2; exit 1; }
fi
# Extract the first word of "pdflatex", so it can be a program name with args.
set dummy pdflatex; ac_word=$2
-echo "$as_me:$LINENO: checking for $ac_word" >&5
-echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6
-if test "${ac_cv_path_PDFLATEX+set}" = set; then
- echo $ECHO_N "(cached) $ECHO_C" >&6
+echo $ac_n "checking for $ac_word""... $ac_c" 1>&6
+echo "configure:567: checking for $ac_word" >&5
+if eval "test \"`echo '$''{'ac_cv_path_PDFLATEX'+set}'`\" = set"; then
+ echo $ac_n "(cached) $ac_c" 1>&6
else
- case $PDFLATEX in
- [\\/]* | ?:[\\/]*)
+ case "$PDFLATEX" in
+ /*)
ac_cv_path_PDFLATEX="$PDFLATEX" # Let the user override the test with a path.
;;
+ ?:/*)
+ ac_cv_path_PDFLATEX="$PDFLATEX" # Let the user override the test with a dos path.
+ ;;
*)
- as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
-for as_dir in $PATH
-do
- IFS=$as_save_IFS
- test -z "$as_dir" && as_dir=.
- for ac_exec_ext in '' $ac_executable_extensions; do
- if $as_executable_p "$as_dir/$ac_word$ac_exec_ext"; then
- ac_cv_path_PDFLATEX="$as_dir/$ac_word$ac_exec_ext"
- echo "$as_me:$LINENO: found $as_dir/$ac_word$ac_exec_ext" >&5
- break 2
- fi
-done
-done
-
+ IFS="${IFS= }"; ac_save_ifs="$IFS"; IFS=":"
+ ac_dummy="$PATH"
+ for ac_dir in $ac_dummy; do
+ test -z "$ac_dir" && ac_dir=.
+ if test -f $ac_dir/$ac_word; then
+ ac_cv_path_PDFLATEX="$ac_dir/$ac_word"
+ break
+ fi
+ done
+ IFS="$ac_save_ifs"
;;
esac
fi
-PDFLATEX=$ac_cv_path_PDFLATEX
-
+PDFLATEX="$ac_cv_path_PDFLATEX"
if test -n "$PDFLATEX"; then
- echo "$as_me:$LINENO: result: $PDFLATEX" >&5
-echo "${ECHO_T}$PDFLATEX" >&6
+ echo "$ac_t""$PDFLATEX" 1>&6
else
- echo "$as_me:$LINENO: result: no" >&5
-echo "${ECHO_T}no" >&6
+ echo "$ac_t""no" 1>&6
fi
if test "x$PDFLATEX" = x; then
- { { echo "$as_me:$LINENO: error: \"pdflatex is required\"" >&5
-echo "$as_me: error: \"pdflatex is required\"" >&2;}
- { (exit 1); exit 1; }; }
+ { echo "configure: error: "pdflatex is required"" 1>&2; exit 1; }
fi
+# Extract the first word of "xmlto", so it can be a program name with args.
+set dummy xmlto; ac_word=$2
+echo $ac_n "checking for $ac_word""... $ac_c" 1>&6
+echo "configure:606: checking for $ac_word" >&5
+if eval "test \"`echo '$''{'ac_cv_path_XMLTO'+set}'`\" = set"; then
+ echo $ac_n "(cached) $ac_c" 1>&6
+else
+ case "$XMLTO" in
+ /*)
+ ac_cv_path_XMLTO="$XMLTO" # Let the user override the test with a path.
+ ;;
+ ?:/*)
+ ac_cv_path_XMLTO="$XMLTO" # Let the user override the test with a dos path.
+ ;;
+ *)
+ IFS="${IFS= }"; ac_save_ifs="$IFS"; IFS=":"
+ ac_dummy="$PATH"
+ for ac_dir in $ac_dummy; do
+ test -z "$ac_dir" && ac_dir=.
+ if test -f $ac_dir/$ac_word; then
+ ac_cv_path_XMLTO="$ac_dir/$ac_word"
+ break
+ fi
+ done
+ IFS="$ac_save_ifs"
+ ;;
+esac
+fi
+XMLTO="$ac_cv_path_XMLTO"
+if test -n "$XMLTO"; then
+ echo "$ac_t""$XMLTO" 1>&6
+else
+ echo "$ac_t""no" 1>&6
+fi
+
+
DOC_BUILD_DATE=`date '+%d-%m-%Y'`
- ac_config_files="$ac_config_files Makefile"
-cat >confcache <<\_ACEOF
+trap '' 1 2 15
+cat > confcache <<\EOF
# This file is a shell script that caches the results of configure
# tests run on this system so they can be shared between configure
-# scripts and configure runs, see configure's option --config-cache.
-# It is not useful on other systems. If it contains results you don't
-# want to keep, you may remove or edit it.
+# scripts and configure runs. It is not useful on other systems.
+# If it contains results you don't want to keep, you may remove or edit it.
#
-# config.status only pays attention to the cache file if you give it
-# the --recheck option to rerun configure.
+# By default, configure uses ./config.cache as the cache file,
+# creating it if it does not exist already. You can give configure
+# the --cache-file=FILE option to use a different cache file; that is
+# what configure does when it calls configure scripts in
+# subdirectories, so they share the cache.
+# Giving --cache-file=/dev/null disables caching, for debugging configure.
+# config.status only pays attention to the cache file if you give it the
+# --recheck option to rerun configure.
#
-# `ac_cv_env_foo' variables (set or unset) will be overridden when
-# loading this file, other *unset* `ac_cv_foo' will be assigned the
-# following values.
-
-_ACEOF
-
+EOF
# The following way of writing the cache mishandles newlines in values,
# but we know of no workaround that is simple, portable, and efficient.
# So, don't put newlines in cache variables' values.
# Ultrix sh set writes to stderr and can't be redirected directly,
# and sets the high bit in the cache file unless we assign to the vars.
-{
- (set) 2>&1 |
- case `(ac_space=' '; set | grep ac_space) 2>&1` in
- *ac_space=\ *)
- # `set' does not quote correctly, so add quotes (double-quote
- # substitution turns \\\\ into \\, and sed turns \\ into \).
- sed -n \
- "s/'/'\\\\''/g;
- s/^\\([_$as_cr_alnum]*_cv_[_$as_cr_alnum]*\\)=\\(.*\\)/\\1='\\2'/p"
- ;;
- *)
- # `set' quotes correctly as required by POSIX, so do not add quotes.
- sed -n \
- "s/^\\([_$as_cr_alnum]*_cv_[_$as_cr_alnum]*\\)=\\(.*\\)/\\1=\\2/p"
- ;;
- esac;
-} |
- sed '
- t clear
- : clear
- s/^\([^=]*\)=\(.*[{}].*\)$/test "${\1+set}" = set || &/
- t end
- /^ac_cv_env/!s/^\([^=]*\)=\(.*\)$/\1=${\1=\2}/
- : end' >>confcache
-if diff $cache_file confcache >/dev/null 2>&1; then :; else
+(set) 2>&1 |
+ case `(ac_space=' '; set | grep ac_space) 2>&1` in
+ *ac_space=\ *)
+ # `set' does not quote correctly, so add quotes (double-quote substitution
+ # turns \\\\ into \\, and sed turns \\ into \).
+ sed -n \
+ -e "s/'/'\\\\''/g" \
+ -e "s/^\\([a-zA-Z0-9_]*_cv_[a-zA-Z0-9_]*\\)=\\(.*\\)/\\1=\${\\1='\\2'}/p"
+ ;;
+ *)
+ # `set' quotes correctly as required by POSIX, so do not add quotes.
+ sed -n -e 's/^\([a-zA-Z0-9_]*_cv_[a-zA-Z0-9_]*\)=\(.*\)/\1=${\1=\2}/p'
+ ;;
+ esac >> confcache
+if cmp -s $cache_file confcache; then
+ :
+else
if test -w $cache_file; then
- test "x$cache_file" != "x/dev/null" && echo "updating cache $cache_file"
- cat confcache >$cache_file
+ echo "updating cache $cache_file"
+ cat confcache > $cache_file
else
echo "not updating unwritable cache $cache_file"
fi
fi
rm -f confcache
+trap 'rm -fr conftest* confdefs* core core.* *.core $ac_clean_files; exit 1' 1 2 15
+
test "x$prefix" = xNONE && prefix=$ac_default_prefix
# Let make expand exec_prefix.
test "x$exec_prefix" = xNONE && exec_prefix='${prefix}'
-# VPATH may cause trouble with some makes, so we remove $(srcdir),
-# ${srcdir} and @srcdir@ from VPATH if srcdir is ".", strip leading and
-# trailing colons and then remove the whole line if VPATH becomes empty
-# (actually we leave an empty line to preserve line numbers).
+# Any assignment to VPATH causes Sun make to only execute
+# the first set of double-colon rules, so remove it if not needed.
+# If there is a colon in the path, we need to keep it.
if test "x$srcdir" = x.; then
- ac_vpsub='/^[ ]*VPATH[ ]*=/{
-s/:*\$(srcdir):*/:/;
-s/:*\${srcdir}:*/:/;
-s/:*@srcdir@:*/:/;
-s/^\([^=]*=[ ]*\):*/\1/;
-s/:*$//;
-s/^[^=]*=[ ]*$//;
-}'
+ ac_vpsub='/^[ ]*VPATH[ ]*=[^:]*$/d'
fi
+trap 'rm -f $CONFIG_STATUS conftest*; exit 1' 1 2 15
+
# Transform confdefs.h into DEFS.
# Protect against shell expansion while executing Makefile rules.
# Protect against Makefile macro expansion.
-#
-# If the first sed substitution is executed (which looks for macros that
-# take arguments), then we branch to the quote section. Otherwise,
-# look for a macro that doesn't take arguments.
-cat >confdef2opt.sed <<\_ACEOF
-t clear
-: clear
-s,^[ ]*#[ ]*define[ ][ ]*\([^ (][^ (]*([^)]*)\)[ ]*\(.*\),-D\1=\2,g
-t quote
-s,^[ ]*#[ ]*define[ ][ ]*\([^ ][^ ]*\)[ ]*\(.*\),-D\1=\2,g
-t quote
-d
-: quote
-s,[ `~#$^&*(){}\\|;'"<>?],\\&,g
-s,\[,\\&,g
-s,\],\\&,g
-s,\$,$$,g
-p
-_ACEOF
-# We use echo to avoid assuming a particular line-breaking character.
-# The extra dot is to prevent the shell from consuming trailing
-# line-breaks from the sub-command output. A line-break within
-# single-quotes doesn't work because, if this script is created in a
-# platform that uses two characters for line-breaks (e.g., DOS), tr
-# would break.
-ac_LF_and_DOT=`echo; echo .`
-DEFS=`sed -n -f confdef2opt.sed confdefs.h | tr "$ac_LF_and_DOT" ' .'`
-rm -f confdef2opt.sed
-
-
-ac_libobjs=
-ac_ltlibobjs=
-for ac_i in : $LIBOBJS; do test "x$ac_i" = x: && continue
- # 1. Remove the extension, and $U if already installed.
- ac_i=`echo "$ac_i" |
- sed 's/\$U\././;s/\.o$//;s/\.obj$//'`
- # 2. Add them.
- ac_libobjs="$ac_libobjs $ac_i\$U.$ac_objext"
- ac_ltlibobjs="$ac_ltlibobjs $ac_i"'$U.lo'
-done
-LIBOBJS=$ac_libobjs
-
-LTLIBOBJS=$ac_ltlibobjs
-
-
-
+cat > conftest.defs <<\EOF
+s%#define \([A-Za-z_][A-Za-z0-9_]*\) *\(.*\)%-D\1=\2%g
+s%[ `~#$^&*(){}\\|;'"<>?]%\\&%g
+s%\[%\\&%g
+s%\]%\\&%g
+s%\$%$$%g
+EOF
+DEFS=`sed -f conftest.defs confdefs.h | tr '\012' ' '`
+rm -f conftest.defs
+
+
+# Without the "./", some shells look in PATH for config.status.
: ${CONFIG_STATUS=./config.status}
-ac_clean_files_save=$ac_clean_files
-ac_clean_files="$ac_clean_files $CONFIG_STATUS"
-{ echo "$as_me:$LINENO: creating $CONFIG_STATUS" >&5
-echo "$as_me: creating $CONFIG_STATUS" >&6;}
-cat >$CONFIG_STATUS <<_ACEOF
-#! $SHELL
-# Generated by $as_me.
+
+echo creating $CONFIG_STATUS
+rm -f $CONFIG_STATUS
+cat > $CONFIG_STATUS <<EOF
+#! /bin/sh
+# Generated automatically by configure.
# Run this file to recreate the current configuration.
+# This directory was configured as follows,
+# on host `(hostname || uname -n) 2>/dev/null | sed 1q`:
+#
+# $0 $ac_configure_args
+#
# Compiler output produced by configure, useful for debugging
-# configure, is in config.log if it exists.
-
-debug=false
-ac_cs_recheck=false
-ac_cs_silent=false
-SHELL=\${CONFIG_SHELL-$SHELL}
-_ACEOF
-
-cat >>$CONFIG_STATUS <<\_ACEOF
-## --------------------- ##
-## M4sh Initialization. ##
-## --------------------- ##
-
-# Be Bourne compatible
-if test -n "${ZSH_VERSION+set}" && (emulate sh) >/dev/null 2>&1; then
- emulate sh
- NULLCMD=:
- # Zsh 3.x and 4.x performs word splitting on ${1+"$@"}, which
- # is contrary to our usage. Disable this feature.
- alias -g '${1+"$@"}'='"$@"'
-elif test -n "${BASH_VERSION+set}" && (set -o posix) >/dev/null 2>&1; then
- set -o posix
-fi
-
-# Support unset when possible.
-if (FOO=FOO; unset FOO) >/dev/null 2>&1; then
- as_unset=unset
-else
- as_unset=false
-fi
-
-
-# Work around bugs in pre-3.0 UWIN ksh.
-$as_unset ENV MAIL MAILPATH
-PS1='$ '
-PS2='> '
-PS4='+ '
+# configure, is in ./config.log if it exists.
-# NLS nuisances.
-for as_var in \
- LANG LANGUAGE LC_ADDRESS LC_ALL LC_COLLATE LC_CTYPE LC_IDENTIFICATION \
- LC_MEASUREMENT LC_MESSAGES LC_MONETARY LC_NAME LC_NUMERIC LC_PAPER \
- LC_TELEPHONE LC_TIME
+ac_cs_usage="Usage: $CONFIG_STATUS [--recheck] [--version] [--help]"
+for ac_option
do
- if (set +x; test -n "`(eval $as_var=C; export $as_var) 2>&1`"); then
- eval $as_var=C; export $as_var
- else
- $as_unset $as_var
- fi
+ case "\$ac_option" in
+ -recheck | --recheck | --rechec | --reche | --rech | --rec | --re | --r)
+ echo "running \${CONFIG_SHELL-/bin/sh} $0 $ac_configure_args --no-create --no-recursion"
+ exec \${CONFIG_SHELL-/bin/sh} $0 $ac_configure_args --no-create --no-recursion ;;
+ -version | --version | --versio | --versi | --vers | --ver | --ve | --v)
+ echo "$CONFIG_STATUS generated by autoconf version 2.13"
+ exit 0 ;;
+ -help | --help | --hel | --he | --h)
+ echo "\$ac_cs_usage"; exit 0 ;;
+ *) echo "\$ac_cs_usage"; exit 1 ;;
+ esac
done
-# Required to use basename.
-if expr a : '\(a\)' >/dev/null 2>&1; then
- as_expr=expr
-else
- as_expr=false
-fi
+ac_given_srcdir=$srcdir
-if (basename /) >/dev/null 2>&1 && test "X`basename / 2>&1`" = "X/"; then
- as_basename=basename
-else
- as_basename=false
-fi
+trap 'rm -fr `echo "Makefile " | sed "s/:[^ ]*//g"` conftest*; exit 1' 1 2 15
+EOF
+cat >> $CONFIG_STATUS <<EOF
+# Protect against being on the right side of a sed subst in config.status.
+sed 's/%@/@@/; s/@%/@@/; s/%g\$/@g/; /@g\$/s/[\\\\&%]/\\\\&/g;
+ s/@@/%@/; s/@@/@%/; s/@g\$/%g/' > conftest.subs <<\\CEOF
+$ac_vpsub
+$extrasub
+s%@SHELL@%$SHELL%g
+s%@CFLAGS@%$CFLAGS%g
+s%@CPPFLAGS@%$CPPFLAGS%g
+s%@CXXFLAGS@%$CXXFLAGS%g
+s%@FFLAGS@%$FFLAGS%g
+s%@DEFS@%$DEFS%g
+s%@LDFLAGS@%$LDFLAGS%g
+s%@LIBS@%$LIBS%g
+s%@exec_prefix@%$exec_prefix%g
+s%@prefix@%$prefix%g
+s%@program_transform_name@%$program_transform_name%g
+s%@bindir@%$bindir%g
+s%@sbindir@%$sbindir%g
+s%@libexecdir@%$libexecdir%g
+s%@datadir@%$datadir%g
+s%@sysconfdir@%$sysconfdir%g
+s%@sharedstatedir@%$sharedstatedir%g
+s%@localstatedir@%$localstatedir%g
+s%@libdir@%$libdir%g
+s%@includedir@%$includedir%g
+s%@oldincludedir@%$oldincludedir%g
+s%@infodir@%$infodir%g
+s%@mandir@%$mandir%g
+s%@XSLTPROC@%$XSLTPROC%g
+s%@PDFLATEX@%$PDFLATEX%g
+s%@XMLTO@%$XMLTO%g
+s%@DOC_BUILD_DATE@%$DOC_BUILD_DATE%g
-# Name of the executable.
-as_me=`$as_basename "$0" ||
-$as_expr X/"$0" : '.*/\([^/][^/]*\)/*$' \| \
- X"$0" : 'X\(//\)$' \| \
- X"$0" : 'X\(/\)$' \| \
- . : '\(.\)' 2>/dev/null ||
-echo X/"$0" |
- sed '/^.*\/\([^/][^/]*\)\/*$/{ s//\1/; q; }
- /^X\/\(\/\/\)$/{ s//\1/; q; }
- /^X\/\(\/\).*/{ s//\1/; q; }
- s/.*/./; q'`
-
-
-# PATH needs CR, and LINENO needs CR and PATH.
-# Avoid depending upon Character Ranges.
-as_cr_letters='abcdefghijklmnopqrstuvwxyz'
-as_cr_LETTERS='ABCDEFGHIJKLMNOPQRSTUVWXYZ'
-as_cr_Letters=$as_cr_letters$as_cr_LETTERS
-as_cr_digits='0123456789'
-as_cr_alnum=$as_cr_Letters$as_cr_digits
-
-# The user is always right.
-if test "${PATH_SEPARATOR+set}" != set; then
- echo "#! /bin/sh" >conf$$.sh
- echo "exit 0" >>conf$$.sh
- chmod +x conf$$.sh
- if (PATH="/nonexistent;."; conf$$.sh) >/dev/null 2>&1; then
- PATH_SEPARATOR=';'
+CEOF
+EOF
+
+cat >> $CONFIG_STATUS <<\EOF
+
+# Split the substitutions into bite-sized pieces for seds with
+# small command number limits, like on Digital OSF/1 and HP-UX.
+ac_max_sed_cmds=90 # Maximum number of lines to put in a sed script.
+ac_file=1 # Number of current file.
+ac_beg=1 # First line for current file.
+ac_end=$ac_max_sed_cmds # Line after last line for current file.
+ac_more_lines=:
+ac_sed_cmds=""
+while $ac_more_lines; do
+ if test $ac_beg -gt 1; then
+ sed "1,${ac_beg}d; ${ac_end}q" conftest.subs > conftest.s$ac_file
else
- PATH_SEPARATOR=:
- fi
- rm -f conf$$.sh
-fi
-
-
- as_lineno_1=$LINENO
- as_lineno_2=$LINENO
- as_lineno_3=`(expr $as_lineno_1 + 1) 2>/dev/null`
- test "x$as_lineno_1" != "x$as_lineno_2" &&
- test "x$as_lineno_3" = "x$as_lineno_2" || {
- # Find who we are. Look in the path if we contain no path at all
- # relative or not.
- case $0 in
- *[\\/]* ) as_myself=$0 ;;
- *) as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
-for as_dir in $PATH
-do
- IFS=$as_save_IFS
- test -z "$as_dir" && as_dir=.
- test -r "$as_dir/$0" && as_myself=$as_dir/$0 && break
-done
-
- ;;
- esac
- # We did not find ourselves, most probably we were run as `sh COMMAND'
- # in which case we are not to be found in the path.
- if test "x$as_myself" = x; then
- as_myself=$0
+ sed "${ac_end}q" conftest.subs > conftest.s$ac_file
fi
- if test ! -f "$as_myself"; then
- { { echo "$as_me:$LINENO: error: cannot find myself; rerun with an absolute path" >&5
-echo "$as_me: error: cannot find myself; rerun with an absolute path" >&2;}
- { (exit 1); exit 1; }; }
- fi
- case $CONFIG_SHELL in
- '')
- as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
-for as_dir in /bin$PATH_SEPARATOR/usr/bin$PATH_SEPARATOR$PATH
-do
- IFS=$as_save_IFS
- test -z "$as_dir" && as_dir=.
- for as_base in sh bash ksh sh5; do
- case $as_dir in
- /*)
- if ("$as_dir/$as_base" -c '
- as_lineno_1=$LINENO
- as_lineno_2=$LINENO
- as_lineno_3=`(expr $as_lineno_1 + 1) 2>/dev/null`
- test "x$as_lineno_1" != "x$as_lineno_2" &&
- test "x$as_lineno_3" = "x$as_lineno_2" ') 2>/dev/null; then
- $as_unset BASH_ENV || test "${BASH_ENV+set}" != set || { BASH_ENV=; export BASH_ENV; }
- $as_unset ENV || test "${ENV+set}" != set || { ENV=; export ENV; }
- CONFIG_SHELL=$as_dir/$as_base
- export CONFIG_SHELL
- exec "$CONFIG_SHELL" "$0" ${1+"$@"}
- fi;;
- esac
- done
-done
-;;
- esac
-
- # Create $as_me.lineno as a copy of $as_myself, but with $LINENO
- # uniformly replaced by the line number. The first 'sed' inserts a
- # line-number line before each line; the second 'sed' does the real
- # work. The second script uses 'N' to pair each line-number line
- # with the numbered line, and appends trailing '-' during
- # substitution so that $LINENO is not a special case at line end.
- # (Raja R Harinath suggested sed '=', and Paul Eggert wrote the
- # second 'sed' script. Blame Lee E. McMahon for sed's syntax. :-)
- sed '=' <$as_myself |
- sed '
- N
- s,$,-,
- : loop
- s,^\(['$as_cr_digits']*\)\(.*\)[$]LINENO\([^'$as_cr_alnum'_]\),\1\2\1\3,
- t loop
- s,-$,,
- s,^['$as_cr_digits']*\n,,
- ' >$as_me.lineno &&
- chmod +x $as_me.lineno ||
- { { echo "$as_me:$LINENO: error: cannot create $as_me.lineno; rerun with a POSIX shell" >&5
-echo "$as_me: error: cannot create $as_me.lineno; rerun with a POSIX shell" >&2;}
- { (exit 1); exit 1; }; }
-
- # Don't try to exec as it changes $[0], causing all sort of problems
- # (the dirname of $[0] is not the place where we might find the
- # original and so on. Autoconf is especially sensible to this).
- . ./$as_me.lineno
- # Exit status is that of the last command.
- exit
-}
-
-
-case `echo "testing\c"; echo 1,2,3`,`echo -n testing; echo 1,2,3` in
- *c*,-n*) ECHO_N= ECHO_C='
-' ECHO_T=' ' ;;
- *c*,* ) ECHO_N=-n ECHO_C= ECHO_T= ;;
- *) ECHO_N= ECHO_C='\c' ECHO_T= ;;
-esac
-
-if expr a : '\(a\)' >/dev/null 2>&1; then
- as_expr=expr
-else
- as_expr=false
-fi
-
-rm -f conf$$ conf$$.exe conf$$.file
-echo >conf$$.file
-if ln -s conf$$.file conf$$ 2>/dev/null; then
- # We could just check for DJGPP; but this test a) works b) is more generic
- # and c) will remain valid once DJGPP supports symlinks (DJGPP 2.04).
- if test -f conf$$.exe; then
- # Don't use ln at all; we don't have any links
- as_ln_s='cp -p'
+ if test ! -s conftest.s$ac_file; then
+ ac_more_lines=false
+ rm -f conftest.s$ac_file
else
- as_ln_s='ln -s'
+ if test -z "$ac_sed_cmds"; then
+ ac_sed_cmds="sed -f conftest.s$ac_file"
+ else
+ ac_sed_cmds="$ac_sed_cmds | sed -f conftest.s$ac_file"
+ fi
+ ac_file=`expr $ac_file + 1`
+ ac_beg=$ac_end
+ ac_end=`expr $ac_end + $ac_max_sed_cmds`
fi
-elif ln conf$$.file conf$$ 2>/dev/null; then
- as_ln_s=ln
-else
- as_ln_s='cp -p'
-fi
-rm -f conf$$ conf$$.exe conf$$.file
-
-if mkdir -p . 2>/dev/null; then
- as_mkdir_p=:
-else
- as_mkdir_p=false
-fi
-
-as_executable_p="test -f"
-
-# Sed expression to map a string onto a valid CPP name.
-as_tr_cpp="sed y%*$as_cr_letters%P$as_cr_LETTERS%;s%[^_$as_cr_alnum]%_%g"
-
-# Sed expression to map a string onto a valid variable name.
-as_tr_sh="sed y%*+%pp%;s%[^_$as_cr_alnum]%_%g"
-
-
-# IFS
-# We need space, tab and new line, in precisely that order.
-as_nl='
-'
-IFS=" $as_nl"
-
-# CDPATH.
-$as_unset CDPATH
-
-exec 6>&1
-
-# Open the log real soon, to keep \$[0] and so on meaningful, and to
-# report actual input values of CONFIG_FILES etc. instead of their
-# values after options handling. Logging --version etc. is OK.
-exec 5>>config.log
-{
- echo
- sed 'h;s/./-/g;s/^.../## /;s/...$/ ##/;p;x;p;x' <<_ASBOX
-## Running $as_me. ##
-_ASBOX
-} >&5
-cat >&5 <<_CSEOF
-
-This file was extended by $as_me, which was
-generated by GNU Autoconf 2.57. Invocation command line was
-
- CONFIG_FILES = $CONFIG_FILES
- CONFIG_HEADERS = $CONFIG_HEADERS
- CONFIG_LINKS = $CONFIG_LINKS
- CONFIG_COMMANDS = $CONFIG_COMMANDS
- $ $0 $@
-
-_CSEOF
-echo "on `(hostname || uname -n) 2>/dev/null | sed 1q`" >&5
-echo >&5
-_ACEOF
-
-# Files that config.status was made for.
-if test -n "$ac_config_files"; then
- echo "config_files=\"$ac_config_files\"" >>$CONFIG_STATUS
-fi
-
-if test -n "$ac_config_headers"; then
- echo "config_headers=\"$ac_config_headers\"" >>$CONFIG_STATUS
-fi
-
-if test -n "$ac_config_links"; then
- echo "config_links=\"$ac_config_links\"" >>$CONFIG_STATUS
-fi
-
-if test -n "$ac_config_commands"; then
- echo "config_commands=\"$ac_config_commands\"" >>$CONFIG_STATUS
-fi
-
-cat >>$CONFIG_STATUS <<\_ACEOF
-
-ac_cs_usage="\
-\`$as_me' instantiates files from templates according to the
-current configuration.
-
-Usage: $0 [OPTIONS] [FILE]...
-
- -h, --help print this help, then exit
- -V, --version print version number, then exit
- -q, --quiet do not print progress messages
- -d, --debug don't remove temporary files
- --recheck update $as_me by reconfiguring in the same conditions
- --file=FILE[:TEMPLATE]
- instantiate the configuration file FILE
-
-Configuration files:
-$config_files
-
-Report bugs to <bug-autoconf@gnu.org>."
-_ACEOF
-
-cat >>$CONFIG_STATUS <<_ACEOF
-ac_cs_version="\\
-config.status
-configured by $0, generated by GNU Autoconf 2.57,
- with options \\"`echo "$ac_configure_args" | sed 's/[\\""\`\$]/\\\\&/g'`\\"
-
-Copyright 1992, 1993, 1994, 1995, 1996, 1998, 1999, 2000, 2001
-Free Software Foundation, Inc.
-This config.status script is free software; the Free Software Foundation
-gives unlimited permission to copy, distribute and modify it."
-srcdir=$srcdir
-_ACEOF
-
-cat >>$CONFIG_STATUS <<\_ACEOF
-# If no file are specified by the user, then we need to provide default
-# value. By we need to know if files were specified by the user.
-ac_need_defaults=:
-while test $# != 0
-do
- case $1 in
- --*=*)
- ac_option=`expr "x$1" : 'x\([^=]*\)='`
- ac_optarg=`expr "x$1" : 'x[^=]*=\(.*\)'`
- ac_shift=:
- ;;
- -*)
- ac_option=$1
- ac_optarg=$2
- ac_shift=shift
- ;;
- *) # This is not an option, so the user has probably given explicit
- # arguments.
- ac_option=$1
- ac_need_defaults=false;;
- esac
-
- case $ac_option in
- # Handling of the options.
-_ACEOF
-cat >>$CONFIG_STATUS <<\_ACEOF
- -recheck | --recheck | --rechec | --reche | --rech | --rec | --re | --r)
- ac_cs_recheck=: ;;
- --version | --vers* | -V )
- echo "$ac_cs_version"; exit 0 ;;
- --he | --h)
- # Conflict between --help and --header
- { { echo "$as_me:$LINENO: error: ambiguous option: $1
-Try \`$0 --help' for more information." >&5
-echo "$as_me: error: ambiguous option: $1
-Try \`$0 --help' for more information." >&2;}
- { (exit 1); exit 1; }; };;
- --help | --hel | -h )
- echo "$ac_cs_usage"; exit 0 ;;
- --debug | --d* | -d )
- debug=: ;;
- --file | --fil | --fi | --f )
- $ac_shift
- CONFIG_FILES="$CONFIG_FILES $ac_optarg"
- ac_need_defaults=false;;
- --header | --heade | --head | --hea )
- $ac_shift
- CONFIG_HEADERS="$CONFIG_HEADERS $ac_optarg"
- ac_need_defaults=false;;
- -q | -quiet | --quiet | --quie | --qui | --qu | --q \
- | -silent | --silent | --silen | --sile | --sil | --si | --s)
- ac_cs_silent=: ;;
-
- # This is an error.
- -*) { { echo "$as_me:$LINENO: error: unrecognized option: $1
-Try \`$0 --help' for more information." >&5
-echo "$as_me: error: unrecognized option: $1
-Try \`$0 --help' for more information." >&2;}
- { (exit 1); exit 1; }; } ;;
-
- *) ac_config_targets="$ac_config_targets $1" ;;
-
- esac
- shift
-done
-
-ac_configure_extra_args=
-
-if $ac_cs_silent; then
- exec 6>/dev/null
- ac_configure_extra_args="$ac_configure_extra_args --silent"
-fi
-
-_ACEOF
-cat >>$CONFIG_STATUS <<_ACEOF
-if \$ac_cs_recheck; then
- echo "running $SHELL $0 " $ac_configure_args \$ac_configure_extra_args " --no-create --no-recursion" >&6
- exec $SHELL $0 $ac_configure_args \$ac_configure_extra_args --no-create --no-recursion
-fi
-
-_ACEOF
-
-
-
-
-
-cat >>$CONFIG_STATUS <<\_ACEOF
-for ac_config_target in $ac_config_targets
-do
- case "$ac_config_target" in
- # Handling of arguments.
- "Makefile" ) CONFIG_FILES="$CONFIG_FILES Makefile" ;;
- *) { { echo "$as_me:$LINENO: error: invalid argument: $ac_config_target" >&5
-echo "$as_me: error: invalid argument: $ac_config_target" >&2;}
- { (exit 1); exit 1; }; };;
- esac
done
-
-# If the user did not use the arguments to specify the items to instantiate,
-# then the envvar interface is used. Set only those that are not.
-# We use the long form for the default assignment because of an extremely
-# bizarre bug on SunOS 4.1.3.
-if $ac_need_defaults; then
- test "${CONFIG_FILES+set}" = set || CONFIG_FILES=$config_files
+if test -z "$ac_sed_cmds"; then
+ ac_sed_cmds=cat
fi
+EOF
-# Have a temporary directory for convenience. Make it in the build tree
-# simply because there is no reason to put it here, and in addition,
-# creating and moving files from /tmp can sometimes cause problems.
-# Create a temporary directory, and hook for its removal unless debugging.
-$debug ||
-{
- trap 'exit_status=$?; rm -rf $tmp && exit $exit_status' 0
- trap '{ (exit 1); exit 1; }' 1 2 13 15
-}
-
-# Create a (secure) tmp directory for tmp files.
-
-{
- tmp=`(umask 077 && mktemp -d -q "./confstatXXXXXX") 2>/dev/null` &&
- test -n "$tmp" && test -d "$tmp"
-} ||
-{
- tmp=./confstat$$-$RANDOM
- (umask 077 && mkdir $tmp)
-} ||
-{
- echo "$me: cannot create a temporary directory in ." >&2
- { (exit 1); exit 1; }
-}
-
-_ACEOF
-
-cat >>$CONFIG_STATUS <<_ACEOF
-
-#
-# CONFIG_FILES section.
-#
-
-# No need to generate the scripts if there are no CONFIG_FILES.
-# This happens for instance when ./config.status config.h
-if test -n "\$CONFIG_FILES"; then
- # Protect against being on the right side of a sed subst in config.status.
- sed 's/,@/@@/; s/@,/@@/; s/,;t t\$/@;t t/; /@;t t\$/s/[\\\\&,]/\\\\&/g;
- s/@@/,@/; s/@@/@,/; s/@;t t\$/,;t t/' >\$tmp/subs.sed <<\\CEOF
-s,@SHELL@,$SHELL,;t t
-s,@PATH_SEPARATOR@,$PATH_SEPARATOR,;t t
-s,@PACKAGE_NAME@,$PACKAGE_NAME,;t t
-s,@PACKAGE_TARNAME@,$PACKAGE_TARNAME,;t t
-s,@PACKAGE_VERSION@,$PACKAGE_VERSION,;t t
-s,@PACKAGE_STRING@,$PACKAGE_STRING,;t t
-s,@PACKAGE_BUGREPORT@,$PACKAGE_BUGREPORT,;t t
-s,@exec_prefix@,$exec_prefix,;t t
-s,@prefix@,$prefix,;t t
-s,@program_transform_name@,$program_transform_name,;t t
-s,@bindir@,$bindir,;t t
-s,@sbindir@,$sbindir,;t t
-s,@libexecdir@,$libexecdir,;t t
-s,@datadir@,$datadir,;t t
-s,@sysconfdir@,$sysconfdir,;t t
-s,@sharedstatedir@,$sharedstatedir,;t t
-s,@localstatedir@,$localstatedir,;t t
-s,@libdir@,$libdir,;t t
-s,@includedir@,$includedir,;t t
-s,@oldincludedir@,$oldincludedir,;t t
-s,@infodir@,$infodir,;t t
-s,@mandir@,$mandir,;t t
-s,@build_alias@,$build_alias,;t t
-s,@host_alias@,$host_alias,;t t
-s,@target_alias@,$target_alias,;t t
-s,@DEFS@,$DEFS,;t t
-s,@ECHO_C@,$ECHO_C,;t t
-s,@ECHO_N@,$ECHO_N,;t t
-s,@ECHO_T@,$ECHO_T,;t t
-s,@LIBS@,$LIBS,;t t
-s,@XSLTPROC@,$XSLTPROC,;t t
-s,@PDFLATEX@,$PDFLATEX,;t t
-s,@DOC_BUILD_DATE@,$DOC_BUILD_DATE,;t t
-s,@LIBOBJS@,$LIBOBJS,;t t
-s,@LTLIBOBJS@,$LTLIBOBJS,;t t
-CEOF
+cat >> $CONFIG_STATUS <<EOF
-_ACEOF
-
- cat >>$CONFIG_STATUS <<\_ACEOF
- # Split the substitutions into bite-sized pieces for seds with
- # small command number limits, like on Digital OSF/1 and HP-UX.
- ac_max_sed_lines=48
- ac_sed_frag=1 # Number of current file.
- ac_beg=1 # First line for current file.
- ac_end=$ac_max_sed_lines # Line after last line for current file.
- ac_more_lines=:
- ac_sed_cmds=
- while $ac_more_lines; do
- if test $ac_beg -gt 1; then
- sed "1,${ac_beg}d; ${ac_end}q" $tmp/subs.sed >$tmp/subs.frag
- else
- sed "${ac_end}q" $tmp/subs.sed >$tmp/subs.frag
- fi
- if test ! -s $tmp/subs.frag; then
- ac_more_lines=false
- else
- # The purpose of the label and of the branching condition is to
- # speed up the sed processing (if there are no `@' at all, there
- # is no need to browse any of the substitutions).
- # These are the two extra sed commands mentioned above.
- (echo ':t
- /@[a-zA-Z_][a-zA-Z_0-9]*@/!b' && cat $tmp/subs.frag) >$tmp/subs-$ac_sed_frag.sed
- if test -z "$ac_sed_cmds"; then
- ac_sed_cmds="sed -f $tmp/subs-$ac_sed_frag.sed"
- else
- ac_sed_cmds="$ac_sed_cmds | sed -f $tmp/subs-$ac_sed_frag.sed"
- fi
- ac_sed_frag=`expr $ac_sed_frag + 1`
- ac_beg=$ac_end
- ac_end=`expr $ac_end + $ac_max_sed_lines`
- fi
- done
- if test -z "$ac_sed_cmds"; then
- ac_sed_cmds=cat
- fi
-fi # test -n "$CONFIG_FILES"
-
-_ACEOF
-cat >>$CONFIG_STATUS <<\_ACEOF
-for ac_file in : $CONFIG_FILES; do test "x$ac_file" = x: && continue
+CONFIG_FILES=\${CONFIG_FILES-"Makefile "}
+EOF
+cat >> $CONFIG_STATUS <<\EOF
+for ac_file in .. $CONFIG_FILES; do if test "x$ac_file" != x..; then
# Support "outfile[:infile[:infile...]]", defaulting infile="outfile.in".
- case $ac_file in
- - | *:- | *:-:* ) # input from stdin
- cat >$tmp/stdin
- ac_file_in=`echo "$ac_file" | sed 's,[^:]*:,,'`
- ac_file=`echo "$ac_file" | sed 's,:.*,,'` ;;
- *:* ) ac_file_in=`echo "$ac_file" | sed 's,[^:]*:,,'`
- ac_file=`echo "$ac_file" | sed 's,:.*,,'` ;;
- * ) ac_file_in=$ac_file.in ;;
+ case "$ac_file" in
+ *:*) ac_file_in=`echo "$ac_file"|sed 's%[^:]*:%%'`
+ ac_file=`echo "$ac_file"|sed 's%:.*%%'` ;;
+ *) ac_file_in="${ac_file}.in" ;;
esac
- # Compute @srcdir@, @top_srcdir@, and @INSTALL@ for subdirectories.
- ac_dir=`(dirname "$ac_file") 2>/dev/null ||
-$as_expr X"$ac_file" : 'X\(.*[^/]\)//*[^/][^/]*/*$' \| \
- X"$ac_file" : 'X\(//\)[^/]' \| \
- X"$ac_file" : 'X\(//\)$' \| \
- X"$ac_file" : 'X\(/\)' \| \
- . : '\(.\)' 2>/dev/null ||
-echo X"$ac_file" |
- sed '/^X\(.*[^/]\)\/\/*[^/][^/]*\/*$/{ s//\1/; q; }
- /^X\(\/\/\)[^/].*/{ s//\1/; q; }
- /^X\(\/\/\)$/{ s//\1/; q; }
- /^X\(\/\).*/{ s//\1/; q; }
- s/.*/./; q'`
- { if $as_mkdir_p; then
- mkdir -p "$ac_dir"
+ # Adjust a relative srcdir, top_srcdir, and INSTALL for subdirectories.
+
+ # Remove last slash and all that follows it. Not all systems have dirname.
+ ac_dir=`echo $ac_file|sed 's%/[^/][^/]*$%%'`
+ if test "$ac_dir" != "$ac_file" && test "$ac_dir" != .; then
+ # The file is in a subdirectory.
+ test ! -d "$ac_dir" && mkdir "$ac_dir"
+ ac_dir_suffix="/`echo $ac_dir|sed 's%^\./%%'`"
+ # A "../" for each directory in $ac_dir_suffix.
+ ac_dots=`echo $ac_dir_suffix|sed 's%/[^/]*%../%g'`
else
- as_dir="$ac_dir"
- as_dirs=
- while test ! -d "$as_dir"; do
- as_dirs="$as_dir $as_dirs"
- as_dir=`(dirname "$as_dir") 2>/dev/null ||
-$as_expr X"$as_dir" : 'X\(.*[^/]\)//*[^/][^/]*/*$' \| \
- X"$as_dir" : 'X\(//\)[^/]' \| \
- X"$as_dir" : 'X\(//\)$' \| \
- X"$as_dir" : 'X\(/\)' \| \
- . : '\(.\)' 2>/dev/null ||
-echo X"$as_dir" |
- sed '/^X\(.*[^/]\)\/\/*[^/][^/]*\/*$/{ s//\1/; q; }
- /^X\(\/\/\)[^/].*/{ s//\1/; q; }
- /^X\(\/\/\)$/{ s//\1/; q; }
- /^X\(\/\).*/{ s//\1/; q; }
- s/.*/./; q'`
- done
- test ! -n "$as_dirs" || mkdir $as_dirs
- fi || { { echo "$as_me:$LINENO: error: cannot create directory \"$ac_dir\"" >&5
-echo "$as_me: error: cannot create directory \"$ac_dir\"" >&2;}
- { (exit 1); exit 1; }; }; }
-
- ac_builddir=.
-
-if test "$ac_dir" != .; then
- ac_dir_suffix=/`echo "$ac_dir" | sed 's,^\.[\\/],,'`
- # A "../" for each directory in $ac_dir_suffix.
- ac_top_builddir=`echo "$ac_dir_suffix" | sed 's,/[^\\/]*,../,g'`
-else
- ac_dir_suffix= ac_top_builddir=
-fi
+ ac_dir_suffix= ac_dots=
+ fi
-case $srcdir in
- .) # No --srcdir option. We are building in place.
- ac_srcdir=.
- if test -z "$ac_top_builddir"; then
- ac_top_srcdir=.
- else
- ac_top_srcdir=`echo $ac_top_builddir | sed 's,/$,,'`
- fi ;;
- [\\/]* | ?:[\\/]* ) # Absolute path.
- ac_srcdir=$srcdir$ac_dir_suffix;
- ac_top_srcdir=$srcdir ;;
+ case "$ac_given_srcdir" in
+ .) srcdir=.
+ if test -z "$ac_dots"; then top_srcdir=.
+ else top_srcdir=`echo $ac_dots|sed 's%/$%%'`; fi ;;
+ /*) srcdir="$ac_given_srcdir$ac_dir_suffix"; top_srcdir="$ac_given_srcdir" ;;
*) # Relative path.
- ac_srcdir=$ac_top_builddir$srcdir$ac_dir_suffix
- ac_top_srcdir=$ac_top_builddir$srcdir ;;
-esac
-# Don't blindly perform a `cd "$ac_dir"/$ac_foo && pwd` since $ac_foo can be
-# absolute.
-ac_abs_builddir=`cd "$ac_dir" && cd $ac_builddir && pwd`
-ac_abs_top_builddir=`cd "$ac_dir" && cd ${ac_top_builddir}. && pwd`
-ac_abs_srcdir=`cd "$ac_dir" && cd $ac_srcdir && pwd`
-ac_abs_top_srcdir=`cd "$ac_dir" && cd $ac_top_srcdir && pwd`
+ srcdir="$ac_dots$ac_given_srcdir$ac_dir_suffix"
+ top_srcdir="$ac_dots$ac_given_srcdir" ;;
+ esac
+ echo creating "$ac_file"
+ rm -f "$ac_file"
+ configure_input="Generated automatically from `echo $ac_file_in|sed 's%.*/%%'` by configure."
+ case "$ac_file" in
+ *Makefile*) ac_comsub="1i\\
+# $configure_input" ;;
+ *) ac_comsub= ;;
+ esac
- if test x"$ac_file" != x-; then
- { echo "$as_me:$LINENO: creating $ac_file" >&5
-echo "$as_me: creating $ac_file" >&6;}
- rm -f "$ac_file"
- fi
- # Let's still pretend it is `configure' which instantiates (i.e., don't
- # use $as_me), people would be surprised to read:
- # /* config.h. Generated by config.status. */
- if test x"$ac_file" = x-; then
- configure_input=
- else
- configure_input="$ac_file. "
- fi
- configure_input=$configure_input"Generated from `echo $ac_file_in |
- sed 's,.*/,,'` by configure."
-
- # First look for the input files in the build tree, otherwise in the
- # src tree.
- ac_file_inputs=`IFS=:
- for f in $ac_file_in; do
- case $f in
- -) echo $tmp/stdin ;;
- [\\/$]*)
- # Absolute (can't be DOS-style, as IFS=:)
- test -f "$f" || { { echo "$as_me:$LINENO: error: cannot find input file: $f" >&5
-echo "$as_me: error: cannot find input file: $f" >&2;}
- { (exit 1); exit 1; }; }
- echo $f;;
- *) # Relative
- if test -f "$f"; then
- # Build tree
- echo $f
- elif test -f "$srcdir/$f"; then
- # Source tree
- echo $srcdir/$f
- else
- # /dev/null tree
- { { echo "$as_me:$LINENO: error: cannot find input file: $f" >&5
-echo "$as_me: error: cannot find input file: $f" >&2;}
- { (exit 1); exit 1; }; }
- fi;;
- esac
- done` || { (exit 1); exit 1; }
-_ACEOF
-cat >>$CONFIG_STATUS <<_ACEOF
- sed "$ac_vpsub
-$extrasub
-_ACEOF
-cat >>$CONFIG_STATUS <<\_ACEOF
-:t
-/@[a-zA-Z_][a-zA-Z_0-9]*@/!b
-s,@configure_input@,$configure_input,;t t
-s,@srcdir@,$ac_srcdir,;t t
-s,@abs_srcdir@,$ac_abs_srcdir,;t t
-s,@top_srcdir@,$ac_top_srcdir,;t t
-s,@abs_top_srcdir@,$ac_abs_top_srcdir,;t t
-s,@builddir@,$ac_builddir,;t t
-s,@abs_builddir@,$ac_abs_builddir,;t t
-s,@top_builddir@,$ac_top_builddir,;t t
-s,@abs_top_builddir@,$ac_abs_top_builddir,;t t
-" $ac_file_inputs | (eval "$ac_sed_cmds") >$tmp/out
- rm -f $tmp/stdin
- if test x"$ac_file" != x-; then
- mv $tmp/out $ac_file
- else
- cat $tmp/out
- rm -f $tmp/out
- fi
+ ac_file_inputs=`echo $ac_file_in|sed -e "s%^%$ac_given_srcdir/%" -e "s%:% $ac_given_srcdir/%g"`
+ sed -e "$ac_comsub
+s%@configure_input@%$configure_input%g
+s%@srcdir@%$srcdir%g
+s%@top_srcdir@%$top_srcdir%g
+" $ac_file_inputs | (eval "$ac_sed_cmds") > $ac_file
+fi; done
+rm -f conftest.s*
-done
-_ACEOF
+EOF
+cat >> $CONFIG_STATUS <<EOF
-cat >>$CONFIG_STATUS <<\_ACEOF
+EOF
+cat >> $CONFIG_STATUS <<\EOF
-{ (exit 0); exit 0; }
-_ACEOF
+exit 0
+EOF
chmod +x $CONFIG_STATUS
-ac_clean_files=$ac_clean_files_save
-
-
-# configure is writing to config.log, and then calls config.status.
-# config.status does its own redirection, appending to config.log.
-# Unfortunately, on DOS this fails, as config.log is still kept open
-# by configure, so config.status won't be able to write to it; its
-# output is simply discarded. So we exec the FD to /dev/null,
-# effectively closing config.log, so it can be properly (re)opened and
-# appended to by config.status. When coming back to configure, we
-# need to make the FD available again.
-if test "$no_create" != yes; then
- ac_cs_success=:
- ac_config_status_args=
- test "$silent" = yes &&
- ac_config_status_args="$ac_config_status_args --quiet"
- exec 5>/dev/null
- $SHELL $CONFIG_STATUS $ac_config_status_args || ac_cs_success=false
- exec 5>>config.log
- # Use ||, not &&, to avoid exiting from the if with $? = 1, which
- # would make configure fail if this is the last instruction.
- $ac_cs_success || { (exit 1); exit 1; }
-fi
+rm -fr confdefs* $ac_clean_files
+test "$no_create" = yes || ${CONFIG_SHELL-/bin/sh} $CONFIG_STATUS || exit 1
diff --git a/docs/docbook/configure.in b/docs/docbook/configure.in
index 6775e6db94..80368d8390 100644
--- a/docs/docbook/configure.in
+++ b/docs/docbook/configure.in
@@ -9,6 +9,8 @@ if test "x$PDFLATEX" = x; then
AC_MSG_ERROR("pdflatex is required")
fi
+AC_PATH_PROG(XMLTO, xmlto)
+
DOC_BUILD_DATE=`date '+%d-%m-%Y'`
AC_SUBST(DOC_BUILD_DATE)
diff --git a/docs/docbook/devdoc/dev-doc.xml b/docs/docbook/devdoc/dev-doc.xml
index 0ed4275972..cb5089309d 100644
--- a/docs/docbook/devdoc/dev-doc.xml
+++ b/docs/docbook/devdoc/dev-doc.xml
@@ -1,5 +1,6 @@
<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE book SYSTEM "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [
+<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"[
+
<!ENTITY NetBIOS SYSTEM "NetBIOS.xml">
<!ENTITY Architecture SYSTEM "architecture.xml">
<!ENTITY debug SYSTEM "debug.xml">
@@ -16,7 +17,6 @@
<!ENTITY rpc-plugin SYSTEM "rpc_plugin.xml">
<!ENTITY modules SYSTEM "modules.xml">
<!ENTITY packagers SYSTEM "packagers.xml">
-<!ENTITY contributing SYSTEM "contributing.xml">
]>
<book id="Samba-Developers-Guide">
@@ -77,6 +77,5 @@ url="http://www.fsf.org/licenses/gpl.txt">http://www.fsf.org/licenses/gpl.txt</u
&modules;
&rpc-plugin;
&packagers;
-&contributing;
</book>
diff --git a/docs/docbook/global.ent b/docs/docbook/global.ent
index 0ff0c9a5cf..69924d7c94 100644
--- a/docs/docbook/global.ent
+++ b/docs/docbook/global.ent
@@ -503,3 +503,5 @@ an Active Directory environment.
<!ENTITY Further-Resources SYSTEM "projdoc/Further-Resources.xml">
<!ENTITY not.implemented "<note><para>Currently NOT implemented.</para></note>">
+<!ENTITY not "<emphasis>NOT</emphasis>">
+<!ENTITY rootprompt "<prompt>root# </prompt>">
diff --git a/docs/docbook/manpages/.cvsignore b/docs/docbook/manpages/.cvsignore
index 2d6c32d7f2..90c11de0f9 100644
--- a/docs/docbook/manpages/.cvsignore
+++ b/docs/docbook/manpages/.cvsignore
@@ -1 +1 @@
-smb.conf.5.xml \ No newline at end of file
+smb.conf.5.xml
diff --git a/docs/docbook/manpages/profiles.1.sgml b/docs/docbook/manpages/profiles.1.sgml
new file mode 100644
index 0000000000..6fd2b6fd86
--- /dev/null
+++ b/docs/docbook/manpages/profiles.1.sgml
@@ -0,0 +1,86 @@
+<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook V4.1//EN" [
+<!ENTITY % globalentities SYSTEM '../global.ent'> %globalentities;
+]>
+<refentry id="profiles.1">
+
+<refmeta>
+ <refentrytitle>profiles</refentrytitle>
+ <manvolnum>1</manvolnum>
+</refmeta>
+
+
+<refnamediv>
+ <refname>profiles</refname>
+ <refpurpose>A utility to report and change SIDs in registry files
+ </refpurpose>
+</refnamediv>
+
+<refsynopsisdiv>
+ <cmdsynopsis>
+ <command>profiles</command>
+ <arg choice="opt">-v</arg>
+ <arg choice="opt">-c SID</arg>
+ <arg choice="opt">-n SID</arg>
+ <arg choice="req">file</arg>
+ </cmdsynopsis>
+</refsynopsisdiv>
+
+<refsect1>
+ <title>DESCRIPTION</title>
+
+ <para>This tool is part of the <citerefentry><refentrytitle>Samba</refentrytitle>
+ <manvolnum>7</manvolnum></citerefentry> suite.</para>
+
+ <para><command>profiles</command> is a utility that
+ reports and changes SIDs in windows registry files. It currently only
+ supports NT.
+ </para>
+</refsect1>
+
+
+<refsect1>
+ <title>OPTIONS</title>
+
+ <variablelist>
+ <varlistentry>
+ <term>file</term>
+ <listitem><para>Registry file to view or edit. </para></listitem>
+ </varlistentry>
+
+
+ <varlistentry>
+ <term>-v,--verbose</term>
+ <listitem><para>Increases verbosity of messages.
+ </para></listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term>-c SID1 -n SID2</term>
+ <listitem><para>Change all occurences of SID1 in <filename>file</filename> by SID2.
+ </para></listitem>
+ </varlistentry>
+
+ &stdarg.help;
+
+ </variablelist>
+</refsect1>
+
+<refsect1>
+ <title>VERSION</title>
+
+ <para>This man page is correct for version 3.0 of the Samba
+ suite.</para>
+</refsect1>
+
+<refsect1>
+ <title>AUTHOR</title>
+
+ <para>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.</para>
+
+ <para>The profiles man page was written by Jelmer Vernooij. </para>
+</refsect1>
+
+</refentry>
diff --git a/docs/docbook/manpages/rpcclient.1.xml b/docs/docbook/manpages/rpcclient.1.xml
index c6775d9721..688eef14e8 100644
--- a/docs/docbook/manpages/rpcclient.1.xml
+++ b/docs/docbook/manpages/rpcclient.1.xml
@@ -299,7 +299,7 @@ Comma Separated list of Files
<listitem><para>Execute an EnumPrinters() call. This lists the various installed
and share printers. Refer to the MS Platform SDK documentation for
more details of the various flags and calling options. Currently
- supported info levels are 0, 1, and 2.</para></listitem></varlistentry>
+ supported info levels are 1, 2 and 5.</para></listitem></varlistentry>
diff --git a/docs/docbook/projdoc/AccessControls.xml b/docs/docbook/projdoc/AccessControls.xml
index 38c3475d34..6a56705a54 100644
--- a/docs/docbook/projdoc/AccessControls.xml
+++ b/docs/docbook/projdoc/AccessControls.xml
@@ -176,11 +176,11 @@ at how Samba helps to bridge the differences.
</para>
<para>
Consider the following, all are unique Unix names but one single MS Windows file name:
- <programlisting>
+ <computeroutput>
MYFILE.TXT
MyFile.txt
myfile.txt
- </programlisting>
+ </computeroutput>
So clearly, In an MS Windows file name space these three files CAN NOT co-exist! But in Unix
they can. So what should Samba do if all three are present? Answer, the one that is lexically
first will be accessible to MS Windows users, the others are invisible and unaccessible - any
@@ -246,13 +246,17 @@ at how Samba helps to bridge the differences.
<para>
There are three basic operations for managing directories, <command>create, delete, rename</command>.
- <programlisting>
- Action MS Windows Command Unix Command
- ------ ------------------ ------------
- create md folder mkdir folder
- delete rd folder rmdir folder
- rename rename oldname newname mv oldname newname
- </programlisting>
+ <table>
+ <thead>
+ <row><entry>Action</entry><entry>MS Windows Command</entry><entry>Unix Command</entry></row>
+ </thead>
+
+ <tbody>
+ <row><entry>create</entry><entry>md folder</entry><entry>mkdir folder</entry></row>
+ <row><entry>delete</entry><entry>rd folder</entry><entry>rmdir folder</entry></row>
+ <row><entry>rename</entry><entry>rename oldname newname</entry><entry>mv oldname newname</entry></row>
+ </tbody>
+ </table>
</para>
</sect2>
@@ -271,8 +275,8 @@ at how Samba helps to bridge the differences.
Unix/Linux file and directory access permissions invloves setting three (3) primary sets of data and one (1) control set.
A Unix file listing looks as follows:-
- <programlisting>
- jht@frodo:~/stuff> ls -la
+ <screen>
+ <prompt>jht@frodo:~/stuff> </prompt><userinput>ls -la</userinput>
total 632
drwxr-xr-x 13 jht users 816 2003-05-12 22:56 .
drwxr-xr-x 37 jht users 3800 2003-05-12 22:29 ..
@@ -293,8 +297,8 @@ at how Samba helps to bridge the differences.
-r-xr-xr-x 1 jht users 206339 2003-05-12 22:32 mydata05.lst
-rw-rw-rw- 1 jht users 41105 2003-05-12 22:32 mydata06.lst
-rwxrwxrwx 1 jht users 19312 2003-05-12 22:32 mydata07.lst
- jht@frodo:~/stuff>
- </programlisting>
+ <prompt>jht@frodo:~/stuff></prompt>
+ </screen>
</para>
<para>
@@ -305,6 +309,7 @@ at how Samba helps to bridge the differences.
The permissions field is made up of:
<programlisting>
+ <!-- JRV: Put this into a diagram of some sort -->
[ type ] [ users ] [ group ] [ others ] [File, Directory Permissions]
[ d | l ] [ r w x ] [ r w x ] [ r w x ]
| | | | | | | | | | |
@@ -324,6 +329,7 @@ at how Samba helps to bridge the differences.
<para>
Any bit flag may be unset. An unset bit flag is the equivalent of 'Can NOT' and is represented as a '-' character.
+ <!-- FIXME -->
<programlisting>
<title>Example File</title>
-rwxr-x--- Means: The owner (user) can read, write, execute
@@ -337,7 +343,7 @@ at how Samba helps to bridge the differences.
</para>
<para>
- The letters `rwxXst' set permissions for the user, group and others as: read (r), write (w), execute (or access for directories) (x),r
+ The letters `rwxXst' set permissions for the user, group and others as: read (r), write (w), execute (or access for directories) (x),r
execute only if the file is a directory or already has execute permission for some user (X), set user or group ID on execution (s),
sticky (t).
</para>
@@ -809,7 +815,7 @@ Before using any of the following options please refer to the man page for &smb.
<sect2>
<title>Viewing file ownership</title>
- <para>Clicking on the <command>"Ownership"</command> button
+ <para>Clicking on the <guibutton>Ownership</guibutton> button
brings up a dialog box telling you who owns the given file. The
owner name will be of the form :</para>
@@ -819,14 +825,14 @@ Before using any of the following options please refer to the man page for &smb.
the Samba server, <replaceable>user</replaceable> is the user name of
the UNIX user who owns the file, and <replaceable>(Long name)</replaceable>
is the descriptive string identifying the user (normally found in the
- GECOS field of the UNIX password database). Click on the <command>Close
- </command> button to remove this dialog.</para>
+ GECOS field of the UNIX password database). Click on the
+ <guibutton>Close </guibutton> button to remove this dialog.</para>
<para>If the parameter <parameter>nt acl support</parameter>
is set to <constant>false</constant> then the file owner will
- be shown as the NT user <command>"Everyone"</command>.</para>
+ be shown as the NT user <constant>"Everyone"</constant>.</para>
- <para>The <command>Take Ownership</command> button will not allow
+ <para>The <guibutton>Take Ownership</guibutton> button will not allow
you to change the ownership of this file to yourself (clicking on
it will display a dialog box complaining that the user you are
currently logged onto the NT client cannot be found). The reason
@@ -849,12 +855,14 @@ Before using any of the following options please refer to the man page for &smb.
<sect2>
<title>Viewing File or Directory Permissions</title>
- <para>The third button is the <command>"Permissions"</command>
+ <para>The third button is the <guibutton>Permissions</guibutton>
button. Clicking on this brings up a dialog box that shows both
the permissions and the UNIX owner of the file or directory.
The owner is displayed in the form :</para>
- <para><command>"SERVER\user (Long name)"</command></para>
+ <para><command>"<replaceable>SERVER</replaceable>\
+ <replaceable>user</replaceable>
+ <replaceable>(Long name)</replaceable>"</command></para>
<para>Where <replaceable>SERVER</replaceable> is the NetBIOS name of
the Samba server, <replaceable>user</replaceable> is the user name of
@@ -864,7 +872,7 @@ Before using any of the following options please refer to the man page for &smb.
<para>If the parameter <parameter>nt acl support</parameter>
is set to <constant>false</constant> then the file owner will
- be shown as the NT user <command>"Everyone"</command> and the
+ be shown as the NT user <constant>"Everyone"</constant> and the
permissions will be shown as NT "Full Control".</para>
@@ -880,18 +888,18 @@ Before using any of the following options please refer to the man page for &smb.
triples are mapped by Samba into a three element NT ACL
with the 'r', 'w', and 'x' bits mapped into the corresponding
NT permissions. The UNIX world permissions are mapped into
- the global NT group <command>Everyone</command>, followed
+ the global NT group <constant>Everyone</constant>, followed
by the list of permissions allowed for UNIX world. The UNIX
owner and group permissions are displayed as an NT
- <command>user</command> icon and an NT <command>local
- group</command> icon respectively followed by the list
+ <guiicon>user</guiicon> icon and an NT <guiicon>local
+ group</guiicon> icon respectively followed by the list
of permissions allowed for the UNIX user and group.</para>
<para>As many UNIX permission sets don't map into common
- NT names such as <command>"read"</command>, <command>
- "change"</command> or <command>"full control"</command> then
- usually the permissions will be prefixed by the words <command>
- "Special Access"</command> in the NT display list.</para>
+ NT names such as <constant>read</constant>, <constant>
+ "change"</constant> or <constant>full control</constant> then
+ usually the permissions will be prefixed by the words <constant>
+ "Special Access"</constant> in the NT display list.</para>
<para>But what happens if the file has no permissions allowed
for a particular UNIX user group or world component ? In order
@@ -916,8 +924,8 @@ Before using any of the following options please refer to the man page for &smb.
above, and is displayed in the same way.</para>
<para>The second set of directory permissions has no real meaning
- in the UNIX permissions world and represents the <command>
- "inherited"</command> permissions that any file created within
+ in the UNIX permissions world and represents the <constant>
+ inherited</constant> permissions that any file created within
this directory would inherit.</para>
<para>Samba synthesises these inherited permissions for NT by
@@ -931,27 +939,27 @@ Before using any of the following options please refer to the man page for &smb.
<para>Modifying file and directory permissions is as simple
as changing the displayed permissions in the dialog box, and
- clicking the <command>OK</command> button. However, there are
+ clicking the <guibutton>OK</guibutton> button. However, there are
limitations that a user needs to be aware of, and also interactions
with the standard Samba permission masks and mapping of DOS
attributes that need to also be taken into account.</para>
<para>If the parameter <parameter>nt acl support</parameter>
is set to <constant>false</constant> then any attempt to set
- security permissions will fail with an <command>"Access Denied"
- </command> message.</para>
+ security permissions will fail with an <errorname>"Access Denied"
+ </errorname> message.</para>
- <para>The first thing to note is that the <command>"Add"</command>
+ <para>The first thing to note is that the <guibutton>"Add"</guibutton>
button will not return a list of users in Samba (it will give
- an error message of <command>"The remote procedure call failed
- and did not execute"</command>). This means that you can only
+ an error message of <errorname>The remote procedure call failed
+ and did not execute</errorname>). This means that you can only
manipulate the current user/group/world permissions listed in
the dialog box. This actually works quite well as these are the
only permissions that UNIX actually has.</para>
<para>If a permission triple (either user, group, or world)
is removed from the list of permissions in the NT dialog box,
- then when the <command>"OK"</command> button is pressed it will
+ then when the <guibutton>OK</guibutton> button is pressed it will
be applied as "no permissions" on the UNIX side. If you then
view the permissions again the "no permissions" entry will appear
as the NT <command>"O"</command> flag, as described above. This
@@ -966,15 +974,15 @@ Before using any of the following options please refer to the man page for &smb.
<para>When setting permissions on a directory the second
set of permissions (in the second set of parentheses) is
by default applied to all files within that directory. If this
- is not what you want you must uncheck the <command>"Replace
- permissions on existing files"</command> checkbox in the NT
- dialog before clicking <command>"OK"</command>.</para>
+ is not what you want you must uncheck the <guilabel>Replace
+ permissions on existing files</guilabel> checkbox in the NT
+ dialog before clicking <guibutton>OK</guibutton>.</para>
<para>If you wish to remove all permissions from a
user/group/world component then you may either highlight the
- component and click the <command>"Remove"</command> button,
- or set the component to only have the special <command>"Take
- Ownership"</command> permission (displayed as <command>"O"
+ component and click the <guibutton>Remove</guibutton> button,
+ or set the component to only have the special <constant>Take
+ Ownership</constant> permission (displayed as <command>"O"
</command>) highlighted.</para>
</sect2>
@@ -991,7 +999,7 @@ Before using any of the following options please refer to the man page for &smb.
<para><parameter>directory security mask</parameter></para>
<para><parameter>force directory security mode</parameter></para>
- <para>Once a user clicks <command>"OK"</command> to apply the
+ <para>Once a user clicks <guibutton>OK</guibutton> to apply the
permissions Samba maps the given permissions into a user/group/world
r/w/x triple set, and then will check the changed permissions for a
file against the bits set in the <ulink url="smb.conf.5.html#SECURITYMASK">
@@ -1075,13 +1083,13 @@ Before using any of the following options please refer to the man page for &smb.
<para>What this can mean is that if the owner changes the permissions
to allow themselves read access using the security dialog, clicks
- <command>"OK"</command> to get back to the standard attributes tab
- dialog, and then clicks <command>"OK"</command> on that dialog, then
+ <guibutton>OK</guibutton> to get back to the standard attributes tab
+ dialog, and then clicks <guibutton>OK</guibutton> on that dialog, then
NT will set the file permissions back to read-only (as that is what
the attributes still say in the dialog). This means that after setting
- permissions and clicking <command>"OK"</command> to get back to the
- attributes dialog you should always hit <command>"Cancel"</command>
- rather than <command>"OK"</command> to ensure that your changes
+ permissions and clicking <guibutton>OK</guibutton> to get back to the
+ attributes dialog you should always hit <guibutton>Cancel</guibutton>
+ rather than <guibutton>OK</guibutton> to ensure that your changes
are not overridden.</para>
</sect2>
</sect1>
@@ -1099,10 +1107,12 @@ are examples taken from the mailing list in recent times.
<title>Users can not write to a public share</title>
<para>
+ <quote>
We are facing some troubles with file / directory permissions. I can log on the domain as admin user(root),
and theres a public share, on which everyone needs to have permission to create / modify files, but only
root can change the file, no one else can. We need to constantly go to server to
- <command>chgrp -R users *</command> and <command>chown -R nobody *</command> to allow others users to change the file.
+ <userinput>chgrp -R users *</userinput> and <userinput>chown -R nobody *</userinput> to allow others users to change the file.
+ </quote>
</para>
<para>
@@ -1112,77 +1122,99 @@ are examples taken from the mailing list in recent times.
<procedure>
<title>Example Solution:</title>
<step>
- <para>
- Go to the top of the directory that is shared
- </para>
+ <para>
+ Go to the top of the directory that is shared
+ </para>
</step>
<step>
- <para>
- Set the ownership to what ever public owner and group you want
- <programlisting>
- find 'directory_name' -type d -exec chown user.group {}\;
- find 'directory_name' -type d -exec chmod 6775 'directory_name'
- find 'directory_name' -type f -exec chmod 0775 {} \;
- find 'directory_name' -type f -exec chown user.group {}\;
- </programlisting>
- </para>
+ <para>
+ Set the ownership to what ever public owner and group you want
+ <programlisting>
+ find 'directory_name' -type d -exec chown user.group {}\;
+ find 'directory_name' -type d -exec chmod 6775 'directory_name'
+ find 'directory_name' -type f -exec chmod 0775 {} \;
+ find 'directory_name' -type f -exec chown user.group {}\;
+ </programlisting>
+ </para>
- <para>
- Note: The above will set the 'sticky bit' on all directories. Read your
- Unix/Linux man page on what that does. It causes the OS to assign to all
- files created in the directories the ownership of the directory.
- </para>
+ <note><para>
+ The above will set the 'sticky bit' on all directories. Read your
+ Unix/Linux man page on what that does. It causes the OS to assign
+ to all files created in the directories the ownership of the
+ directory.
+ </para></note>
+ </step>
+ <step>
+ <para>
- <para>
- <programlisting>
- Directory is: /foodbar
- chown jack.engr /foodbar
+ Directory is: <replaceable>/foodbar</replaceable>
+ <screen>
+ <prompt>$ </prompt><userinput>chown jack.engr /foodbar</userinput>
+ </screen>
+ </para>
- Note: This is the same as doing:
- chown jack /foodbar
- chgrp engr /foodbar
+ <note><para>
+ <para>This is the same as doing:</para>
+ <screen>
+ <prompt>$ </prompt><userinput>chown jack /foodbar</userinput>
+ <prompt>$ </prompt><userinput>chgrp engr /foodbar</userinput>
+ </screen>
+ </para></note>
+ </step>
+ <step>
+ <para>Now do:
- Now do:
- chmod 6775 /foodbar
- ls -al /foodbar/..
+ <screen>
+ <prompt>$ </prompt><userinput>chmod 6775 /foodbar</userinput>
+ <prompt>$ </prompt><userinput>ls -al /foodbar/..</userinput>
+ </screen>
- You should see:
- drwsrwsr-x 2 jack engr 48 2003-02-04 09:55 foodbar
+ </para>
+
+ <para>You should see:
+ <screen>
+ drwsrwsr-x 2 jack engr 48 2003-02-04 09:55 foodbar
+ </screen>
+ </para>
+ </step>
+ <step>
- Now do:
- su - jill
- cd /foodbar
- touch Afile
- ls -al
- </programlisting>
+ <para>Now do:
+ <screen>
+ <prompt>$ </prompt><userinput>su - jill</userinput>
+ <prompt>$ </prompt><userinput>cd /foodbar</userinput>
+ <prompt>$ </prompt><userinput>touch Afile</userinput>
+ <prompt>$ </prompt><userinput>ls -al</userinput>
+ </screen>
</para>
<para>
You should see that the file 'Afile' created by Jill will have ownership
and permissions of Jack, as follows:
- <programlisting>
+ <screen>
-rw-r--r-- 1 jack engr 0 2003-02-04 09:57 Afile
- </programlisting>
+ </screen>
</para>
</step>
<step>
<para>
- Now in your smb.conf for the share add:
+ Now in your &smb.conf; for the share add:
<programlisting>
force create mode = 0775
force direcrtory mode = 6775
</programlisting>
</para>
- <para>
- Note: The above are only needed IF your users are NOT members of the group
+ <note><para>
+ The above are only needed IF your users are NOT members of the group
you have used. ie: Within the OS do not have write permission on the directory.
</para>
-
+ </note>
+
<para>
- An alternative is to set in the smb.conf entry for the share:
+ An alternative is to set in the &smb.conf; entry for the share:
<programlisting>
force user = jack
force group = engr
@@ -1192,7 +1224,6 @@ are examples taken from the mailing list in recent times.
</procedure>
</sect2>
-
</sect1>
</chapter>
diff --git a/docs/docbook/projdoc/AdvancedNetworkAdmin.xml b/docs/docbook/projdoc/AdvancedNetworkAdmin.xml
index e6e7347290..a52728d9c9 100644
--- a/docs/docbook/projdoc/AdvancedNetworkAdmin.xml
+++ b/docs/docbook/projdoc/AdvancedNetworkAdmin.xml
@@ -20,20 +20,20 @@ environment, and to make their lives a little easier.
</para>
<para>
-Since I don't need to buy an NT4 Server, how do I get the 'User Manager for Domains',
+ Since I don't need to buy an <application>NT4 Server</application>, how do I get the 'User Manager for Domains',
the 'Server Manager'?
</para>
<para>
-Microsoft distributes a version of these tools called nexus for installation on Windows 9x / Me
-systems. The tools set includes:
+Microsoft distributes a version of these tools called nexus for installation
+on <application>Windows 9x / Me</application> systems. The tools set includes:
</para>
-<itemizedlist>
- <listitem><para>Server Manager</para></listitem>
- <listitem><para>User Manager for Domains</para></listitem>
- <listitem><para>Event Viewer</para></listitem>
-</itemizedlist>
+<simplelist>
+ <member>Server Manager</member>
+ <member>User Manager for Domains</member>
+ <member>Event Viewer</member>
+</simplelist>
<para>
Click here to download the archived file <ulink
@@ -41,7 +41,7 @@ url="ftp://ftp.microsoft.com/Softlib/MSLFILES/NEXUS.EXE">ftp://ftp.microsoft.com
</para>
<para>
-The Windows NT 4.0 version of the 'User Manager for
+The <application>Windows NT 4.0</application> version of the 'User Manager for
Domains' and 'Server Manager' are available from Microsoft via ftp
from <ulink url="ftp://ftp.microsoft.com/Softlib/MSLFILES/SRVTOOLS.EXE">ftp://ftp.microsoft.com/Softlib/MSLFILES/SRVTOOLS.EXE</ulink>
</para>
@@ -69,7 +69,9 @@ There are several opportunities for creating a custom network startup configurat
</simplelist>
<para>
-The Samba source code tree includes two logon script generation/execution tools. See <filename>examples</filename> directory <filename>genlogon</filename> and <filename>ntlogon</filename> subdirectories.
+The Samba source code tree includes two logon script generation/execution tools.
+See <filename>examples</filename> directory <filename>genlogon</filename> and
+<filename>ntlogon</filename> subdirectories.
</para>
<para>
@@ -77,7 +79,7 @@ The following listings are from the genlogon directory.
</para>
<para>
-This is the genlogon.pl file:
+This is the <filename>genlogon.pl</filename> file:
<programlisting>
#!/usr/bin/perl
@@ -174,10 +176,9 @@ Printers may be added automatically during logon script processing through the u
rundll32 printui.dll,PrintUIEntry /?
</programlisting>
-See the documentation in the Microsoft knowledgebase article no: 189105 referred to above.
+See the documentation in the <ulink url="http://support.microsoft.com/default.asp?scid=kb;en-us;189105">Microsoft knowledgebase article no: 189105</ulink>.
</para>
</sect2>
</sect1>
</chapter>
-
diff --git a/docs/docbook/projdoc/Bugs.xml b/docs/docbook/projdoc/Bugs.xml
index d782920457..03a60b6ce5 100644
--- a/docs/docbook/projdoc/Bugs.xml
+++ b/docs/docbook/projdoc/Bugs.xml
@@ -83,7 +83,7 @@ detail, but may use too much disk space.
</para>
<para>
-To set the debug level use <command>log level =</command> in your
+To set the debug level use the <parameter>log level</parameter> in your
&smb.conf;. You may also find it useful to set the log
level higher for just one machine and keep separate logs for each machine.
To do this use:
@@ -100,24 +100,25 @@ then create a file
<filename>/usr/local/samba/lib/smb.conf.<replaceable>machine</replaceable></filename> where
<replaceable>machine</replaceable> is the name of the client you wish to debug. In that file
put any &smb.conf; commands you want, for example
-<command>log level=</command> may be useful. This also allows you to
+<parameter>log level</parameter> may be useful. This also allows you to
experiment with different security systems, protocol levels etc on just
one machine.
</para>
<para>
-The &smb.conf; entry <command>log level =</command>
-is synonymous with the entry <command>debuglevel =</command> that has been
-used in older versions of Samba and is being retained for backwards
+The &smb.conf; entry <parameter>log level</parameter>
+is synonymous with the parameter <parameter>debuglevel</parameter> that has
+been used in older versions of Samba and is being retained for backwards
compatibility of &smb.conf; files.
</para>
<para>
-As the <command>log level =</command> value is increased you will record
+As the <parameter>log level</parameter> value is increased you will record
a significantly increasing level of debugging information. For most
-debugging operations you may not need a setting higher than 3. Nearly
-all bugs can be tracked at a setting of 10, but be prepared for a VERY
-large volume of log data.
+debugging operations you may not need a setting higher than
+<constant>3</constant>. Nearly
+all bugs can be tracked at a setting of <constant>10</constant>, but be
+prepared for a VERY large volume of log data.
</para>
</sect1>
@@ -126,8 +127,8 @@ large volume of log data.
<title>Internal errors</title>
<para>
-If you get a "INTERNAL ERROR" message in your log files it means that
-Samba got an unexpected signal while running. It is probably a
+If you get a <errorname>INTERNAL ERROR</errorname> message in your log files
+it means that Samba got an unexpected signal while running. It is probably a
segmentation fault and almost certainly means a bug in Samba (unless
you have faulty hardware or system software).
</para>
@@ -151,17 +152,20 @@ files. This file is the most useful tool for tracking down the bug. To
use it you do this:
</para>
-<para><command>gdb smbd core</command></para>
+<screen>
+ <prompt>$ </prompt><userinput>gdb smbd core</userinput>
+</screen>
<para>
adding appropriate paths to smbd and core so gdb can find them. If you
-don't have gdb then try <userinput>dbx</userinput>. Then within the debugger use the
-command <userinput>where</userinput> to give a stack trace of where the problem
-occurred. Include this in your mail.
+don't have gdb then try <userinput>dbx</userinput>. Then within the debugger
+use the command <command>where</command> to give a stack trace of where the
+problem occurred. Include this in your report.
</para>
<para>
-If you know any assembly language then do a <userinput>disass</userinput> of the routine
+If you know any assembly language then do a
+<command>disass</command> of the routine
where the problem occurred (if its in a library routine then
disassemble the routine that called it) and try to work out exactly
where the problem is by looking at the surrounding code. Even if you
@@ -177,8 +181,10 @@ useful.
Unfortunately some unixes (in particular some recent linux kernels)
refuse to dump a core file if the task has changed uid (which smbd
does often). To debug with this sort of system you could try to attach
-to the running process using <userinput>gdb smbd <replaceable>PID</replaceable></userinput> where you get <replaceable>PID</replaceable> from
-<application>smbstatus</application>. Then use <userinput>c</userinput> to continue and try to cause the core dump
+to the running process using
+<userinput>gdb smbd <replaceable>PID</replaceable></userinput> where you get
+<replaceable>PID</replaceable> from <application>smbstatus</application>.
+Then use <command>c</command> to continue and try to cause the core dump
using the client. The debugger should catch the fault and tell you
where it occurred.
</para>
@@ -198,4 +204,3 @@ exactly what version you used.
</sect1>
</chapter>
-
diff --git a/docs/docbook/projdoc/Compiling.xml b/docs/docbook/projdoc/Compiling.xml
index 9638663dde..fb59dead02 100644
--- a/docs/docbook/projdoc/Compiling.xml
+++ b/docs/docbook/projdoc/Compiling.xml
@@ -7,7 +7,7 @@
</author>
&author.jelmer;
- <pubdate> (22 May 2001) </pubdate>
+ <pubdate> 22 May 2001 </pubdate>
<pubdate> 18 March 2003 </pubdate>
</chapterinfo>
@@ -45,8 +45,8 @@ This chapter is a modified version of the instructions found at
<para>
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.
+including samba, rsync, distcc, ccache and jitterbug. There are two main ways
+of accessing the CVS server on this host.
</para>
<sect3>
@@ -80,11 +80,12 @@ just a casual browser.
<para>
To download the latest cvs source code, point your
-browser at the URL : <ulink url="http://www.cyclic.com/">http://www.cyclic.com/</ulink>.
+browser at the URL :
+<ulink url="http://www.cyclic.com/">http://www.cyclic.com/</ulink>.
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.
+Links to theses clients are also available from the Cyclic website.
</para>
<para>
@@ -94,16 +95,17 @@ samba source code. For the other source code repositories
on this system just substitute the correct package name
</para>
-<orderedlist>
-<listitem>
+<procedure>
+ <title>Retrieving samba using CVS</title>
+
+ <step>
<para>
Install a recent copy of cvs. All you really need is a
copy of the cvs client binary.
</para>
-</listitem>
-
+ </step>
-<listitem>
+ <step>
<para>
Run the command
</para>
@@ -111,14 +113,16 @@ on this system just substitute the correct package name
<para>
<userinput>cvs -d :pserver:cvs@samba.org:/cvsroot login</userinput>
</para>
+ </step>
+
+ <step>
<para>
When it asks you for a password type <userinput>cvs</userinput>.
</para>
-</listitem>
+ </step>
-
-<listitem>
+ <step>
<para>
Run the command
</para>
@@ -134,18 +138,19 @@ on this system just substitute the correct package name
</para>
<para>
- CVS branches other then HEAD can be obtained by using the <parameter>-r</parameter>
- 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 userinput.
+ CVS branches other then HEAD can be obtained by using the
+ <option>-r</option> 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 3.0 release code. This could be done by
+ using the following userinput.
</para>
<para>
- <userinput>cvs -d :pserver:cvs@samba.org:/cvsroot co -r SAMBA_2_2 samba</userinput>
+ <userinput>cvs -d :pserver:cvs@samba.org:/cvsroot co -r SAMBA_3_0 samba</userinput>
</para>
-</listitem>
+ </step>
-<listitem>
+ <step>
<para>
Whenever you want to merge in the latest code changes use
the following command from within the samba directory:
@@ -154,8 +159,8 @@ on this system just substitute the correct package name
<para>
<userinput>cvs update -d -P</userinput>
</para>
-</listitem>
-</orderedlist>
+ </step>
+</procedure>
</sect3>
</sect2>
@@ -166,16 +171,16 @@ on this system just substitute the correct package name
<title>Accessing the samba sources via rsync and ftp</title>
<para>
- pserver.samba.org also exports unpacked copies of most parts of the CVS tree at <ulink url="ftp://pserver.samba.org/pub/unpacked">ftp://pserver.samba.org/pub/unpacked</ulink> and also via anonymous rsync at rsync://pserver.samba.org/ftp/unpacked/. I recommend using rsync rather than ftp.
+ pserver.samba.org also exports unpacked copies of most parts of the CVS
+ tree at <ulink url="ftp://pserver.samba.org/pub/unpacked">ftp://pserver.samba.org/pub/unpacked</ulink> and also via anonymous rsync at
+ <ulink url="rsync://pserver.samba.org/ftp/unpacked/">rsync://pserver.samba.org/ftp/unpacked/</ulink>. I recommend using rsync rather than ftp.
See <ulink url="http://rsync.samba.org/">the rsync homepage</ulink> for more info on rsync.
</para>
<para>
- The disadvantage of the unpacked trees
- is that they do not support automatic
- merging of local changes like CVS does.
- rsync access is most convenient for an
- initial install.
+ The disadvantage of the unpacked trees is that they do not support automatic
+ merging of local changes like CVS does. rsync access is most convenient
+ for an initial install.
</para>
</sect1>
@@ -183,11 +188,10 @@ on this system just substitute the correct package name
<title>Verifying Samba's PGP signature</title>
<para>
-In these days of insecurity, it's strongly recommended that you verify the PGP signature for any
-source file before installing it. According to Jerry Carter of the Samba Team, only about 22% of
-all Samba downloads have had a corresponding PGP signature download (a very low percentage, which
-should be considered a bad thing). Even if you're not downloading from a mirror site, verifying PGP
-signatures should be a standard reflex.
+In these days of insecurity, it's strongly recommended that you verify the PGP
+signature for any source file before installing it. Even if you're not
+downloading from a mirror site, verifying PGP signatures should be a
+standard reflex.
</para>
@@ -195,38 +199,39 @@ signatures should be a standard reflex.
With that said, go ahead and download the following files:
</para>
-<para><programlisting>
- $ wget http://us1.samba.org/samba/ftp/samba-2.2.8a.tar.asc
- $ wget http://us1.samba.org/samba/ftp/samba-pubkey.asc
-</programlisting></para>
+<para><screen>
+<prompt>$ </prompt><userinput> wget http://us1.samba.org/samba/ftp/samba-2.2.8a.tar.asc</userinput>
+<prompt>$ </prompt><userinput> wget http://us1.samba.org/samba/ftp/samba-pubkey.asc</userinput>
+</screen></para>
<para>
The first file is the PGP signature for the Samba source file; the other is the Samba public
PGP key itself. Import the public PGP key with:
</para>
-<programlisting>
- $ gpg --import samba-pubkey.asc
-</programlisting>
+<screen>
+ <prompt>$ </prompt><userinput>gpg --import samba-pubkey.asc</userinput>
+</screen>
<para>
And verify the Samba source code integrity with:
</para>
-<programlisting>
- $ gzip -d samba-2.2.8a.tar.gz
- $ gpg --verify samba-2.2.8a.tar.asc
-</programlisting>
+<screen>
+ <prompt>$ </prompt><userinput>gzip -d samba-2.2.8a.tar.gz</userinput>
+ <prompt>$ </prompt><userinput>gpg --verify samba-2.2.8a.tar.asc</userinput>
+</screen>
<para>
-If you receive a message like, "Good signature from Samba Distribution Verification Key..."
-then all is well. The warnings about trust relationships can be ignored. An example of what
-you would not want to see would be:
+If you receive a message like, "Good signature from Samba Distribution
+Verification Key..."
+then all is well. The warnings about trust relationships can be ignored. An
+example of what you would not want to see would be:
</para>
-<programlisting>
+<computeroutput>
gpg: BAD signature from "Samba Distribution Verification Key"
-</programlisting>
+</computeroutput>
</sect1>
@@ -288,28 +293,31 @@ you would not want to see would be:
</itemizedlist>
<para>If your kerberos libraries are in a non-standard location then
- remember to add the configure option --with-krb5=DIR.</para>
+ remember to add the configure option
+ <option>--with-krb5=<replaceable>DIR</replaceable></option>.</para>
- <para>After you run configure make sure that <filename>include/config.h</filename> it generates contains lines like this:</para>
+ <para>After you run configure make sure that
+ <filename>include/config.h</filename> it generates contains lines like
+ this:</para>
- <para><programlisting>
+<para><programlisting>
#define HAVE_KRB5 1
#define HAVE_LDAP 1
</programlisting></para>
- <para>If it doesn't then configure did not find your krb5 libraries or
- your ldap libraries. Look in config.log to figure out why and fix
- it.</para>
+ <para>If it doesn't then configure did not find your krb5 libraries or
+ your ldap libraries. Look in <filename>config.log</filename> to figure
+ out why and fix it.</para>
<sect3>
<title>Installing the required packages for Debian</title>
<para>On Debian you need to install the following packages:</para>
<para>
- <itemizedlist>
- <listitem>libkrb5-dev</listitem>
- <listitem>krb5-user</listitem>
- </itemizedlist>
+ <simplelist>
+ <member>libkrb5-dev</member>
+ <member>krb5-user</member>
+ </simplelist>
</para>
</sect3>
@@ -318,11 +326,11 @@ you would not want to see would be:
<para>On RedHat this means you should have at least: </para>
<para>
- <itemizedlist>
- <listitem>krb5-workstation (for kinit)</listitem>
- <listitem>krb5-libs (for linking with)</listitem>
- <listitem>krb5-devel (because you are compiling from source)</listitem>
- </itemizedlist>
+ <simplelist>
+ <member>krb5-workstation (for kinit)</member>
+ <member>krb5-libs (for linking with)</member>
+ <member>krb5-devel (because you are compiling from source)</member>
+ </simplelist>
</para>
<para>in addition to the standard development environment.</para>
@@ -337,9 +345,9 @@ you would not want to see would be:
</sect1>
<sect1>
- <title>Starting the smbd and nmbd</title>
+ <title>Starting the &smbd; and &nmbd;</title>
- <para>You must choose to start smbd and nmbd either
+ <para>You must choose to start &smbd; and &nmbd; either
as daemons or from <application>inetd</application>Don't try
to do both! Either you can put them in <filename>
inetd.conf</filename> and have them started on demand
@@ -350,26 +358,28 @@ you would not want to see would be:
the bit about what user you need to be in order to start
Samba. In many cases you must be root.</para>
- <para>The main advantage of starting <application>smbd</application>
- and <application>nmbd</application> using the recommended daemon method
+ <para>The main advantage of starting &smbd;
+ and &nmbd; using the recommended daemon method
is that they will respond slightly more quickly to an initial connection
request.</para>
<sect2>
<title>Starting from inetd.conf</title>
- <para>NOTE; The following will be different if
+ <note>
+ <para>The following will be different if
you use NIS, NIS+ or LDAP to distribute services maps.</para>
+ </note>
<para>Look at your <filename>/etc/services</filename>.
What is defined at port 139/tcp. If nothing is defined
then add a line like this:</para>
- <para><userinput>netbios-ssn 139/tcp</userinput></para>
+ <para><programlisting>netbios-ssn 139/tcp</programlisting></para>
<para>similarly for 137/udp you should have an entry like:</para>
- <para><userinput>netbios-ns 137/udp</userinput></para>
+ <para><programlisting>netbios-ns 137/udp</programlisting></para>
<para>Next edit your <filename>/etc/inetd.conf</filename>
and add two lines something like this:</para>
@@ -386,11 +396,13 @@ you would not want to see would be:
<note><para>Some unixes already have entries like netbios_ns
(note the underscore) in <filename>/etc/services</filename>.
You must either edit <filename>/etc/services</filename> or
- <filename>/etc/inetd.conf</filename> to make them consistent.</para></note>
+ <filename>/etc/inetd.conf</filename> to make them consistent.
+ </para></note>
<note><para>On many systems you may need to use the
- <command>interfaces</command> option in &smb.conf; to specify the IP address
- and netmask of your interfaces. Run <application>ifconfig</application>
+ <parameter>interfaces</parameter> option in &smb.conf; to specify the IP
+ address and netmask of your interfaces. Run
+ <application>ifconfig</application>
as root if you don't know what the broadcast is for your
net. &nmbd; tries to determine it at run
time, but fails on some unixes.
@@ -402,9 +414,9 @@ you would not want to see would be:
arguments, or you should use a script, and start the script
from <command>inetd</command>.</para></warning>
- <para>Restart <command>inetd</command>, perhaps just send
- it a HUP. If you have installed an earlier version of <application>
- nmbd</application> then you may need to kill nmbd as well.</para>
+ <para>Restart <application>inetd</application>, perhaps just send
+ it a HUP. If you have installed an earlier version of &nmbd; then
+ you may need to kill &nmbd; as well.</para>
</sect2>
<sect2>
@@ -428,7 +440,7 @@ you would not want to see would be:
</para>
<para>To kill it send a kill signal to the processes
- <command>nmbd</command> and <command>smbd</command>.</para>
+ &nmbd; and &smbd;.</para>
<note><para>If you use the SVR4 style init system then
you may like to look at the <filename>examples/svr4-startup</filename>
diff --git a/docs/docbook/projdoc/DOMAIN_MEMBER.xml b/docs/docbook/projdoc/DOMAIN_MEMBER.xml
index ecb8a3afb3..bb8e95b8a9 100644
--- a/docs/docbook/projdoc/DOMAIN_MEMBER.xml
+++ b/docs/docbook/projdoc/DOMAIN_MEMBER.xml
@@ -4,40 +4,48 @@
&author.jht;
&author.jeremy;
&author.jerry;
+
+<!-- Authors of the ADS-HOWTO -->
+ &author.tridge;
+ &author.jelmer;
</chapterinfo>
<title>Domain Membership</title>
<para>
-Domain Membership is a subject of vital concern, Samba must be able to participate
-as a member server in a Microsoft Domain security context, and Samba must be capable of
-providing Domain machine member trust accounts, otherwise it would not be capable of offering
-a viable option for many users.
+Domain Membership is a subject of vital concern, Samba must be able to
+participate as a member server in a Microsoft Domain security context, and
+Samba must be capable of providing Domain machine member trust accounts,
+otherwise it would not be capable of offering a viable option for many users.
</para>
<para>
-This chapter covers background information pertaining to domain membership, Samba
-configuration for it, and MS Windows client procedures for joining a domain. Why is
-this necessary? Because both are areas in which there exists within the current MS
-Windows networking world and particularly in the Unix/Linux networking and administration
-world, a considerable level of mis-information, incorrect understanding, and a lack of
-knowledge. Hopefully this chapter will fill the voids.
+This chapter covers background information pertaining to domain membership,
+Samba configuration for it, and MS Windows client procedures for joining a
+domain. Why is this necessary? Because both are areas in which there exists
+within the current MS Windows networking world and particularly in the
+Unix/Linux networking and administration world, a considerable level of
+mis-information, incorrect understanding, and a lack of knowledge. Hopefully
+this chapter will fill the voids.
</para>
<sect1>
<title>Features and Benefits</title>
<para>
-MS Windows workstations and servers that want to participate in domain security need to
+MS Windows workstations and servers that want to participate in domain
+security need to
be made Domain members. Participating in Domain security is often called
-<emphasis>Single Sign On</emphasis> or SSO for short. This chapter describes the process
-that must be followed to make a workstation (or another server - be it an MS Windows NT4 / 200x
+<emphasis>Single Sign On</emphasis> or <acronym>SSO</acronym> for short. This
+chapter describes the process that must be followed to make a workstation
+(or another server - be it an <application>MS Windows NT4 / 200x</application>
server) or a Samba server a member of an MS Windows Domain security context.
</para>
<para>
-Samba-3 can join an MS Windows NT4 style domain as a native member server, an MS Windows
-Active Directory Domain as a native member server, or a Samba Domain Control network.
+Samba-3 can join an MS Windows NT4 style domain as a native member server, an
+MS Windows Active Directory Domain as a native member server, or a Samba Domain
+Control network.
</para>
<para>
@@ -50,19 +58,21 @@ Domain membership has many advantages:
</para></listitem>
<listitem><para>
- Domain user access rights and file ownership / access controls can be set from
- the single Domain SAM (Security Accounts Management) database (works with Domain member
- servers as well as with MS Windows workstations that are domain members)
+ Domain user access rights and file ownership / access controls can be set
+ from the single Domain SAM (Security Accounts Management) database
+ (works with Domain member servers as well as with MS Windows workstations
+ that are domain members)
</para></listitem>
<listitem><para>
- Only MS Windows NT4 / 200x / XP Professional workstations that are Domain members
+ Only <application>MS Windows NT4 / 200x / XP Professional</application>
+ workstations that are Domain members
can use network logon facilities
</para></listitem>
<listitem><para>
- Domain Member workstations can be better controlled through the use of Policy files
- (NTConfig.POL) and Desktop Profiles.
+ Domain Member workstations can be better controlled through the use of
+ Policy files (<filename>NTConfig.POL</filename>) and Desktop Profiles.
</para></listitem>
<listitem><para>
@@ -71,10 +81,11 @@ Domain membership has many advantages:
</para></listitem>
<listitem><para>
- Network administrators gain better application and user access management abilities
- because there is no need to maintain user accounts on any network client or server,
- other than the central Domain database (either NT4/Samba SAM style Domain, NT4 Domain
- that is back ended with an LDAP directory, or via an Active Directory infrastructure)
+ Network administrators gain better application and user access management
+ abilities because there is no need to maintain user accounts on any network
+ client or server, other than the central Domain database
+ (either NT4/Samba SAM style Domain, NT4 Domain that is back ended with an
+ LDAP directory, or via an Active Directory infrastructure)
</para></listitem>
</itemizedlist>
@@ -84,7 +95,8 @@ Domain membership has many advantages:
<title>MS Windows Workstation/Server Machine Trust Accounts</title>
<para>
-A machine trust account is an account that is used to authenticate a client machine
+A machine trust account is an account that is used to authenticate a client
+machine
(rather than a user) to the Domain Controller server. In Windows terminology,
this is known as a "Computer Account."
</para>
@@ -113,10 +125,10 @@ as follows:
<itemizedlist>
<listitem><para>
- A Domain Security Account (stored in the <emphasis>passdb backend</emphasis>
- that has been configured in the &smb.conf; file. The precise nature of the
- account information that is stored depends on the type of backend database
- that has been chosen.
+ A Domain Security Account (stored in the
+ <parameter>passdb backend</parameter> that has been configured in the
+ &smb.conf; file. The precise nature of the account information that is
+ stored depends on the type of backend database that has been chosen.
</para>
<para>
@@ -127,15 +139,17 @@ as follows:
</para>
<para>
- The two newer database types are called <emphasis>ldapsam, tdbsam</emphasis>.
- Both store considerably more data than the older <filename>smbpasswd</filename>
- file did. The extra information enables new user account controls to be used.
+ The two newer database types are called <emphasis>ldapsam</emphasis>,
+ <emphasis>tdbsam</emphasis>. Both store considerably more data than the
+ older <filename>smbpasswd</filename> file did. The extra information
+ enables new user account controls to be used.
</para></listitem>
<listitem><para>
- A corresponding Unix account, typically stored in <filename>/etc/passwd</filename>.
- Work is in progress to allow a simplified mode of operation that does not require
- Unix user accounts, but this may not be a feature of the early releases of Samba-3.
+ A corresponding Unix account, typically stored in
+ <filename>/etc/passwd</filename>. Work is in progress to allow a
+ simplified mode of operation that does not require Unix user accounts, but
+ this may not be a feature of the early releases of Samba-3.
</para></listitem>
</itemizedlist>
</para>
@@ -146,20 +160,22 @@ There are three ways to create machine trust accounts:
<itemizedlist>
<listitem><para>
- Manual creation from the Unix/Linux command line. Here, both the Samba and corresponding
- Unix account are created by hand.
+ Manual creation from the Unix/Linux command line. Here, both the Samba and
+ corresponding Unix account are created by hand.
</para></listitem>
<listitem><para>
- Using the MS Windows NT4 Server Manager (either from an NT4 Domain member server, or using
- the Nexus toolkit available from the Microsoft web site. This tool can be run from any
- MS Windows machine so long as the user is logged on as the administrator account.
+ Using the MS Windows NT4 Server Manager (either from an NT4 Domain member
+ server, or using the Nexus toolkit available from the Microsoft web site.
+ This tool can be run from any MS Windows machine so long as the user is
+ logged on as the administrator account.
</para></listitem>
<listitem><para>
- "On-the-fly" creation. The Samba machine trust account is automatically created by
- Samba at the time the client is joined to the domain. (For security, this is the
- recommended method.) The corresponding Unix account may be created automatically or manually.
+ "On-the-fly" creation. The Samba machine trust account is automatically
+ created by Samba at the time the client is joined to the domain.
+ (For security, this is the recommended method.) The corresponding Unix
+ account may be created automatically or manually.
</para></listitem>
</itemizedlist>
@@ -167,26 +183,26 @@ There are three ways to create machine trust accounts:
<title>Manual Creation of Machine Trust Accounts</title>
<para>
-The first step in manually creating a machine trust account is to manually create the
-corresponding Unix account in <filename>/etc/passwd</filename>. This can be done using
-<command>vipw</command> or other 'add user' command that is normally used to create new
-Unix accounts. The following is an example for a Linux based Samba server:
+The first step in manually creating a machine trust account is to manually
+create the corresponding Unix account in <filename>/etc/passwd</filename>.
+This can be done using <command>vipw</command> or another 'add user' command
+that is normally used to create new Unix accounts. The following is an example for a Linux based Samba server:
</para>
<para>
-<prompt>root# </prompt><command>/usr/sbin/useradd -g 100 -d /dev/null -c <replaceable>"machine nickname"</replaceable> -s /bin/false <replaceable>machine_name</replaceable>$ </command>
+<prompt>root# </prompt><userinput>/usr/sbin/useradd -g 100 -d /dev/null -c <replaceable>"machine nickname"</replaceable> -s /bin/false <replaceable>machine_name</replaceable>$ </userinput>
</para>
<para>
-<prompt>root# </prompt><command>passwd -l <replaceable>machine_name</replaceable>$</command>
+<prompt>root# </prompt><userinput>passwd -l <replaceable>machine_name</replaceable>$</userinput>
</para>
<para>
-On *BSD systems, this can be done using the 'chpass' utility:
+On *BSD systems, this can be done using the <command>chpass</command> utility:
</para>
<para>
-<prompt>root# </prompt><command>chpass -a "<replaceable>machine_name</replaceable>$:*:101:100::0:0:Workstation <replaceable>machine_name</replaceable>:/dev/null:/sbin/nologin"</command>
+<prompt>root# </prompt><userinput>chpass -a "<replaceable>machine_name</replaceable>$:*:101:100::0:0:Workstation <replaceable>machine_name</replaceable>:/dev/null:/sbin/nologin"</userinput>
</para>
<para>
@@ -235,11 +251,11 @@ the corresponding Unix account.
<para>
Manually creating a machine trust account using this method is the
equivalent of creating a machine trust account on a Windows NT PDC using
- the "Server Manager". From the time at which the account is created
- to the time which the client joins the domain and changes the password,
- your domain is vulnerable to an intruder joining your domain using
- a machine with the same NetBIOS name. A PDC inherently trusts
- members of the domain and will serve out a large degree of user
+ the <application>Server Manager</application>. From the time at which the
+ account is created to the time which the client joins the domain and
+ changes the password, your domain is vulnerable to an intruder joining
+ your domain using a machine with the same NetBIOS name. A PDC inherently
+ trusts members of the domain and will serve out a large degree of user
information to such clients. You have been warned!
</para>
</warning>
@@ -249,16 +265,19 @@ the corresponding Unix account.
<title>Using NT4 Server Manager to Add Machine Accounts to the Domain</title>
<para>
-If the machine from which you are trying to manage the domain is an MS Windows NT4 workstation
-then the tool of choice is the package called SRVTOOLS.EXE. When executed in the target directory
-this will unpack SrvMge.exe and UsrMgr.exe (both are Domain Management tools for MS Windows NT4
-workstation.
+If the machine from which you are trying to manage the domain is an
+<application>MS Windows NT4 workstation</application>
+then the tool of choice is the package called <command>SRVTOOLS.EXE</command>.
+When executed in the target directory this will unpack
+<command>SrvMge.exe</command> and <command>UsrMgr.exe</command> (both are
+Domain Management tools for MS Windows NT4 workstation.
</para>
<para>
-If your workstation is any other MS Windows product you should download the Nexus.exe package
-from the Microsoft web site. When executed from the target directory this will unpack the same
-tools but for use on MS Windows 9x/Me/200x/XP.
+If your workstation is any other MS Windows product you should download the
+<command>Nexus.exe</command> package from the Microsoft web site. When executed
+from the target directory this will unpack the same tools but for use on
+<application>MS Windows 9x/Me/200x/XP</application>.
</para>
<para>
@@ -268,29 +287,32 @@ Launch the <command>srvmgr.exe</command> (Server Manager for Domains) and follow
<procedure>
<title>Server Manager Account Machine Account Management</title>
<step><para>
- From the menu select Computer
+ From the menu select <guimenu>Computer</guimenu>
</para></step>
<step><para>
- Click on "Select Domain"
+ Click on <guimenuitem>Select Domain</guimenuitem>
</para></step>
<step><para>
- Click on the name of the domain you wish to administer in the "Select Domain" panel
- and then Click OK.
+ Click on the name of the domain you wish to administer in the
+ <guilabel>Select Domain</guilabel> panel and then click
+ <guibutton>OK</guibutton>.
</para></step>
<step><para>
- Again from the menu select Computer
+ Again from the menu select <guimenu>Computer</guimenu>
</para></step>
<step><para>
- Select "Add to Domain"
+ Select <guimenuitem>Add to Domain</guimenuitem>
</para></step>
<step><para>
- In the dialog box, click on the radio button to "Add NT Workstation of Server", then
- enter the machine name in the field provided, then Click the "Add" button.
+ In the dialog box, click on the radio button to
+ <guilabel>Add NT Workstation of Server</guilabel>, then
+ enter the machine name in the field provided, then click the
+ <guibutton>Add</guibutton> button.
</para></step>
</procedure>
@@ -334,8 +356,8 @@ The procedure for making an MS Windows workstation of server a member of the dom
with the version of Windows:
</para>
-<itemizedlist>
- <listitem><para><emphasis>Windows 200x XP Professional</emphasis></para>
+<sect3>
+ <title>Windows 200x XP Professional</title>
<para>
When the user elects to make the client a domain member, Windows 200x prompts for
@@ -363,9 +385,11 @@ with the version of Windows:
encryption key for setting the password of the machine trust
account. The machine trust account will be created on-the-fly, or
updated if it already exists.
- </para></listitem>
+ </para>
+</sect3>
- <listitem><para><emphasis>Windows NT4</emphasis></para>
+<sect3>
+ <title>Windows NT4</title>
<para>
If the machine trust account was created manually, on the
@@ -382,13 +406,16 @@ with the version of Windows:
this case, joining the domain proceeds as above for Windows 2000
(i.e., you must supply a Samba administrative account when
prompted).
- </para></listitem>
+ </para>
+</sect3>
+
+<sect3>
+ <title>Samba</title>
- <listitem><para><emphasis>Samba</emphasis></para>
<para>Joining a samba client to a domain is documented in
the <link linkend="domain-member">Domain Member</link> chapter.
- </para></listitem>
-</itemizedlist>
+ </para>
+</sect3>
</sect2>
</sect1>
@@ -398,38 +425,41 @@ with the version of Windows:
<para>
This mode of server operation involves the samba machine being made a member
-of a domain security context. This means by definition that all user authentication
-will be done from a centrally defined authentication regime. The authentication
-regime may come from an NT3/4 style (old domain technology) server, or it may be
-provided from an Active Directory server (ADS) running on MS Windows 2000 or later.
+of a domain security context. This means by definition that all user
+authentication will be done from a centrally defined authentication regime.
+The authentication regime may come from an NT3/4 style (old domain technology)
+server, or it may be provided from an Active Directory server (ADS) running on
+MS Windows 2000 or later.
</para>
<para>
<emphasis>
-Of course it should be clear that the authentication back end itself could be from any
-distributed directory architecture server that is supported by Samba. This can be
-LDAP (from OpenLDAP), or Sun's iPlanet, of NetWare Directory Server, etc.
+Of course it should be clear that the authentication back end itself could be
+from any distributed directory architecture server that is supported by Samba.
+This can be LDAP (from OpenLDAP), or Sun's iPlanet, of NetWare Directory
+Server, etc.
</emphasis>
</para>
<para>
-Please refer to the section on Howto configure Samba as a Primary Domain Controller
-and for more information regarding how to create a domain machine account for a
-domain member server as well as for information regarding how to enable the samba
-domain member machine to join the domain and to be fully trusted by it.
+Please refer to the <link linkend="samba-pdc">Samba as a Primary Domain
+Controller chapter</link> for more information regarding how to create a domain
+machine account for a domain member server as well as for information
+regarding how to enable the samba domain member machine to join the domain and
+to be fully trusted by it.
</para>
<sect2>
<title>Joining an NT4 type Domain with Samba-3</title>
<para>
-<emphasis>Assumptions:</emphasis>
-<programlisting>
- NetBIOS name: SERV1
- Win2K/NT domain name: DOM
- Domain's PDC NetBIOS name: DOMPDC
- Domain's BDC NetBIOS names: DOMBDC1 and DOMBDC2
-</programlisting>
+Assumptions:
+<table><tbody>
+ <row><entry>NetBIOS name:</entry><entry>SERV1</entry></row>
+ <row><entry>Win2K/NT domain name:</entry><entry>DOM</entry></row>
+ <row><entry>Domain's PDC NetBIOS name:</entry><entry>DOMPDC</entry></row>
+ <row><entry>Domain's BDC NetBIOS names:</entry><entry>DOMBDC1 and DOMBDC2</entry></row>
+</tbody></table>
</para>
<para>
@@ -445,18 +475,19 @@ of your &smb.conf; to read:
<para>
<programlisting>
- <command>security = domain</command>
+security = domain
</programlisting>
</para>
<para>
Next change the <ulink url="smb.conf.5.html#WORKGROUP"><parameter>
-workgroup =</parameter></ulink> line in the [global] section to read:
+workgroup</parameter></ulink> line in the <parameter>[global]</parameter>
+section to read:
</para>
<para>
<programlisting>
- <command>workgroup = DOM</command>
+workgroup = DOM
</programlisting>
</para>
@@ -472,13 +503,13 @@ You must also have the parameter <ulink url="smb.conf.5.html#ENCRYPTPASSWORDS">
<para>
Finally, add (or modify) a <ulink url="smb.conf.5.html#PASSWORDSERVER">
-<parameter>password server =</parameter></ulink> line in the [global]
+<parameter>password server</parameter></ulink> line in the [global]
section to read:
</para>
<para>
<programlisting>
- <command>password server = DOMPDC DOMBDC1 DOMBDC2</command>
+password server = DOMPDC DOMBDC1 DOMBDC2
</programlisting>
</para>
@@ -498,7 +529,7 @@ set this line to be:
<para>
<programlisting>
- <command>password server = *</command>
+password server = *
</programlisting>
</para>
@@ -513,14 +544,14 @@ In order to actually join the domain, you must run this command:
</para>
<para>
-<programlisting>
- <prompt>root# </prompt><userinput>net join -S DOMPDC -U<replaceable>Administrator%password</replaceable></userinput>
-</programlisting>
+<screen>
+<prompt>root# </prompt><userinput>net join -S DOMPDC -U<replaceable>Administrator%password</replaceable></userinput>
+</screen>
</para>
<para>
-If the <userinput>-S DOMPDC</userinput> argument is not given then
-the domain name will be obtained from smb.conf.
+If the <option>-S DOMPDC</option> argument is not given then
+the domain name will be obtained from &smb.conf;.
</para>
<para>
@@ -573,7 +604,7 @@ clients to begin using domain security!
</sect2>
<sect2>
-<title>Why is this better than security = server?</title>
+<title>Why is this better than <parameter>security = server</parameter>?</title>
<para>
Currently, domain security in Samba doesn't free you from
@@ -604,11 +635,11 @@ domain PDC to an account domain PDC).
</para>
<para>
-In addition, with <command>security = server</command> every Samba
+In addition, with <parameter>security = server</parameter> every Samba
daemon on a server has to keep a connection open to the
authenticating server for as long as that daemon lasts. This can drain
the connection resources on a Microsoft NT server and cause it to run
-out of available connections. With <command>security = domain</command>,
+out of available connections. With <parameter>security = domain</parameter>,
however, the Samba daemons connect to the PDC/BDC only for as long
as is necessary to authenticate the user, and then drop the connection,
thus conserving PDC connection resources.
@@ -624,8 +655,8 @@ as the user SID, the list of NT groups the user belongs to, etc.
<note>
<para>
Much of the text of this document
-was first published in the Web magazine <ulink url="http://www.linuxworld.com">
-LinuxWorld</ulink> as the article <ulink
+was first published in the Web magazine
+<ulink url="http://www.linuxworld.com">LinuxWorld</ulink> as the article <ulink
url="http://www.linuxworld.com/linuxworld/lw-1998-10/lw-10-samba.html">Doing
the NIS/NT Samba</ulink>.
</para>
@@ -646,7 +677,7 @@ Windows2000 KDC.
<title>Setup your <filename>smb.conf</filename></title>
<para>
-You must use at least the following 3 options in smb.conf:
+You must use at least the following 3 options in &smb.conf;:
</para>
<para><programlisting>
@@ -657,17 +688,18 @@ You must use at least the following 3 options in smb.conf:
<para>
In case samba can't figure out your ads server using your realm name, use the
-<command>ads server</command> option in <filename>smb.conf</filename>:
+<parameter>ads server</parameter> option in <filename>smb.conf</filename>:
<programlisting>
ads server = your.kerberos.server
</programlisting>
</para>
<note><para>
-You do *not* need a smbpasswd file, and older clients will be authenticated as if
-<command>security = domain</command>, although it won't do any harm and allows you
-to have local users not in the domain. I expect that the above required options will
-change soon when we get better active directory integration.
+You do &not; need a smbpasswd file, and older clients will be authenticated as
+if <parameter>security = domain</parameter>, although it won't do any harm and
+allows you to have local users not in the domain. It is expected that the above
+required options will change soon when active directory integration will get
+better.
</para></note>
</sect2>
@@ -676,10 +708,6 @@ change soon when we get better active directory integration.
<title>Setup your <filename>/etc/krb5.conf</filename></title>
<para>
-Note: you will need the krb5 workstation, devel, and libs installed
-</para>
-
-<para>
The minimal configuration for <filename>krb5.conf</filename> is:
</para>
@@ -697,8 +725,8 @@ making sure that your password is accepted by the Win2000 KDC.
</para>
<note><para>
-The realm must be uppercase or you will get "Cannot find KDC for requested
-realm while getting initial credentials" error
+The realm must be uppercase or you will get <errorname>Cannot find KDC for
+requested realm while getting initial credentials</errorname> error
</para></note>
<note><para>
@@ -748,7 +776,7 @@ As a user that has write permission on the Samba private directory
<para>
<variablelist>
- <varlistentry><term>"ADS support not compiled in"</term>
+ <varlistentry><term>ADS support not compiled in</term>
<listitem><para>Samba must be reconfigured (remove config.cache) and recompiled
(make clean all install) after the kerberos libs and headers are installed.
</para></listitem></varlistentry>
diff --git a/docs/docbook/projdoc/passdb.xml b/docs/docbook/projdoc/passdb.xml
index 78aee30448..419dd51335 100644
--- a/docs/docbook/projdoc/passdb.xml
+++ b/docs/docbook/projdoc/passdb.xml
@@ -208,9 +208,9 @@ Samba-3 introduces the following new password backend capabilities:
In addition to differently encrypted passwords, windows also stores certain data for each
user that is not stored in a unix user database. e.g: workstations the user may logon from,
the location where the users' profile is stored, and so on. Samba retrieves and stores this
- information using a "passdb backend". Commonly available backends are LDAP, plain text
+ information using a <parameter>passdb backend</parameter>. Commonly available backends are LDAP, plain text
file, MySQL and nisplus. For more information, see the man page for &smb.conf; regarding the
- <command>passdb backend = </command> parameter.
+ <parameter>passdb backend</parameter> parameter.
</para>
<sect2>
@@ -346,6 +346,32 @@ Samba-3 introduces the following new password backend capabilities:
</itemizedlist>
</sect3>
</sect2>
+
+ <sect2>
+ <title>Mapping User Identifiers between MS Windows and Unix</title>
+
+ <para>
+ Every operation in Unix/Linux requires a user identifier (UID), just as in
+ MS Windows NT4 / 200x this requires a Security Identifier (SID). Samba provides
+ two means for mapping an MS Windows user to a Unix/Linux UID.
+ </para>
+
+ <para>
+ Firstly, all Samba SAM (Security Account Management database) accounts require
+ a Unix/Linux UID that the account will map to. As users are added to the account
+ information database samba-3 will call the <command>add user script</command>
+ interface to add the account to the Samba host OS. In essence all accounts in
+ the local SAM require a local user account.
+ </para>
+
+ <para>
+ The second way to affect Windows SID to Unix UID mapping is via the
+ <emphasis>idmap uid, idmap gid</emphasis> parameters in &smb.conf;.
+ Please refer to the man page for information about these parameters.
+ These parameters are essential when mapping users from a remote SAM server.
+ </para>
+
+ </sect2>
</sect1>
<sect1>
@@ -687,7 +713,7 @@ In smb.conf [globals]
The LDAP ldapsam code has been developed and tested using the OpenLDAP 2.0 and 2.1 server and
client libraries. The same code should work with Netscape's Directory Server and client SDK.
However, there are bound to be compile errors and bugs. These should not be hard to fix.
- Please submit fixes via <link linkend="bugreport"/>.
+ Please submit fixes via <link linkend="bugreport">Bug reporting facility</link>.
</para>
</sect3>
@@ -756,9 +782,9 @@ objectclass ( 1.3.6.1.4.1.7165.2.2.3 NAME 'sambaAccount' SUP top AUXILIARY
</para>
<para>
-<programlisting>
-<prompt>root# </prompt><userinput>cp samba.schema /etc/openldap/schema/</userinput>
-</programlisting>
+<screen>
+&rootprompt;<userinput>cp samba.schema /etc/openldap/schema/</userinput>
+</screen>
</para>
<para>
@@ -792,7 +818,7 @@ include /etc/openldap/schema/nis.schema
</para>
<para>
-<programlisting>
+<screen>
# Indices to maintain
## required by OpenLDAP
index objectclass eq
@@ -810,12 +836,11 @@ index displayName pres,sub,eq
##index gidNumber eq
##index memberUid eq
-index rid eq
index sambaSID eq
index sambaPrimaryGroupSID eq
index sambaDomainName eq
index default sub
-</programlisting>
+</screen>
</para>
<para>
@@ -823,9 +848,9 @@ index default sub
</para>
<para>
-<programlisting>
+<screen>
./sbin/slapindex -f slapd.conf
-</programlisting>
+</screen>
</para>
<para>
@@ -833,9 +858,9 @@ index default sub
</para>
<para>
-<programlisting>
-<prompt>root# </prompt><userinput>/etc/init.d/slapd restart</userinput>
-</programlisting>
+<screen>
+&rootprompt;<userinput>/etc/init.d/slapd restart</userinput>
+</screen>
</para>
</sect3>
@@ -844,14 +869,13 @@ index default sub
<title>Configuring Samba</title>
<para>
- The following parameters are available in smb.conf only with <parameter>--with-ldapsam</parameter>
- was included when compiling Samba. The following parameters are available in smb.conf only if your
+ The following parameters are available in smb.conf only if your
version of samba was built with LDAP support. Samba automatically builds with LDAP support if the
LDAP libraries are found.
</para>
<itemizedlist>
- <listitem><para><ulink url="smb.conf.5.html#PASSDBBACKEND">passdb backend ldapsam:url</ulink></para></listitem>
+ <listitem><para><ulink url="smb.conf.5.html#PASSDBBACKEND">passdb backend = ldapsam:url</ulink></para></listitem>
<listitem><para><ulink url="smb.conf.5.html#LDAPSSL">ldap ssl</ulink></para></listitem>
<listitem><para><ulink url="smb.conf.5.html#LDAPADMINDN">ldap admin dn</ulink></para></listitem>
<listitem><para><ulink url="smb.conf.5.html#LDAPSUFFIX">ldap suffix</ulink></para></listitem>
@@ -870,51 +894,51 @@ index default sub
use with an LDAP directory could appear as
</para>
- <para>
- <programlisting>
- ## /usr/local/samba/lib/smb.conf
- [global]
- security = user
- encrypt passwords = yes
+<para>
+<screen>
+## /usr/local/samba/lib/smb.conf
+[global]
+ security = user
+ encrypt passwords = yes
- netbios name = TASHTEGO
- workgroup = NARNIA
+ netbios name = TASHTEGO
+ workgroup = NARNIA
- # ldap related parameters
+ # ldap related parameters
- # define the DN to use when binding to the directory servers
- # The password for this DN is not stored in smb.conf. Rather it
- # must be set by using 'smbpasswd -w <replaceable>secretpw</replaceable>' to store the
- # passphrase in the secrets.tdb file. If the "ldap admin dn" values
- # change, this password will need to be reset.
- ldap admin dn = "cn=Samba Manager,ou=people,dc=samba,dc=org"
+ # define the DN to use when binding to the directory servers
+ # The password for this DN is not stored in smb.conf. Rather it
+ # must be set by using 'smbpasswd -w <replaceable>secretpw</replaceable>' to store the
+ # passphrase in the secrets.tdb file. If the "ldap admin dn" values
+ # change, this password will need to be reset.
+ ldap admin dn = "cn=Samba Manager,ou=people,dc=samba,dc=org"
- # Define the SSL option when connecting to the directory
- # ('off', 'start tls', or 'on' (default))
- ldap ssl = start tls
+ # Define the SSL option when connecting to the directory
+ # ('off', 'start tls', or 'on' (default))
+ ldap ssl = start tls
- # syntax: passdb backend = ldapsam:ldap://server-name[:port]
- passdb backend ldapsam:ldap://funball.samba.org
+ # syntax: passdb backend = ldapsam:ldap://server-name[:port]
+ passdb backend = ldapsam:ldap://funball.samba.org, guest
- # smbpasswd -x delete the entire dn-entry
- ldap delete dn = no
+ # smbpasswd -x delete the entire dn-entry
+ ldap delete dn = no
- # the machine and user suffix added to the base suffix
- # wrote WITHOUT quotes. NULL siffixes by default
- ldap user suffix = ou=People
- ldap machine suffix = ou=Systems
+ # the machine and user suffix added to the base suffix
+ # wrote WITHOUT quotes. NULL siffixes by default
+ ldap user suffix = ou=People
+ ldap machine suffix = ou=Systems
- # Trust unix account information in LDAP
- # (see the smb.conf manpage for details)
- ldap trust ids = Yes
+ # Trust unix account information in LDAP
+ # (see the smb.conf manpage for details)
+ ldap trust ids = Yes
- # specify the base DN to use when searching the directory
- ldap suffix = "ou=people,dc=samba,dc=org"
+ # specify the base DN to use when searching the directory
+ ldap suffix = "ou=people,dc=samba,dc=org"
- # generally the default ldap search filter is ok
- # ldap filter = "(&amp;(uid=%u)(objectclass=sambaAccount))"
- </programlisting>
- </para>
+ # generally the default ldap search filter is ok
+ # ldap filter = "(&amp;(uid=%u)(objectclass=sambaAccount))"
+</screen>
+</para>
</sect3>
@@ -929,7 +953,7 @@ index default sub
<para>
Machines accounts are managed with the sambaAccount objectclass, just
like users accounts. However, it's up to you to store thoses accounts
- in a different tree of you LDAP namespace: you should use
+ in a different tree of your LDAP namespace: you should use
"ou=Groups,dc=plainjoe,dc=org" to store groups and
"ou=People,dc=plainjoe,dc=org" to store users. Just configure your
NSS and PAM accordingly (usually, in the /etc/ldap.conf configuration
@@ -970,12 +994,12 @@ index default sub
<para>
To remedy the first security issue, the "ldap ssl" smb.conf parameter defaults
- to require an encrypted session (<command>ldap ssl = on</command>) using
- the default port of 636
+ to require an encrypted session (<parameter>ldap ssl = on</parameter>) using
+ the default port of <constant>636</constant>
when contacting the directory server. When using an OpenLDAP server, it
is possible to use the use the StartTLS LDAP extended operation in the place of
LDAPS. In either case, you are strongly discouraged to disable this security
- (<command>ldap ssl = off</command>).
+ (<parameter>ldap ssl = off</parameter>).
</para>
<para>
@@ -990,14 +1014,14 @@ index default sub
following ACL in <filename>slapd.conf</filename>:
</para>
- <para>
- <programlisting>
- ## allow the "ldap admin dn" access, but deny everyone else
- access to attrs=lmPassword,ntPassword
- by dn="cn=Samba Admin,ou=people,dc=plainjoe,dc=org" write
- by * none
- </programlisting>
- </para>
+<para>
+<screen>
+## allow the "ldap admin dn" access, but deny everyone else
+access to attrs=lmPassword,ntPassword
+ by dn="cn=Samba Admin,ou=people,dc=plainjoe,dc=org" write
+ by * none
+</screen>
+</para>
</sect3>
@@ -1069,7 +1093,7 @@ index default sub
<para>
The majority of these parameters are only used when Samba is acting as a PDC of
- a domain (refer to the <link linkend="pdc">Samba as a primary domain controller</link> chapter for details on
+ a domain (refer to the <link linkend="samba-pdc">Samba as a primary domain controller</link> chapter for details on
how to configure Samba as a Primary Domain Controller). The following four attributes
are only stored with the sambaAccount entry if the values are non-default values:
</para>
@@ -1104,7 +1128,7 @@ index default sub
</para>
<para>
- <programlisting>
+ <screen>
dn: uid=guest2, ou=people,dc=plainjoe,dc=org
ntPassword: 878D8014606CDA29677A44EFA1353FC7
pwdMustChange: 2147483647
@@ -1119,7 +1143,7 @@ index default sub
logoffTime: 2147483647
rid: 19006
pwdCanChange: 0
- </programlisting>
+ </screen>
</para>
<para>
@@ -1128,7 +1152,7 @@ index default sub
</para>
<para>
- <programlisting>
+ <screen>
dn: uid=gcarter, ou=people,dc=plainjoe,dc=org
logonTime: 0
displayName: Gerald Carter
@@ -1151,7 +1175,7 @@ index default sub
pwdCanChange: 0
pwdMustChange: 2147483647
ntPassword: 878D8014606CDA29677A44EFA1353FC7
- </programlisting>
+ </screen>
</para>
</sect3>
@@ -1208,7 +1232,12 @@ index default sub
<title>MySQL</title>
<para>
- Stuff goes here!
+ Every so often someone will come along with a great new idea. Storing of user accounts in an
+ SQL backend is one of them. Those who want to do this are in the best position to know what the
+ specific benefits are to them. This may sound like a cop-out, but in truth we can not attempt
+ to document every nitty little detail why certain things of marginal utility to the bulk of
+ Samba users might make sense to the rest. In any case, the following instructions should help
+ the determined SQL user to implement a working system.
</para>
<sect3>
@@ -1219,7 +1248,9 @@ index default sub
for the column names) or use the default table. The file <filename>examples/pdb/mysql/mysql.dump</filename>
contains the correct queries to create the required tables. Use the command :
+ <screen>
<command>mysql -u<replaceable>username</replaceable> -h<replaceable>hostname</replaceable> -p<replaceable>password</replaceable> <replaceable>databasename</replaceable> &gt; <filename>/path/to/samba/examples/pdb/mysql/mysql.dump</filename></command>
+ </screen>
</para>
</sect3>
@@ -1229,14 +1260,14 @@ index default sub
<para>This plugin lacks some good documentation, but here is some short info:</para>
<para>Add a the following to the <command>passdb backend</command> variable in your <filename>smb.conf</filename>:
- <programlisting>
+ <screen>
passdb backend = [other-plugins] mysql:identifier [other-plugins]
- </programlisting>
+ </screen>
</para>
<para>The identifier can be any string you like, as long as it doesn't collide with
the identifiers of other plugins or other instances of pdb_mysql. If you
- specify multiple pdb_mysql.so entries in 'passdb backend', you also need to
+ specify multiple pdb_mysql.so entries in <parameter>passdb backend</parameter>, you also need to
use different identifiers!
</para>
@@ -1244,16 +1275,16 @@ index default sub
Additional options can be given thru the &smb.conf; file in the <command>[global]</command> section.
</para>
- <para>
- <programlisting>
- identifier:mysql host - host name, defaults to 'localhost'
- identifier:mysql password
- identifier:mysql user - defaults to 'samba'
- identifier:mysql database - defaults to 'samba'
- identifier:mysql port - defaults to 3306
- identifier:table - Name of the table containing users
- </programlisting>
- </para>
+ <para>
+ <screen>
+ identifier:mysql host - host name, defaults to 'localhost'
+ identifier:mysql password
+ identifier:mysql user - defaults to 'samba'
+ identifier:mysql database - defaults to 'samba'
+ identifier:mysql port - defaults to 3306
+ identifier:table - Name of the table containing users
+ </screen>
+ </para>
<warning>
<para>
@@ -1266,41 +1297,41 @@ index default sub
<para>Names of the columns in this table(I've added column types those columns should have first):</para>
- <para>
- <programlisting>
- identifier:logon time column - int(9)
- identifier:logoff time column - int(9)
- identifier:kickoff time column - int(9)
- identifier:pass last set time column - int(9)
- identifier:pass can change time column - int(9)
- identifier:pass must change time column - int(9)
- identifier:username column - varchar(255) - unix username
- identifier:domain column - varchar(255) - NT domain user is part of
- identifier:nt username column - varchar(255) - NT username
- identifier:fullname column - varchar(255) - Full name of user
- identifier:home dir column - varchar(255) - Unix homedir path
- identifier:dir drive column - varchar(2) - Directory drive path (eg: 'H:')
- identifier:logon script column - varchar(255)
- - Batch file to run on client side when logging on
- identifier:profile path column - varchar(255) - Path of profile
- identifier:acct desc column - varchar(255) - Some ASCII NT user data
- identifier:workstations column - varchar(255)
- - Workstations user can logon to (or NULL for all)
- identifier:unknown string column - varchar(255) - unknown string
- identifier:munged dial column - varchar(255) - ?
- identifier:user sid column - varchar(255) - NT user SID
- identifier:group sid column - varchar(255) - NT group ID
- identifier:lanman pass column - varchar(255) - encrypted lanman password
- identifier:nt pass column - varchar(255) - encrypted nt passwd
- identifier:plain pass column - varchar(255) - plaintext password
- identifier:acct control column - int(9) - nt user data
- identifier:unknown 3 column - int(9) - unknown
- identifier:logon divs column - int(9) - ?
- identifier:hours len column - int(9) - ?
- identifier:unknown 5 column - int(9) - unknown
- identifier:unknown 6 column - int(9) - unknown
- </programlisting>
- </para>
+ <para>
+ <screen>
+ identifier:logon time column - int(9)
+ identifier:logoff time column - int(9)
+ identifier:kickoff time column - int(9)
+ identifier:pass last set time column - int(9)
+ identifier:pass can change time column - int(9)
+ identifier:pass must change time column - int(9)
+ identifier:username column - varchar(255) - unix username
+ identifier:domain column - varchar(255) - NT domain user is part of
+ identifier:nt username column - varchar(255) - NT username
+ identifier:fullname column - varchar(255) - Full name of user
+ identifier:home dir column - varchar(255) - Unix homedir path
+ identifier:dir drive column - varchar(2) - Directory drive path (eg: 'H:')
+ identifier:logon script column - varchar(255)
+ - Batch file to run on client side when logging on
+ identifier:profile path column - varchar(255) - Path of profile
+ identifier:acct desc column - varchar(255) - Some ASCII NT user data
+ identifier:workstations column - varchar(255)
+ - Workstations user can logon to (or NULL for all)
+ identifier:unknown string column - varchar(255) - unknown string
+ identifier:munged dial column - varchar(255) - ?
+ identifier:user sid column - varchar(255) - NT user SID
+ identifier:group sid column - varchar(255) - NT group ID
+ identifier:lanman pass column - varchar(255) - encrypted lanman password
+ identifier:nt pass column - varchar(255) - encrypted nt passwd
+ identifier:plain pass column - varchar(255) - plaintext password
+ identifier:acct control column - int(9) - nt user data
+ identifier:unknown 3 column - int(9) - unknown
+ identifier:logon divs column - int(9) - ?
+ identifier:hours len column - int(9) - ?
+ identifier:unknown 5 column - int(9) - unknown
+ identifier:unknown 6 column - int(9) - unknown
+ </screen>
+ </para>
<para>
Eventually, you can put a colon (:) after the name of each column, which
@@ -1383,10 +1414,10 @@ index default sub
</para>
<para>
- <programlisting>
then execute (as root):
- pdbedit -i smbpasswd -e tdbsam
- </programlisting>
+ <screen>
+ &rootprompt;<userinput>pdbedit -i smbpasswd -e tdbsam</userinput>
+ </screen>
</para>
</sect2>
</sect1>
@@ -1394,11 +1425,47 @@ index default sub
<sect1>
<title>Common Errors</title>
-<para>
-Put stuff here
-- People forget to put their users in their backend and then complain samba
- won't authorize them
-</para>
+ <sect2>
+ <title>Users can not logon - Users not in Samba SAM</title>
+
+ <para>
+ People forget to put their users in their backend and then complain samba won't authorize them.
+ </para>
+
+ </sect2>
+ <sect2>
+ <title>Users are being added to the wrong backend database</title>
+
+ <para>
+ A few complaints have been recieved from users that just moved to samba-3. The following
+ &smb.conf; file entries were causing problems, new accounts were being added to the old
+ smbpasswd file, not to the tdbsam passdb.tdb file:
+ </para>
+
+ <para>
+ <screen>
+ [globals]
+ ...
+ passdb backend = smbpasswd, tdbsam, guest
+ ...
+ </screen>
+ </para>
+
+ <para>
+ Samba will add new accounts to the first entry in the <emphasis>passdb backend</emphasis>
+ parameter entry. If you want to update to the tdbsam, then change the entry to:
+ </para>
+
+ <para>
+ <screen>
+ [globals]
+ ...
+ passdb backend = tdbsam, smbpasswd, guest
+ ...
+ </screen>
+ </para>
+
+ </sect2>
</sect1>
</chapter>
diff --git a/docs/docbook/projdoc/printer_driver2.xml b/docs/docbook/projdoc/printer_driver2.xml
index da3eb838f2..76f59c12ea 100644
--- a/docs/docbook/projdoc/printer_driver2.xml
+++ b/docs/docbook/projdoc/printer_driver2.xml
@@ -8,7 +8,7 @@
<address><email>papowell@lprng.org</email></address>
</affiliation>
</author>
- <pubdate> (3 May 2001) </pubdate>
+ <pubdate> 3 May 2001 </pubdate>
</chapterinfo>
<title>Printing Support</title>
diff --git a/docs/docbook/smbdotconf/printing/printcommand.xml b/docs/docbook/smbdotconf/printing/printcommand.xml
index 5444309053..4b9904f6a8 100644
--- a/docs/docbook/smbdotconf/printing/printcommand.xml
+++ b/docs/docbook/smbdotconf/printing/printcommand.xml
@@ -15,7 +15,7 @@
<para>The print command is simply a text string. It will be used
verbatim after macro substitutions have been made:</para>
- <para>%s, %p - the path to the spool
+ <para>%s, %f - the path to the spool
file name</para>
<para>%p - the appropriate printer
diff --git a/docs/docbook/smbdotconf/printing/totalprintjobs.xml b/docs/docbook/smbdotconf/printing/totalprintjobs.xml
new file mode 100644
index 0000000000..ccdb137a69
--- /dev/null
+++ b/docs/docbook/smbdotconf/printing/totalprintjobs.xml
@@ -0,0 +1,22 @@
+<samba:parameter name="total print jobs"
+ context="G"
+ print="1"
+ xmlns:samba="http://samba.org/common">
+<listitem>
+ <para>This parameter accepts an integer value which defines
+ a limit on the maximum number of print jobs that will be accepted
+ system wide at any given time. If a print job is submitted
+ by a client which will exceed this number, then <citerefentry><refentrytitle>smbd</refentrytitle>
+ <manvolnum>8</manvolnum></citerefentry> will return an
+ error indicating that no space is available on the server. The
+ default value of 0 means that no such limit exists. This parameter
+ can be used to prevent a server from exceeding its capacity and is
+ designed as a printing throttle. See also <link linkend="MAXPRINTJOBS">
+ <parameter moreinfo="none">max print jobs</parameter></link>.
+ </para>
+
+ <para>Default: <command moreinfo="none">total print jobs = 0</command></para>
+
+ <para>Example: <command moreinfo="none">total print jobs = 5000</command></para>
+</listitem>
+</samba:parameter>
diff --git a/docs/docbook/smbdotconf/smb.conf.5.xml b/docs/docbook/smbdotconf/smb.conf.5.xml
index db8eb81c28..2a5d190f69 100644
--- a/docs/docbook/smbdotconf/smb.conf.5.xml
+++ b/docs/docbook/smbdotconf/smb.conf.5.xml
@@ -396,10 +396,10 @@ alias|alias|alias|alias...
<listitem><para>the architecture of the remote
machine. Only some are recognized, and those may not be
100% reliable. It currently recognizes Samba, WfWg, Win95,
- WinNT, Win2k, WinXP, and Win2K3. Anything else will be known as
+ WinNT and Win2k. Anything else will be known as
&quot;UNKNOWN&quot;. If it gets it wrong then sending a level
- 3 log to <ulink url="mailto:samba-technical@samba.org">samba-technical@samba.org</ulink>
- should allow it to be fixed.</para></listitem>
+ 3 log to <ulink url="mailto:samba@samba.org">samba@samba.org
+ </ulink> should allow it to be fixed.</para></listitem>
</varlistentry>
<varlistentry>
@@ -507,11 +507,9 @@ alias|alias|alias|alias...
<varlistentry>
<term>case sensitive = yes/no</term>
- <listitem><para>controls whether filenames are case sensitive.
- Windows clients <emphasis>will</emphasis> break if you enable
- this parameter. It is only included for case insentive
- file systems (such as VFAT) and performance testing.
- Default <emphasis>no</emphasis>.</para></listitem>
+ <listitem><para>controls whether filenames are case sensitive. If
+ they aren't then Samba must do a filename search and match on passed
+ names. Default <emphasis>no</emphasis>.</para></listitem>
</varlistentry>
<varlistentry>
diff --git a/docs/docbook/xslt/db2latex/VERSION.xml b/docs/docbook/xslt/db2latex/VERSION.xml
index 6ac59ae4dd..4a9d0f5f4f 100644
--- a/docs/docbook/xslt/db2latex/VERSION.xml
+++ b/docs/docbook/xslt/db2latex/VERSION.xml
@@ -1,8 +1,8 @@
<?xml version='1.0'?>
<!--#############################################################################
- | $Id: VERSION.xml,v 1.1 2003/04/30 21:39:49 ab Exp $
+ | $Id: VERSION.xml,v 1.1.2.1 2003/05/01 14:14:13 jelmer Exp $
|- #############################################################################
- | $Author: ab $
+ | $Author: jelmer $
|
| PURPOSE:
+ ############################################################################## -->
@@ -17,7 +17,7 @@
<xsl:otherwise><xsl:value-of select="$RCSTAG" /></xsl:otherwise>
</xsl:choose>
</xsl:variable>
-<xsl:variable name="CVSVERSION">$Id: VERSION.xml,v 1.1 2003/04/30 21:39:49 ab Exp $</xsl:variable>
+<xsl:variable name="CVSVERSION">$Id: VERSION.xml,v 1.1.2.1 2003/05/01 14:14:13 jelmer Exp $</xsl:variable>
</xsl:stylesheet>
diff --git a/docs/docbook/xslt/db2latex/abstract.mod.xsl b/docs/docbook/xslt/db2latex/abstract.mod.xsl
index 6fd44bf9f2..3a1cf0ebf5 100644
--- a/docs/docbook/xslt/db2latex/abstract.mod.xsl
+++ b/docs/docbook/xslt/db2latex/abstract.mod.xsl
@@ -1,8 +1,8 @@
<?xml version='1.0'?>
<!--#############################################################################
-| $Id: abstract.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+| $Id: abstract.mod.xsl,v 1.1.2.1 2003/05/01 14:06:14 jelmer Exp $
|- #############################################################################
-| $Author: ab $
+| $Author: jelmer $
|
| PURPOSE:
+ ############################################################################## -->
@@ -18,7 +18,7 @@
<doc:reference id="abstract" xmlns="">
<referenceinfo>
<releaseinfo role="meta">
- $Id: abstract.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+ $Id: abstract.mod.xsl,v 1.1.2.1 2003/05/01 14:06:14 jelmer Exp $
</releaseinfo>
<authorgroup>
<author><firstname>Ramon</firstname> <surname>Casellas</surname></author>
diff --git a/docs/docbook/xslt/db2latex/admonition.mod.xsl b/docs/docbook/xslt/db2latex/admonition.mod.xsl
index c42d926c16..b1f8319bc6 100644
--- a/docs/docbook/xslt/db2latex/admonition.mod.xsl
+++ b/docs/docbook/xslt/db2latex/admonition.mod.xsl
@@ -1,8 +1,8 @@
<?xml version='1.0'?>
<!--#############################################################################
-| $Id: admonition.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+| $Id: admonition.mod.xsl,v 1.1.2.1 2003/05/01 14:06:14 jelmer Exp $
|- #############################################################################
-| $Author: ab $
+| $Author: jelmer $
|
| PURPOSE: Admonition templates.
+ ############################################################################## -->
@@ -17,7 +17,7 @@
<doc:reference name="admonition" xmlns="">
<referenceinfo>
<releaseinfo role="meta">
- $Id: admonition.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+ $Id: admonition.mod.xsl,v 1.1.2.1 2003/05/01 14:06:14 jelmer Exp $
</releaseinfo>
<authorgroup>
<author><firstname>Ramon</firstname> <surname>Casellas</surname></author>
diff --git a/docs/docbook/xslt/db2latex/authorgroup.mod.xsl b/docs/docbook/xslt/db2latex/authorgroup.mod.xsl
index 6af88ff51a..770737cf1f 100644
--- a/docs/docbook/xslt/db2latex/authorgroup.mod.xsl
+++ b/docs/docbook/xslt/db2latex/authorgroup.mod.xsl
@@ -1,8 +1,8 @@
<?xml version='1.0'?>
<!--#############################################################################
-| $Id: authorgroup.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+| $Id: authorgroup.mod.xsl,v 1.1.2.1 2003/05/01 14:06:14 jelmer Exp $
|- #############################################################################
-| $Author: ab $
+| $Author: jelmer $
|
| PURPOSE: Manage Authorgroups
+ ############################################################################## -->
@@ -19,7 +19,7 @@
<doc:reference id="authorgroup" xmlns="">
<referenceinfo>
<releaseinfo role="meta">
- $Id: authorgroup.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+ $Id: authorgroup.mod.xsl,v 1.1.2.1 2003/05/01 14:06:14 jelmer Exp $
</releaseinfo>
<authorgroup>
<author><firstname>Ramon</firstname> <surname>Casellas</surname></author>
diff --git a/docs/docbook/xslt/db2latex/biblio.mod.xsl b/docs/docbook/xslt/db2latex/biblio.mod.xsl
index f26cfb7b2d..68d509d520 100644
--- a/docs/docbook/xslt/db2latex/biblio.mod.xsl
+++ b/docs/docbook/xslt/db2latex/biblio.mod.xsl
@@ -1,8 +1,8 @@
<?xml version='1.0'?>
<!--#############################################################################
-| $Id: biblio.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+| $Id: biblio.mod.xsl,v 1.1.2.1 2003/05/01 14:06:14 jelmer Exp $
|- #############################################################################
-| $Author: ab $
+| $Author: jelmer $
|
| PURPOSE: Manage Bibliography.
+ ############################################################################## -->
@@ -19,7 +19,7 @@
<doc:reference id="biblio" xmlns="">
<referenceinfo>
<releaseinfo role="meta">
- $Id: biblio.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+ $Id: biblio.mod.xsl,v 1.1.2.1 2003/05/01 14:06:14 jelmer Exp $
</releaseinfo>
<authorgroup>
<author> <firstname>Ramon</firstname> <surname>Casellas</surname> </author>
diff --git a/docs/docbook/xslt/db2latex/block.mod.xsl b/docs/docbook/xslt/db2latex/block.mod.xsl
index 98d689989d..0eebb7c7ae 100644
--- a/docs/docbook/xslt/db2latex/block.mod.xsl
+++ b/docs/docbook/xslt/db2latex/block.mod.xsl
@@ -1,8 +1,8 @@
<?xml version='1.0'?>
<!--#############################################################################
-| $Id: block.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+| $Id: block.mod.xsl,v 1.1.2.1 2003/05/01 14:06:14 jelmer Exp $
|- #############################################################################
-| $Author: ab $
+| $Author: jelmer $
|
| PURPOSE:
+ ############################################################################## -->
@@ -18,7 +18,7 @@
<doc:reference id="block" xmlns="">
<referenceinfo>
<releaseinfo role="meta">
- $Id: block.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+ $Id: block.mod.xsl,v 1.1.2.1 2003/05/01 14:06:14 jelmer Exp $
</releaseinfo>
<authorgroup>
<author><firstname>Ramon</firstname> <surname>Casellas</surname></author>
diff --git a/docs/docbook/xslt/db2latex/book-article.mod.xsl b/docs/docbook/xslt/db2latex/book-article.mod.xsl
index 594e2f7f2a..9569e896d8 100644
--- a/docs/docbook/xslt/db2latex/book-article.mod.xsl
+++ b/docs/docbook/xslt/db2latex/book-article.mod.xsl
@@ -1,8 +1,8 @@
<?xml version='1.0'?>
<!--#############################################################################
-| $Id: book-article.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+| $Id: book-article.mod.xsl,v 1.1.2.1 2003/05/01 14:06:14 jelmer Exp $
|- #############################################################################
-| $Author: ab $
+| $Author: jelmer $
|
| PURPOSE:
| This template matches a book / article
@@ -20,7 +20,7 @@
<doc:reference id="book-article" xmlns="">
<referenceinfo>
<releaseinfo role="meta">
- $Id: book-article.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+ $Id: book-article.mod.xsl,v 1.1.2.1 2003/05/01 14:06:14 jelmer Exp $
</releaseinfo>
<authorgroup>
<author> <firstname>Ramon</firstname> <surname>Casellas</surname> </author>
@@ -467,9 +467,9 @@
<!--#############################################################################
- | $Id: book-article.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+ | $Id: book-article.mod.xsl,v 1.1.2.1 2003/05/01 14:06:14 jelmer Exp $
|- #############################################################################
- | $Author: ab $
+ | $Author: jelmer $
|
| PURPOSE: Table of Contents, Figures, ...
+ ############################################################################## -->
diff --git a/docs/docbook/xslt/db2latex/bridgehead.mod.xsl b/docs/docbook/xslt/db2latex/bridgehead.mod.xsl
index 0fb75841cd..525625a781 100644
--- a/docs/docbook/xslt/db2latex/bridgehead.mod.xsl
+++ b/docs/docbook/xslt/db2latex/bridgehead.mod.xsl
@@ -1,8 +1,8 @@
<?xml version='1.0'?>
<!--#############################################################################
-| $Id: bridgehead.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+| $Id: bridgehead.mod.xsl,v 1.1.2.1 2003/05/01 14:06:14 jelmer Exp $
|- #############################################################################
-| $Author: ab $
+| $Author: jelmer $
|
| PURPOSE:
+ ############################################################################## -->
@@ -17,7 +17,7 @@
<doc:reference id="bridgehead" xmlns="">
<referenceinfo>
<releaseinfo role="meta">
- $Id: bridgehead.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+ $Id: bridgehead.mod.xsl,v 1.1.2.1 2003/05/01 14:06:14 jelmer Exp $
</releaseinfo>
<authorgroup>
<author><firstname>Ramon</firstname> <surname>Casellas</surname></author>
diff --git a/docs/docbook/xslt/db2latex/callout.mod.xsl b/docs/docbook/xslt/db2latex/callout.mod.xsl
index 25ccc95882..d9f6c227bc 100644
--- a/docs/docbook/xslt/db2latex/callout.mod.xsl
+++ b/docs/docbook/xslt/db2latex/callout.mod.xsl
@@ -1,8 +1,8 @@
<?xml version='1.0'?>
<!--#############################################################################
-| $Id: callout.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+| $Id: callout.mod.xsl,v 1.1.2.1 2003/05/01 14:06:14 jelmer Exp $
|- #############################################################################
-| $Author: ab $
+| $Author: jelmer $
|
| PURPOSE:
+ ############################################################################## -->
@@ -17,7 +17,7 @@
<doc:reference id="callout" xmlns="">
<referenceinfo>
<releaseinfo role="meta">
- $Id: callout.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+ $Id: callout.mod.xsl,v 1.1.2.1 2003/05/01 14:06:14 jelmer Exp $
</releaseinfo>
<authorgroup>
<author> <firstname>Ramon</firstname> <surname>Casellas</surname> </author>
diff --git a/docs/docbook/xslt/db2latex/citation.mod.xsl b/docs/docbook/xslt/db2latex/citation.mod.xsl
index ef3493d413..ecf8ebfcb2 100644
--- a/docs/docbook/xslt/db2latex/citation.mod.xsl
+++ b/docs/docbook/xslt/db2latex/citation.mod.xsl
@@ -1,8 +1,8 @@
<?xml version='1.0'?>
<!--#############################################################################
-| $Id: citation.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+| $Id: citation.mod.xsl,v 1.1.2.1 2003/05/01 14:06:14 jelmer Exp $
|- #############################################################################
-| $Author: ab $
+| $Author: jelmer $
|
| PURPOSE:
+ ############################################################################## -->
@@ -18,7 +18,7 @@
<doc:reference id="citation" xmlns="">
<referenceinfo>
<releaseinfo role="meta">
- $Id: citation.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+ $Id: citation.mod.xsl,v 1.1.2.1 2003/05/01 14:06:14 jelmer Exp $
</releaseinfo>
<authorgroup>
<author> <firstname>Ramon</firstname> <surname>Casellas</surname> </author>
diff --git a/docs/docbook/xslt/db2latex/common/common.xsl b/docs/docbook/xslt/db2latex/common/common.xsl
index 2f0883a7f3..7da64de238 100644
--- a/docs/docbook/xslt/db2latex/common/common.xsl
+++ b/docs/docbook/xslt/db2latex/common/common.xsl
@@ -5,7 +5,7 @@
version='1.0'>
<!-- ********************************************************************
- $Id: common.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+ $Id: common.xsl,v 1.1.2.1 2003/05/01 14:14:13 jelmer Exp $
********************************************************************
Derived from the official DocBook XSL Stylesheets
@@ -17,7 +17,7 @@
<doc:reference xmlns="">
<referenceinfo>
-<releaseinfo role="meta"> $Id: common.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $ </releaseinfo>
+<releaseinfo role="meta"> $Id: common.xsl,v 1.1.2.1 2003/05/01 14:14:13 jelmer Exp $ </releaseinfo>
<author>
<surname>Ramon</surname>
<firstname>Casellas</firstname>
diff --git a/docs/docbook/xslt/db2latex/common/l10n.xsl b/docs/docbook/xslt/db2latex/common/l10n.xsl
index df07f4efe8..3f8d28e2a2 100644
--- a/docs/docbook/xslt/db2latex/common/l10n.xsl
+++ b/docs/docbook/xslt/db2latex/common/l10n.xsl
@@ -3,7 +3,7 @@
version='1.0'>
<!-- ********************************************************************
- $Id: l10n.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+ $Id: l10n.xsl,v 1.1.2.1 2003/05/01 14:14:14 jelmer Exp $
********************************************************************
Derived from the official XSL DocBook Stylesheet distribution.
diff --git a/docs/docbook/xslt/db2latex/component.mod.xsl b/docs/docbook/xslt/db2latex/component.mod.xsl
index 2197c94674..d8fd8c10c2 100644
--- a/docs/docbook/xslt/db2latex/component.mod.xsl
+++ b/docs/docbook/xslt/db2latex/component.mod.xsl
@@ -1,8 +1,8 @@
<?xml version='1.0'?>
<!--#############################################################################
-| $Id: component.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+| $Id: component.mod.xsl,v 1.1.2.1 2003/05/01 14:06:14 jelmer Exp $
|- #############################################################################
-| $Author: ab $
+| $Author: jelmer $
|
| PURPOSE:
+ ############################################################################## -->
@@ -19,7 +19,7 @@
<doc:reference id="component" xmlns="">
<referenceinfo>
<releaseinfo role="meta">
- $Id: component.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+ $Id: component.mod.xsl,v 1.1.2.1 2003/05/01 14:06:14 jelmer Exp $
</releaseinfo>
<authorgroup>
<author> <firstname>Ramon</firstname> <surname>Casellas</surname> </author>
diff --git a/docs/docbook/xslt/db2latex/dedication.mod.xsl b/docs/docbook/xslt/db2latex/dedication.mod.xsl
index 67012391f8..8914dba6de 100644
--- a/docs/docbook/xslt/db2latex/dedication.mod.xsl
+++ b/docs/docbook/xslt/db2latex/dedication.mod.xsl
@@ -1,8 +1,8 @@
<?xml version='1.0'?>
<!--#############################################################################
-| $Id: dedication.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+| $Id: dedication.mod.xsl,v 1.1.2.1 2003/05/01 14:06:14 jelmer Exp $
|- #############################################################################
-| $Author: ab $
+| $Author: jelmer $
|
| PURPOSE:
+ ############################################################################## -->
@@ -19,7 +19,7 @@
<doc:reference id="dedication" xmlns="">
<referenceinfo>
<releaseinfo role="meta">
- $Id: dedication.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+ $Id: dedication.mod.xsl,v 1.1.2.1 2003/05/01 14:06:14 jelmer Exp $
</releaseinfo>
<authorgroup>
<author> <firstname>Ramon</firstname> <surname>Casellas</surname> </author>
diff --git a/docs/docbook/xslt/db2latex/dingbat.mod.xsl b/docs/docbook/xslt/db2latex/dingbat.mod.xsl
index 86b2f25b30..30b91eeac6 100644
--- a/docs/docbook/xslt/db2latex/dingbat.mod.xsl
+++ b/docs/docbook/xslt/db2latex/dingbat.mod.xsl
@@ -1,8 +1,8 @@
<?xml version='1.0'?>
<!--#############################################################################
-| $Id: dingbat.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+| $Id: dingbat.mod.xsl,v 1.1.2.1 2003/05/01 14:06:14 jelmer Exp $
|- #############################################################################
-| $Author: ab $
+| $Author: jelmer $
|
| PURPOSE:
|
@@ -20,7 +20,7 @@
<doc:reference id="dingbat" xmlns="">
<referenceinfo>
<releaseinfo role="meta">
- $Id: dingbat.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+ $Id: dingbat.mod.xsl,v 1.1.2.1 2003/05/01 14:06:14 jelmer Exp $
</releaseinfo>
<authorgroup>
<author> <firstname>Ramon</firstname> <surname>Casellas</surname> </author>
diff --git a/docs/docbook/xslt/db2latex/docbook.xsl b/docs/docbook/xslt/db2latex/docbook.xsl
index 3a8759d57d..05fdbcc2ea 100644
--- a/docs/docbook/xslt/db2latex/docbook.xsl
+++ b/docs/docbook/xslt/db2latex/docbook.xsl
@@ -1,8 +1,8 @@
<?xml version='1.0'?>
<!--#############################################################################
-| $Id: docbook.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+| $Id: docbook.xsl,v 1.1.2.1 2003/05/01 14:06:14 jelmer Exp $
|- #############################################################################
-| $Author: ab $
+| $Author: jelmer $
|
| PURPOSE:
| This is the "parent" stylesheet. The used "modules" are included here.
diff --git a/docs/docbook/xslt/db2latex/email.mod.xsl b/docs/docbook/xslt/db2latex/email.mod.xsl
index fad6b59551..da74e7fb4f 100644
--- a/docs/docbook/xslt/db2latex/email.mod.xsl
+++ b/docs/docbook/xslt/db2latex/email.mod.xsl
@@ -1,8 +1,8 @@
<?xml version='1.0'?>
<!--#############################################################################
-| $Id: email.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+| $Id: email.mod.xsl,v 1.1.2.1 2003/05/01 14:06:14 jelmer Exp $
|- #############################################################################
-| $Author: ab $
+| $Author: jelmer $
|
| PURPOSE:
+ ############################################################################## -->
@@ -18,7 +18,7 @@
<doc:reference id="email" xmlns="">
<referenceinfo>
<releaseinfo role="meta">
- $Id: email.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+ $Id: email.mod.xsl,v 1.1.2.1 2003/05/01 14:06:14 jelmer Exp $
</releaseinfo>
<authorgroup>
<author> <firstname>Ramon</firstname> <surname>Casellas</surname> </author>
diff --git a/docs/docbook/xslt/db2latex/errors.mod.xsl b/docs/docbook/xslt/db2latex/errors.mod.xsl
index 466f052c7f..de3118bec2 100644
--- a/docs/docbook/xslt/db2latex/errors.mod.xsl
+++ b/docs/docbook/xslt/db2latex/errors.mod.xsl
@@ -1,9 +1,9 @@
<?xml version='1.0'?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version='1.0'>
<!--#############################################################################
- | $Id: errors.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+ | $Id: errors.mod.xsl,v 1.1.2.1 2003/05/01 14:06:14 jelmer Exp $
|- #############################################################################
- | $Author: ab $
+ | $Author: jelmer $
|
| PURPOSE:
+ ############################################################################## -->
diff --git a/docs/docbook/xslt/db2latex/example.mod.xsl b/docs/docbook/xslt/db2latex/example.mod.xsl
index 6f67df52bf..0c5a593aea 100644
--- a/docs/docbook/xslt/db2latex/example.mod.xsl
+++ b/docs/docbook/xslt/db2latex/example.mod.xsl
@@ -1,8 +1,8 @@
<?xml version='1.0'?>
<!--#############################################################################
-| $Id: example.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+| $Id: example.mod.xsl,v 1.1.2.1 2003/05/01 14:06:14 jelmer Exp $
|- #############################################################################
-| $Author: ab $
+| $Author: jelmer $
|
| PURPOSE:
+ ############################################################################## -->
@@ -19,7 +19,7 @@
<doc:reference id="example" xmlns="">
<referenceinfo>
<releaseinfo role="meta">
- $Id: example.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+ $Id: example.mod.xsl,v 1.1.2.1 2003/05/01 14:06:14 jelmer Exp $
</releaseinfo>
<authorgroup>
<author> <firstname>Ramon</firstname> <surname>Casellas</surname> </author>
diff --git a/docs/docbook/xslt/db2latex/figure.mod.xsl b/docs/docbook/xslt/db2latex/figure.mod.xsl
index f23689608a..2794144bbf 100644
--- a/docs/docbook/xslt/db2latex/figure.mod.xsl
+++ b/docs/docbook/xslt/db2latex/figure.mod.xsl
@@ -1,8 +1,8 @@
<?xml version='1.0'?>
<!--#############################################################################
-| $Id: figure.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+| $Id: figure.mod.xsl,v 1.1.2.1 2003/05/01 14:06:14 jelmer Exp $
|- #############################################################################
-| $Author: ab $
+| $Author: jelmer $
|
| PURPOSE: Template for figure tag.
+ ############################################################################## -->
@@ -17,7 +17,7 @@
<doc:reference id="figure" xmlns="">
<referenceinfo>
<releaseinfo role="meta">
- $Id: figure.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+ $Id: figure.mod.xsl,v 1.1.2.1 2003/05/01 14:06:14 jelmer Exp $
</releaseinfo>
<authorgroup>
<author> <firstname>Ramon</firstname> <surname>Casellas</surname> </author>
diff --git a/docs/docbook/xslt/db2latex/font.mod.xsl b/docs/docbook/xslt/db2latex/font.mod.xsl
index c66d6aab37..f8b3b9373b 100644
--- a/docs/docbook/xslt/db2latex/font.mod.xsl
+++ b/docs/docbook/xslt/db2latex/font.mod.xsl
@@ -1,8 +1,8 @@
<?xml version='1.0'?>
<!--#############################################################################
-| $Id: font.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+| $Id: font.mod.xsl,v 1.1.2.1 2003/05/01 14:06:14 jelmer Exp $
|- #############################################################################
-| $Author: ab $
+| $Author: jelmer $
|
| PURPOSE:
+ ############################################################################## -->
@@ -18,7 +18,7 @@
<doc:reference id="font" xmlns="">
<referenceinfo>
<releaseinfo role="meta">
- $Id: font.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+ $Id: font.mod.xsl,v 1.1.2.1 2003/05/01 14:06:14 jelmer Exp $
</releaseinfo>
<authorgroup>
<author> <firstname>Ramon</firstname> <surname>Casellas</surname> </author>
diff --git a/docs/docbook/xslt/db2latex/footnote.mod.xsl b/docs/docbook/xslt/db2latex/footnote.mod.xsl
index 1fb23dfbeb..b3e6dd3373 100644
--- a/docs/docbook/xslt/db2latex/footnote.mod.xsl
+++ b/docs/docbook/xslt/db2latex/footnote.mod.xsl
@@ -1,8 +1,8 @@
<?xml version='1.0'?>
<!--#############################################################################
-| $Id: footnote.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+| $Id: footnote.mod.xsl,v 1.1.2.1 2003/05/01 14:06:14 jelmer Exp $
|- #############################################################################
-| $Author: ab $
+| $Author: jelmer $
|
| PURPOSE:
+ ############################################################################## -->
@@ -18,7 +18,7 @@
<doc:reference id="footnote" xmlns="">
<referenceinfo>
<releaseinfo role="meta">
- $Id: footnote.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+ $Id: footnote.mod.xsl,v 1.1.2.1 2003/05/01 14:06:14 jelmer Exp $
</releaseinfo>
<authorgroup>
<author> <firstname>Ramon</firstname> <surname>Casellas</surname> </author>
diff --git a/docs/docbook/xslt/db2latex/formal.mod.xsl b/docs/docbook/xslt/db2latex/formal.mod.xsl
index 6c3ea3ff55..604a0d0cfd 100644
--- a/docs/docbook/xslt/db2latex/formal.mod.xsl
+++ b/docs/docbook/xslt/db2latex/formal.mod.xsl
@@ -1,8 +1,8 @@
<?xml version='1.0'?>
<!--#############################################################################
-| $Id: formal.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+| $Id: formal.mod.xsl,v 1.1.2.1 2003/05/01 14:06:14 jelmer Exp $
|- #############################################################################
-| $Author: ab $
+| $Author: jelmer $
|
| PURPOSE:
+ ############################################################################## -->
@@ -18,7 +18,7 @@
<doc:reference id="formal" xmlns="">
<referenceinfo>
<releaseinfo role="meta">
- $Id: formal.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+ $Id: formal.mod.xsl,v 1.1.2.1 2003/05/01 14:06:14 jelmer Exp $
</releaseinfo>
<authorgroup>
<author> <firstname>Ramon</firstname> <surname>Casellas</surname> </author>
diff --git a/docs/docbook/xslt/db2latex/glossary.mod.xsl b/docs/docbook/xslt/db2latex/glossary.mod.xsl
index a88fe609c2..2fa7979dcd 100644
--- a/docs/docbook/xslt/db2latex/glossary.mod.xsl
+++ b/docs/docbook/xslt/db2latex/glossary.mod.xsl
@@ -1,8 +1,8 @@
<?xml version='1.0'?>
<!--#############################################################################
-| $Id: glossary.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+| $Id: glossary.mod.xsl,v 1.1.2.1 2003/05/01 14:06:14 jelmer Exp $
|- #############################################################################
-| $Author: ab $
+| $Author: jelmer $
|
| PURPOSE:
+ ############################################################################## -->
@@ -19,7 +19,7 @@
<doc:reference id="glossary" xmlns="">
<referenceinfo>
<releaseinfo role="meta">
- $Id: glossary.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+ $Id: glossary.mod.xsl,v 1.1.2.1 2003/05/01 14:06:14 jelmer Exp $
</releaseinfo>
<authorgroup>
<author> <firstname>Ramon</firstname> <surname>Casellas</surname> </author>
diff --git a/docs/docbook/xslt/db2latex/graphic.mod.xsl b/docs/docbook/xslt/db2latex/graphic.mod.xsl
index 89799dbbb9..741f9ae03d 100644
--- a/docs/docbook/xslt/db2latex/graphic.mod.xsl
+++ b/docs/docbook/xslt/db2latex/graphic.mod.xsl
@@ -1,8 +1,8 @@
<?xml version='1.0'?>
<!--#############################################################################
-| $Id: graphic.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+| $Id: graphic.mod.xsl,v 1.1.2.1 2003/05/01 14:06:14 jelmer Exp $
|- #############################################################################
-| $Author: ab $
+| $Author: jelmer $
|
| PURPOSE:
+ ############################################################################## -->
@@ -18,7 +18,7 @@
<doc:reference id="graphic" xmlns="">
<referenceinfo>
<releaseinfo role="meta">
- $Id: graphic.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+ $Id: graphic.mod.xsl,v 1.1.2.1 2003/05/01 14:06:14 jelmer Exp $
</releaseinfo>
<authorgroup>
<author> <firstname>Ramon</firstname> <surname>Casellas</surname> </author>
diff --git a/docs/docbook/xslt/db2latex/html.mod.xsl b/docs/docbook/xslt/db2latex/html.mod.xsl
index fade6e7e78..e1e8db304e 100644
--- a/docs/docbook/xslt/db2latex/html.mod.xsl
+++ b/docs/docbook/xslt/db2latex/html.mod.xsl
@@ -1,9 +1,9 @@
<?xml version='1.0'?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version='1.0'>
<!--#############################################################################
- | $Id: html.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+ | $Id: html.mod.xsl,v 1.1.2.1 2003/05/01 14:06:14 jelmer Exp $
|- #############################################################################
- | $Author: ab $
+ | $Author: jelmer $
|
| PURPOSE:
|
diff --git a/docs/docbook/xslt/db2latex/index.mod.xsl b/docs/docbook/xslt/db2latex/index.mod.xsl
index 76985c19fd..40586567c8 100644
--- a/docs/docbook/xslt/db2latex/index.mod.xsl
+++ b/docs/docbook/xslt/db2latex/index.mod.xsl
@@ -1,8 +1,8 @@
<?xml version='1.0'?>
<!--#############################################################################
-| $Id: index.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+| $Id: index.mod.xsl,v 1.1.2.1 2003/05/01 14:06:14 jelmer Exp $
|- #############################################################################
-| $Author: ab $
+| $Author: jelmer $
|
| PURPOSE:
+ ############################################################################## -->
@@ -18,7 +18,7 @@
<doc:reference id="index" xmlns="">
<referenceinfo>
<releaseinfo role="meta">
- $Id: index.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+ $Id: index.mod.xsl,v 1.1.2.1 2003/05/01 14:06:14 jelmer Exp $
</releaseinfo>
<authorgroup>
<author> <firstname>Ramon</firstname> <surname>Casellas</surname> </author>
diff --git a/docs/docbook/xslt/db2latex/info.mod.xsl b/docs/docbook/xslt/db2latex/info.mod.xsl
index 3b8bb5162a..609df842f9 100644
--- a/docs/docbook/xslt/db2latex/info.mod.xsl
+++ b/docs/docbook/xslt/db2latex/info.mod.xsl
@@ -1,8 +1,8 @@
<?xml version='1.0'?>
<!--#############################################################################
-| $Id: info.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+| $Id: info.mod.xsl,v 1.1.2.1 2003/05/01 14:06:14 jelmer Exp $
|- #############################################################################
-| $Author: ab $
+| $Author: jelmer $
|
| PURPOSE:
+ ############################################################################## -->
@@ -18,7 +18,7 @@
<doc:reference id="info" xmlns="">
<referenceinfo>
<releaseinfo role="meta">
- $Id: info.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+ $Id: info.mod.xsl,v 1.1.2.1 2003/05/01 14:06:14 jelmer Exp $
</releaseinfo>
<authorgroup>
<author> <firstname>Ramon</firstname> <surname>Casellas</surname> </author>
diff --git a/docs/docbook/xslt/db2latex/inline.mod.xsl b/docs/docbook/xslt/db2latex/inline.mod.xsl
index 5661ca4385..e5fe2b476c 100644
--- a/docs/docbook/xslt/db2latex/inline.mod.xsl
+++ b/docs/docbook/xslt/db2latex/inline.mod.xsl
@@ -1,8 +1,8 @@
<?xml version='1.0'?>
<!--#############################################################################
-| $Id: inline.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+| $Id: inline.mod.xsl,v 1.1.2.1 2003/05/01 14:06:14 jelmer Exp $
|- #############################################################################
-| $Author: ab $
+| $Author: jelmer $
|
| PURPOSE:
+ ############################################################################## -->
@@ -17,7 +17,7 @@
<doc:reference id="inline" xmlns="">
<referenceinfo>
<releaseinfo role="meta">
- $Id: inline.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+ $Id: inline.mod.xsl,v 1.1.2.1 2003/05/01 14:06:14 jelmer Exp $
</releaseinfo>
<authorgroup>
<author> <firstname>Ramon</firstname> <surname>Casellas</surname> </author>
diff --git a/docs/docbook/xslt/db2latex/keywords.mod.xsl b/docs/docbook/xslt/db2latex/keywords.mod.xsl
index c3fd7376b5..a9e2477b96 100644
--- a/docs/docbook/xslt/db2latex/keywords.mod.xsl
+++ b/docs/docbook/xslt/db2latex/keywords.mod.xsl
@@ -1,8 +1,8 @@
<?xml version='1.0'?>
<!--#############################################################################
-| $Id: keywords.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+| $Id: keywords.mod.xsl,v 1.1.2.1 2003/05/01 14:06:14 jelmer Exp $
|- #############################################################################
-| $Author: ab $
+| $Author: jelmer $
|
| PURPOSE:
+ ############################################################################## -->
@@ -18,7 +18,7 @@
<doc:reference id="keywords" xmlns="">
<referenceinfo>
<releaseinfo role="meta">
- $Id: keywords.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+ $Id: keywords.mod.xsl,v 1.1.2.1 2003/05/01 14:06:14 jelmer Exp $
</releaseinfo>
<authorgroup>
<author> <firstname>Ramon</firstname> <surname>Casellas</surname> </author>
diff --git a/docs/docbook/xslt/db2latex/labelid.mod.xsl b/docs/docbook/xslt/db2latex/labelid.mod.xsl
index 7f8206321f..342516cb35 100644
--- a/docs/docbook/xslt/db2latex/labelid.mod.xsl
+++ b/docs/docbook/xslt/db2latex/labelid.mod.xsl
@@ -1,8 +1,8 @@
<?xml version='1.0'?>
<!--#############################################################################
-| $Id: labelid.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+| $Id: labelid.mod.xsl,v 1.1.2.1 2003/05/01 14:06:14 jelmer Exp $
|- #############################################################################
-| $Author: ab $
+| $Author: jelmer $
|
| PURPOSE: When this template is called, it marks the object with a label
| and an hypertarget.
@@ -20,7 +20,7 @@
<doc:reference id="labelid" xmlns="">
<referenceinfo>
<releaseinfo role="meta">
- $Id: labelid.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+ $Id: labelid.mod.xsl,v 1.1.2.1 2003/05/01 14:06:14 jelmer Exp $
</releaseinfo>
<authorgroup>
<author> <firstname>Ramon</firstname> <surname>Casellas</surname> </author>
diff --git a/docs/docbook/xslt/db2latex/latex.mapping.xsl b/docs/docbook/xslt/db2latex/latex.mapping.xsl
index 5e11f9de3c..a0fd5ca101 100644
--- a/docs/docbook/xslt/db2latex/latex.mapping.xsl
+++ b/docs/docbook/xslt/db2latex/latex.mapping.xsl
@@ -1,8 +1,8 @@
<?xml version='1.0'?>
<!--#############################################################################
-| $Id: latex.mapping.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+| $Id: latex.mapping.xsl,v 1.1.2.1 2003/05/01 14:06:14 jelmer Exp $
|- #############################################################################
-| $Author: ab $
+| $Author: jelmer $
|
| PURPOSE:
+ ############################################################################## -->
@@ -20,7 +20,7 @@
<doc:reference id="glossary" xmlns="">
<referenceinfo>
<releaseinfo role="meta">
- $Id: latex.mapping.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+ $Id: latex.mapping.xsl,v 1.1.2.1 2003/05/01 14:06:14 jelmer Exp $
</releaseinfo>
<author>
<firstname>Ramon</firstname><surname>Casellas</surname>
diff --git a/docs/docbook/xslt/db2latex/lists.mod.xsl b/docs/docbook/xslt/db2latex/lists.mod.xsl
index 29afd0f58d..bcd3305b14 100644
--- a/docs/docbook/xslt/db2latex/lists.mod.xsl
+++ b/docs/docbook/xslt/db2latex/lists.mod.xsl
@@ -1,8 +1,8 @@
<?xml version='1.0'?>
<!--#############################################################################
-| $Id: lists.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+| $Id: lists.mod.xsl,v 1.1.2.1 2003/05/01 14:06:15 jelmer Exp $
|- #############################################################################
-| $Author: ab $
+| $Author: jelmer $
|
| PURPOSE:
+ ############################################################################## -->
@@ -19,7 +19,7 @@
<doc:reference id="lists" xmlns="">
<referenceinfo>
<releaseinfo role="meta">
- $Id: lists.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+ $Id: lists.mod.xsl,v 1.1.2.1 2003/05/01 14:06:15 jelmer Exp $
</releaseinfo>
<authorgroup>
<author> <firstname>Ramon</firstname> <surname>Casellas</surname> </author>
diff --git a/docs/docbook/xslt/db2latex/mathelem.mod.xsl b/docs/docbook/xslt/db2latex/mathelem.mod.xsl
index 66e7089413..0402ed97ae 100644
--- a/docs/docbook/xslt/db2latex/mathelem.mod.xsl
+++ b/docs/docbook/xslt/db2latex/mathelem.mod.xsl
@@ -1,8 +1,8 @@
<?xml version='1.0'?>
<!--#############################################################################
-| $Id: mathelem.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+| $Id: mathelem.mod.xsl,v 1.1.2.1 2003/05/01 14:06:15 jelmer Exp $
|- #############################################################################
-| $Author: ab $
+| $Author: jelmer $
|
| PURPOSE: Math Elements as theorems, lemmas, propositions, etc.
| Note: these elements are not part of the DocBook DTD. I have extended
@@ -22,7 +22,7 @@
<doc:reference id="mathelems" xmlns="">
<referenceinfo>
<releaseinfo role="meta">
- $Id: mathelem.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+ $Id: mathelem.mod.xsl,v 1.1.2.1 2003/05/01 14:06:15 jelmer Exp $
</releaseinfo>
<authorgroup>
<author> <firstname>Ramon</firstname> <surname>Casellas</surname> </author>
diff --git a/docs/docbook/xslt/db2latex/mathml/mathml.content.constsymb.mod.xsl b/docs/docbook/xslt/db2latex/mathml/mathml.content.constsymb.mod.xsl
index 1317c483a7..e262c3ce8c 100644
--- a/docs/docbook/xslt/db2latex/mathml/mathml.content.constsymb.mod.xsl
+++ b/docs/docbook/xslt/db2latex/mathml/mathml.content.constsymb.mod.xsl
@@ -5,9 +5,9 @@
<!ENTITY % mmlextra PUBLIC "MathML extra" "ent/mmlextra.ent"> %mmlextra;
]>
<!--#############################################################################
- | $Id: mathml.content.constsymb.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+ | $Id: mathml.content.constsymb.mod.xsl,v 1.1.2.1 2003/05/01 14:10:37 jelmer Exp $
|- #############################################################################
- | $Author: ab $
+ | $Author: jelmer $
|
| PURPOSE: MathML content markup, constants and symbols, 4.4.12.
| MathML namespace used -> mml
diff --git a/docs/docbook/xslt/db2latex/mathml/mathml.content.functions.mod.xsl b/docs/docbook/xslt/db2latex/mathml/mathml.content.functions.mod.xsl
index a317fc018b..6b9c5f00cf 100644
--- a/docs/docbook/xslt/db2latex/mathml/mathml.content.functions.mod.xsl
+++ b/docs/docbook/xslt/db2latex/mathml/mathml.content.functions.mod.xsl
@@ -5,9 +5,9 @@
<!ENTITY % mmlextra PUBLIC "MathML extra" "ent/mmlextra.ent"> %mmlextra;
]>
<!--#############################################################################
- | $Id: mathml.content.functions.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+ | $Id: mathml.content.functions.mod.xsl,v 1.1.2.1 2003/05/01 14:10:37 jelmer Exp $
|- #############################################################################
- | $Author: ab $
+ | $Author: jelmer $
|
| PURPOSE: MathML content markup.
| Note: these elements are not part of the DocBook DTD. I have extended
diff --git a/docs/docbook/xslt/db2latex/mathml/mathml.content.mod.xsl b/docs/docbook/xslt/db2latex/mathml/mathml.content.mod.xsl
index ded65f4a9c..be8ed9eda3 100644
--- a/docs/docbook/xslt/db2latex/mathml/mathml.content.mod.xsl
+++ b/docs/docbook/xslt/db2latex/mathml/mathml.content.mod.xsl
@@ -5,9 +5,9 @@
<!ENTITY % mmlextra PUBLIC "MathML extra" "ent/mmlextra.ent"> %mmlextra;
]>
<!--#############################################################################
- | $Id: mathml.content.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+ | $Id: mathml.content.mod.xsl,v 1.1.2.1 2003/05/01 14:10:37 jelmer Exp $
|- #############################################################################
- | $Author: ab $
+ | $Author: jelmer $
|
| PURPOSE: MathML content markup.
| Note: these elements are not part of the DocBook DTD. I have extended
diff --git a/docs/docbook/xslt/db2latex/mathml/mathml.content.token.mod.xsl b/docs/docbook/xslt/db2latex/mathml/mathml.content.token.mod.xsl
index cad72c5139..bfa565b396 100644
--- a/docs/docbook/xslt/db2latex/mathml/mathml.content.token.mod.xsl
+++ b/docs/docbook/xslt/db2latex/mathml/mathml.content.token.mod.xsl
@@ -5,9 +5,9 @@
<!ENTITY % mmlextra PUBLIC "MathML extra" "ent/mmlextra.ent"> %mmlextra;
]>
<!--#############################################################################
- | $Id: mathml.content.token.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+ | $Id: mathml.content.token.mod.xsl,v 1.1.2.1 2003/05/01 14:10:37 jelmer Exp $
|- #############################################################################
- | $Author: ab $
+ | $Author: jelmer $
|
| PURPOSE: MathML Content Markup, tokens (ci, cn, csymbol)
| MathML namespace used -> mml
diff --git a/docs/docbook/xslt/db2latex/mathml/mathml.mod.xsl b/docs/docbook/xslt/db2latex/mathml/mathml.mod.xsl
index c87b4ef7f6..e60acf67c0 100644
--- a/docs/docbook/xslt/db2latex/mathml/mathml.mod.xsl
+++ b/docs/docbook/xslt/db2latex/mathml/mathml.mod.xsl
@@ -5,9 +5,9 @@
<!ENTITY % mmlextra PUBLIC "MathML extra" "ent/mmlextra.ent"> %mmlextra;
]>
<!--#############################################################################
- | $Id: mathml.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+ | $Id: mathml.mod.xsl,v 1.1.2.1 2003/05/01 14:10:37 jelmer Exp $
|- #############################################################################
- | $Author: ab $
+ | $Author: jelmer $
|
| PURPOSE: MathML presentation and content markup.
| Note: these elements are not part of the DocBook DTD. I have extended
diff --git a/docs/docbook/xslt/db2latex/mathml/mathml.presentation.mod.xsl b/docs/docbook/xslt/db2latex/mathml/mathml.presentation.mod.xsl
index 6e8bb83f30..3f9047902b 100644
--- a/docs/docbook/xslt/db2latex/mathml/mathml.presentation.mod.xsl
+++ b/docs/docbook/xslt/db2latex/mathml/mathml.presentation.mod.xsl
@@ -5,9 +5,9 @@
<!ENTITY % mmlextra PUBLIC "MathML extra" "ent/mmlextra.ent"> %mmlextra;
]>
<!--#############################################################################
- | $Id: mathml.presentation.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+ | $Id: mathml.presentation.mod.xsl,v 1.1.2.1 2003/05/01 14:10:37 jelmer Exp $
|- #############################################################################
- | $Author: ab $
+ | $Author: jelmer $
|
| PURPOSE: MathML presentation markup.
| Note: these elements are not part of the DocBook DTD. I have extended
diff --git a/docs/docbook/xslt/db2latex/mediaobject.mod.xsl b/docs/docbook/xslt/db2latex/mediaobject.mod.xsl
index dc1685b480..9d727a2156 100644
--- a/docs/docbook/xslt/db2latex/mediaobject.mod.xsl
+++ b/docs/docbook/xslt/db2latex/mediaobject.mod.xsl
@@ -1,8 +1,8 @@
<?xml version='1.0'?>
<!--#############################################################################
-| $Id: mediaobject.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+| $Id: mediaobject.mod.xsl,v 1.1.2.1 2003/05/01 14:06:15 jelmer Exp $
|- #############################################################################
-| $Author: ab $
+| $Author: jelmer $
|
| PURPOSE: Manage Imageobject related tags.
+ ############################################################################## -->
@@ -19,7 +19,7 @@
<doc:reference id="mediaobject" xmlns="">
<referenceinfo>
<releaseinfo role="meta">
- $Id: mediaobject.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+ $Id: mediaobject.mod.xsl,v 1.1.2.1 2003/05/01 14:06:15 jelmer Exp $
</releaseinfo>
<authorgroup>
<author> <firstname>Ramon</firstname> <surname>Casellas</surname> </author>
diff --git a/docs/docbook/xslt/db2latex/msgset.mod.xsl b/docs/docbook/xslt/db2latex/msgset.mod.xsl
index aef046f665..345e52406f 100644
--- a/docs/docbook/xslt/db2latex/msgset.mod.xsl
+++ b/docs/docbook/xslt/db2latex/msgset.mod.xsl
@@ -1,9 +1,9 @@
<?xml version='1.0'?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version='1.0'>
<!--#############################################################################
- | $Id: msgset.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+ | $Id: msgset.mod.xsl,v 1.1.2.1 2003/05/01 14:06:15 jelmer Exp $
|- #############################################################################
- | $Author: ab $
+ | $Author: jelmer $
|
| PURPOSE:
+ ############################################################################## -->
diff --git a/docs/docbook/xslt/db2latex/normalize-scape.mod.xsl b/docs/docbook/xslt/db2latex/normalize-scape.mod.xsl
index 15e2e94e25..68b2ad801c 100644
--- a/docs/docbook/xslt/db2latex/normalize-scape.mod.xsl
+++ b/docs/docbook/xslt/db2latex/normalize-scape.mod.xsl
@@ -1,8 +1,8 @@
<?xml version='1.0'?>
<!--#############################################################################
-| $Id: normalize-scape.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+| $Id: normalize-scape.mod.xsl,v 1.1.2.1 2003/05/01 14:06:15 jelmer Exp $
|- #############################################################################
-| $Author: ab $
+| $Author: jelmer $
|
| PURPOSE:
| Escape LaTeX and normalize-space templates.
@@ -20,7 +20,7 @@
<doc:reference id="normalize-scape" xmlns="">
<referenceinfo>
<releaseinfo role="meta">
- $Id: normalize-scape.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+ $Id: normalize-scape.mod.xsl,v 1.1.2.1 2003/05/01 14:06:15 jelmer Exp $
</releaseinfo>
<authorgroup>
<author> <firstname>Ramon</firstname> <surname>Casellas</surname> </author>
diff --git a/docs/docbook/xslt/db2latex/para.mod.xsl b/docs/docbook/xslt/db2latex/para.mod.xsl
index 64d6d8f01d..6965cfaf4e 100644
--- a/docs/docbook/xslt/db2latex/para.mod.xsl
+++ b/docs/docbook/xslt/db2latex/para.mod.xsl
@@ -1,8 +1,8 @@
<?xml version='1.0'?>
<!--#############################################################################
-| $Id: para.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+| $Id: para.mod.xsl,v 1.1.2.1 2003/05/01 14:06:15 jelmer Exp $
|- #############################################################################
-| $Author: ab $
+| $Author: jelmer $
|
| PURPOSE:
+ ############################################################################## -->
@@ -17,7 +17,7 @@
<doc:reference id="para" xmlns="">
<referenceinfo>
<releaseinfo role="meta">
- $Id: para.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+ $Id: para.mod.xsl,v 1.1.2.1 2003/05/01 14:06:15 jelmer Exp $
</releaseinfo>
<authorgroup>
<author> <firstname>Ramon</firstname> <surname>Casellas</surname> </author>
diff --git a/docs/docbook/xslt/db2latex/part-chap-app.mod.xsl b/docs/docbook/xslt/db2latex/part-chap-app.mod.xsl
index 376b2b82e6..6d15782185 100644
--- a/docs/docbook/xslt/db2latex/part-chap-app.mod.xsl
+++ b/docs/docbook/xslt/db2latex/part-chap-app.mod.xsl
@@ -1,8 +1,8 @@
<?xml version='1.0'?>
<!--#############################################################################
-| $Id: part-chap-app.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+| $Id: part-chap-app.mod.xsl,v 1.1.2.1 2003/05/01 14:06:15 jelmer Exp $
|- #############################################################################
-| $Author: ab $
+| $Author: jelmer $
|
| PURPOSE: Part
+ ############################################################################## -->
@@ -18,7 +18,7 @@
<doc:reference id="part-chap-app" xmlns="">
<referenceinfo>
<releaseinfo role="meta">
- $Id: part-chap-app.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+ $Id: part-chap-app.mod.xsl,v 1.1.2.1 2003/05/01 14:06:15 jelmer Exp $
</releaseinfo>
<authorgroup>
<author> <firstname>Ramon</firstname> <surname>Casellas</surname> </author>
@@ -56,9 +56,9 @@
<!--#############################################################################
- | $Id: part-chap-app.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+ | $Id: part-chap-app.mod.xsl,v 1.1.2.1 2003/05/01 14:06:15 jelmer Exp $
|- #############################################################################
- | $Author: ab $
+ | $Author: jelmer $
|
| PURPOSE: Chapter
+ ############################################################################## -->
@@ -103,9 +103,9 @@
<!--#############################################################################
- | $Id: part-chap-app.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+ | $Id: part-chap-app.mod.xsl,v 1.1.2.1 2003/05/01 14:06:15 jelmer Exp $
|- #############################################################################
- | $Author: ab $
+ | $Author: jelmer $
|
| PURPOSE:
+ ############################################################################## -->
diff --git a/docs/docbook/xslt/db2latex/pi.mod.xsl b/docs/docbook/xslt/db2latex/pi.mod.xsl
index fe84aa446e..0640e8e77a 100644
--- a/docs/docbook/xslt/db2latex/pi.mod.xsl
+++ b/docs/docbook/xslt/db2latex/pi.mod.xsl
@@ -1,8 +1,8 @@
<?xml version='1.0'?>
<!--#############################################################################
-| $Id: pi.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+| $Id: pi.mod.xsl,v 1.1.2.1 2003/05/01 14:06:15 jelmer Exp $
|- #############################################################################
-| $Author: ab $
+| $Author: jelmer $
|
| PURPOSE:
+ ############################################################################## -->
@@ -20,7 +20,7 @@
<doc:reference id="abstract" xmlns="">
<referenceinfo>
<releaseinfo role="meta">
- $Id: pi.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+ $Id: pi.mod.xsl,v 1.1.2.1 2003/05/01 14:06:15 jelmer Exp $
</releaseinfo>
<authorgroup>
<author> <firstname>Ramon</firstname> <surname>Casellas</surname> </author>
diff --git a/docs/docbook/xslt/db2latex/preamble.mod.xsl b/docs/docbook/xslt/db2latex/preamble.mod.xsl
index 3e66f33c16..381ed8fe12 100644
--- a/docs/docbook/xslt/db2latex/preamble.mod.xsl
+++ b/docs/docbook/xslt/db2latex/preamble.mod.xsl
@@ -1,8 +1,8 @@
<?xml version='1.0'?>
<!--#############################################################################
-| $Id: preamble.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+| $Id: preamble.mod.xsl,v 1.1.2.1 2003/05/01 14:06:15 jelmer Exp $
|- #############################################################################
-| $Author: ab $
+| $Author: jelmer $
|
| PURPOSE: Variables and templates to manage LaTeX preamble.
+ ############################################################################## -->
@@ -15,7 +15,7 @@
<doc:reference id="preamble" xmlns="">
<referenceinfo>
<releaseinfo role="meta">
- $Id: preamble.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+ $Id: preamble.mod.xsl,v 1.1.2.1 2003/05/01 14:06:15 jelmer Exp $
</releaseinfo>
<authorgroup>
<author> <firstname>Ramon</firstname> <surname>Casellas</surname> </author>
diff --git a/docs/docbook/xslt/db2latex/preface.mod.xsl b/docs/docbook/xslt/db2latex/preface.mod.xsl
index 90d30f09cf..36ede3e9b5 100644
--- a/docs/docbook/xslt/db2latex/preface.mod.xsl
+++ b/docs/docbook/xslt/db2latex/preface.mod.xsl
@@ -1,8 +1,8 @@
<?xml version='1.0'?>
<!--#############################################################################
-| $Id: preface.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+| $Id: preface.mod.xsl,v 1.1.2.1 2003/05/01 14:06:15 jelmer Exp $
|- #############################################################################
-| $Author: ab $
+| $Author: jelmer $
|
| PURPOSE:
+ ############################################################################## -->
@@ -19,7 +19,7 @@
<doc:reference id="preface" xmlns="">
<referenceinfo>
<releaseinfo role="meta">
- $Id: preface.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+ $Id: preface.mod.xsl,v 1.1.2.1 2003/05/01 14:06:15 jelmer Exp $
</releaseinfo>
<authorgroup>
<author> <firstname>Ramon</firstname> <surname>Casellas</surname> </author>
diff --git a/docs/docbook/xslt/db2latex/procedure.mod.xsl b/docs/docbook/xslt/db2latex/procedure.mod.xsl
index 3fca796151..40d450504b 100644
--- a/docs/docbook/xslt/db2latex/procedure.mod.xsl
+++ b/docs/docbook/xslt/db2latex/procedure.mod.xsl
@@ -1,8 +1,8 @@
<?xml version='1.0'?>
<!--#############################################################################
-| $Id: procedure.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+| $Id: procedure.mod.xsl,v 1.1.2.1 2003/05/01 14:06:15 jelmer Exp $
|- #############################################################################
-| $Author: ab $
+| $Author: jelmer $
|
| PURPOSE:
+ ############################################################################## -->
@@ -19,7 +19,7 @@
<doc:reference id="procedure" xmlns="">
<referenceinfo>
<releaseinfo role="meta">
- $Id: procedure.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+ $Id: procedure.mod.xsl,v 1.1.2.1 2003/05/01 14:06:15 jelmer Exp $
</releaseinfo>
<authorgroup>
<author> <firstname>Ramon</firstname> <surname>Casellas</surname> </author>
diff --git a/docs/docbook/xslt/db2latex/qandaset.mod.xsl b/docs/docbook/xslt/db2latex/qandaset.mod.xsl
index c6363e4782..f7729be035 100644
--- a/docs/docbook/xslt/db2latex/qandaset.mod.xsl
+++ b/docs/docbook/xslt/db2latex/qandaset.mod.xsl
@@ -1,8 +1,8 @@
<?xml version="1.0"?>
<!--#############################################################################
-| $Id: qandaset.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+| $Id: qandaset.mod.xsl,v 1.1.2.1 2003/05/01 14:06:15 jelmer Exp $
|- #############################################################################
-| $Author: ab $
+| $Author: jelmer $
|
| PURPOSE:
| Portions (c) Norman Walsh, official DocBook XSL stylesheets.
@@ -19,7 +19,7 @@
<!-- DOCUMENTATION -->
<doc:reference xmlns="" id="qandaset">
<referenceinfo>
- <releaseinfo role="meta"> $Id: qandaset.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $ </releaseinfo>
+ <releaseinfo role="meta"> $Id: qandaset.mod.xsl,v 1.1.2.1 2003/05/01 14:06:15 jelmer Exp $ </releaseinfo>
<authorgroup>
<author> <firstname>Ramon</firstname> <surname>Casellas</surname> </author>
<author> <firstname>James</firstname> <surname>Devenish</surname> </author>
diff --git a/docs/docbook/xslt/db2latex/refentry.mod.xsl b/docs/docbook/xslt/db2latex/refentry.mod.xsl
index dc1a7c440c..be10075f1f 100644
--- a/docs/docbook/xslt/db2latex/refentry.mod.xsl
+++ b/docs/docbook/xslt/db2latex/refentry.mod.xsl
@@ -1,8 +1,8 @@
<?xml version='1.0'?>
<!--#############################################################################
-| $Id: refentry.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+| $Id: refentry.mod.xsl,v 1.1.2.1 2003/05/01 14:06:15 jelmer Exp $
|- #############################################################################
-| $Author: ab $
+| $Author: jelmer $
|
| PURPOSE:
+ ############################################################################## -->
@@ -19,7 +19,7 @@
<doc:reference id="refentry" xmlns="">
<referenceinfo>
<releaseinfo role="meta">
- $Id: refentry.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+ $Id: refentry.mod.xsl,v 1.1.2.1 2003/05/01 14:06:15 jelmer Exp $
</releaseinfo>
<authogroup>
<author> <firstname>Ramon</firstname> <surname>Casellas</surname> </author>
diff --git a/docs/docbook/xslt/db2latex/revision.mod.xsl b/docs/docbook/xslt/db2latex/revision.mod.xsl
index c1b39cee48..abbcaa1526 100644
--- a/docs/docbook/xslt/db2latex/revision.mod.xsl
+++ b/docs/docbook/xslt/db2latex/revision.mod.xsl
@@ -1,8 +1,8 @@
<?xml version='1.0'?>
<!--#############################################################################
-| $Id: revision.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+| $Id: revision.mod.xsl,v 1.1.2.1 2003/05/01 14:06:15 jelmer Exp $
|- #############################################################################
-| $Author: ab $
+| $Author: jelmer $
|
| PURPOSE:
+ ############################################################################## -->
@@ -19,7 +19,7 @@
<doc:reference id="revision" xmlns="">
<referenceinfo>
<releaseinfo role="meta">
- $Id: revision.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+ $Id: revision.mod.xsl,v 1.1.2.1 2003/05/01 14:06:15 jelmer Exp $
</releaseinfo>
<authorgroup>
<author> <firstname>Ramon</firstname> <surname>Casellas</surname> </author>
diff --git a/docs/docbook/xslt/db2latex/sections.mod.xsl b/docs/docbook/xslt/db2latex/sections.mod.xsl
index f81524d51d..8ae802dce2 100644
--- a/docs/docbook/xslt/db2latex/sections.mod.xsl
+++ b/docs/docbook/xslt/db2latex/sections.mod.xsl
@@ -1,8 +1,8 @@
<?xml version='1.0'?>
<!--#############################################################################
-| $Id: sections.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+| $Id: sections.mod.xsl,v 1.1.2.1 2003/05/01 14:06:15 jelmer Exp $
|- #############################################################################
-| $Author: ab $
+| $Author: jelmer $
|
| PURPOSE: sections.
| PENDING:
@@ -22,7 +22,7 @@
<doc:reference id="sections" xmlns="">
<referenceinfo>
<releaseinfo role="meta">
- $Id: sections.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+ $Id: sections.mod.xsl,v 1.1.2.1 2003/05/01 14:06:15 jelmer Exp $
</releaseinfo>
<authogroup>
<author> <firstname>Ramon</firstname> <surname>Casellas</surname> </author>
diff --git a/docs/docbook/xslt/db2latex/set.mod.xsl b/docs/docbook/xslt/db2latex/set.mod.xsl
index 9c45efec52..f3843498b6 100644
--- a/docs/docbook/xslt/db2latex/set.mod.xsl
+++ b/docs/docbook/xslt/db2latex/set.mod.xsl
@@ -1,8 +1,8 @@
<?xml version='1.0'?>
<!--#############################################################################
-| $Id: set.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+| $Id: set.mod.xsl,v 1.1.2.1 2003/05/01 14:06:15 jelmer Exp $
|- #############################################################################
-| $Author: ab $
+| $Author: jelmer $
|
| PURPOSE:
+ ############################################################################## -->
@@ -18,7 +18,7 @@
<doc:reference id="set" xmlns="">
<referenceinfo>
<releaseinfo role="meta">
- $Id: set.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+ $Id: set.mod.xsl,v 1.1.2.1 2003/05/01 14:06:15 jelmer Exp $
</releaseinfo>
<authorgroup>
<author> <firstname>Ramon</firstname> <surname>Casellas</surname> </author>
diff --git a/docs/docbook/xslt/db2latex/sgmltag.mod.xsl b/docs/docbook/xslt/db2latex/sgmltag.mod.xsl
index 8c0c57d83f..82bba79fa0 100644
--- a/docs/docbook/xslt/db2latex/sgmltag.mod.xsl
+++ b/docs/docbook/xslt/db2latex/sgmltag.mod.xsl
@@ -1,8 +1,8 @@
<?xml version='1.0'?>
<!--#############################################################################
-| $Id: sgmltag.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+| $Id: sgmltag.mod.xsl,v 1.1.2.1 2003/05/01 14:06:15 jelmer Exp $
|- #############################################################################
-| $Author: ab $
+| $Author: jelmer $
|
| PURPOSE:
+ ############################################################################## -->
@@ -19,7 +19,7 @@
<doc:reference id="sgmltag" xmlns="">
<referenceinfo>
<releaseinfo role="meta">
- $Id: sgmltag.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+ $Id: sgmltag.mod.xsl,v 1.1.2.1 2003/05/01 14:06:15 jelmer Exp $
</releaseinfo>
<authogroup>
<author> <firstname>Ramon</firstname> <surname>Casellas</surname> </author>
diff --git a/docs/docbook/xslt/db2latex/synop-oop.mod.xsl b/docs/docbook/xslt/db2latex/synop-oop.mod.xsl
index 1b5d660aac..146849dd5e 100644
--- a/docs/docbook/xslt/db2latex/synop-oop.mod.xsl
+++ b/docs/docbook/xslt/db2latex/synop-oop.mod.xsl
@@ -2,9 +2,9 @@
<!DOCTYPE xsl:stylesheet [ <!ENTITY RE "&#10;"> ]>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version='1.0'>
<!--#############################################################################
- | $Id: synop-oop.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+ | $Id: synop-oop.mod.xsl,v 1.1.2.1 2003/05/01 14:06:15 jelmer Exp $
|- #############################################################################
- | $Author: ab $
+ | $Author: jelmer $
|
| PURPOSE:
+ ############################################################################## -->
diff --git a/docs/docbook/xslt/db2latex/synop-struct.mod.xsl b/docs/docbook/xslt/db2latex/synop-struct.mod.xsl
index 1fef51e62e..c6cbb15392 100644
--- a/docs/docbook/xslt/db2latex/synop-struct.mod.xsl
+++ b/docs/docbook/xslt/db2latex/synop-struct.mod.xsl
@@ -1,8 +1,8 @@
<?xml version='1.0'?>
<!--#############################################################################
-| $Id: synop-struct.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+| $Id: synop-struct.mod.xsl,v 1.1.2.1 2003/05/01 14:06:15 jelmer Exp $
|- #############################################################################
-| $Author: ab $
+| $Author: jelmer $
|
| PURPOSE:
+ ############################################################################## -->
diff --git a/docs/docbook/xslt/db2latex/table.mod.xsl b/docs/docbook/xslt/db2latex/table.mod.xsl
index 31085b9093..b2d2a2a7f4 100644
--- a/docs/docbook/xslt/db2latex/table.mod.xsl
+++ b/docs/docbook/xslt/db2latex/table.mod.xsl
@@ -1,8 +1,8 @@
<?xml version='1.0'?>
<!--#############################################################################
-| $Id: table.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+| $Id: table.mod.xsl,v 1.1.2.1 2003/05/01 14:06:15 jelmer Exp $
|- #############################################################################
-| $Author: ab $
+| $Author: jelmer $
|
| PURPOSE:
+ ############################################################################## -->
@@ -18,7 +18,7 @@
<doc:reference id="table" xmlns="">
<referenceinfo>
<releaseinfo role="meta">
- $Id: table.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+ $Id: table.mod.xsl,v 1.1.2.1 2003/05/01 14:06:15 jelmer Exp $
</releaseinfo>
<authorgroup>
<firstname>Ramon</firstname> <surname>Casellas</surname>
diff --git a/docs/docbook/xslt/db2latex/texmath.mod.xsl b/docs/docbook/xslt/db2latex/texmath.mod.xsl
index 84becee530..8f6724fb86 100644
--- a/docs/docbook/xslt/db2latex/texmath.mod.xsl
+++ b/docs/docbook/xslt/db2latex/texmath.mod.xsl
@@ -1,8 +1,8 @@
<?xml version='1.0'?>
<!--#############################################################################
-| $Id: texmath.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+| $Id: texmath.mod.xsl,v 1.1.2.1 2003/05/01 14:06:15 jelmer Exp $
|- #############################################################################
-| $Author: ab $
+| $Author: jelmer $
|
| PURPOSE:
+ ############################################################################## -->
@@ -20,7 +20,7 @@
<doc:reference id="texmath" xmlns="">
<referenceinfo>
<releaseinfo role="meta">
- $Id: texmath.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+ $Id: texmath.mod.xsl,v 1.1.2.1 2003/05/01 14:06:15 jelmer Exp $
</releaseinfo>
<authorgroup>
<author> <firstname>Ramon</firstname> <surname>Casellas</surname> </author>
diff --git a/docs/docbook/xslt/db2latex/vars.mod.xsl b/docs/docbook/xslt/db2latex/vars.mod.xsl
index 764c3a0a95..a997437283 100644
--- a/docs/docbook/xslt/db2latex/vars.mod.xsl
+++ b/docs/docbook/xslt/db2latex/vars.mod.xsl
@@ -1,8 +1,8 @@
<?xml version='1.0'?>
<!--#############################################################################
-| $Id: vars.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+| $Id: vars.mod.xsl,v 1.1.2.1 2003/05/01 14:06:15 jelmer Exp $
|- #############################################################################
-| $Author: ab $
+| $Author: jelmer $
|
| PURPOSE: User and stylesheets XSL variables
+ ############################################################################## -->
@@ -15,7 +15,7 @@
<doc:reference id="vars" xmlns="">
<referenceinfo>
<releaseinfo role="meta">
- $Id: vars.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+ $Id: vars.mod.xsl,v 1.1.2.1 2003/05/01 14:06:15 jelmer Exp $
</releaseinfo>
<authorgroup>
<author><surname>Casellas</surname><firstname>Ramon</firstname></author>
@@ -43,7 +43,7 @@
<!--#############################################################################
| COMMON VARIABLES
|- #############################################################################
- | $Author: ab $
+ | $Author: jelmer $
|
+ ############################################################################## -->
<xsl:variable name="default-classsynopsis-language">java</xsl:variable>
@@ -180,7 +180,7 @@
<!--#############################################################################
| LaTeX VARIABLES
|- #############################################################################
- | $Author: ab $
+ | $Author: jelmer $
|
| PURPOSE: User and stylesheets XSL variables
+ ############################################################################## -->
@@ -859,7 +859,7 @@
<!--#############################################################################
| XSL VARIABLES FOR ARTICLES
|- #############################################################################
- | $Author: ab $
+ | $Author: jelmer $
|
+ ############################################################################## -->
diff --git a/docs/docbook/xslt/db2latex/verbatim.mod.xsl b/docs/docbook/xslt/db2latex/verbatim.mod.xsl
index a5bb09099a..03917f884f 100644
--- a/docs/docbook/xslt/db2latex/verbatim.mod.xsl
+++ b/docs/docbook/xslt/db2latex/verbatim.mod.xsl
@@ -1,8 +1,8 @@
<?xml version='1.0'?>
<!--#############################################################################
-| $Id: verbatim.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+| $Id: verbatim.mod.xsl,v 1.1.2.1 2003/05/01 14:06:15 jelmer Exp $
|- #############################################################################
-| $Author: ab $
+| $Author: jelmer $
|
| PURPOSE:
+ ############################################################################## -->
@@ -18,7 +18,7 @@
<doc:reference id="verbatim" xmlns="">
<referenceinfo>
<releaseinfo role="meta">
- $Id: verbatim.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+ $Id: verbatim.mod.xsl,v 1.1.2.1 2003/05/01 14:06:15 jelmer Exp $
</releaseinfo>
<authorgroup>
<author> <firstname>Ramon</firstname> <surname>Casellas</surname> </author>
diff --git a/docs/docbook/xslt/db2latex/xref.mod.xsl b/docs/docbook/xslt/db2latex/xref.mod.xsl
index ecd03153cb..070821070e 100644
--- a/docs/docbook/xslt/db2latex/xref.mod.xsl
+++ b/docs/docbook/xslt/db2latex/xref.mod.xsl
@@ -1,8 +1,8 @@
<?xml version='1.0'?>
<!--#############################################################################
-| $Id: xref.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+| $Id: xref.mod.xsl,v 1.1.2.1 2003/05/01 14:06:15 jelmer Exp $
|- #############################################################################
-| $Author: ab $
+| $Author: jelmer $
|
| PURPOSE: Manage XREFs
+ ############################################################################## -->
@@ -19,7 +19,7 @@
<doc:reference id="xref" xmlns="">
<referenceinfo>
<releaseinfo role="meta">
-$Id: xref.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+$Id: xref.mod.xsl,v 1.1.2.1 2003/05/01 14:06:15 jelmer Exp $
</releaseinfo>
<authorgroup>
<author> <surname>Casellas</surname><firstname>Ramon</firstname> </author>
diff --git a/docs/docbook/xslt/lists.mod.xsl b/docs/docbook/xslt/lists.mod.xsl
index 5fbd02de3a..22ac8d7113 100644
--- a/docs/docbook/xslt/lists.mod.xsl
+++ b/docs/docbook/xslt/lists.mod.xsl
@@ -1,8 +1,8 @@
<?xml version='1.0'?>
<!--#############################################################################
-| $Id: lists.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+| $Id: lists.mod.xsl,v 1.1.2.1 2003/05/01 14:06:14 jelmer Exp $
|- #############################################################################
-| $Author: ab $
+| $Author: jelmer $
|
| PURPOSE:
+ ############################################################################## -->
diff --git a/docs/docbook/xslt/table.mod.xsl b/docs/docbook/xslt/table.mod.xsl
index 336cac6dfb..1c648da322 100644
--- a/docs/docbook/xslt/table.mod.xsl
+++ b/docs/docbook/xslt/table.mod.xsl
@@ -1,8 +1,8 @@
<?xml version='1.0'?>
<!--#############################################################################
-| $Id: table.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+| $Id: table.mod.xsl,v 1.1.2.1 2003/05/01 14:06:14 jelmer Exp $
|- #############################################################################
-| $Author: ab $
+| $Author: jelmer $
|
| PURPOSE:
+ ############################################################################## -->
@@ -18,7 +18,7 @@
<doc:reference id="table" xmlns="">
<referenceinfo>
<releaseinfo role="meta">
- $Id: table.mod.xsl,v 1.1 2003/04/30 21:39:49 ab Exp $
+ $Id: table.mod.xsl,v 1.1.2.1 2003/05/01 14:06:14 jelmer Exp $
</releaseinfo>
<authorgroup>
<firstname>Ramon</firstname> <surname>Casellas</surname>
diff --git a/docs/faq/FAQ-Config.html b/docs/faq/FAQ-Config.html
deleted file mode 100644
index 785522ec4e..0000000000
--- a/docs/faq/FAQ-Config.html
+++ /dev/null
@@ -1,16 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter3.Configuration problems</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"><link rel="home" href="samba-faq.html" title="Samba FAQ"><link rel="up" href="samba-faq.html" title="Samba FAQ"><link rel="previous" href="FAQ-Install.html" title="Chapter2.Compiling and installing Samba on a Unix host"><link rel="next" href="FAQ-ClientApp.html" title="Chapter4.Specific client application problems"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter3.Configuration problems</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="FAQ-Install.html">Prev</a></td><th width="60%" align="center"></th><td width="20%" align="right"><a accesskey="n" href="FAQ-ClientApp.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="FAQ-Config"></a>Chapter3.Configuration problems</h2></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="FAQ-Config.html#id2811370">I have set 'force user' and samba still makes 'root' the owner of all the files I touch!</a></dt><dt><a href="FAQ-Config.html#id2811387">I have just installed samba and I'm trying to log in from Windows, but samba refuses all logins!</a></dt><dt><a href="FAQ-Config.html#id2811409">How can I make samba use netbios scope ID's</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2811370"></a>I have set 'force user' and samba still makes 'root' the owner of all the files I touch!</h2></div></div><p>
-When you have a user in 'admin users', samba will always do file operations for
-this user as 'root', even if 'force user' has been set.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2811387"></a>I have just installed samba and I'm trying to log in from Windows, but samba refuses all logins!</h2></div></div><p>
-Newer windows clients(NT4, 2000, XP) send encrypted passwords. Samba can't compare these
-passwords to the unix password database, so it needs it's own user database. You can
-add users to this database using &quot;smbpasswd -a user-name&quot;.
-</p><p>
-See also the &quot;User database&quot; chapter of the samba HOWTO Collection.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2811409"></a>How can I make samba use netbios scope ID's</h2></div></div><p>By default Samba uses a blank scope ID. This means
-all your windows boxes must also have a blank scope ID.
-If you really want to use a non-blank scope ID then you will
-need to use the 'netbios scope' smb.conf option.
-All your PCs will need to have the same setting for
-this to work. Scope ID's are not recommended.</p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="FAQ-Install.html">Prev</a></td><td width="20%" align="center"><a accesskey="u" href="samba-faq.html">Up</a></td><td width="40%" align="right"><a accesskey="n" href="FAQ-ClientApp.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter2.Compiling and installing Samba on a Unix host</td><td width="20%" align="center"><a accesskey="h" href="samba-faq.html">Home</a></td><td width="40%" align="right" valign="top">Chapter4.Specific client application problems</td></tr></table></div></body></html>
diff --git a/docs/faq/FAQ-Printing.html b/docs/faq/FAQ-Printing.html
deleted file mode 100644
index a924d40cd5..0000000000
--- a/docs/faq/FAQ-Printing.html
+++ /dev/null
@@ -1,16 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter7.Printing problems</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"><link rel="home" href="samba-faq.html" title="Samba FAQ"><link rel="up" href="samba-faq.html" title="Samba FAQ"><link rel="previous" href="FAQ-features.html" title="Chapter6.Features"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter7.Printing problems</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="FAQ-features.html">Prev</a></td><th width="60%" align="center"></th><td width="20%" align="right"></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="FAQ-Printing"></a>Chapter7.Printing problems</h2></div><div><div class="author"><h3 class="author">Ronan Waide</h3></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="FAQ-Printing.html#id2875214">setdriver or cupsaddsmb failes</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2875214"></a>setdriver or cupsaddsmb failes</h2></div></div><p>
-setdriver expects the following setup:
-
-</p><table class="simplelist" border="0" summary="Simple list"><tr><td>you are a printer admin, or root. this is the smb.conf printer admin group, not the Printer Operators group in NT. I've not tried the latter, but I don't believe it will work based on the current code.</td></tr><tr><td>printer admins has to be defined in [global]</td></tr><tr><td>upload the driver files to \\server\print$\w32x86 and win40 as appropriate. DON'T put them in the 0 or 2 subdirectories.</td></tr><tr><td>Make sure that the user you're connecting as is able to write to the print$ directories</td></tr><tr><td>Use adddriver (with appropriate parameters) to create the driver. note, this will not just update samba's notion of drivers, it will also move the files from the w32x86 and win40 directories to an appropriate subdirectory (based on driver version, I think, but not important enough for me to find out)</td></tr><tr><td>Use setdriver to associate the driver with a printer</td></tr></table><p>
-</p><p>
-The setdriver call will fail if the printer doesn't already exist in
-samba's view of the world. Either create the printer in cups and
-restart samba, or create an add printer command (see smb.conf doco)
-and use RPC calls to create a printer. NB the add printer command MUST
-return a single line of text indicating which port the printer was
-added on. If it doesn't, Samba won't reload the printer
-definitions. Although samba doesn't really support the notion of
-ports, suitable add printer command and enumport command settings can
-allow you pretty good remote control of the samba printer setup.
-</p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="FAQ-features.html">Prev</a></td><td width="20%" align="center"><a accesskey="u" href="samba-faq.html">Up</a></td><td width="40%" align="right"></td></tr><tr><td width="40%" align="left" valign="top">Chapter6.Features</td><td width="20%" align="center"><a accesskey="h" href="samba-faq.html">Home</a></td><td width="40%" align="right" valign="top"></td></tr></table></div></body></html>
diff --git a/docs/faq/clientapp.html b/docs/faq/clientapp.html
new file mode 100644
index 0000000000..d24e778b2a
--- /dev/null
+++ b/docs/faq/clientapp.html
@@ -0,0 +1,250 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<HTML
+><HEAD
+><TITLE
+>Specific client application problems</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
+REL="HOME"
+TITLE="Samba FAQ"
+HREF="samba-faq.html"><LINK
+REL="PREVIOUS"
+TITLE="Configuration problems"
+HREF="config.html"><LINK
+REL="NEXT"
+TITLE="Common errors"
+HREF="errors.html"></HEAD
+><BODY
+CLASS="CHAPTER"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><TABLE
+SUMMARY="Header navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>Samba FAQ</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="config.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+></TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="errors.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="CHAPTER"
+><H1
+><A
+NAME="CLIENTAPP">Chapter 4. Specific client application problems</H1
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN174">4.1. MS Office Setup reports "Cannot change properties of '\MSOFFICE\SETUP.INI'"</H1
+><P
+>When installing MS Office on a Samba drive for which you have admin
+user permissions, ie. admin users = username, you will find the
+setup program unable to complete the installation.</P
+><P
+>To get around this problem, do the installation without admin user
+permissions The problem is that MS Office Setup checks that a file is
+rdonly by trying to open it for writing.</P
+><P
+>Admin users can always open a file for writing, as they run as root.
+You just have to install as a non-admin user and then use "chown -R"
+to fix the owner.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN179">4.2. How to use a Samba share as an administrative share for MS Office, etc.</H1
+><P
+>Microsoft Office products can be installed as an administrative installation
+from which the application can either be run off the administratively installed
+product that resides on a shared resource, or from which that product can be
+installed onto workstation clients.</P
+><P
+>The general mechanism for implementing an adminstrative installation involves
+running <B
+CLASS="COMMAND"
+>X:\setup /A</B
+>, where X is the drive letter of either CDROM or floppy.</P
+><P
+>This installation process will NOT install the product for use per se, but
+rather results in unpacking of the compressed distribution files into a target
+shared folder. For this process you need write privilidge to the share and it
+is desirable to enable file locking and share mode operation during this
+process.</P
+><P
+>Subsequent installation of MS Office from this share will FAIL unless certain
+precautions are taken. This failure will be caused by share mode operation
+which will prevent the MS Office installation process from re-opening various
+dynamic link library files and will cause sporadic file not found problems.</P
+><P
+></P
+><UL
+><LI
+><P
+>As soon as the administrative installation (unpacking) has completed
+set the following parameters on the share containing it:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+> [MSOP95]
+ path = /where_you_put_it
+ comment = Your comment
+ volume = "The_CD_ROM_Label"
+ read only = yes
+ available = yes
+ share modes = no
+ locking = no
+ browseable = yes
+ public = yes</PRE
+></P
+></LI
+><LI
+><P
+>Now you are ready to run the setup program from the Microsoft Windows
+workstation as follows: <B
+CLASS="COMMAND"
+>\\"Server_Name"\MSOP95\msoffice\setup</B
+></P
+></LI
+></UL
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN194">4.3. Microsoft Access database opening errors</H1
+><P
+>Here are some notes on running MS-Access on a Samba drive from <A
+HREF="stefank@esi.com.au"
+TARGET="_top"
+>Stefan Kjellberg</A
+></P
+><P
+><P
+></P
+><TABLE
+BORDER="0"
+><TBODY
+><TR
+><TD
+>Opening a database in 'exclusive' mode does NOT work. Samba ignores r/w/share modes on file open.</TD
+></TR
+><TR
+><TD
+>Make sure that you open the database as 'shared' and to 'lock modified records'</TD
+></TR
+><TR
+><TD
+>Of course locking must be enabled for the particular share (smb.conf)</TD
+></TR
+></TBODY
+></TABLE
+><P
+></P
+></P
+></DIV
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+SUMMARY="Footer navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="config.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="samba-faq.html"
+ACCESSKEY="H"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="errors.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>Configuration problems</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+>&nbsp;</TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>Common errors</TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+> \ No newline at end of file
diff --git a/docs/faq/errors.html b/docs/faq/errors.html
new file mode 100644
index 0000000000..dd105396ba
--- /dev/null
+++ b/docs/faq/errors.html
@@ -0,0 +1,314 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<HTML
+><HEAD
+><TITLE
+>Common errors</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
+REL="HOME"
+TITLE="Samba FAQ"
+HREF="samba-faq.html"><LINK
+REL="PREVIOUS"
+TITLE="Specific client application problems"
+HREF="clientapp.html"><LINK
+REL="NEXT"
+TITLE="Features"
+HREF="features.html"></HEAD
+><BODY
+CLASS="CHAPTER"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><TABLE
+SUMMARY="Header navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>Samba FAQ</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="clientapp.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+></TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="features.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="CHAPTER"
+><H1
+><A
+NAME="ERRORS">Chapter 5. Common errors</H1
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN205">5.1. Not listening for calling name</H1
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>Session request failed (131,129) with myname=HOBBES destname=CALVIN
+Not listening for calling name</PRE
+></P
+><P
+>If you get this when talking to a Samba box then it means that your
+global "hosts allow" or "hosts deny" settings are causing the Samba
+server to refuse the connection. </P
+><P
+>Look carefully at your "hosts allow" and "hosts deny" lines in the
+global section of smb.conf. </P
+><P
+>It can also be a problem with reverse DNS lookups not functioning
+correctly, leading to the remote host identity not being able to
+be confirmed, but that is less likely.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN212">5.2. System Error 1240</H1
+><P
+>System error 1240 means that the client is refusing to talk
+to a non-encrypting server. Microsoft changed WinNT in service
+pack 3 to refuse to connect to servers that do not support
+SMB password encryption.</P
+><P
+>There are two main solutions:
+<P
+></P
+><TABLE
+BORDER="0"
+><TBODY
+><TR
+><TD
+>enable SMB password encryption in Samba. See the encryption part of
+the samba HOWTO Collection</TD
+></TR
+><TR
+><TD
+>disable this new behaviour in NT. See the section about
+Windows NT in the chapter "Portability" of the samba HOWTO collection</TD
+></TR
+></TBODY
+></TABLE
+><P
+></P
+></P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN219">5.3. smbclient ignores -N !</H1
+><P
+><SPAN
+CLASS="QUOTE"
+>"When getting the list of shares available on a host using the command
+<B
+CLASS="COMMAND"
+>smbclient -N -L</B
+>
+the program always prompts for the password if the server is a Samba server.
+It also ignores the "-N" argument when querying some (but not all) of our
+NT servers."</SPAN
+></P
+><P
+>No, it does not ignore -N, it is just that your server rejected the
+null password in the connection, so smbclient prompts for a password
+to try again.</P
+><P
+>To get the behaviour that you probably want use <B
+CLASS="COMMAND"
+>smbclient -L host -U%</B
+></P
+><P
+>This will set both the username and password to null, which is
+an anonymous login for SMB. Using -N would only set the password
+to null, and this is not accepted as an anonymous login for most
+SMB servers.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN228">5.4. The data on the CD-Drive I've shared seems to be corrupted!</H1
+><P
+>Some OSes (notably Linux) default to auto detection of file type on
+cdroms and do cr/lf translation. This is a very bad idea when use with
+Samba. It causes all sorts of stuff ups.</P
+><P
+>To overcome this problem use conv=binary when mounting the cdrom
+before exporting it with Samba.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN232">5.5. Why can users access home directories of other users?</H1
+><P
+><SPAN
+CLASS="QUOTE"
+>"We are unable to keep individual users from mapping to any other user's
+home directory once they have supplied a valid password! They only need
+to enter their own password. I have not found *any* method that I can
+use to configure samba to enforce that only a user may map their own
+home directory."</SPAN
+></P
+><P
+><SPAN
+CLASS="QUOTE"
+>"User xyzzy can map his home directory. Once mapped user xyzzy can also map
+*anyone* elses home directory!"</SPAN
+></P
+><P
+>This is not a security flaw, it is by design. Samba allows
+users to have *exactly* the same access to the UNIX filesystem
+as they would if they were logged onto the UNIX box, except
+that it only allows such views onto the file system as are
+allowed by the defined shares.</P
+><P
+>This means that if your UNIX home directories are set up
+such that one user can happily cd into another users
+directory and do an ls, the UNIX security solution is to
+change the UNIX file permissions on the users home directories
+such that the cd and ls would be denied.</P
+><P
+>Samba tries very hard not to second guess the UNIX administrators
+security policies, and trusts the UNIX admin to set
+the policies and permissions he or she desires.</P
+><P
+>Samba does allow the setup you require when you have set the
+"only user = yes" option on the share, is that you have not set the
+valid users list for the share.</P
+><P
+>Note that only user works in conjunction with the users= list,
+so to get the behavior you require, add the line :
+<PRE
+CLASS="PROGRAMLISTING"
+>users = %S</PRE
+>
+this is equivalent to:
+<PRE
+CLASS="PROGRAMLISTING"
+>valid users = %S</PRE
+>
+to the definition of the [homes] share, as recommended in
+the smb.conf man page.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN245">5.6. Until a few minutes after samba has started, clients get the error "Domain Controller Unavailable"</H1
+><P
+>A domain controller has to announce on the network who it is. This usually takes a while.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN248">5.7. I'm getting "open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was Cannot assign requested" in the logs</H1
+><P
+>Your loopback device isn't working correctly. Make sure it's running.</P
+></DIV
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+SUMMARY="Footer navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="clientapp.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="samba-faq.html"
+ACCESSKEY="H"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="features.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>Specific client application problems</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+>&nbsp;</TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>Features</TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+> \ No newline at end of file
diff --git a/docs/faq/general.html b/docs/faq/general.html
new file mode 100644
index 0000000000..435a2282b4
--- /dev/null
+++ b/docs/faq/general.html
@@ -0,0 +1,439 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<HTML
+><HEAD
+><TITLE
+>General Information</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
+REL="HOME"
+TITLE="Samba FAQ"
+HREF="samba-faq.html"><LINK
+REL="PREVIOUS"
+TITLE="Samba FAQ"
+HREF="samba-faq.html"><LINK
+REL="NEXT"
+TITLE="Compiling and installing Samba on a Unix host"
+HREF="install.html"></HEAD
+><BODY
+CLASS="CHAPTER"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><TABLE
+SUMMARY="Header navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>Samba FAQ</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="samba-faq.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+></TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="install.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="CHAPTER"
+><H1
+><A
+NAME="GENERAL">Chapter 1. General Information</H1
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN12">1.1. Where can I get it?</H1
+><P
+>The Samba suite is available at the <A
+HREF="http://samba.org/"
+TARGET="_top"
+>samba website</A
+>.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN16">1.2. What do the version numbers mean?</H1
+><P
+>It is not recommended that you run a version of Samba with the word
+"alpha" in its name unless you know what you are doing and are willing
+to do some debugging. Many, many people just get the latest
+recommended stable release version and are happy. If you are brave, by
+all means take the plunge and help with the testing and development -
+but don't install it on your departmental server. Samba is typically
+very stable and safe, and this is mostly due to the policy of many
+public releases.</P
+><P
+>How the scheme works:
+<P
+></P
+><TABLE
+BORDER="0"
+><TBODY
+><TR
+><TD
+>When major changes are made the version number is increased. For
+example, the transition from 1.9.15 to 1.9.16. However, this version
+number will not appear immediately and people should continue to use
+1.9.15 for production systems (see next point.)</TD
+></TR
+><TR
+><TD
+>Just after major changes are made the software is considered
+unstable, and a series of alpha releases are distributed, for example
+1.9.16alpha1. These are for testing by those who know what they are
+doing. The "alpha" in the filename will hopefully scare off those who
+are just looking for the latest version to install.</TD
+></TR
+><TR
+><TD
+>When Andrew thinks that the alphas have stabilised to the point
+where he would recommend new users install it, he renames it to the
+same version number without the alpha, for example 1.9.16.</TD
+></TR
+><TR
+><TD
+>Inevitably bugs are found in the "stable" releases and minor patch
+levels are released which give us the pXX series, for example 1.9.16p2.</TD
+></TR
+></TBODY
+></TABLE
+><P
+></P
+></P
+><P
+>So the progression goes:
+
+<PRE
+CLASS="PROGRAMLISTING"
+>1.9.15p7 (production)
+1.9.15p8 (production)
+1.9.16alpha1 (test sites only)
+:
+1.9.16alpha20 (test sites only)
+1.9.16 (production)
+1.9.16p1 (production)</PRE
+></P
+><P
+>The above system means that whenever someone looks at the samba ftp
+site they will be able to grab the highest numbered release without an
+alpha in the name and be sure of getting the current recommended
+version.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN28">1.3. What platforms are supported?</H1
+><P
+>Many different platforms have run Samba successfully. The platforms
+most widely used and thus best tested are Linux and SunOS.</P
+><P
+>At time of writing, there is support (or has been support for in earlier
+versions):</P
+><P
+></P
+><TABLE
+BORDER="0"
+><TBODY
+><TR
+><TD
+>A/UX 3.0</TD
+></TR
+><TR
+><TD
+>AIX</TD
+></TR
+><TR
+><TD
+>Altos Series 386/1000</TD
+></TR
+><TR
+><TD
+>Amiga</TD
+></TR
+><TR
+><TD
+>Apollo Domain/OS sr10.3</TD
+></TR
+><TR
+><TD
+>BSDI </TD
+></TR
+><TR
+><TD
+>B.O.S. (Bull Operating System)</TD
+></TR
+><TR
+><TD
+>Cray, Unicos 8.0</TD
+></TR
+><TR
+><TD
+>Convex</TD
+></TR
+><TR
+><TD
+>DGUX. </TD
+></TR
+><TR
+><TD
+>DNIX.</TD
+></TR
+><TR
+><TD
+>FreeBSD</TD
+></TR
+><TR
+><TD
+>HP-UX</TD
+></TR
+><TR
+><TD
+>Intergraph. </TD
+></TR
+><TR
+><TD
+>Linux with/without shadow passwords and quota</TD
+></TR
+><TR
+><TD
+>LYNX 2.3.0</TD
+></TR
+><TR
+><TD
+>MachTen (a unix like system for Macintoshes)</TD
+></TR
+><TR
+><TD
+>Motorola 88xxx/9xx range of machines</TD
+></TR
+><TR
+><TD
+>NetBSD</TD
+></TR
+><TR
+><TD
+>NEXTSTEP Release 2.X, 3.0 and greater (including OPENSTEP for Mach).</TD
+></TR
+><TR
+><TD
+>OS/2 using EMX 0.9b</TD
+></TR
+><TR
+><TD
+>OSF1</TD
+></TR
+><TR
+><TD
+>QNX 4.22</TD
+></TR
+><TR
+><TD
+>RiscIX. </TD
+></TR
+><TR
+><TD
+>RISCOs 5.0B</TD
+></TR
+><TR
+><TD
+>SEQUENT. </TD
+></TR
+><TR
+><TD
+>SCO (including: 3.2v2, European dist., OpenServer 5)</TD
+></TR
+><TR
+><TD
+>SGI.</TD
+></TR
+><TR
+><TD
+>SMP_DC.OSx v1.1-94c079 on Pyramid S series</TD
+></TR
+><TR
+><TD
+>SONY NEWS, NEWS-OS (4.2.x and 6.1.x)</TD
+></TR
+><TR
+><TD
+>SUNOS 4</TD
+></TR
+><TR
+><TD
+>SUNOS 5.2, 5.3, and 5.4 (Solaris 2.2, 2.3, and '2.4 and later')</TD
+></TR
+><TR
+><TD
+>Sunsoft ISC SVR3V4</TD
+></TR
+><TR
+><TD
+>SVR4</TD
+></TR
+><TR
+><TD
+>System V with some berkely extensions (Motorola 88k R32V3.2).</TD
+></TR
+><TR
+><TD
+>ULTRIX.</TD
+></TR
+><TR
+><TD
+>UNIXWARE</TD
+></TR
+><TR
+><TD
+>UXP/DS</TD
+></TR
+></TBODY
+></TABLE
+><P
+></P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN71">1.4. How do I subscribe to the Samba Mailing Lists?</H1
+><P
+>Look at <A
+HREF="http://samba.org/samba/archives.html"
+TARGET="_top"
+>the samba mailing list page</A
+></P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN75">1.5. Pizza supply details</H1
+><P
+>Those who have registered in the Samba survey as "Pizza Factory" will
+already know this, but the rest may need some help. Andrew doesn't ask
+for payment, but he does appreciate it when people give him
+pizza. This calls for a little organisation when the pizza donor is
+twenty thousand kilometres away, but it has been done.</P
+><P
+>Method 1: Ring up your local branch of an international pizza chain
+and see if they honour their vouchers internationally. Pizza Hut do,
+which is how the entire Canberra Linux Users Group got to eat pizza
+one night, courtesy of someone in the US.</P
+><P
+>Method 2: Ring up a local pizza shop in Canberra and quote a credit
+card number for a certain amount, and tell them that Andrew will be
+collecting it (don't forget to tell him.) One kind soul from Germany
+did this.</P
+><P
+>Method 3: Purchase a pizza voucher from your local pizza shop that has
+no international affiliations and send it to Andrew. It is completely
+useless but he can hang it on the wall next to the one he already has
+from Germany :-)</P
+><P
+>Method 4: Air freight him a pizza with your favourite regional
+flavours. It will probably get stuck in customs or torn apart by
+hungry sniffer dogs but it will have been a noble gesture.</P
+></DIV
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+SUMMARY="Footer navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="samba-faq.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="samba-faq.html"
+ACCESSKEY="H"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="install.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>Samba FAQ</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+>&nbsp;</TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>Compiling and installing Samba on a Unix host</TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+> \ No newline at end of file
diff --git a/docs/faq/install.html b/docs/faq/install.html
new file mode 100644
index 0000000000..e647aef6d4
--- /dev/null
+++ b/docs/faq/install.html
@@ -0,0 +1,502 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<HTML
+><HEAD
+><TITLE
+>Compiling and installing Samba on a Unix host</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
+REL="HOME"
+TITLE="Samba FAQ"
+HREF="samba-faq.html"><LINK
+REL="PREVIOUS"
+TITLE="General Information"
+HREF="general.html"><LINK
+REL="NEXT"
+TITLE="Configuration problems"
+HREF="config.html"></HEAD
+><BODY
+CLASS="CHAPTER"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><TABLE
+SUMMARY="Header navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>Samba FAQ</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="general.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+></TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="config.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="CHAPTER"
+><H1
+><A
+NAME="INSTALL">Chapter 2. Compiling and installing Samba on a Unix host</H1
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN84">2.1. I can't see the Samba server in any browse lists!</H1
+><P
+>See Browsing.html in the docs directory of the samba source
+for more information on browsing.</P
+><P
+>If your GUI client does not permit you to select non-browsable
+servers, you may need to do so on the command line. For example, under
+Lan Manager you might connect to the above service as disk drive M:
+thusly:
+<PRE
+CLASS="PROGRAMLISTING"
+> net use M: \\mary\fred</PRE
+>
+The details of how to do this and the specific syntax varies from
+client to client - check your client's documentation.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN89">2.2. Some files that I KNOW are on the server doesn't show up when I view the files from my client!</H1
+><P
+>See the next question.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN92">2.3. Some files on the server show up with really wierd filenames when I view the files from my client!</H1
+><P
+>If you check what files are not showing up, you will note that they
+are files which contain upper case letters or which are otherwise not
+DOS-compatible (ie, they are not legal DOS filenames for some reason).</P
+><P
+>The Samba server can be configured either to ignore such files
+completely, or to present them to the client in "mangled" form. If you
+are not seeing the files at all, the Samba server has most likely been
+configured to ignore them. Consult the man page smb.conf(5) for
+details of how to change this - the parameter you need to set is
+"mangled names = yes".</P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN96">2.4. My client reports "cannot locate specified computer" or similar</H1
+><P
+>This indicates one of three things: You supplied an incorrect server
+name, the underlying TCP/IP layer is not working correctly, or the
+name you specified cannot be resolved.</P
+><P
+>After carefully checking that the name you typed is the name you
+should have typed, try doing things like pinging a host or telnetting
+to somewhere on your network to see if TCP/IP is functioning OK. If it
+is, the problem is most likely name resolution.</P
+><P
+>If your client has a facility to do so, hardcode a mapping between the
+hosts IP and the name you want to use. For example, with Lan Manager
+or Windows for Workgroups you would put a suitable entry in the file
+LMHOSTS. If this works, the problem is in the communication between
+your client and the netbios name server. If it does not work, then
+there is something fundamental wrong with your naming and the solution
+is beyond the scope of this document.</P
+><P
+>If you do not have any server on your subnet supplying netbios name
+resolution, hardcoded mappings are your only option. If you DO have a
+netbios name server running (such as the Samba suite's nmbd program),
+the problem probably lies in the way it is set up. Refer to Section
+Two of this FAQ for more ideas.</P
+><P
+>By the way, remember to REMOVE the hardcoded mapping before further
+tests :-)</P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN103">2.5. My client reports "cannot locate specified share name" or similar</H1
+><P
+>This message indicates that your client CAN locate the specified
+server, which is a good start, but that it cannot find a service of
+the name you gave.</P
+><P
+>The first step is to check the exact name of the service you are
+trying to connect to (consult your system administrator). Assuming it
+exists and you specified it correctly (read your client's docs on how
+to specify a service name correctly), read on:</P
+><P
+></P
+><TABLE
+BORDER="0"
+><TBODY
+><TR
+><TD
+>Many clients cannot accept or use service names longer than eight characters.</TD
+></TR
+><TR
+><TD
+>Many clients cannot accept or use service names containing spaces.</TD
+></TR
+><TR
+><TD
+>Some servers (not Samba though) are case sensitive with service names.</TD
+></TR
+><TR
+><TD
+>Some clients force service names into upper case.</TD
+></TR
+></TBODY
+></TABLE
+><P
+></P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN112">2.6. Printing doesn't work</H1
+><P
+>Make sure that the specified print command for the service you are
+connecting to is correct and that it has a fully-qualified path (eg.,
+use "/usr/bin/lpr" rather than just "lpr").</P
+><P
+>Make sure that the spool directory specified for the service is
+writable by the user connected to the service. In particular the user
+"nobody" often has problems with printing, even if it worked with an
+earlier version of Samba. Try creating another guest user other than
+"nobody".</P
+><P
+>Make sure that the user specified in the service is permitted to use
+the printer.</P
+><P
+>Check the debug log produced by smbd. Search for the printer name and
+see if the log turns up any clues. Note that error messages to do with
+a service ipc$ are meaningless - they relate to the way the client
+attempts to retrieve status information when using the LANMAN1
+protocol.</P
+><P
+>If using WfWg then you need to set the default protocol to TCP/IP, not
+Netbeui. This is a WfWg bug.</P
+><P
+>If using the Lanman1 protocol (the default) then try switching to
+coreplus. Also not that print status error messages don't mean
+printing won't work. The print status is received by a different
+mechanism.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN120">2.7. My client reports "This server is not configured to list shared resources"</H1
+><P
+>Your guest account is probably invalid for some reason. Samba uses the
+guest account for browsing in smbd. Check that your guest account is
+valid.</P
+><P
+>See also 'guest account' in smb.conf man page.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN124">2.8. Log message "you appear to have a trapdoor uid system"</H1
+><P
+>This can have several causes. It might be because you are using a uid
+or gid of 65535 or -1. This is a VERY bad idea, and is a big security
+hole. Check carefully in your /etc/passwd file and make sure that no
+user has uid 65535 or -1. Especially check the "nobody" user, as many
+broken systems are shipped with nobody setup with a uid of 65535.</P
+><P
+>It might also mean that your OS has a trapdoor uid/gid system :-)</P
+><P
+>This means that once a process changes effective uid from root to
+another user it can't go back to root. Unfortunately Samba relies on
+being able to change effective uid from root to non-root and back
+again to implement its security policy. If your OS has a trapdoor uid
+system this won't work, and several things in Samba may break. Less
+things will break if you use user or server level security instead of
+the default share level security, but you may still strike
+problems.</P
+><P
+>The problems don't give rise to any security holes, so don't panic,
+but it does mean some of Samba's capabilities will be unavailable.
+In particular you will not be able to connect to the Samba server as
+two different uids at once. This may happen if you try to print as a
+"guest" while accessing a share as a normal user. It may also affect
+your ability to list the available shares as this is normally done as
+the guest user.</P
+><P
+>Complain to your OS vendor and ask them to fix their system.</P
+><P
+>Note: the reason why 65535 is a VERY bad choice of uid and gid is that
+it casts to -1 as a uid, and the setreuid() system call ignores (with
+no error) uid changes to -1. This means any daemon attempting to run
+as uid 65535 will actually run as root. This is not good!</P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN132">2.9. Why are my file's timestamps off by an hour, or by a few hours?</H1
+><P
+>This is from Paul Eggert eggert@twinsun.com.</P
+><P
+>Most likely it's a problem with your time zone settings.</P
+><P
+>Internally, Samba maintains time in traditional Unix format,
+namely, the number of seconds since 1970-01-01 00:00:00 Universal Time
+(or ``GMT''), not counting leap seconds.</P
+><P
+>On the server side, Samba uses the Unix TZ variable to convert
+internal timestamps to and from local time. So on the server side, there are
+two things to get right.
+<P
+></P
+><TABLE
+BORDER="0"
+><TBODY
+><TR
+><TD
+>The Unix system clock must have the correct Universal time. Use the shell command "sh -c 'TZ=UTC0 date'" to check this.</TD
+></TR
+><TR
+><TD
+>The TZ environment variable must be set on the server before Samba is invoked. The details of this depend on the server OS, but typically you must edit a file whose name is /etc/TIMEZONE or /etc/default/init, or run the command `zic -l'.</TD
+></TR
+></TBODY
+></TABLE
+><P
+></P
+></P
+><P
+>TZ must have the correct value.</P
+><P
+>If possible, use geographical time zone settings
+(e.g. TZ='America/Los_Angeles' or perhaps
+ TZ=':US/Pacific'). These are supported by most
+popular Unix OSes, are easier to get right, and are
+more accurate for historical timestamps. If your
+operating system has out-of-date tables, you should be
+able to update them from the public domain time zone
+tables at <A
+HREF="ftp://elsie.nci.nih.gov/pub/"
+TARGET="_top"
+>ftp://elsie.nci.nih.gov/pub/</A
+>.</P
+><P
+>If your system does not support geographical timezone
+settings, you must use a Posix-style TZ strings, e.g.
+TZ='PST8PDT,M4.1.0/2,M10.5.0/2' for US Pacific time.
+Posix TZ strings can take the following form (with optional
+ items in brackets):
+<PRE
+CLASS="PROGRAMLISTING"
+> StdOffset[Dst[Offset],Date/Time,Date/Time]</PRE
+>
+ where:</P
+><P
+><P
+></P
+><TABLE
+BORDER="0"
+><TBODY
+><TR
+><TD
+>`Std' is the standard time designation (e.g. `PST').</TD
+></TR
+><TR
+><TD
+>`Offset' is the number of hours behind UTC (e.g. `8').
+Prepend a `-' if you are ahead of UTC, and
+append `:30' if you are at a half-hour offset.
+Omit all the remaining items if you do not use
+daylight-saving time.</TD
+></TR
+><TR
+><TD
+>`Dst' is the daylight-saving time designation
+(e.g. `PDT').</TD
+></TR
+><TR
+><TD
+>The optional second `Offset' is the number of
+hours that daylight-saving time is behind UTC.
+The default is 1 hour ahead of standard time.</TD
+></TR
+><TR
+><TD
+>`Date/Time,Date/Time' specify when daylight-saving
+time starts and ends. The format for a date is
+`Mm.n.d', which specifies the dth day (0 is Sunday)
+of the nth week of the mth month, where week 5 means
+the last such day in the month. The format for a
+time is [h]h[:mm[:ss]], using a 24-hour clock.</TD
+></TR
+></TBODY
+></TABLE
+><P
+></P
+></P
+><P
+>Other Posix string formats are allowed but you don't want
+to know about them.</P
+><P
+>On the client side, you must make sure that your client's clock and
+time zone is also set appropriately. [[I don't know how to do this.]]
+Samba traditionally has had many problems dealing with time zones, due
+to the bizarre ways that Microsoft network protocols handle time
+zones. </P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN155">2.10. How do I set the printer driver name correctly?</H1
+><P
+>Question:
+<SPAN
+CLASS="QUOTE"
+>" On NT, I opened "Printer Manager" and "Connect to Printer".
+ Enter ["\\ptdi270\ps1"] in the box of printer. I got the
+ following error message
+ "</SPAN
+></P
+><P
+> <PRE
+CLASS="PROGRAMLISTING"
+> You do not have sufficient access to your machine
+ to connect to the selected printer, since a driver
+ needs to be installed locally.
+ </PRE
+>
+ </P
+><P
+>Answer:</P
+><P
+>In the more recent versions of Samba you can now set the "printer
+driver" in smb.conf. This tells the client what driver to use. For
+example:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+> printer driver = HP LaserJet 4L</PRE
+></P
+><P
+>With this, NT knows to use the right driver. You have to get this string
+exactly right.</P
+><P
+>To find the exact string to use, you need to get to the dialog box in
+your client where you select which printer driver to install. The
+correct strings for all the different printers are shown in a listbox
+in that dialog box.</P
+></DIV
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+SUMMARY="Footer navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="general.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="samba-faq.html"
+ACCESSKEY="H"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="config.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>General Information</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+>&nbsp;</TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>Configuration problems</TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+> \ No newline at end of file
diff --git a/docs/faq/samba-faq.html b/docs/faq/samba-faq.html
index d9c14289b1..ec46e078a3 100644
--- a/docs/faq/samba-faq.html
+++ b/docs/faq/samba-faq.html
@@ -1,11 +1,350 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Samba FAQ</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"><link rel="home" href="samba-faq.html" title="Samba FAQ"><link rel="next" href="FAQ-general.html" title="Chapter1.General Information"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Samba FAQ</th></tr><tr><td width="20%" align="left"></td><th width="60%" align="center"></th><td width="20%" align="right"><a accesskey="n" href="FAQ-general.html">Next</a></td></tr></table><hr></div><div class="book" lang="en"><div class="titlepage"><div><h1 class="title"><a name="Samba-FAQ"></a>Samba FAQ</h1></div><div><div class="author"><h3 class="author">Samba Team</h3></div></div><div><p class="pubdate">October 2002</p></div><hr></div><div class="dedication" lang="en"><div class="titlepage"><div><h2 class="title"><a name="id2860306"></a>Dedication</h2></div></div><p>
-This is the Frequently Asked Questions (FAQ) document for
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<HTML
+><HEAD
+><TITLE
+>Samba FAQ</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
+REL="NEXT"
+TITLE="General Information"
+HREF="general.html"></HEAD
+><BODY
+CLASS="BOOK"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="BOOK"
+><A
+NAME="SAMBA-FAQ"><DIV
+CLASS="TITLEPAGE"
+><H1
+CLASS="TITLE"
+><A
+NAME="SAMBA-FAQ">Samba FAQ</H1
+><H3
+CLASS="AUTHOR"
+><A
+NAME="AEN4">Samba Team</H3
+><HR></DIV
+><H1
+><A
+NAME="AEN7">Dedication</H1
+><P
+>This is the Frequently Asked Questions (FAQ) document for
Samba, the free and very popular SMB server product. An SMB server
allows file and printer connections from clients such as Windows,
OS/2, Linux and others. Current to version 3.0. Please send any
corrections to the samba documentation mailinglist at
-<a href="mailto:samba-doc@samba.org" target="_top">samba-doc@samba.org</a>.
+<A
+HREF="mailto:samba-doc@samba.org"
+TARGET="_top"
+>samba-doc@samba.org</A
+>.
This FAQ was based on the old Samba FAQ by Dan Shearer and Paul Blackman,
-and the old samba text documents which were mostly written by John Terpstra.
-</p></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt>1. <a href="FAQ-general.html">General Information</a></dt><dd><dl><dt><a href="FAQ-general.html#id2808041">Where can I get it?</a></dt><dt><a href="FAQ-general.html#id2808063">What do the version numbers mean?</a></dt><dt><a href="FAQ-general.html#id2808152">What platforms are supported?</a></dt><dt><a href="FAQ-general.html#id2808341">How do I subscribe to the Samba Mailing Lists?</a></dt></dl></dd><dt>2. <a href="FAQ-Install.html">Compiling and installing Samba on a Unix host</a></dt><dd><dl><dt><a href="FAQ-Install.html#id2808542">I can't see the Samba server in any browse lists!</a></dt><dt><a href="FAQ-Install.html#id2811456">Some files that I KNOW are on the server don't show up when I view the files from my client!</a></dt><dt><a href="FAQ-Install.html#id2811470">Some files on the server show up with really wierd filenames when I view the files from my client!</a></dt><dt><a href="FAQ-Install.html#id2860743">My client reports &quot;cannot locate specified computer&quot; or similar</a></dt><dt><a href="FAQ-Install.html#id2860797">My client reports &quot;cannot locate specified share name&quot; or similar</a></dt><dt><a href="FAQ-Install.html#id2806029">Printing doesn't work</a></dt><dt><a href="FAQ-Install.html#id2807904">My client reports &quot;This server is not configured to list shared resources&quot;</a></dt><dt><a href="FAQ-Install.html#id2807925">Log message &quot;you appear to have a trapdoor uid system&quot; </a></dt><dt><a href="FAQ-Install.html#id2807990">Why are my file's timestamps off by an hour, or by a few hours?</a></dt><dt><a href="FAQ-Install.html#id2811127">How do I set the printer driver name correctly?</a></dt></dl></dd><dt>3. <a href="FAQ-Config.html">Configuration problems</a></dt><dd><dl><dt><a href="FAQ-Config.html#id2811370">I have set 'force user' and samba still makes 'root' the owner of all the files I touch!</a></dt><dt><a href="FAQ-Config.html#id2811387">I have just installed samba and I'm trying to log in from Windows, but samba refuses all logins!</a></dt><dt><a href="FAQ-Config.html#id2811409">How can I make samba use netbios scope ID's</a></dt></dl></dd><dt>4. <a href="FAQ-ClientApp.html">Specific client application problems</a></dt><dd><dl><dt><a href="FAQ-ClientApp.html#id2808466">MS Office Setup reports &quot;Cannot change properties of '\\MSOFFICE\\SETUP.INI'&quot;</a></dt><dt><a href="FAQ-ClientApp.html#id2808495">How to use a Samba share as an administrative share for MS Office, etc.</a></dt><dt><a href="FAQ-ClientApp.html#id2808433">Microsoft Access database opening errors</a></dt></dl></dd><dt>5. <a href="FAQ-errors.html">Common errors</a></dt><dd><dl><dt><a href="FAQ-errors.html#id2811288">Not listening for calling name</a></dt><dt><a href="FAQ-errors.html#id2811329">System Error 1240</a></dt><dt><a href="FAQ-errors.html#id2811215">smbclient ignores -N !</a></dt><dt><a href="FAQ-errors.html#id2811270">The data on the CD-Drive I've shared seems to be corrupted!</a></dt><dt><a href="FAQ-errors.html#id2874350">Why can users access home directories of other users?</a></dt><dt><a href="FAQ-errors.html#id2874436">Until a few minutes after samba has started, clients get the error &quot;Domain Controller Unavailable&quot;</a></dt><dt><a href="FAQ-errors.html#id2874451">I'm getting &quot;open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was Cannot assign requested&quot; in the logs</a></dt></dl></dd><dt>6. <a href="FAQ-features.html">Features</a></dt><dd><dl><dt><a href="FAQ-features.html#id2874269">How can I prevent my samba server from being used to distribute the Nimda worm?</a></dt><dt><a href="FAQ-features.html#id2874209">How can I use samba as a fax server?</a></dt><dd><dl><dt><a href="FAQ-features.html#id2874628">Tools for printing faxes</a></dt><dt><a href="FAQ-features.html#id2874681">Making the fax-server</a></dt><dt><a href="FAQ-features.html#id2874774">Installing the client drivers</a></dt><dt><a href="FAQ-features.html#id2874858">Example smb.conf</a></dt></dl></dd><dt><a href="FAQ-features.html#id2874883">Samba doesn't work well together with DHCP!</a></dt><dt><a href="FAQ-features.html#id2874531">How can I assign NetBIOS names to clients with DHCP?</a></dt><dt><a href="FAQ-features.html#id2874581">How do I convert between unix and dos text formats?</a></dt><dt><a href="FAQ-features.html#id2874612">Does samba have wins replication support?</a></dt></dl></dd><dt>7. <a href="FAQ-Printing.html">Printing problems</a></dt><dd><dl><dt><a href="FAQ-Printing.html#id2875214">setdriver or cupsaddsmb failes</a></dt></dl></dd></dl></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"></td><td width="20%" align="center"></td><td width="40%" align="right"><a accesskey="n" href="FAQ-general.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top"></td><td width="20%" align="center"></td><td width="40%" align="right" valign="top">Chapter1.General Information</td></tr></table></div></body></html>
+and the old samba text documents which were mostly written by John Terpstra.</P
+><DIV
+CLASS="TOC"
+><DL
+><DT
+><B
+>Table of Contents</B
+></DT
+><DT
+>1. <A
+HREF="general.html"
+>General Information</A
+></DT
+><DD
+><DL
+><DT
+>1.1. <A
+HREF="general.html#AEN12"
+>Where can I get it?</A
+></DT
+><DT
+>1.2. <A
+HREF="general.html#AEN16"
+>What do the version numbers mean?</A
+></DT
+><DT
+>1.3. <A
+HREF="general.html#AEN28"
+>What platforms are supported?</A
+></DT
+><DT
+>1.4. <A
+HREF="general.html#AEN71"
+>How do I subscribe to the Samba Mailing Lists?</A
+></DT
+><DT
+>1.5. <A
+HREF="general.html#AEN75"
+>Pizza supply details</A
+></DT
+></DL
+></DD
+><DT
+>2. <A
+HREF="install.html"
+>Compiling and installing Samba on a Unix host</A
+></DT
+><DD
+><DL
+><DT
+>2.1. <A
+HREF="install.html#AEN84"
+>I can't see the Samba server in any browse lists!</A
+></DT
+><DT
+>2.2. <A
+HREF="install.html#AEN89"
+>Some files that I KNOW are on the server doesn't show up when I view the files from my client!</A
+></DT
+><DT
+>2.3. <A
+HREF="install.html#AEN92"
+>Some files on the server show up with really wierd filenames when I view the files from my client!</A
+></DT
+><DT
+>2.4. <A
+HREF="install.html#AEN96"
+>My client reports "cannot locate specified computer" or similar</A
+></DT
+><DT
+>2.5. <A
+HREF="install.html#AEN103"
+>My client reports "cannot locate specified share name" or similar</A
+></DT
+><DT
+>2.6. <A
+HREF="install.html#AEN112"
+>Printing doesn't work</A
+></DT
+><DT
+>2.7. <A
+HREF="install.html#AEN120"
+>My client reports "This server is not configured to list shared resources"</A
+></DT
+><DT
+>2.8. <A
+HREF="install.html#AEN124"
+>Log message "you appear to have a trapdoor uid system"</A
+></DT
+><DT
+>2.9. <A
+HREF="install.html#AEN132"
+>Why are my file's timestamps off by an hour, or by a few hours?</A
+></DT
+><DT
+>2.10. <A
+HREF="install.html#AEN155"
+>How do I set the printer driver name correctly?</A
+></DT
+></DL
+></DD
+><DT
+>3. <A
+HREF="config.html"
+>Configuration problems</A
+></DT
+><DD
+><DL
+><DT
+>3.1. <A
+HREF="config.html#AEN169"
+>I have set 'force user' and samba still makes 'root' the owner of all the files I touch!</A
+></DT
+></DL
+></DD
+><DT
+>4. <A
+HREF="clientapp.html"
+>Specific client application problems</A
+></DT
+><DD
+><DL
+><DT
+>4.1. <A
+HREF="clientapp.html#AEN174"
+>MS Office Setup reports "Cannot change properties of '\MSOFFICE\SETUP.INI'"</A
+></DT
+><DT
+>4.2. <A
+HREF="clientapp.html#AEN179"
+>How to use a Samba share as an administrative share for MS Office, etc.</A
+></DT
+><DT
+>4.3. <A
+HREF="clientapp.html#AEN194"
+>Microsoft Access database opening errors</A
+></DT
+></DL
+></DD
+><DT
+>5. <A
+HREF="errors.html"
+>Common errors</A
+></DT
+><DD
+><DL
+><DT
+>5.1. <A
+HREF="errors.html#AEN205"
+>Not listening for calling name</A
+></DT
+><DT
+>5.2. <A
+HREF="errors.html#AEN212"
+>System Error 1240</A
+></DT
+><DT
+>5.3. <A
+HREF="errors.html#AEN219"
+>smbclient ignores -N !</A
+></DT
+><DT
+>5.4. <A
+HREF="errors.html#AEN228"
+>The data on the CD-Drive I've shared seems to be corrupted!</A
+></DT
+><DT
+>5.5. <A
+HREF="errors.html#AEN232"
+>Why can users access home directories of other users?</A
+></DT
+><DT
+>5.6. <A
+HREF="errors.html#AEN245"
+>Until a few minutes after samba has started, clients get the error "Domain Controller Unavailable"</A
+></DT
+><DT
+>5.7. <A
+HREF="errors.html#AEN248"
+>I'm getting "open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was Cannot assign requested" in the logs</A
+></DT
+></DL
+></DD
+><DT
+>6. <A
+HREF="features.html"
+>Features</A
+></DT
+><DD
+><DL
+><DT
+>6.1. <A
+HREF="features.html#AEN253"
+>How can I prevent my samba server from being used to distribute the Nimda worm?</A
+></DT
+><DT
+>6.2. <A
+HREF="features.html#AEN267"
+>How can I use samba as a fax server?</A
+></DT
+><DD
+><DL
+><DT
+>6.2.1. <A
+HREF="features.html#AEN278"
+>Tools for printing faxes</A
+></DT
+><DT
+>6.2.2. <A
+HREF="features.html#AEN288"
+>Making the fax-server</A
+></DT
+><DT
+>6.2.3. <A
+HREF="features.html#AEN304"
+>Installing the client drivers</A
+></DT
+><DT
+>6.2.4. <A
+HREF="features.html#AEN318"
+>Example smb.conf</A
+></DT
+></DL
+></DD
+><DT
+>6.3. <A
+HREF="features.html#AEN322"
+>Samba doesn't work well together with DHCP!</A
+></DT
+><DT
+>6.4. <A
+HREF="features.html#AEN335"
+>How can I assign NetBIOS names to clients with DHCP?</A
+></DT
+><DT
+>6.5. <A
+HREF="features.html#AEN342"
+>How do I convert between unix and dos text formats?</A
+></DT
+><DT
+>6.6. <A
+HREF="features.html#AEN347"
+>Does samba have wins replication support?</A
+></DT
+></DL
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+SUMMARY="Footer navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>&nbsp;</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+>&nbsp;</TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="general.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>&nbsp;</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+>&nbsp;</TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>General Information</TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+> \ No newline at end of file
diff --git a/docs/htmldocs/Samba-Developers-Guide.html b/docs/htmldocs/Samba-Developers-Guide.html
index cc12fe60f8..b90d99bf66 100644
--- a/docs/htmldocs/Samba-Developers-Guide.html
+++ b/docs/htmldocs/Samba-Developers-Guide.html
@@ -1,176 +1,1091 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>SAMBA Developers Guide</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="book" lang="en"><div class="titlepage"><div><h1 class="title"><a name="Samba-Developers-Guide"></a>SAMBA Developers Guide</h1></div><div><div class="author"><h3 class="author">SAMBA Team</h3></div></div><hr></div><div class="dedication" lang="en"><div class="titlepage"><div><h2 class="title"><a name="id2791718"></a>Abstract</h2></div></div><p>
-<span class="emphasis"><em>Last Update</em></span> : Mon Sep 30 15:23:53 CDT 2002
-</p><p>
-This book is a collection of documents that might be useful for
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<HTML
+><HEAD
+><TITLE
+>SAMBA Developers Guide</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.77"></HEAD
+><BODY
+CLASS="BOOK"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="BOOK"
+><A
+NAME="SAMBA-DEVELOPERS-GUIDE"
+></A
+><DIV
+CLASS="TITLEPAGE"
+><H1
+CLASS="TITLE"
+><A
+NAME="SAMBA-DEVELOPERS-GUIDE"
+></A
+>SAMBA Developers Guide</H1
+><H3
+CLASS="AUTHOR"
+><A
+NAME="AEN4"
+></A
+>SAMBA Team</H3
+><HR></DIV
+><HR><H1
+><A
+NAME="AEN8"
+></A
+>Abstract</H1
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Last Update</I
+></SPAN
+> : Mon Sep 30 15:23:53 CDT 2002</P
+><P
+>This book is a collection of documents that might be useful for
people developing samba or those interested in doing so.
It's nothing more than a collection of documents written by samba developers about
the internals of various parts of samba and the SMB protocol. It's still incomplete.
The most recent version of this document
-can be found at <a href="http://devel.samba.org/" target="_top">http://devel.samba.org/</a>.
-Please send updates to <a href="mailto:jelmer@samba.org" target="_top">Jelmer Veenrooij</a>.
-</p><p>
-This documentation is distributed under the GNU General Public License (GPL)
+can be found at <A
+HREF="http://devel.samba.org/"
+TARGET="_top"
+>http://devel.samba.org/</A
+>.
+Please send updates to <A
+HREF="mailto:jelmer@samba.org"
+TARGET="_top"
+>jelmer@samba.org</A
+>.</P
+><P
+>This documentation is distributed under the GNU General Public License (GPL)
version 2. A copy of the license is included with the Samba source
-distribution. A copy can be found on-line at <a href="http://www.fsf.org/licenses/gpl.txt" target="_top">http://www.fsf.org/licenses/gpl.txt</a>
-</p></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt>1. <a href="#netbios">Definition of NetBIOS Protocol and Name Resolution Modes</a></dt><dd><dl><dt><a href="#id2791176">NETBIOS</a></dt><dt><a href="#id2791260">BROADCAST NetBIOS</a></dt><dt><a href="#id2791291">NBNS NetBIOS</a></dt></dl></dd><dt>2. <a href="#architecture">Samba Architecture</a></dt><dd><dl><dt><a href="#id2795118">Introduction</a></dt><dt><a href="#id2795170">Multithreading and Samba</a></dt><dt><a href="#id2790937">Threading smbd</a></dt><dt><a href="#id2843423">Threading nmbd</a></dt><dt><a href="#id2791332">nbmd Design</a></dt></dl></dd><dt>3. <a href="#debug">The samba DEBUG system</a></dt><dd><dl><dt><a href="#id2790677">New Output Syntax</a></dt><dt><a href="#id2791433">The DEBUG() Macro</a></dt><dt><a href="#id2791102">The DEBUGADD() Macro</a></dt><dt><a href="#id2790705">The DEBUGLVL() Macro</a></dt><dt><a href="#id2790812">New Functions</a></dt><dd><dl><dt><a href="#id2790819">dbgtext()</a></dt><dt><a href="#id2790839">dbghdr()</a></dt><dt><a href="#id2790862">format_debug_text()</a></dt></dl></dd></dl></dd><dt>4. <a href="#CodingSuggestions">Coding Suggestions</a></dt><dt>5. <a href="#internals">Samba Internals</a></dt><dd><dl><dt><a href="#id2857490">Character Handling</a></dt><dt><a href="#id2857515">The new functions</a></dt><dt><a href="#id2857977">Macros in byteorder.h</a></dt><dd><dl><dt><a href="#id2857991">CVAL(buf,pos)</a></dt><dt><a href="#id2858005">PVAL(buf,pos)</a></dt><dt><a href="#id2858019">SCVAL(buf,pos,val)</a></dt><dt><a href="#id2858032">SVAL(buf,pos)</a></dt><dt><a href="#id2858048">IVAL(buf,pos)</a></dt><dt><a href="#id2858062">SVALS(buf,pos)</a></dt><dt><a href="#id2858077">IVALS(buf,pos)</a></dt><dt><a href="#id2858091">SSVAL(buf,pos,val)</a></dt><dt><a href="#id2858106">SIVAL(buf,pos,val)</a></dt><dt><a href="#id2858120">SSVALS(buf,pos,val)</a></dt><dt><a href="#id2858134">SIVALS(buf,pos,val)</a></dt><dt><a href="#id2858149">RSVAL(buf,pos)</a></dt><dt><a href="#id2858163">RIVAL(buf,pos)</a></dt><dt><a href="#id2858177">RSSVAL(buf,pos,val)</a></dt><dt><a href="#id2858192">RSIVAL(buf,pos,val)</a></dt></dl></dd><dt><a href="#id2858208">LAN Manager Samba API</a></dt><dd><dl><dt><a href="#id2858243">Parameters</a></dt><dt><a href="#id2858395">Return value</a></dt></dl></dd><dt><a href="#id2858481">Code character table</a></dt></dl></dd><dt>6. <a href="#parsing">The smb.conf file</a></dt><dd><dl><dt><a href="#id2857849">Lexical Analysis</a></dt><dd><dl><dt><a href="#id2857787">Handling of Whitespace</a></dt><dt><a href="#id2858749">Handling of Line Continuation</a></dt><dt><a href="#id2858813">Line Continuation Quirks</a></dt></dl></dd><dt><a href="#id2858913">Syntax</a></dt><dd><dl><dt><a href="#id2858982">About params.c</a></dt></dl></dd></dl></dd><dt>7. <a href="#unix-smb">NetBIOS in a Unix World</a></dt><dd><dl><dt><a href="#id2858682">Introduction</a></dt><dt><a href="#id2858703">Usernames</a></dt><dt><a href="#id2858620">File Ownership</a></dt><dt><a href="#id2858644">Passwords</a></dt><dt><a href="#id2859208">Locking</a></dt><dt><a href="#id2859270">Deny Modes</a></dt><dt><a href="#id2859300">Trapdoor UIDs</a></dt><dt><a href="#id2859325">Port numbers</a></dt><dt><a href="#id2859371">Protocol Complexity</a></dt></dl></dd><dt>8. <a href="#tracing">Tracing samba system calls</a></dt><dt>9. <a href="#ntdomain">NT Domain RPC's</a></dt><dd><dl><dt><a href="#id2859563">Introduction</a></dt><dd><dl><dt><a href="#id2859980">Sources</a></dt><dt><a href="#id2860014">Credits</a></dt></dl></dd><dt><a href="#id2860053">Notes and Structures</a></dt><dd><dl><dt><a href="#id2860060">Notes</a></dt><dt><a href="#id2860137">Enumerations</a></dt><dt><a href="#id2860350">Structures</a></dt></dl></dd><dt><a href="#id2863307">MSRPC over Transact Named Pipe</a></dt><dd><dl><dt><a href="#id2863320">MSRPC Pipes</a></dt><dt><a href="#id2863422">Header</a></dt><dt><a href="#id2864296">Tail</a></dt><dt><a href="#id2864342">RPC Bind / Bind Ack</a></dt><dt><a href="#id2864522">NTLSA Transact Named Pipe</a></dt><dt><a href="#id2864687">LSA Open Policy</a></dt><dt><a href="#id2864813">LSA Query Info Policy</a></dt><dt><a href="#id2864921">LSA Enumerate Trusted Domains</a></dt><dt><a href="#id2865012">LSA Open Secret</a></dt><dt><a href="#id2865122">LSA Close</a></dt><dt><a href="#id2865188">LSA Lookup SIDS</a></dt><dt><a href="#id2865399">LSA Lookup Names</a></dt></dl></dd><dt><a href="#id2865625">NETLOGON rpc Transact Named Pipe</a></dt><dd><dl><dt><a href="#id2865786">LSA Request Challenge</a></dt><dt><a href="#id2865921">LSA Authenticate 2</a></dt><dt><a href="#id2866069">LSA Server Password Set</a></dt><dt><a href="#id2866185">LSA SAM Logon</a></dt><dt><a href="#id2866299">LSA SAM Logoff</a></dt></dl></dd><dt><a href="#id2866391">\\MAILSLOT\NET\NTLOGON</a></dt><dd><dl><dt><a href="#id2866408">Query for PDC</a></dt><dt><a href="#id2866670">SAM Logon</a></dt></dl></dd><dt><a href="#id2866996">SRVSVC Transact Named Pipe</a></dt><dd><dl><dt><a href="#id2867041">Net Share Enum</a></dt><dt><a href="#id2867261">Net Server Get Info</a></dt></dl></dd><dt><a href="#id2867378">Cryptographic side of NT Domain Authentication</a></dt><dd><dl><dt><a href="#id2867386">Definitions</a></dt><dt><a href="#id2867548">Protocol</a></dt><dt><a href="#id2867629">Comments</a></dt></dl></dd><dt><a href="#id2867679">SIDs and RIDs</a></dt><dd><dl><dt><a href="#id2867719">Well-known SIDs</a></dt><dt><a href="#id2868034">Well-known RIDS</a></dt></dl></dd></dl></dd><dt>10. <a href="#printing">Samba Printing Internals</a></dt><dd><dl><dt><a href="#id2859754">Abstract</a></dt><dt><a href="#id2859770">
-Printing Interface to Various Back ends
-</a></dt><dt><a href="#id2859712">
-Print Queue TDB's
-</a></dt><dt><a href="#id2868639">
-ChangeID and Client Caching of Printer Information
-</a></dt><dt><a href="#id2868653">
-Windows NT/2K Printer Change Notify
-</a></dt></dl></dd><dt>11. <a href="#wins">Samba WINS Internals</a></dt><dd><dl><dt><a href="#id2868400">WINS Failover</a></dt></dl></dd><dt>12. <a href="#sam">The Upcoming SAM System</a></dt><dd><dl><dt><a href="#id2869126">Security in the 'new SAM'</a></dt><dt><a href="#id2869257">Standalone from UNIX</a></dt><dt><a href="#id2869292">Handles and Races in the new SAM</a></dt><dt><a href="#id2869361">Layers</a></dt><dd><dl><dt><a href="#id2869368">Application</a></dt><dt><a href="#id2869384">SAM Interface</a></dt><dt><a href="#id2869412">SAM Modules</a></dt></dl></dd><dt><a href="#id2869434">SAM Modules</a></dt><dd><dl><dt><a href="#id2869441">Special Module: sam_passdb</a></dt><dt><a href="#id2869459">sam_ads</a></dt></dl></dd><dt><a href="#id2869498">Memory Management</a></dt><dt><a href="#id2869589">Testing</a></dt></dl></dd><dt>13. <a href="#pwencrypt">LanMan and NT Password Encryption</a></dt><dd><dl><dt><a href="#id2869092">Introduction</a></dt><dt><a href="#id2868961">How does it work?</a></dt><dt><a href="#id2869678">The smbpasswd file</a></dt></dl></dd><dt>14. <a href="#modules">Modules</a></dt><dd><dl><dt><a href="#id2870133">Advantages</a></dt><dt><a href="#id2869868">Loading modules</a></dt><dd><dl><dt><a href="#id2869901">Static modules</a></dt><dt><a href="#id2870337">Shared modules</a></dt></dl></dd><dt><a href="#id2870365">Writing modules</a></dt><dd><dl><dt><a href="#id2870425">Static/Shared selection in configure.in</a></dt></dl></dd></dl></dd><dt>15. <a href="#rpc-plugin">RPC Pluggable Modules</a></dt><dd><dl><dt><a href="#id2869935">About</a></dt><dt><a href="#id2869954">General Overview</a></dt></dl></dd><dt>16. <a href="#Packaging">Notes to packagers</a></dt><dd><dl><dt><a href="#id2870644">Versioning</a></dt><dt><a href="#id2870677">Modules</a></dt></dl></dd></dl></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="netbios"></a>Chapter1.Definition of NetBIOS Protocol and Name Resolution Modes</h2></div><div><div class="author"><h3 class="author">Luke Leighton</h3></div></div><div><p class="pubdate">12 June 1997</p></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2791176">NETBIOS</a></dt><dt><a href="#id2791260">BROADCAST NetBIOS</a></dt><dt><a href="#id2791291">NBNS NetBIOS</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2791176"></a>NETBIOS</h2></div></div><p>
-NetBIOS runs over the following tranports: TCP/IP; NetBEUI and IPX/SPX.
+distribution. A copy can be found on-line at <A
+HREF="http://www.fsf.org/licenses/gpl.txt"
+TARGET="_top"
+>http://www.fsf.org/licenses/gpl.txt</A
+></P
+><DIV
+CLASS="TOC"
+><DL
+><DT
+><B
+>Table of Contents</B
+></DT
+><DT
+>1. <A
+HREF="#NETBIOS"
+>Definition of NetBIOS Protocol and Name Resolution Modes</A
+></DT
+><DD
+><DL
+><DT
+>1.1. <A
+HREF="#AEN24"
+>NETBIOS</A
+></DT
+><DT
+>1.2. <A
+HREF="#AEN35"
+>BROADCAST NetBIOS</A
+></DT
+><DT
+>1.3. <A
+HREF="#AEN39"
+>NBNS NetBIOS</A
+></DT
+></DL
+></DD
+><DT
+>2. <A
+HREF="#ARCHITECTURE"
+>Samba Architecture</A
+></DT
+><DD
+><DL
+><DT
+>2.1. <A
+HREF="#AEN54"
+>Introduction</A
+></DT
+><DT
+>2.2. <A
+HREF="#AEN65"
+>Multithreading and Samba</A
+></DT
+><DT
+>2.3. <A
+HREF="#AEN70"
+>Threading smbd</A
+></DT
+><DT
+>2.4. <A
+HREF="#AEN86"
+>Threading nmbd</A
+></DT
+><DT
+>2.5. <A
+HREF="#AEN92"
+>nbmd Design</A
+></DT
+></DL
+></DD
+><DT
+>3. <A
+HREF="#DEBUG"
+>The samba DEBUG system</A
+></DT
+><DD
+><DL
+><DT
+>3.1. <A
+HREF="#AEN103"
+>New Output Syntax</A
+></DT
+><DT
+>3.2. <A
+HREF="#AEN128"
+>The DEBUG() Macro</A
+></DT
+><DT
+>3.3. <A
+HREF="#AEN151"
+>The DEBUGADD() Macro</A
+></DT
+><DT
+>3.4. <A
+HREF="#AEN159"
+>The DEBUGLVL() Macro</A
+></DT
+><DT
+>3.5. <A
+HREF="#AEN179"
+>New Functions</A
+></DT
+><DD
+><DL
+><DT
+>3.5.1. <A
+HREF="#AEN181"
+>dbgtext()</A
+></DT
+><DT
+>3.5.2. <A
+HREF="#AEN184"
+>dbghdr()</A
+></DT
+><DT
+>3.5.3. <A
+HREF="#AEN188"
+>format_debug_text()</A
+></DT
+></DL
+></DD
+></DL
+></DD
+><DT
+>4. <A
+HREF="#CODINGSUGGESTIONS"
+>Coding Suggestions</A
+></DT
+><DT
+>5. <A
+HREF="#INTERNALS"
+>Samba Internals</A
+></DT
+><DD
+><DL
+><DT
+>5.1. <A
+HREF="#AEN284"
+>Character Handling</A
+></DT
+><DT
+>5.2. <A
+HREF="#AEN288"
+>The new functions</A
+></DT
+><DT
+>5.3. <A
+HREF="#AEN317"
+>Macros in byteorder.h</A
+></DT
+><DD
+><DL
+><DT
+>5.3.1. <A
+HREF="#AEN320"
+>CVAL(buf,pos)</A
+></DT
+><DT
+>5.3.2. <A
+HREF="#AEN323"
+>PVAL(buf,pos)</A
+></DT
+><DT
+>5.3.3. <A
+HREF="#AEN326"
+>SCVAL(buf,pos,val)</A
+></DT
+><DT
+>5.3.4. <A
+HREF="#AEN329"
+>SVAL(buf,pos)</A
+></DT
+><DT
+>5.3.5. <A
+HREF="#AEN332"
+>IVAL(buf,pos)</A
+></DT
+><DT
+>5.3.6. <A
+HREF="#AEN335"
+>SVALS(buf,pos)</A
+></DT
+><DT
+>5.3.7. <A
+HREF="#AEN338"
+>IVALS(buf,pos)</A
+></DT
+><DT
+>5.3.8. <A
+HREF="#AEN341"
+>SSVAL(buf,pos,val)</A
+></DT
+><DT
+>5.3.9. <A
+HREF="#AEN344"
+>SIVAL(buf,pos,val)</A
+></DT
+><DT
+>5.3.10. <A
+HREF="#AEN347"
+>SSVALS(buf,pos,val)</A
+></DT
+><DT
+>5.3.11. <A
+HREF="#AEN350"
+>SIVALS(buf,pos,val)</A
+></DT
+><DT
+>5.3.12. <A
+HREF="#AEN353"
+>RSVAL(buf,pos)</A
+></DT
+><DT
+>5.3.13. <A
+HREF="#AEN356"
+>RIVAL(buf,pos)</A
+></DT
+><DT
+>5.3.14. <A
+HREF="#AEN359"
+>RSSVAL(buf,pos,val)</A
+></DT
+><DT
+>5.3.15. <A
+HREF="#AEN362"
+>RSIVAL(buf,pos,val)</A
+></DT
+></DL
+></DD
+><DT
+>5.4. <A
+HREF="#AEN365"
+>LAN Manager Samba API</A
+></DT
+><DD
+><DL
+><DT
+>5.4.1. <A
+HREF="#AEN371"
+>Parameters</A
+></DT
+><DT
+>5.4.2. <A
+HREF="#AEN406"
+>Return value</A
+></DT
+></DL
+></DD
+><DT
+>5.5. <A
+HREF="#AEN420"
+>Code character table</A
+></DT
+></DL
+></DD
+><DT
+>6. <A
+HREF="#PARSING"
+>The smb.conf file</A
+></DT
+><DD
+><DL
+><DT
+>6.1. <A
+HREF="#AEN451"
+>Lexical Analysis</A
+></DT
+><DD
+><DL
+><DT
+>6.1.1. <A
+HREF="#AEN472"
+>Handling of Whitespace</A
+></DT
+><DT
+>6.1.2. <A
+HREF="#AEN484"
+>Handling of Line Continuation</A
+></DT
+><DT
+>6.1.3. <A
+HREF="#AEN495"
+>Line Continuation Quirks</A
+></DT
+></DL
+></DD
+><DT
+>6.2. <A
+HREF="#AEN515"
+>Syntax</A
+></DT
+><DD
+><DL
+><DT
+>6.2.1. <A
+HREF="#AEN530"
+>About params.c</A
+></DT
+></DL
+></DD
+></DL
+></DD
+><DT
+>7. <A
+HREF="#UNIX-SMB"
+>NetBIOS in a Unix World</A
+></DT
+><DD
+><DL
+><DT
+>7.1. <A
+HREF="#AEN540"
+>Introduction</A
+></DT
+><DT
+>7.2. <A
+HREF="#AEN544"
+>Usernames</A
+></DT
+><DT
+>7.3. <A
+HREF="#AEN552"
+>File Ownership</A
+></DT
+><DT
+>7.4. <A
+HREF="#AEN557"
+>Passwords</A
+></DT
+><DT
+>7.5. <A
+HREF="#AEN563"
+>Locking</A
+></DT
+><DT
+>7.6. <A
+HREF="#AEN571"
+>Deny Modes</A
+></DT
+><DT
+>7.7. <A
+HREF="#AEN575"
+>Trapdoor UIDs</A
+></DT
+><DT
+>7.8. <A
+HREF="#AEN579"
+>Port numbers</A
+></DT
+><DT
+>7.9. <A
+HREF="#AEN584"
+>Protocol Complexity</A
+></DT
+></DL
+></DD
+><DT
+>8. <A
+HREF="#TRACING"
+>Tracing samba system calls</A
+></DT
+><DT
+>9. <A
+HREF="#NTDOMAIN"
+>NT Domain RPC's</A
+></DT
+><DD
+><DL
+><DT
+>9.1. <A
+HREF="#AEN652"
+>Introduction</A
+></DT
+><DD
+><DL
+><DT
+>9.1.1. <A
+HREF="#AEN688"
+>Sources</A
+></DT
+><DT
+>9.1.2. <A
+HREF="#AEN695"
+>Credits</A
+></DT
+></DL
+></DD
+><DT
+>9.2. <A
+HREF="#AEN702"
+>Notes and Structures</A
+></DT
+><DD
+><DL
+><DT
+>9.2.1. <A
+HREF="#AEN704"
+>Notes</A
+></DT
+><DT
+>9.2.2. <A
+HREF="#AEN717"
+>Enumerations</A
+></DT
+><DT
+>9.2.3. <A
+HREF="#AEN775"
+>Structures</A
+></DT
+></DL
+></DD
+><DT
+>9.3. <A
+HREF="#AEN1571"
+>MSRPC over Transact Named Pipe</A
+></DT
+><DD
+><DL
+><DT
+>9.3.1. <A
+HREF="#AEN1574"
+>MSRPC Pipes</A
+></DT
+><DT
+>9.3.2. <A
+HREF="#AEN1588"
+>Header</A
+></DT
+><DT
+>9.3.3. <A
+HREF="#AEN1842"
+>Tail</A
+></DT
+><DT
+>9.3.4. <A
+HREF="#AEN1854"
+>RPC Bind / Bind Ack</A
+></DT
+><DT
+>9.3.5. <A
+HREF="#AEN1898"
+>NTLSA Transact Named Pipe</A
+></DT
+><DT
+>9.3.6. <A
+HREF="#AEN1939"
+>LSA Open Policy</A
+></DT
+><DT
+>9.3.7. <A
+HREF="#AEN1973"
+>LSA Query Info Policy</A
+></DT
+><DT
+>9.3.8. <A
+HREF="#AEN2001"
+>LSA Enumerate Trusted Domains</A
+></DT
+><DT
+>9.3.9. <A
+HREF="#AEN2025"
+>LSA Open Secret</A
+></DT
+><DT
+>9.3.10. <A
+HREF="#AEN2054"
+>LSA Close</A
+></DT
+><DT
+>9.3.11. <A
+HREF="#AEN2071"
+>LSA Lookup SIDS</A
+></DT
+><DT
+>9.3.12. <A
+HREF="#AEN2130"
+>LSA Lookup Names</A
+></DT
+></DL
+></DD
+><DT
+>9.4. <A
+HREF="#AEN2193"
+>NETLOGON rpc Transact Named Pipe</A
+></DT
+><DD
+><DL
+><DT
+>9.4.1. <A
+HREF="#AEN2232"
+>LSA Request Challenge</A
+></DT
+><DT
+>9.4.2. <A
+HREF="#AEN2267"
+>LSA Authenticate 2</A
+></DT
+><DT
+>9.4.3. <A
+HREF="#AEN2306"
+>LSA Server Password Set</A
+></DT
+><DT
+>9.4.4. <A
+HREF="#AEN2335"
+>LSA SAM Logon</A
+></DT
+><DT
+>9.4.5. <A
+HREF="#AEN2359"
+>LSA SAM Logoff</A
+></DT
+></DL
+></DD
+><DT
+>9.5. <A
+HREF="#AEN2382"
+>\\MAILSLOT\NET\NTLOGON</A
+></DT
+><DD
+><DL
+><DT
+>9.5.1. <A
+HREF="#AEN2386"
+>Query for PDC</A
+></DT
+><DT
+>9.5.2. <A
+HREF="#AEN2460"
+>SAM Logon</A
+></DT
+></DL
+></DD
+><DT
+>9.6. <A
+HREF="#AEN2550"
+>SRVSVC Transact Named Pipe</A
+></DT
+><DD
+><DL
+><DT
+>9.6.1. <A
+HREF="#AEN2562"
+>Net Share Enum</A
+></DT
+><DT
+>9.6.2. <A
+HREF="#AEN2623"
+>Net Server Get Info</A
+></DT
+></DL
+></DD
+><DT
+>9.7. <A
+HREF="#AEN2654"
+>Cryptographic side of NT Domain Authentication</A
+></DT
+><DD
+><DL
+><DT
+>9.7.1. <A
+HREF="#AEN2656"
+>Definitions</A
+></DT
+><DT
+>9.7.2. <A
+HREF="#AEN2699"
+>Protocol</A
+></DT
+><DT
+>9.7.3. <A
+HREF="#AEN2709"
+>Comments</A
+></DT
+></DL
+></DD
+><DT
+>9.8. <A
+HREF="#AEN2716"
+>SIDs and RIDs</A
+></DT
+><DD
+><DL
+><DT
+>9.8.1. <A
+HREF="#AEN2724"
+>Well-known SIDs</A
+></DT
+><DT
+>9.8.2. <A
+HREF="#AEN2812"
+>Well-known RIDS</A
+></DT
+></DL
+></DD
+></DL
+></DD
+><DT
+>10. <A
+HREF="#PRINTING"
+>Samba Printing Internals</A
+></DT
+><DD
+><DL
+><DT
+>10.1. <A
+HREF="#AEN2896"
+>Abstract</A
+></DT
+><DT
+>10.2. <A
+HREF="#AEN2899"
+>Printing Interface to Various Back ends</A
+></DT
+><DT
+>10.3. <A
+HREF="#AEN2925"
+>Print Queue TDB's</A
+></DT
+><DT
+>10.4. <A
+HREF="#AEN2959"
+>ChangeID &#38; Client Caching of Printer Information</A
+></DT
+><DT
+>10.5. <A
+HREF="#AEN2962"
+>Windows NT/2K Printer Change Notify</A
+></DT
+></DL
+></DD
+><DT
+>11. <A
+HREF="#WINS"
+>Samba WINS Internals</A
+></DT
+><DD
+><DL
+><DT
+>11.1. <A
+HREF="#AEN3033"
+>WINS Failover</A
+></DT
+></DL
+></DD
+><DT
+>12. <A
+HREF="#SAM"
+>The Upcoming SAM System</A
+></DT
+><DD
+><DL
+><DT
+>12.1. <A
+HREF="#AEN3054"
+>Security in the 'new SAM'</A
+></DT
+><DT
+>12.2. <A
+HREF="#AEN3071"
+>Standalone from UNIX</A
+></DT
+><DT
+>12.3. <A
+HREF="#AEN3075"
+>Handles and Races in the new SAM</A
+></DT
+><DT
+>12.4. <A
+HREF="#AEN3086"
+>Layers</A
+></DT
+><DD
+><DL
+><DT
+>12.4.1. <A
+HREF="#AEN3088"
+>Application</A
+></DT
+><DT
+>12.4.2. <A
+HREF="#AEN3091"
+>SAM Interface</A
+></DT
+><DT
+>12.4.3. <A
+HREF="#AEN3095"
+>SAM Modules</A
+></DT
+></DL
+></DD
+><DT
+>12.5. <A
+HREF="#AEN3098"
+>SAM Modules</A
+></DT
+><DD
+><DL
+><DT
+>12.5.1. <A
+HREF="#AEN3100"
+>Special Module: sam_passdb</A
+></DT
+><DT
+>12.5.2. <A
+HREF="#AEN3103"
+>sam_ads</A
+></DT
+></DL
+></DD
+><DT
+>12.6. <A
+HREF="#AEN3107"
+>Memory Management</A
+></DT
+><DT
+>12.7. <A
+HREF="#AEN3121"
+>Testing</A
+></DT
+></DL
+></DD
+><DT
+>13. <A
+HREF="#PWENCRYPT"
+>LanMan and NT Password Encryption</A
+></DT
+><DD
+><DL
+><DT
+>13.1. <A
+HREF="#AEN3147"
+>Introduction</A
+></DT
+><DT
+>13.2. <A
+HREF="#AEN3151"
+>How does it work?</A
+></DT
+><DT
+>13.3. <A
+HREF="#AEN3162"
+><A
+NAME="SMBPASSWDFILEFORMAT"
+></A
+>The smbpasswd file</A
+></DT
+></DL
+></DD
+></DL
+></DIV
+><DIV
+CLASS="CHAPTER"
+><HR><H1
+><A
+NAME="NETBIOS"
+></A
+>Chapter 1. Definition of NetBIOS Protocol and Name Resolution Modes</H1
+><DIV
+CLASS="SECT1"
+><H2
+CLASS="SECT1"
+><A
+NAME="AEN24"
+></A
+>1.1. NETBIOS</H2
+><P
+>NetBIOS runs over the following tranports: TCP/IP; NetBEUI and IPX/SPX.
Samba only uses NetBIOS over TCP/IP. For details on the TCP/IP NetBIOS
Session Service NetBIOS Datagram Service, and NetBIOS Names, see
-rfc1001.txt and rfc1002.txt.
-</p><p>
+rfc1001.txt and rfc1002.txt.</P
+><P
+>
NetBEUI is a raw NetBIOS frame protocol implementation that allows NetBIOS
datagrams to be sent out over the 'wire' embedded within LLC frames.
NetBEUI is not required when using NetBIOS over TCP/IP protocols and it
-is preferable NOT to install NetBEUI if it can be avoided.
-</p><p>
+is preferable NOT to install NetBEUI if it can be avoided.</P
+><P
+>
IPX/SPX is also not required when using NetBIOS over TCP/IP, and it is
preferable NOT to install the IPX/SPX transport unless you are using Novell
servers. At the very least, it is recommended that you do not install
-'NetBIOS over IPX/SPX'.
-</p><p>
-[When installing Windows 95, you will find that NetBEUI and IPX/SPX are
+'NetBIOS over IPX/SPX'.</P
+><P
+>[When installing Windows 95, you will find that NetBEUI and IPX/SPX are
installed as the default protocols. This is because they are the simplest
-to manage: no Windows 95 user-configuration is required].
-</p><p>
+to manage: no Windows 95 user-configuration is required].</P
+><P
+>
NetBIOS applications (such as samba) offer their services (for example,
SMB file and print sharing) on a NetBIOS name. They must claim this name
on the network before doing so. The NetBIOS session service will then
accept connections on the application's behalf (on the NetBIOS name
claimed by the application). A NetBIOS session between the application
-and the client can then commence.
-</p><p>
+and the client can then commence.</P
+><P
+>
NetBIOS names consist of 15 characters plus a 'type' character. This is
similar, in concept, to an IP address and a TCP port number, respectively.
A NetBIOS-aware application on a host will offer different services under
different NetBIOS name types, just as a host will offer different TCP/IP
-services on different port numbers.
-</p><p>
+services on different port numbers.</P
+><P
+>
NetBIOS names must be claimed on a network, and must be defended. The use
of NetBIOS names is most suitable on a single subnet; a Local Area Network
-or a Wide Area Network.
-</p><p>
+or a Wide Area Network.</P
+><P
+>
NetBIOS names are either UNIQUE or GROUP. Only one application can claim a
-UNIQUE NetBIOS name on a network.
-</p><p>
-There are two kinds of NetBIOS Name resolution: Broadcast and Point-to-Point.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2791260"></a>BROADCAST NetBIOS</h2></div></div><p>
+UNIQUE NetBIOS name on a network.</P
+><P
+>There are two kinds of NetBIOS Name resolution: Broadcast and Point-to-Point.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN35"
+></A
+>1.2. BROADCAST NetBIOS</H2
+><P
+>
Clients can claim names, and therefore offer services on successfully claimed
names, on their broadcast-isolated subnet. One way to get NetBIOS services
(such as browsing: see ftp.microsoft.com/drg/developr/CIFS/browdiff.txt; and
SMB file/print sharing: see cifs4.txt) working on a LAN or WAN is to make
-your routers forward all broadcast packets from TCP/IP ports 137, 138 and 139.
-</p><p>
+your routers forward all broadcast packets from TCP/IP ports 137, 138 and 139.</P
+><P
+>
This, however, is not recommended. If you have a large LAN or WAN, you will
find that some of your hosts spend 95 percent of their time dealing with
broadcast traffic. [If you have IPX/SPX on your LAN or WAN, you will find
that this is already happening: a packet analyzer will show, roughly
-every twelve minutes, great swathes of broadcast traffic!].
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2791291"></a>NBNS NetBIOS</h2></div></div><p>
-rfc1001.txt describes, amongst other things, the implementation and use
+every twelve minutes, great swathes of broadcast traffic!].</P
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN39"
+></A
+>1.3. NBNS NetBIOS</H2
+><P
+>rfc1001.txt describes, amongst other things, the implementation and use
of, a 'NetBIOS Name Service'. NT/AS offers 'Windows Internet Name Service'
which is fully rfc1001/2 compliant, but has had to take specific action
with certain NetBIOS names in order to make it useful. (for example, it
-deals with the registration of &lt;1c&gt; &lt;1d&gt; &lt;1e&gt; names all in different ways.
+deals with the registration of &#60;1c&#62; &#60;1d&#62; &#60;1e&#62; names all in different ways.
I recommend the reading of the Microsoft WINS Server Help files for full
-details).
-</p><p>
+details).</P
+><P
+>
The use of a WINS server cuts down on broadcast network traffic for
NetBIOS name resolution. It has the effect of pulling all the broadcast
isolated subnets together into a single NetBIOS scope, across your LAN
-or WAN, while avoiding the use of TCP/IP broadcast packets.
-</p><p>
-When you have a WINS server on your LAN, WINS clients will be able to
+or WAN, while avoiding the use of TCP/IP broadcast packets.</P
+><P
+>When you have a WINS server on your LAN, WINS clients will be able to
contact the WINS server to resolve NetBIOS names. Note that only those
WINS clients that have registered with the same WINS server will be
visible. The WINS server _can_ have static NetBIOS entries added to its
database (usually for security reasons you might want to consider putting
your domain controllers or other important servers as static entries,
but you should not rely on this as your sole means of security), but for
-the most part, NetBIOS names are registered dynamically.
-</p><p>
-This provides some confusion for lots of people, and is worth mentioning
+the most part, NetBIOS names are registered dynamically.</P
+><P
+>This provides some confusion for lots of people, and is worth mentioning
here: a Browse Server is NOT a WINS Server, even if these services are
implemented in the same application. A Browse Server _needs_ a WINS server
-because a Browse Server is a WINS client, which is _not_ the same thing].
-</p><p>
-Clients can claim names, and therefore offer services on successfully claimed
+because a Browse Server is a WINS client, which is _not_ the same thing].</P
+><P
+>Clients can claim names, and therefore offer services on successfully claimed
names, on their broadcast-isolated subnet. One way to get NetBIOS services
(such as browsing: see ftp.microsoft.com/drg/developr/CIFS/browdiff.txt; and
SMB file/print sharing: see cifs6.txt) working on a LAN or WAN is to make
your routers forward all broadcast packets from TCP/IP ports 137, 138 and 139.
You will find, however, if you do this on a large LAN or a WAN, that your
network is completely swamped by NetBIOS and browsing packets, which is why
-WINS was developed to minimise the necessity of broadcast traffic.
-</p><p>
+WINS was developed to minimise the necessity of broadcast traffic.</P
+><P
+>
WINS Clients therefore claim names from the WINS server. If the WINS
server allows them to register a name, the client's NetBIOS session service
can then offer services on this name. Other WINS clients will then
-contact the WINS server to resolve a NetBIOS name.
-</p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="architecture"></a>Chapter2.Samba Architecture</h2></div><div><div class="author"><h3 class="author">Dan Shearer</h3></div></div><div><p class="pubdate"> November 1997</p></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2795118">Introduction</a></dt><dt><a href="#id2795170">Multithreading and Samba</a></dt><dt><a href="#id2790937">Threading smbd</a></dt><dt><a href="#id2843423">Threading nmbd</a></dt><dt><a href="#id2791332">nbmd Design</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2795118"></a>Introduction</h2></div></div><p>
-This document gives a general overview of how Samba works
+contact the WINS server to resolve a NetBIOS name.</P
+></DIV
+></DIV
+><DIV
+CLASS="CHAPTER"
+><HR><H1
+><A
+NAME="ARCHITECTURE"
+></A
+>Chapter 2. Samba Architecture</H1
+><DIV
+CLASS="SECT1"
+><H2
+CLASS="SECT1"
+><A
+NAME="AEN54"
+></A
+>2.1. Introduction</H2
+><P
+>This document gives a general overview of how Samba works
internally. The Samba Team has tried to come up with a model which is
the best possible compromise between elegance, portability, security
and the constraints imposed by the very messy SMB and CIFS
-protocol.
-</p><p>
-It also tries to answer some of the frequently asked questions such as:
-</p><div class="orderedlist"><ol type="1"><li><p>
- Is Samba secure when running on Unix? The xyz platform?
- What about the root priveliges issue?
-</p></li><li><p>Pros and cons of multithreading in various parts of Samba</p></li><li><p>Why not have a separate process for name resolution, WINS, and browsing?</p></li></ol></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2795170"></a>Multithreading and Samba</h2></div></div><p>
-People sometimes tout threads as a uniformly good thing. They are very
+protocol. </P
+><P
+>It also tries to answer some of the frequently asked questions such as:</P
+><P
+></P
+><OL
+TYPE="1"
+><LI
+><P
+> Is Samba secure when running on Unix? The xyz platform?
+ What about the root priveliges issue?</P
+></LI
+><LI
+><P
+>Pros and cons of multithreading in various parts of Samba</P
+></LI
+><LI
+><P
+>Why not have a separate process for name resolution, WINS, and browsing?</P
+></LI
+></OL
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN65"
+></A
+>2.2. Multithreading and Samba</H2
+><P
+>People sometimes tout threads as a uniformly good thing. They are very
nice in their place but are quite inappropriate for smbd. nmbd is
-another matter, and multi-threading it would be very nice.
-</p><p>
-The short version is that smbd is not multithreaded, and alternative
+another matter, and multi-threading it would be very nice. </P
+><P
+>The short version is that smbd is not multithreaded, and alternative
servers that take this approach under Unix (such as Syntax, at the
time of writing) suffer tremendous performance penalties and are less
robust. nmbd is not threaded either, but this is because it is not
possible to do it while keeping code consistent and portable across 35
-or more platforms. (This drawback also applies to threading smbd.)
-</p><p>
-The longer versions is that there are very good reasons for not making
+or more platforms. (This drawback also applies to threading smbd.)</P
+><P
+>The longer versions is that there are very good reasons for not making
smbd multi-threaded. Multi-threading would actually make Samba much
slower, less scalable, less portable and much less robust. The fact
that we use a separate process for each connection is one of Samba's
-biggest advantages.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2790937"></a>Threading smbd</h2></div></div><p>
-A few problems that would arise from a threaded smbd are:
-</p><div class="orderedlist"><ol type="1"><li><p>
- It's not only to create threads instead of processes, but you
+biggest advantages.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN70"
+></A
+>2.3. Threading smbd</H2
+><P
+>A few problems that would arise from a threaded smbd are:</P
+><P
+></P
+><OL
+TYPE="1"
+><LI
+><P
+> It's not only to create threads instead of processes, but you
must care about all variables if they have to be thread specific
- (currently they would be global).
-</p></li><li><p>
- if one thread dies (eg. a seg fault) then all threads die. We can
- immediately throw robustness out the window.
-</p></li><li><p>
- many of the system calls we make are blocking. Non-blocking
+ (currently they would be global).</P
+></LI
+><LI
+><P
+> if one thread dies (eg. a seg fault) then all threads die. We can
+ immediately throw robustness out the window.</P
+></LI
+><LI
+><P
+> many of the system calls we make are blocking. Non-blocking
equivalents of many calls are either not available or are awkward (and
slow) to use. So while we block in one thread all clients are
waiting. Imagine if one share is a slow NFS filesystem and the others
- are fast, we will end up slowing all clients to the speed of NFS.
-</p></li><li><p>
- you can't run as a different uid in different threads. This means
+ are fast, we will end up slowing all clients to the speed of NFS.</P
+></LI
+><LI
+><P
+> you can't run as a different uid in different threads. This means
we would have to switch uid/gid on _every_ SMB packet. It would be
- horrendously slow.
-</p></li><li><p>
- the per process file descriptor limit would mean that we could only
- support a limited number of clients.
-</p></li><li><p>
- we couldn't use the system locking calls as the locking context of
- fcntl() is a process, not a thread.
-</p></li></ol></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2843423"></a>Threading nmbd</h2></div></div><p>
-This would be ideal, but gets sunk by portability requirements.
-</p><p>
-Andrew tried to write a test threads library for nmbd that used only
+ horrendously slow.</P
+></LI
+><LI
+><P
+> the per process file descriptor limit would mean that we could only
+ support a limited number of clients.</P
+></LI
+><LI
+><P
+> we couldn't use the system locking calls as the locking context of
+ fcntl() is a process, not a thread.</P
+></LI
+></OL
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN86"
+></A
+>2.4. Threading nmbd</H2
+><P
+>This would be ideal, but gets sunk by portability requirements.</P
+><P
+>Andrew tried to write a test threads library for nmbd that used only
ansi-C constructs (using setjmp and longjmp). Unfortunately some OSes
defeat this by restricting longjmp to calling addresses that are
shallower than the current address on the stack (apparently AIX does
@@ -180,22 +1095,31 @@ and without threads, and as the real aim of threads is to make the
code clearer we would not have gained anything. (it is a myth that
threads make things faster. threading is like recursion, it can make
things clear but the same thing can always be done faster by some
-other method)
-</p><p>
-Chris tried to spec out a general design that would abstract threading
+other method)</P
+><P
+>Chris tried to spec out a general design that would abstract threading
vs separate processes (vs other methods?) and make them accessible
through some general API. This doesn't work because of the data
sharing requirements of the protocol (packets in the future depending
on packets now, etc.) At least, the code would work but would be very
-clumsy, and besides the fork() type model would never work on Unix. (Is there an OS that it would work on, for nmbd?)
-</p><p>
-A fork() is cheap, but not nearly cheap enough to do on every UDP
+clumsy, and besides the fork() type model would never work on Unix. (Is there an OS that it would work on, for nmbd?)</P
+><P
+>A fork() is cheap, but not nearly cheap enough to do on every UDP
packet that arrives. Having a pool of processes is possible but is
nasty to program cleanly due to the enormous amount of shared data (in
complex structures) between the processes. We can't rely on each
-platform having a shared memory system.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2791332"></a>nbmd Design</h2></div></div><p>
-Originally Andrew used recursion to simulate a multi-threaded
+platform having a shared memory system.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN92"
+></A
+>2.5. nbmd Design</H2
+><P
+>Originally Andrew used recursion to simulate a multi-threaded
environment, which use the stack enormously and made for really
confusing debugging sessions. Luke Leighton rewrote it to use a
queuing system that keeps state information on each packet. The
@@ -207,18 +1131,37 @@ and a pointer to a user-defined memory block. This suddenly
made things much simpler: large numbers of functions could be
made static, and modularised. This is the same principle as used
in NT's kernel, and achieves the same effect as threads, but in
-a single process.
-</p><p>
-Then Jeremy rewrote nmbd. The packet data in nmbd isn't what's on the
+a single process.</P
+><P
+>Then Jeremy rewrote nmbd. The packet data in nmbd isn't what's on the
wire. It's a nice format that is very amenable to processing but still
-keeps the idea of a distinct packet. See &quot;struct packet_struct&quot; in
+keeps the idea of a distinct packet. See "struct packet_struct" in
nameserv.h. It has all the detail but none of the on-the-wire
mess. This makes it ideal for using in disk or memory-based databases
-for browsing and WINS support.
-</p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="debug"></a>Chapter3.The samba DEBUG system</h2></div><div><div class="author"><h3 class="author">Chris Hertel</h3></div></div><div><p class="pubdate">July 1998</p></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2790677">New Output Syntax</a></dt><dt><a href="#id2791433">The DEBUG() Macro</a></dt><dt><a href="#id2791102">The DEBUGADD() Macro</a></dt><dt><a href="#id2790705">The DEBUGLVL() Macro</a></dt><dt><a href="#id2790812">New Functions</a></dt><dd><dl><dt><a href="#id2790819">dbgtext()</a></dt><dt><a href="#id2790839">dbghdr()</a></dt><dt><a href="#id2790862">format_debug_text()</a></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2790677"></a>New Output Syntax</h2></div></div><p>
- The syntax of a debugging log file is represented as:
-</p><pre class="programlisting">
- &gt;debugfile&lt; :== { &gt;debugmsg&lt; }
+for browsing and WINS support. </P
+></DIV
+></DIV
+><DIV
+CLASS="CHAPTER"
+><HR><H1
+><A
+NAME="DEBUG"
+></A
+>Chapter 3. The samba DEBUG system</H1
+><DIV
+CLASS="SECT1"
+><H2
+CLASS="SECT1"
+><A
+NAME="AEN103"
+></A
+>3.1. New Output Syntax</H2
+><P
+> The syntax of a debugging log file is represented as:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+> &gt;debugfile&lt; :== { &gt;debugmsg&lt; }
&gt;debugmsg&lt; :== &gt;debughdr&lt; '\n' &gt;debugtext&lt;
@@ -226,178 +1169,323 @@ for browsing and WINS support.
&gt;debugtext&lt; :== { &gt;debugline&lt; }
- &gt;debugline&lt; :== TEXT '\n'
-</pre><p>
-TEXT is a string of characters excluding the newline character.
-</p><p>
-LEVEL is the DEBUG level of the message (an integer in the range
- 0..10).
-</p><p>
-TIME is a timestamp.
-</p><p>
-FILE is the name of the file from which the debug message was
-generated.
-</p><p>
-FUNCTION is the function from which the debug message was generated.
-</p><p>
-LINE is the line number of the debug statement that generated the
-message.
-</p><p>Basically, what that all means is:</p><div class="orderedlist"><ol type="1"><li><p>
-A debugging log file is made up of debug messages.
-</p></li><li><p>
-Each debug message is made up of a header and text. The header is
-separated from the text by a newline.
-</p></li><li><p>
-The header begins with the timestamp and debug level of the
+ &gt;debugline&lt; :== TEXT '\n'</PRE
+></P
+><P
+>TEXT is a string of characters excluding the newline character.</P
+><P
+>LEVEL is the DEBUG level of the message (an integer in the range
+ 0..10).</P
+><P
+>TIME is a timestamp.</P
+><P
+>FILE is the name of the file from which the debug message was
+generated.</P
+><P
+>FUNCTION is the function from which the debug message was generated.</P
+><P
+>LINE is the line number of the debug statement that generated the
+message.</P
+><P
+>Basically, what that all means is:</P
+><P
+></P
+><OL
+TYPE="1"
+><LI
+><P
+>A debugging log file is made up of debug messages.</P
+></LI
+><LI
+><P
+>Each debug message is made up of a header and text. The header is
+separated from the text by a newline.</P
+></LI
+><LI
+><P
+>The header begins with the timestamp and debug level of the
message enclosed in brackets. The filename, function, and line
number at which the message was generated follow. The filename is
terminated by a colon, and the function name is terminated by the
parenthesis which contain the line number. Depending upon the
compiler, the function name may be missing (it is generated by the
-__FUNCTION__ macro, which is not universally implemented, dangit).
-</p></li><li><p>
-The message text is made up of zero or more lines, each terminated
-by a newline.
-</p></li></ol></div><p>Here's some example output:</p><pre class="programlisting">
- [1998/08/03 12:55:25, 1] nmbd.c:(659)
+__FUNCTION__ macro, which is not universally implemented, dangit).</P
+></LI
+><LI
+><P
+>The message text is made up of zero or more lines, each terminated
+by a newline.</P
+></LI
+></OL
+><P
+>Here's some example output:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+> [1998/08/03 12:55:25, 1] nmbd.c:(659)
Netbios nameserver version 1.9.19-prealpha started.
Copyright Andrew Tridgell 1994-1997
[1998/08/03 12:55:25, 3] loadparm.c:(763)
- Initializing global parameters
-</pre><p>
-Note that in the above example the function names are not listed on
+ Initializing global parameters</PRE
+></P
+><P
+>Note that in the above example the function names are not listed on
the header line. That's because the example above was generated on an
-SGI Indy, and the SGI compiler doesn't support the __FUNCTION__ macro.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2791433"></a>The DEBUG() Macro</h2></div></div><p>
-Use of the DEBUG() macro is unchanged. DEBUG() takes two parameters.
+SGI Indy, and the SGI compiler doesn't support the __FUNCTION__ macro.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN128"
+></A
+>3.2. The DEBUG() Macro</H2
+><P
+>Use of the DEBUG() macro is unchanged. DEBUG() takes two parameters.
The first is the message level, the second is the body of a function
-call to the Debug1() function.
-</p><p>That's confusing.</p><p>Here's an example which may help a bit. If you would write</p><pre class="programlisting">
-printf( &quot;This is a %s message.\n&quot;, &quot;debug&quot; );
-</pre><p>
-to send the output to stdout, then you would write
-</p><pre class="programlisting">
-DEBUG( 0, ( &quot;This is a %s message.\n&quot;, &quot;debug&quot; ) );
-</pre><p>
-to send the output to the debug file. All of the normal printf()
-formatting escapes work.
-</p><p>
-Note that in the above example the DEBUG message level is set to 0.
+call to the Debug1() function.</P
+><P
+>That's confusing.</P
+><P
+>Here's an example which may help a bit. If you would write</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>printf( "This is a %s message.\n", "debug" );</PRE
+></P
+><P
+>to send the output to stdout, then you would write</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>DEBUG( 0, ( "This is a %s message.\n", "debug" ) );</PRE
+></P
+><P
+>to send the output to the debug file. All of the normal printf()
+formatting escapes work.</P
+><P
+>Note that in the above example the DEBUG message level is set to 0.
Messages at level 0 always print. Basically, if the message level is
less than or equal to the global value DEBUGLEVEL, then the DEBUG
-statement is processed.
-</p><p>
-The output of the above example would be something like:
-</p><pre class="programlisting">
- [1998/07/30 16:00:51, 0] file.c:function(128)
- This is a debug message.
-</pre><p>
-Each call to DEBUG() creates a new header *unless* the output produced
+statement is processed.</P
+><P
+>The output of the above example would be something like:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+> [1998/07/30 16:00:51, 0] file.c:function(128)
+ This is a debug message.</PRE
+></P
+><P
+>Each call to DEBUG() creates a new header *unless* the output produced
by the previous call to DEBUG() did not end with a '\n'. Output to the
debug file is passed through a formatting buffer which is flushed
every time a newline is encountered. If the buffer is not empty when
-DEBUG() is called, the new input is simply appended.
-</p><p>
-...but that's really just a Kludge. It was put in place because
+DEBUG() is called, the new input is simply appended.</P
+><P
+>...but that's really just a Kludge. It was put in place because
DEBUG() has been used to write partial lines. Here's a simple (dumb)
-example of the kind of thing I'm talking about:
-</p><pre class="programlisting">
- DEBUG( 0, (&quot;The test returned &quot; ) );
+example of the kind of thing I'm talking about:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+> DEBUG( 0, ("The test returned " ) );
if( test() )
- DEBUG(0, (&quot;True&quot;) );
+ DEBUG(0, ("True") );
else
- DEBUG(0, (&quot;False&quot;) );
- DEBUG(0, (&quot;.\n&quot;) );
-</pre><p>
-Without the format buffer, the output (assuming test() returned true)
-would look like this:
-</p><pre class="programlisting">
- [1998/07/30 16:00:51, 0] file.c:function(256)
+ DEBUG(0, ("False") );
+ DEBUG(0, (".\n") );</PRE
+></P
+><P
+>Without the format buffer, the output (assuming test() returned true)
+would look like this:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+> [1998/07/30 16:00:51, 0] file.c:function(256)
The test returned
[1998/07/30 16:00:51, 0] file.c:function(258)
True
[1998/07/30 16:00:51, 0] file.c:function(261)
- .
-</pre><p>Which isn't much use. The format buffer kludge fixes this problem.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2791102"></a>The DEBUGADD() Macro</h2></div></div><p>
-In addition to the kludgey solution to the broken line problem
+ .</PRE
+></P
+><P
+>Which isn't much use. The format buffer kludge fixes this problem.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN151"
+></A
+>3.3. The DEBUGADD() Macro</H2
+><P
+>In addition to the kludgey solution to the broken line problem
described above, there is a clean solution. The DEBUGADD() macro never
generates a header. It will append new text to the current debug
message even if the format buffer is empty. The syntax of the
-DEBUGADD() macro is the same as that of the DEBUG() macro.
-</p><pre class="programlisting">
- DEBUG( 0, (&quot;This is the first line.\n&quot; ) );
- DEBUGADD( 0, (&quot;This is the second line.\nThis is the third line.\n&quot; ) );
-</pre><p>Produces</p><pre class="programlisting">
- [1998/07/30 16:00:51, 0] file.c:function(512)
+DEBUGADD() macro is the same as that of the DEBUG() macro.</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+> DEBUG( 0, ("This is the first line.\n" ) );
+ DEBUGADD( 0, ("This is the second line.\nThis is the third line.\n" ) );</PRE
+></P
+><P
+>Produces</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+> [1998/07/30 16:00:51, 0] file.c:function(512)
This is the first line.
This is the second line.
- This is the third line.
-</pre></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2790705"></a>The DEBUGLVL() Macro</h2></div></div><p>
-One of the problems with the DEBUG() macro was that DEBUG() lines
+ This is the third line.</PRE
+></P
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN159"
+></A
+>3.4. The DEBUGLVL() Macro</H2
+><P
+>One of the problems with the DEBUG() macro was that DEBUG() lines
tended to get a bit long. Consider this example from
-nmbd_sendannounce.c:
-</p><pre class="programlisting">
- DEBUG(3,(&quot;send_local_master_announcement: type %x for name %s on subnet %s for workgroup %s\n&quot;,
- type, global_myname, subrec-&gt;subnet_name, work-&gt;work_group));
-</pre><p>
-One solution to this is to break it down using DEBUG() and DEBUGADD(),
-as follows:
-</p><pre class="programlisting">
- DEBUG( 3, ( &quot;send_local_master_announcement: &quot; ) );
- DEBUGADD( 3, ( &quot;type %x for name %s &quot;, type, global_myname ) );
- DEBUGADD( 3, ( &quot;on subnet %s &quot;, subrec-&gt;subnet_name ) );
- DEBUGADD( 3, ( &quot;for workgroup %s\n&quot;, work-&gt;work_group ) );
-</pre><p>
-A similar, but arguably nicer approach is to use the DEBUGLVL() macro.
+nmbd_sendannounce.c:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+> DEBUG(3,("send_local_master_announcement: type %x for name %s on subnet %s for workgroup %s\n",
+ type, global_myname, subrec-&#62;subnet_name, work-&#62;work_group));</PRE
+></P
+><P
+>One solution to this is to break it down using DEBUG() and DEBUGADD(),
+as follows:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+> DEBUG( 3, ( "send_local_master_announcement: " ) );
+ DEBUGADD( 3, ( "type %x for name %s ", type, global_myname ) );
+ DEBUGADD( 3, ( "on subnet %s ", subrec-&#62;subnet_name ) );
+ DEBUGADD( 3, ( "for workgroup %s\n", work-&#62;work_group ) );</PRE
+></P
+><P
+>A similar, but arguably nicer approach is to use the DEBUGLVL() macro.
This macro returns True if the message level is less than or equal to
-the global DEBUGLEVEL value, so:
-</p><pre class="programlisting">
- if( DEBUGLVL( 3 ) )
+the global DEBUGLEVEL value, so:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+> if( DEBUGLVL( 3 ) )
{
- dbgtext( &quot;send_local_master_announcement: &quot; );
- dbgtext( &quot;type %x for name %s &quot;, type, global_myname );
- dbgtext( &quot;on subnet %s &quot;, subrec-&gt;subnet_name );
- dbgtext( &quot;for workgroup %s\n&quot;, work-&gt;work_group );
- }
-</pre><p>(The dbgtext() function is explained below.)</p><p>There are a few advantages to this scheme:</p><div class="orderedlist"><ol type="1"><li><p>
-The test is performed only once.
-</p></li><li><p>
-You can allocate variables off of the stack that will only be used
-within the DEBUGLVL() block.
-</p></li><li><p>
-Processing that is only relevant to debug output can be contained
-within the DEBUGLVL() block.
-</p></li></ol></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2790812"></a>New Functions</h2></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2790819"></a>dbgtext()</h3></div></div><p>
-This function prints debug message text to the debug file (and
+ dbgtext( "send_local_master_announcement: " );
+ dbgtext( "type %x for name %s ", type, global_myname );
+ dbgtext( "on subnet %s ", subrec-&#62;subnet_name );
+ dbgtext( "for workgroup %s\n", work-&#62;work_group );
+ }</PRE
+></P
+><P
+>(The dbgtext() function is explained below.)</P
+><P
+>There are a few advantages to this scheme:</P
+><P
+></P
+><OL
+TYPE="1"
+><LI
+><P
+>The test is performed only once.</P
+></LI
+><LI
+><P
+>You can allocate variables off of the stack that will only be used
+within the DEBUGLVL() block.</P
+></LI
+><LI
+><P
+>Processing that is only relevant to debug output can be contained
+within the DEBUGLVL() block.</P
+></LI
+></OL
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN179"
+></A
+>3.5. New Functions</H2
+><DIV
+CLASS="SECT2"
+><H3
+CLASS="SECT2"
+><A
+NAME="AEN181"
+></A
+>3.5.1. dbgtext()</H3
+><P
+>This function prints debug message text to the debug file (and
possibly to syslog) via the format buffer. The function uses a
variable argument list just like printf() or Debug1(). The
input is printed into a buffer using the vslprintf() function,
and then passed to format_debug_text().
If you use DEBUGLVL() you will probably print the body of the
-message using dbgtext().
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2790839"></a>dbghdr()</h3></div></div><p>
-This is the function that writes a debug message header.
+message using dbgtext(). </P
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN184"
+></A
+>3.5.2. dbghdr()</H3
+><P
+>This is the function that writes a debug message header.
Headers are not processed via the format buffer. Also note that
if the format buffer is not empty, a call to dbghdr() will not
-produce any output. See the comments in dbghdr() for more info.
-</p><p>
-It is not likely that this function will be called directly. It
-is used by DEBUG() and DEBUGADD().
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2790862"></a>format_debug_text()</h3></div></div><p>
-This is a static function in debug.c. It stores the output text
+produce any output. See the comments in dbghdr() for more info.</P
+><P
+>It is not likely that this function will be called directly. It
+is used by DEBUG() and DEBUGADD().</P
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN188"
+></A
+>3.5.3. format_debug_text()</H3
+><P
+>This is a static function in debug.c. It stores the output text
for the body of the message in a buffer until it encounters a
newline. When the newline character is found, the buffer is
written to the debug file via the Debug1() function, and the
buffer is reset. This allows us to add the indentation at the
beginning of each line of the message body, and also ensures
that the output is written a line at a time (which cleans up
-syslog output).
-</p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="CodingSuggestions"></a>Chapter4.Coding Suggestions</h2></div><div><div class="author"><h3 class="author">Steve French</h3></div></div><div><div class="author"><h3 class="author">Simo Sorce</h3></div></div><div><div class="author"><h3 class="author">Andrew Bartlett</h3></div></div><div><div class="author"><h3 class="author">Tim Potter</h3></div></div><div><div class="author"><h3 class="author">Martin Pool</h3></div></div></div><p>
-So you want to add code to Samba ...
-</p><p>
-One of the daunting tasks facing a programmer attempting to write code for
+syslog output).</P
+></DIV
+></DIV
+></DIV
+><DIV
+CLASS="CHAPTER"
+><HR><H1
+><A
+NAME="CODINGSUGGESTIONS"
+></A
+>Chapter 4. Coding Suggestions</H1
+><P
+>So you want to add code to Samba ...</P
+><P
+>One of the daunting tasks facing a programmer attempting to write code for
Samba is understanding the various coding conventions used by those most
active in the project. These conventions were mostly unwritten and helped
improve either the portability, stability or consistency of the code. This
@@ -405,181 +1493,305 @@ document will attempt to document a few of the more important coding
practices used at this time on the Samba project. The coding practices are
expected to change slightly over time, and even to grow as more is learned
about obscure portability considerations. Two existing documents
-<tt>samba/source/internals.doc</tt> and
-<tt>samba/source/architecture.doc</tt> provide
-additional information.
-</p><p>
-The loosely related question of coding style is very personal and this
+<TT
+CLASS="FILENAME"
+>samba/source/internals.doc</TT
+> and
+<TT
+CLASS="FILENAME"
+>samba/source/architecture.doc</TT
+> provide
+additional information.</P
+><P
+>The loosely related question of coding style is very personal and this
document does not attempt to address that subject, except to say that I
have observed that eight character tabs seem to be preferred in Samba
source. If you are interested in the topic of coding style, two oft-quoted
-documents are:
-</p><p>
-<a href="http://lxr.linux.no/source/Documentation/CodingStyle" target="_top">http://lxr.linux.no/source/Documentation/CodingStyle</a>
-</p><p>
-<a href="http://www.fsf.org/prep/standards_toc.html" target="_top">http://www.fsf.org/prep/standards_toc.html</a>
-</p><p>
-But note that coding style in Samba varies due to the many different
-programmers who have contributed.
-</p><p>
-Following are some considerations you should use when adding new code to
-Samba. First and foremost remember that:
-</p><p>
-Portability is a primary consideration in adding function, as is network
+documents are:</P
+><P
+><A
+HREF="http://lxr.linux.no/source/Documentation/CodingStyle"
+TARGET="_top"
+>http://lxr.linux.no/source/Documentation/CodingStyle</A
+></P
+><P
+><A
+HREF="http://www.fsf.org/prep/standards_toc.html"
+TARGET="_top"
+>http://www.fsf.org/prep/standards_toc.html</A
+></P
+><P
+>But note that coding style in Samba varies due to the many different
+programmers who have contributed.</P
+><P
+>Following are some considerations you should use when adding new code to
+Samba. First and foremost remember that:</P
+><P
+>Portability is a primary consideration in adding function, as is network
compatability with de facto, existing, real world CIFS/SMB implementations.
There are lots of platforms that Samba builds on so use caution when adding
a call to a library function that is not invoked in existing Samba code.
Also note that there are many quite different SMB/CIFS clients that Samba
tries to support, not all of which follow the SNIA CIFS Technical Reference
(or the earlier Microsoft reference documents or the X/Open book on the SMB
-Standard) perfectly.
-</p><p>
-Here are some other suggestions:
-</p><div class="orderedlist"><ol type="1"><li><p>
- use d_printf instead of printf for display text
- reason: enable auto-substitution of translated language text
-</p></li><li><p>
- use SAFE_FREE instead of free
- reason: reduce traps due to null pointers
-</p></li><li><p>
- don't use bzero use memset, or ZERO_STRUCT and ZERO_STRUCTP macros
- reason: not POSIX
-</p></li><li><p>
- don't use strcpy and strlen (use safe_* equivalents)
- reason: to avoid traps due to buffer overruns
-</p></li><li><p>
- don't use getopt_long, use popt functions instead
- reason: portability
-</p></li><li><p>
- explicitly add const qualifiers on parm passing in functions where parm
- is input only (somewhat controversial but const can be #defined away)
-</p></li><li><p>
- when passing a va_list as an arg, or assigning one to another
+Standard) perfectly.</P
+><P
+>Here are some other suggestions:</P
+><P
+></P
+><OL
+TYPE="1"
+><LI
+><P
+> use d_printf instead of printf for display text
+ reason: enable auto-substitution of translated language text </P
+></LI
+><LI
+><P
+> use SAFE_FREE instead of free
+ reason: reduce traps due to null pointers</P
+></LI
+><LI
+><P
+> don't use bzero use memset, or ZERO_STRUCT and ZERO_STRUCTP macros
+ reason: not POSIX</P
+></LI
+><LI
+><P
+> don't use strcpy and strlen (use safe_* equivalents)
+ reason: to avoid traps due to buffer overruns</P
+></LI
+><LI
+><P
+> don't use getopt_long, use popt functions instead
+ reason: portability</P
+></LI
+><LI
+><P
+> explicitly add const qualifiers on parm passing in functions where parm
+ is input only (somewhat controversial but const can be #defined away)</P
+></LI
+><LI
+><P
+> when passing a va_list as an arg, or assigning one to another
please use the VA_COPY() macro
reason: on some platforms, va_list is a struct that must be
- initialized in each function...can SEGV if you don't.
-</p></li><li><p>
- discourage use of threads
- reason: portability (also see architecture.doc)
-</p></li><li><p>
- don't explicitly include new header files in C files - new h files
+ initialized in each function...can SEGV if you don't.</P
+></LI
+><LI
+><P
+> discourage use of threads
+ reason: portability (also see architecture.doc)</P
+></LI
+><LI
+><P
+> don't explicitly include new header files in C files - new h files
should be included by adding them once to includes.h
- reason: consistency
-</p></li><li><p>
- don't explicitly extern functions (they are autogenerated by
- &quot;make proto&quot; into proto.h)
- reason: consistency
-</p></li><li><p>
- use endian safe macros when unpacking SMBs (see byteorder.h and
+ reason: consistency</P
+></LI
+><LI
+><P
+> don't explicitly extern functions (they are autogenerated by
+ "make proto" into proto.h)
+ reason: consistency</P
+></LI
+><LI
+><P
+> use endian safe macros when unpacking SMBs (see byteorder.h and
internals.doc)
- reason: not everyone uses Intel
-</p></li><li><p>
- Note Unicode implications of charset handling (see internals.doc). See
+ reason: not everyone uses Intel</P
+></LI
+><LI
+><P
+> Note Unicode implications of charset handling (see internals.doc). See
pull_* and push_* and convert_string functions.
- reason: Internationalization
-</p></li><li><p>
- Don't assume English only
- reason: See above
-</p></li><li><p>
- Try to avoid using in/out parameters (functions that return data which
+ reason: Internationalization</P
+></LI
+><LI
+><P
+> Don't assume English only
+ reason: See above</P
+></LI
+><LI
+><P
+> Try to avoid using in/out parameters (functions that return data which
overwrites input parameters)
- reason: Can cause stability problems
-</p></li><li><p>
- Ensure copyright notices are correct, don't append Tridge's name to code
+ reason: Can cause stability problems</P
+></LI
+><LI
+><P
+> Ensure copyright notices are correct, don't append Tridge's name to code
that he didn't write. If you did not write the code, make sure that it
- can coexist with the rest of the Samba GPLed code.
-</p></li><li><p>
- Consider usage of DATA_BLOBs for length specified byte-data.
- reason: stability
-</p></li><li><p>
- Take advantage of tdbs for database like function
- reason: consistency
-</p></li><li><p>
- Don't access the SAM_ACCOUNT structure directly, they should be accessed
+ can coexist with the rest of the Samba GPLed code.</P
+></LI
+><LI
+><P
+> Consider usage of DATA_BLOBs for length specified byte-data.
+ reason: stability</P
+></LI
+><LI
+><P
+> Take advantage of tdbs for database like function
+ reason: consistency</P
+></LI
+><LI
+><P
+> Don't access the SAM_ACCOUNT structure directly, they should be accessed
via pdb_get...() and pdb_set...() functions.
- reason: stability, consistency
-</p></li><li><p>
- Don't check a password directly against the passdb, always use the
+ reason: stability, consistency</P
+></LI
+><LI
+><P
+> Don't check a password directly against the passdb, always use the
check_password() interface.
- reason: long term pluggability
-</p></li><li><p>
- Try to use asprintf rather than pstrings and fstrings where possible
-</p></li><li><p>
- Use normal C comments / * instead of C++ comments // like
+ reason: long term pluggability</P
+></LI
+><LI
+><P
+> Try to use asprintf rather than pstrings and fstrings where possible</P
+></LI
+><LI
+><P
+> Use normal C comments / * instead of C++ comments // like
this. Although the C++ comment format is part of the C99
- standard, some older vendor C compilers do not accept it.
-</p></li><li><p>
- Try to write documentation for API functions and structures
+ standard, some older vendor C compilers do not accept it.</P
+></LI
+><LI
+><P
+> Try to write documentation for API functions and structures
explaining the point of the code, the way it should be used, and
any special conditions or results. Mark these with a double-star
comment start / ** so that they can be picked up by Doxygen, as in
- this file.
-</p></li><li><p>
- Keep the scope narrow. This means making functions/variables
+ this file.</P
+></LI
+><LI
+><P
+> Keep the scope narrow. This means making functions/variables
static whenever possible. We don't want our namespace
polluted. Each module should have a minimal number of externally
- visible functions or variables.
-</p></li><li><p>
- Use function pointers to keep knowledge about particular pieces of
+ visible functions or variables.</P
+></LI
+><LI
+><P
+> Use function pointers to keep knowledge about particular pieces of
code isolated in one place. We don't want a particular piece of
functionality to be spread out across lots of places - that makes
for fragile, hand to maintain code. Instead, design an interface
and use tables containing function pointers to implement specific
functionality. This is particularly important for command
- interpreters.
-</p></li><li><p>
- Think carefully about what it will be like for someone else to add
+ interpreters. </P
+></LI
+><LI
+><P
+> Think carefully about what it will be like for someone else to add
to and maintain your code. If it would be hard for someone else to
- maintain then do it another way.
-</p></li></ol></div><p>
-The suggestions above are simply that, suggestions, but the information may
+ maintain then do it another way. </P
+></LI
+></OL
+><P
+>The suggestions above are simply that, suggestions, but the information may
help in reducing the routine rework done on new code. The preceeding list
is expected to change routinely as new support routines and macros are
-added.
-</p></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="internals"></a>Chapter5.Samba Internals</h2></div><div><div class="author"><h3 class="author">David Chappell</h3><div class="affiliation"><div class="address"><p><tt>&lt;<a href="mailto:David.Chappell@mail.trincoll.edu">David.Chappell@mail.trincoll.edu</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate">8 May 1996</p></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2857490">Character Handling</a></dt><dt><a href="#id2857515">The new functions</a></dt><dt><a href="#id2857977">Macros in byteorder.h</a></dt><dd><dl><dt><a href="#id2857991">CVAL(buf,pos)</a></dt><dt><a href="#id2858005">PVAL(buf,pos)</a></dt><dt><a href="#id2858019">SCVAL(buf,pos,val)</a></dt><dt><a href="#id2858032">SVAL(buf,pos)</a></dt><dt><a href="#id2858048">IVAL(buf,pos)</a></dt><dt><a href="#id2858062">SVALS(buf,pos)</a></dt><dt><a href="#id2858077">IVALS(buf,pos)</a></dt><dt><a href="#id2858091">SSVAL(buf,pos,val)</a></dt><dt><a href="#id2858106">SIVAL(buf,pos,val)</a></dt><dt><a href="#id2858120">SSVALS(buf,pos,val)</a></dt><dt><a href="#id2858134">SIVALS(buf,pos,val)</a></dt><dt><a href="#id2858149">RSVAL(buf,pos)</a></dt><dt><a href="#id2858163">RIVAL(buf,pos)</a></dt><dt><a href="#id2858177">RSSVAL(buf,pos,val)</a></dt><dt><a href="#id2858192">RSIVAL(buf,pos,val)</a></dt></dl></dd><dt><a href="#id2858208">LAN Manager Samba API</a></dt><dd><dl><dt><a href="#id2858243">Parameters</a></dt><dt><a href="#id2858395">Return value</a></dt></dl></dd><dt><a href="#id2858481">Code character table</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2857490"></a>Character Handling</h2></div></div><p>
-This section describes character set handling in Samba, as implemented in
-Samba 3.0 and above
-</p><p>
-In the past Samba had very ad-hoc character set handling. Scattered
+added.</P
+></DIV
+><DIV
+CLASS="CHAPTER"
+><HR><H1
+><A
+NAME="INTERNALS"
+></A
+>Chapter 5. Samba Internals</H1
+><DIV
+CLASS="SECT1"
+><H2
+CLASS="SECT1"
+><A
+NAME="AEN284"
+></A
+>5.1. Character Handling</H2
+><P
+>This section describes character set handling in Samba, as implemented in
+Samba 3.0 and above</P
+><P
+>In the past Samba had very ad-hoc character set handling. Scattered
throughout the code were numerous calls which converted particular
strings to/from DOS codepages. The problem is that there was no way of
telling if a particular char* is in dos codepage or unix
codepage. This led to a nightmare of code that tried to cope with
-particular cases without handlingt the general case.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2857515"></a>The new functions</h2></div></div><p>
-The new system works like this:
-</p><div class="orderedlist"><ol type="1"><li><p>
- all char* strings inside Samba are &quot;unix&quot; strings. These are
- multi-byte strings that are in the charset defined by the &quot;unix
- charset&quot; option in smb.conf.
-</p></li><li><p>
- there is no single fixed character set for unix strings, but any
+particular cases without handlingt the general case.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN288"
+></A
+>5.2. The new functions</H2
+><P
+>The new system works like this:</P
+><P
+></P
+><OL
+TYPE="1"
+><LI
+><P
+> all char* strings inside Samba are "unix" strings. These are
+ multi-byte strings that are in the charset defined by the "unix
+ charset" option in smb.conf. </P
+></LI
+><LI
+><P
+> there is no single fixed character set for unix strings, but any
character set that is used does need the following properties:
- </p><div class="orderedlist"><ol type="a"><li><p>
- must not contain NULLs except for termination
- </p></li><li><p>
- must be 7-bit compatible with C strings, so that a constant
+ </P
+><P
+></P
+><OL
+TYPE="a"
+><LI
+><P
+> must not contain NULLs except for termination
+ </P
+></LI
+><LI
+><P
+> must be 7-bit compatible with C strings, so that a constant
string or character in C will be byte-for-byte identical to the
equivalent string in the chosen character set.
- </p></li><li><p>
- when you uppercase or lowercase a string it does not become
+ </P
+></LI
+><LI
+><P
+> when you uppercase or lowercase a string it does not become
longer than the original string
- </p></li><li><p>
- must be able to correctly hold all characters that your client
+ </P
+></LI
+><LI
+><P
+> must be able to correctly hold all characters that your client
will throw at it
- </p></li></ol></div><p>
- For example, UTF-8 is fine, and most multi-byte asian character sets
+ </P
+></LI
+></OL
+><P
+> For example, UTF-8 is fine, and most multi-byte asian character sets
are fine, but UCS2 could not be used for unix strings as they
contain nulls.
- </p></li><li><p>
- when you need to put a string into a buffer that will be sent on the
+ </P
+></LI
+><LI
+><P
+> when you need to put a string into a buffer that will be sent on the
wire, or you need a string in a character set format that is
compatible with the clients character set then you need to use a
pull_ or push_ function. The pull_ functions pull a string from a
wire buffer into a (multi-byte) unix string. The push_ functions
- push a string out to a wire buffer.
-</p></li><li><p>
- the two main pull_ and push_ functions you need to understand are
+ push a string out to a wire buffer. </P
+></LI
+><LI
+><P
+> the two main pull_ and push_ functions you need to understand are
pull_string and push_string. These functions take a base pointer
that should point at the start of the SMB packet that the string is
in. The functions will check the flags field in this packet to
@@ -589,426 +1801,953 @@ The new system works like this:
STR_ASCII flags. For use in smbd/ and libsmb/ there are wrapper
functions clistr_ and srvstr_ that call the pull_/push_ functions
with the appropriate first argument.
- </p><p>
- You may also call the pull_ascii/pull_ucs2 or push_ascii/push_ucs2
+ </P
+><P
+> You may also call the pull_ascii/pull_ucs2 or push_ascii/push_ucs2
functions if you know that a particular string is ascii or
unicode. There are also a number of other convenience functions in
charcnv.c that call the pull_/push_ functions with particularly
common arguments, such as pull_ascii_pstring()
- </p></li><li><p>
- The biggest thing to remember is that internal (unix) strings in Samba
+ </P
+></LI
+><LI
+><P
+> The biggest thing to remember is that internal (unix) strings in Samba
may now contain multi-byte characters. This means you cannot assume
that characters are always 1 byte long. Often this means that you will
have to convert strings to ucs2 and back again in order to do some
(seemingly) simple task. For examples of how to do this see functions
like strchr_m(). I know this is very slow, and we will eventually
- speed it up but right now we want this stuff correct not fast.
-</p></li><li><p>
- all lp_ functions now return unix strings. The magic &quot;DOS&quot; flag on
- parameters is gone.
-</p></li><li><p>
- all vfs functions take unix strings. Don't convert when passing to them
-</p></li></ol></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2857977"></a>Macros in byteorder.h</h2></div></div><p>
-This section describes the macros defined in byteorder.h. These macros
-are used extensively in the Samba code.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2857991"></a>CVAL(buf,pos)</h3></div></div><p>
-returns the byte at offset pos within buffer buf as an unsigned character.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2858005"></a>PVAL(buf,pos)</h3></div></div><p>returns the value of CVAL(buf,pos) cast to type unsigned integer.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2858019"></a>SCVAL(buf,pos,val)</h3></div></div><p>sets the byte at offset pos within buffer buf to value val.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2858032"></a>SVAL(buf,pos)</h3></div></div><p>
- returns the value of the unsigned short (16 bit) little-endian integer at
+ speed it up but right now we want this stuff correct not fast.</P
+></LI
+><LI
+><P
+> all lp_ functions now return unix strings. The magic "DOS" flag on
+ parameters is gone.</P
+></LI
+><LI
+><P
+> all vfs functions take unix strings. Don't convert when passing to them</P
+></LI
+></OL
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN317"
+></A
+>5.3. Macros in byteorder.h</H2
+><P
+>This section describes the macros defined in byteorder.h. These macros
+are used extensively in the Samba code.</P
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN320"
+></A
+>5.3.1. CVAL(buf,pos)</H3
+><P
+>returns the byte at offset pos within buffer buf as an unsigned character.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN323"
+></A
+>5.3.2. PVAL(buf,pos)</H3
+><P
+>returns the value of CVAL(buf,pos) cast to type unsigned integer.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN326"
+></A
+>5.3.3. SCVAL(buf,pos,val)</H3
+><P
+>sets the byte at offset pos within buffer buf to value val.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN329"
+></A
+>5.3.4. SVAL(buf,pos)</H3
+><P
+> returns the value of the unsigned short (16 bit) little-endian integer at
offset pos within buffer buf. An integer of this type is sometimes
- refered to as &quot;USHORT&quot;.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2858048"></a>IVAL(buf,pos)</h3></div></div><p>returns the value of the unsigned 32 bit little-endian integer at offset
-pos within buffer buf.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2858062"></a>SVALS(buf,pos)</h3></div></div><p>returns the value of the signed short (16 bit) little-endian integer at
-offset pos within buffer buf.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2858077"></a>IVALS(buf,pos)</h3></div></div><p>returns the value of the signed 32 bit little-endian integer at offset pos
-within buffer buf.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2858091"></a>SSVAL(buf,pos,val)</h3></div></div><p>sets the unsigned short (16 bit) little-endian integer at offset pos within
-buffer buf to value val.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2858106"></a>SIVAL(buf,pos,val)</h3></div></div><p>sets the unsigned 32 bit little-endian integer at offset pos within buffer
-buf to the value val.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2858120"></a>SSVALS(buf,pos,val)</h3></div></div><p>sets the short (16 bit) signed little-endian integer at offset pos within
-buffer buf to the value val.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2858134"></a>SIVALS(buf,pos,val)</h3></div></div><p>sets the signed 32 bit little-endian integer at offset pos withing buffer
-buf to the value val.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2858149"></a>RSVAL(buf,pos)</h3></div></div><p>returns the value of the unsigned short (16 bit) big-endian integer at
-offset pos within buffer buf.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2858163"></a>RIVAL(buf,pos)</h3></div></div><p>returns the value of the unsigned 32 bit big-endian integer at offset
-pos within buffer buf.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2858177"></a>RSSVAL(buf,pos,val)</h3></div></div><p>sets the value of the unsigned short (16 bit) big-endian integer at
+ refered to as "USHORT".</P
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN332"
+></A
+>5.3.5. IVAL(buf,pos)</H3
+><P
+>returns the value of the unsigned 32 bit little-endian integer at offset
+pos within buffer buf.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN335"
+></A
+>5.3.6. SVALS(buf,pos)</H3
+><P
+>returns the value of the signed short (16 bit) little-endian integer at
+offset pos within buffer buf.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN338"
+></A
+>5.3.7. IVALS(buf,pos)</H3
+><P
+>returns the value of the signed 32 bit little-endian integer at offset pos
+within buffer buf.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN341"
+></A
+>5.3.8. SSVAL(buf,pos,val)</H3
+><P
+>sets the unsigned short (16 bit) little-endian integer at offset pos within
+buffer buf to value val.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN344"
+></A
+>5.3.9. SIVAL(buf,pos,val)</H3
+><P
+>sets the unsigned 32 bit little-endian integer at offset pos within buffer
+buf to the value val.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN347"
+></A
+>5.3.10. SSVALS(buf,pos,val)</H3
+><P
+>sets the short (16 bit) signed little-endian integer at offset pos within
+buffer buf to the value val.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN350"
+></A
+>5.3.11. SIVALS(buf,pos,val)</H3
+><P
+>sets the signed 32 bit little-endian integer at offset pos withing buffer
+buf to the value val.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN353"
+></A
+>5.3.12. RSVAL(buf,pos)</H3
+><P
+>returns the value of the unsigned short (16 bit) big-endian integer at
+offset pos within buffer buf.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN356"
+></A
+>5.3.13. RIVAL(buf,pos)</H3
+><P
+>returns the value of the unsigned 32 bit big-endian integer at offset
+pos within buffer buf.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN359"
+></A
+>5.3.14. RSSVAL(buf,pos,val)</H3
+><P
+>sets the value of the unsigned short (16 bit) big-endian integer at
offset pos within buffer buf to value val.
-refered to as &quot;USHORT&quot;.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2858192"></a>RSIVAL(buf,pos,val)</h3></div></div><p>sets the value of the unsigned 32 bit big-endian integer at offset
-pos within buffer buf to value val.</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2858208"></a>LAN Manager Samba API</h2></div></div><p>
-This section describes the functions need to make a LAN Manager RPC call.
+refered to as "USHORT".</P
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN362"
+></A
+>5.3.15. RSIVAL(buf,pos,val)</H3
+><P
+>sets the value of the unsigned 32 bit big-endian integer at offset
+pos within buffer buf to value val.</P
+></DIV
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN365"
+></A
+>5.4. LAN Manager Samba API</H2
+><P
+>This section describes the functions need to make a LAN Manager RPC call.
This information had been obtained by examining the Samba code and the LAN
Manager 2.0 API documentation. It should not be considered entirely
-reliable.
-</p><p>
-</p><pre class="programlisting">
-call_api(int prcnt, int drcnt, int mprcnt, int mdrcnt,
- char *param, char *data, char **rparam, char **rdata);
-</pre><p>
-</p><p>
-This function is defined in client.c. It uses an SMB transaction to call a
-remote api.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2858243"></a>Parameters</h3></div></div><p>The parameters are as follows:</p><div class="orderedlist"><ol type="1"><li><p>
- prcnt: the number of bytes of parameters begin sent.
-</p></li><li><p>
- drcnt: the number of bytes of data begin sent.
-</p></li><li><p>
- mprcnt: the maximum number of bytes of parameters which should be returned
-</p></li><li><p>
- mdrcnt: the maximum number of bytes of data which should be returned
-</p></li><li><p>
- param: a pointer to the parameters to be sent.
-</p></li><li><p>
- data: a pointer to the data to be sent.
-</p></li><li><p>
- rparam: a pointer to a pointer which will be set to point to the returned
- paramters. The caller of call_api() must deallocate this memory.
-</p></li><li><p>
- rdata: a pointer to a pointer which will be set to point to the returned
- data. The caller of call_api() must deallocate this memory.
-</p></li></ol></div><p>
-These are the parameters which you ought to send, in the order of their
-appearance in the parameter block:
-</p><div class="orderedlist"><ol type="1"><li><p>
-An unsigned 16 bit integer API number. You should set this value with
-SSVAL(). I do not know where these numbers are described.
-</p></li><li><p>
-An ASCIIZ string describing the parameters to the API function as defined
+reliable.</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>call_api(int prcnt, int drcnt, int mprcnt, int mdrcnt,
+ char *param, char *data, char **rparam, char **rdata);</PRE
+></P
+><P
+>This function is defined in client.c. It uses an SMB transaction to call a
+remote api.</P
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN371"
+></A
+>5.4.1. Parameters</H3
+><P
+>The parameters are as follows:</P
+><P
+></P
+><OL
+TYPE="1"
+><LI
+><P
+> prcnt: the number of bytes of parameters begin sent.</P
+></LI
+><LI
+><P
+> drcnt: the number of bytes of data begin sent.</P
+></LI
+><LI
+><P
+> mprcnt: the maximum number of bytes of parameters which should be returned</P
+></LI
+><LI
+><P
+> mdrcnt: the maximum number of bytes of data which should be returned</P
+></LI
+><LI
+><P
+> param: a pointer to the parameters to be sent.</P
+></LI
+><LI
+><P
+> data: a pointer to the data to be sent.</P
+></LI
+><LI
+><P
+> rparam: a pointer to a pointer which will be set to point to the returned
+ paramters. The caller of call_api() must deallocate this memory.</P
+></LI
+><LI
+><P
+> rdata: a pointer to a pointer which will be set to point to the returned
+ data. The caller of call_api() must deallocate this memory.</P
+></LI
+></OL
+><P
+>These are the parameters which you ought to send, in the order of their
+appearance in the parameter block:</P
+><P
+></P
+><OL
+TYPE="1"
+><LI
+><P
+>An unsigned 16 bit integer API number. You should set this value with
+SSVAL(). I do not know where these numbers are described.</P
+></LI
+><LI
+><P
+>An ASCIIZ string describing the parameters to the API function as defined
in the LAN Manager documentation. The first parameter, which is the server
name, is ommited. This string is based uppon the API function as described
-in the manual, not the data which is actually passed.
-</p></li><li><p>
-An ASCIIZ string describing the data structure which ought to be returned.
-</p></li><li><p>
-Any parameters which appear in the function call, as defined in the LAN
-Manager API documentation, after the &quot;Server&quot; and up to and including the
-&quot;uLevel&quot; parameters.
-</p></li><li><p>
-An unsigned 16 bit integer which gives the size in bytes of the buffer we
+in the manual, not the data which is actually passed.</P
+></LI
+><LI
+><P
+>An ASCIIZ string describing the data structure which ought to be returned.</P
+></LI
+><LI
+><P
+>Any parameters which appear in the function call, as defined in the LAN
+Manager API documentation, after the "Server" and up to and including the
+"uLevel" parameters.</P
+></LI
+><LI
+><P
+>An unsigned 16 bit integer which gives the size in bytes of the buffer we
will use to receive the returned array of data structures. Presumably this
-should be the same as mdrcnt. This value should be set with SSVAL().
-</p></li><li><p>
-An ASCIIZ string describing substructures which should be returned. If no
-substructures apply, this string is of zero length.
-</p></li></ol></div><p>
-The code in client.c always calls call_api() with no data. It is unclear
-when a non-zero length data buffer would be sent.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2858395"></a>Return value</h3></div></div><p>
-The returned parameters (pointed to by rparam), in their order of appearance
-are:</p><div class="orderedlist"><ol type="1"><li><p>
-An unsigned 16 bit integer which contains the API function's return code.
-This value should be read with SVAL().
-</p></li><li><p>
-An adjustment which tells the amount by which pointers in the returned
+should be the same as mdrcnt. This value should be set with SSVAL().</P
+></LI
+><LI
+><P
+>An ASCIIZ string describing substructures which should be returned. If no
+substructures apply, this string is of zero length.</P
+></LI
+></OL
+><P
+>The code in client.c always calls call_api() with no data. It is unclear
+when a non-zero length data buffer would be sent.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN406"
+></A
+>5.4.2. Return value</H3
+><P
+>The returned parameters (pointed to by rparam), in their order of appearance
+are:</P
+><P
+></P
+><OL
+TYPE="1"
+><LI
+><P
+>An unsigned 16 bit integer which contains the API function's return code.
+This value should be read with SVAL().</P
+></LI
+><LI
+><P
+>An adjustment which tells the amount by which pointers in the returned
data should be adjusted. This value should be read with SVAL(). Basically,
the address of the start of the returned data buffer should have the returned
pointer value added to it and then have this value subtracted from it in
-order to obtain the currect offset into the returned data buffer.
-</p></li><li><p>
-A count of the number of elements in the array of structures returned.
-It is also possible that this may sometimes be the number of bytes returned.
-</p></li></ol></div><p>
-When call_api() returns, rparam points to the returned parameters. The
+order to obtain the currect offset into the returned data buffer.</P
+></LI
+><LI
+><P
+>A count of the number of elements in the array of structures returned.
+It is also possible that this may sometimes be the number of bytes returned.</P
+></LI
+></OL
+><P
+>When call_api() returns, rparam points to the returned parameters. The
first if these is the result code. It will be zero if the API call
-suceeded. This value by be read with &quot;SVAL(rparam,0)&quot;.
-</p><p>
-The second parameter may be read as &quot;SVAL(rparam,2)&quot;. It is a 16 bit offset
+suceeded. This value by be read with "SVAL(rparam,0)".</P
+><P
+>The second parameter may be read as "SVAL(rparam,2)". It is a 16 bit offset
which indicates what the base address of the returned data buffer was when
it was built on the server. It should be used to correct pointer before
-use.
-</p><p>
-The returned data buffer contains the array of returned data structures.
+use.</P
+><P
+>The returned data buffer contains the array of returned data structures.
Note that all pointers must be adjusted before use. The function
-fix_char_ptr() in client.c can be used for this purpose.
-</p><p>
-The third parameter (which may be read as &quot;SVAL(rparam,4)&quot;) has something to
+fix_char_ptr() in client.c can be used for this purpose.</P
+><P
+>The third parameter (which may be read as "SVAL(rparam,4)") has something to
do with indicating the amount of data returned or possibly the amount of
-data which can be returned if enough buffer space is allowed.
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2858481"></a>Code character table</h2></div></div><p>
-Certain data structures are described by means of ASCIIz strings containing
-code characters. These are the code characters:
-</p><div class="orderedlist"><ol type="1"><li><p>
-W a type byte little-endian unsigned integer
-</p></li><li><p>
-N a count of substructures which follow
-</p></li><li><p>
-D a four byte little-endian unsigned integer
-</p></li><li><p>
-B a byte (with optional count expressed as trailing ASCII digits)
-</p></li><li><p>
-z a four byte offset to a NULL terminated string
-</p></li><li><p>
-l a four byte offset to non-string user data
-</p></li><li><p>
-b an offset to data (with count expressed as trailing ASCII digits)
-</p></li><li><p>
-r pointer to returned data buffer???
-</p></li><li><p>
-L length in bytes of returned data buffer???
-</p></li><li><p>
-h number of bytes of information available???
-</p></li></ol></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="parsing"></a>Chapter6.The smb.conf file</h2></div><div><div class="author"><h3 class="author">Chris Hertel</h3></div></div><div><p class="pubdate">November 1997</p></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2857849">Lexical Analysis</a></dt><dd><dl><dt><a href="#id2857787">Handling of Whitespace</a></dt><dt><a href="#id2858749">Handling of Line Continuation</a></dt><dt><a href="#id2858813">Line Continuation Quirks</a></dt></dl></dd><dt><a href="#id2858913">Syntax</a></dt><dd><dl><dt><a href="#id2858982">About params.c</a></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2857849"></a>Lexical Analysis</h2></div></div><p>
-Basically, the file is processed on a line by line basis. There are
+data which can be returned if enough buffer space is allowed.</P
+></DIV
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN420"
+></A
+>5.5. Code character table</H2
+><P
+>Certain data structures are described by means of ASCIIz strings containing
+code characters. These are the code characters:</P
+><P
+></P
+><OL
+TYPE="1"
+><LI
+><P
+>W a type byte little-endian unsigned integer</P
+></LI
+><LI
+><P
+>N a count of substructures which follow</P
+></LI
+><LI
+><P
+>D a four byte little-endian unsigned integer</P
+></LI
+><LI
+><P
+>B a byte (with optional count expressed as trailing ASCII digits)</P
+></LI
+><LI
+><P
+>z a four byte offset to a NULL terminated string</P
+></LI
+><LI
+><P
+>l a four byte offset to non-string user data</P
+></LI
+><LI
+><P
+>b an offset to data (with count expressed as trailing ASCII digits)</P
+></LI
+><LI
+><P
+>r pointer to returned data buffer???</P
+></LI
+><LI
+><P
+>L length in bytes of returned data buffer???</P
+></LI
+><LI
+><P
+>h number of bytes of information available???</P
+></LI
+></OL
+></DIV
+></DIV
+><DIV
+CLASS="CHAPTER"
+><HR><H1
+><A
+NAME="PARSING"
+></A
+>Chapter 6. The smb.conf file</H1
+><DIV
+CLASS="SECT1"
+><H2
+CLASS="SECT1"
+><A
+NAME="AEN451"
+></A
+>6.1. Lexical Analysis</H2
+><P
+>Basically, the file is processed on a line by line basis. There are
four types of lines that are recognized by the lexical analyzer
-(params.c):
-</p><div class="orderedlist"><ol type="1"><li><p>
-Blank lines - Lines containing only whitespace.
-</p></li><li><p>
-Comment lines - Lines beginning with either a semi-colon or a
-pound sign (';' or '#').
-</p></li><li><p>
-Section header lines - Lines beginning with an open square bracket ('[').
-</p></li><li><p>
-Parameter lines - Lines beginning with any other character.
-(The default line type.)
-</p></li></ol></div><p>
-The first two are handled exclusively by the lexical analyzer, which
-ignores them. The latter two line types are scanned for
-</p><div class="orderedlist"><ol type="1"><li><p>
- - Section names
-</p></li><li><p>
- - Parameter names
-</p></li><li><p>
- - Parameter values
-</p></li></ol></div><p>
-These are the only tokens passed to the parameter loader
+(params.c):</P
+><P
+></P
+><OL
+TYPE="1"
+><LI
+><P
+>Blank lines - Lines containing only whitespace.</P
+></LI
+><LI
+><P
+>Comment lines - Lines beginning with either a semi-colon or a
+pound sign (';' or '#').</P
+></LI
+><LI
+><P
+>Section header lines - Lines beginning with an open square bracket ('[').</P
+></LI
+><LI
+><P
+>Parameter lines - Lines beginning with any other character.
+(The default line type.)</P
+></LI
+></OL
+><P
+>The first two are handled exclusively by the lexical analyzer, which
+ignores them. The latter two line types are scanned for</P
+><P
+></P
+><OL
+TYPE="1"
+><LI
+><P
+> - Section names</P
+></LI
+><LI
+><P
+> - Parameter names</P
+></LI
+><LI
+><P
+> - Parameter values</P
+></LI
+></OL
+><P
+>These are the only tokens passed to the parameter loader
(loadparm.c). Parameter names and values are divided from one
-another by an equal sign: '='.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2857787"></a>Handling of Whitespace</h3></div></div><p>
-Whitespace is defined as all characters recognized by the isspace()
+another by an equal sign: '='.</P
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN472"
+></A
+>6.1.1. Handling of Whitespace</H3
+><P
+>Whitespace is defined as all characters recognized by the isspace()
function (see ctype(3C)) except for the newline character ('\n')
-The newline is excluded because it identifies the end of the line.
-</p><div class="orderedlist"><ol type="1"><li><p>
-The lexical analyzer scans past white space at the beginning of a line.
-</p></li><li><p>
-Section and parameter names may contain internal white space. All
-whitespace within a name is compressed to a single space character.
-</p></li><li><p>
-Internal whitespace within a parameter value is kept verbatim with
+The newline is excluded because it identifies the end of the line.</P
+><P
+></P
+><OL
+TYPE="1"
+><LI
+><P
+>The lexical analyzer scans past white space at the beginning of a line.</P
+></LI
+><LI
+><P
+>Section and parameter names may contain internal white space. All
+whitespace within a name is compressed to a single space character. </P
+></LI
+><LI
+><P
+>Internal whitespace within a parameter value is kept verbatim with
the exception of carriage return characters ('\r'), all of which
-are removed.
-</p></li><li><p>
-Leading and trailing whitespace is removed from names and values.
-</p></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2858749"></a>Handling of Line Continuation</h3></div></div><p>
-Long section header and parameter lines may be extended across
+are removed.</P
+></LI
+><LI
+><P
+>Leading and trailing whitespace is removed from names and values.</P
+></LI
+></OL
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN484"
+></A
+>6.1.2. Handling of Line Continuation</H3
+><P
+>Long section header and parameter lines may be extended across
multiple lines by use of the backslash character ('\\'). Line
-continuation is ignored for blank and comment lines.
-</p><p>
-If the last (non-whitespace) character within a section header or on
+continuation is ignored for blank and comment lines.</P
+><P
+>If the last (non-whitespace) character within a section header or on
a parameter line is a backslash, then the next line will be
(logically) concatonated with the current line by the lexical
-analyzer. For example:
-</p><pre class="programlisting">
- param name = parameter value string \
- with line continuation.
-</pre><p>Would be read as</p><pre class="programlisting">
- param name = parameter value string with line continuation.
-</pre><p>
-Note that there are five spaces following the word 'string',
+analyzer. For example:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+> param name = parameter value string \
+ with line continuation.</PRE
+></P
+><P
+>Would be read as</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+> param name = parameter value string with line continuation.</PRE
+></P
+><P
+>Note that there are five spaces following the word 'string',
representing the one space between 'string' and '\\' in the top
line, plus the four preceeding the word 'with' in the second line.
-(Yes, I'm counting the indentation.)
-</p><p>
-Line continuation characters are ignored on blank lines and at the end
+(Yes, I'm counting the indentation.)</P
+><P
+>Line continuation characters are ignored on blank lines and at the end
of comments. They are *only* recognized within section and parameter
-lines.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2858813"></a>Line Continuation Quirks</h3></div></div><p>Note the following example:</p><pre class="programlisting">
- param name = parameter value string \
+lines.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN495"
+></A
+>6.1.3. Line Continuation Quirks</H3
+><P
+>Note the following example:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+> param name = parameter value string \
\
- with line continuation.
-</pre><p>
-The middle line is *not* parsed as a blank line because it is first
-concatonated with the top line. The result is
-</p><pre class="programlisting">
-param name = parameter value string with line continuation.
-</pre><p>The same is true for comment lines.</p><pre class="programlisting">
- param name = parameter value string \
+ with line continuation.</PRE
+></P
+><P
+>The middle line is *not* parsed as a blank line because it is first
+concatonated with the top line. The result is</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>param name = parameter value string with line continuation.</PRE
+></P
+><P
+>The same is true for comment lines.</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+> param name = parameter value string \
; comment \
- with a comment.
-</pre><p>This becomes:</p><pre class="programlisting">
-param name = parameter value string ; comment with a comment.
-</pre><p>
-On a section header line, the closing bracket (']') is considered a
-terminating character, and the rest of the line is ignored. The lines
-</p><pre class="programlisting">
- [ section name ] garbage \
- param name = value
-</pre><p>are read as</p><pre class="programlisting">
- [section name]
- param name = value
-</pre></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2858913"></a>Syntax</h2></div></div><p>The syntax of the smb.conf file is as follows:</p><pre class="programlisting">
- &lt;file&gt; :== { &lt;section&gt; } EOF
+ with a comment.</PRE
+></P
+><P
+>This becomes:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>param name = parameter value string ; comment with a comment.</PRE
+></P
+><P
+>On a section header line, the closing bracket (']') is considered a
+terminating character, and the rest of the line is ignored. The lines</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+> [ section name ] garbage \
+ param name = value</PRE
+></P
+><P
+>are read as</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+> [section name]
+ param name = value</PRE
+></P
+></DIV
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN515"
+></A
+>6.2. Syntax</H2
+><P
+>The syntax of the smb.conf file is as follows:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+> &lt;file&gt; :== { &lt;section&gt; } EOF
&lt;section&gt; :== &lt;section header&gt; { &lt;parameter line&gt; }
&lt;section header&gt; :== '[' NAME ']'
- &lt;parameter line&gt; :== NAME '=' VALUE NL
-</pre><p>Basically, this means that</p><div class="orderedlist"><ol type="1"><li><p>
- a file is made up of zero or more sections, and is terminated by
- an EOF (we knew that).
-</p></li><li><p>
- A section is made up of a section header followed by zero or more
- parameter lines.
-</p></li><li><p>
- A section header is identified by an opening bracket and
+ &lt;parameter line&gt; :== NAME '=' VALUE NL</PRE
+></P
+><P
+>Basically, this means that</P
+><P
+></P
+><OL
+TYPE="1"
+><LI
+><P
+> a file is made up of zero or more sections, and is terminated by
+ an EOF (we knew that).</P
+></LI
+><LI
+><P
+> A section is made up of a section header followed by zero or more
+ parameter lines.</P
+></LI
+><LI
+><P
+> A section header is identified by an opening bracket and
terminated by the closing bracket. The enclosed NAME identifies
- the section.
-</p></li><li><p>
- A parameter line is divided into a NAME and a VALUE. The *first*
+ the section.</P
+></LI
+><LI
+><P
+> A parameter line is divided into a NAME and a VALUE. The *first*
equal sign on the line separates the NAME from the VALUE. The
- VALUE is terminated by a newline character (NL = '\n').
-</p></li></ol></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2858982"></a>About params.c</h3></div></div><p>
-The parsing of the config file is a bit unusual if you are used to
+ VALUE is terminated by a newline character (NL = '\n').</P
+></LI
+></OL
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN530"
+></A
+>6.2.1. About params.c</H3
+><P
+>The parsing of the config file is a bit unusual if you are used to
lex, yacc, bison, etc. Both lexical analysis (scanning) and parsing
are performed by params.c. Values are loaded via callbacks to
-loadparm.c.
-</p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="unix-smb"></a>Chapter7.NetBIOS in a Unix World</h2></div><div><div class="author"><h3 class="author">Andrew Tridgell</h3></div></div><div><p class="pubdate">April 1995</p></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2858682">Introduction</a></dt><dt><a href="#id2858703">Usernames</a></dt><dt><a href="#id2858620">File Ownership</a></dt><dt><a href="#id2858644">Passwords</a></dt><dt><a href="#id2859208">Locking</a></dt><dt><a href="#id2859270">Deny Modes</a></dt><dt><a href="#id2859300">Trapdoor UIDs</a></dt><dt><a href="#id2859325">Port numbers</a></dt><dt><a href="#id2859371">Protocol Complexity</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2858682"></a>Introduction</h2></div></div><p>
-This is a short document that describes some of the issues that
+loadparm.c.</P
+></DIV
+></DIV
+></DIV
+><DIV
+CLASS="CHAPTER"
+><HR><H1
+><A
+NAME="UNIX-SMB"
+></A
+>Chapter 7. NetBIOS in a Unix World</H1
+><DIV
+CLASS="SECT1"
+><H2
+CLASS="SECT1"
+><A
+NAME="AEN540"
+></A
+>7.1. Introduction</H2
+><P
+>This is a short document that describes some of the issues that
confront a SMB implementation on unix, and how Samba copes with
-them. They may help people who are looking at unix&lt;-&gt;PC
-interoperability.
-</p><p>
-It was written to help out a person who was writing a paper on unix to
-PC connectivity.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2858703"></a>Usernames</h2></div></div><p>
-The SMB protocol has only a loose username concept. Early SMB
+them. They may help people who are looking at unix&#60;-&#62;PC
+interoperability.</P
+><P
+>It was written to help out a person who was writing a paper on unix to
+PC connectivity.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN544"
+></A
+>7.2. Usernames</H2
+><P
+>The SMB protocol has only a loose username concept. Early SMB
protocols (such as CORE and COREPLUS) have no username concept at
all. Even in later protocols clients often attempt operations
(particularly printer operations) without first validating a username
-on the server.
-</p><p>
-Unix security is based around username/password pairs. A unix box
+on the server.</P
+><P
+>Unix security is based around username/password pairs. A unix box
should not allow clients to do any substantive operation without some
-sort of validation.
-</p><p>
-The problem mostly manifests itself when the unix server is in &quot;share
-level&quot; security mode. This is the default mode as the alternative
-&quot;user level&quot; security mode usually forces a client to connect to the
+sort of validation. </P
+><P
+>The problem mostly manifests itself when the unix server is in "share
+level" security mode. This is the default mode as the alternative
+"user level" security mode usually forces a client to connect to the
server as the same user for each connected share, which is
-inconvenient in many sites.
-</p><p>
-In &quot;share level&quot; security the client normally gives a username in the
-&quot;session setup&quot; protocol, but does not supply an accompanying
-password. The client then connects to resources using the &quot;tree
-connect&quot; protocol, and supplies a password. The problem is that the
+inconvenient in many sites.</P
+><P
+>In "share level" security the client normally gives a username in the
+"session setup" protocol, but does not supply an accompanying
+password. The client then connects to resources using the "tree
+connect" protocol, and supplies a password. The problem is that the
user on the PC types the username and the password in different
contexts, unaware that they need to go together to give access to the
server. The username is normally the one the user typed in when they
-&quot;logged onto&quot; the PC (this assumes Windows for Workgroups). The
-password is the one they chose when connecting to the disk or printer.
-</p><p>
-The user often chooses a totally different username for their login as
+"logged onto" the PC (this assumes Windows for Workgroups). The
+password is the one they chose when connecting to the disk or printer.</P
+><P
+>The user often chooses a totally different username for their login as
for the drive connection. Often they also want to access different
drives as different usernames. The unix server needs some way of
-divining the correct username to combine with each password.
-</p><p>
-Samba tries to avoid this problem using several methods. These succeed
+divining the correct username to combine with each password.</P
+><P
+>Samba tries to avoid this problem using several methods. These succeed
in the vast majority of cases. The methods include username maps, the
service%user syntax, the saving of session setup usernames for later
validation and the derivation of the username from the service name
-(either directly or via the user= option).
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2858620"></a>File Ownership</h2></div></div><p>
-The commonly used SMB protocols have no way of saying &quot;you can't do
-that because you don't own the file&quot;. They have, in fact, no concept
-of file ownership at all.
-</p><p>
-This brings up all sorts of interesting problems. For example, when
+(either directly or via the user= option).</P
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN552"
+></A
+>7.3. File Ownership</H2
+><P
+>The commonly used SMB protocols have no way of saying "you can't do
+that because you don't own the file". They have, in fact, no concept
+of file ownership at all.</P
+><P
+>This brings up all sorts of interesting problems. For example, when
you copy a file to a unix drive, and the file is world writeable but
owned by another user the file will transfer correctly but will
receive the wrong date. This is because the utime() call under unix
only succeeds for the owner of the file, or root, even if the file is
world writeable. For security reasons Samba does all file operations
as the validated user, not root, so the utime() fails. This can stuff
-up shared development diectories as programs like &quot;make&quot; will not get
-file time comparisons right.
-</p><p>
-There are several possible solutions to this problem, including
+up shared development diectories as programs like "make" will not get
+file time comparisons right.</P
+><P
+>There are several possible solutions to this problem, including
username mapping, and forcing a specific username for particular
-shares.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2858644"></a>Passwords</h2></div></div><p>
-Many SMB clients uppercase passwords before sending them. I have no
+shares.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN557"
+></A
+>7.4. Passwords</H2
+><P
+>Many SMB clients uppercase passwords before sending them. I have no
idea why they do this. Interestingly WfWg uppercases the password only
if the server is running a protocol greater than COREPLUS, so
-obviously it isn't just the data entry routines that are to blame.
-</p><p>
-Unix passwords are case sensitive. So if users use mixed case
-passwords they are in trouble.
-</p><p>
-Samba can try to cope with this by either using the &quot;password level&quot;
+obviously it isn't just the data entry routines that are to blame.</P
+><P
+>Unix passwords are case sensitive. So if users use mixed case
+passwords they are in trouble.</P
+><P
+>Samba can try to cope with this by either using the "password level"
option which causes Samba to try the offered password with up to the
-specified number of case changes, or by using the &quot;password server&quot;
+specified number of case changes, or by using the "password server"
option which allows Samba to do its validation via another machine
-(typically a WinNT server).
-</p><p>
-Samba supports the password encryption method used by SMB
+(typically a WinNT server).</P
+><P
+>Samba supports the password encryption method used by SMB
clients. Note that the use of password encryption in Microsoft
-networking leads to password hashes that are &quot;plain text equivalent&quot;.
+networking leads to password hashes that are "plain text equivalent".
This means that it is *VERY* important to ensure that the Samba
smbpasswd file containing these password hashes is only readable
by the root user. See the documentation ENCRYPTION.txt for more
-details.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2859208"></a>Locking</h2></div></div><p>
-Since samba 2.2, samba supports other types of locking as well. This
-section is outdated.
-</p><p>
-The locking calls available under a DOS/Windows environment are much
+details.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN563"
+></A
+>7.5. Locking</H2
+><P
+>Since samba 2.2, samba supports other types of locking as well. This
+section is outdated.</P
+><P
+>The locking calls available under a DOS/Windows environment are much
richer than those available in unix. This means a unix server (like
Samba) choosing to use the standard fcntl() based unix locking calls
-to implement SMB locking has to improvise a bit.
-</p><p>
-One major problem is that dos locks can be in a 32 bit (unsigned)
+to implement SMB locking has to improvise a bit.</P
+><P
+>One major problem is that dos locks can be in a 32 bit (unsigned)
range. Unix locking calls are 32 bits, but are signed, giving only a 31
bit range. Unfortunately OLE2 clients use the top bit to select a
-locking range used for OLE semaphores.
-</p><p>
-To work around this problem Samba compresses the 32 bit range into 31
+locking range used for OLE semaphores.</P
+><P
+>To work around this problem Samba compresses the 32 bit range into 31
bits by appropriate bit shifting. This seems to work but is not
ideal. In a future version a separate SMB lockd may be added to cope
-with the problem.
-</p><p>
-It also doesn't help that many unix lockd daemons are very buggy and
+with the problem.</P
+><P
+>It also doesn't help that many unix lockd daemons are very buggy and
crash at the slightest provocation. They normally go mostly unused in
a unix environment because few unix programs use byte range
locking. The stress of huge numbers of lock requests from dos/windows
-clients can kill the daemon on some systems.
-</p><p>
-The second major problem is the &quot;opportunistic locking&quot; requested by
+clients can kill the daemon on some systems.</P
+><P
+>The second major problem is the "opportunistic locking" requested by
some clients. If a client requests opportunistic locking then it is
asking the server to notify it if anyone else tries to do something on
the same file, at which time the client will say if it is willing to
give up its lock. Unix has no simple way of implementing
-opportunistic locking, and currently Samba has no support for it.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2859270"></a>Deny Modes</h2></div></div><p>
-When a SMB client opens a file it asks for a particular &quot;deny mode&quot; to
+opportunistic locking, and currently Samba has no support for it.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN571"
+></A
+>7.6. Deny Modes</H2
+><P
+>When a SMB client opens a file it asks for a particular "deny mode" to
be placed on the file. These modes (DENY_NONE, DENY_READ, DENY_WRITE,
DENY_ALL, DENY_FCB and DENY_DOS) specify what actions should be
allowed by anyone else who tries to use the file at the same time. If
DENY_READ is placed on the file, for example, then any attempt to open
-the file for reading should fail.
-</p><p>
-Unix has no equivalent notion. To implement this Samba uses either lock
+the file for reading should fail.</P
+><P
+>Unix has no equivalent notion. To implement this Samba uses either lock
files based on the files inode and placed in a separate lock
directory or a shared memory implementation. The lock file method
is clumsy and consumes processing and file resources,
the shared memory implementation is vastly prefered and is turned on
-by default for those systems that support it.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2859300"></a>Trapdoor UIDs</h2></div></div><p>
-A SMB session can run with several uids on the one socket. This
+by default for those systems that support it.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN575"
+></A
+>7.7. Trapdoor UIDs</H2
+><P
+>A SMB session can run with several uids on the one socket. This
happens when a user connects to two shares with different
usernames. To cope with this the unix server needs to switch uids
within the one process. On some unixes (such as SCO) this is not
possible. This means that on those unixes the client is restricted to
-a single uid.
-</p><p>
-Note that you can also get the &quot;trapdoor uid&quot; message for other
-reasons. Please see the FAQ for details.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2859325"></a>Port numbers</h2></div></div><p>
-There is a convention that clients on sockets use high &quot;unprivilaged&quot;
-port numbers (&gt;1000) and connect to servers on low &quot;privilaged&quot; port
+a single uid.</P
+><P
+>Note that you can also get the "trapdoor uid" message for other
+reasons. Please see the FAQ for details.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN579"
+></A
+>7.8. Port numbers</H2
+><P
+>There is a convention that clients on sockets use high "unprivilaged"
+port numbers (&#62;1000) and connect to servers on low "privilaged" port
numbers. This is enforced in Unix as non-root users can't open a
-socket for listening on port numbers less than 1000.
-</p><p>
-Most PC based SMB clients (such as WfWg and WinNT) don't follow this
+socket for listening on port numbers less than 1000.</P
+><P
+>Most PC based SMB clients (such as WfWg and WinNT) don't follow this
convention completely. The main culprit is the netbios nameserving on
udp port 137. Name query requests come from a source port of 137. This
is a problem when you combine it with the common firewalling technique
of not allowing incoming packets on low port numbers. This means that
these clients can't query a netbios nameserver on the other side of a
-low port based firewall.
-</p><p>
-The problem is more severe with netbios node status queries. I've
+low port based firewall.</P
+><P
+>The problem is more severe with netbios node status queries. I've
found that WfWg, Win95 and WinNT3.5 all respond to netbios node status
queries on port 137 no matter what the source port was in the
request. This works between machines that are both using port 137, but
@@ -1016,179 +2755,421 @@ it means it's not possible for a unix user to do a node status request
to any of these OSes unless they are running as root. The answer comes
back, but it goes to port 137 which the unix user can't listen
on. Interestingly WinNT3.1 got this right - it sends node status
-responses back to the source port in the request.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2859371"></a>Protocol Complexity</h2></div></div><p>
-There are many &quot;protocol levels&quot; in the SMB protocol. It seems that
+responses back to the source port in the request.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN584"
+></A
+>7.9. Protocol Complexity</H2
+><P
+>There are many "protocol levels" in the SMB protocol. It seems that
each time new functionality was added to a Microsoft operating system,
they added the equivalent functions in a new protocol level of the SMB
-protocol to &quot;externalise&quot; the new capabilities.
-</p><p>
-This means the protocol is very &quot;rich&quot;, offering many ways of doing
+protocol to "externalise" the new capabilities.</P
+><P
+>This means the protocol is very "rich", offering many ways of doing
each file operation. This means SMB servers need to be complex and
large. It also means it is very difficult to make them bug free. It is
not just Samba that suffers from this problem, other servers such as
WinNT don't support every variation of every call and it has almost
certainly been a headache for MS developers to support the myriad of
-SMB calls that are available.
-</p><p>
-There are about 65 &quot;top level&quot; operations in the SMB protocol (things
+SMB calls that are available.</P
+><P
+>There are about 65 "top level" operations in the SMB protocol (things
like SMBread and SMBwrite). Some of these include hundreds of
sub-functions (SMBtrans has at least 120 sub-functions, like
DosPrintQAdd and NetSessionEnum). All of them take several options
that can change the way they work. Many take dozens of possible
-&quot;information levels&quot; that change the structures that need to be
-returned. Samba supports all but 2 of the &quot;top level&quot; functions. It
+"information levels" that change the structures that need to be
+returned. Samba supports all but 2 of the "top level" functions. It
supports only 8 (so far) of the SMBtrans sub-functions. Even NT
-doesn't support them all.
-</p><p>
-Samba currently supports up to the &quot;NT LM 0.12&quot; protocol, which is the
+doesn't support them all.</P
+><P
+>Samba currently supports up to the "NT LM 0.12" protocol, which is the
one preferred by Win95 and WinNT3.5. Luckily this protocol level has a
-&quot;capabilities&quot; field which specifies which super-duper new-fangled
+"capabilities" field which specifies which super-duper new-fangled
options the server suports. This helps to make the implementation of
-this protocol level much easier.
-</p><p>
-There is also a problem with the SMB specications. SMB is a X/Open
+this protocol level much easier.</P
+><P
+>There is also a problem with the SMB specications. SMB is a X/Open
spec, but the X/Open book is far from ideal, and fails to cover many
important issues, leaving much to the imagination. Microsoft recently
renamed the SMB protocol CIFS (Common Internet File System) and have
published new specifications. These are far superior to the old
X/Open documents but there are still undocumented calls and features.
This specification is actively being worked on by a CIFS developers
-mailing list hosted by Microsft.
-</p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="tracing"></a>Chapter8.Tracing samba system calls</h2></div><div><div class="author"><h3 class="author">Andrew Tridgell</h3><div class="affiliation"><span class="orgname">Samba Team<br></span></div></div></div></div><p>
-This file describes how to do a system call trace on Samba to work out
+mailing list hosted by Microsft.</P
+></DIV
+></DIV
+><DIV
+CLASS="CHAPTER"
+><HR><H1
+><A
+NAME="TRACING"
+></A
+>Chapter 8. Tracing samba system calls</H1
+><P
+>This file describes how to do a system call trace on Samba to work out
what its doing wrong. This is not for the faint of heart, but if you
-are reading this then you are probably desperate.
-</p><p>
-Actually its not as bad as the the above makes it sound, just don't
-expect the output to be very pretty :-)
-</p><p>
-Ok, down to business. One of the big advantages of unix systems is
+are reading this then you are probably desperate.</P
+><P
+>Actually its not as bad as the the above makes it sound, just don't
+expect the output to be very pretty :-)</P
+><P
+>Ok, down to business. One of the big advantages of unix systems is
that they nearly all come with a system trace utility that allows you
to monitor all system calls that a program is making. This is
extremely using for debugging and also helps when trying to work out
why something is slower than you expect. You can use system tracing
-without any special compilation options.
-</p><p>
-The system trace utility is called different things on different
+without any special compilation options. </P
+><P
+>The system trace utility is called different things on different
systems. On Linux systems its called strace. Under SunOS 4 its called
trace. Under SVR4 style systems (including solaris) its called
-truss. Under many BSD systems its called ktrace.
-</p><p>
-The first thing you should do is read the man page for your native
+truss. Under many BSD systems its called ktrace. </P
+><P
+>The first thing you should do is read the man page for your native
system call tracer. In the discussion below I'll assume its called
strace as strace is the only portable system tracer (its available for
free for many unix types) and its also got some of the nicest
-features.
-</p><p>
-Next, try using strace on some simple commands. For example, <b>strace
-ls</b> or <b>strace echo hello</b>.
-</p><p>
+features.</P
+><P
+>Next, try using strace on some simple commands. For example, <B
+CLASS="COMMAND"
+>strace
+ls</B
+> or <B
+CLASS="COMMAND"
+>strace echo hello</B
+>.</P
+><P
+>
You'll notice that it produces a LOT of output. It is showing you the
arguments to every system call that the program makes and the
result. Very little happens in a program without a system call so you
get lots of output. You'll also find that it produces a lot of
-&quot;preamble&quot; stuff showing the loading of shared libraries etc. Ignore
-this (unless its going wrong!)
-</p><p>
-For example, the only line that really matters in the <b>strace echo
-hello</b> output is:
-</p><pre class="programlisting">
-write(1, &quot;hello\n&quot;, 6) = 6
-</pre><p>all the rest is just setting up to run the program.</p><p>
-Ok, now you're familiar with strace. To use it on Samba you need to
+"preamble" stuff showing the loading of shared libraries etc. Ignore
+this (unless its going wrong!)</P
+><P
+>For example, the only line that really matters in the <B
+CLASS="COMMAND"
+>strace echo
+hello</B
+> output is:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>write(1, "hello\n", 6) = 6</PRE
+></P
+><P
+>all the rest is just setting up to run the program.</P
+><P
+>Ok, now you're familiar with strace. To use it on Samba you need to
strace the running smbd daemon. The way I tend ot use it is to first
login from my Windows PC to the Samba server, then use smbstatus to
find which process ID that client is attached to, then as root I do
-<b>strace -p PID</b> to attach to that process. I normally redirect the
+<B
+CLASS="COMMAND"
+>strace -p PID</B
+> to attach to that process. I normally redirect the
stderr output from this command to a file for later perusal. For
-example, if I'm using a csh style shell:
-</p><p><b>strace -f -p 3872 &gt;&amp; strace.out</b></p><p>or with a sh style shell:</p><p><b>strace -f -p 3872 &gt; strace.out 2&gt;&amp;1</b></p><p>
-Note the &quot;-f&quot; option. This is only available on some systems, and
+example, if I'm using a csh style shell:</P
+><P
+><B
+CLASS="COMMAND"
+>strace -f -p 3872 &#62;&#38; strace.out</B
+></P
+><P
+>or with a sh style shell:</P
+><P
+><B
+CLASS="COMMAND"
+>strace -f -p 3872 &#62; strace.out 2&#62;&#38;1</B
+></P
+><P
+>Note the "-f" option. This is only available on some systems, and
allows you to trace not just the current process, but any children it
forks. This is great for finding printing problems caused by the
-&quot;print command&quot; being wrong.
-</p><p>
-Once you are attached you then can do whatever it is on the client
+"print command" being wrong.</P
+><P
+>Once you are attached you then can do whatever it is on the client
that is causing problems and you will capture all the system calls
-that smbd makes.
-</p><p>
-So how do you interpret the results? Generally I search through the
+that smbd makes. </P
+><P
+>So how do you interpret the results? Generally I search through the
output for strings that I know will appear when the problem
happens. For example, if I am having touble with permissions on a file
I would search for that files name in the strace output and look at
the surrounding lines. Another trick is to match up file descriptor
-numbers and &quot;follow&quot; what happens to an open file until it is closed.
-</p><p>
-Beyond this you will have to use your initiative. To give you an idea
+numbers and "follow" what happens to an open file until it is closed.</P
+><P
+>Beyond this you will have to use your initiative. To give you an idea
of what you are looking for here is a piece of strace output that
-shows that <tt>/dev/null</tt> is not world writeable, which
-causes printing to fail with Samba:
-</p><pre class="programlisting">
-[pid 28268] open(&quot;/dev/null&quot;, O_RDWR) = -1 EACCES (Permission denied)
-[pid 28268] open(&quot;/dev/null&quot;, O_WRONLY) = -1 EACCES (Permission denied)
-</pre><p>
-The process is trying to first open <tt>/dev/null</tt> read-write
-then read-only. Both fail. This means <tt>/dev/null</tt> has
-incorrect permissions.
-</p></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="ntdomain"></a>Chapter9.NT Domain RPC's</h2></div><div><div class="author"><h3 class="author">Luke Leighton</h3><div class="affiliation"><div class="address"><p><tt>&lt;<a href="mailto:lkcl@switchboard.net">lkcl@switchboard.net</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author">Paul Ashton</h3><div class="affiliation"><div class="address"><p><tt>&lt;<a href="mailto:paul@argo.demon.co.uk">paul@argo.demon.co.uk</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author">Duncan Stansfield</h3><div class="affiliation"><div class="address"><p><tt>&lt;<a href="mailto:duncans@sco.com">duncans@sco.com</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate">01 November 97(version 0.0.24)</p></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2859563">Introduction</a></dt><dd><dl><dt><a href="#id2859980">Sources</a></dt><dt><a href="#id2860014">Credits</a></dt></dl></dd><dt><a href="#id2860053">Notes and Structures</a></dt><dd><dl><dt><a href="#id2860060">Notes</a></dt><dt><a href="#id2860137">Enumerations</a></dt><dt><a href="#id2860350">Structures</a></dt></dl></dd><dt><a href="#id2863307">MSRPC over Transact Named Pipe</a></dt><dd><dl><dt><a href="#id2863320">MSRPC Pipes</a></dt><dt><a href="#id2863422">Header</a></dt><dt><a href="#id2864296">Tail</a></dt><dt><a href="#id2864342">RPC Bind / Bind Ack</a></dt><dt><a href="#id2864522">NTLSA Transact Named Pipe</a></dt><dt><a href="#id2864687">LSA Open Policy</a></dt><dt><a href="#id2864813">LSA Query Info Policy</a></dt><dt><a href="#id2864921">LSA Enumerate Trusted Domains</a></dt><dt><a href="#id2865012">LSA Open Secret</a></dt><dt><a href="#id2865122">LSA Close</a></dt><dt><a href="#id2865188">LSA Lookup SIDS</a></dt><dt><a href="#id2865399">LSA Lookup Names</a></dt></dl></dd><dt><a href="#id2865625">NETLOGON rpc Transact Named Pipe</a></dt><dd><dl><dt><a href="#id2865786">LSA Request Challenge</a></dt><dt><a href="#id2865921">LSA Authenticate 2</a></dt><dt><a href="#id2866069">LSA Server Password Set</a></dt><dt><a href="#id2866185">LSA SAM Logon</a></dt><dt><a href="#id2866299">LSA SAM Logoff</a></dt></dl></dd><dt><a href="#id2866391">\\MAILSLOT\NET\NTLOGON</a></dt><dd><dl><dt><a href="#id2866408">Query for PDC</a></dt><dt><a href="#id2866670">SAM Logon</a></dt></dl></dd><dt><a href="#id2866996">SRVSVC Transact Named Pipe</a></dt><dd><dl><dt><a href="#id2867041">Net Share Enum</a></dt><dt><a href="#id2867261">Net Server Get Info</a></dt></dl></dd><dt><a href="#id2867378">Cryptographic side of NT Domain Authentication</a></dt><dd><dl><dt><a href="#id2867386">Definitions</a></dt><dt><a href="#id2867548">Protocol</a></dt><dt><a href="#id2867629">Comments</a></dt></dl></dd><dt><a href="#id2867679">SIDs and RIDs</a></dt><dd><dl><dt><a href="#id2867719">Well-known SIDs</a></dt><dt><a href="#id2868034">Well-known RIDS</a></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2859563"></a>Introduction</h2></div></div><p>
-This document contains information to provide an NT workstation with login
-services, without the need for an NT server. It is the sgml version of <a href="http://mailhost.cb1.com/~lkcl/cifsntdomain.txt" target="_top">http://mailhost.cb1.com/~lkcl/cifsntdomain.txt</a>, controlled by Luke.
-</p><p>
-It should be possible to select a domain instead of a workgroup (in the NT
+shows that <TT
+CLASS="FILENAME"
+>/dev/null</TT
+> is not world writeable, which
+causes printing to fail with Samba:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>[pid 28268] open("/dev/null", O_RDWR) = -1 EACCES (Permission denied)
+[pid 28268] open("/dev/null", O_WRONLY) = -1 EACCES (Permission denied)</PRE
+></P
+><P
+>The process is trying to first open <TT
+CLASS="FILENAME"
+>/dev/null</TT
+> read-write
+then read-only. Both fail. This means <TT
+CLASS="FILENAME"
+>/dev/null</TT
+> has
+incorrect permissions.</P
+></DIV
+><DIV
+CLASS="CHAPTER"
+><HR><H1
+><A
+NAME="NTDOMAIN"
+></A
+>Chapter 9. NT Domain RPC's</H1
+><DIV
+CLASS="SECT1"
+><H2
+CLASS="SECT1"
+><A
+NAME="AEN652"
+></A
+>9.1. Introduction</H2
+><P
+>This document contains information to provide an NT workstation with login
+services, without the need for an NT server. It is the sgml version of <A
+HREF="http://mailhost.cb1.com/~lkcl/cifsntdomain.txt"
+TARGET="_top"
+>http://mailhost.cb1.com/~lkcl/cifsntdomain.txt</A
+>, controlled by Luke.</P
+><P
+>It should be possible to select a domain instead of a workgroup (in the NT
workstation's TCP/IP settings) and after the obligatory reboot, type in a
username, password, select a domain and successfully log in. I would
appreciate any feedback on your experiences with this process, and any
-comments, corrections and additions to this document.
-</p><p>
-The packets described here can be easily derived from (and are probably
+comments, corrections and additions to this document.</P
+><P
+>The packets described here can be easily derived from (and are probably
better understood using) Netmon.exe. You will need to use the version
of Netmon that matches your system, in order to correctly decode the
NETLOGON, lsarpc and srvsvc Transact pipes. This document is derived from
NT Service Pack 1 and its corresponding version of Netmon. It is intended
that an annotated packet trace be produced, which will likely be more
-instructive than this document.
-</p><p>
-Also needed, to fully implement NT Domain Login Services, is the
+instructive than this document.</P
+><P
+>Also needed, to fully implement NT Domain Login Services, is the
document describing the cryptographic part of the NT authentication.
This document is available from comp.protocols.smb; from the ntsecurity.net
-digest and from the samba digest, amongst other sources.
-</p><p>
-A copy is available from:
-</p><p><a href="http://ntbugtraq.rc.on.ca/SCRIPTS/WA.EXE?A2=ind9708;L=ntbugtraq;O=A;P=2935" target="_top">http://ntbugtraq.rc.on.ca/SCRIPTS/WA.EXE?A2=ind9708;L=ntbugtraq;O=A;P=2935</a></p><p><a href="http://mailhost.cb1.com/~lkcl/crypt.html" target="_top">http://mailhost.cb1.com/~lkcl/crypt.html</a></p><p>
-A c-code implementation, provided by <a href="mailto:linus@incolumitas.se" target="_top">Linus Nordberg</a>
-of this protocol is available from:
-</p><p><a href="http://samba.org/cgi-bin/mfs/01/digest/1997/97aug/0391.html" target="_top">http://samba.org/cgi-bin/mfs/01/digest/1997/97aug/0391.html</a></p><p><a href="http://mailhost.cb1.com/~lkcl/crypt.txt" target="_top">http://mailhost.cb1.com/~lkcl/crypt.txt</a></p><p>
-Also used to provide debugging information is the Check Build version of
+digest and from the samba digest, amongst other sources.</P
+><P
+>A copy is available from:</P
+><P
+><A
+HREF="http://ntbugtraq.rc.on.ca/SCRIPTS/WA.EXE?A2=ind9708;L=ntbugtraq;O=A;P=2935"
+TARGET="_top"
+>http://ntbugtraq.rc.on.ca/SCRIPTS/WA.EXE?A2=ind9708;L=ntbugtraq;O=A;P=2935</A
+></P
+><P
+><A
+HREF="http://mailhost.cb1.com/~lkcl/crypt.html"
+TARGET="_top"
+>http://mailhost.cb1.com/~lkcl/crypt.html</A
+></P
+><P
+>A c-code implementation, provided by <A
+HREF="mailto:linus@incolumitas.se"
+TARGET="_top"
+>Linus Nordberg</A
+>
+of this protocol is available from:</P
+><P
+><A
+HREF="http://samba.org/cgi-bin/mfs/01/digest/1997/97aug/0391.html"
+TARGET="_top"
+>http://samba.org/cgi-bin/mfs/01/digest/1997/97aug/0391.html</A
+></P
+><P
+><A
+HREF="http://mailhost.cb1.com/~lkcl/crypt.txt"
+TARGET="_top"
+>http://mailhost.cb1.com/~lkcl/crypt.txt</A
+></P
+><P
+>Also used to provide debugging information is the Check Build version of
NT workstation, and enabling full debugging in NETLOGON. This is
-achieved by setting the following REG_SZ registry key to 0x1ffffff:
-</p><p><tt>HKLM\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters</tt></p><p><span class="emphasis"><em>Incorrect direct editing of the registry can cause your
+achieved by setting the following REG_SZ registry key to 0x1ffffff:</P
+><P
+><TT
+CLASS="FILENAME"
+>HKLM\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters</TT
+></P
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Incorrect direct editing of the registry can cause your
machine to fail. Then again, so can incorrect implementation of this
-protocol. See &quot;Liability:&quot; above.</em></span></p><p>
-Bear in mind that each packet over-the-wire will have its origin in an
+protocol. See "Liability:" above.</I
+></SPAN
+></P
+><P
+>Bear in mind that each packet over-the-wire will have its origin in an
API call. Therefore, there are likely to be structures, enumerations
-and defines that are usefully documented elsewhere.
-</p><p>
-This document is by no means complete or authoritative. Missing sections
-include, but are not limited to:
-</p><div class="orderedlist"><ol type="1"><li><p>Mappings of RIDs to usernames (and vice-versa).</p></li><li><p>What a User ID is and what a Group ID is.</p></li><li><p>The exact meaning/definition of various magic constants or enumerations.</p></li><li><p>The reply error code and use of that error code when a
+and defines that are usefully documented elsewhere.</P
+><P
+>This document is by no means complete or authoritative. Missing sections
+include, but are not limited to:</P
+><P
+></P
+><OL
+TYPE="1"
+><LI
+><P
+>Mappings of RIDs to usernames (and vice-versa).</P
+></LI
+><LI
+><P
+>What a User ID is and what a Group ID is.</P
+></LI
+><LI
+><P
+>The exact meaning/definition of various magic constants or enumerations.</P
+></LI
+><LI
+><P
+>The reply error code and use of that error code when a
workstation becomes a member of a domain (to be described later).
Failure to return this error code will make the workstation report
-that it is already a member of the domain.</p></li><li><p>the cryptographic side of the NetrServerPasswordSet command,
+that it is already a member of the domain.</P
+></LI
+><LI
+><P
+>the cryptographic side of the NetrServerPasswordSet command,
which would allow the workstation to change its password. This password is
used to generate the long-term session key. [It is possible to reject this
-command, and keep the default workstation password].</p></li></ol></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2859980"></a>Sources</h3></div></div><table class="simplelist" border="0" summary="Simple list"><tr><td>cket Traces from Netmonitor (Service Pack 1 and above)</td></tr><tr><td>ul Ashton and Luke Leighton's other &quot;NT Domain&quot; doc.</td></tr><tr><td>FS documentation - cifs6.txt</td></tr><tr><td>FS documentation - cifsrap2.txt</td></tr></table></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2860014"></a>Credits</h3></div></div><table class="simplelist" border="0" summary="Simple list"><tr><td>Paul Ashton: loads of work with Net Monitor; understanding the NT authentication system; reference implementation of the NT domain support on which this document is originally based.</td></tr><tr><td>Duncan Stansfield: low-level analysis of MSRPC Pipes.</td></tr><tr><td>Linus Nordberg: producing c-code from Paul's crypto spec.</td></tr><tr><td>Windows Sourcer development team</td></tr></table></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2860053"></a>Notes and Structures</h2></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2860060"></a>Notes</h3></div></div><div class="orderedlist"><ol type="1"><li><p>
-In the SMB Transact pipes, some &quot;Structures&quot;, described here, appear to be
+command, and keep the default workstation password].</P
+></LI
+></OL
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN688"
+></A
+>9.1.1. Sources</H3
+><P
+></P
+><TABLE
+BORDER="0"
+><TBODY
+><TR
+><TD
+>cket Traces from Netmonitor (Service Pack 1 and above)</TD
+></TR
+><TR
+><TD
+>ul Ashton and Luke Leighton's other "NT Domain" doc.</TD
+></TR
+><TR
+><TD
+>FS documentation - cifs6.txt</TD
+></TR
+><TR
+><TD
+>FS documentation - cifsrap2.txt</TD
+></TR
+></TBODY
+></TABLE
+><P
+></P
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN695"
+></A
+>9.1.2. Credits</H3
+><P
+></P
+><TABLE
+BORDER="0"
+><TBODY
+><TR
+><TD
+>Paul Ashton: loads of work with Net Monitor; understanding the NT authentication system; reference implementation of the NT domain support on which this document is originally based.</TD
+></TR
+><TR
+><TD
+>Duncan Stansfield: low-level analysis of MSRPC Pipes.</TD
+></TR
+><TR
+><TD
+>Linus Nordberg: producing c-code from Paul's crypto spec.</TD
+></TR
+><TR
+><TD
+>Windows Sourcer development team</TD
+></TR
+></TBODY
+></TABLE
+><P
+></P
+></DIV
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN702"
+></A
+>9.2. Notes and Structures</H2
+><DIV
+CLASS="SECT2"
+><H3
+CLASS="SECT2"
+><A
+NAME="AEN704"
+></A
+>9.2.1. Notes</H3
+><P
+></P
+><OL
+TYPE="1"
+><LI
+><P
+>In the SMB Transact pipes, some "Structures", described here, appear to be
4-byte aligned with the SMB header, at their start. Exactly which
-&quot;Structures&quot; need aligning is not precisely known or documented.
-</p></li><li><p>
-In the UDP NTLOGON Mailslots, some &quot;Structures&quot;, described here, appear to be
-2-byte aligned with the start of the mailslot, at their start.
-</p></li><li><p>
-Domain SID is of the format S-revision-version-auth1-auth2...authN.
-e.g S-1-5-123-456-789-123-456. the 5 could be a sub-revision.
-</p></li><li><p>
-any undocumented buffer pointers must be non-zero if the string buffer it
+"Structures" need aligning is not precisely known or documented.</P
+></LI
+><LI
+><P
+>In the UDP NTLOGON Mailslots, some "Structures", described here, appear to be
+2-byte aligned with the start of the mailslot, at their start.</P
+></LI
+><LI
+><P
+>Domain SID is of the format S-revision-version-auth1-auth2...authN.
+e.g S-1-5-123-456-789-123-456. the 5 could be a sub-revision.</P
+></LI
+><LI
+><P
+>any undocumented buffer pointers must be non-zero if the string buffer it
refers to contains characters. exactly what value they should be is unknown.
0x0000 0002 seems to do the trick to indicate that the buffer exists. a
NULL buffer pointer indicates that the string buffer is of zero length.
@@ -1197,90 +3178,3707 @@ refers to is NOT put into (or taken out of) the SMB data stream. This is
empirically derived from, for example, the LSA SAM Logon response packet,
where if the buffer pointer is NULL, the user information is not inserted
into the data stream. Exactly what happens with an array of buffer pointers
-is not known, although an educated guess can be made.
-</p></li><li><p>
-an array of structures (a container) appears to have a count and a pointer.
+is not known, although an educated guess can be made.</P
+></LI
+><LI
+><P
+>an array of structures (a container) appears to have a count and a pointer.
if the count is zero, the pointer is also zero. no further data is put
into or taken out of the SMB data stream. if the count is non-zero, then
the pointer is also non-zero. immediately following the pointer is the
count again, followed by an array of container sub-structures. the count
-appears a third time after the last sub-structure.
-</p></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2860137"></a>Enumerations</h3></div></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2860144"></a>MSRPC Header type</h4></div></div><p>command number in the msrpc packet header</p><div class="variablelist"><dl><dt><span class="term">MSRPC_Request:</span></dt><dd><p>0x00</p></dd><dt><span class="term">MSRPC_Response:</span></dt><dd><p>0x02</p></dd><dt><span class="term">MSRPC_Bind:</span></dt><dd><p>0x0B</p></dd><dt><span class="term">MSRPC_BindAck:</span></dt><dd><p>0x0C</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2860218"></a>MSRPC Packet info</h4></div></div><p>The meaning of these flags is undocumented</p><div class="variablelist"><dl><dt><span class="term">FirstFrag:</span></dt><dd><p>0x01 </p></dd><dt><span class="term">LastFrag:</span></dt><dd><p>0x02 </p></dd><dt><span class="term">NotaFrag:</span></dt><dd><p>0x04 </p></dd><dt><span class="term">RecRespond:</span></dt><dd><p>0x08 </p></dd><dt><span class="term">NoMultiplex:</span></dt><dd><p>0x10 </p></dd><dt><span class="term">NotForIdemp:</span></dt><dd><p>0x20 </p></dd><dt><span class="term">NotforBcast:</span></dt><dd><p>0x40 </p></dd><dt><span class="term">NoUuid:</span></dt><dd><p>0x80 </p></dd></dl></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2860350"></a>Structures</h3></div></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2860357"></a>VOID *</h4></div></div><p>sizeof VOID* is 32 bits.</p></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2860368"></a>char</h4></div></div><p>sizeof char is 8 bits.</p></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2860380"></a>UTIME</h4></div></div><p>UTIME is 32 bits, indicating time in seconds since 01jan1970. documented in cifs6.txt (section 3.5 page, page 30).</p></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2860393"></a>NTTIME</h4></div></div><p>NTTIME is 64 bits. documented in cifs6.txt (section 3.5 page, page 30).</p></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2860405"></a>DOM_SID (domain SID structure)</h4></div></div><div class="variablelist"><dl><dt><span class="term">UINT32</span></dt><dd><p>num of sub-authorities in domain SID</p></dd><dt><span class="term">UINT8</span></dt><dd><p>SID revision number</p></dd><dt><span class="term">UINT8</span></dt><dd><p>num of sub-authorities in domain SID</p></dd><dt><span class="term">UINT8[6]</span></dt><dd><p>6 bytes for domain SID - Identifier Authority.</p></dd><dt><span class="term">UINT16[n_subauths]</span></dt><dd><p>domain SID sub-authorities</p></dd></dl></div><p><span class="emphasis"><em>Note: the domain SID is documented elsewhere.</em></span>
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2860499"></a>STR (string)</h4></div></div><p>STR (string) is a char[] : a null-terminated string of ascii characters.</p></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2860513"></a>UNIHDR (unicode string header) </h4></div></div><div class="variablelist"><dl><dt><span class="term">UINT16</span></dt><dd><p>length of unicode string</p></dd><dt><span class="term">UINT16</span></dt><dd><p>max length of unicode string</p></dd><dt><span class="term">UINT32</span></dt><dd><p>4 - undocumented.</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2860569"></a>UNIHDR2 (unicode string header plus buffer pointer)</h4></div></div><div class="variablelist"><dl><dt><span class="term">UNIHDR</span></dt><dd><p>unicode string header</p></dd><dt><span class="term">VOID*</span></dt><dd><p>undocumented buffer pointer</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2860611"></a>UNISTR (unicode string)</h4></div></div><div class="variablelist"><dl><dt><span class="term">UINT16[]</span></dt><dd><p>null-terminated string of unicode characters.</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2860639"></a>NAME (length-indicated unicode string)</h4></div></div><div class="variablelist"><dl><dt><span class="term">UINT32</span></dt><dd><p>length of unicode string</p></dd><dt><span class="term">UINT16[]</span></dt><dd><p>null-terminated string of unicode characters.</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2860682"></a>UNISTR2 (aligned unicode string)</h4></div></div><div class="variablelist"><dl><dt><span class="term">UINT8[]</span></dt><dd><p>padding to get unicode string 4-byte aligned with the start of the SMB header.</p></dd><dt><span class="term">UINT32</span></dt><dd><p>max length of unicode string</p></dd><dt><span class="term">UINT32</span></dt><dd><p>0 - undocumented</p></dd><dt><span class="term">UINT32</span></dt><dd><p>length of unicode string</p></dd><dt><span class="term">UINT16[]</span></dt><dd><p>string of uncode characters</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2860768"></a>OBJ_ATTR (object attributes)</h4></div></div><div class="variablelist"><dl><dt><span class="term">UINT32</span></dt><dd><p>0x18 - length (in bytes) including the length field.</p></dd><dt><span class="term">VOID*</span></dt><dd><p>0 - root directory (pointer)</p></dd><dt><span class="term">VOID*</span></dt><dd><p>0 - object name (pointer)</p></dd><dt><span class="term">UINT32</span></dt><dd><p>0 - attributes (undocumented)</p></dd><dt><span class="term">VOID*</span></dt><dd><p>0 - security descriptior (pointer)</p></dd><dt><span class="term">UINT32</span></dt><dd><p>0 - security quality of service</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2860861"></a>POL_HND (LSA policy handle)</h4></div></div><div class="variablelist"><dl><dt><span class="term">char[20]</span></dt><dd><p>policy handle</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2860889"></a>DOM_SID2 (domain SID structure, SIDS stored in unicode)</h4></div></div><div class="variablelist"><dl><dt><span class="term">UINT32</span></dt><dd><p>5 - SID type</p></dd><dt><span class="term">UINT32</span></dt><dd><p>0 - undocumented</p></dd><dt><span class="term">UNIHDR2</span></dt><dd><p>domain SID unicode string header</p></dd><dt><span class="term">UNISTR</span></dt><dd><p>domain SID unicode string</p></dd></dl></div><p><span class="emphasis"><em>Note: there is a conflict between the unicode string header and the unicode string itself as to which to use to indicate string length. this will need to be resolved.</em></span></p><p><span class="emphasis"><em>Note: the SID type indicates, for example, an alias; a well-known group etc. this is documented somewhere.</em></span></p></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2860976"></a>DOM_RID (domain RID structure)</h4></div></div><div class="variablelist"><dl><dt><span class="term">UINT32</span></dt><dd><p>5 - well-known SID. 1 - user SID (see ShowACLs)</p></dd><dt><span class="term">UINT32</span></dt><dd><p>5 - undocumented</p></dd><dt><span class="term">UINT32</span></dt><dd><p>domain RID </p></dd><dt><span class="term">UINT32</span></dt><dd><p>0 - domain index out of above reference domains</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2861045"></a>LOG_INFO (server, account, client structure)</h4></div></div><p><span class="emphasis"><em>Note: logon server name starts with two '\' characters and is upper case.</em></span></p><p><span class="emphasis"><em>Note: account name is the logon client name from the LSA Request Challenge, with a $ on the end of it, in upper case.</em></span></p><div class="variablelist"><dl><dt><span class="term">VOID*</span></dt><dd><p>undocumented buffer pointer</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>logon server unicode string</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>account name unicode string</p></dd><dt><span class="term">UINT16</span></dt><dd><p>sec_chan - security channel type</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>logon client machine unicode string</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2861145"></a>CLNT_SRV (server, client names structure)</h4></div></div><p><span class="emphasis"><em>Note: logon server name starts with two '\' characters and is upper case.</em></span></p><div class="variablelist"><dl><dt><span class="term">VOID*</span></dt><dd><p>undocumented buffer pointer</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>logon server unicode string</p></dd><dt><span class="term">VOID*</span></dt><dd><p>undocumented buffer pointer</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>logon client machine unicode string</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2861223"></a>CREDS (credentials + time stamp)</h4></div></div><div class="variablelist"><dl><dt><span class="term">char[8]</span></dt><dd><p>credentials</p></dd><dt><span class="term">UTIME</span></dt><dd><p>time stamp</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2861264"></a>CLNT_INFO2 (server, client structure, client credentials)</h4></div></div><p><span class="emphasis"><em>Note: whenever this structure appears in a request, you must take a copy of the client-calculated credentials received, because they will beused in subsequent credential checks. the presumed intention is to
- maintain an authenticated request/response trail.</em></span></p><div class="variablelist"><dl><dt><span class="term">CLNT_SRV</span></dt><dd><p>client and server names</p></dd><dt><span class="term">UINT8[]</span></dt><dd><p>???? padding, for 4-byte alignment with SMB header.</p></dd><dt><span class="term">VOID*</span></dt><dd><p>pointer to client credentials.</p></dd><dt><span class="term">CREDS</span></dt><dd><p>client-calculated credentials + client time</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2861347"></a>CLNT_INFO (server, account, client structure, client credentials)</h4></div></div><p><span class="emphasis"><em>Note: whenever this structure appears in a request, you must take a copy of the client-calculated credentials received, because they will be used in subsequent credential checks. the presumed intention is to maintain an authenticated request/response trail.</em></span></p><div class="variablelist"><dl><dt><span class="term">LOG_INFO</span></dt><dd><p>logon account info</p></dd><dt><span class="term">CREDS</span></dt><dd><p>client-calculated credentials + client time</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2861400"></a>ID_INFO_1 (id info structure, auth level 1)</h4></div></div><div class="variablelist"><dl><dt><span class="term">VOID*</span></dt><dd><p>ptr_id_info_1</p></dd><dt><span class="term">UNIHDR</span></dt><dd><p>domain name unicode header</p></dd><dt><span class="term">UINT32</span></dt><dd><p>param control</p></dd><dt><span class="term">UINT64</span></dt><dd><p>logon ID</p></dd><dt><span class="term">UNIHDR</span></dt><dd><p>user name unicode header</p></dd><dt><span class="term">UNIHDR</span></dt><dd><p>workgroup name unicode header</p></dd><dt><span class="term">char[16]</span></dt><dd><p>arc4 LM OWF Password</p></dd><dt><span class="term">char[16]</span></dt><dd><p>arc4 NT OWF Password</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>domain name unicode string</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>user name unicode string</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>workstation name unicode string</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2861570"></a>SAM_INFO (sam logon/logoff id info structure)</h4></div></div><p><span class="emphasis"><em>Note: presumably, the return credentials is supposedly for the server to verify that the credential chain hasn't been compromised.</em></span></p><div class="variablelist"><dl><dt><span class="term">CLNT_INFO2</span></dt><dd><p>client identification/authentication info</p></dd><dt><span class="term">VOID*</span></dt><dd><p>pointer to return credentials.</p></dd><dt><span class="term">CRED</span></dt><dd><p>return credentials - ignored.</p></dd><dt><span class="term">UINT16</span></dt><dd><p>logon level</p></dd><dt><span class="term">UINT16</span></dt><dd><p>switch value</p></dd></dl></div><pre class="programlisting">
- switch (switch_value)
+appears a third time after the last sub-structure.</P
+></LI
+></OL
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN717"
+></A
+>9.2.2. Enumerations</H3
+><DIV
+CLASS="SECT3"
+><H4
+CLASS="SECT3"
+><A
+NAME="AEN719"
+></A
+>9.2.2.1. MSRPC Header type</H4
+><P
+>command number in the msrpc packet header</P
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>MSRPC_Request:</DT
+><DD
+><P
+>0x00</P
+></DD
+><DT
+>MSRPC_Response:</DT
+><DD
+><P
+>0x02</P
+></DD
+><DT
+>MSRPC_Bind:</DT
+><DD
+><P
+>0x0B</P
+></DD
+><DT
+>MSRPC_BindAck:</DT
+><DD
+><P
+>0x0C</P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN739"
+></A
+>9.2.2.2. MSRPC Packet info</H4
+><P
+>The meaning of these flags is undocumented</P
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>FirstFrag:</DT
+><DD
+><P
+>0x01 </P
+></DD
+><DT
+>LastFrag:</DT
+><DD
+><P
+>0x02 </P
+></DD
+><DT
+>NotaFrag:</DT
+><DD
+><P
+>0x04 </P
+></DD
+><DT
+>RecRespond:</DT
+><DD
+><P
+>0x08 </P
+></DD
+><DT
+>NoMultiplex:</DT
+><DD
+><P
+>0x10 </P
+></DD
+><DT
+>NotForIdemp:</DT
+><DD
+><P
+>0x20 </P
+></DD
+><DT
+>NotforBcast:</DT
+><DD
+><P
+>0x40 </P
+></DD
+><DT
+>NoUuid:</DT
+><DD
+><P
+>0x80 </P
+></DD
+></DL
+></DIV
+></DIV
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN775"
+></A
+>9.2.3. Structures</H3
+><DIV
+CLASS="SECT3"
+><H4
+CLASS="SECT3"
+><A
+NAME="AEN777"
+></A
+>9.2.3.1. VOID *</H4
+><P
+>sizeof VOID* is 32 bits.</P
+></DIV
+><DIV
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN780"
+></A
+>9.2.3.2. char</H4
+><P
+>sizeof char is 8 bits.</P
+></DIV
+><DIV
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN783"
+></A
+>9.2.3.3. UTIME</H4
+><P
+>UTIME is 32 bits, indicating time in seconds since 01jan1970. documented in cifs6.txt (section 3.5 page, page 30).</P
+></DIV
+><DIV
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN786"
+></A
+>9.2.3.4. NTTIME</H4
+><P
+>NTTIME is 64 bits. documented in cifs6.txt (section 3.5 page, page 30).</P
+></DIV
+><DIV
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN789"
+></A
+>9.2.3.5. DOM_SID (domain SID structure)</H4
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>UINT32</DT
+><DD
+><P
+>num of sub-authorities in domain SID</P
+></DD
+><DT
+>UINT8</DT
+><DD
+><P
+>SID revision number</P
+></DD
+><DT
+>UINT8</DT
+><DD
+><P
+>num of sub-authorities in domain SID</P
+></DD
+><DT
+>UINT8[6]</DT
+><DD
+><P
+>6 bytes for domain SID - Identifier Authority.</P
+></DD
+><DT
+>UINT16[n_subauths]</DT
+><DD
+><P
+>domain SID sub-authorities</P
+></DD
+></DL
+></DIV
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Note: the domain SID is documented elsewhere.</I
+></SPAN
+></P
+></DIV
+><DIV
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN814"
+></A
+>9.2.3.6. STR (string)</H4
+><P
+>STR (string) is a char[] : a null-terminated string of ascii characters.</P
+></DIV
+><DIV
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN817"
+></A
+>9.2.3.7. UNIHDR (unicode string header)</H4
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>UINT16</DT
+><DD
+><P
+>length of unicode string</P
+></DD
+><DT
+>UINT16</DT
+><DD
+><P
+>max length of unicode string</P
+></DD
+><DT
+>UINT32</DT
+><DD
+><P
+>4 - undocumented.</P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN832"
+></A
+>9.2.3.8. UNIHDR2 (unicode string header plus buffer pointer)</H4
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>UNIHDR</DT
+><DD
+><P
+>unicode string header</P
+></DD
+><DT
+>VOID*</DT
+><DD
+><P
+>undocumented buffer pointer</P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN843"
+></A
+>9.2.3.9. UNISTR (unicode string)</H4
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>UINT16[]</DT
+><DD
+><P
+>null-terminated string of unicode characters.</P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN850"
+></A
+>9.2.3.10. NAME (length-indicated unicode string)</H4
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>UINT32</DT
+><DD
+><P
+>length of unicode string</P
+></DD
+><DT
+>UINT16[]</DT
+><DD
+><P
+>null-terminated string of unicode characters.</P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN861"
+></A
+>9.2.3.11. UNISTR2 (aligned unicode string)</H4
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>UINT8[]</DT
+><DD
+><P
+>padding to get unicode string 4-byte aligned with the start of the SMB header.</P
+></DD
+><DT
+>UINT32</DT
+><DD
+><P
+>max length of unicode string</P
+></DD
+><DT
+>UINT32</DT
+><DD
+><P
+>0 - undocumented</P
+></DD
+><DT
+>UINT32</DT
+><DD
+><P
+>length of unicode string</P
+></DD
+><DT
+>UINT16[]</DT
+><DD
+><P
+>string of uncode characters</P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN884"
+></A
+>9.2.3.12. OBJ_ATTR (object attributes)</H4
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>UINT32</DT
+><DD
+><P
+>0x18 - length (in bytes) including the length field.</P
+></DD
+><DT
+>VOID*</DT
+><DD
+><P
+>0 - root directory (pointer)</P
+></DD
+><DT
+>VOID*</DT
+><DD
+><P
+>0 - object name (pointer)</P
+></DD
+><DT
+>UINT32</DT
+><DD
+><P
+>0 - attributes (undocumented)</P
+></DD
+><DT
+>VOID*</DT
+><DD
+><P
+>0 - security descriptior (pointer)</P
+></DD
+><DT
+>UINT32</DT
+><DD
+><P
+>0 - security quality of service</P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN911"
+></A
+>9.2.3.13. POL_HND (LSA policy handle)</H4
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>char[20]</DT
+><DD
+><P
+>policy handle</P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN918"
+></A
+>9.2.3.14. DOM_SID2 (domain SID structure, SIDS stored in unicode)</H4
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>UINT32</DT
+><DD
+><P
+>5 - SID type</P
+></DD
+><DT
+>UINT32</DT
+><DD
+><P
+>0 - undocumented</P
+></DD
+><DT
+>UNIHDR2</DT
+><DD
+><P
+>domain SID unicode string header</P
+></DD
+><DT
+>UNISTR</DT
+><DD
+><P
+>domain SID unicode string</P
+></DD
+></DL
+></DIV
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Note: there is a conflict between the unicode string header and the unicode string itself as to which to use to indicate string length. this will need to be resolved.</I
+></SPAN
+></P
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Note: the SID type indicates, for example, an alias; a well-known group etc. this is documented somewhere.</I
+></SPAN
+></P
+></DIV
+><DIV
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN941"
+></A
+>9.2.3.15. DOM_RID (domain RID structure)</H4
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>UINT32</DT
+><DD
+><P
+>5 - well-known SID. 1 - user SID (see ShowACLs)</P
+></DD
+><DT
+>UINT32</DT
+><DD
+><P
+>5 - undocumented</P
+></DD
+><DT
+>UINT32</DT
+><DD
+><P
+>domain RID </P
+></DD
+><DT
+>UINT32</DT
+><DD
+><P
+>0 - domain index out of above reference domains</P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN960"
+></A
+>9.2.3.16. LOG_INFO (server, account, client structure)</H4
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Note: logon server name starts with two '\' characters and is upper case.</I
+></SPAN
+></P
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Note: account name is the logon client name from the LSA Request Challenge, with a $ on the end of it, in upper case.</I
+></SPAN
+></P
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>VOID*</DT
+><DD
+><P
+>undocumented buffer pointer</P
+></DD
+><DT
+>UNISTR2</DT
+><DD
+><P
+>logon server unicode string</P
+></DD
+><DT
+>UNISTR2</DT
+><DD
+><P
+>account name unicode string</P
+></DD
+><DT
+>UINT16</DT
+><DD
+><P
+>sec_chan - security channel type</P
+></DD
+><DT
+>UNISTR2</DT
+><DD
+><P
+>logon client machine unicode string</P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN987"
+></A
+>9.2.3.17. CLNT_SRV (server, client names structure)</H4
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Note: logon server name starts with two '\' characters and is upper case.</I
+></SPAN
+></P
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>VOID*</DT
+><DD
+><P
+>undocumented buffer pointer</P
+></DD
+><DT
+>UNISTR2</DT
+><DD
+><P
+>logon server unicode string</P
+></DD
+><DT
+>VOID*</DT
+><DD
+><P
+>undocumented buffer pointer</P
+></DD
+><DT
+>UNISTR2</DT
+><DD
+><P
+>logon client machine unicode string</P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN1008"
+></A
+>9.2.3.18. CREDS (credentials + time stamp)</H4
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>char[8]</DT
+><DD
+><P
+>credentials</P
+></DD
+><DT
+>UTIME</DT
+><DD
+><P
+>time stamp</P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN1019"
+></A
+>9.2.3.19. CLNT_INFO2 (server, client structure, client credentials)</H4
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Note: whenever this structure appears in a request, you must take a copy of the client-calculated credentials received, because they will beused in subsequent credential checks. the presumed intention is to
+ maintain an authenticated request/response trail.</I
+></SPAN
+></P
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>CLNT_SRV</DT
+><DD
+><P
+>client and server names</P
+></DD
+><DT
+>UINT8[]</DT
+><DD
+><P
+>???? padding, for 4-byte alignment with SMB header.</P
+></DD
+><DT
+>VOID*</DT
+><DD
+><P
+>pointer to client credentials.</P
+></DD
+><DT
+>CREDS</DT
+><DD
+><P
+>client-calculated credentials + client time</P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN1040"
+></A
+>9.2.3.20. CLNT_INFO (server, account, client structure, client credentials)</H4
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Note: whenever this structure appears in a request, you must take a copy of the client-calculated credentials received, because they will be used in subsequent credential checks. the presumed intention is to maintain an authenticated request/response trail.</I
+></SPAN
+></P
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>LOG_INFO</DT
+><DD
+><P
+>logon account info</P
+></DD
+><DT
+>CREDS</DT
+><DD
+><P
+>client-calculated credentials + client time</P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN1053"
+></A
+>9.2.3.21. ID_INFO_1 (id info structure, auth level 1)</H4
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>VOID*</DT
+><DD
+><P
+>ptr_id_info_1</P
+></DD
+><DT
+>UNIHDR</DT
+><DD
+><P
+>domain name unicode header</P
+></DD
+><DT
+>UINT32</DT
+><DD
+><P
+>param control</P
+></DD
+><DT
+>UINT64</DT
+><DD
+><P
+>logon ID</P
+></DD
+><DT
+>UNIHDR</DT
+><DD
+><P
+>user name unicode header</P
+></DD
+><DT
+>UNIHDR</DT
+><DD
+><P
+>workgroup name unicode header</P
+></DD
+><DT
+>char[16]</DT
+><DD
+><P
+>arc4 LM OWF Password</P
+></DD
+><DT
+>char[16]</DT
+><DD
+><P
+>arc4 NT OWF Password</P
+></DD
+><DT
+>UNISTR2</DT
+><DD
+><P
+>domain name unicode string</P
+></DD
+><DT
+>UNISTR2</DT
+><DD
+><P
+>user name unicode string</P
+></DD
+><DT
+>UNISTR2</DT
+><DD
+><P
+>workstation name unicode string</P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN1100"
+></A
+>9.2.3.22. SAM_INFO (sam logon/logoff id info structure)</H4
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Note: presumably, the return credentials is supposedly for the server to verify that the credential chain hasn't been compromised.</I
+></SPAN
+></P
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>CLNT_INFO2</DT
+><DD
+><P
+>client identification/authentication info</P
+></DD
+><DT
+>VOID*</DT
+><DD
+><P
+>pointer to return credentials.</P
+></DD
+><DT
+>CRED</DT
+><DD
+><P
+>return credentials - ignored.</P
+></DD
+><DT
+>UINT16</DT
+><DD
+><P
+>logon level</P
+></DD
+><DT
+>UINT16</DT
+><DD
+><P
+>switch value</P
+></DD
+></DL
+></DIV
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+> switch (switch_value)
case 1:
{
ID_INFO_1 id_info_1;
- }
-</pre></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2861675"></a>GID (group id info)</h4></div></div><div class="variablelist"><dl><dt><span class="term">UINT32</span></dt><dd><p>group id</p></dd><dt><span class="term">UINT32</span></dt><dd><p>user attributes (only used by NT 3.1 and 3.51)</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2861713"></a>DOM_REF (domain reference info)</h4></div></div><div class="variablelist"><dl><dt><span class="term">VOID*</span></dt><dd><p>undocumented buffer pointer.</p></dd><dt><span class="term">UINT32</span></dt><dd><p>num referenced domains?</p></dd><dt><span class="term">VOID*</span></dt><dd><p>undocumented domain name buffer pointer.</p></dd><dt><span class="term">UINT32</span></dt><dd><p>32 - max number of entries</p></dd><dt><span class="term">UINT32</span></dt><dd><p>4 - num referenced domains?</p></dd><dt><span class="term">UNIHDR2</span></dt><dd><p>domain name unicode string header</p></dd><dt><span class="term">UNIHDR2[num_ref_doms-1]</span></dt><dd><p>referenced domain unicode string headers</p></dd><dt><span class="term">UNISTR</span></dt><dd><p>domain name unicode string</p></dd><dt><span class="term">DOM_SID[num_ref_doms]</span></dt><dd><p>referenced domain SIDs</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2861857"></a>DOM_INFO (domain info, levels 3 and 5 are the same))</h4></div></div><div class="variablelist"><dl><dt><span class="term">UINT8[]</span></dt><dd><p>??? padding to get 4-byte alignment with start of SMB header</p></dd><dt><span class="term">UINT16</span></dt><dd><p>domain name string length * 2</p></dd><dt><span class="term">UINT16</span></dt><dd><p>domain name string length * 2</p></dd><dt><span class="term">VOID*</span></dt><dd><p>undocumented domain name string buffer pointer</p></dd><dt><span class="term">VOID*</span></dt><dd><p>undocumented domain SID string buffer pointer</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>domain name (unicode string)</p></dd><dt><span class="term">DOM_SID</span></dt><dd><p>domain SID</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2861970"></a>USER_INFO (user logon info)</h4></div></div><p><span class="emphasis"><em>Note: it would be nice to know what the 16 byte user session key is for.</em></span></p><div class="variablelist"><dl><dt><span class="term">NTTIME</span></dt><dd><p>logon time</p></dd><dt><span class="term">NTTIME</span></dt><dd><p>logoff time</p></dd><dt><span class="term">NTTIME</span></dt><dd><p>kickoff time</p></dd><dt><span class="term">NTTIME</span></dt><dd><p>password last set time</p></dd><dt><span class="term">NTTIME</span></dt><dd><p>password can change time</p></dd><dt><span class="term">NTTIME</span></dt><dd><p>password must change time</p></dd><dt><span class="term">UNIHDR</span></dt><dd><p>username unicode string header</p></dd><dt><span class="term">UNIHDR</span></dt><dd><p>user's full name unicode string header</p></dd><dt><span class="term">UNIHDR</span></dt><dd><p>logon script unicode string header</p></dd><dt><span class="term">UNIHDR</span></dt><dd><p>profile path unicode string header</p></dd><dt><span class="term">UNIHDR</span></dt><dd><p>home directory unicode string header</p></dd><dt><span class="term">UNIHDR</span></dt><dd><p>home directory drive unicode string header</p></dd><dt><span class="term">UINT16</span></dt><dd><p>logon count</p></dd><dt><span class="term">UINT16</span></dt><dd><p>bad password count</p></dd><dt><span class="term">UINT32</span></dt><dd><p>User ID</p></dd><dt><span class="term">UINT32</span></dt><dd><p>Group ID</p></dd><dt><span class="term">UINT32</span></dt><dd><p>num groups</p></dd><dt><span class="term">VOID*</span></dt><dd><p>undocumented buffer pointer to groups.</p></dd><dt><span class="term">UINT32</span></dt><dd><p>user flags</p></dd><dt><span class="term">char[16]</span></dt><dd><p>user session key</p></dd><dt><span class="term">UNIHDR</span></dt><dd><p>logon server unicode string header</p></dd><dt><span class="term">UNIHDR</span></dt><dd><p>logon domain unicode string header</p></dd><dt><span class="term">VOID*</span></dt><dd><p>undocumented logon domain id pointer</p></dd><dt><span class="term">char[40]</span></dt><dd><p>40 undocumented padding bytes. future expansion?</p></dd><dt><span class="term">UINT32</span></dt><dd><p>0 - num_other_sids?</p></dd><dt><span class="term">VOID*</span></dt><dd><p>NULL - undocumented pointer to other domain SIDs.</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>username unicode string</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>user's full name unicode string</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>logon script unicode string</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>profile path unicode string</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>home directory unicode string</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>home directory drive unicode string</p></dd><dt><span class="term">UINT32</span></dt><dd><p>num groups</p></dd><dt><span class="term">GID[num_groups]</span></dt><dd><p>group info</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>logon server unicode string</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>logon domain unicode string</p></dd><dt><span class="term">DOM_SID</span></dt><dd><p>domain SID</p></dd><dt><span class="term">DOM_SID[num_sids]</span></dt><dd><p>other domain SIDs?</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2862534"></a>SH_INFO_1_PTR (pointers to level 1 share info strings)</h4></div></div><p><span class="emphasis"><em>Note: see cifsrap2.txt section5, page 10.</em></span></p><table class="simplelist" border="0" summary="Simple list"><tr><td>0 for shi1_type indicates a Disk.</td></tr><tr><td>1 for shi1_type indicates a Print Queue.</td></tr><tr><td>2 for shi1_type indicates a Device.</td></tr><tr><td>3 for shi1_type indicates an IPC pipe.</td></tr><tr><td>0x8000 0000 (top bit set in shi1_type) indicates a hidden share.</td></tr></table><div class="variablelist"><dl><dt><span class="term">VOID*</span></dt><dd><p>shi1_netname - pointer to net name</p></dd><dt><span class="term">UINT32</span></dt><dd><p>shi1_type - type of share. 0 - undocumented.</p></dd><dt><span class="term">VOID*</span></dt><dd><p>shi1_remark - pointer to comment.</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2862629"></a>SH_INFO_1_STR (level 1 share info strings)</h4></div></div><div class="variablelist"><dl><dt><span class="term">UNISTR2</span></dt><dd><p>shi1_netname - unicode string of net name</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>shi1_remark - unicode string of comment.</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2862671"></a>SHARE_INFO_1_CTR</h4></div></div><p>share container with 0 entries:</p><div class="variablelist"><dl><dt><span class="term">UINT32</span></dt><dd><p>0 - EntriesRead</p></dd><dt><span class="term">UINT32</span></dt><dd><p>0 - Buffer</p></dd></dl></div><p>share container with &gt; 0 entries:</p><div class="variablelist"><dl><dt><span class="term">UINT32</span></dt><dd><p>EntriesRead</p></dd><dt><span class="term">UINT32</span></dt><dd><p>non-zero - Buffer</p></dd><dt><span class="term">UINT32</span></dt><dd><p>EntriesRead</p></dd><dt><span class="term">SH_INFO_1_PTR[EntriesRead]</span></dt><dd><p>share entry pointers</p></dd><dt><span class="term">SH_INFO_1_STR[EntriesRead]</span></dt><dd><p>share entry strings</p></dd><dt><span class="term">UINT8[]</span></dt><dd><p>padding to get unicode string 4-byte aligned with start of the SMB header.</p></dd><dt><span class="term">UINT32</span></dt><dd><p>EntriesRead</p></dd><dt><span class="term">UINT32</span></dt><dd><p>0 - padding</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2862841"></a>SERVER_INFO_101</h4></div></div><p><span class="emphasis"><em>Note: see cifs6.txt section 6.4 - the fields described therein will be of assistance here. for example, the type listed below is the same as fServerType, which is described in 6.4.1. </em></span></p><div class="variablelist"><dl><dt><span class="term">SV_TYPE_WORKSTATION</span></dt><dd><p>0x00000001 All workstations</p></dd><dt><span class="term">SV_TYPE_SERVER</span></dt><dd><p>0x00000002 All servers</p></dd><dt><span class="term">SV_TYPE_SQLSERVER</span></dt><dd><p>0x00000004 Any server running with SQL server</p></dd><dt><span class="term">SV_TYPE_DOMAIN_CTRL</span></dt><dd><p>0x00000008 Primary domain controller</p></dd><dt><span class="term">SV_TYPE_DOMAIN_BAKCTRL</span></dt><dd><p>0x00000010 Backup domain controller</p></dd><dt><span class="term">SV_TYPE_TIME_SOURCE</span></dt><dd><p>0x00000020 Server running the timesource service</p></dd><dt><span class="term">SV_TYPE_AFP</span></dt><dd><p>0x00000040 Apple File Protocol servers</p></dd><dt><span class="term">SV_TYPE_NOVELL</span></dt><dd><p>0x00000080 Novell servers</p></dd><dt><span class="term">SV_TYPE_DOMAIN_MEMBER</span></dt><dd><p>0x00000100 Domain Member</p></dd><dt><span class="term">SV_TYPE_PRINTQ_SERVER</span></dt><dd><p>0x00000200 Server sharing print queue</p></dd><dt><span class="term">SV_TYPE_DIALIN_SERVER</span></dt><dd><p>0x00000400 Server running dialin service.</p></dd><dt><span class="term">SV_TYPE_XENIX_SERVER</span></dt><dd><p>0x00000800 Xenix server</p></dd><dt><span class="term">SV_TYPE_NT</span></dt><dd><p>0x00001000 NT server</p></dd><dt><span class="term">SV_TYPE_WFW</span></dt><dd><p>0x00002000 Server running Windows for </p></dd><dt><span class="term">SV_TYPE_SERVER_NT</span></dt><dd><p>0x00008000 Windows NT non DC server</p></dd><dt><span class="term">SV_TYPE_POTENTIAL_BROWSER</span></dt><dd><p>0x00010000 Server that can run the browser service</p></dd><dt><span class="term">SV_TYPE_BACKUP_BROWSER</span></dt><dd><p>0x00020000 Backup browser server</p></dd><dt><span class="term">SV_TYPE_MASTER_BROWSER</span></dt><dd><p>0x00040000 Master browser server</p></dd><dt><span class="term">SV_TYPE_DOMAIN_MASTER</span></dt><dd><p>0x00080000 Domain Master Browser server</p></dd><dt><span class="term">SV_TYPE_LOCAL_LIST_ONLY</span></dt><dd><p>0x40000000 Enumerate only entries marked &quot;local&quot;</p></dd><dt><span class="term">SV_TYPE_DOMAIN_ENUM</span></dt><dd><p>0x80000000 Enumerate Domains. The pszServer and pszDomain parameters must be NULL.</p></dd></dl></div><div class="variablelist"><dl><dt><span class="term">UINT32</span></dt><dd><p>500 - platform_id</p></dd><dt><span class="term">VOID*</span></dt><dd><p>pointer to name</p></dd><dt><span class="term">UINT32</span></dt><dd><p>5 - major version</p></dd><dt><span class="term">UINT32</span></dt><dd><p>4 - minor version</p></dd><dt><span class="term">UINT32</span></dt><dd><p>type (SV_TYPE_... bit field)</p></dd><dt><span class="term">VOID*</span></dt><dd><p>pointer to comment</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>sv101_name - unicode string of server name</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>sv_101_comment - unicode string of server comment.</p></dd><dt><span class="term">UINT8[]</span></dt><dd><p>padding to get unicode string 4-byte aligned with start of the SMB header.</p></dd></dl></div></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2863307"></a>MSRPC over Transact Named Pipe</h2></div></div><p>For details on the SMB Transact Named Pipe, see cifs6.txt</p><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2863320"></a>MSRPC Pipes</h3></div></div><p>
-The MSRPC is conducted over an SMB Transact Pipe with a name of
-<tt>\PIPE\</tt>. You must first obtain a 16 bit file handle, by
-sending a SMBopenX with the pipe name <tt>\PIPE\srvsvc</tt> for
+ }</PRE
+></P
+></DIV
+><DIV
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN1127"
+></A
+>9.2.3.23. GID (group id info)</H4
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>UINT32</DT
+><DD
+><P
+>group id</P
+></DD
+><DT
+>UINT32</DT
+><DD
+><P
+>user attributes (only used by NT 3.1 and 3.51)</P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN1138"
+></A
+>9.2.3.24. DOM_REF (domain reference info)</H4
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>VOID*</DT
+><DD
+><P
+>undocumented buffer pointer.</P
+></DD
+><DT
+>UINT32</DT
+><DD
+><P
+>num referenced domains?</P
+></DD
+><DT
+>VOID*</DT
+><DD
+><P
+>undocumented domain name buffer pointer.</P
+></DD
+><DT
+>UINT32</DT
+><DD
+><P
+>32 - max number of entries</P
+></DD
+><DT
+>UINT32</DT
+><DD
+><P
+>4 - num referenced domains?</P
+></DD
+><DT
+>UNIHDR2</DT
+><DD
+><P
+>domain name unicode string header</P
+></DD
+><DT
+>UNIHDR2[num_ref_doms-1]</DT
+><DD
+><P
+>referenced domain unicode string headers</P
+></DD
+><DT
+>UNISTR</DT
+><DD
+><P
+>domain name unicode string</P
+></DD
+><DT
+>DOM_SID[num_ref_doms]</DT
+><DD
+><P
+>referenced domain SIDs</P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN1177"
+></A
+>9.2.3.25. DOM_INFO (domain info, levels 3 and 5 are the same))</H4
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>UINT8[]</DT
+><DD
+><P
+>??? padding to get 4-byte alignment with start of SMB header</P
+></DD
+><DT
+>UINT16</DT
+><DD
+><P
+>domain name string length * 2</P
+></DD
+><DT
+>UINT16</DT
+><DD
+><P
+>domain name string length * 2</P
+></DD
+><DT
+>VOID*</DT
+><DD
+><P
+>undocumented domain name string buffer pointer</P
+></DD
+><DT
+>VOID*</DT
+><DD
+><P
+>undocumented domain SID string buffer pointer</P
+></DD
+><DT
+>UNISTR2</DT
+><DD
+><P
+>domain name (unicode string)</P
+></DD
+><DT
+>DOM_SID</DT
+><DD
+><P
+>domain SID</P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN1208"
+></A
+>9.2.3.26. USER_INFO (user logon info)</H4
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Note: it would be nice to know what the 16 byte user session key is for.</I
+></SPAN
+></P
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>NTTIME</DT
+><DD
+><P
+>logon time</P
+></DD
+><DT
+>NTTIME</DT
+><DD
+><P
+>logoff time</P
+></DD
+><DT
+>NTTIME</DT
+><DD
+><P
+>kickoff time</P
+></DD
+><DT
+>NTTIME</DT
+><DD
+><P
+>password last set time</P
+></DD
+><DT
+>NTTIME</DT
+><DD
+><P
+>password can change time</P
+></DD
+><DT
+>NTTIME</DT
+><DD
+><P
+>password must change time</P
+></DD
+><DT
+>UNIHDR</DT
+><DD
+><P
+>username unicode string header</P
+></DD
+><DT
+>UNIHDR</DT
+><DD
+><P
+>user's full name unicode string header</P
+></DD
+><DT
+>UNIHDR</DT
+><DD
+><P
+>logon script unicode string header</P
+></DD
+><DT
+>UNIHDR</DT
+><DD
+><P
+>profile path unicode string header</P
+></DD
+><DT
+>UNIHDR</DT
+><DD
+><P
+>home directory unicode string header</P
+></DD
+><DT
+>UNIHDR</DT
+><DD
+><P
+>home directory drive unicode string header</P
+></DD
+><DT
+>UINT16</DT
+><DD
+><P
+>logon count</P
+></DD
+><DT
+>UINT16</DT
+><DD
+><P
+>bad password count</P
+></DD
+><DT
+>UINT32</DT
+><DD
+><P
+>User ID</P
+></DD
+><DT
+>UINT32</DT
+><DD
+><P
+>Group ID</P
+></DD
+><DT
+>UINT32</DT
+><DD
+><P
+>num groups</P
+></DD
+><DT
+>VOID*</DT
+><DD
+><P
+>undocumented buffer pointer to groups.</P
+></DD
+><DT
+>UINT32</DT
+><DD
+><P
+>user flags</P
+></DD
+><DT
+>char[16]</DT
+><DD
+><P
+>user session key</P
+></DD
+><DT
+>UNIHDR</DT
+><DD
+><P
+>logon server unicode string header</P
+></DD
+><DT
+>UNIHDR</DT
+><DD
+><P
+>logon domain unicode string header</P
+></DD
+><DT
+>VOID*</DT
+><DD
+><P
+>undocumented logon domain id pointer</P
+></DD
+><DT
+>char[40]</DT
+><DD
+><P
+>40 undocumented padding bytes. future expansion?</P
+></DD
+><DT
+>UINT32</DT
+><DD
+><P
+>0 - num_other_sids?</P
+></DD
+><DT
+>VOID*</DT
+><DD
+><P
+>NULL - undocumented pointer to other domain SIDs.</P
+></DD
+><DT
+>UNISTR2</DT
+><DD
+><P
+>username unicode string</P
+></DD
+><DT
+>UNISTR2</DT
+><DD
+><P
+>user's full name unicode string</P
+></DD
+><DT
+>UNISTR2</DT
+><DD
+><P
+>logon script unicode string</P
+></DD
+><DT
+>UNISTR2</DT
+><DD
+><P
+>profile path unicode string</P
+></DD
+><DT
+>UNISTR2</DT
+><DD
+><P
+>home directory unicode string</P
+></DD
+><DT
+>UNISTR2</DT
+><DD
+><P
+>home directory drive unicode string</P
+></DD
+><DT
+>UINT32</DT
+><DD
+><P
+>num groups</P
+></DD
+><DT
+>GID[num_groups]</DT
+><DD
+><P
+>group info</P
+></DD
+><DT
+>UNISTR2</DT
+><DD
+><P
+>logon server unicode string</P
+></DD
+><DT
+>UNISTR2</DT
+><DD
+><P
+>logon domain unicode string</P
+></DD
+><DT
+>DOM_SID</DT
+><DD
+><P
+>domain SID</P
+></DD
+><DT
+>DOM_SID[num_sids]</DT
+><DD
+><P
+>other domain SIDs?</P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN1365"
+></A
+>9.2.3.27. SH_INFO_1_PTR (pointers to level 1 share info strings)</H4
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Note: see cifsrap2.txt section5, page 10.</I
+></SPAN
+></P
+><P
+></P
+><TABLE
+BORDER="0"
+><TBODY
+><TR
+><TD
+>0 for shi1_type indicates a Disk.</TD
+></TR
+><TR
+><TD
+>1 for shi1_type indicates a Print Queue.</TD
+></TR
+><TR
+><TD
+>2 for shi1_type indicates a Device.</TD
+></TR
+><TR
+><TD
+>3 for shi1_type indicates an IPC pipe.</TD
+></TR
+><TR
+><TD
+>0x8000 0000 (top bit set in shi1_type) indicates a hidden share.</TD
+></TR
+></TBODY
+></TABLE
+><P
+></P
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>VOID*</DT
+><DD
+><P
+>shi1_netname - pointer to net name</P
+></DD
+><DT
+>UINT32</DT
+><DD
+><P
+>shi1_type - type of share. 0 - undocumented.</P
+></DD
+><DT
+>VOID*</DT
+><DD
+><P
+>shi1_remark - pointer to comment.</P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN1388"
+></A
+>9.2.3.28. SH_INFO_1_STR (level 1 share info strings)</H4
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>UNISTR2</DT
+><DD
+><P
+>shi1_netname - unicode string of net name</P
+></DD
+><DT
+>UNISTR2</DT
+><DD
+><P
+>shi1_remark - unicode string of comment.</P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN1399"
+></A
+>9.2.3.29. SHARE_INFO_1_CTR</H4
+><P
+>share container with 0 entries:</P
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>UINT32</DT
+><DD
+><P
+>0 - EntriesRead</P
+></DD
+><DT
+>UINT32</DT
+><DD
+><P
+>0 - Buffer</P
+></DD
+></DL
+></DIV
+><P
+>share container with &#62; 0 entries:</P
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>UINT32</DT
+><DD
+><P
+>EntriesRead</P
+></DD
+><DT
+>UINT32</DT
+><DD
+><P
+>non-zero - Buffer</P
+></DD
+><DT
+>UINT32</DT
+><DD
+><P
+>EntriesRead</P
+></DD
+><DT
+>SH_INFO_1_PTR[EntriesRead]</DT
+><DD
+><P
+>share entry pointers</P
+></DD
+><DT
+>SH_INFO_1_STR[EntriesRead]</DT
+><DD
+><P
+>share entry strings</P
+></DD
+><DT
+>UINT8[]</DT
+><DD
+><P
+>padding to get unicode string 4-byte aligned with start of the SMB header.</P
+></DD
+><DT
+>UINT32</DT
+><DD
+><P
+>EntriesRead</P
+></DD
+><DT
+>UINT32</DT
+><DD
+><P
+>0 - padding</P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN1445"
+></A
+>9.2.3.30. SERVER_INFO_101</H4
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Note: see cifs6.txt section 6.4 - the fields described therein will be of assistance here. for example, the type listed below is the same as fServerType, which is described in 6.4.1. </I
+></SPAN
+></P
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>SV_TYPE_WORKSTATION</DT
+><DD
+><P
+>0x00000001 All workstations</P
+></DD
+><DT
+>SV_TYPE_SERVER</DT
+><DD
+><P
+>0x00000002 All servers</P
+></DD
+><DT
+>SV_TYPE_SQLSERVER</DT
+><DD
+><P
+>0x00000004 Any server running with SQL server</P
+></DD
+><DT
+>SV_TYPE_DOMAIN_CTRL</DT
+><DD
+><P
+>0x00000008 Primary domain controller</P
+></DD
+><DT
+>SV_TYPE_DOMAIN_BAKCTRL</DT
+><DD
+><P
+>0x00000010 Backup domain controller</P
+></DD
+><DT
+>SV_TYPE_TIME_SOURCE</DT
+><DD
+><P
+>0x00000020 Server running the timesource service</P
+></DD
+><DT
+>SV_TYPE_AFP</DT
+><DD
+><P
+>0x00000040 Apple File Protocol servers</P
+></DD
+><DT
+>SV_TYPE_NOVELL</DT
+><DD
+><P
+>0x00000080 Novell servers</P
+></DD
+><DT
+>SV_TYPE_DOMAIN_MEMBER</DT
+><DD
+><P
+>0x00000100 Domain Member</P
+></DD
+><DT
+>SV_TYPE_PRINTQ_SERVER</DT
+><DD
+><P
+>0x00000200 Server sharing print queue</P
+></DD
+><DT
+>SV_TYPE_DIALIN_SERVER</DT
+><DD
+><P
+>0x00000400 Server running dialin service.</P
+></DD
+><DT
+>SV_TYPE_XENIX_SERVER</DT
+><DD
+><P
+>0x00000800 Xenix server</P
+></DD
+><DT
+>SV_TYPE_NT</DT
+><DD
+><P
+>0x00001000 NT server</P
+></DD
+><DT
+>SV_TYPE_WFW</DT
+><DD
+><P
+>0x00002000 Server running Windows for </P
+></DD
+><DT
+>SV_TYPE_SERVER_NT</DT
+><DD
+><P
+>0x00008000 Windows NT non DC server</P
+></DD
+><DT
+>SV_TYPE_POTENTIAL_BROWSER</DT
+><DD
+><P
+>0x00010000 Server that can run the browser service</P
+></DD
+><DT
+>SV_TYPE_BACKUP_BROWSER</DT
+><DD
+><P
+>0x00020000 Backup browser server</P
+></DD
+><DT
+>SV_TYPE_MASTER_BROWSER</DT
+><DD
+><P
+>0x00040000 Master browser server</P
+></DD
+><DT
+>SV_TYPE_DOMAIN_MASTER</DT
+><DD
+><P
+>0x00080000 Domain Master Browser server</P
+></DD
+><DT
+>SV_TYPE_LOCAL_LIST_ONLY</DT
+><DD
+><P
+>0x40000000 Enumerate only entries marked "local"</P
+></DD
+><DT
+>SV_TYPE_DOMAIN_ENUM</DT
+><DD
+><P
+>0x80000000 Enumerate Domains. The pszServer and pszDomain parameters must be NULL.</P
+></DD
+></DL
+></DIV
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>UINT32</DT
+><DD
+><P
+>500 - platform_id</P
+></DD
+><DT
+>VOID*</DT
+><DD
+><P
+>pointer to name</P
+></DD
+><DT
+>UINT32</DT
+><DD
+><P
+>5 - major version</P
+></DD
+><DT
+>UINT32</DT
+><DD
+><P
+>4 - minor version</P
+></DD
+><DT
+>UINT32</DT
+><DD
+><P
+>type (SV_TYPE_... bit field)</P
+></DD
+><DT
+>VOID*</DT
+><DD
+><P
+>pointer to comment</P
+></DD
+><DT
+>UNISTR2</DT
+><DD
+><P
+>sv101_name - unicode string of server name</P
+></DD
+><DT
+>UNISTR2</DT
+><DD
+><P
+>sv_101_comment - unicode string of server comment.</P
+></DD
+><DT
+>UINT8[]</DT
+><DD
+><P
+>padding to get unicode string 4-byte aligned with start of the SMB header.</P
+></DD
+></DL
+></DIV
+></DIV
+></DIV
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN1571"
+></A
+>9.3. MSRPC over Transact Named Pipe</H2
+><P
+>For details on the SMB Transact Named Pipe, see cifs6.txt</P
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN1574"
+></A
+>9.3.1. MSRPC Pipes</H3
+><P
+>The MSRPC is conducted over an SMB Transact Pipe with a name of
+<TT
+CLASS="FILENAME"
+>\PIPE\</TT
+>. You must first obtain a 16 bit file handle, by
+sending a SMBopenX with the pipe name <TT
+CLASS="FILENAME"
+>\PIPE\srvsvc</TT
+> for
example. You can then perform an SMB Trans,
-and must carry out an SMBclose on the file handle once you are finished.
-</p><p>
-Trans Requests must be sent with two setup UINT16s, no UINT16 params (none
+and must carry out an SMBclose on the file handle once you are finished.</P
+><P
+>Trans Requests must be sent with two setup UINT16s, no UINT16 params (none
known about), and UINT8 data parameters sufficient to contain the MSRPC
header, and MSRPC data. The first UINT16 setup parameter must be either
0x0026 to indicate an RPC, or 0x0001 to indicate Set Named Pipe Handle
state. The second UINT16 parameter must be the file handle for the pipe,
-obtained above.
-</p><p>
-The Data section for an API Command of 0x0026 (RPC pipe) in the Trans
+obtained above.</P
+><P
+>The Data section for an API Command of 0x0026 (RPC pipe) in the Trans
Request is the RPC Header, followed by the RPC Data. The Data section for
an API Command of 0x0001 (Set Named Pipe Handle state) is two bytes. The
-only value seen for these two bytes is 0x00 0x43.
-</p><p>
-MSRPC Responses are sent as response data inside standard SMB Trans
-responses, with the MSRPC Header, MSRPC Data and MSRPC tail.
-</p><p>
-It is suspected that the Trans Requests will need to be at least 2-byte
+only value seen for these two bytes is 0x00 0x43.</P
+><P
+>MSRPC Responses are sent as response data inside standard SMB Trans
+responses, with the MSRPC Header, MSRPC Data and MSRPC tail.</P
+><P
+>It is suspected that the Trans Requests will need to be at least 2-byte
aligned (probably 4-byte). This is standard practice for SMBs. It is also
independent of the observed 4-byte alignments with the start of the MSRPC
header, including the 4-byte alignment between the MSRPC header and the
-MSRPC data.
-</p><p>
-First, an SMBtconX connection is made to the IPC$ share. The connection
+MSRPC data.</P
+><P
+>First, an SMBtconX connection is made to the IPC$ share. The connection
must be made using encrypted passwords, not clear-text. Then, an SMBopenX
is made on the pipe. Then, a Set Named Pipe Handle State must be sent,
after which the pipe is ready to accept API commands. Lastly, and SMBclose
-is sent.
-</p><p>
-To be resolved:
-</p><p>
-lkcl/01nov97 there appear to be two additional bytes after the null-terminated \PIPE\ name for the RPC pipe. Values seen so far are
-listed below:</p><pre class="programlisting">
- initial SMBopenX request: RPC API command 0x26 params:
- &quot;\\PIPE\\lsarpc&quot; 0x65 0x63; 0x72 0x70; 0x44 0x65;
- &quot;\\PIPE\\srvsvc&quot; 0x73 0x76; 0x4E 0x00; 0x5C 0x43;
-</pre></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2863422"></a>Header</h3></div></div><p>[section to be rewritten, following receipt of work by Duncan Stansfield]</p><p>Interesting note: if you set packed data representation to 0x0100 0000
-then all 4-byte and 2-byte word ordering is turned around!</p><p>The start of each of the NTLSA and NETLOGON named pipes begins with:</p><div class="segmentedlist"><p><b>offset: </b>00</p><p><b>Variable type: </b>UINT8</p><p><b>Variable data: </b>5 - RPC major version</p><p><b>offset: </b>01</p><p><b>Variable type: </b>UINT8</p><p><b>Variable data: </b>0 - RPC minor version</p><p><b>offset: </b>02</p><p><b>Variable type: </b>UINT8</p><p><b>Variable data: </b>2 - RPC response packet</p><p><b>offset: </b>03</p><p><b>Variable type: </b>UINT8</p><p><b>Variable data: </b>3 - (FirstFrag bit-wise or with LastFrag)</p><p><b>offset: </b>04</p><p><b>Variable type: </b>UINT32</p><p><b>Variable data: </b>0x1000 0000 - packed data representation</p><p><b>offset: </b>08</p><p><b>Variable type: </b>UINT16</p><p><b>Variable data: </b>fragment length - data size (bytes) inc header and tail.</p><p><b>offset: </b>0A</p><p><b>Variable type: </b>UINT16</p><p><b>Variable data: </b>0 - authentication length </p><p><b>offset: </b>0C</p><p><b>Variable type: </b>UINT32</p><p><b>Variable data: </b>call identifier. matches 12th UINT32 of incoming RPC data.</p><p><b>offset: </b>10</p><p><b>Variable type: </b>UINT32</p><p><b>Variable data: </b>allocation hint - data size (bytes) minus header and tail.</p><p><b>offset: </b>14</p><p><b>Variable type: </b>UINT16</p><p><b>Variable data: </b>0 - presentation context identifier</p><p><b>offset: </b>16</p><p><b>Variable type: </b>UINT8</p><p><b>Variable data: </b>0 - cancel count</p><p><b>offset: </b>17</p><p><b>Variable type: </b>UINT8</p><p><b>Variable data: </b>in replies: 0 - reserved; in requests: opnum - see #defines.</p><p><b>offset: </b>18</p><p><b>Variable type: </b>......</p><p><b>Variable data: </b>start of data (goes on for allocation_hint bytes)</p></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2863612"></a>RPC_Packet for request, response, bind and bind acknowledgement</h4></div></div><div class="variablelist"><dl><dt><span class="term">UINT8 versionmaj</span></dt><dd><p>reply same as request (0x05)</p></dd><dt><span class="term">UINT8 versionmin</span></dt><dd><p>reply same as request (0x00)</p></dd><dt><span class="term">UINT8 type</span></dt><dd><p>one of the MSRPC_Type enums</p></dd><dt><span class="term">UINT8 flags</span></dt><dd><p>reply same as request (0x00 for Bind, 0x03 for Request)</p></dd><dt><span class="term">UINT32 representation</span></dt><dd><p>reply same as request (0x00000010)</p></dd><dt><span class="term">UINT16 fraglength</span></dt><dd><p>the length of the data section of the SMB trans packet</p></dd><dt><span class="term">UINT16 authlength</span></dt><dd><p></p></dd><dt><span class="term">UINT32 callid</span></dt><dd><p>call identifier. (e.g. 0x00149594)</p></dd><dt><span class="term">* stub USE TvPacket</span></dt><dd><p>the remainder of the packet depending on the &quot;type&quot;</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2863746"></a>Interface identification</h4></div></div><p>the interfaces are numbered. as yet I haven't seen more than one interface used on the same pipe name srvsvc</p><pre class="programlisting">
-abstract (0x4B324FC8, 0x01D31670, 0x475A7812, 0x88E16EBF, 0x00000003)
-transfer (0x8A885D04, 0x11C91CEB, 0x0008E89F, 0x6048102B, 0x00000002)
-</pre></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2863772"></a>RPC_Iface RW</h4></div></div><div class="variablelist"><dl><dt><span class="term">UINT8 byte[16]</span></dt><dd><p>16 bytes of number</p></dd><dt><span class="term">UINT32 version</span></dt><dd><p>the interface number</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2863811"></a>RPC_ReqBind RW</h4></div></div><p>the remainder of the packet after the header if &quot;type&quot; was Bind in the response header, &quot;type&quot; should be BindAck</p><div class="variablelist"><dl><dt><span class="term">UINT16 maxtsize</span></dt><dd><p>maximum transmission fragment size (0x1630)</p></dd><dt><span class="term">UINT16 maxrsize</span></dt><dd><p>max receive fragment size (0x1630)</p></dd><dt><span class="term">UINT32 assocgid</span></dt><dd><p>associated group id (0x0)</p></dd><dt><span class="term">UINT32 numelements</span></dt><dd><p>the number of elements (0x1)</p></dd><dt><span class="term">UINT16 contextid</span></dt><dd><p>presentation context identifier (0x0)</p></dd><dt><span class="term">UINT8 numsyntaxes</span></dt><dd><p>the number of syntaxes (has always been 1?)(0x1)</p></dd><dt><span class="term">UINT8[]</span></dt><dd><p>4-byte alignment padding, against SMB header</p></dd><dt><span class="term">* abstractint USE RPC_Iface</span></dt><dd><p>num and vers. of interface client is using</p></dd><dt><span class="term">* transferint USE RPC_Iface</span></dt><dd><p>num and vers. of interface to use for replies</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2863952"></a>RPC_Address RW</h4></div></div><div class="variablelist"><dl><dt><span class="term">UINT16 length</span></dt><dd><p>length of the string including null terminator</p></dd><dt><span class="term">* port USE string</span></dt><dd><p>the string above in single byte, null terminated form</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2863992"></a>RPC_ResBind RW</h4></div></div><p>the response to place after the header in the reply packet</p><div class="variablelist"><dl><dt><span class="term">UINT16 maxtsize</span></dt><dd><p>same as request</p></dd><dt><span class="term">UINT16 maxrsize</span></dt><dd><p>same as request</p></dd><dt><span class="term">UINT32 assocgid</span></dt><dd><p>zero</p></dd><dt><span class="term">* secondaddr USE RPC_Address</span></dt><dd><p>the address string, as described earlier</p></dd><dt><span class="term">UINT8[]</span></dt><dd><p>4-byte alignment padding, against SMB header</p></dd><dt><span class="term">UINT8 numresults</span></dt><dd><p>the number of results (0x01)</p></dd><dt><span class="term">UINT8[]</span></dt><dd><p>4-byte alignment padding, against SMB header</p></dd><dt><span class="term">UINT16 result</span></dt><dd><p>result (0x00 = accept)</p></dd><dt><span class="term">UINT16 reason</span></dt><dd><p>reason (0x00 = no reason specified)</p></dd><dt><span class="term">* transfersyntax USE RPC_Iface</span></dt><dd><p>the transfer syntax from the request</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2864143"></a>RPC_ReqNorm RW</h4></div></div><p>the remainder of the packet after the header for every other other request</p><div class="variablelist"><dl><dt><span class="term">UINT32 allochint</span></dt><dd><p>the size of the stub data in bytes</p></dd><dt><span class="term">UINT16 prescontext</span></dt><dd><p>presentation context identifier (0x0)</p></dd><dt><span class="term">UINT16 opnum</span></dt><dd><p>operation number (0x15)</p></dd><dt><span class="term">* stub USE TvPacket</span></dt><dd><p>a packet dependent on the pipe name (probably the interface) and the op number)</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2864215"></a>RPC_ResNorm RW</h4></div></div><div class="variablelist"><dl><dt><span class="term">UINT32 allochint</span></dt><dd><p># size of the stub data in bytes</p></dd><dt><span class="term">UINT16 prescontext</span></dt><dd><p># presentation context identifier (same as request)</p></dd><dt><span class="term">UINT8 cancelcount</span></dt><dd><p># cancel count? (0x0)</p></dd><dt><span class="term">UINT8 reserved</span></dt><dd><p># 0 - one byte padding</p></dd><dt><span class="term">* stub USE TvPacket</span></dt><dd><p># the remainder of the reply</p></dd></dl></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2864296"></a>Tail</h3></div></div><p>The end of each of the NTLSA and NETLOGON named pipes ends with:</p><div class="variablelist"><dl><dt><span class="term">......</span></dt><dd><p>end of data</p></dd><dt><span class="term">UINT32</span></dt><dd><p>return code</p></dd></dl></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2864342"></a>RPC Bind / Bind Ack</h3></div></div><p>
-RPC Binds are the process of associating an RPC pipe (e.g \PIPE\lsarpc)
-with a &quot;transfer syntax&quot; (see RPC_Iface structure). The purpose for doing
-this is unknown.
-</p><p><span class="emphasis"><em>Note: The RPC_ResBind SMB Transact request is sent with two uint16 setup parameters. The first is 0x0026; the second is the file handle
- returned by the SMBopenX Transact response.</em></span></p><p><span class="emphasis"><em>Note: The RPC_ResBind members maxtsize, maxrsize and assocgid are the same in the response as the same members in the RPC_ReqBind. The
+is sent.</P
+><P
+>To be resolved:</P
+><P
+>lkcl/01nov97 there appear to be two additional bytes after the null-terminated \PIPE\ name for the RPC pipe. Values seen so far are
+listed below:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+> initial SMBopenX request: RPC API command 0x26 params:
+ "\\PIPE\\lsarpc" 0x65 0x63; 0x72 0x70; 0x44 0x65;
+ "\\PIPE\\srvsvc" 0x73 0x76; 0x4E 0x00; 0x5C 0x43;</PRE
+></P
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN1588"
+></A
+>9.3.2. Header</H3
+><P
+>[section to be rewritten, following receipt of work by Duncan Stansfield]</P
+><P
+>Interesting note: if you set packed data representation to 0x0100 0000
+then all 4-byte and 2-byte word ordering is turned around!</P
+><P
+>The start of each of the NTLSA and NETLOGON named pipes begins with:</P
+><P
+><B
+>offset: </B
+>00</P
+><P
+><B
+>Variable type: </B
+>UINT8</P
+><P
+><B
+>Variable data: </B
+>5 - RPC major version</P
+><P
+><B
+>offset: </B
+>01</P
+><P
+><B
+>Variable type: </B
+>UINT8</P
+><P
+><B
+>Variable data: </B
+>0 - RPC minor version</P
+><P
+><B
+>offset: </B
+>02</P
+><P
+><B
+>Variable type: </B
+>UINT8</P
+><P
+><B
+>Variable data: </B
+>2 - RPC response packet</P
+><P
+><B
+>offset: </B
+>03</P
+><P
+><B
+>Variable type: </B
+>UINT8</P
+><P
+><B
+>Variable data: </B
+>3 - (FirstFrag bit-wise or with LastFrag)</P
+><P
+><B
+>offset: </B
+>04</P
+><P
+><B
+>Variable type: </B
+>UINT32</P
+><P
+><B
+>Variable data: </B
+>0x1000 0000 - packed data representation</P
+><P
+><B
+>offset: </B
+>08</P
+><P
+><B
+>Variable type: </B
+>UINT16</P
+><P
+><B
+>Variable data: </B
+>fragment length - data size (bytes) inc header and tail.</P
+><P
+><B
+>offset: </B
+>0A</P
+><P
+><B
+>Variable type: </B
+>UINT16</P
+><P
+><B
+>Variable data: </B
+>0 - authentication length </P
+><P
+><B
+>offset: </B
+>0C</P
+><P
+><B
+>Variable type: </B
+>UINT32</P
+><P
+><B
+>Variable data: </B
+>call identifier. matches 12th UINT32 of incoming RPC data.</P
+><P
+><B
+>offset: </B
+>10</P
+><P
+><B
+>Variable type: </B
+>UINT32</P
+><P
+><B
+>Variable data: </B
+>allocation hint - data size (bytes) minus header and tail.</P
+><P
+><B
+>offset: </B
+>14</P
+><P
+><B
+>Variable type: </B
+>UINT16</P
+><P
+><B
+>Variable data: </B
+>0 - presentation context identifier</P
+><P
+><B
+>offset: </B
+>16</P
+><P
+><B
+>Variable type: </B
+>UINT8</P
+><P
+><B
+>Variable data: </B
+>0 - cancel count</P
+><P
+><B
+>offset: </B
+>17</P
+><P
+><B
+>Variable type: </B
+>UINT8</P
+><P
+><B
+>Variable data: </B
+>in replies: 0 - reserved; in requests: opnum - see #defines.</P
+><P
+><B
+>offset: </B
+>18</P
+><P
+><B
+>Variable type: </B
+>......</P
+><P
+><B
+>Variable data: </B
+>start of data (goes on for allocation_hint bytes)</P
+><DIV
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN1649"
+></A
+>9.3.2.1. RPC_Packet for request, response, bind and bind acknowledgement</H4
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>UINT8 versionmaj</DT
+><DD
+><P
+>reply same as request (0x05)</P
+></DD
+><DT
+>UINT8 versionmin</DT
+><DD
+><P
+>reply same as request (0x00)</P
+></DD
+><DT
+>UINT8 type</DT
+><DD
+><P
+>one of the MSRPC_Type enums</P
+></DD
+><DT
+>UINT8 flags</DT
+><DD
+><P
+>reply same as request (0x00 for Bind, 0x03 for Request)</P
+></DD
+><DT
+>UINT32 representation</DT
+><DD
+><P
+>reply same as request (0x00000010)</P
+></DD
+><DT
+>UINT16 fraglength</DT
+><DD
+><P
+>the length of the data section of the SMB trans packet</P
+></DD
+><DT
+>UINT16 authlength</DT
+><DD
+><P
+></P
+></DD
+><DT
+>UINT32 callid</DT
+><DD
+><P
+>call identifier. (e.g. 0x00149594)</P
+></DD
+><DT
+>* stub USE TvPacket</DT
+><DD
+><P
+>the remainder of the packet depending on the "type"</P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN1688"
+></A
+>9.3.2.2. Interface identification</H4
+><P
+>the interfaces are numbered. as yet I haven't seen more than one interface used on the same pipe name srvsvc</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>abstract (0x4B324FC8, 0x01D31670, 0x475A7812, 0x88E16EBF, 0x00000003)
+transfer (0x8A885D04, 0x11C91CEB, 0x0008E89F, 0x6048102B, 0x00000002)</PRE
+></P
+></DIV
+><DIV
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN1693"
+></A
+>9.3.2.3. RPC_Iface RW</H4
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>UINT8 byte[16]</DT
+><DD
+><P
+>16 bytes of number</P
+></DD
+><DT
+>UINT32 version</DT
+><DD
+><P
+>the interface number</P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN1704"
+></A
+>9.3.2.4. RPC_ReqBind RW</H4
+><P
+>the remainder of the packet after the header if "type" was Bind in the response header, "type" should be BindAck</P
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>UINT16 maxtsize</DT
+><DD
+><P
+>maximum transmission fragment size (0x1630)</P
+></DD
+><DT
+>UINT16 maxrsize</DT
+><DD
+><P
+>max receive fragment size (0x1630)</P
+></DD
+><DT
+>UINT32 assocgid</DT
+><DD
+><P
+>associated group id (0x0)</P
+></DD
+><DT
+>UINT32 numelements</DT
+><DD
+><P
+>the number of elements (0x1)</P
+></DD
+><DT
+>UINT16 contextid</DT
+><DD
+><P
+>presentation context identifier (0x0)</P
+></DD
+><DT
+>UINT8 numsyntaxes</DT
+><DD
+><P
+>the number of syntaxes (has always been 1?)(0x1)</P
+></DD
+><DT
+>UINT8[]</DT
+><DD
+><P
+>4-byte alignment padding, against SMB header</P
+></DD
+><DT
+>* abstractint USE RPC_Iface</DT
+><DD
+><P
+>num and vers. of interface client is using</P
+></DD
+><DT
+>* transferint USE RPC_Iface</DT
+><DD
+><P
+>num and vers. of interface to use for replies</P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN1744"
+></A
+>9.3.2.5. RPC_Address RW</H4
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>UINT16 length</DT
+><DD
+><P
+>length of the string including null terminator</P
+></DD
+><DT
+>* port USE string</DT
+><DD
+><P
+>the string above in single byte, null terminated form</P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN1755"
+></A
+>9.3.2.6. RPC_ResBind RW</H4
+><P
+>the response to place after the header in the reply packet</P
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>UINT16 maxtsize</DT
+><DD
+><P
+>same as request</P
+></DD
+><DT
+>UINT16 maxrsize</DT
+><DD
+><P
+>same as request</P
+></DD
+><DT
+>UINT32 assocgid</DT
+><DD
+><P
+>zero</P
+></DD
+><DT
+>* secondaddr USE RPC_Address</DT
+><DD
+><P
+>the address string, as described earlier</P
+></DD
+><DT
+>UINT8[]</DT
+><DD
+><P
+>4-byte alignment padding, against SMB header</P
+></DD
+><DT
+>UINT8 numresults</DT
+><DD
+><P
+>the number of results (0x01)</P
+></DD
+><DT
+>UINT8[]</DT
+><DD
+><P
+>4-byte alignment padding, against SMB header</P
+></DD
+><DT
+>UINT16 result</DT
+><DD
+><P
+>result (0x00 = accept)</P
+></DD
+><DT
+>UINT16 reason</DT
+><DD
+><P
+>reason (0x00 = no reason specified)</P
+></DD
+><DT
+>* transfersyntax USE RPC_Iface</DT
+><DD
+><P
+>the transfer syntax from the request</P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN1799"
+></A
+>9.3.2.7. RPC_ReqNorm RW</H4
+><P
+>the remainder of the packet after the header for every other other request</P
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>UINT32 allochint</DT
+><DD
+><P
+>the size of the stub data in bytes</P
+></DD
+><DT
+>UINT16 prescontext</DT
+><DD
+><P
+>presentation context identifier (0x0)</P
+></DD
+><DT
+>UINT16 opnum</DT
+><DD
+><P
+>operation number (0x15)</P
+></DD
+><DT
+>* stub USE TvPacket</DT
+><DD
+><P
+>a packet dependent on the pipe name (probably the interface) and the op number)</P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN1819"
+></A
+>9.3.2.8. RPC_ResNorm RW</H4
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>UINT32 allochint</DT
+><DD
+><P
+># size of the stub data in bytes</P
+></DD
+><DT
+>UINT16 prescontext</DT
+><DD
+><P
+># presentation context identifier (same as request)</P
+></DD
+><DT
+>UINT8 cancelcount</DT
+><DD
+><P
+># cancel count? (0x0)</P
+></DD
+><DT
+>UINT8 reserved</DT
+><DD
+><P
+># 0 - one byte padding</P
+></DD
+><DT
+>* stub USE TvPacket</DT
+><DD
+><P
+># the remainder of the reply</P
+></DD
+></DL
+></DIV
+></DIV
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN1842"
+></A
+>9.3.3. Tail</H3
+><P
+>The end of each of the NTLSA and NETLOGON named pipes ends with:</P
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>......</DT
+><DD
+><P
+>end of data</P
+></DD
+><DT
+>UINT32</DT
+><DD
+><P
+>return code</P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN1854"
+></A
+>9.3.4. RPC Bind / Bind Ack</H3
+><P
+>RPC Binds are the process of associating an RPC pipe (e.g \PIPE\lsarpc)
+with a "transfer syntax" (see RPC_Iface structure). The purpose for doing
+this is unknown.</P
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Note: The RPC_ResBind SMB Transact request is sent with two uint16 setup parameters. The first is 0x0026; the second is the file handle
+ returned by the SMBopenX Transact response.</I
+></SPAN
+></P
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Note: The RPC_ResBind members maxtsize, maxrsize and assocgid are the same in the response as the same members in the RPC_ReqBind. The
RPC_ResBind member transfersyntax is the same in the response as
- the</em></span></p><p><span class="emphasis"><em>Note: The RPC_ResBind response member secondaddr contains the name of what is presumed to be the service behind the RPC pipe. The
- mapping identified so far is:</em></span></p><div class="variablelist"><dl><dt><span class="term">initial SMBopenX request:</span></dt><dd><p>RPC_ResBind response:</p></dd><dt><span class="term">&quot;\\PIPE\\srvsvc&quot;</span></dt><dd><p>&quot;\\PIPE\\ntsvcs&quot;</p></dd><dt><span class="term">&quot;\\PIPE\\samr&quot;</span></dt><dd><p>&quot;\\PIPE\\lsass&quot;</p></dd><dt><span class="term">&quot;\\PIPE\\lsarpc&quot;</span></dt><dd><p>&quot;\\PIPE\\lsass&quot;</p></dd><dt><span class="term">&quot;\\PIPE\\wkssvc&quot;</span></dt><dd><p>&quot;\\PIPE\\wksvcs&quot;</p></dd><dt><span class="term">&quot;\\PIPE\\NETLOGON&quot;</span></dt><dd><p>&quot;\\PIPE\\NETLOGON&quot;</p></dd></dl></div><p><span class="emphasis"><em>Note: The RPC_Packet fraglength member in both the Bind Request and Bind Acknowledgment must contain the length of the entire RPC data, including the RPC_Packet header.</em></span></p><p>Request:</p><table class="simplelist" border="0" summary="Simple list"><tr><td>RPC_Packet</td></tr><tr><td>RPC_ReqBind</td></tr></table><p>Response:</p><table class="simplelist" border="0" summary="Simple list"><tr><td>RPC_Packet</td></tr><tr><td>RPC_ResBind</td></tr></table></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2864522"></a>NTLSA Transact Named Pipe</h3></div></div><p>The sequence of actions taken on this pipe are:</p><table class="simplelist" border="0" summary="Simple list"><tr><td>Establish a connection to the IPC$ share (SMBtconX). use encrypted passwords.</td></tr><tr><td>Open an RPC Pipe with the name &quot;\\PIPE\\lsarpc&quot;. Store the file handle.</td></tr><tr><td>Using the file handle, send a Set Named Pipe Handle state to 0x4300.</td></tr><tr><td>Send an LSA Open Policy request. Store the Policy Handle.</td></tr><tr><td>Using the Policy Handle, send LSA Query Info Policy requests, etc.</td></tr><tr><td>Using the Policy Handle, send an LSA Close.</td></tr><tr><td>Close the IPC$ share.</td></tr></table><p>Defines for this pipe, identifying the query are:</p><div class="variablelist"><dl><dt><span class="term">LSA Open Policy:</span></dt><dd><p>0x2c</p></dd><dt><span class="term">LSA Query Info Policy:</span></dt><dd><p>0x07</p></dd><dt><span class="term">LSA Enumerate Trusted Domains:</span></dt><dd><p>0x0d</p></dd><dt><span class="term">LSA Open Secret:</span></dt><dd><p>0xff</p></dd><dt><span class="term">LSA Lookup SIDs:</span></dt><dd><p>0xfe</p></dd><dt><span class="term">LSA Lookup Names:</span></dt><dd><p>0xfd</p></dd><dt><span class="term">LSA Close:</span></dt><dd><p>0x00</p></dd></dl></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2864687"></a>LSA Open Policy</h3></div></div><p><span class="emphasis"><em>Note: The policy handle can be anything you like.</em></span></p><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2864701"></a>Request</h4></div></div><div class="variablelist"><dl><dt><span class="term">VOID*</span></dt><dd><p>buffer pointer</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>server name - unicode string starting with two '\'s</p></dd><dt><span class="term">OBJ_ATTR</span></dt><dd><p>object attributes</p></dd><dt><span class="term">UINT32</span></dt><dd><p>1 - desired access</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2864771"></a>Response</h4></div></div><div class="variablelist"><dl><dt><span class="term">POL_HND</span></dt><dd><p>LSA policy handle</p></dd><dt><span class="term">return</span></dt><dd><p>0 - indicates success</p></dd></dl></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2864813"></a>LSA Query Info Policy</h3></div></div><p><span class="emphasis"><em>Note: The info class in response must be the same as that in the request.</em></span></p><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2864828"></a>Request</h4></div></div><div class="variablelist"><dl><dt><span class="term">POL_HND</span></dt><dd><p>LSA policy handle</p></dd><dt><span class="term">UINT16</span></dt><dd><p>info class (also a policy handle?)</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2864866"></a>Response</h4></div></div><div class="variablelist"><dl><dt><span class="term">VOID*</span></dt><dd><p>undocumented buffer pointer</p></dd><dt><span class="term">UINT16</span></dt><dd><p>info class (same as info class in request).</p></dd></dl></div><pre class="programlisting">
-switch (info class)
+ the</I
+></SPAN
+></P
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Note: The RPC_ResBind response member secondaddr contains the name of what is presumed to be the service behind the RPC pipe. The
+ mapping identified so far is:</I
+></SPAN
+></P
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>initial SMBopenX request:</DT
+><DD
+><P
+>RPC_ResBind response:</P
+></DD
+><DT
+>"\\PIPE\\srvsvc"</DT
+><DD
+><P
+>"\\PIPE\\ntsvcs"</P
+></DD
+><DT
+>"\\PIPE\\samr"</DT
+><DD
+><P
+>"\\PIPE\\lsass"</P
+></DD
+><DT
+>"\\PIPE\\lsarpc"</DT
+><DD
+><P
+>"\\PIPE\\lsass"</P
+></DD
+><DT
+>"\\PIPE\\wkssvc"</DT
+><DD
+><P
+>"\\PIPE\\wksvcs"</P
+></DD
+><DT
+>"\\PIPE\\NETLOGON"</DT
+><DD
+><P
+>"\\PIPE\\NETLOGON"</P
+></DD
+></DL
+></DIV
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Note: The RPC_Packet fraglength member in both the Bind Request and Bind Acknowledgment must contain the length of the entire RPC data, including the RPC_Packet header.</I
+></SPAN
+></P
+><P
+>Request:</P
+><P
+></P
+><TABLE
+BORDER="0"
+><TBODY
+><TR
+><TD
+>RPC_Packet</TD
+></TR
+><TR
+><TD
+>RPC_ReqBind</TD
+></TR
+></TBODY
+></TABLE
+><P
+></P
+><P
+>Response:</P
+><P
+></P
+><TABLE
+BORDER="0"
+><TBODY
+><TR
+><TD
+>RPC_Packet</TD
+></TR
+><TR
+><TD
+>RPC_ResBind</TD
+></TR
+></TBODY
+></TABLE
+><P
+></P
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN1898"
+></A
+>9.3.5. NTLSA Transact Named Pipe</H3
+><P
+>The sequence of actions taken on this pipe are:</P
+><P
+></P
+><TABLE
+BORDER="0"
+><TBODY
+><TR
+><TD
+>Establish a connection to the IPC$ share (SMBtconX). use encrypted passwords.</TD
+></TR
+><TR
+><TD
+>Open an RPC Pipe with the name "\\PIPE\\lsarpc". Store the file handle.</TD
+></TR
+><TR
+><TD
+>Using the file handle, send a Set Named Pipe Handle state to 0x4300.</TD
+></TR
+><TR
+><TD
+>Send an LSA Open Policy request. Store the Policy Handle.</TD
+></TR
+><TR
+><TD
+>Using the Policy Handle, send LSA Query Info Policy requests, etc.</TD
+></TR
+><TR
+><TD
+>Using the Policy Handle, send an LSA Close.</TD
+></TR
+><TR
+><TD
+>Close the IPC$ share.</TD
+></TR
+></TBODY
+></TABLE
+><P
+></P
+><P
+>Defines for this pipe, identifying the query are:</P
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>LSA Open Policy:</DT
+><DD
+><P
+>0x2c</P
+></DD
+><DT
+>LSA Query Info Policy:</DT
+><DD
+><P
+>0x07</P
+></DD
+><DT
+>LSA Enumerate Trusted Domains:</DT
+><DD
+><P
+>0x0d</P
+></DD
+><DT
+>LSA Open Secret:</DT
+><DD
+><P
+>0xff</P
+></DD
+><DT
+>LSA Lookup SIDs:</DT
+><DD
+><P
+>0xfe</P
+></DD
+><DT
+>LSA Lookup Names:</DT
+><DD
+><P
+>0xfd</P
+></DD
+><DT
+>LSA Close:</DT
+><DD
+><P
+>0x00</P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN1939"
+></A
+>9.3.6. LSA Open Policy</H3
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Note: The policy handle can be anything you like.</I
+></SPAN
+></P
+><DIV
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN1943"
+></A
+>9.3.6.1. Request</H4
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>VOID*</DT
+><DD
+><P
+>buffer pointer</P
+></DD
+><DT
+>UNISTR2</DT
+><DD
+><P
+>server name - unicode string starting with two '\'s</P
+></DD
+><DT
+>OBJ_ATTR</DT
+><DD
+><P
+>object attributes</P
+></DD
+><DT
+>UINT32</DT
+><DD
+><P
+>1 - desired access</P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN1962"
+></A
+>9.3.6.2. Response</H4
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>POL_HND</DT
+><DD
+><P
+>LSA policy handle</P
+></DD
+><DT
+>return</DT
+><DD
+><P
+>0 - indicates success</P
+></DD
+></DL
+></DIV
+></DIV
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN1973"
+></A
+>9.3.7. LSA Query Info Policy</H3
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Note: The info class in response must be the same as that in the request.</I
+></SPAN
+></P
+><DIV
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN1977"
+></A
+>9.3.7.1. Request</H4
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>POL_HND</DT
+><DD
+><P
+>LSA policy handle</P
+></DD
+><DT
+>UINT16</DT
+><DD
+><P
+>info class (also a policy handle?)</P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN1988"
+></A
+>9.3.7.2. Response</H4
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>VOID*</DT
+><DD
+><P
+>undocumented buffer pointer</P
+></DD
+><DT
+>UINT16</DT
+><DD
+><P
+>info class (same as info class in request).</P
+></DD
+></DL
+></DIV
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>switch (info class)
case 3:
case 5:
{
DOM_INFO domain info, levels 3 and 5 (are the same).
}
-return 0 - indicates success
-</pre></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2864921"></a>LSA Enumerate Trusted Domains</h3></div></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2864928"></a>Request</h4></div></div><p>no extra data</p></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2864941"></a>Response</h4></div></div><div class="variablelist"><dl><dt><span class="term">UINT32</span></dt><dd><p>0 - enumeration context</p></dd><dt><span class="term">UINT32</span></dt><dd><p>0 - entries read</p></dd><dt><span class="term">UINT32</span></dt><dd><p>0 - trust information</p></dd><dt><span class="term">return</span></dt><dd><p>0x8000 001a - &quot;no trusted domains&quot; success code</p></dd></dl></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2865012"></a>LSA Open Secret</h3></div></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2865020"></a>Request</h4></div></div><p>no extra data</p></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2865032"></a>Response</h4></div></div><div class="variablelist"><dl><dt><span class="term">UINT32</span></dt><dd><p>0 - undocumented</p></dd><dt><span class="term">UINT32</span></dt><dd><p>0 - undocumented</p></dd><dt><span class="term">UINT32</span></dt><dd><p>0 - undocumented</p></dd><dt><span class="term">UINT32</span></dt><dd><p>0 - undocumented</p></dd><dt><span class="term">UINT32</span></dt><dd><p>0 - undocumented</p></dd></dl></div><p>return 0x0C00 0034 - &quot;no such secret&quot; success code</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2865122"></a>LSA Close</h3></div></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2865129"></a>Request</h4></div></div><div class="variablelist"><dl><dt><span class="term">POL_HND</span></dt><dd><p>policy handle to be closed</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2865157"></a>Response</h4></div></div><div class="variablelist"><dl><dt><span class="term">POL_HND</span></dt><dd><p>0s - closed policy handle (all zeros)</p></dd></dl></div><p>return 0 - indicates success</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2865188"></a>LSA Lookup SIDS</h3></div></div><p><span class="emphasis"><em>Note: num_entries in response must be same as num_entries in request.</em></span></p><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2865203"></a>Request</h4></div></div><div class="variablelist"><dl><dt><span class="term">POL_HND</span></dt><dd><p>LSA policy handle</p></dd><dt><span class="term">UINT32</span></dt><dd><p>num_entries</p></dd><dt><span class="term">VOID*</span></dt><dd><p>undocumented domain SID buffer pointer</p></dd><dt><span class="term">VOID*</span></dt><dd><p>undocumented domain name buffer pointer</p></dd><dt><span class="term">VOID*[num_entries] undocumented domain SID pointers to be looked up.
-</span></dt><dd><p>DOM_SID[num_entries] domain SIDs to be looked up.</p></dd><dt><span class="term">char[16]</span></dt><dd><p>completely undocumented 16 bytes.</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2865302"></a>Response</h4></div></div><div class="variablelist"><dl><dt><span class="term">DOM_REF</span></dt><dd><p>domain reference response</p></dd><dt><span class="term">UINT32</span></dt><dd><p>num_entries (listed above)</p></dd><dt><span class="term">VOID*</span></dt><dd><p>undocumented buffer pointer</p></dd><dt><span class="term">UINT32</span></dt><dd><p>num_entries (listed above)</p></dd><dt><span class="term">DOM_SID2[num_entries]</span></dt><dd><p>domain SIDs (from Request, listed above).</p></dd><dt><span class="term">UINT32</span></dt><dd><p>num_entries (listed above)</p></dd></dl></div><p>return 0 - indicates success</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2865399"></a>LSA Lookup Names</h3></div></div><p><span class="emphasis"><em>Note: num_entries in response must be same as num_entries in request.</em></span></p><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2865413"></a>Request</h4></div></div><div class="variablelist"><dl><dt><span class="term">POL_HND</span></dt><dd><p>LSA policy handle</p></dd><dt><span class="term">UINT32</span></dt><dd><p>num_entries</p></dd><dt><span class="term">UINT32</span></dt><dd><p>num_entries</p></dd><dt><span class="term">VOID*</span></dt><dd><p>undocumented domain SID buffer pointer</p></dd><dt><span class="term">VOID*</span></dt><dd><p>undocumented domain name buffer pointer</p></dd><dt><span class="term">NAME[num_entries]</span></dt><dd><p>names to be looked up.</p></dd><dt><span class="term">char[]</span></dt><dd><p>undocumented bytes - falsely translated SID structure?</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2865527"></a>Response</h4></div></div><div class="variablelist"><dl><dt><span class="term">DOM_REF</span></dt><dd><p>domain reference response</p></dd><dt><span class="term">UINT32</span></dt><dd><p>num_entries (listed above)</p></dd><dt><span class="term">VOID*</span></dt><dd><p>undocumented buffer pointer</p></dd><dt><span class="term">UINT32</span></dt><dd><p>num_entries (listed above)</p></dd><dt><span class="term">DOM_RID[num_entries]</span></dt><dd><p>domain SIDs (from Request, listed above).</p></dd><dt><span class="term">UINT32</span></dt><dd><p>num_entries (listed above)</p></dd></dl></div><p>return 0 - indicates success</p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2865625"></a>NETLOGON rpc Transact Named Pipe</h2></div></div><p>The sequence of actions taken on this pipe are:</p><table class="simplelist" border="0" summary="Simple list"><tr><td>tablish a connection to the IPC$ share (SMBtconX). use encrypted passwords.</td></tr><tr><td>en an RPC Pipe with the name &quot;\\PIPE\\NETLOGON&quot;. Store the file handle.</td></tr><tr><td>ing the file handle, send a Set Named Pipe Handle state to 0x4300.</td></tr><tr><td>eate Client Challenge. Send LSA Request Challenge. Store Server Challenge.</td></tr><tr><td>lculate Session Key. Send an LSA Auth 2 Challenge. Store Auth2 Challenge.</td></tr><tr><td>lc/Verify Client Creds. Send LSA Srv PW Set. Calc/Verify Server Creds.</td></tr><tr><td>lc/Verify Client Creds. Send LSA SAM Logon . Calc/Verify Server Creds.</td></tr><tr><td>lc/Verify Client Creds. Send LSA SAM Logoff. Calc/Verify Server Creds.</td></tr><tr><td>ose the IPC$ share.</td></tr></table><p>Defines for this pipe, identifying the query are</p><div class="variablelist"><dl><dt><span class="term">LSA Request Challenge:</span></dt><dd><p>0x04</p></dd><dt><span class="term">LSA Server Password Set:</span></dt><dd><p>0x06</p></dd><dt><span class="term">LSA SAM Logon:</span></dt><dd><p>0x02</p></dd><dt><span class="term">LSA SAM Logoff:</span></dt><dd><p>0x03</p></dd><dt><span class="term">LSA Auth 2:</span></dt><dd><p>0x0f</p></dd><dt><span class="term">LSA Logon Control:</span></dt><dd><p>0x0e</p></dd></dl></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2865786"></a>LSA Request Challenge</h3></div></div><p><span class="emphasis"><em>Note: logon server name starts with two '\' characters and is upper case.</em></span></p><p><span class="emphasis"><em>Note: logon client is the machine, not the user.</em></span></p><p><span class="emphasis"><em>Note: the initial LanManager password hash, against which the challenge is issued, is the machine name itself (lower case). there will becalls issued (LSA Server Password Set) which will change this, later. refusing these calls allows you to always deal with the same password (i.e the LM# of the machine name in lower case).</em></span></p><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2865818"></a>Request</h4></div></div><div class="variablelist"><dl><dt><span class="term">VOID*</span></dt><dd><p>undocumented buffer pointer</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>logon server unicode string</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>logon client unicode string</p></dd><dt><span class="term">char[8]</span></dt><dd><p>client challenge</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2865888"></a>Response</h4></div></div><div class="variablelist"><dl><dt><span class="term">char[8]</span></dt><dd><p>server challenge</p></dd></dl></div><p>return 0 - indicates success</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2865921"></a>LSA Authenticate 2</h3></div></div><p><span class="emphasis"><em>Note: in between request and response, calculate the client credentials, and check them against the client-calculated credentials (this process uses the previously received client credentials).</em></span></p><p><span class="emphasis"><em>Note: neg_flags in the response is the same as that in the request.</em></span></p><p><span class="emphasis"><em>Note: you must take a copy of the client-calculated credentials received here, because they will be used in subsequent authentication packets.</em></span></p><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2865952"></a>Request</h4></div></div><div class="variablelist"><dl><dt><span class="term">LOG_INFO</span></dt><dd><p>client identification info</p></dd><dt><span class="term">char[8]</span></dt><dd><p>client-calculated credentials</p></dd><dt><span class="term">UINT8[]</span></dt><dd><p>padding to 4-byte align with start of SMB header.</p></dd><dt><span class="term">UINT32</span></dt><dd><p>neg_flags - negotiated flags (usual value is 0x0000 01ff)</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2866021"></a>Response</h4></div></div><div class="variablelist"><dl><dt><span class="term">char[8]</span></dt><dd><p>server credentials.</p></dd><dt><span class="term">UINT32</span></dt><dd><p>neg_flags - same as neg_flags in request.</p></dd></dl></div><p>return 0 - indicates success. failure value unknown.</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2866069"></a>LSA Server Password Set</h3></div></div><p><span class="emphasis"><em>Note: the new password is suspected to be a DES encryption using the old password to generate the key.</em></span></p><p><span class="emphasis"><em>Note: in between request and response, calculate the client credentials, and check them against the client-calculated credentials (this process uses the previously received client credentials).</em></span></p><p><span class="emphasis"><em>Note: the server credentials are constructed from the client-calculated credentials and the client time + 1 second.</em></span></p><p><span class="emphasis"><em>Note: you must take a copy of the client-calculated credentials received here, because they will be used in subsequent authentication packets.</em></span></p><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2866109"></a>Request</h4></div></div><div class="variablelist"><dl><dt><span class="term">CLNT_INFO</span></dt><dd><p>client identification/authentication info</p></dd><dt><span class="term">char[]</span></dt><dd><p>new password - undocumented.</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2866151"></a>Response</h4></div></div><div class="variablelist"><dl><dt><span class="term">CREDS</span></dt><dd><p>server credentials. server time stamp appears to be ignored.</p></dd></dl></div><p>return 0 - indicates success; 0xC000 006a indicates failure</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2866185"></a>LSA SAM Logon</h3></div></div><p><span class="emphasis"><em>
-Note: valid_user is True iff the username and password hash are valid for
- the requested domain.
-</em></span></p><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2866200"></a>Request</h4></div></div><div class="variablelist"><dl><dt><span class="term">SAM_INFO</span></dt><dd><p>sam_id structure</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2866227"></a>Response</h4></div></div><div class="variablelist"><dl><dt><span class="term">VOID*</span></dt><dd><p>undocumented buffer pointer</p></dd><dt><span class="term">CREDS</span></dt><dd><p>server credentials. server time stamp appears to be ignored.</p></dd></dl></div><pre class="programlisting">
-if (valid_user)
+return 0 - indicates success</PRE
+></P
+></DIV
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN2001"
+></A
+>9.3.8. LSA Enumerate Trusted Domains</H3
+><DIV
+CLASS="SECT3"
+><H4
+CLASS="SECT3"
+><A
+NAME="AEN2003"
+></A
+>9.3.8.1. Request</H4
+><P
+>no extra data</P
+></DIV
+><DIV
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN2006"
+></A
+>9.3.8.2. Response</H4
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>UINT32</DT
+><DD
+><P
+>0 - enumeration context</P
+></DD
+><DT
+>UINT32</DT
+><DD
+><P
+>0 - entries read</P
+></DD
+><DT
+>UINT32</DT
+><DD
+><P
+>0 - trust information</P
+></DD
+><DT
+>return</DT
+><DD
+><P
+>0x8000 001a - "no trusted domains" success code</P
+></DD
+></DL
+></DIV
+></DIV
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN2025"
+></A
+>9.3.9. LSA Open Secret</H3
+><DIV
+CLASS="SECT3"
+><H4
+CLASS="SECT3"
+><A
+NAME="AEN2027"
+></A
+>9.3.9.1. Request</H4
+><P
+>no extra data</P
+></DIV
+><DIV
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN2030"
+></A
+>9.3.9.2. Response</H4
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>UINT32</DT
+><DD
+><P
+>0 - undocumented</P
+></DD
+><DT
+>UINT32</DT
+><DD
+><P
+>0 - undocumented</P
+></DD
+><DT
+>UINT32</DT
+><DD
+><P
+>0 - undocumented</P
+></DD
+><DT
+>UINT32</DT
+><DD
+><P
+>0 - undocumented</P
+></DD
+><DT
+>UINT32</DT
+><DD
+><P
+>0 - undocumented</P
+></DD
+></DL
+></DIV
+><P
+>return 0x0C00 0034 - "no such secret" success code</P
+></DIV
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN2054"
+></A
+>9.3.10. LSA Close</H3
+><DIV
+CLASS="SECT3"
+><H4
+CLASS="SECT3"
+><A
+NAME="AEN2056"
+></A
+>9.3.10.1. Request</H4
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>POL_HND</DT
+><DD
+><P
+>policy handle to be closed</P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN2063"
+></A
+>9.3.10.2. Response</H4
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>POL_HND</DT
+><DD
+><P
+>0s - closed policy handle (all zeros)</P
+></DD
+></DL
+></DIV
+><P
+>return 0 - indicates success</P
+></DIV
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN2071"
+></A
+>9.3.11. LSA Lookup SIDS</H3
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Note: num_entries in response must be same as num_entries in request.</I
+></SPAN
+></P
+><DIV
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN2075"
+></A
+>9.3.11.1. Request</H4
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>POL_HND</DT
+><DD
+><P
+>LSA policy handle</P
+></DD
+><DT
+>UINT32</DT
+><DD
+><P
+>num_entries</P
+></DD
+><DT
+>VOID*</DT
+><DD
+><P
+>undocumented domain SID buffer pointer</P
+></DD
+><DT
+>VOID*</DT
+><DD
+><P
+>undocumented domain name buffer pointer</P
+></DD
+><DT
+>VOID*[num_entries] undocumented domain SID pointers to be looked up.</DT
+><DD
+><P
+>DOM_SID[num_entries] domain SIDs to be looked up.</P
+></DD
+><DT
+>char[16]</DT
+><DD
+><P
+>completely undocumented 16 bytes.</P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN2102"
+></A
+>9.3.11.2. Response</H4
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>DOM_REF</DT
+><DD
+><P
+>domain reference response</P
+></DD
+><DT
+>UINT32</DT
+><DD
+><P
+>num_entries (listed above)</P
+></DD
+><DT
+>VOID*</DT
+><DD
+><P
+>undocumented buffer pointer</P
+></DD
+><DT
+>UINT32</DT
+><DD
+><P
+>num_entries (listed above)</P
+></DD
+><DT
+>DOM_SID2[num_entries]</DT
+><DD
+><P
+>domain SIDs (from Request, listed above).</P
+></DD
+><DT
+>UINT32</DT
+><DD
+><P
+>num_entries (listed above)</P
+></DD
+></DL
+></DIV
+><P
+>return 0 - indicates success</P
+></DIV
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN2130"
+></A
+>9.3.12. LSA Lookup Names</H3
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Note: num_entries in response must be same as num_entries in request.</I
+></SPAN
+></P
+><DIV
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN2134"
+></A
+>9.3.12.1. Request</H4
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>POL_HND</DT
+><DD
+><P
+>LSA policy handle</P
+></DD
+><DT
+>UINT32</DT
+><DD
+><P
+>num_entries</P
+></DD
+><DT
+>UINT32</DT
+><DD
+><P
+>num_entries</P
+></DD
+><DT
+>VOID*</DT
+><DD
+><P
+>undocumented domain SID buffer pointer</P
+></DD
+><DT
+>VOID*</DT
+><DD
+><P
+>undocumented domain name buffer pointer</P
+></DD
+><DT
+>NAME[num_entries]</DT
+><DD
+><P
+>names to be looked up.</P
+></DD
+><DT
+>char[]</DT
+><DD
+><P
+>undocumented bytes - falsely translated SID structure?</P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN2165"
+></A
+>9.3.12.2. Response</H4
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>DOM_REF</DT
+><DD
+><P
+>domain reference response</P
+></DD
+><DT
+>UINT32</DT
+><DD
+><P
+>num_entries (listed above)</P
+></DD
+><DT
+>VOID*</DT
+><DD
+><P
+>undocumented buffer pointer</P
+></DD
+><DT
+>UINT32</DT
+><DD
+><P
+>num_entries (listed above)</P
+></DD
+><DT
+>DOM_RID[num_entries]</DT
+><DD
+><P
+>domain SIDs (from Request, listed above).</P
+></DD
+><DT
+>UINT32</DT
+><DD
+><P
+>num_entries (listed above)</P
+></DD
+></DL
+></DIV
+><P
+>return 0 - indicates success</P
+></DIV
+></DIV
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN2193"
+></A
+>9.4. NETLOGON rpc Transact Named Pipe</H2
+><P
+>The sequence of actions taken on this pipe are:</P
+><P
+></P
+><TABLE
+BORDER="0"
+><TBODY
+><TR
+><TD
+>tablish a connection to the IPC$ share (SMBtconX). use encrypted passwords.</TD
+></TR
+><TR
+><TD
+>en an RPC Pipe with the name "\\PIPE\\NETLOGON". Store the file handle.</TD
+></TR
+><TR
+><TD
+>ing the file handle, send a Set Named Pipe Handle state to 0x4300.</TD
+></TR
+><TR
+><TD
+>eate Client Challenge. Send LSA Request Challenge. Store Server Challenge.</TD
+></TR
+><TR
+><TD
+>lculate Session Key. Send an LSA Auth 2 Challenge. Store Auth2 Challenge.</TD
+></TR
+><TR
+><TD
+>lc/Verify Client Creds. Send LSA Srv PW Set. Calc/Verify Server Creds.</TD
+></TR
+><TR
+><TD
+>lc/Verify Client Creds. Send LSA SAM Logon . Calc/Verify Server Creds.</TD
+></TR
+><TR
+><TD
+>lc/Verify Client Creds. Send LSA SAM Logoff. Calc/Verify Server Creds.</TD
+></TR
+><TR
+><TD
+>ose the IPC$ share.</TD
+></TR
+></TBODY
+></TABLE
+><P
+></P
+><P
+>Defines for this pipe, identifying the query are</P
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>LSA Request Challenge:</DT
+><DD
+><P
+>0x04</P
+></DD
+><DT
+>LSA Server Password Set:</DT
+><DD
+><P
+>0x06</P
+></DD
+><DT
+>LSA SAM Logon:</DT
+><DD
+><P
+>0x02</P
+></DD
+><DT
+>LSA SAM Logoff:</DT
+><DD
+><P
+>0x03</P
+></DD
+><DT
+>LSA Auth 2:</DT
+><DD
+><P
+>0x0f</P
+></DD
+><DT
+>LSA Logon Control:</DT
+><DD
+><P
+>0x0e</P
+></DD
+></DL
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN2232"
+></A
+>9.4.1. LSA Request Challenge</H3
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Note: logon server name starts with two '\' characters and is upper case.</I
+></SPAN
+></P
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Note: logon client is the machine, not the user.</I
+></SPAN
+></P
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Note: the initial LanManager password hash, against which the challenge is issued, is the machine name itself (lower case). there will becalls issued (LSA Server Password Set) which will change this, later. refusing these calls allows you to always deal with the same password (i.e the LM# of the machine name in lower case).</I
+></SPAN
+></P
+><DIV
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN2240"
+></A
+>9.4.1.1. Request</H4
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>VOID*</DT
+><DD
+><P
+>undocumented buffer pointer</P
+></DD
+><DT
+>UNISTR2</DT
+><DD
+><P
+>logon server unicode string</P
+></DD
+><DT
+>UNISTR2</DT
+><DD
+><P
+>logon client unicode string</P
+></DD
+><DT
+>char[8]</DT
+><DD
+><P
+>client challenge</P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN2259"
+></A
+>9.4.1.2. Response</H4
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>char[8]</DT
+><DD
+><P
+>server challenge</P
+></DD
+></DL
+></DIV
+><P
+>return 0 - indicates success</P
+></DIV
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN2267"
+></A
+>9.4.2. LSA Authenticate 2</H3
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Note: in between request and response, calculate the client credentials, and check them against the client-calculated credentials (this process uses the previously received client credentials).</I
+></SPAN
+></P
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Note: neg_flags in the response is the same as that in the request.</I
+></SPAN
+></P
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Note: you must take a copy of the client-calculated credentials received here, because they will be used in subsequent authentication packets.</I
+></SPAN
+></P
+><DIV
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN2275"
+></A
+>9.4.2.1. Request</H4
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>LOG_INFO</DT
+><DD
+><P
+>client identification info</P
+></DD
+><DT
+>char[8]</DT
+><DD
+><P
+>client-calculated credentials</P
+></DD
+><DT
+>UINT8[]</DT
+><DD
+><P
+>padding to 4-byte align with start of SMB header.</P
+></DD
+><DT
+>UINT32</DT
+><DD
+><P
+>neg_flags - negotiated flags (usual value is 0x0000 01ff)</P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN2294"
+></A
+>9.4.2.2. Response</H4
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>char[8]</DT
+><DD
+><P
+>server credentials.</P
+></DD
+><DT
+>UINT32</DT
+><DD
+><P
+>neg_flags - same as neg_flags in request.</P
+></DD
+></DL
+></DIV
+><P
+>return 0 - indicates success. failure value unknown.</P
+></DIV
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN2306"
+></A
+>9.4.3. LSA Server Password Set</H3
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Note: the new password is suspected to be a DES encryption using the old password to generate the key.</I
+></SPAN
+></P
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Note: in between request and response, calculate the client credentials, and check them against the client-calculated credentials (this process uses the previously received client credentials).</I
+></SPAN
+></P
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Note: the server credentials are constructed from the client-calculated credentials and the client time + 1 second.</I
+></SPAN
+></P
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Note: you must take a copy of the client-calculated credentials received here, because they will be used in subsequent authentication packets.</I
+></SPAN
+></P
+><DIV
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN2316"
+></A
+>9.4.3.1. Request</H4
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>CLNT_INFO</DT
+><DD
+><P
+>client identification/authentication info</P
+></DD
+><DT
+>char[]</DT
+><DD
+><P
+>new password - undocumented.</P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN2327"
+></A
+>9.4.3.2. Response</H4
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>CREDS</DT
+><DD
+><P
+>server credentials. server time stamp appears to be ignored.</P
+></DD
+></DL
+></DIV
+><P
+>return 0 - indicates success; 0xC000 006a indicates failure</P
+></DIV
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN2335"
+></A
+>9.4.4. LSA SAM Logon</H3
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Note: valid_user is True iff the username and password hash are valid for
+ the requested domain.</I
+></SPAN
+></P
+><DIV
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN2339"
+></A
+>9.4.4.1. Request</H4
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>SAM_INFO</DT
+><DD
+><P
+>sam_id structure</P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN2346"
+></A
+>9.4.4.2. Response</H4
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>VOID*</DT
+><DD
+><P
+>undocumented buffer pointer</P
+></DD
+><DT
+>CREDS</DT
+><DD
+><P
+>server credentials. server time stamp appears to be ignored.</P
+></DD
+></DL
+></DIV
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>if (valid_user)
{
UINT16 3 - switch value indicating USER_INFO structure.
VOID* non-zero - pointer to USER_INFO structure
@@ -1298,117 +6896,1325 @@ else
UINT32 1 - Authoritative response; 0 - Non-Auth?
return 0xC000 0064 - NT_STATUS_NO_SUCH_USER.
-}
-</pre></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2866299"></a>LSA SAM Logoff</h3></div></div><p><span class="emphasis"><em>
-Note: presumably, the SAM_INFO structure is validated, and a (currently
- undocumented) error code returned if the Logoff is invalid.
-</em></span></p><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2866314"></a>Request</h4></div></div><div class="variablelist"><dl><dt><span class="term">SAM_INFO</span></dt><dd><p>sam_id structure</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2866341"></a>Response</h4></div></div><div class="variablelist"><dl><dt><span class="term">VOID*</span></dt><dd><p>undocumented buffer pointer</p></dd><dt><span class="term">CREDS</span></dt><dd><p>server credentials. server time stamp appears to be ignored.</p></dd></dl></div><p>return 0 - indicates success. undocumented failure indication.</p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2866391"></a>\\MAILSLOT\NET\NTLOGON</h2></div></div><p><span class="emphasis"><em>
-Note: mailslots will contain a response mailslot, to which the response
- should be sent. the target NetBIOS name is REQUEST_NAME&lt;20&gt;, where
- REQUEST_NAME is the name of the machine that sent the request.
-</em></span></p><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2866408"></a>Query for PDC</h3></div></div><p><span class="emphasis"><em>Note: NTversion, LMNTtoken, LM20token in response are the same as those given in the request.</em></span></p><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2866422"></a>Request</h4></div></div><div class="variablelist"><dl><dt><span class="term">UINT16</span></dt><dd><p>0x0007 - Query for PDC</p></dd><dt><span class="term">STR</span></dt><dd><p>machine name</p></dd><dt><span class="term">STR</span></dt><dd><p>response mailslot</p></dd><dt><span class="term">UINT8[]</span></dt><dd><p>padding to 2-byte align with start of mailslot.</p></dd><dt><span class="term">UNISTR</span></dt><dd><p>machine name</p></dd><dt><span class="term">UINT32</span></dt><dd><p>NTversion</p></dd><dt><span class="term">UINT16</span></dt><dd><p>LMNTtoken</p></dd><dt><span class="term">UINT16</span></dt><dd><p>LM20token</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2866549"></a>Response</h4></div></div><div class="variablelist"><dl><dt><span class="term">UINT16</span></dt><dd><p>0x000A - Respose to Query for PDC</p></dd><dt><span class="term">STR</span></dt><dd><p>machine name (in uppercase)</p></dd><dt><span class="term">UINT8[]</span></dt><dd><p>padding to 2-byte align with start of mailslot.</p></dd><dt><span class="term">UNISTR</span></dt><dd><p>machine name</p></dd><dt><span class="term">UNISTR</span></dt><dd><p>domain name</p></dd><dt><span class="term">UINT32</span></dt><dd><p>NTversion (same as received in request)</p></dd><dt><span class="term">UINT16</span></dt><dd><p>LMNTtoken (same as received in request)</p></dd><dt><span class="term">UINT16</span></dt><dd><p>LM20token (same as received in request)</p></dd></dl></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2866670"></a>SAM Logon</h3></div></div><p><span class="emphasis"><em>Note: machine name in response is preceded by two '\' characters.</em></span></p><p><span class="emphasis"><em>Note: NTversion, LMNTtoken, LM20token in response are the same as those given in the request.</em></span></p><p><span class="emphasis"><em>Note: user name in the response is presumably the same as that in the request.</em></span></p><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2866698"></a>Request</h4></div></div><div class="variablelist"><dl><dt><span class="term">UINT16</span></dt><dd><p>0x0012 - SAM Logon</p></dd><dt><span class="term">UINT16</span></dt><dd><p>request count</p></dd><dt><span class="term">UNISTR</span></dt><dd><p>machine name</p></dd><dt><span class="term">UNISTR</span></dt><dd><p>user name</p></dd><dt><span class="term">STR</span></dt><dd><p>response mailslot</p></dd><dt><span class="term">UINT32</span></dt><dd><p>alloweable account</p></dd><dt><span class="term">UINT32</span></dt><dd><p>domain SID size</p></dd><dt><span class="term">char[sid_size]</span></dt><dd><p>domain SID, of sid_size bytes.</p></dd><dt><span class="term">UINT8[]</span></dt><dd><p>???? padding to 4? 2? -byte align with start of mailslot.</p></dd><dt><span class="term">UINT32</span></dt><dd><p>NTversion</p></dd><dt><span class="term">UINT16</span></dt><dd><p>LMNTtoken</p></dd><dt><span class="term">UINT16</span></dt><dd><p>LM20token</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2866881"></a>Response</h4></div></div><div class="variablelist"><dl><dt><span class="term">UINT16</span></dt><dd><p>0x0013 - Response to SAM Logon</p></dd><dt><span class="term">UNISTR</span></dt><dd><p>machine name</p></dd><dt><span class="term">UNISTR</span></dt><dd><p>user name - workstation trust account</p></dd><dt><span class="term">UNISTR</span></dt><dd><p>domain name </p></dd><dt><span class="term">UINT32</span></dt><dd><p>NTversion</p></dd><dt><span class="term">UINT16</span></dt><dd><p>LMNTtoken</p></dd><dt><span class="term">UINT16</span></dt><dd><p>LM20token</p></dd></dl></div></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2866996"></a>SRVSVC Transact Named Pipe</h2></div></div><p>Defines for this pipe, identifying the query are:</p><div class="variablelist"><dl><dt><span class="term">Net Share Enum</span></dt><dd><p>0x0f</p></dd><dt><span class="term">Net Server Get Info</span></dt><dd><p>0x15</p></dd></dl></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2867041"></a>Net Share Enum</h3></div></div><p><span class="emphasis"><em>Note: share level and switch value in the response are presumably the same as those in the request.</em></span></p><p><span class="emphasis"><em>Note: cifsrap2.txt (section 5) may be of limited assistance here.</em></span></p><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2867062"></a>Request</h4></div></div><div class="variablelist"><dl><dt><span class="term">VOID*</span></dt><dd><p>pointer (to server name?)</p></dd><dt><span class="term">UNISTR2</span></dt><dd><p>server name</p></dd><dt><span class="term">UINT8[]</span></dt><dd><p>padding to get unicode string 4-byte aligned with the start of the SMB header.</p></dd><dt><span class="term">UINT32</span></dt><dd><p>share level</p></dd><dt><span class="term">UINT32</span></dt><dd><p>switch value</p></dd><dt><span class="term">VOID*</span></dt><dd><p>pointer to SHARE_INFO_1_CTR</p></dd><dt><span class="term">SHARE_INFO_1_CTR</span></dt><dd><p>share info with 0 entries</p></dd><dt><span class="term">UINT32</span></dt><dd><p>preferred maximum length (0xffff ffff)</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2867188"></a>Response</h4></div></div><div class="variablelist"><dl><dt><span class="term">UINT32</span></dt><dd><p>share level</p></dd><dt><span class="term">UINT32</span></dt><dd><p>switch value</p></dd><dt><span class="term">VOID*</span></dt><dd><p>pointer to SHARE_INFO_1_CTR</p></dd><dt><span class="term">SHARE_INFO_1_CTR</span></dt><dd><p>share info (only added if share info ptr is non-zero)</p></dd></dl></div><p>return 0 - indicates success</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2867261"></a>Net Server Get Info</h3></div></div><p><span class="emphasis"><em>Note: level is the same value as in the request.</em></span></p><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2867275"></a>Request</h4></div></div><div class="variablelist"><dl><dt><span class="term">UNISTR2</span></dt><dd><p>server name</p></dd><dt><span class="term">UINT32</span></dt><dd><p>switch level</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2867316"></a>Response</h4></div></div><div class="variablelist"><dl><dt><span class="term">UINT32</span></dt><dd><p>switch level</p></dd><dt><span class="term">VOID*</span></dt><dd><p>pointer to SERVER_INFO_101</p></dd><dt><span class="term">SERVER_INFO_101</span></dt><dd><p>server info (only added if server info ptr is non-zero)</p></dd></dl></div><p>return 0 - indicates success</p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2867378"></a>Cryptographic side of NT Domain Authentication</h2></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2867386"></a>Definitions</h3></div></div><div class="variablelist"><dl><dt><span class="term">Add(A1,A2)</span></dt><dd><p>Intel byte ordered addition of corresponding 4 byte words in arrays A1 and A2</p></dd><dt><span class="term">E(K,D)</span></dt><dd><p>DES ECB encryption of 8 byte data D using 7 byte key K</p></dd><dt><span class="term">lmowf()</span></dt><dd><p>Lan man hash</p></dd><dt><span class="term">ntowf()</span></dt><dd><p>NT hash</p></dd><dt><span class="term">PW</span></dt><dd><p>md4(machine_password) == md4(lsadump $machine.acc) ==
-pwdump(machine$) (initially) == md4(lmowf(unicode(machine)))
-</p></dd><dt><span class="term">ARC4(K,Lk,D,Ld)</span></dt><dd><p>ARC4 encryption of data D of length Ld with key K of length Lk</p></dd><dt><span class="term">v[m..n(,l)]</span></dt><dd><p>subset of v from bytes m to n, optionally padded with zeroes to length l</p></dd><dt><span class="term">Cred(K,D)</span></dt><dd><p>E(K[7..7,7],E(K[0..6],D)) computes a credential</p></dd><dt><span class="term">Time()</span></dt><dd><p>4 byte current time</p></dd><dt><span class="term">Cc,Cs</span></dt><dd><p>8 byte client and server challenges Rc,Rs: 8 byte client and server credentials</p></dd></dl></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2867548"></a>Protocol</h3></div></div><pre class="programlisting">
-C-&gt;S ReqChal,Cc
-S-&gt;C Cs
-</pre><pre class="programlisting">
-C &amp; S compute session key Ks = E(PW[9..15],E(PW[0..6],Add(Cc,Cs)))
-</pre><pre class="programlisting">
-C: Rc = Cred(Ks,Cc)
-C-&gt;S Authenticate,Rc
-S: Rs = Cred(Ks,Cs), assert(Rc == Cred(Ks,Cc))
-S-&gt;C Rs
-C: assert(Rs == Cred(Ks,Cs))
-</pre><p>
-On joining the domain the client will optionally attempt to change its
+}</PRE
+></P
+></DIV
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN2359"
+></A
+>9.4.5. LSA SAM Logoff</H3
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Note: presumably, the SAM_INFO structure is validated, and a (currently
+ undocumented) error code returned if the Logoff is invalid.</I
+></SPAN
+></P
+><DIV
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN2363"
+></A
+>9.4.5.1. Request</H4
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>SAM_INFO</DT
+><DD
+><P
+>sam_id structure</P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN2370"
+></A
+>9.4.5.2. Response</H4
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>VOID*</DT
+><DD
+><P
+>undocumented buffer pointer</P
+></DD
+><DT
+>CREDS</DT
+><DD
+><P
+>server credentials. server time stamp appears to be ignored.</P
+></DD
+></DL
+></DIV
+><P
+>return 0 - indicates success. undocumented failure indication.</P
+></DIV
+></DIV
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN2382"
+></A
+>9.5. \\MAILSLOT\NET\NTLOGON</H2
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Note: mailslots will contain a response mailslot, to which the response
+ should be sent. the target NetBIOS name is REQUEST_NAME&#60;20&#62;, where
+ REQUEST_NAME is the name of the machine that sent the request.</I
+></SPAN
+></P
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN2386"
+></A
+>9.5.1. Query for PDC</H3
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Note: NTversion, LMNTtoken, LM20token in response are the same as those given in the request.</I
+></SPAN
+></P
+><DIV
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN2390"
+></A
+>9.5.1.1. Request</H4
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>UINT16</DT
+><DD
+><P
+>0x0007 - Query for PDC</P
+></DD
+><DT
+>STR</DT
+><DD
+><P
+>machine name</P
+></DD
+><DT
+>STR</DT
+><DD
+><P
+>response mailslot</P
+></DD
+><DT
+>UINT8[]</DT
+><DD
+><P
+>padding to 2-byte align with start of mailslot.</P
+></DD
+><DT
+>UNISTR</DT
+><DD
+><P
+>machine name</P
+></DD
+><DT
+>UINT32</DT
+><DD
+><P
+>NTversion</P
+></DD
+><DT
+>UINT16</DT
+><DD
+><P
+>LMNTtoken</P
+></DD
+><DT
+>UINT16</DT
+><DD
+><P
+>LM20token</P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN2425"
+></A
+>9.5.1.2. Response</H4
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>UINT16</DT
+><DD
+><P
+>0x000A - Respose to Query for PDC</P
+></DD
+><DT
+>STR</DT
+><DD
+><P
+>machine name (in uppercase)</P
+></DD
+><DT
+>UINT8[]</DT
+><DD
+><P
+>padding to 2-byte align with start of mailslot.</P
+></DD
+><DT
+>UNISTR</DT
+><DD
+><P
+>machine name</P
+></DD
+><DT
+>UNISTR</DT
+><DD
+><P
+>domain name</P
+></DD
+><DT
+>UINT32</DT
+><DD
+><P
+>NTversion (same as received in request)</P
+></DD
+><DT
+>UINT16</DT
+><DD
+><P
+>LMNTtoken (same as received in request)</P
+></DD
+><DT
+>UINT16</DT
+><DD
+><P
+>LM20token (same as received in request)</P
+></DD
+></DL
+></DIV
+></DIV
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN2460"
+></A
+>9.5.2. SAM Logon</H3
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Note: machine name in response is preceded by two '\' characters.</I
+></SPAN
+></P
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Note: NTversion, LMNTtoken, LM20token in response are the same as those given in the request.</I
+></SPAN
+></P
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Note: user name in the response is presumably the same as that in the request.</I
+></SPAN
+></P
+><DIV
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN2468"
+></A
+>9.5.2.1. Request</H4
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>UINT16</DT
+><DD
+><P
+>0x0012 - SAM Logon</P
+></DD
+><DT
+>UINT16</DT
+><DD
+><P
+>request count</P
+></DD
+><DT
+>UNISTR</DT
+><DD
+><P
+>machine name</P
+></DD
+><DT
+>UNISTR</DT
+><DD
+><P
+>user name</P
+></DD
+><DT
+>STR</DT
+><DD
+><P
+>response mailslot</P
+></DD
+><DT
+>UINT32</DT
+><DD
+><P
+>alloweable account</P
+></DD
+><DT
+>UINT32</DT
+><DD
+><P
+>domain SID size</P
+></DD
+><DT
+>char[sid_size]</DT
+><DD
+><P
+>domain SID, of sid_size bytes.</P
+></DD
+><DT
+>UINT8[]</DT
+><DD
+><P
+>???? padding to 4? 2? -byte align with start of mailslot.</P
+></DD
+><DT
+>UINT32</DT
+><DD
+><P
+>NTversion</P
+></DD
+><DT
+>UINT16</DT
+><DD
+><P
+>LMNTtoken</P
+></DD
+><DT
+>UINT16</DT
+><DD
+><P
+>LM20token</P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN2519"
+></A
+>9.5.2.2. Response</H4
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>UINT16</DT
+><DD
+><P
+>0x0013 - Response to SAM Logon</P
+></DD
+><DT
+>UNISTR</DT
+><DD
+><P
+>machine name</P
+></DD
+><DT
+>UNISTR</DT
+><DD
+><P
+>user name - workstation trust account</P
+></DD
+><DT
+>UNISTR</DT
+><DD
+><P
+>domain name </P
+></DD
+><DT
+>UINT32</DT
+><DD
+><P
+>NTversion</P
+></DD
+><DT
+>UINT16</DT
+><DD
+><P
+>LMNTtoken</P
+></DD
+><DT
+>UINT16</DT
+><DD
+><P
+>LM20token</P
+></DD
+></DL
+></DIV
+></DIV
+></DIV
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN2550"
+></A
+>9.6. SRVSVC Transact Named Pipe</H2
+><P
+>Defines for this pipe, identifying the query are:</P
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>Net Share Enum</DT
+><DD
+><P
+>0x0f</P
+></DD
+><DT
+>Net Server Get Info</DT
+><DD
+><P
+>0x15</P
+></DD
+></DL
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN2562"
+></A
+>9.6.1. Net Share Enum</H3
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Note: share level and switch value in the response are presumably the same as those in the request.</I
+></SPAN
+></P
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Note: cifsrap2.txt (section 5) may be of limited assistance here.</I
+></SPAN
+></P
+><DIV
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN2568"
+></A
+>9.6.1.1. Request</H4
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>VOID*</DT
+><DD
+><P
+>pointer (to server name?)</P
+></DD
+><DT
+>UNISTR2</DT
+><DD
+><P
+>server name</P
+></DD
+><DT
+>UINT8[]</DT
+><DD
+><P
+>padding to get unicode string 4-byte aligned with the start of the SMB header.</P
+></DD
+><DT
+>UINT32</DT
+><DD
+><P
+>share level</P
+></DD
+><DT
+>UINT32</DT
+><DD
+><P
+>switch value</P
+></DD
+><DT
+>VOID*</DT
+><DD
+><P
+>pointer to SHARE_INFO_1_CTR</P
+></DD
+><DT
+>SHARE_INFO_1_CTR</DT
+><DD
+><P
+>share info with 0 entries</P
+></DD
+><DT
+>UINT32</DT
+><DD
+><P
+>preferred maximum length (0xffff ffff)</P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN2603"
+></A
+>9.6.1.2. Response</H4
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>UINT32</DT
+><DD
+><P
+>share level</P
+></DD
+><DT
+>UINT32</DT
+><DD
+><P
+>switch value</P
+></DD
+><DT
+>VOID*</DT
+><DD
+><P
+>pointer to SHARE_INFO_1_CTR</P
+></DD
+><DT
+>SHARE_INFO_1_CTR</DT
+><DD
+><P
+>share info (only added if share info ptr is non-zero)</P
+></DD
+></DL
+></DIV
+><P
+>return 0 - indicates success</P
+></DIV
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN2623"
+></A
+>9.6.2. Net Server Get Info</H3
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Note: level is the same value as in the request.</I
+></SPAN
+></P
+><DIV
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN2627"
+></A
+>9.6.2.1. Request</H4
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>UNISTR2</DT
+><DD
+><P
+>server name</P
+></DD
+><DT
+>UINT32</DT
+><DD
+><P
+>switch level</P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN2638"
+></A
+>9.6.2.2. Response</H4
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>UINT32</DT
+><DD
+><P
+>switch level</P
+></DD
+><DT
+>VOID*</DT
+><DD
+><P
+>pointer to SERVER_INFO_101</P
+></DD
+><DT
+>SERVER_INFO_101</DT
+><DD
+><P
+>server info (only added if server info ptr is non-zero)</P
+></DD
+></DL
+></DIV
+><P
+>return 0 - indicates success</P
+></DIV
+></DIV
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN2654"
+></A
+>9.7. Cryptographic side of NT Domain Authentication</H2
+><DIV
+CLASS="SECT2"
+><H3
+CLASS="SECT2"
+><A
+NAME="AEN2656"
+></A
+>9.7.1. Definitions</H3
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>Add(A1,A2)</DT
+><DD
+><P
+>Intel byte ordered addition of corresponding 4 byte words in arrays A1 and A2</P
+></DD
+><DT
+>E(K,D)</DT
+><DD
+><P
+>DES ECB encryption of 8 byte data D using 7 byte key K</P
+></DD
+><DT
+>lmowf()</DT
+><DD
+><P
+>Lan man hash</P
+></DD
+><DT
+>ntowf()</DT
+><DD
+><P
+>NT hash</P
+></DD
+><DT
+>PW</DT
+><DD
+><P
+>md4(machine_password) == md4(lsadump $machine.acc) ==
+pwdump(machine$) (initially) == md4(lmowf(unicode(machine)))</P
+></DD
+><DT
+>ARC4(K,Lk,D,Ld)</DT
+><DD
+><P
+>ARC4 encryption of data D of length Ld with key K of length Lk</P
+></DD
+><DT
+>v[m..n(,l)]</DT
+><DD
+><P
+>subset of v from bytes m to n, optionally padded with zeroes to length l</P
+></DD
+><DT
+>Cred(K,D)</DT
+><DD
+><P
+>E(K[7..7,7],E(K[0..6],D)) computes a credential</P
+></DD
+><DT
+>Time()</DT
+><DD
+><P
+>4 byte current time</P
+></DD
+><DT
+>Cc,Cs</DT
+><DD
+><P
+>8 byte client and server challenges Rc,Rs: 8 byte client and server credentials</P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN2699"
+></A
+>9.7.2. Protocol</H3
+><P
+>C-&#62;S ReqChal,Cc S-&#62;C Cs</P
+><P
+>C &#38; S compute session key Ks = E(PW[9..15],E(PW[0..6],Add(Cc,Cs)))</P
+><P
+>C: Rc = Cred(Ks,Cc) C-&#62;S Authenticate,Rc S: Rs = Cred(Ks,Cs),
+assert(Rc == Cred(Ks,Cc)) S-&#62;C Rs C: assert(Rs == Cred(Ks,Cs))</P
+><P
+>On joining the domain the client will optionally attempt to change its
password and the domain controller may refuse to update it depending
-on registry settings. This will also occur weekly afterwards.
-</p><pre class="programlisting">
-C: Tc = Time(), Rc' = Cred(Ks,Rc+Tc)
-C-&gt;S ServerPasswordSet,Rc',Tc,arc4(Ks[0..7,16],lmowf(randompassword())
-C: Rc = Cred(Ks,Rc+Tc+1)
-S: assert(Rc' == Cred(Ks,Rc+Tc)), Ts = Time()
-S: Rs' = Cred(Ks,Rs+Tc+1)
-S-&gt;C Rs',Ts
-C: assert(Rs' == Cred(Ks,Rs+Tc+1))
-S: Rs = Rs'
-</pre><p>
-User: U with password P wishes to login to the domain (incidental data
-such as workstation and domain omitted)
-</p><pre class="programlisting">
-C: Tc = Time(), Rc' = Cred(Ks,Rc+Tc)
-C-&gt;S NetLogonSamLogon,Rc',Tc,U,arc4(Ks[0..7,16],16,ntowf(P),16), arc4(Ks[0..7,16],16,lmowf(P),16)
-S: assert(Rc' == Cred(Ks,Rc+Tc)) assert(passwords match those in SAM)
-S: Ts = Time()
-</pre><pre class="programlisting">
-S-&gt;C Cred(Ks,Cred(Ks,Rc+Tc+1)),userinfo(logon script,UID,SIDs,etc)
-C: assert(Rs == Cred(Ks,Cred(Rc+Tc+1))
-C: Rc = Cred(Ks,Rc+Tc+1)
-</pre></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2867629"></a>Comments</h3></div></div><p>
-On first joining the domain the session key could be computed by
+on registry settings. This will also occur weekly afterwards.</P
+><P
+>C: Tc = Time(), Rc' = Cred(Ks,Rc+Tc) C-&#62;S ServerPasswordSet,Rc',Tc,
+arc4(Ks[0..7,16],lmowf(randompassword()) C: Rc = Cred(Ks,Rc+Tc+1) S:
+assert(Rc' == Cred(Ks,Rc+Tc)), Ts = Time() S: Rs' = Cred(Ks,Rs+Tc+1)
+S-&#62;C Rs',Ts C: assert(Rs' == Cred(Ks,Rs+Tc+1)) S: Rs = Rs'</P
+><P
+>User: U with password P wishes to login to the domain (incidental data
+such as workstation and domain omitted)</P
+><P
+>C: Tc = Time(), Rc' = Cred(Ks,Rc+Tc) C-&#62;S NetLogonSamLogon,Rc',Tc,U,
+arc4(Ks[0..7,16],16,ntowf(P),16), arc4(Ks[0..7,16],16,lmowf(P),16) S:
+assert(Rc' == Cred(Ks,Rc+Tc)) assert(passwords match those in SAM) S:
+Ts = Time()</P
+><P
+>S-&#62;C Cred(Ks,Cred(Ks,Rc+Tc+1)),userinfo(logon script,UID,SIDs,etc) C:
+assert(Rs == Cred(Ks,Cred(Rc+Tc+1)) C: Rc = Cred(Ks,Rc+Tc+1)</P
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN2709"
+></A
+>9.7.3. Comments</H3
+><P
+>On first joining the domain the session key could be computed by
anyone listening in on the network as the machine password has a well
known value. Until the machine is rebooted it will use this session
key to encrypt NT and LM one way functions of passwords which are
password equivalents. Any user who logs in before the machine has been
rebooted a second time will have their password equivalent exposed. Of
-course the new machine password is exposed at this time anyway.
-</p><p>
-None of the returned user info such as logon script, profile path and
-SIDs *appear* to be protected by anything other than the TCP checksum.
-</p><p>
-The server time stamps appear to be ignored.
-</p><p>
-The client sends a ReturnAuthenticator in the SamLogon request which I
+course the new machine password is exposed at this time anyway.</P
+><P
+>None of the returned user info such as logon script, profile path and
+SIDs *appear* to be protected by anything other than the TCP checksum.</P
+><P
+>The server time stamps appear to be ignored.</P
+><P
+>The client sends a ReturnAuthenticator in the SamLogon request which I
can't find a use for. However its time is used as the timestamp
-returned by the server.
-</p><p>
-The password OWFs should NOT be sent over the network reversibly
+returned by the server.</P
+><P
+>The password OWFs should NOT be sent over the network reversibly
encrypted. They should be sent using ARC4(Ks,md4(owf)) with the server
-computing the same function using the owf values in the SAM.
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2867679"></a>SIDs and RIDs</h2></div></div><p>
-SIDs and RIDs are well documented elsewhere.
-</p><p>
-A SID is an NT Security ID (see DOM_SID structure). They are of the form:
-</p><table class="simplelist" border="0" summary="Simple list"><tr><td>revision-NN-SubAuth1-SubAuth2-SubAuth3... </td></tr><tr><td>revision-0xNNNNNNNNNNNN-SubAuth1-SubAuth2-SubAuth3...</td></tr></table><p>
-currently, the SID revision is 1.
-The Sub-Authorities are known as Relative IDs (RIDs).
-</p><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2867719"></a>Well-known SIDs</h3></div></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2867726"></a>Universal well-known SIDs</h4></div></div><div class="variablelist"><dl><dt><span class="term">Null SID</span></dt><dd><p>S-1-0-0</p></dd><dt><span class="term">World</span></dt><dd><p>S-1-1-0</p></dd><dt><span class="term">Local</span></dt><dd><p>S-1-2-0</p></dd><dt><span class="term">Creator Owner ID</span></dt><dd><p>S-1-3-0</p></dd><dt><span class="term">Creator Group ID</span></dt><dd><p>S-1-3-1</p></dd><dt><span class="term">Creator Owner Server ID</span></dt><dd><p>S-1-3-2</p></dd><dt><span class="term">Creator Group Server ID</span></dt><dd><p>S-1-3-3</p></dd><dt><span class="term">(Non-unique IDs)</span></dt><dd><p>S-1-4</p></dd></dl></div></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2867852"></a>NT well-known SIDs</h4></div></div><div class="variablelist"><dl><dt><span class="term">NT Authority</span></dt><dd><p>S-1-5</p></dd><dt><span class="term">Dialup</span></dt><dd><p>S-1-5-1</p></dd><dt><span class="term">Network</span></dt><dd><p>S-1-5-2</p></dd><dt><span class="term">Batch</span></dt><dd><p>S-1-5-3</p></dd><dt><span class="term">Interactive</span></dt><dd><p>S-1-5-4</p></dd><dt><span class="term">Service</span></dt><dd><p>S-1-5-6</p></dd><dt><span class="term">AnonymousLogon(aka null logon session)</span></dt><dd><p>S-1-5-7</p></dd><dt><span class="term">Proxy</span></dt><dd><p>S-1-5-8</p></dd><dt><span class="term">ServerLogon(aka domain controller account)</span></dt><dd><p>S-1-5-8</p></dd><dt><span class="term">(Logon IDs)</span></dt><dd><p>S-1-5-5-X-Y</p></dd><dt><span class="term">(NT non-unique IDs)</span></dt><dd><p>S-1-5-0x15-...</p></dd><dt><span class="term">(Built-in domain)</span></dt><dd><p>s-1-5-0x20</p></dd></dl></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2868034"></a>Well-known RIDS</h3></div></div><p>
-A RID is a sub-authority value, as part of either a SID, or in the case
+computing the same function using the owf values in the SAM.</P
+></DIV
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN2716"
+></A
+>9.8. SIDs and RIDs</H2
+><P
+>SIDs and RIDs are well documented elsewhere.</P
+><P
+>A SID is an NT Security ID (see DOM_SID structure). They are of the form:</P
+><P
+></P
+><TABLE
+BORDER="0"
+><TBODY
+><TR
+><TD
+>revision-NN-SubAuth1-SubAuth2-SubAuth3... </TD
+></TR
+><TR
+><TD
+>revision-0xNNNNNNNNNNNN-SubAuth1-SubAuth2-SubAuth3...</TD
+></TR
+></TBODY
+></TABLE
+><P
+></P
+><P
+>currently, the SID revision is 1.
+The Sub-Authorities are known as Relative IDs (RIDs).</P
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN2724"
+></A
+>9.8.1. Well-known SIDs</H3
+><DIV
+CLASS="SECT3"
+><H4
+CLASS="SECT3"
+><A
+NAME="AEN2726"
+></A
+>9.8.1.1. Universal well-known SIDs</H4
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>Null SID</DT
+><DD
+><P
+>S-1-0-0</P
+></DD
+><DT
+>World</DT
+><DD
+><P
+>S-1-1-0</P
+></DD
+><DT
+>Local</DT
+><DD
+><P
+>S-1-2-0</P
+></DD
+><DT
+>Creator Owner ID</DT
+><DD
+><P
+>S-1-3-0</P
+></DD
+><DT
+>Creator Group ID</DT
+><DD
+><P
+>S-1-3-1</P
+></DD
+><DT
+>Creator Owner Server ID</DT
+><DD
+><P
+>S-1-3-2</P
+></DD
+><DT
+>Creator Group Server ID</DT
+><DD
+><P
+>S-1-3-3</P
+></DD
+><DT
+>(Non-unique IDs)</DT
+><DD
+><P
+>S-1-4</P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN2761"
+></A
+>9.8.1.2. NT well-known SIDs</H4
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>NT Authority</DT
+><DD
+><P
+>S-1-5</P
+></DD
+><DT
+>Dialup</DT
+><DD
+><P
+>S-1-5-1</P
+></DD
+><DT
+>Network</DT
+><DD
+><P
+>S-1-5-2</P
+></DD
+><DT
+>Batch</DT
+><DD
+><P
+>S-1-5-3</P
+></DD
+><DT
+>Interactive</DT
+><DD
+><P
+>S-1-5-4</P
+></DD
+><DT
+>Service</DT
+><DD
+><P
+>S-1-5-6</P
+></DD
+><DT
+>AnonymousLogon(aka null logon session)</DT
+><DD
+><P
+>S-1-5-7</P
+></DD
+><DT
+>Proxy</DT
+><DD
+><P
+>S-1-5-8</P
+></DD
+><DT
+>ServerLogon(aka domain controller account)</DT
+><DD
+><P
+>S-1-5-8</P
+></DD
+><DT
+>(Logon IDs)</DT
+><DD
+><P
+>S-1-5-5-X-Y</P
+></DD
+><DT
+>(NT non-unique IDs)</DT
+><DD
+><P
+>S-1-5-0x15-...</P
+></DD
+><DT
+>(Built-in domain)</DT
+><DD
+><P
+>s-1-5-0x20</P
+></DD
+></DL
+></DIV
+></DIV
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN2812"
+></A
+>9.8.2. Well-known RIDS</H3
+><P
+>A RID is a sub-authority value, as part of either a SID, or in the case
of Group RIDs, part of the DOM_GID structure, in the USER_INFO_1
-structure, in the LSA SAM Logon response.
-</p><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2868049"></a>Well-known RID users</h4></div></div><div class="segmentedlist"><p><b>Groupname: </b>DOMAIN_USER_RID_ADMIN</p><p><b>????: </b>0x0000</p><p><b>RID: </b>01F4</p><p><b>Groupname: </b>DOMAIN_USER_RID_GUEST</p><p><b>????: </b>0x0000</p><p><b>RID: </b>01F5</p></div></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2868097"></a>Well-known RID groups</h4></div></div><div class="segmentedlist"><p><b>Groupname: </b> DOMAIN_GROUP_RID_ADMINS</p><p><b>????: </b>0x0000</p><p><b>RID: </b>0200</p><p><b>Groupname: </b> DOMAIN_GROUP_RID_USERS</p><p><b>????: </b>0x0000</p><p><b>RID: </b>0201</p><p><b>Groupname: </b> DOMAIN_GROUP_RID_GUESTS</p><p><b>????: </b>0x0000</p><p><b>RID: </b>0202</p></div></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2868157"></a>Well-known RID aliases</h4></div></div><div class="segmentedlist"><p><b>Groupname: </b> DOMAIN_ALIAS_RID_ADMINS</p><p><b>????: </b>0x0000</p><p><b>RID: </b>0220</p><p><b>Groupname: </b> DOMAIN_ALIAS_RID_USERS</p><p><b>????: </b>0x0000</p><p><b>RID: </b>0221</p><p><b>Groupname: </b> DOMAIN_ALIAS_RID_GUESTS</p><p><b>????: </b>0x0000</p><p><b>RID: </b>0222</p><p><b>Groupname: </b> DOMAIN_ALIAS_RID_POWER_USERS</p><p><b>????: </b>0x0000</p><p><b>RID: </b>0223</p><p><b>Groupname: </b> DOMAIN_ALIAS_RID_ACCOUNT_OPS</p><p><b>????: </b>0x0000</p><p><b>RID: </b>0224</p><p><b>Groupname: </b> DOMAIN_ALIAS_RID_SYSTEM_OPS</p><p><b>????: </b>0x0000</p><p><b>RID: </b>0225</p><p><b>Groupname: </b> DOMAIN_ALIAS_RID_PRINT_OPS</p><p><b>????: </b>0x0000</p><p><b>RID: </b>0226</p><p><b>Groupname: </b> DOMAIN_ALIAS_RID_BACKUP_OPS</p><p><b>????: </b>0x0000</p><p><b>RID: </b>0227</p><p><b>Groupname: </b> DOMAIN_ALIAS_RID_REPLICATOR</p><p><b>????: </b>0x0000</p><p><b>RID: </b>0228</p></div></div></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="printing"></a>Chapter10.Samba Printing Internals</h2></div><div><div class="author"><h3 class="author">Gerald Carter</h3></div></div><div><p class="pubdate">October 2002</p></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2859754">Abstract</a></dt><dt><a href="#id2859770">
-Printing Interface to Various Back ends
-</a></dt><dt><a href="#id2859712">
-Print Queue TDB's
-</a></dt><dt><a href="#id2868639">
-ChangeID and Client Caching of Printer Information
-</a></dt><dt><a href="#id2868653">
-Windows NT/2K Printer Change Notify
-</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2859754"></a>Abstract</h2></div></div><p>
-The purpose of this document is to provide some insight into
+structure, in the LSA SAM Logon response.</P
+><DIV
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN2815"
+></A
+>9.8.2.1. Well-known RID users</H4
+><P
+><B
+>Groupname: </B
+>DOMAIN_USER_RID_ADMIN</P
+><P
+><B
+>????: </B
+>0x0000</P
+><P
+><B
+>RID: </B
+>01F4</P
+><P
+><B
+>Groupname: </B
+>DOMAIN_USER_RID_GUEST</P
+><P
+><B
+>????: </B
+>0x0000</P
+><P
+><B
+>RID: </B
+>01F5</P
+></DIV
+><DIV
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN2829"
+></A
+>9.8.2.2. Well-known RID groups</H4
+><P
+><B
+>Groupname: </B
+> DOMAIN_GROUP_RID_ADMINS</P
+><P
+><B
+>????: </B
+>0x0000</P
+><P
+><B
+>RID: </B
+>0200</P
+><P
+><B
+>Groupname: </B
+> DOMAIN_GROUP_RID_USERS</P
+><P
+><B
+>????: </B
+>0x0000</P
+><P
+><B
+>RID: </B
+>0201</P
+><P
+><B
+>Groupname: </B
+> DOMAIN_GROUP_RID_GUESTS</P
+><P
+><B
+>????: </B
+>0x0000</P
+><P
+><B
+>RID: </B
+>0202</P
+></DIV
+><DIV
+CLASS="SECT3"
+><HR><H4
+CLASS="SECT3"
+><A
+NAME="AEN2847"
+></A
+>9.8.2.3. Well-known RID aliases</H4
+><P
+><B
+>Groupname: </B
+> DOMAIN_ALIAS_RID_ADMINS</P
+><P
+><B
+>????: </B
+>0x0000</P
+><P
+><B
+>RID: </B
+>0220</P
+><P
+><B
+>Groupname: </B
+> DOMAIN_ALIAS_RID_USERS</P
+><P
+><B
+>????: </B
+>0x0000</P
+><P
+><B
+>RID: </B
+>0221</P
+><P
+><B
+>Groupname: </B
+> DOMAIN_ALIAS_RID_GUESTS</P
+><P
+><B
+>????: </B
+>0x0000</P
+><P
+><B
+>RID: </B
+>0222</P
+><P
+><B
+>Groupname: </B
+> DOMAIN_ALIAS_RID_POWER_USERS</P
+><P
+><B
+>????: </B
+>0x0000</P
+><P
+><B
+>RID: </B
+>0223</P
+><P
+><B
+>Groupname: </B
+> DOMAIN_ALIAS_RID_ACCOUNT_OPS</P
+><P
+><B
+>????: </B
+>0x0000</P
+><P
+><B
+>RID: </B
+>0224</P
+><P
+><B
+>Groupname: </B
+> DOMAIN_ALIAS_RID_SYSTEM_OPS</P
+><P
+><B
+>????: </B
+>0x0000</P
+><P
+><B
+>RID: </B
+>0225</P
+><P
+><B
+>Groupname: </B
+> DOMAIN_ALIAS_RID_PRINT_OPS</P
+><P
+><B
+>????: </B
+>0x0000</P
+><P
+><B
+>RID: </B
+>0226</P
+><P
+><B
+>Groupname: </B
+> DOMAIN_ALIAS_RID_BACKUP_OPS</P
+><P
+><B
+>????: </B
+>0x0000</P
+><P
+><B
+>RID: </B
+>0227</P
+><P
+><B
+>Groupname: </B
+> DOMAIN_ALIAS_RID_REPLICATOR</P
+><P
+><B
+>????: </B
+>0x0000</P
+><P
+><B
+>RID: </B
+>0228</P
+></DIV
+></DIV
+></DIV
+></DIV
+><DIV
+CLASS="CHAPTER"
+><HR><H1
+><A
+NAME="PRINTING"
+></A
+>Chapter 10. Samba Printing Internals</H1
+><DIV
+CLASS="SECT1"
+><H2
+CLASS="SECT1"
+><A
+NAME="AEN2896"
+></A
+>10.1. Abstract</H2
+><P
+>The purpose of this document is to provide some insight into
Samba's printing functionality and also to describe the semantics
-of certain features of Windows client printing.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2859770"></a>
-Printing Interface to Various Back ends
-</h2></div></div><p>
-Samba uses a table of function pointers to seven functions. The
-function prototypes are defined in the <tt>printif</tt> structure declared
-in <tt>printing.h</tt>.
-</p><div class="itemizedlist"><ul type="disc"><li><p>retrieve the contents of a print queue</p></li><li><p>pause the print queue</p></li><li><p>resume a paused print queue</p></li><li><p>delete a job from the queue</p></li><li><p>pause a job in the print queue</p></li><li><p>result a paused print job in the queue</p></li><li><p>submit a job to the print queue</p></li></ul></div><p>
-Currently there are only two printing back end implementations
-defined.
-</p><div class="itemizedlist"><ul type="disc"><li><p>a generic set of functions for working with standard UNIX
- printing subsystems</p></li><li><p>a set of CUPS specific functions (this is only enabled if
- the CUPS libraries were located at compile time).</p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2859712"></a>
-Print Queue TDB's
-</h2></div></div><p>
-Samba provides periodic caching of the output from the &quot;lpq command&quot;
+of certain features of Windows client printing.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN2899"
+></A
+>10.2. Printing Interface to Various Back ends</H2
+><P
+>Samba uses a table of function pointers to seven functions. The
+function prototypes are defined in the <TT
+CLASS="VARNAME"
+>printif</TT
+> structure declared
+in <TT
+CLASS="FILENAME"
+>printing.h</TT
+>.</P
+><P
+></P
+><UL
+><LI
+><P
+>retrieve the contents of a print queue</P
+></LI
+><LI
+><P
+>pause the print queue</P
+></LI
+><LI
+><P
+>resume a paused print queue</P
+></LI
+><LI
+><P
+>delete a job from the queue</P
+></LI
+><LI
+><P
+>pause a job in the print queue</P
+></LI
+><LI
+><P
+>result a paused print job in the queue</P
+></LI
+><LI
+><P
+>submit a job to the print queue</P
+></LI
+></UL
+><P
+>Currently there are only two printing back end implementations
+defined.</P
+><P
+></P
+><UL
+><LI
+><P
+>a generic set of functions for working with standard UNIX
+ printing subsystems</P
+></LI
+><LI
+><P
+>a set of CUPS specific functions (this is only enabled if
+ the CUPS libraries were located at compile time).</P
+></LI
+></UL
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN2925"
+></A
+>10.3. Print Queue TDB's</H2
+><P
+>Samba provides periodic caching of the output from the "lpq command"
for performance reasons. This cache time is configurable in seconds.
Obviously the longer the cache time the less often smbd will be
required to exec a copy of lpq. However, the accuracy of the print
-queue contents displayed to clients will be diminished as well.
-</p><p>
-The list of currently opened print queue TDB's can be found
+queue contents displayed to clients will be diminished as well.</P
+><P
+>The list of currently opened print queue TDB's can be found
be examining the list of tdb_print_db structures ( see print_db_head
in printing.c ). A queue TDB is opened using the wrapper function
printing.c:get_print_db_byname(). The function ensures that smbd
@@ -1416,15 +8222,17 @@ does not open more than MAX_PRINT_DBS_OPEN in an effort to prevent
a large print server from exhausting all available file descriptors.
If the number of open queue TDB's exceeds the MAX_PRINT_DBS_OPEN
limit, smbd falls back to a most recently used algorithm for maintaining
-a list of open TDB's.
-</p><p>
-There are two ways in which a a print job can be entered into
+a list of open TDB's.</P
+><P
+>There are two ways in which a a print job can be entered into
a print queue's TDB. The first is to submit the job from a Windows
client which will insert the job information directly into the TDB.
The second method is to have the print job picked up by executing the
-&quot;lpq command&quot;.
-</p><pre class="programlisting">
-/* included from printing.h */
+"lpq command".</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>/* included from printing.h */
struct printjob {
pid_t pid; /* which process launched the job */
int sysjob; /* the system (lp) job number */
@@ -1440,28 +8248,63 @@ struct printjob {
fstring user; /* the user who started the job */
fstring queuename; /* service number of printer for this job */
NT_DEVICEMODE *nt_devmode;
-};
-</pre><p>
-The current manifestation of the printjob structure contains a field
-for the UNIX job id returned from the &quot;lpq command&quot; and a Windows job
+};</PRE
+></P
+><P
+>The current manifestation of the printjob structure contains a field
+for the UNIX job id returned from the "lpq command" and a Windows job
ID (32-bit bounded by PRINT_MAX_JOBID). When a print job is returned
-by the &quot;lpq command&quot; that does not match an existing job in the queue's
+by the "lpq command" that does not match an existing job in the queue's
TDB, a 32-bit job ID above the &lt;*vance doesn't know what word is missing here*&gt; is generating by adding UNIX_JOB_START to
-the id reported by lpq.
-</p><p>
-In order to match a 32-bit Windows jobid onto a 16-bit lanman print job
+the id reported by lpq.</P
+><P
+>In order to match a 32-bit Windows jobid onto a 16-bit lanman print job
id, smbd uses an in memory TDB to match the former to a number appropriate
-for old lanman clients.
-</p><p>
-When updating a print queue, smbd will perform the following
-steps ( refer to <tt>print.c:print_queue_update()</tt> ):
-</p><div class="orderedlist"><ol type="1"><li><p>Check to see if another smbd is currently in
+for old lanman clients.</P
+><P
+>When updating a print queue, smbd will perform the following
+steps ( refer to <TT
+CLASS="FILENAME"
+>print.c:print_queue_update()</TT
+> ):</P
+><P
+></P
+><OL
+TYPE="1"
+><LI
+><P
+>Check to see if another smbd is currently in
the process of updating the queue contents by checking the pid
- stored in <tt>LOCK/<i><tt>printer_name</tt></i></tt>.
- If so, then do not update the TDB.</p></li><li><p>Lock the mutex entry in the TDB and store our own pid.
- Check that this succeeded, else fail.</p></li><li><p>Store the updated time stamp for the new cache
- listing</p></li><li><p>Retrieve the queue listing via &quot;lpq command&quot;</p></li><li><pre class="programlisting">
- foreach job in the queue
+ stored in <TT
+CLASS="CONSTANT"
+>LOCK/<TT
+CLASS="REPLACEABLE"
+><I
+>printer_name</I
+></TT
+></TT
+>.
+ If so, then do not update the TDB.</P
+></LI
+><LI
+><P
+>Lock the mutex entry in the TDB and store our own pid.
+ Check that this succeeded, else fail.</P
+></LI
+><LI
+><P
+>Store the updated time stamp for the new cache
+ listing</P
+></LI
+><LI
+><P
+>Retrieve the queue listing via "lpq command"</P
+></LI
+><LI
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+> foreach job in the queue
{
if the job is a UNIX job, create a new entry;
if the job has a Windows based jobid, then
@@ -1472,51 +8315,119 @@ steps ( refer to <tt>print.c:print_queue_update()</tt> ):
else
update the job status only
}
- }</pre></li><li><p>Delete any jobs in the TDB that are not
- in the in the lpq listing</p></li><li><p>Store the print queue status in the TDB</p></li><li><p>update the cache time stamp again</p></li></ol></div><p>
-Note that it is the contents of this TDB that is returned to Windows
-clients and not the actual listing from the &quot;lpq command&quot;.
-</p><p>
-The NT_DEVICEMODE stored as part of the printjob structure is used to
+ }</PRE
+></P
+></LI
+><LI
+><P
+>Delete any jobs in the TDB that are not
+ in the in the lpq listing</P
+></LI
+><LI
+><P
+>Store the print queue status in the TDB</P
+></LI
+><LI
+><P
+>update the cache time stamp again</P
+></LI
+></OL
+><P
+>Note that it is the contents of this TDB that is returned to Windows
+clients and not the actual listing from the "lpq command".</P
+><P
+>The NT_DEVICEMODE stored as part of the printjob structure is used to
store a pointer to a non-default DeviceMode associated with the print
job. The pointer will be non-null when the client included a Device
Mode in the OpenPrinterEx() call and subsequently submitted a job for
printing on that same handle. If the client did not include a Device
Mode in the OpenPrinterEx() request, the nt_devmode field is NULL
-and the job has the printer's device mode associated with it by default.
-</p><p>
-Only non-default Device Mode are stored with print jobs in the print
+and the job has the printer's device mode associated with it by default.</P
+><P
+>Only non-default Device Mode are stored with print jobs in the print
queue TDB. Otherwise, the Device Mode is obtained from the printer
-object when the client issues a GetJob(level == 2) request.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2868639"></a>
-ChangeID and Client Caching of Printer Information
-</h2></div></div><p>
-[To be filled in later]
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2868653"></a>
-Windows NT/2K Printer Change Notify
-</h2></div></div><p>
-When working with Windows NT+ clients, it is possible for a
+object when the client issues a GetJob(level == 2) request.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN2959"
+></A
+>10.4. ChangeID &#38; Client Caching of Printer Information</H2
+><P
+>[To be filled in later]</P
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN2962"
+></A
+>10.5. Windows NT/2K Printer Change Notify</H2
+><P
+>When working with Windows NT+ clients, it is possible for a
print server to use RPC to send asynchronous change notification
events to clients for certain printer and print job attributes.
This can be useful when the client needs to know that a new
job has been added to the queue for a given printer or that the
driver for a printer has been changed. Note that this is done
entirely orthogonal to cache updates based on a new ChangeID for
-a printer object.
-</p><p>
-The basic set of RPC's used to implement change notification are
-</p><div class="itemizedlist"><ul type="disc"><li><p>RemoteFindFirstPrinterChangeNotifyEx ( RFFPCN )</p></li><li><p>RemoteFindNextPrinterChangeNotifyEx ( RFNPCN )</p></li><li><p>FindClosePrinterChangeNotify( FCPCN )</p></li><li><p>ReplyOpenPrinter</p></li><li><p>ReplyClosePrinter</p></li><li><p>RouteRefreshPrinterChangeNotify ( RRPCN )</p></li></ul></div><p>
-One additional RPC is available to a server, but is never used by the
-Windows spooler service:
-</p><div class="itemizedlist"><ul type="disc"><li><p>RouteReplyPrinter()</p></li></ul></div><p>
-The opnum for all of these RPC's are defined in include/rpc_spoolss.h
-</p><p>
-Windows NT print servers use a bizarre method of sending print
+a printer object.</P
+><P
+>The basic set of RPC's used to implement change notification are</P
+><P
+></P
+><UL
+><LI
+><P
+>RemoteFindFirstPrinterChangeNotifyEx ( RFFPCN )</P
+></LI
+><LI
+><P
+>RemoteFindNextPrinterChangeNotifyEx ( RFNPCN )</P
+></LI
+><LI
+><P
+>FindClosePrinterChangeNotify( FCPCN )</P
+></LI
+><LI
+><P
+>ReplyOpenPrinter</P
+></LI
+><LI
+><P
+>ReplyClosePrinter</P
+></LI
+><LI
+><P
+>RouteRefreshPrinterChangeNotify ( RRPCN )</P
+></LI
+></UL
+><P
+>One additional RPC is available to a server, but is never used by the
+Windows spooler service:</P
+><P
+></P
+><UL
+><LI
+><P
+>RouteReplyPrinter()</P
+></LI
+></UL
+><P
+>The opnum for all of these RPC's are defined in include/rpc_spoolss.h</P
+><P
+>Windows NT print servers use a bizarre method of sending print
notification event to clients. The process of registering a new change
notification handle is as follows. The 'C' is for client and the
-'S' is for server. All error conditions have been eliminated.
-</p><pre class="programlisting">
-C: Obtain handle to printer or to the printer
+'S' is for server. All error conditions have been eliminated.</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>C: Obtain handle to printer or to the printer
server via the standard OpenPrinterEx() call.
S: Respond with a valid handle to object
@@ -1546,229 +8457,453 @@ C: If the change notification handle is ever released by the
or a piece of data was wrong.
S: The server closes the internal change notification handle
(POLICY_HND) and does not send any further change notification
- events to the client for that printer or job.
-</pre><p>
-The current list of notification events supported by Samba can be
-found by examining the internal tables in srv_spoolss_nt.c
-</p><div class="itemizedlist"><ul type="disc"><li><p>printer_notify_table[]</p></li><li><p>job_notify_table[]</p></li></ul></div><p>
-When an event occurs that could be monitored, smbd sends a message
+ events to the client for that printer or job.</PRE
+></P
+><P
+>The current list of notification events supported by Samba can be
+found by examining the internal tables in srv_spoolss_nt.c</P
+><P
+></P
+><UL
+><LI
+><P
+>printer_notify_table[]</P
+></LI
+><LI
+><P
+>job_notify_table[]</P
+></LI
+></UL
+><P
+>When an event occurs that could be monitored, smbd sends a message
to itself about the change. The list of events to be transmitted
are queued by the smbd process sending the message to prevent an
overload of TDB usage and the internal message is sent during smbd's
idle loop (refer to printing/notify.c and the functions
-send_spoolss_notify2_msg() and print_notify_send_messages() ).
-</p><p>
-The decision of whether or not the change is to be sent to connected
+send_spoolss_notify2_msg() and print_notify_send_messages() ).</P
+><P
+>The decision of whether or not the change is to be sent to connected
clients is made by the routine which actually sends the notification.
-( refer to srv_spoolss_nt.c:recieve_notify2_message() ).
-</p><p>
-Because it possible to receive a listing of multiple changes for
+( refer to srv_spoolss_nt.c:recieve_notify2_message() ).</P
+><P
+>Because it possible to receive a listing of multiple changes for
multiple printers, the notification events must be split into
categories by the printer name. This makes it possible to group
multiple change events to be sent in a single RPC according to the
-printer handle obtained via a ReplyOpenPrinter().
-</p><p>
-The actual change notification is performed using the RRPCN request
-RPC. This packet contains
-</p><div class="itemizedlist"><ul type="disc"><li><p>the printer handle registered with the
-client's spooler on which the change occurred</p></li><li><p>The change_low value which was sent as part
-of the last RFNPCN request from the client</p></li><li><p>The SPOOL_NOTIFY_INFO container with the event
-information</p></li></ul></div><p>
-A <tt>SPOOL_NOTIFY_INFO</tt> contains:
-</p><div class="itemizedlist"><ul type="disc"><li><p>the version and flags field are predefined
-and should not be changed</p></li><li><p>The count field is the number of entries
-in the SPOOL_NOTIFY_INFO_DATA array</p></li></ul></div><p>
-The <tt>SPOOL_NOTIFY_INFO_DATA</tt> entries contain:
-</p><div class="itemizedlist"><ul type="disc"><li><p>The type defines whether or not this event
-is for a printer or a print job</p></li><li><p>The field is the flag identifying the event</p></li><li><p>the notify_data union contains the new valuie of the
-attribute</p></li><li><p>The enc_type defines the size of the structure for marshalling
-and unmarshalling</p></li><li><p>(a) the id must be 0 for a printer event on a printer handle.
+printer handle obtained via a ReplyOpenPrinter().</P
+><P
+>The actual change notification is performed using the RRPCN request
+RPC. This packet contains</P
+><P
+></P
+><UL
+><LI
+><P
+>the printer handle registered with the
+client's spooler on which the change occurred</P
+></LI
+><LI
+><P
+>The change_low value which was sent as part
+of the last RFNPCN request from the client</P
+></LI
+><LI
+><P
+>The SPOOL_NOTIFY_INFO container with the event
+information</P
+></LI
+></UL
+><P
+>A <TT
+CLASS="VARNAME"
+>SPOOL_NOTIFY_INFO</TT
+> contains:</P
+><P
+></P
+><UL
+><LI
+><P
+>the version and flags field are predefined
+and should not be changed</P
+></LI
+><LI
+><P
+>The count field is the number of entries
+in the SPOOL_NOTIFY_INFO_DATA array</P
+></LI
+></UL
+><P
+>The <TT
+CLASS="VARNAME"
+>SPOOL_NOTIFY_INFO_DATA</TT
+> entries contain:</P
+><P
+></P
+><UL
+><LI
+><P
+>The type defines whether or not this event
+is for a printer or a print job</P
+></LI
+><LI
+><P
+>The field is the flag identifying the event</P
+></LI
+><LI
+><P
+>the notify_data union contains the new valuie of the
+attribute</P
+></LI
+><LI
+><P
+>The enc_type defines the size of the structure for marshalling
+and unmarshalling</P
+></LI
+><LI
+><P
+>(a) the id must be 0 for a printer event on a printer handle.
(b) the id must be the job id for an event on a printer job
(c) the id must be the matching number of the printer index used
in the response packet to the RFNPCN when using a print server
handle for notification. Samba currently uses the snum of
the printer for this which can break if the list of services
-has been modified since the notification handle was registered.</p></li><li><p>The size is either (a) the string length in UNICODE for strings,
+has been modified since the notification handle was registered.</P
+></LI
+><LI
+><P
+>The size is either (a) the string length in UNICODE for strings,
(b) the size in bytes of the security descriptor, or (c) 0 for
-data values.</p></li></ul></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="wins"></a>Chapter11.Samba WINS Internals</h2></div><div><div class="author"><h3 class="author">Gerald Carter</h3></div></div><div><p class="pubdate">October 2002</p></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2868400">WINS Failover</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2868400"></a>WINS Failover</h2></div></div><p>
-The current Samba codebase possesses the capability to use groups of WINS
+data values.</P
+></LI
+></UL
+></DIV
+></DIV
+><DIV
+CLASS="CHAPTER"
+><HR><H1
+><A
+NAME="WINS"
+></A
+>Chapter 11. Samba WINS Internals</H1
+><DIV
+CLASS="SECT1"
+><H2
+CLASS="SECT1"
+><A
+NAME="AEN3033"
+></A
+>11.1. WINS Failover</H2
+><P
+>The current Samba codebase possesses the capability to use groups of WINS
servers that share a common namespace for NetBIOS name registration and
-resolution. The formal parameter syntax is
-</p><pre class="programlisting">
- WINS_SERVER_PARAM = SERVER [ SEPARATOR SERVER_LIST ]
+resolution. The formal parameter syntax is</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+> WINS_SERVER_PARAM = SERVER [ SEPARATOR SERVER_LIST ]
WINS_SERVER_PARAM = &quot;wins server&quot;
SERVER = ADDR[:TAG]
ADDR = ip_addr | fqdn
TAG = string
SEPARATOR = comma | \s+
- SERVER_LIST = SERVER [ SEPARATOR SERVER_LIST ]
-</pre><p>
-A simple example of a valid wins server setting is
-</p><pre class="programlisting">
-[global]
- wins server = 192.168.1.2 192.168.1.3
-</pre><p>
-In the event that no TAG is defined in for a SERVER in the list, smbd assigns a default
+ SERVER_LIST = SERVER [ SEPARATOR SERVER_LIST ]</PRE
+></P
+><P
+>A simple example of a valid wins server setting is</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>[global]
+ wins server = 192.168.1.2 192.168.1.3</PRE
+></P
+><P
+>In the event that no TAG is defined in for a SERVER in the list, smbd assigns a default
TAG of &quot;*&quot;. A TAG is used to group servers of a shared NetBIOS namespace together. Upon
startup, nmbd will attempt to register the netbios name value with one server in each
-tagged group.
-</p><p>
-An example using tags to group WINS servers together is show here. Note that the use of
-interface names in the tags is only by convention and is not a technical requirement.
-</p><pre class="programlisting">
-[global]
- wins server = 192.168.1.2:eth0 192.168.1.3:eth0 192.168.2.2:eth1
-</pre><p>
-Using this configuration, nmbd would attempt to register the server's NetBIOS name
+tagged group.</P
+><P
+>An example using tags to group WINS servers together is show here. Note that the use of
+interface names in the tags is only by convention and is not a technical requirement.</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>[global]
+ wins server = 192.168.1.2:eth0 192.168.1.3:eth0 192.168.2.2:eth1</PRE
+></P
+><P
+>Using this configuration, nmbd would attempt to register the server's NetBIOS name
with one WINS server in each group. Because the &quot;eth0&quot; group has two servers, the
second server would only be used when a registration (or resolution) request to
-the first server in that group timed out.
-</p><p>
-NetBIOS name resolution follows a similar pattern as name registration. When resolving
+the first server in that group timed out.</P
+><P
+>NetBIOS name resolution follows a similar pattern as name registration. When resolving
a NetBIOS name via WINS, smbd and other Samba programs will attempt to query a single WINS
server in a tagged group until either a positive response is obtained at least once or
until a server from every tagged group has responded negatively to the name query request.
If a timeout occurs when querying a specific WINS server, that server is marked as down to
prevent further timeouts and the next server in the WINS group is contacted. Once marked as
dead, Samba will not attempt to contact that server for name registration/resolution queries
-for a period of 10 minutes.
-</p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="sam"></a>Chapter12.The Upcoming SAM System</h2></div><div><div class="author"><h3 class="author">Andrew Bartlett</h3></div></div><div><p class="pubdate">1 October 2002</p></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2869126">Security in the 'new SAM'</a></dt><dt><a href="#id2869257">Standalone from UNIX</a></dt><dt><a href="#id2869292">Handles and Races in the new SAM</a></dt><dt><a href="#id2869361">Layers</a></dt><dd><dl><dt><a href="#id2869368">Application</a></dt><dt><a href="#id2869384">SAM Interface</a></dt><dt><a href="#id2869412">SAM Modules</a></dt></dl></dd><dt><a href="#id2869434">SAM Modules</a></dt><dd><dl><dt><a href="#id2869441">Special Module: sam_passdb</a></dt><dt><a href="#id2869459">sam_ads</a></dt></dl></dd><dt><a href="#id2869498">Memory Management</a></dt><dt><a href="#id2869589">Testing</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2869126"></a>Security in the 'new SAM'</h2></div></div><p>One of the biggest problems with passdb is it's implementation of
+for a period of 10 minutes.</P
+></DIV
+></DIV
+><DIV
+CLASS="CHAPTER"
+><HR><H1
+><A
+NAME="SAM"
+></A
+>Chapter 12. The Upcoming SAM System</H1
+><DIV
+CLASS="SECT1"
+><H2
+CLASS="SECT1"
+><A
+NAME="AEN3054"
+></A
+>12.1. Security in the 'new SAM'</H2
+><P
+>One of the biggest problems with passdb is it's implementation of
'security'. Access control is on a 'are you root at the moment' basis,
and it has no concept of NT ACLs. Things like ldapsam had to add
-'magic' 'are you root' checks.</p><p>We took this very seriously when we started work, and the new structure
+'magic' 'are you root' checks.</P
+><P
+>We took this very seriously when we started work, and the new structure
is designed with this in mind, from the ground up. Each call to the SAM
has a NT_TOKEN and (if relevant) an 'access desired'. This is either
provided as a parameter, or implicitly supplied by the object being
-accessed.</p><p>
-For example, when you call
-</p><pre class="programlisting">
+accessed.</P
+><P
+>For example, when you call </P
+><PRE
+CLASS="PROGRAMLISTING"
+>&#60;
NTSTATUS sam_get_account_by_name(const SAM_CONTEXT *context, const
NT_USER_TOKEN *access_token, uint32 access_desired, const char *domain,
-const char *name, SAM_ACCOUNT_HANDLE **account)
-</pre><p>
-The context can be NULL (and is used to allow import/export by setting
-up 2 contexts, and allowing calls on both simultaneously)
-</p><p>
-The access token *must* be specified. Normally the user's token out of
-current_user, this can also be a global 'system' context.
-</p><p>
-The access desired is as per the ACL, for passing to the seaccess stuff.
-</p><p>
-The domain/username are standard. Even if we only have one domain,
+const char *name, SAM_ACCOUNT_HANDLE **account)</PRE
+><P
+>The context can be NULL (and is used to allow import/export by setting
+up 2 contexts, and allowing calls on both simultaneously)</P
+><P
+>The access token *must* be specified. Normally the user's token out of
+current_user, this can also be a global 'system' context.</P
+><P
+>The access desired is as per the ACL, for passing to the seaccess stuff.</P
+><P
+>The domain/username are standard. Even if we only have one domain,
keeping this ensures that we don't get 'unqualified' usernames (same
-problem as we had with unqualified SIDs).
-</p><p>
-We return a 'handle'. This is opaque to the rest of Samba, but is
-operated on by get/set routines, all of which return NTSTATUS.
-</p><p>
-The access checking is done by the SAM module. The reason it is not
+problem as we had with unqualified SIDs).</P
+><P
+>We return a 'handle'. This is opaque to the rest of Samba, but is
+operated on by get/set routines, all of which return NTSTATUS.</P
+><P
+>The access checking is done by the SAM module. The reason it is not
done 'above' the interface is to ensure a 'choke point'. I put a lot of
effort into the auth subsystem to ensure we never 'accidentally' forgot
to check for null passwords, missed a restriction etc. I intend the SAM
-to be written with the same caution.
-</p><p>
-The reason the access checking is not handled by the interface itself is
+to be written with the same caution.</P
+><P
+>The reason the access checking is not handled by the interface itself is
due to the different implementations it make take on. For example, on
ADS, you cannot set a password over a non-SSL connection. Other
backends may have similar requirements - we need to leave this policy up
to the modules. They will naturally have access to 'helper' procedures
-and good examples to avoid mishaps.
-</p><p>
-(Furthermore, some backends my actually chose to push the whole ACL
+and good examples to avoid mishaps.</P
+><P
+>(Furthermore, some backends my actually chose to push the whole ACL
issue to the remote server, and - assuming ldap for this example - bind
-as the user directly)
-</p><p>
-Each returned handle has an internal 'access permitted', which allows
+as the user directly)</P
+><P
+>Each returned handle has an internal 'access permitted', which allows
the 'get' and 'set' routines to return 'ACCESS_DENIED' for things that
were not able to be retrieved from the backend. This removes the need
to specify the NT_TOKEN on every operation, and allows for 'object not
-present' to be easily distinguished from 'access denied'.
-</p><p>
-When you 'set' an object (calling sam_update_account) the internal
+present' to be easily distinguished from 'access denied'.</P
+><P
+>When you 'set' an object (calling sam_update_account) the internal
details are again used. Each change that has been made to the object
has been flagged, so as to avoid race conditions (on unmodified
components) and to avoid violating any extra ACL requirements on the
-actual data store (like the LDAP server).
-</p><p>
-Finally, we have generic get_sec_desc() and set_sec_desc() routines to
-allow external ACL manipulation. These do lookups based on SID.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2869257"></a>Standalone from UNIX</h2></div></div><p>
-One of the primary tenants of the 'new SAM' is that it would not attempt
+actual data store (like the LDAP server).</P
+><P
+>Finally, we have generic get_sec_desc() and set_sec_desc() routines to
+allow external ACL manipulation. These do lookups based on SID.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN3071"
+></A
+>12.2. Standalone from UNIX</H2
+><P
+>One of the primary tenants of the 'new SAM' is that it would not attempt
to deal with 'what unix id for that'. This would be left to the 'SMS'
(Sid Mapping System') or SID farm, and probably administered via
winbind. We have had constructive discussion on how 'basic' unix
accounts like 'root' would be handled, and we think this can work.
-Accounts not preexisting in unix would be served up via winbind.
-</p><p>
-This is an *optional* part, and my preferred end-game. We have a fare
-way to go before things like winbind up to it however.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2869292"></a>Handles and Races in the new SAM</h2></div></div><p>
-One of the things that the 'new SAM' work has tried to face is both
+Accounts not preexisting in unix would be served up via winbind.</P
+><P
+>This is an *optional* part, and my preferred end-game. We have a fare
+way to go before things like winbind up to it however.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN3075"
+></A
+>12.3. Handles and Races in the new SAM</H2
+><P
+>One of the things that the 'new SAM' work has tried to face is both
compatibility with existing code, and a closer alignment to the SAMR
interface. I consider SAMR to be a 'primary customer' to the this work,
because if we get alignment with that wrong, things get more, rather
than less complex. Also, most other parts of Samba are much more
-flexible with what they can allow.
-</p><p>
-In any case, that was a decision taken as to how the general design
-would progress. BTW, my understanding of SAMR may be completely flawed.
-</p><p>
-One of the most race-prone areas of the new code is the conflicting
-update problem. We have taken two approaches:
-</p><div class="itemizedlist"><ul type="disc"><li><p>'Not conflicting' conflicts. Due to the way usrmgr operates, it will
+flexible with what they can allow.</P
+><P
+>In any case, that was a decision taken as to how the general design
+would progress. BTW, my understanding of SAMR may be completely flawed.</P
+><P
+>One of the most race-prone areas of the new code is the conflicting
+update problem. We have taken two approaches: </P
+><P
+></P
+><UL
+><LI
+><P
+>'Not conflicting' conflicts. Due to the way usrmgr operates, it will
open a user, display all the properties and *save* them all, even if you
-don't change any.
-</p><p>
-For this, see what I've done in rpc_server/srv_samr_util.c. I intend
+don't change any.</P
+><P
+>For this, see what I've done in rpc_server/srv_samr_util.c. I intend
to take this one step further, and operate on the 'handle' that the
values were read from. This should mean that we only update things that
-have *really* changed.
-</p></li><li><p>
-'conflicting' updates: Currently we don't deal with this (in passdb
+have *really* changed.</P
+></LI
+><LI
+><P
+>'conflicting' updates: Currently we don't deal with this (in passdb
or the new sam stuff), but the design is sufficiently flexible to 'deny'
-a second update. I don't foresee locking records however.
-</p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2869361"></a>Layers</h2></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2869368"></a>Application</h3></div></div><p>
-This is where smbd, samtest and whatever end-user replacement we have
+a second update. I don't foresee locking records however.</P
+></LI
+></UL
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN3086"
+></A
+>12.4. Layers</H2
+><DIV
+CLASS="SECT2"
+><H3
+CLASS="SECT2"
+><A
+NAME="AEN3088"
+></A
+>12.4.1. Application</H3
+><P
+>This is where smbd, samtest and whatever end-user replacement we have
for pdbedit sits. They use only the SAM interface, and do not get
-'special knowledge' of what is below them.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2869384"></a>SAM Interface</h3></div></div><p>
-This level 'owns' the various handle structures, the get/set routines on
+'special knowledge' of what is below them.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN3091"
+></A
+>12.4.2. SAM Interface</H3
+><P
+>This level 'owns' the various handle structures, the get/set routines on
those structures and provides the public interface. The application
layer may initialize a 'context' to be passed to all interface routines,
else a default, self-initialising context will be supplied. This layser
finds the appropriate backend module for the task, and tries very hard
not to need to much 'knowledge'. It should just provide the required
-abstraction to the modules below, and arrange for their initial loading.
-</p><p>
-We could possibly add ACL checking at this layer, to avoid discrepancies
-in implementation modules.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2869412"></a>SAM Modules</h3></div></div><p>
-These do not communicate with the application directly, only by setting
+abstraction to the modules below, and arrange for their initial loading.</P
+><P
+>We could possibly add ACL checking at this layer, to avoid discrepancies
+in implementation modules.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN3095"
+></A
+>12.4.3. SAM Modules</H3
+><P
+>These do not communicate with the application directly, only by setting
values in the handles, and receiving requests from the interface. These
modules are responsible for translating values from the handle's
.private into (say) an LDAP modification list. The module is expected
to 'know' things like it's own domain SID, domain name, and any other
state attached to the SAM. Simpler modules may call back to some helper
-routine.
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2869434"></a>SAM Modules</h2></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2869441"></a>Special Module: sam_passdb</h3></div></div><p>
-In order for there to be a smooth transition, kai is writing a module
+routine.</P
+></DIV
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN3098"
+></A
+>12.5. SAM Modules</H2
+><DIV
+CLASS="SECT2"
+><H3
+CLASS="SECT2"
+><A
+NAME="AEN3100"
+></A
+>12.5.1. Special Module: sam_passdb</H3
+><P
+>In order for there to be a smooth transition, kai is writing a module
that reads existing passdb backends, and translates them into SAM
replies. (Also pulling data from the account policy DB etc). We also
intend to write a module that does the reverse - gives the SAM a passdb
-interface.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2869459"></a>sam_ads</h3></div></div><p>
-This is the first of the SAM modules to be committed to the tree -
+interface.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN3103"
+></A
+>12.5.2. sam_ads</H3
+><P
+>This is the first of the SAM modules to be committed to the tree -
mainly because I needed to coordinate work with metze (who authored most
of it). This module aims to use Samba's libads code to provide an
Active Directory LDAP client, suitable for use on a mixed-mode DC.
While it is currently being tested against Win2k servers (with a
password in the smb.conf file) it is expected to eventually use a
(possibly modified) OpenLDAP server. We hope that this will assist in
-the construction of an Samba AD DC.
-</p><p>
-We also intend to construct a Samba 2.2/3.0 compatible ldap module,
-again using libads code.
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2869498"></a>Memory Management</h2></div></div><p>
+the construction of an Samba AD DC.</P
+><P
+>We also intend to construct a Samba 2.2/3.0 compatible ldap module,
+again using libads code.</P
+></DIV
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN3107"
+></A
+>12.6. Memory Management</H2
+><P
+>
The 'new SAM' development effort also concerned itself with getting a
sane implementation of memory management. It was decided that we would
be (as much as possible) talloc based, using an 'internal talloc
@@ -1776,63 +8911,132 @@ context' on many objects. That is, the creation of an object would
initiate it's own internal talloc context, and this would be used for
all operations on that object. Much of this is already implemented in
passdb. Also, like passdb, it will be possible to specify that some
-object actually be created on a specified context.
-</p><p>
-Memory management is important here because the APIs in the 'new SAM' do
+object actually be created on a specified context. </P
+><P
+>Memory management is important here because the APIs in the 'new SAM' do
not use 'pdb_init()' or an equivalent. They always allocate new
objects. Enumeration's are slightly different, and occur on a supplied
context that 'owns' the entire list, rather than per-element. (the
enumeration functions return an array of all elements - not full handles
just basic (and public) info) Likewise for things that fill in a char
-**.
-</p><p>For example:</p><pre class="programlisting">
-NTSTATUS sam_lookup_sid(const SAM_CONTEXT *context, const NT_USER_TOKEN
+**.</P
+><P
+>For example:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>NTSTATUS sam_lookup_sid(const SAM_CONTEXT *context, const NT_USER_TOKEN
*access_token, TALLOC_CTX *mem_ctx, const DOM_SID *sid, char **name,
-uint32 *type)
-</pre><p>Takes a context to allocate the 'name' on, while:</p><pre class="programlisting">
-NTSTATUS sam_get_account_by_sid(const SAM_CONTEXT *context, const
+uint32 *type)</PRE
+></P
+><P
+>Takes a context to allocate the 'name' on, while:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>NTSTATUS sam_get_account_by_sid(const SAM_CONTEXT *context, const
NT_USER_TOKEN *access_token, uint32 access_desired, const DOM_SID
-*accountsid, SAM_ACCOUNT_HANDLE **account)
-</pre><p>Allocates a handle and stores the allocation context on that handle.</p><p>I think that the following:</p><pre class="programlisting">
-NTSTATUS sam_enum_accounts(const SAM_CONTEXT *context, const
+*accountsid, SAM_ACCOUNT_HANDLE **account)</PRE
+></P
+><P
+>Allocates a handle and stores the allocation context on that handle.</P
+><P
+>I think that the following:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>NTSTATUS sam_enum_accounts(const SAM_CONTEXT *context, const
NT_USER_TOKEN *access_token, const DOM_SID *domainsid, uint16 acct_ctrl,
-int32 *account_count, SAM_ACCOUNT_ENUM **accounts)
-</pre></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2869589"></a>Testing</h2></div></div><p>
-Testing is vital in any piece of software, and Samba is certainly no
+int32 *account_count, SAM_ACCOUNT_ENUM **accounts)</PRE
+></P
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN3121"
+></A
+>12.7. Testing</H2
+><P
+>Testing is vital in any piece of software, and Samba is certainly no
exception. In designing this new subsystem, we have taken care to ensure
-it is easily tested, independent of outside protocols.
-</p><p>
-To this end, Jelmer has constructed 'samtest'.
-</p><p>
-This utility (see torture/samtest.c) is structured like rpcclient, but
+it is easily tested, independent of outside protocols.</P
+><P
+>To this end, Jelmer has constructed 'samtest'. </P
+><P
+>This utility (see torture/samtest.c) is structured like rpcclient, but
instead operates on the SAM subsystem. It creates a 'custom' SAM
context, that may be distinct from the default values used by the rest
-of the system, and can load a separate configuration file.
-</p><p>
-A small number of commands are currently implemented, but these have
+of the system, and can load a separate configuration file. </P
+><P
+>A small number of commands are currently implemented, but these have
already proved vital in testing. I expect SAM module authors will find
-it particularly valuable.
-</p><p>Example useage:</p><p><tt>$</tt> <b>bin/samtest</b></p><pre class="programlisting">
-&gt; context ads:ldap://192.168.1.96
-</pre><p>
+it particularly valuable.</P
+><P
+>Example useage:</P
+><P
+><TT
+CLASS="PROMPT"
+>$</TT
+> <B
+CLASS="COMMAND"
+>bin/samtest</B
+></P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>&#62; context ads:ldap://192.168.1.96</PRE
+>
(this loads a new context, using the new ADS module. The parameter is
-the 'location' of the ldap server)
-</p><pre class="programlisting">
-&gt; lookup_name DOMAIN abartlet
-</pre><p>
-(returns a sid).
-</p><p>
-Because the 'new SAM' is NT ACL based, there will be a command to
-specify an arbitrary NT ACL, but for now it uses 'system' by default.
-</p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="pwencrypt"></a>Chapter13.LanMan and NT Password Encryption</h2></div><div><div class="author"><h3 class="author">Jeremy Allison</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><br>
- <tt>&lt;<a href="mailto:samba@samba.org">samba@samba.org</a>&gt;</tt><br>
- </p></div></div></div></div><div><p class="pubdate">19 Apr 1999</p></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2869092">Introduction</a></dt><dt><a href="#id2868961">How does it work?</a></dt><dt><a href="#id2869678">The smbpasswd file</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2869092"></a>Introduction</h2></div></div><p>With the development of LanManager and Windows NT
+the 'location' of the ldap server)</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>&#62; lookup_name DOMAIN abartlet</PRE
+>
+(returns a sid).</P
+><P
+>Because the 'new SAM' is NT ACL based, there will be a command to
+specify an arbitrary NT ACL, but for now it uses 'system' by default.</P
+></DIV
+></DIV
+><DIV
+CLASS="CHAPTER"
+><HR><H1
+><A
+NAME="PWENCRYPT"
+></A
+>Chapter 13. LanMan and NT Password Encryption</H1
+><DIV
+CLASS="SECT1"
+><H2
+CLASS="SECT1"
+><A
+NAME="AEN3147"
+></A
+>13.1. Introduction</H2
+><P
+>With the development of LanManager and Windows NT
compatible password encryption for Samba, it is now able
to validate user connections in exactly the same way as
- a LanManager or Windows NT server.</p><p>This document describes how the SMB password encryption
+ a LanManager or Windows NT server.</P
+><P
+>This document describes how the SMB password encryption
algorithm works and what issues there are in choosing whether
you want to use it. You should read it carefully, especially
- the part about security and the &quot;PROS and CONS&quot; section.</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2868961"></a>How does it work?</h2></div></div><p>LanManager encryption is somewhat similar to UNIX
+ the part about security and the "PROS and CONS" section.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN3151"
+></A
+>13.2. How does it work?</H2
+><P
+>LanManager encryption is somewhat similar to UNIX
password encryption. The server uses a file containing a
hashed value of a user's password. This is created by taking
the user's plaintext password, capitalising it, and either
@@ -1840,190 +9044,265 @@ specify an arbitrary NT ACL, but for now it uses 'system' by default.
This 14 byte value is used as two 56 bit DES keys to encrypt
a 'magic' eight byte value, forming a 16 byte value which is
stored by the server and client. Let this value be known as
- the &quot;hashed password&quot;.</p><p>Windows NT encryption is a higher quality mechanism,
+ the "hashed password".</P
+><P
+>Windows NT encryption is a higher quality mechanism,
consisting of doing an MD4 hash on a Unicode version of the user's
password. This also produces a 16 byte hash value that is
- non-reversible.</p><p>When a client (LanManager, Windows for WorkGroups, Windows
+ non-reversible.</P
+><P
+>When a client (LanManager, Windows for WorkGroups, Windows
95 or Windows NT) wishes to mount a Samba drive (or use a Samba
resource), it first requests a connection and negotiates the
protocol that the client and server will use. In the reply to this
request the Samba server generates and appends an 8 byte, random
value - this is stored in the Samba server after the reply is sent
- and is known as the &quot;challenge&quot;. The challenge is different for
- every client connection.</p><p>The client then uses the hashed password (16 byte values
+ and is known as the "challenge". The challenge is different for
+ every client connection.</P
+><P
+>The client then uses the hashed password (16 byte values
described above), appended with 5 null bytes, as three 56 bit
DES keys, each of which is used to encrypt the challenge 8 byte
- value, forming a 24 byte value known as the &quot;response&quot;.</p><p>In the SMB call SMBsessionsetupX (when user level security
+ value, forming a 24 byte value known as the "response".</P
+><P
+>In the SMB call SMBsessionsetupX (when user level security
is selected) or the call SMBtconX (when share level security is
selected), the 24 byte response is returned by the client to the
Samba server. For Windows NT protocol levels the above calculation
is done on both hashes of the user's password and both responses are
- returned in the SMB call, giving two 24 byte values.</p><p>The Samba server then reproduces the above calculation, using
+ returned in the SMB call, giving two 24 byte values.</P
+><P
+>The Samba server then reproduces the above calculation, using
its own stored value of the 16 byte hashed password (read from the
- <tt>smbpasswd</tt> file - described later) and the challenge
+ <TT
+CLASS="FILENAME"
+>smbpasswd</TT
+> file - described later) and the challenge
value that it kept from the negotiate protocol reply. It then checks
to see if the 24 byte value it calculates matches the 24 byte value
- returned to it from the client.</p><p>If these values match exactly, then the client knew the
+ returned to it from the client.</P
+><P
+>If these values match exactly, then the client knew the
correct password (or the 16 byte hashed value - see security note
below) and is thus allowed access. If not, then the client did not
- know the correct password and is denied access.</p><p>Note that the Samba server never knows or stores the cleartext
+ know the correct password and is denied access.</P
+><P
+>Note that the Samba server never knows or stores the cleartext
of the user's password - just the 16 byte hashed values derived from
it. Also note that the cleartext password or 16 byte hashed values
- are never transmitted over the network - thus increasing security.</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2869678"></a>The smbpasswd file</h2></div></div><a name="SMBPASSWDFILEFORMAT"></a><p>In order for Samba to participate in the above protocol
+ are never transmitted over the network - thus increasing security.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN3162"
+></A
+>13.3. <A
+NAME="SMBPASSWDFILEFORMAT"
+></A
+>The smbpasswd file</H2
+><P
+>In order for Samba to participate in the above protocol
it must be able to look up the 16 byte hashed values given a user name.
Unfortunately, as the UNIX password value is also a one way hash
function (ie. it is impossible to retrieve the cleartext of the user's
password given the UNIX hash of it), a separate password file
containing this 16 byte value must be kept. To minimise problems with
- these two password files, getting out of sync, the UNIX <tt>
- /etc/passwd</tt> and the <tt>smbpasswd</tt> file,
- a utility, <b>mksmbpasswd.sh</b>, is provided to generate
- a smbpasswd file from a UNIX <tt>/etc/passwd</tt> file.
- </p><p>To generate the smbpasswd file from your <tt>/etc/passwd
- </tt> file use the following command:</p><p><tt>$ </tt><b><tt>cat /etc/passwd | mksmbpasswd.sh
- &gt; /usr/local/samba/private/smbpasswd</tt></b></p><p>If you are running on a system that uses NIS, use</p><p><tt>$ </tt><b><tt>ypcat passwd | mksmbpasswd.sh
- &gt; /usr/local/samba/private/smbpasswd</tt></b></p><p>The <b>mksmbpasswd.sh</b> program is found in
+ these two password files, getting out of sync, the UNIX <TT
+CLASS="FILENAME"
+> /etc/passwd</TT
+> and the <TT
+CLASS="FILENAME"
+>smbpasswd</TT
+> file,
+ a utility, <B
+CLASS="COMMAND"
+>mksmbpasswd.sh</B
+>, is provided to generate
+ a smbpasswd file from a UNIX <TT
+CLASS="FILENAME"
+>/etc/passwd</TT
+> file.
+ </P
+><P
+>To generate the smbpasswd file from your <TT
+CLASS="FILENAME"
+>/etc/passwd
+ </TT
+> file use the following command :</P
+><P
+><TT
+CLASS="PROMPT"
+>$ </TT
+><TT
+CLASS="USERINPUT"
+><B
+>cat /etc/passwd | mksmbpasswd.sh
+ &gt; /usr/local/samba/private/smbpasswd</B
+></TT
+></P
+><P
+>If you are running on a system that uses NIS, use</P
+><P
+><TT
+CLASS="PROMPT"
+>$ </TT
+><TT
+CLASS="USERINPUT"
+><B
+>ypcat passwd | mksmbpasswd.sh
+ &gt; /usr/local/samba/private/smbpasswd</B
+></TT
+></P
+><P
+>The <B
+CLASS="COMMAND"
+>mksmbpasswd.sh</B
+> program is found in
the Samba source directory. By default, the smbpasswd file is
- stored in :</p><p><tt>/usr/local/samba/private/smbpasswd</tt></p><p>The owner of the <tt>/usr/local/samba/private/</tt>
+ stored in :</P
+><P
+><TT
+CLASS="FILENAME"
+>/usr/local/samba/private/smbpasswd</TT
+></P
+><P
+>The owner of the <TT
+CLASS="FILENAME"
+>/usr/local/samba/private/</TT
+>
directory should be set to root, and the permissions on it should
- be set to 0500 (<b>chmod 500 /usr/local/samba/private</b>).
- </p><p>Likewise, the smbpasswd file inside the private directory should
+ be set to 0500 (<B
+CLASS="COMMAND"
+>chmod 500 /usr/local/samba/private</B
+>).
+ </P
+><P
+>Likewise, the smbpasswd file inside the private directory should
be owned by root and the permissions on is should be set to 0600
- (<b>chmod 600 smbpasswd</b>).</p><p>The format of the smbpasswd file is (The line has been
+ (<B
+CLASS="COMMAND"
+>chmod 600 smbpasswd</B
+>).</P
+><P
+>The format of the smbpasswd file is (The line has been
wrapped here. It should appear as one entry per line in
- your smbpasswd file.)</p><pre class="programlisting">
-username:uid:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:
+ your smbpasswd file.)</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>username:uid:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:
[Account type]:LCT-&lt;last-change-time&gt;:Long name
- </pre><p>Although only the <i><tt>username</tt></i>,
- <i><tt>uid</tt></i>, <i><tt>
- XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX</tt></i>,
- [<i><tt>Account type</tt></i>] and <i><tt>
- last-change-time</tt></i> sections are significant
- and are looked at in the Samba code.</p><p>It is <span class="emphasis"><em>VITALLY</em></span> important that there by 32
+ </PRE
+></P
+><P
+>Although only the <TT
+CLASS="REPLACEABLE"
+><I
+>username</I
+></TT
+>,
+ <TT
+CLASS="REPLACEABLE"
+><I
+>uid</I
+></TT
+>, <TT
+CLASS="REPLACEABLE"
+><I
+> XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX</I
+></TT
+>,
+ [<TT
+CLASS="REPLACEABLE"
+><I
+>Account type</I
+></TT
+>] and <TT
+CLASS="REPLACEABLE"
+><I
+> last-change-time</I
+></TT
+> sections are significant
+ and are looked at in the Samba code.</P
+><P
+>It is <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>VITALLY</I
+></SPAN
+> important that there by 32
'X' characters between the two ':' characters in the XXX sections -
the smbpasswd and Samba code will fail to validate any entries that
do not have 32 characters between ':' characters. The first XXX
section is for the Lanman password hash, the second is for the
- Windows NT version.</p><p>When the password file is created all users have password entries
+ Windows NT version.</P
+><P
+>When the password file is created all users have password entries
consisting of 32 'X' characters. By default this disallows any access
as this user. When a user has a password set, the 'X' characters change
to 32 ascii hexadecimal digits (0-9, A-F). These are an ascii
- representation of the 16 byte hashed value of a user's password.</p><p>To set a user to have no password (not recommended), edit the file
+ representation of the 16 byte hashed value of a user's password.</P
+><P
+>To set a user to have no password (not recommended), edit the file
using vi, and replace the first 11 characters with the ascii text
- <tt>&quot;NO PASSWORD&quot;</tt> (minus the quotes).</p><p>For example, to clear the password for user bob, his smbpasswd file
- entry would look like :</p><pre class="programlisting">
-bob:100:NO PASSWORDXXXXXXXXXXXXXXXXXXXXX:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:
- [U ]:LCT-00000000:Bob's full name:/bobhome:/bobshell
- </pre><p>If you are allowing users to use the smbpasswd command to set
+ <TT
+CLASS="CONSTANT"
+>"NO PASSWORD"</TT
+> (minus the quotes).</P
+><P
+>For example, to clear the password for user bob, his smbpasswd file
+ entry would look like :</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+> bob:100:NO PASSWORDXXXXXXXXXXXXXXXXXXXXX:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:[U ]:LCT-00000000:Bob's full name:/bobhome:/bobshell
+ </PRE
+></P
+><P
+>If you are allowing users to use the smbpasswd command to set
their own passwords, you may want to give users NO PASSWORD initially
so they do not have to enter a previous password when changing to their
new password (not recommended). In order for you to allow this the
- <b>smbpasswd</b> program must be able to connect to the
- <b>smbd</b> daemon as that user with no password. Enable this
- by adding the line :</p><p><b>null passwords = yes</b></p><p>to the [global] section of the smb.conf file (this is why
+ <B
+CLASS="COMMAND"
+>smbpasswd</B
+> program must be able to connect to the
+ <B
+CLASS="COMMAND"
+>smbd</B
+> daemon as that user with no password. Enable this
+ by adding the line :</P
+><P
+><B
+CLASS="COMMAND"
+>null passwords = yes</B
+></P
+><P
+>to the [global] section of the smb.conf file (this is why
the above scenario is not recommended). Preferably, allocate your
users a default password to begin with, so you do not have
- to enable this on your server.</p><p><span class="emphasis"><em>Note : </em></span>This file should be protected very
+ to enable this on your server.</P
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Note : </I
+></SPAN
+>This file should be protected very
carefully. Anyone with access to this file can (with enough knowledge of
the protocols) gain access to your SMB server. The file is thus more
- sensitive than a normal unix <tt>/etc/passwd</tt> file.</p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="modules"></a>Chapter14.Modules</h2></div><div><div class="author"><h3 class="author">Jelmer Vernooij</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt>&lt;<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate"> 19 March 2003 </p></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2870133">Advantages</a></dt><dt><a href="#id2869868">Loading modules</a></dt><dd><dl><dt><a href="#id2869901">Static modules</a></dt><dt><a href="#id2870337">Shared modules</a></dt></dl></dd><dt><a href="#id2870365">Writing modules</a></dt><dd><dl><dt><a href="#id2870425">Static/Shared selection in configure.in</a></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2870133"></a>Advantages</h2></div></div><p>
-The new modules system has the following advantages:
-</p><table class="simplelist" border="0" summary="Simple list"><tr><td>Transparent loading of static and shared modules (no need
-for a subsystem to know about modules)</td></tr><tr><td>Simple selection between shared and static modules at configure time</td></tr><tr><td>&quot;preload modules&quot; option for increasing performance for stable modules</td></tr><tr><td>No nasty #define stuff anymore</td></tr><tr><td>All backends are available as plugin now (including pdb_ldap and pdb_tdb)</td></tr></table></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2869868"></a>Loading modules</h2></div></div><p>
-Some subsystems in samba use different backends. These backends can be
-either statically linked in to samba or available as a plugin. A subsystem
-should have a function that allows a module to register itself. For example,
-the passdb subsystem has:
-</p><pre class="programlisting">
-BOOL smb_register_passdb(const char *name, pdb_init_function init, int version);
-</pre><p>
-This function will be called by the initialisation function of the module to
-register itself.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2869901"></a>Static modules</h3></div></div><p>
-The modules system compiles a list of initialisation functions for the
-static modules of each subsystem. This is a define. For example,
-it is here currently (from <tt>include/config.h</tt>):
-</p><pre class="programlisting">
-/* Static init functions */
-#define static_init_pdb { pdb_mysql_init(); pdb_ldap_init(); pdb_smbpasswd_init(); pdb_tdbsam_init(); pdb_guest_init();}
-</pre><p>
-These functions should be called before the subsystem is used. That
-should be done when the subsystem is initialised or first used.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2870337"></a>Shared modules</h3></div></div><p>
-If a subsystem needs a certain backend, it should check if it has
-already been registered. If the backend hasn't been registered already,
-the subsystem should call smb_probe_module(char *subsystem, char *backend).
-This function tries to load the correct module from a certain path
-($LIBDIR/subsystem/backend.so). If the first character in 'backend'
-is a slash, smb_probe_module() tries to load the module from the
-absolute path specified in 'backend'.
-</p><p>After smb_probe_module() has been executed, the subsystem
-should check again if the module has been registered.
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2870365"></a>Writing modules</h2></div></div><p>
-Each module has an initialisation function. For modules that are
-included with samba this name is '<i><tt>subsystem</tt></i>_<i><tt>backend</tt></i>_init'. For external modules (that will never be built-in, but only available as a module) this name is always 'init_module'. (In the case of modules included with samba, the configure system will add a #define subsystem_backend_init() init_module()).
-The prototype for these functions is:
-</p><pre class="programlisting">
-int init_module(void);
-</pre><p>This function should call one or more
-registration functions. The function should return non-zero on success and zero on
-failure.</p><p>For example, pdb_ldap_init() contains: </p><pre class="programlisting">
-int pdb_ldap_init(void)
-{
- smb_register_passdb(&quot;ldapsam&quot;, pdb_init_ldapsam, PASSDB_INTERFACE_VERSION);
- smb_register_passdb(&quot;ldapsam_nua&quot;, pdb_init_ldapsam_nua, PASSDB_INTERFACE_VERSION);
- return TRUE;
-}
-</pre><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2870425"></a>Static/Shared selection in configure.in</h3></div></div><p>
-Some macros in configure.in generate the various defines and substs that
-are necessary for the system to work correct. All modules that should
-be built by default have to be added to the variable 'default_modules'.
-For example, if ldap is found, pdb_ldap is added to this variable.
-</p><p>
-On the bottom of configure.in, SMB_MODULE() should be called
-for each module and SMB_SUBSYSTEM() for each subsystem.
-</p><p>Syntax:</p><pre class="programlisting">
-SMB_MODULE(<i><tt>subsystem</tt></i>_<i><tt>backend</tt></i>, <i><tt>object files</tt></i>, <i><tt>plugin name</tt></i>, <i><tt>subsystem name</tt></i>, <i><tt>static_action</tt></i>, <i><tt>shared_action</tt></i>)
-SMB_SUBSYSTEM(<i><tt>subsystem</tt></i>)
-</pre><p>Also, make sure to add the correct directives to
-<tt>Makefile.in</tt>. <i><tt>@SUBSYSTEM_STATIC@</tt></i>
-will be replaced with a list of objects files of the modules that need to
-be linked in statically. <i><tt>@SUBSYSTEM_MODULES@</tt></i> will
-be replaced with the names of the plugins to build.
-</p><p>You must make sure all .c files that contain defines that can
-be changed by ./configure are rebuilded in the 'modules_clean' make target.
-Practically, this means all c files that contain <b>static_init_subsystem;</b> calls need to be rebuilded.
-</p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="rpc-plugin"></a>Chapter15.RPC Pluggable Modules</h2></div><div><div class="author"><h3 class="author">Anthony Liguori</h3><div class="affiliation"><span class="orgname">IBM<br></span><div class="address"><p><tt>&lt;<a href="mailto:aliguor@us.ibm.com">aliguor@us.ibm.com</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author">Jelmer Vernooij</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt>&lt;<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate">January 2003</p></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2869935">About</a></dt><dt><a href="#id2869954">General Overview</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2869935"></a>About</h2></div></div><p>
-This document describes how to make use the new RPC Pluggable Modules features
-of Samba 3.0. This architecture was added to increase the maintainability of
-Samba allowing RPC Pipes to be worked on separately from the main CVS branch.
-The RPM architecture will also allow third-party vendors to add functionality
-to Samba through plug-ins.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2869954"></a>General Overview</h2></div></div><p>
-When an RPC call is sent to smbd, smbd tries to load a shared library by the
-name <tt>librpc_&lt;pipename&gt;.so</tt> to handle the call if
-it doesn't know how to handle the call internally. For instance, LSA calls
-are handled by <tt>librpc_lsass.so</tt>..
-These shared libraries should be located in the <tt>&lt;sambaroot&gt;/lib/rpc</tt>. smbd then attempts to call the init_module function within
-the shared library. Check the chapter on modules for more information.
-</p><p>
-In the init_module function, the library should call
-rpc_pipe_register_commands(). This function takes the following arguments:
-</p><pre class="programlisting">
-int rpc_pipe_register_commands(const char *clnt, const char *srv,
- const struct api_struct *cmds, int size);
-</pre><div class="variablelist"><dl><dt><span class="term">clnt</span></dt><dd><p>the Client name of the named pipe</p></dd><dt><span class="term">srv</span></dt><dd><p>the Server name of the named pipe</p></dd><dt><span class="term">cmds</span></dt><dd><p>a list of api_structs that map RPC ordinal numbers to function calls</p></dd><dt><span class="term">size</span></dt><dd><p>the number of api_structs contained in cmds</p></dd></dl></div><p>
-See rpc_server/srv_reg.c and rpc_server/srv_reg_nt.c for a small example of
-how to use this library.
-</p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="Packaging"></a>Chapter16.Notes to packagers</h2></div><div><div class="author"><h3 class="author">Jelmer Vernooij</h3></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2870644">Versioning</a></dt><dt><a href="#id2870677">Modules</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2870644"></a>Versioning</h2></div></div><p>Please, please update the version number in
-<tt>source/include/version.h</tt> to include the versioning of your package. This makes it easier to distinguish standard samba builds
-from custom-build samba builds (distributions often patch packages). For
-example, a good version would be: </p><pre class="programlisting">
-Version 2.999+3.0.alpha21-5 for Debian
-</pre></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2870677"></a>Modules</h2></div></div><p>Samba now has support for building parts of samba as plugins. This
-makes it possible to, for example, put ldap or mysql support in a seperate
-package, thus making it possible to have a normal samba package not
-depending on ldap or mysql. To build as much parts of samba
-as a plugin, run: </p><pre class="programlisting">
-./configure --with-shared-modules=rpc,vfs,auth,pdb,charset
-</pre></div></div></div></body></html>
+ sensitive than a normal unix <TT
+CLASS="FILENAME"
+>/etc/passwd</TT
+> file.</P
+></DIV
+></DIV
+></DIV
+></BODY
+></HTML
+> \ No newline at end of file
diff --git a/docs/htmldocs/Samba-HOWTO-Collection.html b/docs/htmldocs/Samba-HOWTO-Collection.html
deleted file mode 100644
index 8334ef82f3..0000000000
--- a/docs/htmldocs/Samba-HOWTO-Collection.html
+++ /dev/null
@@ -1,9515 +0,0 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>SAMBA Project Documentation</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"><meta name="description" content="
-This book is a collection of HOWTOs added to Samba documentation over the years.
-Samba is always under development, and so is its' documentation. This release of the
-documentation represents a major revision or layout as well as contents.
-The most recent version of this document can be found at
-http://www.samba.org/
-on the &quot;Documentation&quot; page. Please send updates to
-Jelmer Venrooij,
-John Terpstra or
-Gerald (Jerry) Carter.
-
-The Samba-Team would like to express sincere thanks to the many people who have with
-or without their knowledge contributed to this update. The size and scope of this
-project would not have been possible without significant community contribution. A not
-insignificant number of ideas for inclusion (if not content itself) has been obtained
-from a number of Unofficial HOWTOs - to each such author a big &quot;Thank-you&quot; is also offered.
-Please keep publishing your Unofficial HOWTO's - they are a source of inspiration and
-application knowledge that is most to be desired by many Samba users and administrators.
-"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="book" lang="en"><div class="titlepage"><div><h1 class="title"><a name="Samba-HOWTO-Collection"></a>SAMBA Project Documentation</h1></div><div><div class="author"><h3 class="author">SAMBA Team</h3><div class="affiliation"><div class="address"><p><tt>&lt;<a href="mailto:samba@samba.org">samba@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="legalnotice"><p>
-This documentation is distributed under the GNU General Public License (GPL)
-version 2. A copy of the license is included with the Samba source
-distribution. A copy can be found on-line at <a href="http://www.fsf.org/licenses/gpl.txt" target="_top">http://www.fsf.org/licenses/gpl.txt</a>
-</p></div></div><div><p class="pubdate">Monday April 21, 2003</p></div><div><div class="abstract"><p class="title"><b>Abstract</b></p><p>
-This book is a collection of HOWTOs added to Samba documentation over the years.
-Samba is always under development, and so is its' documentation. This release of the
-documentation represents a major revision or layout as well as contents.
-The most recent version of this document can be found at
-<a href="http://www.samba.org/" target="_top">http://www.samba.org/</a>
-on the &quot;Documentation&quot; page. Please send updates to
-<a href="mailto:jelmer@samba.org" target="_top">Jelmer Venrooij</a>,
-<a href="mailto:jht@samba.org" target="_top">John Terpstra</a> or
-<a href="mailto:jerry@samba.org" target="_top">Gerald (Jerry) Carter</a>.
-</p><p>
-The Samba-Team would like to express sincere thanks to the many people who have with
-or without their knowledge contributed to this update. The size and scope of this
-project would not have been possible without significant community contribution. A not
-insignificant number of ideas for inclusion (if not content itself) has been obtained
-from a number of Unofficial HOWTOs - to each such author a big &quot;Thank-you&quot; is also offered.
-Please keep publishing your Unofficial HOWTO's - they are a source of inspiration and
-application knowledge that is most to be desired by many Samba users and administrators.
-</p></div></div><hr></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt>I. <a href="#introduction">General Installation</a></dt><dd><dl><dt>1. <a href="#IntroSMB">Introduction to Samba</a></dt><dd><dl><dt><a href="#id2794048">Background</a></dt><dt><a href="#id2794106">Terminology</a></dt><dt><a href="#id2795149">Related Projects</a></dt><dt><a href="#id2845311">SMB Methodology</a></dt><dt><a href="#id2790901">Additional Resources</a></dt><dt><a href="#id2793926">Epilogue</a></dt><dt><a href="#id2844986">Miscellaneous</a></dt></dl></dd><dt>2. <a href="#install">How to Install and Test SAMBA</a></dt><dd><dl><dt><a href="#id2844847">Obtaining and installing samba</a></dt><dt><a href="#id2845201">Configuring samba</a></dt><dd><dl><dt><a href="#id2844744">Editing the smb.conf file</a></dt><dt><a href="#id2858916">SWAT</a></dt></dl></dd><dt><a href="#id2858954">Try listing the shares available on your
- server</a></dt><dt><a href="#id2859005">Try connecting with the unix client</a></dt><dt><a href="#id2859108">Try connecting from a DOS, WfWg, Win9x, WinNT,
- Win2k, OS/2, etc... client</a></dt><dt><a href="#id2859169">What If Things Don't Work?</a></dt></dl></dd></dl></dd><dt>II. <a href="#type">Server Configuration Basics</a></dt><dd><dl><dt>3. <a href="#ServerType">Nomenclature of Server Types</a></dt><dd><dl><dt><a href="#id2845139">Stand Alone Server</a></dt><dt><a href="#id2859402">Domain Member Server</a></dt><dt><a href="#id2859442">Domain Controller</a></dt><dd><dl><dt><a href="#id2859458">Domain Controller Types</a></dt></dl></dd></dl></dd><dt>4. <a href="#securitylevels">Samba as Stand-Alone Server</a></dt><dd><dl><dt><a href="#id2859216">User and Share security level</a></dt><dd><dl><dt><a href="#id2859238">User Level Security</a></dt><dt><a href="#id2859720">Share Level Security</a></dt><dt><a href="#id2859774">Server Level Security</a></dt><dt><a href="#id2860095">Domain Level Security</a></dt><dt><a href="#id2860234">ADS Level Security</a></dt></dl></dd></dl></dd><dt>5. <a href="#samba-pdc">
-Samba as an NT4 or Win2k Primary Domain Controller
-</a></dt><dd><dl><dt><a href="#id2859583">Prerequisite Reading</a></dt><dt><a href="#id2859607">
-Background
-</a></dt><dt><a href="#id2860563">Configuring the Samba Domain Controller</a></dt><dt><a href="#id2860863">Creating Machine Trust Accounts and Joining Clients to the Domain</a></dt><dd><dl><dt><a href="#id2861132">Manual Creation of Machine Trust Accounts</a></dt><dt><a href="#id2861366">&quot;On-the-Fly&quot; Creation of Machine Trust Accounts</a></dt><dt><a href="#id2861423">Joining the Client to the Domain</a></dt></dl></dd><dt><a href="#id2861529">Common Problems and Errors</a></dt><dd><dl><dt><a href="#id2861536">I cannot include a '$' in a machine name</a></dt><dt><a href="#id2861574">I get told &quot;You already have a connection to the Domain....&quot;
-or &quot;Cannot join domain, the credentials supplied conflict with an
-existing set..&quot; when creating a machine trust account.</a></dt><dt><a href="#id2861621">The system can not log you on (C000019B)....</a></dt><dt><a href="#id2861672">The machine trust account for this computer either does not
-exist or is not accessible.</a></dt><dt><a href="#id2861721">When I attempt to login to a Samba Domain from a NT4/W2K workstation,
-I get a message about my account being disabled.</a></dt></dl></dd><dt><a href="#id2861746">Domain Control for Windows 9x/ME</a></dt><dd><dl><dt><a href="#id2861910">Configuration Instructions: Network Logons</a></dt></dl></dd></dl></dd><dt>6. <a href="#samba-bdc">
-Samba Backup Domain Controller to Samba Domain Control
-</a></dt><dd><dl><dt><a href="#id2845056">Prerequisite Reading</a></dt><dt><a href="#id2860294">Background</a></dt><dt><a href="#id2862166">What qualifies a Domain Controller on the network?</a></dt><dd><dl><dt><a href="#id2862187">How does a Workstation find its domain controller?</a></dt><dt><a href="#id2862212">When is the PDC needed?</a></dt></dl></dd><dt><a href="#id2862231">Can Samba be a Backup Domain Controller to an NT PDC?</a></dt><dt><a href="#id2862264">How do I set up a Samba BDC?</a></dt><dd><dl><dt><a href="#id2862361">How do I replicate the smbpasswd file?</a></dt><dt><a href="#id2862390">Can I do this all with LDAP?</a></dt></dl></dd></dl></dd><dt>7. <a href="#ADS">Samba as a ADS domain member</a></dt><dd><dl><dt><a href="#id2862021">Setup your smb.conf</a></dt><dt><a href="#id2862571">Setup your /etc/krb5.conf</a></dt><dt><a href="#ads-create-machine-account">Create the computer account</a></dt><dd><dl><dt><a href="#id2862765">Possible errors</a></dt></dl></dd><dt><a href="#ads-test-server">Test your server setup</a></dt><dt><a href="#ads-test-smbclient">Testing with smbclient</a></dt><dt><a href="#id2862919">Notes</a></dt></dl></dd><dt>8. <a href="#domain-member">Samba as a NT4 or Win2k domain member</a></dt><dd><dl><dt><a href="#id2862413">Joining an NT Domain with Samba 3.0</a></dt><dt><a href="#id2863318">Why is this better than security = server?</a></dt></dl></dd></dl></dd><dt>III. <a href="#optional">Advanced Configuration</a></dt><dd><dl><dt>9. <a href="#NetworkBrowsing">Samba / MS Windows Network Browsing Guide</a></dt><dd><dl><dt><a href="#id2862996">What is Browsing?</a></dt><dt><a href="#id2863646">Discussion</a></dt><dt><a href="#id2863809">How Browsing Functions</a></dt><dd><dl><dt><a href="#id2863936">Setting up WORKGROUP Browsing</a></dt><dt><a href="#id2864124">Setting up DOMAIN Browsing</a></dt><dt><a href="#browse-force-master">Forcing samba to be the master</a></dt><dt><a href="#id2864390">Making samba the domain master</a></dt><dt><a href="#id2864538">Note about broadcast addresses</a></dt><dt><a href="#id2864555">Multiple interfaces</a></dt><dt><a href="#id2864584">Use of the Remote Announce parameter</a></dt><dt><a href="#id2864695">Use of the Remote Browse Sync parameter</a></dt></dl></dd><dt><a href="#id2864763">WINS - The Windows Internetworking Name Server</a></dt><dd><dl><dt><a href="#id2863586">Setting up a WINS server</a></dt><dt><a href="#id2865218">WINS Replication</a></dt><dt><a href="#id2865243">Static WINS Entries</a></dt></dl></dd><dt><a href="#id2865274">Helpful Hints</a></dt><dd><dl><dt><a href="#id2865287">Windows Networking Protocols</a></dt><dt><a href="#id2865354">Name Resolution Order</a></dt></dl></dd><dt><a href="#id2865470">Technical Overview of browsing</a></dt><dd><dl><dt><a href="#id2865517">Browsing support in samba</a></dt><dt><a href="#id2865624">Problem resolution</a></dt><dt><a href="#id2865703">Browsing across subnets</a></dt></dl></dd></dl></dd><dt>10. <a href="#passdb">User information database</a></dt><dd><dl><dt><a href="#id2866099">Introduction</a></dt><dt><a href="#id2866152">Important Notes About Security</a></dt><dd><dl><dt><a href="#id2866314">Advantages of SMB Encryption</a></dt><dt><a href="#id2866353">Advantages of non-encrypted passwords</a></dt></dl></dd><dt><a href="#id2866388">The smbpasswd Command</a></dt><dt><a href="#id2866568">Plain text</a></dt><dt><a href="#id2866597">TDB</a></dt><dt><a href="#id2866613">LDAP</a></dt><dd><dl><dt><a href="#id2866621">Introduction</a></dt><dt><a href="#id2866721">Encrypted Password Database</a></dt><dt><a href="#id2866860">Supported LDAP Servers</a></dt><dt><a href="#id2866898">Schema and Relationship to the RFC 2307 posixAccount</a></dt><dt><a href="#id2867008">Configuring Samba with LDAP</a></dt><dt><a href="#id2867304">Accounts and Groups management</a></dt><dt><a href="#id2867341">Security and sambaAccount</a></dt><dt><a href="#id2867456">LDAP specials attributes for sambaAccounts</a></dt><dt><a href="#id2867737">Example LDIF Entries for a sambaAccount</a></dt></dl></dd><dt><a href="#id2867793">MySQL</a></dt><dd><dl><dt><a href="#id2867800">Creating the database</a></dt><dt><a href="#id2867854">Configuring</a></dt><dt><a href="#id2867999">Using plaintext passwords or encrypted password</a></dt><dt><a href="#id2868029">Getting non-column data from the table</a></dt></dl></dd><dt><a href="#id2868072">XML</a></dt></dl></dd><dt>11. <a href="#unix-permissions">UNIX Permission Bits and Windows NT Access Control Lists</a></dt><dd><dl><dt><a href="#id2865054">Viewing and changing UNIX permissions using the NT
- security dialogs</a></dt><dt><a href="#id2864937">How to view file security on a Samba share</a></dt><dt><a href="#id2868280">Viewing file ownership</a></dt><dt><a href="#id2868401">Viewing file or directory permissions</a></dt><dd><dl><dt><a href="#id2868484">File Permissions</a></dt><dt><a href="#id2868587">Directory Permissions</a></dt></dl></dd><dt><a href="#id2868637">Modifying file or directory permissions</a></dt><dt><a href="#id2868797">Interaction with the standard Samba create mask
- parameters</a></dt><dt><a href="#id2869113">Interaction with the standard Samba file attribute
- mapping</a></dt></dl></dd><dt>12. <a href="#groupmapping">Configuring Group Mapping</a></dt><dt>13. <a href="#printing">Printing Support</a></dt><dd><dl><dt><a href="#id2869498">Introduction</a></dt><dt><a href="#id2869614">Configuration</a></dt><dd><dl><dt><a href="#id2869661">Creating [print$]</a></dt><dt><a href="#id2869893">Setting Drivers for Existing Printers</a></dt><dt><a href="#id2869992">Support a large number of printers</a></dt><dt><a href="#id2870099">Adding New Printers via the Windows NT APW</a></dt><dt><a href="#id2870231">Samba and Printer Ports</a></dt></dl></dd><dt><a href="#id2869233">The Imprints Toolset</a></dt><dd><dl><dt><a href="#id2869259">What is Imprints?</a></dt><dt><a href="#id2870336">Creating Printer Driver Packages</a></dt><dt><a href="#id2870355">The Imprints server</a></dt><dt><a href="#id2870379">The Installation Client</a></dt></dl></dd><dt><a href="#id2869340">Diagnosis</a></dt><dd><dl><dt><a href="#id2869347">Introduction</a></dt><dt><a href="#id2870552">Debugging printer problems</a></dt><dt><a href="#id2870619">What printers do I have?</a></dt><dt><a href="#id2870661">Setting up printcap and print servers</a></dt><dt><a href="#id2870795">Job sent, no output</a></dt><dt><a href="#id2871344">Job sent, strange output</a></dt><dt><a href="#id2871420">Raw PostScript printed</a></dt><dt><a href="#id2871438">Advanced Printing</a></dt><dt><a href="#id2871464">Real debugging</a></dt></dl></dd></dl></dd><dt>14. <a href="#CUPS-printing">CUPS Printing Support</a></dt><dd><dl><dt><a href="#id2871008">Introduction</a></dt><dt><a href="#id2871067">Configuring smb.conf for CUPS</a></dt><dt><a href="#id2871607">CUPS - RAW Print Through Mode</a></dt><dt><a href="#id2871091">CUPS as a network PostScript RIP</a></dt><dt><a href="#id2872272">Windows Terminal Servers (WTS) as CUPS clients</a></dt><dt><a href="#id2872314">Setting up CUPS for driver download</a></dt><dt><a href="#id2872401">Sources of CUPS drivers / PPDs</a></dt><dd><dl><dt><a href="#id2872566">cupsaddsmb</a></dt></dl></dd><dt><a href="#id2872915">The CUPS Filter Chains</a></dt><dt><a href="#id2873302">CUPS Print Drivers and Devices</a></dt><dd><dl><dt><a href="#id2873339">Further printing steps</a></dt></dl></dd><dt><a href="#id2873758">Limiting the number of pages users can print</a></dt><dt><a href="#id2874367">Advanced Postscript Printing from MS Windows</a></dt><dt><a href="#id2874473">Auto-Deletion of CUPS spool files</a></dt></dl></dd><dt>15. <a href="#winbind">Unified Logons between Windows NT and UNIX using Winbind</a></dt><dd><dl><dt><a href="#id2874714">Abstract</a></dt><dt><a href="#id2874743">Introduction</a></dt><dt><a href="#id2874814">What Winbind Provides</a></dt><dd><dl><dt><a href="#id2872076">Target Uses</a></dt></dl></dd><dt><a href="#id2872107">How Winbind Works</a></dt><dd><dl><dt><a href="#id2872135">Microsoft Remote Procedure Calls</a></dt><dt><a href="#id2872170">Microsoft Active Directory Services</a></dt><dt><a href="#id2872192">Name Service Switch</a></dt><dt><a href="#id2875280">Pluggable Authentication Modules</a></dt><dt><a href="#id2875352">User and Group ID Allocation</a></dt><dt><a href="#id2875387">Result Caching</a></dt></dl></dd><dt><a href="#id2875414">Installation and Configuration</a></dt><dd><dl><dt><a href="#id2875442">Introduction</a></dt><dt><a href="#id2875518">Requirements</a></dt><dt><a href="#id2875611">Testing Things Out</a></dt></dl></dd><dt><a href="#id2877210">Limitations</a></dt><dt><a href="#id2877264">Conclusion</a></dt></dl></dd><dt>16. <a href="#AdvancedNetworkManagement">Advanced Network Manangement</a></dt><dd><dl><dt><a href="#id2875143">Configuring Samba Share Access Controls</a></dt><dd><dl><dt><a href="#id2874905">Share Permissions Management</a></dt></dl></dd><dt><a href="#id2874974">Remote Server Administration</a></dt><dt><a href="#id2875057">Network Logon Script Magic</a></dt><dd><dl><dt><a href="#id2877889">Adding printers without user intervention</a></dt></dl></dd></dl></dd><dt>17. <a href="#PolicyMgmt">System and Account Policies</a></dt><dd><dl><dt><a href="#id2877672">Creating and Managing System Policies</a></dt><dd><dl><dt><a href="#id2877925">Windows 9x/Me Policies</a></dt><dt><a href="#id2878014">Windows NT4 Style Policy Files</a></dt><dt><a href="#id2878140">MS Windows 200x / XP Professional Policies</a></dt></dl></dd><dt><a href="#id2878344">Managing Account/User Policies</a></dt><dd><dl><dt><a href="#id2878457">With Windows NT4/200x</a></dt><dt><a href="#id2878478">With a Samba PDC</a></dt></dl></dd><dt><a href="#id2878502">System Startup and Logon Processing Overview</a></dt></dl></dd><dt>18. <a href="#ProfileMgmt">Desktop Profile Management</a></dt><dd><dl><dt><a href="#id2877599">Roaming Profiles</a></dt><dd><dl><dt><a href="#id2877483">Samba Configuration for Profile Handling</a></dt><dt><a href="#id2879080">Windows Client Profile Configuration Information</a></dt><dt><a href="#id2879695">Sharing Profiles between W9x/Me and NT4/200x/XP workstations</a></dt><dt><a href="#id2879742">Profile Migration from Windows NT4/200x Server to Samba</a></dt></dl></dd><dt><a href="#id2879925">Mandatory profiles</a></dt><dt><a href="#id2879970">Creating/Managing Group Profiles</a></dt><dt><a href="#id2880011">Default Profile for Windows Users</a></dt><dd><dl><dt><a href="#id2880040">MS Windows 9x/Me</a></dt><dt><a href="#id2880129">MS Windows NT4 Workstation</a></dt><dt><a href="#id2880513">MS Windows 200x/XP</a></dt></dl></dd></dl></dd><dt>19. <a href="#InterdomainTrusts">Interdomain Trust Relationships</a></dt><dd><dl><dt><a href="#id2878684">Trust Relationship Background</a></dt><dt><a href="#id2881006">Native MS Windows NT4 Trusts Configuration</a></dt><dd><dl><dt><a href="#id2881019">NT4 as the Trusting Domain (ie. creating the trusted account)</a></dt><dt><a href="#id2881063">NT4 as the Trusted Domain (ie. creating trusted account's password)</a></dt></dl></dd><dt><a href="#id2881087">Configuring Samba NT-style Domain Trusts</a></dt><dd><dl><dt><a href="#id2881114">Samba-3 as the Trusting Domain</a></dt><dt><a href="#id2881210">Samba-3 as the Trusted Domain</a></dt></dl></dd></dl></dd><dt>20. <a href="#pam">PAM Configuration for Centrally Managed Authentication</a></dt><dd><dl><dt><a href="#id2880956">Samba and PAM</a></dt><dd><dl><dt><a href="#id2881738">PAM Configuration in smb.conf</a></dt><dt><a href="#id2881795">Password Synchronisation using pam_smbpass.so</a></dt></dl></dd><dt><a href="#id2882047">Distributed Authentication</a></dt></dl></dd><dt>21. <a href="#VFS">Stackable VFS modules</a></dt><dd><dl><dt><a href="#id2881331">Introduction and configuration</a></dt><dt><a href="#id2882249">Included modules</a></dt><dd><dl><dt><a href="#id2882256">audit</a></dt><dt><a href="#id2882295">extd_audit</a></dt><dt><a href="#id2882416">recycle</a></dt><dt><a href="#id2882554">netatalk</a></dt></dl></dd><dt><a href="#id2882592">VFS modules available elsewhere</a></dt><dd><dl><dt><a href="#id2882614">DatabaseFS</a></dt><dt><a href="#id2882669">vscan</a></dt></dl></dd></dl></dd><dt>22. <a href="#msdfs">Hosting a Microsoft Distributed File System tree on Samba</a></dt><dd><dl><dt><a href="#id2882214">Instructions</a></dt><dd><dl><dt><a href="#id2882961">Notes</a></dt></dl></dd></dl></dd><dt>23. <a href="#integrate-ms-networks">Integrating MS Windows networks with Samba</a></dt><dd><dl><dt><a href="#id2882745">Name Resolution in a pure Unix/Linux world</a></dt><dd><dl><dt><a href="#id2883178">/etc/hosts</a></dt><dt><a href="#id2883316">/etc/resolv.conf</a></dt><dt><a href="#id2883360">/etc/host.conf</a></dt><dt><a href="#id2883403">/etc/nsswitch.conf</a></dt></dl></dd><dt><a href="#id2883498">Name resolution as used within MS Windows networking</a></dt><dd><dl><dt><a href="#id2883030">The NetBIOS Name Cache</a></dt><dt><a href="#id2883069">The LMHOSTS file</a></dt><dt><a href="#id2883112">HOSTS file</a></dt><dt><a href="#id2883144">DNS Lookup</a></dt><dt><a href="#id2883156">WINS Lookup</a></dt></dl></dd></dl></dd><dt>24. <a href="#securing-samba">Securing Samba</a></dt><dd><dl><dt><a href="#id2883603">Introduction</a></dt><dt><a href="#id2883619">Using host based protection</a></dt><dt><a href="#id2884070">Using interface protection</a></dt><dt><a href="#id2884122">Using a firewall</a></dt><dt><a href="#id2884164">Using a IPC$ share deny</a></dt><dt><a href="#id2883724">NTLMv2 Security</a></dt><dt><a href="#id2883760">Upgrading Samba</a></dt></dl></dd><dt>25. <a href="#unicode">Unicode/Charsets</a></dt><dd><dl><dt><a href="#id2884358">What are charsets and unicode?</a></dt><dt><a href="#id2884428">Samba and charsets</a></dt><dt><a href="#id2884517">Conversion from old names</a></dt><dt><a href="#id2884562">Japanese charsets</a></dt></dl></dd><dt>26. <a href="#locking">File and Record Locking</a></dt><dd><dl><dt><a href="#id2884210">Discussion</a></dt><dt><a href="#id2884872">Samba Opportunistic Locking Control</a></dt><dt><a href="#id2884987">MS Windows Opportunistic Locking and Caching Controls</a></dt><dd><dl><dt><a href="#id2885212">Workstation Service Entries</a></dt><dt><a href="#id2885239">Server Service Entries</a></dt></dl></dd><dt><a href="#id2885320">Persistent Data Corruption</a></dt><dt><a href="#id2885350">Additional Reading</a></dt></dl></dd></dl></dd><dt>IV. <a href="#troubleshooting">Troubleshooting</a></dt><dd><dl><dt>27. <a href="#diagnosis">The samba checklist</a></dt><dd><dl><dt><a href="#id2884776">Introduction</a></dt><dt><a href="#id2884810">Assumptions</a></dt><dt><a href="#id2793401">The tests</a></dt><dt><a href="#id2886854">Still having troubles?</a></dt></dl></dd><dt>28. <a href="#problems">Analysing and solving samba problems</a></dt><dd><dl><dt><a href="#id2790687">Diagnostics tools</a></dt><dt><a href="#id2887096">Installing 'Network Monitor' on an NT Workstation or a Windows 9x box</a></dt><dt><a href="#id2887237">Useful URL's</a></dt><dt><a href="#id2887343">Getting help from the mailing lists</a></dt><dt><a href="#id2887497">How to get off the mailinglists</a></dt></dl></dd><dt>29. <a href="#bugreport">Reporting Bugs</a></dt><dd><dl><dt><a href="#id2887016">Introduction</a></dt><dt><a href="#id2886937">General info</a></dt><dt><a href="#id2887713">Debug levels</a></dt><dt><a href="#id2887849">Internal errors</a></dt><dt><a href="#id2887942">Attaching to a running process</a></dt><dt><a href="#id2887989">Patches</a></dt></dl></dd></dl></dd><dt>V. <a href="#Appendixes">Appendixes</a></dt><dd><dl><dt>30. <a href="#compiling">How to compile SAMBA</a></dt><dd><dl><dt><a href="#id2887580">Access Samba source code via CVS</a></dt><dd><dl><dt><a href="#id2887587">Introduction</a></dt><dt><a href="#id2887620">CVS Access to samba.org</a></dt></dl></dd><dt><a href="#id2888377">Accessing the samba sources via rsync and ftp</a></dt><dt><a href="#id2888418">Verifying Samba's PGP signature</a></dt><dt><a href="#id2888501">Building the Binaries</a></dt><dd><dl><dt><a href="#id2888639">Compiling samba with Active Directory support</a></dt></dl></dd><dt><a href="#id2888786">Starting the smbd and nmbd</a></dt><dd><dl><dt><a href="#id2888853">Starting from inetd.conf</a></dt><dt><a href="#id2889045">Alternative: starting it as a daemon</a></dt></dl></dd></dl></dd><dt>31. <a href="#NT4Migration">Migration from NT4 PDC to Samba-3 PDC</a></dt><dd><dl><dt><a href="#id2888159">Planning and Getting Started</a></dt><dd><dl><dt><a href="#id2888028">Objectives</a></dt><dt><a href="#id2889725">Steps In Migration Process</a></dt></dl></dd><dt><a href="#id2889980">Migration Options</a></dt><dd><dl><dt><a href="#id2890062">Planning for Success</a></dt><dt><a href="#id2890304">Samba Implementation Choices</a></dt></dl></dd></dl></dd><dt>32. <a href="#Portability">Portability</a></dt><dd><dl><dt><a href="#id2889273">HPUX</a></dt><dt><a href="#id2889171">SCO Unix</a></dt><dt><a href="#id2889194">DNIX</a></dt><dt><a href="#id2890671">RedHat Linux Rembrandt-II</a></dt><dt><a href="#id2890709">AIX</a></dt><dd><dl><dt><a href="#id2890716">Sequential Read Ahead</a></dt></dl></dd><dt><a href="#id2890741">Solaris</a></dt><dd><dl><dt><a href="#id2890748">Locking improvements</a></dt><dt><a href="#winbind-solaris9">Winbind on Solaris 9</a></dt></dl></dd></dl></dd><dt>33. <a href="#Other-Clients">Samba and other CIFS clients</a></dt><dd><dl><dt><a href="#id2890402">Macintosh clients?</a></dt><dt><a href="#id2890976">OS2 Client</a></dt><dd><dl><dt><a href="#id2890983">How can I configure OS/2 Warp Connect or
- OS/2 Warp 4 as a client for Samba?</a></dt><dt><a href="#id2891066">How can I configure OS/2 Warp 3 (not Connect),
- OS/2 1.2, 1.3 or 2.x for Samba?</a></dt><dt><a href="#id2891126">Are there any other issues when OS/2 (any version)
- is used as a client?</a></dt><dt><a href="#id2891155">How do I get printer driver download working
- for OS/2 clients?</a></dt></dl></dd><dt><a href="#id2891218">Windows for Workgroups</a></dt><dd><dl><dt><a href="#id2891226">Use latest TCP/IP stack from Microsoft</a></dt><dt><a href="#id2891257">Delete .pwl files after password change</a></dt><dt><a href="#id2891287">Configure WfW password handling</a></dt><dt><a href="#id2891313">Case handling of passwords</a></dt><dt><a href="#id2891344">Use TCP/IP as default protocol</a></dt><dt><a href="#id2891361">Speed improvement</a></dt></dl></dd><dt><a href="#id2891388">Windows '95/'98</a></dt><dd><dl><dt><a href="#id2891458">Speed improvement</a></dt></dl></dd><dt><a href="#id2891475">Windows 2000 Service Pack 2</a></dt><dt><a href="#id2891585">Windows NT 3.1</a></dt></dl></dd><dt>34. <a href="#SWAT">SWAT - The Samba Web Admininistration Tool</a></dt><dd><dl><dt><a href="#id2890961">SWAT Features and Benefits</a></dt><dd><dl><dt><a href="#id2890837">Enabling SWAT for use</a></dt><dt><a href="#id2891873">Securing SWAT through SSL</a></dt><dt><a href="#id2891946">The SWAT Home Page</a></dt><dt><a href="#id2892010">Global Settings</a></dt><dt><a href="#id2892118">Share Settings</a></dt><dt><a href="#id2892167">Printers Settings</a></dt><dt><a href="#id2892216">The SWAT Wizard</a></dt><dt><a href="#id2892261">The Status Page</a></dt><dt><a href="#id2892300">The View Page</a></dt><dt><a href="#id2892316">The Password Change Page</a></dt></dl></dd></dl></dd><dt>35. <a href="#speed">Samba performance issues</a></dt><dd><dl><dt><a href="#id2891608">Comparisons</a></dt><dt><a href="#id2891653">Socket options</a></dt><dt><a href="#id2892541">Read size</a></dt><dt><a href="#id2892584">Max xmit</a></dt><dt><a href="#id2892637">Log level</a></dt><dt><a href="#id2892660">Read raw</a></dt><dt><a href="#id2892717">Write raw</a></dt><dt><a href="#id2892759">Slow Logins</a></dt><dt><a href="#id2892781">Client tuning</a></dt></dl></dd></dl></dd></dl></div><div class="list-of-tables"><p><b>List of Tables</b></p><dl><dt>21.1. <a href="#id2882333">Extended Auditing Log Information</a></dt><dt>31.1. <a href="#id2889997">The 3 Major Site Types</a></dt><dt>31.2. <a href="#id2890135">Nature of the Conversion Choices</a></dt></dl></div><div class="part" lang="en"><div class="titlepage"><div><h1 class="title"><a name="introduction"></a>General Installation</h1></div></div><div class="partintro" lang="en"><div><div><h1 class="title"><a name="id2789774"></a>Preparing Samba for Configuration</h1></div></div><p>This section of the Samba-HOWTO-Collection contains general info on how to install samba
-and how to configure the parts of samba you will most likely need.
-PLEASE read this.</p><div class="toc"><p><b>Table of Contents</b></p><dl><dt>1. <a href="#IntroSMB">Introduction to Samba</a></dt><dd><dl><dt><a href="#id2794048">Background</a></dt><dt><a href="#id2794106">Terminology</a></dt><dt><a href="#id2795149">Related Projects</a></dt><dt><a href="#id2845311">SMB Methodology</a></dt><dt><a href="#id2790901">Additional Resources</a></dt><dt><a href="#id2793926">Epilogue</a></dt><dt><a href="#id2844986">Miscellaneous</a></dt></dl></dd><dt>2. <a href="#install">How to Install and Test SAMBA</a></dt><dd><dl><dt><a href="#id2844847">Obtaining and installing samba</a></dt><dt><a href="#id2845201">Configuring samba</a></dt><dd><dl><dt><a href="#id2844744">Editing the smb.conf file</a></dt><dt><a href="#id2858916">SWAT</a></dt></dl></dd><dt><a href="#id2858954">Try listing the shares available on your
- server</a></dt><dt><a href="#id2859005">Try connecting with the unix client</a></dt><dt><a href="#id2859108">Try connecting from a DOS, WfWg, Win9x, WinNT,
- Win2k, OS/2, etc... client</a></dt><dt><a href="#id2859169">What If Things Don't Work?</a></dt></dl></dd></dl></div></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="IntroSMB"></a>Chapter1.Introduction to Samba</h2></div><div><div class="author"><h3 class="author">David Lechnyr</h3><div class="affiliation"><span class="orgname">Unofficial HOWTO<br></span><div class="address"><p><tt>&lt;<a href="mailto:david@lechnyr.com">david@lechnyr.com</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate">April 14, 2003</p></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2794048">Background</a></dt><dt><a href="#id2794106">Terminology</a></dt><dt><a href="#id2795149">Related Projects</a></dt><dt><a href="#id2845311">SMB Methodology</a></dt><dt><a href="#id2790901">Additional Resources</a></dt><dt><a href="#id2793926">Epilogue</a></dt><dt><a href="#id2844986">Miscellaneous</a></dt></dl></div><p><span class="emphasis"><em>
-&quot;If you understand what you're doing, you're not learning anything.&quot;
--- Anonymous
-</em></span></p><p>
-Samba is a file and print server for Windows-based clients using TCP/IP as the underlying
-transport protocol. In fact, it can support any SMB/CIFS-enabled client. One of Samba's big
-strengths is that you can use it to blend your mix of Windows and Linux machines together
-without requiring a separate Windows NT/2000/2003 Server. Samba is actively being developed
-by a global team of about 30 active programmers and was originally developed by Andrew Tridgell.
-</p><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2794048"></a>Background</h2></div></div><p>
-Once long ago, there was a buzzword referred to as DCE/RPC. This stood for Distributed
-Computing Environment/Remote Procedure Calls and conceptually was a good idea. It was
-originally developed by Apollo/HP as NCA 1.0 (Network Computing Architecture) and only
-ran over UDP. When there was a need to run it over TCP so that it would be compatible
-with DECnet 3.0, it was redesigned, submitted to The Open Group, and officially became
-known as DCE/RPC. Microsoft came along and decided, rather than pay $20 per seat to
-license this technology, to reimplement DCE/RPC themselves as MSRPC. From this, the
-concept continued in the form of SMB (Server Message Block, or the &quot;what&quot;) using the
-NetBIOS (Network Basic Input/Output System, or the &quot;how&quot;) compatibility layer. You can
-run SMB (i.e., transport) over several different protocols; many different implementations
-arose as a result, including NBIPX (NetBIOS over IPX, NwLnkNb, or NWNBLink) and NBT
-(NetBIOS over TCP/IP, or NetBT). As the years passed, NBT became the most common form
-of implementation until the advance of &quot;Direct-Hosted TCP&quot; -- the Microsoft marketing
-term for eliminating NetBIOS entirely and running SMB by itself across TCP port 445
-only. As of yet, direct-hosted TCP has yet to catch on.
-</p><p>
-Perhaps the best summary of the origins of SMB are voiced in the 1997 article titled, CIFS:
-Common Insecurities Fail Scrutiny:
-</p><p><span class="emphasis"><em>
-Several megabytes of NT-security archives, random whitepapers, RFCs, the CIFS spec, the Samba
-stuff, a few MS knowledge-base articles, strings extracted from binaries, and packet dumps have
-been dutifully waded through during the information-gathering stages of this project, and there
-are *still* many missing pieces... While often tedious, at least the way has been generously
-littered with occurrences of clapping hand to forehead and muttering 'crikey, what are they
-thinking?
-</em></span></p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2794106"></a>Terminology</h2></div></div><div class="itemizedlist"><ul type="disc"><li><p>
- SMB: Acronym for &quot;Server Message Block&quot;. This is Microsoft's file and printer sharing protocol.
- </p></li><li><p>
- CIFS: Acronym for &quot;Common Internet File System&quot;. Around 1996, Microsoft apparently
- decided that SMB needed the word &quot;Internet&quot; in it, so they changed it to CIFS.
- </p></li><li><p>
- Direct-Hosted: A method of providing file/printer sharing services over port 445/tcp
- only using DNS for name resolution instead of WINS.
- </p></li><li><p>
- IPC: Acronym for &quot;Inter-Process Communication&quot;. A method to communicate specific
- information between programs.
- </p></li><li><p>
- Marshalling: - A method of serializing (i.e., sequential ordering of) variable data
- suitable for transmission via a network connection or storing in a file. The source
- data can be re-created using a similar process called unmarshalling.
- </p></li><li><p>
- NetBIOS: Acronym for &quot;Network Basic Input/Output System&quot;. This is not a protocol;
- it is a method of communication across an existing protocol. This is a standard which
- was originally developed for IBM by Sytek in 1983. To exaggerate the analogy a bit,
- it can help to think of this in comparison your computer's BIOS -- it controls the
- essential functions of your input/output hardware -- whereas NetBIOS controls the
- essential functions of your input/output traffic via the network. Again, this is a bit
- of an exaggeration but it should help that paradigm shift. What is important to realize
- is that NetBIOS is a transport standard, not a protocol. Unfortunately, even technically
- brilliant people tend to interchange NetBIOS with terms like NetBEUI without a second
- thought; this will cause no end (and no doubt) of confusion.
- </p></li><li><p>
- NetBEUI: Acronym for the &quot;NetBIOS Extended User Interface&quot;. Unlike NetBIOS, NetBEUI
- is a protocol, not a standard. It is also not routable, so traffic on one side of a
- router will be unable to communicate with the other side. Understanding NetBEUI is
- not essential to deciphering SMB; however it helps to point out that it is not the
- same as NetBIOS and to improve your score in trivia at parties. NetBEUI was originally
- referred to by Microsoft as &quot;NBF&quot;, or &quot;The Windows NT NetBEUI Frame protocol driver&quot;.
- It is not often heard from these days.
- </p></li><li><p>
- NBT: Acronym for &quot;NetBIOS over TCP&quot;; also known as &quot;NetBT&quot;. Allows the continued use
- of NetBIOS traffic proxied over TCP/IP. As a result, NetBIOS names are made
- to IP addresses and NetBIOS name types are conceptually equivalent to TCP/IP ports.
- This is how file and printer sharing are accomplished in Windows 95/98/ME. They
- traditionally rely on three ports: NetBIOS Name Service (nbname) via UDP port 137,
- NetBIOS Datagram Service (nbdatagram) via UDP port 138, and NetBIOS Session Service
- (nbsession) via TCP port 139. All name resolution is done via WINS, NetBIOS broadcasts,
- and DNS. NetBIOS over TCP is documented in RFC 1001 (Concepts and methods) and RFC 1002
- (Detailed specifications).
- </p></li><li><p>
- W2K: Acronym for Windows 2000 Professional or Server
- </p></li><li><p>
- W3K: Acronym for Windows 2003 Server
- </p></li></ul></div><p>If you plan on getting help, make sure to subscribe to the Samba Mailing List (available at
-http://www.samba.org). Optionally, you could just search mailing.unix.samba at http://groups.google.com
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2795149"></a>Related Projects</h2></div></div><p>
-There are currently two network filesystem client projects for Linux that are directly
-related to Samba: SMBFS and CIFS VFS. These are both available in the Linux kernel itself.
-</p><div class="itemizedlist"><ul type="disc"><li><p>
- SMBFS (Server Message Block File System) allows you to mount SMB shares (the protocol
- that Microsoft Windows and OS/2 Lan Manager use to share files and printers
- over local networks) and access them just like any other Unix directory. This is useful
- if you just want to mount such filesystems without being a SMBFS server.
- </p></li><li><p>
- CIFS VFS (Common Internet File System Virtual File System) is the successor to SMBFS, and
- is being actively developed for the upcoming version of the Linux kernel. The intent of this module
- is to provide advanced network file system functionality including support for dfs (heirarchical
- name space), secure per-user session establishment, safe distributed caching (oplock),
- optional packet signing, Unicode and other internationalization improvements, and optional
- Winbind (nsswitch) integration.
- </p></li></ul></div><p>
-Again, it's important to note that these are implementations for client filesystems, and have
-nothing to do with acting as a file and print server for SMB/CIFS clients.
-</p><p>
-There are other Open Source CIFS client implementations, such as the jCIFS project
-(jcifs.samba.org) which provides an SMB client toolkit written in Java.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2845311"></a>SMB Methodology</h2></div></div><p>
-Traditionally, SMB uses UDP port 137 (NetBIOS name service, or netbios-ns),
-UDP port 138 (NetBIOS datagram service, or netbios-dgm), and TCP port 139 (NetBIOS
-session service, or netbios-ssn). Anyone looking at their network with a good
-packet sniffer will be amazed at the amount of traffic generated by just opening
-up a single file. In general, SMB sessions are established in the following order:
-</p><div class="itemizedlist"><ul type="disc"><li><p>
- &quot;TCP Connection&quot; - establish 3-way handshake (connection) to port 139/tcp
- or 445/tcp.
- </p></li><li><p>
- &quot;NetBIOS Session Request&quot; - using the following &quot;Calling Names&quot;: The local
- machine's NetBIOS name plus the 16th character 0x00; The server's NetBIOS
- name plus the 16th character 0x20
- </p></li><li><p>
- &quot;SMB Negotiate Protocol&quot; - determine the protocol dialect to use, which will
- be one of the following: PC Network Program 1.0 (Core) - share level security
- mode only; Microsoft Networks 1.03 (Core Plus) - share level security
- mode only; Lanman1.0 (LAN Manager 1.0) - uses Challenge/Response
- Authentication; Lanman2.1 (LAN Manager 2.1) - uses Challenge/Response
- Authentication; NT LM 0.12 (NT LM 0.12) - uses Challenge/Response
- Authentication
- </p></li><li><p>
- SMB Session Startup. Passwords are encrypted (or not) according to one of
- the following methods: Null (no encryption); Cleartext (no encryption); LM
- and NTLM; NTLM; NTLMv2
- </p></li><li><p>
- SMB Tree Connect: Connect to a share name (e.g., \\servername\share); Connect
- to a service type (e.g., IPC$ named pipe)
- </p></li></ul></div><p>
-A good way to examine this process in depth is to try out SecurityFriday's SWB program
-at http://www.securityfriday.com/ToolDownload/SWB/swb_doc.html. It allows you to
-walk through the establishment of a SMB/CIFS session step by step.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2790901"></a>Additional Resources</h2></div></div><div class="itemizedlist"><ul type="disc"><li><p>
- <a href="http://hr.uoregon.edu/davidrl/cifs.txt" target="_top">
- <span class="emphasis"><em>CIFS: Common Insecurities Fail Scrutiny</em></span> by &quot;Hobbit&quot;</a>
- </p></li><li><p>
- <a href="http://afr.com/it/2002/10/01/FFXDF43AP6D.html" target="_top">
- <span class="emphasis"><em>Doing the Samba on Windows</em></span> by Financial Review
- </a>
- </p></li><li><p>
- <a href="http://ubiqx.org/cifs/" target="_top">
- <span class="emphasis"><em>Implementing CIFS</em></span> by Christopher R. Hertel
- </a>
- </p></li><li><p>
- <a href="http://samba.anu.edu.au/cifs/docs/what-is-smb.html" target="_top">
- <span class="emphasis"><em>Just What Is SMB?</em></span> by Richard Sharpe
- </a>
- </p></li><li><p>
- <a href="http://www.linux-mag.com/1999-05/samba_01.html" target="_top">
- <span class="emphasis"><em>Opening Windows Everywhere</em></span> by Mike Warfield
- </a>
- </p></li><li><p>
- <a href="http://www.tldp.org/HOWTO/SMB-HOWTO.html" target="_top">
- <span class="emphasis"><em>SMB HOWTO</em></span> by David Wood
- </a>
- </p></li><li><p>
- <a href="http://www.phrack.org/phrack/60/p60-0x0b.txt" target="_top">
- <span class="emphasis"><em>SMB/CIFS by The Root</em></span> by &quot;ledin&quot;
- </a>
- </p></li><li><p>
- <a href="http://www.linux-mag.com/1999-09/samba_01.html" target="_top">
- <span class="emphasis"><em>The Story of Samba</em></span> by Christopher R. Hertel
- </a>
- </p></li><li><p>
- <a href="http://hr.uoregon.edu/davidrl/samba/" target="_top">
- <span class="emphasis"><em>The Unofficial Samba HOWTO</em></span> by David Lechnyr
- </a>
- </p></li><li><p>
- <a href="http://www.linux-mag.com/2001-05/smb_01.html" target="_top">
- <span class="emphasis"><em>Understanding the Network Neighborhood</em></span> by Christopher R. Hertel
- </a>
- </p></li><li><p>
- <a href="http://www.linux-mag.com/2002-02/samba_01.html" target="_top">
- <span class="emphasis"><em>Using Samba as a PDC</em></span> by Andrew Bartlett
- </a>
- </p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2793926"></a>Epilogue</h2></div></div><p><span class="emphasis"><em>
-&quot;What's fundamentally wrong is that nobody ever had any taste when they
-did it. Microsoft has been very much into making the user interface look good,
-but internally it's just a complete mess. And even people who program for Microsoft
-and who have had years of experience, just don't know how it works internally.
-Worse, nobody dares change it. Nobody dares to fix bugs because it's such a
-mess that fixing one bug might just break a hundred programs that depend on
-that bug. And Microsoft isn't interested in anyone fixing bugs -- they're interested
-in making money. They don't have anybody who takes pride in Windows 95 as an
-operating system.
-</em></span></p><p><span class="emphasis"><em>
-People inside Microsoft know it's a bad operating system and they still
-continue obviously working on it because they want to get the next version out
-because they want to have all these new features to sell more copies of the
-system.
-</em></span></p><p><span class="emphasis"><em>
-The problem with that is that over time, when you have this kind of approach,
-and because nobody understands it, because nobody REALLY fixes bugs (other than
-when they're really obvious), the end result is really messy. You can't trust
-it because under certain circumstances it just spontaneously reboots or just
-halts in the middle of something that shouldn't be strange. Normally it works
-fine and then once in a blue moon for some completely unknown reason, it's dead,
-and nobody knows why. Not Microsoft, not the experienced user and certainly
-not the completely clueless user who probably sits there shivering thinking
-&quot;What did I do wrong?&quot; when they didn't do anything wrong at all.
-</em></span></p><p><span class="emphasis"><em>
-That's what's really irritating to me.&quot;
-</em></span></p><p>--
-<a href="http://hr.uoregon.edu/davidrl/boot.txt" target="_top">Linus Torvalds, from an interview with BOOT Magazine, Sept 1998</a>
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2844986"></a>Miscellaneous</h2></div></div><p>
-This chapter was lovingly handcrafted on a Dell Latitude C400 laptop running Slackware Linux 9.0,
-in case anyone asks.
-</p><p>
-This chapter is Copyright 2003 David Lechnyr (david at lechnyr dot com).
-Permission is granted to copy, distribute and/or modify this document under the terms
-of the GNU Free Documentation License, Version 1.2 or any later version published by the Free
-Software Foundation. A copy of the license is available at http://www.gnu.org/licenses/fdl.txt.
-</p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="install"></a>Chapter2.How to Install and Test SAMBA</h2></div><div><div class="author"><h3 class="author">Andrew Tridgell</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt>&lt;<a href="mailto:tridge@samba.org">tridge@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author">Jelmer R. Vernooij</h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt>&lt;<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author">Karl Auer</h3></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2844847">Obtaining and installing samba</a></dt><dt><a href="#id2845201">Configuring samba</a></dt><dd><dl><dt><a href="#id2844744">Editing the smb.conf file</a></dt><dt><a href="#id2858916">SWAT</a></dt></dl></dd><dt><a href="#id2858954">Try listing the shares available on your
- server</a></dt><dt><a href="#id2859005">Try connecting with the unix client</a></dt><dt><a href="#id2859108">Try connecting from a DOS, WfWg, Win9x, WinNT,
- Win2k, OS/2, etc... client</a></dt><dt><a href="#id2859169">What If Things Don't Work?</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2844847"></a>Obtaining and installing samba</h2></div></div><p>Binary packages of samba are included in almost any Linux or
- Unix distribution. There are also some packages available at
- <a href="http://samba.org/" target="_top">the samba homepage</a>.
- </p><p>If you need to compile samba from source, check the
- <a href="#compiling" title="Chapter30.How to compile SAMBA">appropriate appendix chapter</a>.</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2845201"></a>Configuring samba</h2></div></div><p>Samba's configuration is stored in the smb.conf file,
- that usually resides in <tt>/etc/samba/smb.conf</tt>
- or <tt>/usr/local/samba/lib/smb.conf</tt>. You can either
- edit this file yourself or do it using one of the many graphical
- tools that are available, such as the web-based interface swat, that
- is included with samba.</p><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2844744"></a>Editing the <tt>smb.conf</tt> file</h3></div></div><p>There are sample configuration files in the examples
- subdirectory in the distribution. I suggest you read them
- carefully so you can see how the options go together in
- practice. See the man page for all the options.</p><p>The simplest useful configuration file would be
- something like this:</p><pre class="programlisting">
-[global]
- workgroup = MYGROUP
-
-[homes]
- guest ok = no
- read only = no
- </pre><p>which would allow connections by anyone with an
- account on the server, using either their login name or
- &quot;<b>homes</b>&quot; as the service name. (Note that I also set the
- workgroup that Samba is part of. See BROWSING.txt for details)</p><p>Make sure you put the <tt>smb.conf</tt> file in the same place
- you specified in the<tt>Makefile</tt> (the default is to
- look for it in <tt>/usr/local/samba/lib/</tt>).</p><p>For more information about security settings for the
- <b>[homes]</b> share please refer to the chapter
- <a href="#securing-samba" title="Chapter24.Securing Samba">Securing Samba</a>.</p><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2858862"></a>Test your config file with
- <b>testparm</b></h4></div></div><p>It's important that you test the validity of your
- <tt>smb.conf</tt> file using the testparm program.
- If testparm runs OK then it will list the loaded services. If
- not it will give an error message.</p><p>Make sure it runs OK and that the services look
- reasonable before proceeding. </p><p>Always run testparm again when you change
- <tt>smb.conf</tt>!</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2858916"></a>SWAT</h3></div></div><p>
- SWAT is a web-based interface that helps you configure samba.
- SWAT might not be available in the samba package on your platform,
- but in a separate package. Please read the swat manpage
- on compiling, installing and configuring swat from source.
- </p><p>To launch SWAT just run your favorite web browser and
- point it at &quot;http://localhost:901/&quot;. Replace <i><tt>localhost</tt></i> with the name of the computer you are running samba on if you
- are running samba on a different computer than your browser.</p><p>Note that you can attach to SWAT from any IP connected
- machine but connecting from a remote machine leaves your
- connection open to password sniffing as passwords will be sent
- in the clear over the wire. </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2858954"></a>Try listing the shares available on your
- server</h2></div></div><p><tt>$ </tt><b><tt>smbclient -L
- <i><tt>yourhostname</tt></i></tt></b></p><p>You should get back a list of shares available on
- your server. If you don't then something is incorrectly setup.
- Note that this method can also be used to see what shares
- are available on other LanManager clients (such as WfWg).</p><p>If you choose user level security then you may find
- that Samba requests a password before it will list the shares.
- See the <b>smbclient</b> man page for details. (you
- can force it to list the shares without a password by
- adding the option -U% to the command line. This will not work
- with non-Samba servers)</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2859005"></a>Try connecting with the unix client</h2></div></div><p><tt>$ </tt><b><tt>smbclient <i><tt>
- //yourhostname/aservice</tt></i></tt></b></p><p>Typically the <i><tt>yourhostname</tt></i>
- would be the name of the host where you installed smbd.
- The <i><tt>aservice</tt></i> is
- any service you have defined in the <tt>smb.conf</tt>
- file. Try your user name if you just have a <b>[homes]</b>
- section
- in <tt>smb.conf</tt>.</p><p>For example if your unix host is <i><tt>bambi</tt></i>
- and your login name is <i><tt>fred</tt></i> you would type:</p><p><tt>$ </tt><b><tt>smbclient //<i><tt>bambi</tt></i>/<i><tt>fred</tt></i>
- </tt></b></p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2859108"></a>Try connecting from a DOS, WfWg, Win9x, WinNT,
- Win2k, OS/2, etc... client</h2></div></div><p>Try mounting disks. eg:</p><p><tt>C:\WINDOWS\&gt; </tt><b><tt>net use d: \\servername\service
- </tt></b></p><p>Try printing. eg:</p><p><tt>C:\WINDOWS\&gt; </tt><b><tt>net use lpt1:
- \\servername\spoolservice</tt></b></p><p><tt>C:\WINDOWS\&gt; </tt><b><tt>print filename
- </tt></b></p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2859169"></a>What If Things Don't Work?</h2></div></div><p>Then you might read the file chapter
- <a href="#diagnosis" title="Chapter27.The samba checklist">Diagnosis</a> and the
- FAQ. If you are still stuck then try to follow
- the <a href="#problems" title="Chapter28.Analysing and solving samba problems">Analysing and Solving Problems chapter</a>
- Samba has been successfully installed at thousands of sites worldwide,
- so maybe someone else has hit your problem and has overcome it. </p></div></div></div><div class="part" lang="en"><div class="titlepage"><div><h1 class="title"><a name="type"></a>Server Configuration Basics</h1></div></div><div class="partintro" lang="en"><div><div><h1 class="title"><a name="id2845027"></a>First Steps in Server Configuration</h1></div></div><p>
-Samba can operate in various modes within SMB networks. This HOWTO section contains information on
-configuring samba to function as the type of server your network requires. Please read this
-section carefully.
-</p><div class="toc"><p><b>Table of Contents</b></p><dl><dt>3. <a href="#ServerType">Nomenclature of Server Types</a></dt><dd><dl><dt><a href="#id2845139">Stand Alone Server</a></dt><dt><a href="#id2859402">Domain Member Server</a></dt><dt><a href="#id2859442">Domain Controller</a></dt><dd><dl><dt><a href="#id2859458">Domain Controller Types</a></dt></dl></dd></dl></dd><dt>4. <a href="#securitylevels">Samba as Stand-Alone Server</a></dt><dd><dl><dt><a href="#id2859216">User and Share security level</a></dt><dd><dl><dt><a href="#id2859238">User Level Security</a></dt><dt><a href="#id2859720">Share Level Security</a></dt><dt><a href="#id2859774">Server Level Security</a></dt><dt><a href="#id2860095">Domain Level Security</a></dt><dt><a href="#id2860234">ADS Level Security</a></dt></dl></dd></dl></dd><dt>5. <a href="#samba-pdc">
-Samba as an NT4 or Win2k Primary Domain Controller
-</a></dt><dd><dl><dt><a href="#id2859583">Prerequisite Reading</a></dt><dt><a href="#id2859607">
-Background
-</a></dt><dt><a href="#id2860563">Configuring the Samba Domain Controller</a></dt><dt><a href="#id2860863">Creating Machine Trust Accounts and Joining Clients to the Domain</a></dt><dd><dl><dt><a href="#id2861132">Manual Creation of Machine Trust Accounts</a></dt><dt><a href="#id2861366">&quot;On-the-Fly&quot; Creation of Machine Trust Accounts</a></dt><dt><a href="#id2861423">Joining the Client to the Domain</a></dt></dl></dd><dt><a href="#id2861529">Common Problems and Errors</a></dt><dd><dl><dt><a href="#id2861536">I cannot include a '$' in a machine name</a></dt><dt><a href="#id2861574">I get told &quot;You already have a connection to the Domain....&quot;
-or &quot;Cannot join domain, the credentials supplied conflict with an
-existing set..&quot; when creating a machine trust account.</a></dt><dt><a href="#id2861621">The system can not log you on (C000019B)....</a></dt><dt><a href="#id2861672">The machine trust account for this computer either does not
-exist or is not accessible.</a></dt><dt><a href="#id2861721">When I attempt to login to a Samba Domain from a NT4/W2K workstation,
-I get a message about my account being disabled.</a></dt></dl></dd><dt><a href="#id2861746">Domain Control for Windows 9x/ME</a></dt><dd><dl><dt><a href="#id2861910">Configuration Instructions: Network Logons</a></dt></dl></dd></dl></dd><dt>6. <a href="#samba-bdc">
-Samba Backup Domain Controller to Samba Domain Control
-</a></dt><dd><dl><dt><a href="#id2845056">Prerequisite Reading</a></dt><dt><a href="#id2860294">Background</a></dt><dt><a href="#id2862166">What qualifies a Domain Controller on the network?</a></dt><dd><dl><dt><a href="#id2862187">How does a Workstation find its domain controller?</a></dt><dt><a href="#id2862212">When is the PDC needed?</a></dt></dl></dd><dt><a href="#id2862231">Can Samba be a Backup Domain Controller to an NT PDC?</a></dt><dt><a href="#id2862264">How do I set up a Samba BDC?</a></dt><dd><dl><dt><a href="#id2862361">How do I replicate the smbpasswd file?</a></dt><dt><a href="#id2862390">Can I do this all with LDAP?</a></dt></dl></dd></dl></dd><dt>7. <a href="#ADS">Samba as a ADS domain member</a></dt><dd><dl><dt><a href="#id2862021">Setup your smb.conf</a></dt><dt><a href="#id2862571">Setup your /etc/krb5.conf</a></dt><dt><a href="#ads-create-machine-account">Create the computer account</a></dt><dd><dl><dt><a href="#id2862765">Possible errors</a></dt></dl></dd><dt><a href="#ads-test-server">Test your server setup</a></dt><dt><a href="#ads-test-smbclient">Testing with smbclient</a></dt><dt><a href="#id2862919">Notes</a></dt></dl></dd><dt>8. <a href="#domain-member">Samba as a NT4 or Win2k domain member</a></dt><dd><dl><dt><a href="#id2862413">Joining an NT Domain with Samba 3.0</a></dt><dt><a href="#id2863318">Why is this better than security = server?</a></dt></dl></dd></dl></div></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="ServerType"></a>Chapter3.Nomenclature of Server Types</h2></div><div><div class="author"><h3 class="author">John H. Terpstra</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt>&lt;<a href="mailto:jht@samba.org">jht@samba.org</a>&gt;</tt></p></div></div></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2845139">Stand Alone Server</a></dt><dt><a href="#id2859402">Domain Member Server</a></dt><dt><a href="#id2859442">Domain Controller</a></dt><dd><dl><dt><a href="#id2859458">Domain Controller Types</a></dt></dl></dd></dl></div><p>Adminstrators of Microsoft networks often refer to there being three
-different type of servers:</p><div class="itemizedlist"><ul type="disc"><li><p>Stand Alone Server</p></li><li><p>Domain Member Server</p></li><li><p>Domain Controller</p><div class="itemizedlist"><ul type="circle"><li><p>Primary Domain Controller</p></li><li><p>Backup Domain Controller</p></li><li><p>ADS Domain Controller</p></li></ul></div></li></ul></div><p>A network administrator who is familiar with these terms and who
-wishes to migrate to or use Samba will want to know what these terms mean
-within a Samba context.</p><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2845139"></a>Stand Alone Server</h2></div></div><p>
-The term <span class="emphasis"><em>stand alone server</em></span> means that the server
-will provide local authentication and access control for all resources
-that are available from it. In general this means that there will be a
-local user database. In more technical terms, it means that resources
-on the machine will either be made available in either SHARE mode or in
-USER mode. SHARE mode and USER mode security are documented under
-discussions regarding &quot;security mode&quot;. The smb.conf configuration parameters
-that control security mode are: &quot;security = user&quot; and &quot;security = share&quot;.
-</p><p>
-No special action is needed other than to create user accounts. Stand-alone
-servers do NOT provide network logon services, meaning that machines that
-use this server do NOT perform a domain logon but instead make use only of
-the MS Windows logon which is local to the MS Windows workstation/server.
-</p><p>
-Samba tends to blur the distinction a little in respect of what is
-a stand alone server. This is because the authentication database may be
-local or on a remote server, even if from the samba protocol perspective
-the samba server is NOT a member of a domain security context.
-</p><p>
-Through the use of PAM (Pluggable Authentication Modules) and nsswitch
-(the name service switcher) the source of authentication may reside on
-another server. We would be inclined to call this the authentication server.
-This means that the samba server may use the local Unix/Linux system
-password database (/etc/passwd or /etc/shadow), may use a local smbpasswd
-file (/etc/samba/smbpasswd or /usr/local/samba/lib/private/smbpasswd), or
-may use an LDAP back end, or even via PAM and Winbind another CIFS/SMB
-server for authentication.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2859402"></a>Domain Member Server</h2></div></div><p>
-This mode of server operation involves the samba machine being made a member
-of a domain security context. This means by definition that all user authentication
-will be done from a centrally defined authentication regime. The authentication
-regime may come from an NT3/4 style (old domain technology) server, or it may be
-provided from an Active Directory server (ADS) running on MS Windows 2000 or later.
-</p><p><span class="emphasis"><em>
-Of course it should be clear that the authentication back end itself could be from any
-distributed directory architecture server that is supported by Samba. This can be
-LDAP (from OpenLDAP), or Sun's iPlanet, of NetWare Directory Server, etc.
-</em></span></p><p>
-Please refer to the section on Howto configure Samba as a Primary Domain Controller
-and for more information regarding how to create a domain machine account for a
-domain member server as well as for information regarding how to enable the samba
-domain member machine to join the domain and to be fully trusted by it.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2859442"></a>Domain Controller</h2></div></div><p>
-Over the years public perceptions of what Domain Control really is has taken on an
-almost mystical nature. Before we branch into a brief overview of what Domain Control
-is the following types of controller are known:
-</p><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2859458"></a>Domain Controller Types</h3></div></div><table class="simplelist" border="0" summary="Simple list"><tr><td>Primary Domain Controller</td></tr><tr><td>Backup Domain Controller</td></tr><tr><td>ADS Domain Controller</td></tr></table><p>
-The <span class="emphasis"><em>Primary Domain Controller</em></span> or PDC plays an important role in the MS
-Windows NT3 and NT4 Domain Control architecture, but not in the manner that so many
-expect. The PDC seeds the Domain Control database (a part of the Windows registry) and
-it plays a key part in synchronisation of the domain authentication database.
-</p><p>
-New to Samba-3.0.0 is the ability to use a back-end file that holds the same type of data as
-the NT4 style SAM (Security Account Manager) database (one of the registry files).
-The samba-3.0.0 SAM can be specified via the smb.conf file parameter &quot;passwd backend&quot; and
-valid options include <span class="emphasis"><em> smbpasswd tdbsam ldapsam nisplussam plugin unixsam</em></span>.
-The smbpasswd, tdbsam and ldapsam options can have a &quot;_nua&quot; suffix to indicate that No Unix
-Accounts need to be created. In other words, the Samba SAM will be independant of Unix/Linux
-system accounts, provided a uid range is defined from which SAM accounts can be created.
-</p><p>
-The <span class="emphasis"><em>Backup Domain Controller</em></span> or BDC plays a key role in servicing network
-authentication requests. The BDC is biased to answer logon requests so that on a network segment
-that has a BDC and a PDC the BDC will be most likely to service network logon requests. The PDC will
-answer network logon requests when the BDC is too busy (high load). A BDC can be promoted to
-a PDC. If the PDC is on line at the time that the BDC is promoted to PDC the previous PDC is
-automatically demoted to a BDC.
-</p><p>
-At this time Samba is NOT capable of acting as an <span class="emphasis"><em>ADS Domain Controller</em></span>.
-</p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="securitylevels"></a>Chapter4.Samba as Stand-Alone Server</h2></div><div><div class="author"><h3 class="author">Andrew Tridgell</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt>&lt;<a href="mailto:tridge@samba.org">tridge@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author">Jelmer R. Vernooij</h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt>&lt;<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</tt></p></div></div></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2859216">User and Share security level</a></dt><dd><dl><dt><a href="#id2859238">User Level Security</a></dt><dt><a href="#id2859720">Share Level Security</a></dt><dt><a href="#id2859774">Server Level Security</a></dt><dt><a href="#id2860095">Domain Level Security</a></dt><dt><a href="#id2860234">ADS Level Security</a></dt></dl></dd></dl></div><p>
-In this section the function and purpose of Samba's <span class="emphasis"><em>security</em></span>
-modes are described.
-</p><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2859216"></a>User and Share security level</h2></div></div><p>
-A SMB server tells the client at startup what &quot;security level&quot; it is
-running. There are two options &quot;share level&quot; and &quot;user level&quot;. Which
-of these two the client receives affects the way the client then tries
-to authenticate itself. It does not directly affect (to any great
-extent) the way the Samba server does security. I know this is
-strange, but it fits in with the client/server approach of SMB. In SMB
-everything is initiated and controlled by the client, and the server
-can only tell the client what is available and whether an action is
-allowed.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2859238"></a>User Level Security</h3></div></div><p>
-I'll describe user level security first, as its simpler. In user level
-security the client will send a &quot;session setup&quot; command directly after
-the protocol negotiation. This contains a username and password. The
-server can either accept or reject that username/password
-combination. Note that at this stage the server has no idea what
-share the client will eventually try to connect to, so it can't base
-the &quot;accept/reject&quot; on anything other than:
-</p><div class="orderedlist"><ol type="1"><li><p>the username/password</p></li><li><p>the machine that the client is coming from</p></li></ol></div><p>
-If the server accepts the username/password then the client expects to
-be able to mount any share (using a &quot;tree connection&quot;) without
-specifying a password. It expects that all access rights will be as
-the username/password specified in the &quot;session setup&quot;.
-</p><p>
-It is also possible for a client to send multiple &quot;session setup&quot;
-requests. When the server responds it gives the client a &quot;uid&quot; to use
-as an authentication tag for that username/password. The client can
-maintain multiple authentication contexts in this way (WinDD is an
-example of an application that does this)
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2859720"></a>Share Level Security</h3></div></div><p>
-Ok, now for share level security. In share level security the client
-authenticates itself separately for each share. It will send a
-password along with each &quot;tree connection&quot; (share mount). It does not
-explicitly send a username with this operation. The client is
-expecting a password to be associated with each share, independent of
-the user. This means that samba has to work out what username the
-client probably wants to use. It is never explicitly sent the
-username. Some commercial SMB servers such as NT actually associate
-passwords directly with shares in share level security, but samba
-always uses the unix authentication scheme where it is a
-username/password that is authenticated, not a &quot;share/password&quot;.
-</p><p>
-Many clients send a &quot;session setup&quot; even if the server is in share
-level security. They normally send a valid username but no
-password. Samba records this username in a list of &quot;possible
-usernames&quot;. When the client then does a &quot;tree connection&quot; it also adds
-to this list the name of the share they try to connect to (useful for
-home directories) and any users listed in the <b>user =</b> <tt>smb.conf</tt>
-line. The password is then checked in turn against these &quot;possible
-usernames&quot;. If a match is found then the client is authenticated as
-that user.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2859774"></a>Server Level Security</h3></div></div><p>
-Finally &quot;server level&quot; security. In server level security the samba
-server reports to the client that it is in user level security. The
-client then does a &quot;session setup&quot; as described earlier. The samba
-server takes the username/password that the client sends and attempts
-to login to the &quot;password server&quot; by sending exactly the same
-username/password that it got from the client. If that server is in
-user level security and accepts the password then samba accepts the
-clients connection. This allows the samba server to use another SMB
-server as the &quot;password server&quot;.
-</p><p>
-You should also note that at the very start of all this, where the
-server tells the client what security level it is in, it also tells
-the client if it supports encryption. If it does then it supplies the
-client with a random &quot;cryptkey&quot;. The client will then send all
-passwords in encrypted form. You have to compile samba with encryption
-enabled to support this feature, and you have to maintain a separate
-smbpasswd file with SMB style encrypted passwords. It is
-cryptographically impossible to translate from unix style encryption
-to SMB style encryption, although there are some fairly simple management
-schemes by which the two could be kept in sync.
-</p><p>
-&quot;security = server&quot; means that Samba reports to clients that
-it is running in &quot;user mode&quot; but actually passes off all authentication
-requests to another &quot;user mode&quot; server. This requires an additional
-parameter &quot;password server =&quot; that points to the real authentication server.
-That real authentication server can be another Samba server or can be a
-Windows NT server, the later natively capable of encrypted password support.
-</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-<span class="emphasis"><em>Server</em></span> level security is incompatible with what is known
-as <span class="emphasis"><em>schannel</em></span> or &quot;sign and seal&quot; protocols. This means that
-if you want to use <span class="emphasis"><em>server</em></span> level security you must disable
-the use of &quot;sign and seal&quot; on all machines on your network.
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2859859"></a>Configuring Samba for Seemless Windows Network Integration</h4></div></div><p>
-MS Windows clients may use encrypted passwords as part of a challenege/response
-authentication model (a.k.a. NTLMv1) or alone, or clear text strings for simple
-password based authentication. It should be realized that with the SMB protocol
-the password is passed over the network either in plain text or encrypted, but
-not both in the same authentication request.
-</p><p>
-When encrypted passwords are used a password that has been entered by the user
-is encrypted in two ways:
-</p><div class="itemizedlist"><ul type="disc"><li><p>An MD4 hash of the UNICODE of the password
- string. This is known as the NT hash.
- </p></li><li><p>The password is converted to upper case,
- and then padded or trucated to 14 bytes. This string is
- then appended with 5 bytes of NULL characters and split to
- form two 56 bit DES keys to encrypt a &quot;magic&quot; 8 byte value.
- The resulting 16 bytes for the LanMan hash.
- </p></li></ul></div><p>
-MS Windows 95 pre-service pack 1, MS Windows NT versions 3.x and version 4.0
-pre-service pack 3 will use either mode of password authentication. All
-versions of MS Windows that follow these versions no longer support plain
-text passwords by default.
-</p><p>
-MS Windows clients have a habit of dropping network mappings that have been idle
-for 10 minutes or longer. When the user attempts to use the mapped drive
-connection that has been dropped, the client re-establishes the connection using
-a cached copy of the password.
-</p><p>
-When Microsoft changed the default password mode, support was dropped for caching
-of the plain text password. This means that when the registry parameter is changed
-to re-enable use of plain text passwords it appears to work, but when a dropped
-service connection mapping attempts to revalidate it will fail if the remote
-authentication server does not support encrypted passwords. This means that it
-is definitely not a good idea to re-enable plain text password support in such clients.
-</p><p>
-The following parameters can be used to work around the issue of Windows 9x client
-upper casing usernames and password before transmitting them to the SMB server
-when using clear text authentication.
-</p><pre class="programlisting">
- <a href="smb.conf.5.html#PASSWORDLEVEL" target="_top">passsword level</a> = <i><tt>integer</tt></i>
- <a href="smb.conf.5.html#USERNAMELEVEL" target="_top">username level</a> = <i><tt>integer</tt></i>
-</pre><p>
-By default Samba will lower case the username before attempting to lookup the user
-in the database of local system accounts. Because UNIX usernames conventionally
-only contain lower case character, the <i><tt>username level</tt></i> parameter
-is rarely needed.
-</p><p>
-However, passwords on UNIX systems often make use of mixed case characters.
-This means that in order for a user on a Windows 9x client to connect to a Samba
-server using clear text authentication, the <i><tt>password level</tt></i>
-must be set to the maximum number of upper case letter which <span class="emphasis"><em>could</em></span>
-appear is a password. Note that the server OS uses the traditional DES version
-of crypt(), a <i><tt>password level</tt></i> of 8 will result in case
-insensitive passwords as seen from Windows users. This will also result in longer
-login times as Samba has to compute the permutations of the password string and
-try them one by one until a match is located (or all combinations fail).
-</p><p>
-The best option to adopt is to enable support for encrypted passwords
-where ever Samba is used. There are three configuration possibilities
-for support of encrypted passwords:
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2860034"></a>Use MS Windows NT as an authentication server</h4></div></div><p>
-This method involves the additions of the following parameters in the <tt>smb.conf</tt> file:
-</p><pre class="programlisting">
- encrypt passwords = Yes
- security = server
- password server = &quot;NetBIOS_name_of_PDC&quot;
-</pre><p>
-There are two ways of identifying whether or not a username and
-password pair was valid or not. One uses the reply information provided
-as part of the authentication messaging process, the other uses
-just an error code.
-</p><p>
-The down-side of this mode of configuration is the fact that
-for security reasons Samba will send the password server a bogus
-username and a bogus password and if the remote server fails to
-reject the username and password pair then an alternative mode
-of identification of validation is used. Where a site uses password
-lock out after a certain number of failed authentication attempts
-this will result in user lockouts.
-</p><p>
-Use of this mode of authentication does require there to be
-a standard Unix account for the user, this account can be blocked
-to prevent logons by other than MS Windows clients.
-</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2860095"></a>Domain Level Security</h3></div></div><p>
-When samba is operating in <span class="emphasis"><em>security = domain</em></span> mode this means that
-the Samba server has a domain security trust account (a machine account) and will cause
-all authentication requests to be passed through to the domain controllers.
-</p><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2860115"></a>Samba as a member of an MS Windows NT security domain</h4></div></div><p>
-This method involves addition of the following parameters in the <tt>smb.conf</tt> file:
-</p><pre class="programlisting">
- encrypt passwords = Yes
- security = domain
- workgroup = &quot;name of NT domain&quot;
- password server = *
-</pre><p>
-The use of the &quot;*&quot; argument to <b>password server</b> will cause samba to locate the
-domain controller in a way analogous to the way this is done within MS Windows NT.
-This is the default behaviour.
-</p><p>
-In order for this method to work the Samba server needs to join the
-MS Windows NT security domain. This is done as follows:
-</p><div class="itemizedlist"><ul type="disc"><li><p>On the MS Windows NT domain controller using
- the Server Manager add a machine account for the Samba server.
- </p></li><li><p>Next, on the Linux system execute:
- <b>smbpasswd -r PDC_NAME -j DOMAIN_NAME</b> (samba 2.x)
-
- <b>net join -U administrator%password</b> (samba-3)
- </p></li></ul></div><p>
-Use of this mode of authentication does require there to be a standard Unix account
-for the user in order to assign a uid once the account has been authenticated by
-the remote Windows DC. This account can be blocked to prevent logons by clients other than
-MS Windows through things such as setting an invalid shell in the
-<tt>/etc/passwd</tt> entry.
-</p><p>
-An alternative to assigning UIDs to Windows users on a Samba member server is
-presented in the <a href="#winbind" title="Chapter15.Unified Logons between Windows NT and UNIX using Winbind">Winbind Overview</a> chapter
-in this HOWTO collection.
-</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2860234"></a>ADS Level Security</h3></div></div><p>
-For information about the configuration option please refer to the entire section entitled
-<span class="emphasis"><em>Samba as an ADS Domain Member.</em></span>
-</p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="samba-pdc"></a>Chapter5.
-Samba as an NT4 or Win2k Primary Domain Controller
-</h2></div><div><div class="author"><h3 class="author">Gerald (Jerry) Carter</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt>&lt;<a href="mailto:jerry@samba.org">jerry@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author">John H. Terpstra</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt>&lt;<a href="mailto:jht@samba.org">jht@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author">David Bannon</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt>&lt;<a href="mailto:dbannon@samba.org">dbannon@samba.org</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate"> (26 Apr 2001) </p></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2859583">Prerequisite Reading</a></dt><dt><a href="#id2859607">
-Background
-</a></dt><dt><a href="#id2860563">Configuring the Samba Domain Controller</a></dt><dt><a href="#id2860863">Creating Machine Trust Accounts and Joining Clients to the Domain</a></dt><dd><dl><dt><a href="#id2861132">Manual Creation of Machine Trust Accounts</a></dt><dt><a href="#id2861366">&quot;On-the-Fly&quot; Creation of Machine Trust Accounts</a></dt><dt><a href="#id2861423">Joining the Client to the Domain</a></dt></dl></dd><dt><a href="#id2861529">Common Problems and Errors</a></dt><dd><dl><dt><a href="#id2861536">I cannot include a '$' in a machine name</a></dt><dt><a href="#id2861574">I get told &quot;You already have a connection to the Domain....&quot;
-or &quot;Cannot join domain, the credentials supplied conflict with an
-existing set..&quot; when creating a machine trust account.</a></dt><dt><a href="#id2861621">The system can not log you on (C000019B)....</a></dt><dt><a href="#id2861672">The machine trust account for this computer either does not
-exist or is not accessible.</a></dt><dt><a href="#id2861721">When I attempt to login to a Samba Domain from a NT4/W2K workstation,
-I get a message about my account being disabled.</a></dt></dl></dd><dt><a href="#id2861746">Domain Control for Windows 9x/ME</a></dt><dd><dl><dt><a href="#id2861910">Configuration Instructions: Network Logons</a></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2859583"></a>Prerequisite Reading</h2></div></div><p>
-Before you continue reading in this chapter, please make sure
-that you are comfortable with configuring basic files services
-in smb.conf and how to enable and administer password
-encryption in Samba. Theses two topics are covered in the
-<tt>smb.conf</tt> manpage.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2859607"></a>
-Background
-</h2></div></div><p>
-This article outlines the steps necessary for configuring Samba as a PDC.
-It is necessary to have a working Samba server prior to implementing the
-PDC functionality.
-</p><div class="itemizedlist"><ul type="disc"><li><p>
- Domain logons for Windows NT 4.0 / 200x / XP Professional clients.
- </p></li><li><p>
- Placing Windows 9x / Me clients in user level security
- </p></li><li><p>
- Retrieving a list of users and groups from a Samba PDC to
- Windows 9x / Me / NT / 200x / XP Professional clients
- </p></li><li><p>
- Roaming Profiles
- </p></li><li><p>
- Network/System Policies
- </p></li></ul></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-Roaming Profiles and System/Network policies are advanced network administration topics
-that are covered separately in this document.
-</p></div><p>
-The following functionalities are new to the Samba 3.0 release:
-</p><div class="itemizedlist"><ul type="disc"><li><p>
- Windows NT 4 domain trusts
- </p></li><li><p>
- Adding users via the User Manager for Domains
- </p></li></ul></div><p>
-The following functionalities are NOT provided by Samba 3.0:
-</p><div class="itemizedlist"><ul type="disc"><li><p>
- SAM replication with Windows NT 4.0 Domain Controllers
- (i.e. a Samba PDC and a Windows NT BDC or vice versa)
- </p></li><li><p>
- Acting as a Windows 2000 Domain Controller (i.e. Kerberos and
- Active Directory)
- </p></li></ul></div><p>
-Please note that Windows 9x / Me / XP Home clients are not true members of a domain
-for reasons outlined in this article. Therefore the protocol for
-support of Windows 9x-style domain logons is completely different
-from NT4 / Win2k type domain logons and has been officially supported for some
-time.
-</p><p><span class="emphasis"><em>
-MS Windows XP Home edition is NOT able to join a domain and does not permit
-the use of domain logons.</em></span>
-</p><p>
-Implementing a Samba PDC can basically be divided into 3 broad
-steps.
-</p><div class="orderedlist"><ol type="1"><li><p>
- Configuring the Samba PDC
- </p></li><li><p>
- Creating machine trust accounts and joining clients to the domain
- </p></li><li><p>
- Adding and managing domain user accounts
- </p></li></ol></div><p>
-There are other minor details such as user profiles, system
-policies, etc... However, these are not necessarily specific
-to a Samba PDC as much as they are related to Windows NT networking
-concepts.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2860563"></a>Configuring the Samba Domain Controller</h2></div></div><p>
-The first step in creating a working Samba PDC is to
-understand the parameters necessary in smb.conf. Here we
-attempt to explain the parameters that are covered in
-the <tt>smb.conf</tt> man page.
-</p><p>
-Here is an example <tt>smb.conf</tt> for acting as a PDC:
-</p><pre class="programlisting">
-[global]
- ; Basic server settings
- <a href="smb.conf.5.html#NETBIOSNAME" target="_top">netbios name</a> = <i><tt>POGO</tt></i>
- <a href="smb.conf.5.html#WORKGROUP" target="_top">workgroup</a> = <i><tt>NARNIA</tt></i>
-
- ; User and Machine Account Backends
- ; Choices are: tdbsam, tdbsam_nua, smbpasswd, smbpasswd_nua, ldapsam, ldapsam_nua, ...
- ; mysqlsam, xmlsam, guest
- <a href="smb.conf.5.html#PASSDBBACKEND" target="_top">passdb backend</a> = ldapsam, guest
-
- ; we should act as the domain and local master browser
- <a href="smb.conf.5.html#OSLEVEL" target="_top">os level</a> = 64
- <a href="smb.conf.5.html#PERFERREDMASTER" target="_top">preferred master</a> = yes
- <a href="smb.conf.5.html#DOMAINMASTER" target="_top">domain master</a> = yes
- <a href="smb.conf.5.html#LOCALMASTER" target="_top">local master</a> = yes
-
- ; security settings (must user security = user)
- <a href="smb.conf.5.html#SECURITYEQUALSUSER" target="_top">security</a> = user
-
- ; encrypted passwords are a requirement for a PDC
- <a href="smb.conf.5.html#ENCRYPTPASSWORDS" target="_top">encrypt passwords</a> = yes
-
- ; support domain logons
- <a href="smb.conf.5.html#DOMAINLOGONS" target="_top">domain logons</a> = yes
-
- ; where to store user profiles?
- <a href="smb.conf.5.html#LOGONPATH" target="_top">logon path</a> = \\%N\profiles\%u
-
- ; where is a user's home directory and where should it be mounted at?
- <a href="smb.conf.5.html#LOGONDRIVE" target="_top">logon drive</a> = H:
- <a href="smb.conf.5.html#LOGONHOME" target="_top">logon home</a> = \\homeserver\%u
-
- ; specify a generic logon script for all users
- ; this is a relative **DOS** path to the [netlogon] share
- <a href="smb.conf.5.html#LOGONSCRIPT" target="_top">logon script</a> = logon.cmd
-
-; necessary share for domain controller
-[netlogon]
- <a href="smb.conf.5.html#PATH" target="_top">path</a> = /usr/local/samba/lib/netlogon
- <a href="smb.conf.5.html#READONLY" target="_top">read only</a> = yes
- <a href="smb.conf.5.html#WRITELIST" target="_top">write list</a> = <i><tt>ntadmin</tt></i>
-
-; share for storing user profiles
-[profiles]
- <a href="smb.conf.5.html#PATH" target="_top">path</a> = /export/smb/ntprofile
- <a href="smb.conf.5.html#READONLY" target="_top">read only</a> = no
- <a href="smb.conf.5.html#CREATEMASK" target="_top">create mask</a> = 0600
- <a href="smb.conf.5.html#DIRECTORYMASK" target="_top">directory mask</a> = 0700
-</pre><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-The above parameters make for a full set of parameters that may define the server's mode
-of operation. The following parameters are the essentials alone:
-
-</p><pre class="programlisting">
- workgroup = NARNIA
- domain logons = Yes
- security = User
-</pre><p>
-
-The additional parameters shown in the longer listing above just makes for a
-more complete environment.
-</p></div><p>
-There are a couple of points to emphasize in the above configuration.
-</p><div class="itemizedlist"><ul type="disc"><li><p>
- Encrypted passwords must be enabled. For more details on how
- to do this, refer to <a href="#passdb" title="Chapter10.User information database">the User Database chapter</a>.
- </p></li><li><p>
- The server must support domain logons and a
- <tt>[netlogon]</tt> share
- </p></li><li><p>
- The server must be the domain master browser in order for Windows
- client to locate the server as a DC. Please refer to the various
- Network Browsing documentation included with this distribution for
- details.
- </p></li></ul></div><p>
-Samba 3.0 offers a complete implementation of group mapping
-between Windows NT groups and Unix groups (this is really quite
-complicated to explain in a short space).
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2860863"></a>Creating Machine Trust Accounts and Joining Clients to the Domain</h2></div></div><p>
-A machine trust account is a Samba account that is used to
-authenticate a client machine (rather than a user) to the Samba
-server. In Windows terminology, this is known as a &quot;Computer
-Account.&quot;</p><p>
-The password of a machine trust account acts as the shared secret for
-secure communication with the Domain Controller. This is a security
-feature to prevent an unauthorized machine with the same NetBIOS name
-from joining the domain and gaining access to domain user/group
-accounts. Windows NT, 200x, XP Professional clients use machine trust
-accounts, but Windows 9x / Me / XP Home clients do not. Hence, a
-Windows 9x / Me / XP Home client is never a true member of a domain
-because it does not possess a machine trust account, and thus has no
-shared secret with the domain controller.
-</p><p>A Windows PDC stores each machine trust account in the Windows
-Registry. A Samba-3 PDC also has to store machine trust account information
-in a suitable backend data store. With Samba-3 there can be multiple back-ends
-for this including:
-</p><div class="itemizedlist"><ul type="disc"><li><p>
- <span class="emphasis"><em>smbpasswd</em></span> - the plain ascii file stored used by
- earlier versions of Samba. This file configuration option requires
- a Unix/Linux system account for EVERY entry (ie: both for user and for
- machine accounts). This file will be located in the <span class="emphasis"><em>private</em></span>
- directory (default is /usr/local/samba/lib/private or on linux /etc/samba).
- </p></li><li><p>
- <span class="emphasis"><em>smbpasswd_nua</em></span> - This file is independant of the
- system wide user accounts. The use of this back-end option requires
- specification of the &quot;non unix account range&quot; option also. It is called
- smbpasswd and will be located in the <tt>private</tt> directory.
- </p></li><li><p>
- <span class="emphasis"><em>tdbsam</em></span> - a binary database backend that will be
- stored in the <span class="emphasis"><em>private</em></span> directory in a file called
- <span class="emphasis"><em>passwd.tdb</em></span>. The key benefit of this binary format
- file is that it can store binary objects that can not be accomodated
- in the traditional plain text smbpasswd file.
- </p></li><li><p>
- <span class="emphasis"><em>tdbsam_nua</em></span> like the smbpasswd_nua option above, this
- file allows the creation of arbitrary user and machine accounts without
- requiring that account to be added to the system (/etc/passwd) file. It
- too requires the specification of the &quot;non unix account range&quot; option
- in the [globals] section of the <tt>smb.conf</tt> file.
- </p></li><li><p>
- <span class="emphasis"><em>ldapsam</em></span> - An LDAP based back-end. Permits the
- LDAP server to be specified. eg: ldap://localhost or ldap://frodo.murphy.com
- </p></li><li><p>
- <span class="emphasis"><em>ldapsam_nua</em></span> - LDAP based back-end with no unix
- account requirement, like smbpasswd_nua and tdbsam_nua above.
- </p></li></ul></div><p>Read the chapter about the <a href="#passdb" title="Chapter10.User information database">User Database</a>
-for details.</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-The new tdbsam and ldapsam account backends store vastly more information than
-smbpasswd is capable of. The new backend database includes capacity to specify
-per user settings for many parameters, over-riding global settings given in the
-<tt>smb.conf</tt> file. eg: logon drive, logon home, logon path, etc.
-</p></div><p>
-A Samba PDC, however, stores each machine trust account in two parts,
-as follows:
-
-</p><div class="itemizedlist"><ul type="disc"><li><p>A Samba account, stored in the same location as user
- LanMan and NT password hashes (currently
- <tt>smbpasswd</tt>). The Samba account
- possesses and uses only the NT password hash.</p></li><li><p>A corresponding Unix account, typically stored in
- <tt>/etc/passwd</tt>. (Future releases will alleviate the need to
- create <tt>/etc/passwd</tt> entries.) </p></li></ul></div><p>
-</p><p>
-There are two ways to create machine trust accounts:
-</p><div class="itemizedlist"><ul type="disc"><li><p> Manual creation. Both the Samba and corresponding
- Unix account are created by hand.</p></li><li><p> &quot;On-the-fly&quot; creation. The Samba machine trust
- account is automatically created by Samba at the time the client
- is joined to the domain. (For security, this is the
- recommended method.) The corresponding Unix account may be
- created automatically or manually. </p></li></ul></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2861132"></a>Manual Creation of Machine Trust Accounts</h3></div></div><p>
-The first step in manually creating a machine trust account is to
-manually create the corresponding Unix account in
-<tt>/etc/passwd</tt>. This can be done using
-<b>vipw</b> or other 'add user' command that is normally
-used to create new Unix accounts. The following is an example for a
-Linux based Samba server:
-</p><p>
- <tt>root# </tt><b>/usr/sbin/useradd -g 100 -d /dev/null -c <i><tt>&quot;machine
-nickname&quot;</tt></i> -s /bin/false <i><tt>machine_name</tt></i>$ </b>
-</p><p>
-<tt>root# </tt><b>passwd -l <i><tt>machine_name</tt></i>$</b>
-</p><p>On *BSD systems, this can be done using the 'chpass' utility:</p><p>
-<tt>root# </tt><b>chpass -a &quot;<i><tt>machine_name</tt></i>$:*:101:100::0:0:Workstation <i><tt>machine_name</tt></i>:/dev/null:/sbin/nologin&quot;</b>
-</p><p>
-The <tt>/etc/passwd</tt> entry will list the machine name
-with a &quot;$&quot; appended, won't have a password, will have a null shell and no
-home directory. For example a machine named 'doppy' would have an
-<tt>/etc/passwd</tt> entry like this:
-</p><pre class="programlisting">
-doppy$:x:505:501:<i><tt>machine_nickname</tt></i>:/dev/null:/bin/false
-</pre><p>
-Above, <i><tt>machine_nickname</tt></i> can be any
-descriptive name for the client, i.e., BasementComputer.
-<i><tt>machine_name</tt></i> absolutely must be the NetBIOS
-name of the client to be joined to the domain. The &quot;$&quot; must be
-appended to the NetBIOS name of the client or Samba will not recognize
-this as a machine trust account.
-</p><p>
-Now that the corresponding Unix account has been created, the next step is to create
-the Samba account for the client containing the well-known initial
-machine trust account password. This can be done using the <a href="smbpasswd.8.html" target="_top"><b>smbpasswd(8)</b></a> command
-as shown here:
-</p><p>
-<tt>root# </tt><b><tt>smbpasswd -a -m <i><tt>machine_name</tt></i></tt></b>
-</p><p>
-where <i><tt>machine_name</tt></i> is the machine's NetBIOS
-name. The RID of the new machine account is generated from the UID of
-the corresponding Unix account.
-</p><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Join the client to the domain immediately</h3><p>
- Manually creating a machine trust account using this method is the
- equivalent of creating a machine trust account on a Windows NT PDC using
- the &quot;Server Manager&quot;. From the time at which the account is created
- to the time which the client joins the domain and changes the password,
- your domain is vulnerable to an intruder joining your domain using
- a machine with the same NetBIOS name. A PDC inherently trusts
- members of the domain and will serve out a large degree of user
- information to such clients. You have been warned!
- </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2861366"></a>&quot;On-the-Fly&quot; Creation of Machine Trust Accounts</h3></div></div><p>
-The second (and recommended) way of creating machine trust accounts is
-simply to allow the Samba server to create them as needed when the client
-is joined to the domain. </p><p>Since each Samba machine trust account requires a corresponding
-Unix account, a method for automatically creating the
-Unix account is usually supplied; this requires configuration of the
-<a href="smb.conf.5.html#ADDUSERSCRIPT" target="_top">add user script</a>
-option in <tt>smb.conf</tt>. This
-method is not required, however; corresponding Unix accounts may also
-be created manually.
-</p><p>Below is an example for a RedHat 6.2 Linux system.
-</p><pre class="programlisting">
-[global]
- # &lt;...remainder of parameters...&gt;
- add user script = /usr/sbin/useradd -d /dev/null -g 100 -s /bin/false -M %u
-</pre></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2861423"></a>Joining the Client to the Domain</h3></div></div><p>
-The procedure for joining a client to the domain varies with the
-version of Windows.
-</p><div class="itemizedlist"><ul type="disc"><li><p><span class="emphasis"><em>Windows 2000</em></span></p><p>
- When the user elects to join the client to a domain, Windows prompts for
- an account and password that is privileged to join the domain. A Samba administrative
- account (i.e., a Samba account that has root privileges on the Samba server) must be
- entered here; the operation will fail if an ordinary user account is given.
- The password for this account should be set to a different password than the associated
- <tt>/etc/passwd</tt> entry, for security reasons.
- </p><p>
- The session key of the Samba administrative account acts as an
- encryption key for setting the password of the machine trust
- account. The machine trust account will be created on-the-fly, or
- updated if it already exists.
- </p></li><li><p><span class="emphasis"><em>Windows NT</em></span></p><p> If the machine trust account was created manually, on the
- Identification Changes menu enter the domain name, but do not
- check the box &quot;Create a Computer Account in the Domain.&quot; In this case,
- the existing machine trust account is used to join the machine to
- the domain.</p><p> If the machine trust account is to be created
- on-the-fly, on the Identification Changes menu enter the domain
- name, and check the box &quot;Create a Computer Account in the Domain.&quot; In
- this case, joining the domain proceeds as above for Windows 2000
- (i.e., you must supply a Samba administrative account when
- prompted).</p></li><li><p><span class="emphasis"><em>Samba</em></span></p><p>Joining a samba client to a domain is documented in
- the <a href="#domain-member" title="Chapter8.Samba as a NT4 or Win2k domain member">Domain Member</a> chapter.
-</p></li></ul></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2861529"></a>Common Problems and Errors</h2></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2861536"></a>I cannot include a '$' in a machine name</h3></div></div><p>
-A 'machine name' in (typically) <tt>/etc/passwd</tt>
-of the machine name with a '$' appended. FreeBSD (and other BSD
-systems?) won't create a user with a '$' in their name.
-</p><p>
-The problem is only in the program used to make the entry. Once made, it works perfectly.
-Create a user without the '$' using <b>vipw</b> to edit the entry, adding
-the '$'. Or create the whole entry with vipw if you like, make sure you use a unique User ID!
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2861574"></a>I get told &quot;You already have a connection to the Domain....&quot;
-or &quot;Cannot join domain, the credentials supplied conflict with an
-existing set..&quot; when creating a machine trust account.</h3></div></div><p>
-This happens if you try to create a machine trust account from the
-machine itself and already have a connection (e.g. mapped drive)
-to a share (or IPC$) on the Samba PDC. The following command
-will remove all network drive connections:
-</p><p>
-<tt>C:\WINNT\&gt;</tt> <b>net use * /d</b>
-</p><p>
-Further, if the machine is already a 'member of a workgroup' that
-is the same name as the domain you are joining (bad idea) you will
-get this message. Change the workgroup name to something else, it
-does not matter what, reboot, and try again.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2861621"></a>The system can not log you on (C000019B)....</h3></div></div><p>I joined the domain successfully but after upgrading
-to a newer version of the Samba code I get the message, &quot;The system
-can not log you on (C000019B), Please try again or consult your
-system administrator&quot; when attempting to logon.
-</p><p>
-This occurs when the domain SID stored in the secrets.tdb database
-is changed. The most common cause of a change in domain SID is when
-the domain name and/or the server name (netbios name) is changed.
-The only way to correct the problem is to restore the original domain
-SID or remove the domain client from the domain and rejoin. The domain
-SID may be reset using either the net or rpcclient utilities.
-</p><p>
-The reset or change the domain SID you can use the net command as follows:
-
-</p><pre class="programlisting">
- net getlocalsid 'OLDNAME'
- net setlocalsid 'SID'
-</pre><p>
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2861672"></a>The machine trust account for this computer either does not
-exist or is not accessible.</h3></div></div><p>
-When I try to join the domain I get the message &quot;The machine account
-for this computer either does not exist or is not accessible&quot;. What's
-wrong?
-</p><p>
-This problem is caused by the PDC not having a suitable machine trust account.
-If you are using the <i><tt>add user script</tt></i> method to create
-accounts then this would indicate that it has not worked. Ensure the domain
-admin user system is working.
-</p><p>
-Alternatively if you are creating account entries manually then they
-have not been created correctly. Make sure that you have the entry
-correct for the machine trust account in smbpasswd file on the Samba PDC.
-If you added the account using an editor rather than using the smbpasswd
-utility, make sure that the account name is the machine NetBIOS name
-with a '$' appended to it ( i.e. computer_name$ ). There must be an entry
-in both /etc/passwd and the smbpasswd file. Some people have reported
-that inconsistent subnet masks between the Samba server and the NT
-client have caused this problem. Make sure that these are consistent
-for both client and server.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2861721"></a>When I attempt to login to a Samba Domain from a NT4/W2K workstation,
-I get a message about my account being disabled.</h3></div></div><p>
-At first be ensure to enable the useraccounts with <b>smbpasswd -e
-%user%</b>, this is normally done, when you create an account.
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2861746"></a>Domain Control for Windows 9x/ME</h2></div></div><p>
-A domain and a workgroup are exactly the same thing in terms of network
-browsing. The difference is that a distributable authentication
-database is associated with a domain, for secure login access to a
-network. Also, different access rights can be granted to users if they
-successfully authenticate against a domain logon server. Samba-3 does this
-now in the same way that MS Windows NT/2K.
-</p><p>
-The SMB client logging on to a domain has an expectation that every other
-server in the domain should accept the same authentication information.
-Network browsing functionality of domains and workgroups is identical and
-is explained in this documentation under the browsing discussions.
-It should be noted, that browsing is totally orthogonal to logon support.
-</p><p>
-Issues related to the single-logon network model are discussed in this
-section. Samba supports domain logons, network logon scripts, and user
-profiles for MS Windows for workgroups and MS Windows 9X/ME clients
-which are the focus of this section.
-</p><p>
-When an SMB client in a domain wishes to logon it broadcast requests for a
-logon server. The first one to reply gets the job, and validates its
-password using whatever mechanism the Samba administrator has installed.
-It is possible (but very stupid) to create a domain where the user
-database is not shared between servers, i.e. they are effectively workgroup
-servers advertising themselves as participating in a domain. This
-demonstrates how authentication is quite different from but closely
-involved with domains.
-</p><p>
-Using these features you can make your clients verify their logon via
-the Samba server; make clients run a batch file when they logon to
-the network and download their preferences, desktop and start menu.
-</p><p>
-Before launching into the configuration instructions, it is
-worthwhile to look at how a Windows 9x/ME client performs a logon:
-</p><div class="orderedlist"><ol type="1"><li><p>
- The client broadcasts (to the IP broadcast address of the subnet it is in)
- a NetLogon request. This is sent to the NetBIOS name DOMAIN&lt;1c&gt; at the
- NetBIOS layer. The client chooses the first response it receives, which
- contains the NetBIOS name of the logon server to use in the format of
- \\SERVER.
- </p></li><li><p>
- The client then connects to that server, logs on (does an SMBsessetupX) and
- then connects to the IPC$ share (using an SMBtconX).
- </p></li><li><p>
- The client then does a NetWkstaUserLogon request, which retrieves the name
- of the user's logon script.
- </p></li><li><p>
- The client then connects to the NetLogon share and searches for this
- and if it is found and can be read, is retrieved and executed by the client.
- After this, the client disconnects from the NetLogon share.
- </p></li><li><p>
- The client then sends a NetUserGetInfo request to the server, to retrieve
- the user's home share, which is used to search for profiles. Since the
- response to the NetUserGetInfo request does not contain much more then
- the user's home share, profiles for Win9X clients MUST reside in the user
- home directory.
- </p></li><li><p>
- The client then connects to the user's home share and searches for the
- user's profile. As it turns out, you can specify the user's home share as
- a sharename and path. For example, \\server\fred\.profile.
- If the profiles are found, they are implemented.
- </p></li><li><p>
- The client then disconnects from the user's home share, and reconnects to
- the NetLogon share and looks for CONFIG.POL, the policies file. If this is
- found, it is read and implemented.
- </p></li></ol></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2861910"></a>Configuration Instructions: Network Logons</h3></div></div><p>
-The main difference between a PDC and a Windows 9x logon
-server configuration is that
-</p><div class="itemizedlist"><ul type="disc"><li><p>
-Password encryption is not required for a Windows 9x logon server.
-</p></li><li><p>
-Windows 9x/ME clients do not possess machine trust accounts.
-</p></li></ul></div><p>
-Therefore, a Samba PDC will also act as a Windows 9x logon
-server.
-</p><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">security mode and master browsers</h3><p>
-There are a few comments to make in order to tie up some
-loose ends. There has been much debate over the issue of whether
-or not it is ok to configure Samba as a Domain Controller in security
-modes other than <tt>USER</tt>. The only security mode
-which will not work due to technical reasons is <tt>SHARE</tt>
-mode security. <tt>DOMAIN</tt> and <tt>SERVER</tt>
-mode security is really just a variation on SMB user level security.
-</p><p>
-Actually, this issue is also closely tied to the debate on whether
-or not Samba must be the domain master browser for its workgroup
-when operating as a DC. While it may technically be possible
-to configure a server as such (after all, browsing and domain logons
-are two distinctly different functions), it is not a good idea to do
-so. You should remember that the DC must register the DOMAIN#1b NetBIOS
-name. This is the name used by Windows clients to locate the DC.
-Windows clients do not distinguish between the DC and the DMB.
-For this reason, it is very wise to configure the Samba DC as the DMB.
-</p><p>
-Now back to the issue of configuring a Samba DC to use a mode other
-than &quot;security = user&quot;. If a Samba host is configured to use
-another SMB server or DC in order to validate user connection
-requests, then it is a fact that some other machine on the network
-(the &quot;password server&quot;) knows more about the user than the Samba host.
-99% of the time, this other host is a domain controller. Now
-in order to operate in domain mode security, the &quot;workgroup&quot; parameter
-must be set to the name of the Windows NT domain (which already
-has a domain controller, right?)
-</p><p>
-Therefore configuring a Samba box as a DC for a domain that
-already by definition has a PDC is asking for trouble.
-Therefore, you should always configure the Samba DC to be the DMB
-for its domain.
-</p></div></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="samba-bdc"></a>Chapter6.
-Samba Backup Domain Controller to Samba Domain Control
-</h2></div><div><div class="author"><h3 class="author">Volker Lendecke</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt>&lt;<a href="mailto:Volker.Lendecke@SerNet.DE">Volker.Lendecke@SerNet.DE</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate"> (26 Apr 2001) </p></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2845056">Prerequisite Reading</a></dt><dt><a href="#id2860294">Background</a></dt><dt><a href="#id2862166">What qualifies a Domain Controller on the network?</a></dt><dd><dl><dt><a href="#id2862187">How does a Workstation find its domain controller?</a></dt><dt><a href="#id2862212">When is the PDC needed?</a></dt></dl></dd><dt><a href="#id2862231">Can Samba be a Backup Domain Controller to an NT PDC?</a></dt><dt><a href="#id2862264">How do I set up a Samba BDC?</a></dt><dd><dl><dt><a href="#id2862361">How do I replicate the smbpasswd file?</a></dt><dt><a href="#id2862390">Can I do this all with LDAP?</a></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2845056"></a>Prerequisite Reading</h2></div></div><p>
-Before you continue reading in this chapter, please make sure
-that you are comfortable with configuring a Samba PDC
-as described in the <a href="Samba-PDC-HOWTO.html" target="_top">Samba-PDC-HOWTO</a>.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2860294"></a>Background</h2></div></div><p>
-What is a Domain Controller? It is a machine that is able to answer
-logon requests from workstations in a Windows NT Domain. Whenever a
-user logs into a Windows NT Workstation, the workstation connects to a
-Domain Controller and asks him whether the username and password the
-user typed in is correct. The Domain Controller replies with a lot of
-information about the user, for example the place where the users
-profile is stored, the users full name of the user. All this
-information is stored in the NT user database, the so-called SAM.
-</p><p>
-There are two kinds of Domain Controller in a NT 4 compatible Domain:
-A Primary Domain Controller (PDC) and one or more Backup Domain
-Controllers (BDC). The PDC contains the master copy of the
-SAM. Whenever the SAM has to change, for example when a user changes
-his password, this change has to be done on the PDC. A Backup Domain
-Controller is a machine that maintains a read-only copy of the
-SAM. This way it is able to reply to logon requests and authenticate
-users in case the PDC is not available. During this time no changes to
-the SAM are possible. Whenever changes to the SAM are done on the PDC,
-all BDC receive the changes from the PDC.
-</p><p>
-Since version 2.2 Samba officially supports domain logons for all
-current Windows Clients, including Windows 2000 and XP. This text
-assumes the domain to be named SAMBA. To be able to act as a PDC, some
-parameters in the [global]-section of the smb.conf have to be set:
-</p><pre class="programlisting">
- workgroup = SAMBA
- domain master = yes
- domain logons = yes
-</pre><p>
-Several other things like a [homes] and a [netlogon] share also may be
-set along with settings for the profile path, the users home drive and
-others. This will not be covered in this document.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2862166"></a>What qualifies a Domain Controller on the network?</h2></div></div><p>
-Every machine that is a Domain Controller for the domain SAMBA has to
-register the NetBIOS group name SAMBA#1c with the WINS server and/or
-by broadcast on the local network. The PDC also registers the unique
-NetBIOS name SAMBA#1b with the WINS server. The name type #1b is
-normally reserved for the domain master browser, a role that has
-nothing to do with anything related to authentication, but the
-Microsoft Domain implementation requires the domain master browser to
-be on the same machine as the PDC.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2862187"></a>How does a Workstation find its domain controller?</h3></div></div><p>
-A NT workstation in the domain SAMBA that wants a local user to be
-authenticated has to find the domain controller for SAMBA. It does
-this by doing a NetBIOS name query for the group name SAMBA#1c. It
-assumes that each of the machines it gets back from the queries is a
-domain controller and can answer logon requests. To not open security
-holes both the workstation and the selected (TODO: How is the DC
-chosen) domain controller authenticate each other. After that the
-workstation sends the user's credentials (his name and password) to
-the domain controller, asking for approval.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2862212"></a>When is the PDC needed?</h3></div></div><p>
-Whenever a user wants to change his password, this has to be done on
-the PDC. To find the PDC, the workstation does a NetBIOS name query
-for SAMBA#1b, assuming this machine maintains the master copy of the
-SAM. The workstation contacts the PDC, both mutually authenticate and
-the password change is done.
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2862231"></a>Can Samba be a Backup Domain Controller to an NT PDC?</h2></div></div><p>
-With version 2.2, no. The native NT SAM replication protocols have
-not yet been fully implemented. The Samba Team is working on
-understanding and implementing the protocols, but this work has not
-been finished for version 2.2.
-</p><p>
-With version 3.0, the work on both the replication protocols and a
-suitable storage mechanism has progressed, and some form of NT4 BDC
-support is expected soon.
-</p><p>
-Can I get the benefits of a BDC with Samba? Yes. The main reason for
-implementing a BDC is availability. If the PDC is a Samba machine,
-a second Samba machine can be set up to
-service logon requests whenever the PDC is down.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2862264"></a>How do I set up a Samba BDC?</h2></div></div><p>
-Several things have to be done:
-</p><div class="itemizedlist"><ul type="disc"><li><p>
-The domain SID has to be the same on the PDC and the BDC. This used to
-be stored in the file private/MACHINE.SID. This file is not created
-anymore since Samba 2.2.5 or even earlier. Nowadays the domain SID is
-stored in the file private/secrets.tdb. Simply copying the secrets.tdb
-from the PDC to the BDC does not work, as the BDC would
-generate a new SID for itself and override the domain SID with this
-new BDC SID.</p><p>
-To retrieve the domain SID from the PDC or an existing BDC and store it in the
-secrets.tdb, execute 'net rpc getsid' on the BDC.
-</p></li><li><p>
-The Unix user database has to be synchronized from the PDC to the
-BDC. This means that both the /etc/passwd and /etc/group have to be
-replicated from the PDC to the BDC. This can be done manually
-whenever changes are made, or the PDC is set up as a NIS master
-server and the BDC as a NIS slave server. To set up the BDC as a
-mere NIS client would not be enough, as the BDC would not be able to
-access its user database in case of a PDC failure.
-</p></li><li><p>
-The Samba password database in the file private/smbpasswd has to be
-replicated from the PDC to the BDC. This is a bit tricky, see the
-next section.
-</p></li><li><p>
-Any netlogon share has to be replicated from the PDC to the
-BDC. This can be done manually whenever login scripts are changed,
-or it can be done automatically together with the smbpasswd
-synchronization.
-</p></li></ul></div><p>
-Finally, the BDC has to be found by the workstations. This can be done
-by setting
-</p><pre class="programlisting">
- workgroup = samba
- domain master = no
- domain logons = yes
-</pre><p>
-in the [global]-section of the smb.conf of the BDC. This makes the BDC
-only register the name SAMBA#1c with the WINS server. This is no
-problem as the name SAMBA#1c is a NetBIOS group name that is meant to
-be registered by more than one machine. The parameter 'domain master =
-no' forces the BDC not to register SAMBA#1b which as a unique NetBIOS
-name is reserved for the Primary Domain Controller.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2862361"></a>How do I replicate the smbpasswd file?</h3></div></div><p>
-Replication of the smbpasswd file is sensitive. It has to be done
-whenever changes to the SAM are made. Every user's password change is
-done in the smbpasswd file and has to be replicated to the BDC. So
-replicating the smbpasswd file very often is necessary.
-</p><p>
-As the smbpasswd file contains plain text password equivalents, it
-must not be sent unencrypted over the wire. The best way to set up
-smbpasswd replication from the PDC to the BDC is to use the utility
-rsync. rsync can use ssh as a transport. ssh itself can be set up to
-accept *only* rsync transfer without requiring the user to type a
-password.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2862390"></a>Can I do this all with LDAP?</h3></div></div><p>The simple answer is YES. Samba's pdb_ldap code supports
-binding to a replica LDAP server, and will also follow referrals and
-rebind to the master if it ever needs to make a modification to the
-database. (Normally BDCs are read only, so this will not occur
-often).
-</p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="ADS"></a>Chapter7.Samba as a ADS domain member</h2></div><div><div class="author"><h3 class="author">Andrew Tridgell</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt>&lt;<a href="mailto:tridge@samba.org">tridge@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author">Jelmer R. Vernooij</h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt>&lt;<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate">2002/2003</p></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2862021">Setup your smb.conf</a></dt><dt><a href="#id2862571">Setup your /etc/krb5.conf</a></dt><dt><a href="#ads-create-machine-account">Create the computer account</a></dt><dd><dl><dt><a href="#id2862765">Possible errors</a></dt></dl></dd><dt><a href="#ads-test-server">Test your server setup</a></dt><dt><a href="#ads-test-smbclient">Testing with smbclient</a></dt><dt><a href="#id2862919">Notes</a></dt></dl></div><p>
-This is a rough guide to setting up Samba 3.0 with kerberos authentication against a
-Windows2000 KDC.
-</p><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2862021"></a>Setup your <tt>smb.conf</tt></h2></div></div><p>You must use at least the following 3 options in smb.conf:</p><pre class="programlisting">
- realm = YOUR.KERBEROS.REALM
- security = ADS
- encrypt passwords = yes
-</pre><p>
-In case samba can't figure out your ads server using your realm name, use the
-<b>ads server</b> option in <tt>smb.conf</tt>:
-</p><pre class="programlisting">
- ads server = your.kerberos.server
-</pre><p>
-</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>You do *not* need a smbpasswd file, and older clients will
- be authenticated as if <b>security = domain</b>,
- although it won't do any harm
- and allows you to have local users not in the domain.
- I expect that the above required options will change soon when we get better
- active directory integration.</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2862571"></a>Setup your <tt>/etc/krb5.conf</tt></h2></div></div><p>Note: you will need the krb5 workstation, devel, and libs installed</p><p>The minimal configuration for <tt>krb5.conf</tt> is:</p><pre class="programlisting">
- [realms]
- YOUR.KERBEROS.REALM = {
- kdc = your.kerberos.server
- }
-</pre><p>Test your config by doing a <b><tt>kinit
-<i><tt>USERNAME</tt></i>@<i><tt>REALM</tt></i></tt></b> and
-making sure that your password is accepted by the Win2000 KDC.
-</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>The realm must be uppercase or you will get &quot;Cannot find KDC for requested
-realm while getting initial credentials&quot; error </p></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>Time between the two servers must be synchronized. You will get a
-&quot;kinit(v5): Clock skew too great while getting initial credentials&quot; if the time
-difference is more than five minutes. </p></div><p>
-You also must ensure that you can do a reverse DNS lookup on the IP
-address of your KDC. Also, the name that this reverse lookup maps to
-must either be the netbios name of the KDC (ie. the hostname with no
-domain attached) or it can alternatively be the netbios name
-followed by the realm.
-</p><p>
-The easiest way to ensure you get this right is to add a
-<tt>/etc/hosts</tt> entry mapping the IP address of your KDC to
-its netbios name. If you don't get this right then you will get a
-&quot;local error&quot; when you try to join the realm.
-</p><p>
-If all you want is kerberos support in smbclient then you can skip
-straight to <a href="#ads-test-smbclient" title="Testing with smbclient">Test with smbclient</a> now.
-<a href="#ads-create-machine-account" title="Create the computer account">Creating a computer account</a>
-and <a href="#ads-test-server" title="Test your server setup">testing your servers</a>
-is only needed if you want kerberos support for smbd and winbindd.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="ads-create-machine-account"></a>Create the computer account</h2></div></div><p>
-As a user that has write permission on the Samba private directory
-(usually root) run:
-</p><pre class="programlisting">
- <b><tt>net join -U Administrator%password</tt></b>
-</pre><p>
-</p><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2862765"></a>Possible errors</h3></div></div><p>
-</p><div class="variablelist"><dl><dt><span class="term">&quot;ADS support not compiled in&quot;</span></dt><dd><p>Samba must be reconfigured (remove config.cache) and recompiled
- (make clean all install) after the kerberos libs and headers are installed.
- </p></dd><dt><span class="term">net join prompts for user name</span></dt><dd><p>You need to login to the domain using <b><tt>kinit
- <i><tt>USERNAME</tt></i>@<i><tt>REALM</tt></i></tt></b>.
- <i><tt>USERNAME</tt></i> must be a user who has rights to add a machine
- to the domain. </p></dd></dl></div><p>
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="ads-test-server"></a>Test your server setup</h2></div></div><p>
-If the join was successful, you will see a new computer account with the
-NetBIOS name of your Samba server in Active Directory (in the &quot;Computers&quot;
-folder under Users and Computers.
-</p><p>
-On a Windows 2000 client try <b><tt>net use * \\server\share</tt></b>. You should
-be logged in with kerberos without needing to know a password. If
-this fails then run <b><tt>klist tickets</tt></b>. Did you get a ticket for the
-server? Does it have an encoding type of DES-CBC-MD5 ?
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="ads-test-smbclient"></a>Testing with smbclient</h2></div></div><p>
-On your Samba server try to login to a Win2000 server or your Samba
-server using smbclient and kerberos. Use smbclient as usual, but
-specify the <i><tt>-k</tt></i> option to choose kerberos authentication.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2862919"></a>Notes</h2></div></div><p>You must change administrator password at least once after DC
-install, to create the right encoding types</p><p>w2k doesn't seem to create the _kerberos._udp and _ldap._tcp in
- their defaults DNS setup. Maybe fixed in service packs?</p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="domain-member"></a>Chapter8.Samba as a NT4 or Win2k domain member</h2></div><div><div class="author"><h3 class="author">Jeremy Allison</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt>&lt;<a href="mailto:jra@samba.org">jra@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author">Gerald (Jerry) Carter</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt>&lt;<a href="mailto:jerry@samba.org">jerry@samba.org</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate">16 Apr 2001</p></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2862413">Joining an NT Domain with Samba 3.0</a></dt><dt><a href="#id2863318">Why is this better than security = server?</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2862413"></a>Joining an NT Domain with Samba 3.0</h2></div></div><p><span class="emphasis"><em>Assumptions:</em></span>
- </p><pre class="programlisting">
- NetBIOS name: SERV1
- Win2K/NT domain name: DOM
- Domain's PDC NetBIOS name: DOMPDC
- Domain's BDC NetBIOS names: DOMBDC1 and DOMBDC2
- </pre><p>
- </p><p>First, you must edit your <tt>smb.conf</tt> file to tell Samba it should
- now use domain security.</p><p>Change (or add) your <a href="smb.conf.5.html#SECURITY" target="_top">
- <i><tt>security =</tt></i></a> line in the [global] section
- of your <tt>smb.conf</tt> to read:</p><p><b>security = domain</b></p><p>Next change the <a href="smb.conf.5.html#WORKGROUP" target="_top"><i><tt>
- workgroup =</tt></i></a> line in the [global] section to read: </p><p><b>workgroup = DOM</b></p><p>as this is the name of the domain we are joining. </p><p>You must also have the parameter <a href="smb.conf.5.html#ENCRYPTPASSWORDS" target="_top">
- <i><tt>encrypt passwords</tt></i></a> set to <tt>yes
- </tt> in order for your users to authenticate to the NT PDC.</p><p>Finally, add (or modify) a <a href="smb.conf.5.html#PASSWORDSERVER" target="_top">
- <i><tt>password server =</tt></i></a> line in the [global]
- section to read: </p><p><b>password server = DOMPDC DOMBDC1 DOMBDC2</b></p><p>These are the primary and backup domain controllers Samba
- will attempt to contact in order to authenticate users. Samba will
- try to contact each of these servers in order, so you may want to
- rearrange this list in order to spread out the authentication load
- among domain controllers.</p><p>Alternatively, if you want smbd to automatically determine
- the list of Domain controllers to use for authentication, you may
- set this line to be :</p><p><b>password server = *</b></p><p>This method, allows Samba to use exactly the same
- mechanism that NT does. This
- method either broadcasts or uses a WINS database in order to
- find domain controllers to authenticate against.</p><p>In order to actually join the domain, you must run this
- command:</p><p><tt>root# </tt><b><tt>net join -S DOMPDC
- -U<i><tt>Administrator%password</tt></i></tt></b></p><p>
- If the <b><tt>-S DOMPDC</tt></b> argument is not given then
- the domain name will be obtained from smb.conf.
- </p><p>as we are joining the domain DOM and the PDC for that domain
- (the only machine that has write access to the domain SAM database)
- is DOMPDC. The <i><tt>Administrator%password</tt></i> is
- the login name and password for an account which has the necessary
- privilege to add machines to the domain. If this is successful
- you will see the message:</p><p><tt>Joined domain DOM.</tt>
- or <tt>Joined 'SERV1' to realm 'MYREALM'</tt>
- </p><p>in your terminal window. See the <a href="net.8.html" target="_top">
- net(8)</a> man page for more details.</p><p>This process joins the server to the domain
- without having to create the machine trust account on the PDC
- beforehand.</p><p>This command goes through the machine account password
- change protocol, then writes the new (random) machine account
- password for this Samba server into a file in the same directory
- in which an smbpasswd file would be stored - normally :</p><p><tt>/usr/local/samba/private/secrets.tdb</tt></p><p>This file is created and owned by root and is not
- readable by any other user. It is the key to the domain-level
- security for your system, and should be treated as carefully
- as a shadow password file.</p><p>Finally, restart your Samba daemons and get ready for
- clients to begin using domain security!</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2863318"></a>Why is this better than security = server?</h2></div></div><p>Currently, domain security in Samba doesn't free you from
- having to create local Unix users to represent the users attaching
- to your server. This means that if domain user <tt>DOM\fred
- </tt> attaches to your domain security Samba server, there needs
- to be a local Unix user fred to represent that user in the Unix
- filesystem. This is very similar to the older Samba security mode
- <a href="smb.conf.5.html#SECURITYEQUALSSERVER" target="_top">security = server</a>,
- where Samba would pass through the authentication request to a Windows
- NT server in the same way as a Windows 95 or Windows 98 server would.
- </p><p>Please refer to the <a href="winbind.html" target="_top">Winbind
- paper</a> for information on a system to automatically
- assign UNIX uids and gids to Windows NT Domain users and groups.
- </p><p>The advantage to domain-level security is that the
- authentication in domain-level security is passed down the authenticated
- RPC channel in exactly the same way that an NT server would do it. This
- means Samba servers now participate in domain trust relationships in
- exactly the same way NT servers do (i.e., you can add Samba servers into
- a resource domain and have the authentication passed on from a resource
- domain PDC to an account domain PDC).</p><p>In addition, with <b>security = server</b> every Samba
- daemon on a server has to keep a connection open to the
- authenticating server for as long as that daemon lasts. This can drain
- the connection resources on a Microsoft NT server and cause it to run
- out of available connections. With <b>security = domain</b>,
- however, the Samba daemons connect to the PDC/BDC only for as long
- as is necessary to authenticate the user, and then drop the connection,
- thus conserving PDC connection resources.</p><p>And finally, acting in the same manner as an NT server
- authenticating to a PDC means that as part of the authentication
- reply, the Samba server gets the user identification information such
- as the user SID, the list of NT groups the user belongs to, etc. </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> Much of the text of this document
- was first published in the Web magazine <a href="http://www.linuxworld.com" target="_top">
- LinuxWorld</a> as the article <a href="http://www.linuxworld.com/linuxworld/lw-1998-10/lw-10-samba.html" target="_top">Doing
- the NIS/NT Samba</a>.</p></div></div></div></div><div class="part" lang="en"><div class="titlepage"><div><h1 class="title"><a name="optional"></a>Advanced Configuration</h1></div></div><div class="partintro" lang="en"><div><div><h1 class="title"><a name="id2859626"></a>Valuable Nuts and Bolts Information</h1></div></div><p>
-Samba has several features that you might want or might not want to use. The chapters in this part each cover specific Samba features.
-</p><div class="toc"><p><b>Table of Contents</b></p><dl><dt>9. <a href="#NetworkBrowsing">Samba / MS Windows Network Browsing Guide</a></dt><dd><dl><dt><a href="#id2862996">What is Browsing?</a></dt><dt><a href="#id2863646">Discussion</a></dt><dt><a href="#id2863809">How Browsing Functions</a></dt><dd><dl><dt><a href="#id2863936">Setting up WORKGROUP Browsing</a></dt><dt><a href="#id2864124">Setting up DOMAIN Browsing</a></dt><dt><a href="#browse-force-master">Forcing samba to be the master</a></dt><dt><a href="#id2864390">Making samba the domain master</a></dt><dt><a href="#id2864538">Note about broadcast addresses</a></dt><dt><a href="#id2864555">Multiple interfaces</a></dt><dt><a href="#id2864584">Use of the Remote Announce parameter</a></dt><dt><a href="#id2864695">Use of the Remote Browse Sync parameter</a></dt></dl></dd><dt><a href="#id2864763">WINS - The Windows Internetworking Name Server</a></dt><dd><dl><dt><a href="#id2863586">Setting up a WINS server</a></dt><dt><a href="#id2865218">WINS Replication</a></dt><dt><a href="#id2865243">Static WINS Entries</a></dt></dl></dd><dt><a href="#id2865274">Helpful Hints</a></dt><dd><dl><dt><a href="#id2865287">Windows Networking Protocols</a></dt><dt><a href="#id2865354">Name Resolution Order</a></dt></dl></dd><dt><a href="#id2865470">Technical Overview of browsing</a></dt><dd><dl><dt><a href="#id2865517">Browsing support in samba</a></dt><dt><a href="#id2865624">Problem resolution</a></dt><dt><a href="#id2865703">Browsing across subnets</a></dt></dl></dd></dl></dd><dt>10. <a href="#passdb">User information database</a></dt><dd><dl><dt><a href="#id2866099">Introduction</a></dt><dt><a href="#id2866152">Important Notes About Security</a></dt><dd><dl><dt><a href="#id2866314">Advantages of SMB Encryption</a></dt><dt><a href="#id2866353">Advantages of non-encrypted passwords</a></dt></dl></dd><dt><a href="#id2866388">The smbpasswd Command</a></dt><dt><a href="#id2866568">Plain text</a></dt><dt><a href="#id2866597">TDB</a></dt><dt><a href="#id2866613">LDAP</a></dt><dd><dl><dt><a href="#id2866621">Introduction</a></dt><dt><a href="#id2866721">Encrypted Password Database</a></dt><dt><a href="#id2866860">Supported LDAP Servers</a></dt><dt><a href="#id2866898">Schema and Relationship to the RFC 2307 posixAccount</a></dt><dt><a href="#id2867008">Configuring Samba with LDAP</a></dt><dt><a href="#id2867304">Accounts and Groups management</a></dt><dt><a href="#id2867341">Security and sambaAccount</a></dt><dt><a href="#id2867456">LDAP specials attributes for sambaAccounts</a></dt><dt><a href="#id2867737">Example LDIF Entries for a sambaAccount</a></dt></dl></dd><dt><a href="#id2867793">MySQL</a></dt><dd><dl><dt><a href="#id2867800">Creating the database</a></dt><dt><a href="#id2867854">Configuring</a></dt><dt><a href="#id2867999">Using plaintext passwords or encrypted password</a></dt><dt><a href="#id2868029">Getting non-column data from the table</a></dt></dl></dd><dt><a href="#id2868072">XML</a></dt></dl></dd><dt>11. <a href="#unix-permissions">UNIX Permission Bits and Windows NT Access Control Lists</a></dt><dd><dl><dt><a href="#id2865054">Viewing and changing UNIX permissions using the NT
- security dialogs</a></dt><dt><a href="#id2864937">How to view file security on a Samba share</a></dt><dt><a href="#id2868280">Viewing file ownership</a></dt><dt><a href="#id2868401">Viewing file or directory permissions</a></dt><dd><dl><dt><a href="#id2868484">File Permissions</a></dt><dt><a href="#id2868587">Directory Permissions</a></dt></dl></dd><dt><a href="#id2868637">Modifying file or directory permissions</a></dt><dt><a href="#id2868797">Interaction with the standard Samba create mask
- parameters</a></dt><dt><a href="#id2869113">Interaction with the standard Samba file attribute
- mapping</a></dt></dl></dd><dt>12. <a href="#groupmapping">Configuring Group Mapping</a></dt><dt>13. <a href="#printing">Printing Support</a></dt><dd><dl><dt><a href="#id2869498">Introduction</a></dt><dt><a href="#id2869614">Configuration</a></dt><dd><dl><dt><a href="#id2869661">Creating [print$]</a></dt><dt><a href="#id2869893">Setting Drivers for Existing Printers</a></dt><dt><a href="#id2869992">Support a large number of printers</a></dt><dt><a href="#id2870099">Adding New Printers via the Windows NT APW</a></dt><dt><a href="#id2870231">Samba and Printer Ports</a></dt></dl></dd><dt><a href="#id2869233">The Imprints Toolset</a></dt><dd><dl><dt><a href="#id2869259">What is Imprints?</a></dt><dt><a href="#id2870336">Creating Printer Driver Packages</a></dt><dt><a href="#id2870355">The Imprints server</a></dt><dt><a href="#id2870379">The Installation Client</a></dt></dl></dd><dt><a href="#id2869340">Diagnosis</a></dt><dd><dl><dt><a href="#id2869347">Introduction</a></dt><dt><a href="#id2870552">Debugging printer problems</a></dt><dt><a href="#id2870619">What printers do I have?</a></dt><dt><a href="#id2870661">Setting up printcap and print servers</a></dt><dt><a href="#id2870795">Job sent, no output</a></dt><dt><a href="#id2871344">Job sent, strange output</a></dt><dt><a href="#id2871420">Raw PostScript printed</a></dt><dt><a href="#id2871438">Advanced Printing</a></dt><dt><a href="#id2871464">Real debugging</a></dt></dl></dd></dl></dd><dt>14. <a href="#CUPS-printing">CUPS Printing Support</a></dt><dd><dl><dt><a href="#id2871008">Introduction</a></dt><dt><a href="#id2871067">Configuring smb.conf for CUPS</a></dt><dt><a href="#id2871607">CUPS - RAW Print Through Mode</a></dt><dt><a href="#id2871091">CUPS as a network PostScript RIP</a></dt><dt><a href="#id2872272">Windows Terminal Servers (WTS) as CUPS clients</a></dt><dt><a href="#id2872314">Setting up CUPS for driver download</a></dt><dt><a href="#id2872401">Sources of CUPS drivers / PPDs</a></dt><dd><dl><dt><a href="#id2872566">cupsaddsmb</a></dt></dl></dd><dt><a href="#id2872915">The CUPS Filter Chains</a></dt><dt><a href="#id2873302">CUPS Print Drivers and Devices</a></dt><dd><dl><dt><a href="#id2873339">Further printing steps</a></dt></dl></dd><dt><a href="#id2873758">Limiting the number of pages users can print</a></dt><dt><a href="#id2874367">Advanced Postscript Printing from MS Windows</a></dt><dt><a href="#id2874473">Auto-Deletion of CUPS spool files</a></dt></dl></dd><dt>15. <a href="#winbind">Unified Logons between Windows NT and UNIX using Winbind</a></dt><dd><dl><dt><a href="#id2874714">Abstract</a></dt><dt><a href="#id2874743">Introduction</a></dt><dt><a href="#id2874814">What Winbind Provides</a></dt><dd><dl><dt><a href="#id2872076">Target Uses</a></dt></dl></dd><dt><a href="#id2872107">How Winbind Works</a></dt><dd><dl><dt><a href="#id2872135">Microsoft Remote Procedure Calls</a></dt><dt><a href="#id2872170">Microsoft Active Directory Services</a></dt><dt><a href="#id2872192">Name Service Switch</a></dt><dt><a href="#id2875280">Pluggable Authentication Modules</a></dt><dt><a href="#id2875352">User and Group ID Allocation</a></dt><dt><a href="#id2875387">Result Caching</a></dt></dl></dd><dt><a href="#id2875414">Installation and Configuration</a></dt><dd><dl><dt><a href="#id2875442">Introduction</a></dt><dt><a href="#id2875518">Requirements</a></dt><dt><a href="#id2875611">Testing Things Out</a></dt></dl></dd><dt><a href="#id2877210">Limitations</a></dt><dt><a href="#id2877264">Conclusion</a></dt></dl></dd><dt>16. <a href="#AdvancedNetworkManagement">Advanced Network Manangement</a></dt><dd><dl><dt><a href="#id2875143">Configuring Samba Share Access Controls</a></dt><dd><dl><dt><a href="#id2874905">Share Permissions Management</a></dt></dl></dd><dt><a href="#id2874974">Remote Server Administration</a></dt><dt><a href="#id2875057">Network Logon Script Magic</a></dt><dd><dl><dt><a href="#id2877889">Adding printers without user intervention</a></dt></dl></dd></dl></dd><dt>17. <a href="#PolicyMgmt">System and Account Policies</a></dt><dd><dl><dt><a href="#id2877672">Creating and Managing System Policies</a></dt><dd><dl><dt><a href="#id2877925">Windows 9x/Me Policies</a></dt><dt><a href="#id2878014">Windows NT4 Style Policy Files</a></dt><dt><a href="#id2878140">MS Windows 200x / XP Professional Policies</a></dt></dl></dd><dt><a href="#id2878344">Managing Account/User Policies</a></dt><dd><dl><dt><a href="#id2878457">With Windows NT4/200x</a></dt><dt><a href="#id2878478">With a Samba PDC</a></dt></dl></dd><dt><a href="#id2878502">System Startup and Logon Processing Overview</a></dt></dl></dd><dt>18. <a href="#ProfileMgmt">Desktop Profile Management</a></dt><dd><dl><dt><a href="#id2877599">Roaming Profiles</a></dt><dd><dl><dt><a href="#id2877483">Samba Configuration for Profile Handling</a></dt><dt><a href="#id2879080">Windows Client Profile Configuration Information</a></dt><dt><a href="#id2879695">Sharing Profiles between W9x/Me and NT4/200x/XP workstations</a></dt><dt><a href="#id2879742">Profile Migration from Windows NT4/200x Server to Samba</a></dt></dl></dd><dt><a href="#id2879925">Mandatory profiles</a></dt><dt><a href="#id2879970">Creating/Managing Group Profiles</a></dt><dt><a href="#id2880011">Default Profile for Windows Users</a></dt><dd><dl><dt><a href="#id2880040">MS Windows 9x/Me</a></dt><dt><a href="#id2880129">MS Windows NT4 Workstation</a></dt><dt><a href="#id2880513">MS Windows 200x/XP</a></dt></dl></dd></dl></dd><dt>19. <a href="#InterdomainTrusts">Interdomain Trust Relationships</a></dt><dd><dl><dt><a href="#id2878684">Trust Relationship Background</a></dt><dt><a href="#id2881006">Native MS Windows NT4 Trusts Configuration</a></dt><dd><dl><dt><a href="#id2881019">NT4 as the Trusting Domain (ie. creating the trusted account)</a></dt><dt><a href="#id2881063">NT4 as the Trusted Domain (ie. creating trusted account's password)</a></dt></dl></dd><dt><a href="#id2881087">Configuring Samba NT-style Domain Trusts</a></dt><dd><dl><dt><a href="#id2881114">Samba-3 as the Trusting Domain</a></dt><dt><a href="#id2881210">Samba-3 as the Trusted Domain</a></dt></dl></dd></dl></dd><dt>20. <a href="#pam">PAM Configuration for Centrally Managed Authentication</a></dt><dd><dl><dt><a href="#id2880956">Samba and PAM</a></dt><dd><dl><dt><a href="#id2881738">PAM Configuration in smb.conf</a></dt><dt><a href="#id2881795">Password Synchronisation using pam_smbpass.so</a></dt></dl></dd><dt><a href="#id2882047">Distributed Authentication</a></dt></dl></dd><dt>21. <a href="#VFS">Stackable VFS modules</a></dt><dd><dl><dt><a href="#id2881331">Introduction and configuration</a></dt><dt><a href="#id2882249">Included modules</a></dt><dd><dl><dt><a href="#id2882256">audit</a></dt><dt><a href="#id2882295">extd_audit</a></dt><dt><a href="#id2882416">recycle</a></dt><dt><a href="#id2882554">netatalk</a></dt></dl></dd><dt><a href="#id2882592">VFS modules available elsewhere</a></dt><dd><dl><dt><a href="#id2882614">DatabaseFS</a></dt><dt><a href="#id2882669">vscan</a></dt></dl></dd></dl></dd><dt>22. <a href="#msdfs">Hosting a Microsoft Distributed File System tree on Samba</a></dt><dd><dl><dt><a href="#id2882214">Instructions</a></dt><dd><dl><dt><a href="#id2882961">Notes</a></dt></dl></dd></dl></dd><dt>23. <a href="#integrate-ms-networks">Integrating MS Windows networks with Samba</a></dt><dd><dl><dt><a href="#id2882745">Name Resolution in a pure Unix/Linux world</a></dt><dd><dl><dt><a href="#id2883178">/etc/hosts</a></dt><dt><a href="#id2883316">/etc/resolv.conf</a></dt><dt><a href="#id2883360">/etc/host.conf</a></dt><dt><a href="#id2883403">/etc/nsswitch.conf</a></dt></dl></dd><dt><a href="#id2883498">Name resolution as used within MS Windows networking</a></dt><dd><dl><dt><a href="#id2883030">The NetBIOS Name Cache</a></dt><dt><a href="#id2883069">The LMHOSTS file</a></dt><dt><a href="#id2883112">HOSTS file</a></dt><dt><a href="#id2883144">DNS Lookup</a></dt><dt><a href="#id2883156">WINS Lookup</a></dt></dl></dd></dl></dd><dt>24. <a href="#securing-samba">Securing Samba</a></dt><dd><dl><dt><a href="#id2883603">Introduction</a></dt><dt><a href="#id2883619">Using host based protection</a></dt><dt><a href="#id2884070">Using interface protection</a></dt><dt><a href="#id2884122">Using a firewall</a></dt><dt><a href="#id2884164">Using a IPC$ share deny</a></dt><dt><a href="#id2883724">NTLMv2 Security</a></dt><dt><a href="#id2883760">Upgrading Samba</a></dt></dl></dd><dt>25. <a href="#unicode">Unicode/Charsets</a></dt><dd><dl><dt><a href="#id2884358">What are charsets and unicode?</a></dt><dt><a href="#id2884428">Samba and charsets</a></dt><dt><a href="#id2884517">Conversion from old names</a></dt><dt><a href="#id2884562">Japanese charsets</a></dt></dl></dd><dt>26. <a href="#locking">File and Record Locking</a></dt><dd><dl><dt><a href="#id2884210">Discussion</a></dt><dt><a href="#id2884872">Samba Opportunistic Locking Control</a></dt><dt><a href="#id2884987">MS Windows Opportunistic Locking and Caching Controls</a></dt><dd><dl><dt><a href="#id2885212">Workstation Service Entries</a></dt><dt><a href="#id2885239">Server Service Entries</a></dt></dl></dd><dt><a href="#id2885320">Persistent Data Corruption</a></dt><dt><a href="#id2885350">Additional Reading</a></dt></dl></dd></dl></div></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="NetworkBrowsing"></a>Chapter9.Samba / MS Windows Network Browsing Guide</h2></div><div><div class="author"><h3 class="author">John H. Terpstra</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt>&lt;<a href="mailto:jht@samba.org">jht@samba.org</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate">July 5, 1998</p></div><div><p class="pubdate">Updated: April 21, 2003</p></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2862996">What is Browsing?</a></dt><dt><a href="#id2863646">Discussion</a></dt><dt><a href="#id2863809">How Browsing Functions</a></dt><dd><dl><dt><a href="#id2863936">Setting up WORKGROUP Browsing</a></dt><dt><a href="#id2864124">Setting up DOMAIN Browsing</a></dt><dt><a href="#browse-force-master">Forcing samba to be the master</a></dt><dt><a href="#id2864390">Making samba the domain master</a></dt><dt><a href="#id2864538">Note about broadcast addresses</a></dt><dt><a href="#id2864555">Multiple interfaces</a></dt><dt><a href="#id2864584">Use of the Remote Announce parameter</a></dt><dt><a href="#id2864695">Use of the Remote Browse Sync parameter</a></dt></dl></dd><dt><a href="#id2864763">WINS - The Windows Internetworking Name Server</a></dt><dd><dl><dt><a href="#id2863586">Setting up a WINS server</a></dt><dt><a href="#id2865218">WINS Replication</a></dt><dt><a href="#id2865243">Static WINS Entries</a></dt></dl></dd><dt><a href="#id2865274">Helpful Hints</a></dt><dd><dl><dt><a href="#id2865287">Windows Networking Protocols</a></dt><dt><a href="#id2865354">Name Resolution Order</a></dt></dl></dd><dt><a href="#id2865470">Technical Overview of browsing</a></dt><dd><dl><dt><a href="#id2865517">Browsing support in samba</a></dt><dt><a href="#id2865624">Problem resolution</a></dt><dt><a href="#id2865703">Browsing across subnets</a></dt></dl></dd></dl></div><p>
-This document contains detailed information as well as a fast track guide to
-implementing browsing across subnets and / or across workgroups (or domains).
-WINS is the best tool for resolution of NetBIOS names to IP addesses. WINS is
-NOT involved in browse list handling except by way of name to address resolution.
-</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-MS Windows 2000 and later can be configured to operate with NO NetBIOS
-over TCP/IP. Samba-3 and later also supports this mode of operation.
-When the use of NetBIOS over TCP/IP has been disabled then the primary
-means for resolution of MS Windows machine names is via DNS and Active Directory.
-The following information assumes that your site is running NetBIOS over TCP/IP.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2862996"></a>What is Browsing?</h2></div></div><p>
-To most people browsing means that they can see the MS Windows and Samba servers
-in the Network Neighborhood, and when the computer icon for a particular server is
-clicked, it opens up and shows the shares and printers available on the target server.
-</p><p>
-What seems so simple is in fact a very complex interaction of different technologies.
-The technologies (or methods) employed in making all of this work includes:
-</p><table class="simplelist" border="0" summary="Simple list"><tr><td>MS Windows machines register their presence to the network</td></tr><tr><td>Machines announce themselves to other machines on the network</td></tr><tr><td>One or more machine on the network collates the local announcements</td></tr><tr><td>The client machine finds the machine that has the collated list of machines</td></tr><tr><td>The client machine is able to resolve the machine names to IP addresses</td></tr><tr><td>The client machine is able to connect to a target machine</td></tr></table><p>
-The samba application that controls/manages browse list management and name resolution is
-called <tt>nmbd</tt>. The configuration parameters involved in nmbd's operation are:
-</p><pre class="programlisting">
- Browsing options:
- -----------------
- * os level
- lm announce
- lm interval
- * preferred master
- * local master
- * domain master
- browse list
- enhanced browsing
-
- Name Resolution Method:
- -----------------------
- * name resolve order
-
- WINS options:
- -------------
- dns proxy
- wins proxy
- * wins server
- * wins support
- wins hook
-</pre><p>
-WINS Server and WINS Support are mutually exclusive options. Those marked with an '*' are
-the only options that commonly MAY need to be modified. Even if not one of these parameters
-is set nmbd will still do it's job.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2863646"></a>Discussion</h2></div></div><p>
-Firstly, all MS Windows networking is based on SMB (Server Message
-Block) based messaging. SMB messaging may be implemented using NetBIOS or
-without NetBIOS. Samba implements NetBIOS by encapsulating it over TCP/IP.
-MS Windows products can do likewise. NetBIOS based networking uses broadcast
-messaging to affect browse list management. When running NetBIOS over
-TCP/IP this uses UDP based messaging. UDP messages can be broadcast or unicast.
-</p><p>
-Normally, only unicast UDP messaging can be forwarded by routers. The
-<b>remote announce</b>
-parameter to smb.conf helps to project browse announcements
-to remote network segments via unicast UDP. Similarly, the
-<b>remote browse sync</b> parameter of <tt>smb.conf</tt>
-implements browse list collation using unicast UDP.
-</p><p>
-Secondly, in those networks where Samba is the only SMB server technology
-wherever possible <tt>nmbd</tt> should be configured on one (1) machine as the WINS
-server. This makes it easy to manage the browsing environment. If each network
-segment is configured with it's own Samba WINS server, then the only way to
-get cross segment browsing to work is by using the
-<b>remote announce</b> and the <b>remote browse sync</b>
-parameters to your <tt>smb.conf</tt> file.
-</p><p>
-If only one WINS server is used for an entire multi-segment network then
-the use of the <b>remote announce</b> and the
-<b>remote browse sync</b> parameters should NOT be necessary.
-</p><p>
-As of Samba 3 WINS replication is being worked on. The bulk of the code has
-been committed, but it still needs maturation.
-</p><p>
-Right now samba WINS does not support MS-WINS replication. This means that
-when setting up Samba as a WINS server there must only be one <tt>nmbd</tt> configured
-as a WINS server on the network. Some sites have used multiple Samba WINS
-servers for redundancy (one server per subnet) and then used
-<b>remote browse sync</b> and <b>remote announce</b>
-to affect browse list collation across all
-segments. Note that this means clients will only resolve local names,
-and must be configured to use DNS to resolve names on other subnets in
-order to resolve the IP addresses of the servers they can see on other
-subnets. This setup is not recommended, but is mentioned as a practical
-consideration (ie: an 'if all else fails' scenario).
-</p><p>
-Lastly, take note that browse lists are a collection of unreliable broadcast
-messages that are repeated at intervals of not more than 15 minutes. This means
-that it will take time to establish a browse list and it can take up to 45
-minutes to stabilise, particularly across network segments.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2863809"></a>How Browsing Functions</h2></div></div><p>
-As stated above, MS Windows machines register their NetBIOS names
-(ie: the machine name for each service type in operation) on start
-up. Also, as stated above, the exact method by which this name registration
-takes place is determined by whether or not the MS Windows client/server
-has been given a WINS server address, whether or not LMHOSTS lookup
-is enabled, or if DNS for NetBIOS name resolution is enabled, etc.
-</p><p>
-In the case where there is no WINS server all name registrations as
-well as name lookups are done by UDP broadcast. This isolates name
-resolution to the local subnet, unless LMHOSTS is used to list all
-names and IP addresses. In such situations Samba provides a means by
-which the samba server name may be forcibly injected into the browse
-list of a remote MS Windows network (using the
-<b>remote announce</b> parameter).
-</p><p>
-Where a WINS server is used, the MS Windows client will use UDP
-unicast to register with the WINS server. Such packets can be routed
-and thus WINS allows name resolution to function across routed networks.
-</p><p>
-During the startup process an election will take place to create a
-local master browser if one does not already exist. On each NetBIOS network
-one machine will be elected to function as the domain master browser. This
-domain browsing has nothing to do with MS security domain control.
-Instead, the domain master browser serves the role of contacting each local
-master browser (found by asking WINS or from LMHOSTS) and exchanging browse
-list contents. This way every master browser will eventually obtain a complete
-list of all machines that are on the network. Every 11-15 minutes an election
-is held to determine which machine will be the master browser. By the nature of
-the election criteria used, the machine with the highest uptime, or the
-most senior protocol version, or other criteria, will win the election
-as domain master browser.
-</p><p>
-Clients wishing to browse the network make use of this list, but also depend
-on the availability of correct name resolution to the respective IP
-address/addresses.
-</p><p>
-Any configuration that breaks name resolution and/or browsing intrinsics
-will annoy users because they will have to put up with protracted
-inability to use the network services.
-</p><p>
-Samba supports a feature that allows forced synchonisation
-of browse lists across routed networks using the <b>remote
-browse sync</b> parameter in the <tt>smb.conf</tt> file.
-This causes Samba to contact the local master browser on a remote network and
-to request browse list synchronisation. This effectively bridges
-two networks that are separated by routers. The two remote
-networks may use either broadcast based name resolution or WINS
-based name resolution, but it should be noted that the <b>remote
-browse sync</b> parameter provides browse list synchronisation - and
-that is distinct from name to address resolution, in other
-words, for cross subnet browsing to function correctly it is
-essential that a name to address resolution mechanism be provided.
-This mechanism could be via DNS, <tt>/etc/hosts</tt>,
-and so on.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2863936"></a>Setting up WORKGROUP Browsing</h3></div></div><p>
-To set up cross subnet browsing on a network containing machines
-in up to be in a WORKGROUP, not an NT Domain you need to set up one
-Samba server to be the Domain Master Browser (note that this is *NOT*
-the same as a Primary Domain Controller, although in an NT Domain the
-same machine plays both roles). The role of a Domain master browser is
-to collate the browse lists from local master browsers on all the
-subnets that have a machine participating in the workgroup. Without
-one machine configured as a domain master browser each subnet would
-be an isolated workgroup, unable to see any machines on any other
-subnet. It is the presense of a domain master browser that makes
-cross subnet browsing possible for a workgroup.
-</p><p>
-In an WORKGROUP environment the domain master browser must be a
-Samba server, and there must only be one domain master browser per
-workgroup name. To set up a Samba server as a domain master browser,
-set the following option in the [global] section of the <tt>smb.conf</tt> file :
-</p><p>
-</p><pre class="programlisting">
- domain master = yes
-</pre><p>
-</p><p>
-The domain master browser should also preferrably be the local master
-browser for its own subnet. In order to achieve this set the following
-options in the [global] section of the <tt>smb.conf</tt> file :
-</p><p>
-</p><pre class="programlisting">
- domain master = yes
- local master = yes
- preferred master = yes
- os level = 65
-</pre><p>
-</p><p>
-The domain master browser may be the same machine as the WINS
-server, if you require.
-</p><p>
-Next, you should ensure that each of the subnets contains a
-machine that can act as a local master browser for the
-workgroup. Any MS Windows NT/2K/XP/2003 machine should be
-able to do this, as will Windows 9x machines (although these
-tend to get rebooted more often, so it's not such a good idea
-to use these). To make a Samba server a local master browser
-set the following options in the [global] section of the
-<tt>smb.conf</tt> file :
-</p><p>
-</p><pre class="programlisting">
- domain master = no
- local master = yes
- preferred master = yes
- os level = 65
-</pre><p>
-</p><p>
-Do not do this for more than one Samba server on each subnet,
-or they will war with each other over which is to be the local
-master browser.
-</p><p>
-The <b>local master</b> parameter allows Samba to act as a
-local master browser. The <b>preferred master</b> causes nmbd
-to force a browser election on startup and the <b>os level</b>
-parameter sets Samba high enough so that it should win any browser elections.
-</p><p>
-If you have an NT machine on the subnet that you wish to
-be the local master browser then you can disable Samba from
-becoming a local master browser by setting the following
-options in the <b>[global]</b> section of the
-<tt>smb.conf</tt> file :
-</p><p>
-</p><pre class="programlisting">
- domain master = no
- local master = no
- preferred master = no
- os level = 0
-</pre><p>
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2864124"></a>Setting up DOMAIN Browsing</h3></div></div><p>
-If you are adding Samba servers to a Windows NT Domain then
-you must not set up a Samba server as a domain master browser.
-By default, a Windows NT Primary Domain Controller for a Domain
-name is also the Domain master browser for that name, and many
-things will break if a Samba server registers the Domain master
-browser NetBIOS name (<i><tt>DOMAIN</tt></i>&lt;1B&gt;)
-with WINS instead of the PDC.
-</p><p>
-For subnets other than the one containing the Windows NT PDC
-you may set up Samba servers as local master browsers as
-described. To make a Samba server a local master browser set
-the following options in the <b>[global]</b> section
-of the <tt>smb.conf</tt> file :
-</p><p>
-</p><pre class="programlisting">
- domain master = no
- local master = yes
- preferred master = yes
- os level = 65
-</pre><p>
-</p><p>
-If you wish to have a Samba server fight the election with machines
-on the same subnet you may set the <b>os level</b> parameter
-to lower levels. By doing this you can tune the order of machines that
-will become local master browsers if they are running. For
-more details on this see the section <a href="#browse-force-master" title="Forcing samba to be the master">
-Forcing samba to be the master browser</a>
-below.
-</p><p>
-If you have Windows NT machines that are members of the domain
-on all subnets, and you are sure they will always be running then
-you can disable Samba from taking part in browser elections and
-ever becoming a local master browser by setting following options
-in the <b>[global]</b> section of the <tt>smb.conf</tt>
-file :
-</p><p>
-</p><pre class="programlisting">
- domain master = no
- local master = no
- preferred master = no
- os level = 0
-</pre><p>
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="browse-force-master"></a>Forcing samba to be the master</h3></div></div><p>
-Who becomes the <b>master browser</b> is determined by an election
-process using broadcasts. Each election packet contains a number of parameters
-which determine what precedence (bias) a host should have in the
-election. By default Samba uses a very low precedence and thus loses
-elections to just about anyone else.
-</p><p>
-If you want Samba to win elections then just set the <b>os level</b> global
-option in <tt>smb.conf</tt> to a higher number. It defaults to 0. Using 34
-would make it win all elections over every other system (except other
-samba systems!)
-</p><p>
-A <b>os level</b> of 2 would make it beat WfWg and Win95, but not MS Windows
-NT/2K Server. A MS Windows NT/2K Server domain controller uses level 32.
-</p><p>The maximum os level is 255</p><p>
-If you want samba to force an election on startup, then set the
-<b>preferred master</b> global option in <tt>smb.conf</tt> to &quot;yes&quot;. Samba will
-then have a slight advantage over other potential master browsers
-that are not preferred master browsers. Use this parameter with
-care, as if you have two hosts (whether they are windows 95 or NT or
-samba) on the same local subnet both set with <b>preferred master</b> to
-&quot;yes&quot;, then periodically and continually they will force an election
-in order to become the local master browser.
-</p><p>
-If you want samba to be a <b>domain master browser</b>, then it is
-recommended that you also set <b>preferred master</b> to &quot;yes&quot;, because
-samba will not become a domain master browser for the whole of your
-LAN or WAN if it is not also a local master browser on its own
-broadcast isolated subnet.
-</p><p>
-It is possible to configure two samba servers to attempt to become
-the domain master browser for a domain. The first server that comes
-up will be the domain master browser. All other samba servers will
-attempt to become the domain master browser every 5 minutes. They
-will find that another samba server is already the domain master
-browser and will fail. This provides automatic redundancy, should
-the current domain master browser fail.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2864390"></a>Making samba the domain master</h3></div></div><p>
-The domain master is responsible for collating the browse lists of
-multiple subnets so that browsing can occur between subnets. You can
-make samba act as the domain master by setting <b>domain master = yes</b>
-in <tt>smb.conf</tt>. By default it will not be a domain master.
-</p><p>
-Note that you should NOT set Samba to be the domain master for a
-workgroup that has the same name as an NT Domain.
-</p><p>
-When samba is the domain master and the master browser it will listen
-for master announcements (made roughly every twelve minutes) from local
-master browsers on other subnets and then contact them to synchronise
-browse lists.
-</p><p>
-If you want samba to be the domain master then I suggest you also set
-the <b>os level</b> high enough to make sure it wins elections, and set
-<b>preferred master</b> to &quot;yes&quot;, to get samba to force an election on
-startup.
-</p><p>
-Note that all your servers (including samba) and clients should be
-using a WINS server to resolve NetBIOS names. If your clients are only
-using broadcasting to resolve NetBIOS names, then two things will occur:
-</p><div class="orderedlist"><ol type="1"><li><p>
- your local master browsers will be unable to find a domain master
- browser, as it will only be looking on the local subnet.
- </p></li><li><p>
- if a client happens to get hold of a domain-wide browse list, and
- a user attempts to access a host in that list, it will be unable to
- resolve the NetBIOS name of that host.
- </p></li></ol></div><p>
-If, however, both samba and your clients are using a WINS server, then:
-</p><div class="orderedlist"><ol type="1"><li><p>
- your local master browsers will contact the WINS server and, as long as
- samba has registered that it is a domain master browser with the WINS
- server, your local master browser will receive samba's ip address
- as its domain master browser.
- </p></li><li><p>
- when a client receives a domain-wide browse list, and a user attempts
- to access a host in that list, it will contact the WINS server to
- resolve the NetBIOS name of that host. as long as that host has
- registered its NetBIOS name with the same WINS server, the user will
- be able to see that host.
- </p></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2864538"></a>Note about broadcast addresses</h3></div></div><p>
-If your network uses a &quot;0&quot; based broadcast address (for example if it
-ends in a 0) then you will strike problems. Windows for Workgroups
-does not seem to support a 0's broadcast and you will probably find
-that browsing and name lookups won't work.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2864555"></a>Multiple interfaces</h3></div></div><p>
-Samba now supports machines with multiple network interfaces. If you
-have multiple interfaces then you will need to use the <b>interfaces</b>
-option in <tt>smb.conf</tt> to configure them.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2864584"></a>Use of the <b>Remote Announce</b> parameter</h3></div></div><p>
-The <b>remote announce</b> parameter of
-<tt>smb.conf</tt> can be used to forcibly ensure
-that all the NetBIOS names on a network get announced to a remote network.
-The syntax of the <b>remote announce</b> parameter is:
-</p><pre class="programlisting">
- remote announce = a.b.c.d [e.f.g.h] ...
-</pre><p>
-_or_
-</p><pre class="programlisting">
- remote announce = a.b.c.d/WORKGROUP [e.f.g.h/WORKGROUP] ...
-</pre><p>
-
-where:
-</p><div class="variablelist"><dl><dt><span class="term"><i><tt>a.b.c.d</tt></i> and
-<i><tt>e.f.g.h</tt></i></span></dt><dd><p>is either the LMB (Local Master Browser) IP address
-or the broadcst address of the remote network.
-ie: the LMB is at 192.168.1.10, or the address
-could be given as 192.168.1.255 where the netmask
-is assumed to be 24 bits (255.255.255.0).
-When the remote announcement is made to the broadcast
-address of the remote network every host will receive
-our announcements. This is noisy and therefore
-undesirable but may be necessary if we do NOT know
-the IP address of the remote LMB.</p></dd><dt><span class="term"><i><tt>WORKGROUP</tt></i></span></dt><dd><p>is optional and can be either our own workgroup
-or that of the remote network. If you use the
-workgroup name of the remote network then our
-NetBIOS machine names will end up looking like
-they belong to that workgroup, this may cause
-name resolution problems and should be avoided.
-</p></dd></dl></div><p>
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2864695"></a>Use of the <b>Remote Browse Sync</b> parameter</h3></div></div><p>
-The <b>remote browse sync</b> parameter of
-<tt>smb.conf</tt> is used to announce to
-another LMB that it must synchronise it's NetBIOS name list with our
-Samba LMB. It works ONLY if the Samba server that has this option is
-simultaneously the LMB on it's network segment.
-</p><p>
-The syntax of the <b>remote browse sync</b> parameter is:
-
-</p><pre class="programlisting">
-remote browse sync = <i><tt>a.b.c.d</tt></i>
-</pre><p>
-
-where <i><tt>a.b.c.d</tt></i> is either the IP address of the
-remote LMB or else is the network broadcast address of the remote segment.
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2864763"></a>WINS - The Windows Internetworking Name Server</h2></div></div><p>
-Use of WINS (either Samba WINS _or_ MS Windows NT Server WINS) is highly
-recommended. Every NetBIOS machine registers it's name together with a
-name_type value for each of of several types of service it has available.
-eg: It registers it's name directly as a unique (the type 0x03) name.
-It also registers it's name if it is running the lanmanager compatible
-server service (used to make shares and printers available to other users)
-by registering the server (the type 0x20) name.
-</p><p>
-All NetBIOS names are up to 15 characters in length. The name_type variable
-is added to the end of the name - thus creating a 16 character name. Any
-name that is shorter than 15 characters is padded with spaces to the 15th
-character. ie: All NetBIOS names are 16 characters long (including the
-name_type information).
-</p><p>
-WINS can store these 16 character names as they get registered. A client
-that wants to log onto the network can ask the WINS server for a list
-of all names that have registered the NetLogon service name_type. This saves
-broadcast traffic and greatly expedites logon processing. Since broadcast
-name resolution can not be used across network segments this type of
-information can only be provided via WINS _or_ via statically configured
-<tt>lmhosts</tt> files that must reside on all clients in the
-absence of WINS.
-</p><p>
-WINS also serves the purpose of forcing browse list synchronisation by all
-LMB's. LMB's must synchronise their browse list with the DMB (domain master
-browser) and WINS helps the LMB to identify it's DMB. By definition this
-will work only within a single workgroup. Note that the domain master browser
-has NOTHING to do with what is referred to as an MS Windows NT Domain. The
-later is a reference to a security environment while the DMB refers to the
-master controller for browse list information only.
-</p><p>
-Use of WINS will work correctly only if EVERY client TCP/IP protocol stack
-has been configured to use the WINS server/s. Any client that has not been
-configured to use the WINS server will continue to use only broadcast based
-name registration so that WINS may NEVER get to know about it. In any case,
-machines that have not registered with a WINS server will fail name to address
-lookup attempts by other clients and will therefore cause workstation access
-errors.
-</p><p>
-To configure Samba as a WINS server just add
-<b>wins support = yes</b> to the <tt>smb.conf</tt>
-file [globals] section.
-</p><p>
-To configure Samba to register with a WINS server just add
-&quot;wins server = a.b.c.d&quot; to your smb.conf file [globals] section.
-</p><div class="important" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Important</h3><p>
-Never use both <b>wins support = yes</b> together
-with <b>wins server = a.b.c.d</b>
-particularly not using it's own IP address.
-Specifying both will cause nmbd to refuse to start!
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2863586"></a>Setting up a WINS server</h3></div></div><p>
-Either a Samba machine or a Windows NT Server machine may be set up
-as a WINS server. To set a Samba machine to be a WINS server you must
-add the following option to the <tt>smb.conf</tt> file on the selected machine :
-in the [globals] section add the line
-</p><p>
-</p><pre class="programlisting">
- wins support = yes
-</pre><p>
-</p><p>
-Versions of Samba prior to 1.9.17 had this parameter default to
-yes. If you have any older versions of Samba on your network it is
-strongly suggested you upgrade to a recent version, or at the very
-least set the parameter to 'no' on all these machines.
-</p><p>
-Machines with <b>wins support = yes</b> will keep a list of
-all NetBIOS names registered with them, acting as a DNS for NetBIOS names.
-</p><p>
-You should set up only ONE wins server. Do NOT set the
-<b>wins support = yes</b> option on more than one Samba
-server.
-</p><p>
-To set up a Windows NT Server as a WINS server you need to set up
-the WINS service - see your NT documentation for details. Note that
-Windows NT WINS Servers can replicate to each other, allowing more
-than one to be set up in a complex subnet environment. As Microsoft
-refuse to document these replication protocols Samba cannot currently
-participate in these replications. It is possible in the future that
-a Samba-&gt;Samba WINS replication protocol may be defined, in which
-case more than one Samba machine could be set up as a WINS server
-but currently only one Samba server should have the
-<b>wins support = yes</b> parameter set.
-</p><p>
-After the WINS server has been configured you must ensure that all
-machines participating on the network are configured with the address
-of this WINS server. If your WINS server is a Samba machine, fill in
-the Samba machine IP address in the &quot;Primary WINS Server&quot; field of
-the &quot;Control Panel-&gt;Network-&gt;Protocols-&gt;TCP-&gt;WINS Server&quot; dialogs
-in Windows 95 or Windows NT. To tell a Samba server the IP address
-of the WINS server add the following line to the [global] section of
-all <tt>smb.conf</tt> files :
-</p><p>
-</p><pre class="programlisting">
- wins server = &lt;name or IP address&gt;
-</pre><p>
-</p><p>
-where &lt;name or IP address&gt; is either the DNS name of the WINS server
-machine or its IP address.
-</p><p>
-Note that this line MUST NOT BE SET in the <tt>smb.conf</tt> file of the Samba
-server acting as the WINS server itself. If you set both the
-<b>wins support = yes</b> option and the
-<b>wins server = &lt;name&gt;</b> option then
-nmbd will fail to start.
-</p><p>
-There are two possible scenarios for setting up cross subnet browsing.
-The first details setting up cross subnet browsing on a network containing
-Windows 95, Samba and Windows NT machines that are not configured as
-part of a Windows NT Domain. The second details setting up cross subnet
-browsing on networks that contain NT Domains.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2865218"></a>WINS Replication</h3></div></div><p>
-Samba-3 permits WINS replication through the use of the <tt>wrepld</tt> utility.
-This tool is not currently capable of being used as it is still in active development.
-As soon as this tool becomes moderately functional we will prepare man pages and enhance this
-section of the documentation to provide usage and technical details.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2865243"></a>Static WINS Entries</h3></div></div><p>
-New to Samba-3 is a tool called <tt>winsedit</tt> that may be used to add
-static WINS entries to the WINS database. This tool can be used also to modify entries
-existing in the WINS database.
-</p><p>
-The development of the winsedit tool was made necessary due to the migration
-of the older style wins.dat file into a new tdb binary backend data store.
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2865274"></a>Helpful Hints</h2></div></div><p>
-The following hints should be carefully considered as they are stumbling points
-for many new network administrators.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2865287"></a>Windows Networking Protocols</h3></div></div><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p>
-Do NOT use more than one (1) protocol on MS Windows machines
-</p></div><p>
-A very common cause of browsing problems results from installing more than
-one protocol on an MS Windows machine.
-</p><p>
-Every NetBIOS machine takes part in a process of electing the LMB (and DMB)
-every 15 minutes. A set of election criteria is used to determine the order
-of precidence for winning this election process. A machine running Samba or
-Windows NT will be biased so that the most suitable machine will predictably
-win and thus retain it's role.
-</p><p>
-The election process is &quot;fought out&quot; so to speak over every NetBIOS network
-interface. In the case of a Windows 9x machine that has both TCP/IP and IPX
-installed and has NetBIOS enabled over both protocols the election will be
-decided over both protocols. As often happens, if the Windows 9x machine is
-the only one with both protocols then the LMB may be won on the NetBIOS
-interface over the IPX protocol. Samba will then lose the LMB role as Windows
-9x will insist it knows who the LMB is. Samba will then cease to function
-as an LMB and thus browse list operation on all TCP/IP only machines will
-fail.
-</p><p><span class="emphasis"><em>
-Windows 95, 98, 98se, Me are referred to generically as Windows 9x.
-The Windows NT4, 2000, XP and 2003 use common protocols. These are roughly
-referred to as the WinNT family, but it should be recognised that 2000 and
-XP/2003 introduce new protocol extensions that cause them to behave
-differently from MS Windows NT4. Generally, where a server does NOT support
-the newer or extended protocol, these will fall back to the NT4 protocols.
-</em></span></p><p>
-The safest rule of all to follow it this - USE ONLY ONE PROTOCOL!
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2865354"></a>Name Resolution Order</h3></div></div><p>
-Resolution of NetBIOS names to IP addresses can take place using a number
-of methods. The only ones that can provide NetBIOS name_type information
-are:</p><table class="simplelist" border="0" summary="Simple list"><tr><td>WINS: the best tool!</td></tr><tr><td>LMHOSTS: is static and hard to maintain.</td></tr><tr><td>Broadcast: uses UDP and can not resolve names across remote segments.</td></tr></table><p>
-Alternative means of name resolution includes:</p><table class="simplelist" border="0" summary="Simple list"><tr><td>/etc/hosts: is static, hard to maintain, and lacks name_type info</td></tr><tr><td>DNS: is a good choice but lacks essential name_type info.</td></tr></table><p>
-Many sites want to restrict DNS lookups and want to avoid broadcast name
-resolution traffic. The &quot;name resolve order&quot; parameter is of great help here.
-The syntax of the &quot;name resolve order&quot; parameter is:
-</p><pre class="programlisting">
-name resolve order = wins lmhosts bcast host
-</pre><p>
-_or_
-</p><pre class="programlisting">
-name resolve order = wins lmhosts (eliminates bcast and host)
-</pre><p>
-The default is:
-</p><pre class="programlisting">
-name resolve order = host lmhost wins bcast
-</pre><p>
-where &quot;host&quot; refers the the native methods used by the Unix system
-to implement the gethostbyname() function call. This is normally
-controlled by <tt>/etc/host.conf</tt>, <tt>/etc/nsswitch.conf</tt> and <tt>/etc/resolv.conf</tt>.
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2865470"></a>Technical Overview of browsing</h2></div></div><p>
-SMB networking provides a mechanism by which clients can access a list
-of machines in a network, a so-called <b>browse list</b>. This list
-contains machines that are ready to offer file and/or print services
-to other machines within the network. Thus it does not include
-machines which aren't currently able to do server tasks. The browse
-list is heavily used by all SMB clients. Configuration of SMB
-browsing has been problematic for some Samba users, hence this
-document.
-</p><p>
-MS Windows 2000 and later, as with Samba 3 and later, can be
-configured to not use NetBIOS over TCP/IP. When configured this way
-it is imperative that name resolution (using DNS/LDAP/ADS) be correctly
-configured and operative. Browsing will NOT work if name resolution
-from SMB machine names to IP addresses does not function correctly.
-</p><p>
-Where NetBIOS over TCP/IP is enabled use of a WINS server is highly
-recommended to aid the resolution of NetBIOS (SMB) names to IP addresses.
-WINS allows remote segment clients to obtain NetBIOS name_type information
-that can NOT be provided by any other means of name resolution.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2865517"></a>Browsing support in samba</h3></div></div><p>
-Samba facilitates browsing. The browsing is supported by nmbd
-and is also controlled by options in the <tt>smb.conf</tt> file.
-Samba can act as a local browse master for a workgroup and the ability
-to support domain logons and scripts is now available.
-</p><p>
-Samba can also act as a domain master browser for a workgroup. This
-means that it will collate lists from local browse masters into a
-wide area network server list. In order for browse clients to
-resolve the names they may find in this list, it is recommended that
-both samba and your clients use a WINS server.
-</p><p>
-Note that you should NOT set Samba to be the domain master for a
-workgroup that has the same name as an NT Domain: on each wide area
-network, you must only ever have one domain master browser per workgroup,
-regardless of whether it is NT, Samba or any other type of domain master
-that is providing this service.
-</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-Nmbd can be configured as a WINS server, but it is not
-necessary to specifically use samba as your WINS server. MS Windows
-NT4, Server or Advanced Server 2000 or 2003 can be configured as
-your WINS server. In a mixed NT/2000/2003 server and samba environment on
-a Wide Area Network, it is recommended that you use the Microsoft
-WINS server capabilities. In a samba-only environment, it is
-recommended that you use one and only one Samba server as your WINS server.
-</p></div><p>
-To get browsing to work you need to run nmbd as usual, but will need
-to use the <b>workgroup</b> option in <tt>smb.conf</tt>
-to control what workgroup Samba becomes a part of.
-</p><p>
-Samba also has a useful option for a Samba server to offer itself for
-browsing on another subnet. It is recommended that this option is only
-used for 'unusual' purposes: announcements over the internet, for
-example. See <b>remote announce</b> in the
-<tt>smb.conf</tt> man page.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2865624"></a>Problem resolution</h3></div></div><p>
-If something doesn't work then hopefully the log.nmb file will help
-you track down the problem. Try a debug level of 2 or 3 for finding
-problems. Also note that the current browse list usually gets stored
-in text form in a file called <tt>browse.dat</tt>.
-</p><p>
-Note that if it doesn't work for you, then you should still be able to
-type the server name as <tt>\\SERVER</tt> in filemanager then
-hit enter and filemanager should display the list of available shares.
-</p><p>
-Some people find browsing fails because they don't have the global
-<b>guest account</b> set to a valid account. Remember that the
-IPC$ connection that lists the shares is done as guest, and thus you must
-have a valid guest account.
-</p><p><span class="emphasis"><em>
-MS Windows 2000 and upwards (as with Samba) can be configured to disallow
-anonymous (ie: Guest account) access to the IPC$ share. In that case, the
-MS Windows 2000/XP/2003 machine acting as an SMB/CIFS client will use the
-name of the currently logged in user to query the IPC$ share. MS Windows
-9X clients are not able to do this and thus will NOT be able to browse
-server resources.
-</em></span></p><p>
-The other big problem people have is that their broadcast address,
-netmask or IP address is wrong (specified with the &quot;interfaces&quot; option
-in <tt>smb.conf</tt>)
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2865703"></a>Browsing across subnets</h3></div></div><p>
-Since the release of Samba 1.9.17(alpha1) Samba has been
-updated to enable it to support the replication of browse lists
-across subnet boundaries. New code and options have been added to
-achieve this. This section describes how to set this feature up
-in different settings.
-</p><p>
-To see browse lists that span TCP/IP subnets (ie. networks separated
-by routers that don't pass broadcast traffic) you must set up at least
-one WINS server. The WINS server acts as a DNS for NetBIOS names, allowing
-NetBIOS name to IP address translation to be done by doing a direct
-query of the WINS server. This is done via a directed UDP packet on
-port 137 to the WINS server machine. The reason for a WINS server is
-that by default, all NetBIOS name to IP address translation is done
-by broadcasts from the querying machine. This means that machines
-on one subnet will not be able to resolve the names of machines on
-another subnet without using a WINS server.
-</p><p>
-Remember, for browsing across subnets to work correctly, all machines,
-be they Windows 95, Windows NT, or Samba servers must have the IP address
-of a WINS server given to them by a DHCP server, or by manual configuration
-(for Win95 and WinNT, this is in the TCP/IP Properties, under Network
-settings) for Samba this is in the <tt>smb.conf</tt> file.
-</p><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2865754"></a>How does cross subnet browsing work ?</h4></div></div><p>
-Cross subnet browsing is a complicated dance, containing multiple
-moving parts. It has taken Microsoft several years to get the code
-that achieves this correct, and Samba lags behind in some areas.
-Samba is capable of cross subnet browsing when configured correctly.
-</p><p>
-Consider a network set up as follows :
-</p><p>
-</p><pre class="programlisting">
- (DMB)
- N1_A N1_B N1_C N1_D N1_E
- | | | | |
- -------------------------------------------------------
- | subnet 1 |
- +---+ +---+
- |R1 | Router 1 Router 2 |R2 |
- +---+ +---+
- | |
- | subnet 2 subnet 3 |
- -------------------------- ------------------------------------
- | | | | | | | |
- N2_A N2_B N2_C N2_D N3_A N3_B N3_C N3_D
- (WINS)
-</pre><p>
-</p><p>
-Consisting of 3 subnets (1, 2, 3) connected by two routers
-(R1, R2) - these do not pass broadcasts. Subnet 1 has 5 machines
-on it, subnet 2 has 4 machines, subnet 3 has 4 machines. Assume
-for the moment that all these machines are configured to be in the
-same workgroup (for simplicities sake). Machine N1_C on subnet 1
-is configured as Domain Master Browser (ie. it will collate the
-browse lists for the workgroup). Machine N2_D is configured as
-WINS server and all the other machines are configured to register
-their NetBIOS names with it.
-</p><p>
-As all these machines are booted up, elections for master browsers
-will take place on each of the three subnets. Assume that machine
-N1_C wins on subnet 1, N2_B wins on subnet 2, and N3_D wins on
-subnet 3 - these machines are known as local master browsers for
-their particular subnet. N1_C has an advantage in winning as the
-local master browser on subnet 1 as it is set up as Domain Master
-Browser.
-</p><p>
-On each of the three networks, machines that are configured to
-offer sharing services will broadcast that they are offering
-these services. The local master browser on each subnet will
-receive these broadcasts and keep a record of the fact that
-the machine is offering a service. This list of records is
-the basis of the browse list. For this case, assume that
-all the machines are configured to offer services so all machines
-will be on the browse list.
-</p><p>
-For each network, the local master browser on that network is
-considered 'authoritative' for all the names it receives via
-local broadcast. This is because a machine seen by the local
-master browser via a local broadcast must be on the same
-network as the local master browser and thus is a 'trusted'
-and 'verifiable' resource. Machines on other networks that
-the local master browsers learn about when collating their
-browse lists have not been directly seen - these records are
-called 'non-authoritative'.
-</p><p>
-At this point the browse lists look as follows (these are
-the machines you would see in your network neighborhood if
-you looked in it on a particular network right now).
-</p><p>
-</p><pre class="programlisting">
-Subnet Browse Master List
------- ------------- ----
-Subnet1 N1_C N1_A, N1_B, N1_C, N1_D, N1_E
-
-Subnet2 N2_B N2_A, N2_B, N2_C, N2_D
-
-Subnet3 N3_D N3_A, N3_B, N3_C, N3_D
-</pre><p>
-</p><p>
-Note that at this point all the subnets are separate, no
-machine is seen across any of the subnets.
-</p><p>
-Now examine subnet 2. As soon as N2_B has become the local
-master browser it looks for a Domain master browser to synchronize
-its browse list with. It does this by querying the WINS server
-(N2_D) for the IP address associated with the NetBIOS name
-WORKGROUP&lt;1B&gt;. This name was registerd by the Domain master
-browser (N1_C) with the WINS server as soon as it was booted.
-</p><p>
-Once N2_B knows the address of the Domain master browser it
-tells it that is the local master browser for subnet 2 by
-sending a MasterAnnouncement packet as a UDP port 138 packet.
-It then synchronizes with it by doing a NetServerEnum2 call. This
-tells the Domain Master Browser to send it all the server
-names it knows about. Once the domain master browser receives
-the MasterAnnouncement packet it schedules a synchronization
-request to the sender of that packet. After both synchronizations
-are done the browse lists look like :
-</p><p>
-</p><pre class="programlisting">
-Subnet Browse Master List
------- ------------- ----
-Subnet1 N1_C N1_A, N1_B, N1_C, N1_D, N1_E,
- N2_A(*), N2_B(*), N2_C(*), N2_D(*)
-
-Subnet2 N2_B N2_A, N2_B, N2_C, N2_D
- N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*)
-
-Subnet3 N3_D N3_A, N3_B, N3_C, N3_D
-
-Servers with a (*) after them are non-authoritative names.
-</pre><p>
-</p><p>
-At this point users looking in their network neighborhood on
-subnets 1 or 2 will see all the servers on both, users on
-subnet 3 will still only see the servers on their own subnet.
-</p><p>
-The same sequence of events that occured for N2_B now occurs
-for the local master browser on subnet 3 (N3_D). When it
-synchronizes browse lists with the domain master browser (N1_A)
-it gets both the server entries on subnet 1, and those on
-subnet 2. After N3_D has synchronized with N1_C and vica-versa
-the browse lists look like.
-</p><p>
-</p><pre class="programlisting">
-Subnet Browse Master List
------- ------------- ----
-Subnet1 N1_C N1_A, N1_B, N1_C, N1_D, N1_E,
- N2_A(*), N2_B(*), N2_C(*), N2_D(*),
- N3_A(*), N3_B(*), N3_C(*), N3_D(*)
-
-Subnet2 N2_B N2_A, N2_B, N2_C, N2_D
- N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*)
-
-Subnet3 N3_D N3_A, N3_B, N3_C, N3_D
- N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*),
- N2_A(*), N2_B(*), N2_C(*), N2_D(*)
-
-Servers with a (*) after them are non-authoritative names.
-</pre><p>
-</p><p>
-At this point users looking in their network neighborhood on
-subnets 1 or 3 will see all the servers on all sunbets, users on
-subnet 2 will still only see the servers on subnets 1 and 2, but not 3.
-</p><p>
-Finally, the local master browser for subnet 2 (N2_B) will sync again
-with the domain master browser (N1_C) and will recieve the missing
-server entries. Finally - and as a steady state (if no machines
-are removed or shut off) the browse lists will look like :
-</p><p>
-</p><pre class="programlisting">
-Subnet Browse Master List
------- ------------- ----
-Subnet1 N1_C N1_A, N1_B, N1_C, N1_D, N1_E,
- N2_A(*), N2_B(*), N2_C(*), N2_D(*),
- N3_A(*), N3_B(*), N3_C(*), N3_D(*)
-
-Subnet2 N2_B N2_A, N2_B, N2_C, N2_D
- N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*)
- N3_A(*), N3_B(*), N3_C(*), N3_D(*)
-
-Subnet3 N3_D N3_A, N3_B, N3_C, N3_D
- N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*),
- N2_A(*), N2_B(*), N2_C(*), N2_D(*)
-
-Servers with a (*) after them are non-authoritative names.
-</pre><p>
-</p><p>
-Synchronizations between the domain master browser and local
-master browsers will continue to occur, but this should be a
-steady state situation.
-</p><p>
-If either router R1 or R2 fails the following will occur:
-</p><div class="orderedlist"><ol type="1"><li><p>
- Names of computers on each side of the inaccessible network fragments
- will be maintained for as long as 36 minutes, in the network neighbourhood
- lists.
- </p></li><li><p>
- Attempts to connect to these inaccessible computers will fail, but the
- names will not be removed from the network neighbourhood lists.
- </p></li><li><p>
- If one of the fragments is cut off from the WINS server, it will only
- be able to access servers on its local subnet, by using subnet-isolated
- broadcast NetBIOS name resolution. The effects are similar to that of
- losing access to a DNS server.
- </p></li></ol></div></div></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="passdb"></a>Chapter10.User information database</h2></div><div><div class="author"><h3 class="author">Jelmer R. Vernooij</h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt>&lt;<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author">Gerald (Jerry) Carter</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt>&lt;<a href="mailto:jerry@samba.org">jerry@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author">Jeremy Allison</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt>&lt;<a href="mailto:jra@samba.org">jra@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author">John H. Terpstra</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt>&lt;<a href="mailto:jht@samba.org">jht@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author">Olivier (lem) Lemaire</h3><div class="affiliation"><span class="orgname">IDEALX<br></span><div class="address"><p><tt>&lt;<a href="mailto:olem@IDEALX.org">olem@IDEALX.org</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate">February 2003</p></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2866099">Introduction</a></dt><dt><a href="#id2866152">Important Notes About Security</a></dt><dd><dl><dt><a href="#id2866314">Advantages of SMB Encryption</a></dt><dt><a href="#id2866353">Advantages of non-encrypted passwords</a></dt></dl></dd><dt><a href="#id2866388">The smbpasswd Command</a></dt><dt><a href="#id2866568">Plain text</a></dt><dt><a href="#id2866597">TDB</a></dt><dt><a href="#id2866613">LDAP</a></dt><dd><dl><dt><a href="#id2866621">Introduction</a></dt><dt><a href="#id2866721">Encrypted Password Database</a></dt><dt><a href="#id2866860">Supported LDAP Servers</a></dt><dt><a href="#id2866898">Schema and Relationship to the RFC 2307 posixAccount</a></dt><dt><a href="#id2867008">Configuring Samba with LDAP</a></dt><dt><a href="#id2867304">Accounts and Groups management</a></dt><dt><a href="#id2867341">Security and sambaAccount</a></dt><dt><a href="#id2867456">LDAP specials attributes for sambaAccounts</a></dt><dt><a href="#id2867737">Example LDIF Entries for a sambaAccount</a></dt></dl></dd><dt><a href="#id2867793">MySQL</a></dt><dd><dl><dt><a href="#id2867800">Creating the database</a></dt><dt><a href="#id2867854">Configuring</a></dt><dt><a href="#id2867999">Using plaintext passwords or encrypted password</a></dt><dt><a href="#id2868029">Getting non-column data from the table</a></dt></dl></dd><dt><a href="#id2868072">XML</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2866099"></a>Introduction</h2></div></div><p>Old windows clients send plain text passwords over the wire.
- Samba can check these passwords by crypting them and comparing them
- to the hash stored in the unix user database.
- </p><p>
- Newer windows clients send encrypted passwords (so-called
- Lanman and NT hashes) over
- the wire, instead of plain text passwords. The newest clients
- will only send encrypted passwords and refuse to send plain text
- passwords, unless their registry is tweaked.
- </p><p>These passwords can't be converted to unix style encrypted
- passwords. Because of that you can't use the standard unix
- user database, and you have to store the Lanman and NT hashes
- somewhere else. </p><p>Next to a differently encrypted passwords,
- windows also stores certain data for each user
- that is not stored in a unix user database, e.g.
- workstations the user may logon from, the location where his/her
- profile is stored, etc.
- Samba retrieves and stores this information using a &quot;passdb backend&quot;.
- Commonly
- available backends are LDAP, plain text file, MySQL and nisplus.
- For more information, see the documentation about the
- <b>passdb backend = </b> parameter.
- </p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2866152"></a>Important Notes About Security</h2></div></div><p>The unix and SMB password encryption techniques seem similar
- on the surface. This similarity is, however, only skin deep. The unix
- scheme typically sends clear text passwords over the network when
- logging in. This is bad. The SMB encryption scheme never sends the
- cleartext password over the network but it does store the 16 byte
- hashed values on disk. This is also bad. Why? Because the 16 byte hashed
- values are a &quot;password equivalent&quot;. You cannot derive the user's
- password from them, but they could potentially be used in a modified
- client to gain access to a server. This would require considerable
- technical knowledge on behalf of the attacker but is perfectly possible.
- You should thus treat the data stored in whatever
- passdb backend you use (smbpasswd file, ldap, mysql) as though it contained the
- cleartext passwords of all your users. Its contents must be kept
- secret, and the file should be protected accordingly.</p><p>Ideally we would like a password scheme which neither requires
- plain text passwords on the net or on disk. Unfortunately this
- is not available as Samba is stuck with being compatible with
- other SMB systems (WinNT, WfWg, Win95 etc). </p><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p>Note that Windows NT 4.0 Service pack 3 changed the
- default for permissible authentication so that plaintext
- passwords are <span class="emphasis"><em>never</em></span> sent over the wire.
- The solution to this is either to switch to encrypted passwords
- with Samba or edit the Windows NT registry to re-enable plaintext
- passwords. See the document WinNT.txt for details on how to do
- this.</p><p>Other Microsoft operating systems which also exhibit
- this behavior includes</p><p> These versions of MS Windows do not support full domain
- security protocols, although they may log onto a domain environment.
- Of these Only MS Windows XP Home does NOT support domain logons.</p><table class="simplelist" border="0" summary="Simple list"><tr><td>MS DOS Network client 3.0 with
- the basic network redirector installed</td></tr><tr><td>Windows 95 with the network redirector
- update installed</td></tr><tr><td>Windows 98 [se]</td></tr><tr><td>Windows Me</td></tr><tr><td>Windows XP Home</td></tr></table><p> The following versions of MS Windows fully support domain
- security protocols.</p><table class="simplelist" border="0" summary="Simple list"><tr><td>Windows NT 3.5x</td></tr><tr><td>Windows NT 4.0</td></tr><tr><td>Windows 2000 Professional</td></tr><tr><td>Windows 200x Server/Advanced Server</td></tr><tr><td>Windows XP Professional</td></tr></table></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>All current release of
- Microsoft SMB/CIFS clients support authentication via the
- SMB Challenge/Response mechanism described here. Enabling
- clear text authentication does not disable the ability
- of the client to participate in encrypted authentication.</p></div><p>MS Windows clients will cache the encrypted password alone.
- Even when plain text passwords are re-enabled, through the appropriate
- registry change, the plain text password is NEVER cached. This means that
- in the event that a network connections should become disconnected (broken)
- only the cached (encrypted) password will be sent to the resource server
- to affect a auto-reconnect. If the resource server does not support encrypted
- passwords the auto-reconnect will fail. <span class="emphasis"><em>USE OF ENCRYPTED PASSWORDS
- IS STRONGLY ADVISED.</em></span></p><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2866314"></a>Advantages of SMB Encryption</h3></div></div><table class="simplelist" border="0" summary="Simple list"><tr><td>Plain text passwords are not passed across
- the network. Someone using a network sniffer cannot just
- record passwords going to the SMB server.</td></tr><tr><td>WinNT doesn't like talking to a server
- that does not support encrypted passwords. It will refuse
- to browse the server if the server is also in user level
- security mode. It will insist on prompting the user for the
- password on each connection, which is very annoying. The
- only things you can do to stop this is to use SMB encryption.
- </td></tr><tr><td>Encrypted password support allows automatic share
- (resource) reconnects.</td></tr></table></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2866353"></a>Advantages of non-encrypted passwords</h3></div></div><table class="simplelist" border="0" summary="Simple list"><tr><td>Plain text passwords are not kept
- on disk, and are NOT cached in memory. </td></tr><tr><td>Uses same password file as other unix
- services such as login and ftp</td></tr><tr><td>Use of other services (such as telnet and ftp) which
- send plain text passwords over the net, so sending them for SMB
- isn't such a big deal.</td></tr></table></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2866388"></a>The smbpasswd Command</h2></div></div><p>The smbpasswd utility is a utility similar to the
- <b>passwd</b> or <b>yppasswd</b> programs.
- It maintains the two 32 byte password fields in the passdb backend. </p><p><b>smbpasswd</b> works in a client-server mode
- where it contacts the local smbd to change the user's password on its
- behalf. This has enormous benefits - as follows.</p><p><b>smbpasswd</b> has the capability
- to change passwords on Windows NT servers (this only works when
- the request is sent to the NT Primary Domain Controller if you
- are changing an NT Domain user's password).</p><p>To run smbpasswd as a normal user just type :</p><p><tt>$ </tt><b><tt>smbpasswd</tt></b></p><p><tt>Old SMB password: </tt><b><tt>&lt;type old value here -
- or hit return if there was no old password&gt;</tt></b></p><p><tt>New SMB Password: </tt><b><tt>&lt;type new value&gt;
- </tt></b></p><p><tt>Repeat New SMB Password: </tt><b><tt>&lt;re-type new value
- </tt></b></p><p>If the old value does not match the current value stored for
- that user, or the two new values do not match each other, then the
- password will not be changed.</p><p>If invoked by an ordinary user it will only allow the user
- to change his or her own Samba password.</p><p>If run by the root user smbpasswd may take an optional
- argument, specifying the user name whose SMB password you wish to
- change. Note that when run as root smbpasswd does not prompt for
- or check the old password value, thus allowing root to set passwords
- for users who have forgotten their passwords.</p><p><b>smbpasswd</b> is designed to work in the same way
- and be familiar to UNIX users who use the <b>passwd</b> or
- <b>yppasswd</b> commands.</p><p>For more details on using <b>smbpasswd</b> refer
- to the man page which will always be the definitive reference.</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2866568"></a>Plain text</h2></div></div><p>
-Older versions of samba retrieved user information from the unix user database
-and eventually some other fields from the file <tt>/etc/samba/smbpasswd</tt>
-or <tt>/etc/smbpasswd</tt>. When password encryption is disabled, no
-data is stored at all.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2866597"></a>TDB</h2></div></div><p>Samba can also store the user data in a &quot;TDB&quot; (Trivial Database). Using this backend
-doesn't require any additional configuration. This backend is recommended for new installations that
-don not require LDAP.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2866613"></a>LDAP</h2></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2866621"></a>Introduction</h3></div></div><p>
-This document describes how to use an LDAP directory for storing Samba user
-account information traditionally stored in the smbpasswd(5) file. It is
-assumed that the reader already has a basic understanding of LDAP concepts
-and has a working directory server already installed. For more information
-on LDAP architectures and Directories, please refer to the following sites.
-</p><div class="itemizedlist"><ul type="disc"><li><p>OpenLDAP - <a href="http://www.openldap.org/" target="_top">http://www.openldap.org/</a></p></li><li><p>iPlanet Directory Server - <a href="http://iplanet.netscape.com/directory" target="_top">http://iplanet.netscape.com/directory</a></p></li></ul></div><p>
-Note that <a href="http://www.ora.com/" target="_top">O'Reilly Publishing</a> is working on
-a guide to LDAP for System Administrators which has a planned release date of
-early summer, 2002.
-</p><p>
-Two additional Samba resources which may prove to be helpful are
-</p><div class="itemizedlist"><ul type="disc"><li><p>The <a href="http://www.unav.es/cti/ldap-smb/ldap-smb-3-howto.html" target="_top">Samba-PDC-LDAP-HOWTO</a>
- maintained by Ignacio Coupeau.</p></li><li><p>The NT migration scripts from <a href="http://samba.idealx.org/" target="_top">IDEALX</a> that are
- geared to manage users and group in such a Samba-LDAP Domain Controller configuration.
- </p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2866721"></a>Encrypted Password Database</h3></div></div><p>
-Traditionally, when configuring <a href="smb.conf.5.html#ENCRYPTPASSWORDS" target="_top">&quot;encrypt
-passwords = yes&quot;</a> in Samba's <tt>smb.conf</tt> file, user account
-information such as username, LM/NT password hashes, password change times, and account
-flags have been stored in the <tt>smbpasswd(5)</tt> file. There are several
-disadvantages to this approach for sites with very large numbers of users (counted
-in the thousands).
-</p><div class="itemizedlist"><ul type="disc"><li><p>
-The first is that all lookups must be performed sequentially. Given that
-there are approximately two lookups per domain logon (one for a normal
-session connection such as when mapping a network drive or printer), this
-is a performance bottleneck for large sites. What is needed is an indexed approach
-such as is used in databases.
-</p></li><li><p>
-The second problem is that administrators who desired to replicate a
-smbpasswd file to more than one Samba server were left to use external
-tools such as <b>rsync(1)</b> and <b>ssh(1)</b>
-and wrote custom, in-house scripts.
-</p></li><li><p>
-And finally, the amount of information which is stored in an
-smbpasswd entry leaves no room for additional attributes such as
-a home directory, password expiration time, or even a Relative
-Identified (RID).
-</p></li></ul></div><p>
-As a result of these defeciencies, a more robust means of storing user attributes
-used by smbd was developed. The API which defines access to user accounts
-is commonly referred to as the samdb interface (previously this was called the passdb
-API, and is still so named in the CVS trees).
-</p><p>
-There are a few points to stress about that the ldapsam
-does not provide. The LDAP support referred to in the this documentation does not
-include:
-</p><div class="itemizedlist"><ul type="disc"><li><p>A means of retrieving user account information from
- an Windows 2000 Active Directory server.</p></li><li><p>A means of replacing /etc/passwd.</p></li></ul></div><p>
-The second item can be accomplished by using LDAP NSS and PAM modules. LGPL
-versions of these libraries can be obtained from PADL Software
-(<a href="http://www.padl.com/" target="_top">http://www.padl.com/</a>). More
-information about the configuration of these packages may be found at &quot;LDAP,
-System Administration; Gerald Carter, O'Reilly; Chapter 6: Replacing NIS&quot;.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2866860"></a>Supported LDAP Servers</h3></div></div><p>
-The LDAP samdb code in 2.2.3 (and later) has been developed and tested
-using the OpenLDAP 2.0 server and client libraries.
-The same code should be able to work with Netscape's Directory Server
-and client SDK. However, due to lack of testing so far, there are bound
-to be compile errors and bugs. These should not be hard to fix.
-If you are so inclined, please be sure to forward all patches to
-<a href="mailto:samba-patches@samba.org" target="_top">samba-patches@samba.org</a> and
-<a href="mailto:jerry@samba.org" target="_top">jerry@samba.org</a>.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2866898"></a>Schema and Relationship to the RFC 2307 posixAccount</h3></div></div><p>
-Samba 3.0 includes the necessary schema file for OpenLDAP 2.0 in
-<tt>examples/LDAP/samba.schema</tt>. The sambaAccount objectclass is given here:
-</p><pre class="programlisting">
-objectclass ( 1.3.1.5.1.4.1.7165.2.2.2 NAME 'sambaAccount' SUP top AUXILIARY
- DESC 'Samba Account'
- MUST ( uid $ rid )
- MAY ( cn $ lmPassword $ ntPassword $ pwdLastSet $ logonTime $
- logoffTime $ kickoffTime $ pwdCanChange $ pwdMustChange $ acctFlags $
- displayName $ smbHome $ homeDrive $ scriptPath $ profilePath $
- description $ userWorkstations $ primaryGroupID $ domain ))
-</pre><p>
-The samba.schema file has been formatted for OpenLDAP 2.0. The OID's are
-owned by the Samba Team and as such is legal to be openly published.
-If you translate the schema to be used with Netscape DS, please
-submit the modified schema file as a patch to <a href="mailto:jerry@samba.org" target="_top">jerry@samba.org</a>
-</p><p>
-Just as the smbpasswd file is meant to store information which supplements a
-user's <tt>/etc/passwd</tt> entry, so is the sambaAccount object
-meant to supplement the UNIX user account information. A sambaAccount is a
-<tt>STRUCTURAL</tt> objectclass so it can be stored individually
-in the directory. However, there are several fields (e.g. uid) which overlap
-with the posixAccount objectclass outlined in RFC2307. This is by design.
-</p><p>
-In order to store all user account information (UNIX and Samba) in the directory,
-it is necessary to use the sambaAccount and posixAccount objectclasses in
-combination. However, smbd will still obtain the user's UNIX account
-information via the standard C library calls (e.g. getpwnam(), et. al.).
-This means that the Samba server must also have the LDAP NSS library installed
-and functioning correctly. This division of information makes it possible to
-store all Samba account information in LDAP, but still maintain UNIX account
-information in NIS while the network is transitioning to a full LDAP infrastructure.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2867008"></a>Configuring Samba with LDAP</h3></div></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2867016"></a>OpenLDAP configuration</h4></div></div><p>
-To include support for the sambaAccount object in an OpenLDAP directory
-server, first copy the samba.schema file to slapd's configuration directory.
-</p><p>
-<tt>root# </tt><b><tt>cp samba.schema /etc/openldap/schema/</tt></b>
-</p><p>
-Next, include the <tt>samba.schema</tt> file in <tt>slapd.conf</tt>.
-The sambaAccount object contains two attributes which depend upon other schema
-files. The 'uid' attribute is defined in <tt>cosine.schema</tt> and
-the 'displayName' attribute is defined in the <tt>inetorgperson.schema</tt>
-file. Both of these must be included before the <tt>samba.schema</tt> file.
-</p><pre class="programlisting">
-## /etc/openldap/slapd.conf
-
-## schema files (core.schema is required by default)
-include /etc/openldap/schema/core.schema
-
-## needed for sambaAccount
-include /etc/openldap/schema/cosine.schema
-include /etc/openldap/schema/inetorgperson.schema
-include /etc/openldap/schema/samba.schema
-include /etc/openldap/schema/nis.schema
-
-....
-</pre><p>
-It is recommended that you maintain some indices on some of the most usefull attributes,
-like in the following example, to speed up searches made on sambaAccount objectclasses
-(and possibly posixAccount and posixGroup as well).
-</p><pre class="programlisting">
-# Indices to maintain
-## required by OpenLDAP 2.0
-index objectclass eq
-
-## support pb_getsampwnam()
-index uid pres,eq
-## support pdb_getsambapwrid()
-index rid eq
-
-## uncomment these if you are storing posixAccount and
-## posixGroup entries in the directory as well
-##index uidNumber eq
-##index gidNumber eq
-##index cn eq
-##index memberUid eq
-
-# (both fetched via ldapsearch):
-index primaryGroupID eq
-index displayName pres,eq
-
-</pre></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2867134"></a>Configuring Samba</h4></div></div><p>
-The following parameters are available in smb.conf only with <i><tt>--with-ldapsam</tt></i>
-was included when compiling Samba.
-</p><div class="itemizedlist"><ul type="disc"><li><p><a href="smb.conf.5.html#PASSDBBACKEND" target="_top">passdb backend [ldapsam|ldapsam_nua]:url</a></p></li><li><p><a href="smb.conf.5.html#LDAPSSL" target="_top">ldap ssl</a></p></li><li><p><a href="smb.conf.5.html#LDAPADMINDN" target="_top">ldap admin dn</a></p></li><li><p><a href="smb.conf.5.html#LDAPSUFFIX" target="_top">ldap suffix</a></p></li><li><p><a href="smb.conf.5.html#LDAPFILTER" target="_top">ldap filter</a></p></li><li><p><a href="smb.conf.5.html#LDAPPORT" target="_top">ldap port</a></p></li><li><p><a href="smb.conf.5.html#LDAPMACHINSUFFIX" target="_top">ldap machine suffix</a></p></li><li><p><a href="smb.conf.5.html#LDAPUSERSUFFIX" target="_top">ldap user suffix</a></p></li><li><p><a href="smb.conf.5.html#LDAPDELETEDN" target="_top">ldap delete dn</a></p></li></ul></div><p>
-These are described in the <a href="smb.conf.5.html" target="_top">smb.conf(5)</a> man
-page and so will not be repeated here. However, a sample smb.conf file for
-use with an LDAP directory could appear as
-</p><pre class="programlisting">
-## /usr/local/samba/lib/smb.conf
-[global]
- security = user
- encrypt passwords = yes
-
- netbios name = TASHTEGO
- workgroup = NARNIA
-
- # ldap related parameters
-
- # define the DN to use when binding to the directory servers
- # The password for this DN is not stored in smb.conf. Rather it
- # must be set by using 'smbpasswd -w <i><tt>secretpw</tt></i>' to store the
- # passphrase in the secrets.tdb file. If the &quot;ldap admin dn&quot; values
- # change, this password will need to be reset.
- ldap admin dn = &quot;cn=Samba Manager,ou=people,dc=samba,dc=org&quot;
-
- # Define the SSL option when connecting to the directory
- # ('off', 'start tls', or 'on' (default))
- ldap ssl = start tls
-
- passdb backend ldapsam:ldap://ahab.samba.org
-
- # smbpasswd -x delete the entire dn-entry
- ldap delete dn = no
-
- # the machine and user suffix added to the base suffix
- # wrote WITHOUT quotes. NULL siffixes by default
- ldap user suffix = ou=People
- ldap machine suffix = ou=Systems
-
- # define the port to use in the LDAP session (defaults to 636 when
- # &quot;ldap ssl = on&quot;)
- ldap port = 389
-
- # specify the base DN to use when searching the directory
- ldap suffix = &quot;ou=people,dc=samba,dc=org&quot;
-
- # generally the default ldap search filter is ok
- # ldap filter = &quot;(&amp;(uid=%u)(objectclass=sambaAccount))&quot;
-</pre></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2867304"></a>Accounts and Groups management</h3></div></div><p>
-As users accounts are managed thru the sambaAccount objectclass, you should
-modify your existing administration tools to deal with sambaAccount attributes.
-</p><p>
-Machines accounts are managed with the sambaAccount objectclass, just
-like users accounts. However, it's up to you to store thoses accounts
-in a different tree of you LDAP namespace: you should use
-&quot;ou=Groups,dc=plainjoe,dc=org&quot; to store groups and
-&quot;ou=People,dc=plainjoe,dc=org&quot; to store users. Just configure your
-NSS and PAM accordingly (usually, in the /etc/ldap.conf configuration
-file).
-</p><p>
-In Samba release 3.0, the group management system is based on posix
-groups. This means that Samba makes usage of the posixGroup objectclass.
-For now, there is no NT-like group system management (global and local
-groups).
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2867341"></a>Security and sambaAccount</h3></div></div><p>
-There are two important points to remember when discussing the security
-of sambaAccount entries in the directory.
-</p><div class="itemizedlist"><ul type="disc"><li><p><span class="emphasis"><em>Never</em></span> retrieve the lmPassword or
- ntPassword attribute values over an unencrypted LDAP session.</p></li><li><p><span class="emphasis"><em>Never</em></span> allow non-admin users to
- view the lmPassword or ntPassword attribute values.</p></li></ul></div><p>
-These password hashes are clear text equivalents and can be used to impersonate
-the user without deriving the original clear text strings. For more information
-on the details of LM/NT password hashes, refer to the <a href="#passdb" title="Chapter10.User information database">User Database</a> of the Samba-HOWTO-Collection.
-</p><p>
-To remedy the first security issue, the &quot;ldap ssl&quot; smb.conf parameter defaults
-to require an encrypted session (<b>ldap ssl = on</b>) using
-the default port of 636
-when contacting the directory server. When using an OpenLDAP 2.0 server, it
-is possible to use the use the StartTLS LDAP extended operation in the place of
-LDAPS. In either case, you are strongly discouraged to disable this security
-(<b>ldap ssl = off</b>).
-</p><p>
-Note that the LDAPS protocol is deprecated in favor of the LDAPv3 StartTLS
-extended operation. However, the OpenLDAP library still provides support for
-the older method of securing communication between clients and servers.
-</p><p>
-The second security precaution is to prevent non-administrative users from
-harvesting password hashes from the directory. This can be done using the
-following ACL in <tt>slapd.conf</tt>:
-</p><pre class="programlisting">
-## allow the &quot;ldap admin dn&quot; access, but deny everyone else
-access to attrs=lmPassword,ntPassword
- by dn=&quot;cn=Samba Admin,ou=people,dc=plainjoe,dc=org&quot; write
- by * none
-</pre></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2867456"></a>LDAP specials attributes for sambaAccounts</h3></div></div><p>
-The sambaAccount objectclass is composed of the following attributes:
-</p><div class="itemizedlist"><ul type="disc"><li><p><tt>lmPassword</tt>: the LANMAN password 16-byte hash stored as a character
- representation of a hexidecimal string.</p></li><li><p><tt>ntPassword</tt>: the NT password hash 16-byte stored as a character
- representation of a hexidecimal string.</p></li><li><p><tt>pwdLastSet</tt>: The integer time in seconds since 1970 when the
- <tt>lmPassword</tt> and <tt>ntPassword</tt> attributes were last set.
- </p></li><li><p><tt>acctFlags</tt>: string of 11 characters surrounded by square brackets []
- representing account flags such as U (user), W(workstation), X(no password expiration), and
- D(disabled).</p></li><li><p><tt>logonTime</tt>: Integer value currently unused</p></li><li><p><tt>logoffTime</tt>: Integer value currently unused</p></li><li><p><tt>kickoffTime</tt>: Integer value currently unused</p></li><li><p><tt>pwdCanChange</tt>: Integer value currently unused</p></li><li><p><tt>pwdMustChange</tt>: Integer value currently unused</p></li><li><p><tt>homeDrive</tt>: specifies the drive letter to which to map the
- UNC path specified by homeDirectory. The drive letter must be specified in the form &quot;X:&quot;
- where X is the letter of the drive to map. Refer to the &quot;logon drive&quot; parameter in the
- smb.conf(5) man page for more information.</p></li><li><p><tt>scriptPath</tt>: The scriptPath property specifies the path of
- the user's logon script, .CMD, .EXE, or .BAT file. The string can be null. The path
- is relative to the netlogon share. Refer to the &quot;logon script&quot; parameter in the
- smb.conf(5) man page for more information.</p></li><li><p><tt>profilePath</tt>: specifies a path to the user's profile.
- This value can be a null string, a local absolute path, or a UNC path. Refer to the
- &quot;logon path&quot; parameter in the smb.conf(5) man page for more information.</p></li><li><p><tt>smbHome</tt>: The homeDirectory property specifies the path of
- the home directory for the user. The string can be null. If homeDrive is set and specifies
- a drive letter, homeDirectory should be a UNC path. The path must be a network
- UNC path of the form \\server\share\directory. This value can be a null string.
- Refer to the &quot;logon home&quot; parameter in the smb.conf(5) man page for more information.
- </p></li><li><p><tt>userWorkstation</tt>: character string value currently unused.
- </p></li><li><p><tt>rid</tt>: the integer representation of the user's relative identifier
- (RID).</p></li><li><p><tt>primaryGroupID</tt>: the relative identifier (RID) of the primary group
- of the user.</p></li></ul></div><p>
-The majority of these parameters are only used when Samba is acting as a PDC of
-a domain (refer to the <a href="Samba-PDC-HOWTO.html" target="_top">Samba-PDC-HOWTO</a> for details on
-how to configure Samba as a Primary Domain Controller). The following four attributes
-are only stored with the sambaAccount entry if the values are non-default values:
-</p><div class="itemizedlist"><ul type="disc"><li><p>smbHome</p></li><li><p>scriptPath</p></li><li><p>logonPath</p></li><li><p>homeDrive</p></li></ul></div><p>
-These attributes are only stored with the sambaAccount entry if
-the values are non-default values. For example, assume TASHTEGO has now been
-configured as a PDC and that <b>logon home = \\%L\%u</b> was defined in
-its <tt>smb.conf</tt> file. When a user named &quot;becky&quot; logons to the domain,
-the <i><tt>logon home</tt></i> string is expanded to \\TASHTEGO\becky.
-If the smbHome attribute exists in the entry &quot;uid=becky,ou=people,dc=samba,dc=org&quot;,
-this value is used. However, if this attribute does not exist, then the value
-of the <i><tt>logon home</tt></i> parameter is used in its place. Samba
-will only write the attribute value to the directory entry if the value is
-something other than the default (e.g. \\MOBY\becky).
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2867737"></a>Example LDIF Entries for a sambaAccount</h3></div></div><p>
-The following is a working LDIF with the inclusion of the posixAccount objectclass:
-</p><pre class="programlisting">
-dn: uid=guest2, ou=people,dc=plainjoe,dc=org
-ntPassword: 878D8014606CDA29677A44EFA1353FC7
-pwdMustChange: 2147483647
-primaryGroupID: 1201
-lmPassword: 552902031BEDE9EFAAD3B435B51404EE
-pwdLastSet: 1010179124
-logonTime: 0
-objectClass: sambaAccount
-uid: guest2
-kickoffTime: 2147483647
-acctFlags: [UX ]
-logoffTime: 2147483647
-rid: 19006
-pwdCanChange: 0
-</pre><p>
-The following is an LDIF entry for using both the sambaAccount and
-posixAccount objectclasses:
-</p><pre class="programlisting">
-dn: uid=gcarter, ou=people,dc=plainjoe,dc=org
-logonTime: 0
-displayName: Gerald Carter
-lmPassword: 552902031BEDE9EFAAD3B435B51404EE
-primaryGroupID: 1201
-objectClass: posixAccount
-objectClass: sambaAccount
-acctFlags: [UX ]
-userPassword: {crypt}BpM2ej8Rkzogo
-uid: gcarter
-uidNumber: 9000
-cn: Gerald Carter
-loginShell: /bin/bash
-logoffTime: 2147483647
-gidNumber: 100
-kickoffTime: 2147483647
-pwdLastSet: 1010179230
-rid: 19000
-homeDirectory: /home/tashtego/gcarter
-pwdCanChange: 0
-pwdMustChange: 2147483647
-ntPassword: 878D8014606CDA29677A44EFA1353FC7
-</pre></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2867793"></a>MySQL</h2></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2867800"></a>Creating the database</h3></div></div><p>
-You either can set up your own table and specify the field names to pdb_mysql (see below
-for the column names) or use the default table. The file <tt>examples/pdb/mysql/mysql.dump</tt>
-contains the correct queries to create the required tables. Use the command :
-
-<b>mysql -u<i><tt>username</tt></i> -h<i><tt>hostname</tt></i> -p<i><tt>password</tt></i> <i><tt>databasename</tt></i> &gt; <tt>/path/to/samba/examples/pdb/mysql/mysql.dump</tt></b>
-
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2867854"></a>Configuring</h3></div></div><p>This plugin lacks some good documentation, but here is some short info:</p><p>Add a the following to the <b>passdb backend</b> variable in your <tt>smb.conf</tt>:
-</p><pre class="programlisting">
-passdb backend = [other-plugins] mysql:identifier [other-plugins]
-</pre><p>
-</p><p>The identifier can be any string you like, as long as it doesn't collide with
-the identifiers of other plugins or other instances of pdb_mysql. If you
-specify multiple pdb_mysql.so entries in 'passdb backend', you also need to
-use different identifiers!
-</p><p>
-Additional options can be given thru the smb.conf file in the [global] section.
-</p><pre class="programlisting">
-identifier:mysql host - host name, defaults to 'localhost'
-identifier:mysql password
-identifier:mysql user - defaults to 'samba'
-identifier:mysql database - defaults to 'samba'
-identifier:mysql port - defaults to 3306
-identifier:table - Name of the table containing users
-</pre><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p>
-Since the password for the mysql user is stored in the
-smb.conf file, you should make the the smb.conf file
-readable only to the user that runs samba. This is considered a security
-bug and will be fixed soon.
-</p></div><p>Names of the columns in this table(I've added column types those columns should have first):</p><pre class="programlisting">
-identifier:logon time column - int(9)
-identifier:logoff time column - int(9)
-identifier:kickoff time column - int(9)
-identifier:pass last set time column - int(9)
-identifier:pass can change time column - int(9)
-identifier:pass must change time column - int(9)
-identifier:username column - varchar(255) - unix username
-identifier:domain column - varchar(255) - NT domain user is part of
-identifier:nt username column - varchar(255) - NT username
-identifier:fullname column - varchar(255) - Full name of user
-identifier:home dir column - varchar(255) - Unix homedir path
-identifier:dir drive column - varchar(2) - Directory drive path (eg: 'H:')
-identifier:logon script column - varchar(255)
- - Batch file to run on client side when logging on
-identifier:profile path column - varchar(255) - Path of profile
-identifier:acct desc column - varchar(255) - Some ASCII NT user data
-identifier:workstations column - varchar(255)
- - Workstations user can logon to (or NULL for all)
-identifier:unknown string column - varchar(255) - unknown string
-identifier:munged dial column - varchar(255) - ?
-identifier:user sid column - varchar(255) - NT user SID
-identifier:group sid column - varchar(255) - NT group ID
-identifier:lanman pass column - varchar(255) - encrypted lanman password
-identifier:nt pass column - varchar(255) - encrypted nt passwd
-identifier:plain pass column - varchar(255) - plaintext password
-identifier:acct control column - int(9) - nt user data
-identifier:unknown 3 column - int(9) - unknown
-identifier:logon divs column - int(9) - ?
-identifier:hours len column - int(9) - ?
-identifier:unknown 5 column - int(9) - unknown
-identifier:unknown 6 column - int(9) - unknown
-</pre><p>
-Eventually, you can put a colon (:) after the name of each column, which
-should specify the column to update when updating the table. You can also
-specify nothing behind the colon - then the data from the field will not be
-updated.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2867999"></a>Using plaintext passwords or encrypted password</h3></div></div><p>
-I strongly discourage the use of plaintext passwords, however, you can use them:
-</p><p>
-If you would like to use plaintext passwords, set
-'identifier:lanman pass column' and 'identifier:nt pass column' to
-'NULL' (without the quotes) and 'identifier:plain pass column' to the
-name of the column containing the plaintext passwords.
-</p><p>
-If you use encrypted passwords, set the 'identifier:plain pass
-column' to 'NULL' (without the quotes). This is the default.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2868029"></a>Getting non-column data from the table</h3></div></div><p>
-It is possible to have not all data in the database and making some 'constant'.
-</p><p>
-For example, you can set 'identifier:fullname column' to :
-<b>CONCAT(First_name,' ',Sur_name)</b>
-</p><p>
-Or, set 'identifier:workstations column' to :
-<b>NULL</b></p><p>See the MySQL documentation for more language constructs.</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2868072"></a>XML</h2></div></div><p>This module requires libxml2 to be installed.</p><p>The usage of pdb_xml is pretty straightforward. To export data, use:
-</p><p>
- <b><tt>pdbedit -e xml:filename</tt></b>
-</p><p>
-(where filename is the name of the file to put the data in)
-</p><p>
-To import data, use:
-<b><tt>pdbedit -i xml:filename -e current-pdb</tt></b>
-</p><p>
-Where filename is the name to read the data from and current-pdb to put it in.
-</p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="unix-permissions"></a>Chapter11.UNIX Permission Bits and Windows NT Access Control Lists</h2></div><div><div class="author"><h3 class="author">Jeremy Allison</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt>&lt;<a href="mailto:jra@samba.org">jra@samba.org</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate">12 Apr 1999</p></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2865054">Viewing and changing UNIX permissions using the NT
- security dialogs</a></dt><dt><a href="#id2864937">How to view file security on a Samba share</a></dt><dt><a href="#id2868280">Viewing file ownership</a></dt><dt><a href="#id2868401">Viewing file or directory permissions</a></dt><dd><dl><dt><a href="#id2868484">File Permissions</a></dt><dt><a href="#id2868587">Directory Permissions</a></dt></dl></dd><dt><a href="#id2868637">Modifying file or directory permissions</a></dt><dt><a href="#id2868797">Interaction with the standard Samba create mask
- parameters</a></dt><dt><a href="#id2869113">Interaction with the standard Samba file attribute
- mapping</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2865054"></a>Viewing and changing UNIX permissions using the NT
- security dialogs</h2></div></div><p>Windows NT clients can use their native security settings
- dialog box to view and modify the underlying UNIX permissions.</p><p>Note that this ability is careful not to compromise
- the security of the UNIX host Samba is running on, and
- still obeys all the file permission rules that a Samba
- administrator can set.</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
- All access to Unix/Linux system file via Samba is controlled at
- the operating system file access control level. When trying to
- figure out file access problems it is vitally important to identify
- the identity of the Windows user as it is presented by Samba at
- the point of file access. This can best be determined from the
- Samba log files.
- </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2864937"></a>How to view file security on a Samba share</h2></div></div><p>From an NT4/2000/XP client, single-click with the right
- mouse button on any file or directory in a Samba mounted
- drive letter or UNC path. When the menu pops-up, click
- on the <span class="emphasis"><em>Properties</em></span> entry at the bottom of
- the menu. This brings up the file properties dialog
- box. Click on the tab <span class="emphasis"><em>Security</em></span> and you
- will see three buttons, <span class="emphasis"><em>Permissions</em></span>,
- <span class="emphasis"><em>Auditing</em></span>, and <span class="emphasis"><em>Ownership</em></span>.
- The <span class="emphasis"><em>Auditing</em></span> button will cause either
- an error message A requested privilege is not held
- by the client to appear if the user is not the
- NT Administrator, or a dialog which is intended to allow an
- Administrator to add auditing requirements to a file if the
- user is logged on as the NT Administrator. This dialog is
- non-functional with a Samba share at this time, as the only
- useful button, the <b>Add</b> button will not currently
- allow a list of users to be seen.</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2868280"></a>Viewing file ownership</h2></div></div><p>Clicking on the <b>&quot;Ownership&quot;</b> button
- brings up a dialog box telling you who owns the given file. The
- owner name will be of the form :</p><p><b>&quot;SERVER\user (Long name)&quot;</b></p><p>Where <i><tt>SERVER</tt></i> is the NetBIOS name of
- the Samba server, <i><tt>user</tt></i> is the user name of
- the UNIX user who owns the file, and <i><tt>(Long name)</tt></i>
- is the descriptive string identifying the user (normally found in the
- GECOS field of the UNIX password database). Click on the <b>Close
- </b> button to remove this dialog.</p><p>If the parameter <i><tt>nt acl support</tt></i>
- is set to <tt>false</tt> then the file owner will
- be shown as the NT user <b>&quot;Everyone&quot;</b>.</p><p>The <b>Take Ownership</b> button will not allow
- you to change the ownership of this file to yourself (clicking on
- it will display a dialog box complaining that the user you are
- currently logged onto the NT client cannot be found). The reason
- for this is that changing the ownership of a file is a privileged
- operation in UNIX, available only to the <span class="emphasis"><em>root</em></span>
- user. As clicking on this button causes NT to attempt to change
- the ownership of a file to the current user logged into the NT
- client this will not work with Samba at this time.</p><p>There is an NT chown command that will work with Samba
- and allow a user with Administrator privilege connected
- to a Samba server as root to change the ownership of
- files on both a local NTFS filesystem or remote mounted NTFS
- or Samba drive. This is available as part of the <span class="emphasis"><em>Seclib
- </em></span> NT security library written by Jeremy Allison of
- the Samba Team, available from the main Samba ftp site.</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2868401"></a>Viewing file or directory permissions</h2></div></div><p>The third button is the <b>&quot;Permissions&quot;</b>
- button. Clicking on this brings up a dialog box that shows both
- the permissions and the UNIX owner of the file or directory.
- The owner is displayed in the form :</p><p><b>&quot;SERVER\user (Long name)&quot;</b></p><p>Where <i><tt>SERVER</tt></i> is the NetBIOS name of
- the Samba server, <i><tt>user</tt></i> is the user name of
- the UNIX user who owns the file, and <i><tt>(Long name)</tt></i>
- is the descriptive string identifying the user (normally found in the
- GECOS field of the UNIX password database).</p><p>If the parameter <i><tt>nt acl support</tt></i>
- is set to <tt>false</tt> then the file owner will
- be shown as the NT user <b>&quot;Everyone&quot;</b> and the
- permissions will be shown as NT &quot;Full Control&quot;.</p><p>The permissions field is displayed differently for files
- and directories, so I'll describe the way file permissions
- are displayed first.</p><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2868484"></a>File Permissions</h3></div></div><p>The standard UNIX user/group/world triple and
- the corresponding &quot;read&quot;, &quot;write&quot;, &quot;execute&quot; permissions
- triples are mapped by Samba into a three element NT ACL
- with the 'r', 'w', and 'x' bits mapped into the corresponding
- NT permissions. The UNIX world permissions are mapped into
- the global NT group <b>Everyone</b>, followed
- by the list of permissions allowed for UNIX world. The UNIX
- owner and group permissions are displayed as an NT
- <b>user</b> icon and an NT <b>local
- group</b> icon respectively followed by the list
- of permissions allowed for the UNIX user and group.</p><p>As many UNIX permission sets don't map into common
- NT names such as <b>&quot;read&quot;</b>, <b>
- &quot;change&quot;</b> or <b>&quot;full control&quot;</b> then
- usually the permissions will be prefixed by the words <b>
- &quot;Special Access&quot;</b> in the NT display list.</p><p>But what happens if the file has no permissions allowed
- for a particular UNIX user group or world component ? In order
- to allow &quot;no permissions&quot; to be seen and modified then Samba
- overloads the NT <b>&quot;Take Ownership&quot;</b> ACL attribute
- (which has no meaning in UNIX) and reports a component with
- no permissions as having the NT <b>&quot;O&quot;</b> bit set.
- This was chosen of course to make it look like a zero, meaning
- zero permissions. More details on the decision behind this will
- be given below.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2868587"></a>Directory Permissions</h3></div></div><p>Directories on an NT NTFS file system have two
- different sets of permissions. The first set of permissions
- is the ACL set on the directory itself, this is usually displayed
- in the first set of parentheses in the normal <b>&quot;RW&quot;</b>
- NT style. This first set of permissions is created by Samba in
- exactly the same way as normal file permissions are, described
- above, and is displayed in the same way.</p><p>The second set of directory permissions has no real meaning
- in the UNIX permissions world and represents the <b>
- &quot;inherited&quot;</b> permissions that any file created within
- this directory would inherit.</p><p>Samba synthesises these inherited permissions for NT by
- returning as an NT ACL the UNIX permission mode that a new file
- created by Samba on this share would receive.</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2868637"></a>Modifying file or directory permissions</h2></div></div><p>Modifying file and directory permissions is as simple
- as changing the displayed permissions in the dialog box, and
- clicking the <b>OK</b> button. However, there are
- limitations that a user needs to be aware of, and also interactions
- with the standard Samba permission masks and mapping of DOS
- attributes that need to also be taken into account.</p><p>If the parameter <i><tt>nt acl support</tt></i>
- is set to <tt>false</tt> then any attempt to set
- security permissions will fail with an <b>&quot;Access Denied&quot;
- </b> message.</p><p>The first thing to note is that the <b>&quot;Add&quot;</b>
- button will not return a list of users in Samba (it will give
- an error message of <b>&quot;The remote procedure call failed
- and did not execute&quot;</b>). This means that you can only
- manipulate the current user/group/world permissions listed in
- the dialog box. This actually works quite well as these are the
- only permissions that UNIX actually has.</p><p>If a permission triple (either user, group, or world)
- is removed from the list of permissions in the NT dialog box,
- then when the <b>&quot;OK&quot;</b> button is pressed it will
- be applied as &quot;no permissions&quot; on the UNIX side. If you then
- view the permissions again the &quot;no permissions&quot; entry will appear
- as the NT <b>&quot;O&quot;</b> flag, as described above. This
- allows you to add permissions back to a file or directory once
- you have removed them from a triple component.</p><p>As UNIX supports only the &quot;r&quot;, &quot;w&quot; and &quot;x&quot; bits of
- an NT ACL then if other NT security attributes such as &quot;Delete
- access&quot; are selected then they will be ignored when applied on
- the Samba server.</p><p>When setting permissions on a directory the second
- set of permissions (in the second set of parentheses) is
- by default applied to all files within that directory. If this
- is not what you want you must uncheck the <b>&quot;Replace
- permissions on existing files&quot;</b> checkbox in the NT
- dialog before clicking <b>&quot;OK&quot;</b>.</p><p>If you wish to remove all permissions from a
- user/group/world component then you may either highlight the
- component and click the <b>&quot;Remove&quot;</b> button,
- or set the component to only have the special <b>&quot;Take
- Ownership&quot;</b> permission (displayed as <b>&quot;O&quot;
- </b>) highlighted.</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2868797"></a>Interaction with the standard Samba create mask
- parameters</h2></div></div><p>There are four parameters
- to control interaction with the standard Samba create mask parameters.
- These are :</p><p><i><tt>security mask</tt></i></p><p><i><tt>force security mode</tt></i></p><p><i><tt>directory security mask</tt></i></p><p><i><tt>force directory security mode</tt></i></p><p>Once a user clicks <b>&quot;OK&quot;</b> to apply the
- permissions Samba maps the given permissions into a user/group/world
- r/w/x triple set, and then will check the changed permissions for a
- file against the bits set in the <a href="smb.conf.5.html#SECURITYMASK" target="_top">
- <i><tt>security mask</tt></i></a> parameter. Any bits that
- were changed that are not set to '1' in this parameter are left alone
- in the file permissions.</p><p>Essentially, zero bits in the <i><tt>security mask</tt></i>
- mask may be treated as a set of bits the user is <span class="emphasis"><em>not</em></span>
- allowed to change, and one bits are those the user is allowed to change.
- </p><p>If not set explicitly this parameter is set to the same value as
- the <a href="smb.conf.5.html#CREATEMASK" target="_top"><i><tt>create mask
- </tt></i></a> parameter. To allow a user to modify all the
- user/group/world permissions on a file, set this parameter
- to 0777.</p><p>Next Samba checks the changed permissions for a file against
- the bits set in the <a href="smb.conf.5.html#FORCESECURITYMODE" target="_top">
- <i><tt>force security mode</tt></i></a> parameter. Any bits
- that were changed that correspond to bits set to '1' in this parameter
- are forced to be set.</p><p>Essentially, bits set in the <i><tt>force security mode
- </tt></i> parameter may be treated as a set of bits that, when
- modifying security on a file, the user has always set to be 'on'.</p><p>If not set explicitly this parameter is set to the same value
- as the <a href="smb.conf.5.html#FORCECREATEMODE" target="_top"><i><tt>force
- create mode</tt></i></a> parameter.
- To allow a user to modify all the user/group/world permissions on a file
- with no restrictions set this parameter to 000.</p><p>The <i><tt>security mask</tt></i> and <i><tt>force
- security mode</tt></i> parameters are applied to the change
- request in that order.</p><p>For a directory Samba will perform the same operations as
- described above for a file except using the parameter <i><tt>
- directory security mask</tt></i> instead of <i><tt>security
- mask</tt></i>, and <i><tt>force directory security mode
- </tt></i> parameter instead of <i><tt>force security mode
- </tt></i>.</p><p>The <i><tt>directory security mask</tt></i> parameter
- by default is set to the same value as the <i><tt>directory mask
- </tt></i> parameter and the <i><tt>force directory security
- mode</tt></i> parameter by default is set to the same value as
- the <i><tt>force directory mode</tt></i> parameter. </p><p>In this way Samba enforces the permission restrictions that
- an administrator can set on a Samba share, whilst still allowing users
- to modify the permission bits within that restriction.</p><p>If you want to set up a share that allows users full control
- in modifying the permission bits on their files and directories and
- doesn't force any particular bits to be set 'on', then set the following
- parameters in the <tt>smb.conf</tt> file in that share specific section :</p><p><i><tt>security mask = 0777</tt></i></p><p><i><tt>force security mode = 0</tt></i></p><p><i><tt>directory security mask = 0777</tt></i></p><p><i><tt>force directory security mode = 0</tt></i></p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2869113"></a>Interaction with the standard Samba file attribute
- mapping</h2></div></div><p>Samba maps some of the DOS attribute bits (such as &quot;read
- only&quot;) into the UNIX permissions of a file. This means there can
- be a conflict between the permission bits set via the security
- dialog and the permission bits set by the file attribute mapping.
- </p><p>One way this can show up is if a file has no UNIX read access
- for the owner it will show up as &quot;read only&quot; in the standard
- file attributes tabbed dialog. Unfortunately this dialog is
- the same one that contains the security info in another tab.</p><p>What this can mean is that if the owner changes the permissions
- to allow themselves read access using the security dialog, clicks
- <b>&quot;OK&quot;</b> to get back to the standard attributes tab
- dialog, and then clicks <b>&quot;OK&quot;</b> on that dialog, then
- NT will set the file permissions back to read-only (as that is what
- the attributes still say in the dialog). This means that after setting
- permissions and clicking <b>&quot;OK&quot;</b> to get back to the
- attributes dialog you should always hit <b>&quot;Cancel&quot;</b>
- rather than <b>&quot;OK&quot;</b> to ensure that your changes
- are not overridden.</p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="groupmapping"></a>Chapter12.Configuring Group Mapping</h2></div><div><div class="author"><h3 class="author">Jean Franois Micouleau</h3></div></div><div><div class="author"><h3 class="author">Gerald (Jerry) Carter</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt>&lt;<a href="mailto:jerry@samba.org">jerry@samba.org</a>&gt;</tt></p></div></div></div></div></div><p>
-Starting with Samba 3.0 alpha 2, new group mapping functionality
-is available to create associations between Windows SIDs and UNIX
-groups. The <i><tt>groupmap</tt></i> subcommand included with
-the <b>net</b> tool can be used to manage these associations.
-</p><p>
-The first immediate reason to use the group mapping on a Samba PDC, is that
-the <i><tt>domain admin group</tt></i> <tt>smb.conf</tt> has been removed.
-This parameter was used to give the listed users membership in the &quot;Domain Admins&quot;
-Windows group which gave local admin rights on their workstations (in
-default configurations).
-</p><p>
-When installing NT/W2K on a computer, the installer program creates some users
-and groups. Notably the 'Administrators' group, and gives to that group some
-privileges like the ability to change the date and time or to kill any process
-(or close too) running on the local machine. The 'Administrator' user is a
-member of the 'Administrators' group, and thus 'inherit' the 'Administrators'
-group privileges. If a 'joe' user is created and become a member of the
-'Administrator' group, 'joe' has exactly the same rights as 'Administrator'.
-</p><p>
-When a NT/W2K machine is joined to a domain, the &quot;Domain Adminis&quot; group of the
-PDC is added to the local 'Administrators' group of the workstation. Every
-member of the 'Domain Administrators' group 'inherit' the
-rights of the local 'Administrators' group when logging on the workstation.
-</p><p>
-The following steps describe how to make samba PDC users members of the
-'Domain Admins' group?
-</p><div class="orderedlist"><ol type="1"><li><p>create a unix group (usually in <tt>/etc/group</tt>),
- let's call it domadm</p></li><li><p>add to this group the users that must be Administrators. For example
- if you want joe,john and mary, your entry in <tt>/etc/group</tt> will
- look like:</p><pre class="programlisting">
- domadm:x:502:joe,john,mary
- </pre></li><li><p>Map this domadm group to the &quot;Domain Admins&quot; group
- by running the command:</p><p><tt>root# </tt><b><tt>net groupmap add ntgroup=&quot;Domain Admins&quot; unixgroup=domadm</tt></b></p><p>The quotes around &quot;Domain Admins&quot; are necessary due to the space in the group name. Also make
- sure to leave no whitespace surrounding the equal character (=).</p></li></ol></div><p>Now joe, john and mary are domain administrators!</p><p>
-It is possible to map any arbitrary UNIX group to any Windows NT
-group as well as making any UNIX group a Windows domain group.
-For example, if you wanted to include a UNIX group (e.g. acct) in a ACL on a
-local file or printer on a domain member machine, you would flag
-that group as a domain group by running the following on the Samba PDC:
-</p><p><tt>root# </tt><b><tt>net groupmap add rid=1000 ntgroup=&quot;Accounting&quot; unixgroup=acct</tt></b></p><p>Be aware that the rid parmeter is a unsigned 32 bit integer that should
-normally start at 1000. However, this rid must not overlap with any RID assigned
-to a user. Verifying this is done differently depending on on the passdb backend
-you are using. Future versions of the tools may perform the verification automatically,
-but for now the burden in on you.</p><p>You can list the various groups in the mapping database by executing
-<b>net groupmap list</b>. Here is an example:</p><pre class="programlisting"><tt>root# </tt>net groupmap list
-System Administrators (S-1-5-21-2547222302-1596225915-2414751004-1002) -&gt; sysadmin
-Domain Admins (S-1-5-21-2547222302-1596225915-2414751004-512) -&gt; domadmin
-Domain Users (S-1-5-21-2547222302-1596225915-2414751004-513) -&gt; domuser
-Domain Guests (S-1-5-21-2547222302-1596225915-2414751004-514) -&gt; domguest
-</pre><p>For complete details on <b>net groupmap</b>, refer to the
-net(8) man page.</p></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="printing"></a>Chapter13.Printing Support</h2></div><div><div class="author"><h3 class="author">Gerald (Jerry) Carter</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt>&lt;<a href="mailto:jerry@samba.org">jerry@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author">Patrick Powell</h3><div class="affiliation"><div class="address"><p><tt>&lt;<a href="mailto:papowell@lprng.org">papowell@lprng.org</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate"> (3 May 2001) </p></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2869498">Introduction</a></dt><dt><a href="#id2869614">Configuration</a></dt><dd><dl><dt><a href="#id2869661">Creating [print$]</a></dt><dt><a href="#id2869893">Setting Drivers for Existing Printers</a></dt><dt><a href="#id2869992">Support a large number of printers</a></dt><dt><a href="#id2870099">Adding New Printers via the Windows NT APW</a></dt><dt><a href="#id2870231">Samba and Printer Ports</a></dt></dl></dd><dt><a href="#id2869233">The Imprints Toolset</a></dt><dd><dl><dt><a href="#id2869259">What is Imprints?</a></dt><dt><a href="#id2870336">Creating Printer Driver Packages</a></dt><dt><a href="#id2870355">The Imprints server</a></dt><dt><a href="#id2870379">The Installation Client</a></dt></dl></dd><dt><a href="#id2869340">Diagnosis</a></dt><dd><dl><dt><a href="#id2869347">Introduction</a></dt><dt><a href="#id2870552">Debugging printer problems</a></dt><dt><a href="#id2870619">What printers do I have?</a></dt><dt><a href="#id2870661">Setting up printcap and print servers</a></dt><dt><a href="#id2870795">Job sent, no output</a></dt><dt><a href="#id2871344">Job sent, strange output</a></dt><dt><a href="#id2871420">Raw PostScript printed</a></dt><dt><a href="#id2871438">Advanced Printing</a></dt><dt><a href="#id2871464">Real debugging</a></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2869498"></a>Introduction</h2></div></div><p>Beginning with the 2.2.0 release, Samba supports
-the native Windows NT printing mechanisms implemented via
-MS-RPC (i.e. the SPOOLSS named pipe). Previous versions of
-Samba only supported LanMan printing calls.</p><p>The additional functionality provided by the new
-SPOOLSS support includes:</p><div class="itemizedlist"><ul type="disc"><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
- Imprints tool set (refer to <a href="http://imprints.sourceforge.net" target="_top">http://imprints.sourceforge.net</a>).
- </p></li><li><p>Support for the native MS-RPC printing
- calls such as StartDocPrinter, EnumJobs(), etc... (See
- the MSDN documentation at <a href="http://msdn.microsoft.com/" target="_top">http://msdn.microsoft.com/</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 databases for spooled job
- information</p></li></ul></div><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. 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: <span class="emphasis"><em>How to Add Printers with No User
-Interaction in Windows 2000</em></span>
-</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" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2869614"></a>Configuration</h2></div></div><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">[print$] vs. [printer$]</h3><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 <i><tt>printer driver location</tt></i>
-to be used on a per share basis to specify the location of
-the driver files associated with that printer. Another
-parameter named <i><tt>printer driver</tt></i> provided
-a means of defining the printer driver name to be sent to
-the client.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2869661"></a>Creating [print$]</h3></div></div><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><p>You should modify the server's smb.conf file to add the global
-parameters and 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><pre class="programlisting">
-[global]
- ; members of the ntadmin group should be able
- ; to add drivers and set printer properties
- ; root is implicitly a 'printer admin'
- printer admin = @ntadmin
-
-[print$]
- path = /usr/local/samba/printers
- 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,root
-</pre><p>The <a href="smb.conf.5.html#WRITELIST" target="_top"><i><tt>
-write list</tt></i></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>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><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Author's Note</h3><p>
-The non-issue is that if all your Windows NT users are guaranteed 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>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></div><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><tt>
-[print$]-----
- |-W32X86 ; &quot;Windows NT x86&quot;
- |-WIN40 ; &quot;Windows 95/98&quot;
- |-W32ALPHA ; &quot;Windows NT Alpha_AXP&quot;
- |-W32MIPS ; &quot;Windows NT R4000&quot;
- |-W32PPC ; &quot;Windows NT PowerPC&quot;
-</tt></p><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">ATTENTION! REQUIRED PERMISSIONS</h3><p>
-In order to currently add a new driver to you Samba host,
-one of two conditions must hold true:
-</p><div class="itemizedlist"><ul type="disc"><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#PRINTERADMIN" target="_top"><i><tt>printer
- admin</tt></i></a> list.</p></li></ul></div><p>
-Of course, the connected account must still possess access
-to add files to the subdirectories beneath [print$]. Remember
-that all file shares are set to 'read only' by default.
-</p></div><p>
-Once you have created the required [print$] service and
-associated subdirectories, simply log onto the Samba server using
-a root (or <i><tt>printer admin</tt></i>) account
-from a Windows NT 4.0/2k client. Open &quot;Network Neighbourhood&quot; or
-&quot;My Network Places&quot; and browse for the Samba host. Once you have located
-the server, navigate to the &quot;Printers...&quot; folder.
-You should see an initial listing of printers
-that matches the printer shares defined on your Samba host.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2869893"></a>Setting Drivers for Existing Printers</h3></div></div><p>The initial listing of printers in the Samba host's
-Printers folder will have no real printer driver assigned
-to them. This defaults to a NULL string to allow the use
-of the local Add Printer Wizard on NT/2000 clients.
-Attempting to view the printer properties for a printer
-which has this default driver assigned will result in
-the error message:</p><p>
-<span class="emphasis"><em>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?</em></span>
-</p><p>
-Click &quot;No&quot; in the error dialog and you will be presented with
-the printer properties window. The way to assign a driver to a
-printer is to either
-</p><div class="itemizedlist"><ul type="disc"><li><p>Use the &quot;New Driver...&quot; 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></div><p>If you wish to install printer drivers for client
-operating systems other than &quot;Windows NT x86&quot;, you will need
-to use the &quot;Sharing&quot; 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><p>A few closing comments for this section, 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>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 &quot;Print&quot;
-permissions to the &quot;Everyone&quot; well-known group.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2869992"></a>Support a large number of printers</h3></div></div><p>One issue that has arisen during the development
-phase of Samba 2.2 is the need to support driver downloads for
-100's of printers. Using the Windows NT APW is somewhat
-awkward to say the list. If more than one printer are using the
-same driver, the <a href="rpcclient.1.html" target="_top"><b>rpcclient's
-setdriver command</b></a> can be used to set the driver
-associated with an installed driver. The following is example
-of how this could be accomplished:</p><p>
-<tt>$ </tt><b><tt>rpcclient pogo -U root%secret -c &quot;enumdrivers&quot;</tt></b>
-</p><pre class="programlisting">
-Domain=[NARNIA] OS=[Unix] Server=[Samba 2.2.0-alpha3]
-
-[Windows NT x86]
-Printer Driver Info 1:
- Driver Name: [HP LaserJet 4000 Series PS]
-
-Printer Driver Info 1:
- Driver Name: [HP LaserJet 2100 Series PS]
-
-Printer Driver Info 1:
- Driver Name: [HP LaserJet 4Si/4SiMX PS]
-</pre><p>
-<tt>$ </tt><b><tt>rpcclient pogo -U root%secret -c &quot;enumprinters&quot;</tt></b>
-</p><pre class="programlisting">
-Domain=[NARNIA] OS=[Unix] Server=[Samba 2.2.0-alpha3]
- flags:[0x800000]
- name:[\\POGO\hp-print]
- description:[POGO\\POGO\hp-print,NO DRIVER AVAILABLE FOR THIS PRINTER,]
- comment:[]
-
-</pre><p>
-<tt>$ </tt><b><tt>rpcclient pogo -U root%secret -c &quot;setdriver hp-print \&quot;HP LaserJet 4000 Series PS\&quot;&quot;</tt></b>
-</p><pre class="programlisting">
-Domain=[NARNIA] OS=[Unix] Server=[Samba 2.2.0-alpha3]
-Successfully set hp-print to driver HP LaserJet 4000 Series PS.
-</pre></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2870099"></a>Adding New Printers via the Windows NT APW</h3></div></div><p>
-By default, Samba offers all printer shares defined in <tt>smb.conf</tt>
-in the &quot;Printers...&quot; folder. Also existing in this folder is the Windows NT
-Add Printer Wizard icon. The APW will be show only if
-</p><div class="itemizedlist"><ul type="disc"><li><p>The connected user is able to successfully
- execute an OpenPrinterEx(\\server) with administrative
- privileges (i.e. root or <i><tt>printer admin</tt></i>).
- </p></li><li><p><a href="smb.conf.5.html#SHOWADDPRINTERWIZARD" target="_top"><i><tt>show
- add printer wizard = yes</tt></i></a> (the default).
- </p></li></ul></div><p>
-In order to be able to use the APW to successfully add a printer to a Samba
-server, the <a href="smb.conf.5.html#ADDPRINTERCOMMAND" target="_top"><i><tt>add
-printer command</tt></i></a> must have a defined value. The program
-hook must successfully add the printer to the system (i.e.
-<tt>/etc/printcap</tt> or appropriate files) and
-<tt>smb.conf</tt> if necessary.
-</p><p>
-When using the APW from a client, if the named printer share does
-not exist, <b>smbd</b> will execute the <i><tt>add printer
-command</tt></i> and reparse to the <tt>smb.conf</tt>
-to attempt to locate the new printer share. If the share is still not defined,
-an error of &quot;Access Denied&quot; is returned to the client. Note that the
-<i><tt>add printer program</tt></i> is executed under the context
-of the connected user, not necessarily a root account.
-</p><p>
-There is a complementary <a href="smb.conf.5.html#DELETEPRINTERCOMMAND" target="_top"><i><tt>delete
-printer command</tt></i></a> for removing entries from the &quot;Printers...&quot;
-folder.
-</p><p>
-The following is an example <a href="smb.conf.5.html#ADDPRINTERCOMMAN" target="_top"><i><tt>add printer command</tt></i></a> script. It adds the appropriate entries to <tt>/etc/printcap.local</tt> (change that to what you need) and returns a line of 'Done' which is needed for the whole process to work.
-</p><pre class="programlisting">
-#!/bin/sh
-
-# Script to insert a new printer entry into printcap.local
-#
-# $1, printer name, used as the descriptive name
-# $2, share name, used as the printer name for Linux
-# $3, port name
-# $4, driver name
-# $5, location, used for the device file of the printer
-# $6, win9x location
-
-#
-# Make sure we use the location that RedHat uses for local printer defs
-PRINTCAP=/etc/printcap.local
-DATE=`date +%Y%m%d-%H%M%S`
-LP=lp
-RESTART=&quot;service lpd restart&quot;
-
-# Keep a copy
-cp $PRINTCAP $PRINTCAP.$DATE
-# Add the printer to $PRINTCAP
-echo &quot;&quot; &gt;&gt; $PRINTCAP
-echo &quot;$2|$1:\\&quot; &gt;&gt; $PRINTCAP
-echo &quot; :sd=/var/spool/lpd/$2:\\&quot; &gt;&gt; $PRINTCAP
-echo &quot; :mx=0:ml=0:sh:\\&quot; &gt;&gt; $PRINTCAP
-echo &quot; :lp=/usr/local/samba/var/print/$5.prn:&quot; &gt;&gt; $PRINTCAP
-
-touch &quot;/usr/local/samba/var/print/$5.prn&quot; &gt;&gt; /tmp/printadd.$$ 2&gt;&amp;1
-chown $LP &quot;/usr/local/samba/var/print/$5.prn&quot; &gt;&gt; /tmp/printadd.$$ 2&gt;&amp;1
-
-mkdir /var/spool/lpd/$2
-chmod 700 /var/spool/lpd/$2
-chown $LP /var/spool/lpd/$2
-#echo $1 &gt;&gt; &quot;/usr/local/samba/var/print/$5.prn&quot;
-#echo $2 &gt;&gt; &quot;/usr/local/samba/var/print/$5.prn&quot;
-#echo $3 &gt;&gt; &quot;/usr/local/samba/var/print/$5.prn&quot;
-#echo $4 &gt;&gt; &quot;/usr/local/samba/var/print/$5.prn&quot;
-#echo $5 &gt;&gt; &quot;/usr/local/samba/var/print/$5.prn&quot;
-#echo $6 &gt;&gt; &quot;/usr/local/samba/var/print/$5.prn&quot;
-$RESTART &gt;&gt; &quot;/usr/local/samba/var/print/$5.prn&quot;
-# Not sure if this is needed
-touch /usr/local/samba/lib/smb.conf
-#
-# You need to return a value, but I am not sure what it means.
-#
-echo &quot;Done&quot;
-exit 0
-</pre></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2870231"></a>Samba and Printer Ports</h3></div></div><p>
-Windows NT/2000 print servers associate a port with each printer. These normally
-take the form of LPT1:, COM1:, FILE:, etc... Samba must also support the
-concept of ports associated with a printer. By default, only one printer port,
-named &quot;Samba Printer Port&quot;, exists on a system. Samba does not really a port in
-order to print, rather it is a requirement of Windows clients.
-</p><p>
-Note that Samba does not support the concept of &quot;Printer Pooling&quot; internally
-either. This is when a logical printer is assigned to multiple ports as
-a form of load balancing or fail over.
-</p><p>
-If you require that multiple ports be defined for some reason,
-<tt>smb.conf</tt> possesses a <a href="smb.conf.5.html#ENUMPORTSCOMMAND" target="_top"><i><tt>enumports
-command</tt></i></a> which can be used to define an external program
-that generates a listing of ports on a system.
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2869233"></a>The Imprints Toolset</h2></div></div><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" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2869259"></a>What is Imprints?</h3></div></div><p>Imprints is a collection of tools for supporting the goals
- of</p><div class="itemizedlist"><ul type="disc"><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><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2870336"></a>Creating Printer Driver Packages</h3></div></div><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" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2870355"></a>The Imprints server</h3></div></div><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
- <span class="emphasis"><em>not</em></span> recommended that this security check
- be disabled.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2870379"></a>The Installation Client</h3></div></div><p>More information regarding the Imprints installation client
- is available in the <tt>Imprints-Client-HOWTO.ps</tt>
- file included with the imprints source package.</p><p>The Imprints installation client comes in two forms.</p><div class="itemizedlist"><ul type="disc"><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></div><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>smbclient</b>
- and <b>rpcclient</b>.</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>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 &quot;Apple LaserWriter II NTX v51.8&quot;
- and Windows 95 calls its version of this driver &quot;Apple
- LaserWriter II NTX&quot;</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>HKLM\System\CurrentControlSet\Control\Print\Environment
- </tt></p><p>will reveal that Windows NT always uses the NT driver
- 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
- 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" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2869340"></a>Diagnosis</h2></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2869347"></a>Introduction</h3></div></div><p>
-This is a short description of how to debug printing problems with
-Samba. This describes how to debug problems with printing from a SMB
-client to a Samba server, not the other way around. For the reverse
-see the examples/printing directory.
-</p><p>
-Ok, so you want to print to a Samba server from your PC. The first
-thing you need to understand is that Samba does not actually do any
-printing itself, it just acts as a middleman between your PC client
-and your Unix printing subsystem. Samba receives the file from the PC
-then passes the file to a external &quot;print command&quot;. What print command
-you use is up to you.
-</p><p>
-The whole things is controlled using options in smb.conf. The most
-relevant options (which you should look up in the smb.conf man page)
-are:
-</p><pre class="programlisting">
- [global]
- print command - send a file to a spooler
- lpq command - get spool queue status
- lprm command - remove a job
- [printers]
- path = /var/spool/lpd/samba
-</pre><p>
-The following are nice to know about:
-</p><pre class="programlisting">
- queuepause command - stop a printer or print queue
- queueresume command - start a printer or print queue
-</pre><p>
-Example:
-</p><pre class="programlisting">
- print command = /usr/bin/lpr -r -P%p %s
- lpq command = /usr/bin/lpq -P%p %s
- lprm command = /usr/bin/lprm -P%p %j
- queuepause command = /usr/sbin/lpc -P%p stop
- queuepause command = /usr/sbin/lpc -P%p start
-</pre><p>
-Samba should set reasonable defaults for these depending on your
-system type, but it isn't clairvoyant. It is not uncommon that you
-have to tweak these for local conditions. The commands should
-always have fully specified pathnames, as the smdb may not have
-the correct PATH values.
-</p><p>
-When you send a job to Samba to be printed, it will make a temporary
-copy of it in the directory specified in the [printers] section.
-and it should be periodically cleaned out. The lpr -r option
-requests that the temporary copy be removed after printing; If
-printing fails then you might find leftover files in this directory,
-and it should be periodically cleaned out. Samba used the lpq
-command to determine the &quot;job number&quot; assigned to your print job
-by the spooler.
-</p><p>
-The %&gt;letter&lt; are &quot;macros&quot; that get dynamically replaced with appropriate
-values when they are used. The %s gets replaced with the name of the spool
-file that Samba creates and the %p gets replaced with the name of the
-printer. The %j gets replaced with the &quot;job number&quot; which comes from
-the lpq output.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2870552"></a>Debugging printer problems</h3></div></div><p>
-One way to debug printing problems is to start by replacing these
-command with shell scripts that record the arguments and the contents
-of the print file. A simple example of this kind of things might
-be:
-</p><pre class="programlisting">
- print command = /tmp/saveprint %p %s
-
- #!/bin/saveprint
- # we make sure that we are the right user
- /usr/bin/id -p &gt;/tmp/tmp.print
- # we run the command and save the error messages
- # replace the command with the one appropriate for your system
- /usr/bin/lpr -r -P$1 $2 2&gt;&gt;&amp;/tmp/tmp.print
-</pre><p>
-Then you print a file and try removing it. You may find that the
-print queue needs to be stopped in order to see the queue status
-and remove the job:
-</p><pre class="programlisting">
-
-h4: {42} % echo hi &gt;/tmp/hi
-h4: {43} % smbclient //localhost/lw4
-added interface ip=10.0.0.4 bcast=10.0.0.255 nmask=255.255.255.0
-Password:
-Domain=[ASTART] OS=[Unix] Server=[Samba 2.0.7]
-smb: \&gt; print /tmp/hi
-putting file /tmp/hi as hi-17534 (0.0 kb/s) (average 0.0 kb/s)
-smb: \&gt; queue
-1049 3 hi-17534
-smb: \&gt; cancel 1049
-Error cancelling job 1049 : code 0
-smb: \&gt; cancel 1049
-Job 1049 cancelled
-smb: \&gt; queue
-smb: \&gt; exit
-</pre><p>
-The 'code 0' indicates that the job was removed. The comment
-by the smbclient is a bit misleading on this.
-You can observe the command output and then and look at the
-/tmp/tmp.print file to see what the results are. You can quickly
-find out if the problem is with your printing system. Often people
-have problems with their /etc/printcap file or permissions on
-various print queues.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2870619"></a>What printers do I have?</h3></div></div><p>
-You can use the 'testprns' program to check to see if the printer
-name you are using is recognized by Samba. For example, you can
-use:
-</p><pre class="programlisting">
- testprns printer /etc/printcap
-</pre><p>
-Samba can get its printcap information from a file or from a program.
-You can try the following to see the format of the extracted
-information:
-</p><pre class="programlisting">
- testprns -a printer /etc/printcap
-
- testprns -a printer '|/bin/cat printcap'
-</pre></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2870661"></a>Setting up printcap and print servers</h3></div></div><p>
-You may need to set up some printcaps for your Samba system to use.
-It is strongly recommended that you use the facilities provided by
-the print spooler to set up queues and printcap information.
-</p><p>
-Samba requires either a printcap or program to deliver printcap
-information. This printcap information has the format:
-</p><pre class="programlisting">
- name|alias1|alias2...:option=value:...
-</pre><p>
-For almost all printing systems, the printer 'name' must be composed
-only of alphanumeric or underscore '_' characters. Some systems also
-allow hyphens ('-') as well. An alias is an alternative name for the
-printer, and an alias with a space in it is used as a 'comment'
-about the printer. The printcap format optionally uses a \ at the end of lines
-to extend the printcap to multiple lines.
-</p><p>
-Here are some examples of printcap files:
-</p><p>
-</p><div class="orderedlist"><ol type="1"><li><p>
-pr just printer name
-</p></li><li><p>
-pr|alias printer name and alias
-</p></li><li><p>
-pr|My Printer printer name, alias used as comment
-</p></li><li><p>
-pr:sh:\ Same as pr:sh:cm= testing
- :cm= \
- testing
-</p></li><li><p>
-pr:sh Same as pr:sh:cm= testing
- :cm= testing
-</p></li></ol></div><p>
-</p><p>
-Samba reads the printcap information when first started. If you make
-changes in the printcap information, then you must do the following:
-</p><div class="orderedlist"><ol type="1"><li><p>
-make sure that the print spooler is aware of these changes.
-The LPRng system uses the 'lpc reread' command to do this.
-</p></li><li><p>
-make sure that the spool queues, etc., exist and have the
-correct permissions. The LPRng system uses the 'checkpc -f'
-command to do this.
-</p></li><li><p>
-You now should send a SIGHUP signal to the smbd server to have
-it reread the printcap information.
-</p></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2870795"></a>Job sent, no output</h3></div></div><p>
-This is the most frustrating part of printing. You may have sent the
-job, verified that the job was forwarded, set up a wrapper around
-the command to send the file, but there was no output from the printer.
-</p><p>
-First, check to make sure that the job REALLY is getting to the
-right print queue. If you are using a BSD or LPRng print spooler,
-you can temporarily stop the printing of jobs. Jobs can still be
-submitted, but they will not be printed. Use:
-</p><pre class="programlisting">
- lpc -Pprinter stop
-</pre><p>
-Now submit a print job and then use 'lpq -Pprinter' to see if the
-job is in the print queue. If it is not in the print queue then
-you will have to find out why it is not being accepted for printing.
-</p><p>
-Next, you may want to check to see what the format of the job really
-was. With the assistance of the system administrator you can view
-the submitted jobs files. You may be surprised to find that these
-are not in what you would expect to call a printable format.
-You can use the UNIX 'file' utitily to determine what the job
-format actually is:
-</p><pre class="programlisting">
- cd /var/spool/lpd/printer # spool directory of print jobs
- ls # find job files
- file dfA001myhost
-</pre><p>
-You should make sure that your printer supports this format OR that
-your system administrator has installed a 'print filter' that will
-convert the file to a format appropriate for your printer.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2871344"></a>Job sent, strange output</h3></div></div><p>
-Once you have the job printing, you can then start worrying about
-making it print nicely.
-</p><p>
-The most common problem is extra pages of output: banner pages
-OR blank pages at the end.
-</p><p>
-If you are getting banner pages, check and make sure that the
-printcap option or printer option is configured for no banners.
-If you have a printcap, this is the :sh (suppress header or banner
-page) option. You should have the following in your printer.
-</p><pre class="programlisting">
- printer: ... :sh
-</pre><p>
-If you have this option and are still getting banner pages, there
-is a strong chance that your printer is generating them for you
-automatically. You should make sure that banner printing is disabled
-for the printer. This usually requires using the printer setup software
-or procedures supplied by the printer manufacturer.
-</p><p>
-If you get an extra page of output, this could be due to problems
-with your job format, or if you are generating PostScript jobs,
-incorrect setting on your printer driver on the MicroSoft client.
-For example, under Win95 there is a option:
-</p><pre class="programlisting">
- Printers|Printer Name|(Right Click)Properties|Postscript|Advanced|
-</pre><p>
-that allows you to choose if a Ctrl-D is appended to all jobs.
-This is a very bad thing to do, as most spooling systems will
-automatically add a ^D to the end of the job if it is detected as
-PostScript. The multiple ^D may cause an additional page of output.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2871420"></a>Raw PostScript printed</h3></div></div><p>
-This is a problem that is usually caused by either the print spooling
-system putting information at the start of the print job that makes
-the printer think the job is a text file, or your printer simply
-does not support PostScript. You may need to enable 'Automatic
-Format Detection' on your printer.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2871438"></a>Advanced Printing</h3></div></div><p>
-Note that you can do some pretty magic things by using your
-imagination with the &quot;print command&quot; option and some shell scripts.
-Doing print accounting is easy by passing the %U option to a print
-command shell script. You could even make the print command detect
-the type of output and its size and send it to an appropriate
-printer.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2871464"></a>Real debugging</h3></div></div><p>
-If the above debug tips don't help, then maybe you need to bring in
-the bug guns, system tracing. See Tracing.txt in this directory.
-</p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="CUPS-printing"></a>Chapter14.CUPS Printing Support</h2></div><div><div class="author"><h3 class="author">John H. Terpstra</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt>&lt;<a href="mailto:jht@samba.org">jht@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author">Kurt Pfeifle</h3><div class="affiliation"><div class="address"><p><tt>&lt;<a href="mailto:kpfeifle@danka.de">kpfeifle@danka.de</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate"> (25 March 2003) </p></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2871008">Introduction</a></dt><dt><a href="#id2871067">Configuring smb.conf for CUPS</a></dt><dt><a href="#id2871607">CUPS - RAW Print Through Mode</a></dt><dt><a href="#id2871091">CUPS as a network PostScript RIP</a></dt><dt><a href="#id2872272">Windows Terminal Servers (WTS) as CUPS clients</a></dt><dt><a href="#id2872314">Setting up CUPS for driver download</a></dt><dt><a href="#id2872401">Sources of CUPS drivers / PPDs</a></dt><dd><dl><dt><a href="#id2872566">cupsaddsmb</a></dt></dl></dd><dt><a href="#id2872915">The CUPS Filter Chains</a></dt><dt><a href="#id2873302">CUPS Print Drivers and Devices</a></dt><dd><dl><dt><a href="#id2873339">Further printing steps</a></dt></dl></dd><dt><a href="#id2873758">Limiting the number of pages users can print</a></dt><dt><a href="#id2874367">Advanced Postscript Printing from MS Windows</a></dt><dt><a href="#id2874473">Auto-Deletion of CUPS spool files</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2871008"></a>Introduction</h2></div></div><p>
-The Common Unix Print System (CUPS) has become very popular, but to many it is
-a very mystical tool. There is a great deal of uncertainty regarding CUPS and how
-it works. The result is seen in a large number of posting on the samba mailing lists
-expressing frustration when MS Windows printers appear not to work with a CUPS
-backr-end.
-</p><p>
-This is a good time to point out how CUPS can be used and what it does. CUPS is more
-than just a print spooling system - it is a complete printer management system that
-complies with HTTP and IPP protocols. It can be managed remotely via a web browser
-and it can print using http and ipp protocols.
-</p><p>
-CUPS allows to creation of RAW printers (ie: NO file format translation) as well as
-SMART printers (ie: CUPS does file format conversion as required for the printer). In
-many ways this gives CUPS similar capabilities to the MS Windows print monitoring
-system. Of course, if you are a CUPS advocate, you would agrue that CUPS is better!
-In any case, let us now move on to explore how one may configure CUPS for interfacing
-with MS Windows print clients via Samba.
-</p><p>
-<a href="http://www.cups.org/" target="_top">CUPS</a> is a newcomer in the UNIX printing scene,
-which has convinced many people upon first trial already. However, it has quite a few
-new features, which make it different from other, more traditional printing systems.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2871067"></a>Configuring <tt>smb.conf</tt> for CUPS</h2></div></div><p>
-Printing with CUPS in the most basic <tt>smb.conf</tt>
-setup in Samba-3 only needs two settings: <b>printing = cups</b> and
-<b>printcap = cups</b>. While CUPS itself doesn't need a printcap
-anymore, the <tt>cupsd.conf</tt> configuration file knows two directives
-(example: <b>Printcap /etc/printcap</b> and <b>PrintcapFormat
-BSD</b>), which control if such a file should be created for the
-convenience of third party applications. Make sure it is set! For details see
-<b>man cupsd.conf</b> and other CUPS-related documentation.
-</p><p>
-If SAMBA is compiled against libcups, then <b>printcap = cups</b> uses the
-CUPS API to list printers, submit jobs, etc. Otherwise it maps to the System V commands
-with an additional <i><tt>-oraw</tt></i> option for printing. On a Linux system,
-you can use the <b>ldd</b> command to find out details (ldd may not be
-present on other OS platforms, or its function may be embodied by a different command):
-</p><p>
-</p><pre class="programlisting">transmeta:/home/kurt # ldd `which smbd`
- libssl.so.0.9.6 =&gt; /usr/lib/libssl.so.0.9.6 (0x4002d000)
- libcrypto.so.0.9.6 =&gt; /usr/lib/libcrypto.so.0.9.6 (0x4005a000)
- libcups.so.2 =&gt; /usr/lib/libcups.so.2 (0x40123000)
- libdl.so.2 =&gt; /lib/libdl.so.2 (0x401e8000)
- libnsl.so.1 =&gt; /lib/libnsl.so.1 (0x401ec000)
- libpam.so.0 =&gt; /lib/libpam.so.0 (0x40202000)
- libc.so.6 =&gt; /lib/libc.so.6 (0x4020b000)
- /lib/ld-linux.so.2 =&gt; /lib/ld-linux.so.2 (0x40000000)
-</pre><p>
-The line &quot;libcups.so.2 =&gt; /usr/lib/libcups.so.2
-(0x40123000)&quot; shows there is CUPS support compiled into this version of
-Samba. If this is the case, and <b>printing = cups</b> is set, then any
-otherwise manually set print command in <tt>smb.conf</tt> is ignored.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2871607"></a>CUPS - RAW Print Through Mode</h2></div></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-When used in raw print through mode is will be necessary to use the printer
-vendor's drivers in each Windows client PC.
-</p></div><p>
-When CUPS printers are configured for RAW print-through mode operation it is the
-responsibility of the Samba client to fully render the print job (file) in a format
-that is suitable for direct delivery to the printer. In this case CUPS will NOT
-do any print file format conversion work.
-</p><p>
-The CUPS files that need to be correctly set for RAW mode printers to work are:
-
-</p><div class="itemizedlist"><ul type="disc"><li><p><tt>/etc/cups/mime.types</tt></p></li><li><p><tt>/etc/cups/mime.convs</tt></p></li></ul></div><p>
-
-Both contain entries that must be uncommented to allow <span class="emphasis"><em>RAW</em></span> mode
-operation.
-</p><p>
-Firstly, to enable CUPS based printing from Samba the following options must be
-enabled in your <tt>smb.conf</tt> file [globals] section:
-
-</p><div class="itemizedlist"><ul type="disc"><li><p>printing = CUPS</p></li><li><p>printcap = CUPS</p></li></ul></div><p>
-
-When these parameters are specified the print directives in <tt>smb.conf</tt> (as well as in
-samba itself) will be ignored because samba will directly interface with CUPS through
-it's application program interface (API) - so long as Samba has been compiled with
-CUPS library (libcups) support. If samba has NOT been compiled with CUPS support then
-printing will use the System V AT&amp;T command set with the <span class="emphasis"><em>-oraw</em></span>
-option automatically passing through.
-</p><p>
-Cupsomatic (an enhanced printing utility that is part of some CUPS implementations)
-on the Samba/CUPS server does *not* add any features if a file is really
-printed &quot;raw&quot;. However, if you have loaded the driver for the Windows client from
-the CUPS server, using the &quot;cupsaddsmb&quot; utility, and if this driver is one using
-a &quot;Foomatic&quot; PPD, the PJL header in question is already added on the Windows client,
-at the time when the driver initially generated the PostScript data and CUPS in true
-&quot;-oraw&quot; manner doesn't remove this PJL header and passes the file &quot;as is&quot; to its
-printer communication backend.
-</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>NOTE: editing in the &quot;mime.convs&quot; and the &quot;mime.types&quot; file does not *enforce*
-&quot;raw&quot; printing, it only *allows* it.</p></div><p>
-Print files that arrive from MS Windows printing are &quot;auto-typed&quot; by CUPS. This aids
-the process of determining proper treatment while in the print queue system.
-
-</p><div class="itemizedlist"><ul type="disc"><li><p>
- Files generated by PCL drivers and directed at PCK printers get auto-typed as
- <tt>application/octet-stream</tt>. Unknown file format types also
- get auto-typed with this tag.
- </p></li><li><p>
- Files generated by a Postscript driver and directed at a Postscript printer
- are auto-typed depending on the auto-detected most suitable MIME type as:
-
- </p><div class="itemizedlist"><ul type="circle"><li><p>* application/postscript</p></li><li><p>* application/vnd.cups-postscript</p></li></ul></div><p>
- </p></li></ul></div><p>
-</p><p>
-&quot;application/postscript&quot; first goes thru the &quot;pstops&quot; filter (where the page counting
-and accounting takes place). The outcome will be of MIME type
-&quot;application/vnd.cups-postscript&quot;. The pstopsfilter reads and uses information from
-the PPD and inserts user-provided options into the PostScript file. As a consequence,
-the filtered file could possibly have an unwanted PJL header.
-</p><p>
-&quot;application/postscript&quot; will be all files with a &quot;.ps&quot;, &quot;.ai&quot;, &quot;.eps&quot; suffix or which
-have as their first character string one of &quot;%!&quot; or &quot;&gt;04&lt;%&quot;.
-</p><p>
-&quot;application/vnd.cups-postscript&quot; will files which contain the string
-&quot;LANGUAGE=POSTSCRIPT&quot; (or similar variations with different capitalization) in the
-first 512 bytes, and also contain the &quot;PJL super escape code&quot; in the first 128 bytes
-(&quot;&gt;1B&lt;%-12345X&quot;). Very likely, most PostScript files generated on Windows using a CUPS
-or other PPD, will have to be auto-typed as &quot;vnd.cups-postscript&quot;. A file produced
-with a &quot;Generic PostScript driver&quot; will just be tagged &quot;application/postscript&quot;.
-</p><p>
-Once the file is in &quot;application/vnd.cups-postscript&quot; format, either &quot;pstoraster&quot;
-or &quot;cupsomatic&quot; will take over (depending on the printer configuration, as
-determined by the PPD in use).
-</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-A printer queue with *no* PPD associated to it is a &quot;raw&quot; printer and all files
-will go directly there as received by the spooler. The exeptions are file types
-&quot;application/octet-stream&quot; which need &quot;passthrough feature&quot; enabled.
-&quot;Raw&quot; queues don't do any filtering at all, they hand the file directly to the
-CUPS backend. This backend is responsible for the sending of the data to the device
-(as in the &quot;device URI&quot; notation as lpd://, socket://, smb://, ipp://, http://,
-parallel:/, serial:/, usb:/ etc.)
-</p></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-&quot;cupsomatic&quot;/Foomatic are *not* native CUPS drivers and they don't ship with CUPS.
-They are a Third Party add-on, developed at Linuxprinting.org. As such, they are
-a brilliant hack to make all models (driven by Ghostscript drivers/filters in
-traditional spoolers) also work via CUPS, with the same (good or bad!) quality
-as in these other spoolers. &quot;cupsomatic&quot; is only a vehicle to execute a ghostscript
-commandline at that stage in the CUPS filtering chain, where &quot;normally&quot; the native
-CUPS &quot;pstoraster&quot; filter would kick in. cupsomatic by-passes pstoraster, &quot;kidnaps&quot;
-the printfile from CUPS away and re-directs it to go through Ghostscipt. CUPS accepts this,
-because the associated CUPS-O-Matic-/Foomatic-PPD specifies:
-</p><pre class="programlisting">
- *cupsFilter: &quot;application/vnd.cups-postscript 0 cupsomatic&quot;
-</pre><p>
-This line persuades CUPS to hand the file to cupsomatic, once it has successfully
-converted it to the MIME type &quot;application/vnd.cups-postscript&quot;. This conversion will not
-happen for Jobs arriving from Windows which are auto-typed &quot;application/octet-stream&quot;,
-with the according changes in &quot;/etc/cups/mime.types&quot; in place.
-</p></div><p>
-CUPS is widely configurable and flexible, even regarding its filtering mechanism.
-Another workaround in some situations would be to have
-in &quot;/etc/cups/mime.types&quot; entries as follows:
-</p><pre class="programlisting">
- application/postscript application/vnd.cups-raw 0 -
- application/vnd.cups-postscript application/vnd.cups-raw 0 -
-</pre><p>
-This would prevent all Postscript files from being filtered (rather, they will go
-thru the virtual &quot;nullfilter&quot; denoted with &quot;-&quot;). This could only be useful for
-PS printers. If you want to print PS code on non-PS printers an entry as follows
-could be useful:
-</p><pre class="programlisting">
- */* application/vnd.cups-raw 0 -
-</pre><p>
-and would effectively send *all* files to the backend without further processing.
-</p><p>
-Lastly, you could have the following entry:
-</p><pre class="programlisting">
- application/vnd.cups-postscript application/vnd.cups-raw 0 my_PJL_stripping_filter
-</pre><p>
-You will need to write a &quot;my_PJL_stripping_filter&quot; (could be a shellscript) that
-parses the PostScript and removes the unwanted PJL. This would need to conform to
-CUPS filter design (mainly, receive and pass the parameters printername, job-id,
-username, jobtitle, copies, print options and possibly the filename). It would
-be installed as world executable into &quot;/usr/lib/cups/filters/&quot; and will be called
-by CUPS if it encounters a MIME type &quot;application/vnd.cups-postscript&quot;.
-</p><p>
-CUPS can handle &quot;-o job-hold-until=indefinite&quot;. This keeps the job in the queue
-&quot;on hold&quot;. It will only be printed upon manual release by the printer operator.
-This is a requirement in many &quot;central reproduction departments&quot;, where a few
-operators manage the jobs of hundreds of users on some big machine, where no
-user is allowed to have direct access. (The operators often need to load the
-proper paper type before running the 10.000 page job requested by marketing
-for the mailing, etc.).
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2871091"></a>CUPS as a network PostScript RIP</h2></div></div><p>
-This is the configuration where CUPS drivers are working on server, and where the
-Adobe PostScript driver with CUPS-PPDs is downloaded to clients.
-</p><p>
-CUPS is perfectly able to use PPD files (PostScript
-Printer Descriptions). PPDs can control all print device options. They
-are usually provided by the manufacturer -- if you own a PostSript printer,
-that is. PPD files are always a component of PostScript printer drivers on MS
-Windows or Apple Mac OS systems. They are ASCII files containing
-user-selectable print options, mapped to appropriate PostScript, PCL or PJL
-commands for the target printer. Printer driver GUI dialogs translate these
-options &quot;on-the-fly&quot; into buttons and drop-down lists for the user to
-select.
-</p><p>
-CUPS can load, without any conversions, the PPD file from
-any Windows (NT is recommended) PostScript driver and handle the options.
-There is a web browser interface to the print options (select
-http://localhost:631/printers/ and click on one &quot;Configure Printer&quot; button
-to see it), a commandline interface (see <b>man lpoptions</b> or
-try if you have <b>lphelp</b> on your system) plus some different GUI frontends on Linux
-UNIX, which can present PPD options to the users. PPD options are normally
-meant to become evaluated by the PostScript RIP on the real PostScript
-printer.
-</p><p>
-CUPS doesn't stop at &quot;real&quot; PostScript printers in its
-usage of PPDs. The CUPS developers have extended the PPD concept, to also
-describe available device and driver options for non-PostScript printers
-through CUPS-PPDs.
-</p><p>
-This is logical, as CUPS includes a fully featured
-PostScript interpreter (RIP). This RIP is based on Ghostscript. It can
-process all received PostScript (and additionally many other file formats)
-from clients. All CUPS-PPDs geared to non-PostScript printers contain an
-additional line, starting with the keyword <i><tt>*cupsFilter</tt></i>.
-This line
-tells the CUPS print system which printer-specific filter to use for the
-interpretation of the accompanying PostScript. Thus CUPS lets all its
-printers appear as PostScript devices to its clients, because it can act as a
-PostScript RIP for those printers, processing the received PostScript code
-into a proper raster print format.
-</p><p>
-CUPS-PPDs can also be used on Windows-Clients, on top of a
-PostScript driver (recommended is the Adobe one).
-</p><p>
-This feature enables CUPS to do a few tricks no other
-spooler can do:
-</p><div class="itemizedlist"><ul type="disc"><li><p>act as a networked PostScript RIP (Raster Image Processor), handling
- printfiles from all client platforms in a uniform way;</p></li><li><p>act as a central accounting and billing server, as all files are passed
- through the <b>pstops</b> Filter and are therefor logged in
- the CUPS <tt>page_log</tt>. - <span class="emphasis"><em>NOTE: </em></span>this
- can not happen with &quot;raw&quot; print jobs, which always remain unfiltered
- per definition;</p></li><li><p>enable clients to consolidate on a single PostScript driver, even for
- many different target printers.</p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2872272"></a>Windows Terminal Servers (WTS) as CUPS clients</h2></div></div><p>
-This setup may be of special interest to people
-experiencing major problems in WTS environments. WTS need often a multitude
-of non-PostScript drivers installed to run their clients' variety of
-different printer models. This often imposes the price of much increased
-instability. In many cases, in an attempt to overcome this problem, site
-administrators have resorted to restrict the allowed drivers installed on
-their WTS to one generic PCL- and one PostScript driver. This however
-restricts the clients in the amount of printer options available for them --
-often they can't get out more then simplex prints from one standard paper
-tray, while their devices could do much better, if driven by a different
-driver!
-</p><p>
-Using an Adobe PostScript driver, enabled with a CUPS-PPD,
-seems to be a very elegant way to overcome all these shortcomings. The
-PostScript driver is not known to cause major stability problems on WTS (even
-if used with many different PPDs). The clients will be able to (again) chose
-paper trays, duplex printing and other settings. However, there is a certain
-price for this too: a CUPS server acting as a PostScript RIP for its clients
-requires more CPU and RAM than just to act as a &quot;raw spooling&quot; device. Plus,
-this setup is not yet widely tested, although the first feedbacks look very
-promising...
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2872314"></a>Setting up CUPS for driver download</h2></div></div><p>
-The <b>cupsadsmb</b> utility (shipped with all current
-CUPS versions) makes the sharing of any (or all) installed CUPS printers very
-easy. Prior to using it, you need the following settings in <tt>smb.conf</tt>:
-</p><pre class="programlisting">[global]
- load printers = yes
- printing = cups
- printcap name = cups
-
- [printers]
- comment = All Printers
- path = /var/spool/samba
- browseable = no
- public = yes
- guest ok = yes
- writable = no
- printable = yes
- printer admin = root
-
- [print$]
- comment = Printer Drivers
- path = /etc/samba/drivers
- browseable = yes
- guest ok = no
- read only = yes
- write list = root
- </pre><p>
-For licensing reasons the necessary files of the Adobe
-Postscript driver can not be distributed with either Samba or CUPS. You need
-to download them yourself from the Adobe website. Once extracted, create a
-<tt>drivers</tt> directory in the CUPS data directory (usually
-<tt>/usr/share/cups/</tt>). Copy the Adobe files using
-UPPERCASE filenames, to this directory as follows:
-</p><pre class="programlisting">
- ADFONTS.MFM
- ADOBEPS4.DRV
- ADOBEPS4.HLP
- ADOBEPS5.DLL
- ADOBEPSU.DLL
- ADOBEPSU.HLP
- DEFPRTR2.PPD
- ICONLIB.DLL
- </pre><p>
-Users of the ESP Print Pro software are able to install
-their &quot;Samba Drivers&quot; package for this purpose with no problem.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2872401"></a>Sources of CUPS drivers / PPDs</h2></div></div><p>
-On the internet you can find now many thousand CUPS-PPD
-files (with their companion filters), in many national languages,
-supporting more than 1.000 non-PostScript models.
-</p><div class="itemizedlist"><ul type="disc"><li><p><a href="http://wwwl.easysw.com/printpro/" target="_top">ESP PrintPro
- (http://wwwl.easysw.com/printpro/)</a>
- (commercial, non-Free) is packaged with more than 3.000 PPDs, ready for
- successful usage &quot;out of the box&quot; on Linux, IBM-AIX, HP-UX, Sun-Solaris,
- SGI-IRIX, Compaq Tru64, Digital Unix and some more commercial Unices (it
- is written by the CUPS developers themselves and its sales help finance
- the further development of CUPS, as they feed their creators)</p></li><li><p>the <a href="http://gimp-print.sourceforge.net/" target="_top">Gimp-Print-Project
- (http://gimp-print.sourceforge.net/)</a>
- (GPL, Free Software) provides around 120 PPDs (supporting nearly 300
- printers, many driven to photo quality output), to be used alongside the
- Gimp-Print CUPS filters;</p></li><li><p><a href="http://www.turboprint.com/" target="_top">TurboPrint
- (http://www.turboprint.com/)</a>
- (Shareware, non-Freee) supports roughly the same amount of printers in
- excellent quality;</p></li><li><p><a href="http://www-124.ibm.com/developerworks/oss/linux/projects/omni/" target="_top">OMNI
- (http://www-124.ibm.com/developerworks/oss/linux/projects/omni/)</a>
- (LPGL, Free) is a package made by IBM, now containing support for more
- than 400 printers, stemming from the inheritance of IBM OS/2 KnowHow
- ported over to Linux (CUPS support is in a Beta-stage at present);</p></li><li><p><a href="http://hpinkjet.sourceforge.net/" target="_top">HPIJS
- (http://hpinkjet.sourceforge.net/)</a>
- (BSD-style licnes, Free) supports around 120 of HP's own printers and is
- also providing excellent print quality now;</p></li><li><p><a href="http://www.linuxprinting.org/" target="_top">Foomatic/cupsomatic (http://www.linuxprinting.org/)</a>
- (LPGL, Free) from Linuxprinting.org are providing PPDs for practically every
- Ghostscript filter known to the world, now usable with CUPS.</p></li></ul></div><p>
-<span class="emphasis"><em>NOTE: </em></span>the cupsomatic trick from Linuxprinting.org is
-working different from the other drivers. While the other drivers take the
-generic CUPS raster (produced by CUPS' own pstoraster PostScript RIP) as
-their input, cupsomatic &quot;kidnaps&quot; the PostScript inside CUPS, before
-RIP-ping, deviates it to an external Ghostscript installation (which now
-becomes the RIP) and gives it back to a CUPS backend once Ghostscript is
-finished. -- CUPS versions from 1.1.15 and later will provide their pstoraster
-PostScript RIP function again inside a system-wide Ghostscript
-installation rather than in &quot;their own&quot; pstoraster filter. (This
-CUPS-enabling Ghostscript version may be installed either as a
-patch to GNU or AFPL Ghostscript, or as a complete ESP Ghostscript package).
-However, this will not change the cupsomatic approach of guiding the printjob
-along a different path through the filtering system than the standard CUPS
-way...
-</p><p>
-Once you installed a printer inside CUPS with one of the
-recommended methods (the lpadmin command, the web browser interface or one of
-the available GUI wizards), you can use <b>cupsaddsmb</b> to share the
-printer via Samba. <b>cupsaddsmb</b> prepares the driver files for
-comfortable client download and installation upon their first contact with
-this printer share.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2872566"></a><b>cupsaddsmb</b></h3></div></div><p>
-The <b>cupsaddsmb</b> command copies the needed files
-for convenient Windows client installations from the previously prepared CUPS
-data directory to your [print$] share. Additionally, the PPD
-associated with this printer is copied from <tt>/etc/cups/ppd/</tt> to
-[print$].
-</p><pre class="programlisting">
-<tt>root# </tt> <b>cupsaddsmb -U root infotec_IS2027</b>
-Password for root required to access localhost via
-SAMBA: <b><tt>[type in password 'secret']</tt></b>
-</pre><p>
-To share all printers and drivers, use the <i><tt>-a</tt></i>
-parameter instead of a printer name.
-</p><p>
-Probably you want to see what's going on. Use the
-<i><tt>-v</tt></i> parameter to get a more verbose output:
-</p><p>
-Probably you want to see what's going on. Use the
-<i><tt>-v</tt></i> parameter to get a more verbose output:
-</p><pre class="programlisting">
-Note: The following line shave been wrapped so that information is not lost.
-
-<tt>root# </tt> cupsaddsmb -v -U root infotec_IS2027
- Password for root required to access localhost via SAMBA:
- Running command: smbclient //localhost/print\$ -N -U'root%secret' -c 'mkdir W32X86;put
- /var/spool/cups/tmp/3cd1cc66376c0 W32X86/infotec_IS2027.PPD;put
- /usr/share/cups/drivers/
- ADOBEPS5.DLL W32X86/ADOBEPS5.DLL;put /usr/share/cups/drivers/ADOBEPSU.DLLr
- W32X86/ADOBEPSU.DLL;put /usr/share/cups/drivers/ADOBEPSU.HLP W32X86/ADOBEPSU.HLP'
- added interface ip=10.160.16.45 bcast=10.160.31.255 nmask=255.255.240.0
- added interface ip=192.168.182.1 bcast=192.168.182.255 nmask=255.255.255.0
- added interface ip=172.16.200.1 bcast=172.16.200.255 nmask=255.255.255.0
- Domain=[TUX-NET] OS=[Unix] Server=[Samba 2.2.3a.200204262025cvs]
- NT_STATUS_OBJECT_NAME_COLLISION making remote directory \W32X86
- putting file /var/spool/cups/tmp/3cd1cc66376c0 as
- \W32X86/infotec_IS2027.PPD (17394.6 kb/s) (average 17395.2 kb/s)
- putting file /usr/share/cups/drivers/ADOBEPS5.DLL as
- \W32X86/ADOBEPS5.DLL (10877.4 kb/s) (average 11343.0 kb/s)
- putting file /usr/share/cups/drivers/ADOBEPSU.DLL as
- \W32X86/ADOBEPSU.DLL (5095.2 kb/s) (average 9260.4 kb/s)
- putting file /usr/share/cups/drivers/ADOBEPSU.HLP as
- \W32X86/ADOBEPSU.HLP (8828.7 kb/s) (average 9247.1 kb/s)
-
- Running command: smbclient //localhost/print\$ -N -U'root%secret' -c 'mkdir WIN40;put
- /var/spool/cups/tmp/3cd1cc66376c0 WIN40/infotec_IS2027.PPD;put
- /usr/share/cups/drivers/ADFONTS.MFM WIN40/ADFONTS.MFM;put
- /usr/share/cups/drivers/ADOBEPS4.DRV WIN40/ADOBEPS4.DRV;put
- /usr/share/cups/drivers/ADOBEPS4.HLP WIN40/ADOBEPS4.HLP;put
- /usr/share/cups/drivers/DEFPRTR2.PPD WIN40/DEFPRTR2.PPD;put
- /usr/share/cups/drivers/ICONLIB.DLL WIN40/ICONLIB.DLL;put
- /usr/share/cups/drivers/PSMON.DLL WIN40/PSMON.DLL;'
- added interface ip=10.160.16.45 bcast=10.160.31.255 nmask=255.255.240.0
- added interface ip=192.168.182.1 bcast=192.168.182.255 nmask=255.255.255.0
- added interface ip=172.16.200.1 bcast=172.16.200.255 nmask=255.255.255.0
- Domain=[TUX-NET] OS=[Unix] Server=[Samba 2.2.3a.200204262025cvs]
- NT_STATUS_OBJECT_NAME_COLLISION making remote directory \WIN40
- putting file /var/spool/cups/tmp/3cd1cc66376c0 as
- \WIN40/infotec_IS2027.PPD (26091.5 kb/s) (average 26092.8 kb/s)
- putting file /usr/share/cups/drivers/ADFONTS.MFM as
- \WIN40/ADFONTS.MFM (11241.6 kb/s) (average 11812.9 kb/s)
- putting file /usr/share/cups/drivers/ADOBEPS4.DRV as
- \WIN40/ADOBEPS4.DRV (16640.6 kb/s) (average 14679.3 kb/s)
- putting file /usr/share/cups/drivers/ADOBEPS4.HLP as
- \WIN40/ADOBEPS4.HLP (11285.6 kb/s) (average 14281.5 kb/s)
- putting file /usr/share/cups/drivers/DEFPRTR2.PPD as
- \WIN40/DEFPRTR2.PPD (823.5 kb/s) (average 12944.0 kb/s)
- putting file /usr/share/cups/drivers/ICONLIB.DLL as
- \WIN40/ICONLIB.DLL (19226.2 kb/s) (average 13169.7 kb/s)
- putting file /usr/share/cups/drivers/PSMON.DLL as
- \WIN40/PSMON.DLL (18666.1 kb/s) (average 13266.7 kb/s)
-
- Running command: rpcclient localhost -N -U'root%secret'
- -c 'adddriver &quot;Windows NT x86&quot;
- &quot;infotec_IS2027:ADOBEPS5.DLL:infotec_IS2027.PPD:ADOBEPSU.DLL:
- ADOBEPSU.HLP:NULL:RAW:NULL&quot;'
- cmd = adddriver &quot;Windows NT x86&quot;
- &quot;infotec_IS2027:ADOBEPS5.DLL:infotec_IS2027.PPD:ADOBEPSU.DLL:
- ADOBEPSU.HLP:NULL:RAW:NULL&quot;
- Printer Driver infotec_IS2027 successfully installed.
-
- Running command: rpcclient localhost -N -U'root%secret'
- -c 'adddriver &quot;Windows 4.0&quot;
- &quot;infotec_IS2027:ADOBEPS4.DRV:infotec_IS2027.PPD:NULL:
- ADOBEPS4.HLP:PSMON.DLL:RAW: ADFONTS.MFM,DEFPRTR2.PPD,ICONLIB.DLL&quot;'
- cmd = adddriver &quot;Windows 4.0&quot; &quot;infotec_IS2027:ADOBEPS4.DRV:
- infotec_IS2027.PPD:NULL:ADOBEPS4.HLP:PSMON.DLL:RAW:
- ADFONTS.MFM,DEFPRTR2.PPD,ICONLIB.DLL&quot;
- Printer Driver infotec_IS2027 successfully installed.
-
- Running command: rpcclient localhost -N -U'root%secret'
- -c 'setdriver infotec_IS2027 infotec_IS2027'
- cmd = setdriver infotec_IS2027 infotec_IS2027
- Succesfully set infotec_IS2027 to driver infotec_IS2027.
-
- <tt>root# </tt>
-</pre><p>
-If you look closely, you'll discover your root password was transfered unencrypted over
-the wire, so beware! Also, if you look further her, you'll discover error messages like
-<tt>NT_STATUS_OBJECT_NAME_COLLISION</tt> in between. They occur, because
-the directories <tt>WIN40</tt> and <tt>W32X86</tt> already
-existed in the [print$] driver download share (from a previous driver
-installation). They are harmless here.
-</p><p>
-Now your printer is prepared for the clients to use. From
-a client, browse to the CUPS/Samba server, open the &quot;Printers&quot;
-share, right-click on this printer and select &quot;Install...&quot; or
-&quot;Connect...&quot; (depending on the Windows version you use). Now their
-should be a new printer in your client's local &quot;Printers&quot; folder,
-named (in my case) &quot;infotec_IS2027 on kdebitshop&quot;
-</p><p>
-<span class="emphasis"><em>NOTE: </em></span>
-<b>cupsaddsmb</b> will only reliably work i
-with CUPS version 1.1.15 or higher
-and Samba from 2.2.4. If it doesn't work, or if the automatic printer
-driver download to the clients doesn't succeed, you can still manually
-install the CUPS printer PPD on top of the Adobe PostScript driver on
-clients and then point the client's printer queue to the Samba printer
-share for connection, should you desire to use the CUPS networked
-PostScript RIP functions.
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2872915"></a>The CUPS Filter Chains</h2></div></div><p>
-The following diagrams reveal how CUPS handles print jobs.
-</p><pre class="programlisting">
-#########################################################################
-#
-# CUPS in and of itself has this (general) filter chain (CAPITAL
-# letters are FILE-FORMATS or MIME types, other are filters (this is
-# true for pre-1.1.15 of pre-4.3 versions of CUPS and ESP PrintPro):
-#
-# <i><tt>SOMETHNG</tt></i>-FILEFORMAT
-# |
-# |
-# V
-# <i><tt>something</tt></i>tops
-# |
-# |
-# V
-# APPLICATION/POSTSCRIPT
-# |
-# |
-# V
-# pstops
-# |
-# |
-# V
-# APPLICATION/VND.CUPS-POSTSCRIPT
-# |
-# |
-# V
-# pstoraster # as shipped with CUPS, independent from any Ghostscipt
-# | # installation on the system
-# | (= &quot;postscipt interpreter&quot;)
-# |
-# V
-# APPLICATION/VND.CUPS-RASTER
-# |
-# |
-# V
-# rasterto<i><tt>something</tt></i> (f.e. Gimp-Print filters may be plugged in here)
-# | (= &quot;raster driver&quot;)
-# |
-# V
-# SOMETHING-DEVICE-SPECIFIC
-# |
-# |
-# V
-# backend
-#
-#
-# ESP PrintPro has some enhanced &quot;rasterto<i><tt>something</tt></i>&quot; filters as compared to
-# CUPS, and also a somewhat improved &quot;pstoraster&quot; filter.
-#
-# NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to
-# CUPS and ESP PrintPro plug-in where rasterto<i><tt>something</tt></i> is noted.
-#
-#########################################################################
-</pre><pre class="programlisting">
-#########################################################################
-#
-# This is how &quot;cupsomatic&quot; comes into play:
-# =========================================
-#
-# <i><tt>SOMETHNG</tt></i>-FILEFORMAT
-# |
-# |
-# V
-# <i><tt>something</tt></i>tops
-# |
-# |
-# V
-# APPLICATION/POSTSCRIPT
-# |
-# |
-# V
-# pstops
-# |
-# |
-# V
-# APPLICATION/VND.CUPS-POSTSCRIPT ----------------+
-# | |
-# | V
-# V cupsomatic
-# pstoraster (constructs complicated
-# | (= &quot;postscipt interpreter&quot;) Ghostscript commandline
-# | to let the file be
-# V processed by a
-# APPLICATION/VND.CUPS-RASTER &quot;-sDEVICE=<i><tt>s.th.</tt></i>&quot;
-# | call...)
-# | |
-# V |
-# rasterto<i><tt>something</tt></i> V
-# | (= &quot;raster driver&quot;) +-------------------------+
-# | | Ghostscript at work.... |
-# V | |
-# SOMETHING-DEVICE-SPECIFIC *-------------------------+
-# | |
-# | |
-# V |
-# backend &gt;------------------------------------+
-# |
-# |
-# V
-# THE PRINTER
-#
-#
-# Note, that cupsomatic &quot;kidnaps&quot; the printfile after the
-# &quot;APPLICATION/VND.CUPS-POSTSCRPT&quot; stage and deviates it through
-# the CUPS-external, systemwide Ghostscript installation, bypassing the
-# &quot;pstoraster&quot; filter (therefor also bypassing the CUPS-raster-drivers
-# &quot;rasterto<i><tt>something</tt></i>&quot;, and hands the rasterized file directly to the CUPS
-# backend...
-#
-# cupsomatic is not made by the CUPS developers. It is an independent
-# contribution to printing development, made by people from
-# Linuxprinting.org. (see also http://www.cups.org/cups-help.html)
-#
-# NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to
-# CUPS and ESP PrintPro plug-in where rasterto<i><tt>something</tt></i> is noted.
-#
-#########################################################################
-</pre><pre class="programlisting">
-#########################################################################
-#
-# And this is how it works for ESP PrintPro from 4.3:
-# ===================================================
-#
-# <i><tt>SOMETHNG</tt></i>-FILEFORMAT
-# |
-# |
-# V
-# <i><tt>something</tt></i>tops
-# |
-# |
-# V
-# APPLICATION/POSTSCRIPT
-# |
-# |
-# V
-# pstops
-# |
-# |
-# V
-# APPLICATION/VND.CUPS-POSTSCRIPT
-# |
-# |
-# V
-# gsrip
-# | (= &quot;postscipt interpreter&quot;)
-# |
-# V
-# APPLICATION/VND.CUPS-RASTER
-# |
-# |
-# V
-# rasterto<i><tt>something</tt></i> (f.e. Gimp-Print filters may be plugged in here)
-# | (= &quot;raster driver&quot;)
-# |
-# V
-# SOMETHING-DEVICE-SPECIFIC
-# |
-# |
-# V
-# backend
-#
-# NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to
-# CUPS and ESP PrintPro plug-in where rasterto<i><tt>something</tt></i> is noted.
-#
-#########################################################################
-</pre><pre class="programlisting">
-#########################################################################
-#
-# This is how &quot;cupsomatic&quot; would come into play with ESP PrintPro:
-# ================================================================
-#
-#
-# <i><tt>SOMETHNG</tt></i>-FILEFORMAT
-# |
-# |
-# V
-# <i><tt>something</tt></i>tops
-# |
-# |
-# V
-# APPLICATION/POSTSCRIPT
-# |
-# |
-# V
-# pstops
-# |
-# |
-# V
-# APPLICATION/VND.CUPS-POSTSCRIPT ----------------+
-# | |
-# | V
-# V cupsomatic
-# gsrip (constructs complicated
-# | (= &quot;postscipt interpreter&quot;) Ghostscript commandline
-# | to let the file be
-# V processed by a
-# APPLICATION/VND.CUPS-RASTER &quot;-sDEVICE=<i><tt>s.th.</tt></i>&quot;
-# | call...)
-# | |
-# V |
-# rasterto<i><tt>something</tt></i> V
-# | (= &quot;raster driver&quot;) +-------------------------+
-# | | Ghostscript at work.... |
-# V | |
-# SOMETHING-DEVICE-SPECIFIC *-------------------------+
-# | |
-# | |
-# V |
-# backend &gt;------------------------------------+
-# |
-# |
-# V
-# THE PRINTER
-#
-# NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to
-# CUPS and ESP PrintPro plug-in where rasterto<i><tt>something</tt></i> is noted.
-#
-#########################################################################
-</pre><pre class="programlisting">
-#########################################################################
-#
-# And this is how it works for CUPS from 1.1.15:
-# ==============================================
-#
-# <i><tt>SOMETHNG</tt></i>-FILEFORMAT
-# |
-# |
-# V
-# <i><tt>something</tt></i>tops
-# |
-# |
-# V
-# APPLICATION/POSTSCRIPT
-# |
-# |
-# V
-# pstops
-# |
-# |
-# V
-# APPLICATION/VND.CUPS-POSTSCRIPT-----+
-# |
-# +------------------v------------------------------+
-# | Ghostscript |
-# | at work... |
-# | (with |
-# | &quot;-sDEVICE=cups&quot;) |
-# | |
-# | (= &quot;postscipt interpreter&quot;) |
-# | |
-# +------------------v------------------------------+
-# |
-# |
-# APPLICATION/VND.CUPS-RASTER &gt;-------+
-# |
-# |
-# V
-# rasterto<i><tt>something</tt></i>
-# | (= &quot;raster driver&quot;)
-# |
-# V
-# SOMETHING-DEVICE-SPECIFIC
-# |
-# |
-# V
-# backend
-#
-#
-# NOTE: since version 1.1.15 CUPS &quot;outsourced&quot; the pstoraster process to
-# Ghostscript. GNU Ghostscript needs to be patched to handle the
-# CUPS requirement; ESP Ghostscript has this builtin. In any case,
-# &quot;gs -h&quot; needs to show up a &quot;cups&quot; device. pstoraster is now a
-# calling an appropriate &quot;gs -sDEVICE=cups...&quot; commandline to do
-# the job. It will output &quot;application/vnd.cup-raster&quot;, which will
-# be finally processed by a CUPS raster driver &quot;rasterto<i><tt>something</tt></i>&quot;
-# Note the difference to &quot;cupsomatic&quot;, which will *not* output
-# CUPS-raster, but a final version of the printfile, ready to be
-# sent to the printer. cupsomatic also doesn't use the &quot;cups&quot;
-# devicemode in Ghostscript, but one of the classical devicemodes....
-#
-# NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to
-# CUPS and ESP PrintPro plug-in where rasterto<i><tt>something</tt></i> is noted.
-#
-#########################################################################
-</pre><pre class="programlisting">
-#########################################################################
-#
-# And this is how it works for CUPS from 1.1.15, with cupsomatic included:
-# ========================================================================
-#
-# <i><tt>SOMETHNG</tt></i>-FILEFORMAT
-# |
-# |
-# V
-# <i><tt>something</tt></i>tops
-# |
-# |
-# V
-# APPLICATION/POSTSCRIPT
-# |
-# |
-# V
-# pstops
-# |
-# |
-# V
-# APPLICATION/VND.CUPS-POSTSCRIPT-----+
-# |
-# +------------------v------------------------------+
-# | Ghostscript . Ghostscript at work.... |
-# | at work... . (with &quot;-sDEVICE= |
-# | (with . <i><tt>s.th.</tt></i>&quot; |
-# | &quot;-sDEVICE=cups&quot;) . |
-# | . |
-# | (CUPS standard) . (cupsomatic) |
-# | . |
-# | (= &quot;postscript interpreter&quot;) |
-# | . |
-# +------------------v--------------v---------------+
-# | |
-# | |
-# APPLICATION/VND.CUPS-RASTER &gt;-------+ |
-# | |
-# | |
-# V |
-# rasterto<i><tt>something</tt></i> |
-# | (= &quot;raster driver&quot;) |
-# | |
-# V |
-# SOMETHING-DEVICE-SPECIFIC &gt;------------------------+
-# |
-# |
-# V
-# backend
-#
-#
-# NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to
-# CUPS and ESP PrintPro plug-in where rasterto<i><tt>something</tt></i> is noted.
-#
-##########################################################################
-</pre></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2873302"></a>CUPS Print Drivers and Devices</h2></div></div><p>
-CUPS ships with good support for HP LaserJet type printers. You can install
-the driver as follows:
-
-</p><div class="itemizedlist"><ul type="disc"><li><p>
- lpadmin -p laserjet4plus -v parallel:/dev/lp0 -E -m laserjet.ppd
- </p></li></ul></div><p>
-
-(The &quot;-m&quot; switch will retrieve the &quot;laserjet.ppd&quot; from the standard repository
-for not-yet-installed-PPDs, which CUPS typically stores in
-<tt>/usr/share/cups/model</tt>. Alternatively, you may use
-&quot;-P /absolute/filesystem/path/to/where/there/is/PPD/your.ppd&quot;).
-</p><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2873339"></a>Further printing steps</h3></div></div><p>
-Always also consult the database on linuxprinting.org for all recommendations
-about which driver is best used for each printer:
-</p><p><a href="http://www.linuxprinting.org/printer_list.cgi" target="_top">http://www.linuxprinting.org/printer_list.cgi</a></p><p>
-There select your model and click on &quot;Show&quot;. You'll arrive at a page listing
-all drivers working with your model. There will always be *one*
-<span class="emphasis"><em>recommended</em></span> one. Try this one first. In your case
-(&quot;HP LaserJet 4 Plus&quot;), you'll arrive here:
-</p><p><a href="http://www.linuxprinting.org/show_printer.cgi?recnum=75104" target="_top">http://www.linuxprinting.org/show_printer.cgi?recnum=75104</a></p><p>
-The recommended driver is &quot;ljet4&quot;. It has a link to the page for the ljet4
-driver too:
-</p><p><a href="http://www.linuxprinting.org/show_driver.cgi?driver=ljet4" target="_top">http://www.linuxprinting.org/show_driver.cgi?driver=ljet4</a></p><p>
-On the driver's page, you'll find important and detailed info about how to use
-that driver within the various available spoolers. You can generate a PPD for
-CUPS. The PPD contains all the info about how to use your model and the driver;
-this is, once installed, working transparently for the user -- you'll only
-need to choose resolution, paper size etc. from the web-based menu or from
-the print dialog GUI or from the commandline...
-</p><p>
-On the driver's page, choose to use the &quot;PPD-O-Matic&quot; online PPD generator
-program. Select your model and click &quot;Generate PPD file&quot;. When you safe the
-appearing ASCII text file, don't use &quot;cut'n'past&quot; (as it could possiblly corrupt
-line endings and tabs), but use &quot;Save as...&quot; in your browser's menu. Save it
-at &quot;/some/path/on/your/filesystem/somewhere/my-name-for-my-printer.ppd&quot;
-</p><p>
-Then install the printer:
-</p><pre class="programlisting">
- &quot;lpadmin -p laserjet4plus -v parallel:/dev/lp0 -E \
- -P /some/path/on/your/filesystem/somewhere/my-name-for-my-printer.ppd&quot;
-</pre><p>
-Note, that for all the &quot;Foomatic-PPDs&quot; from Linuxprinting.org, you also need
-a special &quot;CUPS filter&quot; named &quot;cupsomatic&quot;. Get the latest version of
-&quot;cupsomatic&quot; from:
-</p><p><a href="http://www.linuxprinting.org/cupsomatic" target="_top">http://www.linuxprinting.org/cupsomatic</a></p><p>
-This needs to be copied to <tt>/usr/lib/cups/filter/cupsomatic</tt>
-and be made world executable. This filter is needed to read and act upon the
-specially encoded Foomatic comments, embedded in the printfile, which in turn
-are used to construct (transparently for you, the user) the complicated
-ghostscript command line needed for your printer/driver combo.
-</p><p>
-You can have a look at all the options for the Ghostscript commandline supported
-by your printer and the ljet4 driver by going to the section &quot;Execution details&quot;,
-selecting your model (Laserjet 4 Plus) and clicking on &quot;Show execution details&quot;.
-This will bring up this web page:
-</p><p><a href="http://www.linuxprinting.org/execution.cgi?driver=ljet4&amp;printer=75104&amp;.submit=Show%2Bexecution%2Bdetails" target="_top">http://www.linuxprinting.org/execution.cgi?driver=ljet4&amp;printer=75104&amp;.submit=Show+execution+details</a></p><p>
-The ingenious thing is that the database is kept current. If there
-is a bug fix and an improvement somewhere in the database, you will
-always get the most current and stable and feature-rich driver by following
-the steps described above.
-</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-Till Kamppeter from MandrakeSoft is doing an excellent job here that too few
-people are aware of. (So if you use it often, please send him a note showing
-your appreciation).</p></div><p>
-The latest and greatest improvement now is support for &quot;custom page sizes&quot;
-for all those printers which support it.
-</p><p>
-&quot;cupsomatic&quot; is documented here:
-</p><p><a href="http://www.linuxprinting.org/cups-doc.html" target="_top">http://www.linuxprinting.org/cups-doc.html</a></p><p>
-More printing tutorial info may be found here:
-</p><p><a href="http://www.linuxprinting.org/kpfeifle/LinuxKongress2002/Tutorial/" target="_top">http://www.linuxprinting.org/kpfeifle/LinuxKongress2002/Tutorial/</a></p><p>
-Note, that *all* the Foomatic drivers listed on Linuxprinting.org (now
-approaching the &quot;all-time high&quot; number of 1.000 for the supported models)
-are using a special filtering chain involving Ghostscript, as described
-in this document.
-</p><p>
-Summary - You need:
-</p><p>
-</p><table class="simplelist" border="0" summary="Simple list"><tr><td>A &quot;foomatic+<i><tt>something</tt></i>&quot; PPD is not enough to print with CUPS (but it is *one* important component)</td></tr><tr><td>The &quot;cupsomatic&quot; filter script (Perl) in <tt>/usr/lib/cups/filters/</tt></td></tr><tr><td>Perl to make cupsomatic run</td></tr><tr><td>Ghostscript (because it is called and controlled by the PPD/cupsomatic combo in a way to fit your printermodel/driver combo.</td></tr><tr><td>Ghostscript *must*, depending on the driver/model, contain support for a certain &quot;device&quot; (as shown by &quot;gs -h&quot;)</td></tr></table><p>
-</p><p>
-In the case of the &quot;hpijs&quot; driver, you need a Ghostscript version, which
-has &quot;ijs&quot; amongst its supported devices in &quot;gs -h&quot;. In the case of
-&quot;hpijs+foomatic&quot;, a valid ghostscript commandline would be reading like this:
-</p><pre class="programlisting">
- gs -q -dBATCH -dPARANOIDSAFER -dQUIET -dNOPAUSE -sDEVICE=ijs \
- -sIjsServer=hpijs<i><tt>PageSize</tt></i> -dDuplex=<i><tt>Duplex</tt></i> <i><tt>Model</tt></i> \
- -r<i><tt>Resolution</tt></i>,PS:MediaPosition=<i><tt>InputSlot</tt></i> -dIjsUseOutputFD \
- -sOutputFile=- -
-</pre><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-Note, that with CUPS and the &quot;hpijs+foomatic&quot; PPD (plus Perl and cupsomatic)
-you don't need to remember this. You can choose the available print options
-thru a GUI print command (like &quot;glp&quot; from ESP's commercially supported
-PrintPro software, or KDE's &quot;kprinter&quot;, or GNOME's &quot;gtklp&quot; or the independent
-&quot;xpp&quot;) or the CUPS web interface via human-readable drop-down selection
-menus.
-</p></div><p>
-If you use &quot;ESP Ghostscript&quot; (also under the GPL, provided by Easy Software
-Products, the makers of CUPS, downloadable from
-<a href="http://www.cups.org/software.html" target="_top">http://www.cups.org/software.html</a>,
-co-maintained by the developers of linuxprinting.org), you are guaranteed to
-have in use the most uptodate, bug-fixed, enhanced and stable version of a Free
-Ghostscript. It contains support for ~300 devices, whereas plain vanilla
-GNU Ghostscript 7.05 only has ~200.
-</p><p>
-If you print only one CUPS test page, from the web interface and when you try to
-print a windows test page, it acts like the job was never sent:
-
-</p><table class="simplelist" border="0" summary="Simple list"><tr><td>Can you print &quot;standard&quot; jobs from the CUPS machine?</td></tr><tr><td>Are the jobs from Windows visible in the Web interface on CUPS (http://localhost:631/)?</td></tr><tr><td><span class="emphasis"><em>Most important:</em></span> What kind of printer driver are you using on the Windows clients?</td></tr></table><p>
-
-You can try to get a more detailed debugging info by setting &quot;LogLevel debug&quot; in
-<tt>/etc/cups/cupsd.conf</tt>, re-start cupsd and investigate <tt>/var/log/cups/error_log</tt>
-for the whereabouts of your Windows-originating printjobs:
-</p><table class="simplelist" border="0" summary="Simple list"><tr><td>what does the &quot;auto-typing&quot; line say? which is the &quot;MIME type&quot; CUPS thinks is arriving from the Windows clients?</td></tr><tr><td>are there &quot;filter&quot; available for this MIME type?</td></tr><tr><td>are there &quot;filter rules&quot; defined in &quot;/etc/cups/mime.convs&quot; for this MIME type?</td></tr></table></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2873758"></a>Limiting the number of pages users can print</h2></div></div><p>
-The feature you want is dependent on the real print subsystem you're using.
-Samba's part is always to receive the job files from the clients (filtered
-*or* unfiltered) and hand it over to this printing subsystem.
-</p><p>
-Of course one could &quot;hack&quot; things with one's own scripts.
-</p><p>
-But there is CUPS (Common Unix Printing System). CUPS supports &quot;quotas&quot;.
-Quotas can be based on sizes of jobs or on the number of pages or both,
-and are spanning any time period you want.
-</p><p>
-This is an example command how root would set a print quota in CUPS,
-assuming an existing printer named &quot;quotaprinter&quot;:
-</p><pre class="programlisting">
- lpadmin -p quotaprinter -o job-quota-period=604800 -o job-k-limit=1024 \
- -o job-page-limit=100
-</pre><p>
-This would limit every single user to print 100 pages or 1024 KB of
-data (whichever comes first) within the last 604.800 seconds ( = 1 week).
-</p><p>
-For CUPS to count correctly, the printfile needs to pass the CUPS &quot;pstops&quot; filter,
-otherwise it uses a &quot;dummy&quot; count of &quot;1&quot;. Some printfiles don't pass it
-(eg: image files) but then those are mostly 1 page jobs anyway. This also means,
-proprietary drivers for the target printer running on the client computers and
-CUPS/Samba then spooling these files as &quot;raw&quot; (i.e. leaving them untouched, not
-filtering them), will be counted as &quot;1-pagers&quot; too!
-</p><p>
-You need to send PostScript from the clients (i.e. run a PostScript driver there)
-for having the chance to get accounting done. If the printer is a non-PostScript model,
-you need to let CUPS do the job to convert the file to a print-ready format for the
-target printer. This will be working for currently ~1.000 different printer models, see
-</p><pre class="programlisting">
- http://www.linuxprinting.org/printer_list.cgi
-</pre><p>
-Before CUPS-1.1.16 your only option was to use the Adobe PostScript
-Driver on the Windows clients. The output of this driver was not always
-passed thru the &quot;pstops&quot; filter on the CUPS/Samba side, and therefor was
-not counted correctly (the reason is that it often --- depending on the
-&quot;PPD&quot; being used --- did write a &quot;PJL&quot;-header in front of the real
-PostScript which made CUPS to skip the pstops and go directy to
-the &quot;pstoraster&quot; stage).
-</p><p>
-From CUPS-1.1.16 onward you can use the &quot;CUPS PostScript Driver
-for Windows NT/2K/XP clients&quot; (it is tagged in the download area of
-http://www.cups.org/ as the &quot;cups-samba-1.1.16.tar.gz&quot; package).
-It is *not* working for Win9x/ME clients. But it:
-</p><table class="simplelist" border="0" summary="Simple list"><tr><td>it guarantees to not write an PJL-header</td></tr><tr><td>it guarantees to still read and support all PJL-options named in the driver PPD with its own means</td></tr><tr><td>it guarantees the file going thru the &quot;pstops&quot; filter on the CUPS/Samba server</td></tr><tr><td>it guarantees to page-count correctly the printfile</td></tr></table><p>
-You can read more about the setup of this combination in the
-manpage for &quot;cupsaddsmb&quot; (only present with CUPS installed, only
-current with CUPS 1.1.16).
-</p><p>
-These are the items CUPS logs in the &quot;page_log&quot; for every single *page* of a job:
-</p><table class="simplelist" border="0" summary="Simple list"><tr><td>Printer name</td></tr><tr><td>User name</td></tr><tr><td>Job ID</td></tr><tr><td>Time of printing</td></tr><tr><td>the page number</td></tr><tr><td>the number of copies</td></tr><tr><td>a billing info string (optional)</td></tr></table><p>
-</p><p>
-Here is an extract of my CUPS server's page_log file to illustrate
-the format and included items:
-</p><p><tt>
- infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 1 2 #marketing
- infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 2 2 #marketing
- infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 3 2 #marketing
- infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 4 2 #marketing
- infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 5 2 #marketing
- infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 6 2 #marketing
-</tt></p><p>
-This was Job ID &quot;40&quot;, printed on &quot;infotec_IS2027&quot; by user &quot;kurt&quot;, a 6-page job
-printed in 2 copies and billed to &quot;#marketing&quot;...
-</p><p>
-What flaws or shortcomings are there?
-</p><table class="simplelist" border="0" summary="Simple list"><tr><td>the ones named above</td></tr><tr><td>
- CUPS really counts the job pages being *processsed in software*
- (going thru the &quot;RIP&quot;) rather than the physical sheets successfully
- leaving the printing device -- if there is a jam while printing
- the 5th sheet out of 1000 and the job is aborted by the printer,
- the &quot;page count&quot; will still show the figure of 1000 for that job
- </td></tr><tr><td>
- all quotas are the same for all users (no flexibility to give the
- boss a higher quota than the clerk) no support for groups
- </td></tr><tr><td>
- no means to read out the current balance or &quot;used-up&quot; number of current quota
- </td></tr><tr><td>
- a user having used up 99 sheets of 100 quota will still be able to send and print a 1.000 sheet job
- </td></tr><tr><td>
- a user being denied a job because of a filled-up quota doesn't get a meaningful
- error message from CUPS other than &quot;client-error-not-possible&quot;.
- </td></tr></table><p>
-But this is the best system out there currently. And there are
-huge improvements under development:
-</p><table class="simplelist" border="0" summary="Simple list"><tr><td>page counting will go into the &quot;backends&quot; (these talk
- directly to the printer and will increase the count in sync with the
- actual printing process -- a jam at the 5th sheet will lead to a stop in the counting)</td></tr><tr><td>quotas will be handled more flexibly</td></tr><tr><td>probably there will be support for users to inquire their &quot;accounts&quot; in advance</td></tr><tr><td>probably there will be support for some other tools around this topic</td></tr></table><p>
-Other than the current stage of the CUPS development, I don't
-know any other ready-to-use tool which you could consider.
-</p><p>
-You can download the driver files from
-<a href="http://www.cups.org/software.html" target="_top">http://www.cups.org/software.html</a>.
-It is a separate package from the CUPS base software files, tagged as &quot;CUPS 1.1.16
-Windows NT/2k/XP Printer Driver for SAMBA (tar.gz, 192k)&quot;. The filename to
-download is &quot;cups-samba-1.1.16.tar.gz&quot;. Upon untar-/unzip-ping it will reveal
-the files:
-</p><p>
-<tt>
- cups-samba.install
- cups-samba.license
- cups-samba.readme
- cups-samba.remove
- cups-samba.ss
-</tt>
-</p><p>
-These have been packaged with the ESP meta packager software &quot;EPM&quot;. The
-*.install and *.remove files are simple shell script, which untars the
-*.ss (which is nothing else than a tar-archive) and puts its contents
-into <tt>/usr/share/cups/drivers/</tt>. Its contents are 3 files:
-</p><p>
-<tt>
- cupsdrvr.dll
- cupsui.dll
- cups.hlp
-</tt>
-</p><div class="caution" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Caution</h3><p>
-Due to a bug one CUPS release puts the <tt>cups.hlp</tt>
-into <tt>/usr/share/drivers/</tt> instead of
-<tt>/usr/share/cups/drivers/</tt>. To work around this, copy/move
-the file after running the &quot;./cups-samba.install&quot; script manually to the right place:
-</p><p>
-<b><tt> cp /usr/share/drivers/cups.hlp /usr/share/cups/drivers/
-</tt></b>
- </p></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-This new CUPS PostScript driver is currently binary-only, but free
-no source code is provided (yet). The reason is this: it has
-been developed with the help of the Microsoft Driver Developer Kit (DDK)
-and compiled with Microsoft Visual Studio 6. It is not clear to the driver
-developers if they are allowed to distribute the whole of the source code
-as Free Software. However, they will likely release the &quot;diff&quot; in source
-code under the GPL, so anybody with a license of Visual Studio and a DDK
-will be able to compile for him/herself.
-</p><p>
-Once you have run the install script (and possibly manually moved the
-&quot;cups.hlp&quot; file to &quot;/usr/share/cups/drivers/&quot;), the driver is ready to be
-put into Samba's [print$] share (which often maps to &quot;/etc/samba/drivers/&quot;
-and contains a subdir tree with WIN40 and W32X86 branches), by running
-&quot;cupsaddsmb&quot; (see also &quot;man cupsaddsmb&quot; for CUPS 1.1.16). [Don't forget to
-put root into the smbpasswd file by running &quot;smbpasswd&quot; should you run
-this whole procedure for the first time.] Once the driver files are in the
-[print$] share, they are ready to be downloaded and installed by the
-Win NT/2k/XP clients.
-</p></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
- Win 9x/ME clients won't work with this driver. For these you'd
- still need to use the ADOBE*.* drivers as previously.
- </p></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
- It is not harming if you've still the ADOBE*.* driver files from
- previous installations in the &quot;/usr/share/cups/drivers/&quot; directory.
- The new cupsaddsmb (from 1.1.16) will automatically use the
- &quot;newest&quot; installed driver (which here then is the CUPS drivers).
- </p></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
- Should your Win clients have had the old ADOBE*.* files and the
- Adobe PostScript drivers installed, the download and installation
- of the new CUPS PostScript driver for Windows NT/2k/XP will fail
- at first.
- </p><p>
- It is not enough to &quot;delete&quot; the printer (as the driver files
- will still be kept by the clients and re-used if you try to
- re-install the printer). To really get rid of the Adobe driver
- files on the clients, open the &quot;Printers&quot; folder (possibly via
- &quot;Start --&gt; Settings --&gt; Control Panel --&gt; Printers&quot;), right-click
- onto the folder background and select &quot;Server Properties&quot;. A
- new dialog opens; select the &quot;Drivers&quot; tab; on the list select
- the driver you want to delete and click on the &quot;Delete&quot; button.
- (This will only work if there is no single printer left which
- uses that particular driver -- you need to &quot;delete&quot; all printers
- using this driver in the &quot;Printers&quot; folder first.)
- </p></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
- Once you have successfully downloaded the CUPS PostScript driver
- to a client, you can easily switch all printers to this one
- by proceeding as described elsewhere in the &quot;Samba HOWTO
- Collection&quot; to change a driver for an existing printer.
- </p></div><p>
-What are the benefits with the &quot;CUPS PostScript driver for Windows NT/2k/XP&quot;
-as compared to the Adobe drivers?
-</p><p>
-</p><table class="simplelist" border="0" summary="Simple list"><tr><td><p>
- no hassle with the Adobe EULA
- </p></td></tr><tr><td><p>
- no hassle with the question &quot;where do I get the ADOBE*.* driver files from?&quot;
- </p></td></tr><tr><td><p>
- the Adobe drivers (depending on the printer PPD associated with them)
- often put a PJL header in front of the core PostScript part of the print
- file (thus the file starts with &quot;<i><tt>1B</tt></i>%-12345X&quot;
- or &quot;<i><tt>escape</tt></i>%-12345X&quot;
- instead of &quot;%!PS&quot;). This leads to the CUPS daemon autotyping the
- arriving file as a print-ready file, not requiring a pass thru the
- &quot;pstops&quot; filter (to speak more technical, it is not regarded as the
- generic MIME type &quot;application/postscript&quot;, but as the more special
- MIME type &quot;application/cups.vnd-postscript&quot;), which therefore also
- leads to the page accounting in &quot;/var/log/cups/page_log&quot; not receiving
- the exact mumber of pages; instead the dummy page number of &quot;1&quot; is
- logged in a standard setup)
- </p></td></tr><tr><td><p>
- the Adobe driver has more options to &quot;mis-configure&quot; the PostScript
- generated by it (like setting it inadvertedly to &quot;Optimize for Speed&quot;,
- instead of &quot;Optimize for Portability&quot;, which could lead to CUPS being
- unable to process it)
- </p></td></tr><tr><td><p>
- the CUPS PostScript driver output sent by Windows clients to the CUPS
- server will be guaranteed to be auto-typed as generic MIME type
- &quot;application/postscript&quot;, thusly passing thru the CUPS &quot;pstops&quot; filter
- and logging the correct number of pages in the page_log for accounting
- and quota purposes
- </p></td></tr><tr><td><p>
- the CUPS PostScript driver supports the sending of additional print
- options by the Win NT/2k/XP clients, such as naming the CUPS standard
- banner pages (or the custom ones, should they be installed at the time
- of driver download), using the CUPS &quot;page-label&quot; option, setting a
- job-priority and setting the scheduled time of printing (with the option
- to support additional useful IPP job attributes in the future).
- </p></td></tr><tr><td><p>
- the CUPS PostScript driver supports the inclusion of the new
- &quot;*cupsJobTicket&quot; comments at the beginnig of the PostScript file (which
- could be used in the future for all sort of beneficial extensions on
- the CUPS side, but which will not disturb any other application as those
- will regard it as a comment and simply ignore it).
- </p></td></tr><tr><td><p>
- the CUPS PostScript driver will be the heart of the fully fledged CUPS
- IPP client for Windows NT/2k/XP to be released soon (probably alongside
- the first Beta release for CUPS 1.2).
- </p></td></tr></table><p>
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2874367"></a>Advanced Postscript Printing from MS Windows</h2></div></div><p>
-Let the Windows Clients use a PostScript driver to deliver poistscript to
-the samba print server (just like any Linux or Unix Client would also use
-PostScript to send to the server)
-</p><p>
-Make the Unix printing subsystem to which Samba sends the job convert the
-incoming PostScript files to the native print format of the target printers
-(would be PCL if you have an HP printer)
-</p><p>
-Now if you are afraid that this would just mean using a *Generic* PostScript
-driver for the clients that has no Simplex/Duplex selection, and no paper tray
-choice, but you need them to be able to set up print jobs, with all the bells
-and whistles of your printers:-
-</p><table class="simplelist" border="0" summary="Simple list"><tr><td>Not possible with traditional spooling systems</td></tr><tr><td>
- But perfectly supported by CUPS (which uses &quot;PPD&quot; files to
- describe how to control the print options for PostScript and
- non-PostScript devices alike...
- </td></tr></table><p>
-CUPS PPDs are working perfectly on Windows clients who use Adobe PostScript
-drivers (or the new CUPS PostScript driver for Windows NT/2K/XP). Clients can use
-them to setup the job to their liking and CUPS will use the received job options
-to make the (PCL-, ESC/P- or PostScript-) printer behave as required.
-</p><p>
-If you want to have the additional benefit of page count logging and accounting
-then the CUPS PostScript driver is the best choice (better than the Adobe one).
-</p><p>
-If you want to make the drivers downloadable for the clients then &quot;cupsaddsmb&quot; is
-your friend. It will setup the [print$] share on the Samba host to be ready to serve
-the clients for a &quot;point and print&quot; driver installation.
-</p><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p>What strings are attached?</p></div><p>
-There are some. But, given the sheer CPU power you can buy nowadays,
-these can be overcome easily. The strings:
-</p><p>
-Well, if the CUPS/Samba side will have to print to many printers serving many users,
-you probably will need to set up a second server (which can do automatic load balancing
-with the first one, plus a degree of fail-over mechanism). Converting the incoming
-PostScript jobs, &quot;interpreting&quot; them for non-PostScript printers, amounts to the work
-of a &quot;RIP&quot; (Raster Image Processor) done in software. This requires more CPU and RAM
-than for the mere &quot;raw spooling&quot; task your current setup is solving. It all depends
-on the avarage and peak printing load the server should be able to handle.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2874473"></a>Auto-Deletion of CUPS spool files</h2></div></div><p>
-Samba print files pass thru two &quot;spool&quot; directories. One the incoming directory
-managed by Samba, (set eg: in the <b>path = /var/spool/samba</b> directive in the [printers]
-section of <tt>smb.conf</tt>). Second is the spool directory of your UNIX print subsystem.
-For CUPS it is normally &quot;/var/spool/cups/&quot;, as set by the cupsd.conf directive
-&quot;RequestRoot /var/spool/cups&quot;.
-</p><p>
-I am not sure, which one of your directories keeps the files. From what you say,
-it is most likely the Samba part.
-</p><p>
-For the CUPS part, you may want to consult:
-</p><table class="simplelist" border="0" summary="Simple list"><tr><td>http://localhost:631/sam.html#PreserveJobFiles</td></tr><tr><td>http://localhost:631/sam.html#PreserveJobHistory</td></tr><tr><td>http://localhost:631/sam.html#MaxJobs</td></tr></table><p>
-There are the settings described for your CUPS daemon, which could lead to completed
-job files not being deleted.
-</p><p>
-&quot;PreserveJobHistory Yes&quot; -- keeps some details of jobs in
-cupsd's mind (well it keeps the &quot;c12345&quot;, &quot;c12346&quot; etc. files
-in the CUPS spool directory, which do a similar job as the
-old-fashioned BSD-LPD control files). This is set to &quot;Yes&quot;
-as a default.
-</p><p>
-&quot;PreserveJobFiles Yes&quot; -- keeps the job files themselves in
-cupsd's mind (well it keeps the &quot;d12345&quot;, &quot;d12346&quot; etc. files
-in the CUPS spool directory...). This is set to &quot;No&quot; as the
-CUPS default.
-</p><p>
-&quot;MaxJobs 500&quot; -- this directive controls the maximum number
-of jobs that are kept in memory. Once the number of jobs
-reaches the limit, the oldest completed job is automatically
-purged from the system to make room for the new one. If all
-of the known jobs are still pending or active then the new
-job will be rejected. Setting the maximum to 0 disables this
-functionality. The default setting is 0.
-</p><p>
-(There are also additional settings for &quot;MaxJobsPerUser&quot; and
-&quot;MaxJobsPerPrinter&quot;...)
-</p><p>
-For everything to work as announced, you need to have three things:
-</p><table class="simplelist" border="0" summary="Simple list"><tr><td>
- a Samba-smbd which is compiled against &quot;libcups&quot; (Check on Linux by running <b><tt>ldd `which smbd`</tt></b>)
- </td></tr><tr><td>
- a Samba-<tt>smb.conf</tt> setting of <b>printing = cups</b>
- </td></tr><tr><td>
- another Samba-<tt>smb.conf</tt> setting of <b>printcap = cups</b>
- </td></tr></table><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-Note, that in this case all other manually set printing-related
-commands (like &quot;print command&quot;, &quot;lpq command&quot;, &quot;lprm command&quot;,
-&quot;lppause command&quot; or &quot;lpresume command&quot;) are ignored and they
-should normally have no influence what-so-ever on your printing.
-</p></div><p>
-If you want to do things manually, replace the &quot;printing = cups&quot;
-by &quot;printing = bsd&quot;. Then your manually set commands may work
-(haven't tested this), and a &quot;print command = lp -d %P %s; rm %s&quot;
-may do what you need.
-</p><p>
-You forgot to mention the CUPS version you're using. If you did
-set things up as described in the man pages, then the Samba
-spool files should be deleted. Otherwise it may be a bug. On
-the CUPS side, you can control the behaviour as described
-above.
-</p><p>
-If you have more problems, post the output of these commands:
-</p><p>
-<b><tt>
- grep -v ^# /etc/cups/cupsd.conf | grep -v ^$
- grep -v ^# /etc/samba/smb.conf | grep -v ^$ | grep -v &quot;^;&quot;
-</tt></b>
-</p><p>
-(adapt paths as needed). These commands sanitize the files
-and cut out the empty lines and lines with comments, providing
-the &quot;naked settings&quot; in a compact way.
-</p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="winbind"></a>Chapter15.Unified Logons between Windows NT and UNIX using Winbind</h2></div><div><div class="authorgroup"><div class="author"><h3 class="author">Tim Potter</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt>&lt;<a href="mailto:tpot@linuxcare.com.au">tpot@linuxcare.com.au</a>&gt;</tt></p></div></div></div><div class="author"><h3 class="author">Andrew Tridgell</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt>&lt;<a href="mailto:tridge@samba.org">tridge@samba.org</a>&gt;</tt></p></div></div></div><div class="author"><h3 class="author">John H. Terpstra</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt>&lt;<a href="mailto:jht@samba.org">jht@samba.org</a>&gt;</tt></p></div></div></div><div class="author"><h3 class="author">Naag Mummaneni</h3><div class="affiliation"><div class="address"><p><tt>&lt;<a href="mailto:getnag@rediffmail.com">getnag@rediffmail.com</a>&gt;</tt></p></div></div></div><div class="author"><h3 class="author">Jelmer R. Vernooij</h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt>&lt;<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</tt></p></div></div></div></div></div><div><p class="pubdate">27 June 2002</p></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2874714">Abstract</a></dt><dt><a href="#id2874743">Introduction</a></dt><dt><a href="#id2874814">What Winbind Provides</a></dt><dd><dl><dt><a href="#id2872076">Target Uses</a></dt></dl></dd><dt><a href="#id2872107">How Winbind Works</a></dt><dd><dl><dt><a href="#id2872135">Microsoft Remote Procedure Calls</a></dt><dt><a href="#id2872170">Microsoft Active Directory Services</a></dt><dt><a href="#id2872192">Name Service Switch</a></dt><dt><a href="#id2875280">Pluggable Authentication Modules</a></dt><dt><a href="#id2875352">User and Group ID Allocation</a></dt><dt><a href="#id2875387">Result Caching</a></dt></dl></dd><dt><a href="#id2875414">Installation and Configuration</a></dt><dd><dl><dt><a href="#id2875442">Introduction</a></dt><dt><a href="#id2875518">Requirements</a></dt><dt><a href="#id2875611">Testing Things Out</a></dt></dl></dd><dt><a href="#id2877210">Limitations</a></dt><dt><a href="#id2877264">Conclusion</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2874714"></a>Abstract</h2></div></div><p>Integration of UNIX and Microsoft Windows NT through
- a unified logon has been considered a &quot;holy grail&quot; in heterogeneous
- computing environments for a long time. We present
- <span class="emphasis"><em>winbind</em></span>, a component of the Samba suite
- of programs as a solution to the unified logon problem. Winbind
- uses a UNIX implementation
- of Microsoft RPC calls, Pluggable Authentication Modules, and the Name
- Service Switch to allow Windows NT domain users to appear and operate
- as UNIX users on a UNIX machine. This paper describes the winbind
- system, explaining the functionality it provides, how it is configured,
- and how it works internally.</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2874743"></a>Introduction</h2></div></div><p>It is well known that UNIX and Microsoft Windows NT have
- different models for representing user and group information and
- use different technologies for implementing them. This fact has
- made it difficult to integrate the two systems in a satisfactory
- manner.</p><p>One common solution in use today has been to create
- identically named user accounts on both the UNIX and Windows systems
- and use the Samba suite of programs to provide file and print services
- between the two. This solution is far from perfect however, as
- adding and deleting users on both sets of machines becomes a chore
- and two sets of passwords are required both of which
- can lead to synchronization problems between the UNIX and Windows
- systems and confusion for users.</p><p>We divide the unified logon problem for UNIX machines into
- three smaller problems:</p><div class="itemizedlist"><ul type="disc"><li><p>Obtaining Windows NT user and group information
- </p></li><li><p>Authenticating Windows NT users
- </p></li><li><p>Password changing for Windows NT users
- </p></li></ul></div><p>Ideally, a prospective solution to the unified logon problem
- would satisfy all the above components without duplication of
- information on the UNIX machines and without creating additional
- tasks for the system administrator when maintaining users and
- groups on either system. The winbind system provides a simple
- and elegant solution to all three components of the unified logon
- problem.</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2874814"></a>What Winbind Provides</h2></div></div><p>Winbind unifies UNIX and Windows NT account management by
- allowing a UNIX box to become a full member of a NT domain. Once
- this is done the UNIX box will see NT users and groups as if
- they were native UNIX users and groups, allowing the NT domain
- to be used in much the same manner that NIS+ is used within
- UNIX-only environments.</p><p>The end result is that whenever any
- program on the UNIX machine asks the operating system to lookup
- a user or group name, the query will be resolved by asking the
- NT domain controller for the specified domain to do the lookup.
- Because Winbind hooks into the operating system at a low level
- (via the NSS name resolution modules in the C library) this
- redirection to the NT domain controller is completely
- transparent.</p><p>Users on the UNIX machine can then use NT user and group
- names as they would use &quot;native&quot; UNIX names. They can chown files
- so that they are owned by NT domain users or even login to the
- UNIX machine and run a UNIX X-Window session as a domain user.</p><p>The only obvious indication that Winbind is being used is
- that user and group names take the form DOMAIN\user and
- DOMAIN\group. This is necessary as it allows Winbind to determine
- that redirection to a domain controller is wanted for a particular
- lookup and which trusted domain is being referenced.</p><p>Additionally, Winbind provides an authentication service
- that hooks into the Pluggable Authentication Modules (PAM) system
- to provide authentication via a NT domain to any PAM enabled
- applications. This capability solves the problem of synchronizing
- passwords between systems since all passwords are stored in a single
- location (on the domain controller).</p><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2872076"></a>Target Uses</h3></div></div><p>Winbind is targeted at organizations that have an
- existing NT based domain infrastructure into which they wish
- to put UNIX workstations or servers. Winbind will allow these
- organizations to deploy UNIX workstations without having to
- maintain a separate account infrastructure. This greatly
- simplifies the administrative overhead of deploying UNIX
- workstations into a NT based organization.</p><p>Another interesting way in which we expect Winbind to
- be used is as a central part of UNIX based appliances. Appliances
- that provide file and print services to Microsoft based networks
- will be able to use Winbind to provide seamless integration of
- the appliance into the domain.</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2872107"></a>How Winbind Works</h2></div></div><p>The winbind system is designed around a client/server
- architecture. A long running <b>winbindd</b> daemon
- listens on a UNIX domain socket waiting for requests
- to arrive. These requests are generated by the NSS and PAM
- clients and processed sequentially.</p><p>The technologies used to implement winbind are described
- in detail below.</p><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2872135"></a>Microsoft Remote Procedure Calls</h3></div></div><p>Over the last few years, efforts have been underway
- by various Samba Team members to decode various aspects of
- the Microsoft Remote Procedure Call (MSRPC) system. This
- system is used for most network related operations between
- Windows NT machines including remote management, user authentication
- and print spooling. Although initially this work was done
- to aid the implementation of Primary Domain Controller (PDC)
- functionality in Samba, it has also yielded a body of code which
- can be used for other purposes.</p><p>Winbind uses various MSRPC calls to enumerate domain users
- and groups and to obtain detailed information about individual
- users or groups. Other MSRPC calls can be used to authenticate
- NT domain users and to change user passwords. By directly querying
- a Windows PDC for user and group information, winbind maps the
- NT account information onto UNIX user and group names.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2872170"></a>Microsoft Active Directory Services</h3></div></div><p>
- Since late 2001, Samba has gained the ability to
- interact with Microsoft Windows 2000 using its 'Native
- Mode' protocols, rather than the NT4 RPC services.
- Using LDAP and Kerberos, a domain member running
- winbind can enumerate users and groups in exactly the
- same way as a Win2k client would, and in so doing
- provide a much more efficient and
- effective winbind implementation.
- </p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2872192"></a>Name Service Switch</h3></div></div><p>The Name Service Switch, or NSS, is a feature that is
- present in many UNIX operating systems. It allows system
- information such as hostnames, mail aliases and user information
- to be resolved from different sources. For example, a standalone
- UNIX workstation may resolve system information from a series of
- flat files stored on the local filesystem. A networked workstation
- may first attempt to resolve system information from local files,
- and then consult a NIS database for user information or a DNS server
- for hostname information.</p><p>The NSS application programming interface allows winbind
- to present itself as a source of system information when
- resolving UNIX usernames and groups. Winbind uses this interface,
- and information obtained from a Windows NT server using MSRPC
- calls to provide a new source of account enumeration. Using standard
- UNIX library calls, one can enumerate the users and groups on
- a UNIX machine running winbind and see all users and groups in
- a NT domain plus any trusted domain as though they were local
- users and groups.</p><p>The primary control file for NSS is
- <tt>/etc/nsswitch.conf</tt>.
- When a UNIX application makes a request to do a lookup
- the C library looks in <tt>/etc/nsswitch.conf</tt>
- for a line which matches the service type being requested, for
- example the &quot;passwd&quot; service type is used when user or group names
- are looked up. This config line species which implementations
- of that service should be tried and in what order. If the passwd
- config line is:</p><p><b>passwd: files example</b></p><p>then the C library will first load a module called
- <tt>/lib/libnss_files.so</tt> followed by
- the module <tt>/lib/libnss_example.so</tt>. The
- C library will dynamically load each of these modules in turn
- and call resolver functions within the modules to try to resolve
- the request. Once the request is resolved the C library returns the
- result to the application.</p><p>This NSS interface provides a very easy way for Winbind
- to hook into the operating system. All that needs to be done
- is to put <tt>libnss_winbind.so</tt> in <tt>/lib/</tt>
- then add &quot;winbind&quot; into <tt>/etc/nsswitch.conf</tt> at
- the appropriate place. The C library will then call Winbind to
- resolve user and group names.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2875280"></a>Pluggable Authentication Modules</h3></div></div><p>Pluggable Authentication Modules, also known as PAM,
- is a system for abstracting authentication and authorization
- technologies. With a PAM module it is possible to specify different
- authentication methods for different system applications without
- having to recompile these applications. PAM is also useful
- for implementing a particular policy for authorization. For example,
- a system administrator may only allow console logins from users
- stored in the local password file but only allow users resolved from
- a NIS database to log in over the network.</p><p>Winbind uses the authentication management and password
- management PAM interface to integrate Windows NT users into a
- UNIX system. This allows Windows NT users to log in to a UNIX
- machine and be authenticated against a suitable Primary Domain
- Controller. These users can also change their passwords and have
- this change take effect directly on the Primary Domain Controller.
- </p><p>PAM is configured by providing control files in the directory
- <tt>/etc/pam.d/</tt> for each of the services that
- require authentication. When an authentication request is made
- by an application the PAM code in the C library looks up this
- control file to determine what modules to load to do the
- authentication check and in what order. This interface makes adding
- a new authentication service for Winbind very easy, all that needs
- to be done is that the <tt>pam_winbind.so</tt> module
- is copied to <tt>/lib/security/</tt> and the PAM
- control files for relevant services are updated to allow
- authentication via winbind. See the PAM documentation
- for more details.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2875352"></a>User and Group ID Allocation</h3></div></div><p>When a user or group is created under Windows NT
- is it allocated a numerical relative identifier (RID). This is
- slightly different to UNIX which has a range of numbers that are
- used to identify users, and the same range in which to identify
- groups. It is winbind's job to convert RIDs to UNIX id numbers and
- vice versa. When winbind is configured it is given part of the UNIX
- user id space and a part of the UNIX group id space in which to
- store Windows NT users and groups. If a Windows NT user is
- resolved for the first time, it is allocated the next UNIX id from
- the range. The same process applies for Windows NT groups. Over
- time, winbind will have mapped all Windows NT users and groups
- to UNIX user ids and group ids.</p><p>The results of this mapping are stored persistently in
- an ID mapping database held in a tdb database). This ensures that
- RIDs are mapped to UNIX IDs in a consistent way.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2875387"></a>Result Caching</h3></div></div><p>An active system can generate a lot of user and group
- name lookups. To reduce the network cost of these lookups winbind
- uses a caching scheme based on the SAM sequence number supplied
- by NT domain controllers. User or group information returned
- by a PDC is cached by winbind along with a sequence number also
- returned by the PDC. This sequence number is incremented by
- Windows NT whenever any user or group information is modified. If
- a cached entry has expired, the sequence number is requested from
- the PDC and compared against the sequence number of the cached entry.
- If the sequence numbers do not match, then the cached information
- is discarded and up to date information is requested directly
- from the PDC.</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2875414"></a>Installation and Configuration</h2></div></div><p>
-Many thanks to John Trostel <a href="mailto:jtrostel@snapserver.com" target="_top">jtrostel@snapserver.com</a>
-for providing the HOWTO for this section.
-</p><p>
-This HOWTO describes how to get winbind services up and running
-to control access and authenticate users on your Linux box using
-the winbind services which come with SAMBA 3.0.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2875442"></a>Introduction</h3></div></div><p>
-This HOWTO describes the procedures used to get winbind up and
-running on my RedHat 7.1 system. Winbind is capable of providing access
-and authentication control for Windows Domain users through an NT
-or Win2K PDC for 'regular' services, such as telnet a nd ftp, as
-well for SAMBA services.
-</p><p>
-This HOWTO has been written from a 'RedHat-centric' perspective, so if
-you are using another distribution, you may have to modify the instructions
-somewhat to fit the way your distribution works.
-</p><div class="itemizedlist"><ul type="disc"><li><p>
- <span class="emphasis"><em>Why should I to this?</em></span>
- </p><p>This allows the SAMBA administrator to rely on the
- authentication mechanisms on the NT/Win2K PDC for the authentication
- of domain members. NT/Win2K users no longer need to have separate
- accounts on the SAMBA server.
- </p></li><li><p>
- <span class="emphasis"><em>Who should be reading this document?</em></span>
- </p><p>
- This HOWTO is designed for system administrators. If you are
- implementing SAMBA on a file server and wish to (fairly easily)
- integrate existing NT/Win2K users from your PDC onto the
- SAMBA server, this HOWTO is for you. That said, I am no NT or PAM
- expert, so you may find a better or easier way to accomplish
- these tasks.
- </p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2875518"></a>Requirements</h3></div></div><p>
-If you have a samba configuration file that you are currently
-using... <span class="emphasis"><em>BACK IT UP!</em></span> If your system already uses PAM,
-<span class="emphasis"><em>back up the <tt>/etc/pam.d</tt> directory
-contents!</em></span> If you haven't already made a boot disk,
-<span class="emphasis"><em>MAKE ONE NOW!</em></span>
-</p><p>
-Messing with the pam configuration files can make it nearly impossible
-to log in to yourmachine. That's why you want to be able to boot back
-into your machine in single user mode and restore your
-<tt>/etc/pam.d</tt> back to the original state they were in if
-you get frustrated with the way things are going. ;-)
-</p><p>
-The latest version of SAMBA (version 3.0 as of this writing), now
-includes a functioning winbindd daemon. Please refer to the
-<a href="http://samba.org/" target="_top">main SAMBA web page</a> or,
-better yet, your closest SAMBA mirror site for instructions on
-downloading the source code.
-</p><p>
-To allow Domain users the ability to access SAMBA shares and
-files, as well as potentially other services provided by your
-SAMBA machine, PAM (pluggable authentication modules) must
-be setup properly on your machine. In order to compile the
-winbind modules, you should have at least the pam libraries resident
-on your system. For recent RedHat systems (7.1, for instance), that
-means <tt>pam-0.74-22</tt>. For best results, it is helpful to also
-install the development packages in <tt>pam-devel-0.74-22</tt>.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2875611"></a>Testing Things Out</h3></div></div><p>
-Before starting, it is probably best to kill off all the SAMBA
-related daemons running on your server. Kill off all <b>smbd</b>,
-<b>nmbd</b>, and <b>winbindd</b> processes that may
-be running. To use PAM, you will want to make sure that you have the
-standard PAM package (for RedHat) which supplies the <tt>/etc/pam.d</tt>
-directory structure, including the pam modules are used by pam-aware
-services, several pam libraries, and the <tt>/usr/doc</tt>
-and <tt>/usr/man</tt> entries for pam. Winbind built better
-in SAMBA if the pam-devel package was also installed. This package includes
-the header files needed to compile pam-aware applications. For instance,
-my RedHat system has both <tt>pam-0.74-22</tt> and
-<tt>pam-devel-0.74-22</tt> RPMs installed.
-</p><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2875688"></a>Configure and compile SAMBA</h4></div></div><p>
-The configuration and compilation of SAMBA is pretty straightforward.
-The first three steps may not be necessary depending upon
-whether or not you have previously built the Samba binaries.
-</p><pre class="programlisting">
-<tt>root#</tt> <b>autoconf</b>
-<tt>root#</tt> <b>make clean</b>
-<tt>root#</tt> <b>rm config.cache</b>
-<tt>root#</tt> <b>./configure</b>
-<tt>root#</tt> <b>make</b>
-<tt>root#</tt> <b>make install</b>
-</pre><p>
-This will, by default, install SAMBA in <tt>/usr/local/samba</tt>.
-See the main SAMBA documentation if you want to install SAMBA somewhere else.
-It will also build the winbindd executable and libraries.
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2875809"></a>Configure <tt>nsswitch.conf</tt> and the
-winbind libraries on Linux and Solaris</h4></div></div><p>
-The libraries needed to run the <b>winbindd</b> daemon
-through nsswitch need to be copied to their proper locations, so
-</p><p>
-<tt>root#</tt> <b>cp ../samba/source/nsswitch/libnss_winbind.so /lib</b>
-</p><p>
-I also found it necessary to make the following symbolic link:
-</p><p>
-<tt>root#</tt> <b>ln -s /lib/libnss_winbind.so /lib/libnss_winbind.so.2</b>
-</p><p>And, in the case of Sun solaris:</p><p>
-<tt>root#</tt> <b><tt>ln -s /usr/lib/libnss_winbind.so /usr/lib/libnss_winbind.so.1</tt></b>
-<tt>root#</tt> <b><tt>ln -s /usr/lib/libnss_winbind.so /usr/lib/nss_winbind.so.1</tt></b>
-<tt>root#</tt> <b><tt>ln -s /usr/lib/libnss_winbind.so /usr/lib/nss_winbind.so.2</tt></b>
-</p><p>
-Now, as root you need to edit <tt>/etc/nsswitch.conf</tt> to
-allow user and group entries to be visible from the <b>winbindd</b>
-daemon. My <tt>/etc/nsswitch.conf</tt> file look like
-this after editing:
-</p><pre class="programlisting">
- passwd: files winbind
- shadow: files
- group: files winbind
-</pre><p>
-The libraries needed by the winbind daemon will be automatically
-entered into the <b>ldconfig</b> cache the next time
-your system reboots, but it
-is faster (and you don't need to reboot) if you do it manually:
-</p><p>
-<tt>root#</tt> <b>/sbin/ldconfig -v | grep winbind</b>
-</p><p>
-This makes <tt>libnss_winbind</tt> available to winbindd
-and echos back a check to you.
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2876014"></a>NSS Winbind on AIX</h4></div></div><p>(This section is only for those running AIX)</p><p>
-The winbind AIX identification module gets built as libnss_winbind.so in the
-nsswitch directory of the samba source. This file can be copied to
-/usr/lib/security, and the AIX naming convention would indicate that it
-should be named WINBIND. A stanza like the following:
-</p><pre class="programlisting">
-WINBIND:
- program = /usr/lib/security/WINBIND
- options = authonly
-</pre><p>can then be added to
-<tt>/usr/lib/security/methods.cfg</tt>. This module only
-supports identification, but there have been success reports using the
-standard winbind pam module for authentication. Use caution configuring
-loadable authentication modules as it is possible to make it impossible
-to logon to the system. More information about the AIX authentication
-module API can be found at &quot;Kernel Extensions and Device Support
-Programming Concepts for AIX&quot;: <a href="#">
-Chapter 18. Loadable Authentication Module Programming Interface</a>
-and more information on administering the modules at <a href="#">
-&quot;System Management Guide: Operating System and Devices&quot;</a>.
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2876087"></a>Configure smb.conf</h4></div></div><p>
-Several parameters are needed in the smb.conf file to control
-the behavior of <b>winbindd</b>. Configure
-<tt>smb.conf</tt> These are described in more detail in
-the <a href="winbindd.8.html">winbindd(8)</a> man page. My
-<tt>smb.conf</tt> file was modified to
-include the following entries in the [global] section:
-</p><pre class="programlisting">
-[global]
- &lt;...&gt;
- # separate domain and username with '+', like DOMAIN+username
- <a href="winbindd.8.html#WINBINDSEPARATOR" target="_top">winbind separator</a> = +
- # use uids from 10000 to 20000 for domain users
- <a href="winbindd.8.html#WINBINDUID" target="_top">winbind uid</a> = 10000-20000
- # use gids from 10000 to 20000 for domain groups
- <a href="winbindd.8.html#WINBINDGID" target="_top">winbind gid</a> = 10000-20000
- # allow enumeration of winbind users and groups
- <a href="winbindd.8.html#WINBINDENUMUSERS" target="_top">winbind enum users</a> = yes
- <a href="winbindd.8.html#WINBINDENUMGROUP" target="_top">winbind enum groups</a> = yes
- # give winbind users a real shell (only needed if they have telnet access)
- <a href="winbindd.8.html#TEMPLATEHOMEDIR" target="_top">template homedir</a> = /home/winnt/%D/%U
- <a href="winbindd.8.html#TEMPLATESHELL" target="_top">template shell</a> = /bin/bash
-</pre></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2876202"></a>Join the SAMBA server to the PDC domain</h4></div></div><p>
-Enter the following command to make the SAMBA server join the
-PDC domain, where <i><tt>DOMAIN</tt></i> is the name of
-your Windows domain and <i><tt>Administrator</tt></i> is
-a domain user who has administrative privileges in the domain.
-</p><p>
-<tt>root#</tt> <b>/usr/local/samba/bin/net join -S PDC -U Administrator</b>
-</p><p>
-The proper response to the command should be: &quot;Joined the domain
-<i><tt>DOMAIN</tt></i>&quot; where <i><tt>DOMAIN</tt></i>
-is your DOMAIN name.
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2876259"></a>Start up the winbindd daemon and test it!</h4></div></div><p>
-Eventually, you will want to modify your smb startup script to
-automatically invoke the winbindd daemon when the other parts of
-SAMBA start, but it is possible to test out just the winbind
-portion first. To start up winbind services, enter the following
-command as root:
-</p><p>
-<tt>root#</tt> <b>/usr/local/samba/bin/winbindd</b>
-</p><p>
-Winbindd can now also run in 'dual daemon mode'. This will make it
-run as 2 processes. The first will answer all requests from the cache,
-thus making responses to clients faster. The other will
-update the cache for the query that the first has just responded.
-Advantage of this is that responses stay accurate and are faster.
-You can enable dual daemon mode by adding '-B' to the commandline:
-</p><p>
-<tt>root#</tt> <b>/usr/local/samba/bin/winbindd -B</b>
-</p><p>
-I'm always paranoid and like to make sure the daemon
-is really running...
-</p><p>
-<tt>root#</tt> <b>ps -ae | grep winbindd</b>
-</p><p>
-This command should produce output like this, if the daemon is running
-</p><p>
-3025 ? 00:00:00 winbindd
-</p><p>
-Now... for the real test, try to get some information about the
-users on your PDC
-</p><p>
-<tt>root#</tt> <b>/usr/local/samba/bin/wbinfo -u</b>
-</p><p>
-This should echo back a list of users on your Windows users on
-your PDC. For example, I get the following response:
-</p><pre class="programlisting">
- CEO+Administrator
- CEO+burdell
- CEO+Guest
- CEO+jt-ad
- CEO+krbtgt
- CEO+TsInternetUser
-</pre><p>
-Obviously, I have named my domain 'CEO' and my <i><tt>winbind
-separator</tt></i> is '+'.
-</p><p>
-You can do the same sort of thing to get group information from
-the PDC:
-</p><pre class="programlisting">
-<tt>root#</tt> <b>/usr/local/samba/bin/wbinfo -g</b>
- CEO+Domain Admins
- CEO+Domain Users
- CEO+Domain Guests
- CEO+Domain Computers
- CEO+Domain Controllers
- CEO+Cert Publishers
- CEO+Schema Admins
- CEO+Enterprise Admins
- CEO+Group Policy Creator Owners
-</pre><p>
-The function 'getent' can now be used to get unified
-lists of both local and PDC users and groups.
-Try the following command:
-</p><p>
-<tt>root#</tt> <b>getent passwd</b>
-</p><p>
-You should get a list that looks like your <tt>/etc/passwd</tt>
-list followed by the domain users with their new uids, gids, home
-directories and default shells.
-</p><p>
-The same thing can be done for groups with the command
-</p><p>
-<tt>root#</tt> <b>getent group</b>
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2876504"></a>Fix the init.d startup scripts</h4></div></div><div class="sect4" lang="en"><div class="titlepage"><div><h5 class="title"><a name="id2876511"></a>Linux</h5></div></div><p>
-The <b>winbindd</b> daemon needs to start up after the
-<b>smbd</b> and <b>nmbd</b> daemons are running.
-To accomplish this task, you need to modify the startup scripts of your system.
-They are located at <tt>/etc/init.d/smb</tt> in RedHat and
-<tt>/etc/init.d/samba</tt> in Debian.
-script to add commands to invoke this daemon in the proper sequence. My
-startup script starts up <b>smbd</b>,
-<b>nmbd</b>, and <b>winbindd</b> from the
-<tt>/usr/local/samba/bin</tt> directory directly. The 'start'
-function in the script looks like this:
-</p><pre class="programlisting">
-start() {
- KIND=&quot;SMB&quot;
- echo -n $&quot;Starting $KIND services: &quot;
- daemon /usr/local/samba/bin/smbd $SMBDOPTIONS
- RETVAL=$?
- echo
- KIND=&quot;NMB&quot;
- echo -n $&quot;Starting $KIND services: &quot;
- daemon /usr/local/samba/bin/nmbd $NMBDOPTIONS
- RETVAL2=$?
- echo
- KIND=&quot;Winbind&quot;
- echo -n $&quot;Starting $KIND services: &quot;
- daemon /usr/local/samba/bin/winbindd
- RETVAL3=$?
- echo
- [ $RETVAL -eq 0 -a $RETVAL2 -eq 0 -a $RETVAL3 -eq 0 ] &amp;&amp; \
- touch /var/lock/subsys/smb || RETVAL=1
- return $RETVAL
-}
-</pre><p>If you would like to run winbindd in dual daemon mode, replace
-the line
-</p><pre class="programlisting">
- daemon /usr/local/samba/bin/winbindd
-</pre><p>
-
-in the example above with:
-
-</p><pre class="programlisting">
- daemon /usr/local/samba/bin/winbindd -B
-</pre><p>.
-</p><p>
-The 'stop' function has a corresponding entry to shut down the
-services and looks like this:
-</p><pre class="programlisting">
-stop() {
- KIND=&quot;SMB&quot;
- echo -n $&quot;Shutting down $KIND services: &quot;
- killproc smbd
- RETVAL=$?
- echo
- KIND=&quot;NMB&quot;
- echo -n $&quot;Shutting down $KIND services: &quot;
- killproc nmbd
- RETVAL2=$?
- echo
- KIND=&quot;Winbind&quot;
- echo -n $&quot;Shutting down $KIND services: &quot;
- killproc winbindd
- RETVAL3=$?
- [ $RETVAL -eq 0 -a $RETVAL2 -eq 0 -a $RETVAL3 -eq 0 ] &amp;&amp; \
- rm -f /var/lock/subsys/smb
- echo &quot;&quot;
- return $RETVAL
-}
-</pre></div><div class="sect4" lang="en"><div class="titlepage"><div><h5 class="title"><a name="id2876648"></a>Solaris</h5></div></div><p>Winbind doesn't work on solaris 9, see the <a href="#winbind-solaris9" title="Winbind on Solaris 9">Portability</a> chapter for details.</p><p>On solaris, you need to modify the
-<tt>/etc/init.d/samba.server</tt> startup script. It usually
-only starts smbd and nmbd but should now start winbindd too. If you
-have samba installed in <tt>/usr/local/samba/bin</tt>,
-the file could contains something like this:
-</p><pre class="programlisting">
- ##
- ## samba.server
- ##
-
- if [ ! -d /usr/bin ]
- then # /usr not mounted
- exit
- fi
-
- killproc() { # kill the named process(es)
- pid=`/usr/bin/ps -e |
- /usr/bin/grep -w $1 |
- /usr/bin/sed -e 's/^ *//' -e 's/ .*//'`
- [ &quot;$pid&quot; != &quot;&quot; ] &amp;&amp; kill $pid
- }
-
- # Start/stop processes required for samba server
-
- case &quot;$1&quot; in
-
- 'start')
- #
- # Edit these lines to suit your installation (paths, workgroup, host)
- #
- echo Starting SMBD
- /usr/local/samba/bin/smbd -D -s \
- /usr/local/samba/smb.conf
-
- echo Starting NMBD
- /usr/local/samba/bin/nmbd -D -l \
- /usr/local/samba/var/log -s /usr/local/samba/smb.conf
-
- echo Starting Winbind Daemon
- /usr/local/samba/bin/winbindd
- ;;
-
- 'stop')
- killproc nmbd
- killproc smbd
- killproc winbindd
- ;;
-
- *)
- echo &quot;Usage: /etc/init.d/samba.server { start | stop }&quot;
- ;;
- esac
-</pre><p>
-Again, if you would like to run samba in dual daemon mode, replace
-</p><pre class="programlisting">
- /usr/local/samba/bin/winbindd
-</pre><p>
-
-in the script above with:
-
-</p><pre class="programlisting">
- /usr/local/samba/bin/winbindd -B
-</pre><p>
-</p></div><div class="sect4" lang="en"><div class="titlepage"><div><h5 class="title"><a name="id2876749"></a>Restarting</h5></div></div><p>
-If you restart the <b>smbd</b>, <b>nmbd</b>,
-and <b>winbindd</b> daemons at this point, you
-should be able to connect to the samba server as a domain member just as
-if you were a local user.
-</p></div></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2876785"></a>Configure Winbind and PAM</h4></div></div><p>
-If you have made it this far, you know that winbindd and samba are working
-together. If you want to use winbind to provide authentication for other
-services, keep reading. The pam configuration files need to be altered in
-this step. (Did you remember to make backups of your original
-<tt>/etc/pam.d</tt> files? If not, do it now.)
-</p><p>
-You will need a pam module to use winbindd with these other services. This
-module will be compiled in the <tt>../source/nsswitch</tt> directory
-by invoking the command
-</p><p>
-<tt>root#</tt> <b>make nsswitch/pam_winbind.so</b>
-</p><p>
-from the <tt>../source</tt> directory. The
-<tt>pam_winbind.so</tt> file should be copied to the location of
-your other pam security modules. On my RedHat system, this was the
-<tt>/lib/security</tt> directory. On Solaris, the pam security
-modules reside in <tt>/usr/lib/security</tt>.
-</p><p>
-<tt>root#</tt> <b>cp ../samba/source/nsswitch/pam_winbind.so /lib/security</b>
-</p><div class="sect4" lang="en"><div class="titlepage"><div><h5 class="title"><a name="id2876895"></a>Linux/FreeBSD-specific PAM configuration</h5></div></div><p>
-The <tt>/etc/pam.d/samba</tt> file does not need to be changed. I
-just left this fileas it was:
-</p><pre class="programlisting">
- auth required /lib/security/pam_stack.so service=system-auth
- account required /lib/security/pam_stack.so service=system-auth
-</pre><p>
-The other services that I modified to allow the use of winbind
-as an authentication service were the normal login on the console (or a terminal
-session), telnet logins, and ftp service. In order to enable these
-services, you may first need to change the entries in
-<tt>/etc/xinetd.d</tt> (or <tt>/etc/inetd.conf</tt>).
-RedHat 7.1 uses the new xinetd.d structure, in this case you need
-to change the lines in <tt>/etc/xinetd.d/telnet</tt>
-and <tt>/etc/xinetd.d/wu-ftp</tt> from
-</p><pre class="programlisting">
- enable = no
-</pre><p>
-to
-</p><pre class="programlisting">
- enable = yes
-</pre><p>
-For ftp services to work properly, you will also need to either
-have individual directories for the domain users already present on
-the server, or change the home directory template to a general
-directory for all domain users. These can be easily set using
-the <tt>smb.conf</tt> global entry
-<b>template homedir</b>.
-</p><p>
-The <tt>/etc/pam.d/ftp</tt> file can be changed
-to allow winbind ftp access in a manner similar to the
-samba file. My <tt>/etc/pam.d/ftp</tt> file was
-changed to look like this:
-</p><pre class="programlisting">
- auth required /lib/security/pam_listfile.so item=user sense=deny \
- file=/etc/ftpusers onerr=succeed
- auth sufficient /lib/security/pam_winbind.so
- auth required /lib/security/pam_stack.so service=system-auth
- auth required /lib/security/pam_shells.so
- account sufficient /lib/security/pam_winbind.so
- account required /lib/security/pam_stack.so service=system-auth
- session required /lib/security/pam_stack.so service=system-auth
-</pre><p>
-The <tt>/etc/pam.d/login</tt> file can be changed nearly the
-same way. It now looks like this:
-</p><pre class="programlisting">
- auth required /lib/security/pam_securetty.so
- auth sufficient /lib/security/pam_winbind.so
- auth sufficient /lib/security/pam_unix.so use_first_pass
- auth required /lib/security/pam_stack.so service=system-auth
- auth required /lib/security/pam_nologin.so
- account sufficient /lib/security/pam_winbind.so
- account required /lib/security/pam_stack.so service=system-auth
- password required /lib/security/pam_stack.so service=system-auth
- session required /lib/security/pam_stack.so service=system-auth
- session optional /lib/security/pam_console.so
-</pre><p>
-In this case, I added the <b>auth sufficient /lib/security/pam_winbind.so</b>
-lines as before, but also added the <b>required pam_securetty.so</b>
-above it, to disallow root logins over the network. I also added a
-<b>sufficient /lib/security/pam_unix.so use_first_pass</b>
-line after the <b>winbind.so</b> line to get rid of annoying
-double prompts for passwords.
-</p></div><div class="sect4" lang="en"><div class="titlepage"><div><h5 class="title"><a name="id2877118"></a>Solaris-specific configuration</h5></div></div><p>
-The /etc/pam.conf needs to be changed. I changed this file so that my Domain
-users can logon both locally as well as telnet.The following are the changes
-that I made.You can customize the pam.conf file as per your requirements,but
-be sure of those changes because in the worst case it will leave your system
-nearly impossible to boot.
-</p><pre class="programlisting">
- #
- #ident &quot;@(#)pam.conf 1.14 99/09/16 SMI&quot;
- #
- # Copyright (c) 1996-1999, Sun Microsystems, Inc.
- # All Rights Reserved.
- #
- # PAM configuration
- #
- # Authentication management
- #
- login auth required /usr/lib/security/pam_winbind.so
- login auth required /usr/lib/security/$ISA/pam_unix.so.1 try_first_pass
- login auth required /usr/lib/security/$ISA/pam_dial_auth.so.1 try_first_pass
- #
- rlogin auth sufficient /usr/lib/security/pam_winbind.so
- rlogin auth sufficient /usr/lib/security/$ISA/pam_rhosts_auth.so.1
- rlogin auth required /usr/lib/security/$ISA/pam_unix.so.1 try_first_pass
- #
- dtlogin auth sufficient /usr/lib/security/pam_winbind.so
- dtlogin auth required /usr/lib/security/$ISA/pam_unix.so.1 try_first_pass
- #
- rsh auth required /usr/lib/security/$ISA/pam_rhosts_auth.so.1
- other auth sufficient /usr/lib/security/pam_winbind.so
- other auth required /usr/lib/security/$ISA/pam_unix.so.1 try_first_pass
- #
- # Account management
- #
- login account sufficient /usr/lib/security/pam_winbind.so
- login account requisite /usr/lib/security/$ISA/pam_roles.so.1
- login account required /usr/lib/security/$ISA/pam_unix.so.1
- #
- dtlogin account sufficient /usr/lib/security/pam_winbind.so
- dtlogin account requisite /usr/lib/security/$ISA/pam_roles.so.1
- dtlogin account required /usr/lib/security/$ISA/pam_unix.so.1
- #
- other account sufficient /usr/lib/security/pam_winbind.so
- other account requisite /usr/lib/security/$ISA/pam_roles.so.1
- other account required /usr/lib/security/$ISA/pam_unix.so.1
- #
- # Session management
- #
- other session required /usr/lib/security/$ISA/pam_unix.so.1
- #
- # Password management
- #
- #other password sufficient /usr/lib/security/pam_winbind.so
- other password required /usr/lib/security/$ISA/pam_unix.so.1
- dtsession auth required /usr/lib/security/$ISA/pam_unix.so.1
- #
- # Support for Kerberos V5 authentication (uncomment to use Kerberos)
- #
- #rlogin auth optional /usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass
- #login auth optional /usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass
- #dtlogin auth optional /usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass
- #other auth optional /usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass
- #dtlogin account optional /usr/lib/security/$ISA/pam_krb5.so.1
- #other account optional /usr/lib/security/$ISA/pam_krb5.so.1
- #other session optional /usr/lib/security/$ISA/pam_krb5.so.1
- #other password optional /usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass
-</pre><p>
-I also added a try_first_pass line after the winbind.so line to get rid of
-annoying double prompts for passwords.
-</p><p>
-Now restart your Samba and try connecting through your application that you
-configured in the pam.conf.
-</p></div></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2877210"></a>Limitations</h2></div></div><p>Winbind has a number of limitations in its current
- released version that we hope to overcome in future
- releases:</p><div class="itemizedlist"><ul type="disc"><li><p>Winbind is currently only available for
- the Linux, Solaris and IRIX operating systems, although ports to other operating
- systems are certainly possible. For such ports to be feasible,
- we require the C library of the target operating system to
- support the Name Service Switch and Pluggable Authentication
- Modules systems. This is becoming more common as NSS and
- PAM gain support among UNIX vendors.</p></li><li><p>The mappings of Windows NT RIDs to UNIX ids
- is not made algorithmically and depends on the order in which
- unmapped users or groups are seen by winbind. It may be difficult
- to recover the mappings of rid to UNIX id mapping if the file
- containing this information is corrupted or destroyed.</p></li><li><p>Currently the winbind PAM module does not take
- into account possible workstation and logon time restrictions
- that may be been set for Windows NT users, this is
- instead up to the PDC to enforce.</p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2877264"></a>Conclusion</h2></div></div><p>The winbind system, through the use of the Name Service
- Switch, Pluggable Authentication Modules, and appropriate
- Microsoft RPC calls have allowed us to provide seamless
- integration of Microsoft Windows NT domain users on a
- UNIX system. The result is a great reduction in the administrative
- cost of running a mixed UNIX and NT network.</p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="AdvancedNetworkManagement"></a>Chapter16.Advanced Network Manangement</h2></div><div><div class="author"><h3 class="author">John H. Terpstra</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt>&lt;<a href="mailto:jht@samba.org">jht@samba.org</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate">April 3 2003</p></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2875143">Configuring Samba Share Access Controls</a></dt><dd><dl><dt><a href="#id2874905">Share Permissions Management</a></dt></dl></dd><dt><a href="#id2874974">Remote Server Administration</a></dt><dt><a href="#id2875057">Network Logon Script Magic</a></dt><dd><dl><dt><a href="#id2877889">Adding printers without user intervention</a></dt></dl></dd></dl></div><p>
-This section attempts to document peripheral issues that are of great importance to network
-administrators who want to improve network resource access control, to automate the user
-environment, and to make their lives a little easier.
-</p><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2875143"></a>Configuring Samba Share Access Controls</h2></div></div><p>
-This section deals with how to configure Samba per share access control restrictions.
-By default samba sets no restrictions on the share itself. Restrictions on the share itself
-can be set on MS Windows NT4/200x/XP shares. This can be a very effective way to limit who can
-connect to a share. In the absence of specific restrictions the default setting is to allow
-the global user <span class="emphasis"><em>Everyone</em></span> Full Control (ie: Full control, Change and Read).
-</p><p>
-At this time Samba does NOT provide a tool for configuring access control setting on the Share
-itself. Samba does have the capacity to store and act on access control settings, but the only
-way to create those settings is to use either the NT4 Server Manager or the Windows 200x MMC for
-Computer Management.
-</p><p>
-Samba stores the per share access control settings in a file called <tt>share_info.tdb</tt>.
-The location of this file on your system will depend on how samba was compiled. The default location
-for samba's tdb files is under <tt>/usr/local/samba/var</tt>. If the <tt>tdbdump</tt>
-utility has been compiled and installed on your system then you can examine the contents of this file
-by: <b><tt>tdbdump share_info.tdb</tt></b>.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2874905"></a>Share Permissions Management</h3></div></div><p>
-The best tool for the task is platform dependant. Choose the best tool for your environmemt.
-</p><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2874919"></a>Windows NT4 Workstation/Server</h4></div></div><p>
-The tool you need to use to manage share permissions on a Samba server is the NT Server Manager.
-Server Manager is shipped with Windows NT4 Server products but not with Windows NT4 Workstation.
-You can obtain the NT Server Manager for MS Windows NT4 Workstation from Microsoft - see details below.
-</p><div class="procedure"><p class="title"><b>Procedure16.1.Instructions</b></p><ol type="1"><li><p>
-Launch the NT4 Server Manager, click on the Samba server you want to administer, then from the menu
-select Computer, then click on the Shared Directories entry.
-</p></li><li><p>
- Now click on the share that you wish to manage, then click on the Properties tab, next click on
- the Permissions tab. Now you can Add or change access control settings as you wish.
-</p></li></ol></div></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2877329"></a>Windows 200x/XP</h4></div></div><p>
-On MS Windows NT4/200x/XP system access control lists on the share itself are set using native
-tools, usually from filemanager. For example, in Windows 200x: right click on the shared folder,
-then select 'Sharing', then click on 'Permissions'. The default Windows NT4/200x permission allows
-<span class="emphasis"><em>Everyone</em></span> Full Control on the Share.
-</p><p>
-MS Windows 200x and later all comes with a tool called the 'Computer Management' snap-in for the
-Microsoft Management Console (MMC). This tool is located by clicking on <tt>Control Panel -&gt;
-Administrative Tools -&gt; Computer Management</tt>.
-</p><div class="procedure"><p class="title"><b>Procedure16.2.Instructions</b></p><ol type="1"><li><p>
- After launching the MMC with the Computer Management snap-in, click on the menu item 'Action',
- select 'Connect to another computer'. If you are not logged onto a domain you will be prompted
- to enter a domain login user identifier and a password. This will authenticate you to the domain.
- If you where already logged in with administrative privilidge this step is not offered.
-</p></li><li><p>
-If the Samba server is not shown in the Select Computer box, then type in the name of the target
-Samba server in the field 'Name:'. Now click on the [+] next to 'System Tools', then on the [+]
-next to 'Shared Folders' in the left panel.
-</p></li><li><p>
-Now in the right panel, double-click on the share you wish to set access control permissions on.
-Then click on the tab 'Share Permissions'. It is now possible to add access control entities
-to the shared folder. Do NOT forget to set what type of access (full control, change, read) you
-wish to assign for each entry.
-</p></li></ol></div><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p>
-Be careful. If you take away all permissions from the Everyone user without removing this user
-then effectively no user will be able to access the share. This is a result of what is known as
-ACL precidence. ie: Everyone with NO ACCESS means that MaryK who is part of the group Everyone
-will have no access even if this user is given explicit full control access.
-</p></div></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2874974"></a>Remote Server Administration</h2></div></div><p>
-<span class="emphasis"><em>How do I get 'User Manager' and 'Server Manager'?</em></span>
-</p><p>
-Since I don't need to buy an NT4 Server, how do I get the 'User Manager for Domains',
-the 'Server Manager'?
-</p><p>
-Microsoft distributes a version of these tools called nexus for installation on Windows 9x / Me
-systems. The tools set includes:
-</p><div class="itemizedlist"><ul type="disc"><li><p>Server Manager</p></li><li><p>User Manager for Domains</p></li><li><p>Event Viewer</p></li></ul></div><p>
-Click here to download the archived file <a href="ftp://ftp.microsoft.com/Softlib/MSLFILES/NEXUS.EXE" target="_top">ftp://ftp.microsoft.com/Softlib/MSLFILES/NEXUS.EXE</a>
-</p><p>
-The Windows NT 4.0 version of the 'User Manager for
-Domains' and 'Server Manager' are available from Microsoft via ftp
-from <a href="ftp://ftp.microsoft.com/Softlib/MSLFILES/SRVTOOLS.EXE" target="_top">ftp://ftp.microsoft.com/Softlib/MSLFILES/SRVTOOLS.EXE</a>
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2875057"></a>Network Logon Script Magic</h2></div></div><p>
-This section needs work. Volunteer contributions most welcome. Please send your patches or updates
-to <a href="mailto:jht@samba.org" target="_top">John Terpstra</a>.
-</p><p>
-There are several opportunities for creating a custom network startup configuration environment.
-</p><table class="simplelist" border="0" summary="Simple list"><tr><td>No Logon Script</td></tr><tr><td>Simple universal Logon Script that applies to all users</td></tr><tr><td>Use of a conditional Logon Script that applies per user or per group attirbutes</td></tr><tr><td>Use of Samba's Preexec and Postexec functions on access to the NETLOGON share to create
- a custom Logon Script and then execute it.</td></tr><tr><td>User of a tool such as KixStart</td></tr></table><p>
-The Samba source code tree includes two logon script generation/execution tools. See <tt>examples</tt> directory <tt>genlogon</tt> and <tt>ntlogon</tt> subdirectories.
-</p><p>
-The following listings are from the genlogon directory.
-</p><p>
-This is the genlogon.pl file:
-
-</p><pre class="programlisting">
- #!/usr/bin/perl
- #
- # genlogon.pl
- #
- # Perl script to generate user logon scripts on the fly, when users
- # connect from a Windows client. This script should be called from smb.conf
- # with the %U, %G and %L parameters. I.e:
- #
- # root preexec = genlogon.pl %U %G %L
- #
- # The script generated will perform
- # the following:
- #
- # 1. Log the user connection to /var/log/samba/netlogon.log
- # 2. Set the PC's time to the Linux server time (which is maintained
- # daily to the National Institute of Standard's Atomic clock on the
- # internet.
- # 3. Connect the user's home drive to H: (H for Home).
- # 4. Connect common drives that everyone uses.
- # 5. Connect group-specific drives for certain user groups.
- # 6. Connect user-specific drives for certain users.
- # 7. Connect network printers.
-
- # Log client connection
- #($sec,$min,$hour,$mday,$mon,$year,$wday,$yday,$isdst) = localtime(time);
- ($sec,$min,$hour,$mday,$mon,$year,$wday,$yday,$isdst) = localtime(time);
- open LOG, &quot;&gt;&gt;/var/log/samba/netlogon.log&quot;;
- print LOG &quot;$mon/$mday/$year $hour:$min:$sec - User $ARGV[0] logged into $ARGV[1]\n&quot;;
- close LOG;
-
- # Start generating logon script
- open LOGON, &quot;&gt;/shared/netlogon/$ARGV[0].bat&quot;;
- print LOGON &quot;\@ECHO OFF\r\n&quot;;
-
- # Connect shares just use by Software Development group
- if ($ARGV[1] eq &quot;SOFTDEV&quot; || $ARGV[0] eq &quot;softdev&quot;)
- {
- print LOGON &quot;NET USE M: \\\\$ARGV[2]\\SOURCE\r\n&quot;;
- }
-
- # Connect shares just use by Technical Support staff
- if ($ARGV[1] eq &quot;SUPPORT&quot; || $ARGV[0] eq &quot;support&quot;)
- {
- print LOGON &quot;NET USE S: \\\\$ARGV[2]\\SUPPORT\r\n&quot;;
- }
-
- # Connect shares just used by Administration staff
- If ($ARGV[1] eq &quot;ADMIN&quot; || $ARGV[0] eq &quot;admin&quot;)
- {
- print LOGON &quot;NET USE L: \\\\$ARGV[2]\\ADMIN\r\n&quot;;
- print LOGON &quot;NET USE K: \\\\$ARGV[2]\\MKTING\r\n&quot;;
- }
-
- # Now connect Printers. We handle just two or three users a little
- # differently, because they are the exceptions that have desktop
- # printers on LPT1: - all other user's go to the LaserJet on the
- # server.
- if ($ARGV[0] eq 'jim'
- || $ARGV[0] eq 'yvonne')
- {
- print LOGON &quot;NET USE LPT2: \\\\$ARGV[2]\\LJET3\r\n&quot;;
- print LOGON &quot;NET USE LPT3: \\\\$ARGV[2]\\FAXQ\r\n&quot;;
- }
- else
- {
- print LOGON &quot;NET USE LPT1: \\\\$ARGV[2]\\LJET3\r\n&quot;;
- print LOGON &quot;NET USE LPT3: \\\\$ARGV[2]\\FAXQ\r\n&quot;;
- }
-
- # All done! Close the output file.
- close LOGON;
-</pre><p>
-</p><p>
-Those wishing to use more elaborate or capable logon processing system should check out the following sites:
-</p><table class="simplelist" border="0" summary="Simple list"><tr><td>http://www.craigelachie.org/rhacer/ntlogon</td></tr><tr><td>http://www.kixtart.org</td></tr><tr><td>http://support.microsoft.com/default.asp?scid=kb;en-us;189105</td></tr></table><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2877889"></a>Adding printers without user intervention</h3></div></div><p>
-Printers may be added automatically during logon script processing through the use of:
-
-</p><pre class="programlisting">
- rundll32 printui.dll,PrintUIEntry /?
-</pre><p>
-
-See the documentation in the Microsoft knowledgebase article no: 189105 referred to above.
-</p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="PolicyMgmt"></a>Chapter17.System and Account Policies</h2></div><div><div class="author"><h3 class="author">John H. Terpstra</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt>&lt;<a href="mailto:jht@samba.org">jht@samba.org</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate">April 3 2003</p></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2877672">Creating and Managing System Policies</a></dt><dd><dl><dt><a href="#id2877925">Windows 9x/Me Policies</a></dt><dt><a href="#id2878014">Windows NT4 Style Policy Files</a></dt><dt><a href="#id2878140">MS Windows 200x / XP Professional Policies</a></dt></dl></dd><dt><a href="#id2878344">Managing Account/User Policies</a></dt><dd><dl><dt><a href="#id2878457">With Windows NT4/200x</a></dt><dt><a href="#id2878478">With a Samba PDC</a></dt></dl></dd><dt><a href="#id2878502">System Startup and Logon Processing Overview</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2877672"></a>Creating and Managing System Policies</h2></div></div><p>
-Under MS Windows platforms, particularly those following the release of MS Windows
-NT4 and MS Windows 95) it is possible to create a type of file that would be placed
-in the NETLOGON share of a domain controller. As the client logs onto the network
-this file is read and the contents initiate changes to the registry of the client
-machine. This file allows changes to be made to those parts of the registry that
-affect users, groups of users, or machines.
-</p><p>
-For MS Windows 9x/Me this file must be called <tt>Config.POL</tt> and may
-be generated using a tool called <tt>poledit.exe</tt>, better known as the
-Policy Editor. The policy editor was provided on the Windows 98 installation CD, but
-dissappeared again with the introduction of MS Windows Me (Millenium Edition). From
-comments from MS Windows network administrators it would appear that this tool became
-a part of the MS Windows Me Resource Kit.
-</p><p>
-MS Windows NT4 Server products include the <span class="emphasis"><em>System Policy Editor</em></span>
-under the <tt>Start -&gt; Programs -&gt; Administrative Tools</tt> menu item.
-For MS Windows NT4 and later clients this file must be called <tt>NTConfig.POL</tt>.
-</p><p>
-New with the introduction of MS Windows 2000 was the Microsoft Management Console
-or MMC. This tool is the new wave in the ever changing landscape of Microsoft
-methods for management of network access and security. Every new Microsoft product
-or technology seems to obsolete the old rules and to introduce newer and more
-complex tools and methods. To Microsoft's credit though, the MMC does appear to
-be a step forward, but improved functionality comes at a great price.
-</p><p>
-Before embarking on the configuration of network and system policies it is highly
-advisable to read the documentation available from Microsoft's web site regarding
-<a href="http://www.microsoft.com/ntserver/management/deployment/planguide/prof_policies.asp" target="_top">
-Implementing Profiles and Policies in Windows NT 4.0 from http://www.microsoft.com/ntserver/management/deployment/planguide/prof_policies.asp</a> available from Microsoft.
-There are a large number of documents in addition to this old one that should also
-be read and understood. Try searching on the Microsoft web site for &quot;Group Policies&quot;.
-</p><p>
-What follows is a very brief discussion with some helpful notes. The information provided
-here is incomplete - you are warned.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2877925"></a>Windows 9x/Me Policies</h3></div></div><p>
-You need the Win98 Group Policy Editor to set Group Profiles up under Windows 9x/Me.
-It can be found on the Original full product Win98 installation CD under
-<tt>tools/reskit/netadmin/poledit</tt>. Install this using the
-Add/Remove Programs facility and then click on the 'Have Disk' tab.
-</p><p>
-Use the Group Policy Editor to create a policy file that specifies the location of
-user profiles and/or the <tt>My Documents</tt> etc. stuff. Then
-save these settings in a file called <tt>Config.POL</tt> that needs to
-be placed in the root of the [NETLOGON] share. If Win98 is configured to log onto
-the Samba Domain, it will automatically read this file and update the Win9x/Me registry
-of the machine as it logs on.
-</p><p>
-Further details are covered in the Win98 Resource Kit documentation.
-</p><p>
-If you do not take the right steps, then every so often Win9x/Me will check the
-integrity of the registry and will restore it's settings from the back-up
-copy of the registry it stores on each Win9x/Me machine. Hence, you will
-occasionally notice things changing back to the original settings.
-</p><p>
-Install the group policy handler for Win9x to pick up group policies. Look on the
-Win98 CD in <tt>\tools\reskit\netadmin\poledit</tt>.
-Install group policies on a Win9x client by double-clicking
-<tt>grouppol.inf</tt>. Log off and on again a couple of times and see
-if Win98 picks up group policies. Unfortunately this needs to be done on every
-Win9x/Me machine that uses group policies.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2878014"></a>Windows NT4 Style Policy Files</h3></div></div><p>
-To create or edit <tt>ntconfig.pol</tt> you must use the NT Server
-Policy Editor, <b>poledit.exe</b> which is included with NT4 Server
-but <span class="emphasis"><em>not NT Workstation</em></span>. There is a Policy Editor on a NT4
-Workstation but it is not suitable for creating <span class="emphasis"><em>Domain Policies</em></span>.
-Further, although the Windows 95 Policy Editor can be installed on an NT4
-Workstation/Server, it will not work with NT clients. However, the files from
-the NT Server will run happily enough on an NT4 Workstation.
-</p><p>
-You need <tt>poledit.exe, common.adm</tt> and <tt>winnt.adm</tt>.
-It is convenient to put the two *.adm files in the <tt>c:\winnt\inf</tt>
-directory which is where the binary will look for them unless told otherwise. Note also that that
-directory is normally 'hidden'.
-</p><p>
-The Windows NT policy editor is also included with the Service Pack 3 (and
-later) for Windows NT 4.0. Extract the files using <b>servicepackname /x</b>,
-i.e. that's <b>Nt4sp6ai.exe /x</b> for service pack 6a. The policy editor,
-<b>poledit.exe</b> and the associated template files (*.adm) should
-be extracted as well. It is also possible to downloaded the policy template
-files for Office97 and get a copy of the policy editor. Another possible
-location is with the Zero Administration Kit available for download from Microsoft.
-</p><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2878116"></a>Registry Tattoos</h4></div></div><p>
- With NT4 style registry based policy changes, a large number of settings are not
- automatically reversed as the user logs off. Since the settings that were in the
- NTConfig.POL file were applied to the client machine registry and that apply to the
- hive key HKEY_LOCAL_MACHINE are permanent until explicitly reversed. This is known
- as tattooing. It can have serious consequences down-stream and the administrator must
- be extremely careful not to lock out the ability to manage the machine at a later date.
- </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2878140"></a>MS Windows 200x / XP Professional Policies</h3></div></div><p>
-Windows NT4 System policies allows setting of registry parameters specific to
-users, groups and computers (client workstations) that are members of the NT4
-style domain. Such policy file will work with MS Windows 2000 / XP clients also.
-</p><p>
-New to MS Windows 2000 Microsoft introduced a new style of group policy that confers
-a superset of capabilities compared with NT4 style policies. Obviously, the tool used
-to create them is different, and the mechanism for implementing them is much changed.
-</p><p>
-The older NT4 style registry based policies are known as <span class="emphasis"><em>Administrative Templates</em></span>
-in MS Windows 2000/XP Group Policy Objects (GPOs). The later includes ability to set various security
-configurations, enforce Internet Explorer browser settings, change and redirect aspects of the
-users' desktop (including: the location of <span class="emphasis"><em>My Documents</em></span> files (directory), as
-well as intrinsics of where menu items will appear in the Start menu). An additional new
-feature is the ability to make available particular software Windows applications to particular
-users and/or groups.
-</p><p>
-Remember: NT4 policy files are named <tt>NTConfig.POL</tt> and are stored in the root
-of the NETLOGON share on the domain controllers. A Windows NT4 user enters a username, a password
-and selects the domain name to which the logon will attempt to take place. During the logon
-process the client machine reads the NTConfig.POL file from the NETLOGON share on the authenticating
-server, modifies the local registry values according to the settings in this file.
-</p><p>
-Windows 2K GPOs are very feature rich. They are NOT stored in the NETLOGON share, rather part of
-a Windows 200x policy file is stored in the Active Directory itself and the other part is stored
-in a shared (and replicated) volume called the SYSVOL folder. This folder is present on all Active
-Directory domain controllers. The part that is stored in the Active Directory itself is called the
-group policy container (GPC), and the part that is stored in the replicated share called SYSVOL is
-known as the group policy template (GPT).
-</p><p>
-With NT4 clients the policy file is read and executed upon only as each user logs onto the network.
-MS Windows 200x policies are much more complex - GPOs are processed and applied at client machine
-startup (machine specific part) and when the user logs onto the network the user specific part
-is applied. In MS Windows 200x style policy management each machine and/or user may be subject
-to any number of concurently applicable (and applied) policy sets (GPOs). Active Directory allows
-the administrator to also set filters over the policy settings. No such equivalent capability
-exists with NT4 style policy files.
-</p><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2878237"></a>Administration of Win2K / XP Policies</h4></div><div><h4 class="title"><a name="id2878237"></a>Administration of Win2K / XP Policies</h4></div></div><p>
-Instead of using the tool called &quot;The System Policy Editor&quot;, commonly called Poledit (from the
-executable name poledit.exe), GPOs are created and managed using a Microsoft Management Console
-(MMC) snap-in as follows:</p><div class="procedure"><ol type="1"><li><p>
-Go to the Windows 200x / XP menu <tt>Start-&gt;Programs-&gt;Administrative Tools</tt>
- and select the MMC snap-in called &quot;Active Directory Users and Computers&quot;
-</p></li><li><p>
-Select the domain or organizational unit (OU) that you wish to manage, then right click
-to open the context menu for that object, select the properties item.
-</p></li><li><p>
-Now left click on the Group Policy tab, then left click on the New tab. Type a name
-for the new policy you will create.
-</p></li><li><p>
-Now left click on the Edit tab to commence the steps needed to create the GPO.
-</p></li></ol></div><p>
-All policy configuration options are controlled through the use of policy administrative
-templates. These files have a .adm extension, both in NT4 as well as in Windows 200x / XP.
-Beware however, since the .adm files are NOT interchangible across NT4 and Windows 200x.
-The later introduces many new features as well as extended definition capabilities. It is
-well beyond the scope of this documentation to explain how to program .adm files, for that
-the adminsitrator is referred to the Microsoft Windows Resource Kit for your particular
-version of MS Windows.
-</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-The MS Windows 2000 Resource Kit contains a tool called gpolmig.exe. This tool can be used
-to migrate an NT4 NTConfig.POL file into a Windows 200x style GPO. Be VERY careful how you
-use this powerful tool. Please refer to the resource kit manuals for specific usage information.
-</p></div></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2878344"></a>Managing Account/User Policies</h2></div></div><p>
-Policies can define a specific user's settings or the settings for a group of users. The resulting
-policy file contains the registry settings for all users, groups, and computers that will be using
-the policy file. Separate policy files for each user, group, or computer are not not necessary.
-</p><p>
-If you create a policy that will be automatically downloaded from validating domain controllers,
-you should name the file NTconfig.POL. As system administrator, you have the option of renaming the
-policy file and, by modifying the Windows NT-based workstation, directing the computer to update
-the policy from a manual path. You can do this by either manually changing the registry or by using
-the System Policy Editor. This path can even be a local path such that each machine has its own policy file,
-but if a change is necessary to all machines, this change must be made individually to each workstation.
-</p><p>
-When a Windows NT4/200x/XP machine logs onto the network the NETLOGON share on the authenticating domain
-controller for the presence of the NTConfig.POL file. If one exists it is downloaded, parsed and then
-applied to the user's part of the registry.
-</p><p>
-MS Windows 200x/XP clients that log onto an MS Windows Active Directory security domain may additionally,
-acquire policy settings through Group Policy Objects (GPOs) that are defined and stored in Active Directory
-itself. The key benefit of using AS GPOs is that they impose no registry <span class="emphasis"><em>tatooing</em></span> effect.
-This has considerable advanage compared with the use of NTConfig.POL (NT4) style policy updates.
-</p><p>
-In addition to user access controls that may be imposed or applied via system and/or group policies
-in a manner that works in conjunction with user profiles, the user management environment under
-MS Windows NT4/200x/XP allows per domain as well as per user account restrictions to be applied.
-Common restrictions that are frequently used includes:
-</p><p>
-</p><table class="simplelist" border="0" summary="Simple list"><tr><td>Logon Hours</td></tr><tr><td>Password Aging</td></tr><tr><td>Permitted Logon from certain machines only</td></tr><tr><td>Account type (Local or Global)</td></tr><tr><td>User Rights</td></tr></table><p>
-</p><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2878457"></a>With Windows NT4/200x</h3></div></div><p>
-The tools that may be used to configure these types of controls from the MS Windows environment are:
-The NT4 User Manager for domains, the NT4 System and Group Policy Editor, the registry editor (regedt32.exe).
-Under MS Windows 200x/XP this is done using the Microsoft Managment Console (MMC) with approapriate
-&quot;snap-ins&quot;, the registry editor, and potentially also the NT4 System and Group Policy Editor.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2878478"></a>With a Samba PDC</h3></div></div><p>
-With a Samba Domain Controller, the new tools for managing of user account and policy information includes:
-<tt>smbpasswd, pdbedit, net, rpcclient.</tt>. The administrator should read the
-man pages for these tools and become familiar with their use.
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2878502"></a>System Startup and Logon Processing Overview</h2></div></div><p>
-The following attempts to document the order of processing of system and user policies following a system
-reboot and as part of the user logon:
-</p><div class="orderedlist"><ol type="1"><li><p>
- Network starts, then Remote Procedure Call System Service (RPCSS) and Multiple Universal Naming
- Convention Provider (MUP) start
- </p></li><li><p>
- Where Active Directory is involved, an ordered list of Group Policy Objects (GPOs) is downloaded
- and applied. The list may include GPOs that:
-</p><table class="simplelist" border="0" summary="Simple list"><tr><td>Apply to the location of machines in a Directory</td></tr><tr><td>Apply only when settings have changed</td></tr><tr><td>Depend on configuration of scope of applicability: local, site, domain, organizational unit, etc.</td></tr></table><p>
- No desktop user interface is presented until the above have been processed.
- </p></li><li><p>
- Execution of start-up scripts (hidden and synchronous by defaut).
- </p></li><li><p>
- A keyboard action to affect start of logon (Ctrl-Alt-Del).
- </p></li><li><p>
- User credentials are validated, User profile is loaded (depends on policy settings).
- </p></li><li><p>
- An ordered list of User GPOs is obtained. The list contents depends on what is configured in respsect of:
-
-</p><table class="simplelist" border="0" summary="Simple list"><tr><td>Is user a domain member, thus subject to particular policies</td></tr><tr><td>Loopback enablement, and the state of the loopback policy (Merge or Replace)</td></tr><tr><td>Location of the Active Directory itself</td></tr><tr><td>Has the list of GPOs changed. No processing is needed if not changed.</td></tr></table><p>
- </p></li><li><p>
- User Policies are applied from Active Directory. Note: There are several types.
- </p></li><li><p>
- Logon scripts are run. New to Win2K and Active Directory, logon scripts may be obtained based on Group
- Policy objects (hidden and executed synchronously). NT4 style logon scripts are then run in a normal
- window.
- </p></li><li><p>
- The User Interface as determined from the GPOs is presented. Note: In a Samba domain (like and NT4
- Domain) machine (system) policies are applied at start-up, User policies are applied at logon.
- </p></li></ol></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="ProfileMgmt"></a>Chapter18.Desktop Profile Management</h2></div><div><div class="author"><h3 class="author">John H. Terpstra</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt>&lt;<a href="mailto:jht@samba.org">jht@samba.org</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate">April 3 2003</p></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2877599">Roaming Profiles</a></dt><dd><dl><dt><a href="#id2877483">Samba Configuration for Profile Handling</a></dt><dt><a href="#id2879080">Windows Client Profile Configuration Information</a></dt><dt><a href="#id2879695">Sharing Profiles between W9x/Me and NT4/200x/XP workstations</a></dt><dt><a href="#id2879742">Profile Migration from Windows NT4/200x Server to Samba</a></dt></dl></dd><dt><a href="#id2879925">Mandatory profiles</a></dt><dt><a href="#id2879970">Creating/Managing Group Profiles</a></dt><dt><a href="#id2880011">Default Profile for Windows Users</a></dt><dd><dl><dt><a href="#id2880040">MS Windows 9x/Me</a></dt><dt><a href="#id2880129">MS Windows NT4 Workstation</a></dt><dt><a href="#id2880513">MS Windows 200x/XP</a></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2877599"></a>Roaming Profiles</h2></div></div><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p>
-Roaming profiles support is different for Win9x / Me and Windows NT4/200x.
-</p></div><p>
-Before discussing how to configure roaming profiles, it is useful to see how
-Windows 9x / Me and Windows NT4/200x clients implement these features.
-</p><p>
-Windows 9x / Me clients send a NetUserGetInfo request to the server to get the user's
-profiles location. However, the response does not have room for a separate
-profiles location field, only the user's home share. This means that Win9X/Me
-profiles are restricted to being stored in the user's home directory.
-</p><p>
-Windows NT4/200x clients send a NetSAMLogon RPC request, which contains many fields,
-including a separate field for the location of the user's profiles.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2877483"></a>Samba Configuration for Profile Handling</h3></div></div><p>
-This section documents how to configure Samba for MS Windows client profile support.
-</p><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2877497"></a>NT4/200x User Profiles</h4></div></div><p>
-To support Windowns NT4/200x clients, in the [global] section of smb.conf set the
-following (for example):
-</p><p>
-</p><pre class="programlisting">
- logon path = \\profileserver\profileshare\profilepath\%U\moreprofilepath
-</pre><p>
-
- This is typically implemented like:
-
-</p><pre class="programlisting">
- logon path = \\%L\Profiles\%u
-</pre><p>
-where %L translates to the name of the Samba server and %u translates to the user name
-</p><p>
-The default for this option is \\%N\%U\profile, namely \\sambaserver\username\profile.
-The \\N%\%U service is created automatically by the [homes] service. If you are using
-a samba server for the profiles, you _must_ make the share specified in the logon path
-browseable. Please refer to the man page for smb.conf in respect of the different
-symantics of %L and %N, as well as %U and %u.
-</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-MS Windows NT/2K clients at times do not disconnect a connection to a server
-between logons. It is recommended to NOT use the <b>homes</b>
-meta-service name as part of the profile share path.
-</p></div></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2878824"></a>Windows 9x / Me User Profiles</h4></div></div><p>
-To support Windows 9x / Me clients, you must use the &quot;logon home&quot; parameter. Samba has
-now been fixed so that <b><tt>net use /home</tt></b> now works as well, and it, too, relies
-on the <b>logon home</b> parameter.
-</p><p>
-By using the logon home parameter, you are restricted to putting Win9x / Me
-profiles in the user's home directory. But wait! There is a trick you
-can use. If you set the following in the <b>[global]</b> section of your <tt>smb.conf</tt> file:
-</p><pre class="programlisting">
- logon home = \\%L\%U\.profiles
-</pre><p>
-then your Windows 9x / Me clients will dutifully put their clients in a subdirectory
-of your home directory called <tt>.profiles</tt> (thus making them hidden).
-</p><p>
-Not only that, but <b><tt>net use /home</tt></b> will also work, because of a feature in
-Windows 9x / Me. It removes any directory stuff off the end of the home directory area
-and only uses the server and share portion. That is, it looks like you
-specified \\%L\%U for <b>logon home</b>.
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2878920"></a>Mixed Windows 9x / Me and Windows NT4/200x User Profiles</h4></div></div><p>
-You can support profiles for both Win9X and WinNT clients by setting both the
-<b>logon home</b> and <b>logon path</b> parameters. For example:
-</p><pre class="programlisting">
- logon home = \\%L\%u\.profiles
- logon path = \\%L\profiles\%u
-</pre></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2878959"></a>Disabling Roaming Profile Support</h4></div></div><p>
-A question often asked is &quot;How may I enforce use of local profiles?&quot; or
-&quot;How do I disable Roaming Profiles?&quot;
-</p><p>
-There are three ways of doing this:
-</p><div class="itemizedlist"><ul type="disc"><li><p>
- <b>In smb.conf:</b> affect the following settings and ALL clients
- will be forced to use a local profile:
- </p><pre class="programlisting">
- logon home =
- logon path =
- </pre></li><li><p>
- <b>MS Windows Registry:</b> by using the Microsoft Management Console
- gpedit.msc to instruct your MS Windows XP machine to use only a local profile. This
- of course modifies registry settings. The full path to the option is:
- </p><pre class="programlisting">
- Local Computer Policy\
- Computer Configuration\
- Administrative Templates\
- System\
- User Profiles\
-
- Disable: Only Allow Local User Profiles
- Disable: Prevent Roaming Profile Change from Propogating to the Server
- </pre><p>
- </p></li><li><p>
- <b>Change of Profile Type:</b> From the start menu right click on the
- MY Computer icon, select <span class="emphasis"><em>Properties</em></span>, click on the &quot;<span class="emphasis"><em>User Profiles</em></span>
- tab, select the profile you wish to change from Roaming type to Local, click <span class="emphasis"><em>Change Type</em></span>.
- </p></li></ul></div><p>
-Consult the MS Windows registry guide for your particular MS Windows version for more
-information about which registry keys to change to enforce use of only local user
-profiles.
-</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-The specifics of how to convert a local profile to a roaming profile, or a roaming profile
-to a local one vary according to the version of MS Windows you are running. Consult the
-Microsoft MS Windows Resource Kit for your version of Windows for specific information.
-</p></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2879080"></a>Windows Client Profile Configuration Information</h3></div></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2879088"></a>Windows 9x / Me Profile Setup</h4></div></div><p>
-When a user first logs in on Windows 9X, the file user.DAT is created,
-as are folders &quot;Start Menu&quot;, &quot;Desktop&quot;, &quot;Programs&quot; and &quot;Nethood&quot;.
-These directories and their contents will be merged with the local
-versions stored in c:\windows\profiles\username on subsequent logins,
-taking the most recent from each. You will need to use the [global]
-options &quot;preserve case = yes&quot;, &quot;short preserve case = yes&quot; and
-&quot;case sensitive = no&quot; in order to maintain capital letters in shortcuts
-in any of the profile folders.
-</p><p>
-The user.DAT file contains all the user's preferences. If you wish to
-enforce a set of preferences, rename their user.DAT file to user.MAN,
-and deny them write access to this file.
-</p><div class="orderedlist"><ol type="1"><li><p>
- On the Windows 9x / Me machine, go to Control Panel -&gt; Passwords and
- select the User Profiles tab. Select the required level of
- roaming preferences. Press OK, but do _not_ allow the computer
- to reboot.
- </p></li><li><p>
- On the Windows 9x / Me machine, go to Control Panel -&gt; Network -&gt;
- Client for Microsoft Networks -&gt; Preferences. Select 'Log on to
- NT Domain'. Then, ensure that the Primary Logon is 'Client for
- Microsoft Networks'. Press OK, and this time allow the computer
- to reboot.
- </p></li></ol></div><p>
-Under Windows 9x / Me Profiles are downloaded from the Primary Logon.
-If you have the Primary Logon as 'Client for Novell Networks', then
-the profiles and logon script will be downloaded from your Novell
-Server. If you have the Primary Logon as 'Windows Logon', then the
-profiles will be loaded from the local machine - a bit against the
-concept of roaming profiles, it would seem!
-</p><p>
-You will now find that the Microsoft Networks Login box contains
-[user, password, domain] instead of just [user, password]. Type in
-the samba server's domain name (or any other domain known to exist,
-but bear in mind that the user will be authenticated against this
-domain and profiles downloaded from it, if that domain logon server
-supports it), user name and user's password.
-</p><p>
-Once the user has been successfully validated, the Windows 9x / Me machine
-will inform you that 'The user has not logged on before' and asks you
-if you wish to save the user's preferences? Select 'yes'.
-</p><p>
-Once the Windows 9x / Me client comes up with the desktop, you should be able
-to examine the contents of the directory specified in the &quot;logon path&quot;
-on the samba server and verify that the &quot;Desktop&quot;, &quot;Start Menu&quot;,
-&quot;Programs&quot; and &quot;Nethood&quot; folders have been created.
-</p><p>
-These folders will be cached locally on the client, and updated when
-the user logs off (if you haven't made them read-only by then).
-You will find that if the user creates further folders or short-cuts,
-that the client will merge the profile contents downloaded with the
-contents of the profile directory already on the local client, taking
-the newest folders and short-cuts from each set.
-</p><p>
-If you have made the folders / files read-only on the samba server,
-then you will get errors from the Windows 9x / Me machine on logon and logout, as
-it attempts to merge the local and the remote profile. Basically, if
-you have any errors reported by the Windows 9x / Me machine, check the Unix file
-permissions and ownership rights on the profile directory contents,
-on the samba server.
-</p><p>
-If you have problems creating user profiles, you can reset the user's
-local desktop cache, as shown below. When this user then next logs in,
-they will be told that they are logging in &quot;for the first time&quot;.
-</p><div class="orderedlist"><ol type="1"><li><p>
- instead of logging in under the [user, password, domain] dialog,
- press escape.
- </p></li><li><p>
- run the regedit.exe program, and look in:
- </p><p>
- HKEY_LOCAL_MACHINE\Windows\CurrentVersion\ProfileList
- </p><p>
- you will find an entry, for each user, of ProfilePath. Note the
- contents of this key (likely to be c:\windows\profiles\username),
- then delete the key ProfilePath for the required user.
-
- [Exit the registry editor].
-
- </p></li><li><p>
- <span class="emphasis"><em>WARNING</em></span> - before deleting the contents of the
- directory listed in the ProfilePath (this is likely to be
- <tt>c:\windows\profiles\username)</tt>, ask them if they
- have any important files stored on their desktop or in their start menu.
- Delete the contents of the directory ProfilePath (making a backup if any
- of the files are needed).
- </p><p>
- This will have the effect of removing the local (read-only hidden
- system file) user.DAT in their profile directory, as well as the
- local &quot;desktop&quot;, &quot;nethood&quot;, &quot;start menu&quot; and &quot;programs&quot; folders.
- </p></li><li><p>
- search for the user's .PWL password-caching file in the c:\windows
- directory, and delete it.
- </p></li><li><p>
- log off the windows 9x / Me client.
- </p></li><li><p>
- check the contents of the profile path (see &quot;logon path&quot; described
- above), and delete the user.DAT or user.MAN file for the user,
- making a backup if required.
- </p></li></ol></div><p>
-If all else fails, increase samba's debug log levels to between 3 and 10,
-and / or run a packet trace program such as ethereal or netmon.exe, and
-look for error messages.
-</p><p>
-If you have access to an Windows NT4/200x server, then first set up roaming profiles
-and / or netlogons on the Windows NT4/200x server. Make a packet trace, or examine
-the example packet traces provided with Windows NT4/200x server, and see what the
-differences are with the equivalent samba trace.
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2879358"></a>Windows NT4 Workstation</h4></div></div><p>
-When a user first logs in to a Windows NT Workstation, the profile
-NTuser.DAT is created. The profile location can be now specified
-through the &quot;logon path&quot; parameter.
-</p><p>
-There is a parameter that is now available for use with NT Profiles:
-&quot;logon drive&quot;. This should be set to <tt>H:</tt> or any other drive, and
-should be used in conjunction with the new &quot;logon home&quot; parameter.
-</p><p>
-The entry for the NT4 profile is a _directory_ not a file. The NT
-help on profiles mentions that a directory is also created with a .PDS
-extension. The user, while logging in, must have write permission to
-create the full profile path (and the folder with the .PDS extension
-for those situations where it might be created.)
-</p><p>
-In the profile directory, Windows NT4 creates more folders than Windows 9x / Me.
-It creates &quot;Application Data&quot; and others, as well as &quot;Desktop&quot;, &quot;Nethood&quot;,
-&quot;Start Menu&quot; and &quot;Programs&quot;. The profile itself is stored in a file
-NTuser.DAT. Nothing appears to be stored in the .PDS directory, and
-its purpose is currently unknown.
-</p><p>
-You can use the System Control Panel to copy a local profile onto
-a samba server (see NT Help on profiles: it is also capable of firing
-up the correct location in the System Control Panel for you). The
-NT Help file also mentions that renaming NTuser.DAT to NTuser.MAN
-turns a profile into a mandatory one.
-</p><p>
-The case of the profile is significant. The file must be called
-NTuser.DAT or, for a mandatory profile, NTuser.MAN.
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2879426"></a>Windows 2000/XP Professional</h4></div></div><p>
-You must first convert the profile from a local profile to a domain
-profile on the MS Windows workstation as follows:
-</p><div class="itemizedlist"><ul type="disc"><li><p>
- Log on as the LOCAL workstation administrator.
- </p></li><li><p>
- Right click on the 'My Computer' Icon, select 'Properties'
- </p></li><li><p>
- Click on the 'User Profiles' tab
- </p></li><li><p>
- Select the profile you wish to convert (click on it once)
- </p></li><li><p>
- Click on the button 'Copy To'
- </p></li><li><p>
- In the &quot;Permitted to use&quot; box, click on the 'Change' button.
- </p></li><li><p>
- Click on the 'Look in&quot; area that lists the machine name, when you click
- here it will open up a selection box. Click on the domain to which the
- profile must be accessible.
- </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>You will need to log on if a logon box opens up. Eg: In the connect
- as: MIDEARTH\root, password: mypassword.</p></div></li><li><p>
- To make the profile capable of being used by anyone select 'Everyone'
- </p></li><li><p>
- Click OK. The Selection box will close.
- </p></li><li><p>
- Now click on the 'Ok' button to create the profile in the path you
- nominated.
- </p></li></ul></div><p>
-Done. You now have a profile that can be editted using the samba-3.0.0
-<tt>profiles</tt> tool.
-</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-Under NT/2K the use of mandotory profiles forces the use of MS Exchange
-storage of mail data. That keeps desktop profiles usable.
-</p></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><div class="itemizedlist"><ul type="disc"><li><p>
-This is a security check new to Windows XP (or maybe only
-Windows XP service pack 1). It can be disabled via a group policy in
-Active Directory. The policy is:</p><p>&quot;Computer Configuration\Administrative Templates\System\User
-Profiles\Do not check for user ownership of Roaming Profile Folders&quot;</p><p>...and it should be set to &quot;Enabled&quot;.
-Does the new version of samba have an Active Directory analogue? If so,
-then you may be able to set the policy through this.
-</p><p>
-If you cannot set group policies in samba, then you may be able to set
-the policy locally on each machine. If you want to try this, then do
-the following (N.B. I don't know for sure that this will work in the
-same way as a domain group policy):
-</p></li><li><p>
-On the XP workstation log in with an Administrator account.
-</p></li><li><p>Click: &quot;Start&quot;, &quot;Run&quot;</p></li><li><p>Type: &quot;mmc&quot;</p></li><li><p>Click: &quot;OK&quot;</p></li><li><p>A Microsoft Management Console should appear.</p></li><li><p>Click: File, &quot;Add/Remove Snap-in...&quot;, &quot;Add&quot;</p></li><li><p>Double-Click: &quot;Group Policy&quot;</p></li><li><p>Click: &quot;Finish&quot;, &quot;Close&quot;</p></li><li><p>Click: &quot;OK&quot;</p></li><li><p>In the &quot;Console Root&quot; window:</p></li><li><p>Expand: &quot;Local Computer Policy&quot;, &quot;Computer Configuration&quot;,</p></li><li><p>&quot;Administrative Templates&quot;, &quot;System&quot;, &quot;User Profiles&quot;</p></li><li><p>Double-Click: &quot;Do not check for user ownership of Roaming Profile</p></li><li><p>Folders&quot;</p></li><li><p>Select: &quot;Enabled&quot;</p></li><li><p>Click: OK&quot;</p></li><li><p>Close the whole console. You do not need to save the settings (this
- refers to the console settings rather than the policies you have
- changed).</p></li><li><p>Reboot</p></li></ul></div></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2879695"></a>Sharing Profiles between W9x/Me and NT4/200x/XP workstations</h3></div></div><p>
-Sharing of desktop profiles between Windows versions is NOT recommended.
-Desktop profiles are an evolving phenomenon and profiles for later versions
-of MS Windows clients add features that may interfere with earlier versions
-of MS Windows clients. Probably the more salient reason to NOT mix profiles
-is that when logging off an earlier version of MS Windows the older format
-of profile contents may overwrite information that belongs to the newer
-version resulting in loss of profile information content when that user logs
-on again with the newer version of MS Windows.
-</p><p>
-If you then want to share the same Start Menu / Desktop with W9x/Me, you will
-need to specify a common location for the profiles. The smb.conf parameters
-that need to be common are <span class="emphasis"><em>logon path</em></span> and
-<span class="emphasis"><em>logon home</em></span>.
-</p><p>
-If you have this set up correctly, you will find separate user.DAT and
-NTuser.DAT files in the same profile directory.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2879742"></a>Profile Migration from Windows NT4/200x Server to Samba</h3></div></div><p>
-There is nothing to stop you specifying any path that you like for the
-location of users' profiles. Therefore, you could specify that the
-profile be stored on a samba server, or any other SMB server, as long as
-that SMB server supports encrypted passwords.
-</p><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2879759"></a>Windows NT4 Profile Management Tools</h4></div></div><p>
-Unfortunately, the Resource Kit information is specific to the version of MS Windows
-NT4/200x. The correct resource kit is required for each platform.
-</p><p>
-Here is a quick guide:
-</p><div class="itemizedlist"><ul type="disc"><li><p>
-On your NT4 Domain Controller, right click on 'My Computer', then
-select the tab labelled 'User Profiles'.
-</p></li><li><p>
-Select a user profile you want to migrate and click on it.
-</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>I am using the term &quot;migrate&quot; lossely. You can copy a profile to
-create a group profile. You can give the user 'Everyone' rights to the
-profile you copy this to. That is what you need to do, since your samba
-domain is not a member of a trust relationship with your NT4 PDC.</p></div></li><li><p>Click the 'Copy To' button.</p></li><li><p>In the box labelled 'Copy Profile to' add your new path, eg:
- <tt>c:\temp\foobar</tt></p></li><li><p>Click on the button labelled 'Change' in the &quot;Permitted to use&quot; box.</p></li><li><p>Click on the group 'Everyone' and then click OK. This closes the
- 'chose user' box.</p></li><li><p>Now click OK.</p></li></ul></div><p>
-Follow the above for every profile you need to migrate.
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2879852"></a>Side bar Notes</h4></div></div><p>
-You should obtain the SID of your NT4 domain. You can use smbpasswd to do
-this. Read the man page.</p><p>
-With Samba-3.0.0 alpha code you can import all you NT4 domain accounts
-using the net samsync method. This way you can retain your profile
-settings as well as all your users.
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2879874"></a>moveuser.exe</h4></div></div><p>
-The W2K professional resource kit has moveuser.exe. moveuser.exe changes
-the security of a profile from one user to another. This allows the account
-domain to change, and/or the user name to change.
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2879890"></a>Get SID</h4></div></div><p>
-You can identify the SID by using GetSID.exe from the Windows NT Server 4.0
-Resource Kit.
-</p><p>
-Windows NT 4.0 stores the local profile information in the registry under
-the following key:
-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList
-</p><p>
-Under the ProfileList key, there will be subkeys named with the SIDs of the
-users who have logged on to this computer. (To find the profile information
-for the user whose locally cached profile you want to move, find the SID for
-the user with the GetSID.exe utility.) Inside of the appropriate user's
-subkey, you will see a string value named ProfileImagePath.
-</p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2879925"></a>Mandatory profiles</h2></div></div><p>
-A Mandatory Profile is a profile that the user does NOT have the ability to overwrite.
-During the user's session it may be possible to change the desktop environment, but
-as the user logs out all changes made will be lost. If it is desired to NOT allow the
-user any ability to change the desktop environment then this must be done through
-policy settings. See previous chapter.
-</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-Under NO circumstances should the profile directory (or it's contents) be made read-only
-as this may render the profile un-usable.
-</p></div><p>
-For MS Windows NT4/200x/XP the above method can be used to create mandatory profiles
-also. To convert a group profile into a mandatory profile simply locate the NTUser.DAT
-file in the copied profile and rename it to NTUser.MAN.
-</p><p>
-For MS Windows 9x / Me it is the User.DAT file that must be renamed to User.MAN to
-affect a mandatory profile.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2879970"></a>Creating/Managing Group Profiles</h2></div></div><p>
-Most organisations are arranged into departments. There is a nice benenfit in
-this fact since usually most users in a department will require the same desktop
-applications and the same desktop layout. MS Windows NT4/200x/XP will allow the
-use of Group Profiles. A Group Profile is a profile that is created firstly using
-a template (example) user. Then using the profile migration tool (see above) the
-profile is assigned access rights for the user group that needs to be given access
-to the group profile.
-</p><p>
-The next step is rather important. PLEASE NOTE: Instead of assigning a group profile
-to users (ie: Using User Manager) on a &quot;per user&quot; basis, the group itself is assigned
-the now modified profile.
-</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
- Be careful with group profiles, if the user who is a member of a group also
- has a personal profile, then the result will be a fusion (merge) of the two.
- </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2880011"></a>Default Profile for Windows Users</h2></div></div><p>
-MS Windows 9x / Me and NT4/200x/XP will use a default profile for any user for whom
-a profile does not already exist. Armed with a knowledge of where the default profile
-is located on the Windows workstation, and knowing which registry keys affect the path
-from which the default profile is created, it is possible to modify the default profile
-to one that has been optimised for the site. This has significant administrative
-advantages.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2880040"></a>MS Windows 9x/Me</h3></div></div><p>
-To enable default per use profiles in Windows 9x / Me you can either use the Windows 98 System
-Policy Editor or change the registry directly.
-</p><p>
-To enable default per user profiles in Windows 9x / Me, launch the System Policy Editor, then
-select File -&gt; Open Registry, then click on the Local Computer icon, click on Windows 98 System,
-select User Profiles, click on the enable box. Do not forget to save the registry changes.
-</p><p>
-To modify the registry directly, launch the Registry Editor (regedit.exe), select the hive
-<tt>HKEY_LOCAL_MACHINE\Network\Logon</tt>. Now add a DWORD type key with the name
-&quot;User Profiles&quot;, to enable user profiles set the value to 1, to disable user profiles set it to 0.
-</p><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2880080"></a>How User Profiles Are Handled in Windows 9x / Me?</h4></div></div><p>
-When a user logs on to a Windows 9x / Me machine, the local profile path,
-<tt>HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\ProfileList</tt>, is checked
-for an existing entry for that user:
-</p><p>
-If the user has an entry in this registry location, Windows 9x / Me checks for a locally cached
-version of the user profile. Windows 9x / Me also checks the user's home directory (or other
-specified directory if the location has been modified) on the server for the User Profile.
-If a profile exists in both locations, the newer of the two is used. If the User Profile exists
-on the server, but does not exist on the local machine, the profile on the server is downloaded
-and used. If the User Profile only exists on the local machine, that copy is used.
-</p><p>
-If a User Profile is not found in either location, the Default User Profile from the Windows 9x / Me
-machine is used and is copied to a newly created folder for the logged on user. At log off, any
-changes that the user made are written to the user's local profile. If the user has a roaming
-profile, the changes are written to the user's profile on the server.
-</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2880129"></a>MS Windows NT4 Workstation</h3></div></div><p>
-On MS Windows NT4 the default user profile is obtained from the location
-<tt>%SystemRoot%\Profiles</tt> which in a default installation will translate to
-<tt>C:\WinNT\Profiles</tt>. Under this directory on a clean install there will be
-three (3) directories: <tt>Administrator, All Users, Default User</tt>.
-</p><p>
-The <tt>All Users</tt> directory contains menu settings that are common across all
-system users. The <tt>Default User</tt> directory contains menu entries that are
-customisable per user depending on the profile settings chosen/created.
-</p><p>
-When a new user first logs onto an MS Windows NT4 machine a new profile is created from:
-</p><table class="simplelist" border="0" summary="Simple list"><tr><td>All Users settings</td></tr><tr><td>Default User settings (contains the default NTUser.DAT file)</td></tr></table><p>
-When a user logs onto an MS Windows NT4 machine that is a member of a Microsoft security domain
-the following steps are followed in respect of profile handling:
-</p><div class="orderedlist"><ol type="1"><li><p>
- The users' account information which is obtained during the logon process contains
- the location of the users' desktop profile. The profile path may be local to the
- machine or it may be located on a network share. If there exists a profile at the location
- of the path from the user account, then this profile is copied to the location
- <tt>%SystemRoot%\Profiles\%USERNAME%</tt>. This profile then inherits the
- settings in the <tt>All Users</tt> profile in the <tt>%SystemRoot%\Profiles</tt>
- location.
- </p></li><li><p>
- If the user account has a profile path, but at it's location a profile does not exist,
- then a new profile is created in the <tt>%SystemRoot%\Profiles\%USERNAME%</tt>
- directory from reading the <tt>Default User</tt> profile.
- </p></li><li><p>
- If the NETLOGON share on the authenticating server (logon server) contains a policy file
- (<tt>NTConfig.POL</tt>) then it's contents are applied to the <tt>NTUser.DAT</tt>
- which is applied to the <tt>HKEY_CURRENT_USER</tt> part of the registry.
- </p></li><li><p>
- When the user logs out, if the profile is set to be a roaming profile it will be written
- out to the location of the profile. The <tt>NTuser.DAT</tt> file is then
- re-created from the contents of the <tt>HKEY_CURRENT_USER</tt> contents.
- Thus, should there not exist in the NETLOGON share an <tt>NTConfig.POL</tt> at the
- next logon, the effect of the provious <tt>NTConfig.POL</tt> will still be held
- in the profile. The effect of this is known as <span class="emphasis"><em>tatooing</em></span>.
- </p></li></ol></div><p>
-MS Windows NT4 profiles may be <span class="emphasis"><em>Local</em></span> or <span class="emphasis"><em>Roaming</em></span>. A Local profile
-will stored in the <tt>%SystemRoot%\Profiles\%USERNAME%</tt> location. A roaming profile will
-also remain stored in the same way, unless the following registry key is created:
-</p><p>
-</p><pre class="programlisting">
- HKEY_LOCAL_MACHINE\SYSTEM\Software\Microsoft\Windows NT\CurrentVersion\winlogon\
- &quot;DeleteRoamingCache&quot;=dword:00000001
-</pre><p>
-
-In which case, the local copy (in <tt>%SystemRoot%\Profiles\%USERNAME%</tt>) will be
-deleted on logout.
-</p><p>
-Under MS Windows NT4 default locations for common resources (like <tt>My Documents</tt>
-may be redirected to a network share by modifying the following registry keys. These changes may be affected
-via use of the System Policy Editor (to do so may require that you create your owns template extension
-for the policy editor to allow this to be done through the GUI. Another way to do this is by way of first
-creating a default user profile, then while logged in as that user, run regedt32 to edit the key settings.
-</p><p>
-The Registry Hive key that affects the behaviour of folders that are part of the default user profile
-are controlled by entries on Windows NT4 is:
-</p><p>
-</p><pre class="programlisting">
- HKEY_CURRENT_USER
- \Software
- \Microsoft
- \Windows
- \CurrentVersion
- \Explorer
- \User Shell Folders\
-</pre><p>
-</p><p>
-The above hive key contains a list of automatically managed folders. The default entries are:
-</p><p>
- </p><pre class="programlisting">
- Name Default Value
- -------------- -----------------------------------------
- AppData %USERPROFILE%\Application Data
- Desktop %USERPROFILE%\Desktop
- Favorites %USERPROFILE%\Favorites
- NetHood %USERPROFILE%\NetHood
- PrintHood %USERPROFILE%\PrintHood
- Programs %USERPROFILE%\Start Menu\Programs
- Recent %USERPROFILE%\Recent
- SendTo %USERPROFILE%\SendTo
- Start Menu %USERPROFILE%\Start Menu
- Startup %USERPROFILE%\Start Menu\Programs\Startup
- </pre><p>
- </p><p>
-The registry key that contains the location of the default profile settings is:
-
-</p><pre class="programlisting">
- HKEY_LOCAL_MACHINE
- \SOFTWARE
- \Microsoft
- \Windows
- \CurrentVersion
- \Explorer
- \User Shell Folders
-</pre><p>
-
-The default entries are:
-
-</p><pre class="programlisting">
- Common Desktop %SystemRoot%\Profiles\All Users\Desktop
- Common Programs %SystemRoot%\Profiles\All Users\Programs
- Common Start Menu %SystemRoot%\Profiles\All Users\Start Menu
- Common Startup %SystemRoot%\Profiles\All Users\Start Menu\Progams\Startup
-</pre><p>
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2880513"></a>MS Windows 200x/XP</h3></div></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
- MS Windows XP Home Edition does use default per user profiles, but can not participate
- in domain security, can not log onto an NT/ADS style domain, and thus can obtain the profile
- only from itself. While there are benefits in doing this the beauty of those MS Windows
- clients that CAN participate in domain logon processes allows the administrator to create
- a global default profile and to enforce it through the use of Group Policy Objects (GPOs).
- </p></div><p>
-When a new user first logs onto MS Windows 200x/XP machine the default profile is obtained from
-<tt>C:\Documents and Settings\Default User</tt>. The administrator can modify (or change
-the contents of this location and MS Windows 200x/XP will gladly use it. This is far from the optimum
-arrangement since it will involve copying a new default profile to every MS Windows 200x/XP client
-workstation.
-</p><p>
-When MS Windows 200x/XP participate in a domain security context, and if the default user
-profile is not found, then the client will search for a default profile in the NETLOGON share
-of the authenticating server. ie: In MS Windows parlance:
-<tt>%LOGONSERVER%\NETLOGON\Default User</tt> and if one exits there it will copy this
-to the workstation to the <tt>C:\Documents and Settings\</tt> under the Windows
-login name of the user.
-</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
- This path translates, in Samba parlance, to the smb.conf [NETLOGON] share. The directory
- should be created at the root of this share and must be called <tt>Default Profile</tt>.
- </p></div><p>
-If a default profile does not exist in this location then MS Windows 200x/XP will use the local
-default profile.
-</p><p>
-On loging out, the users' desktop profile will be stored to the location specified in the registry
-settings that pertain to the user. If no specific policies have been created, or passed to the client
-during the login process (as Samba does automatically), then the user's profile will be written to
-the local machine only under the path <tt>C:\Documents and Settings\%USERNAME%</tt>.
-</p><p>
-Those wishing to modify the default behaviour can do so through three methods:
-</p><div class="itemizedlist"><ul type="disc"><li><p>
- Modify the registry keys on the local machine manually and place the new default profile in the
- NETLOGON share root - NOT recommended as it is maintenance intensive.
- </p></li><li><p>
- Create an NT4 style NTConfig.POL file that specified this behaviour and locate this file
- in the root of the NETLOGON share along with the new default profile.
- </p></li><li><p>
- Create a GPO that enforces this through Active Directory, and place the new default profile
- in the NETLOGON share.
- </p></li></ul></div><p>
-The Registry Hive key that affects the behaviour of folders that are part of the default user profile
-are controlled by entries on Windows 200x/XP is:
-</p><p>
-</p><pre class="programlisting">
- HKEY_CURRENT_USER
- \Software
- \Microsoft
- \Windows
- \CurrentVersion
- \Explorer
- \User Shell Folders\
-</pre><p>
-</p><p>
-The above hive key contains a list of automatically managed folders. The default entries are:
-</p><p>
- </p><pre class="programlisting">
- Name Default Value
- -------------- -----------------------------------------
- AppData %USERPROFILE%\Application Data
- Cache %USERPROFILE%\Local Settings\Temporary Internet Files
- Cookies %USERPROFILE%\Cookies
- Desktop %USERPROFILE%\Desktop
- Favorites %USERPROFILE%\Favorites
- History %USERPROFILE%\Local Settings\History
- Local AppData %USERPROFILE%\Local Settings\Application Data
- Local Settings %USERPROFILE%\Local Settings
- My Pictures %USERPROFILE%\My Documents\My Pictures
- NetHood %USERPROFILE%\NetHood
- Personal %USERPROFILE%\My Documents
- PrintHood %USERPROFILE%\PrintHood
- Programs %USERPROFILE%\Start Menu\Programs
- Recent %USERPROFILE%\Recent
- SendTo %USERPROFILE%\SendTo
- Start Menu %USERPROFILE%\Start Menu
- Startup %USERPROFILE%\Start Menu\Programs\Startup
- Templates %USERPROFILE%\Templates
- </pre><p>
- </p><p>
-There is also an entry called &quot;Default&quot; that has no value set. The default entry is of type REG_SZ, all
-the others are of type REG_EXPAND_SZ.
-</p><p>
-It makes a huge difference to the speed of handling roaming user profiles if all the folders are
-stored on a dedicated location on a network server. This means that it will NOT be necessary to
-write the Outlook PST file over the network for every login and logout.
-</p><p>
-To set this to a network location you could use the following examples:
-
-</p><pre class="programlisting">
- %LOGONSERVER%\%USERNAME%\Default Folders
-</pre><p>
-
-This would store the folders in the user's home directory under a directory called &quot;Default Folders&quot;
-
-You could also use:
-
-</p><pre class="programlisting">
- \\SambaServer\FolderShare\%USERNAME%
-</pre><p>
-
-in which case the default folders will be stored in the server named <span class="emphasis"><em>SambaServer</em></span>
-in the share called <span class="emphasis"><em>FolderShare</em></span> under a directory that has the name of the MS Windows
-user as seen by the Linux/Unix file system.
-</p><p>
-Please note that once you have created a default profile share, you MUST migrate a user's profile
-(default or custom) to it.
-</p><p>
-MS Windows 200x/XP profiles may be <span class="emphasis"><em>Local</em></span> or <span class="emphasis"><em>Roaming</em></span>.
-A roaming profile will be cached locally unless the following registry key is created:
-</p><p>
-</p><pre class="programlisting">
- HKEY_LOCAL_MACHINE\SYSTEM\Software\Microsoft\Windows NT\CurrentVersion\winlogon\
- &quot;DeleteRoamingCache&quot;=dword:00000001
-</pre><p>
-
-In which case, the local cache copy will be deleted on logout.
-</p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="InterdomainTrusts"></a>Chapter19.Interdomain Trust Relationships</h2></div><div><div class="author"><h3 class="author">John H. Terpstra</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt>&lt;<a href="mailto:jht@samba.org">jht@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author">Rafal Szczesniak</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt>&lt;<a href="mailto:mimir@samba.org">mimir@samba.org</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate">April 3, 2003</p></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2878684">Trust Relationship Background</a></dt><dt><a href="#id2881006">Native MS Windows NT4 Trusts Configuration</a></dt><dd><dl><dt><a href="#id2881019">NT4 as the Trusting Domain (ie. creating the trusted account)</a></dt><dt><a href="#id2881063">NT4 as the Trusted Domain (ie. creating trusted account's password)</a></dt></dl></dd><dt><a href="#id2881087">Configuring Samba NT-style Domain Trusts</a></dt><dd><dl><dt><a href="#id2881114">Samba-3 as the Trusting Domain</a></dt><dt><a href="#id2881210">Samba-3 as the Trusted Domain</a></dt></dl></dd></dl></div><p>
-Samba-3 supports NT4 style domain trust relationships. This is feature that many sites
-will want to use if they migrate to Samba-3 from and NT4 style domain and do NOT want to
-adopt Active Directory or an LDAP based authentication back end. This section explains
-some background information regarding trust relationships and how to create them. It is now
-possible for Samba-3 to NT4 trust (and vice versa), as well as Samba3 to Samba3 trusts.
-</p><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2878684"></a>Trust Relationship Background</h2></div></div><p>
-MS Windows NT3.x/4.0 type security domains employ a non-hierarchical security structure.
-The limitations of this architecture as it affects the scalability of MS Windows networking
-in large organisations is well known. Additionally, the flat-name space that results from
-this design significantly impacts the delegation of administrative responsibilities in
-large and diverse organisations.
-</p><p>
-Microsoft developed Active Directory Service (ADS), based on Kerberos and LDAP, as a means
-of circumventing the limitations of the older technologies. Not every organisation is ready
-or willing to embrace ADS. For small companies the older NT4 style domain security paradigm
-is quite adequate, there thus remains an entrenched user base for whom there is no direct
-desire to go through a disruptive change to adopt ADS.
-</p><p>
-Microsoft introduced with MS Windows NT the ability to allow differing security domains
-to affect a mechanism so that users from one domain may be given access rights and privileges
-in another domain. The language that describes this capability is couched in terms of
-<span class="emphasis"><em>Trusts</em></span>. Specifically, one domain will <span class="emphasis"><em>trust</em></span> the users
-from another domain. The domain from which users are available to another security domain is
-said to be a trusted domain. The domain in which those users have assigned rights and privileges
-is the trusting domain. With NT3.x/4.0 all trust relationships are always in one direction only,
-thus if users in both domains are to have privileges and rights in each others' domain, then it is
-necessary to establish two (2) relationships, one in each direction.
-</p><p>
-In an NT4 style MS security domain, all trusts are non-transitive. This means that if there
-are three (3) domains (let's call them RED, WHITE, and BLUE) where RED and WHITE have a trust
-relationship, and WHITE and BLUE have a trust relationship, then it holds that there is no
-implied trust between the RED and BLUE domains. ie: Relationships are explicit and not
-transitive.
-</p><p>
-New to MS Windows 2000 ADS security contexts is the fact that trust relationships are two-way
-by default. Also, all inter-ADS domain trusts are transitive. In the case of the RED, WHITE and BLUE
-domains above, with Windows 2000 and ADS the RED and BLUE domains CAN trust each other. This is
-an inherent feature of ADS domains. Samba-3 implements MS Windows NT4
-style Interdomain trusts and interoperates with MS Windows 200x ADS
-security domains in similar manner to MS Windows NT4 style domains.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2881006"></a>Native MS Windows NT4 Trusts Configuration</h2></div></div><p>
-There are two steps to creating an interdomain trust relationship.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2881019"></a>NT4 as the Trusting Domain (ie. creating the trusted account)</h3></div></div><p>
-For MS Windows NT4, all domain trust relationships are configured using the Domain User Manager.
-To affect a two way trust relationship it is necessary for each domain administrator to make
-available (for use by an external domain) it's security resources. This is done from the Domain
-User Manager Policies entry on the menu bar. From the Policy menu, select Trust Relationships, then
-next to the lower box that is labelled &quot;Permitted to Trust this Domain&quot; are two buttons, &quot;Add&quot; and
-&quot;Remove&quot;. The &quot;Add&quot; button will open a panel in which needs to be entered the remote domain that
-will be able to assign user rights to your domain. In addition it is necessary to enter a password
-that is specific to this trust relationship. The password needs to be
-typed twice (for standard confirmation).
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2881063"></a>NT4 as the Trusted Domain (ie. creating trusted account's password)</h3></div></div><p>
-A trust relationship will work only when the other (trusting) domain makes the appropriate connections
-with the trusted domain. To consumate the trust relationship the administrator will launch the
-Domain User Manager, from the menu select Policies, then select Trust Relationships, then click on the
-&quot;Add&quot; button that is next to the box that is labelled &quot;Trusted Domains&quot;. A panel will open in
-which must be entered the name of the remote domain as well as the password assigned to that trust.
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2881087"></a>Configuring Samba NT-style Domain Trusts</h2></div></div><p>
-This description is meant to be a fairly short introduction about how to set up a Samba server so
-that it could participate in interdomain trust relationships. Trust relationship support in Samba
-is in its early stage, so lot of things don't work yet.
-</p><p>
-Each of the procedures described below is treated as they were performed with Windows NT4 Server on
-one end. The remote end could just as well be another Samba-3 domain. It can be clearly seen, after
-reading this document, that combining Samba-specific parts of what's written below leads to trust
-between domains in purely Samba environment.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2881114"></a>Samba-3 as the Trusting Domain</h3></div></div><p>
-In order to set the Samba PDC to be the trusted party of the relationship first you need
-to create special account for the domain that will be the trusting party. To do that,
-you can use the 'smbpasswd' utility. Creating the trusted domain account is very
-similiar to creating a trusted machine account. Suppose, your domain is
-called SAMBA, and the remote domain is called RUMBA. The first step
-will be to issue this command from your favourite shell:
-</p><p>
-</p><pre class="screen">
-<tt>deity#</tt> <b><tt>smbpasswd -a -i rumba</tt></b>
- New SMB password: XXXXXXXX
- Retype SMB password: XXXXXXXX
- Added user rumba$
-</pre><p>
-
-where <i><tt>-a</tt></i> means to add a new account into the
-passdb database and <i><tt>-i</tt></i> means: ''create this
-account with the InterDomain trust flag''
-</p><p>
-The account name will be 'rumba$' (the name of the remote domain)
-</p><p>
-After issuing this command you'll be asked to enter the password for
-the account. You can use any password you want, but be aware that Windows NT will
-not change this password until 7 days following account creation.
-After the command returns successfully, you can look at the entry for the new account
-(in the stardard way depending on your configuration) and see that account's name is
-really RUMBA$ and it has 'I' flag in the flags field. Now you're ready to confirm
-the trust by establishing it from Windows NT Server.
-</p><p>
-Open 'User Manager for Domains' and from menu 'Policies' select 'Trust Relationships...'.
-Right beside 'Trusted domains' list box press 'Add...' button. You will be prompted for
-the trusted domain name and the relationship password. Type in SAMBA, as this is
-your domain name, and the password used at the time of account creation.
-Press OK and, if everything went without incident, you will see 'Trusted domain relationship
-successfully established' message.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2881210"></a>Samba-3 as the Trusted Domain</h3></div></div><p>
-This time activities are somewhat reversed. Again, we'll assume that your domain
-controlled by the Samba PDC is called SAMBA and NT-controlled domain is called RUMBA.
-</p><p>
-The very first thing requirement is to add an account for the SAMBA domain on RUMBA's PDC.
-</p><p>
-Launch the Domain User Manager, then from the menu select 'Policies', 'Trust Relationships'.
-Now, next to 'Trusted Domains' box press the 'Add' button, and type in the name of the trusted
-domain (SAMBA) and password securing the relationship.
-</p><p>
-The password can be arbitrarily chosen. It is easy to change the password
-from the Samba server whenever you want. After confirming the password your account is
-ready for use. Now it's Samba's turn.
-</p><p>
-Using your favourite shell while being logged in as root, issue this command:
-</p><p>
-<tt>deity# </tt><b><tt>net rpc trustdom establish rumba</tt></b>
-</p><p>
-You will be prompted for the password you just typed on your Windows NT4 Server box.
-Do not worry if you see an error message that mentions a returned code of
-NT_STATUS_NOLOGON_INTERDOMAIN_TRUST_ACCOUNT. It means the
-password you gave is correct and the NT4 Server says the account is
-ready for interdomain connection and not for ordinary
-connection. After that, be patient it can take a while (especially
-in large networks), you should see the 'Success' message. Congratulations! Your trust
-relationship has just been established.
-</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-Note that you have to run this command as root because you must have write access to
-the <tt>secrets.tdb</tt> file.
-</p></div></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="pam"></a>Chapter20.PAM Configuration for Centrally Managed Authentication</h2></div><div><div class="author"><h3 class="author">John H. Terpstra</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt>&lt;<a href="mailto:jht@samba.org">jht@samba.org</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate"> (Jun 21 2001) </p></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2880956">Samba and PAM</a></dt><dd><dl><dt><a href="#id2881738">PAM Configuration in smb.conf</a></dt><dt><a href="#id2881795">Password Synchronisation using pam_smbpass.so</a></dt></dl></dd><dt><a href="#id2882047">Distributed Authentication</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2880956"></a>Samba and PAM</h2></div></div><p>
-A number of Unix systems (eg: Sun Solaris), as well as the
-xxxxBSD family and Linux, now utilize the Pluggable Authentication
-Modules (PAM) facility to provide all authentication,
-authorization and resource control services. Prior to the
-introduction of PAM, a decision to use an alternative to
-the system password database (<tt>/etc/passwd</tt>)
-would require the provision of alternatives for all programs that provide
-security services. Such a choice would involve provision of
-alternatives to such programs as: <b>login</b>,
-<b>passwd</b>, <b>chown</b>, etc.
-</p><p>
-PAM provides a mechanism that disconnects these security programs
-from the underlying authentication/authorization infrastructure.
-PAM is configured either through one file <tt>/etc/pam.conf</tt> (Solaris),
-or by editing individual files that are located in <tt>/etc/pam.d</tt>.
-</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
- If the PAM authentication module (loadable link library file) is located in the
- default location then it is not necessary to specify the path. In the case of
- Linux, the default location is <tt>/lib/security</tt>. If the module
- is located outside the default then the path must be specified as:
-
- </p><pre class="programlisting">
- auth required /other_path/pam_strange_module.so
- </pre><p>
- </p></div><p>
-The following is an example <tt>/etc/pam.d/login</tt> configuration file.
-This example had all options been uncommented is probably not usable
-as it stacks many conditions before allowing successful completion
-of the login process. Essentially all conditions can be disabled
-by commenting them out except the calls to <tt>pam_pwdb.so</tt>.
-</p><pre class="programlisting">
- #%PAM-1.0
- # The PAM configuration file for the `login' service
- #
- auth required pam_securetty.so
- auth required pam_nologin.so
- # auth required pam_dialup.so
- # auth optional pam_mail.so
- auth required pam_pwdb.so shadow md5
- # account requisite pam_time.so
- account required pam_pwdb.so
- session required pam_pwdb.so
- # session optional pam_lastlog.so
- # password required pam_cracklib.so retry=3
- password required pam_pwdb.so shadow md5
-</pre><p>
-PAM allows use of replacable modules. Those available on a
-sample system include:
-</p><p><tt>$</tt><b><tt>/bin/ls /lib/security</tt></b>
-</p><pre class="programlisting">
- pam_access.so pam_ftp.so pam_limits.so
- pam_ncp_auth.so pam_rhosts_auth.so pam_stress.so
- pam_cracklib.so pam_group.so pam_listfile.so
- pam_nologin.so pam_rootok.so pam_tally.so
- pam_deny.so pam_issue.so pam_mail.so
- pam_permit.so pam_securetty.so pam_time.so
- pam_dialup.so pam_lastlog.so pam_mkhomedir.so
- pam_pwdb.so pam_shells.so pam_unix.so
- pam_env.so pam_ldap.so pam_motd.so
- pam_radius.so pam_smbpass.so pam_unix_acct.so
- pam_wheel.so pam_unix_auth.so pam_unix_passwd.so
- pam_userdb.so pam_warn.so pam_unix_session.so
-</pre><p>
-The following example for the login program replaces the use of
-the <tt>pam_pwdb.so</tt> module which uses the system
-password database (<tt>/etc/passwd</tt>,
-<tt>/etc/shadow</tt>, <tt>/etc/group</tt>) with
-the module <tt>pam_smbpass.so</tt> which uses the Samba
-database which contains the Microsoft MD4 encrypted password
-hashes. This database is stored in either
-<tt>/usr/local/samba/private/smbpasswd</tt>,
-<tt>/etc/samba/smbpasswd</tt>, or in
-<tt>/etc/samba.d/smbpasswd</tt>, depending on the
-Samba implementation for your Unix/Linux system. The
-<tt>pam_smbpass.so</tt> module is provided by
-Samba version 2.2.1 or later. It can be compiled by specifying the
-<b>--with-pam_smbpass</b> options when running Samba's
-<tt>configure</tt> script. For more information
-on the <tt>pam_smbpass</tt> module, see the documentation
-in the <tt>source/pam_smbpass</tt> directory of the Samba
-source distribution.
-</p><pre class="programlisting">
- #%PAM-1.0
- # The PAM configuration file for the `login' service
- #
- auth required pam_smbpass.so nodelay
- account required pam_smbpass.so nodelay
- session required pam_smbpass.so nodelay
- password required pam_smbpass.so nodelay
-</pre><p>
-The following is the PAM configuration file for a particular
-Linux system. The default condition uses <tt>pam_pwdb.so</tt>.
-</p><pre class="programlisting">
- #%PAM-1.0
- # The PAM configuration file for the `samba' service
- #
- auth required pam_pwdb.so nullok nodelay shadow audit
- account required pam_pwdb.so audit nodelay
- session required pam_pwdb.so nodelay
- password required pam_pwdb.so shadow md5
-</pre><p>
-In the following example the decision has been made to use the
-smbpasswd database even for basic samba authentication. Such a
-decision could also be made for the passwd program and would
-thus allow the smbpasswd passwords to be changed using the passwd
-program.
-</p><pre class="programlisting">
- #%PAM-1.0
- # The PAM configuration file for the `samba' service
- #
- auth required pam_smbpass.so nodelay
- account required pam_pwdb.so audit nodelay
- session required pam_pwdb.so nodelay
- password required pam_smbpass.so nodelay smbconf=/etc/samba.d/smb.conf
-</pre><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>PAM allows stacking of authentication mechanisms. It is
-also possible to pass information obtained within one PAM module through
-to the next module in the PAM stack. Please refer to the documentation for
-your particular system implementation for details regarding the specific
-capabilities of PAM in this environment. Some Linux implmentations also
-provide the <tt>pam_stack.so</tt> module that allows all
-authentication to be configured in a single central file. The
-<tt>pam_stack.so</tt> method has some very devoted followers
-on the basis that it allows for easier administration. As with all issues in
-life though, every decision makes trade-offs, so you may want examine the
-PAM documentation for further helpful information.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2881738"></a>PAM Configuration in smb.conf</h3></div></div><p>
-There is an option in smb.conf called <a href="smb.conf.5.html#OBEYPAMRESTRICTIONS" target="_top">obey pam restrictions</a>.
-The following is from the on-line help for this option in SWAT;
-</p><p>
-When Samba is configured to enable PAM support (i.e.
-<tt>--with-pam</tt>), this parameter will
-control whether or not Samba should obey PAM's account
-and session management directives. The default behavior
-is to use PAM for clear text authentication only and to
-ignore any account or session management. Note that Samba always
-ignores PAM for authentication in the case of
-<a href="smb.conf.5.html#ENCRYPTPASSWORDS" target="_top">encrypt passwords = yes</a>.
-The reason is that PAM modules cannot support the challenge/response
-authentication mechanism needed in the presence of SMB
-password encryption.
-</p><p>Default: <b>obey pam restrictions = no</b></p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2881795"></a>Password Synchronisation using pam_smbpass.so</h3></div></div><p>
-pam_smbpass is a PAM module which can be used on conforming systems to
-keep the smbpasswd (Samba password) database in sync with the unix
-password file. PAM (Pluggable Authentication Modules) is an API supported
-under some Unices, such as Solaris, HPUX and Linux, that provides a
-generic interface to authentication mechanisms.
-</p><p>
-For more information on PAM, see http://ftp.kernel.org/pub/linux/libs/pam/
-</p><p>
-This module authenticates a local smbpasswd user database. If you require
-support for authenticating against a remote SMB server, or if you're
-concerned about the presence of suid root binaries on your system, it is
-recommended that you use pam_winbind instead.
-</p><pre class="programlisting">
-Options recognized by this module are as follows:
-
- debug - log more debugging info
- audit - like debug, but also logs unknown usernames
- use_first_pass - don't prompt the user for passwords;
- take them from PAM_ items instead
- try_first_pass - try to get the password from a previous
- PAM module, fall back to prompting the user
- use_authtok - like try_first_pass, but *fail* if the new
- PAM_AUTHTOK has not been previously set.
- (intended for stacking password modules only)
- not_set_pass - don't make passwords used by this module
- available to other modules.
- nodelay - don't insert ~1 second delays on authentication
- failure.
- nullok - null passwords are allowed.
- nonull - null passwords are not allowed. Used to
- override the Samba configuration.
- migrate - only meaningful in an &quot;auth&quot; context;
- used to update smbpasswd file with a
- password used for successful authentication.
- smbconf=&lt; file &gt; - specify an alternate path to the smb.conf
- file.
-</pre><pre class="programlisting">
-Thanks go to the following people:
-
- * Andrew Morgan &lt; morgan@transmeta.com &gt;, for providing the Linux-PAM
- framework, without which none of this would have happened
-
- * Christian Gafton &lt; gafton@redhat.com &gt; and Andrew Morgan again, for the
- pam_pwdb module upon which pam_smbpass was originally based
-
- * Luke Leighton &lt; lkcl@switchboard.net &gt; for being receptive to the idea,
- and for the occasional good-natured complaint about the project's status
- that keep me working on it :)
-
- * and of course, all the other members of the Samba team
- &lt;http://www.samba.org/samba/team.html&gt;, for creating a great product
- and for giving this project a purpose
-
- ---------------------
- Stephen Langasek &lt; vorlon@netexpress.net &gt;
-</pre><p>
-The following are examples of the use of pam_smbpass.so in the format of Linux
-<tt>/etc/pam.d/</tt> files structure. Those wishing to implement this
-tool on other platforms will need to adapt this appropriately.
-</p><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2881907"></a>Password Synchonisation Configuration</h4></div></div><p>
-A sample PAM configuration that shows the use of pam_smbpass to make
-sure private/smbpasswd is kept in sync when /etc/passwd (/etc/shadow)
-is changed. Useful when an expired password might be changed by an
-application (such as ssh).
-</p><pre class="programlisting">
- #%PAM-1.0
- # password-sync
- #
- auth requisite pam_nologin.so
- auth required pam_unix.so
- account required pam_unix.so
- password requisite pam_cracklib.so retry=3
- password requisite pam_unix.so shadow md5 use_authtok try_first_pass
- password required pam_smbpass.so nullok use_authtok try_first_pass
- session required pam_unix.so
-</pre></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2881941"></a>Password Migration Configuration</h4></div></div><p>
-A sample PAM configuration that shows the use of pam_smbpass to migrate
-from plaintext to encrypted passwords for Samba. Unlike other methods,
-this can be used for users who have never connected to Samba shares:
-password migration takes place when users ftp in, login using ssh, pop
-their mail, etc.
-</p><pre class="programlisting">
- #%PAM-1.0
- # password-migration
- #
- auth requisite pam_nologin.so
- # pam_smbpass is called IFF pam_unix succeeds.
- auth requisite pam_unix.so
- auth optional pam_smbpass.so migrate
- account required pam_unix.so
- password requisite pam_cracklib.so retry=3
- password requisite pam_unix.so shadow md5 use_authtok try_first_pass
- password optional pam_smbpass.so nullok use_authtok try_first_pass
- session required pam_unix.so
-</pre></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2881978"></a>Mature Password Configuration</h4></div></div><p>
-A sample PAM configuration for a 'mature' smbpasswd installation.
-private/smbpasswd is fully populated, and we consider it an error if
-the smbpasswd doesn't exist or doesn't match the Unix password.
-</p><pre class="programlisting">
- #%PAM-1.0
- # password-mature
- #
- auth requisite pam_nologin.so
- auth required pam_unix.so
- account required pam_unix.so
- password requisite pam_cracklib.so retry=3
- password requisite pam_unix.so shadow md5 use_authtok try_first_pass
- password required pam_smbpass.so use_authtok use_first_pass
- session required pam_unix.so
-</pre></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2882011"></a>Kerberos Password Integration Configuration</h4></div></div><p>
-A sample PAM configuration that shows pam_smbpass used together with
-pam_krb5. This could be useful on a Samba PDC that is also a member of
-a Kerberos realm.
-</p><pre class="programlisting">
- #%PAM-1.0
- # kdc-pdc
- #
- auth requisite pam_nologin.so
- auth requisite pam_krb5.so
- auth optional pam_smbpass.so migrate
- account required pam_krb5.so
- password requisite pam_cracklib.so retry=3
- password optional pam_smbpass.so nullok use_authtok try_first_pass
- password required pam_krb5.so use_authtok try_first_pass
- session required pam_krb5.so
-</pre></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2882047"></a>Distributed Authentication</h2></div></div><p>
-The astute administrator will realize from this that the
-combination of <tt>pam_smbpass.so</tt>,
-<b>winbindd</b>, and a distributed
-passdb backend, such as ldap, will allow the establishment of a
-centrally managed, distributed
-user/password database that can also be used by all
-PAM (eg: Linux) aware programs and applications. This arrangement
-can have particularly potent advantages compared with the
-use of Microsoft Active Directory Service (ADS) in so far as
-reduction of wide area network authentication traffic.
-</p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="VFS"></a>Chapter21.Stackable VFS modules</h2></div><div><div class="author"><h3 class="author">Jelmer R. Vernooij</h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt>&lt;<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author">John H. Terpstra</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt>&lt;<a href="mailto:jht@samba.org">jht@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author">Alexander Bokovoy</h3></div></div><div><div class="author"><h3 class="author">Tim Potter</h3></div></div><div><div class="author"><h3 class="author">Simo Sorce</h3></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2881331">Introduction and configuration</a></dt><dt><a href="#id2882249">Included modules</a></dt><dd><dl><dt><a href="#id2882256">audit</a></dt><dt><a href="#id2882295">extd_audit</a></dt><dt><a href="#id2882416">recycle</a></dt><dt><a href="#id2882554">netatalk</a></dt></dl></dd><dt><a href="#id2882592">VFS modules available elsewhere</a></dt><dd><dl><dt><a href="#id2882614">DatabaseFS</a></dt><dt><a href="#id2882669">vscan</a></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2881331"></a>Introduction and configuration</h2></div></div><p>
-Since samba 3.0, samba supports stackable VFS(Virtual File System) modules.
-Samba passes each request to access the unix file system thru the loaded VFS modules.
-This chapter covers all the modules that come with the samba source and references to
-some external modules.
-</p><p>
-You may have problems to compile these modules, as shared libraries are
-compiled and linked in different ways on different systems.
-They currently have been tested against GNU/linux and IRIX.
-</p><p>
-To use the VFS modules, create a share similar to the one below. The
-important parameter is the <b>vfs object</b> parameter which must point to
-the exact pathname of the shared library objects. For example, to log all access
-to files and use a recycle bin:
-
-</p><pre class="programlisting">
- [audit]
- comment = Audited /data directory
- path = /data
- vfs object = /path/to/audit.so /path/to/recycle.so
- writeable = yes
- browseable = yes
-</pre><p>
-</p><p>
-The modules are used in the order they are specified.
-</p><p>
-Further documentation on writing VFS modules for Samba can be found in
-the Samba Developers Guide.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2882249"></a>Included modules</h2></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2882256"></a>audit</h3></div></div><p>A simple module to audit file access to the syslog
-facility. The following operations are logged:
-</p><table class="simplelist" border="0" summary="Simple list"><tr><td>share</td></tr><tr><td>connect/disconnect</td></tr><tr><td>directory opens/create/remove</td></tr><tr><td>file open/close/rename/unlink/chmod</td></tr></table><p>
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2882295"></a>extd_audit</h3></div></div><p>
-This module is identical with the <span class="emphasis"><em>audit</em></span> module above except
-that it sends audit logs to both syslog as well as the smbd log file/s. The
-loglevel for this module is set in the smb.conf file.
-</p><p>
-The logging information that will be written to the smbd log file is controlled by
-the <span class="emphasis"><em>log level</em></span> parameter in <tt>smb.conf</tt>. The
-following information will be recorded:
-</p><div class="table"><a name="id2882333"></a><p class="title"><b>Table21.1.Extended Auditing Log Information</b></p><table summary="Extended Auditing Log Information" border="1"><colgroup><col><col></colgroup><thead><tr><th align="center">Log Level</th><th align="center">Log Details - File and Directory Operations</th></tr></thead><tbody><tr><td align="center">0</td><td align="left">Creation / Deletion</td></tr><tr><td align="center">1</td><td align="left">Create / Delete / Rename / Permission Changes</td></tr><tr><td align="center">2</td><td align="left">Create / Delete / Rename / Perm Change / Open / Close</td></tr></tbody></table></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2882416"></a>recycle</h3></div></div><p>
-A recycle-bin like module. When used any unlink call
-will be intercepted and files moved to the recycle
-directory instead of being deleted.
-</p><p>Supported options:
-</p><div class="variablelist"><dl><dt><span class="term">vfs_recycle_bin:repository</span></dt><dd><p>FIXME</p></dd><dt><span class="term">vfs_recycle_bin:keeptree</span></dt><dd><p>FIXME</p></dd><dt><span class="term">vfs_recycle_bin:versions</span></dt><dd><p>FIXME</p></dd><dt><span class="term">vfs_recycle_bin:touch</span></dt><dd><p>FIXME</p></dd><dt><span class="term">vfs_recycle_bin:maxsize</span></dt><dd><p>FIXME</p></dd><dt><span class="term">vfs_recycle_bin:exclude</span></dt><dd><p>FIXME</p></dd><dt><span class="term">vfs_recycle_bin:exclude_dir</span></dt><dd><p>FIXME</p></dd><dt><span class="term">vfs_recycle_bin:noversions</span></dt><dd><p>FIXME</p></dd></dl></div><p>
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2882554"></a>netatalk</h3></div></div><p>
-A netatalk module, that will ease co-existence of samba and
-netatalk file sharing services.
-</p><p>Advantages compared to the old netatalk module:
-</p><table class="simplelist" border="0" summary="Simple list"><tr><td>it doesn't care about creating of .AppleDouble forks, just keeps them in sync</td></tr><tr><td>if share in smb.conf doesn't contain .AppleDouble item in hide or veto list, it will be added automatically</td></tr></table><p>
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2882592"></a>VFS modules available elsewhere</h2></div></div><p>
-This section contains a listing of various other VFS modules that
-have been posted but don't currently reside in the Samba CVS
-tree for one reason or another (e.g. it is easy for the maintainer
-to have his or her own CVS tree).
-</p><p>
-No statemets about the stability or functionality of any module
-should be implied due to its presence here.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2882614"></a>DatabaseFS</h3></div></div><p>
-URL: <a href="http://www.css.tayloru.edu/~elorimer/databasefs/index.php" target="_top">http://www.css.tayloru.edu/~elorimer/databasefs/index.php</a>
-</p><p>By <a href="mailto:elorimer@css.tayloru.edu" target="_top">Eric Lorimer</a>.</p><p>
-I have created a VFS module which implements a fairly complete read-only
-filesystem. It presents information from a database as a filesystem in
-a modular and generic way to allow different databases to be used
-(originally designed for organizing MP3s under directories such as
-&quot;Artists,&quot; &quot;Song Keywords,&quot; etc... I have since applied it to a student
-roster database very easily). The directory structure is stored in the
-database itself and the module makes no assumptions about the database
-structure beyond the table it requires to run.
-</p><p>
-Any feedback would be appreciated: comments, suggestions, patches,
-etc... If nothing else, hopefully it might prove useful for someone
-else who wishes to create a virtual filesystem.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2882669"></a>vscan</h3></div></div><p>URL: <a href="http://www.openantivirus.org/" target="_top">http://www.openantivirus.org/</a></p><p>
-samba-vscan is a proof-of-concept module for Samba, which
-uses the VFS (virtual file system) features of Samba 2.2.x/3.0
-alphaX. Of couse, Samba has to be compiled with VFS support.
-samba-vscan supports various virus scanners and is maintained
-by Rainer Link.
-</p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="msdfs"></a>Chapter22.Hosting a Microsoft Distributed File System tree on Samba</h2></div><div><div class="author"><h3 class="author">Shirish Kalele</h3><div class="affiliation"><span class="orgname">Samba Team &amp; Veritas Software<br></span><div class="address"><p><br>
- <tt>&lt;<a href="mailto:samba@samba.org">samba@samba.org</a>&gt;</tt><br>
- </p></div></div></div></div><div><p class="pubdate">12 Jul 2000</p></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2882214">Instructions</a></dt><dd><dl><dt><a href="#id2882961">Notes</a></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2882214"></a>Instructions</h2></div></div><p>The Distributed File System (or Dfs) provides a means of
- separating the logical view of files and directories that users
- see from the actual physical locations of these resources on the
- network. It allows for higher availability, smoother storage expansion,
- load balancing etc. For more information about Dfs, refer to <a href="http://www.microsoft.com/NTServer/nts/downloads/winfeatures/NTSDistrFile/AdminGuide.asp" target="_top">
- Microsoft documentation</a>. </p><p>This document explains how to host a Dfs tree on a Unix
- machine (for Dfs-aware clients to browse) using Samba.</p><p>To enable SMB-based DFS for Samba, configure it with the
- <i><tt>--with-msdfs</tt></i> option. Once built, a
- Samba server can be made a Dfs server by setting the global
- boolean <a href="smb.conf.5.html#HOSTMSDFS" target="_top"><i><tt>
- host msdfs</tt></i></a> parameter in the <tt>smb.conf
- </tt> file. You designate a share as a Dfs root using the share
- level boolean <a href="smb.conf.5.html#MSDFSROOT" target="_top"><i><tt>
- msdfs root</tt></i></a> parameter. A Dfs root directory on
- Samba hosts Dfs links in the form of symbolic links that point
- to other servers. For example, a symbolic link
- <tt>junction-&gt;msdfs:storage1\share1</tt> in
- the share directory acts as the Dfs junction. When Dfs-aware
- clients attempt to access the junction link, they are redirected
- to the storage location (in this case, \\storage1\share1).</p><p>Dfs trees on Samba work with all Dfs-aware clients ranging
- from Windows 95 to 2000.</p><p>Here's an example of setting up a Dfs tree on a Samba
- server.</p><pre class="programlisting">
-# The smb.conf file:
-[global]
- netbios name = SAMBA
- host msdfs = yes
-
-[dfs]
- path = /export/dfsroot
- msdfs root = yes
- </pre><p>In the /export/dfsroot directory we set up our dfs links to
- other servers on the network.</p><p><tt>root# </tt><b><tt>cd /export/dfsroot</tt></b></p><p><tt>root# </tt><b><tt>chown root /export/dfsroot</tt></b></p><p><tt>root# </tt><b><tt>chmod 755 /export/dfsroot</tt></b></p><p><tt>root# </tt><b><tt>ln -s msdfs:storageA\\shareA linka</tt></b></p><p><tt>root# </tt><b><tt>ln -s msdfs:serverB\\share,serverC\\share linkb</tt></b></p><p>You should set up the permissions and ownership of
- the directory acting as the Dfs root such that only designated
- users can create, delete or modify the msdfs links. Also note
- that symlink names should be all lowercase. This limitation exists
- to have Samba avoid trying all the case combinations to get at
- the link name. Finally set up the symbolic links to point to the
- network shares you want, and start Samba.</p><p>Users on Dfs-aware clients can now browse the Dfs tree
- 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" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2882961"></a>Notes</h3></div></div><div class="itemizedlist"><ul type="disc"><li><p>Windows clients need to be rebooted
- if a previously mounted non-dfs share is made a dfs
- root or vice versa. A better way is to introduce a
- new share and make it the dfs root.</p></li><li><p>Currently there's a restriction that msdfs
- symlink names should all be lowercase.</p></li><li><p>For security purposes, the directory
- acting as the root of the Dfs tree should have ownership
- and permissions set so that only designated users can
- modify the symbolic links in the directory.</p></li></ul></div></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="integrate-ms-networks"></a>Chapter23.Integrating MS Windows networks with Samba</h2></div><div><div class="author"><h3 class="author">John H. Terpstra</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt>&lt;<a href="mailto:jht@samba.org">jht@samba.org</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate"> (Jan 01 2001) </p></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2882745">Name Resolution in a pure Unix/Linux world</a></dt><dd><dl><dt><a href="#id2883178">/etc/hosts</a></dt><dt><a href="#id2883316">/etc/resolv.conf</a></dt><dt><a href="#id2883360">/etc/host.conf</a></dt><dt><a href="#id2883403">/etc/nsswitch.conf</a></dt></dl></dd><dt><a href="#id2883498">Name resolution as used within MS Windows networking</a></dt><dd><dl><dt><a href="#id2883030">The NetBIOS Name Cache</a></dt><dt><a href="#id2883069">The LMHOSTS file</a></dt><dt><a href="#id2883112">HOSTS file</a></dt><dt><a href="#id2883144">DNS Lookup</a></dt><dt><a href="#id2883156">WINS Lookup</a></dt></dl></dd></dl></div><p>
-This section deals with NetBIOS over TCP/IP name to IP address resolution. If
-your MS Windows clients are NOT configured to use NetBIOS over TCP/IP then this
-section does not apply to your installation. If your installation involves use of
-NetBIOS over TCP/IP then this section may help you to resolve networking problems.
-</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
- NetBIOS over TCP/IP has nothing to do with NetBEUI. NetBEUI is NetBIOS
- over Logical Link Control (LLC). On modern networks it is highly advised
- to NOT run NetBEUI at all. Note also that there is NO such thing as
- NetBEUI over TCP/IP - the existence of such a protocol is a complete
- and utter mis-apprehension.
-</p></div><p>
-Since the introduction of MS Windows 2000 it is possible to run MS Windows networking
-without the use of NetBIOS over TCP/IP. NetBIOS over TCP/IP uses UDP port 137 for NetBIOS
-name resolution and uses TCP port 139 for NetBIOS session services. When NetBIOS over
-TCP/IP is disabled on MS Windows 2000 and later clients then only TCP port 445 will be
-used and UDP port 137 and TCP port 139 will not.
-</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-When using Windows 2000 or later clients, if NetBIOS over TCP/IP is NOT disabled, then
-the client will use UDP port 137 (NetBIOS Name Service, also known as the Windows Internet
-Name Service or WINS), TCP port 139 AND TCP port 445 (for actual file and print traffic).
-</p></div><p>
-When NetBIOS over TCP/IP is disabled the use of DNS is essential. Most installations that
-disable NetBIOS over TCP/IP today use MS Active Directory Service (ADS). ADS requires
-Dynamic DNS with Service Resource Records (SRV RR) and with Incremental Zone Transfers (IXFR).
-Use of DHCP with ADS is recommended as a further means of maintaining central control
-over client workstation network configuration.
-</p><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2882745"></a>Name Resolution in a pure Unix/Linux world</h2></div></div><p>
-The key configuration files covered in this section are:
-</p><div class="itemizedlist"><ul type="disc"><li><p><tt>/etc/hosts</tt></p></li><li><p><tt>/etc/resolv.conf</tt></p></li><li><p><tt>/etc/host.conf</tt></p></li><li><p><tt>/etc/nsswitch.conf</tt></p></li></ul></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2883178"></a><tt>/etc/hosts</tt></h3></div></div><p>
-Contains a static list of IP Addresses and names.
-eg:
-</p><pre class="programlisting">
- 127.0.0.1 localhost localhost.localdomain
- 192.168.1.1 bigbox.caldera.com bigbox alias4box
-</pre><p>
-The purpose of <tt>/etc/hosts</tt> is to provide a
-name resolution mechanism so that uses do not need to remember
-IP addresses.
-</p><p>
-Network packets that are sent over the physical network transport
-layer communicate not via IP addresses but rather using the Media
-Access Control address, or MAC address. IP Addresses are currently
-32 bits in length and are typically presented as four (4) decimal
-numbers that are separated by a dot (or period). eg: 168.192.1.1
-</p><p>
-MAC Addresses use 48 bits (or 6 bytes) and are typically represented
-as two digit hexadecimal numbers separated by colons. eg:
-40:8e:0a:12:34:56
-</p><p>
-Every network interfrace must have an MAC address. Associated with
-a MAC address there may be one or more IP addresses. There is NO
-relationship between an IP address and a MAC address, all such assignments
-are arbitary or discretionary in nature. At the most basic level all
-network communications takes place using MAC addressing. Since MAC
-addresses must be globally unique, and generally remains fixed for
-any particular interface, the assignment of an IP address makes sense
-from a network management perspective. More than one IP address can
-be assigned per MAC address. One address must be the primary IP address,
-this is the address that will be returned in the ARP reply.
-</p><p>
-When a user or a process wants to communicate with another machine
-the protocol implementation ensures that the &quot;machine name&quot; or &quot;host
-name&quot; is resolved to an IP address in a manner that is controlled
-by the TCP/IP configuration control files. The file
-<tt>/etc/hosts</tt> is one such file.
-</p><p>
-When the IP address of the destination interface has been
-determined a protocol called ARP/RARP is used to identify
-the MAC address of the target interface. ARP stands for Address
-Resolution Protocol, and is a broadcast oriented method that
-uses UDP (User Datagram Protocol) to send a request to all
-interfaces on the local network segment using the all 1's MAC
-address. Network interfaces are programmed to respond to two
-MAC addresses only; their own unique address and the address
-ff:ff:ff:ff:ff:ff. The reply packet from an ARP request will
-contain the MAC address and the primary IP address for each
-interface.
-</p><p>
-The <tt>/etc/hosts</tt> file is foundational to all
-Unix/Linux TCP/IP installations and as a minumum will contain
-the localhost and local network interface IP addresses and the
-primary names by which they are known within the local machine.
-This file helps to prime the pump so that a basic level of name
-resolution can exist before any other method of name resolution
-becomes available.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2883316"></a><tt>/etc/resolv.conf</tt></h3></div></div><p>
-This file tells the name resolution libraries:
-</p><div class="itemizedlist"><ul type="disc"><li><p>The name of the domain to which the machine
- belongs
- </p></li><li><p>The name(s) of any domains that should be
- automatically searched when trying to resolve unqualified
- host names to their IP address
- </p></li><li><p>The name or IP address of available Domain
- Name Servers that may be asked to perform name to address
- translation lookups
- </p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2883360"></a><tt>/etc/host.conf</tt></h3></div></div><p>
-<tt>/etc/host.conf</tt> is the primary means by
-which the setting in /etc/resolv.conf may be affected. It is a
-critical configuration file. This file controls the order by
-which name resolution may procede. The typical structure is:
-</p><pre class="programlisting">
- order hosts,bind
- multi on
-</pre><p>
-then both addresses should be returned. Please refer to the
-man page for host.conf for further details.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2883403"></a><tt>/etc/nsswitch.conf</tt></h3></div></div><p>
-This file controls the actual name resolution targets. The
-file typically has resolver object specifications as follows:
-</p><pre class="programlisting">
- # /etc/nsswitch.conf
- #
- # Name Service Switch configuration file.
- #
-
- passwd: compat
- # Alternative entries for password authentication are:
- # passwd: compat files nis ldap winbind
- shadow: compat
- group: compat
-
- hosts: files nis dns
- # Alternative entries for host name resolution are:
- # hosts: files dns nis nis+ hesoid db compat ldap wins
- networks: nis files dns
-
- ethers: nis files
- protocols: nis files
- rpc: nis files
- services: nis files
-</pre><p>
-Of course, each of these mechanisms requires that the appropriate
-facilities and/or services are correctly configured.
-</p><p>
-It should be noted that unless a network request/message must be
-sent, TCP/IP networks are silent. All TCP/IP communications assumes a
-principal of speaking only when necessary.
-</p><p>
-Starting with version 2.2.0 samba has Linux support for extensions to
-the name service switch infrastructure so that linux clients will
-be able to obtain resolution of MS Windows NetBIOS names to IP
-Addresses. To gain this functionality Samba needs to be compiled
-with appropriate arguments to the make command (ie: <b>make
-nsswitch/libnss_wins.so</b>). The resulting library should
-then be installed in the <tt>/lib</tt> directory and
-the &quot;wins&quot; parameter needs to be added to the &quot;hosts:&quot; line in
-the <tt>/etc/nsswitch.conf</tt> file. At this point it
-will be possible to ping any MS Windows machine by it's NetBIOS
-machine name, so long as that machine is within the workgroup to
-which both the samba machine and the MS Windows machine belong.
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2883498"></a>Name resolution as used within MS Windows networking</h2></div></div><p>
-MS Windows networking is predicated about the name each machine
-is given. This name is known variously (and inconsistently) as
-the &quot;computer name&quot;, &quot;machine name&quot;, &quot;networking name&quot;, &quot;netbios name&quot;,
-&quot;SMB name&quot;. All terms mean the same thing with the exception of
-&quot;netbios name&quot; which can apply also to the name of the workgroup or the
-domain name. The terms &quot;workgroup&quot; and &quot;domain&quot; are really just a
-simply name with which the machine is associated. All NetBIOS names
-are exactly 16 characters in length. The 16th character is reserved.
-It is used to store a one byte value that indicates service level
-information for the NetBIOS name that is registered. A NetBIOS machine
-name is therefore registered for each service type that is provided by
-the client/server.
-</p><p>
-The following are typical NetBIOS name/service type registrations:
-</p><pre class="programlisting">
- Unique NetBIOS Names:
- MACHINENAME&lt;00&gt; = Server Service is running on MACHINENAME
- MACHINENAME&lt;03&gt; = Generic Machine Name (NetBIOS name)
- MACHINENAME&lt;20&gt; = LanMan Server service is running on MACHINENAME
- WORKGROUP&lt;1b&gt; = Domain Master Browser
-
- Group Names:
- WORKGROUP&lt;03&gt; = Generic Name registered by all members of WORKGROUP
- WORKGROUP&lt;1c&gt; = Domain Controllers / Netlogon Servers
- WORKGROUP&lt;1d&gt; = Local Master Browsers
- WORKGROUP&lt;1e&gt; = Internet Name Resolvers
-</pre><p>
-It should be noted that all NetBIOS machines register their own
-names as per the above. This is in vast contrast to TCP/IP
-installations where traditionally the system administrator will
-determine in the /etc/hosts or in the DNS database what names
-are associated with each IP address.
-</p><p>
-One further point of clarification should be noted, the <tt>/etc/hosts</tt>
-file and the DNS records do not provide the NetBIOS name type information
-that MS Windows clients depend on to locate the type of service that may
-be needed. An example of this is what happens when an MS Windows client
-wants to locate a domain logon server. It finds this service and the IP
-address of a server that provides it by performing a lookup (via a
-NetBIOS broadcast) for enumeration of all machines that have
-registered the name type *&lt;1c&gt;. A logon request is then sent to each
-IP address that is returned in the enumerated list of IP addresses. Which
-ever machine first replies then ends up providing the logon services.
-</p><p>
-The name &quot;workgroup&quot; or &quot;domain&quot; really can be confusing since these
-have the added significance of indicating what is the security
-architecture of the MS Windows network. The term &quot;workgroup&quot; indicates
-that the primary nature of the network environment is that of a
-peer-to-peer design. In a WORKGROUP all machines are responsible for
-their own security, and generally such security is limited to use of
-just a password (known as SHARE MODE security). In most situations
-with peer-to-peer networking the users who control their own machines
-will simply opt to have no security at all. It is possible to have
-USER MODE security in a WORKGROUP environment, thus requiring use
-of a user name and a matching password.
-</p><p>
-MS Windows networking is thus predetermined to use machine names
-for all local and remote machine message passing. The protocol used is
-called Server Message Block (SMB) and this is implemented using
-the NetBIOS protocol (Network Basic Input Output System). NetBIOS can
-be encapsulated using LLC (Logical Link Control) protocol - in which case
-the resulting protocol is called NetBEUI (Network Basic Extended User
-Interface). NetBIOS can also be run over IPX (Internetworking Packet
-Exchange) protocol as used by Novell NetWare, and it can be run
-over TCP/IP protocols - in which case the resulting protocol is called
-NBT or NetBT, the NetBIOS over TCP/IP.
-</p><p>
-MS Windows machines use a complex array of name resolution mechanisms.
-Since we are primarily concerned with TCP/IP this demonstration is
-limited to this area.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2883030"></a>The NetBIOS Name Cache</h3></div></div><p>
-All MS Windows machines employ an in memory buffer in which is
-stored the NetBIOS names and IP addresses for all external
-machines that that machine has communicated with over the
-past 10-15 minutes. It is more efficient to obtain an IP address
-for a machine from the local cache than it is to go through all the
-configured name resolution mechanisms.
-</p><p>
-If a machine whose name is in the local name cache has been shut
-down before the name had been expired and flushed from the cache, then
-an attempt to exchange a message with that machine will be subject
-to time-out delays. i.e.: Its name is in the cache, so a name resolution
-lookup will succeed, but the machine can not respond. This can be
-frustrating for users - but it is a characteristic of the protocol.
-</p><p>
-The MS Windows utility that allows examination of the NetBIOS
-name cache is called &quot;nbtstat&quot;. The Samba equivalent of this
-is called &quot;nmblookup&quot;.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2883069"></a>The LMHOSTS file</h3></div></div><p>
-This file is usually located in MS Windows NT 4.0 or
-2000 in <tt>C:\WINNT\SYSTEM32\DRIVERS\ETC</tt> and contains
-the IP Address and the machine name in matched pairs. The
-<tt>LMHOSTS</tt> file performs NetBIOS name
-to IP address mapping.
-</p><p>
-It typically looks like:
-</p><pre class="programlisting">
- # Copyright (c) 1998 Microsoft Corp.
- #
- # This is a sample LMHOSTS file used by the Microsoft Wins Client (NetBIOS
- # over TCP/IP) stack for Windows98
- #
- # This file contains the mappings of IP addresses to NT computernames
- # (NetBIOS) names. Each entry should be kept on an individual line.
- # The IP address should be placed in the first column followed by the
- # corresponding computername. The address and the comptername
- # should be separated by at least one space or tab. The &quot;#&quot; character
- # is generally used to denote the start of a comment (see the exceptions
- # below).
- #
- # This file is compatible with Microsoft LAN Manager 2.x TCP/IP lmhosts
- # files and offers the following extensions:
- #
- # #PRE
- # #DOM:&lt;domain&gt;
- # #INCLUDE &lt;filename&gt;
- # #BEGIN_ALTERNATE
- # #END_ALTERNATE
- # \0xnn (non-printing character support)
- #
- # Following any entry in the file with the characters &quot;#PRE&quot; will cause
- # the entry to be preloaded into the name cache. By default, entries are
- # not preloaded, but are parsed only after dynamic name resolution fails.
- #
- # Following an entry with the &quot;#DOM:&lt;domain&gt;&quot; tag will associate the
- # entry with the domain specified by &lt;domain&gt;. This affects how the
- # browser and logon services behave in TCP/IP environments. To preload
- # the host name associated with #DOM entry, it is necessary to also add a
- # #PRE to the line. The &lt;domain&gt; is always preloaded although it will not
- # be shown when the name cache is viewed.
- #
- # Specifying &quot;#INCLUDE &lt;filename&gt;&quot; will force the RFC NetBIOS (NBT)
- # software to seek the specified &lt;filename&gt; and parse it as if it were
- # local. &lt;filename&gt; is generally a UNC-based name, allowing a
- # centralized lmhosts file to be maintained on a server.
- # It is ALWAYS necessary to provide a mapping for the IP address of the
- # server prior to the #INCLUDE. This mapping must use the #PRE directive.
- # In addtion the share &quot;public&quot; in the example below must be in the
- # LanManServer list of &quot;NullSessionShares&quot; in order for client machines to
- # be able to read the lmhosts file successfully. This key is under
- # \machine\system\currentcontrolset\services\lanmanserver\parameters\nullsessionshares
- # in the registry. Simply add &quot;public&quot; to the list found there.
- #
- # The #BEGIN_ and #END_ALTERNATE keywords allow multiple #INCLUDE
- # statements to be grouped together. Any single successful include
- # will cause the group to succeed.
- #
- # Finally, non-printing characters can be embedded in mappings by
- # first surrounding the NetBIOS name in quotations, then using the
- # \0xnn notation to specify a hex value for a non-printing character.
- #
- # The following example illustrates all of these extensions:
- #
- # 102.54.94.97 rhino #PRE #DOM:networking #net group's DC
- # 102.54.94.102 &quot;appname \0x14&quot; #special app server
- # 102.54.94.123 popular #PRE #source server
- # 102.54.94.117 localsrv #PRE #needed for the include
- #
- # #BEGIN_ALTERNATE
- # #INCLUDE \\localsrv\public\lmhosts
- # #INCLUDE \\rhino\public\lmhosts
- # #END_ALTERNATE
- #
- # In the above example, the &quot;appname&quot; server contains a special
- # character in its name, the &quot;popular&quot; and &quot;localsrv&quot; server names are
- # preloaded, and the &quot;rhino&quot; server name is specified so it can be used
- # to later #INCLUDE a centrally maintained lmhosts file if the &quot;localsrv&quot;
- # system is unavailable.
- #
- # Note that the whole file is parsed including comments on each lookup,
- # so keeping the number of comments to a minimum will improve performance.
- # Therefore it is not advisable to simply add lmhosts file entries onto the
- # end of this file.
-</pre></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2883112"></a>HOSTS file</h3></div></div><p>
-This file is usually located in MS Windows NT 4.0 or 2000 in
-<tt>C:\WINNT\SYSTEM32\DRIVERS\ETC</tt> and contains
-the IP Address and the IP hostname in matched pairs. It can be
-used by the name resolution infrastructure in MS Windows, depending
-on how the TCP/IP environment is configured. This file is in
-every way the equivalent of the Unix/Linux <tt>/etc/hosts</tt> file.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2883144"></a>DNS Lookup</h3></div></div><p>
-This capability is configured in the TCP/IP setup area in the network
-configuration facility. If enabled an elaborate name resolution sequence
-is followed the precise nature of which is dependant on what the NetBIOS
-Node Type parameter is configured to. A Node Type of 0 means use
-NetBIOS broadcast (over UDP broadcast) is first used if the name
-that is the subject of a name lookup is not found in the NetBIOS name
-cache. If that fails then DNS, HOSTS and LMHOSTS are checked. If set to
-Node Type 8, then a NetBIOS Unicast (over UDP Unicast) is sent to the
-WINS Server to obtain a lookup before DNS, HOSTS, LMHOSTS, or broadcast
-lookup is used.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2883156"></a>WINS Lookup</h3></div></div><p>
-A WINS (Windows Internet Name Server) service is the equivaent of the
-rfc1001/1002 specified NBNS (NetBIOS Name Server). A WINS server stores
-the names and IP addresses that are registered by a Windows client
-if the TCP/IP setup has been given at least one WINS Server IP Address.
-</p><p>
-To configure Samba to be a WINS server the following parameter needs
-to be added to the <tt>smb.conf</tt> file:
-</p><pre class="programlisting">
- wins support = Yes
-</pre><p>
-To configure Samba to use a WINS server the following parameters are
-needed in the <tt>smb.conf</tt> file:
-</p><pre class="programlisting">
- wins support = No
- wins server = xxx.xxx.xxx.xxx
-</pre><p>
-where <i><tt>xxx.xxx.xxx.xxx</tt></i> is the IP address
-of the WINS server.
-</p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="securing-samba"></a>Chapter24.Securing Samba</h2></div><div><div class="author"><h3 class="author">Andrew Tridgell</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt>&lt;<a href="mailto:tridge@samba.org">tridge@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author">John H. Terpstra</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt>&lt;<a href="mailto:jht@samba.org">jht@samba.org</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate">17 March 2003</p></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2883603">Introduction</a></dt><dt><a href="#id2883619">Using host based protection</a></dt><dt><a href="#id2884070">Using interface protection</a></dt><dt><a href="#id2884122">Using a firewall</a></dt><dt><a href="#id2884164">Using a IPC$ share deny</a></dt><dt><a href="#id2883724">NTLMv2 Security</a></dt><dt><a href="#id2883760">Upgrading Samba</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2883603"></a>Introduction</h2></div></div><p>
-This note was attached to the Samba 2.2.8 release notes as it contained an
-important security fix. The information contained here applies to Samba
-installations in general.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2883619"></a>Using host based protection</h2></div></div><p>
-In many installations of Samba the greatest threat comes for outside
-your immediate network. By default Samba will accept connections from
-any host, which means that if you run an insecure version of Samba on
-a host that is directly connected to the Internet you can be
-especially vulnerable.
-</p><p>
-One of the simplest fixes in this case is to use the <b>hosts allow</b> and
-<b>hosts deny</b> options in the Samba <tt>smb.conf</tt> configuration file to only
-allow access to your server from a specific range of hosts. An example
-might be:
-</p><pre class="programlisting">
- hosts allow = 127.0.0.1 192.168.2.0/24 192.168.3.0/24
- hosts deny = 0.0.0.0/0
-</pre><p>
-The above will only allow SMB connections from 'localhost' (your own
-computer) and from the two private networks 192.168.2 and
-192.168.3. All other connections will be refused as soon
-as the client sends its first packet. The refusal will be marked as a
-'not listening on called name' error.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2884070"></a>Using interface protection</h2></div></div><p>
-By default Samba will accept connections on any network interface that
-it finds on your system. That means if you have a ISDN line or a PPP
-connection to the Internet then Samba will accept connections on those
-links. This may not be what you want.
-</p><p>
-You can change this behaviour using options like the following:
-</p><pre class="programlisting">
- interfaces = eth* lo
- bind interfaces only = yes
-</pre><p>
-This tells Samba to only listen for connections on interfaces with a
-name starting with 'eth' such as eth0, eth1, plus on the loopback
-interface called 'lo'. The name you will need to use depends on what
-OS you are using, in the above I used the common name for Ethernet
-adapters on Linux.
-</p><p>
-If you use the above and someone tries to make a SMB connection to
-your host over a PPP interface called 'ppp0' then they will get a TCP
-connection refused reply. In that case no Samba code is run at all as
-the operating system has been told not to pass connections from that
-interface to any samba process.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2884122"></a>Using a firewall</h2></div></div><p>
-Many people use a firewall to deny access to services that they don't
-want exposed outside their network. This can be a very good idea,
-although I would recommend using it in conjunction with the above
-methods so that you are protected even if your firewall is not active
-for some reason.
-</p><p>
-If you are setting up a firewall then you need to know what TCP and
-UDP ports to allow and block. Samba uses the following:
-</p><pre class="programlisting">
- UDP/137 - used by nmbd
- UDP/138 - used by nmbd
- TCP/139 - used by smbd
- TCP/445 - used by smbd
-</pre><p>
-The last one is important as many older firewall setups may not be
-aware of it, given that this port was only added to the protocol in
-recent years.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2884164"></a>Using a IPC$ share deny</h2></div></div><p>
-If the above methods are not suitable, then you could also place a
-more specific deny on the IPC$ share that is used in the recently
-discovered security hole. This allows you to offer access to other
-shares while denying access to IPC$ from potentially untrustworthy
-hosts.
-</p><p>
-To do that you could use:
-</p><pre class="programlisting">
- [ipc$]
- hosts allow = 192.168.115.0/24 127.0.0.1
- hosts deny = 0.0.0.0/0
-</pre><p>
-this would tell Samba that IPC$ connections are not allowed from
-anywhere but the two listed places (localhost and a local
-subnet). Connections to other shares would still be allowed. As the
-IPC$ share is the only share that is always accessible anonymously
-this provides some level of protection against attackers that do not
-know a username/password for your host.
-</p><p>
-If you use this method then clients will be given a 'access denied'
-reply when they try to access the IPC$ share. That means that those
-clients will not be able to browse shares, and may also be unable to
-access some other resources.
-</p><p>
-This is not recommended unless you cannot use one of the other
-methods listed above for some reason.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2883724"></a>NTLMv2 Security</h2></div></div><p>
-To configure NTLMv2 authentication the following registry keys are worth knowing about:
-</p><p>
-</p><pre class="programlisting">
- [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa]
- &quot;lmcompatibilitylevel&quot;=dword:00000003
-
- 0x3 - Send NTLMv2 response only. Clients will use NTLMv2 authentication,
- use NTLMv2 session security if the server supports it. Domain
- controllers accept LM, NTLM and NTLMv2 authentication.
-
- [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0]
- &quot;NtlmMinClientSec&quot;=dword:00080000
-
- 0x80000 - NTLMv2 session security. If either NtlmMinClientSec or
- NtlmMinServerSec is set to 0x80000, the connection will fail if NTLMv2
- session security is not negotiated.
-</pre><p>
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2883760"></a>Upgrading Samba</h2></div></div><p>
-Please check regularly on <a href="http://www.samba.org/" target="_top">http://www.samba.org/</a> for updates and
-important announcements. Occasionally security releases are made and
-it is highly recommended to upgrade Samba when a security vulnerability
-is discovered.
-</p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="unicode"></a>Chapter25.Unicode/Charsets</h2></div><div><div class="author"><h3 class="author">Jelmer R. Vernooij</h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt>&lt;<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author">TAKAHASHI Motonobu</h3><div class="affiliation"><div class="address"><p><tt>&lt;<a href="mailto:monyo@home.monyo.com">monyo@home.monyo.com</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate">25 March 2003</p></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2884358">What are charsets and unicode?</a></dt><dt><a href="#id2884428">Samba and charsets</a></dt><dt><a href="#id2884517">Conversion from old names</a></dt><dt><a href="#id2884562">Japanese charsets</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2884358"></a>What are charsets and unicode?</h2></div></div><p>
-Computers communicate in numbers. In texts, each number will be
-translated to a corresponding letter. The meaning that will be assigned
-to a certain number depends on the <span class="emphasis"><em>character set(charset)
-</em></span> that is used.
-A charset can be seen as a table that is used to translate numbers to
-letters. Not all computers use the same charset (there are charsets
-with German umlauts, Japanese characters, etc). Usually a charset contains
-256 characters, which means that storing a character with it takes
-exactly one byte. </p><p>
-There are also charsets that support even more characters,
-but those need twice(or even more) as much storage space. These
-charsets can contain <b>256 * 256 = 65536</b> characters, which
-is more then all possible characters one could think of. They are called
-multibyte charsets (because they use more then one byte to
-store one character).
-</p><p>
-A standardised multibyte charset is unicode, info is available at
-<a href="http://www.unicode.org/" target="_top">www.unicode.org</a>.
-A big advantage of using a multibyte charset is that you only need one; no
-need to make sure two computers use the same charset when they are
-communicating.
-</p><p>Old windows clients used to use single-byte charsets, named
-'codepages' by microsoft. However, there is no support for
-negotiating the charset to be used in the smb protocol. Thus, you
-have to make sure you are using the same charset when talking to an old client.
-Newer clients (Windows NT, 2K, XP) talk unicode over the wire.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2884428"></a>Samba and charsets</h2></div></div><p>
-As of samba 3.0, samba can (and will) talk unicode over the wire. Internally,
-samba knows of three kinds of character sets:
-</p><div class="variablelist"><dl><dt><span class="term">unix charset</span></dt><dd><p>
- This is the charset used internally by your operating system.
- The default is <tt>ASCII</tt>, which is fine for most
- systems.
- </p></dd><dt><span class="term">display charset</span></dt><dd><p>This is the charset samba will use to print messages
- on your screen. It should generally be the same as the <b>unix charset</b>.
- </p></dd><dt><span class="term">dos charset</span></dt><dd><p>This is the charset samba uses when communicating with
- DOS and Windows 9x clients. It will talk unicode to all newer clients.
- The default depends on the charsets you have installed on your system.
- Run <b>testparm -v | grep &quot;dos charset&quot;</b> to see
- what the default is on your system.
- </p></dd></dl></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2884517"></a>Conversion from old names</h2></div></div><p>Because previous samba versions did not do any charset conversion,
-characters in filenames are usually not correct in the unix charset but only
-for the local charset used by the DOS/Windows clients.</p><p>The following script from Steve Langasek converts all
-filenames from CP850 to the iso8859-15 charset.</p><p>
-<tt>#</tt><b><tt>find <i><tt>/path/to/share</tt></i> -type f -exec bash -c 'CP=&quot;{}&quot;; ISO=`echo -n &quot;$CP&quot; | iconv -f cp850 \
- -t iso8859-15`; if [ &quot;$CP&quot; != &quot;$ISO&quot; ]; then mv &quot;$CP&quot; &quot;$ISO&quot;; fi' \;
-</tt></b>
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2884562"></a>Japanese charsets</h2></div></div><p>Samba doesn't work correctly with Japanese charsets yet. Here are
-points of attention when setting it up:</p><div class="itemizedlist"><ul type="disc"><li><p>You should set <b>mangling method =
-hash</b></p></li><li><p>There are various iconv() implementations around and not
-all of them work equally well. glibc2's iconv() has a critical problem
-in CP932. libiconv-1.8 works with CP932 but still has some problems and
-does not work with EUC-JP.</p></li><li><p>You should set <b>dos charset = CP932</b>, not
-Shift_JIS, SJIS...</p></li><li><p>Currently only <b>unix charset = CP932</b>
-will work (but still has some problems...) because of iconv() issues.
-<b>unix charset = EUC-JP</b> doesn't work well because of
-iconv() issues.</p></li><li><p>Currently Samba 3.0 does not support <b>unix charset
-= UTF8-MAC/CAP/HEX/JIS*</b></p></li></ul></div><p>More information (in Japanese) is available at: <a href="http://www.atmarkit.co.jp/flinux/special/samba3/samba3a.html" target="_top">http://www.atmarkit.co.jp/flinux/special/samba3/samba3a.html</a>.</p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="locking"></a>Chapter26.File and Record Locking</h2></div><div><div class="author"><h3 class="author">Jeremy Allison</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt>&lt;<a href="mailto:jra@samba.org">jra@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author">Jelmer R. Vernooij</h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt>&lt;<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author">John H. Terpstra</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt>&lt;<a href="mailto:jht@samba.org">jht@samba.org</a>&gt;</tt></p></div></div></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2884210">Discussion</a></dt><dt><a href="#id2884872">Samba Opportunistic Locking Control</a></dt><dt><a href="#id2884987">MS Windows Opportunistic Locking and Caching Controls</a></dt><dd><dl><dt><a href="#id2885212">Workstation Service Entries</a></dt><dt><a href="#id2885239">Server Service Entries</a></dt></dl></dd><dt><a href="#id2885320">Persistent Data Corruption</a></dt><dt><a href="#id2885350">Additional Reading</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2884210"></a>Discussion</h2></div></div><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 <span class="emphasis"><em>record locking</em></span> which allows a client to lock
-a range of bytes in a open file. The second is the <span class="emphasis"><em>deny modes</em></span>
-that are specified when a file is open.
-</p><p>
-Record locking semantics under Unix is very different from record locking under
-Windows. Versions of Samba before 2.2 have tried to use the native fcntl() unix
-system call to implement proper record locking between different Samba clients.
-This can not be fully correct due to several reasons. The simplest is the fact
-that a Windows client is allowed to lock a byte range up to 2^32 or 2^64,
-depending on the client OS. The unix locking only supports byte ranges up to 2^31.
-So it is not possible to correctly satisfy a lock request above 2^31. There are
-many more differences, too many to be listed here.
-</p><p>
-Samba 2.2 and above implements record locking completely independent of the
-underlying unix system. If a byte range lock that the client requests happens
-to fall into the range 0-2^31, Samba hands this request down to the Unix system.
-All other locks can not be seen by unix anyway.
-</p><p>
-Strictly a SMB server should check for locks before every read and write call on
-a file. Unfortunately with the way fcntl() works this can be slow and may overstress
-the rpc.lockd. It is also almost always unnecessary as clients are supposed to
-independently make locking calls before reads and writes anyway if locking is
-important to them. By default Samba only makes locking calls when explicitly asked
-to by a client, but if you set <span class="emphasis"><em>strict locking = yes</em></span> then it
-will make lock checking calls on every read and write.
-</p><p>
-You can also disable by range locking completely using <span class="emphasis"><em>locking = no</em></span>.
-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 <span class="emphasis"><em>deny modes</em></span>. These
-are set by an application when it opens a file to determine what types of
-access should be allowed simultaneously with its open. A client may ask for
-DENY_NONE, DENY_READ, DENY_WRITE or DENY_ALL. There are also special compatibility
-modes called DENY_FCB and DENY_DOS.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2884872"></a>Samba Opportunistic Locking Control</h2></div></div><p>
-Opportunistic locking essentially means that the client is allowed to download and cache
-a file on their hard drive while making changes; if a second client wants to access the
-file, the first client receives a break and must synchronise the file back to the server.
-This can give significant performance gains in some cases; some programs insist on
-synchronising the contents of the entire file back to the server for a single change.
-</p><p>
-Level1 Oplocks (aka just plain &quot;oplocks&quot;) is another term for opportunistic locking.
-</p><p>
-Level2 Oplocks provids opportunistic locking for a file that will be treated as
-<span class="emphasis"><em>read only</em></span>. Typically this is used on files that are read-only or
-on files that the client has no initial intention to write to at time of opening the file.
-</p><p>
-Kernel Oplocks are essentially a method that allows the Linux kernel to co-exist with
-Samba's oplocked files, although this has provided better integration of MS Windows network
-file locking with the under lying OS, SGI IRIX and Linux are the only two OS's that are
-oplock aware at this time.
-</p><p>
-Unless your system supports kernel oplocks, you should disable oplocks if you are
-accessing the same files from both Unix/Linux and SMB clients. Regardless, oplocks should
-always be disabled if you are sharing a database file (e.g., Microsoft Access) between
-multiple clients, as any break the first client receives will affect synchronisation of
-the entire file (not just the single record), which will result in a noticable performance
-impairment and, more likely, problems accessing the database in the first place. Notably,
-Microsoft Outlook's personal folders (*.pst) react very badly to oplocks. If in doubt,
-disable oplocks and tune your system from that point.
-</p><p>
-If client-side caching is desirable and reliable on your network, you will benefit from
-turning on oplocks. If your network is slow and/or unreliable, or you are sharing your
-files among other file sharing mechanisms (e.g., NFS) or across a WAN, or multiple people
-will be accessing the same files frequently, you probably will not benefit from the overhead
-of your client sending oplock breaks and will instead want to disable oplocks for the share.
-</p><p>
-Another factor to consider is the perceived performance of file access. If oplocks provide no
-measurable speed benefit on your network, it might not be worth the hassle of dealing with them.
-</p><p>
-You can disable oplocks on a per-share basis with the following:
-
-</p><pre class="programlisting">
- oplocks = False
- level2 oplocks = False
-</pre><p>
-
-Alternately, you could disable oplocks on a per-file basis within the share:
-
-</p><pre class="programlisting">
- veto oplock files = /*.mdb/*.MDB/*.dbf/*.DBF/
-</pre><p>
-</p><p>
-If you are experiencing problems with oplocks as apparent from Samba's log entries,
-you may want to play it safe and disable oplocks and level2 oplocks.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2884987"></a>MS Windows Opportunistic Locking and Caching Controls</h2></div></div><p>
-There is a known issue when running applications (like Norton Anti-Virus) on a Windows 2000/ XP
-workstation computer that can affect any application attempting to access shared database files
-across a network. This is a result of a default setting configured in the Windows 2000/XP
-operating system known as <span class="emphasis"><em>Opportunistic Locking</em></span>. When a workstation
-attempts to access shared data files located on another Windows 2000/XP computer,
-the Windows 2000/XP operating system will attempt to increase performance by locking the
-files and caching information locally. When this occurs, the application is unable to
-properly function, which results in an <span class="emphasis"><em>Access Denied</em></span>
- error message being displayed during network operations.
-</p><p>
-All Windows operating systems in the NT family that act as database servers for data files
-(meaning that data files are stored there and accessed by other Windows PCs) may need to
-have opportunistic locking disabled in order to minimize the risk of data file corruption.
-This includes Windows 9x/Me, Windows NT, Windows 200x and Windows XP.
-</p><p>
-If you are using a Windows NT family workstation in place of a server, you must also
-disable opportunistic locking (oplocks) on that workstation. For example, if you use a
-PC with the Windows NT Workstation operating system instead of Windows NT Server, and you
-have data files located on it that are accessed from other Windows PCs, you may need to
-disable oplocks on that system.
-</p><p>
-The major difference is the location in the Windows registry where the values for disabling
-oplocks are entered. Instead of the LanManServer location, the LanManWorkstation location
-may be used.
-</p><p>
-You can verify (or change or add, if necessary) this Registry value using the Windows
-Registry Editor. When you change this registry value, you will have to reboot the PC
-to ensure that the new setting goes into effect.
-</p><p>
-The location of the client registry entry for opportunistic locking has changed in
-Windows 2000 from the earlier location in Microsoft Windows NT.
-</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-Windows 2000 will still respect the EnableOplocks registry value used to disable oplocks
-in earlier versions of Windows.
-</p></div><p>
-You can also deny the granting of opportunistic locks by changing the following registry entries:
-</p><p>
-</p><pre class="programlisting">
- HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MRXSmb\Parameters\
-
- OplocksDisabled REG_DWORD 0 or 1
- Default: 0 (not disabled)
-</pre><p>
-</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-The OplocksDisabled registry value configures Windows clients to either request or not
-request opportunistic locks on a remote file. To disable oplocks, the value of
- OplocksDisabled must be set to 1.
-</p></div><p>
-</p><pre class="programlisting">
- HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters
-
- EnableOplocks REG_DWORD 0 or 1
- Default: 1 (Enabled by Default)
-
- EnableOpLockForceClose REG_DWORD 0 or 1
- Default: 0 (Disabled by Default)
-</pre><p>
-</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-The EnableOplocks value configures Windows-based servers (including Workstations sharing
-files) to allow or deny opportunistic locks on local files.
-</p></div><p>
-To force closure of open oplocks on close or program exit EnableOpLockForceClose must be set to 1.
-</p><p>
-An illustration of how level II oplocks work:
-</p><div class="itemizedlist"><ul type="disc"><li><p>
- Station 1 opens the file, requesting oplock.
- </p></li><li><p>
- Since no other station has the file open, the server grants station 1 exclusive oplock.
- </p></li><li><p>
- Station 2 opens the file, requesting oplock.
- </p></li><li><p>
- Since station 1 has not yet written to the file, the server asks station 1 to Break
- to Level II Oplock.
- </p></li><li><p>
- Station 1 complies by flushing locally buffered lock information to the server.
- </p></li><li><p>
- Station 1 informs the server that it has Broken to Level II Oplock (alternatively,
- station 1 could have closed the file).
- </p></li><li><p>
- The server responds to station 2's open request, granting it level II oplock.
- Other stations can likewise open the file and obtain level II oplock.
- </p></li><li><p>
- Station 2 (or any station that has the file open) sends a write request SMB.
- The server returns the write response.
- </p></li><li><p>
- The server asks all stations that have the file open to Break to None, meaning no
- station holds any oplock on the file. Because the workstations can have no cached
- writes or locks at this point, they need not respond to the break-to-none advisory;
- all they need do is invalidate locally cashed read-ahead data.
- </p></li></ul></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2885212"></a>Workstation Service Entries</h3></div></div><pre class="programlisting">
- \HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters
-
- UseOpportunisticLocking REG_DWORD 0 or 1
- Default: 1 (true)
-</pre><p>
-Indicates whether the redirector should use opportunistic-locking (oplock) performance
-enhancement. This parameter should be disabled only to isolate problems.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2885239"></a>Server Service Entries</h3></div></div><pre class="programlisting">
- \HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters
-
- EnableOplocks REG_DWORD 0 or 1
- Default: 1 (true)
-</pre><p>
-Specifies whether the server allows clients to use oplocks on files. Oplocks are a
-significant performance enhancement, but have the potential to cause lost cached
-data on some networks, particularly wide-area networks.
-</p><pre class="programlisting">
- MinLinkThroughput REG_DWORD 0 to infinite bytes per second
- Default: 0
-</pre><p>
-Specifies the minimum link throughput allowed by the server before it disables
-raw and opportunistic locks for this connection.
-</p><pre class="programlisting">
- MaxLinkDelay REG_DWORD 0 to 100,000 seconds
- Default: 60
-</pre><p>
-Specifies the maximum time allowed for a link delay. If delays exceed this number,
-the server disables raw I/O and opportunistic locking for this connection.
-</p><pre class="programlisting">
- OplockBreakWait REG_DWORD 10 to 180 seconds
- Default: 35
-</pre><p>
-Specifies the time that the server waits for a client to respond to an oplock break
-request. Smaller values can allow detection of crashed clients more quickly but can
-potentially cause loss of cached data.
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2885320"></a>Persistent Data Corruption</h2></div></div><p>
-If you have applied all of the settings discussed in this paper but data corruption problems
-and other symptoms persist, here are some additional things to check out:
-</p><p>
-We have credible reports from developers that faulty network hardware, such as a single
-faulty network card, can cause symptoms similar to read caching and data corruption.
-If you see persistent data corruption even after repeated reindexing, you may have to
-rebuild the data files in question. This involves creating a new data file with the
-same definition as the file to be rebuilt and transferring the data from the old file
-to the new one. There are several known methods for doing this that can be found in
-our Knowledge Base.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2885350"></a>Additional Reading</h2></div></div><p>
-You may want to check for an updated version of this white paper on our Web site from
-time to time. Many of our white papers are updated as information changes. For those papers,
-the Last Edited date is always at the top of the paper.
-</p><p>
-Section of the Microsoft MSDN Library on opportunistic locking:
-</p><p>
-Opportunistic Locks, Microsoft Developer Network (MSDN), Windows Development &gt;
-Windows Base Services &gt; Files and I/O &gt; SDK Documentation &gt; File Storage &gt; File Systems
-&gt; About File Systems &gt; Opportunistic Locks, Microsoft Corporation.
-<a href="http://msdn.microsoft.com/library/en-us/fileio/storage_5yk3.asp" target="_top">http://msdn.microsoft.com/library/en-us/fileio/storage_5yk3.asp</a>
-</p><p>
-Microsoft Knowledge Base Article Q224992 &quot;Maintaining Transactional Integrity with OPLOCKS&quot;,
-Microsoft Corporation, April 1999, <a href="=http://support.microsoft.com/default.aspx?scid=kb;en-us;Q224992" target="_top">http://support.microsoft.com/default.aspx?scid=kb;en-us;Q224992</a>.
-</p><p>
-Microsoft Knowledge Base Article Q296264 &quot;Configuring Opportunistic Locking in Windows 2000&quot;,
-Microsoft Corporation, April 2001, <a href="http://support.microsoft.com/default.aspx?scid=kb;en-us;Q296264" target="_top">http://support.microsoft.com/default.aspx?scid=kb;en-us;Q296264</a>.
-</p><p>
-Microsoft Knowledge Base Article Q129202 &quot;PC Ext: Explanation of Opportunistic Locking on Windows NT&quot;,
- Microsoft Corporation, April 1995, <a href="http://support.microsoft.com/default.aspx?scid=kb;en-us;Q129202" target="_top">http://support.microsoft.com/default.aspx?scid=kb;en-us;Q129202</a>.
-</p></div></div></div><div class="part" lang="en"><div class="titlepage"><div><h1 class="title"><a name="troubleshooting"></a>Troubleshooting</h1></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt>27. <a href="#diagnosis">The samba checklist</a></dt><dd><dl><dt><a href="#id2884776">Introduction</a></dt><dt><a href="#id2884810">Assumptions</a></dt><dt><a href="#id2793401">The tests</a></dt><dt><a href="#id2886854">Still having troubles?</a></dt></dl></dd><dt>28. <a href="#problems">Analysing and solving samba problems</a></dt><dd><dl><dt><a href="#id2790687">Diagnostics tools</a></dt><dt><a href="#id2887096">Installing 'Network Monitor' on an NT Workstation or a Windows 9x box</a></dt><dt><a href="#id2887237">Useful URL's</a></dt><dt><a href="#id2887343">Getting help from the mailing lists</a></dt><dt><a href="#id2887497">How to get off the mailinglists</a></dt></dl></dd><dt>29. <a href="#bugreport">Reporting Bugs</a></dt><dd><dl><dt><a href="#id2887016">Introduction</a></dt><dt><a href="#id2886937">General info</a></dt><dt><a href="#id2887713">Debug levels</a></dt><dt><a href="#id2887849">Internal errors</a></dt><dt><a href="#id2887942">Attaching to a running process</a></dt><dt><a href="#id2887989">Patches</a></dt></dl></dd></dl></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="diagnosis"></a>Chapter27.The samba checklist</h2></div><div><div class="author"><h3 class="author">Andrew Tridgell</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt>&lt;<a href="mailto:tridge@samba.org">tridge@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author">Jelmer R. Vernooij</h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt>&lt;<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate">Wed Jan 15</p></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2884776">Introduction</a></dt><dt><a href="#id2884810">Assumptions</a></dt><dt><a href="#id2793401">The tests</a></dt><dt><a href="#id2886854">Still having troubles?</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2884776"></a>Introduction</h2></div></div><p>
-This file contains a list of tests you can perform to validate your
-Samba server. It also tells you what the likely cause of the problem
-is if it fails any one of these steps. If it passes all these tests
-then it is probably working fine.
-</p><p>
-You should do ALL the tests, in the order shown. We have tried to
-carefully choose them so later tests only use capabilities verified in
-the earlier tests. However, do not stop at the first error as there
-have been some instances when continuing with the tests has helped
-to solve a problem.
-</p><p>
-If you send one of the samba mailing lists an email saying &quot;it doesn't work&quot;
-and you have not followed this test procedure then you should not be surprised
-if your email is ignored.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2884810"></a>Assumptions</h2></div></div><p>
-In all of the tests it is assumed you have a Samba server called
-BIGSERVER and a PC called ACLIENT both in workgroup TESTGROUP.
-</p><p>
-The procedure is similar for other types of clients.
-</p><p>
-It is also assumed you know the name of an available share in your
-<tt>smb.conf</tt>. I will assume this share is called <i><tt>tmp</tt></i>.
-You can add a <i><tt>tmp</tt></i> share like this by adding the
-following to <tt>smb.conf</tt>:
-</p><pre class="programlisting">
-
-[tmp]
- comment = temporary files
- path = /tmp
- read only = yes
-
-</pre><p>
-</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-These tests assume version 3.0 or later of the samba suite.
-Some commands shown did not exist in earlier versions.
-</p></div><p>
-Please pay attention to the error messages you receive. If any error message
-reports that your server is being unfriendly you should first check that your
-IP name resolution is correctly set up. eg: Make sure your <tt>/etc/resolv.conf</tt>
-file points to name servers that really do exist.
-</p><p>
-Also, if you do not have DNS server access for name resolution please check
-that the settings for your <tt>smb.conf</tt> file results in <b>dns proxy = no</b>. The
-best way to check this is with <b><tt>testparm smb.conf</tt></b>.
-</p><p>
-It is helpful to monitor the log files during testing by using the
-<b>tail -F <i><tt>log_file_name</tt></i></b> in a separate
-terminal console (use ctrl-alt-F1 through F6 or multiple terminals in X).
-Relevant log files can be found (for default installations) in
-<tt>/usr/local/samba/var</tt>. Also, connection logs from
-machines can be found here or possibly in <tt>/var/log/samba</tt>
-depending on how or if you specified logging in your <tt>smb.conf</tt> file.
-</p><p>
-If you make changes to your <tt>smb.conf</tt> file while going through these test,
-don't forget to restart smbd and nmbd.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2793401"></a>The tests</h2></div></div><div class="procedure"><p class="title"><b>Procedure27.1.Diagnosing your samba server</b></p><ol type="1"><li><p>
-In the directory in which you store your <tt>smb.conf</tt> file, run the command
-<b><tt>testparm smb.conf</tt></b>. If it reports any errors then your <tt>smb.conf</tt>
-configuration file is faulty.
-</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-Your <tt>smb.conf</tt> file may be located in: <tt>/etc/samba</tt>
-Or in: <tt>/usr/local/samba/lib</tt>
-</p></div></li><li><p>
-Run the command <b><tt>ping BIGSERVER</tt></b> from the PC and
-<b><tt>ping ACLIENT</tt></b> from
-the unix box. If you don't get a valid response then your TCP/IP
-software is not correctly installed.
-</p><p>
-Note that you will need to start a &quot;dos prompt&quot; window on the PC to
-run ping.
-</p><p>
-If you get a message saying &quot;host not found&quot; or similar then your DNS
-software or <tt>/etc/hosts</tt> file is not correctly setup.
-It is possible to
-run samba without DNS entries for the server and client, but I assume
-you do have correct entries for the remainder of these tests.
-</p><p>
-Another reason why ping might fail is if your host is running firewall
-software. You will need to relax the rules to let in the workstation
-in question, perhaps by allowing access from another subnet (on Linux
-this is done via the ipfwadm program.)
-</p><p>
-Note: Modern Linux distributions install ipchains/iptables by default.
-This is a common problem that is often overlooked.
-</p></li><li><p>
-Run the command <b><tt>smbclient -L BIGSERVER</tt></b> on the unix box. You
-should get a list of available shares back.
-</p><p>
-If you get a error message containing the string &quot;Bad password&quot; then
-you probably have either an incorrect <b>hosts allow</b>,
-<b>hosts deny</b> or <b>valid users</b> line in your
-<tt>smb.conf</tt>, or your guest account is not
-valid. Check what your guest account is using testparm and
-temporarily remove any <b>hosts allow</b>, <b>hosts deny</b>, <b>valid users</b> or <b>invalid users</b> lines.
-</p><p>
-If you get a &quot;connection refused&quot; response then the smbd server may
-not be running. If you installed it in inetd.conf then you probably edited
-that file incorrectly. If you installed it as a daemon then check that
-it is running, and check that the netbios-ssn port is in a LISTEN
-state using <b><tt>netstat -a</tt></b>.
-</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-Some Unix / Linux systems use <b>xinetd</b> in place of
-<b>inetd</b>. Check your system documentation for the location
-of the control file/s for your particular system implementation of
-this network super daemon.
-</p></div><p>
-If you get a &quot;session request failed&quot; then the server refused the
-connection. If it says &quot;Your server software is being unfriendly&quot; then
-its probably because you have invalid command line parameters to smbd,
-or a similar fatal problem with the initial startup of smbd. Also
-check your config file (<tt>smb.conf</tt>) for syntax errors with testparm
-and that the various directories where samba keeps its log and lock
-files exist.
-</p><p>
-There are a number of reasons for which smbd may refuse or decline
-a session request. The most common of these involve one or more of
-the following <tt>smb.conf</tt> file entries:
-</p><pre class="programlisting">
- hosts deny = ALL
- hosts allow = xxx.xxx.xxx.xxx/yy
- bind interfaces only = Yes
-</pre><p>
-In the above, no allowance has been made for any session requests that
-will automatically translate to the loopback adaptor address 127.0.0.1.
-To solve this problem change these lines to:
-</p><pre class="programlisting">
- hosts deny = ALL
- hosts allow = xxx.xxx.xxx.xxx/yy 127.
-</pre><p>
-Do NOT use the <b>bind interfaces only</b> parameter where you
-may wish to
-use the samba password change facility, or where smbclient may need to
-access a local service for name resolution or for local resource
-connections. (Note: the <b>bind interfaces only</b> parameter deficiency
-where it will not allow connections to the loopback address will be
-fixed soon).
-</p><p>
-Another common cause of these two errors is having something already running
-on port 139, such as Samba (ie: smbd is running from inetd already) or
-something like Digital's Pathworks. Check your <tt>inetd.conf</tt> file before trying
-to start smbd as a daemon, it can avoid a lot of frustration!
-</p><p>
-And yet another possible cause for failure of this test is when the subnet mask
-and / or broadcast address settings are incorrect. Please check that the
-network interface IP Address / Broadcast Address / Subnet Mask settings are
-correct and that Samba has correctly noted these in the <tt>log.nmb</tt> file.
-</p></li><li><p>
-Run the command <b><tt>nmblookup -B BIGSERVER __SAMBA__</tt></b>. You should get the
-IP address of your Samba server back.
-</p><p>
-If you don't then nmbd is incorrectly installed. Check your <tt>inetd.conf</tt>
-if you run it from there, or that the daemon is running and listening
-to udp port 137.
-</p><p>
-One common problem is that many inetd implementations can't take many
-parameters on the command line. If this is the case then create a
-one-line script that contains the right parameters and run that from
-inetd.
-</p></li><li><p>run the command <b><tt>nmblookup -B ACLIENT '*'</tt></b></p><p>
-You should get the PCs IP address back. If you don't then the client
-software on the PC isn't installed correctly, or isn't started, or you
-got the name of the PC wrong.
-</p><p>
-If ACLIENT doesn't resolve via DNS then use the IP address of the
-client in the above test.
-</p></li><li><p>
-Run the command <b><tt>nmblookup -d 2 '*'</tt></b>
-</p><p>
-This time we are trying the same as the previous test but are trying
-it via a broadcast to the default broadcast address. A number of
-Netbios/TCPIP hosts on the network should respond, although Samba may
-not catch all of the responses in the short time it listens. You
-should see &quot;got a positive name query response&quot; messages from several
-hosts.
-</p><p>
-If this doesn't give a similar result to the previous test then
-nmblookup isn't correctly getting your broadcast address through its
-automatic mechanism. In this case you should experiment with the
-<b>interfaces</b> option in <tt>smb.conf</tt> to manually configure your IP
-address, broadcast and netmask.
-</p><p>
-If your PC and server aren't on the same subnet then you will need to
-use the <i><tt>-B</tt></i> option to set the broadcast address to that of the PCs
-subnet.
-</p><p>
-This test will probably fail if your subnet mask and broadcast address are
-not correct. (Refer to TEST 3 notes above).
-</p></li><li><p>
-Run the command <b><tt>smbclient //BIGSERVER/TMP</tt></b>. You should
-then be prompted for a password. You should use the password of the account
-you are logged into the unix box with. If you want to test with
-another account then add the <i><tt>-U <i><tt>accountname</tt></i></tt></i> option to the end of
-the command line. eg:
-<b><tt>smbclient //bigserver/tmp -Ujohndoe</tt></b>
-</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-It is possible to specify the password along with the username
-as follows:
-<b><tt>smbclient //bigserver/tmp -Ujohndoe%secret</tt></b>
-</p></div><p>
-Once you enter the password you should get the <tt>smb&gt;</tt> prompt. If you
-don't then look at the error message. If it says &quot;invalid network
-name&quot; then the service &quot;tmp&quot; is not correctly setup in your <tt>smb.conf</tt>.
-</p><p>
-If it says &quot;bad password&quot; then the likely causes are:
-</p><div class="orderedlist"><ol type="1"><li><p>
- you have shadow passords (or some other password system) but didn't
- compile in support for them in smbd
- </p></li><li><p>
- your <b>valid users</b> configuration is incorrect
- </p></li><li><p>
- you have a mixed case password and you haven't enabled the <b>password
- level</b> option at a high enough level
- </p></li><li><p>
- the <b>path =</b> line in <tt>smb.conf</tt> is incorrect. Check it with testparm
- </p></li><li><p>
- you enabled password encryption but didn't create the SMB encrypted
- password file
- </p></li></ol></div><p>
-Once connected you should be able to use the commands
-<b>dir</b> <b>get</b> <b>put</b> etc.
-Type <b>help <i><tt>command</tt></i></b> for instructions. You should
-especially check that the amount of free disk space shown is correct
-when you type <b>dir</b>.
-</p></li><li><p>
-On the PC, type the command <b><tt>net view \\BIGSERVER</tt></b>. You will
-need to do this from within a &quot;dos prompt&quot; window. You should get back a
-list of available shares on the server.
-</p><p>
-If you get a &quot;network name not found&quot; or similar error then netbios
-name resolution is not working. This is usually caused by a problem in
-nmbd. To overcome it you could do one of the following (you only need
-to choose one of them):
-</p><div class="orderedlist"><ol type="1"><li><p>
- fixup the nmbd installation
-</p></li><li><p>
- add the IP address of BIGSERVER to the <b>wins server</b> box in the
- advanced tcp/ip setup on the PC.
-</p></li><li><p>
- enable windows name resolution via DNS in the advanced section of
- the tcp/ip setup
-</p></li><li><p>
- add BIGSERVER to your lmhosts file on the PC.
-</p></li></ol></div><p>
-If you get a &quot;invalid network name&quot; or &quot;bad password error&quot; then the
-same fixes apply as they did for the <b><tt>smbclient -L</tt></b> test above. In
-particular, make sure your <b>hosts allow</b> line is correct (see the man
-pages)
-</p><p>
-Also, do not overlook that fact that when the workstation requests the
-connection to the samba server it will attempt to connect using the
-name with which you logged onto your Windows machine. You need to make
-sure that an account exists on your Samba server with that exact same
-name and password.
-</p><p>
-If you get &quot;specified computer is not receiving requests&quot; or similar
-it probably means that the host is not contactable via tcp services.
-Check to see if the host is running tcp wrappers, and if so add an entry in
-the <tt>hosts.allow</tt> file for your client (or subnet, etc.)
-</p></li><li><p>
-Run the command <b><tt>net use x: \\BIGSERVER\TMP</tt></b>. You should
-be prompted for a password then you should get a &quot;command completed
-successfully&quot; message. If not then your PC software is incorrectly
-installed or your smb.conf is incorrect. make sure your <b>hosts allow</b>
-and other config lines in <tt>smb.conf</tt> are correct.
-</p><p>
-It's also possible that the server can't work out what user name to
-connect you as. To see if this is the problem add the line <b>user =
-<i><tt>username</tt></i></b> to the <b>[tmp]</b> section of
-<tt>smb.conf</tt> where <i><tt>username</tt></i> is the
-username corresponding to the password you typed. If you find this
-fixes things you may need the username mapping option.
-</p><p>
-It might also be the case that your client only sends encrypted passwords
-and you have <b>encrypt passwords = no</b> in <tt>smb.conf</tt>
-Turn it back on to fix.
-</p></li><li><p>
-Run the command <b><tt>nmblookup -M <i><tt>testgroup</tt></i></tt></b> where
-<i><tt>testgroup</tt></i> is the name of the workgroup that your Samba server and
-Windows PCs belong to. You should get back the IP address of the
-master browser for that workgroup.
-</p><p>
-If you don't then the election process has failed. Wait a minute to
-see if it is just being slow then try again. If it still fails after
-that then look at the browsing options you have set in <tt>smb.conf</tt>. Make
-sure you have <b>preferred master = yes</b> to ensure that
-an election is held at startup.
-</p></li><li><p>
-&gt;From file manager try to browse the server. Your samba server should
-appear in the browse list of your local workgroup (or the one you
-specified in smb.conf). You should be able to double click on the name
-of the server and get a list of shares. If you get a &quot;invalid
-password&quot; error when you do then you are probably running WinNT and it
-is refusing to browse a server that has no encrypted password
-capability and is in user level security mode. In this case either set
-<b>security = server</b> AND
-<b>password server = Windows_NT_Machine</b> in your
-<tt>smb.conf</tt> file, or make sure <b>encrypted passwords</b> is
-set to &quot;yes&quot;.
-</p></li></ol></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2886854"></a>Still having troubles?</h2></div></div><p>Read the chapter on
-<a href="#problems" title="Chapter28.Analysing and solving samba problems">Analysing and Solving Problems</a>.
-</p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="problems"></a>Chapter28.Analysing and solving samba problems</h2></div><div><div class="author"><h3 class="author">Gerald (Jerry) Carter</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt>&lt;<a href="mailto:jerry@samba.org">jerry@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author">Jelmer R. Vernooij</h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt>&lt;<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author">David Bannon</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt>&lt;<a href="mailto:dbannon@samba.org">dbannon@samba.org</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate">8 Apr 2003</p></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2790687">Diagnostics tools</a></dt><dt><a href="#id2887096">Installing 'Network Monitor' on an NT Workstation or a Windows 9x box</a></dt><dt><a href="#id2887237">Useful URL's</a></dt><dt><a href="#id2887343">Getting help from the mailing lists</a></dt><dt><a href="#id2887497">How to get off the mailinglists</a></dt></dl></div><p>
-There are many sources of information available in the form
-of mailing lists, RFC's and documentation. The docs that come
-with the samba distribution contain very good explanations of
-general SMB topics such as browsing.</p><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2790687"></a>Diagnostics tools</h2></div></div><p>
-One of the best diagnostic tools for debugging problems is Samba itself.
-You can use the -d option for both smbd and nmbd to specify what
-'debug level' at which to run. See the man pages on smbd, nmbd and
-smb.conf for more information on debugging options. The debug
-level can range from 1 (the default) to 10 (100 for debugging passwords).
-</p><p>
-Another helpful method of debugging is to compile samba using the
-<b>gcc -g </b> flag. This will include debug
-information in the binaries and allow you to attach gdb to the
-running smbd / nmbd process. In order to attach gdb to an smbd
-process for an NT workstation, first get the workstation to make the
-connection. Pressing ctrl-alt-delete and going down to the domain box
-is sufficient (at least, on the first time you join the domain) to
-generate a 'LsaEnumTrustedDomains'. Thereafter, the workstation
-maintains an open connection, and therefore there will be an smbd
-process running (assuming that you haven't set a really short smbd
-idle timeout) So, in between pressing ctrl alt delete, and actually
-typing in your password, you can attach gdb and continue.
-</p><p>
-Some useful samba commands worth investigating:
-</p><div class="itemizedlist"><ul type="disc"><li><p>testparam | more</p></li><li><p>smbclient -L //{netbios name of server}</p></li></ul></div><p>
-An SMB enabled version of tcpdump is available from
-<a href="http://www.tcpdump.org/" target="_top">http://www.tcpdup.org/</a>.
-Ethereal, another good packet sniffer for Unix and Win32
-hosts, can be downloaded from <a href="http://www.ethereal.com/" target="_top">http://www.ethereal.com</a>.
-</p><p>
-For tracing things on the Microsoft Windows NT, Network Monitor
-(aka. netmon) is available on the Microsoft Developer Network CD's,
-the Windows NT Server install CD and the SMS CD's. The version of
-netmon that ships with SMS allows for dumping packets between any two
-computers (i.e. placing the network interface in promiscuous mode).
-The version on the NT Server install CD will only allow monitoring
-of network traffic directed to the local NT box and broadcasts on the
-local subnet. Be aware that Ethereal can read and write netmon
-formatted files.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2887096"></a>Installing 'Network Monitor' on an NT Workstation or a Windows 9x box</h2></div></div><p>
-Installing netmon on an NT workstation requires a couple
-of steps. The following are for installing Netmon V4.00.349, which comes
-with Microsoft Windows NT Server 4.0, on Microsoft Windows NT
-Workstation 4.0. The process should be similar for other versions of
-Windows NT / Netmon. You will need both the Microsoft Windows
-NT Server 4.0 Install CD and the Workstation 4.0 Install CD.
-</p><p>
-Initially you will need to install 'Network Monitor Tools and Agent'
-on the NT Server. To do this
-</p><div class="itemizedlist"><ul type="disc"><li><p>Goto Start - Settings - Control Panel -
- Network - Services - Add </p></li><li><p>Select the 'Network Monitor Tools and Agent' and
- click on 'OK'.</p></li><li><p>Click 'OK' on the Network Control Panel.
- </p></li><li><p>Insert the Windows NT Server 4.0 install CD
- when prompted.</p></li></ul></div><p>
-At this point the Netmon files should exist in
-<tt>%SYSTEMROOT%\System32\netmon\*.*</tt>.
-Two subdirectories exist as well, <tt>parsers\</tt>
-which contains the necessary DLL's for parsing the netmon packet
-dump, and <tt>captures\</tt>.
-</p><p>
-In order to install the Netmon tools on an NT Workstation, you will
-first need to install the 'Network Monitor Agent' from the Workstation
-install CD.
-</p><div class="itemizedlist"><ul type="disc"><li><p>Goto Start - Settings - Control Panel -
- Network - Services - Add</p></li><li><p>Select the 'Network Monitor Agent' and click
- on 'OK'.</p></li><li><p>Click 'OK' on the Network Control Panel.
- </p></li><li><p>Insert the Windows NT Workstation 4.0 install
- CD when prompted.</p></li></ul></div><p>
-Now copy the files from the NT Server in %SYSTEMROOT%\System32\netmon\*.*
-to %SYSTEMROOT%\System32\netmon\*.* on the Workstation and set
-permissions as you deem appropriate for your site. You will need
-administrative rights on the NT box to run netmon.
-</p><p>
-To install Netmon on a Windows 9x box install the network monitor agent
-from the Windows 9x CD (\admin\nettools\netmon). There is a readme
-file located with the netmon driver files on the CD if you need
-information on how to do this. Copy the files from a working
-Netmon installation.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2887237"></a>Useful URL's</h2></div></div><div class="itemizedlist"><ul type="disc"><li><p>Home of Samba site <a href="http://samba.org" target="_top">
- http://samba.org</a>. We have a mirror near you !</p></li><li><p> The <span class="emphasis"><em>Development</em></span> document
-on the Samba mirrors might mention your problem. If so,
-it might mean that the developers are working on it.</p></li><li><p>See how Scott Merrill simulates a BDC behavior at
- <a href="http://www.skippy.net/linux/smb-howto.html" target="_top">
- http://www.skippy.net/linux/smb-howto.html</a>. </p></li><li><p>Although 2.0.7 has almost had its day as a PDC, David Bannon will
- keep the 2.0.7 PDC pages at <a href="http://bioserve.latrobe.edu.au/samba" target="_top">
- http://bioserve.latrobe.edu.au/samba</a> going for a while yet.</p></li><li><p>Misc links to CIFS information
- <a href="http://samba.org/cifs/" target="_top">http://samba.org/cifs/</a></p></li><li><p>NT Domains for Unix <a href="http://mailhost.cb1.com/~lkcl/ntdom/" target="_top">
- http://mailhost.cb1.com/~lkcl/ntdom/</a></p></li><li><p>FTP site for older SMB specs:
- <a href="ftp://ftp.microsoft.com/developr/drg/CIFS/" target="_top">
- ftp://ftp.microsoft.com/developr/drg/CIFS/</a></p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2887343"></a>Getting help from the mailing lists</h2></div></div><p>
-There are a number of Samba related mailing lists. Go to <a href="http://samba.org" target="_top">http://samba.org</a>, click on your nearest mirror
-and then click on <b>Support</b> and then click on <b>
-Samba related mailing lists</b>.
-</p><p>
-For questions relating to Samba TNG go to
-<a href="http://www.samba-tng.org/" target="_top">http://www.samba-tng.org/</a>
-It has been requested that you don't post questions about Samba-TNG to the
-main stream Samba lists.</p><p>
-If you post a message to one of the lists please observe the following guide lines :
-</p><div class="itemizedlist"><ul type="disc"><li><p> Always remember that the developers are volunteers, they are
-not paid and they never guarantee to produce a particular feature at
-a particular time. Any time lines are 'best guess' and nothing more.
-</p></li><li><p> Always mention what version of samba you are using and what
-operating system its running under. You should probably list the
-relevant sections of your <tt>smb.conf</tt> file, at least the options
-in [global] that affect PDC support.</p></li><li><p>In addition to the version, if you obtained Samba via
-CVS mention the date when you last checked it out.</p></li><li><p> Try and make your question clear and brief, lots of long,
-convoluted questions get deleted before they are completely read !
-Don't post html encoded messages (if you can select colour or font
-size its html).</p></li><li><p> If you run one of those nifty 'I'm on holidays' things when
-you are away, make sure its configured to not answer mailing lists.
-</p></li><li><p> Don't cross post. Work out which is the best list to post to
-and see what happens, i.e. don't post to both samba-ntdom and samba-technical.
-Many people active on the lists subscribe to more
-than one list and get annoyed to see the same message two or more times.
-Often someone will see a message and thinking it would be better dealt
-with on another, will forward it on for you.</p></li><li><p>You might include <span class="emphasis"><em>partial</em></span>
-log files written at a debug level set to as much as 20.
-Please don't send the entire log but enough to give the context of the
-error messages.</p></li><li><p>(Possibly) If you have a complete netmon trace ( from the opening of
-the pipe to the error ) you can send the *.CAP file as well.</p></li><li><p>Please think carefully before attaching a document to an email.
-Consider pasting the relevant parts into the body of the message. The samba
-mailing lists go to a huge number of people, do they all need a copy of your
-smb.conf in their attach directory?</p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2887497"></a>How to get off the mailinglists</h2></div></div><p>To have your name removed from a samba mailing list, go to the
-same place you went to to get on it. Go to <a href="http://lists.samba.org/" target="_top">http://lists.samba.org</a>,
-click on your nearest mirror and then click on <b>Support</b> and
-then click on <b> Samba related mailing lists</b>. Or perhaps see
-<a href="http://lists.samba.org/mailman/roster/samba-ntdom" target="_top">here</a>
-</p><p>
-Please don't post messages to the list asking to be removed, you will just
-be referred to the above address (unless that process failed in some way...)
-</p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="bugreport"></a>Chapter29.Reporting Bugs</h2></div><div><div class="author"><h3 class="author">Jelmer R. Vernooij</h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt>&lt;<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"></h3><div class="affiliation"><span class="orgname">Samba Team<br></span></div></div></div><div><p class="pubdate"> 27 June 1997 </p></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2887016">Introduction</a></dt><dt><a href="#id2886937">General info</a></dt><dt><a href="#id2887713">Debug levels</a></dt><dt><a href="#id2887849">Internal errors</a></dt><dt><a href="#id2887942">Attaching to a running process</a></dt><dt><a href="#id2887989">Patches</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2887016"></a>Introduction</h2></div></div><p>Please report bugs using <a href="https://bugzilla.samba.org/" target="_top">bugzilla</a>.</p><p>
-Please take the time to read this file before you submit a bug
-report. Also, please see if it has changed between releases, as we
-may be changing the bug reporting mechanism at some time.
-</p><p>
-Please also do as much as you can yourself to help track down the
-bug. Samba is maintained by a dedicated group of people who volunteer
-their time, skills and efforts. We receive far more mail about it than
-we can possibly answer, so you have a much higher chance of an answer
-and a fix if you send us a &quot;developer friendly&quot; bug report that lets
-us fix it fast.
-</p><p>
-Do not assume that if you post the bug to the comp.protocols.smb
-newsgroup or the mailing list that we will read it. If you suspect that your
-problem is not a bug but a configuration problem then it is better to send
-it to the Samba mailing list, as there are (at last count) 5000 other users on
-that list that may be able to help you.
-</p><p>
-You may also like to look though the recent mailing list archives,
-which are conveniently accessible on the Samba web pages
-at <a href="http://samba.org/samba/" target="_top">http://samba.org/samba/</a>.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2886937"></a>General info</h2></div></div><p>
-Before submitting a bug report check your config for silly
-errors. Look in your log files for obvious messages that tell you that
-you've misconfigured something and run testparm to test your config
-file for correct syntax.
-</p><p>
-Have you run through the <a href="#diagnosis" title="Chapter27.The samba checklist">diagnosis</a>?
-This is very important.
-</p><p>
-If you include part of a log file with your bug report then be sure to
-annotate it with exactly what you were doing on the client at the
-time, and exactly what the results were.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2887713"></a>Debug levels</h2></div></div><p>
-If the bug has anything to do with Samba behaving incorrectly as a
-server (like refusing to open a file) then the log files will probably
-be very useful. Depending on the problem a log level of between 3 and
-10 showing the problem may be appropriate. A higher level givesmore
-detail, but may use too much disk space.
-</p><p>
-To set the debug level use <b>log level =</b> in your
-<tt>smb.conf</tt>. You may also find it useful to set the log
-level higher for just one machine and keep separate logs for each machine.
-To do this use:
-</p><pre class="programlisting">
-log level = 10
-log file = /usr/local/samba/lib/log.%m
-include = /usr/local/samba/lib/smb.conf.%m
-</pre><p>
-then create a file
-<tt>/usr/local/samba/lib/smb.conf.<i><tt>machine</tt></i></tt> where
-<i><tt>machine</tt></i> is the name of the client you wish to debug. In that file
-put any <tt>smb.conf</tt> commands you want, for example
-<b>log level=</b> may be useful. This also allows you to
-experiment with different security systems, protocol levels etc on just
-one machine.
-</p><p>
-The <tt>smb.conf</tt> entry <b>log level =</b>
-is synonymous with the entry <b>debuglevel =</b> that has been
-used in older versions of Samba and is being retained for backwards
-compatibility of <tt>smb.conf</tt> files.
-</p><p>
-As the <b>log level =</b> value is increased you will record
-a significantly increasing level of debugging information. For most
-debugging operations you may not need a setting higher than 3. Nearly
-all bugs can be tracked at a setting of 10, but be prepared for a VERY
-large volume of log data.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2887849"></a>Internal errors</h2></div></div><p>
-If you get a &quot;INTERNAL ERROR&quot; message in your log files it means that
-Samba got an unexpected signal while running. It is probably a
-segmentation fault and almost certainly means a bug in Samba (unless
-you have faulty hardware or system software).
-</p><p>
-If the message came from smbd then it will probably be accompanied by
-a message which details the last SMB message received by smbd. This
-info is often very useful in tracking down the problem so please
-include it in your bug report.
-</p><p>
-You should also detail how to reproduce the problem, if
-possible. Please make this reasonably detailed.
-</p><p>
-You may also find that a core file appeared in a <tt>corefiles</tt>
-subdirectory of the directory where you keep your samba log
-files. This file is the most useful tool for tracking down the bug. To
-use it you do this:
-</p><p><b>gdb smbd core</b></p><p>
-adding appropriate paths to smbd and core so gdb can find them. If you
-don't have gdb then try <b><tt>dbx</tt></b>. Then within the debugger use the
-command <b><tt>where</tt></b> to give a stack trace of where the problem
-occurred. Include this in your mail.
-</p><p>
-If you know any assembly language then do a <b><tt>disass</tt></b> of the routine
-where the problem occurred (if its in a library routine then
-disassemble the routine that called it) and try to work out exactly
-where the problem is by looking at the surrounding code. Even if you
-don't know assembly then incuding this info in the bug report can be
-useful.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2887942"></a>Attaching to a running process</h2></div></div><p>
-Unfortunately some unixes (in particular some recent linux kernels)
-refuse to dump a core file if the task has changed uid (which smbd
-does often). To debug with this sort of system you could try to attach
-to the running process using <b><tt>gdb smbd <i><tt>PID</tt></i></tt></b> where you get <i><tt>PID</tt></i> from
-smbstatus. Then use <b><tt>c</tt></b> to continue and try to cause the core dump
-using the client. The debugger should catch the fault and tell you
-where it occurred.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2887989"></a>Patches</h2></div></div><p>
-The best sort of bug report is one that includes a fix! If you send us
-patches please use <b><tt>diff -u</tt></b> format if your version of
-diff supports it, otherwise use <b><tt>diff -c4</tt></b>. Make sure
-you do the diff against a clean version of the source and let me know
-exactly what version you used.
-</p></div></div></div><div class="part" lang="en"><div class="titlepage"><div><h1 class="title"><a name="Appendixes"></a>Appendixes</h1></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt>30. <a href="#compiling">How to compile SAMBA</a></dt><dd><dl><dt><a href="#id2887580">Access Samba source code via CVS</a></dt><dd><dl><dt><a href="#id2887587">Introduction</a></dt><dt><a href="#id2887620">CVS Access to samba.org</a></dt></dl></dd><dt><a href="#id2888377">Accessing the samba sources via rsync and ftp</a></dt><dt><a href="#id2888418">Verifying Samba's PGP signature</a></dt><dt><a href="#id2888501">Building the Binaries</a></dt><dd><dl><dt><a href="#id2888639">Compiling samba with Active Directory support</a></dt></dl></dd><dt><a href="#id2888786">Starting the smbd and nmbd</a></dt><dd><dl><dt><a href="#id2888853">Starting from inetd.conf</a></dt><dt><a href="#id2889045">Alternative: starting it as a daemon</a></dt></dl></dd></dl></dd><dt>31. <a href="#NT4Migration">Migration from NT4 PDC to Samba-3 PDC</a></dt><dd><dl><dt><a href="#id2888159">Planning and Getting Started</a></dt><dd><dl><dt><a href="#id2888028">Objectives</a></dt><dt><a href="#id2889725">Steps In Migration Process</a></dt></dl></dd><dt><a href="#id2889980">Migration Options</a></dt><dd><dl><dt><a href="#id2890062">Planning for Success</a></dt><dt><a href="#id2890304">Samba Implementation Choices</a></dt></dl></dd></dl></dd><dt>32. <a href="#Portability">Portability</a></dt><dd><dl><dt><a href="#id2889273">HPUX</a></dt><dt><a href="#id2889171">SCO Unix</a></dt><dt><a href="#id2889194">DNIX</a></dt><dt><a href="#id2890671">RedHat Linux Rembrandt-II</a></dt><dt><a href="#id2890709">AIX</a></dt><dd><dl><dt><a href="#id2890716">Sequential Read Ahead</a></dt></dl></dd><dt><a href="#id2890741">Solaris</a></dt><dd><dl><dt><a href="#id2890748">Locking improvements</a></dt><dt><a href="#winbind-solaris9">Winbind on Solaris 9</a></dt></dl></dd></dl></dd><dt>33. <a href="#Other-Clients">Samba and other CIFS clients</a></dt><dd><dl><dt><a href="#id2890402">Macintosh clients?</a></dt><dt><a href="#id2890976">OS2 Client</a></dt><dd><dl><dt><a href="#id2890983">How can I configure OS/2 Warp Connect or
- OS/2 Warp 4 as a client for Samba?</a></dt><dt><a href="#id2891066">How can I configure OS/2 Warp 3 (not Connect),
- OS/2 1.2, 1.3 or 2.x for Samba?</a></dt><dt><a href="#id2891126">Are there any other issues when OS/2 (any version)
- is used as a client?</a></dt><dt><a href="#id2891155">How do I get printer driver download working
- for OS/2 clients?</a></dt></dl></dd><dt><a href="#id2891218">Windows for Workgroups</a></dt><dd><dl><dt><a href="#id2891226">Use latest TCP/IP stack from Microsoft</a></dt><dt><a href="#id2891257">Delete .pwl files after password change</a></dt><dt><a href="#id2891287">Configure WfW password handling</a></dt><dt><a href="#id2891313">Case handling of passwords</a></dt><dt><a href="#id2891344">Use TCP/IP as default protocol</a></dt><dt><a href="#id2891361">Speed improvement</a></dt></dl></dd><dt><a href="#id2891388">Windows '95/'98</a></dt><dd><dl><dt><a href="#id2891458">Speed improvement</a></dt></dl></dd><dt><a href="#id2891475">Windows 2000 Service Pack 2</a></dt><dt><a href="#id2891585">Windows NT 3.1</a></dt></dl></dd><dt>34. <a href="#SWAT">SWAT - The Samba Web Admininistration Tool</a></dt><dd><dl><dt><a href="#id2890961">SWAT Features and Benefits</a></dt><dd><dl><dt><a href="#id2890837">Enabling SWAT for use</a></dt><dt><a href="#id2891873">Securing SWAT through SSL</a></dt><dt><a href="#id2891946">The SWAT Home Page</a></dt><dt><a href="#id2892010">Global Settings</a></dt><dt><a href="#id2892118">Share Settings</a></dt><dt><a href="#id2892167">Printers Settings</a></dt><dt><a href="#id2892216">The SWAT Wizard</a></dt><dt><a href="#id2892261">The Status Page</a></dt><dt><a href="#id2892300">The View Page</a></dt><dt><a href="#id2892316">The Password Change Page</a></dt></dl></dd></dl></dd><dt>35. <a href="#speed">Samba performance issues</a></dt><dd><dl><dt><a href="#id2891608">Comparisons</a></dt><dt><a href="#id2891653">Socket options</a></dt><dt><a href="#id2892541">Read size</a></dt><dt><a href="#id2892584">Max xmit</a></dt><dt><a href="#id2892637">Log level</a></dt><dt><a href="#id2892660">Read raw</a></dt><dt><a href="#id2892717">Write raw</a></dt><dt><a href="#id2892759">Slow Logins</a></dt><dt><a href="#id2892781">Client tuning</a></dt></dl></dd></dl></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="compiling"></a>Chapter30.How to compile SAMBA</h2></div><div><div class="author"><h3 class="author"></h3><div class="affiliation"><span class="orgname">Samba Team<br></span></div></div></div><div><div class="author"><h3 class="author">Jelmer R. Vernooij</h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt>&lt;<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate"> (22 May 2001) </p></div><div><p class="pubdate"> 18 March 2003 </p></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2887580">Access Samba source code via CVS</a></dt><dd><dl><dt><a href="#id2887587">Introduction</a></dt><dt><a href="#id2887620">CVS Access to samba.org</a></dt></dl></dd><dt><a href="#id2888377">Accessing the samba sources via rsync and ftp</a></dt><dt><a href="#id2888418">Verifying Samba's PGP signature</a></dt><dt><a href="#id2888501">Building the Binaries</a></dt><dd><dl><dt><a href="#id2888639">Compiling samba with Active Directory support</a></dt></dl></dd><dt><a href="#id2888786">Starting the smbd and nmbd</a></dt><dd><dl><dt><a href="#id2888853">Starting from inetd.conf</a></dt><dt><a href="#id2889045">Alternative: starting it as a daemon</a></dt></dl></dd></dl></div><p>
-You can obtain the samba source from the <a href="http://samba.org/" target="_top">samba website</a>. To obtain a development version,
-you can download samba from CVS or using rsync.
-</p><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2887580"></a>Access Samba source code via CVS</h2></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2887587"></a>Introduction</h3></div></div><p>
-Samba is developed in an open environment. Developers use CVS
-(Concurrent Versioning System) to &quot;checkin&quot; (also known as
-&quot;commit&quot;) new source code. Samba's various CVS branches can
-be accessed via anonymous CVS using the instructions
-detailed in this chapter.
-</p><p>
-This chapter 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="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2887620"></a>CVS Access to samba.org</h3></div></div><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="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2887636"></a>Access via CVSweb</h4></div></div><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="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2888200"></a>Access via cvs</h4></div></div><p>
-You can also access the source code via a
-normal cvs client. This gives you much more control over what you can
-do with the repository and allows you to checkout whole source trees
-and keep them up to date 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><div class="orderedlist"><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><tt>cvs -d :pserver:cvs@samba.org:/cvsroot login</tt></b>
- </p><p>
- When it asks you for a password type <b><tt>cvs</tt></b>.
- </p></li><li><p>
- Run the command
- </p><p>
- <b><tt>cvs -d :pserver:cvs@samba.org:/cvsroot co samba</tt></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 then HEAD can be obtained by using the <i><tt>-r</tt></i>
- and defining a tag name. A list of branch tag names can be found on the
- &quot;Development&quot; 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 userinput.
- </p><p>
- <b><tt>cvs -d :pserver:cvs@samba.org:/cvsroot co -r SAMBA_2_2 samba</tt></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><tt>cvs update -d -P</tt></b>
- </p></li></ol></div></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2888377"></a>Accessing the samba sources via rsync and ftp</h2></div></div><p>
- pserver.samba.org also exports unpacked copies of most parts of the CVS tree at <a href="ftp://pserver.samba.org/pub/unpacked" target="_top">ftp://pserver.samba.org/pub/unpacked</a> and also via anonymous rsync at rsync://pserver.samba.org/ftp/unpacked/. I recommend using rsync rather than ftp.
- See <a href="http://rsync.samba.org/" target="_top">the rsync homepage</a> for more info on rsync.
- </p><p>
- The disadvantage of the unpacked trees
- is that they do not support automatic
- merging of local changes like CVS does.
- rsync access is most convenient for an
- initial install.
- </p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2888418"></a>Verifying Samba's PGP signature</h2></div></div><p>
-In these days of insecurity, it's strongly recommended that you verify the PGP signature for any
-source file before installing it. According to Jerry Carter of the Samba Team, only about 22% of
-all Samba downloads have had a corresponding PGP signature download (a very low percentage, which
-should be considered a bad thing). Even if you're not downloading from a mirror site, verifying PGP
-signatures should be a standard reflex.
-</p><p>
-With that said, go ahead and download the following files:
-</p><pre class="programlisting">
- $ wget http://us1.samba.org/samba/ftp/samba-2.2.8a.tar.asc
- $ wget http://us1.samba.org/samba/ftp/samba-pubkey.asc
-</pre><p>
-The first file is the PGP signature for the Samba source file; the other is the Samba public
-PGP key itself. Import the public PGP key with:
-</p><pre class="programlisting">
- $ gpg --import samba-pubkey.asc
-</pre><p>
-And verify the Samba source code integrity with:
-</p><pre class="programlisting">
- $ gzip -d samba-2.2.8a.tar.gz
- $ gpg --verify samba-2.2.8a.tar.asc
-</pre><p>
-If you receive a message like, &quot;Good signature from Samba Distribution Verification Key...&quot;
-then all is well. The warnings about trust relationships can be ignored. An example of what
-you would not want to see would be:
-</p><pre class="programlisting">
- gpg: BAD signature from &quot;Samba Distribution Verification Key&quot;
-</pre></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2888501"></a>Building the Binaries</h2></div></div><p>To do this, first run the program <b><tt>./configure
- </tt></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>root# </tt><b><tt>./configure --help
- </tt></b></p><p>first to see what special options you can enable.
- Then executing</p><p><tt>root# </tt><b><tt>make</tt></b></p><p>will create the binaries. Once it's successfully
- compiled you can use </p><p><tt>root# </tt><b><tt>make install</tt></b></p><p>to install the binaries and manual pages. You can
- separately install the binaries and/or man pages using</p><p><tt>root# </tt><b><tt>make installbin
- </tt></b></p><p>and</p><p><tt>root# </tt><b><tt>make installman
- </tt></b></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 &quot;.old&quot; extension. You
- can go back to the previous version with</p><p><tt>root# </tt><b><tt>make revert
- </tt></b></p><p>if you find this version a disaster!</p><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2888639"></a>Compiling samba with Active Directory support</h3></div></div><p>In order to compile samba with ADS support, you need to have installed
- on your system:</p><div class="itemizedlist"><ul type="disc"><li><p>the MIT kerberos development libraries
- (either install from the sources or use a package). The
- heimdal libraries will not work.</p></li><li><p>the OpenLDAP development libraries.</p></li></ul></div><p>If your kerberos libraries are in a non-standard location then
- remember to add the configure option --with-krb5=DIR.</p><p>After you run configure make sure that <tt>include/config.h</tt> it generates contains lines like this:</p><pre class="programlisting">
-#define HAVE_KRB5 1
-#define HAVE_LDAP 1
-</pre><p>If it doesn't then configure did not find your krb5 libraries or
- your ldap libraries. Look in config.log to figure out why and fix
- it.</p><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2888706"></a>Installing the required packages for Debian</h4></div></div><p>On Debian you need to install the following packages:</p><p>
- </p><div class="itemizedlist"><ul type="disc"><li>libkrb5-dev</li><li>krb5-user</li></ul></div><p>
- </p></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2888736"></a>Installing the required packages for RedHat</h4></div></div><p>On RedHat this means you should have at least: </p><p>
- </p><div class="itemizedlist"><ul type="disc"><li>krb5-workstation (for kinit)</li><li>krb5-libs (for linking with)</li><li>krb5-devel (because you are compiling from source)</li></ul></div><p>
- </p><p>in addition to the standard development environment.</p><p>Note that these are not standard on a RedHat install, and you may need
- to get them off CD2.</p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2888786"></a>Starting the smbd and nmbd</h2></div></div><p>You must choose to start smbd and nmbd either
- as daemons or from inetdDon't try
- to do both! Either you can put them in <tt>
- inetd.conf</tt> and have them started on demand
- by inetd, or you can start them as
- daemons either from the command line or in <tt>
- /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 smbd
- and nmbd using the recommended daemon method
- is that they will respond slightly more quickly to an initial connection
- request.</p><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2888853"></a>Starting from inetd.conf</h3></div></div><p>NOTE; The following will be different if
- you use NIS, NIS+ or LDAP to distribute services maps.</p><p>Look at your <tt>/etc/services</tt>.
- What is defined at port 139/tcp. If nothing is defined
- then add a line like this:</p><p><b><tt>netbios-ssn 139/tcp</tt></b></p><p>similarly for 137/udp you should have an entry like:</p><p><b><tt>netbios-ns 137/udp</tt></b></p><p>Next edit your <tt>/etc/inetd.conf</tt>
- and add two lines something like this:</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>The exact syntax of <tt>/etc/inetd.conf</tt>
- varies between unixes. Look at the other entries in inetd.conf
- for a guide.</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>Some unixes already have entries like netbios_ns
- (note the underscore) in <tt>/etc/services</tt>.
- You must either edit <tt>/etc/services</tt> or
- <tt>/etc/inetd.conf</tt> to make them consistent.</p></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>On many systems you may need to use the
- <b>interfaces</b> option in <tt>smb.conf</tt> to specify the IP address
- and netmask of your interfaces. Run ifconfig
- as root if you don't know what the broadcast is for your
- net. nmbd tries to determine it at run
- time, but fails on some unixes.
- </p></div><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p>Many unixes only accept around 5
- parameters on the command line in <tt>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>inetd</b>.</p></div><p>Restart <b>inetd</b>, perhaps just send
- it a HUP. If you have installed an earlier version of
- nmbd then you may need to kill nmbd as well.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2889045"></a>Alternative: starting it as a daemon</h3></div></div><p>To start the server as a daemon you should create
- a script something like this one, perhaps calling
- it <tt>startsmb</tt>.</p><pre class="programlisting">
- #!/bin/sh
- /usr/local/samba/bin/smbd -D
- /usr/local/samba/bin/nmbd -D
- </pre><p>then make it executable with <b>chmod
- +x startsmb</b></p><p>You can then run <b>startsmb</b> by
- hand or execute it from <tt>/etc/rc.local</tt>
- </p><p>To kill it send a kill signal to the processes
- <b>nmbd</b> and <b>smbd</b>.</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>If you use the SVR4 style init system then
- you may like to look at the <tt>examples/svr4-startup</tt>
- script to make Samba fit into that system.</p></div></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="NT4Migration"></a>Chapter31.Migration from NT4 PDC to Samba-3 PDC</h2></div><div><div class="author"><h3 class="author">John H. Terpstra</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt>&lt;<a href="mailto:jht@samba.org">jht@samba.org</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate">April 3, 2003</p></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2888159">Planning and Getting Started</a></dt><dd><dl><dt><a href="#id2888028">Objectives</a></dt><dt><a href="#id2889725">Steps In Migration Process</a></dt></dl></dd><dt><a href="#id2889980">Migration Options</a></dt><dd><dl><dt><a href="#id2890062">Planning for Success</a></dt><dt><a href="#id2890304">Samba Implementation Choices</a></dt></dl></dd></dl></div><p>
-This is a rough guide to assist those wishing to migrate from NT4 domain control to
-Samba-3 based domain control.
-</p><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2888159"></a>Planning and Getting Started</h2></div></div><p>
-In the IT world there is often a saying that all problems are encountered because of
-poor planning. The corrollary to this saying is that not all problems can be anticpated
-and planned for. Then again, good planning will anticpate most show stopper type situations.
-</p><p>
-Those wishing to migrate from MS Windows NT4 domain control to a Samba-3 domain control
-environment would do well to develop a detailed migration plan. So here are a few pointers to
-help migration get under way.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2888028"></a>Objectives</h3></div></div><p>
-The key objective for most organisations will be to make the migration from MS Windows NT4
-to Samba-3 domain control as painless as possible. One of the challenges you may experience
-in your migration process may well be one of convincing management that the new environment
-should remain in place. Many who have introduced open source technologies have experienced
-pressure to return to a Microsoft based platform solution at the first sign of trouble.
-</p><p>
-It is strongly advised that before attempting a migration to a Samba-3 controlled network
-that every possible effort be made to gain all-round commitment to the change. Firstly, you
-should know precisely <span class="emphasis"><em>why</em></span> the change is important for the organisation.
-Possible motivations to make a change include:
-</p><div class="itemizedlist"><ul type="disc"><li><p>Improve network manageability</p></li><li><p>Obtain better user level functionality</p></li><li><p>Reduce network operating costs</p></li><li><p>Reduce exposure caused by Microsoft withdrawal of NT4 support</p></li><li><p>Avoid MS License 6 implications</p></li><li><p>Reduce organisation's dependency on Microsoft</p></li></ul></div><p>
-It is vital that it be well recognised that Samba-3 is NOT MS Windows NT4. Samba-3 offers
-an alternative solution that is both different from MS Windows NT4 and that offers some
-advantages compared with it. It should also be recognised that Samba-3 lacks many of the
-features that Microsoft has promoted as core values in migration from MS Windows NT4 to
-MS Windows 2000 and beyond (with or without Active Directory services).
-</p><p>
-What are the features that Samba-3 can NOT provide?
-</p><div class="itemizedlist"><ul type="disc"><li><p>Active Directory Server</p></li><li><p>Group Policy Objects (in Active Direcrtory)</p></li><li><p>Machine Policy objects</p></li><li><p>Logon Scripts in Active Directorty</p></li><li><p>Software Application and Access Controls in Active Directory</p></li></ul></div><p>
-The features that Samba-3 DOES provide and that may be of compelling interest to your site
-includes:
-</p><div class="itemizedlist"><ul type="disc"><li><p>Lower Cost of Ownership</p></li><li><p>Global availability of support with no strings attached</p></li><li><p>Dynamic SMB Servers (ie:Can run more than one server per Unix/Linux system)</p></li><li><p>Creation of on-the-fly logon scripts</p></li><li><p>Creation of on-the-fly Policy Files</p></li><li><p>Greater Stability, Reliability, Performance and Availability</p></li><li><p>Manageability via an ssh connection</p></li><li><p>Flexible choices of back-end authentication technologies (tdbsam, ldapsam, mysqlsam)</p></li><li><p>Ability to implement a full single-signon architecture</p></li><li><p>Ability to distribute authentication systems for absolute minimum wide area network bandwidth demand</p></li></ul></div><p>
-Before migrating a network from MS Windows NT4 to Samba-3 it is vital that all necessary factors are
-considered. Users should be educated about changes they may experience so that the change will be a
-welcome one and not become an obstacle to the work they need to do. The following are some of the
-factors that will go into a successful migration:
-</p><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2889498"></a>Domain Layout</h4></div></div><p>
-Samba-3 can be configured as a domain controller, a back-up domain controller (probably best called
-a secondary controller), a domain member, or as a stand-alone server. The Windows network security
-domain context should be sized and scoped before implementation. Particular attention needs to be
-paid to the location of the primary domain controller (PDC) as well as backup controllers (BDCs).
-It should be noted that one way in which Samba-3 differs from Microsoft technology is that if one
-chooses to use an LDAP authentication backend then the same database can be used by several different
-domains. This means that in a complex organisation there can be a single LDAP database, that itself
-can be distributed, that can simultaneously serve multiple domains (that can also be widely distributed).
-</p><p>
-It is recommended that from a design perspective, the number of users per server, as well as the number
-of servers, per domain should be scaled according to needs and should also consider server capacity
-and network bandwidth.
-</p><p>
-A physical network segment may house several domains, each of which may span multiple network segments.
-Where domains span routed network segments it is most advisable to consider and test the performance
-implications of the design and layout of a network. A Centrally located domain controller that is being
-designed to serve mulitple routed network segments may result in severe performance problems if the
-response time (eg: ping timing) between the remote segment and the PDC is more than 100 ms. In situations
-where the delay is too long it is highly recommended to locate a backup controller (BDC) to serve as
-the local authentication and access control server.
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2889551"></a>Server Share and Directory Layout</h4></div></div><p>
-There are few cardinal rules to effective network design that can be broken with impunity.
-The most important rule of effective network management is that simplicity is king in every
-well controlled network. Every part of the infrastructure must be managed, the more complex
-it is, the greater will be the demand of keeping systems secure and functional.
-</p><p>
-The nature of the data that must be stored needs to be born in mind when deciding how many
-shares must be created. The physical disk space layout should also be taken into account
-when designing where share points will be created. Keep in mind that all data needs to be
-backed up, thus the simpler the disk layout the easier it will be to keep track of what must
-be backed up to tape or other off-line storage medium. Always plan and implement for minimum
-maintenance. Leave nothing to chance in your design, above all, do not leave backups to chance:
-Backup and test, validate every backup, create a disaster recovery plan and prove that it works.
-</p><p>
-Users should be grouped according to data access control needs. File and directory access
-is best controlled via group permissions and the use of the &quot;sticky bit&quot; on group controlled
-directories may substantially avoid file access complaints from samba share users.
-</p><p>
-Many network administrators who are new to the game will attempt to use elaborate techniques
-to set access controls, on files, directories, shares, as well as in share definitions.
-There is the ever present danger that that administrator's successor will not understand the
-complex mess that has been inherited. Remember, apparent job security through complex design
-and implementation may ultimately cause loss of operations and downtime to users as the new
-administrator learns to untangle your web. Keep access controls simple and effective and
-make sure that users will never be interrupted by the stupidity of complexity.
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2889612"></a>Logon Scripts</h4></div></div><p>
-Please refer to the section of this document on Advanced Network Adminsitration for information
-regarding the network logon script options for Samba-3. Logon scripts can help to ensure that
-all users gain share and printer connections they need.
-</p><p>
-Logon scripts can be created on-the-fly so that all commands executed are specific to the
-rights and privilidges granted to the user. The preferred controls should be affected through
-group membership so that group information can be used to custom create a logong script using
-the <tt>root preexec</tt> parameters to the <tt>NETLOGON</tt> share.
-</p><p>
-Some sites prefer to use a tool such as <tt>kixstart</tt> to establish a controlled
-user environment. In any case you may wish to do a google search for logon script process controls.
-In particular, you may wish to explore the use of the Microsoft knowledgebase article KB189105 that
-deals with how to add printers without user intervention via the logon script process.
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2889670"></a>Profile Migration/Creation</h4></div></div><p>
-User and Group Profiles may be migrated using the tools described in the section titled Desktop Profile
-Management.
-</p><p>
-Profiles may also be managed using the Samba-3 tool <tt>profiles</tt>. This tool allows
-the MS Windows NT style security identifiers (SIDs) that are stored inside the profile NTuser.DAT file
-to be changed to the SID of the Samba-3 domain.
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2889700"></a>User and Group Accounts</h4></div></div><p>
-It is possible to migrate all account settings from an MS Windows NT4 domain to Samba-3. Before
-attempting to migrate user and group accounts it is STRONGLY advised to create in Samba-3 the
-groups that are present on the MS Windows NT4 domain <span class="emphasis"><em>AND</em></span> to connect these to
-suitable Unix/Linux groups. Following this simple advice will mean that all user and group attributes
-should migrate painlessly.
-</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2889725"></a>Steps In Migration Process</h3></div></div><p>
-The approximate migration process is described below.
-</p><div class="itemizedlist"><ul type="disc"><li><p>
-You will have an NT4 PDC that has the users, groups, policies and profiles to be migrated
-</p></li><li><p>
-Samba-3 set up as a DC with netlogon share, profile share, etc.
-</p></li></ul></div><div class="procedure"><p class="title"><b>Procedure31.1.The Account Migration Process</b></p><ol type="1"><li><p>Create a BDC account for the samba server using NT Server Manager</p><ol type="a"><li><p>Samba must NOT be running</p></li></ol></li><li><p>rpcclient NT4PDC -U Administrator%passwd</p><ol type="a"><li><p>lsaquery</p></li><li><p>Note the SID returned</p></li></ol></li><li><p>net getsid -S NT4PDC -w DOMNAME -U Administrator%passwd</p><ol type="a"><li><p>Note the SID</p></li></ol></li><li><p>net getlocalsid</p><ol type="a"><li><p>Note the SID, now check that all three SIDS reported are the same!</p></li></ol></li><li><p>net rpc join -S NT4PDC -w DOMNAME -U Administrator%passwd</p></li><li><p>net rpc vampire -S NT4PDC -U administrator%passwd</p></li><li><p>pdbedit -l</p><ol type="a"><li><p>Note - did the users migrate?</p></li></ol></li><li><p>initGrps.sh DOMNAME</p></li><li><p>net groupmap list</p><ol type="a"><li><p>Now check that all groups are recognised</p></li></ol></li><li><p>net rpc campire -S NT4PDC -U administrator%passwd</p></li><li><p>pdbedit -lv</p><ol type="a"><li><p>Note - check that all group membership has been migrated</p></li></ol></li></ol></div><p>
-Now it is time to migrate all the profiles, then migrate all policy files.
-More later.
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2889980"></a>Migration Options</h2></div></div><p>
-Based on feedback from many sites as well as from actual installation and maintenance
-experience sites that wish to migrate from MS Windows NT4 Domain Control to a Samba
-based solution fit into three basic categories.
-</p><div class="table"><a name="id2889997"></a><p class="title"><b>Table31.1.The 3 Major Site Types</b></p><table summary="The 3 Major Site Types" border="1"><colgroup><col><col></colgroup><thead><tr><th>Number of Users</th><th>Description</th></tr></thead><tbody><tr><td>&lt; 50</td><td><p>Want simple conversion with NO pain</p></td></tr><tr><td>50 - 250</td><td><p>Want new features, can manage some in-house complexity</p></td></tr><tr><td>&gt; 250</td><td><p>Solution/Implementation MUST scale well, complex needs. Cross departmental decision process. Local expertise in most areas</p></td></tr></tbody></table></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2890062"></a>Planning for Success</h3></div></div><p>
-There are three basic choices for sites that intend to migrate from MS Windwows NT4
-to Samba-3.
-</p><div class="itemizedlist"><ul type="disc"><li><p>
- Simple Conversion (total replacement)
- </p></li><li><p>
- Upgraded Conversion (could be one of integration)
- </p></li><li><p>
- Complete Redesign (completely new solution)
- </p></li></ul></div><p>
-No matter what choice you make, the following rules will minimise down-stream problems:
-</p><div class="itemizedlist"><ul type="disc"><li><p>
- Take sufficient time
- </p></li><li><p>
- Avoid Panic
- </p></li><li><p>
- Test ALL assumptions
- </p></li><li><p>
- Test full roll-out program, including workstation deployment
- </p></li></ul></div><div class="table"><a name="id2890135"></a><p class="title"><b>Table31.2.Nature of the Conversion Choices</b></p><table summary="Nature of the Conversion Choices" border="1"><colgroup><col><col><col></colgroup><thead><tr><th>Simple</th><th>Upgraded</th><th>Redesign</th></tr></thead><tbody><tr><td><p>Make use of minimal OS specific features</p></td><td><p>Translate NT4 features to new host OS features</p></td><td><p>Decide:</p></td></tr><tr><td><p>Suck all accounts from NT4 into Samba-3</p></td><td><p>Copy and improve:</p></td><td><p>Authentication Regime (database location and access)</p></td></tr><tr><td><p>Make least number of operational changes</p></td><td><p>Make progressive improvements</p></td><td><p>Desktop Management Methods</p></td></tr><tr><td><p>Take least amount of time to migrate</p></td><td><p>Minimise user impact</p></td><td><p>Better Control of Desktops / Users</p></td></tr><tr><td><p>Live versus Isolated Conversion</p></td><td><p>Maximise functionality</p></td><td><p>Identify Needs for: Manageability, Scalability, Security, Availability</p></td></tr><tr><td><p>Integrate Samba-3 then migrate while users are active, then Change of control (ie: swap out)</p></td><td><p>Take advantage of lower maintenance opportunity</p></td><td><p></p></td></tr></tbody></table></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2890304"></a>Samba Implementation Choices</h3></div></div><pre class="programlisting">
-Authentication database back end
- Winbind (external Samba or NT4/200x server)
- Can use pam_mkhomedir.so to auto-create home dirs
- External server could use Active Directory or NT4 Domain
-
-Database type
- smbpasswd, tdbsam, ldapsam, MySQLsam
-
-Access Control Points
- On the Share itself (Use NT4 Server Manager)
- On the file system
- Unix permissions on files and directories
- Posix ACLs enablement in file system?
- Through Samba share parameters
- Not recommended - except as only resort
-
-Policies (migrate or create new ones)
- Group Policy Editor (NT4)
- Watch out for Tattoo effect
-
-User and Group Profiles
- Platform specific so use platform tool to change from a Local
- to a Roaming profile Can use new profiles tool to change SIDs
- (NTUser.DAT)
-
-Logon Scripts (Know how they work)
-
-User and Group mapping to Unix/Linux
- username map facility may be needed
- Use 'net groupmap' to connect NT4 groups to Unix groups
- Use pdbedit to set/change user configuration
-NOTE:
-If migrating to LDAP back end it may be easier to dump initial LDAP database
-to LDIF, then edit, then reload into LDAP
-
- OS specific scripts / programs may be needed
- Add / delete Users
- Note OS limits on size of name (Linux 8 chars)
- NT4 up to 254 chars
- Add / delete machines
- Applied only to domain members (note up to 16 chars)
- Add / delete Groups
- Note OS limits on size and nature
- Linux limit is 16 char,
- no spaces and no upper case chars (groupadd)
-
-Migration Tools
- Domain Control (NT4 Style)
- Profiles, Policies, Access Controls, Security
-
-Migration Tools
- Samba: net, rpcclient, smbpasswd, pdbedit, profiles
- Windows: NT4 Domain User Manager, Server Manager (NEXUS)
-
-Authentication
- New SAM back end (smbpasswd, tdbsam, ldapsam, mysqlsam)
-</pre><p>
-</p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="Portability"></a>Chapter32.Portability</h2></div><div><div class="author"><h3 class="author">Jelmer R. Vernooij</h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt>&lt;<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</tt></p></div></div></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2889273">HPUX</a></dt><dt><a href="#id2889171">SCO Unix</a></dt><dt><a href="#id2889194">DNIX</a></dt><dt><a href="#id2890671">RedHat Linux Rembrandt-II</a></dt><dt><a href="#id2890709">AIX</a></dt><dd><dl><dt><a href="#id2890716">Sequential Read Ahead</a></dt></dl></dd><dt><a href="#id2890741">Solaris</a></dt><dd><dl><dt><a href="#id2890748">Locking improvements</a></dt><dt><a href="#winbind-solaris9">Winbind on Solaris 9</a></dt></dl></dd></dl></div><p>Samba works on a wide range of platforms but the interface all the
-platforms provide is not always compatible. This chapter contains
-platform-specific information about compiling and using samba.</p><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2889273"></a>HPUX</h2></div></div><p>
-HP's implementation of supplementary groups is, er, non-standard (for
-hysterical reasons). There are two group files, /etc/group and
-/etc/logingroup; the system maps UIDs to numbers using the former, but
-initgroups() reads the latter. Most system admins who know the ropes
-symlink /etc/group to /etc/logingroup (hard link doesn't work for reasons
-too stupid to go into here). initgroups() will complain if one of the
-groups you're in in /etc/logingroup has what it considers to be an invalid
-ID, which means outside the range [0..UID_MAX], where UID_MAX is (I think)
-60000 currently on HP-UX. This precludes -2 and 65534, the usual 'nobody'
-GIDs.
-</p><p>
-If you encounter this problem, make sure that the programs that are failing
-to initgroups() be run as users not in any groups with GIDs outside the
-allowed range.
-</p><p>This is documented in the HP manual pages under setgroups(2) and passwd(4).
-</p><p>
-On HPUX you must use gcc or the HP Ansi compiler. The free compiler
-that comes with HP-UX is not Ansi compliant and cannot compile
-Samba.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2889171"></a>SCO Unix</h2></div></div><p>
-If you run an old version of SCO Unix then you may need to get important
-TCP/IP patches for Samba to work correctly. Without the patch, you may
-encounter corrupt data transfers using samba.
-</p><p>
-The patch you need is UOD385 Connection Drivers SLS. It is available from
-SCO (ftp.sco.com, directory SLS, files uod385a.Z and uod385a.ltr.Z).
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2889194"></a>DNIX</h2></div></div><p>
-DNIX has a problem with seteuid() and setegid(). These routines are
-needed for Samba to work correctly, but they were left out of the DNIX
-C library for some reason.
-</p><p>
-For this reason Samba by default defines the macro NO_EID in the DNIX
-section of includes.h. This works around the problem in a limited way,
-but it is far from ideal, some things still won't work right.
-</p><p>
-To fix the problem properly you need to assemble the following two
-functions and then either add them to your C library or link them into
-Samba.
-</p><p>
-put this in the file <tt>setegid.s</tt>:
-</p><pre class="programlisting">
- .globl _setegid
-_setegid:
- moveq #47,d0
- movl #100,a0
- moveq #1,d1
- movl 4(sp),a1
- trap #9
- bccs 1$
- jmp cerror
-1$:
- clrl d0
- rts
-</pre><p>
-put this in the file <tt>seteuid.s</tt>:
-</p><pre class="programlisting">
- .globl _seteuid
-_seteuid:
- moveq #47,d0
- movl #100,a0
- moveq #0,d1
- movl 4(sp),a1
- trap #9
- bccs 1$
- jmp cerror
-1$:
- clrl d0
- rts
-</pre><p>
-after creating the above files you then assemble them using
-</p><p><b>as seteuid.s</b></p><p><b>as setegid.s</b></p><p>
-that should produce the files <tt>seteuid.o</tt> and
-<tt>setegid.o</tt>
-</p><p>
-then you need to add these to the LIBSM line in the DNIX section of
-the Samba Makefile. Your LIBSM line will then look something like this:
-</p><pre class="programlisting">
-LIBSM = setegid.o seteuid.o -ln
-</pre><p>
-You should then remove the line:
-</p><pre class="programlisting">
-#define NO_EID
-</pre><p>from the DNIX section of <tt>includes.h</tt></p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2890671"></a>RedHat Linux Rembrandt-II</h2></div></div><p>
-By default RedHat Rembrandt-II during installation adds an
-entry to /etc/hosts as follows:
-</p><pre class="programlisting">
- 127.0.0.1 loopback &quot;hostname&quot;.&quot;domainname&quot;
-</pre><p>
-</p><p>
-This causes Samba to loop back onto the loopback interface.
-The result is that Samba fails to communicate correctly with
-the world and therefor may fail to correctly negotiate who
-is the master browse list holder and who is the master browser.
-</p><p>
-Corrective Action: Delete the entry after the word loopback
- in the line starting 127.0.0.1
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2890709"></a>AIX</h2></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2890716"></a>Sequential Read Ahead</h3></div></div><p>
-Disabling Sequential Read Ahead using <b><tt>vmtune -r 0</tt></b> improves
-samba performance significally.
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2890741"></a>Solaris</h2></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2890748"></a>Locking improvements</h3></div></div><p>Some people have been experiencing problems with F_SETLKW64/fcntl
-when running samba on solaris. The built in file locking mechanism was
-not scalable. Performance would degrade to the point where processes would
-get into loops of trying to lock a file. It woul try a lock, then fail,
-then try again. The lock attempt was failing before the grant was
-occurring. So the visible manifestation of this would be a handful of
-processes stealing all of the CPU, and when they were trussed they would
-be stuck if F_SETLKW64 loops.
-</p><p>
-Sun released patches for Solaris 2.6, 8, and 9. The patch for Solaris 7
-has not been released yet.
-</p><p>
-The patch revision for 2.6 is 105181-34
-for 8 is 108528-19
-and for 9 is 112233-04
-</p><p>
-After the install of these patches it is recommended to reconfigure
-and rebuild samba.
-</p><p>Thanks to Joe Meslovich for reporting</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="winbind-solaris9"></a>Winbind on Solaris 9</h3></div></div><p>
-Nsswitch on Solaris 9 refuses to use the winbind nss module. This behavior
-is fixed by Sun in patch 113476-05 which as of March 2003 is not in any
-roll-up packages.
-</p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="Other-Clients"></a>Chapter33.Samba and other CIFS clients</h2></div><div><div class="author"><h3 class="author">Jim McDonough</h3><div class="affiliation"><span class="orgname">IBM<br></span><div class="address"><p><tt>&lt;<a href="mailto:jmcd@us.ibm.com">jmcd@us.ibm.com</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author">Jelmer R. Vernooij</h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt>&lt;<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate">5 Mar 2001</p></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2890402">Macintosh clients?</a></dt><dt><a href="#id2890976">OS2 Client</a></dt><dd><dl><dt><a href="#id2890983">How can I configure OS/2 Warp Connect or
- OS/2 Warp 4 as a client for Samba?</a></dt><dt><a href="#id2891066">How can I configure OS/2 Warp 3 (not Connect),
- OS/2 1.2, 1.3 or 2.x for Samba?</a></dt><dt><a href="#id2891126">Are there any other issues when OS/2 (any version)
- is used as a client?</a></dt><dt><a href="#id2891155">How do I get printer driver download working
- for OS/2 clients?</a></dt></dl></dd><dt><a href="#id2891218">Windows for Workgroups</a></dt><dd><dl><dt><a href="#id2891226">Use latest TCP/IP stack from Microsoft</a></dt><dt><a href="#id2891257">Delete .pwl files after password change</a></dt><dt><a href="#id2891287">Configure WfW password handling</a></dt><dt><a href="#id2891313">Case handling of passwords</a></dt><dt><a href="#id2891344">Use TCP/IP as default protocol</a></dt><dt><a href="#id2891361">Speed improvement</a></dt></dl></dd><dt><a href="#id2891388">Windows '95/'98</a></dt><dd><dl><dt><a href="#id2891458">Speed improvement</a></dt></dl></dd><dt><a href="#id2891475">Windows 2000 Service Pack 2</a></dt><dt><a href="#id2891585">Windows NT 3.1</a></dt></dl></div><p>This chapter contains client-specific information.</p><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2890402"></a>Macintosh clients?</h2></div></div><p>
-Yes. <a href="http://www.thursby.com/" target="_top">Thursby</a> now have a CIFS Client / Server called <a href="http://www.thursby.com/products/dave.html" target="_top">DAVE</a>
-</p><p>
-They test it against Windows 95, Windows NT and samba for
-compatibility issues. At the time of writing, DAVE was at version
-1.0.1. The 1.0.0 to 1.0.1 update is available as a free download from
-the Thursby web site (the speed of finder copies has been greatly
-enhanced, and there are bug-fixes included).
-</p><p>
-Alternatives - There are two free implementations of AppleTalk for
-several kinds of UNIX machnes, and several more commercial ones.
-These products allow you to run file services and print services
-natively to Macintosh users, with no additional support required on
-the Macintosh. The two free omplementations are
-<a href="http://www.umich.edu/~rsug/netatalk/" target="_top">Netatalk</a>, and
-<a href="http://www.cs.mu.oz.au/appletalk/atalk.html" target="_top">CAP</a>.
-What Samba offers MS
-Windows users, these packages offer to Macs. For more info on these
-packages, Samba, and Linux (and other UNIX-based systems) see
-<a href="http://www.eats.com/linux_mac_win.html" target="_top">http://www.eats.com/linux_mac_win.html</a>
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2890976"></a>OS2 Client</h2></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2890983"></a>How can I configure OS/2 Warp Connect or
- OS/2 Warp 4 as a client for Samba?</h3></div></div><p>A more complete answer to this question can be
- found on <a href="http://carol.wins.uva.nl/~leeuw/samba/warp.html" target="_top">
- http://carol.wins.uva.nl/~leeuw/samba/warp.html</a>.</p><p>Basically, you need three components:</p><div class="itemizedlist"><ul type="disc"><li><p>The File and Print Client ('IBM Peer')
- </p></li><li><p>TCP/IP ('Internet support')
- </p></li><li><p>The &quot;NetBIOS over TCP/IP&quot; driver ('TCPBEUI')
- </p></li></ul></div><p>Installing the first two together with the base operating
- system on a blank system is explained in the Warp manual. If Warp
- has already been installed, but you now want to install the
- networking support, use the &quot;Selective Install for Networking&quot;
- object in the &quot;System Setup&quot; folder.</p><p>Adding the &quot;NetBIOS over TCP/IP&quot; driver is not described
- in the manual and just barely in the online documentation. Start
- MPTS.EXE, click on OK, click on &quot;Configure LAPS&quot; and click
- on &quot;IBM OS/2 NETBIOS OVER TCP/IP&quot; in 'Protocols'. This line
- is then moved to 'Current Configuration'. Select that line,
- click on &quot;Change number&quot; and increase it from 0 to 1. Save this
- configuration.</p><p>If the Samba server(s) is not on your local subnet, you
- can optionally add IP names and addresses of these servers
- to the &quot;Names List&quot;, or specify a WINS server ('NetBIOS
- Nameserver' in IBM and RFC terminology). For Warp Connect you
- may need to download an update for 'IBM Peer' to bring it on
- the same level as Warp 4. See the webpage mentioned above.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2891066"></a>How can I configure OS/2 Warp 3 (not Connect),
- OS/2 1.2, 1.3 or 2.x for Samba?</h3></div></div><p>You can use the free Microsoft LAN Manager 2.2c Client
- for OS/2 from
- <a href="ftp://ftp.microsoft.com/BusSys/Clients/LANMAN.OS2/" target="_top">
- ftp://ftp.microsoft.com/BusSys/Clients/LANMAN.OS2/</a>.
- See <a href="http://carol.wins.uva.nl/~leeuw/lanman.html" target="_top">
- http://carol.wins.uva.nl/~leeuw/lanman.html</a> for
- more information on how to install and use this client. In
- a nutshell, edit the file \OS2VER in the root directory of
- the OS/2 boot partition and add the lines:</p><pre class="programlisting">
- 20=setup.exe
- 20=netwksta.sys
- 20=netvdd.sys
- </pre><p>before you install the client. Also, don't use the
- included NE2000 driver because it is buggy. Try the NE2000
- or NS2000 driver from
- <a href="ftp://ftp.cdrom.com/pub/os2/network/ndis/" target="_top">
- ftp://ftp.cdrom.com/pub/os2/network/ndis/</a> instead.
- </p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2891126"></a>Are there any other issues when OS/2 (any version)
- is used as a client?</h3></div></div><p>When you do a NET VIEW or use the &quot;File and Print
- Client Resource Browser&quot;, no Samba servers show up. This can
- be fixed by a patch from <a href="http://carol.wins.uva.nl/~leeuw/samba/fix.html" target="_top">
- http://carol.wins.uva.nl/~leeuw/samba/fix.html</a>.
- The patch will be included in a later version of Samba. It also
- fixes a couple of other problems, such as preserving long
- filenames when objects are dragged from the Workplace Shell
- to the Samba server. </p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2891155"></a>How do I get printer driver download working
- for OS/2 clients?</h3></div></div><p>First, create a share called [PRINTDRV] that is
- world-readable. Copy your OS/2 driver files there. Note
- that the .EA_ files must still be separate, so you will need
- to use the original install files, and not copy an installed
- driver from an OS/2 system.</p><p>Install the NT driver first for that printer. Then,
- add to your smb.conf a parameter, os2 driver map =
- <i><tt>filename</tt></i>&quot;. Then, in the file
- specified by <i><tt>filename</tt></i>, map the
- name of the NT driver name to the OS/2 driver name as
- follows:</p><p><b>nt driver name = os2 &quot;driver
- name&quot;.&quot;device name&quot;</b>, e.g.:
- HP LaserJet 5L = LASERJET.HP LaserJet 5L</p><p>You can have multiple drivers mapped in this file.</p><p>If you only specify the OS/2 driver name, and not the
- device name, the first attempt to download the driver will
- actually download the files, but the OS/2 client will tell
- you the driver is not available. On the second attempt, it
- will work. This is fixed simply by adding the device name
- to the mapping, after which it will work on the first attempt.
- </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2891218"></a>Windows for Workgroups</h2></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2891226"></a>Use latest TCP/IP stack from Microsoft</h3></div></div><p>Use the latest TCP/IP stack from microsoft if you use Windows
-for workgroups.
-</p><p>The early TCP/IP stacks had lots of bugs.</p><p>
-Microsoft has released an incremental upgrade to their TCP/IP 32-Bit
-VxD drivers. The latest release can be found on their ftp site at
-ftp.microsoft.com, located in /peropsys/windows/public/tcpip/wfwt32.exe.
-There is an update.txt file there that describes the problems that were
-fixed. New files include WINSOCK.DLL, TELNET.EXE, WSOCK.386, VNBT.386,
-WSTCP.386, TRACERT.EXE, NETSTAT.EXE, and NBTSTAT.EXE.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2891257"></a>Delete .pwl files after password change</h3></div></div><p>
-WfWg does a lousy job with passwords. I find that if I change my
-password on either the unix box or the PC the safest thing to do is to
-delete the .pwl files in the windows directory. The PC will complain about not finding the files, but will soon get over it, allowing you to enter the new password.
-</p><p>
-If you don't do this you may find that WfWg remembers and uses the old
-password, even if you told it a new one.
-</p><p>
-Often WfWg will totally ignore a password you give it in a dialog box.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2891287"></a>Configure WfW password handling</h3></div></div><p>
-There is a program call admincfg.exe
-on the last disk (disk 8) of the WFW 3.11 disk set. To install it
-type EXPAND A:\ADMINCFG.EX_ C:\WINDOWS\ADMINCFG.EXE Then add an icon
-for it via the &quot;Progam Manager&quot; &quot;New&quot; Menu. This program allows you
-to control how WFW handles passwords. ie disable Password Caching etc
-for use with <b>security = user</b>
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2891313"></a>Case handling of passwords</h3></div></div><p>Windows for Workgroups uppercases the password before sending it to the server. Unix passwords can be case-sensitive though. Check the <a href="smb.conf.5.html" target="_top">smb.conf(5)</a> information on <b>password level</b> to specify what characters samba should try to uppercase when checking.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2891344"></a>Use TCP/IP as default protocol</h3></div></div><p>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" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2891361"></a>Speed improvement</h3></div></div><p>
-Note that some people have found that setting DefaultRcvWindow in
-the [MSTCP] section of the SYSTEM.INI file under WfWg to 3072 gives a
-big improvement. I don't know why.
-</p><p>
-My own experience wth DefaultRcvWindow is that I get much better
-performance with a large value (16384 or larger). Other people have
-reported that anything over 3072 slows things down enourmously. One
-person even reported a speed drop of a factor of 30 when he went from
-3072 to 8192. I don't know why.
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2891388"></a>Windows '95/'98</h2></div></div><p>
-When using Windows 95 OEM SR2 the following updates are recommended where Samba
-is being used. Please NOTE that the above change will affect you once these
-updates have been installed.
-</p><p>
-There are more updates than the ones mentioned here. You are referred to the
-Microsoft Web site for all currently available updates to your specific version
-of Windows 95.
-</p><div class="orderedlist"><ol type="1"><li><p>Kernel Update: KRNLUPD.EXE</p></li><li><p>Ping Fix: PINGUPD.EXE</p></li><li><p>RPC Update: RPCRTUPD.EXE</p></li><li><p>TCP/IP Update: VIPUPD.EXE</p></li><li><p>Redirector Update: VRDRUPD.EXE</p></li></ol></div><p>
-Also, if using MS OutLook it is desirable to install the OLEUPD.EXE fix. This
-fix may stop your machine from hanging for an extended period when exiting
-OutLook and you may also notice a significant speedup when accessing network
-neighborhood services.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2891458"></a>Speed improvement</h3></div></div><p>
-Configure the win95 TCPIP registry settings to give better
-performance. I use a program called MTUSPEED.exe which I got off the
-net. There are various other utilities of this type freely available.
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2891475"></a>Windows 2000 Service Pack 2</h2></div></div><p>
-There are several annoyances with Windows 2000 SP2. One of which
-only appears when using a Samba server to host user profiles
-to Windows 2000 SP2 clients in a Windows domain. This assumes
-that Samba is a member of the domain, but the problem will
-likely occur if it is not.
-</p><p>
-In order to server profiles successfully to Windows 2000 SP2
-clients (when not operating as a PDC), Samba must have
-<b>nt acl support = no</b>
-added to the file share which houses the roaming profiles.
-If this is not done, then the Windows 2000 SP2 client will
-complain about not being able to access the profile (Access
-Denied) and create multiple copies of it on disk (DOMAIN.user.001,
-DOMAIN.user.002, etc...). See the
-<a href="smb.conf.5.html" target="_top">smb.conf(5)</a> man page
-for more details on this option. Also note that the
-<b>nt acl support</b> parameter was formally a global parameter in
-releases prior to Samba 2.2.2.
-</p><p>
-The following is a minimal profile share:
-</p><pre class="programlisting">
- [profile]
- path = /export/profile
- create mask = 0600
- directory mask = 0700
- nt acl support = no
- read only = no
-</pre><p>
-The reason for this bug is that the Win2k SP2 client copies
-the security descriptor for the profile which contains
-the Samba server's SID, and not the domain SID. The client
-compares the SID for SAMBA\user and realizes it is
-different that the one assigned to DOMAIN\user. Hence the reason
-for the &quot;access denied&quot; message.
-</p><p>
-By disabling the <b>nt acl support</b> parameter, Samba will send
-the Win2k client a response to the QuerySecurityDescriptor
-trans2 call which causes the client to set a default ACL
-for the profile. This default ACL includes
-</p><p><b>DOMAIN\user &quot;Full Control&quot;</b></p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>This bug does not occur when using winbind to
-create accounts on the Samba host for Domain users.</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2891585"></a>Windows NT 3.1</h2></div></div><p>If you have problems communicating across routers with Windows
-NT 3.1 workstations, read <a href="http://support.microsoft.com/default.aspx?scid=kb;%5BLN%5D;Q103765" target="_top">this Microsoft Knowledge Base article</a>.
-
-</p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="SWAT"></a>Chapter34.SWAT - The Samba Web Admininistration Tool</h2></div><div><div class="author"><h3 class="author">John H. Terpstra</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt>&lt;<a href="mailto:jht@samba.org">jht@samba.org</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate">April 21, 2003</p></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2890961">SWAT Features and Benefits</a></dt><dd><dl><dt><a href="#id2890837">Enabling SWAT for use</a></dt><dt><a href="#id2891873">Securing SWAT through SSL</a></dt><dt><a href="#id2891946">The SWAT Home Page</a></dt><dt><a href="#id2892010">Global Settings</a></dt><dt><a href="#id2892118">Share Settings</a></dt><dt><a href="#id2892167">Printers Settings</a></dt><dt><a href="#id2892216">The SWAT Wizard</a></dt><dt><a href="#id2892261">The Status Page</a></dt><dt><a href="#id2892300">The View Page</a></dt><dt><a href="#id2892316">The Password Change Page</a></dt></dl></dd></dl></div><p>
-There are many and varied opinions regarding the usefulness or otherwise of SWAT.
-No matter how hard one tries to produce the perfect configuration tool it remains
-an object of personal taste. SWAT is a tool that will allow web based configuration
-of samba. It has a wizard that may help to get samba configured quickly, it has context
-sensitive help on each smb.conf parameter, it provides for monitoring of current state
-of connection information, and it allows network wide MS Windows network password
-management.
-</p><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2890961"></a>SWAT Features and Benefits</h2></div></div><p>
-There are network administrators who believe that it is a good idea to write systems
-documentation inside configuration files, for them SWAT will aways be a nasty tool. SWAT
-does not store the configuration file in any intermediate form, rather, it stores only the
-parameter settings, so when SWAT writes the smb.conf file to disk it will write only
-those parameters that are at other than the default settings. The result is that all comments
-will be lost from the smb.conf file. Additionally, the parameters will be written back in
-internal ordering.
-</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-So before using SWAT please be warned - SWAT will completely replace your smb.conf with
-a fully optimised file that has been stripped of all comments you might have placed there
-and only non-default settings will be written to the file.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2890837"></a>Enabling SWAT for use</h3></div></div><p>
-SWAT should be installed to run via the network super daemon. Depending on which system
-your Unix/Linux system has you will have either an <tt>inetd</tt> or
-<tt>xinetd</tt> based system.
-</p><p>
-The nature and location of the network super-daemon varies with the operating system
-implementation. The control file (or files) can be located in the file
-<tt>/etc/inetd.conf</tt> or in the directory <tt>/etc/[x]inet.d</tt>
-or similar.
-</p><p>
-The control entry for the older style file might be:
-</p><pre class="programlisting">
- # swat is the Samba Web Administration Tool
- swat stream tcp nowait.400 root /usr/sbin/swat swat
-</pre><p>
-A control file for the newer style xinetd could be:
-</p><p>
-</p><pre class="programlisting">
- # default: off
- # description: SWAT is the Samba Web Admin Tool. Use swat \
- # to configure your Samba server. To use SWAT, \
- # connect to port 901 with your favorite web browser.
- service swat
- {
- port = 901
- socket_type = stream
- wait = no
- only_from = localhost
- user = root
- server = /usr/sbin/swat
- log_on_failure += USERID
- disable = yes
- }
-</pre><p>
-
-</p><p>
-Both the above examples assume that the <tt>swat</tt> binary has been
-located in the <tt>/usr/sbin</tt> directory. In addition to the above
-SWAT will use a directory access point from which it will load it's help files
-as well as other control information. The default location for this on most Linux
-systems is in the directory <tt>/usr/share/samba/swat</tt>. The default
-location using samba defaults will be <tt>/usr/local/samba/swat</tt>.
-</p><p>
-Access to SWAT will prompt for a logon. If you log onto SWAT as any non-root user
-the only permission allowed is to view certain aspects of configuration as well as
-access to the password change facility. The buttons that will be exposed to the non-root
-user are: <span class="emphasis"><em>HOME, STATUS, VIEW, PASSWORD</em></span>. The only page that allows
-change capability in this case is <span class="emphasis"><em>PASSWORD</em></span>.
-</p><p>
-So long as you log onto SWAT as the user <b>root</b> you should obtain
-full change and commit ability. The buttons that will be exposed includes:
-<span class="emphasis"><em>HOME, GLOBALS, SHARES, PRINTERS, WIZARD, STATUS, VIEW, PASSWORD</em></span>.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2891873"></a>Securing SWAT through SSL</h3></div></div><p>
-Lots of people have asked about how to setup SWAT with SSL to allow for secure remote
-administration of Samba. Here is a method that works, courtesy of Markus Krieger
-</p><p>
-Modifications to the swat setup are as following:
-</p><div class="itemizedlist"><ul type="disc"><li><p>
- install OpenSSL
- </p></li><li><p>
- generate certificate and private key
-
- </p><pre class="programlisting">
- root# /usr/bin/openssl req -new -x509 -days 365 -nodes -config \
- /usr/share/doc/packages/stunnel/stunnel.cnf \
- -out /etc/stunnel/stunnel.pem -keyout /etc/stunnel/stunnel.pem
- </pre></li><li><p>
- remove swat-entry from [x]inetd
- </p></li><li><p>
- start stunnel
-
- </p><pre class="programlisting">
- root# stunnel -p /etc/stunnel/stunnel.pem -d 901 \
- -l /usr/local/samba/bin/swat swat
- </pre></li></ul></div><p>
-afterwards simply contact to swat by using the URL &quot;https://myhost:901&quot;, accept the certificate
-and the SSL connection is up.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2891946"></a>The SWAT Home Page</h3></div></div><p>
-The SWAT title page provides access to the latest Samba documentation. The manual page for
-each samba component is accessible from this page as are the Samba-HOWTO-Collection (this
-document) as well as the O'Reilly book &quot;Using Samba&quot;.
-</p><p>
-Administrators who wish to validate their samba configuration may obtain useful information
-from the man pages for the diganostic utilities. These are available from the SWAT home page
-also. One diagnostic tool that is NOT mentioned on this page, but that is particularly
-useful is <b>ethereal</b>, available from <a href="http://www.ethereal.com" target="_top">
-http://www.ethereal.com</a>.
-</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-SWAT can be configured to run in <span class="emphasis"><em>demo</em></span> mode. This is NOT recommended
-as it runs SWAT without authentication and with full administrative ability. ie: Allows
-changes to smb.conf as well as general operation with root privilidges. The option that
-creates this ability is the <b>-a</b> flag to swat. DO NOT USE THIS IN ANY
-PRODUCTION ENVIRONMENT - you have been warned!
-</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2892010"></a>Global Settings</h3></div></div><p>
-The Globals button will expose a page that allows configuration of the global parameters
-in smb.conf. There are three levels of exposure of the parameters:
-</p><div class="itemizedlist"><ul type="disc"><li><p>
- <b>Basic</b> - exposes common configuration options.
- </p></li><li><p>
- <b>Advanced</b> - exposes configuration options needed in more
- complex environments.
- </p></li><li><p>
- <b>Developer</b> - exposes configuration options that only the brave
- will want to tamper with.
- </p></li></ul></div><p>
-To switch to other than <span class="emphasis"><em>Basic</em></span> editing ability click on either the
-<span class="emphasis"><em>Advanced</em></span> or the <span class="emphasis"><em>Developer</em></span> dial, then click the
-<span class="emphasis"><em>Commit Changes</em></span> button.
-</p><p>
-After making any changes to configuration parameters make sure that you click on the
-<span class="emphasis"><em>Commit Changes</em></span> button before moving to another area otherwise
-your changes will be immediately lost.
-</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-SWAT has context sensitive help. To find out what each parameter is for simply click the
-<b>Help</b> link to the left of the configurartion parameter.
-</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2892118"></a>Share Settings</h3></div></div><p>
-To affect a currenly configured share, simply click on the pull down button between the
-<span class="emphasis"><em>Choose Share</em></span> and the <span class="emphasis"><em>Delete Share</em></span> buttons,
-select the share you wish to operate on, then to edit the settings click on the
-<span class="emphasis"><em>Choose Share</em></span> button, to delete the share simply press the
-<span class="emphasis"><em>Delete Share</em></span> button.
-</p><p>
-To create a new share, next to the button labelled <span class="emphasis"><em>Create Share</em></span> enter
-into the text field the name of the share to be created, then click on the
-<span class="emphasis"><em>Create Share</em></span> button.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2892167"></a>Printers Settings</h3></div></div><p>
-To affect a currenly configured printer, simply click on the pull down button between the
-<span class="emphasis"><em>Choose Printer</em></span> and the <span class="emphasis"><em>Delete Printer</em></span> buttons,
-select the printer you wish to operate on, then to edit the settings click on the
-<span class="emphasis"><em>Choose Printer</em></span> button, to delete the share simply press the
-<span class="emphasis"><em>Delete Printer</em></span> button.
-</p><p>
-To create a new printer, next to the button labelled <span class="emphasis"><em>Create Printer</em></span> enter
-into the text field the name of the share to be created, then click on the
-<span class="emphasis"><em>Create Printer</em></span> button.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2892216"></a>The SWAT Wizard</h3></div></div><p>
-The purpose if the SWAT Wizard is to help the Microsoft knowledgable network administrator
-to configure Samba with a minimum of effort.
-</p><p>
-The Wizard page provides a tool for rewiting the smb.conf file in fully optimised format.
-This will also happen if you press the commit button. The two differ in the the rewrite button
-ignores any changes that may have been made, while the Commit button causes all changes to be
-affected.
-</p><p>
-The <span class="emphasis"><em>Edit</em></span> button permits the editing (setting) of the minimal set of
-options that may be necessary to create a working samba server.
-</p><p>
-Finally, there are a limited set of options that will determine what type of server samba
-will be configured for, whether it will be a WINS server, participate as a WINS client, or
-operate with no WINS support. By clicking on one button you can elect to epose (or not) user
-home directories.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2892261"></a>The Status Page</h3></div></div><p>
-The status page serves a limited purpose. Firstly, it allows control of the samba daemons.
-The key daemons that create the samba server environment are: <b> smbd, nmbd, winbindd</b>.
-</p><p>
-The daemons may be controlled individually or as a total group. Additionally, you may set
-an automatic screen refresh timing. As MS Windows clients interact with Samba new smbd processes
-will be continually spawned. The auto-refresh facility will allow you to track the changing
-conditions with minimal effort.
-</p><p>
-Lastly, the Status page may be used to terminate specific smbd client connections in order to
-free files that may be locked.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2892300"></a>The View Page</h3></div></div><p>
-This page allows the administrator to view the optimised smb.conf file and if you are
-particularly massochistic will permit you also to see all possible global configuration
-parameters and their settings.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2892316"></a>The Password Change Page</h3></div></div><p>
-The Password Change page is a popular tool. This tool allows the creation, deletion, deactivation
-and reactivation of MS Windows networking users on the local machine. Alternatively, you can use
-this tool to change a local password for a user account.
-</p><p>
-When logged in as a non-root account the user will have to provide the old password as well as
-the new password (twice). When logged in as <b>root</b> only the new password is
-required.
-</p><p>
-One popular use for this tool is to change user passwords across a range of remote MS Windows
-servers.
-</p></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="speed"></a>Chapter35.Samba performance issues</h2></div><div><div class="author"><h3 class="author">Paul Cochrane</h3><div class="affiliation"><span class="orgname">Dundee Limb Fitting Centre<br></span><div class="address"><p><tt>&lt;<a href="mailto:paulc@dth.scot.nhs.uk">paulc@dth.scot.nhs.uk</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author">Jelmer R. Vernooij</h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt>&lt;<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</tt></p></div></div></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="#id2891608">Comparisons</a></dt><dt><a href="#id2891653">Socket options</a></dt><dt><a href="#id2892541">Read size</a></dt><dt><a href="#id2892584">Max xmit</a></dt><dt><a href="#id2892637">Log level</a></dt><dt><a href="#id2892660">Read raw</a></dt><dt><a href="#id2892717">Write raw</a></dt><dt><a href="#id2892759">Slow Logins</a></dt><dt><a href="#id2892781">Client tuning</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2891608"></a>Comparisons</h2></div></div><p>
-The Samba server uses TCP to talk to the client. Thus if you are
-trying to see if it performs well you should really compare it to
-programs that use the same protocol. The most readily available
-programs for file transfer that use TCP are ftp or another TCP based
-SMB server.
-</p><p>
-If you want to test against something like a NT or WfWg server then
-you will have to disable all but TCP on either the client or
-server. Otherwise you may well be using a totally different protocol
-(such as Netbeui) and comparisons may not be valid.
-</p><p>
-Generally you should find that Samba performs similarly to ftp at raw
-transfer speed. It should perform quite a bit faster than NFS,
-although this very much depends on your system.
-</p><p>
-Several people have done comparisons between Samba and Novell, NFS or
-WinNT. In some cases Samba performed the best, in others the worst. I
-suspect the biggest factor is not Samba vs some other system but the
-hardware and drivers used on the various systems. Given similar
-hardware Samba should certainly be competitive in speed with other
-systems.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2891653"></a>Socket options</h2></div></div><p>
-There are a number of socket options that can greatly affect the
-performance of a TCP based server like Samba.
-</p><p>
-The socket options that Samba uses are settable both on the command
-line with the -O option, or in the smb.conf file.
-</p><p>
-The <b>socket options</b> section of the <tt>smb.conf</tt> manual page describes how
-to set these and gives recommendations.
-</p><p>
-Getting the socket options right can make a big difference to your
-performance, but getting them wrong can degrade it by just as
-much. The correct settings are very dependent on your local network.
-</p><p>
-The socket option TCP_NODELAY is the one that seems to make the
-biggest single difference for most networks. Many people report that
-adding <b>socket options = TCP_NODELAY</b> doubles the read
-performance of a Samba drive. The best explanation I have seen for this is
-that the Microsoft TCP/IP stack is slow in sending tcp ACKs.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2892541"></a>Read size</h2></div></div><p>
-The option <b>read size</b> affects the overlap of disk
-reads/writes with network reads/writes. If the amount of data being
-transferred in several of the SMB commands (currently SMBwrite, SMBwriteX and
-SMBreadbraw) is larger than this value then the server begins writing
-the data before it has received the whole packet from the network, or
-in the case of SMBreadbraw, it begins writing to the network before
-all the data has been read from disk.
-</p><p>
-This overlapping works best when the speeds of disk and network access
-are similar, having very little effect when the speed of one is much
-greater than the other.
-</p><p>
-The default value is 16384, but very little experimentation has been
-done yet to determine the optimal value, and it is likely that the best
-value will vary greatly between systems anyway. A value over 65536 is
-pointless and will cause you to allocate memory unnecessarily.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2892584"></a>Max xmit</h2></div></div><p>
-At startup the client and server negotiate a <b>maximum transmit</b> size,
-which limits the size of nearly all SMB commands. You can set the
-maximum size that Samba will negotiate using the <b>max xmit = </b> option
-in <tt>smb.conf</tt>. Note that this is the maximum size of SMB requests that
-Samba will accept, but not the maximum size that the *client* will accept.
-The client maximum receive size is sent to Samba by the client and Samba
-honours this limit.
-</p><p>
-It defaults to 65536 bytes (the maximum), but it is possible that some
-clients may perform better with a smaller transmit unit. Trying values
-of less than 2048 is likely to cause severe problems.
-</p><p>
-In most cases the default is the best option.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2892637"></a>Log level</h2></div></div><p>
-If you set the log level (also known as <b>debug level</b>) higher than 2
-then you may suffer a large drop in performance. This is because the
-server flushes the log file after each operation, which can be very
-expensive.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2892660"></a>Read raw</h2></div></div><p>
-The <b>read raw</b> operation is designed to be an optimised, low-latency
-file read operation. A server may choose to not support it,
-however. and Samba makes support for <b>read raw</b> optional, with it
-being enabled by default.
-</p><p>
-In some cases clients don't handle <b>read raw</b> very well and actually
-get lower performance using it than they get using the conventional
-read operations.
-</p><p>
-So you might like to try <b>read raw = no</b> and see what happens on your
-network. It might lower, raise or not affect your performance. Only
-testing can really tell.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2892717"></a>Write raw</h2></div></div><p>
-The <b>write raw</b> operation is designed to be an optimised, low-latency
-file write operation. A server may choose to not support it,
-however. and Samba makes support for <b>write raw</b> optional, with it
-being enabled by default.
-</p><p>
-Some machines may find <b>write raw</b> slower than normal write, in which
-case you may wish to change this option.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2892759"></a>Slow Logins</h2></div></div><p>
-Slow logins are almost always due to the password checking time. Using
-the lowest practical <b>password level</b> will improve things.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2892781"></a>Client tuning</h2></div></div><p>
-Often a speed problem can be traced to the client. The client (for
-example Windows for Workgroups) can often be tuned for better TCP
-performance. Check the sections on the various clients in
-<a href="#Other-Clients" title="Chapter33.Samba and other CIFS clients">Samba and Other Clients</a>.
-</p></div></div></div></div></body></html>
diff --git a/docs/htmldocs/ads.html b/docs/htmldocs/ads.html
index b7468eb091..26ec1d04a7 100644
--- a/docs/htmldocs/ads.html
+++ b/docs/htmldocs/ads.html
@@ -5,7 +5,8 @@
>Samba as a ADS domain member</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
REL="HOME"
TITLE="SAMBA Project Documentation"
HREF="samba-howto-collection.html"><LINK
@@ -13,11 +14,11 @@ REL="UP"
TITLE="Type of installation"
HREF="type.html"><LINK
REL="PREVIOUS"
-TITLE="Samba Backup Domain Controller to Samba Domain Control"
+TITLE="How to Act as a Backup Domain Controller in a Purely Samba Controlled Domain"
HREF="samba-bdc.html"><LINK
REL="NEXT"
-TITLE="Samba as a NT4 or Win2k domain member"
-HREF="domain-member.html"></HEAD
+TITLE="Samba as a NT4 domain member"
+HREF="domain-security.html"></HEAD
><BODY
CLASS="CHAPTER"
BGCOLOR="#FFFFFF"
@@ -59,7 +60,7 @@ WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
-HREF="domain-member.html"
+HREF="domain-security.html"
ACCESSKEY="N"
>Next</A
></TD
@@ -72,73 +73,126 @@ WIDTH="100%"></DIV
CLASS="CHAPTER"
><H1
><A
-NAME="ADS"
-></A
->Chapter 9. Samba as a ADS domain member</H1
-><DIV
-CLASS="TOC"
-><DL
-><DT
-><B
->Table of Contents</B
-></DT
-><DT
->9.1. <A
-HREF="ads.html#AEN1363"
->Setup your <TT
-CLASS="FILENAME"
->smb.conf</TT
-></A
-></DT
-><DT
->9.2. <A
-HREF="ads.html#AEN1376"
->Setup your <TT
-CLASS="FILENAME"
->/etc/krb5.conf</TT
-></A
-></DT
-><DT
->9.3. <A
-HREF="ads.html#ADS-CREATE-MACHINE-ACCOUNT"
->Create the computer account</A
-></DT
-><DT
->9.4. <A
-HREF="ads.html#ADS-TEST-SERVER"
->Test your server setup</A
-></DT
-><DT
->9.5. <A
-HREF="ads.html#ADS-TEST-SMBCLIENT"
->Testing with <SPAN
-CLASS="APPLICATION"
->smbclient</SPAN
-></A
-></DT
-><DT
->9.6. <A
-HREF="ads.html#AEN1424"
->Notes</A
-></DT
-></DL
-></DIV
+NAME="ADS">Chapter 8. Samba as a ADS domain member</H1
><P
>This is a rough guide to setting up Samba 3.0 with kerberos authentication against a
Windows2000 KDC. </P
+><P
+>Pieces you need before you begin:
+<P
+></P
+><TABLE
+BORDER="0"
+><TBODY
+><TR
+><TD
+>a Windows 2000 server.</TD
+></TR
+><TR
+><TD
+>samba 3.0 or higher.</TD
+></TR
+><TR
+><TD
+>the MIT kerberos development libraries (either install from the above sources or use a package). The heimdal libraries will not work.</TD
+></TR
+><TR
+><TD
+>the OpenLDAP development libraries.</TD
+></TR
+></TBODY
+></TABLE
+><P
+></P
+></P
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="AEN1363"
->9.1. Setup your <TT
-CLASS="FILENAME"
->smb.conf</TT
-></A
-></H1
+NAME="AEN1187">8.1. Installing the required packages for Debian</H1
+><P
+>On Debian you need to install the following packages:
+<P
+></P
+><TABLE
+BORDER="0"
+><TBODY
+><TR
+><TD
+>libkrb5-dev</TD
+></TR
+><TR
+><TD
+>krb5-user</TD
+></TR
+></TBODY
+></TABLE
><P
->You must use at least the following 3 options in smb.conf:</P
+></P
+></P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN1193">8.2. Installing the required packages for RedHat</H1
+><P
+>On RedHat this means you should have at least:
+<P
+></P
+><TABLE
+BORDER="0"
+><TBODY
+><TR
+><TD
+>krb5-workstation (for kinit)</TD
+></TR
+><TR
+><TD
+>krb5-libs (for linking with)</TD
+></TR
+><TR
+><TD
+>krb5-devel (because you are compiling from source)</TD
+></TR
+></TBODY
+></TABLE
+><P
+></P
+></P
+><P
+>in addition to the standard development environment.</P
+><P
+>Note that these are not standard on a RedHat install, and you may need
+to get them off CD2.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN1202">8.3. Compile Samba</H1
+><P
+>If your kerberos libraries are in a non-standard location then
+ remember to add the configure option --with-krb5=DIR.</P
+><P
+>After you run configure make sure that include/config.h contains
+ lines like this:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>#define HAVE_KRB5 1
+#define HAVE_LDAP 1</PRE
+></P
+><P
+>If it doesn't then configure did not find your krb5 libraries or
+ your ldap libraries. Look in config.log to figure out why and fix
+ it.</P
+><P
+>Then compile and install Samba as usual. You must use at least the
+ following 3 options in smb.conf:</P
><P
><PRE
CLASS="PROGRAMLISTING"
@@ -159,103 +213,34 @@ CLASS="FILENAME"
CLASS="PROGRAMLISTING"
> ads server = your.kerberos.server</PRE
></P
-><DIV
-CLASS="NOTE"
-><P
-></P
-><TABLE
-CLASS="NOTE"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
><P
->You do *not* need a smbpasswd file, and older clients will
- be authenticated as if <B
-CLASS="COMMAND"
->security = domain</B
->,
- although it won't do any harm
- and allows you to have local users not in the domain.
- I expect that the above required options will change soon when we get better
- active directory integration.</P
-></TD
-></TR
-></TABLE
-></DIV
+>You do *not* need a smbpasswd file, although it won't do any harm
+ and if you have one then Samba will be able to fall back to normal
+ password security for older clients. I expect that the above
+ required options will change soon when we get better active
+ directory integration.</P
></DIV
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="AEN1376"
->9.2. Setup your <TT
-CLASS="FILENAME"
->/etc/krb5.conf</TT
-></A
-></H1
+NAME="AEN1217">8.4. Setup your /etc/krb5.conf</H1
><P
->The minimal configuration for <TT
-CLASS="FILENAME"
->krb5.conf</TT
-> is:</P
+>The minimal configuration for krb5.conf is:</P
><P
><PRE
CLASS="PROGRAMLISTING"
->[realms]
+> [realms]
YOUR.KERBEROS.REALM = {
kdc = your.kerberos.server
}</PRE
></P
><P
->Test your config by doing a <KBD
-CLASS="USERINPUT"
->kinit <VAR
-CLASS="REPLACEABLE"
->USERNAME</VAR
->@<VAR
-CLASS="REPLACEABLE"
->REALM</VAR
-></KBD
-> and making sure that
+>Test your config by doing a "kinit USERNAME@REALM" and making sure that
your password is accepted by the Win2000 KDC. </P
-><DIV
-CLASS="NOTE"
-><P
-></P
-><TABLE
-CLASS="NOTE"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
><P
->The realm must be uppercase. </P
-></TD
-></TR
-></TABLE
-></DIV
+>NOTE: The realm must be uppercase. </P
><P
>You also must ensure that you can do a reverse DNS lookup on the IP
address of your KDC. Also, the name that this reverse lookup maps to
@@ -263,65 +248,36 @@ must either be the netbios name of the KDC (ie. the hostname with no
domain attached) or it can alternatively be the netbios name
followed by the realm. </P
><P
->The easiest way to ensure you get this right is to add a
-<TT
-CLASS="FILENAME"
->/etc/hosts</TT
-> entry mapping the IP address of your KDC to
-its netbios name. If you don't get this right then you will get a
-"local error" when you try to join the realm.</P
-><P
->If all you want is kerberos support in <SPAN
-CLASS="APPLICATION"
->smbclient</SPAN
-> then you can skip
-straight to <A
-HREF="ads.html#ADS-TEST-SMBCLIENT"
->Test with <SPAN
-CLASS="APPLICATION"
->smbclient</SPAN
-></A
-> now.
-<A
-HREF="ads.html#ADS-CREATE-MACHINE-ACCOUNT"
->Creating a computer account</A
->
-and <A
-HREF="ads.html#ADS-TEST-SERVER"
->testing your servers</A
->
-is only needed if you want kerberos
-support for <SPAN
-CLASS="APPLICATION"
->smbd</SPAN
-> and <SPAN
-CLASS="APPLICATION"
->winbindd</SPAN
->.</P
+>The easiest way to ensure you get this right is to add a /etc/hosts
+entry mapping the IP address of your KDC to its netbios name. If you
+don't get this right then you will get a "local error" when you try
+to join the realm.</P
+><P
+>If all you want is kerberos support in smbclient then you can skip
+straight to step 5 now. Step 3 is only needed if you want kerberos
+support in smbd.</P
></DIV
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="ADS-CREATE-MACHINE-ACCOUNT"
->9.3. Create the computer account</A
-></H1
+NAME="AEN1227">8.5. Create the computer account</H1
><P
->As a user that has write permission on the Samba private directory
+>Do a "kinit" as a user that has authority to change arbitrary
+passwords on the KDC ("Administrator" is a good choice). Then as a
+user that has write permission on the Samba private directory
(usually root) run:
-<KBD
-CLASS="USERINPUT"
->net ads join</KBD
+<B
+CLASS="COMMAND"
+>net ads join</B
></P
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
-NAME="AEN1404"
->9.3.1. Possible errors</A
-></H2
+NAME="AEN1231">8.5.1. Possible errors</H2
><P
><P
></P
@@ -329,6 +285,12 @@ NAME="AEN1404"
CLASS="VARIABLELIST"
><DL
><DT
+>"bash: kinit: command not found"</DT
+><DD
+><P
+>kinit is in the krb5-workstation RPM on RedHat systems, and is in /usr/kerberos/bin, so it won't be in the path until you log in again (or open a new terminal)</P
+></DD
+><DT
>"ADS support not compiled in"</DT
><DD
><P
@@ -344,18 +306,16 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="ADS-TEST-SERVER"
->9.4. Test your server setup</A
-></H1
+NAME="AEN1243">8.6. Test your server setup</H1
><P
->On a Windows 2000 client try <KBD
-CLASS="USERINPUT"
->net use * \\server\share</KBD
+>On a Windows 2000 client try <B
+CLASS="COMMAND"
+>net use * \\server\share</B
>. You should
be logged in with kerberos without needing to know a password. If
-this fails then run <KBD
-CLASS="USERINPUT"
->klist tickets</KBD
+this fails then run <B
+CLASS="COMMAND"
+>klist tickets</B
>. Did you get a ticket for the
server? Does it have an encoding type of DES-CBC-MD5 ? </P
></DIV
@@ -364,37 +324,21 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="ADS-TEST-SMBCLIENT"
->9.5. Testing with <SPAN
-CLASS="APPLICATION"
->smbclient</SPAN
-></A
-></H1
+NAME="AEN1248">8.7. Testing with smbclient</H1
><P
>On your Samba server try to login to a Win2000 server or your Samba
-server using <SPAN
-CLASS="APPLICATION"
->smbclient</SPAN
-> and kerberos. Use <SPAN
-CLASS="APPLICATION"
->smbclient</SPAN
-> as usual, but
-specify the <VAR
-CLASS="PARAMETER"
->-k</VAR
-> option to choose kerberos authentication.</P
+server using smbclient and kerberos. Use smbclient as usual, but
+specify the -k option to choose kerberos authentication.</P
></DIV
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="AEN1424"
->9.6. Notes</A
-></H1
+NAME="AEN1251">8.8. Notes</H1
><P
->You must change administrator password at least once after DC
-install, to create the right encoding types</P
+>You must change administrator password at least once after DC install,
+ to create the right encoding types</P
><P
>w2k doesn't seem to create the _kerberos._udp and _ldap._tcp in
their defaults DNS setup. Maybe fixed in service packs?</P
@@ -434,7 +378,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
-HREF="domain-member.html"
+HREF="domain-security.html"
ACCESSKEY="N"
>Next</A
></TD
@@ -444,7 +388,7 @@ ACCESSKEY="N"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
->Samba Backup Domain Controller to Samba Domain Control</TD
+>How to Act as a Backup Domain Controller in a Purely Samba Controlled Domain</TD
><TD
WIDTH="34%"
ALIGN="center"
@@ -458,7 +402,7 @@ ACCESSKEY="U"
WIDTH="33%"
ALIGN="right"
VALIGN="top"
->Samba as a NT4 or Win2k domain member</TD
+>Samba as a NT4 domain member</TD
></TR
></TABLE
></DIV
diff --git a/docs/htmldocs/advancednetworkmanagement.html b/docs/htmldocs/advancednetworkmanagement.html
deleted file mode 100644
index b55eed16bc..0000000000
--- a/docs/htmldocs/advancednetworkmanagement.html
+++ /dev/null
@@ -1,555 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<HTML
-><HEAD
-><TITLE
->Advanced Network Manangement</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
-REL="HOME"
-TITLE="SAMBA Project Documentation"
-HREF="samba-howto-collection.html"><LINK
-REL="UP"
-TITLE="Advanced Configuration"
-HREF="optional.html"><LINK
-REL="PREVIOUS"
-TITLE="Unified Logons between Windows NT and UNIX using Winbind"
-HREF="winbind.html"><LINK
-REL="NEXT"
-TITLE="System and Account Policies"
-HREF="policymgmt.html"></HEAD
-><BODY
-CLASS="CHAPTER"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->SAMBA Project Documentation</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="winbind.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
-></TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="policymgmt.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="CHAPTER"
-><H1
-><A
-NAME="ADVANCEDNETWORKMANAGEMENT"
-></A
->Chapter 16. Advanced Network Manangement</H1
-><DIV
-CLASS="TOC"
-><DL
-><DT
-><B
->Table of Contents</B
-></DT
-><DT
->16.1. <A
-HREF="advancednetworkmanagement.html#AEN2869"
->Configuring Samba Share Access Controls</A
-></DT
-><DT
->16.2. <A
-HREF="advancednetworkmanagement.html#AEN2907"
->Remote Server Administration</A
-></DT
-><DT
->16.3. <A
-HREF="advancednetworkmanagement.html#AEN2924"
->Network Logon Script Magic</A
-></DT
-></DL
-></DIV
-><P
->This section attempts to document peripheral issues that are of great importance to network
-administrators who want to improve network resource access control, to automate the user
-environment, and to make their lives a little easier.</P
-><DIV
-CLASS="SECT1"
-><H1
-CLASS="SECT1"
-><A
-NAME="AEN2869"
->16.1. Configuring Samba Share Access Controls</A
-></H1
-><P
->This section deals with how to configure Samba per share access control restrictions.
-By default samba sets no restrictions on the share itself. Restrictions on the share itself
-can be set on MS Windows NT4/200x/XP shares. This can be a very effective way to limit who can
-connect to a share. In the absence of specific restrictions the default setting is to allow
-the global user <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->Everyone</I
-></SPAN
-> Full Control (ie: Full control, Change and Read).</P
-><P
->At this time Samba does NOT provide a tool for configuring access control setting on the Share
-itself. Samba does have the capacity to store and act on access control settings, but the only
-way to create those settings is to use either the NT4 Server Manager or the Windows 200x MMC for
-Computer Management.</P
-><P
->Samba stores the per share access control settings in a file called <TT
-CLASS="FILENAME"
->share_info.tdb</TT
->.
-The location of this file on your system will depend on how samba was compiled. The default location
-for samba's tdb files is under <TT
-CLASS="FILENAME"
->/usr/local/samba/var</TT
->. If the <TT
-CLASS="FILENAME"
->tdbdump</TT
->
-utility has been compiled and installed on your system then you can examine the contents of this file
-by: <KBD
-CLASS="USERINPUT"
->tdbdump share_info.tdb</KBD
->.</P
-><DIV
-CLASS="SECT2"
-><H2
-CLASS="SECT2"
-><A
-NAME="AEN2879"
->16.1.1. Share Permissions Management</A
-></H2
-><P
->The best tool for the task is platform dependant. Choose the best tool for your environmemt.</P
-><DIV
-CLASS="SECT3"
-><H3
-CLASS="SECT3"
-><A
-NAME="AEN2882"
->16.1.1.1. Windows NT4 Workstation/Server</A
-></H3
-><P
->The tool you need to use to manage share permissions on a Samba server is the NT Server Manager.
-Server Manager is shipped with Windows NT4 Server products but not with Windows NT4 Workstation.
-You can obtain the NT Server Manager for MS Windows NT4 Workstation from Microsoft - see details below.</P
-><DIV
-CLASS="PROCEDURE"
-><P
-><B
->Instructions</B
-></P
-><OL
-TYPE="1"
-><LI
-><P
->Launch the NT4 Server Manager, click on the Samba server you want to administer, then from the menu
-select Computer, then click on the Shared Directories entry.</P
-></LI
-><LI
-><P
-> Now click on the share that you wish to manage, then click on the Properties tab, next click on
- the Permissions tab. Now you can Add or change access control settings as you wish.</P
-></LI
-></OL
-></DIV
-></DIV
-><DIV
-CLASS="SECT3"
-><H3
-CLASS="SECT3"
-><A
-NAME="AEN2891"
->16.1.1.2. Windows 200x/XP</A
-></H3
-><P
->On MS Windows NT4/200x/XP system access control lists on the share itself are set using native
-tools, usually from filemanager. For example, in Windows 200x: right click on the shared folder,
-then select 'Sharing', then click on 'Permissions'. The default Windows NT4/200x permission allows
-<SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->Everyone</I
-></SPAN
-> Full Control on the Share.</P
-><P
->MS Windows 200x and later all comes with a tool called the 'Computer Management' snap-in for the
-Microsoft Management Console (MMC). This tool is located by clicking on <TT
-CLASS="FILENAME"
->Control Panel -&#62;
-Administrative Tools -&#62; Computer Management</TT
->.</P
-><DIV
-CLASS="PROCEDURE"
-><P
-><B
->Instructions</B
-></P
-><OL
-TYPE="1"
-><LI
-><P
-> After launching the MMC with the Computer Management snap-in, click on the menu item 'Action',
- select 'Connect to another computer'. If you are not logged onto a domain you will be prompted
- to enter a domain login user identifier and a password. This will authenticate you to the domain.
- If you where already logged in with administrative privilidge this step is not offered.</P
-></LI
-><LI
-><P
->If the Samba server is not shown in the Select Computer box, then type in the name of the target
-Samba server in the field 'Name:'. Now click on the [+] next to 'System Tools', then on the [+]
-next to 'Shared Folders' in the left panel.</P
-></LI
-><LI
-><P
->Now in the right panel, double-click on the share you wish to set access control permissions on.
-Then click on the tab 'Share Permissions'. It is now possible to add access control entities
-to the shared folder. Do NOT forget to set what type of access (full control, change, read) you
-wish to assign for each entry.</P
-></LI
-></OL
-></DIV
-><DIV
-CLASS="WARNING"
-><P
-></P
-><TABLE
-CLASS="WARNING"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/warning.gif"
-HSPACE="5"
-ALT="Warning"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->Be careful. If you take away all permissions from the Everyone user without removing this user
-then effectively no user will be able to access the share. This is a result of what is known as
-ACL precidence. ie: Everyone with NO ACCESS means that MaryK who is part of the group Everyone
-will have no access even if this user is given explicit full control access.</P
-></TD
-></TR
-></TABLE
-></DIV
-></DIV
-></DIV
-></DIV
-><DIV
-CLASS="SECT1"
-><H1
-CLASS="SECT1"
-><A
-NAME="AEN2907"
->16.2. Remote Server Administration</A
-></H1
-><P
-><SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->How do I get 'User Manager' and 'Server Manager'?</I
-></SPAN
-></P
-><P
->Since I don't need to buy an NT4 Server, how do I get the 'User Manager for Domains',
-the 'Server Manager'?</P
-><P
->Microsoft distributes a version of these tools called nexus for installation on Windows 9x / Me
-systems. The tools set includes:</P
-><P
-></P
-><UL
-><LI
-><P
->Server Manager</P
-></LI
-><LI
-><P
->User Manager for Domains</P
-></LI
-><LI
-><P
->Event Viewer</P
-></LI
-></UL
-><P
->Click here to download the archived file <A
-HREF="ftp://ftp.microsoft.com/Softlib/MSLFILES/NEXUS.EXE"
-TARGET="_top"
->ftp://ftp.microsoft.com/Softlib/MSLFILES/NEXUS.EXE</A
-></P
-><P
->The Windows NT 4.0 version of the 'User Manager for
-Domains' and 'Server Manager' are available from Microsoft via ftp
-from <A
-HREF="ftp://ftp.microsoft.com/Softlib/MSLFILES/SRVTOOLS.EXE"
-TARGET="_top"
->ftp://ftp.microsoft.com/Softlib/MSLFILES/SRVTOOLS.EXE</A
-></P
-></DIV
-><DIV
-CLASS="SECT1"
-><H1
-CLASS="SECT1"
-><A
-NAME="AEN2924"
->16.3. Network Logon Script Magic</A
-></H1
-><P
->This section needs work. Volunteer contributions most welcome. Please send your patches or updates
-to <A
-HREF="mailto:jht@samba.org"
-TARGET="_top"
->John Terpstra</A
->.</P
-><P
->There are several opportunities for creating a custom network startup configuration environment.</P
-><P
-></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
->No Logon Script</TD
-></TR
-><TR
-><TD
->Simple universal Logon Script that applies to all users</TD
-></TR
-><TR
-><TD
->Use of a conditional Logon Script that applies per user or per group attirbutes</TD
-></TR
-><TR
-><TD
->Use of Samba's Preexec and Postexec functions on access to the NETLOGON share to create
- a custom Logon Script and then execute it.</TD
-></TR
-><TR
-><TD
->User of a tool such as KixStart</TD
-></TR
-></TBODY
-></TABLE
-><P
-></P
-><P
->The Samba source code tree includes two logon script generation/execution tools. See <TT
-CLASS="FILENAME"
->examples</TT
-> directory <TT
-CLASS="FILENAME"
->genlogon</TT
-> and <TT
-CLASS="FILENAME"
->ntlogon</TT
-> subdirectories.</P
-><P
->The following listings are from the genlogon directory.</P
-><P
->This is the genlogon.pl file:
-
-<PRE
-CLASS="PROGRAMLISTING"
-> #!/usr/bin/perl
- #
- # genlogon.pl
- #
- # Perl script to generate user logon scripts on the fly, when users
- # connect from a Windows client. This script should be called from smb.conf
- # with the %U, %G and %L parameters. I.e:
- #
- # root preexec = genlogon.pl %U %G %L
- #
- # The script generated will perform
- # the following:
- #
- # 1. Log the user connection to /var/log/samba/netlogon.log
- # 2. Set the PC's time to the Linux server time (which is maintained
- # daily to the National Institute of Standard's Atomic clock on the
- # internet.
- # 3. Connect the user's home drive to H: (H for Home).
- # 4. Connect common drives that everyone uses.
- # 5. Connect group-specific drives for certain user groups.
- # 6. Connect user-specific drives for certain users.
- # 7. Connect network printers.
-
- # Log client connection
- #($sec,$min,$hour,$mday,$mon,$year,$wday,$yday,$isdst) = localtime(time);
- ($sec,$min,$hour,$mday,$mon,$year,$wday,$yday,$isdst) = localtime(time);
- open LOG, "&#62;&#62;/var/log/samba/netlogon.log";
- print LOG "$mon/$mday/$year $hour:$min:$sec - User $ARGV[0] logged into $ARGV[1]\n";
- close LOG;
-
- # Start generating logon script
- open LOGON, "&#62;/shared/netlogon/$ARGV[0].bat";
- print LOGON "\@ECHO OFF\r\n";
-
- # Connect shares just use by Software Development group
- if ($ARGV[1] eq "SOFTDEV" || $ARGV[0] eq "softdev")
- {
- print LOGON "NET USE M: \\\\$ARGV[2]\\SOURCE\r\n";
- }
-
- # Connect shares just use by Technical Support staff
- if ($ARGV[1] eq "SUPPORT" || $ARGV[0] eq "support")
- {
- print LOGON "NET USE S: \\\\$ARGV[2]\\SUPPORT\r\n";
- }
-
- # Connect shares just used by Administration staff
- If ($ARGV[1] eq "ADMIN" || $ARGV[0] eq "admin")
- {
- print LOGON "NET USE L: \\\\$ARGV[2]\\ADMIN\r\n";
- print LOGON "NET USE K: \\\\$ARGV[2]\\MKTING\r\n";
- }
-
- # Now connect Printers. We handle just two or three users a little
- # differently, because they are the exceptions that have desktop
- # printers on LPT1: - all other user's go to the LaserJet on the
- # server.
- if ($ARGV[0] eq 'jim'
- || $ARGV[0] eq 'yvonne')
- {
- print LOGON "NET USE LPT2: \\\\$ARGV[2]\\LJET3\r\n";
- print LOGON "NET USE LPT3: \\\\$ARGV[2]\\FAXQ\r\n";
- }
- else
- {
- print LOGON "NET USE LPT1: \\\\$ARGV[2]\\LJET3\r\n";
- print LOGON "NET USE LPT3: \\\\$ARGV[2]\\FAXQ\r\n";
- }
-
- # All done! Close the output file.
- close LOGON;</PRE
-></P
-><P
->Those wishing to use more elaborate or capable logon processing system should check out the following sites:</P
-><P
-></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
->http://www.craigelachie.org/rhacer/ntlogon</TD
-></TR
-><TR
-><TD
->http://www.kixtart.org</TD
-></TR
-></TBODY
-></TABLE
-><P
-></P
-></DIV
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="winbind.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="samba-howto-collection.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="policymgmt.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Unified Logons between Windows NT and UNIX using Winbind</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="optional.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->System and Account Policies</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
-> \ No newline at end of file
diff --git a/docs/htmldocs/appendixes.html b/docs/htmldocs/appendixes.html
index 8015702c51..e7eefcb441 100644
--- a/docs/htmldocs/appendixes.html
+++ b/docs/htmldocs/appendixes.html
@@ -5,16 +5,17 @@
>Appendixes</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
REL="HOME"
TITLE="SAMBA Project Documentation"
HREF="samba-howto-collection.html"><LINK
REL="PREVIOUS"
-TITLE="Unicode/Charsets"
-HREF="unicode.html"><LINK
+TITLE="Samba performance issues"
+HREF="speed.html"><LINK
REL="NEXT"
-TITLE="How to compile SAMBA"
-HREF="compiling.html"></HEAD
+TITLE="Portability"
+HREF="portability.html"></HEAD
><BODY
CLASS="PART"
BGCOLOR="#FFFFFF"
@@ -42,7 +43,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
-HREF="unicode.html"
+HREF="speed.html"
ACCESSKEY="P"
>Prev</A
></TD
@@ -56,7 +57,7 @@ WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
-HREF="compiling.html"
+HREF="portability.html"
ACCESSKEY="N"
>Next</A
></TD
@@ -68,13 +69,262 @@ WIDTH="100%"></DIV
><DIV
CLASS="PART"
><A
-NAME="APPENDIXES"
-></A
-><DIV
+NAME="APPENDIXES"><DIV
CLASS="TITLEPAGE"
><H1
CLASS="TITLE"
>IV. Appendixes</H1
+><DIV
+CLASS="TOC"
+><DL
+><DT
+><B
+>Table of Contents</B
+></DT
+><DT
+>23. <A
+HREF="portability.html"
+>Portability</A
+></DT
+><DD
+><DL
+><DT
+>23.1. <A
+HREF="portability.html#AEN3139"
+>HPUX</A
+></DT
+><DT
+>23.2. <A
+HREF="portability.html#AEN3145"
+>SCO Unix</A
+></DT
+><DT
+>23.3. <A
+HREF="portability.html#AEN3149"
+>DNIX</A
+></DT
+><DT
+>23.4. <A
+HREF="portability.html#AEN3178"
+>RedHat Linux Rembrandt-II</A
+></DT
+></DL
+></DD
+><DT
+>24. <A
+HREF="other-clients.html"
+>Samba and other CIFS clients</A
+></DT
+><DD
+><DL
+><DT
+>24.1. <A
+HREF="other-clients.html#AEN3199"
+>Macintosh clients?</A
+></DT
+><DT
+>24.2. <A
+HREF="other-clients.html#AEN3208"
+>OS2 Client</A
+></DT
+><DD
+><DL
+><DT
+>24.2.1. <A
+HREF="other-clients.html#AEN3210"
+>How can I configure OS/2 Warp Connect or
+ OS/2 Warp 4 as a client for Samba?</A
+></DT
+><DT
+>24.2.2. <A
+HREF="other-clients.html#AEN3225"
+>How can I configure OS/2 Warp 3 (not Connect),
+ OS/2 1.2, 1.3 or 2.x for Samba?</A
+></DT
+><DT
+>24.2.3. <A
+HREF="other-clients.html#AEN3234"
+>Are there any other issues when OS/2 (any version)
+ is used as a client?</A
+></DT
+><DT
+>24.2.4. <A
+HREF="other-clients.html#AEN3238"
+>How do I get printer driver download working
+ for OS/2 clients?</A
+></DT
+></DL
+></DD
+><DT
+>24.3. <A
+HREF="other-clients.html#AEN3248"
+>Windows for Workgroups</A
+></DT
+><DD
+><DL
+><DT
+>24.3.1. <A
+HREF="other-clients.html#AEN3250"
+>Use latest TCP/IP stack from Microsoft</A
+></DT
+><DT
+>24.3.2. <A
+HREF="other-clients.html#AEN3255"
+>Delete .pwl files after password change</A
+></DT
+><DT
+>24.3.3. <A
+HREF="other-clients.html#AEN3260"
+>Configure WfW password handling</A
+></DT
+><DT
+>24.3.4. <A
+HREF="other-clients.html#AEN3264"
+>Case handling of passwords</A
+></DT
+></DL
+></DD
+><DT
+>24.4. <A
+HREF="other-clients.html#AEN3269"
+>Windows '95/'98</A
+></DT
+><DT
+>24.5. <A
+HREF="other-clients.html#AEN3285"
+>Windows 2000 Service Pack 2</A
+></DT
+></DL
+></DD
+><DT
+>25. <A
+HREF="bugreport.html"
+>Reporting Bugs</A
+></DT
+><DD
+><DL
+><DT
+>25.1. <A
+HREF="bugreport.html#AEN3309"
+>Introduction</A
+></DT
+><DT
+>25.2. <A
+HREF="bugreport.html#AEN3319"
+>General info</A
+></DT
+><DT
+>25.3. <A
+HREF="bugreport.html#AEN3325"
+>Debug levels</A
+></DT
+><DT
+>25.4. <A
+HREF="bugreport.html#AEN3342"
+>Internal errors</A
+></DT
+><DT
+>25.5. <A
+HREF="bugreport.html#AEN3352"
+>Attaching to a running process</A
+></DT
+><DT
+>25.6. <A
+HREF="bugreport.html#AEN3355"
+>Patches</A
+></DT
+></DL
+></DD
+><DT
+>26. <A
+HREF="diagnosis.html"
+>Diagnosing your samba server</A
+></DT
+><DD
+><DL
+><DT
+>26.1. <A
+HREF="diagnosis.html#AEN3378"
+>Introduction</A
+></DT
+><DT
+>26.2. <A
+HREF="diagnosis.html#AEN3383"
+>Assumptions</A
+></DT
+><DT
+>26.3. <A
+HREF="diagnosis.html#AEN3393"
+>Tests</A
+></DT
+><DD
+><DL
+><DT
+>26.3.1. <A
+HREF="diagnosis.html#AEN3395"
+>Test 1</A
+></DT
+><DT
+>26.3.2. <A
+HREF="diagnosis.html#AEN3401"
+>Test 2</A
+></DT
+><DT
+>26.3.3. <A
+HREF="diagnosis.html#AEN3407"
+>Test 3</A
+></DT
+><DT
+>26.3.4. <A
+HREF="diagnosis.html#AEN3422"
+>Test 4</A
+></DT
+><DT
+>26.3.5. <A
+HREF="diagnosis.html#AEN3427"
+>Test 5</A
+></DT
+><DT
+>26.3.6. <A
+HREF="diagnosis.html#AEN3433"
+>Test 6</A
+></DT
+><DT
+>26.3.7. <A
+HREF="diagnosis.html#AEN3441"
+>Test 7</A
+></DT
+><DT
+>26.3.8. <A
+HREF="diagnosis.html#AEN3467"
+>Test 8</A
+></DT
+><DT
+>26.3.9. <A
+HREF="diagnosis.html#AEN3484"
+>Test 9</A
+></DT
+><DT
+>26.3.10. <A
+HREF="diagnosis.html#AEN3492"
+>Test 10</A
+></DT
+><DT
+>26.3.11. <A
+HREF="diagnosis.html#AEN3498"
+>Test 11</A
+></DT
+></DL
+></DD
+><DT
+>26.4. <A
+HREF="diagnosis.html#AEN3503"
+>Still having troubles?</A
+></DT
+></DL
+></DD
+></DL
+></DIV
></DIV
></DIV
><DIV
@@ -93,7 +343,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
-HREF="unicode.html"
+HREF="speed.html"
ACCESSKEY="P"
>Prev</A
></TD
@@ -111,7 +361,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
-HREF="compiling.html"
+HREF="portability.html"
ACCESSKEY="N"
>Next</A
></TD
@@ -121,7 +371,7 @@ ACCESSKEY="N"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
->Unicode/Charsets</TD
+>Samba performance issues</TD
><TD
WIDTH="34%"
ALIGN="center"
@@ -131,7 +381,7 @@ VALIGN="top"
WIDTH="33%"
ALIGN="right"
VALIGN="top"
->How to compile SAMBA</TD
+>Portability</TD
></TR
></TABLE
></DIV
diff --git a/docs/htmldocs/browsing-quick.html b/docs/htmldocs/browsing-quick.html
index 4611db7195..8c597e001f 100644
--- a/docs/htmldocs/browsing-quick.html
+++ b/docs/htmldocs/browsing-quick.html
@@ -5,7 +5,8 @@
>Quick Cross Subnet Browsing / Cross Workgroup Browsing guide</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
REL="HOME"
TITLE="SAMBA Project Documentation"
HREF="samba-howto-collection.html"><LINK
@@ -13,11 +14,11 @@ REL="UP"
TITLE="General installation"
HREF="introduction.html"><LINK
REL="PREVIOUS"
-TITLE="How to Install and Test SAMBA"
-HREF="install.html"><LINK
+TITLE="Improved browsing in samba"
+HREF="improved-browsing.html"><LINK
REL="NEXT"
-TITLE="User information database"
-HREF="passdb.html"></HEAD
+TITLE="LanMan and NT Password Encryption in Samba"
+HREF="pwencrypt.html"></HEAD
><BODY
CLASS="CHAPTER"
BGCOLOR="#FFFFFF"
@@ -45,7 +46,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
-HREF="install.html"
+HREF="improved-browsing.html"
ACCESSKEY="P"
>Prev</A
></TD
@@ -59,7 +60,7 @@ WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
-HREF="passdb.html"
+HREF="pwencrypt.html"
ACCESSKEY="N"
>Next</A
></TD
@@ -72,74 +73,7 @@ WIDTH="100%"></DIV
CLASS="CHAPTER"
><H1
><A
-NAME="BROWSING-QUICK"
-></A
->Chapter 3. Quick Cross Subnet Browsing / Cross Workgroup Browsing guide</H1
-><DIV
-CLASS="TOC"
-><DL
-><DT
-><B
->Table of Contents</B
-></DT
-><DT
->3.1. <A
-HREF="browsing-quick.html#AEN305"
->Discussion</A
-></DT
-><DT
->3.2. <A
-HREF="browsing-quick.html#AEN326"
->How browsing functions and how to deploy stable and
-dependable browsing using Samba</A
-></DT
-><DT
->3.3. <A
-HREF="browsing-quick.html#AEN340"
->Use of the <B
-CLASS="COMMAND"
->Remote Announce</B
-> parameter</A
-></DT
-><DT
->3.4. <A
-HREF="browsing-quick.html#AEN363"
->Use of the <B
-CLASS="COMMAND"
->Remote Browse Sync</B
-> parameter</A
-></DT
-><DT
->3.5. <A
-HREF="browsing-quick.html#AEN374"
->Use of WINS</A
-></DT
-><DD
-><DL
-><DT
->3.5.1. <A
-HREF="browsing-quick.html#AEN391"
->WINS Replication</A
-></DT
-><DT
->3.5.2. <A
-HREF="browsing-quick.html#AEN395"
->Static WINS Entries</A
-></DT
-></DL
-></DD
-><DT
->3.6. <A
-HREF="browsing-quick.html#AEN400"
->Do NOT use more than one (1) protocol on MS Windows machines</A
-></DT
-><DT
->3.7. <A
-HREF="browsing-quick.html#AEN408"
->Name Resolution Order</A
-></DT
-></DL
-></DIV
+NAME="BROWSING-QUICK">Chapter 3. Quick Cross Subnet Browsing / Cross Workgroup Browsing guide</H1
><P
>This document should be read in conjunction with Browsing and may
be taken as the fast track guide to implementing browsing across subnets
@@ -147,117 +81,43 @@ and / or across workgroups (or domains). WINS is the best tool for resolution
of NetBIOS names to IP addesses. WINS is NOT involved in browse list handling
except by way of name to address mapping.</P
><DIV
-CLASS="NOTE"
-><P
-></P
-><TABLE
-CLASS="NOTE"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->MS Windows 2000 and later can be configured to operate with NO NetBIOS
-over TCP/IP. Samba-3 and later also supports this mode of operation.</P
-></TD
-></TR
-></TABLE
-></DIV
-><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="AEN305"
->3.1. Discussion</A
-></H1
+NAME="AEN377">3.1. Discussion</H1
><P
>Firstly, all MS Windows networking is based on SMB (Server Message
-Block) based messaging. SMB messaging may be implemented using NetBIOS or
-without NetBIOS. Samba implements NetBIOS by encapsulating it over TCP/IP.
-MS Windows products can do likewise. NetBIOS based networking uses broadcast
-messaging to affect browse list management. When running NetBIOS over
-TCP/IP this uses UDP based messaging. UDP messages can be broadcast or unicast.</P
+Block) based messaging. SMB messaging is implemented using NetBIOS. Samba
+implements NetBIOS by encapsulating it over TCP/IP. MS Windows products can
+do likewise. NetBIOS based networking uses broadcast messaging to affect
+browse list management. When running NetBIOS over TCP/IP this uses UDP
+based messaging. UDP messages can be broadcast or unicast.</P
><P
>Normally, only unicast UDP messaging can be forwarded by routers. The
-<B
-CLASS="COMMAND"
->remote announce</B
->
-parameter to smb.conf helps to project browse announcements
-to remote network segments via unicast UDP. Similarly, the
-<B
-CLASS="COMMAND"
->remote browse sync</B
-> parameter of <TT
-CLASS="FILENAME"
->smb.conf</TT
->
-implements browse list collation using unicast UDP.</P
+"remote announce" parameter to smb.conf helps to project browse announcements
+to remote network segments via unicast UDP. Similarly, the "remote browse sync"
+parameter of smb.conf implements browse list collation using unicast UDP.</P
><P
>Secondly, in those networks where Samba is the only SMB server technology
-wherever possible <SPAN
-CLASS="APPLICATION"
->nmbd</SPAN
-> should be configured on one (1) machine as the WINS
+wherever possible nmbd should be configured on one (1) machine as the WINS
server. This makes it easy to manage the browsing environment. If each network
segment is configured with it's own Samba WINS server, then the only way to
-get cross segment browsing to work is by using the
-<B
-CLASS="COMMAND"
->remote announce</B
-> and the <B
-CLASS="COMMAND"
->remote browse sync</B
->
-parameters to your <TT
-CLASS="FILENAME"
->smb.conf</TT
-> file.</P
-><P
->If only one WINS server is used for an entire multi-segment network then
-the use of the <B
-CLASS="COMMAND"
->remote announce</B
-> and the
-<B
-CLASS="COMMAND"
->remote browse sync</B
-> parameters should NOT be necessary.</P
-><P
->As of Samba 3 WINS replication is being worked on. The bulk of the code has
-been committed, but it still needs maturation.</P
-><P
->Right now samba WINS does not support MS-WINS replication. This means that
-when setting up Samba as a WINS server there must only be one <SPAN
-CLASS="APPLICATION"
->nmbd</SPAN
-> configured
-as a WINS server on the network. Some sites have used multiple Samba WINS
-servers for redundancy (one server per subnet) and then used
-<B
-CLASS="COMMAND"
->remote browse sync</B
-> and <B
-CLASS="COMMAND"
->remote announce</B
->
-to affect browse list collation across all
-segments. Note that this means clients will only resolve local names,
-and must be configured to use DNS to resolve names on other subnets in
-order to resolve the IP addresses of the servers they can see on other
-subnets. This setup is not recommended, but is mentioned as a practical
-consideration (ie: an 'if all else fails' scenario).</P
+get cross segment browsing to work is by using the "remote announce" and
+the "remote browse sync" parameters to your smb.conf file.</P
+><P
+>If only one WINS server is used then the use of the "remote announce" and the
+"remote browse sync" parameters should NOT be necessary.</P
+><P
+>Samba WINS does not support MS-WINS replication. This means that when setting up
+Samba as a WINS server there must only be one nmbd configured as a WINS server
+on the network. Some sites have used multiple Samba WINS servers for redundancy
+(one server per subnet) and then used "remote browse sync" and "remote announce"
+to affect browse list collation across all segments. Note that this means
+clients will only resolve local names, and must be configured to use DNS to
+resolve names on other subnets in order to resolve the IP addresses of the
+servers they can see on other subnets. This setup is not recommended, but is
+mentioned as a practical consideration (ie: an 'if all else fails' scenario).</P
><P
>Lastly, take note that browse lists are a collection of unreliable broadcast
messages that are repeated at intervals of not more than 15 minutes. This means
@@ -269,120 +129,19 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="AEN326"
->3.2. How browsing functions and how to deploy stable and
-dependable browsing using Samba</A
-></H1
-><P
->As stated above, MS Windows machines register their NetBIOS names
-(i.e.: the machine name for each service type in operation) on start
-up. Also, as stated above, the exact method by which this name registration
-takes place is determined by whether or not the MS Windows client/server
-has been given a WINS server address, whether or not LMHOSTS lookup
-is enabled, or if DNS for NetBIOS name resolution is enabled, etc.</P
-><P
->In the case where there is no WINS server all name registrations as
-well as name lookups are done by UDP broadcast. This isolates name
-resolution to the local subnet, unless LMHOSTS is used to list all
-names and IP addresses. In such situations Samba provides a means by
-which the samba server name may be forcibly injected into the browse
-list of a remote MS Windows network (using the
-<B
-CLASS="COMMAND"
->remote announce</B
-> parameter).</P
-><P
->Where a WINS server is used, the MS Windows client will use UDP
-unicast to register with the WINS server. Such packets can be routed
-and thus WINS allows name resolution to function across routed networks.</P
-><P
->During the startup process an election will take place to create a
-local master browser if one does not already exist. On each NetBIOS network
-one machine will be elected to function as the domain master browser. This
-domain browsing has nothing to do with MS security domain control.
-Instead, the domain master browser serves the role of contacting each local
-master browser (found by asking WINS or from LMHOSTS) and exchanging browse
-list contents. This way every master browser will eventually obtain a complete
-list of all machines that are on the network. Every 11-15 minutes an election
-is held to determine which machine will be the master browser. By the nature of
-the election criteria used, the machine with the highest uptime, or the
-most senior protocol version, or other criteria, will win the election
-as domain master browser.</P
-><P
->Clients wishing to browse the network make use of this list, but also depend
-on the availability of correct name resolution to the respective IP
-address/addresses. </P
-><P
->Any configuration that breaks name resolution and/or browsing intrinsics
-will annoy users because they will have to put up with protracted
-inability to use the network services.</P
+NAME="AEN385">3.2. Use of the "Remote Announce" parameter</H1
><P
->Samba supports a feature that allows forced synchonisation
-of browse lists across routed networks using the <B
-CLASS="COMMAND"
->remote
-browse sync</B
-> parameter in the <TT
-CLASS="FILENAME"
->smb.conf</TT
-> file.
-This causes Samba to contact the local master browser on a remote network and
-to request browse list synchronisation. This effectively bridges
-two networks that are separated by routers. The two remote
-networks may use either broadcast based name resolution or WINS
-based name resolution, but it should be noted that the <B
-CLASS="COMMAND"
->remote
-browse sync</B
-> parameter provides browse list synchronisation - and
-that is distinct from name to address resolution, in other
-words, for cross subnet browsing to function correctly it is
-essential that a name to address resolution mechanism be provided.
-This mechanism could be via DNS, <TT
-CLASS="FILENAME"
->/etc/hosts</TT
->,
-and so on.</P
-></DIV
-><DIV
-CLASS="SECT1"
-><H1
-CLASS="SECT1"
-><A
-NAME="AEN340"
->3.3. Use of the <B
-CLASS="COMMAND"
->Remote Announce</B
-> parameter</A
-></H1
-><P
->The <B
-CLASS="COMMAND"
->remote announce</B
-> parameter of
-<TT
-CLASS="FILENAME"
->smb.conf</TT
-> can be used to forcibly ensure
+>The "remote announce" parameter of smb.conf can be used to forcibly ensure
that all the NetBIOS names on a network get announced to a remote network.
-The syntax of the <B
-CLASS="COMMAND"
->remote announce</B
-> parameter is:
+The syntax of the "remote announce" parameter is:
<PRE
CLASS="PROGRAMLISTING"
-> remote announce = <VAR
-CLASS="REPLACEABLE"
->a.b.c.d [e.f.g.h]</VAR
-> ...</PRE
+> remote announce = a.b.c.d [e.f.g.h] ...</PRE
>
_or_
<PRE
CLASS="PROGRAMLISTING"
-> remote announce = <VAR
-CLASS="REPLACEABLE"
->a.b.c.d/WORKGROUP [e.f.g.h/WORKGROUP]</VAR
-> ...</PRE
+> remote announce = a.b.c.d/WORKGROUP [e.f.g.h/WORKGROUP] ...</PRE
>
where:
@@ -392,14 +151,7 @@ where:
CLASS="VARIABLELIST"
><DL
><DT
-><VAR
-CLASS="REPLACEABLE"
->a.b.c.d</VAR
-> and
-<VAR
-CLASS="REPLACEABLE"
->e.f.g.h</VAR
-></DT
+>a.b.c.d and e.f.g.h</DT
><DD
><P
>is either the LMB (Local Master Browser) IP address
@@ -414,10 +166,7 @@ undesirable but may be necessary if we do NOT know
the IP address of the remote LMB.</P
></DD
><DT
-><VAR
-CLASS="REPLACEABLE"
->WORKGROUP</VAR
-></DT
+>WORKGROUP</DT
><DD
><P
>is optional and can be either our own workgroup
@@ -436,51 +185,27 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="AEN363"
->3.4. Use of the <B
-CLASS="COMMAND"
->Remote Browse Sync</B
-> parameter</A
-></H1
+NAME="AEN399">3.3. Use of the "Remote Browse Sync" parameter</H1
><P
->The <B
-CLASS="COMMAND"
->remote browse sync</B
-> parameter of
-<TT
-CLASS="FILENAME"
->smb.conf</TT
-> is used to announce to
+>The "remote browse sync" parameter of smb.conf is used to announce to
another LMB that it must synchronise it's NetBIOS name list with our
Samba LMB. It works ONLY if the Samba server that has this option is
simultaneously the LMB on it's network segment.</P
><P
->The syntax of the <B
-CLASS="COMMAND"
->remote browse sync</B
-> parameter is:
-
+>The syntax of the "remote browse sync" parameter is:
<PRE
CLASS="PROGRAMLISTING"
->remote browse sync = <VAR
-CLASS="REPLACEABLE"
->a.b.c.d</VAR
-></PRE
+> remote browse sync = a.b.c.d</PRE
>
-where <VAR
-CLASS="REPLACEABLE"
->a.b.c.d</VAR
-> is either the IP address of the remote LMB or else is the network broadcast address of the remote segment.</P
+where a.b.c.d is either the IP address of the remote LMB or else is the network broadcast address of the remote segment.</P
></DIV
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="AEN374"
->3.5. Use of WINS</A
-></H1
+NAME="AEN404">3.4. Use of WINS</H1
><P
>Use of WINS (either Samba WINS _or_ MS Windows NT Server WINS) is highly
recommended. Every NetBIOS machine registers it's name together with a
@@ -502,11 +227,7 @@ of all names that have registered the NetLogon service name_type. This saves
broadcast traffic and greatly expedites logon processing. Since broadcast
name resolution can not be used across network segments this type of
information can only be provided via WINS _or_ via statically configured
-<TT
-CLASS="FILENAME"
->lmhosts</TT
-> files that must reside on all clients in the
-absence of WINS.</P
+"lmhosts" files that must reside on all clients in the absence of WINS.</P
><P
>WINS also serves the purpose of forcing browse list synchronisation by all
LMB's. LMB's must synchronise their browse list with the DMB (domain master
@@ -524,106 +245,32 @@ machines that have not registered with a WINS server will fail name to address
lookup attempts by other clients and will therefore cause workstation access
errors.</P
><P
->To configure Samba as a WINS server just add
-<B
-CLASS="COMMAND"
->wins support = yes</B
-> to the <TT
-CLASS="FILENAME"
->smb.conf</TT
->
-file [globals] section.</P
+>To configure Samba as a WINS server just add "wins support = yes" to the
+smb.conf file [globals] section.</P
><P
>To configure Samba to register with a WINS server just add
"wins server = a.b.c.d" to your smb.conf file [globals] section.</P
-><DIV
-CLASS="IMPORTANT"
-><P
-></P
-><TABLE
-CLASS="IMPORTANT"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/important.gif"
-HSPACE="5"
-ALT="Important"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->Never use both <B
-CLASS="COMMAND"
->wins support = yes</B
-> together
-with <B
-CLASS="COMMAND"
->wins server = a.b.c.d</B
->
-particularly not using it's own IP address.
-Specifying both will cause <SPAN
-CLASS="APPLICATION"
->nmbd</SPAN
-> to refuse to start!</P
-></TD
-></TR
-></TABLE
-></DIV
-><DIV
-CLASS="SECT2"
-><H2
-CLASS="SECT2"
-><A
-NAME="AEN391"
->3.5.1. WINS Replication</A
-></H2
><P
->Samba-3 permits WINS replication through the use of the <TT
-CLASS="FILENAME"
->wrepld</TT
-> utility.
-This tool is not currently capable of being used as it is still in active development.
-As soon as this tool becomes moderately functional we will prepare man pages and enhance this
-section of the documentation to provide usage and technical details.</P
-></DIV
-><DIV
-CLASS="SECT2"
-><H2
-CLASS="SECT2"
-><A
-NAME="AEN395"
->3.5.2. Static WINS Entries</A
-></H2
-><P
->New to Samba-3 is a tool called <TT
-CLASS="FILENAME"
->winsedit</TT
-> that may be used to add
-static WINS entries to the WINS database. This tool can be used also to modify entries
-existing in the WINS database.</P
-><P
->The development of the winsedit tool was made necessary due to the migration
-of the older style wins.dat file into a new tdb binary backend data store.</P
-></DIV
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>DO NOT EVER</I
+></SPAN
+> use both "wins support = yes" together with "wins server = a.b.c.d"
+particularly not using it's own IP address.</P
></DIV
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="AEN400"
->3.6. Do NOT use more than one (1) protocol on MS Windows machines</A
-></H1
+NAME="AEN415">3.5. Do NOT use more than one (1) protocol on MS Windows machines</H1
><P
>A very common cause of browsing problems results from installing more than
one protocol on an MS Windows machine.</P
><P
->Every NetBIOS machine takes part in a process of electing the LMB (and DMB)
+>Every NetBIOS machine take part in a process of electing the LMB (and DMB)
every 15 minutes. A set of election criteria is used to determine the order
of precidence for winning this election process. A machine running Samba or
Windows NT will be biased so that the most suitable machine will predictably
@@ -639,19 +286,6 @@ interface over the IPX protocol. Samba will then lose the LMB role as Windows
as an LMB and thus browse list operation on all TCP/IP only machines will
fail.</P
><P
-><SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->Windows 95, 98, 98se, Me are referred to generically as Windows 9x.
-The Windows NT4, 2000, XP and 2003 use common protocols. These are roughly
-referred to as the WinNT family, but it should be recognised that 2000 and
-XP/2003 introduce new protocol extensions that cause them to behave
-differently from MS Windows NT4. Generally, where a server does NOT support
-the newer or extended protocol, these will fall back to the NT4 protocols.</I
-></SPAN
-></P
-><P
>The safest rule of all to follow it this - USE ONLY ONE PROTOCOL!</P
></DIV
><DIV
@@ -659,14 +293,12 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="AEN408"
->3.7. Name Resolution Order</A
-></H1
+NAME="AEN421">3.6. Name Resolution Order</H1
><P
>Resolution of NetBIOS names to IP addresses can take place using a number
of methods. The only ones that can provide NetBIOS name_type information
-are:</P
-><P
+are:
+<P
></P
><TABLE
BORDER="0"
@@ -687,9 +319,10 @@ BORDER="0"
></TABLE
><P
></P
+></P
><P
->Alternative means of name resolution includes:</P
-><P
+>Alternative means of name resolution includes:
+<P
></P
><TABLE
BORDER="0"
@@ -706,23 +339,24 @@ BORDER="0"
></TABLE
><P
></P
+></P
><P
>Many sites want to restrict DNS lookups and want to avoid broadcast name
resolution traffic. The "name resolve order" parameter is of great help here.
The syntax of the "name resolve order" parameter is:
<PRE
CLASS="PROGRAMLISTING"
->name resolve order = wins lmhosts bcast host</PRE
+> name resolve order = wins lmhosts bcast host</PRE
>
_or_
<PRE
CLASS="PROGRAMLISTING"
->name resolve order = wins lmhosts (eliminates bcast and host)</PRE
+> name resolve order = wins lmhosts (eliminates bcast and host)</PRE
>
The default is:
<PRE
CLASS="PROGRAMLISTING"
->name resolve order = host lmhost wins bcast</PRE
+> name resolve order = host lmhost wins bcast</PRE
>.
where "host" refers the the native methods used by the Unix system
to implement the gethostbyname() function call. This is normally
@@ -754,7 +388,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
-HREF="install.html"
+HREF="improved-browsing.html"
ACCESSKEY="P"
>Prev</A
></TD
@@ -772,7 +406,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
-HREF="passdb.html"
+HREF="pwencrypt.html"
ACCESSKEY="N"
>Next</A
></TD
@@ -782,7 +416,7 @@ ACCESSKEY="N"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
->How to Install and Test SAMBA</TD
+>Improved browsing in samba</TD
><TD
WIDTH="34%"
ALIGN="center"
@@ -796,7 +430,7 @@ ACCESSKEY="U"
WIDTH="33%"
ALIGN="right"
VALIGN="top"
->User information database</TD
+>LanMan and NT Password Encryption in Samba</TD
></TR
></TABLE
></DIV
diff --git a/docs/htmldocs/bugreport.html b/docs/htmldocs/bugreport.html
index b46173f559..fcc4b7e91a 100644
--- a/docs/htmldocs/bugreport.html
+++ b/docs/htmldocs/bugreport.html
@@ -1,113 +1,352 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter29.Reporting Bugs</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"><link rel="home" href="index.html" title="SAMBA Project Documentation"><link rel="up" href="troubleshooting.html" title="PartIV.Troubleshooting"><link rel="previous" href="problems.html" title="Chapter28.Analysing and solving samba problems"><link rel="next" href="Appendixes.html" title="PartV.Appendixes"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter29.Reporting Bugs</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="problems.html">Prev</a></td><th width="60%" align="center">PartIV.Troubleshooting</th><td width="20%" align="right"><a accesskey="n" href="Appendixes.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="bugreport"></a>Chapter29.Reporting Bugs</h2></div><div><div class="author"><h3 class="author">Jelmer R. Vernooij</h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt>&lt;<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author"></h3><div class="affiliation"><span class="orgname">Samba Team<br></span></div></div></div><div><p class="pubdate"> 27 June 1997 </p></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="bugreport.html#id2903912">Introduction</a></dt><dt><a href="bugreport.html#id2903826">General info</a></dt><dt><a href="bugreport.html#id2904609">Debug levels</a></dt><dt><a href="bugreport.html#id2904745">Internal errors</a></dt><dt><a href="bugreport.html#id2904838">Attaching to a running process</a></dt><dt><a href="bugreport.html#id2904885">Patches</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2903912"></a>Introduction</h2></div></div><p>Please report bugs using <a href="https://bugzilla.samba.org/" target="_top">bugzilla</a>.</p><p>
-Please take the time to read this file before you submit a bug
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<HTML
+><HEAD
+><TITLE
+>Reporting Bugs</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
+REL="HOME"
+TITLE="SAMBA Project Documentation"
+HREF="samba-howto-collection.html"><LINK
+REL="UP"
+TITLE="Appendixes"
+HREF="appendixes.html"><LINK
+REL="PREVIOUS"
+TITLE="Samba and other CIFS clients"
+HREF="other-clients.html"><LINK
+REL="NEXT"
+TITLE="Diagnosing your samba server"
+HREF="diagnosis.html"></HEAD
+><BODY
+CLASS="CHAPTER"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><TABLE
+SUMMARY="Header navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>SAMBA Project Documentation</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="other-clients.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+></TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="diagnosis.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="CHAPTER"
+><H1
+><A
+NAME="BUGREPORT">Chapter 25. Reporting Bugs</H1
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN3309">25.1. Introduction</H1
+><P
+>The email address for bug reports for stable releases is <A
+HREF="samba@samba.org"
+TARGET="_top"
+>samba@samba.org</A
+>.
+Bug reports for alpha releases should go to <A
+HREF="mailto:samba-technical@samba.org"
+TARGET="_top"
+>samba-technical@samba.org</A
+>.</P
+><P
+>Please take the time to read this file before you submit a bug
report. Also, please see if it has changed between releases, as we
-may be changing the bug reporting mechanism at some time.
-</p><p>
-Please also do as much as you can yourself to help track down the
+may be changing the bug reporting mechanism at some time.</P
+><P
+>Please also do as much as you can yourself to help track down the
bug. Samba is maintained by a dedicated group of people who volunteer
their time, skills and efforts. We receive far more mail about it than
we can possibly answer, so you have a much higher chance of an answer
-and a fix if you send us a &quot;developer friendly&quot; bug report that lets
-us fix it fast.
-</p><p>
-Do not assume that if you post the bug to the comp.protocols.smb
+and a fix if you send us a "developer friendly" bug report that lets
+us fix it fast. </P
+><P
+>Do not assume that if you post the bug to the comp.protocols.smb
newsgroup or the mailing list that we will read it. If you suspect that your
problem is not a bug but a configuration problem then it is better to send
it to the Samba mailing list, as there are (at last count) 5000 other users on
-that list that may be able to help you.
-</p><p>
-You may also like to look though the recent mailing list archives,
+that list that may be able to help you.</P
+><P
+>You may also like to look though the recent mailing list archives,
which are conveniently accessible on the Samba web pages
-at <a href="http://samba.org/samba/" target="_top">http://samba.org/samba/</a>.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2903826"></a>General info</h2></div></div><p>
-Before submitting a bug report check your config for silly
+at <A
+HREF="http://samba.org/samba/"
+TARGET="_top"
+>http://samba.org/samba/</A
+>.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN3319">25.2. General info</H1
+><P
+>Before submitting a bug report check your config for silly
errors. Look in your log files for obvious messages that tell you that
you've misconfigured something and run testparm to test your config
-file for correct syntax.
-</p><p>
-Have you run through the <a href="diagnosis.html" title="Chapter27.The samba checklist">diagnosis</a>?
-This is very important.
-</p><p>
-If you include part of a log file with your bug report then be sure to
+file for correct syntax.</P
+><P
+>Have you run through the <A
+HREF="Diagnosis.html"
+TARGET="_top"
+>diagnosis</A
+>?
+This is very important.</P
+><P
+>If you include part of a log file with your bug report then be sure to
annotate it with exactly what you were doing on the client at the
-time, and exactly what the results were.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2904609"></a>Debug levels</h2></div></div><p>
-If the bug has anything to do with Samba behaving incorrectly as a
+time, and exactly what the results were.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN3325">25.3. Debug levels</H1
+><P
+>If the bug has anything to do with Samba behaving incorrectly as a
server (like refusing to open a file) then the log files will probably
be very useful. Depending on the problem a log level of between 3 and
10 showing the problem may be appropriate. A higher level givesmore
-detail, but may use too much disk space.
-</p><p>
-To set the debug level use <b>log level =</b> in your
-<tt>smb.conf</tt>. You may also find it useful to set the log
+detail, but may use too much disk space.</P
+><P
+>To set the debug level use <B
+CLASS="COMMAND"
+>log level =</B
+> in your
+<TT
+CLASS="FILENAME"
+>smb.conf</TT
+>. You may also find it useful to set the log
level higher for just one machine and keep separate logs for each machine.
-To do this use:
-</p><pre class="programlisting">
-log level = 10
+To do this use:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>log level = 10
log file = /usr/local/samba/lib/log.%m
-include = /usr/local/samba/lib/smb.conf.%m
-</pre><p>
-then create a file
-<tt>/usr/local/samba/lib/smb.conf.<i><tt>machine</tt></i></tt> where
-<i><tt>machine</tt></i> is the name of the client you wish to debug. In that file
-put any <tt>smb.conf</tt> commands you want, for example
-<b>log level=</b> may be useful. This also allows you to
+include = /usr/local/samba/lib/smb.conf.%m</PRE
+></P
+><P
+>then create a file
+<TT
+CLASS="FILENAME"
+>/usr/local/samba/lib/smb.conf.machine</TT
+> where
+"machine" is the name of the client you wish to debug. In that file
+put any smb.conf commands you want, for example
+<B
+CLASS="COMMAND"
+>log level=</B
+> may be useful. This also allows you to
experiment with different security systems, protocol levels etc on just
-one machine.
-</p><p>
-The <tt>smb.conf</tt> entry <b>log level =</b>
-is synonymous with the entry <b>debuglevel =</b> that has been
+one machine.</P
+><P
+>The <TT
+CLASS="FILENAME"
+>smb.conf</TT
+> entry <B
+CLASS="COMMAND"
+>log level =</B
+>
+is synonymous with the entry <B
+CLASS="COMMAND"
+>debuglevel =</B
+> that has been
used in older versions of Samba and is being retained for backwards
-compatibility of <tt>smb.conf</tt> files.
-</p><p>
-As the <b>log level =</b> value is increased you will record
+compatibility of smb.conf files.</P
+><P
+>As the <B
+CLASS="COMMAND"
+>log level =</B
+> value is increased you will record
a significantly increasing level of debugging information. For most
debugging operations you may not need a setting higher than 3. Nearly
all bugs can be tracked at a setting of 10, but be prepared for a VERY
-large volume of log data.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2904745"></a>Internal errors</h2></div></div><p>
-If you get a &quot;INTERNAL ERROR&quot; message in your log files it means that
+large volume of log data.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN3342">25.4. Internal errors</H1
+><P
+>If you get a "INTERNAL ERROR" message in your log files it means that
Samba got an unexpected signal while running. It is probably a
segmentation fault and almost certainly means a bug in Samba (unless
-you have faulty hardware or system software).
-</p><p>
-If the message came from smbd then it will probably be accompanied by
+you have faulty hardware or system software)</P
+><P
+>If the message came from smbd then it will probably be accompanied by
a message which details the last SMB message received by smbd. This
info is often very useful in tracking down the problem so please
-include it in your bug report.
-</p><p>
-You should also detail how to reproduce the problem, if
-possible. Please make this reasonably detailed.
-</p><p>
-You may also find that a core file appeared in a <tt>corefiles</tt>
+include it in your bug report.</P
+><P
+>You should also detail how to reproduce the problem, if
+possible. Please make this reasonably detailed.</P
+><P
+>You may also find that a core file appeared in a "corefiles"
subdirectory of the directory where you keep your samba log
files. This file is the most useful tool for tracking down the bug. To
-use it you do this:
-</p><p><b>gdb smbd core</b></p><p>
-adding appropriate paths to smbd and core so gdb can find them. If you
-don't have gdb then try <b><tt>dbx</tt></b>. Then within the debugger use the
-command <b><tt>where</tt></b> to give a stack trace of where the problem
-occurred. Include this in your mail.
-</p><p>
-If you know any assembly language then do a <b><tt>disass</tt></b> of the routine
+use it you do this:</P
+><P
+><B
+CLASS="COMMAND"
+>gdb smbd core</B
+></P
+><P
+>adding appropriate paths to smbd and core so gdb can find them. If you
+don't have gdb then try "dbx". Then within the debugger use the
+command "where" to give a stack trace of where the problem
+occurred. Include this in your mail.</P
+><P
+>If you known any assembly language then do a "disass" of the routine
where the problem occurred (if its in a library routine then
disassemble the routine that called it) and try to work out exactly
where the problem is by looking at the surrounding code. Even if you
don't know assembly then incuding this info in the bug report can be
-useful.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2904838"></a>Attaching to a running process</h2></div></div><p>
-Unfortunately some unixes (in particular some recent linux kernels)
+useful. </P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN3352">25.5. Attaching to a running process</H1
+><P
+>Unfortunately some unixes (in particular some recent linux kernels)
refuse to dump a core file if the task has changed uid (which smbd
does often). To debug with this sort of system you could try to attach
-to the running process using <b><tt>gdb smbd <i><tt>PID</tt></i></tt></b> where you get <i><tt>PID</tt></i> from
-smbstatus. Then use <b><tt>c</tt></b> to continue and try to cause the core dump
+to the running process using "gdb smbd PID" where you get PID from
+smbstatus. Then use "c" to continue and try to cause the core dump
using the client. The debugger should catch the fault and tell you
-where it occurred.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2904885"></a>Patches</h2></div></div><p>
-The best sort of bug report is one that includes a fix! If you send us
-patches please use <b><tt>diff -u</tt></b> format if your version of
-diff supports it, otherwise use <b><tt>diff -c4</tt></b>. Make sure
-you do the diff against a clean version of the source and let me know
-exactly what version you used.
-</p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="problems.html">Prev</a></td><td width="20%" align="center"><a accesskey="u" href="troubleshooting.html">Up</a></td><td width="40%" align="right"><a accesskey="n" href="Appendixes.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter28.Analysing and solving samba problems</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">PartV.Appendixes</td></tr></table></div></body></html>
+where it occurred.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN3355">25.6. Patches</H1
+><P
+>The best sort of bug report is one that includes a fix! If you send us
+patches please use <B
+CLASS="COMMAND"
+>diff -u</B
+> format if your version of
+diff supports it, otherwise use <B
+CLASS="COMMAND"
+>diff -c4</B
+>. Make sure
+your do the diff against a clean version of the source and let me know
+exactly what version you used. </P
+></DIV
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+SUMMARY="Footer navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="other-clients.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="samba-howto-collection.html"
+ACCESSKEY="H"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="diagnosis.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>Samba and other CIFS clients</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="appendixes.html"
+ACCESSKEY="U"
+>Up</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>Diagnosing your samba server</TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+> \ No newline at end of file
diff --git a/docs/htmldocs/cups-printing.html b/docs/htmldocs/cups-printing.html
deleted file mode 100644
index 8dd4a94f4f..0000000000
--- a/docs/htmldocs/cups-printing.html
+++ /dev/null
@@ -1,2773 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<HTML
-><HEAD
-><TITLE
->CUPS Printing Support</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
-REL="HOME"
-TITLE="SAMBA Project Documentation"
-HREF="samba-howto-collection.html"><LINK
-REL="UP"
-TITLE="Advanced Configuration"
-HREF="optional.html"><LINK
-REL="PREVIOUS"
-TITLE="Printing Support"
-HREF="printing.html"><LINK
-REL="NEXT"
-TITLE="Unified Logons between Windows NT and UNIX using Winbind"
-HREF="winbind.html"></HEAD
-><BODY
-CLASS="CHAPTER"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->SAMBA Project Documentation</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="printing.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
-></TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="winbind.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="CHAPTER"
-><H1
-><A
-NAME="CUPS-PRINTING"
-></A
->Chapter 14. CUPS Printing Support</H1
-><DIV
-CLASS="TOC"
-><DL
-><DT
-><B
->Table of Contents</B
-></DT
-><DT
->14.1. <A
-HREF="cups-printing.html#AEN2034"
->Introduction</A
-></DT
-><DT
->14.2. <A
-HREF="cups-printing.html#AEN2041"
->Configuring <TT
-CLASS="FILENAME"
->smb.conf</TT
-> for CUPS</A
-></DT
-><DT
->14.3. <A
-HREF="cups-printing.html#AEN2061"
->CUPS - RAW Print Through Mode</A
-></DT
-><DT
->14.4. <A
-HREF="cups-printing.html#AEN2118"
->CUPS as a network PostScript RIP -- CUPS drivers working on server, Adobe
-PostScript driver with CUPS-PPDs downloaded to clients</A
-></DT
-><DT
->14.5. <A
-HREF="cups-printing.html#AEN2139"
->Windows Terminal Servers (WTS) as CUPS clients</A
-></DT
-><DT
->14.6. <A
-HREF="cups-printing.html#AEN2143"
->Setting up CUPS for driver download</A
-></DT
-><DT
->14.7. <A
-HREF="cups-printing.html#AEN2156"
->Sources of CUPS drivers / PPDs</A
-></DT
-><DT
->14.8. <A
-HREF="cups-printing.html#AEN2212"
->The CUPS Filter Chains</A
-></DT
-><DT
->14.9. <A
-HREF="cups-printing.html#AEN2251"
->CUPS Print Drivers and Devices</A
-></DT
-><DT
->14.10. <A
-HREF="cups-printing.html#AEN2328"
->Limiting the number of pages users can print</A
-></DT
-><DT
->14.11. <A
-HREF="cups-printing.html#AEN2424"
->Advanced Postscript Printing from MS Windows</A
-></DT
-><DT
->14.12. <A
-HREF="cups-printing.html#AEN2439"
->Auto-Deletion of CUPS spool files</A
-></DT
-></DL
-></DIV
-><DIV
-CLASS="SECT1"
-><H1
-CLASS="SECT1"
-><A
-NAME="AEN2034"
->14.1. Introduction</A
-></H1
-><P
->The Common Unix Print System (CUPS) has become very popular, but to many it is
-a very mystical tool. There is a great deal of uncertainty regarding CUPS and how
-it works. The result is seen in a large number of posting on the samba mailing lists
-expressing frustration when MS Windows printers appear not to work with a CUPS
-backr-end.</P
-><P
->This is a good time to point out how CUPS can be used and what it does. CUPS is more
-than just a print spooling system - it is a complete printer management system that
-complies with HTTP and IPP protocols. It can be managed remotely via a web browser
-and it can print using http and ipp protocols.</P
-><P
->CUPS allows to creation of RAW printers (ie: NO file format translation) as well as
-SMART printers (ie: CUPS does file format conversion as required for the printer). In
-many ways this gives CUPS similar capabilities to the MS Windows print monitoring
-system. Of course, if you are a CUPS advocate, you would agrue that CUPS is better!
-In any case, let us now move on to explore how one may configure CUPS for interfacing
-with MS Windows print clients via Samba.</P
-><P
-><A
-HREF="http://www.cups.org/"
-TARGET="_top"
->CUPS</A
-> is a newcomer in the UNIX printing scene,
-which has convinced many people upon first trial already. However, it has quite a few
-new features, which make it different from other, more traditional printing systems.</P
-></DIV
-><DIV
-CLASS="SECT1"
-><H1
-CLASS="SECT1"
-><A
-NAME="AEN2041"
->14.2. Configuring <TT
-CLASS="FILENAME"
->smb.conf</TT
-> for CUPS</A
-></H1
-><P
->Printing with CUPS in the most basic <TT
-CLASS="FILENAME"
->smb.conf</TT
->
-setup in Samba-3 only needs two settings: <B
-CLASS="COMMAND"
->printing = cups</B
-> and
-<B
-CLASS="COMMAND"
->printcap = cups</B
->. While CUPS itself doesn't need a printcap
-anymore, the <TT
-CLASS="FILENAME"
->cupsd.conf</TT
-> configuration file knows two directives
-(example: <B
-CLASS="COMMAND"
->Printcap /etc/printcap</B
-> and <B
-CLASS="COMMAND"
->PrintcapFormat
-BSD</B
->), which control if such a file should be created for the
-convenience of third party applications. Make sure it is set! For details see
-<B
-CLASS="COMMAND"
->man cupsd.conf</B
-> and other CUPS-related documentation.</P
-><P
->If SAMBA is compiled against libcups, then <B
-CLASS="COMMAND"
->printcap = cups</B
-> uses the
-CUPS API to list printers, submit jobs, etc. Otherwise it maps to the System V commands
-with an additional <VAR
-CLASS="PARAMETER"
->-oraw</VAR
-> option for printing. On a Linux system,
-you can use the <B
-CLASS="COMMAND"
->ldd</B
-> command to find out details (ldd may not be
-present on other OS platforms, or its function may be embodied by a different command):</P
-><P
-><PRE
-CLASS="PROGRAMLISTING"
->transmeta:/home/kurt # ldd `which smbd`
- libssl.so.0.9.6 =&#62; /usr/lib/libssl.so.0.9.6 (0x4002d000)
- libcrypto.so.0.9.6 =&#62; /usr/lib/libcrypto.so.0.9.6 (0x4005a000)
- libcups.so.2 =&#62; /usr/lib/libcups.so.2 (0x40123000)
- libdl.so.2 =&#62; /lib/libdl.so.2 (0x401e8000)
- libnsl.so.1 =&#62; /lib/libnsl.so.1 (0x401ec000)
- libpam.so.0 =&#62; /lib/libpam.so.0 (0x40202000)
- libc.so.6 =&#62; /lib/libc.so.6 (0x4020b000)
- /lib/ld-linux.so.2 =&#62; /lib/ld-linux.so.2 (0x40000000)</PRE
-></P
-><P
->The line "libcups.so.2 =&#62; /usr/lib/libcups.so.2
-(0x40123000)" shows there is CUPS support compiled into this version of
-Samba. If this is the case, and <B
-CLASS="COMMAND"
->printing = cups</B
-> is set, then any
-otherwise manually set print command in <TT
-CLASS="FILENAME"
->smb.conf</TT
-> is ignored.</P
-></DIV
-><DIV
-CLASS="SECT1"
-><H1
-CLASS="SECT1"
-><A
-NAME="AEN2061"
->14.3. CUPS - RAW Print Through Mode</A
-></H1
-><DIV
-CLASS="NOTE"
-><P
-></P
-><TABLE
-CLASS="NOTE"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->When used in raw print through mode is will be necessary to use the printer
-vendor's drivers in each Windows client PC.</P
-></TD
-></TR
-></TABLE
-></DIV
-><P
->When CUPS printers are configured for RAW print-through mode operation it is the
-responsibility of the Samba client to fully render the print job (file) in a format
-that is suitable for direct delivery to the printer. In this case CUPS will NOT
-do any print file format conversion work.</P
-><P
->The CUPS files that need to be correctly set for RAW mode printers to work are:
-
-<P
-></P
-><UL
-><LI
-><P
-><TT
-CLASS="FILENAME"
->/etc/cups/mime.types</TT
-></P
-></LI
-><LI
-><P
-><TT
-CLASS="FILENAME"
->/etc/cups/mime.convs</TT
-></P
-></LI
-></UL
->
-
-Both contain entries that must be uncommented to allow <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->RAW</I
-></SPAN
-> mode
-operation.</P
-><P
->Firstly, to enable CUPS based printing from Samba the following options must be
-enabled in your <TT
-CLASS="FILENAME"
->smb.conf</TT
-> file [globals] section:
-
-<P
-></P
-><UL
-><LI
-><P
->printing = CUPS</P
-></LI
-><LI
-><P
->printcap = CUPS</P
-></LI
-></UL
->
-
-When these parameters are specified the print directives in <TT
-CLASS="FILENAME"
->smb.conf</TT
-> (as well as in
-samba itself) will be ignored because samba will directly interface with CUPS through
-it's application program interface (API) - so long as Samba has been compiled with
-CUPS library (libcups) support. If samba has NOT been compiled with CUPS support then
-printing will use the System V AT&#38;T command set with the <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->-oraw</I
-></SPAN
->
-option automatically passing through.</P
-><P
->Cupsomatic (an enhanced printing utility that is part of some CUPS implementations)
-on the Samba/CUPS server does *not* add any features if a file is really
-printed "raw". However, if you have loaded the driver for the Windows client from
-the CUPS server, using the "cupsaddsmb" utility, and if this driver is one using
-a "Foomatic" PPD, the PJL header in question is already added on the Windows client,
-at the time when the driver initially generated the PostScript data and CUPS in true
-"-oraw" manner doesn't remove this PJL header and passes the file "as is" to its
-printer communication backend.</P
-><DIV
-CLASS="NOTE"
-><P
-></P
-><TABLE
-CLASS="NOTE"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->NOTE: editing in the "mime.convs" and the "mime.types" file does not *enforce*
-"raw" printing, it only *allows* it.</P
-></TD
-></TR
-></TABLE
-></DIV
-><P
->Print files that arrive from MS Windows printing are "auto-typed" by CUPS. This aids
-the process of determining proper treatment while in the print queue system.
-
-<P
-></P
-><UL
-><LI
-><P
-> Files generated by PCL drivers and directed at PCK printers get auto-typed as
- <TT
-CLASS="FILENAME"
->application/octet-stream</TT
->. Unknown file format types also
- get auto-typed with this tag.
- </P
-></LI
-><LI
-><P
-> Files generated by a Postscript driver and directed at a Postscript printer
- are auto-typed depending on the auto-detected most suitable MIME type as:
-
- <P
-></P
-><UL
-><LI
-><P
->* application/postscript</P
-></LI
-><LI
-><P
->* application/vnd.cups-postscript</P
-></LI
-></UL
->
- </P
-></LI
-></UL
-></P
-><P
->"application/postscript" first goes thru the "pstops" filter (where the page counting
-and accounting takes place). The outcome will be of MIME type
-"application/vnd.cups-postscript". The pstopsfilter reads and uses information from
-the PPD and inserts user-provided options into the PostScript file. As a consequence,
-the filtered file could possibly have an unwanted PJL header.</P
-><P
->"application/postscript" will be all files with a ".ps", ".ai", ".eps" suffix or which
-have as their first character string one of "%!" or "&#62;04&#60;%".</P
-><P
->"application/vnd.cups-postscript" will files which contain the string
-"LANGUAGE=POSTSCRIPT" (or similar variations with different capitalization) in the
-first 512 bytes, and also contain the "PJL super escape code" in the first 128 bytes
-("&#62;1B&#60;%-12345X"). Very likely, most PostScript files generated on Windows using a CUPS
-or other PPD, will have to be auto-typed as "vnd.cups-postscript". A file produced
-with a "Generic PostScript driver" will just be tagged "application/postscript".</P
-><P
->Once the file is in "application/vnd.cups-postscript" format, either "pstoraster"
-or "cupsomatic" will take over (depending on the printer configuration, as
-determined by the PPD in use).</P
-><DIV
-CLASS="NOTE"
-><P
-></P
-><TABLE
-CLASS="NOTE"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->A printer queue with *no* PPD associated to it is a "raw" printer and all files
-will go directly there as received by the spooler. The exeptions are file types
-"application/octet-stream" which need "passthrough feature" enabled.
-"Raw" queues don't do any filtering at all, they hand the file directly to the
-CUPS backend. This backend is responsible for the sending of the data to the device
-(as in the "device URI" notation as lpd://, socket://, smb://, ipp://, http://,
-parallel:/, serial:/, usb:/ etc.)</P
-></TD
-></TR
-></TABLE
-></DIV
-><DIV
-CLASS="NOTE"
-><P
-></P
-><TABLE
-CLASS="NOTE"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->"cupsomatic"/Foomatic are *not* native CUPS drivers and they don't ship with CUPS.
-They are a Third Party add-on, developed at Linuxprinting.org. As such, they are
-a brilliant hack to make all models (driven by Ghostscript drivers/filters in
-traditional spoolers) also work via CUPS, with the same (good or bad!) quality
-as in these other spoolers. "cupsomatic" is only a vehicle to execute a ghostscript
-commandline at that stage in the CUPS filtering chain, where "normally" the native
-CUPS "pstoraster" filter would kick in. cupsomatic by-passes pstoraster, "kidnaps"
-the printfile from CUPS away and re-directs it to go through Ghostscipt. CUPS accepts this,
-because the associated CUPS-O-Matic-/Foomatic-PPD specifies:</P
-><PRE
-CLASS="PROGRAMLISTING"
-> *cupsFilter: "application/vnd.cups-postscript 0 cupsomatic"</PRE
-><P
->This line persuades CUPS to hand the file to cupsomatic, once it has successfully
-converted it to the MIME type "application/vnd.cups-postscript". This conversion will not
-happen for Jobs arriving from Windows which are auto-typed "application/octet-stream",
-with the according changes in "/etc/cups/mime.types" in place.</P
-></TD
-></TR
-></TABLE
-></DIV
-><P
->CUPS is widely configurable and flexible, even regarding its filtering mechanism.
-Another workaround in some situations would be to have
-in "/etc/cups/mime.types" entries as follows:</P
-><PRE
-CLASS="PROGRAMLISTING"
-> application/postscript application/vnd.cups-raw 0 -
- application/vnd.cups-postscript application/vnd.cups-raw 0 -</PRE
-><P
->This would prevent all Postscript files from being filtered (rather, they will go
-thru the virtual "nullfilter" denoted with "-"). This could only be useful for
-PS printers. If you want to print PS code on non-PS printers an entry as follows
-could be useful:</P
-><PRE
-CLASS="PROGRAMLISTING"
-> */* application/vnd.cups-raw 0 -</PRE
-><P
->and would effectively send *all* files to the backend without further processing.</P
-><P
->Lastly, you could have the following entry:</P
-><PRE
-CLASS="PROGRAMLISTING"
-> application/vnd.cups-postscript application/vnd.cups-raw 0 my_PJL_stripping_filter</PRE
-><P
->You will need to write a "my_PJL_stripping_filter" (could be a shellscript) that
-parses the PostScript and removes the unwanted PJL. This would need to conform to
-CUPS filter design (mainly, receive and pass the parameters printername, job-id,
-username, jobtitle, copies, print options and possibly the filename). It would
-be installed as world executable into "/usr/lib/cups/filters/" and will be called
-by CUPS if it encounters a MIME type "application/vnd.cups-postscript".</P
-><P
->CUPS can handle "-o job-hold-until=indefinite". This keeps the job in the queue
-"on hold". It will only be printed upon manual release by the printer operator.
-This is a requirement in many "central reproduction departments", where a few
-operators manage the jobs of hundreds of users on some big machine, where no
-user is allowed to have direct access. (The operators often need to load the
-proper paper type before running the 10.000 page job requested by marketing
-for the mailing, etc.).</P
-></DIV
-><DIV
-CLASS="SECT1"
-><H1
-CLASS="SECT1"
-><A
-NAME="AEN2118"
->14.4. CUPS as a network PostScript RIP -- CUPS drivers working on server, Adobe
-PostScript driver with CUPS-PPDs downloaded to clients</A
-></H1
-><P
->CUPS is perfectly able to use PPD files (PostScript
-Printer Descriptions). PPDs can control all print device options. They
-are usually provided by the manufacturer -- if you own a PostSript printer,
-that is. PPD files are always a component of PostScript printer drivers on MS
-Windows or Apple Mac OS systems. They are ASCII files containing
-user-selectable print options, mapped to appropriate PostScript, PCL or PJL
-commands for the target printer. Printer driver GUI dialogs translate these
-options "on-the-fly" into buttons and drop-down lists for the user to
-select.</P
-><P
->CUPS can load, without any conversions, the PPD file from
-any Windows (NT is recommended) PostScript driver and handle the options.
-There is a web browser interface to the print options (select
-http://localhost:631/printers/ and click on one "Configure Printer" button
-to see it), a commandline interface (see <B
-CLASS="COMMAND"
->man lpoptions</B
-> or
-try if you have <B
-CLASS="COMMAND"
->lphelp</B
-> on your system) plus some different GUI frontends on Linux
-UNIX, which can present PPD options to the users. PPD options are normally
-meant to become evaluated by the PostScript RIP on the real PostScript
-printer.</P
-><P
->CUPS doesn't stop at "real" PostScript printers in its
-usage of PPDs. The CUPS developers have extended the PPD concept, to also
-describe available device and driver options for non-PostScript printers
-through CUPS-PPDs.</P
-><P
->This is logical, as CUPS includes a fully featured
-PostScript interpreter (RIP). This RIP is based on Ghostscript. It can
-process all received PostScript (and additionally many other file formats)
-from clients. All CUPS-PPDs geared to non-PostScript printers contain an
-additional line, starting with the keyword <VAR
-CLASS="PARAMETER"
->*cupsFilter</VAR
->.
-This line
-tells the CUPS print system which printer-specific filter to use for the
-interpretation of the accompanying PostScript. Thus CUPS lets all its
-printers appear as PostScript devices to its clients, because it can act as a
-PostScript RIP for those printers, processing the received PostScript code
-into a proper raster print format.</P
-><P
->CUPS-PPDs can also be used on Windows-Clients, on top of a
-PostScript driver (recommended is the Adobe one).</P
-><P
->This feature enables CUPS to do a few tricks no other
-spooler can do:</P
-><P
-></P
-><UL
-><LI
-><P
->act as a networked PostScript RIP (Raster Image Processor), handling
- printfiles from all client platforms in a uniform way;</P
-></LI
-><LI
-><P
->act as a central accounting and billing server, as all files are passed
- through the <B
-CLASS="COMMAND"
->pstops</B
-> Filter and are therefor logged in
- the CUPS <TT
-CLASS="FILENAME"
->page&lowbar;log</TT
->. - <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->NOTE: </I
-></SPAN
->this
- can not happen with "raw" print jobs, which always remain unfiltered
- per definition;</P
-></LI
-><LI
-><P
->enable clients to consolidate on a single PostScript driver, even for
- many different target printers.</P
-></LI
-></UL
-></DIV
-><DIV
-CLASS="SECT1"
-><H1
-CLASS="SECT1"
-><A
-NAME="AEN2139"
->14.5. Windows Terminal Servers (WTS) as CUPS clients</A
-></H1
-><P
->This setup may be of special interest to people
-experiencing major problems in WTS environments. WTS need often a multitude
-of non-PostScript drivers installed to run their clients' variety of
-different printer models. This often imposes the price of much increased
-instability. In many cases, in an attempt to overcome this problem, site
-administrators have resorted to restrict the allowed drivers installed on
-their WTS to one generic PCL- and one PostScript driver. This however
-restricts the clients in the amount of printer options available for them --
-often they can't get out more then simplex prints from one standard paper
-tray, while their devices could do much better, if driven by a different
-driver!</P
-><P
->Using an Adobe PostScript driver, enabled with a CUPS-PPD,
-seems to be a very elegant way to overcome all these shortcomings. The
-PostScript driver is not known to cause major stability problems on WTS (even
-if used with many different PPDs). The clients will be able to (again) chose
-paper trays, duplex printing and other settings. However, there is a certain
-price for this too: a CUPS server acting as a PostScript RIP for its clients
-requires more CPU and RAM than just to act as a "raw spooling" device. Plus,
-this setup is not yet widely tested, although the first feedbacks look very
-promising...</P
-></DIV
-><DIV
-CLASS="SECT1"
-><H1
-CLASS="SECT1"
-><A
-NAME="AEN2143"
->14.6. Setting up CUPS for driver download</A
-></H1
-><P
->The <B
-CLASS="COMMAND"
->cupsadsmb</B
-> utility (shipped with all current
-CUPS versions) makes the sharing of any (or all) installed CUPS printers very
-easy. Prior to using it, you need the following settings in <TT
-CLASS="FILENAME"
->smb.conf</TT
->:</P
-><P
-><PRE
-CLASS="PROGRAMLISTING"
->[global]
- load printers = yes
- printing = cups
- printcap name = cups
-
- [printers]
- comment = All Printers
- path = /var/spool/samba
- browseable = no
- public = yes
- guest ok = yes
- writable = no
- printable = yes
- printer admin = root
-
- [print$]
- comment = Printer Drivers
- path = /etc/samba/drivers
- browseable = yes
- guest ok = no
- read only = yes
- write list = root
- </PRE
-></P
-><P
->For licensing reasons the necessary files of the Adobe
-Postscript driver can not be distributed with either Samba or CUPS. You need
-to download them yourself from the Adobe website. Once extracted, create a
-<TT
-CLASS="FILENAME"
->drivers</TT
-> directory in the CUPS data directory (usually
-<TT
-CLASS="FILENAME"
->/usr/share/cups/</TT
->). Copy the Adobe files using
-UPPERCASE filenames, to this directory as follows:</P
-><P
-><PRE
-CLASS="PROGRAMLISTING"
-> ADFONTS.MFM
- ADOBEPS4.DRV
- ADOBEPS4.HLP
- ADOBEPS5.DLL
- ADOBEPSU.DLL
- ADOBEPSU.HLP
- DEFPRTR2.PPD
- ICONLIB.DLL
- </PRE
-></P
-><P
->Users of the ESP Print Pro software are able to install
-their "Samba Drivers" package for this purpose with no problem.</P
-></DIV
-><DIV
-CLASS="SECT1"
-><H1
-CLASS="SECT1"
-><A
-NAME="AEN2156"
->14.7. Sources of CUPS drivers / PPDs</A
-></H1
-><P
->On the internet you can find now many thousand CUPS-PPD
-files (with their companion filters), in many national languages,
-supporting more than 1.000 non-PostScript models.</P
-><P
-></P
-><UL
-><LI
-><P
-><A
-HREF="http://wwwl.easysw.com/printpro/"
-TARGET="_top"
->ESP PrintPro
- (http://wwwl.easysw.com/printpro/)</A
->
- (commercial, non-Free) is packaged with more than 3.000 PPDs, ready for
- successful usage "out of the box" on Linux, IBM-AIX, HP-UX, Sun-Solaris,
- SGI-IRIX, Compaq Tru64, Digital Unix and some more commercial Unices (it
- is written by the CUPS developers themselves and its sales help finance
- the further development of CUPS, as they feed their creators)</P
-></LI
-><LI
-><P
->the <A
-HREF="http://gimp-print.sourceforge.net/"
-TARGET="_top"
->Gimp-Print-Project
- (http://gimp-print.sourceforge.net/)</A
->
- (GPL, Free Software) provides around 120 PPDs (supporting nearly 300
- printers, many driven to photo quality output), to be used alongside the
- Gimp-Print CUPS filters;</P
-></LI
-><LI
-><P
-><A
-HREF="http://www.turboprint.com/"
-TARGET="_top"
->TurboPrint
- (http://www.turboprint.com/)</A
->
- (Shareware, non-Freee) supports roughly the same amount of printers in
- excellent quality;</P
-></LI
-><LI
-><P
-><A
-HREF="http://www-124.ibm.com/developerworks/oss/linux/projects/omni/"
-TARGET="_top"
->OMNI
- (http://www-124.ibm.com/developerworks/oss/linux/projects/omni/)</A
->
- (LPGL, Free) is a package made by IBM, now containing support for more
- than 400 printers, stemming from the inheritance of IBM OS/2 KnowHow
- ported over to Linux (CUPS support is in a Beta-stage at present);</P
-></LI
-><LI
-><P
-><A
-HREF="http://hpinkjet.sourceforge.net/"
-TARGET="_top"
->HPIJS
- (http://hpinkjet.sourceforge.net/)</A
->
- (BSD-style licnes, Free) supports around 120 of HP's own printers and is
- also providing excellent print quality now;</P
-></LI
-><LI
-><P
-><A
-HREF="http://www.linuxprinting.org/"
-TARGET="_top"
->Foomatic/cupsomatic (http://www.linuxprinting.org/)</A
->
- (LPGL, Free) from Linuxprinting.org are providing PPDs for practically every
- Ghostscript filter known to the world, now usable with CUPS.</P
-></LI
-></UL
-><P
-><SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->NOTE: </I
-></SPAN
->the cupsomatic trick from Linuxprinting.org is
-working different from the other drivers. While the other drivers take the
-generic CUPS raster (produced by CUPS' own pstoraster PostScript RIP) as
-their input, cupsomatic "kidnaps" the PostScript inside CUPS, before
-RIP-ping, deviates it to an external Ghostscript installation (which now
-becomes the RIP) and gives it back to a CUPS backend once Ghostscript is
-finished. -- CUPS versions from 1.1.15 and later will provide their pstoraster
-PostScript RIP function again inside a system-wide Ghostscript
-installation rather than in "their own" pstoraster filter. (This
-CUPS-enabling Ghostscript version may be installed either as a
-patch to GNU or AFPL Ghostscript, or as a complete ESP Ghostscript package).
-However, this will not change the cupsomatic approach of guiding the printjob
-along a different path through the filtering system than the standard CUPS
-way...</P
-><P
->Once you installed a printer inside CUPS with one of the
-recommended methods (the lpadmin command, the web browser interface or one of
-the available GUI wizards), you can use <B
-CLASS="COMMAND"
->cupsaddsmb</B
-> to share the
-printer via Samba. <B
-CLASS="COMMAND"
->cupsaddsmb</B
-> prepares the driver files for
-comfortable client download and installation upon their first contact with
-this printer share.</P
-><DIV
-CLASS="SECT2"
-><H2
-CLASS="SECT2"
-><A
-NAME="AEN2183"
->14.7.1. <B
-CLASS="COMMAND"
->cupsaddsmb</B
-></A
-></H2
-><P
->The <B
-CLASS="COMMAND"
->cupsaddsmb</B
-> command copies the needed files
-for convenient Windows client installations from the previously prepared CUPS
-data directory to your [print$] share. Additionally, the PPD
-associated with this printer is copied from <TT
-CLASS="FILENAME"
->/etc/cups/ppd/</TT
-> to
-[print$].</P
-><P
-><PRE
-CLASS="PROGRAMLISTING"
-><SAMP
-CLASS="PROMPT"
->root# </SAMP
-> <B
-CLASS="COMMAND"
->cupsaddsmb -U root infotec_IS2027</B
->
-Password for root required to access localhost via SAMBA: <KBD
-CLASS="USERINPUT"
->[type in password 'secret']</KBD
-></PRE
-></P
-><P
->To share all printers and drivers, use the <VAR
-CLASS="PARAMETER"
->-a</VAR
->
-parameter instead of a printer name.</P
-><P
->Probably you want to see what's going on. Use the
-<VAR
-CLASS="PARAMETER"
->-v</VAR
-> parameter to get a more verbose output:</P
-><P
->Probably you want to see what's going on. Use the
-<VAR
-CLASS="PARAMETER"
->-v</VAR
-> parameter to get a more verbose output:</P
-><P
-><PRE
-CLASS="PROGRAMLISTING"
->Note: The following line shave been wrapped so that information is not lost.
-
-<SAMP
-CLASS="PROMPT"
->root# </SAMP
-> cupsaddsmb -v -U root infotec_IS2027
- Password for root required to access localhost via SAMBA:
- Running command: smbclient //localhost/print\$ -N -U'root%secret' -c 'mkdir W32X86;put
- /var/spool/cups/tmp/3cd1cc66376c0 W32X86/infotec_IS2027.PPD;put /usr/share/cups/drivers/
- ADOBEPS5.DLL W32X86/ADOBEPS5.DLL;put /usr/share/cups/drivers/ADOBEPSU.DLLr
- W32X86/ADOBEPSU.DLL;put /usr/share/cups/drivers/ADOBEPSU.HLP W32X86/ADOBEPSU.HLP'
- added interface ip=10.160.16.45 bcast=10.160.31.255 nmask=255.255.240.0
- added interface ip=192.168.182.1 bcast=192.168.182.255 nmask=255.255.255.0
- added interface ip=172.16.200.1 bcast=172.16.200.255 nmask=255.255.255.0
- Domain=[TUX-NET] OS=[Unix] Server=[Samba 2.2.3a.200204262025cvs]
- NT_STATUS_OBJECT_NAME_COLLISION making remote directory \W32X86
- putting file /var/spool/cups/tmp/3cd1cc66376c0 as \W32X86/infotec_IS2027.PPD (17394.6 kb/s)
- (average 17395.2 kb/s)
- putting file /usr/share/cups/drivers/ADOBEPS5.DLL as \W32X86/ADOBEPS5.DLL (10877.4 kb/s)
- (average 11343.0 kb/s)
- putting file /usr/share/cups/drivers/ADOBEPSU.DLL as \W32X86/ADOBEPSU.DLL (5095.2 kb/s)
- (average 9260.4 kb/s)
- putting file /usr/share/cups/drivers/ADOBEPSU.HLP as \W32X86/ADOBEPSU.HLP (8828.7 kb/s)
- (average 9247.1 kb/s)
-
- Running command: smbclient //localhost/print\$ -N -U'root%secret' -c 'mkdir WIN40;put
- /var/spool/cups/tmp/3cd1cc66376c0 WIN40/infotec_IS2027.PPD;put
- /usr/share/cups/drivers/ADFONTS.MFM WIN40/ADFONTS.MFM;put
- /usr/share/cups/drivers/ADOBEPS4.DRV WIN40/ADOBEPS4.DRV;put
- /usr/share/cups/drivers/ADOBEPS4.HLP WIN40/ADOBEPS4.HLP;put
- /usr/share/cups/drivers/DEFPRTR2.PPD WIN40/DEFPRTR2.PPD;put
- /usr/share/cups/drivers/ICONLIB.DLL WIN40/ICONLIB.DLL;put
- /usr/share/cups/drivers/PSMON.DLL WIN40/PSMON.DLL;'
- added interface ip=10.160.16.45 bcast=10.160.31.255 nmask=255.255.240.0
- added interface ip=192.168.182.1 bcast=192.168.182.255 nmask=255.255.255.0
- added interface ip=172.16.200.1 bcast=172.16.200.255 nmask=255.255.255.0
- Domain=[TUX-NET] OS=[Unix] Server=[Samba 2.2.3a.200204262025cvs]
- NT_STATUS_OBJECT_NAME_COLLISION making remote directory \WIN40
- putting file /var/spool/cups/tmp/3cd1cc66376c0 as \WIN40/infotec_IS2027.PPD (26091.5 kb/s)
- (average 26092.8 kb/s)
- putting file /usr/share/cups/drivers/ADFONTS.MFM as \WIN40/ADFONTS.MFM (11241.6 kb/s)
- (average 11812.9 kb/s)
- putting file /usr/share/cups/drivers/ADOBEPS4.DRV as \WIN40/ADOBEPS4.DRV (16640.6 kb/s)
- (average 14679.3 kb/s)
- putting file /usr/share/cups/drivers/ADOBEPS4.HLP as \WIN40/ADOBEPS4.HLP (11285.6 kb/s)
- (average 14281.5 kb/s)
- putting file /usr/share/cups/drivers/DEFPRTR2.PPD as \WIN40/DEFPRTR2.PPD (823.5 kb/s)
- (average 12944.0 kb/s)
- putting file /usr/share/cups/drivers/ICONLIB.DLL as \WIN40/ICONLIB.DLL (19226.2 kb/s)
- (average 13169.7 kb/s)
- putting file /usr/share/cups/drivers/PSMON.DLL as \WIN40/PSMON.DLL (18666.1 kb/s)
- (average 13266.7 kb/s)
-
- Running command: rpcclient localhost -N -U'root%secret' -c 'adddriver "Windows NT x86"
- "infotec_IS2027:ADOBEPS5.DLL:infotec_IS2027.PPD:ADOBEPSU.DLL:ADOBEPSU.HLP:NULL:RAW:NULL"'
- cmd = adddriver "Windows NT x86" "infotec_IS2027:ADOBEPS5.DLL:infotec_IS2027.PPD:ADOBEPSU.DLL:
- ADOBEPSU.HLP:NULL:RAW:NULL"
- Printer Driver infotec_IS2027 successfully installed.
-
- Running command: rpcclient localhost -N -U'root%secret' -c 'adddriver "Windows 4.0"
- "infotec_IS2027:ADOBEPS4.DRV:infotec_IS2027.PPD:NULL:ADOBEPS4.HLP:PSMON.DLL:RAW:
- ADFONTS.MFM,DEFPRTR2.PPD,ICONLIB.DLL"'
- cmd = adddriver "Windows 4.0" "infotec_IS2027:ADOBEPS4.DRV:infotec_IS2027.PPD:NULL:
- ADOBEPS4.HLP:PSMON.DLL:RAW:ADFONTS.MFM,DEFPRTR2.PPD,ICONLIB.DLL"
- Printer Driver infotec_IS2027 successfully installed.
-
- Running command: rpcclient localhost -N -U'root%secret'
- -c 'setdriver infotec_IS2027 infotec_IS2027'
- cmd = setdriver infotec_IS2027 infotec_IS2027
- Succesfully set infotec_IS2027 to driver infotec_IS2027.
-
- <SAMP
-CLASS="PROMPT"
->root# </SAMP
-></PRE
-></P
-><P
->If you look closely, you'll discover your root password was transfered unencrypted over
-the wire, so beware! Also, if you look further her, you'll discover error messages like
-<CODE
-CLASS="CONSTANT"
->NT_STATUS_OBJECT_NAME_COLLISION</CODE
-> in between. They occur, because
-the directories <TT
-CLASS="FILENAME"
->WIN40</TT
-> and <TT
-CLASS="FILENAME"
->W32X86</TT
-> already
-existed in the [print$] driver download share (from a previous driver
-installation). They are harmless here.</P
-><P
->Now your printer is prepared for the clients to use. From
-a client, browse to the CUPS/Samba server, open the "Printers"
-share, right-click on this printer and select "Install..." or
-"Connect..." (depending on the Windows version you use). Now their
-should be a new printer in your client's local "Printers" folder,
-named (in my case) "infotec_IS2027 on kdebitshop"</P
-><P
-><SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->NOTE: </I
-></SPAN
->
-<B
-CLASS="COMMAND"
->cupsaddsmb</B
-> will only reliably work i
-with CUPS version 1.1.15 or higher
-and Samba from 2.2.4. If it doesn't work, or if the automatic printer
-driver download to the clients doesn't succeed, you can still manually
-install the CUPS printer PPD on top of the Adobe PostScript driver on
-clients and then point the client's printer queue to the Samba printer
-share for connection, should you desire to use the CUPS networked
-PostScript RIP functions.</P
-></DIV
-></DIV
-><DIV
-CLASS="SECT1"
-><H1
-CLASS="SECT1"
-><A
-NAME="AEN2212"
->14.8. The CUPS Filter Chains</A
-></H1
-><P
->The following diagrams reveal how CUPS handles print jobs.</P
-><PRE
-CLASS="PROGRAMLISTING"
->#########################################################################
-#
-# CUPS in and of itself has this (general) filter chain (CAPITAL
-# letters are FILE-FORMATS or MIME types, other are filters (this is
-# true for pre-1.1.15 of pre-4.3 versions of CUPS and ESP PrintPro):
-#
-# <VAR
-CLASS="REPLACEABLE"
->SOMETHNG</VAR
->-FILEFORMAT
-# |
-# |
-# V
-# <VAR
-CLASS="REPLACEABLE"
->something</VAR
->tops
-# |
-# |
-# V
-# APPLICATION/POSTSCRIPT
-# |
-# |
-# V
-# pstops
-# |
-# |
-# V
-# APPLICATION/VND.CUPS-POSTSCRIPT
-# |
-# |
-# V
-# pstoraster # as shipped with CUPS, independent from any Ghostscipt
-# | # installation on the system
-# | (= "postscipt interpreter")
-# |
-# V
-# APPLICATION/VND.CUPS-RASTER
-# |
-# |
-# V
-# rasterto<VAR
-CLASS="REPLACEABLE"
->something</VAR
-> (f.e. Gimp-Print filters may be plugged in here)
-# | (= "raster driver")
-# |
-# V
-# SOMETHING-DEVICE-SPECIFIC
-# |
-# |
-# V
-# backend
-#
-#
-# ESP PrintPro has some enhanced "rasterto<VAR
-CLASS="REPLACEABLE"
->something</VAR
->" filters as compared to
-# CUPS, and also a somewhat improved "pstoraster" filter.
-#
-# NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to
-# CUPS and ESP PrintPro plug-in where rasterto<VAR
-CLASS="REPLACEABLE"
->something</VAR
-> is noted.
-#
-#########################################################################</PRE
-><PRE
-CLASS="PROGRAMLISTING"
->#########################################################################
-#
-# This is how "cupsomatic" comes into play:
-# =========================================
-#
-# <VAR
-CLASS="REPLACEABLE"
->SOMETHNG</VAR
->-FILEFORMAT
-# |
-# |
-# V
-# <VAR
-CLASS="REPLACEABLE"
->something</VAR
->tops
-# |
-# |
-# V
-# APPLICATION/POSTSCRIPT
-# |
-# |
-# V
-# pstops
-# |
-# |
-# V
-# APPLICATION/VND.CUPS-POSTSCRIPT ----------------+
-# | |
-# | V
-# V cupsomatic
-# pstoraster (constructs complicated
-# | (= "postscipt interpreter") Ghostscript commandline
-# | to let the file be
-# V processed by a
-# APPLICATION/VND.CUPS-RASTER "-sDEVICE=<VAR
-CLASS="REPLACEABLE"
->s.th.</VAR
->"
-# | call...)
-# | |
-# V |
-# rasterto<VAR
-CLASS="REPLACEABLE"
->something</VAR
-> V
-# | (= "raster driver") +-------------------------+
-# | | Ghostscript at work.... |
-# V | |
-# SOMETHING-DEVICE-SPECIFIC *-------------------------+
-# | |
-# | |
-# V |
-# backend &#62;------------------------------------+
-# |
-# |
-# V
-# THE PRINTER
-#
-#
-# Note, that cupsomatic "kidnaps" the printfile after the
-# "APPLICATION/VND.CUPS-POSTSCRPT" stage and deviates it through
-# the CUPS-external, systemwide Ghostscript installation, bypassing the
-# "pstoraster" filter (therefor also bypassing the CUPS-raster-drivers
-# "rasterto<VAR
-CLASS="REPLACEABLE"
->something</VAR
->", and hands the rasterized file directly to the CUPS
-# backend...
-#
-# cupsomatic is not made by the CUPS developers. It is an independent
-# contribution to printing development, made by people from
-# Linuxprinting.org. (see also http://www.cups.org/cups-help.html)
-#
-# NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to
-# CUPS and ESP PrintPro plug-in where rasterto<VAR
-CLASS="REPLACEABLE"
->something</VAR
-> is noted.
-#
-#########################################################################</PRE
-><PRE
-CLASS="PROGRAMLISTING"
->#########################################################################
-#
-# And this is how it works for ESP PrintPro from 4.3:
-# ===================================================
-#
-# <VAR
-CLASS="REPLACEABLE"
->SOMETHNG</VAR
->-FILEFORMAT
-# |
-# |
-# V
-# <VAR
-CLASS="REPLACEABLE"
->something</VAR
->tops
-# |
-# |
-# V
-# APPLICATION/POSTSCRIPT
-# |
-# |
-# V
-# pstops
-# |
-# |
-# V
-# APPLICATION/VND.CUPS-POSTSCRIPT
-# |
-# |
-# V
-# gsrip
-# | (= "postscipt interpreter")
-# |
-# V
-# APPLICATION/VND.CUPS-RASTER
-# |
-# |
-# V
-# rasterto<VAR
-CLASS="REPLACEABLE"
->something</VAR
-> (f.e. Gimp-Print filters may be plugged in here)
-# | (= "raster driver")
-# |
-# V
-# SOMETHING-DEVICE-SPECIFIC
-# |
-# |
-# V
-# backend
-#
-# NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to
-# CUPS and ESP PrintPro plug-in where rasterto<VAR
-CLASS="REPLACEABLE"
->something</VAR
-> is noted.
-#
-#########################################################################</PRE
-><PRE
-CLASS="PROGRAMLISTING"
->#########################################################################
-#
-# This is how "cupsomatic" would come into play with ESP PrintPro:
-# ================================================================
-#
-#
-# <VAR
-CLASS="REPLACEABLE"
->SOMETHNG</VAR
->-FILEFORMAT
-# |
-# |
-# V
-# <VAR
-CLASS="REPLACEABLE"
->something</VAR
->tops
-# |
-# |
-# V
-# APPLICATION/POSTSCRIPT
-# |
-# |
-# V
-# pstops
-# |
-# |
-# V
-# APPLICATION/VND.CUPS-POSTSCRIPT ----------------+
-# | |
-# | V
-# V cupsomatic
-# gsrip (constructs complicated
-# | (= "postscipt interpreter") Ghostscript commandline
-# | to let the file be
-# V processed by a
-# APPLICATION/VND.CUPS-RASTER "-sDEVICE=<VAR
-CLASS="REPLACEABLE"
->s.th.</VAR
->"
-# | call...)
-# | |
-# V |
-# rasterto<VAR
-CLASS="REPLACEABLE"
->something</VAR
-> V
-# | (= "raster driver") +-------------------------+
-# | | Ghostscript at work.... |
-# V | |
-# SOMETHING-DEVICE-SPECIFIC *-------------------------+
-# | |
-# | |
-# V |
-# backend &#62;------------------------------------+
-# |
-# |
-# V
-# THE PRINTER
-#
-# NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to
-# CUPS and ESP PrintPro plug-in where rasterto<VAR
-CLASS="REPLACEABLE"
->something</VAR
-> is noted.
-#
-#########################################################################</PRE
-><PRE
-CLASS="PROGRAMLISTING"
->#########################################################################
-#
-# And this is how it works for CUPS from 1.1.15:
-# ==============================================
-#
-# <VAR
-CLASS="REPLACEABLE"
->SOMETHNG</VAR
->-FILEFORMAT
-# |
-# |
-# V
-# <VAR
-CLASS="REPLACEABLE"
->something</VAR
->tops
-# |
-# |
-# V
-# APPLICATION/POSTSCRIPT
-# |
-# |
-# V
-# pstops
-# |
-# |
-# V
-# APPLICATION/VND.CUPS-POSTSCRIPT-----+
-# |
-# +------------------v------------------------------+
-# | Ghostscript |
-# | at work... |
-# | (with |
-# | "-sDEVICE=cups") |
-# | |
-# | (= "postscipt interpreter") |
-# | |
-# +------------------v------------------------------+
-# |
-# |
-# APPLICATION/VND.CUPS-RASTER &#62;-------+
-# |
-# |
-# V
-# rasterto<VAR
-CLASS="REPLACEABLE"
->something</VAR
->
-# | (= "raster driver")
-# |
-# V
-# SOMETHING-DEVICE-SPECIFIC
-# |
-# |
-# V
-# backend
-#
-#
-# NOTE: since version 1.1.15 CUPS "outsourced" the pstoraster process to
-# Ghostscript. GNU Ghostscript needs to be patched to handle the
-# CUPS requirement; ESP Ghostscript has this builtin. In any case,
-# "gs -h" needs to show up a "cups" device. pstoraster is now a
-# calling an appropriate "gs -sDEVICE=cups..." commandline to do
-# the job. It will output "application/vnd.cup-raster", which will
-# be finally processed by a CUPS raster driver "rasterto<VAR
-CLASS="REPLACEABLE"
->something</VAR
->"
-# Note the difference to "cupsomatic", which will *not* output
-# CUPS-raster, but a final version of the printfile, ready to be
-# sent to the printer. cupsomatic also doesn't use the "cups"
-# devicemode in Ghostscript, but one of the classical devicemodes....
-#
-# NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to
-# CUPS and ESP PrintPro plug-in where rasterto<VAR
-CLASS="REPLACEABLE"
->something</VAR
-> is noted.
-#
-#########################################################################</PRE
-><PRE
-CLASS="PROGRAMLISTING"
->#########################################################################
-#
-# And this is how it works for CUPS from 1.1.15, with cupsomatic included:
-# ========================================================================
-#
-# <VAR
-CLASS="REPLACEABLE"
->SOMETHNG</VAR
->-FILEFORMAT
-# |
-# |
-# V
-# <VAR
-CLASS="REPLACEABLE"
->something</VAR
->tops
-# |
-# |
-# V
-# APPLICATION/POSTSCRIPT
-# |
-# |
-# V
-# pstops
-# |
-# |
-# V
-# APPLICATION/VND.CUPS-POSTSCRIPT-----+
-# |
-# +------------------v------------------------------+
-# | Ghostscript . Ghostscript at work.... |
-# | at work... . (with "-sDEVICE= |
-# | (with . <VAR
-CLASS="REPLACEABLE"
->s.th.</VAR
->" |
-# | "-sDEVICE=cups") . |
-# | . |
-# | (CUPS standard) . (cupsomatic) |
-# | . |
-# | (= "postscript interpreter") |
-# | . |
-# +------------------v--------------v---------------+
-# | |
-# | |
-# APPLICATION/VND.CUPS-RASTER &#62;-------+ |
-# | |
-# | |
-# V |
-# rasterto<VAR
-CLASS="REPLACEABLE"
->something</VAR
-> |
-# | (= "raster driver") |
-# | |
-# V |
-# SOMETHING-DEVICE-SPECIFIC &#62;------------------------+
-# |
-# |
-# V
-# backend
-#
-#
-# NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to
-# CUPS and ESP PrintPro plug-in where rasterto<VAR
-CLASS="REPLACEABLE"
->something</VAR
-> is noted.
-#
-##########################################################################</PRE
-></DIV
-><DIV
-CLASS="SECT1"
-><H1
-CLASS="SECT1"
-><A
-NAME="AEN2251"
->14.9. CUPS Print Drivers and Devices</A
-></H1
-><P
->CUPS ships with good support for HP LaserJet type printers. You can install
-the driver as follows:
-
-<P
-></P
-><UL
-><LI
-><P
-> lpadmin -p laserjet4plus -v parallel:/dev/lp0 -E -m laserjet.ppd
- </P
-></LI
-></UL
->
-
-(The "-m" switch will retrieve the "laserjet.ppd" from the standard repository
-for not-yet-installed-PPDs, which CUPS typically stores in
-<TT
-CLASS="FILENAME"
->/usr/share/cups/model</TT
->. Alternatively, you may use
-"-P /absolute/filesystem/path/to/where/there/is/PPD/your.ppd").</P
-><DIV
-CLASS="SECT2"
-><H2
-CLASS="SECT2"
-><A
-NAME="AEN2258"
->14.9.1. Further printing steps</A
-></H2
-><P
->Always also consult the database on linuxprinting.org for all recommendations
-about which driver is best used for each printer:</P
-><P
-><A
-HREF="http://www.linuxprinting.org/printer_list.cgi"
-TARGET="_top"
->http://www.linuxprinting.org/printer_list.cgi</A
-></P
-><P
->There select your model and click on "Show". You'll arrive at a page listing
-all drivers working with your model. There will always be *one*
-<SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->recommended</I
-></SPAN
-> one. Try this one first. In your case
-("HP LaserJet 4 Plus"), you'll arrive here:</P
-><P
-><A
-HREF="http://www.linuxprinting.org/show_printer.cgi?recnum=75104"
-TARGET="_top"
->http://www.linuxprinting.org/show_printer.cgi?recnum=75104</A
-></P
-><P
->The recommended driver is "ljet4". It has a link to the page for the ljet4
-driver too:</P
-><P
-><A
-HREF="http://www.linuxprinting.org/show_driver.cgi?driver=ljet4"
-TARGET="_top"
->http://www.linuxprinting.org/show_driver.cgi?driver=ljet4</A
-></P
-><P
->On the driver's page, you'll find important and detailed info about how to use
-that driver within the various available spoolers. You can generate a PPD for
-CUPS. The PPD contains all the info about how to use your model and the driver;
-this is, once installed, working transparently for the user -- you'll only
-need to choose resolution, paper size etc. from the web-based menu or from
-the print dialog GUI or from the commandline...</P
-><P
->On the driver's page, choose to use the "PPD-O-Matic" online PPD generator
-program. Select your model and click "Generate PPD file". When you safe the
-appearing ASCII text file, don't use "cut'n'past" (as it could possiblly corrupt
-line endings and tabs), but use "Save as..." in your browser's menu. Save it
-at "/some/path/on/your/filesystem/somewhere/my-name-for-my-printer.ppd"</P
-><P
->Then install the printer:</P
-><P
-><PRE
-CLASS="PROGRAMLISTING"
-> "lpadmin -p laserjet4plus -v parallel:/dev/lp0 -E \
- -P /some/path/on/your/filesystem/somewhere/my-name-for-my-printer.ppd"</PRE
-></P
-><P
->Note, that for all the "Foomatic-PPDs" from Linuxprinting.org, you also need
-a special "CUPS filter" named "cupsomatic". Get the latest version of
-"cupsomatic" from:</P
-><P
-><A
-HREF="http://www.linuxprinting.org/cupsomatic"
-TARGET="_top"
->http://www.linuxprinting.org/cupsomatic</A
-></P
-><P
->This needs to be copied to <TT
-CLASS="FILENAME"
->/usr/lib/cups/filter/cupsomatic</TT
->
-and be made world executable. This filter is needed to read and act upon the
-specially encoded Foomatic comments, embedded in the printfile, which in turn
-are used to construct (transparently for you, the user) the complicated
-ghostscript command line needed for your printer/driver combo.</P
-><P
->You can have a look at all the options for the Ghostscript commandline supported
-by your printer and the ljet4 driver by going to the section "Execution details",
-selecting your model (Laserjet 4 Plus) and clicking on "Show execution details".
-This will bring up this web page:</P
-><P
-><A
-HREF="http://www.linuxprinting.org/execution.cgi?driver=ljet4&printer=75104&.submit=Show+execution+details"
-TARGET="_top"
->http://www.linuxprinting.org/execution.cgi?driver=ljet4&#38;printer=75104&#38;.submit=Show+execution+details</A
-></P
-><P
->The ingenious thing is that the database is kept current. If there
-is a bug fix and an improvement somewhere in the database, you will
-always get the most current and stable and feature-rich driver by following
-the steps described above.</P
-><DIV
-CLASS="NOTE"
-><P
-></P
-><TABLE
-CLASS="NOTE"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->Till Kamppeter from MandrakeSoft is doing an excellent job here that too few
-people are aware of. (So if you use it often, please send him a note showing
-your appreciation).</P
-></TD
-></TR
-></TABLE
-></DIV
-><P
->The latest and greatest improvement now is support for "custom page sizes"
-for all those printers which support it.</P
-><P
->"cupsomatic" is documented here:</P
-><P
-><A
-HREF="http://www.linuxprinting.org/cups-doc.html"
-TARGET="_top"
->http://www.linuxprinting.org/cups-doc.html</A
-></P
-><P
->More printing tutorial info may be found here:</P
-><P
-><A
-HREF="http://www.linuxprinting.org/kpfeifle/LinuxKongress2002/Tutorial/"
-TARGET="_top"
->http://www.linuxprinting.org/kpfeifle/LinuxKongress2002/Tutorial/</A
-></P
-><P
->Note, that *all* the Foomatic drivers listed on Linuxprinting.org (now
-approaching the "all-time high" number of 1.000 for the supported models)
-are using a special filtering chain involving Ghostscript, as described
-in this document.</P
-><P
->Summary - You need:</P
-><P
-><P
-></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
->A "foomatic+<VAR
-CLASS="REPLACEABLE"
->something</VAR
->" PPD is not enough to print with CUPS (but it is *one* important component)</TD
-></TR
-><TR
-><TD
->The "cupsomatic" filter script (Perl) in <TT
-CLASS="FILENAME"
->/usr/lib/cups/filters/</TT
-></TD
-></TR
-><TR
-><TD
->Perl to make cupsomatic run</TD
-></TR
-><TR
-><TD
->Ghostscript (because it is called and controlled by the PPD/cupsomatic combo in a way to fit your printermodel/driver combo.</TD
-></TR
-><TR
-><TD
->Ghostscript *must*, depending on the driver/model, contain support for a certain "device" (as shown by "gs -h")</TD
-></TR
-></TBODY
-></TABLE
-><P
-></P
-></P
-><P
->In the case of the "hpijs" driver, you need a Ghostscript version, which
-has "ijs" amongst its supported devices in "gs -h". In the case of
-"hpijs+foomatic", a valid ghostscript commandline would be reading like this:</P
-><P
-><PRE
-CLASS="PROGRAMLISTING"
-> gs -q -dBATCH -dPARANOIDSAFER -dQUIET -dNOPAUSE -sDEVICE=ijs \
- -sIjsServer=hpijs<VAR
-CLASS="REPLACEABLE"
->PageSize</VAR
-> -dDuplex=<VAR
-CLASS="REPLACEABLE"
->Duplex</VAR
-> <VAR
-CLASS="REPLACEABLE"
->Model</VAR
-> \
- -r<VAR
-CLASS="REPLACEABLE"
->Resolution</VAR
->,PS:MediaPosition=<VAR
-CLASS="REPLACEABLE"
->InputSlot</VAR
-> -dIjsUseOutputFD \
- -sOutputFile=- -</PRE
-></P
-><DIV
-CLASS="NOTE"
-><P
-></P
-><TABLE
-CLASS="NOTE"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->Note, that with CUPS and the "hpijs+foomatic" PPD (plus Perl and cupsomatic)
-you don't need to remember this. You can choose the available print options
-thru a GUI print command (like "glp" from ESP's commercially supported
-PrintPro software, or KDE's "kprinter", or GNOME's "gtklp" or the independent
-"xpp") or the CUPS web interface via human-readable drop-down selection
-menus.</P
-></TD
-></TR
-></TABLE
-></DIV
-><P
->If you use "ESP Ghostscript" (also under the GPL, provided by Easy Software
-Products, the makers of CUPS, downloadable from
-<A
-HREF="http://www.cups.org/software.html"
-TARGET="_top"
->http://www.cups.org/software.html</A
->,
-co-maintained by the developers of linuxprinting.org), you are guaranteed to
-have in use the most uptodate, bug-fixed, enhanced and stable version of a Free
-Ghostscript. It contains support for ~300 devices, whereas plain vanilla
-GNU Ghostscript 7.05 only has ~200.</P
-><P
->If you print only one CUPS test page, from the web interface and when you try to
-print a windows test page, it acts like the job was never sent:
-
-<P
-></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
->Can you print "standard" jobs from the CUPS machine?</TD
-></TR
-><TR
-><TD
->Are the jobs from Windows visible in the Web interface on CUPS (http://localhost:631/)?</TD
-></TR
-><TR
-><TD
-><SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->Most important:</I
-></SPAN
-> What kind of printer driver are you using on the Windows clients?</TD
-></TR
-></TBODY
-></TABLE
-><P
-></P
->
-
-You can try to get a more detailed debugging info by setting "LogLevel debug" in
-<TT
-CLASS="FILENAME"
->/etc/cups/cupsd.conf</TT
->, re-start cupsd and investigate <TT
-CLASS="FILENAME"
->/var/log/cups/error_log</TT
->
-for the whereabouts of your Windows-originating printjobs:</P
-><P
-></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
->what does the "auto-typing" line say? which is the "MIME type" CUPS thinks is arriving from the Windows clients?</TD
-></TR
-><TR
-><TD
->are there "filter" available for this MIME type?</TD
-></TR
-><TR
-><TD
->are there "filter rules" defined in "/etc/cups/mime.convs" for this MIME type?</TD
-></TR
-></TBODY
-></TABLE
-><P
-></P
-></DIV
-></DIV
-><DIV
-CLASS="SECT1"
-><H1
-CLASS="SECT1"
-><A
-NAME="AEN2328"
->14.10. Limiting the number of pages users can print</A
-></H1
-><P
->The feature you want is dependent on the real print subsystem you're using.
-Samba's part is always to receive the job files from the clients (filtered
-*or* unfiltered) and hand it over to this printing subsystem.</P
-><P
->Of course one could "hack" things with one's own scripts.</P
-><P
->But there is CUPS (Common Unix Printing System). CUPS supports "quotas".
-Quotas can be based on sizes of jobs or on the number of pages or both,
-and are spanning any time period you want.</P
-><P
->This is an example command how root would set a print quota in CUPS,
-assuming an existing printer named "quotaprinter":</P
-><PRE
-CLASS="PROGRAMLISTING"
-> lpadmin -p quotaprinter -o job-quota-period=604800 -o job-k-limit=1024 \
- -o job-page-limit=100</PRE
-><P
->This would limit every single user to print 100 pages or 1024 KB of
-data (whichever comes first) within the last 604.800 seconds ( = 1 week).</P
-><P
->For CUPS to count correctly, the printfile needs to pass the CUPS "pstops" filter,
-otherwise it uses a "dummy" count of "1". Some printfiles don't pass it
-(eg: image files) but then those are mostly 1 page jobs anyway. This also means,
-proprietary drivers for the target printer running on the client computers and
-CUPS/Samba then spooling these files as "raw" (i.e. leaving them untouched, not
-filtering them), will be counted as "1-pagers" too!</P
-><P
->You need to send PostScript from the clients (i.e. run a PostScript driver there)
-for having the chance to get accounting done. If the printer is a non-PostScript model,
-you need to let CUPS do the job to convert the file to a print-ready format for the
-target printer. This will be working for currently ~1.000 different printer models, see</P
-><PRE
-CLASS="PROGRAMLISTING"
-> http://www.linuxprinting.org/printer_list.cgi</PRE
-><P
->Before CUPS-1.1.16 your only option was to use the Adobe PostScript
-Driver on the Windows clients. The output of this driver was not always
-passed thru the "pstops" filter on the CUPS/Samba side, and therefor was
-not counted correctly (the reason is that it often --- depending on the
-"PPD" being used --- did write a "PJL"-header in front of the real
-PostScript which made CUPS to skip the pstops and go directy to
-the "pstoraster" stage).</P
-><P
->From CUPS-1.1.16 onward you can use the "CUPS PostScript Driver
-for Windows NT/2K/XP clients" (it is tagged in the download area of
-http://www.cups.org/ as the "cups-samba-1.1.16.tar.gz" package).
-It is *not* working for Win9x/ME clients. But it:</P
-><P
-></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
->it guarantees to not write an PJL-header</TD
-></TR
-><TR
-><TD
->it guarantees to still read and support all PJL-options named in the driver PPD with its own means</TD
-></TR
-><TR
-><TD
->it guarantees the file going thru the "pstops" filter on the CUPS/Samba server</TD
-></TR
-><TR
-><TD
->it guarantees to page-count correctly the printfile</TD
-></TR
-></TBODY
-></TABLE
-><P
-></P
-><P
->You can read more about the setup of this combination in the
-manpage for "cupsaddsmb" (only present with CUPS installed, only
-current with CUPS 1.1.16).</P
-><P
->These are the items CUPS logs in the "page_log" for every single *page* of a job:</P
-><P
-><P
-></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
->Printer name</TD
-></TR
-><TR
-><TD
->User name</TD
-></TR
-><TR
-><TD
->Job ID</TD
-></TR
-><TR
-><TD
->Time of printing</TD
-></TR
-><TR
-><TD
->the page number</TD
-></TR
-><TR
-><TD
->the number of copies</TD
-></TR
-><TR
-><TD
->a billing info string (optional)</TD
-></TR
-></TBODY
-></TABLE
-><P
-></P
-></P
-><P
->Here is an extract of my CUPS server's page_log file to illustrate
-the format and included items:</P
-><P
-><SAMP
-CLASS="COMPUTEROUTPUT"
-> infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 1 2 #marketing
- infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 2 2 #marketing
- infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 3 2 #marketing
- infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 4 2 #marketing
- infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 5 2 #marketing
- infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 6 2 #marketing</SAMP
-></P
-><P
->This was Job ID "40", printed on "infotec_IS2027" by user "kurt", a 6-page job
-printed in 2 copies and billed to "#marketing"...</P
-><P
->What flaws or shortcomings are there?</P
-><P
-></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
->the ones named above</TD
-></TR
-><TR
-><TD
-> CUPS really counts the job pages being *processsed in software*
- (going thru the "RIP") rather than the physical sheets successfully
- leaving the printing device -- if there is a jam while printing
- the 5th sheet out of 1000 and the job is aborted by the printer,
- the "page count" will still show the figure of 1000 for that job
- </TD
-></TR
-><TR
-><TD
-> all quotas are the same for all users (no flexibility to give the
- boss a higher quota than the clerk) no support for groups
- </TD
-></TR
-><TR
-><TD
-> no means to read out the current balance or "used-up" number of current quota
- </TD
-></TR
-><TR
-><TD
-> a user having used up 99 sheets of 100 quota will still be able to send and print a 1.000 sheet job
- </TD
-></TR
-><TR
-><TD
-> a user being denied a job because of a filled-up quota doesn't get a meaningful
- error message from CUPS other than "client-error-not-possible".
- </TD
-></TR
-></TBODY
-></TABLE
-><P
-></P
-><P
->But this is the best system out there currently. And there are
-huge improvements under development:</P
-><P
-></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
->page counting will go into the "backends" (these talk
- directly to the printer and will increase the count in sync with the
- actual printing process -- a jam at the 5th sheet will lead to a stop in the counting)</TD
-></TR
-><TR
-><TD
->quotas will be handled more flexibly</TD
-></TR
-><TR
-><TD
->probably there will be support for users to inquire their "accounts" in advance</TD
-></TR
-><TR
-><TD
->probably there will be support for some other tools around this topic</TD
-></TR
-></TBODY
-></TABLE
-><P
-></P
-><P
->Other than the current stage of the CUPS development, I don't
-know any other ready-to-use tool which you could consider.</P
-><P
->You can download the driver files from
-<A
-HREF="http://www.cups.org/software.html"
-TARGET="_top"
->http://www.cups.org/software.html</A
->.
-It is a separate package from the CUPS base software files, tagged as "CUPS 1.1.16
-Windows NT/2k/XP Printer Driver for SAMBA (tar.gz, 192k)". The filename to
-download is "cups-samba-1.1.16.tar.gz". Upon untar-/unzip-ping it will reveal
-the files:</P
-><P
-> <SAMP
-CLASS="COMPUTEROUTPUT"
-> cups-samba.install
- cups-samba.license
- cups-samba.readme
- cups-samba.remove
- cups-samba.ss
- </SAMP
->
- </P
-><P
->These have been packaged with the ESP meta packager software "EPM". The
-*.install and *.remove files are simple shell script, which untars the
-*.ss (which is nothing else than a tar-archive) and puts its contents
-into <TT
-CLASS="FILENAME"
->/usr/share/cups/drivers/</TT
->. Its contents are 3 files:</P
-><P
-> <SAMP
-CLASS="COMPUTEROUTPUT"
-> cupsdrvr.dll
- cupsui.dll
- cups.hlp
- </SAMP
->
- </P
-><DIV
-CLASS="CAUTION"
-><P
-></P
-><TABLE
-CLASS="CAUTION"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/caution.gif"
-HSPACE="5"
-ALT="Caution"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->Due to a bug one CUPS release puts the <TT
-CLASS="FILENAME"
->cups.hlp</TT
->
-into <TT
-CLASS="FILENAME"
->/usr/share/drivers/</TT
-> instead of
-<TT
-CLASS="FILENAME"
->/usr/share/cups/drivers/</TT
->. To work around this, copy/move
-the file after running the "./cups-samba.install" script manually to the right place:</P
-><P
-> <KBD
-CLASS="USERINPUT"
-> cp /usr/share/drivers/cups.hlp /usr/share/cups/drivers/
- </KBD
->
- </P
-></TD
-></TR
-></TABLE
-></DIV
-><DIV
-CLASS="NOTE"
-><P
-></P
-><TABLE
-CLASS="NOTE"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->This new CUPS PostScript driver is currently binary-only, but free
-no source code is provided (yet). The reason is this: it has
-been developed with the help of the Microsoft Driver Developer Kit (DDK)
-and compiled with Microsoft Visual Studio 6. It is not clear to the driver
-developers if they are allowed to distribute the whole of the source code
-as Free Software. However, they will likely release the "diff" in source
-code under the GPL, so anybody with a license of Visual Studio and a DDK
-will be able to compile for him/herself.</P
-><P
->Once you have run the install script (and possibly manually moved the
-"cups.hlp" file to "/usr/share/cups/drivers/"), the driver is ready to be
-put into Samba's [print$] share (which often maps to "/etc/samba/drivers/"
-and contains a subdir tree with WIN40 and W32X86 branches), by running
-"cupsaddsmb" (see also "man cupsaddsmb" for CUPS 1.1.16). [Don't forget to
-put root into the smbpasswd file by running "smbpasswd" should you run
-this whole procedure for the first time.] Once the driver files are in the
-[print$] share, they are ready to be downloaded and installed by the
-Win NT/2k/XP clients.</P
-></TD
-></TR
-></TABLE
-></DIV
-><DIV
-CLASS="NOTE"
-><P
-></P
-><TABLE
-CLASS="NOTE"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
-> Win 9x/ME clients won't work with this driver. For these you'd
- still need to use the ADOBE*.* drivers as previously.
- </P
-></TD
-></TR
-></TABLE
-></DIV
-><DIV
-CLASS="NOTE"
-><P
-></P
-><TABLE
-CLASS="NOTE"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
-> It is not harming if you've still the ADOBE*.* driver files from
- previous installations in the "/usr/share/cups/drivers/" directory.
- The new cupsaddsmb (from 1.1.16) will automatically use the
- "newest" installed driver (which here then is the CUPS drivers).
- </P
-></TD
-></TR
-></TABLE
-></DIV
-><DIV
-CLASS="NOTE"
-><P
-></P
-><TABLE
-CLASS="NOTE"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
-> Should your Win clients have had the old ADOBE*.* files and the
- Adobe PostScript drivers installed, the download and installation
- of the new CUPS PostScript driver for Windows NT/2k/XP will fail
- at first.
- </P
-><P
-> It is not enough to "delete" the printer (as the driver files
- will still be kept by the clients and re-used if you try to
- re-install the printer). To really get rid of the Adobe driver
- files on the clients, open the "Printers" folder (possibly via
- "Start --&#62; Settings --&#62; Control Panel --&#62; Printers"), right-click
- onto the folder background and select "Server Properties". A
- new dialog opens; select the "Drivers" tab; on the list select
- the driver you want to delete and click on the "Delete" button.
- (This will only work if there is no single printer left which
- uses that particular driver -- you need to "delete" all printers
- using this driver in the "Printers" folder first.)
- </P
-></TD
-></TR
-></TABLE
-></DIV
-><DIV
-CLASS="NOTE"
-><P
-></P
-><TABLE
-CLASS="NOTE"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
-> Once you have successfully downloaded the CUPS PostScript driver
- to a client, you can easily switch all printers to this one
- by proceeding as described elsewhere in the "Samba HOWTO
- Collection" to change a driver for an existing printer.
- </P
-></TD
-></TR
-></TABLE
-></DIV
-><P
->What are the benefits with the "CUPS PostScript driver for Windows NT/2k/XP"
-as compared to the Adobe drivers?</P
-><P
-><P
-></P
-><UL
-><LI
-><P
-> no hassle with the Adobe EULA
- </P
-></LI
-><LI
-><P
-> no hassle with the question "where do I get the ADOBE*.* driver files from?"
- </P
-></LI
-><LI
-><P
-> the Adobe drivers (depending on the printer PPD associated with them)
- often put a PJL header in front of the core PostScript part of the print
- file (thus the file starts with "<VAR
-CLASS="REPLACEABLE"
->1B</VAR
->%-12345X" or "<VAR
-CLASS="REPLACEABLE"
->escape</VAR
->%-12345X"
- instead of "%!PS"). This leads to the CUPS daemon autotyping the
- arriving file as a print-ready file, not requiring a pass thru the
- "pstops" filter (to speak more technical, it is not regarded as the
- generic MIME type "application/postscript", but as the more special
- MIME type "application/cups.vnd-postscript"), which therefore also
- leads to the page accounting in "/var/log/cups/page_log" not receiving
- the exact mumber of pages; instead the dummy page number of "1" is
- logged in a standard setup)
- </P
-></LI
-><LI
-><P
-> the Adobe driver has more options to "mis-configure" the PostScript
- generated by it (like setting it inadvertedly to "Optimize for Speed",
- instead of "Optimize for Portability", which could lead to CUPS being
- unable to process it)
- </P
-></LI
-><LI
-><P
-> the CUPS PostScript driver output sent by Windows clients to the CUPS
- server will be guaranteed to be auto-typed as generic MIME type
- "application/postscript", thusly passing thru the CUPS "pstops" filter
- and logging the correct number of pages in the page_log for accounting
- and quota purposes
- </P
-></LI
-><LI
-><P
-> the CUPS PostScript driver supports the sending of additional print
- options by the Win NT/2k/XP clients, such as naming the CUPS standard
- banner pages (or the custom ones, should they be installed at the time
- of driver download), using the CUPS "page-label" option, setting a
- job-priority and setting the scheduled time of printing (with the option
- to support additional useful IPP job attributes in the future).
- </P
-></LI
-><LI
-><P
-> the CUPS PostScript driver supports the inclusion of the new
- "*cupsJobTicket" comments at the beginnig of the PostScript file (which
- could be used in the future for all sort of beneficial extensions on
- the CUPS side, but which will not disturb any other application as those
- will regard it as a comment and simply ignore it).
- </P
-></LI
-><LI
-><P
-> the CUPS PostScript driver will be the heart of the fully fledged CUPS
- IPP client for Windows NT/2k/XP to be released soon (probably alongside
- the first Beta release for CUPS 1.2).
- </P
-></LI
-></UL
-></P
-></DIV
-><DIV
-CLASS="SECT1"
-><H1
-CLASS="SECT1"
-><A
-NAME="AEN2424"
->14.11. Advanced Postscript Printing from MS Windows</A
-></H1
-><P
->Let the Windows Clients use a PostScript driver to deliver poistscript to
-the samba print server (just like any Linux or Unix Client would also use
-PostScript to send to the server)</P
-><P
->Make the Unix printing subsystem to which Samba sends the job convert the
-incoming PostScript files to the native print format of the target printers
-(would be PCL if you have an HP printer)</P
-><P
->Now if you are afraid that this would just mean using a *Generic* PostScript
-driver for the clients that has no Simplex/Duplex selection, and no paper tray
-choice, but you need them to be able to set up print jobs, with all the bells
-and whistles of your printers:-</P
-><P
-></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
->Not possible with traditional spooling systems</TD
-></TR
-><TR
-><TD
-> But perfectly supported by CUPS (which uses "PPD" files to
- describe how to control the print options for PostScript and
- non-PostScript devices alike...
- </TD
-></TR
-></TBODY
-></TABLE
-><P
-></P
-><P
->CUPS PPDs are working perfectly on Windows clients who use Adobe PostScript
-drivers (or the new CUPS PostScript driver for Windows NT/2K/XP). Clients can use
-them to setup the job to their liking and CUPS will use the received job options
-to make the (PCL-, ESC/P- or PostScript-) printer behave as required.</P
-><P
->If you want to have the additional benefit of page count logging and accounting
-then the CUPS PostScript driver is the best choice (better than the Adobe one).</P
-><P
->If you want to make the drivers downloadable for the clients then "cupsaddsmb" is
-your friend. It will setup the [print$] share on the Samba host to be ready to serve
-the clients for a "point and print" driver installation.</P
-><DIV
-CLASS="WARNING"
-><P
-></P
-><TABLE
-CLASS="WARNING"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/warning.gif"
-HSPACE="5"
-ALT="Warning"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->What strings are attached?</P
-></TD
-></TR
-></TABLE
-></DIV
-><P
->There are some. But, given the sheer CPU power you can buy nowadays,
-these can be overcome easily. The strings:</P
-><P
->Well, if the CUPS/Samba side will have to print to many printers serving many users,
-you probably will need to set up a second server (which can do automatic load balancing
-with the first one, plus a degree of fail-over mechanism). Converting the incoming
-PostScript jobs, "interpreting" them for non-PostScript printers, amounts to the work
-of a "RIP" (Raster Image Processor) done in software. This requires more CPU and RAM
-than for the mere "raw spooling" task your current setup is solving. It all depends
-on the avarage and peak printing load the server should be able to handle.</P
-></DIV
-><DIV
-CLASS="SECT1"
-><H1
-CLASS="SECT1"
-><A
-NAME="AEN2439"
->14.12. Auto-Deletion of CUPS spool files</A
-></H1
-><P
->Samba print files pass thru two "spool" directories. One the incoming directory
-managed by Samba, (set eg: in the <B
-CLASS="COMMAND"
->path = /var/spool/samba</B
-> directive in the [printers]
-section of <TT
-CLASS="FILENAME"
->smb.conf</TT
->). Second is the spool directory of your UNIX print subsystem.
-For CUPS it is normally "/var/spool/cups/", as set by the cupsd.conf directive
-"RequestRoot /var/spool/cups".</P
-><P
->I am not sure, which one of your directories keeps the files. From what you say,
-it is most likely the Samba part.</P
-><P
->For the CUPS part, you may want to consult:</P
-><P
-></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
->http://localhost:631/sam.html#PreserveJobFiles</TD
-></TR
-><TR
-><TD
->http://localhost:631/sam.html#PreserveJobHistory</TD
-></TR
-><TR
-><TD
->http://localhost:631/sam.html#MaxJobs</TD
-></TR
-></TBODY
-></TABLE
-><P
-></P
-><P
->There are the settings described for your CUPS daemon, which could lead to completed
-job files not being deleted.</P
-><P
->"PreserveJobHistory Yes" -- keeps some details of jobs in
-cupsd's mind (well it keeps the "c12345", "c12346" etc. files
-in the CUPS spool directory, which do a similar job as the
-old-fashioned BSD-LPD control files). This is set to "Yes"
-as a default.</P
-><P
->"PreserveJobFiles Yes" -- keeps the job files themselves in
-cupsd's mind (well it keeps the "d12345", "d12346" etc. files
-in the CUPS spool directory...). This is set to "No" as the
-CUPS default.</P
-><P
->"MaxJobs 500" -- this directive controls the maximum number
-of jobs that are kept in memory. Once the number of jobs
-reaches the limit, the oldest completed job is automatically
-purged from the system to make room for the new one. If all
-of the known jobs are still pending or active then the new
-job will be rejected. Setting the maximum to 0 disables this
-functionality. The default setting is 0.</P
-><P
->(There are also additional settings for "MaxJobsPerUser" and
-"MaxJobsPerPrinter"...)</P
-><P
->For everything to work as announced, you need to have three things:</P
-><P
-></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
-> a Samba-<SPAN
-CLASS="APPLICATION"
->smbd</SPAN
-> which is compiled against "libcups" (Check on Linux by running <KBD
-CLASS="USERINPUT"
->ldd `which smbd`</KBD
->)
- </TD
-></TR
-><TR
-><TD
-> a Samba-<TT
-CLASS="FILENAME"
->smb.conf</TT
-> setting of <B
-CLASS="COMMAND"
->printing = cups</B
->
- </TD
-></TR
-><TR
-><TD
-> another Samba-<TT
-CLASS="FILENAME"
->smb.conf</TT
-> setting of <B
-CLASS="COMMAND"
->printcap = cups</B
->
- </TD
-></TR
-></TBODY
-></TABLE
-><P
-></P
-><DIV
-CLASS="NOTE"
-><P
-></P
-><TABLE
-CLASS="NOTE"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->Note, that in this case all other manually set printing-related
-commands (like "print command", "lpq command", "lprm command",
-"lppause command" or "lpresume command") are ignored and they
-should normally have no influence what-so-ever on your printing.</P
-></TD
-></TR
-></TABLE
-></DIV
-><P
->If you want to do things manually, replace the "printing = cups"
-by "printing = bsd". Then your manually set commands may work
-(haven't tested this), and a "print command = lp -d %P %s; rm %s"
-may do what you need.</P
-><P
->You forgot to mention the CUPS version you're using. If you did
-set things up as described in the man pages, then the Samba
-spool files should be deleted. Otherwise it may be a bug. On
-the CUPS side, you can control the behaviour as described
-above.</P
-><P
->If you have more problems, post the output of these commands:</P
-><P
-><KBD
-CLASS="USERINPUT"
-> grep -v ^# /etc/cups/cupsd.conf | grep -v ^$
- grep -v ^# /etc/samba/smb.conf | grep -v ^$ | grep -v "^;"</KBD
-></P
-><P
->(adapt paths as needed). These commands sanitize the files
-and cut out the empty lines and lines with comments, providing
-the "naked settings" in a compact way.</P
-></DIV
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="printing.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="samba-howto-collection.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="winbind.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Printing Support</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="optional.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Unified Logons between Windows NT and UNIX using Winbind</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
-> \ No newline at end of file
diff --git a/docs/htmldocs/cvs-access.html b/docs/htmldocs/cvs-access.html
new file mode 100644
index 0000000000..73cd333805
--- /dev/null
+++ b/docs/htmldocs/cvs-access.html
@@ -0,0 +1,298 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<HTML
+><HEAD
+><TITLE
+>HOWTO Access Samba source code via CVS</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
+REL="HOME"
+TITLE="SAMBA Project Documentation"
+HREF="samba-howto-collection.html"><LINK
+REL="UP"
+TITLE="Optional configuration"
+HREF="optional.html"><LINK
+REL="PREVIOUS"
+TITLE="Storing Samba's User/Machine Account information in an LDAP Directory"
+HREF="samba-ldap-howto.html"><LINK
+REL="NEXT"
+TITLE="Group mapping HOWTO"
+HREF="groupmapping.html"></HEAD
+><BODY
+CLASS="CHAPTER"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><TABLE
+SUMMARY="Header navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>SAMBA Project Documentation</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="samba-ldap-howto.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+></TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="groupmapping.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="CHAPTER"
+><H1
+><A
+NAME="CVS-ACCESS">Chapter 20. HOWTO Access Samba source code via CVS</H1
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN2964">20.1. Introduction</H1
+><P
+>Samba is developed in an open environment. Developers use CVS
+(Concurrent Versioning System) to "checkin" (also known as
+"commit") new source code. Samba's various CVS branches can
+be accessed via anonymous 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"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN2969">20.2. CVS Access to samba.org</H1
+><P
+>The machine samba.org runs a publicly accessible CVS
+repository for access to the source code of several packages,
+including samba, rsync and jitterbug. There are two main ways of
+accessing the CVS server on this host.</P
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN2972">20.2.1. Access via CVSweb</H2
+><P
+>You can access the source code via your
+favourite WWW browser. This allows you to access the contents of
+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"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN2977">20.2.2. Access via cvs</H2
+><P
+>You can also access the source code via a
+normal cvs client. This gives you much more control over you can
+do with the repository and allows you to checkout whole source trees
+and keep them up to date 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
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+SUMMARY="Footer navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="samba-ldap-howto.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="samba-howto-collection.html"
+ACCESSKEY="H"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="groupmapping.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>Storing Samba's User/Machine Account information in an LDAP Directory</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="optional.html"
+ACCESSKEY="U"
+>Up</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>Group mapping HOWTO</TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+> \ No newline at end of file
diff --git a/docs/htmldocs/diagnosis.html b/docs/htmldocs/diagnosis.html
index 35c0ea11ac..a7b2e59436 100644
--- a/docs/htmldocs/diagnosis.html
+++ b/docs/htmldocs/diagnosis.html
@@ -1,303 +1,627 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter27.The samba checklist</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"><link rel="home" href="index.html" title="SAMBA Project Documentation"><link rel="up" href="troubleshooting.html" title="PartIV.Troubleshooting"><link rel="previous" href="troubleshooting.html" title="PartIV.Troubleshooting"><link rel="next" href="problems.html" title="Chapter28.Analysing and solving samba problems"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter27.The samba checklist</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="troubleshooting.html">Prev</a></td><th width="60%" align="center">PartIV.Troubleshooting</th><td width="20%" align="right"><a accesskey="n" href="problems.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="diagnosis"></a>Chapter27.The samba checklist</h2></div><div><div class="author"><h3 class="author">Andrew Tridgell</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt>&lt;<a href="mailto:tridge@samba.org">tridge@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author">Jelmer R. Vernooij</h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt>&lt;<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate">Wed Jan 15</p></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="diagnosis.html#id2901594">Introduction</a></dt><dt><a href="diagnosis.html#id2901628">Assumptions</a></dt><dt><a href="diagnosis.html#id2902640">The tests</a></dt><dt><a href="diagnosis.html#id2903749">Still having troubles?</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2901594"></a>Introduction</h2></div></div><p>
-This file contains a list of tests you can perform to validate your
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<HTML
+><HEAD
+><TITLE
+>Diagnosing your samba server</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
+REL="HOME"
+TITLE="SAMBA Project Documentation"
+HREF="samba-howto-collection.html"><LINK
+REL="UP"
+TITLE="Appendixes"
+HREF="appendixes.html"><LINK
+REL="PREVIOUS"
+TITLE="Reporting Bugs"
+HREF="bugreport.html"></HEAD
+><BODY
+CLASS="CHAPTER"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><TABLE
+SUMMARY="Header navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>SAMBA Project Documentation</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="bugreport.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+></TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+>&nbsp;</TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="CHAPTER"
+><H1
+><A
+NAME="DIAGNOSIS">Chapter 26. Diagnosing your samba server</H1
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN3378">26.1. Introduction</H1
+><P
+>This file contains a list of tests you can perform to validate your
Samba server. It also tells you what the likely cause of the problem
is if it fails any one of these steps. If it passes all these tests
-then it is probably working fine.
-</p><p>
-You should do ALL the tests, in the order shown. We have tried to
+then it is probably working fine.</P
+><P
+>You should do ALL the tests, in the order shown. We have tried to
carefully choose them so later tests only use capabilities verified in
-the earlier tests. However, do not stop at the first error as there
-have been some instances when continuing with the tests has helped
-to solve a problem.
-</p><p>
-If you send one of the samba mailing lists an email saying &quot;it doesn't work&quot;
+the earlier tests.</P
+><P
+>If you send one of the samba mailing lists an email saying "it doesn't work"
and you have not followed this test procedure then you should not be surprised
-if your email is ignored.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2901628"></a>Assumptions</h2></div></div><p>
-In all of the tests it is assumed you have a Samba server called
-BIGSERVER and a PC called ACLIENT both in workgroup TESTGROUP.
-</p><p>
-The procedure is similar for other types of clients.
-</p><p>
-It is also assumed you know the name of an available share in your
-<tt>smb.conf</tt>. I will assume this share is called <i><tt>tmp</tt></i>.
-You can add a <i><tt>tmp</tt></i> share like this by adding the
-following to <tt>smb.conf</tt>:
-</p><pre class="programlisting">
-
-[tmp]
+your email is ignored.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN3383">26.2. Assumptions</H1
+><P
+>In all of the tests it is assumed you have a Samba server called
+BIGSERVER and a PC called ACLIENT both in workgroup TESTGROUP.</P
+><P
+>The procedure is similar for other types of clients.</P
+><P
+>It is also assumed you know the name of an available share in your
+smb.conf. I will assume this share is called "tmp". You can add a
+"tmp" share like by adding the following to smb.conf:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>&#13;[tmp]
comment = temporary files
path = /tmp
- read only = yes
-
-</pre><p>
-</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-These tests assume version 3.0 or later of the samba suite.
-Some commands shown did not exist in earlier versions.
-</p></div><p>
-Please pay attention to the error messages you receive. If any error message
-reports that your server is being unfriendly you should first check that your
-IP name resolution is correctly set up. eg: Make sure your <tt>/etc/resolv.conf</tt>
-file points to name servers that really do exist.
-</p><p>
-Also, if you do not have DNS server access for name resolution please check
-that the settings for your <tt>smb.conf</tt> file results in <b>dns proxy = no</b>. The
-best way to check this is with <b><tt>testparm smb.conf</tt></b>.
-</p><p>
-It is helpful to monitor the log files during testing by using the
-<b>tail -F <i><tt>log_file_name</tt></i></b> in a separate
-terminal console (use ctrl-alt-F1 through F6 or multiple terminals in X).
-Relevant log files can be found (for default installations) in
-<tt>/usr/local/samba/var</tt>. Also, connection logs from
-machines can be found here or possibly in <tt>/var/log/samba</tt>
-depending on how or if you specified logging in your <tt>smb.conf</tt> file.
-</p><p>
-If you make changes to your <tt>smb.conf</tt> file while going through these test,
-don't forget to restart smbd and nmbd.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2902640"></a>The tests</h2></div></div><div class="procedure"><p class="title"><b>Procedure27.1.Diagnosing your samba server</b></p><ol type="1"><li><p>
-In the directory in which you store your <tt>smb.conf</tt> file, run the command
-<b><tt>testparm smb.conf</tt></b>. If it reports any errors then your <tt>smb.conf</tt>
-configuration file is faulty.
-</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-Your <tt>smb.conf</tt> file may be located in: <tt>/etc/samba</tt>
-Or in: <tt>/usr/local/samba/lib</tt>
-</p></div></li><li><p>
-Run the command <b><tt>ping BIGSERVER</tt></b> from the PC and
-<b><tt>ping ACLIENT</tt></b> from
+ read only = yes&#13;</PRE
+></P
+><P
+>THESE TESTS ASSUME VERSION 3.0.0 OR LATER OF THE SAMBA SUITE. SOME
+COMMANDS SHOWN DID NOT EXIST IN EARLIER VERSIONS</P
+><P
+>Please pay attention to the error messages you receive. If any error message
+reports that your server is being unfriendly you should first check that you
+IP name resolution is correctly set up. eg: Make sure your /etc/resolv.conf
+file points to name servers that really do exist.</P
+><P
+>Also, if you do not have DNS server access for name resolution please check
+that the settings for your smb.conf file results in "dns proxy = no". The
+best way to check this is with "testparm smb.conf"</P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN3393">26.3. Tests</H1
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN3395">26.3.1. Test 1</H2
+><P
+>In the directory in which you store your smb.conf file, run the command
+"testparm smb.conf". If it reports any errors then your smb.conf
+configuration file is faulty.</P
+><P
+>Note: Your smb.conf file may be located in: <TT
+CLASS="FILENAME"
+>/etc/samba</TT
+>
+ Or in: <TT
+CLASS="FILENAME"
+>/usr/local/samba/lib</TT
+></P
+></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN3401">26.3.2. Test 2</H2
+><P
+>Run the command "ping BIGSERVER" from the PC and "ping ACLIENT" from
the unix box. If you don't get a valid response then your TCP/IP
-software is not correctly installed.
-</p><p>
-Note that you will need to start a &quot;dos prompt&quot; window on the PC to
-run ping.
-</p><p>
-If you get a message saying &quot;host not found&quot; or similar then your DNS
-software or <tt>/etc/hosts</tt> file is not correctly setup.
-It is possible to
+software is not correctly installed. </P
+><P
+>Note that you will need to start a "dos prompt" window on the PC to
+run ping.</P
+><P
+>If you get a message saying "host not found" or similar then your DNS
+software or /etc/hosts file is not correctly setup. It is possible to
run samba without DNS entries for the server and client, but I assume
-you do have correct entries for the remainder of these tests.
-</p><p>
-Another reason why ping might fail is if your host is running firewall
+you do have correct entries for the remainder of these tests. </P
+><P
+>Another reason why ping might fail is if your host is running firewall
software. You will need to relax the rules to let in the workstation
in question, perhaps by allowing access from another subnet (on Linux
-this is done via the ipfwadm program.)
-</p><p>
-Note: Modern Linux distributions install ipchains/iptables by default.
-This is a common problem that is often overlooked.
-</p></li><li><p>
-Run the command <b><tt>smbclient -L BIGSERVER</tt></b> on the unix box. You
-should get a list of available shares back.
-</p><p>
-If you get a error message containing the string &quot;Bad password&quot; then
-you probably have either an incorrect <b>hosts allow</b>,
-<b>hosts deny</b> or <b>valid users</b> line in your
-<tt>smb.conf</tt>, or your guest account is not
-valid. Check what your guest account is using testparm and
-temporarily remove any <b>hosts allow</b>, <b>hosts deny</b>, <b>valid users</b> or <b>invalid users</b> lines.
-</p><p>
-If you get a &quot;connection refused&quot; response then the smbd server may
+this is done via the ipfwadm program.)</P
+></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN3407">26.3.3. Test 3</H2
+><P
+>Run the command "smbclient -L BIGSERVER" on the unix box. You
+should get a list of available shares back. </P
+><P
+>If you get a error message containing the string "Bad password" then
+you probably have either an incorrect "hosts allow", "hosts deny" or
+"valid users" line in your smb.conf, or your guest account is not
+valid. Check what your guest account is using "testparm" and
+temporarily remove any "hosts allow", "hosts deny", "valid users" or
+"invalid users" lines.</P
+><P
+>If you get a "connection refused" response then the smbd server may
not be running. If you installed it in inetd.conf then you probably edited
that file incorrectly. If you installed it as a daemon then check that
it is running, and check that the netbios-ssn port is in a LISTEN
-state using <b><tt>netstat -a</tt></b>.
-</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-Some Unix / Linux systems use <b>xinetd</b> in place of
-<b>inetd</b>. Check your system documentation for the location
-of the control file/s for your particular system implementation of
-this network super daemon.
-</p></div><p>
-If you get a &quot;session request failed&quot; then the server refused the
-connection. If it says &quot;Your server software is being unfriendly&quot; then
+state using "netstat -a".</P
+><P
+>If you get a "session request failed" then the server refused the
+connection. If it says "Your server software is being unfriendly" then
its probably because you have invalid command line parameters to smbd,
or a similar fatal problem with the initial startup of smbd. Also
-check your config file (<tt>smb.conf</tt>) for syntax errors with testparm
+check your config file (smb.conf) for syntax errors with "testparm"
and that the various directories where samba keeps its log and lock
-files exist.
-</p><p>
-There are a number of reasons for which smbd may refuse or decline
+files exist.</P
+><P
+>There are a number of reasons for which smbd may refuse or decline
a session request. The most common of these involve one or more of
-the following <tt>smb.conf</tt> file entries:
-</p><pre class="programlisting">
- hosts deny = ALL
+the following smb.conf file entries:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+> hosts deny = ALL
hosts allow = xxx.xxx.xxx.xxx/yy
- bind interfaces only = Yes
-</pre><p>
-In the above, no allowance has been made for any session requests that
+ bind interfaces only = Yes</PRE
+></P
+><P
+>In the above, no allowance has been made for any session requests that
will automatically translate to the loopback adaptor address 127.0.0.1.
-To solve this problem change these lines to:
-</p><pre class="programlisting">
- hosts deny = ALL
- hosts allow = xxx.xxx.xxx.xxx/yy 127.
-</pre><p>
-Do NOT use the <b>bind interfaces only</b> parameter where you
-may wish to
+To solve this problem change these lines to:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+> hosts deny = ALL
+ hosts allow = xxx.xxx.xxx.xxx/yy 127.</PRE
+></P
+><P
+>Do NOT use the "bind interfaces only" parameter where you may wish to
use the samba password change facility, or where smbclient may need to
-access a local service for name resolution or for local resource
-connections. (Note: the <b>bind interfaces only</b> parameter deficiency
+access local service for name resolution or for local resource
+connections. (Note: the "bind interfaces only" parameter deficiency
where it will not allow connections to the loopback address will be
-fixed soon).
-</p><p>
-Another common cause of these two errors is having something already running
+fixed soon).</P
+><P
+>Another common cause of these two errors is having something already running
on port 139, such as Samba (ie: smbd is running from inetd already) or
-something like Digital's Pathworks. Check your <tt>inetd.conf</tt> file before trying
-to start smbd as a daemon, it can avoid a lot of frustration!
-</p><p>
-And yet another possible cause for failure of this test is when the subnet mask
+something like Digital's Pathworks. Check your inetd.conf file before trying
+to start smbd as a daemon, it can avoid a lot of frustration!</P
+><P
+>And yet another possible cause for failure of TEST 3 is when the subnet mask
and / or broadcast address settings are incorrect. Please check that the
network interface IP Address / Broadcast Address / Subnet Mask settings are
-correct and that Samba has correctly noted these in the <tt>log.nmb</tt> file.
-</p></li><li><p>
-Run the command <b><tt>nmblookup -B BIGSERVER __SAMBA__</tt></b>. You should get the
-IP address of your Samba server back.
-</p><p>
-If you don't then nmbd is incorrectly installed. Check your <tt>inetd.conf</tt>
+correct and that Samba has correctly noted these in the log.nmb file.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN3422">26.3.4. Test 4</H2
+><P
+>Run the command "nmblookup -B BIGSERVER __SAMBA__". You should get the
+IP address of your Samba server back.</P
+><P
+>If you don't then nmbd is incorrectly installed. Check your inetd.conf
if you run it from there, or that the daemon is running and listening
-to udp port 137.
-</p><p>
-One common problem is that many inetd implementations can't take many
+to udp port 137.</P
+><P
+>One common problem is that many inetd implementations can't take many
parameters on the command line. If this is the case then create a
one-line script that contains the right parameters and run that from
-inetd.
-</p></li><li><p>run the command <b><tt>nmblookup -B ACLIENT '*'</tt></b></p><p>
-You should get the PCs IP address back. If you don't then the client
+inetd.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN3427">26.3.5. Test 5</H2
+><P
+>run the command <B
+CLASS="COMMAND"
+>nmblookup -B ACLIENT '*'</B
+></P
+><P
+>You should get the PCs IP address back. If you don't then the client
software on the PC isn't installed correctly, or isn't started, or you
-got the name of the PC wrong.
-</p><p>
-If ACLIENT doesn't resolve via DNS then use the IP address of the
-client in the above test.
-</p></li><li><p>
-Run the command <b><tt>nmblookup -d 2 '*'</tt></b>
-</p><p>
-This time we are trying the same as the previous test but are trying
+got the name of the PC wrong. </P
+><P
+>If ACLIENT doesn't resolve via DNS then use the IP address of the
+client in the above test.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN3433">26.3.6. Test 6</H2
+><P
+>Run the command <B
+CLASS="COMMAND"
+>nmblookup -d 2 '*'</B
+></P
+><P
+>This time we are trying the same as the previous test but are trying
it via a broadcast to the default broadcast address. A number of
Netbios/TCPIP hosts on the network should respond, although Samba may
not catch all of the responses in the short time it listens. You
-should see &quot;got a positive name query response&quot; messages from several
-hosts.
-</p><p>
-If this doesn't give a similar result to the previous test then
+should see "got a positive name query response" messages from several
+hosts.</P
+><P
+>If this doesn't give a similar result to the previous test then
nmblookup isn't correctly getting your broadcast address through its
-automatic mechanism. In this case you should experiment with the
-<b>interfaces</b> option in <tt>smb.conf</tt> to manually configure your IP
-address, broadcast and netmask.
-</p><p>
-If your PC and server aren't on the same subnet then you will need to
-use the <i><tt>-B</tt></i> option to set the broadcast address to that of the PCs
-subnet.
-</p><p>
-This test will probably fail if your subnet mask and broadcast address are
-not correct. (Refer to TEST 3 notes above).
-</p></li><li><p>
-Run the command <b><tt>smbclient //BIGSERVER/TMP</tt></b>. You should
+automatic mechanism. In this case you should experiment use the
+"interfaces" option in smb.conf to manually configure your IP
+address, broadcast and netmask. </P
+><P
+>If your PC and server aren't on the same subnet then you will need to
+use the -B option to set the broadcast address to the that of the PCs
+subnet.</P
+><P
+>This test will probably fail if your subnet mask and broadcast address are
+not correct. (Refer to TEST 3 notes above).</P
+></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN3441">26.3.7. Test 7</H2
+><P
+>Run the command <B
+CLASS="COMMAND"
+>smbclient //BIGSERVER/TMP</B
+>. You should
then be prompted for a password. You should use the password of the account
you are logged into the unix box with. If you want to test with
-another account then add the <i><tt>-U <i><tt>accountname</tt></i></tt></i> option to the end of
+another account then add the -U &gt;accountname&lt; option to the end of
the command line. eg:
-<b><tt>smbclient //bigserver/tmp -Ujohndoe</tt></b>
-</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-It is possible to specify the password along with the username
+<B
+CLASS="COMMAND"
+>smbclient //bigserver/tmp -Ujohndoe</B
+></P
+><P
+>Note: It is possible to specify the password along with the username
as follows:
-<b><tt>smbclient //bigserver/tmp -Ujohndoe%secret</tt></b>
-</p></div><p>
-Once you enter the password you should get the <tt>smb&gt;</tt> prompt. If you
-don't then look at the error message. If it says &quot;invalid network
-name&quot; then the service &quot;tmp&quot; is not correctly setup in your <tt>smb.conf</tt>.
-</p><p>
-If it says &quot;bad password&quot; then the likely causes are:
-</p><div class="orderedlist"><ol type="1"><li><p>
- you have shadow passords (or some other password system) but didn't
+<B
+CLASS="COMMAND"
+>smbclient //bigserver/tmp -Ujohndoe%secret</B
+></P
+><P
+>Once you enter the password you should get the "smb&#62;" prompt. If you
+don't then look at the error message. If it says "invalid network
+name" then the service "tmp" is not correctly setup in your smb.conf.</P
+><P
+>If it says "bad password" then the likely causes are:</P
+><P
+></P
+><OL
+TYPE="1"
+><LI
+><P
+> you have shadow passords (or some other password system) but didn't
compile in support for them in smbd
- </p></li><li><p>
- your <b>valid users</b> configuration is incorrect
- </p></li><li><p>
- you have a mixed case password and you haven't enabled the <b>password
- level</b> option at a high enough level
- </p></li><li><p>
- the <b>path =</b> line in <tt>smb.conf</tt> is incorrect. Check it with testparm
- </p></li><li><p>
- you enabled password encryption but didn't create the SMB encrypted
+ </P
+></LI
+><LI
+><P
+> your "valid users" configuration is incorrect
+ </P
+></LI
+><LI
+><P
+> you have a mixed case password and you haven't enabled the "password
+ level" option at a high enough level
+ </P
+></LI
+><LI
+><P
+> the "path =" line in smb.conf is incorrect. Check it with testparm
+ </P
+></LI
+><LI
+><P
+> you enabled password encryption but didn't create the SMB encrypted
password file
- </p></li></ol></div><p>
-Once connected you should be able to use the commands
-<b>dir</b> <b>get</b> <b>put</b> etc.
-Type <b>help <i><tt>command</tt></i></b> for instructions. You should
+ </P
+></LI
+></OL
+><P
+>Once connected you should be able to use the commands
+<B
+CLASS="COMMAND"
+>dir</B
+> <B
+CLASS="COMMAND"
+>get</B
+> <B
+CLASS="COMMAND"
+>put</B
+> etc.
+Type <B
+CLASS="COMMAND"
+>help &gt;command&lt;</B
+> for instructions. You should
especially check that the amount of free disk space shown is correct
-when you type <b>dir</b>.
-</p></li><li><p>
-On the PC, type the command <b><tt>net view \\BIGSERVER</tt></b>. You will
-need to do this from within a &quot;dos prompt&quot; window. You should get back a
-list of available shares on the server.
-</p><p>
-If you get a &quot;network name not found&quot; or similar error then netbios
+when you type <B
+CLASS="COMMAND"
+>dir</B
+>.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN3467">26.3.8. Test 8</H2
+><P
+>On the PC type the command <B
+CLASS="COMMAND"
+>net view \\BIGSERVER</B
+>. You will
+need to do this from within a "dos prompt" window. You should get back a
+list of available shares on the server.</P
+><P
+>If you get a "network name not found" or similar error then netbios
name resolution is not working. This is usually caused by a problem in
nmbd. To overcome it you could do one of the following (you only need
-to choose one of them):
-</p><div class="orderedlist"><ol type="1"><li><p>
- fixup the nmbd installation
-</p></li><li><p>
- add the IP address of BIGSERVER to the <b>wins server</b> box in the
- advanced tcp/ip setup on the PC.
-</p></li><li><p>
- enable windows name resolution via DNS in the advanced section of
- the tcp/ip setup
-</p></li><li><p>
- add BIGSERVER to your lmhosts file on the PC.
-</p></li></ol></div><p>
-If you get a &quot;invalid network name&quot; or &quot;bad password error&quot; then the
-same fixes apply as they did for the <b><tt>smbclient -L</tt></b> test above. In
-particular, make sure your <b>hosts allow</b> line is correct (see the man
-pages)
-</p><p>
-Also, do not overlook that fact that when the workstation requests the
+to choose one of them):</P
+><P
+></P
+><OL
+TYPE="1"
+><LI
+><P
+> fixup the nmbd installation</P
+></LI
+><LI
+><P
+> add the IP address of BIGSERVER to the "wins server" box in the
+ advanced tcp/ip setup on the PC.</P
+></LI
+><LI
+><P
+> enable windows name resolution via DNS in the advanced section of
+ the tcp/ip setup</P
+></LI
+><LI
+><P
+> add BIGSERVER to your lmhosts file on the PC.</P
+></LI
+></OL
+><P
+>If you get a "invalid network name" or "bad password error" then the
+same fixes apply as they did for the "smbclient -L" test above. In
+particular, make sure your "hosts allow" line is correct (see the man
+pages)</P
+><P
+>Also, do not overlook that fact that when the workstation requests the
connection to the samba server it will attempt to connect using the
name with which you logged onto your Windows machine. You need to make
sure that an account exists on your Samba server with that exact same
-name and password.
-</p><p>
-If you get &quot;specified computer is not receiving requests&quot; or similar
+name and password.</P
+><P
+>If you get "specified computer is not receiving requests" or similar
it probably means that the host is not contactable via tcp services.
Check to see if the host is running tcp wrappers, and if so add an entry in
-the <tt>hosts.allow</tt> file for your client (or subnet, etc.)
-</p></li><li><p>
-Run the command <b><tt>net use x: \\BIGSERVER\TMP</tt></b>. You should
-be prompted for a password then you should get a &quot;command completed
-successfully&quot; message. If not then your PC software is incorrectly
-installed or your smb.conf is incorrect. make sure your <b>hosts allow</b>
-and other config lines in <tt>smb.conf</tt> are correct.
-</p><p>
-It's also possible that the server can't work out what user name to
-connect you as. To see if this is the problem add the line <b>user =
-<i><tt>username</tt></i></b> to the <b>[tmp]</b> section of
-<tt>smb.conf</tt> where <i><tt>username</tt></i> is the
+the hosts.allow file for your client (or subnet, etc.)</P
+></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN3484">26.3.9. Test 9</H2
+><P
+>Run the command <B
+CLASS="COMMAND"
+>net use x: \\BIGSERVER\TMP</B
+>. You should
+be prompted for a password then you should get a "command completed
+successfully" message. If not then your PC software is incorrectly
+installed or your smb.conf is incorrect. make sure your "hosts allow"
+and other config lines in smb.conf are correct.</P
+><P
+>It's also possible that the server can't work out what user name to
+connect you as. To see if this is the problem add the line "user =
+USERNAME" to the [tmp] section of smb.conf where "USERNAME" is the
username corresponding to the password you typed. If you find this
-fixes things you may need the username mapping option.
-</p><p>
-It might also be the case that your client only sends encrypted passwords
-and you have <b>encrypt passwords = no</b> in <tt>smb.conf</tt>
-Turn it back on to fix.
-</p></li><li><p>
-Run the command <b><tt>nmblookup -M <i><tt>testgroup</tt></i></tt></b> where
-<i><tt>testgroup</tt></i> is the name of the workgroup that your Samba server and
+fixes things you may need the username mapping option. </P
+><P
+>It might also be the case that your client only sends encrypted passwords
+and you have <B
+CLASS="COMMAND"
+>encrypt passwords = no</B
+> in <TT
+CLASS="FILENAME"
+>smb.conf</TT
+>.
+Turn it back on to fix.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN3492">26.3.10. Test 10</H2
+><P
+>Run the command <B
+CLASS="COMMAND"
+>nmblookup -M TESTGROUP</B
+> where
+TESTGROUP is the name of the workgroup that your Samba server and
Windows PCs belong to. You should get back the IP address of the
-master browser for that workgroup.
-</p><p>
-If you don't then the election process has failed. Wait a minute to
+master browser for that workgroup.</P
+><P
+>If you don't then the election process has failed. Wait a minute to
see if it is just being slow then try again. If it still fails after
-that then look at the browsing options you have set in <tt>smb.conf</tt>. Make
-sure you have <b>preferred master = yes</b> to ensure that
-an election is held at startup.
-</p></li><li><p>
-&gt;From file manager try to browse the server. Your samba server should
+that then look at the browsing options you have set in smb.conf. Make
+sure you have <B
+CLASS="COMMAND"
+>preferred master = yes</B
+> to ensure that
+an election is held at startup.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN3498">26.3.11. Test 11</H2
+><P
+>From file manager try to browse the server. Your samba server should
appear in the browse list of your local workgroup (or the one you
specified in smb.conf). You should be able to double click on the name
-of the server and get a list of shares. If you get a &quot;invalid
-password&quot; error when you do then you are probably running WinNT and it
+of the server and get a list of shares. If you get a "invalid
+password" error when you do then you are probably running WinNT and it
is refusing to browse a server that has no encrypted password
capability and is in user level security mode. In this case either set
-<b>security = server</b> AND
-<b>password server = Windows_NT_Machine</b> in your
-<tt>smb.conf</tt> file, or make sure <b>encrypted passwords</b> is
-set to &quot;yes&quot;.
-</p></li></ol></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2903749"></a>Still having troubles?</h2></div></div><p>Read the chapter on
-<a href="problems.html" title="Chapter28.Analysing and solving samba problems">Analysing and Solving Problems</a>.
-</p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="troubleshooting.html">Prev</a></td><td width="20%" align="center"><a accesskey="u" href="troubleshooting.html">Up</a></td><td width="40%" align="right"><a accesskey="n" href="problems.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">PartIV.Troubleshooting</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">Chapter28.Analysing and solving samba problems</td></tr></table></div></body></html>
+<B
+CLASS="COMMAND"
+>security = server</B
+> AND
+<B
+CLASS="COMMAND"
+>password server = Windows_NT_Machine</B
+> in your
+smb.conf file, or enable encrypted passwords AFTER compiling in support
+for encrypted passwords (refer to the Makefile).</P
+></DIV
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN3503">26.4. Still having troubles?</H1
+><P
+>Try the mailing list or newsgroup, or use the ethereal utility to
+sniff the problem. The official samba mailing list can be reached at
+<A
+HREF="mailto:samba@samba.org"
+TARGET="_top"
+>samba@samba.org</A
+>. To find
+out more about samba and how to subscribe to the mailing list check
+out the samba web page at
+<A
+HREF="http://samba.org/samba"
+TARGET="_top"
+>http://samba.org/samba</A
+></P
+><P
+>Also look at the other docs in the Samba package!</P
+></DIV
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+SUMMARY="Footer navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="bugreport.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="samba-howto-collection.html"
+ACCESSKEY="H"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>&nbsp;</TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>Reporting Bugs</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="appendixes.html"
+ACCESSKEY="U"
+>Up</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>&nbsp;</TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+> \ No newline at end of file
diff --git a/docs/htmldocs/domain-security.html b/docs/htmldocs/domain-security.html
index ddbc4624b8..670d96ba5f 100644
--- a/docs/htmldocs/domain-security.html
+++ b/docs/htmldocs/domain-security.html
@@ -2,10 +2,11 @@
<HTML
><HEAD
><TITLE
->Samba as a NT4 or Win2k domain member</TITLE
+>Samba as a NT4 domain member</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
REL="HOME"
TITLE="SAMBA Project Documentation"
HREF="samba-howto-collection.html"><LINK
@@ -16,7 +17,7 @@ REL="PREVIOUS"
TITLE="Samba as a ADS domain member"
HREF="ads.html"><LINK
REL="NEXT"
-TITLE="Advanced Configuration"
+TITLE="Optional configuration"
HREF="optional.html"></HEAD
><BODY
CLASS="CHAPTER"
@@ -72,58 +73,157 @@ WIDTH="100%"></DIV
CLASS="CHAPTER"
><H1
><A
-NAME="DOMAIN-SECURITY"
-></A
->Chapter 9. Samba as a NT4 or Win2k domain member</H1
+NAME="DOMAIN-SECURITY">Chapter 9. Samba as a NT4 domain member</H1
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="AEN1439"
->9.1. Joining an NT Domain with Samba 3.0</A
-></H1
+NAME="AEN1273">9.1. Joining an NT Domain with Samba 2.2</H1
><P
->Assume you have a Samba 3.0 server with a NetBIOS name of
- <CODE
+>Assume you have a Samba 2.x server with a NetBIOS name of
+ <TT
CLASS="CONSTANT"
->SERV1</CODE
-> and are joining an or Win2k NT domain called
- <CODE
+>SERV1</TT
+> and are joining an NT domain called
+ <TT
CLASS="CONSTANT"
->DOM</CODE
+>DOM</TT
>, which has a PDC with a NetBIOS name
- of <CODE
+ of <TT
CLASS="CONSTANT"
->DOMPDC</CODE
+>DOMPDC</TT
> and two backup domain controllers
- with NetBIOS names <CODE
+ with NetBIOS names <TT
CLASS="CONSTANT"
->DOMBDC1</CODE
-> and <CODE
+>DOMBDC1</TT
+> and <TT
CLASS="CONSTANT"
>DOMBDC2
- </CODE
+ </TT
>.</P
><P
->Firstly, you must edit your <TT
+>In order to join the domain, first stop all Samba daemons
+ and run the command:</P
+><P
+><TT
+CLASS="PROMPT"
+>root# </TT
+><TT
+CLASS="USERINPUT"
+><B
+>smbpasswd -j DOM -r DOMPDC
+ -U<TT
+CLASS="REPLACEABLE"
+><I
+>Administrator%password</I
+></TT
+></B
+></TT
+></P
+><P
+>as we are joining the domain DOM and the PDC for that domain
+ (the only machine that has write access to the domain SAM database)
+ is DOMPDC. The <TT
+CLASS="REPLACEABLE"
+><I
+>Administrator%password</I
+></TT
+> is
+ the login name and password for an account which has the necessary
+ privilege to add machines to the domain. If this is successful
+ you will see the message:</P
+><P
+><TT
+CLASS="COMPUTEROUTPUT"
+>smbpasswd: Joined domain DOM.</TT
+>
+ </P
+><P
+>in your terminal window. See the <A
+HREF="smbpasswd.8.html"
+TARGET="_top"
+> smbpasswd(8)</A
+> man page for more details.</P
+><P
+>There is existing development code to join a domain
+ without having to create the machine trust account on the PDC
+ beforehand. This code will hopefully be available soon
+ in release branches as well.</P
+><P
+>This command goes through the machine account password
+ change protocol, then writes the new (random) machine account
+ password for this Samba server into a file in the same directory
+ in which an smbpasswd file would be stored - normally :</P
+><P
+><TT
+CLASS="FILENAME"
+>/usr/local/samba/private</TT
+></P
+><P
+>In Samba 2.0.x, the filename looks like this:</P
+><P
+><TT
CLASS="FILENAME"
->smb.conf</TT
-> file to tell Samba it should
- now use domain security.</P
+><TT
+CLASS="REPLACEABLE"
+><I
+>&lt;NT DOMAIN NAME&gt;</I
+></TT
+>.<TT
+CLASS="REPLACEABLE"
+><I
+>&lt;Samba
+ Server Name&gt;</I
+></TT
+>.mac</TT
+></P
+><P
+>The <TT
+CLASS="FILENAME"
+>.mac</TT
+> suffix stands for machine account
+ password file. So in our example above, the file would be called:</P
+><P
+><TT
+CLASS="FILENAME"
+>DOM.SERV1.mac</TT
+></P
+><P
+>In Samba 2.2, this file has been replaced with a TDB
+ (Trivial Database) file named <TT
+CLASS="FILENAME"
+>secrets.tdb</TT
+>.
+ </P
+><P
+>This file is created and owned by root and is not
+ readable by any other user. It is the key to the domain-level
+ security for your system, and should be treated as carefully
+ as a shadow password file.</P
+><P
+>Now, before restarting the Samba daemons you must
+ edit your <A
+HREF="smb.conf.5.html"
+TARGET="_top"
+><TT
+CLASS="FILENAME"
+>smb.conf(5)</TT
+>
+ </A
+> file to tell Samba it should now use domain security.</P
><P
>Change (or add) your <A
HREF="smb.conf.5.html#SECURITY"
TARGET="_top"
-> <VAR
+> <TT
CLASS="PARAMETER"
->security =</VAR
+><I
+>security =</I
+></TT
></A
> line in the [global] section
- of your <TT
-CLASS="FILENAME"
->smb.conf</TT
-> to read:</P
+ of your smb.conf to read:</P
><P
><B
CLASS="COMMAND"
@@ -133,9 +233,11 @@ CLASS="COMMAND"
>Next change the <A
HREF="smb.conf.5.html#WORKGROUP"
TARGET="_top"
-><VAR
+><TT
CLASS="PARAMETER"
-> workgroup =</VAR
+><I
+> workgroup =</I
+></TT
></A
> line in the [global] section to read: </P
><P
@@ -149,22 +251,26 @@ CLASS="COMMAND"
>You must also have the parameter <A
HREF="smb.conf.5.html#ENCRYPTPASSWORDS"
TARGET="_top"
-> <VAR
+> <TT
CLASS="PARAMETER"
->encrypt passwords</VAR
+><I
+>encrypt passwords</I
+></TT
></A
-> set to <CODE
+> set to <TT
CLASS="CONSTANT"
>yes
- </CODE
+ </TT
> in order for your users to authenticate to the NT PDC.</P
><P
>Finally, add (or modify) a <A
HREF="smb.conf.5.html#PASSWORDSERVER"
TARGET="_top"
-> <VAR
+> <TT
CLASS="PARAMETER"
->password server =</VAR
+><I
+>password server =</I
+></TT
></A
> line in the [global]
section to read: </P
@@ -189,89 +295,50 @@ CLASS="COMMAND"
>password server = *</B
></P
><P
->This method, allows Samba to use exactly the same
- mechanism that NT does. This
+>This method, which was introduced in Samba 2.0.6,
+ allows Samba to use exactly the same mechanism that NT does. This
method either broadcasts or uses a WINS database in order to
find domain controllers to authenticate against.</P
><P
->In order to actually join the domain, you must run this
- command:</P
-><P
-><SAMP
-CLASS="PROMPT"
->root# </SAMP
-><KBD
-CLASS="USERINPUT"
->net rpc join -S DOMPDC
- -U<VAR
-CLASS="REPLACEABLE"
->Administrator%password</VAR
-></KBD
-></P
-><P
->as we are joining the domain DOM and the PDC for that domain
- (the only machine that has write access to the domain SAM database)
- is DOMPDC. The <VAR
-CLASS="REPLACEABLE"
->Administrator%password</VAR
-> is
- the login name and password for an account which has the necessary
- privilege to add machines to the domain. If this is successful
- you will see the message:</P
-><P
-><SAMP
-CLASS="COMPUTEROUTPUT"
->Joined domain DOM.</SAMP
->
- or <SAMP
-CLASS="COMPUTEROUTPUT"
->Joined 'SERV1' to realm 'MYREALM'</SAMP
->
- </P
-><P
->in your terminal window. See the <A
-HREF="net.8.html"
-TARGET="_top"
-> net(8)</A
-> man page for more details.</P
-><P
->This process joins the server to thedomain
- without having to create the machine trust account on the PDC
- beforehand.</P
-><P
->This command goes through the machine account password
- change protocol, then writes the new (random) machine account
- password for this Samba server into a file in the same directory
- in which an smbpasswd file would be stored - normally :</P
+>Finally, restart your Samba daemons and get ready for
+ clients to begin using domain security!</P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN1337">9.2. Samba and Windows 2000 Domains</H1
><P
-><TT
-CLASS="FILENAME"
->/usr/local/samba/private/secrets.tdb</TT
-></P
+>Many people have asked regarding the state of Samba's ability to participate in
+a Windows 2000 Domain. Samba 3.0 is able to act as a member server of a Windows
+2000 domain operating in mixed or native mode.</P
><P
->This file is created and owned by root and is not
- readable by any other user. It is the key to the domain-level
- security for your system, and should be treated as carefully
- as a shadow password file.</P
+>There is much confusion between the circumstances that require a "mixed" mode
+Win2k DC and a when this host can be switched to "native" mode. A "mixed" mode
+Win2k domain controller is only needed if Windows NT BDCs must exist in the same
+domain. By default, a Win2k DC in "native" mode will still support
+NetBIOS and NTLMv1 for authentication of legacy clients such as Windows 9x and
+NT 4.0. Samba has the same requirements as a Windows NT 4.0 member server.</P
><P
->Finally, restart your Samba daemons and get ready for
- clients to begin using domain security!</P
+>The steps for adding a Samba 2.2 host to a Win2k domain are the same as those
+for adding a Samba server to a Windows NT 4.0 domain. The only exception is that
+the "Server Manager" from NT 4 has been replaced by the "Active Directory Users and
+Computers" MMC (Microsoft Management Console) plugin.</P
></DIV
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="AEN1493"
->9.2. Why is this better than security = server?</A
-></H1
+NAME="AEN1342">9.3. Why is this better than security = server?</H1
><P
>Currently, domain security in Samba doesn't free you from
having to create local Unix users to represent the users attaching
- to your server. This means that if domain user <CODE
+ to your server. This means that if domain user <TT
CLASS="CONSTANT"
>DOM\fred
- </CODE
+ </TT
> attaches to your domain security Samba server, there needs
to be a local Unix user fred to represent that user in the Unix
filesystem. This is very similar to the older Samba security mode
@@ -320,28 +387,20 @@ CLASS="COMMAND"
>And finally, acting in the same manner as an NT server
authenticating to a PDC means that as part of the authentication
reply, the Samba server gets the user identification information such
- as the user SID, the list of NT groups the user belongs to, etc. </P
-><DIV
-CLASS="NOTE"
-><P
-></P
-><TABLE
-CLASS="NOTE"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
+ as the user SID, the list of NT groups the user belongs to, etc. All
+ this information will allow Samba to be extended in the future into
+ a mode the developers currently call appliance mode. In this mode,
+ no local Unix users will be necessary, and Samba will generate Unix
+ uids and gids from the information passed back from the PDC when a
+ user is authenticated, making a Samba server truly plug and play
+ in an NT domain environment. Watch for this code soon.</P
><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>NOTE:</I
+></SPAN
> Much of the text of this document
was first published in the Web magazine <A
HREF="http://www.linuxworld.com"
@@ -354,10 +413,6 @@ TARGET="_top"
>Doing
the NIS/NT Samba</A
>.</P
-></TD
-></TR
-></TABLE
-></DIV
></DIV
></DIV
><DIV
@@ -418,7 +473,7 @@ ACCESSKEY="U"
WIDTH="33%"
ALIGN="right"
VALIGN="top"
->Advanced Configuration</TD
+>Optional configuration</TD
></TR
></TABLE
></DIV
diff --git a/docs/htmldocs/findsmb.1.html b/docs/htmldocs/findsmb.1.html
index 878c3d78fe..af7100ed6f 100644
--- a/docs/htmldocs/findsmb.1.html
+++ b/docs/htmldocs/findsmb.1.html
@@ -1,41 +1,214 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>findsmb</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="findsmb.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>findsmb &#8212; list info about machines that respond to SMB
- name queries on a subnet</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><tt>findsmb</tt> [subnet broadcast address]</p></div></div><div class="refsect1" lang="en"><h2>DESCRIPTION</h2><p>This perl script is part of the <a href="Samba.7.html">Samba(7)</a>
- suite.</p><p><b>findsmb</b> is a perl script that
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
+<HTML
+><HEAD
+><TITLE
+>findsmb</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"></HEAD
+><BODY
+CLASS="REFENTRY"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><H1
+><A
+NAME="FINDSMB">findsmb</H1
+><DIV
+CLASS="REFNAMEDIV"
+><A
+NAME="AEN5"
+></A
+><H2
+>Name</H2
+>findsmb&nbsp;--&nbsp;list info about machines that respond to SMB
+ name queries on a subnet</DIV
+><DIV
+CLASS="REFSYNOPSISDIV"
+><A
+NAME="AEN8"><H2
+>Synopsis</H2
+><P
+><B
+CLASS="COMMAND"
+>findsmb</B
+> [subnet broadcast address]</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN12"
+></A
+><H2
+>DESCRIPTION</H2
+><P
+>This perl script is part of the <A
+HREF="samba.7.html"
+TARGET="_top"
+> Samba</A
+> suite.</P
+><P
+><B
+CLASS="COMMAND"
+>findsmb</B
+> is a perl script that
prints out several pieces of information about machines
on a subnet that respond to SMB name query requests.
- It uses <a href="nmblookup.1.html">nmblookup(1)</a>
- and <a href="smbclient.1.html">smbclient(1)</a>
- to obtain this information.
- </p></div><div class="refsect1" lang="en"><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-r</span></dt><dd><p>Controls whether <b>findsmb</b> takes
+ It uses <A
+HREF="nmblookup.1.html"
+TARGET="_top"
+><B
+CLASS="COMMAND"
+> nmblookup(1)</B
+></A
+> and <A
+HREF="smbclient.1.html"
+TARGET="_top"
+> <B
+CLASS="COMMAND"
+>smbclient(1)</B
+></A
+> to obtain this information.
+ </P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN22"
+></A
+><H2
+>OPTIONS</H2
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>-r</DT
+><DD
+><P
+>Controls whether <B
+CLASS="COMMAND"
+>findsmb</B
+> takes
bugs in Windows95 into account when trying to find a Netbios name
registered of the remote machine. This option is disabled by default
because it is specific to Windows 95 and Windows 95 machines only.
- If set, <a href="nmblookup.1.html">nmblookup(1)</a>
- will be called with <tt>-B</tt> option.</p></dd><dt><span class="term">subnet broadcast address</span></dt><dd><p>Without this option, <b>findsmb
- </b> will probe the subnet of the machine where
- <a href="findsmb.1.html">findsmb(1)</a>
- is run. This value is passed to
- <a href="nmblookup.1.html">nmblookup(1)</a>
- as part of the <tt>-B</tt> option.</p></dd></dl></div></div><div class="refsect1" lang="en"><h2>EXAMPLES</h2><p>The output of <b>findsmb</b> lists the following
+ If set, <A
+HREF="nmblookup.1.html"
+TARGET="_top"
+><B
+CLASS="COMMAND"
+>nmblookup</B
+></A
+>
+ will be called with <TT
+CLASS="CONSTANT"
+>-B</TT
+> option.</P
+></DD
+><DT
+>subnet broadcast address</DT
+><DD
+><P
+>Without this option, <B
+CLASS="COMMAND"
+>findsmb
+ </B
+> will probe the subnet of the machine where
+ <B
+CLASS="COMMAND"
+>findsmb</B
+> is run. This value is passed
+ to <B
+CLASS="COMMAND"
+>nmblookup</B
+> as part of the
+ <TT
+CLASS="CONSTANT"
+>-B</TT
+> option.</P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN41"
+></A
+><H2
+>EXAMPLES</H2
+><P
+>The output of <B
+CLASS="COMMAND"
+>findsmb</B
+> lists the following
information for all machines that respond to the initial
- <b>nmblookup</b> for any name: IP address, NetBIOS name,
- Workgroup name, operating system, and SMB server version.</p><p>There will be a '+' in front of the workgroup name for
+ <B
+CLASS="COMMAND"
+>nmblookup</B
+> for any name: IP address, NetBIOS name,
+ Workgroup name, operating system, and SMB server version.</P
+><P
+>There will be a '+' in front of the workgroup name for
machines that are local master browsers for that workgroup. There
will be an '*' in front of the workgroup name for
machines that are the domain master browser for that workgroup.
Machines that are running Windows, Windows 95 or Windows 98 will
not show any information about the operating system or server
- version.</p><p>The command with <tt>-r</tt> option
- must be run on a system without <a href="nmbd.8.html">nmbd(8)</a> running.
-
- If <b>nmbd</b> is running on the system, you will
+ version.</P
+><P
+>The command with <TT
+CLASS="CONSTANT"
+>-r</TT
+> option
+ must be run on a system without <A
+HREF="nmbd.8.html"
+TARGET="_top"
+><B
+CLASS="COMMAND"
+>nmbd</B
+></A
+> running.
+ If <B
+CLASS="COMMAND"
+>nmbd</B
+> is running on the system, you will
only get the IP address and the DNS name of the machine. To
get proper responses from Windows 95 and Windows 98 machines,
- the command must be run as root and with <tt>-r</tt>
- option on a machine without <b>nmbd</b> running.</p><p>For example, running <b>findsmb</b>
- without <tt>-r</tt> option set would yield output similar
- to the following</p><pre class="screen">
-IP ADDR NETBIOS NAME WORKGROUP/OS/VERSION
+ the command must be run as root and with <TT
+CLASS="CONSTANT"
+>-r</TT
+>
+ option on a machine without <B
+CLASS="COMMAND"
+>nmbd</B
+> running.</P
+><P
+>For example, running <B
+CLASS="COMMAND"
+>findsmb</B
+> without
+ <TT
+CLASS="CONSTANT"
+>-r</TT
+> option set would yield output similar
+ to the following</P
+><TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><PRE
+CLASS="SCREEN"
+><TT
+CLASS="COMPUTEROUTPUT"
+>IP ADDR NETBIOS NAME WORKGROUP/OS/VERSION
---------------------------------------------------------------------
192.168.35.10 MINESET-TEST1 [DMVENGR]
192.168.35.55 LINUXBOX *[MYGROUP] [Unix] [Samba 2.0.6]
@@ -47,15 +220,81 @@ IP ADDR NETBIOS NAME WORKGROUP/OS/VERSION
192.168.35.88 SCNT2 +[MVENGR] [Windows NT 4.0] [NT LAN Manager 4.0]
192.168.35.93 FROGSTAR-PC [MVENGR] [Windows 5.0] [Windows 2000 LAN Manager]
192.168.35.97 HERBNT1 *[HERB-NT] [Windows NT 4.0] [NT LAN Manager 4.0]
-</pre></div><div class="refsect1" lang="en"><h2>VERSION</h2><p>This man page is correct for version 3.0 of
- the Samba suite.</p></div><div class="refsect1" lang="en"><h2>SEE ALSO</h2><p><a href="nmbd.8.html">nmbd(8)</a>,
- <a href="smbclient.1.html">smbclient(1)</a>, and <a href="nmblookup.1.html">nmblookup(1)</a>
- </p></div><div class="refsect1" lang="en"><h2>AUTHOR</h2><p>The original Samba software and related utilities
+ </TT
+></PRE
+></TD
+></TR
+></TABLE
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN59"
+></A
+><H2
+>VERSION</H2
+><P
+>This man page is correct for version 3.0 of
+ the Samba suite.</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN62"
+></A
+><H2
+>SEE ALSO</H2
+><P
+><A
+HREF="nmbd.8.html"
+TARGET="_top"
+><B
+CLASS="COMMAND"
+>nmbd(8)</B
+></A
+>,
+ <A
+HREF="smbclient.1.html"
+TARGET="_top"
+><B
+CLASS="COMMAND"
+>smbclient(1)
+ </B
+></A
+>, and <A
+HREF="nmblookup.1.html"
+TARGET="_top"
+> <B
+CLASS="COMMAND"
+>nmblookup(1)</B
+></A
+>
+ </P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN71"
+></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.
+ 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. The conversion to DocBook
- XML 4.2 for Samba 3.0 was done by Alexander Bokovoy.</p></div></div></body></html>
+ 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
+> \ No newline at end of file
diff --git a/docs/htmldocs/groupmapping.html b/docs/htmldocs/groupmapping.html
index 704b799631..84cf521fc9 100644
--- a/docs/htmldocs/groupmapping.html
+++ b/docs/htmldocs/groupmapping.html
@@ -1,53 +1,235 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter12.Configuring Group Mapping</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"><link rel="home" href="index.html" title="SAMBA Project Documentation"><link rel="up" href="optional.html" title="PartIII.Advanced Configuration"><link rel="previous" href="unix-permissions.html" title="Chapter11.UNIX Permission Bits and Windows NT Access Control Lists"><link rel="next" href="printing.html" title="Chapter13.Printing Support"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter12.Configuring Group Mapping</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="unix-permissions.html">Prev</a></td><th width="60%" align="center">PartIII.Advanced Configuration</th><td width="20%" align="right"><a accesskey="n" href="printing.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="groupmapping"></a>Chapter12.Configuring Group Mapping</h2></div><div><div class="author"><h3 class="author">Jean Franois Micouleau</h3></div></div><div><div class="author"><h3 class="author">Gerald (Jerry) Carter</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt>&lt;<a href="mailto:jerry@samba.org">jerry@samba.org</a>&gt;</tt></p></div></div></div></div></div><p>
-Starting with Samba 3.0 alpha 2, new group mapping functionality
-is available to create associations between Windows SIDs and UNIX
-groups. The <i><tt>groupmap</tt></i> subcommand included with
-the <b>net</b> tool can be used to manage these associations.
-</p><p>
-The first immediate reason to use the group mapping on a Samba PDC, is that
-the <i><tt>domain admin group</tt></i> <tt>smb.conf</tt> has been removed.
-This parameter was used to give the listed users membership in the &quot;Domain Admins&quot;
-Windows group which gave local admin rights on their workstations (in
-default configurations).
-</p><p>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<HTML
+><HEAD
+><TITLE
+>Group mapping HOWTO</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
+REL="HOME"
+TITLE="SAMBA Project Documentation"
+HREF="samba-howto-collection.html"><LINK
+REL="UP"
+TITLE="Optional configuration"
+HREF="optional.html"><LINK
+REL="PREVIOUS"
+TITLE="HOWTO Access Samba source code via CVS"
+HREF="cvs-access.html"><LINK
+REL="NEXT"
+TITLE="Samba performance issues"
+HREF="speed.html"></HEAD
+><BODY
+CLASS="CHAPTER"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><TABLE
+SUMMARY="Header navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>SAMBA Project Documentation</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="cvs-access.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+></TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="speed.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="CHAPTER"
+><H1
+><A
+NAME="GROUPMAPPING">Chapter 21. Group mapping HOWTO</H1
+><P
+>
+Starting with Samba 3.0 alpha 2, a new group mapping function is available. The
+current method (likely to change) to manage the groups is a new command called
+<B
+CLASS="COMMAND"
+>smbgroupedit</B
+>.</P
+><P
+>The first immediate reason to use the group mapping on a PDC, is that
+the <B
+CLASS="COMMAND"
+>domain admin group</B
+> of <TT
+CLASS="FILENAME"
+>smb.conf</TT
+> is
+now gone. This parameter was used to give the listed users local admin rights
+on their workstations. It was some magic stuff that simply worked but didn't
+scale very well for complex setups.</P
+><P
+>Let me explain how it works on NT/W2K, to have this magic fade away.
When installing NT/W2K on a computer, the installer program creates some users
and groups. Notably the 'Administrators' group, and gives to that group some
privileges like the ability to change the date and time or to kill any process
(or close too) running on the local machine. The 'Administrator' user is a
member of the 'Administrators' group, and thus 'inherit' the 'Administrators'
group privileges. If a 'joe' user is created and become a member of the
-'Administrator' group, 'joe' has exactly the same rights as 'Administrator'.
-</p><p>
-When a NT/W2K machine is joined to a domain, the &quot;Domain Adminis&quot; group of the
-PDC is added to the local 'Administrators' group of the workstation. Every
-member of the 'Domain Administrators' group 'inherit' the
-rights of the local 'Administrators' group when logging on the workstation.
-</p><p>
-The following steps describe how to make samba PDC users members of the
-'Domain Admins' group?
-</p><div class="orderedlist"><ol type="1"><li><p>create a unix group (usually in <tt>/etc/group</tt>),
- let's call it domadm</p></li><li><p>add to this group the users that must be Administrators. For example
- if you want joe,john and mary, your entry in <tt>/etc/group</tt> will
- look like:</p><pre class="programlisting">
- domadm:x:502:joe,john,mary
- </pre></li><li><p>Map this domadm group to the &quot;Domain Admins&quot; group
- by running the command:</p><p><tt>root# </tt><b><tt>net groupmap add ntgroup=&quot;Domain Admins&quot; unixgroup=domadm</tt></b></p><p>The quotes around &quot;Domain Admins&quot; are necessary due to the space in the group name. Also make
- sure to leave no whitespace surrounding the equal character (=).</p></li></ol></div><p>Now joe, john and mary are domain administrators!</p><p>
-It is possible to map any arbitrary UNIX group to any Windows NT
-group as well as making any UNIX group a Windows domain group.
-For example, if you wanted to include a UNIX group (e.g. acct) in a ACL on a
-local file or printer on a domain member machine, you would flag
-that group as a domain group by running the following on the Samba PDC:
-</p><p><tt>root# </tt><b><tt>net groupmap add rid=1000 ntgroup=&quot;Accounting&quot; unixgroup=acct</tt></b></p><p>Be aware that the rid parmeter is a unsigned 32 bit integer that should
-normally start at 1000. However, this rid must not overlap with any RID assigned
-to a user. Verifying this is done differently depending on on the passdb backend
-you are using. Future versions of the tools may perform the verification automatically,
-but for now the burden in on you.</p><p>You can list the various groups in the mapping database by executing
-<b>net groupmap list</b>. Here is an example:</p><pre class="programlisting"><tt>root# </tt>net groupmap list
-System Administrators (S-1-5-21-2547222302-1596225915-2414751004-1002) -&gt; sysadmin
-Domain Admins (S-1-5-21-2547222302-1596225915-2414751004-512) -&gt; domadmin
-Domain Users (S-1-5-21-2547222302-1596225915-2414751004-513) -&gt; domuser
-Domain Guests (S-1-5-21-2547222302-1596225915-2414751004-514) -&gt; domguest
-</pre><p>For complete details on <b>net groupmap</b>, refer to the
-net(8) man page.</p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="unix-permissions.html">Prev</a></td><td width="20%" align="center"><a accesskey="u" href="optional.html">Up</a></td><td width="40%" align="right"><a accesskey="n" href="printing.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter11.UNIX Permission Bits and Windows NT Access Control Lists</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">Chapter13.Printing Support</td></tr></table></div></body></html>
+'Administrator' group, 'joe' has exactly the same rights as 'Administrator'.</P
+><P
+>When a NT/W2K machine is joined to a domain, during that phase, the "Domain
+Administrators' group of the PDC is added to the 'Administrators' group of the
+workstation. Every members of the 'Domain Administrators' group 'inherit' the
+rights of the 'Administrators' group when logging on the workstation.</P
+><P
+>You are now wondering how to make some of your samba PDC users members of the
+'Domain Administrators' ? That's really easy.</P
+><P
+></P
+><OL
+TYPE="1"
+><LI
+><P
+>create a unix group (usually in <TT
+CLASS="FILENAME"
+>/etc/group</TT
+>), let's call it domadm</P
+></LI
+><LI
+><P
+>add to this group the users that must be Administrators. For example if you want joe,john and mary, your entry in <TT
+CLASS="FILENAME"
+>/etc/group</TT
+> will look like:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>domadm:x:502:joe,john,mary</PRE
+></P
+></LI
+><LI
+><P
+>Map this domadm group to the <B
+CLASS="COMMAND"
+>domain admins</B
+> group by running the command:</P
+><P
+><B
+CLASS="COMMAND"
+>smbgroupedit -c "Domain Admins" -u domadm</B
+></P
+></LI
+></OL
+><P
+>You're set, joe, john and mary are domain administrators !</P
+><P
+>Like the Domain Admins group, you can map any arbitrary Unix group to any NT
+group. You can also make any Unix group a domain group. For example, on a domain
+member machine (an NT/W2K or a samba server running winbind), you would like to
+give access to a certain directory to some users who are member of a group on
+your samba PDC. Flag that group as a domain group by running:</P
+><P
+><B
+CLASS="COMMAND"
+>smbgroupedit -a unixgroup -td</B
+></P
+><P
+>You can list the various groups in the mapping database like this</P
+><P
+><B
+CLASS="COMMAND"
+>smbgroupedit -v</B
+></P
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+SUMMARY="Footer navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="cvs-access.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="samba-howto-collection.html"
+ACCESSKEY="H"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="speed.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>HOWTO Access Samba source code via CVS</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="optional.html"
+ACCESSKEY="U"
+>Up</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>Samba performance issues</TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+> \ No newline at end of file
diff --git a/docs/htmldocs/groupprofiles.html b/docs/htmldocs/groupprofiles.html
deleted file mode 100644
index 9c25717238..0000000000
--- a/docs/htmldocs/groupprofiles.html
+++ /dev/null
@@ -1,568 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<HTML
-><HEAD
-><TITLE
->Creating Group Prolicy Files</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
-REL="HOME"
-TITLE="SAMBA Project Documentation"
-HREF="samba-howto-collection.html"><LINK
-REL="UP"
-TITLE="Optional configuration"
-HREF="optional.html"><LINK
-REL="PREVIOUS"
-TITLE="Samba performance issues"
-HREF="speed.html"><LINK
-REL="NEXT"
-TITLE="Securing Samba"
-HREF="securing-samba.html"></HEAD
-><BODY
-CLASS="CHAPTER"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->SAMBA Project Documentation</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="speed.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
-></TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="securing-samba.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="CHAPTER"
-><H1
-><A
-NAME="GROUPPROFILES"
-></A
->Chapter 21. Creating Group Prolicy Files</H1
-><DIV
-CLASS="SECT1"
-><H1
-CLASS="SECT1"
-><A
-NAME="AEN3410"
->21.1. Windows '9x</A
-></H1
-><P
->You need the Win98 Group Policy Editor to
-set Group Profiles up under Windows '9x. It can be found on the Original
-full product Win98 installation CD under
-<TT
-CLASS="FILENAME"
->tools/reskit/netadmin/poledit</TT
->. You install this
-using the Add/Remove Programs facility and then click on the 'Have Disk'
-tab.</P
-><P
->Use the Group Policy Editor to create a policy file that specifies the
-location of user profiles and/or the <TT
-CLASS="FILENAME"
->My Documents</TT
-> etc.
-stuff. You then save these settings in a file called
-<TT
-CLASS="FILENAME"
->Config.POL</TT
-> that needs to be placed in
-the root of the [NETLOGON] share. If your Win98 is configured to log onto
-the Samba Domain, it will automatically read this file and update the
-Win9x/Me registry of the machine that is logging on.</P
-><P
->All of this is covered in the Win98 Resource Kit documentation.</P
-><P
->If you do not do it this way, then every so often Win9x/Me will check the
-integrity of the registry and will restore it's settings from the back-up
-copy of the registry it stores on each Win9x/Me machine. Hence, you will
-occasionally notice things changing back to the original settings.</P
-><P
->The following all refers to Windows NT/200x profile migration - not to policies.
-We need a separate section on policies (NTConfig.Pol) for NT4/200x.</P
-></DIV
-><DIV
-CLASS="SECT1"
-><H1
-CLASS="SECT1"
-><A
-NAME="AEN3420"
->21.2. Windows NT 4</A
-></H1
-><P
->Unfortunately, the Resource Kit info is Win NT4 or 200x specific.</P
-><P
->Here is a quick guide:</P
-><P
-></P
-><UL
-><LI
-><P
->On your NT4 Domain Controller, right click on 'My Computer', then
-select the tab labelled 'User Profiles'.</P
-></LI
-><LI
-><P
->Select a user profile you want to migrate and click on it.</P
-><DIV
-CLASS="NOTE"
-><P
-></P
-><TABLE
-CLASS="NOTE"
-WIDTH="90%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->I am using the term "migrate" lossely. You can copy a profile to
-create a group profile. You can give the user 'Everyone' rights to the
-profile you copy this to. That is what you need to do, since your samba
-domain is not a member of a trust relationship with your NT4 PDC.</P
-></TD
-></TR
-></TABLE
-></DIV
-></LI
-><LI
-><P
->Click the 'Copy To' button.</P
-></LI
-><LI
-><P
->In the box labelled 'Copy Profile to' add your new path, eg:
-<TT
-CLASS="FILENAME"
->c:\temp\foobar</TT
-></P
-></LI
-><LI
-><P
->Click on the button labelled 'Change' in the "Permitted to use" box.</P
-></LI
-><LI
-><P
->Click on the group 'Everyone' and then click OK. This closes the
-'chose user' box.</P
-></LI
-><LI
-><P
->Now click OK.</P
-></LI
-></UL
-><P
->Follow the above for every profile you need to migrate.</P
-><DIV
-CLASS="SECT2"
-><H2
-CLASS="SECT2"
-><A
-NAME="AEN3443"
->21.2.1. Side bar Notes</A
-></H2
-><P
->You should obtain the SID of your NT4 domain. You can use smbpasswd to do
-this. Read the man page.</P
-><P
->With Samba-3.0.0 alpha code you can import all you NT4 domain accounts
-using the net samsync method. This way you can retain your profile
-settings as well as all your users.</P
-></DIV
-><DIV
-CLASS="SECT2"
-><H2
-CLASS="SECT2"
-><A
-NAME="AEN3447"
->21.2.2. Mandatory profiles</A
-></H2
-><P
->The above method can be used to create mandatory profiles also. To convert
-a group profile into a mandatory profile simply locate the NTUser.DAT file
-in the copied profile and rename it to NTUser.MAN.</P
-></DIV
-><DIV
-CLASS="SECT2"
-><H2
-CLASS="SECT2"
-><A
-NAME="AEN3450"
->21.2.3. moveuser.exe</A
-></H2
-><P
->The W2K professional resource kit has moveuser.exe. moveuser.exe changes
-the security of a profile from one user to another. This allows the account
-domain to change, and/or the user name to change.</P
-></DIV
-><DIV
-CLASS="SECT2"
-><H2
-CLASS="SECT2"
-><A
-NAME="AEN3453"
->21.2.4. Get SID</A
-></H2
-><P
->You can identify the SID by using GetSID.exe from the Windows NT Server 4.0
-Resource Kit.</P
-><P
->Windows NT 4.0 stores the local profile information in the registry under
-the following key:
-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList</P
-><P
->Under the ProfileList key, there will be subkeys named with the SIDs of the
-users who have logged on to this computer. (To find the profile information
-for the user whose locally cached profile you want to move, find the SID for
-the user with the GetSID.exe utility.) Inside of the appropriate user's
-subkey, you will see a string value named ProfileImagePath.</P
-></DIV
-></DIV
-><DIV
-CLASS="SECT1"
-><H1
-CLASS="SECT1"
-><A
-NAME="AEN3458"
->21.3. Windows 2000/XP</A
-></H1
-><P
->You must first convert the profile from a local profile to a domain
-profile on the MS Windows workstation as follows:</P
-><P
-></P
-><UL
-><LI
-><P
->Log on as the LOCAL workstation administrator.</P
-></LI
-><LI
-><P
->Right click on the 'My Computer' Icon, select 'Properties'</P
-></LI
-><LI
-><P
->Click on the 'User Profiles' tab</P
-></LI
-><LI
-><P
->Select the profile you wish to convert (click on it once)</P
-></LI
-><LI
-><P
->Click on the button 'Copy To'</P
-></LI
-><LI
-><P
->In the "Permitted to use" box, click on the 'Change' button.</P
-></LI
-><LI
-><P
->Click on the 'Look in" area that lists the machine name, when you click
-here it will open up a selection box. Click on the domain to which the
-profile must be accessible.</P
-><DIV
-CLASS="NOTE"
-><P
-></P
-><TABLE
-CLASS="NOTE"
-WIDTH="90%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->You will need to log on if a logon box opens up. Eg: In the connect
-as: MIDEARTH\root, password: mypassword.</P
-></TD
-></TR
-></TABLE
-></DIV
-></LI
-><LI
-><P
->To make the profile capable of being used by anyone select 'Everyone'</P
-></LI
-><LI
-><P
->Click OK. The Selection box will close.</P
-></LI
-><LI
-><P
->Now click on the 'Ok' button to create the profile in the path you
-nominated.</P
-></LI
-></UL
-><P
->Done. You now have a profile that can be editted using the samba-3.0.0
-profiles tool.</P
-><DIV
-CLASS="NOTE"
-><P
-></P
-><TABLE
-CLASS="NOTE"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->Under NT/2K the use of mandotory profiles forces the use of MS Exchange
-storage of mail data. That keeps desktop profiles usable.</P
-></TD
-></TR
-></TABLE
-></DIV
-><DIV
-CLASS="NOTE"
-><P
-></P
-><TABLE
-CLASS="NOTE"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
-></P
-><UL
-><LI
-><P
->This is a security check new to Windows XP (or maybe only
-Windows XP service pack 1). It can be disabled via a group policy in
-Active Directory. The policy is:</P
-><P
->"Computer Configuration\Administrative Templates\System\User
-Profiles\Do not check for user ownership of Roaming Profile Folders"</P
-><P
->...and it should be set to "Enabled".
-Does the new version of samba have an Active Directory analogue? If so,
-then you may be able to set the policy through this.</P
-><P
->If you cannot set group policies in samba, then you may be able to set
-the policy locally on each machine. If you want to try this, then do
-the following (N.B. I don't know for sure that this will work in the
-same way as a domain group policy):</P
-></LI
-><LI
-><P
->On the XP workstation log in with an Administrator account.</P
-></LI
-><LI
-><P
->Click: "Start", "Run"</P
-></LI
-><LI
-><P
->Type: "mmc"</P
-></LI
-><LI
-><P
->Click: "OK"</P
-></LI
-><LI
-><P
->A Microsoft Management Console should appear.</P
-></LI
-><LI
-><P
->Click: File, "Add/Remove Snap-in...", "Add"</P
-></LI
-><LI
-><P
->Double-Click: "Group Policy"</P
-></LI
-><LI
-><P
->Click: "Finish", "Close"</P
-></LI
-><LI
-><P
->Click: "OK"</P
-></LI
-><LI
-><P
->In the "Console Root" window:</P
-></LI
-><LI
-><P
->Expand: "Local Computer Policy", "Computer Configuration",</P
-></LI
-><LI
-><P
->"Administrative Templates", "System", "User Profiles"</P
-></LI
-><LI
-><P
->Double-Click: "Do not check for user ownership of Roaming Profile</P
-></LI
-><LI
-><P
->Folders"</P
-></LI
-><LI
-><P
->Select: "Enabled"</P
-></LI
-><LI
-><P
->Click: OK"</P
-></LI
-><LI
-><P
->Close the whole console. You do not need to save the settings (this
-refers to the console settings rather than the policies you have
-changed).</P
-></LI
-><LI
-><P
->Reboot</P
-></LI
-></UL
-></TD
-></TR
-></TABLE
-></DIV
-></DIV
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="speed.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="samba-howto-collection.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="securing-samba.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Samba performance issues</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="optional.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Securing Samba</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
-> \ No newline at end of file
diff --git a/docs/htmldocs/improved-browsing.html b/docs/htmldocs/improved-browsing.html
index 209dfaaf54..4e9d7f639e 100644
--- a/docs/htmldocs/improved-browsing.html
+++ b/docs/htmldocs/improved-browsing.html
@@ -5,19 +5,20 @@
>Improved browsing in samba</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
REL="HOME"
TITLE="SAMBA Project Documentation"
HREF="samba-howto-collection.html"><LINK
REL="UP"
-TITLE="Advanced Configuration"
-HREF="optional.html"><LINK
+TITLE="General installation"
+HREF="introduction.html"><LINK
REL="PREVIOUS"
-TITLE="Integrating MS Windows networks with Samba"
-HREF="integrate-ms-networks.html"><LINK
+TITLE="How to Install and Test SAMBA"
+HREF="install.html"><LINK
REL="NEXT"
-TITLE="Securing Samba"
-HREF="securing-samba.html"></HEAD
+TITLE="Quick Cross Subnet Browsing / Cross Workgroup Browsing guide"
+HREF="browsing-quick.html"></HEAD
><BODY
CLASS="CHAPTER"
BGCOLOR="#FFFFFF"
@@ -45,7 +46,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
-HREF="integrate-ms-networks.html"
+HREF="install.html"
ACCESSKEY="P"
>Prev</A
></TD
@@ -59,7 +60,7 @@ WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
-HREF="securing-samba.html"
+HREF="browsing-quick.html"
ACCESSKEY="N"
>Next</A
></TD
@@ -72,87 +73,16 @@ WIDTH="100%"></DIV
CLASS="CHAPTER"
><H1
><A
-NAME="IMPROVED-BROWSING"
-></A
->Chapter 24. Improved browsing in samba</H1
-><DIV
-CLASS="TOC"
-><DL
-><DT
-><B
->Table of Contents</B
-></DT
-><DT
->24.1. <A
-HREF="improved-browsing.html#AEN3874"
->Overview of browsing</A
-></DT
-><DT
->24.2. <A
-HREF="improved-browsing.html#AEN3880"
->Browsing support in samba</A
-></DT
-><DT
->24.3. <A
-HREF="improved-browsing.html#AEN3895"
->Problem resolution</A
-></DT
-><DT
->24.4. <A
-HREF="improved-browsing.html#AEN3907"
->Browsing across subnets</A
-></DT
-><DT
->24.5. <A
-HREF="improved-browsing.html#AEN3948"
->Setting up a WINS server</A
-></DT
-><DT
->24.6. <A
-HREF="improved-browsing.html#AEN3971"
->Setting up Browsing in a WORKGROUP</A
-></DT
-><DT
->24.7. <A
-HREF="improved-browsing.html#AEN3997"
->Setting up Browsing in a DOMAIN</A
-></DT
-><DT
->24.8. <A
-HREF="improved-browsing.html#BROWSE-FORCE-MASTER"
->Forcing samba to be the master</A
-></DT
-><DT
->24.9. <A
-HREF="improved-browsing.html#AEN4032"
->Making samba the domain master</A
-></DT
-><DT
->24.10. <A
-HREF="improved-browsing.html#AEN4054"
->Note about broadcast addresses</A
-></DT
-><DT
->24.11. <A
-HREF="improved-browsing.html#AEN4057"
->Multiple interfaces</A
-></DT
-></DL
-></DIV
+NAME="IMPROVED-BROWSING">Chapter 2. Improved browsing in samba</H1
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="AEN3874"
->24.1. Overview of browsing</A
-></H1
+NAME="AEN229">2.1. Overview of browsing</H1
><P
>SMB networking provides a mechanism by which clients can access a list
-of machines in a network, a so-called <B
-CLASS="COMMAND"
->browse list</B
->. This list
+of machines in a network, a so-called "browse list". This list
contains machines that are ready to offer file and/or print services
to other machines within the network. Thus it does not include
machines which aren't currently able to do server tasks. The browse
@@ -160,13 +90,8 @@ list is heavily used by all SMB clients. Configuration of SMB
browsing has been problematic for some Samba users, hence this
document.</P
><P
->MS Windows 2000 and later, as with Samba 3 and later, can be
-configured to not use NetBIOS over TCP/IP. When configured this way
-it is imperative that name resolution (using DNS/LDAP/ADS) be correctly
-configured and operative. Browsing will NOT work if name resolution
-from SMB machine names to IP addresses does not function correctly.</P
-><P
->Where NetBIOS over TCP/IP is enabled use of a WINS server is highly
+>Browsing will NOT work if name resolution from NetBIOS names to IP
+addresses does not function correctly. Use of a WINS server is highly
recommended to aid the resolution of NetBIOS (SMB) names to IP addresses.
WINS allows remote segment clients to obtain NetBIOS name_type information
that can NOT be provided by any other means of name resolution.</P
@@ -176,20 +101,14 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="AEN3880"
->24.2. Browsing support in samba</A
-></H1
-><P
->Samba facilitates browsing. The browsing is supported by <SPAN
-CLASS="APPLICATION"
->nmbd</SPAN
->
-and is also controlled by options in the <TT
-CLASS="FILENAME"
->smb.conf</TT
-> file.
-Samba can act as a local browse master for a workgroup and the ability
-for samba to support domain logons and scripts is now available.</P
+NAME="AEN233">2.2. Browsing support in samba</H1
+><P
+>Samba now fully supports browsing. The browsing is supported by nmbd
+and is also controlled by options in the smb.conf file (see smb.conf(5)).</P
+><P
+>Samba can act as a local browse master for a workgroup and the ability
+for samba to support domain logons and scripts is now available. See
+DOMAIN.txt for more information on domain logons.</P
><P
>Samba can also act as a domain master browser for a workgroup. This
means that it will collate lists from local browse masters into a
@@ -202,123 +121,64 @@ workgroup that has the same name as an NT Domain: on each wide area
network, you must only ever have one domain master browser per workgroup,
regardless of whether it is NT, Samba or any other type of domain master
that is providing this service.</P
-><DIV
-CLASS="NOTE"
><P
-></P
-><TABLE
-CLASS="NOTE"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->Nmbd can be configured as a WINS server, but it is not
-necessary to specifically use samba as your WINS server. MS Windows
-NT4, Server or Advanced Server 2000 or 2003 can be configured as
-your WINS server. In a mixed NT/2000/2003 server and samba environment on
-a Wide Area Network, it is recommended that you use the Microsoft
-WINS server capabilities. In a samba-only environment, it is
-recommended that you use one and only one Samba server as your WINS server.</P
-></TD
-></TR
-></TABLE
-></DIV
+>[Note that nmbd can be configured as a WINS server, but it is not
+necessary to specifically use samba as your WINS server. NTAS can
+be configured as your WINS server. In a mixed NT server and
+samba environment on a Wide Area Network, it is recommended that
+you use the NT server's WINS server capabilities. In a samba-only
+environment, it is recommended that you use one and only one nmbd
+as your WINS server].</P
><P
>To get browsing to work you need to run nmbd as usual, but will need
-to use the <B
-CLASS="COMMAND"
->workgroup</B
-> option in <TT
-CLASS="FILENAME"
->smb.conf</TT
->
-to control what workgroup Samba becomes a part of.</P
+to use the "workgroup" option in smb.conf to control what workgroup
+Samba becomes a part of.</P
><P
>Samba also has a useful option for a Samba server to offer itself for
browsing on another subnet. It is recommended that this option is only
used for 'unusual' purposes: announcements over the internet, for
-example. See <B
-CLASS="COMMAND"
->remote announce</B
-> in the
-<TT
-CLASS="FILENAME"
->smb.conf</TT
-> man page. </P
+example. See "remote announce" in the smb.conf man page. </P
></DIV
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="AEN3895"
->24.3. Problem resolution</A
-></H1
+NAME="AEN242">2.3. Problem resolution</H1
><P
>If something doesn't work then hopefully the log.nmb file will help
you track down the problem. Try a debug level of 2 or 3 for finding
problems. Also note that the current browse list usually gets stored
-in text form in a file called <TT
-CLASS="FILENAME"
->browse.dat</TT
->.</P
+in text form in a file called browse.dat.</P
><P
>Note that if it doesn't work for you, then you should still be able to
-type the server name as <TT
-CLASS="FILENAME"
->\\SERVER</TT
-> in filemanager then
-hit enter and filemanager should display the list of available shares.</P
+type the server name as \\SERVER in filemanager then hit enter and
+filemanager should display the list of available shares.</P
><P
>Some people find browsing fails because they don't have the global
-<B
-CLASS="COMMAND"
->guest account</B
-> set to a valid account. Remember that the
-IPC$ connection that lists the shares is done as guest, and thus you must
+"guest account" set to a valid account. Remember that the IPC$
+connection that lists the shares is done as guest, and thus you must
have a valid guest account.</P
><P
-><SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->MS Windows 2000 and upwards (as with Samba) can be configured to disallow
-anonymous (ie: Guest account) access to the IPC$ share. In that case, the
-MS Windows 2000/XP/2003 machine acting as an SMB/CIFS client will use the
-name of the currently logged in user to query the IPC$ share. MS Windows
-9X clients are not able to do this and thus will NOT be able to browse
-server resources.</I
-></SPAN
-></P
+>Also, a lot of people are getting bitten by the problem of too many
+parameters on the command line of nmbd in inetd.conf. This trick is to
+not use spaces between the option and the parameter (eg: -d2 instead
+of -d 2), and to not use the -B and -N options. New versions of nmbd
+are now far more likely to correctly find your broadcast and network
+address, so in most cases these aren't needed.</P
><P
>The other big problem people have is that their broadcast address,
netmask or IP address is wrong (specified with the "interfaces" option
-in <TT
-CLASS="FILENAME"
->smb.conf</TT
->)</P
+in smb.conf)</P
></DIV
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="AEN3907"
->24.4. Browsing across subnets</A
-></H1
+NAME="AEN249">2.4. Browsing across subnets</H1
><P
->Since the release of Samba 1.9.17(alpha1) Samba has been
+>With the release of Samba 1.9.17(alpha1 and above) Samba has been
updated to enable it to support the replication of browse lists
across subnet boundaries. New code and options have been added to
achieve this. This section describes how to set this feature up
@@ -339,23 +199,19 @@ another subnet without using a WINS server.</P
be they Windows 95, Windows NT, or Samba servers must have the IP address
of a WINS server given to them by a DHCP server, or by manual configuration
(for Win95 and WinNT, this is in the TCP/IP Properties, under Network
-settings) for Samba this is in the <TT
-CLASS="FILENAME"
->smb.conf</TT
-> file.</P
+settings) for Samba this is in the smb.conf file.</P
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
-NAME="AEN3913"
->24.4.1. How does cross subnet browsing work ?</A
-></H2
+NAME="AEN254">2.4.1. How does cross subnet browsing work ?</H2
><P
>Cross subnet browsing is a complicated dance, containing multiple
moving parts. It has taken Microsoft several years to get the code
that achieves this correct, and Samba lags behind in some areas.
-Samba is capable of cross subnet browsing when configured correctly.</P
+However, with the 1.9.17 release, Samba is capable of cross subnet
+browsing when configured correctly.</P
><P
>Consider a network set up as follows :</P
><P
@@ -436,7 +292,7 @@ machine is seen across any of the subnets.</P
master browser it looks for a Domain master browser to synchronize
its browse list with. It does this by querying the WINS server
(N2_D) for the IP address associated with the NetBIOS name
-WORKGROUP&#62;1B&#60;. This name was registerd by the Domain master
+WORKGROUP&gt;1B&lt;. This name was registerd by the Domain master
browser (N1_C) with the WINS server as soon as it was booted.</P
><P
>Once N2_B knows the address of the Domain master browser it
@@ -559,16 +415,11 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="AEN3948"
->24.5. Setting up a WINS server</A
-></H1
+NAME="AEN289">2.5. Setting up a WINS server</H1
><P
>Either a Samba machine or a Windows NT Server machine may be set up
as a WINS server. To set a Samba machine to be a WINS server you must
-add the following option to the <TT
-CLASS="FILENAME"
->smb.conf</TT
-> file on the selected machine :
+add the following option to the smb.conf file on the selected machine :
in the [globals] section add the line </P
><P
><B
@@ -576,22 +427,22 @@ CLASS="COMMAND"
> wins support = yes</B
></P
><P
->Versions of Samba prior to 1.9.17 had this parameter default to
+>Versions of Samba previous to 1.9.17 had this parameter default to
yes. If you have any older versions of Samba on your network it is
-strongly suggested you upgrade to a recent version, or at the very
+strongly suggested you upgrade to 1.9.17 or above, or at the very
least set the parameter to 'no' on all these machines.</P
><P
->Machines with <B
+>Machines with "<B
CLASS="COMMAND"
>wins support = yes</B
-> will keep a list of
+>" will keep a list of
all NetBIOS names registered with them, acting as a DNS for NetBIOS names.</P
><P
>You should set up only ONE wins server. Do NOT set the
-<B
+"<B
CLASS="COMMAND"
>wins support = yes</B
-> option on more than one Samba
+>" option on more than one Samba
server.</P
><P
>To set up a Windows NT Server as a WINS server you need to set up
@@ -602,11 +453,8 @@ refuse to document these replication protocols Samba cannot currently
participate in these replications. It is possible in the future that
a Samba-&#62;Samba WINS replication protocol may be defined, in which
case more than one Samba machine could be set up as a WINS server
-but currently only one Samba server should have the
-<B
-CLASS="COMMAND"
->wins support = yes</B
-> parameter set.</P
+but currently only one Samba server should have the "wins support = yes"
+parameter set.</P
><P
>After the WINS server has been configured you must ensure that all
machines participating on the network are configured with the address
@@ -615,32 +463,26 @@ the Samba machine IP address in the "Primary WINS Server" field of
the "Control Panel-&#62;Network-&#62;Protocols-&#62;TCP-&#62;WINS Server" dialogs
in Windows 95 or Windows NT. To tell a Samba server the IP address
of the WINS server add the following line to the [global] section of
-all <TT
-CLASS="FILENAME"
->smb.conf</TT
-> files :</P
+all smb.conf files :</P
><P
><B
CLASS="COMMAND"
->wins server = &#62;name or IP address&#60;</B
+>wins server = &gt;name or IP address&lt;</B
></P
><P
->where &#62;name or IP address&#60; is either the DNS name of the WINS server
+>where &gt;name or IP address&lt; is either the DNS name of the WINS server
machine or its IP address.</P
><P
->Note that this line MUST NOT BE SET in the <TT
-CLASS="FILENAME"
->smb.conf</TT
-> file of the Samba
+>Note that this line MUST NOT BE SET in the smb.conf file of the Samba
server acting as the WINS server itself. If you set both the
-<B
+"<B
CLASS="COMMAND"
>wins support = yes</B
-> option and the
-<B
+>" option and the
+"<B
CLASS="COMMAND"
->wins server = &#60;name&#62;</B
-> option then
+>wins server = &gt;name&lt;</B
+>" option then
nmbd will fail to start.</P
><P
>There are two possible scenarios for setting up cross subnet browsing.
@@ -654,9 +496,7 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="AEN3971"
->24.6. Setting up Browsing in a WORKGROUP</A
-></H1
+NAME="AEN308">2.6. Setting up Browsing in a WORKGROUP</H1
><P
>To set up cross subnet browsing on a network containing machines
in up to be in a WORKGROUP, not an NT Domain you need to set up one
@@ -673,10 +513,7 @@ cross subnet browsing possible for a workgroup.</P
>In an WORKGROUP environment the domain master browser must be a
Samba server, and there must only be one domain master browser per
workgroup name. To set up a Samba server as a domain master browser,
-set the following option in the [global] section of the <TT
-CLASS="FILENAME"
->smb.conf</TT
-> file :</P
+set the following option in the [global] section of the smb.conf file :</P
><P
><B
CLASS="COMMAND"
@@ -685,17 +522,14 @@ CLASS="COMMAND"
><P
>The domain master browser should also preferrably be the local master
browser for its own subnet. In order to achieve this set the following
-options in the [global] section of the <TT
-CLASS="FILENAME"
->smb.conf</TT
-> file :</P
+options in the [global] section of the smb.conf file :</P
><P
><PRE
CLASS="PROGRAMLISTING"
->domain master = yes
-local master = yes
-preferred master = yes
-os level = 65</PRE
+> domain master = yes
+ local master = yes
+ preferred master = yes
+ os level = 65</PRE
></P
><P
>The domain master browser may be the same machine as the WINS
@@ -703,60 +537,40 @@ server, if you require.</P
><P
>Next, you should ensure that each of the subnets contains a
machine that can act as a local master browser for the
-workgroup. Any MS Windows NT/2K/XP/2003 machine should be
-able to do this, as will Windows 9x machines (although these
-tend to get rebooted more often, so it's not such a good idea
-to use these). To make a Samba server a local master browser
-set the following options in the [global] section of the
-<TT
-CLASS="FILENAME"
->smb.conf</TT
-> file :</P
+workgroup. Any NT machine should be able to do this, as will
+Windows 95 machines (although these tend to get rebooted more
+often, so it's not such a good idea to use these). To make a
+Samba server a local master browser set the following
+options in the [global] section of the smb.conf file :</P
><P
><PRE
CLASS="PROGRAMLISTING"
->domain master = no
-local master = yes
-preferred master = yes
-os level = 65</PRE
+> domain master = no
+ local master = yes
+ preferred master = yes
+ os level = 65</PRE
></P
><P
>Do not do this for more than one Samba server on each subnet,
or they will war with each other over which is to be the local
master browser.</P
><P
->The <B
-CLASS="COMMAND"
->local master</B
-> parameter allows Samba to act as a
-local master browser. The <B
-CLASS="COMMAND"
->preferred master</B
-> causes nmbd
-to force a browser election on startup and the <B
-CLASS="COMMAND"
->os level</B
->
-parameter sets Samba high enough so that it should win any browser elections.</P
+>The "local master" parameter allows Samba to act as a local master
+browser. The "preferred master" causes nmbd to force a browser
+election on startup and the "os level" parameter sets Samba high
+enough so that it should win any browser elections.</P
><P
>If you have an NT machine on the subnet that you wish to
be the local master browser then you can disable Samba from
becoming a local master browser by setting the following
-options in the <B
-CLASS="COMMAND"
->[global]</B
-> section of the
-<TT
-CLASS="FILENAME"
->smb.conf</TT
-> file :</P
+options in the [global] section of the smb.conf file :</P
><P
><PRE
CLASS="PROGRAMLISTING"
->domain master = no
-local master = no
-preferred master = no
-os level = 0</PRE
+> domain master = no
+ local master = no
+ preferred master = no
+ os level = 0</PRE
></P
></DIV
><DIV
@@ -764,66 +578,41 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="AEN3997"
->24.7. Setting up Browsing in a DOMAIN</A
-></H1
+NAME="AEN326">2.7. Setting up Browsing in a DOMAIN</H1
><P
>If you are adding Samba servers to a Windows NT Domain then
you must not set up a Samba server as a domain master browser.
By default, a Windows NT Primary Domain Controller for a Domain
name is also the Domain master browser for that name, and many
things will break if a Samba server registers the Domain master
-browser NetBIOS name (<VAR
-CLASS="REPLACEABLE"
->DOMAIN</VAR
->&#60;1B&#62;)
-with WINS instead of the PDC.</P
+browser NetBIOS name (DOMAIN&gt;1B&lt;) with WINS instead of the PDC.</P
><P
>For subnets other than the one containing the Windows NT PDC
you may set up Samba servers as local master browsers as
described. To make a Samba server a local master browser set
-the following options in the <B
-CLASS="COMMAND"
->[global]</B
-> section
-of the <TT
-CLASS="FILENAME"
->smb.conf</TT
-> file :</P
+the following options in the [global] section of the smb.conf
+file :</P
><P
><PRE
CLASS="PROGRAMLISTING"
->domain master = no
-local master = yes
-preferred master = yes
-os level = 65</PRE
+> domain master = no
+ local master = yes
+ preferred master = yes
+ os level = 65</PRE
></P
><P
>If you wish to have a Samba server fight the election with machines
-on the same subnet you may set the <B
-CLASS="COMMAND"
->os level</B
-> parameter
-to lower levels. By doing this you can tune the order of machines that
+on the same subnet you may set the "os level" parameter to lower
+levels. By doing this you can tune the order of machines that
will become local master browsers if they are running. For
-more details on this see the section <A
-HREF="improved-browsing.html#BROWSE-FORCE-MASTER"
->Forcing samba to be the master browser</A
->
+more details on this see the section "FORCING SAMBA TO BE THE MASTER"
below.</P
><P
>If you have Windows NT machines that are members of the domain
on all subnets, and you are sure they will always be running then
you can disable Samba from taking part in browser elections and
ever becoming a local master browser by setting following options
-in the <B
-CLASS="COMMAND"
->[global]</B
-> section of the <TT
-CLASS="FILENAME"
->smb.conf</TT
->
-file :</P
+in the [global] section of the smb.conf file :</P
><P
><B
CLASS="COMMAND"
@@ -838,64 +627,35 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="BROWSE-FORCE-MASTER"
->24.8. Forcing samba to be the master</A
-></H1
+NAME="AEN336">2.8. Forcing samba to be the master</H1
><P
->Who becomes the <B
-CLASS="COMMAND"
->master browser</B
-> is determined by an election
-process using broadcasts. Each election packet contains a number of parameters
+>Who becomes the "master browser" is determined by an election process
+using broadcasts. Each election packet contains a number of parameters
which determine what precedence (bias) a host should have in the
election. By default Samba uses a very low precedence and thus loses
elections to just about anyone else.</P
><P
->If you want Samba to win elections then just set the <B
-CLASS="COMMAND"
->os level</B
-> global
-option in <TT
-CLASS="FILENAME"
->smb.conf</TT
-> to a higher number. It defaults to 0. Using 34
+>If you want Samba to win elections then just set the "os level" global
+option in smb.conf to a higher number. It defaults to 0. Using 34
would make it win all elections over every other system (except other
samba systems!)</P
><P
->A <B
-CLASS="COMMAND"
->os level</B
-> of 2 would make it beat WfWg and Win95, but not MS Windows
-NT/2K Server. A MS Windows NT/2K Server domain controller uses level 32.</P
+>A "os level" of 2 would make it beat WfWg and Win95, but not NTAS. A
+NTAS domain controller uses level 32.</P
><P
>The maximum os level is 255</P
><P
>If you want samba to force an election on startup, then set the
-<B
-CLASS="COMMAND"
->preferred master</B
-> global option in <TT
-CLASS="FILENAME"
->smb.conf</TT
-> to "yes". Samba will
+"preferred master" global option in smb.conf to "yes". Samba will
then have a slight advantage over other potential master browsers
that are not preferred master browsers. Use this parameter with
care, as if you have two hosts (whether they are windows 95 or NT or
-samba) on the same local subnet both set with <B
-CLASS="COMMAND"
->preferred master</B
-> to
+samba) on the same local subnet both set with "preferred master" to
"yes", then periodically and continually they will force an election
in order to become the local master browser.</P
><P
->If you want samba to be a <B
-CLASS="COMMAND"
->domain master browser</B
->, then it is
-recommended that you also set <B
-CLASS="COMMAND"
->preferred master</B
-> to "yes", because
+>If you want samba to be a "domain master browser", then it is
+recommended that you also set "preferred master" to "yes", because
samba will not become a domain master browser for the whole of your
LAN or WAN if it is not also a local master browser on its own
broadcast isolated subnet.</P
@@ -913,20 +673,12 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="AEN4032"
->24.9. Making samba the domain master</A
-></H1
+NAME="AEN345">2.9. Making samba the domain master</H1
><P
>The domain master is responsible for collating the browse lists of
multiple subnets so that browsing can occur between subnets. You can
-make samba act as the domain master by setting <B
-CLASS="COMMAND"
->domain master = yes</B
->
-in <TT
-CLASS="FILENAME"
->smb.conf</TT
->. By default it will not be a domain master.</P
+make samba act as the domain master by setting "domain master = yes"
+in smb.conf. By default it will not be a domain master.</P
><P
>Note that you should NOT set Samba to be the domain master for a
workgroup that has the same name as an NT Domain.</P
@@ -937,14 +689,8 @@ master browsers on other subnets and then contact them to synchronise
browse lists.</P
><P
>If you want samba to be the domain master then I suggest you also set
-the <B
-CLASS="COMMAND"
->os level</B
-> high enough to make sure it wins elections, and set
-<B
-CLASS="COMMAND"
->preferred master</B
-> to "yes", to get samba to force an election on
+the "os level" high enough to make sure it wins elections, and set
+"preferred master" to "yes", to get samba to force an election on
startup.</P
><P
>Note that all your servers (including samba) and clients should be
@@ -998,9 +744,7 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="AEN4054"
->24.10. Note about broadcast addresses</A
-></H1
+NAME="AEN363">2.10. Note about broadcast addresses</H1
><P
>If your network uses a "0" based broadcast address (for example if it
ends in a 0) then you will strike problems. Windows for Workgroups
@@ -1012,19 +756,11 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="AEN4057"
->24.11. Multiple interfaces</A
-></H1
+NAME="AEN366">2.11. Multiple interfaces</H1
><P
>Samba now supports machines with multiple network interfaces. If you
-have multiple interfaces then you will need to use the <B
-CLASS="COMMAND"
->interfaces</B
->
-option in <TT
-CLASS="FILENAME"
->smb.conf</TT
-> to configure them. </P
+have multiple interfaces then you will need to use the "interfaces"
+option in smb.conf to configure them. See smb.conf(5) for details.</P
></DIV
></DIV
><DIV
@@ -1043,7 +779,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
-HREF="integrate-ms-networks.html"
+HREF="install.html"
ACCESSKEY="P"
>Prev</A
></TD
@@ -1061,7 +797,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
-HREF="securing-samba.html"
+HREF="browsing-quick.html"
ACCESSKEY="N"
>Next</A
></TD
@@ -1071,13 +807,13 @@ ACCESSKEY="N"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
->Integrating MS Windows networks with Samba</TD
+>How to Install and Test SAMBA</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
-HREF="optional.html"
+HREF="introduction.html"
ACCESSKEY="U"
>Up</A
></TD
@@ -1085,7 +821,7 @@ ACCESSKEY="U"
WIDTH="33%"
ALIGN="right"
VALIGN="top"
->Securing Samba</TD
+>Quick Cross Subnet Browsing / Cross Workgroup Browsing guide</TD
></TR
></TABLE
></DIV
diff --git a/docs/htmldocs/install.html b/docs/htmldocs/install.html
index 1c107c0019..0ba79dbe26 100644
--- a/docs/htmldocs/install.html
+++ b/docs/htmldocs/install.html
@@ -1,75 +1,896 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter2.How to Install and Test SAMBA</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"><link rel="home" href="index.html" title="SAMBA Project Documentation"><link rel="up" href="introduction.html" title="PartI.General Installation"><link rel="previous" href="IntroSMB.html" title="Chapter1.Introduction to Samba"><link rel="next" href="type.html" title="PartII.Server Configuration Basics"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter2.How to Install and Test SAMBA</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="IntroSMB.html">Prev</a></td><th width="60%" align="center">PartI.General Installation</th><td width="20%" align="right"><a accesskey="n" href="type.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="install"></a>Chapter2.How to Install and Test SAMBA</h2></div><div><div class="author"><h3 class="author">Andrew Tridgell</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt>&lt;<a href="mailto:tridge@samba.org">tridge@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author">Jelmer R. Vernooij</h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt>&lt;<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author">Karl Auer</h3></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="install.html#id2812103">Obtaining and installing samba</a></dt><dt><a href="install.html#id2812254">Configuring samba</a></dt><dd><dl><dt><a href="install.html#id2812000">Editing the smb.conf file</a></dt><dt><a href="install.html#id2875811">SWAT</a></dt></dl></dd><dt><a href="install.html#id2875850">Try listing the shares available on your
- server</a></dt><dt><a href="install.html#id2875900">Try connecting with the unix client</a></dt><dt><a href="install.html#id2876004">Try connecting from a DOS, WfWg, Win9x, WinNT,
- Win2k, OS/2, etc... client</a></dt><dt><a href="install.html#id2876065">What If Things Don't Work?</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2812103"></a>Obtaining and installing samba</h2></div></div><p>Binary packages of samba are included in almost any Linux or
- Unix distribution. There are also some packages available at
- <a href="http://samba.org/" target="_top">the samba homepage</a>.
- </p><p>If you need to compile samba from source, check the
- <a href="compiling.html" title="Chapter30.How to compile SAMBA">appropriate appendix chapter</a>.</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2812254"></a>Configuring samba</h2></div></div><p>Samba's configuration is stored in the smb.conf file,
- that usually resides in <tt>/etc/samba/smb.conf</tt>
- or <tt>/usr/local/samba/lib/smb.conf</tt>. You can either
- edit this file yourself or do it using one of the many graphical
- tools that are available, such as the web-based interface swat, that
- is included with samba.</p><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2812000"></a>Editing the <tt>smb.conf</tt> file</h3></div></div><p>There are sample configuration files in the examples
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<HTML
+><HEAD
+><TITLE
+>How to Install and Test SAMBA</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
+REL="HOME"
+TITLE="SAMBA Project Documentation"
+HREF="samba-howto-collection.html"><LINK
+REL="UP"
+TITLE="General installation"
+HREF="introduction.html"><LINK
+REL="PREVIOUS"
+TITLE="General installation"
+HREF="introduction.html"><LINK
+REL="NEXT"
+TITLE="Improved browsing in samba"
+HREF="improved-browsing.html"></HEAD
+><BODY
+CLASS="CHAPTER"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><TABLE
+SUMMARY="Header navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>SAMBA Project Documentation</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="introduction.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+></TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="improved-browsing.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="CHAPTER"
+><H1
+><A
+NAME="INSTALL">Chapter 1. How to Install and Test SAMBA</H1
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN26">1.1. Read the man pages</H1
+><P
+>The man pages distributed with SAMBA contain
+ lots of useful info that will help to get you started.
+ If you don't know how to read man pages then try
+ something like:</P
+><P
+><TT
+CLASS="PROMPT"
+>$ </TT
+><TT
+CLASS="USERINPUT"
+><B
+>man smbd.8</B
+></TT
+>
+ or
+ <TT
+CLASS="PROMPT"
+>$ </TT
+><TT
+CLASS="USERINPUT"
+><B
+>nroff -man smbd.8 | more
+ </B
+></TT
+> on older unixes.</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"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN36">1.2. Building the Binaries</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 executing</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"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN64">1.3. The all important step</H1
+><P
+>At this stage you must fetch yourself a
+ coffee or other drink you find stimulating. Getting the rest
+ 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"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN68">1.4. Create the smb configuration file.</H1
+><P
+>There are sample configuration files in the examples
subdirectory in the distribution. I suggest you read them
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><pre class="programlisting">
-[global]
- workgroup = MYGROUP
+ 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>which would allow connections by anyone with an
+ [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
- &quot;<b>homes</b>&quot; as the service name. (Note that I also set the
- workgroup that Samba is part of. See BROWSING.txt for details)</p><p>Make sure you put the <tt>smb.conf</tt> file in the same place
- you specified in the<tt>Makefile</tt> (the default is to
- look for it in <tt>/usr/local/samba/lib/</tt>).</p><p>For more information about security settings for the
- <b>[homes]</b> share please refer to the chapter
- <a href="securing-samba.html" title="Chapter24.Securing Samba">Securing Samba</a>.</p><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2875758"></a>Test your config file with
- <b>testparm</b></h4></div></div><p>It's important that you test the validity of your
- <tt>smb.conf</tt> file using the testparm program.
+ "homes" as the service name. (Note that I also set the
+ workgroup that Samba is part of. See BROWSING.txt for details)</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"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN82">1.5. Test your config file with
+ <B
+CLASS="COMMAND"
+>testparm</B
+></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
- reasonable before proceeding. </p><p>Always run testparm again when you change
- <tt>smb.conf</tt>!</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2875811"></a>SWAT</h3></div></div><p>
- SWAT is a web-based interface that helps you configure samba.
- SWAT might not be available in the samba package on your platform,
- but in a separate package. Please read the swat manpage
- on compiling, installing and configuring swat from source.
- </p><p>To launch SWAT just run your favorite web browser and
- point it at &quot;http://localhost:901/&quot;. Replace <i><tt>localhost</tt></i> with the name of the computer you are running samba on if you
- are running samba on a different computer than your browser.</p><p>Note that you can attach to SWAT from any IP connected
- machine but connecting from a remote machine leaves your
- connection open to password sniffing as passwords will be sent
- in the clear over the wire. </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2875850"></a>Try listing the shares available on your
- server</h2></div></div><p><tt>$ </tt><b><tt>smbclient -L
- <i><tt>yourhostname</tt></i></tt></b></p><p>You should get back a list of shares available on
+ not it will give an error message.</P
+><P
+>Make sure it runs OK and that the services look
+ reasonable before proceeding. </P
+><P
+>Always run testparm again when you change
+ <TT
+CLASS="FILENAME"
+>smb.conf</TT
+>!</P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN90">1.6. Starting the smbd and nmbd</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
+> using the recommended daemon method
+ is that they will respond slightly more quickly to an initial connection
+ request.</P
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN100">1.6.1. Starting from inetd.conf</H2
+><P
+>NOTE; The following will be different if
+ you use NIS or NIS+ to distributed services maps.</P
+><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 consistent.</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 some unixes. 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"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN129">1.6.2. Alternative: starting it as a daemon</H2
+><P
+>To start the server as a daemon you should create
+ a script something like this one, perhaps calling
+ 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"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN145">1.7. Try listing the shares available on your
+ server</H1
+><P
+><TT
+CLASS="PROMPT"
+>$ </TT
+><TT
+CLASS="USERINPUT"
+><B
+>smbclient -L
+ <TT
+CLASS="REPLACEABLE"
+><I
+>yourhostname</I
+></TT
+></B
+></TT
+></P
+><P
+>You should get back a list of shares available on
your server. If you don't then something is incorrectly setup.
Note that this method can also be used to see what shares
- are available on other LanManager clients (such as WfWg).</p><p>If you choose user level security then you may find
+ are available on other LanManager clients (such as WfWg).</P
+><P
+>If you choose user level security then you may find
that Samba requests a password before it will list the shares.
- See the <b>smbclient</b> man page for details. (you
+ 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" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2875900"></a>Try connecting with the unix client</h2></div></div><p><tt>$ </tt><b><tt>smbclient <i><tt>
- //yourhostname/aservice</tt></i></tt></b></p><p>Typically the <i><tt>yourhostname</tt></i>
- would be the name of the host where you installed smbd.
- The <i><tt>aservice</tt></i> is
- any service you have defined in the <tt>smb.conf</tt>
- file. Try your user name if you just have a <b>[homes]</b>
- section
- in <tt>smb.conf</tt>.</p><p>For example if your unix host is <i><tt>bambi</tt></i>
- and your login name is <i><tt>fred</tt></i> you would type:</p><p><tt>$ </tt><b><tt>smbclient //<i><tt>bambi</tt></i>/<i><tt>fred</tt></i>
- </tt></b></p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2876004"></a>Try connecting from a DOS, WfWg, Win9x, WinNT,
- Win2k, OS/2, etc... client</h2></div></div><p>Try mounting disks. eg:</p><p><tt>C:\WINDOWS\&gt; </tt><b><tt>net use d: \\servername\service
- </tt></b></p><p>Try printing. eg:</p><p><tt>C:\WINDOWS\&gt; </tt><b><tt>net use lpt1:
- \\servername\spoolservice</tt></b></p><p><tt>C:\WINDOWS\&gt; </tt><b><tt>print filename
- </tt></b></p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2876065"></a>What If Things Don't Work?</h2></div></div><p>Then you might read the file chapter
- <a href="diagnosis.html" title="Chapter27.The samba checklist">Diagnosis</a> and the
- FAQ. If you are still stuck then try to follow
- the <a href="problems.html" title="Chapter28.Analysing and solving samba problems">Analysing and Solving Problems chapter</a>
- Samba has been successfully installed at thousands of sites worldwide,
- so maybe someone else has hit your problem and has overcome it. </p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="IntroSMB.html">Prev</a></td><td width="20%" align="center"><a accesskey="u" href="introduction.html">Up</a></td><td width="40%" align="right"><a accesskey="n" href="type.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter1.Introduction to Samba</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">PartII.Server Configuration Basics</td></tr></table></div></body></html>
+ with non-Samba servers)</P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN154">1.8. Try connecting with the unix client</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"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN170">1.9. Try connecting from a DOS, WfWg, Win9x, WinNT,
+ Win2k, OS/2, etc... client</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"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN184">1.10. What If Things Don't Work?</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"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN189">1.10.1. Diagnosing Problems</H2
+><P
+>If you have installation problems then go to the
+ <A
+HREF="Diagnosis.html"
+TARGET="_top"
+>Diagnosis</A
+> chapter to try to find the
+ problem.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN193">1.10.2. Scope IDs</H2
+><P
+>By default Samba uses a blank scope ID. This means
+ all your windows boxes must also have a blank scope ID.
+ If you really want to use a non-blank scope ID then you will
+ need to use the 'netbios scope' smb.conf option.
+ All your PCs will need to have the same setting for
+ this to work. I do not recommend scope IDs.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN196">1.10.3. Choosing the Protocol Level</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"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN205">1.10.4. Printing from UNIX to a Client PC</H2
+><P
+>To use a printer that is available via a smb-based
+ server from a unix host with LPR 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
+><P
+>See the CUPS manual for information about setting up
+ printing from a unix host with CUPS to a smb-based server. </P
+></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN210">1.10.5. Locking</H2
+><P
+>One area which sometimes causes trouble is locking.</P
+><P
+>There are two types of locking which need to be
+ performed by a SMB server. The first is "record locking"
+ which allows a client to lock a range of bytes in a open file.
+ The second is the "deny modes" that are specified when a file
+ is open.</P
+><P
+>Record locking semantics under Unix is very
+ different from record locking under Windows. Versions
+ of Samba before 2.2 have tried to use the native
+ fcntl() unix system call to implement proper record
+ locking between different Samba clients. This can not
+ be fully correct due to several reasons. The simplest
+ is the fact that a Windows client is allowed to lock a
+ byte range up to 2^32 or 2^64, depending on the client
+ OS. The unix locking only supports byte ranges up to
+ 2^31. So it is not possible to correctly satisfy a
+ lock request above 2^31. There are many more
+ differences, too many to be listed here.</P
+><P
+>Samba 2.2 and above implements record locking
+ completely independent of the underlying unix
+ system. If a byte range lock that the client requests
+ happens to fall into the range 0-2^31, Samba hands
+ this request down to the Unix system. All other locks
+ can not be seen by unix anyway.</P
+><P
+>Strictly a SMB server should check for locks before
+ every read and write call on a file. Unfortunately with the
+ way fcntl() works this can be slow and may overstress the
+ rpc.lockd. It is also almost always unnecessary as clients
+ are supposed to independently make locking calls before reads
+ and writes anyway if locking is important to them. By default
+ Samba only makes locking calls when explicitly asked
+ to by a client, but if you set "strict locking = yes" then it will
+ make lock checking calls on every read and write. </P
+><P
+>You can also disable by range locking completely
+ using "locking = no". This is useful for those shares that
+ don't support locking or don't need it (such as cdroms). In
+ this case Samba fakes the return codes of locking calls to
+ tell clients that everything is OK.</P
+><P
+>The second class of locking is the "deny modes". These
+ are set by an application when it opens a file to determine
+ what types of access should be allowed simultaneously with
+ its open. A client may ask for DENY_NONE, DENY_READ, DENY_WRITE
+ or DENY_ALL. There are also special compatibility modes called
+ DENY_FCB and DENY_DOS.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN219">1.10.6. Mapping Usernames</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
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+SUMMARY="Footer navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="introduction.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="samba-howto-collection.html"
+ACCESSKEY="H"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="improved-browsing.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>General installation</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="introduction.html"
+ACCESSKEY="U"
+>Up</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>Improved browsing in samba</TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+> \ No newline at end of file
diff --git a/docs/htmldocs/integrate-ms-networks.html b/docs/htmldocs/integrate-ms-networks.html
index 70f446e09d..ad6aa9e225 100644
--- a/docs/htmldocs/integrate-ms-networks.html
+++ b/docs/htmldocs/integrate-ms-networks.html
@@ -1,55 +1,221 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter23.Integrating MS Windows networks with Samba</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"><link rel="home" href="index.html" title="SAMBA Project Documentation"><link rel="up" href="optional.html" title="PartIII.Advanced Configuration"><link rel="previous" href="msdfs.html" title="Chapter22.Hosting a Microsoft Distributed File System tree on Samba"><link rel="next" href="securing-samba.html" title="Chapter24.Securing Samba"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter23.Integrating MS Windows networks with Samba</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="msdfs.html">Prev</a></td><th width="60%" align="center">PartIII.Advanced Configuration</th><td width="20%" align="right"><a accesskey="n" href="securing-samba.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="integrate-ms-networks"></a>Chapter23.Integrating MS Windows networks with Samba</h2></div><div><div class="author"><h3 class="author">John H. Terpstra</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt>&lt;<a href="mailto:jht@samba.org">jht@samba.org</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate"> (Jan 01 2001) </p></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="integrate-ms-networks.html#id2899641">Name Resolution in a pure Unix/Linux world</a></dt><dd><dl><dt><a href="integrate-ms-networks.html#id2900075">/etc/hosts</a></dt><dt><a href="integrate-ms-networks.html#id2900212">/etc/resolv.conf</a></dt><dt><a href="integrate-ms-networks.html#id2900256">/etc/host.conf</a></dt><dt><a href="integrate-ms-networks.html#id2900299">/etc/nsswitch.conf</a></dt></dl></dd><dt><a href="integrate-ms-networks.html#id2900394">Name resolution as used within MS Windows networking</a></dt><dd><dl><dt><a href="integrate-ms-networks.html#id2899927">The NetBIOS Name Cache</a></dt><dt><a href="integrate-ms-networks.html#id2899966">The LMHOSTS file</a></dt><dt><a href="integrate-ms-networks.html#id2900009">HOSTS file</a></dt><dt><a href="integrate-ms-networks.html#id2900041">DNS Lookup</a></dt><dt><a href="integrate-ms-networks.html#id2900053">WINS Lookup</a></dt></dl></dd></dl></div><p>
-This section deals with NetBIOS over TCP/IP name to IP address resolution. If
-your MS Windows clients are NOT configured to use NetBIOS over TCP/IP then this
-section does not apply to your installation. If your installation involves use of
-NetBIOS over TCP/IP then this section may help you to resolve networking problems.
-</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
- NetBIOS over TCP/IP has nothing to do with NetBEUI. NetBEUI is NetBIOS
- over Logical Link Control (LLC). On modern networks it is highly advised
- to NOT run NetBEUI at all. Note also that there is NO such thing as
- NetBEUI over TCP/IP - the existence of such a protocol is a complete
- and utter mis-apprehension.
-</p></div><p>
-Since the introduction of MS Windows 2000 it is possible to run MS Windows networking
-without the use of NetBIOS over TCP/IP. NetBIOS over TCP/IP uses UDP port 137 for NetBIOS
-name resolution and uses TCP port 139 for NetBIOS session services. When NetBIOS over
-TCP/IP is disabled on MS Windows 2000 and later clients then only TCP port 445 will be
-used and UDP port 137 and TCP port 139 will not.
-</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-When using Windows 2000 or later clients, if NetBIOS over TCP/IP is NOT disabled, then
-the client will use UDP port 137 (NetBIOS Name Service, also known as the Windows Internet
-Name Service or WINS), TCP port 139 AND TCP port 445 (for actual file and print traffic).
-</p></div><p>
-When NetBIOS over TCP/IP is disabled the use of DNS is essential. Most installations that
-disable NetBIOS over TCP/IP today use MS Active Directory Service (ADS). ADS requires
-Dynamic DNS with Service Resource Records (SRV RR) and with Incremental Zone Transfers (IXFR).
-Use of DHCP with ADS is recommended as a further means of maintaining central control
-over client workstation network configuration.
-</p><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2899641"></a>Name Resolution in a pure Unix/Linux world</h2></div></div><p>
-The key configuration files covered in this section are:
-</p><div class="itemizedlist"><ul type="disc"><li><p><tt>/etc/hosts</tt></p></li><li><p><tt>/etc/resolv.conf</tt></p></li><li><p><tt>/etc/host.conf</tt></p></li><li><p><tt>/etc/nsswitch.conf</tt></p></li></ul></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2900075"></a><tt>/etc/hosts</tt></h3></div></div><p>
-Contains a static list of IP Addresses and names.
-eg:
-</p><pre class="programlisting">
- 127.0.0.1 localhost localhost.localdomain
- 192.168.1.1 bigbox.caldera.com bigbox alias4box
-</pre><p>
-The purpose of <tt>/etc/hosts</tt> is to provide a
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<HTML
+><HEAD
+><TITLE
+>Integrating MS Windows networks with Samba</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
+REL="HOME"
+TITLE="SAMBA Project Documentation"
+HREF="samba-howto-collection.html"><LINK
+REL="UP"
+TITLE="Optional configuration"
+HREF="optional.html"><LINK
+REL="PREVIOUS"
+TITLE="Optional configuration"
+HREF="optional.html"><LINK
+REL="NEXT"
+TITLE="UNIX Permission Bits and Windows NT Access Control Lists"
+HREF="unix-permissions.html"></HEAD
+><BODY
+CLASS="CHAPTER"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><TABLE
+SUMMARY="Header navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>SAMBA Project Documentation</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="optional.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+></TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="unix-permissions.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="CHAPTER"
+><H1
+><A
+NAME="INTEGRATE-MS-NETWORKS">Chapter 10. Integrating MS Windows networks with Samba</H1
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN1374">10.1. Agenda</H1
+><P
+>To identify the key functional mechanisms of MS Windows networking
+to enable the deployment of Samba as a means of extending and/or
+replacing MS Windows NT/2000 technology.</P
+><P
+>We will examine:</P
+><P
+></P
+><OL
+TYPE="1"
+><LI
+><P
+>Name resolution in a pure Unix/Linux TCP/IP
+ environment
+ </P
+></LI
+><LI
+><P
+>Name resolution as used within MS Windows
+ networking
+ </P
+></LI
+><LI
+><P
+>How browsing functions and how to deploy stable
+ and dependable browsing using Samba
+ </P
+></LI
+><LI
+><P
+>MS Windows security options and how to
+ configure Samba for seemless integration
+ </P
+></LI
+><LI
+><P
+>Configuration of Samba as:</P
+><P
+></P
+><OL
+TYPE="a"
+><LI
+><P
+>A stand-alone server</P
+></LI
+><LI
+><P
+>An MS Windows NT 3.x/4.0 security domain member
+ </P
+></LI
+><LI
+><P
+>An alternative to an MS Windows NT 3.x/4.0 Domain Controller
+ </P
+></LI
+></OL
+></LI
+></OL
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN1396">10.2. Name Resolution in a pure Unix/Linux world</H1
+><P
+>The key configuration files covered in this section are:</P
+><P
+></P
+><UL
+><LI
+><P
+><TT
+CLASS="FILENAME"
+>/etc/hosts</TT
+></P
+></LI
+><LI
+><P
+><TT
+CLASS="FILENAME"
+>/etc/resolv.conf</TT
+></P
+></LI
+><LI
+><P
+><TT
+CLASS="FILENAME"
+>/etc/host.conf</TT
+></P
+></LI
+><LI
+><P
+><TT
+CLASS="FILENAME"
+>/etc/nsswitch.conf</TT
+></P
+></LI
+></UL
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN1412">10.2.1. <TT
+CLASS="FILENAME"
+>/etc/hosts</TT
+></H2
+><P
+>Contains a static list of IP Addresses and names.
+eg:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+> 127.0.0.1 localhost localhost.localdomain
+ 192.168.1.1 bigbox.caldera.com bigbox alias4box</PRE
+></P
+><P
+>The purpose of <TT
+CLASS="FILENAME"
+>/etc/hosts</TT
+> is to provide a
name resolution mechanism so that uses do not need to remember
-IP addresses.
-</p><p>
-Network packets that are sent over the physical network transport
+IP addresses.</P
+><P
+>Network packets that are sent over the physical network transport
layer communicate not via IP addresses but rather using the Media
Access Control address, or MAC address. IP Addresses are currently
32 bits in length and are typically presented as four (4) decimal
-numbers that are separated by a dot (or period). eg: 168.192.1.1
-</p><p>
-MAC Addresses use 48 bits (or 6 bytes) and are typically represented
+numbers that are separated by a dot (or period). eg: 168.192.1.1</P
+><P
+>MAC Addresses use 48 bits (or 6 bytes) and are typically represented
as two digit hexadecimal numbers separated by colons. eg:
-40:8e:0a:12:34:56
-</p><p>
-Every network interfrace must have an MAC address. Associated with
+40:8e:0a:12:34:56</P
+><P
+>Every network interfrace must have an MAC address. Associated with
a MAC address there may be one or more IP addresses. There is NO
relationship between an IP address and a MAC address, all such assignments
are arbitary or discretionary in nature. At the most basic level all
@@ -58,15 +224,18 @@ addresses must be globally unique, and generally remains fixed for
any particular interface, the assignment of an IP address makes sense
from a network management perspective. More than one IP address can
be assigned per MAC address. One address must be the primary IP address,
-this is the address that will be returned in the ARP reply.
-</p><p>
-When a user or a process wants to communicate with another machine
-the protocol implementation ensures that the &quot;machine name&quot; or &quot;host
-name&quot; is resolved to an IP address in a manner that is controlled
+this is the address that will be returned in the ARP reply.</P
+><P
+>When a user or a process wants to communicate with another machine
+the protocol implementation ensures that the "machine name" or "host
+name" is resolved to an IP address in a manner that is controlled
by the TCP/IP configuration control files. The file
-<tt>/etc/hosts</tt> is one such file.
-</p><p>
-When the IP address of the destination interface has been
+<TT
+CLASS="FILENAME"
+>/etc/hosts</TT
+> is one such file.</P
+><P
+>When the IP address of the destination interface has been
determined a protocol called ARP/RARP is used to identify
the MAC address of the target interface. ARP stands for Address
Resolution Protocol, and is a broadcast oriented method that
@@ -76,41 +245,98 @@ address. Network interfaces are programmed to respond to two
MAC addresses only; their own unique address and the address
ff:ff:ff:ff:ff:ff. The reply packet from an ARP request will
contain the MAC address and the primary IP address for each
-interface.
-</p><p>
-The <tt>/etc/hosts</tt> file is foundational to all
+interface.</P
+><P
+>The <TT
+CLASS="FILENAME"
+>/etc/hosts</TT
+> file is foundational to all
Unix/Linux TCP/IP installations and as a minumum will contain
the localhost and local network interface IP addresses and the
primary names by which they are known within the local machine.
This file helps to prime the pump so that a basic level of name
resolution can exist before any other method of name resolution
-becomes available.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2900212"></a><tt>/etc/resolv.conf</tt></h3></div></div><p>
-This file tells the name resolution libraries:
-</p><div class="itemizedlist"><ul type="disc"><li><p>The name of the domain to which the machine
+becomes available.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN1428">10.2.2. <TT
+CLASS="FILENAME"
+>/etc/resolv.conf</TT
+></H2
+><P
+>This file tells the name resolution libraries:</P
+><P
+></P
+><UL
+><LI
+><P
+>The name of the domain to which the machine
belongs
- </p></li><li><p>The name(s) of any domains that should be
+ </P
+></LI
+><LI
+><P
+>The name(s) of any domains that should be
automatically searched when trying to resolve unqualified
host names to their IP address
- </p></li><li><p>The name or IP address of available Domain
+ </P
+></LI
+><LI
+><P
+>The name or IP address of available Domain
Name Servers that may be asked to perform name to address
translation lookups
- </p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2900256"></a><tt>/etc/host.conf</tt></h3></div></div><p>
-<tt>/etc/host.conf</tt> is the primary means by
+ </P
+></LI
+></UL
+></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN1439">10.2.3. <TT
+CLASS="FILENAME"
+>/etc/host.conf</TT
+></H2
+><P
+><TT
+CLASS="FILENAME"
+>/etc/host.conf</TT
+> is the primary means by
which the setting in /etc/resolv.conf may be affected. It is a
critical configuration file. This file controls the order by
-which name resolution may procede. The typical structure is:
-</p><pre class="programlisting">
- order hosts,bind
- multi on
-</pre><p>
-then both addresses should be returned. Please refer to the
-man page for host.conf for further details.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2900299"></a><tt>/etc/nsswitch.conf</tt></h3></div></div><p>
-This file controls the actual name resolution targets. The
-file typically has resolver object specifications as follows:
-</p><pre class="programlisting">
- # /etc/nsswitch.conf
+which name resolution may procede. The typical structure is:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+> order hosts,bind
+ multi on</PRE
+></P
+><P
+>then both addresses should be returned. Please refer to the
+man page for host.conf for further details.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN1447">10.2.4. <TT
+CLASS="FILENAME"
+>/etc/nsswitch.conf</TT
+></H2
+><P
+>This file controls the actual name resolution targets. The
+file typically has resolver object specifications as follows:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+> # /etc/nsswitch.conf
#
# Name Service Switch configuration file.
#
@@ -129,75 +355,99 @@ file typically has resolver object specifications as follows:
ethers: nis files
protocols: nis files
rpc: nis files
- services: nis files
-</pre><p>
-Of course, each of these mechanisms requires that the appropriate
-facilities and/or services are correctly configured.
-</p><p>
-It should be noted that unless a network request/message must be
+ services: nis files</PRE
+></P
+><P
+>Of course, each of these mechanisms requires that the appropriate
+facilities and/or services are correctly configured.</P
+><P
+>It should be noted that unless a network request/message must be
sent, TCP/IP networks are silent. All TCP/IP communications assumes a
-principal of speaking only when necessary.
-</p><p>
-Starting with version 2.2.0 samba has Linux support for extensions to
+principal of speaking only when necessary.</P
+><P
+>Starting with version 2.2.0 samba has Linux support for extensions to
the name service switch infrastructure so that linux clients will
be able to obtain resolution of MS Windows NetBIOS names to IP
Addresses. To gain this functionality Samba needs to be compiled
-with appropriate arguments to the make command (ie: <b>make
-nsswitch/libnss_wins.so</b>). The resulting library should
-then be installed in the <tt>/lib</tt> directory and
-the &quot;wins&quot; parameter needs to be added to the &quot;hosts:&quot; line in
-the <tt>/etc/nsswitch.conf</tt> file. At this point it
+with appropriate arguments to the make command (ie: <B
+CLASS="COMMAND"
+>make
+nsswitch/libnss_wins.so</B
+>). The resulting library should
+then be installed in the <TT
+CLASS="FILENAME"
+>/lib</TT
+> directory and
+the "wins" parameter needs to be added to the "hosts:" line in
+the <TT
+CLASS="FILENAME"
+>/etc/nsswitch.conf</TT
+> file. At this point it
will be possible to ping any MS Windows machine by it's NetBIOS
machine name, so long as that machine is within the workgroup to
-which both the samba machine and the MS Windows machine belong.
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2900394"></a>Name resolution as used within MS Windows networking</h2></div></div><p>
-MS Windows networking is predicated about the name each machine
+which both the samba machine and the MS Windows machine belong.</P
+></DIV
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN1459">10.3. Name resolution as used within MS Windows networking</H1
+><P
+>MS Windows networking is predicated about the name each machine
is given. This name is known variously (and inconsistently) as
-the &quot;computer name&quot;, &quot;machine name&quot;, &quot;networking name&quot;, &quot;netbios name&quot;,
-&quot;SMB name&quot;. All terms mean the same thing with the exception of
-&quot;netbios name&quot; which can apply also to the name of the workgroup or the
-domain name. The terms &quot;workgroup&quot; and &quot;domain&quot; are really just a
+the "computer name", "machine name", "networking name", "netbios name",
+"SMB name". All terms mean the same thing with the exception of
+"netbios name" which can apply also to the name of the workgroup or the
+domain name. The terms "workgroup" and "domain" are really just a
simply name with which the machine is associated. All NetBIOS names
are exactly 16 characters in length. The 16th character is reserved.
It is used to store a one byte value that indicates service level
information for the NetBIOS name that is registered. A NetBIOS machine
name is therefore registered for each service type that is provided by
-the client/server.
-</p><p>
-The following are typical NetBIOS name/service type registrations:
-</p><pre class="programlisting">
- Unique NetBIOS Names:
- MACHINENAME&lt;00&gt; = Server Service is running on MACHINENAME
- MACHINENAME&lt;03&gt; = Generic Machine Name (NetBIOS name)
- MACHINENAME&lt;20&gt; = LanMan Server service is running on MACHINENAME
- WORKGROUP&lt;1b&gt; = Domain Master Browser
+the client/server.</P
+><P
+>The following are typical NetBIOS name/service type registrations:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+> Unique NetBIOS Names:
+ MACHINENAME&#60;00&#62; = Server Service is running on MACHINENAME
+ MACHINENAME&#60;03&#62; = Generic Machine Name (NetBIOS name)
+ MACHINENAME&#60;20&#62; = LanMan Server service is running on MACHINENAME
+ WORKGROUP&#60;1b&#62; = Domain Master Browser
Group Names:
- WORKGROUP&lt;03&gt; = Generic Name registered by all members of WORKGROUP
- WORKGROUP&lt;1c&gt; = Domain Controllers / Netlogon Servers
- WORKGROUP&lt;1d&gt; = Local Master Browsers
- WORKGROUP&lt;1e&gt; = Internet Name Resolvers
-</pre><p>
-It should be noted that all NetBIOS machines register their own
+ WORKGROUP&#60;03&#62; = Generic Name registered by all members of WORKGROUP
+ WORKGROUP&#60;1c&#62; = Domain Controllers / Netlogon Servers
+ WORKGROUP&#60;1d&#62; = Local Master Browsers
+ WORKGROUP&#60;1e&#62; = Internet Name Resolvers</PRE
+></P
+><P
+>It should be noted that all NetBIOS machines register their own
names as per the above. This is in vast contrast to TCP/IP
installations where traditionally the system administrator will
determine in the /etc/hosts or in the DNS database what names
-are associated with each IP address.
-</p><p>
-One further point of clarification should be noted, the <tt>/etc/hosts</tt>
+are associated with each IP address.</P
+><P
+>One further point of clarification should be noted, the <TT
+CLASS="FILENAME"
+>/etc/hosts</TT
+>
file and the DNS records do not provide the NetBIOS name type information
that MS Windows clients depend on to locate the type of service that may
be needed. An example of this is what happens when an MS Windows client
-wants to locate a domain logon server. It finds this service and the IP
+wants to locate a domain logon server. It find this service and the IP
address of a server that provides it by performing a lookup (via a
NetBIOS broadcast) for enumeration of all machines that have
-registered the name type *&lt;1c&gt;. A logon request is then sent to each
+registered the name type *&#60;1c&#62;. A logon request is then sent to each
IP address that is returned in the enumerated list of IP addresses. Which
-ever machine first replies then ends up providing the logon services.
-</p><p>
-The name &quot;workgroup&quot; or &quot;domain&quot; really can be confusing since these
+ever machine first replies then ends up providing the logon services.</P
+><P
+>The name "workgroup" or "domain" really can be confusing since these
have the added significance of indicating what is the security
-architecture of the MS Windows network. The term &quot;workgroup&quot; indicates
+architecture of the MS Windows network. The term "workgroup" indicates
that the primary nature of the network environment is that of a
peer-to-peer design. In a WORKGROUP all machines are responsible for
their own security, and generally such security is limited to use of
@@ -205,9 +455,9 @@ just a password (known as SHARE MODE security). In most situations
with peer-to-peer networking the users who control their own machines
will simply opt to have no security at all. It is possible to have
USER MODE security in a WORKGROUP environment, thus requiring use
-of a user name and a matching password.
-</p><p>
-MS Windows networking is thus predetermined to use machine names
+of a user name and a matching password.</P
+><P
+>MS Windows networking is thus predetermined to use machine names
for all local and remote machine message passing. The protocol used is
called Server Message Block (SMB) and this is implemented using
the NetBIOS protocol (Network Basic Input Output System). NetBIOS can
@@ -216,39 +466,60 @@ the resulting protocol is called NetBEUI (Network Basic Extended User
Interface). NetBIOS can also be run over IPX (Internetworking Packet
Exchange) protocol as used by Novell NetWare, and it can be run
over TCP/IP protocols - in which case the resulting protocol is called
-NBT or NetBT, the NetBIOS over TCP/IP.
-</p><p>
-MS Windows machines use a complex array of name resolution mechanisms.
+NBT or NetBT, the NetBIOS over TCP/IP.</P
+><P
+>MS Windows machines use a complex array of name resolution mechanisms.
Since we are primarily concerned with TCP/IP this demonstration is
-limited to this area.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2899927"></a>The NetBIOS Name Cache</h3></div></div><p>
-All MS Windows machines employ an in memory buffer in which is
+limited to this area.</P
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN1471">10.3.1. The NetBIOS Name Cache</H2
+><P
+>All MS Windows machines employ an in memory buffer in which is
stored the NetBIOS names and IP addresses for all external
machines that that machine has communicated with over the
past 10-15 minutes. It is more efficient to obtain an IP address
for a machine from the local cache than it is to go through all the
-configured name resolution mechanisms.
-</p><p>
-If a machine whose name is in the local name cache has been shut
+configured name resolution mechanisms.</P
+><P
+>If a machine whose name is in the local name cache has been shut
down before the name had been expired and flushed from the cache, then
an attempt to exchange a message with that machine will be subject
to time-out delays. i.e.: Its name is in the cache, so a name resolution
lookup will succeed, but the machine can not respond. This can be
-frustrating for users - but it is a characteristic of the protocol.
-</p><p>
-The MS Windows utility that allows examination of the NetBIOS
-name cache is called &quot;nbtstat&quot;. The Samba equivalent of this
-is called &quot;nmblookup&quot;.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2899966"></a>The LMHOSTS file</h3></div></div><p>
-This file is usually located in MS Windows NT 4.0 or
-2000 in <tt>C:\WINNT\SYSTEM32\DRIVERS\ETC</tt> and contains
+frustrating for users - but it is a characteristic of the protocol.</P
+><P
+>The MS Windows utility that allows examination of the NetBIOS
+name cache is called "nbtstat". The Samba equivalent of this
+is called "nmblookup".</P
+></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN1476">10.3.2. The LMHOSTS file</H2
+><P
+>This file is usually located in MS Windows NT 4.0 or
+2000 in <TT
+CLASS="FILENAME"
+>C:\WINNT\SYSTEM32\DRIVERS\ETC</TT
+> and contains
the IP Address and the machine name in matched pairs. The
-<tt>LMHOSTS</tt> file performs NetBIOS name
-to IP address mapping.
-</p><p>
-It typically looks like:
-</p><pre class="programlisting">
- # Copyright (c) 1998 Microsoft Corp.
+<TT
+CLASS="FILENAME"
+>LMHOSTS</TT
+> file performs NetBIOS name
+to IP address mapping oriented.</P
+><P
+>It typically looks like:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+> # Copyright (c) 1998 Microsoft Corp.
#
# This is a sample LMHOSTS file used by the Microsoft Wins Client (NetBIOS
# over TCP/IP) stack for Windows98
@@ -257,7 +528,7 @@ It typically looks like:
# (NetBIOS) names. Each entry should be kept on an individual line.
# The IP address should be placed in the first column followed by the
# corresponding computername. The address and the comptername
- # should be separated by at least one space or tab. The &quot;#&quot; character
+ # should be separated by at least one space or tab. The "#" character
# is generally used to denote the start of a comment (see the exceptions
# below).
#
@@ -271,28 +542,28 @@ It typically looks like:
# #END_ALTERNATE
# \0xnn (non-printing character support)
#
- # Following any entry in the file with the characters &quot;#PRE&quot; will cause
+ # Following any entry in the file with the characters "#PRE" will cause
# the entry to be preloaded into the name cache. By default, entries are
# not preloaded, but are parsed only after dynamic name resolution fails.
#
- # Following an entry with the &quot;#DOM:&lt;domain&gt;&quot; tag will associate the
+ # Following an entry with the "#DOM:&lt;domain&gt;" tag will associate the
# entry with the domain specified by &lt;domain&gt;. This affects how the
# browser and logon services behave in TCP/IP environments. To preload
# the host name associated with #DOM entry, it is necessary to also add a
# #PRE to the line. The &lt;domain&gt; is always preloaded although it will not
# be shown when the name cache is viewed.
#
- # Specifying &quot;#INCLUDE &lt;filename&gt;&quot; will force the RFC NetBIOS (NBT)
+ # Specifying "#INCLUDE &lt;filename&gt;" will force the RFC NetBIOS (NBT)
# software to seek the specified &lt;filename&gt; and parse it as if it were
# local. &lt;filename&gt; is generally a UNC-based name, allowing a
# centralized lmhosts file to be maintained on a server.
# It is ALWAYS necessary to provide a mapping for the IP address of the
# server prior to the #INCLUDE. This mapping must use the #PRE directive.
- # In addtion the share &quot;public&quot; in the example below must be in the
- # LanManServer list of &quot;NullSessionShares&quot; in order for client machines to
+ # In addtion the share "public" in the example below must be in the
+ # LanManServer list of "NullSessionShares" in order for client machines to
# be able to read the lmhosts file successfully. This key is under
# \machine\system\currentcontrolset\services\lanmanserver\parameters\nullsessionshares
- # in the registry. Simply add &quot;public&quot; to the list found there.
+ # in the registry. Simply add "public" to the list found there.
#
# The #BEGIN_ and #END_ALTERNATE keywords allow multiple #INCLUDE
# statements to be grouped together. Any single successful include
@@ -305,7 +576,7 @@ It typically looks like:
# The following example illustrates all of these extensions:
#
# 102.54.94.97 rhino #PRE #DOM:networking #net group's DC
- # 102.54.94.102 &quot;appname \0x14&quot; #special app server
+ # 102.54.94.102 "appname \0x14" #special app server
# 102.54.94.123 popular #PRE #source server
# 102.54.94.117 localsrv #PRE #needed for the include
#
@@ -314,51 +585,564 @@ It typically looks like:
# #INCLUDE \\rhino\public\lmhosts
# #END_ALTERNATE
#
- # In the above example, the &quot;appname&quot; server contains a special
- # character in its name, the &quot;popular&quot; and &quot;localsrv&quot; server names are
- # preloaded, and the &quot;rhino&quot; server name is specified so it can be used
- # to later #INCLUDE a centrally maintained lmhosts file if the &quot;localsrv&quot;
+ # In the above example, the "appname" server contains a special
+ # character in its name, the "popular" and "localsrv" server names are
+ # preloaded, and the "rhino" server name is specified so it can be used
+ # to later #INCLUDE a centrally maintained lmhosts file if the "localsrv"
# system is unavailable.
#
# Note that the whole file is parsed including comments on each lookup,
# so keeping the number of comments to a minimum will improve performance.
# Therefore it is not advisable to simply add lmhosts file entries onto the
- # end of this file.
-</pre></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2900009"></a>HOSTS file</h3></div></div><p>
-This file is usually located in MS Windows NT 4.0 or 2000 in
-<tt>C:\WINNT\SYSTEM32\DRIVERS\ETC</tt> and contains
+ # end of this file.</PRE
+></P
+></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN1484">10.3.3. HOSTS file</H2
+><P
+>This file is usually located in MS Windows NT 4.0 or 2000 in
+<TT
+CLASS="FILENAME"
+>C:\WINNT\SYSTEM32\DRIVERS\ETC</TT
+> and contains
the IP Address and the IP hostname in matched pairs. It can be
used by the name resolution infrastructure in MS Windows, depending
on how the TCP/IP environment is configured. This file is in
-every way the equivalent of the Unix/Linux <tt>/etc/hosts</tt> file.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2900041"></a>DNS Lookup</h3></div></div><p>
-This capability is configured in the TCP/IP setup area in the network
+every way the equivalent of the Unix/Linux <TT
+CLASS="FILENAME"
+>/etc/hosts</TT
+> file.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN1489">10.3.4. DNS Lookup</H2
+><P
+>This capability is configured in the TCP/IP setup area in the network
configuration facility. If enabled an elaborate name resolution sequence
-is followed the precise nature of which is dependant on what the NetBIOS
+is followed the precise nature of which isdependant on what the NetBIOS
Node Type parameter is configured to. A Node Type of 0 means use
NetBIOS broadcast (over UDP broadcast) is first used if the name
that is the subject of a name lookup is not found in the NetBIOS name
cache. If that fails then DNS, HOSTS and LMHOSTS are checked. If set to
Node Type 8, then a NetBIOS Unicast (over UDP Unicast) is sent to the
WINS Server to obtain a lookup before DNS, HOSTS, LMHOSTS, or broadcast
-lookup is used.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2900053"></a>WINS Lookup</h3></div></div><p>
-A WINS (Windows Internet Name Server) service is the equivaent of the
+lookup is used.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN1492">10.3.5. WINS Lookup</H2
+><P
+>A WINS (Windows Internet Name Server) service is the equivaent of the
rfc1001/1002 specified NBNS (NetBIOS Name Server). A WINS server stores
the names and IP addresses that are registered by a Windows client
-if the TCP/IP setup has been given at least one WINS Server IP Address.
-</p><p>
-To configure Samba to be a WINS server the following parameter needs
-to be added to the <tt>smb.conf</tt> file:
-</p><pre class="programlisting">
- wins support = Yes
-</pre><p>
-To configure Samba to use a WINS server the following parameters are
-needed in the <tt>smb.conf</tt> file:
-</p><pre class="programlisting">
- wins support = No
- wins server = xxx.xxx.xxx.xxx
-</pre><p>
-where <i><tt>xxx.xxx.xxx.xxx</tt></i> is the IP address
-of the WINS server.
-</p></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="msdfs.html">Prev</a></td><td width="20%" align="center"><a accesskey="u" href="optional.html">Up</a></td><td width="40%" align="right"><a accesskey="n" href="securing-samba.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter22.Hosting a Microsoft Distributed File System tree on Samba</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">Chapter24.Securing Samba</td></tr></table></div></body></html>
+if the TCP/IP setup has been given at least one WINS Server IP Address.</P
+><P
+>To configure Samba to be a WINS server the following parameter needs
+to be added to the <TT
+CLASS="FILENAME"
+>smb.conf</TT
+> file:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+> wins support = Yes</PRE
+></P
+><P
+>To configure Samba to use a WINS server the following parameters are
+needed in the smb.conf file:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+> wins support = No
+ wins server = xxx.xxx.xxx.xxx</PRE
+></P
+><P
+>where <TT
+CLASS="REPLACEABLE"
+><I
+>xxx.xxx.xxx.xxx</I
+></TT
+> is the IP address
+of the WINS server.</P
+></DIV
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN1504">10.4. How browsing functions and how to deploy stable and
+dependable browsing using Samba</H1
+><P
+>As stated above, MS Windows machines register their NetBIOS names
+(i.e.: the machine name for each service type in operation) on start
+up. Also, as stated above, the exact method by which this name registration
+takes place is determined by whether or not the MS Windows client/server
+has been given a WINS server address, whether or not LMHOSTS lookup
+is enabled, or if DNS for NetBIOS name resolution is enabled, etc.</P
+><P
+>In the case where there is no WINS server all name registrations as
+well as name lookups are done by UDP broadcast. This isolates name
+resolution to the local subnet, unless LMHOSTS is used to list all
+names and IP addresses. In such situations Samba provides a means by
+which the samba server name may be forcibly injected into the browse
+list of a remote MS Windows network (using the "remote announce" parameter).</P
+><P
+>Where a WINS server is used, the MS Windows client will use UDP
+unicast to register with the WINS server. Such packets can be routed
+and thus WINS allows name resolution to function across routed networks.</P
+><P
+>During the startup process an election will take place to create a
+local master browser if one does not already exist. On each NetBIOS network
+one machine will be elected to function as the domain master browser. This
+domain browsing has nothing to do with MS security domain control.
+Instead, the domain master browser serves the role of contacting each local
+master browser (found by asking WINS or from LMHOSTS) and exchanging browse
+list contents. This way every master browser will eventually obtain a complete
+list of all machines that are on the network. Every 11-15 minutes an election
+is held to determine which machine will be the master browser. By the nature of
+the election criteria used, the machine with the highest uptime, or the
+most senior protocol version, or other criteria, will win the election
+as domain master browser.</P
+><P
+>Clients wishing to browse the network make use of this list, but also depend
+on the availability of correct name resolution to the respective IP
+address/addresses. </P
+><P
+>Any configuration that breaks name resolution and/or browsing intrinsics
+will annoy users because they will have to put up with protracted
+inability to use the network services.</P
+><P
+>Samba supports a feature that allows forced synchonisation
+of browse lists across routed networks using the "remote
+browse sync" parameter in the smb.conf file. This causes Samba
+to contact the local master browser on a remote network and
+to request browse list synchronisation. This effectively bridges
+two networks that are separated by routers. The two remote
+networks may use either broadcast based name resolution or WINS
+based name resolution, but it should be noted that the "remote
+browse sync" parameter provides browse list synchronisation - and
+that is distinct from name to address resolution, in other
+words, for cross subnet browsing to function correctly it is
+essential that a name to address resolution mechanism be provided.
+This mechanism could be via DNS, <TT
+CLASS="FILENAME"
+>/etc/hosts</TT
+>,
+and so on.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN1514">10.5. MS Windows security options and how to configure
+Samba for seemless integration</H1
+><P
+>MS Windows clients may use encrypted passwords as part of a
+challenege/response authentication model (a.k.a. NTLMv1) or
+alone, or clear text strings for simple password based
+authentication. It should be realized that with the SMB
+protocol the password is passed over the network either
+in plain text or encrypted, but not both in the same
+authentication requets.</P
+><P
+>When encrypted passwords are used a password that has been
+entered by the user is encrypted in two ways:</P
+><P
+></P
+><UL
+><LI
+><P
+>An MD4 hash of the UNICODE of the password
+ string. This is known as the NT hash.
+ </P
+></LI
+><LI
+><P
+>The password is converted to upper case,
+ and then padded or trucated to 14 bytes. This string is
+ then appended with 5 bytes of NULL characters and split to
+ form two 56 bit DES keys to encrypt a "magic" 8 byte value.
+ The resulting 16 bytes for the LanMan hash.
+ </P
+></LI
+></UL
+><P
+>You should refer to the <A
+HREF="ENCRYPTION.html"
+TARGET="_top"
+>Password Encryption</A
+> chapter in this HOWTO collection
+for more details on the inner workings</P
+><P
+>MS Windows 95 pre-service pack 1, MS Windows NT versions 3.x
+and version 4.0 pre-service pack 3 will use either mode of
+password authentication. All versions of MS Windows that follow
+these versions no longer support plain text passwords by default.</P
+><P
+>MS Windows clients have a habit of dropping network mappings that
+have been idle for 10 minutes or longer. When the user attempts to
+use the mapped drive connection that has been dropped, the client
+re-establishes the connection using
+a cached copy of the password.</P
+><P
+>When Microsoft changed the default password mode, they dropped support for
+caching of the plain text password. This means that when the registry
+parameter is changed to re-enable use of plain text passwords it appears to
+work, but when a dropped mapping attempts to revalidate it will fail if
+the remote authentication server does not support encrypted passwords.
+This means that it is definitely not a good idea to re-enable plain text
+password support in such clients.</P
+><P
+>The following parameters can be used to work around the
+issue of Windows 9x client upper casing usernames and
+password before transmitting them to the SMB server
+when using clear text authentication.</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+> <A
+HREF="smb.conf.5.html#PASSWORDLEVEL"
+TARGET="_top"
+>passsword level</A
+> = <TT
+CLASS="REPLACEABLE"
+><I
+>integer</I
+></TT
+>
+ <A
+HREF="smb.conf.5.html#USERNAMELEVEL"
+TARGET="_top"
+>username level</A
+> = <TT
+CLASS="REPLACEABLE"
+><I
+>integer</I
+></TT
+></PRE
+></P
+><P
+>By default Samba will lower case the username before attempting
+to lookup the user in the database of local system accounts.
+Because UNIX usernames conventionally only contain lower case
+character, the <TT
+CLASS="PARAMETER"
+><I
+>username level</I
+></TT
+> parameter
+is rarely even needed.</P
+><P
+>However, password on UNIX systems often make use of mixed case
+characters. This means that in order for a user on a Windows 9x
+client to connect to a Samba server using clear text authentication,
+the <TT
+CLASS="PARAMETER"
+><I
+>password level</I
+></TT
+> must be set to the maximum
+number of upper case letter which <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>could</I
+></SPAN
+> appear
+is a password. Note that is the server OS uses the traditional
+DES version of crypt(), then a <TT
+CLASS="PARAMETER"
+><I
+>password level</I
+></TT
+>
+of 8 will result in case insensitive passwords as seen from Windows
+users. This will also result in longer login times as Samba
+hash to compute the permutations of the password string and
+try them one by one until a match is located (or all combinations fail).</P
+><P
+>The best option to adopt is to enable support for encrypted passwords
+where ever Samba is used. There are three configuration possibilities
+for support of encrypted passwords:</P
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN1542">10.5.1. Use MS Windows NT as an authentication server</H2
+><P
+>This method involves the additions of the following parameters
+in the smb.conf file:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+> encrypt passwords = Yes
+ security = server
+ password server = "NetBIOS_name_of_PDC"</PRE
+></P
+><P
+>There are two ways of identifying whether or not a username and
+password pair was valid or not. One uses the reply information provided
+as part of the authentication messaging process, the other uses
+just and error code.</P
+><P
+>The down-side of this mode of configuration is the fact that
+for security reasons Samba will send the password server a bogus
+username and a bogus password and if the remote server fails to
+reject the username and password pair then an alternative mode
+of identification of validation is used. Where a site uses password
+lock out after a certain number of failed authentication attempts
+this will result in user lockouts.</P
+><P
+>Use of this mode of authentication does require there to be
+a standard Unix account for the user, this account can be blocked
+to prevent logons by other than MS Windows clients.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN1550">10.5.2. Make Samba a member of an MS Windows NT security domain</H2
+><P
+>This method involves additon of the following paramters in the smb.conf file:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+> encrypt passwords = Yes
+ security = domain
+ workgroup = "name of NT domain"
+ password server = *</PRE
+></P
+><P
+>The use of the "*" argument to "password server" will cause samba
+to locate the domain controller in a way analogous to the way
+this is done within MS Windows NT.</P
+><P
+>In order for this method to work the Samba server needs to join the
+MS Windows NT security domain. This is done as follows:</P
+><P
+></P
+><UL
+><LI
+><P
+>On the MS Windows NT domain controller using
+ the Server Manager add a machine account for the Samba server.
+ </P
+></LI
+><LI
+><P
+>Next, on the Linux system execute:
+ <B
+CLASS="COMMAND"
+>smbpasswd -r PDC_NAME -j DOMAIN_NAME</B
+>
+ </P
+></LI
+></UL
+><P
+>Use of this mode of authentication does require there to be
+a standard Unix account for the user in order to assign
+a uid once the account has been authenticated by the remote
+Windows DC. This account can be blocked to prevent logons by
+other than MS Windows clients by things such as setting an invalid
+shell in the <TT
+CLASS="FILENAME"
+>/etc/passwd</TT
+> entry.</P
+><P
+>An alternative to assigning UIDs to Windows users on a
+Samba member server is presented in the <A
+HREF="winbind.html"
+TARGET="_top"
+>Winbind Overview</A
+> chapter in
+this HOWTO collection.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN1567">10.5.3. Configure Samba as an authentication server</H2
+><P
+>This mode of authentication demands that there be on the
+Unix/Linux system both a Unix style account as well as an
+smbpasswd entry for the user. The Unix system account can be
+locked if required as only the encrypted password will be
+used for SMB client authentication.</P
+><P
+>This method involves addition of the following parameters to
+the smb.conf file:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>## please refer to the Samba PDC HOWTO chapter later in
+## this collection for more details
+[global]
+ encrypt passwords = Yes
+ security = user
+ domain logons = Yes
+ ; an OS level of 33 or more is recommended
+ os level = 33
+
+[NETLOGON]
+ path = /somewhare/in/file/system
+ read only = yes</PRE
+></P
+><P
+>in order for this method to work a Unix system account needs
+to be created for each user, as well as for each MS Windows NT/2000
+machine. The following structure is required.</P
+><DIV
+CLASS="SECT3"
+><H3
+CLASS="SECT3"
+><A
+NAME="AEN1574">10.5.3.1. Users</H3
+><P
+>A user account that may provide a home directory should be
+created. The following Linux system commands are typical of
+the procedure for creating an account.</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+> # useradd -s /bin/bash -d /home/"userid" -m "userid"
+ # passwd "userid"
+ Enter Password: &lt;pw&gt;
+
+ # smbpasswd -a "userid"
+ Enter Password: &lt;pw&gt;</PRE
+></P
+></DIV
+><DIV
+CLASS="SECT3"
+><H3
+CLASS="SECT3"
+><A
+NAME="AEN1579">10.5.3.2. MS Windows NT Machine Accounts</H3
+><P
+>These are required only when Samba is used as a domain
+controller. Refer to the Samba-PDC-HOWTO for more details.</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+> # useradd -s /bin/false -d /dev/null "machine_name"\$
+ # passwd -l "machine_name"\$
+ # smbpasswd -a -m "machine_name"</PRE
+></P
+></DIV
+></DIV
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN1584">10.6. Conclusions</H1
+><P
+>Samba provides a flexible means to operate as...</P
+><P
+></P
+><UL
+><LI
+><P
+>A Stand-alone server - No special action is needed
+ other than to create user accounts. Stand-alone servers do NOT
+ provide network logon services, meaning that machines that use this
+ server do NOT perform a domain logon but instead make use only of
+ the MS Windows logon which is local to the MS Windows
+ workstation/server.
+ </P
+></LI
+><LI
+><P
+>An MS Windows NT 3.x/4.0 security domain member.
+ </P
+></LI
+><LI
+><P
+>An alternative to an MS Windows NT 3.x/4.0
+ Domain Controller.
+ </P
+></LI
+></UL
+></DIV
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+SUMMARY="Footer navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="optional.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="samba-howto-collection.html"
+ACCESSKEY="H"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="unix-permissions.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>Optional configuration</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="optional.html"
+ACCESSKEY="U"
+>Up</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>UNIX Permission Bits and Windows NT Access Control Lists</TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+> \ No newline at end of file
diff --git a/docs/htmldocs/interdomaintrusts.html b/docs/htmldocs/interdomaintrusts.html
deleted file mode 100644
index c9fe4a533f..0000000000
--- a/docs/htmldocs/interdomaintrusts.html
+++ /dev/null
@@ -1,451 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<HTML
-><HEAD
-><TITLE
->Interdomain Trust Relationships</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
-REL="HOME"
-TITLE="SAMBA Project Documentation"
-HREF="samba-howto-collection.html"><LINK
-REL="UP"
-TITLE="Advanced Configuration"
-HREF="optional.html"><LINK
-REL="PREVIOUS"
-TITLE="Desktop Profile Management"
-HREF="profilemgmt.html"><LINK
-REL="NEXT"
-TITLE="PAM Configuration for Centrally Managed Authentication"
-HREF="pam.html"></HEAD
-><BODY
-CLASS="CHAPTER"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->SAMBA Project Documentation</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="profilemgmt.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
-></TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="pam.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="CHAPTER"
-><H1
-><A
-NAME="INTERDOMAINTRUSTS"
-></A
->Chapter 19. Interdomain Trust Relationships</H1
-><DIV
-CLASS="TOC"
-><DL
-><DT
-><B
->Table of Contents</B
-></DT
-><DT
->19.1. <A
-HREF="interdomaintrusts.html#AEN3446"
->Trust Relationship Background</A
-></DT
-><DT
->19.2. <A
-HREF="interdomaintrusts.html#AEN3455"
->Native MS Windows NT4 Trusts Configuration</A
-></DT
-><DD
-><DL
-><DT
->19.2.1. <A
-HREF="interdomaintrusts.html#AEN3458"
->NT4 as the Trusting Domain (ie. creating the trusted account)</A
-></DT
-><DT
->19.2.2. <A
-HREF="interdomaintrusts.html#AEN3461"
->NT4 as the Trusted Domain (ie. creating trusted account's password)</A
-></DT
-></DL
-></DD
-><DT
->19.3. <A
-HREF="interdomaintrusts.html#AEN3464"
->Configuring Samba NT-style Domain Trusts</A
-></DT
-><DD
-><DL
-><DT
->19.3.1. <A
-HREF="interdomaintrusts.html#AEN3468"
->Samba-3 as the Trusting Domain</A
-></DT
-><DT
->19.3.2. <A
-HREF="interdomaintrusts.html#AEN3480"
->Samba-3 as the Trusted Domain</A
-></DT
-></DL
-></DD
-></DL
-></DIV
-><P
->Samba-3 supports NT4 style domain trust relationships. This is feature that many sites
-will want to use if they migrate to Samba-3 from and NT4 style domain and do NOT want to
-adopt Active Directory or an LDAP based authentication back end. This section explains
-some background information regarding trust relationships and how to create them. It is now
-possible for Samba-3 to NT4 trust (and vice versa), as well as Samba3 to Samba3 trusts.</P
-><DIV
-CLASS="SECT1"
-><H1
-CLASS="SECT1"
-><A
-NAME="AEN3446"
->19.1. Trust Relationship Background</A
-></H1
-><P
->MS Windows NT3.x/4.0 type security domains employ a non-hierarchical security structure.
-The limitations of this architecture as it affects the scalability of MS Windows networking
-in large organisations is well known. Additionally, the flat-name space that results from
-this design significantly impacts the delegation of administrative responsibilities in
-large and diverse organisations.</P
-><P
->Microsoft developed Active Directory Service (ADS), based on Kerberos and LDAP, as a means
-of circumventing the limitations of the older technologies. Not every organisation is ready
-or willing to embrace ADS. For small companies the older NT4 style domain security paradigm
-is quite adequate, there thus remains an entrenched user base for whom there is no direct
-desire to go through a disruptive change to adopt ADS.</P
-><P
->Microsoft introduced with MS Windows NT the ability to allow differing security domains
-to affect a mechanism so that users from one domain may be given access rights and privileges
-in another domain. The language that describes this capability is couched in terms of
-<SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->Trusts</I
-></SPAN
->. Specifically, one domain will <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->trust</I
-></SPAN
-> the users
-from another domain. The domain from which users are available to another security domain is
-said to be a trusted domain. The domain in which those users have assigned rights and privileges
-is the trusting domain. With NT3.x/4.0 all trust relationships are always in one direction only,
-thus if users in both domains are to have privileges and rights in each others' domain, then it is
-necessary to establish two (2) relationships, one in each direction.</P
-><P
->In an NT4 style MS security domain, all trusts are non-transitive. This means that if there
-are three (3) domains (let's call them RED, WHITE, and BLUE) where RED and WHITE have a trust
-relationship, and WHITE and BLUE have a trust relationship, then it holds that there is no
-implied trust between the RED and BLUE domains. ie: Relationships are explicit and not
-transitive.</P
-><P
->New to MS Windows 2000 ADS security contexts is the fact that trust relationships are two-way
-by default. Also, all inter-ADS domain trusts are transitive. In the case of the RED, WHITE and BLUE
-domains above, with Windows 2000 and ADS the RED and BLUE domains CAN trust each other. This is
-an inherent feature of ADS domains. Samba-3 implements MS Windows NT4
-style Interdomain trusts and interoperates with MS Windows 200x ADS
-security domains in similar manner to MS Windows NT4 style domains.</P
-></DIV
-><DIV
-CLASS="SECT1"
-><H1
-CLASS="SECT1"
-><A
-NAME="AEN3455"
->19.2. Native MS Windows NT4 Trusts Configuration</A
-></H1
-><P
->There are two steps to creating an interdomain trust relationship.</P
-><DIV
-CLASS="SECT2"
-><H2
-CLASS="SECT2"
-><A
-NAME="AEN3458"
->19.2.1. NT4 as the Trusting Domain (ie. creating the trusted account)</A
-></H2
-><P
->For MS Windows NT4, all domain trust relationships are configured using the Domain User Manager.
-To affect a two way trust relationship it is necessary for each domain administrator to make
-available (for use by an external domain) it's security resources. This is done from the Domain
-User Manager Policies entry on the menu bar. From the Policy menu, select Trust Relationships, then
-next to the lower box that is labelled "Permitted to Trust this Domain" are two buttons, "Add" and
-"Remove". The "Add" button will open a panel in which needs to be entered the remote domain that
-will be able to assign user rights to your domain. In addition it is necessary to enter a password
-that is specific to this trust relationship. The password needs to be
-typed twice (for standard confirmation).</P
-></DIV
-><DIV
-CLASS="SECT2"
-><H2
-CLASS="SECT2"
-><A
-NAME="AEN3461"
->19.2.2. NT4 as the Trusted Domain (ie. creating trusted account's password)</A
-></H2
-><P
->A trust relationship will work only when the other (trusting) domain makes the appropriate connections
-with the trusted domain. To consumate the trust relationship the administrator will launch the
-Domain User Manager, from the menu select Policies, then select Trust Relationships, then click on the
-"Add" button that is next to the box that is labelled "Trusted Domains". A panel will open in
-which must be entered the name of the remote domain as well as the password assigned to that trust.</P
-></DIV
-></DIV
-><DIV
-CLASS="SECT1"
-><H1
-CLASS="SECT1"
-><A
-NAME="AEN3464"
->19.3. Configuring Samba NT-style Domain Trusts</A
-></H1
-><P
->This description is meant to be a fairly short introduction about how to set up a Samba server so
-that it could participate in interdomain trust relationships. Trust relationship support in Samba
-is in its early stage, so lot of things don't work yet.</P
-><P
->Each of the procedures described below is treated as they were performed with Windows NT4 Server on
-one end. The remote end could just as well be another Samba-3 domain. It can be clearly seen, after
-reading this document, that combining Samba-specific parts of what's written below leads to trust
-between domains in purely Samba environment.</P
-><DIV
-CLASS="SECT2"
-><H2
-CLASS="SECT2"
-><A
-NAME="AEN3468"
->19.3.1. Samba-3 as the Trusting Domain</A
-></H2
-><P
->In order to set Samba PDC to be trusted party of the relationship first you need
-to create special account for the domain that will be the trusting party. To do that,
-you can use the 'smbpasswd' utility. Creating the trusted domain account is very
-similiar to creating a trusted machine account. Suppose, your domain is
-called SAMBA, and the remote domain is called RUMBA. The first step
-will be to issue this command from your favourite shell:</P
-><P
-><PRE
-CLASS="SCREEN"
-> &nbsp;<SAMP
-CLASS="PROMPT"
->deity#</SAMP
-> <KBD
-CLASS="USERINPUT"
->smbpasswd -a -i rumba</KBD
->
- &nbsp; New SMB password: XXXXXXXX
- &nbsp; Retype SMB password: XXXXXXXX
- &nbsp; Added user rumba$</PRE
->
-
-where <VAR
-CLASS="PARAMETER"
->-a</VAR
-> means to add a new account into the
-passdb database and <VAR
-CLASS="PARAMETER"
->-i</VAR
-> means: ''create this
-account with the InterDomain trust flag''</P
-><P
->The account name will be 'rumba$' (the name of the remote domain)</P
-><P
->After issuing this command you'll be asked to enter the password for
-the account. You can use any password you want, but be aware that Windows NT will
-not change this password until 7 days following account creation.
-After the command returns successfully, you can look at the entry for new account
-(in the way depending on your configuration) and see that account's name is
-really RUMBA$ and it has 'I' flag in the flags field. Now you're ready to confirm
-the trust by establishing it from Windows NT Server.</P
-><P
->Open 'User Manager for Domains' and from menu 'Policies' select 'Trust Relationships...'.
-Right beside 'Trusted domains' list box press 'Add...' button. You will be prompted for
-the trusted domain name and the relationship password. Type in SAMBA, as this is
-your domain name, and the password used at the time of account creation.
-Press OK and, if everything went without incident, you will see 'Trusted domain relationship
-successfully established' message.</P
-></DIV
-><DIV
-CLASS="SECT2"
-><H2
-CLASS="SECT2"
-><A
-NAME="AEN3480"
->19.3.2. Samba-3 as the Trusted Domain</A
-></H2
-><P
->This time activities are somewhat reversed. Again, we'll assume that your domain
-controlled by the Samba PDC is called SAMBA and NT-controlled domain is called RUMBA.</P
-><P
->The very first thing requirement is to add an account for the SAMBA domain on RUMBA's PDC.</P
-><P
->Launch the Domain User Manager, then from the menu select 'Policies', 'Trust Relationships'.
-Now, next to 'Trusted Domains' box press the 'Add' button, and type in the name of the trusted
-domain (SAMBA) and password securing the relationship.</P
-><P
->The password can be arbitrarily chosen. It is easy to change it the password
-from Samba server whenever you want. After confirming the password your account is
-ready for use. Now it's Samba's turn.</P
-><P
->Using your favourite shell while being logged in as root, issue this command:</P
-><P
-><SAMP
-CLASS="PROMPT"
->deity# </SAMP
-><KBD
-CLASS="USERINPUT"
->net rpc trustdom establish rumba</KBD
-></P
-><P
->You will be prompted for the password you just typed on your Windows NT4 Server box.
-Don not worry if you see an error message that mentions a returned code of
-<SPAN
-CLASS="ERRORNAME"
->NT_STATUS_NOLOGON_INTERDOMAIN_TRUST_ACCOUNT</SPAN
->. It means the
-password you gave is correct and the NT4 Server says the account is
-ready for interdomain connection and not for ordinary
-connection. After that, be patient it can take a while (especially
-in large networks), you should see the 'Success' message. Congratulations! Your trust
-relationship has just been established.</P
-><DIV
-CLASS="NOTE"
-><P
-></P
-><TABLE
-CLASS="NOTE"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->Note that you have to run this command as root because you must have write access to
-the <TT
-CLASS="FILENAME"
->secrets.tdb</TT
-> file.</P
-></TD
-></TR
-></TABLE
-></DIV
-></DIV
-></DIV
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="profilemgmt.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="samba-howto-collection.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="pam.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Desktop Profile Management</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="optional.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->PAM Configuration for Centrally Managed Authentication</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
-> \ No newline at end of file
diff --git a/docs/htmldocs/introduction.html b/docs/htmldocs/introduction.html
index f54776747c..762d56ba6a 100644
--- a/docs/htmldocs/introduction.html
+++ b/docs/htmldocs/introduction.html
@@ -1,6 +1,421 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>PartI.General Installation</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"><link rel="home" href="index.html" title="SAMBA Project Documentation"><link rel="up" href="index.html" title="SAMBA Project Documentation"><link rel="previous" href="index.html" title="SAMBA Project Documentation"><link rel="next" href="IntroSMB.html" title="Chapter1.Introduction to Samba"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">PartI.General Installation</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="index.html">Prev</a></td><th width="60%" align="center"></th><td width="20%" align="right"><a accesskey="n" href="IntroSMB.html">Next</a></td></tr></table><hr></div><div class="part" lang="en"><div class="titlepage"><div><h1 class="title"><a name="introduction"></a>General Installation</h1></div></div><div class="partintro" lang="en"><div><div><h1 class="title"><a name="id2861627"></a>Preparing Samba for Configuration</h1></div></div><p>This section of the Samba-HOWTO-Collection contains general info on how to install samba
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<HTML
+><HEAD
+><TITLE
+>General installation</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
+REL="HOME"
+TITLE="SAMBA Project Documentation"
+HREF="samba-howto-collection.html"><LINK
+REL="PREVIOUS"
+TITLE="SAMBA Project Documentation"
+HREF="samba-howto-collection.html"><LINK
+REL="NEXT"
+TITLE="How to Install and Test SAMBA"
+HREF="install.html"></HEAD
+><BODY
+CLASS="PART"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><TABLE
+SUMMARY="Header navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>SAMBA Project Documentation</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="samba-howto-collection.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+></TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="install.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="PART"
+><A
+NAME="INTRODUCTION"><DIV
+CLASS="TITLEPAGE"
+><H1
+CLASS="TITLE"
+>I. General installation</H1
+><DIV
+CLASS="PARTINTRO"
+><A
+NAME="AEN21"><H1
+>Introduction</H1
+><P
+>This part contains general info on how to install samba
and how to configure the parts of samba you will most likely need.
-PLEASE read this.</p><div class="toc"><p><b>Table of Contents</b></p><dl><dt>1. <a href="IntroSMB.html">Introduction to Samba</a></dt><dd><dl><dt><a href="IntroSMB.html#id2810945">Background</a></dt><dt><a href="IntroSMB.html#id2811002">Terminology</a></dt><dt><a href="IntroSMB.html#id2811109">Related Projects</a></dt><dt><a href="IntroSMB.html#id2810650">SMB Methodology</a></dt><dt><a href="IntroSMB.html#id2807791">Additional Resources</a></dt><dt><a href="IntroSMB.html#id2810803">Epilogue</a></dt><dt><a href="IntroSMB.html#id2810879">Miscellaneous</a></dt></dl></dd><dt>2. <a href="install.html">How to Install and Test SAMBA</a></dt><dd><dl><dt><a href="install.html#id2812103">Obtaining and installing samba</a></dt><dt><a href="install.html#id2812254">Configuring samba</a></dt><dd><dl><dt><a href="install.html#id2812000">Editing the smb.conf file</a></dt><dt><a href="install.html#id2875811">SWAT</a></dt></dl></dd><dt><a href="install.html#id2875850">Try listing the shares available on your
- server</a></dt><dt><a href="install.html#id2875900">Try connecting with the unix client</a></dt><dt><a href="install.html#id2876004">Try connecting from a DOS, WfWg, Win9x, WinNT,
- Win2k, OS/2, etc... client</a></dt><dt><a href="install.html#id2876065">What If Things Don't Work?</a></dt></dl></dd></dl></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="index.html">Prev</a></td><td width="20%" align="center"><a accesskey="u" href="index.html">Up</a></td><td width="40%" align="right"><a accesskey="n" href="IntroSMB.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">SAMBA Project Documentation</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">Chapter1.Introduction to Samba</td></tr></table></div></body></html>
+PLEASE read this.</P
+></DIV
+><DIV
+CLASS="TOC"
+><DL
+><DT
+><B
+>Table of Contents</B
+></DT
+><DT
+>1. <A
+HREF="install.html"
+>How to Install and Test SAMBA</A
+></DT
+><DD
+><DL
+><DT
+>1.1. <A
+HREF="install.html#AEN26"
+>Read the man pages</A
+></DT
+><DT
+>1.2. <A
+HREF="install.html#AEN36"
+>Building the Binaries</A
+></DT
+><DT
+>1.3. <A
+HREF="install.html#AEN64"
+>The all important step</A
+></DT
+><DT
+>1.4. <A
+HREF="install.html#AEN68"
+>Create the smb configuration file.</A
+></DT
+><DT
+>1.5. <A
+HREF="install.html#AEN82"
+>Test your config file with
+ <B
+CLASS="COMMAND"
+>testparm</B
+></A
+></DT
+><DT
+>1.6. <A
+HREF="install.html#AEN90"
+>Starting the smbd and nmbd</A
+></DT
+><DD
+><DL
+><DT
+>1.6.1. <A
+HREF="install.html#AEN100"
+>Starting from inetd.conf</A
+></DT
+><DT
+>1.6.2. <A
+HREF="install.html#AEN129"
+>Alternative: starting it as a daemon</A
+></DT
+></DL
+></DD
+><DT
+>1.7. <A
+HREF="install.html#AEN145"
+>Try listing the shares available on your
+ server</A
+></DT
+><DT
+>1.8. <A
+HREF="install.html#AEN154"
+>Try connecting with the unix client</A
+></DT
+><DT
+>1.9. <A
+HREF="install.html#AEN170"
+>Try connecting from a DOS, WfWg, Win9x, WinNT,
+ Win2k, OS/2, etc... client</A
+></DT
+><DT
+>1.10. <A
+HREF="install.html#AEN184"
+>What If Things Don't Work?</A
+></DT
+><DD
+><DL
+><DT
+>1.10.1. <A
+HREF="install.html#AEN189"
+>Diagnosing Problems</A
+></DT
+><DT
+>1.10.2. <A
+HREF="install.html#AEN193"
+>Scope IDs</A
+></DT
+><DT
+>1.10.3. <A
+HREF="install.html#AEN196"
+>Choosing the Protocol Level</A
+></DT
+><DT
+>1.10.4. <A
+HREF="install.html#AEN205"
+>Printing from UNIX to a Client PC</A
+></DT
+><DT
+>1.10.5. <A
+HREF="install.html#AEN210"
+>Locking</A
+></DT
+><DT
+>1.10.6. <A
+HREF="install.html#AEN219"
+>Mapping Usernames</A
+></DT
+></DL
+></DD
+></DL
+></DD
+><DT
+>2. <A
+HREF="improved-browsing.html"
+>Improved browsing in samba</A
+></DT
+><DD
+><DL
+><DT
+>2.1. <A
+HREF="improved-browsing.html#AEN229"
+>Overview of browsing</A
+></DT
+><DT
+>2.2. <A
+HREF="improved-browsing.html#AEN233"
+>Browsing support in samba</A
+></DT
+><DT
+>2.3. <A
+HREF="improved-browsing.html#AEN242"
+>Problem resolution</A
+></DT
+><DT
+>2.4. <A
+HREF="improved-browsing.html#AEN249"
+>Browsing across subnets</A
+></DT
+><DD
+><DL
+><DT
+>2.4.1. <A
+HREF="improved-browsing.html#AEN254"
+>How does cross subnet browsing work ?</A
+></DT
+></DL
+></DD
+><DT
+>2.5. <A
+HREF="improved-browsing.html#AEN289"
+>Setting up a WINS server</A
+></DT
+><DT
+>2.6. <A
+HREF="improved-browsing.html#AEN308"
+>Setting up Browsing in a WORKGROUP</A
+></DT
+><DT
+>2.7. <A
+HREF="improved-browsing.html#AEN326"
+>Setting up Browsing in a DOMAIN</A
+></DT
+><DT
+>2.8. <A
+HREF="improved-browsing.html#AEN336"
+>Forcing samba to be the master</A
+></DT
+><DT
+>2.9. <A
+HREF="improved-browsing.html#AEN345"
+>Making samba the domain master</A
+></DT
+><DT
+>2.10. <A
+HREF="improved-browsing.html#AEN363"
+>Note about broadcast addresses</A
+></DT
+><DT
+>2.11. <A
+HREF="improved-browsing.html#AEN366"
+>Multiple interfaces</A
+></DT
+></DL
+></DD
+><DT
+>3. <A
+HREF="browsing-quick.html"
+>Quick Cross Subnet Browsing / Cross Workgroup Browsing guide</A
+></DT
+><DD
+><DL
+><DT
+>3.1. <A
+HREF="browsing-quick.html#AEN377"
+>Discussion</A
+></DT
+><DT
+>3.2. <A
+HREF="browsing-quick.html#AEN385"
+>Use of the "Remote Announce" parameter</A
+></DT
+><DT
+>3.3. <A
+HREF="browsing-quick.html#AEN399"
+>Use of the "Remote Browse Sync" parameter</A
+></DT
+><DT
+>3.4. <A
+HREF="browsing-quick.html#AEN404"
+>Use of WINS</A
+></DT
+><DT
+>3.5. <A
+HREF="browsing-quick.html#AEN415"
+>Do NOT use more than one (1) protocol on MS Windows machines</A
+></DT
+><DT
+>3.6. <A
+HREF="browsing-quick.html#AEN421"
+>Name Resolution Order</A
+></DT
+></DL
+></DD
+><DT
+>4. <A
+HREF="pwencrypt.html"
+>LanMan and NT Password Encryption in Samba</A
+></DT
+><DD
+><DL
+><DT
+>4.1. <A
+HREF="pwencrypt.html#AEN457"
+>Introduction</A
+></DT
+><DT
+>4.2. <A
+HREF="pwencrypt.html#AEN462"
+>Important Notes About Security</A
+></DT
+><DD
+><DL
+><DT
+>4.2.1. <A
+HREF="pwencrypt.html#AEN481"
+>Advantages of SMB Encryption</A
+></DT
+><DT
+>4.2.2. <A
+HREF="pwencrypt.html#AEN488"
+>Advantages of non-encrypted passwords</A
+></DT
+></DL
+></DD
+><DT
+>4.3. <A
+HREF="pwencrypt.html#AEN497"
+>The smbpasswd Command</A
+></DT
+></DL
+></DD
+></DL
+></DIV
+></DIV
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+SUMMARY="Footer navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="samba-howto-collection.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="samba-howto-collection.html"
+ACCESSKEY="H"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="install.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>SAMBA Project Documentation</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+>&nbsp;</TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>How to Install and Test SAMBA</TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+> \ No newline at end of file
diff --git a/docs/htmldocs/introsmb.html b/docs/htmldocs/introsmb.html
deleted file mode 100644
index 52db6a8a95..0000000000
--- a/docs/htmldocs/introsmb.html
+++ /dev/null
@@ -1,659 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<HTML
-><HEAD
-><TITLE
->Introduction to Samba</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
-REL="HOME"
-TITLE="SAMBA Project Documentation"
-HREF="samba-howto-collection.html"><LINK
-REL="UP"
-TITLE="General installation"
-HREF="introduction.html"><LINK
-REL="PREVIOUS"
-TITLE="General installation"
-HREF="introduction.html"><LINK
-REL="NEXT"
-TITLE="How to Install and Test SAMBA"
-HREF="install.html"></HEAD
-><BODY
-CLASS="CHAPTER"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->SAMBA Project Documentation</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="introduction.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
-></TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="install.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="CHAPTER"
-><H1
-><A
-NAME="INTROSMB"
-></A
->Chapter 1. Introduction to Samba</H1
-><DIV
-CLASS="TOC"
-><DL
-><DT
-><B
->Table of Contents</B
-></DT
-><DT
->1.1. <A
-HREF="introsmb.html#AEN61"
->Background</A
-></DT
-><DT
->1.2. <A
-HREF="introsmb.html#AEN67"
->Terminology</A
-></DT
-><DT
->1.3. <A
-HREF="introsmb.html#AEN91"
->Related Projects</A
-></DT
-><DT
->1.4. <A
-HREF="introsmb.html#AEN100"
->SMB Methodology</A
-></DT
-><DT
->1.5. <A
-HREF="introsmb.html#AEN115"
->Additional Resources</A
-></DT
-><DT
->1.6. <A
-HREF="introsmb.html#AEN151"
->Epilogue</A
-></DT
-><DT
->1.7. <A
-HREF="introsmb.html#AEN162"
->Miscellaneous</A
-></DT
-></DL
-></DIV
-><P
-><SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->"If you understand what you're doing, you're not learning anything."
--- Anonymous</I
-></SPAN
-></P
-><P
->Samba is a file and print server for Windows-based clients using TCP/IP as the underlying
-transport protocol. In fact, it can support any SMB/CIFS-enabled client. One of Samba's big
-strengths is that you can use it to blend your mix of Windows and Linux machines together
-without requiring a separate Windows NT/2000/2003 Server. Samba is actively being developed
-by a global team of about 30 active programmers and was originally developed by Andrew Tridgell.</P
-><DIV
-CLASS="SECT1"
-><H1
-CLASS="SECT1"
-><A
-NAME="AEN61"
->1.1. Background</A
-></H1
-><P
->Once long ago, there was a buzzword referred to as DCE/RPC. This stood for Distributed
-Computing Environment/Remote Procedure Calls and conceptually was a good idea. It was
-originally developed by Apollo/HP as NCA 1.0 (Network Computing Architecture) and only
-ran over UDP. When there was a need to run it over TCP so that it would be compatible
-with DECnet 3.0, it was redesigned, submitted to The Open Group, and officially became
-known as DCE/RPC. Microsoft came along and decided, rather than pay $20 per seat to
-license this technology, to reimplement DCE/RPC themselves as MSRPC. From this, the
-concept continued in the form of SMB (Server Message Block, or the "what") using the
-NetBIOS (Network Basic Input/Output System, or the "how") compatibility layer. You can
-run SMB (i.e., transport) over several different protocols; many different implementations
-arose as a result, including NBIPX (NetBIOS over IPX, NwLnkNb, or NWNBLink) and NBT
-(NetBIOS over TCP/IP, or NetBT). As the years passed, NBT became the most common form
-of implementation until the advance of "Direct-Hosted TCP" -- the Microsoft marketing
-term for eliminating NetBIOS entirely and running SMB by itself across TCP port 445
-only. As of yet, direct-hosted TCP has yet to catch on.</P
-><P
->Perhaps the best summary of the origins of SMB are voiced in the 1997 article titled, CIFS:
-Common Insecurities Fail Scrutiny:</P
-><P
-><SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->Several megabytes of NT-security archives, random whitepapers, RFCs, the CIFS spec, the Samba
-stuff, a few MS knowledge-base articles, strings extracted from binaries, and packet dumps have
-been dutifully waded through during the information-gathering stages of this project, and there
-are *still* many missing pieces... While often tedious, at least the way has been generously
-littered with occurrences of clapping hand to forehead and muttering 'crikey, what are they
-thinking?</I
-></SPAN
-></P
-></DIV
-><DIV
-CLASS="SECT1"
-><H1
-CLASS="SECT1"
-><A
-NAME="AEN67"
->1.2. Terminology</A
-></H1
-><P
-></P
-><UL
-><LI
-><P
-> SMB: Acronym for "Server Message Block". This is Microsoft's file and printer sharing protocol.
- </P
-></LI
-><LI
-><P
-> CIFS: Acronym for "Common Internet File System". Around 1996, Microsoft apparently
- decided that SMB needed the word "Internet" in it, so they changed it to CIFS.
- </P
-></LI
-><LI
-><P
-> Direct-Hosted: A method of providing file/printer sharing services over port 445/tcp
- only using DNS for name resolution instead of WINS.
- </P
-></LI
-><LI
-><P
-> IPC: Acronym for "Inter-Process Communication". A method to communicate specific
- information between programs.
- </P
-></LI
-><LI
-><P
-> Marshalling: - A method of serializing (i.e., sequential ordering of) variable data
- suitable for transmission via a network connection or storing in a file. The source
- data can be re-created using a similar process called unmarshalling.
- </P
-></LI
-><LI
-><P
-> NetBIOS: Acronym for "Network Basic Input/Output System". This is not a protocol;
- it is a method of communication across an existing protocol. This is a standard which
- was originally developed for IBM by Sytek in 1983. To exaggerate the analogy a bit,
- it can help to think of this in comparison your computer's BIOS -- it controls the
- essential functions of your input/output hardware -- whereas NetBIOS controls the
- essential functions of your input/output traffic via the network. Again, this is a bit
- of an exaggeration but it should help that paradigm shift. What is important to realize
- is that NetBIOS is a transport standard, not a protocol. Unfortunately, even technically
- brilliant people tend to interchange NetBIOS with terms like NetBEUI without a second
- thought; this will cause no end (and no doubt) of confusion.
- </P
-></LI
-><LI
-><P
-> NetBEUI: Acronym for the "NetBIOS Extended User Interface". Unlike NetBIOS, NetBEUI
- is a protocol, not a standard. It is also not routable, so traffic on one side of a
- router will be unable to communicate with the other side. Understanding NetBEUI is
- not essential to deciphering SMB; however it helps to point out that it is not the
- same as NetBIOS and to improve your score in trivia at parties. NetBEUI was originally
- referred to by Microsoft as "NBF", or "The Windows NT NetBEUI Frame protocol driver".
- It is not often heard from these days.
- </P
-></LI
-><LI
-><P
-> NBT: Acronym for "NetBIOS over TCP"; also known as "NetBT". Allows the continued use
- of NetBIOS traffic proxied over TCP/IP. As a result, NetBIOS names are made
- to IP addresses and NetBIOS name types are conceptually equivalent to TCP/IP ports.
- This is how file and printer sharing are accomplished in Windows 95/98/ME. They
- traditionally rely on three ports: NetBIOS Name Service (nbname) via UDP port 137,
- NetBIOS Datagram Service (nbdatagram) via UDP port 138, and NetBIOS Session Service
- (nbsession) via TCP port 139. All name resolution is done via WINS, NetBIOS broadcasts,
- and DNS. NetBIOS over TCP is documented in RFC 1001 (Concepts and methods) and RFC 1002
- (Detailed specifications).
- </P
-></LI
-><LI
-><P
-> W2K: Acronym for Windows 2000 Professional or Server
- </P
-></LI
-><LI
-><P
-> W3K: Acronym for Windows 2003 Server
- </P
-></LI
-></UL
-><P
->If you plan on getting help, make sure to subscribe to the Samba Mailing List (available at
-http://www.samba.org). Optionally, you could just search mailing.unix.samba at http://groups.google.com</P
-></DIV
-><DIV
-CLASS="SECT1"
-><H1
-CLASS="SECT1"
-><A
-NAME="AEN91"
->1.3. Related Projects</A
-></H1
-><P
->Currently, there are two projects that are directly related to Samba: SMBFS and CIFS network
-client file systems for Linux, both available in the Linux kernel itself.</P
-><P
-></P
-><UL
-><LI
-><P
-> SMBFS (Server Message Block File System) allows you to mount SMB shares (the protocol
- that Microsoft Windows and OS/2 Lan Manager use to share files and printers
- over local networks) and access them just like any other Unix directory. This is useful
- if you just want to mount such filesystems without being a SMBFS server.
- </P
-></LI
-><LI
-><P
-> CIFS (Common Internet File System) is the successor to SMB, and is actively being worked
- on in the upcoming version of the Linux kernel. The intent of this module is to
- provide advanced network file system functionality including support for dfs (heirarchical
- name space), secure per-user session establishment, safe distributed caching (oplock),
- optional packet signing, Unicode and other internationalization improvements, and optional
- Winbind (nsswitch) integration.
- </P
-></LI
-></UL
-><P
->Again, it's important to note that these are implementations for client filesystems, and have
-nothing to do with acting as a file and print server for SMB/CIFS clients.</P
-></DIV
-><DIV
-CLASS="SECT1"
-><H1
-CLASS="SECT1"
-><A
-NAME="AEN100"
->1.4. SMB Methodology</A
-></H1
-><P
->Traditionally, SMB uses UDP port 137 (NetBIOS name service, or netbios-ns),
-UDP port 138 (NetBIOS datagram service, or netbios-dgm), and TCP port 139 (NetBIOS
-session service, or netbios-ssn). Anyone looking at their network with a good
-packet sniffer will be amazed at the amount of traffic generated by just opening
-up a single file. In general, SMB sessions are established in the following order:</P
-><P
-></P
-><UL
-><LI
-><P
-> "TCP Connection" - establish 3-way handshake (connection) to port 139/tcp
- or 445/tcp.
- </P
-></LI
-><LI
-><P
-> "NetBIOS Session Request" - using the following "Calling Names": The local
- machine's NetBIOS name plus the 16th character 0x00; The server's NetBIOS
- name plus the 16th character 0x20
- </P
-></LI
-><LI
-><P
-> "SMB Negotiate Protocol" - determine the protocol dialect to use, which will
- be one of the following: PC Network Program 1.0 (Core) - share level security
- mode only; Microsoft Networks 1.03 (Core Plus) - share level security
- mode only; Lanman1.0 (LAN Manager 1.0) - uses Challenge/Response
- Authentication; Lanman2.1 (LAN Manager 2.1) - uses Challenge/Response
- Authentication; NT LM 0.12 (NT LM 0.12) - uses Challenge/Response
- Authentication
- </P
-></LI
-><LI
-><P
-> SMB Session Startup. Passwords are encrypted (or not) according to one of
- the following methods: Null (no encryption); Cleartext (no encryption); LM
- and NTLM; NTLM; NTLMv2
- </P
-></LI
-><LI
-><P
-> SMB Tree Connect: Connect to a share name (e.g., \\servername\share); Connect
- to a service type (e.g., IPC$ named pipe)
- </P
-></LI
-></UL
-><P
->A good way to examine this process in depth is to try out SecurityFriday's SWB program
-at http://www.securityfriday.com/ToolDownload/SWB/swb_doc.html. It allows you to
-walk through the establishment of a SMB/CIFS session step by step.</P
-></DIV
-><DIV
-CLASS="SECT1"
-><H1
-CLASS="SECT1"
-><A
-NAME="AEN115"
->1.5. Additional Resources</A
-></H1
-><P
-></P
-><UL
-><LI
-><P
-> <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->CIFS: Common Insecurities Fail Scrutiny</I
-></SPAN
-> by "Hobbit",
- http://hr.uoregon.edu/davidrl/cifs.txt
- </P
-></LI
-><LI
-><P
-> <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->Doing the Samba on Windows</I
-></SPAN
-> by Financial Review,
- http://afr.com/it/2002/10/01/FFXDF43AP6D.html
- </P
-></LI
-><LI
-><P
-> <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->Implementing CIFS</I
-></SPAN
-> by Christopher R. Hertel,
- http://ubiqx.org/cifs/
- </P
-></LI
-><LI
-><P
-> <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->Just What Is SMB?</I
-></SPAN
-> by Richard Sharpe,
- http://samba.anu.edu.au/cifs/docs/what-is-smb.html
- </P
-></LI
-><LI
-><P
-> <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->Opening Windows Everywhere</I
-></SPAN
-> by Mike Warfield,
- http://www.linux-mag.com/1999-05/samba_01.html
- </P
-></LI
-><LI
-><P
-> <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->SMB HOWTO</I
-></SPAN
-> by David Wood,
- http://www.tldp.org/HOWTO/SMB-HOWTO.html
- </P
-></LI
-><LI
-><P
-> <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->SMB/CIFS by The Root</I
-></SPAN
-> by "ledin",
- http://www.phrack.org/phrack/60/p60-0x0b.txt
- </P
-></LI
-><LI
-><P
-> <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->The Story of Samba</I
-></SPAN
-> by Christopher R. Hertel,
- http://www.linux-mag.com/1999-09/samba_01.html
- </P
-></LI
-><LI
-><P
-> <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->The Unofficial Samba HOWTO</I
-></SPAN
-> by David Lechnyr,
- http://hr.uoregon.edu/davidrl/samba/
- </P
-></LI
-><LI
-><P
-> <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->Understanding the Network Neighborhood</I
-></SPAN
-> by Christopher R. Hertel,
- http://www.linux-mag.com/2001-05/smb_01.html
- </P
-></LI
-><LI
-><P
-> <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->Using Samba as a PDC</I
-></SPAN
-> by Andrew Bartlett,
- http://www.linux-mag.com/2002-02/samba_01.html
- </P
-></LI
-></UL
-></DIV
-><DIV
-CLASS="SECT1"
-><H1
-CLASS="SECT1"
-><A
-NAME="AEN151"
->1.6. Epilogue</A
-></H1
-><P
-><SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->"What's fundamentally wrong is that nobody ever had any taste when they
-did it. Microsoft has been very much into making the user interface look good,
-but internally it's just a complete mess. And even people who program for Microsoft
-and who have had years of experience, just don't know how it works internally.
-Worse, nobody dares change it. Nobody dares to fix bugs because it's such a
-mess that fixing one bug might just break a hundred programs that depend on
-that bug. And Microsoft isn't interested in anyone fixing bugs -- they're interested
-in making money. They don't have anybody who takes pride in Windows 95 as an
-operating system.</I
-></SPAN
-></P
-><P
-><SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->People inside Microsoft know it's a bad operating system and they still
-continue obviously working on it because they want to get the next version out
-because they want to have all these new features to sell more copies of the
-system.</I
-></SPAN
-></P
-><P
-><SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->The problem with that is that over time, when you have this kind of approach,
-and because nobody understands it, because nobody REALLY fixes bugs (other than
-when they're really obvious), the end result is really messy. You can't trust
-it because under certain circumstances it just spontaneously reboots or just
-halts in the middle of something that shouldn't be strange. Normally it works
-fine and then once in a blue moon for some completely unknown reason, it's dead,
-and nobody knows why. Not Microsoft, not the experienced user and certainly
-not the completely clueless user who probably sits there shivering thinking
-"What did I do wrong?" when they didn't do anything wrong at all.</I
-></SPAN
-></P
-><P
-><SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->That's what's really irritating to me."</I
-></SPAN
-></P
-><P
->-- Linus Torvalds, from an interview with BOOT Magazine, Sept 1998
-(http://hr.uoregon.edu/davidrl/boot.txt)</P
-></DIV
-><DIV
-CLASS="SECT1"
-><H1
-CLASS="SECT1"
-><A
-NAME="AEN162"
->1.7. Miscellaneous</A
-></H1
-><P
->This chapter was lovingly handcrafted on a Dell Latitude C400 laptop running Slackware Linux 9.0,
-in case anyone asks.</P
-><P
->This chapter is Copyright 2003 David Lechnyr (david at lechnyr dot com).
-Permission is granted to copy, distribute and/or modify this document under the terms
-of the GNU Free Documentation License, Version 1.2 or any later version published by the Free
-Software Foundation. A copy of the license is available at http://www.gnu.org/licenses/fdl.txt.</P
-></DIV
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="introduction.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="samba-howto-collection.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="install.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->General installation</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="introduction.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->How to Install and Test SAMBA</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
-> \ No newline at end of file
diff --git a/docs/htmldocs/lmhosts.5.html b/docs/htmldocs/lmhosts.5.html
index 9995b6937a..4d7f11e64b 100644
--- a/docs/htmldocs/lmhosts.5.html
+++ b/docs/htmldocs/lmhosts.5.html
@@ -1,37 +1,210 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>lmhosts</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="lmhosts.5"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>lmhosts &#8212; The Samba NetBIOS hosts file</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><p><tt>lmhosts</tt> is the <a href="Samba.7.html">Samba(7)</a> NetBIOS name to IP address mapping file.</p></div><div class="refsect1" lang="en"><h2>DESCRIPTION</h2><p>This file is part of the <a href="Samba.7.html">Samba(7)</a> suite.</p><p><tt>lmhosts</tt> is the <span class="emphasis"><em>Samba
- </em></span> NetBIOS name to IP address mapping file. It
- is very similar to the <tt>/etc/hosts</tt> file
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<HTML
+><HEAD
+><TITLE
+>lmhosts</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.77"></HEAD
+><BODY
+CLASS="REFENTRY"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><H1
+><A
+NAME="LMHOSTS"
+></A
+>lmhosts</H1
+><DIV
+CLASS="REFNAMEDIV"
+><A
+NAME="AEN5"
+></A
+><H2
+>Name</H2
+>lmhosts&nbsp;--&nbsp;The Samba NetBIOS hosts file</DIV
+><DIV
+CLASS="REFSYNOPSISDIV"
+><A
+NAME="AEN8"
+></A
+><H2
+>Synopsis</H2
+><P
+><TT
+CLASS="FILENAME"
+>lmhosts</TT
+> is the <A
+HREF="samba.7.html"
+TARGET="_top"
+> Samba</A
+> NetBIOS name to IP address mapping file.</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN12"
+></A
+><H2
+>DESCRIPTION</H2
+><P
+>This file is part of the <A
+HREF="samba.7.html"
+TARGET="_top"
+> Samba</A
+> suite.</P
+><P
+><TT
+CLASS="FILENAME"
+>lmhosts</TT
+> is the <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Samba
+ </I
+></SPAN
+> NetBIOS name to IP address mapping file. It
+ is very similar to the <TT
+CLASS="FILENAME"
+>/etc/hosts</TT
+> file
format, except that the hostname component must correspond
- to the NetBIOS naming format.</p></div><div class="refsect1" lang="en"><h2>FILE FORMAT</h2><p>It is an ASCII file containing one line for NetBIOS name.
+ to the NetBIOS naming format.</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN20"
+></A
+><H2
+>FILE FORMAT</H2
+><P
+>It is an ASCII file containing one line for NetBIOS name.
The two fields on each line are separated from each other by
white space. Any entry beginning with '#' is ignored. Each line
- in the lmhosts file contains the following information:</p><div class="itemizedlist"><ul type="disc"><li><p>IP Address - in dotted decimal format.</p></li><li><p>NetBIOS Name - This name format is a
+ in the lmhosts file contains the following information :</P
+><P
+></P
+><UL
+><LI
+><P
+>IP Address - in dotted decimal format.</P
+></LI
+><LI
+><P
+>NetBIOS Name - This name format is a
maximum fifteen character host name, with an optional
trailing '#' character followed by the NetBIOS name type
- as two hexadecimal digits.</p><p>If the trailing '#' is omitted then the given IP
+ as two hexadecimal digits.</P
+><P
+>If the trailing '#' is omitted then the given IP
address will be returned for all names that match the given
- name, whatever the NetBIOS name type in the lookup.</p></li></ul></div><p>An example follows:</p><pre class="programlisting">
-#
+ name, whatever the NetBIOS name type in the lookup.</P
+></LI
+></UL
+><P
+>An example follows :</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>#
# Sample Samba lmhosts file.
#
192.9.200.1 TESTPC
192.9.200.20 NTSERVER#20
192.9.200.21 SAMBASERVER
- </pre><p>Contains three IP to NetBIOS name mappings. The first
- and third will be returned for any queries for the names &quot;TESTPC&quot;
- and &quot;SAMBASERVER&quot; respectively, whatever the type component of
- the NetBIOS name requested.</p><p>The second mapping will be returned only when the &quot;0x20&quot; name
- type for a name &quot;NTSERVER&quot; is queried. Any other name type will not
- be resolved.</p><p>The default location of the <tt>lmhosts</tt> file
- is in the same directory as the <a href="smb.conf.5.html">smb.conf(5)</a> file.</p></div><div class="refsect1" lang="en"><h2>VERSION</h2><p>This man page is correct for version 3.0 of the Samba suite.</p></div><div class="refsect1" lang="en"><h2>SEE ALSO</h2><p><a href="smbclient.1.html">smbclient(1)</a>, <a href="smb.conf.5.html">smb.conf(5)</a>, and <a href="smbpasswd.8.html">smbpasswd(8)</a>
- </p></div><div class="refsect1" lang="en"><h2>AUTHOR</h2><p>The original Samba software and related utilities
+ </PRE
+></P
+><P
+>Contains three IP to NetBIOS name mappings. The first
+ and third will be returned for any queries for the names "TESTPC"
+ and "SAMBASERVER" respectively, whatever the type component of
+ the NetBIOS name requested.</P
+><P
+>The second mapping will be returned only when the "0x20" name
+ type for a name "NTSERVER" is queried. Any other name type will not
+ be resolved.</P
+><P
+>The default location of the <TT
+CLASS="FILENAME"
+>lmhosts</TT
+> file
+ is in the same directory as the <A
+HREF="smb.conf.5.html"
+TARGET="_top"
+>
+ smb.conf(5)&#62;</A
+> file.</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN37"
+></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="AEN40"
+></A
+><H2
+>SEE ALSO</H2
+><P
+><A
+HREF="smbclient.1.html"
+TARGET="_top"
+><B
+CLASS="COMMAND"
+>smbclient(1)
+ </B
+></A
+>, <A
+HREF="smb.conf.5.html#NAMERESOLVEORDER"
+TARGET="_top"
+> smb.conf(5)</A
+>, and <A
+HREF="smbpasswd.8.html"
+TARGET="_top"
+><B
+CLASS="COMMAND"
+> smbpasswd(8)</B
+></A
+>
+ </P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN48"
+></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.
+ to the way the Linux kernel is developed.</P
+><P
+>The original Samba man pages were written by Karl Auer.
The man page sources were converted to YODL format (another
excellent piece of Open Source software, available at
- <a href="ftp://ftp.icce.rug.nl/pub/unix/" target="_top">
- ftp://ftp.icce.rug.nl/pub/unix/</a>) and updated for the Samba 2.0
+ <A
+HREF="ftp://ftp.icce.rug.nl/pub/unix/"
+TARGET="_top"
+> ftp://ftp.icce.rug.nl/pub/unix/</A
+>) and updated for the Samba 2.0
release by Jeremy Allison. The conversion to DocBook for
- Samba 2.2 was done by Gerald Carter. The conversion to DocBook
- XML 4.2 was done by Alexander Bokovoy.</p></div></div></body></html>
+ Samba 2.2 was done by Gerald Carter</P
+></DIV
+></BODY
+></HTML
+> \ No newline at end of file
diff --git a/docs/htmldocs/msdfs.html b/docs/htmldocs/msdfs.html
index cb7592214e..f6fe1c7e1d 100644
--- a/docs/htmldocs/msdfs.html
+++ b/docs/htmldocs/msdfs.html
@@ -1,29 +1,151 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter22.Hosting a Microsoft Distributed File System tree on Samba</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"><link rel="home" href="index.html" title="SAMBA Project Documentation"><link rel="up" href="optional.html" title="PartIII.Advanced Configuration"><link rel="previous" href="VFS.html" title="Chapter21.Stackable VFS modules"><link rel="next" href="integrate-ms-networks.html" title="Chapter23.Integrating MS Windows networks with Samba"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter22.Hosting a Microsoft Distributed File System tree on Samba</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="VFS.html">Prev</a></td><th width="60%" align="center">PartIII.Advanced Configuration</th><td width="20%" align="right"><a accesskey="n" href="integrate-ms-networks.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="msdfs"></a>Chapter22.Hosting a Microsoft Distributed File System tree on Samba</h2></div><div><div class="author"><h3 class="author">Shirish Kalele</h3><div class="affiliation"><span class="orgname">Samba Team &amp; Veritas Software<br></span><div class="address"><p><br>
- <tt>&lt;<a href="mailto:samba@samba.org">samba@samba.org</a>&gt;</tt><br>
- </p></div></div></div></div><div><p class="pubdate">12 Jul 2000</p></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="msdfs.html#id2899111">Instructions</a></dt><dd><dl><dt><a href="msdfs.html#id2899858">Notes</a></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2899111"></a>Instructions</h2></div></div><p>The Distributed File System (or Dfs) provides a means of
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<HTML
+><HEAD
+><TITLE
+>Hosting a Microsoft Distributed File System tree on Samba</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
+REL="HOME"
+TITLE="SAMBA Project Documentation"
+HREF="samba-howto-collection.html"><LINK
+REL="UP"
+TITLE="Optional configuration"
+HREF="optional.html"><LINK
+REL="PREVIOUS"
+TITLE="Configuring PAM for distributed but centrally
+managed authentication"
+HREF="pam.html"><LINK
+REL="NEXT"
+TITLE="Printing Support"
+HREF="printing.html"></HEAD
+><BODY
+CLASS="CHAPTER"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><TABLE
+SUMMARY="Header navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>SAMBA Project Documentation</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="pam.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+></TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="printing.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="CHAPTER"
+><H1
+><A
+NAME="MSDFS">Chapter 13. Hosting a Microsoft Distributed File System tree on Samba</H1
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN1859">13.1. Instructions</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>To enable SMB-based DFS for Samba, configure it with the
- <i><tt>--with-msdfs</tt></i> option. Once built, a
+ load balancing etc. For more information about Dfs, refer to <A
+HREF="http://www.microsoft.com/NTServer/nts/downloads/winfeatures/NTSDistrFile/AdminGuide.asp"
+TARGET="_top"
+> Microsoft documentation</A
+>. </P
+><P
+>This document explains how to host a Dfs tree on a Unix
+ machine (for Dfs-aware clients to browse) using Samba.</P
+><P
+>To enable SMB-based DFS for Samba, configure it with the
+ <TT
+CLASS="PARAMETER"
+><I
+>--with-msdfs</I
+></TT
+> option. Once built, a
Samba server can be made a Dfs server by setting the global
- boolean <a href="smb.conf.5.html#HOSTMSDFS" target="_top"><i><tt>
- host msdfs</tt></i></a> parameter in the <tt>smb.conf
- </tt> file. You designate a share as a Dfs root using the share
- level boolean <a href="smb.conf.5.html#MSDFSROOT" target="_top"><i><tt>
- msdfs root</tt></i></a> parameter. A Dfs root directory on
+ 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>junction-&gt;msdfs:storage1\share1</tt> in
+ <TT
+CLASS="FILENAME"
+>junction-&gt;msdfs:storage1\share1</TT
+> in
the share directory acts as the Dfs junction. When Dfs-aware
clients attempt to access the junction link, they are redirected
- to the storage location (in this case, \\storage1\share1).</p><p>Dfs trees on Samba work with all Dfs-aware clients ranging
- from Windows 95 to 2000.</p><p>Here's an example of setting up a Dfs tree on a Samba
- server.</p><pre class="programlisting">
-# The smb.conf file:
+ to the storage location (in this case, \\storage1\share1).</P
+><P
+>Dfs trees on Samba work with all Dfs-aware clients ranging
+ from Windows 95 to 2000.</P
+><P
+>Here's an example of setting up a Dfs tree on a Samba
+ server.</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+># The smb.conf file:
[global]
netbios name = SAMBA
host msdfs = yes
@@ -31,21 +153,169 @@
[dfs]
path = /export/dfsroot
msdfs root = yes
- </pre><p>In the /export/dfsroot directory we set up our dfs links to
- other servers on the network.</p><p><tt>root# </tt><b><tt>cd /export/dfsroot</tt></b></p><p><tt>root# </tt><b><tt>chown root /export/dfsroot</tt></b></p><p><tt>root# </tt><b><tt>chmod 755 /export/dfsroot</tt></b></p><p><tt>root# </tt><b><tt>ln -s msdfs:storageA\\shareA linka</tt></b></p><p><tt>root# </tt><b><tt>ln -s msdfs:serverB\\share,serverC\\share linkb</tt></b></p><p>You should set up the permissions and ownership of
+ </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
+ 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" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2899858"></a>Notes</h3></div></div><div class="itemizedlist"><ul type="disc"><li><p>Windows clients need to be rebooted
+ takes users directly to the appropriate shares on the network.</P
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN1894">13.1.1. Notes</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
+ new share and make it the dfs root.</P
+></LI
+><LI
+><P
+>Currently there's a restriction that msdfs
+ symlink names should all be lowercase.</P
+></LI
+><LI
+><P
+>For security purposes, the directory
acting as the root of the Dfs tree should have ownership
and permissions set so that only designated users can
- modify the symbolic links in the directory.</p></li></ul></div></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="VFS.html">Prev</a></td><td width="20%" align="center"><a accesskey="u" href="optional.html">Up</a></td><td width="40%" align="right"><a accesskey="n" href="integrate-ms-networks.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter21.Stackable VFS modules</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">Chapter23.Integrating MS Windows networks with Samba</td></tr></table></div></body></html>
+ modify the symbolic links in the directory.</P
+></LI
+></UL
+></DIV
+></DIV
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+SUMMARY="Footer navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="pam.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="samba-howto-collection.html"
+ACCESSKEY="H"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="printing.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>Configuring PAM for distributed but centrally
+managed authentication</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="optional.html"
+ACCESSKEY="U"
+>Up</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>Printing Support</TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+> \ No newline at end of file
diff --git a/docs/htmldocs/net.8.html b/docs/htmldocs/net.8.html
index be30dbed05..b7ed1357c3 100644
--- a/docs/htmldocs/net.8.html
+++ b/docs/htmldocs/net.8.html
@@ -1,146 +1,403 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>net</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="net.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>net &#8212; Tool for administration of Samba and remote
- CIFS servers.
- </p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><tt>net</tt> {&lt;ads|rap|rpc&gt;} [-h] [-w workgroup] [-W myworkgroup] [-U user] [-I ip-address] [-p port] [-n myname] [-s conffile] [-S server] [-l] [-P] [-D debuglevel]</p></div></div><div class="refsect1" lang="en"><h2>DESCRIPTION</h2><p>This tool is part of the <a href="Samba.7.html">Samba(7)</a> suite.</p><p>The samba net utility is meant to work just like the net utility
- available for windows and DOS. The first argument should be used
- to specify the protocol to use when executing a certain command.
- ADS is used for ActiveDirectory, RAP is using for old (Win9x/NT3)
- clients and RPC can be used for NT4 and Windows 2000. If this
- argument is omitted, net will try to determine it automatically.
- Not all commands are available on all protocols.
- </p></div><div class="refsect1" lang="en"><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-h|--help</span></dt><dd><p>Print a summary of command line options.
-</p></dd><dt><span class="term">-w target-workgroup</span></dt><dd><p>
- Sets target workgroup or domain. You have to specify
- either this option or the IP address or the name of a server.
- </p></dd><dt><span class="term">-W workgroup</span></dt><dd><p>
- Sets client workgroup or domain
- </p></dd><dt><span class="term">-U user</span></dt><dd><p>
- User name to use
- </p></dd><dt><span class="term">-I ip-address</span></dt><dd><p>
- IP address of target server to use. You have to
- specify either this option or a target workgroup or
- a target server.
- </p></dd><dt><span class="term">-p port</span></dt><dd><p>
- Port on the target server to connect to (usually 139 or 445).
- Defaults to trying 445 first, then 139.
- </p></dd><dt><span class="term">-n &lt;primary NetBIOS name&gt;</span></dt><dd><p>This option allows you to override
-the NetBIOS name that Samba uses for itself. This is identical
-to setting the <a href="smb.conf.5.html#netbiosname" target="_top"><i><tt>NetBIOS
-name</tt></i></a> parameter in the <a href="smb.conf.5.html">smb.conf(5)</a> file. However, a command
-line setting will take precedence over settings in
-<a href="smb.conf.5.html">smb.conf(5)</a>.</p></dd><dt><span class="term">-s &lt;configuration file&gt;</span></dt><dd><p>The file specified contains the
-configuration details required by the server. The
-information in this file includes server-specific
-information such as what printcap file to use, as well
-as descriptions of all the services that the server is
-to provide. See <a href="smb.conf.5.html" target="_top"><tt>
-smb.conf(5)</tt></a> for more information.
-The default configuration file name is determined at
-compile time.</p></dd><dt><span class="term">-S server</span></dt><dd><p>
- Name of target server. You should specify either
- this option or a target workgroup or a target IP address.
- </p></dd><dt><span class="term">-l</span></dt><dd><p>
- When listing data, give more information on each item.
- </p></dd><dt><span class="term">-P</span></dt><dd><p>
- Make queries to the external server using the machine account of the local server.
- </p></dd><dt><span class="term">-d|--debug=debuglevel</span></dt><dd><p><i><tt>debuglevel</tt></i> is an integer
-from 0 to 10. The default value if this parameter is
-not specified is zero.</p><p>The higher this value, the more detail will be
-logged to the log files about the activities of the
-server. At level 0, only critical errors and serious
-warnings will be logged. Level 1 is a reasonable level for
-day to day running - it generates a small amount of
-information about operations carried out.</p><p>Levels above 1 will generate considerable
-amounts of log data, and should only be used when
-investigating a problem. Levels above 3 are designed for
-use only by developers and generate HUGE amounts of log
-data, most of which is extremely cryptic.</p><p>Note that specifying this parameter here will
-override the <a href="smb.conf.5.html#loglevel" target="_top">log
-level</a> parameter in the <a href="smb.conf.5.html" target="_top">
-<tt>smb.conf(5)</tt></a> file.</p></dd></dl></div></div><div class="refsect1" lang="en"><h2>COMMANDS</h2><div class="refsect2" lang="en"><h3>TIME</h3><p>The <b>NET TIME</b> command allows you to view the time on a remote server
- or synchronise the time on the local server with the time on the remote server.</p><div class="refsect3" lang="en"><h4>TIME</h4><p>Without any options, the <b>NET TIME</b> command
-displays the time on the remote server.
-</p></div><div class="refsect3" lang="en"><h4>TIME SYSTEM</h4><p> Displays the time on the remote server in a format ready for <b>/bin/date</b></p></div><div class="refsect3" lang="en"><h4>TIME SET</h4><p>Tries to set the date and time of the local server to that on
-the remote server using <b>/bin/date</b>. </p></div><div class="refsect3" lang="en"><h4>TIME ZONE</h4><p>Displays the timezone in hours from GMT on the remote computer.</p></div></div><div class="refsect2" lang="en"><h3>[RPC|ADS] JOIN [TYPE] [-U username[%password]] [options]</h3><p>
-Join a domain. If the account already exists on the server, and
-[TYPE] is MEMBER, the machine will attempt to join automatically.
-(Assuming that the machine has been created in server manager)
-Otherwise, a password will be prompted for, and a new account may
-be created.</p><p>
-[TYPE] may be PDC, BDC or MEMBER to specify the type of server
-joining the domain.
-</p></div><div class="refsect2" lang="en"><h3>[RPC] OLDJOIN [options]</h3><p>Join a domain. Use the OLDJOIN option to join the domain
-using the old style of domain joining - you need to create a trust
-account in server manager first.</p></div><div class="refsect2" lang="en"><h3>[RPC|ADS] USER</h3><div class="refsect3" lang="en"><h4>[RPC|ADS] USER DELETE <i><tt>target</tt></i></h4><p>Delete specified user</p></div><div class="refsect3" lang="en"><h4>[RPC|ADS] USER LIST</h4><p>List all users</p></div><div class="refsect3" lang="en"><h4>[RPC|ADS] USER INFO <i><tt>target</tt></i></h4><p>List the domain groups of a the specified user.</p></div><div class="refsect3" lang="en"><h4>[RPC|ADS] USER ADD <i><tt>name</tt></i> [password] [-F user flags] [-C comment]</h4><p>Add specified user.</p></div></div><div class="refsect2" lang="en"><h3>[RPC|ADS] GROUP</h3><div class="refsect3" lang="en"><h4>[RPC|ADS] GROUP [misc options] [targets]</h4><p>List user groups.</p></div><div class="refsect3" lang="en"><h4>[RPC|ADS] GROUP DELETE <i><tt>name</tt></i> [misc. options]</h4><p>Delete specified group.</p></div><div class="refsect3" lang="en"><h4>[RPC|ADS] GROUP ADD <i><tt>name</tt></i> [-C comment]</h4><p>Create specified group.</p></div></div><div class="refsect2" lang="en"><h3>[RAP|RPC] SHARE</h3><div class="refsect3" lang="en"><h4>[RAP|RPC] SHARE [misc. options] [targets]</h4><p>Enumerates all exported resources (network shares) on target server.</p></div><div class="refsect3" lang="en"><h4>[RAP|RPC] SHARE ADD <i><tt>name=serverpath</tt></i> [-C comment] [-M maxusers] [targets]</h4><p>Adds a share from a server (makes the export active). Maxusers
-specifies the number of users that can be connected to the
-share simultaneously.</p></div><div class="refsect3" lang="en"><h4>SHARE DELETE <i><tt>sharenam</tt></i></h4><p>Delete specified share.</p></div></div><div class="refsect2" lang="en"><h3>[RPC|RAP] FILE</h3><div class="refsect3" lang="en"><h4>[RPC|RAP] FILE</h4><p>List all open files on remote server.</p></div><div class="refsect3" lang="en"><h4>[RPC|RAP] FILE CLOSE <i><tt>fileid</tt></i></h4><p>Close file with specified <i><tt>fileid</tt></i> on
-remote server.</p></div><div class="refsect3" lang="en"><h4>[RPC|RAP] FILE INFO <i><tt>fileid</tt></i></h4><p>
-Print information on specified <i><tt>fileid</tt></i>.
-Currently listed are: file-id, username, locks, path, permissions.
-</p></div><div class="refsect3" lang="en"><h4>[RAP|RPC] FILE USER</h4><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>Currently NOT implemented.</p></div></div></div><div class="refsect2" lang="en"><h3>SESSION</h3><div class="refsect3" lang="en"><h4>RAP SESSION</h4><p>Without any other options, SESSION enumerates all active SMB/CIFS
-sessions on the target server.</p></div><div class="refsect3" lang="en"><h4>RAP SESSION DELETE|CLOSE <i><tt>CLIENT_NAME</tt></i></h4><p>Close the specified sessions.</p></div><div class="refsect3" lang="en"><h4>RAP SESSION INFO <i><tt>CLIENT_NAME</tt></i></h4><p>Give a list with all the open files in specified session.</p></div></div><div class="refsect2" lang="en"><h3>RAP SERVER <i><tt>DOMAIN</tt></i></h3><p>List all servers in specified domain or workgroup. Defaults
-to local domain.</p></div><div class="refsect2" lang="en"><h3>RAP DOMAIN</h3><p>Lists all domains and workgroups visible on the
-current network.</p></div><div class="refsect2" lang="en"><h3>RAP PRINTQ</h3><div class="refsect3" lang="en"><h4>RAP PRINTQ LIST <i><tt>QUEUE_NAME</tt></i></h4><p>Lists the specified print queue and print jobs on the server.
-If the <i><tt>QUEUE_NAME</tt></i> is omitted, all
-queues are listed.</p></div><div class="refsect3" lang="en"><h4>RAP PRINTQ DELETE <i><tt>JOBID</tt></i></h4><p>Delete job with specified id.</p></div></div><div class="refsect2" lang="en"><h3>RAP VALIDATE <i><tt>user</tt></i> [<i><tt>password</tt></i>]</h3><p>
-Validate whether the specified user can log in to the
-remote server. If the password is not specified on the commandline, it
-will be prompted.
-</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>Currently NOT implemented.</p></div></div><div class="refsect2" lang="en"><h3>RAP GROUPMEMBER</h3><div class="refsect3" lang="en"><h4>RAP GROUPMEMBER LIST <i><tt>GROUP</tt></i></h4><p>List all members of the specified group.</p></div><div class="refsect3" lang="en"><h4>RAP GROUPMEMBER DELETE <i><tt>GROUP</tt></i> <i><tt>USER</tt></i></h4><p>Delete member from group.</p></div><div class="refsect3" lang="en"><h4>RAP GROUPMEMBER ADD <i><tt>GROUP</tt></i> <i><tt>USER</tt></i></h4><p>Add member to group.</p></div></div><div class="refsect2" lang="en"><h3>RAP ADMIN <i><tt>command</tt></i></h3><p>Execute the specified <i><tt>command</tt></i> on
-the remote server. Only works with OS/2 servers.
-</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>Currently NOT implemented.</p></div></div><div class="refsect2" lang="en"><h3>RAP SERVICE</h3><div class="refsect3" lang="en"><h4>RAP SERVICE START <i><tt>NAME</tt></i> [arguments...]</h4><p>Start the specified service on the remote server. Not implemented yet.</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>Currently NOT implemented.</p></div></div><div class="refsect3" lang="en"><h4>RAP SERVICE STOP</h4><p>Stop the specified service on the remote server.</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>Currently NOT implemented.</p></div></div></div><div class="refsect2" lang="en"><h3>RAP PASSWORD <i><tt>USER</tt></i> <i><tt>OLDPASS</tt></i> <i><tt>NEWPASS</tt></i></h3><p>
-Change password of <i><tt>USER</tt></i> from <i><tt>OLDPASS</tt></i> to <i><tt>NEWPASS</tt></i>.
-</p></div><div class="refsect2" lang="en"><h3>LOOKUP</h3><div class="refsect3" lang="en"><h4>LOOKUP HOST <i><tt>HOSTNAME</tt></i> [<i><tt>TYPE</tt></i>]</h4><p>
-Lookup the IP address of the given host with the specified type (netbios suffix).
-The type defaults to 0x20 (workstation).
-</p></div><div class="refsect3" lang="en"><h4>LOOKUP LDAP [<i><tt>DOMAIN</tt></i></h4><p>Give IP address of LDAP server of specified <i><tt>DOMAIN</tt></i>. Defaults to local domain.</p></div><div class="refsect3" lang="en"><h4>LOOKUP KDC [<i><tt>REALM</tt></i>]</h4><p>Give IP address of KDC for the specified <i><tt>REALM</tt></i>.
-Defaults to local realm.</p></div><div class="refsect3" lang="en"><h4>LOOKUP DC [<i><tt>DOMAIN</tt></i>]</h4><p>Give IP's of Domain Controllers for specified <i><tt>
-DOMAIN</tt></i>. Defaults to local domain.</p></div><div class="refsect3" lang="en"><h4>LOOKUP MASTER <i><tt>DOMAIN</tt></i></h4><p>Give IP of master browser for specified <i><tt>DOMAIN</tt></i>
-or workgroup. Defaults to local domain.</p></div></div><div class="refsect2" lang="en"><h3>CACHE</h3><p>Samba uses a general caching interface called 'gencache'. It
-can be controlled using 'NET CACHE'.</p><p>All the timeout parameters support the suffixes:
-
-</p><table class="simplelist" border="0" summary="Simple list"><tr><td>s - Seconds</td></tr><tr><td>m - Minutes</td></tr><tr><td>h - Hours</td></tr><tr><td>d - Days</td></tr><tr><td>w - Weeks</td></tr></table><p>
-
-</p><div class="refsect3" lang="en"><h4>CACHE ADD <i><tt>key</tt></i> <i><tt>data</tt></i> <i><tt>time-out</tt></i></h4><p>Add specified key+data to the cache with the given timeout.</p></div><div class="refsect3" lang="en"><h4>CACHE DEL <i><tt>key</tt></i></h4><p>Delete key from the cache.</p></div><div class="refsect3" lang="en"><h4>CACHE SET <i><tt>key</tt></i> <i><tt>data</tt></i> <i><tt>time-out</tt></i></h4><p>Update data of existing cache entry.</p></div><div class="refsect3" lang="en"><h4>CACHE SEARCH <i><tt>PATTERN</tt></i></h4><p>Search for the specified pattern in the cache data.</p></div><div class="refsect3" lang="en"><h4>CACHE LIST</h4><p>
-List all current items in the cache.
-</p></div><div class="refsect3" lang="en"><h4>CACHE FLUSH</h4><p>Remove all the current items from the cache.</p></div></div><div class="refsect2" lang="en"><h3>GETLOCALSID [DOMAIN]</h3><p>Print the SID of the specified domain, or if the parameter is
-omitted, the SID of the domain the local server is in.</p></div><div class="refsect2" lang="en"><h3>SETLOCALSID S-1-5-21-x-y-z</h3><p>Sets domain sid for the local server to the specified SID.</p></div><div class="refsect2" lang="en"><h3>GROUPMAP</h3><p>Manage the mappings between Windows group SIDs and UNIX groups.
-Parameters take the for &quot;parameter=value&quot;. Common options include:</p><div class="itemizedlist"><ul type="disc"><li><p>unixgroup - Name of the UNIX group</p></li><li><p>ntgroup - Name of the Windows NT group (must be
- resolvable to a SID</p></li><li><p>rid - Unsigned 32-bit integer</p></li><li><p>sid - Full SID in the form of &quot;S-1-...&quot;</p></li><li><p>type - Type of the group; either 'domain', 'local',
- or 'builtin'</p></li><li><p>comment - Freeform text description of the group</p></li></ul></div><div class="refsect3" lang="en"><h4>GROUPMAP ADD</h4><p>Add a new group mapping entry</p><p>net groupmap add {rid=int|sid=string} unixgroup=string [type={domain|local|builtin}] [ntgroup=string] [comment=string]</p></div><div class="refsect3" lang="en"><h4>GROUPMAP DELETE</h4><p>Delete a group mapping entry</p><p>net groupmap delete {ntgroup=string|sid=SID}</p></div><div class="refsect3" lang="en"><h4>GROUPMAP MODIFY</h4><p>Update en existing group entry</p><p>net groupmap modify {ntgroup=string|sid=SID} [unixgroup=string] [comment=string] [type={domain|local}</p></div><div class="refsect3" lang="en"><h4>GROUPMAP LIST</h4><p>List existing group mapping entries</p><p>net groupmap list [verbose] [ntgroup=string] [sid=SID]</p></div></div><div class="refsect2" lang="en"><h3>MAXRID</h3><p>Prints out the highest RID currently in use on the local
-server (by the active 'passdb backend').
-</p></div><div class="refsect2" lang="en"><h3>RPC INFO</h3><p>Print information about the domain of the remote server,
-such as domain name, domain sid and number of users and groups.
-</p></div><div class="refsect2" lang="en"><h3>[RPC|ADS] TESTJOIN</h3><p>Check whether participation in a domain is still valid.</p></div><div class="refsect2" lang="en"><h3>[RPC|ADS] CHANGETRUSTPW</h3><p>Force change of domain trust password.</p></div><div class="refsect2" lang="en"><h3>RPC TRUSTDOM</h3><div class="refsect3" lang="en"><h4>RPC TRUSTDOM ADD <i><tt>DOMAIN</tt></i></h4><p>Add a interdomain trust account for
-<i><tt>DOMAIN</tt></i> to the remote server.
-</p></div><div class="refsect3" lang="en"><h4>RPC TRUSTDOM DEL <i><tt>DOMAIM</tt></i></h4><p>Remove interdomain trust account for
-<i><tt>DOMAIN</tt></i> from the remote server.
-</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>Currently NOT implemented.</p></div></div><div class="refsect3" lang="en"><h4>RPC TRUSTDOM ESTABLISH <i><tt>DOMAIN</tt></i></h4><p>
-Establish a trust relationship to a trusting domain.
-Interdomain account must already be created on the remote PDC.
-</p></div><div class="refsect3" lang="en"><h4>RPC TRUSTDOM REVOKE <i><tt>DOMAIN</tt></i></h4><p>Abandon relationship to trusted domain</p></div><div class="refsect3" lang="en"><h4>RPC TRUSTDOM LIST</h4><p>List all current interdomain trust relationships.</p></div></div><div class="refsect2" lang="en"><h3>RPC ABORTSHUTDOWN</h3><p>Abort the shutdown of a remote server.</p></div><div class="refsect2" lang="en"><h3>SHUTDOWN [-t timeout] [-r] [-f] [-C message]</h3><p>Shut down the remote server.</p><div class="variablelist"><dl><dt><span class="term">-r</span></dt><dd><p>
-Reboot after shutdown.
-</p></dd><dt><span class="term">-f</span></dt><dd><p>
-Force shutting down all applications.
-</p></dd><dt><span class="term">-t timeout</span></dt><dd><p>
-Timeout before system will be shut down. An interactive
-user of the system can use this time to cancel the shutdown.
-</p></dd><dt><span class="term">-C message</span></dt><dd><p>Display the specified message on the screen to
-announce the shutdown.</p></dd></dl></div></div><div class="refsect2" lang="en"><h3>SAMDUMP</h3><p>Print out sam database of remote server. You need
-to run this on either a BDC. </p></div><div class="refsect2" lang="en"><h3>VAMPIRE</h3><p>Export users, aliases and groups from remote server to
-local server. Can only be run an a BDC.
-</p></div><div class="refsect2" lang="en"><h3>GETSID</h3><p>Fetch domain SID and store it in the local <tt>secrets.tdb</tt>. </p></div><div class="refsect2" lang="en"><h3>ADS LEAVE</h3><p>Make the remote host leave the domain it is part of. </p></div><div class="refsect2" lang="en"><h3>ADS STATUS</h3><p>Print out status of machine account of the local machine in ADS.
-Prints out quite some debug info. Aimed at developers, regular
-users should use <b>NET ADS TESTJOIN</b>.</p></div><div class="refsect2" lang="en"><h3>ADS PRINTER</h3><div class="refsect3" lang="en"><h4>ADS PRINTER INFO [<i><tt>PRINTER</tt></i>] [<i><tt>SERVER</tt></i>]</h4><p>
-Lookup info for <i><tt>PRINTER</tt></i> on <i><tt>SERVER</tt></i>. The printer name defaults to &quot;*&quot;, the
-server name defaults to the local host.</p></div><div class="refsect3" lang="en"><h4>ADS PRINTER PUBLISH <i><tt>PRINTER</tt></i></h4><p>Publish specified printer using ADS.</p></div><div class="refsect3" lang="en"><h4>ADS PRINTER REMOVE <i><tt>PRINTER</tt></i></h4><p>Remove specified printer from ADS directory.</p></div></div><div class="refsect2" lang="en"><h3>ADS SEARCH <i><tt>EXPRESSION</tt></i> <i><tt>ATTRIBUTES...</tt></i></h3><p>Perform a raw LDAP search on a ADS server and dump the results. The
-expression is a standard LDAP search expression, and the
-attributes are a list of LDAP fields to show in the results.</p><p>Example: <b><tt>net ads search '(objectCategory=group)' sAMAccountName</tt></b>
-</p></div><div class="refsect2" lang="en"><h3>ADS DN <i><tt>DN</tt></i> <i><tt>(attributes)</tt></i></h3><p>
-Perform a raw LDAP search on a ADS server and dump the results. The
-DN standard LDAP DN, and the attributes are a list of LDAP fields
-to show in the result.
-</p><p>Example: <b><tt>net ads dn 'CN=administrator,CN=Users,DC=my,DC=domain' SAMAccountName</tt></b></p></div><div class="refsect2" lang="en"><h3>WORKGROUP</h3><p>Print out workgroup name for specified kerberos realm.</p></div><div class="refsect2" lang="en"><h3>HELP [COMMAND]</h3><p>Gives usage information for the specified command.</p></div></div><div class="refsect1" lang="en"><h2>VERSION</h2><p>This man page is complete for version 3.0 of the Samba
- suite.</p></div><div class="refsect1" lang="en"><h2>AUTHOR</h2><p>The original Samba software and related utilities
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<HTML
+><HEAD
+><TITLE
+>net</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.77"></HEAD
+><BODY
+CLASS="REFENTRY"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><H1
+><A
+NAME="NET"
+></A
+>net</H1
+><DIV
+CLASS="REFNAMEDIV"
+><A
+NAME="AEN5"
+></A
+><H2
+>Name</H2
+>net&nbsp;--&nbsp;Tool for administration of Samba and remote
+ CIFS servers.</DIV
+><DIV
+CLASS="REFSYNOPSISDIV"
+><A
+NAME="AEN8"
+></A
+><H2
+>Synopsis</H2
+><P
+><B
+CLASS="COMMAND"
+>net</B
+> {&lt;ads|rap|rpc&gt;} [-h] [-w workgroup] [-W myworkgroup] [-U user] [-I ip-address] [-p port] [-n myname] [-s conffile] [-S server] [-C comment] [-M maxusers] [-F flags] [-j jobid] [-l] [-r] [-f] [-t timeout] [-P] [-D debuglevel]</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN31"
+></A
+><H2
+>DESCRIPTION</H2
+><P
+>This tool is part of the <A
+HREF="samba.7.html"
+TARGET="_top"
+> Samba</A
+> suite.</P
+><P
+>The samba net utility is meant to work just like the net utility
+ available for windows and DOS.</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN36"
+></A
+><H2
+>OPTIONS</H2
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>-h</DT
+><DD
+><P
+> Display summary of all available options.
+
+ </P
+></DD
+><DT
+>-w target-workgroup</DT
+><DD
+><P
+> Sets target workgroup or domain. You have to specify either this option or the IP address or the name of a server.
+ </P
+></DD
+><DT
+>-W workgroup</DT
+><DD
+><P
+> Sets client workgroup or domain
+ </P
+></DD
+><DT
+>-U user</DT
+><DD
+><P
+> User name to use
+ </P
+></DD
+><DT
+>-I ip-address</DT
+><DD
+><P
+> IP address of target server to use. You have to specify either this option or a target workgroup or a target server.
+ </P
+></DD
+><DT
+>-p port</DT
+><DD
+><P
+> Port on the target server to connect to.
+ </P
+></DD
+><DT
+>-n myname</DT
+><DD
+><P
+> Sets name of the client.
+ </P
+></DD
+><DT
+>-s conffile</DT
+><DD
+><P
+> Specify alternative configuration file that should be loaded.
+ </P
+></DD
+><DT
+>-S server</DT
+><DD
+><P
+> Name of target server. You should specify either this option or a target workgroup or a target IP address.
+ </P
+></DD
+><DT
+>-C comment</DT
+><DD
+><P
+> FIXME
+ </P
+></DD
+><DT
+>-M maxusers</DT
+><DD
+><P
+> FIXME
+ </P
+></DD
+><DT
+>-F flags</DT
+><DD
+><P
+> FIXME
+ </P
+></DD
+><DT
+>-j jobid</DT
+><DD
+><P
+> FIXME
+ </P
+></DD
+><DT
+>-l</DT
+><DD
+><P
+> FIXME
+ </P
+></DD
+><DT
+>-r</DT
+><DD
+><P
+> FIXME
+ </P
+></DD
+><DT
+>-f</DT
+><DD
+><P
+> FIXME
+ </P
+></DD
+><DT
+>-t timeout</DT
+><DD
+><P
+> FIXME
+ </P
+></DD
+><DT
+>-P</DT
+><DD
+><P
+> Make queries to the external server using the machine account of the local server.
+ </P
+></DD
+><DT
+>-D debuglevel</DT
+><DD
+><P
+>set the debuglevel. Debug level 0 is the lowest
+ and 100 being the highest. This should be set to 100 if you are
+ planning on submitting a bug report to the Samba team (see
+ <TT
+CLASS="FILENAME"
+>BUGS.txt</TT
+>).
+ </P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN116"
+></A
+><H2
+>TIME</H2
+><P
+>The <B
+CLASS="COMMAND"
+>NET TIME</B
+> command allows you to view the time on a remote server
+ or synchronise the time on the local server with the time on the remote server.</P
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+></DT
+><DD
+><P
+> Without any options, the <B
+CLASS="COMMAND"
+>NET TIME</B
+> command
+ displays the time on the remote server.
+ </P
+></DD
+><DT
+>SYSTEM</DT
+><DD
+><P
+> Displays the time on the remote server in a format ready for /bin/date
+ </P
+></DD
+><DT
+>SET</DT
+><DD
+><P
+> Tries to set the date and time of the local server to that on
+ the remote server using /bin/date.
+ </P
+></DD
+><DT
+>ZONE</DT
+><DD
+><P
+> Displays the timezone in hours from GMT on the remote computer.
+ </P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN138"
+></A
+><H2
+>RPC</H2
+><P
+>The <B
+CLASS="COMMAND"
+>NET RPC</B
+> command allows you to do various
+ NT4 operations.</P
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>JOIN -U username[%password] [options]</DT
+><DD
+><P
+> Join a domain with specified username and password. Password
+ will be prompted if none is specified.</P
+></DD
+><DT
+>JOIN [options except -U]</DT
+><DD
+><P
+> to join a domain created in server manager
+ </P
+></DD
+><DT
+>USER [misc. options] [targets]</DT
+><DD
+><P
+> List users
+ </P
+></DD
+><DT
+>USER DELETE &lt;name&gt; [misc options]</DT
+><DD
+><P
+> delete specified user
+ </P
+></DD
+><DT
+>USER INFO &lt;name&gt; [misc options]</DT
+><DD
+><P
+> list the domain groups of the specified user
+ </P
+></DD
+><DT
+>USER ADD &lt;name&gt; [password] [-F user flags] [misc. options</DT
+><DD
+><P
+> Add specified user
+ </P
+></DD
+><DT
+>GROUP [misc options] [targets]</DT
+><DD
+><P
+> List user groups
+ </P
+></DD
+><DT
+>GROUP DELETE &lt;name&gt; [misc. options] [targets]</DT
+><DD
+><P
+> Delete specified group
+ </P
+></DD
+><DT
+>GROUP ADD &lt;name&gt; [-C comment]</DT
+><DD
+><P
+> Create specified group
+ </P
+></DD
+><DT
+>SHARE [misc. options] [targets]</DT
+><DD
+><P
+> enumerates all exported resources (network shares) on target server
+ </P
+></DD
+><DT
+>SHARE ADD &lt;name=serverpath&gt; [misc. options] [targets]</DT
+><DD
+><P
+> Adds a share from a server (makes the export active)
+ </P
+></DD
+><DT
+>SHARE DELETE &lt;sharenam</DT
+><DD
+><P
+></P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN191"
+></A
+><H2
+>VERSION</H2
+><P
+>This man page is incomplete for version 3.0 of the Samba
+ suite.</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN194"
+></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 net manpage was written by Jelmer Vernooij.</p></div></div></body></html>
+ to the way the Linux kernel is developed.</P
+><P
+>The original Samba man pages were written by Karl Auer.
+ The current set of manpages and documentation is maintained
+ by the Samba Team in the same fashion as the Samba source code.</P
+></DIV
+></BODY
+></HTML
+> \ No newline at end of file
diff --git a/docs/htmldocs/nmbd.8.html b/docs/htmldocs/nmbd.8.html
index b07267fa45..1183a14522 100644
--- a/docs/htmldocs/nmbd.8.html
+++ b/docs/htmldocs/nmbd.8.html
@@ -1,153 +1,754 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>nmbd</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="nmbd.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>nmbd &#8212; NetBIOS name server to provide NetBIOS
- over IP naming services to clients</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><tt>nmbd</tt> [-D] [-F] [-S] [-a] [-i] [-o] [-h] [-V] [-d &lt;debug level&gt;] [-H &lt;lmhosts file&gt;] [-l &lt;log directory&gt;] [-n &lt;primary netbios name&gt;] [-p &lt;port number&gt;] [-s &lt;configuration file&gt;]</p></div></div><div class="refsect1" lang="en"><h2>DESCRIPTION</h2><p>This program is part of the <a href="Samba.7.html">Samba(7)</a> suite.</p><p><b>nmbd</b> is a server that understands
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
+<HTML
+><HEAD
+><TITLE
+>nmbd</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"></HEAD
+><BODY
+CLASS="REFENTRY"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><H1
+><A
+NAME="NMBD">nmbd</H1
+><DIV
+CLASS="REFNAMEDIV"
+><A
+NAME="AEN5"
+></A
+><H2
+>Name</H2
+>nmbd&nbsp;--&nbsp;NetBIOS name server to provide NetBIOS
+ over IP naming services to clients</DIV
+><DIV
+CLASS="REFSYNOPSISDIV"
+><A
+NAME="AEN8"><H2
+>Synopsis</H2
+><P
+><B
+CLASS="COMMAND"
+>nmbd</B
+> [-D] [-F] [-S] [-a] [-i] [-o] [-h] [-V] [-d &#60;debug level&#62;] [-H &#60;lmhosts file&#62;] [-l &#60;log directory&#62;] [-n &#60;primary netbios name&#62;] [-p &#60;port number&#62;] [-s &#60;configuration file&#62;]</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN25"
+></A
+><H2
+>DESCRIPTION</H2
+><P
+>This program is part of the Samba suite.</P
+><P
+><B
+CLASS="COMMAND"
+>nmbd</B
+> is a server that understands
and can reply to NetBIOS over IP name service requests, like
those produced by SMB/CIFS clients such as Windows 95/98/ME,
Windows NT, Windows 2000, Windows XP and LanManager clients. It also
participates in the browsing protocols which make up the
- Windows &quot;Network Neighborhood&quot; view.</p><p>SMB/CIFS clients, when they start up, may wish to
+ Windows "Network Neighborhood" view.</P
+><P
+>SMB/CIFS clients, when they start up, may wish to
locate an SMB/CIFS server. That is, they wish to know what
- IP number a specified host is using.</p><p>Amongst other services, <b>nmbd</b> will
+ IP number a specified host is using.</P
+><P
+>Amongst other services, <B
+CLASS="COMMAND"
+>nmbd</B
+> will
listen for such requests, and if its own NetBIOS name is
specified it will respond with the IP number of the host it
- is running on. Its &quot;own NetBIOS name&quot; is by
+ is running on. Its "own NetBIOS name" is by
default the primary DNS name of the host it is running on,
- but this can be overridden with the <span class="emphasis"><em>-n</em></span>
- option (see OPTIONS below). Thus <b>nmbd</b> will
+ but this can be overridden with the <I
+CLASS="EMPHASIS"
+>-n</I
+>
+ option (see OPTIONS below). Thus <B
+CLASS="COMMAND"
+>nmbd</B
+> will
reply to broadcast queries for its own name(s). Additional
- names for <b>nmbd</b> to respond on can be set
- via parameters in the <a href="smb.conf.5.html">smb.conf(5)</a> configuration file.</p><p><b>nmbd</b> can also be used as a WINS
+ names for <B
+CLASS="COMMAND"
+>nmbd</B
+> to respond on can be set
+ via parameters in the <A
+HREF="smb.conf.5.html"
+TARGET="_top"
+><TT
+CLASS="FILENAME"
+> smb.conf(5)</TT
+></A
+> configuration file.</P
+><P
+><B
+CLASS="COMMAND"
+>nmbd</B
+> can also be used as a WINS
(Windows Internet Name Server) server. What this basically means
is that it will act as a WINS database server, creating a
database from name registration requests that it receives and
- replying to queries from clients for these names.</p><p>In addition, <b>nmbd</b> can act as a WINS
+ replying to queries from clients for these names.</P
+><P
+>In addition, <B
+CLASS="COMMAND"
+>nmbd</B
+> can act as a WINS
proxy, relaying broadcast queries from clients that do
not understand how to talk the WINS protocol to a WINS
- server.</p></div><div class="refsect1" lang="en"><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-D</span></dt><dd><p>If specified, this parameter causes
- <b>nmbd</b> to operate as a daemon. That is,
+ server.</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN42"
+></A
+><H2
+>OPTIONS</H2
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>-D</DT
+><DD
+><P
+>If specified, this parameter causes
+ <B
+CLASS="COMMAND"
+>nmbd</B
+> to operate as a daemon. That is,
it detaches itself and runs in the background, fielding
- requests on the appropriate port. By default, <b>nmbd</b>
+ requests on the appropriate port. By default, <B
+CLASS="COMMAND"
+>nmbd</B
+>
will operate as a daemon if launched from a command shell.
- nmbd can also be operated from the <b>inetd</b>
+ nmbd can also be operated from the <B
+CLASS="COMMAND"
+>inetd</B
+>
meta-daemon, although this is not recommended.
- </p></dd><dt><span class="term">-F</span></dt><dd><p>If specified, this parameter causes
- the main <b>nmbd</b> process to not daemonize,
+ </P
+></DD
+><DT
+>-F</DT
+><DD
+><P
+>If specified, this parameter causes
+ the main <B
+CLASS="COMMAND"
+>nmbd</B
+> process to not daemonize,
i.e. double-fork and disassociate with the terminal.
Child processes are still created as normal to service
each connection request, but the main process does not
exit. This operation mode is suitable for running
- <b>nmbd</b> under process supervisors such
- as <b>supervise</b> and <b>svscan</b>
- from Daniel J. Bernstein's <b>daemontools</b>
+ <B
+CLASS="COMMAND"
+>nmbd</B
+> under process supervisors such
+ as <B
+CLASS="COMMAND"
+>supervise</B
+> and <B
+CLASS="COMMAND"
+>svscan</B
+>
+ from Daniel J. Bernstein's <B
+CLASS="COMMAND"
+>daemontools</B
+>
package, or the AIX process monitor.
- </p></dd><dt><span class="term">-S</span></dt><dd><p>If specified, this parameter causes
- <b>nmbd</b> to log to standard output rather
- than a file.</p></dd><dt><span class="term">-i</span></dt><dd><p>If this parameter is specified it causes the
- server to run &quot;interactively&quot;, not as a daemon, even if the
+ </P
+></DD
+><DT
+>-S</DT
+><DD
+><P
+>If specified, this parameter causes
+ <B
+CLASS="COMMAND"
+>nmbd</B
+> to log to standard output rather
+ than a file.</P
+></DD
+><DT
+>-a</DT
+><DD
+><P
+>If this parameter is specified, each new
+ connection will append log messages to the log file.
+ This is the default.</P
+></DD
+><DT
+>-i</DT
+><DD
+><P
+>If this parameter is specified it causes the
+ server to run "interactively", not as a daemon, even if the
server is executed on the command line of a shell. Setting this
parameter negates the implicit daemon mode when run from the
- command line. <b>nmbd</b> also logs to standard
- output, as if the <tt>-S</tt> parameter had been
- given. </p></dd><dt><span class="term">-h|--help</span></dt><dd><p>Print a summary of command line options.
-</p></dd><dt><span class="term">-H &lt;filename&gt;</span></dt><dd><p>NetBIOS lmhosts file. The lmhosts
+ command line. <B
+CLASS="COMMAND"
+>nmbd</B
+> also logs to standard
+ output, as if the <B
+CLASS="COMMAND"
+>-S</B
+> parameter had been
+ given. </P
+></DD
+><DT
+>-o</DT
+><DD
+><P
+>If this parameter is specified, the
+ log files will be overwritten when opened. By default,
+ <B
+CLASS="COMMAND"
+>smbd</B
+> will append entries to the log
+ files.</P
+></DD
+><DT
+>-h</DT
+><DD
+><P
+>Prints the help information (usage)
+ for <B
+CLASS="COMMAND"
+>nmbd</B
+>.</P
+></DD
+><DT
+>-H &#60;filename&#62;</DT
+><DD
+><P
+>NetBIOS lmhosts file. The lmhosts
file is a list of NetBIOS names to IP addresses that
is loaded by the nmbd server and used via the name
- resolution mechanism <a href="smb.conf.5.html#nameresolveorder" target="_top"><i><tt>name resolve
- order</tt></i></a> described in <a href="smb.conf.5.html">smb.conf(5)</a> to resolve any
- NetBIOS name queries needed by the server. Note
- that the contents of this file are <span class="emphasis"><em>NOT</em></span>
- used by <b>nmbd</b> to answer any name queries.
+ resolution mechanism <A
+HREF="smb.conf.5.html#nameresolveorder"
+TARGET="_top"
+> name resolve order</A
+> described in <A
+HREF="smb.conf.5.html"
+TARGET="_top"
+> <TT
+CLASS="FILENAME"
+>smb.conf(5)</TT
+></A
+>
+ to resolve any NetBIOS name queries needed by the server. Note
+ that the contents of this file are <I
+CLASS="EMPHASIS"
+>NOT</I
+>
+ used by <B
+CLASS="COMMAND"
+>nmbd</B
+> to answer any name queries.
Adding a line to this file affects name NetBIOS resolution
- from this host <span class="emphasis"><em>ONLY</em></span>.</p><p>The default path to this file is compiled into
+ from this host <I
+CLASS="EMPHASIS"
+>ONLY</I
+>.</P
+><P
+>The default path to this file is compiled into
Samba as part of the build process. Common defaults
- are <tt>/usr/local/samba/lib/lmhosts</tt>,
- <tt>/usr/samba/lib/lmhosts</tt> or
- <tt>/etc/samba/lmhosts</tt>. See the <a href="lmhosts.5.html">lmhosts(5)</a> man page for details on the contents of this file.</p></dd><dt><span class="term">-V</span></dt><dd><p>Prints the version number for
-<b>smbd</b>.</p></dd><dt><span class="term">-s &lt;configuration file&gt;</span></dt><dd><p>The file specified contains the
-configuration details required by the server. The
-information in this file includes server-specific
-information such as what printcap file to use, as well
-as descriptions of all the services that the server is
-to provide. See <a href="smb.conf.5.html" target="_top"><tt>
-smb.conf(5)</tt></a> for more information.
-The default configuration file name is determined at
-compile time.</p></dd><dt><span class="term">-d|--debug=debuglevel</span></dt><dd><p><i><tt>debuglevel</tt></i> is an integer
-from 0 to 10. The default value if this parameter is
-not specified is zero.</p><p>The higher this value, the more detail will be
-logged to the log files about the activities of the
-server. At level 0, only critical errors and serious
-warnings will be logged. Level 1 is a reasonable level for
-day to day running - it generates a small amount of
-information about operations carried out.</p><p>Levels above 1 will generate considerable
-amounts of log data, and should only be used when
-investigating a problem. Levels above 3 are designed for
-use only by developers and generate HUGE amounts of log
-data, most of which is extremely cryptic.</p><p>Note that specifying this parameter here will
-override the <a href="smb.conf.5.html#loglevel" target="_top">log
-level</a> parameter in the <a href="smb.conf.5.html" target="_top">
-<tt>smb.conf(5)</tt></a> file.</p></dd><dt><span class="term">-l|--logfile=logbasename</span></dt><dd><p>File name for log/debug files. The extension
-<tt>&quot;.client&quot;</tt> will be appended. The log file is
-never removed by the client.
-</p></dd><dt><span class="term">-p &lt;UDP port number&gt;</span></dt><dd><p>UDP port number is a positive integer value.
+ are <TT
+CLASS="FILENAME"
+>/usr/local/samba/lib/lmhosts</TT
+>,
+ <TT
+CLASS="FILENAME"
+>/usr/samba/lib/lmhosts</TT
+> or
+ <TT
+CLASS="FILENAME"
+>/etc/lmhosts</TT
+>. See the
+ <A
+HREF="lmhosts.5.html"
+TARGET="_top"
+><TT
+CLASS="FILENAME"
+>lmhosts(5)</TT
+></A
+>
+ man page for details on the contents of this file.</P
+></DD
+><DT
+>-V</DT
+><DD
+><P
+>Prints the version number for
+ <B
+CLASS="COMMAND"
+>nmbd</B
+>.</P
+></DD
+><DT
+>-d &#60;debug level&#62;</DT
+><DD
+><P
+>debuglevel is an integer
+ from 0 to 10. The default value if this parameter is
+ not specified is zero.</P
+><P
+>The higher this value, the more detail will
+ be logged to the log files about the activities of the
+ server. At level 0, only critical errors and serious
+ warnings will be logged. Level 1 is a reasonable level for
+ day to day running - it generates a small amount of
+ information about operations carried out.</P
+><P
+>Levels above 1 will generate considerable amounts
+ of log data, and should only be used when investigating
+ a problem. Levels above 3 are designed for use only by developers
+ and generate HUGE amounts of log data, most of which is extremely
+ cryptic.</P
+><P
+>Note that specifying this parameter here will override
+ the <A
+HREF="smb.conf.5.html#loglevel"
+TARGET="_top"
+>log level</A
+>
+ parameter in the <A
+HREF="smb.conf.5.html"
+TARGET="_top"
+><TT
+CLASS="FILENAME"
+> smb.conf(5)</TT
+></A
+> file.</P
+></DD
+><DT
+>-l &#60;log directory&#62;</DT
+><DD
+><P
+>The -l parameter specifies a directory
+ into which the "log.nmbd" log file will be created
+ for operational data from the running <B
+CLASS="COMMAND"
+>nmbd</B
+>
+ server. The default log directory is compiled into Samba
+ as part of the build process. Common defaults are <TT
+CLASS="FILENAME"
+> /usr/local/samba/var/log.nmb</TT
+>, <TT
+CLASS="FILENAME"
+> /usr/samba/var/log.nmb</TT
+> or
+ <TT
+CLASS="FILENAME"
+>/var/log/log.nmb</TT
+>. <I
+CLASS="EMPHASIS"
+>Beware:</I
+>
+ If the directory specified does not exist, <B
+CLASS="COMMAND"
+>nmbd</B
+>
+ will log to the default debug log location defined at compile time.
+ </P
+></DD
+><DT
+>-n &#60;primary NetBIOS name&#62;</DT
+><DD
+><P
+>This option allows you to override
+ the NetBIOS name that Samba uses for itself. This is identical
+ to setting the <A
+HREF="smb.conf.5.html#netbiosname"
+TARGET="_top"
+> NetBIOS name</A
+> parameter in the <A
+HREF="smb.conf.5.html"
+TARGET="_top"
+>
+ <TT
+CLASS="FILENAME"
+>smb.conf</TT
+></A
+> file. However, a command
+ line setting will take precedence over settings in
+ <TT
+CLASS="FILENAME"
+>smb.conf</TT
+>.</P
+></DD
+><DT
+>-p &#60;UDP port number&#62;</DT
+><DD
+><P
+>UDP port number is a positive integer value.
This option changes the default UDP port number (normally 137)
- that <b>nmbd</b> responds to name queries on. Don't
+ that <B
+CLASS="COMMAND"
+>nmbd</B
+> responds to name queries on. Don't
use this option unless you are an expert, in which case you
- won't need help!</p></dd></dl></div></div><div class="refsect1" lang="en"><h2>FILES</h2><div class="variablelist"><dl><dt><span class="term"><tt>/etc/inetd.conf</tt></span></dt><dd><p>If the server is to be run by the
- <b>inetd</b> meta-daemon, this file
+ won't need help!</P
+></DD
+><DT
+>-s &#60;configuration file&#62;</DT
+><DD
+><P
+>The default configuration file name
+ is set at build time, typically as <TT
+CLASS="FILENAME"
+> /usr/local/samba/lib/smb.conf</TT
+>, but
+ this may be changed when Samba is autoconfigured.</P
+><P
+>The file specified contains the configuration details
+ required by the server. See <A
+HREF="smb.conf.5.html"
+TARGET="_top"
+> <TT
+CLASS="FILENAME"
+>smb.conf(5)</TT
+></A
+> for more information.
+ </P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN148"
+></A
+><H2
+>FILES</H2
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+><TT
+CLASS="FILENAME"
+>/etc/inetd.conf</TT
+></DT
+><DD
+><P
+>If the server is to be run by the
+ <B
+CLASS="COMMAND"
+>inetd</B
+> meta-daemon, this file
must contain suitable startup information for the
- meta-daemon. See the <a href="install.html" target="_top">install</a> document
+ meta-daemon. See the <A
+HREF="UNIX_INSTALL.html"
+TARGET="_top"
+>UNIX_INSTALL.html</A
+> document
for details.
- </p></dd><dt><span class="term"><tt>/etc/rc</tt></span></dt><dd><p>or whatever initialization script your
- system uses).</p><p>If running the server as a daemon at startup,
+ </P
+></DD
+><DT
+><TT
+CLASS="FILENAME"
+>/etc/rc</TT
+></DT
+><DD
+><P
+>or whatever initialization script your
+ system uses).</P
+><P
+>If running the server as a daemon at startup,
this file will need to contain an appropriate startup
- sequence for the server. See the <a href="install.html" target="_top">&quot;How to Install and Test SAMBA&quot;</a> document
- for details.</p></dd><dt><span class="term"><tt>/etc/services</tt></span></dt><dd><p>If running the server via the
- meta-daemon <b>inetd</b>, this file
+ sequence for the server. See the <A
+HREF="UNIX_INSTALL.html"
+TARGET="_top"
+>UNIX_INSTALL.html</A
+> document
+ for details.</P
+></DD
+><DT
+><TT
+CLASS="FILENAME"
+>/etc/services</TT
+></DT
+><DD
+><P
+>If running the server via the
+ meta-daemon <B
+CLASS="COMMAND"
+>inetd</B
+>, this file
must contain a mapping of service name (e.g., netbios-ssn)
to service port (e.g., 139) and protocol type (e.g., tcp).
- See the <a href="install.html" target="_top">&quot;How to Install and Test SAMBA&quot;</a>
- document for details.</p></dd><dt><span class="term"><tt>/usr/local/samba/lib/smb.conf</tt></span></dt><dd><p>This is the default location of
- the <a href="smb.conf.5.html">smb.conf(5)</a> server
- configuration file. Other common places that systems
- install this file are <tt>/usr/samba/lib/smb.conf</tt>
- and <tt>/etc/samba/smb.conf</tt>.</p><p>When run as a WINS server (see the
- <a href="smb.conf.5.html#WINSSUPPORT" target="_top"><tt>wins support</tt></a>
- parameter in the <a href="smb.conf.5.html">smb.conf(5)</a> man page),
- <b>nmbd</b>
- will store the WINS database in the file <tt>wins.dat</tt>
- in the <tt>var/locks</tt> directory configured under
- wherever Samba was configured to install itself.</p><p>If <b>nmbd</b> is acting as a <span class="emphasis"><em>
- browse master</em></span> (see the <a href="smb.conf.5.html#LOCALMASTER" target="_top"><tt>local master</tt></a>
- parameter in the <a href="smb.conf.5.html">smb.conf(5)</a> man page, <b>nmbd</b>
- will store the browsing database in the file <tt>browse.dat
- </tt> in the <tt>var/locks</tt> directory
+ See the <A
+HREF="UNIX_INSTALL.html"
+TARGET="_top"
+>UNIX_INSTALL.html</A
+>
+ document for details.</P
+></DD
+><DT
+><TT
+CLASS="FILENAME"
+>/usr/local/samba/lib/smb.conf</TT
+></DT
+><DD
+><P
+>This is the default location of the
+ <A
+HREF="smb.conf.5.html"
+TARGET="_top"
+><TT
+CLASS="FILENAME"
+>smb.conf</TT
+></A
+>
+ server configuration file. Other common places that systems
+ install this file are <TT
+CLASS="FILENAME"
+>/usr/samba/lib/smb.conf</TT
+>
+ and <TT
+CLASS="FILENAME"
+>/etc/smb.conf</TT
+>.</P
+><P
+>When run as a WINS server (see the
+ <A
+HREF="smb.conf.5.html#WINSSUPPORT"
+TARGET="_top"
+>wins support</A
+>
+ parameter in the <TT
+CLASS="FILENAME"
+>smb.conf(5)</TT
+> man page),
+ <B
+CLASS="COMMAND"
+>nmbd</B
+>
+ will store the WINS database in the file <TT
+CLASS="FILENAME"
+>wins.dat</TT
+>
+ in the <TT
+CLASS="FILENAME"
+>var/locks</TT
+> directory configured under
+ wherever Samba was configured to install itself.</P
+><P
+>If <B
+CLASS="COMMAND"
+>nmbd</B
+> is acting as a <I
+CLASS="EMPHASIS"
+> browse master</I
+> (see the <A
+HREF="smb.conf.5.html#LOCALMASTER"
+TARGET="_top"
+>local master</A
+>
+ parameter in the <TT
+CLASS="FILENAME"
+>smb.conf(5)</TT
+> man page,
+ <B
+CLASS="COMMAND"
+>nmbd</B
+>
+ will store the browsing database in the file <TT
+CLASS="FILENAME"
+>browse.dat
+ </TT
+> in the <TT
+CLASS="FILENAME"
+>var/locks</TT
+> directory
configured under wherever Samba was configured to install itself.
- </p></dd></dl></div></div><div class="refsect1" lang="en"><h2>SIGNALS</h2><p>To shut down an <b>nmbd</b> process it is recommended
- that SIGKILL (-9) <span class="emphasis"><em>NOT</em></span> be used, except as a last
+ </P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN195"
+></A
+><H2
+>SIGNALS</H2
+><P
+>To shut down an <B
+CLASS="COMMAND"
+>nmbd</B
+> process it is recommended
+ that SIGKILL (-9) <I
+CLASS="EMPHASIS"
+>NOT</I
+> be used, except as a last
resort, as this may leave the name database in an inconsistent state.
- The correct way to terminate <b>nmbd</b> is to send it
- a SIGTERM (-15) signal and wait for it to die on its own.</p><p><b>nmbd</b> will accept SIGHUP, which will cause
- it to dump out its namelists into the file <tt>namelist.debug
- </tt> in the <tt>/usr/local/samba/var/locks</tt>
- directory (or the <tt>var/locks</tt> directory configured
+ The correct way to terminate <B
+CLASS="COMMAND"
+>nmbd</B
+> is to send it
+ a SIGTERM (-15) signal and wait for it to die on its own.</P
+><P
+><B
+CLASS="COMMAND"
+>nmbd</B
+> will accept SIGHUP, which will cause
+ it to dump out its namelists into the file <TT
+CLASS="FILENAME"
+>namelist.debug
+ </TT
+> in the <TT
+CLASS="FILENAME"
+>/usr/local/samba/var/locks</TT
+>
+ directory (or the <TT
+CLASS="FILENAME"
+>var/locks</TT
+> directory configured
under wherever Samba was configured to install itself). This will also
- cause <b>nmbd</b> to dump out its server database in
- the <tt>log.nmb</tt> file.</p><p>The debug log level of nmbd may be raised or lowered
- using <a href="smbcontrol.1.html">smbcontrol(1)</a> (SIGUSR[1|2] signals
- are no longer used since Samba 2.2). This is to allow
- transient problems to be diagnosed, whilst still running
- at a normally low log level.</p></div><div class="refsect1" lang="en"><h2>VERSION</h2><p>This man page is correct for version 3.0 of
- the Samba suite.</p></div><div class="refsect1" lang="en"><h2>SEE ALSO</h2><p>
- <a href="inetd.8.html">inetd(8)</a>, <a href="smbd.8.html">smbd(8)</a>, <a href="smb.conf.5.html">smb.conf(5)</a>, <a href="smbclient.1.html">smbclient(1)</a>, <a href="testparm.1.html">testparm(1)</a>, <a href="testprns.1.html">testprns(1)</a>, and the Internet
- RFC's <tt>rfc1001.txt</tt>, <tt>rfc1002.txt</tt>.
+ cause <B
+CLASS="COMMAND"
+>nmbd</B
+> to dump out its server database in
+ the <TT
+CLASS="FILENAME"
+>log.nmb</TT
+> file.</P
+><P
+>The debug log level of nmbd may be raised or lowered using
+ <A
+HREF="smbcontrol.1.html"
+TARGET="_top"
+><B
+CLASS="COMMAND"
+>smbcontrol(1)</B
+>
+ </A
+> (SIGUSR[1|2] signals are no longer used in Samba 2.2). This is
+ to allow transient problems to be diagnosed, whilst still running
+ at a normally low log level.</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN211"
+></A
+><H2
+>VERSION</H2
+><P
+>This man page is correct for version 3.0 of
+ the Samba suite.</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN214"
+></A
+><H2
+>SEE ALSO</H2
+><P
+><B
+CLASS="COMMAND"
+>inetd(8)</B
+>, <A
+HREF="smbd.8.html"
+TARGET="_top"
+><B
+CLASS="COMMAND"
+>smbd(8)</B
+></A
+>,
+ <A
+HREF="smb.conf.5.html"
+TARGET="_top"
+><TT
+CLASS="FILENAME"
+>smb.conf(5)</TT
+>
+ </A
+>, <A
+HREF="smbclient.1.html"
+TARGET="_top"
+><B
+CLASS="COMMAND"
+>smbclient(1)
+ </B
+></A
+>, <A
+HREF="testparm.1.html"
+TARGET="_top"
+><B
+CLASS="COMMAND"
+> testparm(1)</B
+></A
+>, <A
+HREF="testprns.1.html"
+TARGET="_top"
+> <B
+CLASS="COMMAND"
+>testprns(1)</B
+></A
+>, and the Internet RFC's
+ <TT
+CLASS="FILENAME"
+>rfc1001.txt</TT
+>, <TT
+CLASS="FILENAME"
+>rfc1002.txt</TT
+>.
In addition the CIFS (formerly SMB) specification is available
- as a link from the Web page <a href="http://samba.org/cifs/" target="_top">
- http://samba.org/cifs/</a>.</p></div><div class="refsect1" lang="en"><h2>AUTHOR</h2><p>The original Samba software and related utilities
+ as a link from the Web page <A
+HREF="http://samba.org/cifs/"
+TARGET="_top"
+>
+ http://samba.org/cifs/</A
+>.</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN231"
+></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.
+ to the way the Linux kernel is developed.</P
+><P
+>The original Samba man pages were written by Karl Auer.
The man page sources were converted to YODL format (another
- excellent piece of Open Source software, available at <a href="ftp://ftp.icce.rug.nl/pub/unix/" target="_top">
- ftp://ftp.icce.rug.nl/pub/unix/</a>) and updated for the Samba 2.0
+ excellent piece of Open Source software, available at
+ <A
+HREF="ftp://ftp.icce.rug.nl/pub/unix/"
+TARGET="_top"
+> ftp://ftp.icce.rug.nl/pub/unix/</A
+>) and updated for the Samba 2.0
release by Jeremy Allison. The conversion to DocBook for
- Samba 2.2 was done by Gerald Carter. The conversion to DocBook
- XML 4.2 for Samba 3.0 was done by Alexander Bokovoy.</p></div></div></body></html>
+ Samba 2.2 was done by Gerald Carter</P
+></DIV
+></BODY
+></HTML
+> \ No newline at end of file
diff --git a/docs/htmldocs/nmblookup.1.html b/docs/htmldocs/nmblookup.1.html
index 851544f0d8..2ce322990f 100644
--- a/docs/htmldocs/nmblookup.1.html
+++ b/docs/htmldocs/nmblookup.1.html
@@ -1,107 +1,412 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>nmblookup</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="nmblookup"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>nmblookup &#8212; NetBIOS over TCP/IP client used to lookup NetBIOS
- names</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><tt>nmblookup</tt> [-M] [-R] [-S] [-r] [-A] [-h] [-B &lt;broadcast address&gt;] [-U &lt;unicast address&gt;] [-d &lt;debug level&gt;] [-s &lt;smb config file&gt;] [-i &lt;NetBIOS scope&gt;] [-T] [-f] {name}</p></div></div><div class="refsect1" lang="en"><h2>DESCRIPTION</h2><p>This tool is part of the <a href="Samba.7.html">Samba(7)</a> suite.</p><p><b>nmblookup</b> is used to query NetBIOS names
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<HTML
+><HEAD
+><TITLE
+>nmblookup</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.77"></HEAD
+><BODY
+CLASS="REFENTRY"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><H1
+><A
+NAME="NMBLOOKUP"
+></A
+>nmblookup</H1
+><DIV
+CLASS="REFNAMEDIV"
+><A
+NAME="AEN5"
+></A
+><H2
+>Name</H2
+>nmblookup&nbsp;--&nbsp;NetBIOS over TCP/IP client used to lookup NetBIOS
+ names</DIV
+><DIV
+CLASS="REFSYNOPSISDIV"
+><A
+NAME="AEN8"
+></A
+><H2
+>Synopsis</H2
+><P
+><B
+CLASS="COMMAND"
+>nmblookup</B
+> [-M] [-R] [-S] [-r] [-A] [-h] [-B &lt;broadcast address&gt;] [-U &lt;unicast address&gt;] [-d &lt;debug level&gt;] [-s &lt;smb config file&gt;] [-i &lt;NetBIOS scope&gt;] [-T] [-f] {name}</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN25"
+></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"
+>nmblookup</B
+> is used to query NetBIOS names
and map them to IP addresses in a network using NetBIOS over TCP/IP
queries. The options allow the name queries to be directed at a
particular IP broadcast area or to a particular machine. All queries
- are done over UDP.</p></div><div class="refsect1" lang="en"><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-M</span></dt><dd><p>Searches for a master browser by looking
- up the NetBIOS name <i><tt>name</tt></i> with a
- type of <tt>0x1d</tt>. If <i><tt>
- name</tt></i> is &quot;-&quot; then it does a lookup on the special name
- <tt>__MSBROWSE__</tt>. Please note that in order to
- use the name &quot;-&quot;, you need to make sure &quot;-&quot; isn't parsed as an
- argument, e.g. use :
- <b><tt>nmblookup -M -- -</tt></b>.</p></dd><dt><span class="term">-R</span></dt><dd><p>Set the recursion desired bit in the packet
+ are done over UDP.</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN31"
+></A
+><H2
+>OPTIONS</H2
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>-M</DT
+><DD
+><P
+>Searches for a master browser by looking
+ up the NetBIOS name <TT
+CLASS="REPLACEABLE"
+><I
+>name</I
+></TT
+> with a
+ type of <TT
+CLASS="CONSTANT"
+>0x1d</TT
+>. If <TT
+CLASS="REPLACEABLE"
+><I
+> name</I
+></TT
+> is "-" then it does a lookup on the special name
+ <TT
+CLASS="CONSTANT"
+>__MSBROWSE__</TT
+>.</P
+></DD
+><DT
+>-R</DT
+><DD
+><P
+>Set the recursion desired bit in the packet
to do a recursive lookup. This is used when sending a name
query to a machine running a WINS server and the user wishes
to query the names in the WINS server. If this bit is unset
the normal (broadcast responding) NetBIOS processing code
- on a machine is used instead. See RFC1001, RFC1002 for details.
- </p></dd><dt><span class="term">-S</span></dt><dd><p>Once the name query has returned an IP
+ on a machine is used instead. See rfc1001, rfc1002 for details.
+ </P
+></DD
+><DT
+>-S</DT
+><DD
+><P
+>Once the name query has returned an IP
address then do a node status query as well. A node status
query returns the NetBIOS names registered by a host.
- </p></dd><dt><span class="term">-r</span></dt><dd><p>Try and bind to UDP port 137 to send and receive UDP
+ </P
+></DD
+><DT
+>-r</DT
+><DD
+><P
+>Try and bind to UDP port 137 to send and receive UDP
datagrams. The reason for this option is a bug in Windows 95
where it ignores the source port of the requesting packet
and only replies to UDP port 137. Unfortunately, on most UNIX
systems root privilege is needed to bind to this port, and
- in addition, if the <a href="nmbd.8.html">nmbd(8)</a> daemon is running on this machine it also binds to this port.
- </p></dd><dt><span class="term">-A</span></dt><dd><p>Interpret <i><tt>name</tt></i> as
- an IP Address and do a node status query on this address.</p></dd><dt><span class="term">-n &lt;primary NetBIOS name&gt;</span></dt><dd><p>This option allows you to override
-the NetBIOS name that Samba uses for itself. This is identical
-to setting the <a href="smb.conf.5.html#netbiosname" target="_top"><i><tt>NetBIOS
-name</tt></i></a> parameter in the <a href="smb.conf.5.html">smb.conf(5)</a> file. However, a command
-line setting will take precedence over settings in
-<a href="smb.conf.5.html">smb.conf(5)</a>.</p></dd><dt><span class="term">-i &lt;scope&gt;</span></dt><dd><p>This specifies a NetBIOS scope that
-<b>nmblookup</b> will use to communicate with when
-generating NetBIOS names. For details on the use of NetBIOS
-scopes, see rfc1001.txt and rfc1002.txt. NetBIOS scopes are
-<span class="emphasis"><em>very</em></span> rarely used, only set this parameter
-if you are the system administrator in charge of all the
-NetBIOS systems you communicate with.</p></dd><dt><span class="term">-W|--workgroup=domain</span></dt><dd><p>Set the SMB domain of the username. This
-overrides the default domain which is the domain defined in
-smb.conf. If the domain specified is the same as the servers
-NetBIOS name, it causes the client to log on using the servers local
-SAM (as opposed to the Domain SAM). </p></dd><dt><span class="term">-O socket options</span></dt><dd><p>TCP socket options to set on the client
-socket. See the socket options parameter in
-the <a href="smb.conf.5.html">smb.conf(5)</a> manual page for the list of valid
-options. </p></dd><dt><span class="term">-h|--help</span></dt><dd><p>Print a summary of command line options.
-</p></dd><dt><span class="term">-B &lt;broadcast address&gt;</span></dt><dd><p>Send the query to the given broadcast address. Without
+ in addition, if the <A
+HREF="nmbd.8.html"
+TARGET="_top"
+>nmbd(8)</A
+>
+ daemon is running on this machine it also binds to this port.
+ </P
+></DD
+><DT
+>-A</DT
+><DD
+><P
+>Interpret <TT
+CLASS="REPLACEABLE"
+><I
+>name</I
+></TT
+> as
+ an IP Address and do a node status query on this address.</P
+></DD
+><DT
+>-h</DT
+><DD
+><P
+>Print a help (usage) message.</P
+></DD
+><DT
+>-B &lt;broadcast address&gt;</DT
+><DD
+><P
+>Send the query to the given broadcast address. Without
this option the default behavior of nmblookup is to send the
query to the broadcast address of the network interfaces as
- either auto-detected or defined in the <a href="smb.conf.5.html#INTERFACES" target="_top"><i><tt>interfaces</tt></i>
- </a> parameter of the <a href="smb.conf.5.html">smb.conf(5)</a> file.
- </p></dd><dt><span class="term">-U &lt;unicast address&gt;</span></dt><dd><p>Do a unicast query to the specified address or
- host <i><tt>unicast address</tt></i>. This option
- (along with the <i><tt>-R</tt></i> option) is needed to
- query a WINS server.</p></dd><dt><span class="term">-V</span></dt><dd><p>Prints the version number for
-<b>smbd</b>.</p></dd><dt><span class="term">-s &lt;configuration file&gt;</span></dt><dd><p>The file specified contains the
-configuration details required by the server. The
-information in this file includes server-specific
-information such as what printcap file to use, as well
-as descriptions of all the services that the server is
-to provide. See <a href="smb.conf.5.html" target="_top"><tt>
-smb.conf(5)</tt></a> for more information.
-The default configuration file name is determined at
-compile time.</p></dd><dt><span class="term">-d|--debug=debuglevel</span></dt><dd><p><i><tt>debuglevel</tt></i> is an integer
-from 0 to 10. The default value if this parameter is
-not specified is zero.</p><p>The higher this value, the more detail will be
-logged to the log files about the activities of the
-server. At level 0, only critical errors and serious
-warnings will be logged. Level 1 is a reasonable level for
-day to day running - it generates a small amount of
-information about operations carried out.</p><p>Levels above 1 will generate considerable
-amounts of log data, and should only be used when
-investigating a problem. Levels above 3 are designed for
-use only by developers and generate HUGE amounts of log
-data, most of which is extremely cryptic.</p><p>Note that specifying this parameter here will
-override the <a href="smb.conf.5.html#loglevel" target="_top">log
-level</a> parameter in the <a href="smb.conf.5.html" target="_top">
-<tt>smb.conf(5)</tt></a> file.</p></dd><dt><span class="term">-l|--logfile=logbasename</span></dt><dd><p>File name for log/debug files. The extension
-<tt>&quot;.client&quot;</tt> will be appended. The log file is
-never removed by the client.
-</p></dd><dt><span class="term">-T</span></dt><dd><p>This causes any IP addresses found in the
+ either auto-detected or defined in the <A
+HREF="smb.conf.5.html#INTERFACES"
+TARGET="_top"
+><TT
+CLASS="PARAMETER"
+><I
+>interfaces</I
+></TT
+>
+ </A
+> parameter of the <TT
+CLASS="FILENAME"
+>smb.conf (5)</TT
+> file.
+ </P
+></DD
+><DT
+>-U &lt;unicast address&gt;</DT
+><DD
+><P
+>Do a unicast query to the specified address or
+ host <TT
+CLASS="REPLACEABLE"
+><I
+>unicast address</I
+></TT
+>. This option
+ (along with the <TT
+CLASS="PARAMETER"
+><I
+>-R</I
+></TT
+> option) is needed to
+ query a WINS server.</P
+></DD
+><DT
+>-d &lt;debuglevel&gt;</DT
+><DD
+><P
+>debuglevel is an integer from 0 to 10.</P
+><P
+>The default value if this parameter is not specified
+ is zero.</P
+><P
+>The higher this value, the more detail will be logged
+ about the activities of <B
+CLASS="COMMAND"
+>nmblookup</B
+>. At level
+ 0, only critical errors and serious warnings will be logged.</P
+><P
+>Levels above 1 will generate considerable amounts of
+ log data, and should only be used when investigating a problem.
+ Levels above 3 are designed for use only by developers and
+ generate HUGE amounts of data, most of which is extremely cryptic.</P
+><P
+>Note that specifying this parameter here will override
+ the <A
+HREF="smb.conf.5.html#LOGLEVEL"
+TARGET="_top"
+><TT
+CLASS="PARAMETER"
+><I
+> log level</I
+></TT
+></A
+> parameter in the <TT
+CLASS="FILENAME"
+> smb.conf(5)</TT
+> file.</P
+></DD
+><DT
+>-s &lt;smb.conf&gt;</DT
+><DD
+><P
+>This parameter specifies the pathname to
+ the Samba configuration file, <A
+HREF="smb.conf.5.html"
+TARGET="_top"
+> smb.conf(5)</A
+>. This file controls all aspects of
+ the Samba setup on the machine.</P
+></DD
+><DT
+>-i &lt;scope&gt;</DT
+><DD
+><P
+>This specifies a NetBIOS scope that
+ <B
+CLASS="COMMAND"
+>nmblookup</B
+> will use to communicate with when
+ generating NetBIOS names. For details on the use of NetBIOS
+ scopes, see rfc1001.txt and rfc1002.txt. NetBIOS scopes are
+ <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>very</I
+></SPAN
+> rarely used, only set this parameter
+ if you are the system administrator in charge of all the
+ NetBIOS systems you communicate with.</P
+></DD
+><DT
+>-T</DT
+><DD
+><P
+>This causes any IP addresses found in the
lookup to be looked up via a reverse DNS lookup into a
- DNS name, and printed out before each</p><p><span class="emphasis"><em>IP address .... NetBIOS name</em></span></p><p> pair that is the normal output.</p></dd><dt><span class="term">-f</span></dt><dd><p>
- Show which flags apply to the name that has been looked up. Possible
+ DNS name, and printed out before each</P
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>IP address .... NetBIOS name</I
+></SPAN
+></P
+><P
+> pair that is the normal output.</P
+></DD
+><DT
+>-f</DT
+><DD
+><P
+> Show which flags apply to the name that has been looked up. Possible
answers are zero or more of: Response, Authoritative,
Truncated, Recursion_Desired, Recursion_Available, Broadcast.
- </p></dd><dt><span class="term">name</span></dt><dd><p>This is the NetBIOS name being queried. Depending
+ </P
+></DD
+><DT
+>name</DT
+><DD
+><P
+>This is the NetBIOS name being queried. Depending
upon the previous options this may be a NetBIOS name or IP address.
If a NetBIOS name then the different name types may be specified
by appending '#&lt;type&gt;' to the name. This name may also be
'*', which will return all registered names within a broadcast
- area.</p></dd></dl></div></div><div class="refsect1" lang="en"><h2>EXAMPLES</h2><p><b>nmblookup</b> can be used to query
- a WINS server (in the same way <b>nslookup</b> is
- used to query DNS servers). To query a WINS server, <b>nmblookup</b>
- must be called like this:</p><p><b>nmblookup -U server -R 'name'</b></p><p>For example, running :</p><p><b>nmblookup -U samba.org -R 'IRIX#1B'</b></p><p>would query the WINS server samba.org for the domain
- master browser (1B name type) for the IRIX workgroup.</p></div><div class="refsect1" lang="en"><h2>VERSION</h2><p>This man page is correct for version 3.0 of
- the Samba suite.</p></div><div class="refsect1" lang="en"><h2>SEE ALSO</h2><p><a href="nmbd.8.html">nmbd(8)</a>, <a href="samba.7.html">samba(7)</a>, and <a href="smb.conf.5.html">smb.conf(5)</a>.</p></div><div class="refsect1" lang="en"><h2>AUTHOR</h2><p>The original Samba software and related utilities
+ area.</P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN115"
+></A
+><H2
+>EXAMPLES</H2
+><P
+><B
+CLASS="COMMAND"
+>nmblookup</B
+> can be used to query
+ a WINS server (in the same way <B
+CLASS="COMMAND"
+>nslookup</B
+> is
+ used to query DNS servers). To query a WINS server,
+ <B
+CLASS="COMMAND"
+>nmblookup</B
+> must be called like this:</P
+><P
+><B
+CLASS="COMMAND"
+>nmblookup -U server -R 'name'</B
+></P
+><P
+>For example, running :</P
+><P
+><B
+CLASS="COMMAND"
+>nmblookup -U samba.org -R 'IRIX#1B'</B
+></P
+><P
+>would query the WINS server samba.org for the domain
+ master browser (1B name type) for the IRIX workgroup.</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN127"
+></A
+><H2
+>VERSION</H2
+><P
+>This man page is correct for version 3.0 of
+ the Samba suite.</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN130"
+></A
+><H2
+>SEE ALSO</H2
+><P
+><A
+HREF="nmbd.8.html"
+TARGET="_top"
+><B
+CLASS="COMMAND"
+>nmbd(8)</B
+></A
+>,
+ <A
+HREF="samba.7.html"
+TARGET="_top"
+>samba(7)</A
+>, and <A
+HREF="smb.conf.5.html"
+TARGET="_top"
+>smb.conf(5)</A
+>
+ </P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN137"
+></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.
+ to the way the Linux kernel is developed.</P
+><P
+>The original Samba man pages were written by Karl Auer.
The man page sources were converted to YODL format (another
- excellent piece of Open Source software, available at <a href="ftp://ftp.icce.rug.nl/pub/unix/" target="_top">
- ftp://ftp.icce.rug.nl/pub/unix/</a>) and updated for the Samba 2.0
+ excellent piece of Open Source software, available at
+ <A
+HREF="ftp://ftp.icce.rug.nl/pub/unix/"
+TARGET="_top"
+> ftp://ftp.icce.rug.nl/pub/unix/</A
+>) and updated for the Samba 2.0
release by Jeremy Allison. The conversion to DocBook for
- Samba 2.2 was done by Gerald Carter. The conversion to DocBook
- XML 4.2 for Samba 3.0 was done by Alexander Bokovoy.</p></div></div></body></html>
+ Samba 2.2 was done by Gerald Carter</P
+></DIV
+></BODY
+></HTML
+> \ No newline at end of file
diff --git a/docs/htmldocs/nt4migration.html b/docs/htmldocs/nt4migration.html
deleted file mode 100644
index 2079c1b6c4..0000000000
--- a/docs/htmldocs/nt4migration.html
+++ /dev/null
@@ -1,356 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<HTML
-><HEAD
-><TITLE
->Migration from NT4 PDC to Samba-3 PDC</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
-REL="HOME"
-TITLE="SAMBA Project Documentation"
-HREF="samba-howto-collection.html"><LINK
-REL="UP"
-TITLE="Appendixes"
-HREF="appendixes.html"><LINK
-REL="PREVIOUS"
-TITLE="How to compile SAMBA"
-HREF="compiling.html"><LINK
-REL="NEXT"
-TITLE="Portability"
-HREF="portability.html"></HEAD
-><BODY
-CLASS="CHAPTER"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->SAMBA Project Documentation</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="compiling.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
-></TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="portability.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="CHAPTER"
-><H1
-><A
-NAME="NT4MIGRATION"
-></A
->Chapter 28. Migration from NT4 PDC to Samba-3 PDC</H1
-><DIV
-CLASS="TOC"
-><DL
-><DT
-><B
->Table of Contents</B
-></DT
-><DT
->28.1. <A
-HREF="nt4migration.html#AEN4396"
->Planning and Getting Started</A
-></DT
-><DD
-><DL
-><DT
->28.1.1. <A
-HREF="nt4migration.html#AEN4400"
->Objectives</A
-></DT
-><DT
->28.1.2. <A
-HREF="nt4migration.html#AEN4426"
->Steps In Migration Process</A
-></DT
-></DL
-></DD
-><DT
->28.2. <A
-HREF="nt4migration.html#AEN4429"
->Managing Samba-3 Domain Control</A
-></DT
-></DL
-></DIV
-><P
->This is a rough guide to assist those wishing to migrate from NT4 domain control to
-Samba-3 based domain control.</P
-><DIV
-CLASS="SECT1"
-><H1
-CLASS="SECT1"
-><A
-NAME="AEN4396"
->28.1. Planning and Getting Started</A
-></H1
-><P
->In the IT world there is often a saying that all problems are encountered because of
-poor planning. The corrollary to this saying is that not all problems can be anticpated
-and planned for. Then again, good planning will anticpate most show stopper type situations.</P
-><P
->Those wishing to migrate from MS Windows NT4 domain control to a Samba-3 domain control
-environment would do well to develop a detailed migration plan. So here are a few pointers to
-help migration get under way.</P
-><DIV
-CLASS="SECT2"
-><H2
-CLASS="SECT2"
-><A
-NAME="AEN4400"
->28.1.1. Objectives</A
-></H2
-><P
->The key objective for most organisations will be to make the migration from MS Windows NT4
-to Samba-3 domain control as painless as possible. One of the challenges you may experience
-in your migration process may well be one of convincing management that the new environment
-should remain in place. Many who have introduced open source technologies have experienced
-pressure to return to a Microsoft based platform solution at the first sign of trouble. </P
-><P
->It is strongly advised that before attempting a migration to a Samba-3 controlled network
-that every possible effort be made to gain all-round commitment to the change. Firstly, you
-should know precisely <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->why</I
-></SPAN
-> the change is important for the organisation.
-Possible motivations to make a change include:</P
-><P
-></P
-><UL
-><LI
-><P
->Improve network manageability</P
-></LI
-><LI
-><P
->Obtain better user level functionality</P
-></LI
-><LI
-><P
->Reduce network operating costs</P
-></LI
-><LI
-><P
->Reduce exposure caused by Microsoft withdrawal of NT4 support</P
-></LI
-><LI
-><P
->Avoid MS License 6 implications</P
-></LI
-><LI
-><P
->Reduce organisation's dependency on Microsoft</P
-></LI
-></UL
-><P
->It is vital that oit be well recognised that Samba-3 is NOT MS Windows NT4. Samba-3 offers
-an alternative solution that is both different from MS Windows NT4 and that offers some
-advantages compared with it. It should also be recognised that Samba-3 lacks many of the
-features that Microsoft has promoted as core values in migration from MS Windows NT4 to
-MS Windows 2000 and beyond (with or without Active Directory services).</P
-><P
->What are the features the Samba-3 can NOT provide?</P
-><P
-></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
->Active Directory Server</TD
-></TR
-><TR
-><TD
->Group Policy Objects (in Active Direcrtory)</TD
-></TR
-><TR
-><TD
->Machine Policy objects</TD
-></TR
-><TR
-><TD
->Logon Scripts in Active Directorty</TD
-></TR
-><TR
-><TD
->Software Application and Access Controls in Active Directory</TD
-></TR
-></TBODY
-></TABLE
-><P
-></P
-></DIV
-><DIV
-CLASS="SECT2"
-><H2
-CLASS="SECT2"
-><A
-NAME="AEN4426"
->28.1.2. Steps In Migration Process</A
-></H2
-><P
->This is not a definitive ste-by-step process yet - just a place holder so the info
-is not lost.
-
-1. You will have an NT4 PDC that has the users, groups, policies and profiles to be migrated
-
-2. Samba-3 set up as a DC with netlogon share, profile share, etc.
-
-3. Process:
- a. Create a BDC account for the samba server using NT Server Manager
- - Samba must NOT be running
-
- b. rpcclient NT4PDC -U Administrator%passwd
- lsaquery
-
- Note the SID returned by step b.
-
- c. net getsid -S NT4PDC -w DOMNAME -U Administrator%passwd
-
- Note the SID in step c.
-
- d. net getlocalsid
-
- Note the SID, now check that all three SIDS reported are the same!
-
- e. net rpc join -S NT4PDC -w DOMNAME -U Administrator%passwd
-
- f. net rpc vampire -S NT4PDC -U administrator%passwd
-
- g. pdbedit -l
-
- Note - did the users migrate?
-
- h. initGrps.sh DOMNAME
-
- i. smbgroupedit -v
-
- Now check that all groups are recognised
-
- j. net rpc campire -S NT4PDC -U administrator%passwd
-
- k. pdbedit -lv
-
- Note - check that all group membership has been migrated.
-
-
-Now it is time to migrate all the profiles, then migrate all policy files.
-
-Moe later.</P
-></DIV
-></DIV
-><DIV
-CLASS="SECT1"
-><H1
-CLASS="SECT1"
-><A
-NAME="AEN4429"
->28.2. Managing Samba-3 Domain Control</A
-></H1
-><P
->Lots of blah blah here.</P
-></DIV
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="compiling.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="samba-howto-collection.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="portability.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->How to compile SAMBA</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="appendixes.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Portability</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
-> \ No newline at end of file
diff --git a/docs/htmldocs/oplocks.html b/docs/htmldocs/oplocks.html
new file mode 100644
index 0000000000..6aa91fb17f
--- /dev/null
+++ b/docs/htmldocs/oplocks.html
@@ -0,0 +1,208 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<HTML
+><HEAD
+><TITLE
+>Oplocks</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.77"><LINK
+REL="HOME"
+TITLE="SAMBA Project Documentation"
+HREF="samba-howto-collection.html"><LINK
+REL="UP"
+TITLE="General installation"
+HREF="introduction.html"><LINK
+REL="PREVIOUS"
+TITLE="Improved browsing in samba"
+HREF="improved-browsing.html"><LINK
+REL="NEXT"
+TITLE="Quick Cross Subnet Browsing / Cross Workgroup Browsing guide"
+HREF="browsing-quick.html"></HEAD
+><BODY
+CLASS="CHAPTER"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><TABLE
+SUMMARY="Header navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>SAMBA Project Documentation</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="improved-browsing.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+></TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="browsing-quick.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="CHAPTER"
+><H1
+><A
+NAME="OPLOCKS"
+></A
+>Chapter 3. Oplocks</H1
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN378"
+></A
+>3.1. What are oplocks?</H1
+><P
+>When a client opens a file it can request an "oplock" or file
+lease. This is (to simplify a bit) a guarentee that no one else
+has the file open simultaneously. It allows the client to not
+send any updates on the file to the server, thus reducing a
+network file access to local access (once the file is in
+client cache). An "oplock break" is when the server sends
+a request to the client to flush all its changes back to
+the server, so the file is in a consistent state for other
+opens to succeed. If a client fails to respond to this
+asynchronous request then the file can be corrupted. Hence
+the "turn off oplocks" answer if people are having multi-user
+file access problems.</P
+><P
+>Unless the kernel is "oplock aware" (SGI IRIX and Linux are
+the only two UNIXes that are at the moment) then if a local
+UNIX process accesses the file simultaneously then Samba
+has no way of telling this is occuring, so the guarentee
+to the client is broken. This can corrupt the file. Short
+answer - it you have UNIX clients accessing the same file
+as smbd locally or via NFS and you're not running Linux or
+IRIX then turn off oplocks for that file or share.</P
+><P
+>"Share modes". These are modes of opening a file, that
+guarentee an invarient - such as DENY_WRITE - which means
+that if any other opens are requested with write access after
+this current open has succeeded then they should be denied
+with a "sharing violation" error message. Samba handles these
+internally inside smbd. UNIX clients accessing the same file
+ignore these invarients. Just proving that if you need simultaneous
+file access from a Windows and UNIX client you *must* have an
+application that is written to lock records correctly on both
+sides. Few applications are written like this, and even fewer
+are cross platform (UNIX and Windows) so in practice this isn't
+much of a problem.</P
+><P
+>"Locking". This really means "byte range locking" - such as
+lock 10 bytes at file offset 24 for write access. This is the
+area in which well written UNIX and Windows apps will cooperate.
+Windows locks (at least from NT or above) are 64-bit unsigned
+offsets. UNIX locks are either 31 bit or 63 bit and are signed
+(the top bit is used for the sign). Samba handles these by
+first ensuring that all the Windows locks don't conflict (ie.
+if other Windows clients have competing locks then just reject
+immediately) - this allows us to support 64-bit Windows locks
+on 32-bit filesystems. Secondly any locks that are valid are
+then mapped onto UNIX fcntl byte range locks. These are the
+locks that will be seen by UNIX processes. If there is a conflict
+here the lock is rejected.</P
+><P
+>Note that if a client has an oplock then it "knows" that no
+other client can have the file open so usually doesn't bother
+to send to lock request to the server - this means once again
+if you need to share files between UNIX and Windows processes
+either use IRIX or Linux, or turn off oplocks for these
+files/shares.</P
+></DIV
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+SUMMARY="Footer navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="improved-browsing.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="samba-howto-collection.html"
+ACCESSKEY="H"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="browsing-quick.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>Improved browsing in samba</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="introduction.html"
+ACCESSKEY="U"
+>Up</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>Quick Cross Subnet Browsing / Cross Workgroup Browsing guide</TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+> \ No newline at end of file
diff --git a/docs/htmldocs/optional.html b/docs/htmldocs/optional.html
index 33f7a02b7c..b15515ddab 100644
--- a/docs/htmldocs/optional.html
+++ b/docs/htmldocs/optional.html
@@ -1,7 +1,898 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>PartIII.Advanced Configuration</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"><link rel="home" href="index.html" title="SAMBA Project Documentation"><link rel="up" href="index.html" title="SAMBA Project Documentation"><link rel="previous" href="domain-member.html" title="Chapter8.Samba as a NT4 or Win2k domain member"><link rel="next" href="NetworkBrowsing.html" title="Chapter9.Samba / MS Windows Network Browsing Guide"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">PartIII.Advanced Configuration</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="domain-member.html">Prev</a></td><th width="60%" align="center"></th><td width="20%" align="right"><a accesskey="n" href="NetworkBrowsing.html">Next</a></td></tr></table><hr></div><div class="part" lang="en"><div class="titlepage"><div><h1 class="title"><a name="optional"></a>Advanced Configuration</h1></div></div><div class="partintro" lang="en"><div><div><h1 class="title"><a name="id2812389"></a>Valuable Nuts and Bolts Information</h1></div></div><p>
-Samba has several features that you might want or might not want to use. The chapters in this part each cover specific Samba features.
-</p><div class="toc"><p><b>Table of Contents</b></p><dl><dt>9. <a href="NetworkBrowsing.html">Samba / MS Windows Network Browsing Guide</a></dt><dd><dl><dt><a href="NetworkBrowsing.html#id2879892">What is Browsing?</a></dt><dt><a href="NetworkBrowsing.html#id2880542">Discussion</a></dt><dt><a href="NetworkBrowsing.html#id2880704">How Browsing Functions</a></dt><dd><dl><dt><a href="NetworkBrowsing.html#id2880831">Setting up WORKGROUP Browsing</a></dt><dt><a href="NetworkBrowsing.html#id2881020">Setting up DOMAIN Browsing</a></dt><dt><a href="NetworkBrowsing.html#browse-force-master">Forcing samba to be the master</a></dt><dt><a href="NetworkBrowsing.html#id2881285">Making samba the domain master</a></dt><dt><a href="NetworkBrowsing.html#id2881434">Note about broadcast addresses</a></dt><dt><a href="NetworkBrowsing.html#id2881451">Multiple interfaces</a></dt><dt><a href="NetworkBrowsing.html#id2881480">Use of the Remote Announce parameter</a></dt><dt><a href="NetworkBrowsing.html#id2881591">Use of the Remote Browse Sync parameter</a></dt></dl></dd><dt><a href="NetworkBrowsing.html#id2881658">WINS - The Windows Internetworking Name Server</a></dt><dd><dl><dt><a href="NetworkBrowsing.html#id2880482">Setting up a WINS server</a></dt><dt><a href="NetworkBrowsing.html#id2882114">WINS Replication</a></dt><dt><a href="NetworkBrowsing.html#id2882139">Static WINS Entries</a></dt></dl></dd><dt><a href="NetworkBrowsing.html#id2882170">Helpful Hints</a></dt><dd><dl><dt><a href="NetworkBrowsing.html#id2882183">Windows Networking Protocols</a></dt><dt><a href="NetworkBrowsing.html#id2882250">Name Resolution Order</a></dt></dl></dd><dt><a href="NetworkBrowsing.html#id2882366">Technical Overview of browsing</a></dt><dd><dl><dt><a href="NetworkBrowsing.html#id2882413">Browsing support in samba</a></dt><dt><a href="NetworkBrowsing.html#id2882520">Problem resolution</a></dt><dt><a href="NetworkBrowsing.html#id2882599">Browsing across subnets</a></dt></dl></dd></dl></dd><dt>10. <a href="passdb.html">User information database</a></dt><dd><dl><dt><a href="passdb.html#id2882995">Introduction</a></dt><dt><a href="passdb.html#id2883048">Important Notes About Security</a></dt><dd><dl><dt><a href="passdb.html#id2883210">Advantages of SMB Encryption</a></dt><dt><a href="passdb.html#id2883249">Advantages of non-encrypted passwords</a></dt></dl></dd><dt><a href="passdb.html#id2883283">The smbpasswd Command</a></dt><dt><a href="passdb.html#id2883464">Plain text</a></dt><dt><a href="passdb.html#id2883493">TDB</a></dt><dt><a href="passdb.html#id2883509">LDAP</a></dt><dd><dl><dt><a href="passdb.html#id2883516">Introduction</a></dt><dt><a href="passdb.html#id2883617">Encrypted Password Database</a></dt><dt><a href="passdb.html#id2883756">Supported LDAP Servers</a></dt><dt><a href="passdb.html#id2883794">Schema and Relationship to the RFC 2307 posixAccount</a></dt><dt><a href="passdb.html#id2883904">Configuring Samba with LDAP</a></dt><dt><a href="passdb.html#id2884200">Accounts and Groups management</a></dt><dt><a href="passdb.html#id2884237">Security and sambaAccount</a></dt><dt><a href="passdb.html#id2884352">LDAP specials attributes for sambaAccounts</a></dt><dt><a href="passdb.html#id2884633">Example LDIF Entries for a sambaAccount</a></dt></dl></dd><dt><a href="passdb.html#id2884689">MySQL</a></dt><dd><dl><dt><a href="passdb.html#id2884696">Creating the database</a></dt><dt><a href="passdb.html#id2884750">Configuring</a></dt><dt><a href="passdb.html#id2884895">Using plaintext passwords or encrypted password</a></dt><dt><a href="passdb.html#id2884925">Getting non-column data from the table</a></dt></dl></dd><dt><a href="passdb.html#id2884968">XML</a></dt></dl></dd><dt>11. <a href="unix-permissions.html">UNIX Permission Bits and Windows NT Access Control Lists</a></dt><dd><dl><dt><a href="unix-permissions.html#id2881950">Viewing and changing UNIX permissions using the NT
- security dialogs</a></dt><dt><a href="unix-permissions.html#id2881832">How to view file security on a Samba share</a></dt><dt><a href="unix-permissions.html#id2885176">Viewing file ownership</a></dt><dt><a href="unix-permissions.html#id2885297">Viewing file or directory permissions</a></dt><dd><dl><dt><a href="unix-permissions.html#id2885379">File Permissions</a></dt><dt><a href="unix-permissions.html#id2885483">Directory Permissions</a></dt></dl></dd><dt><a href="unix-permissions.html#id2885533">Modifying file or directory permissions</a></dt><dt><a href="unix-permissions.html#id2885693">Interaction with the standard Samba create mask
- parameters</a></dt><dt><a href="unix-permissions.html#id2886008">Interaction with the standard Samba file attribute
- mapping</a></dt></dl></dd><dt>12. <a href="groupmapping.html">Configuring Group Mapping</a></dt><dt>13. <a href="printing.html">Printing Support</a></dt><dd><dl><dt><a href="printing.html#id2886394">Introduction</a></dt><dt><a href="printing.html#id2886510">Configuration</a></dt><dd><dl><dt><a href="printing.html#id2886557">Creating [print$]</a></dt><dt><a href="printing.html#id2886789">Setting Drivers for Existing Printers</a></dt><dt><a href="printing.html#id2886888">Support a large number of printers</a></dt><dt><a href="printing.html#id2886995">Adding New Printers via the Windows NT APW</a></dt><dt><a href="printing.html#id2887127">Samba and Printer Ports</a></dt></dl></dd><dt><a href="printing.html#id2886128">The Imprints Toolset</a></dt><dd><dl><dt><a href="printing.html#id2886155">What is Imprints?</a></dt><dt><a href="printing.html#id2887231">Creating Printer Driver Packages</a></dt><dt><a href="printing.html#id2887251">The Imprints server</a></dt><dt><a href="printing.html#id2887275">The Installation Client</a></dt></dl></dd><dt><a href="printing.html#id2886236">Diagnosis</a></dt><dd><dl><dt><a href="printing.html#id2886243">Introduction</a></dt><dt><a href="printing.html#id2887448">Debugging printer problems</a></dt><dt><a href="printing.html#id2887515">What printers do I have?</a></dt><dt><a href="printing.html#id2887557">Setting up printcap and print servers</a></dt><dt><a href="printing.html#id2887691">Job sent, no output</a></dt><dt><a href="printing.html#id2888240">Job sent, strange output</a></dt><dt><a href="printing.html#id2888316">Raw PostScript printed</a></dt><dt><a href="printing.html#id2888334">Advanced Printing</a></dt><dt><a href="printing.html#id2888360">Real debugging</a></dt></dl></dd></dl></dd><dt>14. <a href="CUPS-printing.html">CUPS Printing Support</a></dt><dd><dl><dt><a href="CUPS-printing.html#id2887904">Introduction</a></dt><dt><a href="CUPS-printing.html#id2887963">Configuring smb.conf for CUPS</a></dt><dt><a href="CUPS-printing.html#id2888503">CUPS - RAW Print Through Mode</a></dt><dt><a href="CUPS-printing.html#id2887987">CUPS as a network PostScript RIP</a></dt><dt><a href="CUPS-printing.html#id2889168">Windows Terminal Servers (WTS) as CUPS clients</a></dt><dt><a href="CUPS-printing.html#id2889210">Setting up CUPS for driver download</a></dt><dt><a href="CUPS-printing.html#id2889297">Sources of CUPS drivers / PPDs</a></dt><dd><dl><dt><a href="CUPS-printing.html#id2889462">cupsaddsmb</a></dt></dl></dd><dt><a href="CUPS-printing.html#id2889811">The CUPS Filter Chains</a></dt><dt><a href="CUPS-printing.html#id2890198">CUPS Print Drivers and Devices</a></dt><dd><dl><dt><a href="CUPS-printing.html#id2890235">Further printing steps</a></dt></dl></dd><dt><a href="CUPS-printing.html#id2890654">Limiting the number of pages users can print</a></dt><dt><a href="CUPS-printing.html#id2891263">Advanced Postscript Printing from MS Windows</a></dt><dt><a href="CUPS-printing.html#id2891369">Auto-Deletion of CUPS spool files</a></dt></dl></dd><dt>15. <a href="winbind.html">Unified Logons between Windows NT and UNIX using Winbind</a></dt><dd><dl><dt><a href="winbind.html#id2891610">Abstract</a></dt><dt><a href="winbind.html#id2891639">Introduction</a></dt><dt><a href="winbind.html#id2891710">What Winbind Provides</a></dt><dd><dl><dt><a href="winbind.html#id2888972">Target Uses</a></dt></dl></dd><dt><a href="winbind.html#id2889003">How Winbind Works</a></dt><dd><dl><dt><a href="winbind.html#id2889031">Microsoft Remote Procedure Calls</a></dt><dt><a href="winbind.html#id2889066">Microsoft Active Directory Services</a></dt><dt><a href="winbind.html#id2889088">Name Service Switch</a></dt><dt><a href="winbind.html#id2892176">Pluggable Authentication Modules</a></dt><dt><a href="winbind.html#id2892248">User and Group ID Allocation</a></dt><dt><a href="winbind.html#id2892282">Result Caching</a></dt></dl></dd><dt><a href="winbind.html#id2892310">Installation and Configuration</a></dt><dd><dl><dt><a href="winbind.html#id2892338">Introduction</a></dt><dt><a href="winbind.html#id2892413">Requirements</a></dt><dt><a href="winbind.html#id2892507">Testing Things Out</a></dt></dl></dd><dt><a href="winbind.html#id2894106">Limitations</a></dt><dt><a href="winbind.html#id2894160">Conclusion</a></dt></dl></dd><dt>16. <a href="AdvancedNetworkManagement.html">Advanced Network Manangement</a></dt><dd><dl><dt><a href="AdvancedNetworkManagement.html#id2892036">Configuring Samba Share Access Controls</a></dt><dd><dl><dt><a href="AdvancedNetworkManagement.html#id2891799">Share Permissions Management</a></dt></dl></dd><dt><a href="AdvancedNetworkManagement.html#id2891866">Remote Server Administration</a></dt><dt><a href="AdvancedNetworkManagement.html#id2891949">Network Logon Script Magic</a></dt><dd><dl><dt><a href="AdvancedNetworkManagement.html#id2894784">Adding printers without user intervention</a></dt></dl></dd></dl></dd><dt>17. <a href="PolicyMgmt.html">System and Account Policies</a></dt><dd><dl><dt><a href="PolicyMgmt.html#id2894568">Creating and Managing System Policies</a></dt><dd><dl><dt><a href="PolicyMgmt.html#id2894821">Windows 9x/Me Policies</a></dt><dt><a href="PolicyMgmt.html#id2894910">Windows NT4 Style Policy Files</a></dt><dt><a href="PolicyMgmt.html#id2895036">MS Windows 200x / XP Professional Policies</a></dt></dl></dd><dt><a href="PolicyMgmt.html#id2895240">Managing Account/User Policies</a></dt><dd><dl><dt><a href="PolicyMgmt.html#id2895353">With Windows NT4/200x</a></dt><dt><a href="PolicyMgmt.html#id2895374">With a Samba PDC</a></dt></dl></dd><dt><a href="PolicyMgmt.html#id2895398">System Startup and Logon Processing Overview</a></dt></dl></dd><dt>18. <a href="ProfileMgmt.html">Desktop Profile Management</a></dt><dd><dl><dt><a href="ProfileMgmt.html#id2894496">Roaming Profiles</a></dt><dd><dl><dt><a href="ProfileMgmt.html#id2894382">Samba Configuration for Profile Handling</a></dt><dt><a href="ProfileMgmt.html#id2895976">Windows Client Profile Configuration Information</a></dt><dt><a href="ProfileMgmt.html#id2896591">Sharing Profiles between W9x/Me and NT4/200x/XP workstations</a></dt><dt><a href="ProfileMgmt.html#id2896638">Profile Migration from Windows NT4/200x Server to Samba</a></dt></dl></dd><dt><a href="ProfileMgmt.html#id2896821">Mandatory profiles</a></dt><dt><a href="ProfileMgmt.html#id2896866">Creating/Managing Group Profiles</a></dt><dt><a href="ProfileMgmt.html#id2896907">Default Profile for Windows Users</a></dt><dd><dl><dt><a href="ProfileMgmt.html#id2896936">MS Windows 9x/Me</a></dt><dt><a href="ProfileMgmt.html#id2897025">MS Windows NT4 Workstation</a></dt><dt><a href="ProfileMgmt.html#id2897409">MS Windows 200x/XP</a></dt></dl></dd></dl></dd><dt>19. <a href="InterdomainTrusts.html">Interdomain Trust Relationships</a></dt><dd><dl><dt><a href="InterdomainTrusts.html#id2895580">Trust Relationship Background</a></dt><dt><a href="InterdomainTrusts.html#id2897902">Native MS Windows NT4 Trusts Configuration</a></dt><dd><dl><dt><a href="InterdomainTrusts.html#id2897915">NT4 as the Trusting Domain (ie. creating the trusted account)</a></dt><dt><a href="InterdomainTrusts.html#id2897959">NT4 as the Trusted Domain (ie. creating trusted account's password)</a></dt></dl></dd><dt><a href="InterdomainTrusts.html#id2897983">Configuring Samba NT-style Domain Trusts</a></dt><dd><dl><dt><a href="InterdomainTrusts.html#id2898010">Samba-3 as the Trusting Domain</a></dt><dt><a href="InterdomainTrusts.html#id2898106">Samba-3 as the Trusted Domain</a></dt></dl></dd></dl></dd><dt>20. <a href="pam.html">PAM Configuration for Centrally Managed Authentication</a></dt><dd><dl><dt><a href="pam.html#id2897853">Samba and PAM</a></dt><dd><dl><dt><a href="pam.html#id2898634">PAM Configuration in smb.conf</a></dt><dt><a href="pam.html#id2898691">Password Synchronisation using pam_smbpass.so</a></dt></dl></dd><dt><a href="pam.html#id2898943">Distributed Authentication</a></dt></dl></dd><dt>21. <a href="VFS.html">Stackable VFS modules</a></dt><dd><dl><dt><a href="VFS.html#id2898226">Introduction and configuration</a></dt><dt><a href="VFS.html#id2899145">Included modules</a></dt><dd><dl><dt><a href="VFS.html#id2899152">audit</a></dt><dt><a href="VFS.html#id2899191">extd_audit</a></dt><dt><a href="VFS.html#id2899312">recycle</a></dt><dt><a href="VFS.html#id2899450">netatalk</a></dt></dl></dd><dt><a href="VFS.html#id2899488">VFS modules available elsewhere</a></dt><dd><dl><dt><a href="VFS.html#id2899510">DatabaseFS</a></dt><dt><a href="VFS.html#id2899565">vscan</a></dt></dl></dd></dl></dd><dt>22. <a href="msdfs.html">Hosting a Microsoft Distributed File System tree on Samba</a></dt><dd><dl><dt><a href="msdfs.html#id2899111">Instructions</a></dt><dd><dl><dt><a href="msdfs.html#id2899858">Notes</a></dt></dl></dd></dl></dd><dt>23. <a href="integrate-ms-networks.html">Integrating MS Windows networks with Samba</a></dt><dd><dl><dt><a href="integrate-ms-networks.html#id2899641">Name Resolution in a pure Unix/Linux world</a></dt><dd><dl><dt><a href="integrate-ms-networks.html#id2900075">/etc/hosts</a></dt><dt><a href="integrate-ms-networks.html#id2900212">/etc/resolv.conf</a></dt><dt><a href="integrate-ms-networks.html#id2900256">/etc/host.conf</a></dt><dt><a href="integrate-ms-networks.html#id2900299">/etc/nsswitch.conf</a></dt></dl></dd><dt><a href="integrate-ms-networks.html#id2900394">Name resolution as used within MS Windows networking</a></dt><dd><dl><dt><a href="integrate-ms-networks.html#id2899927">The NetBIOS Name Cache</a></dt><dt><a href="integrate-ms-networks.html#id2899966">The LMHOSTS file</a></dt><dt><a href="integrate-ms-networks.html#id2900009">HOSTS file</a></dt><dt><a href="integrate-ms-networks.html#id2900041">DNS Lookup</a></dt><dt><a href="integrate-ms-networks.html#id2900053">WINS Lookup</a></dt></dl></dd></dl></dd><dt>24. <a href="securing-samba.html">Securing Samba</a></dt><dd><dl><dt><a href="securing-samba.html#id2900501">Introduction</a></dt><dt><a href="securing-samba.html#id2900517">Using host based protection</a></dt><dt><a href="securing-samba.html#id2900967">Using interface protection</a></dt><dt><a href="securing-samba.html#id2901018">Using a firewall</a></dt><dt><a href="securing-samba.html#id2901061">Using a IPC$ share deny</a></dt><dt><a href="securing-samba.html#id2900617">NTLMv2 Security</a></dt><dt><a href="securing-samba.html#id2900653">Upgrading Samba</a></dt></dl></dd><dt>25. <a href="unicode.html">Unicode/Charsets</a></dt><dd><dl><dt><a href="unicode.html#id2901255">What are charsets and unicode?</a></dt><dt><a href="unicode.html#id2901324">Samba and charsets</a></dt><dt><a href="unicode.html#id2901414">Conversion from old names</a></dt><dt><a href="unicode.html#id2901459">Japanese charsets</a></dt></dl></dd><dt>26. <a href="locking.html">File and Record Locking</a></dt><dd><dl><dt><a href="locking.html#id2901106">Discussion</a></dt><dt><a href="locking.html#id2901768">Samba Opportunistic Locking Control</a></dt><dt><a href="locking.html#id2901884">MS Windows Opportunistic Locking and Caching Controls</a></dt><dd><dl><dt><a href="locking.html#id2902109">Workstation Service Entries</a></dt><dt><a href="locking.html#id2902136">Server Service Entries</a></dt></dl></dd><dt><a href="locking.html#id2902216">Persistent Data Corruption</a></dt><dt><a href="locking.html#id2902247">Additional Reading</a></dt></dl></dd></dl></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="domain-member.html">Prev</a></td><td width="20%" align="center"><a accesskey="u" href="index.html">Up</a></td><td width="40%" align="right"><a accesskey="n" href="NetworkBrowsing.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter8.Samba as a NT4 or Win2k domain member</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">Chapter9.Samba / MS Windows Network Browsing Guide</td></tr></table></div></body></html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<HTML
+><HEAD
+><TITLE
+>Optional configuration</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
+REL="HOME"
+TITLE="SAMBA Project Documentation"
+HREF="samba-howto-collection.html"><LINK
+REL="PREVIOUS"
+TITLE="Samba as a NT4 domain member"
+HREF="domain-security.html"><LINK
+REL="NEXT"
+TITLE="Integrating MS Windows networks with Samba"
+HREF="integrate-ms-networks.html"></HEAD
+><BODY
+CLASS="PART"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><TABLE
+SUMMARY="Header navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>SAMBA Project Documentation</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="domain-security.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+></TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="integrate-ms-networks.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="PART"
+><A
+NAME="OPTIONAL"><DIV
+CLASS="TITLEPAGE"
+><H1
+CLASS="TITLE"
+>III. Optional configuration</H1
+><DIV
+CLASS="PARTINTRO"
+><A
+NAME="AEN1360"><H1
+>Introduction</H1
+><P
+>Samba has several features that you might want or might not want to use. The chapters in this
+part each cover one specific feature.</P
+></DIV
+><DIV
+CLASS="TOC"
+><DL
+><DT
+><B
+>Table of Contents</B
+></DT
+><DT
+>10. <A
+HREF="integrate-ms-networks.html"
+>Integrating MS Windows networks with Samba</A
+></DT
+><DD
+><DL
+><DT
+>10.1. <A
+HREF="integrate-ms-networks.html#AEN1374"
+>Agenda</A
+></DT
+><DT
+>10.2. <A
+HREF="integrate-ms-networks.html#AEN1396"
+>Name Resolution in a pure Unix/Linux world</A
+></DT
+><DD
+><DL
+><DT
+>10.2.1. <A
+HREF="integrate-ms-networks.html#AEN1412"
+><TT
+CLASS="FILENAME"
+>/etc/hosts</TT
+></A
+></DT
+><DT
+>10.2.2. <A
+HREF="integrate-ms-networks.html#AEN1428"
+><TT
+CLASS="FILENAME"
+>/etc/resolv.conf</TT
+></A
+></DT
+><DT
+>10.2.3. <A
+HREF="integrate-ms-networks.html#AEN1439"
+><TT
+CLASS="FILENAME"
+>/etc/host.conf</TT
+></A
+></DT
+><DT
+>10.2.4. <A
+HREF="integrate-ms-networks.html#AEN1447"
+><TT
+CLASS="FILENAME"
+>/etc/nsswitch.conf</TT
+></A
+></DT
+></DL
+></DD
+><DT
+>10.3. <A
+HREF="integrate-ms-networks.html#AEN1459"
+>Name resolution as used within MS Windows networking</A
+></DT
+><DD
+><DL
+><DT
+>10.3.1. <A
+HREF="integrate-ms-networks.html#AEN1471"
+>The NetBIOS Name Cache</A
+></DT
+><DT
+>10.3.2. <A
+HREF="integrate-ms-networks.html#AEN1476"
+>The LMHOSTS file</A
+></DT
+><DT
+>10.3.3. <A
+HREF="integrate-ms-networks.html#AEN1484"
+>HOSTS file</A
+></DT
+><DT
+>10.3.4. <A
+HREF="integrate-ms-networks.html#AEN1489"
+>DNS Lookup</A
+></DT
+><DT
+>10.3.5. <A
+HREF="integrate-ms-networks.html#AEN1492"
+>WINS Lookup</A
+></DT
+></DL
+></DD
+><DT
+>10.4. <A
+HREF="integrate-ms-networks.html#AEN1504"
+>How browsing functions and how to deploy stable and
+dependable browsing using Samba</A
+></DT
+><DT
+>10.5. <A
+HREF="integrate-ms-networks.html#AEN1514"
+>MS Windows security options and how to configure
+Samba for seemless integration</A
+></DT
+><DD
+><DL
+><DT
+>10.5.1. <A
+HREF="integrate-ms-networks.html#AEN1542"
+>Use MS Windows NT as an authentication server</A
+></DT
+><DT
+>10.5.2. <A
+HREF="integrate-ms-networks.html#AEN1550"
+>Make Samba a member of an MS Windows NT security domain</A
+></DT
+><DT
+>10.5.3. <A
+HREF="integrate-ms-networks.html#AEN1567"
+>Configure Samba as an authentication server</A
+></DT
+></DL
+></DD
+><DT
+>10.6. <A
+HREF="integrate-ms-networks.html#AEN1584"
+>Conclusions</A
+></DT
+></DL
+></DD
+><DT
+>11. <A
+HREF="unix-permissions.html"
+>UNIX Permission Bits and Windows NT Access Control Lists</A
+></DT
+><DD
+><DL
+><DT
+>11.1. <A
+HREF="unix-permissions.html#AEN1605"
+>Viewing and changing UNIX permissions using the NT
+ security dialogs</A
+></DT
+><DT
+>11.2. <A
+HREF="unix-permissions.html#AEN1614"
+>How to view file security on a Samba share</A
+></DT
+><DT
+>11.3. <A
+HREF="unix-permissions.html#AEN1625"
+>Viewing file ownership</A
+></DT
+><DT
+>11.4. <A
+HREF="unix-permissions.html#AEN1645"
+>Viewing file or directory permissions</A
+></DT
+><DD
+><DL
+><DT
+>11.4.1. <A
+HREF="unix-permissions.html#AEN1660"
+>File Permissions</A
+></DT
+><DT
+>11.4.2. <A
+HREF="unix-permissions.html#AEN1674"
+>Directory Permissions</A
+></DT
+></DL
+></DD
+><DT
+>11.5. <A
+HREF="unix-permissions.html#AEN1681"
+>Modifying file or directory permissions</A
+></DT
+><DT
+>11.6. <A
+HREF="unix-permissions.html#AEN1703"
+>Interaction with the standard Samba create mask
+ parameters</A
+></DT
+><DT
+>11.7. <A
+HREF="unix-permissions.html#AEN1767"
+>Interaction with the standard Samba file attribute
+ mapping</A
+></DT
+></DL
+></DD
+><DT
+>12. <A
+HREF="pam.html"
+>Configuring PAM for distributed but centrally
+managed authentication</A
+></DT
+><DD
+><DL
+><DT
+>12.1. <A
+HREF="pam.html#AEN1788"
+>Samba and PAM</A
+></DT
+><DT
+>12.2. <A
+HREF="pam.html#AEN1832"
+>Distributed Authentication</A
+></DT
+><DT
+>12.3. <A
+HREF="pam.html#AEN1839"
+>PAM Configuration in smb.conf</A
+></DT
+></DL
+></DD
+><DT
+>13. <A
+HREF="msdfs.html"
+>Hosting a Microsoft Distributed File System tree on Samba</A
+></DT
+><DD
+><DL
+><DT
+>13.1. <A
+HREF="msdfs.html#AEN1859"
+>Instructions</A
+></DT
+><DD
+><DL
+><DT
+>13.1.1. <A
+HREF="msdfs.html#AEN1894"
+>Notes</A
+></DT
+></DL
+></DD
+></DL
+></DD
+><DT
+>14. <A
+HREF="printing.html"
+>Printing Support</A
+></DT
+><DD
+><DL
+><DT
+>14.1. <A
+HREF="printing.html#AEN1920"
+>Introduction</A
+></DT
+><DT
+>14.2. <A
+HREF="printing.html#AEN1942"
+>Configuration</A
+></DT
+><DD
+><DL
+><DT
+>14.2.1. <A
+HREF="printing.html#AEN1950"
+>Creating [print$]</A
+></DT
+><DT
+>14.2.2. <A
+HREF="printing.html#AEN1985"
+>Setting Drivers for Existing Printers</A
+></DT
+><DT
+>14.2.3. <A
+HREF="printing.html#AEN2001"
+>Support a large number of printers</A
+></DT
+><DT
+>14.2.4. <A
+HREF="printing.html#AEN2012"
+>Adding New Printers via the Windows NT APW</A
+></DT
+><DT
+>14.2.5. <A
+HREF="printing.html#AEN2042"
+>Samba and Printer Ports</A
+></DT
+></DL
+></DD
+><DT
+>14.3. <A
+HREF="printing.html#AEN2050"
+>The Imprints Toolset</A
+></DT
+><DD
+><DL
+><DT
+>14.3.1. <A
+HREF="printing.html#AEN2054"
+>What is Imprints?</A
+></DT
+><DT
+>14.3.2. <A
+HREF="printing.html#AEN2064"
+>Creating Printer Driver Packages</A
+></DT
+><DT
+>14.3.3. <A
+HREF="printing.html#AEN2067"
+>The Imprints server</A
+></DT
+><DT
+>14.3.4. <A
+HREF="printing.html#AEN2071"
+>The Installation Client</A
+></DT
+></DL
+></DD
+><DT
+>14.4. <A
+HREF="printing.html#AEN2093"
+>Diagnosis</A
+></DT
+><DD
+><DL
+><DT
+>14.4.1. <A
+HREF="printing.html#AEN2095"
+>Introduction</A
+></DT
+><DT
+>14.4.2. <A
+HREF="printing.html#AEN2111"
+>Debugging printer problems</A
+></DT
+><DT
+>14.4.3. <A
+HREF="printing.html#AEN2120"
+>What printers do I have?</A
+></DT
+><DT
+>14.4.4. <A
+HREF="printing.html#AEN2128"
+>Setting up printcap and print servers</A
+></DT
+><DT
+>14.4.5. <A
+HREF="printing.html#AEN2156"
+>Job sent, no output</A
+></DT
+><DT
+>14.4.6. <A
+HREF="printing.html#AEN2167"
+>Job sent, strange output</A
+></DT
+><DT
+>14.4.7. <A
+HREF="printing.html#AEN2179"
+>Raw PostScript printed</A
+></DT
+><DT
+>14.4.8. <A
+HREF="printing.html#AEN2182"
+>Advanced Printing</A
+></DT
+><DT
+>14.4.9. <A
+HREF="printing.html#AEN2185"
+>Real debugging</A
+></DT
+></DL
+></DD
+></DL
+></DD
+><DT
+>15. <A
+HREF="winbind.html"
+>Unified Logons between Windows NT and UNIX using Winbind</A
+></DT
+><DD
+><DL
+><DT
+>15.1. <A
+HREF="winbind.html#AEN2225"
+>Abstract</A
+></DT
+><DT
+>15.2. <A
+HREF="winbind.html#AEN2229"
+>Introduction</A
+></DT
+><DT
+>15.3. <A
+HREF="winbind.html#AEN2242"
+>What Winbind Provides</A
+></DT
+><DD
+><DL
+><DT
+>15.3.1. <A
+HREF="winbind.html#AEN2249"
+>Target Uses</A
+></DT
+></DL
+></DD
+><DT
+>15.4. <A
+HREF="winbind.html#AEN2253"
+>How Winbind Works</A
+></DT
+><DD
+><DL
+><DT
+>15.4.1. <A
+HREF="winbind.html#AEN2258"
+>Microsoft Remote Procedure Calls</A
+></DT
+><DT
+>15.4.2. <A
+HREF="winbind.html#AEN2262"
+>Name Service Switch</A
+></DT
+><DT
+>15.4.3. <A
+HREF="winbind.html#AEN2278"
+>Pluggable Authentication Modules</A
+></DT
+><DT
+>15.4.4. <A
+HREF="winbind.html#AEN2286"
+>User and Group ID Allocation</A
+></DT
+><DT
+>15.4.5. <A
+HREF="winbind.html#AEN2290"
+>Result Caching</A
+></DT
+></DL
+></DD
+><DT
+>15.5. <A
+HREF="winbind.html#AEN2293"
+>Installation and Configuration</A
+></DT
+><DD
+><DL
+><DT
+>15.5.1. <A
+HREF="winbind.html#AEN2300"
+>Introduction</A
+></DT
+><DT
+>15.5.2. <A
+HREF="winbind.html#AEN2313"
+>Requirements</A
+></DT
+><DT
+>15.5.3. <A
+HREF="winbind.html#AEN2327"
+>Testing Things Out</A
+></DT
+></DL
+></DD
+><DT
+>15.6. <A
+HREF="winbind.html#AEN2542"
+>Limitations</A
+></DT
+><DT
+>15.7. <A
+HREF="winbind.html#AEN2552"
+>Conclusion</A
+></DT
+></DL
+></DD
+><DT
+>16. <A
+HREF="pdb-mysql.html"
+>Passdb MySQL plugin</A
+></DT
+><DD
+><DL
+><DT
+>16.1. <A
+HREF="pdb-mysql.html#AEN2566"
+>Building</A
+></DT
+><DT
+>16.2. <A
+HREF="pdb-mysql.html#AEN2572"
+>Configuring</A
+></DT
+><DT
+>16.3. <A
+HREF="pdb-mysql.html#AEN2589"
+>Using plaintext passwords or encrypted password</A
+></DT
+><DT
+>16.4. <A
+HREF="pdb-mysql.html#AEN2594"
+>Getting non-column data from the table</A
+></DT
+></DL
+></DD
+><DT
+>17. <A
+HREF="pdb-xml.html"
+>Passdb XML plugin</A
+></DT
+><DD
+><DL
+><DT
+>17.1. <A
+HREF="pdb-xml.html#AEN2613"
+>Building</A
+></DT
+><DT
+>17.2. <A
+HREF="pdb-xml.html#AEN2619"
+>Usage</A
+></DT
+></DL
+></DD
+><DT
+>18. <A
+HREF="vfs.html"
+>Stackable VFS modules</A
+></DT
+><DD
+><DL
+><DT
+>18.1. <A
+HREF="vfs.html#AEN2640"
+>Introduction and configuration</A
+></DT
+><DT
+>18.2. <A
+HREF="vfs.html#AEN2649"
+>Included modules</A
+></DT
+><DD
+><DL
+><DT
+>18.2.1. <A
+HREF="vfs.html#AEN2651"
+>audit</A
+></DT
+><DT
+>18.2.2. <A
+HREF="vfs.html#AEN2659"
+>recycle</A
+></DT
+><DT
+>18.2.3. <A
+HREF="vfs.html#AEN2696"
+>netatalk</A
+></DT
+></DL
+></DD
+><DT
+>18.3. <A
+HREF="vfs.html#AEN2703"
+>VFS modules available elsewhere</A
+></DT
+><DD
+><DL
+><DT
+>18.3.1. <A
+HREF="vfs.html#AEN2707"
+>DatabaseFS</A
+></DT
+><DT
+>18.3.2. <A
+HREF="vfs.html#AEN2715"
+>vscan</A
+></DT
+></DL
+></DD
+></DL
+></DD
+><DT
+>19. <A
+HREF="samba-ldap-howto.html"
+>Storing Samba's User/Machine Account information in an LDAP Directory</A
+></DT
+><DD
+><DL
+><DT
+>19.1. <A
+HREF="samba-ldap-howto.html#AEN2737"
+>Purpose</A
+></DT
+><DT
+>19.2. <A
+HREF="samba-ldap-howto.html#AEN2757"
+>Introduction</A
+></DT
+><DT
+>19.3. <A
+HREF="samba-ldap-howto.html#AEN2786"
+>Supported LDAP Servers</A
+></DT
+><DT
+>19.4. <A
+HREF="samba-ldap-howto.html#AEN2791"
+>Schema and Relationship to the RFC 2307 posixAccount</A
+></DT
+><DT
+>19.5. <A
+HREF="samba-ldap-howto.html#AEN2803"
+>Configuring Samba with LDAP</A
+></DT
+><DD
+><DL
+><DT
+>19.5.1. <A
+HREF="samba-ldap-howto.html#AEN2805"
+>OpenLDAP configuration</A
+></DT
+><DT
+>19.5.2. <A
+HREF="samba-ldap-howto.html#AEN2822"
+>Configuring Samba</A
+></DT
+></DL
+></DD
+><DT
+>19.6. <A
+HREF="samba-ldap-howto.html#AEN2850"
+>Accounts and Groups management</A
+></DT
+><DT
+>19.7. <A
+HREF="samba-ldap-howto.html#AEN2855"
+>Security and sambaAccount</A
+></DT
+><DT
+>19.8. <A
+HREF="samba-ldap-howto.html#AEN2875"
+>LDAP specials attributes for sambaAccounts</A
+></DT
+><DT
+>19.9. <A
+HREF="samba-ldap-howto.html#AEN2945"
+>Example LDIF Entries for a sambaAccount</A
+></DT
+><DT
+>19.10. <A
+HREF="samba-ldap-howto.html#AEN2953"
+>Comments</A
+></DT
+></DL
+></DD
+><DT
+>20. <A
+HREF="cvs-access.html"
+>HOWTO Access Samba source code via CVS</A
+></DT
+><DD
+><DL
+><DT
+>20.1. <A
+HREF="cvs-access.html#AEN2964"
+>Introduction</A
+></DT
+><DT
+>20.2. <A
+HREF="cvs-access.html#AEN2969"
+>CVS Access to samba.org</A
+></DT
+><DD
+><DL
+><DT
+>20.2.1. <A
+HREF="cvs-access.html#AEN2972"
+>Access via CVSweb</A
+></DT
+><DT
+>20.2.2. <A
+HREF="cvs-access.html#AEN2977"
+>Access via cvs</A
+></DT
+></DL
+></DD
+></DL
+></DD
+><DT
+>21. <A
+HREF="groupmapping.html"
+>Group mapping HOWTO</A
+></DT
+><DT
+>22. <A
+HREF="speed.html"
+>Samba performance issues</A
+></DT
+><DD
+><DL
+><DT
+>22.1. <A
+HREF="speed.html#AEN3055"
+>Comparisons</A
+></DT
+><DT
+>22.2. <A
+HREF="speed.html#AEN3061"
+>Socket options</A
+></DT
+><DT
+>22.3. <A
+HREF="speed.html#AEN3068"
+>Read size</A
+></DT
+><DT
+>22.4. <A
+HREF="speed.html#AEN3073"
+>Max xmit</A
+></DT
+><DT
+>22.5. <A
+HREF="speed.html#AEN3078"
+>Log level</A
+></DT
+><DT
+>22.6. <A
+HREF="speed.html#AEN3081"
+>Read raw</A
+></DT
+><DT
+>22.7. <A
+HREF="speed.html#AEN3086"
+>Write raw</A
+></DT
+><DT
+>22.8. <A
+HREF="speed.html#AEN3090"
+>Slow Clients</A
+></DT
+><DT
+>22.9. <A
+HREF="speed.html#AEN3094"
+>Slow Logins</A
+></DT
+><DT
+>22.10. <A
+HREF="speed.html#AEN3097"
+>Client tuning</A
+></DT
+></DL
+></DD
+></DL
+></DIV
+></DIV
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+SUMMARY="Footer navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="domain-security.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="samba-howto-collection.html"
+ACCESSKEY="H"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="integrate-ms-networks.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>Samba as a NT4 domain member</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+>&nbsp;</TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>Integrating MS Windows networks with Samba</TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+> \ No newline at end of file
diff --git a/docs/htmldocs/other-clients.html b/docs/htmldocs/other-clients.html
index 36513c672a..130c9691e7 100644
--- a/docs/htmldocs/other-clients.html
+++ b/docs/htmldocs/other-clients.html
@@ -5,7 +5,8 @@
>Samba and other CIFS clients</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
REL="HOME"
TITLE="SAMBA Project Documentation"
HREF="samba-howto-collection.html"><LINK
@@ -16,8 +17,8 @@ REL="PREVIOUS"
TITLE="Portability"
HREF="portability.html"><LINK
REL="NEXT"
-TITLE="SWAT - The Samba Web Admininistration Tool"
-HREF="swat.html"></HEAD
+TITLE="Reporting Bugs"
+HREF="bugreport.html"></HEAD
><BODY
CLASS="CHAPTER"
BGCOLOR="#FFFFFF"
@@ -59,7 +60,7 @@ WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
-HREF="swat.html"
+HREF="bugreport.html"
ACCESSKEY="N"
>Next</A
></TD
@@ -72,105 +73,7 @@ WIDTH="100%"></DIV
CLASS="CHAPTER"
><H1
><A
-NAME="OTHER-CLIENTS"
-></A
->Chapter 30. Samba and other CIFS clients</H1
-><DIV
-CLASS="TOC"
-><DL
-><DT
-><B
->Table of Contents</B
-></DT
-><DT
->30.1. <A
-HREF="other-clients.html#AEN4522"
->Macintosh clients?</A
-></DT
-><DT
->30.2. <A
-HREF="other-clients.html#AEN4531"
->OS2 Client</A
-></DT
-><DD
-><DL
-><DT
->30.2.1. <A
-HREF="other-clients.html#AEN4533"
->How can I configure OS/2 Warp Connect or
- OS/2 Warp 4 as a client for Samba?</A
-></DT
-><DT
->30.2.2. <A
-HREF="other-clients.html#AEN4548"
->How can I configure OS/2 Warp 3 (not Connect),
- OS/2 1.2, 1.3 or 2.x for Samba?</A
-></DT
-><DT
->30.2.3. <A
-HREF="other-clients.html#AEN4557"
->Are there any other issues when OS/2 (any version)
- is used as a client?</A
-></DT
-><DT
->30.2.4. <A
-HREF="other-clients.html#AEN4561"
->How do I get printer driver download working
- for OS/2 clients?</A
-></DT
-></DL
-></DD
-><DT
->30.3. <A
-HREF="other-clients.html#AEN4571"
->Windows for Workgroups</A
-></DT
-><DD
-><DL
-><DT
->30.3.1. <A
-HREF="other-clients.html#AEN4573"
->Use latest TCP/IP stack from Microsoft</A
-></DT
-><DT
->30.3.2. <A
-HREF="other-clients.html#AEN4578"
->Delete .pwl files after password change</A
-></DT
-><DT
->30.3.3. <A
-HREF="other-clients.html#AEN4583"
->Configure WfW password handling</A
-></DT
-><DT
->30.3.4. <A
-HREF="other-clients.html#AEN4587"
->Case handling of passwords</A
-></DT
-><DT
->30.3.5. <A
-HREF="other-clients.html#AEN4592"
->Use TCP/IP as default protocol</A
-></DT
-></DL
-></DD
-><DT
->30.4. <A
-HREF="other-clients.html#AEN4595"
->Windows '95/'98</A
-></DT
-><DT
->30.5. <A
-HREF="other-clients.html#AEN4611"
->Windows 2000 Service Pack 2</A
-></DT
-><DT
->30.6. <A
-HREF="other-clients.html#AEN4628"
->Windows NT 3.1</A
-></DT
-></DL
-></DIV
+NAME="OTHER-CLIENTS">Chapter 24. Samba and other CIFS clients</H1
><P
>This chapter contains client-specific information.</P
><DIV
@@ -178,9 +81,7 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="AEN4522"
->30.1. Macintosh clients?</A
-></H1
+NAME="AEN3199">24.1. Macintosh clients?</H1
><P
>Yes. <A
HREF="http://www.thursby.com/"
@@ -224,18 +125,14 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="AEN4531"
->30.2. OS2 Client</A
-></H1
+NAME="AEN3208">24.2. OS2 Client</H1
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
-NAME="AEN4533"
->30.2.1. How can I configure OS/2 Warp Connect or
- OS/2 Warp 4 as a client for Samba?</A
-></H2
+NAME="AEN3210">24.2.1. How can I configure OS/2 Warp Connect or
+ OS/2 Warp 4 as a client for Samba?</H2
><P
>A more complete answer to this question can be
found on <A
@@ -291,10 +188,8 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
-NAME="AEN4548"
->30.2.2. How can I configure OS/2 Warp 3 (not Connect),
- OS/2 1.2, 1.3 or 2.x for Samba?</A
-></H2
+NAME="AEN3225">24.2.2. How can I configure OS/2 Warp 3 (not Connect),
+ OS/2 1.2, 1.3 or 2.x for Samba?</H2
><P
>You can use the free Microsoft LAN Manager 2.2c Client
for OS/2 from
@@ -335,10 +230,8 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
-NAME="AEN4557"
->30.2.3. Are there any other issues when OS/2 (any version)
- is used as a client?</A
-></H2
+NAME="AEN3234">24.2.3. Are there any other issues when OS/2 (any version)
+ is used as a client?</H2
><P
>When you do a NET VIEW or use the "File and Print
Client Resource Browser", no Samba servers show up. This can
@@ -357,10 +250,8 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
-NAME="AEN4561"
->30.2.4. How do I get printer driver download working
- for OS/2 clients?</A
-></H2
+NAME="AEN3238">24.2.4. How do I get printer driver download working
+ for OS/2 clients?</H2
><P
>First, create a share called [PRINTDRV] that is
world-readable. Copy your OS/2 driver files there. Note
@@ -370,13 +261,17 @@ NAME="AEN4561"
><P
>Install the NT driver first for that printer. Then,
add to your smb.conf a parameter, os2 driver map =
- <VAR
+ <TT
CLASS="REPLACEABLE"
->filename</VAR
+><I
+>filename</I
+></TT
>". Then, in the file
- specified by <VAR
+ specified by <TT
CLASS="REPLACEABLE"
->filename</VAR
+><I
+>filename</I
+></TT
>, map the
name of the NT driver name to the OS/2 driver name as
follows:</P
@@ -404,17 +299,13 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="AEN4571"
->30.3. Windows for Workgroups</A
-></H1
+NAME="AEN3248">24.3. Windows for Workgroups</H1
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
-NAME="AEN4573"
->30.3.1. Use latest TCP/IP stack from Microsoft</A
-></H2
+NAME="AEN3250">24.3.1. Use latest TCP/IP stack from Microsoft</H2
><P
>Use the latest TCP/IP stack from microsoft if you use Windows
for workgroups.</P
@@ -434,9 +325,7 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
-NAME="AEN4578"
->30.3.2. Delete .pwl files after password change</A
-></H2
+NAME="AEN3255">24.3.2. Delete .pwl files after password change</H2
><P
>WfWg does a lousy job with passwords. I find that if I change my
password on either the unix box or the PC the safest thing to do is to
@@ -454,9 +343,7 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
-NAME="AEN4583"
->30.3.3. Configure WfW password handling</A
-></H2
+NAME="AEN3260">24.3.3. Configure WfW password handling</H2
><P
>There is a program call admincfg.exe
on the last disk (disk 8) of the WFW 3.11 disk set. To install it
@@ -473,9 +360,7 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
-NAME="AEN4587"
->30.3.4. Case handling of passwords</A
-></H2
+NAME="AEN3264">24.3.4. Case handling of passwords</H2
><P
>Windows for Workgroups uppercases the password before sending it to the server. Unix passwords can be case-sensitive though. Check the <A
HREF="smb.conf.5.html"
@@ -486,30 +371,13 @@ CLASS="COMMAND"
>password level</B
> to specify what characters samba should try to uppercase when checking.</P
></DIV
-><DIV
-CLASS="SECT2"
-><H2
-CLASS="SECT2"
-><A
-NAME="AEN4592"
->30.3.5. Use TCP/IP as default protocol</A
-></H2
-><P
->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
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="AEN4595"
->30.4. Windows '95/'98</A
-></H1
+NAME="AEN3269">24.4. Windows '95/'98</H1
><P
>When using Windows 95 OEM SR2 the following updates are recommended where Samba
is being used. Please NOTE that the above change will affect you once these
@@ -555,9 +423,7 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="AEN4611"
->30.5. Windows 2000 Service Pack 2</A
-></H1
+NAME="AEN3285">24.5. Windows 2000 Service Pack 2</H1
><P
>
There are several annoyances with Windows 2000 SP2. One of which
@@ -622,49 +488,15 @@ for the profile. This default ACL includes </P
CLASS="COMMAND"
>DOMAIN\user "Full Control"</B
></P
-><DIV
-CLASS="NOTE"
><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>NOTE : This bug does not occur when using winbind to
+create accounts on the Samba host for Domain users.</I
+></SPAN
></P
-><TABLE
-CLASS="NOTE"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->This bug does not occur when using winbind to
-create accounts on the Samba host for Domain users.</P
-></TD
-></TR
-></TABLE
-></DIV
-></DIV
-><DIV
-CLASS="SECT1"
-><H1
-CLASS="SECT1"
-><A
-NAME="AEN4628"
->30.6. Windows NT 3.1</A
-></H1
-><P
->If you have problems communicating across routers with Windows
-NT 3.1 workstations, read <A
-HREF="http://support.microsoft.com/default.aspx?scid=kb;[LN];Q103765"
-TARGET="_top"
->this Microsoft Knowledge Base article</A
->.&#13;</P
></DIV
></DIV
><DIV
@@ -701,7 +533,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
-HREF="swat.html"
+HREF="bugreport.html"
ACCESSKEY="N"
>Next</A
></TD
@@ -725,7 +557,7 @@ ACCESSKEY="U"
WIDTH="33%"
ALIGN="right"
VALIGN="top"
->SWAT - The Samba Web Admininistration Tool</TD
+>Reporting Bugs</TD
></TR
></TABLE
></DIV
diff --git a/docs/htmldocs/p1346.html b/docs/htmldocs/p1346.html
new file mode 100644
index 0000000000..e558561800
--- /dev/null
+++ b/docs/htmldocs/p1346.html
@@ -0,0 +1,917 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<HTML
+><HEAD
+><TITLE
+>Optional configuration</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.77"><LINK
+REL="HOME"
+TITLE="SAMBA Project Documentation"
+HREF="samba-howto-collection.html"><LINK
+REL="PREVIOUS"
+TITLE="Samba as a NT4 domain member"
+HREF="domain-security.html"><LINK
+REL="NEXT"
+TITLE="Integrating MS Windows networks with Samba"
+HREF="integrate-ms-networks.html"></HEAD
+><BODY
+CLASS="PART"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><TABLE
+SUMMARY="Header navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>SAMBA Project Documentation</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="domain-security.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+></TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="integrate-ms-networks.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="PART"
+><A
+NAME="AEN1346"
+></A
+><DIV
+CLASS="TITLEPAGE"
+><H1
+CLASS="TITLE"
+>III. Optional configuration</H1
+><DIV
+CLASS="PARTINTRO"
+><A
+NAME="AEN1348"
+></A
+><H1
+>Introduction</H1
+><P
+>Samba has several features that you might want or might not want to use. The chapters in this
+part each cover one specific feature.</P
+></DIV
+><DIV
+CLASS="TOC"
+><DL
+><DT
+><B
+>Table of Contents</B
+></DT
+><DT
+>10. <A
+HREF="integrate-ms-networks.html"
+>Integrating MS Windows networks with Samba</A
+></DT
+><DD
+><DL
+><DT
+>10.1. <A
+HREF="integrate-ms-networks.html#AEN1362"
+>Agenda</A
+></DT
+><DT
+>10.2. <A
+HREF="integrate-ms-networks.html#AEN1384"
+>Name Resolution in a pure Unix/Linux world</A
+></DT
+><DD
+><DL
+><DT
+>10.2.1. <A
+HREF="integrate-ms-networks.html#AEN1400"
+><TT
+CLASS="FILENAME"
+>/etc/hosts</TT
+></A
+></DT
+><DT
+>10.2.2. <A
+HREF="integrate-ms-networks.html#AEN1416"
+><TT
+CLASS="FILENAME"
+>/etc/resolv.conf</TT
+></A
+></DT
+><DT
+>10.2.3. <A
+HREF="integrate-ms-networks.html#AEN1427"
+><TT
+CLASS="FILENAME"
+>/etc/host.conf</TT
+></A
+></DT
+><DT
+>10.2.4. <A
+HREF="integrate-ms-networks.html#AEN1435"
+><TT
+CLASS="FILENAME"
+>/etc/nsswitch.conf</TT
+></A
+></DT
+></DL
+></DD
+><DT
+>10.3. <A
+HREF="integrate-ms-networks.html#AEN1447"
+>Name resolution as used within MS Windows networking</A
+></DT
+><DD
+><DL
+><DT
+>10.3.1. <A
+HREF="integrate-ms-networks.html#AEN1459"
+>The NetBIOS Name Cache</A
+></DT
+><DT
+>10.3.2. <A
+HREF="integrate-ms-networks.html#AEN1464"
+>The LMHOSTS file</A
+></DT
+><DT
+>10.3.3. <A
+HREF="integrate-ms-networks.html#AEN1472"
+>HOSTS file</A
+></DT
+><DT
+>10.3.4. <A
+HREF="integrate-ms-networks.html#AEN1477"
+>DNS Lookup</A
+></DT
+><DT
+>10.3.5. <A
+HREF="integrate-ms-networks.html#AEN1480"
+>WINS Lookup</A
+></DT
+></DL
+></DD
+><DT
+>10.4. <A
+HREF="integrate-ms-networks.html#AEN1492"
+>How browsing functions and how to deploy stable and
+dependable browsing using Samba</A
+></DT
+><DT
+>10.5. <A
+HREF="integrate-ms-networks.html#AEN1502"
+>MS Windows security options and how to configure
+Samba for seemless integration</A
+></DT
+><DD
+><DL
+><DT
+>10.5.1. <A
+HREF="integrate-ms-networks.html#AEN1530"
+>Use MS Windows NT as an authentication server</A
+></DT
+><DT
+>10.5.2. <A
+HREF="integrate-ms-networks.html#AEN1538"
+>Make Samba a member of an MS Windows NT security domain</A
+></DT
+><DT
+>10.5.3. <A
+HREF="integrate-ms-networks.html#AEN1555"
+>Configure Samba as an authentication server</A
+></DT
+></DL
+></DD
+><DT
+>10.6. <A
+HREF="integrate-ms-networks.html#AEN1572"
+>Conclusions</A
+></DT
+></DL
+></DD
+><DT
+>11. <A
+HREF="unix-permissions.html"
+>UNIX Permission Bits and Windows NT Access Control Lists</A
+></DT
+><DD
+><DL
+><DT
+>11.1. <A
+HREF="unix-permissions.html#AEN1593"
+>Viewing and changing UNIX permissions using the NT
+ security dialogs</A
+></DT
+><DT
+>11.2. <A
+HREF="unix-permissions.html#AEN1602"
+>How to view file security on a Samba share</A
+></DT
+><DT
+>11.3. <A
+HREF="unix-permissions.html#AEN1613"
+>Viewing file ownership</A
+></DT
+><DT
+>11.4. <A
+HREF="unix-permissions.html#AEN1633"
+>Viewing file or directory permissions</A
+></DT
+><DD
+><DL
+><DT
+>11.4.1. <A
+HREF="unix-permissions.html#AEN1648"
+>File Permissions</A
+></DT
+><DT
+>11.4.2. <A
+HREF="unix-permissions.html#AEN1662"
+>Directory Permissions</A
+></DT
+></DL
+></DD
+><DT
+>11.5. <A
+HREF="unix-permissions.html#AEN1669"
+>Modifying file or directory permissions</A
+></DT
+><DT
+>11.6. <A
+HREF="unix-permissions.html#AEN1691"
+>Interaction with the standard Samba create mask
+ parameters</A
+></DT
+><DT
+>11.7. <A
+HREF="unix-permissions.html#AEN1755"
+>Interaction with the standard Samba file attribute
+ mapping</A
+></DT
+></DL
+></DD
+><DT
+>12. <A
+HREF="pam.html"
+>Configuring PAM for distributed but centrally
+managed authentication</A
+></DT
+><DD
+><DL
+><DT
+>12.1. <A
+HREF="pam.html#AEN1776"
+>Samba and PAM</A
+></DT
+><DT
+>12.2. <A
+HREF="pam.html#AEN1820"
+>Distributed Authentication</A
+></DT
+><DT
+>12.3. <A
+HREF="pam.html#AEN1827"
+>PAM Configuration in smb.conf</A
+></DT
+></DL
+></DD
+><DT
+>13. <A
+HREF="msdfs.html"
+>Hosting a Microsoft Distributed File System tree on Samba</A
+></DT
+><DD
+><DL
+><DT
+>13.1. <A
+HREF="msdfs.html#AEN1847"
+>Instructions</A
+></DT
+><DD
+><DL
+><DT
+>13.1.1. <A
+HREF="msdfs.html#AEN1882"
+>Notes</A
+></DT
+></DL
+></DD
+></DL
+></DD
+><DT
+>14. <A
+HREF="printing.html"
+>Printing Support</A
+></DT
+><DD
+><DL
+><DT
+>14.1. <A
+HREF="printing.html#AEN1908"
+>Introduction</A
+></DT
+><DT
+>14.2. <A
+HREF="printing.html#AEN1930"
+>Configuration</A
+></DT
+><DD
+><DL
+><DT
+>14.2.1. <A
+HREF="printing.html#AEN1938"
+>Creating [print$]</A
+></DT
+><DT
+>14.2.2. <A
+HREF="printing.html#AEN1973"
+>Setting Drivers for Existing Printers</A
+></DT
+><DT
+>14.2.3. <A
+HREF="printing.html#AEN1989"
+>Support a large number of printers</A
+></DT
+><DT
+>14.2.4. <A
+HREF="printing.html#AEN2000"
+>Adding New Printers via the Windows NT APW</A
+></DT
+><DT
+>14.2.5. <A
+HREF="printing.html#AEN2030"
+>Samba and Printer Ports</A
+></DT
+></DL
+></DD
+><DT
+>14.3. <A
+HREF="printing.html#AEN2038"
+>The Imprints Toolset</A
+></DT
+><DD
+><DL
+><DT
+>14.3.1. <A
+HREF="printing.html#AEN2042"
+>What is Imprints?</A
+></DT
+><DT
+>14.3.2. <A
+HREF="printing.html#AEN2052"
+>Creating Printer Driver Packages</A
+></DT
+><DT
+>14.3.3. <A
+HREF="printing.html#AEN2055"
+>The Imprints server</A
+></DT
+><DT
+>14.3.4. <A
+HREF="printing.html#AEN2059"
+>The Installation Client</A
+></DT
+></DL
+></DD
+><DT
+>14.4. <A
+HREF="printing.html#AEN2081"
+>Diagnosis</A
+></DT
+><DD
+><DL
+><DT
+>14.4.1. <A
+HREF="printing.html#AEN2083"
+>Introduction</A
+></DT
+><DT
+>14.4.2. <A
+HREF="printing.html#AEN2099"
+>Debugging printer problems</A
+></DT
+><DT
+>14.4.3. <A
+HREF="printing.html#AEN2108"
+>What printers do I have?</A
+></DT
+><DT
+>14.4.4. <A
+HREF="printing.html#AEN2116"
+>Setting up printcap and print servers</A
+></DT
+><DT
+>14.4.5. <A
+HREF="printing.html#AEN2144"
+>Job sent, no output</A
+></DT
+><DT
+>14.4.6. <A
+HREF="printing.html#AEN2155"
+>Job sent, strange output</A
+></DT
+><DT
+>14.4.7. <A
+HREF="printing.html#AEN2167"
+>Raw PostScript printed</A
+></DT
+><DT
+>14.4.8. <A
+HREF="printing.html#AEN2170"
+>Advanced Printing</A
+></DT
+><DT
+>14.4.9. <A
+HREF="printing.html#AEN2173"
+>Real debugging</A
+></DT
+></DL
+></DD
+></DL
+></DD
+><DT
+>15. <A
+HREF="securitylevels.html"
+>Security levels</A
+></DT
+><DD
+><DL
+><DT
+>15.1. <A
+HREF="securitylevels.html#AEN2186"
+>Introduction</A
+></DT
+><DT
+>15.2. <A
+HREF="securitylevels.html#AEN2197"
+>More complete description of security levels</A
+></DT
+></DL
+></DD
+><DT
+>16. <A
+HREF="winbind.html"
+>Unified Logons between Windows NT and UNIX using Winbind</A
+></DT
+><DD
+><DL
+><DT
+>16.1. <A
+HREF="winbind.html#AEN2249"
+>Abstract</A
+></DT
+><DT
+>16.2. <A
+HREF="winbind.html#AEN2253"
+>Introduction</A
+></DT
+><DT
+>16.3. <A
+HREF="winbind.html#AEN2266"
+>What Winbind Provides</A
+></DT
+><DD
+><DL
+><DT
+>16.3.1. <A
+HREF="winbind.html#AEN2273"
+>Target Uses</A
+></DT
+></DL
+></DD
+><DT
+>16.4. <A
+HREF="winbind.html#AEN2277"
+>How Winbind Works</A
+></DT
+><DD
+><DL
+><DT
+>16.4.1. <A
+HREF="winbind.html#AEN2282"
+>Microsoft Remote Procedure Calls</A
+></DT
+><DT
+>16.4.2. <A
+HREF="winbind.html#AEN2286"
+>Name Service Switch</A
+></DT
+><DT
+>16.4.3. <A
+HREF="winbind.html#AEN2302"
+>Pluggable Authentication Modules</A
+></DT
+><DT
+>16.4.4. <A
+HREF="winbind.html#AEN2310"
+>User and Group ID Allocation</A
+></DT
+><DT
+>16.4.5. <A
+HREF="winbind.html#AEN2314"
+>Result Caching</A
+></DT
+></DL
+></DD
+><DT
+>16.5. <A
+HREF="winbind.html#AEN2317"
+>Installation and Configuration</A
+></DT
+><DD
+><DL
+><DT
+>16.5.1. <A
+HREF="winbind.html#AEN2324"
+>Introduction</A
+></DT
+><DT
+>16.5.2. <A
+HREF="winbind.html#AEN2337"
+>Requirements</A
+></DT
+><DT
+>16.5.3. <A
+HREF="winbind.html#AEN2351"
+>Testing Things Out</A
+></DT
+></DL
+></DD
+><DT
+>16.6. <A
+HREF="winbind.html#AEN2566"
+>Limitations</A
+></DT
+><DT
+>16.7. <A
+HREF="winbind.html#AEN2576"
+>Conclusion</A
+></DT
+></DL
+></DD
+><DT
+>17. <A
+HREF="pdb-mysql.html"
+>Passdb MySQL plugin</A
+></DT
+><DD
+><DL
+><DT
+>17.1. <A
+HREF="pdb-mysql.html#AEN2590"
+>Building</A
+></DT
+><DT
+>17.2. <A
+HREF="pdb-mysql.html#AEN2596"
+>Configuring</A
+></DT
+><DT
+>17.3. <A
+HREF="pdb-mysql.html#AEN2611"
+>Using plaintext passwords or encrypted password</A
+></DT
+><DT
+>17.4. <A
+HREF="pdb-mysql.html#AEN2616"
+>Getting non-column data from the table</A
+></DT
+></DL
+></DD
+><DT
+>18. <A
+HREF="pdb-xml.html"
+>Passdb XML plugin</A
+></DT
+><DD
+><DL
+><DT
+>18.1. <A
+HREF="pdb-xml.html#AEN2635"
+>Building</A
+></DT
+><DT
+>18.2. <A
+HREF="pdb-xml.html#AEN2641"
+>Usage</A
+></DT
+></DL
+></DD
+><DT
+>19. <A
+HREF="samba-ldap-howto.html"
+>Storing Samba's User/Machine Account information in an LDAP Directory</A
+></DT
+><DD
+><DL
+><DT
+>19.1. <A
+HREF="samba-ldap-howto.html#AEN2664"
+>Purpose</A
+></DT
+><DT
+>19.2. <A
+HREF="samba-ldap-howto.html#AEN2684"
+>Introduction</A
+></DT
+><DT
+>19.3. <A
+HREF="samba-ldap-howto.html#AEN2713"
+>Supported LDAP Servers</A
+></DT
+><DT
+>19.4. <A
+HREF="samba-ldap-howto.html#AEN2718"
+>Schema and Relationship to the RFC 2307 posixAccount</A
+></DT
+><DT
+>19.5. <A
+HREF="samba-ldap-howto.html#AEN2730"
+>Configuring Samba with LDAP</A
+></DT
+><DD
+><DL
+><DT
+>19.5.1. <A
+HREF="samba-ldap-howto.html#AEN2732"
+>OpenLDAP configuration</A
+></DT
+><DT
+>19.5.2. <A
+HREF="samba-ldap-howto.html#AEN2749"
+>Configuring Samba</A
+></DT
+></DL
+></DD
+><DT
+>19.6. <A
+HREF="samba-ldap-howto.html#AEN2777"
+>Accounts and Groups management</A
+></DT
+><DT
+>19.7. <A
+HREF="samba-ldap-howto.html#AEN2782"
+>Security and sambaAccount</A
+></DT
+><DT
+>19.8. <A
+HREF="samba-ldap-howto.html#AEN2802"
+>LDAP specials attributes for sambaAccounts</A
+></DT
+><DT
+>19.9. <A
+HREF="samba-ldap-howto.html#AEN2872"
+>Example LDIF Entries for a sambaAccount</A
+></DT
+><DT
+>19.10. <A
+HREF="samba-ldap-howto.html#AEN2880"
+>Comments</A
+></DT
+></DL
+></DD
+><DT
+>20. <A
+HREF="cvs-access.html"
+>HOWTO Access Samba source code via CVS</A
+></DT
+><DD
+><DL
+><DT
+>20.1. <A
+HREF="cvs-access.html#AEN2891"
+>Introduction</A
+></DT
+><DT
+>20.2. <A
+HREF="cvs-access.html#AEN2896"
+>CVS Access to samba.org</A
+></DT
+><DD
+><DL
+><DT
+>20.2.1. <A
+HREF="cvs-access.html#AEN2899"
+>Access via CVSweb</A
+></DT
+><DT
+>20.2.2. <A
+HREF="cvs-access.html#AEN2904"
+>Access via cvs</A
+></DT
+></DL
+></DD
+></DL
+></DD
+><DT
+>21. <A
+HREF="groupmapping.html"
+>Group mapping HOWTO</A
+></DT
+><DT
+>22. <A
+HREF="speed.html"
+>Samba performance issues</A
+></DT
+><DD
+><DL
+><DT
+>22.1. <A
+HREF="speed.html#AEN2982"
+>Comparisons</A
+></DT
+><DT
+>22.2. <A
+HREF="speed.html#AEN2988"
+>Oplocks</A
+></DT
+><DD
+><DL
+><DT
+>22.2.1. <A
+HREF="speed.html#AEN2990"
+>Overview</A
+></DT
+><DT
+>22.2.2. <A
+HREF="speed.html#AEN2998"
+>Level2 Oplocks</A
+></DT
+><DT
+>22.2.3. <A
+HREF="speed.html#AEN3004"
+>Old 'fake oplocks' option - deprecated</A
+></DT
+></DL
+></DD
+><DT
+>22.3. <A
+HREF="speed.html#AEN3008"
+>Socket options</A
+></DT
+><DT
+>22.4. <A
+HREF="speed.html#AEN3015"
+>Read size</A
+></DT
+><DT
+>22.5. <A
+HREF="speed.html#AEN3020"
+>Max xmit</A
+></DT
+><DT
+>22.6. <A
+HREF="speed.html#AEN3025"
+>Locking</A
+></DT
+><DT
+>22.7. <A
+HREF="speed.html#AEN3029"
+>Share modes</A
+></DT
+><DT
+>22.8. <A
+HREF="speed.html#AEN3034"
+>Log level</A
+></DT
+><DT
+>22.9. <A
+HREF="speed.html#AEN3037"
+>Wide lines</A
+></DT
+><DT
+>22.10. <A
+HREF="speed.html#AEN3040"
+>Read raw</A
+></DT
+><DT
+>22.11. <A
+HREF="speed.html#AEN3045"
+>Write raw</A
+></DT
+><DT
+>22.12. <A
+HREF="speed.html#AEN3049"
+>Read prediction</A
+></DT
+><DT
+>22.13. <A
+HREF="speed.html#AEN3056"
+>Memory mapping</A
+></DT
+><DT
+>22.14. <A
+HREF="speed.html#AEN3061"
+>Slow Clients</A
+></DT
+><DT
+>22.15. <A
+HREF="speed.html#AEN3065"
+>Slow Logins</A
+></DT
+><DT
+>22.16. <A
+HREF="speed.html#AEN3068"
+>Client tuning</A
+></DT
+><DT
+>22.17. <A
+HREF="speed.html#AEN3100"
+>My Results</A
+></DT
+></DL
+></DD
+></DL
+></DIV
+></DIV
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+SUMMARY="Footer navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="domain-security.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="samba-howto-collection.html"
+ACCESSKEY="H"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="integrate-ms-networks.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>Samba as a NT4 domain member</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+>&nbsp;</TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>Integrating MS Windows networks with Samba</TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+> \ No newline at end of file
diff --git a/docs/htmldocs/p18.html b/docs/htmldocs/p18.html
new file mode 100644
index 0000000000..a8f2a3c53c
--- /dev/null
+++ b/docs/htmldocs/p18.html
@@ -0,0 +1,438 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<HTML
+><HEAD
+><TITLE
+>General installation</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.77"><LINK
+REL="HOME"
+TITLE="SAMBA Project Documentation"
+HREF="samba-howto-collection.html"><LINK
+REL="PREVIOUS"
+TITLE="SAMBA Project Documentation"
+HREF="samba-howto-collection.html"><LINK
+REL="NEXT"
+TITLE="How to Install and Test SAMBA"
+HREF="install.html"></HEAD
+><BODY
+CLASS="PART"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><TABLE
+SUMMARY="Header navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>SAMBA Project Documentation</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="samba-howto-collection.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+></TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="install.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="PART"
+><A
+NAME="AEN18"
+></A
+><DIV
+CLASS="TITLEPAGE"
+><H1
+CLASS="TITLE"
+>I. General installation</H1
+><DIV
+CLASS="PARTINTRO"
+><A
+NAME="AEN20"
+></A
+><H1
+>Introduction</H1
+><P
+>This part contains general info on how to install samba
+and how to configure the parts of samba you will most likely need.
+PLEASE read this.</P
+></DIV
+><DIV
+CLASS="TOC"
+><DL
+><DT
+><B
+>Table of Contents</B
+></DT
+><DT
+>1. <A
+HREF="install.html"
+>How to Install and Test SAMBA</A
+></DT
+><DD
+><DL
+><DT
+>1.1. <A
+HREF="install.html#AEN25"
+>Read the man pages</A
+></DT
+><DT
+>1.2. <A
+HREF="install.html#AEN35"
+>Building the Binaries</A
+></DT
+><DT
+>1.3. <A
+HREF="install.html#AEN63"
+>The all important step</A
+></DT
+><DT
+>1.4. <A
+HREF="install.html#AEN67"
+>Create the smb configuration file.</A
+></DT
+><DT
+>1.5. <A
+HREF="install.html#AEN81"
+>Test your config file with
+ <B
+CLASS="COMMAND"
+>testparm</B
+></A
+></DT
+><DT
+>1.6. <A
+HREF="install.html#AEN89"
+>Starting the smbd and nmbd</A
+></DT
+><DD
+><DL
+><DT
+>1.6.1. <A
+HREF="install.html#AEN99"
+>Starting from inetd.conf</A
+></DT
+><DT
+>1.6.2. <A
+HREF="install.html#AEN128"
+>Alternative: starting it as a daemon</A
+></DT
+></DL
+></DD
+><DT
+>1.7. <A
+HREF="install.html#AEN144"
+>Try listing the shares available on your
+ server</A
+></DT
+><DT
+>1.8. <A
+HREF="install.html#AEN153"
+>Try connecting with the unix client</A
+></DT
+><DT
+>1.9. <A
+HREF="install.html#AEN169"
+>Try connecting from a DOS, WfWg, Win9x, WinNT,
+ Win2k, OS/2, etc... client</A
+></DT
+><DT
+>1.10. <A
+HREF="install.html#AEN183"
+>What If Things Don't Work?</A
+></DT
+><DD
+><DL
+><DT
+>1.10.1. <A
+HREF="install.html#AEN188"
+>Diagnosing Problems</A
+></DT
+><DT
+>1.10.2. <A
+HREF="install.html#AEN192"
+>Scope IDs</A
+></DT
+><DT
+>1.10.3. <A
+HREF="install.html#AEN195"
+>Choosing the Protocol Level</A
+></DT
+><DT
+>1.10.4. <A
+HREF="install.html#AEN204"
+>Printing from UNIX to a Client PC</A
+></DT
+><DT
+>1.10.5. <A
+HREF="install.html#AEN209"
+>Locking</A
+></DT
+><DT
+>1.10.6. <A
+HREF="install.html#AEN218"
+>Mapping Usernames</A
+></DT
+></DL
+></DD
+></DL
+></DD
+><DT
+>2. <A
+HREF="improved-browsing.html"
+>Improved browsing in samba</A
+></DT
+><DD
+><DL
+><DT
+>2.1. <A
+HREF="improved-browsing.html#AEN228"
+>Overview of browsing</A
+></DT
+><DT
+>2.2. <A
+HREF="improved-browsing.html#AEN232"
+>Browsing support in samba</A
+></DT
+><DT
+>2.3. <A
+HREF="improved-browsing.html#AEN241"
+>Problem resolution</A
+></DT
+><DT
+>2.4. <A
+HREF="improved-browsing.html#AEN248"
+>Browsing across subnets</A
+></DT
+><DD
+><DL
+><DT
+>2.4.1. <A
+HREF="improved-browsing.html#AEN253"
+>How does cross subnet browsing work ?</A
+></DT
+></DL
+></DD
+><DT
+>2.5. <A
+HREF="improved-browsing.html#AEN288"
+>Setting up a WINS server</A
+></DT
+><DT
+>2.6. <A
+HREF="improved-browsing.html#AEN307"
+>Setting up Browsing in a WORKGROUP</A
+></DT
+><DT
+>2.7. <A
+HREF="improved-browsing.html#AEN325"
+>Setting up Browsing in a DOMAIN</A
+></DT
+><DT
+>2.8. <A
+HREF="improved-browsing.html#AEN335"
+>Forcing samba to be the master</A
+></DT
+><DT
+>2.9. <A
+HREF="improved-browsing.html#AEN344"
+>Making samba the domain master</A
+></DT
+><DT
+>2.10. <A
+HREF="improved-browsing.html#AEN362"
+>Note about broadcast addresses</A
+></DT
+><DT
+>2.11. <A
+HREF="improved-browsing.html#AEN365"
+>Multiple interfaces</A
+></DT
+></DL
+></DD
+><DT
+>3. <A
+HREF="oplocks.html"
+>Oplocks</A
+></DT
+><DD
+><DL
+><DT
+>3.1. <A
+HREF="oplocks.html#AEN377"
+>What are oplocks?</A
+></DT
+></DL
+></DD
+><DT
+>4. <A
+HREF="browsing-quick.html"
+>Quick Cross Subnet Browsing / Cross Workgroup Browsing guide</A
+></DT
+><DD
+><DL
+><DT
+>4.1. <A
+HREF="browsing-quick.html#AEN392"
+>Discussion</A
+></DT
+><DT
+>4.2. <A
+HREF="browsing-quick.html#AEN400"
+>Use of the "Remote Announce" parameter</A
+></DT
+><DT
+>4.3. <A
+HREF="browsing-quick.html#AEN414"
+>Use of the "Remote Browse Sync" parameter</A
+></DT
+><DT
+>4.4. <A
+HREF="browsing-quick.html#AEN419"
+>Use of WINS</A
+></DT
+><DT
+>4.5. <A
+HREF="browsing-quick.html#AEN430"
+>Do NOT use more than one (1) protocol on MS Windows machines</A
+></DT
+><DT
+>4.6. <A
+HREF="browsing-quick.html#AEN436"
+>Name Resolution Order</A
+></DT
+></DL
+></DD
+><DT
+>5. <A
+HREF="pwencrypt.html"
+>LanMan and NT Password Encryption in Samba</A
+></DT
+><DD
+><DL
+><DT
+>5.1. <A
+HREF="pwencrypt.html#AEN472"
+>Introduction</A
+></DT
+><DT
+>5.2. <A
+HREF="pwencrypt.html#AEN477"
+>Important Notes About Security</A
+></DT
+><DD
+><DL
+><DT
+>5.2.1. <A
+HREF="pwencrypt.html#AEN496"
+>Advantages of SMB Encryption</A
+></DT
+><DT
+>5.2.2. <A
+HREF="pwencrypt.html#AEN503"
+>Advantages of non-encrypted passwords</A
+></DT
+></DL
+></DD
+><DT
+>5.3. <A
+HREF="pwencrypt.html#AEN512"
+>The smbpasswd Command</A
+></DT
+></DL
+></DD
+></DL
+></DIV
+></DIV
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+SUMMARY="Footer navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="samba-howto-collection.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="samba-howto-collection.html"
+ACCESSKEY="H"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="install.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>SAMBA Project Documentation</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+>&nbsp;</TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>How to Install and Test SAMBA</TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+> \ No newline at end of file
diff --git a/docs/htmldocs/p3106.html b/docs/htmldocs/p3106.html
new file mode 100644
index 0000000000..9967d8fb59
--- /dev/null
+++ b/docs/htmldocs/p3106.html
@@ -0,0 +1,391 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<HTML
+><HEAD
+><TITLE
+>Appendixes</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.77"><LINK
+REL="HOME"
+TITLE="SAMBA Project Documentation"
+HREF="samba-howto-collection.html"><LINK
+REL="PREVIOUS"
+TITLE="Samba performance issues"
+HREF="speed.html"><LINK
+REL="NEXT"
+TITLE="Portability"
+HREF="portability.html"></HEAD
+><BODY
+CLASS="PART"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><TABLE
+SUMMARY="Header navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>SAMBA Project Documentation</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="speed.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+></TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="portability.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="PART"
+><A
+NAME="AEN3106"
+></A
+><DIV
+CLASS="TITLEPAGE"
+><H1
+CLASS="TITLE"
+>IV. Appendixes</H1
+><DIV
+CLASS="TOC"
+><DL
+><DT
+><B
+>Table of Contents</B
+></DT
+><DT
+>23. <A
+HREF="portability.html"
+>Portability</A
+></DT
+><DD
+><DL
+><DT
+>23.1. <A
+HREF="portability.html#AEN3115"
+>HPUX</A
+></DT
+><DT
+>23.2. <A
+HREF="portability.html#AEN3121"
+>SCO Unix</A
+></DT
+><DT
+>23.3. <A
+HREF="portability.html#AEN3125"
+>DNIX</A
+></DT
+><DT
+>23.4. <A
+HREF="portability.html#AEN3154"
+>RedHat Linux Rembrandt-II</A
+></DT
+></DL
+></DD
+><DT
+>24. <A
+HREF="other-clients.html"
+>Samba and other CIFS clients</A
+></DT
+><DD
+><DL
+><DT
+>24.1. <A
+HREF="other-clients.html#AEN3175"
+>Macintosh clients?</A
+></DT
+><DT
+>24.2. <A
+HREF="other-clients.html#AEN3184"
+>OS2 Client</A
+></DT
+><DD
+><DL
+><DT
+>24.2.1. <A
+HREF="other-clients.html#AEN3186"
+>How can I configure OS/2 Warp Connect or
+ OS/2 Warp 4 as a client for Samba?</A
+></DT
+><DT
+>24.2.2. <A
+HREF="other-clients.html#AEN3201"
+>How can I configure OS/2 Warp 3 (not Connect),
+ OS/2 1.2, 1.3 or 2.x for Samba?</A
+></DT
+><DT
+>24.2.3. <A
+HREF="other-clients.html#AEN3210"
+>Are there any other issues when OS/2 (any version)
+ is used as a client?</A
+></DT
+><DT
+>24.2.4. <A
+HREF="other-clients.html#AEN3214"
+>How do I get printer driver download working
+ for OS/2 clients?</A
+></DT
+></DL
+></DD
+><DT
+>24.3. <A
+HREF="other-clients.html#AEN3224"
+>Windows for Workgroups</A
+></DT
+><DD
+><DL
+><DT
+>24.3.1. <A
+HREF="other-clients.html#AEN3226"
+>Use latest TCP/IP stack from Microsoft</A
+></DT
+><DT
+>24.3.2. <A
+HREF="other-clients.html#AEN3231"
+>Delete .pwl files after password change</A
+></DT
+><DT
+>24.3.3. <A
+HREF="other-clients.html#AEN3236"
+>Configure WfW password handling</A
+></DT
+><DT
+>24.3.4. <A
+HREF="other-clients.html#AEN3240"
+>Case handling of passwords</A
+></DT
+></DL
+></DD
+><DT
+>24.4. <A
+HREF="other-clients.html#AEN3245"
+>Windows '95/'98</A
+></DT
+><DT
+>24.5. <A
+HREF="other-clients.html#AEN3261"
+>Windows 2000 Service Pack 2</A
+></DT
+></DL
+></DD
+><DT
+>25. <A
+HREF="bugreport.html"
+>Reporting Bugs</A
+></DT
+><DD
+><DL
+><DT
+>25.1. <A
+HREF="bugreport.html#AEN3285"
+>Introduction</A
+></DT
+><DT
+>25.2. <A
+HREF="bugreport.html#AEN3295"
+>General info</A
+></DT
+><DT
+>25.3. <A
+HREF="bugreport.html#AEN3301"
+>Debug levels</A
+></DT
+><DT
+>25.4. <A
+HREF="bugreport.html#AEN3318"
+>Internal errors</A
+></DT
+><DT
+>25.5. <A
+HREF="bugreport.html#AEN3328"
+>Attaching to a running process</A
+></DT
+><DT
+>25.6. <A
+HREF="bugreport.html#AEN3331"
+>Patches</A
+></DT
+></DL
+></DD
+><DT
+>26. <A
+HREF="diagnosis.html"
+>Diagnosing your samba server</A
+></DT
+><DD
+><DL
+><DT
+>26.1. <A
+HREF="diagnosis.html#AEN3354"
+>Introduction</A
+></DT
+><DT
+>26.2. <A
+HREF="diagnosis.html#AEN3359"
+>Assumptions</A
+></DT
+><DT
+>26.3. <A
+HREF="diagnosis.html#AEN3369"
+>Tests</A
+></DT
+><DD
+><DL
+><DT
+>26.3.1. <A
+HREF="diagnosis.html#AEN3371"
+>Test 1</A
+></DT
+><DT
+>26.3.2. <A
+HREF="diagnosis.html#AEN3377"
+>Test 2</A
+></DT
+><DT
+>26.3.3. <A
+HREF="diagnosis.html#AEN3383"
+>Test 3</A
+></DT
+><DT
+>26.3.4. <A
+HREF="diagnosis.html#AEN3398"
+>Test 4</A
+></DT
+><DT
+>26.3.5. <A
+HREF="diagnosis.html#AEN3403"
+>Test 5</A
+></DT
+><DT
+>26.3.6. <A
+HREF="diagnosis.html#AEN3409"
+>Test 6</A
+></DT
+><DT
+>26.3.7. <A
+HREF="diagnosis.html#AEN3417"
+>Test 7</A
+></DT
+><DT
+>26.3.8. <A
+HREF="diagnosis.html#AEN3443"
+>Test 8</A
+></DT
+><DT
+>26.3.9. <A
+HREF="diagnosis.html#AEN3460"
+>Test 9</A
+></DT
+><DT
+>26.3.10. <A
+HREF="diagnosis.html#AEN3468"
+>Test 10</A
+></DT
+><DT
+>26.3.11. <A
+HREF="diagnosis.html#AEN3474"
+>Test 11</A
+></DT
+></DL
+></DD
+><DT
+>26.4. <A
+HREF="diagnosis.html#AEN3479"
+>Still having troubles?</A
+></DT
+></DL
+></DD
+></DL
+></DIV
+></DIV
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+SUMMARY="Footer navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="speed.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="samba-howto-collection.html"
+ACCESSKEY="H"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="portability.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>Samba performance issues</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+>&nbsp;</TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>Portability</TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+> \ No newline at end of file
diff --git a/docs/htmldocs/p544.html b/docs/htmldocs/p544.html
new file mode 100644
index 0000000000..502d978b5f
--- /dev/null
+++ b/docs/htmldocs/p544.html
@@ -0,0 +1,388 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<HTML
+><HEAD
+><TITLE
+>Type of installation</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.77"><LINK
+REL="HOME"
+TITLE="SAMBA Project Documentation"
+HREF="samba-howto-collection.html"><LINK
+REL="PREVIOUS"
+TITLE="LanMan and NT Password Encryption in Samba"
+HREF="pwencrypt.html"><LINK
+REL="NEXT"
+TITLE="How to Configure Samba as a NT4 Primary Domain Controller"
+HREF="samba-pdc.html"></HEAD
+><BODY
+CLASS="PART"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><TABLE
+SUMMARY="Header navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>SAMBA Project Documentation</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="pwencrypt.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+></TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="samba-pdc.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="PART"
+><A
+NAME="AEN544"
+></A
+><DIV
+CLASS="TITLEPAGE"
+><H1
+CLASS="TITLE"
+>II. Type of installation</H1
+><DIV
+CLASS="PARTINTRO"
+><A
+NAME="AEN546"
+></A
+><H1
+>Introduction</H1
+><P
+>This part contains information on using samba in a (NT 4 or ADS) domain.
+If you wish to run samba as a domain member or DC, read the appropriate chapter in
+this part.</P
+></DIV
+><DIV
+CLASS="TOC"
+><DL
+><DT
+><B
+>Table of Contents</B
+></DT
+><DT
+>6. <A
+HREF="samba-pdc.html"
+>How to Configure Samba as a NT4 Primary Domain Controller</A
+></DT
+><DD
+><DL
+><DT
+>6.1. <A
+HREF="samba-pdc.html#AEN566"
+>Prerequisite Reading</A
+></DT
+><DT
+>6.2. <A
+HREF="samba-pdc.html#AEN572"
+>Background</A
+></DT
+><DT
+>6.3. <A
+HREF="samba-pdc.html#AEN611"
+>Configuring the Samba Domain Controller</A
+></DT
+><DT
+>6.4. <A
+HREF="samba-pdc.html#AEN654"
+>Creating Machine Trust Accounts and Joining Clients to the
+Domain</A
+></DT
+><DD
+><DL
+><DT
+>6.4.1. <A
+HREF="samba-pdc.html#AEN673"
+>Manual Creation of Machine Trust Accounts</A
+></DT
+><DT
+>6.4.2. <A
+HREF="samba-pdc.html#AEN714"
+>"On-the-Fly" Creation of Machine Trust Accounts</A
+></DT
+><DT
+>6.4.3. <A
+HREF="samba-pdc.html#AEN723"
+>Joining the Client to the Domain</A
+></DT
+></DL
+></DD
+><DT
+>6.5. <A
+HREF="samba-pdc.html#AEN738"
+>Common Problems and Errors</A
+></DT
+><DT
+>6.6. <A
+HREF="samba-pdc.html#AEN786"
+>System Policies and Profiles</A
+></DT
+><DT
+>6.7. <A
+HREF="samba-pdc.html#AEN830"
+>What other help can I get?</A
+></DT
+><DT
+>6.8. <A
+HREF="samba-pdc.html#AEN944"
+>Domain Control for Windows 9x/ME</A
+></DT
+><DD
+><DL
+><DT
+>6.8.1. <A
+HREF="samba-pdc.html#AEN970"
+>Configuration Instructions: Network Logons</A
+></DT
+><DT
+>6.8.2. <A
+HREF="samba-pdc.html#AEN989"
+>Configuration Instructions: Setting up Roaming User Profiles</A
+></DT
+></DL
+></DD
+><DT
+>6.9. <A
+HREF="samba-pdc.html#AEN1082"
+>DOMAIN_CONTROL.txt : Windows NT Domain Control &#38; Samba</A
+></DT
+></DL
+></DD
+><DT
+>7. <A
+HREF="samba-bdc.html"
+>How to Act as a Backup Domain Controller in a Purely Samba Controlled Domain</A
+></DT
+><DD
+><DL
+><DT
+>7.1. <A
+HREF="samba-bdc.html#AEN1118"
+>Prerequisite Reading</A
+></DT
+><DT
+>7.2. <A
+HREF="samba-bdc.html#AEN1122"
+>Background</A
+></DT
+><DT
+>7.3. <A
+HREF="samba-bdc.html#AEN1130"
+>What qualifies a Domain Controller on the network?</A
+></DT
+><DD
+><DL
+><DT
+>7.3.1. <A
+HREF="samba-bdc.html#AEN1133"
+>How does a Workstation find its domain controller?</A
+></DT
+><DT
+>7.3.2. <A
+HREF="samba-bdc.html#AEN1136"
+>When is the PDC needed?</A
+></DT
+></DL
+></DD
+><DT
+>7.4. <A
+HREF="samba-bdc.html#AEN1139"
+>Can Samba be a Backup Domain Controller?</A
+></DT
+><DT
+>7.5. <A
+HREF="samba-bdc.html#AEN1143"
+>How do I set up a Samba BDC?</A
+></DT
+><DD
+><DL
+><DT
+>7.5.1. <A
+HREF="samba-bdc.html#AEN1160"
+>How do I replicate the smbpasswd file?</A
+></DT
+></DL
+></DD
+></DL
+></DD
+><DT
+>8. <A
+HREF="ads.html"
+>Samba as a ADS domain member</A
+></DT
+><DD
+><DL
+><DT
+>8.1. <A
+HREF="ads.html#AEN1178"
+>Installing the required packages for Debian</A
+></DT
+><DT
+>8.2. <A
+HREF="ads.html#AEN1184"
+>Installing the required packages for RedHat</A
+></DT
+><DT
+>8.3. <A
+HREF="ads.html#AEN1193"
+>Compile Samba</A
+></DT
+><DT
+>8.4. <A
+HREF="ads.html#AEN1205"
+>Setup your /etc/krb5.conf</A
+></DT
+><DT
+>8.5. <A
+HREF="ads.html#AEN1215"
+>Create the computer account</A
+></DT
+><DD
+><DL
+><DT
+>8.5.1. <A
+HREF="ads.html#AEN1219"
+>Possible errors</A
+></DT
+></DL
+></DD
+><DT
+>8.6. <A
+HREF="ads.html#AEN1231"
+>Test your server setup</A
+></DT
+><DT
+>8.7. <A
+HREF="ads.html#AEN1236"
+>Testing with smbclient</A
+></DT
+><DT
+>8.8. <A
+HREF="ads.html#AEN1239"
+>Notes</A
+></DT
+></DL
+></DD
+><DT
+>9. <A
+HREF="domain-security.html"
+>Samba as a NT4 domain member</A
+></DT
+><DD
+><DL
+><DT
+>9.1. <A
+HREF="domain-security.html#AEN1261"
+>Joining an NT Domain with Samba 2.2</A
+></DT
+><DT
+>9.2. <A
+HREF="domain-security.html#AEN1325"
+>Samba and Windows 2000 Domains</A
+></DT
+><DT
+>9.3. <A
+HREF="domain-security.html#AEN1330"
+>Why is this better than security = server?</A
+></DT
+></DL
+></DD
+></DL
+></DIV
+></DIV
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+SUMMARY="Footer navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="pwencrypt.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="samba-howto-collection.html"
+ACCESSKEY="H"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="samba-pdc.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>LanMan and NT Password Encryption in Samba</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+>&nbsp;</TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>How to Configure Samba as a NT4 Primary Domain Controller</TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+> \ No newline at end of file
diff --git a/docs/htmldocs/pam.html b/docs/htmldocs/pam.html
index f8624e94c5..ba2bf6c922 100644
--- a/docs/htmldocs/pam.html
+++ b/docs/htmldocs/pam.html
@@ -1,280 +1,425 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter20.PAM Configuration for Centrally Managed Authentication</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"><link rel="home" href="index.html" title="SAMBA Project Documentation"><link rel="up" href="optional.html" title="PartIII.Advanced Configuration"><link rel="previous" href="InterdomainTrusts.html" title="Chapter19.Interdomain Trust Relationships"><link rel="next" href="VFS.html" title="Chapter21.Stackable VFS modules"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter20.PAM Configuration for Centrally Managed Authentication</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="InterdomainTrusts.html">Prev</a></td><th width="60%" align="center">PartIII.Advanced Configuration</th><td width="20%" align="right"><a accesskey="n" href="VFS.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="pam"></a>Chapter20.PAM Configuration for Centrally Managed Authentication</h2></div><div><div class="author"><h3 class="author">John H. Terpstra</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt>&lt;<a href="mailto:jht@samba.org">jht@samba.org</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate"> (Jun 21 2001) </p></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="pam.html#id2897853">Samba and PAM</a></dt><dd><dl><dt><a href="pam.html#id2898634">PAM Configuration in smb.conf</a></dt><dt><a href="pam.html#id2898691">Password Synchronisation using pam_smbpass.so</a></dt></dl></dd><dt><a href="pam.html#id2898943">Distributed Authentication</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2897853"></a>Samba and PAM</h2></div></div><p>
-A number of Unix systems (eg: Sun Solaris), as well as the
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<HTML
+><HEAD
+><TITLE
+>Configuring PAM for distributed but centrally
+managed authentication</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
+REL="HOME"
+TITLE="SAMBA Project Documentation"
+HREF="samba-howto-collection.html"><LINK
+REL="UP"
+TITLE="Optional configuration"
+HREF="optional.html"><LINK
+REL="PREVIOUS"
+TITLE="UNIX Permission Bits and Windows NT Access Control Lists"
+HREF="unix-permissions.html"><LINK
+REL="NEXT"
+TITLE="Hosting a Microsoft Distributed File System tree on Samba"
+HREF="msdfs.html"></HEAD
+><BODY
+CLASS="CHAPTER"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><TABLE
+SUMMARY="Header navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>SAMBA Project Documentation</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="unix-permissions.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+></TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="msdfs.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="CHAPTER"
+><H1
+><A
+NAME="PAM">Chapter 12. Configuring PAM for distributed but centrally
+managed authentication</H1
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN1788">12.1. Samba and PAM</H1
+><P
+>A number of Unix systems (eg: Sun Solaris), as well as the
xxxxBSD family and Linux, now utilize the Pluggable Authentication
Modules (PAM) facility to provide all authentication,
authorization and resource control services. Prior to the
introduction of PAM, a decision to use an alternative to
-the system password database (<tt>/etc/passwd</tt>)
+the system password database (<TT
+CLASS="FILENAME"
+>/etc/passwd</TT
+>)
would require the provision of alternatives for all programs that provide
security services. Such a choice would involve provision of
-alternatives to such programs as: <b>login</b>,
-<b>passwd</b>, <b>chown</b>, etc.
-</p><p>
-PAM provides a mechanism that disconnects these security programs
+alternatives to such programs as: <B
+CLASS="COMMAND"
+>login</B
+>,
+<B
+CLASS="COMMAND"
+>passwd</B
+>, <B
+CLASS="COMMAND"
+>chown</B
+>, etc.</P
+><P
+>PAM provides a mechanism that disconnects these security programs
from the underlying authentication/authorization infrastructure.
-PAM is configured either through one file <tt>/etc/pam.conf</tt> (Solaris),
-or by editing individual files that are located in <tt>/etc/pam.d</tt>.
-</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
- If the PAM authentication module (loadable link library file) is located in the
- default location then it is not necessary to specify the path. In the case of
- Linux, the default location is <tt>/lib/security</tt>. If the module
- is located outside the default then the path must be specified as:
-
- </p><pre class="programlisting">
- auth required /other_path/pam_strange_module.so
- </pre><p>
- </p></div><p>
-The following is an example <tt>/etc/pam.d/login</tt> configuration file.
+PAM is configured either through one file <TT
+CLASS="FILENAME"
+>/etc/pam.conf</TT
+> (Solaris),
+or by editing individual files that are located in <TT
+CLASS="FILENAME"
+>/etc/pam.d</TT
+>.</P
+><P
+>The following is an example <TT
+CLASS="FILENAME"
+>/etc/pam.d/login</TT
+> configuration file.
This example had all options been uncommented is probably not usable
as it stacks many conditions before allowing successful completion
of the login process. Essentially all conditions can be disabled
-by commenting them out except the calls to <tt>pam_pwdb.so</tt>.
-</p><pre class="programlisting">
- #%PAM-1.0
- # The PAM configuration file for the `login' service
- #
- auth required pam_securetty.so
- auth required pam_nologin.so
- # auth required pam_dialup.so
- # auth optional pam_mail.so
- auth required pam_pwdb.so shadow md5
- # account requisite pam_time.so
- account required pam_pwdb.so
- session required pam_pwdb.so
- # session optional pam_lastlog.so
- # password required pam_cracklib.so retry=3
- password required pam_pwdb.so shadow md5
-</pre><p>
-PAM allows use of replacable modules. Those available on a
-sample system include:
-</p><p><tt>$</tt><b><tt>/bin/ls /lib/security</tt></b>
-</p><pre class="programlisting">
- pam_access.so pam_ftp.so pam_limits.so
- pam_ncp_auth.so pam_rhosts_auth.so pam_stress.so
- pam_cracklib.so pam_group.so pam_listfile.so
- pam_nologin.so pam_rootok.so pam_tally.so
- pam_deny.so pam_issue.so pam_mail.so
- pam_permit.so pam_securetty.so pam_time.so
- pam_dialup.so pam_lastlog.so pam_mkhomedir.so
- pam_pwdb.so pam_shells.so pam_unix.so
- pam_env.so pam_ldap.so pam_motd.so
- pam_radius.so pam_smbpass.so pam_unix_acct.so
- pam_wheel.so pam_unix_auth.so pam_unix_passwd.so
- pam_userdb.so pam_warn.so pam_unix_session.so
-</pre><p>
-The following example for the login program replaces the use of
-the <tt>pam_pwdb.so</tt> module which uses the system
-password database (<tt>/etc/passwd</tt>,
-<tt>/etc/shadow</tt>, <tt>/etc/group</tt>) with
-the module <tt>pam_smbpass.so</tt> which uses the Samba
+by commenting them out except the calls to <TT
+CLASS="FILENAME"
+>pam_pwdb.so</TT
+>.</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>#%PAM-1.0
+# The PAM configuration file for the `login' service
+#
+auth required pam_securetty.so
+auth required pam_nologin.so
+# auth required pam_dialup.so
+# auth optional pam_mail.so
+auth required pam_pwdb.so shadow md5
+# account requisite pam_time.so
+account required pam_pwdb.so
+session required pam_pwdb.so
+# session optional pam_lastlog.so
+# password required pam_cracklib.so retry=3
+password required pam_pwdb.so shadow md5</PRE
+></P
+><P
+>PAM allows use of replacable modules. Those available on a
+sample system include:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>$ /bin/ls /lib/security
+pam_access.so pam_ftp.so pam_limits.so
+pam_ncp_auth.so pam_rhosts_auth.so pam_stress.so
+pam_cracklib.so pam_group.so pam_listfile.so
+pam_nologin.so pam_rootok.so pam_tally.so
+pam_deny.so pam_issue.so pam_mail.so
+pam_permit.so pam_securetty.so pam_time.so
+pam_dialup.so pam_lastlog.so pam_mkhomedir.so
+pam_pwdb.so pam_shells.so pam_unix.so
+pam_env.so pam_ldap.so pam_motd.so
+pam_radius.so pam_smbpass.so pam_unix_acct.so
+pam_wheel.so pam_unix_auth.so pam_unix_passwd.so
+pam_userdb.so pam_warn.so pam_unix_session.so</PRE
+></P
+><P
+>The following example for the login program replaces the use of
+the <TT
+CLASS="FILENAME"
+>pam_pwdb.so</TT
+> module which uses the system
+password database (<TT
+CLASS="FILENAME"
+>/etc/passwd</TT
+>,
+<TT
+CLASS="FILENAME"
+>/etc/shadow</TT
+>, <TT
+CLASS="FILENAME"
+>/etc/group</TT
+>) with
+the module <TT
+CLASS="FILENAME"
+>pam_smbpass.so</TT
+> which uses the Samba
database which contains the Microsoft MD4 encrypted password
hashes. This database is stored in either
-<tt>/usr/local/samba/private/smbpasswd</tt>,
-<tt>/etc/samba/smbpasswd</tt>, or in
-<tt>/etc/samba.d/smbpasswd</tt>, depending on the
+<TT
+CLASS="FILENAME"
+>/usr/local/samba/private/smbpasswd</TT
+>,
+<TT
+CLASS="FILENAME"
+>/etc/samba/smbpasswd</TT
+>, or in
+<TT
+CLASS="FILENAME"
+>/etc/samba.d/smbpasswd</TT
+>, depending on the
Samba implementation for your Unix/Linux system. The
-<tt>pam_smbpass.so</tt> module is provided by
+<TT
+CLASS="FILENAME"
+>pam_smbpass.so</TT
+> module is provided by
Samba version 2.2.1 or later. It can be compiled by specifying the
-<b>--with-pam_smbpass</b> options when running Samba's
-<tt>configure</tt> script. For more information
-on the <tt>pam_smbpass</tt> module, see the documentation
-in the <tt>source/pam_smbpass</tt> directory of the Samba
-source distribution.
-</p><pre class="programlisting">
- #%PAM-1.0
- # The PAM configuration file for the `login' service
- #
- auth required pam_smbpass.so nodelay
- account required pam_smbpass.so nodelay
- session required pam_smbpass.so nodelay
- password required pam_smbpass.so nodelay
-</pre><p>
-The following is the PAM configuration file for a particular
-Linux system. The default condition uses <tt>pam_pwdb.so</tt>.
-</p><pre class="programlisting">
- #%PAM-1.0
- # The PAM configuration file for the `samba' service
- #
- auth required pam_pwdb.so nullok nodelay shadow audit
- account required pam_pwdb.so audit nodelay
- session required pam_pwdb.so nodelay
- password required pam_pwdb.so shadow md5
-</pre><p>
-In the following example the decision has been made to use the
+<B
+CLASS="COMMAND"
+>--with-pam_smbpass</B
+> options when running Samba's
+<TT
+CLASS="FILENAME"
+>configure</TT
+> script. For more information
+on the <TT
+CLASS="FILENAME"
+>pam_smbpass</TT
+> module, see the documentation
+in the <TT
+CLASS="FILENAME"
+>source/pam_smbpass</TT
+> directory of the Samba
+source distribution.</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>#%PAM-1.0
+# The PAM configuration file for the `login' service
+#
+auth required pam_smbpass.so nodelay
+account required pam_smbpass.so nodelay
+session required pam_smbpass.so nodelay
+password required pam_smbpass.so nodelay</PRE
+></P
+><P
+>The following is the PAM configuration file for a particular
+Linux system. The default condition uses <TT
+CLASS="FILENAME"
+>pam_pwdb.so</TT
+>.</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>#%PAM-1.0
+# The PAM configuration file for the `samba' service
+#
+auth required /lib/security/pam_pwdb.so nullok nodelay shadow audit
+account required /lib/security/pam_pwdb.so audit nodelay
+session required /lib/security/pam_pwdb.so nodelay
+password required /lib/security/pam_pwdb.so shadow md5</PRE
+></P
+><P
+>In the following example the decision has been made to use the
smbpasswd database even for basic samba authentication. Such a
decision could also be made for the passwd program and would
thus allow the smbpasswd passwords to be changed using the passwd
-program.
-</p><pre class="programlisting">
- #%PAM-1.0
- # The PAM configuration file for the `samba' service
- #
- auth required pam_smbpass.so nodelay
- account required pam_pwdb.so audit nodelay
- session required pam_pwdb.so nodelay
- password required pam_smbpass.so nodelay smbconf=/etc/samba.d/smb.conf
-</pre><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>PAM allows stacking of authentication mechanisms. It is
+program.</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>#%PAM-1.0
+# The PAM configuration file for the `samba' service
+#
+auth required /lib/security/pam_smbpass.so nodelay
+account required /lib/security/pam_pwdb.so audit nodelay
+session required /lib/security/pam_pwdb.so nodelay
+password required /lib/security/pam_smbpass.so nodelay smbconf=/etc/samba.d/smb.conf</PRE
+></P
+><P
+>Note: PAM allows stacking of authentication mechanisms. It is
also possible to pass information obtained within one PAM module through
to the next module in the PAM stack. Please refer to the documentation for
your particular system implementation for details regarding the specific
capabilities of PAM in this environment. Some Linux implmentations also
-provide the <tt>pam_stack.so</tt> module that allows all
+provide the <TT
+CLASS="FILENAME"
+>pam_stack.so</TT
+> module that allows all
authentication to be configured in a single central file. The
-<tt>pam_stack.so</tt> method has some very devoted followers
+<TT
+CLASS="FILENAME"
+>pam_stack.so</TT
+> method has some very devoted followers
on the basis that it allows for easier administration. As with all issues in
life though, every decision makes trade-offs, so you may want examine the
-PAM documentation for further helpful information.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2898634"></a>PAM Configuration in smb.conf</h3></div></div><p>
-There is an option in smb.conf called <a href="smb.conf.5.html#OBEYPAMRESTRICTIONS" target="_top">obey pam restrictions</a>.
-The following is from the on-line help for this option in SWAT;
-</p><p>
-When Samba is configured to enable PAM support (i.e.
-<tt>--with-pam</tt>), this parameter will
+PAM documentation for further helpful information.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN1832">12.2. Distributed Authentication</H1
+><P
+>The astute administrator will realize from this that the
+combination of <TT
+CLASS="FILENAME"
+>pam_smbpass.so</TT
+>,
+<B
+CLASS="COMMAND"
+>winbindd</B
+>, and <B
+CLASS="COMMAND"
+>rsync</B
+> (see
+<A
+HREF="http://rsync.samba.org/"
+TARGET="_top"
+>http://rsync.samba.org/</A
+>)
+will allow the establishment of a centrally managed, distributed
+user/password database that can also be used by all
+PAM (eg: Linux) aware programs and applications. This arrangement
+can have particularly potent advantages compared with the
+use of Microsoft Active Directory Service (ADS) in so far as
+reduction of wide area network authentication traffic.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN1839">12.3. PAM Configuration in smb.conf</H1
+><P
+>There is an option in smb.conf called <A
+HREF="smb.conf.5.html#OBEYPAMRESTRICTIONS"
+TARGET="_top"
+>obey pam restrictions</A
+>.
+The following is from the on-line help for this option in SWAT;</P
+><P
+>When Samba 2.2 is configure to enable PAM support (i.e.
+<TT
+CLASS="CONSTANT"
+>--with-pam</TT
+>), this parameter will
control whether or not Samba should obey PAM's account
and session management directives. The default behavior
is to use PAM for clear text authentication only and to
ignore any account or session management. Note that Samba always
ignores PAM for authentication in the case of
-<a href="smb.conf.5.html#ENCRYPTPASSWORDS" target="_top">encrypt passwords = yes</a>.
+<A
+HREF="smb.conf.5.html#ENCRYPTPASSWORDS"
+TARGET="_top"
+>encrypt passwords = yes</A
+>.
The reason is that PAM modules cannot support the challenge/response
authentication mechanism needed in the presence of SMB
-password encryption.
-</p><p>Default: <b>obey pam restrictions = no</b></p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2898691"></a>Password Synchronisation using pam_smbpass.so</h3></div></div><p>
-pam_smbpass is a PAM module which can be used on conforming systems to
-keep the smbpasswd (Samba password) database in sync with the unix
-password file. PAM (Pluggable Authentication Modules) is an API supported
-under some Unices, such as Solaris, HPUX and Linux, that provides a
-generic interface to authentication mechanisms.
-</p><p>
-For more information on PAM, see http://ftp.kernel.org/pub/linux/libs/pam/
-</p><p>
-This module authenticates a local smbpasswd user database. If you require
-support for authenticating against a remote SMB server, or if you're
-concerned about the presence of suid root binaries on your system, it is
-recommended that you use pam_winbind instead.
-</p><pre class="programlisting">
-Options recognized by this module are as follows:
-
- debug - log more debugging info
- audit - like debug, but also logs unknown usernames
- use_first_pass - don't prompt the user for passwords;
- take them from PAM_ items instead
- try_first_pass - try to get the password from a previous
- PAM module, fall back to prompting the user
- use_authtok - like try_first_pass, but *fail* if the new
- PAM_AUTHTOK has not been previously set.
- (intended for stacking password modules only)
- not_set_pass - don't make passwords used by this module
- available to other modules.
- nodelay - don't insert ~1 second delays on authentication
- failure.
- nullok - null passwords are allowed.
- nonull - null passwords are not allowed. Used to
- override the Samba configuration.
- migrate - only meaningful in an &quot;auth&quot; context;
- used to update smbpasswd file with a
- password used for successful authentication.
- smbconf=&lt; file &gt; - specify an alternate path to the smb.conf
- file.
-</pre><pre class="programlisting">
-Thanks go to the following people:
-
- * Andrew Morgan &lt; morgan@transmeta.com &gt;, for providing the Linux-PAM
- framework, without which none of this would have happened
-
- * Christian Gafton &lt; gafton@redhat.com &gt; and Andrew Morgan again, for the
- pam_pwdb module upon which pam_smbpass was originally based
-
- * Luke Leighton &lt; lkcl@switchboard.net &gt; for being receptive to the idea,
- and for the occasional good-natured complaint about the project's status
- that keep me working on it :)
-
- * and of course, all the other members of the Samba team
- &lt;http://www.samba.org/samba/team.html&gt;, for creating a great product
- and for giving this project a purpose
-
- ---------------------
- Stephen Langasek &lt; vorlon@netexpress.net &gt;
-</pre><p>
-The following are examples of the use of pam_smbpass.so in the format of Linux
-<tt>/etc/pam.d/</tt> files structure. Those wishing to implement this
-tool on other platforms will need to adapt this appropriately.
-</p><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2898803"></a>Password Synchonisation Configuration</h4></div></div><p>
-A sample PAM configuration that shows the use of pam_smbpass to make
-sure private/smbpasswd is kept in sync when /etc/passwd (/etc/shadow)
-is changed. Useful when an expired password might be changed by an
-application (such as ssh).
-</p><pre class="programlisting">
- #%PAM-1.0
- # password-sync
- #
- auth requisite pam_nologin.so
- auth required pam_unix.so
- account required pam_unix.so
- password requisite pam_cracklib.so retry=3
- password requisite pam_unix.so shadow md5 use_authtok try_first_pass
- password required pam_smbpass.so nullok use_authtok try_first_pass
- session required pam_unix.so
-</pre></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2898838"></a>Password Migration Configuration</h4></div></div><p>
-A sample PAM configuration that shows the use of pam_smbpass to migrate
-from plaintext to encrypted passwords for Samba. Unlike other methods,
-this can be used for users who have never connected to Samba shares:
-password migration takes place when users ftp in, login using ssh, pop
-their mail, etc.
-</p><pre class="programlisting">
- #%PAM-1.0
- # password-migration
- #
- auth requisite pam_nologin.so
- # pam_smbpass is called IFF pam_unix succeeds.
- auth requisite pam_unix.so
- auth optional pam_smbpass.so migrate
- account required pam_unix.so
- password requisite pam_cracklib.so retry=3
- password requisite pam_unix.so shadow md5 use_authtok try_first_pass
- password optional pam_smbpass.so nullok use_authtok try_first_pass
- session required pam_unix.so
-</pre></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2898875"></a>Mature Password Configuration</h4></div></div><p>
-A sample PAM configuration for a 'mature' smbpasswd installation.
-private/smbpasswd is fully populated, and we consider it an error if
-the smbpasswd doesn't exist or doesn't match the Unix password.
-</p><pre class="programlisting">
- #%PAM-1.0
- # password-mature
- #
- auth requisite pam_nologin.so
- auth required pam_unix.so
- account required pam_unix.so
- password requisite pam_cracklib.so retry=3
- password requisite pam_unix.so shadow md5 use_authtok try_first_pass
- password required pam_smbpass.so use_authtok use_first_pass
- session required pam_unix.so
-</pre></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2898908"></a>Kerberos Password Integration Configuration</h4></div></div><p>
-A sample PAM configuration that shows pam_smbpass used together with
-pam_krb5. This could be useful on a Samba PDC that is also a member of
-a Kerberos realm.
-</p><pre class="programlisting">
- #%PAM-1.0
- # kdc-pdc
- #
- auth requisite pam_nologin.so
- auth requisite pam_krb5.so
- auth optional pam_smbpass.so migrate
- account required pam_krb5.so
- password requisite pam_cracklib.so retry=3
- password optional pam_smbpass.so nullok use_authtok try_first_pass
- password required pam_krb5.so use_authtok try_first_pass
- session required pam_krb5.so
-</pre></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2898943"></a>Distributed Authentication</h2></div></div><p>
-The astute administrator will realize from this that the
-combination of <tt>pam_smbpass.so</tt>,
-<b>winbindd</b>, and a distributed
-passdb backend, such as ldap, will allow the establishment of a
-centrally managed, distributed
-user/password database that can also be used by all
-PAM (eg: Linux) aware programs and applications. This arrangement
-can have particularly potent advantages compared with the
-use of Microsoft Active Directory Service (ADS) in so far as
-reduction of wide area network authentication traffic.
-</p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="InterdomainTrusts.html">Prev</a></td><td width="20%" align="center"><a accesskey="u" href="optional.html">Up</a></td><td width="40%" align="right"><a accesskey="n" href="VFS.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter19.Interdomain Trust Relationships</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">Chapter21.Stackable VFS modules</td></tr></table></div></body></html>
+password encryption. </P
+><P
+>Default: <B
+CLASS="COMMAND"
+>obey pam restrictions = no</B
+></P
+></DIV
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+SUMMARY="Footer navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="unix-permissions.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="samba-howto-collection.html"
+ACCESSKEY="H"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="msdfs.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>UNIX Permission Bits and Windows NT Access Control Lists</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="optional.html"
+ACCESSKEY="U"
+>Up</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>Hosting a Microsoft Distributed File System tree on Samba</TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+> \ No newline at end of file
diff --git a/docs/htmldocs/pdb-mysql.html b/docs/htmldocs/pdb-mysql.html
new file mode 100644
index 0000000000..abca946f6f
--- /dev/null
+++ b/docs/htmldocs/pdb-mysql.html
@@ -0,0 +1,288 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<HTML
+><HEAD
+><TITLE
+>Passdb MySQL plugin</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
+REL="HOME"
+TITLE="SAMBA Project Documentation"
+HREF="samba-howto-collection.html"><LINK
+REL="UP"
+TITLE="Optional configuration"
+HREF="optional.html"><LINK
+REL="PREVIOUS"
+TITLE="Unified Logons between Windows NT and UNIX using Winbind"
+HREF="winbind.html"><LINK
+REL="NEXT"
+TITLE="Passdb XML plugin"
+HREF="pdb-xml.html"></HEAD
+><BODY
+CLASS="CHAPTER"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><TABLE
+SUMMARY="Header navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>SAMBA Project Documentation</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="winbind.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+></TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="pdb-xml.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="CHAPTER"
+><H1
+><A
+NAME="PDB-MYSQL">Chapter 16. Passdb MySQL plugin</H1
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN2566">16.1. Building</H1
+><P
+>To build the plugin, run <B
+CLASS="COMMAND"
+>make bin/pdb_mysql.so</B
+>
+in the <TT
+CLASS="FILENAME"
+>source/</TT
+> directory of samba distribution. </P
+><P
+>Next, copy pdb_mysql.so to any location you want. I
+strongly recommend installing it in $PREFIX/lib or /usr/lib/samba/</P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN2572">16.2. Configuring</H1
+><P
+>This plugin lacks some good documentation, but here is some short info:</P
+><P
+>Add a the following to the <B
+CLASS="COMMAND"
+>passdb backend</B
+> variable in your <TT
+CLASS="FILENAME"
+>smb.conf</TT
+>:
+<PRE
+CLASS="PROGRAMLISTING"
+>passdb backend = [other-plugins] plugin:/location/to/pdb_mysql.so:identifier [other-plugins]</PRE
+></P
+><P
+>The identifier can be any string you like, as long as it doesn't collide with
+the identifiers of other plugins or other instances of pdb_mysql. If you
+specify multiple pdb_mysql.so entries in 'passdb backend', you also need to
+use different identifiers!</P
+><P
+>Additional options can be given thru the smb.conf file in the [global] section.</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>identifier:mysql host - host name, defaults to 'localhost'
+identifier:mysql password
+identifier:mysql user - defaults to 'samba'
+identifier:mysql database - defaults to 'samba'
+identifier:mysql port - defaults to 3306
+identifier:table - Name of the table containing users</PRE
+></P
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>WARNING: since the password for the mysql user is stored in the
+smb.conf file, you should make the the smb.conf file
+readable only to the user that runs samba. This is considered a security
+bug and will be fixed soon.</I
+></SPAN
+></P
+><P
+>Names of the columns in this table(I've added column types those columns should have first):</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>identifier:logon time column - int(9)
+identifier:logoff time column - int(9)
+identifier:kickoff time column - int(9)
+identifier:pass last set time column - int(9)
+identifier:pass can change time column - int(9)
+identifier:pass must change time column - int(9)
+identifier:username column - varchar(255) - unix username
+identifier:domain column - varchar(255) - NT domain user is part of
+identifier:nt username column - varchar(255) - NT username
+identifier:fullname column - varchar(255) - Full name of user
+identifier:home dir column - varchar(255) - Unix homedir path
+identifier:dir drive column - varchar(2) - Directory drive path (eg: 'H:')
+identifier:logon script column - varchar(255) - Batch file to run on client side when logging on
+identifier:profile path column - varchar(255) - Path of profile
+identifier:acct desc column - varchar(255) - Some ASCII NT user data
+identifier:workstations column - varchar(255) - Workstations user can logon to (or NULL for all)
+identifier:unknown string column - varchar(255) - unknown string
+identifier:munged dial column - varchar(255) - ?
+identifier:uid column - int(9) - Unix user ID (uid)
+identifier:gid column - int(9) - Unix user group (gid)
+identifier:user sid column - varchar(255) - NT user SID
+identifier:group sid column - varchar(255) - NT group ID
+identifier:lanman pass column - varchar(255) - encrypted lanman password
+identifier:nt pass column - varchar(255) - encrypted nt passwd
+identifier:plain pass column - varchar(255) - plaintext password
+identifier:acct control column - int(9) - nt user data
+identifier:unknown 3 column - int(9) - unknown
+identifier:logon divs column - int(9) - ?
+identifier:hours len column - int(9) - ?
+identifier:unknown 5 column - int(9) - unknown
+identifier:unknown 6 column - int(9) - unknown</PRE
+></P
+><P
+>Eventually, you can put a colon (:) after the name of each column, which
+should specify the column to update when updating the table. You can also
+specify nothing behind the colon - then the data from the field will not be
+updated. </P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN2589">16.3. Using plaintext passwords or encrypted password</H1
+><P
+>I strongly discourage the use of plaintext passwords, however, you can use them:</P
+><P
+>If you would like to use plaintext passwords, set 'identifier:lanman pass column' and 'identifier:nt pass column' to 'NULL' (without the quotes) and 'identifier:plain pass column' to the name of the column containing the plaintext passwords. </P
+><P
+>If you use encrypted passwords, set the 'identifier:plain pass column' to 'NULL' (without the quotes). This is the default.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN2594">16.4. Getting non-column data from the table</H1
+><P
+>It is possible to have not all data in the database and making some 'constant'.</P
+><P
+>For example, you can set 'identifier:fullname column' to :
+<B
+CLASS="COMMAND"
+>CONCAT(First_name,' ',Sur_name)</B
+></P
+><P
+>Or, set 'identifier:workstations column' to :
+<B
+CLASS="COMMAND"
+>NULL</B
+></P
+><P
+>See the MySQL documentation for more language constructs.</P
+></DIV
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+SUMMARY="Footer navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="winbind.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="samba-howto-collection.html"
+ACCESSKEY="H"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="pdb-xml.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>Unified Logons between Windows NT and UNIX using Winbind</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="optional.html"
+ACCESSKEY="U"
+>Up</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>Passdb XML plugin</TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+> \ No newline at end of file
diff --git a/docs/htmldocs/pdb-xml.html b/docs/htmldocs/pdb-xml.html
new file mode 100644
index 0000000000..4d300d7be0
--- /dev/null
+++ b/docs/htmldocs/pdb-xml.html
@@ -0,0 +1,184 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<HTML
+><HEAD
+><TITLE
+>Passdb XML plugin</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
+REL="HOME"
+TITLE="SAMBA Project Documentation"
+HREF="samba-howto-collection.html"><LINK
+REL="UP"
+TITLE="Optional configuration"
+HREF="optional.html"><LINK
+REL="PREVIOUS"
+TITLE="Passdb MySQL plugin"
+HREF="pdb-mysql.html"><LINK
+REL="NEXT"
+TITLE="Stackable VFS modules"
+HREF="vfs.html"></HEAD
+><BODY
+CLASS="CHAPTER"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><TABLE
+SUMMARY="Header navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>SAMBA Project Documentation</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="pdb-mysql.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+></TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="vfs.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="CHAPTER"
+><H1
+><A
+NAME="PDB-XML">Chapter 17. Passdb XML plugin</H1
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN2613">17.1. Building</H1
+><P
+>This module requires libxml2 to be installed.</P
+><P
+>To build pdb_xml, run: <B
+CLASS="COMMAND"
+>make bin/pdb_xml.so</B
+> in
+the directory <TT
+CLASS="FILENAME"
+>source/</TT
+>. </P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN2619">17.2. Usage</H1
+><P
+>The usage of pdb_xml is pretty straightforward. To export data, use:
+
+<B
+CLASS="COMMAND"
+>pdbedit -e plugin:/usr/lib/samba/pdb_xml.so:filename</B
+>
+
+(where filename is the name of the file to put the data in)</P
+><P
+>To import data, use:
+<B
+CLASS="COMMAND"
+>pdbedit -i plugin:/usr/lib/samba/pdb_xml.so:filename -e current-pdb</B
+>
+
+Where filename is the name to read the data from and current-pdb to put it in.</P
+></DIV
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+SUMMARY="Footer navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="pdb-mysql.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="samba-howto-collection.html"
+ACCESSKEY="H"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="vfs.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>Passdb MySQL plugin</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="optional.html"
+ACCESSKEY="U"
+>Up</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>Stackable VFS modules</TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+> \ No newline at end of file
diff --git a/docs/htmldocs/pdbedit.8.html b/docs/htmldocs/pdbedit.8.html
index f239011639..7b85e2bb80 100644
--- a/docs/htmldocs/pdbedit.8.html
+++ b/docs/htmldocs/pdbedit.8.html
@@ -1,131 +1,606 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>pdbedit</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="pdbedit.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>pdbedit &#8212; manage the SAM database</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><tt>pdbedit</tt> [-l] [-v] [-w] [-u username] [-f fullname] [-h homedir] [-D drive] [-S script] [-p profile] [-a] [-m] [-x] [-i passdb-backend] [-e passdb-backend] [-g] [-b passdb-backend] [-g] [-d debuglevel] [-s configfile] [-P account-policy] [-C value]</p></div></div><div class="refsect1" lang="en"><h2>DESCRIPTION</h2><p>This tool is part of the <a href="Samba.7.html">Samba(7)</a> suite.</p><p>The pdbedit program is used to manage the users accounts
- stored in the sam database and can only be run by root.</p><p>The pdbedit tool uses the passdb modular interface and is
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
+<HTML
+><HEAD
+><TITLE
+>pdbedit</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"></HEAD
+><BODY
+CLASS="REFENTRY"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><H1
+><A
+NAME="PDBEDIT">pdbedit</H1
+><DIV
+CLASS="REFNAMEDIV"
+><A
+NAME="AEN5"
+></A
+><H2
+>Name</H2
+>pdbedit&nbsp;--&nbsp;manage the SAM database</DIV
+><DIV
+CLASS="REFSYNOPSISDIV"
+><A
+NAME="AEN8"><H2
+>Synopsis</H2
+><P
+><B
+CLASS="COMMAND"
+>pdbedit</B
+> [-l] [-v] [-w] [-u username] [-f fullname] [-h homedir] [-D drive] [-S script] [-p profile] [-a] [-m] [-x] [-i passdb-backend] [-e passdb-backend] [-g] [-b passdb-backend] [-d debuglevel] [-s configfile] [-P account-policy] [-V value]</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN31"
+></A
+><H2
+>DESCRIPTION</H2
+><P
+>This tool is part of the <A
+HREF="samba.7.html"
+TARGET="_top"
+> Samba</A
+> suite.</P
+><P
+>The pdbedit program is used to manage the users accounts
+ stored in the sam database and can only be run by root.</P
+><P
+>The pdbedit tool uses the passdb modular interface and is
independent from the kind of users database used (currently there
are smbpasswd, ldap, nis+ and tdb based and more can be added
- without changing the tool).</p><p>There are five main ways to use pdbedit: adding a user account,
+ without changing the tool).</P
+><P
+>There are five main ways to use pdbedit: adding a user account,
removing a user account, modifing a user account, listing user
- accounts, importing users accounts.</p></div><div class="refsect1" lang="en"><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-l</span></dt><dd><p>This option lists all the user accounts
+ accounts, importing users accounts.</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN38"
+></A
+><H2
+>OPTIONS</H2
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>-l</DT
+><DD
+><P
+>This option lists all the user accounts
present in the users database.
This option prints a list of user/uid pairs separated by
- the ':' character.</p><p>Example: <b>pdbedit -l</b></p><pre class="screen">
-sorce:500:Simo Sorce
-samba:45:Test User
-</pre></dd><dt><span class="term">-v</span></dt><dd><p>This option enables the verbose listing format.
+ the ':' character.</P
+><P
+>Example: <B
+CLASS="COMMAND"
+>pdbedit -l</B
+></P
+><P
+><TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="90%"
+><TR
+><TD
+><PRE
+CLASS="PROGRAMLISTING"
+> sorce:500:Simo Sorce
+ samba:45:Test User
+ </PRE
+></TD
+></TR
+></TABLE
+></P
+></DD
+><DT
+>-v</DT
+><DD
+><P
+>This option enables the verbose listing format.
It causes pdbedit to list the users in the database, printing
- out the account fields in a descriptive format.</p><p>Example: <b>pdbedit -l -v</b></p><pre class="screen">
----------------
-username: sorce
-user ID/Group: 500/500
-user RID/GRID: 2000/2001
-Full Name: Simo Sorce
-Home Directory: \\BERSERKER\sorce
-HomeDir Drive: H:
-Logon Script: \\BERSERKER\netlogon\sorce.bat
-Profile Path: \\BERSERKER\profile
----------------
-username: samba
-user ID/Group: 45/45
-user RID/GRID: 1090/1091
-Full Name: Test User
-Home Directory: \\BERSERKER\samba
-HomeDir Drive:
-Logon Script:
-Profile Path: \\BERSERKER\profile
-</pre></dd><dt><span class="term">-w</span></dt><dd><p>This option sets the &quot;smbpasswd&quot; listing format.
+ out the account fields in a descriptive format.</P
+><P
+>Example: <B
+CLASS="COMMAND"
+>pdbedit -l -v</B
+></P
+><P
+><TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="90%"
+><TR
+><TD
+><PRE
+CLASS="PROGRAMLISTING"
+> ---------------
+ username: sorce
+ user ID/Group: 500/500
+ user RID/GRID: 2000/2001
+ Full Name: Simo Sorce
+ Home Directory: \\BERSERKER\sorce
+ HomeDir Drive: H:
+ Logon Script: \\BERSERKER\netlogon\sorce.bat
+ Profile Path: \\BERSERKER\profile
+ ---------------
+ username: samba
+ user ID/Group: 45/45
+ user RID/GRID: 1090/1091
+ Full Name: Test User
+ Home Directory: \\BERSERKER\samba
+ HomeDir Drive:
+ Logon Script:
+ Profile Path: \\BERSERKER\profile
+ </PRE
+></TD
+></TR
+></TABLE
+></P
+></DD
+><DT
+>-w</DT
+><DD
+><P
+>This option sets the "smbpasswd" listing format.
It will make pdbedit list the users in the database, printing
out the account fields in a format compatible with the
- <tt>smbpasswd</tt> file format. (see the
- <a href="smbpasswd.5.html">smbpasswd(5)</a> for details)</p><p>Example: <b>pdbedit -l -w</b></p><pre class="screen">
-sorce:500:508818B733CE64BEAAD3B435B51404EE:D2A2418EFC466A8A0F6B1DBB5C3DB80C:[UX ]:LCT-00000000:
-samba:45:0F2B255F7B67A7A9AAD3B435B51404EE:BC281CE3F53B6A5146629CD4751D3490:[UX ]:LCT-3BFA1E8D:
-</pre></dd><dt><span class="term">-u username</span></dt><dd><p>This option specifies the username to be
+ <TT
+CLASS="FILENAME"
+>smbpasswd</TT
+> file format. (see the <A
+HREF="smbpasswd.5.html"
+TARGET="_top"
+><TT
+CLASS="FILENAME"
+>smbpasswd(5)</TT
+></A
+> for details)</P
+><P
+>Example: <B
+CLASS="COMMAND"
+>pdbedit -l -w</B
+></P
+><P
+><TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="90%"
+><TR
+><TD
+><PRE
+CLASS="PROGRAMLISTING"
+> sorce:500:508818B733CE64BEAAD3B435B51404EE:D2A2418EFC466A8A0F6B1DBB5C3DB80C:[UX ]:LCT-00000000:
+ samba:45:0F2B255F7B67A7A9AAD3B435B51404EE:BC281CE3F53B6A5146629CD4751D3490:[UX ]:LCT-3BFA1E8D:
+ </PRE
+></TD
+></TR
+></TABLE
+></P
+></DD
+><DT
+>-u username</DT
+><DD
+><P
+>This option specifies the username to be
used for the operation requested (listing, adding, removing).
- It is <span class="emphasis"><em>required</em></span> in add, remove and modify
- operations and <span class="emphasis"><em>optional</em></span> in list
- operations.</p></dd><dt><span class="term">-f fullname</span></dt><dd><p>This option can be used while adding or
+ It is <I
+CLASS="EMPHASIS"
+>required</I
+> in add, remove and modify
+ operations and <I
+CLASS="EMPHASIS"
+>optional</I
+> in list
+ operations.</P
+></DD
+><DT
+>-f fullname</DT
+><DD
+><P
+>This option can be used while adding or
modifing a user account. It will specify the user's full
- name. </p><p>Example: <b>-f &quot;Simo Sorce&quot;</b></p></dd><dt><span class="term">-h homedir</span></dt><dd><p>This option can be used while adding or
+ name. </P
+><P
+>Example: <B
+CLASS="COMMAND"
+>-f "Simo Sorce"</B
+></P
+></DD
+><DT
+>-h homedir</DT
+><DD
+><P
+>This option can be used while adding or
modifing a user account. It will specify the user's home
- directory network path.</p><p>Example: <b>-h &quot;\\\\BERSERKER\\sorce&quot;</b>
- </p></dd><dt><span class="term">-D drive</span></dt><dd><p>This option can be used while adding or
+ directory network path.</P
+><P
+>Example: <B
+CLASS="COMMAND"
+>-h "\\\\BERSERKER\\sorce"</B
+>
+ </P
+></DD
+><DT
+>-D drive</DT
+><DD
+><P
+>This option can be used while adding or
modifing a user account. It will specify the windows drive
- letter to be used to map the home directory.</p><p>Example: <b>-d &quot;H:&quot;</b>
- </p></dd><dt><span class="term">-S script</span></dt><dd><p>This option can be used while adding or
+ letter to be used to map the home directory.</P
+><P
+>Example: <B
+CLASS="COMMAND"
+>-d "H:"</B
+>
+ </P
+></DD
+><DT
+>-S script</DT
+><DD
+><P
+>This option can be used while adding or
modifing a user account. It will specify the user's logon
- script path.</p><p>Example: <b>-s &quot;\\\\BERSERKER\\netlogon\\sorce.bat&quot;</b>
- </p></dd><dt><span class="term">-p profile</span></dt><dd><p>This option can be used while adding or
+ script path.</P
+><P
+>Example: <B
+CLASS="COMMAND"
+>-s "\\\\BERSERKER\\netlogon\\sorce.bat"</B
+>
+ </P
+></DD
+><DT
+>-p profile</DT
+><DD
+><P
+>This option can be used while adding or
modifing a user account. It will specify the user's profile
- directory.</p><p>Example: <b>-p &quot;\\\\BERSERKER\\netlogon&quot;</b>
- </p></dd><dt><span class="term">-a</span></dt><dd><p>This option is used to add a user into the
+ directory.</P
+><P
+>Example: <B
+CLASS="COMMAND"
+>-p "\\\\BERSERKER\\netlogon"</B
+>
+ </P
+></DD
+><DT
+>-a</DT
+><DD
+><P
+>This option is used to add a user into the
database. This command needs a user name specified with
the -u switch. When adding a new user, pdbedit will also
- ask for the password to be used.</p><p>Example: <b>pdbedit -a -u sorce</b>
-</p><pre class="programlisting">new password:
-retype new password
-</pre><p>
-</p></dd><dt><span class="term">-m</span></dt><dd><p>This option may only be used in conjunction
- with the <i><tt>-a</tt></i> option. It will make
+ ask for the password to be used.</P
+><P
+>Example: <B
+CLASS="COMMAND"
+>pdbedit -a -u sorce</B
+>
+ <TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="90%"
+><TR
+><TD
+><PRE
+CLASS="PROGRAMLISTING"
+>new password:
+ retype new password</PRE
+></TD
+></TR
+></TABLE
+>
+ </P
+></DD
+><DT
+>-m</DT
+><DD
+><P
+>This option may only be used in conjunction
+ with the <TT
+CLASS="PARAMETER"
+><I
+>-a</I
+></TT
+> option. It will make
pdbedit to add a machine trust account instead of a user
- account (-u username will provide the machine name).</p><p>Example: <b>pdbedit -a -m -u w2k-wks</b>
- </p></dd><dt><span class="term">-x</span></dt><dd><p>This option causes pdbedit to delete an account
+ account (-u username will provide the machine name).</P
+><P
+>Example: <B
+CLASS="COMMAND"
+>pdbedit -a -m -u w2k-wks</B
+>
+ </P
+></DD
+><DT
+>-x</DT
+><DD
+><P
+>This option causes pdbedit to delete an account
from the database. It needs a username specified with the
- -u switch.</p><p>Example: <b>pdbedit -x -u bob</b></p></dd><dt><span class="term">-i passdb-backend</span></dt><dd><p>Use a different passdb backend to retrieve users
+ -u switch.</P
+><P
+>Example: <B
+CLASS="COMMAND"
+>pdbedit -x -u bob</B
+></P
+></DD
+><DT
+>-i passdb-backend</DT
+><DD
+><P
+>Use a different passdb backend to retrieve users
than the one specified in smb.conf. Can be used to import data into
- your local user database.</p><p>This option will ease migration from one passdb backend to
- another.</p><p>Example: <b>pdbedit -i smbpasswd:/etc/smbpasswd.old
- </b></p></dd><dt><span class="term">-e passdb-backend</span></dt><dd><p>Exports all currently available users to the
- specified password database backend.</p><p>This option will ease migration from one passdb backend to
- another and will ease backing up.</p><p>Example: <b>pdbedit -e smbpasswd:/root/samba-users.backup</b></p></dd><dt><span class="term">-g</span></dt><dd><p>If you specify <i><tt>-g</tt></i>,
- then <i><tt>-i in-backend -e out-backend</tt></i>
- applies to the group mapping instead of the user database.</p><p>This option will ease migration from one passdb backend to
- another and will ease backing up.</p></dd><dt><span class="term">-g</span></dt><dd><p>If you specify <i><tt>-g</tt></i>,
- then <i><tt>-i in-backend -e out-backend</tt></i>
- applies to the group mapping instead of the user database.</p><p>This option will ease migration from one passdb backend to
- another and will ease backing up.</p></dd><dt><span class="term">-b passdb-backend</span></dt><dd><p>Use a different default passdb backend. </p><p>Example: <b>pdbedit -b xml:/root/pdb-backup.xml -l</b></p></dd><dt><span class="term">-P account-policy</span></dt><dd><p>Display an account policy</p><p>Valid policies are: minimum password age, reset count minutes, disconnect time,
+ your local user database.</P
+><P
+>This option will ease migration from one passdb backend to
+ another.</P
+><P
+>Example: <B
+CLASS="COMMAND"
+>pdbedit -i smbpasswd:/etc/smbpasswd.old
+ </B
+></P
+></DD
+><DT
+>-e passdb-backend</DT
+><DD
+><P
+>Exports all currently available users to the
+ specified password database backend.</P
+><P
+>This option will ease migration from one passdb backend to
+ another and will ease backing up.</P
+><P
+>Example: <B
+CLASS="COMMAND"
+>pdbedit -e smbpasswd:/root/samba-users.backup</B
+></P
+></DD
+><DT
+>-g</DT
+><DD
+><P
+>If you specify <TT
+CLASS="PARAMETER"
+><I
+>-g</I
+></TT
+>,
+ then <TT
+CLASS="PARAMETER"
+><I
+>-i in-backend -e out-backend</I
+></TT
+>
+ applies to the group mapping instead of the user database.
+ </P
+><P
+>This option will ease migration from one passdb backend to
+ another and will ease backing up.</P
+></DD
+><DT
+>-b passdb-backend</DT
+><DD
+><P
+>Use a different default passdb backend. </P
+><P
+>Example: <B
+CLASS="COMMAND"
+>pdbedit -b xml:/root/pdb-backup.xml -l</B
+></P
+></DD
+><DT
+>-P account-policy</DT
+><DD
+><P
+>Display an account policy</P
+><P
+>Valid policies are: minimum password age, reset count minutes, disconnect time,
user must logon to change password, password history, lockout duration, min password length,
- maximum password age and bad lockout attempt.</p><p>Example: <b>pdbedit -P &quot;bad lockout attempt&quot;</b></p><pre class="programlisting">
-account policy value for bad lockout attempt is 0
-</pre></dd><dt><span class="term">-C account-policy-value</span></dt><dd><p>Sets an account policy to a specified value.
+ maximum password age and bad lockout attempt.</P
+><P
+>Example: <B
+CLASS="COMMAND"
+>pdbedit -P "bad lockout attempt"</B
+></P
+><P
+><TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="90%"
+><TR
+><TD
+><PRE
+CLASS="PROGRAMLISTING"
+> account policy value for bad lockout attempt is 0
+ </PRE
+></TD
+></TR
+></TABLE
+></P
+></DD
+><DT
+>-V account-policy-value</DT
+><DD
+><P
+>Sets an account policy to a specified value.
This option may only be used in conjunction
- with the <i><tt>-P</tt></i> option.
- </p><p>Example: <b>pdbedit -P &quot;bad lockout attempt&quot; -C 3</b></p><pre class="programlisting">
-account policy value for bad lockout attempt was 0
-account policy value for bad lockout attempt is now 3
-</pre></dd><dt><span class="term">-h|--help</span></dt><dd><p>Print a summary of command line options.
-</p></dd><dt><span class="term">-V</span></dt><dd><p>Prints the version number for
-<b>smbd</b>.</p></dd><dt><span class="term">-s &lt;configuration file&gt;</span></dt><dd><p>The file specified contains the
-configuration details required by the server. The
-information in this file includes server-specific
-information such as what printcap file to use, as well
-as descriptions of all the services that the server is
-to provide. See <a href="smb.conf.5.html" target="_top"><tt>
-smb.conf(5)</tt></a> for more information.
-The default configuration file name is determined at
-compile time.</p></dd><dt><span class="term">-d|--debug=debuglevel</span></dt><dd><p><i><tt>debuglevel</tt></i> is an integer
+ with the <TT
+CLASS="PARAMETER"
+><I
+>-P</I
+></TT
+> option.
+ </P
+><P
+>Example: <B
+CLASS="COMMAND"
+>pdbedit -P "bad lockout attempt" -V 3</B
+></P
+><P
+><TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="90%"
+><TR
+><TD
+><PRE
+CLASS="PROGRAMLISTING"
+> account policy value for bad lockout attempt was 0
+ account policy value for bad lockout attempt is now 3
+ </PRE
+></TD
+></TR
+></TABLE
+></P
+></DD
+><DT
+>-d|--debug=debuglevel</DT
+><DD
+><P
+><TT
+CLASS="REPLACEABLE"
+><I
+>debuglevel</I
+></TT
+> is an integer
from 0 to 10. The default value if this parameter is
-not specified is zero.</p><p>The higher this value, the more detail will be
+not specified is zero.</P
+><P
+>The higher this value, the more detail will be
logged to the log files about the activities of the
server. At level 0, only critical errors and serious
warnings will be logged. Level 1 is a reasonable level for
day to day running - it generates a small amount of
-information about operations carried out.</p><p>Levels above 1 will generate considerable
+information about operations carried out.</P
+><P
+>Levels above 1 will generate considerable
amounts of log data, and should only be used when
investigating a problem. Levels above 3 are designed for
use only by developers and generate HUGE amounts of log
-data, most of which is extremely cryptic.</p><p>Note that specifying this parameter here will
-override the <a href="smb.conf.5.html#loglevel" target="_top">log
-level</a> parameter in the <a href="smb.conf.5.html" target="_top">
-<tt>smb.conf(5)</tt></a> file.</p></dd><dt><span class="term">-l|--logfile=logbasename</span></dt><dd><p>File name for log/debug files. The extension
-<tt>&quot;.client&quot;</tt> will be appended. The log file is
-never removed by the client.
-</p></dd></dl></div></div><div class="refsect1" lang="en"><h2>NOTES</h2><p>This command may be used only by root.</p></div><div class="refsect1" lang="en"><h2>VERSION</h2><p>This man page is correct for version 2.2 of
- the Samba suite.</p></div><div class="refsect1" lang="en"><h2>SEE ALSO</h2><p><a href="smbpasswd.5.html">smbpasswd(5)</a>, <a href="samba.7.html">samba(7)</a></p></div><div class="refsect1" lang="en"><h2>AUTHOR</h2><p>The original Samba software and related utilities
+data, most of which is extremely cryptic.</P
+><P
+>Note that specifying this parameter here will
+override the <A
+HREF="smb.conf.5.html#loglevel"
+TARGET="_top"
+>log
+level</A
+> parameter in the <A
+HREF="smb.conf.5.html"
+TARGET="_top"
+><TT
+CLASS="FILENAME"
+>smb.conf(5)</TT
+></A
+> file.</P
+></DD
+><DT
+>-h|--help</DT
+><DD
+><P
+>Print a summary of command line options.</P
+></DD
+><DT
+>-s &#60;configuration file&#62;</DT
+><DD
+><P
+>The file specified contains the
+configuration details required by the server. The
+information in this file includes server-specific
+information such as what printcap file to use, as well
+as descriptions of all the services that the server is
+to provide. See <A
+HREF="smb.conf.5.html"
+TARGET="_top"
+><TT
+CLASS="FILENAME"
+>smb.conf(5)</TT
+></A
+> for more information.
+The default configuration file name is determined at
+compile time.</P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN190"
+></A
+><H2
+>NOTES</H2
+><P
+>This command may be used only by root.</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN193"
+></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="AEN196"
+></A
+><H2
+>SEE ALSO</H2
+><P
+><A
+HREF="smbpasswd.8.html"
+TARGET="_top"
+>smbpasswd(8)</A
+>,
+ <A
+HREF="samba.7.html"
+TARGET="_top"
+>samba(7)</A
+>
+ </P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN201"
+></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.
+ to the way the Linux kernel is developed.</P
+><P
+>The original Samba man pages were written by Karl Auer.
The man page sources were converted to YODL format (another
- excellent piece of Open Source software, available at <a href="ftp://ftp.icce.rug.nl/pub/unix/" target="_top">
- ftp://ftp.icce.rug.nl/pub/unix/</a>) and updated for the Samba 2.0
+ excellent piece of Open Source software, available at
+ <A
+HREF="ftp://ftp.icce.rug.nl/pub/unix/"
+TARGET="_top"
+> ftp://ftp.icce.rug.nl/pub/unix/</A
+>) and updated for the Samba 2.0
release by Jeremy Allison. The conversion to DocBook for
- Samba 2.2 was done by Gerald Carter. The conversion to DocBook
- XML 4.2 for Samba 3.0 was done by Alexander Bokovoy.</p></div></div></body></html>
+ Samba 2.2 was done by Gerald Carter</P
+></DIV
+></BODY
+></HTML
+> \ No newline at end of file
diff --git a/docs/htmldocs/policymgmt.html b/docs/htmldocs/policymgmt.html
deleted file mode 100644
index 5d0c9b19f9..0000000000
--- a/docs/htmldocs/policymgmt.html
+++ /dev/null
@@ -1,758 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<HTML
-><HEAD
-><TITLE
->System and Account Policies</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
-REL="HOME"
-TITLE="SAMBA Project Documentation"
-HREF="samba-howto-collection.html"><LINK
-REL="UP"
-TITLE="Advanced Configuration"
-HREF="optional.html"><LINK
-REL="PREVIOUS"
-TITLE="Advanced Network Manangement"
-HREF="advancednetworkmanagement.html"><LINK
-REL="NEXT"
-TITLE="Desktop Profile Management"
-HREF="profilemgmt.html"></HEAD
-><BODY
-CLASS="CHAPTER"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->SAMBA Project Documentation</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="advancednetworkmanagement.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
-></TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="profilemgmt.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="CHAPTER"
-><H1
-><A
-NAME="POLICYMGMT"
-></A
->Chapter 17. System and Account Policies</H1
-><DIV
-CLASS="TOC"
-><DL
-><DT
-><B
->Table of Contents</B
-></DT
-><DT
->17.1. <A
-HREF="policymgmt.html#AEN2958"
->Creating and Managing System Policies</A
-></DT
-><DD
-><DL
-><DT
->17.1.1. <A
-HREF="policymgmt.html#AEN2972"
->Windows 9x/Me Policies</A
-></DT
-><DT
->17.1.2. <A
-HREF="policymgmt.html#AEN2984"
->Windows NT4 Style Policy Files</A
-></DT
-><DT
->17.1.3. <A
-HREF="policymgmt.html#AEN3002"
->MS Windows 200x / XP Professional Policies</A
-></DT
-></DL
-></DD
-><DT
->17.2. <A
-HREF="policymgmt.html#AEN3030"
->Managing Account/User Policies</A
-></DT
-><DD
-><DL
-><DT
->17.2.1. <A
-HREF="policymgmt.html#AEN3045"
->With Windows NT4/200x</A
-></DT
-><DT
->17.2.2. <A
-HREF="policymgmt.html#AEN3048"
->With a Samba PDC</A
-></DT
-></DL
-></DD
-><DT
->17.3. <A
-HREF="policymgmt.html#AEN3052"
->System Startup and Logon Processing Overview</A
-></DT
-></DL
-></DIV
-><DIV
-CLASS="SECT1"
-><H1
-CLASS="SECT1"
-><A
-NAME="AEN2958"
->17.1. Creating and Managing System Policies</A
-></H1
-><P
->Under MS Windows platforms, particularly those following the release of MS Windows
-NT4 and MS Windows 95) it is possible to create a type of file that would be placed
-in the NETLOGON share of a domain controller. As the client logs onto the network
-this file is read and the contents initiate changes to the registry of the client
-machine. This file allows changes to be made to those parts of the registry that
-affect users, groups of users, or machines.</P
-><P
->For MS Windows 9x/Me this file must be called <TT
-CLASS="FILENAME"
->Config.POL</TT
-> and may
-be generated using a tool called <TT
-CLASS="FILENAME"
->poledit.exe</TT
->, better known as the
-Policy Editor. The policy editor was provided on the Windows 98 installation CD, but
-dissappeared again with the introduction of MS Windows Me (Millenium Edition). From
-comments from MS Windows network administrators it would appear that this tool became
-a part of the MS Windows Me Resource Kit.</P
-><P
->MS Windows NT4 Server products include the <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->System Policy Editor</I
-></SPAN
->
-under the <TT
-CLASS="FILENAME"
->Start -&#62; Programs -&#62; Administrative Tools</TT
-> menu item.
-For MS Windows NT4 and later clients this file must be called <TT
-CLASS="FILENAME"
->NTConfig.POL</TT
->.</P
-><P
->New with the introduction of MS Windows 2000 was the Microsoft Management Console
-or MMC. This tool is the new wave in the ever changing landscape of Microsoft
-methods for management of network access and security. Every new Microsoft product
-or technology seems to obsolete the old rules and to introduce newer and more
-complex tools and methods. To Microsoft's credit though, the MMC does appear to
-be a step forward, but improved functionality comes at a great price.</P
-><P
->Before embarking on the configuration of network and system policies it is highly
-advisable to read the documentation available from Microsoft's web site regarding
-<A
-HREF="http://www.microsoft.com/ntserver/management/deployment/planguide/prof_policies.asp"
-TARGET="_top"
->Implementing Profiles and Policies in Windows NT 4.0 from http://www.microsoft.com/ntserver/management/deployment/planguide/prof_policies.asp</A
-> available from Microsoft.
-There are a large number of documents in addition to this old one that should also
-be read and understood. Try searching on the Microsoft web site for "Group Policies".</P
-><P
->What follows is a very brief discussion with some helpful notes. The information provided
-here is incomplete - you are warned.</P
-><DIV
-CLASS="SECT2"
-><H2
-CLASS="SECT2"
-><A
-NAME="AEN2972"
->17.1.1. Windows 9x/Me Policies</A
-></H2
-><P
->You need the Win98 Group Policy Editor to set Group Profiles up under Windows 9x/Me.
-It can be found on the Original full product Win98 installation CD under
-<TT
-CLASS="FILENAME"
->tools/reskit/netadmin/poledit</TT
->. Install this using the
-Add/Remove Programs facility and then click on the 'Have Disk' tab.</P
-><P
->Use the Group Policy Editor to create a policy file that specifies the location of
-user profiles and/or the <TT
-CLASS="FILENAME"
->My Documents</TT
-> etc. stuff. Then
-save these settings in a file called <TT
-CLASS="FILENAME"
->Config.POL</TT
-> that needs to
-be placed in the root of the [NETLOGON] share. If Win98 is configured to log onto
-the Samba Domain, it will automatically read this file and update the Win9x/Me registry
-of the machine as it logs on.</P
-><P
->Further details are covered in the Win98 Resource Kit documentation.</P
-><P
->If you do not take the right steps, then every so often Win9x/Me will check the
-integrity of the registry and will restore it's settings from the back-up
-copy of the registry it stores on each Win9x/Me machine. Hence, you will
-occasionally notice things changing back to the original settings.</P
-><P
->Install the group policy handler for Win9x to pick up group policies. Look on the
-Win98 CD in <TT
-CLASS="FILENAME"
->\tools\reskit\netadmin\poledit</TT
->.
-Install group policies on a Win9x client by double-clicking
-<TT
-CLASS="FILENAME"
->grouppol.inf</TT
->. Log off and on again a couple of times and see
-if Win98 picks up group policies. Unfortunately this needs to be done on every
-Win9x/Me machine that uses group policies.</P
-></DIV
-><DIV
-CLASS="SECT2"
-><H2
-CLASS="SECT2"
-><A
-NAME="AEN2984"
->17.1.2. Windows NT4 Style Policy Files</A
-></H2
-><P
->To create or edit <TT
-CLASS="FILENAME"
->ntconfig.pol</TT
-> you must use the NT Server
-Policy Editor, <B
-CLASS="COMMAND"
->poledit.exe</B
-> which is included with NT4 Server
-but <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->not NT Workstation</I
-></SPAN
->. There is a Policy Editor on a NT4
-Workstation but it is not suitable for creating <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->Domain Policies</I
-></SPAN
->.
-Further, although the Windows 95 Policy Editor can be installed on an NT4
-Workstation/Server, it will not work with NT clients. However, the files from
-the NT Server will run happily enough on an NT4 Workstation.</P
-><P
->You need <TT
-CLASS="FILENAME"
->poledit.exe, common.adm</TT
-> and <TT
-CLASS="FILENAME"
->winnt.adm</TT
->.
-It is convenient to put the two *.adm files in the <TT
-CLASS="FILENAME"
->c:\winnt\inf</TT
->
-directory which is where the binary will look for them unless told otherwise. Note also that that
-directory is normally 'hidden'.</P
-><P
->The Windows NT policy editor is also included with the Service Pack 3 (and
-later) for Windows NT 4.0. Extract the files using <B
-CLASS="COMMAND"
->servicepackname /x</B
->,
-i.e. that's <B
-CLASS="COMMAND"
->Nt4sp6ai.exe /x</B
-> for service pack 6a. The policy editor,
-<B
-CLASS="COMMAND"
->poledit.exe</B
-> and the associated template files (*.adm) should
-be extracted as well. It is also possible to downloaded the policy template
-files for Office97 and get a copy of the policy editor. Another possible
-location is with the Zero Administration Kit available for download from Microsoft.</P
-><DIV
-CLASS="SECT3"
-><H3
-CLASS="SECT3"
-><A
-NAME="AEN2999"
->17.1.2.1. Registry Tattoos</A
-></H3
-><P
-> With NT4 style registry based policy changes, a large number of settings are not
- automatically reversed as the user logs off. Since the settings that were in the
- NTConfig.POL file were applied to the client machine registry and that apply to the
- hive key HKEY_LOCAL_MACHINE are permanent until explicitly reversed. This is known
- as tattooing. It can have serious consequences down-stream and the administrator must
- be extremely careful not to lock out the ability to manage the machine at a later date.
- </P
-></DIV
-></DIV
-><DIV
-CLASS="SECT2"
-><H2
-CLASS="SECT2"
-><A
-NAME="AEN3002"
->17.1.3. MS Windows 200x / XP Professional Policies</A
-></H2
-><P
->Windows NT4 System policies allows setting of registry parameters specific to
-users, groups and computers (client workstations) that are members of the NT4
-style domain. Such policy file will work with MS Windows 2000 / XP clients also.</P
-><P
->New to MS Windows 2000 Microsoft introduced a new style of group policy that confers
-a superset of capabilities compared with NT4 style policies. Obviously, the tool used
-to create them is different, and the mechanism for implementing them is much changed.</P
-><P
->The older NT4 style registry based policies are known as <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->Administrative Templates</I
-></SPAN
->
-in MS Windows 2000/XP Group Policy Objects (GPOs). The later includes ability to set various security
-configurations, enforce Internet Explorer browser settings, change and redirect aspects of the
-users' desktop (including: the location of <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->My Documents</I
-></SPAN
-> files (directory), as
-well as intrinsics of where menu items will appear in the Start menu). An additional new
-feature is the ability to make available particular software Windows applications to particular
-users and/or groups.</P
-><P
->Remember: NT4 policy files are named <TT
-CLASS="FILENAME"
->NTConfig.POL</TT
-> and are stored in the root
-of the NETLOGON share on the domain controllers. A Windows NT4 user enters a username, a password
-and selects the domain name to which the logon will attempt to take place. During the logon
-process the client machine reads the NTConfig.POL file from the NETLOGON share on the authenticating
-server, modifies the local registry values according to the settings in this file.</P
-><P
->Windows 2K GPOs are very feature rich. They are NOT stored in the NETLOGON share, rather part of
-a Windows 200x policy file is stored in the Active Directory itself and the other part is stored
-in a shared (and replicated) volume called the SYSVOL folder. This folder is present on all Active
-Directory domain controllers. The part that is stored in the Active Directory itself is called the
-group policy container (GPC), and the part that is stored in the replicated share called SYSVOL is
-known as the group policy template (GPT).</P
-><P
->With NT4 clients the policy file is read and executed upon only aas each user log onto the network.
-MS Windows 200x policies are much more complex - GPOs are processed and applied at client machine
-startup (machine specific part) and when the user logs onto the network the user specific part
-is applied. In MS Windows 200x style policy management each machine and/or user may be subject
-to any number of concurently applicable (and applied) policy sets (GPOs). Active Directory allows
-the administrator to also set filters over the policy settings. No such equivalent capability
-exists with NT4 style policy files.</P
-><DIV
-CLASS="SECT3"
-><H3
-CLASS="SECT3"
-><A
-NAME="AEN3013"
->17.1.3.1. Administration of Win2K / XP Policies</A
-></H3
-><DIV
-CLASS="PROCEDURE"
-><P
-><B
->Instructions</B
-></P
-><P
->Instead of using the tool called "The System Policy Editor", commonly called Poledit (from the
-executable name poledit.exe), GPOs are created and managed using a Microsoft Management Console
-(MMC) snap-in as follows:</P
-><OL
-TYPE="1"
-><LI
-><P
->Go to the Windows 200x / XP menu <TT
-CLASS="FILENAME"
->Start-&#62;Programs-&#62;Administrative Tools</TT
->
- and select the MMC snap-in called "Active Directory Users and Computers"</P
-></LI
-><LI
-><P
->Select the domain or organizational unit (OU) that you wish to manage, then right click
-to open the context menu for that object, select the properties item.</P
-></LI
-><LI
-><P
->Now left click on the Group Policy tab, then left click on the New tab. Type a name
-for the new policy you will create.</P
-></LI
-><LI
-><P
->Now left click on the Edit tab to commence the steps needed to create the GPO.</P
-></LI
-></OL
-></DIV
-><P
->All policy configuration options are controlled through the use of policy administrative
-templates. These files have a .adm extension, both in NT4 as well as in Windows 200x / XP.
-Beware however, since the .adm files are NOT interchangible across NT4 and Windows 200x.
-The later introduces many new features as well as extended definition capabilities. It is
-well beyond the scope of this documentation to explain how to program .adm files, for that
-the adminsitrator is referred to the Microsoft Windows Resource Kit for your particular
-version of MS Windows.</P
-><DIV
-CLASS="NOTE"
-><P
-></P
-><TABLE
-CLASS="NOTE"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->The MS Windows 2000 Resource Kit contains a tool called gpolmig.exe. This tool can be used
-to migrate an NT4 NTConfig.POL file into a Windows 200x style GPO. Be VERY careful how you
-use this powerful tool. Please refer to the resource kit manuals for specific usage information.</P
-></TD
-></TR
-></TABLE
-></DIV
-></DIV
-></DIV
-></DIV
-><DIV
-CLASS="SECT1"
-><H1
-CLASS="SECT1"
-><A
-NAME="AEN3030"
->17.2. Managing Account/User Policies</A
-></H1
-><P
->Policies can define a specific user's settings or the settings for a group of users. The resulting
-policy file contains the registry settings for all users, groups, and computers that will be using
-the policy file. Separate policy files for each user, group, or computer are not not necessary.</P
-><P
->If you create a policy that will be automatically downloaded from validating domain controllers,
-you should name the file NTconfig.POL. As system administrator, you have the option of renaming the
-policy file and, by modifying the Windows NT-based workstation, directing the computer to update
-the policy from a manual path. You can do this by either manually changing the registry or by using
-the System Policy Editor. This path can even be a local path such that each machine has its own policy file,
-but if a change is necessary to all machines, this change must be made individually to each workstation.</P
-><P
->When a Windows NT4/200x/XP machine logs onto the network the NETLOGON share on the authenticating domain
-controller for the presence of the NTConfig.POL file. If one exists it is downloaded, parsed and then
-applied to the user's part of the registry.</P
-><P
->MS Windows 200x/XP clients that log onto an MS Windows Active Directory security domain may additionally,
-acquire policy settings through Group Policy Objects (GPOs) that are defined and stored in Active Directory
-itself. The key benefit of using AS GPOs is that they impose no registry <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->tatooing</I
-></SPAN
-> effect.
-This has considerable advanage compared with the use of NTConfig.POL (NT4) style policy updates.</P
-><P
->Inaddition to user access controls that may be imposed or applied via system and/or group policies
-in a manner that works in conjunction with user profiles, the user management environment under
-MS Windows NT4/200x/XP allows per domain as well as per user account restrictions to be applied.
-Common restrictions that are frequently used includes:</P
-><P
-><P
-></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
->Logon Hours</TD
-></TR
-><TR
-><TD
->Password Aging</TD
-></TR
-><TR
-><TD
->Permitted Logon from certain machines only</TD
-></TR
-><TR
-><TD
->Account type (Local or Global)</TD
-></TR
-><TR
-><TD
->User Rights</TD
-></TR
-></TBODY
-></TABLE
-><P
-></P
-></P
-><DIV
-CLASS="SECT2"
-><H2
-CLASS="SECT2"
-><A
-NAME="AEN3045"
->17.2.1. With Windows NT4/200x</A
-></H2
-><P
->The tools that may be used to configure these types of controls from the MS Windows environment are:
-The NT4 User Manager for domains, the NT4 System and Group Policy Editor, the registry editor (regedt32.exe).
-Under MS Windows 200x/XP this is done using the Microsoft Managment Console (MMC) with approapriate
-"snap-ins", the registry editor, and potentially also the NT4 System and Group Policy Editor.</P
-></DIV
-><DIV
-CLASS="SECT2"
-><H2
-CLASS="SECT2"
-><A
-NAME="AEN3048"
->17.2.2. With a Samba PDC</A
-></H2
-><P
->With a Samba Domain Controller, the new tools for managing of user account and policy information includes:
-<TT
-CLASS="FILENAME"
->smbpasswd, pdbedit, smbgroupedit, net, rpcclient.</TT
->. The administrator should read the
-man pages for these tools and become familiar with their use.</P
-></DIV
-></DIV
-><DIV
-CLASS="SECT1"
-><H1
-CLASS="SECT1"
-><A
-NAME="AEN3052"
->17.3. System Startup and Logon Processing Overview</A
-></H1
-><P
->The following attempts to document the order of processing of system and user policies following a system
-reboot and as part of the user logon:</P
-><P
-></P
-><OL
-TYPE="1"
-><LI
-><P
-> Network starts, then Remote Procedure Call System Service (RPCSS) and Multiple Universal Naming
- Convention Provider (MUP) start
- </P
-></LI
-><LI
-><P
-> Where Active Directory is involved, an ordered list of Group Policy Objects (GPOs) is downloaded
- and applied. The list may include GPOs that:
-<P
-></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
->Apply to the location of machines in a Directory</TD
-></TR
-><TR
-><TD
->Apply only when settings have changed</TD
-></TR
-><TR
-><TD
->Depend on configuration of scope of applicability: local, site, domain, organizational unit, etc.</TD
-></TR
-></TBODY
-></TABLE
-><P
-></P
->
- No desktop user interface is presented until the above have been processed.
- </P
-></LI
-><LI
-><P
-> Execution of start-up scripts (hidden and synchronous by defaut).
- </P
-></LI
-><LI
-><P
-> A keyboard action to affect start of logon (Ctrl-Alt-Del).
- </P
-></LI
-><LI
-><P
-> User credentials are validated, User profile is loaded (depends on policy settings).
- </P
-></LI
-><LI
-><P
-> An ordered list of User GPOs is obtained. The list contents depends on what is configured in respsect of:
-
-<P
-></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
->Is user a domain member, thus subject to particular policies</TD
-></TR
-><TR
-><TD
->Loopback enablement, and the state of the loopback policy (Merge or Replace)</TD
-></TR
-><TR
-><TD
->Location of the Active Directory itself</TD
-></TR
-><TR
-><TD
->Has the list of GPOs changed. No processing is needed if not changed.</TD
-></TR
-></TBODY
-></TABLE
-><P
-></P
->
- </P
-></LI
-><LI
-><P
-> User Policies are applied from Active Directory. Note: There are several types.
- </P
-></LI
-><LI
-><P
-> Logon scripts are run. New to Win2K and Active Directory, logon scripts may be obtained based on Group
- Policy objects (hidden and executed synchronously). NT4 style logon scripts are then run in a normal
- window.
- </P
-></LI
-><LI
-><P
-> The User Interface as determined from the GPOs is presented. Note: In a Samba domain (like and NT4
- Domain) machine (system) policies are applied at start-up, User policies are applied at logon.
- </P
-></LI
-></OL
-></DIV
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="advancednetworkmanagement.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="samba-howto-collection.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="profilemgmt.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Advanced Network Manangement</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="optional.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Desktop Profile Management</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
-> \ No newline at end of file
diff --git a/docs/htmldocs/portability.html b/docs/htmldocs/portability.html
index ac3e5b9adb..424fbe5c6c 100644
--- a/docs/htmldocs/portability.html
+++ b/docs/htmldocs/portability.html
@@ -5,7 +5,8 @@
>Portability</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
REL="HOME"
TITLE="SAMBA Project Documentation"
HREF="samba-howto-collection.html"><LINK
@@ -13,8 +14,8 @@ REL="UP"
TITLE="Appendixes"
HREF="appendixes.html"><LINK
REL="PREVIOUS"
-TITLE="Migration from NT4 PDC to Samba-3 PDC"
-HREF="nt4migration.html"><LINK
+TITLE="Appendixes"
+HREF="appendixes.html"><LINK
REL="NEXT"
TITLE="Samba and other CIFS clients"
HREF="other-clients.html"></HEAD
@@ -45,7 +46,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
-HREF="nt4migration.html"
+HREF="appendixes.html"
ACCESSKEY="P"
>Prev</A
></TD
@@ -72,48 +73,7 @@ WIDTH="100%"></DIV
CLASS="CHAPTER"
><H1
><A
-NAME="PORTABILITY"
-></A
->Chapter 29. Portability</H1
-><DIV
-CLASS="TOC"
-><DL
-><DT
-><B
->Table of Contents</B
-></DT
-><DT
->29.1. <A
-HREF="portability.html#AEN4444"
->HPUX</A
-></DT
-><DT
->29.2. <A
-HREF="portability.html#AEN4450"
->SCO Unix</A
-></DT
-><DT
->29.3. <A
-HREF="portability.html#AEN4454"
->DNIX</A
-></DT
-><DT
->29.4. <A
-HREF="portability.html#AEN4483"
->RedHat Linux Rembrandt-II</A
-></DT
-><DT
->29.5. <A
-HREF="portability.html#AEN4489"
->AIX</A
-></DT
-><DT
->29.6. <A
-HREF="portability.html#AEN4495"
->Solaris</A
-></DT
-></DL
-></DIV
+NAME="PORTABILITY">Chapter 23. Portability</H1
><P
>Samba works on a wide range of platforms but the interface all the
platforms provide is not always compatible. This chapter contains
@@ -123,9 +83,7 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="AEN4444"
->29.1. HPUX</A
-></H1
+NAME="AEN3139">23.1. HPUX</H1
><P
>HP's implementation of supplementary groups is, er, non-standard (for
hysterical reasons). There are two group files, /etc/group and
@@ -153,9 +111,7 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="AEN4450"
->29.2. SCO Unix</A
-></H1
+NAME="AEN3145">23.2. SCO Unix</H1
><P
>
If you run an old version of SCO Unix then you may need to get important
@@ -170,9 +126,7 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="AEN4454"
->29.3. DNIX</A
-></H1
+NAME="AEN3149">23.3. DNIX</H1
><P
>DNIX has a problem with seteuid() and setegid(). These routines are
needed for Samba to work correctly, but they were left out of the DNIX
@@ -277,9 +231,7 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="AEN4483"
->29.4. RedHat Linux Rembrandt-II</A
-></H1
+NAME="AEN3178">23.4. RedHat Linux Rembrandt-II</H1
><P
>By default RedHat Rembrandt-II during installation adds an
entry to /etc/hosts as follows:
@@ -296,60 +248,6 @@ is the master browse list holder and who is the master browser.</P
>Corrective Action: Delete the entry after the word loopback
in the line starting 127.0.0.1</P
></DIV
-><DIV
-CLASS="SECT1"
-><H1
-CLASS="SECT1"
-><A
-NAME="AEN4489"
->29.5. AIX</A
-></H1
-><DIV
-CLASS="SECT2"
-><H2
-CLASS="SECT2"
-><A
-NAME="AEN4491"
->29.5.1. Sequential Read Ahead</A
-></H2
-><P
->Disabling Sequential Read Ahead using <KBD
-CLASS="USERINPUT"
->vmtune -r 0</KBD
-> improves
-samba performance significally.</P
-></DIV
-></DIV
-><DIV
-CLASS="SECT1"
-><H1
-CLASS="SECT1"
-><A
-NAME="AEN4495"
->29.6. Solaris</A
-></H1
-><P
->Some people have been experiencing problems with F_SETLKW64/fcntl
-when running samba on solaris. The built in file locking mechanism was
-not scalable. Performance would degrade to the point where processes would
-get into loops of trying to lock a file. It woul try a lock, then fail,
-then try again. The lock attempt was failing before the grant was
-occurring. So the visible manifestation of this would be a handful of
-processes stealing all of the CPU, and when they were trussed they would
-be stuck if F_SETLKW64 loops.</P
-><P
->Sun released patches for Solaris 2.6, 8, and 9. The patch for Solaris 7
-has not been released yet.</P
-><P
->The patch revision for 2.6 is 105181-34
-for 8 is 108528-19
-and for 9 is 112233-04</P
-><P
->After the install of these patches it is recommended to reconfigure
-and rebuild samba.</P
-><P
->Thanks to Joe Meslovich for reporting</P
-></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
@@ -367,7 +265,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
-HREF="nt4migration.html"
+HREF="appendixes.html"
ACCESSKEY="P"
>Prev</A
></TD
@@ -395,7 +293,7 @@ ACCESSKEY="N"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
->Migration from NT4 PDC to Samba-3 PDC</TD
+>Appendixes</TD
><TD
WIDTH="34%"
ALIGN="center"
diff --git a/docs/htmldocs/printing.html b/docs/htmldocs/printing.html
index 620aa5e8ba..46ebbcdf84 100644
--- a/docs/htmldocs/printing.html
+++ b/docs/htmldocs/printing.html
@@ -1,59 +1,247 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter13.Printing Support</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"><link rel="home" href="index.html" title="SAMBA Project Documentation"><link rel="up" href="optional.html" title="PartIII.Advanced Configuration"><link rel="previous" href="groupmapping.html" title="Chapter12.Configuring Group Mapping"><link rel="next" href="CUPS-printing.html" title="Chapter14.CUPS Printing Support"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter13.Printing Support</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="groupmapping.html">Prev</a></td><th width="60%" align="center">PartIII.Advanced Configuration</th><td width="20%" align="right"><a accesskey="n" href="CUPS-printing.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="printing"></a>Chapter13.Printing Support</h2></div><div><div class="author"><h3 class="author">Gerald (Jerry) Carter</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt>&lt;<a href="mailto:jerry@samba.org">jerry@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author">Patrick Powell</h3><div class="affiliation"><div class="address"><p><tt>&lt;<a href="mailto:papowell@lprng.org">papowell@lprng.org</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate"> (3 May 2001) </p></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="printing.html#id2886394">Introduction</a></dt><dt><a href="printing.html#id2886510">Configuration</a></dt><dd><dl><dt><a href="printing.html#id2886557">Creating [print$]</a></dt><dt><a href="printing.html#id2886789">Setting Drivers for Existing Printers</a></dt><dt><a href="printing.html#id2886888">Support a large number of printers</a></dt><dt><a href="printing.html#id2886995">Adding New Printers via the Windows NT APW</a></dt><dt><a href="printing.html#id2887127">Samba and Printer Ports</a></dt></dl></dd><dt><a href="printing.html#id2886128">The Imprints Toolset</a></dt><dd><dl><dt><a href="printing.html#id2886155">What is Imprints?</a></dt><dt><a href="printing.html#id2887231">Creating Printer Driver Packages</a></dt><dt><a href="printing.html#id2887251">The Imprints server</a></dt><dt><a href="printing.html#id2887275">The Installation Client</a></dt></dl></dd><dt><a href="printing.html#id2886236">Diagnosis</a></dt><dd><dl><dt><a href="printing.html#id2886243">Introduction</a></dt><dt><a href="printing.html#id2887448">Debugging printer problems</a></dt><dt><a href="printing.html#id2887515">What printers do I have?</a></dt><dt><a href="printing.html#id2887557">Setting up printcap and print servers</a></dt><dt><a href="printing.html#id2887691">Job sent, no output</a></dt><dt><a href="printing.html#id2888240">Job sent, strange output</a></dt><dt><a href="printing.html#id2888316">Raw PostScript printed</a></dt><dt><a href="printing.html#id2888334">Advanced Printing</a></dt><dt><a href="printing.html#id2888360">Real debugging</a></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2886394"></a>Introduction</h2></div></div><p>Beginning with the 2.2.0 release, Samba supports
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<HTML
+><HEAD
+><TITLE
+>Printing Support</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
+REL="HOME"
+TITLE="SAMBA Project Documentation"
+HREF="samba-howto-collection.html"><LINK
+REL="UP"
+TITLE="Optional configuration"
+HREF="optional.html"><LINK
+REL="PREVIOUS"
+TITLE="Hosting a Microsoft Distributed File System tree on Samba"
+HREF="msdfs.html"><LINK
+REL="NEXT"
+TITLE="Unified Logons between Windows NT and UNIX using Winbind"
+HREF="winbind.html"></HEAD
+><BODY
+CLASS="CHAPTER"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><TABLE
+SUMMARY="Header navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>SAMBA Project Documentation</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="msdfs.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+></TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="winbind.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="CHAPTER"
+><H1
+><A
+NAME="PRINTING">Chapter 14. Printing Support</H1
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN1920">14.1. Introduction</H1
+><P
+>Beginning with the 2.2.0 release, Samba supports
the native Windows NT printing mechanisms implemented via
MS-RPC (i.e. the SPOOLSS named pipe). Previous versions of
-Samba only supported LanMan printing calls.</p><p>The additional functionality provided by the new
-SPOOLSS support includes:</p><div class="itemizedlist"><ul type="disc"><li><p>Support for downloading printer driver
+Samba only supported 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
+ </P
+></LI
+><LI
+><P
+>Uploading of printer drivers via the
Windows NT Add Printer Wizard (APW) or the
- Imprints tool set (refer to <a href="http://imprints.sourceforge.net" target="_top">http://imprints.sourceforge.net</a>).
- </p></li><li><p>Support for the native MS-RPC printing
+ Imprints tool set (refer to <A
+HREF="http://imprints.sourceforge.net"
+TARGET="_top"
+>http://imprints.sourceforge.net</A
+>).
+ </P
+></LI
+><LI
+><P
+>Support for the native MS-RPC printing
calls such as StartDocPrinter, EnumJobs(), etc... (See
- the MSDN documentation at <a href="http://msdn.microsoft.com/" target="_top">http://msdn.microsoft.com/</a>
+ the MSDN documentation at <A
+HREF="http://msdn.microsoft.com/"
+TARGET="_top"
+>http://msdn.microsoft.com/</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
+ </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 databases for spooled job
- information</p></li></ul></div><p>
-There has been some initial confusion about what all this means
+ 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. 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: <span class="emphasis"><em>How to Add Printers with No User
-Interaction in Windows 2000</em></span>
-</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" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2886510"></a>Configuration</h2></div></div><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">[print$] vs. [printer$]</h3><p>
-Previous versions of Samba recommended using a share named [printer$].
+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: <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>How to Add Printers with No User
+Interaction in Windows 2000</I
+></SPAN
+></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"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN1942">14.2. Configuration</H1
+><DIV
+CLASS="WARNING"
+><P
+></P
+><TABLE
+CLASS="WARNING"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/warning.gif"
+HSPACE="5"
+ALT="Warning"></TD
+><TH
+ALIGN="LEFT"
+VALIGN="CENTER"
+><B
+>[print$] vs. [printer$]</B
+></TH
+></TR
+><TR
+><TD
+>&nbsp;</TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><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 <i><tt>printer driver location</tt></i>
+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 <i><tt>printer driver</tt></i> provided
+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></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2886557"></a>Creating [print$]</h3></div></div><p>
-In order to support the uploading of printer driver
+the client.</P
+></TD
+></TR
+></TABLE
+></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN1950">14.2.1. Creating [print$]</H2
+><P
+>In order to support the uploading of printer driver
files, you must first configure a file share named [print$].
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><p>You should modify the server's smb.conf file to add the global
+download).</P
+><P
+>You should modify the server's smb.conf file to add the global
parameters and 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><pre class="programlisting">
-[global]
+appropriate values for your site):</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>[global]
; members of the ntadmin group should be able
; to add drivers and set printer properties
; root is implicitly a 'printer admin'
@@ -69,100 +257,289 @@ appropriate values for your site):</p><pre class="programlisting">
; 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,root
-</pre><p>The <a href="smb.conf.5.html#WRITELIST" target="_top"><i><tt>
-write list</tt></i></a> is used to allow administrative
+ write list = @ntadmin,root</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>guest
-ok = yes</b></a> depends upon how your
+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><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Author's Note</h3><p>
-The non-issue is that if all your Windows NT users are guaranteed to be
+an account on the Samba host, then this is a non-issue.</P
+><DIV
+CLASS="NOTE"
+><P
+></P
+><TABLE
+CLASS="NOTE"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/note.gif"
+HSPACE="5"
+ALT="Note"></TD
+><TH
+ALIGN="LEFT"
+VALIGN="CENTER"
+><B
+>Author's Note</B
+></TH
+></TR
+><TR
+><TD
+>&nbsp;</TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+>The non-issue is that if all your Windows NT users are guaranteed 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>map to guest = Bad User
-</b></a> in the [global] section as well. Make sure
+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></div><p>In order for a Windows NT print server to support
+though. --jerry</P
+></TD
+></TR
+></TABLE
+></DIV
+><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><tt>
-[print$]-----
- |-W32X86 ; &quot;Windows NT x86&quot;
- |-WIN40 ; &quot;Windows 95/98&quot;
- |-W32ALPHA ; &quot;Windows NT Alpha_AXP&quot;
- |-W32MIPS ; &quot;Windows NT R4000&quot;
- |-W32PPC ; &quot;Windows NT PowerPC&quot;
-</tt></p><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">ATTENTION! REQUIRED PERMISSIONS</h3><p>
-In order to currently add a new driver to you Samba host,
-one of two conditions must hold true:
-</p><div class="itemizedlist"><ul type="disc"><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#PRINTERADMIN" target="_top"><i><tt>printer
- admin</tt></i></a> list.</p></li></ul></div><p>
-Of course, the connected account must still possess access
+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"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/warning.gif"
+HSPACE="5"
+ALT="Warning"></TD
+><TH
+ALIGN="LEFT"
+VALIGN="CENTER"
+><B
+>ATTENTION! REQUIRED PERMISSIONS</B
+></TH
+></TR
+><TR
+><TD
+>&nbsp;</TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><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#PRINTERADMIN"
+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 subdirectories beneath [print$]. Remember
-that all file shares are set to 'read only' by default.
-</p></div><p>
-Once you have created the required [print$] service and
+that all file shares are set to 'read only' by default.</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 <i><tt>printer admin</tt></i>) account
-from a Windows NT 4.0/2k client. Open &quot;Network Neighbourhood&quot; or
-&quot;My Network Places&quot; and browse for the Samba host. Once you have located
-the server, navigate to the &quot;Printers...&quot; folder.
+a root (or <TT
+CLASS="PARAMETER"
+><I
+>printer admin</I
+></TT
+>) account
+from a Windows NT 4.0/2k client. Open "Network Neighbourhood" or
+"My Network Places" and browse for the Samba host. Once you have located
+the server, navigate to the "Printers..." folder.
You should see an initial listing of printers
-that matches the printer shares defined on your Samba host.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2886789"></a>Setting Drivers for Existing Printers</h3></div></div><p>The initial listing of printers in the Samba host's
+that matches the printer shares defined on your Samba host.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN1985">14.2.2. Setting Drivers for Existing Printers</H2
+><P
+>The initial listing of printers in the Samba host's
Printers folder will have no real printer driver assigned
to them. This defaults to a NULL string to allow the use
of the local Add Printer Wizard on NT/2000 clients.
Attempting to view the printer properties for a printer
which has this default driver assigned will result in
-the error message:</p><p>
-<span class="emphasis"><em>Device settings cannot be displayed. The driver
+the error message:</P
+><P
+><SPAN
+CLASS="emphasis"
+><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?</em></span>
-</p><p>
-Click &quot;No&quot; in the error dialog and you will be presented with
+driver now?</I
+></SPAN
+></P
+><P
+>Click "No" in the error dialog and you will be presented with
the printer properties window. The way to assign a driver to a
-printer is to either
-</p><div class="itemizedlist"><ul type="disc"><li><p>Use the &quot;New Driver...&quot; 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></div><p>If you wish to install printer drivers for client
-operating systems other than &quot;Windows NT x86&quot;, you will need
-to use the &quot;Sharing&quot; tab of the printer properties dialog.</p><p>Assuming you have connected with a root account, you
+printer is to 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><p>A few closing comments for this section, it is possible
+ACLs and device settings using this dialog box.</P
+><P
+>A few closing comments for this section, 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>smb.conf</tt>.</p><p>Another interesting side note is that Windows NT clients do
+<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 &quot;Print&quot;
-permissions to the &quot;Everyone&quot; well-known group.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2886888"></a>Support a large number of printers</h3></div></div><p>One issue that has arisen during the development
+permissions assigned by Windows NT to a printer gives the "Print"
+permissions to the "Everyone" well-known group.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN2001">14.2.3. Support a large number of printers</H2
+><P
+>One issue that has arisen during the development
phase of Samba 2.2 is the need to support driver downloads for
100's of printers. Using the Windows NT APW is somewhat
awkward to say the list. If more than one printer are using the
-same driver, the <a href="rpcclient.1.html" target="_top"><b>rpcclient's
-setdriver command</b></a> can be used to set the driver
+same driver, the <A
+HREF="rpcclient.1.html"
+TARGET="_top"
+><B
+CLASS="COMMAND"
+>rpcclient's
+setdriver command</B
+></A
+> can be used to set the driver
associated with an installed driver. The following is example
-of how this could be accomplished:</p><p>
-<tt>$ </tt><b><tt>rpcclient pogo -U root%secret -c &quot;enumdrivers&quot;</tt></b>
-</p><pre class="programlisting">
+of how this could be accomplished:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>
+<TT
+CLASS="PROMPT"
+>$ </TT
+>rpcclient pogo -U root%secret -c "enumdrivers"
Domain=[NARNIA] OS=[Unix] Server=[Samba 2.2.0-alpha3]
[Windows NT x86]
@@ -174,52 +551,149 @@ Printer Driver Info 1:
Printer Driver Info 1:
Driver Name: [HP LaserJet 4Si/4SiMX PS]
-</pre><p>
-<tt>$ </tt><b><tt>rpcclient pogo -U root%secret -c &quot;enumprinters&quot;</tt></b>
-</p><pre class="programlisting">
+
+<TT
+CLASS="PROMPT"
+>$ </TT
+>rpcclient pogo -U root%secret -c "enumprinters"
Domain=[NARNIA] OS=[Unix] Server=[Samba 2.2.0-alpha3]
flags:[0x800000]
name:[\\POGO\hp-print]
description:[POGO\\POGO\hp-print,NO DRIVER AVAILABLE FOR THIS PRINTER,]
comment:[]
-</pre><p>
-<tt>$ </tt><b><tt>rpcclient pogo -U root%secret -c &quot;setdriver hp-print \&quot;HP LaserJet 4000 Series PS\&quot;&quot;</tt></b>
-</p><pre class="programlisting">
+<TT
+CLASS="PROMPT"
+>$ </TT
+>rpcclient pogo -U root%secret \
+<TT
+CLASS="PROMPT"
+>&gt; </TT
+> -c "setdriver hp-print \"HP LaserJet 4000 Series PS\""
Domain=[NARNIA] OS=[Unix] Server=[Samba 2.2.0-alpha3]
-Successfully set hp-print to driver HP LaserJet 4000 Series PS.
-</pre></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2886995"></a>Adding New Printers via the Windows NT APW</h3></div></div><p>
-By default, Samba offers all printer shares defined in <tt>smb.conf</tt>
-in the &quot;Printers...&quot; folder. Also existing in this folder is the Windows NT
-Add Printer Wizard icon. The APW will be show only if
-</p><div class="itemizedlist"><ul type="disc"><li><p>The connected user is able to successfully
+Successfully set hp-print to driver HP LaserJet 4000 Series PS.</PRE
+></P
+></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN2012">14.2.4. Adding New Printers via the Windows NT APW</H2
+><P
+>By default, Samba offers all printer shares defined in <TT
+CLASS="FILENAME"
+>smb.conf</TT
+>
+in the "Printers..." folder. Also existing in this folder is the Windows NT
+Add Printer Wizard icon. The APW will be show only if</P
+><P
+></P
+><UL
+><LI
+><P
+>The connected user is able to successfully
execute an OpenPrinterEx(\\server) with administrative
- privileges (i.e. root or <i><tt>printer admin</tt></i>).
- </p></li><li><p><a href="smb.conf.5.html#SHOWADDPRINTERWIZARD" target="_top"><i><tt>show
- add printer wizard = yes</tt></i></a> (the default).
- </p></li></ul></div><p>
-In order to be able to use the APW to successfully add a printer to a Samba
-server, the <a href="smb.conf.5.html#ADDPRINTERCOMMAND" target="_top"><i><tt>add
-printer command</tt></i></a> must have a defined value. The program
+ privileges (i.e. root or <TT
+CLASS="PARAMETER"
+><I
+>printer admin</I
+></TT
+>).
+ </P
+></LI
+><LI
+><P
+><A
+HREF="smb.conf.5.html#SHOWADDPRINTERWIZARD"
+TARGET="_top"
+><TT
+CLASS="PARAMETER"
+><I
+>show
+ add printer wizard = yes</I
+></TT
+></A
+> (the default).
+ </P
+></LI
+></UL
+><P
+>In order to be able to use the APW to successfully add a printer to a Samba
+server, the <A
+HREF="smb.conf.5.html#ADDPRINTERCOMMAND"
+TARGET="_top"
+><TT
+CLASS="PARAMETER"
+><I
+>add
+printer command</I
+></TT
+></A
+> must have a defined value. The program
hook must successfully add the printer to the system (i.e.
-<tt>/etc/printcap</tt> or appropriate files) and
-<tt>smb.conf</tt> if necessary.
-</p><p>
-When using the APW from a client, if the named printer share does
-not exist, <b>smbd</b> will execute the <i><tt>add printer
-command</tt></i> and reparse to the <tt>smb.conf</tt>
+<TT
+CLASS="FILENAME"
+>/etc/printcap</TT
+> or appropriate files) and
+<TT
+CLASS="FILENAME"
+>smb.conf</TT
+> if necessary.</P
+><P
+>When using the APW from a client, if the named printer share does
+not exist, <B
+CLASS="COMMAND"
+>smbd</B
+> will execute the <TT
+CLASS="PARAMETER"
+><I
+>add printer
+command</I
+></TT
+> and reparse to the <TT
+CLASS="FILENAME"
+>smb.conf</TT
+>
to attempt to locate the new printer share. If the share is still not defined,
-an error of &quot;Access Denied&quot; is returned to the client. Note that the
-<i><tt>add printer program</tt></i> is executed under the context
-of the connected user, not necessarily a root account.
-</p><p>
-There is a complementary <a href="smb.conf.5.html#DELETEPRINTERCOMMAND" target="_top"><i><tt>delete
-printer command</tt></i></a> for removing entries from the &quot;Printers...&quot;
-folder.
-</p><p>
-The following is an example <a href="smb.conf.5.html#ADDPRINTERCOMMAN" target="_top"><i><tt>add printer command</tt></i></a> script. It adds the appropriate entries to <tt>/etc/printcap.local</tt> (change that to what you need) and returns a line of 'Done' which is needed for the whole process to work.
-</p><pre class="programlisting">
-#!/bin/sh
+an error of "Access Denied" is returned to the client. Note that the
+<TT
+CLASS="PARAMETER"
+><I
+>add printer program</I
+></TT
+> is executed under the context
+of the connected user, not necessarily a root account.</P
+><P
+>There is a complementary <A
+HREF="smb.conf.5.html#DELETEPRINTERCOMMAND"
+TARGET="_top"
+><TT
+CLASS="PARAMETER"
+><I
+>delete
+printer command</I
+></TT
+></A
+> for removing entries from the "Printers..."
+folder.</P
+><P
+>The following is an example <A
+HREF="smb.conf.5.html#ADDPRINTERCOMMAN"
+TARGET="_top"
+><TT
+CLASS="PARAMETER"
+><I
+>add printer command</I
+></TT
+></A
+> script. It adds the appropriate entries to <TT
+CLASS="FILENAME"
+>/etc/printcap.local</TT
+> (change that to what you need) and returns a line of 'Done' which is needed for the whole process to work.</P
+><PRE
+CLASS="PROGRAMLISTING"
+>#!/bin/sh
# Script to insert a new printer entry into printcap.local
#
@@ -235,84 +709,203 @@ The following is an example <a href="smb.conf.5.html#ADDPRINTERCOMMAN" target="_
PRINTCAP=/etc/printcap.local
DATE=`date +%Y%m%d-%H%M%S`
LP=lp
-RESTART=&quot;service lpd restart&quot;
+RESTART="service lpd restart"
# Keep a copy
cp $PRINTCAP $PRINTCAP.$DATE
# Add the printer to $PRINTCAP
-echo &quot;&quot; &gt;&gt; $PRINTCAP
-echo &quot;$2|$1:\\&quot; &gt;&gt; $PRINTCAP
-echo &quot; :sd=/var/spool/lpd/$2:\\&quot; &gt;&gt; $PRINTCAP
-echo &quot; :mx=0:ml=0:sh:\\&quot; &gt;&gt; $PRINTCAP
-echo &quot; :lp=/usr/local/samba/var/print/$5.prn:&quot; &gt;&gt; $PRINTCAP
+echo "" &#62;&#62; $PRINTCAP
+echo "$2|$1:\\" &#62;&#62; $PRINTCAP
+echo " :sd=/var/spool/lpd/$2:\\" &#62;&#62; $PRINTCAP
+echo " :mx=0:ml=0:sh:\\" &#62;&#62; $PRINTCAP
+echo " :lp=/usr/local/samba/var/print/$5.prn:" &#62;&#62; $PRINTCAP
-touch &quot;/usr/local/samba/var/print/$5.prn&quot; &gt;&gt; /tmp/printadd.$$ 2&gt;&amp;1
-chown $LP &quot;/usr/local/samba/var/print/$5.prn&quot; &gt;&gt; /tmp/printadd.$$ 2&gt;&amp;1
+touch "/usr/local/samba/var/print/$5.prn" &#62;&#62; /tmp/printadd.$$ 2&#62;&#38;1
+chown $LP "/usr/local/samba/var/print/$5.prn" &#62;&#62; /tmp/printadd.$$ 2&#62;&#38;1
mkdir /var/spool/lpd/$2
chmod 700 /var/spool/lpd/$2
chown $LP /var/spool/lpd/$2
-#echo $1 &gt;&gt; &quot;/usr/local/samba/var/print/$5.prn&quot;
-#echo $2 &gt;&gt; &quot;/usr/local/samba/var/print/$5.prn&quot;
-#echo $3 &gt;&gt; &quot;/usr/local/samba/var/print/$5.prn&quot;
-#echo $4 &gt;&gt; &quot;/usr/local/samba/var/print/$5.prn&quot;
-#echo $5 &gt;&gt; &quot;/usr/local/samba/var/print/$5.prn&quot;
-#echo $6 &gt;&gt; &quot;/usr/local/samba/var/print/$5.prn&quot;
-$RESTART &gt;&gt; &quot;/usr/local/samba/var/print/$5.prn&quot;
+#echo $1 &#62;&#62; "/usr/local/samba/var/print/$5.prn"
+#echo $2 &#62;&#62; "/usr/local/samba/var/print/$5.prn"
+#echo $3 &#62;&#62; "/usr/local/samba/var/print/$5.prn"
+#echo $4 &#62;&#62; "/usr/local/samba/var/print/$5.prn"
+#echo $5 &#62;&#62; "/usr/local/samba/var/print/$5.prn"
+#echo $6 &#62;&#62; "/usr/local/samba/var/print/$5.prn"
+$RESTART &#62;&#62; "/usr/local/samba/var/print/$5.prn"
# Not sure if this is needed
touch /usr/local/samba/lib/smb.conf
#
# You need to return a value, but I am not sure what it means.
#
-echo &quot;Done&quot;
-exit 0
-</pre></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2887127"></a>Samba and Printer Ports</h3></div></div><p>
-Windows NT/2000 print servers associate a port with each printer. These normally
+echo "Done"
+exit 0</PRE
+></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN2042">14.2.5. Samba and Printer Ports</H2
+><P
+>Windows NT/2000 print servers associate a port with each printer. These normally
take the form of LPT1:, COM1:, FILE:, etc... Samba must also support the
concept of ports associated with a printer. By default, only one printer port,
-named &quot;Samba Printer Port&quot;, exists on a system. Samba does not really a port in
-order to print, rather it is a requirement of Windows clients.
-</p><p>
-Note that Samba does not support the concept of &quot;Printer Pooling&quot; internally
+named "Samba Printer Port", exists on a system. Samba does not really a port in
+order to print, rather it is a requirement of Windows clients. </P
+><P
+>Note that Samba does not support the concept of "Printer Pooling" internally
either. This is when a logical printer is assigned to multiple ports as
-a form of load balancing or fail over.
-</p><p>
-If you require that multiple ports be defined for some reason,
-<tt>smb.conf</tt> possesses a <a href="smb.conf.5.html#ENUMPORTSCOMMAND" target="_top"><i><tt>enumports
-command</tt></i></a> which can be used to define an external program
-that generates a listing of ports on a system.
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2886128"></a>The Imprints Toolset</h2></div></div><p>The Imprints tool set provides a UNIX equivalent of the
+a form of load balancing or fail over.</P
+><P
+>If you require that multiple ports be defined for some reason,
+<TT
+CLASS="FILENAME"
+>smb.conf</TT
+> possesses a <A
+HREF="smb.conf.5.html#ENUMPORTSCOMMAND"
+TARGET="_top"
+><TT
+CLASS="PARAMETER"
+><I
+>enumports
+command</I
+></TT
+></A
+> which can be used to define an external program
+that generates a listing of ports on a system.</P
+></DIV
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN2050">14.3. The Imprints Toolset</H1
+><P
+>The Imprints tool set provides a UNIX equivalent of the
Windows NT Add Printer Wizard. For complete information, please
- 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
+ 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" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2886155"></a>What is Imprints?</h3></div></div><p>Imprints is a collection of tools for supporting the goals
- of</p><div class="itemizedlist"><ul type="disc"><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
+ only provide a brief introduction to the features of Imprints.</P
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN2054">14.3.1. What is Imprints?</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><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2887231"></a>Creating Printer Driver Packages</h3></div></div><p>The process of creating printer driver packages is beyond
+ and Windows NT 4 print servers.</P
+></LI
+></UL
+></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN2064">14.3.2. Creating Printer Driver Packages</H2
+><P
+>The process of creating printer driver packages is beyond
the scope of this document (refer to Imprints.txt also included
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" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2887251"></a>The Imprints server</h3></div></div><p>The Imprints server is really a database server that
+ installation client.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN2067">14.3.3. The Imprints server</H2
+><P
+>The Imprints server is really a database server that
may be queried via standard HTTP mechanisms. Each printer
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
- <span class="emphasis"><em>not</em></span> recommended that this security check
- be disabled.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2887275"></a>The Installation Client</h3></div></div><p>More information regarding the Imprints installation client
- is available in the <tt>Imprints-Client-HOWTO.ps</tt>
- file included with the imprints source package.</p><p>The Imprints installation client comes in two forms.</p><div class="itemizedlist"><ul type="disc"><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></div><p>The installation client (in both forms) provides a means
+ <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>not</I
+></SPAN
+> recommended that this security check
+ be disabled.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN2071">14.3.4. The Installation Client</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>smbclient</b>
- and <b>rpcclient</b>.</p><pre class="programlisting">
+ 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
@@ -322,260 +915,472 @@ foreach (supported architecture for a given driver)
}
4. rpcclient: Issue an AddPrinterEx() MS-RPC to actually
- create the printer
-</pre><p>One of the problems encountered when implementing
+ 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 &quot;Apple LaserWriter II NTX v51.8&quot;
- and Windows 95 calls its version of this driver &quot;Apple
- LaserWriter II NTX&quot;</p><p>The problem is how to know what client drivers have
+ NT includes a driver named "Apple LaserWriter II NTX v51.8"
+ and Windows 95 calls its 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>HKLM\System\CurrentControlSet\Control\Print\Environment
- </tt></p><p>will reveal that Windows NT always uses the NT driver
+ 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. 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
- already been installed?</p><p>The way of sidestepping this limitation is to require
+ 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" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2886236"></a>Diagnosis</h2></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2886243"></a>Introduction</h3></div></div><p>
-This is a short description of how to debug printing problems with
+ installed first.</P
+></DIV
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN2093">14.4. Diagnosis</H1
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN2095">14.4.1. Introduction</H2
+><P
+>This is a short description of how to debug printing problems with
Samba. This describes how to debug problems with printing from a SMB
client to a Samba server, not the other way around. For the reverse
-see the examples/printing directory.
-</p><p>
-Ok, so you want to print to a Samba server from your PC. The first
+see the examples/printing directory.</P
+><P
+>Ok, so you want to print to a Samba server from your PC. The first
thing you need to understand is that Samba does not actually do any
printing itself, it just acts as a middleman between your PC client
and your Unix printing subsystem. Samba receives the file from the PC
-then passes the file to a external &quot;print command&quot;. What print command
-you use is up to you.
-</p><p>
-The whole things is controlled using options in smb.conf. The most
+then passes the file to a external "print command". What print command
+you use is up to you.</P
+><P
+>The whole things is controlled using options in smb.conf. The most
relevant options (which you should look up in the smb.conf man page)
-are:
-</p><pre class="programlisting">
- [global]
+are:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+> [global]
print command - send a file to a spooler
lpq command - get spool queue status
lprm command - remove a job
[printers]
- path = /var/spool/lpd/samba
-</pre><p>
-The following are nice to know about:
-</p><pre class="programlisting">
- queuepause command - stop a printer or print queue
- queueresume command - start a printer or print queue
-</pre><p>
-Example:
-</p><pre class="programlisting">
- print command = /usr/bin/lpr -r -P%p %s
+ path = /var/spool/lpd/samba</PRE
+></P
+><P
+>The following are nice to know about:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+> queuepause command - stop a printer or print queue
+ queueresume command - start a printer or print queue</PRE
+></P
+><P
+>Example:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+> print command = /usr/bin/lpr -r -P%p %s
lpq command = /usr/bin/lpq -P%p %s
lprm command = /usr/bin/lprm -P%p %j
queuepause command = /usr/sbin/lpc -P%p stop
- queuepause command = /usr/sbin/lpc -P%p start
-</pre><p>
-Samba should set reasonable defaults for these depending on your
+ queuepause command = /usr/sbin/lpc -P%p start</PRE
+></P
+><P
+>Samba should set reasonable defaults for these depending on your
system type, but it isn't clairvoyant. It is not uncommon that you
have to tweak these for local conditions. The commands should
always have fully specified pathnames, as the smdb may not have
-the correct PATH values.
-</p><p>
-When you send a job to Samba to be printed, it will make a temporary
+the correct PATH values.</P
+><P
+>When you send a job to Samba to be printed, it will make a temporary
copy of it in the directory specified in the [printers] section.
and it should be periodically cleaned out. The lpr -r option
requests that the temporary copy be removed after printing; If
printing fails then you might find leftover files in this directory,
and it should be periodically cleaned out. Samba used the lpq
-command to determine the &quot;job number&quot; assigned to your print job
-by the spooler.
-</p><p>
-The %&gt;letter&lt; are &quot;macros&quot; that get dynamically replaced with appropriate
+command to determine the "job number" assigned to your print job
+by the spooler.</P
+><P
+>The %&gt;letter&lt; are "macros" that get dynamically replaced with appropriate
values when they are used. The %s gets replaced with the name of the spool
file that Samba creates and the %p gets replaced with the name of the
-printer. The %j gets replaced with the &quot;job number&quot; which comes from
-the lpq output.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2887448"></a>Debugging printer problems</h3></div></div><p>
-One way to debug printing problems is to start by replacing these
+printer. The %j gets replaced with the "job number" which comes from
+the lpq output.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN2111">14.4.2. Debugging printer problems</H2
+><P
+>One way to debug printing problems is to start by replacing these
command with shell scripts that record the arguments and the contents
of the print file. A simple example of this kind of things might
-be:
-</p><pre class="programlisting">
- print command = /tmp/saveprint %p %s
+be:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+> print command = /tmp/saveprint %p %s
#!/bin/saveprint
# we make sure that we are the right user
- /usr/bin/id -p &gt;/tmp/tmp.print
+ /usr/bin/id -p &#62;/tmp/tmp.print
# we run the command and save the error messages
# replace the command with the one appropriate for your system
- /usr/bin/lpr -r -P$1 $2 2&gt;&gt;&amp;/tmp/tmp.print
-</pre><p>
-Then you print a file and try removing it. You may find that the
+ /usr/bin/lpr -r -P$1 $2 2&#62;&#62;&#38;/tmp/tmp.print</PRE
+></P
+><P
+>Then you print a file and try removing it. You may find that the
print queue needs to be stopped in order to see the queue status
-and remove the job:
-</p><pre class="programlisting">
-
-h4: {42} % echo hi &gt;/tmp/hi
+and remove the job:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>&#13;h4: {42} % echo hi &#62;/tmp/hi
h4: {43} % smbclient //localhost/lw4
added interface ip=10.0.0.4 bcast=10.0.0.255 nmask=255.255.255.0
Password:
Domain=[ASTART] OS=[Unix] Server=[Samba 2.0.7]
-smb: \&gt; print /tmp/hi
+smb: \&#62; print /tmp/hi
putting file /tmp/hi as hi-17534 (0.0 kb/s) (average 0.0 kb/s)
-smb: \&gt; queue
+smb: \&#62; queue
1049 3 hi-17534
-smb: \&gt; cancel 1049
+smb: \&#62; cancel 1049
Error cancelling job 1049 : code 0
-smb: \&gt; cancel 1049
+smb: \&#62; cancel 1049
Job 1049 cancelled
-smb: \&gt; queue
-smb: \&gt; exit
-</pre><p>
-The 'code 0' indicates that the job was removed. The comment
+smb: \&#62; queue
+smb: \&#62; exit</PRE
+></P
+><P
+>The 'code 0' indicates that the job was removed. The comment
by the smbclient is a bit misleading on this.
You can observe the command output and then and look at the
/tmp/tmp.print file to see what the results are. You can quickly
find out if the problem is with your printing system. Often people
have problems with their /etc/printcap file or permissions on
-various print queues.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2887515"></a>What printers do I have?</h3></div></div><p>
-You can use the 'testprns' program to check to see if the printer
+various print queues.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN2120">14.4.3. What printers do I have?</H2
+><P
+>You can use the 'testprns' program to check to see if the printer
name you are using is recognized by Samba. For example, you can
-use:
-</p><pre class="programlisting">
- testprns printer /etc/printcap
-</pre><p>
-Samba can get its printcap information from a file or from a program.
+use:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+> testprns printer /etc/printcap</PRE
+></P
+><P
+>Samba can get its printcap information from a file or from a program.
You can try the following to see the format of the extracted
-information:
-</p><pre class="programlisting">
- testprns -a printer /etc/printcap
+information:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+> testprns -a printer /etc/printcap
- testprns -a printer '|/bin/cat printcap'
-</pre></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2887557"></a>Setting up printcap and print servers</h3></div></div><p>
-You may need to set up some printcaps for your Samba system to use.
+ testprns -a printer '|/bin/cat printcap'</PRE
+></P
+></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN2128">14.4.4. Setting up printcap and print servers</H2
+><P
+>You may need to set up some printcaps for your Samba system to use.
It is strongly recommended that you use the facilities provided by
-the print spooler to set up queues and printcap information.
-</p><p>
-Samba requires either a printcap or program to deliver printcap
-information. This printcap information has the format:
-</p><pre class="programlisting">
- name|alias1|alias2...:option=value:...
-</pre><p>
-For almost all printing systems, the printer 'name' must be composed
+the print spooler to set up queues and printcap information.</P
+><P
+>Samba requires either a printcap or program to deliver printcap
+information. This printcap information has the format:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+> name|alias1|alias2...:option=value:...</PRE
+></P
+><P
+>For almost all printing systems, the printer 'name' must be composed
only of alphanumeric or underscore '_' characters. Some systems also
allow hyphens ('-') as well. An alias is an alternative name for the
printer, and an alias with a space in it is used as a 'comment'
about the printer. The printcap format optionally uses a \ at the end of lines
-to extend the printcap to multiple lines.
-</p><p>
-Here are some examples of printcap files:
-</p><p>
-</p><div class="orderedlist"><ol type="1"><li><p>
-pr just printer name
-</p></li><li><p>
-pr|alias printer name and alias
-</p></li><li><p>
-pr|My Printer printer name, alias used as comment
-</p></li><li><p>
-pr:sh:\ Same as pr:sh:cm= testing
+to extend the printcap to multiple lines.</P
+><P
+>Here are some examples of printcap files:</P
+><P
+><P
+></P
+><OL
+TYPE="1"
+><LI
+><P
+>pr just printer name</P
+></LI
+><LI
+><P
+>pr|alias printer name and alias</P
+></LI
+><LI
+><P
+>pr|My Printer printer name, alias used as comment</P
+></LI
+><LI
+><P
+>pr:sh:\ Same as pr:sh:cm= testing
:cm= \
- testing
-</p></li><li><p>
-pr:sh Same as pr:sh:cm= testing
- :cm= testing
-</p></li></ol></div><p>
-</p><p>
-Samba reads the printcap information when first started. If you make
-changes in the printcap information, then you must do the following:
-</p><div class="orderedlist"><ol type="1"><li><p>
-make sure that the print spooler is aware of these changes.
-The LPRng system uses the 'lpc reread' command to do this.
-</p></li><li><p>
-make sure that the spool queues, etc., exist and have the
+ testing</P
+></LI
+><LI
+><P
+>pr:sh Same as pr:sh:cm= testing
+ :cm= testing</P
+></LI
+></OL
+></P
+><P
+>Samba reads the printcap information when first started. If you make
+changes in the printcap information, then you must do the following:</P
+><P
+></P
+><OL
+TYPE="1"
+><LI
+><P
+>make sure that the print spooler is aware of these changes.
+The LPRng system uses the 'lpc reread' command to do this.</P
+></LI
+><LI
+><P
+>make sure that the spool queues, etc., exist and have the
correct permissions. The LPRng system uses the 'checkpc -f'
-command to do this.
-</p></li><li><p>
-You now should send a SIGHUP signal to the smbd server to have
-it reread the printcap information.
-</p></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2887691"></a>Job sent, no output</h3></div></div><p>
-This is the most frustrating part of printing. You may have sent the
+command to do this.</P
+></LI
+><LI
+><P
+>You now should send a SIGHUP signal to the smbd server to have
+it reread the printcap information.</P
+></LI
+></OL
+></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN2156">14.4.5. Job sent, no output</H2
+><P
+>This is the most frustrating part of printing. You may have sent the
job, verified that the job was forwarded, set up a wrapper around
-the command to send the file, but there was no output from the printer.
-</p><p>
-First, check to make sure that the job REALLY is getting to the
+the command to send the file, but there was no output from the printer.</P
+><P
+>First, check to make sure that the job REALLY is getting to the
right print queue. If you are using a BSD or LPRng print spooler,
you can temporarily stop the printing of jobs. Jobs can still be
-submitted, but they will not be printed. Use:
-</p><pre class="programlisting">
- lpc -Pprinter stop
-</pre><p>
-Now submit a print job and then use 'lpq -Pprinter' to see if the
+submitted, but they will not be printed. Use:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+> lpc -Pprinter stop</PRE
+></P
+><P
+>Now submit a print job and then use 'lpq -Pprinter' to see if the
job is in the print queue. If it is not in the print queue then
-you will have to find out why it is not being accepted for printing.
-</p><p>
-Next, you may want to check to see what the format of the job really
+you will have to find out why it is not being accepted for printing.</P
+><P
+>Next, you may want to check to see what the format of the job really
was. With the assistance of the system administrator you can view
the submitted jobs files. You may be surprised to find that these
are not in what you would expect to call a printable format.
You can use the UNIX 'file' utitily to determine what the job
-format actually is:
-</p><pre class="programlisting">
- cd /var/spool/lpd/printer # spool directory of print jobs
+format actually is:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+> cd /var/spool/lpd/printer # spool directory of print jobs
ls # find job files
- file dfA001myhost
-</pre><p>
-You should make sure that your printer supports this format OR that
+ file dfA001myhost</PRE
+></P
+><P
+>You should make sure that your printer supports this format OR that
your system administrator has installed a 'print filter' that will
-convert the file to a format appropriate for your printer.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2888240"></a>Job sent, strange output</h3></div></div><p>
-Once you have the job printing, you can then start worrying about
-making it print nicely.
-</p><p>
-The most common problem is extra pages of output: banner pages
-OR blank pages at the end.
-</p><p>
-If you are getting banner pages, check and make sure that the
+convert the file to a format appropriate for your printer.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN2167">14.4.6. Job sent, strange output</H2
+><P
+>Once you have the job printing, you can then start worrying about
+making it print nicely.</P
+><P
+>The most common problem is extra pages of output: banner pages
+OR blank pages at the end.</P
+><P
+>If you are getting banner pages, check and make sure that the
printcap option or printer option is configured for no banners.
If you have a printcap, this is the :sh (suppress header or banner
-page) option. You should have the following in your printer.
-</p><pre class="programlisting">
- printer: ... :sh
-</pre><p>
-If you have this option and are still getting banner pages, there
+page) option. You should have the following in your printer.</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+> printer: ... :sh</PRE
+></P
+><P
+>If you have this option and are still getting banner pages, there
is a strong chance that your printer is generating them for you
automatically. You should make sure that banner printing is disabled
for the printer. This usually requires using the printer setup software
-or procedures supplied by the printer manufacturer.
-</p><p>
-If you get an extra page of output, this could be due to problems
+or procedures supplied by the printer manufacturer.</P
+><P
+>If you get an extra page of output, this could be due to problems
with your job format, or if you are generating PostScript jobs,
incorrect setting on your printer driver on the MicroSoft client.
-For example, under Win95 there is a option:
-</p><pre class="programlisting">
- Printers|Printer Name|(Right Click)Properties|Postscript|Advanced|
-</pre><p>
-that allows you to choose if a Ctrl-D is appended to all jobs.
+For example, under Win95 there is a option:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+> Printers|Printer Name|(Right Click)Properties|Postscript|Advanced|</PRE
+></P
+><P
+>that allows you to choose if a Ctrl-D is appended to all jobs.
This is a very bad thing to do, as most spooling systems will
automatically add a ^D to the end of the job if it is detected as
-PostScript. The multiple ^D may cause an additional page of output.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2888316"></a>Raw PostScript printed</h3></div></div><p>
-This is a problem that is usually caused by either the print spooling
+PostScript. The multiple ^D may cause an additional page of output.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN2179">14.4.7. Raw PostScript printed</H2
+><P
+>This is a problem that is usually caused by either the print spooling
system putting information at the start of the print job that makes
the printer think the job is a text file, or your printer simply
does not support PostScript. You may need to enable 'Automatic
-Format Detection' on your printer.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2888334"></a>Advanced Printing</h3></div></div><p>
-Note that you can do some pretty magic things by using your
-imagination with the &quot;print command&quot; option and some shell scripts.
+Format Detection' on your printer.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN2182">14.4.8. Advanced Printing</H2
+><P
+>Note that you can do some pretty magic things by using your
+imagination with the "print command" option and some shell scripts.
Doing print accounting is easy by passing the %U option to a print
command shell script. You could even make the print command detect
the type of output and its size and send it to an appropriate
-printer.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2888360"></a>Real debugging</h3></div></div><p>
-If the above debug tips don't help, then maybe you need to bring in
-the bug guns, system tracing. See Tracing.txt in this directory.
-</p></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="groupmapping.html">Prev</a></td><td width="20%" align="center"><a accesskey="u" href="optional.html">Up</a></td><td width="40%" align="right"><a accesskey="n" href="CUPS-printing.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter12.Configuring Group Mapping</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">Chapter14.CUPS Printing Support</td></tr></table></div></body></html>
+printer.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN2185">14.4.9. Real debugging</H2
+><P
+>If the above debug tips don't help, then maybe you need to bring in
+the bug guns, system tracing. See Tracing.txt in this directory.</P
+></DIV
+></DIV
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+SUMMARY="Footer navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="msdfs.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="samba-howto-collection.html"
+ACCESSKEY="H"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="winbind.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>Hosting a Microsoft Distributed File System tree on Samba</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="optional.html"
+ACCESSKEY="U"
+>Up</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>Unified Logons between Windows NT and UNIX using Winbind</TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+> \ No newline at end of file
diff --git a/docs/htmldocs/profilemgmt.html b/docs/htmldocs/profilemgmt.html
deleted file mode 100644
index 7357336193..0000000000
--- a/docs/htmldocs/profilemgmt.html
+++ /dev/null
@@ -1,1753 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<HTML
-><HEAD
-><TITLE
->Desktop Profile Management</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
-REL="HOME"
-TITLE="SAMBA Project Documentation"
-HREF="samba-howto-collection.html"><LINK
-REL="UP"
-TITLE="Advanced Configuration"
-HREF="optional.html"><LINK
-REL="PREVIOUS"
-TITLE="System and Account Policies"
-HREF="policymgmt.html"><LINK
-REL="NEXT"
-TITLE="Interdomain Trust Relationships"
-HREF="interdomaintrusts.html"></HEAD
-><BODY
-CLASS="CHAPTER"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->SAMBA Project Documentation</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="policymgmt.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
-></TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="interdomaintrusts.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="CHAPTER"
-><H1
-><A
-NAME="PROFILEMGMT"
-></A
->Chapter 18. Desktop Profile Management</H1
-><DIV
-CLASS="TOC"
-><DL
-><DT
-><B
->Table of Contents</B
-></DT
-><DT
->18.1. <A
-HREF="profilemgmt.html#AEN3095"
->Roaming Profiles</A
-></DT
-><DD
-><DL
-><DT
->18.1.1. <A
-HREF="profilemgmt.html#AEN3102"
->Samba Configuration for Profile Handling</A
-></DT
-><DD
-><DL
-><DT
->18.1.1.1. <A
-HREF="profilemgmt.html#AEN3105"
->NT4/200x User Profiles</A
-></DT
-><DT
->18.1.1.2. <A
-HREF="profilemgmt.html#AEN3115"
->Windows 9x / Me User Profiles</A
-></DT
-><DT
->18.1.1.3. <A
-HREF="profilemgmt.html#AEN3130"
->Mixed Windows 9x / Me and Windows NT4/200x User Profiles</A
-></DT
-></DL
-></DD
-><DT
->18.1.2. <A
-HREF="profilemgmt.html#AEN3137"
->Windows Client Profile Configuration Information</A
-></DT
-><DD
-><DL
-><DT
->18.1.2.1. <A
-HREF="profilemgmt.html#AEN3139"
->Windows 9x / Me Profile Setup</A
-></DT
-><DT
->18.1.2.2. <A
-HREF="profilemgmt.html#AEN3175"
->Windows NT4 Workstation</A
-></DT
-><DT
->18.1.2.3. <A
-HREF="profilemgmt.html#AEN3184"
->Windows 2000/XP Professional</A
-></DT
-></DL
-></DD
-><DT
->18.1.3. <A
-HREF="profilemgmt.html#AEN3257"
->Sharing Profiles between W9x/Me and NT4/200x/XP workstations</A
-></DT
-><DT
->18.1.4. <A
-HREF="profilemgmt.html#AEN3264"
->Profile Migration from Windows NT4/200x Server to Samba</A
-></DT
-><DD
-><DL
-><DT
->18.1.4.1. <A
-HREF="profilemgmt.html#AEN3267"
->Windows NT4 Profile Management Tools</A
-></DT
-><DT
->18.1.4.2. <A
-HREF="profilemgmt.html#AEN3290"
->Side bar Notes</A
-></DT
-><DT
->18.1.4.3. <A
-HREF="profilemgmt.html#AEN3294"
->moveuser.exe</A
-></DT
-><DT
->18.1.4.4. <A
-HREF="profilemgmt.html#AEN3297"
->Get SID</A
-></DT
-></DL
-></DD
-></DL
-></DD
-><DT
->18.2. <A
-HREF="profilemgmt.html#AEN3302"
->Mandatory profiles</A
-></DT
-><DT
->18.3. <A
-HREF="profilemgmt.html#AEN3309"
->Creating/Managing Group Profiles</A
-></DT
-><DT
->18.4. <A
-HREF="profilemgmt.html#AEN3315"
->Default Profile for Windows Users</A
-></DT
-><DD
-><DL
-><DT
->18.4.1. <A
-HREF="profilemgmt.html#AEN3318"
->MS Windows 9x/Me</A
-></DT
-><DT
->18.4.2. <A
-HREF="profilemgmt.html#AEN3330"
->MS Windows NT4 Workstation</A
-></DT
-><DT
->18.4.3. <A
-HREF="profilemgmt.html#AEN3384"
->MS Windows 200x/XP</A
-></DT
-></DL
-></DD
-></DL
-></DIV
-><DIV
-CLASS="SECT1"
-><H1
-CLASS="SECT1"
-><A
-NAME="AEN3095"
->18.1. Roaming Profiles</A
-></H1
-><DIV
-CLASS="WARNING"
-><P
-></P
-><TABLE
-CLASS="WARNING"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/warning.gif"
-HSPACE="5"
-ALT="Warning"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->Roaming profiles support is different for Win9x / Me and Windows NT4/200x.</P
-></TD
-></TR
-></TABLE
-></DIV
-><P
->Before discussing how to configure roaming profiles, it is useful to see how
-Windows 9x / Me and Windows NT4/200x clients implement these features.</P
-><P
->Windows 9x / Me clients send a NetUserGetInfo request to the server to get the user's
-profiles location. However, the response does not have room for a separate
-profiles location field, only the user's home share. This means that Win9X/Me
-profiles are restricted to being stored in the user's home directory.</P
-><P
->Windows NT4/200x clients send a NetSAMLogon RPC request, which contains many fields,
-including a separate field for the location of the user's profiles.</P
-><DIV
-CLASS="SECT2"
-><H2
-CLASS="SECT2"
-><A
-NAME="AEN3102"
->18.1.1. Samba Configuration for Profile Handling</A
-></H2
-><P
->This section documents how to configure Samba for MS Windows client profile support.</P
-><DIV
-CLASS="SECT3"
-><H3
-CLASS="SECT3"
-><A
-NAME="AEN3105"
->18.1.1.1. NT4/200x User Profiles</A
-></H3
-><P
->To support Windowns NT4/200x clients, in the [global] section of smb.conf set the
-following (for example):</P
-><P
-><PRE
-CLASS="PROGRAMLISTING"
-> logon path = \\profileserver\profileshare\profilepath\%U\moreprofilepath</PRE
->
-
- This is typically implemented like:
-
-<PRE
-CLASS="PROGRAMLISTING"
-> logon path = \\%L\Profiles\%u</PRE
->
-where %L translates to the name of the Samba server and %u translates to the user name</P
-><P
->The default for this option is \\%N\%U\profile, namely \\sambaserver\username\profile.
-The \\N%\%U service is created automatically by the [homes] service. If you are using
-a samba server for the profiles, you _must_ make the share specified in the logon path
-browseable. Please refer to the man page for smb.conf in respect of the different
-symantics of %L and %N, as well as %U and %u.</P
-><DIV
-CLASS="NOTE"
-><P
-></P
-><TABLE
-CLASS="NOTE"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->MS Windows NT/2K clients at times do not disconnect a connection to a server
-between logons. It is recommended to NOT use the <B
-CLASS="COMMAND"
->homes</B
->
-meta-service name as part of the profile share path.</P
-></TD
-></TR
-></TABLE
-></DIV
-></DIV
-><DIV
-CLASS="SECT3"
-><H3
-CLASS="SECT3"
-><A
-NAME="AEN3115"
->18.1.1.2. Windows 9x / Me User Profiles</A
-></H3
-><P
->To support Windows 9x / Me clients, you must use the "logon home" parameter. Samba has
-now been fixed so that <KBD
-CLASS="USERINPUT"
->net use /home</KBD
-> now works as well, and it, too, relies
-on the <B
-CLASS="COMMAND"
->logon home</B
-> parameter.</P
-><P
->By using the logon home parameter, you are restricted to putting Win9x / Me
-profiles in the user's home directory. But wait! There is a trick you
-can use. If you set the following in the <B
-CLASS="COMMAND"
->[global]</B
-> section of your <TT
-CLASS="FILENAME"
->smb.conf</TT
-> file:</P
-><P
-><PRE
-CLASS="PROGRAMLISTING"
-> logon home = \\%L\%U\.profiles</PRE
-></P
-><P
->then your Windows 9x / Me clients will dutifully put their clients in a subdirectory
-of your home directory called <TT
-CLASS="FILENAME"
->.profiles</TT
-> (thus making them hidden).</P
-><P
->Not only that, but <KBD
-CLASS="USERINPUT"
->net use/home</KBD
-> will also work, because of a feature in
-Windows 9x / Me. It removes any directory stuff off the end of the home directory area
-and only uses the server and share portion. That is, it looks like you
-specified \\%L\%U for <B
-CLASS="COMMAND"
->logon home</B
->.</P
-></DIV
-><DIV
-CLASS="SECT3"
-><H3
-CLASS="SECT3"
-><A
-NAME="AEN3130"
->18.1.1.3. Mixed Windows 9x / Me and Windows NT4/200x User Profiles</A
-></H3
-><P
->You can support profiles for both Win9X and WinNT clients by setting both the
-<B
-CLASS="COMMAND"
->logon home</B
-> and <B
-CLASS="COMMAND"
->logon path</B
-> parameters. For example:</P
-><P
-><PRE
-CLASS="PROGRAMLISTING"
-> logon home = \\%L\%u\.profiles
- logon path = \\%L\profiles\%u</PRE
-></P
-></DIV
-></DIV
-><DIV
-CLASS="SECT2"
-><H2
-CLASS="SECT2"
-><A
-NAME="AEN3137"
->18.1.2. Windows Client Profile Configuration Information</A
-></H2
-><DIV
-CLASS="SECT3"
-><H3
-CLASS="SECT3"
-><A
-NAME="AEN3139"
->18.1.2.1. Windows 9x / Me Profile Setup</A
-></H3
-><P
->When a user first logs in on Windows 9X, the file user.DAT is created,
-as are folders "Start Menu", "Desktop", "Programs" and "Nethood".
-These directories and their contents will be merged with the local
-versions stored in c:\windows\profiles\username on subsequent logins,
-taking the most recent from each. You will need to use the [global]
-options "preserve case = yes", "short preserve case = yes" and
-"case sensitive = no" in order to maintain capital letters in shortcuts
-in any of the profile folders.</P
-><P
->The user.DAT file contains all the user's preferences. If you wish to
-enforce a set of preferences, rename their user.DAT file to user.MAN,
-and deny them write access to this file.</P
-><P
-></P
-><OL
-TYPE="1"
-><LI
-><P
-> On the Windows 9x / Me machine, go to Control Panel -&#62; Passwords and
- select the User Profiles tab. Select the required level of
- roaming preferences. Press OK, but do _not_ allow the computer
- to reboot.
- </P
-></LI
-><LI
-><P
-> On the Windows 9x / Me machine, go to Control Panel -&#62; Network -&#62;
- Client for Microsoft Networks -&#62; Preferences. Select 'Log on to
- NT Domain'. Then, ensure that the Primary Logon is 'Client for
- Microsoft Networks'. Press OK, and this time allow the computer
- to reboot.
- </P
-></LI
-></OL
-><P
->Under Windows 9x / Me Profiles are downloaded from the Primary Logon.
-If you have the Primary Logon as 'Client for Novell Networks', then
-the profiles and logon script will be downloaded from your Novell
-Server. If you have the Primary Logon as 'Windows Logon', then the
-profiles will be loaded from the local machine - a bit against the
-concept of roaming profiles, it would seem!</P
-><P
->You will now find that the Microsoft Networks Login box contains
-[user, password, domain] instead of just [user, password]. Type in
-the samba server's domain name (or any other domain known to exist,
-but bear in mind that the user will be authenticated against this
-domain and profiles downloaded from it, if that domain logon server
-supports it), user name and user's password.</P
-><P
->Once the user has been successfully validated, the Windows 9x / Me machine
-will inform you that 'The user has not logged on before' and asks you
-if you wish to save the user's preferences? Select 'yes'.</P
-><P
->Once the Windows 9x / Me client comes up with the desktop, you should be able
-to examine the contents of the directory specified in the "logon path"
-on the samba server and verify that the "Desktop", "Start Menu",
-"Programs" and "Nethood" folders have been created.</P
-><P
->These folders will be cached locally on the client, and updated when
-the user logs off (if you haven't made them read-only by then).
-You will find that if the user creates further folders or short-cuts,
-that the client will merge the profile contents downloaded with the
-contents of the profile directory already on the local client, taking
-the newest folders and short-cuts from each set.</P
-><P
->If you have made the folders / files read-only on the samba server,
-then you will get errors from the Windows 9x / Me machine on logon and logout, as
-it attempts to merge the local and the remote profile. Basically, if
-you have any errors reported by the Windows 9x / Me machine, check the Unix file
-permissions and ownership rights on the profile directory contents,
-on the samba server.</P
-><P
->If you have problems creating user profiles, you can reset the user's
-local desktop cache, as shown below. When this user then next logs in,
-they will be told that they are logging in "for the first time".</P
-><P
-></P
-><OL
-TYPE="1"
-><LI
-><P
-> instead of logging in under the [user, password, domain] dialog,
- press escape.
- </P
-></LI
-><LI
-><P
-> run the regedit.exe program, and look in:
- </P
-><P
-> HKEY_LOCAL_MACHINE\Windows\CurrentVersion\ProfileList
- </P
-><P
-> you will find an entry, for each user, of ProfilePath. Note the
- contents of this key (likely to be c:\windows\profiles\username),
- then delete the key ProfilePath for the required user.
-
- [Exit the registry editor].
-
- </P
-></LI
-><LI
-><P
-> <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->WARNING</I
-></SPAN
-> - before deleting the contents of the
- directory listed in the ProfilePath (this is likely to be
- <TT
-CLASS="FILENAME"
->c:\windows\profiles\username)</TT
->, ask them if they
- have any important files stored on their desktop or in their start menu.
- Delete the contents of the directory ProfilePath (making a backup if any
- of the files are needed).
- </P
-><P
-> This will have the effect of removing the local (read-only hidden
- system file) user.DAT in their profile directory, as well as the
- local "desktop", "nethood", "start menu" and "programs" folders.
- </P
-></LI
-><LI
-><P
-> search for the user's .PWL password-caching file in the c:\windows
- directory, and delete it.
- </P
-></LI
-><LI
-><P
-> log off the windows 9x / Me client.
- </P
-></LI
-><LI
-><P
-> check the contents of the profile path (see "logon path" described
- above), and delete the user.DAT or user.MAN file for the user,
- making a backup if required.
- </P
-></LI
-></OL
-><P
->If all else fails, increase samba's debug log levels to between 3 and 10,
-and / or run a packet trace program such as ethereal or netmon.exe, and
-look for error messages.</P
-><P
->If you have access to an Windows NT4/200x server, then first set up roaming profiles
-and / or netlogons on the Windows NT4/200x server. Make a packet trace, or examine
-the example packet traces provided with Windows NT4/200x server, and see what the
-differences are with the equivalent samba trace.</P
-></DIV
-><DIV
-CLASS="SECT3"
-><H3
-CLASS="SECT3"
-><A
-NAME="AEN3175"
->18.1.2.2. Windows NT4 Workstation</A
-></H3
-><P
->When a user first logs in to a Windows NT Workstation, the profile
-NTuser.DAT is created. The profile location can be now specified
-through the "logon path" parameter.</P
-><P
->There is a parameter that is now available for use with NT Profiles:
-"logon drive". This should be set to <TT
-CLASS="FILENAME"
->H:</TT
-> or any other drive, and
-should be used in conjunction with the new "logon home" parameter.</P
-><P
->The entry for the NT4 profile is a _directory_ not a file. The NT
-help on profiles mentions that a directory is also created with a .PDS
-extension. The user, while logging in, must have write permission to
-create the full profile path (and the folder with the .PDS extension
-for those situations where it might be created.)</P
-><P
->In the profile directory, Windows NT4 creates more folders than Windows 9x / Me.
-It creates "Application Data" and others, as well as "Desktop", "Nethood",
-"Start Menu" and "Programs". The profile itself is stored in a file
-NTuser.DAT. Nothing appears to be stored in the .PDS directory, and
-its purpose is currently unknown.</P
-><P
->You can use the System Control Panel to copy a local profile onto
-a samba server (see NT Help on profiles: it is also capable of firing
-up the correct location in the System Control Panel for you). The
-NT Help file also mentions that renaming NTuser.DAT to NTuser.MAN
-turns a profile into a mandatory one.</P
-><P
->The case of the profile is significant. The file must be called
-NTuser.DAT or, for a mandatory profile, NTuser.MAN.</P
-></DIV
-><DIV
-CLASS="SECT3"
-><H3
-CLASS="SECT3"
-><A
-NAME="AEN3184"
->18.1.2.3. Windows 2000/XP Professional</A
-></H3
-><P
->You must first convert the profile from a local profile to a domain
-profile on the MS Windows workstation as follows:</P
-><P
-></P
-><UL
-><LI
-><P
-> Log on as the LOCAL workstation administrator.
- </P
-></LI
-><LI
-><P
-> Right click on the 'My Computer' Icon, select 'Properties'
- </P
-></LI
-><LI
-><P
-> Click on the 'User Profiles' tab
- </P
-></LI
-><LI
-><P
-> Select the profile you wish to convert (click on it once)
- </P
-></LI
-><LI
-><P
-> Click on the button 'Copy To'
- </P
-></LI
-><LI
-><P
-> In the "Permitted to use" box, click on the 'Change' button.
- </P
-></LI
-><LI
-><P
-> Click on the 'Look in" area that lists the machine name, when you click
- here it will open up a selection box. Click on the domain to which the
- profile must be accessible.
- </P
-><DIV
-CLASS="NOTE"
-><P
-></P
-><TABLE
-CLASS="NOTE"
-WIDTH="90%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->You will need to log on if a logon box opens up. Eg: In the connect
- as: MIDEARTH\root, password: mypassword.</P
-></TD
-></TR
-></TABLE
-></DIV
-></LI
-><LI
-><P
-> To make the profile capable of being used by anyone select 'Everyone'
- </P
-></LI
-><LI
-><P
-> Click OK. The Selection box will close.
- </P
-></LI
-><LI
-><P
-> Now click on the 'Ok' button to create the profile in the path you
- nominated.
- </P
-></LI
-></UL
-><P
->Done. You now have a profile that can be editted using the samba-3.0.0
-<TT
-CLASS="FILENAME"
->profiles</TT
-> tool.</P
-><DIV
-CLASS="NOTE"
-><P
-></P
-><TABLE
-CLASS="NOTE"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->Under NT/2K the use of mandotory profiles forces the use of MS Exchange
-storage of mail data. That keeps desktop profiles usable.</P
-></TD
-></TR
-></TABLE
-></DIV
-><DIV
-CLASS="NOTE"
-><P
-></P
-><TABLE
-CLASS="NOTE"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
-></P
-><UL
-><LI
-><P
->This is a security check new to Windows XP (or maybe only
-Windows XP service pack 1). It can be disabled via a group policy in
-Active Directory. The policy is:</P
-><P
->"Computer Configuration\Administrative Templates\System\User
-Profiles\Do not check for user ownership of Roaming Profile Folders"</P
-><P
->...and it should be set to "Enabled".
-Does the new version of samba have an Active Directory analogue? If so,
-then you may be able to set the policy through this.</P
-><P
->If you cannot set group policies in samba, then you may be able to set
-the policy locally on each machine. If you want to try this, then do
-the following (N.B. I don't know for sure that this will work in the
-same way as a domain group policy):</P
-></LI
-><LI
-><P
->On the XP workstation log in with an Administrator account.</P
-></LI
-><LI
-><P
->Click: "Start", "Run"</P
-></LI
-><LI
-><P
->Type: "mmc"</P
-></LI
-><LI
-><P
->Click: "OK"</P
-></LI
-><LI
-><P
->A Microsoft Management Console should appear.</P
-></LI
-><LI
-><P
->Click: File, "Add/Remove Snap-in...", "Add"</P
-></LI
-><LI
-><P
->Double-Click: "Group Policy"</P
-></LI
-><LI
-><P
->Click: "Finish", "Close"</P
-></LI
-><LI
-><P
->Click: "OK"</P
-></LI
-><LI
-><P
->In the "Console Root" window:</P
-></LI
-><LI
-><P
->Expand: "Local Computer Policy", "Computer Configuration",</P
-></LI
-><LI
-><P
->"Administrative Templates", "System", "User Profiles"</P
-></LI
-><LI
-><P
->Double-Click: "Do not check for user ownership of Roaming Profile</P
-></LI
-><LI
-><P
->Folders"</P
-></LI
-><LI
-><P
->Select: "Enabled"</P
-></LI
-><LI
-><P
->Click: OK"</P
-></LI
-><LI
-><P
->Close the whole console. You do not need to save the settings (this
- refers to the console settings rather than the policies you have
- changed).</P
-></LI
-><LI
-><P
->Reboot</P
-></LI
-></UL
-></TD
-></TR
-></TABLE
-></DIV
-></DIV
-></DIV
-><DIV
-CLASS="SECT2"
-><H2
-CLASS="SECT2"
-><A
-NAME="AEN3257"
->18.1.3. Sharing Profiles between W9x/Me and NT4/200x/XP workstations</A
-></H2
-><P
->Sharing of desktop profiles between Windows versions is NOT recommended.
-Desktop profiles are an evolving phenomenon and profiles for later versions
-of MS Windows clients add features that may interfere with earlier versions
-of MS Windows clients. Probably the more salient reason to NOT mix profiles
-is that when logging off an earlier version of MS Windows the older format
-of profile contents may overwrite information that belongs to the newer
-version resulting in loss of profile information content when that user logs
-on again with the newer version of MS Windows.</P
-><P
->If you then want to share the same Start Menu / Desktop with W9x/Me, you will
-need to specify a common location for the profiles. The smb.conf parameters
-that need to be common are <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->logon path</I
-></SPAN
-> and
-<SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->logon home</I
-></SPAN
->.</P
-><P
->If you have this set up correctly, you will find separate user.DAT and
-NTuser.DAT files in the same profile directory.</P
-></DIV
-><DIV
-CLASS="SECT2"
-><H2
-CLASS="SECT2"
-><A
-NAME="AEN3264"
->18.1.4. Profile Migration from Windows NT4/200x Server to Samba</A
-></H2
-><P
->There is nothing to stop you specifying any path that you like for the
-location of users' profiles. Therefore, you could specify that the
-profile be stored on a samba server, or any other SMB server, as long as
-that SMB server supports encrypted passwords.</P
-><DIV
-CLASS="SECT3"
-><H3
-CLASS="SECT3"
-><A
-NAME="AEN3267"
->18.1.4.1. Windows NT4 Profile Management Tools</A
-></H3
-><P
->Unfortunately, the Resource Kit information is specific to the version of MS Windows
-NT4/200x. The correct resource kit is required for each platform.</P
-><P
->Here is a quick guide:</P
-><P
-></P
-><UL
-><LI
-><P
->On your NT4 Domain Controller, right click on 'My Computer', then
-select the tab labelled 'User Profiles'.</P
-></LI
-><LI
-><P
->Select a user profile you want to migrate and click on it.</P
-><DIV
-CLASS="NOTE"
-><P
-></P
-><TABLE
-CLASS="NOTE"
-WIDTH="90%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->I am using the term "migrate" lossely. You can copy a profile to
-create a group profile. You can give the user 'Everyone' rights to the
-profile you copy this to. That is what you need to do, since your samba
-domain is not a member of a trust relationship with your NT4 PDC.</P
-></TD
-></TR
-></TABLE
-></DIV
-></LI
-><LI
-><P
->Click the 'Copy To' button.</P
-></LI
-><LI
-><P
->In the box labelled 'Copy Profile to' add your new path, eg:
- <TT
-CLASS="FILENAME"
->c:\temp\foobar</TT
-></P
-></LI
-><LI
-><P
->Click on the button labelled 'Change' in the "Permitted to use" box.</P
-></LI
-><LI
-><P
->Click on the group 'Everyone' and then click OK. This closes the
- 'chose user' box.</P
-></LI
-><LI
-><P
->Now click OK.</P
-></LI
-></UL
-><P
->Follow the above for every profile you need to migrate.</P
-></DIV
-><DIV
-CLASS="SECT3"
-><H3
-CLASS="SECT3"
-><A
-NAME="AEN3290"
->18.1.4.2. Side bar Notes</A
-></H3
-><P
->You should obtain the SID of your NT4 domain. You can use smbpasswd to do
-this. Read the man page.</P
-><P
->With Samba-3.0.0 alpha code you can import all you NT4 domain accounts
-using the net samsync method. This way you can retain your profile
-settings as well as all your users.</P
-></DIV
-><DIV
-CLASS="SECT3"
-><H3
-CLASS="SECT3"
-><A
-NAME="AEN3294"
->18.1.4.3. moveuser.exe</A
-></H3
-><P
->The W2K professional resource kit has moveuser.exe. moveuser.exe changes
-the security of a profile from one user to another. This allows the account
-domain to change, and/or the user name to change.</P
-></DIV
-><DIV
-CLASS="SECT3"
-><H3
-CLASS="SECT3"
-><A
-NAME="AEN3297"
->18.1.4.4. Get SID</A
-></H3
-><P
->You can identify the SID by using GetSID.exe from the Windows NT Server 4.0
-Resource Kit.</P
-><P
->Windows NT 4.0 stores the local profile information in the registry under
-the following key:
-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList</P
-><P
->Under the ProfileList key, there will be subkeys named with the SIDs of the
-users who have logged on to this computer. (To find the profile information
-for the user whose locally cached profile you want to move, find the SID for
-the user with the GetSID.exe utility.) Inside of the appropriate user's
-subkey, you will see a string value named ProfileImagePath.</P
-></DIV
-></DIV
-></DIV
-><DIV
-CLASS="SECT1"
-><H1
-CLASS="SECT1"
-><A
-NAME="AEN3302"
->18.2. Mandatory profiles</A
-></H1
-><P
->A Mandatory Profile is a profile that the user does NOT have the ability to overwrite.
-During the user's session it may be possible to change the desktop environment, but
-as the user logs out all changes made will be lost. If it is desired to NOT allow the
-user any ability to change the desktop environment then this must be done through
-policy settings. See previous chapter.</P
-><DIV
-CLASS="NOTE"
-><P
-></P
-><TABLE
-CLASS="NOTE"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->Under NO circumstances should the profile directory (or it's contents) be made read-only
-as this may render the profile un-usable.</P
-></TD
-></TR
-></TABLE
-></DIV
-><P
->For MS Windows NT4/200x/XP the above method can be used to create mandatory profiles
-also. To convert a group profile into a mandatory profile simply locate the NTUser.DAT
-file in the copied profile and rename it to NTUser.MAN.</P
-><P
->For MS Windows 9x / Me it is the User.DAT file that must be renamed to User.MAN to
-affect a mandatory profile.</P
-></DIV
-><DIV
-CLASS="SECT1"
-><H1
-CLASS="SECT1"
-><A
-NAME="AEN3309"
->18.3. Creating/Managing Group Profiles</A
-></H1
-><P
->Most organisations are arranged into departments. There is a nice benenfit in
-this fact since usually most users in a department will require the same desktop
-applications and the same desktop layout. MS Windows NT4/200x/XP will allow the
-use of Group Profiles. A Group Profile is a profile that is created firstly using
-a template (example) user. Then using the profile migration tool (see above) the
-profile is assigned access rights for the user group that needs to be given access
-to the group profile.</P
-><P
->The next step is rather important. PLEASE NOTE: Instead of assigning a group profile
-to users (ie: Using User Manager) on a "per user" basis, the group itself is assigned
-the now modified profile.</P
-><DIV
-CLASS="NOTE"
-><P
-></P
-><TABLE
-CLASS="NOTE"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
-> Be careful with group profiles, if the user who is a member of a group also
- has a personal profile, then the result will be a fusion (merge) of the two.
- </P
-></TD
-></TR
-></TABLE
-></DIV
-></DIV
-><DIV
-CLASS="SECT1"
-><H1
-CLASS="SECT1"
-><A
-NAME="AEN3315"
->18.4. Default Profile for Windows Users</A
-></H1
-><P
->MS Windows 9x / Me and NT4/200x/XP will use a default profile for any user for whom
-a profile does not already exist. Armed with a knowledge of where the default profile
-is located on the Windows workstation, and knowing which registry keys affect the path
-from which the default profile is created, it is possible to modify the default profile
-to one that has been optimised for the site. This has significant administrative
-advantages.</P
-><DIV
-CLASS="SECT2"
-><H2
-CLASS="SECT2"
-><A
-NAME="AEN3318"
->18.4.1. MS Windows 9x/Me</A
-></H2
-><P
->To enable default per use profiles in Windows 9x / Me you can either use the Windows 98 System
-Policy Editor or change the registry directly.</P
-><P
->To enable default per user profiles in Windows 9x / Me, launch the System Policy Editor, then
-select File -&#62; Open Registry, then click on the Local Computer icon, click on Windows 98 System,
-select User Profiles, click on the enable box. Do not forget to save the registry changes.</P
-><P
->To modify the registry directly, launch the Registry Editor (regedit.exe), select the hive
-<TT
-CLASS="FILENAME"
->HKEY_LOCAL_MACHINE\Network\Logon</TT
->. Now add a DWORD type key with the name
-"User Profiles", to enable user profiles set the value to 1, to disable user profiles set it to 0.</P
-><DIV
-CLASS="SECT3"
-><H3
-CLASS="SECT3"
-><A
-NAME="AEN3324"
->18.4.1.1. How User Profiles Are Handled in Windows 9x / Me?</A
-></H3
-><P
->When a user logs on to a Windows 9x / Me machine, the local profile path,
-<TT
-CLASS="FILENAME"
->HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\ProfileList</TT
->, is checked
-for an existing entry for that user:</P
-><P
->If the user has an entry in this registry location, Windows 9x / Me checks for a locally cached
-version of the user profile. Windows 9x / Me also checks the user's home directory (or other
-specified directory if the location has been modified) on the server for the User Profile.
-If a profile exists in both locations, the newer of the two is used. If the User Profile exists
-on the server, but does not exist on the local machine, the profile on the server is downloaded
-and used. If the User Profile only exists on the local machine, that copy is used.</P
-><P
->If a User Profile is not found in either location, the Default User Profile from the Windows 9x / Me
-machine is used and is copied to a newly created folder for the logged on user. At log off, any
-changes that the user made are written to the user's local profile. If the user has a roaming
-profile, the changes are written to the user's profile on the server.</P
-></DIV
-></DIV
-><DIV
-CLASS="SECT2"
-><H2
-CLASS="SECT2"
-><A
-NAME="AEN3330"
->18.4.2. MS Windows NT4 Workstation</A
-></H2
-><P
->On MS Windows NT4 the default user profile is obtained from the location
-<TT
-CLASS="FILENAME"
->%SystemRoot%\Profiles</TT
-> which in a default installation will translate to
-<TT
-CLASS="FILENAME"
->C:\WinNT\Profiles</TT
->. Under this directory on a clean install there will be
-three (3) directories: <TT
-CLASS="FILENAME"
->Administrator, All Users, Default User</TT
->.</P
-><P
->The <TT
-CLASS="FILENAME"
->All Users</TT
-> directory contains menu settings that are common across all
-system users. The <TT
-CLASS="FILENAME"
->Default User</TT
-> directory contains menu entries that are
-customisable per user depending on the profile settings chosen/created.</P
-><P
->When a new user first logs onto an MS Windows NT4 machine a new profile is created from:</P
-><P
-></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
->All Users settings</TD
-></TR
-><TR
-><TD
->Default User settings (contains the default NTUser.DAT file)</TD
-></TR
-></TBODY
-></TABLE
-><P
-></P
-><P
->When a user logs onto an MS Windows NT4 machine that is a member of a Microsoft security domain
-the following steps are followed in respect of profile handling:</P
-><P
-></P
-><OL
-TYPE="1"
-><LI
-><P
-> The users' account information which is obtained during the logon process contains
- the location of the users' desktop profile. The profile path may be local to the
- machine or it may be located on a network share. If there exists a profile at the location
- of the path from the user account, then this profile is copied to the location
- <TT
-CLASS="FILENAME"
->%SystemRoot%\Profiles\%USERNAME%</TT
->. This profile then inherits the
- settings in the <TT
-CLASS="FILENAME"
->All Users</TT
-> profile in the <TT
-CLASS="FILENAME"
->%SystemRoot%\Profiles</TT
->
- location.
- </P
-></LI
-><LI
-><P
-> If the user account has a profile path, but at it's location a profile does not exist,
- then a new profile is created in the <TT
-CLASS="FILENAME"
->%SystemRoot%\Profiles\%USERNAME%</TT
->
- directory from reading the <TT
-CLASS="FILENAME"
->Default User</TT
-> profile.
- </P
-></LI
-><LI
-><P
-> If the NETLOGON share on the authenticating server (logon server) contains a policy file
- (<TT
-CLASS="FILENAME"
->NTConfig.POL</TT
->) then it's contents are applied to the <TT
-CLASS="FILENAME"
->NTUser.DAT</TT
->
- which is applied to the <TT
-CLASS="FILENAME"
->HKEY_CURRENT_USER</TT
-> part of the registry.
- </P
-></LI
-><LI
-><P
-> When the user logs out, if the profile is set to be a roaming profile it will be written
- out to the location of the profile. The <TT
-CLASS="FILENAME"
->NTuser.DAT</TT
-> file is then
- re-created from the contents of the <TT
-CLASS="FILENAME"
->HKEY_CURRENT_USER</TT
-> contents.
- Thus, should there not exist in the NETLOGON share an <TT
-CLASS="FILENAME"
->NTConfig.POL</TT
-> at the
- next logon, the effect of the provious <TT
-CLASS="FILENAME"
->NTConfig.POL</TT
-> will still be held
- in the profile. The effect of this is known as <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->tatooing</I
-></SPAN
->.
- </P
-></LI
-></OL
-><P
->MS Windows NT4 profiles may be <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->Local</I
-></SPAN
-> or <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->Roaming</I
-></SPAN
->. A Local profile
-will stored in the <TT
-CLASS="FILENAME"
->%SystemRoot%\Profiles\%USERNAME%</TT
-> location. A roaming profile will
-also remain stored in the same way, unless the following registry key is created:</P
-><P
-><PRE
-CLASS="PROGRAMLISTING"
-> HKEY_LOCAL_MACHINE\SYSTEM\Software\Microsoft\Windows NT\CurrentVersion\winlogon\
- "DeleteRoamingCache"=dword:00000001</PRE
->
-
-In which case, the local copy (in <TT
-CLASS="FILENAME"
->%SystemRoot%\Profiles\%USERNAME%</TT
->) will be
-deleted on logout.</P
-><P
->Under MS Windows NT4 default locations for common resources (like <TT
-CLASS="FILENAME"
->My Documents</TT
->
-may be redirected to a network share by modifying the following registry keys. These changes may be affected
-via use of the System Policy Editor (to do so may require that you create your owns template extension
-for the policy editor to allow this to be done through the GUI. Another way to do this is by way of first
-creating a default user profile, then while logged in as that user, run regedt32 to edit the key settings.</P
-><P
->The Registry Hive key that affects the behaviour of folders that are part of the default user profile
-are controlled by entries on Windows NT4 is:</P
-><P
-><PRE
-CLASS="PROGRAMLISTING"
-> HKEY_CURRENT_USER
- \Software
- \Microsoft
- \Windows
- \CurrentVersion
- \Explorer
- \User Shell Folders\</PRE
-></P
-><P
->The above hive key contains a list of automatically managed folders. The default entries are:</P
-><P
-> <PRE
-CLASS="PROGRAMLISTING"
-> Name Default Value
- -------------- -----------------------------------------
- AppData %USERPROFILE%\Application Data
- Desktop %USERPROFILE%\Desktop
- Favorites %USERPROFILE%\Favorites
- NetHood %USERPROFILE%\NetHood
- PrintHood %USERPROFILE%\PrintHood
- Programs %USERPROFILE%\Start Menu\Programs
- Recent %USERPROFILE%\Recent
- SendTo %USERPROFILE%\SendTo
- Start Menu %USERPROFILE%\Start Menu
- Startup %USERPROFILE%\Start Menu\Programs\Startup
- </PRE
->
- </P
-><P
->The registry key that contains the location of the default profile settings is:
-
-<PRE
-CLASS="PROGRAMLISTING"
-> HKEY_LOCAL_MACHINE
- \SOFTWARE
- \Microsoft
- \Windows
- \CurrentVersion
- \Explorer
- \User Shell Folders</PRE
->
-
-The default entries are:
-
-<PRE
-CLASS="PROGRAMLISTING"
-> Common Desktop %SystemRoot%\Profiles\All Users\Desktop
- Common Programs %SystemRoot%\Profiles\All Users\Programs
- Common Start Menu %SystemRoot%\Profiles\All Users\Start Menu
- Common Startu p %SystemRoot%\Profiles\All Users\Start Menu\Progams\Startup</PRE
-></P
-></DIV
-><DIV
-CLASS="SECT2"
-><H2
-CLASS="SECT2"
-><A
-NAME="AEN3384"
->18.4.3. MS Windows 200x/XP</A
-></H2
-><DIV
-CLASS="NOTE"
-><P
-></P
-><TABLE
-CLASS="NOTE"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
-> MS Windows XP Home Edition does use default per user profiles, but can not participate
- in domain security, can not log onto an NT/ADS style domain, and thus can obtain the profile
- only from itself. While there are benefits in doing this the beauty of those MS Windows
- clients that CAN participate in domain logon processes allows the administrator to create
- a global default profile and to enforce it through the use of Group Policy Objects (GPOs).
- </P
-></TD
-></TR
-></TABLE
-></DIV
-><P
->When a new user first logs onto MS Windows 200x/XP machine the default profile is obtained from
-<TT
-CLASS="FILENAME"
->C:\Documents and Settings\Default User</TT
->. The administrator can modify (or change
-the contents of this location and MS Windows 200x/XP will gladly user it. This is far from the optimum
-arrangement since it will involve copying a new default profile to every MS Windows 200x/XP client
-workstation. </P
-><P
->When MS Windows 200x/XP participate in a domain security context, and if the default user
-profile is not found, then the client will search for a default profile in the NETLOGON share
-of the authenticating server. ie: In MS Windows parlance:
-<TT
-CLASS="FILENAME"
->%LOGONSERVER%\NETLOGON\Default User</TT
-> and if one exits there it will copy this
-to the workstation to the <TT
-CLASS="FILENAME"
->C:\Documents and Settings\</TT
-> under the Windows
-login name of the user.</P
-><DIV
-CLASS="NOTE"
-><P
-></P
-><TABLE
-CLASS="NOTE"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
-> This path translates, in Samba parlance, to the smb.conf [NETLOGON] share. The directory
- should be created at the root of this share and msut be called <TT
-CLASS="FILENAME"
->Default Profile</TT
->.
- </P
-></TD
-></TR
-></TABLE
-></DIV
-><P
->If a default profile does not exist in this location then MS Windows 200x/XP will use the local
-default profile.</P
-><P
->On loging out, the users' desktop profile will be stored to the location specified in the registry
-settings that pertain to the user. If no specific policies have been created, or passed to the client
-during the login process (as Samba does automatically), then the user's profile will be written to
-the local machine only under the path <TT
-CLASS="FILENAME"
->C:\Documents and Settings\%USERNAME%</TT
->.</P
-><P
->Those wishing to modify the default behaviour can do so through up to three methods:</P
-><P
-></P
-><UL
-><LI
-><P
-> Modify the registry keys on the local machine manually and place the new default profile in the
- NETLOGON share root - NOT recommended as it is maintenance intensive.
- </P
-></LI
-><LI
-><P
-> Create an NT4 style NTConfig.POL file that specified this behaviour and locate this file
- in the root of the NETLOGON share along with the new default profile.
- </P
-></LI
-><LI
-><P
-> Create a GPO that enforces this through Active Directory, and place the new default profile
- in the NETLOGON share.
- </P
-></LI
-></UL
-><P
->The Registry Hive key that affects the behaviour of folders that are part of the default user profile
-are controlled by entries on Windows 200x/XP is:</P
-><P
-><PRE
-CLASS="PROGRAMLISTING"
-> HKEY_CURRENT_USER
- \Software
- \Microsoft
- \Windows
- \CurrentVersion
- \Explorer
- \User Shell Folders\</PRE
-></P
-><P
->The above hive key contains a list of automatically managed folders. The default entries are:</P
-><P
-> <PRE
-CLASS="PROGRAMLISTING"
-> Name Default Value
- -------------- -----------------------------------------
- AppData %USERPROFILE%\Application Data
- Cache %USERPROFILE%\Local Settings\Temporary Internet Files
- Cookies %USERPROFILE%\Cookies
- Desktop %USERPROFILE%\Desktop
- Favorites %USERPROFILE%\Favorites
- History %USERPROFILE%\Local Settings\History
- Local AppData %USERPROFILE%\Local Settings\Application Data
- Local Settings %USERPROFILE%\Local Settings
- My Pictures %USERPROFILE%\My Documents\My Pictures
- NetHood %USERPROFILE%\NetHood
- Personal %USERPROFILE%\My Documents
- PrintHood %USERPROFILE%\PrintHood
- Programs %USERPROFILE%\Start Menu\Programs
- Recent %USERPROFILE%\Recent
- SendTo %USERPROFILE%\SendTo
- Start Menu %USERPROFILE%\Start Menu
- Startup %USERPROFILE%\Start Menu\Programs\Startup
- Templates %USERPROFILE%\Templates
- </PRE
->
- </P
-><P
->There is also an entry called "Default" that has no value set. The default entry is of type REG_SZ, all
-the others are of type REG_EXPAND_SZ.</P
-><P
->It makes a huge difference to the speed of handling roaming user profiles if all the folders are
-stored on a dedicated location on a network server. This means that it will NOT be necessary to
-write Outlook PST file over the network for every login and logout.</P
-><P
->To set this to a network location you could use the following examples:
-
-<PRE
-CLASS="PROGRAMLISTING"
-> %LOGONSERVER%\%USERNAME%\Default Folders</PRE
->
-
-This would store the folders in the user's home directory under a directory called "Default Folders"
-
-You could also use:
-
-<PRE
-CLASS="PROGRAMLISTING"
-> \\SambaServer\FolderShare\%USERNAME%</PRE
->
-
-in which case the default folders will be stored in the server named <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->SambaServer</I
-></SPAN
->
-in the share called <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->FolderShare</I
-></SPAN
-> under a directory that has the name of the MS Windows
-user as seen by the Linux/Unix file system.</P
-><P
->Please note that once you have created a default profile share, you MUST migrate a user's profile
-(default or custom) to it.</P
-><P
->MS Windows 200x/XP profiles may be <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->Local</I
-></SPAN
-> or <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->Roaming</I
-></SPAN
->.
-A roaming profile will be cached locally unless the following registry key is created:</P
-><P
-><PRE
-CLASS="PROGRAMLISTING"
-> HKEY_LOCAL_MACHINE\SYSTEM\Software\Microsoft\Windows NT\CurrentVersion\winlogon\
- "DeleteRoamingCache"=dword:00000001</PRE
->
-
-In which case, the local cache copy will be deleted on logout.</P
-></DIV
-></DIV
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="policymgmt.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="samba-howto-collection.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="interdomaintrusts.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->System and Account Policies</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="optional.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Interdomain Trust Relationships</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
-> \ No newline at end of file
diff --git a/docs/htmldocs/pwencrypt.html b/docs/htmldocs/pwencrypt.html
new file mode 100644
index 0000000000..9414399bf4
--- /dev/null
+++ b/docs/htmldocs/pwencrypt.html
@@ -0,0 +1,434 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<HTML
+><HEAD
+><TITLE
+>LanMan and NT Password Encryption in Samba</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
+REL="HOME"
+TITLE="SAMBA Project Documentation"
+HREF="samba-howto-collection.html"><LINK
+REL="UP"
+TITLE="General installation"
+HREF="introduction.html"><LINK
+REL="PREVIOUS"
+TITLE="Quick Cross Subnet Browsing / Cross Workgroup Browsing guide"
+HREF="browsing-quick.html"><LINK
+REL="NEXT"
+TITLE="Type of installation"
+HREF="type.html"></HEAD
+><BODY
+CLASS="CHAPTER"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><TABLE
+SUMMARY="Header navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>SAMBA Project Documentation</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="browsing-quick.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+></TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="type.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="CHAPTER"
+><H1
+><A
+NAME="PWENCRYPT">Chapter 4. LanMan and NT Password Encryption in Samba</H1
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN457">4.1. Introduction</H1
+><P
+>Newer windows clients send encrypted passwords over
+ the wire, instead of plain text passwords. The newest clients
+ will only send encrypted passwords and refuse to send plain text
+ passwords, unless their registry is tweaked.</P
+><P
+>These passwords can't be converted to unix style encrypted
+ passwords. Because of that you can't use the standard unix
+ user database, and you have to store the Lanman and NT hashes
+ somewhere else. For more information, see the documentation
+ about the <B
+CLASS="COMMAND"
+>passdb backend = </B
+> parameter.
+ </P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN462">4.2. Important Notes About Security</H1
+><P
+>The unix and SMB password encryption techniques seem similar
+ on the surface. This similarity is, however, only skin deep. The unix
+ scheme typically sends clear text passwords over the network when
+ logging in. This is bad. The SMB encryption scheme never sends the
+ cleartext password over the network but it does store the 16 byte
+ hashed values on disk. This is also bad. Why? Because the 16 byte hashed
+ values are a "password equivalent". You cannot derive the user's
+ password from them, but they could potentially be used in a modified
+ client to gain access to a server. This would require considerable
+ technical knowledge on behalf of the attacker but is perfectly possible.
+ You should thus treat the smbpasswd file as though it contained the
+ cleartext passwords of all your users. Its contents must be kept
+ secret, and the file should be protected accordingly.</P
+><P
+>Ideally we would like a password scheme which neither requires
+ plain text passwords on the net or on disk. Unfortunately this
+ is not available as Samba is stuck with being compatible with
+ other SMB systems (WinNT, WfWg, Win95 etc). </P
+><DIV
+CLASS="WARNING"
+><P
+></P
+><TABLE
+CLASS="WARNING"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/warning.gif"
+HSPACE="5"
+ALT="Warning"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+>Note that Windows NT 4.0 Service pack 3 changed the
+ default for permissible authentication so that plaintext
+ passwords are <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>never</I
+></SPAN
+> sent over the wire.
+ The solution to this is either to switch to encrypted passwords
+ with Samba or edit the Windows NT registry to re-enable plaintext
+ passwords. See the document WinNT.txt for details on how to do
+ this.</P
+><P
+>Other Microsoft operating systems which also exhibit
+ this behavior includes</P
+><P
+></P
+><UL
+><LI
+><P
+>MS DOS Network client 3.0 with
+ the basic network redirector installed</P
+></LI
+><LI
+><P
+>Windows 95 with the network redirector
+ update installed</P
+></LI
+><LI
+><P
+>Windows 98 [se]</P
+></LI
+><LI
+><P
+>Windows 2000</P
+></LI
+></UL
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Note :</I
+></SPAN
+>All current release of
+ Microsoft SMB/CIFS clients support authentication via the
+ SMB Challenge/Response mechanism described here. Enabling
+ clear text authentication does not disable the ability
+ of the client to participate in encrypted authentication.</P
+></TD
+></TR
+></TABLE
+></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN481">4.2.1. Advantages of SMB Encryption</H2
+><P
+></P
+><UL
+><LI
+><P
+>plain text passwords are not passed across
+ the network. Someone using a network sniffer cannot just
+ record passwords going to the SMB server.</P
+></LI
+><LI
+><P
+>WinNT doesn't like talking to a server
+ that isn't using SMB encrypted passwords. It will refuse
+ to browse the server if the server is also in user level
+ security mode. It will insist on prompting the user for the
+ password on each connection, which is very annoying. The
+ only things you can do to stop this is to use SMB encryption.
+ </P
+></LI
+></UL
+></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN488">4.2.2. Advantages of non-encrypted passwords</H2
+><P
+></P
+><UL
+><LI
+><P
+>plain text passwords are not kept
+ on disk. </P
+></LI
+><LI
+><P
+>uses same password file as other unix
+ services such as login and ftp</P
+></LI
+><LI
+><P
+>you are probably already using other
+ services (such as telnet and ftp) which send plain text
+ passwords over the net, so sending them for SMB isn't
+ such a big deal.</P
+></LI
+></UL
+></DIV
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN497">4.3. The smbpasswd Command</H1
+><P
+>The smbpasswd command maintains the two 32 byte password fields
+ in the smbpasswd file. If you wish to make it similar to the unix
+ <B
+CLASS="COMMAND"
+>passwd</B
+> or <B
+CLASS="COMMAND"
+>yppasswd</B
+> programs,
+ install it in <TT
+CLASS="FILENAME"
+>/usr/local/samba/bin/</TT
+> (or your
+ main Samba binary directory).</P
+><P
+><B
+CLASS="COMMAND"
+>smbpasswd</B
+> now works in a client-server mode
+ where it contacts the local smbd to change the user's password on its
+ behalf. This has enormous benefits - as follows.</P
+><P
+><B
+CLASS="COMMAND"
+>smbpasswd</B
+> now has the capability
+ to change passwords on Windows NT servers (this only works when
+ the request is sent to the NT Primary Domain Controller if you
+ are changing an NT Domain user's password).</P
+><P
+>To run smbpasswd as a normal user just type :</P
+><P
+><TT
+CLASS="PROMPT"
+>$ </TT
+><TT
+CLASS="USERINPUT"
+><B
+>smbpasswd</B
+></TT
+></P
+><P
+><TT
+CLASS="PROMPT"
+>Old SMB password: </TT
+><TT
+CLASS="USERINPUT"
+><B
+>&lt;type old value here -
+ or hit return if there was no old password&gt;</B
+></TT
+></P
+><P
+><TT
+CLASS="PROMPT"
+>New SMB Password: </TT
+><TT
+CLASS="USERINPUT"
+><B
+>&lt;type new value&gt;
+ </B
+></TT
+></P
+><P
+><TT
+CLASS="PROMPT"
+>Repeat New SMB Password: </TT
+><TT
+CLASS="USERINPUT"
+><B
+>&lt;re-type new value
+ </B
+></TT
+></P
+><P
+>If the old value does not match the current value stored for
+ that user, or the two new values do not match each other, then the
+ password will not be changed.</P
+><P
+>If invoked by an ordinary user it will only allow the user
+ to change his or her own Samba password.</P
+><P
+>If run by the root user smbpasswd may take an optional
+ argument, specifying the user name whose SMB password you wish to
+ change. Note that when run as root smbpasswd does not prompt for
+ or check the old password value, thus allowing root to set passwords
+ for users who have forgotten their passwords.</P
+><P
+><B
+CLASS="COMMAND"
+>smbpasswd</B
+> is designed to work in the same way
+ and be familiar to UNIX users who use the <B
+CLASS="COMMAND"
+>passwd</B
+> or
+ <B
+CLASS="COMMAND"
+>yppasswd</B
+> commands.</P
+><P
+>For more details on using <B
+CLASS="COMMAND"
+>smbpasswd</B
+> refer
+ to the man page which will always be the definitive reference.</P
+></DIV
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+SUMMARY="Footer navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="browsing-quick.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="samba-howto-collection.html"
+ACCESSKEY="H"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="type.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>Quick Cross Subnet Browsing / Cross Workgroup Browsing guide</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="introduction.html"
+ACCESSKEY="U"
+>Up</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>Type of installation</TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+> \ No newline at end of file
diff --git a/docs/htmldocs/rpcclient.1.html b/docs/htmldocs/rpcclient.1.html
index ed351b0096..e695663c8a 100644
--- a/docs/htmldocs/rpcclient.1.html
+++ b/docs/htmldocs/rpcclient.1.html
@@ -1,198 +1,781 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>rpcclient</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="rpcclient.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>rpcclient &#8212; tool for executing client side
- MS-RPC functions</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><tt>rpcclient</tt> [-A authfile] [-c &lt;command string&gt;] [-d debuglevel] [-h] [-l logfile] [-N] [-s &lt;smb config file&gt;] [-U username[%password]] [-W workgroup] [-N] [-I destinationIP] {server}</p></div></div><div class="refsect1" lang="en"><h2>DESCRIPTION</h2><p>This tool is part of the <a href="Samba.7.html">Samba(7)</a> suite.</p><p><b>rpcclient</b> is a utility initially developed
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<HTML
+><HEAD
+><TITLE
+>rpcclient</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.77"></HEAD
+><BODY
+CLASS="REFENTRY"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><H1
+><A
+NAME="RPCCLIENT"
+></A
+>rpcclient</H1
+><DIV
+CLASS="REFNAMEDIV"
+><A
+NAME="AEN5"
+></A
+><H2
+>Name</H2
+>rpcclient&nbsp;--&nbsp;tool for executing client side
+ MS-RPC functions</DIV
+><DIV
+CLASS="REFSYNOPSISDIV"
+><A
+NAME="AEN8"
+></A
+><H2
+>Synopsis</H2
+><P
+><B
+CLASS="COMMAND"
+>rpcclient</B
+> [-A authfile] [-c &lt;command string&gt;] [-d debuglevel] [-h] [-l logfile] [-N] [-s &lt;smb config file&gt;] [-U username[%password]] [-W workgroup] [-N] [-I destinationIP] {server}</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN23"
+></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"
+>rpcclient</B
+> is a utility initially developed
to test MS-RPC functionality in Samba itself. It has undergone
several stages of development and stability. Many system administrators
have now written scripts around it to manage Windows NT clients from
- their UNIX workstation. </p></div><div class="refsect1" lang="en"><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">server</span></dt><dd><p>NetBIOS name of Server to which to connect.
+ their UNIX workstation. </P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN29"
+></A
+><H2
+>OPTIONS</H2
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>server</DT
+><DD
+><P
+>NetBIOS name of Server to which to connect.
The server can be any SMB/CIFS server. The name is
- resolved using the <a href="smb.conf.5.html#NAMERESOLVEORDER" target="_top">
- <i><tt>name resolve order</tt></i></a> line from <a href="smb.conf.5.html">smb.conf(5)</a>.</p></dd><dt><span class="term">-c|--command='command string'</span></dt><dd><p>execute semicolon separated commands (listed
- below)) </p></dd><dt><span class="term">-I IP-address</span></dt><dd><p><i><tt>IP address</tt></i> is the address of the server to connect to.
- It should be specified in standard &quot;a.b.c.d&quot; notation. </p><p>Normally the client would attempt to locate a named
- SMB/CIFS server by looking it up via the NetBIOS name resolution
- mechanism described above in the <i><tt>name resolve order</tt></i>
- parameter above. Using this parameter will force the client
- to assume that the server is on the machine with the specified IP
- address and the NetBIOS name component of the resource being
- connected to will be ignored. </p><p>There is no default for this parameter. If not supplied,
- it will be determined automatically by the client as described
- above. </p></dd><dt><span class="term">-V</span></dt><dd><p>Prints the version number for
-<b>smbd</b>.</p></dd><dt><span class="term">-s &lt;configuration file&gt;</span></dt><dd><p>The file specified contains the
-configuration details required by the server. The
-information in this file includes server-specific
-information such as what printcap file to use, as well
-as descriptions of all the services that the server is
-to provide. See <a href="smb.conf.5.html" target="_top"><tt>
-smb.conf(5)</tt></a> for more information.
-The default configuration file name is determined at
-compile time.</p></dd><dt><span class="term">-d|--debug=debuglevel</span></dt><dd><p><i><tt>debuglevel</tt></i> is an integer
+ resolved using the <A
+HREF="smb.conf.5.html#NAMERESOLVEORDER"
+TARGET="_top"
+> <TT
+CLASS="PARAMETER"
+><I
+>name resolve order</I
+></TT
+></A
+> line from
+ <TT
+CLASS="FILENAME"
+>smb.conf(5)</TT
+>.</P
+></DD
+><DT
+>-A|--authfile=filename</DT
+><DD
+><P
+>This option allows
+ you to specify a file from which to read the username and
+ password used in the connection. The format of the file is
+ </P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+> username = &lt;value&gt;
+ password = &lt;value&gt;
+ domain = &lt;value&gt;
+ </PRE
+></P
+><P
+>Make certain that the permissions on the file restrict
+ access from unwanted users. </P
+></DD
+><DT
+>-c|--command='command string'</DT
+><DD
+><P
+>execute semicolon separated commands (listed
+ below)) </P
+></DD
+><DT
+>-d|--debug=debuglevel</DT
+><DD
+><P
+><TT
+CLASS="REPLACEABLE"
+><I
+>debuglevel</I
+></TT
+> is an integer
from 0 to 10. The default value if this parameter is
-not specified is zero.</p><p>The higher this value, the more detail will be
+not specified is zero.</P
+><P
+>The higher this value, the more detail will be
logged to the log files about the activities of the
server. At level 0, only critical errors and serious
warnings will be logged. Level 1 is a reasonable level for
day to day running - it generates a small amount of
-information about operations carried out.</p><p>Levels above 1 will generate considerable
+information about operations carried out.</P
+><P
+>Levels above 1 will generate considerable
amounts of log data, and should only be used when
investigating a problem. Levels above 3 are designed for
use only by developers and generate HUGE amounts of log
-data, most of which is extremely cryptic.</p><p>Note that specifying this parameter here will
-override the <a href="smb.conf.5.html#loglevel" target="_top">log
-level</a> parameter in the <a href="smb.conf.5.html" target="_top">
-<tt>smb.conf(5)</tt></a> file.</p></dd><dt><span class="term">-l|--logfile=logbasename</span></dt><dd><p>File name for log/debug files. The extension
-<tt>&quot;.client&quot;</tt> will be appended. The log file is
-never removed by the client.
-</p></dd><dt><span class="term">-N</span></dt><dd><p>If specified, this parameter suppresses the normal
-password prompt from the client to the user. This is useful when
-accessing a service that does not require a password. </p><p>Unless a password is specified on the command line or
-this parameter is specified, the client will request a
-password.</p></dd><dt><span class="term">-k</span></dt><dd><p>
-Try to authenticate with kerberos. Only useful in
-an Active Directory environment.
-</p></dd><dt><span class="term">-A|--authfile=filename</span></dt><dd><p>This option allows
-you to specify a file from which to read the username and
-password used in the connection. The format of the file is
-</p><pre class="programlisting">
-username = &lt;value&gt;
-password = &lt;value&gt;
-domain = &lt;value&gt;
-</pre><p>Make certain that the permissions on the file restrict
-access from unwanted users. </p></dd><dt><span class="term">-U|--user=username[%password]</span></dt><dd><p>Sets the SMB username or username and password. </p><p>If %password is not specified, the user will be prompted. The
-client will first check the <tt>USER</tt> environment variable, then the
-<tt>LOGNAME</tt> variable and if either exists, the
-string is uppercased. If these environmental variables are not
-found, the username <tt>GUEST</tt> is used. </p><p>A third option is to use a credentials file which
-contains the plaintext of the username and password. This
-option is mainly provided for scripts where the admin does not
-wish to pass the credentials on the command line or via environment
-variables. If this method is used, make certain that the permissions
-on the file restrict access from unwanted users. See the
-<i><tt>-A</tt></i> for more details. </p><p>Be cautious about including passwords in scripts. Also, on
-many systems the command line of a running process may be seen
-via the <b>ps</b> command. To be safe always allow
-<b>rpcclient</b> to prompt for a password and type
-it in directly. </p></dd><dt><span class="term">-n &lt;primary NetBIOS name&gt;</span></dt><dd><p>This option allows you to override
-the NetBIOS name that Samba uses for itself. This is identical
-to setting the <a href="smb.conf.5.html#netbiosname" target="_top"><i><tt>NetBIOS
-name</tt></i></a> parameter in the <a href="smb.conf.5.html">smb.conf(5)</a> file. However, a command
-line setting will take precedence over settings in
-<a href="smb.conf.5.html">smb.conf(5)</a>.</p></dd><dt><span class="term">-i &lt;scope&gt;</span></dt><dd><p>This specifies a NetBIOS scope that
-<b>nmblookup</b> will use to communicate with when
-generating NetBIOS names. For details on the use of NetBIOS
-scopes, see rfc1001.txt and rfc1002.txt. NetBIOS scopes are
-<span class="emphasis"><em>very</em></span> rarely used, only set this parameter
-if you are the system administrator in charge of all the
-NetBIOS systems you communicate with.</p></dd><dt><span class="term">-W|--workgroup=domain</span></dt><dd><p>Set the SMB domain of the username. This
-overrides the default domain which is the domain defined in
-smb.conf. If the domain specified is the same as the servers
-NetBIOS name, it causes the client to log on using the servers local
-SAM (as opposed to the Domain SAM). </p></dd><dt><span class="term">-O socket options</span></dt><dd><p>TCP socket options to set on the client
-socket. See the socket options parameter in
-the <a href="smb.conf.5.html">smb.conf(5)</a> manual page for the list of valid
-options. </p></dd><dt><span class="term">-h|--help</span></dt><dd><p>Print a summary of command line options.
-</p></dd></dl></div></div><div class="refsect1" lang="en"><h2>COMMANDS</h2><div class="refsect2" lang="en"><h3>LSARPC</h3><div class="variablelist"><dl><dt><span class="term">lsaquery</span></dt><dd><p>Query info policy</p></dd><dt><span class="term">lookupsids</span></dt><dd><p>Resolve a list
+data, most of which is extremely cryptic.</P
+><P
+>Note that specifying this parameter here will
+override the <A
+HREF="smb.conf.5.html#loglevel"
+TARGET="_top"
+>log
+level</A
+> parameter in the <A
+HREF="smb.conf.5.html"
+TARGET="_top"
+><TT
+CLASS="FILENAME"
+>smb.conf(5)</TT
+></A
+> file.</P
+></DD
+><DT
+>-h|--help</DT
+><DD
+><P
+>Print a summary of command line options.</P
+></DD
+><DT
+>-I IP-address</DT
+><DD
+><P
+><TT
+CLASS="REPLACEABLE"
+><I
+>IP address</I
+></TT
+> is the address of the server to connect to.
+ It should be specified in standard "a.b.c.d" notation. </P
+><P
+>Normally the client would attempt to locate a named
+ SMB/CIFS server by looking it up via the NetBIOS name resolution
+ mechanism described above in the <TT
+CLASS="PARAMETER"
+><I
+>name resolve order</I
+></TT
+>
+ parameter above. Using this parameter will force the client
+ to assume that the server is on the machine with the specified IP
+ address and the NetBIOS name component of the resource being
+ connected to will be ignored. </P
+><P
+>There is no default for this parameter. If not supplied,
+ it will be determined automatically by the client as described
+ above. </P
+></DD
+><DT
+>-l|--logfile=logbasename</DT
+><DD
+><P
+>File name for log/debug files. The extension
+ <TT
+CLASS="CONSTANT"
+>'.client'</TT
+> will be appended. The log file is
+ never removed by the client.
+ </P
+></DD
+><DT
+>-N|--nopass</DT
+><DD
+><P
+>instruct <B
+CLASS="COMMAND"
+>rpcclient</B
+> not to ask
+ for a password. By default, <B
+CLASS="COMMAND"
+>rpcclient</B
+> will
+ prompt for a password. See also the <TT
+CLASS="PARAMETER"
+><I
+>-U</I
+></TT
+>
+ option.</P
+></DD
+><DT
+>-s|--conf=smb.conf</DT
+><DD
+><P
+>Specifies the location of the all-important
+ <TT
+CLASS="FILENAME"
+>smb.conf</TT
+> file. </P
+></DD
+><DT
+>-U|--user=username[%password]</DT
+><DD
+><P
+>Sets the SMB username or username and password. </P
+><P
+>If %password is not specified, the user will be prompted. The
+ client will first check the <TT
+CLASS="ENVAR"
+>USER</TT
+> environment variable, then the
+ <TT
+CLASS="ENVAR"
+>LOGNAME</TT
+> variable and if either exists, the
+ string is uppercased. If these environmental variables are not
+ found, the username <TT
+CLASS="CONSTANT"
+>GUEST</TT
+> is used. </P
+><P
+>A third option is to use a credentials file which
+ contains the plaintext of the username and password. This
+ option is mainly provided for scripts where the admin does not
+ wish to pass the credentials on the command line or via environment
+ variables. If this method is used, make certain that the permissions
+ on the file restrict access from unwanted users. See the
+ <TT
+CLASS="PARAMETER"
+><I
+>-A</I
+></TT
+> for more details. </P
+><P
+>Be cautious about including passwords in scripts. Also, on
+ many systems the command line of a running process may be seen
+ via the <B
+CLASS="COMMAND"
+>ps</B
+> command. To be safe always allow
+ <B
+CLASS="COMMAND"
+>rpcclient</B
+> to prompt for a password and type
+ it in directly. </P
+></DD
+><DT
+>-W|--workgroup=domain</DT
+><DD
+><P
+>Set the SMB domain of the username. This
+ overrides the default domain which is the domain defined in
+ smb.conf. If the domain specified is the same as the 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
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN107"
+></A
+><H2
+>COMMANDS</H2
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>LSARPC</I
+></SPAN
+></P
+><P
+></P
+><UL
+><LI
+><P
+><B
+CLASS="COMMAND"
+>lsaquery</B
+></P
+></LI
+><LI
+><P
+><B
+CLASS="COMMAND"
+>lookupsids</B
+> - Resolve a list
of SIDs to usernames.
- </p></dd><dt><span class="term">lookupnames</span></dt><dd><p>Resolve a list
+ </P
+></LI
+><LI
+><P
+><B
+CLASS="COMMAND"
+>lookupnames</B
+> - Resolve a list
of usernames to SIDs.
- </p></dd><dt><span class="term">enumtrusts</span></dt><dd><p>Enumerate trusted domains</p></dd><dt><span class="term">enumprivs</span></dt><dd><p>Enumerate privileges</p></dd><dt><span class="term">getdispname</span></dt><dd><p>Get the privilege name</p></dd><dt><span class="term">lsaenumsid</span></dt><dd><p>Enumerate the LSA SIDS</p></dd><dt><span class="term">lsaenumprivsaccount</span></dt><dd><p>Enumerate the privileges of an SID</p></dd><dt><span class="term">lsaenumacctrights</span></dt><dd><p>Enumerate the rights of an SID</p></dd><dt><span class="term">lsaenumacctwithright</span></dt><dd><p>Enumerate accounts with a right</p></dd><dt><span class="term">lsaaddacctrights</span></dt><dd><p>Add rights to an account</p></dd><dt><span class="term">lsaremoveacctrights</span></dt><dd><p>Remove rights from an account</p></dd><dt><span class="term">lsalookupprivvalue</span></dt><dd><p>Get a privilege value given its name</p></dd><dt><span class="term">lsaquerysecobj</span></dt><dd><p>Query LSA security object</p></dd></dl></div></div><div class="refsect2" lang="en"><h3>LSARPC-DS</h3><div class="variablelist"><dl><dt><span class="term">dsroledominfo</span></dt><dd><p>Get Primary Domain Information</p></dd></dl></div><p> </p><p><span class="emphasis"><em>DFS</em></span></p><div class="variablelist"><dl><dt><span class="term">dfsexist</span></dt><dd><p>Query DFS support</p></dd><dt><span class="term">dfsadd</span></dt><dd><p>Add a DFS share</p></dd><dt><span class="term">dfsremove</span></dt><dd><p>Remove a DFS share</p></dd><dt><span class="term">dfsgetinfo</span></dt><dd><p>Query DFS share info</p></dd><dt><span class="term">dfsenum</span></dt><dd><p>Enumerate dfs shares</p></dd></dl></div></div><div class="refsect2" lang="en"><h3>REG</h3><div class="variablelist"><dl><dt><span class="term">shutdown</span></dt><dd><p>Remote Shutdown</p></dd><dt><span class="term">abortshutdown</span></dt><dd><p>Abort Shutdown</p></dd></dl></div></div><div class="refsect2" lang="en"><h3>SRVSVC</h3><div class="variablelist"><dl><dt><span class="term">srvinfo</span></dt><dd><p>Server query info</p></dd><dt><span class="term">netshareenum</span></dt><dd><p>Enumerate shares</p></dd><dt><span class="term">netfileenum</span></dt><dd><p>Enumerate open files</p></dd><dt><span class="term">netremotetod</span></dt><dd><p>Fetch remote time of day</p></dd></dl></div></div><div class="refsect2" lang="en"><h3>SAMR</h3><div class="variablelist"><dl><dt><span class="term">queryuser</span></dt><dd><p>Query user info</p></dd><dt><span class="term">querygroup</span></dt><dd><p>Query group info</p></dd><dt><span class="term">queryusergroups</span></dt><dd><p>Query user groups</p></dd><dt><span class="term">querygroupmem</span></dt><dd><p>Query group membership</p></dd><dt><span class="term">queryaliasmem</span></dt><dd><p>Query alias membership</p></dd><dt><span class="term">querydispinfo</span></dt><dd><p>Query display info</p></dd><dt><span class="term">querydominfo</span></dt><dd><p>Query domain info</p></dd><dt><span class="term">enumdomusers</span></dt><dd><p>Enumerate domain users</p></dd><dt><span class="term">enumdomgroups</span></dt><dd><p>Enumerate domain groups</p></dd><dt><span class="term">enumalsgroups</span></dt><dd><p>Enumerate alias groups</p></dd><dt><span class="term">createdomuser</span></dt><dd><p>Create domain user</p></dd><dt><span class="term">samlookupnames</span></dt><dd><p>Look up names</p></dd><dt><span class="term">samlookuprids</span></dt><dd><p>Look up names</p></dd><dt><span class="term">deletedomuser</span></dt><dd><p>Delete domain user</p></dd><dt><span class="term">samquerysecobj</span></dt><dd><p>Query SAMR security object</p></dd><dt><span class="term">getdompwinfo</span></dt><dd><p>Retrieve domain password info</p></dd><dt><span class="term">lookupdomain</span></dt><dd><p>Look up domain</p></dd></dl></div></div><div class="refsect2" lang="en"><h3>SPOOLSS</h3><div class="variablelist"><dl><dt><span class="term">adddriver &lt;arch&gt; &lt;config&gt;</span></dt><dd><p>
- Execute an AddPrinterDriver() RPC to install the printer driver
+ </P
+></LI
+><LI
+><P
+><B
+CLASS="COMMAND"
+>enumtrusts</B
+></P
+></LI
+></UL
+><P
+> </P
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>SAMR</I
+></SPAN
+></P
+><P
+></P
+><UL
+><LI
+><P
+><B
+CLASS="COMMAND"
+>queryuser</B
+></P
+></LI
+><LI
+><P
+><B
+CLASS="COMMAND"
+>querygroup</B
+></P
+></LI
+><LI
+><P
+><B
+CLASS="COMMAND"
+>queryusergroups</B
+></P
+></LI
+><LI
+><P
+><B
+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
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>SPOOLSS</I
+></SPAN
+></P
+><P
+></P
+><UL
+><LI
+><P
+><B
+CLASS="COMMAND"
+>adddriver &lt;arch&gt; &lt;config&gt;</B
+>
+ - Execute an AddPrinterDriver() RPC to install the printer driver
information on the server. Note that the driver files should
already exist in the directory returned by
- <b>getdriverdir</b>. Possible values for
- <i><tt>arch</tt></i> are the same as those for
- the <b>getdriverdir</b> command.
- The <i><tt>config</tt></i> parameter is defined as
- follows: </p><pre class="programlisting">
-Long Printer Name:\
-Driver File Name:\
-Data File Name:\
-Config File Name:\
-Help File Name:\
-Language Monitor Name:\
-Default Data Type:\
-Comma Separated list of Files
-</pre><p>Any empty fields should be enter as the string &quot;NULL&quot;. </p><p>Samba does not need to support the concept of Print Monitors
+ <B
+CLASS="COMMAND"
+>getdriverdir</B
+>. Possible values for
+ <TT
+CLASS="PARAMETER"
+><I
+>arch</I
+></TT
+> are the same as those for
+ the <B
+CLASS="COMMAND"
+>getdriverdir</B
+> command.
+ The <TT
+CLASS="PARAMETER"
+><I
+>config</I
+></TT
+> parameter is defined as
+ follows: </P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+> Long Printer Name:\
+ Driver File Name:\
+ Data File Name:\
+ Config File Name:\
+ Help File Name:\
+ Language Monitor Name:\
+ Default Data Type:\
+ Comma Separated list of Files
+ </PRE
+></P
+><P
+>Any empty fields should be enter as the string "NULL". </P
+><P
+>Samba does not need to support the concept of Print Monitors
since these only apply to local printers whose driver can make
use of a bi-directional link for communication. This field should
- be &quot;NULL&quot;. On a remote NT print server, the Print Monitor for a
+ be "NULL". On a remote NT print server, the Print Monitor for a
driver must already be installed prior to adding the driver or
- else the RPC will fail. </p></dd><dt><span class="term">addprinter &lt;printername&gt;
- &lt;sharename&gt; &lt;drivername&gt; &lt;port&gt;</span></dt><dd><p>
- Add a printer on the remote server. This printer
+ else the RPC will fail. </P
+></LI
+><LI
+><P
+><B
+CLASS="COMMAND"
+>addprinter &lt;printername&gt;
+ &lt;sharename&gt; &lt;drivername&gt; &lt;port&gt;</B
+>
+ - Add a printer on the remote server. This printer
will be automatically shared. Be aware that the printer driver
- must already be installed on the server (see <b>adddriver</b>)
- and the <i><tt>port</tt></i>must be a valid port name (see
- <b>enumports</b>.</p></dd><dt><span class="term">deldriver</span></dt><dd><p>Delete the
+ must already be installed on the server (see <B
+CLASS="COMMAND"
+>adddriver</B
+>)
+ and the <TT
+CLASS="PARAMETER"
+><I
+>port</I
+></TT
+>must be a valid port name (see
+ <B
+CLASS="COMMAND"
+>enumports</B
+>.</P
+></LI
+><LI
+><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></dd><dt><span class="term">enumdata</span></dt><dd><p>Enumerate all
+ </P
+></LI
+><LI
+><P
+><B
+CLASS="COMMAND"
+>enumdata</B
+> - Enumerate all
printer setting data stored on the server. On Windows NT clients,
these values are stored in the registry, while Samba servers
store them in the printers TDB. This command corresponds
to the MS Platform SDK GetPrinterData() function (* This
- command is currently unimplemented).</p></dd><dt><span class="term">enumdataex</span></dt><dd><p>Enumerate printer data for a key</p></dd><dt><span class="term">enumjobs &lt;printer&gt;</span></dt><dd><p>List the jobs and status of a given printer.
+ command is currently unimplemented).</P
+></LI
+><LI
+><P
+><B
+CLASS="COMMAND"
+>enumjobs &lt;printer&gt;</B
+>
+ - List the jobs and status of a given printer.
This command corresponds to the MS Platform SDK EnumJobs()
- function</p></dd><dt><span class="term">enumkey</span></dt><dd><p>Enumerate
- printer keys</p></dd><dt><span class="term">enumports [level]</span></dt><dd><p>
- Executes an EnumPorts() call using the specified
+ function (* This command is currently unimplemented).</P
+></LI
+><LI
+><P
+><B
+CLASS="COMMAND"
+>enumports [level]</B
+>
+ - Executes an EnumPorts() call using the specified
info level. Currently only info levels 1 and 2 are supported.
- </p></dd><dt><span class="term">enumdrivers [level]</span></dt><dd><p>
- Execute an EnumPrinterDrivers() call. This lists the various installed
+ </P
+></LI
+><LI
+><P
+><B
+CLASS="COMMAND"
+>enumdrivers [level]</B
+>
+ - Execute an EnumPrinterDrivers() call. This lists the various installed
printer drivers for all architectures. Refer to the MS Platform SDK
documentation for more details of the various flags and calling
- options. Currently supported info levels are 1, 2, and 3.</p></dd><dt><span class="term">enumprinters [level]</span></dt><dd><p>Execute an EnumPrinters() call. This lists the various installed
+ options. Currently supported info levels are 1, 2, and 3.</P
+></LI
+><LI
+><P
+><B
+CLASS="COMMAND"
+>enumprinters [level]</B
+>
+ - Execute an EnumPrinters() call. This lists the various installed
and share printers. Refer to the MS Platform SDK documentation for
more details of the various flags and calling options. Currently
- supported info levels are 0, 1, and 2.</p></dd><dt><span class="term">getdata &lt;printername&gt; &lt;valuename;&gt;</span></dt><dd><p>Retrieve the data for a given printer setting. See
- the <b>enumdata</b> command for more information.
+ supported info levels are 0, 1, and 2.</P
+></LI
+><LI
+><P
+><B
+CLASS="COMMAND"
+>getdata &lt;printername&gt;</B
+>
+ - Retrieve the data for a given printer setting. See
+ the <B
+CLASS="COMMAND"
+>enumdata</B
+> command for more information.
This command corresponds to the GetPrinterData() MS Platform
- SDK function. </p></dd><dt><span class="term">getdataex</span></dt><dd><p>Get
- printer driver data with
- keyname</p></dd><dt><span class="term">getdriver &lt;printername&gt;</span></dt><dd><p>
- Retrieve the printer driver information (such as driver file,
+ SDK function (* This command is currently unimplemented). </P
+></LI
+><LI
+><P
+><B
+CLASS="COMMAND"
+>getdriver &lt;printername&gt;</B
+>
+ - Retrieve the printer driver information (such as driver file,
config file, dependent files, etc...) for
the given printer. This command corresponds to the GetPrinterDriver()
MS Platform SDK function. Currently info level 1, 2, and 3 are supported.
- </p></dd><dt><span class="term">getdriverdir &lt;arch&gt;</span></dt><dd><p>
- Execute a GetPrinterDriverDirectory()
+ </P
+></LI
+><LI
+><P
+><B
+CLASS="COMMAND"
+>getdriverdir &lt;arch&gt;</B
+>
+ - Execute a GetPrinterDriverDirectory()
RPC to retrieve the SMB share name and subdirectory for
storing printer driver files for a given architecture. Possible
- values for <i><tt>arch</tt></i> are &quot;Windows 4.0&quot;
- (for Windows 95/98), &quot;Windows NT x86&quot;, &quot;Windows NT PowerPC&quot;, &quot;Windows
- Alpha_AXP&quot;, and &quot;Windows NT R4000&quot;. </p></dd><dt><span class="term">getprinter &lt;printername&gt;</span></dt><dd><p>Retrieve the current printer information. This command
+ values for <TT
+CLASS="PARAMETER"
+><I
+>arch</I
+></TT
+> are "Windows 4.0"
+ (for Windows 95/98), "Windows NT x86", "Windows NT PowerPC", "Windows
+ Alpha_AXP", and "Windows NT R4000". </P
+></LI
+><LI
+><P
+><B
+CLASS="COMMAND"
+>getprinter &lt;printername&gt;</B
+>
+ - Retrieve the current printer information. This command
corresponds to the GetPrinter() MS Platform SDK function.
- </p></dd><dt><span class="term">getprintprocdir</span></dt><dd><p>Get
- print processor
- directory</p></dd><dt><span class="term">openprinter &lt;printername&gt;</span></dt><dd><p>Execute an OpenPrinterEx() and ClosePrinter() RPC
- against a given printer. </p></dd><dt><span class="term">setdriver &lt;printername&gt;
- &lt;drivername&gt;</span></dt><dd><p>Execute a SetPrinter() command to update the printer driver
+ </P
+></LI
+><LI
+><P
+><B
+CLASS="COMMAND"
+>openprinter &lt;printername&gt;</B
+>
+ - Execute an OpenPrinterEx() and ClosePrinter() RPC
+ against a given printer. </P
+></LI
+><LI
+><P
+><B
+CLASS="COMMAND"
+>setdriver &lt;printername&gt;
+ &lt;drivername&gt;</B
+>
+ - Execute a SetPrinter() command to update the printer driver
associated with an installed printer. The printer driver must
- already be correctly installed on the print server. </p><p>See also the <b>enumprinters</b> and
- <b>enumdrivers</b> commands for obtaining a list of
- of installed printers and drivers.</p></dd><dt><span class="term">addform</span></dt><dd><p>Add form</p></dd><dt><span class="term">setform</span></dt><dd><p>Set form</p></dd><dt><span class="term">getform</span></dt><dd><p>Get form</p></dd><dt><span class="term">deleteform</span></dt><dd><p>Delete form</p></dd><dt><span class="term">enumforms</span></dt><dd><p>Enumerate form</p></dd><dt><span class="term">setprinter</span></dt><dd><p>Set printer comment</p></dd><dt><span class="term">setprinterdata</span></dt><dd><p>Set REG_SZ printer data</p></dd><dt><span class="term">rffpcnex</span></dt><dd><p>Rffpcnex test</p></dd></dl></div></div><div class="refsect2" lang="en"><h3>NETLOGON</h3><div class="variablelist"><dl><dt><span class="term">logonctrl2</span></dt><dd><p>Logon Control 2</p></dd><dt><span class="term">logonctrl</span></dt><dd><p>Logon Control</p></dd><dt><span class="term">samsync</span></dt><dd><p>Sam Synchronisation</p></dd><dt><span class="term">samdeltas</span></dt><dd><p>Query Sam Deltas</p></dd><dt><span class="term">samlogon</span></dt><dd><p>Sam Logon</p></dd></dl></div></div><div class="refsect2" lang="en"><h3>GENERAL COMMANDS</h3><div class="variablelist"><dl><dt><span class="term">debuglevel</span></dt><dd><p>Set the current
- debug level used to log information.</p></dd><dt><span class="term">help (?)</span></dt><dd><p>Print a listing of all
+ already be correctly installed on the print server. </P
+><P
+>See also the <B
+CLASS="COMMAND"
+>enumprinters</B
+> and
+ <B
+CLASS="COMMAND"
+>enumdrivers</B
+> commands for obtaining a list of
+ of installed printers and drivers.</P
+></LI
+></UL
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>GENERAL OPTIONS</I
+></SPAN
+></P
+><P
+></P
+><UL
+><LI
+><P
+><B
+CLASS="COMMAND"
+>debuglevel</B
+> - Set the current
+ debug level used to log information.</P
+></LI
+><LI
+><P
+><B
+CLASS="COMMAND"
+>help (?)</B
+> - Print a listing of all
known commands or extended help on a particular command.
- </p></dd><dt><span class="term">quit (exit)</span></dt><dd><p>Exit <b>rpcclient
- </b>.</p></dd></dl></div></div></div><div class="refsect1" lang="en"><h2>BUGS</h2><p><b>rpcclient</b> is designed as a developer testing tool
+ </P
+></LI
+><LI
+><P
+><B
+CLASS="COMMAND"
+>quit (exit)</B
+> - Exit <B
+CLASS="COMMAND"
+>rpcclient
+ </B
+>.</P
+></LI
+></UL
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN227"
+></A
+><H2
+>BUGS</H2
+><P
+><B
+CLASS="COMMAND"
+>rpcclient</B
+> is designed as a developer testing tool
and may not be robust in certain areas (such as command line parsing).
It has been known to generate a core dump upon failures when invalid
- parameters where passed to the interpreter. </p><p>From Luke Leighton's original rpcclient man page:</p><p><span class="emphasis"><em>WARNING!</em></span> The MSRPC over SMB code has
+ parameters where passed to the interpreter. </P
+><P
+>From Luke Leighton's original rpcclient man page:</P
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>"WARNING!</I
+></SPAN
+> The MSRPC over SMB code has
been developed from examining Network traces. No documentation is
available from the original creators (Microsoft) on how MSRPC over
SMB works, or how the individual MSRPC services work. Microsoft's
implementation of these services has been demonstrated (and reported)
- to be... a bit flaky in places. </p><p>The development of Samba's implementation is also a bit rough,
- and as more of the services are understood, it can even result in
- versions of <a href="smbd.8.html">smbd(8)</a> and <a href="rpcclient.1.html">rpcclient(1)</a> that are incompatible for some commands or services. Additionally,
+ to be... a bit flaky in places. </P
+><P
+>The development of Samba's implementation is also a bit rough,
+ and as more of the services are understood, it can even result in
+ versions of <B
+CLASS="COMMAND"
+>smbd(8)</B
+> and <B
+CLASS="COMMAND"
+>rpcclient(1)</B
+>
+ that are incompatible for some commands or services. Additionally,
the developers are sending reports to Microsoft, and problems found
or reported to Microsoft are fixed in Service Packs, which may
- result in incompatibilities.</p></div><div class="refsect1" lang="en"><h2>VERSION</h2><p>This man page is correct for version 3.0 of the Samba
- suite.</p></div><div class="refsect1" lang="en"><h2>AUTHOR</h2><p>The original Samba software and related utilities
+ result in incompatibilities." </P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN237"
+></A
+><H2
+>VERSION</H2
+><P
+>This man page is correct for version 3.0 of the Samba
+ suite.</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN240"
+></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 rpcclient man page was written by Matthew
+ to the way the Linux kernel is developed.</P
+><P
+>The original rpcclient man page was written by Matthew
Geddes, Luke Kenneth Casson Leighton, and rewritten by Gerald Carter.
The conversion to DocBook for Samba 2.2 was done by Gerald
- Carter. The conversion to DocBook XML 4.2 for Samba 3.0 was
- done by Alexander Bokovoy.</p></div></div></body></html>
+ Carter.</P
+></DIV
+></BODY
+></HTML
+> \ No newline at end of file
diff --git a/docs/htmldocs/samba-bdc.html b/docs/htmldocs/samba-bdc.html
index 0a8a8fa2e1..ef06a89416 100644
--- a/docs/htmldocs/samba-bdc.html
+++ b/docs/htmldocs/samba-bdc.html
@@ -1,27 +1,111 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter6.
-Samba Backup Domain Controller to Samba Domain Control
-</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"><link rel="home" href="index.html" title="SAMBA Project Documentation"><link rel="up" href="type.html" title="PartII.Server Configuration Basics"><link rel="previous" href="samba-pdc.html" title="Chapter5.
-Samba as an NT4 or Win2k Primary Domain Controller
-"><link rel="next" href="ADS.html" title="Chapter7.Samba as a ADS domain member"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter6.
-Samba Backup Domain Controller to Samba Domain Control
-</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="samba-pdc.html">Prev</a></td><th width="60%" align="center">PartII.Server Configuration Basics</th><td width="20%" align="right"><a accesskey="n" href="ADS.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="samba-bdc"></a>Chapter6.
-Samba Backup Domain Controller to Samba Domain Control
-</h2></div><div><div class="author"><h3 class="author">Volker Lendecke</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt>&lt;<a href="mailto:Volker.Lendecke@SerNet.DE">Volker.Lendecke@SerNet.DE</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate"> (26 Apr 2001) </p></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="samba-bdc.html#id2807541">Prerequisite Reading</a></dt><dt><a href="samba-bdc.html#id2877190">Background</a></dt><dt><a href="samba-bdc.html#id2879061">What qualifies a Domain Controller on the network?</a></dt><dd><dl><dt><a href="samba-bdc.html#id2879083">How does a Workstation find its domain controller?</a></dt><dt><a href="samba-bdc.html#id2879107">When is the PDC needed?</a></dt></dl></dd><dt><a href="samba-bdc.html#id2879127">Can Samba be a Backup Domain Controller to an NT PDC?</a></dt><dt><a href="samba-bdc.html#id2879160">How do I set up a Samba BDC?</a></dt><dd><dl><dt><a href="samba-bdc.html#id2879257">How do I replicate the smbpasswd file?</a></dt><dt><a href="samba-bdc.html#id2879286">Can I do this all with LDAP?</a></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2807541"></a>Prerequisite Reading</h2></div></div><p>
-Before you continue reading in this chapter, please make sure
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<HTML
+><HEAD
+><TITLE
+>How to Act as a Backup Domain Controller in a Purely Samba Controlled Domain</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
+REL="HOME"
+TITLE="SAMBA Project Documentation"
+HREF="samba-howto-collection.html"><LINK
+REL="UP"
+TITLE="Type of installation"
+HREF="type.html"><LINK
+REL="PREVIOUS"
+TITLE="How to Configure Samba as a NT4 Primary Domain Controller"
+HREF="samba-pdc.html"><LINK
+REL="NEXT"
+TITLE="Samba as a ADS domain member"
+HREF="ads.html"></HEAD
+><BODY
+CLASS="CHAPTER"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><TABLE
+SUMMARY="Header navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>SAMBA Project Documentation</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="samba-pdc.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+></TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="ads.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="CHAPTER"
+><H1
+><A
+NAME="SAMBA-BDC">Chapter 7. How to Act as a Backup Domain Controller in a Purely Samba Controlled Domain</H1
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN1127">7.1. Prerequisite Reading</H1
+><P
+>Before you continue reading in this chapter, please make sure
that you are comfortable with configuring a Samba PDC
-as described in the <a href="Samba-PDC-HOWTO.html" target="_top">Samba-PDC-HOWTO</a>.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2877190"></a>Background</h2></div></div><p>
-What is a Domain Controller? It is a machine that is able to answer
+as described in the <A
+HREF="Samba-PDC-HOWTO.html"
+TARGET="_top"
+>Samba-PDC-HOWTO</A
+>.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN1131">7.2. Background</H1
+><P
+>What is a Domain Controller? It is a machine that is able to answer
logon requests from workstations in a Windows NT Domain. Whenever a
user logs into a Windows NT Workstation, the workstation connects to a
Domain Controller and asks him whether the username and password the
user typed in is correct. The Domain Controller replies with a lot of
information about the user, for example the place where the users
profile is stored, the users full name of the user. All this
-information is stored in the NT user database, the so-called SAM.
-</p><p>
-There are two kinds of Domain Controller in a NT 4 compatible Domain:
+information is stored in the NT user database, the so-called SAM.</P
+><P
+>There are two kinds of Domain Controller in a NT 4 compatible Domain:
A Primary Domain Controller (PDC) and one or more Backup Domain
Controllers (BDC). The PDC contains the master copy of the
SAM. Whenever the SAM has to change, for example when a user changes
@@ -30,31 +114,47 @@ Controller is a machine that maintains a read-only copy of the
SAM. This way it is able to reply to logon requests and authenticate
users in case the PDC is not available. During this time no changes to
the SAM are possible. Whenever changes to the SAM are done on the PDC,
-all BDC receive the changes from the PDC.
-</p><p>
-Since version 2.2 Samba officially supports domain logons for all
+all BDC receive the changes from the PDC.</P
+><P
+>Since version 2.2 Samba officially supports domain logons for all
current Windows Clients, including Windows 2000 and XP. This text
assumes the domain to be named SAMBA. To be able to act as a PDC, some
-parameters in the [global]-section of the smb.conf have to be set:
-</p><pre class="programlisting">
- workgroup = SAMBA
- domain master = yes
- domain logons = yes
-</pre><p>
-Several other things like a [homes] and a [netlogon] share also may be
+parameters in the [global]-section of the smb.conf have to be set:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>workgroup = SAMBA
+domain master = yes
+domain logons = yes</PRE
+></P
+><P
+>Several other things like a [homes] and a [netlogon] share also may be
set along with settings for the profile path, the users home drive and
-others. This will not be covered in this document.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2879061"></a>What qualifies a Domain Controller on the network?</h2></div></div><p>
-Every machine that is a Domain Controller for the domain SAMBA has to
+others. This will not be covered in this document.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN1139">7.3. What qualifies a Domain Controller on the network?</H1
+><P
+>Every machine that is a Domain Controller for the domain SAMBA has to
register the NetBIOS group name SAMBA#1c with the WINS server and/or
by broadcast on the local network. The PDC also registers the unique
NetBIOS name SAMBA#1b with the WINS server. The name type #1b is
normally reserved for the domain master browser, a role that has
nothing to do with anything related to authentication, but the
Microsoft Domain implementation requires the domain master browser to
-be on the same machine as the PDC.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2879083"></a>How does a Workstation find its domain controller?</h3></div></div><p>
-A NT workstation in the domain SAMBA that wants a local user to be
+be on the same machine as the PDC.</P
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN1142">7.3.1. How does a Workstation find its domain controller?</H2
+><P
+>A NT workstation in the domain SAMBA that wants a local user to be
authenticated has to find the domain controller for SAMBA. It does
this by doing a NetBIOS name query for the group name SAMBA#1c. It
assumes that each of the machines it gets back from the queries is a
@@ -62,87 +162,187 @@ domain controller and can answer logon requests. To not open security
holes both the workstation and the selected (TODO: How is the DC
chosen) domain controller authenticate each other. After that the
workstation sends the user's credentials (his name and password) to
-the domain controller, asking for approval.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2879107"></a>When is the PDC needed?</h3></div></div><p>
-Whenever a user wants to change his password, this has to be done on
+the domain controller, asking for approval.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN1145">7.3.2. When is the PDC needed?</H2
+><P
+>Whenever a user wants to change his password, this has to be done on
the PDC. To find the PDC, the workstation does a NetBIOS name query
for SAMBA#1b, assuming this machine maintains the master copy of the
SAM. The workstation contacts the PDC, both mutually authenticate and
-the password change is done.
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2879127"></a>Can Samba be a Backup Domain Controller to an NT PDC?</h2></div></div><p>
-With version 2.2, no. The native NT SAM replication protocols have
+the password change is done.</P
+></DIV
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN1148">7.4. Can Samba be a Backup Domain Controller?</H1
+><P
+>With version 2.2, no. The native NT SAM replication protocols have
not yet been fully implemented. The Samba Team is working on
understanding and implementing the protocols, but this work has not
-been finished for version 2.2.
-</p><p>
-With version 3.0, the work on both the replication protocols and a
-suitable storage mechanism has progressed, and some form of NT4 BDC
-support is expected soon.
-</p><p>
-Can I get the benefits of a BDC with Samba? Yes. The main reason for
+been finished for version 2.2.</P
+><P
+>Can I get the benefits of a BDC with Samba? Yes. The main reason for
implementing a BDC is availability. If the PDC is a Samba machine,
a second Samba machine can be set up to
-service logon requests whenever the PDC is down.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2879160"></a>How do I set up a Samba BDC?</h2></div></div><p>
-Several things have to be done:
-</p><div class="itemizedlist"><ul type="disc"><li><p>
-The domain SID has to be the same on the PDC and the BDC. This used to
+service logon requests whenever the PDC is down.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN1152">7.5. How do I set up a Samba BDC?</H1
+><P
+>Several things have to be done:</P
+><P
+></P
+><UL
+><LI
+><P
+>The domain SID has to be the same on the PDC and the BDC. This used to
be stored in the file private/MACHINE.SID. This file is not created
anymore since Samba 2.2.5 or even earlier. Nowadays the domain SID is
stored in the file private/secrets.tdb. Simply copying the secrets.tdb
from the PDC to the BDC does not work, as the BDC would
generate a new SID for itself and override the domain SID with this
-new BDC SID.</p><p>
-To retrieve the domain SID from the PDC or an existing BDC and store it in the
-secrets.tdb, execute 'net rpc getsid' on the BDC.
-</p></li><li><p>
-The Unix user database has to be synchronized from the PDC to the
+new BDC SID.</P
+><P
+>To retrieve the domain SID from the PDC or an existing BDC and store it in the
+secrets.tdb, execute 'net rpc getsid' on the BDC.</P
+></LI
+><LI
+><P
+>The Unix user database has to be synchronized from the PDC to the
BDC. This means that both the /etc/passwd and /etc/group have to be
replicated from the PDC to the BDC. This can be done manually
whenever changes are made, or the PDC is set up as a NIS master
server and the BDC as a NIS slave server. To set up the BDC as a
mere NIS client would not be enough, as the BDC would not be able to
-access its user database in case of a PDC failure.
-</p></li><li><p>
-The Samba password database in the file private/smbpasswd has to be
+access its user database in case of a PDC failure.</P
+></LI
+><LI
+><P
+>The Samba password database in the file private/smbpasswd has to be
replicated from the PDC to the BDC. This is a bit tricky, see the
-next section.
-</p></li><li><p>
-Any netlogon share has to be replicated from the PDC to the
+next section.</P
+></LI
+><LI
+><P
+>Any netlogon share has to be replicated from the PDC to the
BDC. This can be done manually whenever login scripts are changed,
or it can be done automatically together with the smbpasswd
-synchronization.
-</p></li></ul></div><p>
-Finally, the BDC has to be found by the workstations. This can be done
-by setting
-</p><pre class="programlisting">
- workgroup = samba
- domain master = no
- domain logons = yes
-</pre><p>
-in the [global]-section of the smb.conf of the BDC. This makes the BDC
+synchronization.</P
+></LI
+></UL
+><P
+>Finally, the BDC has to be found by the workstations. This can be done
+by setting</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>workgroup = samba
+domain master = no
+domain logons = yes</PRE
+></P
+><P
+>in the [global]-section of the smb.conf of the BDC. This makes the BDC
only register the name SAMBA#1c with the WINS server. This is no
problem as the name SAMBA#1c is a NetBIOS group name that is meant to
be registered by more than one machine. The parameter 'domain master =
no' forces the BDC not to register SAMBA#1b which as a unique NetBIOS
-name is reserved for the Primary Domain Controller.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2879257"></a>How do I replicate the smbpasswd file?</h3></div></div><p>
-Replication of the smbpasswd file is sensitive. It has to be done
+name is reserved for the Primary Domain Controller.</P
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN1169">7.5.1. How do I replicate the smbpasswd file?</H2
+><P
+>Replication of the smbpasswd file is sensitive. It has to be done
whenever changes to the SAM are made. Every user's password change is
done in the smbpasswd file and has to be replicated to the BDC. So
-replicating the smbpasswd file very often is necessary.
-</p><p>
-As the smbpasswd file contains plain text password equivalents, it
+replicating the smbpasswd file very often is necessary.</P
+><P
+>As the smbpasswd file contains plain text password equivalents, it
must not be sent unencrypted over the wire. The best way to set up
smbpasswd replication from the PDC to the BDC is to use the utility
rsync. rsync can use ssh as a transport. ssh itself can be set up to
accept *only* rsync transfer without requiring the user to type a
-password.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2879286"></a>Can I do this all with LDAP?</h3></div></div><p>The simple answer is YES. Samba's pdb_ldap code supports
-binding to a replica LDAP server, and will also follow referrals and
-rebind to the master if it ever needs to make a modification to the
-database. (Normally BDCs are read only, so this will not occur
-often).
-</p></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="samba-pdc.html">Prev</a></td><td width="20%" align="center"><a accesskey="u" href="type.html">Up</a></td><td width="40%" align="right"><a accesskey="n" href="ADS.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter5.
-Samba as an NT4 or Win2k Primary Domain Controller
-</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">Chapter7.Samba as a ADS domain member</td></tr></table></div></body></html>
+password.</P
+></DIV
+></DIV
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+SUMMARY="Footer navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="samba-pdc.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="samba-howto-collection.html"
+ACCESSKEY="H"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="ads.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>How to Configure Samba as a NT4 Primary Domain Controller</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="type.html"
+ACCESSKEY="U"
+>Up</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>Samba as a ADS domain member</TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+> \ No newline at end of file
diff --git a/docs/htmldocs/samba-howto-collection.html b/docs/htmldocs/samba-howto-collection.html
index 3d2a95873e..0062e257dc 100644
--- a/docs/htmldocs/samba-howto-collection.html
+++ b/docs/htmldocs/samba-howto-collection.html
@@ -5,7 +5,8 @@
>SAMBA Project Documentation</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
REL="NEXT"
TITLE="General installation"
HREF="introduction.html"></HEAD
@@ -19,61 +20,32 @@ ALINK="#0000FF"
><DIV
CLASS="BOOK"
><A
-NAME="SAMBA-HOWTO-COLLECTION"
-></A
-><DIV
+NAME="SAMBA-HOWTO-COLLECTION"><DIV
CLASS="TITLEPAGE"
><H1
CLASS="TITLE"
><A
-NAME="SAMBA-HOWTO-COLLECTION"
->SAMBA Project Documentation</A
-></H1
+NAME="SAMBA-HOWTO-COLLECTION">SAMBA Project Documentation</H1
><H3
CLASS="AUTHOR"
><A
-NAME="AEN4"
-></A
->SAMBA Team</H3
-><DIV
-CLASS="AFFILIATION"
-><DIV
-CLASS="ADDRESS"
-><P
-CLASS="ADDRESS"
-><CODE
-CLASS="EMAIL"
->&#60;<A
-HREF="mailto:samba@samba.org"
->samba@samba.org</A
->&#62;</CODE
-></P
-></DIV
-></DIV
-><H4
-CLASS="EDITEDBY"
->Edited by</H4
-><H3
-CLASS="EDITOR"
->Jelmer R. Vernooij</H3
-><H3
-CLASS="EDITOR"
->John H. Terpstra</H3
-><H3
-CLASS="EDITOR"
->Gerald (Jerry) Carter</H3
-><DIV
-><DIV
-CLASS="ABSTRACT"
-><P
-></P
+NAME="AEN4">SAMBA Team</H3
+><HR></DIV
+><H1
><A
-NAME="AEN34"
-></A
+NAME="AEN8">Abstract</H1
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Last Update</I
+></SPAN
+> : Wed Jan 15</P
><P
>This book is a collection of HOWTOs added to Samba documentation over the years.
-Samba is always under development, and so is it's documentation.
-The most recent version of this document
+I try to ensure that all are current, but sometimes the is a larger job
+than one person can maintain. The most recent version of this document
can be found at <A
HREF="http://www.samba.org/"
TARGET="_top"
@@ -90,17 +62,6 @@ TARGET="_top"
>jelmer@samba.org</A
>.</P
><P
-></P
-></DIV
-></DIV
-><DIV
-CLASS="LEGALNOTICE"
-><P
-></P
-><A
-NAME="AEN39"
-></A
-><P
>This documentation is distributed under the GNU General Public License (GPL)
version 2. A copy of the license is included with the Samba source
distribution. A copy can be found on-line at <A
@@ -109,9 +70,7 @@ TARGET="_top"
>http://www.fsf.org/licenses/gpl.txt</A
></P
><P
-></P
-></DIV
-><HR></DIV
+>Cheers, jerry</P
><DIV
CLASS="TOC"
><DL
@@ -128,86 +87,130 @@ HREF="introduction.html"
><DL
><DT
>1. <A
-HREF="introsmb.html"
->Introduction to Samba</A
+HREF="install.html"
+>How to Install and Test SAMBA</A
></DT
><DD
><DL
><DT
>1.1. <A
-HREF="introsmb.html#AEN61"
->Background</A
+HREF="install.html#AEN26"
+>Read the man pages</A
></DT
><DT
>1.2. <A
-HREF="introsmb.html#AEN67"
->Terminology</A
+HREF="install.html#AEN36"
+>Building the Binaries</A
></DT
><DT
>1.3. <A
-HREF="introsmb.html#AEN91"
->Related Projects</A
+HREF="install.html#AEN64"
+>The all important step</A
></DT
><DT
>1.4. <A
-HREF="introsmb.html#AEN100"
->SMB Methodology</A
+HREF="install.html#AEN68"
+>Create the smb configuration file.</A
></DT
><DT
>1.5. <A
-HREF="introsmb.html#AEN115"
->Additional Resources</A
+HREF="install.html#AEN82"
+>Test your config file with
+ <B
+CLASS="COMMAND"
+>testparm</B
+></A
></DT
><DT
>1.6. <A
-HREF="introsmb.html#AEN151"
->Epilogue</A
+HREF="install.html#AEN90"
+>Starting the smbd and nmbd</A
></DT
><DT
>1.7. <A
-HREF="introsmb.html#AEN162"
->Miscellaneous</A
+HREF="install.html#AEN145"
+>Try listing the shares available on your
+ server</A
+></DT
+><DT
+>1.8. <A
+HREF="install.html#AEN154"
+>Try connecting with the unix client</A
+></DT
+><DT
+>1.9. <A
+HREF="install.html#AEN170"
+>Try connecting from a DOS, WfWg, Win9x, WinNT,
+ Win2k, OS/2, etc... client</A
+></DT
+><DT
+>1.10. <A
+HREF="install.html#AEN184"
+>What If Things Don't Work?</A
></DT
></DL
></DD
><DT
>2. <A
-HREF="install.html"
->How to Install and Test SAMBA</A
+HREF="improved-browsing.html"
+>Improved browsing in samba</A
></DT
><DD
><DL
><DT
>2.1. <A
-HREF="install.html#AEN187"
->Obtaining and installing samba</A
+HREF="improved-browsing.html#AEN229"
+>Overview of browsing</A
></DT
><DT
>2.2. <A
-HREF="install.html#AEN193"
->Configuring samba</A
+HREF="improved-browsing.html#AEN233"
+>Browsing support in samba</A
></DT
><DT
>2.3. <A
-HREF="install.html#AEN229"
->Try listing the shares available on your
- server</A
+HREF="improved-browsing.html#AEN242"
+>Problem resolution</A
></DT
><DT
>2.4. <A
-HREF="install.html#AEN238"
->Try connecting with the unix client</A
+HREF="improved-browsing.html#AEN249"
+>Browsing across subnets</A
></DT
><DT
>2.5. <A
-HREF="install.html#AEN259"
->Try connecting from a DOS, WfWg, Win9x, WinNT,
- Win2k, OS/2, etc... client</A
+HREF="improved-browsing.html#AEN289"
+>Setting up a WINS server</A
></DT
><DT
>2.6. <A
-HREF="install.html#AEN272"
->What If Things Don't Work?</A
+HREF="improved-browsing.html#AEN308"
+>Setting up Browsing in a WORKGROUP</A
+></DT
+><DT
+>2.7. <A
+HREF="improved-browsing.html#AEN326"
+>Setting up Browsing in a DOMAIN</A
+></DT
+><DT
+>2.8. <A
+HREF="improved-browsing.html#AEN336"
+>Forcing samba to be the master</A
+></DT
+><DT
+>2.9. <A
+HREF="improved-browsing.html#AEN345"
+>Making samba the domain master</A
+></DT
+><DT
+>2.10. <A
+HREF="improved-browsing.html#AEN363"
+>Note about broadcast addresses</A
+></DT
+><DT
+>2.11. <A
+HREF="improved-browsing.html#AEN366"
+>Multiple interfaces</A
></DT
></DL
></DD
@@ -220,95 +223,58 @@ HREF="browsing-quick.html"
><DL
><DT
>3.1. <A
-HREF="browsing-quick.html#AEN305"
+HREF="browsing-quick.html#AEN377"
>Discussion</A
></DT
><DT
>3.2. <A
-HREF="browsing-quick.html#AEN326"
->How browsing functions and how to deploy stable and
-dependable browsing using Samba</A
+HREF="browsing-quick.html#AEN385"
+>Use of the "Remote Announce" parameter</A
></DT
><DT
>3.3. <A
-HREF="browsing-quick.html#AEN340"
->Use of the <B
-CLASS="COMMAND"
->Remote Announce</B
-> parameter</A
+HREF="browsing-quick.html#AEN399"
+>Use of the "Remote Browse Sync" parameter</A
></DT
><DT
>3.4. <A
-HREF="browsing-quick.html#AEN363"
->Use of the <B
-CLASS="COMMAND"
->Remote Browse Sync</B
-> parameter</A
-></DT
-><DT
->3.5. <A
-HREF="browsing-quick.html#AEN374"
+HREF="browsing-quick.html#AEN404"
>Use of WINS</A
></DT
><DT
->3.6. <A
-HREF="browsing-quick.html#AEN400"
+>3.5. <A
+HREF="browsing-quick.html#AEN415"
>Do NOT use more than one (1) protocol on MS Windows machines</A
></DT
><DT
->3.7. <A
-HREF="browsing-quick.html#AEN408"
+>3.6. <A
+HREF="browsing-quick.html#AEN421"
>Name Resolution Order</A
></DT
></DL
></DD
><DT
>4. <A
-HREF="passdb.html"
->User information database</A
+HREF="pwencrypt.html"
+>LanMan and NT Password Encryption in Samba</A
></DT
><DD
><DL
><DT
>4.1. <A
-HREF="passdb.html#AEN468"
+HREF="pwencrypt.html#AEN457"
>Introduction</A
></DT
><DT
>4.2. <A
-HREF="passdb.html#AEN475"
+HREF="pwencrypt.html#AEN462"
>Important Notes About Security</A
></DT
><DT
>4.3. <A
-HREF="passdb.html#AEN513"
+HREF="pwencrypt.html#AEN497"
>The smbpasswd Command</A
></DT
-><DT
->4.4. <A
-HREF="passdb.html#AEN544"
->Plain text</A
-></DT
-><DT
->4.5. <A
-HREF="passdb.html#AEN549"
->TDB</A
-></DT
-><DT
->4.6. <A
-HREF="passdb.html#AEN552"
->LDAP</A
-></DT
-><DT
->4.7. <A
-HREF="passdb.html#AEN765"
->MySQL</A
-></DT
-><DT
->4.8. <A
-HREF="passdb.html#AEN807"
->XML</A
-></DT
></DL
></DD
></DL
@@ -322,191 +288,221 @@ HREF="type.html"
><DL
><DT
>5. <A
-HREF="servertype.html"
->Nomenclature of Server Types</A
+HREF="securitylevels.html"
+>User and Share security level (for servers not in a domain)</A
+></DT
+><DT
+>6. <A
+HREF="samba-pdc.html"
+>How to Configure Samba as a NT4 Primary Domain Controller</A
></DT
><DD
><DL
><DT
->5.1. <A
-HREF="servertype.html#AEN846"
->Stand Alone Server</A
+>6.1. <A
+HREF="samba-pdc.html#AEN575"
+>Prerequisite Reading</A
></DT
><DT
->5.2. <A
-HREF="servertype.html#AEN853"
->Domain Member Server</A
+>6.2. <A
+HREF="samba-pdc.html#AEN581"
+>Background</A
></DT
><DT
->5.3. <A
-HREF="servertype.html#AEN859"
->Domain Controller</A
+>6.3. <A
+HREF="samba-pdc.html#AEN620"
+>Configuring the Samba Domain Controller</A
></DT
-></DL
-></DD
><DT
->6. <A
-HREF="securitylevels.html"
->Samba as Stand-Alone Server</A
+>6.4. <A
+HREF="samba-pdc.html#AEN663"
+>Creating Machine Trust Accounts and Joining Clients to the
+Domain</A
></DT
-><DD
-><DL
><DT
->6.1. <A
-HREF="securitylevels.html#AEN896"
->User and Share security level</A
+>6.5. <A
+HREF="samba-pdc.html#AEN747"
+>Common Problems and Errors</A
+></DT
+><DT
+>6.6. <A
+HREF="samba-pdc.html#AEN795"
+>System Policies and Profiles</A
+></DT
+><DT
+>6.7. <A
+HREF="samba-pdc.html#AEN839"
+>What other help can I get?</A
+></DT
+><DT
+>6.8. <A
+HREF="samba-pdc.html#AEN953"
+>Domain Control for Windows 9x/ME</A
+></DT
+><DT
+>6.9. <A
+HREF="samba-pdc.html#AEN1091"
+>DOMAIN_CONTROL.txt : Windows NT Domain Control &#38; Samba</A
></DT
></DL
></DD
><DT
>7. <A
-HREF="samba-pdc.html"
->Samba as an NT4 or Win2k Primary Domain Controller</A
+HREF="samba-bdc.html"
+>How to Act as a Backup Domain Controller in a Purely Samba Controlled Domain</A
></DT
><DD
><DL
><DT
>7.1. <A
-HREF="samba-pdc.html#AEN1009"
+HREF="samba-bdc.html#AEN1127"
>Prerequisite Reading</A
></DT
><DT
>7.2. <A
-HREF="samba-pdc.html#AEN1013"
+HREF="samba-bdc.html#AEN1131"
>Background</A
></DT
><DT
>7.3. <A
-HREF="samba-pdc.html#AEN1053"
->Configuring the Samba Domain Controller</A
+HREF="samba-bdc.html#AEN1139"
+>What qualifies a Domain Controller on the network?</A
></DT
><DT
>7.4. <A
-HREF="samba-pdc.html#AEN1095"
->Creating Machine Trust Accounts and Joining Clients to the Domain</A
+HREF="samba-bdc.html#AEN1148"
+>Can Samba be a Backup Domain Controller?</A
></DT
><DT
>7.5. <A
-HREF="samba-pdc.html#AEN1211"
->Common Problems and Errors</A
-></DT
-><DT
->7.6. <A
-HREF="samba-pdc.html#AEN1240"
->Domain Control for Windows 9x/ME</A
+HREF="samba-bdc.html#AEN1152"
+>How do I set up a Samba BDC?</A
></DT
></DL
></DD
><DT
>8. <A
-HREF="samba-bdc.html"
->Samba Backup Domain Controller to Samba Domain Control</A
+HREF="ads.html"
+>Samba as a ADS domain member</A
></DT
><DD
><DL
><DT
>8.1. <A
-HREF="samba-bdc.html#AEN1293"
->Prerequisite Reading</A
+HREF="ads.html#AEN1187"
+>Installing the required packages for Debian</A
></DT
><DT
>8.2. <A
-HREF="samba-bdc.html#AEN1297"
->Background</A
+HREF="ads.html#AEN1193"
+>Installing the required packages for RedHat</A
></DT
><DT
>8.3. <A
-HREF="samba-bdc.html#AEN1305"
->What qualifies a Domain Controller on the network?</A
+HREF="ads.html#AEN1202"
+>Compile Samba</A
></DT
><DT
>8.4. <A
-HREF="samba-bdc.html#AEN1314"
->Can Samba be a Backup Domain Controller to an NT PDC?</A
+HREF="ads.html#AEN1217"
+>Setup your /etc/krb5.conf</A
></DT
><DT
>8.5. <A
-HREF="samba-bdc.html#AEN1319"
->How do I set up a Samba BDC?</A
+HREF="ads.html#AEN1227"
+>Create the computer account</A
+></DT
+><DT
+>8.6. <A
+HREF="ads.html#AEN1243"
+>Test your server setup</A
+></DT
+><DT
+>8.7. <A
+HREF="ads.html#AEN1248"
+>Testing with smbclient</A
+></DT
+><DT
+>8.8. <A
+HREF="ads.html#AEN1251"
+>Notes</A
></DT
></DL
></DD
><DT
>9. <A
-HREF="ads.html"
->Samba as a ADS domain member</A
+HREF="domain-security.html"
+>Samba as a NT4 domain member</A
></DT
><DD
><DL
><DT
>9.1. <A
-HREF="ads.html#AEN1363"
->Setup your <TT
-CLASS="FILENAME"
->smb.conf</TT
-></A
+HREF="domain-security.html#AEN1273"
+>Joining an NT Domain with Samba 2.2</A
></DT
><DT
>9.2. <A
-HREF="ads.html#AEN1376"
->Setup your <TT
-CLASS="FILENAME"
->/etc/krb5.conf</TT
-></A
+HREF="domain-security.html#AEN1337"
+>Samba and Windows 2000 Domains</A
></DT
><DT
>9.3. <A
-HREF="ads.html#ADS-CREATE-MACHINE-ACCOUNT"
->Create the computer account</A
-></DT
-><DT
->9.4. <A
-HREF="ads.html#ADS-TEST-SERVER"
->Test your server setup</A
-></DT
-><DT
->9.5. <A
-HREF="ads.html#ADS-TEST-SMBCLIENT"
->Testing with <SPAN
-CLASS="APPLICATION"
->smbclient</SPAN
-></A
-></DT
-><DT
->9.6. <A
-HREF="ads.html#AEN1424"
->Notes</A
+HREF="domain-security.html#AEN1342"
+>Why is this better than security = server?</A
></DT
></DL
></DD
+></DL
+></DD
+><DT
+>III. <A
+HREF="optional.html"
+>Optional configuration</A
+></DT
+><DD
+><DL
><DT
>10. <A
-HREF="domain-member.html"
->Samba as a NT4 or Win2k domain member</A
+HREF="integrate-ms-networks.html"
+>Integrating MS Windows networks with Samba</A
></DT
><DD
><DL
><DT
>10.1. <A
-HREF="domain-member.html#AEN1447"
->Joining an NT Domain with Samba 3.0</A
+HREF="integrate-ms-networks.html#AEN1374"
+>Agenda</A
></DT
><DT
>10.2. <A
-HREF="domain-member.html#AEN1501"
->Why is this better than security = server?</A
+HREF="integrate-ms-networks.html#AEN1396"
+>Name Resolution in a pure Unix/Linux world</A
></DT
-></DL
-></DD
-></DL
-></DD
><DT
->III. <A
-HREF="optional.html"
->Advanced Configuration</A
+>10.3. <A
+HREF="integrate-ms-networks.html#AEN1459"
+>Name resolution as used within MS Windows networking</A
+></DT
+><DT
+>10.4. <A
+HREF="integrate-ms-networks.html#AEN1504"
+>How browsing functions and how to deploy stable and
+dependable browsing using Samba</A
+></DT
+><DT
+>10.5. <A
+HREF="integrate-ms-networks.html#AEN1514"
+>MS Windows security options and how to configure
+Samba for seemless integration</A
></DT
-><DD
-><DL
+><DT
+>10.6. <A
+HREF="integrate-ms-networks.html#AEN1584"
+>Conclusions</A
+></DT
+></DL
+></DD
><DT
>11. <A
HREF="unix-permissions.html"
@@ -516,39 +512,39 @@ HREF="unix-permissions.html"
><DL
><DT
>11.1. <A
-HREF="unix-permissions.html#AEN1533"
+HREF="unix-permissions.html#AEN1605"
>Viewing and changing UNIX permissions using the NT
security dialogs</A
></DT
><DT
>11.2. <A
-HREF="unix-permissions.html#AEN1539"
+HREF="unix-permissions.html#AEN1614"
>How to view file security on a Samba share</A
></DT
><DT
>11.3. <A
-HREF="unix-permissions.html#AEN1550"
+HREF="unix-permissions.html#AEN1625"
>Viewing file ownership</A
></DT
><DT
>11.4. <A
-HREF="unix-permissions.html#AEN1570"
+HREF="unix-permissions.html#AEN1645"
>Viewing file or directory permissions</A
></DT
><DT
>11.5. <A
-HREF="unix-permissions.html#AEN1606"
+HREF="unix-permissions.html#AEN1681"
>Modifying file or directory permissions</A
></DT
><DT
>11.6. <A
-HREF="unix-permissions.html#AEN1628"
+HREF="unix-permissions.html#AEN1703"
>Interaction with the standard Samba create mask
parameters</A
></DT
><DT
>11.7. <A
-HREF="unix-permissions.html#AEN1681"
+HREF="unix-permissions.html#AEN1767"
>Interaction with the standard Samba file attribute
mapping</A
></DT
@@ -556,108 +552,69 @@ HREF="unix-permissions.html#AEN1681"
></DD
><DT
>12. <A
-HREF="groupmapping.html"
->Configuring Group Mapping</A
-></DT
-><DT
->13. <A
-HREF="printing.html"
->Printing Support</A
+HREF="pam.html"
+>Configuring PAM for distributed but centrally
+managed authentication</A
></DT
><DD
><DL
><DT
->13.1. <A
-HREF="printing.html#AEN1744"
->Introduction</A
+>12.1. <A
+HREF="pam.html#AEN1788"
+>Samba and PAM</A
></DT
><DT
->13.2. <A
-HREF="printing.html#AEN1766"
->Configuration</A
+>12.2. <A
+HREF="pam.html#AEN1832"
+>Distributed Authentication</A
></DT
><DT
->13.3. <A
-HREF="printing.html#AEN1878"
->The Imprints Toolset</A
+>12.3. <A
+HREF="pam.html#AEN1839"
+>PAM Configuration in smb.conf</A
></DT
+></DL
+></DD
><DT
->13.4. <A
-HREF="printing.html#AEN1921"
->Diagnosis</A
+>13. <A
+HREF="msdfs.html"
+>Hosting a Microsoft Distributed File System tree on Samba</A
+></DT
+><DD
+><DL
+><DT
+>13.1. <A
+HREF="msdfs.html#AEN1859"
+>Instructions</A
></DT
></DL
></DD
><DT
>14. <A
-HREF="cups-printing.html"
->CUPS Printing Support</A
+HREF="printing.html"
+>Printing Support</A
></DT
><DD
><DL
><DT
>14.1. <A
-HREF="cups-printing.html#AEN2034"
+HREF="printing.html#AEN1920"
>Introduction</A
></DT
><DT
>14.2. <A
-HREF="cups-printing.html#AEN2041"
->Configuring <TT
-CLASS="FILENAME"
->smb.conf</TT
-> for CUPS</A
+HREF="printing.html#AEN1942"
+>Configuration</A
></DT
><DT
>14.3. <A
-HREF="cups-printing.html#AEN2061"
->CUPS - RAW Print Through Mode</A
+HREF="printing.html#AEN2050"
+>The Imprints Toolset</A
></DT
><DT
>14.4. <A
-HREF="cups-printing.html#AEN2118"
->CUPS as a network PostScript RIP -- CUPS drivers working on server, Adobe
-PostScript driver with CUPS-PPDs downloaded to clients</A
-></DT
-><DT
->14.5. <A
-HREF="cups-printing.html#AEN2139"
->Windows Terminal Servers (WTS) as CUPS clients</A
-></DT
-><DT
->14.6. <A
-HREF="cups-printing.html#AEN2143"
->Setting up CUPS for driver download</A
-></DT
-><DT
->14.7. <A
-HREF="cups-printing.html#AEN2156"
->Sources of CUPS drivers / PPDs</A
-></DT
-><DT
->14.8. <A
-HREF="cups-printing.html#AEN2212"
->The CUPS Filter Chains</A
-></DT
-><DT
->14.9. <A
-HREF="cups-printing.html#AEN2251"
->CUPS Print Drivers and Devices</A
-></DT
-><DT
->14.10. <A
-HREF="cups-printing.html#AEN2328"
->Limiting the number of pages users can print</A
-></DT
-><DT
->14.11. <A
-HREF="cups-printing.html#AEN2424"
->Advanced Postscript Printing from MS Windows</A
-></DT
-><DT
->14.12. <A
-HREF="cups-printing.html#AEN2439"
->Auto-Deletion of CUPS spool files</A
+HREF="printing.html#AEN2093"
+>Diagnosis</A
></DT
></DL
></DD
@@ -670,352 +627,252 @@ HREF="winbind.html"
><DL
><DT
>15.1. <A
-HREF="winbind.html#AEN2515"
+HREF="winbind.html#AEN2225"
>Abstract</A
></DT
><DT
>15.2. <A
-HREF="winbind.html#AEN2519"
+HREF="winbind.html#AEN2229"
>Introduction</A
></DT
><DT
>15.3. <A
-HREF="winbind.html#AEN2532"
+HREF="winbind.html#AEN2242"
>What Winbind Provides</A
></DT
><DT
>15.4. <A
-HREF="winbind.html#AEN2543"
+HREF="winbind.html#AEN2253"
>How Winbind Works</A
></DT
><DT
>15.5. <A
-HREF="winbind.html#AEN2586"
+HREF="winbind.html#AEN2293"
>Installation and Configuration</A
></DT
><DT
>15.6. <A
-HREF="winbind.html#AEN2843"
+HREF="winbind.html#AEN2542"
>Limitations</A
></DT
><DT
>15.7. <A
-HREF="winbind.html#AEN2853"
+HREF="winbind.html#AEN2552"
>Conclusion</A
></DT
></DL
></DD
><DT
>16. <A
-HREF="advancednetworkmanagement.html"
->Advanced Network Manangement</A
+HREF="pdb-mysql.html"
+>Passdb MySQL plugin</A
></DT
><DD
><DL
><DT
>16.1. <A
-HREF="advancednetworkmanagement.html#AEN2869"
->Configuring Samba Share Access Controls</A
+HREF="pdb-mysql.html#AEN2566"
+>Building</A
></DT
><DT
>16.2. <A
-HREF="advancednetworkmanagement.html#AEN2907"
->Remote Server Administration</A
+HREF="pdb-mysql.html#AEN2572"
+>Configuring</A
></DT
><DT
>16.3. <A
-HREF="advancednetworkmanagement.html#AEN2924"
->Network Logon Script Magic</A
+HREF="pdb-mysql.html#AEN2589"
+>Using plaintext passwords or encrypted password</A
+></DT
+><DT
+>16.4. <A
+HREF="pdb-mysql.html#AEN2594"
+>Getting non-column data from the table</A
></DT
></DL
></DD
><DT
>17. <A
-HREF="policymgmt.html"
->System and Account Policies</A
+HREF="pdb-xml.html"
+>Passdb XML plugin</A
></DT
><DD
><DL
><DT
>17.1. <A
-HREF="policymgmt.html#AEN2958"
->Creating and Managing System Policies</A
+HREF="pdb-xml.html#AEN2613"
+>Building</A
></DT
><DT
>17.2. <A
-HREF="policymgmt.html#AEN3030"
->Managing Account/User Policies</A
-></DT
-><DT
->17.3. <A
-HREF="policymgmt.html#AEN3052"
->System Startup and Logon Processing Overview</A
+HREF="pdb-xml.html#AEN2619"
+>Usage</A
></DT
></DL
></DD
><DT
>18. <A
-HREF="profilemgmt.html"
->Desktop Profile Management</A
+HREF="vfs.html"
+>Stackable VFS modules</A
></DT
><DD
><DL
><DT
>18.1. <A
-HREF="profilemgmt.html#AEN3095"
->Roaming Profiles</A
+HREF="vfs.html#AEN2640"
+>Introduction and configuration</A
></DT
><DT
>18.2. <A
-HREF="profilemgmt.html#AEN3302"
->Mandatory profiles</A
+HREF="vfs.html#AEN2649"
+>Included modules</A
></DT
><DT
>18.3. <A
-HREF="profilemgmt.html#AEN3309"
->Creating/Managing Group Profiles</A
-></DT
-><DT
->18.4. <A
-HREF="profilemgmt.html#AEN3315"
->Default Profile for Windows Users</A
+HREF="vfs.html#AEN2703"
+>VFS modules available elsewhere</A
></DT
></DL
></DD
><DT
>19. <A
-HREF="interdomaintrusts.html"
->Interdomain Trust Relationships</A
+HREF="samba-ldap-howto.html"
+>Storing Samba's User/Machine Account information in an LDAP Directory</A
></DT
><DD
><DL
><DT
>19.1. <A
-HREF="interdomaintrusts.html#AEN3446"
->Trust Relationship Background</A
+HREF="samba-ldap-howto.html#AEN2737"
+>Purpose</A
></DT
><DT
>19.2. <A
-HREF="interdomaintrusts.html#AEN3455"
->Native MS Windows NT4 Trusts Configuration</A
+HREF="samba-ldap-howto.html#AEN2757"
+>Introduction</A
></DT
><DT
>19.3. <A
-HREF="interdomaintrusts.html#AEN3464"
->Configuring Samba NT-style Domain Trusts</A
+HREF="samba-ldap-howto.html#AEN2786"
+>Supported LDAP Servers</A
></DT
-></DL
-></DD
><DT
->20. <A
-HREF="pam.html"
->PAM Configuration for Centrally Managed Authentication</A
+>19.4. <A
+HREF="samba-ldap-howto.html#AEN2791"
+>Schema and Relationship to the RFC 2307 posixAccount</A
></DT
-><DD
-><DL
><DT
->20.1. <A
-HREF="pam.html#AEN3507"
->Samba and PAM</A
+>19.5. <A
+HREF="samba-ldap-howto.html#AEN2803"
+>Configuring Samba with LDAP</A
></DT
><DT
->20.2. <A
-HREF="pam.html#AEN3558"
->Distributed Authentication</A
+>19.6. <A
+HREF="samba-ldap-howto.html#AEN2850"
+>Accounts and Groups management</A
></DT
><DT
->20.3. <A
-HREF="pam.html#AEN3563"
->PAM Configuration in smb.conf</A
+>19.7. <A
+HREF="samba-ldap-howto.html#AEN2855"
+>Security and sambaAccount</A
></DT
-></DL
-></DD
><DT
->21. <A
-HREF="vfs.html"
->Stackable VFS modules</A
-></DT
-><DD
-><DL
-><DT
->21.1. <A
-HREF="vfs.html#AEN3600"
->Introduction and configuration</A
+>19.8. <A
+HREF="samba-ldap-howto.html#AEN2875"
+>LDAP specials attributes for sambaAccounts</A
></DT
><DT
->21.2. <A
-HREF="vfs.html#AEN3609"
->Included modules</A
+>19.9. <A
+HREF="samba-ldap-howto.html#AEN2945"
+>Example LDIF Entries for a sambaAccount</A
></DT
><DT
->21.3. <A
-HREF="vfs.html#AEN3667"
->VFS modules available elsewhere</A
+>19.10. <A
+HREF="samba-ldap-howto.html#AEN2953"
+>Comments</A
></DT
></DL
></DD
><DT
->22. <A
-HREF="msdfs.html"
->Hosting a Microsoft Distributed File System tree on Samba</A
-></DT
-><DD
-><DL
-><DT
->22.1. <A
-HREF="msdfs.html#AEN3695"
->Instructions</A
-></DT
-></DL
-></DD
-><DT
->23. <A
-HREF="integrate-ms-networks.html"
->Integrating MS Windows networks with Samba</A
+>20. <A
+HREF="cvs-access.html"
+>HOWTO Access Samba source code via CVS</A
></DT
><DD
><DL
><DT
->23.1. <A
-HREF="integrate-ms-networks.html#AEN3758"
->Name Resolution in a pure Unix/Linux world</A
+>20.1. <A
+HREF="cvs-access.html#AEN2964"
+>Introduction</A
></DT
><DT
->23.2. <A
-HREF="integrate-ms-networks.html#AEN3821"
->Name resolution as used within MS Windows networking</A
+>20.2. <A
+HREF="cvs-access.html#AEN2969"
+>CVS Access to samba.org</A
></DT
></DL
></DD
><DT
->24. <A
-HREF="improved-browsing.html"
->Improved browsing in samba</A
-></DT
-><DD
-><DL
-><DT
->24.1. <A
-HREF="improved-browsing.html#AEN3874"
->Overview of browsing</A
-></DT
-><DT
->24.2. <A
-HREF="improved-browsing.html#AEN3880"
->Browsing support in samba</A
-></DT
-><DT
->24.3. <A
-HREF="improved-browsing.html#AEN3895"
->Problem resolution</A
-></DT
-><DT
->24.4. <A
-HREF="improved-browsing.html#AEN3907"
->Browsing across subnets</A
-></DT
-><DT
->24.5. <A
-HREF="improved-browsing.html#AEN3948"
->Setting up a WINS server</A
-></DT
-><DT
->24.6. <A
-HREF="improved-browsing.html#AEN3971"
->Setting up Browsing in a WORKGROUP</A
-></DT
-><DT
->24.7. <A
-HREF="improved-browsing.html#AEN3997"
->Setting up Browsing in a DOMAIN</A
-></DT
-><DT
->24.8. <A
-HREF="improved-browsing.html#BROWSE-FORCE-MASTER"
->Forcing samba to be the master</A
-></DT
-><DT
->24.9. <A
-HREF="improved-browsing.html#AEN4032"
->Making samba the domain master</A
-></DT
-><DT
->24.10. <A
-HREF="improved-browsing.html#AEN4054"
->Note about broadcast addresses</A
-></DT
-><DT
->24.11. <A
-HREF="improved-browsing.html#AEN4057"
->Multiple interfaces</A
+>21. <A
+HREF="groupmapping.html"
+>Group mapping HOWTO</A
></DT
-></DL
-></DD
><DT
->25. <A
-HREF="securing-samba.html"
->Securing Samba</A
+>22. <A
+HREF="speed.html"
+>Samba performance issues</A
></DT
><DD
><DL
><DT
->25.1. <A
-HREF="securing-samba.html#AEN4073"
->Introduction</A
-></DT
-><DT
->25.2. <A
-HREF="securing-samba.html#AEN4076"
->Using host based protection</A
+>22.1. <A
+HREF="speed.html#AEN3055"
+>Comparisons</A
></DT
><DT
->25.3. <A
-HREF="securing-samba.html#AEN4086"
->Using interface protection</A
+>22.2. <A
+HREF="speed.html#AEN3061"
+>Socket options</A
></DT
><DT
->25.4. <A
-HREF="securing-samba.html#AEN4094"
->Using a firewall</A
+>22.3. <A
+HREF="speed.html#AEN3068"
+>Read size</A
></DT
><DT
->25.5. <A
-HREF="securing-samba.html#AEN4101"
->Using a IPC$ share deny</A
+>22.4. <A
+HREF="speed.html#AEN3073"
+>Max xmit</A
></DT
><DT
->25.6. <A
-HREF="securing-samba.html#AEN4110"
->Upgrading Samba</A
+>22.5. <A
+HREF="speed.html#AEN3078"
+>Log level</A
></DT
-></DL
-></DD
><DT
->26. <A
-HREF="unicode.html"
->Unicode/Charsets</A
+>22.6. <A
+HREF="speed.html#AEN3081"
+>Read raw</A
></DT
-><DD
-><DL
><DT
->26.1. <A
-HREF="unicode.html#AEN4132"
->What are charsets and unicode?</A
+>22.7. <A
+HREF="speed.html#AEN3086"
+>Write raw</A
></DT
><DT
->26.2. <A
-HREF="unicode.html#AEN4141"
->Samba and charsets</A
+>22.8. <A
+HREF="speed.html#AEN3090"
+>Slow Clients</A
></DT
><DT
->26.3. <A
-HREF="unicode.html#AEN4160"
->Conversion from old names</A
+>22.9. <A
+HREF="speed.html#AEN3094"
+>Slow Logins</A
></DT
><DT
->26.4. <A
-HREF="unicode.html#AEN4168"
->Japanese charsets</A
+>22.10. <A
+HREF="speed.html#AEN3097"
+>Client tuning</A
></DT
></DL
></DD
@@ -1029,311 +886,136 @@ HREF="appendixes.html"
><DD
><DL
><DT
->27. <A
-HREF="compiling.html"
->How to compile SAMBA</A
-></DT
-><DD
-><DL
-><DT
->27.1. <A
-HREF="compiling.html#AEN4204"
->Access Samba source code via CVS</A
-></DT
-><DT
->27.2. <A
-HREF="compiling.html#AEN4247"
->Accessing the samba sources via rsync and ftp</A
-></DT
-><DT
->27.3. <A
-HREF="compiling.html#AEN4253"
->Verifying Samba's PGP signature</A
-></DT
-><DT
->27.4. <A
-HREF="compiling.html#AEN4265"
->Building the Binaries</A
-></DT
-><DT
->27.5. <A
-HREF="compiling.html#AEN4322"
->Starting the smbd and nmbd</A
-></DT
-></DL
-></DD
-><DT
->28. <A
-HREF="nt4migration.html"
->Migration from NT4 PDC to Samba-3 PDC</A
-></DT
-><DD
-><DL
-><DT
->28.1. <A
-HREF="nt4migration.html#AEN4396"
->Planning and Getting Started</A
-></DT
-><DT
->28.2. <A
-HREF="nt4migration.html#AEN4429"
->Managing Samba-3 Domain Control</A
-></DT
-></DL
-></DD
-><DT
->29. <A
+>23. <A
HREF="portability.html"
>Portability</A
></DT
><DD
><DL
><DT
->29.1. <A
-HREF="portability.html#AEN4444"
+>23.1. <A
+HREF="portability.html#AEN3139"
>HPUX</A
></DT
><DT
->29.2. <A
-HREF="portability.html#AEN4450"
+>23.2. <A
+HREF="portability.html#AEN3145"
>SCO Unix</A
></DT
><DT
->29.3. <A
-HREF="portability.html#AEN4454"
+>23.3. <A
+HREF="portability.html#AEN3149"
>DNIX</A
></DT
><DT
->29.4. <A
-HREF="portability.html#AEN4483"
+>23.4. <A
+HREF="portability.html#AEN3178"
>RedHat Linux Rembrandt-II</A
></DT
-><DT
->29.5. <A
-HREF="portability.html#AEN4489"
->AIX</A
-></DT
-><DT
->29.6. <A
-HREF="portability.html#AEN4495"
->Solaris</A
-></DT
></DL
></DD
><DT
->30. <A
+>24. <A
HREF="other-clients.html"
>Samba and other CIFS clients</A
></DT
><DD
><DL
><DT
->30.1. <A
-HREF="other-clients.html#AEN4522"
+>24.1. <A
+HREF="other-clients.html#AEN3199"
>Macintosh clients?</A
></DT
><DT
->30.2. <A
-HREF="other-clients.html#AEN4531"
+>24.2. <A
+HREF="other-clients.html#AEN3208"
>OS2 Client</A
></DT
><DT
->30.3. <A
-HREF="other-clients.html#AEN4571"
+>24.3. <A
+HREF="other-clients.html#AEN3248"
>Windows for Workgroups</A
></DT
><DT
->30.4. <A
-HREF="other-clients.html#AEN4595"
+>24.4. <A
+HREF="other-clients.html#AEN3269"
>Windows '95/'98</A
></DT
><DT
->30.5. <A
-HREF="other-clients.html#AEN4611"
+>24.5. <A
+HREF="other-clients.html#AEN3285"
>Windows 2000 Service Pack 2</A
></DT
-><DT
->30.6. <A
-HREF="other-clients.html#AEN4628"
->Windows NT 3.1</A
-></DT
-></DL
-></DD
-><DT
->31. <A
-HREF="swat.html"
->SWAT - The Samba Web Admininistration Tool</A
-></DT
-><DD
-><DL
-><DT
->31.1. <A
-HREF="swat.html#AEN4645"
->SWAT Features and Benefits</A
-></DT
></DL
></DD
><DT
->32. <A
-HREF="speed.html"
->Samba performance issues</A
+>25. <A
+HREF="bugreport.html"
+>Reporting Bugs</A
></DT
><DD
><DL
><DT
->32.1. <A
-HREF="speed.html#AEN4687"
->Comparisons</A
-></DT
-><DT
->32.2. <A
-HREF="speed.html#AEN4693"
->Socket options</A
-></DT
-><DT
->32.3. <A
-HREF="speed.html#AEN4700"
->Read size</A
-></DT
-><DT
->32.4. <A
-HREF="speed.html#AEN4705"
->Max xmit</A
-></DT
-><DT
->32.5. <A
-HREF="speed.html#AEN4710"
->Log level</A
+>25.1. <A
+HREF="bugreport.html#AEN3309"
+>Introduction</A
></DT
><DT
->32.6. <A
-HREF="speed.html#AEN4713"
->Read raw</A
+>25.2. <A
+HREF="bugreport.html#AEN3319"
+>General info</A
></DT
><DT
->32.7. <A
-HREF="speed.html#AEN4718"
->Write raw</A
+>25.3. <A
+HREF="bugreport.html#AEN3325"
+>Debug levels</A
></DT
><DT
->32.8. <A
-HREF="speed.html#AEN4722"
->Slow Clients</A
+>25.4. <A
+HREF="bugreport.html#AEN3342"
+>Internal errors</A
></DT
><DT
->32.9. <A
-HREF="speed.html#AEN4726"
->Slow Logins</A
+>25.5. <A
+HREF="bugreport.html#AEN3352"
+>Attaching to a running process</A
></DT
><DT
->32.10. <A
-HREF="speed.html#AEN4729"
->Client tuning</A
+>25.6. <A
+HREF="bugreport.html#AEN3355"
+>Patches</A
></DT
></DL
></DD
><DT
->33. <A
+>26. <A
HREF="diagnosis.html"
->The samba checklist</A
+>Diagnosing your samba server</A
></DT
><DD
><DL
><DT
->33.1. <A
-HREF="diagnosis.html#AEN4781"
+>26.1. <A
+HREF="diagnosis.html#AEN3378"
>Introduction</A
></DT
><DT
->33.2. <A
-HREF="diagnosis.html#AEN4786"
+>26.2. <A
+HREF="diagnosis.html#AEN3383"
>Assumptions</A
></DT
><DT
->33.3. <A
-HREF="diagnosis.html#AEN4805"
->The tests</A
+>26.3. <A
+HREF="diagnosis.html#AEN3393"
+>Tests</A
></DT
><DT
->33.4. <A
-HREF="diagnosis.html#AEN4972"
+>26.4. <A
+HREF="diagnosis.html#AEN3503"
>Still having troubles?</A
></DT
></DL
></DD
-><DT
->34. <A
-HREF="problems.html"
->Analysing and solving samba problems</A
-></DT
-><DD
-><DL
-><DT
->34.1. <A
-HREF="problems.html#AEN5004"
->Diagnostics tools</A
-></DT
-><DT
->34.2. <A
-HREF="problems.html#AEN5019"
->Installing 'Network Monitor' on an NT Workstation or a Windows 9x box</A
-></DT
-><DT
->34.3. <A
-HREF="problems.html#AEN5048"
->Useful URL's</A
-></DT
-><DT
->34.4. <A
-HREF="problems.html#AEN5072"
->Getting help from the mailing lists</A
-></DT
-><DT
->34.5. <A
-HREF="problems.html#AEN5102"
->How to get off the mailinglists</A
-></DT
-></DL
-></DD
-><DT
->35. <A
-HREF="bugreport.html"
->Reporting Bugs</A
-></DT
-><DD
-><DL
-><DT
->35.1. <A
-HREF="bugreport.html#AEN5125"
->Introduction</A
-></DT
-><DT
->35.2. <A
-HREF="bugreport.html#AEN5135"
->General info</A
-></DT
-><DT
->35.3. <A
-HREF="bugreport.html#AEN5141"
->Debug levels</A
-></DT
-><DT
->35.4. <A
-HREF="bugreport.html#AEN5162"
->Internal errors</A
-></DT
-><DT
->35.5. <A
-HREF="bugreport.html#AEN5176"
->Attaching to a running process</A
-></DT
-><DT
->35.6. <A
-HREF="bugreport.html#AEN5184"
->Patches</A
-></DT
-></DL
-></DD
></DL
></DD
></DL
diff --git a/docs/htmldocs/samba-ldap-howto.html b/docs/htmldocs/samba-ldap-howto.html
new file mode 100644
index 0000000000..884bb756c1
--- /dev/null
+++ b/docs/htmldocs/samba-ldap-howto.html
@@ -0,0 +1,986 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<HTML
+><HEAD
+><TITLE
+>Storing Samba's User/Machine Account information in an LDAP Directory</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
+REL="HOME"
+TITLE="SAMBA Project Documentation"
+HREF="samba-howto-collection.html"><LINK
+REL="UP"
+TITLE="Optional configuration"
+HREF="optional.html"><LINK
+REL="PREVIOUS"
+TITLE="Stackable VFS modules"
+HREF="vfs.html"><LINK
+REL="NEXT"
+TITLE="HOWTO Access Samba source code via CVS"
+HREF="cvs-access.html"></HEAD
+><BODY
+CLASS="CHAPTER"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><TABLE
+SUMMARY="Header navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>SAMBA Project Documentation</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="vfs.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+></TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="cvs-access.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="CHAPTER"
+><H1
+><A
+NAME="SAMBA-LDAP-HOWTO">Chapter 19. Storing Samba's User/Machine Account information in an LDAP Directory</H1
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN2737">19.1. Purpose</H1
+><P
+>This document describes how to use an LDAP directory for storing Samba user
+account information traditionally stored in the smbpasswd(5) file. It is
+assumed that the reader already has a basic understanding of LDAP concepts
+and has a working directory server already installed. For more information
+on LDAP architectures and Directories, please refer to the following sites.</P
+><P
+></P
+><UL
+><LI
+><P
+>OpenLDAP - <A
+HREF="http://www.openldap.org/"
+TARGET="_top"
+>http://www.openldap.org/</A
+></P
+></LI
+><LI
+><P
+>iPlanet Directory Server - <A
+HREF="http://iplanet.netscape.com/directory"
+TARGET="_top"
+>http://iplanet.netscape.com/directory</A
+></P
+></LI
+></UL
+><P
+>Note that <A
+HREF="http://www.ora.com/"
+TARGET="_top"
+>O'Reilly Publishing</A
+> is working on
+a guide to LDAP for System Administrators which has a planned release date of
+early summer, 2002.</P
+><P
+>Two additional Samba resources which may prove to be helpful are</P
+><P
+></P
+><UL
+><LI
+><P
+>The <A
+HREF="http://www.unav.es/cti/ldap-smb/ldap-smb-3-howto.html"
+TARGET="_top"
+>Samba-PDC-LDAP-HOWTO</A
+>
+ maintained by Ignacio Coupeau.</P
+></LI
+><LI
+><P
+>The NT migration scripts from <A
+HREF="http://samba.idealx.org/"
+TARGET="_top"
+>IDEALX</A
+> that are
+ geared to manage users and group in such a Samba-LDAP Domain Controller configuration.
+ </P
+></LI
+></UL
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN2757">19.2. Introduction</H1
+><P
+>Traditionally, when configuring <A
+HREF="smb.conf.5.html#ENCRYPTPASSWORDS"
+TARGET="_top"
+>"encrypt
+passwords = yes"</A
+> in Samba's <TT
+CLASS="FILENAME"
+>smb.conf</TT
+> file, user account
+information such as username, LM/NT password hashes, password change times, and account
+flags have been stored in the <TT
+CLASS="FILENAME"
+>smbpasswd(5)</TT
+> file. There are several
+disadvantages to this approach for sites with very large numbers of users (counted
+in the thousands).</P
+><P
+></P
+><UL
+><LI
+><P
+>The first is that all lookups must be performed sequentially. Given that
+there are approximately two lookups per domain logon (one for a normal
+session connection such as when mapping a network drive or printer), this
+is a performance bottleneck for lareg sites. What is needed is an indexed approach
+such as is used in databases.</P
+></LI
+><LI
+><P
+>The second problem is that administrators who desired to replicate a
+smbpasswd file to more than one Samba server were left to use external
+tools such as <B
+CLASS="COMMAND"
+>rsync(1)</B
+> and <B
+CLASS="COMMAND"
+>ssh(1)</B
+>
+and wrote custom, in-house scripts.</P
+></LI
+><LI
+><P
+>And finally, the amount of information which is stored in an
+smbpasswd entry leaves no room for additional attributes such as
+a home directory, password expiration time, or even a Relative
+Identified (RID).</P
+></LI
+></UL
+><P
+>As a result of these defeciencies, a more robust means of storing user attributes
+used by smbd was developed. The API which defines access to user accounts
+is commonly referred to as the samdb interface (previously this was called the passdb
+API, and is still so named in the CVS trees). In Samba 2.2.3, enabling support
+for a samdb backend (e.g. <TT
+CLASS="PARAMETER"
+><I
+>--with-ldapsam</I
+></TT
+> or
+<TT
+CLASS="PARAMETER"
+><I
+>--with-tdbsam</I
+></TT
+>) requires compile time support.</P
+><P
+>When compiling Samba to include the <TT
+CLASS="PARAMETER"
+><I
+>--with-ldapsam</I
+></TT
+> autoconf
+option, smbd (and associated tools) will store and lookup user accounts in
+an LDAP directory. In reality, this is very easy to understand. If you are
+comfortable with using an smbpasswd file, simply replace "smbpasswd" with
+"LDAP directory" in all the documentation.</P
+><P
+>There are a few points to stress about what the <TT
+CLASS="PARAMETER"
+><I
+>--with-ldapsam</I
+></TT
+>
+does not provide. The LDAP support referred to in the this documentation does not
+include:</P
+><P
+></P
+><UL
+><LI
+><P
+>A means of retrieving user account information from
+ an Windows 2000 Active Directory server.</P
+></LI
+><LI
+><P
+>A means of replacing /etc/passwd.</P
+></LI
+></UL
+><P
+>The second item can be accomplished by using LDAP NSS and PAM modules. LGPL
+versions of these libraries can be obtained from PADL Software
+(<A
+HREF="http://www.padl.com/"
+TARGET="_top"
+>http://www.padl.com/</A
+>). However,
+the details of configuring these packages are beyond the scope of this document.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN2786">19.3. Supported LDAP Servers</H1
+><P
+>The LDAP samdb code in 2.2.3 has been developed and tested using the OpenLDAP
+2.0 server and client libraries. The same code should be able to work with
+Netscape's Directory Server and client SDK. However, due to lack of testing
+so far, there are bound to be compile errors and bugs. These should not be
+hard to fix. If you are so inclined, please be sure to forward all patches to
+<A
+HREF="samba-patches@samba.org"
+TARGET="_top"
+>samba-patches@samba.org</A
+> and
+<A
+HREF="jerry@samba.org"
+TARGET="_top"
+>jerry@samba.org</A
+>.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN2791">19.4. Schema and Relationship to the RFC 2307 posixAccount</H1
+><P
+>Samba 2.2.3 includes the necessary schema file for OpenLDAP 2.0 in
+<TT
+CLASS="FILENAME"
+>examples/LDAP/samba.schema</TT
+>. (Note that this schema
+file has been modified since the experimental support initially included
+in 2.2.2). The sambaAccount objectclass is given here:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>objectclass ( 1.3.1.5.1.4.1.7165.2.2.2 NAME 'sambaAccount' SUP top STRUCTURAL
+ DESC 'Samba Account'
+ MUST ( uid $ rid )
+ MAY ( cn $ lmPassword $ ntPassword $ pwdLastSet $ logonTime $
+ logoffTime $ kickoffTime $ pwdCanChange $ pwdMustChange $ acctFlags $
+ displayName $ smbHome $ homeDrive $ scriptPath $ profilePath $
+ description $ userWorkstations $ primaryGroupID $ domain ))</PRE
+></P
+><P
+>The samba.schema file has been formatted for OpenLDAP 2.0. The OID's are
+owned by the Samba Team and as such is legal to be openly published.
+If you translate the schema to be used with Netscape DS, please
+submit the modified schema file as a patch to <A
+HREF="jerry@samba.org"
+TARGET="_top"
+>jerry@samba.org</A
+></P
+><P
+>Just as the smbpasswd file is mean to store information which supplements a
+user's <TT
+CLASS="FILENAME"
+>/etc/passwd</TT
+> entry, so is the sambaAccount object
+meant to supplement the UNIX user account information. A sambaAccount is a
+<TT
+CLASS="CONSTANT"
+>STRUCTURAL</TT
+> objectclass so it can be stored individually
+in the directory. However, there are several fields (e.g. uid) which overlap
+with the posixAccount objectclass outlined in RFC2307. This is by design.</P
+><P
+>In order to store all user account information (UNIX and Samba) in the directory,
+it is necessary to use the sambaAccount and posixAccount objectclasses in
+combination. However, smbd will still obtain the user's UNIX account
+information via the standard C library calls (e.g. getpwnam(), et. al.).
+This means that the Samba server must also have the LDAP NSS library installed
+and functioning correctly. This division of information makes it possible to
+store all Samba account information in LDAP, but still maintain UNIX account
+information in NIS while the network is transitioning to a full LDAP infrastructure.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN2803">19.5. Configuring Samba with LDAP</H1
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN2805">19.5.1. OpenLDAP configuration</H2
+><P
+>To include support for the sambaAccount object in an OpenLDAP directory
+server, first copy the samba.schema file to slapd's configuration directory.</P
+><P
+><TT
+CLASS="PROMPT"
+>root# </TT
+><B
+CLASS="COMMAND"
+>cp samba.schema /etc/openldap/schema/</B
+></P
+><P
+>Next, include the <TT
+CLASS="FILENAME"
+>samba.schema</TT
+> file in <TT
+CLASS="FILENAME"
+>slapd.conf</TT
+>.
+The sambaAccount object contains two attributes which depend upon other schema
+files. The 'uid' attribute is defined in <TT
+CLASS="FILENAME"
+>cosine.schema</TT
+> and
+the 'displayName' attribute is defined in the <TT
+CLASS="FILENAME"
+>inetorgperson.schema</TT
+>
+file. Both of these must be included before the <TT
+CLASS="FILENAME"
+>samba.schema</TT
+> file.</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>## /etc/openldap/slapd.conf
+
+## schema files (core.schema is required by default)
+include /etc/openldap/schema/core.schema
+
+## needed for sambaAccount
+include /etc/openldap/schema/cosine.schema
+include /etc/openldap/schema/inetorgperson.schema
+include /etc/openldap/schema/samba.schema
+
+## uncomment this line if you want to support the RFC2307 (NIS) schema
+## include /etc/openldap/schema/nis.schema
+
+....</PRE
+></P
+><P
+>It is recommended that you maintain some indices on some of the most usefull attributes,
+like in the following example, to speed up searches made on sambaAccount objectclasses
+(and possibly posixAccount and posixGroup as well).</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+># Indices to maintain
+## required by OpenLDAP 2.0
+index objectclass eq
+
+## support pb_getsampwnam()
+index uid pres,eq
+## support pdb_getsambapwrid()
+index rid eq
+
+## uncomment these if you are storing posixAccount and
+## posixGroup entries in the directory as well
+##index uidNumber eq
+##index gidNumber eq
+##index cn eq
+##index memberUid eq</PRE
+></P
+></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN2822">19.5.2. Configuring Samba</H2
+><P
+>The following parameters are available in smb.conf only with <TT
+CLASS="PARAMETER"
+><I
+>--with-ldapsam</I
+></TT
+>
+was included with compiling Samba.</P
+><P
+></P
+><UL
+><LI
+><P
+><A
+HREF="smb.conf.5.html#LDAPSSL"
+TARGET="_top"
+>ldap ssl</A
+></P
+></LI
+><LI
+><P
+><A
+HREF="smb.conf.5.html#LDAPSERVER"
+TARGET="_top"
+>ldap server</A
+></P
+></LI
+><LI
+><P
+><A
+HREF="smb.conf.5.html#LDAPADMINDN"
+TARGET="_top"
+>ldap admin dn</A
+></P
+></LI
+><LI
+><P
+><A
+HREF="smb.conf.5.html#LDAPSUFFIX"
+TARGET="_top"
+>ldap suffix</A
+></P
+></LI
+><LI
+><P
+><A
+HREF="smb.conf.5.html#LDAPFILTER"
+TARGET="_top"
+>ldap filter</A
+></P
+></LI
+><LI
+><P
+><A
+HREF="smb.conf.5.html#LDAPPORT"
+TARGET="_top"
+>ldap port</A
+></P
+></LI
+></UL
+><P
+>These are described in the <A
+HREF="smb.conf.5.html"
+TARGET="_top"
+>smb.conf(5)</A
+> man
+page and so will not be repeated here. However, a sample smb.conf file for
+use with an LDAP directory could appear as</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>## /usr/local/samba/lib/smb.conf
+[global]
+ security = user
+ encrypt passwords = yes
+
+ netbios name = TASHTEGO
+ workgroup = NARNIA
+
+ # ldap related parameters
+
+ # define the DN to use when binding to the directory servers
+ # The password for this DN is not stored in smb.conf. Rather it
+ # must be set by using 'smbpasswd -w <TT
+CLASS="REPLACEABLE"
+><I
+>secretpw</I
+></TT
+>' to store the
+ # passphrase in the secrets.tdb file. If the "ldap admin dn" values
+ # changes, this password will need to be reset.
+ ldap admin dn = "cn=Samba Manager,ou=people,dc=samba,dc=org"
+
+ # specify the LDAP server's hostname (defaults to locahost)
+ ldap server = ahab.samba.org
+
+ # Define the SSL option when connecting to the directory
+ # ('off', 'start tls', or 'on' (default))
+ ldap ssl = start tls
+
+ # define the port to use in the LDAP session (defaults to 636 when
+ # "ldap ssl = on")
+ ldap port = 389
+
+ # specify the base DN to use when searching the directory
+ ldap suffix = "ou=people,dc=samba,dc=org"
+
+ # generally the default ldap search filter is ok
+ # ldap filter = "(&amp;(uid=%u)(objectclass=sambaAccount))"</PRE
+></P
+></DIV
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN2850">19.6. Accounts and Groups management</H1
+><P
+>As users accounts are managed thru the sambaAccount objectclass, you should
+modify you existing administration tools to deal with sambaAccount attributes.</P
+><P
+>Machines accounts are managed with the sambaAccount objectclass, just
+like users accounts. However, it's up to you to stored thoses accounts
+in a different tree of you LDAP namespace: you should use
+"ou=Groups,dc=plainjoe,dc=org" to store groups and
+"ou=People,dc=plainjoe,dc=org" to store users. Just configure your
+NSS and PAM accordingly (usually, in the /etc/ldap.conf configuration
+file).</P
+><P
+>In Samba release 2.2.3, the group management system is based on posix
+groups. This meand that Samba make usage of the posixGroup objectclass.
+For now, there is no NT-like group system management (global and local
+groups).</P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN2855">19.7. Security and sambaAccount</H1
+><P
+>There are two important points to remember when discussing the security
+of sambaAccount entries in the directory.</P
+><P
+></P
+><UL
+><LI
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Never</I
+></SPAN
+> retrieve the lmPassword or
+ ntPassword attribute values over an unencrypted LDAP session.</P
+></LI
+><LI
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Never</I
+></SPAN
+> allow non-admin users to
+ view the lmPassword or ntPassword attribute values.</P
+></LI
+></UL
+><P
+>These password hashes are clear text equivalents and can be used to impersonate
+the user without deriving the original clear text strings. For more information
+on the details of LM/NT password hashes, refer to the <A
+HREF="ENCRYPTION.html"
+TARGET="_top"
+>ENCRYPTION chapter</A
+> of the Samba-HOWTO-Collection.</P
+><P
+>To remedy the first security issue, the "ldap ssl" smb.conf parameter defaults
+to require an encrypted session (<B
+CLASS="COMMAND"
+>ldap ssl = on</B
+>) using
+the default port of 636
+when contacting the directory server. When using an OpenLDAP 2.0 server, it
+is possible to use the use the StartTLS LDAP extended operation in the place of
+LDAPS. In either case, you are strongly discouraged to disable this security
+(<B
+CLASS="COMMAND"
+>ldap ssl = off</B
+>).</P
+><P
+>Note that the LDAPS protocol is deprecated in favor of the LDAPv3 StartTLS
+extended operation. However, the OpenLDAP library still provides support for
+the older method of securing communication between clients and servers.</P
+><P
+>The second security precaution is to prevent non-administrative users from
+harvesting password hashes from the directory. This can be done using the
+following ACL in <TT
+CLASS="FILENAME"
+>slapd.conf</TT
+>:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>## allow the "ldap admin dn" access, but deny everyone else
+access to attrs=lmPassword,ntPassword
+ by dn="cn=Samba Admin,ou=people,dc=plainjoe,dc=org" write
+ by * none</PRE
+></P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN2875">19.8. LDAP specials attributes for sambaAccounts</H1
+><P
+>The sambaAccount objectclass is composed of the following attributes:</P
+><P
+></P
+><UL
+><LI
+><P
+><TT
+CLASS="CONSTANT"
+>lmPassword</TT
+>: the LANMAN password 16-byte hash stored as a character
+ representation of a hexidecimal string.</P
+></LI
+><LI
+><P
+><TT
+CLASS="CONSTANT"
+>ntPassword</TT
+>: the NT password hash 16-byte stored as a character
+ representation of a hexidecimal string.</P
+></LI
+><LI
+><P
+><TT
+CLASS="CONSTANT"
+>pwdLastSet</TT
+>: The integer time in seconds since 1970 when the
+ <TT
+CLASS="CONSTANT"
+>lmPassword</TT
+> and <TT
+CLASS="CONSTANT"
+>ntPassword</TT
+> attributes were last set.
+ </P
+></LI
+><LI
+><P
+><TT
+CLASS="CONSTANT"
+>acctFlags</TT
+>: string of 11 characters surrounded by square brackets []
+ representing account flags such as U (user), W(workstation), X(no password expiration), and
+ D(disabled).</P
+></LI
+><LI
+><P
+><TT
+CLASS="CONSTANT"
+>logonTime</TT
+>: Integer value currently unused</P
+></LI
+><LI
+><P
+><TT
+CLASS="CONSTANT"
+>logoffTime</TT
+>: Integer value currently unused</P
+></LI
+><LI
+><P
+><TT
+CLASS="CONSTANT"
+>kickoffTime</TT
+>: Integer value currently unused</P
+></LI
+><LI
+><P
+><TT
+CLASS="CONSTANT"
+>pwdCanChange</TT
+>: Integer value currently unused</P
+></LI
+><LI
+><P
+><TT
+CLASS="CONSTANT"
+>pwdMustChange</TT
+>: Integer value currently unused</P
+></LI
+><LI
+><P
+><TT
+CLASS="CONSTANT"
+>homeDrive</TT
+>: specifies the drive letter to which to map the
+ UNC path specified by homeDirectory. The drive letter must be specified in the form "X:"
+ where X is the letter of the drive to map. Refer to the "logon drive" parameter in the
+ smb.conf(5) man page for more information.</P
+></LI
+><LI
+><P
+><TT
+CLASS="CONSTANT"
+>scriptPath</TT
+>: The scriptPath property specifies the path of
+ the user's logon script, .CMD, .EXE, or .BAT file. The string can be null. The path
+ is relative to the netlogon share. Refer to the "logon script" parameter in the
+ smb.conf(5) man page for more information.</P
+></LI
+><LI
+><P
+><TT
+CLASS="CONSTANT"
+>profilePath</TT
+>: specifies a path to the user's profile.
+ This value can be a null string, a local absolute path, or a UNC path. Refer to the
+ "logon path" parameter in the smb.conf(5) man page for more information.</P
+></LI
+><LI
+><P
+><TT
+CLASS="CONSTANT"
+>smbHome</TT
+>: The homeDirectory property specifies the path of
+ the home directory for the user. The string can be null. If homeDrive is set and specifies
+ a drive letter, homeDirectory should be a UNC path. The path must be a network
+ UNC path of the form \\server\share\directory. This value can be a null string.
+ Refer to the "logon home" parameter in the smb.conf(5) man page for more information.
+ </P
+></LI
+><LI
+><P
+><TT
+CLASS="CONSTANT"
+>userWorkstation</TT
+>: character string value currently unused.
+ </P
+></LI
+><LI
+><P
+><TT
+CLASS="CONSTANT"
+>rid</TT
+>: the integer representation of the user's relative identifier
+ (RID).</P
+></LI
+><LI
+><P
+><TT
+CLASS="CONSTANT"
+>primaryGroupID</TT
+>: the relative identifier (RID) of the primary group
+ of the user.</P
+></LI
+></UL
+><P
+>The majority of these parameters are only used when Samba is acting as a PDC of
+a domain (refer to the <A
+HREF="Samba-PDC-HOWTO.html"
+TARGET="_top"
+>Samba-PDC-HOWTO</A
+> for details on
+how to configure Samba as a Primary Domain Controller). The following four attributes
+are only stored with the sambaAccount entry if the values are non-default values:</P
+><P
+></P
+><UL
+><LI
+><P
+>smbHome</P
+></LI
+><LI
+><P
+>scriptPath</P
+></LI
+><LI
+><P
+>logonPath</P
+></LI
+><LI
+><P
+>homeDrive</P
+></LI
+></UL
+><P
+>These attributes are only stored with the sambaAccount entry if
+the values are non-default values. For example, assume TASHTEGO has now been
+configured as a PDC and that <B
+CLASS="COMMAND"
+>logon home = \\%L\%u</B
+> was defined in
+its <TT
+CLASS="FILENAME"
+>smb.conf</TT
+> file. When a user named "becky" logons to the domain,
+the <TT
+CLASS="PARAMETER"
+><I
+>logon home</I
+></TT
+> string is expanded to \\TASHTEGO\becky.
+If the smbHome attribute exists in the entry "uid=becky,ou=people,dc=samba,dc=org",
+this value is used. However, if this attribute does not exist, then the value
+of the <TT
+CLASS="PARAMETER"
+><I
+>logon home</I
+></TT
+> parameter is used in its place. Samba
+will only write the attribute value to the directory entry is the value is
+something other than the default (e.g. \\MOBY\becky).</P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN2945">19.9. Example LDIF Entries for a sambaAccount</H1
+><P
+>The following is a working LDIF with the inclusion of the posixAccount objectclass:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>dn: uid=guest2, ou=people,dc=plainjoe,dc=org
+ntPassword: 878D8014606CDA29677A44EFA1353FC7
+pwdMustChange: 2147483647
+primaryGroupID: 1201
+lmPassword: 552902031BEDE9EFAAD3B435B51404EE
+pwdLastSet: 1010179124
+logonTime: 0
+objectClass: sambaAccount
+uid: guest2
+kickoffTime: 2147483647
+acctFlags: [UX ]
+logoffTime: 2147483647
+rid: 19006
+pwdCanChange: 0</PRE
+></P
+><P
+>The following is an LDIF entry for using both the sambaAccount and
+posixAccount objectclasses:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>dn: uid=gcarter, ou=people,dc=plainjoe,dc=org
+logonTime: 0
+displayName: Gerald Carter
+lmPassword: 552902031BEDE9EFAAD3B435B51404EE
+primaryGroupID: 1201
+objectClass: posixAccount
+objectClass: sambaAccount
+acctFlags: [UX ]
+userPassword: {crypt}BpM2ej8Rkzogo
+uid: gcarter
+uidNumber: 9000
+cn: Gerald Carter
+loginShell: /bin/bash
+logoffTime: 2147483647
+gidNumber: 100
+kickoffTime: 2147483647
+pwdLastSet: 1010179230
+rid: 19000
+homeDirectory: /home/tashtego/gcarter
+pwdCanChange: 0
+pwdMustChange: 2147483647
+ntPassword: 878D8014606CDA29677A44EFA1353FC7</PRE
+></P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN2953">19.10. Comments</H1
+><P
+>Please mail all comments regarding this HOWTO to <A
+HREF="mailto:jerry@samba.org"
+TARGET="_top"
+>jerry@samba.org</A
+>. This documents was
+last updated to reflect the Samba 2.2.3 release.&#13;</P
+></DIV
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+SUMMARY="Footer navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="vfs.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="samba-howto-collection.html"
+ACCESSKEY="H"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="cvs-access.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>Stackable VFS modules</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="optional.html"
+ACCESSKEY="U"
+>Up</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>HOWTO Access Samba source code via CVS</TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+> \ No newline at end of file
diff --git a/docs/htmldocs/samba-pdc.html b/docs/htmldocs/samba-pdc.html
index 951dd2ea96..93bbc727d4 100644
--- a/docs/htmldocs/samba-pdc.html
+++ b/docs/htmldocs/samba-pdc.html
@@ -1,498 +1,2606 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter5.
-Samba as an NT4 or Win2k Primary Domain Controller
-</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"><link rel="home" href="index.html" title="SAMBA Project Documentation"><link rel="up" href="type.html" title="PartII.Server Configuration Basics"><link rel="previous" href="securitylevels.html" title="Chapter4.Samba as Stand-Alone Server"><link rel="next" href="samba-bdc.html" title="Chapter6.
-Samba Backup Domain Controller to Samba Domain Control
-"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter5.
-Samba as an NT4 or Win2k Primary Domain Controller
-</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="securitylevels.html">Prev</a></td><th width="60%" align="center">PartII.Server Configuration Basics</th><td width="20%" align="right"><a accesskey="n" href="samba-bdc.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="samba-pdc"></a>Chapter5.
-Samba as an NT4 or Win2k Primary Domain Controller
-</h2></div><div><div class="author"><h3 class="author">Gerald (Jerry) Carter</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt>&lt;<a href="mailto:jerry@samba.org">jerry@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author">John H. Terpstra</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt>&lt;<a href="mailto:jht@samba.org">jht@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author">David Bannon</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt>&lt;<a href="mailto:dbannon@samba.org">dbannon@samba.org</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate"> (26 Apr 2001) </p></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="samba-pdc.html#id2807495">Prerequisite Reading</a></dt><dt><a href="samba-pdc.html#id2807518">
-Background
-</a></dt><dt><a href="samba-pdc.html#id2877458">Configuring the Samba Domain Controller</a></dt><dt><a href="samba-pdc.html#id2877759">Creating Machine Trust Accounts and Joining Clients to the Domain</a></dt><dd><dl><dt><a href="samba-pdc.html#id2878028">Manual Creation of Machine Trust Accounts</a></dt><dt><a href="samba-pdc.html#id2878262">&quot;On-the-Fly&quot; Creation of Machine Trust Accounts</a></dt><dt><a href="samba-pdc.html#id2878318">Joining the Client to the Domain</a></dt></dl></dd><dt><a href="samba-pdc.html#id2878425">Common Problems and Errors</a></dt><dd><dl><dt><a href="samba-pdc.html#id2878432">I cannot include a '$' in a machine name</a></dt><dt><a href="samba-pdc.html#id2878470">I get told &quot;You already have a connection to the Domain....&quot;
-or &quot;Cannot join domain, the credentials supplied conflict with an
-existing set..&quot; when creating a machine trust account.</a></dt><dt><a href="samba-pdc.html#id2878517">The system can not log you on (C000019B)....</a></dt><dt><a href="samba-pdc.html#id2878568">The machine trust account for this computer either does not
-exist or is not accessible.</a></dt><dt><a href="samba-pdc.html#id2878617">When I attempt to login to a Samba Domain from a NT4/W2K workstation,
-I get a message about my account being disabled.</a></dt></dl></dd><dt><a href="samba-pdc.html#id2878642">Domain Control for Windows 9x/ME</a></dt><dd><dl><dt><a href="samba-pdc.html#id2878805">Configuration Instructions: Network Logons</a></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2807495"></a>Prerequisite Reading</h2></div></div><p>
-Before you continue reading in this chapter, please make sure
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<HTML
+><HEAD
+><TITLE
+>How to Configure Samba as a NT4 Primary Domain Controller</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
+REL="HOME"
+TITLE="SAMBA Project Documentation"
+HREF="samba-howto-collection.html"><LINK
+REL="UP"
+TITLE="Type of installation"
+HREF="type.html"><LINK
+REL="PREVIOUS"
+TITLE="User and Share security level (for servers not in a domain)"
+HREF="securitylevels.html"><LINK
+REL="NEXT"
+TITLE="How to Act as a Backup Domain Controller in a Purely Samba Controlled Domain"
+HREF="samba-bdc.html"></HEAD
+><BODY
+CLASS="CHAPTER"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><TABLE
+SUMMARY="Header navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>SAMBA Project Documentation</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="securitylevels.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+></TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="samba-bdc.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="CHAPTER"
+><H1
+><A
+NAME="SAMBA-PDC">Chapter 6. How to Configure Samba as a NT4 Primary Domain Controller</H1
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN575">6.1. Prerequisite Reading</H1
+><P
+>Before you continue reading in this chapter, please make sure
that you are comfortable with configuring basic files services
in smb.conf and how to enable and administer password
encryption in Samba. Theses two topics are covered in the
-<tt>smb.conf</tt> manpage.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2807518"></a>
-Background
-</h2></div></div><p>
-This article outlines the steps necessary for configuring Samba as a PDC.
-It is necessary to have a working Samba server prior to implementing the
-PDC functionality.
-</p><div class="itemizedlist"><ul type="disc"><li><p>
- Domain logons for Windows NT 4.0 / 200x / XP Professional clients.
- </p></li><li><p>
- Placing Windows 9x / Me clients in user level security
- </p></li><li><p>
- Retrieving a list of users and groups from a Samba PDC to
- Windows 9x / Me / NT / 200x / XP Professional clients
- </p></li><li><p>
- Roaming Profiles
- </p></li><li><p>
- Network/System Policies
- </p></li></ul></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-Roaming Profiles and System/Network policies are advanced network administration topics
-that are covered separately in this document.
-</p></div><p>
-The following functionalities are new to the Samba 3.0 release:
-</p><div class="itemizedlist"><ul type="disc"><li><p>
- Windows NT 4 domain trusts
- </p></li><li><p>
- Adding users via the User Manager for Domains
- </p></li></ul></div><p>
-The following functionalities are NOT provided by Samba 3.0:
-</p><div class="itemizedlist"><ul type="disc"><li><p>
- SAM replication with Windows NT 4.0 Domain Controllers
+<A
+HREF="smb.conf.5.html"
+TARGET="_top"
+><TT
+CLASS="FILENAME"
+>smb.conf(5)</TT
+></A
+>
+manpage and the <A
+HREF="ENCRYPTION.html"
+TARGET="_top"
+>Encryption chapter</A
+>
+of this HOWTO Collection.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN581">6.2. Background</H1
+><DIV
+CLASS="NOTE"
+><P
+></P
+><TABLE
+CLASS="NOTE"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/note.gif"
+HSPACE="5"
+ALT="Note"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Author's Note:</I
+></SPAN
+> This document is a combination
+of David Bannon's "Samba 2.2 PDC HOWTO" and "Samba NT Domain FAQ".
+Both documents are superseded by this one.</P
+></TD
+></TR
+></TABLE
+></DIV
+><P
+>Versions of Samba prior to release 2.2 had marginal capabilities to act
+as a Windows NT 4.0 Primary Domain Controller
+
+(PDC). With Samba 2.2.0, we are proud to announce official support for
+Windows NT 4.0-style domain logons from Windows NT 4.0 and Windows
+2000 clients. This article outlines the steps
+necessary for configuring Samba as a PDC. It is necessary to have a
+working Samba server prior to implementing the PDC functionality. If
+you have not followed the steps outlined in <A
+HREF="UNIX_INSTALL.html"
+TARGET="_top"
+> UNIX_INSTALL.html</A
+>, please make sure
+that your server is configured correctly before proceeding. Another
+good resource in the <A
+HREF="smb.conf.5.html"
+TARGET="_top"
+>smb.conf(5) man
+page</A
+>. The following functionality should work in 2.2:</P
+><P
+></P
+><UL
+><LI
+><P
+> domain logons for Windows NT 4.0/2000 clients.
+ </P
+></LI
+><LI
+><P
+> placing a Windows 9x client in user level security
+ </P
+></LI
+><LI
+><P
+> retrieving a list of users and groups from a Samba PDC to
+ Windows 9x/NT/2000 clients
+ </P
+></LI
+><LI
+><P
+> roving (roaming) user profiles
+ </P
+></LI
+><LI
+><P
+> Windows NT 4.0-style system policies
+ </P
+></LI
+></UL
+><P
+>The following pieces of functionality are not included in the 2.2 release:</P
+><P
+></P
+><UL
+><LI
+><P
+> Windows NT 4 domain trusts
+ </P
+></LI
+><LI
+><P
+> SAM replication with Windows NT 4.0 Domain Controllers
(i.e. a Samba PDC and a Windows NT BDC or vice versa)
- </p></li><li><p>
- Acting as a Windows 2000 Domain Controller (i.e. Kerberos and
+ </P
+></LI
+><LI
+><P
+> Adding users via the User Manager for Domains
+ </P
+></LI
+><LI
+><P
+> Acting as a Windows 2000 Domain Controller (i.e. Kerberos and
Active Directory)
- </p></li></ul></div><p>
-Please note that Windows 9x / Me / XP Home clients are not true members of a domain
+ </P
+></LI
+></UL
+><P
+>Please note that Windows 9x clients are not true members of a domain
for reasons outlined in this article. Therefore the protocol for
-support of Windows 9x-style domain logons is completely different
-from NT4 / Win2k type domain logons and has been officially supported for some
-time.
-</p><p><span class="emphasis"><em>
-MS Windows XP Home edition is NOT able to join a domain and does not permit
-the use of domain logons.</em></span>
-</p><p>
-Implementing a Samba PDC can basically be divided into 3 broad
-steps.
-</p><div class="orderedlist"><ol type="1"><li><p>
- Configuring the Samba PDC
- </p></li><li><p>
- Creating machine trust accounts and joining clients to the domain
- </p></li><li><p>
- Adding and managing domain user accounts
- </p></li></ol></div><p>
-There are other minor details such as user profiles, system
+support Windows 9x-style domain logons is completely different
+from NT4 domain logons and has been officially supported for some
+time.</P
+><P
+>Implementing a Samba PDC can basically be divided into 2 broad
+steps.</P
+><P
+></P
+><OL
+TYPE="1"
+><LI
+><P
+> Configuring the Samba PDC
+ </P
+></LI
+><LI
+><P
+> Creating machine trust accounts and joining clients
+ to the domain
+ </P
+></LI
+></OL
+><P
+>There are other minor details such as user profiles, system
policies, etc... However, these are not necessarily specific
to a Samba PDC as much as they are related to Windows NT networking
-concepts.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2877458"></a>Configuring the Samba Domain Controller</h2></div></div><p>
-The first step in creating a working Samba PDC is to
-understand the parameters necessary in smb.conf. Here we
-attempt to explain the parameters that are covered in
-the <tt>smb.conf</tt> man page.
-</p><p>
-Here is an example <tt>smb.conf</tt> for acting as a PDC:
-</p><pre class="programlisting">
-[global]
+concepts. They will be mentioned only briefly here.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN620">6.3. Configuring the Samba Domain Controller</H1
+><P
+>The first step in creating a working Samba PDC is to
+understand the parameters necessary in smb.conf. I will not
+attempt to re-explain the parameters here as they are more that
+adequately covered in <A
+HREF="smb.conf.5.html"
+TARGET="_top"
+> the smb.conf
+man page</A
+>. For convenience, the parameters have been
+linked with the actual smb.conf description.</P
+><P
+>Here is an example <TT
+CLASS="FILENAME"
+>smb.conf</TT
+> for acting as a PDC:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>[global]
; Basic server settings
- <a href="smb.conf.5.html#NETBIOSNAME" target="_top">netbios name</a> = <i><tt>POGO</tt></i>
- <a href="smb.conf.5.html#WORKGROUP" target="_top">workgroup</a> = <i><tt>NARNIA</tt></i>
-
- ; User and Machine Account Backends
- ; Choices are: tdbsam, tdbsam_nua, smbpasswd, smbpasswd_nua, ldapsam, ldapsam_nua, ...
- ; mysqlsam, xmlsam, guest
- <a href="smb.conf.5.html#PASSDBBACKEND" target="_top">passdb backend</a> = ldapsam, guest
+ <A
+HREF="smb.conf.5.html#NETBIOSNAME"
+TARGET="_top"
+>netbios name</A
+> = <TT
+CLASS="REPLACEABLE"
+><I
+>POGO</I
+></TT
+>
+ <A
+HREF="smb.conf.5.html#WORKGROUP"
+TARGET="_top"
+>workgroup</A
+> = <TT
+CLASS="REPLACEABLE"
+><I
+>NARNIA</I
+></TT
+>
; we should act as the domain and local master browser
- <a href="smb.conf.5.html#OSLEVEL" target="_top">os level</a> = 64
- <a href="smb.conf.5.html#PERFERREDMASTER" target="_top">preferred master</a> = yes
- <a href="smb.conf.5.html#DOMAINMASTER" target="_top">domain master</a> = yes
- <a href="smb.conf.5.html#LOCALMASTER" target="_top">local master</a> = yes
+ <A
+HREF="smb.conf.5.html#OSLEVEL"
+TARGET="_top"
+>os level</A
+> = 64
+ <A
+HREF="smb.conf.5.html#PERFERREDMASTER"
+TARGET="_top"
+>preferred master</A
+> = yes
+ <A
+HREF="smb.conf.5.html#DOMAINMASTER"
+TARGET="_top"
+>domain master</A
+> = yes
+ <A
+HREF="smb.conf.5.html#LOCALMASTER"
+TARGET="_top"
+>local master</A
+> = yes
; security settings (must user security = user)
- <a href="smb.conf.5.html#SECURITYEQUALSUSER" target="_top">security</a> = user
+ <A
+HREF="smb.conf.5.html#SECURITYEQUALSUSER"
+TARGET="_top"
+>security</A
+> = user
; encrypted passwords are a requirement for a PDC
- <a href="smb.conf.5.html#ENCRYPTPASSWORDS" target="_top">encrypt passwords</a> = yes
+ <A
+HREF="smb.conf.5.html#ENCRYPTPASSWORDS"
+TARGET="_top"
+>encrypt passwords</A
+> = yes
; support domain logons
- <a href="smb.conf.5.html#DOMAINLOGONS" target="_top">domain logons</a> = yes
+ <A
+HREF="smb.conf.5.html#DOMAINLOGONS"
+TARGET="_top"
+>domain logons</A
+> = yes
; where to store user profiles?
- <a href="smb.conf.5.html#LOGONPATH" target="_top">logon path</a> = \\%N\profiles\%u
+ <A
+HREF="smb.conf.5.html#LOGONPATH"
+TARGET="_top"
+>logon path</A
+> = \\%N\profiles\%u
- ; where is a user's home directory and where should it be mounted at?
- <a href="smb.conf.5.html#LOGONDRIVE" target="_top">logon drive</a> = H:
- <a href="smb.conf.5.html#LOGONHOME" target="_top">logon home</a> = \\homeserver\%u
+ ; where is a user's home directory and where should it
+ ; be mounted at?
+ <A
+HREF="smb.conf.5.html#LOGONDRIVE"
+TARGET="_top"
+>logon drive</A
+> = H:
+ <A
+HREF="smb.conf.5.html#LOGONHOME"
+TARGET="_top"
+>logon home</A
+> = \\homeserver\%u
; specify a generic logon script for all users
; this is a relative **DOS** path to the [netlogon] share
- <a href="smb.conf.5.html#LOGONSCRIPT" target="_top">logon script</a> = logon.cmd
+ <A
+HREF="smb.conf.5.html#LOGONSCRIPT"
+TARGET="_top"
+>logon script</A
+> = logon.cmd
; necessary share for domain controller
[netlogon]
- <a href="smb.conf.5.html#PATH" target="_top">path</a> = /usr/local/samba/lib/netlogon
- <a href="smb.conf.5.html#READONLY" target="_top">read only</a> = yes
- <a href="smb.conf.5.html#WRITELIST" target="_top">write list</a> = <i><tt>ntadmin</tt></i>
+ <A
+HREF="smb.conf.5.html#PATH"
+TARGET="_top"
+>path</A
+> = /usr/local/samba/lib/netlogon
+ <A
+HREF="smb.conf.5.html#READONLY"
+TARGET="_top"
+>read only</A
+> = yes
+ <A
+HREF="smb.conf.5.html#WRITELIST"
+TARGET="_top"
+>write list</A
+> = <TT
+CLASS="REPLACEABLE"
+><I
+>ntadmin</I
+></TT
+>
; share for storing user profiles
[profiles]
- <a href="smb.conf.5.html#PATH" target="_top">path</a> = /export/smb/ntprofile
- <a href="smb.conf.5.html#READONLY" target="_top">read only</a> = no
- <a href="smb.conf.5.html#CREATEMASK" target="_top">create mask</a> = 0600
- <a href="smb.conf.5.html#DIRECTORYMASK" target="_top">directory mask</a> = 0700
-</pre><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-The above parameters make for a full set of parameters that may define the server's mode
-of operation. The following parameters are the essentials alone:
-
-</p><pre class="programlisting">
- workgroup = NARNIA
- domain logons = Yes
- security = User
-</pre><p>
-
-The additional parameters shown in the longer listing above just makes for a
-more complete environment.
-</p></div><p>
-There are a couple of points to emphasize in the above configuration.
-</p><div class="itemizedlist"><ul type="disc"><li><p>
- Encrypted passwords must be enabled. For more details on how
- to do this, refer to <a href="passdb.html" title="Chapter10.User information database">the User Database chapter</a>.
- </p></li><li><p>
- The server must support domain logons and a
- <tt>[netlogon]</tt> share
- </p></li><li><p>
- The server must be the domain master browser in order for Windows
+ <A
+HREF="smb.conf.5.html#PATH"
+TARGET="_top"
+>path</A
+> = /export/smb/ntprofile
+ <A
+HREF="smb.conf.5.html#READONLY"
+TARGET="_top"
+>read only</A
+> = no
+ <A
+HREF="smb.conf.5.html#CREATEMASK"
+TARGET="_top"
+>create mask</A
+> = 0600
+ <A
+HREF="smb.conf.5.html#DIRECTORYMASK"
+TARGET="_top"
+>directory mask</A
+> = 0700</PRE
+></P
+><P
+>There are a couple of points to emphasize in the above configuration.</P
+><P
+></P
+><UL
+><LI
+><P
+> Encrypted passwords must be enabled. For more details on how
+ to do this, refer to <A
+HREF="ENCRYPTION.html"
+TARGET="_top"
+>ENCRYPTION.html</A
+>.
+ </P
+></LI
+><LI
+><P
+> The server must support domain logons and a
+ <TT
+CLASS="FILENAME"
+>[netlogon]</TT
+> share
+ </P
+></LI
+><LI
+><P
+> The server must be the domain master browser in order for Windows
client to locate the server as a DC. Please refer to the various
Network Browsing documentation included with this distribution for
details.
- </p></li></ul></div><p>
-Samba 3.0 offers a complete implementation of group mapping
+ </P
+></LI
+></UL
+><P
+>As Samba 2.2 does not offer a complete implementation of group mapping
between Windows NT groups and Unix groups (this is really quite
-complicated to explain in a short space).
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2877759"></a>Creating Machine Trust Accounts and Joining Clients to the Domain</h2></div></div><p>
-A machine trust account is a Samba account that is used to
+complicated to explain in a short space), you should refer to the
+<A
+HREF="smb.conf.5.html#DOMAINADMINGROUP"
+TARGET="_top"
+>domain admin
+group</A
+> smb.conf parameter for information of creating "Domain
+Admins" style accounts.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN663">6.4. Creating Machine Trust Accounts and Joining Clients to the
+Domain</H1
+><P
+>A machine trust account is a Samba account that is used to
authenticate a client machine (rather than a user) to the Samba
-server. In Windows terminology, this is known as a &quot;Computer
-Account.&quot;</p><p>
-The password of a machine trust account acts as the shared secret for
+server. In Windows terminology, this is known as a "Computer
+Account."</P
+><P
+>The password of a machine trust account acts as the shared secret for
secure communication with the Domain Controller. This is a security
feature to prevent an unauthorized machine with the same NetBIOS name
from joining the domain and gaining access to domain user/group
-accounts. Windows NT, 200x, XP Professional clients use machine trust
-accounts, but Windows 9x / Me / XP Home clients do not. Hence, a
-Windows 9x / Me / XP Home client is never a true member of a domain
-because it does not possess a machine trust account, and thus has no
-shared secret with the domain controller.
-</p><p>A Windows PDC stores each machine trust account in the Windows
-Registry. A Samba-3 PDC also has to store machine trust account information
-in a suitable backend data store. With Samba-3 there can be multiple back-ends
-for this including:
-</p><div class="itemizedlist"><ul type="disc"><li><p>
- <span class="emphasis"><em>smbpasswd</em></span> - the plain ascii file stored used by
- earlier versions of Samba. This file configuration option requires
- a Unix/Linux system account for EVERY entry (ie: both for user and for
- machine accounts). This file will be located in the <span class="emphasis"><em>private</em></span>
- directory (default is /usr/local/samba/lib/private or on linux /etc/samba).
- </p></li><li><p>
- <span class="emphasis"><em>smbpasswd_nua</em></span> - This file is independant of the
- system wide user accounts. The use of this back-end option requires
- specification of the &quot;non unix account range&quot; option also. It is called
- smbpasswd and will be located in the <tt>private</tt> directory.
- </p></li><li><p>
- <span class="emphasis"><em>tdbsam</em></span> - a binary database backend that will be
- stored in the <span class="emphasis"><em>private</em></span> directory in a file called
- <span class="emphasis"><em>passwd.tdb</em></span>. The key benefit of this binary format
- file is that it can store binary objects that can not be accomodated
- in the traditional plain text smbpasswd file.
- </p></li><li><p>
- <span class="emphasis"><em>tdbsam_nua</em></span> like the smbpasswd_nua option above, this
- file allows the creation of arbitrary user and machine accounts without
- requiring that account to be added to the system (/etc/passwd) file. It
- too requires the specification of the &quot;non unix account range&quot; option
- in the [globals] section of the <tt>smb.conf</tt> file.
- </p></li><li><p>
- <span class="emphasis"><em>ldapsam</em></span> - An LDAP based back-end. Permits the
- LDAP server to be specified. eg: ldap://localhost or ldap://frodo.murphy.com
- </p></li><li><p>
- <span class="emphasis"><em>ldapsam_nua</em></span> - LDAP based back-end with no unix
- account requirement, like smbpasswd_nua and tdbsam_nua above.
- </p></li></ul></div><p>Read the chapter about the <a href="passdb.html" title="Chapter10.User information database">User Database</a>
-for details.</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-The new tdbsam and ldapsam account backends store vastly more information than
-smbpasswd is capable of. The new backend database includes capacity to specify
-per user settings for many parameters, over-riding global settings given in the
-<tt>smb.conf</tt> file. eg: logon drive, logon home, logon path, etc.
-</p></div><p>
-A Samba PDC, however, stores each machine trust account in two parts,
-as follows:
+accounts. Windows NT and 2000 clients use machine trust accounts, but
+Windows 9x clients do not. Hence, a Windows 9x client is never a true
+member of a domain because it does not possess a machine trust
+account, and thus has no shared secret with the domain controller.</P
+><P
+>A Windows PDC stores each machine trust account in the Windows
+Registry. A Samba PDC, however, stores each machine trust account
+in two parts, as follows:
-</p><div class="itemizedlist"><ul type="disc"><li><p>A Samba account, stored in the same location as user
+<P
+></P
+><UL
+><LI
+><P
+>A Samba account, stored in the same location as user
LanMan and NT password hashes (currently
- <tt>smbpasswd</tt>). The Samba account
- possesses and uses only the NT password hash.</p></li><li><p>A corresponding Unix account, typically stored in
- <tt>/etc/passwd</tt>. (Future releases will alleviate the need to
- create <tt>/etc/passwd</tt> entries.) </p></li></ul></div><p>
-</p><p>
-There are two ways to create machine trust accounts:
-</p><div class="itemizedlist"><ul type="disc"><li><p> Manual creation. Both the Samba and corresponding
- Unix account are created by hand.</p></li><li><p> &quot;On-the-fly&quot; creation. The Samba machine trust
+ <TT
+CLASS="FILENAME"
+>smbpasswd</TT
+>). The Samba account
+ possesses and uses only the NT password hash.</P
+></LI
+><LI
+><P
+>A corresponding Unix account, typically stored in
+ <TT
+CLASS="FILENAME"
+>/etc/passwd</TT
+>. (Future releases will alleviate the need to
+ create <TT
+CLASS="FILENAME"
+>/etc/passwd</TT
+> entries.) </P
+></LI
+></UL
+></P
+><P
+>There are two ways to create machine trust accounts:</P
+><P
+></P
+><UL
+><LI
+><P
+> Manual creation. Both the Samba and corresponding
+ Unix account are created by hand.</P
+></LI
+><LI
+><P
+> "On-the-fly" creation. The Samba machine trust
account is automatically created by Samba at the time the client
is joined to the domain. (For security, this is the
recommended method.) The corresponding Unix account may be
- created automatically or manually. </p></li></ul></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2878028"></a>Manual Creation of Machine Trust Accounts</h3></div></div><p>
-The first step in manually creating a machine trust account is to
+ created automatically or manually. </P
+></LI
+></UL
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN682">6.4.1. Manual Creation of Machine Trust Accounts</H2
+><P
+>The first step in manually creating a machine trust account is to
manually create the corresponding Unix account in
-<tt>/etc/passwd</tt>. This can be done using
-<b>vipw</b> or other 'add user' command that is normally
+<TT
+CLASS="FILENAME"
+>/etc/passwd</TT
+>. This can be done using
+<B
+CLASS="COMMAND"
+>vipw</B
+> or other 'add user' command that is normally
used to create new Unix accounts. The following is an example for a
-Linux based Samba server:
-</p><p>
- <tt>root# </tt><b>/usr/sbin/useradd -g 100 -d /dev/null -c <i><tt>&quot;machine
-nickname&quot;</tt></i> -s /bin/false <i><tt>machine_name</tt></i>$ </b>
-</p><p>
-<tt>root# </tt><b>passwd -l <i><tt>machine_name</tt></i>$</b>
-</p><p>On *BSD systems, this can be done using the 'chpass' utility:</p><p>
-<tt>root# </tt><b>chpass -a &quot;<i><tt>machine_name</tt></i>$:*:101:100::0:0:Workstation <i><tt>machine_name</tt></i>:/dev/null:/sbin/nologin&quot;</b>
-</p><p>
-The <tt>/etc/passwd</tt> entry will list the machine name
-with a &quot;$&quot; appended, won't have a password, will have a null shell and no
+Linux based Samba server:</P
+><P
+> <TT
+CLASS="PROMPT"
+>root# </TT
+><B
+CLASS="COMMAND"
+>/usr/sbin/useradd -g 100 -d /dev/null -c <TT
+CLASS="REPLACEABLE"
+><I
+>"machine
+nickname"</I
+></TT
+> -s /bin/false <TT
+CLASS="REPLACEABLE"
+><I
+>machine_name</I
+></TT
+>$ </B
+></P
+><P
+><TT
+CLASS="PROMPT"
+>root# </TT
+><B
+CLASS="COMMAND"
+>passwd -l <TT
+CLASS="REPLACEABLE"
+><I
+>machine_name</I
+></TT
+>$</B
+></P
+><P
+>On *BSD systems, this can be done using the 'chpass' utility:</P
+><P
+><TT
+CLASS="PROMPT"
+>root# </TT
+><B
+CLASS="COMMAND"
+>chpass -a "<TT
+CLASS="REPLACEABLE"
+><I
+>machine_name</I
+></TT
+>$:*:101:100::0:0:Workstation <TT
+CLASS="REPLACEABLE"
+><I
+>machine_name</I
+></TT
+>:/dev/null:/sbin/nologin"</B
+></P
+><P
+>The <TT
+CLASS="FILENAME"
+>/etc/passwd</TT
+> entry will list the machine name
+with a "$" appended, won't have a password, will have a null shell and no
home directory. For example a machine named 'doppy' would have an
-<tt>/etc/passwd</tt> entry like this:
-</p><pre class="programlisting">
-doppy$:x:505:501:<i><tt>machine_nickname</tt></i>:/dev/null:/bin/false
-</pre><p>
-Above, <i><tt>machine_nickname</tt></i> can be any
+<TT
+CLASS="FILENAME"
+>/etc/passwd</TT
+> entry like this:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>doppy$:x:505:501:<TT
+CLASS="REPLACEABLE"
+><I
+>machine_nickname</I
+></TT
+>:/dev/null:/bin/false</PRE
+></P
+><P
+>Above, <TT
+CLASS="REPLACEABLE"
+><I
+>machine_nickname</I
+></TT
+> can be any
descriptive name for the client, i.e., BasementComputer.
-<i><tt>machine_name</tt></i> absolutely must be the NetBIOS
-name of the client to be joined to the domain. The &quot;$&quot; must be
+<TT
+CLASS="REPLACEABLE"
+><I
+>machine_name</I
+></TT
+> absolutely must be the NetBIOS
+name of the client to be joined to the domain. The "$" must be
appended to the NetBIOS name of the client or Samba will not recognize
-this as a machine trust account.
-</p><p>
-Now that the corresponding Unix account has been created, the next step is to create
+this as a machine trust account.</P
+><P
+>Now that the corresponding Unix account has been created, the next step is to create
the Samba account for the client containing the well-known initial
-machine trust account password. This can be done using the <a href="smbpasswd.8.html" target="_top"><b>smbpasswd(8)</b></a> command
-as shown here:
-</p><p>
-<tt>root# </tt><b><tt>smbpasswd -a -m <i><tt>machine_name</tt></i></tt></b>
-</p><p>
-where <i><tt>machine_name</tt></i> is the machine's NetBIOS
+machine trust account password. This can be done using the <A
+HREF="smbpasswd.8.html"
+TARGET="_top"
+><B
+CLASS="COMMAND"
+>smbpasswd(8)</B
+></A
+> command
+as shown here:</P
+><P
+><TT
+CLASS="PROMPT"
+>root# </TT
+><B
+CLASS="COMMAND"
+>smbpasswd -a -m <TT
+CLASS="REPLACEABLE"
+><I
+>machine_name</I
+></TT
+></B
+></P
+><P
+>where <TT
+CLASS="REPLACEABLE"
+><I
+>machine_name</I
+></TT
+> is the machine's NetBIOS
name. The RID of the new machine account is generated from the UID of
-the corresponding Unix account.
-</p><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Join the client to the domain immediately</h3><p>
- Manually creating a machine trust account using this method is the
+the corresponding Unix account.</P
+><DIV
+CLASS="WARNING"
+><P
+></P
+><TABLE
+CLASS="WARNING"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/warning.gif"
+HSPACE="5"
+ALT="Warning"></TD
+><TH
+ALIGN="LEFT"
+VALIGN="CENTER"
+><B
+>Join the client to the domain immediately</B
+></TH
+></TR
+><TR
+><TD
+>&nbsp;</TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+> Manually creating a machine trust account using this method is the
equivalent of creating a machine trust account on a Windows NT PDC using
- the &quot;Server Manager&quot;. From the time at which the account is created
+ the "Server Manager". From the time at which the account is created
to the time which the client joins the domain and changes the password,
- your domain is vulnerable to an intruder joining your domain using
+ your domain is vulnerable to an intruder joining your domain using a
a machine with the same NetBIOS name. A PDC inherently trusts
members of the domain and will serve out a large degree of user
information to such clients. You have been warned!
- </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2878262"></a>&quot;On-the-Fly&quot; Creation of Machine Trust Accounts</h3></div></div><p>
-The second (and recommended) way of creating machine trust accounts is
+ </P
+></TD
+></TR
+></TABLE
+></DIV
+></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN723">6.4.2. "On-the-Fly" Creation of Machine Trust Accounts</H2
+><P
+>The second (and recommended) way of creating machine trust accounts is
simply to allow the Samba server to create them as needed when the client
-is joined to the domain. </p><p>Since each Samba machine trust account requires a corresponding
+is joined to the domain. </P
+><P
+>Since each Samba machine trust account requires a corresponding
Unix account, a method for automatically creating the
Unix account is usually supplied; this requires configuration of the
-<a href="smb.conf.5.html#ADDUSERSCRIPT" target="_top">add user script</a>
-option in <tt>smb.conf</tt>. This
+<A
+HREF="smb.conf.5.html#ADDUSERSCRIPT"
+TARGET="_top"
+>add user script</A
+>
+option in <TT
+CLASS="FILENAME"
+>smb.conf</TT
+>. This
method is not required, however; corresponding Unix accounts may also
-be created manually.
-</p><p>Below is an example for a RedHat 6.2 Linux system.
-</p><pre class="programlisting">
-[global]
- # &lt;...remainder of parameters...&gt;
- add user script = /usr/sbin/useradd -d /dev/null -g 100 -s /bin/false -M %u
-</pre></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2878318"></a>Joining the Client to the Domain</h3></div></div><p>
-The procedure for joining a client to the domain varies with the
-version of Windows.
-</p><div class="itemizedlist"><ul type="disc"><li><p><span class="emphasis"><em>Windows 2000</em></span></p><p>
- When the user elects to join the client to a domain, Windows prompts for
- an account and password that is privileged to join the domain. A Samba administrative
- account (i.e., a Samba account that has root privileges on the Samba server) must be
- entered here; the operation will fail if an ordinary user account is given.
- The password for this account should be set to a different password than the associated
- <tt>/etc/passwd</tt> entry, for security reasons.
- </p><p>
- The session key of the Samba administrative account acts as an
+be created manually.</P
+><P
+>Below is an example for a RedHat 6.2 Linux system.</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>[global]
+ # &#60;...remainder of parameters...&#62;
+ add user script = /usr/sbin/useradd -d /dev/null -g 100 -s /bin/false -M %u </PRE
+></P
+></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN732">6.4.3. Joining the Client to the Domain</H2
+><P
+>The procedure for joining a client to the domain varies with the
+version of Windows.</P
+><P
+></P
+><UL
+><LI
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Windows 2000</I
+></SPAN
+></P
+><P
+> When the user elects to join the client to a domain, Windows prompts for
+ an account and password that is privileged to join the domain. A
+ Samba administrative account (i.e., a Samba account that has root
+ privileges on the Samba server) must be entered here; the
+ operation will fail if an ordinary user account is given.
+ The password for this account should be
+ set to a different password than the associated
+ <TT
+CLASS="FILENAME"
+>/etc/passwd</TT
+> entry, for security
+ reasons. </P
+><P
+>The session key of the Samba administrative account acts as an
encryption key for setting the password of the machine trust
account. The machine trust account will be created on-the-fly, or
- updated if it already exists.
- </p></li><li><p><span class="emphasis"><em>Windows NT</em></span></p><p> If the machine trust account was created manually, on the
+ updated if it already exists.</P
+></LI
+><LI
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Windows NT</I
+></SPAN
+></P
+><P
+> If the machine trust account was created manually, on the
Identification Changes menu enter the domain name, but do not
- check the box &quot;Create a Computer Account in the Domain.&quot; In this case,
+ check the box "Create a Computer Account in the Domain." In this case,
the existing machine trust account is used to join the machine to
- the domain.</p><p> If the machine trust account is to be created
+ the domain.</P
+><P
+> If the machine trust account is to be created
on-the-fly, on the Identification Changes menu enter the domain
- name, and check the box &quot;Create a Computer Account in the Domain.&quot; In
+ name, and check the box "Create a Computer Account in the Domain." In
this case, joining the domain proceeds as above for Windows 2000
(i.e., you must supply a Samba administrative account when
- prompted).</p></li><li><p><span class="emphasis"><em>Samba</em></span></p><p>Joining a samba client to a domain is documented in
- the <a href="domain-member.html" title="Chapter8.Samba as a NT4 or Win2k domain member">Domain Member</a> chapter.
-</p></li></ul></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2878425"></a>Common Problems and Errors</h2></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2878432"></a>I cannot include a '$' in a machine name</h3></div></div><p>
-A 'machine name' in (typically) <tt>/etc/passwd</tt>
-of the machine name with a '$' appended. FreeBSD (and other BSD
-systems?) won't create a user with a '$' in their name.
-</p><p>
-The problem is only in the program used to make the entry. Once made, it works perfectly.
-Create a user without the '$' using <b>vipw</b> to edit the entry, adding
-the '$'. Or create the whole entry with vipw if you like, make sure you use a unique User ID!
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2878470"></a>I get told &quot;You already have a connection to the Domain....&quot;
-or &quot;Cannot join domain, the credentials supplied conflict with an
-existing set..&quot; when creating a machine trust account.</h3></div></div><p>
-This happens if you try to create a machine trust account from the
-machine itself and already have a connection (e.g. mapped drive)
-to a share (or IPC$) on the Samba PDC. The following command
-will remove all network drive connections:
-</p><p>
-<tt>C:\WINNT\&gt;</tt> <b>net use * /d</b>
-</p><p>
-Further, if the machine is already a 'member of a workgroup' that
-is the same name as the domain you are joining (bad idea) you will
-get this message. Change the workgroup name to something else, it
-does not matter what, reboot, and try again.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2878517"></a>The system can not log you on (C000019B)....</h3></div></div><p>I joined the domain successfully but after upgrading
-to a newer version of the Samba code I get the message, &quot;The system
-can not log you on (C000019B), Please try again or consult your
-system administrator&quot; when attempting to logon.
-</p><p>
-This occurs when the domain SID stored in the secrets.tdb database
-is changed. The most common cause of a change in domain SID is when
-the domain name and/or the server name (netbios name) is changed.
-The only way to correct the problem is to restore the original domain
-SID or remove the domain client from the domain and rejoin. The domain
-SID may be reset using either the net or rpcclient utilities.
-</p><p>
-The reset or change the domain SID you can use the net command as follows:
-
-</p><pre class="programlisting">
- net getlocalsid 'OLDNAME'
- net setlocalsid 'SID'
-</pre><p>
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2878568"></a>The machine trust account for this computer either does not
-exist or is not accessible.</h3></div></div><p>
-When I try to join the domain I get the message &quot;The machine account
-for this computer either does not exist or is not accessible&quot;. What's
-wrong?
-</p><p>
-This problem is caused by the PDC not having a suitable machine trust account.
-If you are using the <i><tt>add user script</tt></i> method to create
-accounts then this would indicate that it has not worked. Ensure the domain
-admin user system is working.
-</p><p>
-Alternatively if you are creating account entries manually then they
-have not been created correctly. Make sure that you have the entry
-correct for the machine trust account in smbpasswd file on the Samba PDC.
-If you added the account using an editor rather than using the smbpasswd
-utility, make sure that the account name is the machine NetBIOS name
-with a '$' appended to it ( i.e. computer_name$ ). There must be an entry
-in both /etc/passwd and the smbpasswd file. Some people have reported
-that inconsistent subnet masks between the Samba server and the NT
-client have caused this problem. Make sure that these are consistent
-for both client and server.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2878617"></a>When I attempt to login to a Samba Domain from a NT4/W2K workstation,
-I get a message about my account being disabled.</h3></div></div><p>
-At first be ensure to enable the useraccounts with <b>smbpasswd -e
-%user%</b>, this is normally done, when you create an account.
-</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2878642"></a>Domain Control for Windows 9x/ME</h2></div></div><p>
-A domain and a workgroup are exactly the same thing in terms of network
+ prompted).</P
+></LI
+></UL
+></DIV
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN747">6.5. Common Problems and Errors</H1
+><P
+></P
+><P
+></P
+><UL
+><LI
+><P
+> <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>I cannot include a '$' in a machine name.</I
+></SPAN
+>
+ </P
+><P
+> A 'machine name' in (typically) <TT
+CLASS="FILENAME"
+>/etc/passwd</TT
+>
+ of the machine name with a '$' appended. FreeBSD (and other BSD
+ systems?) won't create a user with a '$' in their name.
+ </P
+><P
+> The problem is only in the program used to make the entry, once
+ made, it works perfectly. So create a user without the '$' and
+ use <B
+CLASS="COMMAND"
+>vipw</B
+> to edit the entry, adding the '$'. Or create
+ the whole entry with vipw if you like, make sure you use a
+ unique User ID !
+ </P
+></LI
+><LI
+><P
+> <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>I get told "You already have a connection to the Domain...."
+ or "Cannot join domain, the credentials supplied conflict with an
+ existing set.." when creating a machine trust account.</I
+></SPAN
+>
+ </P
+><P
+> This happens if you try to create a machine trust account from the
+ machine itself and already have a connection (e.g. mapped drive)
+ to a share (or IPC$) on the Samba PDC. The following command
+ will remove all network drive connections:
+ </P
+><P
+> <TT
+CLASS="PROMPT"
+>C:\WINNT\&#62;</TT
+> <B
+CLASS="COMMAND"
+>net use * /d</B
+>
+ </P
+><P
+> Further, if the machine is a already a 'member of a workgroup' that
+ is the same name as the domain you are joining (bad idea) you will
+ get this message. Change the workgroup name to something else, it
+ does not matter what, reboot, and try again.
+ </P
+></LI
+><LI
+><P
+> <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>The system can not log you on (C000019B)....</I
+></SPAN
+>
+ </P
+><P
+>I joined the domain successfully but after upgrading
+ to a newer version of the Samba code I get the message, "The system
+ can not log you on (C000019B), Please try a gain or consult your
+ system administrator" when attempting to logon.
+ </P
+><P
+> This occurs when the domain SID stored in
+ <TT
+CLASS="FILENAME"
+>private/WORKGROUP.SID</TT
+> is
+ changed. For example, you remove the file and <B
+CLASS="COMMAND"
+>smbd</B
+> automatically
+ creates a new one. Or you are swapping back and forth between
+ versions 2.0.7, TNG and the HEAD branch code (not recommended). The
+ only way to correct the problem is to restore the original domain
+ SID or remove the domain client from the domain and rejoin.
+ </P
+></LI
+><LI
+><P
+> <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>The machine trust account for this computer either does not
+ exist or is not accessible.</I
+></SPAN
+>
+ </P
+><P
+> When I try to join the domain I get the message "The machine account
+ for this computer either does not exist or is not accessible". What's
+ wrong?
+ </P
+><P
+> This problem is caused by the PDC not having a suitable machine trust account.
+ If you are using the <TT
+CLASS="PARAMETER"
+><I
+>add user script</I
+></TT
+> method to create
+ accounts then this would indicate that it has not worked. Ensure the domain
+ admin user system is working.
+ </P
+><P
+> Alternatively if you are creating account entries manually then they
+ have not been created correctly. Make sure that you have the entry
+ correct for the machine trust account in smbpasswd file on the Samba PDC.
+ If you added the account using an editor rather than using the smbpasswd
+ utility, make sure that the account name is the machine NetBIOS name
+ with a '$' appended to it ( i.e. computer_name$ ). There must be an entry
+ in both /etc/passwd and the smbpasswd file. Some people have reported
+ that inconsistent subnet masks between the Samba server and the NT
+ client have caused this problem. Make sure that these are consistent
+ for both client and server.
+ </P
+></LI
+><LI
+><P
+> <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>When I attempt to login to a Samba Domain from a NT4/W2K workstation,
+ I get a message about my account being disabled.</I
+></SPAN
+>
+ </P
+><P
+> This problem is caused by a PAM related bug in Samba 2.2.0. This bug is
+ fixed in 2.2.1. Other symptoms could be unaccessible shares on
+ NT/W2K member servers in the domain or the following error in your smbd.log:
+ passdb/pampass.c:pam_account(268) PAM: UNKNOWN ERROR for User: %user%
+ </P
+><P
+> At first be ensure to enable the useraccounts with <B
+CLASS="COMMAND"
+>smbpasswd -e
+ %user%</B
+>, this is normally done, when you create an account.
+ </P
+><P
+> In order to work around this problem in 2.2.0, configure the
+ <TT
+CLASS="PARAMETER"
+><I
+>account</I
+></TT
+> control flag in
+ <TT
+CLASS="FILENAME"
+>/etc/pam.d/samba</TT
+> file as follows:
+ </P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+> account required pam_permit.so
+ </PRE
+></P
+><P
+> If you want to remain backward compatibility to samba 2.0.x use
+ <TT
+CLASS="FILENAME"
+>pam_permit.so</TT
+>, it's also possible to use
+ <TT
+CLASS="FILENAME"
+>pam_pwdb.so</TT
+>. There are some bugs if you try to
+ use <TT
+CLASS="FILENAME"
+>pam_unix.so</TT
+>, if you need this, be ensure to use
+ the most recent version of this file.
+ </P
+></LI
+></UL
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN795">6.6. System Policies and Profiles</H1
+><P
+>Much of the information necessary to implement System Policies and
+Roving User Profiles in a Samba domain is the same as that for
+implementing these same items in a Windows NT 4.0 domain.
+You should read the white paper <A
+HREF="http://www.microsoft.com/ntserver/management/deployment/planguide/prof_policies.asp"
+TARGET="_top"
+>Implementing
+Profiles and Policies in Windows NT 4.0</A
+> available from Microsoft.</P
+><P
+>Here are some additional details:</P
+><P
+></P
+><UL
+><LI
+><P
+> <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>What about Windows NT Policy Editor?</I
+></SPAN
+>
+ </P
+><P
+> To create or edit <TT
+CLASS="FILENAME"
+>ntconfig.pol</TT
+> you must use
+ the NT Server Policy Editor, <B
+CLASS="COMMAND"
+>poledit.exe</B
+> which
+ is included with NT Server but <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>not NT Workstation</I
+></SPAN
+>.
+ There is a Policy Editor on a NTws
+ but it is not suitable for creating <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Domain Policies</I
+></SPAN
+>.
+ Further, although the Windows 95
+ Policy Editor can be installed on an NT Workstation/Server, it will not
+ work with NT policies because the registry key that are set by the policy templates.
+ However, the files from the NT Server will run happily enough on an NTws.
+ You need <TT
+CLASS="FILENAME"
+>poledit.exe, common.adm</TT
+> and <TT
+CLASS="FILENAME"
+>winnt.adm</TT
+>. It is convenient
+ to put the two *.adm files in <TT
+CLASS="FILENAME"
+>c:\winnt\inf</TT
+> which is where
+ the binary will look for them unless told otherwise. Note also that that
+ directory is 'hidden'.
+ </P
+><P
+> The Windows NT policy editor is also included with the Service Pack 3 (and
+ later) for Windows NT 4.0. Extract the files using <B
+CLASS="COMMAND"
+>servicepackname /x</B
+>,
+ i.e. that's <B
+CLASS="COMMAND"
+>Nt4sp6ai.exe /x</B
+> for service pack 6a. The policy editor,
+ <B
+CLASS="COMMAND"
+>poledit.exe</B
+> and the associated template files (*.adm) should
+ be extracted as well. It is also possible to downloaded the policy template
+ files for Office97 and get a copy of the policy editor. Another possible
+ location is with the Zero Administration Kit available for download from Microsoft.
+ </P
+></LI
+><LI
+><P
+> <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Can Win95 do Policies?</I
+></SPAN
+>
+ </P
+><P
+> Install the group policy handler for Win9x to pick up group
+ policies. Look on the Win98 CD in <TT
+CLASS="FILENAME"
+>\tools\reskit\netadmin\poledit</TT
+>.
+ Install group policies on a Win9x client by double-clicking
+ <TT
+CLASS="FILENAME"
+>grouppol.inf</TT
+>. Log off and on again a couple of
+ times and see if Win98 picks up group policies. Unfortunately this needs
+ to be done on every Win9x machine that uses group policies....
+ </P
+><P
+> If group policies don't work one reports suggests getting the updated
+ (read: working) grouppol.dll for Windows 9x. The group list is grabbed
+ from /etc/group.
+ </P
+></LI
+><LI
+><P
+> <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>How do I get 'User Manager' and 'Server Manager'</I
+></SPAN
+>
+ </P
+><P
+> Since I don't need to buy an NT Server CD now, how do I get
+ the 'User Manager for Domains', the 'Server Manager'?
+ </P
+><P
+> Microsoft distributes a version of these tools called nexus for
+ installation on Windows 95 systems. The tools set includes
+ </P
+><P
+></P
+><UL
+><LI
+><P
+>Server Manager</P
+></LI
+><LI
+><P
+>User Manager for Domains</P
+></LI
+><LI
+><P
+>Event Viewer</P
+></LI
+></UL
+><P
+> Click here to download the archived file <A
+HREF="ftp://ftp.microsoft.com/Softlib/MSLFILES/NEXUS.EXE"
+TARGET="_top"
+>ftp://ftp.microsoft.com/Softlib/MSLFILES/NEXUS.EXE</A
+>
+ </P
+><P
+> The Windows NT 4.0 version of the 'User Manager for
+ Domains' and 'Server Manager' are available from Microsoft via ftp
+ from <A
+HREF="ftp://ftp.microsoft.com/Softlib/MSLFILES/SRVTOOLS.EXE"
+TARGET="_top"
+>ftp://ftp.microsoft.com/Softlib/MSLFILES/SRVTOOLS.EXE</A
+>
+ </P
+></LI
+></UL
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN839">6.7. What other help can I get?</H1
+><P
+>There are many sources of information available in the form
+of mailing lists, RFC's and documentation. The docs that come
+with the samba distribution contain very good explanations of
+general SMB topics such as browsing.</P
+><P
+></P
+><UL
+><LI
+><P
+> <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>What are some diagnostics tools I can use to debug the domain logon
+ process and where can I find them?</I
+></SPAN
+>
+ </P
+><P
+> One of the best diagnostic tools for debugging problems is Samba itself.
+ You can use the -d option for both smbd and nmbd to specify what
+ 'debug level' at which to run. See the man pages on smbd, nmbd and
+ smb.conf for more information on debugging options. The debug
+ level can range from 1 (the default) to 10 (100 for debugging passwords).
+ </P
+><P
+> Another helpful method of debugging is to compile samba using the
+ <B
+CLASS="COMMAND"
+>gcc -g </B
+> flag. This will include debug
+ information in the binaries and allow you to attach gdb to the
+ running smbd / nmbd process. In order to attach gdb to an smbd
+ process for an NT workstation, first get the workstation to make the
+ connection. Pressing ctrl-alt-delete and going down to the domain box
+ is sufficient (at least, on the first time you join the domain) to
+ generate a 'LsaEnumTrustedDomains'. Thereafter, the workstation
+ maintains an open connection, and therefore there will be an smbd
+ process running (assuming that you haven't set a really short smbd
+ idle timeout) So, in between pressing ctrl alt delete, and actually
+ typing in your password, you can gdb attach and continue.
+ </P
+><P
+> Some useful samba commands worth investigating:
+ </P
+><P
+></P
+><UL
+><LI
+><P
+>testparam | more</P
+></LI
+><LI
+><P
+>smbclient -L //{netbios name of server}</P
+></LI
+></UL
+><P
+> An SMB enabled version of tcpdump is available from
+ <A
+HREF="http://www.tcpdump.org/"
+TARGET="_top"
+>http://www.tcpdup.org/</A
+>.
+ Ethereal, another good packet sniffer for Unix and Win32
+ hosts, can be downloaded from <A
+HREF="http://www.ethereal.com/"
+TARGET="_top"
+>http://www.ethereal.com</A
+>.
+ </P
+><P
+> For tracing things on the Microsoft Windows NT, Network Monitor
+ (aka. netmon) is available on the Microsoft Developer Network CD's,
+ the Windows NT Server install CD and the SMS CD's. The version of
+ netmon that ships with SMS allows for dumping packets between any two
+ computers (i.e. placing the network interface in promiscuous mode).
+ The version on the NT Server install CD will only allow monitoring
+ of network traffic directed to the local NT box and broadcasts on the
+ local subnet. Be aware that Ethereal can read and write netmon
+ formatted files.
+ </P
+></LI
+><LI
+><P
+> <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>How do I install 'Network Monitor' on an NT Workstation
+ or a Windows 9x box?</I
+></SPAN
+>
+ </P
+><P
+> Installing netmon on an NT workstation requires a couple
+ of steps. The following are for installing Netmon V4.00.349, which comes
+ with Microsoft Windows NT Server 4.0, on Microsoft Windows NT
+ Workstation 4.0. The process should be similar for other version of
+ Windows NT / Netmon. You will need both the Microsoft Windows
+ NT Server 4.0 Install CD and the Workstation 4.0 Install CD.
+ </P
+><P
+> Initially you will need to install 'Network Monitor Tools and Agent'
+ on the NT Server. To do this
+ </P
+><P
+></P
+><UL
+><LI
+><P
+>Goto Start - Settings - Control Panel -
+ Network - Services - Add </P
+></LI
+><LI
+><P
+>Select the 'Network Monitor Tools and Agent' and
+ click on 'OK'.</P
+></LI
+><LI
+><P
+>Click 'OK' on the Network Control Panel.
+ </P
+></LI
+><LI
+><P
+>Insert the Windows NT Server 4.0 install CD
+ when prompted.</P
+></LI
+></UL
+><P
+> At this point the Netmon files should exist in
+ <TT
+CLASS="FILENAME"
+>%SYSTEMROOT%\System32\netmon\*.*</TT
+>.
+ Two subdirectories exist as well, <TT
+CLASS="FILENAME"
+>parsers\</TT
+>
+ which contains the necessary DLL's for parsing the netmon packet
+ dump, and <TT
+CLASS="FILENAME"
+>captures\</TT
+>.
+ </P
+><P
+> In order to install the Netmon tools on an NT Workstation, you will
+ first need to install the 'Network Monitor Agent' from the Workstation
+ install CD.
+ </P
+><P
+></P
+><UL
+><LI
+><P
+>Goto Start - Settings - Control Panel -
+ Network - Services - Add</P
+></LI
+><LI
+><P
+>Select the 'Network Monitor Agent' and click
+ on 'OK'.</P
+></LI
+><LI
+><P
+>Click 'OK' on the Network Control Panel.
+ </P
+></LI
+><LI
+><P
+>Insert the Windows NT Workstation 4.0 install
+ CD when prompted.</P
+></LI
+></UL
+><P
+> Now copy the files from the NT Server in %SYSTEMROOT%\System32\netmon\*.*
+ to %SYSTEMROOT%\System32\netmon\*.* on the Workstation and set
+ permissions as you deem appropriate for your site. You will need
+ administrative rights on the NT box to run netmon.
+ </P
+><P
+> To install Netmon on a Windows 9x box install the network monitor agent
+ from the Windows 9x CD (\admin\nettools\netmon). There is a readme
+ file located with the netmon driver files on the CD if you need
+ information on how to do this. Copy the files from a working
+ Netmon installation.
+ </P
+></LI
+><LI
+><P
+> The following is a list if helpful URLs and other links:
+ </P
+><P
+></P
+><UL
+><LI
+><P
+>Home of Samba site <A
+HREF="http://samba.org"
+TARGET="_top"
+> http://samba.org</A
+>. We have a mirror near you !</P
+></LI
+><LI
+><P
+> The <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Development</I
+></SPAN
+> document
+ on the Samba mirrors might mention your problem. If so,
+ it might mean that the developers are working on it.</P
+></LI
+><LI
+><P
+>See how Scott Merrill simulates a BDC behavior at
+ <A
+HREF="http://www.skippy.net/linux/smb-howto.html"
+TARGET="_top"
+> http://www.skippy.net/linux/smb-howto.html</A
+>. </P
+></LI
+><LI
+><P
+>Although 2.0.7 has almost had its day as a PDC, David Bannon will
+ keep the 2.0.7 PDC pages at <A
+HREF="http://bioserve.latrobe.edu.au/samba"
+TARGET="_top"
+> http://bioserve.latrobe.edu.au/samba</A
+> going for a while yet.</P
+></LI
+><LI
+><P
+>Misc links to CIFS information
+ <A
+HREF="http://samba.org/cifs/"
+TARGET="_top"
+>http://samba.org/cifs/</A
+></P
+></LI
+><LI
+><P
+>NT Domains for Unix <A
+HREF="http://mailhost.cb1.com/~lkcl/ntdom/"
+TARGET="_top"
+> http://mailhost.cb1.com/~lkcl/ntdom/</A
+></P
+></LI
+><LI
+><P
+>FTP site for older SMB specs:
+ <A
+HREF="ftp://ftp.microsoft.com/developr/drg/CIFS/"
+TARGET="_top"
+> ftp://ftp.microsoft.com/developr/drg/CIFS/</A
+></P
+></LI
+></UL
+></LI
+></UL
+><P
+></P
+><UL
+><LI
+><P
+> <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>How do I get help from the mailing lists?</I
+></SPAN
+>
+ </P
+><P
+> There are a number of Samba related mailing lists. Go to <A
+HREF="http://samba.org"
+TARGET="_top"
+>http://samba.org</A
+>, click on your nearest mirror
+ and then click on <B
+CLASS="COMMAND"
+>Support</B
+> and then click on <B
+CLASS="COMMAND"
+> Samba related mailing lists</B
+>.
+ </P
+><P
+> For questions relating to Samba TNG go to
+ <A
+HREF="http://www.samba-tng.org/"
+TARGET="_top"
+>http://www.samba-tng.org/</A
+>
+ It has been requested that you don't post questions about Samba-TNG to the
+ main stream Samba lists.</P
+><P
+> If you post a message to one of the lists please observe the following guide lines :
+ </P
+><P
+></P
+><UL
+><LI
+><P
+> Always remember that the developers are volunteers, they are
+ not paid and they never guarantee to produce a particular feature at
+ a particular time. Any time lines are 'best guess' and nothing more.
+ </P
+></LI
+><LI
+><P
+> Always mention what version of samba you are using and what
+ operating system its running under. You should probably list the
+ relevant sections of your smb.conf file, at least the options
+ in [global] that affect PDC support.</P
+></LI
+><LI
+><P
+>In addition to the version, if you obtained Samba via
+ CVS mention the date when you last checked it out.</P
+></LI
+><LI
+><P
+> Try and make your question clear and brief, lots of long,
+ convoluted questions get deleted before they are completely read !
+ Don't post html encoded messages (if you can select colour or font
+ size its html).</P
+></LI
+><LI
+><P
+> If you run one of those nifty 'I'm on holidays' things when
+ you are away, make sure its configured to not answer mailing lists.
+ </P
+></LI
+><LI
+><P
+> Don't cross post. Work out which is the best list to post to
+ and see what happens, i.e. don't post to both samba-ntdom and samba-technical.
+ Many people active on the lists subscribe to more
+ than one list and get annoyed to see the same message two or more times.
+ Often someone will see a message and thinking it would be better dealt
+ with on another, will forward it on for you.</P
+></LI
+><LI
+><P
+>You might include <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>partial</I
+></SPAN
+>
+ log files written at a debug level set to as much as 20.
+ Please don't send the entire log but enough to give the context of the
+ error messages.</P
+></LI
+><LI
+><P
+>(Possibly) If you have a complete netmon trace ( from the opening of
+ the pipe to the error ) you can send the *.CAP file as well.</P
+></LI
+><LI
+><P
+>Please think carefully before attaching a document to an email.
+ Consider pasting the relevant parts into the body of the message. The samba
+ mailing lists go to a huge number of people, do they all need a copy of your
+ smb.conf in their attach directory?</P
+></LI
+></UL
+></LI
+><LI
+><P
+> <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>How do I get off the mailing lists?</I
+></SPAN
+>
+ </P
+><P
+>To have your name removed from a samba mailing list, go to the
+ same place you went to to get on it. Go to <A
+HREF="http://lists.samba.org/"
+TARGET="_top"
+>http://lists.samba.org</A
+>,
+ click on your nearest mirror and then click on <B
+CLASS="COMMAND"
+>Support</B
+> and
+ then click on <B
+CLASS="COMMAND"
+> Samba related mailing lists</B
+>. Or perhaps see
+ <A
+HREF="http://lists.samba.org/mailman/roster/samba-ntdom"
+TARGET="_top"
+>here</A
+>
+ </P
+><P
+> Please don't post messages to the list asking to be removed, you will just
+ be referred to the above address (unless that process failed in some way...)
+ </P
+></LI
+></UL
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN953">6.8. Domain Control for Windows 9x/ME</H1
+><DIV
+CLASS="NOTE"
+><P
+></P
+><TABLE
+CLASS="NOTE"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/note.gif"
+HSPACE="5"
+ALT="Note"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+>The following section contains much of the original
+DOMAIN.txt file previously included with Samba. Much of
+the material is based on what went into the book <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Special
+Edition, Using Samba</I
+></SPAN
+>, by Richard Sharpe.</P
+></TD
+></TR
+></TABLE
+></DIV
+><P
+>A domain and a workgroup are exactly the same thing in terms of network
browsing. The difference is that a distributable authentication
database is associated with a domain, for secure login access to a
network. Also, different access rights can be granted to users if they
-successfully authenticate against a domain logon server. Samba-3 does this
-now in the same way that MS Windows NT/2K.
-</p><p>
-The SMB client logging on to a domain has an expectation that every other
+successfully authenticate against a domain logon server (NT server and
+other systems based on NT server support this, as does at least Samba TNG now).</P
+><P
+>The SMB client logging on to a domain has an expectation that every other
server in the domain should accept the same authentication information.
-Network browsing functionality of domains and workgroups is identical and
-is explained in this documentation under the browsing discussions.
-It should be noted, that browsing is totally orthogonal to logon support.
-</p><p>
-Issues related to the single-logon network model are discussed in this
+Network browsing functionality of domains and workgroups is
+identical and is explained in BROWSING.txt. It should be noted, that browsing
+is totally orthogonal to logon support.</P
+><P
+>Issues related to the single-logon network model are discussed in this
section. Samba supports domain logons, network logon scripts, and user
profiles for MS Windows for workgroups and MS Windows 9X/ME clients
-which are the focus of this section.
-</p><p>
-When an SMB client in a domain wishes to logon it broadcast requests for a
+which will be the focus of this section.</P
+><P
+>When an SMB client in a domain wishes to logon it broadcast requests for a
logon server. The first one to reply gets the job, and validates its
password using whatever mechanism the Samba administrator has installed.
It is possible (but very stupid) to create a domain where the user
database is not shared between servers, i.e. they are effectively workgroup
servers advertising themselves as participating in a domain. This
demonstrates how authentication is quite different from but closely
-involved with domains.
-</p><p>
-Using these features you can make your clients verify their logon via
+involved with domains.</P
+><P
+>Using these features you can make your clients verify their logon via
the Samba server; make clients run a batch file when they logon to
-the network and download their preferences, desktop and start menu.
-</p><p>
-Before launching into the configuration instructions, it is
-worthwhile to look at how a Windows 9x/ME client performs a logon:
-</p><div class="orderedlist"><ol type="1"><li><p>
- The client broadcasts (to the IP broadcast address of the subnet it is in)
- a NetLogon request. This is sent to the NetBIOS name DOMAIN&lt;1c&gt; at the
+the network and download their preferences, desktop and start menu.</P
+><P
+>Before launching into the configuration instructions, it is
+worthwhile lookingat how a Windows 9x/ME client performs a logon:</P
+><P
+></P
+><OL
+TYPE="1"
+><LI
+><P
+> The client broadcasts (to the IP broadcast address of the subnet it is in)
+ a NetLogon request. This is sent to the NetBIOS name DOMAIN&#60;1c&#62; at the
NetBIOS layer. The client chooses the first response it receives, which
contains the NetBIOS name of the logon server to use in the format of
\\SERVER.
- </p></li><li><p>
- The client then connects to that server, logs on (does an SMBsessetupX) and
+ </P
+></LI
+><LI
+><P
+> The client then connects to that server, logs on (does an SMBsessetupX) and
then connects to the IPC$ share (using an SMBtconX).
- </p></li><li><p>
- The client then does a NetWkstaUserLogon request, which retrieves the name
+ </P
+></LI
+><LI
+><P
+> The client then does a NetWkstaUserLogon request, which retrieves the name
of the user's logon script.
- </p></li><li><p>
- The client then connects to the NetLogon share and searches for this
+ </P
+></LI
+><LI
+><P
+> The client then connects to the NetLogon share and searches for this
and if it is found and can be read, is retrieved and executed by the client.
After this, the client disconnects from the NetLogon share.
- </p></li><li><p>
- The client then sends a NetUserGetInfo request to the server, to retrieve
+ </P
+></LI
+><LI
+><P
+> The client then sends a NetUserGetInfo request to the server, to retrieve
the user's home share, which is used to search for profiles. Since the
- response to the NetUserGetInfo request does not contain much more then
+ response to the NetUserGetInfo request does not contain much more
the user's home share, profiles for Win9X clients MUST reside in the user
home directory.
- </p></li><li><p>
- The client then connects to the user's home share and searches for the
+ </P
+></LI
+><LI
+><P
+> The client then connects to the user's home share and searches for the
user's profile. As it turns out, you can specify the user's home share as
a sharename and path. For example, \\server\fred\.profile.
If the profiles are found, they are implemented.
- </p></li><li><p>
- The client then disconnects from the user's home share, and reconnects to
+ </P
+></LI
+><LI
+><P
+> The client then disconnects from the user's home share, and reconnects to
the NetLogon share and looks for CONFIG.POL, the policies file. If this is
found, it is read and implemented.
- </p></li></ol></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2878805"></a>Configuration Instructions: Network Logons</h3></div></div><p>
-The main difference between a PDC and a Windows 9x logon
-server configuration is that
-</p><div class="itemizedlist"><ul type="disc"><li><p>
-Password encryption is not required for a Windows 9x logon server.
-</p></li><li><p>
-Windows 9x/ME clients do not possess machine trust accounts.
-</p></li></ul></div><p>
-Therefore, a Samba PDC will also act as a Windows 9x logon
-server.
-</p><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">security mode and master browsers</h3><p>
-There are a few comments to make in order to tie up some
+ </P
+></LI
+></OL
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN979">6.8.1. Configuration Instructions: Network Logons</H2
+><P
+>The main difference between a PDC and a Windows 9x logon
+server configuration is that</P
+><P
+></P
+><UL
+><LI
+><P
+>Password encryption is not required for a Windows 9x logon server.</P
+></LI
+><LI
+><P
+>Windows 9x/ME clients do not possess machine trust accounts.</P
+></LI
+></UL
+><P
+>Therefore, a Samba PDC will also act as a Windows 9x logon
+server.</P
+><DIV
+CLASS="WARNING"
+><P
+></P
+><TABLE
+CLASS="WARNING"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/warning.gif"
+HSPACE="5"
+ALT="Warning"></TD
+><TH
+ALIGN="LEFT"
+VALIGN="CENTER"
+><B
+>security mode and master browsers</B
+></TH
+></TR
+><TR
+><TD
+>&nbsp;</TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+>There are a few comments to make in order to tie up some
loose ends. There has been much debate over the issue of whether
or not it is ok to configure Samba as a Domain Controller in security
-modes other than <tt>USER</tt>. The only security mode
-which will not work due to technical reasons is <tt>SHARE</tt>
-mode security. <tt>DOMAIN</tt> and <tt>SERVER</tt>
-mode security is really just a variation on SMB user level security.
-</p><p>
-Actually, this issue is also closely tied to the debate on whether
+modes other than <TT
+CLASS="CONSTANT"
+>USER</TT
+>. The only security mode
+which will not work due to technical reasons is <TT
+CLASS="CONSTANT"
+>SHARE</TT
+>
+mode security. <TT
+CLASS="CONSTANT"
+>DOMAIN</TT
+> and <TT
+CLASS="CONSTANT"
+>SERVER</TT
+>
+mode security is really just a variation on SMB user level security.</P
+><P
+>Actually, this issue is also closely tied to the debate on whether
or not Samba must be the domain master browser for its workgroup
when operating as a DC. While it may technically be possible
to configure a server as such (after all, browsing and domain logons
-are two distinctly different functions), it is not a good idea to do
+are two distinctly different functions), it is not a good idea to
so. You should remember that the DC must register the DOMAIN#1b NetBIOS
name. This is the name used by Windows clients to locate the DC.
Windows clients do not distinguish between the DC and the DMB.
-For this reason, it is very wise to configure the Samba DC as the DMB.
-</p><p>
-Now back to the issue of configuring a Samba DC to use a mode other
-than &quot;security = user&quot;. If a Samba host is configured to use
+For this reason, it is very wise to configure the Samba DC as the DMB.</P
+><P
+>Now back to the issue of configuring a Samba DC to use a mode other
+than "security = user". If a Samba host is configured to use
another SMB server or DC in order to validate user connection
requests, then it is a fact that some other machine on the network
-(the &quot;password server&quot;) knows more about the user than the Samba host.
+(the "password server") knows more about user than the Samba host.
99% of the time, this other host is a domain controller. Now
-in order to operate in domain mode security, the &quot;workgroup&quot; parameter
+in order to operate in domain mode security, the "workgroup" parameter
must be set to the name of the Windows NT domain (which already
-has a domain controller, right?)
-</p><p>
-Therefore configuring a Samba box as a DC for a domain that
+has a domain controller, right?)</P
+><P
+>Therefore configuring a Samba box as a DC for a domain that
already by definition has a PDC is asking for trouble.
Therefore, you should always configure the Samba DC to be the DMB
-for its domain.
-</p></div></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="securitylevels.html">Prev</a></td><td width="20%" align="center"><a accesskey="u" href="type.html">Up</a></td><td width="40%" align="right"><a accesskey="n" href="samba-bdc.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter4.Samba as Stand-Alone Server</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">Chapter6.
-Samba Backup Domain Controller to Samba Domain Control
-</td></tr></table></div></body></html>
+for its domain.</P
+></TD
+></TR
+></TABLE
+></DIV
+></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN998">6.8.2. Configuration Instructions: Setting up Roaming User Profiles</H2
+><DIV
+CLASS="WARNING"
+><P
+></P
+><TABLE
+CLASS="WARNING"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/warning.gif"
+HSPACE="5"
+ALT="Warning"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>NOTE!</I
+></SPAN
+> Roaming profiles support is different
+for Win9X and WinNT.</P
+></TD
+></TR
+></TABLE
+></DIV
+><P
+>Before discussing how to configure roaming profiles, it is useful to see how
+Win9X and WinNT clients implement these features.</P
+><P
+>Win9X clients send a NetUserGetInfo request to the server to get the user's
+profiles location. However, the response does not have room for a separate
+profiles location field, only the user's home share. This means that Win9X
+profiles are restricted to being in the user's home directory.</P
+><P
+>WinNT clients send a NetSAMLogon RPC request, which contains many fields,
+including a separate field for the location of the user's profiles.
+This means that support for profiles is different for Win9X and WinNT.</P
+><DIV
+CLASS="SECT3"
+><H3
+CLASS="SECT3"
+><A
+NAME="AEN1006">6.8.2.1. Windows NT Configuration</H3
+><P
+>To support WinNT clients, in the [global] section of smb.conf set the
+following (for example):</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>logon path = \\profileserver\profileshare\profilepath\%U\moreprofilepath</PRE
+></P
+><P
+>The default for this option is \\%N\%U\profile, namely
+\\sambaserver\username\profile. The \\N%\%U service is created
+automatically by the [homes] service.
+If you are using a samba server for the profiles, you _must_ make the
+share specified in the logon path browseable. </P
+><DIV
+CLASS="NOTE"
+><P
+></P
+><TABLE
+CLASS="NOTE"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/note.gif"
+HSPACE="5"
+ALT="Note"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+>[lkcl 26aug96 - we have discovered a problem where Windows clients can
+maintain a connection to the [homes] share in between logins. The
+[homes] share must NOT therefore be used in a profile path.]</P
+></TD
+></TR
+></TABLE
+></DIV
+></DIV
+><DIV
+CLASS="SECT3"
+><H3
+CLASS="SECT3"
+><A
+NAME="AEN1014">6.8.2.2. Windows 9X Configuration</H3
+><P
+>To support Win9X clients, you must use the "logon home" parameter. Samba has
+now been fixed so that "net use/home" now works as well, and it, too, relies
+on the "logon home" parameter.</P
+><P
+>By using the logon home parameter, you are restricted to putting Win9X
+profiles in the user's home directory. But wait! There is a trick you
+can use. If you set the following in the [global] section of your
+smb.conf file:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>logon home = \\%L\%U\.profiles</PRE
+></P
+><P
+>then your Win9X clients will dutifully put their clients in a subdirectory
+of your home directory called .profiles (thus making them hidden).</P
+><P
+>Not only that, but 'net use/home' will also work, because of a feature in
+Win9X. It removes any directory stuff off the end of the home directory area
+and only uses the server and share portion. That is, it looks like you
+specified \\%L\%U for "logon home".</P
+></DIV
+><DIV
+CLASS="SECT3"
+><H3
+CLASS="SECT3"
+><A
+NAME="AEN1022">6.8.2.3. Win9X and WinNT Configuration</H3
+><P
+>You can support profiles for both Win9X and WinNT clients by setting both the
+"logon home" and "logon path" parameters. For example:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>logon home = \\%L\%U\.profiles
+logon path = \\%L\profiles\%U</PRE
+></P
+><DIV
+CLASS="NOTE"
+><P
+></P
+><TABLE
+CLASS="NOTE"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/note.gif"
+HSPACE="5"
+ALT="Note"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+>I have not checked what 'net use /home' does on NT when "logon home" is
+set as above.</P
+></TD
+></TR
+></TABLE
+></DIV
+></DIV
+><DIV
+CLASS="SECT3"
+><H3
+CLASS="SECT3"
+><A
+NAME="AEN1029">6.8.2.4. Windows 9X Profile Setup</H3
+><P
+>When a user first logs in on Windows 9X, the file user.DAT is created,
+as are folders "Start Menu", "Desktop", "Programs" and "Nethood".
+These directories and their contents will be merged with the local
+versions stored in c:\windows\profiles\username on subsequent logins,
+taking the most recent from each. You will need to use the [global]
+options "preserve case = yes", "short preserve case = yes" and
+"case sensitive = no" in order to maintain capital letters in shortcuts
+in any of the profile folders.</P
+><P
+>The user.DAT file contains all the user's preferences. If you wish to
+enforce a set of preferences, rename their user.DAT file to user.MAN,
+and deny them write access to this file.</P
+><P
+></P
+><OL
+TYPE="1"
+><LI
+><P
+> On the Windows 95 machine, go to Control Panel | Passwords and
+ select the User Profiles tab. Select the required level of
+ roaming preferences. Press OK, but do _not_ allow the computer
+ to reboot.
+ </P
+></LI
+><LI
+><P
+> On the Windows 95 machine, go to Control Panel | Network |
+ Client for Microsoft Networks | Preferences. Select 'Log on to
+ NT Domain'. Then, ensure that the Primary Logon is 'Client for
+ Microsoft Networks'. Press OK, and this time allow the computer
+ to reboot.
+ </P
+></LI
+></OL
+><P
+>Under Windows 95, Profiles are downloaded from the Primary Logon.
+If you have the Primary Logon as 'Client for Novell Networks', then
+the profiles and logon script will be downloaded from your Novell
+Server. If you have the Primary Logon as 'Windows Logon', then the
+profiles will be loaded from the local machine - a bit against the
+concept of roaming profiles, if you ask me.</P
+><P
+>You will now find that the Microsoft Networks Login box contains
+[user, password, domain] instead of just [user, password]. Type in
+the samba server's domain name (or any other domain known to exist,
+but bear in mind that the user will be authenticated against this
+domain and profiles downloaded from it, if that domain logon server
+supports it), user name and user's password.</P
+><P
+>Once the user has been successfully validated, the Windows 95 machine
+will inform you that 'The user has not logged on before' and asks you
+if you wish to save the user's preferences? Select 'yes'.</P
+><P
+>Once the Windows 95 client comes up with the desktop, you should be able
+to examine the contents of the directory specified in the "logon path"
+on the samba server and verify that the "Desktop", "Start Menu",
+"Programs" and "Nethood" folders have been created.</P
+><P
+>These folders will be cached locally on the client, and updated when
+the user logs off (if you haven't made them read-only by then :-).
+You will find that if the user creates further folders or short-cuts,
+that the client will merge the profile contents downloaded with the
+contents of the profile directory already on the local client, taking
+the newest folders and short-cuts from each set.</P
+><P
+>If you have made the folders / files read-only on the samba server,
+then you will get errors from the w95 machine on logon and logout, as
+it attempts to merge the local and the remote profile. Basically, if
+you have any errors reported by the w95 machine, check the Unix file
+permissions and ownership rights on the profile directory contents,
+on the samba server.</P
+><P
+>If you have problems creating user profiles, you can reset the user's
+local desktop cache, as shown below. When this user then next logs in,
+they will be told that they are logging in "for the first time".</P
+><P
+></P
+><OL
+TYPE="1"
+><LI
+><P
+> instead of logging in under the [user, password, domain] dialog,
+ press escape.
+ </P
+></LI
+><LI
+><P
+> run the regedit.exe program, and look in:
+ </P
+><P
+> HKEY_LOCAL_MACHINE\Windows\CurrentVersion\ProfileList
+ </P
+><P
+> you will find an entry, for each user, of ProfilePath. Note the
+ contents of this key (likely to be c:\windows\profiles\username),
+ then delete the key ProfilePath for the required user.
+ </P
+><P
+> [Exit the registry editor].
+ </P
+></LI
+><LI
+><P
+> <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>WARNING</I
+></SPAN
+> - before deleting the contents of the
+ directory listed in
+ the ProfilePath (this is likely to be c:\windows\profiles\username),
+ ask them if they have any important files stored on their desktop
+ or in their start menu. delete the contents of the directory
+ ProfilePath (making a backup if any of the files are needed).
+ </P
+><P
+> This will have the effect of removing the local (read-only hidden
+ system file) user.DAT in their profile directory, as well as the
+ local "desktop", "nethood", "start menu" and "programs" folders.
+ </P
+></LI
+><LI
+><P
+> search for the user's .PWL password-caching file in the c:\windows
+ directory, and delete it.
+ </P
+></LI
+><LI
+><P
+> log off the windows 95 client.
+ </P
+></LI
+><LI
+><P
+> check the contents of the profile path (see "logon path" described
+ above), and delete the user.DAT or user.MAN file for the user,
+ making a backup if required.
+ </P
+></LI
+></OL
+><P
+>If all else fails, increase samba's debug log levels to between 3 and 10,
+and / or run a packet trace program such as tcpdump or netmon.exe, and
+look for any error reports.</P
+><P
+>If you have access to an NT server, then first set up roaming profiles
+and / or netlogons on the NT server. Make a packet trace, or examine
+the example packet traces provided with NT server, and see what the
+differences are with the equivalent samba trace.</P
+></DIV
+><DIV
+CLASS="SECT3"
+><H3
+CLASS="SECT3"
+><A
+NAME="AEN1065">6.8.2.5. Windows NT Workstation 4.0</H3
+><P
+>When a user first logs in to a Windows NT Workstation, the profile
+NTuser.DAT is created. The profile location can be now specified
+through the "logon path" parameter. </P
+><DIV
+CLASS="NOTE"
+><P
+></P
+><TABLE
+CLASS="NOTE"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/note.gif"
+HSPACE="5"
+ALT="Note"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+>[lkcl 10aug97 - i tried setting the path to
+\\samba-server\homes\profile, and discovered that this fails because
+a background process maintains the connection to the [homes] share
+which does _not_ close down in between user logins. you have to
+have \\samba-server\%L\profile, where user is the username created
+from the [homes] share].</P
+></TD
+></TR
+></TABLE
+></DIV
+><P
+>There is a parameter that is now available for use with NT Profiles:
+"logon drive". This should be set to "h:" or any other drive, and
+should be used in conjunction with the new "logon home" parameter.</P
+><P
+>The entry for the NT 4.0 profile is a _directory_ not a file. The NT
+help on profiles mentions that a directory is also created with a .PDS
+extension. The user, while logging in, must have write permission to
+create the full profile path (and the folder with the .PDS extension)
+[lkcl 10aug97 - i found that the creation of the .PDS directory failed,
+and had to create these manually for each user, with a shell script.
+also, i presume, but have not tested, that the full profile path must
+be browseable just as it is for w95, due to the manner in which they
+attempt to create the full profile path: test existence of each path
+component; create path component].</P
+><P
+>In the profile directory, NT creates more folders than 95. It creates
+"Application Data" and others, as well as "Desktop", "Nethood",
+"Start Menu" and "Programs". The profile itself is stored in a file
+NTuser.DAT. Nothing appears to be stored in the .PDS directory, and
+its purpose is currently unknown.</P
+><P
+>You can use the System Control Panel to copy a local profile onto
+a samba server (see NT Help on profiles: it is also capable of firing
+up the correct location in the System Control Panel for you). The
+NT Help file also mentions that renaming NTuser.DAT to NTuser.MAN
+turns a profile into a mandatory one.</P
+><DIV
+CLASS="NOTE"
+><P
+></P
+><TABLE
+CLASS="NOTE"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/note.gif"
+HSPACE="5"
+ALT="Note"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+>[lkcl 10aug97 - i notice that NT Workstation tells me that it is
+downloading a profile from a slow link. whether this is actually the
+case, or whether there is some configuration issue, as yet unknown,
+that makes NT Workstation _think_ that the link is a slow one is a
+matter to be resolved].</P
+><P
+>[lkcl 20aug97 - after samba digest correspondence, one user found, and
+another confirmed, that profiles cannot be loaded from a samba server
+unless "security = user" and "encrypt passwords = yes" (see the file
+ENCRYPTION.txt) or "security = server" and "password server = ip.address.
+of.yourNTserver" are used. Either of these options will allow the NT
+workstation to access the samba server using LAN manager encrypted
+passwords, without the user intervention normally required by NT
+workstation for clear-text passwords].</P
+><P
+>[lkcl 25aug97 - more comments received about NT profiles: the case of
+the profile _matters_. the file _must_ be called NTuser.DAT or, for
+a mandatory profile, NTuser.MAN].</P
+></TD
+></TR
+></TABLE
+></DIV
+></DIV
+><DIV
+CLASS="SECT3"
+><H3
+CLASS="SECT3"
+><A
+NAME="AEN1078">6.8.2.6. Windows NT Server</H3
+><P
+>There is nothing to stop you specifying any path that you like for the
+location of users' profiles. Therefore, you could specify that the
+profile be stored on a samba server, or any other SMB server, as long as
+that SMB server supports encrypted passwords.</P
+></DIV
+><DIV
+CLASS="SECT3"
+><H3
+CLASS="SECT3"
+><A
+NAME="AEN1081">6.8.2.7. Sharing Profiles between W95 and NT Workstation 4.0</H3
+><DIV
+CLASS="WARNING"
+><P
+></P
+><TABLE
+CLASS="WARNING"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/warning.gif"
+HSPACE="5"
+ALT="Warning"></TD
+><TH
+ALIGN="LEFT"
+VALIGN="CENTER"
+><B
+>Potentially outdated or incorrect material follows</B
+></TH
+></TR
+><TR
+><TD
+>&nbsp;</TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+>I think this is all bogus, but have not deleted it. (Richard Sharpe)</P
+></TD
+></TR
+></TABLE
+></DIV
+><P
+>The default logon path is \\%N\%U. NT Workstation will attempt to create
+a directory "\\samba-server\username.PDS" if you specify the logon path
+as "\\samba-server\username" with the NT User Manager. Therefore, you
+will need to specify (for example) "\\samba-server\username\profile".
+NT 4.0 will attempt to create "\\samba-server\username\profile.PDS", which
+is more likely to succeed.</P
+><P
+>If you then want to share the same Start Menu / Desktop with W95, you will
+need to specify "logon path = \\samba-server\username\profile" [lkcl 10aug97
+this has its drawbacks: i created a shortcut to telnet.exe, which attempts
+to run from the c:\winnt\system32 directory. this directory is obviously
+unlikely to exist on a Win95-only host].</P
+><P
+>&#13;If you have this set up correctly, you will find separate user.DAT and
+NTuser.DAT files in the same profile directory.</P
+><DIV
+CLASS="NOTE"
+><P
+></P
+><TABLE
+CLASS="NOTE"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/note.gif"
+HSPACE="5"
+ALT="Note"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+>[lkcl 25aug97 - there are some issues to resolve with downloading of
+NT profiles, probably to do with time/date stamps. i have found that
+NTuser.DAT is never updated on the workstation after the first time that
+it is copied to the local workstation profile directory. this is in
+contrast to w95, where it _does_ transfer / update profiles correctly].</P
+></TD
+></TR
+></TABLE
+></DIV
+></DIV
+></DIV
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN1091">6.9. DOMAIN_CONTROL.txt : Windows NT Domain Control &#38; Samba</H1
+><DIV
+CLASS="WARNING"
+><P
+></P
+><TABLE
+CLASS="WARNING"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/warning.gif"
+HSPACE="5"
+ALT="Warning"></TD
+><TH
+ALIGN="LEFT"
+VALIGN="CENTER"
+><B
+>Possibly Outdated Material</B
+></TH
+></TR
+><TR
+><TD
+>&nbsp;</TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+> This appendix was originally authored by John H Terpstra of
+ the Samba Team and is included here for posterity.
+ </P
+></TD
+></TR
+></TABLE
+></DIV
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>NOTE :</I
+></SPAN
+>
+The term "Domain Controller" and those related to it refer to one specific
+method of authentication that can underly an SMB domain. Domain Controllers
+prior to Windows NT Server 3.1 were sold by various companies and based on
+private extensions to the LAN Manager 2.1 protocol. Windows NT introduced
+Microsoft-specific ways of distributing the user authentication database.
+See DOMAIN.txt for examples of how Samba can participate in or create
+SMB domains based on shared authentication database schemes other than the
+Windows NT SAM.</P
+><P
+>Windows NT Server can be installed as either a plain file and print server
+(WORKGROUP workstation or server) or as a server that participates in Domain
+Control (DOMAIN member, Primary Domain controller or Backup Domain controller).
+The same is true for OS/2 Warp Server, Digital Pathworks and other similar
+products, all of which can participate in Domain Control along with Windows NT.</P
+><P
+>To many people these terms can be confusing, so let's try to clear the air.</P
+><P
+>Every Windows NT system (workstation or server) has a registry database.
+The registry contains entries that describe the initialization information
+for all services (the equivalent of Unix Daemons) that run within the Windows
+NT environment. The registry also contains entries that tell application
+software where to find dynamically loadable libraries that they depend upon.
+In fact, the registry contains entries that describes everything that anything
+may need to know to interact with the rest of the system.</P
+><P
+>The registry files can be located on any Windows NT machine by opening a
+command prompt and typing:</P
+><P
+><TT
+CLASS="PROMPT"
+>C:\WINNT\&#62;</TT
+> dir %SystemRoot%\System32\config</P
+><P
+>The environment variable %SystemRoot% value can be obtained by typing:</P
+><P
+><TT
+CLASS="PROMPT"
+>C:\WINNT&#62;</TT
+>echo %SystemRoot%</P
+><P
+>The active parts of the registry that you may want to be familiar with are
+the files called: default, system, software, sam and security.</P
+><P
+>In a domain environment, Microsoft Windows NT domain controllers participate
+in replication of the SAM and SECURITY files so that all controllers within
+the domain have an exactly identical copy of each.</P
+><P
+>The Microsoft Windows NT system is structured within a security model that
+says that all applications and services must authenticate themselves before
+they can obtain permission from the security manager to do what they set out
+to do.</P
+><P
+>The Windows NT User database also resides within the registry. This part of
+the registry contains the user's security identifier, home directory, group
+memberships, desktop profile, and so on.</P
+><P
+>Every Windows NT system (workstation as well as server) will have its own
+registry. Windows NT Servers that participate in Domain Security control
+have a database that they share in common - thus they do NOT own an
+independent full registry database of their own, as do Workstations and
+plain Servers.</P
+><P
+>The User database is called the SAM (Security Access Manager) database and
+is used for all user authentication as well as for authentication of inter-
+process authentication (i.e. to ensure that the service action a user has
+requested is permitted within the limits of that user's privileges).</P
+><P
+>The Samba team have produced a utility that can dump the Windows NT SAM into
+smbpasswd format: see ENCRYPTION.txt for information on smbpasswd and
+/pub/samba/pwdump on your nearest Samba mirror for the utility. This
+facility is useful but cannot be easily used to implement SAM replication
+to Samba systems.</P
+><P
+>Windows for Workgroups, Windows 95, and Windows NT Workstations and Servers
+can participate in a Domain security system that is controlled by Windows NT
+servers that have been correctly configured. Almost every domain will have
+ONE Primary Domain Controller (PDC). It is desirable that each domain will
+have at least one Backup Domain Controller (BDC).</P
+><P
+>The PDC and BDCs then participate in replication of the SAM database so that
+each Domain Controlling participant will have an up to date SAM component
+within its registry.</P
+></DIV
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+SUMMARY="Footer navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="securitylevels.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="samba-howto-collection.html"
+ACCESSKEY="H"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="samba-bdc.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>User and Share security level (for servers not in a domain)</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="type.html"
+ACCESSKEY="U"
+>Up</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>How to Act as a Backup Domain Controller in a Purely Samba Controlled Domain</TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+> \ No newline at end of file
diff --git a/docs/htmldocs/samba.7.html b/docs/htmldocs/samba.7.html
index a54d3e883f..0851e99bd5 100644
--- a/docs/htmldocs/samba.7.html
+++ b/docs/htmldocs/samba.7.html
@@ -1,116 +1,384 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>samba</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="samba.7"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>Samba &#8212; A Windows SMB/CIFS fileserver for UNIX</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><tt>Samba</tt> </p></div></div><div class="refsect1" lang="en"><h2>DESCRIPTION</h2><p>The Samba software suite is a collection of programs
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<HTML
+><HEAD
+><TITLE
+>samba</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.77"></HEAD
+><BODY
+CLASS="REFENTRY"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><H1
+><A
+NAME="SAMBA"
+></A
+>samba</H1
+><DIV
+CLASS="REFNAMEDIV"
+><A
+NAME="AEN5"
+></A
+><H2
+>Name</H2
+>SAMBA&nbsp;--&nbsp;A Windows SMB/CIFS fileserver for UNIX</DIV
+><DIV
+CLASS="REFSYNOPSISDIV"
+><A
+NAME="AEN8"
+></A
+><H2
+>Synopsis</H2
+><P
+><B
+CLASS="COMMAND"
+>Samba</B
+> </P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN11"
+></A
+><H2
+>DESCRIPTION</H2
+><P
+>The Samba software suite is a collection of programs
that implements the Server Message Block (commonly abbreviated
as SMB) protocol for UNIX systems. This protocol is sometimes
also referred to as the Common Internet File System (CIFS). For a
- more thorough description, see <a href="http://www.ubiqx.org/cifs/" target="_top">
- http://www.ubiqx.org/cifs/</a>. Samba also implements the NetBIOS
- protocol in nmbd.</p><div class="variablelist"><dl><dt><span class="term"><a href="smbd.8.html">smbd(8)</a></span></dt><dd><p>The <b>smbd</b> daemon provides the file and print services to
+ more thorough description, see <A
+HREF="http://www.ubiqx.org/cifs/"
+TARGET="_top"
+> http://www.ubiqx.org/cifs/</A
+>. Samba also implements the NetBIOS
+ protocol in nmbd.</P
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+><B
+CLASS="COMMAND"
+>smbd</B
+></DT
+><DD
+><P
+>The <B
+CLASS="COMMAND"
+>smbd </B
+>
+ daemon provides the file and print services to
SMB clients, such as Windows 95/98, Windows NT, Windows
for Workgroups or LanManager. The configuration file
- for this daemon is described in <a href="smb.conf.5.html">smb.conf(5)</a>
- </p></dd><dt><span class="term"><a href="nmbd.8.html">nmbd(8)</a></span></dt><dd><p>The <b>nmbd</b>
+ for this daemon is described in <TT
+CLASS="FILENAME"
+>smb.conf</TT
+>
+ </P
+></DD
+><DT
+><B
+CLASS="COMMAND"
+>nmbd</B
+></DT
+><DD
+><P
+>The <B
+CLASS="COMMAND"
+>nmbd</B
+>
daemon provides NetBIOS nameservice and browsing
support. The configuration file for this daemon
- is described in <a href="smb.conf.5.html">smb.conf(5)</a></p></dd><dt><span class="term"><a href="smbclient.1.html">smbclient(1)</a></span></dt><dd><p>The <b>smbclient</b>
+ is described in <TT
+CLASS="FILENAME"
+>smb.conf</TT
+></P
+></DD
+><DT
+><B
+CLASS="COMMAND"
+>smbclient</B
+></DT
+><DD
+><P
+>The <B
+CLASS="COMMAND"
+>smbclient</B
+>
program implements a simple ftp-like client. This
is useful for accessing SMB shares on other compatible
servers (such as Windows NT), and can also be used
to allow a UNIX box to print to a printer attached to
- any SMB server (such as a PC running Windows NT).</p></dd><dt><span class="term"><a href="testparm.1.html">testparm(1)</a></span></dt><dd><p>The <b>testparm</b>
- utility is a simple syntax checker for Samba's <a href="smb.conf.5.html">smb.conf(5)</a> configuration file.</p></dd><dt><span class="term"><a href="testprns.1.html">testprns(1)</a></span></dt><dd><p>The <b>testprns</b>
+ any SMB server (such as a PC running Windows NT).</P
+></DD
+><DT
+><B
+CLASS="COMMAND"
+>testparm</B
+></DT
+><DD
+><P
+>The <B
+CLASS="COMMAND"
+>testparm</B
+>
+ utility is a simple syntax checker for Samba's
+ <TT
+CLASS="FILENAME"
+>smb.conf</TT
+>configuration file.</P
+></DD
+><DT
+><B
+CLASS="COMMAND"
+>testprns</B
+></DT
+><DD
+><P
+>The <B
+CLASS="COMMAND"
+>testprns</B
+>
utility supports testing printer names defined
- in your <tt>printcap</tt> file used
- by Samba.</p></dd><dt><span class="term"><a href="smbstatus.1.html">smbstatus(1)</a></span></dt><dd><p>The <b>smbstatus</b>
+ in your <TT
+CLASS="FILENAME"
+>printcap</TT
+> file used
+ by Samba.</P
+></DD
+><DT
+><B
+CLASS="COMMAND"
+>smbstatus</B
+></DT
+><DD
+><P
+>The <B
+CLASS="COMMAND"
+>smbstatus</B
+>
tool provides access to information about the
- current connections to <b>smbd</b>.</p></dd><dt><span class="term"><a href="nmblookup.1.html">nmblookup(1)</a></span></dt><dd><p>The <b>nmblookup</b>
+ current connections to <B
+CLASS="COMMAND"
+>smbd</B
+>.</P
+></DD
+><DT
+><B
+CLASS="COMMAND"
+>nmblookup</B
+></DT
+><DD
+><P
+>The <B
+CLASS="COMMAND"
+>nmblookup</B
+>
tools allows NetBIOS name queries to be made
- from a UNIX host.</p></dd><dt><span class="term"><a href="smbgroupedit.8.html">smbgroupedit(8)</a></span></dt><dd><p>The <b>smbgroupedit</b>
- tool allows for mapping unix groups to NT Builtin,
- Domain, or Local groups. Also it allows setting
- priviledges for that group, such as saAddUser, etc.</p></dd><dt><span class="term"><a href="smbpasswd.8.html">smbpasswd(8)</a></span></dt><dd><p>The <b>smbpasswd</b>
+ from a UNIX host.</P
+></DD
+><DT
+><B
+CLASS="COMMAND"
+>make_smbcodepage</B
+></DT
+><DD
+><P
+>The <B
+CLASS="COMMAND"
+>make_smbcodepage</B
+>
+ utility provides a means of creating SMB code page
+ definition files for your <B
+CLASS="COMMAND"
+>smbd</B
+> server.</P
+></DD
+><DT
+><B
+CLASS="COMMAND"
+>smbpasswd</B
+></DT
+><DD
+><P
+>The <B
+CLASS="COMMAND"
+>smbpasswd</B
+>
command is a tool for changing LanMan and Windows NT
- password hashes on Samba and Windows NT servers.</p></dd><dt><span class="term"><a href="smbcacls.1.html">smbcacls(1)</a></span></dt><dd><p>The <b>smbcacls</b> command is
- a tool to set ACL's on remote CIFS servers. </p></dd><dt><span class="term"><a href="smbsh.1.html">smbsh(1)</a></span></dt><dd><p>The <b>smbsh</b> command is
- a program that allows you to run a unix shell with
- with an overloaded VFS.</p></dd><dt><span class="term"><a href="smbtree.1.html">smbtree(1)</a></span></dt><dd><p>The <b>smbtree</b> command
- is a text-based network neighborhood tool.</p></dd><dt><span class="term"><a href="smbtar.1.html">smbtar(1)</a></span></dt><dd><p>The <b>smbtar</b> can make
- backups of data on CIFS/SMB servers.</p></dd><dt><span class="term"><a href="smbspool.8.html">smbspool(8)</a></span></dt><dd><p><b>smbspool</b> is a
- helper utility for printing on printers connected
- to CIFS servers. </p></dd><dt><span class="term"><a href="smbcontrol.1.html">smbcontrol(1)</a></span></dt><dd><p><b>smbcontrol</b> is a utility
- that can change the behaviour of running samba daemons.
- </p></dd><dt><span class="term"><a href="rpcclient.1.html">rpcclient(1)</a></span></dt><dd><p><b>rpcclient</b> is a utility
- that can be used to execute RPC commands on remote
- CIFS servers.</p></dd><dt><span class="term"><a href="pdbedit.8.html">pdbedit(8)</a></span></dt><dd><p>The <b>pdbedit</b> command
- can be used to maintain the local user database on
- a samba server.</p></dd><dt><span class="term"><a href="findsmb.1.html">findsmb(1)</a></span></dt><dd><p>The <b>findsmb</b> command
- can be used to find SMB servers on the local network.
- </p></dd><dt><span class="term"><a href="net.8.html">net(8)</a></span></dt><dd><p>The <b>net</b> command
- is supposed to work similar to the DOS/Windows
- NET.EXE command.</p></dd><dt><span class="term"><a href="swat.8.html">swat(8)</a></span></dt><dd><p><b>swat</b> is a web-based
- interface to configuring <tt>smb.conf</tt>.
- </p></dd><dt><span class="term"><a href="winbindd.8.html">winbindd(8)</a></span></dt><dd><p><b>winbindd</b> is a daemon
- that is used for integrating authentication and
- the user database into unix.</p></dd><dt><span class="term"><a href="wbinfo.1.html">wbinfo(1)</a></span></dt><dd><p><b>wbinfo</b> is a utility
- that retrieves and stores information related to winbind.
- </p></dd><dt><span class="term"><a href="editreg.1.html">editreg(1)</a></span></dt><dd><p><b>editreg</b> is a command-line
- utility that can edit windows registry files.
- </p></dd><dt><span class="term"><a href="profiles.1.html">profiles(1)</a></span></dt><dd><p><b>profiles</b> is a command-line
- utility that can be used to replace all occurences of
- a certain SID with another SID.
- </p></dd><dt><span class="term"><a href="vfstest.1.html">vfstest(1)</a></span></dt><dd><p><b>vfstest</b> is a utility
- that can be used to test vfs modules.</p></dd><dt><span class="term"><a href="ntlm_auth.1.html">ntlm_auth(1)</a></span></dt><dd><p><b>ntlm_auth</b> is a helper-utility
- for external programs wanting to do NTLM-authentication.
- </p></dd><dt><span class="term"><a href="smbmount.8.html">smbmount(8)</a>, <a href="smbumount.8.html">smbumount(8)</a>, <a href="smbmount.8.html">smbmount(8)</a></span></dt><dd><p><b>smbmount</b>,<b>smbmnt</b> and <b>smbmnt</b> are commands that can be used to
- mount CIFS/SMB shares on Linux.
- </p></dd><dt><span class="term"><a href="smbcquotas.1.html">smbcquotas(1)</a></span></dt><dd><p><b>smbcquotas</b> is a tool that
- can set remote QUOTA's on server with NTFS 5. </p></dd></dl></div></div><div class="refsect1" lang="en"><h2>COMPONENTS</h2><p>The Samba suite is made up of several components. Each
+ password hashes on Samba and Windows NT servers.</P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN76"
+></A
+><H2
+>COMPONENTS</H2
+><P
+>The Samba suite is made up of several components. Each
component is described in a separate manual page. It is strongly
recommended that you read the documentation that comes with Samba
and the manual pages of those components that you use. If the
manual pages and documents aren't clear enough then please visit
- <a href="http://devel.samba.org/" target="_top">http://devel.samba.org</a>
- for information on how to file a bug report or submit a patch.</p><p>If you require help, visit the Samba webpage at
- <a href="http://samba.org/" target="_top">http://www.samba.org/</a> and
+ <A
+HREF="http://devel.samba.org/"
+TARGET="_top"
+>http://devel.samba.org</A
+>
+ for information on how to file a bug report or submit a patch.</P
+><P
+>If you require help, visit the Samba webpage at
+ <A
+HREF="http://samba.org/"
+TARGET="_top"
+>http://www.samba.org/</A
+> and
explore the many option available to you.
- </p></div><div class="refsect1" lang="en"><h2>AVAILABILITY</h2><p>The Samba software suite is licensed under the
+ </P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN82"
+></A
+><H2
+>AVAILABILITY</H2
+><P
+>The Samba software suite is licensed under the
GNU Public License(GPL). A copy of that license should
have come with the package in the file COPYING. You are
encouraged to distribute copies of the Samba suite, but
- please obey the terms of this license.</p><p>The latest version of the Samba suite can be
+ please obey the terms of this license.</P
+><P
+>The latest version of the Samba suite can be
obtained via anonymous ftp from samba.org in the
directory pub/samba/. It is also available on several
- mirror sites worldwide.</p><p>You may also find useful information about Samba
- on the newsgroup <a href="news:comp.protocols.smb" target="_top">
- comp.protocol.smb</a> and the Samba mailing
+ mirror sites worldwide.</P
+><P
+>You may also find useful information about Samba
+ on the newsgroup <A
+HREF="news:comp.protocols.smb"
+TARGET="_top"
+> comp.protocol.smb</A
+> and the Samba mailing
list. Details on how to join the mailing list are given in
- the README file that comes with Samba.</p><p>If you have access to a WWW viewer (such as Mozilla
- or Konqueror) then you will also find lots of useful information,
+ the README file that comes with Samba.</P
+><P
+>If you have access to a WWW viewer (such as Netscape
+ or Mosaic) then you will also find lots of useful information,
including back issues of the Samba mailing list, at
- <a href="http://lists.samba.org/" target="_top">http://lists.samba.org</a>.</p></div><div class="refsect1" lang="en"><h2>VERSION</h2><p>This man page is correct for version 3.0 of the
- Samba suite. </p></div><div class="refsect1" lang="en"><h2>CONTRIBUTIONS</h2><p>If you wish to contribute to the Samba project,
+ <A
+HREF="http://lists.samba.org/"
+TARGET="_top"
+>http://lists.samba.org</A
+>.</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN90"
+></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="AEN93"
+></A
+><H2
+>CONTRIBUTIONS</H2
+><P
+>If you wish to contribute to the Samba project,
then I suggest you join the Samba mailing list at
- <a href="http://lists.samba.org/" target="_top">http://lists.samba.org</a>.
- </p><p>If you have patches to submit, visit
- <a href="http://devel.samba.org/" target="_top">http://devel.samba.org/</a>
- for information on how to do it properly. We prefer patches
- in <b>diff -u</b> format.</p></div><div class="refsect1" lang="en"><h2>CONTRIBUTORS</h2><p>Contributors to the project are now too numerous
+ <A
+HREF="http://lists.samba.org/"
+TARGET="_top"
+>http://lists.samba.org</A
+>.
+ </P
+><P
+>If you have patches to submit, visit
+ <A
+HREF="http://devel.samba.org/"
+TARGET="_top"
+>http://devel.samba.org/</A
+>
+ for information on how to do it properly. We prefer patches in
+ <B
+CLASS="COMMAND"
+>diff -u</B
+> format.</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN100"
+></A
+><H2
+>CONTRIBUTORS</H2
+><P
+>Contributors to the project are now too numerous
to mention here but all deserve the thanks of all Samba
- users. To see a full list, look at <a href="ftp://samba.org/pub/samba/alpha/change-log" target="_top">
- ftp://samba.org/pub/samba/alpha/change-log</a>
- for the pre-CVS changes and at <a href="ftp://samba.org/pub/samba/alpha/cvs.log" target="_top">
- ftp://samba.org/pub/samba/alpha/cvs.log</a>
+ users. To see a full list, look at <A
+HREF="ftp://samba.org/pub/samba/alpha/change-log"
+TARGET="_top"
+> ftp://samba.org/pub/samba/alpha/change-log</A
+>
+ for the pre-CVS changes and at <A
+HREF="ftp://samba.org/pub/samba/alpha/cvs.log"
+TARGET="_top"
+> ftp://samba.org/pub/samba/alpha/cvs.log</A
+>
for the contributors to Samba post-CVS. CVS is the Open Source
source code control system used by the Samba Team to develop
- Samba. The project would have been unmanageable without it.</p><p>In addition, several commercial organizations now help
+ Samba. The project would have been unmanageable without it.</P
+><P
+>In addition, several commercial organizations now help
fund the Samba Team with money and equipment. For details see
- the Samba Web pages at <a href="http://samba.org/samba/samba-thanks.html" target="_top">
- http://samba.org/samba/samba-thanks.html</a>.</p></div><div class="refsect1" lang="en"><h2>AUTHOR</h2><p>The original Samba software and related utilities
+ the Samba Web pages at <A
+HREF="http://samba.org/samba/samba-thanks.html"
+TARGET="_top"
+> http://samba.org/samba/samba-thanks.html</A
+>.</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN107"
+></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.
+ to the way the Linux kernel is developed.</P
+><P
+>The original Samba man pages were written by Karl Auer.
The man page sources were converted to YODL format (another
- excellent piece of Open Source software, available at <a href="ftp://ftp.icce.rug.nl/pub/unix/" target="_top">
- ftp://ftp.icce.rug.nl/pub/unix/</a>) and updated for the Samba 2.0
+ excellent piece of Open Source software, available at
+ <A
+HREF="ftp://ftp.icce.rug.nl/pub/unix/"
+TARGET="_top"
+> ftp://ftp.icce.rug.nl/pub/unix/</A
+>) and updated for the Samba 2.0
release by Jeremy Allison. The conversion to DocBook for
- Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML
- 4.2 for Samba 3.0 was done by Alexander Bokovoy.</p></div></div></body></html>
+ Samba 2.2 was done by Gerald Carter</P
+></DIV
+></BODY
+></HTML
+> \ No newline at end of file
diff --git a/docs/htmldocs/securitylevels.html b/docs/htmldocs/securitylevels.html
index ddfb22536b..f1b9967540 100644
--- a/docs/htmldocs/securitylevels.html
+++ b/docs/htmldocs/securitylevels.html
@@ -1,42 +1,125 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter4.Samba as Stand-Alone Server</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"><link rel="home" href="index.html" title="SAMBA Project Documentation"><link rel="up" href="type.html" title="PartII.Server Configuration Basics"><link rel="previous" href="ServerType.html" title="Chapter3.Nomenclature of Server Types"><link rel="next" href="samba-pdc.html" title="Chapter5.
-Samba as an NT4 or Win2k Primary Domain Controller
-"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter4.Samba as Stand-Alone Server</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ServerType.html">Prev</a></td><th width="60%" align="center">PartII.Server Configuration Basics</th><td width="20%" align="right"><a accesskey="n" href="samba-pdc.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="securitylevels"></a>Chapter4.Samba as Stand-Alone Server</h2></div><div><div class="author"><h3 class="author">Andrew Tridgell</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt>&lt;<a href="mailto:tridge@samba.org">tridge@samba.org</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author">Jelmer R. Vernooij</h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt>&lt;<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</tt></p></div></div></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="securitylevels.html#id2807692">User and Share security level</a></dt><dd><dl><dt><a href="securitylevels.html#id2807727">User Level Security</a></dt><dt><a href="securitylevels.html#id2810322">Share Level Security</a></dt><dt><a href="securitylevels.html#id2812328">Server Level Security</a></dt><dt><a href="securitylevels.html#id2876991">Domain Level Security</a></dt><dt><a href="securitylevels.html#id2877129">ADS Level Security</a></dt></dl></dd></dl></div><p>
-In this section the function and purpose of Samba's <span class="emphasis"><em>security</em></span>
-modes are described.
-</p><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2807692"></a>User and Share security level</h2></div></div><p>
-A SMB server tells the client at startup what &quot;security level&quot; it is
-running. There are two options &quot;share level&quot; and &quot;user level&quot;. Which
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<HTML
+><HEAD
+><TITLE
+>User and Share security level (for servers not in a domain)</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
+REL="HOME"
+TITLE="SAMBA Project Documentation"
+HREF="samba-howto-collection.html"><LINK
+REL="UP"
+TITLE="Type of installation"
+HREF="type.html"><LINK
+REL="PREVIOUS"
+TITLE="Type of installation"
+HREF="type.html"><LINK
+REL="NEXT"
+TITLE="How to Configure Samba as a NT4 Primary Domain Controller"
+HREF="samba-pdc.html"></HEAD
+><BODY
+CLASS="CHAPTER"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><TABLE
+SUMMARY="Header navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>SAMBA Project Documentation</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="type.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+></TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="samba-pdc.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="CHAPTER"
+><H1
+><A
+NAME="SECURITYLEVELS">Chapter 5. User and Share security level (for servers not in a domain)</H1
+><P
+>A SMB server tells the client at startup what "security level" it is
+running. There are two options "share level" and "user level". Which
of these two the client receives affects the way the client then tries
to authenticate itself. It does not directly affect (to any great
extent) the way the Samba server does security. I know this is
strange, but it fits in with the client/server approach of SMB. In SMB
everything is initiated and controlled by the client, and the server
can only tell the client what is available and whether an action is
-allowed.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2807727"></a>User Level Security</h3></div></div><p>
-I'll describe user level security first, as its simpler. In user level
-security the client will send a &quot;session setup&quot; command directly after
+allowed. </P
+><P
+>I'll describe user level security first, as its simpler. In user level
+security the client will send a "session setup" command directly after
the protocol negotiation. This contains a username and password. The
server can either accept or reject that username/password
combination. Note that at this stage the server has no idea what
share the client will eventually try to connect to, so it can't base
-the &quot;accept/reject&quot; on anything other than:
-</p><div class="orderedlist"><ol type="1"><li><p>the username/password</p></li><li><p>the machine that the client is coming from</p></li></ol></div><p>
-If the server accepts the username/password then the client expects to
-be able to mount any share (using a &quot;tree connection&quot;) without
+the "accept/reject" on anything other than:</P
+><P
+></P
+><OL
+TYPE="1"
+><LI
+><P
+>the username/password</P
+></LI
+><LI
+><P
+>the machine that the client is coming from</P
+></LI
+></OL
+><P
+>If the server accepts the username/password then the client expects to
+be able to mount any share (using a "tree connection") without
specifying a password. It expects that all access rights will be as
-the username/password specified in the &quot;session setup&quot;.
-</p><p>
-It is also possible for a client to send multiple &quot;session setup&quot;
-requests. When the server responds it gives the client a &quot;uid&quot; to use
+the username/password specified in the "session setup". </P
+><P
+>It is also possible for a client to send multiple "session setup"
+requests. When the server responds it gives the client a "uid" to use
as an authentication tag for that username/password. The client can
maintain multiple authentication contexts in this way (WinDD is an
-example of an application that does this)
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2810322"></a>Share Level Security</h3></div></div><p>
-Ok, now for share level security. In share level security the client
+example of an application that does this)</P
+><P
+>Ok, now for share level security. In share level security the client
authenticates itself separately for each share. It will send a
-password along with each &quot;tree connection&quot; (share mount). It does not
+password along with each "tree connection" (share mount). It does not
explicitly send a username with this operation. The client is
expecting a password to be associated with each share, independent of
the user. This means that samba has to work out what username the
@@ -44,169 +127,108 @@ client probably wants to use. It is never explicitly sent the
username. Some commercial SMB servers such as NT actually associate
passwords directly with shares in share level security, but samba
always uses the unix authentication scheme where it is a
-username/password that is authenticated, not a &quot;share/password&quot;.
-</p><p>
-Many clients send a &quot;session setup&quot; even if the server is in share
+username/password that is authenticated, not a "share/password".</P
+><P
+>Many clients send a "session setup" even if the server is in share
level security. They normally send a valid username but no
-password. Samba records this username in a list of &quot;possible
-usernames&quot;. When the client then does a &quot;tree connection&quot; it also adds
+password. Samba records this username in a list of "possible
+usernames". When the client then does a "tree connection" it also adds
to this list the name of the share they try to connect to (useful for
-home directories) and any users listed in the <b>user =</b> <tt>smb.conf</tt>
-line. The password is then checked in turn against these &quot;possible
-usernames&quot;. If a match is found then the client is authenticated as
-that user.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2812328"></a>Server Level Security</h3></div></div><p>
-Finally &quot;server level&quot; security. In server level security the samba
+home directories) and any users listed in the "user =" smb.conf
+line. The password is then checked in turn against these "possible
+usernames". If a match is found then the client is authenticated as
+that user.</P
+><P
+>Finally "server level" security. In server level security the samba
server reports to the client that it is in user level security. The
-client then does a &quot;session setup&quot; as described earlier. The samba
+client then does a "session setup" as described earlier. The samba
server takes the username/password that the client sends and attempts
-to login to the &quot;password server&quot; by sending exactly the same
+to login to the "password server" by sending exactly the same
username/password that it got from the client. If that server is in
user level security and accepts the password then samba accepts the
clients connection. This allows the samba server to use another SMB
-server as the &quot;password server&quot;.
-</p><p>
-You should also note that at the very start of all this, where the
+server as the "password server". </P
+><P
+>You should also note that at the very start of all this, where the
server tells the client what security level it is in, it also tells
the client if it supports encryption. If it does then it supplies the
-client with a random &quot;cryptkey&quot;. The client will then send all
+client with a random "cryptkey". The client will then send all
passwords in encrypted form. You have to compile samba with encryption
enabled to support this feature, and you have to maintain a separate
smbpasswd file with SMB style encrypted passwords. It is
cryptographically impossible to translate from unix style encryption
to SMB style encryption, although there are some fairly simple management
-schemes by which the two could be kept in sync.
-</p><p>
-&quot;security = server&quot; means that Samba reports to clients that
-it is running in &quot;user mode&quot; but actually passes off all authentication
-requests to another &quot;user mode&quot; server. This requires an additional
-parameter &quot;password server =&quot; that points to the real authentication server.
+schemes by which the two could be kept in sync.</P
+><P
+>"security = server" means that Samba reports to clients that
+it is running in "user mode" but actually passes off all authentication
+requests to another "user mode" server. This requires an additional
+parameter "password server =" that points to the real authentication server.
That real authentication server can be another Samba server or can be a
-Windows NT server, the later natively capable of encrypted password support.
-</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
-<span class="emphasis"><em>Server</em></span> level security is incompatible with what is known
-as <span class="emphasis"><em>schannel</em></span> or &quot;sign and seal&quot; protocols. This means that
-if you want to use <span class="emphasis"><em>server</em></span> level security you must disable
-the use of &quot;sign and seal&quot; on all machines on your network.
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2876754"></a>Configuring Samba for Seemless Windows Network Integration</h4></div></div><p>
-MS Windows clients may use encrypted passwords as part of a challenege/response
-authentication model (a.k.a. NTLMv1) or alone, or clear text strings for simple
-password based authentication. It should be realized that with the SMB protocol
-the password is passed over the network either in plain text or encrypted, but
-not both in the same authentication request.
-</p><p>
-When encrypted passwords are used a password that has been entered by the user
-is encrypted in two ways:
-</p><div class="itemizedlist"><ul type="disc"><li><p>An MD4 hash of the UNICODE of the password
- string. This is known as the NT hash.
- </p></li><li><p>The password is converted to upper case,
- and then padded or trucated to 14 bytes. This string is
- then appended with 5 bytes of NULL characters and split to
- form two 56 bit DES keys to encrypt a &quot;magic&quot; 8 byte value.
- The resulting 16 bytes for the LanMan hash.
- </p></li></ul></div><p>
-MS Windows 95 pre-service pack 1, MS Windows NT versions 3.x and version 4.0
-pre-service pack 3 will use either mode of password authentication. All
-versions of MS Windows that follow these versions no longer support plain
-text passwords by default.
-</p><p>
-MS Windows clients have a habit of dropping network mappings that have been idle
-for 10 minutes or longer. When the user attempts to use the mapped drive
-connection that has been dropped, the client re-establishes the connection using
-a cached copy of the password.
-</p><p>
-When Microsoft changed the default password mode, support was dropped for caching
-of the plain text password. This means that when the registry parameter is changed
-to re-enable use of plain text passwords it appears to work, but when a dropped
-service connection mapping attempts to revalidate it will fail if the remote
-authentication server does not support encrypted passwords. This means that it
-is definitely not a good idea to re-enable plain text password support in such clients.
-</p><p>
-The following parameters can be used to work around the issue of Windows 9x client
-upper casing usernames and password before transmitting them to the SMB server
-when using clear text authentication.
-</p><pre class="programlisting">
- <a href="smb.conf.5.html#PASSWORDLEVEL" target="_top">passsword level</a> = <i><tt>integer</tt></i>
- <a href="smb.conf.5.html#USERNAMELEVEL" target="_top">username level</a> = <i><tt>integer</tt></i>
-</pre><p>
-By default Samba will lower case the username before attempting to lookup the user
-in the database of local system accounts. Because UNIX usernames conventionally
-only contain lower case character, the <i><tt>username level</tt></i> parameter
-is rarely needed.
-</p><p>
-However, passwords on UNIX systems often make use of mixed case characters.
-This means that in order for a user on a Windows 9x client to connect to a Samba
-server using clear text authentication, the <i><tt>password level</tt></i>
-must be set to the maximum number of upper case letter which <span class="emphasis"><em>could</em></span>
-appear is a password. Note that the server OS uses the traditional DES version
-of crypt(), a <i><tt>password level</tt></i> of 8 will result in case
-insensitive passwords as seen from Windows users. This will also result in longer
-login times as Samba has to compute the permutations of the password string and
-try them one by one until a match is located (or all combinations fail).
-</p><p>
-The best option to adopt is to enable support for encrypted passwords
-where ever Samba is used. There are three configuration possibilities
-for support of encrypted passwords:
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2876930"></a>Use MS Windows NT as an authentication server</h4></div></div><p>
-This method involves the additions of the following parameters in the <tt>smb.conf</tt> file:
-</p><pre class="programlisting">
- encrypt passwords = Yes
- security = server
- password server = &quot;NetBIOS_name_of_PDC&quot;
-</pre><p>
-There are two ways of identifying whether or not a username and
-password pair was valid or not. One uses the reply information provided
-as part of the authentication messaging process, the other uses
-just an error code.
-</p><p>
-The down-side of this mode of configuration is the fact that
-for security reasons Samba will send the password server a bogus
-username and a bogus password and if the remote server fails to
-reject the username and password pair then an alternative mode
-of identification of validation is used. Where a site uses password
-lock out after a certain number of failed authentication attempts
-this will result in user lockouts.
-</p><p>
-Use of this mode of authentication does require there to be
-a standard Unix account for the user, this account can be blocked
-to prevent logons by other than MS Windows clients.
-</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2876991"></a>Domain Level Security</h3></div></div><p>
-When samba is operating in <span class="emphasis"><em>security = domain</em></span> mode this means that
-the Samba server has a domain security trust account (a machine account) and will cause
-all authentication requests to be passed through to the domain controllers.
-</p><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2877011"></a>Samba as a member of an MS Windows NT security domain</h4></div></div><p>
-This method involves addition of the following parameters in the <tt>smb.conf</tt> file:
-</p><pre class="programlisting">
- encrypt passwords = Yes
- security = domain
- workgroup = &quot;name of NT domain&quot;
- password server = *
-</pre><p>
-The use of the &quot;*&quot; argument to <b>password server</b> will cause samba to locate the
-domain controller in a way analogous to the way this is done within MS Windows NT.
-This is the default behaviour.
-</p><p>
-In order for this method to work the Samba server needs to join the
-MS Windows NT security domain. This is done as follows:
-</p><div class="itemizedlist"><ul type="disc"><li><p>On the MS Windows NT domain controller using
- the Server Manager add a machine account for the Samba server.
- </p></li><li><p>Next, on the Linux system execute:
- <b>smbpasswd -r PDC_NAME -j DOMAIN_NAME</b> (samba 2.x)
-
- <b>net join -U administrator%password</b> (samba-3)
- </p></li></ul></div><p>
-Use of this mode of authentication does require there to be a standard Unix account
-for the user in order to assign a uid once the account has been authenticated by
-the remote Windows DC. This account can be blocked to prevent logons by clients other than
-MS Windows through things such as setting an invalid shell in the
-<tt>/etc/passwd</tt> entry.
-</p><p>
-An alternative to assigning UIDs to Windows users on a Samba member server is
-presented in the <a href="winbind.html" title="Chapter15.Unified Logons between Windows NT and UNIX using Winbind">Winbind Overview</a> chapter
-in this HOWTO collection.
-</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2877129"></a>ADS Level Security</h3></div></div><p>
-For information about the configuration option please refer to the entire section entitled
-<span class="emphasis"><em>Samba as an ADS Domain Member.</em></span>
-</p></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ServerType.html">Prev</a></td><td width="20%" align="center"><a accesskey="u" href="type.html">Up</a></td><td width="40%" align="right"><a accesskey="n" href="samba-pdc.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter3.Nomenclature of Server Types</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">Chapter5.
-Samba as an NT4 or Win2k Primary Domain Controller
-</td></tr></table></div></body></html>
+Windows NT server, the later natively capable of encrypted password support.</P
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+SUMMARY="Footer navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="type.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="samba-howto-collection.html"
+ACCESSKEY="H"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="samba-pdc.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>Type of installation</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="type.html"
+ACCESSKEY="U"
+>Up</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>How to Configure Samba as a NT4 Primary Domain Controller</TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+> \ No newline at end of file
diff --git a/docs/htmldocs/servertype.html b/docs/htmldocs/servertype.html
deleted file mode 100644
index 42a7604797..0000000000
--- a/docs/htmldocs/servertype.html
+++ /dev/null
@@ -1,368 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<HTML
-><HEAD
-><TITLE
->Nomenclature of Server Types</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
-REL="HOME"
-TITLE="SAMBA Project Documentation"
-HREF="samba-howto-collection.html"><LINK
-REL="UP"
-TITLE="Type of installation"
-HREF="type.html"><LINK
-REL="PREVIOUS"
-TITLE="Type of installation"
-HREF="type.html"><LINK
-REL="NEXT"
-TITLE="Samba as Stand-Alone Server"
-HREF="securitylevels.html"></HEAD
-><BODY
-CLASS="CHAPTER"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->SAMBA Project Documentation</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="type.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
-></TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="securitylevels.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="CHAPTER"
-><H1
-><A
-NAME="SERVERTYPE"
-></A
->Chapter 5. Nomenclature of Server Types</H1
-><DIV
-CLASS="TOC"
-><DL
-><DT
-><B
->Table of Contents</B
-></DT
-><DT
->5.1. <A
-HREF="servertype.html#AEN846"
->Stand Alone Server</A
-></DT
-><DT
->5.2. <A
-HREF="servertype.html#AEN853"
->Domain Member Server</A
-></DT
-><DT
->5.3. <A
-HREF="servertype.html#AEN859"
->Domain Controller</A
-></DT
-></DL
-></DIV
-><P
->Adminstrators of Microsoft networks often refer to there being three
-different type of servers:</P
-><P
-></P
-><UL
-><LI
-><P
->Stand Alone Server</P
-></LI
-><LI
-><P
->Domain Member Server</P
-></LI
-><LI
-><P
->Domain Controller</P
-><P
-></P
-><UL
-><LI
-><P
->Primary Domain Controller</P
-></LI
-><LI
-><P
->Backup Domain Controller</P
-></LI
-><LI
-><P
->ADS Domain Controller</P
-></LI
-></UL
-></LI
-></UL
-><P
->A network administrator who is familiar with these terms and who
-wishes to migrate to or use Samba will want to know what these terms mean
-within a Samba context.</P
-><DIV
-CLASS="SECT1"
-><H1
-CLASS="SECT1"
-><A
-NAME="AEN846"
->5.1. Stand Alone Server</A
-></H1
-><P
->The term <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->stand alone server</I
-></SPAN
-> means that the server
-will provide local authentication and access control for all resources
-that are available from it. In general this means that there will be a
-local user database. In more technical terms, it means that resources
-on the machine will either be made available in either SHARE mode or in
-USER mode. SHARE mode and USER mode security are documented under
-discussions regarding "security mode". The smb.conf configuration parameters
-that control security mode are: "security = user" and "security = share".</P
-><P
->No special action is needed other than to create user accounts. Stand-alone
-servers do NOT provide network logon services, meaning that machines that
-use this server do NOT perform a domain logon but instead make use only of
-the MS Windows logon which is local to the MS Windows workstation/server.</P
-><P
->Samba tends to blur the distinction a little in respect of what is
-a stand alone server. This is because the authentication database may be
-local or on a remote server, even if from the samba protocol perspective
-the samba server is NOT a member of a domain security context.</P
-><P
->Through the use of PAM (Pluggable Authentication Modules) and nsswitch
-(the name service switcher) the source of authentication may reside on
-another server. We would be inclined to call this the authentication server.
-This means that the samba server may use the local Unix/Linux system
-password database (/etc/passwd or /etc/shadow), may use a local smbpasswd
-file (/etc/samba/smbpasswd or /usr/local/samba/lib/private/smbpasswd), or
-may use an LDAP back end, or even via PAM and Winbind another CIFS/SMB
-server for authentication.</P
-></DIV
-><DIV
-CLASS="SECT1"
-><H1
-CLASS="SECT1"
-><A
-NAME="AEN853"
->5.2. Domain Member Server</A
-></H1
-><P
->This mode of server operation involves the samba machine being made a member
-of a domain security context. This means by definition that all user authentication
-will be done from a centrally defined authentication regime. The authentication
-regime may come from an NT3/4 style (old domain technology) server, or it may be
-provided from an Active Directory server (ADS) running on MS Windows 2000 or later.</P
-><P
-><SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->Of course it should be clear that the authentication back end itself could be from any
-distributed directory architecture server that is supported by Samba. This can be
-LDAP (from OpenLDAP), or Sun's iPlanet, of NetWare Directory Server, etc.</I
-></SPAN
-></P
-><P
->Please refer to the section on Howto configure Samba as a Primary Domain Controller
-and for more information regarding how to create a domain machine account for a
-domain member server as well as for information regading how to enable the samba
-domain member machine to join the domain and to be fully trusted by it.</P
-></DIV
-><DIV
-CLASS="SECT1"
-><H1
-CLASS="SECT1"
-><A
-NAME="AEN859"
->5.3. Domain Controller</A
-></H1
-><P
->Over the years public perceptions of what Domain Control really is has taken on an
-almost mystical nature. Before we branch into a brief overview of what Domain Control
-is the following types of controller are known:</P
-><DIV
-CLASS="SECT2"
-><H2
-CLASS="SECT2"
-><A
-NAME="AEN862"
->5.3.1. Domain Controller Types</A
-></H2
-><P
-></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
->Primary Domain Controller</TD
-></TR
-><TR
-><TD
->Backup Domain Controller</TD
-></TR
-><TR
-><TD
->ADS Domain Controller</TD
-></TR
-></TBODY
-></TABLE
-><P
-></P
-><P
->The <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->Primary Domain Controller</I
-></SPAN
-> or PDC plays an important role in the MS
-Windows NT3 and NT4 Domain Control architecture, but not in the manner that so many
-expect. The PDC seeds the Domain Control database (a part of the Windows registry) and
-it plays a key part in synchronisation of the domain authentication database. </P
-><P
->New to Samba-3.0.0 is the ability to use a back-end file that holds the same type of data as
-the NT4 style SAM (Security Account Manager) database (one of the registry files).
-The samba-3.0.0 SAM can be specified via the smb.conf file parameter "passwd backend" and
-valid options include <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
-> smbpasswd tdbsam ldapsam nisplussam plugin unixsam</I
-></SPAN
->.
-The smbpasswd, tdbsam and ldapsam options can have a "_nua" suffix to indicate that No Unix
-Accounts need to be created. In other words, the Samba SAM will be independant of Unix/Linux
-system accounts, provided a uid range is defined from which SAM accounts can be created.</P
-><P
->The <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->Backup Domain Controller</I
-></SPAN
-> or BDC plays a key role in servicing network
-authentication requests. The BDC is biased to answer logon requests so that on a network segment
-that has a BDC and a PDC the BDC will be most likely to service network logon requests. The PDC will
-answer network logon requests when the BDC is too busy (high load). A BDC can be promoted to
-a PDC. If the PDC is on line at the time that the BDC is promoted to PDC the previous PDC is
-automatically demoted to a BDC.</P
-><P
->At this time Samba is NOT capable of acting as an <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->ADS Domain Controller</I
-></SPAN
->.</P
-></DIV
-></DIV
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="type.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="samba-howto-collection.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="securitylevels.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Type of installation</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="type.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Samba as Stand-Alone Server</TD
-></TR
-></TABLE
-></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 3a54a894ac..4f02951a9c 100644
--- a/docs/htmldocs/smb.conf.5.html
+++ b/docs/htmldocs/smb.conf.5.html
@@ -1,3103 +1,19776 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>smb.conf</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="smb.conf.5"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>smb.conf &#8212; The configuration file for the Samba suite</p></div><div class="refsect1" lang="en"><h2>SYNOPSIS</h2><p>The <tt>smb.conf</tt> file is a configuration
- file for the Samba suite. <tt>smb.conf</tt> contains
- runtime configuration information for the Samba programs. The <tt>smb.conf</tt> file
- is designed to be configured and administered by the <a href="swat.8.html">swat(8)</a> program. The complete
- description of the file format and possible parameters held within
- are here for reference purposes.</p></div><div class="refsect1" lang="en"><a name="FILEFORMATSECT"></a><h2>FILE FORMAT</h2><p>The file consists of sections and parameters. A section
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
+<HTML
+><HEAD
+><TITLE
+>smb.conf</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"></HEAD
+><BODY
+CLASS="REFENTRY"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><H1
+><A
+NAME="SMB.CONF">smb.conf</H1
+><DIV
+CLASS="REFNAMEDIV"
+><A
+NAME="AEN5"
+></A
+><H2
+>Name</H2
+>smb.conf&nbsp;--&nbsp;The configuration file for the Samba suite</DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN8"
+></A
+><H2
+>SYNOPSIS</H2
+><P
+>The <TT
+CLASS="FILENAME"
+>smb.conf</TT
+> file is a configuration
+ file for the Samba suite. <TT
+CLASS="FILENAME"
+>smb.conf</TT
+> contains
+ runtime configuration information for the Samba programs. The
+ <TT
+CLASS="FILENAME"
+>smb.conf</TT
+> file is designed to be configured and
+ administered by the <A
+HREF="swat.8.html"
+TARGET="_top"
+><B
+CLASS="COMMAND"
+>swat(8)</B
+>
+ </A
+> program. The complete description of the file format and
+ possible parameters held within are here for reference purposes.</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN16"
+></A
+><H2
+>FILE FORMAT</H2
+><P
+>The file consists of sections and parameters. A section
begins with the name of the section in square brackets and continues
until the next section begins. Sections contain parameters of the
- form</p><p><i><tt>name</tt></i> = <i><tt>value
- </tt></i></p><p>The file is line-based - that is, each newline-terminated
- line represents either a comment, a section name or a parameter.</p><p>Section and parameter names are not case sensitive.</p><p>Only the first equals sign in a parameter is significant.
+ form</P
+><P
+><TT
+CLASS="REPLACEABLE"
+><I
+>name</I
+></TT
+> = <TT
+CLASS="REPLACEABLE"
+><I
+>value
+ </I
+></TT
+></P
+><P
+>The file is line-based - that is, each newline-terminated
+ line represents either a comment, a section name or a parameter.</P
+><P
+>Section and parameter names are not case sensitive.</P
+><P
+>Only the first equals sign in a parameter is significant.
Whitespace before or after the first equals sign is discarded.
Leading, trailing and internal whitespace in section and parameter
names is irrelevant. Leading and trailing whitespace in a parameter
value is discarded. Internal whitespace within a parameter value
- is retained verbatim.</p><p>Any line beginning with a semicolon (';') or a hash ('#')
- character is ignored, as are lines containing only whitespace.</p><p>Any line ending in a '\' is continued
- on the next line in the customary UNIX fashion.</p><p>The values following the equals sign in parameters are all
+ is retained verbatim.</P
+><P
+>Any line beginning with a semicolon (';') or a hash ('#')
+ character is ignored, as are lines containing only whitespace.</P
+><P
+>Any line ending in a '\' is continued
+ on the next line in the customary UNIX fashion.</P
+><P
+>The values following the equals sign in parameters are all
either a string (no quotes needed) or a boolean, which may be given
as yes/no, 0/1 or true/false. Case is not significant in boolean
values, but is preserved in string values. Some items such as
- create modes are numeric.</p></div><div class="refsect1" lang="en"><h2>SECTION DESCRIPTIONS</h2><p>Each section in the configuration file (except for the
+ create modes are numeric.</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN28"
+></A
+><H2
+>SECTION DESCRIPTIONS</H2
+><P
+>Each section in the configuration file (except for the
[global] section) describes a shared resource (known
- as a &quot;share&quot;). The section name is the name of the
+ as a "share"). The section name is the name of the
shared resource and the parameters within the section define
- the shares attributes.</p><p>There are three special sections, [global],
+ the shares attributes.</P
+><P
+>There are three special sections, [global],
[homes] and [printers], which are
- described under <span class="emphasis"><em>special sections</em></span>. The
- following notes apply to ordinary section descriptions.</p><p>A share consists of a directory to which access is being
+ described under <I
+CLASS="EMPHASIS"
+>special sections</I
+>. The
+ following notes apply to ordinary section descriptions.</P
+><P
+>A share consists of a directory to which access is being
given plus a description of the access rights which are granted
to the user of the service. Some housekeeping options are
- also specifiable.</p><p>Sections are either file share services (used by the
+ also specifiable.</P
+><P
+>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><p>Sections may be designated <span class="emphasis"><em>guest</em></span> services,
+ on the host running the server).</P
+><P
+>Sections may be designated <I
+CLASS="EMPHASIS"
+>guest</I
+> services,
in which case no password is required to access them. A specified
- UNIX <span class="emphasis"><em>guest account</em></span> is used to define access
- privileges in this case.</p><p>Sections other than guest services will require a password
+ UNIX <I
+CLASS="EMPHASIS"
+>guest account</I
+> is used to define access
+ privileges in this case.</P
+><P
+>Sections other than guest services will require a password
to access them. The client provides the username. As older clients
only provide passwords and not usernames, you may specify a list
- of usernames to check against the password using the &quot;user =&quot;
+ of usernames to check against the password using the "user ="
option in the share definition. For modern clients such as
- Windows 95/98/ME/NT/2000, this should not be necessary.</p><p>Note that the access rights granted by the server are
+ Windows 95/98/ME/NT/2000, this should not be necessary.</P
+><P
+>Note that the access rights granted by the server are
masked by the access rights granted to the specified or guest
UNIX user by the host system. The server does not grant more
- access than the host system grants.</p><p>The following sample section defines a file space share.
- The user has write access to the path <tt>/home/bar</tt>.
- The share is accessed via the share name &quot;foo&quot;:</p><pre class="screen">
-<tt>
-[foo]
- path = /home/bar
- read only = no
-</tt>
-</pre><p>The following sample section defines a printable share.
+ access than the host system grants.</P
+><P
+>The following sample section defines a file space share.
+ The user has write access to the path <TT
+CLASS="FILENAME"
+>/home/bar</TT
+>.
+ The share is accessed via the share name "foo":</P
+><TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><PRE
+CLASS="SCREEN"
+> <TT
+CLASS="COMPUTEROUTPUT"
+> [foo]
+ path = /home/bar
+ read only = no
+ </TT
+>
+ </PRE
+></TD
+></TR
+></TABLE
+><P
+>The following sample section defines a printable share.
The share is readonly, but printable. That is, the only write
access permitted is via calls to open, write to and close a
- spool file. The <span class="emphasis"><em>guest ok</em></span> parameter means
+ spool file. The <I
+CLASS="EMPHASIS"
+>guest ok</I
+> parameter means
access will be permitted as the default guest user (specified
- elsewhere):</p><pre class="screen">
-<tt>
-[aprinter]
- path = /usr/spool/public
- read only = yes
- printable = yes
- guest ok = yes
-</tt>
-</pre></div><div class="refsect1" lang="en"><h2>SPECIAL SECTIONS</h2><div class="refsect2" lang="en"><h3>The [global] section</h3><p>parameters in this section apply to the server
+ elsewhere):</P
+><TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><PRE
+CLASS="SCREEN"
+> <TT
+CLASS="COMPUTEROUTPUT"
+> [aprinter]
+ path = /usr/spool/public
+ read only = yes
+ printable = yes
+ guest ok = yes
+ </TT
+>
+ </PRE
+></TD
+></TR
+></TABLE
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN48"
+></A
+><H2
+>SPECIAL SECTIONS</H2
+><DIV
+CLASS="REFSECT2"
+><A
+NAME="AEN50"
+></A
+><H3
+>The [global] section</H3
+><P
+>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></div><div class="refsect2" lang="en"><a name="HOMESECT"></a><h3>The [homes] section</h3><p>If a section called homes is included in the
+ under PARAMETERS for more information.</P
+></DIV
+><DIV
+CLASS="REFSECT2"
+><A
+NAME="AEN53"
+></A
+><H3
+>The [homes] section</H3
+><P
+>If a section called homes is included in the
configuration file, services connecting clients to their
- home directories can be created on the fly by the server.</p><p>When the connection request is made, the existing
+ home directories can be created on the fly by the server.</P
+><P
+>When the connection request is made, the existing
sections are scanned. If a match is found, it is used. If no
match is found, the requested section name is treated as a
user name and looked up in the local password file. If the
name exists and the correct password has been given, a share is
- created by cloning the [homes] section.</p><p>Some modifications are then made to the newly
- created share:</p><div class="itemizedlist"><ul type="disc"><li><p>The share name is changed from homes to
- the located username.</p></li><li><p>If no path was given, the path is set to
- the user's home directory.</p></li></ul></div><p>If you decide to use a <span class="emphasis"><em>path =</em></span> line
+ created by cloning the [homes] section.</P
+><P
+>Some modifications are then made to the newly
+ created share:</P
+><P
+></P
+><UL
+><LI
+><P
+>The share name is changed from homes to
+ the located username.</P
+></LI
+><LI
+><P
+>If no path was given, the path is set to
+ the user's home directory.</P
+></LI
+></UL
+><P
+>If you decide to use a <I
+CLASS="EMPHASIS"
+>path =</I
+> line
in your [homes] section then you may find it useful
- to use the %S macro. For example :</p><p><b><tt>path = /data/pchome/%S</tt></b></p><p>would be useful if you have different home directories
- for your PCs than for UNIX access.</p><p>This is a fast and simple way to give a large number
+ to use the %S macro. For example :</P
+><P
+><TT
+CLASS="USERINPUT"
+><B
+>path = /data/pchome/%S</B
+></TT
+></P
+><P
+>would be useful if you have different home directories
+ for your PCs than for UNIX access.</P
+><P
+>This is a fast and simple way to give a large number
of clients access to their home directories with a minimum
- of fuss.</p><p>A similar process occurs if the requested section
- name is &quot;homes&quot;, except that the share name is not
+ of fuss.</P
+><P
+>A similar process occurs if the requested section
+ name is "homes", except that the share name is not
changed to that of the requesting user. This method of using
the [homes] section works well if different users share
- a client PC.</p><p>The [homes] section can specify all the parameters
+ a client PC.</P
+><P
+>The [homes] section can specify all the parameters
a normal service section can specify, though some make more sense
than others. The following is a typical and suitable [homes]
- section:</p><pre class="screen">
-<tt>
-[homes]
- read only = no
-</tt>
-</pre><p>An important point is that if guest access is specified
+ section:</P
+><TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><PRE
+CLASS="SCREEN"
+> <TT
+CLASS="COMPUTEROUTPUT"
+> [homes]
+ read only = no
+ </TT
+>
+ </PRE
+></TD
+></TR
+></TABLE
+><P
+>An important point is that if guest access is specified
in the [homes] section, all home directories will be
- visible to all clients <span class="emphasis"><em>without a password</em></span>.
+ visible to all clients <I
+CLASS="EMPHASIS"
+>without a password</I
+>.
In the very unlikely event that this is actually desirable, it
- would be wise to also specify <span class="emphasis"><em>read only
- access</em></span>.</p><p>Note that the <span class="emphasis"><em>browseable</em></span> flag for
+ would be wise to also specify <I
+CLASS="EMPHASIS"
+>read only
+ access</I
+>.</P
+><P
+>Note that the <I
+CLASS="EMPHASIS"
+>browseable</I
+> flag for
auto home directories will be inherited from the global browseable
flag, not the [homes] browseable flag. This is useful as
- it means setting <span class="emphasis"><em>browseable = no</em></span> in
+ it means setting <I
+CLASS="EMPHASIS"
+>browseable = no</I
+> in
the [homes] section will hide the [homes] share but make
- any auto home directories visible.</p></div><div class="refsect2" lang="en"><a name="PRINTERSSECT"></a><h3>The [printers] section</h3><p>This section works like [homes],
- but for printers.</p><p>If a [printers] section occurs in the
+ any auto home directories visible.</P
+></DIV
+><DIV
+CLASS="REFSECT2"
+><A
+NAME="AEN79"
+></A
+><H3
+>The [printers] section</H3
+><P
+>This section works like [homes],
+ but for printers.</P
+><P
+>If a [printers] section occurs in the
configuration file, users are able to connect to any printer
- specified in the local host's printcap file.</p><p>When a connection request is made, the existing sections
+ specified in the local host's printcap file.</P
+><P
+>When a connection request is made, the existing sections
are scanned. If a match is found, it is used. If no match is found,
but a [homes] section exists, it is used as described
above. Otherwise, the requested section name is treated as a
printer name and the appropriate printcap file is scanned to see
if the requested section name is a valid printer share name. If
a match is found, a new printer share is created by cloning
- the [printers] section.</p><p>A few modifications are then made to the newly created
- share:</p><div class="itemizedlist"><ul type="disc"><li><p>The share name is set to the located printer
- name</p></li><li><p>If no printer name was given, the printer name
- is set to the located printer name</p></li><li><p>If the share does not permit guest access and
+ the [printers] section.</P
+><P
+>A few modifications are then made to the newly created
+ share:</P
+><P
+></P
+><UL
+><LI
+><P
+>The share name is set to the located printer
+ name</P
+></LI
+><LI
+><P
+>If no printer name was given, the printer name
+ is set to the located printer name</P
+></LI
+><LI
+><P
+>If the share does not permit guest access and
no username was given, the username is set to the located
- printer name.</p></li></ul></div><p>Note that the [printers] service MUST be
+ printer name.</P
+></LI
+></UL
+><P
+>Note that the [printers] service MUST be
printable - if you specify otherwise, the server will refuse
- to load the configuration file.</p><p>Typically the path specified would be that of a
+ to load the configuration file.</P
+><P
+>Typically the path specified would be that of a
world-writeable spool directory with the sticky bit set on
it. A typical [printers] entry would look like
- this:</p><pre class="screen"><tt>
-[printers]
- path = /usr/spool/public
- guest ok = yes
- printable = yes
-</tt></pre><p>All aliases given for a printer in the printcap file
+ this:</P
+><TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><PRE
+CLASS="SCREEN"
+><TT
+CLASS="COMPUTEROUTPUT"
+> [printers]
+ path = /usr/spool/public
+ guest ok = yes
+ printable = yes
+ </TT
+></PRE
+></TD
+></TR
+></TABLE
+><P
+>All aliases given for a printer in the printcap file
are legitimate printer names as far as the server is concerned.
If your printing subsystem doesn't work like that, you will have
to set up a pseudo-printcap. This is a file consisting of one or
- more lines like this:</p><pre class="screen">
-<tt>
-alias|alias|alias|alias...
-</tt>
-</pre><p>Each alias should be an acceptable printer name for
+ more lines like this:</P
+><TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><PRE
+CLASS="SCREEN"
+> <TT
+CLASS="COMPUTEROUTPUT"
+> alias|alias|alias|alias...
+ </TT
+>
+ </PRE
+></TD
+></TR
+></TABLE
+><P
+>Each alias should be an acceptable printer name for
your printing subsystem. In the [global] section, specify
the new file as your printcap. The server will then only recognize
names found in your pseudo-printcap, which of course can contain
whatever aliases you like. The same technique could be used
- simply to limit access to a subset of your local printers.</p><p>An alias, by the way, is defined as any component of the
+ simply to limit access to a subset of your local printers.</P
+><P
+>An alias, by the way, is defined as any component of the
first entry of a printcap record. Records are separated by newlines,
components (if there are more than one) are separated by vertical
- bar symbols ('|').</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>On SYSV systems which use lpstat to determine what
+ bar symbols ('|').</P
+><P
+>NOTE: On SYSV systems which use lpstat to determine what
printers are defined on the system you may be able to use
- &quot;printcap name = lpstat&quot; to automatically obtain a list
- of printers. See the &quot;printcap name&quot; option
- for more details.</p></div></div></div><div class="refsect1" lang="en"><h2>PARAMETERS</h2><p>parameters define the specific attributes of sections.</p><p>Some parameters are specific to the [global] section
- (e.g., <span class="emphasis"><em>security</em></span>). Some parameters are usable
- in all sections (e.g., <span class="emphasis"><em>create mode</em></span>). All others
+ "printcap name = lpstat" to automatically obtain a list
+ of printers. See the "printcap name" option
+ for more details.</P
+></DIV
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN102"
+></A
+><H2
+>PARAMETERS</H2
+><P
+>parameters define the specific attributes of sections.</P
+><P
+>Some parameters are specific to the [global] section
+ (e.g., <I
+CLASS="EMPHASIS"
+>security</I
+>). Some parameters are usable
+ in all sections (e.g., <I
+CLASS="EMPHASIS"
+>create mode</I
+>). All others
are permissible only in normal sections. For the purposes of the
following descriptions the [homes] and [printers]
- sections will be considered normal. The letter <span class="emphasis"><em>G</em></span>
+ sections will be considered normal. The letter <I
+CLASS="EMPHASIS"
+>G</I
+>
in parentheses indicates that a parameter is specific to the
- [global] section. The letter <span class="emphasis"><em>S</em></span>
+ [global] section. The letter <I
+CLASS="EMPHASIS"
+>S</I
+>
indicates that a parameter can be specified in a service specific
- section. Note that all <span class="emphasis"><em>S</em></span> parameters can also be specified in
+ section. Note that all <I
+CLASS="EMPHASIS"
+>S</I
+> parameters can also be specified in
the [global] section - in which case they will define
- the default behavior for all services.</p><p>parameters are arranged here in alphabetical order - this may
+ the default behavior for all services.</P
+><P
+>parameters are arranged here in alphabetical order - this may
not create best bedfellows, but at least you can find them! Where
there are synonyms, the preferred synonym is described, others refer
- to the preferred synonym.</p></div><div class="refsect1" lang="en"><h2>VARIABLE SUBSTITUTIONS</h2><p>Many of the strings that are settable in the config file
- can take substitutions. For example the option &quot;path =
- /tmp/%u&quot; would be interpreted as &quot;path =
- /tmp/john&quot; if the user connected with the username john.</p><p>These substitutions are mostly noted in the descriptions below,
+ to the preferred synonym.</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN112"
+></A
+><H2
+>VARIABLE SUBSTITUTIONS</H2
+><P
+>Many of the strings that are settable in the config file
+ can take substitutions. For example the option "path =
+ /tmp/%u" would be interpreted as "path =
+ /tmp/john" if the user connected with the username john.</P
+><P
+>These substitutions are mostly noted in the descriptions below,
but there are some general substitutions which apply whenever they
- might be relevant. These are:</p><div class="variablelist"><dl><dt><span class="term">%U</span></dt><dd><p>session user name (the user name that the client
- wanted, not necessarily the same as the one they got).</p></dd><dt><span class="term">%G</span></dt><dd><p>primary group name of %U.</p></dd><dt><span class="term">%h</span></dt><dd><p>the Internet hostname that Samba is running
- on.</p></dd><dt><span class="term">%m</span></dt><dd><p>the NetBIOS name of the client machine
- (very useful).</p></dd><dt><span class="term">%L</span></dt><dd><p>the NetBIOS name of the server. This allows you
+ might be relevant. These are:</P
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>%U</DT
+><DD
+><P
+>session user name (the user name that the client
+ wanted, not necessarily the same as the one they got).</P
+></DD
+><DT
+>%G</DT
+><DD
+><P
+>primary group name of %U.</P
+></DD
+><DT
+>%h</DT
+><DD
+><P
+>the Internet hostname that Samba is running
+ on.</P
+></DD
+><DT
+>%m</DT
+><DD
+><P
+>the NetBIOS name of the client machine
+ (very useful).</P
+></DD
+><DT
+>%L</DT
+><DD
+><P
+>the NetBIOS name of the server. This allows you
to change your config based on what the client calls you. Your
- server can have a &quot;dual personality&quot;.</p><p>Note that this parameter is not available when Samba listens
- on port 445, as clients no longer send this information </p></dd><dt><span class="term">%M</span></dt><dd><p>the Internet name of the client machine.
- </p></dd><dt><span class="term">%R</span></dt><dd><p>the selected protocol level after
+ server can have a "dual personality".</P
+><P
+>Note that this parameter is not available when Samba listens
+ on port 445, as clients no longer send this information </P
+></DD
+><DT
+>%M</DT
+><DD
+><P
+>the Internet name of the client machine.
+ </P
+></DD
+><DT
+>%R</DT
+><DD
+><P
+>the selected protocol level after
protocol negotiation. It can be one of CORE, COREPLUS,
- LANMAN1, LANMAN2 or NT1.</p></dd><dt><span class="term">%d</span></dt><dd><p>The process id of the current server
- process.</p></dd><dt><span class="term">%a</span></dt><dd><p>the architecture of the remote
+ LANMAN1, LANMAN2 or NT1.</P
+></DD
+><DT
+>%d</DT
+><DD
+><P
+>The process id of the current server
+ process.</P
+></DD
+><DT
+>%a</DT
+><DD
+><P
+>the architecture of the remote
machine. Only some are recognized, and those may not be
100% reliable. It currently recognizes Samba, WfWg, Win95,
WinNT and Win2k. Anything else will be known as
- &quot;UNKNOWN&quot;. If it gets it wrong then sending a level
- 3 log to <a href="mailto:samba@samba.org" target="_top">samba@samba.org
- </a> should allow it to be fixed.</p></dd><dt><span class="term">%I</span></dt><dd><p>The IP address of the client machine.</p></dd><dt><span class="term">%T</span></dt><dd><p>the current date and time.</p></dd><dt><span class="term">%D</span></dt><dd><p>Name of the domain or workgroup of the current user.</p></dd><dt><span class="term">%$(<i><tt>envvar</tt></i>)</span></dt><dd><p>The value of the environment variable
- <i><tt>envar</tt></i>.</p></dd></dl></div><p>The following substitutes apply only to some configuration options(only those
- that are used when a connection has been established):</p><div class="variablelist"><dl><dt><span class="term">%S</span></dt><dd><p>the name of the current service, if any.</p></dd><dt><span class="term">%P</span></dt><dd><p>the root directory of the current service,
- if any.</p></dd><dt><span class="term">%u</span></dt><dd><p>user name of the current service, if any.</p></dd><dt><span class="term">%g</span></dt><dd><p>primary group name of %u.</p></dd><dt><span class="term">%H</span></dt><dd><p>the home directory of the user given
- by %u.</p></dd><dt><span class="term">%N</span></dt><dd><p>the name of your NIS home directory server.
+ "UNKNOWN". If it gets it wrong then sending a level
+ 3 log to <A
+HREF="mailto:samba@samba.org"
+TARGET="_top"
+>samba@samba.org
+ </A
+> should allow it to be fixed.</P
+></DD
+><DT
+>%I</DT
+><DD
+><P
+>The IP address of the client machine.</P
+></DD
+><DT
+>%T</DT
+><DD
+><P
+>the current date and time.</P
+></DD
+><DT
+>%D</DT
+><DD
+><P
+>Name of the domain or workgroup of the current user.</P
+></DD
+><DT
+>%$(<TT
+CLASS="REPLACEABLE"
+><I
+>envvar</I
+></TT
+>)</DT
+><DD
+><P
+>The value of the environment variable
+ <TT
+CLASS="REPLACEABLE"
+><I
+>envar</I
+></TT
+>.</P
+></DD
+></DL
+></DIV
+><P
+>The following substitutes apply only to some configuration options(only those
+ that are used when a connection has been established):</P
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>%S</DT
+><DD
+><P
+>the name of the current service, if any.</P
+></DD
+><DT
+>%P</DT
+><DD
+><P
+>the root directory of the current service,
+ if any.</P
+></DD
+><DT
+>%u</DT
+><DD
+><P
+>user name of the current service, if any.</P
+></DD
+><DT
+>%g</DT
+><DD
+><P
+>primary group name of %u.</P
+></DD
+><DT
+>%H</DT
+><DD
+><P
+>the home directory of the user given
+ by %u.</P
+></DD
+><DT
+>%N</DT
+><DD
+><P
+>the name of your NIS home directory server.
This is obtained from your NIS auto.map entry. If you have
- not compiled Samba with the <span class="emphasis"><em>--with-automount</em></span>
- option then this value will be the same as %L.</p></dd><dt><span class="term">%p</span></dt><dd><p>the path of the service's home directory,
+ not compiled Samba with the <I
+CLASS="EMPHASIS"
+>--with-automount</I
+>
+ option then this value will be the same as %L.</P
+></DD
+><DT
+>%p</DT
+><DD
+><P
+>the path of the service's home directory,
obtained from your NIS auto.map entry. The NIS auto.map entry
- is split up as &quot;%N:%p&quot;.</p></dd></dl></div><p>There are some quite creative things that can be done
- with these substitutions and other smb.conf options.</p></div><div class="refsect1" lang="en"><a name="NAMEMANGLINGSECT"></a><h2>NAME MANGLING</h2><p>Samba supports &quot;name mangling&quot; so that DOS and
+ is split up as "%N:%p".</P
+></DD
+></DL
+></DIV
+><P
+>There are some quite creative things that can be done
+ with these substitutions and other smb.conf options.</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN205"
+></A
+><H2
+>NAME MANGLING</H2
+><P
+>Samba supports "name mangling" so that DOS and
Windows clients can use files that don't conform to the 8.3 format.
- It can also be set to adjust the case of 8.3 format filenames.</p><p>There are several options that control the way mangling is
+ It can also be set to adjust the case of 8.3 format filenames.</P
+><P
+>There are several options that control the way mangling is
performed, and they are grouped here rather than listed separately.
- For the defaults look at the output of the testparm program. </p><p>All of these options can be set separately for each service
- (or globally, of course). </p><p>The options are: </p><div class="variablelist"><dl><dt><span class="term">mangle case = yes/no</span></dt><dd><p> controls if names that have characters that
- aren't of the &quot;default&quot; case are mangled. For example,
- if this is yes then a name like &quot;Mail&quot; would be mangled.
- Default <span class="emphasis"><em>no</em></span>.</p></dd><dt><span class="term">case sensitive = yes/no</span></dt><dd><p>controls whether filenames are case sensitive. If
+ For the defaults look at the output of the testparm program. </P
+><P
+>All of these options can be set separately for each service
+ (or globally, of course). </P
+><P
+>The options are: </P
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>mangle case = yes/no</DT
+><DD
+><P
+> controls if names that have characters that
+ aren't of the "default" case are mangled. For example,
+ if this is yes then a name like "Mail" would be mangled.
+ Default <I
+CLASS="EMPHASIS"
+>no</I
+>.</P
+></DD
+><DT
+>case sensitive = yes/no</DT
+><DD
+><P
+>controls whether filenames are case sensitive. If
they aren't then Samba must do a filename search and match on passed
- names. Default <span class="emphasis"><em>no</em></span>.</p></dd><dt><span class="term">default case = upper/lower</span></dt><dd><p>controls what the default case is for new
- filenames. Default <span class="emphasis"><em>lower</em></span>.</p></dd><dt><span class="term">preserve case = yes/no</span></dt><dd><p>controls if new files are created with the
+ names. Default <I
+CLASS="EMPHASIS"
+>no</I
+>.</P
+></DD
+><DT
+>default case = upper/lower</DT
+><DD
+><P
+>controls what the default case is for new
+ filenames. Default <I
+CLASS="EMPHASIS"
+>lower</I
+>.</P
+></DD
+><DT
+>preserve case = yes/no</DT
+><DD
+><P
+>controls if new files are created with the
case that the client passes, or if they are forced to be the
- &quot;default&quot; case. Default <span class="emphasis"><em>yes</em></span>.
- </p></dd><dt><span class="term">short preserve case = yes/no</span></dt><dd><p>controls if new files which conform to 8.3 syntax,
+ "default" case. Default <I
+CLASS="EMPHASIS"
+>yes</I
+>.
+ </P
+></DD
+><DT
+>short preserve case = yes/no</DT
+><DD
+><P
+>controls if new files which conform to 8.3 syntax,
that is all in upper case and of suitable length, are created
- upper case, or if they are forced to be the &quot;default&quot;
- case. This option can be use with &quot;preserve case = yes&quot;
+ upper case, or if they are forced to be the "default"
+ case. This option can be use with "preserve case = yes"
to permit long filenames to retain their case, while short names
- are lowercased. Default <span class="emphasis"><em>yes</em></span>.</p></dd></dl></div><p>By default, Samba 3.0 has the same semantics as a Windows
- NT server, in that it is case insensitive but case preserving.</p></div><div class="refsect1" lang="en"><a name="VALIDATIONSECT"></a><h2>NOTE ABOUT USERNAME/PASSWORD VALIDATION</h2><p>There are a number of ways in which a user can connect
+ are lowercased. Default <I
+CLASS="EMPHASIS"
+>yes</I
+>.</P
+></DD
+></DL
+></DIV
+><P
+>By default, Samba 3.0 has the same semantics as a Windows
+ NT server, in that it is case insensitive but case preserving.</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN238"
+></A
+><H2
+>NOTE ABOUT USERNAME/PASSWORD VALIDATION</H2
+><P
+>There are a number of ways in which a user can connect
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. However, if one of the
- steps succeeds, then the following steps are not checked.</p><p>If the service is marked &quot;guest only = yes&quot; and the
- server is running with share-level security (&quot;security = share&quot;)
- then steps 1 to 5 are skipped.</p><div class="orderedlist"><ol type="1"><li><p>If the client has passed a username/password
+ steps succeeds, then the following steps are not checked.</P
+><P
+>If the service is marked "guest only = yes" and the
+ server is running with share-level security ("security = share")
+ then steps 1 to 5 are skipped.</P
+><P
+></P
+><OL
+TYPE="1"
+><LI
+><P
+>If the client has passed a username/password
pair and that username/password pair is validated by the UNIX
system's password programs then the connection is made as that
username. Note that this includes the
- \\server\service%<i><tt>username</tt></i> method of passing
- a username.</p></li><li><p>If the client has previously registered a username
+ \\server\service%<TT
+CLASS="REPLACEABLE"
+><I
+>username</I
+></TT
+> method of passing
+ a username.</P
+></LI
+><LI
+><P
+>If the client has previously registered a username
with the system and now supplies a correct password for that
- username then the connection is allowed.</p></li><li><p>The client's NetBIOS name and any previously
+ username then the connection is allowed.</P
+></LI
+><LI
+><P
+>The client's NetBIOS name and any previously
used user names are checked against the supplied password, if
they match then the connection is allowed as the corresponding
- user.</p></li><li><p>If the client has previously validated a
+ user.</P
+></LI
+><LI
+><P
+>If the client has previously validated a
username/password pair with the server and the client has passed
- the validation token then that username is used. </p></li><li><p>If a &quot;user = &quot; field is given in the
- <tt>smb.conf</tt> file for the service and the client
+ the validation token then that username is used. </P
+></LI
+><LI
+><P
+>If a "user = " field is given in the
+ <TT
+CLASS="FILENAME"
+>smb.conf</TT
+> file for the service and the client
has supplied a password, and that password matches (according to
the UNIX system's password checking) with one of the usernames
- from the &quot;user =&quot; field then the connection is made as
- the username in the &quot;user =&quot; line. If one
- of the username in the &quot;user =&quot; list begins with a
+ from the "user =" field then the connection is made as
+ the username in the "user =" line. If one
+ of the username in the "user =" list begins with a
'@' then that name expands to a list of names in
- the group of the same name.</p></li><li><p>If the service is a guest service then a
- connection is made as the username given in the &quot;guest
- account =&quot; for the service, irrespective of the
- supplied password.</p></li></ol></div></div><div class="refsect1" lang="en"><h2>COMPLETE LIST OF GLOBAL PARAMETERS</h2><p>Here is a list of all global parameters. See the section of
- each parameter for details. Note that some are synonyms.</p><div class="itemizedlist"><ul type="disc"><li><p><a href="#ABORTSHUTDOWNSCRIPT"><i><tt>abort shutdown script</tt></i></a></p></li><li><p><a href="#ADDGROUPSCRIPT"><i><tt>add group script</tt></i></a></p></li><li><p><a href="#ADDMACHINESCRIPT"><i><tt>add machine script</tt></i></a></p></li><li><p><a href="#ADDPRINTERCOMMAND"><i><tt>addprinter command</tt></i></a></p></li><li><p><a href="#ADDSHARECOMMAND"><i><tt>add share command</tt></i></a></p></li><li><p><a href="#ADDUSERSCRIPT"><i><tt>add user script</tt></i></a></p></li><li><p><a href="#ADDUSERTOGROUPSCRIPT"><i><tt>add user to group script</tt></i></a></p></li><li><p><a href="#ADSSERVER"><i><tt>ads server</tt></i></a></p></li><li><p><a href="#ALGORITHMICRIDBASE"><i><tt>algorithmic rid base</tt></i></a></p></li><li><p><a href="#ALLOWTRUSTEDDOMAINS"><i><tt>allow trusted domains</tt></i></a></p></li><li><p><a href="#ANNOUNCEAS"><i><tt>announce as</tt></i></a></p></li><li><p><a href="#ANNOUNCEVERSION"><i><tt>announce version</tt></i></a></p></li><li><p><a href="#AUTHMETHODS"><i><tt>auth methods</tt></i></a></p></li><li><p><a href="#AUTOSERVICES"><i><tt>auto services</tt></i></a></p></li><li><p><a href="#BINDINTERFACESONLY"><i><tt>bind interfaces only</tt></i></a></p></li><li><p><a href="#BROWSELIST"><i><tt>browse list</tt></i></a></p></li><li><p><a href="#CHANGENOTIFYTIMEOUT"><i><tt>change notify timeout</tt></i></a></p></li><li><p><a href="#CHANGESHARECOMMAND"><i><tt>change share command</tt></i></a></p></li><li><p><a href="#CONFIGFILE"><i><tt>config file</tt></i></a></p></li><li><p><a href="#DEADTIME"><i><tt>dead time</tt></i></a></p></li><li><p><a href="#DEBUGHIRESTIMESTAMP"><i><tt>debug hires timestamp</tt></i></a></p></li><li><p><a href="#DEBUGLEVEL"><i><tt>debug level</tt></i></a></p></li><li><p><a href="#DEBUGPID"><i><tt>debug pid</tt></i></a></p></li><li><p><a href="#DEBUGTIMESTAMP"><i><tt>debug timestamp</tt></i></a></p></li><li><p><a href="#DEBUGUID"><i><tt>debug uid</tt></i></a></p></li><li><p><a href="#DEFAULTSERVICE"><i><tt>default service</tt></i></a></p></li><li><p><a href="#DEFAULT"><i><tt>default</tt></i></a></p></li><li><p><a href="#DELETEGROUPSCRIPT"><i><tt>delete group script</tt></i></a></p></li><li><p><a href="#DELETEPRINTERCOMMAND"><i><tt>deleteprinter command</tt></i></a></p></li><li><p><a href="#DELETESHARECOMMAND"><i><tt>delete share command</tt></i></a></p></li><li><p><a href="#DELETEUSERFROMGROUPSCRIPT"><i><tt>delete user from group script</tt></i></a></p></li><li><p><a href="#DELETEUSERSCRIPT"><i><tt>delete user script</tt></i></a></p></li><li><p><a href="#DFREECOMMAND"><i><tt>dfree command</tt></i></a></p></li><li><p><a href="#DISABLENETBIOS"><i><tt>disable netbios</tt></i></a></p></li><li><p><a href="#DISABLESPOOLSS"><i><tt>disable spoolss</tt></i></a></p></li><li><p><a href="#DISPLAYCHARSET"><i><tt>display charset</tt></i></a></p></li><li><p><a href="#DNSPROXY"><i><tt>dns proxy</tt></i></a></p></li><li><p><a href="#DOMAINLOGONS"><i><tt>domain logons</tt></i></a></p></li><li><p><a href="#DOMAINMASTER"><i><tt>domain master</tt></i></a></p></li><li><p><a href="#DOSCHARSET"><i><tt>dos charset</tt></i></a></p></li><li><p><a href="#ENCRYPTPASSWORDS"><i><tt>encrypt passwords</tt></i></a></p></li><li><p><a href="#ENHANCEDBROWSING"><i><tt>enhanced browsing</tt></i></a></p></li><li><p><a href="#ENUMPORTSCOMMAND"><i><tt>enumports command</tt></i></a></p></li><li><p><a href="#GETWDCACHE"><i><tt>getwd cache</tt></i></a></p></li><li><p><a href="#GUESTACCOUNT"><i><tt>guest account</tt></i></a></p></li><li><p><a href="#HIDELOCALUSERS"><i><tt>hide local users</tt></i></a></p></li><li><p><a href="#HOMEDIRMAP"><i><tt>homedir map</tt></i></a></p></li><li><p><a href="#HOSTMSDFS"><i><tt>host msdfs</tt></i></a></p></li><li><p><a href="#HOSTNAMELOOKUPS"><i><tt>hostname lookups</tt></i></a></p></li><li><p><a href="#HOSTSEQUIV"><i><tt>hosts equiv</tt></i></a></p></li><li><p><a href="#INCLUDE"><i><tt>include</tt></i></a></p></li><li><p><a href="#INTERFACES"><i><tt>interfaces</tt></i></a></p></li><li><p><a href="#KEEPALIVE"><i><tt>keepalive</tt></i></a></p></li><li><p><a href="#KERNELOPLOCKS"><i><tt>kernel oplocks</tt></i></a></p></li><li><p><a href="#LANMANAUTH"><i><tt>lanman auth</tt></i></a></p></li><li><p><a href="#LARGEREADWRITE"><i><tt>large readwrite</tt></i></a></p></li><li><p><a href="#LDAPADMINDN"><i><tt>ldap admin dn</tt></i></a></p></li><li><p><a href="#LDAPDELETEDN"><i><tt>ldap delete dn</tt></i></a></p></li><li><p><a href="#LDAPFILTER"><i><tt>ldap filter</tt></i></a></p></li><li><p><a href="#LDAPMACHINESUFFIX"><i><tt>ldap machine suffix</tt></i></a></p></li><li><p><a href="#LDAPPASSWDSYNC"><i><tt>ldap passwd sync</tt></i></a></p></li><li><p><a href="#LDAPPORT"><i><tt>ldap port</tt></i></a></p></li><li><p><a href="#LDAPSERVER"><i><tt>ldap server</tt></i></a></p></li><li><p><a href="#LDAPSSL"><i><tt>ldap ssl</tt></i></a></p></li><li><p><a href="#LDAPSUFFIX"><i><tt>ldap suffix</tt></i></a></p></li><li><p><a href="#LDAPTRUSTIDS"><i><tt>ldap trust ids</tt></i></a></p></li><li><p><a href="#LDAPUSERSUFFIX"><i><tt>ldap user suffix</tt></i></a></p></li><li><p><a href="#LMANNOUNCE"><i><tt>lm announce</tt></i></a></p></li><li><p><a href="#LMINTERVAL"><i><tt>lm interval</tt></i></a></p></li><li><p><a href="#LOADPRINTERS"><i><tt>load printers</tt></i></a></p></li><li><p><a href="#LOCALMASTER"><i><tt>local master</tt></i></a></p></li><li><p><a href="#LOCKDIRECTORY"><i><tt>lock directory</tt></i></a></p></li><li><p><a href="#LOCKDIR"><i><tt>lock dir</tt></i></a></p></li><li><p><a href="#LOCKSPINCOUNT"><i><tt>lock spin count</tt></i></a></p></li><li><p><a href="#LOCKSPINTIME"><i><tt>lock spin time</tt></i></a></p></li><li><p><a href="#LOGFILE"><i><tt>log file</tt></i></a></p></li><li><p><a href="#LOGLEVEL"><i><tt>log level</tt></i></a></p></li><li><p><a href="#LOGONDRIVE"><i><tt>logon drive</tt></i></a></p></li><li><p><a href="#LOGONHOME"><i><tt>logon home</tt></i></a></p></li><li><p><a href="#LOGONPATH"><i><tt>logon path</tt></i></a></p></li><li><p><a href="#LOGONSCRIPT"><i><tt>logon script</tt></i></a></p></li><li><p><a href="#LPQCACHETIME"><i><tt>lpq cache time</tt></i></a></p></li><li><p><a href="#MACHINEPASSWORDTIMEOUT"><i><tt>machine password timeout</tt></i></a></p></li><li><p><a href="#MANGLINGSTACK"><i><tt>mangling stack</tt></i></a></p></li><li><p><a href="#MANGLINGPREFIX"><i><tt>mangling prefix</tt></i></a></p></li><li><p><a href="#MANGLINGMETHOD"><i><tt>mangling method</tt></i></a></p></li><li><p><a href="#MAPTOGUEST"><i><tt>map to guest</tt></i></a></p></li><li><p><a href="#MAXDISKSIZE"><i><tt>max disk size</tt></i></a></p></li><li><p><a href="#MAXLOGSIZE"><i><tt>max log size</tt></i></a></p></li><li><p><a href="#MAXMUX"><i><tt>max mux</tt></i></a></p></li><li><p><a href="#MAXOPENFILES"><i><tt>max open files</tt></i></a></p></li><li><p><a href="#MAXPROTOCOL"><i><tt>max protocol</tt></i></a></p></li><li><p><a href="#MAXSMBDPROCESSES"><i><tt>max smbd processes</tt></i></a></p></li><li><p><a href="#MAXTTL"><i><tt>max ttl</tt></i></a></p></li><li><p><a href="#MAXWINSTTL"><i><tt>max wins ttl</tt></i></a></p></li><li><p><a href="#MAXXMIT"><i><tt>max xmit</tt></i></a></p></li><li><p><a href="#MESSAGECOMMAND"><i><tt>message command</tt></i></a></p></li><li><p><a href="#MINPASSWDLENGTH"><i><tt>min passwd length</tt></i></a></p></li><li><p><a href="#MINPASSWORDLENGTH"><i><tt>min password length</tt></i></a></p></li><li><p><a href="#MINPROTOCOL"><i><tt>min protocol</tt></i></a></p></li><li><p><a href="#MINWINSTTL"><i><tt>min wins ttl</tt></i></a></p></li><li><p><a href="#NAMECACHETIMEOUT"><i><tt>name cache timeout</tt></i></a></p></li><li><p><a href="#NAMERESOLVEORDER"><i><tt>name resolve order</tt></i></a></p></li><li><p><a href="#NETBIOSALIASES"><i><tt>netbios aliases</tt></i></a></p></li><li><p><a href="#NETBIOSNAME"><i><tt>netbios name</tt></i></a></p></li><li><p><a href="#NETBIOSSCOPE"><i><tt>netbios scope</tt></i></a></p></li><li><p><a href="#NISHOMEDIR"><i><tt>nis homedir</tt></i></a></p></li><li><p><a href="#NONUNIXACCOUNTRANGE"><i><tt>non unix account range</tt></i></a></p></li><li><p><a href="#NTLMAUTH"><i><tt>ntlm auth</tt></i></a></p></li><li><p><a href="#NTPIPESUPPORT"><i><tt>nt pipe support</tt></i></a></p></li><li><p><a href="#NTSTATUSSUPPORT"><i><tt>nt status support</tt></i></a></p></li><li><p><a href="#NULLPASSWORDS"><i><tt>null passwords</tt></i></a></p></li><li><p><a href="#OBEYPAMRESTRICTIONS"><i><tt>obey pam restrictions</tt></i></a></p></li><li><p><a href="#OPLOCKBREAKWAITTIME"><i><tt>oplock break wait time</tt></i></a></p></li><li><p><a href="#OS2DRIVERMAP"><i><tt>os2 driver map</tt></i></a></p></li><li><p><a href="#OSLEVEL"><i><tt>os level</tt></i></a></p></li><li><p><a href="#PAMPASSWORDCHANGE"><i><tt>pam password change</tt></i></a></p></li><li><p><a href="#PANICACTION"><i><tt>panic action</tt></i></a></p></li><li><p><a href="#PARANOIDSERVERSECURITY"><i><tt>paranoid server security</tt></i></a></p></li><li><p><a href="#PASSDBBACKEND"><i><tt>passdb backend</tt></i></a></p></li><li><p><a href="#PASSWDCHATDEBUG"><i><tt>passwd chat debug</tt></i></a></p></li><li><p><a href="#PASSWDCHAT"><i><tt>passwd chat</tt></i></a></p></li><li><p><a href="#PASSWDPROGRAM"><i><tt>passwd program</tt></i></a></p></li><li><p><a href="#PASSWORDLEVEL"><i><tt>password level</tt></i></a></p></li><li><p><a href="#PASSWORDSERVER"><i><tt>password server</tt></i></a></p></li><li><p><a href="#PIDDIRECTORY"><i><tt>pid directory</tt></i></a></p></li><li><p><a href="#PREFEREDMASTER"><i><tt>prefered master</tt></i></a></p></li><li><p><a href="#PREFERREDMASTER"><i><tt>preferred master</tt></i></a></p></li><li><p><a href="#PRELOADMODULES"><i><tt>preload modules</tt></i></a></p></li><li><p><a href="#PRELOAD"><i><tt>preload</tt></i></a></p></li><li><p><a href="#PRINTCAP"><i><tt>printcap</tt></i></a></p></li><li><p><a href="#PRIVATEDIR"><i><tt>private dir</tt></i></a></p></li><li><p><a href="#PROTOCOL"><i><tt>protocol</tt></i></a></p></li><li><p><a href="#READBMPX"><i><tt>read bmpx</tt></i></a></p></li><li><p><a href="#READRAW"><i><tt>read raw</tt></i></a></p></li><li><p><a href="#READSIZE"><i><tt>read size</tt></i></a></p></li><li><p><a href="#REALM"><i><tt>realm</tt></i></a></p></li><li><p><a href="#REMOTEANNOUNCE"><i><tt>remote announce</tt></i></a></p></li><li><p><a href="#REMOTEBROWSESYNC"><i><tt>remote browse sync</tt></i></a></p></li><li><p><a href="#RESTRICTANONYMOUS"><i><tt>restrict anonymous</tt></i></a></p></li><li><p><a href="#ROOTDIRECTORY"><i><tt>root directory</tt></i></a></p></li><li><p><a href="#ROOTDIR"><i><tt>root dir</tt></i></a></p></li><li><p><a href="#ROOT"><i><tt>root</tt></i></a></p></li><li><p><a href="#SECURITY"><i><tt>security</tt></i></a></p></li><li><p><a href="#SERVERSCHANNEL"><i><tt>server schannel</tt></i></a></p></li><li><p><a href="#SERVERSTRING"><i><tt>server string</tt></i></a></p></li><li><p><a href="#SETPRIMARYGROUPSCRIPT"><i><tt>set primary group script</tt></i></a></p></li><li><p><a href="#SHOWADDPRINTERWIZARD"><i><tt>show add printer wizard</tt></i></a></p></li><li><p><a href="#SHUTDOWNSCRIPT"><i><tt>shutdown script</tt></i></a></p></li><li><p><a href="#SMBPASSWDFILE"><i><tt>smb passwd file</tt></i></a></p></li><li><p><a href="#SMBPORTS"><i><tt>smb ports</tt></i></a></p></li><li><p><a href="#SOCKETADDRESS"><i><tt>socket address</tt></i></a></p></li><li><p><a href="#SOCKETOPTIONS"><i><tt>socket options</tt></i></a></p></li><li><p><a href="#SOURCEENVIRONMENT"><i><tt>source environment</tt></i></a></p></li><li><p><a href="#STATCACHESIZE"><i><tt>stat cache size</tt></i></a></p></li><li><p><a href="#STATCACHE"><i><tt>stat cache</tt></i></a></p></li><li><p><a href="#STRIPDOT"><i><tt>strip dot</tt></i></a></p></li><li><p><a href="#SYSLOGONLY"><i><tt>syslog only</tt></i></a></p></li><li><p><a href="#SYSLOG"><i><tt>syslog</tt></i></a></p></li><li><p><a href="#TEMPLATEHOMEDIR"><i><tt>template homedir</tt></i></a></p></li><li><p><a href="#TEMPLATESHELL"><i><tt>template shell</tt></i></a></p></li><li><p><a href="#TIMEOFFSET"><i><tt>time offset</tt></i></a></p></li><li><p><a href="#TIMESERVER"><i><tt>time server</tt></i></a></p></li><li><p><a href="#TIMESTAMPLOGS"><i><tt>timestamp logs</tt></i></a></p></li><li><p><a href="#TOTALPRINTJOBS"><i><tt>total print jobs</tt></i></a></p></li><li><p><a href="#UNICODE"><i><tt>unicode</tt></i></a></p></li><li><p><a href="#UNIXCHARSET"><i><tt>unix charset</tt></i></a></p></li><li><p><a href="#UNIXEXTENSIONS"><i><tt>unix extensions</tt></i></a></p></li><li><p><a href="#UNIXPASSWORDSYNC"><i><tt>unix password sync</tt></i></a></p></li><li><p><a href="#UPDATEENCRYPTED"><i><tt>update encrypted</tt></i></a></p></li><li><p><a href="#USEMMAP"><i><tt>use mmap</tt></i></a></p></li><li><p><a href="#USERNAMELEVEL"><i><tt>username level</tt></i></a></p></li><li><p><a href="#USERNAMEMAP"><i><tt>username map</tt></i></a></p></li><li><p><a href="#USESPNEGO"><i><tt>use spnego</tt></i></a></p></li><li><p><a href="#UTMPDIRECTORY"><i><tt>utmp directory</tt></i></a></p></li><li><p><a href="#UTMP"><i><tt>utmp</tt></i></a></p></li><li><p><a href="#WINBINDCACHETIME"><i><tt>winbind cache time</tt></i></a></p></li><li><p><a href="#WINBINDENUMGROUPS"><i><tt>winbind enum groups</tt></i></a></p></li><li><p><a href="#WINBINDENUMUSERS"><i><tt>winbind enum users</tt></i></a></p></li><li><p><a href="#WINBINDGID"><i><tt>winbind gid</tt></i></a></p></li><li><p><a href="#WINBINDSEPARATOR"><i><tt>winbind separator</tt></i></a></p></li><li><p><a href="#WINBINDUID"><i><tt>winbind uid</tt></i></a></p></li><li><p><a href="#WINBINDUSEDDEFAULTDOMAIN"><i><tt>winbind used default domain</tt></i></a></p></li><li><p><a href="#WINSHOOK"><i><tt>wins hook</tt></i></a></p></li><li><p><a href="#WINSPARTNER"><i><tt>wins partner</tt></i></a></p></li><li><p><a href="#WINSPROXY"><i><tt>wins proxy</tt></i></a></p></li><li><p><a href="#WINSSERVER"><i><tt>wins server</tt></i></a></p></li><li><p><a href="#WINSSUPPORT"><i><tt>wins support</tt></i></a></p></li><li><p><a href="#WORKGROUP"><i><tt>workgroup</tt></i></a></p></li><li><p><a href="#WRITERAW"><i><tt>write raw</tt></i></a></p></li><li><p><a href="#WTMPDIRECTORY"><i><tt>wtmp directory</tt></i></a></p></li></ul></div></div><div class="refsect1" lang="en"><h2>COMPLETE LIST OF SERVICE PARAMETERS</h2><p>Here is a list of all service parameters. See the section on
- each parameter for details. Note that some are synonyms.</p><div class="itemizedlist"><ul type="disc"><li><p><a href="#ADMINUSERS"><i><tt>admin users</tt></i></a></p></li><li><p><a href="#ALLOWHOSTS"><i><tt>allow hosts</tt></i></a></p></li><li><p><a href="#AVAILABLE"><i><tt>available</tt></i></a></p></li><li><p><a href="#BLOCKINGLOCKS"><i><tt>blocking locks</tt></i></a></p></li><li><p><a href="#BLOCKSIZE"><i><tt>block size</tt></i></a></p></li><li><p><a href="#BROWSABLE"><i><tt>browsable</tt></i></a></p></li><li><p><a href="#BROWSEABLE"><i><tt>browseable</tt></i></a></p></li><li><p><a href="#CASESENSITIVE"><i><tt>case sensitive</tt></i></a></p></li><li><p><a href="#CASESIGNAMES"><i><tt>casesignames</tt></i></a></p></li><li><p><a href="#COMMENT"><i><tt>comment</tt></i></a></p></li><li><p><a href="#COPY"><i><tt>copy</tt></i></a></p></li><li><p><a href="#CREATEMASK"><i><tt>create mask</tt></i></a></p></li><li><p><a href="#CREATEMODE"><i><tt>create mode</tt></i></a></p></li><li><p><a href="#CSCPOLICY"><i><tt>csc policy</tt></i></a></p></li><li><p><a href="#DEFAULTCASE"><i><tt>default case</tt></i></a></p></li><li><p><a href="#DEFAULTDEVMODE"><i><tt>default devmode</tt></i></a></p></li><li><p><a href="#DELETEREADONLY"><i><tt>delete readonly</tt></i></a></p></li><li><p><a href="#DELETEVETOFILES"><i><tt>delete veto files</tt></i></a></p></li><li><p><a href="#DENYHOSTS"><i><tt>deny hosts</tt></i></a></p></li><li><p><a href="#DIRECTORYMASK"><i><tt>directory mask</tt></i></a></p></li><li><p><a href="#DIRECTORYMODE"><i><tt>directory mode</tt></i></a></p></li><li><p><a href="#DIRECTORYSECURITYMASK"><i><tt>directory security mask</tt></i></a></p></li><li><p><a href="#DIRECTORY"><i><tt>directory</tt></i></a></p></li><li><p><a href="#DONTDESCEND"><i><tt>dont descend</tt></i></a></p></li><li><p><a href="#DOSFILEMODE"><i><tt>dos filemode</tt></i></a></p></li><li><p><a href="#DOSFILETIMERESOLUTION"><i><tt>dos filetime resolution</tt></i></a></p></li><li><p><a href="#DOSFILETIMES"><i><tt>dos filetimes</tt></i></a></p></li><li><p><a href="#EXEC"><i><tt>exec</tt></i></a></p></li><li><p><a href="#FAKEDIRECTORYCREATETIMES"><i><tt>fake directory create times</tt></i></a></p></li><li><p><a href="#FAKEOPLOCKS"><i><tt>fake oplocks</tt></i></a></p></li><li><p><a href="#FOLLOWSYMLINKS"><i><tt>follow symlinks</tt></i></a></p></li><li><p><a href="#FORCECREATEMODE"><i><tt>force create mode</tt></i></a></p></li><li><p><a href="#FORCEDIRECTORYMODE"><i><tt>force directory mode</tt></i></a></p></li><li><p><a href="#FORCEDIRECTORYSECURITYMODE"><i><tt>force directory security mode</tt></i></a></p></li><li><p><a href="#FORCEGROUP"><i><tt>force group</tt></i></a></p></li><li><p><a href="#FORCESECURITYMODE"><i><tt>force security mode</tt></i></a></p></li><li><p><a href="#FORCEUSER"><i><tt>force user</tt></i></a></p></li><li><p><a href="#FSTYPE"><i><tt>fstype</tt></i></a></p></li><li><p><a href="#GROUP"><i><tt>group</tt></i></a></p></li><li><p><a href="#GUESTACCOUNT"><i><tt>guest account</tt></i></a></p></li><li><p><a href="#GUESTOK"><i><tt>guest ok</tt></i></a></p></li><li><p><a href="#GUESTONLY"><i><tt>guest only</tt></i></a></p></li><li><p><a href="#HIDEDOTFILES"><i><tt>hide dot files</tt></i></a></p></li><li><p><a href="#HIDEFILES"><i><tt>hide files</tt></i></a></p></li><li><p><a href="#HIDESPECIALFILES"><i><tt>hide special files</tt></i></a></p></li><li><p><a href="#HIDEUNREADABLE"><i><tt>hide unreadable</tt></i></a></p></li><li><p><a href="#HIDEUNWRITEABLEFILES"><i><tt>hide unwriteable files</tt></i></a></p></li><li><p><a href="#HOSTSALLOW"><i><tt>hosts allow</tt></i></a></p></li><li><p><a href="#HOSTSDENY"><i><tt>hosts deny</tt></i></a></p></li><li><p><a href="#INHERITACLS"><i><tt>inherit acls</tt></i></a></p></li><li><p><a href="#INHERITPERMISSIONS"><i><tt>inherit permissions</tt></i></a></p></li><li><p><a href="#INVALIDUSERS"><i><tt>invalid users</tt></i></a></p></li><li><p><a href="#LEVEL2OPLOCKS"><i><tt>level2 oplocks</tt></i></a></p></li><li><p><a href="#LOCKING"><i><tt>locking</tt></i></a></p></li><li><p><a href="#LPPAUSECOMMAND"><i><tt>lppause command</tt></i></a></p></li><li><p><a href="#LPQCOMMAND"><i><tt>lpq command</tt></i></a></p></li><li><p><a href="#LPRESUMECOMMAND"><i><tt>lpresume command</tt></i></a></p></li><li><p><a href="#LPRMCOMMAND"><i><tt>lprm command</tt></i></a></p></li><li><p><a href="#MAGICOUTPUT"><i><tt>magic output</tt></i></a></p></li><li><p><a href="#MAGICSCRIPT"><i><tt>magic script</tt></i></a></p></li><li><p><a href="#MANGLECASE"><i><tt>mangle case</tt></i></a></p></li><li><p><a href="#MANGLEDMAP"><i><tt>mangled map</tt></i></a></p></li><li><p><a href="#MANGLEDNAMES"><i><tt>mangled names</tt></i></a></p></li><li><p><a href="#MANGLINGCHAR"><i><tt>mangling char</tt></i></a></p></li><li><p><a href="#MAPARCHIVE"><i><tt>map archive</tt></i></a></p></li><li><p><a href="#MAPHIDDEN"><i><tt>map hidden</tt></i></a></p></li><li><p><a href="#MAPSYSTEM"><i><tt>map system</tt></i></a></p></li><li><p><a href="#MAXCONNECTIONS"><i><tt>max connections</tt></i></a></p></li><li><p><a href="#MAXPRINTJOBS"><i><tt>max print jobs</tt></i></a></p></li><li><p><a href="#MINPRINTSPACE"><i><tt>min print space</tt></i></a></p></li><li><p><a href="#MSDFSPROXY"><i><tt>msdfs proxy</tt></i></a></p></li><li><p><a href="#MSDFSROOT"><i><tt>msdfs root</tt></i></a></p></li><li><p><a href="#NTACLSUPPORT"><i><tt>nt acl support</tt></i></a></p></li><li><p><a href="#ONLYGUEST"><i><tt>only guest</tt></i></a></p></li><li><p><a href="#ONLYUSER"><i><tt>only user</tt></i></a></p></li><li><p><a href="#OPLOCKCONTENTIONLIMIT"><i><tt>oplock contention limit</tt></i></a></p></li><li><p><a href="#OPLOCKS"><i><tt>oplocks</tt></i></a></p></li><li><p><a href="#PATH"><i><tt>path</tt></i></a></p></li><li><p><a href="#POSIXLOCKING"><i><tt>posix locking</tt></i></a></p></li><li><p><a href="#POSTEXEC"><i><tt>postexec</tt></i></a></p></li><li><p><a href="#PREEXECCLOSE"><i><tt>preexec close</tt></i></a></p></li><li><p><a href="#PREEXEC"><i><tt>preexec</tt></i></a></p></li><li><p><a href="#PRESERVECASE"><i><tt>preserve case</tt></i></a></p></li><li><p><a href="#PRINTABLE"><i><tt>printable</tt></i></a></p></li><li><p><a href="#PRINTCAPNAME"><i><tt>printcap name</tt></i></a></p></li><li><p><a href="#PRINTCOMMAND"><i><tt>print command</tt></i></a></p></li><li><p><a href="#PRINTERADMIN"><i><tt>printer admin</tt></i></a></p></li><li><p><a href="#PRINTERNAME"><i><tt>printer name</tt></i></a></p></li><li><p><a href="#PRINTER"><i><tt>printer</tt></i></a></p></li><li><p><a href="#PRINTING"><i><tt>printing</tt></i></a></p></li><li><p><a href="#PRINTOK"><i><tt>print ok</tt></i></a></p></li><li><p><a href="#PUBLIC"><i><tt>public</tt></i></a></p></li><li><p><a href="#QUEUEPAUSECOMMAND"><i><tt>queuepause command</tt></i></a></p></li><li><p><a href="#QUEUERESUMECOMMAND"><i><tt>queueresume command</tt></i></a></p></li><li><p><a href="#READLIST"><i><tt>read list</tt></i></a></p></li><li><p><a href="#READONLY"><i><tt>read only</tt></i></a></p></li><li><p><a href="#ROOTPOSTEXEC"><i><tt>root postexec</tt></i></a></p></li><li><p><a href="#ROOTPREEXECCLOSE"><i><tt>root preexec close</tt></i></a></p></li><li><p><a href="#ROOTPREEXEC"><i><tt>root preexec</tt></i></a></p></li><li><p><a href="#SECURITYMASK"><i><tt>security mask</tt></i></a></p></li><li><p><a href="#SETDIRECTORY"><i><tt>set directory</tt></i></a></p></li><li><p><a href="#SHAREMODES"><i><tt>share modes</tt></i></a></p></li><li><p><a href="#SHORTPRESERVECASE"><i><tt>short preserve case</tt></i></a></p></li><li><p><a href="#STRICTALLOCATE"><i><tt>strict allocate</tt></i></a></p></li><li><p><a href="#STRICTLOCKING"><i><tt>strict locking</tt></i></a></p></li><li><p><a href="#STRICTSYNC"><i><tt>strict sync</tt></i></a></p></li><li><p><a href="#SYNCALWAYS"><i><tt>sync always</tt></i></a></p></li><li><p><a href="#USECLIENTDRIVER"><i><tt>use client driver</tt></i></a></p></li><li><p><a href="#USERNAME"><i><tt>username</tt></i></a></p></li><li><p><a href="#USERS"><i><tt>users</tt></i></a></p></li><li><p><a href="#USER"><i><tt>user</tt></i></a></p></li><li><p><a href="#USESENDFILE"><i><tt>use sendfile</tt></i></a></p></li><li><p><a href="#VALIDUSERS"><i><tt>valid users</tt></i></a></p></li><li><p><a href="#VETOFILES"><i><tt>veto files</tt></i></a></p></li><li><p><a href="#VETOOPLOCKFILES"><i><tt>veto oplock files</tt></i></a></p></li><li><p><a href="#VFSOBJECT"><i><tt>vfs object</tt></i></a></p></li><li><p><a href="#VFSOPTIONS"><i><tt>vfs options</tt></i></a></p></li><li><p><a href="#VFSPATH"><i><tt>vfs path</tt></i></a></p></li><li><p><a href="#VOLUME"><i><tt>volume</tt></i></a></p></li><li><p><a href="#WIDELINKS"><i><tt>wide links</tt></i></a></p></li><li><p><a href="#WRITABLE"><i><tt>writable</tt></i></a></p></li><li><p><a href="#WRITEABLE"><i><tt>writeable</tt></i></a></p></li><li><p><a href="#WRITECACHESIZE"><i><tt>write cache size</tt></i></a></p></li><li><p><a href="#WRITELIST"><i><tt>write list</tt></i></a></p></li><li><p><a href="#WRITEOK"><i><tt>write ok</tt></i></a></p></li></ul></div></div><div class="refsect1" lang="en"><h2>EXPLANATION OF EACH PARAMETER</h2><div class="variablelist"><dl><dt><span class="term"><a name="ABORTSHUTDOWNSCRIPT"></a>abort shutdown script (G)</span></dt><dd><p><span class="emphasis"><em>This parameter only exists in the HEAD cvs branch</em></span>
- This a full path name to a script called by <a href="smbd.8.html">smbd(8)</a> that
- should stop a shutdown procedure issued by the <a href="#SHUTDOWNSCRIPT">
- <i><tt>shutdown script</tt></i></a>.</p><p>This command will be run as user.</p><p>Default: <span class="emphasis"><em>None</em></span>.</p><p>Example: <b>abort shutdown script = /sbin/shutdown -c</b></p></dd><dt><span class="term"><a name="ADDGROUPSCRIPT"></a>add group script (G)</span></dt><dd><p>This is the full pathname to a script that will be run
- <span class="emphasis"><em>AS ROOT</em></span> by <a href="smbd.8.html">smbd(8)</a>
- when a new group is requested. It will expand any <i><tt>%g</tt></i> to the group name passed. This
- script is only useful for installations using the Windows NT
- domain administration tools. The script is free to create a
- group with an arbitrary name to circumvent unix group name
- restrictions. In that case the script must print the numeric gid
- of the created group on stdout.</p></dd><dt><span class="term"><a name="ADDMACHINESCRIPT"></a>add machine script (G)</span></dt><dd><p>This is the full pathname to a script that will be run by
- <a href="smbd.8.html">smbd(8)</a> when a machine is added
- to it's domain using the administrator username and password
- method. </p><p>This option is only required when using sam back-ends tied
- to the Unix uid method of RID calculation such as smbpasswd.
- This option is only available in Samba 3.0.</p><p>Default: <b>add machine script = &lt;empty string&gt;</b></p><p>Example: <b>add machine script = /usr/sbin/adduser -n -g
- machines -c Machine -d /dev/null -s /bin/false %u</b></p></dd><dt><span class="term"><a name="ADDPRINTERCOMMAND"></a>addprinter command (G)</span></dt><dd><p>With the introduction of MS-RPC based printing
- support for Windows NT/2000 clients in Samba 2.2, The MS Add
- Printer Wizard (APW) icon is now also available in the
- &quot;Printers...&quot; folder displayed a share listing. The APW
- allows for printers to be add remotely to a Samba or Windows
- NT/2000 print server.</p><p>For a Samba host this means that the printer must be
- physically added to the underlying printing system. The <i><tt>add
- printer command</tt></i> defines a script to be run which
- will perform the necessary operations for adding the printer
- to the print system and to add the appropriate service definition
- to the <tt>smb.conf</tt> file in order that it can be
- shared by <a href="smbd.8.html">smbd(8)</a>.</p><p>The <i><tt>addprinter command</tt></i> is
- automatically invoked with the following parameter (in
- order):</p><div class="itemizedlist"><ul type="disc"><li><p><i><tt>printer name</tt></i></p></li><li><p><i><tt>share name</tt></i></p></li><li><p><i><tt>port name</tt></i></p></li><li><p><i><tt>driver name</tt></i></p></li><li><p><i><tt>location</tt></i></p></li><li><p><i><tt>Windows 9x driver location</tt></i></p></li></ul></div><p>All parameters are filled in from the PRINTER_INFO_2 structure sent
- by the Windows NT/2000 client with one exception. The &quot;Windows 9x
- driver location&quot; parameter is included for backwards compatibility
- only. The remaining fields in the structure are generated from answers
- to the APW questions.</p><p>Once the <i><tt>addprinter command</tt></i> has
- been executed, <b>smbd</b> will reparse the <tt>
- smb.conf</tt> to determine if the share defined by the APW
- exists. If the sharename is still invalid, then <b>smbd
- </b> will return an ACCESS_DENIED error to the client.</p><p>
- The &quot;add printer command&quot; program can output a single line of text,
- which Samba will set as the port the new printer is connected to.
- If this line isn't output, Samba won't reload its printer shares.
- </p><p>See also <a href="#DELETEPRINTERCOMMAND"><i><tt>
- deleteprinter command</tt></i></a>, <a href="#PRINTING">
- <i><tt>printing</tt></i></a>,
- <a href="#SHOWADDPRINTERWIZARD"><i><tt>show add
- printer wizard</tt></i></a></p><p>Default: <span class="emphasis"><em>none</em></span></p><p>Example: <b>addprinter command = /usr/bin/addprinter</b></p></dd><dt><span class="term"><a name="ADDSHARECOMMAND"></a>add share command (G)</span></dt><dd><p>Samba 2.2.0 introduced the ability to dynamically
- add and delete shares via the Windows NT 4.0 Server Manager. The
- <i><tt>add share command</tt></i> is used to define an
- external program or script which will add a new service definition
- to <tt>smb.conf</tt>. In order to successfully
- execute the <i><tt>add share command</tt></i>, <b>smbd</b>
- requires that the administrator be connected using a root account (i.e.
- uid == 0).
- </p><p>
- When executed, <b>smbd</b> will automatically invoke the
- <i><tt>add share command</tt></i> with four parameters.
- </p><div class="itemizedlist"><ul type="disc"><li><p><i><tt>configFile</tt></i> - the location
- of the global <tt>smb.conf</tt> file.
- </p></li><li><p><i><tt>shareName</tt></i> - the name of the new
+ the group of the same name.</P
+></LI
+><LI
+><P
+>If the service is a guest service then a
+ connection is made as the username given in the "guest
+ account =" for the service, irrespective of the
+ supplied password.</P
+></LI
+></OL
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN257"
+></A
+><H2
+>COMPLETE LIST OF GLOBAL PARAMETERS</H2
+><P
+>Here is a list of all global parameters. See the section of
+ each parameter for details. Note that some are synonyms.</P
+><P
+></P
+><UL
+><LI
+><P
+><A
+HREF="#ABORTSHUTDOWNSCRIPT"
+><TT
+CLASS="PARAMETER"
+><I
+>abort shutdown script</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#ADDGROUPSCRIPT"
+><TT
+CLASS="PARAMETER"
+><I
+>add group script</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#ADDPRINTERCOMMAND"
+><TT
+CLASS="PARAMETER"
+><I
+>addprinter command</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#ADDSHARECOMMAND"
+><TT
+CLASS="PARAMETER"
+><I
+>add share command</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#ADDUSERSCRIPT"
+><TT
+CLASS="PARAMETER"
+><I
+>add user script</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#ADDUSERTOGROUPSCRIPT"
+><TT
+CLASS="PARAMETER"
+><I
+>add user to group script</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#ADDMACHINESCRIPT"
+><TT
+CLASS="PARAMETER"
+><I
+>add machine script</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#DELETEGROUPSCRIPT"
+><TT
+CLASS="PARAMETER"
+><I
+>delete group script</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#ADSSERVER"
+><TT
+CLASS="PARAMETER"
+><I
+>ads server</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#ALGORITHMICRIDBASE"
+><TT
+CLASS="PARAMETER"
+><I
+>algorithmic rid base</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#ALLOWTRUSTEDDOMAINS"
+><TT
+CLASS="PARAMETER"
+><I
+>allow trusted domains</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#ANNOUNCEAS"
+><TT
+CLASS="PARAMETER"
+><I
+>announce as</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#ANNOUNCEVERSION"
+><TT
+CLASS="PARAMETER"
+><I
+>announce version</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#AUTHMETHODS"
+><TT
+CLASS="PARAMETER"
+><I
+>auth methods</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#AUTOSERVICES"
+><TT
+CLASS="PARAMETER"
+><I
+>auto services</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#BINDINTERFACESONLY"
+><TT
+CLASS="PARAMETER"
+><I
+>bind interfaces only</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#BROWSELIST"
+><TT
+CLASS="PARAMETER"
+><I
+>browse list</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#CHANGENOTIFYTIMEOUT"
+><TT
+CLASS="PARAMETER"
+><I
+>change notify timeout</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#CHANGESHARECOMMAND"
+><TT
+CLASS="PARAMETER"
+><I
+>change share command</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#CONFIGFILE"
+><TT
+CLASS="PARAMETER"
+><I
+>config file</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#DEADTIME"
+><TT
+CLASS="PARAMETER"
+><I
+>deadtime</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#DEBUGHIRESTIMESTAMP"
+><TT
+CLASS="PARAMETER"
+><I
+>debug hires timestamp</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#DEBUGPID"
+><TT
+CLASS="PARAMETER"
+><I
+>debug pid</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#DEBUGTIMESTAMP"
+><TT
+CLASS="PARAMETER"
+><I
+>debug timestamp</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#DEBUGUID"
+><TT
+CLASS="PARAMETER"
+><I
+>debug uid</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#DEBUGLEVEL"
+><TT
+CLASS="PARAMETER"
+><I
+>debuglevel</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#DEFAULT"
+><TT
+CLASS="PARAMETER"
+><I
+>default</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#DEFAULTSERVICE"
+><TT
+CLASS="PARAMETER"
+><I
+>default service</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#DELETEPRINTERCOMMAND"
+><TT
+CLASS="PARAMETER"
+><I
+>deleteprinter command</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#DELETESHARECOMMAND"
+><TT
+CLASS="PARAMETER"
+><I
+>delete share command</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#DELETEUSERSCRIPT"
+><TT
+CLASS="PARAMETER"
+><I
+>delete user script</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#DELETEUSERFROMGROUPSCRIPT"
+><TT
+CLASS="PARAMETER"
+><I
+>delete user from group script</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#DFREECOMMAND"
+><TT
+CLASS="PARAMETER"
+><I
+>dfree command</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#DISABLENETBIOS"
+><TT
+CLASS="PARAMETER"
+><I
+>disable netbios</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#DISABLESPOOLSS"
+><TT
+CLASS="PARAMETER"
+><I
+>disable spoolss</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#DISPLAYCHARSET"
+><TT
+CLASS="PARAMETER"
+><I
+>display charset</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#DNSPROXY"
+><TT
+CLASS="PARAMETER"
+><I
+>dns proxy</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#DOMAINLOGONS"
+><TT
+CLASS="PARAMETER"
+><I
+>domain logons</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#DOMAINMASTER"
+><TT
+CLASS="PARAMETER"
+><I
+>domain master</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#DOSCHARSET"
+><TT
+CLASS="PARAMETER"
+><I
+>dos charset</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#ENCRYPTPASSWORDS"
+><TT
+CLASS="PARAMETER"
+><I
+>encrypt passwords</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#ENHANCEDBROWSING"
+><TT
+CLASS="PARAMETER"
+><I
+>enhanced browsing</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#ENUMPORTSCOMMAND"
+><TT
+CLASS="PARAMETER"
+><I
+>enumports command</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#GETWDCACHE"
+><TT
+CLASS="PARAMETER"
+><I
+>getwd cache</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#HIDELOCALUSERS"
+><TT
+CLASS="PARAMETER"
+><I
+>hide local users</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#HIDEUNREADABLE"
+><TT
+CLASS="PARAMETER"
+><I
+>hide unreadable</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#HIDEUNWRITEABLEFILES"
+><TT
+CLASS="PARAMETER"
+><I
+>hide unwriteable files</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#HIDESPECIALFILES"
+><TT
+CLASS="PARAMETER"
+><I
+>hide special files</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#HOMEDIRMAP"
+><TT
+CLASS="PARAMETER"
+><I
+>homedir map</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#HOSTMSDFS"
+><TT
+CLASS="PARAMETER"
+><I
+>host msdfs</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#HOSTNAMELOOKUPS"
+><TT
+CLASS="PARAMETER"
+><I
+>hostname lookups</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#HOSTSEQUIV"
+><TT
+CLASS="PARAMETER"
+><I
+>hosts equiv</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#INTERFACES"
+><TT
+CLASS="PARAMETER"
+><I
+>interfaces</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#KEEPALIVE"
+><TT
+CLASS="PARAMETER"
+><I
+>keepalive</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#KERNELOPLOCKS"
+><TT
+CLASS="PARAMETER"
+><I
+>kernel oplocks</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#LANMANAUTH"
+><TT
+CLASS="PARAMETER"
+><I
+>lanman auth</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#LARGEREADWRITE"
+><TT
+CLASS="PARAMETER"
+><I
+>large readwrite</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#LDAPADMINDN"
+><TT
+CLASS="PARAMETER"
+><I
+>ldap admin dn</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#LDAPDELETEDN"
+><TT
+CLASS="PARAMETER"
+><I
+>ldap delete dn</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#LDAPDELONLYSAMATTR"
+><TT
+CLASS="PARAMETER"
+><I
+>ldap del only sam attr</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#LDAPFILTER"
+><TT
+CLASS="PARAMETER"
+><I
+>ldap filter</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#LDAPPORT"
+><TT
+CLASS="PARAMETER"
+><I
+>ldap port</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#LDAPSERVER"
+><TT
+CLASS="PARAMETER"
+><I
+>ldap server</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#LDAPSSL"
+><TT
+CLASS="PARAMETER"
+><I
+>ldap ssl</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#LDAPSUFFIX"
+><TT
+CLASS="PARAMETER"
+><I
+>ldap suffix</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#LDAPUSERSUFFIX"
+><TT
+CLASS="PARAMETER"
+><I
+>ldap user suffix</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#LDAPMACHINESUFFIX"
+><TT
+CLASS="PARAMETER"
+><I
+>ldap machine suffix</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#LDAPPASSWDSYNC"
+><TT
+CLASS="PARAMETER"
+><I
+>ldap passwd sync</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#LDAPTRUSTIDS"
+><TT
+CLASS="PARAMETER"
+><I
+>ldap trust ids</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#LMANNOUNCE"
+><TT
+CLASS="PARAMETER"
+><I
+>lm announce</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#LMINTERVAL"
+><TT
+CLASS="PARAMETER"
+><I
+>lm interval</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#LOADPRINTERS"
+><TT
+CLASS="PARAMETER"
+><I
+>load printers</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#LOCALMASTER"
+><TT
+CLASS="PARAMETER"
+><I
+>local master</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#LOCKDIR"
+><TT
+CLASS="PARAMETER"
+><I
+>lock dir</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#LOCKDIRECTORY"
+><TT
+CLASS="PARAMETER"
+><I
+>lock directory</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#LOCKSPINCOUNT"
+><TT
+CLASS="PARAMETER"
+><I
+>lock spin count</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#LOCKSPINTIME"
+><TT
+CLASS="PARAMETER"
+><I
+>lock spin time</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#PIDDIRECTORY"
+><TT
+CLASS="PARAMETER"
+><I
+>pid directory</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#LOGFILE"
+><TT
+CLASS="PARAMETER"
+><I
+>log file</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#LOGLEVEL"
+><TT
+CLASS="PARAMETER"
+><I
+>log level</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#LOGONDRIVE"
+><TT
+CLASS="PARAMETER"
+><I
+>logon drive</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#LOGONHOME"
+><TT
+CLASS="PARAMETER"
+><I
+>logon home</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#LOGONPATH"
+><TT
+CLASS="PARAMETER"
+><I
+>logon path</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#LOGONSCRIPT"
+><TT
+CLASS="PARAMETER"
+><I
+>logon script</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#LPQCACHETIME"
+><TT
+CLASS="PARAMETER"
+><I
+>lpq cache time</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#MACHINEPASSWORDTIMEOUT"
+><TT
+CLASS="PARAMETER"
+><I
+>machine password timeout</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#MANGLEDSTACK"
+><TT
+CLASS="PARAMETER"
+><I
+>mangled stack</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#MAPTOGUEST"
+><TT
+CLASS="PARAMETER"
+><I
+>map to guest</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#MAXDISKSIZE"
+><TT
+CLASS="PARAMETER"
+><I
+>max disk size</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#MAXLOGSIZE"
+><TT
+CLASS="PARAMETER"
+><I
+>max log size</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#MAXMUX"
+><TT
+CLASS="PARAMETER"
+><I
+>max mux</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#MAXOPENFILES"
+><TT
+CLASS="PARAMETER"
+><I
+>max open files</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#MAXPROTOCOL"
+><TT
+CLASS="PARAMETER"
+><I
+>max protocol</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#MAXSMBDPROCESSES"
+><TT
+CLASS="PARAMETER"
+><I
+>max smbd processes</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#MAXTTL"
+><TT
+CLASS="PARAMETER"
+><I
+>max ttl</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#MAXWINSTTL"
+><TT
+CLASS="PARAMETER"
+><I
+>max wins ttl</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#MAXXMIT"
+><TT
+CLASS="PARAMETER"
+><I
+>max xmit</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#MESSAGECOMMAND"
+><TT
+CLASS="PARAMETER"
+><I
+>message command</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#MINPASSWDLENGTH"
+><TT
+CLASS="PARAMETER"
+><I
+>min passwd length</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#MINPASSWORDLENGTH"
+><TT
+CLASS="PARAMETER"
+><I
+>min password length</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#MINPROTOCOL"
+><TT
+CLASS="PARAMETER"
+><I
+>min protocol</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#MINWINSTTL"
+><TT
+CLASS="PARAMETER"
+><I
+>min wins ttl</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#NAMECACHETIMEOUT"
+><TT
+CLASS="PARAMETER"
+><I
+>name cache timeout</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#NAMERESOLVEORDER"
+><TT
+CLASS="PARAMETER"
+><I
+>name resolve order</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#NETBIOSALIASES"
+><TT
+CLASS="PARAMETER"
+><I
+>netbios aliases</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#NETBIOSNAME"
+><TT
+CLASS="PARAMETER"
+><I
+>netbios name</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#NETBIOSSCOPE"
+><TT
+CLASS="PARAMETER"
+><I
+>netbios scope</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#NISHOMEDIR"
+><TT
+CLASS="PARAMETER"
+><I
+>nis homedir</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#NTLMAUTH"
+><TT
+CLASS="PARAMETER"
+><I
+>ntlm auth</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#NONUNIXACCOUNTRANGE"
+><TT
+CLASS="PARAMETER"
+><I
+>non unix account range</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#NTPIPESUPPORT"
+><TT
+CLASS="PARAMETER"
+><I
+>nt pipe support</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#NTSTATUSSUPPORT"
+><TT
+CLASS="PARAMETER"
+><I
+>nt status support</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#NULLPASSWORDS"
+><TT
+CLASS="PARAMETER"
+><I
+>null passwords</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#OBEYPAMRESTRICTIONS"
+><TT
+CLASS="PARAMETER"
+><I
+>obey pam restrictions</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#OPLOCKBREAKWAITTIME"
+><TT
+CLASS="PARAMETER"
+><I
+>oplock break wait time</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#OSLEVEL"
+><TT
+CLASS="PARAMETER"
+><I
+>os level</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#OS2DRIVERMAP"
+><TT
+CLASS="PARAMETER"
+><I
+>os2 driver map</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#PAMPASSWORDCHANGE"
+><TT
+CLASS="PARAMETER"
+><I
+>pam password change</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#PANICACTION"
+><TT
+CLASS="PARAMETER"
+><I
+>panic action</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#PARANOIDSERVERSECURITY"
+><TT
+CLASS="PARAMETER"
+><I
+>paranoid server security</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#PASSDBBACKEND"
+><TT
+CLASS="PARAMETER"
+><I
+>passdb backend</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#PASSWDCHAT"
+><TT
+CLASS="PARAMETER"
+><I
+>passwd chat</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#PASSWDCHATDEBUG"
+><TT
+CLASS="PARAMETER"
+><I
+>passwd chat debug</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#PASSWDPROGRAM"
+><TT
+CLASS="PARAMETER"
+><I
+>passwd program</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#PASSWORDLEVEL"
+><TT
+CLASS="PARAMETER"
+><I
+>password level</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#PASSWORDSERVER"
+><TT
+CLASS="PARAMETER"
+><I
+>password server</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#PREFEREDMASTER"
+><TT
+CLASS="PARAMETER"
+><I
+>prefered master</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#PREFERREDMASTER"
+><TT
+CLASS="PARAMETER"
+><I
+>preferred master</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#PRELOAD"
+><TT
+CLASS="PARAMETER"
+><I
+>preload</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#PRINTCAP"
+><TT
+CLASS="PARAMETER"
+><I
+>printcap</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#PRINTCAPNAME"
+><TT
+CLASS="PARAMETER"
+><I
+>printcap name</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#PRINTERDRIVERFILE"
+><TT
+CLASS="PARAMETER"
+><I
+>printer driver file</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#PRIVATEDIR"
+><TT
+CLASS="PARAMETER"
+><I
+>private dir</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#PROTOCOL"
+><TT
+CLASS="PARAMETER"
+><I
+>protocol</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#READBMPX"
+><TT
+CLASS="PARAMETER"
+><I
+>read bmpx</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#READRAW"
+><TT
+CLASS="PARAMETER"
+><I
+>read raw</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#READSIZE"
+><TT
+CLASS="PARAMETER"
+><I
+>read size</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#REALM"
+><TT
+CLASS="PARAMETER"
+><I
+>realm</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#REMOTEANNOUNCE"
+><TT
+CLASS="PARAMETER"
+><I
+>remote announce</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#REMOTEBROWSESYNC"
+><TT
+CLASS="PARAMETER"
+><I
+>remote browse sync</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#RESTRICTANONYMOUS"
+><TT
+CLASS="PARAMETER"
+><I
+>restrict anonymous</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#ROOT"
+><TT
+CLASS="PARAMETER"
+><I
+>root</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#ROOTDIR"
+><TT
+CLASS="PARAMETER"
+><I
+>root dir</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#ROOTDIRECTORY"
+><TT
+CLASS="PARAMETER"
+><I
+>root directory</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#SECURITY"
+><TT
+CLASS="PARAMETER"
+><I
+>security</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#SERVERSTRING"
+><TT
+CLASS="PARAMETER"
+><I
+>server string</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#SHOWADDPRINTERWIZARD"
+><TT
+CLASS="PARAMETER"
+><I
+>show add printer wizard</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#SHUTDOWNSCRIPT"
+><TT
+CLASS="PARAMETER"
+><I
+>shutdown script</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#SMBPASSWDFILE"
+><TT
+CLASS="PARAMETER"
+><I
+>smb passwd file</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#SMBPORTS"
+><TT
+CLASS="PARAMETER"
+><I
+>smb ports</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#SOCKETADDRESS"
+><TT
+CLASS="PARAMETER"
+><I
+>socket address</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#SOCKETOPTIONS"
+><TT
+CLASS="PARAMETER"
+><I
+>socket options</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#SOURCEENVIRONMENT"
+><TT
+CLASS="PARAMETER"
+><I
+>source environment</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#SPNEGO"
+><TT
+CLASS="PARAMETER"
+><I
+>use spnego</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#STATCACHE"
+><TT
+CLASS="PARAMETER"
+><I
+>stat cache</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#STATCACHESIZE"
+><TT
+CLASS="PARAMETER"
+><I
+>stat cache size</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#STRIPDOT"
+><TT
+CLASS="PARAMETER"
+><I
+>strip dot</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#SYSLOG"
+><TT
+CLASS="PARAMETER"
+><I
+>syslog</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#SYSLOGONLY"
+><TT
+CLASS="PARAMETER"
+><I
+>syslog only</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#TEMPLATEHOMEDIR"
+><TT
+CLASS="PARAMETER"
+><I
+>template homedir</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#TEMPLATESHELL"
+><TT
+CLASS="PARAMETER"
+><I
+>template shell</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#TIMEOFFSET"
+><TT
+CLASS="PARAMETER"
+><I
+>time offset</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#TIMESERVER"
+><TT
+CLASS="PARAMETER"
+><I
+>time server</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#TIMESTAMPLOGS"
+><TT
+CLASS="PARAMETER"
+><I
+>timestamp logs</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#TOTALPRINTJOBS"
+><TT
+CLASS="PARAMETER"
+><I
+>total print jobs</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#UNICODE"
+><TT
+CLASS="PARAMETER"
+><I
+>unicode</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#UNIXCHARSET"
+><TT
+CLASS="PARAMETER"
+><I
+>unix charset</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#UNIXEXTENSIONS"
+><TT
+CLASS="PARAMETER"
+><I
+>unix extensions</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#UNIXPASSWORDSYNC"
+><TT
+CLASS="PARAMETER"
+><I
+>unix password sync</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#UPDATEENCRYPTED"
+><TT
+CLASS="PARAMETER"
+><I
+>update encrypted</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#USEMMAP"
+><TT
+CLASS="PARAMETER"
+><I
+>use mmap</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#USERHOSTS"
+><TT
+CLASS="PARAMETER"
+><I
+>use rhosts</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#USESENDFILE"
+><TT
+CLASS="PARAMETER"
+><I
+>use sendfile</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#USERNAMELEVEL"
+><TT
+CLASS="PARAMETER"
+><I
+>username level</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#USERNAMEMAP"
+><TT
+CLASS="PARAMETER"
+><I
+>username map</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#UTMP"
+><TT
+CLASS="PARAMETER"
+><I
+>utmp</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#UTMPDIRECTORY"
+><TT
+CLASS="PARAMETER"
+><I
+>utmp directory</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#WTMPDIRECTORY"
+><TT
+CLASS="PARAMETER"
+><I
+>wtmp directory</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#WINBINDCACHETIME"
+><TT
+CLASS="PARAMETER"
+><I
+>winbind cache time</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#WINBINDENUMUSERS"
+><TT
+CLASS="PARAMETER"
+><I
+>winbind enum users</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#WINBINDENUMGROUPS"
+><TT
+CLASS="PARAMETER"
+><I
+>winbind enum groups</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#WINBINDGID"
+><TT
+CLASS="PARAMETER"
+><I
+>winbind gid</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#WINBINDSEPARATOR"
+><TT
+CLASS="PARAMETER"
+><I
+>winbind separator</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#WINBINDUID"
+><TT
+CLASS="PARAMETER"
+><I
+>winbind uid</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#WINBINDUSEDEFAULTDOMAIN"
+><TT
+CLASS="PARAMETER"
+><I
+>winbind use default domain</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#WINSHOOK"
+><TT
+CLASS="PARAMETER"
+><I
+>wins hook</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#WINSPARTNERS"
+><TT
+CLASS="PARAMETER"
+><I
+>wins partners</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#WINSPROXY"
+><TT
+CLASS="PARAMETER"
+><I
+>wins proxy</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#WINSSERVER"
+><TT
+CLASS="PARAMETER"
+><I
+>wins server</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#WINSSUPPORT"
+><TT
+CLASS="PARAMETER"
+><I
+>wins support</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#WORKGROUP"
+><TT
+CLASS="PARAMETER"
+><I
+>workgroup</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#WRITERAW"
+><TT
+CLASS="PARAMETER"
+><I
+>write raw</I
+></TT
+></A
+></P
+></LI
+></UL
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN1029"
+></A
+><H2
+>COMPLETE LIST OF SERVICE PARAMETERS</H2
+><P
+>Here is a list of all service parameters. See the section on
+ each parameter for details. Note that some are synonyms.</P
+><P
+></P
+><UL
+><LI
+><P
+><A
+HREF="#ADMINUSERS"
+><TT
+CLASS="PARAMETER"
+><I
+>admin users</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#ALLOWHOSTS"
+><TT
+CLASS="PARAMETER"
+><I
+>allow hosts</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#AVAILABLE"
+><TT
+CLASS="PARAMETER"
+><I
+>available</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#BLOCKINGLOCKS"
+><TT
+CLASS="PARAMETER"
+><I
+>blocking locks</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#BLOCKSIZE"
+><TT
+CLASS="PARAMETER"
+><I
+>block size</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#BROWSABLE"
+><TT
+CLASS="PARAMETER"
+><I
+>browsable</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#BROWSEABLE"
+><TT
+CLASS="PARAMETER"
+><I
+>browseable</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#CASESENSITIVE"
+><TT
+CLASS="PARAMETER"
+><I
+>case sensitive</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#CASESIGNAMES"
+><TT
+CLASS="PARAMETER"
+><I
+>casesignames</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#COMMENT"
+><TT
+CLASS="PARAMETER"
+><I
+>comment</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#COPY"
+><TT
+CLASS="PARAMETER"
+><I
+>copy</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#CREATEMASK"
+><TT
+CLASS="PARAMETER"
+><I
+>create mask</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#CREATEMODE"
+><TT
+CLASS="PARAMETER"
+><I
+>create mode</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#CSCPOLICY"
+><TT
+CLASS="PARAMETER"
+><I
+>csc policy</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#DEFAULTCASE"
+><TT
+CLASS="PARAMETER"
+><I
+>default case</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#DEFAULTDEVMODE"
+><TT
+CLASS="PARAMETER"
+><I
+>default devmode</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#DELETEREADONLY"
+><TT
+CLASS="PARAMETER"
+><I
+>delete readonly</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#DELETEVETOFILES"
+><TT
+CLASS="PARAMETER"
+><I
+>delete veto files</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#DENYHOSTS"
+><TT
+CLASS="PARAMETER"
+><I
+>deny hosts</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#DIRECTORY"
+><TT
+CLASS="PARAMETER"
+><I
+>directory</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#DIRECTORYMASK"
+><TT
+CLASS="PARAMETER"
+><I
+>directory mask</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#DIRECTORYMODE"
+><TT
+CLASS="PARAMETER"
+><I
+>directory mode</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#DIRECTORYSECURITYMASK"
+><TT
+CLASS="PARAMETER"
+><I
+>directory security mask</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#DONTDESCEND"
+><TT
+CLASS="PARAMETER"
+><I
+>dont descend</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#DOSFILEMODE"
+><TT
+CLASS="PARAMETER"
+><I
+>dos filemode</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#DOSFILETIMERESOLUTION"
+><TT
+CLASS="PARAMETER"
+><I
+>dos filetime resolution</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#DOSFILETIMES"
+><TT
+CLASS="PARAMETER"
+><I
+>dos filetimes</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#EXEC"
+><TT
+CLASS="PARAMETER"
+><I
+>exec</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#FAKEDIRECTORYCREATETIMES"
+><TT
+CLASS="PARAMETER"
+><I
+>fake directory create times</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#FAKEOPLOCKS"
+><TT
+CLASS="PARAMETER"
+><I
+>fake oplocks</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#FOLLOWSYMLINKS"
+><TT
+CLASS="PARAMETER"
+><I
+>follow symlinks</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#FORCECREATEMODE"
+><TT
+CLASS="PARAMETER"
+><I
+>force create mode</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#FORCEDIRECTORYMODE"
+><TT
+CLASS="PARAMETER"
+><I
+>force directory mode</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#FORCEDIRECTORYSECURITYMODE"
+><TT
+CLASS="PARAMETER"
+><I
+>force directory security mode</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#FORCEGROUP"
+><TT
+CLASS="PARAMETER"
+><I
+>force group</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#FORCESECURITYMODE"
+><TT
+CLASS="PARAMETER"
+><I
+>force security mode</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#FORCEUSER"
+><TT
+CLASS="PARAMETER"
+><I
+>force user</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#FSTYPE"
+><TT
+CLASS="PARAMETER"
+><I
+>fstype</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#GROUP"
+><TT
+CLASS="PARAMETER"
+><I
+>group</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#GUESTACCOUNT"
+><TT
+CLASS="PARAMETER"
+><I
+>guest account</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#GUESTOK"
+><TT
+CLASS="PARAMETER"
+><I
+>guest ok</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#GUESTONLY"
+><TT
+CLASS="PARAMETER"
+><I
+>guest only</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#HIDEDOTFILES"
+><TT
+CLASS="PARAMETER"
+><I
+>hide dot files</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#HIDEFILES"
+><TT
+CLASS="PARAMETER"
+><I
+>hide files</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#HOSTSALLOW"
+><TT
+CLASS="PARAMETER"
+><I
+>hosts allow</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#HOSTSDENY"
+><TT
+CLASS="PARAMETER"
+><I
+>hosts deny</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#INCLUDE"
+><TT
+CLASS="PARAMETER"
+><I
+>include</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#INHERITACLS"
+><TT
+CLASS="PARAMETER"
+><I
+>inherit acls</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#INHERITPERMISSIONS"
+><TT
+CLASS="PARAMETER"
+><I
+>inherit permissions</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#INVALIDUSERS"
+><TT
+CLASS="PARAMETER"
+><I
+>invalid users</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#LEVEL2OPLOCKS"
+><TT
+CLASS="PARAMETER"
+><I
+>level2 oplocks</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#LOCKING"
+><TT
+CLASS="PARAMETER"
+><I
+>locking</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#LPPAUSECOMMAND"
+><TT
+CLASS="PARAMETER"
+><I
+>lppause command</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#LPQCOMMAND"
+><TT
+CLASS="PARAMETER"
+><I
+>lpq command</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#LPRESUMECOMMAND"
+><TT
+CLASS="PARAMETER"
+><I
+>lpresume command</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#LPRMCOMMAND"
+><TT
+CLASS="PARAMETER"
+><I
+>lprm command</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#MAGICOUTPUT"
+><TT
+CLASS="PARAMETER"
+><I
+>magic output</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#MAGICSCRIPT"
+><TT
+CLASS="PARAMETER"
+><I
+>magic script</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#MANGLECASE"
+><TT
+CLASS="PARAMETER"
+><I
+>mangle case</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#MANGLEDMAP"
+><TT
+CLASS="PARAMETER"
+><I
+>mangled map</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#MANGLEDNAMES"
+><TT
+CLASS="PARAMETER"
+><I
+>mangled names</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#MANGLINGCHAR"
+><TT
+CLASS="PARAMETER"
+><I
+>mangling char</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#MANGLINGMETHOD"
+><TT
+CLASS="PARAMETER"
+><I
+>mangling method</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#MAPARCHIVE"
+><TT
+CLASS="PARAMETER"
+><I
+>map archive</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#MAPHIDDEN"
+><TT
+CLASS="PARAMETER"
+><I
+>map hidden</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#MAPSYSTEM"
+><TT
+CLASS="PARAMETER"
+><I
+>map system</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#MAXCONNECTIONS"
+><TT
+CLASS="PARAMETER"
+><I
+>max connections</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#MAXPRINTJOBS"
+><TT
+CLASS="PARAMETER"
+><I
+>max print jobs</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#MINPRINTSPACE"
+><TT
+CLASS="PARAMETER"
+><I
+>min print space</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#MSDFSPROXY"
+><TT
+CLASS="PARAMETER"
+><I
+>msdfs proxy</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#MSDFSROOT"
+><TT
+CLASS="PARAMETER"
+><I
+>msdfs root</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#NTACLSUPPORT"
+><TT
+CLASS="PARAMETER"
+><I
+>nt acl support</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#ONLYGUEST"
+><TT
+CLASS="PARAMETER"
+><I
+>only guest</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#ONLYUSER"
+><TT
+CLASS="PARAMETER"
+><I
+>only user</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#OPLOCKCONTENTIONLIMIT"
+><TT
+CLASS="PARAMETER"
+><I
+>oplock contention limit</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#OPLOCKS"
+><TT
+CLASS="PARAMETER"
+><I
+>oplocks</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#PATH"
+><TT
+CLASS="PARAMETER"
+><I
+>path</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#POSIXLOCKING"
+><TT
+CLASS="PARAMETER"
+><I
+>posix locking</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#POSTEXEC"
+><TT
+CLASS="PARAMETER"
+><I
+>postexec</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#POSTSCRIPT"
+><TT
+CLASS="PARAMETER"
+><I
+>postscript</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#PREEXEC"
+><TT
+CLASS="PARAMETER"
+><I
+>preexec</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#PREEXECCLOSE"
+><TT
+CLASS="PARAMETER"
+><I
+>preexec close</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#PRESERVECASE"
+><TT
+CLASS="PARAMETER"
+><I
+>preserve case</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#PRINTCOMMAND"
+><TT
+CLASS="PARAMETER"
+><I
+>print command</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#PRINTOK"
+><TT
+CLASS="PARAMETER"
+><I
+>print ok</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#PRINTABLE"
+><TT
+CLASS="PARAMETER"
+><I
+>printable</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#PRINTER"
+><TT
+CLASS="PARAMETER"
+><I
+>printer</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#PRINTERADMIN"
+><TT
+CLASS="PARAMETER"
+><I
+>printer admin</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#PRINTERDRIVER"
+><TT
+CLASS="PARAMETER"
+><I
+>printer driver</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#PRINTERDRIVERLOCATION"
+><TT
+CLASS="PARAMETER"
+><I
+>printer driver location</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#PRINTERNAME"
+><TT
+CLASS="PARAMETER"
+><I
+>printer name</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#PRINTING"
+><TT
+CLASS="PARAMETER"
+><I
+>printing</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#PUBLIC"
+><TT
+CLASS="PARAMETER"
+><I
+>public</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#QUEUEPAUSECOMMAND"
+><TT
+CLASS="PARAMETER"
+><I
+>queuepause command</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#QUEUERESUMECOMMAND"
+><TT
+CLASS="PARAMETER"
+><I
+>queueresume command</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#READLIST"
+><TT
+CLASS="PARAMETER"
+><I
+>read list</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#READONLY"
+><TT
+CLASS="PARAMETER"
+><I
+>read only</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#ROOTPOSTEXEC"
+><TT
+CLASS="PARAMETER"
+><I
+>root postexec</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#ROOTPREEXEC"
+><TT
+CLASS="PARAMETER"
+><I
+>root preexec</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#ROOTPREEXECCLOSE"
+><TT
+CLASS="PARAMETER"
+><I
+>root preexec close</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#SECURITYMASK"
+><TT
+CLASS="PARAMETER"
+><I
+>security mask</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#SETDIRECTORY"
+><TT
+CLASS="PARAMETER"
+><I
+>set directory</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#SHAREMODES"
+><TT
+CLASS="PARAMETER"
+><I
+>share modes</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#SHORTPRESERVECASE"
+><TT
+CLASS="PARAMETER"
+><I
+>short preserve case</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#STRICTALLOCATE"
+><TT
+CLASS="PARAMETER"
+><I
+>strict allocate</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#STRICTLOCKING"
+><TT
+CLASS="PARAMETER"
+><I
+>strict locking</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#STRICTSYNC"
+><TT
+CLASS="PARAMETER"
+><I
+>strict sync</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#SYNCALWAYS"
+><TT
+CLASS="PARAMETER"
+><I
+>sync always</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#USECLIENTDRIVER"
+><TT
+CLASS="PARAMETER"
+><I
+>use client driver</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#USER"
+><TT
+CLASS="PARAMETER"
+><I
+>user</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#USERNAME"
+><TT
+CLASS="PARAMETER"
+><I
+>username</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#USERS"
+><TT
+CLASS="PARAMETER"
+><I
+>users</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#VALIDUSERS"
+><TT
+CLASS="PARAMETER"
+><I
+>valid users</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#VETOFILES"
+><TT
+CLASS="PARAMETER"
+><I
+>veto files</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#VETOOPLOCKFILES"
+><TT
+CLASS="PARAMETER"
+><I
+>veto oplock files</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#VFSPATH"
+><TT
+CLASS="PARAMETER"
+><I
+>vfs path</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#VFSOBJECT"
+><TT
+CLASS="PARAMETER"
+><I
+>vfs object</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#VFSOPTIONS"
+><TT
+CLASS="PARAMETER"
+><I
+>vfs options</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#VOLUME"
+><TT
+CLASS="PARAMETER"
+><I
+>volume</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#WIDELINKS"
+><TT
+CLASS="PARAMETER"
+><I
+>wide links</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#WRITABLE"
+><TT
+CLASS="PARAMETER"
+><I
+>writable</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#WRITECACHESIZE"
+><TT
+CLASS="PARAMETER"
+><I
+>write cache size</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#WRITELIST"
+><TT
+CLASS="PARAMETER"
+><I
+>write list</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#WRITEOK"
+><TT
+CLASS="PARAMETER"
+><I
+>write ok</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="#WRITEABLE"
+><TT
+CLASS="PARAMETER"
+><I
+>writeable</I
+></TT
+></A
+></P
+></LI
+></UL
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN1533"
+></A
+><H2
+>EXPLANATION OF EACH PARAMETER</H2
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+><A
+NAME="ABORTSHUTDOWNSCRIPT"
+></A
+>abort shutdown script (G)</DT
+><DD
+><P
+><I
+CLASS="EMPHASIS"
+>This parameter only exists in the HEAD cvs branch</I
+>
+ This a full path name to a script called by
+ <A
+HREF="smbd.8.html"
+TARGET="_top"
+><B
+CLASS="COMMAND"
+>smbd(8)</B
+></A
+> that
+ should stop a shutdown procedure issued by the <A
+HREF="#SHUTDOWNSCRIPT"
+><TT
+CLASS="PARAMETER"
+><I
+>shutdown script</I
+></TT
+></A
+>.</P
+><P
+>This command will be run as user.</P
+><P
+>Default: <I
+CLASS="EMPHASIS"
+>None</I
+>.</P
+><P
+>Example: <B
+CLASS="COMMAND"
+>abort shutdown script = /sbin/shutdown -c</B
+></P
+></DD
+><DT
+><A
+NAME="ADDPRINTERCOMMAND"
+></A
+>addprinter command (G)</DT
+><DD
+><P
+>With the introduction of MS-RPC based printing
+ support for Windows NT/2000 clients in Samba 2.2, The MS Add
+ Printer Wizard (APW) icon is now also available in the
+ "Printers..." folder displayed a share listing. The APW
+ allows for printers to be add remotely to a Samba or Windows
+ NT/2000 print server.</P
+><P
+>For a Samba host this means that the printer must be
+ physically added to the underlying printing system. The <TT
+CLASS="PARAMETER"
+><I
+>add
+ printer command</I
+></TT
+> defines a script to be run which
+ will perform the necessary operations for adding the printer
+ to the print system and to add the appropriate service definition
+ to the <TT
+CLASS="FILENAME"
+>smb.conf</TT
+> file in order that it can be
+ shared by <A
+HREF="smbd.8.html"
+TARGET="_top"
+><B
+CLASS="COMMAND"
+>smbd(8)</B
+>
+ </A
+>.</P
+><P
+>The <TT
+CLASS="PARAMETER"
+><I
+>addprinter command</I
+></TT
+> is
+ automatically invoked with the following parameter (in
+ order:</P
+><P
+></P
+><UL
+><LI
+><P
+><TT
+CLASS="PARAMETER"
+><I
+>printer name</I
+></TT
+></P
+></LI
+><LI
+><P
+><TT
+CLASS="PARAMETER"
+><I
+>share name</I
+></TT
+></P
+></LI
+><LI
+><P
+><TT
+CLASS="PARAMETER"
+><I
+>port name</I
+></TT
+></P
+></LI
+><LI
+><P
+><TT
+CLASS="PARAMETER"
+><I
+>driver name</I
+></TT
+></P
+></LI
+><LI
+><P
+><TT
+CLASS="PARAMETER"
+><I
+>location</I
+></TT
+></P
+></LI
+><LI
+><P
+><TT
+CLASS="PARAMETER"
+><I
+>Windows 9x driver location</I
+></TT
+>
+ </P
+></LI
+></UL
+><P
+>All parameters are filled in from the PRINTER_INFO_2 structure sent
+ 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
+><P
+>Once the <TT
+CLASS="PARAMETER"
+><I
+>addprinter command</I
+></TT
+> has
+ been executed, <B
+CLASS="COMMAND"
+>smbd</B
+> will reparse the <TT
+CLASS="FILENAME"
+> smb.conf</TT
+> to determine if the share defined by the APW
+ exists. If the sharename is still invalid, then <B
+CLASS="COMMAND"
+>smbd
+ </B
+> will return an ACCESS_DENIED error to the client.</P
+><P
+>See also <A
+HREF="#DELETEPRINTERCOMMAND"
+><TT
+CLASS="PARAMETER"
+><I
+> deleteprinter command</I
+></TT
+></A
+>, <A
+HREF="#PRINTING"
+><TT
+CLASS="PARAMETER"
+><I
+>printing</I
+></TT
+></A
+>,
+ <A
+HREF="#SHOWADDPRINTERWIZARD"
+><TT
+CLASS="PARAMETER"
+><I
+>show add
+ printer wizard</I
+></TT
+></A
+></P
+><P
+>Default: <I
+CLASS="EMPHASIS"
+>none</I
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>addprinter command = /usr/bin/addprinter
+ </B
+></P
+></DD
+><DT
+><A
+NAME="ADDSHARECOMMAND"
+></A
+>add share command (G)</DT
+><DD
+><P
+>Samba 2.2.0 introduced the ability to dynamically
+ add and delete shares via the Windows NT 4.0 Server Manager. The
+ <TT
+CLASS="PARAMETER"
+><I
+>add share command</I
+></TT
+> is used to define an
+ external program or script which will add a new service definition
+ to <TT
+CLASS="FILENAME"
+>smb.conf</TT
+>. In order to successfully
+ execute the <TT
+CLASS="PARAMETER"
+><I
+>add share command</I
+></TT
+>, <B
+CLASS="COMMAND"
+>smbd</B
+>
+ requires that the administrator be connected using a root account (i.e.
+ uid == 0).
+ </P
+><P
+> When executed, <B
+CLASS="COMMAND"
+>smbd</B
+> will automatically invoke the
+ <TT
+CLASS="PARAMETER"
+><I
+>add share command</I
+></TT
+> with four parameters.
+ </P
+><P
+></P
+><UL
+><LI
+><P
+><TT
+CLASS="PARAMETER"
+><I
+>configFile</I
+></TT
+> - the location
+ of the global <TT
+CLASS="FILENAME"
+>smb.conf</TT
+> file.
+ </P
+></LI
+><LI
+><P
+><TT
+CLASS="PARAMETER"
+><I
+>shareName</I
+></TT
+> - the name of the new
share.
- </p></li><li><p><i><tt>pathName</tt></i> - path to an **existing**
+ </P
+></LI
+><LI
+><P
+><TT
+CLASS="PARAMETER"
+><I
+>pathName</I
+></TT
+> - path to an **existing**
directory on disk.
- </p></li><li><p><i><tt>comment</tt></i> - comment string to associate
+ </P
+></LI
+><LI
+><P
+><TT
+CLASS="PARAMETER"
+><I
+>comment</I
+></TT
+> - comment string to associate
with the new share.
- </p></li></ul></div><p>
- This parameter is only used for add file shares. To add printer shares,
- see the <a href="#ADDPRINTERCOMMAND"><i><tt>addprinter
- command</tt></i></a>.
- </p><p>
- See also <a href="#CHANGESHARECOMMAND"><i><tt>change share
- command</tt></i></a>, <a href="#DELETESHARECOMMAND"><i><tt>delete share
- command</tt></i></a>.
- </p><p>Default: <span class="emphasis"><em>none</em></span></p><p>Example: <b>add share command = /usr/local/bin/addshare</b></p></dd><dt><span class="term"><a name="ADDUSERSCRIPT"></a>add user script (G)</span></dt><dd><p>This is the full pathname to a script that will
- be run <span class="emphasis"><em>AS ROOT</em></span> by <a href="smbd.8.html">smbd(8)</a> 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
- that use Windows NT account databases as their primary user database
- creating these users and keeping the user list in sync with the
- Windows NT PDC is an onerous task. This option allows <a href="smbd.8.html" target="_top">smbd</a> to create the required UNIX users
- <span class="emphasis"><em>ON DEMAND</em></span> when a user accesses the Samba server.</p><p>In order to use this option, <a href="smbd.8.html">smbd(8)</a> must <span class="emphasis"><em>NOT</em></span> be set to <i><tt>security = share</tt></i>
- and <i><tt>add user script</tt></i>
- must be set to a full pathname for a script that will create a UNIX
- user given one argument of <i><tt>%u</tt></i>, which expands into
- the UNIX user name to create.</p><p>When the Windows user attempts to access the Samba server,
- at login (session setup in the SMB protocol) time, <a href="smbd.8.html">smbd(8)</a> contacts the <i><tt>password server</tt></i> and
- attempts to authenticate the given user with the given password. If the
- authentication succeeds then <b>smbd</b>
- attempts to find a UNIX user in the UNIX password database to map the
- Windows user into. If this lookup fails, and <i><tt>add user script
- </tt></i> is set then <b>smbd</b> will
- call the specified script <span class="emphasis"><em>AS ROOT</em></span>, expanding
- any <i><tt>%u</tt></i> argument to be the user name to create.</p><p>If this script successfully creates the user then <b>smbd
- </b> will continue on as though the UNIX user
- already existed. In this way, UNIX users are dynamically created to
- match existing Windows NT accounts.</p><p>See also <a href="#SECURITY"><i><tt>
- security</tt></i></a>, <a href="#PASSWORDSERVER">
- <i><tt>password server</tt></i></a>,
- <a href="#DELETEUSERSCRIPT"><i><tt>delete user
- script</tt></i></a>.</p><p>Default: <b>add user script = &lt;empty string&gt;</b></p><p>Example: <b>add user script = /usr/local/samba/bin/add_user %u</b></p></dd><dt><span class="term"><a name="ADDUSERTOGROUPSCRIPT"></a>add user to group script (G)</span></dt><dd><p>Full path to the script that will be called when
- a user is added to a group using the Windows NT domain administration
- tools. It will be run by <a href="smbd.8.html">smbd(8)</a> <span class="emphasis"><em>AS ROOT</em></span>.
- Any <i><tt>%g</tt></i> will be replaced with the group name and
- any <i><tt>%u</tt></i> will be replaced with the user name.
- </p><p>Default: <b>add user to group script = </b></p><p>Example: <b>add user to group script = /usr/sbin/adduser %u %g</b></p></dd><dt><span class="term"><a name="ADMINUSERS"></a>admin users (S)</span></dt><dd><p>This is a list of users who will be granted
- administrative privileges on the share. This means that they
- will do all file operations as the super-user (root).</p><p>You should use this option very carefully, as any user in
- this list will be able to do anything they like on the share,
- irrespective of file permissions.</p><p>Default: <span class="emphasis"><em>no admin users</em></span></p><p>Example: <b>admin users = jason</b></p></dd><dt><span class="term"><a name="ADSSERVER"></a>ads server (G)</span></dt><dd><p>If this option is specified, samba does not try to figure out what
- ads server to use itself, but uses the specified ads server. Either one
- DNS name or IP address can be used.</p><p>Default: <b>ads server = </b></p><p>Example: <b>ads server = 192.168.1.2</b></p></dd><dt><span class="term"><a name="ALGORITHMICRIDBASE"></a>algorithmic rid base (G)</span></dt><dd><p>This determines how Samba will use its
- algorithmic mapping from uids/gid to the RIDs needed to construct
- NT Security Identifiers.
- </p><p>Setting this option to a larger value could be useful to sites
- transitioning from WinNT and Win2k, as existing user and
- group rids would otherwise clash with sytem users etc.
- </p><p>All UIDs and GIDs must be able to be resolved into SIDs for
- the correct operation of ACLs on the server. As such the algorithmic
- mapping can't be 'turned off', but pushing it 'out of the way' should
- resolve the issues. Users and groups can then be assigned 'low' RIDs
- in arbitary-rid supporting backends.
- </p><p>Default: <b>algorithmic rid base = 1000</b></p><p>Example: <b>algorithmic rid base = 100000</b></p></dd><dt><span class="term"><a name="ALLOWHOSTS"></a>allow hosts (S)</span></dt><dd><p>Synonym for <a href="#HOSTSALLOW">
- <i><tt>hosts allow</tt></i></a>.</p></dd><dt><span class="term"><a name="ALLOWTRUSTEDDOMAINS"></a>allow trusted domains (G)</span></dt><dd><p>This option only takes effect when the <a href="#SECURITY">
- <i><tt>security</tt></i></a> option is set to
- <tt>server</tt> or <tt>domain</tt>.
- If it is set to no, then attempts to connect to a resource from
- a domain or workgroup other than the one which <a href="smbd.8.html" target="_top">smbd</a> is running
- in will fail, even if that domain is trusted by the remote server
- doing the authentication.</p><p>This is useful if you only want your Samba server to
- serve resources to users in the domain it is a member of. As
- an example, suppose that there are two domains DOMA and DOMB. DOMB
- is trusted by DOMA, which contains the Samba server. Under normal
- circumstances, a user with an account in DOMB can then access the
- resources of a UNIX account with the same account name on the
- Samba server even if they do not have an account in DOMA. This
- can make implementing a security boundary difficult.</p><p>Default: <b>allow trusted domains = yes</b></p></dd><dt><span class="term"><a name="ANNOUNCEAS"></a>announce as (G)</span></dt><dd><p>This specifies what type of server <a href="nmbd.8.html">nmbd(8)</a> will announce itself as, to a network neighborhood browse
- list. By default this is set to Windows NT. The valid options
- are : &quot;NT Server&quot; (which can also be written as &quot;NT&quot;),
- &quot;NT Workstation&quot;, &quot;Win95&quot; or &quot;WfW&quot; meaning Windows NT Server,
- Windows NT Workstation, Windows 95 and Windows for Workgroups
- respectively. Do not change this parameter unless you have a
- specific need to stop Samba appearing as an NT server as this
- may prevent Samba servers from participating as browser servers
- correctly.</p><p>Default: <b>announce as = NT Server</b></p><p>Example: <b>announce as = Win95</b></p></dd><dt><span class="term"><a name="ANNOUNCEVERSION"></a>announce version (G)</span></dt><dd><p>This specifies the major and minor version numbers
- that nmbd will use when announcing itself as a server. The default
- is 4.9. Do not change this parameter unless you have a specific
- need to set a Samba server to be a downlevel server.</p><p>Default: <b>announce version = 4.9</b></p><p>Example: <b>announce version = 2.0</b></p></dd><dt><span class="term"><a name="AUTHMETHODS"></a>auth methods (G)</span></dt><dd><p>This option allows the administrator to chose what
- authentication methods <b>smbd</b> will use when authenticating
- a user. This option defaults to sensible values based on <a href="#SECURITY">
- <i><tt>security</tt></i></a>.</p><p>Each entry in the list attempts to authenticate the user in turn, until
- the user authenticates. In practice only one method will ever actually
- be able to complete the authentication.
- </p><p>Default: <b>auth methods = &lt;empty string&gt;</b></p><p>Example: <b>auth methods = guest sam ntdomain</b></p></dd><dt><span class="term"><a name="AUTOSERVICES"></a>auto services (G)</span></dt><dd><p>This is a synonym for the <a href="#PRELOAD">
- <i><tt>preload</tt></i></a>.</p></dd><dt><span class="term"><a name="AVAILABLE"></a>available (S)</span></dt><dd><p>This parameter lets you &quot;turn off&quot; a service. If
- <i><tt>available = no</tt></i>, then <span class="emphasis"><em>ALL</em></span>
- attempts to connect to the service will fail. Such failures are
- logged.</p><p>Default: <b>available = yes</b></p></dd><dt><span class="term"><a name="BINDINTERFACESONLY"></a>bind interfaces only (G)</span></dt><dd><p>This global parameter allows the Samba admin
- to limit what interfaces on a machine will serve SMB requests. It
- affects file service <a href="smbd.8.html">smbd(8)</a> and name service <a href="nmbd.8.html">nmbd(8)</a> in a slightly different ways.</p><p>For name service it causes <b>nmbd</b> to bind
- to ports 137 and 138 on the interfaces listed in
- the <a href="#INTERFACES">interfaces</a> parameter. <b>nmbd</b> also
- binds to the &quot;all addresses&quot; interface (0.0.0.0)
- on ports 137 and 138 for the purposes of reading broadcast messages.
- If this option is not set then <b>nmbd</b> will service
- name requests on all of these sockets. If <i><tt>bind interfaces
- only</tt></i> is set then <b>nmbd</b> will check the
- source address of any packets coming in on the broadcast sockets
- and discard any that don't match the broadcast addresses of the
- interfaces in the <i><tt>interfaces</tt></i> parameter list.
- As unicast packets are received on the other sockets it allows
- <b>nmbd</b> to refuse to serve names to machines that
- send packets that arrive through any interfaces not listed in the
- <i><tt>interfaces</tt></i> list. IP Source address spoofing
- does defeat this simple check, however, so it must not be used
- seriously as a security feature for <b>nmbd</b>.</p><p>For file service it causes <a href="smbd.8.html">smbd(8)</a> to bind only to the interface list
- given in the <a href="#INTERFACES">interfaces</a> parameter. This
- restricts the networks that <b>smbd</b> will serve
- to packets coming in those interfaces. Note that you should not use this parameter
- for machines that are serving PPP or other intermittent or non-broadcast network
- interfaces as it will not cope with non-permanent interfaces.</p><p>If <i><tt>bind interfaces only</tt></i> is set then
- unless the network address <span class="emphasis"><em>127.0.0.1</em></span> is added
- to the <i><tt>interfaces</tt></i> parameter
- list <a href="smbpasswd.8.html">smbpasswd(8)</a> and <a href="swat.8.html">swat(8)</a> may not work as expected due
- to the reasons covered below.</p><p>To change a users SMB password, the <b>smbpasswd</b>
- by default connects to the <span class="emphasis"><em>localhost - 127.0.0.1</em></span>
- address as an SMB client to issue the password change request. If
- <i><tt>bind interfaces only</tt></i> is set then unless the
- network address <span class="emphasis"><em>127.0.0.1</em></span> is added to the
- <i><tt>interfaces</tt></i> parameter list then <b>
- smbpasswd</b> will fail to connect in it's default mode.
- <b>smbpasswd</b> can be forced to use the primary IP interface
- of the local host by using its <a href="smbpasswd.8.html">smbpasswd(8)</a> <i><tt>-r <i><tt>remote machine</tt></i></tt></i>
- parameter, with <i><tt>remote machine</tt></i> set
- to the IP name of the primary interface of the local host.</p><p>The <b>swat</b> status page tries to connect with
- <b>smbd</b> and <b>nmbd</b> at the address
- <span class="emphasis"><em>127.0.0.1</em></span> to determine if they are running.
- Not adding <span class="emphasis"><em>127.0.0.1</em></span> will cause <b>
- smbd</b> and <b>nmbd</b> to always show
- &quot;not running&quot; even if they really are. This can prevent <b>
- swat</b> from starting/stopping/restarting <b>smbd</b>
- and <b>nmbd</b>.</p><p>Default: <b>bind interfaces only = no</b></p></dd><dt><span class="term"><a name="BLOCKINGLOCKS"></a>blocking locks (S)</span></dt><dd><p>This parameter controls the behavior
- of <a href="smbd.8.html">smbd(8)</a> when given a request by a client
- to obtain a byte range lock on a region of an open file, and the
- request has a time limit associated with it.</p><p>If this parameter is set and the lock range requested
- cannot be immediately satisfied, samba will internally
- queue the lock request, and periodically attempt to obtain
- the lock until the timeout period expires.</p><p>If this parameter is set to <tt>no</tt>, then
- samba will behave as previous versions of Samba would and
- will fail the lock request immediately if the lock range
- cannot be obtained.</p><p>Default: <b>blocking locks = yes</b></p></dd><dt><span class="term"><a name="BLOCKSIZE"></a>block size (S)</span></dt><dd><p>This parameter controls the behavior of <a href="smbd.8.html">smbd(8)</a> when reporting disk free
- sizes. By default, this reports a disk block size of 1024 bytes.
- </p><p>Changing this parameter may have some effect on the
- efficiency of client writes, this is not yet confirmed. This
- parameter was added to allow advanced administrators to change
- it (usually to a higher value) and test the effect it has on
- client write performance without re-compiling the code. As this
- is an experimental option it may be removed in a future release.
- </p><p>Changing this option does not change the disk free reporting
- size, just the block size unit reported to the client.
- </p></dd><dt><span class="term"><a name="BROWSABLE"></a>browsable (S)</span></dt><dd><p>See the <a href="#BROWSEABLE">
- <i><tt>browseable</tt></i></a>.</p></dd><dt><span class="term"><a name="BROWSEABLE"></a>browseable (S)</span></dt><dd><p>This controls whether this share is seen in
- the list of available shares in a net view and in the browse list.</p><p>Default: <b>browseable = yes</b></p></dd><dt><span class="term"><a name="BROWSELIST"></a>browse list (G)</span></dt><dd><p>This controls whether <a href="smbd.8.html">smbd(8)</a> will serve a browse list to
- a client doing a <b>NetServerEnum</b> call. Normally
- set to <tt>yes</tt>. You should never need to change
- this.</p><p>Default: <b>browse list = yes</b></p></dd><dt><span class="term"><a name="CASESENSITIVE"></a>case sensitive (S)</span></dt><dd><p>See the discussion in the section <a href="#NAMEMANGLINGSECT" title="NAME MANGLING">NAME MANGLING</a>.</p><p>Default: <b>case sensitive = no</b></p></dd><dt><span class="term"><a name="CASESIGNAMES"></a>casesignames (S)</span></dt><dd><p>Synonym for <a href="#CASESENSITIVE">case sensitive</a>.</p></dd><dt><span class="term"><a name="CHANGENOTIFYTIMEOUT"></a>change notify timeout (G)</span></dt><dd><p>This SMB allows a client to tell a server to
- &quot;watch&quot; a particular directory for any changes and only reply to
- the SMB request when a change has occurred. Such constant scanning of
- a directory is expensive under UNIX, hence an <a href="smbd.8.html">smbd(8)</a> daemon only performs such a scan
- on each requested directory once every <i><tt>change notify
- timeout</tt></i> seconds.</p><p>Default: <b>change notify timeout = 60</b></p><p>Example: <b>change notify timeout = 300</b></p><p>Would change the scan time to every 5 minutes.</p></dd><dt><span class="term"><a name="CHANGESHARECOMMAND"></a>change share command (G)</span></dt><dd><p>Samba 2.2.0 introduced the ability to dynamically
- add and delete shares via the Windows NT 4.0 Server Manager. The
- <i><tt>change share command</tt></i> is used to define an
- external program or script which will modify an existing service definition
- in <tt>smb.conf</tt>. In order to successfully
- execute the <i><tt>change share command</tt></i>, <b>smbd</b>
- requires that the administrator be connected using a root account (i.e.
- uid == 0).
- </p><p>
- When executed, <b>smbd</b> will automatically invoke the
- <i><tt>change share command</tt></i> with four parameters.
- </p><div class="itemizedlist"><ul type="disc"><li><p><i><tt>configFile</tt></i> - the location
- of the global <tt>smb.conf</tt> file.
- </p></li><li><p><i><tt>shareName</tt></i> - the name of the new
+ </P
+></LI
+></UL
+><P
+> This parameter is only used for add file shares. To add printer shares,
+ see the <A
+HREF="#ADDPRINTERCOMMAND"
+><TT
+CLASS="PARAMETER"
+><I
+>addprinter
+ command</I
+></TT
+></A
+>.
+ </P
+><P
+> See also <A
+HREF="#CHANGESHARECOMMAND"
+><TT
+CLASS="PARAMETER"
+><I
+>change share
+ command</I
+></TT
+></A
+>, <A
+HREF="#DELETESHARECOMMAND"
+><TT
+CLASS="PARAMETER"
+><I
+>delete share
+ command</I
+></TT
+></A
+>.
+ </P
+><P
+>Default: <I
+CLASS="EMPHASIS"
+>none</I
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>add share command = /usr/local/bin/addshare</B
+></P
+></DD
+><DT
+><A
+NAME="ADDMACHINESCRIPT"
+></A
+>add machine script (G)</DT
+><DD
+><P
+>This is the full pathname to a script that will
+ be run by <A
+HREF="smbd.8.html"
+TARGET="_top"
+>smbd(8)</A
+> when a machine is added
+ to it's domain using the administrator username and password method. </P
+><P
+>This option is only required when using sam back-ends tied to the
+ Unix uid method of RID calculation such as smbpasswd. This option is only
+ available in Samba 3.0.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>add machine script = &#60;empty string&#62;
+ </B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>add machine script = /usr/sbin/adduser -n -g machines -c Machine -d /dev/null -s /bin/false %u
+ </B
+></P
+></DD
+><DT
+><A
+NAME="ADSSERVER"
+></A
+>ads server (G)</DT
+><DD
+><P
+>If this option is specified, samba does
+ not try to figure out what ads server to use itself, but
+ uses the specified ads server. Either one DNS name or IP
+ address can be used.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>ads server = </B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>ads server = 192.168.1.2</B
+></P
+></DD
+><DT
+><A
+NAME="ADDUSERSCRIPT"
+></A
+>add user script (G)</DT
+><DD
+><P
+>This is the full pathname to a script that will
+ be run <I
+CLASS="EMPHASIS"
+>AS ROOT</I
+> by <A
+HREF="smbd.8.html"
+TARGET="_top"
+>smbd(8)
+ </A
+> 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
+ that use Windows NT account databases as their primary user database
+ creating these users and keeping the user list in sync with the
+ Windows NT PDC is an onerous task. This option allows <A
+HREF="smbd.8.html"
+TARGET="_top"
+>smbd</A
+> to create the required UNIX users
+ <I
+CLASS="EMPHASIS"
+>ON DEMAND</I
+> when a user accesses the Samba server.</P
+><P
+>In order to use this option, <A
+HREF="smbd.8.html"
+TARGET="_top"
+>smbd</A
+>
+ must <I
+CLASS="EMPHASIS"
+>NOT</I
+> be set to <TT
+CLASS="PARAMETER"
+><I
+>security = share</I
+></TT
+>
+ and <TT
+CLASS="PARAMETER"
+><I
+>add user script</I
+></TT
+>
+ must be set to a full pathname for a script that will create a UNIX
+ user given one argument of <TT
+CLASS="PARAMETER"
+><I
+>%u</I
+></TT
+>, which expands into
+ the UNIX user name to create.</P
+><P
+>When the Windows user attempts to access the Samba server,
+ at login (session setup in the SMB protocol) time, <A
+HREF="smbd.8.html"
+TARGET="_top"
+> smbd</A
+> contacts the <TT
+CLASS="PARAMETER"
+><I
+>password server</I
+></TT
+> and
+ attempts to authenticate the given user with the given password. If the
+ authentication succeeds then <B
+CLASS="COMMAND"
+>smbd</B
+>
+ attempts to find a UNIX user in the UNIX password database to map the
+ Windows user into. If this lookup fails, and <TT
+CLASS="PARAMETER"
+><I
+>add user script
+ </I
+></TT
+> is set then <B
+CLASS="COMMAND"
+>smbd</B
+> will
+ call the specified script <I
+CLASS="EMPHASIS"
+>AS ROOT</I
+>, expanding
+ any <TT
+CLASS="PARAMETER"
+><I
+>%u</I
+></TT
+> argument to be the user name to create.</P
+><P
+>If this script successfully creates the user then <B
+CLASS="COMMAND"
+>smbd
+ </B
+> will continue on as though the UNIX user
+ already existed. In this way, UNIX users are dynamically created to
+ match existing Windows NT accounts.</P
+><P
+>See also <A
+HREF="#SECURITY"
+><TT
+CLASS="PARAMETER"
+><I
+> security</I
+></TT
+></A
+>, <A
+HREF="#PASSWORDSERVER"
+> <TT
+CLASS="PARAMETER"
+><I
+>password server</I
+></TT
+></A
+>,
+ <A
+HREF="#DELETEUSERSCRIPT"
+><TT
+CLASS="PARAMETER"
+><I
+>delete user
+ script</I
+></TT
+></A
+>.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>add user script = &#60;empty string&#62;
+ </B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>add user script = /usr/local/samba/bin/add_user
+ %u</B
+></P
+></DD
+><DT
+><A
+NAME="ADDGROUPSCRIPT"
+></A
+>add group script (G)</DT
+><DD
+><P
+>This is the full pathname to a script that will
+ be run <I
+CLASS="EMPHASIS"
+>AS ROOT</I
+> by <A
+HREF="smbd.8.html"
+TARGET="_top"
+>smbd(8)</A
+> when a new group is
+ requested. It will expand any
+ <TT
+CLASS="PARAMETER"
+><I
+>%g</I
+></TT
+> to the group name passed.
+ This script is only useful for installations using the
+ Windows NT domain administration tools. The script is
+ free to create a group with an arbitrary name to
+ circumvent unix group name restrictions. In that case
+ the script must print the numeric gid of the created
+ group on stdout.
+ </P
+></DD
+><DT
+><A
+NAME="ADMINUSERS"
+></A
+>admin users (S)</DT
+><DD
+><P
+>This is a list of users who will be granted
+ administrative privileges on the share. This means that they
+ will do all file operations as the super-user (root).</P
+><P
+>You should use this option very carefully, as any user in
+ this list will be able to do anything they like on the share,
+ irrespective of file permissions.</P
+><P
+>Default: <I
+CLASS="EMPHASIS"
+>no admin users</I
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>admin users = jason</B
+></P
+></DD
+><DT
+><A
+NAME="ADDUSERTOGROUPSCRIPT"
+></A
+>add user to group script (G)</DT
+><DD
+><P
+>Full path to the script that will be called when
+ a user is added to a group using the Windows NT domain administration
+ tools. It will be run by <A
+HREF="smbd.8.html"
+TARGET="_top"
+>smbd(8)</A
+>
+ <I
+CLASS="EMPHASIS"
+>AS ROOT</I
+>. Any <TT
+CLASS="PARAMETER"
+><I
+>%g</I
+></TT
+> will be
+ replaced with the group name and any <TT
+CLASS="PARAMETER"
+><I
+>%u</I
+></TT
+> will
+ be replaced with the user name.
+ </P
+><P
+>Default: <B
+CLASS="COMMAND"
+>add user to group script = </B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>add user to group script = /usr/sbin/adduser %u %g</B
+></P
+></DD
+><DT
+><A
+NAME="ALLOWHOSTS"
+></A
+>allow hosts (S)</DT
+><DD
+><P
+>Synonym for <A
+HREF="#HOSTSALLOW"
+> <TT
+CLASS="PARAMETER"
+><I
+>hosts allow</I
+></TT
+></A
+>.</P
+></DD
+><DT
+><A
+NAME="ALGORITHMICRIDBASE"
+></A
+>algorithmic rid base (G)</DT
+><DD
+><P
+>This determines how Samba will use its
+ algorithmic mapping from uids/gid to the RIDs needed to construct
+ NT Security Identifiers.</P
+><P
+>Setting this option to a larger value could be useful to sites
+ transitioning from WinNT and Win2k, as existing user and
+ group rids would otherwise clash with sytem users etc.
+ </P
+><P
+>All UIDs and GIDs must be able to be resolved into SIDs for
+ the correct operation of ACLs on the server. As such the algorithmic
+ mapping can't be 'turned off', but pushing it 'out of the way' should
+ resolve the issues. Users and groups can then be assigned 'low' RIDs
+ in arbitary-rid supporting backends. </P
+><P
+>Default: <B
+CLASS="COMMAND"
+>algorithmic rid base = 1000</B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>algorithmic rid base = 100000</B
+></P
+></DD
+><DT
+><A
+NAME="ALLOWTRUSTEDDOMAINS"
+></A
+>allow trusted domains (G)</DT
+><DD
+><P
+>This option only takes effect when the <A
+HREF="#SECURITY"
+><TT
+CLASS="PARAMETER"
+><I
+>security</I
+></TT
+></A
+> option is set to
+ <TT
+CLASS="CONSTANT"
+>server</TT
+> or <TT
+CLASS="CONSTANT"
+>domain</TT
+>.
+ If it is set to no, then attempts to connect to a resource from
+ a domain or workgroup other than the one which <A
+HREF="smbd.8.html"
+TARGET="_top"
+>smbd</A
+> is running
+ in will fail, even if that domain is trusted by the remote server
+ doing the authentication.</P
+><P
+>This is useful if you only want your Samba server to
+ serve resources to users in the domain it is a member of. As
+ an example, suppose that there are two domains DOMA and DOMB. DOMB
+ is trusted by DOMA, which contains the Samba server. Under normal
+ circumstances, a user with an account in DOMB can then access the
+ resources of a UNIX account with the same account name on the
+ Samba server even if they do not have an account in DOMA. This
+ can make implementing a security boundary difficult.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>allow trusted domains = yes</B
+></P
+></DD
+><DT
+><A
+NAME="ANNOUNCEAS"
+></A
+>announce as (G)</DT
+><DD
+><P
+>This specifies what type of server
+ <A
+HREF="nmbd.8.html"
+TARGET="_top"
+><B
+CLASS="COMMAND"
+>nmbd</B
+></A
+>
+ will announce itself as, to a network neighborhood browse
+ list. By default this is set to Windows NT. The valid options
+ 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
+ specific need to stop Samba appearing as an NT server as this
+ may prevent Samba servers from participating as browser servers
+ correctly.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>announce as = NT Server</B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>announce as = Win95</B
+></P
+></DD
+><DT
+><A
+NAME="ANNOUNCEVERSION"
+></A
+>announce version (G)</DT
+><DD
+><P
+>This specifies the major and minor version numbers
+ that nmbd will use when announcing itself as a server. The default
+ is 4.9. Do not change this parameter unless you have a specific
+ need to set a Samba server to be a downlevel server.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>announce version = 4.9</B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>announce version = 2.0</B
+></P
+></DD
+><DT
+><A
+NAME="AUTOSERVICES"
+></A
+>auto services (G)</DT
+><DD
+><P
+>This is a synonym for the <A
+HREF="#PRELOAD"
+> <TT
+CLASS="PARAMETER"
+><I
+>preload</I
+></TT
+></A
+>.</P
+></DD
+><DT
+><A
+NAME="AUTHMETHODS"
+></A
+>auth methods (G)</DT
+><DD
+><P
+>This option allows the administrator to chose what
+ authentication methods <B
+CLASS="COMMAND"
+>smbd</B
+> will use when authenticating
+ a user. This option defaults to sensible values based on <A
+HREF="#SECURITY"
+><TT
+CLASS="PARAMETER"
+><I
+> security</I
+></TT
+></A
+>.
+
+ Each entry in the list attempts to authenticate the user in turn, until
+ the user authenticates. In practice only one method will ever actually
+ be able to complete the authentication.
+ </P
+><P
+>Default: <B
+CLASS="COMMAND"
+>auth methods = &#60;empty string&#62;</B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>auth methods = guest sam ntdomain</B
+></P
+></DD
+><DT
+><A
+NAME="AVAILABLE"
+></A
+>available (S)</DT
+><DD
+><P
+>This parameter lets you "turn off" a service. If
+ <TT
+CLASS="PARAMETER"
+><I
+>available = no</I
+></TT
+>, then <I
+CLASS="EMPHASIS"
+>ALL</I
+>
+ attempts to connect to the service will fail. Such failures are
+ logged.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>available = yes</B
+></P
+></DD
+><DT
+><A
+NAME="BINDINTERFACESONLY"
+></A
+>bind interfaces only (G)</DT
+><DD
+><P
+>This global parameter allows the Samba admin
+ to limit what interfaces on a machine will serve SMB requests. It
+ affects file service <A
+HREF="smbd.8.html"
+TARGET="_top"
+>smbd(8)</A
+> and
+ name service <A
+HREF="nmbd.8.html"
+TARGET="_top"
+>nmbd(8)</A
+> in slightly
+ different ways.</P
+><P
+>For name service it causes <B
+CLASS="COMMAND"
+>nmbd</B
+> to bind
+ to ports 137 and 138 on the interfaces listed in the <A
+HREF="#INTERFACES"
+>interfaces</A
+> parameter. <B
+CLASS="COMMAND"
+>nmbd
+ </B
+> also binds to the "all addresses" interface (0.0.0.0)
+ on ports 137 and 138 for the purposes of reading broadcast messages.
+ If this option is not set then <B
+CLASS="COMMAND"
+>nmbd</B
+> will service
+ name requests on all of these sockets. If <TT
+CLASS="PARAMETER"
+><I
+>bind interfaces
+ only</I
+></TT
+> is set then <B
+CLASS="COMMAND"
+>nmbd</B
+> will check the
+ source address of any packets coming in on the broadcast sockets
+ and discard any that don't match the broadcast addresses of the
+ interfaces in the <TT
+CLASS="PARAMETER"
+><I
+>interfaces</I
+></TT
+> parameter list.
+ As unicast packets are received on the other sockets it allows
+ <B
+CLASS="COMMAND"
+>nmbd</B
+> to refuse to serve names to machines that
+ send packets that arrive through any interfaces not listed in the
+ <TT
+CLASS="PARAMETER"
+><I
+>interfaces</I
+></TT
+> list. IP Source address spoofing
+ does defeat this simple check, however, so it must not be used
+ seriously as a security feature for <B
+CLASS="COMMAND"
+>nmbd</B
+>.</P
+><P
+>For file service it causes <A
+HREF="smbd.8.html"
+TARGET="_top"
+>smbd(8)</A
+>
+ to bind only to the interface list given in the <A
+HREF="#INTERFACES"
+> interfaces</A
+> parameter. This restricts the networks that
+ <B
+CLASS="COMMAND"
+>smbd</B
+> will serve to packets coming in those
+ interfaces. Note that you should not use this parameter for machines
+ that are serving PPP or other intermittent or non-broadcast network
+ interfaces as it will not cope with non-permanent interfaces.</P
+><P
+>If <TT
+CLASS="PARAMETER"
+><I
+>bind interfaces only</I
+></TT
+> is set then
+ unless the network address <I
+CLASS="EMPHASIS"
+>127.0.0.1</I
+> is added
+ to the <TT
+CLASS="PARAMETER"
+><I
+>interfaces</I
+></TT
+> parameter list <A
+HREF="smbpasswd.8.html"
+TARGET="_top"
+><B
+CLASS="COMMAND"
+>smbpasswd(8)</B
+></A
+>
+ and <A
+HREF="swat.8.html"
+TARGET="_top"
+><B
+CLASS="COMMAND"
+>swat(8)</B
+></A
+> may
+ not work as expected due to the reasons covered below.</P
+><P
+>To change a users SMB password, the <B
+CLASS="COMMAND"
+>smbpasswd</B
+>
+ by default connects to the <I
+CLASS="EMPHASIS"
+>localhost - 127.0.0.1</I
+>
+ address as an SMB client to issue the password change request. If
+ <TT
+CLASS="PARAMETER"
+><I
+>bind interfaces only</I
+></TT
+> is set then unless the
+ network address <I
+CLASS="EMPHASIS"
+>127.0.0.1</I
+> is added to the
+ <TT
+CLASS="PARAMETER"
+><I
+>interfaces</I
+></TT
+> parameter list then <B
+CLASS="COMMAND"
+> smbpasswd</B
+> will fail to connect in it's default mode.
+ <B
+CLASS="COMMAND"
+>smbpasswd</B
+> can be forced to use the primary IP interface
+ of the local host by using its <A
+HREF="smbpasswd.8.html#minusr"
+TARGET="_top"
+> <TT
+CLASS="PARAMETER"
+><I
+>-r <TT
+CLASS="REPLACEABLE"
+><I
+>remote machine</I
+></TT
+></I
+></TT
+>
+ </A
+> parameter, with <TT
+CLASS="REPLACEABLE"
+><I
+>remote machine</I
+></TT
+> set
+ to the IP name of the primary interface of the local host.</P
+><P
+>The <B
+CLASS="COMMAND"
+>swat</B
+> status page tries to connect with
+ <B
+CLASS="COMMAND"
+>smbd</B
+> and <B
+CLASS="COMMAND"
+>nmbd</B
+> at the address
+ <I
+CLASS="EMPHASIS"
+>127.0.0.1</I
+> to determine if they are running.
+ Not adding <I
+CLASS="EMPHASIS"
+>127.0.0.1</I
+> will cause <B
+CLASS="COMMAND"
+> smbd</B
+> and <B
+CLASS="COMMAND"
+>nmbd</B
+> to always show
+ "not running" even if they really are. This can prevent <B
+CLASS="COMMAND"
+> swat</B
+> from starting/stopping/restarting <B
+CLASS="COMMAND"
+>smbd</B
+>
+ and <B
+CLASS="COMMAND"
+>nmbd</B
+>.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>bind interfaces only = no</B
+></P
+></DD
+><DT
+><A
+NAME="BLOCKINGLOCKS"
+></A
+>blocking locks (S)</DT
+><DD
+><P
+>This parameter controls the behavior of <A
+HREF="smbd.8.html"
+TARGET="_top"
+>smbd(8)</A
+> when given a request by a client
+ to obtain a byte range lock on a region of an open file, and the
+ request has a time limit associated with it.</P
+><P
+>If this parameter is set and the lock range requested
+ cannot be immediately satisfied, samba will internally
+ queue the lock request, and periodically attempt to obtain
+ the lock until the timeout period expires.</P
+><P
+>If this parameter is set to <TT
+CLASS="CONSTANT"
+>no</TT
+>, then
+ samba will behave as previous versions of Samba would and
+ will fail the lock request immediately if the lock range
+ cannot be obtained.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>blocking locks = yes</B
+></P
+></DD
+><DT
+><A
+NAME="BLOCKSIZE"
+></A
+>block size (S)</DT
+><DD
+><P
+>This parameter controls the behavior of
+ <A
+HREF="smbd.8.html"
+TARGET="_top"
+>smbd(8)</A
+> when reporting disk free
+ sizes. By default, this reports a disk block size of 1024 bytes.
+ </P
+><P
+>Changing this parameter may have some effect on the
+ efficiency of client writes, this is not yet confirmed. This
+ parameter was added to allow advanced administrators to change
+ it (usually to a higher value) and test the effect it has on
+ client write performance without re-compiling the code. As this
+ is an experimental option it may be removed in a future release.
+ </P
+><P
+>Changing this option does not change the disk free reporting
+ size, just the block size unit reported to the client.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>block size = 1024</B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>block size = 65536</B
+></P
+></DD
+><DT
+><A
+NAME="BROWSABLE"
+></A
+>browsable (S)</DT
+><DD
+><P
+>See the <A
+HREF="#BROWSEABLE"
+><TT
+CLASS="PARAMETER"
+><I
+> browseable</I
+></TT
+></A
+>.</P
+></DD
+><DT
+><A
+NAME="BROWSELIST"
+></A
+>browse list (G)</DT
+><DD
+><P
+>This controls whether <A
+HREF="smbd.8.html"
+TARGET="_top"
+> <B
+CLASS="COMMAND"
+>smbd(8)</B
+></A
+> will serve a browse list to
+ a client doing a <B
+CLASS="COMMAND"
+>NetServerEnum</B
+> call. Normally
+ set to <TT
+CLASS="CONSTANT"
+>yes</TT
+>. You should never need to change
+ this.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>browse list = yes</B
+></P
+></DD
+><DT
+><A
+NAME="BROWSEABLE"
+></A
+>browseable (S)</DT
+><DD
+><P
+>This controls whether this share is seen in
+ the list of available shares in a net view and in the browse list.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>browseable = yes</B
+></P
+></DD
+><DT
+><A
+NAME="CASESENSITIVE"
+></A
+>case sensitive (S)</DT
+><DD
+><P
+>See the discussion in the section <A
+HREF="#AEN205"
+>NAME MANGLING</A
+>.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>case sensitive = no</B
+></P
+></DD
+><DT
+><A
+NAME="CASESIGNAMES"
+></A
+>casesignames (S)</DT
+><DD
+><P
+>Synonym for <A
+HREF="#CASESENSITIVE"
+>case
+ sensitive</A
+>.</P
+></DD
+><DT
+><A
+NAME="CHANGENOTIFYTIMEOUT"
+></A
+>change notify timeout (G)</DT
+><DD
+><P
+>This SMB allows a client to tell a server to
+ "watch" a particular directory for any changes and only reply to
+ the SMB request when a change has occurred. Such constant scanning of
+ a directory is expensive under UNIX, hence an <A
+HREF="smbd.8.html"
+TARGET="_top"
+> <B
+CLASS="COMMAND"
+>smbd(8)</B
+></A
+> daemon only performs such a scan
+ on each requested directory once every <TT
+CLASS="PARAMETER"
+><I
+>change notify
+ timeout</I
+></TT
+> seconds.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>change notify timeout = 60</B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>change notify timeout = 300</B
+></P
+><P
+>Would change the scan time to every 5 minutes.</P
+></DD
+><DT
+><A
+NAME="CHANGESHARECOMMAND"
+></A
+>change share command (G)</DT
+><DD
+><P
+>Samba 2.2.0 introduced the ability to dynamically
+ add and delete shares via the Windows NT 4.0 Server Manager. The
+ <TT
+CLASS="PARAMETER"
+><I
+>change share command</I
+></TT
+> is used to define an
+ external program or script which will modify an existing service definition
+ in <TT
+CLASS="FILENAME"
+>smb.conf</TT
+>. In order to successfully
+ execute the <TT
+CLASS="PARAMETER"
+><I
+>change share command</I
+></TT
+>, <B
+CLASS="COMMAND"
+>smbd</B
+>
+ requires that the administrator be connected using a root account (i.e.
+ uid == 0).
+ </P
+><P
+> When executed, <B
+CLASS="COMMAND"
+>smbd</B
+> will automatically invoke the
+ <TT
+CLASS="PARAMETER"
+><I
+>change share command</I
+></TT
+> with four parameters.
+ </P
+><P
+></P
+><UL
+><LI
+><P
+><TT
+CLASS="PARAMETER"
+><I
+>configFile</I
+></TT
+> - the location
+ of the global <TT
+CLASS="FILENAME"
+>smb.conf</TT
+> file.
+ </P
+></LI
+><LI
+><P
+><TT
+CLASS="PARAMETER"
+><I
+>shareName</I
+></TT
+> - the name of the new
share.
- </p></li><li><p><i><tt>pathName</tt></i> - path to an **existing**
+ </P
+></LI
+><LI
+><P
+><TT
+CLASS="PARAMETER"
+><I
+>pathName</I
+></TT
+> - path to an **existing**
directory on disk.
- </p></li><li><p><i><tt>comment</tt></i> - comment string to associate
+ </P
+></LI
+><LI
+><P
+><TT
+CLASS="PARAMETER"
+><I
+>comment</I
+></TT
+> - comment string to associate
with the new share.
- </p></li></ul></div><p>
- This parameter is only used modify existing file shares definitions. To modify
- printer shares, use the &quot;Printers...&quot; folder as seen when browsing the Samba host.
- </p><p>
- See also <a href="#ADDSHARECOMMAND"><i><tt>add share
- command</tt></i></a>, <a href="#DELETESHARECOMMAND"><i><tt>delete
- share command</tt></i></a>.
- </p><p>Default: <span class="emphasis"><em>none</em></span></p><p>Example: <b>change share command = /usr/local/bin/addshare</b></p></dd><dt><span class="term"><a name="COMMENT"></a>comment (S)</span></dt><dd><p>This is a text field that is seen next to a share
- when a client does a queries the server, either via the network
- neighborhood or via <b>net view</b> to list what shares
- are available.</p><p>If you want to set the string that is displayed next to the
- machine name then see the <a href="#SERVERSTRING"><i><tt>
- server string</tt></i></a> parameter.</p><p>Default: <span class="emphasis"><em>No comment string</em></span></p><p>Example: <b>comment = Fred's Files</b></p></dd><dt><span class="term"><a name="CONFIGFILE"></a>config file (G)</span></dt><dd><p>This allows you to override the config file
- to use, instead of the default (usually <tt>smb.conf</tt>).
- There is a chicken and egg problem here as this option is set
- in the config file!</p><p>For this reason, if the name of the config file has changed
- when the parameters are loaded then it will reload them from
- the new config file.</p><p>This option takes the usual substitutions, which can
- be very useful.</p><p>If the config file doesn't exist then it won't be loaded
- (allowing you to special case the config files of just a few
- clients).</p><p>Example: <b>config file = /usr/local/samba/lib/smb.conf.%m</b></p></dd><dt><span class="term"><a name="COPY"></a>copy (S)</span></dt><dd><p>This parameter allows you to &quot;clone&quot; service
- entries. The specified service is simply duplicated under the
- current service's name. Any parameters specified in the current
- section will override those in the section being copied.</p><p>This feature lets you set up a 'template' service and
- create similar services easily. Note that the service being
- copied must occur earlier in the configuration file than the
- service doing the copying.</p><p>Default: <span class="emphasis"><em>no value</em></span></p><p>Example: <b>copy = otherservice</b></p></dd><dt><span class="term"><a name="CREATEMASK"></a>create mask (S)</span></dt><dd><p>A synonym for this parameter is
- <a href="#CREATEMODE"><i><tt>create mode</tt></i>
- </a>.</p><p>When a file is created, the necessary permissions are
- calculated according to the mapping from DOS modes to UNIX
- permissions, and the resulting UNIX mode is then bit-wise 'AND'ed
- with this parameter. This parameter may be thought of as a bit-wise
- MASK for the UNIX modes of a file. Any bit <span class="emphasis"><em>not</em></span>
- set here will be removed from the modes set on a file when it is
- created.</p><p>The default value of this parameter removes the
- 'group' and 'other' write and execute bits from the UNIX modes.</p><p>Following this Samba will bit-wise 'OR' the UNIX mode created
- from this parameter with the value of the <a href="#FORCECREATEMODE">
- <i><tt>force create mode</tt></i></a>
- parameter which is set to 000 by default.</p><p>This parameter does not affect directory modes. See the
- parameter <a href="#DIRECTORYMODE"><i><tt>directory mode
- </tt></i></a> for details.</p><p>See also the <a href="#FORCECREATEMODE"><i><tt>force
- create mode</tt></i></a> parameter for forcing particular mode
- bits to be set on created files. See also the <a href="#DIRECTORYMODE">
- <i><tt>directory mode</tt></i></a> parameter for masking
- mode bits on created directories. See also the <a href="#INHERITPERMISSIONS">
- <i><tt>inherit permissions</tt></i></a> parameter.</p><p>Note that this parameter does not apply to permissions
- set by Windows NT/2000 ACL editors. If the administrator wishes to enforce
- a mask on access control lists also, they need to set the <a href="#SECURITYMASK">
- <i><tt>security mask</tt></i></a>.</p><p>Default: <b>create mask = 0744</b></p><p>Example: <b>create mask = 0775</b></p></dd><dt><span class="term"><a name="CREATEMODE"></a>create mode (S)</span></dt><dd><p>This is a synonym for <a href="#CREATEMASK"><i><tt>
- create mask</tt></i></a>.</p></dd><dt><span class="term"><a name="CSCPOLICY"></a>csc policy (S)</span></dt><dd><p>This stands for <span class="emphasis"><em>client-side caching
- policy</em></span>, and specifies how clients capable of offline
- caching will cache the files in the share. The valid values
- are: manual, documents, programs, disable.</p><p>These values correspond to those used on Windows servers.</p><p>For example, shares containing roaming profiles can have
- offline caching disabled using <b>csc policy = disable</b>.</p><p>Default: <b>csc policy = manual</b></p><p>Example: <b>csc policy = programs</b></p></dd><dt><span class="term"><a name="DEADTIME"></a>dead time (G)</span></dt><dd><p>The value of the parameter (a decimal integer)
- represents the number of minutes of inactivity before a connection
- is considered dead, and it is disconnected. The deadtime only takes
- effect if the number of open files is zero.</p><p>This is useful to stop a server's resources being
- exhausted by a large number of inactive connections.</p><p>Most clients have an auto-reconnect feature when a
- connection is broken so in most cases this parameter should be
- transparent to users.</p><p>Using this parameter with a timeout of a few minutes
- is recommended for most systems.</p><p>A deadtime of zero indicates that no auto-disconnection
- should be performed.</p><p>Default: <b>deadtime = 0</b></p><p>Example: <b>deadtime = 15</b></p></dd><dt><span class="term"><a name="DEBUGHIRESTIMESTAMP"></a>debug hires timestamp (G)</span></dt><dd><p>Sometimes the timestamps in the log messages
- are needed with a resolution of higher that seconds, this
- boolean parameter adds microsecond resolution to the timestamp
- message header when turned on.</p><p>Note that the parameter <a href="#DEBUGTIMESTAMP"><i><tt>
- debug timestamp</tt></i></a> must be on for this to have an
- effect.</p><p>Default: <b>debug hires timestamp = no</b></p></dd><dt><span class="term"><a name="DEBUGLEVEL"></a>debug level (G)</span></dt><dd><p>Synonym for <a href="#LOGLEVEL"><i><tt>
- log level</tt></i></a>.</p></dd><dt><span class="term"><a name="DEBUGPID"></a>debug pid (G)</span></dt><dd><p>When using only one log file for more then one forked
- <a href="smbd.8.html">smbd(8)</a>-process there may be hard to
- follow which process outputs which message. This boolean parameter
- is adds the process-id to the timestamp message headers in the
- logfile when turned on.</p><p>Note that the parameter <a href="#DEBUGTIMESTAMP"><i><tt>
- debug timestamp</tt></i></a> must be on for this to have an
- effect.</p><p>Default: <b>debug pid = no</b></p></dd><dt><span class="term"><a name="DEBUGTIMESTAMP"></a>debug timestamp (G)</span></dt><dd><p>Samba debug log messages are timestamped
- by default. If you are running at a high <a href="#DEBUGLEVEL">
- <i><tt>debug level</tt></i></a> these timestamps
- can be distracting. This boolean parameter allows timestamping
- to be turned off.</p><p>Default: <b>debug timestamp = yes</b></p></dd><dt><span class="term"><a name="DEBUGUID"></a>debug uid (G)</span></dt><dd><p>Samba is sometimes run as root and sometime
- run as the connected user, this boolean parameter inserts the
- current euid, egid, uid and gid to the timestamp message headers
- in the log file if turned on.</p><p>Note that the parameter <a href="#DEBUGTIMESTAMP"><i><tt>
- debug timestamp</tt></i></a> must be on for this to have an
- effect.</p><p>Default: <b>debug uid = no</b></p></dd><dt><span class="term"><a name="DEFAULTCASE"></a>default case (S)</span></dt><dd><p>See the section on <a href="#NAMEMANGLINGSECT" title="NAME MANGLING">
- NAME MANGLING</a>. Also note the <a href="#SHORTPRESERVECASE">
- <i><tt>short preserve case</tt></i></a> parameter.</p><p>Default: <b>default case = lower</b></p></dd><dt><span class="term"><a name="DEFAULTDEVMODE"></a>default devmode (S)</span></dt><dd><p>This parameter is only applicable to <a href="#PRINTOK">printable</a> services.
- When smbd is serving Printer Drivers to Windows NT/2k/XP clients, each printer on the Samba
- server has a Device Mode which defines things such as paper size and
- orientation and duplex settings. The device mode can only correctly be
- generated by the printer driver itself (which can only be executed on a
- Win32 platform). Because smbd is unable to execute the driver code
- to generate the device mode, the default behavior is to set this field
- to NULL.
- </p><p>Most problems with serving printer drivers to Windows NT/2k/XP clients
- can be traced to a problem with the generated device mode. Certain drivers
- will do things such as crashing the client's Explorer.exe with a NULL devmode.
- However, other printer drivers can cause the client's spooler service
- (spoolsv.exe) to die if the devmode was not created by the driver itself
- (i.e. smbd generates a default devmode).
- </p><p>This parameter should be used with care and tested with the printer
- driver in question. It is better to leave the device mode to NULL
- and let the Windows client set the correct values. Because drivers do not
- do this all the time, setting <b>default devmode = yes</b>
- will instruct smbd to generate a default one.
- </p><p>For more information on Windows NT/2k printing and Device Modes,
- see the <a href="http://msdn.microsoft.com/" target="_top">MSDN documentation</a>.
- </p><p>Default: <b>default devmode = no</b></p></dd><dt><span class="term"><a name="DEFAULTSERVICE"></a>default service (G)</span></dt><dd><p>This parameter specifies the name of a service
- which will be connected to if the service actually requested cannot
- be found. Note that the square brackets are <span class="emphasis"><em>NOT</em></span>
- given in the parameter value (see example below).</p><p>There is no default value for this parameter. If this
- parameter is not given, attempting to connect to a nonexistent
- service results in an error.</p><p>Typically the default service would be a <a href="#GUESTOK">
- <i><tt>guest ok</tt></i></a>, <a href="#READONLY">
- <i><tt>read-only</tt></i></a> service.</p><p>Also note that the apparent service name will be changed
- to equal that of the requested service, this is very useful as it
- allows you to use macros like <i><tt>%S</tt></i> to make
- a wildcard service.</p><p>Note also that any &quot;_&quot; characters in the name of the service
- used in the default service will get mapped to a &quot;/&quot;. This allows for
- interesting things.</p><p>Example:</p><pre class="programlisting">
-[global]
+ </P
+></LI
+></UL
+><P
+> This parameter is only used modify existing file shares definitions. To modify
+ printer shares, use the "Printers..." folder as seen when browsing the Samba host.
+ </P
+><P
+> See also <A
+HREF="#ADDSHARECOMMAND"
+><TT
+CLASS="PARAMETER"
+><I
+>add share
+ command</I
+></TT
+></A
+>, <A
+HREF="#DELETESHARECOMMAND"
+><TT
+CLASS="PARAMETER"
+><I
+>delete
+ share command</I
+></TT
+></A
+>.
+ </P
+><P
+>Default: <I
+CLASS="EMPHASIS"
+>none</I
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>change share command = /usr/local/bin/addshare</B
+></P
+></DD
+><DT
+><A
+NAME="COMMENT"
+></A
+>comment (S)</DT
+><DD
+><P
+>This is a text field that is seen next to a share
+ when a client does a queries the server, either via the network
+ neighborhood or via <B
+CLASS="COMMAND"
+>net view</B
+> to list what shares
+ are available.</P
+><P
+>If you want to set the string that is displayed next to the
+ machine name then see the <A
+HREF="#SERVERSTRING"
+><TT
+CLASS="PARAMETER"
+><I
+> server string</I
+></TT
+></A
+> parameter.</P
+><P
+>Default: <I
+CLASS="EMPHASIS"
+>No comment string</I
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>comment = Fred's Files</B
+></P
+></DD
+><DT
+><A
+NAME="CONFIGFILE"
+></A
+>config file (G)</DT
+><DD
+><P
+>This allows you to override the config file
+ to use, instead of the default (usually <TT
+CLASS="FILENAME"
+>smb.conf</TT
+>).
+ There is a chicken and egg problem here as this option is set
+ in the config file!</P
+><P
+>For this reason, if the name of the config file has changed
+ when the parameters are loaded then it will reload them from
+ the new config file.</P
+><P
+>This option takes the usual substitutions, which can
+ be very useful.</P
+><P
+>If the config file doesn't exist then it won't be loaded
+ (allowing you to special case the config files of just a few
+ clients).</P
+><P
+>Example: <B
+CLASS="COMMAND"
+>config file = /usr/local/samba/lib/smb.conf.%m
+ </B
+></P
+></DD
+><DT
+><A
+NAME="COPY"
+></A
+>copy (S)</DT
+><DD
+><P
+>This parameter allows you to "clone" service
+ entries. The specified service is simply duplicated under the
+ current service's name. Any parameters specified in the current
+ section will override those in the section being copied.</P
+><P
+>This feature lets you set up a 'template' service and
+ create similar services easily. Note that the service being
+ copied must occur earlier in the configuration file than the
+ service doing the copying.</P
+><P
+>Default: <I
+CLASS="EMPHASIS"
+>no value</I
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>copy = otherservice</B
+></P
+></DD
+><DT
+><A
+NAME="CREATEMASK"
+></A
+>create mask (S)</DT
+><DD
+><P
+>A synonym for this parameter is
+ <A
+HREF="#CREATEMODE"
+><TT
+CLASS="PARAMETER"
+><I
+>create mode</I
+></TT
+>
+ </A
+>.</P
+><P
+>When a file is created, the necessary permissions are
+ calculated according to the mapping from DOS modes to UNIX
+ permissions, and the resulting UNIX mode is then bit-wise 'AND'ed
+ with this parameter. This parameter may be thought of as a bit-wise
+ MASK for the UNIX modes of a file. Any bit <I
+CLASS="EMPHASIS"
+>not</I
+>
+ set here will be removed from the modes set on a file when it is
+ created.</P
+><P
+>The default value of this parameter removes the
+ 'group' and 'other' write and execute bits from the UNIX modes.</P
+><P
+>Following this Samba will bit-wise 'OR' the UNIX mode created
+ from this parameter with the value of the <A
+HREF="#FORCECREATEMODE"
+><TT
+CLASS="PARAMETER"
+><I
+>force create mode</I
+></TT
+></A
+>
+ parameter which is set to 000 by default.</P
+><P
+>This parameter does not affect directory modes. See the
+ parameter <A
+HREF="#DIRECTORYMODE"
+><TT
+CLASS="PARAMETER"
+><I
+>directory mode
+ </I
+></TT
+></A
+> for details.</P
+><P
+>See also the <A
+HREF="#FORCECREATEMODE"
+><TT
+CLASS="PARAMETER"
+><I
+>force
+ create mode</I
+></TT
+></A
+> parameter for forcing particular mode
+ bits to be set on created files. See also the <A
+HREF="#DIRECTORYMODE"
+> <TT
+CLASS="PARAMETER"
+><I
+>directory mode</I
+></TT
+></A
+> parameter for masking
+ mode bits on created directories. See also the <A
+HREF="#INHERITPERMISSIONS"
+> <TT
+CLASS="PARAMETER"
+><I
+>inherit permissions</I
+></TT
+></A
+> parameter.</P
+><P
+>Note that this parameter does not apply to permissions
+ set by Windows NT/2000 ACL editors. If the administrator wishes to enforce
+ a mask on access control lists also, they need to set the <A
+HREF="#SECURITYMASK"
+><TT
+CLASS="PARAMETER"
+><I
+>security mask</I
+></TT
+></A
+>.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>create mask = 0744</B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>create mask = 0775</B
+></P
+></DD
+><DT
+><A
+NAME="CREATEMODE"
+></A
+>create mode (S)</DT
+><DD
+><P
+>This is a synonym for <A
+HREF="#CREATEMASK"
+><TT
+CLASS="PARAMETER"
+><I
+> create mask</I
+></TT
+></A
+>.</P
+></DD
+><DT
+><A
+NAME="CSCPOLICY"
+></A
+>csc policy (S)</DT
+><DD
+><P
+>This stands for <I
+CLASS="EMPHASIS"
+>client-side caching
+ policy</I
+>, and specifies how clients capable of offline
+ caching will cache the files in the share. The valid values
+ are: manual, documents, programs, disable.</P
+><P
+>These values correspond to those used on Windows
+ servers.</P
+><P
+>For example, shares containing roaming profiles can have
+ offline caching disabled using <B
+CLASS="COMMAND"
+>csc policy = disable
+ </B
+>.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>csc policy = manual</B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>csc policy = programs</B
+></P
+></DD
+><DT
+><A
+NAME="DEADTIME"
+></A
+>deadtime (G)</DT
+><DD
+><P
+>The value of the parameter (a decimal integer)
+ represents the number of minutes of inactivity before a connection
+ is considered dead, and it is disconnected. The deadtime only takes
+ effect if the number of open files is zero.</P
+><P
+>This is useful to stop a server's resources being
+ exhausted by a large number of inactive connections.</P
+><P
+>Most clients have an auto-reconnect feature when a
+ connection is broken so in most cases this parameter should be
+ transparent to users.</P
+><P
+>Using this parameter with a timeout of a few minutes
+ is recommended for most systems.</P
+><P
+>A deadtime of zero indicates that no auto-disconnection
+ should be performed.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>deadtime = 0</B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>deadtime = 15</B
+></P
+></DD
+><DT
+><A
+NAME="DEBUGHIRESTIMESTAMP"
+></A
+>debug hires timestamp (G)</DT
+><DD
+><P
+>Sometimes the timestamps in the log messages
+ are needed with a resolution of higher that seconds, this
+ boolean parameter adds microsecond resolution to the timestamp
+ message header when turned on.</P
+><P
+>Note that the parameter <A
+HREF="#DEBUGTIMESTAMP"
+><TT
+CLASS="PARAMETER"
+><I
+> debug timestamp</I
+></TT
+></A
+> must be on for this to have an
+ effect.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>debug hires timestamp = no</B
+></P
+></DD
+><DT
+><A
+NAME="DEBUGPID"
+></A
+>debug pid (G)</DT
+><DD
+><P
+>When using only one log file for more then one
+ forked <A
+HREF="smbd.8.html"
+TARGET="_top"
+>smbd</A
+>-process there may be hard to follow which process
+ outputs which message. This boolean parameter is adds the process-id
+ to the timestamp message headers in the logfile when turned on.</P
+><P
+>Note that the parameter <A
+HREF="#DEBUGTIMESTAMP"
+><TT
+CLASS="PARAMETER"
+><I
+> debug timestamp</I
+></TT
+></A
+> must be on for this to have an
+ effect.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>debug pid = no</B
+></P
+></DD
+><DT
+><A
+NAME="DEBUGTIMESTAMP"
+></A
+>debug timestamp (G)</DT
+><DD
+><P
+>Samba debug log messages are timestamped
+ by default. If you are running at a high <A
+HREF="#DEBUGLEVEL"
+> <TT
+CLASS="PARAMETER"
+><I
+>debug level</I
+></TT
+></A
+> these timestamps
+ can be distracting. This boolean parameter allows timestamping
+ to be turned off.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>debug timestamp = yes</B
+></P
+></DD
+><DT
+><A
+NAME="DEBUGUID"
+></A
+>debug uid (G)</DT
+><DD
+><P
+>Samba is sometimes run as root and sometime
+ run as the connected user, this boolean parameter inserts the
+ current euid, egid, uid and gid to the timestamp message headers
+ in the log file if turned on.</P
+><P
+>Note that the parameter <A
+HREF="#DEBUGTIMESTAMP"
+><TT
+CLASS="PARAMETER"
+><I
+> debug timestamp</I
+></TT
+></A
+> must be on for this to have an
+ effect.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>debug uid = no</B
+></P
+></DD
+><DT
+><A
+NAME="DEBUGLEVEL"
+></A
+>debuglevel (G)</DT
+><DD
+><P
+>Synonym for <A
+HREF="#LOGLEVEL"
+><TT
+CLASS="PARAMETER"
+><I
+> log level</I
+></TT
+></A
+>.</P
+></DD
+><DT
+><A
+NAME="DEFAULT"
+></A
+>default (G)</DT
+><DD
+><P
+>A synonym for <A
+HREF="#DEFAULTSERVICE"
+><TT
+CLASS="PARAMETER"
+><I
+> default service</I
+></TT
+></A
+>.</P
+></DD
+><DT
+><A
+NAME="DEFAULTCASE"
+></A
+>default case (S)</DT
+><DD
+><P
+>See the section on <A
+HREF="#AEN205"
+> NAME MANGLING</A
+>. Also note the <A
+HREF="#SHORTPRESERVECASE"
+> <TT
+CLASS="PARAMETER"
+><I
+>short preserve case</I
+></TT
+></A
+> parameter.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>default case = lower</B
+></P
+></DD
+><DT
+><A
+NAME="DEFAULTDEVMODE"
+></A
+>default devmode (S)</DT
+><DD
+><P
+>This parameter is only applicable to <A
+HREF="#PRINTOK"
+>printable</A
+> services. When smbd is serving
+ Printer Drivers to Windows NT/2k/XP clients, each printer on the Samba
+ server has a Device Mode which defines things such as paper size and
+ orientation and duplex settings. The device mode can only correctly be
+ generated by the printer driver itself (which can only be executed on a
+ Win32 platform). Because smbd is unable to execute the driver code
+ to generate the device mode, the default behavior is to set this field
+ to NULL.
+ </P
+><P
+>Most problems with serving printer drivers to Windows NT/2k/XP clients
+ can be traced to a problem with the generated device mode. Certain drivers
+ will do things such as crashing the client's Explorer.exe with a NULL devmode.
+ However, other printer drivers can cause the client's spooler service
+ (spoolsv.exe) to die if the devmode was not created by the driver itself
+ (i.e. smbd generates a default devmode).
+ </P
+><P
+>This parameter should be used with care and tested with the printer
+ driver in question. It is better to leave the device mode to NULL
+ and let the Windows client set the correct values. Because drivers do not
+ do this all the time, setting <B
+CLASS="COMMAND"
+>default devmode = yes</B
+>
+ will instruct smbd to generate a default one.
+ </P
+><P
+>For more information on Windows NT/2k printing and Device Modes,
+ see the <A
+HREF="http://msdn.microsoft.com/"
+TARGET="_top"
+>MSDN documentation</A
+>.
+ </P
+><P
+>Default: <B
+CLASS="COMMAND"
+>default devmode = no</B
+></P
+></DD
+><DT
+><A
+NAME="DEFAULTSERVICE"
+></A
+>default service (G)</DT
+><DD
+><P
+>This parameter specifies the name of a service
+ which will be connected to if the service actually requested cannot
+ be found. Note that the square brackets are <I
+CLASS="EMPHASIS"
+>NOT</I
+>
+ given in the parameter value (see example below).</P
+><P
+>There is no default value for this parameter. If this
+ parameter is not given, attempting to connect to a nonexistent
+ service results in an error.</P
+><P
+>Typically the default service would be a <A
+HREF="#GUESTOK"
+> <TT
+CLASS="PARAMETER"
+><I
+>guest ok</I
+></TT
+></A
+>, <A
+HREF="#READONLY"
+> <TT
+CLASS="PARAMETER"
+><I
+>read-only</I
+></TT
+></A
+> service.</P
+><P
+>Also note that the apparent service name will be changed
+ to equal that of the requested service, this is very useful as it
+ allows you to use macros like <TT
+CLASS="PARAMETER"
+><I
+>%S</I
+></TT
+> to make
+ a wildcard service.</P
+><P
+>Note also that any "_" characters in the name of the service
+ used in the default service will get mapped to a "/". This allows for
+ interesting things.</P
+><P
+>Example:</P
+><P
+><TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="90%"
+><TR
+><TD
+><PRE
+CLASS="PROGRAMLISTING"
+>[global]
default service = pub
[pub]
path = /%S
-</pre></dd><dt><span class="term"><a name="DEFAULT"></a>default (G)</span></dt><dd><p>A synonym for <a href="#DEFAULTSERVICE"><i><tt>
- default service</tt></i></a>.</p></dd><dt><span class="term"><a name="DELETEGROUPSCRIPT"></a>delete group script (G)</span></dt><dd><p>This is the full pathname to a script that will
- be run <span class="emphasis"><em>AS ROOT</em></span> <a href="smbd.8.html">smbd(8)</a> when a group is requested to be deleted.
- It will expand any <i><tt>%g</tt></i> to the group name passed.
- This script is only useful for installations using the Windows NT domain administration tools.
- </p></dd><dt><span class="term"><a name="DELETEPRINTERCOMMAND"></a>deleteprinter command (G)</span></dt><dd><p>With the introduction of MS-RPC based printer
- support for Windows NT/2000 clients in Samba 2.2, it is now
- possible to delete printer at run time by issuing the
- DeletePrinter() RPC call.</p><p>For a Samba host this means that the printer must be
- physically deleted from underlying printing system. The <i><tt>
- deleteprinter command</tt></i> defines a script to be run which
- will perform the necessary operations for removing the printer
- from the print system and from <tt>smb.conf</tt>.
- </p><p>The <i><tt>deleteprinter command</tt></i> is
- automatically called with only one parameter: <i><tt>
- &quot;printer name&quot;</tt></i>.</p><p>Once the <i><tt>deleteprinter command</tt></i> has
- been executed, <b>smbd</b> will reparse the <tt>
- smb.conf</tt> to associated printer no longer exists.
- If the sharename is still valid, then <b>smbd
- </b> will return an ACCESS_DENIED error to the client.</p><p>See also <a href="#ADDPRINTERCOMMAND"><i><tt>
- addprinter command</tt></i></a>, <a href="#PRINTING">
- <i><tt>printing</tt></i></a>,
- <a href="#SHOWADDPRINTERWIZARD"><i><tt>show add
- printer wizard</tt></i></a></p><p>Default: <span class="emphasis"><em>none</em></span></p><p>Example: <b>deleteprinter command = /usr/bin/removeprinter</b></p></dd><dt><span class="term"><a name="DELETEREADONLY"></a>delete readonly (S)</span></dt><dd><p>This parameter allows readonly files to be deleted.
- This is not normal DOS semantics, but is allowed by UNIX.</p><p>This option may be useful for running applications such
- as rcs, where UNIX file ownership prevents changing file
- permissions, and DOS semantics prevent deletion of a read only file.</p><p>Default: <b>delete readonly = no</b></p></dd><dt><span class="term"><a name="DELETESHARECOMMAND"></a>delete share command (G)</span></dt><dd><p>Samba 2.2.0 introduced the ability to dynamically
- add and delete shares via the Windows NT 4.0 Server Manager. The
- <i><tt>delete share command</tt></i> is used to define an
- external program or script which will remove an existing service
- definition from <tt>smb.conf</tt>. In order to successfully
- execute the <i><tt>delete share command</tt></i>, <b>smbd</b>
- requires that the administrator be connected using a root account (i.e.
- uid == 0).
- </p><p>
- When executed, <b>smbd</b> will automatically invoke the
- <i><tt>delete share command</tt></i> with two parameters.
- </p><div class="itemizedlist"><ul type="disc"><li><p><i><tt>configFile</tt></i> - the location
- of the global <tt>smb.conf</tt> file.
- </p></li><li><p><i><tt>shareName</tt></i> - the name of
+ </PRE
+></TD
+></TR
+></TABLE
+></P
+></DD
+><DT
+><A
+NAME="DELETEGROUPSCRIPT"
+></A
+>delete group script (G)</DT
+><DD
+><P
+>This is the full pathname to a script that will
+ be run <I
+CLASS="EMPHASIS"
+>AS ROOT</I
+> by <A
+HREF="smbd.8.html"
+TARGET="_top"
+>smbd(8)</A
+> when a group is requested to be deleted. It will expand any <TT
+CLASS="PARAMETER"
+><I
+>%g</I
+></TT
+> to the group name passed. This script is only useful for installations using the Windows NT domain administration tools.
+ </P
+></DD
+><DT
+><A
+NAME="DELETEPRINTERCOMMAND"
+></A
+>deleteprinter command (G)</DT
+><DD
+><P
+>With the introduction of MS-RPC based printer
+ support for Windows NT/2000 clients in Samba 2.2, it is now
+ possible to delete printer at run time by issuing the
+ DeletePrinter() RPC call.</P
+><P
+>For a Samba host this means that the printer must be
+ physically deleted from underlying printing system. The <TT
+CLASS="PARAMETER"
+><I
+> deleteprinter command</I
+></TT
+> defines a script to be run which
+ will perform the necessary operations for removing the printer
+ from the print system and from <TT
+CLASS="FILENAME"
+>smb.conf</TT
+>.
+ </P
+><P
+>The <TT
+CLASS="PARAMETER"
+><I
+>deleteprinter command</I
+></TT
+> is
+ automatically called with only one parameter: <TT
+CLASS="PARAMETER"
+><I
+> "printer name"</I
+></TT
+>.</P
+><P
+>Once the <TT
+CLASS="PARAMETER"
+><I
+>deleteprinter command</I
+></TT
+> has
+ been executed, <B
+CLASS="COMMAND"
+>smbd</B
+> will reparse the <TT
+CLASS="FILENAME"
+> smb.conf</TT
+> to associated printer no longer exists.
+ If the sharename is still valid, then <B
+CLASS="COMMAND"
+>smbd
+ </B
+> will return an ACCESS_DENIED error to the client.</P
+><P
+>See also <A
+HREF="#ADDPRINTERCOMMAND"
+><TT
+CLASS="PARAMETER"
+><I
+> addprinter command</I
+></TT
+></A
+>, <A
+HREF="#PRINTING"
+><TT
+CLASS="PARAMETER"
+><I
+>printing</I
+></TT
+></A
+>,
+ <A
+HREF="#SHOWADDPRINTERWIZARD"
+><TT
+CLASS="PARAMETER"
+><I
+>show add
+ printer wizard</I
+></TT
+></A
+></P
+><P
+>Default: <I
+CLASS="EMPHASIS"
+>none</I
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>deleteprinter command = /usr/bin/removeprinter
+ </B
+></P
+></DD
+><DT
+><A
+NAME="DELETEREADONLY"
+></A
+>delete readonly (S)</DT
+><DD
+><P
+>This parameter allows readonly files to be deleted.
+ This is not normal DOS semantics, but is allowed by UNIX.</P
+><P
+>This option may be useful for running applications such
+ as rcs, where UNIX file ownership prevents changing file
+ permissions, and DOS semantics prevent deletion of a read only file.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>delete readonly = no</B
+></P
+></DD
+><DT
+><A
+NAME="DELETESHARECOMMAND"
+></A
+>delete share command (G)</DT
+><DD
+><P
+>Samba 2.2.0 introduced the ability to dynamically
+ add and delete shares via the Windows NT 4.0 Server Manager. The
+ <TT
+CLASS="PARAMETER"
+><I
+>delete share command</I
+></TT
+> is used to define an
+ external program or script which will remove an existing service
+ definition from <TT
+CLASS="FILENAME"
+>smb.conf</TT
+>. In order to successfully
+ execute the <TT
+CLASS="PARAMETER"
+><I
+>delete share command</I
+></TT
+>, <B
+CLASS="COMMAND"
+>smbd</B
+>
+ requires that the administrator be connected using a root account (i.e.
+ uid == 0).
+ </P
+><P
+> When executed, <B
+CLASS="COMMAND"
+>smbd</B
+> will automatically invoke the
+ <TT
+CLASS="PARAMETER"
+><I
+>delete share command</I
+></TT
+> with two parameters.
+ </P
+><P
+></P
+><UL
+><LI
+><P
+><TT
+CLASS="PARAMETER"
+><I
+>configFile</I
+></TT
+> - the location
+ of the global <TT
+CLASS="FILENAME"
+>smb.conf</TT
+> file.
+ </P
+></LI
+><LI
+><P
+><TT
+CLASS="PARAMETER"
+><I
+>shareName</I
+></TT
+> - the name of
the existing service.
- </p></li></ul></div><p>
- This parameter is only used to remove file shares. To delete printer shares,
- see the <a href="#DELETEPRINTERCOMMAND"><i><tt>deleteprinter
- command</tt></i></a>.
- </p><p>
- See also <a href="#ADDSHARECOMMAND"><i><tt>add share
- command</tt></i></a>, <a href="#CHANGESHARECOMMAND"><i><tt>change
- share command</tt></i></a>.
- </p><p>Default: <span class="emphasis"><em>none</em></span></p><p>Example: <b>delete share command = /usr/local/bin/delshare</b></p></dd><dt><span class="term"><a name="DELETEUSERFROMGROUPSCRIPT"></a>delete user from group script (G)</span></dt><dd><p>Full path to the script that will be called when
- a user is removed from a group using the Windows NT domain administration
- tools. It will be run by <a href="smbd.8.html">smbd(8)</a> <span class="emphasis"><em>AS ROOT</em></span>.
- Any <i><tt>%g</tt></i> will be replaced with the group name and
- any <i><tt>%u</tt></i> will be replaced with the user name.
- </p><p>Default: <b>delete user from group script = </b></p><p>Example: <b>delete user from group script = /usr/sbin/deluser %u %g</b></p></dd><dt><span class="term"><a name="DELETEUSERSCRIPT"></a>delete user script (G)</span></dt><dd><p>This is the full pathname to a script that will
- be run by <a href="smbd.8.html">smbd(8)</a> when managing users
- with remote RPC (NT) tools.
- </p><p>This script is called when a remote client removes a user
- from the server, normally using 'User Manager for Domains' or
- <b>rpcclient</b>.</p><p>This script should delete the given UNIX username.</p><p>Default: <b>delete user script = &lt;empty string&gt;</b></p><p>Example: <b>delete user script = /usr/local/samba/bin/del_user %u</b></p></dd><dt><span class="term"><a name="DELETEVETOFILES"></a>delete veto files (S)</span></dt><dd><p>This option is used when Samba is attempting to
- delete a directory that contains one or more vetoed directories
- (see the <a href="#VETOFILES"><i><tt>veto files</tt></i></a>
- option). If this option is set to <tt>no</tt> (the default) then if a vetoed
- directory contains any non-vetoed files or directories then the
- directory delete will fail. This is usually what you want.</p><p>If this option is set to <tt>yes</tt>, then Samba
- will attempt to recursively delete any files and directories within
- the vetoed directory. This can be useful for integration with file
- serving systems such as NetAtalk which create meta-files within
- directories you might normally veto DOS/Windows users from seeing
- (e.g. <tt>.AppleDouble</tt>)</p><p>Setting <b>delete veto files = yes</b> allows these
- directories to be transparently deleted when the parent directory
- is deleted (so long as the user has permissions to do so).</p><p>See also the <a href="#VETOFILES"><i><tt>veto
- files</tt></i></a> parameter.</p><p>Default: <b>delete veto files = no</b></p></dd><dt><span class="term"><a name="DENYHOSTS"></a>deny hosts (S)</span></dt><dd><p>Synonym for <a href="#HOSTSDENY"><i><tt>hosts
- deny</tt></i></a>.</p></dd><dt><span class="term"><a name="DFREECOMMAND"></a>dfree command (G)</span></dt><dd><p>The <i><tt>dfree command</tt></i> setting
- should only be used on systems where a problem occurs with the
- internal disk space calculations. This has been known to happen
- with Ultrix, but may occur with other operating systems. The
- symptom that was seen was an error of &quot;Abort Retry
- Ignore&quot; at the end of each directory listing.</p><p>This setting allows the replacement of the internal routines to
- calculate the total disk space and amount available with an external
- routine. The example below gives a possible script that might fulfill
- this function.</p><p>The external program will be passed a single parameter indicating
- a directory in the filesystem being queried. This will typically consist
- of the string <tt>./</tt>. The script should return two
- 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><p>Note: Your script should <span class="emphasis"><em>NOT</em></span> be setuid or
- setgid and should be owned by (and writeable only by) root!</p><p>Default: <span class="emphasis"><em>By default internal routines for
- determining the disk capacity and remaining space will be used.
- </em></span></p><p>Example: <b>dfree command = /usr/local/samba/bin/dfree</b></p><p>Where the script dfree (which must be made executable) could be:</p><pre class="programlisting">
-#!/bin/sh
-df $1 | tail -1 | awk '{print $2&quot; &quot;$4}'
-</pre><p>or perhaps (on Sys V based systems):</p><pre class="programlisting">
-#!/bin/sh
-/usr/bin/df -k $1 | tail -1 | awk '{print $3&quot; &quot;$5}'
-</pre><p>Note that you may have to replace the command names with full path names on some systems.</p></dd><dt><span class="term"><a name="DIRECTORYMASK"></a>directory mask (S)</span></dt><dd><p>This parameter is the octal modes which are
- used when converting DOS modes to UNIX modes when creating UNIX
- directories.</p><p>When a directory is created, the necessary permissions are
- calculated according to the mapping from DOS modes to UNIX permissions,
- and the resulting UNIX mode is then bit-wise 'AND'ed with this
- parameter. This parameter may be thought of as a bit-wise MASK for
- the UNIX modes of a directory. Any bit <span class="emphasis"><em>not</em></span> set
- here will be removed from the modes set on a directory when it is
- created.</p><p>The default value of this parameter removes the 'group'
- and 'other' write bits from the UNIX mode, allowing only the
- user who owns the directory to modify it.</p><p>Following this Samba will bit-wise 'OR' the UNIX mode
- created from this parameter with the value of the <a href="#FORCEDIRECTORYMODE">
- <i><tt>force directory mode</tt></i></a> parameter.
- This parameter is set to 000 by default (i.e. no extra mode bits are added).</p><p>Note that this parameter does not apply to permissions
- set by Windows NT/2000 ACL editors. If the administrator wishes to enforce
- a mask on access control lists also, they need to set the <a href="#DIRECTORYSECURITYMASK">
- <i><tt>directory security mask</tt></i></a>.</p><p>See the <a href="#FORCEDIRECTORYMODE"><i><tt>force
- directory mode</tt></i></a> parameter to cause particular mode
- bits to always be set on created directories.</p><p>See also the <a href="#CREATEMODE"><i><tt>create mode
- </tt></i></a> parameter for masking mode bits on created files,
- and the <a href="#DIRECTORYSECURITYMASK"><i><tt>directory
- security mask</tt></i></a> parameter.</p><p>Also refer to the <a href="#INHERITPERMISSIONS"><i><tt>
- inherit permissions</tt></i></a> parameter.</p><p>Default: <b>directory mask = 0755</b></p><p>Example: <b>directory mask = 0775</b></p></dd><dt><span class="term"><a name="DIRECTORYMODE"></a>directory mode (S)</span></dt><dd><p>Synonym for <a href="#DIRECTORYMASK"><i><tt>
- directory mask</tt></i></a></p></dd><dt><span class="term"><a name="DIRECTORYSECURITYMASK"></a>directory security mask (S)</span></dt><dd><p>This parameter controls what UNIX permission bits
- can be modified when a Windows NT client is manipulating the UNIX
- permission on a directory using the native NT security dialog
- box.</p><p>This parameter is applied as a mask (AND'ed with) to
- the changed permission bits, thus preventing any bits not in
- this mask from being modified. Essentially, zero bits in this
- mask may be treated as a set of bits the user is not allowed
- to change.</p><p>If not set explicitly this parameter is set to 0777
- meaning a user is allowed to modify all the user/group/world
- permissions on a directory.</p><p><span class="emphasis"><em>Note</em></span> that users who can access the
- Samba server through other means can easily bypass this restriction,
- so it is primarily useful for standalone &quot;appliance&quot; systems.
- Administrators of most normal systems will probably want to leave
- it as the default of <tt>0777</tt>.</p><p>See also the <a href="#FORCEDIRECTORYSECURITYMODE"><i><tt>
- force directory security mode</tt></i></a>, <a href="#SECURITYMASK">
- <i><tt>security mask</tt></i></a>,
- <a href="#FORCESECURITYMODE"><i><tt>force security mode
- </tt></i></a> parameters.</p><p>Default: <b>directory security mask = 0777</b></p><p>Example: <b>directory security mask = 0700</b></p></dd><dt><span class="term"><a name="DIRECTORY"></a>directory (S)</span></dt><dd><p>Synonym for <a href="#PATH"><i><tt>path</tt></i></a>.</p></dd><dt><span class="term"><a name="DISABLENETBIOS"></a>disable netbios (G)</span></dt><dd><p>Enabling this parameter will disable netbios support
- in Samba. Netbios is the only available form of browsing in
- all windows versions except for 2000 and XP. </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>Note that clients that only support netbios won't be able to
- see your samba server when netbios support is disabled.
- </p></div><p>Default: <b>disable netbios = no</b></p><p>Example: <b>disable netbios = yes</b></p></dd><dt><span class="term"><a name="DISABLESPOOLSS"></a>disable spoolss (G)</span></dt><dd><p>Enabling this parameter will disable Samba's support
- for the SPOOLSS set of MS-RPC's and will yield identical behavior
- as Samba 2.0.x. Windows NT/2000 clients will downgrade to using
- Lanman style printing commands. Windows 9x/ME will be uneffected by
- the parameter. However, this will also disable the ability to upload
- printer drivers to a Samba server via the Windows NT Add Printer
- Wizard or by using the NT printer properties dialog window. It will
- also disable the capability of Windows NT/2000 clients to download
- print drivers from the Samba host upon demand.
- <span class="emphasis"><em>Be very careful about enabling this parameter.</em></span>
- </p><p>See also <a href="#USECLIENTDRIVER">use client driver</a>
- </p><p>Default : <b>disable spoolss = no</b></p></dd><dt><span class="term"><a name="DISPLAYCHARSET"></a>display charset (G)</span></dt><dd><p>Specifies the charset that samba will use
- to print messages to stdout and stderr and SWAT will use.
- Should generally be the same as the <b>unix charset</b>.
- </p><p>Default: <b>display charset = ASCII</b></p><p>Example: <b>display charset = UTF8</b></p></dd><dt><span class="term"><a name="DNSPROXY"></a>dns proxy (G)</span></dt><dd><p>Specifies that <a href="nmbd.8.html">nmbd(8)</a> when acting as a WINS server and
- finding that a NetBIOS name has not been registered, should treat the
- NetBIOS name word-for-word as a DNS name and do a lookup with the DNS server
- for that name on behalf of the name-querying client.</p><p>Note that the maximum length for a NetBIOS name is 15
- characters, so the DNS name (or DNS alias) can likewise only be
- 15 characters, maximum.</p><p><b>nmbd</b> spawns a second copy of itself to do the
- DNS name lookup requests, as doing a name lookup is a blocking
- action.</p><p>See also the parameter <a href="#WINSSUPPORT"><i><tt>
- wins support</tt></i></a>.</p><p>Default: <b>dns proxy = yes</b></p></dd><dt><span class="term"><a name="DOMAINLOGONS"></a>domain logons (G)</span></dt><dd><p>If set to <tt>yes</tt>, the Samba server will serve
- Windows 95/98 Domain logons for the <a href="#WORKGROUP">
- <i><tt>workgroup</tt></i></a> it is in. Samba 2.2
- has limited capability to act as a domain controller for Windows
- NT 4 Domains. For more details on setting up this feature see
- the Samba-PDC-HOWTO included in the Samba documentation.</p><p>Default: <b>domain logons = no</b></p></dd><dt><span class="term"><a name="DOMAINMASTER"></a>domain master (G)</span></dt><dd><p>Tell <a href="smbd.8.html">smbd(8)</a> to enable WAN-wide browse list
- collation. Setting this option causes <b>nmbd</b> to
- claim a special domain specific NetBIOS name that identifies
- it as a domain master browser for its given <a href="#WORKGROUP">
- <i><tt>workgroup</tt></i></a>. Local master browsers
- in the same <i><tt>workgroup</tt></i> on broadcast-isolated
- subnets will give this <b>nmbd</b> their local browse lists,
- and then ask <a href="smbd.8.html">smbd(8)</a> for a complete copy of the browse
- list for the whole wide area network. Browser clients will then contact
- their local master browser, and will receive the domain-wide browse list,
- instead of just the list for their broadcast-isolated subnet.</p><p>Note that Windows NT Primary Domain Controllers expect to be
- able to claim this <i><tt>workgroup</tt></i> specific special
- NetBIOS name that identifies them as domain master browsers for
- that <i><tt>workgroup</tt></i> by default (i.e. there is no
- way to prevent a Windows NT PDC from attempting to do this). This
- means that if this parameter is set and <b>nmbd</b> claims
- the special name for a <i><tt>workgroup</tt></i> before a Windows
- NT PDC is able to do so then cross subnet browsing will behave
- strangely and may fail.</p><p>If <a href="#DOMAINLOGONS"><b>domain logons = yes</b>
- </a>, then the default behavior is to enable the <i><tt>domain
- master</tt></i> parameter. If <i><tt>domain logons</tt></i> is
- not enabled (the default setting), then neither will <i><tt>domain
- master</tt></i> be enabled by default.</p><p>Default: <b>domain master = auto</b></p></dd><dt><span class="term"><a name="DONTDESCEND"></a>dont descend (S)</span></dt><dd><p>There are certain directories on some systems
- (e.g., the <tt>/proc</tt> tree under Linux) that are either not
- of interest to clients or are infinitely deep (recursive). This
- parameter allows you to specify a comma-delimited list of directories
- that the server should always show as empty.</p><p>Note that Samba can be very fussy about the exact format
- of the &quot;dont descend&quot; entries. For example you may need <tt>
- ./proc</tt> instead of just <tt>/proc</tt>.
- Experimentation is the best policy :-) </p><p>Default: <span class="emphasis"><em>none (i.e., all directories are OK
- to descend)</em></span></p><p>Example: <b>dont descend = /proc,/dev</b></p></dd><dt><span class="term"><a name="DOSCHARSET"></a>dos charset (G)</span></dt><dd><p>DOS SMB clients assume the server has
- the same charset as they do. This option specifies which
- charset Samba should talk to DOS clients.
- </p><p>The default depends on which charsets you have installed.
- Samba tries to use charset 850 but falls back to ASCII in
- case it is not available. Run <a href="testparm.1.html">testparm(1)</a> to check the default on your system.</p></dd><dt><span class="term"><a name="DOSFILEMODE"></a>dos filemode (S)</span></dt><dd><p> The default behavior in Samba is to provide
- UNIX-like behavior where only the owner of a file/directory is
- able to change the permissions on it. However, this behavior
- is often confusing to DOS/Windows users. Enabling this parameter
- allows a user who has write access to the file (by whatever
- means) to modify the permissions on it. Note that a user
- belonging to the group owning the file will not be allowed to
- change permissions if the group is only granted read access.
- Ownership of the file/directory is not changed, only the permissions
- are modified.</p><p>Default: <b>dos filemode = no</b></p></dd><dt><span class="term"><a name="DOSFILETIMERESOLUTION"></a>dos filetime resolution (S)</span></dt><dd><p>Under the DOS and Windows FAT filesystem, the finest
- granularity on time resolution is two seconds. Setting this parameter
- for a share causes Samba to round the reported time down to the
- nearest two second boundary when a query call that requires one second
- resolution is made to <a href="smbd.8.html">smbd(8)</a>.</p><p>This option is mainly used as a compatibility option for Visual
- C++ when used against Samba shares. If oplocks are enabled on a
- share, Visual C++ uses two different time reading calls to check if a
- file has changed since it was last read. One of these calls uses a
- one-second granularity, the other uses a two second granularity. As
- the two second call rounds any odd second down, then if the file has a
- timestamp of an odd number of seconds then the two timestamps will not
- match and Visual C++ will keep reporting the file has changed. Setting
- this option causes the two timestamps to match, and Visual C++ is
- happy.</p><p>Default: <b>dos filetime resolution = no</b></p></dd><dt><span class="term"><a name="DOSFILETIMES"></a>dos filetimes (S)</span></dt><dd><p>Under DOS and Windows, if a user can write to a
- file they can change the timestamp on it. Under POSIX semantics,
- only the owner of the file or root may change the timestamp. By
- default, Samba runs with POSIX semantics and refuses to change the
- timestamp on a file if the user <b>smbd</b> is acting
- on behalf of is not the file owner. Setting this option to <tt>
- yes</tt> allows DOS semantics and <a href="smbd.8.html">smbd(8)</a> will change the file
- timestamp as DOS requires.</p><p>Default: <b>dos filetimes = no</b></p></dd><dt><span class="term"><a name="ENCRYPTPASSWORDS"></a>encrypt passwords (G)</span></dt><dd><p>This boolean controls whether encrypted passwords
- will be negotiated with the client. Note that Windows NT 4.0 SP3 and
- above and also Windows 98 will by default expect encrypted passwords
- unless a registry entry is changed. To use encrypted passwords in
- Samba see the chapter &quot;User Database&quot; in the Samba HOWTO Collection. </p><p>In order for encrypted passwords to work correctly
- <a href="smbd.8.html">smbd(8)</a> must either
- have access to a local <a href="smbpasswd.5.html">smbpasswd(5)</a> file (see the <a href="smbpasswd.8.html">smbpasswd(8)</a> program for information on how to set up
- and maintain this file), or set the <a href="#SECURITY">security = [server|domain|ads]</a> parameter which
- causes <b>smbd</b> to authenticate against another
- server.</p><p>Default: <b>encrypt passwords = yes</b></p></dd><dt><span class="term"><a name="ENHANCEDBROWSING"></a>enhanced browsing (G)</span></dt><dd><p>This option enables a couple of enhancements to
- cross-subnet browse propagation that have been added in Samba
- but which are not standard in Microsoft implementations.
- </p><p>The first enhancement to browse propagation consists of a regular
- wildcard query to a Samba WINS server for all Domain Master Browsers,
- followed by a browse synchronization with each of the returned
- DMBs. The second enhancement consists of a regular randomised browse
- synchronization with all currently known DMBs.</p><p>You may wish to disable this option if you have a problem with empty
- workgroups not disappearing from browse lists. Due to the restrictions
- of the browse protocols these enhancements can cause a empty workgroup
- to stay around forever which can be annoying.</p><p>In general you should leave this option enabled as it makes
- cross-subnet browse propagation much more reliable.</p><p>Default: <b>enhanced browsing = yes</b></p></dd><dt><span class="term"><a name="ENUMPORTSCOMMAND"></a>enumports command (G)</span></dt><dd><p>The concept of a &quot;port&quot; is fairly foreign
- to UNIX hosts. Under Windows NT/2000 print servers, a port
- is associated with a port monitor and generally takes the form of
- a local port (i.e. LPT1:, COM1:, FILE:) or a remote port
- (i.e. LPD Port Monitor, etc...). By default, Samba has only one
- port defined--<tt>&quot;Samba Printer Port&quot;</tt>. Under
- Windows NT/2000, all printers must have a valid port name.
- If you wish to have a list of ports displayed (<b>smbd
- </b> does not use a port name for anything) other than
- the default <tt>&quot;Samba Printer Port&quot;</tt>, you
- can define <i><tt>enumports command</tt></i> to point to
- a program which should generate a list of ports, one per line,
- to standard output. This listing will then be used in response
- to the level 1 and 2 EnumPorts() RPC.</p><p>Default: <span class="emphasis"><em>no enumports command</em></span></p><p>Example: <b>enumports command = /usr/bin/listports</b></p></dd><dt><span class="term"><a name="EXEC"></a>exec (S)</span></dt><dd><p>This is a synonym for <a href="#PREEXEC">
- <i><tt>preexec</tt></i></a>.</p></dd><dt><span class="term"><a name="FAKEDIRECTORYCREATETIMES"></a>fake directory create times (S)</span></dt><dd><p>NTFS and Windows VFAT file systems keep a create
- time for all files and directories. This is not the same as the
- ctime - status change time - that Unix keeps, so Samba by default
- reports the earliest of the various times Unix does keep. Setting
- this parameter for a share causes Samba to always report midnight
- 1-1-1980 as the create time for directories.</p><p>This option is mainly used as a compatibility option for
- Visual C++ when used against Samba shares. Visual C++ generated
- makefiles have the object directory as a dependency for each object
- file, and a make rule to create the directory. Also, when NMAKE
- compares timestamps it uses the creation time when examining a
- directory. Thus the object directory will be created if it does not
- exist, but once it does exist it will always have an earlier
- timestamp than the object files it contains.</p><p>However, Unix time semantics mean that the create time
- reported by Samba will be updated whenever a file is created or
- or deleted in the directory. NMAKE finds all object files in
- the object directory. The timestamp of the last one built is then
- compared to the timestamp of the object directory. If the
- directory's timestamp if newer, then all object files
- will be rebuilt. Enabling this option
- ensures directories always predate their contents and an NMAKE build
- will proceed as expected.</p><p>Default: <b>fake directory create times = no</b></p></dd><dt><span class="term"><a name="FAKEOPLOCKS"></a>fake oplocks (S)</span></dt><dd><p>Oplocks are the way that SMB clients get permission
- from a server to locally cache file operations. If a server grants
- an oplock (opportunistic lock) then the client is free to assume
- that it is the only one accessing the file and it will aggressively
- cache file data. With some oplock types the client may even cache
- file open/close operations. This can give enormous performance benefits.
- </p><p>When you set <b>fake oplocks = yes</b>, <a href="smbd.8.html">smbd(8)</a> will
- always grant oplock requests no matter how many clients are using the file.</p><p>It is generally much better to use the real <a href="#OPLOCKS">
- <i><tt>oplocks</tt></i></a> support rather
- than this parameter.</p><p>If you enable this option on all read-only shares or
- shares that you know will only be accessed from one client at a
- time such as physically read-only media like CDROMs, you will see
- a big performance improvement on many operations. If you enable
- this option on shares where multiple clients may be accessing the
- files read-write at the same time you can get data corruption. Use
- this option carefully!</p><p>Default: <b>fake oplocks = no</b></p></dd><dt><span class="term"><a name="FOLLOWSYMLINKS"></a>follow symlinks (S)</span></dt><dd><p>This parameter allows the Samba administrator
- to stop <a href="smbd.8.html">smbd(8)</a> from following symbolic
- links in a particular share. Setting this
- parameter to <tt>no</tt> prevents any file or directory
- that is a symbolic link from being followed (the user will get an
- error). This option is very useful to stop users from adding a
- symbolic link to <tt>/etc/passwd</tt> in their home
- directory for instance. However it will slow filename lookups
- down slightly.</p><p>This option is enabled (i.e. <b>smbd</b> will
- follow symbolic links) by default.</p><p>Default: <b>follow symlinks = yes</b></p></dd><dt><span class="term"><a name="FORCECREATEMODE"></a>force create mode (S)</span></dt><dd><p>This parameter specifies a set of UNIX mode bit
- permissions that will <span class="emphasis"><em>always</em></span> be set on a
- file created by Samba. This is done by bitwise 'OR'ing these bits onto
- the mode bits of a file that is being created or having its
- permissions changed. The default for this parameter is (in octal)
- 000. The modes in this parameter are bitwise 'OR'ed onto the file
- mode after the mask set in the <i><tt>create mask</tt></i>
- parameter is applied.</p><p>See also the parameter <a href="#CREATEMASK"><i><tt>create
- mask</tt></i></a> for details on masking mode bits on files.</p><p>See also the <a href="#INHERITPERMISSIONS"><i><tt>inherit
- permissions</tt></i></a> parameter.</p><p>Default: <b>force create mode = 000</b></p><p>Example: <b>force create mode = 0755</b></p><p>would force all created files to have read and execute
- permissions set for 'group' and 'other' as well as the
- read/write/execute bits set for the 'user'.</p></dd><dt><span class="term"><a name="FORCEDIRECTORYMODE"></a>force directory mode (S)</span></dt><dd><p>This parameter specifies a set of UNIX mode bit
- permissions that will <span class="emphasis"><em>always</em></span> be set on a directory
- created by Samba. This is done by bitwise 'OR'ing these bits onto the
- mode bits of a directory that is being created. The default for this
- parameter is (in octal) 0000 which will not add any extra permission
- bits to a created directory. This operation is done after the mode
- mask in the parameter <i><tt>directory mask</tt></i> is
- applied.</p><p>See also the parameter <a href="#DIRECTORYMASK"><i><tt>
- directory mask</tt></i></a> for details on masking mode bits
- on created directories.</p><p>See also the <a href="#INHERITPERMISSIONS"><i><tt>
- inherit permissions</tt></i></a> parameter.</p><p>Default: <b>force directory mode = 000</b></p><p>Example: <b>force directory mode = 0755</b></p><p>would force all created directories to have read and execute
- permissions set for 'group' and 'other' as well as the
- read/write/execute bits set for the 'user'.</p></dd><dt><span class="term"><a name="FORCEDIRECTORYSECURITYMODE"></a>force directory security mode (S)</span></dt><dd><p>This parameter controls what UNIX permission bits
- can be modified when a Windows NT client is manipulating the UNIX
- permission on a directory using the native NT security dialog box.</p><p>This parameter is applied as a mask (OR'ed with) to the
- changed permission bits, thus forcing any bits in this mask that
- the user may have modified to be on. Essentially, one bits in this
- mask may be treated as a set of bits that, when modifying security
- on a directory, the user has always set to be 'on'.</p><p>If not set explicitly this parameter is 000, which
- allows a user to modify all the user/group/world permissions on a
- directory without restrictions.</p><p><span class="emphasis"><em>Note</em></span> that users who can access the
- Samba server through other means can easily bypass this restriction,
- so it is primarily useful for standalone &quot;appliance&quot; systems.
- Administrators of most normal systems will probably want to leave
- it set as 0000.</p><p>See also the <a href="#DIRECTORYSECURITYMASK"><i><tt>
- directory security mask</tt></i></a>, <a href="#SECURITYMASK">
- <i><tt>security mask</tt></i></a>,
- <a href="#FORCESECURITYMODE"><i><tt>force security mode
- </tt></i></a> parameters.</p><p>Default: <b>force directory security mode = 0</b></p><p>Example: <b>force directory security mode = 700</b></p></dd><dt><span class="term"><a name="FORCEGROUP"></a>force group (S)</span></dt><dd><p>This specifies a UNIX group name that will be
- assigned as the default primary group for all users connecting
- to this service. This is useful for sharing files by ensuring
- that all access to files on service will use the named group for
- their permissions checking. Thus, by assigning permissions for this
- group to the files and directories within this service the Samba
- administrator can restrict or allow sharing of these files.</p><p>In Samba 2.0.5 and above this parameter has extended
- functionality in the following way. If the group name listed here
- has a '+' character prepended to it then the current user accessing
- the share only has the primary group default assigned to this group
- if they are already assigned as a member of that group. This allows
- an administrator to decide that only users who are already in a
- particular group will create files with group ownership set to that
- group. This gives a finer granularity of ownership assignment. For
- example, the setting <tt>force group = +sys</tt> means
- that only users who are already in group sys will have their default
- primary group assigned to sys when accessing this Samba share. All
- other users will retain their ordinary primary group.</p><p>If the <a href="#FORCEUSER"><i><tt>force user</tt></i>
- </a> parameter is also set the group specified in
- <i><tt>force group</tt></i> will override the primary group
- set in <i><tt>force user</tt></i>.</p><p>See also <a href="#FORCEUSER"><i><tt>force user</tt></i></a>.</p><p>Default: <span class="emphasis"><em>no forced group</em></span></p><p>Example: <b>force group = agroup</b></p></dd><dt><span class="term"><a name="FORCESECURITYMODE"></a>force security mode (S)</span></dt><dd><p>This parameter controls what UNIX permission
- bits can be modified when a Windows NT client is manipulating
- the UNIX permission on a file using the native NT security dialog
- box.</p><p>This parameter is applied as a mask (OR'ed with) to the
- changed permission bits, thus forcing any bits in this mask that
- the user may have modified to be on. Essentially, one bits in this
- mask may be treated as a set of bits that, when modifying security
- on a file, the user has always set to be 'on'.</p><p>If not set explicitly this parameter is set to 0,
- and allows a user to modify all the user/group/world permissions on a file,
- with no restrictions.</p><p><span class="emphasis"><em>Note</em></span> that users who can access
- the Samba server through other means can easily bypass this restriction,
- so it is primarily useful for standalone &quot;appliance&quot; systems.
- Administrators of most normal systems will probably want to leave
- this set to 0000.</p><p>See also the <a href="#FORCEDIRECTORYSECURITYMODE"><i><tt>
- force directory security mode</tt></i></a>,
- <a href="#DIRECTORYSECURITYMASK"><i><tt>directory security
- mask</tt></i></a>, <a href="#SECURITYMASK"><i><tt>
- security mask</tt></i></a> parameters.</p><p>Default: <b>force security mode = 0</b></p><p>Example: <b>force security mode = 700</b></p></dd><dt><span class="term"><a name="FORCEUSER"></a>force user (S)</span></dt><dd><p>This specifies a UNIX user name that will be
- assigned as the default user for all users connecting to this service.
- This is useful for sharing files. You should also use it carefully
- as using it incorrectly can cause security problems.</p><p>This user name only gets used once a connection is established.
- Thus clients still need to connect as a valid user and supply a
- valid password. Once connected, all file operations will be performed
- as the &quot;forced user&quot;, no matter what username the client connected
- as. This can be very useful.</p><p>In Samba 2.0.5 and above this parameter also causes the
- primary group of the forced user to be used as the primary group
- for all file activity. Prior to 2.0.5 the primary group was left
- as the primary group of the connecting user (this was a bug).</p><p>See also <a href="#FORCEGROUP"><i><tt>force group</tt></i></a></p><p>Default: <span class="emphasis"><em>no forced user</em></span></p><p>Example: <b>force user = auser</b></p></dd><dt><span class="term"><a name="FSTYPE"></a>fstype (S)</span></dt><dd><p>This parameter allows the administrator to
- configure the string that specifies the type of filesystem a share
- is using that is reported by <a href="smbd.8.html">smbd(8)</a> when a client queries the filesystem type
- for a share. The default type is <tt>NTFS</tt> for
- compatibility with Windows NT but this can be changed to other
- strings such as <tt>Samba</tt> or <tt>FAT
- </tt> if required.</p><p>Default: <b>fstype = NTFS</b></p><p>Example: <b>fstype = Samba</b></p></dd><dt><span class="term"><a name="GETWDCACHE"></a>getwd cache (G)</span></dt><dd><p>This is a tuning option. When this is enabled a
- caching algorithm will be used to reduce the time taken for getwd()
- calls. This can have a significant impact on performance, especially
- when the <a href="#WIDELINKS"><i><tt>wide links</tt></i>
- </a> parameter is set to <tt>no</tt>.</p><p>Default: <b>getwd cache = yes</b></p></dd><dt><span class="term"><a name="GROUP"></a>group (S)</span></dt><dd><p>Synonym for <a href="#FORCEGROUP">
- <i><tt>force group</tt></i></a>.</p></dd><dt><span class="term"><a name="GUESTACCOUNT"></a>guest account (G,S)</span></dt><dd><p>This is a username which will be used for access
- to services which are specified as <a href="#GUESTOK"><i><tt>
- guest ok</tt></i></a> (see below). Whatever privileges this
- 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 &quot;ftp&quot; is often a good choice
- for this parameter. If a username is specified in a given service,
- the specified username overrides this one.
- </p><p>One some systems the default guest account &quot;nobody&quot; may not
- be able to print. Use another account in this case. You should test
- this by trying to log in as your guest user (perhaps by using the
- <b>su -</b> command) and trying to print using the
- system print command such as <b>lpr(1)</b> or <b>
- lp(1)</b>.</p><p>This parameter does not accept % macros, because
- many parts of the system require this value to be
- constant for correct operation.</p><p>Default: <span class="emphasis"><em>specified at compile time, usually &quot;nobody&quot;</em></span></p><p>Example: <b>guest account = ftp</b></p></dd><dt><span class="term"><a name="GUESTOK"></a>guest ok (S)</span></dt><dd><p>If this parameter is <tt>yes</tt> for
- a service, then no password is required to connect to the service.
- Privileges will be those of the <a href="#GUESTACCOUNT"><i><tt>
- guest account</tt></i></a>.</p><p>This paramater nullifies the benifits of setting
- <a href="#RESTRICTANONYMOUS"><i><tt>restrict
- anonymous</tt></i></a> = 2</p><p>See the section below on <a href="#SECURITY"><i><tt>
- security</tt></i></a> for more information about this option.
- </p><p>Default: <b>guest ok = no</b></p></dd><dt><span class="term"><a name="GUESTONLY"></a>guest only (S)</span></dt><dd><p>If this parameter is <tt>yes</tt> for
- a service, then only guest connections to the service are permitted.
- This parameter will have no effect if <a href="#GUESTOK">
- <i><tt>guest ok</tt></i></a> is not set for the service.</p><p>See the section below on <a href="#SECURITY"><i><tt>
- security</tt></i></a> for more information about this option.
- </p><p>Default: <b>guest only = no</b></p></dd><dt><span class="term"><a name="HIDEDOTFILES"></a>hide dot files (S)</span></dt><dd><p>This is a boolean parameter that controls whether
- files starting with a dot appear as hidden files.</p><p>Default: <b>hide dot files = yes</b></p></dd><dt><span class="term"><a name="HIDEFILES"></a>hide files (S)</span></dt><dd><p>This is a list of files or directories that are not
- visible but are accessible. The DOS 'hidden' attribute is applied
- to any files or directories that match.</p><p>Each entry in the list must be separated by a '/',
- which allows spaces to be included in the entry. '*'
- and '?' can be used to specify multiple files or directories
- as in DOS wildcards.</p><p>Each entry must be a Unix path, not a DOS path and must
- not include the Unix directory separator '/'.</p><p>Note that the case sensitivity option is applicable
- in hiding files.</p><p>Setting this parameter will affect the performance of Samba,
- as it will be forced to check all files and directories for a match
- as they are scanned.</p><p>See also <a href="#HIDEDOTFILES"><i><tt>hide
- dot files</tt></i></a>, <a href="#VETOFILES"><i><tt>
- veto files</tt></i></a> and <a href="#CASESENSITIVE">
- <i><tt>case sensitive</tt></i></a>.</p><p>Default: <span class="emphasis"><em>no file are hidden</em></span></p><p>Example: <b>hide files =
- /.*/DesktopFolderDB/TrashFor%m/resource.frk/</b></p><p>The above example is based on files that the Macintosh
- SMB client (DAVE) available from <a href="http://www.thursby.com" target="_top">
- Thursby</a> creates for internal use, and also still hides
- all files beginning with a dot.</p></dd><dt><span class="term"><a name="HIDELOCALUSERS"></a>hide local users (G)</span></dt><dd><p>This parameter toggles the hiding of local UNIX
- users (root, wheel, floppy, etc) from remote clients.</p><p>Default: <b>hide local users = no</b></p></dd><dt><span class="term"><a name="HIDESPECIALFILES"></a>hide special files (S)</span></dt><dd><p>This parameter prevents clients from seeing
- special files such as sockets, devices and fifo's in directory
- listings.
- </p><p>Default: <b>hide special files = no</b></p></dd><dt><span class="term"><a name="HIDEUNREADABLE"></a>hide unreadable (S)</span></dt><dd><p>This parameter prevents clients from seeing the
- existance of files that cannot be read. Defaults to off.</p><p>Default: <b>hide unreadable = no</b></p></dd><dt><span class="term"><a name="HIDEUNWRITEABLEFILES"></a>hide unwriteable files (S)</span></dt><dd><p>This parameter prevents clients from seeing
- the existance of files that cannot be written to. Defaults to off.
- Note that unwriteable directories are shown as usual.
- </p><p>Default: <b>hide unwriteable = no</b></p></dd><dt><span class="term"><a name="HOMEDIRMAP"></a>homedir map (G)</span></dt><dd><p>If<a href="#NISHOMEDIR"><i><tt>nis homedir
- </tt></i></a> is <tt>yes</tt>, and <a href="smbd.8.html">smbd(8)</a> is also acting
- as a Win95/98 <i><tt>logon server</tt></i> then this parameter
- specifies the NIS (or YP) map from which the server for the user's
- home directory should be extracted. At present, only the Sun
- auto.home map format is understood. The form of the map is:</p><p><b>username server:/some/file/system</b></p><p>and the program will extract the servername from before
- the first ':'. There should probably be a better parsing system
- that copes with different map formats and also Amd (another
- automounter) maps.</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>A working NIS client is required on
- the system for this option to work.</p></div><p>See also <a href="#NISHOMEDIR"><i><tt>nis homedir</tt></i>
- </a>, <a href="#DOMAINLOGONS"><i><tt>domain logons</tt></i>
- </a>.</p><p>Default: <b>homedir map = &lt;empty string&gt;</b></p><p>Example: <b>homedir map = amd.homedir</b></p></dd><dt><span class="term"><a name="HOSTMSDFS"></a>host msdfs (G)</span></dt><dd><p>This boolean parameter is only available
- if Samba has been configured and compiled with the <b>
- --with-msdfs</b> option. If set to <tt>yes</tt>,
- Samba will act as a Dfs server, and allow Dfs-aware clients
- to browse Dfs trees hosted on the server.</p><p>See also the <a href="#MSDFSROOT"><i><tt>
- msdfs root</tt></i></a> share level parameter. For
- more information on setting up a Dfs tree on Samba,
- refer to <a href="msdfs_setup.html" target="_top">msdfs_setup.html</a>.
- </p><p>Default: <b>host msdfs = no</b></p></dd><dt><span class="term"><a name="HOSTNAMELOOKUPS"></a>hostname lookups (G)</span></dt><dd><p>Specifies whether samba should use (expensive)
- hostname lookups or use the ip addresses instead. An example place
- where hostname lookups are currently used is when checking
- the <b>hosts deny</b> and <b>hosts allow</b>.
- </p><p>Default: <b>hostname lookups = yes</b></p><p>Example: <b>hostname lookups = no</b></p></dd><dt><span class="term"><a name="HOSTSALLOW"></a>hosts allow (S)</span></dt><dd><p>A synonym for this parameter is <i><tt>allow
- hosts</tt></i>.</p><p>This parameter is a comma, space, or tab delimited
- set of hosts which are permitted to access a service.</p><p>If specified in the [global] section then it will
- apply to all services, regardless of whether the individual
- service has a different setting.</p><p>You can specify the hosts by name or IP number. For
- example, you could restrict access to only the hosts on a
- Class C subnet with something like <b>allow hosts = 150.203.5.
- </b>. The full syntax of the list is described in the man
- page <tt>hosts_access(5)</tt>. Note that this man
- page may not be present on your system, so a brief description will
- be given here also.</p><p>Note that the localhost address 127.0.0.1 will always
- be allowed access unless specifically denied by a <a href="#HOSTSDENY">
- <i><tt>hosts deny</tt></i></a> option.</p><p>You can also specify hosts by network/netmask pairs and
- by netgroup names if your system supports netgroups. The
- <span class="emphasis"><em>EXCEPT</em></span> keyword can also be used to limit a
- wildcard list. The following examples may provide some help:</p><p>Example 1: allow all IPs in 150.203.*.*; except one</p><p><b>hosts allow = 150.203. EXCEPT 150.203.6.66</b></p><p>Example 2: allow hosts that match the given network/netmask</p><p><b>hosts allow = 150.203.15.0/255.255.255.0</b></p><p>Example 3: allow a couple of hosts</p><p><b>hosts allow = lapland, arvidsjaur</b></p><p>Example 4: allow only hosts in NIS netgroup &quot;foonet&quot;, but
- deny access from one particular host</p><p><b>hosts allow = @foonet</b></p><p><b>hosts deny = pirate</b></p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>Note that access still requires suitable user-level passwords.</p></div><p>See <a href="testparm.1.html">testparm(1)</a> for a way of testing your host access
- to see if it does what you expect.</p><p>Default: <span class="emphasis"><em>none (i.e., all hosts permitted access)</em></span></p><p>Example: <b>allow hosts = 150.203.5. myhost.mynet.edu.au</b></p></dd><dt><span class="term"><a name="HOSTSDENY"></a>hosts deny (S)</span></dt><dd><p>The opposite of <i><tt>hosts allow</tt></i>
- - hosts listed here are <span class="emphasis"><em>NOT</em></span> permitted access to
- services unless the specific services have their own lists to override
- this one. Where the lists conflict, the <i><tt>allow</tt></i>
- list takes precedence.</p><p>Default: <span class="emphasis"><em>none (i.e., no hosts specifically excluded)</em></span></p><p>Example: <b>hosts deny = 150.203.4. badhost.mynet.edu.au</b></p></dd><dt><span class="term"><a name="HOSTSEQUIV"></a>hosts equiv (G)</span></dt><dd><p>If this global parameter is a non-null string,
- it specifies the name of a file to read for the names of hosts
- and users who will be allowed access without specifying a password.
- </p><p>This is not be confused with <a href="#HOSTSALLOW">
- <i><tt>hosts allow</tt></i></a> which is about hosts
- access to services and is more useful for guest services. <i><tt>
- hosts equiv</tt></i> may be useful for NT clients which will
- not supply passwords to Samba.</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>The use of <i><tt>hosts equiv
- </tt></i> can be a major security hole. This is because you are
- trusting the PC to supply the correct username. It is very easy to
- get a PC to supply a false username. I recommend that the
- <i><tt>hosts equiv</tt></i> option be only used if you really
- know what you are doing, or perhaps on a home network where you trust
- your spouse and kids. And only if you <span class="emphasis"><em>really</em></span> trust
- them :-).</p></div><p>Default: <span class="emphasis"><em>no host equivalences</em></span></p><p>Example: <b>hosts equiv = /etc/hosts.equiv</b></p></dd><dt><span class="term"><a name="INCLUDE"></a>include (G)</span></dt><dd><p>This allows you to include one config file
- inside another. The file is included literally, as though typed
- in place.</p><p>It takes the standard substitutions, except <i><tt>%u
- </tt></i>, <i><tt>%P</tt></i> and <i><tt>%S</tt></i>.
- </p><p>Default: <span class="emphasis"><em>no file included</em></span></p><p>Example: <b>include = /usr/local/samba/lib/admin_smb.conf</b></p></dd><dt><span class="term"><a name="INHERITACLS"></a>inherit acls (S)</span></dt><dd><p>This parameter can be used to ensure that if default acls
- exist on parent directories, they are always honored when creating a
- subdirectory. The default behavior is to use the mode specified when
- creating the directory. Enabling this option sets the mode to 0777,
- thus guaranteeing that default directory acls are propagated.
- </p><p>Default: <b>inherit acls = no</b>
-</p></dd><dt><span class="term"><a name="INHERITPERMISSIONS"></a>inherit permissions (S)</span></dt><dd><p>The permissions on new files and directories
- are normally governed by <a href="#CREATEMASK"><i><tt>
- create mask</tt></i></a>, <a href="#DIRECTORYMASK">
- <i><tt>directory mask</tt></i></a>, <a href="#FORCECREATEMODE">
- <i><tt>force create mode</tt></i>
- </a> and <a href="#FORCEDIRECTORYMODE"><i><tt>force
- directory mode</tt></i></a> but the boolean inherit
- permissions parameter overrides this.</p><p>New directories inherit the mode of the parent directory,
- including bits such as setgid.</p><p>New files inherit their read/write bits from the parent
- directory. Their execute bits continue to be determined by
- <a href="#MAPARCHIVE"><i><tt>map archive</tt></i>
- </a>, <a href="#MAPHIDDEN"><i><tt>map hidden</tt></i>
- </a> and <a href="#MAPSYSTEM"><i><tt>map system</tt></i>
- </a> as usual.</p><p>Note that the setuid bit is <span class="emphasis"><em>never</em></span> set via
- inheritance (the code explicitly prohibits this).</p><p>This can be particularly useful on large systems with
- many users, perhaps several thousand, to allow a single [homes]
- share to be used flexibly by each user.</p><p>See also <a href="#CREATEMASK"><i><tt>create mask
- </tt></i></a>, <a href="#DIRECTORYMASK"><i><tt>
- directory mask</tt></i></a>, <a href="#FORCECREATEMODE">
- <i><tt>force create mode</tt></i></a> and <a href="#FORCEDIRECTORYMODE">
- <i><tt>force directory mode</tt></i>
- </a>.</p><p>Default: <b>inherit permissions = no</b></p></dd><dt><span class="term"><a name="INTERFACES"></a>interfaces (G)</span></dt><dd><p>This option allows you to override the default
- network interfaces list that Samba will use for browsing, name
- registration and other NBT traffic. By default Samba will query
- the kernel for the list of all active interfaces and use any
- interfaces except 127.0.0.1 that are broadcast capable.</p><p>The option takes a list of interface strings. Each string
- can be in any of the following forms:</p><div class="itemizedlist"><ul type="disc"><li><p>a network interface name (such as eth0).
- This may include shell-like wildcards so eth* will match
- any interface starting with the substring &quot;eth&quot;</p></li><li><p>an IP address. In this case the netmask is
- determined from the list of interfaces obtained from the
- kernel</p></li><li><p>an IP/mask pair. </p></li><li><p>a broadcast/mask pair.</p></li></ul></div><p>The &quot;mask&quot; parameters can either be a bit length (such
- as 24 for a C class network) or a full netmask in dotted
- decimal form.</p><p>The &quot;IP&quot; parameters above can either be a full dotted
- decimal IP address or a hostname which will be looked up via
- the OS's normal hostname resolution mechanisms.</p><p>For example, the following line:</p><p><b>interfaces = eth0 192.168.2.10/24 192.168.3.10/255.255.255.0</b></p><p>would configure three network interfaces corresponding
- to the eth0 device and IP addresses 192.168.2.10 and 192.168.3.10.
- The netmasks of the latter two interfaces would be set to 255.255.255.0.</p><p>See also <a href="#BINDINTERFACESONLY"><i><tt>bind
- interfaces only</tt></i></a>.</p><p>Default: <span class="emphasis"><em>all active interfaces except 127.0.0.1
- that are broadcast capable</em></span></p></dd><dt><span class="term"><a name="INVALIDUSERS"></a>invalid users (S)</span></dt><dd><p>This is a list of users that should not be allowed
- to login to this service. This is really a <span class="emphasis"><em>paranoid</em></span>
- check to absolutely ensure an improper setting does not breach
- your security.</p><p>A name starting with a '@' is interpreted as an NIS
- netgroup first (if your system supports NIS), and then as a UNIX
- group if the name was not found in the NIS netgroup database.</p><p>A name starting with '+' is interpreted only
- by looking in the UNIX group database. A name starting with
- '&amp;' is interpreted only by looking in the NIS netgroup database
- (this requires NIS to be working on your system). The characters
- '+' and '&amp;' may be used at the start of the name in either order
- so the value <i><tt>+&amp;group</tt></i> means check the
- UNIX group database, followed by the NIS netgroup database, and
- the value <i><tt>&amp;+group</tt></i> means check the NIS
- netgroup database, followed by the UNIX group database (the
- same as the '@' prefix).</p><p>The current servicename is substituted for <i><tt>%S</tt></i>.
- This is useful in the [homes] section.</p><p>See also <a href="#VALIDUSERS"><i><tt>valid users
- </tt></i></a>.</p><p>Default: <span class="emphasis"><em>no invalid users</em></span></p><p>Example: <b>invalid users = root fred admin @wheel</b></p></dd><dt><span class="term"><a name="KEEPALIVE"></a>keepalive (G)</span></dt><dd><p>The value of the parameter (an integer) represents
- the number of seconds between <i><tt>keepalive</tt></i>
- packets. If this parameter is zero, no keepalive packets will be
- sent. Keepalive packets, if sent, allow the server to tell whether
- a client is still present and responding.</p><p>Keepalives should, in general, not be needed if the socket
- being used has the SO_KEEPALIVE attribute set on it (see <a href="#SOCKETOPTIONS">
- <i><tt>socket options</tt></i></a>).
- Basically you should only use this option if you strike difficulties.</p><p>Default: <b>keepalive = 300</b></p><p>Example: <b>keepalive = 600</b></p></dd><dt><span class="term"><a name="KERNELOPLOCKS"></a>kernel oplocks (G)</span></dt><dd><p>For UNIXes that support kernel based <a href="#OPLOCKS">
- <i><tt>oplocks</tt></i></a>
- (currently only IRIX and the Linux 2.4 kernel), this parameter
- allows the use of them to be turned on or off.</p><p>Kernel oplocks support allows Samba <i><tt>oplocks
- </tt></i> to be broken whenever a local UNIX process or NFS operation
- accesses a file that <a href="smbd.8.html">smbd(8)</a> has oplocked. This allows complete
- data consistency between SMB/CIFS, NFS and local file access (and is
- a <span class="emphasis"><em>very</em></span> cool feature :-).</p><p>This parameter defaults to <tt>on</tt>, but is translated
- to a no-op on systems that no not have the necessary kernel support.
- You should never need to touch this parameter.</p><p>See also the <a href="#OPLOCKS"><i><tt>oplocks</tt></i>
- </a> and <a href="#LEVEL2OPLOCKS"><i><tt>level2 oplocks
- </tt></i></a> parameters.</p><p>Default: <b>kernel oplocks = yes</b></p></dd><dt><span class="term"><a name="LANMANAUTH"></a>lanman auth (G)</span></dt><dd><p>This parameter determines whether or not <a href="smbd.8.html">smbd(8)</a> will attempt to authenticate users
- using the LANMAN password hash. If disabled, only clients which support NT
- password hashes (e.g. Windows NT/2000 clients, smbclient, etc... but not
- Windows 95/98 or the MS DOS network client) will be able to connect to the Samba host.</p><p>Default : <b>lanman auth = yes</b></p></dd><dt><span class="term"><a name="LARGEREADWRITE"></a>large readwrite (G)</span></dt><dd><p>This parameter determines whether or not
- <a href="smbd.8.html">smbd(8)</a> supports the new 64k
- streaming read and write varient SMB requests introduced with
- Windows 2000. Note that due to Windows 2000 client redirector bugs
- this requires Samba to be running on a 64-bit capable operating
- system such as IRIX, Solaris or a Linux 2.4 kernel. Can improve
- performance by 10% with Windows 2000 clients. Defaults to on. Not as
- tested as some other Samba code paths.</p><p>Default: <b>large readwrite = yes</b></p></dd><dt><span class="term"><a name="LDAPADMINDN"></a>ldap admin dn (G)</span></dt><dd><p> The <i><tt>ldap admin dn</tt></i>
- defines the Distinguished Name (DN) name used by Samba to
- contact the ldap server when retreiving user account
- information. The <i><tt>ldap admin
- dn</tt></i> is used in conjunction with the admin dn password
- stored in the <tt>private/secrets.tdb</tt> file.
- See the <a href="smbpasswd.8.html">smbpasswd(8)</a> man page for more
- information on how to accmplish this.</p></dd><dt><span class="term"><a name="LDAPDELETEDN"></a>ldap delete dn (G)</span></dt><dd><p> This parameter specifies whether a delete
- operation in the ldapsam deletes the complete entry or only the attributes
- specific to Samba.
- </p><p>Default: <span class="emphasis"><em>ldap delete dn = no</em></span></p></dd><dt><span class="term"><a name="LDAPFILTER"></a>ldap filter (G)</span></dt><dd><p>This parameter specifies the RFC 2254 compliant LDAP search filter.
- The default is to match the login name with the <tt>uid</tt>
- attribute for all entries matching the <tt>sambaAccount</tt>
- objectclass. Note that this filter should only return one entry.
- </p><p>Default: <b>ldap filter = (&amp;(uid=%u)(objectclass=sambaAccount))</b></p></dd><dt><span class="term"><a name="LDAPMACHINESUFFIX"></a>ldap machine suffix (G)</span></dt><dd><p>It specifies where machines should be added to the ldap tree.</p><p>Default: <span class="emphasis"><em>none</em></span></p></dd><dt><span class="term"><a name="LDAPPASSWDSYNC"></a>ldap passwd sync (G)</span></dt><dd><p>This option is used to define whether
- or not Samba should sync the LDAP password with the NT
- and LM hashes for normal accounts (NOT for
- workstation, server or domain trusts) on a password
- change via SAMBA.
- </p><p>The <i><tt>ldap passwd
- sync</tt></i> can be set to one of three values: </p><div class="itemizedlist"><ul type="disc"><li><p><i><tt>Yes</tt></i> = Try
- to update the LDAP, NT and LM passwords and update the pwdLastSet time.</p></li><li><p><i><tt>No</tt></i> = Update NT and
- LM passwords and update the pwdLastSet time.</p></li><li><p><i><tt>Only</tt></i> = Only update
- the LDAP password and let the LDAP server do the rest.</p></li></ul></div><p>Default: <b>ldap passwd sync = no</b></p></dd><dt><span class="term"><a name="LDAPPORT"></a>ldap port (G)</span></dt><dd><p>This parameter is only available if Samba has been
- configure to include the <b>--with-ldapsam</b> option
- at compile time.</p><p>This option is used to control the tcp port number used to contact
- the <a href="#LDAPSERVER"><i><tt>ldap server</tt></i></a>.
- The default is to use the stand LDAPS port 636.</p><p>See Also: <a href="#LDAPSSL">ldap ssl</a></p><p>Default : <b>ldap port = 636 ; if ldap ssl = on</b></p><p>Default : <b>ldap port = 389 ; if ldap ssl = off</b></p></dd><dt><span class="term"><a name="LDAPSERVER"></a>ldap server (G)</span></dt><dd><p>This parameter is only available if Samba has been
- configure to include the <b>--with-ldapsam</b>
- option at compile time.</p><p>This parameter should contain the FQDN of the ldap directory
- server which should be queried to locate user account information.
- </p><p>Default : <b>ldap server = localhost</b></p></dd><dt><span class="term"><a name="LDAPSSL"></a>ldap ssl (G)</span></dt><dd><p>This option is used to define whether or not Samba should
- use SSL when connecting to the ldap server
- This is <span class="emphasis"><em>NOT</em></span> related to
- Samba's previous SSL support which was enabled by specifying the
- <b>--with-ssl</b> option to the <tt>configure</tt>
- script.</p><p>The <i><tt>ldap ssl</tt></i> can be set to one of three values:</p><div class="itemizedlist"><ul type="disc"><li><p><i><tt>Off</tt></i> = Never
- use SSL when querying the directory.</p></li><li><p><i><tt>Start_tls</tt></i> = Use
- the LDAPv3 StartTLS extended operation (RFC2830) for
- communicating with the directory server.</p></li><li><p><i><tt>On</tt></i> = Use SSL
- on the ldaps port when contacting the <i><tt>ldap server</tt></i>. Only available when the
- backwards-compatiblity <b>--with-ldapsam</b> option is specified
- to configure. See <a href="#PASSDBBACKEND"><i><tt>passdb backend</tt></i></a></p></li></ul></div><p>Default : <b>ldap ssl = start_tls</b></p></dd><dt><span class="term"><a name="LDAPSUFFIX"></a>ldap suffix (G)</span></dt><dd><p>Specifies where user and machine accounts are added to the
- tree. Can be overriden by <b>ldap user
- suffix</b> and <b>ldap machine
- suffix</b>. It also used as the base dn for all ldap
- searches. </p><p>Default: <span class="emphasis"><em>none</em></span></p></dd><dt><span class="term"><a name="LDAPTRUSTIDS"></a>ldap trust ids (G)</span></dt><dd><p>Normally, Samba validates each entry in the LDAP server
- against getpwnam(). This allows LDAP to be used for Samba with
- the unix system using NIS (for example) and also ensures that
- Samba does not present accounts that do not otherwise exist.
- </p><p>This option is used to disable this functionality, and
- instead to rely on the presence of the appropriate attributes
- in LDAP directly, which can result in a significant performance
- boost in some situations. Setting this option to yes effectivly
- assumes that the local machine is running <b>nss_ldap</b> against the same LDAP
- server.</p><p>Default: <b>ldap trust ids = No</b></p></dd><dt><span class="term"><a name="LDAPUSERSUFFIX"></a>ldap user suffix (G)</span></dt><dd><p>It specifies where users are added to the tree.</p><p>Default: <span class="emphasis"><em>none</em></span></p></dd><dt><span class="term"><a name="LEVEL2OPLOCKS"></a>level2 oplocks (S)</span></dt><dd><p>This parameter controls whether Samba supports
- level2 (read-only) oplocks on a share.</p><p>Level2, or read-only oplocks allow Windows NT clients
- that have an oplock on a file to downgrade from a read-write oplock
- to a read-only oplock once a second client opens the file (instead
- 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 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
- writes to the file all clients are notified (no reply is needed
- or waited for) and told to break their oplocks to &quot;none&quot; and
- delete any read-ahead caches.</p><p>It is recommended that this parameter be turned on to
- speed access to shared executables.</p><p>For more discussions on level2 oplocks see the CIFS spec.</p><p>Currently, if <a href="#KERNELOPLOCKS"><i><tt>kernel
- oplocks</tt></i></a> are supported then level2 oplocks are
- not granted (even if this parameter is set to <tt>yes</tt>).
- Note also, the <a href="#OPLOCKS"><i><tt>oplocks</tt></i>
- </a> parameter must be set to <tt>yes</tt> on this share in order for
- this parameter to have any effect.</p><p>See also the <a href="#OPLOCKS"><i><tt>oplocks</tt></i>
- </a> and <a href="#OPLOCKS"><i><tt>kernel oplocks</tt></i>
- </a> parameters.</p><p>Default: <b>level2 oplocks = yes</b></p></dd><dt><span class="term"><a name="LMANNOUNCE"></a>lm announce (G)</span></dt><dd><p>This parameter determines if <a href="nmbd.8.html">nmbd(8)</a> will produce Lanman announce
- broadcasts that are needed by OS/2 clients in order for them to see
- the Samba server in their browse list. This parameter can have three
- values, <tt>yes</tt>, <tt>no</tt>, or
- <tt>auto</tt>. The default is <tt>auto</tt>.
- If set to <tt>no</tt> Samba will never produce these
- broadcasts. If set to <tt>yes</tt> Samba will produce
- Lanman announce broadcasts at a frequency set by the parameter
- <i><tt>lm interval</tt></i>. If set to <tt>auto</tt>
- Samba will not send Lanman announce broadcasts by default but will
- listen for them. If it hears such a broadcast on the wire it will
- then start sending them at a frequency set by the parameter
- <i><tt>lm interval</tt></i>.</p><p>See also <a href="#LMINTERVAL"><i><tt>lm interval</tt></i></a>.</p><p>Default: <b>lm announce = auto</b></p><p>Example: <b>lm announce = yes</b></p></dd><dt><span class="term"><a name="LMINTERVAL"></a>lm interval (G)</span></dt><dd><p>If Samba is set to produce Lanman announce
- broadcasts needed by OS/2 clients (see the <a href="#LMANNOUNCE">
- <i><tt>lm announce</tt></i></a> parameter) then this
- parameter defines the frequency in seconds with which they will be
- made. If this is set to zero then no Lanman announcements will be
- made despite the setting of the <i><tt>lm announce</tt></i>
- parameter.</p><p>See also <a href="#LMANNOUNCE"><i><tt>lm announce</tt></i></a>.</p><p>Default: <b>lm interval = 60</b></p><p>Example: <b>lm interval = 120</b></p></dd><dt><span class="term"><a name="LOADPRINTERS"></a>load printers (G)</span></dt><dd><p>A boolean variable that controls whether all
- printers in the printcap will be loaded for browsing by default.
- See the <a href="#PRINTERSSECT" title="The [printers] section">printers</a> section for
- more details.</p><p>Default: <b>load printers = yes</b></p></dd><dt><span class="term"><a name="LOCALMASTER"></a>local master (G)</span></dt><dd><p>This option allows <a href="nmbd.8.html">nmbd(8)</a> to try and become a local master browser
- on a subnet. If set to <tt>no</tt> then <b>
- nmbd</b> will not attempt to become a local master browser
- on a subnet and will also lose in all browsing elections. By
- default this value is set to <tt>yes</tt>. Setting this value to
- <tt>yes</tt> doesn't mean that Samba will <span class="emphasis"><em>become</em></span> the
- local master browser on a subnet, just that <b>nmbd</b>
- will <span class="emphasis"><em>participate</em></span> in elections for local master browser.</p><p>Setting this value to <tt>no</tt> will cause <b>nmbd</b> <span class="emphasis"><em>never</em></span> to become a local
- master browser.</p><p>Default: <b>local master = yes</b></p></dd><dt><span class="term"><a name="LOCKDIRECTORY"></a>lock directory (G)</span></dt><dd><p>This option specifies the directory where lock
- files will be placed. The lock files are used to implement the
- <a href="#MAXCONNECTIONS"><i><tt>max connections</tt></i>
- </a> option.</p><p>Default: <b>lock directory = ${prefix}/var/locks</b></p><p>Example: <b>lock directory = /var/run/samba/locks</b></p></dd><dt><span class="term"><a name="LOCKDIR"></a>lock dir (G)</span></dt><dd><p>Synonym for <a href="#LOCKDIRECTORY"><i><tt>
- lock directory</tt></i></a>.
-</p></dd><dt><span class="term"><a name="LOCKING"></a>locking (S)</span></dt><dd><p>This controls whether or not locking will be
- performed by the server in response to lock requests from the
- client.</p><p>If <b>locking = no</b>, all lock and unlock
- requests will appear to succeed and all lock queries will report
- that the file in question is available for locking.</p><p>If <b>locking = yes</b>, real locking will be performed
- by the server.</p><p>This option <span class="emphasis"><em>may</em></span> be useful for read-only
- filesystems which <span class="emphasis"><em>may</em></span> not need locking (such as
- CDROM drives), although setting this parameter of <tt>no</tt>
- is not really recommended even in this case.</p><p>Be careful about disabling locking either globally or in a
- specific service, as lack of locking may result in data corruption.
- You should never need to set this parameter.</p><p>Default: <b>locking = yes</b></p></dd><dt><span class="term"><a name="LOCKSPINCOUNT"></a>lock spin count (G)</span></dt><dd><p>This parameter controls the number of times
- that smbd should attempt to gain a byte range lock on the
- behalf of a client request. Experiments have shown that
- Windows 2k servers do not reply with a failure if the lock
- could not be immediately granted, but try a few more times
- in case the lock could later be aquired. This behavior
- is used to support PC database formats such as MS Access
- and FoxPro.
- </p><p>Default: <b>lock spin count = 2</b></p></dd><dt><span class="term"><a name="LOCKSPINTIME"></a>lock spin time (G)</span></dt><dd><p>The time in microseconds that smbd should
- pause before attempting to gain a failed lock. See
- <a href="#LOCKSPINCOUNT"><i><tt>lock spin
- count</tt></i></a> for more details.</p><p>Default: <b>lock spin time = 10</b></p></dd><dt><span class="term"><a name="LOGFILE"></a>log file (G)</span></dt><dd><p>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
- you to have separate log files for each user or machine.</p><p>Example: <b>log file = /usr/local/samba/var/log.%m</b></p></dd><dt><span class="term"><a name="LOGLEVEL"></a>log level (G)</span></dt><dd><p>The value of the parameter (a astring) allows
- the debug level (logging level) to be specified in the
- <tt>smb.conf</tt> file. This parameter has been
- extended since the 2.2.x series, now it allow to specify the debug
- level for multiple debug classes. This is to give greater
- flexibility in the configuration of the system.</p><p>The default will be the log level specified on
- the command line or level zero if none was specified.</p><p>Example: <b>log level = 3 passdb:5 auth:10 winbind:2</b></p></dd><dt><span class="term"><a name="LOGONDRIVE"></a>logon drive (G)</span></dt><dd><p>This parameter specifies the local path to
- which the home directory will be connected (see <a href="#LOGONHOME">
- <i><tt>logon home</tt></i></a>)
- and is only used by NT Workstations. </p><p>Note that this option is only useful if Samba is set up as a
- logon server.</p><p>Default: <b>logon drive = z:</b></p><p>Example: <b>logon drive = h:</b></p></dd><dt><span class="term"><a name="LOGONHOME"></a>logon home (G)</span></dt><dd><p>This parameter specifies the home directory
- location when a Win95/98 or NT Workstation logs into a Samba PDC.
- It allows you to do </p><p><tt>C:\&gt;</tt>
- <b><tt>NET USE H: /HOME</tt></b>
- </p><p>from a command prompt, for example.</p><p>This option takes the standard substitutions, allowing
- you to have separate logon scripts for each user or machine.</p><p>This parameter can be used with Win9X workstations to ensure
- that roaming profiles are stored in a subdirectory of the user's
- home directory. This is done in the following way:</p><p><b>logon home = \\%N\%U\profile</b></p><p>This tells Samba to return the above string, with
- substitutions made when a client requests the info, generally
- in a NetUserGetInfo request. Win9X clients truncate the info to
- \\server\share when a user does <b>net use /home</b>
- but use the whole string when dealing with profiles.</p><p>Note that in prior versions of Samba, the <a href="#LOGONPATH">
- <i><tt>logon path</tt></i></a> was returned rather than
- <i><tt>logon home</tt></i>. This broke <b>net use /home</b> but allowed profiles outside the home directory.
- The current implementation is correct, and can be used for profiles if you use
- the above trick.</p><p>This option is only useful if Samba is set up as a logon
- server.</p><p>Default: <b>logon home = &quot;\\%N\%U&quot;</b></p><p>Example: <b>logon home = &quot;\\remote_smb_server\%U&quot;</b></p></dd><dt><span class="term"><a name="LOGONPATH"></a>logon path (G)</span></dt><dd><p>This parameter specifies the home directory
- where roaming profiles (NTuser.dat etc files for Windows NT) are
- stored. Contrary to previous versions of these manual pages, it has
- nothing to do with Win 9X roaming profiles. To find out how to
- handle roaming profiles for Win 9X system, see the <a href="#LOGONHOME">
- <i><tt>logon home</tt></i></a> parameter.</p><p>This option takes the standard substitutions, allowing you
- to have separate logon scripts for each user or machine. It also
- specifies the directory from which the &quot;Application Data&quot;,
- (<tt>desktop</tt>, <tt>start menu</tt>,
- <tt>network neighborhood</tt>, <tt>programs</tt>
- and other folders, and their contents, are loaded and displayed on
- your Windows NT client.</p><p>The share and the path must be readable by the user for
- the preferences and directories to be loaded onto the Windows NT
- client. The share must be writeable when the user logs in for the first
- time, in order that the Windows NT client can create the NTuser.dat
- and other directories.</p><p>Thereafter, the directories and any of the contents can,
- if required, be made read-only. It is not advisable that the
- NTuser.dat file be made read-only - rename it to NTuser.man to
- achieve the desired effect (a <span class="emphasis"><em>MAN</em></span>datory
- profile). </p><p>Windows clients can sometimes maintain a connection to
- the [homes] share, even though there is no user logged in.
- Therefore, it is vital that the logon path does not include a
- reference to the homes share (i.e. setting this parameter to
- \%N\%U\profile_path will cause problems).</p><p>This option takes the standard substitutions, allowing
- you to have separate logon scripts for each user or machine.</p><p>Note that this option is only useful if Samba is set up
- as a logon server.</p><p>Default: <b>logon path = \\%N\%U\profile</b></p><p>Example: <b>logon path = \\PROFILESERVER\PROFILE\%U</b></p></dd><dt><span class="term"><a name="LOGONSCRIPT"></a>logon script (G)</span></dt><dd><p>This parameter specifies the batch file (.bat) or
- NT command file (.cmd) to be downloaded and run on a machine when
- a user successfully logs in. The file must contain the DOS
- style CR/LF line endings. Using a DOS-style editor to create the
- file is recommended.</p><p>The script must be a relative path to the [netlogon]
- service. If the [netlogon] service specifies a <a href="#PATH">
- <i><tt>path</tt></i></a> of <tt>/usr/local/samba/netlogon</tt>, and <b>logon script = STARTUP.BAT</b>, then
- the file that will be downloaded is:</p><p><tt>/usr/local/samba/netlogon/STARTUP.BAT</tt></p><p>The contents of the batch file are entirely your choice. A
- suggested command would be to add <b>NET TIME \\SERVER /SET
- /YES</b>, to force every machine to synchronize clocks with
- the same time server. Another use would be to add <b>NET USE
- U: \\SERVER\UTILS</b> for commonly used utilities, or <b>
- NET USE Q: \\SERVER\ISO9001_QA</b> for example.</p><p>Note that it is particularly important not to allow write
- access to the [netlogon] share, or to grant users write permission
- on the batch files in a secure environment, as this would allow
- the batch files to be arbitrarily modified and security to be
- breached.</p><p>This option takes the standard substitutions, allowing you
- to have separate logon scripts for each user or machine.</p><p>This option is only useful if Samba is set up as a logon
- server.</p><p>Default: <span class="emphasis"><em>no logon script defined</em></span></p><p>Example: <b>logon script = scripts\%U.bat</b></p></dd><dt><span class="term"><a name="LPPAUSECOMMAND"></a>lppause command (S)</span></dt><dd><p>This parameter specifies the command to be
- executed on the server host in order to stop printing or spooling
- a specific print job.</p><p>This command should be a program or script which takes
- a printer name and job number to pause the print job. One way
- of implementing this is by using job priorities, where jobs
- having a too low priority won't be sent to the printer.</p><p>If a <i><tt>%p</tt></i> is given then the printer name
- is put in its place. A <i><tt>%j</tt></i> is replaced with
- the job number (an integer). On HPUX (see <i><tt>printing=hpux
- </tt></i>), if the <i><tt>-p%p</tt></i> option is added
- to the lpq command, the job will show up with the correct status, i.e.
- if the job priority is lower than the set fence priority it will
- have the PAUSED status, whereas if the priority is equal or higher it
- will have the SPOOLED or PRINTING status.</p><p>Note that it is good practice to include the absolute path
- in the lppause command as the PATH may not be available to the server.</p><p>See also the <a href="#PRINTING"><i><tt>printing
- </tt></i></a> parameter.</p><p>Default: Currently no default value is given to
- this string, unless the value of the <i><tt>printing</tt></i>
- parameter is <tt>SYSV</tt>, in which case the default is :</p><p><b>lp -i %p-%j -H hold</b></p><p>or if the value of the <i><tt>printing</tt></i> parameter
- is <tt>SOFTQ</tt>, then the default is:</p><p><b>qstat -s -j%j -h</b></p><p>Example for HPUX: <b>lppause command = /usr/bin/lpalt %p-%j -p0</b></p></dd><dt><span class="term"><a name="LPQCACHETIME"></a>lpq cache time (G)</span></dt><dd><p>This controls how long lpq info will be cached
- for to prevent the <b>lpq</b> command being called too
- often. A separate cache is kept for each variation of the <b>
- lpq</b> command used by the system, so if you use different
- <b>lpq</b> commands for different users then they won't
- share cache information.</p><p>The cache files are stored in <tt>/tmp/lpq.xxxx</tt>
- where xxxx is a hash of the <b>lpq</b> command in use.</p><p>The default is 10 seconds, meaning that the cached results
- of a previous identical <b>lpq</b> command will be used
- if the cached data is less than 10 seconds old. A large value may
- be advisable if your <b>lpq</b> command is very slow.</p><p>A value of 0 will disable caching completely.</p><p>See also the <a href="#PRINTING"><i><tt>printing</tt></i></a> parameter.</p><p>Default: <b>lpq cache time = 10</b></p><p>Example: <b>lpq cache time = 30</b></p></dd><dt><span class="term"><a name="LPQCOMMAND"></a>lpq command (S)</span></dt><dd><p>This parameter specifies the command to be
- executed on the server host in order to obtain <b>lpq
- </b>-style printer status information.</p><p>This command should be a program or script which
- takes a printer name as its only parameter and outputs printer
- status information.</p><p>Currently nine styles of printer status information
- are supported; BSD, AIX, LPRNG, PLP, SYSV, HPUX, QNX, CUPS, and SOFTQ.
- This covers most UNIX systems. You control which type is expected
- using the <i><tt>printing =</tt></i> option.</p><p>Some clients (notably Windows for Workgroups) may not
- correctly send the connection number for the printer they are
- requesting status information about. To get around this, the
- server reports on the first printer service connected to by the
- client. This only happens if the connection number sent is invalid.</p><p>If a <i><tt>%p</tt></i> is given then the printer name
- is put in its place. Otherwise it is placed at the end of the
- command.</p><p>Note that it is good practice to include the absolute path
- in the <i><tt>lpq command</tt></i> as the <tt>$PATH
- </tt> may not be available to the server. When compiled with
- the CUPS libraries, no <i><tt>lpq command</tt></i> is
- needed because smbd will make a library call to obtain the
- print queue listing.</p><p>See also the <a href="#PRINTING"><i><tt>printing
- </tt></i></a> parameter.</p><p>Default: <span class="emphasis"><em>depends on the setting of <i><tt>
- printing</tt></i></em></span></p><p>Example: <b>lpq command = /usr/bin/lpq -P%p</b></p></dd><dt><span class="term"><a name="LPRESUMECOMMAND"></a>lpresume command (S)</span></dt><dd><p>This parameter specifies the command to be
- executed on the server host in order to restart or continue
- printing or spooling a specific print job.</p><p>This command should be a program or script which takes
- a printer name and job number to resume the print job. See
- also the <a href="#LPPAUSECOMMAND"><i><tt>lppause command
- </tt></i></a> parameter.</p><p>If a <i><tt>%p</tt></i> is given then the printer name
- is put in its place. A <i><tt>%j</tt></i> is replaced with
- the job number (an integer).</p><p>Note that it is good practice to include the absolute path
- in the <i><tt>lpresume command</tt></i> as the PATH may not
- be available to the server.</p><p>See also the <a href="#PRINTING"><i><tt>printing
- </tt></i></a> parameter.</p><p>Default: Currently no default value is given
- to this string, unless the value of the <i><tt>printing</tt></i>
- parameter is <tt>SYSV</tt>, in which case the default is :</p><p><b>lp -i %p-%j -H resume</b></p><p>or if the value of the <i><tt>printing</tt></i> parameter
- is <tt>SOFTQ</tt>, then the default is:</p><p><b>qstat -s -j%j -r</b></p><p>Example for HPUX: <b>lpresume command = /usr/bin/lpalt %p-%j -p2</b></p></dd><dt><span class="term"><a name="LPRMCOMMAND"></a>lprm command (S)</span></dt><dd><p>This parameter specifies the command to be
- executed on the server host in order to delete a print job.</p><p>This command should be a program or script which takes
- a printer name and job number, and deletes the print job.</p><p>If a <i><tt>%p</tt></i> is given then the printer name
- is put in its place. A <i><tt>%j</tt></i> is replaced with
- the job number (an integer).</p><p>Note that it is good practice to include the absolute
- path in the <i><tt>lprm command</tt></i> as the PATH may not be
- available to the server.</p><p>See also the <a href="#PRINTING"><i><tt>printing
- </tt></i></a> parameter.</p><p>Default: <span class="emphasis"><em>depends on the setting of <i><tt>printing
- </tt></i></em></span></p><p>Example 1: <b>lprm command = /usr/bin/lprm -P%p %j</b></p><p>Example 2: <b>lprm command = /usr/bin/cancel %p-%j</b></p></dd><dt><span class="term"><a name="MACHINEPASSWORDTIMEOUT"></a>machine password timeout (G)</span></dt><dd><p>If a Samba server is a member of a Windows
- NT Domain (see the <a href="#SECURITYEQUALSDOMAIN">security = domain</a>)
- parameter) then periodically a running <a href="smbd.8.html" target="_top">
- smbd(8)</a> process will try and change the MACHINE ACCOUNT
- PASSWORD stored in the TDB called <tt>private/secrets.tdb
- </tt>. This parameter specifies how often this password
- will be changed, in seconds. The default is one week (expressed in
- seconds), the same as a Windows NT Domain member server.</p><p>See also <a href="smbpasswd.8.html">smbpasswd(8)</a>, and the <a href="#SECURITYEQUALSDOMAIN">
- security = domain</a>) parameter.</p><p>Default: <b>machine password timeout = 604800</b></p></dd><dt><span class="term"><a name="MAGICOUTPUT"></a>magic output (S)</span></dt><dd><p>This parameter specifies the name of a file
- which will contain output created by a magic script (see the
- <a href="#MAGICSCRIPT"><i><tt>magic script</tt></i></a>
- parameter below).</p><p>Warning: If two clients use the same <i><tt>magic script
- </tt></i> in the same directory the output file content
- is undefined.</p><p>Default: <b>magic output = &lt;magic script name&gt;.out</b></p><p>Example: <b>magic output = myfile.txt</b></p></dd><dt><span class="term"><a name="MAGICSCRIPT"></a>magic script (S)</span></dt><dd><p>This parameter specifies the name of a file which,
- if opened, will be executed by the server when the file is closed.
- This allows a UNIX script to be sent to the Samba host and
- executed on behalf of the connected user.</p><p>Scripts executed in this way will be deleted upon
- completion assuming that the user has the appropriate level
- of privilege and the file permissions allow the deletion.</p><p>If the script generates output, output will be sent to
- the file specified by the <a href="#MAGICOUTPUT"><i><tt>
- magic output</tt></i></a> parameter (see above).</p><p>Note that some shells are unable to interpret scripts
- containing CR/LF instead of CR as
- the end-of-line marker. Magic scripts must be executable
- <span class="emphasis"><em>as is</em></span> on the host, which for some hosts and
- some shells will require filtering at the DOS end.</p><p>Magic scripts are <span class="emphasis"><em>EXPERIMENTAL</em></span> and
- should <span class="emphasis"><em>NOT</em></span> be relied upon.</p><p>Default: <span class="emphasis"><em>None. Magic scripts disabled.</em></span></p><p>Example: <b>magic script = user.csh</b></p></dd><dt><span class="term"><a name="MANGLECASE"></a>mangle case (S)</span></dt><dd><p>See the section on <a href="#NAMEMANGLINGSECT" title="NAME MANGLING">NAME MANGLING</a></p><p>Default: <b>mangle case = no</b></p></dd><dt><span class="term"><a name="MANGLEDMAP"></a>mangled map (S)</span></dt><dd><p>This is for those who want to directly map UNIX
- file names which cannot be represented on Windows/DOS. The mangling
- of names is not always what is needed. In particular you may have
- documents with file extensions that differ between DOS and UNIX.
- For example, under UNIX it is common to use <tt>.html</tt>
- for HTML files, whereas under Windows/DOS <tt>.htm</tt>
- is more commonly used.</p><p>So to map <tt>html</tt> to <tt>htm</tt>
- you would use:</p><p><b>mangled map = (*.html *.htm)</b></p><p>One very useful case is to remove the annoying <tt>;1
- </tt> off the ends of filenames on some CDROMs (only visible
- under some UNIXes). To do this use a map of (*;1 *;).</p><p>Default: <span class="emphasis"><em>no mangled map</em></span></p><p>Example: <b>mangled map = (*;1 *;)</b></p></dd><dt><span class="term"><a name="MANGLEDNAMES"></a>mangled names (S)</span></dt><dd><p>This controls whether non-DOS names under UNIX
- should be mapped to DOS-compatible names (&quot;mangled&quot;) and made visible,
- or whether non-DOS names should simply be ignored.</p><p>See the section on <a href="#NAMEMANGLINGSECT" title="NAME MANGLING">NAME MANGLING</a> for
- details on how to control the mangling process.</p><p>If mangling is used then the mangling algorithm is as follows:</p><div class="itemizedlist"><ul type="disc"><li><p>The first (up to) five alphanumeric characters
+ </P
+></LI
+></UL
+><P
+> This parameter is only used to remove file shares. To delete printer shares,
+ see the <A
+HREF="#DELETEPRINTERCOMMAND"
+><TT
+CLASS="PARAMETER"
+><I
+>deleteprinter
+ command</I
+></TT
+></A
+>.
+ </P
+><P
+> See also <A
+HREF="#ADDSHARECOMMAND"
+><TT
+CLASS="PARAMETER"
+><I
+>add share
+ command</I
+></TT
+></A
+>, <A
+HREF="#CHANGESHARECOMMAND"
+><TT
+CLASS="PARAMETER"
+><I
+>change
+ share command</I
+></TT
+></A
+>.
+ </P
+><P
+>Default: <I
+CLASS="EMPHASIS"
+>none</I
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>delete share command = /usr/local/bin/delshare</B
+></P
+></DD
+><DT
+><A
+NAME="DELETEUSERSCRIPT"
+></A
+>delete user script (G)</DT
+><DD
+><P
+>This is the full pathname to a script that will
+ be run by <A
+HREF="smbd.8.html"
+TARGET="_top"
+><B
+CLASS="COMMAND"
+>smbd(8)</B
+></A
+>
+ when managing user's with remote RPC (NT) tools.
+ </P
+><P
+>This script is called when a remote client removes a user
+ from the server, normally using 'User Manager for Domains' or
+ <B
+CLASS="COMMAND"
+>rpcclient</B
+>.
+ </P
+><P
+>This script should delete the given UNIX username.
+ </P
+><P
+>Default: <B
+CLASS="COMMAND"
+>delete user script = &#60;empty string&#62;
+ </B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>delete user script = /usr/local/samba/bin/del_user
+ %u</B
+></P
+></DD
+><DT
+><A
+NAME="DELETEUSERFROMGROUPSCRIPT"
+></A
+>delete user from group script (G)</DT
+><DD
+><P
+>Full path to the script that will be called when
+ a user is removed from a group using the Windows NT domain administration
+ tools. It will be run by <A
+HREF="smbd.8.html"
+TARGET="_top"
+>smbd(8)</A
+>
+ <I
+CLASS="EMPHASIS"
+>AS ROOT</I
+>. Any <TT
+CLASS="PARAMETER"
+><I
+>%g</I
+></TT
+> will be
+ replaced with the group name and any <TT
+CLASS="PARAMETER"
+><I
+>%u</I
+></TT
+> will
+ be replaced with the user name.
+ </P
+><P
+>Default: <B
+CLASS="COMMAND"
+>delete user from group script = </B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>delete user from group script = /usr/sbin/deluser %u %g</B
+></P
+></DD
+><DT
+><A
+NAME="DELETEVETOFILES"
+></A
+>delete veto files (S)</DT
+><DD
+><P
+>This option is used when Samba is attempting to
+ delete a directory that contains one or more vetoed directories
+ (see the <A
+HREF="#VETOFILES"
+><TT
+CLASS="PARAMETER"
+><I
+>veto files</I
+></TT
+></A
+>
+ option). If this option is set to <TT
+CLASS="CONSTANT"
+>no</TT
+> (the default) then if a vetoed
+ directory contains any non-vetoed files or directories then the
+ directory delete will fail. This is usually what you want.</P
+><P
+>If this option is set to <TT
+CLASS="CONSTANT"
+>yes</TT
+>, then Samba
+ will attempt to recursively delete any files and directories within
+ the vetoed directory. This can be useful for integration with file
+ serving systems such as NetAtalk which create meta-files within
+ directories you might normally veto DOS/Windows users from seeing
+ (e.g. <TT
+CLASS="FILENAME"
+>.AppleDouble</TT
+>)</P
+><P
+>Setting <B
+CLASS="COMMAND"
+>delete veto files = yes</B
+> allows these
+ directories to be transparently deleted when the parent directory
+ is deleted (so long as the user has permissions to do so).</P
+><P
+>See also the <A
+HREF="#VETOFILES"
+><TT
+CLASS="PARAMETER"
+><I
+>veto
+ files</I
+></TT
+></A
+> parameter.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>delete veto files = no</B
+></P
+></DD
+><DT
+><A
+NAME="DENYHOSTS"
+></A
+>deny hosts (S)</DT
+><DD
+><P
+>Synonym for <A
+HREF="#HOSTSDENY"
+><TT
+CLASS="PARAMETER"
+><I
+>hosts
+ deny</I
+></TT
+></A
+>.</P
+></DD
+><DT
+><A
+NAME="DFREECOMMAND"
+></A
+>dfree command (G)</DT
+><DD
+><P
+>The <TT
+CLASS="PARAMETER"
+><I
+>dfree command</I
+></TT
+> setting should
+ only be used on systems where a problem occurs with the internal
+ disk space calculations. This has been known to happen with Ultrix,
+ but may occur with other operating systems. The symptom that was
+ seen was an error of "Abort Retry Ignore" at the end of each
+ directory listing.</P
+><P
+>This setting allows the replacement of the internal routines to
+ calculate the total disk space and amount available with an external
+ routine. The example below gives a possible script that might fulfill
+ this function.</P
+><P
+>The external program will be passed a single parameter indicating
+ a directory in the filesystem being queried. This will typically consist
+ of the string <TT
+CLASS="FILENAME"
+>./</TT
+>. The script should return two
+ 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
+><P
+>Note: Your script should <I
+CLASS="EMPHASIS"
+>NOT</I
+> be setuid or
+ setgid and should be owned by (and writeable only by) root!</P
+><P
+>Default: <I
+CLASS="EMPHASIS"
+>By default internal routines for
+ determining the disk capacity and remaining space will be used.
+ </I
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>dfree command = /usr/local/samba/bin/dfree
+ </B
+></P
+><P
+>Where the script dfree (which must be made executable) could be:</P
+><P
+><TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="90%"
+><TR
+><TD
+><PRE
+CLASS="PROGRAMLISTING"
+>
+ #!/bin/sh
+ df $1 | tail -1 | awk '{print $2" "$4}'
+ </PRE
+></TD
+></TR
+></TABLE
+></P
+><P
+>or perhaps (on Sys V based systems):</P
+><P
+><TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="90%"
+><TR
+><TD
+><PRE
+CLASS="PROGRAMLISTING"
+>
+ #!/bin/sh
+ /usr/bin/df -k $1 | tail -1 | awk '{print $3" "$5}'
+ </PRE
+></TD
+></TR
+></TABLE
+></P
+><P
+>Note that you may have to replace the command names
+ with full path names on some systems.</P
+></DD
+><DT
+><A
+NAME="DIRECTORY"
+></A
+>directory (S)</DT
+><DD
+><P
+>Synonym for <A
+HREF="#PATH"
+><TT
+CLASS="PARAMETER"
+><I
+>path
+ </I
+></TT
+></A
+>.</P
+></DD
+><DT
+><A
+NAME="DIRECTORYMASK"
+></A
+>directory mask (S)</DT
+><DD
+><P
+>This parameter is the octal modes which are
+ used when converting DOS modes to UNIX modes when creating UNIX
+ directories.</P
+><P
+>When a directory is created, the necessary permissions are
+ calculated according to the mapping from DOS modes to UNIX permissions,
+ and the resulting UNIX mode is then bit-wise 'AND'ed with this
+ parameter. This parameter may be thought of as a bit-wise MASK for
+ the UNIX modes of a directory. Any bit <I
+CLASS="EMPHASIS"
+>not</I
+> set
+ here will be removed from the modes set on a directory when it is
+ created.</P
+><P
+>The default value of this parameter removes the 'group'
+ and 'other' write bits from the UNIX mode, allowing only the
+ user who owns the directory to modify it.</P
+><P
+>Following this Samba will bit-wise 'OR' the UNIX mode
+ created from this parameter with the value of the <A
+HREF="#FORCEDIRECTORYMODE"
+><TT
+CLASS="PARAMETER"
+><I
+>force directory mode
+ </I
+></TT
+></A
+> parameter. This parameter is set to 000 by
+ default (i.e. no extra mode bits are added).</P
+><P
+>Note that this parameter does not apply to permissions
+ set by Windows NT/2000 ACL editors. If the administrator wishes to enforce
+ a mask on access control lists also, they need to set the <A
+HREF="#DIRECTORYSECURITYMASK"
+><TT
+CLASS="PARAMETER"
+><I
+>directory security mask</I
+></TT
+></A
+>.</P
+><P
+>See the <A
+HREF="#FORCEDIRECTORYMODE"
+><TT
+CLASS="PARAMETER"
+><I
+>force
+ directory mode</I
+></TT
+></A
+> parameter to cause particular mode
+ bits to always be set on created directories.</P
+><P
+>See also the <A
+HREF="#CREATEMODE"
+><TT
+CLASS="PARAMETER"
+><I
+>create mode
+ </I
+></TT
+></A
+> parameter for masking mode bits on created files,
+ and the <A
+HREF="#DIRECTORYSECURITYMASK"
+><TT
+CLASS="PARAMETER"
+><I
+>directory
+ security mask</I
+></TT
+></A
+> parameter.</P
+><P
+>Also refer to the <A
+HREF="#INHERITPERMISSIONS"
+><TT
+CLASS="PARAMETER"
+><I
+> inherit permissions</I
+></TT
+></A
+> parameter.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>directory mask = 0755</B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>directory mask = 0775</B
+></P
+></DD
+><DT
+><A
+NAME="DIRECTORYMODE"
+></A
+>directory mode (S)</DT
+><DD
+><P
+>Synonym for <A
+HREF="#DIRECTORYMASK"
+><TT
+CLASS="PARAMETER"
+><I
+> directory mask</I
+></TT
+></A
+></P
+></DD
+><DT
+><A
+NAME="DIRECTORYSECURITYMASK"
+></A
+>directory security mask (S)</DT
+><DD
+><P
+>This parameter controls what UNIX permission bits
+ can be modified when a Windows NT client is manipulating the UNIX
+ permission on a directory using the native NT security dialog
+ box.</P
+><P
+>This parameter is applied as a mask (AND'ed with) to
+ the changed permission bits, thus preventing any bits not in
+ this mask from being modified. Essentially, zero bits in this
+ mask may be treated as a set of bits the user is not allowed
+ to change.</P
+><P
+>If not set explicitly this parameter is set to 0777
+ meaning a user is allowed to modify all the user/group/world
+ permissions on a directory.</P
+><P
+><I
+CLASS="EMPHASIS"
+>Note</I
+> that users who can access the
+ Samba server through other means can easily bypass this restriction,
+ so it is primarily useful for standalone "appliance" systems.
+ Administrators of most normal systems will probably want to leave
+ it as the default of <TT
+CLASS="CONSTANT"
+>0777</TT
+>.</P
+><P
+>See also the <A
+HREF="#FORCEDIRECTORYSECURITYMODE"
+><TT
+CLASS="PARAMETER"
+><I
+> force directory security mode</I
+></TT
+></A
+>, <A
+HREF="#SECURITYMASK"
+><TT
+CLASS="PARAMETER"
+><I
+>security mask</I
+></TT
+></A
+>,
+ <A
+HREF="#FORCESECURITYMODE"
+><TT
+CLASS="PARAMETER"
+><I
+>force security mode
+ </I
+></TT
+></A
+> parameters.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>directory security mask = 0777</B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>directory security mask = 0700</B
+></P
+></DD
+><DT
+><A
+NAME="DISABLENETBIOS"
+></A
+>disable netbios (G)</DT
+><DD
+><P
+>Enabling this parameter will disable netbios support
+ in Samba. Netbios is the only available form of browsing in
+ all windows versions except for 2000 and XP. </P
+><P
+>Note that clients that only support netbios won't be able to
+ see your samba server when netbios support is disabled.
+ </P
+><P
+>Default: <B
+CLASS="COMMAND"
+>disable netbios = no</B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>disable netbios = yes</B
+></P
+></DD
+><DT
+><A
+NAME="DISABLESPOOLSS"
+></A
+>disable spoolss (G)</DT
+><DD
+><P
+>Enabling this parameter will disable Samba's support
+ for the SPOOLSS set of MS-RPC's and will yield identical behavior
+ as Samba 2.0.x. Windows NT/2000 clients will downgrade to using
+ Lanman style printing commands. Windows 9x/ME will be uneffected by
+ the parameter. However, this will also disable the ability to upload
+ printer drivers to a Samba server via the Windows NT Add Printer
+ Wizard or by using the NT printer properties dialog window. It will
+ also disable the capability of Windows NT/2000 clients to download
+ print drivers from the Samba host upon demand.
+ <I
+CLASS="EMPHASIS"
+>Be very careful about enabling this parameter.</I
+>
+ </P
+><P
+>See also <A
+HREF="#USECLIENTDRIVER"
+>use client driver</A
+>
+ </P
+><P
+>Default : <B
+CLASS="COMMAND"
+>disable spoolss = no</B
+></P
+></DD
+><DT
+><A
+NAME="DISPLAYCHARSET"
+></A
+>display charset (G)</DT
+><DD
+><P
+>Specifies the charset that samba will use
+ to print messages to stdout and stderr and SWAT will use.
+ Should generally be the same as the <B
+CLASS="COMMAND"
+>unix charset</B
+>.
+ </P
+><P
+>Default: <B
+CLASS="COMMAND"
+>display charset = ASCII</B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>display charset = UTF8</B
+></P
+></DD
+><DT
+><A
+NAME="DNSPROXY"
+></A
+>dns proxy (G)</DT
+><DD
+><P
+>Specifies that <A
+HREF="nmbd.8.html"
+TARGET="_top"
+>nmbd(8)</A
+>
+ when acting as a WINS server and finding that a NetBIOS name has not
+ been registered, should treat the NetBIOS name word-for-word as a DNS
+ name and do a lookup with the DNS server for that name on behalf of
+ the name-querying client.</P
+><P
+>Note that the maximum length for a NetBIOS name is 15
+ characters, so the DNS name (or DNS alias) can likewise only be
+ 15 characters, maximum.</P
+><P
+><B
+CLASS="COMMAND"
+>nmbd</B
+> spawns a second copy of itself to do the
+ DNS name lookup requests, as doing a name lookup is a blocking
+ action.</P
+><P
+>See also the parameter <A
+HREF="#WINSSUPPORT"
+><TT
+CLASS="PARAMETER"
+><I
+> wins support</I
+></TT
+></A
+>.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>dns proxy = yes</B
+></P
+></DD
+><DT
+><A
+NAME="DOMAINLOGONS"
+></A
+>domain logons (G)</DT
+><DD
+><P
+>If set to <TT
+CLASS="CONSTANT"
+>yes</TT
+>, the Samba server will serve
+ Windows 95/98 Domain logons for the <A
+HREF="#WORKGROUP"
+> <TT
+CLASS="PARAMETER"
+><I
+>workgroup</I
+></TT
+></A
+> it is in. Samba 2.2
+ has limited capability to act as a domain controller for Windows
+ NT 4 Domains. For more details on setting up this feature see
+ the Samba-PDC-HOWTO included in the <TT
+CLASS="FILENAME"
+>htmldocs/</TT
+>
+ directory shipped with the source code.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>domain logons = no</B
+></P
+></DD
+><DT
+><A
+NAME="DOMAINMASTER"
+></A
+>domain master (G)</DT
+><DD
+><P
+>Tell <A
+HREF="nmbd.8.html"
+TARGET="_top"
+><B
+CLASS="COMMAND"
+> nmbd(8)</B
+></A
+> to enable WAN-wide browse list
+ collation. Setting this option causes <B
+CLASS="COMMAND"
+>nmbd</B
+> to
+ claim a special domain specific NetBIOS name that identifies
+ it as a domain master browser for its given <A
+HREF="#WORKGROUP"
+> <TT
+CLASS="PARAMETER"
+><I
+>workgroup</I
+></TT
+></A
+>. Local master browsers
+ in the same <TT
+CLASS="PARAMETER"
+><I
+>workgroup</I
+></TT
+> on broadcast-isolated
+ subnets will give this <B
+CLASS="COMMAND"
+>nmbd</B
+> their local browse lists,
+ and then ask <A
+HREF="smbd.8.html"
+TARGET="_top"
+><B
+CLASS="COMMAND"
+>smbd(8)</B
+></A
+>
+ for a complete copy of the browse list for the whole wide area
+ network. Browser clients will then contact their local master browser,
+ and will receive the domain-wide browse list, instead of just the list
+ for their broadcast-isolated subnet.</P
+><P
+>Note that Windows NT Primary Domain Controllers expect to be
+ able to claim this <TT
+CLASS="PARAMETER"
+><I
+>workgroup</I
+></TT
+> specific special
+ NetBIOS name that identifies them as domain master browsers for
+ that <TT
+CLASS="PARAMETER"
+><I
+>workgroup</I
+></TT
+> by default (i.e. there is no
+ way to prevent a Windows NT PDC from attempting to do this). This
+ means that if this parameter is set and <B
+CLASS="COMMAND"
+>nmbd</B
+> claims
+ the special name for a <TT
+CLASS="PARAMETER"
+><I
+>workgroup</I
+></TT
+> before a Windows
+ NT PDC is able to do so then cross subnet browsing will behave
+ strangely and may fail.</P
+><P
+>If <A
+HREF="#DOMAINLOGONS"
+><B
+CLASS="COMMAND"
+>domain logons = yes</B
+>
+ </A
+>, then the default behavior is to enable the <TT
+CLASS="PARAMETER"
+><I
+>domain
+ master</I
+></TT
+> parameter. If <TT
+CLASS="PARAMETER"
+><I
+>domain logons</I
+></TT
+> is
+ not enabled (the default setting), then neither will <TT
+CLASS="PARAMETER"
+><I
+>domain
+ master</I
+></TT
+> be enabled by default.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>domain master = auto</B
+></P
+></DD
+><DT
+><A
+NAME="DONTDESCEND"
+></A
+>dont descend (S)</DT
+><DD
+><P
+>There are certain directories on some systems
+ (e.g., the <TT
+CLASS="FILENAME"
+>/proc</TT
+> tree under Linux) that are either not
+ of interest to clients or are infinitely deep (recursive). This
+ parameter allows you to specify a comma-delimited list of directories
+ that the server should always show as empty.</P
+><P
+>Note that Samba can be very fussy about the exact format
+ of the "dont descend" entries. For example you may need <TT
+CLASS="FILENAME"
+> ./proc</TT
+> instead of just <TT
+CLASS="FILENAME"
+>/proc</TT
+>.
+ Experimentation is the best policy :-) </P
+><P
+>Default: <I
+CLASS="EMPHASIS"
+>none (i.e., all directories are OK
+ to descend)</I
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>dont descend = /proc,/dev</B
+></P
+></DD
+><DT
+><A
+NAME="DOSCHARSET"
+></A
+>dos charset (G)</DT
+><DD
+><P
+>DOS SMB clients assume the server has
+ the same charset as they do. This option specifies which
+ charset Samba should talk to DOS clients.
+ </P
+><P
+>The default depends on which charsets you have instaled.
+ Samba tries to use charset 850 but falls back to ASCII in
+ case it is not available. Run <A
+HREF="testparm.1.html"
+TARGET="_top"
+>testparm(1)
+ </A
+> to check the default on your system.
+ </P
+></DD
+><DT
+><A
+NAME="DOSFILEMODE"
+></A
+>dos filemode (S)</DT
+><DD
+><P
+> The default behavior in Samba is to provide
+ UNIX-like behavior where only the owner of a file/directory is
+ able to change the permissions on it. However, this behavior
+ is often confusing to DOS/Windows users. Enabling this parameter
+ allows a user who has write access to the file (by whatever
+ means) to modify the permissions on it. Note that a user
+ belonging to the group owning the file will not be allowed to
+ change permissions if the group is only granted read access.
+ Ownership of the file/directory is not changed, only the permissions
+ are modified.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>dos filemode = no</B
+></P
+></DD
+><DT
+><A
+NAME="DOSFILETIMERESOLUTION"
+></A
+>dos filetime resolution (S)</DT
+><DD
+><P
+>Under the DOS and Windows FAT filesystem, the finest
+ granularity on time resolution is two seconds. Setting this parameter
+ for a share causes Samba to round the reported time down to the
+ nearest two second boundary when a query call that requires one second
+ resolution is made to <A
+HREF="smbd.8.html"
+TARGET="_top"
+><B
+CLASS="COMMAND"
+>smbd(8)</B
+>
+ </A
+>.</P
+><P
+>This option is mainly used as a compatibility option for Visual
+ C++ when used against Samba shares. If oplocks are enabled on a
+ share, Visual C++ uses two different time reading calls to check if a
+ file has changed since it was last read. One of these calls uses a
+ one-second granularity, the other uses a two second granularity. As
+ the two second call rounds any odd second down, then if the file has a
+ timestamp of an odd number of seconds then the two timestamps will not
+ match and Visual C++ will keep reporting the file has changed. Setting
+ this option causes the two timestamps to match, and Visual C++ is
+ happy.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>dos filetime resolution = no</B
+></P
+></DD
+><DT
+><A
+NAME="DOSFILETIMES"
+></A
+>dos filetimes (S)</DT
+><DD
+><P
+>Under DOS and Windows, if a user can write to a
+ file they can change the timestamp on it. Under POSIX semantics,
+ only the owner of the file or root may change the timestamp. By
+ default, Samba runs with POSIX semantics and refuses to change the
+ timestamp on a file if the user <B
+CLASS="COMMAND"
+>smbd</B
+> is acting
+ on behalf of is not the file owner. Setting this option to <TT
+CLASS="CONSTANT"
+> yes</TT
+> allows DOS semantics and <A
+HREF="smbd.8.html"
+TARGET="_top"
+>smbd</A
+> will change the file
+ timestamp as DOS requires.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>dos filetimes = no</B
+></P
+></DD
+><DT
+><A
+NAME="ENCRYPTPASSWORDS"
+></A
+>encrypt passwords (G)</DT
+><DD
+><P
+>This boolean controls whether encrypted passwords
+ will be negotiated with the client. Note that Windows NT 4.0 SP3 and
+ above and also Windows 98 will by default expect encrypted passwords
+ unless a registry entry is changed. To use encrypted passwords in
+ Samba see the file ENCRYPTION.txt in the Samba documentation
+ directory <TT
+CLASS="FILENAME"
+>docs/</TT
+> shipped with the source code.</P
+><P
+>In order for encrypted passwords to work correctly
+ <A
+HREF="smbd.8.html"
+TARGET="_top"
+><B
+CLASS="COMMAND"
+>smbd(8)</B
+></A
+> must either
+ have access to a local <A
+HREF="smbpasswd.5.html"
+TARGET="_top"
+><TT
+CLASS="FILENAME"
+>smbpasswd(5)
+ </TT
+></A
+> file (see the <A
+HREF="smbpasswd.8.html"
+TARGET="_top"
+><B
+CLASS="COMMAND"
+> smbpasswd(8)</B
+></A
+> program for information on how to set up
+ and maintain this file), or set the <A
+HREF="#SECURITY"
+>security = [server|domain|ads]</A
+> parameter which
+ causes <B
+CLASS="COMMAND"
+>smbd</B
+> to authenticate against another
+ server.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>encrypt passwords = yes</B
+></P
+></DD
+><DT
+><A
+NAME="ENHANCEDBROWSING"
+></A
+>enhanced browsing (G)</DT
+><DD
+><P
+>This option enables a couple of enhancements to
+ cross-subnet browse propagation that have been added in Samba
+ but which are not standard in Microsoft implementations.
+ </P
+><P
+>The first enhancement to browse propagation consists of a regular
+ wildcard query to a Samba WINS server for all Domain Master Browsers,
+ followed by a browse synchronization with each of the returned
+ DMBs. The second enhancement consists of a regular randomised browse
+ synchronization with all currently known DMBs.</P
+><P
+>You may wish to disable this option if you have a problem with empty
+ workgroups not disappearing from browse lists. Due to the restrictions
+ of the browse protocols these enhancements can cause a empty workgroup
+ to stay around forever which can be annoying.</P
+><P
+>In general you should leave this option enabled as it makes
+ cross-subnet browse propagation much more reliable.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>enhanced browsing = yes</B
+></P
+></DD
+><DT
+><A
+NAME="ENUMPORTSCOMMAND"
+></A
+>enumports command (G)</DT
+><DD
+><P
+>The concept of a "port" is fairly foreign
+ to UNIX hosts. Under Windows NT/2000 print servers, a port
+ is associated with a port monitor and generally takes the form of
+ a local port (i.e. LPT1:, COM1:, FILE:) or a remote port
+ (i.e. LPD Port Monitor, etc...). By default, Samba has only one
+ port defined--<TT
+CLASS="CONSTANT"
+>"Samba Printer Port"</TT
+>. Under
+ Windows NT/2000, all printers must have a valid port name.
+ If you wish to have a list of ports displayed (<B
+CLASS="COMMAND"
+>smbd
+ </B
+> does not use a port name for anything) other than
+ the default <TT
+CLASS="CONSTANT"
+>"Samba Printer Port"</TT
+>, you
+ can define <TT
+CLASS="PARAMETER"
+><I
+>enumports command</I
+></TT
+> to point to
+ a program which should generate a list of ports, one per line,
+ to standard output. This listing will then be used in response
+ to the level 1 and 2 EnumPorts() RPC.</P
+><P
+>Default: <I
+CLASS="EMPHASIS"
+>no enumports command</I
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>enumports command = /usr/bin/listports
+ </B
+></P
+></DD
+><DT
+><A
+NAME="EXEC"
+></A
+>exec (S)</DT
+><DD
+><P
+>This is a synonym for <A
+HREF="#PREEXEC"
+> <TT
+CLASS="PARAMETER"
+><I
+>preexec</I
+></TT
+></A
+>.</P
+></DD
+><DT
+><A
+NAME="FAKEDIRECTORYCREATETIMES"
+></A
+>fake directory create times (S)</DT
+><DD
+><P
+>NTFS and Windows VFAT file systems keep a create
+ time for all files and directories. This is not the same as the
+ ctime - status change time - that Unix keeps, so Samba by default
+ reports the earliest of the various times Unix does keep. Setting
+ this parameter for a share causes Samba to always report midnight
+ 1-1-1980 as the create time for directories.</P
+><P
+>This option is mainly used as a compatibility option for
+ Visual C++ when used against Samba shares. Visual C++ generated
+ makefiles have the object directory as a dependency for each object
+ file, and a make rule to create the directory. Also, when NMAKE
+ compares timestamps it uses the creation time when examining a
+ directory. Thus the object directory will be created if it does not
+ exist, but once it does exist it will always have an earlier
+ timestamp than the object files it contains.</P
+><P
+>However, Unix time semantics mean that the create time
+ reported by Samba will be updated whenever a file is created or
+ or deleted in the directory. NMAKE finds all object files in
+ the object directory. The timestamp of the last one built is then
+ compared to the timestamp of the object directory. If the
+ directory's timestamp if newer, then all object files
+ will be rebuilt. Enabling this option
+ ensures directories always predate their contents and an NMAKE build
+ will proceed as expected.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>fake directory create times = no</B
+></P
+></DD
+><DT
+><A
+NAME="FAKEOPLOCKS"
+></A
+>fake oplocks (S)</DT
+><DD
+><P
+>Oplocks are the way that SMB clients get permission
+ from a server to locally cache file operations. If a server grants
+ an oplock (opportunistic lock) then the client is free to assume
+ that it is the only one accessing the file and it will aggressively
+ cache file data. With some oplock types the client may even cache
+ file open/close operations. This can give enormous performance benefits.
+ </P
+><P
+>When you set <B
+CLASS="COMMAND"
+>fake oplocks = yes</B
+>, <A
+HREF="smbd.8.html"
+TARGET="_top"
+><B
+CLASS="COMMAND"
+>smbd(8)</B
+></A
+> will
+ always grant oplock requests no matter how many clients are using
+ the file.</P
+><P
+>It is generally much better to use the real <A
+HREF="#OPLOCKS"
+><TT
+CLASS="PARAMETER"
+><I
+>oplocks</I
+></TT
+></A
+> support rather
+ than this parameter.</P
+><P
+>If you enable this option on all read-only shares or
+ shares that you know will only be accessed from one client at a
+ time such as physically read-only media like CDROMs, you will see
+ a big performance improvement on many operations. If you enable
+ this option on shares where multiple clients may be accessing the
+ files read-write at the same time you can get data corruption. Use
+ this option carefully!</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>fake oplocks = no</B
+></P
+></DD
+><DT
+><A
+NAME="FOLLOWSYMLINKS"
+></A
+>follow symlinks (S)</DT
+><DD
+><P
+>This parameter allows the Samba administrator
+ to stop <A
+HREF="smbd.8.html"
+TARGET="_top"
+><B
+CLASS="COMMAND"
+>smbd(8)</B
+></A
+>
+ from following symbolic links in a particular share. Setting this
+ parameter to <TT
+CLASS="CONSTANT"
+>no</TT
+> prevents any file or directory
+ that is a symbolic link from being followed (the user will get an
+ error). This option is very useful to stop users from adding a
+ symbolic link to <TT
+CLASS="FILENAME"
+>/etc/passwd</TT
+> in their home
+ directory for instance. However it will slow filename lookups
+ down slightly.</P
+><P
+>This option is enabled (i.e. <B
+CLASS="COMMAND"
+>smbd</B
+> will
+ follow symbolic links) by default.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>follow symlinks = yes</B
+></P
+></DD
+><DT
+><A
+NAME="FORCECREATEMODE"
+></A
+>force create mode (S)</DT
+><DD
+><P
+>This parameter specifies a set of UNIX mode bit
+ permissions that will <I
+CLASS="EMPHASIS"
+>always</I
+> be set on a
+ file created by Samba. This is done by bitwise 'OR'ing these bits onto
+ the mode bits of a file that is being created or having its
+ permissions changed. The default for this parameter is (in octal)
+ 000. The modes in this parameter are bitwise 'OR'ed onto the file
+ mode after the mask set in the <TT
+CLASS="PARAMETER"
+><I
+>create mask</I
+></TT
+>
+ parameter is applied.</P
+><P
+>See also the parameter <A
+HREF="#CREATEMASK"
+><TT
+CLASS="PARAMETER"
+><I
+>create
+ mask</I
+></TT
+></A
+> for details on masking mode bits on files.</P
+><P
+>See also the <A
+HREF="#INHERITPERMISSIONS"
+><TT
+CLASS="PARAMETER"
+><I
+>inherit
+ permissions</I
+></TT
+></A
+> parameter.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>force create mode = 000</B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>force create mode = 0755</B
+></P
+><P
+>would force all created files to have read and execute
+ permissions set for 'group' and 'other' as well as the
+ read/write/execute bits set for the 'user'.</P
+></DD
+><DT
+><A
+NAME="FORCEDIRECTORYMODE"
+></A
+>force directory mode (S)</DT
+><DD
+><P
+>This parameter specifies a set of UNIX mode bit
+ permissions that will <I
+CLASS="EMPHASIS"
+>always</I
+> be set on a directory
+ created by Samba. This is done by bitwise 'OR'ing these bits onto the
+ mode bits of a directory that is being created. The default for this
+ parameter is (in octal) 0000 which will not add any extra permission
+ bits to a created directory. This operation is done after the mode
+ mask in the parameter <TT
+CLASS="PARAMETER"
+><I
+>directory mask</I
+></TT
+> is
+ applied.</P
+><P
+>See also the parameter <A
+HREF="#DIRECTORYMASK"
+><TT
+CLASS="PARAMETER"
+><I
+> directory mask</I
+></TT
+></A
+> for details on masking mode bits
+ on created directories.</P
+><P
+>See also the <A
+HREF="#INHERITPERMISSIONS"
+><TT
+CLASS="PARAMETER"
+><I
+> inherit permissions</I
+></TT
+></A
+> parameter.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>force directory mode = 000</B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>force directory mode = 0755</B
+></P
+><P
+>would force all created directories to have read and execute
+ permissions set for 'group' and 'other' as well as the
+ read/write/execute bits set for the 'user'.</P
+></DD
+><DT
+><A
+NAME="FORCEDIRECTORYSECURITYMODE"
+></A
+>force directory security mode (S)</DT
+><DD
+><P
+>This parameter controls what UNIX permission bits
+ can be modified when a Windows NT client is manipulating the UNIX
+ permission on a directory using the native NT security dialog box.</P
+><P
+>This parameter is applied as a mask (OR'ed with) to the
+ changed permission bits, thus forcing any bits in this mask that
+ the user may have modified to be on. Essentially, one bits in this
+ mask may be treated as a set of bits that, when modifying security
+ on a directory, the user has always set to be 'on'.</P
+><P
+>If not set explicitly this parameter is 000, which
+ allows a user to modify all the user/group/world permissions on a
+ directory without restrictions.</P
+><P
+><I
+CLASS="EMPHASIS"
+>Note</I
+> that users who can access the
+ Samba server through other means can easily bypass this restriction,
+ so it is primarily useful for standalone "appliance" systems.
+ Administrators of most normal systems will probably want to leave
+ it set as 0000.</P
+><P
+>See also the <A
+HREF="#DIRECTORYSECURITYMASK"
+><TT
+CLASS="PARAMETER"
+><I
+> directory security mask</I
+></TT
+></A
+>, <A
+HREF="#SECURITYMASK"
+> <TT
+CLASS="PARAMETER"
+><I
+>security mask</I
+></TT
+></A
+>,
+ <A
+HREF="#FORCESECURITYMODE"
+><TT
+CLASS="PARAMETER"
+><I
+>force security mode
+ </I
+></TT
+></A
+> parameters.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>force directory security mode = 0</B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>force directory security mode = 700</B
+></P
+></DD
+><DT
+><A
+NAME="FORCEGROUP"
+></A
+>force group (S)</DT
+><DD
+><P
+>This specifies a UNIX group name that will be
+ assigned as the default primary group for all users connecting
+ to this service. This is useful for sharing files by ensuring
+ that all access to files on service will use the named group for
+ their permissions checking. Thus, by assigning permissions for this
+ group to the files and directories within this service the Samba
+ administrator can restrict or allow sharing of these files.</P
+><P
+>In Samba 2.0.5 and above this parameter has extended
+ functionality in the following way. If the group name listed here
+ has a '+' character prepended to it then the current user accessing
+ the share only has the primary group default assigned to this group
+ if they are already assigned as a member of that group. This allows
+ an administrator to decide that only users who are already in a
+ particular group will create files with group ownership set to that
+ group. This gives a finer granularity of ownership assignment. For
+ example, the setting <TT
+CLASS="FILENAME"
+>force group = +sys</TT
+> means
+ that only users who are already in group sys will have their default
+ primary group assigned to sys when accessing this Samba share. All
+ other users will retain their ordinary primary group.</P
+><P
+>If the <A
+HREF="#FORCEUSER"
+><TT
+CLASS="PARAMETER"
+><I
+>force user
+ </I
+></TT
+></A
+> parameter is also set the group specified in
+ <TT
+CLASS="PARAMETER"
+><I
+>force group</I
+></TT
+> will override the primary group
+ set in <TT
+CLASS="PARAMETER"
+><I
+>force user</I
+></TT
+>.</P
+><P
+>See also <A
+HREF="#FORCEUSER"
+><TT
+CLASS="PARAMETER"
+><I
+>force
+ user</I
+></TT
+></A
+>.</P
+><P
+>Default: <I
+CLASS="EMPHASIS"
+>no forced group</I
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>force group = agroup</B
+></P
+></DD
+><DT
+><A
+NAME="FORCESECURITYMODE"
+></A
+>force security mode (S)</DT
+><DD
+><P
+>This parameter controls what UNIX permission
+ bits can be modified when a Windows NT client is manipulating
+ the UNIX permission on a file using the native NT security dialog
+ box.</P
+><P
+>This parameter is applied as a mask (OR'ed with) to the
+ changed permission bits, thus forcing any bits in this mask that
+ the user may have modified to be on. Essentially, one bits in this
+ mask may be treated as a set of bits that, when modifying security
+ on a file, the user has always set to be 'on'.</P
+><P
+>If not set explicitly this parameter is set to 0,
+ and allows a user to modify all the user/group/world permissions on a file,
+ with no restrictions.</P
+><P
+><I
+CLASS="EMPHASIS"
+>Note</I
+> that users who can access
+ the Samba server through other means can easily bypass this restriction,
+ so it is primarily useful for standalone "appliance" systems.
+ Administrators of most normal systems will probably want to leave
+ this set to 0000.</P
+><P
+>See also the <A
+HREF="#FORCEDIRECTORYSECURITYMODE"
+><TT
+CLASS="PARAMETER"
+><I
+> force directory security mode</I
+></TT
+></A
+>,
+ <A
+HREF="#DIRECTORYSECURITYMASK"
+><TT
+CLASS="PARAMETER"
+><I
+>directory security
+ mask</I
+></TT
+></A
+>, <A
+HREF="#SECURITYMASK"
+><TT
+CLASS="PARAMETER"
+><I
+> security mask</I
+></TT
+></A
+> parameters.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>force security mode = 0</B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>force security mode = 700</B
+></P
+></DD
+><DT
+><A
+NAME="FORCEUSER"
+></A
+>force user (S)</DT
+><DD
+><P
+>This specifies a UNIX user name that will be
+ assigned as the default user for all users connecting to this service.
+ This is useful for sharing files. You should also use it carefully
+ as using it incorrectly can cause security problems.</P
+><P
+>This user name only gets used once a connection is established.
+ Thus clients still need to connect as a valid user and supply a
+ valid password. Once connected, all file operations will be performed
+ as the "forced user", no matter what username the client connected
+ as. This can be very useful.</P
+><P
+>In Samba 2.0.5 and above this parameter also causes the
+ primary group of the forced user to be used as the primary group
+ for all file activity. Prior to 2.0.5 the primary group was left
+ as the primary group of the connecting user (this was a bug).</P
+><P
+>See also <A
+HREF="#FORCEGROUP"
+><TT
+CLASS="PARAMETER"
+><I
+>force group
+ </I
+></TT
+></A
+></P
+><P
+>Default: <I
+CLASS="EMPHASIS"
+>no forced user</I
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>force user = auser</B
+></P
+></DD
+><DT
+><A
+NAME="FSTYPE"
+></A
+>fstype (S)</DT
+><DD
+><P
+>This parameter allows the administrator to
+ configure the string that specifies the type of filesystem a share
+ is using that is reported by <A
+HREF="smbd.8.html"
+TARGET="_top"
+><B
+CLASS="COMMAND"
+>smbd(8)
+ </B
+></A
+> when a client queries the filesystem type
+ for a share. The default type is <TT
+CLASS="CONSTANT"
+>NTFS</TT
+> for
+ compatibility with Windows NT but this can be changed to other
+ strings such as <TT
+CLASS="CONSTANT"
+>Samba</TT
+> or <TT
+CLASS="CONSTANT"
+>FAT
+ </TT
+> if required.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>fstype = NTFS</B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>fstype = Samba</B
+></P
+></DD
+><DT
+><A
+NAME="GETWDCACHE"
+></A
+>getwd cache (G)</DT
+><DD
+><P
+>This is a tuning option. When this is enabled a
+ caching algorithm will be used to reduce the time taken for getwd()
+ calls. This can have a significant impact on performance, especially
+ when the <A
+HREF="#WIDELINKS"
+><TT
+CLASS="PARAMETER"
+><I
+>wide links</I
+></TT
+>
+ </A
+>parameter is set to <TT
+CLASS="CONSTANT"
+>no</TT
+>.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>getwd cache = yes</B
+></P
+></DD
+><DT
+><A
+NAME="GROUP"
+></A
+>group (S)</DT
+><DD
+><P
+>Synonym for <A
+HREF="#FORCEGROUP"
+><TT
+CLASS="PARAMETER"
+><I
+>force
+ group</I
+></TT
+></A
+>.</P
+></DD
+><DT
+><A
+NAME="GUESTACCOUNT"
+></A
+>guest account (S)</DT
+><DD
+><P
+>This is a username which will be used for access
+ to services which are specified as <A
+HREF="#GUESTOK"
+><TT
+CLASS="PARAMETER"
+><I
+> guest ok</I
+></TT
+></A
+> (see below). Whatever privileges this
+ 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,
+ the specified username overrides this one.</P
+><P
+>One some systems the default guest account "nobody" may not
+ be able to print. Use another account in this case. You should test
+ this by trying to log in as your guest user (perhaps by using the
+ <B
+CLASS="COMMAND"
+>su -</B
+> command) and trying to print using the
+ system print command such as <B
+CLASS="COMMAND"
+>lpr(1)</B
+> or <B
+CLASS="COMMAND"
+> lp(1)</B
+>.</P
+><P
+>This parameter does not accept % macros, because
+ many parts of the system require this value to be
+ constant for correct operation.</P
+><P
+>Default: <I
+CLASS="EMPHASIS"
+>specified at compile time, usually
+ "nobody"</I
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>guest account = ftp</B
+></P
+></DD
+><DT
+><A
+NAME="GUESTOK"
+></A
+>guest ok (S)</DT
+><DD
+><P
+>If this parameter is <TT
+CLASS="CONSTANT"
+>yes</TT
+> for
+ a service, then no password is required to connect to the service.
+ Privileges will be those of the <A
+HREF="#GUESTACCOUNT"
+><TT
+CLASS="PARAMETER"
+><I
+> guest account</I
+></TT
+></A
+>.</P
+><P
+>See the section below on <A
+HREF="#SECURITY"
+><TT
+CLASS="PARAMETER"
+><I
+> security</I
+></TT
+></A
+> for more information about this option.
+ </P
+><P
+>Default: <B
+CLASS="COMMAND"
+>guest ok = no</B
+></P
+></DD
+><DT
+><A
+NAME="GUESTONLY"
+></A
+>guest only (S)</DT
+><DD
+><P
+>If this parameter is <TT
+CLASS="CONSTANT"
+>yes</TT
+> for
+ a service, then only guest connections to the service are permitted.
+ This parameter will have no effect if <A
+HREF="#GUESTOK"
+> <TT
+CLASS="PARAMETER"
+><I
+>guest ok</I
+></TT
+></A
+> is not set for the service.</P
+><P
+>See the section below on <A
+HREF="#SECURITY"
+><TT
+CLASS="PARAMETER"
+><I
+> security</I
+></TT
+></A
+> for more information about this option.
+ </P
+><P
+>Default: <B
+CLASS="COMMAND"
+>guest only = no</B
+></P
+></DD
+><DT
+><A
+NAME="HIDEDOTFILES"
+></A
+>hide dot files (S)</DT
+><DD
+><P
+>This is a boolean parameter that controls whether
+ files starting with a dot appear as hidden files.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>hide dot files = yes</B
+></P
+></DD
+><DT
+><A
+NAME="HIDEFILES"
+></A
+>hide files(S)</DT
+><DD
+><P
+>This is a list of files or directories that are not
+ visible but are accessible. The DOS 'hidden' attribute is applied
+ to any files or directories that match.</P
+><P
+>Each entry in the list must be separated by a '/',
+ which allows spaces to be included in the entry. '*'
+ and '?' can be used to specify multiple files or directories
+ as in DOS wildcards.</P
+><P
+>Each entry must be a Unix path, not a DOS path and must
+ not include the Unix directory separator '/'.</P
+><P
+>Note that the case sensitivity option is applicable
+ in hiding files.</P
+><P
+>Setting this parameter will affect the performance of Samba,
+ as it will be forced to check all files and directories for a match
+ as they are scanned.</P
+><P
+>See also <A
+HREF="#HIDEDOTFILES"
+><TT
+CLASS="PARAMETER"
+><I
+>hide
+ dot files</I
+></TT
+></A
+>, <A
+HREF="#VETOFILES"
+><TT
+CLASS="PARAMETER"
+><I
+> veto files</I
+></TT
+></A
+> and <A
+HREF="#CASESENSITIVE"
+> <TT
+CLASS="PARAMETER"
+><I
+>case sensitive</I
+></TT
+></A
+>.</P
+><P
+>Default: <I
+CLASS="EMPHASIS"
+>no file are hidden</I
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>hide files =
+ /.*/DesktopFolderDB/TrashFor%m/resource.frk/</B
+></P
+><P
+>The above example is based on files that the Macintosh
+ SMB client (DAVE) available from <A
+HREF="http://www.thursby.com"
+TARGET="_top"
+>
+ Thursby</A
+> creates for internal use, and also still hides
+ all files beginning with a dot.</P
+></DD
+><DT
+><A
+NAME="HIDELOCALUSERS"
+></A
+>hide local users(G)</DT
+><DD
+><P
+>This parameter toggles the hiding of local UNIX
+ users (root, wheel, floppy, etc) from remote clients.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>hide local users = no</B
+></P
+></DD
+><DT
+><A
+NAME="HIDEUNREADABLE"
+></A
+>hide unreadable (G)</DT
+><DD
+><P
+>This parameter prevents clients from seeing the
+ existance of files that cannot be read. Defaults to off.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>hide unreadable = no</B
+></P
+></DD
+><DT
+><A
+NAME="HIDEUNWRITEABLEFILES"
+></A
+>hide unwriteable files (G)</DT
+><DD
+><P
+>This parameter prevents clients from seeing
+ the existance of files that cannot be written to. Defaults to off.
+ Note that unwriteable directories are shown as usual.
+ </P
+><P
+>Default: <B
+CLASS="COMMAND"
+>hide unwriteable = no</B
+></P
+></DD
+><DT
+><A
+NAME="HIDESPECIALFILES"
+></A
+>hide special files (G)</DT
+><DD
+><P
+>This parameter prevents clients from seeing
+ special files such as sockets, devices and fifo's in directory
+ listings.
+ </P
+><P
+>Default: <B
+CLASS="COMMAND"
+>hide special files = no</B
+></P
+></DD
+><DT
+><A
+NAME="HOMEDIRMAP"
+></A
+>homedir map (G)</DT
+><DD
+><P
+>If<A
+HREF="#NISHOMEDIR"
+><TT
+CLASS="PARAMETER"
+><I
+>nis homedir
+ </I
+></TT
+></A
+> is <TT
+CLASS="CONSTANT"
+>yes</TT
+>, and <A
+HREF="smbd.8.html"
+TARGET="_top"
+><B
+CLASS="COMMAND"
+>smbd(8)</B
+></A
+> is also acting
+ as a Win95/98 <TT
+CLASS="PARAMETER"
+><I
+>logon server</I
+></TT
+> then this parameter
+ specifies the NIS (or YP) map from which the server for the user's
+ home directory should be extracted. At present, only the Sun
+ auto.home map format is understood. The form of the map is:</P
+><P
+><B
+CLASS="COMMAND"
+>username server:/some/file/system</B
+></P
+><P
+>and the program will extract the servername from before
+ the first ':'. There should probably be a better parsing system
+ that copes with different map formats and also Amd (another
+ automounter) maps.</P
+><P
+><I
+CLASS="EMPHASIS"
+>NOTE :</I
+>A working NIS client is required on
+ the system for this option to work.</P
+><P
+>See also <A
+HREF="#NISHOMEDIR"
+><TT
+CLASS="PARAMETER"
+><I
+>nis homedir</I
+></TT
+>
+ </A
+>, <A
+HREF="#DOMAINLOGONS"
+><TT
+CLASS="PARAMETER"
+><I
+>domain logons</I
+></TT
+>
+ </A
+>.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>homedir map = &#60;empty string&#62;</B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>homedir map = amd.homedir</B
+></P
+></DD
+><DT
+><A
+NAME="HOSTMSDFS"
+></A
+>host msdfs (G)</DT
+><DD
+><P
+>This boolean parameter is only available
+ if Samba has been configured and compiled with the <B
+CLASS="COMMAND"
+> --with-msdfs</B
+> option. If set to <TT
+CLASS="CONSTANT"
+>yes</TT
+>,
+ Samba will act as a Dfs server, and allow Dfs-aware clients
+ to browse Dfs trees hosted on the server.</P
+><P
+>See also the <A
+HREF="#MSDFSROOT"
+><TT
+CLASS="PARAMETER"
+><I
+> msdfs root</I
+></TT
+></A
+> share level parameter. For
+ more information on setting up a Dfs tree on Samba,
+ refer to <A
+HREF="msdfs_setup.html"
+TARGET="_top"
+>msdfs_setup.html</A
+>.
+ </P
+><P
+>Default: <B
+CLASS="COMMAND"
+>host msdfs = no</B
+></P
+></DD
+><DT
+><A
+NAME="HOSTNAMELOOKUPS"
+></A
+>hostname lookups (G)</DT
+><DD
+><P
+>Specifies whether samba should use (expensive)
+ hostname lookups or use the ip addresses instead. An example place
+ where hostname lookups are currently used is when checking
+ the <B
+CLASS="COMMAND"
+>hosts deny</B
+> and <B
+CLASS="COMMAND"
+>hosts allow</B
+>.
+ </P
+><P
+>Default: <B
+CLASS="COMMAND"
+>hostname lookups = yes</B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>hostname lookups = no</B
+></P
+></DD
+><DT
+><A
+NAME="HOSTSALLOW"
+></A
+>hosts allow (S)</DT
+><DD
+><P
+>A synonym for this parameter is <TT
+CLASS="PARAMETER"
+><I
+>allow
+ hosts</I
+></TT
+>.</P
+><P
+>This parameter is a comma, space, or tab delimited
+ set of hosts which are permitted to access a service.</P
+><P
+>If specified in the [global] section then it will
+ apply to all services, regardless of whether the individual
+ service has a different setting.</P
+><P
+>You can specify the hosts by name or IP number. For
+ example, you could restrict access to only the hosts on a
+ Class C subnet with something like <B
+CLASS="COMMAND"
+>allow hosts = 150.203.5.
+ </B
+>. The full syntax of the list is described in the man
+ page <TT
+CLASS="FILENAME"
+>hosts_access(5)</TT
+>. Note that this man
+ page may not be present on your system, so a brief description will
+ be given here also.</P
+><P
+>Note that the localhost address 127.0.0.1 will always
+ be allowed access unless specifically denied by a <A
+HREF="#HOSTSDENY"
+><TT
+CLASS="PARAMETER"
+><I
+>hosts deny</I
+></TT
+></A
+> option.</P
+><P
+>You can also specify hosts by network/netmask pairs and
+ by netgroup names if your system supports netgroups. The
+ <I
+CLASS="EMPHASIS"
+>EXCEPT</I
+> keyword can also be used to limit a
+ wildcard list. The following examples may provide some help:</P
+><P
+>Example 1: allow all IPs in 150.203.*.*; except one</P
+><P
+><B
+CLASS="COMMAND"
+>hosts allow = 150.203. EXCEPT 150.203.6.66</B
+></P
+><P
+>Example 2: allow hosts that match the given network/netmask</P
+><P
+><B
+CLASS="COMMAND"
+>hosts allow = 150.203.15.0/255.255.255.0</B
+></P
+><P
+>Example 3: allow a couple of hosts</P
+><P
+><B
+CLASS="COMMAND"
+>hosts allow = lapland, arvidsjaur</B
+></P
+><P
+>Example 4: allow only hosts in NIS netgroup "foonet", but
+ deny access from one particular host</P
+><P
+><B
+CLASS="COMMAND"
+>hosts allow = @foonet</B
+></P
+><P
+><B
+CLASS="COMMAND"
+>hosts deny = pirate</B
+></P
+><P
+>Note that access still requires suitable user-level passwords.</P
+><P
+>See <A
+HREF="testparm.1.html"
+TARGET="_top"
+><B
+CLASS="COMMAND"
+>testparm(1)</B
+>
+ </A
+> for a way of testing your host access to see if it does
+ what you expect.</P
+><P
+>Default: <I
+CLASS="EMPHASIS"
+>none (i.e., all hosts permitted access)
+ </I
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>allow hosts = 150.203.5. myhost.mynet.edu.au
+ </B
+></P
+></DD
+><DT
+><A
+NAME="HOSTSDENY"
+></A
+>hosts deny (S)</DT
+><DD
+><P
+>The opposite of <TT
+CLASS="PARAMETER"
+><I
+>hosts allow</I
+></TT
+>
+ - hosts listed here are <I
+CLASS="EMPHASIS"
+>NOT</I
+> permitted access to
+ services unless the specific services have their own lists to override
+ this one. Where the lists conflict, the <TT
+CLASS="PARAMETER"
+><I
+>allow</I
+></TT
+>
+ list takes precedence.</P
+><P
+>Default: <I
+CLASS="EMPHASIS"
+>none (i.e., no hosts specifically excluded)
+ </I
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>hosts deny = 150.203.4. badhost.mynet.edu.au
+ </B
+></P
+></DD
+><DT
+><A
+NAME="HOSTSEQUIV"
+></A
+>hosts equiv (G)</DT
+><DD
+><P
+>If this global parameter is a non-null string,
+ it specifies the name of a file to read for the names of hosts
+ and users who will be allowed access without specifying a password.
+ </P
+><P
+>This is not be confused with <A
+HREF="#HOSTSALLOW"
+> <TT
+CLASS="PARAMETER"
+><I
+>hosts allow</I
+></TT
+></A
+> which is about hosts
+ access to services and is more useful for guest services. <TT
+CLASS="PARAMETER"
+><I
+> hosts equiv</I
+></TT
+> may be useful for NT clients which will
+ not supply passwords to Samba.</P
+><P
+><I
+CLASS="EMPHASIS"
+>NOTE :</I
+> The use of <TT
+CLASS="PARAMETER"
+><I
+>hosts equiv
+ </I
+></TT
+> can be a major security hole. This is because you are
+ trusting the PC to supply the correct username. It is very easy to
+ get a PC to supply a false username. I recommend that the
+ <TT
+CLASS="PARAMETER"
+><I
+>hosts equiv</I
+></TT
+> option be only used if you really
+ know what you are doing, or perhaps on a home network where you trust
+ your spouse and kids. And only if you <I
+CLASS="EMPHASIS"
+>really</I
+> trust
+ them :-).</P
+><P
+>Default: <I
+CLASS="EMPHASIS"
+>no host equivalences</I
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>hosts equiv = /etc/hosts.equiv</B
+></P
+></DD
+><DT
+><A
+NAME="INCLUDE"
+></A
+>include (G)</DT
+><DD
+><P
+>This allows you to include one config file
+ inside another. The file is included literally, as though typed
+ in place.</P
+><P
+>It takes the standard substitutions, except <TT
+CLASS="PARAMETER"
+><I
+>%u
+ </I
+></TT
+>, <TT
+CLASS="PARAMETER"
+><I
+>%P</I
+></TT
+> and <TT
+CLASS="PARAMETER"
+><I
+>%S</I
+></TT
+>.
+ </P
+><P
+>Default: <I
+CLASS="EMPHASIS"
+>no file included</I
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>include = /usr/local/samba/lib/admin_smb.conf
+ </B
+></P
+></DD
+><DT
+><A
+NAME="INHERITACLS"
+></A
+>inherit acls (S)</DT
+><DD
+><P
+>This parameter can be used to ensure
+ that if default acls exist on parent directories,
+ they are always honored when creating a subdirectory.
+ The default behavior is to use the mode specified
+ when creating the directory. Enabling this option
+ sets the mode to 0777, thus guaranteeing that
+ default directory acls are propagated.
+ </P
+><P
+>Default: <B
+CLASS="COMMAND"
+>inherit acls = no</B
+>
+ </P
+></DD
+><DT
+><A
+NAME="INHERITPERMISSIONS"
+></A
+>inherit permissions (S)</DT
+><DD
+><P
+>The permissions on new files and directories
+ are normally governed by <A
+HREF="#CREATEMASK"
+><TT
+CLASS="PARAMETER"
+><I
+> create mask</I
+></TT
+></A
+>, <A
+HREF="#DIRECTORYMASK"
+> <TT
+CLASS="PARAMETER"
+><I
+>directory mask</I
+></TT
+></A
+>, <A
+HREF="#FORCECREATEMODE"
+><TT
+CLASS="PARAMETER"
+><I
+>force create mode</I
+></TT
+>
+ </A
+> and <A
+HREF="#FORCEDIRECTORYMODE"
+><TT
+CLASS="PARAMETER"
+><I
+>force
+ directory mode</I
+></TT
+></A
+> but the boolean inherit
+ permissions parameter overrides this.</P
+><P
+>New directories inherit the mode of the parent directory,
+ including bits such as setgid.</P
+><P
+>New files inherit their read/write bits from the parent
+ directory. Their execute bits continue to be determined by
+ <A
+HREF="#MAPARCHIVE"
+><TT
+CLASS="PARAMETER"
+><I
+>map archive</I
+></TT
+>
+ </A
+>, <A
+HREF="#MAPHIDDEN"
+><TT
+CLASS="PARAMETER"
+><I
+>map hidden</I
+></TT
+>
+ </A
+> and <A
+HREF="#MAPSYSTEM"
+><TT
+CLASS="PARAMETER"
+><I
+>map system</I
+></TT
+>
+ </A
+> as usual.</P
+><P
+>Note that the setuid bit is <I
+CLASS="EMPHASIS"
+>never</I
+> set via
+ inheritance (the code explicitly prohibits this).</P
+><P
+>This can be particularly useful on large systems with
+ many users, perhaps several thousand, to allow a single [homes]
+ share to be used flexibly by each user.</P
+><P
+>See also <A
+HREF="#CREATEMASK"
+><TT
+CLASS="PARAMETER"
+><I
+>create mask
+ </I
+></TT
+></A
+>, <A
+HREF="#DIRECTORYMASK"
+><TT
+CLASS="PARAMETER"
+><I
+> directory mask</I
+></TT
+></A
+>, <A
+HREF="#FORCECREATEMODE"
+> <TT
+CLASS="PARAMETER"
+><I
+>force create mode</I
+></TT
+></A
+> and <A
+HREF="#FORCEDIRECTORYMODE"
+><TT
+CLASS="PARAMETER"
+><I
+>force directory mode</I
+></TT
+>
+ </A
+>.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>inherit permissions = no</B
+></P
+></DD
+><DT
+><A
+NAME="INTERFACES"
+></A
+>interfaces (G)</DT
+><DD
+><P
+>This option allows you to override the default
+ network interfaces list that Samba will use for browsing, name
+ registration and other NBT traffic. By default Samba will query
+ the kernel for the list of all active interfaces and use any
+ interfaces except 127.0.0.1 that are broadcast capable.</P
+><P
+>The option takes a list of interface strings. Each string
+ can be in any of the following forms:</P
+><P
+></P
+><UL
+><LI
+><P
+>a network interface name (such as eth0).
+ This may include shell-like wildcards so eth* will match
+ any interface starting with the substring "eth"</P
+></LI
+><LI
+><P
+>an IP address. In this case the netmask is
+ determined from the list of interfaces obtained from the
+ kernel</P
+></LI
+><LI
+><P
+>an IP/mask pair. </P
+></LI
+><LI
+><P
+>a broadcast/mask pair.</P
+></LI
+></UL
+><P
+>The "mask" parameters can either be a bit length (such
+ as 24 for a C class network) or a full netmask in dotted
+ 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 OS's normal hostname resolution mechanisms.</P
+><P
+>For example, the following line:</P
+><P
+><B
+CLASS="COMMAND"
+>interfaces = eth0 192.168.2.10/24 192.168.3.10/255.255.255.0
+ </B
+></P
+><P
+>would configure three network interfaces corresponding
+ to the eth0 device and IP addresses 192.168.2.10 and 192.168.3.10.
+ The netmasks of the latter two interfaces would be set to 255.255.255.0.</P
+><P
+>See also <A
+HREF="#BINDINTERFACESONLY"
+><TT
+CLASS="PARAMETER"
+><I
+>bind
+ interfaces only</I
+></TT
+></A
+>.</P
+><P
+>Default: <I
+CLASS="EMPHASIS"
+>all active interfaces except 127.0.0.1
+ that are broadcast capable</I
+></P
+></DD
+><DT
+><A
+NAME="INVALIDUSERS"
+></A
+>invalid users (S)</DT
+><DD
+><P
+>This is a list of users that should not be allowed
+ to login to this service. This is really a <I
+CLASS="EMPHASIS"
+>paranoid</I
+>
+ check to absolutely ensure an improper setting does not breach
+ your security.</P
+><P
+>A name starting with a '@' is interpreted as an NIS
+ netgroup first (if your system supports NIS), and then as a UNIX
+ group if the name was not found in the NIS netgroup database.</P
+><P
+>A name starting with '+' is interpreted only
+ by looking in the UNIX group database. A name starting with
+ '&#38;' is interpreted only by looking in the NIS netgroup database
+ (this requires NIS to be working on your system). The characters
+ '+' and '&#38;' may be used at the start of the name in either order
+ so the value <TT
+CLASS="PARAMETER"
+><I
+>+&#38;group</I
+></TT
+> means check the
+ UNIX group database, followed by the NIS netgroup database, and
+ the value <TT
+CLASS="PARAMETER"
+><I
+>&#38;+group</I
+></TT
+> means check the NIS
+ netgroup database, followed by the UNIX group database (the
+ same as the '@' prefix).</P
+><P
+>The current servicename is substituted for <TT
+CLASS="PARAMETER"
+><I
+>%S</I
+></TT
+>.
+ This is useful in the [homes] section.</P
+><P
+>See also <A
+HREF="#VALIDUSERS"
+><TT
+CLASS="PARAMETER"
+><I
+>valid users
+ </I
+></TT
+></A
+>.</P
+><P
+>Default: <I
+CLASS="EMPHASIS"
+>no invalid users</I
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>invalid users = root fred admin @wheel
+ </B
+></P
+></DD
+><DT
+><A
+NAME="KEEPALIVE"
+></A
+>keepalive (G)</DT
+><DD
+><P
+>The value of the parameter (an integer) represents
+ the number of seconds between <TT
+CLASS="PARAMETER"
+><I
+>keepalive</I
+></TT
+>
+ packets. If this parameter is zero, no keepalive packets will be
+ sent. Keepalive packets, if sent, allow the server to tell whether
+ a client is still present and responding.</P
+><P
+>Keepalives should, in general, not be needed if the socket
+ being used has the SO_KEEPALIVE attribute set on it (see <A
+HREF="#SOCKETOPTIONS"
+><TT
+CLASS="PARAMETER"
+><I
+>socket options</I
+></TT
+></A
+>).
+ Basically you should only use this option if you strike difficulties.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>keepalive = 300</B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>keepalive = 600</B
+></P
+></DD
+><DT
+><A
+NAME="KERNELOPLOCKS"
+></A
+>kernel oplocks (G)</DT
+><DD
+><P
+>For UNIXes that support kernel based <A
+HREF="#OPLOCKS"
+><TT
+CLASS="PARAMETER"
+><I
+>oplocks</I
+></TT
+></A
+>
+ (currently only IRIX and the Linux 2.4 kernel), this parameter
+ allows the use of them to be turned on or off.</P
+><P
+>Kernel oplocks support allows Samba <TT
+CLASS="PARAMETER"
+><I
+>oplocks
+ </I
+></TT
+> to be broken whenever a local UNIX process or NFS operation
+ accesses a file that <A
+HREF="smbd.8.html"
+TARGET="_top"
+><B
+CLASS="COMMAND"
+>smbd(8)</B
+>
+ </A
+> has oplocked. This allows complete data consistency between
+ SMB/CIFS, NFS and local file access (and is a <I
+CLASS="EMPHASIS"
+>very</I
+>
+ cool feature :-).</P
+><P
+>This parameter defaults to <TT
+CLASS="CONSTANT"
+>on</TT
+>, but is translated
+ to a no-op on systems that no not have the necessary kernel support.
+ You should never need to touch this parameter.</P
+><P
+>See also the <A
+HREF="#OPLOCKS"
+><TT
+CLASS="PARAMETER"
+><I
+>oplocks</I
+></TT
+>
+ </A
+> and <A
+HREF="#LEVEL2OPLOCKS"
+><TT
+CLASS="PARAMETER"
+><I
+>level2 oplocks
+ </I
+></TT
+></A
+> parameters.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>kernel oplocks = yes</B
+></P
+></DD
+><DT
+><A
+NAME="LANMANAUTH"
+></A
+>lanman auth (G)</DT
+><DD
+><P
+>This parameter determines whether or not <A
+HREF="smbd.8.html"
+TARGET="_top"
+>smbd</A
+> will
+ attempt to authenticate users using the LANMAN password hash.
+ If disabled, only clients which support NT password hashes (e.g. Windows
+ NT/2000 clients, smbclient, etc... but not Windows 95/98 or the MS DOS
+ network client) will be able to connect to the Samba host.</P
+><P
+>Default : <B
+CLASS="COMMAND"
+>lanman auth = yes</B
+></P
+></DD
+><DT
+><A
+NAME="LARGEREADWRITE"
+></A
+>large readwrite (G)</DT
+><DD
+><P
+>This parameter determines whether or not <A
+HREF="smbd.8.html"
+TARGET="_top"
+>smbd</A
+>
+ supports the new 64k streaming read and write varient SMB requests introduced
+ with Windows 2000. Note that due to Windows 2000 client redirector bugs
+ this requires Samba to be running on a 64-bit capable operating system such
+ as IRIX, Solaris or a Linux 2.4 kernel. Can improve performance by 10% with
+ Windows 2000 clients. Defaults to on. Not as tested as some other Samba
+ code paths.
+ </P
+><P
+>Default : <B
+CLASS="COMMAND"
+>large readwrite = yes</B
+></P
+></DD
+><DT
+><A
+NAME="LDAPADMINDN"
+></A
+>ldap admin dn (G)</DT
+><DD
+><P
+>The <TT
+CLASS="PARAMETER"
+><I
+>ldap admin dn</I
+></TT
+> defines the Distinguished
+ Name (DN) name used by Samba to contact the ldap server when retreiving
+ user account information. The <TT
+CLASS="PARAMETER"
+><I
+>ldap
+ admin dn</I
+></TT
+> is used in conjunction with the admin dn password
+ stored in the <TT
+CLASS="FILENAME"
+>private/secrets.tdb</TT
+> file. See the
+ <A
+HREF="smbpasswd.8.html"
+TARGET="_top"
+><B
+CLASS="COMMAND"
+>smbpasswd(8)</B
+></A
+> man
+ page for more information on how to accomplish this.
+ </P
+></DD
+><DT
+><A
+NAME="LDAPDELETEDN"
+></A
+>&#62;ldap del only sam attr (G)</DT
+><DD
+><P
+> This parameter specifies whether a delete
+ operation in the ldapsam deletes the complete entry or only the attributes
+ specific to Samba.
+ </P
+><P
+>Default : <I
+CLASS="EMPHASIS"
+>ldap delete dn = no</I
+></P
+></DD
+><DT
+><A
+NAME="LDAPDELONLYSAMATTR"
+></A
+>&#62;ldap del only sam attr (G)</DT
+><DD
+><P
+> Inverted synonym for <A
+HREF="#LDAPDELETEDN"
+><TT
+CLASS="PARAMETER"
+><I
+> ldap delete dn</I
+></TT
+></A
+>.
+ </P
+></DD
+><DT
+><A
+NAME="LDAPFILTER"
+></A
+>ldap filter (G)</DT
+><DD
+><P
+>This parameter specifies the RFC 2254 compliant LDAP search filter.
+ The default is to match the login name with the <TT
+CLASS="CONSTANT"
+>uid</TT
+>
+ attribute for all entries matching the <TT
+CLASS="CONSTANT"
+>sambaAccount</TT
+>
+ objectclass. Note that this filter should only return one entry.
+ </P
+><P
+>Default : <B
+CLASS="COMMAND"
+>ldap filter = (&#38;(uid=%u)(objectclass=sambaAccount))</B
+></P
+></DD
+><DT
+><A
+NAME="LDAPPORT"
+></A
+>ldap port (G)</DT
+><DD
+><P
+>This parameter is only available if Samba has been
+ configure to include the <B
+CLASS="COMMAND"
+>--with-ldapsam</B
+> option
+ at compile time.
+ </P
+><P
+> This option is used to control the tcp port number used to contact
+ the <A
+HREF="#LDAPSERVER"
+><TT
+CLASS="PARAMETER"
+><I
+>ldap server</I
+></TT
+></A
+>.
+ The default is to use the stand LDAPS port 636.
+ </P
+><P
+>See Also: <A
+HREF="#LDAPSSL"
+>ldap ssl</A
+>
+ </P
+><P
+>Default : <B
+CLASS="COMMAND"
+>ldap port = 636 ; if ldap ssl = on</B
+></P
+><P
+>Default : <B
+CLASS="COMMAND"
+>ldap port = 389 ; if ldap ssl = off</B
+></P
+></DD
+><DT
+><A
+NAME="LDAPSERVER"
+></A
+>ldap server (G)</DT
+><DD
+><P
+>This parameter is only available if Samba has been
+ configure to include the <B
+CLASS="COMMAND"
+>--with-ldapsam</B
+> option
+ at compile time.
+ </P
+><P
+> This parameter should contain the FQDN of the ldap directory
+ server which should be queried to locate user account information.
+ </P
+><P
+>Default : <B
+CLASS="COMMAND"
+>ldap server = localhost</B
+></P
+></DD
+><DT
+><A
+NAME="LDAPSSL"
+></A
+>ldap ssl (G)</DT
+><DD
+><P
+>This option is used to define whether or not Samba should
+ use SSL when connecting to the ldap server
+ This is <I
+CLASS="EMPHASIS"
+>NOT</I
+> related to
+ Samba's previous SSL support which was enabled by specifying the
+ <B
+CLASS="COMMAND"
+>--with-ssl</B
+> option to the <TT
+CLASS="FILENAME"
+>configure</TT
+>
+ script.
+ </P
+><P
+> The <TT
+CLASS="PARAMETER"
+><I
+>ldap ssl</I
+></TT
+> can be set to one of three values:
+ </P
+><P
+></P
+><UL
+><LI
+><P
+><TT
+CLASS="PARAMETER"
+><I
+>Off</I
+></TT
+> = Never use SSL when querying the directory.</P
+></LI
+><LI
+><P
+><TT
+CLASS="PARAMETER"
+><I
+>Start_tls</I
+></TT
+> = Use the LDAPv3 StartTLS extended operation
+ (RFC2830) for communicating with the directory server.</P
+></LI
+><LI
+><P
+><TT
+CLASS="PARAMETER"
+><I
+>On</I
+></TT
+> =
+ Use SSL on the ldaps port when contacting the
+ <TT
+CLASS="PARAMETER"
+><I
+>ldap server</I
+></TT
+>. Only
+ available when the backwards-compatiblity <B
+CLASS="COMMAND"
+> --with-ldapsam</B
+> option is specified
+ to configure. See <A
+HREF="#PASSDBBACKEND"
+><TT
+CLASS="PARAMETER"
+><I
+>passdb backend</I
+></TT
+></A
+></P
+></LI
+></UL
+><P
+>Default : <B
+CLASS="COMMAND"
+>ldap ssl = start_tls</B
+></P
+></DD
+><DT
+><A
+NAME="LDAPSUFFIX"
+></A
+>ldap suffix (G)</DT
+><DD
+><P
+>Specifies where user and machine accounts are added to the tree. Can be overriden by <B
+CLASS="COMMAND"
+>ldap user suffix</B
+> and <B
+CLASS="COMMAND"
+>ldap machine suffix</B
+>. It also used as the base dn for all ldap searches. </P
+><P
+>Default : <I
+CLASS="EMPHASIS"
+>none</I
+></P
+></DD
+><DT
+><A
+NAME="LDAPUSERSUFFIX"
+></A
+>ldap user suffix (G)</DT
+><DD
+><P
+>It specifies where users are added to the tree.
+ </P
+><P
+>Default : <I
+CLASS="EMPHASIS"
+>none</I
+></P
+></DD
+><DT
+><A
+NAME="LDAPMACHINESUFFIX"
+></A
+>ldap machine suffix (G)</DT
+><DD
+><P
+>It specifies where machines should be
+ added to the ldap tree.
+ </P
+><P
+>Default : <I
+CLASS="EMPHASIS"
+>none</I
+></P
+></DD
+><DT
+><A
+NAME="LDAPPASSWDSYNC"
+></A
+>ldap passwd sync (G)</DT
+><DD
+><P
+>This option is used to define whether
+ or not Samba should sync the LDAP password with the NT
+ and LM hashes for normal accounts (NOT for
+ workstation, server or domain trusts) on a password
+ change via SAMBA.
+ </P
+><P
+> The <TT
+CLASS="PARAMETER"
+><I
+>ldap passwd sync</I
+></TT
+> can be set to one of three values:
+ </P
+><P
+></P
+><UL
+><LI
+><P
+><TT
+CLASS="PARAMETER"
+><I
+>Yes</I
+></TT
+> = Try to update the LDAP, NT and LM passwords and update the pwdLastSet time.</P
+></LI
+><LI
+><P
+><TT
+CLASS="PARAMETER"
+><I
+>No</I
+></TT
+> = Update NT and LM passwords and update the pwdLastSet time.</P
+></LI
+><LI
+><P
+><TT
+CLASS="PARAMETER"
+><I
+>Only</I
+></TT
+> = Only update the LDAP password and let the LDAP server do the rest.</P
+></LI
+></UL
+><P
+>Default : <B
+CLASS="COMMAND"
+>ldap passwd sync = no</B
+></P
+></DD
+><DT
+><A
+NAME="LDAPTRUSTIDS"
+></A
+>ldap trust ids (G)</DT
+><DD
+><P
+>Normally, Samba validates each entry
+ in the LDAP server against getpwnam(). This allows
+ LDAP to be used for Samba with the unix system using
+ NIS (for example) and also ensures that Samba does not
+ present accounts that do not otherwise exist. </P
+><P
+>This option is used to disable this functionality, and
+ instead to rely on the presence of the appropriate
+ attributes in LDAP directly, which can result in a
+ significant performance boost in some situations.
+ Setting this option to yes effectivly assumes
+ that the local machine is running <B
+CLASS="COMMAND"
+>nss_ldap</B
+> against the
+ same LDAP server.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>ldap trust ids = No</B
+></P
+></DD
+><DT
+><A
+NAME="LEVEL2OPLOCKS"
+></A
+>level2 oplocks (S)</DT
+><DD
+><P
+>This parameter controls whether Samba supports
+ level2 (read-only) oplocks on a share.</P
+><P
+>Level2, or read-only oplocks allow Windows NT clients
+ that have an oplock on a file to downgrade from a read-write oplock
+ to a read-only oplock once a second client opens the file (instead
+ 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 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
+ writes to the file all clients are notified (no reply is needed
+ or waited for) and told to break their oplocks to "none" and
+ delete any read-ahead caches.</P
+><P
+>It is recommended that this parameter be turned on
+ to speed access to shared executables.</P
+><P
+>For more discussions on level2 oplocks see the CIFS spec.</P
+><P
+>Currently, if <A
+HREF="#KERNELOPLOCKS"
+><TT
+CLASS="PARAMETER"
+><I
+>kernel
+ oplocks</I
+></TT
+></A
+> are supported then level2 oplocks are
+ not granted (even if this parameter is set to <TT
+CLASS="CONSTANT"
+>yes</TT
+>).
+ Note also, the <A
+HREF="#OPLOCKS"
+><TT
+CLASS="PARAMETER"
+><I
+>oplocks</I
+></TT
+>
+ </A
+> parameter must be set to <TT
+CLASS="CONSTANT"
+>yes</TT
+> on this share in order for
+ this parameter to have any effect.</P
+><P
+>See also the <A
+HREF="#OPLOCKS"
+><TT
+CLASS="PARAMETER"
+><I
+>oplocks</I
+></TT
+>
+ </A
+> and <A
+HREF="#OPLOCKS"
+><TT
+CLASS="PARAMETER"
+><I
+>kernel oplocks</I
+></TT
+>
+ </A
+> parameters.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>level2 oplocks = yes</B
+></P
+></DD
+><DT
+><A
+NAME="LMANNOUNCE"
+></A
+>lm announce (G)</DT
+><DD
+><P
+>This parameter determines if <A
+HREF="nmbd.8.html"
+TARGET="_top"
+> <B
+CLASS="COMMAND"
+>nmbd(8)</B
+></A
+> will produce Lanman announce
+ broadcasts that are needed by OS/2 clients in order for them to see
+ the Samba server in their browse list. This parameter can have three
+ values, <TT
+CLASS="CONSTANT"
+>yes</TT
+>, <TT
+CLASS="CONSTANT"
+>no</TT
+>, or
+ <TT
+CLASS="CONSTANT"
+>auto</TT
+>. The default is <TT
+CLASS="CONSTANT"
+>auto</TT
+>.
+ If set to <TT
+CLASS="CONSTANT"
+>no</TT
+> Samba will never produce these
+ broadcasts. If set to <TT
+CLASS="CONSTANT"
+>yes</TT
+> Samba will produce
+ Lanman announce broadcasts at a frequency set by the parameter
+ <TT
+CLASS="PARAMETER"
+><I
+>lm interval</I
+></TT
+>. If set to <TT
+CLASS="CONSTANT"
+>auto</TT
+>
+ Samba will not send Lanman announce broadcasts by default but will
+ listen for them. If it hears such a broadcast on the wire it will
+ then start sending them at a frequency set by the parameter
+ <TT
+CLASS="PARAMETER"
+><I
+>lm interval</I
+></TT
+>.</P
+><P
+>See also <A
+HREF="#LMINTERVAL"
+><TT
+CLASS="PARAMETER"
+><I
+>lm interval
+ </I
+></TT
+></A
+>.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>lm announce = auto</B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>lm announce = yes</B
+></P
+></DD
+><DT
+><A
+NAME="LMINTERVAL"
+></A
+>lm interval (G)</DT
+><DD
+><P
+>If Samba is set to produce Lanman announce
+ broadcasts needed by OS/2 clients (see the <A
+HREF="#LMANNOUNCE"
+> <TT
+CLASS="PARAMETER"
+><I
+>lm announce</I
+></TT
+></A
+> parameter) then this
+ parameter defines the frequency in seconds with which they will be
+ made. If this is set to zero then no Lanman announcements will be
+ made despite the setting of the <TT
+CLASS="PARAMETER"
+><I
+>lm announce</I
+></TT
+>
+ parameter.</P
+><P
+>See also <A
+HREF="#LMANNOUNCE"
+><TT
+CLASS="PARAMETER"
+><I
+>lm
+ announce</I
+></TT
+></A
+>.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>lm interval = 60</B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>lm interval = 120</B
+></P
+></DD
+><DT
+><A
+NAME="LOADPRINTERS"
+></A
+>load printers (G)</DT
+><DD
+><P
+>A boolean variable that controls whether all
+ printers in the printcap will be loaded for browsing by default.
+ See the <A
+HREF="#AEN79"
+>printers</A
+> section for
+ more details.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>load printers = yes</B
+></P
+></DD
+><DT
+><A
+NAME="LOCALMASTER"
+></A
+>local master (G)</DT
+><DD
+><P
+>This option allows <A
+HREF="nmbd.8.html"
+TARGET="_top"
+><B
+CLASS="COMMAND"
+> nmbd(8)</B
+></A
+> to try and become a local master browser
+ on a subnet. If set to <TT
+CLASS="CONSTANT"
+>no</TT
+> then <B
+CLASS="COMMAND"
+> nmbd</B
+> will not attempt to become a local master browser
+ on a subnet and will also lose in all browsing elections. By
+ default this value is set to <TT
+CLASS="CONSTANT"
+>yes</TT
+>. Setting this value to <TT
+CLASS="CONSTANT"
+>yes</TT
+> doesn't
+ mean that Samba will <I
+CLASS="EMPHASIS"
+>become</I
+> the local master
+ browser on a subnet, just that <B
+CLASS="COMMAND"
+>nmbd</B
+> will <I
+CLASS="EMPHASIS"
+> participate</I
+> in elections for local master browser.</P
+><P
+>Setting this value to <TT
+CLASS="CONSTANT"
+>no</TT
+> will cause <B
+CLASS="COMMAND"
+>nmbd</B
+>
+ <I
+CLASS="EMPHASIS"
+>never</I
+> to become a local master browser.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>local master = yes</B
+></P
+></DD
+><DT
+><A
+NAME="LOCKDIR"
+></A
+>lock dir (G)</DT
+><DD
+><P
+>Synonym for <A
+HREF="#LOCKDIRECTORY"
+><TT
+CLASS="PARAMETER"
+><I
+> lock directory</I
+></TT
+></A
+>.</P
+></DD
+><DT
+><A
+NAME="LOCKDIRECTORY"
+></A
+>lock directory (G)</DT
+><DD
+><P
+>This option specifies the directory where lock
+ files will be placed. The lock files are used to implement the
+ <A
+HREF="#MAXCONNECTIONS"
+><TT
+CLASS="PARAMETER"
+><I
+>max connections</I
+></TT
+>
+ </A
+> option.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>lock directory = ${prefix}/var/locks</B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>lock directory = /var/run/samba/locks</B
+>
+ </P
+></DD
+><DT
+><A
+NAME="LOCKSPINCOUNT"
+></A
+>lock spin count (G)</DT
+><DD
+><P
+>This parameter controls the number of times
+ that smbd should attempt to gain a byte range lock on the
+ behalf of a client request. Experiments have shown that
+ Windows 2k servers do not reply with a failure if the lock
+ could not be immediately granted, but try a few more times
+ in case the lock could later be aquired. This behavior
+ is used to support PC database formats such as MS Access
+ and FoxPro.
+ </P
+><P
+>Default: <B
+CLASS="COMMAND"
+>lock spin count = 2</B
+>
+ </P
+></DD
+><DT
+><A
+NAME="LOCKSPINTIME"
+></A
+>lock spin time (G)</DT
+><DD
+><P
+>The time in microseconds that smbd should
+ pause before attempting to gain a failed lock. See
+ <A
+HREF="#LOCKSPINCOUNT"
+><TT
+CLASS="PARAMETER"
+><I
+>lock spin
+ count</I
+></TT
+></A
+> for more details.
+ </P
+><P
+>Default: <B
+CLASS="COMMAND"
+>lock spin time = 10</B
+>
+ </P
+></DD
+><DT
+><A
+NAME="LOCKING"
+></A
+>locking (S)</DT
+><DD
+><P
+>This controls whether or not locking will be
+ performed by the server in response to lock requests from the
+ client.</P
+><P
+>If <B
+CLASS="COMMAND"
+>locking = no</B
+>, all lock and unlock
+ requests will appear to succeed and all lock queries will report
+ that the file in question is available for locking.</P
+><P
+>If <B
+CLASS="COMMAND"
+>locking = yes</B
+>, real locking will be performed
+ by the server.</P
+><P
+>This option <I
+CLASS="EMPHASIS"
+>may</I
+> be useful for read-only
+ filesystems which <I
+CLASS="EMPHASIS"
+>may</I
+> not need locking (such as
+ CDROM drives), although setting this parameter of <TT
+CLASS="CONSTANT"
+>no</TT
+>
+ is not really recommended even in this case.</P
+><P
+>Be careful about disabling locking either globally or in a
+ specific service, as lack of locking may result in data corruption.
+ You should never need to set this parameter.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>locking = yes</B
+></P
+></DD
+><DT
+><A
+NAME="LOGFILE"
+></A
+>log file (G)</DT
+><DD
+><P
+>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
+ you to have separate log files for each user or machine.</P
+><P
+>Example: <B
+CLASS="COMMAND"
+>log file = /usr/local/samba/var/log.%m
+ </B
+></P
+></DD
+><DT
+><A
+NAME="LOGLEVEL"
+></A
+>log level (G)</DT
+><DD
+><P
+>The value of the parameter (a astring) allows
+ the debug level (logging level) to be specified in the
+ <TT
+CLASS="FILENAME"
+>smb.conf</TT
+> file. This parameter has been
+ extended since the 2.2.x series, now it allow to specify the debug
+ level for multiple debug classes. This is to give greater
+ flexibility in the configuration of the system.</P
+><P
+>The default will be the log level specified on
+ the command line or level zero if none was specified.</P
+><P
+>Example: <B
+CLASS="COMMAND"
+>log level = 3 passdb:5 auth:10 winbind:2
+ </B
+></P
+></DD
+><DT
+><A
+NAME="LOGONDRIVE"
+></A
+>logon drive (G)</DT
+><DD
+><P
+>This parameter specifies the local path to
+ which the home directory will be connected (see <A
+HREF="#LOGONHOME"
+><TT
+CLASS="PARAMETER"
+><I
+>logon home</I
+></TT
+></A
+>)
+ and is only used by NT Workstations. </P
+><P
+>Note that this option is only useful if Samba is set up as a
+ logon server.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>logon drive = z:</B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>logon drive = h:</B
+></P
+></DD
+><DT
+><A
+NAME="LOGONHOME"
+></A
+>logon home (G)</DT
+><DD
+><P
+>This parameter specifies the home directory
+ location when a Win95/98 or NT Workstation logs into a Samba PDC.
+ It allows you to do </P
+><P
+><TT
+CLASS="PROMPT"
+>C:\&#62; </TT
+><TT
+CLASS="USERINPUT"
+><B
+>NET USE H: /HOME</B
+></TT
+>
+ </P
+><P
+>from a command prompt, for example.</P
+><P
+>This option takes the standard substitutions, allowing
+ you to have separate logon scripts for each user or machine.</P
+><P
+>This parameter can be used with Win9X workstations to ensure
+ that roaming profiles are stored in a subdirectory of the user's
+ home directory. This is done in the following way:</P
+><P
+><B
+CLASS="COMMAND"
+>logon home = \\%N\%U\profile</B
+></P
+><P
+>This tells Samba to return the above string, with
+ substitutions made when a client requests the info, generally
+ in a NetUserGetInfo request. Win9X clients truncate the info to
+ \\server\share when a user does <B
+CLASS="COMMAND"
+>net use /home</B
+>
+ but use the whole string when dealing with profiles.</P
+><P
+>Note that in prior versions of Samba, the <A
+HREF="#LOGONPATH"
+> <TT
+CLASS="PARAMETER"
+><I
+>logon path</I
+></TT
+></A
+> was returned rather than
+ <TT
+CLASS="PARAMETER"
+><I
+>logon home</I
+></TT
+>. This broke <B
+CLASS="COMMAND"
+>net use
+ /home</B
+> but allowed profiles outside the home directory.
+ The current implementation is correct, and can be used for
+ profiles if you use the above trick.</P
+><P
+>This option is only useful if Samba is set up as a logon
+ server.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>logon home = "\\%N\%U"</B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>logon home = "\\remote_smb_server\%U"</B
+>
+ </P
+></DD
+><DT
+><A
+NAME="LOGONPATH"
+></A
+>logon path (G)</DT
+><DD
+><P
+>This parameter specifies the home directory
+ where roaming profiles (NTuser.dat etc files for Windows NT) are
+ stored. Contrary to previous versions of these manual pages, it has
+ nothing to do with Win 9X roaming profiles. To find out how to
+ handle roaming profiles for Win 9X system, see the <A
+HREF="#LOGONHOME"
+> <TT
+CLASS="PARAMETER"
+><I
+>logon home</I
+></TT
+></A
+> parameter.</P
+><P
+>This option takes the standard substitutions, allowing you
+ to have separate logon scripts for each user or machine. It also
+ specifies the directory from which the "Application Data",
+ (<TT
+CLASS="FILENAME"
+>desktop</TT
+>, <TT
+CLASS="FILENAME"
+>start menu</TT
+>,
+ <TT
+CLASS="FILENAME"
+>network neighborhood</TT
+>, <TT
+CLASS="FILENAME"
+>programs</TT
+>
+ and other folders, and their contents, are loaded and displayed on
+ your Windows NT client.</P
+><P
+>The share and the path must be readable by the user for
+ the preferences and directories to be loaded onto the Windows NT
+ client. The share must be writeable when the user logs in for the first
+ time, in order that the Windows NT client can create the NTuser.dat
+ and other directories.</P
+><P
+>Thereafter, the directories and any of the contents can,
+ if required, be made read-only. It is not advisable that the
+ NTuser.dat file be made read-only - rename it to NTuser.man to
+ achieve the desired effect (a <I
+CLASS="EMPHASIS"
+>MAN</I
+>datory
+ profile). </P
+><P
+>Windows clients can sometimes maintain a connection to
+ the [homes] share, even though there is no user logged in.
+ Therefore, it is vital that the logon path does not include a
+ reference to the homes share (i.e. setting this parameter to
+ \%N\%U\profile_path will cause problems).</P
+><P
+>This option takes the standard substitutions, allowing
+ you to have separate logon scripts for each user or machine.</P
+><P
+>Note that this option is only useful if Samba is set up
+ as a logon server.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>logon path = \\%N\%U\profile</B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>logon path = \\PROFILESERVER\PROFILE\%U</B
+></P
+></DD
+><DT
+><A
+NAME="LOGONSCRIPT"
+></A
+>logon script (G)</DT
+><DD
+><P
+>This parameter specifies the batch file (.bat) or
+ NT command file (.cmd) to be downloaded and run on a machine when
+ a user successfully logs in. The file must contain the DOS
+ style CR/LF line endings. Using a DOS-style editor to create the
+ file is recommended.</P
+><P
+>The script must be a relative path to the [netlogon]
+ service. If the [netlogon] service specifies a <A
+HREF="#PATH"
+> <TT
+CLASS="PARAMETER"
+><I
+>path</I
+></TT
+></A
+> of <TT
+CLASS="FILENAME"
+>/usr/local/samba/netlogon
+ </TT
+>, and <B
+CLASS="COMMAND"
+>logon script = STARTUP.BAT</B
+>, then
+ the file that will be downloaded is:</P
+><P
+><TT
+CLASS="FILENAME"
+>/usr/local/samba/netlogon/STARTUP.BAT</TT
+></P
+><P
+>The contents of the batch file are entirely your choice. A
+ suggested command would be to add <B
+CLASS="COMMAND"
+>NET TIME \\SERVER /SET
+ /YES</B
+>, to force every machine to synchronize clocks with
+ the same time server. Another use would be to add <B
+CLASS="COMMAND"
+>NET USE
+ U: \\SERVER\UTILS</B
+> for commonly used utilities, or <B
+CLASS="COMMAND"
+> NET USE Q: \\SERVER\ISO9001_QA</B
+> for example.</P
+><P
+>Note that it is particularly important not to allow write
+ access to the [netlogon] share, or to grant users write permission
+ on the batch files in a secure environment, as this would allow
+ the batch files to be arbitrarily modified and security to be
+ breached.</P
+><P
+>This option takes the standard substitutions, allowing you
+ to have separate logon scripts for each user or machine.</P
+><P
+>This option is only useful if Samba is set up as a logon
+ server.</P
+><P
+>Default: <I
+CLASS="EMPHASIS"
+>no logon script defined</I
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>logon script = scripts\%U.bat</B
+></P
+></DD
+><DT
+><A
+NAME="LPPAUSECOMMAND"
+></A
+>lppause command (S)</DT
+><DD
+><P
+>This parameter specifies the command to be
+ executed on the server host in order to stop printing or spooling
+ a specific print job.</P
+><P
+>This command should be a program or script which takes
+ a printer name and job number to pause the print job. One way
+ of implementing this is by using job priorities, where jobs
+ having a too low priority won't be sent to the printer.</P
+><P
+>If a <TT
+CLASS="PARAMETER"
+><I
+>%p</I
+></TT
+> is given then the printer name
+ is put in its place. A <TT
+CLASS="PARAMETER"
+><I
+>%j</I
+></TT
+> is replaced with
+ the job number (an integer). On HPUX (see <TT
+CLASS="PARAMETER"
+><I
+>printing=hpux
+ </I
+></TT
+>), if the <TT
+CLASS="PARAMETER"
+><I
+>-p%p</I
+></TT
+> option is added
+ to the lpq command, the job will show up with the correct status, i.e.
+ if the job priority is lower than the set fence priority it will
+ have the PAUSED status, whereas if the priority is equal or higher it
+ will have the SPOOLED or PRINTING status.</P
+><P
+>Note that it is good practice to include the absolute path
+ in the lppause command as the PATH may not be available to the server.</P
+><P
+>See also the <A
+HREF="#PRINTING"
+><TT
+CLASS="PARAMETER"
+><I
+>printing
+ </I
+></TT
+></A
+> parameter.</P
+><P
+>Default: Currently no default value is given to
+ this string, unless the value of the <TT
+CLASS="PARAMETER"
+><I
+>printing</I
+></TT
+>
+ parameter is <TT
+CLASS="CONSTANT"
+>SYSV</TT
+>, in which case the default is :</P
+><P
+><B
+CLASS="COMMAND"
+>lp -i %p-%j -H hold</B
+></P
+><P
+>or if the value of the <TT
+CLASS="PARAMETER"
+><I
+>printing</I
+></TT
+> parameter
+ is <TT
+CLASS="CONSTANT"
+>SOFTQ</TT
+>, then the default is:</P
+><P
+><B
+CLASS="COMMAND"
+>qstat -s -j%j -h</B
+></P
+><P
+>Example for HPUX: <B
+CLASS="COMMAND"
+>lppause command = /usr/bin/lpalt
+ %p-%j -p0</B
+></P
+></DD
+><DT
+><A
+NAME="LPQCACHETIME"
+></A
+>lpq cache time (G)</DT
+><DD
+><P
+>This controls how long lpq info will be cached
+ for to prevent the <B
+CLASS="COMMAND"
+>lpq</B
+> command being called too
+ often. A separate cache is kept for each variation of the <B
+CLASS="COMMAND"
+> lpq</B
+> command used by the system, so if you use different
+ <B
+CLASS="COMMAND"
+>lpq</B
+> commands for different users then they won't
+ share cache information.</P
+><P
+>The cache files are stored in <TT
+CLASS="FILENAME"
+>/tmp/lpq.xxxx</TT
+>
+ where xxxx is a hash of the <B
+CLASS="COMMAND"
+>lpq</B
+> command in use.</P
+><P
+>The default is 10 seconds, meaning that the cached results
+ of a previous identical <B
+CLASS="COMMAND"
+>lpq</B
+> command will be used
+ if the cached data is less than 10 seconds old. A large value may
+ be advisable if your <B
+CLASS="COMMAND"
+>lpq</B
+> command is very slow.</P
+><P
+>A value of 0 will disable caching completely.</P
+><P
+>See also the <A
+HREF="#PRINTING"
+><TT
+CLASS="PARAMETER"
+><I
+>printing
+ </I
+></TT
+></A
+> parameter.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>lpq cache time = 10</B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>lpq cache time = 30</B
+></P
+></DD
+><DT
+><A
+NAME="LPQCOMMAND"
+></A
+>lpq command (S)</DT
+><DD
+><P
+>This parameter specifies the command to be
+ executed on the server host in order to obtain <B
+CLASS="COMMAND"
+>lpq
+ </B
+>-style printer status information.</P
+><P
+>This command should be a program or script which
+ takes a printer name as its only parameter and outputs printer
+ status information.</P
+><P
+>Currently nine styles of printer status information
+ are supported; BSD, AIX, LPRNG, PLP, SYSV, HPUX, QNX, CUPS, and SOFTQ.
+ This covers most UNIX systems. You control which type is expected
+ using the <TT
+CLASS="PARAMETER"
+><I
+>printing =</I
+></TT
+> option.</P
+><P
+>Some clients (notably Windows for Workgroups) may not
+ correctly send the connection number for the printer they are
+ requesting status information about. To get around this, the
+ server reports on the first printer service connected to by the
+ client. This only happens if the connection number sent is invalid.</P
+><P
+>If a <TT
+CLASS="PARAMETER"
+><I
+>%p</I
+></TT
+> is given then the printer name
+ is put in its place. Otherwise it is placed at the end of the
+ command.</P
+><P
+>Note that it is good practice to include the absolute path
+ in the <TT
+CLASS="PARAMETER"
+><I
+>lpq command</I
+></TT
+> as the <TT
+CLASS="ENVAR"
+>$PATH
+ </TT
+> may not be available to the server. When compiled with
+ the CUPS libraries, no <TT
+CLASS="PARAMETER"
+><I
+>lpq command</I
+></TT
+> is
+ needed because smbd will make a library call to obtain the
+ print queue listing.</P
+><P
+>See also the <A
+HREF="#PRINTING"
+><TT
+CLASS="PARAMETER"
+><I
+>printing
+ </I
+></TT
+></A
+> parameter.</P
+><P
+>Default: <I
+CLASS="EMPHASIS"
+>depends on the setting of <TT
+CLASS="PARAMETER"
+><I
+> printing</I
+></TT
+></I
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>lpq command = /usr/bin/lpq -P%p</B
+></P
+></DD
+><DT
+><A
+NAME="LPRESUMECOMMAND"
+></A
+>lpresume command (S)</DT
+><DD
+><P
+>This parameter specifies the command to be
+ executed on the server host in order to restart or continue
+ printing or spooling a specific print job.</P
+><P
+>This command should be a program or script which takes
+ a printer name and job number to resume the print job. See
+ also the <A
+HREF="#LPPAUSECOMMAND"
+><TT
+CLASS="PARAMETER"
+><I
+>lppause command
+ </I
+></TT
+></A
+> parameter.</P
+><P
+>If a <TT
+CLASS="PARAMETER"
+><I
+>%p</I
+></TT
+> is given then the printer name
+ is put in its place. A <TT
+CLASS="PARAMETER"
+><I
+>%j</I
+></TT
+> is replaced with
+ the job number (an integer).</P
+><P
+>Note that it is good practice to include the absolute path
+ in the <TT
+CLASS="PARAMETER"
+><I
+>lpresume command</I
+></TT
+> as the PATH may not
+ be available to the server.</P
+><P
+>See also the <A
+HREF="#PRINTING"
+><TT
+CLASS="PARAMETER"
+><I
+>printing
+ </I
+></TT
+></A
+> parameter.</P
+><P
+>Default: Currently no default value is given
+ to this string, unless the value of the <TT
+CLASS="PARAMETER"
+><I
+>printing</I
+></TT
+>
+ parameter is <TT
+CLASS="CONSTANT"
+>SYSV</TT
+>, in which case the default is :</P
+><P
+><B
+CLASS="COMMAND"
+>lp -i %p-%j -H resume</B
+></P
+><P
+>or if the value of the <TT
+CLASS="PARAMETER"
+><I
+>printing</I
+></TT
+> parameter
+ is <TT
+CLASS="CONSTANT"
+>SOFTQ</TT
+>, then the default is:</P
+><P
+><B
+CLASS="COMMAND"
+>qstat -s -j%j -r</B
+></P
+><P
+>Example for HPUX: <B
+CLASS="COMMAND"
+>lpresume command = /usr/bin/lpalt
+ %p-%j -p2</B
+></P
+></DD
+><DT
+><A
+NAME="LPRMCOMMAND"
+></A
+>lprm command (S)</DT
+><DD
+><P
+>This parameter specifies the command to be
+ executed on the server host in order to delete a print job.</P
+><P
+>This command should be a program or script which takes
+ a printer name and job number, and deletes the print job.</P
+><P
+>If a <TT
+CLASS="PARAMETER"
+><I
+>%p</I
+></TT
+> is given then the printer name
+ is put in its place. A <TT
+CLASS="PARAMETER"
+><I
+>%j</I
+></TT
+> is replaced with
+ the job number (an integer).</P
+><P
+>Note that it is good practice to include the absolute
+ path in the <TT
+CLASS="PARAMETER"
+><I
+>lprm command</I
+></TT
+> as the PATH may not be
+ available to the server.</P
+><P
+>See also the <A
+HREF="#PRINTING"
+><TT
+CLASS="PARAMETER"
+><I
+>printing
+ </I
+></TT
+></A
+> parameter.</P
+><P
+>Default: <I
+CLASS="EMPHASIS"
+>depends on the setting of <TT
+CLASS="PARAMETER"
+><I
+>printing
+ </I
+></TT
+></I
+></P
+><P
+>Example 1: <B
+CLASS="COMMAND"
+>lprm command = /usr/bin/lprm -P%p %j
+ </B
+></P
+><P
+>Example 2: <B
+CLASS="COMMAND"
+>lprm command = /usr/bin/cancel %p-%j
+ </B
+></P
+></DD
+><DT
+><A
+NAME="MACHINEPASSWORDTIMEOUT"
+></A
+>machine password timeout (G)</DT
+><DD
+><P
+>If a Samba server is a member of a Windows
+ NT Domain (see the <A
+HREF="#SECURITYEQUALSDOMAIN"
+>security = domain</A
+>)
+ parameter) then periodically a running <A
+HREF="smbd.8.html"
+TARGET="_top"
+> smbd(8)</A
+> process will try and change the MACHINE ACCOUNT
+ PASSWORD stored in the TDB called <TT
+CLASS="FILENAME"
+>private/secrets.tdb
+ </TT
+>. This parameter specifies how often this password
+ will be changed, in seconds. The default is one week (expressed in
+ seconds), the same as a Windows NT Domain member server.</P
+><P
+>See also <A
+HREF="smbpasswd.8.html"
+TARGET="_top"
+><B
+CLASS="COMMAND"
+>smbpasswd(8)
+ </B
+></A
+>, and the <A
+HREF="#SECURITYEQUALSDOMAIN"
+> security = domain</A
+>) parameter.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>machine password timeout = 604800</B
+></P
+></DD
+><DT
+><A
+NAME="MAGICOUTPUT"
+></A
+>magic output (S)</DT
+><DD
+><P
+>This parameter specifies the name of a file
+ which will contain output created by a magic script (see the
+ <A
+HREF="#MAGICSCRIPT"
+><TT
+CLASS="PARAMETER"
+><I
+>magic script</I
+></TT
+></A
+>
+ parameter below).</P
+><P
+>Warning: If two clients use the same <TT
+CLASS="PARAMETER"
+><I
+>magic script
+ </I
+></TT
+> in the same directory the output file content
+ is undefined.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>magic output = &#60;magic script name&#62;.out
+ </B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>magic output = myfile.txt</B
+></P
+></DD
+><DT
+><A
+NAME="MAGICSCRIPT"
+></A
+>magic script (S)</DT
+><DD
+><P
+>This parameter specifies the name of a file which,
+ if opened, will be executed by the server when the file is closed.
+ This allows a UNIX script to be sent to the Samba host and
+ executed on behalf of the connected user.</P
+><P
+>Scripts executed in this way will be deleted upon
+ completion assuming that the user has the appropriate level
+ of privilege and the file permissions allow the deletion.</P
+><P
+>If the script generates output, output will be sent to
+ the file specified by the <A
+HREF="#MAGICOUTPUT"
+><TT
+CLASS="PARAMETER"
+><I
+> magic output</I
+></TT
+></A
+> parameter (see above).</P
+><P
+>Note that some shells are unable to interpret scripts
+ containing CR/LF instead of CR as
+ the end-of-line marker. Magic scripts must be executable
+ <I
+CLASS="EMPHASIS"
+>as is</I
+> on the host, which for some hosts and
+ some shells will require filtering at the DOS end.</P
+><P
+>Magic scripts are <I
+CLASS="EMPHASIS"
+>EXPERIMENTAL</I
+> and
+ should <I
+CLASS="EMPHASIS"
+>NOT</I
+> be relied upon.</P
+><P
+>Default: <I
+CLASS="EMPHASIS"
+>None. Magic scripts disabled.</I
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>magic script = user.csh</B
+></P
+></DD
+><DT
+><A
+NAME="MANGLECASE"
+></A
+>mangle case (S)</DT
+><DD
+><P
+>See the section on <A
+HREF="#AEN205"
+> NAME MANGLING</A
+></P
+><P
+>Default: <B
+CLASS="COMMAND"
+>mangle case = no</B
+></P
+></DD
+><DT
+><A
+NAME="MANGLEDMAP"
+></A
+>mangled map (S)</DT
+><DD
+><P
+>This is for those who want to directly map UNIX
+ file names which cannot be represented on Windows/DOS. The mangling
+ of names is not always what is needed. In particular you may have
+ documents with file extensions that differ between DOS and UNIX.
+ For example, under UNIX it is common to use <TT
+CLASS="FILENAME"
+>.html</TT
+>
+ for HTML files, whereas under Windows/DOS <TT
+CLASS="FILENAME"
+>.htm</TT
+>
+ is more commonly used.</P
+><P
+>So to map <TT
+CLASS="FILENAME"
+>html</TT
+> to <TT
+CLASS="FILENAME"
+>htm</TT
+>
+ you would use:</P
+><P
+><B
+CLASS="COMMAND"
+>mangled map = (*.html *.htm)</B
+></P
+><P
+>One very useful case is to remove the annoying <TT
+CLASS="FILENAME"
+>;1
+ </TT
+> off the ends of filenames on some CDROMs (only visible
+ under some UNIXes). To do this use a map of (*;1 *;).</P
+><P
+>Default: <I
+CLASS="EMPHASIS"
+>no mangled map</I
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>mangled map = (*;1 *;)</B
+></P
+></DD
+><DT
+><A
+NAME="MANGLEDNAMES"
+></A
+>mangled names (S)</DT
+><DD
+><P
+>This controls whether non-DOS names under UNIX
+ should be mapped to DOS-compatible names ("mangled") and made visible,
+ or whether non-DOS names should simply be ignored.</P
+><P
+>See the section on <A
+HREF="#AEN205"
+> NAME MANGLING</A
+> for details on how to control the mangling process.</P
+><P
+>If mangling is used then the mangling algorithm is as follows:</P
+><P
+></P
+><UL
+><LI
+><P
+>The first (up to) five alphanumeric characters
before the rightmost dot of the filename are preserved, forced
to upper case, and appear as the first (up to) five characters
- of the mangled name.</p></li><li><p>A tilde &quot;~&quot; is appended to the first part of the mangled
+ of the mangled name.</P
+></LI
+><LI
+><P
+>A tilde "~" is appended to the first part of the mangled
name, followed by a two-character unique sequence, based on the
original root name (i.e., the original filename minus its final
extension). The final extension is included in the hash calculation
only if it contains any upper case characters or is longer than three
- characters.</p><p>Note that the character to use may be specified using
- the <a href="#MANGLINGCHAR"><i><tt>mangling char</tt></i>
- </a> option, if you don't like '~'.</p></li><li><p>The first three alphanumeric characters of the final
+ characters.</P
+><P
+>Note that the character to use may be specified using
+ the <A
+HREF="#MANGLINGCHAR"
+><TT
+CLASS="PARAMETER"
+><I
+>mangling char</I
+></TT
+>
+ </A
+> option, if you don't like '~'.</P
+></LI
+><LI
+><P
+>The first three alphanumeric characters of the final
extension are preserved, forced to upper case and appear as the
extension of the mangled name. The final extension is defined as that
part of the original filename after the rightmost dot. If there are no
dots in the filename, the mangled name will have no extension (except
- in the case of &quot;hidden files&quot; - see below).</p></li><li><p>Files whose UNIX name begins with a dot will be
+ in the case of "hidden files" - see below).</P
+></LI
+><LI
+><P
+>Files whose UNIX name begins with a dot will be
presented as DOS hidden files. The mangled name will be created as
- for other filenames, but with the leading dot removed and &quot;___&quot; as
+ for other filenames, but with the leading dot removed and "___" as
its extension regardless of actual original extension (that's three
- underscores).</p></li></ul></div><p>The two-digit hash value consists of upper case alphanumeric characters.</p><p>This algorithm can cause name collisions only if files
- in a directory share the same first five alphanumeric characters.
- The probability of such a clash is 1/1300.</p><p>The name mangling (if enabled) allows a file to be
- copied between UNIX directories from Windows/DOS while retaining
- the long UNIX filename. UNIX files can be renamed to a new extension
- from Windows/DOS and will retain the same basename. Mangled names
- do not change between sessions.</p><p>Default: <b>mangled names = yes</b></p></dd><dt><span class="term"><a name="MANGLINGSTACK"></a>mangling stack (G)</span></dt><dd><p>This parameter controls the number of mangled names
- that should be cached in the Samba server <a href="smbd.8.html">smbd(8)</a>.</p><p>This stack is a list of recently mangled base names
- (extensions are only maintained if they are longer than 3 characters
- or contains upper case characters).</p><p>The larger this value, the more likely it is that mangled
- names can be successfully converted to correct long UNIX names.
- However, large stack sizes will slow most directory accesses. Smaller
- stacks save memory in the server (each stack element costs 256 bytes).
- </p><p>It is not possible to absolutely guarantee correct long
- filenames, so be prepared for some surprises!</p><p>Default: <b>mangled stack = 50</b></p><p>Example: <b>mangled stack = 100</b></p></dd><dt><span class="term"><a name="MANGLINGPREFIX"></a>mangling prefix (G)</span></dt><dd><p> controls the number of prefix
- characters from the original name used when generating
- the mangled names. A larger value will give a weaker
- hash and therefore more name collisions. The minimum
- value is 1 and the maximum value is 6.</p><p>Default: <b>mangle prefix = 1</b></p><p>Example: <b>mangle prefix = 4</b></p></dd><dt><span class="term"><a name="MANGLINGCHAR"></a>mangling char (S)</span></dt><dd><p>This controls what character is used as
- the <span class="emphasis"><em>magic</em></span> character in <a href="#NAMEMANGLINGSECT" title="NAME MANGLING">name mangling</a>. The
- default is a '~' but this may interfere with some software. Use this option to set
- it to whatever you prefer.</p><p>Default: <b>mangling char = ~</b></p><p>Example: <b>mangling char = ^</b></p></dd><dt><span class="term"><a name="MANGLINGMETHOD"></a>mangling method (G)</span></dt><dd><p> controls the algorithm used for the generating
- the mangled names. Can take two different values, &quot;hash&quot; and
- &quot;hash2&quot;. &quot;hash&quot; is the default and is the algorithm that has been
- used in Samba for many years. &quot;hash2&quot; is a newer and considered
- a better algorithm (generates less collisions) in the names.
- However, many Win32 applications store the mangled names and so
- changing to the new algorithm must not be done
- lightly as these applications may break unless reinstalled.</p><p>Default: <b>mangling method = hash2</b></p><p>Example: <b>mangling method = hash</b></p></dd><dt><span class="term"><a name="MAPARCHIVE"></a>map archive (S)</span></dt><dd><p>This controls whether the DOS archive attribute
- should be mapped to the UNIX owner execute bit. The DOS archive bit
- is set when a file has been modified since its last backup. One
- motivation for this option it to keep Samba/your PC from making
- any file it touches from becoming executable under UNIX. This can
- be quite annoying for shared source code, documents, etc...</p><p>Note that this requires the <i><tt>create mask</tt></i>
- parameter to be set such that owner execute bit is not masked out
- (i.e. it must include 100). See the parameter <a href="#CREATEMASK">
- <i><tt>create mask</tt></i></a> for details.</p><p>Default: <b>map archive = yes</b></p></dd><dt><span class="term"><a name="MAPHIDDEN"></a>map hidden (S)</span></dt><dd><p>This controls whether DOS style hidden files
- should be mapped to the UNIX world execute bit.</p><p>Note that this requires the <i><tt>create mask</tt></i>
- to be set such that the world execute bit is not masked out (i.e.
- it must include 001). See the parameter <a href="#CREATEMASK">
- <i><tt>create mask</tt></i></a> for details.</p><p>Default: <b>map hidden = no</b></p></dd><dt><span class="term"><a name="MAPSYSTEM"></a>map system (S)</span></dt><dd><p>This controls whether DOS style system files
- should be mapped to the UNIX group execute bit.</p><p>Note that this requires the <i><tt>create mask</tt></i>
- to be set such that the group execute bit is not masked out (i.e.
- it must include 010). See the parameter <a href="#CREATEMASK">
- <i><tt>create mask</tt></i></a> for details.</p><p>Default: <b>map system = no</b></p></dd><dt><span class="term"><a name="MAPTOGUEST"></a>map to guest (G)</span></dt><dd><p>This parameter is only useful in <a href="#SECURITY">
- security</a> modes other than <i><tt>security = share</tt></i>
- - i.e. <tt>user</tt>, <tt>server</tt>,
- and <tt>domain</tt>.</p><p>This parameter can take three different values, which tell
- <a href="smbd.8.html">smbd(8)</a> what to do with user
- login requests that don't match a valid UNIX user in some way.</p><p>The three settings are :</p><div class="itemizedlist"><ul type="disc"><li><p><tt>Never</tt> - Means user login
- requests with an invalid password are rejected. This is the
- default.</p></li><li><p><tt>Bad User</tt> - Means user
- logins with an invalid password are rejected, unless the username
- does not exist, in which case it is treated as a guest login and
- mapped into the <a href="#GUESTACCOUNT"><i><tt>
- guest account</tt></i></a>.</p></li><li><p><tt>Bad Password</tt> - Means user logins
- with an invalid password are treated as a guest login and mapped
- into the <a href="#GUESTACCOUNT">guest account</a>. Note that
- this can cause problems as it means that any user incorrectly typing
- their password will be silently logged on as &quot;guest&quot; - and
- will not know the reason they cannot access files they think
- they should - there will have been no message given to them
- that they got their password wrong. Helpdesk services will
- <span class="emphasis"><em>hate</em></span> you if you set the <i><tt>map to
- guest</tt></i> parameter this way :-).</p></li></ul></div><p>Note that this parameter is needed to set up &quot;Guest&quot;
- share services when using <i><tt>security</tt></i> modes other than
- share. This is because in these modes the name of the resource being
- requested is <span class="emphasis"><em>not</em></span> sent to the server until after
- the server has successfully authenticated the client so the server
- cannot make authentication decisions at the correct time (connection
- to the share) for &quot;Guest&quot; shares.</p><p>For people familiar with the older Samba releases, this
- parameter maps to the old compile-time setting of the <tt>
- GUEST_SESSSETUP</tt> value in local.h.</p><p>Default: <b>map to guest = Never</b></p><p>Example: <b>map to guest = Bad User</b></p></dd><dt><span class="term"><a name="MAXCONNECTIONS"></a>max connections (S)</span></dt><dd><p>This option allows the number of simultaneous connections to a service to be limited.
- If <i><tt>max connections</tt></i> is greater than 0 then connections
- will be refused if this number of connections to the service are already open. A value
- of zero mean an unlimited number of connections may be made.</p><p>Record lock files are used to implement this feature. The lock files will be stored in
- the directory specified by the <a href="#LOCKDIRECTORY">
- <i><tt>lock directory</tt></i></a> option.</p><p>Default: <b>max connections = 0</b></p><p>Example: <b>max connections = 10</b></p></dd><dt><span class="term"><a name="MAXDISKSIZE"></a>max disk size (G)</span></dt><dd><p>This option allows you to put an upper limit
- on the apparent size of disks. If you set this option to 100
- then all shares will appear to be not larger than 100 MB in
- size.</p><p>Note that this option does not limit the amount of
- data you can put on the disk. In the above case you could still
- store much more than 100 MB on the disk, but if a client ever asks
- for the amount of free disk space or the total disk size then the
- result will be bounded by the amount specified in <i><tt>max
- disk size</tt></i>.</p><p>This option is primarily useful to work around bugs
- in some pieces of software that can't handle very large disks,
- particularly disks over 1GB in size.</p><p>A <i><tt>max disk size</tt></i> of 0 means no limit.</p><p>Default: <b>max disk size = 0</b></p><p>Example: <b>max disk size = 1000</b></p></dd><dt><span class="term"><a name="MAXLOGSIZE"></a>max log size (G)</span></dt><dd><p>This option (an integer in kilobytes) specifies
- the max size the log file should grow to. Samba periodically checks
- the size and if it is exceeded it will rename the file, adding
- a <tt>.old</tt> extension.</p><p>A size of 0 means no limit.</p><p>Default: <b>max log size = 5000</b></p><p>Example: <b>max log size = 1000</b></p></dd><dt><span class="term"><a name="MAXMUX"></a>max mux (G)</span></dt><dd><p>This option controls the maximum number of
- outstanding simultaneous SMB operations that Samba tells the client
- it will allow. You should never need to set this parameter.</p><p>Default: <b>max mux = 50</b></p></dd><dt><span class="term"><a name="MAXOPENFILES"></a>max open files (G)</span></dt><dd><p>This parameter limits the maximum number of
- open files that one <a href="smbd.8.html">smbd(8)</a> file
- serving process may have open for a client at any one time. The
- default for this parameter is set very high (10,000) as Samba uses
- only one bit per unopened file.</p><p>The limit of the number of open files is usually set
- by the UNIX per-process file descriptor limit rather than
- this parameter so you should never need to touch this parameter.</p><p>Default: <b>max open files = 10000</b></p></dd><dt><span class="term"><a name="MAXPRINTJOBS"></a>max print jobs (S)</span></dt><dd><p>This parameter limits the maximum number of
- jobs allowable in a Samba printer queue at any given moment.
- If this number is exceeded, <a href="smbd.8.html">smbd(8)</a> will remote &quot;Out of Space&quot; to the client.
- See all <a href="#TOTALPRINTJOBS"><i><tt>total
- print jobs</tt></i></a>.
- </p><p>Default: <b>max print jobs = 1000</b></p><p>Example: <b>max print jobs = 5000</b></p></dd><dt><span class="term"><a name="MAXPROTOCOL"></a>max protocol (G)</span></dt><dd><p>The value of the parameter (a string) is the highest
- protocol level that will be supported by the server.</p><p>Possible values are :</p><div class="itemizedlist"><ul type="disc"><li><p><tt>CORE</tt>: Earliest version. No
- concept of user names.</p></li><li><p><tt>COREPLUS</tt>: Slight improvements on
- CORE for efficiency.</p></li><li><p><tt>LANMAN1</tt>: First <span class="emphasis"><em>
- modern</em></span> version of the protocol. Long filename
- support.</p></li><li><p><tt>LANMAN2</tt>: Updates to Lanman1 protocol.</p></li><li><p><tt>NT1</tt>: Current up to date version of the protocol.
- Used by Windows NT. Known as CIFS.</p></li></ul></div><p>Normally this option should not be set as the automatic
- negotiation phase in the SMB protocol takes care of choosing
- the appropriate protocol.</p><p>See also <a href="#MINPROTOCOL"><i><tt>min
- protocol</tt></i></a></p><p>Default: <b>max protocol = NT1</b></p><p>Example: <b>max protocol = LANMAN1</b></p></dd><dt><span class="term"><a name="MAXSMBDPROCESSES"></a>max smbd processes (G)</span></dt><dd><p>This parameter limits the maximum number of <a href="smbd.8.html">smbd(8)</a> processes concurrently running on a system and is intended
- as a stopgap to prevent degrading service to clients in the event that the server has insufficient
- resources to handle more than this number of connections. Remember that under normal operating
- conditions, each user will have an <a href="smbd.8.html">smbd(8)</a> associated with him or her to handle connections to all
- shares from a given host.</p><p>Default: <b>max smbd processes = 0</b> ## no limit</p><p>Example: <b>max smbd processes = 1000</b></p></dd><dt><span class="term"><a name="MAXTTL"></a>max ttl (G)</span></dt><dd><p>This option tells <a href="nmbd.8.html">nmbd(8)</a> what the default 'time to live'
- of NetBIOS names should be (in seconds) when <b>nmbd</b> is
- requesting a name using either a broadcast packet or from a WINS server. You should
- never need to change this parameter. The default is 3 days.</p><p>Default: <b>max ttl = 259200</b></p></dd><dt><span class="term"><a name="MAXWINSTTL"></a>max wins ttl (G)</span></dt><dd><p>This option tells <a href="smbd.8.html">smbd(8)</a> when acting as a WINS server (<a href="#WINSSUPPORT">
- <i><tt>wins support = yes</tt></i></a>) what the maximum
- 'time to live' of NetBIOS names that <b>nmbd</b>
- will grant will be (in seconds). You should never need to change this
- parameter. The default is 6 days (518400 seconds).</p><p>See also the <a href="#MINWINSTTL"><i><tt>min
- wins ttl</tt></i></a> parameter.</p><p>Default: <b>max wins ttl = 518400</b></p></dd><dt><span class="term"><a name="MAXXMIT"></a>max xmit (G)</span></dt><dd><p>This option controls the maximum packet size
- that will be negotiated by Samba. The default is 65535, which
- is the maximum. In some cases you may find you get better performance
- with a smaller value. A value below 2048 is likely to cause problems.
- </p><p>Default: <b>max xmit = 65535</b></p><p>Example: <b>max xmit = 8192</b></p></dd><dt><span class="term"><a name="MESSAGECOMMAND"></a>message command (G)</span></dt><dd><p>This specifies what command to run when the
- server receives a WinPopup style message.</p><p>This would normally be a command that would
- deliver the message somehow. How this is to be done is
- up to your imagination.</p><p>An example is:</p><p><b>message command = csh -c 'xedit %s;rm %s' &amp;</b>
- </p><p>This delivers the message using <b>xedit</b>, then
- removes it afterwards. <span class="emphasis"><em>NOTE THAT IT IS VERY IMPORTANT
- THAT THIS COMMAND RETURN IMMEDIATELY</em></span>. That's why I
- have the '&amp;' on the end. If it doesn't return immediately then
- your PCs may freeze when sending messages (they should recover
- after 30 seconds, hopefully).</p><p>All messages are delivered as the global guest user.
- The command takes the standard substitutions, although <i><tt>
- %u</tt></i> won't work (<i><tt>%U</tt></i> may be better
- in this case).</p><p>Apart from the standard substitutions, some additional
- ones apply. In particular:</p><div class="itemizedlist"><ul type="disc"><li><p><i><tt>%s</tt></i> = the filename containing
- the message.</p></li><li><p><i><tt>%t</tt></i> = the destination that
- the message was sent to (probably the server name).</p></li><li><p><i><tt>%f</tt></i> = who the message
- is from.</p></li></ul></div><p>You could make this command send mail, or whatever else
- takes your fancy. Please let us know of any really interesting
- ideas you have.</p><p>Here's a way of sending the messages as mail to root:</p><p><b>message command = /bin/mail -s 'message from %f on
- %m' root &lt; %s; rm %s</b></p><p>If you don't have a message command then the message
- won't be delivered and Samba will tell the sender there was
- an error. Unfortunately WfWg totally ignores the error code
- and carries on regardless, saying that the message was delivered.
- </p><p>If you want to silently delete it then try:</p><p><b>message command = rm %s</b></p><p>Default: <span class="emphasis"><em>no message command</em></span></p><p>Example: <b>message command = csh -c 'xedit %s; rm %s' &amp;</b></p></dd><dt><span class="term"><a name="MINPASSWDLENGTH"></a>min passwd length (G)</span></dt><dd><p>Synonym for <a href="#MINPASSWORDLENGTH">
- <i><tt>min password length</tt></i></a>.
- </p></dd><dt><span class="term"><a name="MINPASSWORDLENGTH"></a>min password length (G)</span></dt><dd><p>This option sets the minimum length in characters of a
- plaintext password that <b>smbd</b> will
- accept when performing UNIX password changing.</p><p>See also <a href="#UNIXPASSWORDSYNC"><i><tt>unix
- password sync</tt></i></a>, <a href="#PASSWDPROGRAM">
- <i><tt>passwd program</tt></i></a> and <a href="#PASSWDCHATDEBUG">
- <i><tt>passwd chat debug</tt></i></a>.</p><p>Default: <b>min password length = 5</b></p></dd><dt><span class="term"><a name="MINPRINTSPACE"></a>min print space (S)</span></dt><dd><p>This sets the minimum amount of free disk
- space that must be available before a user will be able to spool
- a print job. It is specified in kilobytes. The default is 0, which
- means a user can always spool a print job.</p><p>See also the <a href="#PRINTING"><i><tt>printing
- </tt></i></a> parameter.</p><p>Default: <b>min print space = 0</b></p><p>Example: <b>min print space = 2000</b></p></dd><dt><span class="term"><a name="MINPROTOCOL"></a>min protocol (G)</span></dt><dd><p>The value of the parameter (a string) is the
- lowest SMB protocol dialect than Samba will support. Please refer
- to the <a href="#MAXPROTOCOL"><i><tt>max protocol</tt></i></a>
- parameter for a list of valid protocol names and a brief description
- of each. You may also wish to refer to the C source code in
- <tt>source/smbd/negprot.c</tt> for a listing of known protocol
- dialects supported by clients.</p><p>If you are viewing this parameter as a security measure, you should
- also refer to the <a href="#LANMANAUTH"><i><tt>lanman
- auth</tt></i></a> parameter. Otherwise, you should never need
- to change this parameter.</p><p>Default : <b>min protocol = CORE</b></p><p>Example : <b>min protocol = NT1</b> # disable DOS clients</p></dd><dt><span class="term"><a name="MINWINSTTL"></a>min wins ttl (G)</span></dt><dd><p>This option tells <a href="nmbd.8.html">nmbd(8)</a>
- when acting as a WINS server (<a href="#WINSSUPPORT"><i><tt>
- wins support = yes</tt></i></a>) what the minimum 'time to live'
- of NetBIOS names that <b>nmbd</b> will grant will be (in
- seconds). You should never need to change this parameter. The default
- is 6 hours (21600 seconds).</p><p>Default: <b>min wins ttl = 21600</b></p></dd><dt><span class="term"><a name="MSDFSPROXY"></a>msdfs proxy (S)</span></dt><dd><p>This parameter indicates that the share is a
- stand-in for another CIFS share whose location is specified by
- the value of the parameter. When clients attempt to connect to
- this share, they are redirected to the proxied share using
- the SMB-Dfs protocol.</p><p>Only Dfs roots can act as proxy shares. Take a look at the
- <a href="#MSDFSROOT"><i><tt>msdfs root</tt></i></a>
- and <a href="#HOSTMSDFS"><i><tt>host msdfs</tt></i></a>
- options to find out how to set up a Dfs root share.</p><p>Example: <b>msdfs proxy = \\\\otherserver\\someshare</b></p></dd><dt><span class="term"><a name="MSDFSROOT"></a>msdfs root (S)</span></dt><dd><p>This boolean parameter is only available if
- Samba is configured and compiled with the <b>
- --with-msdfs</b> option. If set to <tt>yes</tt>,
- Samba treats the share as a Dfs root and allows clients to browse
- the distributed file system tree rooted at the share directory.
- Dfs links are specified in the share directory by symbolic
- links of the form <tt>msdfs:serverA\\shareA,serverB\\shareB</tt>
- and so on. For more information on setting up a Dfs tree
- on Samba, refer to <a href="msdfs.html" target="_top">&quot;Hosting a Microsoft
- Distributed File System tree on Samba&quot;</a> document.</p><p>See also <a href="#HOSTMSDFS"><i><tt>host msdfs</tt></i></a></p><p>Default: <b>msdfs root = no</b></p></dd><dt><span class="term"><a name="NAMECACHETIMEOUT"></a>name cache timeout (G)</span></dt><dd><p>Specifies the number of seconds it takes before
- entries in samba's hostname resolve cache time out. If
- the timeout is set to 0. the caching is disabled.
- </p><p>Default: <b>name cache timeout = 660</b></p><p>Example: <b>name cache timeout = 0</b></p></dd><dt><span class="term"><a name="NAMERESOLVEORDER"></a>name resolve order (G)</span></dt><dd><p>This option is used by the programs in the Samba
- suite to determine what naming services to use and in what order
- to resolve host names to IP addresses. The option takes a space
- separated string of name resolution options.</p><p>The options are: &quot;lmhosts&quot;, &quot;host&quot;,
- &quot;wins&quot; and &quot;bcast&quot;. They cause names to be
- resolved as follows:</p><div class="itemizedlist"><ul type="disc"><li><p><tt>lmhosts</tt> : Lookup an IP
- address in the Samba lmhosts file. If the line in lmhosts has
- no name type attached to the NetBIOS name (see the <a href="lmhosts.5.html" target="_top">lmhosts(5)</a> for details) then
- any name type matches for lookup.</p></li><li><p><tt>host</tt> : Do a standard host
- name to IP address resolution, using the system <tt>/etc/hosts
- </tt>, NIS, or DNS lookups. This method of name resolution
- is operating system depended for instance on IRIX or Solaris this
- may be controlled by the <tt>/etc/nsswitch.conf</tt>
- file. Note that this method is only used if the NetBIOS name
- type being queried is the 0x20 (server) name type, otherwise
- it is ignored.</p></li><li><p><tt>wins</tt> : Query a name with
- the IP address listed in the <a href="#WINSSERVER"><i><tt>
- wins server</tt></i></a> parameter. If no WINS server has
- been specified this method will be ignored.</p></li><li><p><tt>bcast</tt> : Do a broadcast on
- each of the known local interfaces listed in the <a href="#INTERFACES"><i><tt>interfaces</tt></i></a>
- parameter. This is the least reliable of the name resolution
- methods as it depends on the target host being on a locally
- connected subnet.</p></li></ul></div><p>Default: <b>name resolve order = lmhosts host wins bcast</b></p><p>Example: <b>name resolve order = lmhosts bcast host</b></p><p>This will cause the local lmhosts file to be examined
- first, followed by a broadcast attempt, followed by a normal
- system hostname lookup.</p></dd><dt><span class="term"><a name="NETBIOSALIASES"></a>netbios aliases (G)</span></dt><dd><p>This is a list of NetBIOS names that <a href="nmbd.8.html" target="_top">nmbd(8)</a> will
- advertise as additional names by which the Samba server is known. This allows one machine
- to appear in browse lists under multiple names. If a machine is acting as a browse server
- or logon server none of these names will be advertised as either browse server or logon
- servers, only the primary name of the machine will be advertised with these capabilities.
- </p><p>See also <a href="#NETBIOSNAME"><i><tt>netbios
- name</tt></i></a>.</p><p>Default: <span class="emphasis"><em>empty string (no additional names)</em></span></p><p>Example: <b>netbios aliases = TEST TEST1 TEST2</b></p></dd><dt><span class="term"><a name="NETBIOSNAME"></a>netbios name (G)</span></dt><dd><p>This sets the NetBIOS name by which a Samba
- server is known. By default it is the same as the first component
- of the host's DNS name. If a machine is a browse server or
- logon server this name (or the first component
- of the hosts DNS name) will be the name that these services are
- advertised under.</p><p>See also <a href="#NETBIOSALIASES"><i><tt>netbios
- aliases</tt></i></a>.</p><p>Default: <span class="emphasis"><em>machine DNS name</em></span></p><p>Example: <b>netbios name = MYNAME</b></p></dd><dt><span class="term"><a name="NETBIOSSCOPE"></a>netbios scope (G)</span></dt><dd><p>This sets the NetBIOS scope that Samba will
- operate under. This should not be set unless every machine
- on your LAN also sets this value.</p></dd><dt><span class="term"><a name="NISHOMEDIR"></a>nis homedir (G)</span></dt><dd><p>Get the home share server from a NIS map. For
- UNIX systems that use an automounter, the user's home directory
- will often be mounted on a workstation on demand from a remote
- server. </p><p>When the Samba logon server is not the actual home directory
- server, but is mounting the home directories via NFS then two
- network hops would be required to access the users home directory
- if the logon server told the client to use itself as the SMB server
- for home directories (one over SMB and one over NFS). This can
- be very slow.</p><p>This option allows Samba to return the home share as
- being on a different server to the logon server and as
- long as a Samba daemon is running on the home directory server,
- it will be mounted on the Samba client directly from the directory
- server. When Samba is returning the home share to the client, it
- will consult the NIS map specified in <a href="#HOMEDIRMAP">
- <i><tt>homedir map</tt></i></a> and return the server
- listed there.</p><p>Note that for this option to work there must be a working
- NIS system and the Samba server with this option must also
- be a logon server.</p><p>Default: <b>nis homedir = no</b></p></dd><dt><span class="term"><a name="NONUNIXACCOUNTRANGE"></a>non unix account range (G)</span></dt><dd><p>The non unix account range parameter specifies
- the range of 'user ids' that are allocated by the various 'non unix
- account' passdb backends. These backends allow
- the storage of passwords for users who don't exist in /etc/passwd.
- This is most often used for machine account creation.
- This range of ids should have no existing local or NIS users within
- it as strange conflicts can occur otherwise.</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>These userids never appear on the system and Samba will never
- 'become' these users. They are used only to ensure that the algorithmic
- RID mapping does not conflict with normal users.
- </p></div><p>Default: <b>non unix account range = &lt;empty string&gt;</b></p><p>Example: <b>non unix account range = 10000-20000</b></p></dd><dt><span class="term"><a name="NTACLSUPPORT"></a>nt acl support (S)</span></dt><dd><p>This boolean parameter controls whether <a href="smbd.8.html">smbd(8)</a> will attempt to map
- UNIX permissions into Windows NT access control lists.
- This parameter was formally a global parameter in releases
- prior to 2.2.2.</p><p>Default: <b>nt acl support = yes</b></p></dd><dt><span class="term"><a name="NTLMAUTH"></a>ntlm auth (G)</span></dt><dd><p>This parameter determines whether or not <a href="smbd.8.html">smbd(8)</a> will attempt to authenticate users using the NTLM password hash.
- If disabled, only the lanman password hashes will be used.</p><p>Please note that at least this option or <b>lanman auth</b> should
- be enabled in order to be able to log in.</p><p>Default : <b>ntlm auth = yes</b></p></dd><dt><span class="term"><a name="NTPIPESUPPORT"></a>nt pipe support (G)</span></dt><dd><p>This boolean parameter controls whether
- <a href="smbd.8.html">smbd(8)</a> will allow Windows NT
- clients to connect to the NT SMB specific <tt>IPC$</tt>
- pipes. This is a developer debugging option and can be left
- alone.</p><p>Default: <b>nt pipe support = yes</b></p></dd><dt><span class="term"><a name="NTSTATUSSUPPORT"></a>nt status support (G)</span></dt><dd><p>This boolean parameter controls whether <a href="smbd.8.html">smbd(8)</a> will negotiate NT specific status
- support with Windows NT/2k/XP clients. This is a developer debugging option and should be left alone.
- If this option is set to <tt>no</tt> then Samba offers
- exactly the same DOS error codes that versions prior to Samba 2.2.3
- reported.</p><p>You should not need to ever disable this parameter.</p><p>Default: <b>nt status support = yes</b></p></dd><dt><span class="term"><a name="NULLPASSWORDS"></a>null passwords (G)</span></dt><dd><p>Allow or disallow client access to accounts that have null passwords. </p><p>See also <a href="smbpasswd.5.html">smbpasswd(5)</a>.</p><p>Default: <b>null passwords = no</b></p></dd><dt><span class="term"><a name="OBEYPAMRESTRICTIONS"></a>obey pam restrictions (G)</span></dt><dd><p>When Samba 3.0 is configured to enable PAM support
- (i.e. --with-pam), this parameter will control whether or not Samba
- should obey PAM's account and session management directives. The
- default behavior is to use PAM for clear text authentication only
- and to ignore any account or session management. Note that Samba
- always ignores PAM for authentication in the case of <a href="#ENCRYPTPASSWORDS">
- <i><tt>encrypt passwords = yes</tt></i></a>. The reason
- is that PAM modules cannot support the challenge/response
- authentication mechanism needed in the presence of SMB password encryption.
- </p><p>Default: <b>obey pam restrictions = no</b></p></dd><dt><span class="term"><a name="ONLYGUEST"></a>only guest (S)</span></dt><dd><p>A synonym for <a href="#GUESTONLY"><i><tt>
- guest only</tt></i></a>.</p></dd><dt><span class="term"><a name="ONLYUSER"></a>only user (S)</span></dt><dd><p>This is a boolean option that controls whether
- connections with usernames not in the <i><tt>user</tt></i>
- list will be allowed. By default this option is disabled so that a
- client can supply a username to be used by the server. Enabling
- this parameter will force the server to only use the login
- names from the <i><tt>user</tt></i> list and is only really
- useful in <a href="#SECURITYEQUALSSHARE">share level</a>
- security.</p><p>Note that this also means Samba won't try to deduce
- usernames from the service name. This can be annoying for
- the [homes] section. To get around this you could use <b>user =
- %S</b> which means your <i><tt>user</tt></i> list
- will be just the service name, which for home directories is the
- name of the user.</p><p>See also the <a href="#USER"><i><tt>user</tt></i>
- </a> parameter.</p><p>Default: <b>only user = no</b></p></dd><dt><span class="term"><a name="OPLOCKBREAKWAITTIME"></a>oplock break wait time (G)</span></dt><dd><p>This is a tuning parameter added due to bugs in
- both Windows 9x and WinNT. If Samba responds to a client too
- quickly when that client issues an SMB that can cause an oplock
- break request, then the network client can fail and not respond
- to the break request. This tuning parameter (which is set in milliseconds)
- is the amount of time Samba will wait before sending an oplock break
- request to such (broken) clients.</p><p><span class="emphasis"><em>DO NOT CHANGE THIS PARAMETER UNLESS YOU HAVE READ AND
- UNDERSTOOD THE SAMBA OPLOCK CODE</em></span>.</p><p>Default: <b>oplock break wait time = 0</b></p></dd><dt><span class="term"><a name="OPLOCKCONTENTIONLIMIT"></a>oplock contention limit (S)</span></dt><dd><p>This is a <span class="emphasis"><em>very</em></span> advanced
- <a href="smbd.8.html">smbd(8)</a> tuning option to
- improve the efficiency of the granting of oplocks under multiple
- client contention for the same file.</p><p>In brief it specifies a number, which causes <a href="smbd.8.html">smbd(8)</a>not to grant an oplock even when requested
- if the approximate number of clients contending for an oplock on the same file goes over this
- limit. This causes <b>smbd</b> to behave in a similar
- way to Windows NT.</p><p><span class="emphasis"><em>DO NOT CHANGE THIS PARAMETER UNLESS YOU HAVE READ
- AND UNDERSTOOD THE SAMBA OPLOCK CODE</em></span>.</p><p>Default: <b>oplock contention limit = 2</b></p></dd><dt><span class="term"><a name="OPLOCKS"></a>oplocks (S)</span></dt><dd><p>This boolean option tells <b>smbd</b> 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 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>Speed.txt</tt> in the Samba <tt>docs/</tt>
- directory.</p><p>Oplocks may be selectively turned off on certain files with a
- share. See the <a href="#VETOOPLOCKFILES"><i><tt>
- veto oplock files</tt></i></a> parameter. On some systems
- oplocks are recognized by the underlying operating system. This
- allows data synchronization between all access to oplocked files,
- whether it be via Samba or NFS or a local UNIX process. See the
- <i><tt>kernel oplocks</tt></i> parameter for details.</p><p>See also the <a href="#KERNELOPLOCKS"><i><tt>kernel
- oplocks</tt></i></a> and <a href="#LEVEL2OPLOCKS"><i><tt>
- level2 oplocks</tt></i></a> parameters.</p><p>Default: <b>oplocks = yes</b></p></dd><dt><span class="term"><a name="OS2DRIVERMAP"></a>os2 driver map (G)</span></dt><dd><p>The parameter is used to define the absolute
- path to a file containing a mapping of Windows NT printer driver
- names to OS/2 printer driver names. The format is:</p><p>&lt;nt driver name&gt; = &lt;os2 driver name&gt;.&lt;device name&gt;</p><p>For example, a valid entry using the HP LaserJet 5
- printer driver would appear as <b>HP LaserJet 5L = LASERJET.HP
- LaserJet 5L</b>.</p><p>The need for the file is due to the printer driver namespace
- problem described in the <a href="printing.html" target="_top">Samba
- Printing HOWTO</a>. For more details on OS/2 clients, please
- refer to the OS2-Client-HOWTO containing in the Samba documentation.</p><p>Default: <b>os2 driver map = &lt;empty string&gt;</b></p></dd><dt><span class="term"><a name="OSLEVEL"></a>os level (G)</span></dt><dd><p>This integer value controls what level Samba
- advertises itself as for browse elections. The value of this
- parameter determines whether <a href="nmbd.8.html">nmbd(8)</a>
- has a chance of becoming a local master browser for the <i><tt>
- WORKGROUP</tt></i> in the local broadcast area.</p><p><span class="emphasis"><em>Note :</em></span>By default, Samba will win
- a local master browsing election over all Microsoft operating
- systems except a Windows NT 4.0/2000 Domain Controller. This
- means that a misconfigured Samba host can effectively isolate
- a subnet for browsing purposes. See <tt>BROWSING.txt
- </tt> in the Samba <tt>docs/</tt> directory
- for details.</p><p>Default: <b>os level = 20</b></p><p>Example: <b>os level = 65 </b></p></dd><dt><span class="term"><a name="PAMPASSWORDCHANGE"></a>pam password change (G)</span></dt><dd><p>With the addition of better PAM support in Samba 2.2,
- this parameter, it is possible to use PAM's password change control
- flag for Samba. If enabled, then PAM will be used for password
- changes when requested by an SMB client instead of the program listed in
- <a href="#PASSWDPROGRAM"><i><tt>passwd program</tt></i></a>.
- It should be possible to enable this without changing your
- <a href="#PASSWDCHAT"><i><tt>passwd chat</tt></i></a>
- parameter for most setups.</p><p>Default: <b>pam password change = no</b></p></dd><dt><span class="term"><a name="PANICACTION"></a>panic action (G)</span></dt><dd><p>This is a Samba developer option that allows a
- system command to be called when either <a href="smbd.8.html">smbd(8)</a> or <a href="smbd.8.html">smbd(8)</a> crashes. This is usually used to
- draw attention to the fact that a problem occurred.</p><p>Default: <b>panic action = &lt;empty string&gt;</b></p><p>Example: <b>panic action = &quot;/bin/sleep 90000&quot;</b></p></dd><dt><span class="term"><a name="PARANOIDSERVERSECURITY"></a>paranoid server security (G)</span></dt><dd><p>Some version of NT 4.x allow non-guest
- users with a bad passowrd. When this option is enabled, samba will not
- use a broken NT 4.x server as password server, but instead complain
- to the logs and exit.
- </p><p>Disabling this option prevents Samba from making
- this check, which involves deliberatly attempting a
- bad logon to the remote server.</p><p>Default: <b>paranoid server security = yes</b></p></dd><dt><span class="term"><a name="PASSDBBACKEND"></a>passdb backend (G)</span></dt><dd><p>This option allows the administrator to chose which backends
- to retrieve and store passwords with. This allows (for example) both
- smbpasswd and tdbsam to be used without a recompile. Multiple
- backends can be specified, separated by spaces. The backends will be
- searched in the order they are specified. New users are always added
- to the first backend specified. </p><p>This parameter is in two parts, the backend's name, and a 'location'
- string that has meaning only to that particular backed. These are separated
- by a : character.</p><p>Available backends can include:
- </p><div class="itemizedlist"><ul type="disc"><li><p><b>smbpasswd</b> - The default smbpasswd
- backend. Takes a path to the smbpasswd file as an optional argument.
- </p></li><li><p><b>smbpasswd_nua</b> - The smbpasswd
- backend, but with support for 'not unix accounts'.
- Takes a path to the smbpasswd file as an optional argument.</p><p>See also <a href="#NONUNIXACCOUNTRANGE">
- <i><tt>non unix account range</tt></i></a></p></li><li><p><b>tdbsam</b> - The TDB based password storage
- backend. Takes a path to the TDB as an optional argument (defaults to passdb.tdb
- in the <a href="#PRIVATEDIR">
- <i><tt>private dir</tt></i></a> directory.</p></li><li><p><b>tdbsam_nua</b> - The TDB based password storage
- backend, with non unix account support. Takes a path to the TDB as an optional argument (defaults to passdb.tdb
- in the <a href="#PRIVATEDIR">
- <i><tt>private dir</tt></i></a> directory.</p><p>See also <a href="#NONUNIXACCOUNTRANGE">
- <i><tt>non unix account range</tt></i></a></p></li><li><p><b>ldapsam</b> - The LDAP based passdb
- backend. Takes an LDAP URL as an optional argument (defaults to
- <b>ldap://localhost</b>)</p></li><li><p><b>ldapsam_nua</b> - The LDAP based passdb
- backend, with non unix account support. Takes an LDAP URL as an optional argument (defaults to
- <b>ldap://localhost</b>)</p><p>Note: In this module, any account without a matching POSIX account is regarded
- as 'non unix'. </p><p>See also <a href="#NONUNIXACCOUNTRANGE">
- <i><tt>non unix account range</tt></i></a></p><p>LDAP connections should be secured where possible. This may be done using either
- Start-TLS (see <a href="#LDAPSSL"><i><tt>ldap ssl</tt></i></a>) or by
- specifying <i><tt>ldaps://</tt></i> in
- the URL argument. </p></li><li><p><b>nisplussam</b> -
- The NIS+ based passdb backend. Takes name NIS domain as
- an optional argument. Only works with sun NIS+ servers.
- </p></li></ul></div><p>
- </p><p>Default: <b>passdb backend = smbpasswd unixsam</b></p><p>Example: <b>passdb backend = tdbsam:/etc/samba/private/passdb.tdb smbpasswd:/etc/samba/smbpasswd guest</b></p><p>Example: <b>passdb backend = ldapsam_nua:ldaps://ldap.example.com guest</b></p><p>Example: <b>passdb backend = mysql:my_plugin_args tdbsam:/etc/samba/private/passdb.tdb</b></p></dd><dt><span class="term"><a name="PASSWDCHATDEBUG"></a>passwd chat debug (G)</span></dt><dd><p>This boolean specifies if the passwd chat script
- parameter is run in <span class="emphasis"><em>debug</em></span> mode. In this mode the
- strings passed to and received from the passwd chat are printed
- in the <a href="smbd.8.html">smbd(8)</a> log with a
- <a href="#DEBUGLEVEL"><i><tt>debug level</tt></i></a>
- of 100. This is a dangerous option as it will allow plaintext passwords
- to be seen in the <b>smbd</b> log. It is available to help
- Samba admins debug their <i><tt>passwd chat</tt></i> scripts
- when calling the <i><tt>passwd program</tt></i> and should
- be turned off after this has been done. This option has no effect if the
- <a href="#PAMPASSWORDCHANGE"><i><tt>pam password change</tt></i></a>
- paramter is set. This parameter is off by default.</p><p>See also <a href="#PASSWDCHAT"><i><tt>passwd chat</tt></i>
- </a>, <a href="#PAMPASSWORDCHANGE"><i><tt>pam password change</tt></i>
- </a>, <a href="#PASSWDPROGRAM"><i><tt>passwd program</tt></i>
- </a>.</p><p>Default: <b>passwd chat debug = no</b></p></dd><dt><span class="term"><a name="PASSWDCHAT"></a>passwd chat (G)</span></dt><dd><p>This string controls the <span class="emphasis"><em>&quot;chat&quot;</em></span>
- conversation that takes places between <a href="smbd.8.html">smbd(8)</a> and the local password changing
- program to change the user's password. The string describes a
- sequence of response-receive pairs that <a href="smbd.8.html">smbd(8)</a> uses to determine what to send to the
- <a href="#PASSWDPROGRAM"><i><tt>passwd program</tt></i>
- </a> and what to expect back. If the expected output is not
- received then the password is not changed.</p><p>This chat sequence is often quite site specific, depending
- on what local methods are used for password control (such as NIS
- etc).</p><p>Note that this parameter only is only used if the <a href="#UNIXPASSWORDSYNC"> <i><tt>unix password sync</tt></i>
- </a> parameter is set to <tt>yes</tt>. This sequence is
- then called <span class="emphasis"><em>AS ROOT</em></span> when the SMB password in the
- smbpasswd file is being changed, without access to the old password
- cleartext. This means that root must be able to reset the user's password without
- knowing the text of the previous password. In the presence of
- NIS/YP, this means that the <a href="#PASSWDPROGRAM">passwd program</a> must
- be executed on the NIS master.
- </p><p>The string can contain the macro <i><tt>%n</tt></i> which is substituted
- for the new password. The chat sequence can also contain the standard
- macros <tt>\\n</tt>, <tt>\\r</tt>, <tt>\\t</tt> and <tt>\\s</tt> to
- give line-feed, carriage-return, tab and space. The chat sequence string can also contain
- a '*' which matches any sequence of characters. Double quotes can be used to collect strings with spaces
- in them into a single string.</p><p>If the send string in any part of the chat sequence is a full
- stop &quot;.&quot;, then no string is sent. Similarly, if the
- expect string is a full stop then no string is expected.</p><p>If the <a href="#PAMPASSWORDCHANGE"><i><tt>pam
- password change</tt></i></a> parameter is set to <tt>yes</tt>, the chat pairs
- may be matched in any order, and success is determined by the PAM result,
- not any particular output. The \n macro is ignored for PAM conversions.
- </p><p>See also <a href="#UNIXPASSWORDSYNC"><i><tt>unix password
- sync</tt></i></a>, <a href="#PASSWDPROGRAM"><i><tt>
- passwd program</tt></i></a> ,<a href="#PASSWDCHATDEBUG">
- <i><tt>passwd chat debug</tt></i></a> and <a href="#PAMPASSWORDCHANGE">
- <i><tt>pam password change</tt></i></a>.</p><p>Default: <b>passwd chat = *new*password* %n\\n
- *new*password* %n\\n *changed*</b></p><p>Example: <b>passwd chat = &quot;*Enter OLD password*&quot; %o\\n
- &quot;*Enter NEW password*&quot; %n\\n &quot;*Reenter NEW password*&quot; %n\\n
- &quot;*Password changed*&quot;</b></p></dd><dt><span class="term"><a name="PASSWDPROGRAM"></a>passwd program (G)</span></dt><dd><p>The name of a program that can be used to set
- UNIX user passwords. Any occurrences of <i><tt>%u</tt></i>
- will be replaced with the user name. The user name is checked for
- existence before calling the password changing program.</p><p>Also note that many passwd programs insist in <span class="emphasis"><em>reasonable
- </em></span> passwords, such as a minimum length, or the inclusion
- of mixed case chars and digits. This can pose a problem as some clients
- (such as Windows for Workgroups) uppercase the password before sending
- it.</p><p><span class="emphasis"><em>Note</em></span> that if the <i><tt>unix
- password sync</tt></i> parameter is set to <tt>yes
- </tt> then this program is called <span class="emphasis"><em>AS ROOT</em></span>
- before the SMB password in the <a href="smbpasswd.5.html" target="_top"><a href="smbpasswd.5.html">smbpasswd(5)</a>
- </a> file is changed. If this UNIX password change fails, then
- <b>smbd</b> will fail to change the SMB password also
- (this is by design).</p><p>If the <i><tt>unix password sync</tt></i> parameter
- is set this parameter <span class="emphasis"><em>MUST USE ABSOLUTE PATHS</em></span>
- for <span class="emphasis"><em>ALL</em></span> programs called, and must be examined
- for security implications. Note that by default <i><tt>unix
- password sync</tt></i> is set to <tt>no</tt>.</p><p>See also <a href="#UNIXPASSWORDSYNC"><i><tt>unix
- password sync</tt></i></a>.</p><p>Default: <b>passwd program = /bin/passwd</b></p><p>Example: <b>passwd program = /sbin/npasswd %u</b></p></dd><dt><span class="term"><a name="PASSWORDLEVEL"></a>password level (G)</span></dt><dd><p>Some client/server combinations have difficulty
- with mixed-case passwords. One offending client is Windows for
- Workgroups, which for some reason forces passwords to upper
- case when using the LANMAN1 protocol, but leaves them alone when
- using COREPLUS! Another problem child is the Windows 95/98
- family of operating systems. These clients upper case clear
- text passwords even when NT LM 0.12 selected by the protocol
- negotiation request/response.</p><p>This parameter defines the maximum number of characters
- that may be upper case in passwords.</p><p>For example, say the password given was &quot;FRED&quot;. If <i><tt>
- password level</tt></i> is set to 1, the following combinations
- would be tried if &quot;FRED&quot; failed:</p><p>&quot;Fred&quot;, &quot;fred&quot;, &quot;fRed&quot;, &quot;frEd&quot;,&quot;freD&quot;</p><p>If <i><tt>password level</tt></i> was set to 2,
- the following combinations would also be tried: </p><p>&quot;FRed&quot;, &quot;FrEd&quot;, &quot;FreD&quot;, &quot;fREd&quot;, &quot;fReD&quot;, &quot;frED&quot;, ..</p><p>And so on.</p><p>The higher value this parameter is set to the more likely
- it is that a mixed case password will be matched against a single
- case password. However, you should be aware that use of this
- parameter reduces security and increases the time taken to
- process a new connection.</p><p>A value of zero will cause only two attempts to be
- made - the password as is and the password in all-lower case.</p><p>Default: <b>password level = 0</b></p><p>Example: <b>password level = 4</b></p></dd><dt><span class="term"><a name="PASSWORDSERVER"></a>password server (G)</span></dt><dd><p>By specifying the name of another SMB server (such
- as a WinNT box) with this option, and using <b>security = domain
- </b> or <b>security = server</b> you can get Samba
- to do all its username/password validation via a remote server.</p><p>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
- name to the lmhosts file which is stored in the same directory
- as the <tt>smb.conf</tt> file.</p><p>The name of the password server is looked up using the
- parameter <a href="#NAMERESOLVEORDER"><i><tt>name
- resolve order</tt></i></a> and so may resolved
- by any method and order described in that parameter.</p><p>The password server must be a machine capable of using
- the &quot;LM1.2X002&quot; or the &quot;NT LM 0.12&quot; protocol, and it must be in
- user level security mode.</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>Using a password server means your UNIX box (running
- Samba) is only as secure as your password server. <span class="emphasis"><em>DO NOT
- CHOOSE A PASSWORD SERVER THAT YOU DON'T COMPLETELY TRUST</em></span>.
- </p></div><p>Never point a Samba server at itself for password serving.
- This will cause a loop and could lock up your Samba server!</p><p>The name of the password server takes the standard
- substitutions, but probably the only useful one is <i><tt>%m
- </tt></i>, which means the Samba server will use the incoming
- 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 <i><tt>security</tt></i> parameter is set to
- <tt>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 effectively
- in that domain, and will use cryptographically authenticated RPC calls
- to authenticate the user logging on. The advantage of using <b>
- security = domain</b> is that if you list several hosts in the
- <i><tt>password server</tt></i> option then <b>smbd
- </b> will try each in turn till it finds one that responds. This
- is useful in case your primary server goes down.</p><p>If the <i><tt>password server</tt></i> option is set
- to the character '*', then Samba will attempt to auto-locate the
- Primary or Backup Domain controllers to authenticate against by
- doing a query for the name <tt>WORKGROUP&lt;1C&gt;</tt>
- and then contacting each server returned in the list of IP
- addresses from the name resolution source. </p><p>If the list of servers contains both names and the '*'
- character, the list is treated as a list of preferred
- domain controllers, but an auto lookup of all remaining DC's
- will be added to the list as well. Samba will not attempt to optimize
- this list by locating the closest DC.</p><p>If the <i><tt>security</tt></i> parameter is
- set to <tt>server</tt>, then there are different
- restrictions that <b>security = domain</b> doesn't
- suffer from:</p><div class="itemizedlist"><ul type="disc"><li><p>You may list several password servers in
- the <i><tt>password server</tt></i> parameter, however if an
- <b>smbd</b> makes a connection to a password server,
- and then the password server fails, no more users will be able
- to be authenticated from this <b>smbd</b>. This is a
- restriction of the SMB/CIFS protocol when in <b>security = server
- </b> mode and cannot be fixed in Samba.</p></li><li><p>If you are using a Windows NT server as your
- password server then you will have to ensure that your users
- are able to login from the Samba server, as when in <b>
- security = server</b> mode the network logon will appear to
- come from there rather than from the users workstation.</p></li></ul></div><p>See also the <a href="#SECURITY"><i><tt>security
- </tt></i></a> parameter.</p><p>Default: <b>password server = &lt;empty string&gt;</b></p><p>Example: <b>password server = NT-PDC, NT-BDC1, NT-BDC2, *</b></p><p>Example: <b>password server = *</b></p></dd><dt><span class="term"><a name="PATH"></a>path (S)</span></dt><dd><p>This parameter specifies a directory to which
- the user of the service is to be given access. In the case of
- printable services, this is where print data will spool prior to
- being submitted to the host for printing.</p><p>For a printable service offering guest access, the service
- should be readonly and the path should be world-writeable and
- have the sticky bit set. This is not mandatory of course, but
- you probably won't get the results you expect if you do
- otherwise.</p><p>Any occurrences of <i><tt>%u</tt></i> in the path
- will be replaced with the UNIX username that the client is using
- on this connection. Any occurrences of <i><tt>%m</tt></i>
- will be replaced by the NetBIOS name of the machine they are
- connecting from. These replacements are very useful for setting
- up pseudo home directories for users.</p><p>Note that this path will be based on <a href="#ROOTDIR">
- <i><tt>root dir</tt></i></a> if one was specified.</p><p>Default: <span class="emphasis"><em>none</em></span></p><p>Example: <b>path = /home/fred</b></p></dd><dt><span class="term"><a name="PIDDIRECTORY"></a>pid directory (G)</span></dt><dd><p>This option specifies the directory where pid
- files will be placed. </p><p>Default: <b>pid directory = ${prefix}/var/locks</b></p><p>Example: <b>pid directory = /var/run/</b></p></dd><dt><span class="term"><a name="POSIXLOCKING"></a>posix locking (S)</span></dt><dd><p>The <a href="smbd.8.html">smbd(8)</a>
- daemon maintains an database of file locks obtained by SMB clients.
- The default behavior is to map this internal database to POSIX
- locks. This means that file locks obtained by SMB clients are
- consistent with those seen by POSIX compliant applications accessing
- the files via a non-SMB method (e.g. NFS or local file access).
- You should never need to disable this parameter.</p><p>Default: <b>posix locking = yes</b></p></dd><dt><span class="term"><a name="POSTEXEC"></a>postexec (S)</span></dt><dd><p>This option specifies a command to be run
- whenever the service is disconnected. It takes the usual
- substitutions. The command may be run as the root on some
- systems.</p><p>An interesting example may be to unmount server
- resources:</p><p><b>postexec = /etc/umount /cdrom</b></p><p>See also <a href="#PREEXEC"><i><tt>preexec</tt></i></a>.</p><p>Default: <span class="emphasis"><em>none (no command executed)</em></span></p><p>Example: <b>postexec = echo \&quot;%u disconnected from %S from %m (%I)\&quot; &gt;&gt; /tmp/log</b></p></dd><dt><span class="term"><a name="PREEXECCLOSE"></a>preexec close (S)</span></dt><dd><p>This boolean option controls whether a non-zero
- return code from <a href="#PREEXEC"><i><tt>preexec
- </tt></i></a> should close the service being connected to.</p><p>Default: <b>preexec close = no</b></p></dd><dt><span class="term"><a name="PREEXEC"></a>preexec (S)</span></dt><dd><p>This option specifies a command to be run whenever
- the service is connected to. It takes the usual substitutions.</p><p>An interesting example is to send the users a welcome
- message every time they log in. Maybe a message of the day? Here
- is an example:</p><p><b>preexec = csh -c 'echo \&quot;Welcome to %S!\&quot; | /usr/local/samba/bin/smbclient -M %m -I %I' &amp; </b></p><p>Of course, this could get annoying after a while :-)</p><p>See also <a href="#PREEXECCLOSE"><i><tt>preexec close</tt></i></a> and <a href="#POSTEXEC"><i><tt>postexec
- </tt></i></a>.</p><p>Default: <span class="emphasis"><em>none (no command executed)</em></span></p><p>Example: <b>preexec = echo \&quot;%u connected to %S from %m (%I)\&quot; &gt;&gt; /tmp/log</b></p></dd><dt><span class="term"><a name="PREFEREDMASTER"></a>prefered master (G)</span></dt><dd><p>Synonym for <a href="#PREFERREDMASTER"><i><tt>
- preferred master</tt></i></a> for people who cannot spell :-).</p></dd><dt><span class="term"><a name="PREFERREDMASTER"></a>preferred master (G)</span></dt><dd><p>This boolean parameter controls if
- <a href="nmbd.8.html">nmbd(8)</a> is a preferred master
- browser for its workgroup.</p><p>If this is set to <tt>yes</tt>, on startup, <b>nmbd</b>
- will force an election, and it will have a slight advantage in
- winning the election. It is recommended that this parameter is
- used in conjunction with <b><a href="#DOMAINMASTER">
- <i><tt>domain master</tt></i></a> = yes</b>, so
- that <b>nmbd</b> can guarantee becoming a domain master.</p><p>Use this option with caution, because if there are several
- hosts (whether Samba servers, Windows 95 or NT) that are
- preferred master browsers on the same subnet, they will each
- periodically and continuously attempt to become the local
- master browser. This will result in unnecessary broadcast
- traffic and reduced browsing capabilities.</p><p>See also <a href="#OSLEVEL"><i><tt>os level</tt></i></a>.</p><p>Default: <b>preferred master = auto</b></p></dd><dt><span class="term"><a name="PRELOADMODULES"></a>preload modules (G)</span></dt><dd><p>This is a list of paths to modules that should
- be loaded into smbd before a client connects. This improves
- the speed of smbd when reacting to new connections somewhat. </p><p>It is recommended to only use this option on heavy-performance
- servers.</p><p>Default: <b>preload modules = </b></p><p>Example: <b>preload modules = /usr/lib/samba/passdb/mysql.so+++ </b></p></dd><dt><span class="term"><a name="PRELOAD"></a>preload (G)</span></dt><dd><p>This is a list of services that you want to be
- automatically added to the browse lists. This is most useful
- for homes and printers services that would otherwise not be
- visible.</p><p>Note that if you just want all printers in your
- printcap file loaded then the <a href="#LOADPRINTERS">
- <i><tt>load printers</tt></i></a> option is easier.</p><p>Default: <span class="emphasis"><em>no preloaded services</em></span></p><p>Example: <b>preload = fred lp colorlp</b></p></dd><dt><span class="term"><a name="PRESERVECASE"></a>preserve case (S)</span></dt><dd><p> This controls if new filenames are created
- with the case that the client passes, or if they are forced to
- be the <a href="#DEFAULTCASE"><i><tt>default case
- </tt></i></a>.</p><p>Default: <b>preserve case = yes</b></p><p>See the section on <a href="#NAMEMANGLINGSECT" title="NAME MANGLING">NAME MANGLING</a> for a fuller discussion.</p></dd><dt><span class="term"><a name="PRINTABLE"></a>printable (S)</span></dt><dd><p>If this parameter is <tt>yes</tt>, then
- clients may open, write to and submit spool files on the directory
- specified for the service. </p><p>Note that a printable service will ALWAYS allow writing
- to the service path (user privileges permitting) via the spooling
- of print data. The <a href="#READONLY"><i><tt>read only
- </tt></i></a> parameter controls only non-printing access to
- the resource.</p><p>Default: <b>printable = no</b></p></dd><dt><span class="term"><a name="PRINTCAPNAME"></a>printcap name (S)</span></dt><dd><p>This parameter may be used to override the
- compiled-in default printcap name used by the server (usually <tt>
- /etc/printcap</tt>). See the discussion of the <a href="#PRINTERSSECT" title="The [printers] section">[printers]</a> section above for reasons
- why you might want to do this.</p><p>To use the CUPS printing interface set <b>printcap name = cups
- </b>. This should be supplemented by an addtional setting
- <a href="#PRINTING">printing = cups</a> in the [global]
- section. <b>printcap name = cups</b> will use the
- &quot;dummy&quot; printcap created by CUPS, as specified in your CUPS
- configuration file.
- </p><p>On System V systems that use <b>lpstat</b> to
- list available printers you can use <b>printcap name = lpstat
- </b> to automatically obtain lists of available printers. This
- is the default for systems that define SYSV at configure time in
- Samba (this includes most System V based systems). If <i><tt>
- printcap name</tt></i> is set to <b>lpstat</b> on
- these systems then Samba will launch <b>lpstat -v</b> and
- attempt to parse the output to obtain a printer list.</p><p>A minimal printcap file would look something like this:</p><pre class="programlisting">
-print1|My Printer 1
-print2|My Printer 2
-print3|My Printer 3
-print4|My Printer 4
-print5|My Printer 5
-</pre><p>where the '|' separates aliases of a printer. The fact
- that the second alias has a space in it gives a hint to Samba
- that it's a comment.</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>Under AIX the default printcap
- name is <tt>/etc/qconfig</tt>. Samba will assume the
- file is in AIX <tt>qconfig</tt> format if the string
- <tt>qconfig</tt> appears in the printcap filename.</p></div><p>Default: <b>printcap name = /etc/printcap</b></p><p>Example: <b>printcap name = /etc/myprintcap</b></p></dd><dt><span class="term"><a name="PRINTCAP"></a>printcap (G)</span></dt><dd><p>Synonym for <a href="#PRINTCAPNAME"><i><tt>
- printcap name</tt></i></a>.</p></dd><dt><span class="term"><a name="PRINTCOMMAND"></a>print command (S)</span></dt><dd><p>After a print job has finished spooling to
- a service, this command will be used via a <b>system()</b>
- call to process the spool file. Typically the command specified will
- submit the spool file to the host's printing subsystem, but there
- is no requirement that this be the case. The server will not remove
- the spool file, so whatever command you specify should remove the
- spool file when it has been processed, otherwise you will need to
- manually remove old spool files.</p><p>The print command is simply a text string. It will be used
- verbatim after macro substitutions have been made:</p><p>%s, %p - the path to the spool
- file name</p><p>%p - the appropriate printer
- name</p><p>%J - the job
- name as transmitted by the client.</p><p>%c - The number of printed pages
- of the spooled job (if known).</p><p>%z - the size of the spooled
- print job (in bytes)</p><p>The print command <span class="emphasis"><em>MUST</em></span> contain at least
- one occurrence of <i><tt>%s</tt></i> or <i><tt>%f
- </tt></i> - the <i><tt>%p</tt></i> is optional. At the time
- a job is submitted, if no printer name is supplied the <i><tt>%p
- </tt></i> will be silently removed from the printer command.</p><p>If specified in the [global] section, the print command given
- will be used for any printable service that does not have its own
- print command specified.</p><p>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.</p><p>Note that printing may fail on some UNIXes from the
- <tt>nobody</tt> account. If this happens then create
- an alternative guest account that can print and set the <a href="#GUESTACCOUNT">
- <i><tt>guest account</tt></i></a>
- in the [global] section.</p><p>You can form quite complex print commands by realizing
- that they are just passed to a shell. For example the following
- will log a print job, print the file, then remove it. Note that
- ';' is the usual separator for command in shell scripts.</p><p><b>print command = echo Printing %s &gt;&gt;
- /tmp/print.log; lpr -P %p %s; rm %s</b></p><p>You may have to vary this command considerably depending
- on how you normally print files on your system. The default for
- the parameter varies depending on the setting of the <a href="#PRINTING">
- <i><tt>printing</tt></i></a> parameter.</p><p>Default: For <b>printing = BSD, AIX, QNX, LPRNG
- or PLP :</b></p><p><b>print command = lpr -r -P%p %s</b></p><p>For <b>printing = SYSV or HPUX :</b></p><p><b>print command = lp -c -d%p %s; rm %s</b></p><p>For <b>printing = SOFTQ :</b></p><p><b>print command = lp -d%p -s %s; rm %s</b></p><p>For printing = CUPS : If SAMBA is compiled against
- libcups, then <a href="#PRINTING">printcap = cups</a>
- uses the CUPS API to
- submit jobs, etc. Otherwise it maps to the System V
- commands with the -oraw option for printing, i.e. it
- uses <b>lp -c -d%p -oraw; rm %s</b>.
- With <b>printing = cups</b>,
- and if SAMBA is compiled against libcups, any manually
- set print command will be ignored.</p><p>Example: <b>print command = /usr/local/samba/bin/myprintscript %p %s</b></p></dd><dt><span class="term"><a name="PRINTERADMIN"></a>printer admin (S)</span></dt><dd><p>This is a list of users that can do anything to
- printers via the remote administration interfaces offered by MS-RPC
- (usually using a NT workstation). Note that the root user always
- has admin rights.</p><p>Default: <b>printer admin = &lt;empty string&gt;</b></p><p>Example: <b>printer admin = admin, @staff</b></p></dd><dt><span class="term"><a name="PRINTERNAME"></a>printer name (S)</span></dt><dd><p>This parameter specifies the name of the printer
- to which print jobs spooled through a printable service will be sent.</p><p>If specified in the [global] section, the printer
- name given will be used for any printable service that does
- not have its own printer name specified.</p><p>Default: <span class="emphasis"><em>none (but may be <tt>lp</tt>
- on many systems)</em></span></p><p>Example: <b>printer name = laserwriter</b></p></dd><dt><span class="term"><a name="PRINTER"></a>printer (S)</span></dt><dd><p>Synonym for <a href="#PRINTERNAME"><i><tt>
- printer name</tt></i></a>.</p></dd><dt><span class="term"><a name="PRINTING"></a>printing (S)</span></dt><dd><p>This parameters controls how printer status information is
- interpreted on your system. It also affects the default values for
- the <i><tt>print command</tt></i>, <i><tt>lpq command</tt></i>, <i><tt>lppause command </tt></i>, <i><tt>lpresume command</tt></i>, and <i><tt>lprm command</tt></i> if specified in the
- [global] section.</p><p>Currently nine printing styles are supported. They are
- <tt>BSD</tt>, <tt>AIX</tt>,
- <tt>LPRNG</tt>, <tt>PLP</tt>,
- <tt>SYSV</tt>, <tt>HPUX</tt>,
- <tt>QNX</tt>, <tt>SOFTQ</tt>,
- and <tt>CUPS</tt>.</p><p>To see what the defaults are for the other print
- commands when using the various options use the <a href="testparm.1.html">testparm(1)</a> program.</p><p>This option can be set on a per printer basis</p><p>See also the discussion in the <a href="#PRINTERSSECT" title="The [printers] section">
- [printers]</a> section.</p></dd><dt><span class="term"><a name="PRINTOK"></a>print ok (S)</span></dt><dd><p>Synonym for <a href="#PRINTABLE">
- <i><tt>printable</tt></i></a>.</p></dd><dt><span class="term"><a name="PRIVATEDIR"></a>private dir (G)</span></dt><dd><p>This parameters defines the directory
- smbd will use for storing such files as <tt>smbpasswd</tt>
- and <tt>secrets.tdb</tt>.
- </p><p>Default :<b>private dir = ${prefix}/private</b></p></dd><dt><span class="term"><a name="PROTOCOL"></a>protocol (G)</span></dt><dd><p>Synonym for <a href="#MAXPROTOCOL">
- <i><tt>max protocol</tt></i></a>.</p></dd><dt><span class="term"><a name="PUBLIC"></a>public (S)</span></dt><dd><p>Synonym for <a href="#GUESTOK"><i><tt>guest
- ok</tt></i></a>.</p></dd><dt><span class="term"><a name="QUEUEPAUSECOMMAND"></a>queuepause command (S)</span></dt><dd><p>This parameter specifies the command to be
- executed on the server host in order to pause the printer queue.</p><p>This command should be a program or script which takes
- a printer name as its only parameter and stops the printer queue,
- such that no longer jobs are submitted to the printer.</p><p>This command is not supported by Windows for Workgroups,
- but can be issued from the Printers window under Windows 95
- and NT.</p><p>If a <i><tt>%p</tt></i> is given then the printer name
- is put in its place. Otherwise it is placed at the end of the command.
- </p><p>Note that it is good practice to include the absolute
- path in the command as the PATH may not be available to the
- server.</p><p>Default: <span class="emphasis"><em>depends on the setting of <i><tt>printing</tt></i></em></span></p><p>Example: <b>queuepause command = disable %p</b></p></dd><dt><span class="term"><a name="QUEUERESUMECOMMAND"></a>queueresume command (S)</span></dt><dd><p>This parameter specifies the command to be
- executed on the server host in order to resume the printer queue. It
- is the command to undo the behavior that is caused by the
- previous parameter (<a href="#QUEUEPAUSECOMMAND"><i><tt>
- queuepause command</tt></i></a>).</p><p>This command should be a program or script which takes
- a printer name as its only parameter and resumes the printer queue,
- such that queued jobs are resubmitted to the printer.</p><p>This command is not supported by Windows for Workgroups,
- but can be issued from the Printers window under Windows 95
- and NT.</p><p>If a <i><tt>%p</tt></i> is given then the printer name
- is put in its place. Otherwise it is placed at the end of the
- command.</p><p>Note that it is good practice to include the absolute
- path in the command as the PATH may not be available to the
- server.</p><p>Default: <span class="emphasis"><em>depends on the setting of <a href="#PRINTING">
- <i><tt>printing</tt></i></a></em></span></p><p>Example: <b>queuepause command = enable %p</b></p></dd><dt><span class="term"><a name="READBMPX"></a>read bmpx (G)</span></dt><dd><p>This boolean parameter controls whether
- <a href="smbd.8.html">smbd(8)</a> will support the &quot;Read
- Block Multiplex&quot; SMB. This is now rarely used and defaults to
- <tt>no</tt>. You should never need to set this
- parameter.</p><p>Default: <b>read bmpx = no</b></p></dd><dt><span class="term"><a name="READLIST"></a>read list (S)</span></dt><dd><p>This is a list of users that are given read-only
- access to a service. If the connecting user is in this list then
- they will not be given write access, no matter what the <a href="#READONLY">
- <i><tt>read only</tt></i></a>
- option is set to. The list can include group names using the
- syntax described in the <a href="#INVALIDUSERS"><i><tt>
- invalid users</tt></i></a> parameter.</p><p>See also the <a href="#WRITELIST"><i><tt>
- write list</tt></i></a> parameter and the <a href="#INVALIDUSERS">
- <i><tt>invalid users</tt></i>
- </a> parameter.</p><p>Default: <b>read list = &lt;empty string&gt;</b></p><p>Example: <b>read list = mary, @students</b></p></dd><dt><span class="term"><a name="READONLY"></a>read only (S)</span></dt><dd><p>An inverted synonym is <a href="#WRITEABLE">
- <i><tt>writeable</tt></i></a>.</p><p>If this parameter is <tt>yes</tt>, then users
- of a service may not create or modify files in the service's
- directory.</p><p>Note that a printable service (<b>printable = yes</b>)
- will <span class="emphasis"><em>ALWAYS</em></span> allow writing to the directory
- (user privileges permitting), but only via spooling operations.</p><p>Default: <b>read only = yes</b></p></dd><dt><span class="term"><a name="READRAW"></a>read raw (G)</span></dt><dd><p>This parameter controls whether or not the server
- will support the raw read SMB requests when transferring data
- to clients.</p><p>If enabled, raw reads allow reads of 65535 bytes in
- one packet. This typically provides a major performance benefit.
- </p><p>However, some clients either negotiate the allowable
- block size incorrectly or are incapable of supporting larger block
- sizes, and for these clients you may need to disable raw reads.</p><p>In general this parameter should be viewed as a system tuning
- tool and left severely alone. See also <a href="#WRITERAW">
- <i><tt>write raw</tt></i></a>.</p><p>Default: <b>read raw = yes</b></p></dd><dt><span class="term"><a name="READSIZE"></a>read size (G)</span></dt><dd><p>The option <i><tt>read size</tt></i>
- affects the overlap of disk reads/writes with network reads/writes.
- If the amount of data being transferred in several of the SMB
- commands (currently SMBwrite, SMBwriteX and SMBreadbraw) is larger
- than this value then the server begins writing the data before it
- has received the whole packet from the network, or in the case of
- SMBreadbraw, it begins writing to the network before all the data
- has been read from disk.</p><p>This overlapping works best when the speeds of disk and
- network access are similar, having very little effect when the
- speed of one is much greater than the other.</p><p>The default value is 16384, but very little experimentation
- has been done yet to determine the optimal value, and it is likely
- that the best value will vary greatly between systems anyway.
- A value over 65536 is pointless and will cause you to allocate
- memory unnecessarily.</p><p>Default: <b>read size = 16384</b></p><p>Example: <b>read size = 8192</b></p></dd><dt><span class="term"><a name="REALM"></a>realm (G)</span></dt><dd><p>This option specifies the kerberos realm to use. The realm is
- used as the ADS equivalent of the NT4 <b>domain</b>. It
- is usually set to the DNS name of the kerberos server.
- </p><p>Default: <b>realm = </b></p><p>Example: <b>realm = mysambabox.mycompany.com</b></p></dd><dt><span class="term"><a name="REMOTEANNOUNCE"></a>remote announce (G)</span></dt><dd><p>This option allows you to setup <a href="nmbd.8.html">nmbd(8)</a>to periodically announce itself
- to arbitrary IP addresses with an arbitrary workgroup name.</p><p>This is useful if you want your Samba server to appear
- in a remote workgroup for which the normal browse propagation
- rules don't work. The remote workgroup can be anywhere that you
- can send IP packets to.</p><p>For example:</p><p><b>remote announce = 192.168.2.255/SERVERS
- 192.168.4.255/STAFF</b></p><p>the above line would cause <b>nmbd</b> to announce itself
- to the two given IP addresses using the given workgroup names.
- If you leave out the workgroup name then the one given in
- the <a href="#WORKGROUP"><i><tt>workgroup</tt></i></a>
- parameter is used instead.</p><p>The IP addresses you choose would normally be the broadcast
- addresses of the remote networks, but can also be the IP addresses
- of known browse masters if your network config is that stable.</p><p>See the documentation file <a href="improved-browsing.html" target="_top">BROWSING</a>
- in the <tt>docs/</tt> directory.</p><p>Default: <b>remote announce = &lt;empty string&gt;</b></p></dd><dt><span class="term"><a name="REMOTEBROWSESYNC"></a>remote browse sync (G)</span></dt><dd><p>This option allows you to setup <a href="nmbd.8.html">nmbd(8)</a> to periodically request
- synchronization of browse lists with the master browser of a Samba
- server that is on a remote segment. This option will allow you to
- gain browse lists for multiple workgroups across routed networks. This
- is done in a manner that does not work with any non-Samba servers.</p><p>This is useful if you want your Samba server and all local
- clients to appear in a remote workgroup for which the normal browse
- propagation rules don't work. The remote workgroup can be anywhere
- that you can send IP packets to.</p><p>For example:</p><p><b>remote browse sync = 192.168.2.255 192.168.4.255</b></p><p>the above line would cause <b>nmbd</b> to request
- the master browser on the specified subnets or addresses to
- synchronize their browse lists with the local server.</p><p>The IP addresses you choose would normally be the broadcast
- addresses of the remote networks, but can also be the IP addresses
- of known browse masters if your network config is that stable. If
- a machine IP address is given Samba makes NO attempt to validate
- that the remote machine is available, is listening, nor that it
- is in fact the browse master on its segment.</p><p>Default: <b>remote browse sync = &lt;empty string&gt;</b></p></dd><dt><span class="term"><a name="RESTRICTANONYMOUS"></a>restrict anonymous (G)</span></dt><dd><p>This is a integer parameter, and mirrors as much as possible the functinality the
- <tt>RestrictAnonymous</tt> registry key does on NT/Win2k.
- </p><p>Default: <b>restrict anonymous = 0</b></p></dd><dt><span class="term"><a name="ROOTDIRECTORY"></a>root directory (G)</span></dt><dd><p>The server will <b>chroot()</b> (i.e.
- Change its root directory) to this directory on startup. This is
- not strictly necessary for secure operation. Even without it the
- server will deny access to files not in one of the service entries.
- It may also check for, and deny access to, soft links to other
- parts of the filesystem, or attempts to use &quot;..&quot; in file names
- to access other directories (depending on the setting of the <a href="#WIDELINKS">
- <i><tt>wide links</tt></i></a>
- parameter).
- </p><p>Adding a <i><tt>root directory</tt></i> entry other
- than &quot;/&quot; adds an extra level of security, but at a price. It
- absolutely ensures that no access is given to files not in the
- sub-tree specified in the <i><tt>root directory</tt></i>
- option, <span class="emphasis"><em>including</em></span> some files needed for
- complete operation of the server. To maintain full operability
- of the server you will need to mirror some system files
- into the <i><tt>root directory</tt></i> tree. In particular
- you will need to mirror <tt>/etc/passwd</tt> (or a
- subset of it), and any binaries or configuration files needed for
- printing (if required). The set of files that must be mirrored is
- operating system dependent.</p><p>Default: <b>root directory = /</b></p><p>Example: <b>root directory = /homes/smb</b></p></dd><dt><span class="term"><a name="ROOTDIR"></a>root dir (G)</span></dt><dd><p>Synonym for <a href="#ROOTDIRECTORY">
- <i><tt>root directory&quot;</tt></i></a>.
- </p></dd><dt><span class="term"><a name="ROOTPOSTEXEC"></a>root postexec (S)</span></dt><dd><p>This is the same as the <i><tt>postexec</tt></i>
- parameter except that the command is run as root. This
- is useful for unmounting filesystems
- (such as CDROMs) after a connection is closed.</p><p>See also <a href="#POSTEXEC"><i><tt>
- postexec</tt></i></a>.</p><p>Default: <b>root postexec = &lt;empty string&gt;</b></p></dd><dt><span class="term"><a name="ROOTPREEXECCLOSE"></a>root preexec close (S)</span></dt><dd><p>This is the same as the <i><tt>preexec close
- </tt></i> parameter except that the command is run as root.</p><p>See also <a href="#PREEXEC"><i><tt>
- preexec</tt></i></a> and <a href="#PREEXECCLOSE">
- <i><tt>preexec close</tt></i></a>.</p><p>Default: <b>root preexec close = no</b></p></dd><dt><span class="term"><a name="ROOTPREEXEC"></a>root preexec (S)</span></dt><dd><p>This is the same as the <i><tt>preexec</tt></i>
- parameter except that the command is run as root. This
- is useful for mounting filesystems (such as CDROMs) when a
- connection is opened.</p><p>See also <a href="#PREEXEC"><i><tt>
- preexec</tt></i></a> and <a href="#PREEXECCLOSE">
- <i><tt>preexec close</tt></i></a>.</p><p>Default: <b>root preexec = &lt;empty string&gt;</b></p></dd><dt><span class="term"><a name="ROOT"></a>root (G)</span></dt><dd><p>Synonym for <a href="#ROOTDIRECTORY">
- <i><tt>root directory&quot;</tt></i></a>.
- </p></dd><dt><span class="term"><a name="SECURITYMASK"></a>security mask (S)</span></dt><dd><p>This parameter controls what UNIX permission
- bits can be modified when a Windows NT client is manipulating
- the UNIX permission on a file using the native NT security
- dialog box.</p><p>This parameter is applied as a mask (AND'ed with) to
- the changed permission bits, thus preventing any bits not in
- this mask from being modified. Essentially, zero bits in this
- mask may be treated as a set of bits the user is not allowed
- to change.</p><p>If not set explicitly this parameter is 0777, allowing
- a user to modify all the user/group/world permissions on a file.
- </p><p><span class="emphasis"><em>Note</em></span> that users who can access the
- Samba server through other means can easily bypass this
- restriction, so it is primarily useful for standalone
- &quot;appliance&quot; systems. Administrators of most normal systems will
- probably want to leave it set to <tt>0777</tt>.</p><p>See also the <a href="#FORCEDIRECTORYSECURITYMODE">
- <i><tt>force directory security mode</tt></i></a>,
- <a href="#DIRECTORYSECURITYMASK"><i><tt>directory
- security mask</tt></i></a>, <a href="#FORCESECURITYMODE">
- <i><tt>force security mode</tt></i></a> parameters.</p><p>Default: <b>security mask = 0777</b></p><p>Example: <b>security mask = 0770</b></p></dd><dt><span class="term"><a name="SECURITY"></a>security (G)</span></dt><dd><p>This option affects how clients respond to
- Samba and is one of the most important settings in the <tt>
- smb.conf</tt> file.</p><p>The option sets the &quot;security mode bit&quot; in replies to
- protocol negotiations with <a href="smbd.8.html">smbd(8)</a> to turn share level security on or off. Clients decide
- based on this bit whether (and how) to transfer user and password
- information to the server.</p><p>The default is <b>security = user</b>, as this is
- the most common setting needed when talking to Windows 98 and
- Windows NT.</p><p>The alternatives are <b>security = share</b>,
- <b>security = server</b> or <b>security = domain
- </b>.</p><p>In versions of Samba prior to 2.0.0, the default was
- <b>security = share</b> mainly because that was
- the only option at one stage.</p><p>There is a bug in WfWg that has relevance to this
- setting. When in user or server level security a WfWg client
- will totally ignore the password you type in the &quot;connect
- drive&quot; dialog box. This makes it very difficult (if not impossible)
- to connect to a Samba service as anyone except the user that
- you are logged into WfWg as.</p><p>If your PCs use usernames that are the same as their
- usernames on the UNIX machine then you will want to use
- <b>security = user</b>. If you mostly use usernames
- that don't exist on the UNIX box then use <b>security =
- share</b>.</p><p>You should also use <b>security = share</b> if you
- want to mainly setup shares without a password (guest shares). This
- is commonly used for a shared printer server. It is more difficult
- to setup guest shares with <b>security = user</b>, see
- the <a href="#MAPTOGUEST"><i><tt>map to guest</tt></i>
- </a>parameter for details.</p><p>It is possible to use <b>smbd</b> in a <span class="emphasis"><em>
- hybrid mode</em></span> where it is offers both user and share
- level security under different <a href="#NETBIOSALIASES">
- <i><tt>NetBIOS aliases</tt></i></a>. </p><p>The different settings will now be explained.</p><p><a name="SECURITYEQUALSSHARE"></a><span class="emphasis"><em>SECURITY = SHARE</em></span></p><p>When clients connect to a share level security server they
- need not log onto the server with a valid username and password before
- attempting to connect to a shared resource (although modern clients
- such as Windows 95/98 and Windows NT will send a logon request with
- a username but no password when talking to a <b>security = share
- </b> server). Instead, the clients send authentication information
- (passwords) on a per-share basis, at the time they attempt to connect
- to that share.</p><p>Note that <b>smbd</b> <span class="emphasis"><em>ALWAYS</em></span>
- uses a valid UNIX user to act on behalf of the client, even in
- <b>security = share</b> level security.</p><p>As clients are not required to send a username to the server
- in share level security, <b>smbd</b> uses several
- techniques to determine the correct UNIX user to use on behalf
- of the client.</p><p>A list of possible UNIX usernames to match with the given
- client password is constructed using the following methods :</p><div class="itemizedlist"><ul type="disc"><li><p>If the <a href="#GUESTONLY"><i><tt>guest
- only</tt></i></a> parameter is set, then all the other
- stages are missed and only the <a href="#GUESTACCOUNT">
- <i><tt>guest account</tt></i></a> username is checked.
- </p></li><li><p>Is a username is sent with the share connection
- request, then this username (after mapping - see <a href="#USERNAMEMAP">
- <i><tt>username map</tt></i></a>),
- is added as a potential username.
- </p></li><li><p>If the client did a previous <span class="emphasis"><em>logon
- </em></span> request (the SessionSetup SMB call) then the
- username sent in this SMB will be added as a potential username.
- </p></li><li><p>The name of the service the client requested is
- added as a potential username.
- </p></li><li><p>The NetBIOS name of the client is added to
- the list as a potential username.
- </p></li><li><p>Any users on the <a href="#USER"><i><tt>
- user</tt></i></a> list are added as potential usernames.
- </p></li></ul></div><p>If the <i><tt>guest only</tt></i> parameter is
- not set, then this list is then tried with the supplied password.
- The first user for whom the password matches will be used as the
- UNIX user.</p><p>If the <i><tt>guest only</tt></i> parameter is
- set, or no username can be determined then if the share is marked
- as available to the <i><tt>guest account</tt></i>, then this
- guest user will be used, otherwise access is denied.</p><p>Note that it can be <span class="emphasis"><em>very</em></span> confusing
- in share-level security as to which UNIX username will eventually
- be used in granting access.</p><p>See also the section <a href="#VALIDATIONSECT" title="NOTE ABOUT USERNAME/PASSWORD VALIDATION">
- NOTE ABOUT USERNAME/PASSWORD VALIDATION</a>.</p><p><a name="SECURITYEQUALSUSER"></a><span class="emphasis"><em>SECURITY = USER</em></span></p><p>This is the default security setting in Samba 3.0.
- With user-level security a client must first &quot;log-on&quot; with a
- valid username and password (which can be mapped using the <a href="#USERNAMEMAP">
- <i><tt>username map</tt></i></a>
- parameter). Encrypted passwords (see the <a href="#ENCRYPTPASSWORDS">
- <i><tt>encrypted passwords</tt></i></a> parameter) can also
- be used in this security mode. Parameters such as <a href="#USER">
- <i><tt>user</tt></i></a> and <a href="#GUESTONLY">
- <i><tt>guest only</tt></i></a> if set are then applied and
- may change the UNIX user to use on this connection, but only after
- the user has been successfully authenticated.</p><p><span class="emphasis"><em>Note</em></span> that the name of the resource being
- requested is <span class="emphasis"><em>not</em></span> sent to the server until after
- the server has successfully authenticated the client. This is why
- guest shares don't work in user level security without allowing
- the server to automatically map unknown users into the <a href="#GUESTACCOUNT">
- <i><tt>guest account</tt></i></a>.
- See the <a href="#MAPTOGUEST"><i><tt>map to guest</tt></i>
- </a> parameter for details on doing this.</p><p>See also the section <a href="#VALIDATIONSECT" title="NOTE ABOUT USERNAME/PASSWORD VALIDATION">
- NOTE ABOUT USERNAME/PASSWORD VALIDATION</a>.</p><p><a name="SECURITYEQUALSDOMAIN"></a><span class="emphasis"><em>SECURITY = DOMAIN</em></span></p><p>This mode will only work correctly if <a href="net.8.html">net(8)</a> has been used to add this
- machine into a Windows NT Domain. It expects the <a href="#ENCRYPTPASSWORDS">
- <i><tt>encrypted passwords</tt></i>
- </a> parameter to be set to <tt>yes</tt>. In this
- mode Samba will try to validate the username/password by passing
- it to a Windows NT Primary or Backup Domain Controller, in exactly
- the same way that a Windows NT Server would do.</p><p><span class="emphasis"><em>Note</em></span> that a valid UNIX user must still
- exist as well as the account on the Domain Controller to allow
- Samba to have a valid UNIX account to map file access to.</p><p><span class="emphasis"><em>Note</em></span> that from the client's point
- of view <b>security = domain</b> is the same
- as <b>security = user</b>. It only
- affects how the server deals with the authentication,
- it does not in any way affect what the client sees.</p><p><span class="emphasis"><em>Note</em></span> that the name of the resource being
- requested is <span class="emphasis"><em>not</em></span> sent to the server until after
- the server has successfully authenticated the client. This is why
- guest shares don't work in user level security without allowing
- the server to automatically map unknown users into the <a href="#GUESTACCOUNT">
- <i><tt>guest account</tt></i></a>.
- See the <a href="#MAPTOGUEST"><i><tt>map to guest</tt></i>
- </a> parameter for details on doing this.</p><p>See also the section <a href="#VALIDATIONSECT" title="NOTE ABOUT USERNAME/PASSWORD VALIDATION">
- NOTE ABOUT USERNAME/PASSWORD VALIDATION</a>.</p><p>See also the <a href="#PASSWORDSERVER"><i><tt>password
- server</tt></i></a> parameter and the <a href="#ENCRYPTPASSWORDS">
- <i><tt>encrypted passwords</tt></i>
- </a> parameter.</p><p><a name="SECURITYEQUALSSERVER"></a><span class="emphasis"><em>SECURITY = SERVER</em></span></p><p>In this mode Samba will try to validate the username/password
- by passing it to another SMB server, such as an NT box. If this
- fails it will revert to <b>security =
- user</b>. It expects the <a href="#ENCRYPTPASSWORDS">
- <i><tt>encrypted passwords</tt></i></a> parameter
- to be set to <tt>yes</tt>, unless the remote server
- does not support them. However note that if encrypted passwords have been
- negotiated then Samba cannot revert back to checking the UNIX password file,
- it must have a valid <tt>smbpasswd</tt> file to check
- users against. See the documentation file in the <tt>docs/</tt> directory
- <tt>ENCRYPTION.txt</tt> for details on how to set this up.</p><p><span class="emphasis"><em>Note</em></span> this mode of operation has
- significant pitfalls, due to the fact that is activly initiates a
- man-in-the-middle attack on the remote SMB server. In particular,
- this mode of operation can cause significant resource consuption on
- the PDC, as it must maintain an active connection for the duration
- of the user's session. Furthermore, if this connection is lost,
- there is no way to reestablish it, and futher authenticaions to the
- Samba server may fail. (From a single client, till it disconnects).
- </p><p><span class="emphasis"><em>Note</em></span> that from the client's point of
- view <b>security = server</b> is the
- same as <b>security = user</b>. It
- only affects how the server deals with the authentication, it does
- not in any way affect what the client sees.</p><p><span class="emphasis"><em>Note</em></span> that the name of the resource being
- requested is <span class="emphasis"><em>not</em></span> sent to the server until after
- the server has successfully authenticated the client. This is why
- guest shares don't work in user level security without allowing
- the server to automatically map unknown users into the <a href="#GUESTACCOUNT">
- <i><tt>guest account</tt></i></a>.
- See the <a href="#MAPTOGUEST"><i><tt>map to guest</tt></i>
- </a> parameter for details on doing this.</p><p>See also the section <a href="#VALIDATIONSECT" title="NOTE ABOUT USERNAME/PASSWORD VALIDATION">
- NOTE ABOUT USERNAME/PASSWORD VALIDATION</a>.</p><p>See also the <a href="#PASSWORDSERVER"><i><tt>password
- server</tt></i></a> parameter and the <a href="#ENCRYPTPASSWORDS">
- <i><tt>encrypted passwords</tt></i></a> parameter.</p><p>Default: <b>security = USER</b></p><p>Example: <b>security = DOMAIN</b></p></dd><dt><span class="term"><a name="SERVERSCHANNEL"></a>server schannel (G)</span></dt><dd><p>This controls whether the server offers or even
- demands the use of the netlogon schannel.
- <i><tt>server schannel = no</tt></i> does not
- offer the schannel, <i><tt>server schannel =
- auto</tt></i> offers the schannel but does not
- enforce it, and <i><tt>server schannel =
- yes</tt></i> denies access if the client is not
- able to speak netlogon schannel. This is only the case
- for Windows NT4 before SP4.</p><p>Please note that with this set to
- <i><tt>no</tt></i> you will have to apply the
- WindowsXP requireSignOrSeal-Registry patch found in
- the docs/Registry subdirectory.</p><p>Default: <b>server schannel = auto</b></p><p>Example: <b>server schannel = yes</b></p></dd><dt><span class="term"><a name="SERVERSTRING"></a>server string (G)</span></dt><dd><p>This controls what string will show up in the printer comment box in print
- manager and next to the IPC connection in <b>net view</b>. It
- can be any string that you wish to show to your users.</p><p>It also sets what will appear in browse lists next
- to the machine name.</p><p>A <i><tt>%v</tt></i> will be replaced with the Samba
- version number.</p><p>A <i><tt>%h</tt></i> will be replaced with the
- hostname.</p><p>Default: <b>server string = Samba %v</b></p><p>Example: <b>server string = University of GNUs Samba
- Server</b></p></dd><dt><span class="term"><a name="SETDIRECTORY"></a>set directory (S)</span></dt><dd><p>If <b>set directory = no</b>, then
- users of the service may not use the setdir command to change
- directory.</p><p>The <b>setdir</b> command is only implemented
- in the Digital Pathworks client. See the Pathworks documentation
- for details.</p><p>Default: <b>set directory = no</b></p></dd><dt><span class="term"><a name="SETPRIMARYGROUPSCRIPT"></a>set primary group script (G)</span></dt><dd><p>Thanks to the Posix subsystem in NT a Windows User has a
- primary group in addition to the auxiliary groups. This script
- sets the primary group in the unix userdatase when an
- administrator sets the primary group from the windows user
- manager or when fetching a SAM with <b>net rpc
- vampire</b>. <i><tt>%u</tt></i> will be replaced
- with the user whose primary group is to be set.
- <i><tt>%g</tt></i> will be replaced with the group to
- set.</p><p>Default: <span class="emphasis"><em>No default value</em></span></p><p>Example: <b>set primary group script = /usr/sbin/usermod -g '%g' '%u'</b></p></dd><dt><span class="term"><a name="SHAREMODES"></a>share modes (S)</span></dt><dd><p>This enables or disables the honoring of
- the <i><tt>share modes</tt></i> during a file open. These
- modes are used by clients to gain exclusive read or write access
- to a file.</p><p>These open modes are not directly supported by UNIX, so
- they are simulated using shared memory, or lock files if your
- UNIX doesn't support shared memory (almost all do).</p><p>The share modes that are enabled by this option are
- <tt>DENY_DOS</tt>, <tt>DENY_ALL</tt>,
- <tt>DENY_READ</tt>, <tt>DENY_WRITE</tt>,
- <tt>DENY_NONE</tt> and <tt>DENY_FCB</tt>.
- </p><p>This option gives full share compatibility and enabled
- by default.</p><p>You should <span class="emphasis"><em>NEVER</em></span> turn this parameter
- off as many Windows applications will break if you do so.</p><p>Default: <b>share modes = yes</b></p></dd><dt><span class="term"><a name="SHORTPRESERVECASE"></a>short preserve case (S)</span></dt><dd><p>This boolean parameter controls if new files
- which conform to 8.3 syntax, that is all in upper case and of
- suitable length, are created upper case, or if they are forced
- to be the <a href="#DEFAULTCASE"><i><tt>default case
- </tt></i></a>. This option can be use with <a href="#PRESERVECASE"><b>preserve case = yes</b>
- </a> to permit long filenames to retain their case, while short
- names are lowered. </p><p>See the section on <a href="#NAMEMANGLINGSECT" title="NAME MANGLING">NAME MANGLING</a>.</p><p>Default: <b>short preserve case = yes</b></p></dd><dt><span class="term"><a name="SHOWADDPRINTERWIZARD"></a>show add printer wizard (G)</span></dt><dd><p>With the introduction of MS-RPC based printing support
- for Windows NT/2000 client in Samba 2.2, a &quot;Printers...&quot; 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 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 privileges. If the user does not have administrative
- access on the print server (i.e is not root or a member of the
- <i><tt>printer admin</tt></i> group), the OpenPrinterEx()
- call fails and the client makes another open call with a request for
- a lower privilege level. This should succeed, however the APW
- icon will not be displayed.</p><p>Disabling the <i><tt>show add printer wizard</tt></i>
- parameter will always cause the OpenPrinterEx() on the server
- to fail. Thus the APW icon will never be displayed. <span class="emphasis"><em>
- Note :</em></span>This does not prevent the same user from having
- administrative privilege on an individual printer.</p><p>See also <a href="#ADDPRINTERCOMMAND"><i><tt>addprinter
- command</tt></i></a>, <a href="#DELETEPRINTERCOMMAND">
- <i><tt>deleteprinter command</tt></i></a>, <a href="#PRINTERADMIN">
- <i><tt>printer admin</tt></i></a></p><p>Default :<b>show add printer wizard = yes</b></p></dd><dt><span class="term"><a name="SHUTDOWNSCRIPT"></a>shutdown script (G)</span></dt><dd><p><span class="emphasis"><em>This parameter only exists in the HEAD cvs branch</em></span>
- This a full path name to a script called by <a href="smbd.8.html">smbd(8)</a> that should start a shutdown procedure.</p><p>This command will be run as the user connected to the server.</p><p>%m %t %r %f parameters are expanded:</p><div class="itemizedlist"><ul type="disc"><li><p><i><tt>%m</tt></i> will be substituted with the
- shutdown message sent to the server.</p></li><li><p><i><tt>%t</tt></i> will be substituted with the
- number of seconds to wait before effectively starting the
- shutdown procedure.</p></li><li><p><i><tt>%r</tt></i> will be substituted with the
- switch <span class="emphasis"><em>-r</em></span>. It means reboot after shutdown
- for NT.</p></li><li><p><i><tt>%f</tt></i> will be substituted with the
- switch <span class="emphasis"><em>-f</em></span>. It means force the shutdown
- even if applications do not respond for NT.</p></li></ul></div><p>Default: <span class="emphasis"><em>None</em></span>.</p><p>Example: <b>abort shutdown script = /usr/local/samba/sbin/shutdown %m %t %r %f</b></p><p>Shutdown script example:
-</p><pre class="programlisting">
-#!/bin/bash
+ underscores).</P
+></LI
+></UL
+><P
+>The two-digit hash value consists of upper case
+ alphanumeric characters.</P
+><P
+>This algorithm can cause name collisions only if files
+ in a directory share the same first five alphanumeric characters.
+ The probability of such a clash is 1/1300.</P
+><P
+>The name mangling (if enabled) allows a file to be
+ copied between UNIX directories from Windows/DOS while retaining
+ the long UNIX filename. UNIX files can be renamed to a new extension
+ from Windows/DOS and will retain the same basename. Mangled names
+ do not change between sessions.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>mangled names = yes</B
+></P
+></DD
+><DT
+><A
+NAME="MANGLINGMETHOD"
+></A
+>mangling method (G)</DT
+><DD
+><P
+> controls the algorithm used for the generating
+ the mangled names. Can take two different values, "hash" and
+ "hash2". "hash" is the default and is the algorithm that has been
+ used in Samba for many years. "hash2" is a newer and considered
+ a better algorithm (generates less collisions) in the names.
+ However, many Win32 applications store the mangled names and so
+ changing to the new algorithm must not be done
+ lightly as these applications may break unless reinstalled.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>mangling method = hash2</B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>mangling method = hash</B
+></P
+></DD
+><DT
+><A
+NAME="MANGLEPREFIX"
+></A
+>mangle prefix (G)</DT
+><DD
+><P
+> controls the number of prefix
+ characters from the original name used when generating
+ the mangled names. A larger value will give a weaker
+ hash and therefore more name collisions. The minimum
+ value is 1 and the maximum value is 6.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>mangle prefix = 1</B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>mangle prefix = 4</B
+></P
+></DD
+><DT
+><A
+NAME="MANGLEDSTACK"
+></A
+>mangled stack (G)</DT
+><DD
+><P
+>This parameter controls the number of mangled names
+ that should be cached in the Samba server <A
+HREF="smbd.8.html"
+TARGET="_top"
+> smbd(8)</A
+>.</P
+><P
+>This stack is a list of recently mangled base names
+ (extensions are only maintained if they are longer than 3 characters
+ or contains upper case characters).</P
+><P
+>The larger this value, the more likely it is that mangled
+ names can be successfully converted to correct long UNIX names.
+ However, large stack sizes will slow most directory accesses. Smaller
+ stacks save memory in the server (each stack element costs 256 bytes).
+ </P
+><P
+>It is not possible to absolutely guarantee correct long
+ filenames, so be prepared for some surprises!</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>mangled stack = 50</B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>mangled stack = 100</B
+></P
+></DD
+><DT
+><A
+NAME="MANGLINGCHAR"
+></A
+>mangling char (S)</DT
+><DD
+><P
+>This controls what character is used as
+ the <I
+CLASS="EMPHASIS"
+>magic</I
+> character in <A
+HREF="#AEN205"
+>name mangling</A
+>. The default is a '~'
+ but this may interfere with some software. Use this option to set
+ it to whatever you prefer.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>mangling char = ~</B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>mangling char = ^</B
+></P
+></DD
+><DT
+><A
+NAME="MAPARCHIVE"
+></A
+>map archive (S)</DT
+><DD
+><P
+>This controls whether the DOS archive attribute
+ should be mapped to the UNIX owner execute bit. The DOS archive bit
+ is set when a file has been modified since its last backup. One
+ motivation for this option it to keep Samba/your PC from making
+ any file it touches from becoming executable under UNIX. This can
+ be quite annoying for shared source code, documents, etc...</P
+><P
+>Note that this requires the <TT
+CLASS="PARAMETER"
+><I
+>create mask</I
+></TT
+>
+ parameter to be set such that owner execute bit is not masked out
+ (i.e. it must include 100). See the parameter <A
+HREF="#CREATEMASK"
+> <TT
+CLASS="PARAMETER"
+><I
+>create mask</I
+></TT
+></A
+> for details.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>map archive = yes</B
+></P
+></DD
+><DT
+><A
+NAME="MAPHIDDEN"
+></A
+>map hidden (S)</DT
+><DD
+><P
+>This controls whether DOS style hidden files
+ should be mapped to the UNIX world execute bit.</P
+><P
+>Note that this requires the <TT
+CLASS="PARAMETER"
+><I
+>create mask</I
+></TT
+>
+ to be set such that the world execute bit is not masked out (i.e.
+ it must include 001). See the parameter <A
+HREF="#CREATEMASK"
+> <TT
+CLASS="PARAMETER"
+><I
+>create mask</I
+></TT
+></A
+> for details.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>map hidden = no</B
+></P
+></DD
+><DT
+><A
+NAME="MAPSYSTEM"
+></A
+>map system (S)</DT
+><DD
+><P
+>This controls whether DOS style system files
+ should be mapped to the UNIX group execute bit.</P
+><P
+>Note that this requires the <TT
+CLASS="PARAMETER"
+><I
+>create mask</I
+></TT
+>
+ to be set such that the group execute bit is not masked out (i.e.
+ it must include 010). See the parameter <A
+HREF="#CREATEMASK"
+> <TT
+CLASS="PARAMETER"
+><I
+>create mask</I
+></TT
+></A
+> for details.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>map system = no</B
+></P
+></DD
+><DT
+><A
+NAME="MAPTOGUEST"
+></A
+>map to guest (G)</DT
+><DD
+><P
+>This parameter is only useful in <A
+HREF="#SECURITY"
+> security</A
+> modes other than <TT
+CLASS="PARAMETER"
+><I
+>security = share</I
+></TT
+>
+ - i.e. <TT
+CLASS="CONSTANT"
+>user</TT
+>, <TT
+CLASS="CONSTANT"
+>server</TT
+>,
+ and <TT
+CLASS="CONSTANT"
+>domain</TT
+>.</P
+><P
+>This parameter can take three different values, which tell
+ <A
+HREF="smbd.8.html"
+TARGET="_top"
+>smbd(8)</A
+> what to do with user
+ login requests that don't match a valid UNIX user in some way.</P
+><P
+>The three settings are :</P
+><P
+></P
+><UL
+><LI
+><P
+><TT
+CLASS="CONSTANT"
+>Never</TT
+> - Means user login
+ requests with an invalid password are rejected. This is the
+ default.</P
+></LI
+><LI
+><P
+><TT
+CLASS="CONSTANT"
+>Bad User</TT
+> - Means user
+ logins with an invalid password are rejected, unless the username
+ does not exist, in which case it is treated as a guest login and
+ mapped into the <A
+HREF="#GUESTACCOUNT"
+><TT
+CLASS="PARAMETER"
+><I
+> guest account</I
+></TT
+></A
+>.</P
+></LI
+><LI
+><P
+><TT
+CLASS="CONSTANT"
+>Bad Password</TT
+> - Means user logins
+ with an invalid password are treated as a guest login and mapped
+ into the <A
+HREF="#GUESTACCOUNT"
+>guest account</A
+>. Note that
+ this can cause problems as it means that any user incorrectly typing
+ their password will be silently logged on as "guest" - and
+ will not know the reason they cannot access files they think
+ they should - there will have been no message given to them
+ that they got their password wrong. Helpdesk services will
+ <I
+CLASS="EMPHASIS"
+>hate</I
+> you if you set the <TT
+CLASS="PARAMETER"
+><I
+>map to
+ guest</I
+></TT
+> parameter this way :-).</P
+></LI
+></UL
+><P
+>Note that this parameter is needed to set up "Guest"
+ share services when using <TT
+CLASS="PARAMETER"
+><I
+>security</I
+></TT
+> modes other than
+ share. This is because in these modes the name of the resource being
+ requested is <I
+CLASS="EMPHASIS"
+>not</I
+> sent to the server until after
+ the server has successfully authenticated the client so the server
+ cannot make authentication decisions at the correct time (connection
+ to the share) for "Guest" shares.</P
+><P
+>For people familiar with the older Samba releases, this
+ parameter maps to the old compile-time setting of the <TT
+CLASS="CONSTANT"
+> GUEST_SESSSETUP</TT
+> value in local.h.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>map to guest = Never</B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>map to guest = Bad User</B
+></P
+></DD
+><DT
+><A
+NAME="MAXCONNECTIONS"
+></A
+>max connections (S)</DT
+><DD
+><P
+>This option allows the number of simultaneous
+ connections to a service to be limited. If <TT
+CLASS="PARAMETER"
+><I
+>max connections
+ </I
+></TT
+> is greater than 0 then connections will be refused if
+ this number of connections to the service are already open. A value
+ of zero mean an unlimited number of connections may be made.</P
+><P
+>Record lock files are used to implement this feature. The
+ lock files will be stored in the directory specified by the <A
+HREF="#LOCKDIRECTORY"
+><TT
+CLASS="PARAMETER"
+><I
+>lock directory</I
+></TT
+></A
+>
+ option.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>max connections = 0</B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>max connections = 10</B
+></P
+></DD
+><DT
+><A
+NAME="MAXDISKSIZE"
+></A
+>max disk size (G)</DT
+><DD
+><P
+>This option allows you to put an upper limit
+ on the apparent size of disks. If you set this option to 100
+ then all shares will appear to be not larger than 100 MB in
+ size.</P
+><P
+>Note that this option does not limit the amount of
+ data you can put on the disk. In the above case you could still
+ store much more than 100 MB on the disk, but if a client ever asks
+ for the amount of free disk space or the total disk size then the
+ result will be bounded by the amount specified in <TT
+CLASS="PARAMETER"
+><I
+>max
+ disk size</I
+></TT
+>.</P
+><P
+>This option is primarily useful to work around bugs
+ in some pieces of software that can't handle very large disks,
+ particularly disks over 1GB in size.</P
+><P
+>A <TT
+CLASS="PARAMETER"
+><I
+>max disk size</I
+></TT
+> of 0 means no limit.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>max disk size = 0</B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>max disk size = 1000</B
+></P
+></DD
+><DT
+><A
+NAME="MAXLOGSIZE"
+></A
+>max log size (G)</DT
+><DD
+><P
+>This option (an integer in kilobytes) specifies
+ the max size the log file should grow to. Samba periodically checks
+ the size and if it is exceeded it will rename the file, adding
+ a <TT
+CLASS="FILENAME"
+>.old</TT
+> extension.</P
+><P
+>A size of 0 means no limit.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>max log size = 5000</B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>max log size = 1000</B
+></P
+></DD
+><DT
+><A
+NAME="MAXMUX"
+></A
+>max mux (G)</DT
+><DD
+><P
+>This option controls the maximum number of
+ outstanding simultaneous SMB operations that Samba tells the client
+ it will allow. You should never need to set this parameter.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>max mux = 50</B
+></P
+></DD
+><DT
+><A
+NAME="MAXOPENFILES"
+></A
+>max open files (G)</DT
+><DD
+><P
+>This parameter limits the maximum number of
+ open files that one <A
+HREF="smbd.8.html"
+TARGET="_top"
+>smbd(8)</A
+> file
+ serving process may have open for a client at any one time. The
+ default for this parameter is set very high (10,000) as Samba uses
+ only one bit per unopened file.</P
+><P
+>The limit of the number of open files is usually set
+ by the UNIX per-process file descriptor limit rather than
+ this parameter so you should never need to touch this parameter.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>max open files = 10000</B
+></P
+></DD
+><DT
+><A
+NAME="MAXPRINTJOBS"
+></A
+>max print jobs (S)</DT
+><DD
+><P
+>This parameter limits the maximum number of
+ jobs allowable in a Samba printer queue at any given moment.
+ If this number is exceeded, <A
+HREF="smbd.8.html"
+TARGET="_top"
+><B
+CLASS="COMMAND"
+> smbd(8)</B
+></A
+> will remote "Out of Space" to the client.
+ See all <A
+HREF="#TOTALPRINTJOBS"
+><TT
+CLASS="PARAMETER"
+><I
+>total
+ print jobs</I
+></TT
+></A
+>.
+ </P
+><P
+>Default: <B
+CLASS="COMMAND"
+>max print jobs = 1000</B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>max print jobs = 5000</B
+></P
+></DD
+><DT
+><A
+NAME="MAXPROTOCOL"
+></A
+>max protocol (G)</DT
+><DD
+><P
+>The value of the parameter (a string) is the highest
+ protocol level that will be supported by the server.</P
+><P
+>Possible values are :</P
+><P
+></P
+><UL
+><LI
+><P
+><TT
+CLASS="CONSTANT"
+>CORE</TT
+>: Earliest version. No
+ concept of user names.</P
+></LI
+><LI
+><P
+><TT
+CLASS="CONSTANT"
+>COREPLUS</TT
+>: Slight improvements on
+ CORE for efficiency.</P
+></LI
+><LI
+><P
+><TT
+CLASS="CONSTANT"
+>LANMAN1</TT
+>: First <I
+CLASS="EMPHASIS"
+> modern</I
+> version of the protocol. Long filename
+ support.</P
+></LI
+><LI
+><P
+><TT
+CLASS="CONSTANT"
+>LANMAN2</TT
+>: Updates to Lanman1 protocol.
+ </P
+></LI
+><LI
+><P
+><TT
+CLASS="CONSTANT"
+>NT1</TT
+>: Current up to date version of
+ the protocol. Used by Windows NT. Known as CIFS.</P
+></LI
+></UL
+><P
+>Normally this option should not be set as the automatic
+ negotiation phase in the SMB protocol takes care of choosing
+ the appropriate protocol.</P
+><P
+>See also <A
+HREF="#MINPROTOCOL"
+><TT
+CLASS="PARAMETER"
+><I
+>min
+ protocol</I
+></TT
+></A
+></P
+><P
+>Default: <B
+CLASS="COMMAND"
+>max protocol = NT1</B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>max protocol = LANMAN1</B
+></P
+></DD
+><DT
+><A
+NAME="MAXSMBDPROCESSES"
+></A
+>max smbd processes (G)</DT
+><DD
+><P
+>This parameter limits the maximum number of
+ <A
+HREF="smbd.8.html"
+TARGET="_top"
+><B
+CLASS="COMMAND"
+>smbd(8)</B
+></A
+>
+ processes concurrently running on a system and is intended
+ as a stopgap to prevent degrading service to clients in the event
+ that the server has insufficient resources to handle more than this
+ number of connections. Remember that under normal operating
+ conditions, each user will have an <A
+HREF="smbd.8.html"
+TARGET="_top"
+>smbd</A
+> associated with him or her
+ to handle connections to all shares from a given host.
+ </P
+><P
+>Default: <B
+CLASS="COMMAND"
+>max smbd processes = 0</B
+> ## no limit</P
+><P
+>Example: <B
+CLASS="COMMAND"
+>max smbd processes = 1000</B
+></P
+></DD
+><DT
+><A
+NAME="MAXTTL"
+></A
+>max ttl (G)</DT
+><DD
+><P
+>This option tells <A
+HREF="nmbd.8.html"
+TARGET="_top"
+>nmbd(8)</A
+>
+ what the default 'time to live' of NetBIOS names should be (in seconds)
+ when <B
+CLASS="COMMAND"
+>nmbd</B
+> is requesting a name using either a
+ broadcast packet or from a WINS server. You should never need to
+ change this parameter. The default is 3 days.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>max ttl = 259200</B
+></P
+></DD
+><DT
+><A
+NAME="MAXWINSTTL"
+></A
+>max wins ttl (G)</DT
+><DD
+><P
+>This option tells <A
+HREF="nmbd.8.html"
+TARGET="_top"
+>nmbd(8)
+ </A
+> when acting as a WINS server (<A
+HREF="#WINSSUPPORT"
+> <TT
+CLASS="PARAMETER"
+><I
+>wins support = yes</I
+></TT
+></A
+>) what the maximum
+ 'time to live' of NetBIOS names that <B
+CLASS="COMMAND"
+>nmbd</B
+>
+ will grant will be (in seconds). You should never need to change this
+ parameter. The default is 6 days (518400 seconds).</P
+><P
+>See also the <A
+HREF="#MINWINSTTL"
+><TT
+CLASS="PARAMETER"
+><I
+>min
+ wins ttl</I
+></TT
+></A
+> parameter.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>max wins ttl = 518400</B
+></P
+></DD
+><DT
+><A
+NAME="MAXXMIT"
+></A
+>max xmit (G)</DT
+><DD
+><P
+>This option controls the maximum packet size
+ that will be negotiated by Samba. The default is 65535, which
+ is the maximum. In some cases you may find you get better performance
+ with a smaller value. A value below 2048 is likely to cause problems.
+ </P
+><P
+>Default: <B
+CLASS="COMMAND"
+>max xmit = 65535</B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>max xmit = 8192</B
+></P
+></DD
+><DT
+><A
+NAME="MESSAGECOMMAND"
+></A
+>message command (G)</DT
+><DD
+><P
+>This specifies what command to run when the
+ server receives a WinPopup style message.</P
+><P
+>This would normally be a command that would
+ deliver the message somehow. How this is to be done is
+ up to your imagination.</P
+><P
+>An example is:</P
+><P
+><B
+CLASS="COMMAND"
+>message command = csh -c 'xedit %s;rm %s' &#38;</B
+>
+ </P
+><P
+>This delivers the message using <B
+CLASS="COMMAND"
+>xedit</B
+>, then
+ removes it afterwards. <I
+CLASS="EMPHASIS"
+>NOTE THAT IT IS VERY IMPORTANT
+ THAT THIS COMMAND RETURN IMMEDIATELY</I
+>. That's why I
+ have the '&#38;' on the end. If it doesn't return immediately then
+ your PCs may freeze when sending messages (they should recover
+ after 30 seconds, hopefully).</P
+><P
+>All messages are delivered as the global guest user.
+ The command takes the standard substitutions, although <TT
+CLASS="PARAMETER"
+><I
+> %u</I
+></TT
+> won't work (<TT
+CLASS="PARAMETER"
+><I
+>%U</I
+></TT
+> may be better
+ in this case).</P
+><P
+>Apart from the standard substitutions, some additional
+ ones apply. In particular:</P
+><P
+></P
+><UL
+><LI
+><P
+><TT
+CLASS="PARAMETER"
+><I
+>%s</I
+></TT
+> = the filename containing
+ the message.</P
+></LI
+><LI
+><P
+><TT
+CLASS="PARAMETER"
+><I
+>%t</I
+></TT
+> = the destination that
+ the message was sent to (probably the server name).</P
+></LI
+><LI
+><P
+><TT
+CLASS="PARAMETER"
+><I
+>%f</I
+></TT
+> = who the message
+ is from.</P
+></LI
+></UL
+><P
+>You could make this command send mail, or whatever else
+ takes your fancy. Please let us know of any really interesting
+ ideas you have.</P
+><P
+>Here's a way of sending the messages as mail to root:</P
+><P
+><B
+CLASS="COMMAND"
+>message command = /bin/mail -s 'message from %f on
+ %m' root &#60; %s; rm %s</B
+></P
+><P
+>If you don't have a message command then the message
+ won't be delivered and Samba will tell the sender there was
+ an error. Unfortunately WfWg totally ignores the error code
+ and carries on regardless, saying that the message was delivered.
+ </P
+><P
+>If you want to silently delete it then try:</P
+><P
+><B
+CLASS="COMMAND"
+>message command = rm %s</B
+></P
+><P
+>Default: <I
+CLASS="EMPHASIS"
+>no message command</I
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>message command = csh -c 'xedit %s;
+ rm %s' &#38;</B
+></P
+></DD
+><DT
+><A
+NAME="MINPASSWDLENGTH"
+></A
+>min passwd length (G)</DT
+><DD
+><P
+>Synonym for <A
+HREF="#MINPASSWORDLENGTH"
+> <TT
+CLASS="PARAMETER"
+><I
+>min password length</I
+></TT
+></A
+>.</P
+></DD
+><DT
+><A
+NAME="MINPASSWORDLENGTH"
+></A
+>min password length (G)</DT
+><DD
+><P
+>This option sets the minimum length in characters
+ of a plaintext password that <B
+CLASS="COMMAND"
+>smbd</B
+> will accept when performing
+ UNIX password changing.</P
+><P
+>See also <A
+HREF="#UNIXPASSWORDSYNC"
+><TT
+CLASS="PARAMETER"
+><I
+>unix
+ password sync</I
+></TT
+></A
+>, <A
+HREF="#PASSWDPROGRAM"
+> <TT
+CLASS="PARAMETER"
+><I
+>passwd program</I
+></TT
+></A
+> and <A
+HREF="#PASSWDCHATDEBUG"
+><TT
+CLASS="PARAMETER"
+><I
+>passwd chat debug</I
+></TT
+>
+ </A
+>.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>min password length = 5</B
+></P
+></DD
+><DT
+><A
+NAME="MINPRINTSPACE"
+></A
+>min print space (S)</DT
+><DD
+><P
+>This sets the minimum amount of free disk
+ space that must be available before a user will be able to spool
+ a print job. It is specified in kilobytes. The default is 0, which
+ means a user can always spool a print job.</P
+><P
+>See also the <A
+HREF="#PRINTING"
+><TT
+CLASS="PARAMETER"
+><I
+>printing
+ </I
+></TT
+></A
+> parameter.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>min print space = 0</B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>min print space = 2000</B
+></P
+></DD
+><DT
+><A
+NAME="MINPROTOCOL"
+></A
+>min protocol (G)</DT
+><DD
+><P
+>The value of the parameter (a string) is the
+ lowest SMB protocol dialect than Samba will support. Please refer
+ to the <A
+HREF="#MAXPROTOCOL"
+><TT
+CLASS="PARAMETER"
+><I
+>max protocol</I
+></TT
+></A
+>
+ parameter for a list of valid protocol names and a brief description
+ of each. You may also wish to refer to the C source code in
+ <TT
+CLASS="FILENAME"
+>source/smbd/negprot.c</TT
+> for a listing of known protocol
+ dialects supported by clients.</P
+><P
+>If you are viewing this parameter as a security measure, you should
+ also refer to the <A
+HREF="#LANMANAUTH"
+><TT
+CLASS="PARAMETER"
+><I
+>lanman
+ auth</I
+></TT
+></A
+> parameter. Otherwise, you should never need
+ to change this parameter.</P
+><P
+>Default : <B
+CLASS="COMMAND"
+>min protocol = CORE</B
+></P
+><P
+>Example : <B
+CLASS="COMMAND"
+>min protocol = NT1</B
+> # disable DOS
+ clients</P
+></DD
+><DT
+><A
+NAME="MINWINSTTL"
+></A
+>min wins ttl (G)</DT
+><DD
+><P
+>This option tells <A
+HREF="nmbd.8.html"
+TARGET="_top"
+>nmbd(8)</A
+>
+ when acting as a WINS server (<A
+HREF="#WINSSUPPORT"
+><TT
+CLASS="PARAMETER"
+><I
+> wins support = yes</I
+></TT
+></A
+>) what the minimum 'time to live'
+ of NetBIOS names that <B
+CLASS="COMMAND"
+>nmbd</B
+> will grant will be (in
+ seconds). You should never need to change this parameter. The default
+ is 6 hours (21600 seconds).</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>min wins ttl = 21600</B
+></P
+></DD
+><DT
+><A
+NAME="MSDFSPROXY"
+></A
+>msdfs proxy (S)</DT
+><DD
+><P
+>This parameter indicates that the share is a
+ stand-in for another CIFS share whose location is specified by
+ the value of the parameter. When clients attempt to connect to
+ this share, they are redirected to the proxied share using
+ the SMB-Dfs protocol.</P
+><P
+>Only Dfs roots can act as proxy shares. Take a look at the
+ <A
+HREF="#MSDFSROOT"
+><TT
+CLASS="PARAMETER"
+><I
+>msdfs root</I
+></TT
+></A
+>
+ and
+ <A
+HREF="#HOSTMSDFS"
+><TT
+CLASS="PARAMETER"
+><I
+>host msdfs</I
+></TT
+></A
+>
+ options to find out how to set up a Dfs root share.</P
+><P
+>Example: <B
+CLASS="COMMAND"
+>msdfs proxy = \otherserver\someshare</B
+></P
+></DD
+><DT
+><A
+NAME="MSDFSROOT"
+></A
+>msdfs root (S)</DT
+><DD
+><P
+>This boolean parameter is only available if
+ Samba is configured and compiled with the <B
+CLASS="COMMAND"
+> --with-msdfs</B
+> option. If set to <TT
+CLASS="CONSTANT"
+>yes</TT
+>,
+ Samba treats the share as a Dfs root and allows clients to browse
+ the distributed file system tree rooted at the share directory.
+ Dfs links are specified in the share directory by symbolic
+ links of the form <TT
+CLASS="FILENAME"
+>msdfs:serverA\shareA,serverB\shareB</TT
+>
+ and so on. For more information on setting up a Dfs tree
+ on Samba, refer to <A
+HREF="msdfs_setup.html"
+TARGET="_top"
+>msdfs_setup.html
+ </A
+>.</P
+><P
+>See also <A
+HREF="#HOSTMSDFS"
+><TT
+CLASS="PARAMETER"
+><I
+>host msdfs
+ </I
+></TT
+></A
+></P
+><P
+>Default: <B
+CLASS="COMMAND"
+>msdfs root = no</B
+></P
+></DD
+><DT
+><A
+NAME="NAMECACHETIMEOUT"
+></A
+>name cache timeout (G)</DT
+><DD
+><P
+>Specifies the number of seconds it takes before
+ entries in samba's hostname resolve cache time out. If
+ the timeout is set to 0. the caching is disabled.
+ </P
+><P
+>Default: <B
+CLASS="COMMAND"
+>name cache timeout = 660</B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>name cache timeout = 0</B
+></P
+></DD
+><DT
+><A
+NAME="NAMERESOLVEORDER"
+></A
+>name resolve order (G)</DT
+><DD
+><P
+>This option is used by the programs in the Samba
+ suite to determine what naming services to use and in what order
+ to resolve host names to IP addresses. The option takes a space
+ separated string of name resolution options.</P
+><P
+>The options are :"lmhosts", "host", "wins" and "bcast". They
+ cause names to be resolved as follows :</P
+><P
+></P
+><UL
+><LI
+><P
+><TT
+CLASS="CONSTANT"
+>lmhosts</TT
+> : Lookup an IP
+ address in the Samba lmhosts file. If the line in lmhosts has
+ no name type attached to the NetBIOS name (see the <A
+HREF="lmhosts.5.html"
+TARGET="_top"
+>lmhosts(5)</A
+> for details) then
+ any name type matches for lookup.</P
+></LI
+><LI
+><P
+><TT
+CLASS="CONSTANT"
+>host</TT
+> : Do a standard host
+ name to IP address resolution, using the system <TT
+CLASS="FILENAME"
+>/etc/hosts
+ </TT
+>, NIS, or DNS lookups. This method of name resolution
+ is operating system depended for instance on IRIX or Solaris this
+ may be controlled by the <TT
+CLASS="FILENAME"
+>/etc/nsswitch.conf</TT
+>
+ file. Note that this method is only used if the NetBIOS name
+ type being queried is the 0x20 (server) name type, otherwise
+ it is ignored.</P
+></LI
+><LI
+><P
+><TT
+CLASS="CONSTANT"
+>wins</TT
+> : Query a name with
+ the IP address listed in the <A
+HREF="#WINSSERVER"
+><TT
+CLASS="PARAMETER"
+><I
+> wins server</I
+></TT
+></A
+> parameter. If no WINS server has
+ been specified this method will be ignored.</P
+></LI
+><LI
+><P
+><TT
+CLASS="CONSTANT"
+>bcast</TT
+> : Do a broadcast on
+ each of the known local interfaces listed in the <A
+HREF="#INTERFACES"
+><TT
+CLASS="PARAMETER"
+><I
+>interfaces</I
+></TT
+></A
+>
+ parameter. This is the least reliable of the name resolution
+ methods as it depends on the target host being on a locally
+ connected subnet.</P
+></LI
+></UL
+><P
+>Default: <B
+CLASS="COMMAND"
+>name resolve order = lmhosts host wins bcast
+ </B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>name resolve order = lmhosts bcast host
+ </B
+></P
+><P
+>This will cause the local lmhosts file to be examined
+ first, followed by a broadcast attempt, followed by a normal
+ system hostname lookup.</P
+></DD
+><DT
+><A
+NAME="NETBIOSALIASES"
+></A
+>netbios aliases (G)</DT
+><DD
+><P
+>This is a list of NetBIOS names that <A
+HREF="nmbd.8.html"
+TARGET="_top"
+>nmbd(8)</A
+> will advertise as additional
+ names by which the Samba server is known. This allows one machine
+ to appear in browse lists under multiple names. If a machine is
+ acting as a browse server or logon server none
+ of these names will be advertised as either browse server or logon
+ servers, only the primary name of the machine will be advertised
+ with these capabilities.</P
+><P
+>See also <A
+HREF="#NETBIOSNAME"
+><TT
+CLASS="PARAMETER"
+><I
+>netbios
+ name</I
+></TT
+></A
+>.</P
+><P
+>Default: <I
+CLASS="EMPHASIS"
+>empty string (no additional names)</I
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>netbios aliases = TEST TEST1 TEST2</B
+></P
+></DD
+><DT
+><A
+NAME="NETBIOSNAME"
+></A
+>netbios name (G)</DT
+><DD
+><P
+>This sets the NetBIOS name by which a Samba
+ server is known. By default it is the same as the first component
+ of the host's DNS name. If a machine is a browse server or
+ logon server this name (or the first component
+ of the hosts DNS name) will be the name that these services are
+ advertised under.</P
+><P
+>See also <A
+HREF="#NETBIOSALIASES"
+><TT
+CLASS="PARAMETER"
+><I
+>netbios
+ aliases</I
+></TT
+></A
+>.</P
+><P
+>Default: <I
+CLASS="EMPHASIS"
+>machine DNS name</I
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>netbios name = MYNAME</B
+></P
+></DD
+><DT
+><A
+NAME="NETBIOSSCOPE"
+></A
+>netbios scope (G)</DT
+><DD
+><P
+>This sets the NetBIOS scope that Samba will
+ operate under. This should not be set unless every machine
+ on your LAN also sets this value.</P
+></DD
+><DT
+><A
+NAME="NISHOMEDIR"
+></A
+>nis homedir (G)</DT
+><DD
+><P
+>Get the home share server from a NIS map. For
+ UNIX systems that use an automounter, the user's home directory
+ will often be mounted on a workstation on demand from a remote
+ server. </P
+><P
+>When the Samba logon server is not the actual home directory
+ server, but is mounting the home directories via NFS then two
+ network hops would be required to access the users home directory
+ if the logon server told the client to use itself as the SMB server
+ for home directories (one over SMB and one over NFS). This can
+ be very slow.</P
+><P
+>This option allows Samba to return the home share as
+ being on a different server to the logon server and as
+ long as a Samba daemon is running on the home directory server,
+ it will be mounted on the Samba client directly from the directory
+ server. When Samba is returning the home share to the client, it
+ will consult the NIS map specified in <A
+HREF="#HOMEDIRMAP"
+> <TT
+CLASS="PARAMETER"
+><I
+>homedir map</I
+></TT
+></A
+> and return the server
+ listed there.</P
+><P
+>Note that for this option to work there must be a working
+ NIS system and the Samba server with this option must also
+ be a logon server.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>nis homedir = no</B
+></P
+></DD
+><DT
+><A
+NAME="NONUNIXACCOUNTRANGE"
+></A
+>non unix account range (G)</DT
+><DD
+><P
+>The non unix account range parameter specifies
+ the range of 'user ids' that are allocated by the various 'non unix
+ account' passdb backends. These backends allow
+ the storage of passwords for users who don't exist in /etc/passwd.
+ This is most often used for machine account creation.
+ This range of ids should have no existing local or NIS users within
+ it as strange conflicts can occur otherwise.</P
+><P
+>NOTE: These userids never appear on the system and Samba will never
+ 'become' these users. They are used only to ensure that the algorithmic
+ RID mapping does not conflict with normal users.
+ </P
+><P
+>Default: <B
+CLASS="COMMAND"
+>non unix account range = &#60;empty string&#62;
+ </B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>non unix account range = 10000-20000</B
+></P
+></DD
+><DT
+><A
+NAME="NTACLSUPPORT"
+></A
+>nt acl support (S)</DT
+><DD
+><P
+>This boolean parameter controls whether
+ <A
+HREF="smbd.8.html"
+TARGET="_top"
+>smbd(8)</A
+> will attempt to map
+ UNIX permissions into Windows NT access control lists.
+ This parameter was formally a global parameter in releases
+ prior to 2.2.2.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>nt acl support = yes</B
+></P
+></DD
+><DT
+><A
+NAME="NTPIPESUPPORT"
+></A
+>nt pipe support (G)</DT
+><DD
+><P
+>This boolean parameter controls whether
+ <A
+HREF="smbd.8.html"
+TARGET="_top"
+>smbd(8)</A
+> will allow Windows NT
+ clients to connect to the NT SMB specific <TT
+CLASS="CONSTANT"
+>IPC$</TT
+>
+ pipes. This is a developer debugging option and can be left
+ alone.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>nt pipe support = yes</B
+></P
+></DD
+><DT
+><A
+NAME="NTSTATUSSUPPORT"
+></A
+>nt status support (G)</DT
+><DD
+><P
+>This boolean parameter controls whether <A
+HREF="smbd.8.html"
+TARGET="_top"
+>smbd(8)</A
+> will negotiate NT specific status
+ support with Windows NT/2k/XP clients. This is a developer
+ debugging option and should be left alone.
+ If this option is set to <TT
+CLASS="CONSTANT"
+>no</TT
+> then Samba offers
+ exactly the same DOS error codes that versions prior to Samba 2.2.3
+ reported.</P
+><P
+>You should not need to ever disable this parameter.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>nt status support = yes</B
+></P
+></DD
+><DT
+><A
+NAME="NULLPASSWORDS"
+></A
+>null passwords (G)</DT
+><DD
+><P
+>Allow or disallow client access to accounts
+ that have null passwords. </P
+><P
+>See also <A
+HREF="smbpasswd.5.html"
+TARGET="_top"
+>smbpasswd (5)</A
+>.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>null passwords = no</B
+></P
+></DD
+><DT
+><A
+NAME="OBEYPAMRESTRICTIONS"
+></A
+>obey pam restrictions (G)</DT
+><DD
+><P
+>When Samba 2.2 is configured to enable PAM support
+ (i.e. --with-pam), this parameter will control whether or not Samba
+ should obey PAM's account and session management directives. The
+ default behavior is to use PAM for clear text authentication only
+ and to ignore any account or session management. Note that Samba
+ always ignores PAM for authentication in the case of <A
+HREF="#ENCRYPTPASSWORDS"
+><TT
+CLASS="PARAMETER"
+><I
+>encrypt passwords = yes</I
+></TT
+>
+ </A
+>. The reason is that PAM modules cannot support the challenge/response
+ authentication mechanism needed in the presence of SMB password encryption.
+ </P
+><P
+>Default: <B
+CLASS="COMMAND"
+>obey pam restrictions = no</B
+></P
+></DD
+><DT
+><A
+NAME="ONLYUSER"
+></A
+>only user (S)</DT
+><DD
+><P
+>This is a boolean option that controls whether
+ connections with usernames not in the <TT
+CLASS="PARAMETER"
+><I
+>user</I
+></TT
+>
+ list will be allowed. By default this option is disabled so that a
+ client can supply a username to be used by the server. Enabling
+ this parameter will force the server to only use the login
+ names from the <TT
+CLASS="PARAMETER"
+><I
+>user</I
+></TT
+> list and is only really
+ useful in <A
+HREF="#SECURITYEQUALSSHARE"
+>share level</A
+>
+ security.</P
+><P
+>Note that this also means Samba won't try to deduce
+ usernames from the service name. This can be annoying for
+ the [homes] section. To get around this you could use <B
+CLASS="COMMAND"
+>user =
+ %S</B
+> which means your <TT
+CLASS="PARAMETER"
+><I
+>user</I
+></TT
+> list
+ will be just the service name, which for home directories is the
+ name of the user.</P
+><P
+>See also the <A
+HREF="#USER"
+><TT
+CLASS="PARAMETER"
+><I
+>user</I
+></TT
+>
+ </A
+> parameter.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>only user = no</B
+></P
+></DD
+><DT
+><A
+NAME="ONLYGUEST"
+></A
+>only guest (S)</DT
+><DD
+><P
+>A synonym for <A
+HREF="#GUESTONLY"
+><TT
+CLASS="PARAMETER"
+><I
+> guest only</I
+></TT
+></A
+>.</P
+></DD
+><DT
+><A
+NAME="OPLOCKBREAKWAITTIME"
+></A
+>oplock break wait time (G)</DT
+><DD
+><P
+>This is a tuning parameter added due to bugs in
+ both Windows 9x and WinNT. If Samba responds to a client too
+ quickly when that client issues an SMB that can cause an oplock
+ break request, then the network client can fail and not respond
+ to the break request. This tuning parameter (which is set in milliseconds)
+ is the amount of time Samba will wait before sending an oplock break
+ request to such (broken) clients.</P
+><P
+><I
+CLASS="EMPHASIS"
+>DO NOT CHANGE THIS PARAMETER UNLESS YOU HAVE READ
+ AND UNDERSTOOD THE SAMBA OPLOCK CODE</I
+>.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>oplock break wait time = 0</B
+></P
+></DD
+><DT
+><A
+NAME="OPLOCKCONTENTIONLIMIT"
+></A
+>oplock contention limit (S)</DT
+><DD
+><P
+>This is a <I
+CLASS="EMPHASIS"
+>very</I
+> advanced
+ <A
+HREF="smbd.8.html"
+TARGET="_top"
+>smbd(8)</A
+> tuning option to
+ improve the efficiency of the granting of oplocks under multiple
+ client contention for the same file.</P
+><P
+>In brief it specifies a number, which causes <A
+HREF="smbd.8.html"
+TARGET="_top"
+>smbd</A
+> not to
+ grant an oplock even when requested if the approximate number of
+ clients contending for an oplock on the same file goes over this
+ limit. This causes <B
+CLASS="COMMAND"
+>smbd</B
+> to behave in a similar
+ way to Windows NT.</P
+><P
+><I
+CLASS="EMPHASIS"
+>DO NOT CHANGE THIS PARAMETER UNLESS YOU HAVE READ
+ AND UNDERSTOOD THE SAMBA OPLOCK CODE</I
+>.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>oplock contention limit = 2</B
+></P
+></DD
+><DT
+><A
+NAME="OPLOCKS"
+></A
+>oplocks (S)</DT
+><DD
+><P
+>This boolean option tells <B
+CLASS="COMMAND"
+>smbd</B
+> 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 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
+CLASS="FILENAME"
+>Speed.txt</TT
+> in the Samba <TT
+CLASS="FILENAME"
+>docs/</TT
+>
+ directory.</P
+><P
+>Oplocks may be selectively turned off on certain files with a
+ share. See the <A
+HREF="#VETOOPLOCKFILES"
+><TT
+CLASS="PARAMETER"
+><I
+> veto oplock files</I
+></TT
+></A
+> parameter. On some systems
+ oplocks are recognized by the underlying operating system. This
+ allows data synchronization between all access to oplocked files,
+ whether it be via Samba or NFS or a local UNIX process. See the
+ <TT
+CLASS="PARAMETER"
+><I
+>kernel oplocks</I
+></TT
+> parameter for details.</P
+><P
+>See also the <A
+HREF="#KERNELOPLOCKS"
+><TT
+CLASS="PARAMETER"
+><I
+>kernel
+ oplocks</I
+></TT
+></A
+> and <A
+HREF="#LEVEL2OPLOCKS"
+><TT
+CLASS="PARAMETER"
+><I
+> level2 oplocks</I
+></TT
+></A
+> parameters.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>oplocks = yes</B
+></P
+></DD
+><DT
+><A
+NAME="NTLMAUTH"
+></A
+>ntlm auth (G)</DT
+><DD
+><P
+>This parameter determines whether or not <A
+HREF="smbd.8.html"
+TARGET="_top"
+>smbd</A
+> will
+ attempt to authenticate users using the NTLM password hash.
+ If disabled, only the lanman password hashes will be used.
+ </P
+><P
+>Please note that at least this option or <B
+CLASS="COMMAND"
+>lanman auth</B
+> should be enabled in order to be able to log in.
+ </P
+><P
+>Default : <B
+CLASS="COMMAND"
+>ntlm auth = yes</B
+></P
+></DD
+><DT
+><A
+NAME="OSLEVEL"
+></A
+>os level (G)</DT
+><DD
+><P
+>This integer value controls what level Samba
+ advertises itself as for browse elections. The value of this
+ parameter determines whether <A
+HREF="nmbd.8.html"
+TARGET="_top"
+>nmbd(8)</A
+>
+ has a chance of becoming a local master browser for the <TT
+CLASS="PARAMETER"
+><I
+> WORKGROUP</I
+></TT
+> in the local broadcast area.</P
+><P
+><I
+CLASS="EMPHASIS"
+>Note :</I
+>By default, Samba will win
+ a local master browsing election over all Microsoft operating
+ systems except a Windows NT 4.0/2000 Domain Controller. This
+ means that a misconfigured Samba host can effectively isolate
+ a subnet for browsing purposes. See <TT
+CLASS="FILENAME"
+>BROWSING.txt
+ </TT
+> in the Samba <TT
+CLASS="FILENAME"
+>docs/</TT
+> directory
+ for details.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>os level = 20</B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>os level = 65 </B
+></P
+></DD
+><DT
+><A
+NAME="OS2DRIVERMAP"
+></A
+>os2 driver map (G)</DT
+><DD
+><P
+>The parameter is used to define the absolute
+ path to a file containing a mapping of Windows NT printer driver
+ names to OS/2 printer driver names. The format is:</P
+><P
+>&#60;nt driver name&#62; = &#60;os2 driver
+ name&#62;.&#60;device name&#62;</P
+><P
+>For example, a valid entry using the HP LaserJet 5
+ printer driver would appear as <B
+CLASS="COMMAND"
+>HP LaserJet 5L = LASERJET.HP
+ LaserJet 5L</B
+>.</P
+><P
+>The need for the file is due to the printer driver namespace
+ problem described in the <A
+HREF="printer_driver2.html"
+TARGET="_top"
+>Samba
+ Printing HOWTO</A
+>. For more details on OS/2 clients, please
+ refer to the <A
+HREF="OS2-Client-HOWTO.html"
+TARGET="_top"
+>OS2-Client-HOWTO
+ </A
+> containing in the Samba documentation.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>os2 driver map = &#60;empty string&#62;
+ </B
+></P
+></DD
+><DT
+><A
+NAME="PAMPASSWORDCHANGE"
+></A
+>pam password change (G)</DT
+><DD
+><P
+>With the addition of better PAM support in Samba 2.2,
+ this parameter, it is possible to use PAM's password change control
+ flag for Samba. If enabled, then PAM will be used for password
+ changes when requested by an SMB client instead of the program listed in
+ <A
+HREF="#PASSWDPROGRAM"
+><TT
+CLASS="PARAMETER"
+><I
+>passwd program</I
+></TT
+></A
+>.
+ It should be possible to enable this without changing your
+ <A
+HREF="#PASSWDCHAT"
+><TT
+CLASS="PARAMETER"
+><I
+>passwd chat</I
+></TT
+></A
+>
+ parameter for most setups.
+ </P
+><P
+>Default: <B
+CLASS="COMMAND"
+>pam password change = no</B
+></P
+></DD
+><DT
+><A
+NAME="PANICACTION"
+></A
+>panic action (G)</DT
+><DD
+><P
+>This is a Samba developer option that allows a
+ system command to be called when either <A
+HREF="smbd.8.html"
+TARGET="_top"
+> smbd(8)</A
+> or <A
+HREF="nmbd.8.html"
+TARGET="_top"
+>nmbd(8)</A
+>
+ crashes. This is usually used to draw attention to the fact that
+ a problem occurred.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>panic action = &#60;empty string&#62;</B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>panic action = "/bin/sleep 90000"</B
+></P
+></DD
+><DT
+><A
+NAME="PARANOIDSERVERSECURITY"
+></A
+>paranoid server security (G)</DT
+><DD
+><P
+>Some version of NT 4.x allow non-guest
+ users with a bad passowrd. When this option is enabled, samba will not
+ use a broken NT 4.x server as password server, but instead complain
+ to the logs and exit.
+ </P
+><P
+>Default: <B
+CLASS="COMMAND"
+>paranoid server security = yes</B
+></P
+></DD
+><DT
+><A
+NAME="PASSDBBACKEND"
+></A
+>passdb backend (G)</DT
+><DD
+><P
+>This option allows the administrator to chose which backends to retrieve and store passwords with. This allows (for example) both
+ smbpasswd and tdbsam to be used without a recompile.
+ Multiple backends can be specified, separated by spaces. The backends will be searched in the order they are specified. New users are always added to the first backend specified.
+ Experimental backends must still be selected
+ (eg --with-tdbsam) at configure time.
+ </P
+><P
+>This parameter is in two parts, the backend's name, and a 'location'
+ string that has meaning only to that particular backed. These are separated
+ by a : character.</P
+><P
+>Available backends can include:
+ <P
+></P
+><UL
+><LI
+><P
+><B
+CLASS="COMMAND"
+>smbpasswd</B
+> - The default smbpasswd
+ backend. Takes a path to the smbpasswd file as an optional argument.</P
+></LI
+><LI
+><P
+><B
+CLASS="COMMAND"
+>smbpasswd_nua</B
+> - The smbpasswd
+ backend, but with support for 'not unix accounts'.
+ Takes a path to the smbpasswd file as an optional argument.</P
+><P
+>See also <A
+HREF="#NONUNIXACCOUNTRANGE"
+> <TT
+CLASS="PARAMETER"
+><I
+>non unix account range</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><B
+CLASS="COMMAND"
+>tdbsam</B
+> - The TDB based password storage
+ backend. Takes a path to the TDB as an optional argument (defaults to passdb.tdb
+ in the <A
+HREF="#PRIVATEDIR"
+> <TT
+CLASS="PARAMETER"
+><I
+>private dir</I
+></TT
+></A
+> directory.</P
+></LI
+><LI
+><P
+><B
+CLASS="COMMAND"
+>tdbsam_nua</B
+> - The TDB based password storage
+ backend, with non unix account support. Takes a path to the TDB as an optional argument (defaults to passdb.tdb
+ in the <A
+HREF="#PRIVATEDIR"
+> <TT
+CLASS="PARAMETER"
+><I
+>private dir</I
+></TT
+></A
+> directory.</P
+><P
+>See also <A
+HREF="#NONUNIXACCOUNTRANGE"
+> <TT
+CLASS="PARAMETER"
+><I
+>non unix account range</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><B
+CLASS="COMMAND"
+>ldapsam</B
+> - The LDAP based passdb
+ backend. Takes an LDAP URL as an optional argument (defaults to
+ <B
+CLASS="COMMAND"
+>ldap://localhost</B
+>)</P
+></LI
+><LI
+><P
+><B
+CLASS="COMMAND"
+>ldapsam_nua</B
+> - The LDAP based passdb
+ backend, with non unix account support. Takes an LDAP URL as an optional argument (defaults to
+ <B
+CLASS="COMMAND"
+>ldap://localhost</B
+>)</P
+><P
+>Note: In this module, any account without a matching POSIX account is regarded
+ as 'non unix'. </P
+><P
+>See also <A
+HREF="#NONUNIXACCOUNTRANGE"
+> <TT
+CLASS="PARAMETER"
+><I
+>non unix account
+ range</I
+></TT
+></A
+></P
+><P
+>LDAP connections should be secured where
+ possible. This may be done using either
+ Start-TLS (see <A
+HREF="#LDAPSSL"
+> <TT
+CLASS="PARAMETER"
+><I
+>ldap ssl</I
+></TT
+></A
+>) or by
+ specifying <TT
+CLASS="PARAMETER"
+><I
+>ldaps://</I
+></TT
+> in
+ the URL argument.
+ </P
+></LI
+><LI
+><P
+><B
+CLASS="COMMAND"
+>nisplussam</B
+> - The NIS+ based passdb backend. Takes name NIS domain as an optional argument. Only works with sun NIS+ servers. </P
+></LI
+><LI
+><P
+><B
+CLASS="COMMAND"
+>plugin</B
+> - Allows Samba to load an
+ arbitary passdb backend from the .so specified as a compulsary argument.
+ </P
+><P
+>Any characters after the (optional) second : are passed to the plugin
+ for its own processing</P
+></LI
+><LI
+><P
+><B
+CLASS="COMMAND"
+>unixsam</B
+> - (EXPERIMENTAL) Allows samba to map all (other) available unix users</P
+><P
+>This backend uses the standard unix database for retrieving users. Users included
+ in this pdb are NOT listed in samba user listings and users included in this pdb won't be
+ able to login. The use of this backend is to always be able to display the owner of a file
+ on the samba server - even when the user doesn't have a 'real' samba account in one of the
+ other passdb backends.
+ </P
+><P
+>This backend should always be the last backend listed, since it contains all users in
+ the unix passdb and might 'override' mappings if specified earlier. It's meant to only return
+ accounts for users that aren't covered by the previous backends.</P
+></LI
+></UL
+>
+ </P
+><P
+>Default: <B
+CLASS="COMMAND"
+>passdb backend = smbpasswd guest</B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>passdb backend = tdbsam:/etc/samba/private/passdb.tdb smbpasswd:/etc/samba/smbpasswd </B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>passdb backend = ldapsam_nua:ldaps://ldap.example.com </B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>passdb backend = plugin:/usr/local/samba/lib/my_passdb.so:my_plugin_args tdbsam:/etc/samba/private/passdb.tdb</B
+></P
+></DD
+><DT
+><A
+NAME="PASSWDCHAT"
+></A
+>passwd chat (G)</DT
+><DD
+><P
+>This string controls the <I
+CLASS="EMPHASIS"
+>"chat"</I
+>
+ conversation that takes places between <A
+HREF="smbd.8.html"
+TARGET="_top"
+>smbd</A
+> and the local password changing
+ program to change the user's password. The string describes a
+ sequence of response-receive pairs that <A
+HREF="smbd.8.html"
+TARGET="_top"
+> smbd(8)</A
+> uses to determine what to send to the
+ <A
+HREF="#PASSWDPROGRAM"
+><TT
+CLASS="PARAMETER"
+><I
+>passwd program</I
+></TT
+>
+ </A
+> and what to expect back. If the expected output is not
+ received then the password is not changed.</P
+><P
+>This chat sequence is often quite site specific, depending
+ on what local methods are used for password control (such as NIS
+ etc).</P
+><P
+>Note that this parameter only is only used if the <A
+HREF="#UNIXPASSWORDSYNC"
+><TT
+CLASS="PARAMETER"
+><I
+>unix
+ password sync</I
+></TT
+></A
+> parameter is set to <TT
+CLASS="CONSTANT"
+>yes</TT
+>. This
+ sequence is then called <I
+CLASS="EMPHASIS"
+>AS ROOT</I
+> when the SMB password
+ in the smbpasswd file is being changed, without access to the old
+ password cleartext. This means that root must be able to reset the user's password
+ without knowing the text of the previous password. In the presence of NIS/YP,
+ this means that the <A
+HREF="#PASSWDPROGRAM"
+>passwd program</A
+> must be
+ executed on the NIS master.
+ </P
+><P
+>The string can contain the macro <TT
+CLASS="PARAMETER"
+><I
+>%n</I
+></TT
+> which is substituted
+ for the new password. The chat sequence can also contain the standard
+ macros <TT
+CLASS="CONSTANT"
+>\n</TT
+>, <TT
+CLASS="CONSTANT"
+>\r</TT
+>, <TT
+CLASS="CONSTANT"
+> \t</TT
+> and <TT
+CLASS="CONSTANT"
+>\s</TT
+> to give line-feed,
+ carriage-return, tab and space. The chat sequence string can also contain
+ a '*' which matches any sequence of characters.
+ Double quotes can be used to collect strings with spaces
+ in them into a single string.</P
+><P
+>If the send string in any part of the chat sequence
+ is a full stop ".", then no string is sent. Similarly,
+ if the expect string is a full stop then no string is expected.</P
+><P
+>If the <A
+HREF="#PAMPASSWORDCHANGE"
+><TT
+CLASS="PARAMETER"
+><I
+>pam
+ password change</I
+></TT
+></A
+> parameter is set to <TT
+CLASS="CONSTANT"
+>yes</TT
+>, the chat pairs
+ may be matched in any order, and success is determined by the PAM result,
+ not any particular output. The \n macro is ignored for PAM conversions.
+ </P
+><P
+>See also <A
+HREF="#UNIXPASSWORDSYNC"
+><TT
+CLASS="PARAMETER"
+><I
+>unix password
+ sync</I
+></TT
+></A
+>, <A
+HREF="#PASSWDPROGRAM"
+><TT
+CLASS="PARAMETER"
+><I
+> passwd program</I
+></TT
+></A
+> ,<A
+HREF="#PASSWDCHATDEBUG"
+> <TT
+CLASS="PARAMETER"
+><I
+>passwd chat debug</I
+></TT
+></A
+> and <A
+HREF="#PAMPASSWORDCHANGE"
+> <TT
+CLASS="PARAMETER"
+><I
+>pam password change</I
+></TT
+></A
+>.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>passwd chat = *new*password* %n\n
+ *new*password* %n\n *changed*</B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>passwd chat = "*Enter OLD password*" %o\n
+ "*Enter NEW password*" %n\n "*Reenter NEW password*" %n\n "*Password
+ changed*"</B
+></P
+></DD
+><DT
+><A
+NAME="PASSWDCHATDEBUG"
+></A
+>passwd chat debug (G)</DT
+><DD
+><P
+>This boolean specifies if the passwd chat script
+ parameter is run in <I
+CLASS="EMPHASIS"
+>debug</I
+> mode. In this mode the
+ strings passed to and received from the passwd chat are printed
+ in the <A
+HREF="smbd.8.html"
+TARGET="_top"
+>smbd(8)</A
+> log with a
+ <A
+HREF="#DEBUGLEVEL"
+><TT
+CLASS="PARAMETER"
+><I
+>debug level</I
+></TT
+></A
+>
+ of 100. This is a dangerous option as it will allow plaintext passwords
+ to be seen in the <B
+CLASS="COMMAND"
+>smbd</B
+> log. It is available to help
+ Samba admins debug their <TT
+CLASS="PARAMETER"
+><I
+>passwd chat</I
+></TT
+> scripts
+ when calling the <TT
+CLASS="PARAMETER"
+><I
+>passwd program</I
+></TT
+> and should
+ be turned off after this has been done. This option has no effect if the
+ <A
+HREF="#PAMPASSWORDCHANGE"
+><TT
+CLASS="PARAMETER"
+><I
+>pam password change</I
+></TT
+></A
+>
+ paramter is set. This parameter is off by default.</P
+><P
+>See also <A
+HREF="#PASSWDCHAT"
+><TT
+CLASS="PARAMETER"
+><I
+>passwd chat</I
+></TT
+>
+ </A
+>, <A
+HREF="#PAMPASSWORDCHANGE"
+><TT
+CLASS="PARAMETER"
+><I
+>pam password change</I
+></TT
+>
+ </A
+>, <A
+HREF="#PASSWDPROGRAM"
+><TT
+CLASS="PARAMETER"
+><I
+>passwd program</I
+></TT
+>
+ </A
+>.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>passwd chat debug = no</B
+></P
+></DD
+><DT
+><A
+NAME="PASSWDPROGRAM"
+></A
+>passwd program (G)</DT
+><DD
+><P
+>The name of a program that can be used to set
+ UNIX user passwords. Any occurrences of <TT
+CLASS="PARAMETER"
+><I
+>%u</I
+></TT
+>
+ will be replaced with the user name. The user name is checked for
+ existence before calling the password changing program.</P
+><P
+>Also note that many passwd programs insist in <I
+CLASS="EMPHASIS"
+>reasonable
+ </I
+> passwords, such as a minimum length, or the inclusion
+ of mixed case chars and digits. This can pose a problem as some clients
+ (such as Windows for Workgroups) uppercase the password before sending
+ it.</P
+><P
+><I
+CLASS="EMPHASIS"
+>Note</I
+> that if the <TT
+CLASS="PARAMETER"
+><I
+>unix
+ password sync</I
+></TT
+> parameter is set to <TT
+CLASS="CONSTANT"
+>yes
+ </TT
+> then this program is called <I
+CLASS="EMPHASIS"
+>AS ROOT</I
+>
+ before the SMB password in the <A
+HREF="smbpasswd.5.html"
+TARGET="_top"
+>smbpasswd(5)
+ </A
+> file is changed. If this UNIX password change fails, then
+ <B
+CLASS="COMMAND"
+>smbd</B
+> will fail to change the SMB password also
+ (this is by design).</P
+><P
+>If the <TT
+CLASS="PARAMETER"
+><I
+>unix password sync</I
+></TT
+> parameter
+ is set this parameter <I
+CLASS="EMPHASIS"
+>MUST USE ABSOLUTE PATHS</I
+>
+ for <I
+CLASS="EMPHASIS"
+>ALL</I
+> programs called, and must be examined
+ for security implications. Note that by default <TT
+CLASS="PARAMETER"
+><I
+>unix
+ password sync</I
+></TT
+> is set to <TT
+CLASS="CONSTANT"
+>no</TT
+>.</P
+><P
+>See also <A
+HREF="#UNIXPASSWORDSYNC"
+><TT
+CLASS="PARAMETER"
+><I
+>unix
+ password sync</I
+></TT
+></A
+>.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>passwd program = /bin/passwd</B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>passwd program = /sbin/npasswd %u</B
+>
+ </P
+></DD
+><DT
+><A
+NAME="PASSWORDLEVEL"
+></A
+>password level (G)</DT
+><DD
+><P
+>Some client/server combinations have difficulty
+ with mixed-case passwords. One offending client is Windows for
+ Workgroups, which for some reason forces passwords to upper
+ case when using the LANMAN1 protocol, but leaves them alone when
+ using COREPLUS! Another problem child is the Windows 95/98
+ family of operating systems. These clients upper case clear
+ text passwords even when NT LM 0.12 selected by the protocol
+ negotiation request/response.</P
+><P
+>This parameter defines the maximum number of characters
+ that may be upper case in passwords.</P
+><P
+>For example, say the password given was "FRED". If <TT
+CLASS="PARAMETER"
+><I
+> password level</I
+></TT
+> is set to 1, the following combinations
+ would be tried if "FRED" failed:</P
+><P
+>"Fred", "fred", "fRed", "frEd","freD"</P
+><P
+>If <TT
+CLASS="PARAMETER"
+><I
+>password level</I
+></TT
+> was set to 2,
+ the following combinations would also be tried: </P
+><P
+>"FRed", "FrEd", "FreD", "fREd", "fReD", "frED", ..</P
+><P
+>And so on.</P
+><P
+>The higher value this parameter is set to the more likely
+ it is that a mixed case password will be matched against a single
+ case password. However, you should be aware that use of this
+ parameter reduces security and increases the time taken to
+ process a new connection.</P
+><P
+>A value of zero will cause only two attempts to be
+ made - the password as is and the password in all-lower case.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>password level = 0</B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>password level = 4</B
+></P
+></DD
+><DT
+><A
+NAME="PASSWORDSERVER"
+></A
+>password server (G)</DT
+><DD
+><P
+>By specifying the name of another SMB server (such
+ as a WinNT box) with this option, and using <B
+CLASS="COMMAND"
+>security = domain
+ </B
+> or <B
+CLASS="COMMAND"
+>security = server</B
+> you can get Samba
+ to do all its username/password validation via a remote server.</P
+><P
+>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
+ name to the lmhosts file which is stored in the same directory
+ as the <TT
+CLASS="FILENAME"
+>smb.conf</TT
+> file.</P
+><P
+>The name of the password server is looked up using the
+ parameter <A
+HREF="#NAMERESOLVEORDER"
+><TT
+CLASS="PARAMETER"
+><I
+>name
+ resolve order</I
+></TT
+></A
+> and so may resolved
+ by any method and order described in that parameter.</P
+><P
+>The password server must be a machine capable of using
+ the "LM1.2X002" or the "NT LM 0.12" protocol, and it must be in
+ user level security mode.</P
+><P
+><I
+CLASS="EMPHASIS"
+>NOTE:</I
+> Using a password server
+ means your UNIX box (running Samba) is only as secure as your
+ password server. <I
+CLASS="EMPHASIS"
+>DO NOT CHOOSE A PASSWORD SERVER THAT
+ YOU DON'T COMPLETELY TRUST</I
+>.</P
+><P
+>Never point a Samba server at itself for password
+ serving. This will cause a loop and could lock up your Samba
+ server!</P
+><P
+>The name of the password server takes the standard
+ substitutions, but probably the only useful one is <TT
+CLASS="PARAMETER"
+><I
+>%m
+ </I
+></TT
+>, which means the Samba server will use the incoming
+ 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"
+><I
+>security</I
+></TT
+> parameter is set to
+ <TT
+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 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
+> is that if you list several hosts in the
+ <TT
+CLASS="PARAMETER"
+><I
+>password server</I
+></TT
+> option then <B
+CLASS="COMMAND"
+>smbd
+ </B
+> will try each in turn till it finds one that responds. This
+ is useful in case your primary server goes down.</P
+><P
+>If the <TT
+CLASS="PARAMETER"
+><I
+>password server</I
+></TT
+> option is set
+ to the character '*', then Samba will attempt to auto-locate the
+ Primary or Backup Domain controllers to authenticate against by
+ doing a query for the name <TT
+CLASS="CONSTANT"
+>WORKGROUP&#60;1C&#62;</TT
+>
+ and then contacting each server returned in the list of IP
+ addresses from the name resolution source. </P
+><P
+>If the list of servers contains both names and the '*'
+ character, the list is treated as a list of preferred
+ domain controllers, but an auto lookup of all remaining DC's
+ will be added to the list as well. Samba will not attempt to optimize
+ this list by locating the closest DC.</P
+><P
+>If the <TT
+CLASS="PARAMETER"
+><I
+>security</I
+></TT
+> parameter is
+ set to <TT
+CLASS="CONSTANT"
+>server</TT
+>, then there are different
+ restrictions that <B
+CLASS="COMMAND"
+>security = domain</B
+> doesn't
+ suffer from:</P
+><P
+></P
+><UL
+><LI
+><P
+>You may list several password servers in
+ the <TT
+CLASS="PARAMETER"
+><I
+>password server</I
+></TT
+> parameter, however if an
+ <B
+CLASS="COMMAND"
+>smbd</B
+> makes a connection to a password server,
+ and then the password server fails, no more users will be able
+ to be authenticated from this <B
+CLASS="COMMAND"
+>smbd</B
+>. This is a
+ restriction of the SMB/CIFS protocol when in <B
+CLASS="COMMAND"
+>security = server
+ </B
+> mode and cannot be fixed in Samba.</P
+></LI
+><LI
+><P
+>If you are using a Windows NT server as your
+ password server then you will have to ensure that your users
+ are able to login from the Samba server, as when in <B
+CLASS="COMMAND"
+> security = server</B
+> mode the network logon will appear to
+ come from there rather than from the users workstation.</P
+></LI
+></UL
+><P
+>See also the <A
+HREF="#SECURITY"
+><TT
+CLASS="PARAMETER"
+><I
+>security
+ </I
+></TT
+></A
+> parameter.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>password server = &#60;empty string&#62;</B
+>
+ </P
+><P
+>Example: <B
+CLASS="COMMAND"
+>password server = NT-PDC, NT-BDC1, NT-BDC2, *
+ </B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>password server = *</B
+></P
+></DD
+><DT
+><A
+NAME="PATH"
+></A
+>path (S)</DT
+><DD
+><P
+>This parameter specifies a directory to which
+ the user of the service is to be given access. In the case of
+ printable services, this is where print data will spool prior to
+ being submitted to the host for printing.</P
+><P
+>For a printable service offering guest access, the service
+ should be readonly and the path should be world-writeable and
+ have the sticky bit set. This is not mandatory of course, but
+ you probably won't get the results you expect if you do
+ otherwise.</P
+><P
+>Any occurrences of <TT
+CLASS="PARAMETER"
+><I
+>%u</I
+></TT
+> in the path
+ will be replaced with the UNIX username that the client is using
+ on this connection. Any occurrences of <TT
+CLASS="PARAMETER"
+><I
+>%m</I
+></TT
+>
+ will be replaced by the NetBIOS name of the machine they are
+ connecting from. These replacements are very useful for setting
+ up pseudo home directories for users.</P
+><P
+>Note that this path will be based on <A
+HREF="#ROOTDIR"
+> <TT
+CLASS="PARAMETER"
+><I
+>root dir</I
+></TT
+></A
+> if one was specified.</P
+><P
+>Default: <I
+CLASS="EMPHASIS"
+>none</I
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>path = /home/fred</B
+></P
+></DD
+><DT
+><A
+NAME="PIDDIRECTORY"
+></A
+>pid directory (G)</DT
+><DD
+><P
+>This option specifies the directory where pid
+ files will be placed. </P
+><P
+>Default: <B
+CLASS="COMMAND"
+>pid directory = ${prefix}/var/locks</B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>pid directory = /var/run/</B
+>
+ </P
+></DD
+><DT
+><A
+NAME="POSIXLOCKING"
+></A
+>posix locking (S)</DT
+><DD
+><P
+>The <A
+HREF="smbd.8.html"
+TARGET="_top"
+><B
+CLASS="COMMAND"
+>smbd(8)</B
+></A
+>
+ daemon maintains an database of file locks obtained by SMB clients.
+ The default behavior is to map this internal database to POSIX
+ locks. This means that file locks obtained by SMB clients are
+ consistent with those seen by POSIX compliant applications accessing
+ the files via a non-SMB method (e.g. NFS or local file access).
+ You should never need to disable this parameter.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>posix locking = yes</B
+></P
+></DD
+><DT
+><A
+NAME="POSTEXEC"
+></A
+>postexec (S)</DT
+><DD
+><P
+>This option specifies a command to be run
+ whenever the service is disconnected. It takes the usual
+ substitutions. The command may be run as the root on some
+ systems.</P
+><P
+>An interesting example may be to unmount server
+ resources:</P
+><P
+><B
+CLASS="COMMAND"
+>postexec = /etc/umount /cdrom</B
+></P
+><P
+>See also <A
+HREF="#PREEXEC"
+><TT
+CLASS="PARAMETER"
+><I
+>preexec</I
+></TT
+>
+ </A
+>.</P
+><P
+>Default: <I
+CLASS="EMPHASIS"
+>none (no command executed)</I
+>
+ </P
+><P
+>Example: <B
+CLASS="COMMAND"
+>postexec = echo \"%u disconnected from %S
+ from %m (%I)\" &#62;&#62; /tmp/log</B
+></P
+></DD
+><DT
+><A
+NAME="POSTSCRIPT"
+></A
+>postscript (S)</DT
+><DD
+><P
+>This parameter forces a printer to interpret
+ the print files as PostScript. This is done by adding a <TT
+CLASS="CONSTANT"
+>%!
+ </TT
+> to the start of print output.</P
+><P
+>This is most useful when you have lots of PCs that persist
+ in putting a control-D at the start of print jobs, which then
+ confuses your printer.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>postscript = no</B
+></P
+></DD
+><DT
+><A
+NAME="PREEXEC"
+></A
+>preexec (S)</DT
+><DD
+><P
+>This option specifies a command to be run whenever
+ the service is connected to. It takes the usual substitutions.</P
+><P
+>An interesting example is to send the users a welcome
+ message every time they log in. Maybe a message of the day? Here
+ is an example:</P
+><P
+><B
+CLASS="COMMAND"
+>preexec = csh -c 'echo \"Welcome to %S!\" |
+ /usr/local/samba/bin/smbclient -M %m -I %I' &#38; </B
+></P
+><P
+>Of course, this could get annoying after a while :-)</P
+><P
+>See also <A
+HREF="#PREEXECCLOSE"
+><TT
+CLASS="PARAMETER"
+><I
+>preexec close
+ </I
+></TT
+></A
+> and <A
+HREF="#POSTEXEC"
+><TT
+CLASS="PARAMETER"
+><I
+>postexec
+ </I
+></TT
+></A
+>.</P
+><P
+>Default: <I
+CLASS="EMPHASIS"
+>none (no command executed)</I
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>preexec = echo \"%u connected to %S from %m
+ (%I)\" &#62;&#62; /tmp/log</B
+></P
+></DD
+><DT
+><A
+NAME="PREEXECCLOSE"
+></A
+>preexec close (S)</DT
+><DD
+><P
+>This boolean option controls whether a non-zero
+ return code from <A
+HREF="#PREEXEC"
+><TT
+CLASS="PARAMETER"
+><I
+>preexec
+ </I
+></TT
+></A
+> should close the service being connected to.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>preexec close = no</B
+></P
+></DD
+><DT
+><A
+NAME="PREFERREDMASTER"
+></A
+>preferred master (G)</DT
+><DD
+><P
+>This boolean parameter controls if <A
+HREF="nmbd.8.html"
+TARGET="_top"
+>nmbd(8)</A
+> is a preferred master browser
+ for its workgroup.</P
+><P
+>If this is set to <TT
+CLASS="CONSTANT"
+>yes</TT
+>, on startup, <B
+CLASS="COMMAND"
+>nmbd</B
+>
+ will force an election, and it will have a slight advantage in
+ winning the election. It is recommended that this parameter is
+ used in conjunction with <B
+CLASS="COMMAND"
+><A
+HREF="#DOMAINMASTER"
+><TT
+CLASS="PARAMETER"
+><I
+> domain master</I
+></TT
+></A
+> = yes</B
+>, so that <B
+CLASS="COMMAND"
+> nmbd</B
+> can guarantee becoming a domain master.</P
+><P
+>Use this option with caution, because if there are several
+ hosts (whether Samba servers, Windows 95 or NT) that are preferred
+ master browsers on the same subnet, they will each periodically
+ and continuously attempt to become the local master browser.
+ This will result in unnecessary broadcast traffic and reduced browsing
+ capabilities.</P
+><P
+>See also <A
+HREF="#OSLEVEL"
+><TT
+CLASS="PARAMETER"
+><I
+>os level</I
+></TT
+>
+ </A
+>.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>preferred master = auto</B
+></P
+></DD
+><DT
+><A
+NAME="PREFEREDMASTER"
+></A
+>prefered master (G)</DT
+><DD
+><P
+>Synonym for <A
+HREF="#PREFERREDMASTER"
+><TT
+CLASS="PARAMETER"
+><I
+> preferred master</I
+></TT
+></A
+> for people who cannot spell :-).</P
+></DD
+><DT
+><A
+NAME="PRELOAD"
+></A
+>preload (G)</DT
+><DD
+><P
+>This is a list of services that you want to be
+ automatically added to the browse lists. This is most useful
+ for homes and printers services that would otherwise not be
+ visible.</P
+><P
+>Note that if you just want all printers in your
+ printcap file loaded then the <A
+HREF="#LOADPRINTERS"
+> <TT
+CLASS="PARAMETER"
+><I
+>load printers</I
+></TT
+></A
+> option is easier.</P
+><P
+>Default: <I
+CLASS="EMPHASIS"
+>no preloaded services</I
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>preload = fred lp colorlp</B
+></P
+></DD
+><DT
+><A
+NAME="PRESERVECASE"
+></A
+>preserve case (S)</DT
+><DD
+><P
+> This controls if new filenames are created
+ with the case that the client passes, or if they are forced to
+ be the <A
+HREF="#DEFAULTCASE"
+><TT
+CLASS="PARAMETER"
+><I
+>default case
+ </I
+></TT
+></A
+>.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>preserve case = yes</B
+></P
+><P
+>See the section on <A
+HREF="#AEN205"
+>NAME
+ MANGLING</A
+> for a fuller discussion.</P
+></DD
+><DT
+><A
+NAME="PRINTCOMMAND"
+></A
+>print command (S)</DT
+><DD
+><P
+>After a print job has finished spooling to
+ a service, this command will be used via a <B
+CLASS="COMMAND"
+>system()</B
+>
+ call to process the spool file. Typically the command specified will
+ submit the spool file to the host's printing subsystem, but there
+ is no requirement that this be the case. The server will not remove
+ the spool file, so whatever command you specify should remove the
+ spool file when it has been processed, otherwise you will need to
+ manually remove old spool files.</P
+><P
+>The print command is simply a text string. It will be used
+ verbatim after macro substitutions have been made:</P
+><P
+>s, %p - the path to the spool
+ file name</P
+><P
+>%p - the appropriate printer
+ name</P
+><P
+>%J - the job
+ name as transmitted by the client.</P
+><P
+>%c - The number of printed pages
+ of the spooled job (if known).</P
+><P
+>%z - the size of the spooled
+ print job (in bytes)</P
+><P
+>The print command <I
+CLASS="EMPHASIS"
+>MUST</I
+> contain at least
+ one occurrence of <TT
+CLASS="PARAMETER"
+><I
+>%s</I
+></TT
+> or <TT
+CLASS="PARAMETER"
+><I
+>%f
+ </I
+></TT
+> - the <TT
+CLASS="PARAMETER"
+><I
+>%p</I
+></TT
+> is optional. At the time
+ a job is submitted, if no printer name is supplied the <TT
+CLASS="PARAMETER"
+><I
+>%p
+ </I
+></TT
+> will be silently removed from the printer command.</P
+><P
+>If specified in the [global] section, the print command given
+ will be used for any printable service that does not have its own
+ print command specified.</P
+><P
+>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.</P
+><P
+>Note that printing may fail on some UNIXes from the
+ <TT
+CLASS="CONSTANT"
+>nobody</TT
+> account. If this happens then create
+ an alternative guest account that can print and set the <A
+HREF="#GUESTACCOUNT"
+><TT
+CLASS="PARAMETER"
+><I
+>guest account</I
+></TT
+></A
+>
+ in the [global] section.</P
+><P
+>You can form quite complex print commands by realizing
+ that they are just passed to a shell. For example the following
+ will log a print job, print the file, then remove it. Note that
+ ';' is the usual separator for command in shell scripts.</P
+><P
+><B
+CLASS="COMMAND"
+>print command = echo Printing %s &#62;&#62;
+ /tmp/print.log; lpr -P %p %s; rm %s</B
+></P
+><P
+>You may have to vary this command considerably depending
+ on how you normally print files on your system. The default for
+ the parameter varies depending on the setting of the <A
+HREF="#PRINTING"
+> <TT
+CLASS="PARAMETER"
+><I
+>printing</I
+></TT
+></A
+> parameter.</P
+><P
+>Default: For <B
+CLASS="COMMAND"
+>printing = BSD, AIX, QNX, LPRNG
+ or PLP :</B
+></P
+><P
+><B
+CLASS="COMMAND"
+>print command = lpr -r -P%p %s</B
+></P
+><P
+>For <B
+CLASS="COMMAND"
+>printing = SYSV or HPUX :</B
+></P
+><P
+><B
+CLASS="COMMAND"
+>print command = lp -c -d%p %s; rm %s</B
+></P
+><P
+>For <B
+CLASS="COMMAND"
+>printing = SOFTQ :</B
+></P
+><P
+><B
+CLASS="COMMAND"
+>print command = lp -d%p -s %s; rm %s</B
+></P
+><P
+>For printing = CUPS : If SAMBA is compiled against
+ libcups, then <A
+HREF="#PRINTING"
+>printcap = cups</A
+>
+ uses the CUPS API to
+ submit jobs, etc. Otherwise it maps to the System V
+ commands with the -oraw option for printing, i.e. it
+ uses <B
+CLASS="COMMAND"
+>lp -c -d%p -oraw; rm %s</B
+>.
+ With <B
+CLASS="COMMAND"
+>printing = cups</B
+>,
+ and if SAMBA is compiled against libcups, any manually
+ set print command will be ignored.</P
+><P
+>Example: <B
+CLASS="COMMAND"
+>print command = /usr/local/samba/bin/myprintscript
+ %p %s</B
+></P
+></DD
+><DT
+><A
+NAME="PRINTOK"
+></A
+>print ok (S)</DT
+><DD
+><P
+>Synonym for <A
+HREF="#PRINTABLE"
+> <TT
+CLASS="PARAMETER"
+><I
+>printable</I
+></TT
+></A
+>.</P
+></DD
+><DT
+><A
+NAME="PRINTABLE"
+></A
+>printable (S)</DT
+><DD
+><P
+>If this parameter is <TT
+CLASS="CONSTANT"
+>yes</TT
+>, then
+ clients may open, write to and submit spool files on the directory
+ specified for the service. </P
+><P
+>Note that a printable service will ALWAYS allow writing
+ to the service path (user privileges permitting) via the spooling
+ of print data. The <A
+HREF="#READONLY"
+><TT
+CLASS="PARAMETER"
+><I
+>read only
+ </I
+></TT
+></A
+> parameter controls only non-printing access to
+ the resource.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>printable = no</B
+></P
+></DD
+><DT
+><A
+NAME="PRINTCAP"
+></A
+>printcap (G)</DT
+><DD
+><P
+>Synonym for <A
+HREF="#PRINTCAPNAME"
+><TT
+CLASS="PARAMETER"
+><I
+> printcap name</I
+></TT
+></A
+>.</P
+></DD
+><DT
+><A
+NAME="PRINTCAPNAME"
+></A
+>printcap name (G)</DT
+><DD
+><P
+>This parameter may be used to override the
+ compiled-in default printcap name used by the server (usually <TT
+CLASS="FILENAME"
+> /etc/printcap</TT
+>). See the discussion of the <A
+HREF="#AEN79"
+>[printers]</A
+> section above for reasons
+ why you might want to do this.</P
+><P
+>To use the CUPS printing interface set <B
+CLASS="COMMAND"
+>printcap name = cups
+ </B
+>. This should be supplemented by an addtional setting
+ <A
+HREF="#PRINTING"
+>printing = cups</A
+> in the [global]
+ section. <B
+CLASS="COMMAND"
+>printcap name = cups</B
+> will use the
+ "dummy" printcap created by CUPS, as specified in your CUPS
+ configuration file.
+ </P
+><P
+>On System V systems that use <B
+CLASS="COMMAND"
+>lpstat</B
+> to
+ list available printers you can use <B
+CLASS="COMMAND"
+>printcap name = lpstat
+ </B
+> to automatically obtain lists of available printers. This
+ is the default for systems that define SYSV at configure time in
+ Samba (this includes most System V based systems). If <TT
+CLASS="PARAMETER"
+><I
+> printcap name</I
+></TT
+> is set to <B
+CLASS="COMMAND"
+>lpstat</B
+> on
+ these systems then Samba will launch <B
+CLASS="COMMAND"
+>lpstat -v</B
+> and
+ attempt to parse the output to obtain a printer list.</P
+><P
+>A minimal printcap file would look something like this:</P
+><P
+><TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="90%"
+><TR
+><TD
+><PRE
+CLASS="PROGRAMLISTING"
+> print1|My Printer 1
+ print2|My Printer 2
+ print3|My Printer 3
+ print4|My Printer 4
+ print5|My Printer 5
+ </PRE
+></TD
+></TR
+></TABLE
+></P
+><P
+>where the '|' separates aliases of a printer. The fact
+ that the second alias has a space in it gives a hint to Samba
+ that it's a comment.</P
+><P
+><I
+CLASS="EMPHASIS"
+>NOTE</I
+>: Under AIX the default printcap
+ name is <TT
+CLASS="FILENAME"
+>/etc/qconfig</TT
+>. Samba will assume the
+ file is in AIX <TT
+CLASS="FILENAME"
+>qconfig</TT
+> format if the string
+ <TT
+CLASS="FILENAME"
+>qconfig</TT
+> appears in the printcap filename.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>printcap name = /etc/printcap</B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>printcap name = /etc/myprintcap</B
+></P
+></DD
+><DT
+><A
+NAME="PRINTERADMIN"
+></A
+>printer admin (S)</DT
+><DD
+><P
+>This is a list of users that can do anything to
+ printers via the remote administration interfaces offered by MS-RPC
+ (usually using a NT workstation). Note that the root user always
+ has admin rights.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>printer admin = &#60;empty string&#62;</B
+>
+ </P
+><P
+>Example: <B
+CLASS="COMMAND"
+>printer admin = admin, @staff</B
+></P
+></DD
+><DT
+><A
+NAME="PRINTERDRIVER"
+></A
+>printer driver (S)</DT
+><DD
+><P
+><I
+CLASS="EMPHASIS"
+>Note :</I
+>This is a deprecated
+ parameter and will be removed in the next major release
+ following version 2.2. Please see the instructions in
+ the <A
+HREF="printer_driver2.html"
+TARGET="_top"
+>Samba 2.2. Printing
+ HOWTO</A
+> 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 Windows NT
+ then you can use this to automate the setup of printers on your
+ system.</P
+><P
+>You need to set this parameter to the exact string (case
+ 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 <A
+HREF="#PRINTERDRIVER"
+><TT
+CLASS="PARAMETER"
+><I
+> printer driver</I
+></TT
+></A
+> option set and the client will
+ give you a list of printer drivers. The appropriate strings are
+ shown in a scroll box after you have chosen the printer manufacturer.</P
+><P
+>See also <A
+HREF="#PRINTERDRIVERFILE"
+><TT
+CLASS="PARAMETER"
+><I
+>printer
+ driver file</I
+></TT
+></A
+>.</P
+><P
+>Example: <B
+CLASS="COMMAND"
+>printer driver = HP LaserJet 4L</B
+></P
+></DD
+><DT
+><A
+NAME="PRINTERDRIVERFILE"
+></A
+>printer driver file (G)</DT
+><DD
+><P
+><I
+CLASS="EMPHASIS"
+>Note :</I
+>This is a deprecated
+ parameter and will be removed in the next major release
+ following version 2.2. Please see the instructions in
+ the <A
+HREF="printer_driver2.html"
+TARGET="_top"
+>Samba 2.2. Printing
+ HOWTO</A
+> for more information
+ on the new method of loading printer drivers onto a Samba server.
+ </P
+><P
+>This parameter tells Samba where the printer driver
+ definition file, used when serving drivers to Windows 95 clients, is
+ to be found. If this is not set, the default is :</P
+><P
+><TT
+CLASS="FILENAME"
+><TT
+CLASS="REPLACEABLE"
+><I
+>SAMBA_INSTALL_DIRECTORY</I
+></TT
+>
+ /lib/printers.def</TT
+></P
+><P
+>This file is created from Windows 95 <TT
+CLASS="FILENAME"
+>msprint.inf
+ </TT
+> files found on the Windows 95 client system. For more
+ details on setting up serving of printer drivers to Windows 95
+ clients, see the outdated documentation file in the <TT
+CLASS="FILENAME"
+>docs/</TT
+>
+ directory, <TT
+CLASS="FILENAME"
+>PRINTER_DRIVER.txt</TT
+>.</P
+><P
+>See also <A
+HREF="#PRINTERDRIVERLOCATION"
+><TT
+CLASS="PARAMETER"
+><I
+> printer driver location</I
+></TT
+></A
+>.</P
+><P
+>Default: <I
+CLASS="EMPHASIS"
+>None (set in compile).</I
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>printer driver file =
+ /usr/local/samba/printers/drivers.def</B
+></P
+></DD
+><DT
+><A
+NAME="PRINTERDRIVERLOCATION"
+></A
+>printer driver location (S)</DT
+><DD
+><P
+><I
+CLASS="EMPHASIS"
+>Note :</I
+>This is a deprecated
+ parameter and will be removed in the next major release
+ following version 2.2. Please see the instructions in
+ the <A
+HREF="printer_driver2.html"
+TARGET="_top"
+>Samba 2.2. Printing
+ HOWTO</A
+> for more information
+ on the new method of loading printer drivers onto a Samba server.
+ </P
+><P
+>This parameter tells clients of a particular printer
+ share where to find the printer driver files for the automatic
+ installation of drivers for Windows 95 machines. If Samba is set up
+ to serve printer drivers to Windows 95 machines, this should be set to</P
+><P
+><B
+CLASS="COMMAND"
+>\\MACHINE\PRINTER$</B
+></P
+><P
+>Where MACHINE is the NetBIOS name of your Samba server,
+ and PRINTER$ is a share you set up for serving printer driver
+ files. For more details on setting this up see the outdated documentation
+ file in the <TT
+CLASS="FILENAME"
+>docs/</TT
+> directory, <TT
+CLASS="FILENAME"
+> PRINTER_DRIVER.txt</TT
+>.</P
+><P
+>See also <A
+HREF="#PRINTERDRIVERFILE"
+><TT
+CLASS="PARAMETER"
+><I
+> printer driver file</I
+></TT
+></A
+>.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>none</B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>printer driver location = \\MACHINE\PRINTER$
+ </B
+></P
+></DD
+><DT
+><A
+NAME="PRINTERNAME"
+></A
+>printer name (S)</DT
+><DD
+><P
+>This parameter specifies the name of the printer
+ to which print jobs spooled through a printable service will be sent.</P
+><P
+>If specified in the [global] section, the printer
+ name given will be used for any printable service that does
+ not have its own printer name specified.</P
+><P
+>Default: <I
+CLASS="EMPHASIS"
+>none (but may be <TT
+CLASS="CONSTANT"
+>lp</TT
+>
+ on many systems)</I
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>printer name = laserwriter</B
+></P
+></DD
+><DT
+><A
+NAME="PRINTER"
+></A
+>printer (S)</DT
+><DD
+><P
+>Synonym for <A
+HREF="#PRINTERNAME"
+><TT
+CLASS="PARAMETER"
+><I
+> printer name</I
+></TT
+></A
+>.</P
+></DD
+><DT
+><A
+NAME="PRINTING"
+></A
+>printing (S)</DT
+><DD
+><P
+>This parameters controls how printer status
+ information is interpreted on your system. It also affects the
+ default values for the <TT
+CLASS="PARAMETER"
+><I
+>print command</I
+></TT
+>,
+ <TT
+CLASS="PARAMETER"
+><I
+>lpq command</I
+></TT
+>, <TT
+CLASS="PARAMETER"
+><I
+>lppause command
+ </I
+></TT
+>, <TT
+CLASS="PARAMETER"
+><I
+>lpresume command</I
+></TT
+>, and
+ <TT
+CLASS="PARAMETER"
+><I
+>lprm command</I
+></TT
+> if specified in the
+ [global] section.</P
+><P
+>Currently nine printing styles are supported. They are
+ <TT
+CLASS="CONSTANT"
+>BSD</TT
+>, <TT
+CLASS="CONSTANT"
+>AIX</TT
+>,
+ <TT
+CLASS="CONSTANT"
+>LPRNG</TT
+>, <TT
+CLASS="CONSTANT"
+>PLP</TT
+>,
+ <TT
+CLASS="CONSTANT"
+>SYSV</TT
+>, <TT
+CLASS="CONSTANT"
+>HPUX</TT
+>,
+ <TT
+CLASS="CONSTANT"
+>QNX</TT
+>, <TT
+CLASS="CONSTANT"
+>SOFTQ</TT
+>,
+ and <TT
+CLASS="CONSTANT"
+>CUPS</TT
+>.</P
+><P
+>To see what the defaults are for the other print
+ commands when using the various options use the <A
+HREF="testparm.1.html"
+TARGET="_top"
+>testparm(1)</A
+> program.</P
+><P
+>This option can be set on a per printer basis</P
+><P
+>See also the discussion in the <A
+HREF="#AEN79"
+> [printers]</A
+> section.</P
+></DD
+><DT
+><A
+NAME="PRIVATEDIR"
+></A
+>private dir (G)</DT
+><DD
+><P
+>This parameters defines the directory
+ smbd will use for storing such files as <TT
+CLASS="FILENAME"
+>smbpasswd</TT
+>
+ and <TT
+CLASS="FILENAME"
+>secrets.tdb</TT
+>.
+ </P
+><P
+>Default :<B
+CLASS="COMMAND"
+>private dir = ${prefix}/private</B
+></P
+></DD
+><DT
+><A
+NAME="PROTOCOL"
+></A
+>protocol (G)</DT
+><DD
+><P
+>Synonym for <A
+HREF="#MAXPROTOCOL"
+> <TT
+CLASS="PARAMETER"
+><I
+>max protocol</I
+></TT
+></A
+>.</P
+></DD
+><DT
+><A
+NAME="PUBLIC"
+></A
+>public (S)</DT
+><DD
+><P
+>Synonym for <A
+HREF="#GUESTOK"
+><TT
+CLASS="PARAMETER"
+><I
+>guest
+ ok</I
+></TT
+></A
+>.</P
+></DD
+><DT
+><A
+NAME="QUEUEPAUSECOMMAND"
+></A
+>queuepause command (S)</DT
+><DD
+><P
+>This parameter specifies the command to be
+ executed on the server host in order to pause the printer queue.</P
+><P
+>This command should be a program or script which takes
+ a printer name as its only parameter and stops the printer queue,
+ such that no longer jobs are submitted to the printer.</P
+><P
+>This command is not supported by Windows for Workgroups,
+ but can be issued from the Printers window under Windows 95
+ and NT.</P
+><P
+>If a <TT
+CLASS="PARAMETER"
+><I
+>%p</I
+></TT
+> is given then the printer name
+ is put in its place. Otherwise it is placed at the end of the command.
+ </P
+><P
+>Note that it is good practice to include the absolute
+ path in the command as the PATH may not be available to the
+ server.</P
+><P
+>Default: <I
+CLASS="EMPHASIS"
+>depends on the setting of <TT
+CLASS="PARAMETER"
+><I
+>printing
+ </I
+></TT
+></I
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>queuepause command = disable %p</B
+></P
+></DD
+><DT
+><A
+NAME="QUEUERESUMECOMMAND"
+></A
+>queueresume command (S)</DT
+><DD
+><P
+>This parameter specifies the command to be
+ executed on the server host in order to resume the printer queue. It
+ is the command to undo the behavior that is caused by the
+ previous parameter (<A
+HREF="#QUEUEPAUSECOMMAND"
+><TT
+CLASS="PARAMETER"
+><I
+> queuepause command</I
+></TT
+></A
+>).</P
+><P
+>This command should be a program or script which takes
+ a printer name as its only parameter and resumes the printer queue,
+ such that queued jobs are resubmitted to the printer.</P
+><P
+>This command is not supported by Windows for Workgroups,
+ but can be issued from the Printers window under Windows 95
+ and NT.</P
+><P
+>If a <TT
+CLASS="PARAMETER"
+><I
+>%p</I
+></TT
+> is given then the printer name
+ is put in its place. Otherwise it is placed at the end of the
+ command.</P
+><P
+>Note that it is good practice to include the absolute
+ path in the command as the PATH may not be available to the
+ server.</P
+><P
+>Default: <I
+CLASS="EMPHASIS"
+>depends on the setting of <A
+HREF="#PRINTING"
+><TT
+CLASS="PARAMETER"
+><I
+>printing</I
+></TT
+></A
+></I
+>
+ </P
+><P
+>Example: <B
+CLASS="COMMAND"
+>queuepause command = enable %p
+ </B
+></P
+></DD
+><DT
+><A
+NAME="READBMPX"
+></A
+>read bmpx (G)</DT
+><DD
+><P
+>This boolean parameter controls whether <A
+HREF="smbd.8.html"
+TARGET="_top"
+>smbd(8)</A
+> will support the "Read
+ Block Multiplex" SMB. This is now rarely used and defaults to
+ <TT
+CLASS="CONSTANT"
+>no</TT
+>. You should never need to set this
+ parameter.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>read bmpx = no</B
+></P
+></DD
+><DT
+><A
+NAME="READLIST"
+></A
+>read list (S)</DT
+><DD
+><P
+>This is a list of users that are given read-only
+ access to a service. If the connecting user is in this list then
+ they will not be given write access, no matter what the <A
+HREF="#READONLY"
+><TT
+CLASS="PARAMETER"
+><I
+>read only</I
+></TT
+></A
+>
+ option is set to. The list can include group names using the
+ syntax described in the <A
+HREF="#INVALIDUSERS"
+><TT
+CLASS="PARAMETER"
+><I
+> invalid users</I
+></TT
+></A
+> parameter.</P
+><P
+>See also the <A
+HREF="#WRITELIST"
+><TT
+CLASS="PARAMETER"
+><I
+> write list</I
+></TT
+></A
+> parameter and the <A
+HREF="#INVALIDUSERS"
+><TT
+CLASS="PARAMETER"
+><I
+>invalid users</I
+></TT
+>
+ </A
+> parameter.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>read list = &#60;empty string&#62;</B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>read list = mary, @students</B
+></P
+></DD
+><DT
+><A
+NAME="READONLY"
+></A
+>read only (S)</DT
+><DD
+><P
+>An inverted synonym is <A
+HREF="#WRITEABLE"
+> <TT
+CLASS="PARAMETER"
+><I
+>writeable</I
+></TT
+></A
+>.</P
+><P
+>If this parameter is <TT
+CLASS="CONSTANT"
+>yes</TT
+>, then users
+ of a service may not create or modify files in the service's
+ directory.</P
+><P
+>Note that a printable service (<B
+CLASS="COMMAND"
+>printable = yes</B
+>)
+ will <I
+CLASS="EMPHASIS"
+>ALWAYS</I
+> allow writing to the directory
+ (user privileges permitting), but only via spooling operations.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>read only = yes</B
+></P
+></DD
+><DT
+><A
+NAME="READRAW"
+></A
+>read raw (G)</DT
+><DD
+><P
+>This parameter controls whether or not the server
+ will support the raw read SMB requests when transferring data
+ to clients.</P
+><P
+>If enabled, raw reads allow reads of 65535 bytes in
+ one packet. This typically provides a major performance benefit.
+ </P
+><P
+>However, some clients either negotiate the allowable
+ block size incorrectly or are incapable of supporting larger block
+ sizes, and for these clients you may need to disable raw reads.</P
+><P
+>In general this parameter should be viewed as a system tuning
+ tool and left severely alone. See also <A
+HREF="#WRITERAW"
+> <TT
+CLASS="PARAMETER"
+><I
+>write raw</I
+></TT
+></A
+>.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>read raw = yes</B
+></P
+></DD
+><DT
+><A
+NAME="READSIZE"
+></A
+>read size (G)</DT
+><DD
+><P
+>The option <TT
+CLASS="PARAMETER"
+><I
+>read size</I
+></TT
+>
+ affects the overlap of disk reads/writes with network reads/writes.
+ If the amount of data being transferred in several of the SMB
+ commands (currently SMBwrite, SMBwriteX and SMBreadbraw) is larger
+ than this value then the server begins writing the data before it
+ has received the whole packet from the network, or in the case of
+ SMBreadbraw, it begins writing to the network before all the data
+ has been read from disk.</P
+><P
+>This overlapping works best when the speeds of disk and
+ network access are similar, having very little effect when the
+ speed of one is much greater than the other.</P
+><P
+>The default value is 16384, but very little experimentation
+ has been done yet to determine the optimal value, and it is likely
+ that the best value will vary greatly between systems anyway.
+ A value over 65536 is pointless and will cause you to allocate
+ memory unnecessarily.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>read size = 16384</B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>read size = 8192</B
+></P
+></DD
+><DT
+><A
+NAME="REALM"
+></A
+>realm (G)</DT
+><DD
+><P
+> This option specifies the kerberos realm to use. The realm is
+ used as the ADS equivalent of the NT4<B
+CLASS="COMMAND"
+>domain</B
+>. It
+ is usually set to the DNS name of the kerberos server.
+ </P
+><P
+>Default: <B
+CLASS="COMMAND"
+>realm = </B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>realm = mysambabox.mycompany.com</B
+></P
+></DD
+><DT
+><A
+NAME="REMOTEANNOUNCE"
+></A
+>remote announce (G)</DT
+><DD
+><P
+>This option allows you to setup <A
+HREF="nmbd.8.html"
+TARGET="_top"
+>nmbd(8)</A
+> to periodically announce itself
+ to arbitrary IP addresses with an arbitrary workgroup name.</P
+><P
+>This is useful if you want your Samba server to appear
+ in a remote workgroup for which the normal browse propagation
+ rules don't work. The remote workgroup can be anywhere that you
+ can send IP packets to.</P
+><P
+>For example:</P
+><P
+><B
+CLASS="COMMAND"
+>remote announce = 192.168.2.255/SERVERS
+ 192.168.4.255/STAFF</B
+></P
+><P
+>the above line would cause <B
+CLASS="COMMAND"
+>nmbd</B
+> to announce itself
+ to the two given IP addresses using the given workgroup names.
+ If you leave out the workgroup name then the one given in
+ the <A
+HREF="#WORKGROUP"
+><TT
+CLASS="PARAMETER"
+><I
+>workgroup</I
+></TT
+></A
+>
+ parameter is used instead.</P
+><P
+>The IP addresses you choose would normally be the broadcast
+ addresses of the remote networks, but can also be the IP addresses
+ of known browse masters if your network config is that stable.</P
+><P
+>See the documentation file <TT
+CLASS="FILENAME"
+>BROWSING.txt</TT
+>
+ in the <TT
+CLASS="FILENAME"
+>docs/</TT
+> directory.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>remote announce = &#60;empty string&#62;
+ </B
+></P
+></DD
+><DT
+><A
+NAME="REMOTEBROWSESYNC"
+></A
+>remote browse sync (G)</DT
+><DD
+><P
+>This option allows you to setup <A
+HREF="nmbd.8.html"
+TARGET="_top"
+>nmbd(8)</A
+> to periodically request
+ synchronization of browse lists with the master browser of a Samba
+ server that is on a remote segment. This option will allow you to
+ gain browse lists for multiple workgroups across routed networks. This
+ is done in a manner that does not work with any non-Samba servers.</P
+><P
+>This is useful if you want your Samba server and all local
+ clients to appear in a remote workgroup for which the normal browse
+ propagation rules don't work. The remote workgroup can be anywhere
+ that you can send IP packets to.</P
+><P
+>For example:</P
+><P
+><B
+CLASS="COMMAND"
+>remote browse sync = 192.168.2.255 192.168.4.255
+ </B
+></P
+><P
+>the above line would cause <B
+CLASS="COMMAND"
+>nmbd</B
+> to request
+ the master browser on the specified subnets or addresses to
+ synchronize their browse lists with the local server.</P
+><P
+>The IP addresses you choose would normally be the broadcast
+ addresses of the remote networks, but can also be the IP addresses
+ of known browse masters if your network config is that stable. If
+ a machine IP address is given Samba makes NO attempt to validate
+ that the remote machine is available, is listening, nor that it
+ is in fact the browse master on its segment.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>remote browse sync = &#60;empty string&#62;
+ </B
+></P
+></DD
+><DT
+><A
+NAME="RESTRICTANONYMOUS"
+></A
+>restrict anonymous (G)</DT
+><DD
+><P
+>This is a integer parameter, and
+ mirrors as much as possible the functinality the
+ <TT
+CLASS="CONSTANT"
+>RestrictAnonymous</TT
+>
+ registry key does on NT/Win2k. </P
+><P
+>Default: <B
+CLASS="COMMAND"
+>restrict anonymous = 0</B
+></P
+></DD
+><DT
+><A
+NAME="ROOT"
+></A
+>root (G)</DT
+><DD
+><P
+>Synonym for <A
+HREF="#ROOTDIRECTORY"
+> <TT
+CLASS="PARAMETER"
+><I
+>root directory"</I
+></TT
+></A
+>.</P
+></DD
+><DT
+><A
+NAME="ROOTDIR"
+></A
+>root dir (G)</DT
+><DD
+><P
+>Synonym for <A
+HREF="#ROOTDIRECTORY"
+> <TT
+CLASS="PARAMETER"
+><I
+>root directory"</I
+></TT
+></A
+>.</P
+></DD
+><DT
+><A
+NAME="ROOTDIRECTORY"
+></A
+>root directory (G)</DT
+><DD
+><P
+>The server will <B
+CLASS="COMMAND"
+>chroot()</B
+> (i.e.
+ Change its root directory) to this directory on startup. This is
+ not strictly necessary for secure operation. Even without it the
+ server will deny access to files not in one of the service entries.
+ It may also check for, and deny access to, soft links to other
+ parts of the filesystem, or attempts to use ".." in file names
+ to access other directories (depending on the setting of the <A
+HREF="#WIDELINKS"
+><TT
+CLASS="PARAMETER"
+><I
+>wide links</I
+></TT
+></A
+>
+ parameter).</P
+><P
+>Adding a <TT
+CLASS="PARAMETER"
+><I
+>root directory</I
+></TT
+> entry other
+ than "/" adds an extra level of security, but at a price. It
+ absolutely ensures that no access is given to files not in the
+ sub-tree specified in the <TT
+CLASS="PARAMETER"
+><I
+>root directory</I
+></TT
+>
+ option, <I
+CLASS="EMPHASIS"
+>including</I
+> some files needed for
+ complete operation of the server. To maintain full operability
+ of the server you will need to mirror some system files
+ into the <TT
+CLASS="PARAMETER"
+><I
+>root directory</I
+></TT
+> tree. In particular
+ you will need to mirror <TT
+CLASS="FILENAME"
+>/etc/passwd</TT
+> (or a
+ subset of it), and any binaries or configuration files needed for
+ printing (if required). The set of files that must be mirrored is
+ operating system dependent.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>root directory = /</B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>root directory = /homes/smb</B
+></P
+></DD
+><DT
+><A
+NAME="ROOTPOSTEXEC"
+></A
+>root postexec (S)</DT
+><DD
+><P
+>This is the same as the <TT
+CLASS="PARAMETER"
+><I
+>postexec</I
+></TT
+>
+ parameter except that the command is run as root. This
+ is useful for unmounting filesystems
+ (such as CDROMs) after a connection is closed.</P
+><P
+>See also <A
+HREF="#POSTEXEC"
+><TT
+CLASS="PARAMETER"
+><I
+> postexec</I
+></TT
+></A
+>.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>root postexec = &#60;empty string&#62;
+ </B
+></P
+></DD
+><DT
+><A
+NAME="ROOTPREEXEC"
+></A
+>root preexec (S)</DT
+><DD
+><P
+>This is the same as the <TT
+CLASS="PARAMETER"
+><I
+>preexec</I
+></TT
+>
+ parameter except that the command is run as root. This
+ is useful for mounting filesystems (such as CDROMs) when a
+ connection is opened.</P
+><P
+>See also <A
+HREF="#PREEXEC"
+><TT
+CLASS="PARAMETER"
+><I
+> preexec</I
+></TT
+></A
+> and <A
+HREF="#PREEXECCLOSE"
+> <TT
+CLASS="PARAMETER"
+><I
+>preexec close</I
+></TT
+></A
+>.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>root preexec = &#60;empty string&#62;
+ </B
+></P
+></DD
+><DT
+><A
+NAME="ROOTPREEXECCLOSE"
+></A
+>root preexec close (S)</DT
+><DD
+><P
+>This is the same as the <TT
+CLASS="PARAMETER"
+><I
+>preexec close
+ </I
+></TT
+> parameter except that the command is run as root.</P
+><P
+>See also <A
+HREF="#PREEXEC"
+><TT
+CLASS="PARAMETER"
+><I
+> preexec</I
+></TT
+></A
+> and <A
+HREF="#PREEXECCLOSE"
+> <TT
+CLASS="PARAMETER"
+><I
+>preexec close</I
+></TT
+></A
+>.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>root preexec close = no</B
+></P
+></DD
+><DT
+><A
+NAME="SECURITY"
+></A
+>security (G)</DT
+><DD
+><P
+>This option affects how clients respond to
+ Samba and is one of the most important settings in the <TT
+CLASS="FILENAME"
+> smb.conf</TT
+> file.</P
+><P
+>The option sets the "security mode bit" in replies to
+ protocol negotiations with <A
+HREF="smbd.8.html"
+TARGET="_top"
+>smbd(8)
+ </A
+> to turn share level security on or off. Clients decide
+ based on this bit whether (and how) to transfer user and password
+ information to the server.</P
+><P
+>The default is <B
+CLASS="COMMAND"
+>security = user</B
+>, as this is
+ the most common setting needed when talking to Windows 98 and
+ Windows NT.</P
+><P
+>The alternatives are <B
+CLASS="COMMAND"
+>security = share</B
+>,
+ <B
+CLASS="COMMAND"
+>security = server</B
+> or <B
+CLASS="COMMAND"
+>security = domain
+ </B
+>.</P
+><P
+>In versions of Samba prior to 2.0.0, the default was
+ <B
+CLASS="COMMAND"
+>security = share</B
+> mainly because that was
+ the only option at one stage.</P
+><P
+>There is a bug in WfWg that has relevance to this
+ setting. When in user or server level security a WfWg client
+ will totally ignore the password you type in the "connect
+ drive" dialog box. This makes it very difficult (if not impossible)
+ to connect to a Samba service as anyone except the user that
+ you are logged into WfWg as.</P
+><P
+>If your PCs use usernames that are the same as their
+ usernames on the UNIX machine then you will want to use
+ <B
+CLASS="COMMAND"
+>security = user</B
+>. If you mostly use usernames
+ that don't exist on the UNIX box then use <B
+CLASS="COMMAND"
+>security =
+ share</B
+>.</P
+><P
+>You should also use <B
+CLASS="COMMAND"
+>security = share</B
+> if you
+ want to mainly setup shares without a password (guest shares). This
+ is commonly used for a shared printer server. It is more difficult
+ to setup guest shares with <B
+CLASS="COMMAND"
+>security = user</B
+>, see
+ the <A
+HREF="#MAPTOGUEST"
+><TT
+CLASS="PARAMETER"
+><I
+>map to guest</I
+></TT
+>
+ </A
+>parameter for details.</P
+><P
+>It is possible to use <B
+CLASS="COMMAND"
+>smbd</B
+> in a <I
+CLASS="EMPHASIS"
+> hybrid mode</I
+> where it is offers both user and share
+ level security under different <A
+HREF="#NETBIOSALIASES"
+> <TT
+CLASS="PARAMETER"
+><I
+>NetBIOS aliases</I
+></TT
+></A
+>. </P
+><P
+>The different settings will now be explained.</P
+><P
+><A
+NAME="SECURITYEQUALSSHARE"
+></A
+><I
+CLASS="EMPHASIS"
+>SECURITY = SHARE
+ </I
+></P
+><P
+>When clients connect to a share level security server they
+ need not log onto the server with a valid username and password before
+ attempting to connect to a shared resource (although modern clients
+ such as Windows 95/98 and Windows NT will send a logon request with
+ a username but no password when talking to a <B
+CLASS="COMMAND"
+>security = share
+ </B
+> server). Instead, the clients send authentication information
+ (passwords) on a per-share basis, at the time they attempt to connect
+ to that share.</P
+><P
+>Note that <B
+CLASS="COMMAND"
+>smbd</B
+> <I
+CLASS="EMPHASIS"
+>ALWAYS</I
+>
+ uses a valid UNIX user to act on behalf of the client, even in
+ <B
+CLASS="COMMAND"
+>security = share</B
+> level security.</P
+><P
+>As clients are not required to send a username to the server
+ in share level security, <B
+CLASS="COMMAND"
+>smbd</B
+> uses several
+ techniques to determine the correct UNIX user to use on behalf
+ of the client.</P
+><P
+>A list of possible UNIX usernames to match with the given
+ client password is constructed using the following methods :</P
+><P
+></P
+><UL
+><LI
+><P
+>If the <A
+HREF="#GUESTONLY"
+><TT
+CLASS="PARAMETER"
+><I
+>guest
+ only</I
+></TT
+></A
+> parameter is set, then all the other
+ stages are missed and only the <A
+HREF="#GUESTACCOUNT"
+> <TT
+CLASS="PARAMETER"
+><I
+>guest account</I
+></TT
+></A
+> username is checked.
+ </P
+></LI
+><LI
+><P
+>Is a username is sent with the share connection
+ request, then this username (after mapping - see <A
+HREF="#USERNAMEMAP"
+><TT
+CLASS="PARAMETER"
+><I
+>username map</I
+></TT
+></A
+>),
+ is added as a potential username.</P
+></LI
+><LI
+><P
+>If the client did a previous <I
+CLASS="EMPHASIS"
+>logon
+ </I
+> request (the SessionSetup SMB call) then the
+ username sent in this SMB will be added as a potential username.
+ </P
+></LI
+><LI
+><P
+>The name of the service the client requested is
+ added as a potential username.</P
+></LI
+><LI
+><P
+>The NetBIOS name of the client is added to
+ the list as a potential username.</P
+></LI
+><LI
+><P
+>Any users on the <A
+HREF="#USER"
+><TT
+CLASS="PARAMETER"
+><I
+> user</I
+></TT
+></A
+> list are added as potential usernames.
+ </P
+></LI
+></UL
+><P
+>If the <TT
+CLASS="PARAMETER"
+><I
+>guest only</I
+></TT
+> parameter is
+ not set, then this list is then tried with the supplied password.
+ The first user for whom the password matches will be used as the
+ UNIX user.</P
+><P
+>If the <TT
+CLASS="PARAMETER"
+><I
+>guest only</I
+></TT
+> parameter is
+ set, or no username can be determined then if the share is marked
+ as available to the <TT
+CLASS="PARAMETER"
+><I
+>guest account</I
+></TT
+>, then this
+ guest user will be used, otherwise access is denied.</P
+><P
+>Note that it can be <I
+CLASS="EMPHASIS"
+>very</I
+> confusing
+ in share-level security as to which UNIX username will eventually
+ be used in granting access.</P
+><P
+>See also the section <A
+HREF="#AEN238"
+> NOTE ABOUT USERNAME/PASSWORD VALIDATION</A
+>.</P
+><P
+><A
+NAME="SECURITYEQUALSUSER"
+></A
+><I
+CLASS="EMPHASIS"
+>SECURITY = USER
+ </I
+></P
+><P
+>This is the default security setting in Samba 2.2.
+ With user-level security a client must first "log-on" with a
+ valid username and password (which can be mapped using the <A
+HREF="#USERNAMEMAP"
+><TT
+CLASS="PARAMETER"
+><I
+>username map</I
+></TT
+></A
+>
+ parameter). Encrypted passwords (see the <A
+HREF="#ENCRYPTPASSWORDS"
+> <TT
+CLASS="PARAMETER"
+><I
+>encrypted passwords</I
+></TT
+></A
+> parameter) can also
+ be used in this security mode. Parameters such as <A
+HREF="#USER"
+> <TT
+CLASS="PARAMETER"
+><I
+>user</I
+></TT
+></A
+> and <A
+HREF="#GUESTONLY"
+> <TT
+CLASS="PARAMETER"
+><I
+>guest only</I
+></TT
+></A
+> if set are then applied and
+ may change the UNIX user to use on this connection, but only after
+ the user has been successfully authenticated.</P
+><P
+><I
+CLASS="EMPHASIS"
+>Note</I
+> that the name of the resource being
+ requested is <I
+CLASS="EMPHASIS"
+>not</I
+> sent to the server until after
+ the server has successfully authenticated the client. This is why
+ guest shares don't work in user level security without allowing
+ the server to automatically map unknown users into the <A
+HREF="#GUESTACCOUNT"
+><TT
+CLASS="PARAMETER"
+><I
+>guest account</I
+></TT
+></A
+>.
+ See the <A
+HREF="#MAPTOGUEST"
+><TT
+CLASS="PARAMETER"
+><I
+>map to guest</I
+></TT
+>
+ </A
+> parameter for details on doing this.</P
+><P
+>See also the section <A
+HREF="#AEN238"
+> NOTE ABOUT USERNAME/PASSWORD VALIDATION</A
+>.</P
+><P
+><A
+NAME="SECURITYEQUALSSERVER"
+></A
+><I
+CLASS="EMPHASIS"
+>SECURITY = SERVER
+ </I
+></P
+><P
+>In this mode Samba will try to validate the username/password
+ by passing it to another SMB server, such as an NT box. If this
+ fails it will revert to <B
+CLASS="COMMAND"
+>security = user</B
+>, but note
+ that if encrypted passwords have been negotiated then Samba cannot
+ revert back to checking the UNIX password file, it must have a valid
+ <TT
+CLASS="FILENAME"
+>smbpasswd</TT
+> file to check users against. See the
+ documentation file in the <TT
+CLASS="FILENAME"
+>docs/</TT
+> directory
+ <TT
+CLASS="FILENAME"
+>ENCRYPTION.txt</TT
+> for details on how to set this
+ up.</P
+><P
+><I
+CLASS="EMPHASIS"
+>Note</I
+> that from the client's point of
+ view <B
+CLASS="COMMAND"
+>security = server</B
+> is the same as <B
+CLASS="COMMAND"
+> security = user</B
+>. It only affects how the server deals
+ with the authentication, it does not in any way affect what the
+ client sees.</P
+><P
+><I
+CLASS="EMPHASIS"
+>Note</I
+> that the name of the resource being
+ requested is <I
+CLASS="EMPHASIS"
+>not</I
+> sent to the server until after
+ the server has successfully authenticated the client. This is why
+ guest shares don't work in user level security without allowing
+ the server to automatically map unknown users into the <A
+HREF="#GUESTACCOUNT"
+><TT
+CLASS="PARAMETER"
+><I
+>guest account</I
+></TT
+></A
+>.
+ See the <A
+HREF="#MAPTOGUEST"
+><TT
+CLASS="PARAMETER"
+><I
+>map to guest</I
+></TT
+>
+ </A
+> parameter for details on doing this.</P
+><P
+>See also the section <A
+HREF="#AEN238"
+> NOTE ABOUT USERNAME/PASSWORD VALIDATION</A
+>.</P
+><P
+>See also the <A
+HREF="#PASSWORDSERVER"
+><TT
+CLASS="PARAMETER"
+><I
+>password
+ server</I
+></TT
+></A
+> parameter and the <A
+HREF="#ENCRYPTPASSWORDS"
+><TT
+CLASS="PARAMETER"
+><I
+>encrypted passwords</I
+></TT
+>
+ </A
+> parameter.</P
+><P
+><A
+NAME="SECURITYEQUALSDOMAIN"
+></A
+><I
+CLASS="EMPHASIS"
+>SECURITY = DOMAIN
+ </I
+></P
+><P
+>This mode will only work correctly if <A
+HREF="smbpasswd.8.html"
+TARGET="_top"
+>smbpasswd(8)</A
+> has been used to add this
+ machine into a Windows NT Domain. It expects the <A
+HREF="#ENCRYPTPASSWORDS"
+><TT
+CLASS="PARAMETER"
+><I
+>encrypted passwords</I
+></TT
+>
+ </A
+> parameter to be set to <TT
+CLASS="CONSTANT"
+>yes</TT
+>. In this
+ mode Samba will try to validate the username/password by passing
+ it to a Windows NT Primary or Backup Domain Controller, in exactly
+ the same way that a Windows NT Server would do.</P
+><P
+><I
+CLASS="EMPHASIS"
+>Note</I
+> that a valid UNIX user must still
+ exist as well as the account on the Domain Controller to allow
+ Samba to have a valid UNIX account to map file access to.</P
+><P
+><I
+CLASS="EMPHASIS"
+>Note</I
+> that from the client's point
+ of view <B
+CLASS="COMMAND"
+>security = domain</B
+> is the same as <B
+CLASS="COMMAND"
+>security = user
+ </B
+>. It only affects how the server deals with the authentication,
+ it does not in any way affect what the client sees.</P
+><P
+><I
+CLASS="EMPHASIS"
+>Note</I
+> that the name of the resource being
+ requested is <I
+CLASS="EMPHASIS"
+>not</I
+> sent to the server until after
+ the server has successfully authenticated the client. This is why
+ guest shares don't work in user level security without allowing
+ the server to automatically map unknown users into the <A
+HREF="#GUESTACCOUNT"
+><TT
+CLASS="PARAMETER"
+><I
+>guest account</I
+></TT
+></A
+>.
+ See the <A
+HREF="#MAPTOGUEST"
+><TT
+CLASS="PARAMETER"
+><I
+>map to guest</I
+></TT
+>
+ </A
+> parameter for details on doing this.</P
+><P
+><I
+CLASS="EMPHASIS"
+>BUG:</I
+> There is currently a bug in the
+ implementation of <B
+CLASS="COMMAND"
+>security = domain</B
+> with respect
+ to multi-byte character set usernames. The communication with a
+ Domain Controller must be done in UNICODE and Samba currently
+ does not widen multi-byte user names to UNICODE correctly, thus
+ a multi-byte username will not be recognized correctly at the
+ Domain Controller. This issue will be addressed in a future release.</P
+><P
+>See also the section <A
+HREF="#AEN238"
+> NOTE ABOUT USERNAME/PASSWORD VALIDATION</A
+>.</P
+><P
+>See also the <A
+HREF="#PASSWORDSERVER"
+><TT
+CLASS="PARAMETER"
+><I
+>password
+ server</I
+></TT
+></A
+> parameter and the <A
+HREF="#ENCRYPTPASSWORDS"
+><TT
+CLASS="PARAMETER"
+><I
+>encrypted passwords</I
+></TT
+>
+ </A
+> parameter.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>security = USER</B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>security = DOMAIN</B
+></P
+></DD
+><DT
+><A
+NAME="SECURITYMASK"
+></A
+>security mask (S)</DT
+><DD
+><P
+>This parameter controls what UNIX permission
+ bits can be modified when a Windows NT client is manipulating
+ the UNIX permission on a file using the native NT security
+ dialog box.</P
+><P
+>This parameter is applied as a mask (AND'ed with) to
+ the changed permission bits, thus preventing any bits not in
+ this mask from being modified. Essentially, zero bits in this
+ mask may be treated as a set of bits the user is not allowed
+ to change.</P
+><P
+>If not set explicitly this parameter is 0777, allowing
+ a user to modify all the user/group/world permissions on a file.
+ </P
+><P
+><I
+CLASS="EMPHASIS"
+>Note</I
+> that users who can access the
+ Samba server through other means can easily bypass this
+ restriction, so it is primarily useful for standalone
+ "appliance" systems. Administrators of most normal systems will
+ probably want to leave it set to <TT
+CLASS="CONSTANT"
+>0777</TT
+>.</P
+><P
+>See also the <A
+HREF="#FORCEDIRECTORYSECURITYMODE"
+> <TT
+CLASS="PARAMETER"
+><I
+>force directory security mode</I
+></TT
+></A
+>,
+ <A
+HREF="#DIRECTORYSECURITYMASK"
+><TT
+CLASS="PARAMETER"
+><I
+>directory
+ security mask</I
+></TT
+></A
+>, <A
+HREF="#FORCESECURITYMODE"
+> <TT
+CLASS="PARAMETER"
+><I
+>force security mode</I
+></TT
+></A
+> parameters.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>security mask = 0777</B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>security mask = 0770</B
+></P
+></DD
+><DT
+><A
+NAME="SERVERSTRING"
+></A
+>server string (G)</DT
+><DD
+><P
+>This controls what string will show up in the
+ printer comment box in print manager and next to the IPC connection
+ in <B
+CLASS="COMMAND"
+>net view</B
+>. It can be any string that you wish
+ to show to your users.</P
+><P
+>It also sets what will appear in browse lists next
+ to the machine name.</P
+><P
+>A <TT
+CLASS="PARAMETER"
+><I
+>%v</I
+></TT
+> will be replaced with the Samba
+ version number.</P
+><P
+>A <TT
+CLASS="PARAMETER"
+><I
+>%h</I
+></TT
+> will be replaced with the
+ hostname.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>server string = Samba %v</B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>server string = University of GNUs Samba
+ Server</B
+></P
+></DD
+><DT
+><A
+NAME="SETDIRECTORY"
+></A
+>set directory (S)</DT
+><DD
+><P
+>If <B
+CLASS="COMMAND"
+>set directory = no</B
+>, then
+ users of the service may not use the setdir command to change
+ directory.</P
+><P
+>The <B
+CLASS="COMMAND"
+>setdir</B
+> command is only implemented
+ in the Digital Pathworks client. See the Pathworks documentation
+ for details.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>set directory = no</B
+></P
+></DD
+><DT
+><A
+NAME="SHAREMODES"
+></A
+>share modes (S)</DT
+><DD
+><P
+>This enables or disables the honoring of
+ the <TT
+CLASS="PARAMETER"
+><I
+>share modes</I
+></TT
+> during a file open. These
+ modes are used by clients to gain exclusive read or write access
+ to a file.</P
+><P
+>These open modes are not directly supported by UNIX, so
+ they are simulated using shared memory, or lock files if your
+ UNIX doesn't support shared memory (almost all do).</P
+><P
+>The share modes that are enabled by this option are
+ <TT
+CLASS="CONSTANT"
+>DENY_DOS</TT
+>, <TT
+CLASS="CONSTANT"
+>DENY_ALL</TT
+>,
+ <TT
+CLASS="CONSTANT"
+>DENY_READ</TT
+>, <TT
+CLASS="CONSTANT"
+>DENY_WRITE</TT
+>,
+ <TT
+CLASS="CONSTANT"
+>DENY_NONE</TT
+> and <TT
+CLASS="CONSTANT"
+>DENY_FCB</TT
+>.
+ </P
+><P
+>This option gives full share compatibility and enabled
+ by default.</P
+><P
+>You should <I
+CLASS="EMPHASIS"
+>NEVER</I
+> turn this parameter
+ off as many Windows applications will break if you do so.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>share modes = yes</B
+></P
+></DD
+><DT
+><A
+NAME="SHORTPRESERVECASE"
+></A
+>short preserve case (S)</DT
+><DD
+><P
+>This boolean parameter controls if new files
+ which conform to 8.3 syntax, that is all in upper case and of
+ suitable length, are created upper case, or if they are forced
+ to be the <A
+HREF="#DEFAULTCASE"
+><TT
+CLASS="PARAMETER"
+><I
+>default case
+ </I
+></TT
+></A
+>. This option can be use with <A
+HREF="#PRESERVECASE"
+><B
+CLASS="COMMAND"
+>preserve case = yes</B
+>
+ </A
+> to permit long filenames to retain their case, while short
+ names are lowered. </P
+><P
+>See the section on <A
+HREF="#AEN205"
+> NAME MANGLING</A
+>.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>short preserve case = yes</B
+></P
+></DD
+><DT
+><A
+NAME="SHOWADDPRINTERWIZARD"
+></A
+>show add printer wizard (G)</DT
+><DD
+><P
+>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 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 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"
+><I
+>printer admin</I
+></TT
+> group), the OpenPrinterEx()
+ call fails and the client makes another open call with a request for
+ a lower privilege level. This should succeed, however the APW
+ icon will not be displayed.</P
+><P
+>Disabling the <TT
+CLASS="PARAMETER"
+><I
+>show add printer wizard</I
+></TT
+>
+ parameter will always cause the OpenPrinterEx() on the server
+ to fail. Thus the APW icon will never be displayed. <I
+CLASS="EMPHASIS"
+> Note :</I
+>This does not prevent the same user from having
+ administrative privilege on an individual printer.</P
+><P
+>See also <A
+HREF="#ADDPRINTERCOMMAND"
+><TT
+CLASS="PARAMETER"
+><I
+>addprinter
+ command</I
+></TT
+></A
+>, <A
+HREF="#DELETEPRINTERCOMMAND"
+> <TT
+CLASS="PARAMETER"
+><I
+>deleteprinter command</I
+></TT
+></A
+>, <A
+HREF="#PRINTERADMIN"
+><TT
+CLASS="PARAMETER"
+><I
+>printer admin</I
+></TT
+></A
+></P
+><P
+>Default :<B
+CLASS="COMMAND"
+>show add printer wizard = yes</B
+></P
+></DD
+><DT
+><A
+NAME="SHUTDOWNSCRIPT"
+></A
+>shutdown script (G)</DT
+><DD
+><P
+><I
+CLASS="EMPHASIS"
+>This parameter only exists in the HEAD cvs branch</I
+>
+ This a full path name to a script called by
+ <A
+HREF="smbd.8.html"
+TARGET="_top"
+><B
+CLASS="COMMAND"
+>smbd(8)</B
+></A
+> that
+ should start a shutdown procedure.</P
+><P
+>This command will be run as the user connected to the
+ server.</P
+><P
+>%m %t %r %f parameters are expanded</P
+><P
+><TT
+CLASS="PARAMETER"
+><I
+>%m</I
+></TT
+> will be substituted with the
+ shutdown message sent to the server.</P
+><P
+><TT
+CLASS="PARAMETER"
+><I
+>%t</I
+></TT
+> will be substituted with the
+ number of seconds to wait before effectively starting the
+ shutdown procedure.</P
+><P
+><TT
+CLASS="PARAMETER"
+><I
+>%r</I
+></TT
+> will be substituted with the
+ switch <I
+CLASS="EMPHASIS"
+>-r</I
+>. It means reboot after shutdown
+ for NT.
+ </P
+><P
+><TT
+CLASS="PARAMETER"
+><I
+>%f</I
+></TT
+> will be substituted with the
+ switch <I
+CLASS="EMPHASIS"
+>-f</I
+>. It means force the shutdown
+ even if applications do not respond for NT.</P
+><P
+>Default: <I
+CLASS="EMPHASIS"
+>None</I
+>.</P
+><P
+>Example: <B
+CLASS="COMMAND"
+>abort shutdown script = /usr/local/samba/sbin/shutdown %m %t %r %f</B
+></P
+><P
+>Shutdown script example:
+ <TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="90%"
+><TR
+><TD
+><PRE
+CLASS="PROGRAMLISTING"
+> #!/bin/bash
-$time=0
-let &quot;time/60&quot;
-let &quot;time++&quot;
+ $time=0
+ let "time/60"
+ let "time++"
-/sbin/shutdown $3 $4 +$time $1 &amp;
-</pre><p>
-Shutdown does not return so we need to launch it in background.
-</p><p>See also <a href="#ABORTSHUTDOWNSCRIPT">
- <i><tt>abort shutdown script</tt></i></a>.</p></dd><dt><span class="term"><a name="SMBPASSWDFILE"></a>smb passwd file (G)</span></dt><dd><p>This option sets the path to the encrypted smbpasswd file. By
- default the path to the smbpasswd file is compiled into Samba.</p><p>Default: <b>smb passwd file = ${prefix}/private/smbpasswd</b></p><p>Example: <b>smb passwd file = /etc/samba/smbpasswd</b></p></dd><dt><span class="term"><a name="SMBPORTS"></a>smb ports (G)</span></dt><dd><p>Specifies which ports the server should listen on for SMB traffic.</p><p>Default: <b>smb ports = 445 139</b></p></dd><dt><span class="term"><a name="SOCKETADDRESS"></a>socket address (G)</span></dt><dd><p>This option allows you to control what
- address Samba will listen for connections on. This is used to
- support multiple virtual interfaces on the one server, each
- with a different configuration.</p><p>By default Samba will accept connections on any
- address.</p><p>Example: <b>socket address = 192.168.2.20</b></p></dd><dt><span class="term"><a name="SOCKETOPTIONS"></a>socket options (G)</span></dt><dd><p>This option allows you to set socket options
- to be used when talking with the client.</p><p>Socket options are controls on the networking layer
- of the operating systems which allow the connection to be
- tuned.</p><p>This option will typically be used to tune your Samba server
- for optimal performance for your local network. There is no way
- that Samba can know what the optimal parameters are for your net,
- so you must experiment and choose them yourself. We strongly
- suggest you read the appropriate documentation for your operating
- system first (perhaps <b>man
- setsockopt</b> will help).</p><p>You may find that on some systems Samba will say
- &quot;Unknown socket option&quot; when you supply an option. This means you
- either incorrectly typed it or you need to add an include file
- to includes.h for your OS. If the latter is the case please
- send the patch to <a href="mailto:samba-technical@samba.org" target="_top">
- samba-technical@samba.org</a>.</p><p>Any of the supported socket options may be combined
- in any way you like, as long as your OS allows it.</p><p>This is the list of socket options currently settable
- using this option:</p><div class="itemizedlist"><ul type="disc"><li><p>SO_KEEPALIVE</p></li><li><p>SO_REUSEADDR</p></li><li><p>SO_BROADCAST</p></li><li><p>TCP_NODELAY</p></li><li><p>IPTOS_LOWDELAY</p></li><li><p>IPTOS_THROUGHPUT</p></li><li><p>SO_SNDBUF *</p></li><li><p>SO_RCVBUF *</p></li><li><p>SO_SNDLOWAT *</p></li><li><p>SO_RCVLOWAT *</p></li></ul></div><p>Those marked with a <span class="emphasis"><em>'*'</em></span> take an integer
- argument. The others can optionally take a 1 or 0 argument to enable
- or disable the option, by default they will be enabled if you
- don't specify 1 or 0.</p><p>To specify an argument use the syntax SOME_OPTION = VALUE
- for example <b>SO_SNDBUF = 8192</b>. Note that you must
- not have any spaces before or after the = sign.</p><p>If you are on a local network then a sensible option
- might be:</p><p><b>socket options = IPTOS_LOWDELAY</b></p><p>If you have a local network then you could try:</p><p><b>socket options = IPTOS_LOWDELAY TCP_NODELAY</b></p><p>If you are on a wide area network then perhaps try
- setting IPTOS_THROUGHPUT. </p><p>Note that several of the options may cause your Samba
- server to fail completely. Use these options with caution!</p><p>Default: <b>socket options = TCP_NODELAY</b></p><p>Example: <b>socket options = IPTOS_LOWDELAY</b></p></dd><dt><span class="term"><a name="SOURCEENVIRONMENT"></a>source environment (G)</span></dt><dd><p>This parameter causes Samba to set environment
- variables as per the content of the file named.</p><p>If the value of this parameter starts with a &quot;|&quot; character
- then Samba will treat that value as a pipe command to open and
- will set the environment variables from the output of the pipe.</p><p>The contents of the file or the output of the pipe should
- be formatted as the output of the standard Unix <b>env(1)</b> command. This is of the form:</p><p>Example environment entry:</p><p><b>SAMBA_NETBIOS_NAME = myhostname</b></p><p>Default: <span class="emphasis"><em>No default value</em></span></p><p>Examples: <b>source environment = |/etc/smb.conf.sh</b></p><p>Example: <b>source environment =
- /usr/local/smb_env_vars</b></p></dd><dt><span class="term"><a name="STATCACHESIZE"></a>stat cache size (G)</span></dt><dd><p>This parameter determines the number of
- entries in the <i><tt>stat cache</tt></i>. You should
- never need to change this parameter.</p><p>Default: <b>stat cache size = 50</b></p></dd><dt><span class="term"><a name="STATCACHE"></a>stat cache (G)</span></dt><dd><p>This parameter determines if <a href="smbd.8.html">smbd(8)</a> will use a cache in order to
- speed up case insensitive name mappings. You should never need
- to change this parameter.</p><p>Default: <b>stat cache = yes</b></p></dd><dt><span class="term"><a name="STRICTALLOCATE"></a>strict allocate (S)</span></dt><dd><p>This is a boolean that controls the handling of
- disk space allocation in the server. When this is set to <tt>yes</tt>
- the server will change from UNIX behaviour of not committing real
- disk storage blocks when a file is extended to the Windows behaviour
- of actually forcing the disk system to allocate real storage blocks
- when a file is created or extended to be a given size. In UNIX
- terminology this means that Samba will stop creating sparse files.
- This can be slow on some systems.</p><p>When strict allocate is <tt>no</tt> the server does sparse
- disk block allocation when a file is extended.</p><p>Setting this to <tt>yes</tt> can help Samba return
- out of quota messages on systems that are restricting the disk quota
- of users.</p><p>Default: <b>strict allocate = no</b></p></dd><dt><span class="term"><a name="STRICTLOCKING"></a>strict locking (S)</span></dt><dd><p>This is a boolean that controls the handling of
- file locking in the server. When this is set to <tt>yes</tt>
- the server will check every read and write access for file locks, and
- deny access if locks exist. This can be slow on some systems.</p><p>When strict locking is <tt>no</tt> the server does file
- lock checks only when the client explicitly asks for them.</p><p>Well-behaved clients always ask for lock checks when it
- is important, so in the vast majority of cases <b>strict
- locking = no</b> is preferable.</p><p>Default: <b>strict locking = no</b></p></dd><dt><span class="term"><a name="STRICTSYNC"></a>strict sync (S)</span></dt><dd><p>Many Windows applications (including the Windows 98 explorer
- shell) seem to confuse flushing buffer contents to disk with doing
- a sync to disk. Under UNIX, a sync call forces the process to be
- suspended until the kernel has ensured that all outstanding data in
- kernel disk buffers has been safely stored onto stable storage.
- This is very slow and should only be done rarely. Setting this
- parameter to <tt>no</tt> (the default) means that
- <a href="smbd.8.html">smbd(8)</a> ignores the Windows
- applications requests for a sync call. There is only a possibility
- of losing data if the operating system itself that Samba is running
- on crashes, so there is little danger in this default setting. In
- addition, this fixes many performance problems that people have
- reported with the new Windows98 explorer shell file copies.</p><p>See also the <a href="#SYNCALWAYS"><i><tt>sync
- always</tt></i></a> parameter.</p><p>Default: <b>strict sync = no</b></p></dd><dt><span class="term"><a name="STRIPDOT"></a>strip dot (G)</span></dt><dd><p>This is a boolean that controls whether to
- strip trailing dots off UNIX filenames. This helps with some
- CDROMs that have filenames ending in a single dot.</p><p>Default: <b>strip dot = no</b></p></dd><dt><span class="term"><a name="SYNCALWAYS"></a>sync always (S)</span></dt><dd><p>This is a boolean parameter that controls
- whether writes will always be written to stable storage before
- the write call returns. If this is <tt>no</tt> then the server will be
- guided by the client's request in each write call (clients can
- set a bit indicating that a particular write should be synchronous).
- If this is <tt>yes</tt> then every write will be followed by a <b>fsync()
- </b> call to ensure the data is written to disk. Note that
- the <i><tt>strict sync</tt></i> parameter must be set to
- <tt>yes</tt> in order for this parameter to have
- any affect.</p><p>See also the <a href="#STRICTSYNC"><i><tt>strict
- sync</tt></i></a> parameter.</p><p>Default: <b>sync always = no</b></p></dd><dt><span class="term"><a name="SYSLOGONLY"></a>syslog only (G)</span></dt><dd><p>If this parameter is set then Samba debug
- messages are logged into the system syslog only, and not to
- the debug log files.</p><p>Default: <b>syslog only = no</b></p></dd><dt><span class="term"><a name="SYSLOG"></a>syslog (G)</span></dt><dd><p>This parameter maps how Samba debug messages
- are logged onto the system syslog logging levels. Samba debug
- level zero maps onto syslog <tt>LOG_ERR</tt>, debug
- level one maps onto <tt>LOG_WARNING</tt>, debug level
- two maps onto <tt>LOG_NOTICE</tt>, debug level three
- maps onto LOG_INFO. All higher levels are mapped to <tt>
- LOG_DEBUG</tt>.</p><p>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>Default: <b>syslog = 1</b></p></dd><dt><span class="term"><a name="TEMPLATEHOMEDIR"></a>template homedir (G)</span></dt><dd><p>When filling out the user information for a Windows NT
- user, the <a href="winbindd.8.html">winbindd(8)</a> daemon uses this
- parameter to fill in the home directory for that user. If the
- string <i><tt>%D</tt></i> is present it
- is substituted with the user's Windows NT domain name. If the
- string <i><tt>%U</tt></i> is present it
- is substituted with the user's Windows NT user name.</p><p>Default: <b>template homedir = /home/%D/%U</b></p></dd><dt><span class="term"><a name="TEMPLATESHELL"></a>template shell (G)</span></dt><dd><p>When filling out the user information for a Windows NT
- user, the <a href="winbindd.8.html">winbindd(8)</a> daemon uses this
- parameter to fill in the login shell for that user.</p><p>Default: <b>template shell = /bin/false</b></p></dd><dt><span class="term"><a name="TIMEOFFSET"></a>time offset (G)</span></dt><dd><p>This parameter is a setting in minutes to add
- to the normal GMT to local time conversion. This is useful if
- you are serving a lot of PCs that have incorrect daylight
- saving time handling.</p><p>Default: <b>time offset = 0</b></p><p>Example: <b>time offset = 60</b></p></dd><dt><span class="term"><a name="TIMESERVER"></a>time server (G)</span></dt><dd><p>This parameter determines if <a href="nmbd.8.html">nmbd(8)</a> advertises itself as a time server to Windows
- clients.</p><p>Default: <b>time server = no</b></p></dd><dt><span class="term"><a name="TIMESTAMPLOGS"></a>timestamp logs (G)</span></dt><dd><p>Synonym for <a href="#DEBUGTIMESTAMP"><i><tt>
- debug timestamp</tt></i></a>.</p></dd><dt><span class="term"><a name="TOTALPRINTJOBS"></a>total print jobs (G)</span></dt><dd><p>This parameter accepts an integer value which defines
- a limit on the maximum number of print jobs that will be accepted
- system wide at any given time. If a print job is submitted
- by a client which will exceed this number, then <a href="smbd.8.html">smbd(8)</a> will return an
- error indicating that no space is available on the server. The
- default value of 0 means that no such limit exists. This parameter
- can be used to prevent a server from exceeding its capacity and is
- designed as a printing throttle. See also <a href="#MAXPRINTJOBS">
- <i><tt>max print jobs</tt></i></a>.
- </p><p>Default: <b>total print jobs = 0</b></p><p>Example: <b>total print jobs = 5000</b></p></dd><dt><span class="term"><a name="UNICODE"></a>unicode (G)</span></dt><dd><p>Specifies whether Samba should try
- to use unicode on the wire by default. Note: This does NOT
- mean that samba will assume that the unix machine uses unicode!
- </p><p>Default: <b>unicode = yes</b></p></dd><dt><span class="term"><a name="UNIXCHARSET"></a>unix charset (G)</span></dt><dd><p>Specifies the charset the unix machine
- Samba runs on uses. Samba needs to know this in order to be able to
- convert text to the charsets other SMB clients use.
- </p><p>Default: <b>unix charset = UTF8</b></p><p>Example: <b>unix charset = ASCII</b></p></dd><dt><span class="term"><a name="UNIXEXTENSIONS"></a>unix extensions (G)</span></dt><dd><p>This boolean parameter controls whether Samba
- implments the CIFS UNIX extensions, as defined by HP.
- These extensions enable Samba to better serve UNIX CIFS clients
- by supporting features such as symbolic links, hard links, etc...
- These extensions require a similarly enabled client, and are of
- no current use to Windows clients.</p><p>Default: <b>unix extensions = no</b></p></dd><dt><span class="term"><a name="UNIXPASSWORDSYNC"></a>unix password sync (G)</span></dt><dd><p>This boolean parameter controls whether Samba
- attempts to synchronize the UNIX password with the SMB password
- when the encrypted SMB password in the smbpasswd file is changed.
- If this is set to <tt>yes</tt> the program specified in the <i><tt>passwd
- program</tt></i>parameter is called <span class="emphasis"><em>AS ROOT</em></span> -
- to allow the new UNIX password to be set without access to the
- old UNIX password (as the SMB password change code has no
- access to the old password cleartext, only the new).</p><p>See also <a href="#PASSWDPROGRAM"><i><tt>passwd
- program</tt></i></a>, <a href="#PASSWDCHAT"><i><tt>
- passwd chat</tt></i></a>.
- </p><p>Default: <b>unix password sync = no</b></p></dd><dt><span class="term"><a name="UPDATEENCRYPTED"></a>update encrypted (G)</span></dt><dd><p>This boolean parameter allows a user logging on with
- a plaintext password to have their encrypted (hashed) password in
- the smbpasswd file to be updated automatically as they log
- on. This option allows a site to migrate from plaintext
- password authentication (users authenticate with plaintext
- password over the wire, and are checked against a UNIX account
- database) to encrypted password authentication (the SMB
- challenge/response authentication mechanism) without forcing all
- users to re-enter their passwords via smbpasswd at the time the
- change is made. This is a convenience option to allow the change
- over to encrypted passwords to be made over a longer period.
- Once all users have encrypted representations of their passwords
- in the smbpasswd file this parameter should be set to
- <tt>no</tt>.</p><p>In order for this parameter to work correctly the <a href="#ENCRYPTPASSWORDS">
- <i><tt>encrypt passwords</tt></i></a> parameter must
- be set to <tt>no</tt> when this parameter is set to <tt>yes</tt>.</p><p>Note that even when this parameter is set a user
- authenticating to <b>smbd</b> must still enter a valid
- password in order to connect correctly, and to update their hashed
- (smbpasswd) passwords.</p><p>Default: <b>update encrypted = no</b></p></dd><dt><span class="term"><a name="USECLIENTDRIVER"></a>use client driver (S)</span></dt><dd><p>This parameter applies only to Windows NT/2000
- clients. It has no affect on Windows 95/98/ME clients. When
- serving a printer to Windows NT/2000 clients without first installing
- a valid printer driver on the Samba host, the client will be required
- to install a local printer driver. From this point on, the client
- will treat the print as a local printer and not a network printer
- connection. This is much the same behavior that will occur
- when <b>disable spoolss = yes</b>.
- </p><p>The differentiating factor is that under normal
- circumstances, the NT/2000 client will attempt to open the network
- printer using MS-RPC. The problem is that because the client
- considers the printer to be local, it will attempt to issue the
- OpenPrinterEx() call requesting access rights associated with the
- logged on user. If the user possesses local administator rights but
- not root privilegde on the Samba host (often the case), the
- OpenPrinterEx() call will fail. The result is that the client will
- now display an &quot;Access Denied; Unable to connect&quot; message
- in the printer queue window (even though jobs may successfully be
- printed). </p><p>If this parameter is enabled for a printer, then any attempt
- to open the printer with the PRINTER_ACCESS_ADMINISTER right is mapped
- to PRINTER_ACCESS_USE instead. Thus allowing the OpenPrinterEx()
- call to succeed. <span class="emphasis"><em>This parameter MUST not be able enabled
- on a print share which has valid print driver installed on the Samba
- server.</em></span></p><p>See also <a href="#DISABLESPOOLSS"><i><tt>disable spoolss</tt></i></a></p><p>Default: <b>use client driver = no</b></p></dd><dt><span class="term"><a name="USEMMAP"></a>use mmap (G)</span></dt><dd><p>This global parameter determines if the tdb internals of Samba can
- depend on mmap working correctly on the running system. Samba requires a coherent
- mmap/read-write system memory cache. Currently only HPUX does not have such a
- coherent cache, and so this parameter is set to <tt>no</tt> by
- default on HPUX. On all other systems this parameter should be left alone. This
- parameter is provided to help the Samba developers track down problems with
- the tdb internal code.
- </p><p>Default: <b>use mmap = yes</b></p></dd><dt><span class="term"><a name="USERNAMELEVEL"></a>username level (G)</span></dt><dd><p>This option helps Samba to try and 'guess' at
- the real UNIX username, as many DOS clients send an all-uppercase
- username. By default Samba tries all lowercase, followed by the
- username with the first letter capitalized, and fails if the
- username is not found on the UNIX machine.</p><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 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>AstrangeUser
- </tt>.</p><p>Default: <b>username level = 0</b></p><p>Example: <b>username level = 5</b></p></dd><dt><span class="term"><a name="USERNAMEMAP"></a>username map (G)</span></dt><dd><p>This option allows you to specify a file containing
- a mapping of usernames from the clients to the server. This can be
- used for several purposes. The most common is to map usernames
- that users use on DOS or Windows machines to those that the UNIX
- box uses. The other is to map multiple users to a single username
- so that they can more easily share files.</p><p>The map file is parsed line by line. Each line should
- contain a single UNIX username on the left then a '=' followed
- by a list of usernames on the right. The list of usernames on the
- right may contain names of the form @group in which case they
- will match any UNIX username in that group. The special client
- name '*' is a wildcard and matches any name. Each line of the
- map file may be up to 1023 characters long.</p><p>The file is processed on each line by taking the
- supplied username and comparing it with each username on the right
- hand side of the '=' signs. If the supplied name matches any of
- the names on the right hand side then it is replaced with the name
- on the left. Processing then continues with the next line.</p><p>If any line begins with a '#' or a ';' then it is ignored</p><p>If any line begins with an '!' then the processing
- will stop after that line if a mapping was done by the line.
- Otherwise mapping continues with every line being processed.
- Using '!' is most useful when you have a wildcard mapping line
- later in the file.</p><p>For example to map from the name <tt>admin</tt>
- or <tt>administrator</tt> to the UNIX name <tt>
- root</tt> you would use:</p><p><b>root = admin administrator</b></p><p>Or to map anyone in the UNIX group <tt>system</tt>
- to the UNIX name <tt>sys</tt> you would use:</p><p><b>sys = @system</b></p><p>You can have as many mappings as you like in a username map file.</p><p>If your system supports the NIS NETGROUP option then
- the netgroup database is checked before the <tt>/etc/group
- </tt> database for matching groups.</p><p>You can map Windows usernames that have spaces in them
- by using double quotes around the name. For example:</p><p><b>tridge = &quot;Andrew Tridgell&quot;</b></p><p>would map the windows username &quot;Andrew Tridgell&quot; to the
- unix username &quot;tridge&quot;.</p><p>The following example would map mary and fred to the
- unix user sys, and map the rest to guest. Note the use of the
- '!' to tell Samba to stop processing if it gets a match on
- that line.</p><pre class="programlisting">
-!sys = mary fred
-guest = *
-</pre><p>Note that the remapping is applied to all occurrences
- of usernames. Thus if you connect to \\server\fred and <tt>
- fred</tt> is remapped to <tt>mary</tt> then you
- will actually be connecting to \\server\mary and will need to
- supply a password suitable for <tt>mary</tt> not
- <tt>fred</tt>. The only exception to this is the
- username passed to the <a href="#PASSWORDSERVER"><i><tt>
- password server</tt></i></a> (if you have one). The password
- server will receive whatever username the client supplies without
- modification.</p><p>Also note that no reverse mapping is done. The main effect
- this has is with printing. Users who have been mapped may have
- trouble deleting print jobs as PrintManager under WfWg will think
- they don't own the print job.</p><p>Default: <span class="emphasis"><em>no username map</em></span></p><p>Example: <b>username map = /usr/local/samba/lib/users.map</b></p></dd><dt><span class="term"><a name="USERNAME"></a>username (S)</span></dt><dd><p>Multiple users may be specified in a comma-delimited
- list, in which case the supplied password will be tested against
- each username in turn (left to right).</p><p>The <i><tt>username</tt></i> line is needed only when
- the PC is unable to supply its own username. This is the case
- for the COREPLUS protocol or where your users have different WfWg
- usernames to UNIX usernames. In both these cases you may also be
- better using the \\server\share%user syntax instead.</p><p>The <i><tt>username</tt></i> line is not a great
- solution in many cases as it means Samba will try to validate
- the supplied password against each of the usernames in the
- <i><tt>username</tt></i> line in turn. This is slow and
- a bad idea for lots of users in case of duplicate passwords.
- You may get timeouts or security breaches using this parameter
- unwisely.</p><p>Samba relies on the underlying UNIX security. This
- parameter does not restrict who can login, it just offers hints
- to the Samba server as to what usernames might correspond to the
- supplied password. Users can login as whoever they please and
- they will be able to do no more damage than if they started a
- telnet session. The daemon runs as the user that they log in as,
- so they cannot do anything that user cannot do.</p><p>To restrict a service to a particular set of users you
- can use the <a href="#VALIDUSERS"><i><tt>valid users
- </tt></i></a> parameter.</p><p>If any of the usernames begin with a '@' then the name
- will be looked up first in the NIS netgroups list (if Samba
- is compiled with netgroup support), followed by a lookup in
- the UNIX groups database and will expand to a list of all users
- in the group of that name.</p><p>If any of the usernames begin with a '+' then the name
- will be looked up only in the UNIX groups database and will
- expand to a list of all users in the group of that name.</p><p>If any of the usernames begin with a '&amp;' then the name
- will be looked up only in the NIS netgroups database (if Samba
- is compiled with netgroup support) and will expand to a list
- of all users in the netgroup group of that name.</p><p>Note that searching though a groups database can take
- quite some time, and some clients may time out during the
- search.</p><p>See the section <a href="#VALIDATIONSECT" title="NOTE ABOUT USERNAME/PASSWORD VALIDATION">NOTE ABOUT
- USERNAME/PASSWORD VALIDATION</a> for more information on how
- this parameter determines access to the services.</p><p>Default: <b>The guest account if a guest service,
- else &lt;empty string&gt;.</b></p><p>Examples:<b>username = fred, mary, jack, jane,
- @users, @pcgroup</b></p></dd><dt><span class="term"><a name="USERS"></a>users (S)</span></dt><dd><p>Synonym for <a href="#USERNAME"><i><tt>
- username</tt></i></a>.</p></dd><dt><span class="term"><a name="USER"></a>user (S)</span></dt><dd><p>Synonym for <a href="#USERNAME"><i><tt>username</tt></i></a>.</p></dd><dt><span class="term"><a name="USESENDFILE"></a>use sendfile (S)</span></dt><dd><p>If this parameter is <tt>yes</tt>, and Samba
- was built with the --with-sendfile-support option, and the underlying operating
- system supports sendfile system call, then some SMB read calls (mainly ReadAndX
- and ReadRaw) will use the more efficient sendfile system call for files that
- are exclusively oplocked. This may make more efficient use of the system CPU's
- and cause Samba to be faster. This is off by default as it's effects are unknown
- as yet.</p><p>Default: <b>use sendfile = no</b></p></dd><dt><span class="term"><a name="USESPNEGO"></a>use spnego (G)</span></dt><dd><p> This variable controls controls whether samba will try
- to use Simple and Protected NEGOciation (as specified by rfc2478) with
- WindowsXP and Windows2000sp2 clients to agree upon an authentication mechanism.
- Unless further issues are discovered with our SPNEGO
- implementation, there is no reason this should ever be
- disabled.</p><p>Default: <span class="emphasis"><em>use spnego = yes</em></span></p></dd><dt><span class="term"><a name="UTMPDIRECTORY"></a>utmp directory (G)</span></dt><dd><p>This parameter is only available if Samba has
- been configured and compiled with the option <b>
- --with-utmp</b>. It specifies a directory pathname that is
- used to store the utmp or utmpx files (depending on the UNIX system) that
- record user connections to a Samba server. See also the <a href="#UTMP">
- <i><tt>utmp</tt></i></a> parameter. By default this is
- not set, meaning the system will use whatever utmp file the
- native system is set to use (usually
- <tt>/var/run/utmp</tt> on Linux).</p><p>Default: <span class="emphasis"><em>no utmp directory</em></span></p><p>Example: <b>utmp directory = /var/run/utmp</b></p></dd><dt><span class="term"><a name="UTMP"></a>utmp (G)</span></dt><dd><p>This boolean parameter is only available if
- Samba has been configured and compiled with the option <b>
- --with-utmp</b>. If set to <tt>yes</tt> then Samba will attempt
- to add utmp or utmpx records (depending on the UNIX system) whenever a
- connection is made to a Samba server. Sites may use this to record the
- user connecting to a Samba share.</p><p>Due to the requirements of the utmp record, we
- are required to create a unique identifier for the
- incoming user. Enabling this option creates an n^2
- algorithm to find this number. This may impede
- performance on large installations. </p><p>See also the <a href="#UTMPDIRECTORY"><i><tt>
- utmp directory</tt></i></a> parameter.</p><p>Default: <b>utmp = no</b></p></dd><dt><span class="term"><a name="VALIDUSERS"></a>valid users (S)</span></dt><dd><p>This is a list of users that should be allowed
- to login to this service. Names starting with '@', '+' and '&amp;'
- are interpreted using the same rules as described in the
- <i><tt>invalid users</tt></i> parameter.</p><p>If this is empty (the default) then any user can login.
- If a username is in both this list and the <i><tt>invalid
- users</tt></i> list then access is denied for that user.</p><p>The current servicename is substituted for <i><tt>%S
- </tt></i>. This is useful in the [homes] section.</p><p>See also <a href="#INVALIDUSERS"><i><tt>invalid users
- </tt></i></a></p><p>Default: <span class="emphasis"><em>No valid users list (anyone can login)
- </em></span></p><p>Example: <b>valid users = greg, @pcusers</b></p></dd><dt><span class="term"><a name="VETOFILES"></a>veto files (S)</span></dt><dd><p>This is a list of files and directories that
- are neither visible nor accessible. Each entry in the list must
- be separated by a '/', which allows spaces to be included
- in the entry. '*' and '?' can be used to specify multiple files
- or directories as in DOS wildcards.</p><p>Each entry must be a unix path, not a DOS path and
- must <span class="emphasis"><em>not</em></span> include the unix directory
- separator '/'.</p><p>Note that the <i><tt>case sensitive</tt></i> option
- is applicable in vetoing files.</p><p>One feature of the veto files parameter that it
- is important to be aware of is Samba's behaviour when
- trying to delete a directory. If a directory that is
- to be deleted contains nothing but veto files this
- deletion will <span class="emphasis"><em>fail</em></span> unless you also set
- the <i><tt>delete veto files</tt></i> parameter to
- <i><tt>yes</tt></i>.</p><p>Setting this parameter will affect the performance
- of Samba, as it will be forced to check all files and directories
- for a match as they are scanned.</p><p>See also <a href="#HIDEFILES"><i><tt>hide files
- </tt></i></a> and <a href="#CASESENSITIVE"><i><tt>
- case sensitive</tt></i></a>.</p><p>Default: <span class="emphasis"><em>No files or directories are vetoed.
- </em></span></p><p>Examples:
-</p><pre class="programlisting">
-; Veto any files containing the word Security,
+ /sbin/shutdown $3 $4 +$time $1 &#38;
+ </PRE
+></TD
+></TR
+></TABLE
+>
+ Shutdown does not return so we need to launch it in background.
+ </P
+><P
+>See also <A
+HREF="#ABORTSHUTDOWNSCRIPT"
+><TT
+CLASS="PARAMETER"
+><I
+>abort shutdown script</I
+></TT
+></A
+>.</P
+></DD
+><DT
+><A
+NAME="SMBPASSWDFILE"
+></A
+>smb passwd file (G)</DT
+><DD
+><P
+>This option sets the path to the encrypted
+ smbpasswd file. By default the path to the smbpasswd file
+ is compiled into Samba.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>smb passwd file = ${prefix}/private/smbpasswd
+ </B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>smb passwd file = /etc/samba/smbpasswd
+ </B
+></P
+></DD
+><DT
+><A
+NAME="SMBPORTS"
+></A
+>smb ports (G)</DT
+><DD
+><P
+>Specifies which ports the server should listen on
+ for SMB traffic.
+ </P
+><P
+>Default: <B
+CLASS="COMMAND"
+>smb ports = 445 139</B
+></P
+></DD
+><DT
+><A
+NAME="SOCKETADDRESS"
+></A
+>socket address (G)</DT
+><DD
+><P
+>This option allows you to control what
+ address Samba will listen for connections on. This is used to
+ support multiple virtual interfaces on the one server, each
+ with a different configuration.</P
+><P
+>By default Samba will accept connections on any
+ address.</P
+><P
+>Example: <B
+CLASS="COMMAND"
+>socket address = 192.168.2.20</B
+>
+ </P
+></DD
+><DT
+><A
+NAME="SOCKETOPTIONS"
+></A
+>socket options (G)</DT
+><DD
+><P
+>This option allows you to set socket options
+ to be used when talking with the client.</P
+><P
+>Socket options are controls on the networking layer
+ of the operating systems which allow the connection to be
+ tuned.</P
+><P
+>This option will typically be used to tune your Samba
+ server for optimal performance for your local network. There is
+ no way that Samba can know what the optimal parameters are for
+ your net, so you must experiment and choose them yourself. We
+ strongly suggest you read the appropriate documentation for your
+ operating system first (perhaps <B
+CLASS="COMMAND"
+>man setsockopt</B
+>
+ will help).</P
+><P
+>You may find that on some systems Samba will say
+ "Unknown socket option" when you supply an option. This means you
+ either incorrectly typed it or you need to add an include file
+ to includes.h for your OS. If the latter is the case please
+ send the patch to <A
+HREF="mailto:samba@samba.org"
+TARGET="_top"
+> samba@samba.org</A
+>.</P
+><P
+>Any of the supported socket options may be combined
+ in any way you like, as long as your OS allows it.</P
+><P
+>This is the list of socket options currently settable
+ using this option:</P
+><P
+></P
+><UL
+><LI
+><P
+>SO_KEEPALIVE</P
+></LI
+><LI
+><P
+>SO_REUSEADDR</P
+></LI
+><LI
+><P
+>SO_BROADCAST</P
+></LI
+><LI
+><P
+>TCP_NODELAY</P
+></LI
+><LI
+><P
+>IPTOS_LOWDELAY</P
+></LI
+><LI
+><P
+>IPTOS_THROUGHPUT</P
+></LI
+><LI
+><P
+>SO_SNDBUF *</P
+></LI
+><LI
+><P
+>SO_RCVBUF *</P
+></LI
+><LI
+><P
+>SO_SNDLOWAT *</P
+></LI
+><LI
+><P
+>SO_RCVLOWAT *</P
+></LI
+></UL
+><P
+>Those marked with a <I
+CLASS="EMPHASIS"
+>'*'</I
+> take an integer
+ argument. The others can optionally take a 1 or 0 argument to enable
+ or disable the option, by default they will be enabled if you
+ don't specify 1 or 0.</P
+><P
+>To specify an argument use the syntax SOME_OPTION = VALUE
+ for example <B
+CLASS="COMMAND"
+>SO_SNDBUF = 8192</B
+>. Note that you must
+ not have any spaces before or after the = sign.</P
+><P
+>If you are on a local network then a sensible option
+ might be</P
+><P
+><B
+CLASS="COMMAND"
+>socket options = IPTOS_LOWDELAY</B
+></P
+><P
+>If you have a local network then you could try:</P
+><P
+><B
+CLASS="COMMAND"
+>socket options = IPTOS_LOWDELAY TCP_NODELAY</B
+></P
+><P
+>If you are on a wide area network then perhaps try
+ setting IPTOS_THROUGHPUT. </P
+><P
+>Note that several of the options may cause your Samba
+ server to fail completely. Use these options with caution!</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>socket options = TCP_NODELAY</B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>socket options = IPTOS_LOWDELAY</B
+></P
+></DD
+><DT
+><A
+NAME="SOURCEENVIRONMENT"
+></A
+>source environment (G)</DT
+><DD
+><P
+>This parameter causes Samba to set environment
+ variables as per the content of the file named.</P
+><P
+>If the value of this parameter starts with a "|" character
+ then Samba will treat that value as a pipe command to open and
+ will set the environment variables from the output of the pipe.</P
+><P
+>The contents of the file or the output of the pipe should
+ be formatted as the output of the standard Unix <B
+CLASS="COMMAND"
+>env(1)
+ </B
+> command. This is of the form :</P
+><P
+>Example environment entry:</P
+><P
+><B
+CLASS="COMMAND"
+>SAMBA_NETBIOS_NAME = myhostname</B
+></P
+><P
+>Default: <I
+CLASS="EMPHASIS"
+>No default value</I
+></P
+><P
+>Examples: <B
+CLASS="COMMAND"
+>source environment = |/etc/smb.conf.sh
+ </B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>source environment =
+ /usr/local/smb_env_vars</B
+></P
+></DD
+><DT
+><A
+NAME="SPNEGO"
+></A
+>use spnego (G)</DT
+><DD
+><P
+> This variable controls controls whether samba will try to use Simple and Protected NEGOciation (as specified by rfc2478) with WindowsXP and Windows2000sp2 clients to agree upon an authentication mechanism. As of samba 3.0alpha it must be set to "no" for these clients to join a samba domain controller. It can be set to "yes" to allow samba to participate in an AD domain controlled by a Windows2000 domain controller.</P
+><P
+>Default: <I
+CLASS="EMPHASIS"
+>use spnego = yes</I
+></P
+></DD
+><DT
+><A
+NAME="STATCACHE"
+></A
+>stat cache (G)</DT
+><DD
+><P
+>This parameter determines if <A
+HREF="smbd.8.html"
+TARGET="_top"
+>smbd(8)</A
+> will use a cache in order to
+ speed up case insensitive name mappings. You should never need
+ to change this parameter.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>stat cache = yes</B
+></P
+></DD
+><DT
+><A
+NAME="STATCACHESIZE"
+></A
+>stat cache size (G)</DT
+><DD
+><P
+>This parameter determines the number of
+ entries in the <TT
+CLASS="PARAMETER"
+><I
+>stat cache</I
+></TT
+>. You should
+ never need to change this parameter.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>stat cache size = 50</B
+></P
+></DD
+><DT
+><A
+NAME="STRICTALLOCATE"
+></A
+>strict allocate (S)</DT
+><DD
+><P
+>This is a boolean that controls the handling of
+ disk space allocation in the server. When this is set to <TT
+CLASS="CONSTANT"
+>yes</TT
+>
+ the server will change from UNIX behaviour of not committing real
+ disk storage blocks when a file is extended to the Windows behaviour
+ of actually forcing the disk system to allocate real storage blocks
+ when a file is created or extended to be a given size. In UNIX
+ terminology this means that Samba will stop creating sparse files.
+ This can be slow on some systems.</P
+><P
+>When strict allocate is <TT
+CLASS="CONSTANT"
+>no</TT
+> the server does sparse
+ disk block allocation when a file is extended.</P
+><P
+>Setting this to <TT
+CLASS="CONSTANT"
+>yes</TT
+> can help Samba return
+ out of quota messages on systems that are restricting the disk quota
+ of users.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>strict allocate = no</B
+></P
+></DD
+><DT
+><A
+NAME="STRICTLOCKING"
+></A
+>strict locking (S)</DT
+><DD
+><P
+>This is a boolean that controls the handling of
+ file locking in the server. When this is set to <TT
+CLASS="CONSTANT"
+>yes</TT
+>
+ the server will check every read and write access for file locks, and
+ deny access if locks exist. This can be slow on some systems.</P
+><P
+>When strict locking is <TT
+CLASS="CONSTANT"
+>no</TT
+> the server does file
+ lock checks only when the client explicitly asks for them.</P
+><P
+>Well-behaved clients always ask for lock checks when it
+ is important, so in the vast majority of cases <B
+CLASS="COMMAND"
+>strict
+ locking = no</B
+> is preferable.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>strict locking = no</B
+></P
+></DD
+><DT
+><A
+NAME="STRICTSYNC"
+></A
+>strict sync (S)</DT
+><DD
+><P
+>Many Windows applications (including the Windows
+ 98 explorer shell) seem to confuse flushing buffer contents to
+ disk with doing a sync to disk. Under UNIX, a sync call forces
+ the process to be suspended until the kernel has ensured that
+ all outstanding data in kernel disk buffers has been safely stored
+ onto stable storage. This is very slow and should only be done
+ rarely. Setting this parameter to <TT
+CLASS="CONSTANT"
+>no</TT
+> (the
+ default) means that <A
+HREF="smbd.8.html"
+TARGET="_top"
+>smbd</A
+> ignores the Windows applications requests for
+ a sync call. There is only a possibility of losing data if the
+ operating system itself that Samba is running on crashes, so there is
+ little danger in this default setting. In addition, this fixes many
+ performance problems that people have reported with the new Windows98
+ explorer shell file copies.</P
+><P
+>See also the <A
+HREF="#SYNCALWAYS"
+><TT
+CLASS="PARAMETER"
+><I
+>sync
+ always&#62;</I
+></TT
+></A
+> parameter.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>strict sync = no</B
+></P
+></DD
+><DT
+><A
+NAME="STRIPDOT"
+></A
+>strip dot (G)</DT
+><DD
+><P
+>This is a boolean that controls whether to
+ strip trailing dots off UNIX filenames. This helps with some
+ CDROMs that have filenames ending in a single dot.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>strip dot = no</B
+></P
+></DD
+><DT
+><A
+NAME="SYNCALWAYS"
+></A
+>sync always (S)</DT
+><DD
+><P
+>This is a boolean parameter that controls
+ whether writes will always be written to stable storage before
+ the write call returns. If this is <TT
+CLASS="CONSTANT"
+>no</TT
+> then the server will be
+ guided by the client's request in each write call (clients can
+ set a bit indicating that a particular write should be synchronous).
+ If this is <TT
+CLASS="CONSTANT"
+>yes</TT
+> then every write will be followed by a <B
+CLASS="COMMAND"
+>fsync()
+ </B
+> call to ensure the data is written to disk. Note that
+ the <TT
+CLASS="PARAMETER"
+><I
+>strict sync</I
+></TT
+> parameter must be set to
+ <TT
+CLASS="CONSTANT"
+>yes</TT
+> in order for this parameter to have
+ any affect.</P
+><P
+>See also the <A
+HREF="#STRICTSYNC"
+><TT
+CLASS="PARAMETER"
+><I
+>strict
+ sync</I
+></TT
+></A
+> parameter.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>sync always = no</B
+></P
+></DD
+><DT
+><A
+NAME="SYSLOG"
+></A
+>syslog (G)</DT
+><DD
+><P
+>This parameter maps how Samba debug messages
+ are logged onto the system syslog logging levels. Samba debug
+ level zero maps onto syslog <TT
+CLASS="CONSTANT"
+>LOG_ERR</TT
+>, debug
+ level one maps onto <TT
+CLASS="CONSTANT"
+>LOG_WARNING</TT
+>, debug level
+ two maps onto <TT
+CLASS="CONSTANT"
+>LOG_NOTICE</TT
+>, debug level three
+ maps onto LOG_INFO. All higher levels are mapped to <TT
+CLASS="CONSTANT"
+> LOG_DEBUG</TT
+>.</P
+><P
+>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
+>Default: <B
+CLASS="COMMAND"
+>syslog = 1</B
+></P
+></DD
+><DT
+><A
+NAME="SYSLOGONLY"
+></A
+>syslog only (G)</DT
+><DD
+><P
+>If this parameter is set then Samba debug
+ messages are logged into the system syslog only, and not to
+ the debug log files.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>syslog only = no</B
+></P
+></DD
+><DT
+><A
+NAME="TEMPLATEHOMEDIR"
+></A
+>template homedir (G)</DT
+><DD
+><P
+>When filling out the user information for a Windows NT
+ user, the <A
+HREF="winbindd.8.html"
+TARGET="_top"
+>winbindd(8)</A
+> daemon
+ uses this parameter to fill in the home directory for that user.
+ If the string <TT
+CLASS="PARAMETER"
+><I
+>%D</I
+></TT
+> is present it is substituted
+ with the user's Windows NT domain name. If the string <TT
+CLASS="PARAMETER"
+><I
+>%U
+ </I
+></TT
+> is present it is substituted with the user's Windows
+ NT user name.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>template homedir = /home/%D/%U</B
+></P
+></DD
+><DT
+><A
+NAME="TEMPLATESHELL"
+></A
+>template shell (G)</DT
+><DD
+><P
+>When filling out the user information for a Windows NT
+ user, the <A
+HREF="winbindd.8.html"
+TARGET="_top"
+>winbindd(8)</A
+> daemon
+ uses this parameter to fill in the login shell for that user.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>template shell = /bin/false</B
+></P
+></DD
+><DT
+><A
+NAME="TIMEOFFSET"
+></A
+>time offset (G)</DT
+><DD
+><P
+>This parameter is a setting in minutes to add
+ to the normal GMT to local time conversion. This is useful if
+ you are serving a lot of PCs that have incorrect daylight
+ saving time handling.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>time offset = 0</B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>time offset = 60</B
+></P
+></DD
+><DT
+><A
+NAME="TIMESERVER"
+></A
+>time server (G)</DT
+><DD
+><P
+>This parameter determines if <A
+HREF="nmbd.8.html"
+TARGET="_top"
+>
+ nmbd(8)</A
+> advertises itself as a time server to Windows
+ clients.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>time server = no</B
+></P
+></DD
+><DT
+><A
+NAME="TIMESTAMPLOGS"
+></A
+>timestamp logs (G)</DT
+><DD
+><P
+>Synonym for <A
+HREF="#DEBUGTIMESTAMP"
+><TT
+CLASS="PARAMETER"
+><I
+> debug timestamp</I
+></TT
+></A
+>.</P
+></DD
+><DT
+><A
+NAME="TOTALPRINTJOBS"
+></A
+>total print jobs (G)</DT
+><DD
+><P
+>This parameter accepts an integer value which defines
+ a limit on the maximum number of print jobs that will be accepted
+ system wide at any given time. If a print job is submitted
+ by a client which will exceed this number, then <A
+HREF="smbd.8.html"
+TARGET="_top"
+>smbd</A
+> will return an
+ error indicating that no space is available on the server. The
+ default value of 0 means that no such limit exists. This parameter
+ can be used to prevent a server from exceeding its capacity and is
+ designed as a printing throttle. See also
+ <A
+HREF="#MAXPRINTJOBS"
+><TT
+CLASS="PARAMETER"
+><I
+>max print jobs</I
+></TT
+></A
+>.
+ </P
+><P
+>Default: <B
+CLASS="COMMAND"
+>total print jobs = 0</B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>total print jobs = 5000</B
+></P
+></DD
+><DT
+><A
+NAME="UNICODE"
+></A
+>unicode (G)</DT
+><DD
+><P
+>Specifies whether Samba should try
+ to use unicode on the wire by default. Note: This does NOT
+ mean that samba will assume that the unix machine uses unicode!
+ </P
+><P
+>Default: <B
+CLASS="COMMAND"
+>unicode = yes</B
+></P
+></DD
+><DT
+><A
+NAME="UNIXCHARSET"
+></A
+>unix charset (G)</DT
+><DD
+><P
+>Specifies the charset the unix machine
+ Samba runs on uses. Samba needs to know this in order to be able to
+ convert text to the charsets other SMB clients use.
+ </P
+><P
+>Default: <B
+CLASS="COMMAND"
+>unix charset = ASCII</B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>unix charset = UTF8</B
+></P
+></DD
+><DT
+><A
+NAME="UNIXEXTENSIONS"
+></A
+>unix extensions(G)</DT
+><DD
+><P
+>This boolean parameter controls whether Samba
+ implments the CIFS UNIX extensions, as defined by HP.
+ These extensions enable Samba to better serve UNIX CIFS clients
+ by supporting features such as symbolic links, hard links, etc...
+ These extensions require a similarly enabled client, and are of
+ no current use to Windows clients.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>unix extensions = no</B
+></P
+></DD
+><DT
+><A
+NAME="UNIXPASSWORDSYNC"
+></A
+>unix password sync (G)</DT
+><DD
+><P
+>This boolean parameter controls whether Samba
+ attempts to synchronize the UNIX password with the SMB password
+ when the encrypted SMB password in the smbpasswd file is changed.
+ If this is set to <TT
+CLASS="CONSTANT"
+>yes</TT
+> the program specified in the <TT
+CLASS="PARAMETER"
+><I
+>passwd
+ program</I
+></TT
+>parameter is called <I
+CLASS="EMPHASIS"
+>AS ROOT</I
+> -
+ to allow the new UNIX password to be set without access to the
+ old UNIX password (as the SMB password change code has no
+ access to the old password cleartext, only the new).</P
+><P
+>See also <A
+HREF="#PASSWDPROGRAM"
+><TT
+CLASS="PARAMETER"
+><I
+>passwd
+ program</I
+></TT
+></A
+>, <A
+HREF="#PASSWDCHAT"
+><TT
+CLASS="PARAMETER"
+><I
+> passwd chat</I
+></TT
+></A
+>.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>unix password sync = no</B
+></P
+></DD
+><DT
+><A
+NAME="UPDATEENCRYPTED"
+></A
+>update encrypted (G)</DT
+><DD
+><P
+>This boolean parameter allows a user logging
+ on with a plaintext password to have their encrypted (hashed)
+ password in the smbpasswd file to be updated automatically as
+ they log on. This option allows a site to migrate from plaintext
+ password authentication (users authenticate with plaintext
+ password over the wire, and are checked against a UNIX account
+ database) to encrypted password authentication (the SMB
+ challenge/response authentication mechanism) without forcing
+ all users to re-enter their passwords via smbpasswd at the time the
+ change is made. This is a convenience option to allow the change over
+ to encrypted passwords to be made over a longer period. Once all users
+ have encrypted representations of their passwords in the smbpasswd
+ file this parameter should be set to <TT
+CLASS="CONSTANT"
+>no</TT
+>.</P
+><P
+>In order for this parameter to work correctly the <A
+HREF="#ENCRYPTPASSWORDS"
+><TT
+CLASS="PARAMETER"
+><I
+>encrypt passwords</I
+></TT
+>
+ </A
+> parameter must be set to <TT
+CLASS="CONSTANT"
+>no</TT
+> when
+ this parameter is set to <TT
+CLASS="CONSTANT"
+>yes</TT
+>.</P
+><P
+>Note that even when this parameter is set a user
+ authenticating to <B
+CLASS="COMMAND"
+>smbd</B
+> must still enter a valid
+ password in order to connect correctly, and to update their hashed
+ (smbpasswd) passwords.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>update encrypted = no</B
+></P
+></DD
+><DT
+><A
+NAME="USECLIENTDRIVER"
+></A
+>use client driver (S)</DT
+><DD
+><P
+>This parameter applies only to Windows NT/2000
+ clients. It has no affect on Windows 95/98/ME clients. When
+ serving a printer to Windows NT/2000 clients without first installing
+ a valid printer driver on the Samba host, the client will be required
+ to install a local printer driver. From this point on, the client
+ will treat the print as a local printer and not a network printer
+ connection. This is much the same behavior that will occur
+ when <B
+CLASS="COMMAND"
+>disable spoolss = yes</B
+>. </P
+><P
+>The differentiating
+ factor is that under normal circumstances, the NT/2000 client will
+ attempt to open the network printer using MS-RPC. The problem is that
+ because the client considers the printer to be local, it will attempt
+ to issue the OpenPrinterEx() call requesting access rights associated
+ with the logged on user. If the user possesses local administator rights
+ but not root privilegde on the Samba host (often the case), the OpenPrinterEx()
+ call will fail. The result is that the client will now display an "Access
+ Denied; Unable to connect" message in the printer queue window (even though
+ jobs may successfully be printed). </P
+><P
+>If this parameter is enabled for a printer, then any attempt
+ to open the printer with the PRINTER_ACCESS_ADMINISTER right is mapped
+ to PRINTER_ACCESS_USE instead. Thus allowing the OpenPrinterEx()
+ call to succeed. <I
+CLASS="EMPHASIS"
+>This parameter MUST not be able enabled
+ on a print share which has valid print driver installed on the Samba
+ server.</I
+></P
+><P
+>See also <A
+HREF="#DISABLESPOOLSS"
+>disable spoolss</A
+>
+ </P
+><P
+>Default: <B
+CLASS="COMMAND"
+>use client driver = no</B
+></P
+></DD
+><DT
+><A
+NAME="USEMMAP"
+></A
+>use mmap (G)</DT
+><DD
+><P
+>This global parameter determines if the tdb internals of Samba can
+ depend on mmap working correctly on the running system. Samba requires a coherent
+ mmap/read-write system memory cache. Currently only HPUX does not have such a
+ coherent cache, and so this parameter is set to <TT
+CLASS="CONSTANT"
+>no</TT
+> by
+ default on HPUX. On all other systems this parameter should be left alone. This
+ parameter is provided to help the Samba developers track down problems with
+ the tdb internal code.
+ </P
+><P
+>Default: <B
+CLASS="COMMAND"
+>use mmap = yes</B
+></P
+></DD
+><DT
+><A
+NAME="USERHOSTS"
+></A
+>use rhosts (G)</DT
+><DD
+><P
+>If this global parameter is <TT
+CLASS="CONSTANT"
+>yes</TT
+>, it specifies
+ that the UNIX user's <TT
+CLASS="FILENAME"
+>.rhosts</TT
+> file in their home directory
+ will be read to find the names of hosts and users who will be allowed
+ access without specifying a password.</P
+><P
+><I
+CLASS="EMPHASIS"
+>NOTE:</I
+> The use of <TT
+CLASS="PARAMETER"
+><I
+>use rhosts
+ </I
+></TT
+> can be a major security hole. This is because you are
+ trusting the PC to supply the correct username. It is very easy to
+ get a PC to supply a false username. I recommend that the <TT
+CLASS="PARAMETER"
+><I
+> use rhosts</I
+></TT
+> option be only used if you really know what
+ you are doing.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>use rhosts = no</B
+></P
+></DD
+><DT
+><A
+NAME="USER"
+></A
+>user (S)</DT
+><DD
+><P
+>Synonym for <A
+HREF="#USERNAME"
+><TT
+CLASS="PARAMETER"
+><I
+> username</I
+></TT
+></A
+>.</P
+></DD
+><DT
+><A
+NAME="USERS"
+></A
+>users (S)</DT
+><DD
+><P
+>Synonym for <A
+HREF="#USERNAME"
+><TT
+CLASS="PARAMETER"
+><I
+> username</I
+></TT
+></A
+>.</P
+></DD
+><DT
+><A
+NAME="USERNAME"
+></A
+>username (S)</DT
+><DD
+><P
+>Multiple users may be specified in a comma-delimited
+ list, in which case the supplied password will be tested against
+ each username in turn (left to right).</P
+><P
+>The <TT
+CLASS="PARAMETER"
+><I
+>username</I
+></TT
+> line is needed only when
+ the PC is unable to supply its own username. This is the case
+ for the COREPLUS protocol or where your users have different WfWg
+ usernames to UNIX usernames. In both these cases you may also be
+ better using the \\server\share%user syntax instead.</P
+><P
+>The <TT
+CLASS="PARAMETER"
+><I
+>username</I
+></TT
+> line is not a great
+ solution in many cases as it means Samba will try to validate
+ the supplied password against each of the usernames in the
+ <TT
+CLASS="PARAMETER"
+><I
+>username</I
+></TT
+> line in turn. This is slow and
+ a bad idea for lots of users in case of duplicate passwords.
+ You may get timeouts or security breaches using this parameter
+ unwisely.</P
+><P
+>Samba relies on the underlying UNIX security. This
+ parameter does not restrict who can login, it just offers hints
+ to the Samba server as to what usernames might correspond to the
+ supplied password. Users can login as whoever they please and
+ they will be able to do no more damage than if they started a
+ telnet session. The daemon runs as the user that they log in as,
+ so they cannot do anything that user cannot do.</P
+><P
+>To restrict a service to a particular set of users you
+ can use the <A
+HREF="#VALIDUSERS"
+><TT
+CLASS="PARAMETER"
+><I
+>valid users
+ </I
+></TT
+></A
+> parameter.</P
+><P
+>If any of the usernames begin with a '@' then the name
+ will be looked up first in the NIS netgroups list (if Samba
+ is compiled with netgroup support), followed by a lookup in
+ the UNIX groups database and will expand to a list of all users
+ in the group of that name.</P
+><P
+>If any of the usernames begin with a '+' then the name
+ will be looked up only in the UNIX groups database and will
+ expand to a list of all users in the group of that name.</P
+><P
+>If any of the usernames begin with a '&#38;'then the name
+ will be looked up only in the NIS netgroups database (if Samba
+ is compiled with netgroup support) and will expand to a list
+ of all users in the netgroup group of that name.</P
+><P
+>Note that searching though a groups database can take
+ quite some time, and some clients may time out during the
+ search.</P
+><P
+>See the section <A
+HREF="#AEN238"
+>NOTE ABOUT
+ USERNAME/PASSWORD VALIDATION</A
+> for more information on how
+ this parameter determines access to the services.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>The guest account if a guest service,
+ else &#60;empty string&#62;.</B
+></P
+><P
+>Examples:<B
+CLASS="COMMAND"
+>username = fred, mary, jack, jane,
+ @users, @pcgroup</B
+></P
+></DD
+><DT
+><A
+NAME="USERNAMELEVEL"
+></A
+>username level (G)</DT
+><DD
+><P
+>This option helps Samba to try and 'guess' at
+ the real UNIX username, as many DOS clients send an all-uppercase
+ username. By default Samba tries all lowercase, followed by the
+ username with the first letter capitalized, and fails if the
+ username is not found on the UNIX machine.</P
+><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 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
+CLASS="CONSTANT"
+>AstrangeUser
+ </TT
+>.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>username level = 0</B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>username level = 5</B
+></P
+></DD
+><DT
+><A
+NAME="USERNAMEMAP"
+></A
+>username map (G)</DT
+><DD
+><P
+>This option allows you to specify a file containing
+ a mapping of usernames from the clients to the server. This can be
+ used for several purposes. The most common is to map usernames
+ that users use on DOS or Windows machines to those that the UNIX
+ box uses. The other is to map multiple users to a single username
+ so that they can more easily share files.</P
+><P
+>The map file is parsed line by line. Each line should
+ contain a single UNIX username on the left then a '=' followed
+ by a list of usernames on the right. The list of usernames on the
+ right may contain names of the form @group in which case they
+ will match any UNIX username in that group. The special client
+ name '*' is a wildcard and matches any name. Each line of the
+ map file may be up to 1023 characters long.</P
+><P
+>The file is processed on each line by taking the
+ supplied username and comparing it with each username on the right
+ hand side of the '=' signs. If the supplied name matches any of
+ the names on the right hand side then it is replaced with the name
+ on the left. Processing then continues with the next line.</P
+><P
+>If any line begins with a '#' or a ';' then it is
+ ignored</P
+><P
+>If any line begins with an '!' then the processing
+ will stop after that line if a mapping was done by the line.
+ Otherwise mapping continues with every line being processed.
+ Using '!' is most useful when you have a wildcard mapping line
+ later in the file.</P
+><P
+>For example to map from the name <TT
+CLASS="CONSTANT"
+>admin</TT
+>
+ or <TT
+CLASS="CONSTANT"
+>administrator</TT
+> to the UNIX name <TT
+CLASS="CONSTANT"
+> root</TT
+> you would use:</P
+><P
+><B
+CLASS="COMMAND"
+>root = admin administrator</B
+></P
+><P
+>Or to map anyone in the UNIX group <TT
+CLASS="CONSTANT"
+>system</TT
+>
+ to the UNIX name <TT
+CLASS="CONSTANT"
+>sys</TT
+> you would use:</P
+><P
+><B
+CLASS="COMMAND"
+>sys = @system</B
+></P
+><P
+>You can have as many mappings as you like in a username
+ map file.</P
+><P
+>If your system supports the NIS NETGROUP option then
+ the netgroup database is checked before the <TT
+CLASS="FILENAME"
+>/etc/group
+ </TT
+> database for matching groups.</P
+><P
+>You can map Windows usernames that have spaces in them
+ by using double quotes around the name. For example:</P
+><P
+><B
+CLASS="COMMAND"
+>tridge = "Andrew Tridgell"</B
+></P
+><P
+>would map the windows username "Andrew Tridgell" to the
+ unix username "tridge".</P
+><P
+>The following example would map mary and fred to the
+ unix user sys, and map the rest to guest. Note the use of the
+ '!' to tell Samba to stop processing if it gets a match on
+ that line.</P
+><P
+><TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="90%"
+><TR
+><TD
+><PRE
+CLASS="PROGRAMLISTING"
+> !sys = mary fred
+ guest = *
+ </PRE
+></TD
+></TR
+></TABLE
+></P
+><P
+>Note that the remapping is applied to all occurrences
+ of usernames. Thus if you connect to \\server\fred and <TT
+CLASS="CONSTANT"
+> fred</TT
+> is remapped to <TT
+CLASS="CONSTANT"
+>mary</TT
+> then you
+ will actually be connecting to \\server\mary and will need to
+ supply a password suitable for <TT
+CLASS="CONSTANT"
+>mary</TT
+> not
+ <TT
+CLASS="CONSTANT"
+>fred</TT
+>. The only exception to this is the
+ username passed to the <A
+HREF="#PASSWORDSERVER"
+><TT
+CLASS="PARAMETER"
+><I
+> password server</I
+></TT
+></A
+> (if you have one). The password
+ server will receive whatever username the client supplies without
+ modification.</P
+><P
+>Also note that no reverse mapping is done. The main effect
+ this has is with printing. Users who have been mapped may have
+ trouble deleting print jobs as PrintManager under WfWg will think
+ they don't own the print job.</P
+><P
+>Default: <I
+CLASS="EMPHASIS"
+>no username map</I
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>username map = /usr/local/samba/lib/users.map
+ </B
+></P
+></DD
+><DT
+><A
+NAME="USESENDFILE"
+></A
+>use sendfile (S)</DT
+><DD
+><P
+>If this parameter is <TT
+CLASS="CONSTANT"
+>yes</TT
+>, and Samba
+ was built with the --with-sendfile-support option, and the underlying operating
+ system supports sendfile system call, then some SMB read calls (mainly ReadAndX
+ and ReadRaw) will use the more efficient sendfile system call for files that
+ are exclusively oplocked. This may make more efficient use of the system CPU's
+ and cause Samba to be faster. This is off by default as it's effects are unknown
+ as yet.
+ </P
+><P
+>Default: <B
+CLASS="COMMAND"
+>use sendfile = no</B
+></P
+></DD
+><DT
+><A
+NAME="UTMP"
+></A
+>utmp (G)</DT
+><DD
+><P
+>This boolean parameter is only available if
+ Samba has been configured and compiled with the option <B
+CLASS="COMMAND"
+> --with-utmp</B
+>. If set to <TT
+CLASS="CONSTANT"
+>yes</TT
+> then Samba will attempt
+ to add utmp or utmpx records (depending on the UNIX system) whenever a
+ connection is made to a Samba server. Sites may use this to record the
+ user connecting to a Samba share.</P
+><P
+>Due to the requirements of the utmp record, we
+ are required to create a unique identifier for the
+ incoming user. Enabling this option creates an n^2
+ algorithm to find this number. This may impede
+ performance on large installations. </P
+><P
+>See also the <A
+HREF="#UTMPDIRECTORY"
+><TT
+CLASS="PARAMETER"
+><I
+> utmp directory</I
+></TT
+></A
+> parameter.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>utmp = no</B
+></P
+></DD
+><DT
+><A
+NAME="UTMPDIRECTORY"
+></A
+>utmp directory(G)</DT
+><DD
+><P
+>This parameter is only available if Samba has
+ been configured and compiled with the option <B
+CLASS="COMMAND"
+> --with-utmp</B
+>. It specifies a directory pathname that is
+ used to store the utmp or utmpx files (depending on the UNIX system) that
+ record user connections to a Samba server. See also the <A
+HREF="#UTMP"
+> <TT
+CLASS="PARAMETER"
+><I
+>utmp</I
+></TT
+></A
+> parameter. By default this is
+ not set, meaning the system will use whatever utmp file the
+ native system is set to use (usually
+ <TT
+CLASS="FILENAME"
+>/var/run/utmp</TT
+> on Linux).</P
+><P
+>Default: <I
+CLASS="EMPHASIS"
+>no utmp directory</I
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>utmp directory = /var/run/utmp</B
+></P
+></DD
+><DT
+><A
+NAME="WTMPDIRECTORY"
+></A
+>wtmp directory(G)</DT
+><DD
+><P
+>This parameter is only available if Samba has
+ been configured and compiled with the option <B
+CLASS="COMMAND"
+> --with-utmp</B
+>. It specifies a directory pathname that is
+ used to store the wtmp or wtmpx files (depending on the UNIX system) that
+ record user connections to a Samba server. The difference with
+ the utmp directory is the fact that user info is kept after a user
+ has logged out.
+
+ See also the <A
+HREF="#UTMP"
+> <TT
+CLASS="PARAMETER"
+><I
+>utmp</I
+></TT
+></A
+> parameter. By default this is
+ not set, meaning the system will use whatever utmp file the
+ native system is set to use (usually
+ <TT
+CLASS="FILENAME"
+>/var/run/wtmp</TT
+> on Linux).</P
+><P
+>Default: <I
+CLASS="EMPHASIS"
+>no wtmp directory</I
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>wtmp directory = /var/log/wtmp</B
+></P
+></DD
+><DT
+><A
+NAME="VALIDUSERS"
+></A
+>valid users (S)</DT
+><DD
+><P
+>This is a list of users that should be allowed
+ to login to this service. Names starting with '@', '+' and '&#38;'
+ are interpreted using the same rules as described in the
+ <TT
+CLASS="PARAMETER"
+><I
+>invalid users</I
+></TT
+> parameter.</P
+><P
+>If this is empty (the default) then any user can login.
+ If a username is in both this list and the <TT
+CLASS="PARAMETER"
+><I
+>invalid
+ users</I
+></TT
+> list then access is denied for that user.</P
+><P
+>The current servicename is substituted for <TT
+CLASS="PARAMETER"
+><I
+>%S
+ </I
+></TT
+>. This is useful in the [homes] section.</P
+><P
+>See also <A
+HREF="#INVALIDUSERS"
+><TT
+CLASS="PARAMETER"
+><I
+>invalid users
+ </I
+></TT
+></A
+></P
+><P
+>Default: <I
+CLASS="EMPHASIS"
+>No valid users list (anyone can login)
+ </I
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>valid users = greg, @pcusers</B
+></P
+></DD
+><DT
+><A
+NAME="VETOFILES"
+></A
+>veto files(S)</DT
+><DD
+><P
+>This is a list of files and directories that
+ are neither visible nor accessible. Each entry in the list must
+ be separated by a '/', which allows spaces to be included
+ in the entry. '*' and '?' can be used to specify multiple files
+ or directories as in DOS wildcards.</P
+><P
+>Each entry must be a unix path, not a DOS path and
+ must <I
+CLASS="EMPHASIS"
+>not</I
+> include the unix directory
+ separator '/'.</P
+><P
+>Note that the <TT
+CLASS="PARAMETER"
+><I
+>case sensitive</I
+></TT
+> option
+ is applicable in vetoing files.</P
+><P
+>One feature of the veto files parameter that it
+ is important to be aware of is Samba's behaviour when
+ trying to delete a directory. If a directory that is
+ to be deleted contains nothing but veto files this
+ deletion will <I
+CLASS="EMPHASIS"
+>fail</I
+> unless you also set
+ the <TT
+CLASS="PARAMETER"
+><I
+>delete veto files</I
+></TT
+> parameter to
+ <TT
+CLASS="PARAMETER"
+><I
+>yes</I
+></TT
+>.</P
+><P
+>Setting this parameter will affect the performance
+ of Samba, as it will be forced to check all files and directories
+ for a match as they are scanned.</P
+><P
+>See also <A
+HREF="#HIDEFILES"
+><TT
+CLASS="PARAMETER"
+><I
+>hide files
+ </I
+></TT
+></A
+> and <A
+HREF="#CASESENSITIVE"
+><TT
+CLASS="PARAMETER"
+><I
+> case sensitive</I
+></TT
+></A
+>.</P
+><P
+>Default: <I
+CLASS="EMPHASIS"
+>No files or directories are vetoed.
+ </I
+></P
+><P
+>Examples:<TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="90%"
+><TR
+><TD
+><PRE
+CLASS="PROGRAMLISTING"
+>; Veto any files containing the word Security,
; any ending in .tmp, and any directory containing the
; word root.
veto files = /*Security*/*.tmp/*root*/
; Veto the Apple specific files that a NetAtalk server
; creates.
-veto files = /.AppleDouble/.bin/.AppleDesktop/Network Trash Folder/
-</pre></dd><dt><span class="term"><a name="VETOOPLOCKFILES"></a>veto oplock files (S)</span></dt><dd><p>This parameter is only valid when the <a href="#OPLOCKS">
- <i><tt>oplocks</tt></i></a>
- parameter is turned on for a share. It allows the Samba administrator
- to selectively turn off the granting of oplocks on selected files that
- match a wildcarded list, similar to the wildcarded list used in the
- <a href="#VETOFILES"><i><tt>veto files</tt></i></a>
- parameter.</p><p>Default: <span class="emphasis"><em>No files are vetoed for oplock grants</em></span></p><p>You might want to do this on files that you know will
- be heavily contended for by clients. A good example of this
- is in the NetBench SMB benchmark program, which causes heavy
- client contention for files ending in <tt>.SEM</tt>.
- To cause Samba not to grant oplocks on these files you would use
- the line (either in the [global] section or in the section for
- the particular NetBench share :</p><p>Example: <b>veto oplock files = /*.SEM/</b></p></dd><dt><span class="term"><a name="VFSOBJECT"></a>vfs object (S)</span></dt><dd><p>This parameter specifies a shared object files that
- are used for Samba VFS I/O operations. By default, normal
- disk I/O operations are used but these can be overloaded
- with one or more VFS objects. </p><p>Default: <span class="emphasis"><em>no value</em></span></p></dd><dt><span class="term"><a name="VFSOPTIONS"></a>vfs options (S)</span></dt><dd><p>This parameter allows parameters to be passed
- to the vfs layer at initialization time.
- See also <a href="#VFSOBJECT"><i><tt>
- vfs object</tt></i></a>.</p><p>Default: <span class="emphasis"><em>no value</em></span></p></dd><dt><span class="term"><a name="VFSPATH"></a>vfs path (S)</span></dt><dd><p>This parameter specifies the directory
- to look in for vfs modules. The name of every <b>vfs object
- </b> will be prepended by this directory.</p><p>Default: <b>vfs path = </b></p><p>Example: <b>vfs path = /usr/lib/samba/vfs</b></p></dd><dt><span class="term"><a name="VOLUME"></a>volume (S)</span></dt><dd><p> This allows you to override the volume label
- returned for a share. Useful for CDROMs with installation programs
- that insist on a particular volume label.</p><p>Default: <span class="emphasis"><em>the name of the share</em></span></p></dd><dt><span class="term"><a name="WIDELINKS"></a>wide links (S)</span></dt><dd><p>This parameter controls whether or not links
- in the UNIX file system may be followed by the server. Links
- that point to areas within the directory tree exported by the
- server are always allowed; this parameter controls access only
- to areas that are outside the directory tree being exported.</p><p>Note that setting this parameter can have a negative
- effect on your server performance due to the extra system calls
- that Samba has to do in order to perform the link checks.</p><p>Default: <b>wide links = yes</b></p></dd><dt><span class="term"><a name="WINBINDCACHETIME"></a>winbind cache time (G)</span></dt><dd><p>This parameter specifies the number of
- seconds the <a href="winbindd.8.html">winbindd(8)</a> daemon will cache
- user and group information before querying a Windows NT server
- again.</p><p>Default: <b>winbind cache type = 15</b></p></dd><dt><span class="term"><a name="WINBINDENUMGROUPS"></a>winbind enum groups (G)</span></dt><dd><p>On large installations using <a href="winbindd.8.html">winbindd(8)</a> it may be necessary to suppress
- the enumeration of groups through the <b>setgrent()</b>,
- <b>getgrent()</b> and
- <b>endgrent()</b> group of system calls. If
- the <i><tt>winbind enum groups</tt></i> parameter is
- <tt>no</tt>, calls to the <b>getgrent()</b> system
- call will not return any data. </p><p><span class="emphasis"><em>Warning:</em></span> Turning off group
- enumeration may cause some programs to behave oddly.
- </p><p>Default: <b>winbind enum groups = yes </b></p></dd><dt><span class="term"><a name="WINBINDENUMUSERS"></a>winbind enum users (G)</span></dt><dd><p>On large installations using <a href="winbindd.8.html">winbindd(8)</a> it may be
- necessary to suppress the enumeration of users through the <b>setpwent()</b>,
- <b>getpwent()</b> and
- <b>endpwent()</b> group of system calls. If
- the <i><tt>winbind enum users</tt></i> parameter is
- <tt>no</tt>, calls to the <b>getpwent</b> system call
- will not return any data. </p><p><span class="emphasis"><em>Warning:</em></span> Turning off user
- enumeration may cause some programs to behave oddly. For
- example, the finger program relies on having access to the
- full user list when searching for matching
- usernames. </p><p>Default: <b>winbind enum users = yes </b></p></dd><dt><span class="term"><a name="WINBINDGID"></a>winbind gid (G)</span></dt><dd><p>The winbind gid parameter specifies the range of group
- ids that are allocated by the <a href="winbindd.8.html">winbindd(8)</a> daemon. This range of group ids should have no
- existing local or NIS groups within it as strange conflicts can
- occur otherwise.</p><p>Default: <b>winbind gid = &lt;empty string&gt;</b></p><p>Example: <b>winbind gid = 10000-20000</b></p></dd><dt><span class="term"><a name="WINBINDSEPARATOR"></a>winbind separator (G)</span></dt><dd><p>This parameter allows an admin to define the character
- used when listing a username of the form of <i><tt>DOMAIN
- </tt></i>\<i><tt>user</tt></i>. This parameter
- is only applicable when using the <tt>pam_winbind.so</tt>
- and <tt>nss_winbind.so</tt> modules for UNIX services.
- </p><p>Please note that setting this parameter to + causes problems
- with group membership at least on glibc systems, as the character +
- is used as a special character for NIS in /etc/group.</p><p>Default: <b>winbind separator = '\'</b></p><p>Example: <b>winbind separator = +</b></p></dd><dt><span class="term"><a name="WINBINDUID"></a>winbind uid (G)</span></dt><dd><p>The winbind gid parameter specifies the range of group
- ids that are allocated by the <a href="winbindd.8.html">winbindd(8)</a> daemon. This range of ids should have no
- existing local or NIS users within it as strange conflicts can
- occur otherwise.</p><p>Default: <b>winbind uid = &lt;empty string&gt;</b></p><p>Example: <b>winbind uid = 10000-20000</b></p></dd><dt><span class="term"><a name="WINBINDUSEDDEFAULTDOMAIN"></a>winbind used default domain (G)</span></dt><dd><p>This parameter specifies whether the
- <a href="winbindd.8.html">winbindd(8)</a> daemon should operate on users
- without domain component in their username. Users without a domain
- component are treated as is part of the winbindd server's own
- domain. While this does not benifit Windows users, it makes SSH, FTP and
- e-mail function in a way much closer to the way they
- would in a native unix system.</p><p>Default: <b>winbind use default domain = &lt;no&gt;</b></p><p>Example: <b>winbind use default domain = yes</b></p></dd><dt><span class="term"><a name="WINSHOOK"></a>wins hook (G)</span></dt><dd><p>When Samba is running as a WINS server this
- allows you to call an external program for all changes to the
- WINS database. The primary use for this option is to allow the
- dynamic update of external name resolution databases such as
- dynamic DNS.</p><p>The wins hook parameter specifies the name of a script
- or executable that will be called as follows:</p><p><b>wins_hook operation name nametype ttl IP_list</b></p><div class="itemizedlist"><ul type="disc"><li><p>The first argument is the operation and is
- one of &quot;add&quot;, &quot;delete&quot;, or
- &quot;refresh&quot;. In most cases the operation
- can be ignored as the rest of the parameters
- provide sufficient information. Note that
- &quot;refresh&quot; may sometimes be called when
- the name has not previously been added, in that
- case it should be treated as an add.</p></li><li><p>The second argument is the NetBIOS name. If the
+veto files = /.AppleDouble/.bin/.AppleDesktop/Network Trash Folder/</PRE
+></TD
+></TR
+></TABLE
+></P
+></DD
+><DT
+><A
+NAME="VETOOPLOCKFILES"
+></A
+>veto oplock files (S)</DT
+><DD
+><P
+>This parameter is only valid when the <A
+HREF="#OPLOCKS"
+><TT
+CLASS="PARAMETER"
+><I
+>oplocks</I
+></TT
+></A
+>
+ parameter is turned on for a share. It allows the Samba administrator
+ to selectively turn off the granting of oplocks on selected files that
+ match a wildcarded list, similar to the wildcarded list used in the
+ <A
+HREF="#VETOFILES"
+><TT
+CLASS="PARAMETER"
+><I
+>veto files</I
+></TT
+></A
+>
+ parameter.</P
+><P
+>Default: <I
+CLASS="EMPHASIS"
+>No files are vetoed for oplock
+ grants</I
+></P
+><P
+>You might want to do this on files that you know will
+ be heavily contended for by clients. A good example of this
+ is in the NetBench SMB benchmark program, which causes heavy
+ client contention for files ending in <TT
+CLASS="FILENAME"
+>.SEM</TT
+>.
+ To cause Samba not to grant oplocks on these files you would use
+ the line (either in the [global] section or in the section for
+ the particular NetBench share :</P
+><P
+>Example: <B
+CLASS="COMMAND"
+>veto oplock files = /*.SEM/
+ </B
+></P
+></DD
+><DT
+><A
+NAME="VFSPATH"
+></A
+>vfs path (S)</DT
+><DD
+><P
+>This parameter specifies the directory
+ to look in for vfs modules. The name of every <B
+CLASS="COMMAND"
+>vfs object
+ </B
+> will be prepended by this directory
+ </P
+><P
+>Default: <B
+CLASS="COMMAND"
+>vfs path = </B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>vfs path = /usr/lib/samba/vfs</B
+></P
+></DD
+><DT
+><A
+NAME="VFSOBJECT"
+></A
+>vfs object (S)</DT
+><DD
+><P
+>This parameter specifies a shared object files that
+ are used for Samba VFS I/O operations. By default, normal
+ disk I/O operations are used but these can be overloaded
+ with one or more VFS objects. </P
+><P
+>Default : <I
+CLASS="EMPHASIS"
+>no value</I
+></P
+></DD
+><DT
+><A
+NAME="VFSOPTIONS"
+></A
+>vfs options (S)</DT
+><DD
+><P
+>This parameter allows parameters to be passed
+ to the vfs layer at initialization time.
+ See also <A
+HREF="#VFSOBJECT"
+><TT
+CLASS="PARAMETER"
+><I
+> vfs object</I
+></TT
+></A
+>.</P
+><P
+>Default : <I
+CLASS="EMPHASIS"
+>no value</I
+></P
+></DD
+><DT
+><A
+NAME="VOLUME"
+></A
+>volume (S)</DT
+><DD
+><P
+> This allows you to override the volume label
+ returned for a share. Useful for CDROMs with installation programs
+ that insist on a particular volume label.</P
+><P
+>Default: <I
+CLASS="EMPHASIS"
+>the name of the share</I
+></P
+></DD
+><DT
+><A
+NAME="WIDELINKS"
+></A
+>wide links (S)</DT
+><DD
+><P
+>This parameter controls whether or not links
+ in the UNIX file system may be followed by the server. Links
+ that point to areas within the directory tree exported by the
+ server are always allowed; this parameter controls access only
+ to areas that are outside the directory tree being exported.</P
+><P
+>Note that setting this parameter can have a negative
+ effect on your server performance due to the extra system calls
+ that Samba has to do in order to perform the link checks.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>wide links = yes</B
+></P
+></DD
+><DT
+><A
+NAME="WINBINDCACHETIME"
+></A
+>winbind cache time (G)</DT
+><DD
+><P
+>This parameter specifies the number of seconds the
+ <A
+HREF="winbindd.8.html"
+TARGET="_top"
+>winbindd(8)</A
+> daemon will cache
+ user and group information before querying a Windows NT server
+ again.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>winbind cache type = 15</B
+></P
+></DD
+><DT
+><A
+NAME="WINBINDENUMUSERS"
+></A
+>winbind enum users (G)</DT
+><DD
+><P
+>On large installations using
+ <A
+HREF="winbindd.8.html"
+TARGET="_top"
+>winbindd(8)</A
+> it may be
+ necessary to suppress the enumeration of users through the
+ <B
+CLASS="COMMAND"
+> setpwent()</B
+>,
+ <B
+CLASS="COMMAND"
+>getpwent()</B
+> and
+ <B
+CLASS="COMMAND"
+>endpwent()</B
+> group of system calls. If
+ the <TT
+CLASS="PARAMETER"
+><I
+>winbind enum users</I
+></TT
+> parameter is
+ <TT
+CLASS="CONSTANT"
+>no</TT
+>, calls to the <B
+CLASS="COMMAND"
+>getpwent</B
+> system call
+ will not return any data. </P
+><P
+><I
+CLASS="EMPHASIS"
+>Warning:</I
+> Turning off user
+ enumeration may cause some programs to behave oddly. For
+ example, the finger program relies on having access to the
+ full user list when searching for matching
+ usernames. </P
+><P
+>Default: <B
+CLASS="COMMAND"
+>winbind enum users = yes </B
+></P
+></DD
+><DT
+><A
+NAME="WINBINDENUMGROUPS"
+></A
+>winbind enum groups (G)</DT
+><DD
+><P
+>On large installations using
+ <A
+HREF="winbindd.8.html"
+TARGET="_top"
+>winbindd(8)</A
+> it may be
+ necessary to suppress the enumeration of groups through the
+ <B
+CLASS="COMMAND"
+> setgrent()</B
+>,
+ <B
+CLASS="COMMAND"
+>getgrent()</B
+> and
+ <B
+CLASS="COMMAND"
+>endgrent()</B
+> group of system calls. If
+ the <TT
+CLASS="PARAMETER"
+><I
+>winbind enum groups</I
+></TT
+> parameter is
+ <TT
+CLASS="CONSTANT"
+>no</TT
+>, calls to the <B
+CLASS="COMMAND"
+>getgrent()</B
+> system
+ call will not return any data. </P
+><P
+><I
+CLASS="EMPHASIS"
+>Warning:</I
+> Turning off group
+ enumeration may cause some programs to behave oddly.
+ </P
+><P
+>Default: <B
+CLASS="COMMAND"
+>winbind enum groups = yes </B
+>
+ </P
+></DD
+><DT
+><A
+NAME="WINBINDGID"
+></A
+>winbind gid (G)</DT
+><DD
+><P
+>The winbind gid parameter specifies the range of group
+ ids that are allocated by the <A
+HREF="winbindd.8.html"
+TARGET="_top"
+> winbindd(8)</A
+> daemon. This range of group ids should have no
+ existing local or NIS groups within it as strange conflicts can
+ occur otherwise.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>winbind gid = &#60;empty string&#62;
+ </B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>winbind gid = 10000-20000</B
+></P
+></DD
+><DT
+><A
+NAME="WINBINDSEPARATOR"
+></A
+>winbind separator (G)</DT
+><DD
+><P
+>This parameter allows an admin to define the character
+ used when listing a username of the form of <TT
+CLASS="REPLACEABLE"
+><I
+>DOMAIN
+ </I
+></TT
+>\<TT
+CLASS="REPLACEABLE"
+><I
+>user</I
+></TT
+>. This parameter
+ is only applicable when using the <TT
+CLASS="FILENAME"
+>pam_winbind.so</TT
+>
+ and <TT
+CLASS="FILENAME"
+>nss_winbind.so</TT
+> modules for UNIX services.
+ </P
+><P
+>Please note that setting this parameter to + causes problems
+ with group membership at least on glibc systems, as the character +
+ is used as a special character for NIS in /etc/group.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>winbind separator = '\'</B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>winbind separator = +</B
+></P
+></DD
+><DT
+><A
+NAME="WINBINDUID"
+></A
+>winbind uid (G)</DT
+><DD
+><P
+>The winbind gid parameter specifies the range of group
+ ids that are allocated by the <A
+HREF="winbindd.8.html"
+TARGET="_top"
+> winbindd(8)</A
+> daemon. This range of ids should have no
+ existing local or NIS users within it as strange conflicts can
+ occur otherwise.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>winbind uid = &#60;empty string&#62;
+ </B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>winbind uid = 10000-20000</B
+></P
+></DD
+><DT
+>winbind use default domain, <A
+NAME="WINBINDUSEDEFAULTDOMAIN"
+></A
+>winbind use default domain (G)</DT
+><DD
+><P
+>This parameter specifies whether the <A
+HREF="winbindd.8.html"
+TARGET="_top"
+> winbindd(8)</A
+>
+ daemon should operate on users without domain component in their username.
+ Users without a domain component are treated as is part of the winbindd server's
+ own domain. While this does not benifit Windows users, it makes SSH, FTP and e-mail
+ function in a way much closer to the way they would in a native unix system.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>winbind use default domain = &#60;no&#62;
+ </B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>winbind use default domain = yes</B
+></P
+></DD
+><DT
+><A
+NAME="WINSHOOK"
+></A
+>wins hook (G)</DT
+><DD
+><P
+>When Samba is running as a WINS server this
+ allows you to call an external program for all changes to the
+ WINS database. The primary use for this option is to allow the
+ dynamic update of external name resolution databases such as
+ dynamic DNS.</P
+><P
+>The wins hook parameter specifies the name of a script
+ or executable that will be called as follows:</P
+><P
+><B
+CLASS="COMMAND"
+>wins_hook operation name nametype ttl IP_list
+ </B
+></P
+><P
+></P
+><UL
+><LI
+><P
+>The first argument is the operation and is one
+ of "add", "delete", or "refresh". In most cases the operation can
+ be ignored as the rest of the parameters provide sufficient
+ information. Note that "refresh" may sometimes be called when the
+ name has not previously been added, in that case it should be treated
+ as an add.</P
+></LI
+><LI
+><P
+>The second argument is the NetBIOS name. If the
name is not a legal name then the wins hook is not called.
Legal names contain only letters, digits, hyphens, underscores
- and periods.</p></li><li><p>The third argument is the NetBIOS name
- type as a 2 digit hexadecimal number. </p></li><li><p>The fourth argument is the TTL (time to live)
- for the name in seconds.</p></li><li><p>The fifth and subsequent arguments are the IP
+ and periods.</P
+></LI
+><LI
+><P
+>The third argument is the NetBIOS name
+ type as a 2 digit hexadecimal number. </P
+></LI
+><LI
+><P
+>The fourth argument is the TTL (time to live)
+ for the name in seconds.</P
+></LI
+><LI
+><P
+>The fifth and subsequent arguments are the IP
addresses currently registered for that name. If this list is
- empty then the name should be deleted.</p></li></ul></div><p>An example script that calls the BIND dynamic DNS update
- program <b>nsupdate</b> is provided in the examples
- directory of the Samba source code. </p></dd><dt><span class="term"><a name="WINSPARTNER"></a>wins partner (G)</span></dt><dd><p>A space separated list of partners' IP addresses for
- WINS replication. WINS partners are always defined as push/pull
- partners as defining only one way WINS replication is unreliable.
- WINS replication is currently experimental and unreliable between
- samba servers.
- </p><p>Default: <b>wins partners = </b></p><p>Example: <b>wins partners = 192.168.0.1 172.16.1.2</b></p></dd><dt><span class="term"><a name="WINSPROXY"></a>wins proxy (G)</span></dt><dd><p>This is a boolean that controls if <a href="nmbd.8.html">nmbd(8)</a> will respond to broadcast name
- queries on behalf of other hosts. You may need to set this
- to <tt>yes</tt> for some older clients.</p><p>Default: <b>wins proxy = no</b></p></dd><dt><span class="term"><a name="WINSSERVER"></a>wins server (G)</span></dt><dd><p>This specifies the IP address (or DNS name: IP
- address for preference) of the WINS server that <a href="nmbd.8.html">nmbd(8)</a> should register with. If you have a WINS server on
- your network then you should set this to the WINS server's IP.</p><p>You should point this at your WINS server if you have a
- multi-subnetted network.</p><p>If you want to work in multiple namespaces, you can
- give every wins server a 'tag'. For each tag, only one
- (working) server will be queried for a name. The tag should be
- seperated from the ip address by a colon.
- </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>You need to set up Samba to point
- to a WINS server if you have multiple subnets and wish cross-subnet
- browsing to work correctly.</p></div><p>See the documentation file <a href="improved-browsing.html" target="_top">Browsing</a> in the samba howto collection.</p><p>Default: <span class="emphasis"><em>not enabled</em></span></p><p>Example: <b>wins server = mary:192.9.200.1 fred:192.168.3.199 mary:192.168.2.61</b></p><p>For this example when querying a certain name, 192.19.200.1 will
- be asked first and if that doesn't respond 192.168.2.61. If either
- of those doesn't know the name 192.168.3.199 will be queried.
- </p><p>Example: <b>wins server = 192.9.200.1 192.168.2.61</b></p></dd><dt><span class="term"><a name="WINSSUPPORT"></a>wins support (G)</span></dt><dd><p>This boolean controls if the <a href="nmbd.8.html">nmbd(8)</a> process in Samba will act as a WINS server. You should
- not set this to <tt>yes</tt> unless you have a multi-subnetted network and
- you wish a particular <b>nmbd</b> to be your WINS server.
- Note that you should <span class="emphasis"><em>NEVER</em></span> set this to <tt>yes</tt>
- on more than one machine in your network.</p><p>Default: <b>wins support = no</b></p></dd><dt><span class="term"><a name="WORKGROUP"></a>workgroup (G)</span></dt><dd><p>This controls what workgroup your server will
- appear to be in when queried by clients. Note that this parameter
- also controls the Domain name used with
- the <a href="#SECURITYEQUALSDOMAIN"><b>security = domain</b></a>
- setting.</p><p>Default: <span class="emphasis"><em>set at compile time to WORKGROUP</em></span></p><p>Example: <b>workgroup = MYGROUP</b></p></dd><dt><span class="term"><a name="WRITABLE"></a>writable (S)</span></dt><dd><p>Synonym for <a href="#WRITEABLE"><i><tt>
- writeable</tt></i></a> for people who can't spell :-).</p></dd><dt><span class="term"><a name="WRITEABLE"></a>writeable (S)</span></dt><dd><p>Inverted synonym for <a href="#READONLY">
- <i><tt>read only</tt></i></a>.</p></dd><dt><span class="term"><a name="WRITECACHESIZE"></a>write cache size (S)</span></dt><dd><p>If this integer parameter is set to non-zero value,
- Samba will create an in-memory cache for each oplocked file
- (it does <span class="emphasis"><em>not</em></span> do this for
- non-oplocked files). All writes that the client does not request
- to be flushed directly to disk will be stored in this cache if possible.
- The cache is flushed onto disk when a write comes in whose offset
- would not fit into the cache or when the file is closed by the client.
- Reads for the file are also served from this cache if the data is stored
- within it.</p><p>This cache allows Samba to batch client writes into a more
- efficient write size for RAID disks (i.e. writes may be tuned to
- be the RAID stripe size) and can improve performance on systems
- where the disk subsystem is a bottleneck but there is free
- memory for userspace programs.</p><p>The integer parameter specifies the size of this cache
- (per oplocked file) in bytes.</p><p>Default: <b>write cache size = 0</b></p><p>Example: <b>write cache size = 262144</b></p><p>for a 256k cache size per file.</p></dd><dt><span class="term"><a name="WRITELIST"></a>write list (S)</span></dt><dd><p>This is a list of users that are given read-write
- access to a service. If the connecting user is in this list then
- they will be given write access, no matter what the <a href="#READONLY">
- <i><tt>read only</tt></i></a>
- option is set to. The list can include group names using the
- @group syntax.</p><p>Note that if a user is in both the read list and the
- write list then they will be given write access.</p><p>See also the <a href="#READLIST"><i><tt>read list
- </tt></i></a> option.</p><p>Default: <b>write list = &lt;empty string&gt;</b></p><p>Example: <b>write list = admin, root, @staff</b></p></dd><dt><span class="term"><a name="WRITEOK"></a>write ok (S)</span></dt><dd><p>Inverted synonym for <a href="#READONLY">
- <i><tt>read only</tt></i></a>.</p></dd><dt><span class="term"><a name="WRITERAW"></a>write raw (G)</span></dt><dd><p>This parameter controls whether or not the server
- will support raw write SMB's when transferring data from clients.
- You should never need to change this parameter.</p><p>Default: <b>write raw = yes</b></p></dd><dt><span class="term"><a name="WTMPDIRECTORY"></a>wtmp directory (G)</span></dt><dd><p>This parameter is only available if Samba has
- been configured and compiled with the option <b>
- --with-utmp</b>. It specifies a directory pathname that is
- used to store the wtmp or wtmpx files (depending on the UNIX system) that
- record user connections to a Samba server. The difference with
- the utmp directory is the fact that user info is kept after a user
- has logged out.</p><p>See also the <a href="#UTMP">
- <i><tt>utmp</tt></i></a> parameter. By default this is
- not set, meaning the system will use whatever utmp file the
- native system is set to use (usually
- <tt>/var/run/wtmp</tt> on Linux).</p><p>Default: <span class="emphasis"><em>no wtmp directory</em></span></p><p>Example: <b>wtmp directory = /var/log/wtmp</b></p></dd></dl></div></div><div class="refsect1" lang="en"><h2>WARNINGS</h2><p>Although the configuration file permits service names
+ empty then the name should be deleted.</P
+></LI
+></UL
+><P
+>An example script that calls the BIND dynamic DNS update
+ program <B
+CLASS="COMMAND"
+>nsupdate</B
+> is provided in the examples
+ directory of the Samba source code. </P
+></DD
+><DT
+><A
+NAME="WINSPROXY"
+></A
+>wins proxy (G)</DT
+><DD
+><P
+>This is a boolean that controls if <A
+HREF="nmbd.8.html"
+TARGET="_top"
+>nmbd(8)</A
+> will respond to broadcast name
+ queries on behalf of other hosts. You may need to set this
+ to <TT
+CLASS="CONSTANT"
+>yes</TT
+> for some older clients.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>wins proxy = no</B
+></P
+></DD
+><DT
+><A
+NAME="WINSSERVER"
+></A
+>wins server (G)</DT
+><DD
+><P
+>This specifies the IP address (or DNS name: IP
+ address for preference) of the WINS server that <A
+HREF="nmbd.8.html"
+TARGET="_top"
+> nmbd(8)</A
+> should register with. If you have a WINS server on
+ your network then you should set this to the WINS server's IP.</P
+><P
+>You should point this at your WINS server if you have a
+ multi-subnetted network.</P
+><P
+><I
+CLASS="EMPHASIS"
+>NOTE</I
+>. You need to set up Samba to point
+ to a WINS server if you have multiple subnets and wish cross-subnet
+ browsing to work correctly.</P
+><P
+>See the documentation file <TT
+CLASS="FILENAME"
+>BROWSING.txt</TT
+>
+ in the docs/ directory of your Samba source distribution.</P
+><P
+>Default: <I
+CLASS="EMPHASIS"
+>not enabled</I
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>wins server = 192.9.200.1</B
+></P
+></DD
+><DT
+><A
+NAME="WINSSUPPORT"
+></A
+>wins support (G)</DT
+><DD
+><P
+>This boolean controls if the <A
+HREF="nmbd.8.html"
+TARGET="_top"
+>
+ nmbd(8)</A
+> process in Samba will act as a WINS server. You should
+ not set this to <TT
+CLASS="CONSTANT"
+>yes</TT
+> unless you have a multi-subnetted network and
+ you wish a particular <B
+CLASS="COMMAND"
+>nmbd</B
+> to be your WINS server.
+ Note that you should <I
+CLASS="EMPHASIS"
+>NEVER</I
+> set this to <TT
+CLASS="CONSTANT"
+>yes</TT
+>
+ on more than one machine in your network.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>wins support = no</B
+></P
+></DD
+><DT
+><A
+NAME="WORKGROUP"
+></A
+>workgroup (G)</DT
+><DD
+><P
+>This controls what workgroup your server will
+ appear to be in when queried by clients. Note that this parameter
+ also controls the Domain name used with the <A
+HREF="#SECURITYEQUALSDOMAIN"
+><B
+CLASS="COMMAND"
+>security = domain</B
+></A
+>
+ setting.</P
+><P
+>Default: <I
+CLASS="EMPHASIS"
+>set at compile time to WORKGROUP</I
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>workgroup = MYGROUP</B
+></P
+></DD
+><DT
+><A
+NAME="WRITABLE"
+></A
+>writable (S)</DT
+><DD
+><P
+>Synonym for <A
+HREF="#WRITEABLE"
+><TT
+CLASS="PARAMETER"
+><I
+> writeable</I
+></TT
+></A
+> for people who can't spell :-).</P
+></DD
+><DT
+><A
+NAME="WRITECACHESIZE"
+></A
+>write cache size (S)</DT
+><DD
+><P
+>If this integer parameter is set to non-zero value,
+ Samba will create an in-memory cache for each oplocked file
+ (it does <I
+CLASS="EMPHASIS"
+>not</I
+> do this for
+ non-oplocked files). All writes that the client does not request
+ to be flushed directly to disk will be stored in this cache if possible.
+ The cache is flushed onto disk when a write comes in whose offset
+ would not fit into the cache or when the file is closed by the client.
+ Reads for the file are also served from this cache if the data is stored
+ within it.</P
+><P
+>This cache allows Samba to batch client writes into a more
+ efficient write size for RAID disks (i.e. writes may be tuned to
+ be the RAID stripe size) and can improve performance on systems
+ where the disk subsystem is a bottleneck but there is free
+ memory for userspace programs.</P
+><P
+>The integer parameter specifies the size of this cache
+ (per oplocked file) in bytes.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>write cache size = 0</B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>write cache size = 262144</B
+></P
+><P
+>for a 256k cache size per file.</P
+></DD
+><DT
+><A
+NAME="WRITELIST"
+></A
+>write list (S)</DT
+><DD
+><P
+>This is a list of users that are given read-write
+ access to a service. If the connecting user is in this list then
+ they will be given write access, no matter what the <A
+HREF="#READONLY"
+><TT
+CLASS="PARAMETER"
+><I
+>read only</I
+></TT
+></A
+>
+ option is set to. The list can include group names using the
+ @group syntax.</P
+><P
+>Note that if a user is in both the read list and the
+ write list then they will be given write access.</P
+><P
+>See also the <A
+HREF="#READLIST"
+><TT
+CLASS="PARAMETER"
+><I
+>read list
+ </I
+></TT
+></A
+> option.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>write list = &#60;empty string&#62;
+ </B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>write list = admin, root, @staff
+ </B
+></P
+></DD
+><DT
+><A
+NAME="WINSPARTNERS"
+></A
+>wins partners (G)</DT
+><DD
+><P
+>A space separated list of partners' IP addresses for
+ WINS replication. WINS partners are always defined as push/pull
+ partners as defining only one way WINS replication is unreliable.
+ WINS replication is currently experimental and unreliable between
+ samba servers.
+ </P
+><P
+>Default: <B
+CLASS="COMMAND"
+>wins partners = </B
+></P
+><P
+>Example: <B
+CLASS="COMMAND"
+>wins partners = 192.168.0.1 172.16.1.2</B
+></P
+></DD
+><DT
+><A
+NAME="WRITEOK"
+></A
+>write ok (S)</DT
+><DD
+><P
+>Inverted synonym for <A
+HREF="#READONLY"
+><TT
+CLASS="PARAMETER"
+><I
+> read only</I
+></TT
+></A
+>.</P
+></DD
+><DT
+><A
+NAME="WRITERAW"
+></A
+>write raw (G)</DT
+><DD
+><P
+>This parameter controls whether or not the server
+ will support raw write SMB's when transferring data from clients.
+ You should never need to change this parameter.</P
+><P
+>Default: <B
+CLASS="COMMAND"
+>write raw = yes</B
+></P
+></DD
+><DT
+><A
+NAME="WRITEABLE"
+></A
+>writeable (S)</DT
+><DD
+><P
+>Inverted synonym for <A
+HREF="#READONLY"
+><TT
+CLASS="PARAMETER"
+><I
+> read only</I
+></TT
+></A
+>.</P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN6215"
+></A
+><H2
+>WARNINGS</H2
+><P
+>Although the configuration file permits service names
to contain spaces, your client software may not. Spaces will
be ignored in comparisons anyway, so it shouldn't be a
- problem - but be aware of the possibility.</p><p>On a similar note, many clients - especially DOS clients -
- limit service names to eight characters. <a href="smbd.8.html">smbd(8)</a> has no such limitation, but attempts to connect from such
+ problem - but be aware of the possibility.</P
+><P
+>On a similar note, many clients - especially DOS clients -
+ limit service names to eight characters. <A
+HREF="smbd.8.html"
+TARGET="_top"
+>smbd(8)
+ </A
+> has no such limitation, but attempts to connect from such
clients will fail if they truncate the service names. For this reason
you should probably keep your service names down to eight characters
- in length.</p><p>Use of the [homes] and [printers] special sections make life
+ in length.</P
+><P
+>Use of the [homes] and [printers] special sections make life
for an administrator easy, but the various combinations of default
attributes can be tricky. Take extreme care when designing these
sections. In particular, ensure that the permissions on spool
- directories are correct.</p></div><div class="refsect1" lang="en"><h2>VERSION</h2><p>This man page is correct for version 3.0 of the Samba suite.</p></div><div class="refsect1" lang="en"><h2>SEE ALSO</h2><p>
- <a href="samba.7.html">samba(7)</a>, <a href="smbpasswd.8.html">smbpasswd(8)</a>, <a href="swat.8.html">swat(8)</a>, <a href="smbd.8.html">smbd(8)</a>, <a href="nmbd.8.html">nmbd(8)</a>, <a href="smbclient.1.html">smbclient(1)</a>, <a href="nmblookup.1.html">nmblookup(1)</a>, <a href="testparm.1.html">testparm(1)</a>, <a href="testprns.1.html">testprns(1)</a>.</p></div><div class="refsect1" lang="en"><h2>AUTHOR</h2><p>The original Samba software and related utilities
+ directories are correct.</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN6221"
+></A
+><H2
+>VERSION</H2
+><P
+>This man page is correct for version 3.0 of
+ the Samba suite.</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN6224"
+></A
+><H2
+>SEE ALSO</H2
+><P
+><A
+HREF="samba.7.html"
+TARGET="_top"
+>samba(7)</A
+>,
+ <A
+HREF="smbpasswd.8.html"
+TARGET="_top"
+><B
+CLASS="COMMAND"
+>smbpasswd(8)</B
+></A
+>,
+ <A
+HREF="swat.8.html"
+TARGET="_top"
+><B
+CLASS="COMMAND"
+>swat(8)</B
+></A
+>,
+ <A
+HREF="smbd.8.html"
+TARGET="_top"
+><B
+CLASS="COMMAND"
+>smbd(8)</B
+></A
+>,
+ <A
+HREF="nmbd.8.html"
+TARGET="_top"
+><B
+CLASS="COMMAND"
+>nmbd(8)</B
+></A
+>,
+ <A
+HREF="smbclient.1.html"
+TARGET="_top"
+><B
+CLASS="COMMAND"
+>smbclient(1)</B
+></A
+>,
+ <A
+HREF="nmblookup.1.html"
+TARGET="_top"
+><B
+CLASS="COMMAND"
+>nmblookup(1)</B
+></A
+>,
+ <A
+HREF="testparm.1.html"
+TARGET="_top"
+><B
+CLASS="COMMAND"
+>testparm(1)</B
+></A
+>,
+ <A
+HREF="testprns.1.html"
+TARGET="_top"
+><B
+CLASS="COMMAND"
+>testprns(1)</B
+></A
+>
+ </P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN6244"
+></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.
+ to the way the Linux kernel is developed.</P
+><P
+>The original Samba man pages were written by Karl Auer.
The man page sources were converted to YODL format (another
- excellent piece of Open Source software, available at <a href="ftp://ftp.icce.rug.nl/pub/unix/" target="_top">
- ftp://ftp.icce.rug.nl/pub/unix/</a>) and updated for the Samba 2.0
+ excellent piece of Open Source software, available at
+ <A
+HREF="ftp://ftp.icce.rug.nl/pub/unix/"
+TARGET="_top"
+> ftp://ftp.icce.rug.nl/pub/unix/</A
+>) and updated for the Samba 2.0
release by Jeremy Allison. The conversion to DocBook for
- Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2
- for Samba 3.0 was done by Alexander Bokovoy.</p></div></div></body></html>
+ Samba 2.2 was done by Gerald Carter</P
+></DIV
+></BODY
+></HTML
+> \ No newline at end of file
diff --git a/docs/htmldocs/smbcacls.1.html b/docs/htmldocs/smbcacls.1.html
index f987680f33..e0425d481d 100644
--- a/docs/htmldocs/smbcacls.1.html
+++ b/docs/htmldocs/smbcacls.1.html
@@ -1,95 +1,415 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>smbcacls</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="smbcacls.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>smbcacls &#8212; Set or get ACLs on an NT file or directory names</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><tt>smbcacls</tt> {//server/share} {filename} [-D acls] [-M acls] [-A acls] [-S acls] [-C name] [-G name] [-n] [-t] [-U username] [-h] [-d]</p></div></div><div class="refsect1" lang="en"><h2>DESCRIPTION</h2><p>This tool is part of the <a href="Samba.7.html">Samba(7)</a> suite.</p><p>The <b>smbcacls</b> program manipulates NT Access Control
- Lists (ACLs) on SMB file shares. </p></div><div class="refsect1" lang="en"><h2>OPTIONS</h2><p>The following options are available to the <b>smbcacls</b> program.
- The format of ACLs is described in the section ACL FORMAT </p><div class="variablelist"><dl><dt><span class="term">-A acls</span></dt><dd><p>Add the ACLs specified to the ACL list. Existing
- access control entries are unchanged. </p></dd><dt><span class="term">-M acls</span></dt><dd><p>Modify the mask value (permissions) for the ACLs
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<HTML
+><HEAD
+><TITLE
+>smbcacls</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.77"></HEAD
+><BODY
+CLASS="REFENTRY"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><H1
+><A
+NAME="SMBCACLS"
+></A
+>smbcacls</H1
+><DIV
+CLASS="REFNAMEDIV"
+><A
+NAME="AEN5"
+></A
+><H2
+>Name</H2
+>smbcacls&nbsp;--&nbsp;Set or get ACLs on an NT file or directory names</DIV
+><DIV
+CLASS="REFSYNOPSISDIV"
+><A
+NAME="AEN8"
+></A
+><H2
+>Synopsis</H2
+><P
+><B
+CLASS="COMMAND"
+>smbcacls</B
+> {//server/share} {filename} [-U username] [-A acls] [-M acls] [-D acls] [-S acls] [-C name] [-G name] [-n] [-h]</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN22"
+></A
+><H2
+>DESCRIPTION</H2
+><P
+>This tool is part of the <A
+HREF="samba.7.html"
+TARGET="_top"
+> Samba</A
+> suite.</P
+><P
+>The <B
+CLASS="COMMAND"
+>smbcacls</B
+> program manipulates NT Access Control
+ Lists (ACLs) on SMB file shares. </P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN28"
+></A
+><H2
+>OPTIONS</H2
+><P
+>The following options are available to the <B
+CLASS="COMMAND"
+>smbcacls</B
+> program.
+ The format of ACLs is described in the section ACL FORMAT </P
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>-A acls</DT
+><DD
+><P
+>Add the ACLs specified to the ACL list. Existing
+ access control entries are unchanged. </P
+></DD
+><DT
+>-M acls</DT
+><DD
+><P
+>Modify the mask value (permissions) for the ACLs
specified on the command line. An error will be printed for each
ACL specified that was not already present in the ACL list
- </p></dd><dt><span class="term">-D acls</span></dt><dd><p>Delete any ACLs specified on the command line.
+ </P
+></DD
+><DT
+>-D acls</DT
+><DD
+><P
+>Delete any ACLs specified on the command line.
An error will be printed for each ACL specified that was not
- already present in the ACL list. </p></dd><dt><span class="term">-S acls</span></dt><dd><p>This command sets the ACLs on the file with
+ already present in the ACL list. </P
+></DD
+><DT
+>-S acls</DT
+><DD
+><P
+>This command sets the ACLs on the file with
only the ones specified on the command line. All other ACLs are
erased. Note that the ACL specified must contain at least a revision,
- type, owner and group for the call to succeed. </p></dd><dt><span class="term">-U username</span></dt><dd><p>Specifies a username used to connect to the
- specified service. The username may be of the form &quot;username&quot; in
+ type, owner and group for the call to succeed. </P
+></DD
+><DT
+>-U username</DT
+><DD
+><P
+>Specifies a username used to connect to the
+ specified service. The username may be of the form "username" in
which case the user is prompted to enter in a password and the
- workgroup specified in the <a href="smb.conf.5.html">smb.conf(5)</a> file is
- used, or &quot;username%password&quot; or &quot;DOMAIN\username%password&quot; and the
- password and workgroup names are used as provided. </p></dd><dt><span class="term">-C name</span></dt><dd><p>The owner of a file or directory can be changed
- to the name given using the <i><tt>-C</tt></i> option.
+ workgroup specified in the <TT
+CLASS="FILENAME"
+>smb.conf</TT
+> file is
+ used, or "username%password" or "DOMAIN\username%password" and the
+ password and workgroup names are used as provided. </P
+></DD
+><DT
+>-C name</DT
+><DD
+><P
+>The owner of a file or directory can be changed
+ to the name given using the <TT
+CLASS="PARAMETER"
+><I
+>-C</I
+></TT
+> option.
The name can be a sid in the form S-1-x-y-z or a name resolved
- against the server specified in the first argument. </p><p>This command is a shortcut for -M OWNER:name.
- </p></dd><dt><span class="term">-G name</span></dt><dd><p>The group owner of a file or directory can
- be changed to the name given using the <i><tt>-G</tt></i>
+ against the server specified in the first argument. </P
+><P
+>This command is a shortcut for -M OWNER:name.
+ </P
+></DD
+><DT
+>-G name</DT
+><DD
+><P
+>The group owner of a file or directory can
+ be changed to the name given using the <TT
+CLASS="PARAMETER"
+><I
+>-G</I
+></TT
+>
option. The name can be a sid in the form S-1-x-y-z or a name
resolved against the server specified n the first argument.
- </p><p>This command is a shortcut for -M GROUP:name.</p></dd><dt><span class="term">-n</span></dt><dd><p>This option displays all ACL information in numeric
+ </P
+><P
+>This command is a shortcut for -M GROUP:name.</P
+></DD
+><DT
+>-n</DT
+><DD
+><P
+>This option displays all ACL information in numeric
format. The default is to convert SIDs to names and ACE types
- and masks to a readable string format. </p></dd><dt><span class="term">-t</span></dt><dd><p>
- Don't actually do anything, only validate the correctness of
- the arguments.
- </p></dd><dt><span class="term">-h|--help</span></dt><dd><p>Print a summary of command line options.
-</p></dd><dt><span class="term">-V</span></dt><dd><p>Prints the version number for
-<b>smbd</b>.</p></dd><dt><span class="term">-s &lt;configuration file&gt;</span></dt><dd><p>The file specified contains the
-configuration details required by the server. The
-information in this file includes server-specific
-information such as what printcap file to use, as well
-as descriptions of all the services that the server is
-to provide. See <a href="smb.conf.5.html" target="_top"><tt>
-smb.conf(5)</tt></a> for more information.
-The default configuration file name is determined at
-compile time.</p></dd><dt><span class="term">-d|--debug=debuglevel</span></dt><dd><p><i><tt>debuglevel</tt></i> is an integer
-from 0 to 10. The default value if this parameter is
-not specified is zero.</p><p>The higher this value, the more detail will be
-logged to the log files about the activities of the
-server. At level 0, only critical errors and serious
-warnings will be logged. Level 1 is a reasonable level for
-day to day running - it generates a small amount of
-information about operations carried out.</p><p>Levels above 1 will generate considerable
-amounts of log data, and should only be used when
-investigating a problem. Levels above 3 are designed for
-use only by developers and generate HUGE amounts of log
-data, most of which is extremely cryptic.</p><p>Note that specifying this parameter here will
-override the <a href="smb.conf.5.html#loglevel" target="_top">log
-level</a> parameter in the <a href="smb.conf.5.html" target="_top">
-<tt>smb.conf(5)</tt></a> file.</p></dd><dt><span class="term">-l|--logfile=logbasename</span></dt><dd><p>File name for log/debug files. The extension
-<tt>&quot;.client&quot;</tt> will be appended. The log file is
-never removed by the client.
-</p></dd></dl></div></div><div class="refsect1" lang="en"><h2>ACL FORMAT</h2><p>The format of an ACL is one or more ACL entries separated by
- either commas or newlines. An ACL entry is one of the following: </p><pre class="programlisting">
+ and masks to a readable string format. </P
+></DD
+><DT
+>-h</DT
+><DD
+><P
+>Print usage information on the <B
+CLASS="COMMAND"
+>smbcacls
+ </B
+> program.</P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN75"
+></A
+><H2
+>ACL FORMAT</H2
+><P
+>The format of an ACL is one or more ACL entries separated by
+ either commas or newlines. An ACL entry is one of the following: </P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>
REVISION:&lt;revision number&gt;
OWNER:&lt;sid or name&gt;
GROUP:&lt;sid or name&gt;
ACL:&lt;sid or name&gt;:&lt;type&gt;/&lt;flags&gt;/&lt;mask&gt;
-</pre><p>The revision of the ACL specifies the internal Windows
+ </PRE
+></P
+><P
+>The revision of the ACL specifies the internal Windows
NT ACL revision for the security descriptor.
If not specified it defaults to 1. Using values other than 1 may
- cause strange behaviour. </p><p>The owner and group specify the owner and group sids for the
+ cause strange behaviour. </P
+><P
+>The owner and group specify the owner and group sids for the
object. If a SID in the format CWS-1-x-y-z is specified this is used,
otherwise the name specified is resolved using the server on which
- the file or directory resides. </p><p>ACLs specify permissions granted to the SID. This SID again
- can be specified in CWS-1-x-y-z format or as a name in which case
- it is resolved against the server on which the file or directory
- resides. The type, flags and mask values determine the type of
- access granted to the SID. </p><p>The type can be either 0 or 1 corresponding to ALLOWED or
- DENIED access to the SID. The flags values are generally
- zero for file ACLs and either 9 or 2 for directory ACLs. Some
- common flags are: </p><div class="itemizedlist"><ul type="disc"><li><p><tt>#define SEC_ACE_FLAG_OBJECT_INHERIT 0x1</tt></p></li><li><p><tt>#define SEC_ACE_FLAG_CONTAINER_INHERIT 0x2</tt></p></li><li><p><tt>#define SEC_ACE_FLAG_NO_PROPAGATE_INHERIT 0x4</tt></p></li><li><p><tt>#define SEC_ACE_FLAG_INHERIT_ONLY 0x8</tt></p></li></ul></div><p>At present flags can only be specified as decimal or
- hexadecimal values.</p><p>The mask is a value which expresses the access right
+ the file or directory resides. </P
+><P
+>ACLs specify permissions granted to the SID. This SID again
+ can be specified in CWS-1-x-y-z format or as a name in which case
+ it is resolved against the server on which the file or directory
+ resides. The type, flags and mask values determine the type of
+ access granted to the SID. </P
+><P
+>The type can be either 0 or 1 corresponding to ALLOWED or
+ DENIED access to the SID. The flags values are generally
+ zero for file ACLs and either 9 or 2 for directory ACLs. Some
+ common flags are: </P
+><P
+></P
+><UL
+><LI
+><P
+>#define SEC_ACE_FLAG_OBJECT_INHERIT 0x1</P
+></LI
+><LI
+><P
+>#define SEC_ACE_FLAG_CONTAINER_INHERIT 0x2</P
+></LI
+><LI
+><P
+>#define SEC_ACE_FLAG_NO_PROPAGATE_INHERIT 0x4
+ </P
+></LI
+><LI
+><P
+>#define SEC_ACE_FLAG_INHERIT_ONLY 0x8</P
+></LI
+></UL
+><P
+>At present flags can only be specified as decimal or
+ hexadecimal values.</P
+><P
+>The mask is a value which expresses the access right
granted to the SID. It can be given as a decimal or hexadecimal value,
or by using one of the following text strings which map to the NT
- file permissions of the same name. </p><div class="itemizedlist"><ul type="disc"><li><p><span class="emphasis"><em>R</em></span> - Allow read access </p></li><li><p><span class="emphasis"><em>W</em></span> - Allow write access</p></li><li><p><span class="emphasis"><em>X</em></span> - Execute permission on the object</p></li><li><p><span class="emphasis"><em>D</em></span> - Delete the object</p></li><li><p><span class="emphasis"><em>P</em></span> - Change permissions</p></li><li><p><span class="emphasis"><em>O</em></span> - Take ownership</p></li></ul></div><p>The following combined permissions can be specified:</p><div class="itemizedlist"><ul type="disc"><li><p><span class="emphasis"><em>READ</em></span> - Equivalent to 'RX'
- permissions</p></li><li><p><span class="emphasis"><em>CHANGE</em></span> - Equivalent to 'RXWD' permissions
- </p></li><li><p><span class="emphasis"><em>FULL</em></span> - Equivalent to 'RWXDPO'
- permissions</p></li></ul></div></div><div class="refsect1" lang="en"><h2>EXIT STATUS</h2><p>The <b>smbcacls</b> program sets the exit status
+ file permissions of the same name. </P
+><P
+></P
+><UL
+><LI
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>R</I
+></SPAN
+> - Allow read access </P
+></LI
+><LI
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>W</I
+></SPAN
+> - Allow write access</P
+></LI
+><LI
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>X</I
+></SPAN
+> - Execute permission on the object</P
+></LI
+><LI
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>D</I
+></SPAN
+> - Delete the object</P
+></LI
+><LI
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>P</I
+></SPAN
+> - Change permissions</P
+></LI
+><LI
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>O</I
+></SPAN
+> - Take ownership</P
+></LI
+></UL
+><P
+>The following combined permissions can be specified:</P
+><P
+></P
+><UL
+><LI
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>READ</I
+></SPAN
+> - Equivalent to 'RX'
+ permissions</P
+></LI
+><LI
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>CHANGE</I
+></SPAN
+> - Equivalent to 'RXWD' permissions
+ </P
+></LI
+><LI
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>FULL</I
+></SPAN
+> - Equivalent to 'RWXDPO'
+ permissions</P
+></LI
+></UL
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN125"
+></A
+><H2
+>EXIT STATUS</H2
+><P
+>The <B
+CLASS="COMMAND"
+>smbcacls</B
+> program sets the exit status
depending on the success or otherwise of the operations performed.
- The exit status may be one of the following values. </p><p>If the operation succeeded, smbcacls returns and exit
- status of 0. If <b>smbcacls</b> couldn't connect to the specified server,
+ The exit status may be one of the following values. </P
+><P
+>If the operation succeeded, smbcacls returns and exit
+ status of 0. If <B
+CLASS="COMMAND"
+>smbcacls</B
+> couldn't connect to the specified server,
or there was an error getting or setting the ACLs, an exit status
of 1 is returned. If there was an error parsing any command line
- arguments, an exit status of 2 is returned. </p></div><div class="refsect1" lang="en"><h2>VERSION</h2><p>This man page is correct for version 3.0 of the Samba suite.</p></div><div class="refsect1" lang="en"><h2>AUTHOR</h2><p>The original Samba software and related utilities
+ arguments, an exit status of 2 is returned. </P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN131"
+></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="AEN134"
+></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><b>smbcacls</b> was written by Andrew Tridgell
- and Tim Potter.</p><p>The conversion to DocBook for Samba 2.2 was done
- by Gerald Carter. The conversion to DocBook XML 4.2 for Samba 3.0 was done
- by Alexander Bokovoy.</p></div></div></body></html>
+ to the way the Linux kernel is developed.</P
+><P
+><B
+CLASS="COMMAND"
+>smbcacls</B
+> was written by Andrew Tridgell
+ and Tim Potter.</P
+><P
+>The conversion to DocBook for Samba 2.2 was done
+ by Gerald Carter</P
+></DIV
+></BODY
+></HTML
+> \ No newline at end of file
diff --git a/docs/htmldocs/smbclient.1.html b/docs/htmldocs/smbclient.1.html
index 49f00fb2db..ca8cafd312 100644
--- a/docs/htmldocs/smbclient.1.html
+++ b/docs/htmldocs/smbclient.1.html
@@ -1,424 +1,1645 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>smbclient</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="smbclient.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>smbclient &#8212; ftp-like client to access SMB/CIFS resources
- on servers</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><tt>smbclient</tt> {servicename} [password] [-b &lt;buffer size&gt;] [-d debuglevel] [-D Directory] [-U username] [-W workgroup] [-M &lt;netbios name&gt;] [-m maxprotocol] [-A authfile] [-N] [-l logfile] [-L &lt;netbios name&gt;] [-I destinationIP] [-E] [-c &lt;command string&gt;] [-i scope] [-O &lt;socket options&gt;] [-p port] [-R &lt;name resolve order&gt;] [-s &lt;smb config file&gt;] [-T&lt;c|x&gt;IXFqgbNan] [-k]</p></div></div><div class="refsect1" lang="en"><h2>DESCRIPTION</h2><p>This tool is part of the <a href="Samba.7.html">Samba(7)</a> suite.</p><p><b>smbclient</b> is a client that can
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<HTML
+><HEAD
+><TITLE
+>smbclient</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.77"></HEAD
+><BODY
+CLASS="REFENTRY"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><H1
+><A
+NAME="SMBCLIENT"
+></A
+>smbclient</H1
+><DIV
+CLASS="REFNAMEDIV"
+><A
+NAME="AEN5"
+></A
+><H2
+>Name</H2
+>smbclient&nbsp;--&nbsp;ftp-like client to access SMB/CIFS resources
+ on servers</DIV
+><DIV
+CLASS="REFSYNOPSISDIV"
+><A
+NAME="AEN8"
+></A
+><H2
+>Synopsis</H2
+><P
+><B
+CLASS="COMMAND"
+>smbclient</B
+> {servicename} [password] [-b &lt;buffer size&gt;] [-d debuglevel] [-D Directory] [-U username] [-W workgroup] [-M &lt;netbios name&gt;] [-m maxprotocol] [-A authfile] [-N] [-l logfile] [-L &lt;netbios name&gt;] [-I destinationIP] [-E] [-c &lt;command string&gt;] [-i scope] [-O &lt;socket options&gt;] [-p port] [-R &lt;name resolve order&gt;] [-s &lt;smb config file&gt;] [-T&lt;c|x&gt;IXFqgbNan]</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN33"
+></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"
+>smbclient</B
+> is a client that can
'talk' to an SMB/CIFS server. It offers an interface
- similar to that of the ftp program (see <a href="ftp.1.html">ftp(1)</a>).
+ similar to that of the ftp program (see <B
+CLASS="COMMAND"
+>ftp(1)</B
+>).
Operations include things like getting files from the server
to the local machine, putting files from the local machine to
the server, retrieving directory information from the server
- and so on. </p></div><div class="refsect1" lang="en"><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">servicename</span></dt><dd><p>servicename is the name of the service
+ and so on. </P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN40"
+></A
+><H2
+>OPTIONS</H2
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>servicename</DT
+><DD
+><P
+>servicename is the name of the service
you want to use on the server. A service name takes the form
- <tt>//server/service</tt> where <i><tt>server
- </tt></i> is the NetBIOS name of the SMB/CIFS server
- offering the desired service and <i><tt>service</tt></i>
+ <TT
+CLASS="FILENAME"
+>//server/service</TT
+> where <TT
+CLASS="PARAMETER"
+><I
+>server
+ </I
+></TT
+> is the NetBIOS name of the SMB/CIFS server
+ offering the desired service and <TT
+CLASS="PARAMETER"
+><I
+>service</I
+></TT
+>
is the name of the service offered. Thus to connect to
- the service &quot;printer&quot; on the SMB/CIFS server &quot;smbserver&quot;,
- you would use the servicename <tt>//smbserver/printer
- </tt></p><p>Note that the server name required is NOT necessarily
+ the service "printer" on the SMB/CIFS server "smbserver",
+ you would use the servicename <TT
+CLASS="FILENAME"
+>//smbserver/printer
+ </TT
+></P
+><P
+>Note that the server name required is NOT necessarily
the IP (DNS) host name of the server ! The name required is
a NetBIOS server name, which may or may not be the
same as the IP hostname of the machine running the server.
- </p><p>The server name is looked up according to either
- the <i><tt>-R</tt></i> parameter to <b>smbclient</b> or
- using the name resolve order parameter in
- the <a href="smb.conf.5.html">smb.conf(5)</a> file,
+ </P
+><P
+>The server name is looked up according to either
+ the <TT
+CLASS="PARAMETER"
+><I
+>-R</I
+></TT
+> parameter to <B
+CLASS="COMMAND"
+>smbclient</B
+> or
+ using the name resolve order parameter in the <TT
+CLASS="FILENAME"
+>smb.conf</TT
+> file,
allowing an administrator to change the order and methods
- by which server names are looked up. </p></dd><dt><span class="term">password</span></dt><dd><p>The password required to access the specified
+ by which server names are looked up. </P
+></DD
+><DT
+>password</DT
+><DD
+><P
+>The password required to access the specified
service on the specified server. If this parameter is
- supplied, the <i><tt>-N</tt></i> option (suppress
- password prompt) is assumed. </p><p>There is no default password. If no password is supplied
+ supplied, the <TT
+CLASS="PARAMETER"
+><I
+>-N</I
+></TT
+> option (suppress
+ password prompt) is assumed. </P
+><P
+>There is no default password. If no password is supplied
on the command line (either by using this parameter or adding
- a password to the <i><tt>-U</tt></i> option (see
- below)) and the <i><tt>-N</tt></i> option is not
+ a password to the <TT
+CLASS="PARAMETER"
+><I
+>-U</I
+></TT
+> option (see
+ below)) and the <TT
+CLASS="PARAMETER"
+><I
+>-N</I
+></TT
+> option is not
specified, the client will prompt for a password, even if
the desired service does not require one. (If no password is
required, simply press ENTER to provide a null password.)
- </p><p>Note: Some servers (including OS/2 and Windows for
+ </P
+><P
+>Note: Some servers (including OS/2 and Windows for
Workgroups) insist on an uppercase password. Lowercase
or mixed case passwords may be rejected by these servers.
- </p><p>Be cautious about including passwords in scripts.
- </p></dd><dt><span class="term">-R &lt;name resolve order&gt;</span></dt><dd><p>This option is used by the programs in the Samba
+ </P
+><P
+>Be cautious about including passwords in scripts.
+ </P
+></DD
+><DT
+>-s smb.conf</DT
+><DD
+><P
+>Specifies the location of the all important
+ <TT
+CLASS="FILENAME"
+>smb.conf</TT
+> file. </P
+></DD
+><DT
+>-O socket options</DT
+><DD
+><P
+>TCP socket options to set on the client
+ socket. See the socket options parameter in the <TT
+CLASS="FILENAME"
+> smb.conf (5)</TT
+> manpage for the list of valid
+ options. </P
+></DD
+><DT
+>-R &lt;name resolve order&gt;</DT
+><DD
+><P
+>This option is used by the programs in the Samba
suite to determine what naming services and in what order to resolve
host names to IP addresses. The option takes a space-separated
- string of different name resolution options.</p><p>The options are :&quot;lmhosts&quot;, &quot;host&quot;, &quot;wins&quot; and &quot;bcast&quot;. They
- cause names to be resolved as follows:</p><div class="itemizedlist"><ul type="disc"><li><p><tt>lmhosts</tt>: Lookup an IP
+ string of different name resolution options.</P
+><P
+>The options are :"lmhosts", "host", "wins" and "bcast". They
+ cause names to be resolved as follows :</P
+><P
+></P
+><UL
+><LI
+><P
+><TT
+CLASS="CONSTANT"
+>lmhosts</TT
+> : Lookup an IP
address in the Samba lmhosts file. If the line in lmhosts has
- no name type attached to the NetBIOS name (see
- the <a href="lmhosts.5.html">lmhosts(5)</a> for details) then
- any name type matches for lookup.</p></li><li><p><tt>host</tt>: Do a standard host
- name to IP address resolution, using the system <tt>/etc/hosts
- </tt>, NIS, or DNS lookups. This method of name resolution
+ no name type attached to the NetBIOS name (see the <A
+HREF="lmhosts.5.html"
+TARGET="_top"
+>lmhosts(5)</A
+> for details) then
+ any name type matches for lookup.</P
+></LI
+><LI
+><P
+><TT
+CLASS="CONSTANT"
+>host</TT
+> : Do a standard host
+ name to IP address resolution, using the system <TT
+CLASS="FILENAME"
+>/etc/hosts
+ </TT
+>, NIS, or DNS lookups. This method of name resolution
is operating system dependent, for instance on IRIX or Solaris this
- may be controlled by the <tt>/etc/nsswitch.conf</tt>
+ may be controlled by the <TT
+CLASS="FILENAME"
+>/etc/nsswitch.conf</TT
+>
file). Note that this method is only used if the NetBIOS name
type being queried is the 0x20 (server) name type, otherwise
- it is ignored.</p></li><li><p><tt>wins</tt>: Query a name with
- the IP address listed in the <i><tt>wins server</tt></i>
+ it is ignored.</P
+></LI
+><LI
+><P
+><TT
+CLASS="CONSTANT"
+>wins</TT
+> : Query a name with
+ the IP address listed in the <TT
+CLASS="PARAMETER"
+><I
+>wins server</I
+></TT
+>
parameter. If no WINS server has
- been specified this method will be ignored.</p></li><li><p><tt>bcast</tt>: Do a broadcast on
+ been specified this method will be ignored.</P
+></LI
+><LI
+><P
+><TT
+CLASS="CONSTANT"
+>bcast</TT
+> : Do a broadcast on
each of the known local interfaces listed in the
- <i><tt>interfaces</tt></i>
+ <TT
+CLASS="PARAMETER"
+><I
+>interfaces</I
+></TT
+>
parameter. This is the least reliable of the name resolution
methods as it depends on the target host being on a locally
- connected subnet.</p></li></ul></div><p>If this parameter is not set then the name resolve order
- defined in the <a href="smb.conf.5.html">smb.conf(5)</a> file parameter
- (name resolve order) will be used. </p><p>The default order is lmhosts, host, wins, bcast and without
- this parameter or any entry in the <i><tt>name resolve order
- </tt></i> parameter of the <a href="smb.conf.5.html">smb.conf(5)</a> file the name resolution
- methods will be attempted in this order. </p></dd><dt><span class="term">-M NetBIOS name</span></dt><dd><p>This options allows you to send messages, using
- the &quot;WinPopup&quot; protocol, to another computer. Once a connection is
+ connected subnet.</P
+></LI
+></UL
+><P
+>If this parameter is not set then the name resolve order
+ defined in the <TT
+CLASS="FILENAME"
+>smb.conf</TT
+> file parameter
+ (name resolve order) will be used. </P
+><P
+>The default order is lmhosts, host, wins, bcast and without
+ this parameter or any entry in the <TT
+CLASS="PARAMETER"
+><I
+>name resolve order
+ </I
+></TT
+> parameter of the <TT
+CLASS="FILENAME"
+>smb.conf</TT
+> file the name resolution
+ methods will be attempted in this order. </P
+></DD
+><DT
+>-M NetBIOS name</DT
+><DD
+><P
+>This options allows you to send messages, using
+ the "WinPopup" protocol, to another computer. Once a connection is
established you then type your message, pressing ^D (control-D) to
- end. </p><p>If the receiving computer is running WinPopup the user will
+ end. </P
+><P
+>If the receiving computer is running WinPopup the user will
receive the message and probably a beep. If they are not running
WinPopup the message will be lost, and no error message will
- occur. </p><p>The message is also automatically truncated if the message
+ occur. </P
+><P
+>The message is also automatically truncated if the message
is over 1600 bytes, as this is the limit of the protocol.
- </p><p>One useful trick is to cat the message through
- <b>smbclient</b>. For example: <b>
- cat mymessage.txt | smbclient -M FRED </b> will
- send the message in the file <tt>mymessage.txt</tt>
- to the machine FRED. </p><p>You may also find the <i><tt>-U</tt></i> and
- <i><tt>-I</tt></i> options useful, as they allow you to
- control the FROM and TO parts of the message. </p><p>See the <i><tt>message command</tt></i> parameter in the <a href="smb.conf.5.html">smb.conf(5)</a> for a description of how to handle incoming
- WinPopup messages in Samba. </p><p><span class="emphasis"><em>Note</em></span>: Copy WinPopup into the startup group
+ </P
+><P
+>One useful trick is to cat the message through
+ <B
+CLASS="COMMAND"
+>smbclient</B
+>. For example: <B
+CLASS="COMMAND"
+> cat mymessage.txt | smbclient -M FRED </B
+> will
+ send the message in the file <TT
+CLASS="FILENAME"
+>mymessage.txt</TT
+>
+ to the machine FRED. </P
+><P
+>You may also find the <TT
+CLASS="PARAMETER"
+><I
+>-U</I
+></TT
+> and
+ <TT
+CLASS="PARAMETER"
+><I
+>-I</I
+></TT
+> options useful, as they allow you to
+ control the FROM and TO parts of the message. </P
+><P
+>See the message command parameter in the <TT
+CLASS="FILENAME"
+> smb.conf(5)</TT
+> for a description of how to handle incoming
+ WinPopup messages in Samba. </P
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Note</I
+></SPAN
+>: Copy WinPopup into the startup group
on your WfWg PCs if you want them to always be able to receive
- messages. </p></dd><dt><span class="term">-p port</span></dt><dd><p>This number is the TCP port number that will be used
+ messages. </P
+></DD
+><DT
+>-i scope</DT
+><DD
+><P
+>This specifies a NetBIOS scope that smbclient will
+ use to communicate with when generating NetBIOS names. For details
+ on the use of NetBIOS scopes, see <TT
+CLASS="FILENAME"
+>rfc1001.txt</TT
+>
+ and <TT
+CLASS="FILENAME"
+>rfc1002.txt</TT
+>.
+ NetBIOS scopes are <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>very</I
+></SPAN
+> rarely used, only set
+ this parameter if you are the system administrator in charge of all
+ the NetBIOS systems you communicate with. </P
+></DD
+><DT
+>-N</DT
+><DD
+><P
+>If specified, this parameter suppresses the normal
+ password prompt from the client to the user. This is useful when
+ accessing a service that does not require a password. </P
+><P
+>Unless a password is specified on the command line or
+ this parameter is specified, the client will request a
+ password.</P
+></DD
+><DT
+>-n NetBIOS name</DT
+><DD
+><P
+>By default, the client will use the local
+ machine's hostname (in uppercase) as its NetBIOS name. This parameter
+ allows you to override the host name and use whatever NetBIOS
+ name you wish. </P
+></DD
+><DT
+>-d debuglevel</DT
+><DD
+><P
+><TT
+CLASS="REPLACEABLE"
+><I
+>debuglevel</I
+></TT
+> is an integer from 0 to 10, or
+ the letter 'A'. </P
+><P
+>The default value if this parameter is not specified
+ is zero. </P
+><P
+>The higher this value, the more detail will be logged to
+ the log files about the activities of the
+ client. At level 0, only critical errors and serious warnings will
+ be logged. Level 1 is a reasonable level for day to day running -
+ it generates a small amount of information about operations
+ carried out. </P
+><P
+>Levels above 1 will generate considerable amounts of log
+ data, and should only be used when investigating a problem.
+ Levels above 3 are designed for use only by developers and
+ generate HUGE amounts of log data, most of which is extremely
+ cryptic. If <TT
+CLASS="REPLACEABLE"
+><I
+>debuglevel</I
+></TT
+> is set to the letter 'A', then <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>all
+ </I
+></SPAN
+> debug messages will be printed. This setting
+ is for developers only (and people who <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>really</I
+></SPAN
+> want
+ to know how the code works internally). </P
+><P
+>Note that specifying this parameter here will override
+ the log level parameter in the <TT
+CLASS="FILENAME"
+>smb.conf (5)</TT
+>
+ file. </P
+></DD
+><DT
+>-p port</DT
+><DD
+><P
+>This number is the TCP port number that will be used
when making connections to the server. The standard (well-known)
TCP port number for an SMB/CIFS server is 139, which is the
- default. </p></dd><dt><span class="term">-l logfilename</span></dt><dd><p>If specified, <i><tt>logfilename</tt></i> specifies a base filename
+ default. </P
+></DD
+><DT
+>-l logfilename</DT
+><DD
+><P
+>If specified, <TT
+CLASS="REPLACEABLE"
+><I
+>logfilename</I
+></TT
+> specifies a base filename
into which operational data from the running client will be
- logged. </p><p>The default base name is specified at compile time.</p><p>The base name is used to generate actual log file names.
- For example, if the name specified was &quot;log&quot;, the debug file
- would be <tt>log.client</tt>.</p><p>The log file generated is never removed by the client.
- </p></dd><dt><span class="term">-h|--help</span></dt><dd><p>Print a summary of command line options.
-</p></dd><dt><span class="term">-I IP-address</span></dt><dd><p><i><tt>IP address</tt></i> is the address of the server to connect to.
- It should be specified in standard &quot;a.b.c.d&quot; notation. </p><p>Normally the client would attempt to locate a named
+ logged. </P
+><P
+>The default base name is specified at compile time.</P
+><P
+>The base name is used to generate actual log file names.
+ For example, if the name specified was "log", the debug file
+ would be <TT
+CLASS="FILENAME"
+>log.client</TT
+>.</P
+><P
+>The log file generated is never removed by the client.
+ </P
+></DD
+><DT
+>-h</DT
+><DD
+><P
+>Print the usage message for the client. </P
+></DD
+><DT
+>-I IP-address</DT
+><DD
+><P
+><TT
+CLASS="REPLACEABLE"
+><I
+>IP address</I
+></TT
+> is the address of the server to connect to.
+ It should be specified in standard "a.b.c.d" notation. </P
+><P
+>Normally the client would attempt to locate a named
SMB/CIFS server by looking it up via the NetBIOS name resolution
- mechanism described above in the <i><tt>name resolve order</tt></i>
+ mechanism described above in the <TT
+CLASS="PARAMETER"
+><I
+>name resolve order</I
+></TT
+>
parameter above. Using this parameter will force the client
to assume that the server is on the machine with the specified IP
address and the NetBIOS name component of the resource being
- connected to will be ignored. </p><p>There is no default for this parameter. If not supplied,
+ connected to will be ignored. </P
+><P
+>There is no default for this parameter. If not supplied,
it will be determined automatically by the client as described
- above. </p></dd><dt><span class="term">-E</span></dt><dd><p>This parameter causes the client to write messages
+ above. </P
+></DD
+><DT
+>-E</DT
+><DD
+><P
+>This parameter causes the client to write messages
to the standard error stream (stderr) rather than to the standard
- output stream. </p><p>By default, the client writes messages to standard output
- - typically the user's tty. </p></dd><dt><span class="term">-L</span></dt><dd><p>This option allows you to look at what services
- are available on a server. You use it as <b>smbclient -L
- host</b> and a list should appear. The <i><tt>-I
- </tt></i> option may be useful if your NetBIOS names don't
+ output stream. </P
+><P
+>By default, the client writes messages to standard output
+ - typically the user's tty. </P
+></DD
+><DT
+>-U username[%pass]</DT
+><DD
+><P
+>Sets the SMB username or username and password.
+ If %pass is not specified, The user will be prompted. The client
+ will first check the <TT
+CLASS="ENVAR"
+>USER</TT
+> environment variable, then the
+ <TT
+CLASS="ENVAR"
+>LOGNAME</TT
+> variable and if either exists, the
+ string is uppercased. Anything in these variables following a '%'
+ sign will be treated as the password. If these environment
+ variables are not found, the username <TT
+CLASS="CONSTANT"
+>GUEST</TT
+>
+ is used. </P
+><P
+>If the password is not included in these environment
+ variables (using the %pass syntax), <B
+CLASS="COMMAND"
+>smbclient</B
+> will look for
+ a <TT
+CLASS="ENVAR"
+>PASSWD</TT
+> environment variable from which
+ to read the password. </P
+><P
+>A third option is to use a credentials file which
+ contains the plaintext of the domain name, username and password. This
+ option is mainly provided for scripts where the admin doesn't
+ wish to pass the credentials on the command line or via environment
+ variables. If this method is used, make certain that the permissions
+ on the file restrict access from unwanted users. See the
+ <TT
+CLASS="PARAMETER"
+><I
+>-A</I
+></TT
+> for more details. </P
+><P
+>Be cautious about including passwords in scripts or in
+ the <TT
+CLASS="ENVAR"
+>PASSWD</TT
+> environment variable. Also, on
+ many systems the command line of a running process may be seen
+ via the <B
+CLASS="COMMAND"
+>ps</B
+> command to be safe always allow
+ <B
+CLASS="COMMAND"
+>smbclient</B
+> to prompt for a password and type
+ it in directly. </P
+></DD
+><DT
+>-A filename</DT
+><DD
+><P
+>This option allows
+ you to specify a file from which to read the username, domain name, and
+ password used in the connection. The format of the file is
+ </P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>username = &lt;value&gt;
+password = &lt;value&gt;
+domain = &lt;value&gt;
+ </PRE
+></P
+><P
+>If the domain parameter is missing the current workgroup name
+ is used instead. Make certain that the permissions on the file restrict
+ access from unwanted users. </P
+></DD
+><DT
+>-L</DT
+><DD
+><P
+>This option allows you to look at what services
+ are available on a server. You use it as <B
+CLASS="COMMAND"
+>smbclient -L
+ host</B
+> and a list should appear. The <TT
+CLASS="PARAMETER"
+><I
+>-I
+ </I
+></TT
+> option may be useful if your NetBIOS names don't
match your TCP/IP DNS host names or if you are trying to reach a
- host on another network. </p></dd><dt><span class="term">-t terminal code</span></dt><dd><p>This option tells <b>smbclient</b> how to interpret
+ host on another network. </P
+></DD
+><DT
+>-t terminal code</DT
+><DD
+><P
+>This option tells <B
+CLASS="COMMAND"
+>smbclient</B
+> how to interpret
filenames coming from the remote server. Usually Asian language
multibyte UNIX implementations use different character sets than
- SMB/CIFS servers (<span class="emphasis"><em>EUC</em></span> instead of <span class="emphasis"><em>
- SJIS</em></span> for example). Setting this parameter will let
- <b>smbclient</b> convert between the UNIX filenames and
+ SMB/CIFS servers (<SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>EUC</I
+></SPAN
+> instead of <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+> SJIS</I
+></SPAN
+> for example). Setting this parameter will let
+ <B
+CLASS="COMMAND"
+>smbclient</B
+> convert between the UNIX filenames and
the SMB filenames correctly. This option has not been seriously tested
- and may have some problems. </p><p>The terminal codes include CWsjis, CWeuc, CWjis7, CWjis8,
+ and may have some problems. </P
+><P
+>The terminal codes include CWsjis, CWeuc, CWjis7, CWjis8,
CWjunet, CWhex, CWcap. This is not a complete list, check the Samba
- source code for the complete list. </p></dd><dt><span class="term">-b buffersize</span></dt><dd><p>This option changes the transmit/send buffer
+ source code for the complete list. </P
+></DD
+><DT
+>-b buffersize</DT
+><DD
+><P
+>This option changes the transmit/send buffer
size when getting or putting a file from/to the server. The default
is 65520 bytes. Setting this value smaller (to 1200 bytes) has been
observed to speed up file transfers to and from a Win9x server.
- </p></dd><dt><span class="term">-V</span></dt><dd><p>Prints the version number for
-<b>smbd</b>.</p></dd><dt><span class="term">-s &lt;configuration file&gt;</span></dt><dd><p>The file specified contains the
-configuration details required by the server. The
-information in this file includes server-specific
-information such as what printcap file to use, as well
-as descriptions of all the services that the server is
-to provide. See <a href="smb.conf.5.html" target="_top"><tt>
-smb.conf(5)</tt></a> for more information.
-The default configuration file name is determined at
-compile time.</p></dd><dt><span class="term">-d|--debug=debuglevel</span></dt><dd><p><i><tt>debuglevel</tt></i> is an integer
-from 0 to 10. The default value if this parameter is
-not specified is zero.</p><p>The higher this value, the more detail will be
-logged to the log files about the activities of the
-server. At level 0, only critical errors and serious
-warnings will be logged. Level 1 is a reasonable level for
-day to day running - it generates a small amount of
-information about operations carried out.</p><p>Levels above 1 will generate considerable
-amounts of log data, and should only be used when
-investigating a problem. Levels above 3 are designed for
-use only by developers and generate HUGE amounts of log
-data, most of which is extremely cryptic.</p><p>Note that specifying this parameter here will
-override the <a href="smb.conf.5.html#loglevel" target="_top">log
-level</a> parameter in the <a href="smb.conf.5.html" target="_top">
-<tt>smb.conf(5)</tt></a> file.</p></dd><dt><span class="term">-l|--logfile=logbasename</span></dt><dd><p>File name for log/debug files. The extension
-<tt>&quot;.client&quot;</tt> will be appended. The log file is
-never removed by the client.
-</p></dd><dt><span class="term">-N</span></dt><dd><p>If specified, this parameter suppresses the normal
-password prompt from the client to the user. This is useful when
-accessing a service that does not require a password. </p><p>Unless a password is specified on the command line or
-this parameter is specified, the client will request a
-password.</p></dd><dt><span class="term">-k</span></dt><dd><p>
-Try to authenticate with kerberos. Only useful in
-an Active Directory environment.
-</p></dd><dt><span class="term">-A|--authfile=filename</span></dt><dd><p>This option allows
-you to specify a file from which to read the username and
-password used in the connection. The format of the file is
-</p><pre class="programlisting">
-username = &lt;value&gt;
-password = &lt;value&gt;
-domain = &lt;value&gt;
-</pre><p>Make certain that the permissions on the file restrict
-access from unwanted users. </p></dd><dt><span class="term">-U|--user=username[%password]</span></dt><dd><p>Sets the SMB username or username and password. </p><p>If %password is not specified, the user will be prompted. The
-client will first check the <tt>USER</tt> environment variable, then the
-<tt>LOGNAME</tt> variable and if either exists, the
-string is uppercased. If these environmental variables are not
-found, the username <tt>GUEST</tt> is used. </p><p>A third option is to use a credentials file which
-contains the plaintext of the username and password. This
-option is mainly provided for scripts where the admin does not
-wish to pass the credentials on the command line or via environment
-variables. If this method is used, make certain that the permissions
-on the file restrict access from unwanted users. See the
-<i><tt>-A</tt></i> for more details. </p><p>Be cautious about including passwords in scripts. Also, on
-many systems the command line of a running process may be seen
-via the <b>ps</b> command. To be safe always allow
-<b>rpcclient</b> to prompt for a password and type
-it in directly. </p></dd><dt><span class="term">-n &lt;primary NetBIOS name&gt;</span></dt><dd><p>This option allows you to override
-the NetBIOS name that Samba uses for itself. This is identical
-to setting the <a href="smb.conf.5.html#netbiosname" target="_top"><i><tt>NetBIOS
-name</tt></i></a> parameter in the <a href="smb.conf.5.html">smb.conf(5)</a> file. However, a command
-line setting will take precedence over settings in
-<a href="smb.conf.5.html">smb.conf(5)</a>.</p></dd><dt><span class="term">-i &lt;scope&gt;</span></dt><dd><p>This specifies a NetBIOS scope that
-<b>nmblookup</b> will use to communicate with when
-generating NetBIOS names. For details on the use of NetBIOS
-scopes, see rfc1001.txt and rfc1002.txt. NetBIOS scopes are
-<span class="emphasis"><em>very</em></span> rarely used, only set this parameter
-if you are the system administrator in charge of all the
-NetBIOS systems you communicate with.</p></dd><dt><span class="term">-W|--workgroup=domain</span></dt><dd><p>Set the SMB domain of the username. This
-overrides the default domain which is the domain defined in
-smb.conf. If the domain specified is the same as the servers
-NetBIOS name, it causes the client to log on using the servers local
-SAM (as opposed to the Domain SAM). </p></dd><dt><span class="term">-O socket options</span></dt><dd><p>TCP socket options to set on the client
-socket. See the socket options parameter in
-the <a href="smb.conf.5.html">smb.conf(5)</a> manual page for the list of valid
-options. </p></dd><dt><span class="term">-T tar options</span></dt><dd><p>smbclient may be used to create <b>tar(1)
- </b> compatible backups of all the files on an SMB/CIFS
+ </P
+></DD
+><DT
+>-W WORKGROUP</DT
+><DD
+><P
+>Override the default workgroup (domain) specified
+ in the workgroup parameter of the <TT
+CLASS="FILENAME"
+>smb.conf</TT
+>
+ file for this connection. This may be needed to connect to some
+ servers. </P
+></DD
+><DT
+>-T tar options</DT
+><DD
+><P
+>smbclient may be used to create <B
+CLASS="COMMAND"
+>tar(1)
+ </B
+> compatible backups of all the files on an SMB/CIFS
share. The secondary tar flags that can be given to this option
- are : </p><div class="itemizedlist"><ul type="disc"><li><p><i><tt>c</tt></i> - Create a tar file on UNIX.
+ are : </P
+><P
+></P
+><UL
+><LI
+><P
+><TT
+CLASS="PARAMETER"
+><I
+>c</I
+></TT
+> - Create a tar file on UNIX.
Must be followed by the name of a tar file, tape device
- or &quot;-&quot; for standard output. If using standard output you must
+ or "-" for standard output. If using standard output you must
turn the log level to its lowest value -d0 to avoid corrupting
your tar file. This flag is mutually exclusive with the
- <i><tt>x</tt></i> flag. </p></li><li><p><i><tt>x</tt></i> - Extract (restore) a local
+ <TT
+CLASS="PARAMETER"
+><I
+>x</I
+></TT
+> flag. </P
+></LI
+><LI
+><P
+><TT
+CLASS="PARAMETER"
+><I
+>x</I
+></TT
+> - Extract (restore) a local
tar file back to a share. Unless the -D option is given, the tar
files will be restored from the top level of the share. Must be
- followed by the name of the tar file, device or &quot;-&quot; for standard
- input. Mutually exclusive with the <i><tt>c</tt></i> flag.
+ followed by the name of the tar file, device or "-" for standard
+ input. Mutually exclusive with the <TT
+CLASS="PARAMETER"
+><I
+>c</I
+></TT
+> flag.
Restored files have their creation times (mtime) set to the
date saved in the tar file. Directories currently do not get
- their creation dates restored properly. </p></li><li><p><i><tt>I</tt></i> - Include files and directories.
+ their creation dates restored properly. </P
+></LI
+><LI
+><P
+><TT
+CLASS="PARAMETER"
+><I
+>I</I
+></TT
+> - Include files and directories.
Is the default behavior when filenames are specified above. Causes
tar files to be included in an extract or create (and therefore
everything else to be excluded). See example below. Filename globbing
- works in one of two ways. See r below. </p></li><li><p><i><tt>X</tt></i> - Exclude files and directories.
+ works in one of two ways. See r below. </P
+></LI
+><LI
+><P
+><TT
+CLASS="PARAMETER"
+><I
+>X</I
+></TT
+> - Exclude files and directories.
Causes tar files to be excluded from an extract or create. See
example below. Filename globbing works in one of two ways now.
- See <i><tt>r</tt></i> below. </p></li><li><p><i><tt>b</tt></i> - Blocksize. Must be followed
+ See <TT
+CLASS="PARAMETER"
+><I
+>r</I
+></TT
+> below. </P
+></LI
+><LI
+><P
+><TT
+CLASS="PARAMETER"
+><I
+>b</I
+></TT
+> - Blocksize. Must be followed
by a valid (greater than zero) blocksize. Causes tar file to be
written out in blocksize*TBLOCK (usually 512 byte) blocks.
- </p></li><li><p><i><tt>g</tt></i> - Incremental. Only back up
+ </P
+></LI
+><LI
+><P
+><TT
+CLASS="PARAMETER"
+><I
+>g</I
+></TT
+> - Incremental. Only back up
files that have the archive bit set. Useful only with the
- <i><tt>c</tt></i> flag. </p></li><li><p><i><tt>q</tt></i> - Quiet. Keeps tar from printing
+ <TT
+CLASS="PARAMETER"
+><I
+>c</I
+></TT
+> flag. </P
+></LI
+><LI
+><P
+><TT
+CLASS="PARAMETER"
+><I
+>q</I
+></TT
+> - Quiet. Keeps tar from printing
diagnostics as it works. This is the same as tarmode quiet.
- </p></li><li><p><i><tt>r</tt></i> - Regular expression include
+ </P
+></LI
+><LI
+><P
+><TT
+CLASS="PARAMETER"
+><I
+>r</I
+></TT
+> - Regular expression include
or exclude. Uses regular expression matching for
excluding or excluding files if compiled with HAVE_REGEX_H.
However this mode can be very slow. If not compiled with
HAVE_REGEX_H, does a limited wildcard match on '*' and '?'.
- </p></li><li><p><i><tt>N</tt></i> - Newer than. Must be followed
+ </P
+></LI
+><LI
+><P
+><TT
+CLASS="PARAMETER"
+><I
+>N</I
+></TT
+> - Newer than. Must be followed
by the name of a file whose date is compared against files found
on the share during a create. Only files newer than the file
specified are backed up to the tar file. Useful only with the
- <i><tt>c</tt></i> flag. </p></li><li><p><i><tt>a</tt></i> - Set archive bit. Causes the
+ <TT
+CLASS="PARAMETER"
+><I
+>c</I
+></TT
+> flag. </P
+></LI
+><LI
+><P
+><TT
+CLASS="PARAMETER"
+><I
+>a</I
+></TT
+> - Set archive bit. Causes the
archive bit to be reset when a file is backed up. Useful with the
- <i><tt>g</tt></i> and <i><tt>c</tt></i> flags.
- </p></li></ul></div><p><span class="emphasis"><em>Tar Long File Names</em></span></p><p><b>smbclient</b>'s tar option now supports long
+ <TT
+CLASS="PARAMETER"
+><I
+>g</I
+></TT
+> and <TT
+CLASS="PARAMETER"
+><I
+>c</I
+></TT
+> flags.
+ </P
+></LI
+></UL
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Tar Long File Names</I
+></SPAN
+></P
+><P
+><B
+CLASS="COMMAND"
+>smbclient</B
+>'s tar option now supports long
file names both on backup and restore. However, the full path
name of the file must be less than 1024 bytes. Also, when
- a tar archive is created, <b>smbclient</b>'s tar option places all
+ a tar archive is created, <B
+CLASS="COMMAND"
+>smbclient</B
+>'s tar option places all
files in the archive with relative names, not absolute names.
- </p><p><span class="emphasis"><em>Tar Filenames</em></span></p><p>All file names can be given as DOS path names (with '\\'
+ </P
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Tar Filenames</I
+></SPAN
+></P
+><P
+>All file names can be given as DOS path names (with '\'
as the component separator) or as UNIX path names (with '/' as
- the component separator). </p><p><span class="emphasis"><em>Examples</em></span></p><p>Restore from tar file <tt>backup.tar</tt> into myshare on mypc
- (no password on share). </p><p><b>smbclient //mypc/yshare &quot;&quot; -N -Tx backup.tar
- </b></p><p>Restore everything except <tt>users/docs</tt>
- </p><p><b>smbclient //mypc/myshare &quot;&quot; -N -TXx backup.tar
- users/docs</b></p><p>Create a tar file of the files beneath <tt>
- users/docs</tt>. </p><p><b>smbclient //mypc/myshare &quot;&quot; -N -Tc
- backup.tar users/docs </b></p><p>Create the same tar file as above, but now use
- a DOS path name. </p><p><b>smbclient //mypc/myshare &quot;&quot; -N -tc backup.tar
- users\edocs </b></p><p>Create a tar file of all the files and directories in
- the share. </p><p><b>smbclient //mypc/myshare &quot;&quot; -N -Tc backup.tar *
- </b></p></dd><dt><span class="term">-D initial directory</span></dt><dd><p>Change to initial directory before starting. Probably
- only of any use with the tar -T option. </p></dd><dt><span class="term">-c command string</span></dt><dd><p>command string is a semicolon-separated list of
- commands to be executed instead of prompting from stdin. <i><tt>
- -N</tt></i> is implied by <i><tt>-c</tt></i>.</p><p>This is particularly useful in scripts and for printing stdin
- to the server, e.g. <b>-c 'print -'</b>. </p></dd></dl></div></div><div class="refsect1" lang="en"><h2>OPERATIONS</h2><p>Once the client is running, the user is presented with
- a prompt : </p><p><tt>smb:\&gt; </tt></p><p>The backslash (&quot;\\&quot;) indicates the current working directory
+ the component separator). </P
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Examples</I
+></SPAN
+></P
+><P
+>Restore from tar file <TT
+CLASS="FILENAME"
+>backup.tar</TT
+> into myshare on mypc
+ (no password on share). </P
+><P
+><B
+CLASS="COMMAND"
+>smbclient //mypc/yshare "" -N -Tx backup.tar
+ </B
+></P
+><P
+>Restore everything except <TT
+CLASS="FILENAME"
+>users/docs</TT
+>
+ </P
+><P
+><B
+CLASS="COMMAND"
+>smbclient //mypc/myshare "" -N -TXx backup.tar
+ users/docs</B
+></P
+><P
+>Create a tar file of the files beneath <TT
+CLASS="FILENAME"
+> users/docs</TT
+>. </P
+><P
+><B
+CLASS="COMMAND"
+>smbclient //mypc/myshare "" -N -Tc
+ backup.tar users/docs </B
+></P
+><P
+>Create the same tar file as above, but now use
+ a DOS path name. </P
+><P
+><B
+CLASS="COMMAND"
+>smbclient //mypc/myshare "" -N -tc backup.tar
+ users\edocs </B
+></P
+><P
+>Create a tar file of all the files and directories in
+ the share. </P
+><P
+><B
+CLASS="COMMAND"
+>smbclient //mypc/myshare "" -N -Tc backup.tar *
+ </B
+></P
+></DD
+><DT
+>-D initial directory</DT
+><DD
+><P
+>Change to initial directory before starting. Probably
+ only of any use with the tar -T option. </P
+></DD
+><DT
+>-c command string</DT
+><DD
+><P
+>command string is a semicolon-separated list of
+ commands to be executed instead of prompting from stdin. <TT
+CLASS="PARAMETER"
+><I
+> -N</I
+></TT
+> is implied by <TT
+CLASS="PARAMETER"
+><I
+>-c</I
+></TT
+>.</P
+><P
+>This is particularly useful in scripts and for printing stdin
+ to the server, e.g. <B
+CLASS="COMMAND"
+>-c 'print -'</B
+>. </P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN310"
+></A
+><H2
+>OPERATIONS</H2
+><P
+>Once the client is running, the user is presented with
+ a prompt : </P
+><P
+><TT
+CLASS="PROMPT"
+>smb:\&gt; </TT
+></P
+><P
+>The backslash ("\") indicates the current working directory
on the server, and will change if the current working directory
- is changed. </p><p>The prompt indicates that the client is ready and waiting to
+ is changed. </P
+><P
+>The prompt indicates that the client is ready and waiting to
carry out a user command. Each command is a single word, optionally
followed by parameters specific to that command. Command and parameters
are space-delimited unless these notes specifically
state otherwise. All commands are case-insensitive. Parameters to
commands may or may not be case sensitive, depending on the command.
- </p><p>You can specify file names which have spaces in them by quoting
- the name with double quotes, for example &quot;a long file name&quot;. </p><p>Parameters shown in square brackets (e.g., &quot;[parameter]&quot;) are
+ </P
+><P
+>You can specify file names which have spaces in them by quoting
+ the name with double quotes, for example "a long file name". </P
+><P
+>Parameters shown in square brackets (e.g., "[parameter]") are
optional. If not given, the command will use suitable defaults. Parameters
- shown in angle brackets (e.g., &quot;&lt;parameter&gt;&quot;) are required.
- </p><p>Note that all commands operating on the server are actually
+ shown in angle brackets (e.g., "&lt;parameter&gt;") are required.
+ </P
+><P
+>Note that all commands operating on the server are actually
performed by issuing a request to the server. Thus the behavior may
vary from server to server, depending on how the server was implemented.
- </p><p>The commands available are given here in alphabetical order. </p><div class="variablelist"><dl><dt><span class="term">? [command]</span></dt><dd><p>If <i><tt>command</tt></i> is specified, the ? command will display
+ </P
+><P
+>The commands available are given here in alphabetical order. </P
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>? [command]</DT
+><DD
+><P
+>If <TT
+CLASS="REPLACEABLE"
+><I
+>command</I
+></TT
+> is specified, the ? command will display
a brief informative message about the specified command. If no
command is specified, a list of available commands will
- be displayed. </p></dd><dt><span class="term">! [shell command]</span></dt><dd><p>If <i><tt>shell command</tt></i> is specified, the !
+ be displayed. </P
+></DD
+><DT
+>! [shell command]</DT
+><DD
+><P
+>If <TT
+CLASS="REPLACEABLE"
+><I
+>shell command</I
+></TT
+> is specified, the !
command will execute a shell locally and run the specified shell
command. If no command is specified, a local shell will be run.
- </p></dd><dt><span class="term">altname file</span></dt><dd><p>The client will request that the server return
- the &quot;alternate&quot; name (the 8.3 name) for a file or directory.
- </p></dd><dt><span class="term">cancel jobid0 [jobid1] ... [jobidN]</span></dt><dd><p>The client will request that the server cancel
+ </P
+></DD
+><DT
+>altname file</DT
+><DD
+><P
+>The client will request that the server return
+ the "alternate" name (the 8.3 name) for a file or directory.
+ </P
+></DD
+><DT
+>cancel jobid0 [jobid1] ... [jobidN]</DT
+><DD
+><P
+>The client will request that the server cancel
the printjobs identified by the given numeric print job ids.
- </p></dd><dt><span class="term">chmod file mode in octal</span></dt><dd><p>This command depends on the server supporting the CIFS
+ </P
+></DD
+><DT
+>chmod file mode in octal</DT
+><DD
+><P
+>This command depends on the server supporting the CIFS
UNIX extensions and will fail if the server does not. The client requests that the server
change the UNIX permissions to the given octal mode, in standard UNIX format.
- </p></dd><dt><span class="term">chown file uid gid</span></dt><dd><p>This command depends on the server supporting the CIFS
+ </P
+></DD
+><DT
+>chown file uid gid</DT
+><DD
+><P
+>This command depends on the server supporting the CIFS
UNIX extensions and will fail if the server does not. The client requests that the server
change the UNIX user and group ownership to the given decimal values. Note there is
currently no way to remotely look up the UNIX uid and gid values for a given name.
This may be addressed in future versions of the CIFS UNIX extensions.
- </p></dd><dt><span class="term">cd [directory name]</span></dt><dd><p>If &quot;directory name&quot; is specified, the current
+ </P
+></DD
+><DT
+>cd [directory name]</DT
+><DD
+><P
+>If "directory name" is specified, the current
working directory on the server will be changed to the directory
specified. This operation will fail if for any reason the specified
- directory is inaccessible. </p><p>If no directory name is specified, the current working
- directory on the server will be reported. </p></dd><dt><span class="term">del &lt;mask&gt;</span></dt><dd><p>The client will request that the server attempt
- to delete all files matching <i><tt>mask</tt></i> from the current working
- directory on the server. </p></dd><dt><span class="term">dir &lt;mask&gt;</span></dt><dd><p>A list of the files matching <i><tt>mask</tt></i> in the current
+ directory is inaccessible. </P
+><P
+>If no directory name is specified, the current working
+ directory on the server will be reported. </P
+></DD
+><DT
+>del &lt;mask&gt;</DT
+><DD
+><P
+>The client will request that the server attempt
+ to delete all files matching <TT
+CLASS="REPLACEABLE"
+><I
+>mask</I
+></TT
+> from the current working
+ directory on the server. </P
+></DD
+><DT
+>dir &lt;mask&gt;</DT
+><DD
+><P
+>A list of the files matching <TT
+CLASS="REPLACEABLE"
+><I
+>mask</I
+></TT
+> in the current
working directory on the server will be retrieved from the server
- and displayed. </p></dd><dt><span class="term">exit</span></dt><dd><p>Terminate the connection with the server and exit
- from the program. </p></dd><dt><span class="term">get &lt;remote file name&gt; [local file name]</span></dt><dd><p>Copy the file called <tt>remote file name</tt> from
+ and displayed. </P
+></DD
+><DT
+>exit</DT
+><DD
+><P
+>Terminate the connection with the server and exit
+ from the program. </P
+></DD
+><DT
+>get &lt;remote file name&gt; [local file name]</DT
+><DD
+><P
+>Copy the file called <TT
+CLASS="FILENAME"
+>remote file name</TT
+> from
the server to the machine running the client. If specified, name
- the local copy <tt>local file name</tt>. Note that all transfers in
- <b>smbclient</b> are binary. See also the
- lowercase command. </p></dd><dt><span class="term">help [command]</span></dt><dd><p>See the ? command above. </p></dd><dt><span class="term">lcd [directory name]</span></dt><dd><p>If <i><tt>directory name</tt></i> is specified, the current
+ the local copy <TT
+CLASS="FILENAME"
+>local file name</TT
+>. Note that all transfers in
+ <B
+CLASS="COMMAND"
+>smbclient</B
+> are binary. See also the
+ lowercase command. </P
+></DD
+><DT
+>help [command]</DT
+><DD
+><P
+>See the ? command above. </P
+></DD
+><DT
+>lcd [directory name]</DT
+><DD
+><P
+>If <TT
+CLASS="REPLACEABLE"
+><I
+>directory name</I
+></TT
+> is specified, the current
working directory on the local machine will be changed to
the directory specified. This operation will fail if for any
- reason the specified directory is inaccessible. </p><p>If no directory name is specified, the name of the
+ reason the specified directory is inaccessible. </P
+><P
+>If no directory name is specified, the name of the
current working directory on the local machine will be reported.
- </p></dd><dt><span class="term">link source destination</span></dt><dd><p>This command depends on the server supporting the CIFS
+ </P
+></DD
+><DT
+>link source destination</DT
+><DD
+><P
+>This command depends on the server supporting the CIFS
UNIX extensions and will fail if the server does not. The client requests that the server
create a hard link between the source and destination files. The source file
must not exist.
- </p></dd><dt><span class="term">lowercase</span></dt><dd><p>Toggle lowercasing of filenames for the get and
- mget commands. </p><p>When lowercasing is toggled ON, local filenames are converted
+ </P
+></DD
+><DT
+>lowercase</DT
+><DD
+><P
+>Toggle lowercasing of filenames for the get and
+ mget commands. </P
+><P
+>When lowercasing is toggled ON, local filenames are converted
to lowercase when using the get and mget commands. This is
often useful when copying (say) MSDOS files from a server, because
- lowercase filenames are the norm on UNIX systems. </p></dd><dt><span class="term">ls &lt;mask&gt;</span></dt><dd><p>See the dir command above. </p></dd><dt><span class="term">mask &lt;mask&gt;</span></dt><dd><p>This command allows the user to set up a mask
+ lowercase filenames are the norm on UNIX systems. </P
+></DD
+><DT
+>ls &lt;mask&gt;</DT
+><DD
+><P
+>See the dir command above. </P
+></DD
+><DT
+>mask &lt;mask&gt;</DT
+><DD
+><P
+>This command allows the user to set up a mask
which will be used during recursive operation of the mget and
- mput commands. </p><p>The masks specified to the mget and mput commands act as
+ mput commands. </P
+><P
+>The masks specified to the mget and mput commands act as
filters for directories rather than files when recursion is
- toggled ON. </p><p>The mask specified with the mask command is necessary
+ toggled ON. </P
+><P
+>The mask specified with the mask command is necessary
to filter files within those directories. For example, if the
- mask specified in an mget command is &quot;source*&quot; and the mask
- specified with the mask command is &quot;*.c&quot; and recursion is
+ mask specified in an mget command is "source*" and the mask
+ specified with the mask command is "*.c" and recursion is
toggled ON, the mget command will retrieve all files matching
- &quot;*.c&quot; in all directories below and including all directories
- matching &quot;source*&quot; in the current working directory. </p><p>Note that the value for mask defaults to blank (equivalent
- to &quot;*&quot;) and remains so until the mask command is used to change it.
+ "*.c" in all directories below and including all directories
+ matching "source*" in the current working directory. </P
+><P
+>Note that the value for mask defaults to blank (equivalent
+ to "*") and remains so until the mask command is used to change it.
It retains the most recently specified value indefinitely. To
avoid unexpected results it would be wise to change the value of
- mask back to &quot;*&quot; after using the mget or mput commands. </p></dd><dt><span class="term">md &lt;directory name&gt;</span></dt><dd><p>See the mkdir command. </p></dd><dt><span class="term">mget &lt;mask&gt;</span></dt><dd><p>Copy all files matching <i><tt>mask</tt></i> from the server to
- the machine running the client. </p><p>Note that <i><tt>mask</tt></i> is interpreted differently during recursive
+ mask back to "*" after using the mget or mput commands. </P
+></DD
+><DT
+>md &lt;directory name&gt;</DT
+><DD
+><P
+>See the mkdir command. </P
+></DD
+><DT
+>mget &lt;mask&gt;</DT
+><DD
+><P
+>Copy all files matching <TT
+CLASS="REPLACEABLE"
+><I
+>mask</I
+></TT
+> from the server to
+ the machine running the client. </P
+><P
+>Note that <TT
+CLASS="REPLACEABLE"
+><I
+>mask</I
+></TT
+> is interpreted differently during recursive
operation and non-recursive operation - refer to the recurse and
mask commands for more information. Note that all transfers in
- <b>smbclient</b> are binary. See also the lowercase command. </p></dd><dt><span class="term">mkdir &lt;directory name&gt;</span></dt><dd><p>Create a new directory on the server (user access
- privileges permitting) with the specified name. </p></dd><dt><span class="term">mput &lt;mask&gt;</span></dt><dd><p>Copy all files matching <i><tt>mask</tt></i> in the current working
+ <B
+CLASS="COMMAND"
+>smbclient</B
+> are binary. See also the lowercase command. </P
+></DD
+><DT
+>mkdir &lt;directory name&gt;</DT
+><DD
+><P
+>Create a new directory on the server (user access
+ privileges permitting) with the specified name. </P
+></DD
+><DT
+>mput &lt;mask&gt;</DT
+><DD
+><P
+>Copy all files matching <TT
+CLASS="REPLACEABLE"
+><I
+>mask</I
+></TT
+> in the current working
directory on the local machine to the current working directory on
- the server. </p><p>Note that <i><tt>mask</tt></i> is interpreted differently during recursive
+ the server. </P
+><P
+>Note that <TT
+CLASS="REPLACEABLE"
+><I
+>mask</I
+></TT
+> is interpreted differently during recursive
operation and non-recursive operation - refer to the recurse and mask
- commands for more information. Note that all transfers in <b>smbclient</b>
- are binary. </p></dd><dt><span class="term">print &lt;file name&gt;</span></dt><dd><p>Print the specified file from the local machine
- through a printable service on the server. </p><p>See also the printmode command.</p></dd><dt><span class="term">printmode &lt;graphics or text&gt;</span></dt><dd><p>Set the print mode to suit either binary data
+ commands for more information. Note that all transfers in <B
+CLASS="COMMAND"
+>smbclient</B
+>
+ are binary. </P
+></DD
+><DT
+>print &lt;file name&gt;</DT
+><DD
+><P
+>Print the specified file from the local machine
+ through a printable service on the server. </P
+><P
+>See also the printmode command.</P
+></DD
+><DT
+>printmode &lt;graphics or text&gt;</DT
+><DD
+><P
+>Set the print mode to suit either binary data
(such as graphical information) or text. Subsequent print
- commands will use the currently set print mode. </p></dd><dt><span class="term">prompt</span></dt><dd><p>Toggle prompting for filenames during operation
- of the mget and mput commands. </p><p>When toggled ON, the user will be prompted to confirm
+ commands will use the currently set print mode. </P
+></DD
+><DT
+>prompt</DT
+><DD
+><P
+>Toggle prompting for filenames during operation
+ of the mget and mput commands. </P
+><P
+>When toggled ON, the user will be prompted to confirm
the transfer of each file during these commands. When toggled
OFF, all specified files will be transferred without prompting.
- </p></dd><dt><span class="term">put &lt;local file name&gt; [remote file name]</span></dt><dd><p>Copy the file called <tt>local file name</tt> from the
+ </P
+></DD
+><DT
+>put &lt;local file name&gt; [remote file name]</DT
+><DD
+><P
+>Copy the file called <TT
+CLASS="FILENAME"
+>local file name</TT
+> from the
machine running the client to the server. If specified,
- name the remote copy <tt>remote file name</tt>. Note that all transfers
- in <b>smbclient</b> are binary. See also the lowercase command.
- </p></dd><dt><span class="term">queue</span></dt><dd><p>Displays the print queue, showing the job id,
- name, size and current status. </p></dd><dt><span class="term">quit</span></dt><dd><p>See the exit command. </p></dd><dt><span class="term">rd &lt;directory name&gt;</span></dt><dd><p>See the rmdir command. </p></dd><dt><span class="term">recurse</span></dt><dd><p>Toggle directory recursion for the commands mget
- and mput. </p><p>When toggled ON, these commands will process all directories
+ name the remote copy <TT
+CLASS="FILENAME"
+>remote file name</TT
+>. Note that all transfers
+ in <B
+CLASS="COMMAND"
+>smbclient</B
+> are binary. See also the lowercase command.
+ </P
+></DD
+><DT
+>queue</DT
+><DD
+><P
+>Displays the print queue, showing the job id,
+ name, size and current status. </P
+></DD
+><DT
+>quit</DT
+><DD
+><P
+>See the exit command. </P
+></DD
+><DT
+>rd &lt;directory name&gt;</DT
+><DD
+><P
+>See the rmdir command. </P
+></DD
+><DT
+>recurse</DT
+><DD
+><P
+>Toggle directory recursion for the commands mget
+ and mput. </P
+><P
+>When toggled ON, these commands will process all directories
in the source directory (i.e., the directory they are copying
from ) and will recurse into any that match the mask specified
to the command. Only files that match the mask specified using
the mask command will be retrieved. See also the mask command.
- </p><p>When recursion is toggled OFF, only files from the current
+ </P
+><P
+>When recursion is toggled OFF, only files from the current
working directory on the source machine that match the mask specified
to the mget or mput commands will be copied, and any mask specified
- using the mask command will be ignored. </p></dd><dt><span class="term">rm &lt;mask&gt;</span></dt><dd><p>Remove all files matching <i><tt>mask</tt></i> from the current
- working directory on the server. </p></dd><dt><span class="term">rmdir &lt;directory name&gt;</span></dt><dd><p>Remove the specified directory (user access
- privileges permitting) from the server. </p></dd><dt><span class="term">setmode &lt;filename&gt; &lt;perm=[+|\-]rsha&gt;</span></dt><dd><p>A version of the DOS attrib command to set
- file permissions. For example: </p><p><b>setmode myfile +r </b></p><p>would make myfile read only. </p></dd><dt><span class="term">symlink source destination</span></dt><dd><p>This command depends on the server supporting the CIFS
+ using the mask command will be ignored. </P
+></DD
+><DT
+>rm &lt;mask&gt;</DT
+><DD
+><P
+>Remove all files matching <TT
+CLASS="REPLACEABLE"
+><I
+>mask</I
+></TT
+> from the current
+ working directory on the server. </P
+></DD
+><DT
+>rmdir &lt;directory name&gt;</DT
+><DD
+><P
+>Remove the specified directory (user access
+ privileges permitting) from the server. </P
+></DD
+><DT
+>setmode &lt;filename&gt; &lt;perm=[+|\-]rsha&gt;</DT
+><DD
+><P
+>A version of the DOS attrib command to set
+ file permissions. For example: </P
+><P
+><B
+CLASS="COMMAND"
+>setmode myfile +r </B
+></P
+><P
+>would make myfile read only. </P
+></DD
+><DT
+>symlink source destination</DT
+><DD
+><P
+>This command depends on the server supporting the CIFS
UNIX extensions and will fail if the server does not. The client requests that the server
create a symbolic hard link between the source and destination files. The source file
must not exist. Note that the server will not create a link to any path that lies
outside the currently connected share. This is enforced by the Samba server.
- </p></dd><dt><span class="term">tar &lt;c|x&gt;[IXbgNa]</span></dt><dd><p>Performs a tar operation - see the <i><tt>-T
- </tt></i> command line option above. Behavior may be affected
+ </P
+></DD
+><DT
+>tar &lt;c|x&gt;[IXbgNa]</DT
+><DD
+><P
+>Performs a tar operation - see the <TT
+CLASS="PARAMETER"
+><I
+>-T
+ </I
+></TT
+> command line option above. Behavior may be affected
by the tarmode command (see below). Using g (incremental) and N
- (newer) will affect tarmode settings. Note that using the &quot;-&quot; option
+ (newer) will affect tarmode settings. Note that using the "-" option
with tar x may not work - use the command line option instead.
- </p></dd><dt><span class="term">blocksize &lt;blocksize&gt;</span></dt><dd><p>Blocksize. Must be followed by a valid (greater
+ </P
+></DD
+><DT
+>blocksize &lt;blocksize&gt;</DT
+><DD
+><P
+>Blocksize. Must be followed by a valid (greater
than zero) blocksize. Causes tar file to be written out in
- <i><tt>blocksize</tt></i>*TBLOCK (usually 512 byte) blocks. </p></dd><dt><span class="term">tarmode &lt;full|inc|reset|noreset&gt;</span></dt><dd><p>Changes tar's behavior with regard to archive
+ <TT
+CLASS="REPLACEABLE"
+><I
+>blocksize</I
+></TT
+>*TBLOCK (usually 512 byte) blocks. </P
+></DD
+><DT
+>tarmode &lt;full|inc|reset|noreset&gt;</DT
+><DD
+><P
+>Changes tar's behavior with regard to archive
bits. In full mode, tar will back up everything regardless of the
archive bit setting (this is the default mode). In incremental mode,
tar will only back up files with the archive bit set. In reset mode,
tar will reset the archive bit on all files it backs up (implies
- read/write share). </p></dd></dl></div></div><div class="refsect1" lang="en"><h2>NOTES</h2><p>Some servers are fussy about the case of supplied usernames,
+ read/write share). </P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN501"
+></A
+><H2
+>NOTES</H2
+><P
+>Some servers are fussy about the case of supplied usernames,
passwords, share names (AKA service names) and machine names.
If you fail to connect try giving all parameters in uppercase.
- </p><p>It is often necessary to use the -n option when connecting
+ </P
+><P
+>It is often necessary to use the -n option when connecting
to some types of servers. For example OS/2 LanManager insists
on a valid NetBIOS name being used, so you need to supply a valid
- name that would be known to the server.</p><p>smbclient supports long file names where the server
- supports the LANMAN2 protocol or above. </p></div><div class="refsect1" lang="en"><h2>ENVIRONMENT VARIABLES</h2><p>The variable <tt>USER</tt> may contain the
+ name that would be known to the server.</P
+><P
+>smbclient supports long file names where the server
+ supports the LANMAN2 protocol or above. </P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN506"
+></A
+><H2
+>ENVIRONMENT VARIABLES</H2
+><P
+>The variable <TT
+CLASS="ENVAR"
+>USER</TT
+> may contain the
username of the person using the client. This information is
used only if the protocol level is high enough to support
- session-level passwords.</p><p>The variable <tt>PASSWD</tt> may contain
+ session-level passwords.</P
+><P
+>The variable <TT
+CLASS="ENVAR"
+>PASSWD</TT
+> may contain
the password of the person using the client. This information is
used only if the protocol level is high enough to support
- session-level passwords. </p><p>The variable <tt>LIBSMB_PROG</tt> may contain
+ session-level passwords. </P
+><P
+>The variable <TT
+CLASS="ENVAR"
+>LIBSMB_PROG</TT
+> may contain
the path, executed with system(), which the client should connect
to instead of connecting to a server. This functionality is primarily
intended as a development aid, and works best when using a LMHOSTS
- file</p></div><div class="refsect1" lang="en"><h2>INSTALLATION</h2><p>The location of the client program is a matter for
+ file</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN514"
+></A
+><H2
+>INSTALLATION</H2
+><P
+>The location of the client program is a matter for
individual system administrators. The following are thus
- suggestions only. </p><p>It is recommended that the smbclient software be installed
- in the <tt>/usr/local/samba/bin/</tt> or <tt>
- /usr/samba/bin/</tt> directory, this directory readable
+ suggestions only. </P
+><P
+>It is recommended that the smbclient software be installed
+ in the <TT
+CLASS="FILENAME"
+>/usr/local/samba/bin/</TT
+> or <TT
+CLASS="FILENAME"
+> /usr/samba/bin/</TT
+> directory, this directory readable
by all, writeable only by root. The client program itself should
- be executable by all. The client should <span class="emphasis"><em>NOT</em></span> be
- setuid or setgid! </p><p>The client log files should be put in a directory readable
- and writeable only by the user. </p><p>To test the client, you will need to know the name of a
- running SMB/CIFS server. It is possible to run <a href="smbd.8.html">smbd(8)</a> as an ordinary user - running that server as a daemon
+ be executable by all. The client should <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>NOT</I
+></SPAN
+> be
+ setuid or setgid! </P
+><P
+>The client log files should be put in a directory readable
+ and writeable only by the user. </P
+><P
+>To test the client, you will need to know the name of a
+ running SMB/CIFS server. It is possible to run <B
+CLASS="COMMAND"
+>smbd(8)
+ </B
+> as an ordinary user - running that server as a daemon
on a user-accessible port (typically any port number over 1024)
- would provide a suitable test server. </p></div><div class="refsect1" lang="en"><h2>DIAGNOSTICS</h2><p>Most diagnostics issued by the client are logged in a
+ would provide a suitable test server. </P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN524"
+></A
+><H2
+>DIAGNOSTICS</H2
+><P
+>Most diagnostics issued by the client are logged in a
specified log file. The log file name is specified at compile time,
- but may be overridden on the command line. </p><p>The number and nature of diagnostics available depends
+ but may be overridden on the command line. </P
+><P
+>The number and nature of diagnostics available depends
on the debug level used by the client. If you have problems,
- set the debug level to 3 and peruse the log files. </p></div><div class="refsect1" lang="en"><h2>VERSION</h2><p>This man page is correct for version 2.2 of the Samba suite.</p></div><div class="refsect1" lang="en"><h2>AUTHOR</h2><p>The original Samba software and related utilities
+ set the debug level to 3 and peruse the log files. </P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN528"
+></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="AEN531"
+></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.
+ to the way the Linux kernel is developed.</P
+><P
+>The original Samba man pages were written by Karl Auer.
The man page sources were converted to YODL format (another
- excellent piece of Open Source software, available at <a href="ftp://ftp.icce.rug.nl/pub/unix/" target="_top">
- ftp://ftp.icce.rug.nl/pub/unix/</a>) and updated for the Samba 2.0
+ excellent piece of Open Source software, available at
+ <A
+HREF="ftp://ftp.icce.rug.nl/pub/unix/"
+TARGET="_top"
+> ftp://ftp.icce.rug.nl/pub/unix/</A
+>) and updated for the Samba 2.0
release by Jeremy Allison. The conversion to DocBook for
- Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 for Samba 3.0
- was done by Alexander Bokovoy.</p></div></div></body></html>
+ Samba 2.2 was done by Gerald Carter</P
+></DIV
+></BODY
+></HTML
+> \ No newline at end of file
diff --git a/docs/htmldocs/smbcontrol.1.html b/docs/htmldocs/smbcontrol.1.html
index 6fa017fdb0..12662dcc04 100644
--- a/docs/htmldocs/smbcontrol.1.html
+++ b/docs/htmldocs/smbcontrol.1.html
@@ -1,71 +1,385 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>smbcontrol</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="smbcontrol.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>smbcontrol &#8212; send messages to smbd, nmbd or winbindd processes</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><tt>smbcontrol</tt> [-i] [-s]</p></div><div class="cmdsynopsis"><p><tt>smbcontrol</tt> [destination] [message-type] [parameter]</p></div></div><div class="refsect1" lang="en"><h2>DESCRIPTION</h2><p>This tool is part of the <a href="Samba.7.html">Samba(7)</a> suite.</p><p><b>smbcontrol</b> is a very small program, which
- sends messages to a <a href="smbd.8.html">smbd(8)</a>, a <a href="nmbd.8.html">nmbd(8)</a>, or a <a href="winbindd.8.html">winbindd(8)</a> daemon running on the system.</p></div><div class="refsect1" lang="en"><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-h|--help</span></dt><dd><p>Print a summary of command line options.
-</p></dd><dt><span class="term">-s &lt;configuration file&gt;</span></dt><dd><p>The file specified contains the
-configuration details required by the server. The
-information in this file includes server-specific
-information such as what printcap file to use, as well
-as descriptions of all the services that the server is
-to provide. See <a href="smb.conf.5.html" target="_top"><tt>
-smb.conf(5)</tt></a> for more information.
-The default configuration file name is determined at
-compile time.</p></dd><dt><span class="term">-i</span></dt><dd><p>Run interactively. Individual commands
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<HTML
+><HEAD
+><TITLE
+>smbcontrol</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.77"></HEAD
+><BODY
+CLASS="REFENTRY"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><H1
+><A
+NAME="SMBCONTROL"
+></A
+>smbcontrol</H1
+><DIV
+CLASS="REFNAMEDIV"
+><A
+NAME="AEN5"
+></A
+><H2
+>Name</H2
+>smbcontrol&nbsp;--&nbsp;send messages to smbd, nmbd or winbindd processes</DIV
+><DIV
+CLASS="REFSYNOPSISDIV"
+><A
+NAME="AEN8"
+></A
+><H2
+>Synopsis</H2
+><P
+><B
+CLASS="COMMAND"
+>smbcontrol</B
+> [-i]</P
+><P
+><B
+CLASS="COMMAND"
+>smbcontrol</B
+> [destination] [message-type] [parameter]</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN17"
+></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"
+>smbcontrol</B
+> is a very small program, which
+ sends messages to an <A
+HREF="smbd.8.html"
+TARGET="_top"
+>smbd(8)</A
+>,
+ an <A
+HREF="nmbd.8.html"
+TARGET="_top"
+>nmbd(8)</A
+>
+ or a <A
+HREF="winbindd.8.html"
+TARGET="_top"
+>winbindd(8)</A
+>
+ daemon running on the system.</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN26"
+></A
+><H2
+>OPTIONS</H2
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>-i</DT
+><DD
+><P
+>Run interactively. Individual commands
of the form destination message-type parameters can be entered
- on STDIN. An empty command line or a &quot;q&quot; will quit the
- program.</p></dd><dt><span class="term">destination</span></dt><dd><p>One of <i><tt>nmbd</tt></i>, <i><tt>smbd</tt></i> or a process ID.</p><p>The <i><tt>smbd</tt></i> destination causes the
- message to &quot;broadcast&quot; to all smbd daemons.</p><p>The <i><tt>nmbd</tt></i> destination causes the
+ on STDIN. An empty command line or a "q" will quit the
+ program.</P
+></DD
+><DT
+>destination</DT
+><DD
+><P
+>One of <TT
+CLASS="PARAMETER"
+><I
+>nmbd</I
+></TT
+>
+ <TT
+CLASS="PARAMETER"
+><I
+>smbd</I
+></TT
+> or a process ID.</P
+><P
+>The <TT
+CLASS="PARAMETER"
+><I
+>smbd</I
+></TT
+> destination causes the
+ message to "broadcast" to all smbd daemons.</P
+><P
+>The <TT
+CLASS="PARAMETER"
+><I
+>nmbd</I
+></TT
+> destination causes the
message to be sent to the nmbd daemon specified in the
- <tt>nmbd.pid</tt> file.</p><p>If a single process ID is given, the message is sent
- to only that process.</p></dd><dt><span class="term">message-type</span></dt><dd><p>Type of message to send. See
- the section <tt>MESSAGE-TYPES</tt> for details.
- </p></dd><dt><span class="term">parameters</span></dt><dd><p>any parameters required for the message-type</p></dd></dl></div></div><div class="refsect1" lang="en"><h2>MESSAGE-TYPES</h2><p>Available message types are:</p><div class="variablelist"><dl><dt><span class="term">close-share</span></dt><dd><p>Order smbd to close the client
- connections to the named share. Note that this doesn't affect client
- connections to any other shares. This message-type takes an argument of the
- share name for which client connections will be closed, or the
- &quot;*&quot; character which will close all currently open shares.
- This may be useful if you made changes to the access controls on the share.
- This message can only be sent to <tt>smbd</tt>.</p></dd><dt><span class="term">debug</span></dt><dd><p>Set debug level to the value specified by the
- parameter. This can be sent to any of the destinations.</p></dd><dt><span class="term">force-election</span></dt><dd><p>This message causes the <b>nmbd</b> daemon to
- force a new browse master election. </p></dd><dt><span class="term">ping</span></dt><dd><p>
- Send specified number of &quot;ping&quot; messages and
- wait for the same number of reply &quot;pong&quot; messages. This can be sent to
- any of the destinations.</p></dd><dt><span class="term">profile</span></dt><dd><p>Change profile settings of a daemon, based on the
- parameter. The parameter can be &quot;on&quot; to turn on profile stats
- collection, &quot;off&quot; to turn off profile stats collection, &quot;count&quot;
- to enable only collection of count stats (time stats are
- disabled), and &quot;flush&quot; to zero the current profile stats. This can
- be sent to any smbd or nmbd destinations.</p></dd><dt><span class="term">debuglevel</span></dt><dd><p>
- Request debuglevel of a certain daemon and write it to stdout. This
- can be sent to any of the destinations.</p></dd><dt><span class="term">profilelevel</span></dt><dd><p>
- Request profilelevel of a certain daemon and write it to stdout.
- This can be sent to any smbd or nmbd destinations.</p></dd><dt><span class="term">printnotify</span></dt><dd><p>
- Order smbd to send a printer notify message to any Windows NT clients
- connected to a printer. This message-type takes the following arguments:
- </p><div class="variablelist"><dl><dt><span class="term">queuepause printername</span></dt><dd><p>Send a queue pause change notify
- message to the printer specified.</p></dd><dt><span class="term">queueresume printername</span></dt><dd><p>Send a queue resume change notify
- message for the printer specified.</p></dd><dt><span class="term">jobpause printername unixjobid</span></dt><dd><p>Send a job pause change notify
- message for the printer and unix jobid
- specified.</p></dd><dt><span class="term">jobresume printername unixjobid</span></dt><dd><p>Send a job resume change notify
- message for the printer and unix jobid
- specified.</p></dd><dt><span class="term">jobdelete printername unixjobid</span></dt><dd><p>Send a job delete change notify
- message for the printer and unix jobid
- specified.</p></dd></dl></div><p>
- Note that this message only sends notification that an
- event has occured. It doesn't actually cause the
- event to happen.
- </p><p>This message can only be sent to <tt>smbd</tt>. </p></dd><dt><span class="term">samsync</span></dt><dd><p>Order smbd to synchronise sam database from PDC (being BDC). Can only be sent to <tt>smbd</tt>. </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>Not working at the moment</p></div></dd><dt><span class="term">samrepl</span></dt><dd><p>Send sam replication message, with specified serial. Can only be sent to <tt>smbd</tt>. Should not be used manually.</p></dd><dt><span class="term">dmalloc-mark</span></dt><dd><p>Set a mark for dmalloc. Can be sent to both smbd and nmbd. Only available if samba is built with dmalloc support. </p></dd><dt><span class="term">dmalloc-log-changed</span></dt><dd><p>
- Dump the pointers that have changed since the mark set by dmalloc-mark.
- Can be sent to both smbd and nmbd. Only available if samba is built with dmalloc support. </p></dd><dt><span class="term">shutdown</span></dt><dd><p>Shut down specified daemon. Can be sent to both smbd and nmbd.</p></dd><dt><span class="term">pool-usage</span></dt><dd><p>Print a human-readable description of all
- talloc(pool) memory usage by the specified daemon/process. Available
- for both smbd and nmbd.</p></dd><dt><span class="term">drvupgrade</span></dt><dd><p>Force clients of printers using specified driver
- to update their local version of the driver. Can only be
- sent to smbd.</p></dd></dl></div></div><div class="refsect1" lang="en"><h2>VERSION</h2><p>This man page is correct for version 3.0 of
- the Samba suite.</p></div><div class="refsect1" lang="en"><h2>SEE ALSO</h2><p><a href="nmbd.8.html">nmbd(8)</a> and <a href="smbd.8.html">smbd(8)</a>.</p></div><div class="refsect1" lang="en"><h2>AUTHOR</h2><p>The original Samba software and related utilities
+ <TT
+CLASS="FILENAME"
+>nmbd.pid</TT
+> file.</P
+><P
+>If a single process ID is given, the message is sent
+ to only that process.</P
+></DD
+><DT
+>message-type</DT
+><DD
+><P
+>One of: <TT
+CLASS="CONSTANT"
+>close-share</TT
+>,
+ <TT
+CLASS="CONSTANT"
+>debug</TT
+>,
+ <TT
+CLASS="CONSTANT"
+>force-election</TT
+>, <TT
+CLASS="CONSTANT"
+>ping
+ </TT
+>, <TT
+CLASS="CONSTANT"
+>profile</TT
+>, <TT
+CLASS="CONSTANT"
+> debuglevel</TT
+>, <TT
+CLASS="CONSTANT"
+>profilelevel</TT
+>,
+ or <TT
+CLASS="CONSTANT"
+>printnotify</TT
+>.</P
+><P
+>The <TT
+CLASS="CONSTANT"
+>close-share</TT
+> message-type sends a
+ message to smbd which will then close the client connections to
+ the named share. Note that this doesn't affect client connections
+ to any other shares. This message-type takes an argument of the
+ share name for which client connections will be closed, or the
+ "*" character which will close all currently open shares.
+ This may be useful if you made changes to the access controls on the share.
+ This message can only be sent to <TT
+CLASS="CONSTANT"
+>smbd</TT
+>.</P
+><P
+>The <TT
+CLASS="CONSTANT"
+>debug</TT
+> message-type allows
+ the debug level to be set to the value specified by the
+ parameter. This can be sent to any of the destinations.</P
+><P
+>The <TT
+CLASS="CONSTANT"
+>force-election</TT
+> message-type can only be
+ sent to the <TT
+CLASS="CONSTANT"
+>nmbd</TT
+> destination. This message
+ causes the <B
+CLASS="COMMAND"
+>nmbd</B
+> daemon to force a new browse
+ master election.</P
+><P
+>The <TT
+CLASS="CONSTANT"
+>ping</TT
+> message-type sends the
+ number of "ping" messages specified by the parameter and waits
+ for the same number of reply "pong" messages. This can be sent to
+ any of the destinations.</P
+><P
+>The <TT
+CLASS="CONSTANT"
+>profile</TT
+> message-type sends a
+ message to an smbd to change the profile settings based on the
+ parameter. The parameter can be "on" to turn on profile stats
+ collection, "off" to turn off profile stats collection, "count"
+ to enable only collection of count stats (time stats are
+ disabled), and "flush" to zero the current profile stats. This can
+ be sent to any smbd or nmbd destinations.</P
+><P
+>The <TT
+CLASS="CONSTANT"
+>debuglevel</TT
+> message-type sends
+ a "request debug level" message. The current debug level setting
+ is returned by a "debuglevel" message. This can be
+ sent to any of the destinations.</P
+><P
+>The <TT
+CLASS="CONSTANT"
+>profilelevel</TT
+> message-type sends
+ a "request profile level" message. The current profile level
+ setting is returned by a "profilelevel" message. This can be sent
+ to any smbd or nmbd destinations.</P
+><P
+>The <TT
+CLASS="CONSTANT"
+>printnotify</TT
+> message-type sends a
+ message to smbd which in turn sends a printer notify message to
+ any Windows NT clients connected to a printer. This message-type
+ takes the following arguments:
+
+ <P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>queuepause printername</DT
+><DD
+><P
+>Send a queue pause change notify
+ message to the printer specified.</P
+></DD
+><DT
+>queueresume printername</DT
+><DD
+><P
+>Send a queue resume change notify
+ message for the printer specified.</P
+></DD
+><DT
+>jobpause printername unixjobid</DT
+><DD
+><P
+>Send a job pause change notify
+ message for the printer and unix jobid
+ specified.</P
+></DD
+><DT
+>jobresume printername unixjobid</DT
+><DD
+><P
+>Send a job resume change notify
+ message for the printer and unix jobid
+ specified.</P
+></DD
+><DT
+>jobdelete printername unixjobid</DT
+><DD
+><P
+>Send a job delete change notify
+ message for the printer and unix jobid
+ specified.</P
+></DD
+></DL
+></DIV
+>
+
+ Note that this message only sends notification that an
+ event has occured. It doesn't actually cause the
+ event to happen.
+
+ This message can only be sent to <TT
+CLASS="CONSTANT"
+>smbd</TT
+>.
+ </P
+></DD
+><DT
+>parameters</DT
+><DD
+><P
+>any parameters required for the message-type</P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN102"
+></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="AEN105"
+></A
+><H2
+>SEE ALSO</H2
+><P
+><A
+HREF="nmbd.8.html"
+TARGET="_top"
+><B
+CLASS="COMMAND"
+>nmbd(8)</B
+></A
+>,
+ and <A
+HREF="smbd.8.html"
+TARGET="_top"
+><B
+CLASS="COMMAND"
+>smbd(8)</B
+></A
+>.
+ </P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN112"
+></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.
+ to the way the Linux kernel is developed.</P
+><P
+>The original Samba man pages were written by Karl Auer.
The man page sources were converted to YODL format (another
- excellent piece of Open Source software, available at <a href="ftp://ftp.icce.rug.nl/pub/unix/" target="_top">
- ftp://ftp.icce.rug.nl/pub/unix/</a>) and updated for the Samba 2.0
+ excellent piece of Open Source software, available at
+ <A
+HREF="ftp://ftp.icce.rug.nl/pub/unix/"
+TARGET="_top"
+> ftp://ftp.icce.rug.nl/pub/unix/</A
+>) and updated for the Samba 2.0
release by Jeremy Allison. The conversion to DocBook for
- Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 for
- Samba 3.0 was done by Alexander Bokovoy.</p></div></div></body></html>
+ Samba 2.2 was done by Gerald Carter</P
+></DIV
+></BODY
+></HTML
+> \ No newline at end of file
diff --git a/docs/htmldocs/smbd.8.html b/docs/htmldocs/smbd.8.html
index 2ae976c3e8..65f5f95b8d 100644
--- a/docs/htmldocs/smbd.8.html
+++ b/docs/htmldocs/smbd.8.html
@@ -1,183 +1,780 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>smbd</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="smbd.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>smbd &#8212; server to provide SMB/CIFS services to clients</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><tt>smbd</tt> [-D] [-F] [-S] [-i] [-h] [-V] [-b] [-d &lt;debug level&gt;] [-l &lt;log directory&gt;] [-p &lt;port number&gt;] [-O &lt;socket option&gt;] [-s &lt;configuration file&gt;]</p></div></div><div class="refsect1" lang="en"><h2>DESCRIPTION</h2><p>This program is part of the <a href="Samba.7.html">Samba(7)</a> suite.</p><p><b>smbd</b> is the server daemon that
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
+<HTML
+><HEAD
+><TITLE
+>smbd</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"></HEAD
+><BODY
+CLASS="REFENTRY"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><H1
+><A
+NAME="SMBD">smbd</H1
+><DIV
+CLASS="REFNAMEDIV"
+><A
+NAME="AEN5"
+></A
+><H2
+>Name</H2
+>smbd&nbsp;--&nbsp;server to provide SMB/CIFS services to clients</DIV
+><DIV
+CLASS="REFSYNOPSISDIV"
+><A
+NAME="AEN8"><H2
+>Synopsis</H2
+><P
+><B
+CLASS="COMMAND"
+>smbd</B
+> [-D] [-F] [-S] [-i] [-h] [-V] [-b] [-d &#60;debug level&#62;] [-l &#60;log directory&#62;] [-p &#60;port number&#62;] [-O &#60;socket option&#62;] [-s &#60;configuration file&#62;]</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN23"
+></A
+><H2
+>DESCRIPTION</H2
+><P
+>This program is part of the Samba suite.</P
+><P
+><B
+CLASS="COMMAND"
+>smbd</B
+> is the server daemon that
provides filesharing and printing services to Windows clients.
The server provides filespace and printer services to
clients using the SMB (or CIFS) protocol. This is compatible
with the LanManager protocol, and can service LanManager
clients. These include MSCLIENT 3.0 for DOS, Windows for
Workgroups, Windows 95/98/ME, Windows NT, Windows 2000,
- OS/2, DAVE for Macintosh, and smbfs for Linux.</p><p>An extensive description of the services that the
+ OS/2, DAVE for Macintosh, and smbfs for Linux.</P
+><P
+>An extensive description of the services that the
server can provide is given in the man page for the
configuration file controlling the attributes of those
- services (see <a href="smb.conf.5.html">smb.conf(5)</a>. This man page will not describe the
+ services (see <A
+HREF="smb.conf.5.html"
+TARGET="_top"
+><TT
+CLASS="FILENAME"
+>smb.conf(5)
+ </TT
+></A
+>. This man page will not describe the
services, but will concentrate on the administrative aspects
- of running the server.</p><p>Please note that there are significant security
- implications to running this server, and the <a href="smb.conf.5.html">smb.conf(5)</a> manual page should be regarded as mandatory reading before
- proceeding with installation.</p><p>A session is created whenever a client requests one.
+ of running the server.</P
+><P
+>Please note that there are significant security
+ implications to running this server, and the <A
+HREF="smb.conf.5.html"
+TARGET="_top"
+><TT
+CLASS="FILENAME"
+>smb.conf(5)</TT
+></A
+>
+ manpage should be regarded as mandatory reading before
+ proceeding with installation.</P
+><P
+>A session is created whenever a client requests one.
Each client gets a copy of the server for each session. This
copy then services all connections made by the client during
that session. When all connections from its client are closed,
- the copy of the server for that client terminates.</p><p>The configuration file, and any files that it includes,
+ the copy of the server for that client terminates.</P
+><P
+>The configuration file, and any files that it includes,
are automatically reloaded every minute, if they change. You
can force a reload by sending a SIGHUP to the server. Reloading
the configuration file will not affect connections to any service
that is already established. Either the user will have to
- disconnect from the service, or <b>smbd</b> killed and restarted.</p></div><div class="refsect1" lang="en"><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-D</span></dt><dd><p>If specified, this parameter causes
+ disconnect from the service, or <B
+CLASS="COMMAND"
+>smbd</B
+> killed and restarted.</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN37"
+></A
+><H2
+>OPTIONS</H2
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>-D</DT
+><DD
+><P
+>If specified, this parameter causes
the server to operate as a daemon. That is, it detaches
itself and runs in the background, fielding requests
on the appropriate port. Operating the server as a
- daemon is the recommended way of running <b>smbd</b> for
+ daemon is the recommended way of running <B
+CLASS="COMMAND"
+>smbd</B
+> for
servers that provide more than casual use file and
- print services. This switch is assumed if <b>smbd
- </b> is executed on the command line of a shell.
- </p></dd><dt><span class="term">-F</span></dt><dd><p>If specified, this parameter causes
- the main <b>smbd</b> process to not daemonize,
+ print services. This switch is assumed if <B
+CLASS="COMMAND"
+>smbd
+ </B
+> is executed on the command line of a shell.
+ </P
+></DD
+><DT
+>-F</DT
+><DD
+><P
+>If specified, this parameter causes
+ the main <B
+CLASS="COMMAND"
+>smbd</B
+> process to not daemonize,
i.e. double-fork and disassociate with the terminal.
Child processes are still created as normal to service
each connection request, but the main process does not
exit. This operation mode is suitable for running
- <b>smbd</b> under process supervisors such
- as <b>supervise</b> and <b>svscan</b>
- from Daniel J. Bernstein's <b>daemontools</b>
+ <B
+CLASS="COMMAND"
+>smbd</B
+> under process supervisors such
+ as <B
+CLASS="COMMAND"
+>supervise</B
+> and <B
+CLASS="COMMAND"
+>svscan</B
+>
+ from Daniel J. Bernstein's <B
+CLASS="COMMAND"
+>daemontools</B
+>
package, or the AIX process monitor.
- </p></dd><dt><span class="term">-S</span></dt><dd><p>If specified, this parameter causes
- <b>smbd</b> to log to standard output rather
- than a file.</p></dd><dt><span class="term">-i</span></dt><dd><p>If this parameter is specified it causes the
- server to run &quot;interactively&quot;, not as a daemon, even if the
+ </P
+></DD
+><DT
+>-S</DT
+><DD
+><P
+>If specified, this parameter causes
+ <B
+CLASS="COMMAND"
+>smbd</B
+> to log to standard output rather
+ than a file.</P
+></DD
+><DT
+>-i</DT
+><DD
+><P
+>If this parameter is specified it causes the
+ server to run "interactively", not as a daemon, even if the
server is executed on the command line of a shell. Setting this
parameter negates the implicit deamon mode when run from the
- command line. <b>smbd</b> also logs to standard
- output, as if the <b>-S</b> parameter had been
+ command line. <B
+CLASS="COMMAND"
+>smbd</B
+> also logs to standard
+ output, as if the <B
+CLASS="COMMAND"
+>-S</B
+> parameter had been
given.
- </p></dd><dt><span class="term">-V</span></dt><dd><p>Prints the version number for
-<b>smbd</b>.</p></dd><dt><span class="term">-s &lt;configuration file&gt;</span></dt><dd><p>The file specified contains the
-configuration details required by the server. The
-information in this file includes server-specific
-information such as what printcap file to use, as well
-as descriptions of all the services that the server is
-to provide. See <a href="smb.conf.5.html" target="_top"><tt>
-smb.conf(5)</tt></a> for more information.
-The default configuration file name is determined at
-compile time.</p></dd><dt><span class="term">-d|--debug=debuglevel</span></dt><dd><p><i><tt>debuglevel</tt></i> is an integer
-from 0 to 10. The default value if this parameter is
-not specified is zero.</p><p>The higher this value, the more detail will be
-logged to the log files about the activities of the
-server. At level 0, only critical errors and serious
-warnings will be logged. Level 1 is a reasonable level for
-day to day running - it generates a small amount of
-information about operations carried out.</p><p>Levels above 1 will generate considerable
-amounts of log data, and should only be used when
-investigating a problem. Levels above 3 are designed for
-use only by developers and generate HUGE amounts of log
-data, most of which is extremely cryptic.</p><p>Note that specifying this parameter here will
-override the <a href="smb.conf.5.html#loglevel" target="_top">log
-level</a> parameter in the <a href="smb.conf.5.html" target="_top">
-<tt>smb.conf(5)</tt></a> file.</p></dd><dt><span class="term">-l|--logfile=logbasename</span></dt><dd><p>File name for log/debug files. The extension
-<tt>&quot;.client&quot;</tt> will be appended. The log file is
-never removed by the client.
-</p></dd><dt><span class="term">-h|--help</span></dt><dd><p>Print a summary of command line options.
-</p></dd><dt><span class="term">-b</span></dt><dd><p>Prints information about how
- Samba was built.</p></dd><dt><span class="term">-l &lt;log directory&gt;</span></dt><dd><p>If specified,
- <i><tt>log directory</tt></i>
- specifies a log directory into which the &quot;log.smbd&quot; log
+ </P
+></DD
+><DT
+>-h</DT
+><DD
+><P
+>Prints the help information (usage)
+ for <B
+CLASS="COMMAND"
+>smbd</B
+>.</P
+></DD
+><DT
+>-V</DT
+><DD
+><P
+>Prints the version number for
+ <B
+CLASS="COMMAND"
+>smbd</B
+>.</P
+></DD
+><DT
+>-b</DT
+><DD
+><P
+>Prints information about how
+ Samba was built.</P
+></DD
+><DT
+>-d &#60;debug level&#62;</DT
+><DD
+><P
+><TT
+CLASS="REPLACEABLE"
+><I
+>debuglevel</I
+></TT
+> is an integer
+ from 0 to 10. The default value if this parameter is
+ not specified is zero.</P
+><P
+>The higher this value, the more detail will be
+ logged to the log files about the activities of the
+ server. At level 0, only critical errors and serious
+ warnings will be logged. Level 1 is a reasonable level for
+ day to day running - it generates a small amount of
+ information about operations carried out.</P
+><P
+>Levels above 1 will generate considerable
+ amounts of log data, and should only be used when
+ investigating a problem. Levels above 3 are designed for
+ use only by developers and generate HUGE amounts of log
+ data, most of which is extremely cryptic.</P
+><P
+>Note that specifying this parameter here will
+ override the <A
+HREF="smb.conf.5.html#loglevel"
+TARGET="_top"
+>log
+ level</A
+> parameter in the <A
+HREF="smb.conf.5.html"
+TARGET="_top"
+> <TT
+CLASS="FILENAME"
+>smb.conf(5)</TT
+></A
+> file.</P
+></DD
+><DT
+>-l &#60;log directory&#62;</DT
+><DD
+><P
+>If specified,
+ <TT
+CLASS="REPLACEABLE"
+><I
+>log directory</I
+></TT
+>
+ specifies a log directory into which the "log.smbd" log
file will be created for informational and debug
messages from the running server. The log
file generated is never removed by the server although
- its size may be controlled by the <a href="smb.conf.5.html#maxlogsize" target="_top"><i><tt>max log size</tt></i></a>
- option in the <a href="smb.conf.5.html">smb.conf(5)</a> file. <span class="emphasis"><em>Beware:</em></span>
- If the directory specified does not exist, <b>smbd</b>
+ its size may be controlled by the <A
+HREF="smb.conf.5.html#maxlogsize"
+TARGET="_top"
+>max log size</A
+>
+ option in the <A
+HREF="smb.conf.5.html"
+TARGET="_top"
+><TT
+CLASS="FILENAME"
+> smb.conf(5)</TT
+></A
+> file. <I
+CLASS="EMPHASIS"
+>Beware:</I
+>
+ If the directory specified does not exist, <B
+CLASS="COMMAND"
+>smbd</B
+>
will log to the default debug log location defined at compile time.
- </p><p>The default log directory is specified at
- compile time.</p></dd><dt><span class="term">-p &lt;port number&gt;</span></dt><dd><p><i><tt>port number</tt></i> is a positive integer
+ </P
+><P
+>The default log directory is specified at
+ compile time.</P
+></DD
+><DT
+>-O &#60;socket options&#62;</DT
+><DD
+><P
+>See the <A
+HREF="smb.conf.5.html#socketoptions"
+TARGET="_top"
+>socket options</A
+>
+ parameter in the <A
+HREF="smb.conf.5.html"
+TARGET="_top"
+><TT
+CLASS="FILENAME"
+>smb.conf(5)
+ </TT
+></A
+> file for details.</P
+></DD
+><DT
+>-p &#60;port number&#62;</DT
+><DD
+><P
+><TT
+CLASS="REPLACEABLE"
+><I
+>port number</I
+></TT
+> is a positive integer
value. The default value if this parameter is not
- specified is 139.</p><p>This number is the port number that will be
+ specified is 139.</P
+><P
+>This number is the port number that will be
used when making connections to the server from client
software. The standard (well-known) port number for the
SMB over TCP is 139, hence the default. If you wish to
run the server as an ordinary user rather than
as root, most systems will require you to use a port
number greater than 1024 - ask your system administrator
- for help if you are in this situation.</p><p>In order for the server to be useful by most
+ for help if you are in this situation.</P
+><P
+>In order for the server to be useful by most
clients, should you configure it on a port other
than 139, you will require port redirection services
on port 139, details of which are outlined in rfc1002.txt
- section 4.3.5.</p><p>This parameter is not normally specified except
- in the above situation.</p></dd></dl></div></div><div class="refsect1" lang="en"><h2>FILES</h2><div class="variablelist"><dl><dt><span class="term"><tt>/etc/inetd.conf</tt></span></dt><dd><p>If the server is to be run by the
- <b>inetd</b> meta-daemon, this file
+ section 4.3.5.</P
+><P
+>This parameter is not normally specified except
+ in the above situation.</P
+></DD
+><DT
+>-s &#60;configuration file&#62;</DT
+><DD
+><P
+>The file specified contains the
+ configuration details required by the server. The
+ information in this file includes server-specific
+ information such as what printcap file to use, as well
+ as descriptions of all the services that the server is
+ to provide. See <A
+HREF="smb.conf.5.html"
+TARGET="_top"
+><TT
+CLASS="FILENAME"
+> smb.conf(5)</TT
+></A
+> for more information.
+ The default configuration file name is determined at
+ compile time.</P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN123"
+></A
+><H2
+>FILES</H2
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+><TT
+CLASS="FILENAME"
+>/etc/inetd.conf</TT
+></DT
+><DD
+><P
+>If the server is to be run by the
+ <B
+CLASS="COMMAND"
+>inetd</B
+> meta-daemon, this file
must contain suitable startup information for the
- meta-daemon. See the <a href="install.html" target="_top">&quot;How to Install and Test SAMBA&quot;</a>
+ meta-daemon. See the <A
+HREF="UNIX_INSTALL.html"
+TARGET="_top"
+>UNIX_INSTALL.html</A
+>
document for details.
- </p></dd><dt><span class="term"><tt>/etc/rc</tt></span></dt><dd><p>or whatever initialization script your
- system uses).</p><p>If running the server as a daemon at startup,
+ </P
+></DD
+><DT
+><TT
+CLASS="FILENAME"
+>/etc/rc</TT
+></DT
+><DD
+><P
+>or whatever initialization script your
+ system uses).</P
+><P
+>If running the server as a daemon at startup,
this file will need to contain an appropriate startup
- sequence for the server. See the <a href="install.html" target="_top">&quot;How to Install and Test SAMBA&quot;</a>
- document for details.</p></dd><dt><span class="term"><tt>/etc/services</tt></span></dt><dd><p>If running the server via the
- meta-daemon <b>inetd</b>, this file
+ sequence for the server. See the <A
+HREF="UNIX_INSTALL.html"
+TARGET="_top"
+>UNIX_INSTALL.html</A
+>
+ document for details.</P
+></DD
+><DT
+><TT
+CLASS="FILENAME"
+>/etc/services</TT
+></DT
+><DD
+><P
+>If running the server via the
+ meta-daemon <B
+CLASS="COMMAND"
+>inetd</B
+>, this file
must contain a mapping of service name (e.g., netbios-ssn)
to service port (e.g., 139) and protocol type (e.g., tcp).
- See the <a href="install.html" target="_top">&quot;How to Install and Test SAMBA&quot;</a>
- document for details.</p></dd><dt><span class="term"><tt>/usr/local/samba/lib/smb.conf</tt></span></dt><dd><p>This is the default location of the <a href="smb.conf.5.html">smb.conf(5)</a> server configuration file. Other common places that systems
- install this file are <tt>/usr/samba/lib/smb.conf</tt>
- and <tt>/etc/samba/smb.conf</tt>.</p><p>This file describes all the services the server
- is to make available to clients. See <a href="smb.conf.5.html">smb.conf(5)</a> for more information.</p></dd></dl></div></div><div class="refsect1" lang="en"><h2>LIMITATIONS</h2><p>On some systems <b>smbd</b> cannot change uid back
+ See the <A
+HREF="UNIX_INSTALL.html"
+TARGET="_top"
+>UNIX_INSTALL.html</A
+>
+ document for details.</P
+></DD
+><DT
+><TT
+CLASS="FILENAME"
+>/usr/local/samba/lib/smb.conf</TT
+></DT
+><DD
+><P
+>This is the default location of the
+ <A
+HREF="smb.conf.5.html"
+TARGET="_top"
+><TT
+CLASS="FILENAME"
+>smb.conf</TT
+></A
+>
+ server configuration file. Other common places that systems
+ install this file are <TT
+CLASS="FILENAME"
+>/usr/samba/lib/smb.conf</TT
+>
+ and <TT
+CLASS="FILENAME"
+>/etc/smb.conf</TT
+>.</P
+><P
+>This file describes all the services the server
+ is to make available to clients. See <A
+HREF="smb.conf.5.html"
+TARGET="_top"
+> <TT
+CLASS="FILENAME"
+>smb.conf(5)</TT
+></A
+> for more information.</P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN159"
+></A
+><H2
+>LIMITATIONS</H2
+><P
+>On some systems <B
+CLASS="COMMAND"
+>smbd</B
+> cannot change uid back
to root after a setuid() call. Such systems are called
trapdoor uid systems. If you have such a system,
you will be unable to connect from a client (such as a PC) as
two different users at once. Attempts to connect the
second user will result in access denied or
- similar.</p></div><div class="refsect1" lang="en"><h2>ENVIRONMENT VARIABLES</h2><div class="variablelist"><dl><dt><span class="term"><tt>PRINTER</tt></span></dt><dd><p>If no printer name is specified to
+ similar.</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN163"
+></A
+><H2
+>ENVIRONMENT VARIABLES</H2
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+><TT
+CLASS="ENVAR"
+>PRINTER</TT
+></DT
+><DD
+><P
+>If no printer name is specified to
printable services, most systems will use the value of
- this variable (or <tt>lp</tt> if this variable is
+ this variable (or <TT
+CLASS="CONSTANT"
+>lp</TT
+> if this variable is
not defined) as the name of the printer to use. This
- is not specific to the server, however.</p></dd></dl></div></div><div class="refsect1" lang="en"><h2>PAM INTERACTION</h2><p>Samba uses PAM for authentication (when presented with a plaintext
+ is not specific to the server, however.</P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN172"
+></A
+><H2
+>PAM INTERACTION</H2
+><P
+>Samba uses PAM for authentication (when presented with a plaintext
password), for account checking (is this account disabled?) and for
session management. The degree too which samba supports PAM is restricted
- by the limitations of the SMB protocol and the <a href="smb.conf.5.html#OBEYPAMRESRICTIONS" target="_top"><i><tt>obey
- pam restricions</tt></i></a> <a href="smb.conf.5.html">smb.conf(5)</a> paramater. When this is set, the following restrictions apply:
- </p><div class="itemizedlist"><ul type="disc"><li><p><span class="emphasis"><em>Account Validation</em></span>: All accesses to a
+ by the limitations of the SMB protocol and the
+ <A
+HREF="smb.conf.5.html#OBEYPAMRESRICTIONS"
+TARGET="_top"
+>obey pam restricions</A
+>
+ smb.conf paramater. When this is set, the following restrictions apply:
+ </P
+><P
+></P
+><UL
+><LI
+><P
+><I
+CLASS="EMPHASIS"
+>Account Validation</I
+>: All accesses to a
samba server are checked
against PAM to see if the account is vaild, not disabled and is permitted to
login at this time. This also applies to encrypted logins.
- </p></li><li><p><span class="emphasis"><em>Session Management</em></span>: When not using share
+ </P
+></LI
+><LI
+><P
+><I
+CLASS="EMPHASIS"
+>Session Management</I
+>: When not using share
level secuirty, users must pass PAM's session checks before access
is granted. Note however, that this is bypassed in share level secuirty.
Note also that some older pam configuration files may need a line
added for session support.
- </p></li></ul></div></div><div class="refsect1" lang="en"><h2>VERSION</h2><p>This man page is correct for version 3.0 of
- the Samba suite.</p></div><div class="refsect1" lang="en"><h2>DIAGNOSTICS</h2><p>Most diagnostics issued by the server are logged
+ </P
+></LI
+></UL
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN183"
+></A
+><H2
+>VERSION</H2
+><P
+>This man page is correct for version 3.0 of
+ the Samba suite.</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN186"
+></A
+><H2
+>DIAGNOSTICS</H2
+><P
+>Most diagnostics issued by the server are logged
in a specified log file. The log file name is specified
- at compile time, but may be overridden on the command line.</p><p>The number and nature of diagnostics available depends
+ at compile time, but may be overridden on the command line.</P
+><P
+>The number and nature of diagnostics available depends
on the debug level used by the server. If you have problems, set
- the debug level to 3 and peruse the log files.</p><p>Most messages are reasonably self-explanatory. Unfortunately,
+ the debug level to 3 and peruse the log files.</P
+><P
+>Most messages are reasonably self-explanatory. Unfortunately,
at the time this man page was created, there are too many diagnostics
available in the source code to warrant describing each and every
diagnostic. At this stage your best bet is still to grep the
source code and inspect the conditions that gave rise to the
- diagnostics you are seeing.</p></div><div class="refsect1" lang="en"><h2>SIGNALS</h2><p>Sending the <b>smbd</b> a SIGHUP will cause it to
- reload its <tt>smb.conf</tt> configuration
- file within a short period of time.</p><p>To shut down a user's <b>smbd</b> process it is recommended
- that <b>SIGKILL (-9)</b> <span class="emphasis"><em>NOT</em></span>
+ diagnostics you are seeing.</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN191"
+></A
+><H2
+>SIGNALS</H2
+><P
+>Sending the <B
+CLASS="COMMAND"
+>smbd</B
+> a SIGHUP will cause it to
+ reload its <TT
+CLASS="FILENAME"
+>smb.conf</TT
+> configuration
+ file within a short period of time.</P
+><P
+>To shut down a user's <B
+CLASS="COMMAND"
+>smbd</B
+> process it is recommended
+ that <B
+CLASS="COMMAND"
+>SIGKILL (-9)</B
+> <I
+CLASS="EMPHASIS"
+>NOT</I
+>
be used, except as a last resort, as this may leave the shared
memory area in an inconsistent state. The safe way to terminate
- an <b>smbd</b> is to send it a SIGTERM (-15) signal and wait for
- it to die on its own.</p><p>The debug log level of <b>smbd</b> may be raised
- or lowered using <a href="smbcontrol.1.html">smbcontrol(1)</a> program (SIGUSR[1|2] signals are no longer
- used since Samba 2.2). This is to allow transient problems to be diagnosed,
- whilst still running at a normally low log level.</p><p>Note that as the signal handlers send a debug write,
- they are not re-entrant in <b>smbd</b>. This you should wait until
- <b>smbd</b> is in a state of waiting for an incoming SMB before
+ an <B
+CLASS="COMMAND"
+>smbd</B
+> is to send it a SIGTERM (-15) signal and wait for
+ it to die on its own.</P
+><P
+>The debug log level of <B
+CLASS="COMMAND"
+>smbd</B
+> may be raised
+ or lowered using <A
+HREF="smbcontrol.1.html"
+TARGET="_top"
+><B
+CLASS="COMMAND"
+>smbcontrol(1)
+ </B
+></A
+> program (SIGUSR[1|2] signals are no longer used in
+ Samba 2.2). This is to allow transient problems to be diagnosed,
+ whilst still running at a normally low log level.</P
+><P
+>Note that as the signal handlers send a debug write,
+ they are not re-entrant in <B
+CLASS="COMMAND"
+>smbd</B
+>. This you should wait until
+ <B
+CLASS="COMMAND"
+>smbd</B
+> is in a state of waiting for an incoming SMB before
issuing them. It is possible to make the signal handlers safe
by un-blocking the signals before the select call and re-blocking
- them after, however this would affect performance.</p></div><div class="refsect1" lang="en"><h2>SEE ALSO</h2><p><a href="hosts_access.5.html">hosts_access(5)</a>, <a href="inetd.8.html">inetd(8)</a>, <a href="nmbd.8.html">nmbd(8)</a>, <a href="smb.conf.5.html">smb.conf(5)</a>, <a href="smbclient.1.html">smbclient(1)</a>, <a href="testparm.1.html">testparm(1)</a>, <a href="testprns.1.html">testprns(1)</a>, and the
- Internet RFC's <tt>rfc1001.txt</tt>, <tt>rfc1002.txt</tt>.
+ them after, however this would affect performance.</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN208"
+></A
+><H2
+>SEE ALSO</H2
+><P
+>hosts_access(5), <B
+CLASS="COMMAND"
+>inetd(8)</B
+>,
+ <A
+HREF="nmbd.8.html"
+TARGET="_top"
+><B
+CLASS="COMMAND"
+>nmbd(8)</B
+></A
+>,
+ <A
+HREF="smb.conf.5.html"
+TARGET="_top"
+><TT
+CLASS="FILENAME"
+>smb.conf(5)</TT
+>
+ </A
+>, <A
+HREF="smbclient.1.html"
+TARGET="_top"
+><B
+CLASS="COMMAND"
+>smbclient(1)
+ </B
+></A
+>, <A
+HREF="testparm.1.html"
+TARGET="_top"
+><B
+CLASS="COMMAND"
+> testparm(1)</B
+></A
+>, <A
+HREF="testprns.1.html"
+TARGET="_top"
+> <B
+CLASS="COMMAND"
+>testprns(1)</B
+></A
+>, and the Internet RFC's
+ <TT
+CLASS="FILENAME"
+>rfc1001.txt</TT
+>, <TT
+CLASS="FILENAME"
+>rfc1002.txt</TT
+>.
In addition the CIFS (formerly SMB) specification is available
- as a link from the Web page <a href="http://samba.org/cifs/" target="_top">
- http://samba.org/cifs/</a>.</p></div><div class="refsect1" lang="en"><h2>AUTHOR</h2><p>The original Samba software and related utilities
+ as a link from the Web page <A
+HREF="http://samba.org/cifs/"
+TARGET="_top"
+>
+ http://samba.org/cifs/</A
+>.</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN225"
+></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.
+ to the way the Linux kernel is developed.</P
+><P
+>The original Samba man pages were written by Karl Auer.
The man page sources were converted to YODL format (another
- excellent piece of Open Source software, available at <a href="ftp://ftp.icce.rug.nl/pub/unix/" target="_top">
- ftp://ftp.icce.rug.nl/pub/unix/</a>) and updated for the Samba 2.0
+ excellent piece of Open Source software, available at
+ <A
+HREF="ftp://ftp.icce.rug.nl/pub/unix/"
+TARGET="_top"
+> ftp://ftp.icce.rug.nl/pub/unix/</A
+>) and updated for the Samba 2.0
release by Jeremy Allison. The conversion to DocBook for
- Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 for
- Samba 3.0 was done by Alexander Bokovoy.</p></div></div></body></html>
+ Samba 2.2 was done by Gerald Carter</P
+></DIV
+></BODY
+></HTML
+> \ No newline at end of file
diff --git a/docs/htmldocs/smbmnt.8.html b/docs/htmldocs/smbmnt.8.html
index d577a6a3a7..06b9fb1fd3 100644
--- a/docs/htmldocs/smbmnt.8.html
+++ b/docs/htmldocs/smbmnt.8.html
@@ -1,24 +1,179 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>smbmnt</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="smbmnt.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>smbmnt &#8212; helper utility for mounting SMB filesystems</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><tt>smbmnt</tt> {mount-point} [-s &lt;share&gt;] [-r] [-u &lt;uid&gt;] [-g &lt;gid&gt;] [-f &lt;mask&gt;] [-d &lt;mask&gt;] [-o &lt;options&gt;] [-h]</p></div></div><div class="refsect1" lang="en"><h2>DESCRIPTION</h2><p><b>smbmnt</b> is a helper application used
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<HTML
+><HEAD
+><TITLE
+>smbmnt</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.77"></HEAD
+><BODY
+CLASS="REFENTRY"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><H1
+><A
+NAME="SMBMNT"
+></A
+>smbmnt</H1
+><DIV
+CLASS="REFNAMEDIV"
+><A
+NAME="AEN5"
+></A
+><H2
+>Name</H2
+>smbmnt&nbsp;--&nbsp;helper utility for mounting SMB filesystems</DIV
+><DIV
+CLASS="REFSYNOPSISDIV"
+><A
+NAME="AEN8"
+></A
+><H2
+>Synopsis</H2
+><P
+><B
+CLASS="COMMAND"
+>smbmnt</B
+> {mount-point} [-s &lt;share&gt;] [-r] [-u &lt;uid&gt;] [-g &lt;gid&gt;] [-f &lt;mask&gt;] [-d &lt;mask&gt;] [-o &lt;options&gt;]</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN19"
+></A
+><H2
+>DESCRIPTION</H2
+><P
+><B
+CLASS="COMMAND"
+>smbmnt</B
+> is a helper application used
by the smbmount program to do the actual mounting of SMB shares.
- <b>smbmnt</b> can be installed setuid root if you want
- normal users to be able to mount their SMB shares.</p><p>A setuid smbmnt will only allow mounts on directories owned
- by the user, and that the user has write permission on.</p><p>The <b>smbmnt</b> program is normally invoked
- by <a href="smbmount.8.html">smbmount(8)</a>. It should not be invoked directly by users. </p><p>smbmount searches the normal PATH for smbmnt. You must ensure
- that the smbmnt version in your path matches the smbmount used.</p></div><div class="refsect1" lang="en"><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-r</span></dt><dd><p>mount the filesystem read-only
- </p></dd><dt><span class="term">-u uid</span></dt><dd><p>specify the uid that the files will
- be owned by </p></dd><dt><span class="term">-g gid</span></dt><dd><p>specify the gid that the files will be
- owned by </p></dd><dt><span class="term">-f mask</span></dt><dd><p>specify the octal file mask applied
- </p></dd><dt><span class="term">-d mask</span></dt><dd><p>specify the octal directory mask
- applied </p></dd><dt><span class="term">-o options</span></dt><dd><p>
- list of options that are passed as-is to smbfs, if this
+ <B
+CLASS="COMMAND"
+>smbmnt</B
+> can be installed setuid root if you want
+ normal users to be able to mount their SMB shares.</P
+><P
+>A setuid smbmnt will only allow mounts on directories owned
+ by the user, and that the user has write permission on.</P
+><P
+>The <B
+CLASS="COMMAND"
+>smbmnt</B
+> program is normally invoked
+ by <A
+HREF="smbmount.8.html"
+TARGET="_top"
+><B
+CLASS="COMMAND"
+>smbmount(8)</B
+>
+ </A
+>. It should not be invoked directly by users. </P
+><P
+>smbmount searches the normal PATH for smbmnt. You must ensure
+ that the smbmnt version in your path matches the smbmount used.</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN30"
+></A
+><H2
+>OPTIONS</H2
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>-r</DT
+><DD
+><P
+>mount the filesystem read-only
+ </P
+></DD
+><DT
+>-u uid</DT
+><DD
+><P
+>specify the uid that the files will
+ be owned by </P
+></DD
+><DT
+>-g gid</DT
+><DD
+><P
+>specify the gid that the files will be
+ owned by </P
+></DD
+><DT
+>-f mask</DT
+><DD
+><P
+>specify the octal file mask applied
+ </P
+></DD
+><DT
+>-d mask</DT
+><DD
+><P
+>specify the octal directory mask
+ applied </P
+></DD
+><DT
+>-o options</DT
+><DD
+><P
+> list of options that are passed as-is to smbfs, if this
command is run on a 2.4 or higher Linux kernel.
- </p></dd><dt><span class="term">-h|--help</span></dt><dd><p>Print a summary of command line options.
-</p></dd></dl></div></div><div class="refsect1" lang="en"><h2>AUTHOR</h2><p>Volker Lendecke, Andrew Tridgell, Michael H. Warfield
- and others.</p><p>The current maintainer of smbfs and the userspace
- tools <b>smbmount</b>, <b>smbumount</b>,
- and <b>smbmnt</b> is <a href="mailto:urban@teststation.com" target="_top">Urban Widmark</a>.
- The <a href="mailto:samba@samba.org" target="_top">SAMBA Mailing list</a>
+ </P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN57"
+></A
+><H2
+>AUTHOR</H2
+><P
+>Volker Lendecke, Andrew Tridgell, Michael H. Warfield
+ and others.</P
+><P
+>The current maintainer of smbfs and the userspace
+ tools <B
+CLASS="COMMAND"
+>smbmount</B
+>, <B
+CLASS="COMMAND"
+>smbumount</B
+>,
+ and <B
+CLASS="COMMAND"
+>smbmnt</B
+> is <A
+HREF="mailto:urban@teststation.com"
+TARGET="_top"
+>Urban Widmark</A
+>.
+ The <A
+HREF="mailto:samba@samba.org"
+TARGET="_top"
+>SAMBA Mailing list</A
+>
is the preferred place to ask questions regarding these programs.
- </p><p>The conversion of this manpage for Samba 2.2 was performed
- by Gerald Carter. The conversion to DocBook XML 4.2 for Samba 3.0
- was done by Alexander Bokovoy.</p></div></div></body></html>
+ </P
+><P
+>The conversion of this manpage for Samba 2.2 was performed
+ by Gerald Carter</P
+></DIV
+></BODY
+></HTML
+> \ No newline at end of file
diff --git a/docs/htmldocs/smbmount.8.html b/docs/htmldocs/smbmount.8.html
index 94560fba66..81a3ac04b2 100644
--- a/docs/htmldocs/smbmount.8.html
+++ b/docs/htmldocs/smbmount.8.html
@@ -1,70 +1,321 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>smbmount</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="smbmount.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>smbmount &#8212; mount an smbfs filesystem</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><tt>smbmount</tt> {service} {mount-point} [-o options]</p></div></div><div class="refsect1" lang="en"><h2>DESCRIPTION</h2><p><b>smbmount</b> mounts a Linux SMB filesystem. It
- is usually invoked as <b>mount.smbfs</b> by
- the <a href="mount.8.html">mount(8)</a> command when using the
- &quot;-t smbfs&quot; option. This command only works in Linux, and the kernel must
- support the smbfs filesystem. </p><p>Options to <b>smbmount</b> are specified as a comma-separated
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<HTML
+><HEAD
+><TITLE
+>smbmount</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.77"></HEAD
+><BODY
+CLASS="REFENTRY"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><H1
+><A
+NAME="SMBMOUNT"
+></A
+>smbmount</H1
+><DIV
+CLASS="REFNAMEDIV"
+><A
+NAME="AEN5"
+></A
+><H2
+>Name</H2
+>smbmount&nbsp;--&nbsp;mount an smbfs filesystem</DIV
+><DIV
+CLASS="REFSYNOPSISDIV"
+><A
+NAME="AEN8"
+></A
+><H2
+>Synopsis</H2
+><P
+><B
+CLASS="COMMAND"
+>smbmount</B
+> {service} {mount-point} [-o options]</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN14"
+></A
+><H2
+>DESCRIPTION</H2
+><P
+><B
+CLASS="COMMAND"
+>smbmount</B
+> mounts a Linux SMB filesystem. It
+ is usually invoked as <B
+CLASS="COMMAND"
+>mount.smbfs</B
+> by
+ the <B
+CLASS="COMMAND"
+>mount(8)</B
+> command when using the
+ "-t smbfs" option. This command only works in Linux, and the kernel must
+ support the smbfs filesystem. </P
+><P
+>Options to <B
+CLASS="COMMAND"
+>smbmount</B
+> are specified as a comma-separated
list of key=value pairs. It is possible to send options other
than those listed here, assuming that smbfs supports them. If
you get mount failures, check your kernel log for errors on
- unknown options.</p><p><b>smbmount</b> is a daemon. After mounting it keeps running until
+ unknown options.</P
+><P
+><B
+CLASS="COMMAND"
+>smbmount</B
+> is a daemon. After mounting it keeps running until
the mounted smbfs is umounted. It will log things that happen
- when in daemon mode using the &quot;machine name&quot; smbmount, so
- typically this output will end up in <tt>log.smbmount</tt>. The <b>
- smbmount</b> process may also be called mount.smbfs.</p><p><span class="emphasis"><em>NOTE:</em></span> <b>smbmount</b>
- calls <a href="smbmnt.8.html">smbmnt(8)</a> to do the actual mount. You
- must make sure that <b>smbmnt</b> is in the path so
- that it can be found. </p></div><div class="refsect1" lang="en"><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">username=&lt;arg&gt;</span></dt><dd><p>specifies the username to connect as. If
- this is not given, then the environment variable <tt>
- USER</tt> is used. This option can also take the
- form &quot;user%password&quot; or &quot;user/workgroup&quot; or
- &quot;user/workgroup%password&quot; to allow the password and workgroup
- to be specified as part of the username.</p></dd><dt><span class="term">password=&lt;arg&gt;</span></dt><dd><p>specifies the SMB password. If this
+ when in daemon mode using the "machine name" smbmount, so
+ typically this output will end up in <TT
+CLASS="FILENAME"
+>log.smbmount</TT
+>. The
+ <B
+CLASS="COMMAND"
+>smbmount</B
+> process may also be called mount.smbfs.</P
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>NOTE:</I
+></SPAN
+> <B
+CLASS="COMMAND"
+>smbmount</B
+>
+ calls <B
+CLASS="COMMAND"
+>smbmnt(8)</B
+> to do the actual mount. You
+ must make sure that <B
+CLASS="COMMAND"
+>smbmnt</B
+> is in the path so
+ that it can be found. </P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN31"
+></A
+><H2
+>OPTIONS</H2
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>username=&lt;arg&gt;</DT
+><DD
+><P
+>specifies the username to connect as. If
+ this is not given, then the environment variable <TT
+CLASS="ENVAR"
+> USER</TT
+> is used. This option can also take the
+ form "user%password" or "user/workgroup" or
+ "user/workgroup%password" to allow the password and workgroup
+ to be specified as part of the username.</P
+></DD
+><DT
+>password=&lt;arg&gt;</DT
+><DD
+><P
+>specifies the SMB password. If this
option is not given then the environment variable
- <tt>PASSWD</tt> is used. If it can find
- no password <b>smbmount</b> will prompt
+ <TT
+CLASS="ENVAR"
+>PASSWD</TT
+> is used. If it can find
+ no password <B
+CLASS="COMMAND"
+>smbmount</B
+> will prompt
for a passeword, unless the guest option is
- given. </p><p>
- Note that passwords which contain the argument delimiter
+ given. </P
+><P
+> Note that passwords which contain the argument delimiter
character (i.e. a comma ',') will failed to be parsed correctly
on the command line. However, the same password defined
in the PASSWD environment variable or a credentials file (see
below) will be read correctly.
- </p></dd><dt><span class="term">credentials=&lt;filename&gt;</span></dt><dd><p>specifies a file that contains a username and/or password.
-The format of the file is:
-</p><pre class="programlisting">
-username = &lt;value&gt;
-password = &lt;value&gt;
-</pre><p>This is preferred over having passwords in plaintext in a
- shared file, such as <tt>/etc/fstab</tt>. Be sure to protect any
+ </P
+></DD
+><DT
+>credentials=&lt;filename&gt;</DT
+><DD
+><P
+>specifies a file that contains a username
+ and/or password. The format of the file is:</P
+><P
+> <PRE
+CLASS="PROGRAMLISTING"
+> username = &lt;value&gt;
+ password = &lt;value&gt;
+ </PRE
+>
+ </P
+><P
+>This is preferred over having passwords in plaintext in a
+ shared file, such as <TT
+CLASS="FILENAME"
+>/etc/fstab</TT
+>. Be sure to protect any
credentials file properly.
- </p></dd><dt><span class="term">krb</span></dt><dd><p>Use kerberos (Active Directory). </p></dd><dt><span class="term">netbiosname=&lt;arg&gt;</span></dt><dd><p>sets the source NetBIOS name. It defaults
- to the local hostname. </p></dd><dt><span class="term">uid=&lt;arg&gt;</span></dt><dd><p>sets the uid that will own all files on
+ </P
+></DD
+><DT
+>netbiosname=&lt;arg&gt;</DT
+><DD
+><P
+>sets the source NetBIOS name. It defaults
+ to the local hostname. </P
+></DD
+><DT
+>uid=&lt;arg&gt;</DT
+><DD
+><P
+>sets the uid that will own all files on
the mounted filesystem.
It may be specified as either a username or a numeric uid.
- </p></dd><dt><span class="term">gid=&lt;arg&gt;</span></dt><dd><p>sets the gid that will own all files on
+ </P
+></DD
+><DT
+>gid=&lt;arg&gt;</DT
+><DD
+><P
+>sets the gid that will own all files on
the mounted filesystem.
It may be specified as either a groupname or a numeric
- gid. </p></dd><dt><span class="term">port=&lt;arg&gt;</span></dt><dd><p>sets the remote SMB port number. The default
- is 139. </p></dd><dt><span class="term">fmask=&lt;arg&gt;</span></dt><dd><p>sets the file mask. This determines the
+ gid. </P
+></DD
+><DT
+>port=&lt;arg&gt;</DT
+><DD
+><P
+>sets the remote SMB port number. The default
+ is 139. </P
+></DD
+><DT
+>fmask=&lt;arg&gt;</DT
+><DD
+><P
+>sets the file mask. This determines the
permissions that remote files have in the local filesystem.
- The default is based on the current umask. </p></dd><dt><span class="term">dmask=&lt;arg&gt;</span></dt><dd><p>Sets the directory mask. This determines the
+ The default is based on the current umask. </P
+></DD
+><DT
+>dmask=&lt;arg&gt;</DT
+><DD
+><P
+>sets the directory mask. This determines the
permissions that remote directories have in the local filesystem.
- The default is based on the current umask. </p></dd><dt><span class="term">debug=&lt;arg&gt;</span></dt><dd><p>Sets the debug level. This is useful for
+ The default is based on the current umask. </P
+></DD
+><DT
+>debug=&lt;arg&gt;</DT
+><DD
+><P
+>sets the debug level. This is useful for
tracking down SMB connection problems. A suggested value to
start with is 4. If set too high there will be a lot of
- output, possibly hiding the useful output.</p></dd><dt><span class="term">ip=&lt;arg&gt;</span></dt><dd><p>Sets the destination host or IP address.
- </p></dd><dt><span class="term">workgroup=&lt;arg&gt;</span></dt><dd><p>Sets the workgroup on the destination </p></dd><dt><span class="term">sockopt=&lt;arg&gt;</span></dt><dd><p>Sets the TCP socket options. See the <a href="smb.conf.5.html#SOCKETOPTIONS" target="_top"><a href="smb.conf.5.html">smb.conf(5)</a></a> <i><tt>socket options</tt></i> option.
- </p></dd><dt><span class="term">scope=&lt;arg&gt;</span></dt><dd><p>Sets the NetBIOS scope </p></dd><dt><span class="term">guest</span></dt><dd><p>Don't prompt for a password </p></dd><dt><span class="term">ro</span></dt><dd><p>mount read-only </p></dd><dt><span class="term">rw</span></dt><dd><p>mount read-write </p></dd><dt><span class="term">iocharset=&lt;arg&gt;</span></dt><dd><p>
- sets the charset used by the Linux side for codepage
+ output, possibly hiding the useful output.</P
+></DD
+><DT
+>ip=&lt;arg&gt;</DT
+><DD
+><P
+>sets the destination host or IP address.
+ </P
+></DD
+><DT
+>workgroup=&lt;arg&gt;</DT
+><DD
+><P
+>sets the workgroup on the destination </P
+></DD
+><DT
+>sockopt=&lt;arg&gt;</DT
+><DD
+><P
+>sets the TCP socket options. See the <A
+HREF="smb.conf.5.html#SOCKETOPTIONS"
+TARGET="_top"
+><TT
+CLASS="FILENAME"
+>smb.conf
+ </TT
+></A
+> <TT
+CLASS="PARAMETER"
+><I
+>socket options</I
+></TT
+> option.
+ </P
+></DD
+><DT
+>scope=&lt;arg&gt;</DT
+><DD
+><P
+>sets the NetBIOS scope </P
+></DD
+><DT
+>guest</DT
+><DD
+><P
+>don't prompt for a password </P
+></DD
+><DT
+>ro</DT
+><DD
+><P
+>mount read-only </P
+></DD
+><DT
+>rw</DT
+><DD
+><P
+>mount read-write </P
+></DD
+><DT
+>iocharset=&lt;arg&gt;</DT
+><DD
+><P
+> sets the charset used by the Linux side for codepage
to charset translations (NLS). Argument should be the
name of a charset, like iso8859-1. (Note: only kernel
2.4.0 or later)
- </p></dd><dt><span class="term">codepage=&lt;arg&gt;</span></dt><dd><p>
- sets the codepage the server uses. See the iocharset
+ </P
+></DD
+><DT
+>codepage=&lt;arg&gt;</DT
+><DD
+><P
+> sets the codepage the server uses. See the iocharset
option. Example value cp850. (Note: only kernel 2.4.0
or later)
- </p></dd><dt><span class="term">ttl=&lt;arg&gt;</span></dt><dd><p>
- sets how long a directory listing is cached in milliseconds
+ </P
+></DD
+><DT
+>ttl=&lt;arg&gt;</DT
+><DD
+><P
+> sets how long a directory listing is cached in milliseconds
(also affects visibility of file size and date
changes). A higher value means that changes on the
server take longer to be noticed but it can give
@@ -73,34 +324,141 @@ password = &lt;value&gt;
like 10000ms (10 seconds) is probably more reasonable
in many cases.
(Note: only kernel 2.4.2 or later)
- </p></dd></dl></div></div><div class="refsect1" lang="en"><h2>ENVIRONMENT VARIABLES</h2><p>The variable <tt>USER</tt> may contain the username of the
+ </P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN125"
+></A
+><H2
+>ENVIRONMENT VARIABLES</H2
+><P
+>The variable <TT
+CLASS="ENVAR"
+>USER</TT
+> may contain the username of the
person using the client. This information is used only if the
protocol level is high enough to support session-level
passwords. The variable can be used to set both username and
- password by using the format username%password.</p><p>The variable <tt>PASSWD</tt> may contain the password of the
+ password by using the format username%password.</P
+><P
+>The variable <TT
+CLASS="ENVAR"
+>PASSWD</TT
+> may contain the password of the
person using the client. This information is used only if the
protocol level is high enough to support session-level
- passwords.</p><p>The variable <tt>PASSWD_FILE</tt> may contain the pathname
+ passwords.</P
+><P
+>The variable <TT
+CLASS="ENVAR"
+>PASSWD_FILE</TT
+> may contain the pathname
of a file to read the password from. A single line of input is
- read and used as the password.</p></div><div class="refsect1" lang="en"><h2>BUGS</h2><p>Passwords and other options containing , can not be handled.
+ read and used as the password.</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN133"
+></A
+><H2
+>BUGS</H2
+><P
+>Passwords and other options containing , can not be handled.
For passwords an alternative way of passing them is in a credentials
- file or in the PASSWD environment.</p><p>The credentials file does not handle usernames or passwords with
- leading space.</p><p>One smbfs bug is important enough to mention here, even if it
- is a bit misplaced:</p><div class="itemizedlist"><ul type="disc"><li><p>Mounts sometimes stop working. This is usually
+ file or in the PASSWD environment.</P
+><P
+>The credentials file does not handle usernames or passwords with
+ leading space.</P
+><P
+>One smbfs bug is important enough to mention here, even if it
+ is a bit misplaced:</P
+><P
+></P
+><UL
+><LI
+><P
+>Mounts sometimes stop working. This is usually
caused by smbmount terminating. Since smbfs needs smbmount to
reconnect when the server disconnects, the mount will eventually go
dead. An umount/mount normally fixes this. At least 2 ways to
- trigger this bug are known.</p></li></ul></div><p>Note that the typical response to a bug report is suggestion
+ trigger this bug are known.</P
+></LI
+></UL
+><P
+>Note that the typical response to a bug report is suggestion
to try the latest version first. So please try doing that first,
and always include which versions you use of relevant software
- when reporting bugs (minimum: samba, kernel, distribution)</p></div><div class="refsect1" lang="en"><h2>SEE ALSO</h2><p>Documentation/filesystems/smbfs.txt in the linux kernel
- source tree may contain additional options and information.</p><p>FreeBSD also has a smbfs, but it is not related to smbmount</p><p>For Solaris, HP-UX and others you may want to look at <a href="smbsh.1.html">smbsh(1)</a> or at other solutions, such as
- Sharity or perhaps replacing the SMB server with a NFS server.</p></div><div class="refsect1" lang="en"><h2>AUTHOR</h2><p>Volker Lendecke, Andrew Tridgell, Michael H. Warfield
- and others.</p><p>The current maintainer of smbfs and the userspace
- tools <b>smbmount</b>, <b>smbumount</b>,
- and <b>smbmnt</b> is <a href="mailto:urban@teststation.com" target="_top">Urban Widmark</a>.
- The <a href="mailto:samba@samba.org" target="_top">SAMBA Mailing list</a>
+ when reporting bugs (minimum: samba, kernel, distribution)</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN142"
+></A
+><H2
+>SEE ALSO</H2
+><P
+>Documentation/filesystems/smbfs.txt in the linux kernel
+ source tree may contain additional options and information.</P
+><P
+>FreeBSD also has a smbfs, but it is not related to smbmount</P
+><P
+>For Solaris, HP-UX and others you may want to look at
+ <A
+HREF="smbsh.1.html"
+TARGET="_top"
+><B
+CLASS="COMMAND"
+>smbsh(1)</B
+></A
+> or at other
+ solutions, such as sharity or perhaps replacing the SMB server with
+ a NFS server.</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN149"
+></A
+><H2
+>AUTHOR</H2
+><P
+>Volker Lendecke, Andrew Tridgell, Michael H. Warfield
+ and others.</P
+><P
+>The current maintainer of smbfs and the userspace
+ tools <B
+CLASS="COMMAND"
+>smbmount</B
+>, <B
+CLASS="COMMAND"
+>smbumount</B
+>,
+ and <B
+CLASS="COMMAND"
+>smbmnt</B
+> is <A
+HREF="mailto:urban@teststation.com"
+TARGET="_top"
+>Urban Widmark</A
+>.
+ The <A
+HREF="mailto:samba@samba.org"
+TARGET="_top"
+>SAMBA Mailing list</A
+>
is the preferred place to ask questions regarding these programs.
- </p><p>The conversion of this manpage for Samba 2.2 was performed
- by Gerald Carter. The conversion to DocBook XML 4.2 for Samba 3.0
- was done by Alexander Bokovoy.</p></div></div></body></html>
+ </P
+><P
+>The conversion of this manpage for Samba 2.2 was performed
+ by Gerald Carter</P
+></DIV
+></BODY
+></HTML
+> \ No newline at end of file
diff --git a/docs/htmldocs/smbpasswd.5.html b/docs/htmldocs/smbpasswd.5.html
index 82cb3450e9..ac3ab94691 100644
--- a/docs/htmldocs/smbpasswd.5.html
+++ b/docs/htmldocs/smbpasswd.5.html
@@ -1,89 +1,357 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>smbpasswd</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="smbpasswd.5"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>smbpasswd &#8212; The Samba encrypted password file</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><p><tt>smbpasswd</tt></p></div><div class="refsect1" lang="en"><h2>DESCRIPTION</h2><p>This tool is part of the <a href="Samba.7.html">Samba(7)</a> suite.</p><p>smbpasswd is the Samba encrypted password file. It contains
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<HTML
+><HEAD
+><TITLE
+>smbpasswd</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.77"></HEAD
+><BODY
+CLASS="REFENTRY"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><H1
+><A
+NAME="SMBPASSWD"
+></A
+>smbpasswd</H1
+><DIV
+CLASS="REFNAMEDIV"
+><A
+NAME="AEN5"
+></A
+><H2
+>Name</H2
+>smbpasswd&nbsp;--&nbsp;The Samba encrypted password file</DIV
+><DIV
+CLASS="REFSYNOPSISDIV"
+><A
+NAME="AEN8"
+></A
+><H2
+>Synopsis</H2
+><P
+><TT
+CLASS="FILENAME"
+>smbpasswd</TT
+></P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN11"
+></A
+><H2
+>DESCRIPTION</H2
+><P
+>This tool is part of the <A
+HREF="samba.7.html"
+TARGET="_top"
+> Samba</A
+> suite.</P
+><P
+>smbpasswd is the Samba encrypted password file. It contains
the username, Unix user id and the SMB hashed passwords of the
user, as well as account flag information and the time the
password was last changed. This file format has been evolving with
- Samba and has had several different formats in the past. </p></div><div class="refsect1" lang="en"><h2>FILE FORMAT</h2><p>The format of the smbpasswd file used by Samba 2.2
- is very similar to the familiar Unix <tt>passwd(5)</tt>
+ Samba and has had several different formats in the past. </P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN16"
+></A
+><H2
+>FILE FORMAT</H2
+><P
+>The format of the smbpasswd file used by Samba 2.2
+ is very similar to the familiar Unix <TT
+CLASS="FILENAME"
+>passwd(5)</TT
+>
file. It is an ASCII file containing one line for each user. Each field
ithin each line is separated from the next by a colon. Any entry
beginning with '#' is ignored. The smbpasswd file contains the
- following information for each user: </p><div class="variablelist"><dl><dt><span class="term">name</span></dt><dd><p> This is the user name. It must be a name that
- already exists in the standard UNIX passwd file. </p></dd><dt><span class="term">uid</span></dt><dd><p>This is the UNIX uid. It must match the uid
+ following information for each user: </P
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>name</DT
+><DD
+><P
+> This is the user name. It must be a name that
+ already exists in the standard UNIX passwd file. </P
+></DD
+><DT
+>uid</DT
+><DD
+><P
+>This is the UNIX uid. It must match the uid
field for the same user entry in the standard UNIX passwd file.
If this does not match then Samba will refuse to recognize
this smbpasswd file entry as being valid for a user.
- </p></dd><dt><span class="term">Lanman Password Hash</span></dt><dd><p>This is the LANMAN hash of the user's password,
+ </P
+></DD
+><DT
+>Lanman Password Hash</DT
+><DD
+><P
+>This is the LANMAN hash of the user's password,
encoded as 32 hex digits. The LANMAN hash is created by DES
encrypting a well known string with the user's password as the
DES key. This is the same password used by Windows 95/98 machines.
Note that this password hash is regarded as weak as it is
vulnerable to dictionary attacks and if two users choose the
same password this entry will be identical (i.e. the password
- is not &quot;salted&quot; as the UNIX password is). If the user has a
- null password this field will contain the characters &quot;NO PASSWORD&quot;
+ is not "salted" as the UNIX password is). If the user has a
+ null password this field will contain the characters "NO PASSWORD"
as the start of the hex string. If the hex string is equal to
32 'X' characters then the user's account is marked as
- <tt>disabled</tt> and the user will not be able to
- log onto the Samba server. </p><p><span class="emphasis"><em>WARNING !!</em></span> Note that, due to
+ <TT
+CLASS="CONSTANT"
+>disabled</TT
+> and the user will not be able to
+ log onto the Samba server. </P
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>WARNING !!</I
+></SPAN
+> Note that, due to
the challenge-response nature of the SMB/CIFS authentication
protocol, anyone with a knowledge of this password hash will
be able to impersonate the user on the network. For this
- reason these hashes are known as <span class="emphasis"><em>plain text
- equivalents</em></span> and must <span class="emphasis"><em>NOT</em></span> be made
+ reason these hashes are known as <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>plain text
+ equivalents</I
+></SPAN
+> and must <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>NOT</I
+></SPAN
+> be made
available to anyone but the root user. To protect these passwords
the smbpasswd file is placed in a directory with read and
traverse access only to the root user and the smbpasswd file
itself must be set to be read/write only by root, with no
- other access. </p></dd><dt><span class="term">NT Password Hash</span></dt><dd><p>This is the Windows NT hash of the user's
+ other access. </P
+></DD
+><DT
+>NT Password Hash</DT
+><DD
+><P
+>This is the Windows NT hash of the user's
password, encoded as 32 hex digits. The Windows NT hash is
created by taking the user's password as represented in
16-bit, little-endian UNICODE and then applying the MD4
- (internet rfc1321) hashing algorithm to it. </p><p>This password hash is considered more secure than
+ (internet rfc1321) hashing algorithm to it. </P
+><P
+>This password hash is considered more secure than
the LANMAN Password Hash as it preserves the case of the
password and uses a much higher quality hashing algorithm.
However, it is still the case that if two users choose the same
password this entry will be identical (i.e. the password is
- not &quot;salted&quot; as the UNIX password is). </p><p><span class="emphasis"><em>WARNING !!</em></span>. Note that, due to
+ not "salted" as the UNIX password is). </P
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>WARNING !!</I
+></SPAN
+>. Note that, due to
the challenge-response nature of the SMB/CIFS authentication
protocol, anyone with a knowledge of this password hash will
be able to impersonate the user on the network. For this
- reason these hashes are known as <span class="emphasis"><em>plain text
- equivalents</em></span> and must <span class="emphasis"><em>NOT</em></span> be made
+ reason these hashes are known as <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>plain text
+ equivalents</I
+></SPAN
+> and must <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>NOT</I
+></SPAN
+> be made
available to anyone but the root user. To protect these passwords
the smbpasswd file is placed in a directory with read and
traverse access only to the root user and the smbpasswd file
itself must be set to be read/write only by root, with no
- other access. </p></dd><dt><span class="term">Account Flags</span></dt><dd><p>This section contains flags that describe
+ other access. </P
+></DD
+><DT
+>Account Flags</DT
+><DD
+><P
+>This section contains flags that describe
the attributes of the users account. In the Samba 2.2 release
this field is bracketed by '[' and ']' characters and is always
13 characters in length (including the '[' and ']' characters).
- The contents of this field may be any of the following characters:
- </p><div class="itemizedlist"><ul type="disc"><li><p><span class="emphasis"><em>U</em></span> - This means
- this is a &quot;User&quot; account, i.e. an ordinary user. Only User
+ The contents of this field may be any of the characters.
+ </P
+><P
+></P
+><UL
+><LI
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>U</I
+></SPAN
+> - This means
+ this is a "User" account, i.e. an ordinary user. Only User
and Workstation Trust accounts are currently supported
- in the smbpasswd file. </p></li><li><p><span class="emphasis"><em>N</em></span> - This means the
+ in the smbpasswd file. </P
+></LI
+><LI
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>N</I
+></SPAN
+> - This means the
account has no password (the passwords in the fields LANMAN
Password Hash and NT Password Hash are ignored). Note that this
- will only allow users to log on with no password if the <i><tt>
- null passwords</tt></i> parameter is set in the <a href="smb.conf.5.html#NULLPASSWORDS" target="_top"><a href="smb.conf.5.html">smb.conf(5)</a></a> config file. </p></li><li><p><span class="emphasis"><em>D</em></span> - This means the account
- is disabled and no SMB/CIFS logins will be allowed for this user. </p></li><li><p><span class="emphasis"><em>W</em></span> - This means this account
- is a &quot;Workstation Trust&quot; account. This kind of account is used
+ will only allow users to log on with no password if the <TT
+CLASS="PARAMETER"
+><I
+> null passwords</I
+></TT
+> parameter is set in the <A
+HREF="smb.conf.5.html#NULLPASSWORDS"
+TARGET="_top"
+><TT
+CLASS="FILENAME"
+>smb.conf(5)
+ </TT
+></A
+> config file. </P
+></LI
+><LI
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>D</I
+></SPAN
+> - This means the account
+ is disabled and no SMB/CIFS logins will be allowed for
+ this user. </P
+></LI
+><LI
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>W</I
+></SPAN
+> - This means this account
+ is a "Workstation Trust" account. This kind of account is used
in the Samba PDC code stream to allow Windows NT Workstations
- and Servers to join a Domain hosted by a Samba PDC. </p></li></ul></div><p>Other flags may be added as the code is extended in future.
- The rest of this field space is filled in with spaces. </p></dd><dt><span class="term">Last Change Time</span></dt><dd><p>This field consists of the time the account was
+ and Servers to join a Domain hosted by a Samba PDC. </P
+></LI
+></UL
+><P
+>Other flags may be added as the code is extended in future.
+ The rest of this field space is filled in with spaces. </P
+></DD
+><DT
+>Last Change Time</DT
+><DD
+><P
+>This field consists of the time the account was
last modified. It consists of the characters 'LCT-' (standing for
- &quot;Last Change Time&quot;) followed by a numeric encoding of the UNIX time
+ "Last Change Time") followed by a numeric encoding of the UNIX time
in seconds since the epoch (1970) that the last change was made.
- </p></dd></dl></div><p>All other colon separated fields are ignored at this time.</p></div><div class="refsect1" lang="en"><h2>VERSION</h2><p>This man page is correct for version 3.0 of
- the Samba suite.</p></div><div class="refsect1" lang="en"><h2>SEE ALSO</h2><p><a href="smbpasswd.8.html">smbpasswd(8)</a>, <a href="Samba.7.html">Samba(7)</a>, and
+ </P
+></DD
+></DL
+></DIV
+><P
+>All other colon separated fields are ignored at this time.</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN73"
+></A
+><H2
+>VERSION</H2
+><P
+>This man page is correct for version 3.0 of
+ the Samba suite.</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN76"
+></A
+><H2
+>SEE ALSO</H2
+><P
+><A
+HREF="smbpasswd.8.html"
+TARGET="_top"
+><B
+CLASS="COMMAND"
+>smbpasswd(8)</B
+></A
+>,
+ <A
+HREF="samba.7.html"
+TARGET="_top"
+>samba(7)</A
+>, and
the Internet RFC1321 for details on the MD4 algorithm.
- </p></div><div class="refsect1" lang="en"><h2>AUTHOR</h2><p>The original Samba software and related utilities
+ </P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN82"
+></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.
+ to the way the Linux kernel is developed.</P
+><P
+>The original Samba man pages were written by Karl Auer.
The man page sources were converted to YODL format (another
- excellent piece of Open Source software, available at <a href="ftp://ftp.icce.rug.nl/pub/unix/" target="_top">
- ftp://ftp.icce.rug.nl/pub/unix/</a>) and updated for the Samba 2.0
+ excellent piece of Open Source software, available at
+ <A
+HREF="ftp://ftp.icce.rug.nl/pub/unix/"
+TARGET="_top"
+> ftp://ftp.icce.rug.nl/pub/unix/</A
+>) and updated for the Samba 2.0
release by Jeremy Allison. The conversion to DocBook for
- Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2
- for Samba 3.0 was done by Alexander Bokovoy.</p></div></div></body></html>
+ Samba 2.2 was done by Gerald Carter</P
+></DIV
+></BODY
+></HTML
+> \ No newline at end of file
diff --git a/docs/htmldocs/smbpasswd.8.html b/docs/htmldocs/smbpasswd.8.html
index 44a1089e13..da3cb9f601 100644
--- a/docs/htmldocs/smbpasswd.8.html
+++ b/docs/htmldocs/smbpasswd.8.html
@@ -1,163 +1,626 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>smbpasswd</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="smbpasswd.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>smbpasswd &#8212; change a user's SMB password</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><tt>smbpasswd</tt> [-a] [-x] [-d] [-e] [-D debuglevel] [-n] [-r &lt;remote machine&gt;] [-R &lt;name resolve order&gt;] [-m] [-U username[%password]] [-h] [-s] [-w pass] [-i] [-L] [username]</p></div></div><div class="refsect1" lang="en"><h2>DESCRIPTION</h2><p>This tool is part of the <a href="Samba.7.html">Samba(7)</a> suite.</p><p>The smbpasswd program has several different
- functions, depending on whether it is run by the <span class="emphasis"><em>root</em></span> user
- or not. When run as a normal user it allows the user to change
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
+<HTML
+><HEAD
+><TITLE
+>smbpasswd</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"></HEAD
+><BODY
+CLASS="REFENTRY"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><H1
+><A
+NAME="SMBPASSWD">smbpasswd</H1
+><DIV
+CLASS="REFNAMEDIV"
+><A
+NAME="AEN5"
+></A
+><H2
+>Name</H2
+>smbpasswd&nbsp;--&nbsp;change a user's SMB password</DIV
+><DIV
+CLASS="REFSYNOPSISDIV"
+><A
+NAME="AEN8"><H2
+>Synopsis</H2
+><P
+><B
+CLASS="COMMAND"
+>smbpasswd</B
+> [-a] [-x] [-d] [-e] [-D debuglevel] [-n] [-r &#60;remote machine&#62;] [-R &#60;name resolve order&#62;] [-m] [-U username[%password]] [-h] [-s] [-w pass] [-i] [-L] [username]</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN27"
+></A
+><H2
+>DESCRIPTION</H2
+><P
+>This tool is part of the <A
+HREF="samba.7.html"
+TARGET="_top"
+> Samba</A
+> suite.</P
+><P
+>The smbpasswd program has several different
+ functions, depending on whether it is run by the <I
+CLASS="EMPHASIS"
+>root</I
+>
+ user or not. When run as a normal user it allows the user to change
the password used for their SMB sessions on any machines that store
- SMB passwords. </p><p>By default (when run with no arguments) it will attempt to
+ SMB passwords. </P
+><P
+>By default (when run with no arguments) it will attempt to
change the current user's SMB password on the local machine. This is
- similar to the way the <b>passwd(1)</b> program works. <b>
- smbpasswd</b> differs from how the passwd program works
- however in that it is not <span class="emphasis"><em>setuid root</em></span> but works in
- a client-server mode and communicates with a
- locally running <a href="smbd.8.html">smbd(8)</a>. As a consequence in order for this to
+ similar to the way the <B
+CLASS="COMMAND"
+>passwd(1)</B
+> program works.
+ <B
+CLASS="COMMAND"
+>smbpasswd</B
+> differs from how the passwd program works
+ however in that it is not <I
+CLASS="EMPHASIS"
+>setuid root</I
+> but works in
+ a client-server mode and communicates with a locally running
+ <B
+CLASS="COMMAND"
+>smbd(8)</B
+>. As a consequence in order for this to
succeed the smbd daemon must be running on the local machine. On a
UNIX machine the encrypted SMB passwords are usually stored in
- the <a href="smbpasswd.5.html">smbpasswd(5)</a> file. </p><p>When run by an ordinary user with no options, smbpasswd
+ the <TT
+CLASS="FILENAME"
+>smbpasswd(5)</TT
+> file. </P
+><P
+>When run by an ordinary user with no options, smbpasswd
will prompt them for their old SMB password and then ask them
for their new password twice, to ensure that the new password
was typed correctly. No passwords will be echoed on the screen
whilst being typed. If you have a blank SMB password (specified by
- the string &quot;NO PASSWORD&quot; in the smbpasswd file) then just press
- the &lt;Enter&gt; key when asked for your old password. </p><p>smbpasswd can also be used by a normal user to change their
+ the string "NO PASSWORD" in the smbpasswd file) then just press
+ the &#60;Enter&#62; key when asked for your old password. </P
+><P
+>smbpasswd can also be used by a normal user to change their
SMB password on remote machines, such as Windows NT Primary Domain
- Controllers. See the (<i><tt>-r</tt></i>) and <i><tt>-U</tt></i> options
- below. </p><p>When run by root, smbpasswd allows new users to be added
+ Controllers. See the (-r) and -U options below. </P
+><P
+>When run by root, smbpasswd allows new users to be added
and deleted in the smbpasswd file, as well as allows changes to
- the attributes of the user in this file to be made. When run by root, <b>
- smbpasswd</b> accesses the local smbpasswd file
+ the attributes of the user in this file to be made. When run by root,
+ <B
+CLASS="COMMAND"
+>smbpasswd</B
+> accesses the local smbpasswd file
directly, thus enabling changes to be made even if smbd is not
- running. </p></div><div class="refsect1" lang="en"><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-a</span></dt><dd><p>This option specifies that the username
+ running. </P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN43"
+></A
+><H2
+>OPTIONS</H2
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>-a</DT
+><DD
+><P
+>This option specifies that the username
following should be added to the local smbpasswd file, with the
- new password typed (type &lt;Enter&gt; for the old password). This
+ new password typed (type &#60;Enter&#62; for the old password). This
option is ignored if the username following already exists in
the smbpasswd file and it is treated like a regular change
password command. Note that the default passdb backends require
the user to already exist in the system password file (usually
- <tt>/etc/passwd</tt>), else the request to add the
- user will fail. </p><p>This option is only available when running smbpasswd
- as root. </p></dd><dt><span class="term">-x</span></dt><dd><p>This option specifies that the username
+ <TT
+CLASS="FILENAME"
+>/etc/passwd</TT
+>), else the request to add the
+ user will fail. </P
+><P
+>This option is only available when running smbpasswd
+ as root. </P
+></DD
+><DT
+>-x</DT
+><DD
+><P
+>This option specifies that the username
following should be deleted from the local smbpasswd file.
- </p><p>This option is only available when running smbpasswd as
- root.</p></dd><dt><span class="term">-d</span></dt><dd><p>This option specifies that the username following
- should be <tt>disabled</tt> in the local smbpasswd
- file. This is done by writing a <tt>'D'</tt> flag
+ </P
+><P
+>This option is only available when running smbpasswd as
+ root.</P
+></DD
+><DT
+>-d</DT
+><DD
+><P
+>This option specifies that the username following
+ should be <TT
+CLASS="CONSTANT"
+>disabled</TT
+> in the local smbpasswd
+ file. This is done by writing a <TT
+CLASS="CONSTANT"
+>'D'</TT
+> flag
into the account control space in the smbpasswd file. Once this
is done all attempts to authenticate via SMB using this username
- will fail. </p><p>If the smbpasswd file is in the 'old' format (pre-Samba 2.0
+ will fail. </P
+><P
+>If the smbpasswd file is in the 'old' format (pre-Samba 2.0
format) there is no space in the user's password entry to write
- this information and the command will FAIL. See <a href="smbpasswd.5.html">smbpasswd(5)</a> for details on the 'old' and new password file formats.
- </p><p>This option is only available when running smbpasswd as
- root.</p></dd><dt><span class="term">-e</span></dt><dd><p>This option specifies that the username following
- should be <tt>enabled</tt> in the local smbpasswd file,
+ this information and the command will FAIL. See <B
+CLASS="COMMAND"
+>smbpasswd(5)
+ </B
+> for details on the 'old' and new password file formats.
+ </P
+><P
+>This option is only available when running smbpasswd as
+ root.</P
+></DD
+><DT
+>-e</DT
+><DD
+><P
+>This option specifies that the username following
+ should be <TT
+CLASS="CONSTANT"
+>enabled</TT
+> in the local smbpasswd file,
if the account was previously disabled. If the account was not
disabled this option has no effect. Once the account is enabled then
- the user will be able to authenticate via SMB once again. </p><p>If the smbpasswd file is in the 'old' format, then <b>
- smbpasswd</b> will FAIL to enable the account.
- See <a href="smbpasswd.5.html">smbpasswd(5)</a> for
- details on the 'old' and new password file formats. </p><p>This option is only available when running smbpasswd as root.
- </p></dd><dt><span class="term">-D debuglevel</span></dt><dd><p><i><tt>debuglevel</tt></i> is an integer
+ the user will be able to authenticate via SMB once again. </P
+><P
+>If the smbpasswd file is in the 'old' format, then <B
+CLASS="COMMAND"
+> smbpasswd</B
+> will FAIL to enable the account.
+ See <B
+CLASS="COMMAND"
+>smbpasswd (5)</B
+> for
+ details on the 'old' and new password file formats. </P
+><P
+>This option is only available when running smbpasswd as root.
+ </P
+></DD
+><DT
+>-D debuglevel</DT
+><DD
+><P
+><TT
+CLASS="REPLACEABLE"
+><I
+>debuglevel</I
+></TT
+> is an integer
from 0 to 10. The default value if this parameter is not specified
- is zero. </p><p>The higher this value, the more detail will be logged to the
+ is zero. </P
+><P
+>The higher this value, the more detail will be logged to the
log files about the activities of smbpasswd. At level 0, only
- critical errors and serious warnings will be logged. </p><p>Levels above 1 will generate considerable amounts of log
+ critical errors and serious warnings will be logged. </P
+><P
+>Levels above 1 will generate considerable amounts of log
data, and should only be used when investigating a problem. Levels
above 3 are designed for use only by developers and generate
HUGE amounts of log data, most of which is extremely cryptic.
- </p></dd><dt><span class="term">-n</span></dt><dd><p>This option specifies that the username following
+ </P
+></DD
+><DT
+>-n</DT
+><DD
+><P
+>This option specifies that the username following
should have their password set to null (i.e. a blank password) in
- the local smbpasswd file. This is done by writing the string &quot;NO
- PASSWORD&quot; as the first part of the first password stored in the
- smbpasswd file. </p><p>Note that to allow users to logon to a Samba server once
- the password has been set to &quot;NO PASSWORD&quot; in the smbpasswd
+ the local smbpasswd file. This is done by writing the string "NO
+ PASSWORD" as the first part of the first password stored in the
+ smbpasswd file. </P
+><P
+>Note that to allow users to logon to a Samba server once
+ the password has been set to "NO PASSWORD" in the smbpasswd
file the administrator must set the following parameter in the [global]
- section of the <tt>smb.conf</tt> file : </p><p><b>null passwords = yes</b></p><p>This option is only available when running smbpasswd as
- root.</p></dd><dt><span class="term">-r remote machine name</span></dt><dd><p>This option allows a user to specify what machine
+ section of the <TT
+CLASS="FILENAME"
+>smb.conf</TT
+> file : </P
+><P
+><B
+CLASS="COMMAND"
+>null passwords = yes</B
+></P
+><P
+>This option is only available when running smbpasswd as
+ root.</P
+></DD
+><DT
+>-r remote machine name</DT
+><DD
+><P
+>This option allows a user to specify what machine
they wish to change their password on. Without this parameter
- smbpasswd defaults to the local host. The <i><tt>remote
- machine name</tt></i> is the NetBIOS name of the SMB/CIFS
+ smbpasswd defaults to the local host. The <TT
+CLASS="REPLACEABLE"
+><I
+>remote
+ machine name</I
+></TT
+> is the NetBIOS name of the SMB/CIFS
server to contact to attempt the password change. This name is
resolved into an IP address using the standard name resolution
- mechanism in all programs of the Samba suite. See the <i><tt>-R
- name resolve order</tt></i> parameter for details on changing
- this resolving mechanism. </p><p>The username whose password is changed is that of the
- current UNIX logged on user. See the <i><tt>-U username</tt></i>
+ mechanism in all programs of the Samba suite. See the <TT
+CLASS="PARAMETER"
+><I
+>-R
+ name resolve order</I
+></TT
+> parameter for details on changing
+ this resolving mechanism. </P
+><P
+>The username whose password is changed is that of the
+ current UNIX logged on user. See the <TT
+CLASS="PARAMETER"
+><I
+>-U username</I
+></TT
+>
parameter for details on changing the password for a different
- username. </p><p>Note that if changing a Windows NT Domain password the
+ username. </P
+><P
+>Note that if changing a Windows NT Domain password the
remote machine specified must be the Primary Domain Controller for
the domain (Backup Domain Controllers only have a read-only
copy of the user account database and will not allow the password
- change).</p><p><span class="emphasis"><em>Note</em></span> that Windows 95/98 do not have
+ change).</P
+><P
+><I
+CLASS="EMPHASIS"
+>Note</I
+> that Windows 95/98 do not have
a real password database so it is not possible to change passwords
- specifying a Win95/98 machine as remote machine target. </p></dd><dt><span class="term">-R name resolve order</span></dt><dd><p>This option allows the user of smbpasswd to determine
+ specifying a Win95/98 machine as remote machine target. </P
+></DD
+><DT
+>-R name resolve order</DT
+><DD
+><P
+>This option allows the user of smbpasswd to determine
what name resolution services to use when looking up the NetBIOS
- name of the host being connected to. </p><p>The options are :&quot;lmhosts&quot;, &quot;host&quot;, &quot;wins&quot; and &quot;bcast&quot;. They
- cause names to be resolved as follows: </p><div class="itemizedlist"><ul type="disc"><li><p><tt>lmhosts</tt>: Lookup an IP
+ name of the host being connected to. </P
+><P
+>The options are :"lmhosts", "host", "wins" and "bcast". They
+ cause names to be resolved as follows : </P
+><P
+></P
+><UL
+><LI
+><P
+><TT
+CLASS="CONSTANT"
+>lmhosts</TT
+> : Lookup an IP
address in the Samba lmhosts file. If the line in lmhosts has
- no name type attached to the NetBIOS name (see the <a href="lmhosts.5.html">lmhosts(5)</a> for details) then
- any name type matches for lookup.</p></li><li><p><tt>host</tt>: Do a standard host
- name to IP address resolution, using the system <tt>/etc/hosts
- </tt>, NIS, or DNS lookups. This method of name resolution
+ no name type attached to the NetBIOS name (see the <A
+HREF="lmhosts.5.html"
+TARGET="_top"
+>lmhosts(5)</A
+> for details) then
+ any name type matches for lookup.</P
+></LI
+><LI
+><P
+><TT
+CLASS="CONSTANT"
+>host</TT
+> : Do a standard host
+ name to IP address resolution, using the system <TT
+CLASS="FILENAME"
+>/etc/hosts
+ </TT
+>, NIS, or DNS lookups. This method of name resolution
is operating system depended for instance on IRIX or Solaris this
- may be controlled by the <tt>/etc/nsswitch.conf</tt>
+ may be controlled by the <TT
+CLASS="FILENAME"
+>/etc/nsswitch.conf</TT
+>
file). Note that this method is only used if the NetBIOS name
type being queried is the 0x20 (server) name type, otherwise
- it is ignored.</p></li><li><p><tt>wins</tt>: Query a name with
- the IP address listed in the <i><tt>wins server</tt></i>
+ it is ignored.</P
+></LI
+><LI
+><P
+><TT
+CLASS="CONSTANT"
+>wins</TT
+> : Query a name with
+ the IP address listed in the <TT
+CLASS="PARAMETER"
+><I
+>wins server</I
+></TT
+>
parameter. If no WINS server has been specified this method
- will be ignored.</p></li><li><p><tt>bcast</tt>: Do a broadcast on
+ will be ignored.</P
+></LI
+><LI
+><P
+><TT
+CLASS="CONSTANT"
+>bcast</TT
+> : Do a broadcast on
each of the known local interfaces listed in the
- <i><tt>interfaces</tt></i> parameter. This is the least
+ <TT
+CLASS="PARAMETER"
+><I
+>interfaces</I
+></TT
+> parameter. This is the least
reliable of the name resolution methods as it depends on the
- target host being on a locally connected subnet.</p></li></ul></div><p>The default order is <b>lmhosts, host, wins, bcast</b>
- and without this parameter or any entry in the <a href="smb.conf.5.html">smb.conf(5)</a> file the name resolution methods will
- be attempted in this order. </p></dd><dt><span class="term">-m</span></dt><dd><p>This option tells smbpasswd that the account
+ target host being on a locally connected subnet.</P
+></LI
+></UL
+><P
+>The default order is <B
+CLASS="COMMAND"
+>lmhosts, host, wins, bcast</B
+>
+ and without this parameter or any entry in the
+ <TT
+CLASS="FILENAME"
+>smb.conf</TT
+> file the name resolution methods will
+ be attempted in this order. </P
+></DD
+><DT
+>-m</DT
+><DD
+><P
+>This option tells smbpasswd that the account
being changed is a MACHINE account. Currently this is used
- when Samba is being used as an NT Primary Domain Controller.</p><p>This option is only available when running smbpasswd as root.
- </p></dd><dt><span class="term">-U username</span></dt><dd><p>This option may only be used in conjunction
- with the <i><tt>-r</tt></i> option. When changing
+ when Samba is being used as an NT Primary Domain Controller.</P
+><P
+>This option is only available when running smbpasswd as root.
+ </P
+></DD
+><DT
+>-U username</DT
+><DD
+><P
+>This option may only be used in conjunction
+ with the <TT
+CLASS="PARAMETER"
+><I
+>-r</I
+></TT
+> option. When changing
a password on a remote machine it allows the user to specify
the user name on that machine whose password will be changed. It
is present to allow users who have different user names on
- different systems to change these passwords. </p></dd><dt><span class="term">-h</span></dt><dd><p>This option prints the help string for <b>
- smbpasswd</b>, selecting the correct one for running as root
- or as an ordinary user. </p></dd><dt><span class="term">-s</span></dt><dd><p>This option causes smbpasswd to be silent (i.e.
+ different systems to change these passwords. </P
+></DD
+><DT
+>-h</DT
+><DD
+><P
+>This option prints the help string for <B
+CLASS="COMMAND"
+> smbpasswd</B
+>, selecting the correct one for running as root
+ or as an ordinary user. </P
+></DD
+><DT
+>-s</DT
+><DD
+><P
+>This option causes smbpasswd to be silent (i.e.
not issue prompts) and to read its old and new passwords from
- standard input, rather than from <tt>/dev/tty</tt>
- (like the <b>passwd(1)</b> program does). This option
- is to aid people writing scripts to drive smbpasswd</p></dd><dt><span class="term">-w password</span></dt><dd><p>This parameter is only available if Samba
+ standard input, rather than from <TT
+CLASS="FILENAME"
+>/dev/tty</TT
+>
+ (like the <B
+CLASS="COMMAND"
+>passwd(1)</B
+> program does). This option
+ is to aid people writing scripts to drive smbpasswd</P
+></DD
+><DT
+>-w password</DT
+><DD
+><P
+>This parameter is only available if Samba
has been configured to use the experimental
- <b>--with-ldapsam</b> option. The <i><tt>-w</tt></i>
+ <B
+CLASS="COMMAND"
+>--with-ldapsam</B
+> option. The <TT
+CLASS="PARAMETER"
+><I
+>-w</I
+></TT
+>
switch is used to specify the password to be used with the
- <a href="smb.conf.5.html#LDAPADMINDN" target="_top"><i><tt>ldap admin
- dn</tt></i></a>. Note that the password is stored in
- the <tt>secrets.tdb</tt> and is keyed off
- of the admin's DN. This means that if the value of <i><tt>ldap
- admin dn</tt></i> ever changes, the password will need to be
+ <A
+HREF="smb.conf.5.html#LDAPADMINDN"
+TARGET="_top"
+><TT
+CLASS="PARAMETER"
+><I
+>ldap admin
+ dn</I
+></TT
+></A
+>. Note that the password is stored in
+ the <TT
+CLASS="FILENAME"
+>private/secrets.tdb</TT
+> and is keyed off
+ of the admin's DN. This means that if the value of <TT
+CLASS="PARAMETER"
+><I
+>ldap
+ admin dn</I
+></TT
+> ever changes, the password will need to be
manually updated as well.
- </p></dd><dt><span class="term">-i</span></dt><dd><p>This option tells smbpasswd that the account
+ </P
+></DD
+><DT
+>-i</DT
+><DD
+><P
+>This option tells smbpasswd that the account
being changed is an interdomain trust account. Currently this is used
when Samba is being used as an NT Primary Domain Controller.
- The account contains the info about another trusted domain.</p><p>This option is only available when running smbpasswd as root.
- </p></dd><dt><span class="term">-L</span></dt><dd><p>Run in local mode.</p></dd><dt><span class="term">username</span></dt><dd><p>This specifies the username for all of the
- <span class="emphasis"><em>root only</em></span> options to operate on. Only root
+ The account contains the info about another trusted domain.</P
+><P
+>This option is only available when running smbpasswd as root.
+ </P
+></DD
+><DT
+>-L</DT
+><DD
+><P
+>Run in local mode.</P
+></DD
+><DT
+>username</DT
+><DD
+><P
+>This specifies the username for all of the
+ <I
+CLASS="EMPHASIS"
+>root only</I
+> options to operate on. Only root
can specify this parameter as only root has the permission needed
to modify attributes directly in the local smbpasswd file.
- </p></dd></dl></div></div><div class="refsect1" lang="en"><h2>NOTES</h2><p>Since <b>smbpasswd</b> works in client-server
+ </P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN173"
+></A
+><H2
+>NOTES</H2
+><P
+>Since <B
+CLASS="COMMAND"
+>smbpasswd</B
+> works in client-server
mode communicating with a local smbd for a non-root user then
the smbd daemon must be running for this to work. A common problem
- is to add a restriction to the hosts that may access the <b>
- smbd</b> running on the local machine by specifying either <i><tt>allow
- hosts</tt></i> or <i><tt>deny hosts</tt></i> entry in
- the <a href="smb.conf.5.html">smb.conf(5)</a> file and neglecting to
- allow &quot;localhost&quot; access to the smbd. </p><p>In addition, the smbpasswd command is only useful if Samba
- has been set up to use encrypted passwords. See the document <a href="pwencrypt.html" target="_top">
- &quot;LanMan and NT Password Encryption in Samba&quot;</a> in the docs directory for details
- on how to do this. </p></div><div class="refsect1" lang="en"><h2>VERSION</h2><p>This man page is correct for version 3.0 of the Samba suite.</p></div><div class="refsect1" lang="en"><h2>SEE ALSO</h2><p><a href="smbpasswd.5.html">smbpasswd(5)</a>, <a href="Samba.7.html">Samba(7)</a>.</p></div><div class="refsect1" lang="en"><h2>AUTHOR</h2><p>The original Samba software and related utilities
+ is to add a restriction to the hosts that may access the <B
+CLASS="COMMAND"
+> smbd</B
+> running on the local machine by specifying a
+ <TT
+CLASS="PARAMETER"
+><I
+>allow hosts</I
+></TT
+> or <TT
+CLASS="PARAMETER"
+><I
+>deny hosts</I
+></TT
+>
+ entry in the <TT
+CLASS="FILENAME"
+>smb.conf</TT
+> file and neglecting to
+ allow "localhost" access to the smbd. </P
+><P
+>In addition, the smbpasswd command is only useful if Samba
+ has been set up to use encrypted passwords. See the file
+ <TT
+CLASS="FILENAME"
+>ENCRYPTION.txt</TT
+> in the docs directory for details
+ on how to do this. </P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN183"
+></A
+><H2
+>VERSION</H2
+><P
+>This man page is correct for version 3.0 of
+ the Samba suite.</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN186"
+></A
+><H2
+>SEE ALSO</H2
+><P
+><A
+HREF="smbpasswd.5.html"
+TARGET="_top"
+><TT
+CLASS="FILENAME"
+>smbpasswd(5)</TT
+></A
+>,
+ <A
+HREF="samba.7.html"
+TARGET="_top"
+>samba(7)</A
+>
+ </P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN192"
+></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.
+ to the way the Linux kernel is developed.</P
+><P
+>The original Samba man pages were written by Karl Auer.
The man page sources were converted to YODL format (another
- excellent piece of Open Source software, available at <a href="ftp://ftp.icce.rug.nl/pub/unix/" target="_top">
- ftp://ftp.icce.rug.nl/pub/unix/</a>) and updated for the Samba 2.0
+ excellent piece of Open Source software, available at
+ <A
+HREF="ftp://ftp.icce.rug.nl/pub/unix/"
+TARGET="_top"
+> ftp://ftp.icce.rug.nl/pub/unix/</A
+>) and updated for the Samba 2.0
release by Jeremy Allison. The conversion to DocBook for
- Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2
- for Samba 3.0 was done by Alexander Bokovoy.</p></div></div></body></html>
+ Samba 2.2 was done by Gerald Carter</P
+></DIV
+></BODY
+></HTML
+> \ No newline at end of file
diff --git a/docs/htmldocs/smbsh.1.html b/docs/htmldocs/smbsh.1.html
index 942f617920..bab2b45cdd 100644
--- a/docs/htmldocs/smbsh.1.html
+++ b/docs/htmldocs/smbsh.1.html
@@ -1,110 +1,467 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>smbsh</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="smbsh.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>smbsh &#8212; Allows access to Windows NT filesystem
- using UNIX commands</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><tt>smbsh</tt> [-W workgroup] [-U username] [-P prefix] [-R &lt;name resolve order&gt;] [-d &lt;debug level&gt;] [-l logfile] [-L libdir]</p></div></div><div class="refsect1" lang="en"><h2>DESCRIPTION</h2><p>This tool is part of the <a href="Samba.7.html">Samba(7)</a> suite.</p><p><b>smbsh</b> allows you to access an NT filesystem
- using UNIX commands such as <b>ls</b>, <b>
- egrep</b>, and <b>rcp</b>. You must use a
- shell that is dynamically linked in order for <b>smbsh</b>
- to work correctly.</p></div><div class="refsect1" lang="en"><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-W WORKGROUP</span></dt><dd><p>Override the default workgroup specified in the
- workgroup parameter of the <a href="smb.conf.5.html">smb.conf(5)</a> file
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
+<HTML
+><HEAD
+><TITLE
+>smbsh</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"></HEAD
+><BODY
+CLASS="REFENTRY"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><H1
+><A
+NAME="SMBSH">smbsh</H1
+><DIV
+CLASS="REFNAMEDIV"
+><A
+NAME="AEN5"
+></A
+><H2
+>Name</H2
+>smbsh&nbsp;--&nbsp;Allows access to Windows NT filesystem
+ using UNIX commands</DIV
+><DIV
+CLASS="REFSYNOPSISDIV"
+><A
+NAME="AEN8"><H2
+>Synopsis</H2
+><P
+><B
+CLASS="COMMAND"
+>smbsh</B
+> [-W workgroup] [-U username] [-P prefix] [-R &#60;name resolve order&#62;] [-d &#60;debug level&#62;] [-l logfile] [-L libdir]</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN18"
+></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"
+>smbsh</B
+> allows you to access an NT filesystem
+ using UNIX commands such as <B
+CLASS="COMMAND"
+>ls</B
+>, <B
+CLASS="COMMAND"
+> egrep</B
+>, and <B
+CLASS="COMMAND"
+>rcp</B
+>. You must use a
+ shell that is dynamically linked in order for <B
+CLASS="COMMAND"
+>smbsh</B
+>
+ to work correctly.</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN28"
+></A
+><H2
+>OPTIONS</H2
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>-W WORKGROUP</DT
+><DD
+><P
+>Override the default workgroup specified in the
+ workgroup parameter of the <TT
+CLASS="FILENAME"
+>smb.conf</TT
+> file
for this session. This may be needed to connect to some
- servers. </p></dd><dt><span class="term">-U username[%pass]</span></dt><dd><p>Sets the SMB username or username and password.
+ servers. </P
+></DD
+><DT
+>-U username[%pass]</DT
+><DD
+><P
+>Sets the SMB username or username and password.
If this option is not specified, the user will be prompted for
both the username and the password. If %pass is not specified,
the user will be prompted for the password.
- </p></dd><dt><span class="term">-P prefix</span></dt><dd><p>This option allows
+ </P
+></DD
+><DT
+>-P prefix</DT
+><DD
+><P
+>This option allows
the user to set the directory prefix for SMB access. The
default value if this option is not specified is
- <span class="emphasis"><em>smb</em></span>.
- </p></dd><dt><span class="term">-s &lt;configuration file&gt;</span></dt><dd><p>The file specified contains the
-configuration details required by the server. The
-information in this file includes server-specific
-information such as what printcap file to use, as well
-as descriptions of all the services that the server is
-to provide. See <a href="smb.conf.5.html" target="_top"><tt>
-smb.conf(5)</tt></a> for more information.
-The default configuration file name is determined at
-compile time.</p></dd><dt><span class="term">-d|--debug=debuglevel</span></dt><dd><p><i><tt>debuglevel</tt></i> is an integer
-from 0 to 10. The default value if this parameter is
-not specified is zero.</p><p>The higher this value, the more detail will be
-logged to the log files about the activities of the
-server. At level 0, only critical errors and serious
-warnings will be logged. Level 1 is a reasonable level for
-day to day running - it generates a small amount of
-information about operations carried out.</p><p>Levels above 1 will generate considerable
-amounts of log data, and should only be used when
-investigating a problem. Levels above 3 are designed for
-use only by developers and generate HUGE amounts of log
-data, most of which is extremely cryptic.</p><p>Note that specifying this parameter here will
-override the <a href="smb.conf.5.html#loglevel" target="_top">log
-level</a> parameter in the <a href="smb.conf.5.html" target="_top">
-<tt>smb.conf(5)</tt></a> file.</p></dd><dt><span class="term">-R &lt;name resolve order&gt;</span></dt><dd><p>This option is used to determine what naming
-services and in what order to resolve
-host names to IP addresses. The option takes a space-separated
-string of different name resolution options.</p><p>The options are: &quot;lmhosts&quot;, &quot;host&quot;, &quot;wins&quot; and &quot;bcast&quot;.
-They cause names to be resolved as follows :</p><div class="itemizedlist"><ul type="disc"><li><p><tt>lmhosts</tt>:
-Lookup an IP address in the Samba lmhosts file. If the
-line in lmhosts has no name type attached to the
-NetBIOS name
-(see the <a href="lmhosts.5.html">lmhosts(5)</a> for details)
-then any name type matches for lookup.
-</p></li><li><p><tt>host</tt>:
-Do a standard host name to IP address resolution, using
-the system <tt>/etc/hosts</tt>, NIS, or DNS
-lookups. This method of name resolution is operating
-system dependent, for instance on IRIX or Solaris this
-may be controlled by the <tt>/etc/nsswitch.conf
-</tt> file). Note that this method is only used
-if the NetBIOS name type being queried is the 0x20
-(server) name type, otherwise it is ignored.
-</p></li><li><p><tt>wins</tt>:
-Query a name with the IP address listed in the
-<i><tt>wins server</tt></i> parameter. If no
-WINS server has been specified this method will be
-ignored.
-</p></li><li><p><tt>bcast</tt>:
-Do a broadcast on each of the known local interfaces
-listed in the <i><tt>interfaces</tt></i>
-parameter. This is the least reliable of the name
-resolution methods as it depends on the target host
-being on a locally connected subnet.
-</p></li></ul></div><p>If this parameter is not set then the name resolve order
-defined in the <a href="smb.conf.5.html">smb.conf(5)</a> file parameter
-(<i><tt>name resolve order</tt></i>) will be used. </p><p>The default order is lmhosts, host, wins, bcast. Without
-this parameter or any entry in the <i><tt>name resolve order
-</tt></i> parameter of the <a href="smb.conf.5.html">smb.conf(5)</a> file, the name resolution methods
-will be attempted in this order. </p></dd><dt><span class="term">-L libdir</span></dt><dd><p>This parameter specifies the location of the
- shared libraries used by <b>smbsh</b>. The default
+ <I
+CLASS="EMPHASIS"
+>smb</I
+>.
+ </P
+></DD
+><DT
+>-R &#60;name resolve order&#62;</DT
+><DD
+><P
+>This option is used to determine what naming
+ services and in what order to resolve
+ host names to IP addresses. The option takes a space-separated
+ string of different name resolution options.</P
+><P
+>The options are :"lmhosts", "host", "wins" and "bcast".
+ They cause names to be resolved as follows :</P
+><P
+></P
+><UL
+><LI
+><P
+><TT
+CLASS="CONSTANT"
+>lmhosts</TT
+> :
+ Lookup an IP address in the Samba lmhosts file. If the
+ line in lmhosts has no name type attached to the
+ NetBIOS name
+ (see the <A
+HREF="lmhosts.5.html"
+TARGET="_top"
+>lmhosts(5)</A
+>
+ for details) then any name type matches for lookup.
+ </P
+></LI
+><LI
+><P
+><TT
+CLASS="CONSTANT"
+>host</TT
+> :
+ Do a standard host name to IP address resolution, using
+ the system <TT
+CLASS="FILENAME"
+>/etc/hosts</TT
+>, NIS, or DNS
+ lookups. This method of name resolution is operating
+ system dependent, for instance on IRIX or Solaris this
+ may be controlled by the <TT
+CLASS="FILENAME"
+>/etc/nsswitch.conf
+ </TT
+> file). Note that this method is only used
+ if the NetBIOS name type being queried is the 0x20
+ (server) name type, otherwise it is ignored.
+ </P
+></LI
+><LI
+><P
+><TT
+CLASS="CONSTANT"
+>wins</TT
+> :
+ Query a name with the IP address listed in the
+ <TT
+CLASS="PARAMETER"
+><I
+>wins server</I
+></TT
+> parameter. If no
+ WINS server has been specified this method will be
+ ignored.
+ </P
+></LI
+><LI
+><P
+><TT
+CLASS="CONSTANT"
+>bcast</TT
+> :
+ Do a broadcast on each of the known local interfaces
+ listed in the <TT
+CLASS="PARAMETER"
+><I
+>interfaces</I
+></TT
+>
+ parameter. This is the least reliable of the name
+ resolution methods as it depends on the target host
+ being on a locally connected subnet.
+ </P
+></LI
+></UL
+><P
+>If this parameter is not set then the name resolve order
+ defined in the <TT
+CLASS="FILENAME"
+>smb.conf</TT
+> file parameter
+ (name resolve order) will be used. </P
+><P
+>The default order is lmhosts, host, wins, bcast. Without
+ this parameter or any entry in the <TT
+CLASS="PARAMETER"
+><I
+>name resolve order
+ </I
+></TT
+> parameter of the <TT
+CLASS="FILENAME"
+>smb.conf</TT
+>
+ file, the name resolution methods will be attempted in this
+ order. </P
+></DD
+><DT
+>-d &#60;debug level&#62;</DT
+><DD
+><P
+>debug level is an integer from 0 to 10.</P
+><P
+>The default value if this parameter is not specified
+ is zero.</P
+><P
+>The higher this value, the more detail will be logged
+ about the activities of <B
+CLASS="COMMAND"
+>nmblookup</B
+>. At level
+ 0, only critical errors and serious warnings will be logged.
+ </P
+></DD
+><DT
+>-l logfilename</DT
+><DD
+><P
+>If specified causes all debug messages to be
+ written to the file specified by <TT
+CLASS="REPLACEABLE"
+><I
+>logfilename
+ </I
+></TT
+>. If not specified then all messages will be
+ written to<TT
+CLASS="REPLACEABLE"
+><I
+>stderr</I
+></TT
+>.
+ </P
+></DD
+><DT
+>-L libdir</DT
+><DD
+><P
+>This parameter specifies the location of the
+ shared libraries used by <B
+CLASS="COMMAND"
+>smbsh</B
+>. The default
value is specified at compile time.
- </p></dd></dl></div></div><div class="refsect1" lang="en"><h2>EXAMPLES</h2><p>To use the <b>smbsh</b> command, execute <b>
- smbsh</b> from the prompt and enter the username and password
+ </P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN91"
+></A
+><H2
+>EXAMPLES</H2
+><P
+>To use the <B
+CLASS="COMMAND"
+>smbsh</B
+> command, execute <B
+CLASS="COMMAND"
+> smbsh</B
+> from the prompt and enter the username and password
that authenticates you to the machine running the Windows NT
- operating system.
-</p><pre class="programlisting">
-<tt>system% </tt><b><tt>smbsh</tt></b>
-<tt>Username: </tt><b><tt>user</tt></b>
-<tt>Password: </tt><b><tt>XXXXXXX</tt></b>
-</pre><p>Any dynamically linked command you execute from
- this shell will access the <tt>/smb</tt> directory
- using the smb protocol. For example, the command <b>ls /smb
- </b> will show a list of workgroups. The command
- <b>ls /smb/MYGROUP </b> will show all the machines in
+ operating system.</P
+><P
+><TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><PRE
+CLASS="PROGRAMLISTING"
+> <TT
+CLASS="PROMPT"
+>system% </TT
+><TT
+CLASS="USERINPUT"
+><B
+>smbsh</B
+></TT
+>
+ <TT
+CLASS="PROMPT"
+>Username: </TT
+><TT
+CLASS="USERINPUT"
+><B
+>user</B
+></TT
+>
+ <TT
+CLASS="PROMPT"
+>Password: </TT
+><TT
+CLASS="USERINPUT"
+><B
+>XXXXXXX</B
+></TT
+>
+ </PRE
+></TD
+></TR
+></TABLE
+></P
+><P
+>Any dynamically linked command you execute from
+ this shell will access the <TT
+CLASS="FILENAME"
+>/smb</TT
+> directory
+ using the smb protocol. For example, the command <B
+CLASS="COMMAND"
+>ls /smb
+ </B
+> will show a list of workgroups. The command
+ <B
+CLASS="COMMAND"
+>ls /smb/MYGROUP </B
+> will show all the machines in
the workgroup MYGROUP. The command
- <b>ls /smb/MYGROUP/&lt;machine-name&gt;</b> will show the share
- names for that machine. You could then, for example, use the <b>
- cd</b> command to change directories, <b>vi</b> to
- edit files, and <b>rcp</b> to copy files.</p></div><div class="refsect1" lang="en"><h2>VERSION</h2><p>This man page is correct for version 3.0 of the Samba suite.</p></div><div class="refsect1" lang="en"><h2>BUGS</h2><p><b>smbsh</b> works by intercepting the standard
- libc calls with the dynamically loaded versions in <tt>
- smbwrapper.o</tt>. Not all calls have been &quot;wrapped&quot;, so
- some programs may not function correctly under <b>smbsh
- </b>.</p><p>Programs which are not dynamically linked cannot make
- use of <b>smbsh</b>'s functionality. Most versions
- of UNIX have a <b>file</b> command that will
- describe how a program was linked.</p></div><div class="refsect1" lang="en"><h2>SEE ALSO</h2><p><a href="smbd.8.html">smbd(8)</a>, <a href="smb.conf.5.html">smb.conf(5)</a></p></div><div class="refsect1" lang="en"><h2>AUTHOR</h2><p>The original Samba software and related utilities
+ <B
+CLASS="COMMAND"
+>ls /smb/MYGROUP/&#60;machine-name&#62;</B
+> will show the share
+ names for that machine. You could then, for example, use the <B
+CLASS="COMMAND"
+> cd</B
+> command to change directories, <B
+CLASS="COMMAND"
+>vi</B
+> to
+ edit files, and <B
+CLASS="COMMAND"
+>rcp</B
+> to copy files.</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN112"
+></A
+><H2
+>VERSION</H2
+><P
+>This man page is correct for version 3.0 of
+ the Samba suite.</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN115"
+></A
+><H2
+>BUGS</H2
+><P
+><B
+CLASS="COMMAND"
+>smbsh</B
+> works by intercepting the standard
+ libc calls with the dynamically loaded versions in <TT
+CLASS="FILENAME"
+> smbwrapper.o</TT
+>. Not all calls have been "wrapped", so
+ some programs may not function correctly under <B
+CLASS="COMMAND"
+>smbsh
+ </B
+>.</P
+><P
+>Programs which are not dynamically linked cannot make
+ use of <B
+CLASS="COMMAND"
+>smbsh</B
+>'s functionality. Most versions
+ of UNIX have a <B
+CLASS="COMMAND"
+>file</B
+> command that will
+ describe how a program was linked.</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN124"
+></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="AEN130"
+></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.
+ to the way the Linux kernel is developed.</P
+><P
+>The original Samba man pages were written by Karl Auer.
The man page sources were converted to YODL format (another
- excellent piece of Open Source software, available at <a href="ftp://ftp.icce.rug.nl/pub/unix/" target="_top">
- ftp://ftp.icce.rug.nl/pub/unix/</a>) and updated for the Samba 2.0
+ excellent piece of Open Source software, available at
+ <A
+HREF="ftp://ftp.icce.rug.nl/pub/unix/"
+TARGET="_top"
+> ftp://ftp.icce.rug.nl/pub/unix/</A
+>) and updated for the Samba 2.0
release by Jeremy Allison. The conversion to DocBook for
- Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2
- for Samba 3.0 was done by Alexander Bokovoy.</p></div></div></body></html>
+ Samba 2.2 was done by Gerald Carter</P
+></DIV
+></BODY
+></HTML
+> \ No newline at end of file
diff --git a/docs/htmldocs/smbspool.8.html b/docs/htmldocs/smbspool.8.html
index fffd779dcf..8dc2fbbd63 100644
--- a/docs/htmldocs/smbspool.8.html
+++ b/docs/htmldocs/smbspool.8.html
@@ -1,35 +1,227 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>smbspool</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="smbspool.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>smbspool &#8212; send a print file to an SMB printer</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><tt>smbspool</tt> {job} {user} {title} {copies} {options} [filename]</p></div></div><div class="refsect1" lang="en"><h2>DESCRIPTION</h2><p>This tool is part of the <a href="Samba.7.html">Samba(7)</a> suite.</p><p>smbspool is a very small print spooling program that
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<HTML
+><HEAD
+><TITLE
+>smbspool</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.77"></HEAD
+><BODY
+CLASS="REFENTRY"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><H1
+><A
+NAME="SMBSPOOL"
+></A
+>smbspool</H1
+><DIV
+CLASS="REFNAMEDIV"
+><A
+NAME="AEN5"
+></A
+><H2
+>Name</H2
+>smbspool&nbsp;--&nbsp;send a print file to an SMB printer</DIV
+><DIV
+CLASS="REFSYNOPSISDIV"
+><A
+NAME="AEN8"
+></A
+><H2
+>Synopsis</H2
+><P
+><B
+CLASS="COMMAND"
+>smbspool</B
+> [job] [user] [title] [copies] [options] [filename]</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN17"
+></A
+><H2
+>DESCRIPTION</H2
+><P
+>This tool is part of the <A
+HREF="samba.7.html"
+TARGET="_top"
+> Samba</A
+> suite.</P
+><P
+>smbspool is a very small print spooling program that
sends a print file to an SMB printer. The command-line arguments
are position-dependent for compatibility with the Common UNIX
Printing System, but you can use smbspool with any printing system
- or from a program or script.</p><p><span class="emphasis"><em>DEVICE URI</em></span></p><p>smbspool specifies the destination using a Uniform Resource
- Identifier (&quot;URI&quot;) with a method of &quot;smb&quot;. This string can take
- a number of forms:</p><div class="itemizedlist"><ul type="disc"><li><p>smb://server/printer</p></li><li><p>smb://workgroup/server/printer</p></li><li><p>smb://username:password@server/printer</p></li><li><p>smb://username:password@workgroup/server/printer</p></li></ul></div><p>smbspool tries to get the URI from argv[0]. If argv[0]
- contains the name of the program then it looks in the <tt>
- DEVICE_URI</tt> environment variable.</p><p>Programs using the <b>exec(2)</b> functions can
+ or from a program or script.</P
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>DEVICE URI</I
+></SPAN
+></P
+><P
+>smbspool specifies the destination using a Uniform Resource
+ Identifier ("URI") with a method of "smb". This string can take
+ a number of forms:</P
+><P
+></P
+><UL
+><LI
+><P
+>smb://server/printer</P
+></LI
+><LI
+><P
+>smb://workgroup/server/printer</P
+></LI
+><LI
+><P
+>smb://username:password@server/printer</P
+></LI
+><LI
+><P
+>smb://username:password@workgroup/server/printer
+ </P
+></LI
+></UL
+><P
+>smbspool tries to get the URI from argv[0]. If argv[0]
+ contains the name of the program then it looks in the <TT
+CLASS="ENVAR"
+> DEVICE_URI</TT
+> environment variable.</P
+><P
+>Programs using the <B
+CLASS="COMMAND"
+>exec(2)</B
+> functions can
pass the URI in argv[0], while shell scripts must set the
- <tt>DEVICE_URI</tt> environment variable prior to
- running smbspool.</p></div><div class="refsect1" lang="en"><h2>OPTIONS</h2><div class="itemizedlist"><ul type="disc"><li><p>The job argument (argv[1]) contains the
+ <TT
+CLASS="ENVAR"
+>DEVICE_URI</TT
+> environment variable prior to
+ running smbspool.</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN39"
+></A
+><H2
+>OPTIONS</H2
+><P
+></P
+><UL
+><LI
+><P
+>The job argument (argv[1]) contains the
job ID number and is presently not used by smbspool.
- </p></li><li><p>The user argument (argv[2]) contains the
+ </P
+></LI
+><LI
+><P
+>The user argument (argv[2]) contains the
print user's name and is presently not used by smbspool.
- </p></li><li><p>The title argument (argv[3]) contains the
+ </P
+></LI
+><LI
+><P
+>The title argument (argv[3]) contains the
job title string and is passed as the remote file name
- when sending the print job.</p></li><li><p>The copies argument (argv[4]) contains
+ when sending the print job.</P
+></LI
+><LI
+><P
+>The copies argument (argv[4]) contains
the number of copies to be printed of the named file. If
no filename is provided then this argument is not used by
- smbspool.</p></li><li><p>The options argument (argv[5]) contains
+ smbspool.</P
+></LI
+><LI
+><P
+>The options argument (argv[5]) contains
the print options in a single string and is currently
- not used by smbspool.</p></li><li><p>The filename argument (argv[6]) contains the
+ not used by smbspool.</P
+></LI
+><LI
+><P
+>The filename argument (argv[6]) contains the
name of the file to print. If this argument is not specified
- then the print file is read from the standard input.</p></li></ul></div></div><div class="refsect1" lang="en"><h2>VERSION</h2><p>This man page is correct for version 3.0 of the Samba suite.</p></div><div class="refsect1" lang="en"><h2>SEE ALSO</h2><p><a href="smbd.8.html">smbd(8)</a> and <a href="Samba.7.html">Samba(7)</a>.</p></div><div class="refsect1" lang="en"><h2>AUTHOR</h2><p><b>smbspool</b> was written by Michael Sweet
- at Easy Software Products.</p><p>The original Samba software and related utilities
+ then the print file is read from the standard input.</P
+></LI
+></UL
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN54"
+></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="AEN57"
+></A
+><H2
+>SEE ALSO</H2
+><P
+><A
+HREF="smbd.8.html"
+TARGET="_top"
+><B
+CLASS="COMMAND"
+>smbd(8)</B
+></A
+>,
+ and <A
+HREF="samba.7.html"
+TARGET="_top"
+>samba(7)</A
+>.
+ </P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN63"
+></A
+><H2
+>AUTHOR</H2
+><P
+><B
+CLASS="COMMAND"
+>smbspool</B
+> was written by Michael Sweet
+ at Easy Software Products.</P
+><P
+>The original Samba software and related utilities
were created by Andrew Tridgell. Samba is now developed
by the Samba Team as an Open Source project similar
- to the way the Linux kernel is developed.</p><p>The original Samba man pages were written by Karl Auer.
+ to the way the Linux kernel is developed.</P
+><P
+>The original Samba man pages were written by Karl Auer.
The man page sources were converted to YODL format (another
- excellent piece of Open Source software, available at <a href="ftp://ftp.icce.rug.nl/pub/unix/" target="_top">
- ftp://ftp.icce.rug.nl/pub/unix/</a>) and updated for the Samba 2.0
+ excellent piece of Open Source software, available at
+ <A
+HREF="ftp://ftp.icce.rug.nl/pub/unix/"
+TARGET="_top"
+> ftp://ftp.icce.rug.nl/pub/unix/</A
+>) and updated for the Samba 2.0
release by Jeremy Allison. The conversion to DocBook for
- Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2
- for Samba 3.0 was done by Alexander Bokovoy.</p></div></div></body></html>
+ Samba 2.2 was done by Gerald Carter</P
+></DIV
+></BODY
+></HTML
+> \ No newline at end of file
diff --git a/docs/htmldocs/smbstatus.1.html b/docs/htmldocs/smbstatus.1.html
index a8ae9132ec..fb7e14fadd 100644
--- a/docs/htmldocs/smbstatus.1.html
+++ b/docs/htmldocs/smbstatus.1.html
@@ -1,44 +1,223 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>smbstatus</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="smbstatus.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>smbstatus &#8212; report on current Samba connections</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><tt>smbstatus</tt> [-P] [-b] [-d &lt;debug level&gt;] [-v] [-L] [-B] [-p] [-S] [-s &lt;configuration file&gt;] [-u &lt;username&gt;]</p></div></div><div class="refsect1" lang="en"><h2>DESCRIPTION</h2><p>This tool is part of the <a href="Samba.7.html">Samba(7)</a> suite.</p><p><b>smbstatus</b> is a very simple program to
- list the current Samba connections.</p></div><div class="refsect1" lang="en"><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-P|--profile</span></dt><dd><p>If samba has been compiled with the
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<HTML
+><HEAD
+><TITLE
+>smbstatus</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.77"></HEAD
+><BODY
+CLASS="REFENTRY"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><H1
+><A
+NAME="SMBSTATUS"
+></A
+>smbstatus</H1
+><DIV
+CLASS="REFNAMEDIV"
+><A
+NAME="AEN5"
+></A
+><H2
+>Name</H2
+>smbstatus&nbsp;--&nbsp;report on current Samba connections</DIV
+><DIV
+CLASS="REFSYNOPSISDIV"
+><A
+NAME="AEN8"
+></A
+><H2
+>Synopsis</H2
+><P
+><B
+CLASS="COMMAND"
+>smbstatus</B
+> [-P] [-b] [-d &lt;debug level&gt;] [-v] [-L] [-B] [-p] [-S] [-s &lt;configuration file&gt;] [-u &lt;username&gt;]</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN21"
+></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"
+>smbstatus</B
+> is a very simple program to
+ list the current Samba connections.</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN27"
+></A
+><H2
+>OPTIONS</H2
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>-P|--profile</DT
+><DD
+><P
+>If samba has been compiled with the
profiling option, print only the contents of the profiling
- shared memory area.</p></dd><dt><span class="term">-b|--brief</span></dt><dd><p>gives brief output.</p></dd><dt><span class="term">-V</span></dt><dd><p>Prints the version number for
-<b>smbd</b>.</p></dd><dt><span class="term">-s &lt;configuration file&gt;</span></dt><dd><p>The file specified contains the
-configuration details required by the server. The
-information in this file includes server-specific
-information such as what printcap file to use, as well
-as descriptions of all the services that the server is
-to provide. See <a href="smb.conf.5.html" target="_top"><tt>
-smb.conf(5)</tt></a> for more information.
-The default configuration file name is determined at
-compile time.</p></dd><dt><span class="term">-d|--debug=debuglevel</span></dt><dd><p><i><tt>debuglevel</tt></i> is an integer
-from 0 to 10. The default value if this parameter is
-not specified is zero.</p><p>The higher this value, the more detail will be
-logged to the log files about the activities of the
-server. At level 0, only critical errors and serious
-warnings will be logged. Level 1 is a reasonable level for
-day to day running - it generates a small amount of
-information about operations carried out.</p><p>Levels above 1 will generate considerable
-amounts of log data, and should only be used when
-investigating a problem. Levels above 3 are designed for
-use only by developers and generate HUGE amounts of log
-data, most of which is extremely cryptic.</p><p>Note that specifying this parameter here will
-override the <a href="smb.conf.5.html#loglevel" target="_top">log
-level</a> parameter in the <a href="smb.conf.5.html" target="_top">
-<tt>smb.conf(5)</tt></a> file.</p></dd><dt><span class="term">-l|--logfile=logbasename</span></dt><dd><p>File name for log/debug files. The extension
-<tt>&quot;.client&quot;</tt> will be appended. The log file is
-never removed by the client.
-</p></dd><dt><span class="term">-v|--verbose</span></dt><dd><p>gives verbose output.</p></dd><dt><span class="term">-L|--locks</span></dt><dd><p>causes smbstatus to only list locks.</p></dd><dt><span class="term">-B|--byterange</span></dt><dd><p>causes smbstatus to include byte range locks.
- </p></dd><dt><span class="term">-p|--processes</span></dt><dd><p>print a list of <a href="smbd.8.html">smbd(8)</a> processes and exit.
- Useful for scripting.</p></dd><dt><span class="term">-S|--shares</span></dt><dd><p>causes smbstatus to only list shares.</p></dd><dt><span class="term">-h|--help</span></dt><dd><p>Print a summary of command line options.
-</p></dd><dt><span class="term">-u|--user=&lt;username&gt;</span></dt><dd><p>selects information relevant to
- <i><tt>username</tt></i> only.</p></dd></dl></div></div><div class="refsect1" lang="en"><h2>VERSION</h2><p>This man page is correct for version 3.0 of
- the Samba suite.</p></div><div class="refsect1" lang="en"><h2>SEE ALSO</h2><p><a href="smbd.8.html">smbd(8)</a> and <a href="smb.conf.5.html">smb.conf(5)</a>.</p></div><div class="refsect1" lang="en"><h2>AUTHOR</h2><p>The original Samba software and related utilities
+ shared memory area.</P
+></DD
+><DT
+>-b|--brief</DT
+><DD
+><P
+>gives brief output.</P
+></DD
+><DT
+>-d|--debug=&lt;debuglevel&gt;</DT
+><DD
+><P
+>sets debugging to specified level</P
+></DD
+><DT
+>-v|--verbose</DT
+><DD
+><P
+>gives verbose output.</P
+></DD
+><DT
+>-L|--locks</DT
+><DD
+><P
+>causes smbstatus to only list locks.</P
+></DD
+><DT
+>-B|--byterange</DT
+><DD
+><P
+>causes smbstatus to include byte range locks.
+ </P
+></DD
+><DT
+>-p|--processes</DT
+><DD
+><P
+>print a list of <A
+HREF="smbd.8.html"
+TARGET="_top"
+> <B
+CLASS="COMMAND"
+>smbd(8)</B
+></A
+> processes and exit.
+ Useful for scripting.</P
+></DD
+><DT
+>-S|--shares</DT
+><DD
+><P
+>causes smbstatus to only list shares.</P
+></DD
+><DT
+>-s|--conf=&lt;configuration file&gt;</DT
+><DD
+><P
+>The default configuration file name is
+ determined at compile time. The file specified contains the
+ configuration details required by the server. See <A
+HREF="smb.conf.5.html"
+TARGET="_top"
+><TT
+CLASS="FILENAME"
+>smb.conf(5)</TT
+>
+ </A
+> for more information.</P
+></DD
+><DT
+>-u|--user=&lt;username&gt;</DT
+><DD
+><P
+>selects information relevant to
+ <TT
+CLASS="PARAMETER"
+><I
+>username</I
+></TT
+> only.</P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN75"
+></A
+><H2
+>VERSION</H2
+><P
+>This man page is correct for version 3.0 of
+ the Samba suite.</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN78"
+></A
+><H2
+>SEE ALSO</H2
+><P
+><A
+HREF="smbd.8.html"
+TARGET="_top"
+><B
+CLASS="COMMAND"
+>smbd(8)</B
+></A
+> and
+ <A
+HREF="smb.conf.5.html"
+TARGET="_top"
+>smb.conf(5)</A
+>.</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN84"
+></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.
+ to the way the Linux kernel is developed.</P
+><P
+>The original Samba man pages were written by Karl Auer.
The man page sources were converted to YODL format (another
- excellent piece of Open Source software, available at <a href="ftp://ftp.icce.rug.nl/pub/unix/" target="_top">
- ftp://ftp.icce.rug.nl/pub/unix/</a>) and updated for the Samba 2.0
+ excellent piece of Open Source software, available at
+ <A
+HREF="ftp://ftp.icce.rug.nl/pub/unix/"
+TARGET="_top"
+> ftp://ftp.icce.rug.nl/pub/unix/</A
+>) and updated for the Samba 2.0
release by Jeremy Allison. The conversion to DocBook for
- Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2
- for Samba 3.0 was done by Alexander Bokovoy.</p></div></div></body></html>
+ Samba 2.2 was done by Gerald Carter</P
+></DIV
+></BODY
+></HTML
+> \ No newline at end of file
diff --git a/docs/htmldocs/smbtar.1.html b/docs/htmldocs/smbtar.1.html
index 35802edb90..d3215c6901 100644
--- a/docs/htmldocs/smbtar.1.html
+++ b/docs/htmldocs/smbtar.1.html
@@ -1,39 +1,356 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>smbtar</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="smbtar.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>smbtar &#8212; shell script for backing up SMB/CIFS shares
- directly to UNIX tape drives</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><tt>smbtar</tt> [-r] [-i] [-a] [-v] {-s server} [-p password] [-x services] [-X] [-N filename] [-b blocksize] [-d directory] [-l loglevel] [-u user] [-t tape] {filenames}</p></div></div><div class="refsect1" lang="en"><h2>DESCRIPTION</h2><p>This tool is part of the <a href="Samba.7.html">Samba(7)</a> suite.</p><p><b>smbtar</b> is a very small shell script on top
- of <a href="smbclient.1.html">smbclient(1)</a> which dumps SMB shares directly to tape.</p></div><div class="refsect1" lang="en"><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-s server</span></dt><dd><p>The SMB/CIFS server that the share resides
- upon.</p></dd><dt><span class="term">-x service</span></dt><dd><p>The share name on the server to connect to.
- The default is &quot;backup&quot;.</p></dd><dt><span class="term">-X</span></dt><dd><p>Exclude mode. Exclude filenames... from tar
- create or restore. </p></dd><dt><span class="term">-d directory</span></dt><dd><p>Change to initial <i><tt>directory
- </tt></i> before restoring / backing up files. </p></dd><dt><span class="term">-v</span></dt><dd><p>Verbose mode.</p></dd><dt><span class="term">-p password</span></dt><dd><p>The password to use to access a share.
- Default: none </p></dd><dt><span class="term">-u user</span></dt><dd><p>The user id to connect as. Default:
- UNIX login name. </p></dd><dt><span class="term">-a</span></dt><dd><p>Reset DOS archive bit mode to
- indicate file has been archived. </p></dd><dt><span class="term">-t tape</span></dt><dd><p>Tape device. May be regular file or tape
- device. Default: <i><tt>$TAPE</tt></i> environmental
- variable; if not set, a file called <tt>tar.out
- </tt>. </p></dd><dt><span class="term">-b blocksize</span></dt><dd><p>Blocking factor. Defaults to 20. See
- <b>tar(1)</b> for a fuller explanation. </p></dd><dt><span class="term">-N filename</span></dt><dd><p>Backup only files newer than filename. Could
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<HTML
+><HEAD
+><TITLE
+>smbtar</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.77"></HEAD
+><BODY
+CLASS="REFENTRY"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><H1
+><A
+NAME="SMBTAR"
+></A
+>smbtar</H1
+><DIV
+CLASS="REFNAMEDIV"
+><A
+NAME="AEN5"
+></A
+><H2
+>Name</H2
+>smbtar&nbsp;--&nbsp;shell script for backing up SMB/CIFS shares
+ directly to UNIX tape drives</DIV
+><DIV
+CLASS="REFSYNOPSISDIV"
+><A
+NAME="AEN8"
+></A
+><H2
+>Synopsis</H2
+><P
+><B
+CLASS="COMMAND"
+>smbtar</B
+> {-s server} [-p password] [-x services] [-X] [-d directory] [-u user] [-t tape] [-t tape] [-b blocksize] [-N filename] [-i] [-r] [-l loglevel] [-v] {filenames}</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN26"
+></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"
+>smbtar</B
+> is a very small shell script on top
+ of <A
+HREF="smbclient.1.html"
+TARGET="_top"
+><B
+CLASS="COMMAND"
+>smbclient(1)</B
+></A
+>
+ which dumps SMB shares directly to tape. </P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN34"
+></A
+><H2
+>OPTIONS</H2
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>-s server</DT
+><DD
+><P
+>The SMB/CIFS server that the share resides
+ upon.</P
+></DD
+><DT
+>-x service</DT
+><DD
+><P
+>The share name on the server to connect to.
+ The default is "backup".</P
+></DD
+><DT
+>-X</DT
+><DD
+><P
+>Exclude mode. Exclude filenames... from tar
+ create or restore. </P
+></DD
+><DT
+>-d directory</DT
+><DD
+><P
+>Change to initial <TT
+CLASS="PARAMETER"
+><I
+>directory
+ </I
+></TT
+> before restoring / backing up files. </P
+></DD
+><DT
+>-v</DT
+><DD
+><P
+>Verbose mode.</P
+></DD
+><DT
+>-p password</DT
+><DD
+><P
+>The password to use to access a share.
+ Default: none </P
+></DD
+><DT
+>-u user</DT
+><DD
+><P
+>The user id to connect as. Default:
+ UNIX login name. </P
+></DD
+><DT
+>-t tape</DT
+><DD
+><P
+>Tape device. May be regular file or tape
+ device. Default: <TT
+CLASS="PARAMETER"
+><I
+>$TAPE</I
+></TT
+> environmental
+ variable; if not set, a file called <TT
+CLASS="FILENAME"
+>tar.out
+ </TT
+>. </P
+></DD
+><DT
+>-b blocksize</DT
+><DD
+><P
+>Blocking factor. Defaults to 20. See
+ <B
+CLASS="COMMAND"
+>tar(1)</B
+> for a fuller explanation. </P
+></DD
+><DT
+>-N filename</DT
+><DD
+><P
+>Backup only files newer than filename. Could
be used (for example) on a log file to implement incremental
- backups. </p></dd><dt><span class="term">-i</span></dt><dd><p>Incremental mode; tar files are only backed
+ backups. </P
+></DD
+><DT
+>-i</DT
+><DD
+><P
+>Incremental mode; tar files are only backed
up if they have the archive bit set. The archive bit is reset
- after each file is read. </p></dd><dt><span class="term">-r</span></dt><dd><p>Restore. Files are restored to the share
- from the tar file. </p></dd><dt><span class="term">-l log level</span></dt><dd><p>Log (debug) level. Corresponds to the
- <i><tt>-d</tt></i> flag of <a href="smbclient.1.html">smbclient(1)</a>.</p></dd></dl></div></div><div class="refsect1" lang="en"><h2>ENVIRONMENT VARIABLES</h2><p>The <i><tt>$TAPE</tt></i> variable specifies the
+ after each file is read. </P
+></DD
+><DT
+>-r</DT
+><DD
+><P
+>Restore. Files are restored to the share
+ from the tar file. </P
+></DD
+><DT
+>-l log level</DT
+><DD
+><P
+>Log (debug) level. Corresponds to the
+ <TT
+CLASS="PARAMETER"
+><I
+>-d</I
+></TT
+> flag of <B
+CLASS="COMMAND"
+>smbclient(1)
+ </B
+>. </P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN95"
+></A
+><H2
+>ENVIRONMENT VARIABLES</H2
+><P
+>The <TT
+CLASS="PARAMETER"
+><I
+>$TAPE</I
+></TT
+> variable specifies the
default tape device to write to. May be overridden
- with the -t option. </p></div><div class="refsect1" lang="en"><h2>BUGS</h2><p>The <b>smbtar</b> script has different
- options from ordinary tar and from smbclient's tar command. </p></div><div class="refsect1" lang="en"><h2>CAVEATS</h2><p>Sites that are more careful about security may not like
+ with the -t option. </P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN99"
+></A
+><H2
+>BUGS</H2
+><P
+>The <B
+CLASS="COMMAND"
+>smbtar</B
+> script has different
+ options from ordinary tar and from smbclient's tar command. </P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN103"
+></A
+><H2
+>CAVEATS</H2
+><P
+>Sites that are more careful about security may not like
the way the script handles PC passwords. Backup and restore work
on entire shares; should work on file lists. smbtar works best
- with GNU tar and may not work well with other versions. </p></div><div class="refsect1" lang="en"><h2>DIAGNOSTICS</h2><p>See the <span class="emphasis"><em>DIAGNOSTICS</em></span> section for the <a href="smbclient.1.html">smbclient(1)</a> command.</p></div><div class="refsect1" lang="en"><h2>VERSION</h2><p>This man page is correct for version 3.0 of
- the Samba suite.</p></div><div class="refsect1" lang="en"><h2>SEE ALSO</h2><p><a href="smbd.8.html">smbd(8)</a>, <a href="smbclient.1.html">smbclient(1)</a>, <a href="smb.conf.5.html">smb.conf(5)</a>.</p></div><div class="refsect1" lang="en"><h2>AUTHOR</h2><p>The original Samba software and related utilities
+ with GNU tar and may not work well with other versions. </P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN106"
+></A
+><H2
+>DIAGNOSTICS</H2
+><P
+>See the <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>DIAGNOSTICS</I
+></SPAN
+> section for the
+ <A
+HREF="smbclient.1.html"
+TARGET="_top"
+><B
+CLASS="COMMAND"
+>smbclient(1)</B
+>
+ </A
+> command.</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN112"
+></A
+><H2
+>VERSION</H2
+><P
+>This man page is correct for version 3.0 of
+ the Samba suite.</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN115"
+></A
+><H2
+>SEE ALSO</H2
+><P
+><A
+HREF="smbd.8.html"
+TARGET="_top"
+><B
+CLASS="COMMAND"
+>smbd(8)</B
+></A
+>,
+ <A
+HREF="smbclient.1.html"
+TARGET="_top"
+><B
+CLASS="COMMAND"
+>smbclient(1)</B
+></A
+>,
+ <A
+HREF="smb.conf.5.html"
+TARGET="_top"
+>smb.conf(5)</A
+>,
+ </P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN123"
+></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><a href="mailto:poultenr@logica.co.uk" target="_top">Ricky Poulten</a>
- wrote the tar extension and this man page. The <b>smbtar</b>
- script was heavily rewritten and improved by <a href="mailto:Martin.Kraemer@mch.sni.de" target="_top">Martin Kraemer</a>. Many
+ to the way the Linux kernel is developed.</P
+><P
+><A
+HREF="mailto:poultenr@logica.co.uk"
+TARGET="_top"
+>Ricky Poulten</A
+>
+ wrote the tar extension and this man page. The <B
+CLASS="COMMAND"
+>smbtar</B
+>
+ script was heavily rewritten and improved by <A
+HREF="mailto:Martin.Kraemer@mch.sni.de"
+TARGET="_top"
+>Martin Kraemer</A
+>. Many
thanks to everyone who suggested extensions, improvements, bug
fixes, etc. The man page sources were converted to YODL format (another
- excellent piece of Open Source software, available at <a href="ftp://ftp.icce.rug.nl/pub/unix/" target="_top">
- ftp://ftp.icce.rug.nl/pub/unix/</a>) and updated for the Samba 2.0
+ excellent piece of Open Source software, available at
+ <A
+HREF="ftp://ftp.icce.rug.nl/pub/unix/"
+TARGET="_top"
+> ftp://ftp.icce.rug.nl/pub/unix/</A
+>) and updated for the Samba 2.0
release by Jeremy Allison. The conversion to DocBook for
- Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 for
- Samba 3.0 was done by Alexander Bokovoy.</p></div></div></body></html>
+ Samba 2.2 was done by Gerald Carter.</P
+></DIV
+></BODY
+></HTML
+> \ No newline at end of file
diff --git a/docs/htmldocs/smbumount.8.html b/docs/htmldocs/smbumount.8.html
index e297d448e3..993436f0c6 100644
--- a/docs/htmldocs/smbumount.8.html
+++ b/docs/htmldocs/smbumount.8.html
@@ -1,16 +1,141 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>smbumount</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="smbumount.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>smbumount &#8212; smbfs umount for normal users</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><tt>smbumount</tt> {mount-point}</p></div></div><div class="refsect1" lang="en"><h2>DESCRIPTION</h2><p>With this program, normal users can unmount smb-filesystems,
- provided that it is suid root. <b>smbumount</b> has
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<HTML
+><HEAD
+><TITLE
+>smbumount</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.77"></HEAD
+><BODY
+CLASS="REFENTRY"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><H1
+><A
+NAME="SMBUMOUNT"
+></A
+>smbumount</H1
+><DIV
+CLASS="REFNAMEDIV"
+><A
+NAME="AEN5"
+></A
+><H2
+>Name</H2
+>smbumount&nbsp;--&nbsp;smbfs umount for normal users</DIV
+><DIV
+CLASS="REFSYNOPSISDIV"
+><A
+NAME="AEN8"
+></A
+><H2
+>Synopsis</H2
+><P
+><B
+CLASS="COMMAND"
+>smbumount</B
+> {mount-point}</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN12"
+></A
+><H2
+>DESCRIPTION</H2
+><P
+>With this program, normal users can unmount smb-filesystems,
+ provided that it is suid root. <B
+CLASS="COMMAND"
+>smbumount</B
+> has
been written to give normal Linux users more control over their
resources. It is safe to install this program suid root, because only
the user who has mounted a filesystem is allowed to unmount it again.
For root it is not necessary to use smbumount. The normal umount
program works perfectly well, but it would certainly be problematic
- to make umount setuid root.</p></div><div class="refsect1" lang="en"><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">mount-point</span></dt><dd><p>The directory to unmount.</p></dd></dl></div></div><div class="refsect1" lang="en"><h2>SEE ALSO</h2><p><a href="smbmount.8.html">smbmount(8)</a></p></div><div class="refsect1" lang="en"><h2>AUTHOR</h2><p>Volker Lendecke, Andrew Tridgell, Michael H. Warfield
- and others.</p><p>The current maintainer of smbfs and the userspace
- tools <b>smbmount</b>, <b>smbumount</b>,
- and <b>smbmnt</b> is <a href="mailto:urban@teststation.com" target="_top">Urban Widmark</a>.
- The <a href="mailto:samba@samba.org" target="_top">SAMBA Mailing list</a>
+ to make umount setuid root.</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN16"
+></A
+><H2
+>OPTIONS</H2
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>mount-point</DT
+><DD
+><P
+>The directory to unmount.</P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN23"
+></A
+><H2
+>SEE ALSO</H2
+><P
+><A
+HREF="smbmount.8.html"
+TARGET="_top"
+><B
+CLASS="COMMAND"
+>smbmount(8)</B
+>
+ </A
+></P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN28"
+></A
+><H2
+>AUTHOR</H2
+><P
+>Volker Lendecke, Andrew Tridgell, Michael H. Warfield
+ and others.</P
+><P
+>The current maintainer of smbfs and the userspace
+ tools <B
+CLASS="COMMAND"
+>smbmount</B
+>, <B
+CLASS="COMMAND"
+>smbumount</B
+>,
+ and <B
+CLASS="COMMAND"
+>smbmnt</B
+> is <A
+HREF="mailto:urban@teststation.com"
+TARGET="_top"
+>Urban Widmark</A
+>.
+ The <A
+HREF="mailto:samba@samba.org"
+TARGET="_top"
+>SAMBA Mailing list</A
+>
is the preferred place to ask questions regarding these programs.
- </p><p>The conversion of this manpage for Samba 2.2 was performed
- by Gerald Carter. The conversion to DocBook XML 4.2 for Samba 3.0
- was done by Alexander Bokovoy.</p></div></div></body></html>
+ </P
+><P
+>The conversion of this manpage for Samba 2.2 was performed
+ by Gerald Carter</P
+></DIV
+></BODY
+></HTML
+> \ No newline at end of file
diff --git a/docs/htmldocs/speed.html b/docs/htmldocs/speed.html
index d2e1f2c15b..1a05706f92 100644
--- a/docs/htmldocs/speed.html
+++ b/docs/htmldocs/speed.html
@@ -1,108 +1,419 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter35.Samba performance issues</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"><link rel="home" href="index.html" title="SAMBA Project Documentation"><link rel="up" href="Appendixes.html" title="PartV.Appendixes"><link rel="previous" href="SWAT.html" title="Chapter34.SWAT - The Samba Web Admininistration Tool"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter35.Samba performance issues</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="SWAT.html">Prev</a></td><th width="60%" align="center">PartV.Appendixes</th><td width="20%" align="right"></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="speed"></a>Chapter35.Samba performance issues</h2></div><div><div class="author"><h3 class="author">Paul Cochrane</h3><div class="affiliation"><span class="orgname">Dundee Limb Fitting Centre<br></span><div class="address"><p><tt>&lt;<a href="mailto:paulc@dth.scot.nhs.uk">paulc@dth.scot.nhs.uk</a>&gt;</tt></p></div></div></div></div><div><div class="author"><h3 class="author">Jelmer R. Vernooij</h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt>&lt;<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</tt></p></div></div></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="speed.html#id2908657">Comparisons</a></dt><dt><a href="speed.html#id2908548">Socket options</a></dt><dt><a href="speed.html#id2909437">Read size</a></dt><dt><a href="speed.html#id2909480">Max xmit</a></dt><dt><a href="speed.html#id2909533">Log level</a></dt><dt><a href="speed.html#id2909556">Read raw</a></dt><dt><a href="speed.html#id2909613">Write raw</a></dt><dt><a href="speed.html#id2909655">Slow Logins</a></dt><dt><a href="speed.html#id2909676">Client tuning</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2908657"></a>Comparisons</h2></div></div><p>
-The Samba server uses TCP to talk to the client. Thus if you are
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<HTML
+><HEAD
+><TITLE
+>Samba performance issues</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
+REL="HOME"
+TITLE="SAMBA Project Documentation"
+HREF="samba-howto-collection.html"><LINK
+REL="UP"
+TITLE="Optional configuration"
+HREF="optional.html"><LINK
+REL="PREVIOUS"
+TITLE="Group mapping HOWTO"
+HREF="groupmapping.html"><LINK
+REL="NEXT"
+TITLE="Appendixes"
+HREF="appendixes.html"></HEAD
+><BODY
+CLASS="CHAPTER"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><TABLE
+SUMMARY="Header navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>SAMBA Project Documentation</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="groupmapping.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+></TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="appendixes.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="CHAPTER"
+><H1
+><A
+NAME="SPEED">Chapter 22. Samba performance issues</H1
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN3055">22.1. Comparisons</H1
+><P
+>The Samba server uses TCP to talk to the client. Thus if you are
trying to see if it performs well you should really compare it to
programs that use the same protocol. The most readily available
programs for file transfer that use TCP are ftp or another TCP based
-SMB server.
-</p><p>
-If you want to test against something like a NT or WfWg server then
+SMB server.</P
+><P
+>If you want to test against something like a NT or WfWg server then
you will have to disable all but TCP on either the client or
server. Otherwise you may well be using a totally different protocol
-(such as Netbeui) and comparisons may not be valid.
-</p><p>
-Generally you should find that Samba performs similarly to ftp at raw
+(such as Netbeui) and comparisons may not be valid.</P
+><P
+>Generally you should find that Samba performs similarly to ftp at raw
transfer speed. It should perform quite a bit faster than NFS,
-although this very much depends on your system.
-</p><p>
-Several people have done comparisons between Samba and Novell, NFS or
+although this very much depends on your system.</P
+><P
+>Several people have done comparisons between Samba and Novell, NFS or
WinNT. In some cases Samba performed the best, in others the worst. I
suspect the biggest factor is not Samba vs some other system but the
hardware and drivers used on the various systems. Given similar
hardware Samba should certainly be competitive in speed with other
-systems.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2908548"></a>Socket options</h2></div></div><p>
-There are a number of socket options that can greatly affect the
-performance of a TCP based server like Samba.
-</p><p>
-The socket options that Samba uses are settable both on the command
-line with the -O option, or in the smb.conf file.
-</p><p>
-The <b>socket options</b> section of the <tt>smb.conf</tt> manual page describes how
-to set these and gives recommendations.
-</p><p>
-Getting the socket options right can make a big difference to your
+systems.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN3061">22.2. Socket options</H1
+><P
+>There are a number of socket options that can greatly affect the
+performance of a TCP based server like Samba.</P
+><P
+>The socket options that Samba uses are settable both on the command
+line with the -O option, or in the smb.conf file.</P
+><P
+>The "socket options" section of the smb.conf manual page describes how
+to set these and gives recommendations.</P
+><P
+>Getting the socket options right can make a big difference to your
performance, but getting them wrong can degrade it by just as
-much. The correct settings are very dependent on your local network.
-</p><p>
-The socket option TCP_NODELAY is the one that seems to make the
+much. The correct settings are very dependent on your local network.</P
+><P
+>The socket option TCP_NODELAY is the one that seems to make the
biggest single difference for most networks. Many people report that
-adding <b>socket options = TCP_NODELAY</b> doubles the read
-performance of a Samba drive. The best explanation I have seen for this is
-that the Microsoft TCP/IP stack is slow in sending tcp ACKs.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2909437"></a>Read size</h2></div></div><p>
-The option <b>read size</b> affects the overlap of disk
-reads/writes with network reads/writes. If the amount of data being
-transferred in several of the SMB commands (currently SMBwrite, SMBwriteX and
+adding "socket options = TCP_NODELAY" doubles the read performance of
+a Samba drive. The best explanation I have seen for this is that the
+Microsoft TCP/IP stack is slow in sending tcp ACKs.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN3068">22.3. Read size</H1
+><P
+>The option "read size" affects the overlap of disk reads/writes with
+network reads/writes. If the amount of data being transferred in
+several of the SMB commands (currently SMBwrite, SMBwriteX and
SMBreadbraw) is larger than this value then the server begins writing
the data before it has received the whole packet from the network, or
in the case of SMBreadbraw, it begins writing to the network before
-all the data has been read from disk.
-</p><p>
-This overlapping works best when the speeds of disk and network access
+all the data has been read from disk.</P
+><P
+>This overlapping works best when the speeds of disk and network access
are similar, having very little effect when the speed of one is much
-greater than the other.
-</p><p>
-The default value is 16384, but very little experimentation has been
+greater than the other.</P
+><P
+>The default value is 16384, but very little experimentation has been
done yet to determine the optimal value, and it is likely that the best
value will vary greatly between systems anyway. A value over 65536 is
-pointless and will cause you to allocate memory unnecessarily.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2909480"></a>Max xmit</h2></div></div><p>
-At startup the client and server negotiate a <b>maximum transmit</b> size,
+pointless and will cause you to allocate memory unnecessarily.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN3073">22.4. Max xmit</H1
+><P
+>At startup the client and server negotiate a "maximum transmit" size,
which limits the size of nearly all SMB commands. You can set the
-maximum size that Samba will negotiate using the <b>max xmit = </b> option
-in <tt>smb.conf</tt>. Note that this is the maximum size of SMB requests that
+maximum size that Samba will negotiate using the "max xmit = " option
+in smb.conf. Note that this is the maximum size of SMB request that
Samba will accept, but not the maximum size that the *client* will accept.
The client maximum receive size is sent to Samba by the client and Samba
-honours this limit.
-</p><p>
-It defaults to 65536 bytes (the maximum), but it is possible that some
+honours this limit.</P
+><P
+>It defaults to 65536 bytes (the maximum), but it is possible that some
clients may perform better with a smaller transmit unit. Trying values
-of less than 2048 is likely to cause severe problems.
-</p><p>
-In most cases the default is the best option.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2909533"></a>Log level</h2></div></div><p>
-If you set the log level (also known as <b>debug level</b>) higher than 2
+of less than 2048 is likely to cause severe problems.</P
+><P
+>In most cases the default is the best option.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN3078">22.5. Log level</H1
+><P
+>If you set the log level (also known as "debug level") higher than 2
then you may suffer a large drop in performance. This is because the
server flushes the log file after each operation, which can be very
-expensive.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2909556"></a>Read raw</h2></div></div><p>
-The <b>read raw</b> operation is designed to be an optimised, low-latency
+expensive. </P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN3081">22.6. Read raw</H1
+><P
+>The "read raw" operation is designed to be an optimised, low-latency
file read operation. A server may choose to not support it,
-however. and Samba makes support for <b>read raw</b> optional, with it
-being enabled by default.
-</p><p>
-In some cases clients don't handle <b>read raw</b> very well and actually
+however. and Samba makes support for "read raw" optional, with it
+being enabled by default.</P
+><P
+>In some cases clients don't handle "read raw" very well and actually
get lower performance using it than they get using the conventional
-read operations.
-</p><p>
-So you might like to try <b>read raw = no</b> and see what happens on your
+read operations. </P
+><P
+>So you might like to try "read raw = no" and see what happens on your
network. It might lower, raise or not affect your performance. Only
-testing can really tell.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2909613"></a>Write raw</h2></div></div><p>
-The <b>write raw</b> operation is designed to be an optimised, low-latency
+testing can really tell.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN3086">22.7. Write raw</H1
+><P
+>The "write raw" operation is designed to be an optimised, low-latency
file write operation. A server may choose to not support it,
-however. and Samba makes support for <b>write raw</b> optional, with it
-being enabled by default.
-</p><p>
-Some machines may find <b>write raw</b> slower than normal write, in which
-case you may wish to change this option.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2909655"></a>Slow Logins</h2></div></div><p>
-Slow logins are almost always due to the password checking time. Using
-the lowest practical <b>password level</b> will improve things.
-</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2909676"></a>Client tuning</h2></div></div><p>
-Often a speed problem can be traced to the client. The client (for
+however. and Samba makes support for "write raw" optional, with it
+being enabled by default.</P
+><P
+>Some machines may find "write raw" slower than normal write, in which
+case you may wish to change this option.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN3090">22.8. Slow Clients</H1
+><P
+>One person has reported that setting the protocol to COREPLUS rather
+than LANMAN2 gave a dramatic speed improvement (from 10k/s to 150k/s).</P
+><P
+>I suspect that his PC's (386sx16 based) were asking for more data than
+they could chew. I suspect a similar speed could be had by setting
+"read raw = no" and "max xmit = 2048", instead of changing the
+protocol. Lowering the "read size" might also help.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN3094">22.9. Slow Logins</H1
+><P
+>Slow logins are almost always due to the password checking time. Using
+the lowest practical "password level" will improve things a lot. You
+could also enable the "UFC crypt" option in the Makefile.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN3097">22.10. Client tuning</H1
+><P
+>Often a speed problem can be traced to the client. The client (for
example Windows for Workgroups) can often be tuned for better TCP
-performance. Check the sections on the various clients in
-<a href="Other-Clients.html" title="Chapter33.Samba and other CIFS clients">Samba and Other Clients</a>.
-</p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="SWAT.html">Prev</a></td><td width="20%" align="center"><a accesskey="u" href="Appendixes.html">Up</a></td><td width="40%" align="right"></td></tr><tr><td width="40%" align="left" valign="top">Chapter34.SWAT - The Samba Web Admininistration Tool</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"></td></tr></table></div></body></html>
+performance.</P
+><P
+>See your client docs for details. In particular, I have heard rumours
+that the WfWg options TCPWINDOWSIZE and TCPSEGMENTSIZE can have a
+large impact on performance.</P
+><P
+>Also note that some people have found that setting DefaultRcvWindow in
+the [MSTCP] section of the SYSTEM.INI file under WfWg to 3072 gives a
+big improvement. I don't know why.</P
+><P
+>My own experience wth DefaultRcvWindow is that I get much better
+performance with a large value (16384 or larger). Other people have
+reported that anything over 3072 slows things down enourmously. One
+person even reported a speed drop of a factor of 30 when he went from
+3072 to 8192. I don't know why.</P
+><P
+>It probably depends a lot on your hardware, and the type of unix box
+you have at the other end of the link.</P
+><P
+>Paul Cochrane has done some testing on client side tuning and come
+to the following conclusions:</P
+><P
+>Install the W2setup.exe file from www.microsoft.com. This is an
+update for the winsock stack and utilities which improve performance.</P
+><P
+>Configure the win95 TCPIP registry settings to give better
+perfomance. I use a program called MTUSPEED.exe which I got off the
+net. There are various other utilities of this type freely available.
+The setting which give the best performance for me are:</P
+><P
+></P
+><OL
+TYPE="1"
+><LI
+><P
+>MaxMTU Remove</P
+></LI
+><LI
+><P
+>RWIN Remove</P
+></LI
+><LI
+><P
+>MTUAutoDiscover Disable</P
+></LI
+><LI
+><P
+>MTUBlackHoleDetect Disable</P
+></LI
+><LI
+><P
+>Time To Live Enabled</P
+></LI
+><LI
+><P
+>Time To Live - HOPS 32</P
+></LI
+><LI
+><P
+>NDI Cache Size 0</P
+></LI
+></OL
+><P
+>I tried virtually all of the items mentioned in the document and
+the only one which made a difference to me was the socket options. It
+turned out I was better off without any!!!!!</P
+><P
+>In terms of overall speed of transfer, between various win95 clients
+and a DX2-66 20MB server with a crappy NE2000 compatible and old IDE
+drive (Kernel 2.0.30). The transfer rate was reasonable for 10 baseT.</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>The figures are: Put Get
+P166 client 3Com card: 420-440kB/s 500-520kB/s
+P100 client 3Com card: 390-410kB/s 490-510kB/s
+DX4-75 client NE2000: 370-380kB/s 330-350kB/s</PRE
+></P
+><P
+>I based these test on transfer two files a 4.5MB text file and a 15MB
+textfile. The results arn't bad considering the hardware Samba is
+running on. It's a crap machine!!!!</P
+><P
+>The updates mentioned in 1 and 2 brought up the transfer rates from
+just over 100kB/s in some clients.</P
+><P
+>A new client is a P333 connected via a 100MB/s card and hub. The
+transfer rates from this were good: 450-500kB/s on put and 600+kB/s
+on get.</P
+><P
+>Looking at standard FTP throughput, Samba is a bit slower (100kB/s
+upwards). I suppose there is more going on in the samba protocol, but
+if it could get up to the rate of FTP the perfomance would be quite
+staggering.</P
+></DIV
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+SUMMARY="Footer navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="groupmapping.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="samba-howto-collection.html"
+ACCESSKEY="H"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="appendixes.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>Group mapping HOWTO</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="optional.html"
+ACCESSKEY="U"
+>Up</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>Appendixes</TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+> \ No newline at end of file
diff --git a/docs/htmldocs/swat.8.html b/docs/htmldocs/swat.8.html
index c5a5ab271b..f101a7bc26 100644
--- a/docs/htmldocs/swat.8.html
+++ b/docs/htmldocs/swat.8.html
@@ -1,87 +1,425 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>swat</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="swat.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>swat &#8212; Samba Web Administration Tool</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><tt>swat</tt> [-s &lt;smb config file&gt;] [-a]</p></div></div><div class="refsect1" lang="en"><h2>DESCRIPTION</h2><p>This tool is part of the <a href="Samba.7.html">Samba(7)</a> suite.</p><p><b>swat</b> allows a Samba administrator to
- configure the complex <a href="smb.conf.5.html">smb.conf(5)</a> file via a Web browser. In addition,
- a <b>swat</b> configuration page has help links
- to all the configurable options in the <tt>smb.conf</tt> file allowing an
- administrator to easily look up the effects of any change. </p><p><b>swat</b> is run from <b>inetd</b> </p></div><div class="refsect1" lang="en"><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-s smb configuration file</span></dt><dd><p>The default configuration file path is
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<HTML
+><HEAD
+><TITLE
+>swat</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.77"></HEAD
+><BODY
+CLASS="REFENTRY"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><H1
+><A
+NAME="SWAT"
+></A
+>swat</H1
+><DIV
+CLASS="REFNAMEDIV"
+><A
+NAME="AEN5"
+></A
+><H2
+>Name</H2
+>swat&nbsp;--&nbsp;Samba Web Administration Tool</DIV
+><DIV
+CLASS="REFSYNOPSISDIV"
+><A
+NAME="AEN8"
+></A
+><H2
+>Synopsis</H2
+><P
+><B
+CLASS="COMMAND"
+>swat</B
+> [-s &lt;smb config file&gt;] [-a]</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN13"
+></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"
+>swat</B
+> allows a Samba administrator to
+ configure the complex <A
+HREF="smb.conf.5.html"
+TARGET="_top"
+><TT
+CLASS="FILENAME"
+> smb.conf(5)</TT
+></A
+> file via a Web browser. In addition,
+ a <B
+CLASS="COMMAND"
+>swat</B
+> configuration page has help links
+ to all the configurable options in the <TT
+CLASS="FILENAME"
+>smb.conf</TT
+> file allowing an
+ administrator to easily look up the effects of any change. </P
+><P
+><B
+CLASS="COMMAND"
+>swat</B
+> is run from <B
+CLASS="COMMAND"
+>inetd</B
+> </P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN26"
+></A
+><H2
+>OPTIONS</H2
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>-s smb configuration file</DT
+><DD
+><P
+>The default configuration file path is
determined at compile time. The file specified contains
- the configuration details required by the <a href="smbd.8.html">smbd(8)</a> server. This is the file
- that <b>swat</b> will modify.
+ the configuration details required by the <B
+CLASS="COMMAND"
+>smbd
+ </B
+> server. This is the file that <B
+CLASS="COMMAND"
+>swat</B
+> will modify.
The information in this file includes server-specific
information such as what printcap file to use, as well as
descriptions of all the services that the server is to provide.
- See <tt>smb.conf</tt> for more information.
- </p></dd><dt><span class="term">-a</span></dt><dd><p>This option disables authentication and puts
- <b>swat</b> in demo mode. In that mode anyone will be able to modify
- the <tt>smb.conf</tt> file. </p><p><span class="emphasis"><em>WARNING: Do NOT enable this option on a production
- server. </em></span></p></dd><dt><span class="term">-V</span></dt><dd><p>Prints the version number for
-<b>smbd</b>.</p></dd><dt><span class="term">-s &lt;configuration file&gt;</span></dt><dd><p>The file specified contains the
-configuration details required by the server. The
-information in this file includes server-specific
-information such as what printcap file to use, as well
-as descriptions of all the services that the server is
-to provide. See <a href="smb.conf.5.html" target="_top"><tt>
-smb.conf(5)</tt></a> for more information.
-The default configuration file name is determined at
-compile time.</p></dd><dt><span class="term">-d|--debug=debuglevel</span></dt><dd><p><i><tt>debuglevel</tt></i> is an integer
-from 0 to 10. The default value if this parameter is
-not specified is zero.</p><p>The higher this value, the more detail will be
-logged to the log files about the activities of the
-server. At level 0, only critical errors and serious
-warnings will be logged. Level 1 is a reasonable level for
-day to day running - it generates a small amount of
-information about operations carried out.</p><p>Levels above 1 will generate considerable
-amounts of log data, and should only be used when
-investigating a problem. Levels above 3 are designed for
-use only by developers and generate HUGE amounts of log
-data, most of which is extremely cryptic.</p><p>Note that specifying this parameter here will
-override the <a href="smb.conf.5.html#loglevel" target="_top">log
-level</a> parameter in the <a href="smb.conf.5.html" target="_top">
-<tt>smb.conf(5)</tt></a> file.</p></dd><dt><span class="term">-l|--logfile=logbasename</span></dt><dd><p>File name for log/debug files. The extension
-<tt>&quot;.client&quot;</tt> will be appended. The log file is
-never removed by the client.
-</p></dd><dt><span class="term">-h|--help</span></dt><dd><p>Print a summary of command line options.
-</p></dd></dl></div></div><div class="refsect1" lang="en"><h2>INSTALLATION</h2><p>Swat is included as binary package with most distributions. The
- package manager in this case takes care of the installation and
- configuration. This section is only for those who have compiled
- swat from scratch.
- </p><p>After you compile SWAT you need to run <b>make install
- </b> to install the <b>swat</b> binary
+ See <TT
+CLASS="FILENAME"
+>smb.conf</TT
+> for more information.
+ </P
+></DD
+><DT
+>-a</DT
+><DD
+><P
+>This option disables authentication and puts
+ <B
+CLASS="COMMAND"
+>swat</B
+> in demo mode. In that mode anyone will be able to modify
+ the <TT
+CLASS="FILENAME"
+>smb.conf</TT
+> file. </P
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>WARNING: Do NOT enable this option on a production
+ server. </I
+></SPAN
+></P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN44"
+></A
+><H2
+>INSTALLATION</H2
+><P
+>After you compile SWAT you need to run <B
+CLASS="COMMAND"
+>make install
+ </B
+> to install the <B
+CLASS="COMMAND"
+>swat</B
+> binary
and the various help files and images. A default install would put
- these in: </p><div class="itemizedlist"><ul type="disc"><li><p>/usr/local/samba/bin/swat</p></li><li><p>/usr/local/samba/swat/images/*</p></li><li><p>/usr/local/samba/swat/help/*</p></li></ul></div><div class="refsect2" lang="en"><h3>Inetd Installation</h3><p>You need to edit your <tt>/etc/inetd.conf
- </tt> and <tt>/etc/services</tt>
- to enable SWAT to be launched via <b>inetd</b>.</p><p>In <tt>/etc/services</tt> you need to
- add a line like this: </p><p><b>swat 901/tcp</b></p><p>Note for NIS/YP and LDAP users - you may need to rebuild the
- NIS service maps rather than alter your local <tt>
- /etc/services</tt> file. </p><p>the choice of port number isn't really important
+ these in: </P
+><P
+></P
+><UL
+><LI
+><P
+>/usr/local/samba/bin/swat</P
+></LI
+><LI
+><P
+>/usr/local/samba/swat/images/*</P
+></LI
+><LI
+><P
+>/usr/local/samba/swat/help/*</P
+></LI
+></UL
+><DIV
+CLASS="REFSECT2"
+><A
+NAME="AEN56"
+></A
+><H3
+>Inetd Installation</H3
+><P
+>You need to edit your <TT
+CLASS="FILENAME"
+>/etc/inetd.conf
+ </TT
+> and <TT
+CLASS="FILENAME"
+>/etc/services</TT
+>
+ to enable SWAT to be launched via <B
+CLASS="COMMAND"
+>inetd</B
+>.</P
+><P
+>In <TT
+CLASS="FILENAME"
+>/etc/services</TT
+> you need to
+ add a line like this: </P
+><P
+><B
+CLASS="COMMAND"
+>swat 901/tcp</B
+></P
+><P
+>Note for NIS/YP users - you may need to rebuild the
+ NIS service maps rather than alter your local <TT
+CLASS="FILENAME"
+> /etc/services</TT
+> file. </P
+><P
+>the choice of port number isn't really important
except that it should be less than 1024 and not currently
used (using a number above 1024 presents an obscure security
hole depending on the implementation details of your
- <b>inetd</b> daemon). </p><p>In <tt>/etc/inetd.conf</tt> you should
- add a line like this: </p><p><b>swat stream tcp nowait.400 root
- /usr/local/samba/bin/swat swat</b></p><p>One you have edited <tt>/etc/services</tt>
- and <tt>/etc/inetd.conf</tt> you need to send a
- HUP signal to inetd. To do this use <b>kill -1 PID
- </b> where PID is the process ID of the inetd daemon. </p></div></div><div class="refsect1" lang="en"><h2>LAUNCHING</h2><p>To launch SWAT just run your favorite web browser and
- point it at &quot;http://localhost:901/&quot;.</p><p>Note that you can attach to SWAT from any IP connected
- machine but connecting from a remote machine leaves your
- connection open to password sniffing as passwords will be sent
- in the clear over the wire. </p></div><div class="refsect1" lang="en"><h2>FILES</h2><div class="variablelist"><dl><dt><span class="term"><tt>/etc/inetd.conf</tt></span></dt><dd><p>This file must contain suitable startup
- information for the meta-daemon.</p></dd><dt><span class="term"><tt>/etc/services</tt></span></dt><dd><p>This file must contain a mapping of service name
+ <B
+CLASS="COMMAND"
+>inetd</B
+> daemon). </P
+><P
+>In <TT
+CLASS="FILENAME"
+>/etc/inetd.conf</TT
+> you should
+ add a line like this: </P
+><P
+><B
+CLASS="COMMAND"
+>swat stream tcp nowait.400 root
+ /usr/local/samba/bin/swat swat</B
+></P
+><P
+>One you have edited <TT
+CLASS="FILENAME"
+>/etc/services</TT
+>
+ and <TT
+CLASS="FILENAME"
+>/etc/inetd.conf</TT
+> you need to send a
+ HUP signal to inetd. To do this use <B
+CLASS="COMMAND"
+>kill -1 PID
+ </B
+> where PID is the process ID of the inetd daemon. </P
+></DIV
+><DIV
+CLASS="REFSECT2"
+><A
+NAME="AEN78"
+></A
+><H3
+>Launching</H3
+><P
+>To launch SWAT just run your favorite web browser and
+ point it at "http://localhost:901/".</P
+><P
+>Note that you can attach to SWAT from any IP connected
+ machine but connecting from a remote machine leaves your
+ connection open to password sniffing as passwords will be sent
+ in the clear over the wire. </P
+></DIV
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN82"
+></A
+><H2
+>FILES</H2
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+><TT
+CLASS="FILENAME"
+>/etc/inetd.conf</TT
+></DT
+><DD
+><P
+>This file must contain suitable startup
+ information for the meta-daemon.</P
+></DD
+><DT
+><TT
+CLASS="FILENAME"
+>/etc/services</TT
+></DT
+><DD
+><P
+>This file must contain a mapping of service name
(e.g., swat) to service port (e.g., 901) and protocol type
- (e.g., tcp). </p></dd><dt><span class="term"><tt>/usr/local/samba/lib/smb.conf</tt></span></dt><dd><p>This is the default location of the <a href="smb.conf.5.html">smb.conf(5)</a> server configuration file that swat edits. Other
- common places that systems install this file are <tt>
- /usr/samba/lib/smb.conf</tt> and <tt>/etc/smb.conf
- </tt>. This file describes all the services the server
- is to make available to clients. </p></dd></dl></div></div><div class="refsect1" lang="en"><h2>WARNINGS</h2><p><b>swat</b> will rewrite your <a href="smb.conf.5.html">smb.conf(5)</a> file. It will rearrange the entries and delete all
- comments, <i><tt>include=</tt></i> and <i><tt>copy=
- </tt></i> options. If you have a carefully crafted <tt>
- smb.conf</tt> then back it up or don't use swat! </p></div><div class="refsect1" lang="en"><h2>VERSION</h2><p>This man page is correct for version 3.0 of the Samba suite.</p></div><div class="refsect1" lang="en"><h2>SEE ALSO</h2><p><b>inetd(5)</b>, <a href="smbd.8.html">smbd(8)</a>, <a href="smb.conf.5.html">smb.conf(5)</a></p></div><div class="refsect1" lang="en"><h2>AUTHOR</h2><p>The original Samba software and related utilities
+ (e.g., tcp). </P
+></DD
+><DT
+><TT
+CLASS="FILENAME"
+>/usr/local/samba/lib/smb.conf</TT
+></DT
+><DD
+><P
+>This is the default location of the <TT
+CLASS="FILENAME"
+>smb.conf(5)
+ </TT
+> server configuration file that swat edits. Other
+ common places that systems install this file are <TT
+CLASS="FILENAME"
+> /usr/samba/lib/smb.conf</TT
+> and <TT
+CLASS="FILENAME"
+>/etc/smb.conf
+ </TT
+>. This file describes all the services the server
+ is to make available to clients. </P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN103"
+></A
+><H2
+>WARNINGS</H2
+><P
+><B
+CLASS="COMMAND"
+>swat</B
+> will rewrite your <TT
+CLASS="FILENAME"
+>smb.conf
+ </TT
+> file. It will rearrange the entries and delete all
+ comments, <TT
+CLASS="PARAMETER"
+><I
+>include=</I
+></TT
+> and <TT
+CLASS="PARAMETER"
+><I
+>copy=
+ </I
+></TT
+> options. If you have a carefully crafted <TT
+CLASS="FILENAME"
+> smb.conf</TT
+> then back it up or don't use swat! </P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN111"
+></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="AEN114"
+></A
+><H2
+>SEE ALSO</H2
+><P
+><B
+CLASS="COMMAND"
+>inetd(5)</B
+>,
+ <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="AEN121"
+></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.
+ to the way the Linux kernel is developed.</P
+><P
+>The original Samba man pages were written by Karl Auer.
The man page sources were converted to YODL format (another
- excellent piece of Open Source software, available at <a href="ftp://ftp.icce.rug.nl/pub/unix/" target="_top">
- ftp://ftp.icce.rug.nl/pub/unix/</a>) and updated for the Samba 2.0
+ excellent piece of Open Source software, available at
+ <A
+HREF="ftp://ftp.icce.rug.nl/pub/unix/"
+TARGET="_top"
+> ftp://ftp.icce.rug.nl/pub/unix/</A
+>) and updated for the Samba 2.0
release by Jeremy Allison. The conversion to DocBook for
- Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 for
- Samba 3.0 was done by Alexander Bokovoy.</p></div></div></body></html>
+ Samba 2.2 was done by Gerald Carter</P
+></DIV
+></BODY
+></HTML
+> \ No newline at end of file
diff --git a/docs/htmldocs/swat.html b/docs/htmldocs/swat.html
deleted file mode 100644
index e70fac5403..0000000000
--- a/docs/htmldocs/swat.html
+++ /dev/null
@@ -1,233 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<HTML
-><HEAD
-><TITLE
->SWAT - The Samba Web Admininistration Tool</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
-REL="HOME"
-TITLE="SAMBA Project Documentation"
-HREF="samba-howto-collection.html"><LINK
-REL="UP"
-TITLE="Appendixes"
-HREF="appendixes.html"><LINK
-REL="PREVIOUS"
-TITLE="Samba and other CIFS clients"
-HREF="other-clients.html"><LINK
-REL="NEXT"
-TITLE="Samba performance issues"
-HREF="speed.html"></HEAD
-><BODY
-CLASS="CHAPTER"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->SAMBA Project Documentation</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="other-clients.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
-></TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="speed.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="CHAPTER"
-><H1
-><A
-NAME="SWAT"
-></A
->Chapter 31. SWAT - The Samba Web Admininistration Tool</H1
-><P
->This is a rough guide to SWAT.</P
-><DIV
-CLASS="SECT1"
-><H1
-CLASS="SECT1"
-><A
-NAME="AEN4645"
->31.1. SWAT Features and Benefits</A
-></H1
-><P
->You must use at least the following ...</P
-><DIV
-CLASS="SECT2"
-><H2
-CLASS="SECT2"
-><A
-NAME="AEN4648"
->31.1.1. The SWAT Home Page</A
-></H2
-><P
->Blah blah here.</P
-></DIV
-><DIV
-CLASS="SECT2"
-><H2
-CLASS="SECT2"
-><A
-NAME="AEN4651"
->31.1.2. Global Settings</A
-></H2
-><P
->Document steps right here!</P
-></DIV
-><DIV
-CLASS="SECT2"
-><H2
-CLASS="SECT2"
-><A
-NAME="AEN4654"
->31.1.3. The SWAT Wizard</A
-></H2
-><P
->Lots of blah blah here.</P
-></DIV
-><DIV
-CLASS="SECT2"
-><H2
-CLASS="SECT2"
-><A
-NAME="AEN4657"
->31.1.4. Share Settings</A
-></H2
-><P
->Document steps right here!</P
-></DIV
-><DIV
-CLASS="SECT2"
-><H2
-CLASS="SECT2"
-><A
-NAME="AEN4660"
->31.1.5. Printing Settings</A
-></H2
-><P
->Document steps right here!</P
-></DIV
-><DIV
-CLASS="SECT2"
-><H2
-CLASS="SECT2"
-><A
-NAME="AEN4663"
->31.1.6. The Status Page</A
-></H2
-><P
->Document steps right here!</P
-></DIV
-><DIV
-CLASS="SECT2"
-><H2
-CLASS="SECT2"
-><A
-NAME="AEN4666"
->31.1.7. The Password Change Page</A
-></H2
-><P
->Document steps right here!</P
-></DIV
-></DIV
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="other-clients.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="samba-howto-collection.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="speed.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Samba and other CIFS clients</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="appendixes.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Samba performance issues</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
-> \ No newline at end of file
diff --git a/docs/htmldocs/testparm.1.html b/docs/htmldocs/testparm.1.html
index 55779a2ad8..baf11bacac 100644
--- a/docs/htmldocs/testparm.1.html
+++ b/docs/htmldocs/testparm.1.html
@@ -1,51 +1,316 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>testparm</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="testparm.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>testparm &#8212; check an smb.conf configuration file for
- internal correctness</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><tt>testparm</tt> [-s] [-h] [-v] [-L &lt;servername&gt;] [-t &lt;encoding&gt;] {config filename} [hostname hostIP]</p></div></div><div class="refsect1" lang="en"><h2>DESCRIPTION</h2><p>This tool is part of the <a href="Samba.7.html">Samba(7)</a> suite.</p><p><b>testparm</b> is a very simple test program
- to check an <a href="smbd.8.html">smbd(8)</a> configuration file for
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
+<HTML
+><HEAD
+><TITLE
+>testparm</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"></HEAD
+><BODY
+CLASS="REFENTRY"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><H1
+><A
+NAME="TESTPARM">testparm</H1
+><DIV
+CLASS="REFNAMEDIV"
+><A
+NAME="AEN5"
+></A
+><H2
+>Name</H2
+>testparm&nbsp;--&nbsp;check an smb.conf configuration file for
+ internal correctness</DIV
+><DIV
+CLASS="REFSYNOPSISDIV"
+><A
+NAME="AEN8"><H2
+>Synopsis</H2
+><P
+><B
+CLASS="COMMAND"
+>testparm</B
+> [-s] [-h] [-v] [-L &#60;servername&#62;] [-t &#60;encoding&#62;] {config filename} [hostname hostIP]</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN18"
+></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"
+>testparm</B
+> is a very simple test program
+ to check an <B
+CLASS="COMMAND"
+>smbd</B
+> configuration file for
internal correctness. If this program reports no problems, you
- can use the configuration file with confidence that <b>smbd
- </b> will successfully load the configuration file.</p><p>Note that this is <span class="emphasis"><em>NOT</em></span> a guarantee that
+ can use the configuration file with confidence that <B
+CLASS="COMMAND"
+>smbd
+ </B
+> will successfully load the configuration file.</P
+><P
+>Note that this is <I
+CLASS="EMPHASIS"
+>NOT</I
+> a guarantee that
the services specified in the configuration file will be
- available or will operate as expected. </p><p>If the optional host name and host IP address are
+ available or will operate as expected. </P
+><P
+>If the optional host name and host IP address are
specified on the command line, this test program will run through
the service entries reporting whether the specified host
- has access to each service. </p><p>If <b>testparm</b> finds an error in the <tt>
- smb.conf</tt> file it returns an exit code of 1 to the calling
+ has access to each service. </P
+><P
+>If <B
+CLASS="COMMAND"
+>testparm</B
+> finds an error in the <TT
+CLASS="FILENAME"
+> smb.conf</TT
+> file it returns an exit code of 1 to the calling
program, else it returns an exit code of 0. This allows shell scripts
- to test the output from <b>testparm</b>.</p></div><div class="refsect1" lang="en"><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-s</span></dt><dd><p>Without this option, <b>testparm</b>
+ to test the output from <B
+CLASS="COMMAND"
+>testparm</B
+>.</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN33"
+></A
+><H2
+>OPTIONS</H2
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>-s</DT
+><DD
+><P
+>Without this option, <B
+CLASS="COMMAND"
+>testparm</B
+>
will prompt for a carriage return after printing the service
- names and before dumping the service definitions.</p></dd><dt><span class="term">-h|--help</span></dt><dd><p>Print a summary of command line options.
-</p></dd><dt><span class="term">-V</span></dt><dd><p>Prints the version number for
-<b>smbd</b>.</p></dd><dt><span class="term">-L servername</span></dt><dd><p>Sets the value of the %L macro to <i><tt>servername</tt></i>.
+ names and before dumping the service definitions.</P
+></DD
+><DT
+>-h</DT
+><DD
+><P
+>Print usage message </P
+></DD
+><DT
+>-L servername</DT
+><DD
+><P
+>Sets the value of the %L macro to <TT
+CLASS="REPLACEABLE"
+><I
+>servername</I
+></TT
+>.
This is useful for testing include files specified with the
- %L macro. </p></dd><dt><span class="term">-v</span></dt><dd><p>If this option is specified, testparm
- will also output all options that were not used in <a href="smb.conf.5.html">smb.conf(5)</a> and are thus set to their defaults.</p></dd><dt><span class="term">-t encoding</span></dt><dd><p>
- Output data in specified encoding.
- </p></dd><dt><span class="term">configfilename</span></dt><dd><p>This is the name of the configuration file
+ %L macro. </P
+></DD
+><DT
+>-v</DT
+><DD
+><P
+>If this option is specified, testparm
+ will also output all options that were not used in
+ <TT
+CLASS="FILENAME"
+>smb.conf</TT
+> and are thus set to
+ their defaults.</P
+></DD
+><DT
+>-t encoding</DT
+><DD
+><P
+> Output data in specified encoding.
+ </P
+></DD
+><DT
+>configfilename</DT
+><DD
+><P
+>This is the name of the configuration file
to check. If this parameter is not present then the
- default <a href="smb.conf.5.html">smb.conf(5)</a> file will be checked.
- </p></dd><dt><span class="term">hostname</span></dt><dd><p>If this parameter and the following are
- specified, then <b>testparm</b> will examine the <i><tt>hosts
- allow</tt></i> and <i><tt>hosts deny</tt></i>
- parameters in the <a href="smb.conf.5.html">smb.conf(5)</a> file to
+ default <TT
+CLASS="FILENAME"
+>smb.conf</TT
+> file will be checked.
+ </P
+></DD
+><DT
+>hostname</DT
+><DD
+><P
+>If this parameter and the following are
+ specified, then <B
+CLASS="COMMAND"
+>testparm</B
+> will examine the <TT
+CLASS="PARAMETER"
+><I
+>hosts
+ allow</I
+></TT
+> and <TT
+CLASS="PARAMETER"
+><I
+>hosts deny</I
+></TT
+>
+ parameters in the <TT
+CLASS="FILENAME"
+>smb.conf</TT
+> file to
determine if the hostname with this IP address would be
- allowed access to the <b>smbd</b> server. If
+ allowed access to the <B
+CLASS="COMMAND"
+>smbd</B
+> server. If
this parameter is supplied, the hostIP parameter must also
- be supplied.</p></dd><dt><span class="term">hostIP</span></dt><dd><p>This is the IP address of the host specified
+ be supplied.</P
+></DD
+><DT
+>hostIP</DT
+><DD
+><P
+>This is the IP address of the host specified
in the previous parameter. This address must be supplied
- if the hostname parameter is supplied. </p></dd></dl></div></div><div class="refsect1" lang="en"><h2>FILES</h2><div class="variablelist"><dl><dt><span class="term"><a href="smb.conf.5.html">smb.conf(5)</a></span></dt><dd><p>This is usually the name of the configuration
- file used by <a href="smbd.8.html">smbd(8)</a>.
- </p></dd></dl></div></div><div class="refsect1" lang="en"><h2>DIAGNOSTICS</h2><p>The program will issue a message saying whether the
+ if the hostname parameter is supplied. </P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN77"
+></A
+><H2
+>FILES</H2
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+><TT
+CLASS="FILENAME"
+>smb.conf</TT
+></DT
+><DD
+><P
+>This is usually the name of the configuration
+ file used by <B
+CLASS="COMMAND"
+>smbd</B
+>.
+ </P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN86"
+></A
+><H2
+>DIAGNOSTICS</H2
+><P
+>The program will issue a message saying whether the
configuration file loaded OK or not. This message may be preceded by
errors and warnings if the file did not load. If the file was
loaded OK, the program then dumps all known service details
- to stdout. </p></div><div class="refsect1" lang="en"><h2>VERSION</h2><p>This man page is correct for version 3.0 of
- the Samba suite.</p></div><div class="refsect1" lang="en"><h2>SEE ALSO</h2><p><a href="smb.conf.5.html">smb.conf(5)</a>, <a href="smbd.8.html">smbd(8)</a></p></div><div class="refsect1" lang="en"><h2>AUTHOR</h2><p>The original Samba software and related utilities
+ to stdout. </P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN89"
+></A
+><H2
+>VERSION</H2
+><P
+>This man page is correct for version 3.0 of
+ the Samba suite.</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN92"
+></A
+><H2
+>SEE ALSO</H2
+><P
+><A
+HREF="smb.conf.5.html"
+TARGET="_top"
+><TT
+CLASS="FILENAME"
+>smb.conf(5)</TT
+></A
+>,
+ <A
+HREF="smbd.8.html"
+TARGET="_top"
+><B
+CLASS="COMMAND"
+>smbd(8)</B
+></A
+>
+ </P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN99"
+></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.
+ to the way the Linux kernel is developed.</P
+><P
+>The original Samba man pages were written by Karl Auer.
The man page sources were converted to YODL format (another
- excellent piece of Open Source software, available at <a href="ftp://ftp.icce.rug.nl/pub/unix/" target="_top">
- ftp://ftp.icce.rug.nl/pub/unix/</a>) and updated for the Samba 2.0
+ excellent piece of Open Source software, available at
+ <A
+HREF="ftp://ftp.icce.rug.nl/pub/unix/"
+TARGET="_top"
+> ftp://ftp.icce.rug.nl/pub/unix/</A
+>) and updated for the Samba 2.0
release by Jeremy Allison. The conversion to DocBook for
- Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2
- for Samba 3.0 was done by Alexander Bokovoy.</p></div></div></body></html>
+ Samba 2.2 was done by Gerald Carter</P
+></DIV
+></BODY
+></HTML
+> \ No newline at end of file
diff --git a/docs/htmldocs/testprns.1.html b/docs/htmldocs/testprns.1.html
index 16784fcc25..0225aad9d5 100644
--- a/docs/htmldocs/testprns.1.html
+++ b/docs/htmldocs/testprns.1.html
@@ -1,38 +1,253 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>testprns</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="testprns.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>testprns &#8212; check printer name for validity with smbd</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><tt>testprns</tt> {printername} [printcapname]</p></div></div><div class="refsect1" lang="en"><h2>DESCRIPTION</h2><p>This tool is part of the <a href="Samba.7.html">Samba(7)</a> suite.</p><p><b>testprns</b> is a very simple test program
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<HTML
+><HEAD
+><TITLE
+>testprns</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.77"></HEAD
+><BODY
+CLASS="REFENTRY"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><H1
+><A
+NAME="TESTPRNS"
+></A
+>testprns</H1
+><DIV
+CLASS="REFNAMEDIV"
+><A
+NAME="AEN5"
+></A
+><H2
+>Name</H2
+>testprns&nbsp;--&nbsp;check printer name for validity with smbd</DIV
+><DIV
+CLASS="REFSYNOPSISDIV"
+><A
+NAME="AEN8"
+></A
+><H2
+>Synopsis</H2
+><P
+><B
+CLASS="COMMAND"
+>testprns</B
+> {printername} [printcapname]</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN13"
+></A
+><H2
+>DESCRIPTION</H2
+><P
+>This tool is part of the <A
+HREF="samba.7.html"
+TARGET="_top"
+> Samba</A
+> suite.</P
+><P
+><B
+CLASS="COMMAND"
+>testprns</B
+> is a very simple test program
to determine whether a given printer name is valid for use in
- a service to be provided by <a href="smbd.8.html">smbd(8)</a>.</p><p>&quot;Valid&quot; in this context means &quot;can be found in the
- printcap specified&quot;. This program is very stupid - so stupid in
+ a service to be provided by <A
+HREF="smbd.8.html"
+TARGET="_top"
+><B
+CLASS="COMMAND"
+> smbd(8)</B
+></A
+>. </P
+><P
+>"Valid" in this context means "can be found in the
+ printcap specified". This program is very stupid - so stupid in
fact that it would be wisest to always specify the printcap file
- to use. </p></div><div class="refsect1" lang="en"><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">printername</span></dt><dd><p>The printer name to validate.</p><p>Printer names are taken from the first field in each
+ to use. </P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN22"
+></A
+><H2
+>OPTIONS</H2
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>printername</DT
+><DD
+><P
+>The printer name to validate.</P
+><P
+>Printer names are taken from the first field in each
record in the printcap file, single printer names and sets
- of aliases separated by vertical bars (&quot;|&quot;) are recognized.
+ of aliases separated by vertical bars ("|") are recognized.
Note that no validation or checking of the printcap syntax is
done beyond that required to extract the printer name. It may
be that the print spooling system is more forgiving or less
- forgiving than <b>testprns</b>. However, if
- <b>testprns</b> finds the printer then <a href="smbd.8.html">smbd(8)</a> should do so as well. </p></dd><dt><span class="term">printcapname</span></dt><dd><p>This is the name of the printcap file within
- which to search for the given printer name. </p><p>If no printcap name is specified <b>testprns
- </b> will attempt to scan the printcap file name
- specified at compile time. </p></dd></dl></div></div><div class="refsect1" lang="en"><h2>FILES</h2><div class="variablelist"><dl><dt><span class="term"><tt>/etc/printcap</tt></span></dt><dd><p>This is usually the default printcap
- file to scan. See <tt>printcap (5)</tt>.
- </p></dd></dl></div></div><div class="refsect1" lang="en"><h2>DIAGNOSTICS</h2><p>If a printer is found to be valid, the message
- &quot;Printer name &lt;printername&gt; is valid&quot; will be
- displayed. </p><p>If a printer is found to be invalid, the message
- &quot;Printer name &lt;printername&gt; is not valid&quot; will be
- displayed. </p><p>All messages that would normally be logged during
+ forgiving than <B
+CLASS="COMMAND"
+>testprns</B
+>. However, if
+ <B
+CLASS="COMMAND"
+>testprns</B
+> finds the printer then
+ <B
+CLASS="COMMAND"
+>smbd</B
+> should do so as well. </P
+></DD
+><DT
+>printcapname</DT
+><DD
+><P
+>This is the name of the printcap file within
+ which to search for the given printer name. </P
+><P
+>If no printcap name is specified <B
+CLASS="COMMAND"
+>testprns
+ </B
+> will attempt to scan the printcap file name
+ specified at compile time. </P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN39"
+></A
+><H2
+>FILES</H2
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+><TT
+CLASS="FILENAME"
+>/etc/printcap</TT
+></DT
+><DD
+><P
+>This is usually the default printcap
+ file to scan. See <TT
+CLASS="FILENAME"
+>printcap (5)</TT
+>.
+ </P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN48"
+></A
+><H2
+>DIAGNOSTICS</H2
+><P
+>If a printer is found to be valid, the message
+ "Printer name &lt;printername&gt; is valid" will be
+ displayed. </P
+><P
+>If a printer is found to be invalid, the message
+ "Printer name &lt;printername&gt; is not valid" will be
+ displayed. </P
+><P
+>All messages that would normally be logged during
operation of the Samba daemons are logged by this program to the
- file <tt>test.log</tt> in the current directory. The
+ file <TT
+CLASS="FILENAME"
+>test.log</TT
+> in the current directory. The
program runs at debuglevel 3, so quite extensive logging
information is written. The log should be checked carefully
- for errors and warnings. </p><p>Other messages are self-explanatory. </p></div><div class="refsect1" lang="en"><h2>VERSION</h2><p>This man page is correct for version 3.0 of
- the Samba suite.</p></div><div class="refsect1" lang="en"><h2>SEE ALSO</h2><p><tt>printcap(5)</tt>,
- <a href="smbd.8.html">smbd(8)</a>, <a href="smbclient.1.html">smbclient(1)</a></p></div><div class="refsect1" lang="en"><h2>AUTHOR</h2><p>The original Samba software and related utilities
+ for errors and warnings. </P
+><P
+>Other messages are self-explanatory. </P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN55"
+></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="AEN58"
+></A
+><H2
+>SEE ALSO</H2
+><P
+><TT
+CLASS="FILENAME"
+>printcap(5)</TT
+>,
+ <A
+HREF="smbd.8.html"
+TARGET="_top"
+><B
+CLASS="COMMAND"
+>smbd(8)</B
+></A
+>,
+ <A
+HREF="smbclient.1.html"
+TARGET="_top"
+><B
+CLASS="COMMAND"
+>smbclient(1)</B
+></A
+>
+ </P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN66"
+></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.
+ to the way the Linux kernel is developed.</P
+><P
+>The original Samba man pages were written by Karl Auer.
The man page sources were converted to YODL format (another
- excellent piece of Open Source software, available at <a href="ftp://ftp.icce.rug.nl/pub/unix/" target="_top">
- ftp://ftp.icce.rug.nl/pub/unix/</a>) and updated for the Samba 2.0
+ excellent piece of Open Source software, available at
+ <A
+HREF="ftp://ftp.icce.rug.nl/pub/unix/"
+TARGET="_top"
+> ftp://ftp.icce.rug.nl/pub/unix/</A
+>) and updated for the Samba 2.0
release by Jeremy Allison. The conversion to DocBook for
- Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2
- for Samba 3.0 was done by Alexander Bokovoy.</p></div></div></body></html>
+ Samba 2.2 was done by Gerald Carter</P
+></DIV
+></BODY
+></HTML
+> \ No newline at end of file
diff --git a/docs/htmldocs/type.html b/docs/htmldocs/type.html
index 3524abc962..e3f09acc18 100644
--- a/docs/htmldocs/type.html
+++ b/docs/htmldocs/type.html
@@ -1,16 +1,389 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>PartII.Server Configuration Basics</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"><link rel="home" href="index.html" title="SAMBA Project Documentation"><link rel="up" href="index.html" title="SAMBA Project Documentation"><link rel="previous" href="install.html" title="Chapter2.How to Install and Test SAMBA"><link rel="next" href="ServerType.html" title="Chapter3.Nomenclature of Server Types"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">PartII.Server Configuration Basics</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="install.html">Prev</a></td><th width="60%" align="center"></th><td width="20%" align="right"><a accesskey="n" href="ServerType.html">Next</a></td></tr></table><hr></div><div class="part" lang="en"><div class="titlepage"><div><h1 class="title"><a name="type"></a>Server Configuration Basics</h1></div></div><div class="partintro" lang="en"><div><div><h1 class="title"><a name="id2812280"></a>First Steps in Server Configuration</h1></div></div><p>
-Samba can operate in various modes within SMB networks. This HOWTO section contains information on
-configuring samba to function as the type of server your network requires. Please read this
-section carefully.
-</p><div class="toc"><p><b>Table of Contents</b></p><dl><dt>3. <a href="ServerType.html">Nomenclature of Server Types</a></dt><dd><dl><dt><a href="ServerType.html#id2810455">Stand Alone Server</a></dt><dt><a href="ServerType.html#id2810516">Domain Member Server</a></dt><dt><a href="ServerType.html#id2810556">Domain Controller</a></dt><dd><dl><dt><a href="ServerType.html#id2810572">Domain Controller Types</a></dt></dl></dd></dl></dd><dt>4. <a href="securitylevels.html">Samba as Stand-Alone Server</a></dt><dd><dl><dt><a href="securitylevels.html#id2807692">User and Share security level</a></dt><dd><dl><dt><a href="securitylevels.html#id2807727">User Level Security</a></dt><dt><a href="securitylevels.html#id2810322">Share Level Security</a></dt><dt><a href="securitylevels.html#id2812328">Server Level Security</a></dt><dt><a href="securitylevels.html#id2876991">Domain Level Security</a></dt><dt><a href="securitylevels.html#id2877129">ADS Level Security</a></dt></dl></dd></dl></dd><dt>5. <a href="samba-pdc.html">
-Samba as an NT4 or Win2k Primary Domain Controller
-</a></dt><dd><dl><dt><a href="samba-pdc.html#id2807495">Prerequisite Reading</a></dt><dt><a href="samba-pdc.html#id2807518">
-Background
-</a></dt><dt><a href="samba-pdc.html#id2877458">Configuring the Samba Domain Controller</a></dt><dt><a href="samba-pdc.html#id2877759">Creating Machine Trust Accounts and Joining Clients to the Domain</a></dt><dd><dl><dt><a href="samba-pdc.html#id2878028">Manual Creation of Machine Trust Accounts</a></dt><dt><a href="samba-pdc.html#id2878262">&quot;On-the-Fly&quot; Creation of Machine Trust Accounts</a></dt><dt><a href="samba-pdc.html#id2878318">Joining the Client to the Domain</a></dt></dl></dd><dt><a href="samba-pdc.html#id2878425">Common Problems and Errors</a></dt><dd><dl><dt><a href="samba-pdc.html#id2878432">I cannot include a '$' in a machine name</a></dt><dt><a href="samba-pdc.html#id2878470">I get told &quot;You already have a connection to the Domain....&quot;
-or &quot;Cannot join domain, the credentials supplied conflict with an
-existing set..&quot; when creating a machine trust account.</a></dt><dt><a href="samba-pdc.html#id2878517">The system can not log you on (C000019B)....</a></dt><dt><a href="samba-pdc.html#id2878568">The machine trust account for this computer either does not
-exist or is not accessible.</a></dt><dt><a href="samba-pdc.html#id2878617">When I attempt to login to a Samba Domain from a NT4/W2K workstation,
-I get a message about my account being disabled.</a></dt></dl></dd><dt><a href="samba-pdc.html#id2878642">Domain Control for Windows 9x/ME</a></dt><dd><dl><dt><a href="samba-pdc.html#id2878805">Configuration Instructions: Network Logons</a></dt></dl></dd></dl></dd><dt>6. <a href="samba-bdc.html">
-Samba Backup Domain Controller to Samba Domain Control
-</a></dt><dd><dl><dt><a href="samba-bdc.html#id2807541">Prerequisite Reading</a></dt><dt><a href="samba-bdc.html#id2877190">Background</a></dt><dt><a href="samba-bdc.html#id2879061">What qualifies a Domain Controller on the network?</a></dt><dd><dl><dt><a href="samba-bdc.html#id2879083">How does a Workstation find its domain controller?</a></dt><dt><a href="samba-bdc.html#id2879107">When is the PDC needed?</a></dt></dl></dd><dt><a href="samba-bdc.html#id2879127">Can Samba be a Backup Domain Controller to an NT PDC?</a></dt><dt><a href="samba-bdc.html#id2879160">How do I set up a Samba BDC?</a></dt><dd><dl><dt><a href="samba-bdc.html#id2879257">How do I replicate the smbpasswd file?</a></dt><dt><a href="samba-bdc.html#id2879286">Can I do this all with LDAP?</a></dt></dl></dd></dl></dd><dt>7. <a href="ADS.html">Samba as a ADS domain member</a></dt><dd><dl><dt><a href="ADS.html#id2878917">Setup your smb.conf</a></dt><dt><a href="ADS.html#id2879467">Setup your /etc/krb5.conf</a></dt><dt><a href="ADS.html#ads-create-machine-account">Create the computer account</a></dt><dd><dl><dt><a href="ADS.html#id2879661">Possible errors</a></dt></dl></dd><dt><a href="ADS.html#ads-test-server">Test your server setup</a></dt><dt><a href="ADS.html#ads-test-smbclient">Testing with smbclient</a></dt><dt><a href="ADS.html#id2879814">Notes</a></dt></dl></dd><dt>8. <a href="domain-member.html">Samba as a NT4 or Win2k domain member</a></dt><dd><dl><dt><a href="domain-member.html#id2879309">Joining an NT Domain with Samba 3.0</a></dt><dt><a href="domain-member.html#id2880214">Why is this better than security = server?</a></dt></dl></dd></dl></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="install.html">Prev</a></td><td width="20%" align="center"><a accesskey="u" href="index.html">Up</a></td><td width="40%" align="right"><a accesskey="n" href="ServerType.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter2.How to Install and Test SAMBA</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">Chapter3.Nomenclature of Server Types</td></tr></table></div></body></html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<HTML
+><HEAD
+><TITLE
+>Type of installation</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
+REL="HOME"
+TITLE="SAMBA Project Documentation"
+HREF="samba-howto-collection.html"><LINK
+REL="PREVIOUS"
+TITLE="LanMan and NT Password Encryption in Samba"
+HREF="pwencrypt.html"><LINK
+REL="NEXT"
+TITLE="User and Share security level (for servers not in a domain)"
+HREF="securitylevels.html"></HEAD
+><BODY
+CLASS="PART"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><TABLE
+SUMMARY="Header navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>SAMBA Project Documentation</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="pwencrypt.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+></TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="securitylevels.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="PART"
+><A
+NAME="TYPE"><DIV
+CLASS="TITLEPAGE"
+><H1
+CLASS="TITLE"
+>II. Type of installation</H1
+><DIV
+CLASS="PARTINTRO"
+><A
+NAME="AEN531"><H1
+>Introduction</H1
+><P
+>Samba can operate in various SMB networks. This part contains information on configuring samba
+for various environments.</P
+></DIV
+><DIV
+CLASS="TOC"
+><DL
+><DT
+><B
+>Table of Contents</B
+></DT
+><DT
+>5. <A
+HREF="securitylevels.html"
+>User and Share security level (for servers not in a domain)</A
+></DT
+><DT
+>6. <A
+HREF="samba-pdc.html"
+>How to Configure Samba as a NT4 Primary Domain Controller</A
+></DT
+><DD
+><DL
+><DT
+>6.1. <A
+HREF="samba-pdc.html#AEN575"
+>Prerequisite Reading</A
+></DT
+><DT
+>6.2. <A
+HREF="samba-pdc.html#AEN581"
+>Background</A
+></DT
+><DT
+>6.3. <A
+HREF="samba-pdc.html#AEN620"
+>Configuring the Samba Domain Controller</A
+></DT
+><DT
+>6.4. <A
+HREF="samba-pdc.html#AEN663"
+>Creating Machine Trust Accounts and Joining Clients to the
+Domain</A
+></DT
+><DD
+><DL
+><DT
+>6.4.1. <A
+HREF="samba-pdc.html#AEN682"
+>Manual Creation of Machine Trust Accounts</A
+></DT
+><DT
+>6.4.2. <A
+HREF="samba-pdc.html#AEN723"
+>"On-the-Fly" Creation of Machine Trust Accounts</A
+></DT
+><DT
+>6.4.3. <A
+HREF="samba-pdc.html#AEN732"
+>Joining the Client to the Domain</A
+></DT
+></DL
+></DD
+><DT
+>6.5. <A
+HREF="samba-pdc.html#AEN747"
+>Common Problems and Errors</A
+></DT
+><DT
+>6.6. <A
+HREF="samba-pdc.html#AEN795"
+>System Policies and Profiles</A
+></DT
+><DT
+>6.7. <A
+HREF="samba-pdc.html#AEN839"
+>What other help can I get?</A
+></DT
+><DT
+>6.8. <A
+HREF="samba-pdc.html#AEN953"
+>Domain Control for Windows 9x/ME</A
+></DT
+><DD
+><DL
+><DT
+>6.8.1. <A
+HREF="samba-pdc.html#AEN979"
+>Configuration Instructions: Network Logons</A
+></DT
+><DT
+>6.8.2. <A
+HREF="samba-pdc.html#AEN998"
+>Configuration Instructions: Setting up Roaming User Profiles</A
+></DT
+></DL
+></DD
+><DT
+>6.9. <A
+HREF="samba-pdc.html#AEN1091"
+>DOMAIN_CONTROL.txt : Windows NT Domain Control &#38; Samba</A
+></DT
+></DL
+></DD
+><DT
+>7. <A
+HREF="samba-bdc.html"
+>How to Act as a Backup Domain Controller in a Purely Samba Controlled Domain</A
+></DT
+><DD
+><DL
+><DT
+>7.1. <A
+HREF="samba-bdc.html#AEN1127"
+>Prerequisite Reading</A
+></DT
+><DT
+>7.2. <A
+HREF="samba-bdc.html#AEN1131"
+>Background</A
+></DT
+><DT
+>7.3. <A
+HREF="samba-bdc.html#AEN1139"
+>What qualifies a Domain Controller on the network?</A
+></DT
+><DD
+><DL
+><DT
+>7.3.1. <A
+HREF="samba-bdc.html#AEN1142"
+>How does a Workstation find its domain controller?</A
+></DT
+><DT
+>7.3.2. <A
+HREF="samba-bdc.html#AEN1145"
+>When is the PDC needed?</A
+></DT
+></DL
+></DD
+><DT
+>7.4. <A
+HREF="samba-bdc.html#AEN1148"
+>Can Samba be a Backup Domain Controller?</A
+></DT
+><DT
+>7.5. <A
+HREF="samba-bdc.html#AEN1152"
+>How do I set up a Samba BDC?</A
+></DT
+><DD
+><DL
+><DT
+>7.5.1. <A
+HREF="samba-bdc.html#AEN1169"
+>How do I replicate the smbpasswd file?</A
+></DT
+></DL
+></DD
+></DL
+></DD
+><DT
+>8. <A
+HREF="ads.html"
+>Samba as a ADS domain member</A
+></DT
+><DD
+><DL
+><DT
+>8.1. <A
+HREF="ads.html#AEN1187"
+>Installing the required packages for Debian</A
+></DT
+><DT
+>8.2. <A
+HREF="ads.html#AEN1193"
+>Installing the required packages for RedHat</A
+></DT
+><DT
+>8.3. <A
+HREF="ads.html#AEN1202"
+>Compile Samba</A
+></DT
+><DT
+>8.4. <A
+HREF="ads.html#AEN1217"
+>Setup your /etc/krb5.conf</A
+></DT
+><DT
+>8.5. <A
+HREF="ads.html#AEN1227"
+>Create the computer account</A
+></DT
+><DD
+><DL
+><DT
+>8.5.1. <A
+HREF="ads.html#AEN1231"
+>Possible errors</A
+></DT
+></DL
+></DD
+><DT
+>8.6. <A
+HREF="ads.html#AEN1243"
+>Test your server setup</A
+></DT
+><DT
+>8.7. <A
+HREF="ads.html#AEN1248"
+>Testing with smbclient</A
+></DT
+><DT
+>8.8. <A
+HREF="ads.html#AEN1251"
+>Notes</A
+></DT
+></DL
+></DD
+><DT
+>9. <A
+HREF="domain-security.html"
+>Samba as a NT4 domain member</A
+></DT
+><DD
+><DL
+><DT
+>9.1. <A
+HREF="domain-security.html#AEN1273"
+>Joining an NT Domain with Samba 2.2</A
+></DT
+><DT
+>9.2. <A
+HREF="domain-security.html#AEN1337"
+>Samba and Windows 2000 Domains</A
+></DT
+><DT
+>9.3. <A
+HREF="domain-security.html#AEN1342"
+>Why is this better than security = server?</A
+></DT
+></DL
+></DD
+></DL
+></DIV
+></DIV
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+SUMMARY="Footer navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="pwencrypt.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="samba-howto-collection.html"
+ACCESSKEY="H"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="securitylevels.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>LanMan and NT Password Encryption in Samba</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+>&nbsp;</TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>User and Share security level (for servers not in a domain)</TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+> \ No newline at end of file
diff --git a/docs/htmldocs/unix-permissions.html b/docs/htmldocs/unix-permissions.html
index e9a3b5e671..f29d450e6d 100644
--- a/docs/htmldocs/unix-permissions.html
+++ b/docs/htmldocs/unix-permissions.html
@@ -1,194 +1,907 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter11.UNIX Permission Bits and Windows NT Access Control Lists</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"><link rel="home" href="index.html" title="SAMBA Project Documentation"><link rel="up" href="optional.html" title="PartIII.Advanced Configuration"><link rel="previous" href="passdb.html" title="Chapter10.User information database"><link rel="next" href="groupmapping.html" title="Chapter12.Configuring Group Mapping"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter11.UNIX Permission Bits and Windows NT Access Control Lists</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="passdb.html">Prev</a></td><th width="60%" align="center">PartIII.Advanced Configuration</th><td width="20%" align="right"><a accesskey="n" href="groupmapping.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="unix-permissions"></a>Chapter11.UNIX Permission Bits and Windows NT Access Control Lists</h2></div><div><div class="author"><h3 class="author">Jeremy Allison</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt>&lt;<a href="mailto:jra@samba.org">jra@samba.org</a>&gt;</tt></p></div></div></div></div><div><p class="pubdate">12 Apr 1999</p></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="unix-permissions.html#id2881950">Viewing and changing UNIX permissions using the NT
- security dialogs</a></dt><dt><a href="unix-permissions.html#id2881832">How to view file security on a Samba share</a></dt><dt><a href="unix-permissions.html#id2885176">Viewing file ownership</a></dt><dt><a href="unix-permissions.html#id2885297">Viewing file or directory permissions</a></dt><dd><dl><dt><a href="unix-permissions.html#id2885379">File Permissions</a></dt><dt><a href="unix-permissions.html#id2885483">Directory Permissions</a></dt></dl></dd><dt><a href="unix-permissions.html#id2885533">Modifying file or directory permissions</a></dt><dt><a href="unix-permissions.html#id2885693">Interaction with the standard Samba create mask
- parameters</a></dt><dt><a href="unix-permissions.html#id2886008">Interaction with the standard Samba file attribute
- mapping</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2881950"></a>Viewing and changing UNIX permissions using the NT
- security dialogs</h2></div></div><p>Windows NT clients can use their native security settings
- dialog box to view and modify the underlying UNIX permissions.</p><p>Note that this ability is careful not to compromise
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<HTML
+><HEAD
+><TITLE
+>UNIX Permission Bits and Windows NT Access Control Lists</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
+REL="HOME"
+TITLE="SAMBA Project Documentation"
+HREF="samba-howto-collection.html"><LINK
+REL="UP"
+TITLE="Optional configuration"
+HREF="optional.html"><LINK
+REL="PREVIOUS"
+TITLE="Integrating MS Windows networks with Samba"
+HREF="integrate-ms-networks.html"><LINK
+REL="NEXT"
+TITLE="Configuring PAM for distributed but centrally
+managed authentication"
+HREF="pam.html"></HEAD
+><BODY
+CLASS="CHAPTER"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><TABLE
+SUMMARY="Header navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>SAMBA Project Documentation</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="integrate-ms-networks.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+></TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="pam.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="CHAPTER"
+><H1
+><A
+NAME="UNIX-PERMISSIONS">Chapter 11. UNIX Permission Bits and Windows NT Access Control Lists</H1
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN1605">11.1. Viewing and changing UNIX permissions using the NT
+ security dialogs</H1
+><P
+>New in the Samba 2.0.4 release is the ability for Windows
+ NT clients to use their native security settings dialog box to
+ view and modify the underlying UNIX permissions.</P
+><P
+>Note that this ability is careful not to compromise
the security of the UNIX host Samba is running on, and
still obeys all the file permission rules that a Samba
- administrator can set.</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
- All access to Unix/Linux system file via Samba is controlled at
- the operating system file access control level. When trying to
- figure out file access problems it is vitally important to identify
- the identity of the Windows user as it is presented by Samba at
- the point of file access. This can best be determined from the
- Samba log files.
- </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2881832"></a>How to view file security on a Samba share</h2></div></div><p>From an NT4/2000/XP client, single-click with the right
+ administrator can set.</P
+><P
+>In Samba 2.0.4 and above the default value of the
+ parameter <A
+HREF="smb.conf.5.html#NTACLSUPPORT"
+TARGET="_top"
+><TT
+CLASS="PARAMETER"
+><I
+> nt acl support</I
+></TT
+></A
+> has been changed from
+ <TT
+CLASS="CONSTANT"
+>false</TT
+> to <TT
+CLASS="CONSTANT"
+>true</TT
+>, so
+ manipulation of permissions is turned on by default.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN1614">11.2. How to view file security on a Samba share</H1
+><P
+>From an NT 4.0 client, single-click with the right
mouse button on any file or directory in a Samba mounted
drive letter or UNC path. When the menu pops-up, click
- on the <span class="emphasis"><em>Properties</em></span> entry at the bottom of
- the menu. This brings up the file properties dialog
- box. Click on the tab <span class="emphasis"><em>Security</em></span> and you
- will see three buttons, <span class="emphasis"><em>Permissions</em></span>,
- <span class="emphasis"><em>Auditing</em></span>, and <span class="emphasis"><em>Ownership</em></span>.
- The <span class="emphasis"><em>Auditing</em></span> button will cause either
- an error message A requested privilege is not held
- by the client to appear if the user is not the
+ on the <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Properties</I
+></SPAN
+> entry at the bottom of
+ the menu. This brings up the normal file properties dialog
+ box, but with Samba 2.0.4 this will have a new tab along the top
+ marked <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Security</I
+></SPAN
+>. Click on this tab and you
+ will see three buttons, <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Permissions</I
+></SPAN
+>,
+ <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Auditing</I
+></SPAN
+>, and <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Ownership</I
+></SPAN
+>.
+ The <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Auditing</I
+></SPAN
+> button will cause either
+ an error message <SPAN
+CLASS="ERRORNAME"
+>A requested privilege is not held
+ by the client</SPAN
+> to appear if the user is not the
NT Administrator, or a dialog which is intended to allow an
Administrator to add auditing requirements to a file if the
user is logged on as the NT Administrator. This dialog is
non-functional with a Samba share at this time, as the only
- useful button, the <b>Add</b> button will not currently
- allow a list of users to be seen.</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2885176"></a>Viewing file ownership</h2></div></div><p>Clicking on the <b>&quot;Ownership&quot;</b> button
+ useful button, the <B
+CLASS="COMMAND"
+>Add</B
+> button will not currently
+ allow a list of users to be seen.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN1625">11.3. Viewing file ownership</H1
+><P
+>Clicking on the <B
+CLASS="COMMAND"
+>"Ownership"</B
+> button
brings up a dialog box telling you who owns the given file. The
- owner name will be of the form :</p><p><b>&quot;SERVER\user (Long name)&quot;</b></p><p>Where <i><tt>SERVER</tt></i> is the NetBIOS name of
- the Samba server, <i><tt>user</tt></i> is the user name of
- the UNIX user who owns the file, and <i><tt>(Long name)</tt></i>
+ owner name will be of the form :</P
+><P
+><B
+CLASS="COMMAND"
+>"SERVER\user (Long name)"</B
+></P
+><P
+>Where <TT
+CLASS="REPLACEABLE"
+><I
+>SERVER</I
+></TT
+> is the NetBIOS name of
+ the Samba server, <TT
+CLASS="REPLACEABLE"
+><I
+>user</I
+></TT
+> is the user name of
+ the UNIX user who owns the file, and <TT
+CLASS="REPLACEABLE"
+><I
+>(Long name)</I
+></TT
+>
is the descriptive string identifying the user (normally found in the
- GECOS field of the UNIX password database). Click on the <b>Close
- </b> button to remove this dialog.</p><p>If the parameter <i><tt>nt acl support</tt></i>
- is set to <tt>false</tt> then the file owner will
- be shown as the NT user <b>&quot;Everyone&quot;</b>.</p><p>The <b>Take Ownership</b> button will not allow
+ GECOS field of the UNIX password database). Click on the <B
+CLASS="COMMAND"
+>Close
+ </B
+> button to remove this dialog.</P
+><P
+>If the parameter <TT
+CLASS="PARAMETER"
+><I
+>nt acl support</I
+></TT
+>
+ is set to <TT
+CLASS="CONSTANT"
+>false</TT
+> then the file owner will
+ be shown as the NT user <B
+CLASS="COMMAND"
+>"Everyone"</B
+>.</P
+><P
+>The <B
+CLASS="COMMAND"
+>Take Ownership</B
+> button will not allow
you to change the ownership of this file to yourself (clicking on
it will display a dialog box complaining that the user you are
currently logged onto the NT client cannot be found). The reason
for this is that changing the ownership of a file is a privileged
- operation in UNIX, available only to the <span class="emphasis"><em>root</em></span>
+ operation in UNIX, available only to the <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>root</I
+></SPAN
+>
user. As clicking on this button causes NT to attempt to change
the ownership of a file to the current user logged into the NT
- client this will not work with Samba at this time.</p><p>There is an NT chown command that will work with Samba
+ client this will not work with Samba at this time.</P
+><P
+>There is an NT chown command that will work with Samba
and allow a user with Administrator privilege connected
- to a Samba server as root to change the ownership of
+ to a Samba 2.0.4 server as root to change the ownership of
files on both a local NTFS filesystem or remote mounted NTFS
- or Samba drive. This is available as part of the <span class="emphasis"><em>Seclib
- </em></span> NT security library written by Jeremy Allison of
- the Samba Team, available from the main Samba ftp site.</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2885297"></a>Viewing file or directory permissions</h2></div></div><p>The third button is the <b>&quot;Permissions&quot;</b>
+ or Samba drive. This is available as part of the <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Seclib
+ </I
+></SPAN
+> NT security library written by Jeremy Allison of
+ the Samba Team, available from the main Samba ftp site.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN1645">11.4. Viewing file or directory permissions</H1
+><P
+>The third button is the <B
+CLASS="COMMAND"
+>"Permissions"</B
+>
button. Clicking on this brings up a dialog box that shows both
the permissions and the UNIX owner of the file or directory.
- The owner is displayed in the form :</p><p><b>&quot;SERVER\user (Long name)&quot;</b></p><p>Where <i><tt>SERVER</tt></i> is the NetBIOS name of
- the Samba server, <i><tt>user</tt></i> is the user name of
- the UNIX user who owns the file, and <i><tt>(Long name)</tt></i>
+ The owner is displayed in the form :</P
+><P
+><B
+CLASS="COMMAND"
+>"SERVER\user (Long name)"</B
+></P
+><P
+>Where <TT
+CLASS="REPLACEABLE"
+><I
+>SERVER</I
+></TT
+> is the NetBIOS name of
+ the Samba server, <TT
+CLASS="REPLACEABLE"
+><I
+>user</I
+></TT
+> is the user name of
+ the UNIX user who owns the file, and <TT
+CLASS="REPLACEABLE"
+><I
+>(Long name)</I
+></TT
+>
is the descriptive string identifying the user (normally found in the
- GECOS field of the UNIX password database).</p><p>If the parameter <i><tt>nt acl support</tt></i>
- is set to <tt>false</tt> then the file owner will
- be shown as the NT user <b>&quot;Everyone&quot;</b> and the
- permissions will be shown as NT &quot;Full Control&quot;.</p><p>The permissions field is displayed differently for files
+ GECOS field of the UNIX password database).</P
+><P
+>If the parameter <TT
+CLASS="PARAMETER"
+><I
+>nt acl support</I
+></TT
+>
+ is set to <TT
+CLASS="CONSTANT"
+>false</TT
+> then the file owner will
+ be shown as the NT user <B
+CLASS="COMMAND"
+>"Everyone"</B
+> and the
+ permissions will be shown as NT "Full Control".</P
+><P
+>The permissions field is displayed differently for files
and directories, so I'll describe the way file permissions
- are displayed first.</p><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2885379"></a>File Permissions</h3></div></div><p>The standard UNIX user/group/world triple and
- the corresponding &quot;read&quot;, &quot;write&quot;, &quot;execute&quot; permissions
+ are displayed first.</P
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN1660">11.4.1. File Permissions</H2
+><P
+>The standard UNIX user/group/world triple and
+ the corresponding "read", "write", "execute" permissions
triples are mapped by Samba into a three element NT ACL
with the 'r', 'w', and 'x' bits mapped into the corresponding
NT permissions. The UNIX world permissions are mapped into
- the global NT group <b>Everyone</b>, followed
+ the global NT group <B
+CLASS="COMMAND"
+>Everyone</B
+>, followed
by the list of permissions allowed for UNIX world. The UNIX
owner and group permissions are displayed as an NT
- <b>user</b> icon and an NT <b>local
- group</b> icon respectively followed by the list
- of permissions allowed for the UNIX user and group.</p><p>As many UNIX permission sets don't map into common
- NT names such as <b>&quot;read&quot;</b>, <b>
- &quot;change&quot;</b> or <b>&quot;full control&quot;</b> then
- usually the permissions will be prefixed by the words <b>
- &quot;Special Access&quot;</b> in the NT display list.</p><p>But what happens if the file has no permissions allowed
+ <B
+CLASS="COMMAND"
+>user</B
+> icon and an NT <B
+CLASS="COMMAND"
+>local
+ group</B
+> icon respectively followed by the list
+ of permissions allowed for the UNIX user and group.</P
+><P
+>As many UNIX permission sets don't map into common
+ NT names such as <B
+CLASS="COMMAND"
+>"read"</B
+>, <B
+CLASS="COMMAND"
+> "change"</B
+> or <B
+CLASS="COMMAND"
+>"full control"</B
+> then
+ usually the permissions will be prefixed by the words <B
+CLASS="COMMAND"
+> "Special Access"</B
+> in the NT display list.</P
+><P
+>But what happens if the file has no permissions allowed
for a particular UNIX user group or world component ? In order
- to allow &quot;no permissions&quot; to be seen and modified then Samba
- overloads the NT <b>&quot;Take Ownership&quot;</b> ACL attribute
+ to allow "no permissions" to be seen and modified then Samba
+ overloads the NT <B
+CLASS="COMMAND"
+>"Take Ownership"</B
+> ACL attribute
(which has no meaning in UNIX) and reports a component with
- no permissions as having the NT <b>&quot;O&quot;</b> bit set.
+ no permissions as having the NT <B
+CLASS="COMMAND"
+>"O"</B
+> bit set.
This was chosen of course to make it look like a zero, meaning
zero permissions. More details on the decision behind this will
- be given below.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2885483"></a>Directory Permissions</h3></div></div><p>Directories on an NT NTFS file system have two
+ be given below.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN1674">11.4.2. Directory Permissions</H2
+><P
+>Directories on an NT NTFS file system have two
different sets of permissions. The first set of permissions
is the ACL set on the directory itself, this is usually displayed
- in the first set of parentheses in the normal <b>&quot;RW&quot;</b>
+ in the first set of parentheses in the normal <B
+CLASS="COMMAND"
+>"RW"</B
+>
NT style. This first set of permissions is created by Samba in
exactly the same way as normal file permissions are, described
- above, and is displayed in the same way.</p><p>The second set of directory permissions has no real meaning
- in the UNIX permissions world and represents the <b>
- &quot;inherited&quot;</b> permissions that any file created within
- this directory would inherit.</p><p>Samba synthesises these inherited permissions for NT by
+ above, and is displayed in the same way.</P
+><P
+>The second set of directory permissions has no real meaning
+ in the UNIX permissions world and represents the <B
+CLASS="COMMAND"
+> "inherited"</B
+> permissions that any file created within
+ this directory would inherit.</P
+><P
+>Samba synthesises these inherited permissions for NT by
returning as an NT ACL the UNIX permission mode that a new file
- created by Samba on this share would receive.</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2885533"></a>Modifying file or directory permissions</h2></div></div><p>Modifying file and directory permissions is as simple
+ created by Samba on this share would receive.</P
+></DIV
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN1681">11.5. Modifying file or directory permissions</H1
+><P
+>Modifying file and directory permissions is as simple
as changing the displayed permissions in the dialog box, and
- clicking the <b>OK</b> button. However, there are
+ clicking the <B
+CLASS="COMMAND"
+>OK</B
+> button. However, there are
limitations that a user needs to be aware of, and also interactions
with the standard Samba permission masks and mapping of DOS
- attributes that need to also be taken into account.</p><p>If the parameter <i><tt>nt acl support</tt></i>
- is set to <tt>false</tt> then any attempt to set
- security permissions will fail with an <b>&quot;Access Denied&quot;
- </b> message.</p><p>The first thing to note is that the <b>&quot;Add&quot;</b>
- button will not return a list of users in Samba (it will give
- an error message of <b>&quot;The remote procedure call failed
- and did not execute&quot;</b>). This means that you can only
+ attributes that need to also be taken into account.</P
+><P
+>If the parameter <TT
+CLASS="PARAMETER"
+><I
+>nt acl support</I
+></TT
+>
+ is set to <TT
+CLASS="CONSTANT"
+>false</TT
+> then any attempt to set
+ security permissions will fail with an <B
+CLASS="COMMAND"
+>"Access Denied"
+ </B
+> message.</P
+><P
+>The first thing to note is that the <B
+CLASS="COMMAND"
+>"Add"</B
+>
+ button will not return a list of users in Samba 2.0.4 (it will give
+ an error message of <B
+CLASS="COMMAND"
+>"The remote procedure call failed
+ and did not execute"</B
+>). This means that you can only
manipulate the current user/group/world permissions listed in
the dialog box. This actually works quite well as these are the
- only permissions that UNIX actually has.</p><p>If a permission triple (either user, group, or world)
+ only permissions that UNIX actually has.</P
+><P
+>If a permission triple (either user, group, or world)
is removed from the list of permissions in the NT dialog box,
- then when the <b>&quot;OK&quot;</b> button is pressed it will
- be applied as &quot;no permissions&quot; on the UNIX side. If you then
- view the permissions again the &quot;no permissions&quot; entry will appear
- as the NT <b>&quot;O&quot;</b> flag, as described above. This
+ then when the <B
+CLASS="COMMAND"
+>"OK"</B
+> button is pressed it will
+ be applied as "no permissions" on the UNIX side. If you then
+ view the permissions again the "no permissions" entry will appear
+ as the NT <B
+CLASS="COMMAND"
+>"O"</B
+> flag, as described above. This
allows you to add permissions back to a file or directory once
- you have removed them from a triple component.</p><p>As UNIX supports only the &quot;r&quot;, &quot;w&quot; and &quot;x&quot; bits of
- an NT ACL then if other NT security attributes such as &quot;Delete
- access&quot; are selected then they will be ignored when applied on
- the Samba server.</p><p>When setting permissions on a directory the second
+ you have removed them from a triple component.</P
+><P
+>As UNIX supports only the "r", "w" and "x" bits of
+ an NT ACL then if other NT security attributes such as "Delete
+ access" are selected then they will be ignored when applied on
+ the Samba server.</P
+><P
+>When setting permissions on a directory the second
set of permissions (in the second set of parentheses) is
by default applied to all files within that directory. If this
- is not what you want you must uncheck the <b>&quot;Replace
- permissions on existing files&quot;</b> checkbox in the NT
- dialog before clicking <b>&quot;OK&quot;</b>.</p><p>If you wish to remove all permissions from a
+ is not what you want you must uncheck the <B
+CLASS="COMMAND"
+>"Replace
+ permissions on existing files"</B
+> checkbox in the NT
+ dialog before clicking <B
+CLASS="COMMAND"
+>"OK"</B
+>.</P
+><P
+>If you wish to remove all permissions from a
user/group/world component then you may either highlight the
- component and click the <b>&quot;Remove&quot;</b> button,
- or set the component to only have the special <b>&quot;Take
- Ownership&quot;</b> permission (displayed as <b>&quot;O&quot;
- </b>) highlighted.</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2885693"></a>Interaction with the standard Samba create mask
- parameters</h2></div></div><p>There are four parameters
- to control interaction with the standard Samba create mask parameters.
- These are :</p><p><i><tt>security mask</tt></i></p><p><i><tt>force security mode</tt></i></p><p><i><tt>directory security mask</tt></i></p><p><i><tt>force directory security mode</tt></i></p><p>Once a user clicks <b>&quot;OK&quot;</b> to apply the
+ component and click the <B
+CLASS="COMMAND"
+>"Remove"</B
+> button,
+ or set the component to only have the special <B
+CLASS="COMMAND"
+>"Take
+ Ownership"</B
+> permission (displayed as <B
+CLASS="COMMAND"
+>"O"
+ </B
+>) highlighted.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN1703">11.6. Interaction with the standard Samba create mask
+ parameters</H1
+><P
+>Note that with Samba 2.0.5 there are four new parameters
+ to control this interaction. These are :</P
+><P
+><TT
+CLASS="PARAMETER"
+><I
+>security mask</I
+></TT
+></P
+><P
+><TT
+CLASS="PARAMETER"
+><I
+>force security mode</I
+></TT
+></P
+><P
+><TT
+CLASS="PARAMETER"
+><I
+>directory security mask</I
+></TT
+></P
+><P
+><TT
+CLASS="PARAMETER"
+><I
+>force directory security mode</I
+></TT
+></P
+><P
+>Once a user clicks <B
+CLASS="COMMAND"
+>"OK"</B
+> to apply the
permissions Samba maps the given permissions into a user/group/world
r/w/x triple set, and then will check the changed permissions for a
- file against the bits set in the <a href="smb.conf.5.html#SECURITYMASK" target="_top">
- <i><tt>security mask</tt></i></a> parameter. Any bits that
+ file against the bits set in the <A
+HREF="smb.conf.5.html#SECURITYMASK"
+TARGET="_top"
+>
+ <TT
+CLASS="PARAMETER"
+><I
+>security mask</I
+></TT
+></A
+> parameter. Any bits that
were changed that are not set to '1' in this parameter are left alone
- in the file permissions.</p><p>Essentially, zero bits in the <i><tt>security mask</tt></i>
- mask may be treated as a set of bits the user is <span class="emphasis"><em>not</em></span>
+ in the file permissions.</P
+><P
+>Essentially, zero bits in the <TT
+CLASS="PARAMETER"
+><I
+>security mask</I
+></TT
+>
+ mask may be treated as a set of bits the user is <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>not</I
+></SPAN
+>
allowed to change, and one bits are those the user is allowed to change.
- </p><p>If not set explicitly this parameter is set to the same value as
- the <a href="smb.conf.5.html#CREATEMASK" target="_top"><i><tt>create mask
- </tt></i></a> parameter. To allow a user to modify all the
- user/group/world permissions on a file, set this parameter
- to 0777.</p><p>Next Samba checks the changed permissions for a file against
- the bits set in the <a href="smb.conf.5.html#FORCESECURITYMODE" target="_top">
- <i><tt>force security mode</tt></i></a> parameter. Any bits
+ </P
+><P
+>If not set explicitly this parameter is set to the same value as
+ the <A
+HREF="smb.conf.5.html#CREATEMASK"
+TARGET="_top"
+><TT
+CLASS="PARAMETER"
+><I
+>create mask
+ </I
+></TT
+></A
+> parameter to provide compatibility with Samba 2.0.4
+ where this permission change facility was introduced. To allow a user to
+ modify all the user/group/world permissions on a file, set this parameter
+ to 0777.</P
+><P
+>Next Samba checks the changed permissions for a file against
+ the bits set in the <A
+HREF="smb.conf.5.html#FORCESECURITYMODE"
+TARGET="_top"
+> <TT
+CLASS="PARAMETER"
+><I
+>force security mode</I
+></TT
+></A
+> parameter. Any bits
that were changed that correspond to bits set to '1' in this parameter
- are forced to be set.</p><p>Essentially, bits set in the <i><tt>force security mode
- </tt></i> parameter may be treated as a set of bits that, when
- modifying security on a file, the user has always set to be 'on'.</p><p>If not set explicitly this parameter is set to the same value
- as the <a href="smb.conf.5.html#FORCECREATEMODE" target="_top"><i><tt>force
- create mode</tt></i></a> parameter.
+ are forced to be set.</P
+><P
+>Essentially, bits set in the <TT
+CLASS="PARAMETER"
+><I
+>force security mode
+ </I
+></TT
+> parameter may be treated as a set of bits that, when
+ modifying security on a file, the user has always set to be 'on'.</P
+><P
+>If not set explicitly this parameter is set to the same value
+ as the <A
+HREF="smb.conf.5.html#FORCECREATEMODE"
+TARGET="_top"
+><TT
+CLASS="PARAMETER"
+><I
+>force
+ create mode</I
+></TT
+></A
+> parameter to provide compatibility
+ with Samba 2.0.4 where the permission change facility was introduced.
To allow a user to modify all the user/group/world permissions on a file
- with no restrictions set this parameter to 000.</p><p>The <i><tt>security mask</tt></i> and <i><tt>force
- security mode</tt></i> parameters are applied to the change
- request in that order.</p><p>For a directory Samba will perform the same operations as
- described above for a file except using the parameter <i><tt>
- directory security mask</tt></i> instead of <i><tt>security
- mask</tt></i>, and <i><tt>force directory security mode
- </tt></i> parameter instead of <i><tt>force security mode
- </tt></i>.</p><p>The <i><tt>directory security mask</tt></i> parameter
- by default is set to the same value as the <i><tt>directory mask
- </tt></i> parameter and the <i><tt>force directory security
- mode</tt></i> parameter by default is set to the same value as
- the <i><tt>force directory mode</tt></i> parameter. </p><p>In this way Samba enforces the permission restrictions that
+ with no restrictions set this parameter to 000.</P
+><P
+>The <TT
+CLASS="PARAMETER"
+><I
+>security mask</I
+></TT
+> and <TT
+CLASS="PARAMETER"
+><I
+>force
+ security mode</I
+></TT
+> parameters are applied to the change
+ request in that order.</P
+><P
+>For a directory Samba will perform the same operations as
+ described above for a file except using the parameter <TT
+CLASS="PARAMETER"
+><I
+> directory security mask</I
+></TT
+> instead of <TT
+CLASS="PARAMETER"
+><I
+>security
+ mask</I
+></TT
+>, and <TT
+CLASS="PARAMETER"
+><I
+>force directory security mode
+ </I
+></TT
+> parameter instead of <TT
+CLASS="PARAMETER"
+><I
+>force security mode
+ </I
+></TT
+>.</P
+><P
+>The <TT
+CLASS="PARAMETER"
+><I
+>directory security mask</I
+></TT
+> parameter
+ by default is set to the same value as the <TT
+CLASS="PARAMETER"
+><I
+>directory mask
+ </I
+></TT
+> parameter and the <TT
+CLASS="PARAMETER"
+><I
+>force directory security
+ mode</I
+></TT
+> parameter by default is set to the same value as
+ the <TT
+CLASS="PARAMETER"
+><I
+>force directory mode</I
+></TT
+> parameter to provide
+ compatibility with Samba 2.0.4 where the permission change facility
+ was introduced.</P
+><P
+>In this way Samba enforces the permission restrictions that
an administrator can set on a Samba share, whilst still allowing users
- to modify the permission bits within that restriction.</p><p>If you want to set up a share that allows users full control
+ to modify the permission bits within that restriction.</P
+><P
+>If you want to set up a share that allows users full control
in modifying the permission bits on their files and directories and
doesn't force any particular bits to be set 'on', then set the following
- parameters in the <tt>smb.conf</tt> file in that share specific section :</p><p><i><tt>security mask = 0777</tt></i></p><p><i><tt>force security mode = 0</tt></i></p><p><i><tt>directory security mask = 0777</tt></i></p><p><i><tt>force directory security mode = 0</tt></i></p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2886008"></a>Interaction with the standard Samba file attribute
- mapping</h2></div></div><p>Samba maps some of the DOS attribute bits (such as &quot;read
- only&quot;) into the UNIX permissions of a file. This means there can
+ parameters in the <A
+HREF="smb.conf.5.html"
+TARGET="_top"
+><TT
+CLASS="FILENAME"
+>smb.conf(5)
+ </TT
+></A
+> file in that share specific section :</P
+><P
+><TT
+CLASS="PARAMETER"
+><I
+>security mask = 0777</I
+></TT
+></P
+><P
+><TT
+CLASS="PARAMETER"
+><I
+>force security mode = 0</I
+></TT
+></P
+><P
+><TT
+CLASS="PARAMETER"
+><I
+>directory security mask = 0777</I
+></TT
+></P
+><P
+><TT
+CLASS="PARAMETER"
+><I
+>force directory security mode = 0</I
+></TT
+></P
+><P
+>As described, in Samba 2.0.4 the parameters :</P
+><P
+><TT
+CLASS="PARAMETER"
+><I
+>create mask</I
+></TT
+></P
+><P
+><TT
+CLASS="PARAMETER"
+><I
+>force create mode</I
+></TT
+></P
+><P
+><TT
+CLASS="PARAMETER"
+><I
+>directory mask</I
+></TT
+></P
+><P
+><TT
+CLASS="PARAMETER"
+><I
+>force directory mode</I
+></TT
+></P
+><P
+>were used instead of the parameters discussed here.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN1767">11.7. Interaction with the standard Samba file attribute
+ mapping</H1
+><P
+>Samba maps some of the DOS attribute bits (such as "read
+ only") into the UNIX permissions of a file. This means there can
be a conflict between the permission bits set via the security
dialog and the permission bits set by the file attribute mapping.
- </p><p>One way this can show up is if a file has no UNIX read access
- for the owner it will show up as &quot;read only&quot; in the standard
+ </P
+><P
+>One way this can show up is if a file has no UNIX read access
+ for the owner it will show up as "read only" in the standard
file attributes tabbed dialog. Unfortunately this dialog is
- the same one that contains the security info in another tab.</p><p>What this can mean is that if the owner changes the permissions
+ the same one that contains the security info in another tab.</P
+><P
+>What this can mean is that if the owner changes the permissions
to allow themselves read access using the security dialog, clicks
- <b>&quot;OK&quot;</b> to get back to the standard attributes tab
- dialog, and then clicks <b>&quot;OK&quot;</b> on that dialog, then
+ <B
+CLASS="COMMAND"
+>"OK"</B
+> to get back to the standard attributes tab
+ dialog, and then clicks <B
+CLASS="COMMAND"
+>"OK"</B
+> on that dialog, then
NT will set the file permissions back to read-only (as that is what
the attributes still say in the dialog). This means that after setting
- permissions and clicking <b>&quot;OK&quot;</b> to get back to the
- attributes dialog you should always hit <b>&quot;Cancel&quot;</b>
- rather than <b>&quot;OK&quot;</b> to ensure that your changes
- are not overridden.</p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="passdb.html">Prev</a></td><td width="20%" align="center"><a accesskey="u" href="optional.html">Up</a></td><td width="40%" align="right"><a accesskey="n" href="groupmapping.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter10.User information database</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">Chapter12.Configuring Group Mapping</td></tr></table></div></body></html>
+ permissions and clicking <B
+CLASS="COMMAND"
+>"OK"</B
+> to get back to the
+ attributes dialog you should always hit <B
+CLASS="COMMAND"
+>"Cancel"</B
+>
+ rather than <B
+CLASS="COMMAND"
+>"OK"</B
+> to ensure that your changes
+ are not overridden.</P
+></DIV
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+SUMMARY="Footer navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="integrate-ms-networks.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="samba-howto-collection.html"
+ACCESSKEY="H"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="pam.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>Integrating MS Windows networks with Samba</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="optional.html"
+ACCESSKEY="U"
+>Up</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>Configuring PAM for distributed but centrally
+managed authentication</TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+> \ No newline at end of file
diff --git a/docs/htmldocs/vfs.html b/docs/htmldocs/vfs.html
index fcaca133fe..11934ae47c 100644
--- a/docs/htmldocs/vfs.html
+++ b/docs/htmldocs/vfs.html
@@ -5,19 +5,20 @@
>Stackable VFS modules</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
REL="HOME"
TITLE="SAMBA Project Documentation"
HREF="samba-howto-collection.html"><LINK
REL="UP"
-TITLE="Advanced Configuration"
+TITLE="Optional configuration"
HREF="optional.html"><LINK
REL="PREVIOUS"
-TITLE="PAM Configuration for Centrally Managed Authentication"
-HREF="pam.html"><LINK
+TITLE="Passdb XML plugin"
+HREF="pdb-xml.html"><LINK
REL="NEXT"
-TITLE="Hosting a Microsoft Distributed File System tree on Samba"
-HREF="msdfs.html"></HEAD
+TITLE="Storing Samba's User/Machine Account information in an LDAP Directory"
+HREF="samba-ldap-howto.html"></HEAD
><BODY
CLASS="CHAPTER"
BGCOLOR="#FFFFFF"
@@ -45,7 +46,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
-HREF="pam.html"
+HREF="pdb-xml.html"
ACCESSKEY="P"
>Prev</A
></TD
@@ -59,7 +60,7 @@ WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
-HREF="msdfs.html"
+HREF="samba-ldap-howto.html"
ACCESSKEY="N"
>Next</A
></TD
@@ -72,79 +73,13 @@ WIDTH="100%"></DIV
CLASS="CHAPTER"
><H1
><A
-NAME="VFS"
-></A
->Chapter 21. Stackable VFS modules</H1
-><DIV
-CLASS="TOC"
-><DL
-><DT
-><B
->Table of Contents</B
-></DT
-><DT
->21.1. <A
-HREF="vfs.html#AEN3600"
->Introduction and configuration</A
-></DT
-><DT
->21.2. <A
-HREF="vfs.html#AEN3609"
->Included modules</A
-></DT
-><DD
-><DL
-><DT
->21.2.1. <A
-HREF="vfs.html#AEN3611"
->audit</A
-></DT
-><DT
->21.2.2. <A
-HREF="vfs.html#AEN3619"
->extd_audit</A
-></DT
-><DT
->21.2.3. <A
-HREF="vfs.html#AEN3623"
->recycle</A
-></DT
-><DT
->21.2.4. <A
-HREF="vfs.html#AEN3660"
->netatalk</A
-></DT
-></DL
-></DD
-><DT
->21.3. <A
-HREF="vfs.html#AEN3667"
->VFS modules available elsewhere</A
-></DT
-><DD
-><DL
-><DT
->21.3.1. <A
-HREF="vfs.html#AEN3671"
->DatabaseFS</A
-></DT
-><DT
->21.3.2. <A
-HREF="vfs.html#AEN3679"
->vscan</A
-></DT
-></DL
-></DD
-></DL
-></DIV
+NAME="VFS">Chapter 18. Stackable VFS modules</H1
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="AEN3600"
->21.1. Introduction and configuration</A
-></H1
+NAME="AEN2640">18.1. Introduction and configuration</H1
><P
>Since samba 3.0, samba supports stackable VFS(Virtual File System) modules.
Samba passes each request to access the unix file system thru the loaded VFS modules.
@@ -183,17 +118,13 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="AEN3609"
->21.2. Included modules</A
-></H1
+NAME="AEN2649">18.2. Included modules</H1
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
-NAME="AEN3611"
->21.2.1. audit</A
-></H2
+NAME="AEN2651">18.2.1. audit</H2
><P
>A simple module to audit file access to the syslog
facility. The following operations are logged:
@@ -229,31 +160,7 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
-NAME="AEN3619"
->21.2.2. extd_audit</A
-></H2
-><P
->This module is identical with the <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->audit</I
-></SPAN
-> module above except
-that it sends audit logs to both syslog as well as the smbd log file/s. The
-loglevel for this module is set in the smb.conf file. At loglevel = 0, only file
-and directory deletions and directory and file creations are logged. At loglevel = 1
-file opens are renames and permission changes are logged , while at loglevel = 2 file
-open and close calls are logged also.</P
-></DIV
-><DIV
-CLASS="SECT2"
-><H2
-CLASS="SECT2"
-><A
-NAME="AEN3623"
->21.2.3. recycle</A
-></H2
+NAME="AEN2659">18.2.2. recycle</H2
><P
>A recycle-bin like modules. When used any unlink call
will be intercepted and files moved to the recycle
@@ -322,9 +229,7 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
-NAME="AEN3660"
->21.2.4. netatalk</A
-></H2
+NAME="AEN2696">18.2.3. netatalk</H2
><P
>A netatalk module, that will ease co-existence of samba and
netatalk file sharing services.</P
@@ -355,9 +260,7 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="AEN3667"
->21.3. VFS modules available elsewhere</A
-></H1
+NAME="AEN2703">18.3. VFS modules available elsewhere</H1
><P
>This section contains a listing of various other VFS modules that
have been posted but don't currently reside in the Samba CVS
@@ -371,9 +274,7 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
-NAME="AEN3671"
->21.3.1. DatabaseFS</A
-></H2
+NAME="AEN2707">18.3.1. DatabaseFS</H2
><P
>URL: <A
HREF="http://www.css.tayloru.edu/~elorimer/databasefs/index.php"
@@ -405,9 +306,7 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
-NAME="AEN3679"
->21.3.2. vscan</A
-></H2
+NAME="AEN2715">18.3.2. vscan</H2
><P
>URL: <A
HREF="http://www.openantivirus.org/"
@@ -439,7 +338,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
-HREF="pam.html"
+HREF="pdb-xml.html"
ACCESSKEY="P"
>Prev</A
></TD
@@ -457,7 +356,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
-HREF="msdfs.html"
+HREF="samba-ldap-howto.html"
ACCESSKEY="N"
>Next</A
></TD
@@ -467,7 +366,7 @@ ACCESSKEY="N"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
->PAM Configuration for Centrally Managed Authentication</TD
+>Passdb XML plugin</TD
><TD
WIDTH="34%"
ALIGN="center"
@@ -481,7 +380,7 @@ ACCESSKEY="U"
WIDTH="33%"
ALIGN="right"
VALIGN="top"
->Hosting a Microsoft Distributed File System tree on Samba</TD
+>Storing Samba's User/Machine Account information in an LDAP Directory</TD
></TR
></TABLE
></DIV
diff --git a/docs/htmldocs/vfstest.1.html b/docs/htmldocs/vfstest.1.html
index 8c5565f02b..1fd7880805 100644
--- a/docs/htmldocs/vfstest.1.html
+++ b/docs/htmldocs/vfstest.1.html
@@ -1,43 +1,487 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>vfstest</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="vfstest.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>vfstest &#8212; tool for testing samba VFS modules </p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><tt>vfstest</tt> [-d debuglevel] [-c command] [-l logfile] [-h]</p></div></div><div class="refsect1" lang="en"><h2>DESCRIPTION</h2><p>This tool is part of the <a href="Samba.7.html">Samba(7)</a> suite.</p><p><b>vfstest</b> is a small command line
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
+<HTML
+><HEAD
+><TITLE
+>vfstest</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"></HEAD
+><BODY
+CLASS="REFENTRY"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><H1
+><A
+NAME="VFSTEST">vfstest</H1
+><DIV
+CLASS="REFNAMEDIV"
+><A
+NAME="AEN5"
+></A
+><H2
+>Name</H2
+>vfstest&nbsp;--&nbsp;tool for testing samba VFS modules </DIV
+><DIV
+CLASS="REFSYNOPSISDIV"
+><A
+NAME="AEN8"><H2
+>Synopsis</H2
+><P
+><B
+CLASS="COMMAND"
+>vfstest</B
+> [-d debuglevel] [-c command] [-l logfile] [-h]</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN15"
+></A
+><H2
+>DESCRIPTION</H2
+><P
+>This tool is part of the <A
+HREF="samba.7.html"
+TARGET="_top"
+> Samba</A
+> suite.</P
+><P
+><B
+CLASS="COMMAND"
+>vfstest</B
+> is a small command line
utility that has the ability to test dso samba VFS modules. It gives the
user the ability to call the various VFS functions manually and
supports cascaded VFS modules.
- </p></div><div class="refsect1" lang="en"><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-c|--command=command</span></dt><dd><p>Execute the specified (colon-separated) commands.
+ </P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN21"
+></A
+><H2
+>OPTIONS</H2
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>-c|--command=command</DT
+><DD
+><P
+>Execute the specified (colon-separated) commands.
See below for the commands that are available.
- </p></dd><dt><span class="term">-h|--help</span></dt><dd><p>Print a summary of command line options.
-</p></dd><dt><span class="term">-l|--logfile=logbasename</span></dt><dd><p>File name for log/debug files. The extension
- <tt>'.client'</tt> will be appended. The log file is never removed
- by the client.
- </p></dd><dt><span class="term">-V</span></dt><dd><p>Prints the version number for
-<b>smbd</b>.</p></dd><dt><span class="term">-s &lt;configuration file&gt;</span></dt><dd><p>The file specified contains the
-configuration details required by the server. The
-information in this file includes server-specific
-information such as what printcap file to use, as well
-as descriptions of all the services that the server is
-to provide. See <a href="smb.conf.5.html" target="_top"><tt>
-smb.conf(5)</tt></a> for more information.
-The default configuration file name is determined at
-compile time.</p></dd><dt><span class="term">-d|--debug=debuglevel</span></dt><dd><p><i><tt>debuglevel</tt></i> is an integer
+ </P
+></DD
+><DT
+>-d|--debug=debuglevel</DT
+><DD
+><P
+><TT
+CLASS="REPLACEABLE"
+><I
+>debuglevel</I
+></TT
+> is an integer
from 0 to 10. The default value if this parameter is
-not specified is zero.</p><p>The higher this value, the more detail will be
+not specified is zero.</P
+><P
+>The higher this value, the more detail will be
logged to the log files about the activities of the
server. At level 0, only critical errors and serious
warnings will be logged. Level 1 is a reasonable level for
day to day running - it generates a small amount of
-information about operations carried out.</p><p>Levels above 1 will generate considerable
+information about operations carried out.</P
+><P
+>Levels above 1 will generate considerable
amounts of log data, and should only be used when
investigating a problem. Levels above 3 are designed for
use only by developers and generate HUGE amounts of log
-data, most of which is extremely cryptic.</p><p>Note that specifying this parameter here will
-override the <a href="smb.conf.5.html#loglevel" target="_top">log
-level</a> parameter in the <a href="smb.conf.5.html" target="_top">
-<tt>smb.conf(5)</tt></a> file.</p></dd><dt><span class="term">-l|--logfile=logbasename</span></dt><dd><p>File name for log/debug files. The extension
-<tt>&quot;.client&quot;</tt> will be appended. The log file is
-never removed by the client.
-</p></dd></dl></div></div><div class="refsect1" lang="en"><h2>COMMANDS</h2><p><span class="emphasis"><em>VFS COMMANDS</em></span></p><div class="itemizedlist"><ul type="disc"><li><p><b>load &lt;module.so&gt;</b> - Load specified VFS module </p></li><li><p><b>populate &lt;char&gt; &lt;size&gt;</b> - Populate a data buffer with the specified data
- </p></li><li><p><b>showdata [&lt;offset&gt; &lt;len&gt;]</b> - Show data currently in data buffer
- </p></li><li><p><b>connect</b> - VFS connect()</p></li><li><p><b>disconnect</b> - VFS disconnect()</p></li><li><p><b>disk_free</b> - VFS disk_free()</p></li><li><p><b>opendir</b> - VFS opendir()</p></li><li><p><b>readdir</b> - VFS readdir()</p></li><li><p><b>mkdir</b> - VFS mkdir()</p></li><li><p><b>rmdir</b> - VFS rmdir()</p></li><li><p><b>closedir</b> - VFS closedir()</p></li><li><p><b>open</b> - VFS open()</p></li><li><p><b>close</b> - VFS close()</p></li><li><p><b>read</b> - VFS read()</p></li><li><p><b>write</b> - VFS write()</p></li><li><p><b>lseek</b> - VFS lseek()</p></li><li><p><b>rename</b> - VFS rename()</p></li><li><p><b>fsync</b> - VFS fsync()</p></li><li><p><b>stat</b> - VFS stat()</p></li><li><p><b>fstat</b> - VFS fstat()</p></li><li><p><b>lstat</b> - VFS lstat()</p></li><li><p><b>unlink</b> - VFS unlink()</p></li><li><p><b>chmod</b> - VFS chmod()</p></li><li><p><b>fchmod</b> - VFS fchmod()</p></li><li><p><b>chown</b> - VFS chown()</p></li><li><p><b>fchown</b> - VFS fchown()</p></li><li><p><b>chdir</b> - VFS chdir()</p></li><li><p><b>getwd</b> - VFS getwd()</p></li><li><p><b>utime</b> - VFS utime()</p></li><li><p><b>ftruncate</b> - VFS ftruncate()</p></li><li><p><b>lock</b> - VFS lock()</p></li><li><p><b>symlink</b> - VFS symlink()</p></li><li><p><b>readlink</b> - VFS readlink()</p></li><li><p><b>link</b> - VFS link()</p></li><li><p><b>mknod</b> - VFS mknod()</p></li><li><p><b>realpath</b> - VFS realpath()</p></li></ul></div><p><span class="emphasis"><em>GENERAL COMMANDS</em></span></p><div class="itemizedlist"><ul type="disc"><li><p><b>conf &lt;smb.conf&gt;</b> - Load a different configuration file</p></li><li><p><b>help [&lt;command&gt;]</b> - Get list of commands or info about specified command</p></li><li><p><b>debuglevel &lt;level&gt;</b> - Set debug level</p></li><li><p><b>freemem</b> - Free memory currently in use</p></li><li><p><b>exit</b> - Exit vfstest</p></li></ul></div></div><div class="refsect1" lang="en"><h2>VERSION</h2><p>This man page is correct for version 3.0 of the Samba
- suite.</p></div><div class="refsect1" lang="en"><h2>AUTHOR</h2><p>The original Samba software and related utilities
+data, most of which is extremely cryptic.</P
+><P
+>Note that specifying this parameter here will
+override the <A
+HREF="smb.conf.5.html#loglevel"
+TARGET="_top"
+>log
+level</A
+> parameter in the <A
+HREF="smb.conf.5.html"
+TARGET="_top"
+><TT
+CLASS="FILENAME"
+>smb.conf(5)</TT
+></A
+> file.</P
+></DD
+><DT
+>-h|--help</DT
+><DD
+><P
+>Print a summary of command line options.</P
+></DD
+><DT
+>-l|--logfile=logbasename</DT
+><DD
+><P
+>File name for log/debug files. The extension
+ <TT
+CLASS="CONSTANT"
+>'.client'</TT
+> will be appended. The log file is never removed
+ by the client.
+ </P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN48"
+></A
+><H2
+>COMMANDS</H2
+><P
+><I
+CLASS="EMPHASIS"
+>VFS COMMANDS</I
+></P
+><P
+></P
+><UL
+><LI
+><P
+><B
+CLASS="COMMAND"
+>load &#60;module.so&#62;</B
+> - Load specified VFS module </P
+></LI
+><LI
+><P
+><B
+CLASS="COMMAND"
+>populate &#60;char&#62; &#60;size&#62;</B
+> - Populate a data buffer with the specified data
+ </P
+></LI
+><LI
+><P
+><B
+CLASS="COMMAND"
+>showdata [&#60;offset&#62; &#60;len&#62;]</B
+> - Show data currently in data buffer
+ </P
+></LI
+><LI
+><P
+><B
+CLASS="COMMAND"
+>connect</B
+> - VFS connect()</P
+></LI
+><LI
+><P
+><B
+CLASS="COMMAND"
+>disconnect</B
+> - VFS disconnect()</P
+></LI
+><LI
+><P
+><B
+CLASS="COMMAND"
+>disk_free</B
+> - VFS disk_free()</P
+></LI
+><LI
+><P
+><B
+CLASS="COMMAND"
+>opendir</B
+> - VFS opendir()</P
+></LI
+><LI
+><P
+><B
+CLASS="COMMAND"
+>readdir</B
+> - VFS readdir()</P
+></LI
+><LI
+><P
+><B
+CLASS="COMMAND"
+>mkdir</B
+> - VFS mkdir()</P
+></LI
+><LI
+><P
+><B
+CLASS="COMMAND"
+>rmdir</B
+> - VFS rmdir()</P
+></LI
+><LI
+><P
+><B
+CLASS="COMMAND"
+>closedir</B
+> - VFS closedir()</P
+></LI
+><LI
+><P
+><B
+CLASS="COMMAND"
+>open</B
+> - VFS open()</P
+></LI
+><LI
+><P
+><B
+CLASS="COMMAND"
+>close</B
+> - VFS close()</P
+></LI
+><LI
+><P
+><B
+CLASS="COMMAND"
+>read</B
+> - VFS read()</P
+></LI
+><LI
+><P
+><B
+CLASS="COMMAND"
+>write</B
+> - VFS write()</P
+></LI
+><LI
+><P
+><B
+CLASS="COMMAND"
+>lseek</B
+> - VFS lseek()</P
+></LI
+><LI
+><P
+><B
+CLASS="COMMAND"
+>rename</B
+> - VFS rename()</P
+></LI
+><LI
+><P
+><B
+CLASS="COMMAND"
+>fsync</B
+> - VFS fsync()</P
+></LI
+><LI
+><P
+><B
+CLASS="COMMAND"
+>stat</B
+> - VFS stat()</P
+></LI
+><LI
+><P
+><B
+CLASS="COMMAND"
+>fstat</B
+> - VFS fstat()</P
+></LI
+><LI
+><P
+><B
+CLASS="COMMAND"
+>lstat</B
+> - VFS lstat()</P
+></LI
+><LI
+><P
+><B
+CLASS="COMMAND"
+>unlink</B
+> - VFS unlink()</P
+></LI
+><LI
+><P
+><B
+CLASS="COMMAND"
+>chmod</B
+> - VFS chmod()</P
+></LI
+><LI
+><P
+><B
+CLASS="COMMAND"
+>fchmod</B
+> - VFS fchmod()</P
+></LI
+><LI
+><P
+><B
+CLASS="COMMAND"
+>chown</B
+> - VFS chown()</P
+></LI
+><LI
+><P
+><B
+CLASS="COMMAND"
+>fchown</B
+> - VFS fchown()</P
+></LI
+><LI
+><P
+><B
+CLASS="COMMAND"
+>chdir</B
+> - VFS chdir()</P
+></LI
+><LI
+><P
+><B
+CLASS="COMMAND"
+>getwd</B
+> - VFS getwd()</P
+></LI
+><LI
+><P
+><B
+CLASS="COMMAND"
+>utime</B
+> - VFS utime()</P
+></LI
+><LI
+><P
+><B
+CLASS="COMMAND"
+>ftruncate</B
+> - VFS ftruncate()</P
+></LI
+><LI
+><P
+><B
+CLASS="COMMAND"
+>lock</B
+> - VFS lock()</P
+></LI
+><LI
+><P
+><B
+CLASS="COMMAND"
+>symlink</B
+> - VFS symlink()</P
+></LI
+><LI
+><P
+><B
+CLASS="COMMAND"
+>readlink</B
+> - VFS readlink()</P
+></LI
+><LI
+><P
+><B
+CLASS="COMMAND"
+>link</B
+> - VFS link()</P
+></LI
+><LI
+><P
+><B
+CLASS="COMMAND"
+>mknod</B
+> - VFS mknod()</P
+></LI
+><LI
+><P
+><B
+CLASS="COMMAND"
+>realpath</B
+> - VFS realpath()</P
+></LI
+></UL
+><P
+><I
+CLASS="EMPHASIS"
+>GENERAL COMMANDS</I
+></P
+><P
+></P
+><UL
+><LI
+><P
+><B
+CLASS="COMMAND"
+>conf &#60;smb.conf&#62;</B
+> - Load a different configuration file</P
+></LI
+><LI
+><P
+><B
+CLASS="COMMAND"
+>help [&#60;command&#62;]</B
+> - Get list of commands or info about specified command</P
+></LI
+><LI
+><P
+><B
+CLASS="COMMAND"
+>debuglevel &#60;level&#62;</B
+> - Set debug level</P
+></LI
+><LI
+><P
+><B
+CLASS="COMMAND"
+>freemem</B
+> - Free memory currently in use</P
+></LI
+><LI
+><P
+><B
+CLASS="COMMAND"
+>exit</B
+> - Exit vfstest</P
+></LI
+></UL
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN179"
+></A
+><H2
+>VERSION</H2
+><P
+>This man page is correct for version 3.0 of the Samba
+ suite.</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN182"
+></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 vfstest man page was written by Jelmer Vernooij.</p></div></div></body></html>
+ to the way the Linux kernel is developed.</P
+><P
+>The vfstest man page was written by Jelmer Vernooij.</P
+></DIV
+></BODY
+></HTML
+> \ No newline at end of file
diff --git a/docs/htmldocs/wbinfo.1.html b/docs/htmldocs/wbinfo.1.html
index fc72b333a8..a8aa065eed 100644
--- a/docs/htmldocs/wbinfo.1.html
+++ b/docs/htmldocs/wbinfo.1.html
@@ -1,71 +1,383 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>wbinfo</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="wbinfo.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>wbinfo &#8212; Query information from winbind daemon</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><tt>wbinfo</tt> [-u] [-g] [-N netbios-name] [-I ip] [-n name] [-s sid] [-U uid] [-G gid] [-S sid] [-Y sid] [-t] [-m] [--sequence] [-r user] [-a user%password] [-A user%password] [--get-auth-user] [-p]</p></div></div><div class="refsect1" lang="en"><h2>DESCRIPTION</h2><p>This tool is part of the <a href="Samba.7.html">Samba(7)</a> suite.</p><p>The <b>wbinfo</b> program queries and returns information
- created and used by the <a href="winbindd.8.html">winbindd(8)</a> daemon. </p><p>The <a href="winbindd.8.html">winbindd(8)</a> daemon must be configured
- and running for the <b>wbinfo</b> program to be able
- to return information.</p></div><div class="refsect1" lang="en"><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-u</span></dt><dd><p>This option will list all users available
- in the Windows NT domain for which the <a href="winbindd.8.html">winbindd(8)</a> daemon is operating in. Users in all trusted domains
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<HTML
+><HEAD
+><TITLE
+>wbinfo</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.77"></HEAD
+><BODY
+CLASS="REFENTRY"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><H1
+><A
+NAME="WBINFO"
+></A
+>wbinfo</H1
+><DIV
+CLASS="REFNAMEDIV"
+><A
+NAME="AEN5"
+></A
+><H2
+>Name</H2
+>wbinfo&nbsp;--&nbsp;Query information from winbind daemon</DIV
+><DIV
+CLASS="REFSYNOPSISDIV"
+><A
+NAME="AEN8"
+></A
+><H2
+>Synopsis</H2
+><P
+><B
+CLASS="COMMAND"
+>wbinfo</B
+> [-u] [-g] [-i ip] [-N netbios-name] [-n name] [-s sid] [-U uid] [-G gid] [-S sid] [-Y sid] [-t] [-m] [-r user] [-a user%password] [-A user%password] [-p]</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN27"
+></A
+><H2
+>DESCRIPTION</H2
+><P
+>This tool is part of the <A
+HREF="samba.7.html"
+TARGET="_top"
+> Samba</A
+> suite.</P
+><P
+>The <B
+CLASS="COMMAND"
+>wbinfo</B
+> program queries and returns information
+ created and used by the <A
+HREF="winbindd.8.html"
+TARGET="_top"
+><B
+CLASS="COMMAND"
+> winbindd(8)</B
+></A
+> daemon. </P
+><P
+>The <B
+CLASS="COMMAND"
+>winbindd(8)</B
+> daemon must be configured
+ and running for the <B
+CLASS="COMMAND"
+>wbinfo</B
+> program to be able
+ to return information.</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN38"
+></A
+><H2
+>OPTIONS</H2
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>-u</DT
+><DD
+><P
+>This option will list all users available
+ in the Windows NT domain for which the <B
+CLASS="COMMAND"
+>winbindd(8)
+ </B
+> daemon is operating in. Users in all trusted domains
will also be listed. Note that this operation does not assign
- user ids to any users that have not already been seen by <a href="winbindd.8.html">winbindd(8)</a>
- .</p></dd><dt><span class="term">-g</span></dt><dd><p>This option will list all groups available
- in the Windows NT domain for which the <a href="Samba.7.html">Samba(7)</a> daemon is operating in. Groups in all trusted domains
+ user ids to any users that have not already been seen by
+ <B
+CLASS="COMMAND"
+>winbindd(8)</B
+>.</P
+></DD
+><DT
+>-g</DT
+><DD
+><P
+>This option will list all groups available
+ in the Windows NT domain for which the <B
+CLASS="COMMAND"
+>winbindd(8)
+ </B
+> daemon is operating in. Groups in all trusted domains
will also be listed. Note that this operation does not assign
- group ids to any groups that have not already been
- seen by <a href="winbindd.8.html">winbindd(8)</a>. </p></dd><dt><span class="term">-N name</span></dt><dd><p>The <i><tt>-N</tt></i> option
- queries <a href="winbindd.8.html">winbindd(8)</a> to query the WINS
+ group ids to any groups that have not already been seen by
+ <B
+CLASS="COMMAND"
+>winbindd(8)</B
+>. </P
+></DD
+><DT
+>-N name</DT
+><DD
+><P
+>The <TT
+CLASS="PARAMETER"
+><I
+>-N</I
+></TT
+> option
+ queries <B
+CLASS="COMMAND"
+>winbindd(8)</B
+> to query the WINS
server for the IP address associated with the NetBIOS name
- specified by the <i><tt>name</tt></i> parameter.
- </p></dd><dt><span class="term">-I ip</span></dt><dd><p>The <i><tt>-I</tt></i> option
- queries <a href="winbindd.8.html">winbindd(8)</a> to send a node status
+ specified by the <TT
+CLASS="PARAMETER"
+><I
+>name</I
+></TT
+> parameter.
+ </P
+></DD
+><DT
+>-I ip</DT
+><DD
+><P
+>The <TT
+CLASS="PARAMETER"
+><I
+>-I</I
+></TT
+> option
+ queries <B
+CLASS="COMMAND"
+>winbindd(8)</B
+> to send a node status
request to get the NetBIOS name associated with the IP address
- specified by the <i><tt>ip</tt></i> parameter.
- </p></dd><dt><span class="term">-n name</span></dt><dd><p>The <i><tt>-n</tt></i> option
- queries <a href="winbindd.8.html">winbindd(8)</a> for the SID
+ specified by the <TT
+CLASS="PARAMETER"
+><I
+>ip</I
+></TT
+> parameter.
+ </P
+></DD
+><DT
+>-n name</DT
+><DD
+><P
+>The <TT
+CLASS="PARAMETER"
+><I
+>-n</I
+></TT
+> option
+ queries <B
+CLASS="COMMAND"
+>winbindd(8)</B
+> for the SID
associated with the name specified. Domain names can be specified
before the user name by using the winbind separator character.
For example CWDOM1/Administrator refers to the Administrator
user in the domain CWDOM1. If no domain is specified then the
- domain used is the one specified in the <a href="smb.conf.5.html">smb.conf(5)</a> <i><tt>workgroup
- </tt></i> parameter. </p></dd><dt><span class="term">-s sid</span></dt><dd><p>Use <i><tt>-s</tt></i> to resolve
- a SID to a name. This is the inverse of the <i><tt>-n
- </tt></i> option above. SIDs must be specified as ASCII strings
+ domain used is the one specified in the <TT
+CLASS="FILENAME"
+>smb.conf</TT
+>
+ <TT
+CLASS="PARAMETER"
+><I
+>workgroup</I
+></TT
+> parameter. </P
+></DD
+><DT
+>-s sid</DT
+><DD
+><P
+>Use <TT
+CLASS="PARAMETER"
+><I
+>-s</I
+></TT
+> to resolve
+ a SID to a name. This is the inverse of the <TT
+CLASS="PARAMETER"
+><I
+>-n
+ </I
+></TT
+> option above. SIDs must be specified as ASCII strings
in the traditional Microsoft format. For example,
- S-1-5-21-1455342024-3071081365-2475485837-500. </p></dd><dt><span class="term">-U uid</span></dt><dd><p>Try to convert a UNIX user id to a Windows NT
+ S-1-5-21-1455342024-3071081365-2475485837-500. </P
+></DD
+><DT
+>-U uid</DT
+><DD
+><P
+>Try to convert a UNIX user id to a Windows NT
SID. If the uid specified does not refer to one within
- the winbind uid range then the operation will fail. </p></dd><dt><span class="term">-G gid</span></dt><dd><p>Try to convert a UNIX group id to a Windows
+ the winbind uid range then the operation will fail. </P
+></DD
+><DT
+>-G gid</DT
+><DD
+><P
+>Try to convert a UNIX group id to a Windows
NT SID. If the gid specified does not refer to one within
- the winbind gid range then the operation will fail. </p></dd><dt><span class="term">-S sid</span></dt><dd><p>Convert a SID to a UNIX user id. If the SID
- does not correspond to a UNIX user mapped by <a href="winbindd.8.html">winbindd(8)</a> then the operation will fail. </p></dd><dt><span class="term">-Y sid</span></dt><dd><p>Convert a SID to a UNIX group id. If the SID
- does not correspond to a UNIX group mapped by <a href="winbindd.8.html">winbindd(8)</a> then
- the operation will fail. </p></dd><dt><span class="term">-t</span></dt><dd><p>Verify that the workstation trust account
+ the winbind gid range then the operation will fail. </P
+></DD
+><DT
+>-S sid</DT
+><DD
+><P
+>Convert a SID to a UNIX user id. If the SID
+ does not correspond to a UNIX user mapped by <B
+CLASS="COMMAND"
+> winbindd(8)</B
+> then the operation will fail. </P
+></DD
+><DT
+>-Y sid</DT
+><DD
+><P
+>Convert a SID to a UNIX group id. If the SID
+ does not correspond to a UNIX group mapped by <B
+CLASS="COMMAND"
+> winbindd(8)</B
+> then the operation will fail. </P
+></DD
+><DT
+>-t</DT
+><DD
+><P
+>Verify that the workstation trust account
created when the Samba server is added to the Windows NT
- domain is working. </p></dd><dt><span class="term">-m</span></dt><dd><p>Produce a list of domains trusted by the
- Windows NT server <a href="winbindd.8.html">winbindd(8)</a> contacts
+ domain is working. </P
+></DD
+><DT
+>-m</DT
+><DD
+><P
+>Produce a list of domains trusted by the
+ Windows NT server <B
+CLASS="COMMAND"
+>winbindd(8)</B
+> contacts
when resolving names. This list does not include the Windows
NT domain the server is a Primary Domain Controller for.
- </p></dd><dt><span class="term">--sequence</span></dt><dd><p>Show sequence numbers of
- all known domains</p></dd><dt><span class="term">-r username</span></dt><dd><p>Try to obtain the list of UNIX group ids
+ </P
+></DD
+><DT
+>-r username</DT
+><DD
+><P
+>Try to obtain the list of UNIX group ids
to which the user belongs. This only works for users
defined on a Domain Controller.
- </p></dd><dt><span class="term">-a username%password</span></dt><dd><p>Attempt to authenticate a user via winbindd.
+ </P
+></DD
+><DT
+>-a username%password</DT
+><DD
+><P
+>Attempt to authenticate a user via winbindd.
This checks both authenticaion methods and reports its results.
- </p></dd><dt><span class="term">-A username%password</span></dt><dd><p>Store username and password used by winbindd
+ </P
+></DD
+><DT
+>-A username%password</DT
+><DD
+><P
+>Store username and password used by winbindd
during session setup to a domain controller. This enables
winbindd to operate in a Windows 2000 domain with Restrict
Anonymous turned on (a.k.a. Permissions compatiable with
Windows 2000 servers only).
- </p></dd><dt><span class="term">--get-auth-user</span></dt><dd><p>Print username and password used by winbindd
- during session setup to a domain controller. Username
- and password can be set using '-A'. Only available for
- root.</p></dd><dt><span class="term">-p</span></dt><dd><p>Check whether winbindd is still alive.
- Prints out either 'succeeded' or 'failed'.
- </p></dd><dt><span class="term">-V</span></dt><dd><p>Prints the version number for
-<b>smbd</b>.</p></dd><dt><span class="term">-h|--help</span></dt><dd><p>Print a summary of command line options.
-</p></dd></dl></div></div><div class="refsect1" lang="en"><h2>EXIT STATUS</h2><p>The wbinfo program returns 0 if the operation
- succeeded, or 1 if the operation failed. If the <a href="winbindd.8.html">winbindd(8)</a> daemon is not working <b>wbinfo</b> will always return
- failure. </p></div><div class="refsect1" lang="en"><h2>VERSION</h2><p>This man page is correct for version 3.0 of
- the Samba suite.</p></div><div class="refsect1" lang="en"><h2>SEE ALSO</h2><p><a href="winbindd.8.html">winbindd(8)</a></p></div><div class="refsect1" lang="en"><h2>AUTHOR</h2><p>The original Samba software and related utilities
+ </P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN120"
+></A
+><H2
+>EXIT STATUS</H2
+><P
+>The wbinfo program returns 0 if the operation
+ succeeded, or 1 if the operation failed. If the <B
+CLASS="COMMAND"
+>winbindd(8)
+ </B
+> daemon is not working <B
+CLASS="COMMAND"
+>wbinfo</B
+> will always return
+ failure. </P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN125"
+></A
+><H2
+>VERSION</H2
+><P
+>This man page is correct for version 3.0 of
+ the Samba suite.</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN128"
+></A
+><H2
+>SEE ALSO</H2
+><P
+><A
+HREF="winbindd.8.html"
+TARGET="_top"
+><B
+CLASS="COMMAND"
+>winbindd(8)</B
+>
+ </A
+></P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN133"
+></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><b>wbinfo</b> and <b>winbindd</b>
- were written by Tim Potter.</p><p>The conversion to DocBook for Samba 2.2 was done
- by Gerald Carter. The conversion to DocBook XML 4.2 for Samba
- 3.0 was done by Alexander Bokovoy.</p></div></div></body></html>
+ to the way the Linux kernel is developed.</P
+><P
+><B
+CLASS="COMMAND"
+>wbinfo</B
+> and <B
+CLASS="COMMAND"
+>winbindd</B
+>
+ were written by Tim Potter.</P
+><P
+>The conversion to DocBook for Samba 2.2 was done
+ by Gerald Carter</P
+></DIV
+></BODY
+></HTML
+> \ No newline at end of file
diff --git a/docs/htmldocs/winbind.html b/docs/htmldocs/winbind.html
index 3672fa0717..1558512a61 100644
--- a/docs/htmldocs/winbind.html
+++ b/docs/htmldocs/winbind.html
@@ -1,75 +1,244 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter15.Unified Logons between Windows NT and UNIX using Winbind</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"><link rel="home" href="index.html" title="SAMBA Project Documentation"><link rel="up" href="optional.html" title="PartIII.Advanced Configuration"><link rel="previous" href="CUPS-printing.html" title="Chapter14.CUPS Printing Support"><link rel="next" href="AdvancedNetworkManagement.html" title="Chapter16.Advanced Network Manangement"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter15.Unified Logons between Windows NT and UNIX using Winbind</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="CUPS-printing.html">Prev</a></td><th width="60%" align="center">PartIII.Advanced Configuration</th><td width="20%" align="right"><a accesskey="n" href="AdvancedNetworkManagement.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="winbind"></a>Chapter15.Unified Logons between Windows NT and UNIX using Winbind</h2></div><div><div class="authorgroup"><div class="author"><h3 class="author">Tim Potter</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt>&lt;<a href="mailto:tpot@linuxcare.com.au">tpot@linuxcare.com.au</a>&gt;</tt></p></div></div></div><div class="author"><h3 class="author">Andrew Tridgell</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt>&lt;<a href="mailto:tridge@samba.org">tridge@samba.org</a>&gt;</tt></p></div></div></div><div class="author"><h3 class="author">John H. Terpstra</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt>&lt;<a href="mailto:jht@samba.org">jht@samba.org</a>&gt;</tt></p></div></div></div><div class="author"><h3 class="author">Naag Mummaneni</h3><div class="affiliation"><div class="address"><p><tt>&lt;<a href="mailto:getnag@rediffmail.com">getnag@rediffmail.com</a>&gt;</tt></p></div></div></div><div class="author"><h3 class="author">Jelmer R. Vernooij</h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt>&lt;<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>&gt;</tt></p></div></div></div></div></div><div><p class="pubdate">27 June 2002</p></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="winbind.html#id2891610">Abstract</a></dt><dt><a href="winbind.html#id2891639">Introduction</a></dt><dt><a href="winbind.html#id2891710">What Winbind Provides</a></dt><dd><dl><dt><a href="winbind.html#id2888972">Target Uses</a></dt></dl></dd><dt><a href="winbind.html#id2889003">How Winbind Works</a></dt><dd><dl><dt><a href="winbind.html#id2889031">Microsoft Remote Procedure Calls</a></dt><dt><a href="winbind.html#id2889066">Microsoft Active Directory Services</a></dt><dt><a href="winbind.html#id2889088">Name Service Switch</a></dt><dt><a href="winbind.html#id2892176">Pluggable Authentication Modules</a></dt><dt><a href="winbind.html#id2892248">User and Group ID Allocation</a></dt><dt><a href="winbind.html#id2892282">Result Caching</a></dt></dl></dd><dt><a href="winbind.html#id2892310">Installation and Configuration</a></dt><dd><dl><dt><a href="winbind.html#id2892338">Introduction</a></dt><dt><a href="winbind.html#id2892413">Requirements</a></dt><dt><a href="winbind.html#id2892507">Testing Things Out</a></dt></dl></dd><dt><a href="winbind.html#id2894106">Limitations</a></dt><dt><a href="winbind.html#id2894160">Conclusion</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2891610"></a>Abstract</h2></div></div><p>Integration of UNIX and Microsoft Windows NT through
- a unified logon has been considered a &quot;holy grail&quot; in heterogeneous
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<HTML
+><HEAD
+><TITLE
+>Unified Logons between Windows NT and UNIX using Winbind</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
+REL="HOME"
+TITLE="SAMBA Project Documentation"
+HREF="samba-howto-collection.html"><LINK
+REL="UP"
+TITLE="Optional configuration"
+HREF="optional.html"><LINK
+REL="PREVIOUS"
+TITLE="Printing Support"
+HREF="printing.html"><LINK
+REL="NEXT"
+TITLE="Passdb MySQL plugin"
+HREF="pdb-mysql.html"></HEAD
+><BODY
+CLASS="CHAPTER"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><TABLE
+SUMMARY="Header navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>SAMBA Project Documentation</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="printing.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+></TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="pdb-mysql.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="CHAPTER"
+><H1
+><A
+NAME="WINBIND">Chapter 15. Unified Logons between Windows NT and UNIX using Winbind</H1
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN2225">15.1. Abstract</H1
+><P
+>Integration of UNIX and Microsoft Windows NT through
+ a unified logon has been considered a "holy grail" in heterogeneous
computing environments for a long time. We present
- <span class="emphasis"><em>winbind</em></span>, a component of the Samba suite
+ <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>winbind</I
+></SPAN
+>, a component of the Samba suite
of programs as a solution to the unified logon problem. Winbind
uses a UNIX implementation
of Microsoft RPC calls, Pluggable Authentication Modules, and the Name
Service Switch to allow Windows NT domain users to appear and operate
as UNIX users on a UNIX machine. This paper describes the winbind
system, explaining the functionality it provides, how it is configured,
- and how it works internally.</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2891639"></a>Introduction</h2></div></div><p>It is well known that UNIX and Microsoft Windows NT have
+ and how it works internally.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN2229">15.2. Introduction</H1
+><P
+>It is well known that UNIX and Microsoft Windows NT have
different models for representing user and group information and
use different technologies for implementing them. This fact has
made it difficult to integrate the two systems in a satisfactory
- manner.</p><p>One common solution in use today has been to create
+ manner.</P
+><P
+>One common solution in use today has been to create
identically named user accounts on both the UNIX and Windows systems
and use the Samba suite of programs to provide file and print services
between the two. This solution is far from perfect however, as
adding and deleting users on both sets of machines becomes a chore
and two sets of passwords are required both of which
can lead to synchronization problems between the UNIX and Windows
- systems and confusion for users.</p><p>We divide the unified logon problem for UNIX machines into
- three smaller problems:</p><div class="itemizedlist"><ul type="disc"><li><p>Obtaining Windows NT user and group information
- </p></li><li><p>Authenticating Windows NT users
- </p></li><li><p>Password changing for Windows NT users
- </p></li></ul></div><p>Ideally, a prospective solution to the unified logon problem
+ systems and confusion for users.</P
+><P
+>We divide the unified logon problem for UNIX machines into
+ three smaller problems:</P
+><P
+></P
+><UL
+><LI
+><P
+>Obtaining Windows NT user and group information
+ </P
+></LI
+><LI
+><P
+>Authenticating Windows NT users
+ </P
+></LI
+><LI
+><P
+>Password changing for Windows NT users
+ </P
+></LI
+></UL
+><P
+>Ideally, a prospective solution to the unified logon problem
would satisfy all the above components without duplication of
information on the UNIX machines and without creating additional
tasks for the system administrator when maintaining users and
groups on either system. The winbind system provides a simple
and elegant solution to all three components of the unified logon
- problem.</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2891710"></a>What Winbind Provides</h2></div></div><p>Winbind unifies UNIX and Windows NT account management by
+ problem.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN2242">15.3. What Winbind Provides</H1
+><P
+>Winbind unifies UNIX and Windows NT account management by
allowing a UNIX box to become a full member of a NT domain. Once
this is done the UNIX box will see NT users and groups as if
they were native UNIX users and groups, allowing the NT domain
to be used in much the same manner that NIS+ is used within
- UNIX-only environments.</p><p>The end result is that whenever any
+ UNIX-only environments.</P
+><P
+>The end result is that whenever any
program on the UNIX machine asks the operating system to lookup
a user or group name, the query will be resolved by asking the
NT domain controller for the specified domain to do the lookup.
Because Winbind hooks into the operating system at a low level
(via the NSS name resolution modules in the C library) this
redirection to the NT domain controller is completely
- transparent.</p><p>Users on the UNIX machine can then use NT user and group
- names as they would use &quot;native&quot; UNIX names. They can chown files
+ transparent.</P
+><P
+>Users on the UNIX machine can then use NT user and group
+ names as they would use "native" UNIX names. They can chown files
so that they are owned by NT domain users or even login to the
- UNIX machine and run a UNIX X-Window session as a domain user.</p><p>The only obvious indication that Winbind is being used is
+ UNIX machine and run a UNIX X-Window session as a domain user.</P
+><P
+>The only obvious indication that Winbind is being used is
that user and group names take the form DOMAIN\user and
DOMAIN\group. This is necessary as it allows Winbind to determine
that redirection to a domain controller is wanted for a particular
- lookup and which trusted domain is being referenced.</p><p>Additionally, Winbind provides an authentication service
+ lookup and which trusted domain is being referenced.</P
+><P
+>Additionally, Winbind provides an authentication service
that hooks into the Pluggable Authentication Modules (PAM) system
to provide authentication via a NT domain to any PAM enabled
applications. This capability solves the problem of synchronizing
passwords between systems since all passwords are stored in a single
- location (on the domain controller).</p><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2888972"></a>Target Uses</h3></div></div><p>Winbind is targeted at organizations that have an
+ location (on the domain controller).</P
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN2249">15.3.1. Target Uses</H2
+><P
+>Winbind is targeted at organizations that have an
existing NT based domain infrastructure into which they wish
to put UNIX workstations or servers. Winbind will allow these
organizations to deploy UNIX workstations without having to
maintain a separate account infrastructure. This greatly
simplifies the administrative overhead of deploying UNIX
- workstations into a NT based organization.</p><p>Another interesting way in which we expect Winbind to
+ workstations into a NT based organization.</P
+><P
+>Another interesting way in which we expect Winbind to
be used is as a central part of UNIX based appliances. Appliances
that provide file and print services to Microsoft based networks
will be able to use Winbind to provide seamless integration of
- the appliance into the domain.</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2889003"></a>How Winbind Works</h2></div></div><p>The winbind system is designed around a client/server
- architecture. A long running <b>winbindd</b> daemon
+ the appliance into the domain.</P
+></DIV
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN2253">15.4. How Winbind Works</H1
+><P
+>The winbind system is designed around a client/server
+ architecture. A long running <B
+CLASS="COMMAND"
+>winbindd</B
+> daemon
listens on a UNIX domain socket waiting for requests
to arrive. These requests are generated by the NSS and PAM
- clients and processed sequentially.</p><p>The technologies used to implement winbind are described
- in detail below.</p><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2889031"></a>Microsoft Remote Procedure Calls</h3></div></div><p>Over the last few years, efforts have been underway
+ clients and processed sequentially.</P
+><P
+>The technologies used to implement winbind are described
+ in detail below.</P
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN2258">15.4.1. Microsoft Remote Procedure Calls</H2
+><P
+>Over the last two years, efforts have been underway
by various Samba Team members to decode various aspects of
the Microsoft Remote Procedure Call (MSRPC) system. This
system is used for most network related operations between
@@ -77,21 +246,23 @@
and print spooling. Although initially this work was done
to aid the implementation of Primary Domain Controller (PDC)
functionality in Samba, it has also yielded a body of code which
- can be used for other purposes.</p><p>Winbind uses various MSRPC calls to enumerate domain users
+ can be used for other purposes.</P
+><P
+>Winbind uses various MSRPC calls to enumerate domain users
and groups and to obtain detailed information about individual
users or groups. Other MSRPC calls can be used to authenticate
NT domain users and to change user passwords. By directly querying
a Windows PDC for user and group information, winbind maps the
- NT account information onto UNIX user and group names.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2889066"></a>Microsoft Active Directory Services</h3></div></div><p>
- Since late 2001, Samba has gained the ability to
- interact with Microsoft Windows 2000 using its 'Native
- Mode' protocols, rather than the NT4 RPC services.
- Using LDAP and Kerberos, a domain member running
- winbind can enumerate users and groups in exactly the
- same way as a Win2k client would, and in so doing
- provide a much more efficient and
- effective winbind implementation.
- </p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2889088"></a>Name Service Switch</h3></div></div><p>The Name Service Switch, or NSS, is a feature that is
+ NT account information onto UNIX user and group names.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN2262">15.4.2. Name Service Switch</H2
+><P
+>The Name Service Switch, or NSS, is a feature that is
present in many UNIX operating systems. It allows system
information such as hostnames, mail aliases and user information
to be resolved from different sources. For example, a standalone
@@ -99,7 +270,9 @@
flat files stored on the local filesystem. A networked workstation
may first attempt to resolve system information from local files,
and then consult a NIS database for user information or a DNS server
- for hostname information.</p><p>The NSS application programming interface allows winbind
+ for hostname information.</P
+><P
+>The NSS application programming interface allows winbind
to present itself as a source of system information when
resolving UNIX usernames and groups. Winbind uses this interface,
and information obtained from a Windows NT server using MSRPC
@@ -107,26 +280,67 @@
UNIX library calls, one can enumerate the users and groups on
a UNIX machine running winbind and see all users and groups in
a NT domain plus any trusted domain as though they were local
- users and groups.</p><p>The primary control file for NSS is
- <tt>/etc/nsswitch.conf</tt>.
+ users and groups.</P
+><P
+>The primary control file for NSS is
+ <TT
+CLASS="FILENAME"
+>/etc/nsswitch.conf</TT
+>.
When a UNIX application makes a request to do a lookup
- the C library looks in <tt>/etc/nsswitch.conf</tt>
+ the C library looks in <TT
+CLASS="FILENAME"
+>/etc/nsswitch.conf</TT
+>
for a line which matches the service type being requested, for
- example the &quot;passwd&quot; service type is used when user or group names
+ example the "passwd" service type is used when user or group names
are looked up. This config line species which implementations
of that service should be tried and in what order. If the passwd
- config line is:</p><p><b>passwd: files example</b></p><p>then the C library will first load a module called
- <tt>/lib/libnss_files.so</tt> followed by
- the module <tt>/lib/libnss_example.so</tt>. The
+ config line is:</P
+><P
+><B
+CLASS="COMMAND"
+>passwd: files example</B
+></P
+><P
+>then the C library will first load a module called
+ <TT
+CLASS="FILENAME"
+>/lib/libnss_files.so</TT
+> followed by
+ the module <TT
+CLASS="FILENAME"
+>/lib/libnss_example.so</TT
+>. The
C library will dynamically load each of these modules in turn
and call resolver functions within the modules to try to resolve
the request. Once the request is resolved the C library returns the
- result to the application.</p><p>This NSS interface provides a very easy way for Winbind
+ result to the application.</P
+><P
+>This NSS interface provides a very easy way for Winbind
to hook into the operating system. All that needs to be done
- is to put <tt>libnss_winbind.so</tt> in <tt>/lib/</tt>
- then add &quot;winbind&quot; into <tt>/etc/nsswitch.conf</tt> at
+ is to put <TT
+CLASS="FILENAME"
+>libnss_winbind.so</TT
+> in <TT
+CLASS="FILENAME"
+>/lib/</TT
+>
+ then add "winbind" into <TT
+CLASS="FILENAME"
+>/etc/nsswitch.conf</TT
+> at
the appropriate place. The C library will then call Winbind to
- resolve user and group names.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2892176"></a>Pluggable Authentication Modules</h3></div></div><p>Pluggable Authentication Modules, also known as PAM,
+ resolve user and group names.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN2278">15.4.3. Pluggable Authentication Modules</H2
+><P
+>Pluggable Authentication Modules, also known as PAM,
is a system for abstracting authentication and authorization
technologies. With a PAM module it is possible to specify different
authentication methods for different system applications without
@@ -134,24 +348,46 @@
for implementing a particular policy for authorization. For example,
a system administrator may only allow console logins from users
stored in the local password file but only allow users resolved from
- a NIS database to log in over the network.</p><p>Winbind uses the authentication management and password
+ a NIS database to log in over the network.</P
+><P
+>Winbind uses the authentication management and password
management PAM interface to integrate Windows NT users into a
UNIX system. This allows Windows NT users to log in to a UNIX
machine and be authenticated against a suitable Primary Domain
Controller. These users can also change their passwords and have
this change take effect directly on the Primary Domain Controller.
- </p><p>PAM is configured by providing control files in the directory
- <tt>/etc/pam.d/</tt> for each of the services that
+ </P
+><P
+>PAM is configured by providing control files in the directory
+ <TT
+CLASS="FILENAME"
+>/etc/pam.d/</TT
+> for each of the services that
require authentication. When an authentication request is made
by an application the PAM code in the C library looks up this
control file to determine what modules to load to do the
authentication check and in what order. This interface makes adding
a new authentication service for Winbind very easy, all that needs
- to be done is that the <tt>pam_winbind.so</tt> module
- is copied to <tt>/lib/security/</tt> and the PAM
+ to be done is that the <TT
+CLASS="FILENAME"
+>pam_winbind.so</TT
+> module
+ is copied to <TT
+CLASS="FILENAME"
+>/lib/security/</TT
+> and the PAM
control files for relevant services are updated to allow
authentication via winbind. See the PAM documentation
- for more details.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2892248"></a>User and Group ID Allocation</h3></div></div><p>When a user or group is created under Windows NT
+ for more details.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN2286">15.4.4. User and Group ID Allocation</H2
+><P
+>When a user or group is created under Windows NT
is it allocated a numerical relative identifier (RID). This is
slightly different to UNIX which has a range of numbers that are
used to identify users, and the same range in which to identify
@@ -162,9 +398,20 @@
resolved for the first time, it is allocated the next UNIX id from
the range. The same process applies for Windows NT groups. Over
time, winbind will have mapped all Windows NT users and groups
- to UNIX user ids and group ids.</p><p>The results of this mapping are stored persistently in
+ to UNIX user ids and group ids.</P
+><P
+>The results of this mapping are stored persistently in
an ID mapping database held in a tdb database). This ensures that
- RIDs are mapped to UNIX IDs in a consistent way.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2892282"></a>Result Caching</h3></div></div><p>An active system can generate a lot of user and group
+ RIDs are mapped to UNIX IDs in a consistent way.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN2290">15.4.5. Result Caching</H2
+><P
+>An active system can generate a lot of user and group
name lookups. To reduce the network cost of these lookups winbind
uses a caching scheme based on the SAM sequence number supplied
by NT domain controllers. User or group information returned
@@ -175,559 +422,1182 @@
the PDC and compared against the sequence number of the cached entry.
If the sequence numbers do not match, then the cached information
is discarded and up to date information is requested directly
- from the PDC.</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2892310"></a>Installation and Configuration</h2></div></div><p>
-Many thanks to John Trostel <a href="mailto:jtrostel@snapserver.com" target="_top">jtrostel@snapserver.com</a>
-for providing the HOWTO for this section.
-</p><p>
-This HOWTO describes how to get winbind services up and running
+ from the PDC.</P
+></DIV
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN2293">15.5. Installation and Configuration</H1
+><P
+>Many thanks to John Trostel <A
+HREF="mailto:jtrostel@snapserver.com"
+TARGET="_top"
+>jtrostel@snapserver.com</A
+>
+for providing the HOWTO for this section.</P
+><P
+>This HOWTO describes how to get winbind services up and running
to control access and authenticate users on your Linux box using
-the winbind services which come with SAMBA 3.0.
-</p><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2892338"></a>Introduction</h3></div></div><p>
-This HOWTO describes the procedures used to get winbind up and
+the winbind services which come with SAMBA 2.2.2.</P
+><P
+>There is also some Solaris specific information in
+<TT
+CLASS="FILENAME"
+>docs/textdocs/Solaris-Winbind-HOWTO.txt</TT
+>.
+Future revisions of this document will incorporate that
+information.</P
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN2300">15.5.1. Introduction</H2
+><P
+>This HOWTO describes the procedures used to get winbind up and
running on my RedHat 7.1 system. Winbind is capable of providing access
and authentication control for Windows Domain users through an NT
or Win2K PDC for 'regular' services, such as telnet a nd ftp, as
-well for SAMBA services.
-</p><p>
-This HOWTO has been written from a 'RedHat-centric' perspective, so if
+well for SAMBA services.</P
+><P
+>This HOWTO has been written from a 'RedHat-centric' perspective, so if
you are using another distribution, you may have to modify the instructions
-somewhat to fit the way your distribution works.
-</p><div class="itemizedlist"><ul type="disc"><li><p>
- <span class="emphasis"><em>Why should I to this?</em></span>
- </p><p>This allows the SAMBA administrator to rely on the
+somewhat to fit the way your distribution works.</P
+><P
+></P
+><UL
+><LI
+><P
+> <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Why should I to this?</I
+></SPAN
+>
+ </P
+><P
+>This allows the SAMBA administrator to rely on the
authentication mechanisms on the NT/Win2K PDC for the authentication
of domain members. NT/Win2K users no longer need to have separate
accounts on the SAMBA server.
- </p></li><li><p>
- <span class="emphasis"><em>Who should be reading this document?</em></span>
- </p><p>
- This HOWTO is designed for system administrators. If you are
+ </P
+></LI
+><LI
+><P
+> <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>Who should be reading this document?</I
+></SPAN
+>
+ </P
+><P
+> This HOWTO is designed for system administrators. If you are
implementing SAMBA on a file server and wish to (fairly easily)
integrate existing NT/Win2K users from your PDC onto the
SAMBA server, this HOWTO is for you. That said, I am no NT or PAM
expert, so you may find a better or easier way to accomplish
these tasks.
- </p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2892413"></a>Requirements</h3></div></div><p>
-If you have a samba configuration file that you are currently
-using... <span class="emphasis"><em>BACK IT UP!</em></span> If your system already uses PAM,
-<span class="emphasis"><em>back up the <tt>/etc/pam.d</tt> directory
-contents!</em></span> If you haven't already made a boot disk,
-<span class="emphasis"><em>MAKE ONE NOW!</em></span>
-</p><p>
-Messing with the pam configuration files can make it nearly impossible
+ </P
+></LI
+></UL
+></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN2313">15.5.2. Requirements</H2
+><P
+>If you have a samba configuration file that you are currently
+using... <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>BACK IT UP!</I
+></SPAN
+> If your system already uses PAM,
+<SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>back up the <TT
+CLASS="FILENAME"
+>/etc/pam.d</TT
+> directory
+contents!</I
+></SPAN
+> If you haven't already made a boot disk,
+<SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>MAKE ONE NOW!</I
+></SPAN
+></P
+><P
+>Messing with the pam configuration files can make it nearly impossible
to log in to yourmachine. That's why you want to be able to boot back
into your machine in single user mode and restore your
-<tt>/etc/pam.d</tt> back to the original state they were in if
-you get frustrated with the way things are going. ;-)
-</p><p>
-The latest version of SAMBA (version 3.0 as of this writing), now
+<TT
+CLASS="FILENAME"
+>/etc/pam.d</TT
+> back to the original state they were in if
+you get frustrated with the way things are going. ;-)</P
+><P
+>The latest version of SAMBA (version 3.0 as of this writing), now
includes a functioning winbindd daemon. Please refer to the
-<a href="http://samba.org/" target="_top">main SAMBA web page</a> or,
+<A
+HREF="http://samba.org/"
+TARGET="_top"
+>main SAMBA web page</A
+> or,
better yet, your closest SAMBA mirror site for instructions on
-downloading the source code.
-</p><p>
-To allow Domain users the ability to access SAMBA shares and
+downloading the source code.</P
+><P
+>To allow Domain users the ability to access SAMBA shares and
files, as well as potentially other services provided by your
SAMBA machine, PAM (pluggable authentication modules) must
be setup properly on your machine. In order to compile the
winbind modules, you should have at least the pam libraries resident
on your system. For recent RedHat systems (7.1, for instance), that
-means <tt>pam-0.74-22</tt>. For best results, it is helpful to also
-install the development packages in <tt>pam-devel-0.74-22</tt>.
-</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2892507"></a>Testing Things Out</h3></div></div><p>
-Before starting, it is probably best to kill off all the SAMBA
-related daemons running on your server. Kill off all <b>smbd</b>,
-<b>nmbd</b>, and <b>winbindd</b> processes that may
+means <TT
+CLASS="FILENAME"
+>pam-0.74-22</TT
+>. For best results, it is helpful to also
+install the development packages in <TT
+CLASS="FILENAME"
+>pam-devel-0.74-22</TT
+>.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="AEN2327">15.5.3. Testing Things Out</H2
+><P
+>Before starting, it is probably best to kill off all the SAMBA
+related daemons running on your server. Kill off all <B
+CLASS="COMMAND"
+>smbd</B
+>,
+<B
+CLASS="COMMAND"
+>nmbd</B
+>, and <B
+CLASS="COMMAND"
+>winbindd</B
+> processes that may
be running. To use PAM, you will want to make sure that you have the
-standard PAM package (for RedHat) which supplies the <tt>/etc/pam.d</tt>
+standard PAM package (for RedHat) which supplies the <TT
+CLASS="FILENAME"
+>/etc/pam.d</TT
+>
directory structure, including the pam modules are used by pam-aware
-services, several pam libraries, and the <tt>/usr/doc</tt>
-and <tt>/usr/man</tt> entries for pam. Winbind built better
+services, several pam libraries, and the <TT
+CLASS="FILENAME"
+>/usr/doc</TT
+>
+and <TT
+CLASS="FILENAME"
+>/usr/man</TT
+> entries for pam. Winbind built better
in SAMBA if the pam-devel package was also installed. This package includes
the header files needed to compile pam-aware applications. For instance,
-my RedHat system has both <tt>pam-0.74-22</tt> and
-<tt>pam-devel-0.74-22</tt> RPMs installed.
-</p><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2892584"></a>Configure and compile SAMBA</h4></div></div><p>
-The configuration and compilation of SAMBA is pretty straightforward.
+my RedHat system has both <TT
+CLASS="FILENAME"
+>pam-0.74-22</TT
+> and
+<TT
+CLASS="FILENAME"
+>pam-devel-0.74-22</TT
+> RPMs installed.</P
+><DIV
+CLASS="SECT3"
+><H3
+CLASS="SECT3"
+><A
+NAME="AEN2338">15.5.3.1. Configure and compile SAMBA</H3
+><P
+>The configuration and compilation of SAMBA is pretty straightforward.
The first three steps may not be necessary depending upon
-whether or not you have previously built the Samba binaries.
-</p><pre class="programlisting">
-<tt>root#</tt> <b>autoconf</b>
-<tt>root#</tt> <b>make clean</b>
-<tt>root#</tt> <b>rm config.cache</b>
-<tt>root#</tt> <b>./configure</b>
-<tt>root#</tt> <b>make</b>
-<tt>root#</tt> <b>make install</b>
-</pre><p>
-This will, by default, install SAMBA in <tt>/usr/local/samba</tt>.
+whether or not you have previously built the Samba binaries.</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+><TT
+CLASS="PROMPT"
+>root#</TT
+> <B
+CLASS="COMMAND"
+>autoconf</B
+>
+<TT
+CLASS="PROMPT"
+>root#</TT
+> <B
+CLASS="COMMAND"
+>make clean</B
+>
+<TT
+CLASS="PROMPT"
+>root#</TT
+> <B
+CLASS="COMMAND"
+>rm config.cache</B
+>
+<TT
+CLASS="PROMPT"
+>root#</TT
+> <B
+CLASS="COMMAND"
+>./configure --with-winbind</B
+>
+<TT
+CLASS="PROMPT"
+>root#</TT
+> <B
+CLASS="COMMAND"
+>make</B
+>
+<TT
+CLASS="PROMPT"
+>root#</TT
+> <B
+CLASS="COMMAND"
+>make install</B
+></PRE
+></P
+><P
+>This will, by default, install SAMBA in <TT
+CLASS="FILENAME"
+>/usr/local/samba</TT
+>.
See the main SAMBA documentation if you want to install SAMBA somewhere else.
-It will also build the winbindd executable and libraries.
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2892705"></a>Configure <tt>nsswitch.conf</tt> and the
-winbind libraries on Linux and Solaris</h4></div></div><p>
-The libraries needed to run the <b>winbindd</b> daemon
-through nsswitch need to be copied to their proper locations, so
-</p><p>
-<tt>root#</tt> <b>cp ../samba/source/nsswitch/libnss_winbind.so /lib</b>
-</p><p>
-I also found it necessary to make the following symbolic link:
-</p><p>
-<tt>root#</tt> <b>ln -s /lib/libnss_winbind.so /lib/libnss_winbind.so.2</b>
-</p><p>And, in the case of Sun solaris:</p><p>
-<tt>root#</tt> <b><tt>ln -s /usr/lib/libnss_winbind.so /usr/lib/libnss_winbind.so.1</tt></b>
-<tt>root#</tt> <b><tt>ln -s /usr/lib/libnss_winbind.so /usr/lib/nss_winbind.so.1</tt></b>
-<tt>root#</tt> <b><tt>ln -s /usr/lib/libnss_winbind.so /usr/lib/nss_winbind.so.2</tt></b>
-</p><p>
-Now, as root you need to edit <tt>/etc/nsswitch.conf</tt> to
-allow user and group entries to be visible from the <b>winbindd</b>
-daemon. My <tt>/etc/nsswitch.conf</tt> file look like
-this after editing:
-</p><pre class="programlisting">
- passwd: files winbind
+It will also build the winbindd executable and libraries. </P
+></DIV
+><DIV
+CLASS="SECT3"
+><H3
+CLASS="SECT3"
+><A
+NAME="AEN2357">15.5.3.2. Configure <TT
+CLASS="FILENAME"
+>nsswitch.conf</TT
+> and the
+winbind libraries</H3
+><P
+>The libraries needed to run the <B
+CLASS="COMMAND"
+>winbindd</B
+> daemon
+through nsswitch need to be copied to their proper locations, so</P
+><P
+><TT
+CLASS="PROMPT"
+>root#</TT
+> <B
+CLASS="COMMAND"
+>cp ../samba/source/nsswitch/libnss_winbind.so /lib</B
+></P
+><P
+>I also found it necessary to make the following symbolic link:</P
+><P
+><TT
+CLASS="PROMPT"
+>root#</TT
+> <B
+CLASS="COMMAND"
+>ln -s /lib/libnss_winbind.so /lib/libnss_winbind.so.2</B
+></P
+><P
+>And, in the case of Sun solaris:</P
+><P
+><TT
+CLASS="PROMPT"
+>root#</TT
+> <B
+CLASS="COMMAND"
+>ln -s /usr/lib/libnss_winbind.so /usr/lib/libnss_winbind.so.1</B
+>
+<TT
+CLASS="PROMPT"
+>root#</TT
+> <B
+CLASS="COMMAND"
+>ln -s /usr/lib/libnss_winbind.so /usr/lib/nss_winbind.so.1</B
+>
+<TT
+CLASS="PROMPT"
+>root#</TT
+> <B
+CLASS="COMMAND"
+>ln -s /usr/lib/libnss_winbind.so /usr/lib/nss_winbind.so.2</B
+></P
+><P
+>Now, as root you need to edit <TT
+CLASS="FILENAME"
+>/etc/nsswitch.conf</TT
+> to
+allow user and group entries to be visible from the <B
+CLASS="COMMAND"
+>winbindd</B
+>
+daemon. My <TT
+CLASS="FILENAME"
+>/etc/nsswitch.conf</TT
+> file look like
+this after editing:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+> passwd: files winbind
shadow: files
- group: files winbind
-</pre><p>
+ group: files winbind</PRE
+></P
+><P
+>
The libraries needed by the winbind daemon will be automatically
-entered into the <b>ldconfig</b> cache the next time
+entered into the <B
+CLASS="COMMAND"
+>ldconfig</B
+> cache the next time
your system reboots, but it
-is faster (and you don't need to reboot) if you do it manually:
-</p><p>
-<tt>root#</tt> <b>/sbin/ldconfig -v | grep winbind</b>
-</p><p>
-This makes <tt>libnss_winbind</tt> available to winbindd
-and echos back a check to you.
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2892910"></a>NSS Winbind on AIX</h4></div></div><p>(This section is only for those running AIX)</p><p>
-The winbind AIX identification module gets built as libnss_winbind.so in the
-nsswitch directory of the samba source. This file can be copied to
-/usr/lib/security, and the AIX naming convention would indicate that it
-should be named WINBIND. A stanza like the following:
-</p><pre class="programlisting">
-WINBIND:
- program = /usr/lib/security/WINBIND
- options = authonly
-</pre><p>can then be added to
-<tt>/usr/lib/security/methods.cfg</tt>. This module only
-supports identification, but there have been success reports using the
-standard winbind pam module for authentication. Use caution configuring
-loadable authentication modules as it is possible to make it impossible
-to logon to the system. More information about the AIX authentication
-module API can be found at &quot;Kernel Extensions and Device Support
-Programming Concepts for AIX&quot;: <a href="">
-Chapter 18. Loadable Authentication Module Programming Interface</a>
-and more information on administering the modules at <a href="">
-&quot;System Management Guide: Operating System and Devices&quot;</a>.
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2892983"></a>Configure smb.conf</h4></div></div><p>
-Several parameters are needed in the smb.conf file to control
-the behavior of <b>winbindd</b>. Configure
-<tt>smb.conf</tt> These are described in more detail in
-the <a href="winbindd.8.html">winbindd(8)</a> man page. My
-<tt>smb.conf</tt> file was modified to
-include the following entries in the [global] section:
-</p><pre class="programlisting">
-[global]
- &lt;...&gt;
+is faster (and you don't need to reboot) if you do it manually:</P
+><P
+><TT
+CLASS="PROMPT"
+>root#</TT
+> <B
+CLASS="COMMAND"
+>/sbin/ldconfig -v | grep winbind</B
+></P
+><P
+>This makes <TT
+CLASS="FILENAME"
+>libnss_winbind</TT
+> available to winbindd
+and echos back a check to you.</P
+></DIV
+><DIV
+CLASS="SECT3"
+><H3
+CLASS="SECT3"
+><A
+NAME="AEN2390">15.5.3.3. Configure smb.conf</H3
+><P
+>Several parameters are needed in the smb.conf file to control
+the behavior of <B
+CLASS="COMMAND"
+>winbindd</B
+>. Configure
+<TT
+CLASS="FILENAME"
+>smb.conf</TT
+> These are described in more detail in
+the <A
+HREF="winbindd.8.html"
+TARGET="_top"
+>winbindd(8)</A
+> man page. My
+<TT
+CLASS="FILENAME"
+>smb.conf</TT
+> file was modified to
+include the following entries in the [global] section:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>[global]
+ &#60;...&#62;
# separate domain and username with '+', like DOMAIN+username
- <a href="winbindd.8.html#WINBINDSEPARATOR" target="_top">winbind separator</a> = +
+ <A
+HREF="winbindd.8.html#WINBINDSEPARATOR"
+TARGET="_top"
+>winbind separator</A
+> = +
# use uids from 10000 to 20000 for domain users
- <a href="winbindd.8.html#WINBINDUID" target="_top">winbind uid</a> = 10000-20000
+ <A
+HREF="winbindd.8.html#WINBINDUID"
+TARGET="_top"
+>winbind uid</A
+> = 10000-20000
# use gids from 10000 to 20000 for domain groups
- <a href="winbindd.8.html#WINBINDGID" target="_top">winbind gid</a> = 10000-20000
+ <A
+HREF="winbindd.8.html#WINBINDGID"
+TARGET="_top"
+>winbind gid</A
+> = 10000-20000
# allow enumeration of winbind users and groups
- <a href="winbindd.8.html#WINBINDENUMUSERS" target="_top">winbind enum users</a> = yes
- <a href="winbindd.8.html#WINBINDENUMGROUP" target="_top">winbind enum groups</a> = yes
+ <A
+HREF="winbindd.8.html#WINBINDENUMUSERS"
+TARGET="_top"
+>winbind enum users</A
+> = yes
+ <A
+HREF="winbindd.8.html#WINBINDENUMGROUP"
+TARGET="_top"
+>winbind enum groups</A
+> = yes
# give winbind users a real shell (only needed if they have telnet access)
- <a href="winbindd.8.html#TEMPLATEHOMEDIR" target="_top">template homedir</a> = /home/winnt/%D/%U
- <a href="winbindd.8.html#TEMPLATESHELL" target="_top">template shell</a> = /bin/bash
-</pre></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2893098"></a>Join the SAMBA server to the PDC domain</h4></div></div><p>
-Enter the following command to make the SAMBA server join the
-PDC domain, where <i><tt>DOMAIN</tt></i> is the name of
-your Windows domain and <i><tt>Administrator</tt></i> is
-a domain user who has administrative privileges in the domain.
-</p><p>
-<tt>root#</tt> <b>/usr/local/samba/bin/net join -S PDC -U Administrator</b>
-</p><p>
-The proper response to the command should be: &quot;Joined the domain
-<i><tt>DOMAIN</tt></i>&quot; where <i><tt>DOMAIN</tt></i>
-is your DOMAIN name.
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2893155"></a>Start up the winbindd daemon and test it!</h4></div></div><p>
-Eventually, you will want to modify your smb startup script to
+ <A
+HREF="winbindd.8.html#TEMPLATEHOMEDIR"
+TARGET="_top"
+>template homedir</A
+> = /home/winnt/%D/%U
+ <A
+HREF="winbindd.8.html#TEMPLATESHELL"
+TARGET="_top"
+>template shell</A
+> = /bin/bash</PRE
+></P
+></DIV
+><DIV
+CLASS="SECT3"
+><H3
+CLASS="SECT3"
+><A
+NAME="AEN2406">15.5.3.4. Join the SAMBA server to the PDC domain</H3
+><P
+>Enter the following command to make the SAMBA server join the
+PDC domain, where <TT
+CLASS="REPLACEABLE"
+><I
+>DOMAIN</I
+></TT
+> is the name of
+your Windows domain and <TT
+CLASS="REPLACEABLE"
+><I
+>Administrator</I
+></TT
+> is
+a domain user who has administrative privileges in the domain.</P
+><P
+><TT
+CLASS="PROMPT"
+>root#</TT
+> <B
+CLASS="COMMAND"
+>/usr/local/samba/bin/net rpc join -S PDC -U Administrator</B
+></P
+><P
+>The proper response to the command should be: "Joined the domain
+<TT
+CLASS="REPLACEABLE"
+><I
+>DOMAIN</I
+></TT
+>" where <TT
+CLASS="REPLACEABLE"
+><I
+>DOMAIN</I
+></TT
+>
+is your DOMAIN name.</P
+></DIV
+><DIV
+CLASS="SECT3"
+><H3
+CLASS="SECT3"
+><A
+NAME="AEN2417">15.5.3.5. Start up the winbindd daemon and test it!</H3
+><P
+>Eventually, you will want to modify your smb startup script to
automatically invoke the winbindd daemon when the other parts of
SAMBA start, but it is possible to test out just the winbind
portion first. To start up winbind services, enter the following
-command as root:
-</p><p>
-<tt>root#</tt> <b>/usr/local/samba/bin/winbindd</b>
-</p><p>
-Winbindd can now also run in 'dual daemon mode'. This will make it
-run as 2 processes. The first will answer all requests from the cache,
-thus making responses to clients faster. The other will
-update the cache for the query that the first has just responded.
-Advantage of this is that responses stay accurate and are faster.
-You can enable dual daemon mode by adding '-B' to the commandline:
-</p><p>
-<tt>root#</tt> <b>/usr/local/samba/bin/winbindd -B</b>
-</p><p>
-I'm always paranoid and like to make sure the daemon
-is really running...
-</p><p>
-<tt>root#</tt> <b>ps -ae | grep winbindd</b>
-</p><p>
-This command should produce output like this, if the daemon is running
-</p><p>
-3025 ? 00:00:00 winbindd
-</p><p>
-Now... for the real test, try to get some information about the
-users on your PDC
-</p><p>
-<tt>root#</tt> <b>/usr/local/samba/bin/wbinfo -u</b>
-</p><p>
+command as root:</P
+><P
+><TT
+CLASS="PROMPT"
+>root#</TT
+> <B
+CLASS="COMMAND"
+>/usr/local/samba/bin/winbindd</B
+></P
+><P
+>I'm always paranoid and like to make sure the daemon
+is really running...</P
+><P
+><TT
+CLASS="PROMPT"
+>root#</TT
+> <B
+CLASS="COMMAND"
+>ps -ae | grep winbindd</B
+></P
+><P
+>This command should produce output like this, if the daemon is running</P
+><P
+>3025 ? 00:00:00 winbindd</P
+><P
+>Now... for the real test, try to get some information about the
+users on your PDC</P
+><P
+><TT
+CLASS="PROMPT"
+>root#</TT
+> <B
+CLASS="COMMAND"
+>/usr/local/samba/bin/wbinfo -u</B
+></P
+><P
+>
This should echo back a list of users on your Windows users on
-your PDC. For example, I get the following response:
-</p><pre class="programlisting">
- CEO+Administrator
- CEO+burdell
- CEO+Guest
- CEO+jt-ad
- CEO+krbtgt
- CEO+TsInternetUser
-</pre><p>
-Obviously, I have named my domain 'CEO' and my <i><tt>winbind
-separator</tt></i> is '+'.
-</p><p>
-You can do the same sort of thing to get group information from
-the PDC:
-</p><pre class="programlisting">
-<tt>root#</tt> <b>/usr/local/samba/bin/wbinfo -g</b>
- CEO+Domain Admins
- CEO+Domain Users
- CEO+Domain Guests
- CEO+Domain Computers
- CEO+Domain Controllers
- CEO+Cert Publishers
- CEO+Schema Admins
- CEO+Enterprise Admins
- CEO+Group Policy Creator Owners
-</pre><p>
-The function 'getent' can now be used to get unified
+your PDC. For example, I get the following response:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>CEO+Administrator
+CEO+burdell
+CEO+Guest
+CEO+jt-ad
+CEO+krbtgt
+CEO+TsInternetUser</PRE
+></P
+><P
+>Obviously, I have named my domain 'CEO' and my <TT
+CLASS="PARAMETER"
+><I
+>winbind
+separator</I
+></TT
+> is '+'.</P
+><P
+>You can do the same sort of thing to get group information from
+the PDC:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+><TT
+CLASS="PROMPT"
+>root#</TT
+> <B
+CLASS="COMMAND"
+>/usr/local/samba/bin/wbinfo -g</B
+>
+CEO+Domain Admins
+CEO+Domain Users
+CEO+Domain Guests
+CEO+Domain Computers
+CEO+Domain Controllers
+CEO+Cert Publishers
+CEO+Schema Admins
+CEO+Enterprise Admins
+CEO+Group Policy Creator Owners</PRE
+></P
+><P
+>The function 'getent' can now be used to get unified
lists of both local and PDC users and groups.
-Try the following command:
-</p><p>
-<tt>root#</tt> <b>getent passwd</b>
-</p><p>
-You should get a list that looks like your <tt>/etc/passwd</tt>
+Try the following command:</P
+><P
+><TT
+CLASS="PROMPT"
+>root#</TT
+> <B
+CLASS="COMMAND"
+>getent passwd</B
+></P
+><P
+>You should get a list that looks like your <TT
+CLASS="FILENAME"
+>/etc/passwd</TT
+>
list followed by the domain users with their new uids, gids, home
-directories and default shells.
-</p><p>
-The same thing can be done for groups with the command
-</p><p>
-<tt>root#</tt> <b>getent group</b>
-</p></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2893399"></a>Fix the init.d startup scripts</h4></div></div><div class="sect4" lang="en"><div class="titlepage"><div><h5 class="title"><a name="id2893407"></a>Linux</h5></div></div><p>
-The <b>winbindd</b> daemon needs to start up after the
-<b>smbd</b> and <b>nmbd</b> daemons are running.
-To accomplish this task, you need to modify the startup scripts of your system.
-They are located at <tt>/etc/init.d/smb</tt> in RedHat and
-<tt>/etc/init.d/samba</tt> in Debian.
+directories and default shells.</P
+><P
+>The same thing can be done for groups with the command</P
+><P
+><TT
+CLASS="PROMPT"
+>root#</TT
+> <B
+CLASS="COMMAND"
+>getent group</B
+></P
+></DIV
+><DIV
+CLASS="SECT3"
+><H3
+CLASS="SECT3"
+><A
+NAME="AEN2453">15.5.3.6. Fix the init.d startup scripts</H3
+><DIV
+CLASS="SECT4"
+><H4
+CLASS="SECT4"
+><A
+NAME="AEN2455">15.5.3.6.1. Linux</H4
+><P
+>The <B
+CLASS="COMMAND"
+>winbindd</B
+> daemon needs to start up after the
+<B
+CLASS="COMMAND"
+>smbd</B
+> and <B
+CLASS="COMMAND"
+>nmbd</B
+> daemons are running.
+To accomplish this task, you need to modify the startup scripts of your system. They are located at <TT
+CLASS="FILENAME"
+>/etc/init.d/smb</TT
+> in RedHat and
+<TT
+CLASS="FILENAME"
+>/etc/init.d/samba</TT
+> in Debian.
script to add commands to invoke this daemon in the proper sequence. My
-startup script starts up <b>smbd</b>,
-<b>nmbd</b>, and <b>winbindd</b> from the
-<tt>/usr/local/samba/bin</tt> directory directly. The 'start'
-function in the script looks like this:
-</p><pre class="programlisting">
-start() {
- KIND=&quot;SMB&quot;
- echo -n $&quot;Starting $KIND services: &quot;
+startup script starts up <B
+CLASS="COMMAND"
+>smbd</B
+>,
+<B
+CLASS="COMMAND"
+>nmbd</B
+>, and <B
+CLASS="COMMAND"
+>winbindd</B
+> from the
+<TT
+CLASS="FILENAME"
+>/usr/local/samba/bin</TT
+> directory directly. The 'start'
+function in the script looks like this:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>start() {
+ KIND="SMB"
+ echo -n $"Starting $KIND services: "
daemon /usr/local/samba/bin/smbd $SMBDOPTIONS
RETVAL=$?
echo
- KIND=&quot;NMB&quot;
- echo -n $&quot;Starting $KIND services: &quot;
+ KIND="NMB"
+ echo -n $"Starting $KIND services: "
daemon /usr/local/samba/bin/nmbd $NMBDOPTIONS
RETVAL2=$?
echo
- KIND=&quot;Winbind&quot;
- echo -n $&quot;Starting $KIND services: &quot;
+ KIND="Winbind"
+ echo -n $"Starting $KIND services: "
daemon /usr/local/samba/bin/winbindd
RETVAL3=$?
echo
- [ $RETVAL -eq 0 -a $RETVAL2 -eq 0 -a $RETVAL3 -eq 0 ] &amp;&amp; \
- touch /var/lock/subsys/smb || RETVAL=1
+ [ $RETVAL -eq 0 -a $RETVAL2 -eq 0 -a $RETVAL3 -eq 0 ] &#38;&#38; touch /var/lock/subsys/smb || \
+ RETVAL=1
return $RETVAL
-}
-</pre><p>If you would like to run winbindd in dual daemon mode, replace
-the line
-</p><pre class="programlisting">
- daemon /usr/local/samba/bin/winbindd
-</pre><p>
-
-in the example above with:
-
-</p><pre class="programlisting">
- daemon /usr/local/samba/bin/winbindd -B
-</pre><p>.
-</p><p>
-The 'stop' function has a corresponding entry to shut down the
-services and looks like this:
-</p><pre class="programlisting">
-stop() {
- KIND=&quot;SMB&quot;
- echo -n $&quot;Shutting down $KIND services: &quot;
+}</PRE
+></P
+><P
+>The 'stop' function has a corresponding entry to shut down the
+services and look s like this:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>stop() {
+ KIND="SMB"
+ echo -n $"Shutting down $KIND services: "
killproc smbd
RETVAL=$?
echo
- KIND=&quot;NMB&quot;
- echo -n $&quot;Shutting down $KIND services: &quot;
+ KIND="NMB"
+ echo -n $"Shutting down $KIND services: "
killproc nmbd
RETVAL2=$?
echo
- KIND=&quot;Winbind&quot;
- echo -n $&quot;Shutting down $KIND services: &quot;
+ KIND="Winbind"
+ echo -n $"Shutting down $KIND services: "
killproc winbindd
RETVAL3=$?
- [ $RETVAL -eq 0 -a $RETVAL2 -eq 0 -a $RETVAL3 -eq 0 ] &amp;&amp; \
- rm -f /var/lock/subsys/smb
- echo &quot;&quot;
+ [ $RETVAL -eq 0 -a $RETVAL2 -eq 0 -a $RETVAL3 -eq 0 ] &#38;&#38; rm -f /var/lock/subsys/smb
+ echo ""
return $RETVAL
-}
-</pre></div><div class="sect4" lang="en"><div class="titlepage"><div><h5 class="title"><a name="id2893544"></a>Solaris</h5></div></div><p>Winbind doesn't work on solaris 9, see the <a href="Portability.html#winbind-solaris9" title="Winbind on Solaris 9">Portability</a> chapter for details.</p><p>On solaris, you need to modify the
-<tt>/etc/init.d/samba.server</tt> startup script. It usually
+}</PRE
+></P
+></DIV
+><DIV
+CLASS="SECT4"
+><H4
+CLASS="SECT4"
+><A
+NAME="AEN2472">15.5.3.6.2. Solaris</H4
+><P
+>On solaris, you need to modify the
+<TT
+CLASS="FILENAME"
+>/etc/init.d/samba.server</TT
+> startup script. It usually
only starts smbd and nmbd but should now start winbindd too. If you
-have samba installed in <tt>/usr/local/samba/bin</tt>,
-the file could contains something like this:
-</p><pre class="programlisting">
- ##
- ## samba.server
- ##
-
- if [ ! -d /usr/bin ]
- then # /usr not mounted
- exit
- fi
+have samba installed in <TT
+CLASS="FILENAME"
+>/usr/local/samba/bin</TT
+>,
+the file could contains something like this:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>##
+## samba.server
+##
- killproc() { # kill the named process(es)
- pid=`/usr/bin/ps -e |
- /usr/bin/grep -w $1 |
- /usr/bin/sed -e 's/^ *//' -e 's/ .*//'`
- [ &quot;$pid&quot; != &quot;&quot; ] &amp;&amp; kill $pid
- }
-
- # Start/stop processes required for samba server
+if [ ! -d /usr/bin ]
+then # /usr not mounted
+ exit
+fi
- case &quot;$1&quot; in
-
- 'start')
- #
- # Edit these lines to suit your installation (paths, workgroup, host)
- #
- echo Starting SMBD
- /usr/local/samba/bin/smbd -D -s \
- /usr/local/samba/smb.conf
+killproc() { # kill the named process(es)
+ pid=`/usr/bin/ps -e |
+ /usr/bin/grep -w $1 |
+ /usr/bin/sed -e 's/^ *//' -e 's/ .*//'`
+ [ "$pid" != "" ] &#38;&#38; kill $pid
+}
+
+# Start/stop processes required for samba server
- echo Starting NMBD
- /usr/local/samba/bin/nmbd -D -l \
- /usr/local/samba/var/log -s /usr/local/samba/smb.conf
+case "$1" in
- echo Starting Winbind Daemon
- /usr/local/samba/bin/winbindd
- ;;
+'start')
+#
+# Edit these lines to suit your installation (paths, workgroup, host)
+#
+echo Starting SMBD
+ /usr/local/samba/bin/smbd -D -s \
+ /usr/local/samba/smb.conf
- 'stop')
- killproc nmbd
- killproc smbd
- killproc winbindd
- ;;
+echo Starting NMBD
+ /usr/local/samba/bin/nmbd -D -l \
+ /usr/local/samba/var/log -s /usr/local/samba/smb.conf
- *)
- echo &quot;Usage: /etc/init.d/samba.server { start | stop }&quot;
- ;;
- esac
-</pre><p>
-Again, if you would like to run samba in dual daemon mode, replace
-</p><pre class="programlisting">
- /usr/local/samba/bin/winbindd
-</pre><p>
+echo Starting Winbind Daemon
+ /usr/local/samba/bin/winbindd
+ ;;
-in the script above with:
+'stop')
+ killproc nmbd
+ killproc smbd
+ killproc winbindd
+ ;;
-</p><pre class="programlisting">
- /usr/local/samba/bin/winbindd -B
-</pre><p>
-</p></div><div class="sect4" lang="en"><div class="titlepage"><div><h5 class="title"><a name="id2893644"></a>Restarting</h5></div></div><p>
-If you restart the <b>smbd</b>, <b>nmbd</b>,
-and <b>winbindd</b> daemons at this point, you
+*)
+ echo "Usage: /etc/init.d/samba.server { start | stop }"
+ ;;
+esac</PRE
+></P
+></DIV
+><DIV
+CLASS="SECT4"
+><H4
+CLASS="SECT4"
+><A
+NAME="AEN2479">15.5.3.6.3. Restarting</H4
+><P
+>If you restart the <B
+CLASS="COMMAND"
+>smbd</B
+>, <B
+CLASS="COMMAND"
+>nmbd</B
+>,
+and <B
+CLASS="COMMAND"
+>winbindd</B
+> daemons at this point, you
should be able to connect to the samba server as a domain member just as
-if you were a local user.
-</p></div></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2893681"></a>Configure Winbind and PAM</h4></div></div><p>
-If you have made it this far, you know that winbindd and samba are working
+if you were a local user.</P
+></DIV
+></DIV
+><DIV
+CLASS="SECT3"
+><H3
+CLASS="SECT3"
+><A
+NAME="AEN2485">15.5.3.7. Configure Winbind and PAM</H3
+><P
+>If you have made it this far, you know that winbindd and samba are working
together. If you want to use winbind to provide authentication for other
services, keep reading. The pam configuration files need to be altered in
this step. (Did you remember to make backups of your original
-<tt>/etc/pam.d</tt> files? If not, do it now.)
-</p><p>
-You will need a pam module to use winbindd with these other services. This
-module will be compiled in the <tt>../source/nsswitch</tt> directory
-by invoking the command
-</p><p>
-<tt>root#</tt> <b>make nsswitch/pam_winbind.so</b>
-</p><p>
-from the <tt>../source</tt> directory. The
-<tt>pam_winbind.so</tt> file should be copied to the location of
+<TT
+CLASS="FILENAME"
+>/etc/pam.d</TT
+> files? If not, do it now.)</P
+><P
+>You will need a pam module to use winbindd with these other services. This
+module will be compiled in the <TT
+CLASS="FILENAME"
+>../source/nsswitch</TT
+> directory
+by invoking the command</P
+><P
+><TT
+CLASS="PROMPT"
+>root#</TT
+> <B
+CLASS="COMMAND"
+>make nsswitch/pam_winbind.so</B
+></P
+><P
+>from the <TT
+CLASS="FILENAME"
+>../source</TT
+> directory. The
+<TT
+CLASS="FILENAME"
+>pam_winbind.so</TT
+> file should be copied to the location of
your other pam security modules. On my RedHat system, this was the
-<tt>/lib/security</tt> directory. On Solaris, the pam security
-modules reside in <tt>/usr/lib/security</tt>.
-</p><p>
-<tt>root#</tt> <b>cp ../samba/source/nsswitch/pam_winbind.so /lib/security</b>
-</p><div class="sect4" lang="en"><div class="titlepage"><div><h5 class="title"><a name="id2893790"></a>Linux/FreeBSD-specific PAM configuration</h5></div></div><p>
-The <tt>/etc/pam.d/samba</tt> file does not need to be changed. I
-just left this fileas it was:
-</p><pre class="programlisting">
- auth required /lib/security/pam_stack.so service=system-auth
- account required /lib/security/pam_stack.so service=system-auth
-</pre><p>
-The other services that I modified to allow the use of winbind
+<TT
+CLASS="FILENAME"
+>/lib/security</TT
+> directory. On Solaris, the pam security
+modules reside in <TT
+CLASS="FILENAME"
+>/usr/lib/security</TT
+>.</P
+><P
+><TT
+CLASS="PROMPT"
+>root#</TT
+> <B
+CLASS="COMMAND"
+>cp ../samba/source/nsswitch/pam_winbind.so /lib/security</B
+></P
+><DIV
+CLASS="SECT4"
+><H4
+CLASS="SECT4"
+><A
+NAME="AEN2502">15.5.3.7.1. Linux/FreeBSD-specific PAM configuration</H4
+><P
+>The <TT
+CLASS="FILENAME"
+>/etc/pam.d/samba</TT
+> file does not need to be changed. I
+just left this fileas it was:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>auth required /lib/security/pam_stack.so service=system-auth
+account required /lib/security/pam_stack.so service=system-auth</PRE
+></P
+><P
+>The other services that I modified to allow the use of winbind
as an authentication service were the normal login on the console (or a terminal
session), telnet logins, and ftp service. In order to enable these
services, you may first need to change the entries in
-<tt>/etc/xinetd.d</tt> (or <tt>/etc/inetd.conf</tt>).
+<TT
+CLASS="FILENAME"
+>/etc/xinetd.d</TT
+> (or <TT
+CLASS="FILENAME"
+>/etc/inetd.conf</TT
+>).
RedHat 7.1 uses the new xinetd.d structure, in this case you need
-to change the lines in <tt>/etc/xinetd.d/telnet</tt>
-and <tt>/etc/xinetd.d/wu-ftp</tt> from
-</p><pre class="programlisting">
- enable = no
-</pre><p>
-to
-</p><pre class="programlisting">
- enable = yes
-</pre><p>
+to change the lines in <TT
+CLASS="FILENAME"
+>/etc/xinetd.d/telnet</TT
+>
+and <TT
+CLASS="FILENAME"
+>/etc/xinetd.d/wu-ftp</TT
+> from </P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>enable = no</PRE
+></P
+><P
+>to</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>enable = yes</PRE
+></P
+><P
+>
For ftp services to work properly, you will also need to either
have individual directories for the domain users already present on
the server, or change the home directory template to a general
directory for all domain users. These can be easily set using
-the <tt>smb.conf</tt> global entry
-<b>template homedir</b>.
-</p><p>
-The <tt>/etc/pam.d/ftp</tt> file can be changed
+the <TT
+CLASS="FILENAME"
+>smb.conf</TT
+> global entry
+<B
+CLASS="COMMAND"
+>template homedir</B
+>.</P
+><P
+>The <TT
+CLASS="FILENAME"
+>/etc/pam.d/ftp</TT
+> file can be changed
to allow winbind ftp access in a manner similar to the
-samba file. My <tt>/etc/pam.d/ftp</tt> file was
-changed to look like this:
-</p><pre class="programlisting">
- auth required /lib/security/pam_listfile.so item=user sense=deny \
- file=/etc/ftpusers onerr=succeed
- auth sufficient /lib/security/pam_winbind.so
- auth required /lib/security/pam_stack.so service=system-auth
- auth required /lib/security/pam_shells.so
- account sufficient /lib/security/pam_winbind.so
- account required /lib/security/pam_stack.so service=system-auth
- session required /lib/security/pam_stack.so service=system-auth
-</pre><p>
-The <tt>/etc/pam.d/login</tt> file can be changed nearly the
-same way. It now looks like this:
-</p><pre class="programlisting">
- auth required /lib/security/pam_securetty.so
- auth sufficient /lib/security/pam_winbind.so
- auth sufficient /lib/security/pam_unix.so use_first_pass
- auth required /lib/security/pam_stack.so service=system-auth
- auth required /lib/security/pam_nologin.so
- account sufficient /lib/security/pam_winbind.so
- account required /lib/security/pam_stack.so service=system-auth
- password required /lib/security/pam_stack.so service=system-auth
- session required /lib/security/pam_stack.so service=system-auth
- session optional /lib/security/pam_console.so
-</pre><p>
-In this case, I added the <b>auth sufficient /lib/security/pam_winbind.so</b>
-lines as before, but also added the <b>required pam_securetty.so</b>
+samba file. My <TT
+CLASS="FILENAME"
+>/etc/pam.d/ftp</TT
+> file was
+changed to look like this:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>auth required /lib/security/pam_listfile.so item=user sense=deny file=/etc/ftpusers onerr=succeed
+auth sufficient /lib/security/pam_winbind.so
+auth required /lib/security/pam_stack.so service=system-auth
+auth required /lib/security/pam_shells.so
+account sufficient /lib/security/pam_winbind.so
+account required /lib/security/pam_stack.so service=system-auth
+session required /lib/security/pam_stack.so service=system-auth</PRE
+></P
+><P
+>The <TT
+CLASS="FILENAME"
+>/etc/pam.d/login</TT
+> file can be changed nearly the
+same way. It now looks like this:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>auth required /lib/security/pam_securetty.so
+auth sufficient /lib/security/pam_winbind.so
+auth sufficient /lib/security/pam_unix.so use_first_pass
+auth required /lib/security/pam_stack.so service=system-auth
+auth required /lib/security/pam_nologin.so
+account sufficient /lib/security/pam_winbind.so
+account required /lib/security/pam_stack.so service=system-auth
+password required /lib/security/pam_stack.so service=system-auth
+session required /lib/security/pam_stack.so service=system-auth
+session optional /lib/security/pam_console.so</PRE
+></P
+><P
+>In this case, I added the <B
+CLASS="COMMAND"
+>auth sufficient /lib/security/pam_winbind.so</B
+>
+lines as before, but also added the <B
+CLASS="COMMAND"
+>required pam_securetty.so</B
+>
above it, to disallow root logins over the network. I also added a
-<b>sufficient /lib/security/pam_unix.so use_first_pass</b>
-line after the <b>winbind.so</b> line to get rid of annoying
-double prompts for passwords.
-</p></div><div class="sect4" lang="en"><div class="titlepage"><div><h5 class="title"><a name="id2894014"></a>Solaris-specific configuration</h5></div></div><p>
-The /etc/pam.conf needs to be changed. I changed this file so that my Domain
+<B
+CLASS="COMMAND"
+>sufficient /lib/security/pam_unix.so use_first_pass</B
+>
+line after the <B
+CLASS="COMMAND"
+>winbind.so</B
+> line to get rid of annoying
+double prompts for passwords.</P
+></DIV
+><DIV
+CLASS="SECT4"
+><H4
+CLASS="SECT4"
+><A
+NAME="AEN2535">15.5.3.7.2. Solaris-specific configuration</H4
+><P
+>The /etc/pam.conf needs to be changed. I changed this file so that my Domain
users can logon both locally as well as telnet.The following are the changes
that I made.You can customize the pam.conf file as per your requirements,but
be sure of those changes because in the worst case it will leave your system
-nearly impossible to boot.
-</p><pre class="programlisting">
- #
- #ident &quot;@(#)pam.conf 1.14 99/09/16 SMI&quot;
- #
- # Copyright (c) 1996-1999, Sun Microsystems, Inc.
- # All Rights Reserved.
- #
- # PAM configuration
- #
- # Authentication management
- #
- login auth required /usr/lib/security/pam_winbind.so
- login auth required /usr/lib/security/$ISA/pam_unix.so.1 try_first_pass
- login auth required /usr/lib/security/$ISA/pam_dial_auth.so.1 try_first_pass
- #
- rlogin auth sufficient /usr/lib/security/pam_winbind.so
- rlogin auth sufficient /usr/lib/security/$ISA/pam_rhosts_auth.so.1
- rlogin auth required /usr/lib/security/$ISA/pam_unix.so.1 try_first_pass
- #
- dtlogin auth sufficient /usr/lib/security/pam_winbind.so
- dtlogin auth required /usr/lib/security/$ISA/pam_unix.so.1 try_first_pass
- #
- rsh auth required /usr/lib/security/$ISA/pam_rhosts_auth.so.1
- other auth sufficient /usr/lib/security/pam_winbind.so
- other auth required /usr/lib/security/$ISA/pam_unix.so.1 try_first_pass
- #
- # Account management
- #
- login account sufficient /usr/lib/security/pam_winbind.so
- login account requisite /usr/lib/security/$ISA/pam_roles.so.1
- login account required /usr/lib/security/$ISA/pam_unix.so.1
- #
- dtlogin account sufficient /usr/lib/security/pam_winbind.so
- dtlogin account requisite /usr/lib/security/$ISA/pam_roles.so.1
- dtlogin account required /usr/lib/security/$ISA/pam_unix.so.1
- #
- other account sufficient /usr/lib/security/pam_winbind.so
- other account requisite /usr/lib/security/$ISA/pam_roles.so.1
- other account required /usr/lib/security/$ISA/pam_unix.so.1
- #
- # Session management
- #
- other session required /usr/lib/security/$ISA/pam_unix.so.1
- #
- # Password management
- #
- #other password sufficient /usr/lib/security/pam_winbind.so
- other password required /usr/lib/security/$ISA/pam_unix.so.1
- dtsession auth required /usr/lib/security/$ISA/pam_unix.so.1
- #
- # Support for Kerberos V5 authentication (uncomment to use Kerberos)
- #
- #rlogin auth optional /usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass
- #login auth optional /usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass
- #dtlogin auth optional /usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass
- #other auth optional /usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass
- #dtlogin account optional /usr/lib/security/$ISA/pam_krb5.so.1
- #other account optional /usr/lib/security/$ISA/pam_krb5.so.1
- #other session optional /usr/lib/security/$ISA/pam_krb5.so.1
- #other password optional /usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass
-</pre><p>
-I also added a try_first_pass line after the winbind.so line to get rid of
-annoying double prompts for passwords.
-</p><p>
-Now restart your Samba and try connecting through your application that you
-configured in the pam.conf.
-</p></div></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2894106"></a>Limitations</h2></div></div><p>Winbind has a number of limitations in its current
+nearly impossible to boot.</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>#
+#ident "@(#)pam.conf 1.14 99/09/16 SMI"
+#
+# Copyright (c) 1996-1999, Sun Microsystems, Inc.
+# All Rights Reserved.
+#
+# PAM configuration
+#
+# Authentication management
+#
+login auth required /usr/lib/security/pam_winbind.so
+login auth required /usr/lib/security/$ISA/pam_unix.so.1 try_first_pass
+login auth required /usr/lib/security/$ISA/pam_dial_auth.so.1 try_first_pass
+#
+rlogin auth sufficient /usr/lib/security/pam_winbind.so
+rlogin auth sufficient /usr/lib/security/$ISA/pam_rhosts_auth.so.1
+rlogin auth required /usr/lib/security/$ISA/pam_unix.so.1 try_first_pass
+#
+dtlogin auth sufficient /usr/lib/security/pam_winbind.so
+dtlogin auth required /usr/lib/security/$ISA/pam_unix.so.1 try_first_pass
+#
+rsh auth required /usr/lib/security/$ISA/pam_rhosts_auth.so.1
+other auth sufficient /usr/lib/security/pam_winbind.so
+other auth required /usr/lib/security/$ISA/pam_unix.so.1 try_first_pass
+#
+# Account management
+#
+login account sufficient /usr/lib/security/pam_winbind.so
+login account requisite /usr/lib/security/$ISA/pam_roles.so.1
+login account required /usr/lib/security/$ISA/pam_unix.so.1
+#
+dtlogin account sufficient /usr/lib/security/pam_winbind.so
+dtlogin account requisite /usr/lib/security/$ISA/pam_roles.so.1
+dtlogin account required /usr/lib/security/$ISA/pam_unix.so.1
+#
+other account sufficient /usr/lib/security/pam_winbind.so
+other account requisite /usr/lib/security/$ISA/pam_roles.so.1
+other account required /usr/lib/security/$ISA/pam_unix.so.1
+#
+# Session management
+#
+other session required /usr/lib/security/$ISA/pam_unix.so.1
+#
+# Password management
+#
+#other password sufficient /usr/lib/security/pam_winbind.so
+other password required /usr/lib/security/$ISA/pam_unix.so.1
+dtsession auth required /usr/lib/security/$ISA/pam_unix.so.1
+#
+# Support for Kerberos V5 authentication (uncomment to use Kerberos)
+#
+#rlogin auth optional /usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass
+#login auth optional /usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass
+#dtlogin auth optional /usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass
+#other auth optional /usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass
+#dtlogin account optional /usr/lib/security/$ISA/pam_krb5.so.1
+#other account optional /usr/lib/security/$ISA/pam_krb5.so.1
+#other session optional /usr/lib/security/$ISA/pam_krb5.so.1
+#other password optional /usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass</PRE
+></P
+><P
+>I also added a try_first_pass line after the winbind.so line to get rid of
+annoying double prompts for passwords.</P
+><P
+>Now restart your Samba &#38; try connecting through your application that you
+configured in the pam.conf.</P
+></DIV
+></DIV
+></DIV
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN2542">15.6. Limitations</H1
+><P
+>Winbind has a number of limitations in its current
released version that we hope to overcome in future
- releases:</p><div class="itemizedlist"><ul type="disc"><li><p>Winbind is currently only available for
- the Linux, Solaris and IRIX operating systems, although ports to other operating
+ releases:</P
+><P
+></P
+><UL
+><LI
+><P
+>Winbind is currently only available for
+ the Linux operating system, although ports to other operating
systems are certainly possible. For such ports to be feasible,
we require the C library of the target operating system to
support the Name Service Switch and Pluggable Authentication
Modules systems. This is becoming more common as NSS and
- PAM gain support among UNIX vendors.</p></li><li><p>The mappings of Windows NT RIDs to UNIX ids
+ PAM gain support among UNIX vendors.</P
+></LI
+><LI
+><P
+>The mappings of Windows NT RIDs to UNIX ids
is not made algorithmically and depends on the order in which
unmapped users or groups are seen by winbind. It may be difficult
to recover the mappings of rid to UNIX id mapping if the file
- containing this information is corrupted or destroyed.</p></li><li><p>Currently the winbind PAM module does not take
+ containing this information is corrupted or destroyed.</P
+></LI
+><LI
+><P
+>Currently the winbind PAM module does not take
into account possible workstation and logon time restrictions
- that may be been set for Windows NT users, this is
- instead up to the PDC to enforce.</p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2894160"></a>Conclusion</h2></div></div><p>The winbind system, through the use of the Name Service
+ that may be been set for Windows NT users.</P
+></LI
+></UL
+></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN2552">15.7. Conclusion</H1
+><P
+>The winbind system, through the use of the Name Service
Switch, Pluggable Authentication Modules, and appropriate
Microsoft RPC calls have allowed us to provide seamless
integration of Microsoft Windows NT domain users on a
UNIX system. The result is a great reduction in the administrative
- cost of running a mixed UNIX and NT network.</p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="CUPS-printing.html">Prev</a></td><td width="20%" align="center"><a accesskey="u" href="optional.html">Up</a></td><td width="40%" align="right"><a accesskey="n" href="AdvancedNetworkManagement.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter14.CUPS Printing Support</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">Chapter16.Advanced Network Manangement</td></tr></table></div></body></html>
+ cost of running a mixed UNIX and NT network.</P
+></DIV
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+SUMMARY="Footer navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="printing.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="samba-howto-collection.html"
+ACCESSKEY="H"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="pdb-mysql.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>Printing Support</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="optional.html"
+ACCESSKEY="U"
+>Up</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>Passdb MySQL plugin</TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+> \ No newline at end of file
diff --git a/docs/htmldocs/winbindd.8.html b/docs/htmldocs/winbindd.8.html
index b1260df500..fb8c9c0458 100644
--- a/docs/htmldocs/winbindd.8.html
+++ b/docs/htmldocs/winbindd.8.html
@@ -1,153 +1,644 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>winbindd</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="winbindd.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>winbindd &#8212; Name Service Switch daemon for resolving names
- from NT servers</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><tt>winbindd</tt> [-F] [-S] [-i] [-B] [-d &lt;debug level&gt;] [-s &lt;smb config file&gt;] [-n]</p></div></div><div class="refsect1" lang="en"><h2>DESCRIPTION</h2><p>This program is part of the <a href="Samba.7.html">Samba(7)</a> suite.</p><p><b>winbindd</b> is a daemon that provides
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
+<HTML
+><HEAD
+><TITLE
+>winbindd</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"></HEAD
+><BODY
+CLASS="REFENTRY"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><H1
+><A
+NAME="WINBINDD">winbindd</H1
+><DIV
+CLASS="REFNAMEDIV"
+><A
+NAME="AEN5"
+></A
+><H2
+>Name</H2
+>winbindd&nbsp;--&nbsp;Name Service Switch daemon for resolving names
+ from NT servers</DIV
+><DIV
+CLASS="REFSYNOPSISDIV"
+><A
+NAME="AEN8"><H2
+>Synopsis</H2
+><P
+><B
+CLASS="COMMAND"
+>winbindd</B
+> [-F] [-S] [-i] [-B] [-d &#60;debug level&#62;] [-s &#60;smb config file&#62;] [-n]</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN18"
+></A
+><H2
+>DESCRIPTION</H2
+><P
+>This program is part of the <A
+HREF="samba.7.html"
+TARGET="_top"
+> Samba</A
+> suite.</P
+><P
+><B
+CLASS="COMMAND"
+>winbindd</B
+> is a daemon that provides
a service for the Name Service Switch capability that is present
in most modern C libraries. The Name Service Switch allows user
and system information to be obtained from different databases
services such as NIS or DNS. The exact behaviour can be configured
- throught the <tt>/etc/nsswitch.conf</tt> file.
+ throught the <TT
+CLASS="FILENAME"
+>/etc/nsswitch.conf</TT
+> file.
Users and groups are allocated as they are resolved to a range
of user and group ids specified by the administrator of the
- Samba system.</p><p>The service provided by <b>winbindd</b> is called `winbind' and
+ Samba system.</P
+><P
+>The service provided by <B
+CLASS="COMMAND"
+>winbindd</B
+> is called `winbind' and
can be used to resolve user and group information from a
Windows NT server. The service can also provide authentication
- services via an associated PAM module. </p><p>
- The <tt>pam_winbind</tt> module in the 2.2.2 release only
- supports the <i><tt>auth</tt></i> and <i><tt>account</tt></i>
+ services via an associated PAM module. </P
+><P
+> The <TT
+CLASS="FILENAME"
+>pam_winbind</TT
+> module in the 2.2.2 release only
+ supports the <TT
+CLASS="PARAMETER"
+><I
+>auth</I
+></TT
+> and <TT
+CLASS="PARAMETER"
+><I
+>account</I
+></TT
+>
module-types. The latter simply
performs a getpwnam() to verify that the system can obtain a uid for the
- user. If the <tt>libnss_winbind</tt> library has been correctly
+ user. If the <TT
+CLASS="FILENAME"
+>libnss_winbind</TT
+> library has been correctly
installed, this should always succeed.
- </p><p>The following nsswitch databases are implemented by
- the winbindd service: </p><div class="variablelist"><dl><dt><span class="term">hosts</span></dt><dd><p>User information traditionally stored in
- the <tt>hosts(5)</tt> file and used by
- <b>gethostbyname(3)</b> functions. Names are
+ </P
+><P
+>The following nsswitch databases are implemented by
+ the winbindd service: </P
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>hosts</DT
+><DD
+><P
+>User information traditionally stored in
+ the <TT
+CLASS="FILENAME"
+>hosts(5)</TT
+> file and used by
+ <B
+CLASS="COMMAND"
+>gethostbyname(3)</B
+> functions. Names are
resolved through the WINS server or by broadcast.
- </p></dd><dt><span class="term">passwd</span></dt><dd><p>User information traditionally stored in
- the <tt>passwd(5)</tt> file and used by
- <b>getpwent(3)</b> functions. </p></dd><dt><span class="term">group</span></dt><dd><p>Group information traditionally stored in
- the <tt>group(5)</tt> file and used by
- <b>getgrent(3)</b> functions. </p></dd></dl></div><p>For example, the following simple configuration in the
- <tt>/etc/nsswitch.conf</tt> file can be used to initially
- resolve user and group information from <tt>/etc/passwd
- </tt> and <tt>/etc/group</tt> and then from the
- Windows NT server.
-</p><pre class="programlisting">
-passwd: files winbind
+ </P
+></DD
+><DT
+>passwd</DT
+><DD
+><P
+>User information traditionally stored in
+ the <TT
+CLASS="FILENAME"
+>passwd(5)</TT
+> file and used by
+ <B
+CLASS="COMMAND"
+>getpwent(3)</B
+> functions. </P
+></DD
+><DT
+>group</DT
+><DD
+><P
+>Group information traditionally stored in
+ the <TT
+CLASS="FILENAME"
+>group(5)</TT
+> file and used by
+ <B
+CLASS="COMMAND"
+>getgrent(3)</B
+> functions. </P
+></DD
+></DL
+></DIV
+><P
+>For example, the following simple configuration in the
+ <TT
+CLASS="FILENAME"
+>/etc/nsswitch.conf</TT
+> file can be used to initially
+ resolve user and group information from <TT
+CLASS="FILENAME"
+>/etc/passwd
+ </TT
+> and <TT
+CLASS="FILENAME"
+>/etc/group</TT
+> and then from the
+ Windows NT server. </P
+><P
+><TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><PRE
+CLASS="PROGRAMLISTING"
+>passwd: files winbind
group: files winbind
-</pre><p>The following simple configuration in the
- <tt>/etc/nsswitch.conf</tt> file can be used to initially
- resolve hostnames from <tt>/etc/hosts</tt> and then from the
- WINS server.</p></div><div class="refsect1" lang="en"><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-F</span></dt><dd><p>If specified, this parameter causes
- the main <b>winbindd</b> process to not daemonize,
+ </PRE
+></TD
+></TR
+></TABLE
+></P
+><P
+>The following simple configuration in the
+ <TT
+CLASS="FILENAME"
+>/etc/nsswitch.conf</TT
+> file can be used to initially
+ resolve hostnames from <TT
+CLASS="FILENAME"
+>/etc/hosts</TT
+> and then from the
+ WINS server.</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN61"
+></A
+><H2
+>OPTIONS</H2
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>-F</DT
+><DD
+><P
+>If specified, this parameter causes
+ the main <B
+CLASS="COMMAND"
+>winbindd</B
+> process to not daemonize,
i.e. double-fork and disassociate with the terminal.
Child processes are still created as normal to service
each connection request, but the main process does not
exit. This operation mode is suitable for running
- <b>winbindd</b> under process supervisors such
- as <b>supervise</b> and <b>svscan</b>
- from Daniel J. Bernstein's <b>daemontools</b>
+ <B
+CLASS="COMMAND"
+>winbindd</B
+> under process supervisors such
+ as <B
+CLASS="COMMAND"
+>supervise</B
+> and <B
+CLASS="COMMAND"
+>svscan</B
+>
+ from Daniel J. Bernstein's <B
+CLASS="COMMAND"
+>daemontools</B
+>
package, or the AIX process monitor.
- </p></dd><dt><span class="term">-S</span></dt><dd><p>If specified, this parameter causes
- <b>winbindd</b> to log to standard output rather
- than a file.</p></dd><dt><span class="term">-V</span></dt><dd><p>Prints the version number for
-<b>smbd</b>.</p></dd><dt><span class="term">-s &lt;configuration file&gt;</span></dt><dd><p>The file specified contains the
-configuration details required by the server. The
-information in this file includes server-specific
-information such as what printcap file to use, as well
-as descriptions of all the services that the server is
-to provide. See <a href="smb.conf.5.html" target="_top"><tt>
-smb.conf(5)</tt></a> for more information.
-The default configuration file name is determined at
-compile time.</p></dd><dt><span class="term">-d|--debug=debuglevel</span></dt><dd><p><i><tt>debuglevel</tt></i> is an integer
-from 0 to 10. The default value if this parameter is
-not specified is zero.</p><p>The higher this value, the more detail will be
-logged to the log files about the activities of the
-server. At level 0, only critical errors and serious
-warnings will be logged. Level 1 is a reasonable level for
-day to day running - it generates a small amount of
-information about operations carried out.</p><p>Levels above 1 will generate considerable
-amounts of log data, and should only be used when
-investigating a problem. Levels above 3 are designed for
-use only by developers and generate HUGE amounts of log
-data, most of which is extremely cryptic.</p><p>Note that specifying this parameter here will
-override the <a href="smb.conf.5.html#loglevel" target="_top">log
-level</a> parameter in the <a href="smb.conf.5.html" target="_top">
-<tt>smb.conf(5)</tt></a> file.</p></dd><dt><span class="term">-l|--logfile=logbasename</span></dt><dd><p>File name for log/debug files. The extension
-<tt>&quot;.client&quot;</tt> will be appended. The log file is
-never removed by the client.
-</p></dd><dt><span class="term">-h|--help</span></dt><dd><p>Print a summary of command line options.
-</p></dd><dt><span class="term">-i</span></dt><dd><p>Tells <b>winbindd</b> to not
+ </P
+></DD
+><DT
+>-S</DT
+><DD
+><P
+>If specified, this parameter causes
+ <B
+CLASS="COMMAND"
+>winbindd</B
+> to log to standard output rather
+ than a file.</P
+></DD
+><DT
+>-d debuglevel</DT
+><DD
+><P
+>Sets the debuglevel to an integer between
+ 0 and 100. 0 is for no debugging and 100 is for reams and
+ reams. To submit a bug report to the Samba Team, use debug
+ level 100 (see BUGS.txt). </P
+></DD
+><DT
+>-i</DT
+><DD
+><P
+>Tells <B
+CLASS="COMMAND"
+>winbindd</B
+> to not
become a daemon and detach from the current terminal. This
option is used by developers when interactive debugging
- of <b>winbindd</b> is required.
- <b>winbindd</b> also logs to standard output,
- as if the <b>-S</b> parameter had been given.
- </p></dd><dt><span class="term">-n</span></dt><dd><p>Disable caching. This means winbindd will
+ of <B
+CLASS="COMMAND"
+>winbindd</B
+> is required.
+ <B
+CLASS="COMMAND"
+>winbindd</B
+> also logs to standard output,
+ as if the <B
+CLASS="COMMAND"
+>-S</B
+> parameter had been given.
+ </P
+></DD
+><DT
+>-n</DT
+><DD
+><P
+>Disable caching. This means winbindd will
always have to wait for a response from the domain controller
before it can respond to a client and this thus makes things
slower. The results will however be more accurate, since
results from the cache might not be up-to-date. This
might also temporarily hang winbindd if the DC doesn't respond.
- </p></dd><dt><span class="term">-B</span></dt><dd><p>Dual daemon mode. This means winbindd will run
+ </P
+></DD
+><DT
+>-B</DT
+><DD
+><P
+>Dual daemon mode. This means winbindd will run
as 2 threads. The first will answer all requests from the cache,
thus making responses to clients faster. The other will
update the cache for the query that the first has just responded.
- Advantage of this is that responses stay accurate and are faster.
- </p></dd></dl></div></div><div class="refsect1" lang="en"><h2>NAME AND ID RESOLUTION</h2><p>Users and groups on a Windows NT server are assigned
+ Advantage of this is that responses are accurate and fast.
+ </P
+></DD
+><DT
+>-s|--conf=smb.conf</DT
+><DD
+><P
+>Specifies the location of the all-important
+ <TT
+CLASS="FILENAME"
+>smb.conf</TT
+> file. </P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN103"
+></A
+><H2
+>NAME AND ID RESOLUTION</H2
+><P
+>Users and groups on a Windows NT server are assigned
a relative id (rid) which is unique for the domain when the
user or group is created. To convert the Windows NT user or group
into a unix user or group, a mapping between rids and unix user
- and group ids is required. This is one of the jobs that <b>
- winbindd</b> performs. </p><p>As winbindd users and groups are resolved from a server, user
+ and group ids is required. This is one of the jobs that <B
+CLASS="COMMAND"
+> winbindd</B
+> performs. </P
+><P
+>As winbindd users and groups are resolved from a server, user
and group ids are allocated from a specified range. This
is done on a first come, first served basis, although all existing
users and groups will be mapped as soon as a client performs a user
or group enumeration command. The allocated unix ids are stored
in a database file under the Samba lock directory and will be
- remembered. </p><p>WARNING: The rid to unix id database is the only location
+ remembered. </P
+><P
+>WARNING: The rid to unix id database is the only location
where the user and group mappings are stored by winbindd. If this
file is deleted or corrupted, there is no way for winbindd to
determine which user and group ids correspond to Windows NT user
- and group rids. </p></div><div class="refsect1" lang="en"><h2>CONFIGURATION</h2><p>Configuration of the <b>winbindd</b> daemon
- is done through configuration parameters in the <a href="smb.conf.5.html">smb.conf(5)</a> file. All parameters should be specified in the
- [global] section of smb.conf. </p><div class="itemizedlist"><ul type="disc"><li><p><a href="smb.conf.5.html#WINBINDSEPARATOR" target="_top">
- <i><tt>winbind separator</tt></i></a></p></li><li><p><a href="smb.conf.5.html#WINBINDUID" target="_top">
- <i><tt>winbind uid</tt></i></a></p></li><li><p><a href="smb.conf.5.html#WINBINDGID" target="_top">
- <i><tt>winbind gid</tt></i></a></p></li><li><p><a href="smb.conf.5.html#WINBINDCACHETIME" target="_top">
- <i><tt>winbind cache time</tt></i></a></p></li><li><p><a href="smb.conf.5.html#WINBINDENUMUSERS" target="_top">
- <i><tt>winbind enum users</tt></i></a></p></li><li><p><a href="smb.conf.5.html#WINBINDENUMGROUPS" target="_top">
- <i><tt>winbind enum groups</tt></i></a></p></li><li><p><a href="smb.conf.5.html#TEMPLATEHOMEDIR" target="_top">
- <i><tt>template homedir</tt></i></a></p></li><li><p><a href="smb.conf.5.html#TEMPLATESHELL" target="_top">
- <i><tt>template shell</tt></i></a></p></li><li><p><a href="smb.conf.5.html#WINBINDUSEDEFAULTDOMAIN" target="_top">
- <i><tt>winbind use default domain</tt></i></a></p></li></ul></div></div><div class="refsect1" lang="en"><h2>EXAMPLE SETUP</h2><p>To setup winbindd for user and group lookups plus
+ and group rids. </P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN109"
+></A
+><H2
+>CONFIGURATION</H2
+><P
+>Configuration of the <B
+CLASS="COMMAND"
+>winbindd</B
+> daemon
+ is done through configuration parameters in the <TT
+CLASS="FILENAME"
+>smb.conf(5)
+ </TT
+> file. All parameters should be specified in the
+ [global] section of smb.conf. </P
+><P
+></P
+><UL
+><LI
+><P
+><A
+HREF="smb.conf.5.html#WINBINDSEPARATOR"
+TARGET="_top"
+> <TT
+CLASS="PARAMETER"
+><I
+>winbind separator</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="smb.conf.5.html#WINBINDUID"
+TARGET="_top"
+> <TT
+CLASS="PARAMETER"
+><I
+>winbind uid</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="smb.conf.5.html#WINBINDGID"
+TARGET="_top"
+> <TT
+CLASS="PARAMETER"
+><I
+>winbind gid</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="smb.conf.5.html#WINBINDCACHETIME"
+TARGET="_top"
+> <TT
+CLASS="PARAMETER"
+><I
+>winbind cache time</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="smb.conf.5.html#WINBINDENUMUSERS"
+TARGET="_top"
+> <TT
+CLASS="PARAMETER"
+><I
+>winbind enum users</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="smb.conf.5.html#WINBINDENUMGROUPS"
+TARGET="_top"
+> <TT
+CLASS="PARAMETER"
+><I
+>winbind enum groups</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="smb.conf.5.html#TEMPLATEHOMEDIR"
+TARGET="_top"
+> <TT
+CLASS="PARAMETER"
+><I
+>template homedir</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="smb.conf.5.html#TEMPLATESHELL"
+TARGET="_top"
+> <TT
+CLASS="PARAMETER"
+><I
+>template shell</I
+></TT
+></A
+></P
+></LI
+><LI
+><P
+><A
+HREF="smb.conf.5.html#WINBINDUSEDEFAULTDOMAIN"
+TARGET="_top"
+> <TT
+CLASS="PARAMETER"
+><I
+>winbind use default domain</I
+></TT
+></A
+></P
+></LI
+></UL
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN151"
+></A
+><H2
+>EXAMPLE SETUP</H2
+><P
+>To setup winbindd for user and group lookups plus
authentication from a domain controller use something like the
- following setup. This was tested on a RedHat 6.2 Linux box. </p><p>In <tt>/etc/nsswitch.conf</tt> put the
- following:
-</p><pre class="programlisting">
-passwd: files winbind
+ following setup. This was tested on a RedHat 6.2 Linux box. </P
+><P
+>In <TT
+CLASS="FILENAME"
+>/etc/nsswitch.conf</TT
+> put the
+ following:</P
+><P
+><TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><PRE
+CLASS="PROGRAMLISTING"
+>passwd: files winbind
group: files winbind
-</pre><p>In <tt>/etc/pam.d/*</tt> replace the <i><tt>
- auth</tt></i> lines with something like this:
-</p><pre class="programlisting">
-auth required /lib/security/pam_securetty.so
+ </PRE
+></TD
+></TR
+></TABLE
+></P
+><P
+>In <TT
+CLASS="FILENAME"
+>/etc/pam.d/*</TT
+> replace the
+ <TT
+CLASS="PARAMETER"
+><I
+>auth</I
+></TT
+> lines with something like this: </P
+><P
+><TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><PRE
+CLASS="PROGRAMLISTING"
+>auth required /lib/security/pam_securetty.so
auth required /lib/security/pam_nologin.so
auth sufficient /lib/security/pam_winbind.so
auth required /lib/security/pam_pwdb.so use_first_pass shadow nullok
-</pre><p>Note in particular the use of the <i><tt>sufficient
- </tt></i> keyword and the <i><tt>use_first_pass</tt></i> keyword. </p><p>Now replace the account lines with this: </p><p><b>account required /lib/security/pam_winbind.so
- </b></p><p>The next step is to join the domain. To do that use the
- <b>net</b> program like this: </p><p><b>net join -S PDC -U Administrator</b></p><p>The username after the <i><tt>-U</tt></i> can be any
+ </PRE
+></TD
+></TR
+></TABLE
+></P
+><P
+>Note in particular the use of the <TT
+CLASS="PARAMETER"
+><I
+>sufficient</I
+></TT
+>
+ keyword and the <TT
+CLASS="PARAMETER"
+><I
+>use_first_pass</I
+></TT
+> keyword. </P
+><P
+>Now replace the account lines with this: </P
+><P
+><B
+CLASS="COMMAND"
+>account required /lib/security/pam_winbind.so
+ </B
+></P
+><P
+>The next step is to join the domain. To do that use the
+ <B
+CLASS="COMMAND"
+>smbpasswd</B
+> program like this: </P
+><P
+><B
+CLASS="COMMAND"
+>smbpasswd -j DOMAIN -r PDC -U
+ Administrator</B
+></P
+><P
+>The username after the <TT
+CLASS="PARAMETER"
+><I
+>-U</I
+></TT
+> can be any
Domain user that has administrator privileges on the machine.
- Substitute the name or IP of your PDC for &quot;PDC&quot;.</p><p>Next copy <tt>libnss_winbind.so</tt> to
- <tt>/lib</tt> and <tt>pam_winbind.so
- </tt> to <tt>/lib/security</tt>. A symbolic link needs to be
- made from <tt>/lib/libnss_winbind.so</tt> to
- <tt>/lib/libnss_winbind.so.2</tt>. If you are using an
+ Substitute your domain name for "DOMAIN" and the name of your PDC
+ for "PDC".</P
+><P
+>Next copy <TT
+CLASS="FILENAME"
+>libnss_winbind.so</TT
+> to
+ <TT
+CLASS="FILENAME"
+>/lib</TT
+> and <TT
+CLASS="FILENAME"
+>pam_winbind.so</TT
+>
+ to <TT
+CLASS="FILENAME"
+>/lib/security</TT
+>. A symbolic link needs to be
+ made from <TT
+CLASS="FILENAME"
+>/lib/libnss_winbind.so</TT
+> to
+ <TT
+CLASS="FILENAME"
+>/lib/libnss_winbind.so.2</TT
+>. If you are using an
older version of glibc then the target of the link should be
- <tt>/lib/libnss_winbind.so.1</tt>.</p><p>Finally, setup a <a href="smb.conf.5.html">smb.conf(5)</a> containing directives like the
- following:
-</p><pre class="programlisting">
-[global]
+ <TT
+CLASS="FILENAME"
+>/lib/libnss_winbind.so.1</TT
+>.</P
+><P
+>Finally, setup a <TT
+CLASS="FILENAME"
+>smb.conf</TT
+> containing directives like the
+ following: </P
+><P
+><TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><PRE
+CLASS="PROGRAMLISTING"
+>[global]
winbind separator = +
winbind cache time = 10
template shell = /bin/bash
@@ -157,58 +648,274 @@ auth required /lib/security/pam_pwdb.so use_first_pass shadow nullok
workgroup = DOMAIN
security = domain
password server = *
-</pre><p>Now start winbindd and you should find that your user and
+ </PRE
+></TD
+></TR
+></TABLE
+></P
+><P
+>Now start winbindd and you should find that your user and
group database is expanded to include your NT users and groups,
and that you can login to your unix box as a domain user, using
the DOMAIN+user syntax for the username. You may wish to use the
- commands <b>getent passwd</b> and <b>getent group
- </b> to confirm the correct operation of winbindd.</p></div><div class="refsect1" lang="en"><h2>NOTES</h2><p>The following notes are useful when configuring and
- running <b>winbindd</b>: </p><p><a href="nmbd.8.html">nmbd(8)</a> must be running on the local machine
- for <b>winbindd</b> to work. <b>winbindd</b> queries
- the list of trusted domains for the Windows NT server
- on startup and when a SIGHUP is received. Thus, for a running <b>
- winbindd</b> to become aware of new trust relationships between
- servers, it must be sent a SIGHUP signal. </p><p>PAM is really easy to misconfigure. Make sure you know what
+ commands <B
+CLASS="COMMAND"
+>getent passwd</B
+> and <B
+CLASS="COMMAND"
+>getent group
+ </B
+> to confirm the correct operation of winbindd.</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN190"
+></A
+><H2
+>NOTES</H2
+><P
+>The following notes are useful when configuring and
+ running <B
+CLASS="COMMAND"
+>winbindd</B
+>: </P
+><P
+><B
+CLASS="COMMAND"
+>nmbd</B
+> must be running on the local machine
+ for <B
+CLASS="COMMAND"
+>winbindd</B
+> to work. <B
+CLASS="COMMAND"
+>winbindd</B
+>
+ queries the list of trusted domains for the Windows NT server
+ on startup and when a SIGHUP is received. Thus, for a running <B
+CLASS="COMMAND"
+> winbindd</B
+> to become aware of new trust relationships between
+ servers, it must be sent a SIGHUP signal. </P
+><P
+>Client processes resolving names through the <B
+CLASS="COMMAND"
+>winbindd</B
+>
+ nsswitch module read an environment variable named <TT
+CLASS="ENVAR"
+> $WINBINDD_DOMAIN</TT
+>. If this variable contains a comma separated
+ list of Windows NT domain names, then winbindd will only resolve users
+ and groups within those Windows NT domains. </P
+><P
+>PAM is really easy to misconfigure. Make sure you know what
you are doing when modifying PAM configuration files. It is possible
- to set up PAM such that you can no longer log into your system. </p><p>If more than one UNIX machine is running <b>winbindd</b>,
+ to set up PAM such that you can no longer log into your system. </P
+><P
+>If more than one UNIX machine is running <B
+CLASS="COMMAND"
+>winbindd</B
+>,
then in general the user and groups ids allocated by winbindd will not
be the same. The user and group ids will only be valid for the local
- machine.</p><p>If the the Windows NT RID to UNIX user and group id mapping
- file is damaged or destroyed then the mappings will be lost. </p></div><div class="refsect1" lang="en"><h2>SIGNALS</h2><p>The following signals can be used to manipulate the
- <b>winbindd</b> daemon. </p><div class="variablelist"><dl><dt><span class="term">SIGHUP</span></dt><dd><p>Reload the <a href="smb.conf.5.html">smb.conf(5)</a> file and
- apply any parameter changes to the running
+ machine.</P
+><P
+>If the the Windows NT RID to UNIX user and group id mapping
+ file is damaged or destroyed then the mappings will be lost. </P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN206"
+></A
+><H2
+>SIGNALS</H2
+><P
+>The following signals can be used to manipulate the
+ <B
+CLASS="COMMAND"
+>winbindd</B
+> daemon. </P
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>SIGHUP</DT
+><DD
+><P
+>Reload the <TT
+CLASS="FILENAME"
+>smb.conf(5)</TT
+>
+ file and apply any parameter changes to the running
version of winbindd. This signal also clears any cached
user and group information. The list of other domains trusted
- by winbindd is also reloaded. </p></dd><dt><span class="term">SIGUSR1</span></dt><dd><p>The SIGUSR1 signal will cause <b>
- winbindd</b> to write status information to the winbind
+ by winbindd is also reloaded. </P
+></DD
+><DT
+>SIGUSR1</DT
+><DD
+><P
+>The SIGUSR1 signal will cause <B
+CLASS="COMMAND"
+> winbindd</B
+> to write status information to the winbind
log file including information about the number of user and
- group ids allocated by <b>winbindd</b>.</p><p>Log files are stored in the filename specified by the
- log file parameter.</p></dd></dl></div></div><div class="refsect1" lang="en"><h2>FILES</h2><div class="variablelist"><dl><dt><span class="term"><tt>/etc/nsswitch.conf(5)</tt></span></dt><dd><p>Name service switch configuration file.</p></dd><dt><span class="term">/tmp/.winbindd/pipe</span></dt><dd><p>The UNIX pipe over which clients communicate with
- the <b>winbindd</b> program. For security reasons, the
+ group ids allocated by <B
+CLASS="COMMAND"
+>winbindd</B
+>.</P
+><P
+>Log files are stored in the filename specified by the
+ log file parameter.</P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN223"
+></A
+><H2
+>FILES</H2
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+><TT
+CLASS="FILENAME"
+>/etc/nsswitch.conf(5)</TT
+></DT
+><DD
+><P
+>Name service switch configuration file.</P
+></DD
+><DT
+>/tmp/.winbindd/pipe</DT
+><DD
+><P
+>The UNIX pipe over which clients communicate with
+ the <B
+CLASS="COMMAND"
+>winbindd</B
+> program. For security reasons, the
winbind client will only attempt to connect to the winbindd daemon
- if both the <tt>/tmp/.winbindd</tt> directory
- and <tt>/tmp/.winbindd/pipe</tt> file are owned by
- root. </p></dd><dt><span class="term">$LOCKDIR/winbindd_privilaged/pipe</span></dt><dd><p>The UNIX pipe over which 'privilaged' clients
- communicate with the <b>winbindd</b> program. For security
- reasons, access to some winbindd functions - like those needed by
- the <b>ntlm_auth</b> utility - is restricted. By default,
- only users in the 'root' group will get this access, however the administrator
- may change the group permissions on $LOCKDIR/winbindd_privilaged to allow
- programs like 'squid' to use ntlm_auth.
- Note that the winbind client will only attempt to connect to the winbindd daemon
- if both the <tt>$LOCKDIR/winbindd_privilaged</tt> directory
- and <tt>$LOCKDIR/winbindd_privilaged/pipe</tt> file are owned by
- root. </p></dd><dt><span class="term">/lib/libnss_winbind.so.X</span></dt><dd><p>Implementation of name service switch library.
- </p></dd><dt><span class="term">$LOCKDIR/winbindd_idmap.tdb</span></dt><dd><p>Storage for the Windows NT rid to UNIX user/group
+ if both the <TT
+CLASS="FILENAME"
+>/tmp/.winbindd</TT
+> directory
+ and <TT
+CLASS="FILENAME"
+>/tmp/.winbindd/pipe</TT
+> file are owned by
+ root. </P
+></DD
+><DT
+>/lib/libnss_winbind.so.X</DT
+><DD
+><P
+>Implementation of name service switch library.
+ </P
+></DD
+><DT
+>$LOCKDIR/winbindd_idmap.tdb</DT
+><DD
+><P
+>Storage for the Windows NT rid to UNIX user/group
id mapping. The lock directory is specified when Samba is initially
- compiled using the <i><tt>--with-lockdir</tt></i> option.
- This directory is by default <tt>/usr/local/samba/var/locks
- </tt>. </p></dd><dt><span class="term">$LOCKDIR/winbindd_cache.tdb</span></dt><dd><p>Storage for cached user and group information.
- </p></dd></dl></div></div><div class="refsect1" lang="en"><h2>VERSION</h2><p>This man page is correct for version 3.0 of
- the Samba suite.</p></div><div class="refsect1" lang="en"><h2>SEE ALSO</h2><p><tt>nsswitch.conf(5)</tt>, <a href="Samba.7.html">Samba(7)</a>, <a href="wbinfo.8.html">wbinfo(8)</a>, <a href="smb.conf.5.html">smb.conf(5)</a></p></div><div class="refsect1" lang="en"><h2>AUTHOR</h2><p>The original Samba software and related utilities
+ compiled using the <TT
+CLASS="PARAMETER"
+><I
+>--with-lockdir</I
+></TT
+> option.
+ This directory is by default <TT
+CLASS="FILENAME"
+>/usr/local/samba/var/locks
+ </TT
+>. </P
+></DD
+><DT
+>$LOCKDIR/winbindd_cache.tdb</DT
+><DD
+><P
+>Storage for cached user and group information.
+ </P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN252"
+></A
+><H2
+>VERSION</H2
+><P
+>This man page is correct for version 3.0 of
+ the Samba suite.</P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN255"
+></A
+><H2
+>SEE ALSO</H2
+><P
+><TT
+CLASS="FILENAME"
+>nsswitch.conf(5)</TT
+>,
+ <A
+HREF="samba.7.html"
+TARGET="_top"
+>samba(7)</A
+>,
+ <A
+HREF="wbinfo.1.html"
+TARGET="_top"
+>wbinfo(1)</A
+>,
+ <A
+HREF="smb.conf.5.html"
+TARGET="_top"
+>smb.conf(5)</A
+></P
+></DIV
+><DIV
+CLASS="REFSECT1"
+><A
+NAME="AEN262"
+></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><b>wbinfo</b> and <b>winbindd</b> were
- written by Tim Potter.</p><p>The conversion to DocBook for Samba 2.2 was done
- by Gerald Carter. The conversion to DocBook XML 4.2 for
- Samba 3.0 was done by Alexander Bokovoy.</p></div></div></body></html>
+ to the way the Linux kernel is developed.</P
+><P
+><B
+CLASS="COMMAND"
+>wbinfo</B
+> and <B
+CLASS="COMMAND"
+>winbindd</B
+>
+ were written by Tim Potter.</P
+><P
+>The conversion to DocBook for Samba 2.2 was done
+ by Gerald Carter</P
+></DIV
+></BODY
+></HTML
+> \ No newline at end of file
diff --git a/docs/manpages/findsmb.1 b/docs/manpages/findsmb.1
index bd9ba62b05..22362f8b6d 100644
--- a/docs/manpages/findsmb.1
+++ b/docs/manpages/findsmb.1
@@ -1,95 +1,100 @@
-.\"Generated by db2man.xsl. Don't modify this, modify the source.
-.de Sh \" Subsection
-.br
-.if t .Sp
-.ne 5
-.PP
-\fB\\$1\fR
-.PP
-..
-.de Sp \" Vertical space (when we can't use .PP)
-.if t .sp .5v
-.if n .sp
-..
-.de Ip \" List item
-.br
-.ie \\n(.$>=3 .ne \\$3
-.el .ne 3
-.IP "\\$1" \\$2
-..
-.TH "FINDSMB" 1 "" "" ""
+.\" This manpage has been automatically generated by docbook2man
+.\" from a DocBook document. This tool can be found at:
+.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
+.\" Please send any bug reports, improvements, comments, patches,
+.\" etc. to Steve Cheng <steve@ggi-project.org>.
+.TH "FINDSMB" "1" "04 March 2003" "" ""
.SH NAME
-findsmb \- list info about machines that respond to SMB name queries on a subnet
-.SH "SYNOPSIS"
+findsmb \- list info about machines that respond to SMB name queries on a subnet
+.SH SYNOPSIS
-.nf
-\fBfindsmb\fR [subnet broadcast address]
-.fi
+\fBfindsmb\fR [ \fBsubnet broadcast address\fR ]
.SH "DESCRIPTION"
-
.PP
-This perl script is part of the \fBSamba\fR(7) suite\&.
-
+This perl script is part of the Samba suite.
.PP
-\fBfindsmb\fR is a perl script that prints out several pieces of information about machines on a subnet that respond to SMB name query requests\&. It uses \fBnmblookup\fR(1) and \fBsmbclient\fR(1) to obtain this information\&.
-
+\fBfindsmb\fR is a perl script that
+prints out several pieces of information about machines
+on a subnet that respond to SMB name query requests.
+It uses \fB nmblookup(1)\fR to obtain this information.
.SH "OPTIONS"
-
.TP
--r
-Controls whether \fBfindsmb\fR takes bugs in Windows95 into account when trying to find a Netbios name registered of the remote machine\&. This option is disabled by default because it is specific to Windows 95 and Windows 95 machines only\&. If set, \fBnmblookup\fR(1) will be called with \fB-B\fR option\&.
-
-
+\fB-r\fR
+Controls whether \fBfindsmb\fR takes
+bugs in Windows95 into account when trying to find a Netbios name
+registered of the remote machine. This option is disabled by default
+because it is specific to Windows 95 and Windows 95 machines only.
+If set, \fBnmblookup\fR
+will be called with -B option.
.TP
-subnet broadcast address
-Without this option, \fBfindsmb \fR will probe the subnet of the machine where \fBfindsmb\fR(1) is run\&. This value is passed to \fBnmblookup\fR(1) as part of the \fB-B\fR option\&.
-
-
+\fBsubnet broadcast address\fR
+Without this option, \fBfindsmb
+\fR will probe the subnet of the machine where
+\fBfindsmb\fR is run. This value is passed
+to \fBnmblookup\fR as part of the
+-B option.
.SH "EXAMPLES"
-
.PP
-The output of \fBfindsmb\fR lists the following information for all machines that respond to the initial\fBnmblookup\fR for any name: IP address, NetBIOS name, Workgroup name, operating system, and SMB server version\&.
-
+The output of \fBfindsmb\fR lists the following
+information for all machines that respond to the initial
+\fBnmblookup\fR for any name: IP address, NetBIOS name,
+Workgroup name, operating system, and SMB server version.
.PP
-There will be a '+' in front of the workgroup name for machines that are local master browsers for that workgroup\&. There will be an '*' in front of the workgroup name for machines that are the domain master browser for that workgroup\&. Machines that are running Windows, Windows 95 or Windows 98 will not show any information about the operating system or server version\&.
-
+There will be a '+' in front of the workgroup name for
+machines that are local master browsers for that workgroup. There
+will be an '*' in front of the workgroup name for
+machines that are the domain master browser for that workgroup.
+Machines that are running Windows, Windows 95 or Windows 98 will
+not show any information about the operating system or server
+version.
.PP
-The command with \fB-r\fR option must be run on a system without \fBnmbd\fR(8)running\&. If \fBnmbd\fR is running on the system, you will only get the IP address and the DNS name of the machine\&. To get proper responses from Windows 95 and Windows 98 machines, the command must be run as root and with \fB-r\fR option on a machine without \fBnmbd\fR running\&.
-
+The command with -r option
+must be run on a system without \fBnmbd\fR running.
+If \fBnmbd\fR is running on the system, you will
+only get the IP address and the DNS name of the machine. To
+get proper responses from Windows 95 and Windows 98 machines,
+the command must be run as root and with -r
+option on a machine without \fBnmbd\fR running.
.PP
-For example, running \fBfindsmb\fR without \fB-r\fR option set would yield output similar to the following
-.nf
+For example, running \fBfindsmb\fR without
+-r option set would yield output similar
+to the following
+.nf
IP ADDR NETBIOS NAME WORKGROUP/OS/VERSION
---------------------------------------------------------------------
-192\&.168\&.35\&.10 MINESET-TEST1 [DMVENGR]
-192\&.168\&.35\&.55 LINUXBOX *[MYGROUP] [Unix] [Samba 2\&.0\&.6]
-192\&.168\&.35\&.56 HERBNT2 [HERB-NT]
-192\&.168\&.35\&.63 GANDALF [MVENGR] [Unix] [Samba 2\&.0\&.5a for IRIX]
-192\&.168\&.35\&.65 SAUNA [WORKGROUP] [Unix] [Samba 1\&.9\&.18p10]
-192\&.168\&.35\&.71 FROGSTAR [ENGR] [Unix] [Samba 2\&.0\&.0 for IRIX]
-192\&.168\&.35\&.78 HERBDHCP1 +[HERB]
-192\&.168\&.35\&.88 SCNT2 +[MVENGR] [Windows NT 4\&.0] [NT LAN Manager 4\&.0]
-192\&.168\&.35\&.93 FROGSTAR-PC [MVENGR] [Windows 5\&.0] [Windows 2000 LAN Manager]
-192\&.168\&.35\&.97 HERBNT1 *[HERB-NT] [Windows NT 4\&.0] [NT LAN Manager 4\&.0]
+192.168.35.10 MINESET-TEST1 [DMVENGR]
+192.168.35.55 LINUXBOX *[MYGROUP] [Unix] [Samba 2.0.6]
+192.168.35.56 HERBNT2 [HERB-NT]
+192.168.35.63 GANDALF [MVENGR] [Unix] [Samba 2.0.5a for IRIX]
+192.168.35.65 SAUNA [WORKGROUP] [Unix] [Samba 1.9.18p10]
+192.168.35.71 FROGSTAR [ENGR] [Unix] [Samba 2.0.0 for IRIX]
+192.168.35.78 HERBDHCP1 +[HERB]
+192.168.35.88 SCNT2 +[MVENGR] [Windows NT 4.0] [NT LAN Manager 4.0]
+192.168.35.93 FROGSTAR-PC [MVENGR] [Windows 5.0] [Windows 2000 LAN Manager]
+192.168.35.97 HERBNT1 *[HERB-NT] [Windows NT 4.0] [NT LAN Manager 4.0]
+
.fi
-
.SH "VERSION"
-
.PP
-This man page is correct for version 3\&.0 of the Samba suite\&.
-
+This man page is correct for version 3.0 of
+the Samba suite.
.SH "SEE ALSO"
-
.PP
-\fBnmbd\fR(8),\fBsmbclient\fR(1), and \fBnmblookup\fR(1)
-
+\fBnmbd(8)\fR
+\fBsmbclient(1)
+\fR and \fBnmblookup(1)\fR
.SH "AUTHOR"
-
.PP
-The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&.
-
+The original Samba software and related utilities
+were created by Andrew Tridgell. Samba is now developed
+by the Samba Team as an Open Source project similar
+to the way the Linux kernel is developed.
.PP
-The original Samba man pages were written by Karl Auer\&. The man page sources were converted to YODL format (another excellent piece of Open Source software, available at ftp://ftp\&.icce\&.rug\&.nl/pub/unix/) and updated for the Samba 2\&.0 release by Jeremy Allison\&. The conversion to DocBook for Samba 2\&.2 was done by Gerald Carter\&. The conversion to DocBook XML 4\&.2 for Samba 3\&.0 was done by Alexander Bokovoy\&.
-
+The original Samba man pages were written by Karl Auer.
+The man page sources were converted to YODL format (another
+excellent piece of Open Source software, available at
+ftp://ftp.icce.rug.nl/pub/unix/ <URL:ftp://ftp.icce.rug.nl/pub/unix/>) and updated for the Samba 2.0
+release by Jeremy Allison. The conversion to DocBook for
+Samba 2.2 was done by Gerald Carter
diff --git a/docs/manpages/lmhosts.5 b/docs/manpages/lmhosts.5
index 47bedda12a..82660f26bd 100644
--- a/docs/manpages/lmhosts.5
+++ b/docs/manpages/lmhosts.5
@@ -1,92 +1,86 @@
-.\"Generated by db2man.xsl. Don't modify this, modify the source.
-.de Sh \" Subsection
-.br
-.if t .Sp
-.ne 5
-.PP
-\fB\\$1\fR
-.PP
-..
-.de Sp \" Vertical space (when we can't use .PP)
-.if t .sp .5v
-.if n .sp
-..
-.de Ip \" List item
-.br
-.ie \\n(.$>=3 .ne \\$3
-.el .ne 3
-.IP "\\$1" \\$2
-..
-.TH "LMHOSTS" 5 "" "" ""
+.\" This manpage has been automatically generated by docbook2man
+.\" from a DocBook document. This tool can be found at:
+.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
+.\" Please send any bug reports, improvements, comments, patches,
+.\" etc. to Steve Cheng <steve@ggi-project.org>.
+.TH "LMHOSTS" "5" "04 March 2003" "" ""
.SH NAME
lmhosts \- The Samba NetBIOS hosts file
-.SH "SYNOPSIS"
-
+.SH SYNOPSIS
.PP
-\fIlmhosts\fR is the \fBSamba\fR(7) NetBIOS name to IP address mapping file\&.
-
+\fIlmhosts\fR is the Samba NetBIOS name to IP address mapping file.
.SH "DESCRIPTION"
-
.PP
-This file is part of the \fBSamba\fR(7) suite\&.
-
+This file is part of the Samba suite.
.PP
-\fIlmhosts\fR is the \fBSamba \fR NetBIOS name to IP address mapping file\&. It is very similar to the \fI/etc/hosts\fR file format, except that the hostname component must correspond to the NetBIOS naming format\&.
-
+\fIlmhosts\fR is the \fBSamba
+\fR NetBIOS name to IP address mapping file. It
+is very similar to the \fI/etc/hosts\fR file
+format, except that the hostname component must correspond
+to the NetBIOS naming format.
.SH "FILE FORMAT"
-
.PP
-It is an ASCII file containing one line for NetBIOS name\&. The two fields on each line are separated from each other by white space\&. Any entry beginning with '#' is ignored\&. Each line in the lmhosts file contains the following information:
-
-.TP 3
+It is an ASCII file containing one line for NetBIOS name.
+The two fields on each line are separated from each other by
+white space. Any entry beginning with '#' is ignored. Each line
+in the lmhosts file contains the following information :
+.TP 0.2i
\(bu
-IP Address - in dotted decimal format\&.
-
-.TP
+IP Address - in dotted decimal format.
+.TP 0.2i
\(bu
-NetBIOS Name - This name format is a maximum fifteen character host name, with an optional trailing '#' character followed by the NetBIOS name type as two hexadecimal digits\&.
-
-
-If the trailing '#' is omitted then the given IP address will be returned for all names that match the given name, whatever the NetBIOS name type in the lookup\&.
-
-.LP
-
+NetBIOS Name - This name format is a
+maximum fifteen character host name, with an optional
+trailing '#' character followed by the NetBIOS name type
+as two hexadecimal digits.
+
+If the trailing '#' is omitted then the given IP
+address will be returned for all names that match the given
+name, whatever the NetBIOS name type in the lookup.
+.PP
+An example follows :
.PP
-An example follows:
-.nf
+.nf
#
-# Sample Samba lmhosts file\&.
+# Sample Samba lmhosts file.
#
-192\&.9\&.200\&.1 TESTPC
-192\&.9\&.200\&.20 NTSERVER#20
-192\&.9\&.200\&.21 SAMBASERVER
- .fi
-
+192.9.200.1 TESTPC
+192.9.200.20 NTSERVER#20
+192.9.200.21 SAMBASERVER
+
+.fi
.PP
-Contains three IP to NetBIOS name mappings\&. The first and third will be returned for any queries for the names "TESTPC" and "SAMBASERVER" respectively, whatever the type component of the NetBIOS name requested\&.
-
+Contains three IP to NetBIOS name mappings. The first
+and third will be returned for any queries for the names "TESTPC"
+and "SAMBASERVER" respectively, whatever the type component of
+the NetBIOS name requested.
.PP
-The second mapping will be returned only when the "0x20" name type for a name "NTSERVER" is queried\&. Any other name type will not be resolved\&.
-
+The second mapping will be returned only when the "0x20" name
+type for a name "NTSERVER" is queried. Any other name type will not
+be resolved.
.PP
-The default location of the \fIlmhosts\fR file is in the same directory as the \fBsmb.conf\fR(5) file\&.
-
+The default location of the \fIlmhosts\fR file
+is in the same directory as the
+smb.conf(5)> file.
.SH "VERSION"
-
.PP
-This man page is correct for version 3\&.0 of the Samba suite\&.
-
+This man page is correct for version 2.2 of
+the Samba suite.
.SH "SEE ALSO"
-
.PP
-\fBsmbclient\fR(1), \fBsmb.conf\fR(5), and \fBsmbpasswd\fR(8)
-
+\fBsmbclient(1)
+\fR and \fB smbpasswd(8)\fR
.SH "AUTHOR"
-
.PP
-The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&.
-
+The original Samba software and related utilities
+were created by Andrew Tridgell. Samba is now developed
+by the Samba Team as an Open Source project similar
+to the way the Linux kernel is developed.
.PP
-The original Samba man pages were written by Karl Auer\&. The man page sources were converted to YODL format (another excellent piece of Open Source software, available atftp://ftp\&.icce\&.rug\&.nl/pub/unix/) and updated for the Samba 2\&.0 release by Jeremy Allison\&. The conversion to DocBook for Samba 2\&.2 was done by Gerald Carter\&. The conversion to DocBook XML 4\&.2 was done by Alexander Bokovoy\&.
-
+The original Samba man pages were written by Karl Auer.
+The man page sources were converted to YODL format (another
+excellent piece of Open Source software, available at
+ftp://ftp.icce.rug.nl/pub/unix/ <URL:ftp://ftp.icce.rug.nl/pub/unix/>) and updated for the Samba 2.0
+release by Jeremy Allison. The conversion to DocBook for
+Samba 2.2 was done by Gerald Carter
diff --git a/docs/manpages/net.8 b/docs/manpages/net.8
index d473503792..9b25d30c4f 100644
--- a/docs/manpages/net.8
+++ b/docs/manpages/net.8
@@ -1,549 +1,151 @@
-.\"Generated by db2man.xsl. Don't modify this, modify the source.
-.de Sh \" Subsection
-.br
-.if t .Sp
-.ne 5
-.PP
-\fB\\$1\fR
-.PP
-..
-.de Sp \" Vertical space (when we can't use .PP)
-.if t .sp .5v
-.if n .sp
-..
-.de Ip \" List item
-.br
-.ie \\n(.$>=3 .ne \\$3
-.el .ne 3
-.IP "\\$1" \\$2
-..
-.TH "NET" 8 "" "" ""
+.\" This manpage has been automatically generated by docbook2man
+.\" from a DocBook document. This tool can be found at:
+.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
+.\" Please send any bug reports, improvements, comments, patches,
+.\" etc. to Steve Cheng <steve@ggi-project.org>.
+.TH "NET" "8" "04 March 2003" "" ""
.SH NAME
net \- Tool for administration of Samba and remote CIFS servers.
-.SH "SYNOPSIS"
+.SH SYNOPSIS
-.nf
-\fBnet\fR {<ads|rap|rpc>} [-h] [-w workgroup] [-W myworkgroup] [-U user] [-I ip-address]
- [-p port] [-n myname] [-s conffile] [-S server] [-l] [-P] [-D debuglevel]
-
-.fi
+\fBnet\fR \fB<ads|rap|rpc>\fR [ \fB-h\fR ] [ \fB-w workgroup\fR ] [ \fB-W myworkgroup\fR ] [ \fB-U user\fR ] [ \fB-I ip-address\fR ] [ \fB-p port\fR ] [ \fB-n myname\fR ] [ \fB-s conffile\fR ] [ \fB-S server\fR ] [ \fB-C comment\fR ] [ \fB-M maxusers\fR ] [ \fB-F flags\fR ] [ \fB-j jobid\fR ] [ \fB-l\fR ] [ \fB-r\fR ] [ \fB-f\fR ] [ \fB-t timeout\fR ] [ \fB-P\fR ] [ \fB-D debuglevel\fR ]
.SH "DESCRIPTION"
-
.PP
-This tool is part of the \fBSamba\fR(7) suite\&.
-
+This tool is part of the Samba suite.
.PP
-The samba net utility is meant to work just like the net utility available for windows and DOS\&. The first argument should be used to specify the protocol to use when executing a certain command\&. ADS is used for ActiveDirectory, RAP is using for old (Win9x/NT3) clients and RPC can be used for NT4 and Windows 2000\&. If this argument is omitted, net will try to determine it automatically\&. Not all commands are available on all protocols\&.
-
+The samba net utility is meant to work just like the net utility
+available for windows and DOS.
.SH "OPTIONS"
-
.TP
--h|--help
-Print a summary of command line options\&.
-
-
+\fB-h\fR
+Display summary of all available options.
.TP
--w target-workgroup
-Sets target workgroup or domain\&. You have to specify either this option or the IP address or the name of a server\&.
-
-
+\fB-w target-workgroup\fR
+Sets target workgroup or domain. You have to specify either this option or the IP address or the name of a server.
.TP
--W workgroup
+\fB-W workgroup\fR
Sets client workgroup or domain
-
-
.TP
--U user
+\fB-U user\fR
User name to use
-
-
.TP
--I ip-address
-IP address of target server to use\&. You have to specify either this option or a target workgroup or a target server\&.
-
-
+\fB-I ip-address\fR
+IP address of target server to use. You have to specify either this option or a target workgroup or a target server.
.TP
--p port
-Port on the target server to connect to (usually 139 or 445)\&. Defaults to trying 445 first, then 139\&.
-
-
+\fB-p port\fR
+Port on the target server to connect to.
.TP
--n <primary NetBIOS name>
-This option allows you to override the NetBIOS name that Samba uses for itself\&. This is identical to setting the \fINetBIOS name\fR parameter in the \fBsmb.conf\fR(5) file\&. However, a command line setting will take precedence over settings in \fBsmb.conf\fR(5)\&.
-
-
+\fB-n myname\fR
+Sets name of the client.
.TP
--s <configuration file>
-The file specified contains the configuration details required by the server\&. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is to provide\&. See \fI smb\&.conf(5)\fR for more information\&. The default configuration file name is determined at compile time\&.
-
-
+\fB-s conffile\fR
+Specify alternative configuration file that should be loaded.
.TP
--S server
-Name of target server\&. You should specify either this option or a target workgroup or a target IP address\&.
-
-
+\fB-S server\fR
+Name of target server. You should specify either this option or a target workgroup or a target IP address.
.TP
--l
-When listing data, give more information on each item\&.
-
-
+\fB-C comment\fR
+FIXME
.TP
--P
-Make queries to the external server using the machine account of the local server\&.
-
-
+\fB-M maxusers\fR
+FIXME
.TP
--d|--debug=debuglevel
-\fIdebuglevel\fR is an integer from 0 to 10\&. The default value if this parameter is not specified is zero\&.
-
-
-The higher this value, the more detail will be logged to the log files about the activities of the server\&. At level 0, only critical errors and serious warnings will be logged\&. Level 1 is a reasonable level for day to day running - it generates a small amount of information about operations carried out\&.
-
-
-Levels above 1 will generate considerable amounts of log data, and should only be used when investigating a problem\&. Levels above 3 are designed for use only by developers and generate HUGE amounts of log data, most of which is extremely cryptic\&.
-
-
-Note that specifying this parameter here will override the log level parameter in the \fIsmb\&.conf(5)\fR file\&.
-
-
-.SH "COMMANDS"
-
-.SS "TIME"
-
-.PP
-The \fBNET TIME\fR command allows you to view the time on a remote server or synchronise the time on the local server with the time on the remote server\&.
-
-.PP
-Without any options, the \fBNET TIME\fR command displays the time on the remote server\&.
-
-.PP
-Displays the time on the remote server in a format ready for \fB/bin/date\fR
-
-.PP
-Tries to set the date and time of the local server to that on the remote server using \fB/bin/date\fR\&.
-
-.PP
-Displays the timezone in hours from GMT on the remote computer\&.
-
-.SS "[RPC|ADS] JOIN [TYPE] [-U username[%password]] [options]"
-
-.PP
-Join a domain\&. If the account already exists on the server, and [TYPE] is MEMBER, the machine will attempt to join automatically\&. (Assuming that the machine has been created in server manager) Otherwise, a password will be prompted for, and a new account may be created\&.
-
-.PP
-[TYPE] may be PDC, BDC or MEMBER to specify the type of server joining the domain\&.
-
-.SS "[RPC] OLDJOIN [options]"
-
-.PP
-Join a domain\&. Use the OLDJOIN option to join the domain using the old style of domain joining - you need to create a trust account in server manager first\&.
-
-.SS "[RPC|ADS] USER"
-
-.PP
-Delete specified user
-
-.PP
-List all users
-
-.PP
-List the domain groups of a the specified user\&.
-
-.PP
-Add specified user\&.
-
-.SS "[RPC|ADS] GROUP"
-
-.PP
-List user groups\&.
-
-.PP
-Delete specified group\&.
-
-.PP
-Create specified group\&.
-
-.SS "[RAP|RPC] SHARE"
-
-.PP
-Enumerates all exported resources (network shares) on target server\&.
-
-.PP
-Adds a share from a server (makes the export active)\&. Maxusers specifies the number of users that can be connected to the share simultaneously\&.
-
-.PP
-Delete specified share\&.
-
-.SS "[RPC|RAP] FILE"
-
-.PP
-List all open files on remote server\&.
-
-.PP
-Close file with specified \fIfileid\fR on remote server\&.
-
-.PP
-Print information on specified \fIfileid\fR\&. Currently listed are: file-id, username, locks, path, permissions\&.
-
-.RS
-.Sh "Note"
-
-.PP
-Currently NOT implemented\&.
-
-.RE
-
-.SS "SESSION"
-
-.PP
-Without any other options, SESSION enumerates all active SMB/CIFS sessions on the target server\&.
-
-.PP
-Close the specified sessions\&.
-
-.PP
-Give a list with all the open files in specified session\&.
-
-.SS "RAP SERVER DOMAIN"
-
-.PP
-List all servers in specified domain or workgroup\&. Defaults to local domain\&.
-
-.SS "RAP DOMAIN"
-
-.PP
-Lists all domains and workgroups visible on the current network\&.
-
-.SS "RAP PRINTQ"
-
-.PP
-Lists the specified print queue and print jobs on the server\&. If the \fIQUEUE_NAME\fR is omitted, all queues are listed\&.
-
-.PP
-Delete job with specified id\&.
-
-.SS "RAP VALIDATE user [password]"
-
-.PP
-Validate whether the specified user can log in to the remote server\&. If the password is not specified on the commandline, it will be prompted\&.
-
-.RS
-.Sh "Note"
-
-.PP
-Currently NOT implemented\&.
-
-.RE
-
-.SS "RAP GROUPMEMBER"
-
-.PP
-List all members of the specified group\&.
-
-.PP
-Delete member from group\&.
-
-.PP
-Add member to group\&.
-
-.SS "RAP ADMIN command"
-
-.PP
-Execute the specified \fIcommand\fR on the remote server\&. Only works with OS/2 servers\&.
-
-.RS
-.Sh "Note"
-
-.PP
-Currently NOT implemented\&.
-
-.RE
-
-.SS "RAP SERVICE"
-
-.PP
-Start the specified service on the remote server\&. Not implemented yet\&.
-
-.RS
-.Sh "Note"
-
-.PP
-Currently NOT implemented\&.
-
-.RE
-
-.PP
-Stop the specified service on the remote server\&.
-
-.RS
-.Sh "Note"
-
-.PP
-Currently NOT implemented\&.
-
-.RE
-
-.SS "RAP PASSWORD USER OLDPASS NEWPASS"
-
-.PP
-Change password of \fIUSER\fR from \fIOLDPASS\fR to \fINEWPASS\fR\&.
-
-.SS "LOOKUP"
-
-.PP
-Lookup the IP address of the given host with the specified type (netbios suffix)\&. The type defaults to 0x20 (workstation)\&.
-
-.PP
-Give IP address of LDAP server of specified \fIDOMAIN\fR\&. Defaults to local domain\&.
-
-.PP
-Give IP address of KDC for the specified \fIREALM\fR\&. Defaults to local realm\&.
-
-.PP
-Give IP's of Domain Controllers for specified \fI DOMAIN\fR\&. Defaults to local domain\&.
-
-.PP
-Give IP of master browser for specified \fIDOMAIN\fR or workgroup\&. Defaults to local domain\&.
-
-.SS "CACHE"
-
-.PP
-Samba uses a general caching interface called 'gencache'\&. It can be controlled using 'NET CACHE'\&.
-
-.PP
-All the timeout parameters support the suffixes: s - Secondsm - Minutesh - Hoursd - Daysw - Weeks
-
-.PP
-Add specified key+data to the cache with the given timeout\&.
-
-.PP
-Delete key from the cache\&.
-
-.PP
-Update data of existing cache entry\&.
-
-.PP
-Search for the specified pattern in the cache data\&.
-
-.PP
-List all current items in the cache\&.
-
-.PP
-Remove all the current items from the cache\&.
-
-.SS "GETLOCALSID [DOMAIN]"
-
-.PP
-Print the SID of the specified domain, or if the parameter is omitted, the SID of the domain the local server is in\&.
-
-.SS "SETLOCALSID S-1-5-21-x-y-z"
-
-.PP
-Sets domain sid for the local server to the specified SID\&.
-
-.SS "GROUPMAP"
-
-.PP
-Manage the mappings between Windows group SIDs and UNIX groups\&. Parameters take the for "parameter=value"\&. Common options include:
-
-.TP 3
-\(bu
-unixgroup - Name of the UNIX group
-
+\fB-F flags\fR
+FIXME
.TP
-\(bu
-ntgroup - Name of the Windows NT group (must be resolvable to a SID
-
+\fB-j jobid\fR
+FIXME
.TP
-\(bu
-rid - Unsigned 32-bit integer
-
+\fB-l\fR
+FIXME
.TP
-\(bu
-sid - Full SID in the form of "S-1-\&.\&.\&."
-
+\fB-r\fR
+FIXME
.TP
-\(bu
-type - Type of the group; either 'domain', 'local', or 'builtin'
-
+\fB-f\fR
+FIXME
.TP
-\(bu
-comment - Freeform text description of the group
-
-.LP
-
-.PP
-Add a new group mapping entry
-
-.PP
-net groupmap add {rid=int|sid=string} unixgroup=string [type={domain|local|builtin}] [ntgroup=string] [comment=string]
-
-.PP
-Delete a group mapping entry
-
-.PP
-net groupmap delete {ntgroup=string|sid=SID}
-
-.PP
-Update en existing group entry
-
-.PP
-net groupmap modify {ntgroup=string|sid=SID} [unixgroup=string] [comment=string] [type={domain|local}
-
-.PP
-List existing group mapping entries
-
-.PP
-net groupmap list [verbose] [ntgroup=string] [sid=SID]
-
-.SS "MAXRID"
-
-.PP
-Prints out the highest RID currently in use on the local server (by the active 'passdb backend')\&.
-
-.SS "RPC INFO"
-
-.PP
-Print information about the domain of the remote server, such as domain name, domain sid and number of users and groups\&.
-
-.SS "[RPC|ADS] TESTJOIN"
-
-.PP
-Check whether participation in a domain is still valid\&.
-
-.SS "[RPC|ADS] CHANGETRUSTPW"
-
-.PP
-Force change of domain trust password\&.
-
-.SS "RPC TRUSTDOM"
-
-.PP
-Add a interdomain trust account for \fIDOMAIN\fR to the remote server\&.
-
-.PP
-Remove interdomain trust account for \fIDOMAIN\fR from the remote server\&.
-
-.RS
-.Sh "Note"
-
-.PP
-Currently NOT implemented\&.
-
-.RE
-
-.PP
-Establish a trust relationship to a trusting domain\&. Interdomain account must already be created on the remote PDC\&.
-
-.PP
-Abandon relationship to trusted domain
-
-.PP
-List all current interdomain trust relationships\&.
-
-.SS "RPC ABORTSHUTDOWN"
-
-.PP
-Abort the shutdown of a remote server\&.
-
-.SS "SHUTDOWN [-t timeout] [-r] [-f] [-C message]"
-
+\fB-t timeout\fR
+FIXME
+.TP
+\fB-P\fR
+Make queries to the external server using the machine account of the local server.
+.TP
+\fB-D debuglevel\fR
+set the debuglevel. Debug level 0 is the lowest
+and 100 being the highest. This should be set to 100 if you are
+planning on submitting a bug report to the Samba team (see
+\fIBUGS.txt\fR).
+.SH "TIME"
.PP
-Shut down the remote server\&.
-
+The \fBNET TIME\fR command allows you to view the time on a remote server
+or synchronise the time on the local server with the time on the remote server.
.TP
--r
-Reboot after shutdown\&.
-
-
+\fB\fR
+Without any options, the \fBNET TIME\fR command
+displays the time on the remote server.
.TP
--f
-Force shutting down all applications\&.
-
-
+\fBSYSTEM\fR
+Displays the time on the remote server in a format ready for /bin/date
.TP
--t timeout
-Timeout before system will be shut down\&. An interactive user of the system can use this time to cancel the shutdown\&.
-
-
+\fBSET\fR
+Tries to set the date and time of the local server to that on
+the remote server using /bin/date.
.TP
--C message
-Display the specified message on the screen to announce the shutdown\&.
-
-
-.SS "SAMDUMP"
-
-.PP
-Print out sam database of remote server\&. You need to run this on either a BDC\&.
-
-.SS "VAMPIRE"
-
+\fBZONE\fR
+Displays the timezone in hours from GMT on the remote computer.
+.SH "RPC"
.PP
-Export users, aliases and groups from remote server to local server\&. Can only be run an a BDC\&.
-
-.SS "GETSID"
-
-.PP
-Fetch domain SID and store it in the local \fIsecrets\&.tdb\fR\&.
-
-.SS "ADS LEAVE"
-
-.PP
-Make the remote host leave the domain it is part of\&.
-
-.SS "ADS STATUS"
-
-.PP
-Print out status of machine account of the local machine in ADS\&. Prints out quite some debug info\&. Aimed at developers, regular users should use \fBNET ADS TESTJOIN\fR\&.
-
-.SS "ADS PRINTER"
-
-.PP
-Lookup info for \fIPRINTER\fR on \fISERVER\fR\&. The printer name defaults to "*", the server name defaults to the local host\&.
-
-.PP
-Publish specified printer using ADS\&.
-
-.PP
-Remove specified printer from ADS directory\&.
-
-.SS "ADS SEARCH EXPRESSION ATTRIBUTES..."
-
-.PP
-Perform a raw LDAP search on a ADS server and dump the results\&. The expression is a standard LDAP search expression, and the attributes are a list of LDAP fields to show in the results\&.
-
-.PP
-Example: \fBnet ads search '(objectCategory=group)' sAMAccountName\fR
-
-.SS "ADS DN DN (attributes)"
-
-.PP
-Perform a raw LDAP search on a ADS server and dump the results\&. The DN standard LDAP DN, and the attributes are a list of LDAP fields to show in the result\&.
-
-.PP
-Example: \fBnet ads dn 'CN=administrator,CN=Users,DC=my,DC=domain' SAMAccountName\fR
-
-.SS "WORKGROUP"
-
-.PP
-Print out workgroup name for specified kerberos realm\&.
-
-.SS "HELP [COMMAND]"
-
-.PP
-Gives usage information for the specified command\&.
-
+The \fBNET RPC\fR command allows you to do various
+NT4 operations.
+.TP
+\fBJOIN -U username[%password] [options]\fR
+Join a domain with specified username and password. Password
+will be prompted if none is specified.
+.TP
+\fBJOIN [options except -U]\fR
+to join a domain created in server manager
+.TP
+\fBUSER [misc. options] [targets]\fR
+List users
+.TP
+\fBUSER DELETE <name> [misc options]\fR
+delete specified user
+.TP
+\fBUSER INFO <name> [misc options]\fR
+list the domain groups of the specified user
+.TP
+\fBUSER ADD <name> [password] [-F user flags] [misc. options\fR
+Add specified user
+.TP
+\fBGROUP [misc options] [targets]\fR
+List user groups
+.TP
+\fBGROUP DELETE <name> [misc. options] [targets]\fR
+Delete specified group
+.TP
+\fBGROUP ADD <name> [-C comment]\fR
+Create specified group
+.TP
+\fBSHARE [misc. options] [targets]\fR
+enumerates all exported resources (network shares) on target server
+.TP
+\fBSHARE ADD <name=serverpath> [misc. options] [targets]\fR
+Adds a share from a server (makes the export active)
+.TP
+\fBSHARE DELETE <sharenam\fR
.SH "VERSION"
-
.PP
-This man page is complete for version 3\&.0 of the Samba suite\&.
-
+This man page is incomplete for version 3.0 of the Samba
+suite.
.SH "AUTHOR"
-
.PP
-The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&.
-
+The original Samba software and related utilities
+were created by Andrew Tridgell. Samba is now developed
+by the Samba Team as an Open Source project similar
+to the way the Linux kernel is developed.
.PP
-The net manpage was written by Jelmer Vernooij\&.
-
+The original Samba man pages were written by Karl Auer.
+The current set of manpages and documentation is maintained
+by the Samba Team in the same fashion as the Samba source code.
diff --git a/docs/manpages/nmbd.8 b/docs/manpages/nmbd.8
index 096876bfde..44a39c1730 100644
--- a/docs/manpages/nmbd.8
+++ b/docs/manpages/nmbd.8
@@ -1,178 +1,272 @@
-.\"Generated by db2man.xsl. Don't modify this, modify the source.
-.de Sh \" Subsection
-.br
-.if t .Sp
-.ne 5
-.PP
-\fB\\$1\fR
-.PP
-..
-.de Sp \" Vertical space (when we can't use .PP)
-.if t .sp .5v
-.if n .sp
-..
-.de Ip \" List item
-.br
-.ie \\n(.$>=3 .ne \\$3
-.el .ne 3
-.IP "\\$1" \\$2
-..
-.TH "NMBD" 8 "" "" ""
+.\" This manpage has been automatically generated by docbook2man
+.\" from a DocBook document. This tool can be found at:
+.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
+.\" Please send any bug reports, improvements, comments, patches,
+.\" etc. to Steve Cheng <steve@ggi-project.org>.
+.TH "NMBD" "8" "04 March 2003" "" ""
.SH NAME
-nmbd \- NetBIOS name server to provide NetBIOS over IP naming services to clients
-.SH "SYNOPSIS"
+nmbd \- NetBIOS name server to provide NetBIOS over IP naming services to clients
+.SH SYNOPSIS
-.nf
-\fBnmbd\fR [-D] [-F] [-S] [-a] [-i] [-o] [-h] [-V] [-d <debug level>] [-H <lmhosts file>] [-l <log directory>] [-n <primary netbios name>] [-p <port number>] [-s <configuration file>]
-
-.fi
+\fBnmbd\fR [ \fB-D\fR ] [ \fB-F\fR ] [ \fB-S\fR ] [ \fB-a\fR ] [ \fB-i\fR ] [ \fB-o\fR ] [ \fB-h\fR ] [ \fB-V\fR ] [ \fB-d <debug level>\fR ] [ \fB-H <lmhosts file>\fR ] [ \fB-l <log directory>\fR ] [ \fB-n <primary netbios name>\fR ] [ \fB-p <port number>\fR ] [ \fB-s <configuration file>\fR ]
.SH "DESCRIPTION"
-
.PP
-This program is part of the \fBSamba\fR(7) suite\&.
-
+This program is part of the Samba suite.
.PP
-\fBnmbd\fR is a server that understands and can reply to NetBIOS over IP name service requests, like those produced by SMB/CIFS clients such as Windows 95/98/ME, Windows NT, Windows 2000, Windows XP and LanManager clients\&. It also participates in the browsing protocols which make up the Windows "Network Neighborhood" view\&.
-
+\fBnmbd\fR is a server that understands
+and can reply to NetBIOS over IP name service requests, like
+those produced by SMB/CIFS clients such as Windows 95/98/ME,
+Windows NT, Windows 2000, Windows XP and LanManager clients. It also
+participates in the browsing protocols which make up the
+Windows "Network Neighborhood" view.
.PP
-SMB/CIFS clients, when they start up, may wish to locate an SMB/CIFS server\&. That is, they wish to know what IP number a specified host is using\&.
-
+SMB/CIFS clients, when they start up, may wish to
+locate an SMB/CIFS server. That is, they wish to know what
+IP number a specified host is using.
.PP
-Amongst other services, \fBnmbd\fR will listen for such requests, and if its own NetBIOS name is specified it will respond with the IP number of the host it is running on\&. Its "own NetBIOS name" is by default the primary DNS name of the host it is running on, but this can be overridden with the \fB-n\fR option (see OPTIONS below)\&. Thus \fBnmbd\fR will reply to broadcast queries for its own name(s)\&. Additional names for \fBnmbd\fR to respond on can be set via parameters in the \fBsmb.conf\fR(5) configuration file\&.
-
+Amongst other services, \fBnmbd\fR will
+listen for such requests, and if its own NetBIOS name is
+specified it will respond with the IP number of the host it
+is running on. Its "own NetBIOS name" is by
+default the primary DNS name of the host it is running on,
+but this can be overridden with the \fB-n\fR
+option (see OPTIONS below). Thus \fBnmbd\fR will
+reply to broadcast queries for its own name(s). Additional
+names for \fBnmbd\fR to respond on can be set
+via parameters in the \fI smb.conf(5)\fR configuration file.
.PP
-\fBnmbd\fR can also be used as a WINS (Windows Internet Name Server) server\&. What this basically means is that it will act as a WINS database server, creating a database from name registration requests that it receives and replying to queries from clients for these names\&.
-
+\fBnmbd\fR can also be used as a WINS
+(Windows Internet Name Server) server. What this basically means
+is that it will act as a WINS database server, creating a
+database from name registration requests that it receives and
+replying to queries from clients for these names.
.PP
-In addition, \fBnmbd\fR can act as a WINS proxy, relaying broadcast queries from clients that do not understand how to talk the WINS protocol to a WINS server\&.
-
+In addition, \fBnmbd\fR can act as a WINS
+proxy, relaying broadcast queries from clients that do
+not understand how to talk the WINS protocol to a WINS
+server.
.SH "OPTIONS"
-
.TP
--D
-If specified, this parameter causes \fBnmbd\fR to operate as a daemon\&. That is, it detaches itself and runs in the background, fielding requests on the appropriate port\&. By default, \fBnmbd\fR will operate as a daemon if launched from a command shell\&. nmbd can also be operated from the \fBinetd\fR meta-daemon, although this is not recommended\&.
-
-
+\fB-D\fR
+If specified, this parameter causes
+\fBnmbd\fR to operate as a daemon. That is,
+it detaches itself and runs in the background, fielding
+requests on the appropriate port. By default, \fBnmbd\fR
+will operate as a daemon if launched from a command shell.
+nmbd can also be operated from the \fBinetd\fR
+meta-daemon, although this is not recommended.
.TP
--F
-If specified, this parameter causes the main \fBnmbd\fR process to not daemonize, i\&.e\&. double-fork and disassociate with the terminal\&. Child processes are still created as normal to service each connection request, but the main process does not exit\&. This operation mode is suitable for running \fBnmbd\fR under process supervisors such as \fBsupervise\fR and \fBsvscan\fR from Daniel J\&. Bernstein's \fBdaemontools\fR package, or the AIX process monitor\&.
-
-
+\fB-F\fR
+If specified, this parameter causes
+the main \fBnmbd\fR process to not daemonize,
+i.e. double-fork and disassociate with the terminal.
+Child processes are still created as normal to service
+each connection request, but the main process does not
+exit. This operation mode is suitable for running
+\fBnmbd\fR under process supervisors such
+as \fBsupervise\fR and \fBsvscan\fR
+from Daniel J. Bernstein's \fBdaemontools\fR
+package, or the AIX process monitor.
.TP
--S
-If specified, this parameter causes \fBnmbd\fR to log to standard output rather than a file\&.
-
-
+\fB-S\fR
+If specified, this parameter causes
+\fBnmbd\fR to log to standard output rather
+than a file.
.TP
--i
-If this parameter is specified it causes the server to run "interactively", not as a daemon, even if the server is executed on the command line of a shell\&. Setting this parameter negates the implicit daemon mode when run from the command line\&. \fBnmbd\fR also logs to standard output, as if the \fB-S\fR parameter had been given\&.
-
-
+\fB-a\fR
+If this parameter is specified, each new
+connection will append log messages to the log file.
+This is the default.
.TP
--h|--help
-Print a summary of command line options\&.
-
-
+\fB-i\fR
+If this parameter is specified it causes the
+server to run "interactively", not as a daemon, even if the
+server is executed on the command line of a shell. Setting this
+parameter negates the implicit daemon mode when run from the
+command line. \fBnmbd\fR also logs to standard
+output, as if the \fB-S\fR parameter had been
+given.
.TP
--H <filename>
-NetBIOS lmhosts file\&. The lmhosts file is a list of NetBIOS names to IP addresses that is loaded by the nmbd server and used via the name resolution mechanism \fIname resolve order\fR described in \fBsmb.conf\fR(5) to resolve any NetBIOS name queries needed by the server\&. Note that the contents of this file are \fBNOT\fR used by \fBnmbd\fR to answer any name queries\&. Adding a line to this file affects name NetBIOS resolution from this host \fBONLY\fR\&.
-
-
-The default path to this file is compiled into Samba as part of the build process\&. Common defaults are \fI/usr/local/samba/lib/lmhosts\fR, \fI/usr/samba/lib/lmhosts\fR or \fI/etc/samba/lmhosts\fR\&. See the \fBlmhosts\fR(5) man page for details on the contents of this file\&.
-
-
+\fB-o\fR
+If this parameter is specified, the
+log files will be overwritten when opened. By default,
+\fBsmbd\fR will append entries to the log
+files.
.TP
--V
-Prints the version number for \fBsmbd\fR\&.
-
-
+\fB-h\fR
+Prints the help information (usage)
+for \fBnmbd\fR.
.TP
--s <configuration file>
-The file specified contains the configuration details required by the server\&. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is to provide\&. See \fI smb\&.conf(5)\fR for more information\&. The default configuration file name is determined at compile time\&.
-
-
+\fB-H <filename>\fR
+NetBIOS lmhosts file. The lmhosts
+file is a list of NetBIOS names to IP addresses that
+is loaded by the nmbd server and used via the name
+resolution mechanism name resolve order described in \fIsmb.conf(5)\fR
+to resolve any NetBIOS name queries needed by the server. Note
+that the contents of this file are \fBNOT\fR
+used by \fBnmbd\fR to answer any name queries.
+Adding a line to this file affects name NetBIOS resolution
+from this host \fBONLY\fR.
+
+The default path to this file is compiled into
+Samba as part of the build process. Common defaults
+are \fI/usr/local/samba/lib/lmhosts\fR,
+\fI/usr/samba/lib/lmhosts\fR or
+\fI/etc/lmhosts\fR. See the
+\fIlmhosts(5)\fR
+man page for details on the contents of this file.
.TP
--d|--debug=debuglevel
-\fIdebuglevel\fR is an integer from 0 to 10\&. The default value if this parameter is not specified is zero\&.
-
-
-The higher this value, the more detail will be logged to the log files about the activities of the server\&. At level 0, only critical errors and serious warnings will be logged\&. Level 1 is a reasonable level for day to day running - it generates a small amount of information about operations carried out\&.
-
-
-Levels above 1 will generate considerable amounts of log data, and should only be used when investigating a problem\&. Levels above 3 are designed for use only by developers and generate HUGE amounts of log data, most of which is extremely cryptic\&.
-
-
-Note that specifying this parameter here will override the log level parameter in the \fIsmb\&.conf(5)\fR file\&.
-
-
+\fB-V\fR
+Prints the version number for
+\fBnmbd\fR.
.TP
--l|--logfile=logbasename
-File name for log/debug files\&. The extension \fB"\&.client"\fR will be appended\&. The log file is never removed by the client\&.
-
-
+\fB-d <debug level>\fR
+debuglevel is an integer
+from 0 to 10. The default value if this parameter is
+not specified is zero.
+
+The higher this value, the more detail will
+be logged to the log files about the activities of the
+server. At level 0, only critical errors and serious
+warnings will be logged. Level 1 is a reasonable level for
+day to day running - it generates a small amount of
+information about operations carried out.
+
+Levels above 1 will generate considerable amounts
+of log data, and should only be used when investigating
+a problem. Levels above 3 are designed for use only by developers
+and generate HUGE amounts of log data, most of which is extremely
+cryptic.
+
+Note that specifying this parameter here will override
+the log level
+parameter in the \fI smb.conf(5)\fR file.
.TP
--p <UDP port number>
-UDP port number is a positive integer value\&. This option changes the default UDP port number (normally 137) that \fBnmbd\fR responds to name queries on\&. Don't use this option unless you are an expert, in which case you won't need help!
-
+\fB-l <log directory>\fR
+The -l parameter specifies a directory
+into which the "log.nmbd" log file will be created
+for operational data from the running \fBnmbd\fR
+server. The default log directory is compiled into Samba
+as part of the build process. Common defaults are \fI /usr/local/samba/var/log.nmb\fR, \fI /usr/samba/var/log.nmb\fR or
+\fI/var/log/log.nmb\fR. \fBBeware:\fR
+If the directory specified does not exist, \fBnmbd\fR
+will log to the default debug log location defined at compile time.
+.TP
+\fB-n <primary NetBIOS name>\fR
+This option allows you to override
+the NetBIOS name that Samba uses for itself. This is identical
+to setting the NetBIOS name parameter in the
+\fIsmb.conf\fR file. However, a command
+line setting will take precedence over settings in
+\fIsmb.conf\fR.
+.TP
+\fB-p <UDP port number>\fR
+UDP port number is a positive integer value.
+This option changes the default UDP port number (normally 137)
+that \fBnmbd\fR responds to name queries on. Don't
+use this option unless you are an expert, in which case you
+won't need help!
+.TP
+\fB-s <configuration file>\fR
+The default configuration file name
+is set at build time, typically as \fI /usr/local/samba/lib/smb.conf\fR, but
+this may be changed when Samba is autoconfigured.
+The file specified contains the configuration details
+required by the server. See \fIsmb.conf(5)\fR for more information.
.SH "FILES"
-
.TP
-\fI/etc/inetd\&.conf\fR
-If the server is to be run by the \fBinetd\fR meta-daemon, this file must contain suitable startup information for the meta-daemon\&. See the install document for details\&.
-
-
+\fB\fI/etc/inetd.conf\fB\fR
+If the server is to be run by the
+\fBinetd\fR meta-daemon, this file
+must contain suitable startup information for the
+meta-daemon. See the UNIX_INSTALL.html document
+for details.
.TP
-\fI/etc/rc\fR
-or whatever initialization script your system uses)\&.
-
-
-If running the server as a daemon at startup, this file will need to contain an appropriate startup sequence for the server\&. See the "How to Install and Test SAMBA" document for details\&.
-
-
+\fB\fI/etc/rc\fB\fR
+or whatever initialization script your
+system uses).
+
+If running the server as a daemon at startup,
+this file will need to contain an appropriate startup
+sequence for the server. See the UNIX_INSTALL.html document
+for details.
.TP
-\fI/etc/services\fR
-If running the server via the meta-daemon \fBinetd\fR, this file must contain a mapping of service name (e\&.g\&., netbios-ssn) to service port (e\&.g\&., 139) and protocol type (e\&.g\&., tcp)\&. See the "How to Install and Test SAMBA" document for details\&.
-
-
+\fB\fI/etc/services\fB\fR
+If running the server via the
+meta-daemon \fBinetd\fR, this file
+must contain a mapping of service name (e.g., netbios-ssn)
+to service port (e.g., 139) and protocol type (e.g., tcp).
+See the UNIX_INSTALL.html
+document for details.
.TP
-\fI/usr/local/samba/lib/smb\&.conf\fR
-This is the default location of the \fBsmb.conf\fR(5) server configuration file\&. Other common places that systems install this file are \fI/usr/samba/lib/smb\&.conf\fR and \fI/etc/samba/smb\&.conf\fR\&.
-
-
-When run as a WINS server (see the \fBwins support\fR parameter in the \fBsmb.conf\fR(5) man page), \fBnmbd\fR will store the WINS database in the file \fIwins\&.dat\fR in the \fIvar/locks\fR directory configured under wherever Samba was configured to install itself\&.
-
-
-If \fBnmbd\fR is acting as a \fB browse master\fR (see the \fBlocal master\fR parameter in the \fBsmb.conf\fR(5) man page, \fBnmbd\fR will store the browsing database in the file \fIbrowse\&.dat \fR in the \fIvar/locks\fR directory configured under wherever Samba was configured to install itself\&.
-
-
+\fB\fI/usr/local/samba/lib/smb.conf\fB\fR
+This is the default location of the
+\fIsmb.conf\fR
+server configuration file. Other common places that systems
+install this file are \fI/usr/samba/lib/smb.conf\fR
+and \fI/etc/smb.conf\fR.
+
+When run as a WINS server (see the
+wins support
+parameter in the \fIsmb.conf(5)\fR man page),
+\fBnmbd\fR
+will store the WINS database in the file \fIwins.dat\fR
+in the \fIvar/locks\fR directory configured under
+wherever Samba was configured to install itself.
+
+If \fBnmbd\fR is acting as a \fB browse master\fR (see the local master
+parameter in the \fIsmb.conf(5)\fR man page,
+\fBnmbd\fR
+will store the browsing database in the file \fIbrowse.dat
+\fR in the \fIvar/locks\fR directory
+configured under wherever Samba was configured to install itself.
.SH "SIGNALS"
-
.PP
-To shut down an \fBnmbd\fR process it is recommended that SIGKILL (-9) \fBNOT\fR be used, except as a last resort, as this may leave the name database in an inconsistent state\&. The correct way to terminate \fBnmbd\fR is to send it a SIGTERM (-15) signal and wait for it to die on its own\&.
-
+To shut down an \fBnmbd\fR process it is recommended
+that SIGKILL (-9) \fBNOT\fR be used, except as a last
+resort, as this may leave the name database in an inconsistent state.
+The correct way to terminate \fBnmbd\fR is to send it
+a SIGTERM (-15) signal and wait for it to die on its own.
.PP
-\fBnmbd\fR will accept SIGHUP, which will cause it to dump out its namelists into the file \fInamelist\&.debug \fR in the \fI/usr/local/samba/var/locks\fR directory (or the \fIvar/locks\fR directory configured under wherever Samba was configured to install itself)\&. This will also cause \fBnmbd\fR to dump out its server database in the \fIlog\&.nmb\fR file\&.
-
+\fBnmbd\fR will accept SIGHUP, which will cause
+it to dump out its namelists into the file \fInamelist.debug
+\fR in the \fI/usr/local/samba/var/locks\fR
+directory (or the \fIvar/locks\fR directory configured
+under wherever Samba was configured to install itself). This will also
+cause \fBnmbd\fR to dump out its server database in
+the \fIlog.nmb\fR file.
.PP
-The debug log level of nmbd may be raised or lowered using \fBsmbcontrol\fR(1) (SIGUSR[1|2] signals are no longer used since Samba 2\&.2)\&. This is to allow transient problems to be diagnosed, whilst still running at a normally low log level\&.
-
+The debug log level of nmbd may be raised or lowered using
+\fBsmbcontrol(1)\fR
+ (SIGUSR[1|2] signals are no longer used in Samba 2.2). This is
+to allow transient problems to be diagnosed, whilst still running
+at a normally low log level.
.SH "VERSION"
-
.PP
-This man page is correct for version 3\&.0 of the Samba suite\&.
-
+This man page is correct for version 3.0 of
+the Samba suite.
.SH "SEE ALSO"
-
.PP
-\fBinetd\fR(8), \fBsmbd\fR(8), \fBsmb.conf\fR(5), \fBsmbclient\fR(1), \fBtestparm\fR(1), \fBtestprns\fR(1), and the Internet RFC's \fIrfc1001\&.txt\fR, \fIrfc1002\&.txt\fR\&. In addition the CIFS (formerly SMB) specification is available as a link from the Web page http://samba\&.org/cifs/\&.
-
+\fBinetd(8)\fR, \fBsmbd(8)\fR
+\fIsmb.conf(5)\fR
+ \fBsmbclient(1)
+\fR and the Internet RFC's
+\fIrfc1001.txt\fR, \fIrfc1002.txt\fR.
+In addition the CIFS (formerly SMB) specification is available
+as a link from the Web page
+http://samba.org/cifs/ <URL:http://samba.org/cifs/>.
.SH "AUTHOR"
-
.PP
-The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&.
-
+The original Samba software and related utilities
+were created by Andrew Tridgell. Samba is now developed
+by the Samba Team as an Open Source project similar
+to the way the Linux kernel is developed.
.PP
-The original Samba man pages were written by Karl Auer\&. The man page sources were converted to YODL format (another excellent piece of Open Source software, available at ftp://ftp\&.icce\&.rug\&.nl/pub/unix/) and updated for the Samba 2\&.0 release by Jeremy Allison\&. The conversion to DocBook for Samba 2\&.2 was done by Gerald Carter\&. The conversion to DocBook XML 4\&.2 for Samba 3\&.0 was done by Alexander Bokovoy\&.
-
+The original Samba man pages were written by Karl Auer.
+The man page sources were converted to YODL format (another
+excellent piece of Open Source software, available at
+ftp://ftp.icce.rug.nl/pub/unix/ <URL:ftp://ftp.icce.rug.nl/pub/unix/>) and updated for the Samba 2.0
+release by Jeremy Allison. The conversion to DocBook for
+Samba 2.2 was done by Gerald Carter
diff --git a/docs/manpages/nmblookup.1 b/docs/manpages/nmblookup.1
index 2f16025593..06e608a62e 100644
--- a/docs/manpages/nmblookup.1
+++ b/docs/manpages/nmblookup.1
@@ -1,185 +1,160 @@
-.\"Generated by db2man.xsl. Don't modify this, modify the source.
-.de Sh \" Subsection
-.br
-.if t .Sp
-.ne 5
-.PP
-\fB\\$1\fR
-.PP
-..
-.de Sp \" Vertical space (when we can't use .PP)
-.if t .sp .5v
-.if n .sp
-..
-.de Ip \" List item
-.br
-.ie \\n(.$>=3 .ne \\$3
-.el .ne 3
-.IP "\\$1" \\$2
-..
-.TH "NMBLOOKUP" 1 "" "" ""
+.\" This manpage has been automatically generated by docbook2man
+.\" from a DocBook document. This tool can be found at:
+.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
+.\" Please send any bug reports, improvements, comments, patches,
+.\" etc. to Steve Cheng <steve@ggi-project.org>.
+.TH "NMBLOOKUP" "1" "04 March 2003" "" ""
.SH NAME
-nmblookup \- NetBIOS over TCP/IP client used to lookup NetBIOS names
-.SH "SYNOPSIS"
+nmblookup \- NetBIOS over TCP/IP client used to lookup NetBIOS names
+.SH SYNOPSIS
-.nf
-\fBnmblookup\fR [-M] [-R] [-S] [-r] [-A] [-h] [-B <broadcast address>] [-U <unicast
- address>] [-d <debug level>] [-s <smb config file>] [-i <NetBIOS scope>]
- [-T] [-f] {name}
-.fi
+\fBnmblookup\fR [ \fB-M\fR ] [ \fB-R\fR ] [ \fB-S\fR ] [ \fB-r\fR ] [ \fB-A\fR ] [ \fB-h\fR ] [ \fB-B <broadcast address>\fR ] [ \fB-U <unicast address>\fR ] [ \fB-d <debug level>\fR ] [ \fB-s <smb config file>\fR ] [ \fB-i <NetBIOS scope>\fR ] [ \fB-T\fR ] [ \fB-f\fR ] \fBname\fR
.SH "DESCRIPTION"
-
.PP
-This tool is part of the \fBSamba\fR(7) suite\&.
-
+This tool is part of the Samba suite.
.PP
-\fBnmblookup\fR is used to query NetBIOS names and map them to IP addresses in a network using NetBIOS over TCP/IP queries\&. The options allow the name queries to be directed at a particular IP broadcast area or to a particular machine\&. All queries are done over UDP\&.
-
+\fBnmblookup\fR is used to query NetBIOS names
+and map them to IP addresses in a network using NetBIOS over TCP/IP
+queries. The options allow the name queries to be directed at a
+particular IP broadcast area or to a particular machine. All queries
+are done over UDP.
.SH "OPTIONS"
-
-.TP
--M
-Searches for a master browser by looking up the NetBIOS name \fIname\fR with a type of \fB0x1d\fR\&. If \fI name\fR is "-" then it does a lookup on the special name \fB__MSBROWSE__\fR\&. Please note that in order to use the name "-", you need to make sure "-" isn't parsed as an argument, e\&.g\&. use : \fBnmblookup -M -- -\fR\&.
-
-
-.TP
--R
-Set the recursion desired bit in the packet to do a recursive lookup\&. This is used when sending a name query to a machine running a WINS server and the user wishes to query the names in the WINS server\&. If this bit is unset the normal (broadcast responding) NetBIOS processing code on a machine is used instead\&. See RFC1001, RFC1002 for details\&.
-
-
-.TP
--S
-Once the name query has returned an IP address then do a node status query as well\&. A node status query returns the NetBIOS names registered by a host\&.
-
-
.TP
--r
-Try and bind to UDP port 137 to send and receive UDP datagrams\&. The reason for this option is a bug in Windows 95 where it ignores the source port of the requesting packet and only replies to UDP port 137\&. Unfortunately, on most UNIX systems root privilege is needed to bind to this port, and in addition, if the \fBnmbd\fR(8) daemon is running on this machine it also binds to this port\&.
-
-
-.TP
--A
-Interpret \fIname\fR as an IP Address and do a node status query on this address\&.
-
-
-.TP
--n <primary NetBIOS name>
-This option allows you to override the NetBIOS name that Samba uses for itself\&. This is identical to setting the \fINetBIOS name\fR parameter in the \fBsmb.conf\fR(5) file\&. However, a command line setting will take precedence over settings in \fBsmb.conf\fR(5)\&.
-
-
-.TP
--i <scope>
-This specifies a NetBIOS scope that \fBnmblookup\fR will use to communicate with when generating NetBIOS names\&. For details on the use of NetBIOS scopes, see rfc1001\&.txt and rfc1002\&.txt\&. NetBIOS scopes are \fBvery\fR rarely used, only set this parameter if you are the system administrator in charge of all the NetBIOS systems you communicate with\&.
-
-
-.TP
--W|--workgroup=domain
-Set the SMB domain of the username\&. This overrides the default domain which is the domain defined in smb\&.conf\&. If the domain specified is the same as the servers NetBIOS name, it causes the client to log on using the servers local SAM (as opposed to the Domain SAM)\&.
-
-
-.TP
--O socket options
-TCP socket options to set on the client socket\&. See the socket options parameter in the \fBsmb.conf\fR(5) manual page for the list of valid options\&.
-
-
-.TP
--h|--help
-Print a summary of command line options\&.
-
-
-.TP
--B <broadcast address>
-Send the query to the given broadcast address\&. Without this option the default behavior of nmblookup is to send the query to the broadcast address of the network interfaces as either auto-detected or defined in the \fIinterfaces\fR parameter of the \fBsmb.conf\fR(5) file\&.
-
-
-.TP
--U <unicast address>
-Do a unicast query to the specified address or host \fIunicast address\fR\&. This option (along with the \fI-R\fR option) is needed to query a WINS server\&.
-
-
-.TP
--V
-Prints the version number for \fBsmbd\fR\&.
-
-
-.TP
--s <configuration file>
-The file specified contains the configuration details required by the server\&. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is to provide\&. See \fI smb\&.conf(5)\fR for more information\&. The default configuration file name is determined at compile time\&.
-
-
-.TP
--d|--debug=debuglevel
-\fIdebuglevel\fR is an integer from 0 to 10\&. The default value if this parameter is not specified is zero\&.
-
-
-The higher this value, the more detail will be logged to the log files about the activities of the server\&. At level 0, only critical errors and serious warnings will be logged\&. Level 1 is a reasonable level for day to day running - it generates a small amount of information about operations carried out\&.
-
-
-Levels above 1 will generate considerable amounts of log data, and should only be used when investigating a problem\&. Levels above 3 are designed for use only by developers and generate HUGE amounts of log data, most of which is extremely cryptic\&.
-
-
-Note that specifying this parameter here will override the log level parameter in the \fIsmb\&.conf(5)\fR file\&.
-
-
-.TP
--l|--logfile=logbasename
-File name for log/debug files\&. The extension \fB"\&.client"\fR will be appended\&. The log file is never removed by the client\&.
-
-
-.TP
--T
-This causes any IP addresses found in the lookup to be looked up via a reverse DNS lookup into a DNS name, and printed out before each
-
-
-\fBIP address \&.\&.\&.\&. NetBIOS name\fR
-
-
-pair that is the normal output\&.
-
-
-.TP
--f
-Show which flags apply to the name that has been looked up\&. Possible answers are zero or more of: Response, Authoritative, Truncated, Recursion_Desired, Recursion_Available, Broadcast\&.
-
-
-.TP
-name
-This is the NetBIOS name being queried\&. Depending upon the previous options this may be a NetBIOS name or IP address\&. If a NetBIOS name then the different name types may be specified by appending '#<type>' to the name\&. This name may also be '*', which will return all registered names within a broadcast area\&.
-
-
+\fB-M\fR
+Searches for a master browser by looking
+up the NetBIOS name \fIname\fR with a
+type of 0x1d. If \fI name\fR is "-" then it does a lookup on the special name
+__MSBROWSE__.
+.TP
+\fB-R\fR
+Set the recursion desired bit in the packet
+to do a recursive lookup. This is used when sending a name
+query to a machine running a WINS server and the user wishes
+to query the names in the WINS server. If this bit is unset
+the normal (broadcast responding) NetBIOS processing code
+on a machine is used instead. See rfc1001, rfc1002 for details.
+.TP
+\fB-S\fR
+Once the name query has returned an IP
+address then do a node status query as well. A node status
+query returns the NetBIOS names registered by a host.
+.TP
+\fB-r\fR
+Try and bind to UDP port 137 to send and receive UDP
+datagrams. The reason for this option is a bug in Windows 95
+where it ignores the source port of the requesting packet
+and only replies to UDP port 137. Unfortunately, on most UNIX
+systems root privilege is needed to bind to this port, and
+in addition, if the nmbd(8)
+daemon is running on this machine it also binds to this port.
+.TP
+\fB-A\fR
+Interpret \fIname\fR as
+an IP Address and do a node status query on this address.
+.TP
+\fB-h\fR
+Print a help (usage) message.
+.TP
+\fB-B <broadcast address>\fR
+Send the query to the given broadcast address. Without
+this option the default behavior of nmblookup is to send the
+query to the broadcast address of the network interfaces as
+either auto-detected or defined in the \fIinterfaces\fR
+ parameter of the \fIsmb.conf (5)\fR file.
+.TP
+\fB-U <unicast address>\fR
+Do a unicast query to the specified address or
+host \fIunicast address\fR. This option
+(along with the \fI-R\fR option) is needed to
+query a WINS server.
+.TP
+\fB-d <debuglevel>\fR
+debuglevel is an integer from 0 to 10.
+
+The default value if this parameter is not specified
+is zero.
+
+The higher this value, the more detail will be logged
+about the activities of \fBnmblookup\fR. At level
+0, only critical errors and serious warnings will be logged.
+
+Levels above 1 will generate considerable amounts of
+log data, and should only be used when investigating a problem.
+Levels above 3 are designed for use only by developers and
+generate HUGE amounts of data, most of which is extremely cryptic.
+
+Note that specifying this parameter here will override
+the \fI log level\fR parameter in the \fI smb.conf(5)\fR file.
+.TP
+\fB-s <smb.conf>\fR
+This parameter specifies the pathname to
+the Samba configuration file, smb.conf(5) This file controls all aspects of
+the Samba setup on the machine.
+.TP
+\fB-i <scope>\fR
+This specifies a NetBIOS scope that
+\fBnmblookup\fR will use to communicate with when
+generating NetBIOS names. For details on the use of NetBIOS
+scopes, see rfc1001.txt and rfc1002.txt. NetBIOS scopes are
+\fBvery\fR rarely used, only set this parameter
+if you are the system administrator in charge of all the
+NetBIOS systems you communicate with.
+.TP
+\fB-T\fR
+This causes any IP addresses found in the
+lookup to be looked up via a reverse DNS lookup into a
+DNS name, and printed out before each
+
+\fBIP address .... NetBIOS name\fR
+
+pair that is the normal output.
+.TP
+\fB-f\fR
+Show which flags apply to the name that has been looked up. Possible
+answers are zero or more of: Response, Authoritative,
+Truncated, Recursion_Desired, Recursion_Available, Broadcast.
+.TP
+\fBname\fR
+This is the NetBIOS name being queried. Depending
+upon the previous options this may be a NetBIOS name or IP address.
+If a NetBIOS name then the different name types may be specified
+by appending '#<type>' to the name. This name may also be
+\&'*', which will return all registered names within a broadcast
+area.
.SH "EXAMPLES"
-
.PP
-\fBnmblookup\fR can be used to query a WINS server (in the same way \fBnslookup\fR is used to query DNS servers)\&. To query a WINS server, \fBnmblookup\fR must be called like this:
-
+\fBnmblookup\fR can be used to query
+a WINS server (in the same way \fBnslookup\fR is
+used to query DNS servers). To query a WINS server,
+\fBnmblookup\fR must be called like this:
.PP
\fBnmblookup -U server -R 'name'\fR
-
.PP
For example, running :
-
.PP
\fBnmblookup -U samba.org -R 'IRIX#1B'\fR
-
.PP
-would query the WINS server samba\&.org for the domain master browser (1B name type) for the IRIX workgroup\&.
-
+would query the WINS server samba.org for the domain
+master browser (1B name type) for the IRIX workgroup.
.SH "VERSION"
-
.PP
-This man page is correct for version 3\&.0 of the Samba suite\&.
-
+This man page is correct for version 3.0 of
+the Samba suite.
.SH "SEE ALSO"
-
.PP
-\fBnmbd\fR(8), \fBsamba\fR(7), and \fBsmb.conf\fR(5)\&.
-
+\fBnmbd(8)\fR
+samba(7) and smb.conf(5)
.SH "AUTHOR"
-
.PP
-The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&.
-
+The original Samba software and related utilities
+were created by Andrew Tridgell. Samba is now developed
+by the Samba Team as an Open Source project similar
+to the way the Linux kernel is developed.
.PP
-The original Samba man pages were written by Karl Auer\&. The man page sources were converted to YODL format (another excellent piece of Open Source software, available at ftp://ftp\&.icce\&.rug\&.nl/pub/unix/) and updated for the Samba 2\&.0 release by Jeremy Allison\&. The conversion to DocBook for Samba 2\&.2 was done by Gerald Carter\&. The conversion to DocBook XML 4\&.2 for Samba 3\&.0 was done by Alexander Bokovoy\&.
-
+The original Samba man pages were written by Karl Auer.
+The man page sources were converted to YODL format (another
+excellent piece of Open Source software, available at
+ftp://ftp.icce.rug.nl/pub/unix/ <URL:ftp://ftp.icce.rug.nl/pub/unix/>) and updated for the Samba 2.0
+release by Jeremy Allison. The conversion to DocBook for
+Samba 2.2 was done by Gerald Carter
diff --git a/docs/manpages/pdbedit.8 b/docs/manpages/pdbedit.8
index 51dcf44bf0..82765d6dad 100644
--- a/docs/manpages/pdbedit.8
+++ b/docs/manpages/pdbedit.8
@@ -1,313 +1,279 @@
-.\"Generated by db2man.xsl. Don't modify this, modify the source.
-.de Sh \" Subsection
-.br
-.if t .Sp
-.ne 5
-.PP
-\fB\\$1\fR
-.PP
-..
-.de Sp \" Vertical space (when we can't use .PP)
-.if t .sp .5v
-.if n .sp
-..
-.de Ip \" List item
-.br
-.ie \\n(.$>=3 .ne \\$3
-.el .ne 3
-.IP "\\$1" \\$2
-..
-.TH "PDBEDIT" 8 "" "" ""
+.\" This manpage has been automatically generated by docbook2man
+.\" from a DocBook document. This tool can be found at:
+.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
+.\" Please send any bug reports, improvements, comments, patches,
+.\" etc. to Steve Cheng <steve@ggi-project.org>.
+.TH "PDBEDIT" "8" "30 March 2003" "" ""
.SH NAME
pdbedit \- manage the SAM database
-.SH "SYNOPSIS"
+.SH SYNOPSIS
-.nf
-\fBpdbedit\fR [-l] [-v] [-w] [-u username] [-f fullname] [-h homedir] [-D drive] [-S
- script] [-p profile] [-a] [-m] [-x] [-i passdb-backend] [-e passdb-backend]
- [-g] [-b passdb-backend] [-g] [-d debuglevel] [-s configfile] [-P account-policy]
- [-C value]
-.fi
+\fBpdbedit\fR [ \fB-l\fR ] [ \fB-v\fR ] [ \fB-w\fR ] [ \fB-u username\fR ] [ \fB-f fullname\fR ] [ \fB-h homedir\fR ] [ \fB-D drive\fR ] [ \fB-S script\fR ] [ \fB-p profile\fR ] [ \fB-a\fR ] [ \fB-m\fR ] [ \fB-x\fR ] [ \fB-i passdb-backend\fR ] [ \fB-e passdb-backend\fR ] [ \fB-g\fR ] [ \fB-b passdb-backend\fR ] [ \fB-d debuglevel\fR ] [ \fB-s configfile\fR ] [ \fB-P account-policy\fR ] [ \fB-V value\fR ]
.SH "DESCRIPTION"
-
.PP
-This tool is part of the \fBSamba\fR(7) suite\&.
-
+This tool is part of the Samba suite.
.PP
-The pdbedit program is used to manage the users accounts stored in the sam database and can only be run by root\&.
-
+The pdbedit program is used to manage the users accounts
+stored in the sam database and can only be run by root.
.PP
-The pdbedit tool uses the passdb modular interface and is independent from the kind of users database used (currently there are smbpasswd, ldap, nis+ and tdb based and more can be added without changing the tool)\&.
-
+The pdbedit tool uses the passdb modular interface and is
+independent from the kind of users database used (currently there
+are smbpasswd, ldap, nis+ and tdb based and more can be added
+without changing the tool).
.PP
-There are five main ways to use pdbedit: adding a user account, removing a user account, modifing a user account, listing user accounts, importing users accounts\&.
-
+There are five main ways to use pdbedit: adding a user account,
+removing a user account, modifing a user account, listing user
+accounts, importing users accounts.
.SH "OPTIONS"
-
.TP
--l
-This option lists all the user accounts present in the users database\&. This option prints a list of user/uid pairs separated by the ':' character\&.
-
+\fB-l\fR
+This option lists all the user accounts
+present in the users database.
+This option prints a list of user/uid pairs separated by
+the ':' character.
Example: \fBpdbedit -l\fR
.nf
-
-sorce:500:Simo Sorce
-samba:45:Test User
+ sorce:500:Simo Sorce
+ samba:45:Test User
+
.fi
-
-
.TP
--v
-This option enables the verbose listing format\&. It causes pdbedit to list the users in the database, printing out the account fields in a descriptive format\&.
-
+\fB-v\fR
+This option enables the verbose listing format.
+It causes pdbedit to list the users in the database, printing
+out the account fields in a descriptive format.
Example: \fBpdbedit -l -v\fR
.nf
-
----------------
-username: sorce
-user ID/Group: 500/500
-user RID/GRID: 2000/2001
-Full Name: Simo Sorce
-Home Directory: \\\\BERSERKER\\sorce
-HomeDir Drive: H:
-Logon Script: \\\\BERSERKER\\netlogon\\sorce\&.bat
-Profile Path: \\\\BERSERKER\\profile
----------------
-username: samba
-user ID/Group: 45/45
-user RID/GRID: 1090/1091
-Full Name: Test User
-Home Directory: \\\\BERSERKER\\samba
-HomeDir Drive:
-Logon Script:
-Profile Path: \\\\BERSERKER\\profile
+ ---------------
+ username: sorce
+ user ID/Group: 500/500
+ user RID/GRID: 2000/2001
+ Full Name: Simo Sorce
+ Home Directory: \\\\BERSERKER\\sorce
+ HomeDir Drive: H:
+ Logon Script: \\\\BERSERKER\\netlogon\\sorce.bat
+ Profile Path: \\\\BERSERKER\\profile
+ ---------------
+ username: samba
+ user ID/Group: 45/45
+ user RID/GRID: 1090/1091
+ Full Name: Test User
+ Home Directory: \\\\BERSERKER\\samba
+ HomeDir Drive:
+ Logon Script:
+ Profile Path: \\\\BERSERKER\\profile
+
.fi
-
-
.TP
--w
-This option sets the "smbpasswd" listing format\&. It will make pdbedit list the users in the database, printing out the account fields in a format compatible with the \fIsmbpasswd\fR file format\&. (see the \fBsmbpasswd\fR(5) for details)
-
+\fB-w\fR
+This option sets the "smbpasswd" listing format.
+It will make pdbedit list the users in the database, printing
+out the account fields in a format compatible with the
+\fIsmbpasswd\fR file format. (see the \fIsmbpasswd(5)\fR for details)
Example: \fBpdbedit -l -w\fR
-sorce:500:508818B733CE64BEAAD3B435B51404EE:D2A2418EFC466A8A0F6B1DBB5C3DB80C:[UX ]:LCT-00000000:
-samba:45:0F2B255F7B67A7A9AAD3B435B51404EE:BC281CE3F53B6A5146629CD4751D3490:[UX ]:LCT-3BFA1E8D:
-
+.nf
+ sorce:500:508818B733CE64BEAAD3B435B51404EE:D2A2418EFC466A8A0F6B1DBB5C3DB80C:[UX ]:LCT-00000000:
+ samba:45:0F2B255F7B67A7A9AAD3B435B51404EE:BC281CE3F53B6A5146629CD4751D3490:[UX ]:LCT-3BFA1E8D:
+
+.fi
.TP
--u username
-This option specifies the username to be used for the operation requested (listing, adding, removing)\&. It is \fBrequired\fR in add, remove and modify operations and \fBoptional\fR in list operations\&.
-
-
+\fB-u username\fR
+This option specifies the username to be
+used for the operation requested (listing, adding, removing).
+It is \fBrequired\fR in add, remove and modify
+operations and \fBoptional\fR in list
+operations.
.TP
--f fullname
-This option can be used while adding or modifing a user account\&. It will specify the user's full name\&.
-
+\fB-f fullname\fR
+This option can be used while adding or
+modifing a user account. It will specify the user's full
+name.
Example: \fB-f "Simo Sorce"\fR
-
-
.TP
--h homedir
-This option can be used while adding or modifing a user account\&. It will specify the user's home directory network path\&.
-
-
-Example: \fB-h "\\\\BERSERKER\\sorce"\fR
-
+\fB-h homedir\fR
+This option can be used while adding or
+modifing a user account. It will specify the user's home
+directory network path.
+Example: \fB-h "\\\\\\\\BERSERKER\\\\sorce"\fR
.TP
--D drive
-This option can be used while adding or modifing a user account\&. It will specify the windows drive letter to be used to map the home directory\&.
-
+\fB-D drive\fR
+This option can be used while adding or
+modifing a user account. It will specify the windows drive
+letter to be used to map the home directory.
Example: \fB-d "H:"\fR
-
-
.TP
--S script
-This option can be used while adding or modifing a user account\&. It will specify the user's logon script path\&.
-
-
-Example: \fB-s "\\\\BERSERKER\\netlogon\\sorce.bat"\fR
-
+\fB-S script\fR
+This option can be used while adding or
+modifing a user account. It will specify the user's logon
+script path.
+Example: \fB-s "\\\\\\\\BERSERKER\\\\netlogon\\\\sorce.bat"\fR
.TP
--p profile
-This option can be used while adding or modifing a user account\&. It will specify the user's profile directory\&.
-
-
-Example: \fB-p "\\\\BERSERKER\\netlogon"\fR
-
+\fB-p profile\fR
+This option can be used while adding or
+modifing a user account. It will specify the user's profile
+directory.
+Example: \fB-p "\\\\\\\\BERSERKER\\\\netlogon"\fR
.TP
--a
-This option is used to add a user into the database\&. This command needs a user name specified with the -u switch\&. When adding a new user, pdbedit will also ask for the password to be used\&.
-
+\fB-a\fR
+This option is used to add a user into the
+database. This command needs a user name specified with
+the -u switch. When adding a new user, pdbedit will also
+ask for the password to be used.
Example: \fBpdbedit -a -u sorce\fR
+
.nf
new password:
-retype new password
+ retype new password
.fi
-
-
-
.TP
--m
-This option may only be used in conjunction with the \fI-a\fR option\&. It will make pdbedit to add a machine trust account instead of a user account (-u username will provide the machine name)\&.
-
+\fB-m\fR
+This option may only be used in conjunction
+with the \fI-a\fR option. It will make
+pdbedit to add a machine trust account instead of a user
+account (-u username will provide the machine name).
Example: \fBpdbedit -a -m -u w2k-wks\fR
-
-
.TP
--x
-This option causes pdbedit to delete an account from the database\&. It needs a username specified with the -u switch\&.
-
+\fB-x\fR
+This option causes pdbedit to delete an account
+from the database. It needs a username specified with the
+-u switch.
Example: \fBpdbedit -x -u bob\fR
-
-
.TP
--i passdb-backend
-Use a different passdb backend to retrieve users than the one specified in smb\&.conf\&. Can be used to import data into your local user database\&.
-
-
-This option will ease migration from one passdb backend to another\&.
-
-
-Example: \fBpdbedit -i smbpasswd:/etc/smbpasswd.old \fR
+\fB-i passdb-backend\fR
+Use a different passdb backend to retrieve users
+than the one specified in smb.conf. Can be used to import data into
+your local user database.
+This option will ease migration from one passdb backend to
+another.
+Example: \fBpdbedit -i smbpasswd:/etc/smbpasswd.old
+\fR
.TP
--e passdb-backend
-Exports all currently available users to the specified password database backend\&.
-
-
-This option will ease migration from one passdb backend to another and will ease backing up\&.
+\fB-e passdb-backend\fR
+Exports all currently available users to the
+specified password database backend.
+This option will ease migration from one passdb backend to
+another and will ease backing up.
Example: \fBpdbedit -e smbpasswd:/root/samba-users.backup\fR
-
-
.TP
--g
-If you specify \fI-g\fR, then \fI-i in-backend -e out-backend\fR applies to the group mapping instead of the user database\&.
-
-
-This option will ease migration from one passdb backend to another and will ease backing up\&.
-
-
-.TP
--g
-If you specify \fI-g\fR, then \fI-i in-backend -e out-backend\fR applies to the group mapping instead of the user database\&.
-
-
-This option will ease migration from one passdb backend to another and will ease backing up\&.
-
+\fB-g\fR
+If you specify \fI-g\fR,
+then \fI-i in-backend -e out-backend\fR
+applies to the group mapping instead of the user database.
+This option will ease migration from one passdb backend to
+another and will ease backing up.
.TP
--b passdb-backend
-Use a different default passdb backend\&.
-
+\fB-b passdb-backend\fR
+Use a different default passdb backend.
Example: \fBpdbedit -b xml:/root/pdb-backup.xml -l\fR
-
-
.TP
--P account-policy
+\fB-P account-policy\fR
Display an account policy
-
-Valid policies are: minimum password age, reset count minutes, disconnect time, user must logon to change password, password history, lockout duration, min password length, maximum password age and bad lockout attempt\&.
-
+Valid policies are: minimum password age, reset count minutes, disconnect time,
+user must logon to change password, password history, lockout duration, min password length,
+maximum password age and bad lockout attempt.
Example: \fBpdbedit -P "bad lockout attempt"\fR
.nf
-
-account policy value for bad lockout attempt is 0
+ account policy value for bad lockout attempt is 0
+
.fi
-
-
.TP
--C account-policy-value
-Sets an account policy to a specified value\&. This option may only be used in conjunction with the \fI-P\fR option\&.
-
+\fB-V account-policy-value\fR
+Sets an account policy to a specified value.
+This option may only be used in conjunction
+with the \fI-P\fR option.
-Example: \fBpdbedit -P "bad lockout attempt" -C 3\fR
+Example: \fBpdbedit -P "bad lockout attempt" -V 3\fR
.nf
-
-account policy value for bad lockout attempt was 0
-account policy value for bad lockout attempt is now 3
+ account policy value for bad lockout attempt was 0
+ account policy value for bad lockout attempt is now 3
+
.fi
-
-
-.TP
--h|--help
-Print a summary of command line options\&.
-
-
.TP
--V
-Prints the version number for \fBsmbd\fR\&.
-
-
-.TP
--s <configuration file>
-The file specified contains the configuration details required by the server\&. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is to provide\&. See \fI smb\&.conf(5)\fR for more information\&. The default configuration file name is determined at compile time\&.
-
-
+\fB-d|--debug=debuglevel\fR
+\fIdebuglevel\fR is an integer
+from 0 to 10. The default value if this parameter is
+not specified is zero.
+
+The higher this value, the more detail will be
+logged to the log files about the activities of the
+server. At level 0, only critical errors and serious
+warnings will be logged. Level 1 is a reasonable level for
+day to day running - it generates a small amount of
+information about operations carried out.
+
+Levels above 1 will generate considerable
+amounts of log data, and should only be used when
+investigating a problem. Levels above 3 are designed for
+use only by developers and generate HUGE amounts of log
+data, most of which is extremely cryptic.
+
+Note that specifying this parameter here will
+override the log
+level file.
.TP
--d|--debug=debuglevel
-\fIdebuglevel\fR is an integer from 0 to 10\&. The default value if this parameter is not specified is zero\&.
-
-
-The higher this value, the more detail will be logged to the log files about the activities of the server\&. At level 0, only critical errors and serious warnings will be logged\&. Level 1 is a reasonable level for day to day running - it generates a small amount of information about operations carried out\&.
-
-
-Levels above 1 will generate considerable amounts of log data, and should only be used when investigating a problem\&. Levels above 3 are designed for use only by developers and generate HUGE amounts of log data, most of which is extremely cryptic\&.
-
-
-Note that specifying this parameter here will override the log level parameter in the \fIsmb\&.conf(5)\fR file\&.
-
-
+\fB-h|--help\fR
+Print a summary of command line options.
.TP
--l|--logfile=logbasename
-File name for log/debug files\&. The extension \fB"\&.client"\fR will be appended\&. The log file is never removed by the client\&.
-
-
+\fB-s <configuration file>\fR
+The file specified contains the
+configuration details required by the server. The
+information in this file includes server-specific
+information such as what printcap file to use, as well
+as descriptions of all the services that the server is
+to provide. See \fIsmb.conf(5)\fR for more information.
+The default configuration file name is determined at
+compile time.
.SH "NOTES"
-
.PP
-This command may be used only by root\&.
-
+This command may be used only by root.
.SH "VERSION"
-
.PP
-This man page is correct for version 2\&.2 of the Samba suite\&.
-
+This man page is correct for version 2.2 of
+the Samba suite.
.SH "SEE ALSO"
-
.PP
-\fBsmbpasswd\fR(5), \fBsamba\fR(7)
-
+smbpasswd(8)
+samba(7)
.SH "AUTHOR"
-
.PP
-The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&.
-
+The original Samba software and related utilities
+were created by Andrew Tridgell. Samba is now developed
+by the Samba Team as an Open Source project similar
+to the way the Linux kernel is developed.
.PP
-The original Samba man pages were written by Karl Auer\&. The man page sources were converted to YODL format (another excellent piece of Open Source software, available at ftp://ftp\&.icce\&.rug\&.nl/pub/unix/) and updated for the Samba 2\&.0 release by Jeremy Allison\&. The conversion to DocBook for Samba 2\&.2 was done by Gerald Carter\&. The conversion to DocBook XML 4\&.2 for Samba 3\&.0 was done by Alexander Bokovoy\&.
-
+The original Samba man pages were written by Karl Auer.
+The man page sources were converted to YODL format (another
+excellent piece of Open Source software, available at
+ftp://ftp.icce.rug.nl/pub/unix/ <URL:ftp://ftp.icce.rug.nl/pub/unix/>) and updated for the Samba 2.0
+release by Jeremy Allison. The conversion to DocBook for
+Samba 2.2 was done by Gerald Carter
diff --git a/docs/manpages/rpcclient.1 b/docs/manpages/rpcclient.1
index 7655d6c312..dcba30100b 100644
--- a/docs/manpages/rpcclient.1
+++ b/docs/manpages/rpcclient.1
@@ -1,616 +1,358 @@
-.\"Generated by db2man.xsl. Don't modify this, modify the source.
-.de Sh \" Subsection
-.br
-.if t .Sp
-.ne 5
-.PP
-\fB\\$1\fR
-.PP
-..
-.de Sp \" Vertical space (when we can't use .PP)
-.if t .sp .5v
-.if n .sp
-..
-.de Ip \" List item
-.br
-.ie \\n(.$>=3 .ne \\$3
-.el .ne 3
-.IP "\\$1" \\$2
-..
-.TH "RPCCLIENT" 1 "" "" ""
+.\" This manpage has been automatically generated by docbook2man
+.\" from a DocBook document. This tool can be found at:
+.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
+.\" Please send any bug reports, improvements, comments, patches,
+.\" etc. to Steve Cheng <steve@ggi-project.org>.
+.TH "RPCCLIENT" "1" "04 March 2003" "" ""
.SH NAME
-rpcclient \- tool for executing client side MS-RPC functions
-.SH "SYNOPSIS"
+rpcclient \- tool for executing client side MS-RPC functions
+.SH SYNOPSIS
-.nf
-\fBrpcclient\fR [-A authfile] [-c <command string>] [-d debuglevel] [-h] [-l logfile]
- [-N] [-s <smb config file>] [-U username[%password]] [-W workgroup]
- [-N] [-I destinationIP] {server}
-.fi
+\fBrpcclient\fR [ \fB-A authfile\fR ] [ \fB-c <command string>\fR ] [ \fB-d debuglevel\fR ] [ \fB-h\fR ] [ \fB-l logfile\fR ] [ \fB-N\fR ] [ \fB-s <smb config file>\fR ] [ \fB-U username[%password]\fR ] [ \fB-W workgroup\fR ] [ \fB-N\fR ] [ \fB-I destinationIP\fR ] \fBserver\fR
.SH "DESCRIPTION"
-
.PP
-This tool is part of the \fBSamba\fR(7) suite\&.
-
+This tool is part of the Samba suite.
.PP
-\fBrpcclient\fR is a utility initially developed to test MS-RPC functionality in Samba itself\&. It has undergone several stages of development and stability\&. Many system administrators have now written scripts around it to manage Windows NT clients from their UNIX workstation\&.
-
+\fBrpcclient\fR is a utility initially developed
+to test MS-RPC functionality in Samba itself. It has undergone
+several stages of development and stability. Many system administrators
+have now written scripts around it to manage Windows NT clients from
+their UNIX workstation.
.SH "OPTIONS"
-
-.TP
-server
-NetBIOS name of Server to which to connect\&. The server can be any SMB/CIFS server\&. The name is resolved using the \fIname resolve order\fR line from \fBsmb.conf\fR(5)\&.
-
-
.TP
--c|--command='command string'
-execute semicolon separated commands (listed below))
-
-
-.TP
--I IP-address
-\fIIP address\fR is the address of the server to connect to\&. It should be specified in standard "a\&.b\&.c\&.d" notation\&.
-
-
-Normally the client would attempt to locate a named SMB/CIFS server by looking it up via the NetBIOS name resolution mechanism described above in the \fIname resolve order\fR parameter above\&. Using this parameter will force the client to assume that the server is on the machine with the specified IP address and the NetBIOS name component of the resource being connected to will be ignored\&.
-
-
-There is no default for this parameter\&. If not supplied, it will be determined automatically by the client as described above\&.
-
-
-.TP
--V
-Prints the version number for \fBsmbd\fR\&.
-
-
-.TP
--s <configuration file>
-The file specified contains the configuration details required by the server\&. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is to provide\&. See \fI smb\&.conf(5)\fR for more information\&. The default configuration file name is determined at compile time\&.
-
-
-.TP
--d|--debug=debuglevel
-\fIdebuglevel\fR is an integer from 0 to 10\&. The default value if this parameter is not specified is zero\&.
-
-
-The higher this value, the more detail will be logged to the log files about the activities of the server\&. At level 0, only critical errors and serious warnings will be logged\&. Level 1 is a reasonable level for day to day running - it generates a small amount of information about operations carried out\&.
-
-
-Levels above 1 will generate considerable amounts of log data, and should only be used when investigating a problem\&. Levels above 3 are designed for use only by developers and generate HUGE amounts of log data, most of which is extremely cryptic\&.
-
-
-Note that specifying this parameter here will override the log level parameter in the \fIsmb\&.conf(5)\fR file\&.
-
-
-.TP
--l|--logfile=logbasename
-File name for log/debug files\&. The extension \fB"\&.client"\fR will be appended\&. The log file is never removed by the client\&.
-
-
-.TP
--N
-If specified, this parameter suppresses the normal password prompt from the client to the user\&. This is useful when accessing a service that does not require a password\&.
-
-
-Unless a password is specified on the command line or this parameter is specified, the client will request a password\&.
-
-
+\fBserver\fR
+NetBIOS name of Server to which to connect.
+The server can be any SMB/CIFS server. The name is
+resolved using the \fIname resolve order\fR line from
+\fIsmb.conf(5)\fR.
.TP
--k
-Try to authenticate with kerberos\&. Only useful in an Active Directory environment\&.
-
-
-.TP
--A|--authfile=filename
-This option allows you to specify a file from which to read the username and password used in the connection\&. The format of the file is
+\fB-A|--authfile=filename\fR
+This option allows
+you to specify a file from which to read the username and
+password used in the connection. The format of the file is
.nf
-
-username = <value>
-password = <value>
-domain = <value>
+ username = <value>
+ password = <value>
+ domain = <value>
+
.fi
-
-Make certain that the permissions on the file restrict access from unwanted users\&.
-
-
-.TP
--U|--user=username[%password]
-Sets the SMB username or username and password\&.
-
-
-If %password is not specified, the user will be prompted\&. The client will first check the \fBUSER\fR environment variable, then the \fBLOGNAME\fR variable and if either exists, the string is uppercased\&. If these environmental variables are not found, the username \fBGUEST\fR is used\&.
-
-
-A third option is to use a credentials file which contains the plaintext of the username and password\&. This option is mainly provided for scripts where the admin does not wish to pass the credentials on the command line or via environment variables\&. If this method is used, make certain that the permissions on the file restrict access from unwanted users\&. See the \fI-A\fR for more details\&.
-
-
-Be cautious about including passwords in scripts\&. Also, on many systems the command line of a running process may be seen via the \fBps\fR command\&. To be safe always allow \fBrpcclient\fR to prompt for a password and type it in directly\&.
-
-
-.TP
--n <primary NetBIOS name>
-This option allows you to override the NetBIOS name that Samba uses for itself\&. This is identical to setting the \fINetBIOS name\fR parameter in the \fBsmb.conf\fR(5) file\&. However, a command line setting will take precedence over settings in \fBsmb.conf\fR(5)\&.
-
-
-.TP
--i <scope>
-This specifies a NetBIOS scope that \fBnmblookup\fR will use to communicate with when generating NetBIOS names\&. For details on the use of NetBIOS scopes, see rfc1001\&.txt and rfc1002\&.txt\&. NetBIOS scopes are \fBvery\fR rarely used, only set this parameter if you are the system administrator in charge of all the NetBIOS systems you communicate with\&.
-
-
-.TP
--W|--workgroup=domain
-Set the SMB domain of the username\&. This overrides the default domain which is the domain defined in smb\&.conf\&. If the domain specified is the same as the servers NetBIOS name, it causes the client to log on using the servers local SAM (as opposed to the Domain SAM)\&.
-
-
-.TP
--O socket options
-TCP socket options to set on the client socket\&. See the socket options parameter in the \fBsmb.conf\fR(5) manual page for the list of valid options\&.
-
-
-.TP
--h|--help
-Print a summary of command line options\&.
-
-
+Make certain that the permissions on the file restrict
+access from unwanted users.
+.TP
+\fB-c|--command='command string'\fR
+execute semicolon separated commands (listed
+below))
+.TP
+\fB-d|--debug=debuglevel\fR
+\fIdebuglevel\fR is an integer
+from 0 to 10. The default value if this parameter is
+not specified is zero.
+
+The higher this value, the more detail will be
+logged to the log files about the activities of the
+server. At level 0, only critical errors and serious
+warnings will be logged. Level 1 is a reasonable level for
+day to day running - it generates a small amount of
+information about operations carried out.
+
+Levels above 1 will generate considerable
+amounts of log data, and should only be used when
+investigating a problem. Levels above 3 are designed for
+use only by developers and generate HUGE amounts of log
+data, most of which is extremely cryptic.
+
+Note that specifying this parameter here will
+override the log
+level file.
+.TP
+\fB-h|--help\fR
+Print a summary of command line options.
+.TP
+\fB-I IP-address\fR
+\fIIP address\fR is the address of the server to connect to.
+It should be specified in standard "a.b.c.d" notation.
+
+Normally the client would attempt to locate a named
+SMB/CIFS server by looking it up via the NetBIOS name resolution
+mechanism described above in the \fIname resolve order\fR
+parameter above. Using this parameter will force the client
+to assume that the server is on the machine with the specified IP
+address and the NetBIOS name component of the resource being
+connected to will be ignored.
+
+There is no default for this parameter. If not supplied,
+it will be determined automatically by the client as described
+above.
+.TP
+\fB-l|--logfile=logbasename\fR
+File name for log/debug files. The extension
+\&'.client' will be appended. The log file is
+never removed by the client.
+.TP
+\fB-N|--nopass\fR
+instruct \fBrpcclient\fR not to ask
+for a password. By default, \fBrpcclient\fR will
+prompt for a password. See also the \fI-U\fR
+option.
+.TP
+\fB-s|--conf=smb.conf\fR
+Specifies the location of the all-important
+\fIsmb.conf\fR file.
+.TP
+\fB-U|--user=username[%password]\fR
+Sets the SMB username or username and password.
+
+If %password is not specified, the user will be prompted. The
+client will first check the \fBUSER\fR environment variable, then the
+\fBLOGNAME\fR variable and if either exists, the
+string is uppercased. If these environmental variables are not
+found, the username GUEST is used.
+
+A third option is to use a credentials file which
+contains the plaintext of the username and password. This
+option is mainly provided for scripts where the admin does not
+wish to pass the credentials on the command line or via environment
+variables. If this method is used, make certain that the permissions
+on the file restrict access from unwanted users. See the
+\fI-A\fR for more details.
+
+Be cautious about including passwords in scripts. Also, on
+many systems the command line of a running process may be seen
+via the \fBps\fR command. To be safe always allow
+\fBrpcclient\fR to prompt for a password and type
+it in directly.
+.TP
+\fB-W|--workgroup=domain\fR
+Set the SMB domain of the username. This
+overrides the default domain which is the domain defined in
+smb.conf. If the domain specified is the same as the server's NetBIOS name,
+it causes the client to log on using the server's local SAM (as
+opposed to the Domain SAM).
.SH "COMMANDS"
-
-.SS "LSARPC"
-
-.TP
-lsaquery
-Query info policy
-
-
-.TP
-lookupsids
-Resolve a list of SIDs to usernames\&.
-
-
-.TP
-lookupnames
-Resolve a list of usernames to SIDs\&.
-
-
-.TP
-enumtrusts
-Enumerate trusted domains
-
-
-.TP
-enumprivs
-Enumerate privileges
-
-
-.TP
-getdispname
-Get the privilege name
-
-
-.TP
-lsaenumsid
-Enumerate the LSA SIDS
-
-
-.TP
-lsaenumprivsaccount
-Enumerate the privileges of an SID
-
-
-.TP
-lsaenumacctrights
-Enumerate the rights of an SID
-
-
-.TP
-lsaenumacctwithright
-Enumerate accounts with a right
-
-
-.TP
-lsaaddacctrights
-Add rights to an account
-
-
-.TP
-lsaremoveacctrights
-Remove rights from an account
-
-
-.TP
-lsalookupprivvalue
-Get a privilege value given its name
-
-
-.TP
-lsaquerysecobj
-Query LSA security object
-
-
-.SS "LSARPC-DS"
-
-.TP
-dsroledominfo
-Get Primary Domain Information
-
-
.PP
-
-
+\fBLSARPC\fR
+.TP 0.2i
+\(bu
+\fBlsaquery\fR
+.TP 0.2i
+\(bu
+\fBlookupsids\fR - Resolve a list
+of SIDs to usernames.
+.TP 0.2i
+\(bu
+\fBlookupnames\fR - Resolve a list
+of usernames to SIDs.
+.TP 0.2i
+\(bu
+\fBenumtrusts\fR
.PP
-\fBDFS\fR
-
-.TP
-dfsexist
-Query DFS support
-
-
-.TP
-dfsadd
-Add a DFS share
-
-
-.TP
-dfsremove
-Remove a DFS share
-
-
-.TP
-dfsgetinfo
-Query DFS share info
-
-
-.TP
-dfsenum
-Enumerate dfs shares
-
-
-.SS "REG"
-
-.TP
-shutdown
-Remote Shutdown
-
-
-.TP
-abortshutdown
-Abort Shutdown
-
-
-.SS "SRVSVC"
-
-.TP
-srvinfo
-Server query info
-
-
-.TP
-netshareenum
-Enumerate shares
-
-
-.TP
-netfileenum
-Enumerate open files
-
-
-.TP
-netremotetod
-Fetch remote time of day
-
-
-.SS "SAMR"
-
-.TP
-queryuser
-Query user info
-
-
-.TP
-querygroup
-Query group info
-
-
-.TP
-queryusergroups
-Query user groups
-
-
-.TP
-querygroupmem
-Query group membership
-
-
-.TP
-queryaliasmem
-Query alias membership
-
-
-.TP
-querydispinfo
-Query display info
-
-
-.TP
-querydominfo
-Query domain info
-
-
-.TP
-enumdomusers
-Enumerate domain users
-
-
-.TP
-enumdomgroups
-Enumerate domain groups
-
-
-.TP
-enumalsgroups
-Enumerate alias groups
-
-
-.TP
-createdomuser
-Create domain user
-
-
-.TP
-samlookupnames
-Look up names
-
-
-.TP
-samlookuprids
-Look up names
-
-
-.TP
-deletedomuser
-Delete domain user
-
-
-.TP
-samquerysecobj
-Query SAMR security object
-
-
-.TP
-getdompwinfo
-Retrieve domain password info
-
-
-.TP
-lookupdomain
-Look up domain
-
-
-.SS "SPOOLSS"
-
-.TP
-adddriver <arch> <config>
-Execute an AddPrinterDriver() RPC to install the printer driver information on the server\&. Note that the driver files should already exist in the directory returned by \fBgetdriverdir\fR\&. Possible values for \fIarch\fR are the same as those for the \fBgetdriverdir\fR command\&. The \fIconfig\fR parameter is defined as follows:
+.PP
+\fBSAMR\fR
+.TP 0.2i
+\(bu
+\fBqueryuser\fR
+.TP 0.2i
+\(bu
+\fBquerygroup\fR
+.TP 0.2i
+\(bu
+\fBqueryusergroups\fR
+.TP 0.2i
+\(bu
+\fBquerygroupmem\fR
+.TP 0.2i
+\(bu
+\fBqueryaliasmem\fR
+.TP 0.2i
+\(bu
+\fBquerydispinfo\fR
+.TP 0.2i
+\(bu
+\fBquerydominfo\fR
+.TP 0.2i
+\(bu
+\fBenumdomgroups\fR
+.PP
+.PP
+\fBSPOOLSS\fR
+.TP 0.2i
+\(bu
+\fBadddriver <arch> <config>\fR
+- Execute an AddPrinterDriver() RPC to install the printer driver
+information on the server. Note that the driver files should
+already exist in the directory returned by
+\fBgetdriverdir\fR. Possible values for
+\fIarch\fR are the same as those for
+the \fBgetdriverdir\fR command.
+The \fIconfig\fR parameter is defined as
+follows:
.nf
-
-Long Printer Name:\\
-Driver File Name:\\
-Data File Name:\\
-Config File Name:\\
-Help File Name:\\
-Language Monitor Name:\\
-Default Data Type:\\
-Comma Separated list of Files
+ Long Printer Name:\\
+ Driver File Name:\\
+ Data File Name:\\
+ Config File Name:\\
+ Help File Name:\\
+ Language Monitor Name:\\
+ Default Data Type:\\
+ Comma Separated list of Files
+
.fi
-
-Any empty fields should be enter as the string "NULL"\&.
-
-
-Samba does not need to support the concept of Print Monitors since these only apply to local printers whose driver can make use of a bi-directional link for communication\&. This field should be "NULL"\&. On a remote NT print server, the Print Monitor for a driver must already be installed prior to adding the driver or else the RPC will fail\&.
-
-
-.TP
-addprinter <printername> <sharename> <drivername> <port>
-Add a printer on the remote server\&. This printer will be automatically shared\&. Be aware that the printer driver must already be installed on the server (see \fBadddriver\fR) and the \fIport\fRmust be a valid port name (see \fBenumports\fR\&.
-
-
-.TP
-deldriver
-Delete the specified printer driver for all architectures\&. This does not delete the actual driver files from the server, only the entry from the server's list of drivers\&.
-
-
-.TP
-enumdata
-Enumerate all printer setting data stored on the server\&. On Windows NT clients, these values are stored in the registry, while Samba servers store them in the printers TDB\&. This command corresponds to the MS Platform SDK GetPrinterData() function (* This command is currently unimplemented)\&.
-
-
-.TP
-enumdataex
-Enumerate printer data for a key
-
-
-.TP
-enumjobs <printer>
-List the jobs and status of a given printer\&. This command corresponds to the MS Platform SDK EnumJobs() function
-
-
-.TP
-enumkey
-Enumerate printer keys
-
-
-.TP
-enumports [level]
-Executes an EnumPorts() call using the specified info level\&. Currently only info levels 1 and 2 are supported\&.
-
-
-.TP
-enumdrivers [level]
-Execute an EnumPrinterDrivers() call\&. This lists the various installed printer drivers for all architectures\&. Refer to the MS Platform SDK documentation for more details of the various flags and calling options\&. Currently supported info levels are 1, 2, and 3\&.
-
-
-.TP
-enumprinters [level]
-Execute an EnumPrinters() call\&. This lists the various installed and share printers\&. Refer to the MS Platform SDK documentation for more details of the various flags and calling options\&. Currently supported info levels are 0, 1, and 2\&.
-
-
-.TP
-getdata <printername> <valuename;>
-Retrieve the data for a given printer setting\&. See the \fBenumdata\fR command for more information\&. This command corresponds to the GetPrinterData() MS Platform SDK function\&.
-
-
-.TP
-getdataex
-Get printer driver data with keyname
-
-
-.TP
-getdriver <printername>
-Retrieve the printer driver information (such as driver file, config file, dependent files, etc\&.\&.\&.) for the given printer\&. This command corresponds to the GetPrinterDriver() MS Platform SDK function\&. Currently info level 1, 2, and 3 are supported\&.
-
-
-.TP
-getdriverdir <arch>
-Execute a GetPrinterDriverDirectory() RPC to retrieve the SMB share name and subdirectory for storing printer driver files for a given architecture\&. Possible values for \fIarch\fR are "Windows 4\&.0" (for Windows 95/98), "Windows NT x86", "Windows NT PowerPC", "Windows Alpha_AXP", and "Windows NT R4000"\&.
-
-
-.TP
-getprinter <printername>
-Retrieve the current printer information\&. This command corresponds to the GetPrinter() MS Platform SDK function\&.
-
-
-.TP
-getprintprocdir
-Get print processor directory
-
-
-.TP
-openprinter <printername>
-Execute an OpenPrinterEx() and ClosePrinter() RPC against a given printer\&.
-
-
-.TP
-setdriver <printername> <drivername>
-Execute a SetPrinter() command to update the printer driver associated with an installed printer\&. The printer driver must already be correctly installed on the print server\&.
-
-
-See also the \fBenumprinters\fR and \fBenumdrivers\fR commands for obtaining a list of of installed printers and drivers\&.
-
-
-.TP
-addform
-Add form
-
-
-.TP
-setform
-Set form
-
-
-.TP
-getform
-Get form
-
-
-.TP
-deleteform
-Delete form
-
-
-.TP
-enumforms
-Enumerate form
-
-
-.TP
-setprinter
-Set printer comment
-
-
-.TP
-setprinterdata
-Set REG_SZ printer data
-
-
-.TP
-rffpcnex
-Rffpcnex test
-
-
-.SS "NETLOGON"
-
-.TP
-logonctrl2
-Logon Control 2
-
-
-.TP
-logonctrl
-Logon Control
-
-
-.TP
-samsync
-Sam Synchronisation
-
-
-.TP
-samdeltas
-Query Sam Deltas
-
-
-.TP
-samlogon
-Sam Logon
-
-
-.SS "GENERAL COMMANDS"
-
-.TP
-debuglevel
-Set the current debug level used to log information\&.
-
-
-.TP
-help (?)
-Print a listing of all known commands or extended help on a particular command\&.
-
-
-.TP
-quit (exit)
-Exit \fBrpcclient \fR\&.
-
-
+Any empty fields should be enter as the string "NULL".
+
+Samba does not need to support the concept of Print Monitors
+since these only apply to local printers whose driver can make
+use of a bi-directional link for communication. This field should
+be "NULL". On a remote NT print server, the Print Monitor for a
+driver must already be installed prior to adding the driver or
+else the RPC will fail.
+.TP 0.2i
+\(bu
+\fBaddprinter <printername>
+<sharename> <drivername> <port>\fR
+- Add a printer on the remote server. This printer
+will be automatically shared. Be aware that the printer driver
+must already be installed on the server (see \fBadddriver\fR)
+and the \fIport\fRmust be a valid port name (see
+\fBenumports\fR.
+.TP 0.2i
+\(bu
+\fBdeldriver\fR - Delete the
+specified printer driver for all architectures. This
+does not delete the actual driver files from the server,
+only the entry from the server's list of drivers.
+.TP 0.2i
+\(bu
+\fBenumdata\fR - Enumerate all
+printer setting data stored on the server. On Windows NT clients,
+these values are stored in the registry, while Samba servers
+store them in the printers TDB. This command corresponds
+to the MS Platform SDK GetPrinterData() function (* This
+command is currently unimplemented).
+.TP 0.2i
+\(bu
+\fBenumjobs <printer>\fR
+- List the jobs and status of a given printer.
+This command corresponds to the MS Platform SDK EnumJobs()
+function (* This command is currently unimplemented).
+.TP 0.2i
+\(bu
+\fBenumports [level]\fR
+- Executes an EnumPorts() call using the specified
+info level. Currently only info levels 1 and 2 are supported.
+.TP 0.2i
+\(bu
+\fBenumdrivers [level]\fR
+- Execute an EnumPrinterDrivers() call. This lists the various installed
+printer drivers for all architectures. Refer to the MS Platform SDK
+documentation for more details of the various flags and calling
+options. Currently supported info levels are 1, 2, and 3.
+.TP 0.2i
+\(bu
+\fBenumprinters [level]\fR
+- Execute an EnumPrinters() call. This lists the various installed
+and share printers. Refer to the MS Platform SDK documentation for
+more details of the various flags and calling options. Currently
+supported info levels are 0, 1, and 2.
+.TP 0.2i
+\(bu
+\fBgetdata <printername>\fR
+- Retrieve the data for a given printer setting. See
+the \fBenumdata\fR command for more information.
+This command corresponds to the GetPrinterData() MS Platform
+SDK function (* This command is currently unimplemented).
+.TP 0.2i
+\(bu
+\fBgetdriver <printername>\fR
+- Retrieve the printer driver information (such as driver file,
+config file, dependent files, etc...) for
+the given printer. This command corresponds to the GetPrinterDriver()
+MS Platform SDK function. Currently info level 1, 2, and 3 are supported.
+.TP 0.2i
+\(bu
+\fBgetdriverdir <arch>\fR
+- Execute a GetPrinterDriverDirectory()
+RPC to retrieve the SMB share name and subdirectory for
+storing printer driver files for a given architecture. Possible
+values for \fIarch\fR are "Windows 4.0"
+(for Windows 95/98), "Windows NT x86", "Windows NT PowerPC", "Windows
+Alpha_AXP", and "Windows NT R4000".
+.TP 0.2i
+\(bu
+\fBgetprinter <printername>\fR
+- Retrieve the current printer information. This command
+corresponds to the GetPrinter() MS Platform SDK function.
+.TP 0.2i
+\(bu
+\fBopenprinter <printername>\fR
+- Execute an OpenPrinterEx() and ClosePrinter() RPC
+against a given printer.
+.TP 0.2i
+\(bu
+\fBsetdriver <printername>
+<drivername>\fR
+- Execute a SetPrinter() command to update the printer driver
+associated with an installed printer. The printer driver must
+already be correctly installed on the print server.
+
+See also the \fBenumprinters\fR and
+\fBenumdrivers\fR commands for obtaining a list of
+of installed printers and drivers.
+.PP
+\fBGENERAL OPTIONS\fR
+.TP 0.2i
+\(bu
+\fBdebuglevel\fR - Set the current
+debug level used to log information.
+.TP 0.2i
+\(bu
+\fBhelp (?)\fR - Print a listing of all
+known commands or extended help on a particular command.
+.TP 0.2i
+\(bu
+\fBquit (exit)\fR - Exit \fBrpcclient
+\fR.
.SH "BUGS"
-
.PP
-\fBrpcclient\fR is designed as a developer testing tool and may not be robust in certain areas (such as command line parsing)\&. It has been known to generate a core dump upon failures when invalid parameters where passed to the interpreter\&.
-
+\fBrpcclient\fR is designed as a developer testing tool
+and may not be robust in certain areas (such as command line parsing).
+It has been known to generate a core dump upon failures when invalid
+parameters where passed to the interpreter.
.PP
From Luke Leighton's original rpcclient man page:
-
.PP
-\fBWARNING!\fR The MSRPC over SMB code has been developed from examining Network traces\&. No documentation is available from the original creators (Microsoft) on how MSRPC over SMB works, or how the individual MSRPC services work\&. Microsoft's implementation of these services has been demonstrated (and reported) to be\&.\&.\&. a bit flaky in places\&.
-
+\fB"WARNING!\fR The MSRPC over SMB code has
+been developed from examining Network traces. No documentation is
+available from the original creators (Microsoft) on how MSRPC over
+SMB works, or how the individual MSRPC services work. Microsoft's
+implementation of these services has been demonstrated (and reported)
+to be... a bit flaky in places.
.PP
-The development of Samba's implementation is also a bit rough, and as more of the services are understood, it can even result in versions of \fBsmbd\fR(8) and \fBrpcclient\fR(1) that are incompatible for some commands or services\&. Additionally, the developers are sending reports to Microsoft, and problems found or reported to Microsoft are fixed in Service Packs, which may result in incompatibilities\&.
-
+The development of Samba's implementation is also a bit rough,
+and as more of the services are understood, it can even result in
+versions of \fBsmbd(8)\fR and \fBrpcclient(1)\fR
+that are incompatible for some commands or services. Additionally,
+the developers are sending reports to Microsoft, and problems found
+or reported to Microsoft are fixed in Service Packs, which may
+result in incompatibilities."
.SH "VERSION"
-
.PP
-This man page is correct for version 3\&.0 of the Samba suite\&.
-
+This man page is correct for version 3.0 of the Samba
+suite.
.SH "AUTHOR"
-
.PP
-The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&.
-
+The original Samba software and related utilities
+were created by Andrew Tridgell. Samba is now developed
+by the Samba Team as an Open Source project similar
+to the way the Linux kernel is developed.
.PP
-The original rpcclient man page was written by Matthew Geddes, Luke Kenneth Casson Leighton, and rewritten by Gerald Carter\&. The conversion to DocBook for Samba 2\&.2 was done by Gerald Carter\&. The conversion to DocBook XML 4\&.2 for Samba 3\&.0 was done by Alexander Bokovoy\&.
-
+The original rpcclient man page was written by Matthew
+Geddes, Luke Kenneth Casson Leighton, and rewritten by Gerald Carter.
+The conversion to DocBook for Samba 2.2 was done by Gerald
+Carter.
diff --git a/docs/manpages/samba.7 b/docs/manpages/samba.7
index 9f01169a5a..0a64a78718 100644
--- a/docs/manpages/samba.7
+++ b/docs/manpages/samba.7
@@ -3,10 +3,9 @@
.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
.\" Please send any bug reports, improvements, comments, patches,
.\" etc. to Steve Cheng <steve@ggi-project.org>.
-.TH "SAMBA" "7" "19 april 2003" "" ""
-
+.TH "SAMBA" "7" "04 March 2003" "" ""
.SH NAME
-Samba \- A Windows SMB/CIFS fileserver for UNIX
+SAMBA \- A Windows SMB/CIFS fileserver for UNIX
.SH SYNOPSIS
\fBSamba\fR
@@ -20,19 +19,20 @@ also referred to as the Common Internet File System (CIFS). For a
more thorough description, see http://www.ubiqx.org/cifs/ <URL:http://www.ubiqx.org/cifs/>. Samba also implements the NetBIOS
protocol in nmbd.
.TP
-\fBsmbd(8)\fR
-The \fBsmbd\fR daemon provides the file and print services to
+\fBsmbd\fR
+The \fBsmbd \fR
+daemon provides the file and print services to
SMB clients, such as Windows 95/98, Windows NT, Windows
for Workgroups or LanManager. The configuration file
-for this daemon is described in \fBsmb.conf\fR(5)
+for this daemon is described in \fIsmb.conf\fR
.TP
-\fBnmbd(8)\fR
+\fBnmbd\fR
The \fBnmbd\fR
daemon provides NetBIOS nameservice and browsing
support. The configuration file for this daemon
-is described in \fBsmb.conf\fR(5)
+is described in \fIsmb.conf\fR
.TP
-\fBsmbclient(1)\fR
+\fBsmbclient\fR
The \fBsmbclient\fR
program implements a simple ftp-like client. This
is useful for accessing SMB shares on other compatible
@@ -40,119 +40,36 @@ servers (such as Windows NT), and can also be used
to allow a UNIX box to print to a printer attached to
any SMB server (such as a PC running Windows NT).
.TP
-\fBtestparm(1)\fR
+\fBtestparm\fR
The \fBtestparm\fR
-utility is a simple syntax checker for Samba's \fBsmb.conf\fR(5) configuration file.
+utility is a simple syntax checker for Samba's
+\fIsmb.conf\fRconfiguration file.
.TP
-\fBtestprns(1)\fR
+\fBtestprns\fR
The \fBtestprns\fR
utility supports testing printer names defined
in your \fIprintcap\fR file used
by Samba.
.TP
-\fBsmbstatus(1)\fR
+\fBsmbstatus\fR
The \fBsmbstatus\fR
tool provides access to information about the
current connections to \fBsmbd\fR.
.TP
-\fBnmblookup(1)\fR
+\fBnmblookup\fR
The \fBnmblookup\fR
tools allows NetBIOS name queries to be made
from a UNIX host.
.TP
-\fBsmbgroupedit(8)\fR
-The \fBsmbgroupedit\fR
-tool allows for mapping unix groups to NT Builtin,
-Domain, or Local groups. Also it allows setting
-priviledges for that group, such as saAddUser, etc.
+\fBmake_smbcodepage\fR
+The \fBmake_smbcodepage\fR
+utility provides a means of creating SMB code page
+definition files for your \fBsmbd\fR server.
.TP
-\fBsmbpasswd(8)\fR
+\fBsmbpasswd\fR
The \fBsmbpasswd\fR
command is a tool for changing LanMan and Windows NT
password hashes on Samba and Windows NT servers.
-.TP
-\fBsmbcacls(1)\fR
-The \fBsmbcacls\fR command is
-a tool to set ACL's on remote CIFS servers.
-.TP
-\fBsmbsh(1)\fR
-The \fBsmbsh\fR command is
-a program that allows you to run a unix shell with
-with an overloaded VFS.
-.TP
-\fBsmbtree(1)\fR
-The \fBsmbtree\fR command
-is a text-based network neighborhood tool.
-.TP
-\fBsmbtar(1)\fR
-The \fBsmbtar\fR can make
-backups of data on CIFS/SMB servers.
-.TP
-\fBsmbspool(8)\fR
-\fBsmbspool\fR is a
-helper utility for printing on printers connected
-to CIFS servers.
-.TP
-\fBsmbcontrol(1)\fR
-\fBsmbcontrol\fR is a utility
-that can change the behaviour of running samba daemons.
-.TP
-\fBrpcclient(1)\fR
-\fBrpcclient\fR is a utility
-that can be used to execute RPC commands on remote
-CIFS servers.
-.TP
-\fBpdbedit(8)\fR
-The \fBpdbedit\fR command
-can be used to maintain the local user database on
-a samba server.
-.TP
-\fBfindsmb(1)\fR
-The \fBfindsmb\fR command
-can be used to find SMB servers on the local network.
-.TP
-\fBnet(8)\fR
-The \fBnet\fR command
-is supposed to work similar to the DOS/Windows
-NET.EXE command.
-.TP
-\fBswat(8)\fR
-\fBswat\fR is a web-based
-interface to configuring \fIsmb.conf\fR.
-.TP
-\fBwinbindd(8)\fR
-\fBwinbindd\fR is a daemon
-that is used for integrating authentication and
-the user database into unix.
-.TP
-\fBwbinfo(1)\fR
-\fBwbinfo\fR is a utility
-that retrieves and stores information related to winbind.
-.TP
-\fBeditreg(1)\fR
-\fBeditreg\fR is a command-line
-utility that can edit windows registry files.
-.TP
-\fBprofiles(1)\fR
-\fBprofiles\fR is a command-line
-utility that can be used to replace all occurences of
-a certain SID with another SID.
-.TP
-\fBvfstest(1)\fR
-\fBvfstest\fR is a utility
-that can be used to test vfs modules.
-.TP
-\fBntlm_auth(1)\fR
-\fBntlm_auth\fR is a helper-utility
-for external programs wanting to do NTLM-authentication.
-.TP
-\fBsmbmount(8), smbumount(8), smbmount(8)\fR
-\fBsmbmount\fR,\fBsmbmnt\fR and \fBsmbmnt\fR are commands that can be used to
-mount CIFS/SMB shares on Linux.
-.TP
-\fBsmbcquotas(1)\fR
-\fBsmbcquotas\fR is a tool that
-can set remote QUOTA's on server with NTFS 5.
.SH "COMPONENTS"
.PP
The Samba suite is made up of several components. Each
@@ -184,13 +101,13 @@ on the newsgroup comp.protocol.smb <URL:news:comp.protocols.smb> and the Samba
list. Details on how to join the mailing list are given in
the README file that comes with Samba.
.PP
-If you have access to a WWW viewer (such as Mozilla
-or Konqueror) then you will also find lots of useful information,
+If you have access to a WWW viewer (such as Netscape
+or Mosaic) then you will also find lots of useful information,
including back issues of the Samba mailing list, at
http://lists.samba.org <URL:http://lists.samba.org/>.
.SH "VERSION"
.PP
-This man page is correct for version 3.0 of the
+This man page is correct for version 2.2 of the
Samba suite.
.SH "CONTRIBUTIONS"
.PP
@@ -200,8 +117,8 @@ http://lists.samba.org <URL:http://lists.samba.org/>.
.PP
If you have patches to submit, visit
http://devel.samba.org/ <URL:http://devel.samba.org/>
-for information on how to do it properly. We prefer patches
-in \fBdiff -u\fR format.
+for information on how to do it properly. We prefer patches in
+\fBdiff -u\fR format.
.SH "CONTRIBUTORS"
.PP
Contributors to the project are now too numerous
@@ -224,7 +141,7 @@ to the way the Linux kernel is developed.
.PP
The original Samba man pages were written by Karl Auer.
The man page sources were converted to YODL format (another
-excellent piece of Open Source software, available at ftp://ftp.icce.rug.nl/pub/unix/ <URL:ftp://ftp.icce.rug.nl/pub/unix/>) and updated for the Samba 2.0
+excellent piece of Open Source software, available at
+ftp://ftp.icce.rug.nl/pub/unix/ <URL:ftp://ftp.icce.rug.nl/pub/unix/>) and updated for the Samba 2.0
release by Jeremy Allison. The conversion to DocBook for
-Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML
-4.2 for Samba 3.0 was done by Alexander Bokovoy.
+Samba 2.2 was done by Gerald Carter
diff --git a/docs/manpages/smb.conf.5 b/docs/manpages/smb.conf.5
index 74716bf1bd..02861d492d 100644
--- a/docs/manpages/smb.conf.5
+++ b/docs/manpages/smb.conf.5
@@ -1,6520 +1,7441 @@
-.\"Generated by db2man.xsl. Don't modify this, modify the source.
-.de Sh \" Subsection
-.br
-.if t .Sp
-.ne 5
-.PP
-\fB\\$1\fR
-.PP
-..
-.de Sp \" Vertical space (when we can't use .PP)
-.if t .sp .5v
-.if n .sp
-..
-.de Ip \" List item
-.br
-.ie \\n(.$>=3 .ne \\$3
-.el .ne 3
-.IP "\\$1" \\$2
-..
-.TH "SMB.CONF" 5 "" "" ""
+.\" This manpage has been automatically generated by docbook2man
+.\" from a DocBook document. This tool can be found at:
+.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
+.\" Please send any bug reports, improvements, comments, patches,
+.\" etc. to Steve Cheng <steve@ggi-project.org>.
+.TH "SMB.CONF" "5" "30 March 2003" "" ""
.SH NAME
smb.conf \- The configuration file for the Samba suite
.SH "SYNOPSIS"
-
.PP
-The \fIsmb\&.conf\fR file is a configuration file for the Samba suite\&. \fIsmb\&.conf\fR contains runtime configuration information for the Samba programs\&. The \fIsmb\&.conf\fR file is designed to be configured and administered by the \fBswat\fR(8) program\&. The complete description of the file format and possible parameters held within are here for reference purposes\&.
-
+The \fIsmb.conf\fR file is a configuration
+file for the Samba suite. \fIsmb.conf\fR contains
+runtime configuration information for the Samba programs. The
+\fIsmb.conf\fR file is designed to be configured and
+administered by the \fBswat(8)\fR
+ program. The complete description of the file format and
+possible parameters held within are here for reference purposes.
.SH "FILE FORMAT"
-
.PP
-The file consists of sections and parameters\&. A section begins with the name of the section in square brackets and continues until the next section begins\&. Sections contain parameters of the form
-
+The file consists of sections and parameters. A section
+begins with the name of the section in square brackets and continues
+until the next section begins. Sections contain parameters of the
+form
.PP
-\fIname\fR = \fIvalue \fR
-
+\fIname\fR = \fIvalue
+\fR
.PP
-The file is line-based - that is, each newline-terminated line represents either a comment, a section name or a parameter\&.
-
+The file is line-based - that is, each newline-terminated
+line represents either a comment, a section name or a parameter.
.PP
-Section and parameter names are not case sensitive\&.
-
+Section and parameter names are not case sensitive.
.PP
-Only the first equals sign in a parameter is significant\&. Whitespace before or after the first equals sign is discarded\&. Leading, trailing and internal whitespace in section and parameter names is irrelevant\&. Leading and trailing whitespace in a parameter value is discarded\&. Internal whitespace within a parameter value is retained verbatim\&.
-
+Only the first equals sign in a parameter is significant.
+Whitespace before or after the first equals sign is discarded.
+Leading, trailing and internal whitespace in section and parameter
+names is irrelevant. Leading and trailing whitespace in a parameter
+value is discarded. Internal whitespace within a parameter value
+is retained verbatim.
.PP
-Any line beginning with a semicolon (';') or a hash ('#') character is ignored, as are lines containing only whitespace\&.
-
+Any line beginning with a semicolon (';') or a hash ('#')
+character is ignored, as are lines containing only whitespace.
.PP
-Any line ending in a '\\' is continued on the next line in the customary UNIX fashion\&.
-
+Any line ending in a '\\' is continued
+on the next line in the customary UNIX fashion.
.PP
-The values following the equals sign in parameters are all either a string (no quotes needed) or a boolean, which may be given as yes/no, 0/1 or true/false\&. Case is not significant in boolean values, but is preserved in string values\&. Some items such as create modes are numeric\&.
-
+The values following the equals sign in parameters are all
+either a string (no quotes needed) or a boolean, which may be given
+as yes/no, 0/1 or true/false. Case is not significant in boolean
+values, but is preserved in string values. Some items such as
+create modes are numeric.
.SH "SECTION DESCRIPTIONS"
-
.PP
-Each section in the configuration file (except for the [global] section) describes a shared resource (known as a "share")\&. The section name is the name of the shared resource and the parameters within the section define the shares attributes\&.
-
+Each section in the configuration file (except for the
+[global] section) describes a shared resource (known
+as a "share"). The section name is the name of the
+shared resource and the parameters within the section define
+the shares attributes.
.PP
-There are three special sections, [global], [homes] and [printers], which are described under \fBspecial sections\fR\&. The following notes apply to ordinary section descriptions\&.
-
+There are three special sections, [global],
+[homes] and [printers], which are
+described under \fBspecial sections\fR. The
+following notes apply to ordinary section descriptions.
.PP
-A share consists of a directory to which access is being given plus a description of the access rights which are granted to the user of the service\&. Some housekeeping options are also specifiable\&.
-
+A share consists of a directory to which access is being
+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 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)\&.
-
+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).
.PP
-Sections may be designated \fBguest\fR services, in which case no password is required to access them\&. A specified UNIX \fBguest account\fR is used to define access privileges in this case\&.
-
+Sections may be designated \fBguest\fR services,
+in which case no password is required to access them. A specified
+UNIX \fBguest account\fR is used to define access
+privileges in this case.
.PP
-Sections other than guest services will require a password to access them\&. The client provides the username\&. As older clients only provide passwords and not usernames, you may specify a list of usernames to check against the password using the "user =" option in the share definition\&. For modern clients such as Windows 95/98/ME/NT/2000, this should not be necessary\&.
-
+Sections other than guest services will require a password
+to access them. The client provides the username. As older clients
+only provide passwords and not usernames, you may specify a list
+of usernames to check against the password using the "user ="
+option in the share definition. For modern clients such as
+Windows 95/98/ME/NT/2000, this should not be necessary.
.PP
-Note that the access rights granted by the server are masked by the access rights granted to the specified or guest UNIX user by the host system\&. The server does not grant more access than the host system grants\&.
-
+Note that the access rights granted by the server are
+masked by the access rights granted to the specified or guest
+UNIX user by the host system. The server does not grant more
+access than the host system grants.
.PP
-The following sample section defines a file space share\&. The user has write access to the path \fI/home/bar\fR\&. The share is accessed via the share name "foo":
-.nf
-
-
-[foo]
- path = /home/bar
- read only = no
+The following sample section defines a file space share.
+The user has write access to the path \fI/home/bar\fR.
+The share is accessed via the share name "foo":
+.nf
+ [foo]
+ path = /home/bar
+ read only = no
+
+
.fi
-
.PP
-The following sample section defines a printable share\&. The share is readonly, but printable\&. That is, the only write access permitted is via calls to open, write to and close a spool file\&. The \fBguest ok\fR parameter means access will be permitted as the default guest user (specified elsewhere):
-.nf
-
-
-[aprinter]
- path = /usr/spool/public
- read only = yes
- printable = yes
- guest ok = yes
+The following sample section defines a printable share.
+The share is readonly, but printable. That is, the only write
+access permitted is via calls to open, write to and close a
+spool file. The \fBguest ok\fR parameter means
+access will be permitted as the default guest user (specified
+elsewhere):
+.nf
+ [aprinter]
+ path = /usr/spool/public
+ read only = yes
+ printable = yes
+ guest ok = yes
+
+
.fi
-
.SH "SPECIAL SECTIONS"
-
-.SS "The [global] section"
-
+.SS "THE [GLOBAL] SECTION"
.PP
-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\&.
-
-.SS "The [homes] section"
-
+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.
+.SS "THE [HOMES] SECTION"
.PP
-If a section called homes is included in the configuration file, services connecting clients to their home directories can be created on the fly by the server\&.
-
+If a section called homes is included in the
+configuration file, services connecting clients to their
+home directories can be created on the fly by the server.
.PP
-When the connection request is made, the existing sections are scanned\&. If a match is found, it is used\&. If no match is found, the requested section name is treated as a user name and looked up in the local password file\&. If the name exists and the correct password has been given, a share is created by cloning the [homes] section\&.
-
+When the connection request is made, the existing
+sections are scanned. If a match is found, it is used. If no
+match is found, the requested section name is treated as a
+user name and looked up in the local password file. If the
+name exists and the correct password has been given, a share is
+created by cloning the [homes] section.
.PP
-Some modifications are then made to the newly created share:
-
-.TP 3
+Some modifications are then made to the newly
+created share:
+.TP 0.2i
\(bu
-The share name is changed from homes to the located username\&.
-
-.TP
+The share name is changed from homes to
+the located username.
+.TP 0.2i
\(bu
-If no path was given, the path is set to the user's home directory\&.
-
-.LP
-
+If no path was given, the path is set to
+the user's home directory.
.PP
-If you decide to use a \fBpath =\fR line in your [homes] section then you may find it useful to use the %S macro\&. For example :
-
+If you decide to use a \fBpath =\fR line
+in your [homes] section then you may find it useful
+to use the %S macro. For example :
.PP
\fBpath = /data/pchome/%S\fR
-
.PP
-would be useful if you have different home directories for your PCs than for UNIX access\&.
-
+would be useful if you have different home directories
+for your PCs than for UNIX access.
.PP
-This is a fast and simple way to give a large number of clients access to their home directories with a minimum of fuss\&.
-
+This is a fast and simple way to give a large number
+of clients access to their home directories with a minimum
+of fuss.
.PP
-A similar process occurs if the requested section name is "homes", except that the share name is not changed to that of the requesting user\&. This method of using the [homes] section works well if different users share a client PC\&.
-
+A similar process occurs if the requested section
+name is "homes", except that the share name is not
+changed to that of the requesting user. This method of using
+the [homes] section works well if different users share
+a client PC.
.PP
-The [homes] section can specify all the parameters a normal service section can specify, though some make more sense than others\&. The following is a typical and suitable [homes] section:
-.nf
-
-
-[homes]
- read only = no
+The [homes] section can specify all the parameters
+a normal service section can specify, though some make more sense
+than others. The following is a typical and suitable [homes]
+section:
+.nf
+ [homes]
+ read only = no
+
+
.fi
-
.PP
-An important point is that if guest access is specified in the [homes] section, all home directories will be visible to all clients \fBwithout a password\fR\&. In the very unlikely event that this is actually desirable, it would be wise to also specify \fBread only access\fR\&.
-
+An important point is that if guest access is specified
+in the [homes] section, all home directories will be
+visible to all clients \fBwithout a password\fR.
+In the very unlikely event that this is actually desirable, it
+would be wise to also specify \fBread only
+access\fR.
.PP
-Note that the \fBbrowseable\fR flag for auto home directories will be inherited from the global browseable flag, not the [homes] browseable flag\&. This is useful as it means setting \fBbrowseable = no\fR in the [homes] section will hide the [homes] share but make any auto home directories visible\&.
-
-.SS "The [printers] section"
-
+Note that the \fBbrowseable\fR flag for
+auto home directories will be inherited from the global browseable
+flag, not the [homes] browseable flag. This is useful as
+it means setting \fBbrowseable = no\fR in
+the [homes] section will hide the [homes] share but make
+any auto home directories visible.
+.SS "THE [PRINTERS] SECTION"
.PP
-This section works like [homes], but for printers\&.
-
+This section works like [homes],
+but for printers.
.PP
-If a [printers] section occurs in the configuration file, users are able to connect to any printer specified in the local host's printcap file\&.
-
+If a [printers] section occurs in the
+configuration file, users are able to connect to any printer
+specified in the local host's printcap file.
.PP
-When a connection request is made, the existing sections are scanned\&. If a match is found, it is used\&. If no match is found, but a [homes] section exists, it is used as described above\&. Otherwise, the requested section name is treated as a printer name and the appropriate printcap file is scanned to see if the requested section name is a valid printer share name\&. If a match is found, a new printer share is created by cloning the [printers] section\&.
-
+When a connection request is made, the existing sections
+are scanned. If a match is found, it is used. If no match is found,
+but a [homes] section exists, it is used as described
+above. Otherwise, the requested section name is treated as a
+printer name and the appropriate printcap file is scanned to see
+if the requested section name is a valid printer share name. If
+a match is found, a new printer share is created by cloning
+the [printers] section.
.PP
-A few modifications are then made to the newly created share:
-
-.TP 3
+A few modifications are then made to the newly created
+share:
+.TP 0.2i
\(bu
-The share name is set to the located printer name
-
-.TP
+The share name is set to the located printer
+name
+.TP 0.2i
\(bu
-If no printer name was given, the printer name is set to the located printer name
-
-.TP
+If no printer name was given, the printer name
+is set to the located printer name
+.TP 0.2i
\(bu
-If the share does not permit guest access and no username was given, the username is set to the located printer name\&.
-
-.LP
-
+If the share does not permit guest access and
+no username was given, the username is set to the located
+printer name.
.PP
-Note that the [printers] service MUST be printable - if you specify otherwise, the server will refuse to load the configuration file\&.
-
+Note that the [printers] service MUST be
+printable - if you specify otherwise, the server will refuse
+to load the configuration file.
.PP
-Typically the path specified would be that of a world-writeable spool directory with the sticky bit set on it\&. A typical [printers] entry would look like this:
-.nf
+Typically the path specified would be that of a
+world-writeable spool directory with the sticky bit set on
+it. A typical [printers] entry would look like
+this:
-[printers]
- path = /usr/spool/public
- guest ok = yes
- printable = yes
+.nf
+ [printers]
+ path = /usr/spool/public
+ guest ok = yes
+ printable = yes
+
.fi
-
.PP
-All aliases given for a printer in the printcap file are legitimate printer names as far as the server is concerned\&. If your printing subsystem doesn't work like that, you will have to set up a pseudo-printcap\&. This is a file consisting of one or more lines like this:
-.nf
-
-
-alias|alias|alias|alias\&.\&.\&.
+All aliases given for a printer in the printcap file
+are legitimate printer names as far as the server is concerned.
+If your printing subsystem doesn't work like that, you will have
+to set up a pseudo-printcap. This is a file consisting of one or
+more lines like this:
+.nf
+ alias|alias|alias|alias...
+
+
.fi
-
.PP
-Each alias should be an acceptable printer name for your printing subsystem\&. In the [global] section, specify the new file as your printcap\&. The server will then only recognize names found in your pseudo-printcap, which of course can contain whatever aliases you like\&. The same technique could be used simply to limit access to a subset of your local printers\&.
-
+Each alias should be an acceptable printer name for
+your printing subsystem. In the [global] section, specify
+the new file as your printcap. The server will then only recognize
+names found in your pseudo-printcap, which of course can contain
+whatever aliases you like. The same technique could be used
+simply to limit access to a subset of your local printers.
.PP
-An alias, by the way, is defined as any component of the first entry of a printcap record\&. Records are separated by newlines, components (if there are more than one) are separated by vertical bar symbols ('|')\&.
-
-.RS
-.Sh "Note"
-
+An alias, by the way, is defined as any component of the
+first entry of a printcap record. Records are separated by newlines,
+components (if there are more than one) are separated by vertical
+bar symbols ('|').
.PP
-On SYSV systems which use lpstat to determine what printers are defined on the system you may be able to use "printcap name = lpstat" to automatically obtain a list of printers\&. See the "printcap name" option for more details\&.
-
-.RE
-
+NOTE: On SYSV systems which use lpstat to determine what
+printers are defined on the system you may be able to use
+"printcap name = lpstat" to automatically obtain a list
+of printers. See the "printcap name" option
+for more details.
.SH "PARAMETERS"
-
.PP
-parameters define the specific attributes of sections\&.
-
+parameters define the specific attributes of sections.
.PP
-Some parameters are specific to the [global] section (e\&.g\&., \fBsecurity\fR)\&. Some parameters are usable in all sections (e\&.g\&., \fBcreate mode\fR)\&. All others are permissible only in normal sections\&. For the purposes of the following descriptions the [homes] and [printers] sections will be considered normal\&. The letter \fBG\fR in parentheses indicates that a parameter is specific to the [global] section\&. The letter \fBS\fR indicates that a parameter can be specified in a service specific section\&. Note that all \fBS\fR parameters can also be specified in the [global] section - in which case they will define the default behavior for all services\&.
-
+Some parameters are specific to the [global] section
+(e.g., \fBsecurity\fR). Some parameters are usable
+in all sections (e.g., \fBcreate mode\fR). All others
+are permissible only in normal sections. For the purposes of the
+following descriptions the [homes] and [printers]
+sections will be considered normal. The letter \fBG\fR
+in parentheses indicates that a parameter is specific to the
+[global] section. The letter \fBS\fR
+indicates that a parameter can be specified in a service specific
+section. Note that all \fBS\fR parameters can also be specified in
+the [global] section - in which case they will define
+the default behavior for all services.
.PP
-parameters are arranged here in alphabetical order - this may not create best bedfellows, but at least you can find them! Where there are synonyms, the preferred synonym is described, others refer to the preferred synonym\&.
-
+parameters are arranged here in alphabetical order - this may
+not create best bedfellows, but at least you can find them! Where
+there are synonyms, the preferred synonym is described, others refer
+to the preferred synonym.
.SH "VARIABLE SUBSTITUTIONS"
-
.PP
-Many of the strings that are settable in the config file can take substitutions\&. For example the option "path = /tmp/%u" would be interpreted as "path = /tmp/john" if the user connected with the username john\&.
-
+Many of the strings that are settable in the config file
+can take substitutions. For example the option "path =
+/tmp/%u" would be interpreted as "path =
+/tmp/john" if the user connected with the username john.
.PP
-These substitutions are mostly noted in the descriptions below, but there are some general substitutions which apply whenever they might be relevant\&. These are:
-
-.TP
-%U
-session user name (the user name that the client wanted, not necessarily the same as the one they got)\&.
-
-
-.TP
-%G
-primary group name of %U\&.
-
-
-.TP
-%h
-the Internet hostname that Samba is running on\&.
-
-
-.TP
-%m
-the NetBIOS name of the client machine (very useful)\&.
-
-
-.TP
-%L
-the NetBIOS name of the server\&. This allows you to change your config based on what the client calls you\&. Your server can have a "dual personality"\&.
-
-
-Note that this parameter is not available when Samba listens on port 445, as clients no longer send this information
-
-
-.TP
-%M
-the Internet name of the client machine\&.
-
-
-.TP
-%R
-the selected protocol level after protocol negotiation\&. It can be one of CORE, COREPLUS, LANMAN1, LANMAN2 or NT1\&.
-
-
-.TP
-%d
-The process id of the current server process\&.
-
-
-.TP
-%a
-the architecture of the remote machine\&. Only some are recognized, and those may not be 100% reliable\&. It currently recognizes Samba, WfWg, Win95, WinNT and Win2k\&. Anything else will be known as "UNKNOWN"\&. If it gets it wrong then sending a level 3 log to samba@samba\&.org should allow it to be fixed\&.
-
-
-.TP
-%I
-The IP address of the client machine\&.
-
-
-.TP
-%T
-the current date and time\&.
-
-
-.TP
-%D
-Name of the domain or workgroup of the current user\&.
-
-
-.TP
-%$(\fIenvvar\fR)
-The value of the environment variable \fIenvar\fR\&.
-
-
+These substitutions are mostly noted in the descriptions below,
+but there are some general substitutions which apply whenever they
+might be relevant. These are:
+.TP
+\fB%U\fR
+session user name (the user name that the client
+wanted, not necessarily the same as the one they got).
+.TP
+\fB%G\fR
+primary group name of %U.
+.TP
+\fB%h\fR
+the Internet hostname that Samba is running
+on.
+.TP
+\fB%m\fR
+the NetBIOS name of the client machine
+(very useful).
+.TP
+\fB%L\fR
+the NetBIOS name of the server. This allows you
+to change your config based on what the client calls you. Your
+server can have a "dual personality".
+
+Note that this parameter is not available when Samba listens
+on port 445, as clients no longer send this information
+.TP
+\fB%M\fR
+the Internet name of the client machine.
+.TP
+\fB%R\fR
+the selected protocol level after
+protocol negotiation. It can be one of CORE, COREPLUS,
+LANMAN1, LANMAN2 or NT1.
+.TP
+\fB%d\fR
+The process id of the current server
+process.
+.TP
+\fB%a\fR
+the architecture of the remote
+machine. Only some are recognized, and those may not be
+100% reliable. It currently recognizes Samba, WfWg, Win95,
+WinNT and Win2k. Anything else will be known as
+"UNKNOWN". If it gets it wrong then sending a level
+3 log to samba@samba.org
+ <URL:mailto:samba@samba.org> should allow it to be fixed.
+.TP
+\fB%I\fR
+The IP address of the client machine.
+.TP
+\fB%T\fR
+the current date and time.
+.TP
+\fB%D\fR
+Name of the domain or workgroup of the current user.
+.TP
+\fB%$(\fIenvvar\fB)\fR
+The value of the environment variable
+\fIenvar\fR.
.PP
-The following substitutes apply only to some configuration options(only those that are used when a connection has been established):
-
+The following substitutes apply only to some configuration options(only those
+that are used when a connection has been established):
.TP
-%S
-the name of the current service, if any\&.
-
-
+\fB%S\fR
+the name of the current service, if any.
.TP
-%P
-the root directory of the current service, if any\&.
-
-
+\fB%P\fR
+the root directory of the current service,
+if any.
.TP
-%u
-user name of the current service, if any\&.
-
-
+\fB%u\fR
+user name of the current service, if any.
.TP
-%g
-primary group name of %u\&.
-
-
+\fB%g\fR
+primary group name of %u.
.TP
-%H
-the home directory of the user given by %u\&.
-
-
+\fB%H\fR
+the home directory of the user given
+by %u.
.TP
-%N
-the name of your NIS home directory server\&. This is obtained from your NIS auto\&.map entry\&. If you have not compiled Samba with the \fB--with-automount\fR option then this value will be the same as %L\&.
-
-
+\fB%N\fR
+the name of your NIS home directory server.
+This is obtained from your NIS auto.map entry. If you have
+not compiled Samba with the \fB--with-automount\fR
+option then this value will be the same as %L.
.TP
-%p
-the path of the service's home directory, obtained from your NIS auto\&.map entry\&. The NIS auto\&.map entry is split up as "%N:%p"\&.
-
-
+\fB%p\fR
+the path of the service's home directory,
+obtained from your NIS auto.map entry. The NIS auto.map entry
+is split up as "%N:%p".
.PP
-There are some quite creative things that can be done with these substitutions and other smb\&.conf options\&.
-
+There are some quite creative things that can be done
+with these substitutions and other smb.conf options.
.SH "NAME MANGLING"
-
.PP
-Samba supports "name mangling" so that DOS and Windows clients can use files that don't conform to the 8\&.3 format\&. It can also be set to adjust the case of 8\&.3 format filenames\&.
-
+Samba supports "name mangling" so that DOS and
+Windows clients can use files that don't conform to the 8.3 format.
+It can also be set to adjust the case of 8.3 format filenames.
.PP
-There are several options that control the way mangling is performed, and they are grouped here rather than listed separately\&. For the defaults look at the output of the testparm program\&.
-
+There are several options that control the way mangling is
+performed, and they are grouped here rather than listed separately.
+For the defaults look at the output of the testparm program.
.PP
-All of these options can be set separately for each service (or globally, of course)\&.
-
+All of these options can be set separately for each service
+(or globally, of course).
.PP
-The options are:
-
-.TP
-mangle case = yes/no
-controls if names that have characters that aren't of the "default" case are mangled\&. For example, if this is yes then a name like "Mail" would be mangled\&. Default \fBno\fR\&.
-
-
-.TP
-case sensitive = yes/no
-controls whether filenames are case sensitive\&. If they aren't then Samba must do a filename search and match on passed names\&. Default \fBno\fR\&.
-
-
-.TP
-default case = upper/lower
-controls what the default case is for new filenames\&. Default \fBlower\fR\&.
-
-
-.TP
-preserve case = yes/no
-controls if new files are created with the case that the client passes, or if they are forced to be the "default" case\&. Default \fByes\fR\&.
-
-
-.TP
-short preserve case = yes/no
-controls if new files which conform to 8\&.3 syntax, that is all in upper case and of suitable length, are created upper case, or if they are forced to be the "default" case\&. This option can be use with "preserve case = yes" to permit long filenames to retain their case, while short names are lowercased\&. Default \fByes\fR\&.
-
-
+The options are:
+.TP
+\fBmangle case = yes/no\fR
+controls if names that have characters that
+aren't of the "default" case are mangled. For example,
+if this is yes then a name like "Mail" would be mangled.
+Default \fBno\fR.
+.TP
+\fBcase sensitive = yes/no\fR
+controls whether filenames are case sensitive. If
+they aren't then Samba must do a filename search and match on passed
+names. Default \fBno\fR.
+.TP
+\fBdefault case = upper/lower\fR
+controls what the default case is for new
+filenames. Default \fBlower\fR.
+.TP
+\fBpreserve case = yes/no\fR
+controls if new files are created with the
+case that the client passes, or if they are forced to be the
+"default" case. Default \fByes\fR.
+.TP
+\fBshort preserve case = yes/no\fR
+controls if new files which conform to 8.3 syntax,
+that is all in upper case and of suitable length, are created
+upper case, or if they are forced to be the "default"
+case. This option can be use with "preserve case = yes"
+to permit long filenames to retain their case, while short names
+are lowercased. Default \fByes\fR.
.PP
-By default, Samba 3\&.0 has the same semantics as a Windows NT server, in that it is case insensitive but case preserving\&.
-
+By default, Samba 3.0 has the same semantics as a Windows
+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 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\&. However, if one of the steps succeeds, then the following steps are not checked\&.
-
+There are a number of ways in which a user can connect
+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. However, if one of the
+steps succeeds, then the following steps are not checked.
.PP
-If the service is marked "guest only = yes" and the server is running with share-level security ("security = share") then steps 1 to 5 are skipped\&.
-
+If the service is marked "guest only = yes" and the
+server is running with share-level security ("security = share")
+then steps 1 to 5 are skipped.
.TP 3
-1.
-If the client has passed a username/password pair and that username/password pair is validated by the UNIX system's password programs then the connection is made as that username\&. Note that this includes the \\\\server\\service%\fIusername\fR method of passing a username\&.
-
-.TP
-2.
-If the client has previously registered a username with the system and now supplies a correct password for that username then the connection is allowed\&.
-
-.TP
-3.
-The client's NetBIOS name and any previously used user names are checked against the supplied password, if they match then the connection is allowed as the corresponding user\&.
-
-.TP
-4.
-If the client has previously validated a username/password pair with the server and the client has passed the validation token then that username is used\&.
-
-.TP
-5.
-If a "user = " field is given in the \fIsmb\&.conf\fR file for the service and the client has supplied a password, and that password matches (according to the UNIX system's password checking) with one of the usernames from the "user =" field then the connection is made as the username in the "user =" line\&. If one of the username in the "user =" list begins with a '@' then that name expands to a list of names in the group of the same name\&.
-
-.TP
-6.
-If the service is a guest service then a connection is made as the username given in the "guest account =" for the service, irrespective of the supplied password\&.
-
-.LP
-
+1.
+If the client has passed a username/password
+pair and that username/password pair is validated by the UNIX
+system's password programs then the connection is made as that
+username. Note that this includes the
+\\\\server\\service%\fIusername\fR method of passing
+a username.
+.TP 3
+2.
+If the client has previously registered a username
+with the system and now supplies a correct password for that
+username then the connection is allowed.
+.TP 3
+3.
+The client's NetBIOS name and any previously
+used user names are checked against the supplied password, if
+they match then the connection is allowed as the corresponding
+user.
+.TP 3
+4.
+If the client has previously validated a
+username/password pair with the server and the client has passed
+the validation token then that username is used.
+.TP 3
+5.
+If a "user = " field is given in the
+\fIsmb.conf\fR file for the service and the client
+has supplied a password, and that password matches (according to
+the UNIX system's password checking) with one of the usernames
+from the "user =" field then the connection is made as
+the username in the "user =" line. If one
+of the username in the "user =" list begins with a
+\&'@' then that name expands to a list of names in
+the group of the same name.
+.TP 3
+6.
+If the service is a guest service then a
+connection is made as the username given in the "guest
+account =" for the service, irrespective of the
+supplied password.
.SH "COMPLETE LIST OF GLOBAL PARAMETERS"
-
.PP
-Here is a list of all global parameters\&. See the section of each parameter for details\&. Note that some are synonyms\&.
-
-.TP 3
+Here is a list of all global parameters. See the section of
+each parameter for details. Note that some are synonyms.
+.TP 0.2i
\(bu
\fIabort shutdown script\fR
-
-.TP
+.TP 0.2i
\(bu
\fIadd group script\fR
-
-.TP
-\(bu
-\fIadd machine script\fR
-
-.TP
+.TP 0.2i
\(bu
\fIaddprinter command\fR
-
-.TP
+.TP 0.2i
\(bu
\fIadd share command\fR
-
-.TP
+.TP 0.2i
\(bu
\fIadd user script\fR
-
-.TP
+.TP 0.2i
\(bu
\fIadd user to group script\fR
-
-.TP
+.TP 0.2i
+\(bu
+\fIadd machine script\fR
+.TP 0.2i
+\(bu
+\fIdelete group script\fR
+.TP 0.2i
\(bu
\fIads server\fR
-
-.TP
+.TP 0.2i
\(bu
\fIalgorithmic rid base\fR
-
-.TP
+.TP 0.2i
\(bu
\fIallow trusted domains\fR
-
-.TP
+.TP 0.2i
\(bu
\fIannounce as\fR
-
-.TP
+.TP 0.2i
\(bu
\fIannounce version\fR
-
-.TP
+.TP 0.2i
\(bu
\fIauth methods\fR
-
-.TP
+.TP 0.2i
\(bu
\fIauto services\fR
-
-.TP
+.TP 0.2i
\(bu
\fIbind interfaces only\fR
-
-.TP
+.TP 0.2i
\(bu
\fIbrowse list\fR
-
-.TP
+.TP 0.2i
\(bu
\fIchange notify timeout\fR
-
-.TP
+.TP 0.2i
\(bu
\fIchange share command\fR
-
-.TP
+.TP 0.2i
\(bu
\fIconfig file\fR
-
-.TP
+.TP 0.2i
\(bu
-\fIdead time\fR
-
-.TP
+\fIdeadtime\fR
+.TP 0.2i
\(bu
\fIdebug hires timestamp\fR
-
-.TP
-\(bu
-\fIdebug level\fR
-
-.TP
+.TP 0.2i
\(bu
\fIdebug pid\fR
-
-.TP
+.TP 0.2i
\(bu
\fIdebug timestamp\fR
-
-.TP
+.TP 0.2i
\(bu
\fIdebug uid\fR
-
-.TP
+.TP 0.2i
\(bu
-\fIdefault service\fR
-
-.TP
+\fIdebuglevel\fR
+.TP 0.2i
\(bu
\fIdefault\fR
-
-.TP
+.TP 0.2i
\(bu
-\fIdelete group script\fR
-
-.TP
+\fIdefault service\fR
+.TP 0.2i
\(bu
\fIdeleteprinter command\fR
-
-.TP
+.TP 0.2i
\(bu
\fIdelete share command\fR
-
-.TP
-\(bu
-\fIdelete user from group script\fR
-
-.TP
+.TP 0.2i
\(bu
\fIdelete user script\fR
-
-.TP
+.TP 0.2i
+\(bu
+\fIdelete user from group script\fR
+.TP 0.2i
\(bu
\fIdfree command\fR
-
-.TP
+.TP 0.2i
\(bu
\fIdisable netbios\fR
-
-.TP
+.TP 0.2i
\(bu
\fIdisable spoolss\fR
-
-.TP
+.TP 0.2i
\(bu
\fIdisplay charset\fR
-
-.TP
+.TP 0.2i
\(bu
\fIdns proxy\fR
-
-.TP
+.TP 0.2i
\(bu
\fIdomain logons\fR
-
-.TP
+.TP 0.2i
\(bu
\fIdomain master\fR
-
-.TP
+.TP 0.2i
\(bu
\fIdos charset\fR
-
-.TP
+.TP 0.2i
\(bu
\fIencrypt passwords\fR
-
-.TP
+.TP 0.2i
\(bu
\fIenhanced browsing\fR
-
-.TP
+.TP 0.2i
\(bu
\fIenumports command\fR
-
-.TP
+.TP 0.2i
\(bu
\fIgetwd cache\fR
-
-.TP
-\(bu
-\fIguest account\fR
-
-.TP
+.TP 0.2i
\(bu
\fIhide local users\fR
-
-.TP
+.TP 0.2i
+\(bu
+\fIhide unreadable\fR
+.TP 0.2i
+\(bu
+\fIhide unwriteable files\fR
+.TP 0.2i
+\(bu
+\fIhide special files\fR
+.TP 0.2i
\(bu
\fIhomedir map\fR
-
-.TP
+.TP 0.2i
\(bu
\fIhost msdfs\fR
-
-.TP
+.TP 0.2i
\(bu
\fIhostname lookups\fR
-
-.TP
+.TP 0.2i
\(bu
\fIhosts equiv\fR
-
-.TP
-\(bu
-\fIinclude\fR
-
-.TP
+.TP 0.2i
\(bu
\fIinterfaces\fR
-
-.TP
+.TP 0.2i
\(bu
\fIkeepalive\fR
-
-.TP
+.TP 0.2i
\(bu
\fIkernel oplocks\fR
-
-.TP
+.TP 0.2i
\(bu
\fIlanman auth\fR
-
-.TP
+.TP 0.2i
\(bu
\fIlarge readwrite\fR
-
-.TP
+.TP 0.2i
\(bu
\fIldap admin dn\fR
-
-.TP
+.TP 0.2i
\(bu
\fIldap delete dn\fR
-
-.TP
+.TP 0.2i
\(bu
-\fIldap filter\fR
-
-.TP
+\fIldap del only sam attr\fR
+.TP 0.2i
\(bu
-\fIldap machine suffix\fR
-
-.TP
-\(bu
-\fIldap passwd sync\fR
-
-.TP
+\fIldap filter\fR
+.TP 0.2i
\(bu
\fIldap port\fR
-
-.TP
+.TP 0.2i
\(bu
\fIldap server\fR
-
-.TP
+.TP 0.2i
\(bu
\fIldap ssl\fR
-
-.TP
+.TP 0.2i
\(bu
\fIldap suffix\fR
-
-.TP
-\(bu
-\fIldap trust ids\fR
-
-.TP
+.TP 0.2i
\(bu
\fIldap user suffix\fR
-
-.TP
+.TP 0.2i
+\(bu
+\fIldap machine suffix\fR
+.TP 0.2i
+\(bu
+\fIldap passwd sync\fR
+.TP 0.2i
+\(bu
+\fIldap trust ids\fR
+.TP 0.2i
\(bu
\fIlm announce\fR
-
-.TP
+.TP 0.2i
\(bu
\fIlm interval\fR
-
-.TP
+.TP 0.2i
\(bu
\fIload printers\fR
-
-.TP
+.TP 0.2i
\(bu
\fIlocal master\fR
-
-.TP
-\(bu
-\fIlock directory\fR
-
-.TP
+.TP 0.2i
\(bu
\fIlock dir\fR
-
-.TP
+.TP 0.2i
+\(bu
+\fIlock directory\fR
+.TP 0.2i
\(bu
\fIlock spin count\fR
-
-.TP
+.TP 0.2i
\(bu
\fIlock spin time\fR
-
-.TP
+.TP 0.2i
+\(bu
+\fIpid directory\fR
+.TP 0.2i
\(bu
\fIlog file\fR
-
-.TP
+.TP 0.2i
\(bu
\fIlog level\fR
-
-.TP
+.TP 0.2i
\(bu
\fIlogon drive\fR
-
-.TP
+.TP 0.2i
\(bu
\fIlogon home\fR
-
-.TP
+.TP 0.2i
\(bu
\fIlogon path\fR
-
-.TP
+.TP 0.2i
\(bu
\fIlogon script\fR
-
-.TP
+.TP 0.2i
\(bu
\fIlpq cache time\fR
-
-.TP
+.TP 0.2i
\(bu
\fImachine password timeout\fR
-
-.TP
-\(bu
-\fImangling stack\fR
-
-.TP
+.TP 0.2i
\(bu
-\fImangling prefix\fR
-
-.TP
-\(bu
-\fImangling method\fR
-
-.TP
+\fImangled stack\fR
+.TP 0.2i
\(bu
\fImap to guest\fR
-
-.TP
+.TP 0.2i
\(bu
\fImax disk size\fR
-
-.TP
+.TP 0.2i
\(bu
\fImax log size\fR
-
-.TP
+.TP 0.2i
\(bu
\fImax mux\fR
-
-.TP
+.TP 0.2i
\(bu
\fImax open files\fR
-
-.TP
+.TP 0.2i
\(bu
\fImax protocol\fR
-
-.TP
+.TP 0.2i
\(bu
\fImax smbd processes\fR
-
-.TP
+.TP 0.2i
\(bu
\fImax ttl\fR
-
-.TP
+.TP 0.2i
\(bu
\fImax wins ttl\fR
-
-.TP
+.TP 0.2i
\(bu
\fImax xmit\fR
-
-.TP
+.TP 0.2i
\(bu
\fImessage command\fR
-
-.TP
+.TP 0.2i
\(bu
\fImin passwd length\fR
-
-.TP
+.TP 0.2i
\(bu
\fImin password length\fR
-
-.TP
+.TP 0.2i
\(bu
\fImin protocol\fR
-
-.TP
+.TP 0.2i
\(bu
\fImin wins ttl\fR
-
-.TP
+.TP 0.2i
\(bu
\fIname cache timeout\fR
-
-.TP
+.TP 0.2i
\(bu
\fIname resolve order\fR
-
-.TP
+.TP 0.2i
\(bu
\fInetbios aliases\fR
-
-.TP
+.TP 0.2i
\(bu
\fInetbios name\fR
-
-.TP
+.TP 0.2i
\(bu
\fInetbios scope\fR
-
-.TP
+.TP 0.2i
\(bu
\fInis homedir\fR
-
-.TP
-\(bu
-\fInon unix account range\fR
-
-.TP
+.TP 0.2i
\(bu
\fIntlm auth\fR
-
-.TP
+.TP 0.2i
+\(bu
+\fInon unix account range\fR
+.TP 0.2i
\(bu
\fInt pipe support\fR
-
-.TP
+.TP 0.2i
\(bu
\fInt status support\fR
-
-.TP
+.TP 0.2i
\(bu
\fInull passwords\fR
-
-.TP
+.TP 0.2i
\(bu
\fIobey pam restrictions\fR
-
-.TP
+.TP 0.2i
\(bu
\fIoplock break wait time\fR
-
-.TP
-\(bu
-\fIos2 driver map\fR
-
-.TP
+.TP 0.2i
\(bu
\fIos level\fR
-
-.TP
+.TP 0.2i
+\(bu
+\fIos2 driver map\fR
+.TP 0.2i
\(bu
\fIpam password change\fR
-
-.TP
+.TP 0.2i
\(bu
\fIpanic action\fR
-
-.TP
+.TP 0.2i
\(bu
\fIparanoid server security\fR
-
-.TP
+.TP 0.2i
\(bu
\fIpassdb backend\fR
-
-.TP
-\(bu
-\fIpasswd chat debug\fR
-
-.TP
+.TP 0.2i
\(bu
\fIpasswd chat\fR
-
-.TP
+.TP 0.2i
+\(bu
+\fIpasswd chat debug\fR
+.TP 0.2i
\(bu
\fIpasswd program\fR
-
-.TP
+.TP 0.2i
\(bu
\fIpassword level\fR
-
-.TP
+.TP 0.2i
\(bu
\fIpassword server\fR
-
-.TP
-\(bu
-\fIpid directory\fR
-
-.TP
+.TP 0.2i
\(bu
\fIprefered master\fR
-
-.TP
+.TP 0.2i
\(bu
\fIpreferred master\fR
-
-.TP
-\(bu
-\fIpreload modules\fR
-
-.TP
+.TP 0.2i
\(bu
\fIpreload\fR
-
-.TP
+.TP 0.2i
\(bu
\fIprintcap\fR
-
-.TP
+.TP 0.2i
+\(bu
+\fIprintcap name\fR
+.TP 0.2i
+\(bu
+\fIprinter driver file\fR
+.TP 0.2i
\(bu
\fIprivate dir\fR
-
-.TP
+.TP 0.2i
\(bu
\fIprotocol\fR
-
-.TP
+.TP 0.2i
\(bu
\fIread bmpx\fR
-
-.TP
+.TP 0.2i
\(bu
\fIread raw\fR
-
-.TP
+.TP 0.2i
\(bu
\fIread size\fR
-
-.TP
+.TP 0.2i
\(bu
\fIrealm\fR
-
-.TP
+.TP 0.2i
\(bu
\fIremote announce\fR
-
-.TP
+.TP 0.2i
\(bu
\fIremote browse sync\fR
-
-.TP
+.TP 0.2i
\(bu
\fIrestrict anonymous\fR
-
-.TP
+.TP 0.2i
\(bu
-\fIroot directory\fR
-
-.TP
+\fIroot\fR
+.TP 0.2i
\(bu
\fIroot dir\fR
-
-.TP
+.TP 0.2i
\(bu
-\fIroot\fR
-
-.TP
+\fIroot directory\fR
+.TP 0.2i
\(bu
\fIsecurity\fR
-
-.TP
-\(bu
-\fIserver schannel\fR
-
-.TP
+.TP 0.2i
\(bu
\fIserver string\fR
-
-.TP
-\(bu
-\fIset primary group script\fR
-
-.TP
+.TP 0.2i
\(bu
\fIshow add printer wizard\fR
-
-.TP
+.TP 0.2i
\(bu
\fIshutdown script\fR
-
-.TP
+.TP 0.2i
\(bu
\fIsmb passwd file\fR
-
-.TP
+.TP 0.2i
\(bu
\fIsmb ports\fR
-
-.TP
+.TP 0.2i
\(bu
\fIsocket address\fR
-
-.TP
+.TP 0.2i
\(bu
\fIsocket options\fR
-
-.TP
+.TP 0.2i
\(bu
\fIsource environment\fR
-
-.TP
+.TP 0.2i
\(bu
-\fIstat cache size\fR
-
-.TP
+\fIuse spnego\fR
+.TP 0.2i
\(bu
\fIstat cache\fR
-
-.TP
+.TP 0.2i
\(bu
-\fIstrip dot\fR
-
-.TP
+\fIstat cache size\fR
+.TP 0.2i
\(bu
-\fIsyslog only\fR
-
-.TP
+\fIstrip dot\fR
+.TP 0.2i
\(bu
\fIsyslog\fR
-
-.TP
+.TP 0.2i
+\(bu
+\fIsyslog only\fR
+.TP 0.2i
\(bu
\fItemplate homedir\fR
-
-.TP
+.TP 0.2i
\(bu
\fItemplate shell\fR
-
-.TP
+.TP 0.2i
\(bu
\fItime offset\fR
-
-.TP
+.TP 0.2i
\(bu
\fItime server\fR
-
-.TP
+.TP 0.2i
\(bu
\fItimestamp logs\fR
-
-.TP
+.TP 0.2i
\(bu
\fItotal print jobs\fR
-
-.TP
+.TP 0.2i
\(bu
\fIunicode\fR
-
-.TP
+.TP 0.2i
\(bu
\fIunix charset\fR
-
-.TP
+.TP 0.2i
\(bu
\fIunix extensions\fR
-
-.TP
+.TP 0.2i
\(bu
\fIunix password sync\fR
-
-.TP
+.TP 0.2i
\(bu
\fIupdate encrypted\fR
-
-.TP
+.TP 0.2i
\(bu
\fIuse mmap\fR
-
-.TP
+.TP 0.2i
+\(bu
+\fIuse rhosts\fR
+.TP 0.2i
+\(bu
+\fIuse sendfile\fR
+.TP 0.2i
\(bu
\fIusername level\fR
-
-.TP
+.TP 0.2i
\(bu
\fIusername map\fR
-
-.TP
+.TP 0.2i
\(bu
-\fIuse spnego\fR
-
-.TP
+\fIutmp\fR
+.TP 0.2i
\(bu
\fIutmp directory\fR
-
-.TP
+.TP 0.2i
\(bu
-\fIutmp\fR
-
-.TP
+\fIwtmp directory\fR
+.TP 0.2i
\(bu
\fIwinbind cache time\fR
-
-.TP
-\(bu
-\fIwinbind enum groups\fR
-
-.TP
+.TP 0.2i
\(bu
\fIwinbind enum users\fR
-
-.TP
+.TP 0.2i
+\(bu
+\fIwinbind enum groups\fR
+.TP 0.2i
\(bu
\fIwinbind gid\fR
-
-.TP
+.TP 0.2i
\(bu
\fIwinbind separator\fR
-
-.TP
+.TP 0.2i
\(bu
\fIwinbind uid\fR
-
-.TP
+.TP 0.2i
\(bu
-\fIwinbind used default domain\fR
-
-.TP
+\fIwinbind use default domain\fR
+.TP 0.2i
\(bu
\fIwins hook\fR
-
-.TP
+.TP 0.2i
\(bu
-\fIwins partner\fR
-
-.TP
+\fIwins partners\fR
+.TP 0.2i
\(bu
\fIwins proxy\fR
-
-.TP
+.TP 0.2i
\(bu
\fIwins server\fR
-
-.TP
+.TP 0.2i
\(bu
\fIwins support\fR
-
-.TP
+.TP 0.2i
\(bu
\fIworkgroup\fR
-
-.TP
+.TP 0.2i
\(bu
\fIwrite raw\fR
-
-.TP
-\(bu
-\fIwtmp directory\fR
-
-.LP
-
.SH "COMPLETE LIST OF SERVICE PARAMETERS"
-
.PP
-Here is a list of all service parameters\&. See the section on each parameter for details\&. Note that some are synonyms\&.
-
-.TP 3
+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
\fIadmin users\fR
-
-.TP
+.TP 0.2i
\(bu
\fIallow hosts\fR
-
-.TP
+.TP 0.2i
\(bu
\fIavailable\fR
-
-.TP
+.TP 0.2i
\(bu
\fIblocking locks\fR
-
-.TP
+.TP 0.2i
\(bu
\fIblock size\fR
-
-.TP
+.TP 0.2i
\(bu
\fIbrowsable\fR
-
-.TP
+.TP 0.2i
\(bu
\fIbrowseable\fR
-
-.TP
+.TP 0.2i
\(bu
\fIcase sensitive\fR
-
-.TP
+.TP 0.2i
\(bu
\fIcasesignames\fR
-
-.TP
+.TP 0.2i
\(bu
\fIcomment\fR
-
-.TP
+.TP 0.2i
\(bu
\fIcopy\fR
-
-.TP
+.TP 0.2i
\(bu
\fIcreate mask\fR
-
-.TP
+.TP 0.2i
\(bu
\fIcreate mode\fR
-
-.TP
+.TP 0.2i
\(bu
\fIcsc policy\fR
-
-.TP
+.TP 0.2i
\(bu
\fIdefault case\fR
-
-.TP
+.TP 0.2i
\(bu
\fIdefault devmode\fR
-
-.TP
+.TP 0.2i
\(bu
\fIdelete readonly\fR
-
-.TP
+.TP 0.2i
\(bu
\fIdelete veto files\fR
-
-.TP
+.TP 0.2i
\(bu
\fIdeny hosts\fR
-
-.TP
+.TP 0.2i
+\(bu
+\fIdirectory\fR
+.TP 0.2i
\(bu
\fIdirectory mask\fR
-
-.TP
+.TP 0.2i
\(bu
\fIdirectory mode\fR
-
-.TP
+.TP 0.2i
\(bu
\fIdirectory security mask\fR
-
-.TP
-\(bu
-\fIdirectory\fR
-
-.TP
+.TP 0.2i
\(bu
\fIdont descend\fR
-
-.TP
+.TP 0.2i
\(bu
\fIdos filemode\fR
-
-.TP
+.TP 0.2i
\(bu
\fIdos filetime resolution\fR
-
-.TP
+.TP 0.2i
\(bu
\fIdos filetimes\fR
-
-.TP
+.TP 0.2i
\(bu
\fIexec\fR
-
-.TP
+.TP 0.2i
\(bu
\fIfake directory create times\fR
-
-.TP
+.TP 0.2i
\(bu
\fIfake oplocks\fR
-
-.TP
+.TP 0.2i
\(bu
\fIfollow symlinks\fR
-
-.TP
+.TP 0.2i
\(bu
\fIforce create mode\fR
-
-.TP
+.TP 0.2i
\(bu
\fIforce directory mode\fR
-
-.TP
+.TP 0.2i
\(bu
\fIforce directory security mode\fR
-
-.TP
+.TP 0.2i
\(bu
\fIforce group\fR
-
-.TP
+.TP 0.2i
\(bu
\fIforce security mode\fR
-
-.TP
+.TP 0.2i
\(bu
\fIforce user\fR
-
-.TP
+.TP 0.2i
\(bu
\fIfstype\fR
-
-.TP
+.TP 0.2i
\(bu
\fIgroup\fR
-
-.TP
+.TP 0.2i
\(bu
\fIguest account\fR
-
-.TP
+.TP 0.2i
\(bu
\fIguest ok\fR
-
-.TP
+.TP 0.2i
\(bu
\fIguest only\fR
-
-.TP
+.TP 0.2i
\(bu
\fIhide dot files\fR
-
-.TP
+.TP 0.2i
\(bu
\fIhide files\fR
-
-.TP
-\(bu
-\fIhide special files\fR
-
-.TP
-\(bu
-\fIhide unreadable\fR
-
-.TP
-\(bu
-\fIhide unwriteable files\fR
-
-.TP
+.TP 0.2i
\(bu
\fIhosts allow\fR
-
-.TP
+.TP 0.2i
\(bu
\fIhosts deny\fR
-
-.TP
+.TP 0.2i
+\(bu
+\fIinclude\fR
+.TP 0.2i
\(bu
\fIinherit acls\fR
-
-.TP
+.TP 0.2i
\(bu
\fIinherit permissions\fR
-
-.TP
+.TP 0.2i
\(bu
\fIinvalid users\fR
-
-.TP
+.TP 0.2i
\(bu
\fIlevel2 oplocks\fR
-
-.TP
+.TP 0.2i
\(bu
\fIlocking\fR
-
-.TP
+.TP 0.2i
\(bu
\fIlppause command\fR
-
-.TP
+.TP 0.2i
\(bu
\fIlpq command\fR
-
-.TP
+.TP 0.2i
\(bu
\fIlpresume command\fR
-
-.TP
+.TP 0.2i
\(bu
\fIlprm command\fR
-
-.TP
+.TP 0.2i
\(bu
\fImagic output\fR
-
-.TP
+.TP 0.2i
\(bu
\fImagic script\fR
-
-.TP
+.TP 0.2i
\(bu
\fImangle case\fR
-
-.TP
+.TP 0.2i
\(bu
\fImangled map\fR
-
-.TP
+.TP 0.2i
\(bu
\fImangled names\fR
-
-.TP
+.TP 0.2i
\(bu
\fImangling char\fR
-
-.TP
+.TP 0.2i
+\(bu
+\fImangling method\fR
+.TP 0.2i
\(bu
\fImap archive\fR
-
-.TP
+.TP 0.2i
\(bu
\fImap hidden\fR
-
-.TP
+.TP 0.2i
\(bu
\fImap system\fR
-
-.TP
+.TP 0.2i
\(bu
\fImax connections\fR
-
-.TP
+.TP 0.2i
\(bu
\fImax print jobs\fR
-
-.TP
+.TP 0.2i
\(bu
\fImin print space\fR
-
-.TP
+.TP 0.2i
\(bu
\fImsdfs proxy\fR
-
-.TP
+.TP 0.2i
\(bu
\fImsdfs root\fR
-
-.TP
+.TP 0.2i
\(bu
\fInt acl support\fR
-
-.TP
+.TP 0.2i
\(bu
\fIonly guest\fR
-
-.TP
+.TP 0.2i
\(bu
\fIonly user\fR
-
-.TP
+.TP 0.2i
\(bu
\fIoplock contention limit\fR
-
-.TP
+.TP 0.2i
\(bu
\fIoplocks\fR
-
-.TP
+.TP 0.2i
\(bu
\fIpath\fR
-
-.TP
+.TP 0.2i
\(bu
\fIposix locking\fR
-
-.TP
+.TP 0.2i
\(bu
\fIpostexec\fR
-
-.TP
+.TP 0.2i
\(bu
-\fIpreexec close\fR
-
-.TP
+\fIpostscript\fR
+.TP 0.2i
\(bu
\fIpreexec\fR
-
-.TP
+.TP 0.2i
+\(bu
+\fIpreexec close\fR
+.TP 0.2i
\(bu
\fIpreserve case\fR
-
-.TP
+.TP 0.2i
\(bu
-\fIprintable\fR
-
-.TP
+\fIprint command\fR
+.TP 0.2i
\(bu
-\fIprintcap name\fR
-
-.TP
+\fIprint ok\fR
+.TP 0.2i
\(bu
-\fIprint command\fR
-
-.TP
+\fIprintable\fR
+.TP 0.2i
+\(bu
+\fIprinter\fR
+.TP 0.2i
\(bu
\fIprinter admin\fR
-
-.TP
+.TP 0.2i
\(bu
-\fIprinter name\fR
-
-.TP
+\fIprinter driver\fR
+.TP 0.2i
\(bu
-\fIprinter\fR
-
-.TP
+\fIprinter driver location\fR
+.TP 0.2i
\(bu
-\fIprinting\fR
-
-.TP
+\fIprinter name\fR
+.TP 0.2i
\(bu
-\fIprint ok\fR
-
-.TP
+\fIprinting\fR
+.TP 0.2i
\(bu
\fIpublic\fR
-
-.TP
+.TP 0.2i
\(bu
\fIqueuepause command\fR
-
-.TP
+.TP 0.2i
\(bu
\fIqueueresume command\fR
-
-.TP
+.TP 0.2i
\(bu
\fIread list\fR
-
-.TP
+.TP 0.2i
\(bu
\fIread only\fR
-
-.TP
+.TP 0.2i
\(bu
\fIroot postexec\fR
-
-.TP
-\(bu
-\fIroot preexec close\fR
-
-.TP
+.TP 0.2i
\(bu
\fIroot preexec\fR
-
-.TP
+.TP 0.2i
+\(bu
+\fIroot preexec close\fR
+.TP 0.2i
\(bu
\fIsecurity mask\fR
-
-.TP
+.TP 0.2i
\(bu
\fIset directory\fR
-
-.TP
+.TP 0.2i
\(bu
\fIshare modes\fR
-
-.TP
+.TP 0.2i
\(bu
\fIshort preserve case\fR
-
-.TP
+.TP 0.2i
\(bu
\fIstrict allocate\fR
-
-.TP
+.TP 0.2i
\(bu
\fIstrict locking\fR
-
-.TP
+.TP 0.2i
\(bu
\fIstrict sync\fR
-
-.TP
+.TP 0.2i
\(bu
\fIsync always\fR
-
-.TP
+.TP 0.2i
\(bu
\fIuse client driver\fR
-
-.TP
+.TP 0.2i
+\(bu
+\fIuser\fR
+.TP 0.2i
\(bu
\fIusername\fR
-
-.TP
+.TP 0.2i
\(bu
\fIusers\fR
-
-.TP
-\(bu
-\fIuser\fR
-
-.TP
-\(bu
-\fIuse sendfile\fR
-
-.TP
+.TP 0.2i
\(bu
\fIvalid users\fR
-
-.TP
+.TP 0.2i
\(bu
\fIveto files\fR
-
-.TP
+.TP 0.2i
\(bu
\fIveto oplock files\fR
-
-.TP
+.TP 0.2i
+\(bu
+\fIvfs path\fR
+.TP 0.2i
\(bu
\fIvfs object\fR
-
-.TP
+.TP 0.2i
\(bu
\fIvfs options\fR
-
-.TP
-\(bu
-\fIvfs path\fR
-
-.TP
+.TP 0.2i
\(bu
\fIvolume\fR
-
-.TP
+.TP 0.2i
\(bu
\fIwide links\fR
-
-.TP
+.TP 0.2i
\(bu
\fIwritable\fR
-
-.TP
-\(bu
-\fIwriteable\fR
-
-.TP
+.TP 0.2i
\(bu
\fIwrite cache size\fR
-
-.TP
+.TP 0.2i
\(bu
\fIwrite list\fR
-
-.TP
+.TP 0.2i
\(bu
\fIwrite ok\fR
-
-.LP
-
+.TP 0.2i
+\(bu
+\fIwriteable\fR
.SH "EXPLANATION OF EACH PARAMETER"
-
.TP
-abort shutdown script (G)
-\fBThis parameter only exists in the HEAD cvs branch\fR This a full path name to a script called by \fBsmbd\fR(8) that should stop a shutdown procedure issued by the \fIshutdown script\fR\&.
+\fBabort shutdown script (G)\fR
+\fBThis parameter only exists in the HEAD cvs branch\fR
+This a full path name to a script called by
+\fBsmbd(8)\fR that
+should stop a shutdown procedure issued by the \fIshutdown script\fR.
+This command will be run as user.
-This command will be run as user\&.
-
-
-Default: \fBNone\fR\&.
-
+Default: \fBNone\fR.
Example: \fBabort shutdown script = /sbin/shutdown -c\fR
-
-
.TP
-add group script (G)
-This is the full pathname to a script that will be run \fBAS ROOT\fR by \fBsmbd\fR(8) when a new group is requested\&. It will expand any \fI%g\fR to the group name passed\&. This script is only useful for installations using the Windows NT domain administration tools\&. The script is free to create a group with an arbitrary name to circumvent unix group name restrictions\&. In that case the script must print the numeric gid of the created group on stdout\&.
-
-
-.TP
-add machine script (G)
-This is the full pathname to a script that will be run by \fBsmbd\fR(8) when a machine is added to it's domain using the administrator username and password method\&.
-
-
-This option is only required when using sam back-ends tied to the Unix uid method of RID calculation such as smbpasswd\&. This option is only available in Samba 3\&.0\&.
-
-
-Default: \fBadd machine script = <empty string>\fR
-
-
-Example: \fBadd machine script = /usr/sbin/adduser -n -g machines -c Machine -d /dev/null -s /bin/false %u\fR
-
-
-.TP
-addprinter command (G)
-With the introduction of MS-RPC based printing support for Windows NT/2000 clients in Samba 2\&.2, The MS Add Printer Wizard (APW) icon is now also available in the "Printers\&.\&.\&." folder displayed a share listing\&. The APW allows for printers to be add remotely to a Samba or Windows NT/2000 print server\&.
-
-
-For a Samba host this means that the printer must be physically added to the underlying printing system\&. The \fIadd printer command\fR defines a script to be run which will perform the necessary operations for adding the printer to the print system and to add the appropriate service definition to the \fIsmb\&.conf\fR file in order that it can be shared by \fBsmbd\fR(8)\&.
-
-
-The \fIaddprinter command\fR is automatically invoked with the following parameter (in order):
-
-
+\fBaddprinter command (G)\fR
+With the introduction of MS-RPC based printing
+support for Windows NT/2000 clients in Samba 2.2, The MS Add
+Printer Wizard (APW) icon is now also available in the
+"Printers..." folder displayed a share listing. The APW
+allows for printers to be add remotely to a Samba or Windows
+NT/2000 print server.
+
+For a Samba host this means that the printer must be
+physically added to the underlying printing system. The \fIadd
+printer command\fR defines a script to be run which
+will perform the necessary operations for adding the printer
+to the print system and to add the appropriate service definition
+to the \fIsmb.conf\fR file in order that it can be
+shared by \fBsmbd(8)\fR
+
+
+The \fIaddprinter command\fR is
+automatically invoked with the following parameter (in
+order:
+.RS
+.TP 0.2i
+\(bu
\fIprinter name\fR
-
+.TP 0.2i
+\(bu
\fIshare name\fR
-
+.TP 0.2i
+\(bu
\fIport name\fR
-
+.TP 0.2i
+\(bu
\fIdriver name\fR
-
+.TP 0.2i
+\(bu
\fIlocation\fR
-
+.TP 0.2i
+\(bu
\fIWindows 9x driver location\fR
+.RE
-All parameters are filled in from the PRINTER_INFO_2 structure sent 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\&.
-
-
-Once the \fIaddprinter command\fR has been executed, \fBsmbd\fR will reparse the \fI smb\&.conf\fR to determine if the share defined by the APW exists\&. If the sharename is still invalid, then \fBsmbd \fR will return an ACCESS_DENIED error to the client\&.
-
-
-The "add printer command" program can output a single line of text, which Samba will set as the port the new printer is connected to\&. If this line isn't output, Samba won't reload its printer shares\&.
-
+All parameters are filled in from the PRINTER_INFO_2 structure sent
+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.
-See also \fI deleteprinter command\fR, \fIprinting\fR, \fIshow add printer wizard\fR
+Once the \fIaddprinter command\fR has
+been executed, \fBsmbd\fR will reparse the \fI smb.conf\fR to determine if the share defined by the APW
+exists. If the sharename is still invalid, then \fBsmbd
+\fR will return an ACCESS_DENIED error to the client.
+See also \fI deleteprinter command\fR, \fIprinting\fR,
+\fIshow add
+printer wizard\fR
Default: \fBnone\fR
+Example: \fBaddprinter command = /usr/bin/addprinter
+\fR
+.TP
+\fBadd share command (G)\fR
+Samba 2.2.0 introduced the ability to dynamically
+add and delete shares via the Windows NT 4.0 Server Manager. The
+\fIadd share command\fR is used to define an
+external program or script which will add a new service definition
+to \fIsmb.conf\fR. In order to successfully
+execute the \fIadd share command\fR, \fBsmbd\fR
+requires that the administrator be connected using a root account (i.e.
+uid == 0).
+
+When executed, \fBsmbd\fR will automatically invoke the
+\fIadd share command\fR with four parameters.
+.RS
+.TP 0.2i
+\(bu
+\fIconfigFile\fR - the location
+of the global \fIsmb.conf\fR file.
+.TP 0.2i
+\(bu
+\fIshareName\fR - the name of the new
+share.
+.TP 0.2i
+\(bu
+\fIpathName\fR - path to an **existing**
+directory on disk.
+.TP 0.2i
+\(bu
+\fIcomment\fR - comment string to associate
+with the new share.
+.RE
-Example: \fBaddprinter command = /usr/bin/addprinter\fR
-
-
-.TP
-add share command (G)
-Samba 2\&.2\&.0 introduced the ability to dynamically add and delete shares via the Windows NT 4\&.0 Server Manager\&. The \fIadd share command\fR is used to define an external program or script which will add a new service definition to \fIsmb\&.conf\fR\&. In order to successfully execute the \fIadd share command\fR, \fBsmbd\fR requires that the administrator be connected using a root account (i\&.e\&. uid == 0)\&.
-
-
-When executed, \fBsmbd\fR will automatically invoke the \fIadd share command\fR with four parameters\&.
-
-
-\fIconfigFile\fR - the location of the global \fIsmb\&.conf\fR file\&.
-
-\fIshareName\fR - the name of the new share\&.
-
-\fIpathName\fR - path to an **existing** directory on disk\&.
-
-\fIcomment\fR - comment string to associate with the new share\&.
-
-This parameter is only used for add file shares\&. To add printer shares, see the \fIaddprinter command\fR\&.
-
-
-See also \fIchange share command\fR, \fIdelete share command\fR\&.
+This parameter is only used for add file shares. To add printer shares,
+see the \fIaddprinter
+command\fR.
+See also \fIchange share
+command\fR, \fIdelete share
+command\fR.
Default: \fBnone\fR
-
Example: \fBadd share command = /usr/local/bin/addshare\fR
-
-
.TP
-add user script (G)
-This is the full pathname to a script that will be run \fBAS ROOT\fR by \fBsmbd\fR(8) 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 that use Windows NT account databases as their primary user database creating these users and keeping the user list in sync with the Windows NT PDC is an onerous task\&. This option allows smbd to create the required UNIX users \fBON DEMAND\fR when a user accesses the Samba server\&.
-
-
-In order to use this option, \fBsmbd\fR(8) must \fBNOT\fR be set to \fIsecurity = share\fR and \fIadd user script\fR must be set to a full pathname for a script that will create a UNIX user given one argument of \fI%u\fR, which expands into the UNIX user name to create\&.
-
-
-When the Windows user attempts to access the Samba server, at login (session setup in the SMB protocol) time, \fBsmbd\fR(8) contacts the \fIpassword server\fR and attempts to authenticate the given user with the given password\&. If the authentication succeeds then \fBsmbd\fR attempts to find a UNIX user in the UNIX password database to map the Windows user into\&. If this lookup fails, and \fIadd user script \fR is set then \fBsmbd\fR will call the specified script \fBAS ROOT\fR, expanding any \fI%u\fR argument to be the user name to create\&.
-
-
-If this script successfully creates the user then \fBsmbd \fR will continue on as though the UNIX user already existed\&. In this way, UNIX users are dynamically created to match existing Windows NT accounts\&.
-
-
-See also \fI security\fR, \fIpassword server\fR, \fIdelete user script\fR\&.
+\fBadd machine script (G)\fR
+This is the full pathname to a script that will
+be run by smbd(8) when a machine is added
+to it's domain using the administrator username and password method.
+This option is only required when using sam back-ends tied to the
+Unix uid method of RID calculation such as smbpasswd. This option is only
+available in Samba 3.0.
-Default: \fBadd user script = <empty string>\fR
-
-
-Example: \fBadd user script = /usr/local/samba/bin/add_user %u\fR
-
+Default: \fBadd machine script = <empty string>
+\fR
+Example: \fBadd machine script = /usr/sbin/adduser -n -g machines -c Machine -d /dev/null -s /bin/false %u
+\fR
.TP
-add user to group script (G)
-Full path to the script that will be called when a user is added to a group using the Windows NT domain administration tools\&. It will be run by \fBsmbd\fR(8) \fBAS ROOT\fR\&. Any \fI%g\fR will be replaced with the group name and any \fI%u\fR will be replaced with the user name\&.
-
-
-Default: \fBadd user to group script = \fR
-
-
-Example: \fBadd user to group script = /usr/sbin/adduser %u %g\fR
+\fBads server (G)\fR
+If this option is specified, samba does
+not try to figure out what ads server to use itself, but
+uses the specified ads server. Either one DNS name or IP
+address can be used.
+Default: \fBads server = \fR
+Example: \fBads server = 192.168.1.2\fR
.TP
-admin users (S)
-This is a list of users who will be granted administrative privileges on the share\&. This means that they will do all file operations as the super-user (root)\&.
-
-
-You should use this option very carefully, as any user in this list will be able to do anything they like on the share, irrespective of file permissions\&.
-
+\fBadd user script (G)\fR
+This is the full pathname to a script that will
+be run \fBAS ROOT\fR by smbd(8)
+ 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
+that use Windows NT account databases as their primary user database
+creating these users and keeping the user list in sync with the
+Windows NT PDC is an onerous task. This option allows smbd to create the required UNIX users
+\fBON DEMAND\fR when a user accesses the Samba server.
+
+In order to use this option, smbd
+must \fBNOT\fR be set to \fIsecurity = share\fR
+and \fIadd user script\fR
+must be set to a full pathname for a script that will create a UNIX
+user given one argument of \fI%u\fR, which expands into
+the UNIX user name to create.
+
+When the Windows user attempts to access the Samba server,
+at login (session setup in the SMB protocol) time, smbd contacts the \fIpassword server\fR and
+attempts to authenticate the given user with the given password. If the
+authentication succeeds then \fBsmbd\fR
+attempts to find a UNIX user in the UNIX password database to map the
+Windows user into. If this lookup fails, and \fIadd user script
+\fR is set then \fBsmbd\fR will
+call the specified script \fBAS ROOT\fR, expanding
+any \fI%u\fR argument to be the user name to create.
+
+If this script successfully creates the user then \fBsmbd
+\fR will continue on as though the UNIX user
+already existed. In this way, UNIX users are dynamically created to
+match existing Windows NT accounts.
+
+See also \fI security\fR, \fIpassword server\fR,
+\fIdelete user
+script\fR.
+
+Default: \fBadd user script = <empty string>
+\fR
+
+Example: \fBadd user script = /usr/local/samba/bin/add_user
+%u\fR
+.TP
+\fBadd group script (G)\fR
+This is the full pathname to a script that will
+be run \fBAS ROOT\fR by smbd(8) when a new group is
+requested. It will expand any
+\fI%g\fR to the group name passed.
+This script is only useful for installations using the
+Windows NT domain administration tools. The script is
+free to create a group with an arbitrary name to
+circumvent unix group name restrictions. In that case
+the script must print the numeric gid of the created
+group on stdout.
+.TP
+\fBadmin users (S)\fR
+This is a list of users who will be granted
+administrative privileges on the share. This means that they
+will do all file operations as the super-user (root).
+
+You should use this option very carefully, as any user in
+this list will be able to do anything they like on the share,
+irrespective of file permissions.
Default: \fBno admin users\fR
-
Example: \fBadmin users = jason\fR
-
-
.TP
-ads server (G)
-If this option is specified, samba does not try to figure out what ads server to use itself, but uses the specified ads server\&. Either one DNS name or IP address can be used\&.
-
-
-Default: \fBads server = \fR
-
-
-Example: \fBads server = 192.168.1.2\fR
+\fBadd user to group script (G)\fR
+Full path to the script that will be called when
+a user is added to a group using the Windows NT domain administration
+tools. It will be run by smbd(8)
+\fBAS ROOT\fR. Any \fI%g\fR will be
+replaced with the group name and any \fI%u\fR will
+be replaced with the user name.
+Default: \fBadd user to group script = \fR
+Example: \fBadd user to group script = /usr/sbin/adduser %u %g\fR
.TP
-algorithmic rid base (G)
-This determines how Samba will use its algorithmic mapping from uids/gid to the RIDs needed to construct NT Security Identifiers\&.
-
-
-Setting this option to a larger value could be useful to sites transitioning from WinNT and Win2k, as existing user and group rids would otherwise clash with sytem users etc\&.
-
+\fBallow hosts (S)\fR
+Synonym for \fIhosts allow\fR.
+.TP
+\fBalgorithmic rid base (G)\fR
+This determines how Samba will use its
+algorithmic mapping from uids/gid to the RIDs needed to construct
+NT Security Identifiers.
-All UIDs and GIDs must be able to be resolved into SIDs for the correct operation of ACLs on the server\&. As such the algorithmic mapping can't be 'turned off', but pushing it 'out of the way' should resolve the issues\&. Users and groups can then be assigned 'low' RIDs in arbitary-rid supporting backends\&.
+Setting this option to a larger value could be useful to sites
+transitioning from WinNT and Win2k, as existing user and
+group rids would otherwise clash with sytem users etc.
+All UIDs and GIDs must be able to be resolved into SIDs for
+the correct operation of ACLs on the server. As such the algorithmic
+mapping can't be 'turned off', but pushing it 'out of the way' should
+resolve the issues. Users and groups can then be assigned 'low' RIDs
+in arbitary-rid supporting backends.
Default: \fBalgorithmic rid base = 1000\fR
-
Example: \fBalgorithmic rid base = 100000\fR
-
-
-.TP
-allow hosts (S)
-Synonym for \fIhosts allow\fR\&.
-
-
.TP
-allow trusted domains (G)
-This option only takes effect when the \fIsecurity\fR option is set to \fBserver\fR or \fBdomain\fR\&. If it is set to no, then attempts to connect to a resource from a domain or workgroup other than the one which smbd is running in will fail, even if that domain is trusted by the remote server doing the authentication\&.
-
-
-This is useful if you only want your Samba server to serve resources to users in the domain it is a member of\&. As an example, suppose that there are two domains DOMA and DOMB\&. DOMB is trusted by DOMA, which contains the Samba server\&. Under normal circumstances, a user with an account in DOMB can then access the resources of a UNIX account with the same account name on the Samba server even if they do not have an account in DOMA\&. This can make implementing a security boundary difficult\&.
-
+\fBallow trusted domains (G)\fR
+This option only takes effect when the \fIsecurity\fR option is set to
+server or domain.
+If it is set to no, then attempts to connect to a resource from
+a domain or workgroup other than the one which smbd is running
+in will fail, even if that domain is trusted by the remote server
+doing the authentication.
+
+This is useful if you only want your Samba server to
+serve resources to users in the domain it is a member of. As
+an example, suppose that there are two domains DOMA and DOMB. DOMB
+is trusted by DOMA, which contains the Samba server. Under normal
+circumstances, a user with an account in DOMB can then access the
+resources of a UNIX account with the same account name on the
+Samba server even if they do not have an account in DOMA. This
+can make implementing a security boundary difficult.
Default: \fBallow trusted domains = yes\fR
-
-
.TP
-announce as (G)
-This specifies what type of server \fBnmbd\fR(8) will announce itself as, to a network neighborhood browse list\&. By default this is set to Windows NT\&. The valid options 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 specific need to stop Samba appearing as an NT server as this may prevent Samba servers from participating as browser servers correctly\&.
-
+\fBannounce as (G)\fR
+This specifies what type of server
+\fBnmbd\fR
+will announce itself as, to a network neighborhood browse
+list. By default this is set to Windows NT. The valid options
+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
+specific need to stop Samba appearing as an NT server as this
+may prevent Samba servers from participating as browser servers
+correctly.
Default: \fBannounce as = NT Server\fR
-
Example: \fBannounce as = Win95\fR
-
-
.TP
-announce version (G)
-This specifies the major and minor version numbers that nmbd will use when announcing itself as a server\&. The default is 4\&.9\&. Do not change this parameter unless you have a specific need to set a Samba server to be a downlevel server\&.
-
+\fBannounce version (G)\fR
+This specifies the major and minor version numbers
+that nmbd will use when announcing itself as a server. The default
+is 4.9. Do not change this parameter unless you have a specific
+need to set a Samba server to be a downlevel server.
Default: \fBannounce version = 4.9\fR
-
Example: \fBannounce version = 2.0\fR
-
-
.TP
-auth methods (G)
-This option allows the administrator to chose what authentication methods \fBsmbd\fR will use when authenticating a user\&. This option defaults to sensible values based on \fIsecurity\fR\&.
-
-
-Each entry in the list attempts to authenticate the user in turn, until the user authenticates\&. In practice only one method will ever actually be able to complete the authentication\&.
-
+\fBauto services (G)\fR
+This is a synonym for the \fIpreload\fR.
+.TP
+\fBauth methods (G)\fR
+This option allows the administrator to chose what
+authentication methods \fBsmbd\fR will use when authenticating
+a user. This option defaults to sensible values based on \fI security\fR.
+Each entry in the list attempts to authenticate the user in turn, until
+the user authenticates. In practice only one method will ever actually
+be able to complete the authentication.
Default: \fBauth methods = <empty string>\fR
-
Example: \fBauth methods = guest sam ntdomain\fR
-
-
.TP
-auto services (G)
-This is a synonym for the \fIpreload\fR\&.
-
-
-.TP
-available (S)
-This parameter lets you "turn off" a service\&. If \fIavailable = no\fR, then \fBALL\fR attempts to connect to the service will fail\&. Such failures are logged\&.
-
+\fBavailable (S)\fR
+This parameter lets you "turn off" a service. If
+\fIavailable = no\fR, then \fBALL\fR
+attempts to connect to the service will fail. Such failures are
+logged.
Default: \fBavailable = yes\fR
-
-
.TP
-bind interfaces only (G)
-This global parameter allows the Samba admin to limit what interfaces on a machine will serve SMB requests\&. It affects file service \fBsmbd\fR(8) and name service \fBnmbd\fR(8) in a slightly different ways\&.
-
-
-For name service it causes \fBnmbd\fR to bind to ports 137 and 138 on the interfaces listed in the interfaces parameter\&. \fBnmbd\fR also binds to the "all addresses" interface (0\&.0\&.0\&.0) on ports 137 and 138 for the purposes of reading broadcast messages\&. If this option is not set then \fBnmbd\fR will service name requests on all of these sockets\&. If \fIbind interfaces only\fR is set then \fBnmbd\fR will check the source address of any packets coming in on the broadcast sockets and discard any that don't match the broadcast addresses of the interfaces in the \fIinterfaces\fR parameter list\&. As unicast packets are received on the other sockets it allows \fBnmbd\fR to refuse to serve names to machines that send packets that arrive through any interfaces not listed in the \fIinterfaces\fR list\&. IP Source address spoofing does defeat this simple check, however, so it must not be used seriously as a security feature for \fBnmbd\fR\&.
-
-
-For file service it causes \fBsmbd\fR(8) to bind only to the interface list given in the interfaces parameter\&. This restricts the networks that \fBsmbd\fR will serve to packets coming in those interfaces\&. Note that you should not use this parameter for machines that are serving PPP or other intermittent or non-broadcast network interfaces as it will not cope with non-permanent interfaces\&.
-
-
-If \fIbind interfaces only\fR is set then unless the network address \fB127\&.0\&.0\&.1\fR is added to the \fIinterfaces\fR parameter list \fBsmbpasswd\fR(8) and \fBswat\fR(8) may not work as expected due to the reasons covered below\&.
-
-
-To change a users SMB password, the \fBsmbpasswd\fR by default connects to the \fBlocalhost - 127\&.0\&.0\&.1\fR address as an SMB client to issue the password change request\&. If \fIbind interfaces only\fR is set then unless the network address \fB127\&.0\&.0\&.1\fR is added to the \fIinterfaces\fR parameter list then \fB smbpasswd\fR will fail to connect in it's default mode\&. \fBsmbpasswd\fR can be forced to use the primary IP interface of the local host by using its \fBsmbpasswd\fR(8) \fI-r remote machine\fR parameter, with \fIremote machine\fR set to the IP name of the primary interface of the local host\&.
-
-
-The \fBswat\fR status page tries to connect with \fBsmbd\fR and \fBnmbd\fR at the address \fB127\&.0\&.0\&.1\fR to determine if they are running\&. Not adding \fB127\&.0\&.0\&.1\fR will cause \fB smbd\fR and \fBnmbd\fR to always show "not running" even if they really are\&. This can prevent \fB swat\fR from starting/stopping/restarting \fBsmbd\fR and \fBnmbd\fR\&.
-
+\fBbind interfaces only (G)\fR
+This global parameter allows the Samba admin
+to limit what interfaces on a machine will serve SMB requests. It
+affects file service smbd(8) and
+name service nmbd(8) in slightly
+different ways.
+
+For name service it causes \fBnmbd\fR to bind
+to ports 137 and 138 on the interfaces listed in the interfaces parameter. \fBnmbd
+\fR also binds to the "all addresses" interface (0.0.0.0)
+on ports 137 and 138 for the purposes of reading broadcast messages.
+If this option is not set then \fBnmbd\fR will service
+name requests on all of these sockets. If \fIbind interfaces
+only\fR is set then \fBnmbd\fR will check the
+source address of any packets coming in on the broadcast sockets
+and discard any that don't match the broadcast addresses of the
+interfaces in the \fIinterfaces\fR parameter list.
+As unicast packets are received on the other sockets it allows
+\fBnmbd\fR to refuse to serve names to machines that
+send packets that arrive through any interfaces not listed in the
+\fIinterfaces\fR list. IP Source address spoofing
+does defeat this simple check, however, so it must not be used
+seriously as a security feature for \fBnmbd\fR.
+
+For file service it causes smbd(8)
+to bind only to the interface list given in the interfaces parameter. This restricts the networks that
+\fBsmbd\fR will serve to packets coming in those
+interfaces. Note that you should not use this parameter for machines
+that are serving PPP or other intermittent or non-broadcast network
+interfaces as it will not cope with non-permanent interfaces.
+
+If \fIbind interfaces only\fR is set then
+unless the network address \fB127.0.0.1\fR is added
+to the \fIinterfaces\fR parameter list \fBsmbpasswd(8)\fR
+and \fBswat(8)\fR may
+not work as expected due to the reasons covered below.
+
+To change a users SMB password, the \fBsmbpasswd\fR
+by default connects to the \fBlocalhost - 127.0.0.1\fR
+address as an SMB client to issue the password change request. If
+\fIbind interfaces only\fR is set then unless the
+network address \fB127.0.0.1\fR is added to the
+\fIinterfaces\fR parameter list then \fB smbpasswd\fR will fail to connect in it's default mode.
+\fBsmbpasswd\fR can be forced to use the primary IP interface
+of the local host by using its \fI-r remote machine\fR
+ parameter, with \fIremote machine\fR set
+to the IP name of the primary interface of the local host.
+
+The \fBswat\fR status page tries to connect with
+\fBsmbd\fR and \fBnmbd\fR at the address
+\fB127.0.0.1\fR to determine if they are running.
+Not adding \fB127.0.0.1\fR will cause \fB smbd\fR and \fBnmbd\fR to always show
+"not running" even if they really are. This can prevent \fB swat\fR from starting/stopping/restarting \fBsmbd\fR
+and \fBnmbd\fR.
Default: \fBbind interfaces only = no\fR
-
-
.TP
-blocking locks (S)
-This parameter controls the behavior of \fBsmbd\fR(8) when given a request by a client to obtain a byte range lock on a region of an open file, and the request has a time limit associated with it\&.
-
-
-If this parameter is set and the lock range requested cannot be immediately satisfied, samba will internally queue the lock request, and periodically attempt to obtain the lock until the timeout period expires\&.
+\fBblocking locks (S)\fR
+This parameter controls the behavior of smbd(8) when given a request by a client
+to obtain a byte range lock on a region of an open file, and the
+request has a time limit associated with it.
+If this parameter is set and the lock range requested
+cannot be immediately satisfied, samba will internally
+queue the lock request, and periodically attempt to obtain
+the lock until the timeout period expires.
-If this parameter is set to \fBno\fR, then samba will behave as previous versions of Samba would and will fail the lock request immediately if the lock range cannot be obtained\&.
-
+If this parameter is set to no, then
+samba will behave as previous versions of Samba would and
+will fail the lock request immediately if the lock range
+cannot be obtained.
Default: \fBblocking locks = yes\fR
-
-
.TP
-block size (S)
-This parameter controls the behavior of \fBsmbd\fR(8) when reporting disk free sizes\&. By default, this reports a disk block size of 1024 bytes\&.
+\fBblock size (S)\fR
+This parameter controls the behavior of
+smbd(8) when reporting disk free
+sizes. By default, this reports a disk block size of 1024 bytes.
+Changing this parameter may have some effect on the
+efficiency of client writes, this is not yet confirmed. This
+parameter was added to allow advanced administrators to change
+it (usually to a higher value) and test the effect it has on
+client write performance without re-compiling the code. As this
+is an experimental option it may be removed in a future release.
-Changing this parameter may have some effect on the efficiency of client writes, this is not yet confirmed\&. This parameter was added to allow advanced administrators to change it (usually to a higher value) and test the effect it has on client write performance without re-compiling the code\&. As this is an experimental option it may be removed in a future release\&.
-
-
-Changing this option does not change the disk free reporting size, just the block size unit reported to the client\&.
-
-
-.TP
-browsable (S)
-See the \fIbrowseable\fR\&.
+Changing this option does not change the disk free reporting
+size, just the block size unit reported to the client.
+Default: \fBblock size = 1024\fR
+Example: \fBblock size = 65536\fR
.TP
-browseable (S)
-This controls whether this share is seen in the list of available shares in a net view and in the browse list\&.
-
-
-Default: \fBbrowseable = yes\fR
-
-
+\fBbrowsable (S)\fR
+See the \fI browseable\fR.
.TP
-browse list (G)
-This controls whether \fBsmbd\fR(8) will serve a browse list to a client doing a \fBNetServerEnum\fR call\&. Normally set to \fByes\fR\&. You should never need to change this\&.
-
+\fBbrowse list (G)\fR
+This controls whether \fBsmbd(8)\fR will serve a browse list to
+a client doing a \fBNetServerEnum\fR call. Normally
+set to yes. You should never need to change
+this.
Default: \fBbrowse list = yes\fR
-
-
.TP
-case sensitive (S)
-See the discussion in the section NAME MANGLING\&.
+\fBbrowseable (S)\fR
+This controls whether this share is seen in
+the list of available shares in a net view and in the browse list.
+Default: \fBbrowseable = yes\fR
+.TP
+\fBcase sensitive (S)\fR
+See the discussion in the section NAME MANGLING.
Default: \fBcase sensitive = no\fR
-
-
.TP
-casesignames (S)
-Synonym for case sensitive\&.
-
-
+\fBcasesignames (S)\fR
+Synonym for case
+sensitive.
.TP
-change notify timeout (G)
-This SMB allows a client to tell a server to "watch" a particular directory for any changes and only reply to the SMB request when a change has occurred\&. Such constant scanning of a directory is expensive under UNIX, hence an \fBsmbd\fR(8) daemon only performs such a scan on each requested directory once every \fIchange notify timeout\fR seconds\&.
-
+\fBchange notify timeout (G)\fR
+This SMB allows a client to tell a server to
+"watch" a particular directory for any changes and only reply to
+the SMB request when a change has occurred. Such constant scanning of
+a directory is expensive under UNIX, hence an \fBsmbd(8)\fR daemon only performs such a scan
+on each requested directory once every \fIchange notify
+timeout\fR seconds.
Default: \fBchange notify timeout = 60\fR
-
Example: \fBchange notify timeout = 300\fR
-
-Would change the scan time to every 5 minutes\&.
-
-
+Would change the scan time to every 5 minutes.
.TP
-change share command (G)
-Samba 2\&.2\&.0 introduced the ability to dynamically add and delete shares via the Windows NT 4\&.0 Server Manager\&. The \fIchange share command\fR is used to define an external program or script which will modify an existing service definition in \fIsmb\&.conf\fR\&. In order to successfully execute the \fIchange share command\fR, \fBsmbd\fR requires that the administrator be connected using a root account (i\&.e\&. uid == 0)\&.
-
-
-When executed, \fBsmbd\fR will automatically invoke the \fIchange share command\fR with four parameters\&.
-
-
-\fIconfigFile\fR - the location of the global \fIsmb\&.conf\fR file\&.
-
-\fIshareName\fR - the name of the new share\&.
-
-\fIpathName\fR - path to an **existing** directory on disk\&.
-
-\fIcomment\fR - comment string to associate with the new share\&.
-
-This parameter is only used modify existing file shares definitions\&. To modify printer shares, use the "Printers\&.\&.\&." folder as seen when browsing the Samba host\&.
+\fBchange share command (G)\fR
+Samba 2.2.0 introduced the ability to dynamically
+add and delete shares via the Windows NT 4.0 Server Manager. The
+\fIchange share command\fR is used to define an
+external program or script which will modify an existing service definition
+in \fIsmb.conf\fR. In order to successfully
+execute the \fIchange share command\fR, \fBsmbd\fR
+requires that the administrator be connected using a root account (i.e.
+uid == 0).
+When executed, \fBsmbd\fR will automatically invoke the
+\fIchange share command\fR with four parameters.
+.RS
+.TP 0.2i
+\(bu
+\fIconfigFile\fR - the location
+of the global \fIsmb.conf\fR file.
+.TP 0.2i
+\(bu
+\fIshareName\fR - the name of the new
+share.
+.TP 0.2i
+\(bu
+\fIpathName\fR - path to an **existing**
+directory on disk.
+.TP 0.2i
+\(bu
+\fIcomment\fR - comment string to associate
+with the new share.
+.RE
-See also \fIadd share command\fR, \fIdelete share command\fR\&.
+This parameter is only used modify existing file shares definitions. To modify
+printer shares, use the "Printers..." folder as seen when browsing the Samba host.
+See also \fIadd share
+command\fR, \fIdelete
+share command\fR.
Default: \fBnone\fR
-
Example: \fBchange share command = /usr/local/bin/addshare\fR
-
-
.TP
-comment (S)
-This is a text field that is seen next to a share when a client does a queries the server, either via the network neighborhood or via \fBnet view\fR to list what shares are available\&.
-
-
-If you want to set the string that is displayed next to the machine name then see the \fI server string\fR parameter\&.
+\fBcomment (S)\fR
+This is a text field that is seen next to a share
+when a client does a queries the server, either via the network
+neighborhood or via \fBnet view\fR to list what shares
+are available.
+If you want to set the string that is displayed next to the
+machine name then see the \fI server string\fR parameter.
Default: \fBNo comment string\fR
-
Example: \fBcomment = Fred's Files\fR
-
-
.TP
-config file (G)
-This allows you to override the config file to use, instead of the default (usually \fIsmb\&.conf\fR)\&. There is a chicken and egg problem here as this option is set in the config file!
-
-
-For this reason, if the name of the config file has changed when the parameters are loaded then it will reload them from the new config file\&.
-
+\fBconfig file (G)\fR
+This allows you to override the config file
+to use, instead of the default (usually \fIsmb.conf\fR).
+There is a chicken and egg problem here as this option is set
+in the config file!
-This option takes the usual substitutions, which can be very useful\&.
+For this reason, if the name of the config file has changed
+when the parameters are loaded then it will reload them from
+the new config file.
+This option takes the usual substitutions, which can
+be very useful.
-If the config file doesn't exist then it won't be loaded (allowing you to special case the config files of just a few clients)\&.
-
-
-Example: \fBconfig file = /usr/local/samba/lib/smb.conf.%m\fR
-
+If the config file doesn't exist then it won't be loaded
+(allowing you to special case the config files of just a few
+clients).
+Example: \fBconfig file = /usr/local/samba/lib/smb.conf.%m
+\fR
.TP
-copy (S)
-This parameter allows you to "clone" service entries\&. The specified service is simply duplicated under the current service's name\&. Any parameters specified in the current section will override those in the section being copied\&.
-
-
-This feature lets you set up a 'template' service and create similar services easily\&. Note that the service being copied must occur earlier in the configuration file than the service doing the copying\&.
+\fBcopy (S)\fR
+This parameter allows you to "clone" service
+entries. The specified service is simply duplicated under the
+current service's name. Any parameters specified in the current
+section will override those in the section being copied.
+This feature lets you set up a 'template' service and
+create similar services easily. Note that the service being
+copied must occur earlier in the configuration file than the
+service doing the copying.
Default: \fBno value\fR
-
Example: \fBcopy = otherservice\fR
-
-
.TP
-create mask (S)
-A synonym for this parameter is \fIcreate mode\fR \&.
-
-
-When a file is created, the necessary permissions are calculated according to the mapping from DOS modes to UNIX permissions, and the resulting UNIX mode is then bit-wise 'AND'ed with this parameter\&. This parameter may be thought of as a bit-wise MASK for the UNIX modes of a file\&. Any bit \fBnot\fR set here will be removed from the modes set on a file when it is created\&.
-
-
-The default value of this parameter removes the 'group' and 'other' write and execute bits from the UNIX modes\&.
-
-
-Following this Samba will bit-wise 'OR' the UNIX mode created from this parameter with the value of the \fIforce create mode\fR parameter which is set to 000 by default\&.
-
+\fBcreate mask (S)\fR
+A synonym for this parameter is
+\fIcreate mode\fR
+\&.
-This parameter does not affect directory modes\&. See the parameter \fIdirectory mode \fR for details\&.
+When a file is created, the necessary permissions are
+calculated according to the mapping from DOS modes to UNIX
+permissions, and the resulting UNIX mode is then bit-wise 'AND'ed
+with this parameter. This parameter may be thought of as a bit-wise
+MASK for the UNIX modes of a file. Any bit \fBnot\fR
+set here will be removed from the modes set on a file when it is
+created.
+The default value of this parameter removes the
+\&'group' and 'other' write and execute bits from the UNIX modes.
-See also the \fIforce create mode\fR parameter for forcing particular mode bits to be set on created files\&. See also the \fIdirectory mode\fR parameter for masking mode bits on created directories\&. See also the \fIinherit permissions\fR parameter\&.
+Following this Samba will bit-wise 'OR' the UNIX mode created
+from this parameter with the value of the \fIforce create mode\fR
+parameter which is set to 000 by default.
+This parameter does not affect directory modes. See the
+parameter \fIdirectory mode
+\fR for details.
-Note that this parameter does not apply to permissions set by Windows NT/2000 ACL editors\&. If the administrator wishes to enforce a mask on access control lists also, they need to set the \fIsecurity mask\fR\&.
+See also the \fIforce
+create mode\fR parameter for forcing particular mode
+bits to be set on created files. See also the \fIdirectory mode\fR parameter for masking
+mode bits on created directories. See also the \fIinherit permissions\fR parameter.
+Note that this parameter does not apply to permissions
+set by Windows NT/2000 ACL editors. If the administrator wishes to enforce
+a mask on access control lists also, they need to set the \fIsecurity mask\fR.
Default: \fBcreate mask = 0744\fR
-
Example: \fBcreate mask = 0775\fR
-
-
.TP
-create mode (S)
-This is a synonym for \fI create mask\fR\&.
-
-
+\fBcreate mode (S)\fR
+This is a synonym for \fI create mask\fR.
.TP
-csc policy (S)
-This stands for \fBclient-side caching policy\fR, and specifies how clients capable of offline caching will cache the files in the share\&. The valid values are: manual, documents, programs, disable\&.
-
-
-These values correspond to those used on Windows servers\&.
-
+\fBcsc policy (S)\fR
+This stands for \fBclient-side caching
+policy\fR, and specifies how clients capable of offline
+caching will cache the files in the share. The valid values
+are: manual, documents, programs, disable.
-For example, shares containing roaming profiles can have offline caching disabled using \fBcsc policy = disable\fR\&.
+These values correspond to those used on Windows
+servers.
+For example, shares containing roaming profiles can have
+offline caching disabled using \fBcsc policy = disable
+\fR.
Default: \fBcsc policy = manual\fR
-
Example: \fBcsc policy = programs\fR
-
-
.TP
-dead time (G)
-The value of the parameter (a decimal integer) represents the number of minutes of inactivity before a connection is considered dead, and it is disconnected\&. The deadtime only takes effect if the number of open files is zero\&.
-
-
-This is useful to stop a server's resources being exhausted by a large number of inactive connections\&.
-
+\fBdeadtime (G)\fR
+The value of the parameter (a decimal integer)
+represents the number of minutes of inactivity before a connection
+is considered dead, and it is disconnected. The deadtime only takes
+effect if the number of open files is zero.
-Most clients have an auto-reconnect feature when a connection is broken so in most cases this parameter should be transparent to users\&.
+This is useful to stop a server's resources being
+exhausted by a large number of inactive connections.
+Most clients have an auto-reconnect feature when a
+connection is broken so in most cases this parameter should be
+transparent to users.
-Using this parameter with a timeout of a few minutes is recommended for most systems\&.
-
-
-A deadtime of zero indicates that no auto-disconnection should be performed\&.
+Using this parameter with a timeout of a few minutes
+is recommended for most systems.
+A deadtime of zero indicates that no auto-disconnection
+should be performed.
Default: \fBdeadtime = 0\fR
-
Example: \fBdeadtime = 15\fR
-
-
.TP
-debug hires timestamp (G)
-Sometimes the timestamps in the log messages are needed with a resolution of higher that seconds, this boolean parameter adds microsecond resolution to the timestamp message header when turned on\&.
-
-
-Note that the parameter \fI debug timestamp\fR must be on for this to have an effect\&.
+\fBdebug hires timestamp (G)\fR
+Sometimes the timestamps in the log messages
+are needed with a resolution of higher that seconds, this
+boolean parameter adds microsecond resolution to the timestamp
+message header when turned on.
+Note that the parameter \fI debug timestamp\fR must be on for this to have an
+effect.
Default: \fBdebug hires timestamp = no\fR
-
-
-.TP
-debug level (G)
-Synonym for \fI log level\fR\&.
-
-
.TP
-debug pid (G)
-When using only one log file for more then one forked \fBsmbd\fR(8)-process there may be hard to follow which process outputs which message\&. This boolean parameter is adds the process-id to the timestamp message headers in the logfile when turned on\&.
-
-
-Note that the parameter \fI debug timestamp\fR must be on for this to have an effect\&.
+\fBdebug pid (G)\fR
+When using only one log file for more then one
+forked smbdprocess there may be hard to follow which process
+outputs which message. This boolean parameter is adds the process-id
+to the timestamp message headers in the logfile when turned on.
+Note that the parameter \fI debug timestamp\fR must be on for this to have an
+effect.
Default: \fBdebug pid = no\fR
-
-
.TP
-debug timestamp (G)
-Samba debug log messages are timestamped by default\&. If you are running at a high \fIdebug level\fR these timestamps can be distracting\&. This boolean parameter allows timestamping to be turned off\&.
-
+\fBdebug timestamp (G)\fR
+Samba debug log messages are timestamped
+by default. If you are running at a high \fIdebug level\fR these timestamps
+can be distracting. This boolean parameter allows timestamping
+to be turned off.
Default: \fBdebug timestamp = yes\fR
-
-
.TP
-debug uid (G)
-Samba is sometimes run as root and sometime run as the connected user, this boolean parameter inserts the current euid, egid, uid and gid to the timestamp message headers in the log file if turned on\&.
-
-
-Note that the parameter \fI debug timestamp\fR must be on for this to have an effect\&.
+\fBdebug uid (G)\fR
+Samba is sometimes run as root and sometime
+run as the connected user, this boolean parameter inserts the
+current euid, egid, uid and gid to the timestamp message headers
+in the log file if turned on.
+Note that the parameter \fI debug timestamp\fR must be on for this to have an
+effect.
Default: \fBdebug uid = no\fR
-
-
.TP
-default case (S)
-See the section on NAME MANGLING\&. Also note the \fIshort preserve case\fR parameter\&.
-
+\fBdebuglevel (G)\fR
+Synonym for \fI log level\fR.
+.TP
+\fBdefault (G)\fR
+A synonym for \fI default service\fR.
+.TP
+\fBdefault case (S)\fR
+See the section on NAME MANGLING. Also note the \fIshort preserve case\fR parameter.
Default: \fBdefault case = lower\fR
-
-
.TP
-default devmode (S)
-This parameter is only applicable to printable services\&. When smbd is serving Printer Drivers to Windows NT/2k/XP clients, each printer on the Samba server has a Device Mode which defines things such as paper size and orientation and duplex settings\&. The device mode can only correctly be generated by the printer driver itself (which can only be executed on a Win32 platform)\&. Because smbd is unable to execute the driver code to generate the device mode, the default behavior is to set this field to NULL\&.
-
-
-Most problems with serving printer drivers to Windows NT/2k/XP clients can be traced to a problem with the generated device mode\&. Certain drivers will do things such as crashing the client's Explorer\&.exe with a NULL devmode\&. However, other printer drivers can cause the client's spooler service (spoolsv\&.exe) to die if the devmode was not created by the driver itself (i\&.e\&. smbd generates a default devmode)\&.
-
-
-This parameter should be used with care and tested with the printer driver in question\&. It is better to leave the device mode to NULL and let the Windows client set the correct values\&. Because drivers do not do this all the time, setting \fBdefault devmode = yes\fR will instruct smbd to generate a default one\&.
-
-
-For more information on Windows NT/2k printing and Device Modes, see the MSDN documentation\&.
-
+\fBdefault devmode (S)\fR
+This parameter is only applicable to printable services. When smbd is serving
+Printer Drivers to Windows NT/2k/XP clients, each printer on the Samba
+server has a Device Mode which defines things such as paper size and
+orientation and duplex settings. The device mode can only correctly be
+generated by the printer driver itself (which can only be executed on a
+Win32 platform). Because smbd is unable to execute the driver code
+to generate the device mode, the default behavior is to set this field
+to NULL.
+
+Most problems with serving printer drivers to Windows NT/2k/XP clients
+can be traced to a problem with the generated device mode. Certain drivers
+will do things such as crashing the client's Explorer.exe with a NULL devmode.
+However, other printer drivers can cause the client's spooler service
+(spoolsv.exe) to die if the devmode was not created by the driver itself
+(i.e. smbd generates a default devmode).
+
+This parameter should be used with care and tested with the printer
+driver in question. It is better to leave the device mode to NULL
+and let the Windows client set the correct values. Because drivers do not
+do this all the time, setting \fBdefault devmode = yes\fR
+will instruct smbd to generate a default one.
+
+For more information on Windows NT/2k printing and Device Modes,
+see the MSDN documentation <URL:http://msdn.microsoft.com/>.
Default: \fBdefault devmode = no\fR
-
-
.TP
-default service (G)
-This parameter specifies the name of a service which will be connected to if the service actually requested cannot be found\&. Note that the square brackets are \fBNOT\fR given in the parameter value (see example below)\&.
-
-
-There is no default value for this parameter\&. If this parameter is not given, attempting to connect to a nonexistent service results in an error\&.
-
-
-Typically the default service would be a \fIguest ok\fR, \fIread-only\fR service\&.
-
+\fBdefault service (G)\fR
+This parameter specifies the name of a service
+which will be connected to if the service actually requested cannot
+be found. Note that the square brackets are \fBNOT\fR
+given in the parameter value (see example below).
-Also note that the apparent service name will be changed to equal that of the requested service, this is very useful as it allows you to use macros like \fI%S\fR to make a wildcard service\&.
+There is no default value for this parameter. If this
+parameter is not given, attempting to connect to a nonexistent
+service results in an error.
+Typically the default service would be a \fIguest ok\fR, \fIread-only\fR service.
-Note also that any "_" characters in the name of the service used in the default service will get mapped to a "/"\&. This allows for interesting things\&.
+Also note that the apparent service name will be changed
+to equal that of the requested service, this is very useful as it
+allows you to use macros like \fI%S\fR to make
+a wildcard service.
+Note also that any "_" characters in the name of the service
+used in the default service will get mapped to a "/". This allows for
+interesting things.
Example:
.nf
-
[global]
default service = pub
[pub]
path = /%S
+
.fi
-
-
-.TP
-default (G)
-A synonym for \fI default service\fR\&.
-
-
.TP
-delete group script (G)
-This is the full pathname to a script that will be run \fBAS ROOT\fR \fBsmbd\fR(8) when a group is requested to be deleted\&. It will expand any \fI%g\fR to the group name passed\&. This script is only useful for installations using the Windows NT domain administration tools\&.
-
-
+\fBdelete group script (G)\fR
+This is the full pathname to a script that will
+be run \fBAS ROOT\fR by smbd(8) when a group is requested to be deleted. It will expand any \fI%g\fR to the group name passed. This script is only useful for installations using the Windows NT domain administration tools.
.TP
-deleteprinter command (G)
-With the introduction of MS-RPC based printer support for Windows NT/2000 clients in Samba 2\&.2, it is now possible to delete printer at run time by issuing the DeletePrinter() RPC call\&.
-
-
-For a Samba host this means that the printer must be physically deleted from underlying printing system\&. The \fI deleteprinter command\fR defines a script to be run which will perform the necessary operations for removing the printer from the print system and from \fIsmb\&.conf\fR\&.
-
+\fBdeleteprinter command (G)\fR
+With the introduction of MS-RPC based printer
+support for Windows NT/2000 clients in Samba 2.2, it is now
+possible to delete printer at run time by issuing the
+DeletePrinter() RPC call.
-The \fIdeleteprinter command\fR is automatically called with only one parameter: \fI "printer name"\fR\&.
+For a Samba host this means that the printer must be
+physically deleted from underlying printing system. The \fI deleteprinter command\fR defines a script to be run which
+will perform the necessary operations for removing the printer
+from the print system and from \fIsmb.conf\fR.
+The \fIdeleteprinter command\fR is
+automatically called with only one parameter: \fI "printer name"\fR.
-Once the \fIdeleteprinter command\fR has been executed, \fBsmbd\fR will reparse the \fI smb\&.conf\fR to associated printer no longer exists\&. If the sharename is still valid, then \fBsmbd \fR will return an ACCESS_DENIED error to the client\&.
-
-
-See also \fI addprinter command\fR, \fIprinting\fR, \fIshow add printer wizard\fR
+Once the \fIdeleteprinter command\fR has
+been executed, \fBsmbd\fR will reparse the \fI smb.conf\fR to associated printer no longer exists.
+If the sharename is still valid, then \fBsmbd
+\fR will return an ACCESS_DENIED error to the client.
+See also \fI addprinter command\fR, \fIprinting\fR,
+\fIshow add
+printer wizard\fR
Default: \fBnone\fR
-
-Example: \fBdeleteprinter command = /usr/bin/removeprinter\fR
-
-
+Example: \fBdeleteprinter command = /usr/bin/removeprinter
+\fR
.TP
-delete readonly (S)
-This parameter allows readonly files to be deleted\&. This is not normal DOS semantics, but is allowed by UNIX\&.
-
-
-This option may be useful for running applications such as rcs, where UNIX file ownership prevents changing file permissions, and DOS semantics prevent deletion of a read only file\&.
+\fBdelete readonly (S)\fR
+This parameter allows readonly files to be deleted.
+This is not normal DOS semantics, but is allowed by UNIX.
+This option may be useful for running applications such
+as rcs, where UNIX file ownership prevents changing file
+permissions, and DOS semantics prevent deletion of a read only file.
Default: \fBdelete readonly = no\fR
-
-
.TP
-delete share command (G)
-Samba 2\&.2\&.0 introduced the ability to dynamically add and delete shares via the Windows NT 4\&.0 Server Manager\&. The \fIdelete share command\fR is used to define an external program or script which will remove an existing service definition from \fIsmb\&.conf\fR\&. In order to successfully execute the \fIdelete share command\fR, \fBsmbd\fR requires that the administrator be connected using a root account (i\&.e\&. uid == 0)\&.
-
-
-When executed, \fBsmbd\fR will automatically invoke the \fIdelete share command\fR with two parameters\&.
-
-
-\fIconfigFile\fR - the location of the global \fIsmb\&.conf\fR file\&.
-
-\fIshareName\fR - the name of the existing service\&.
-
-This parameter is only used to remove file shares\&. To delete printer shares, see the \fIdeleteprinter command\fR\&.
-
+\fBdelete share command (G)\fR
+Samba 2.2.0 introduced the ability to dynamically
+add and delete shares via the Windows NT 4.0 Server Manager. The
+\fIdelete share command\fR is used to define an
+external program or script which will remove an existing service
+definition from \fIsmb.conf\fR. In order to successfully
+execute the \fIdelete share command\fR, \fBsmbd\fR
+requires that the administrator be connected using a root account (i.e.
+uid == 0).
+
+When executed, \fBsmbd\fR will automatically invoke the
+\fIdelete share command\fR with two parameters.
+.RS
+.TP 0.2i
+\(bu
+\fIconfigFile\fR - the location
+of the global \fIsmb.conf\fR file.
+.TP 0.2i
+\(bu
+\fIshareName\fR - the name of
+the existing service.
+.RE
-See also \fIadd share command\fR, \fIchange share command\fR\&.
+This parameter is only used to remove file shares. To delete printer shares,
+see the \fIdeleteprinter
+command\fR.
+See also \fIadd share
+command\fR, \fIchange
+share command\fR.
Default: \fBnone\fR
-
Example: \fBdelete share command = /usr/local/bin/delshare\fR
-
-
.TP
-delete user from group script (G)
-Full path to the script that will be called when a user is removed from a group using the Windows NT domain administration tools\&. It will be run by \fBsmbd\fR(8) \fBAS ROOT\fR\&. Any \fI%g\fR will be replaced with the group name and any \fI%u\fR will be replaced with the user name\&.
-
-
-Default: \fBdelete user from group script = \fR
+\fBdelete user script (G)\fR
+This is the full pathname to a script that will
+be run by \fBsmbd(8)\fR
+when managing user's with remote RPC (NT) tools.
+This script is called when a remote client removes a user
+from the server, normally using 'User Manager for Domains' or
+\fBrpcclient\fR.
-Example: \fBdelete user from group script = /usr/sbin/deluser %u %g\fR
+This script should delete the given UNIX username.
+Default: \fBdelete user script = <empty string>
+\fR
+Example: \fBdelete user script = /usr/local/samba/bin/del_user
+%u\fR
.TP
-delete user script (G)
-This is the full pathname to a script that will be run by \fBsmbd\fR(8) when managing users with remote RPC (NT) tools\&.
-
-
-This script is called when a remote client removes a user from the server, normally using 'User Manager for Domains' or \fBrpcclient\fR\&.
-
-
-This script should delete the given UNIX username\&.
-
-
-Default: \fBdelete user script = <empty string>\fR
-
-
-Example: \fBdelete user script = /usr/local/samba/bin/del_user %u\fR
+\fBdelete user from group script (G)\fR
+Full path to the script that will be called when
+a user is removed from a group using the Windows NT domain administration
+tools. It will be run by smbd(8)
+\fBAS ROOT\fR. Any \fI%g\fR will be
+replaced with the group name and any \fI%u\fR will
+be replaced with the user name.
+Default: \fBdelete user from group script = \fR
+Example: \fBdelete user from group script = /usr/sbin/deluser %u %g\fR
.TP
-delete veto files (S)
-This option is used when Samba is attempting to delete a directory that contains one or more vetoed directories (see the \fIveto files\fR option)\&. If this option is set to \fBno\fR (the default) then if a vetoed directory contains any non-vetoed files or directories then the directory delete will fail\&. This is usually what you want\&.
+\fBdelete veto files (S)\fR
+This option is used when Samba is attempting to
+delete a directory that contains one or more vetoed directories
+(see the \fIveto files\fR
+option). If this option is set to no (the default) then if a vetoed
+directory contains any non-vetoed files or directories then the
+directory delete will fail. This is usually what you want.
+If this option is set to yes, then Samba
+will attempt to recursively delete any files and directories within
+the vetoed directory. This can be useful for integration with file
+serving systems such as NetAtalk which create meta-files within
+directories you might normally veto DOS/Windows users from seeing
+(e.g. \fI.AppleDouble\fR)
-If this option is set to \fByes\fR, then Samba will attempt to recursively delete any files and directories within the vetoed directory\&. This can be useful for integration with file serving systems such as NetAtalk which create meta-files within directories you might normally veto DOS/Windows users from seeing (e\&.g\&. \fI\&.AppleDouble\fR)
-
-
-Setting \fBdelete veto files = yes\fR allows these directories to be transparently deleted when the parent directory is deleted (so long as the user has permissions to do so)\&.
-
-
-See also the \fIveto files\fR parameter\&.
+Setting \fBdelete veto files = yes\fR allows these
+directories to be transparently deleted when the parent directory
+is deleted (so long as the user has permissions to do so).
+See also the \fIveto
+files\fR parameter.
Default: \fBdelete veto files = no\fR
-
-
.TP
-deny hosts (S)
-Synonym for \fIhosts deny\fR\&.
-
-
-.TP
-dfree command (G)
-The \fIdfree command\fR setting should only be used on systems where a problem occurs with the internal disk space calculations\&. This has been known to happen with Ultrix, but may occur with other operating systems\&. The symptom that was seen was an error of "Abort Retry Ignore" at the end of each directory listing\&.
-
-
-This setting allows the replacement of the internal routines to calculate the total disk space and amount available with an external routine\&. The example below gives a possible script that might fulfill 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, 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\&.
-
-
-Note: Your script should \fBNOT\fR be setuid or setgid and should be owned by (and writeable only by) root!
-
-
-Default: \fBBy default internal routines for determining the disk capacity and remaining space will be used\&. \fR
-
-
-Example: \fBdfree command = /usr/local/samba/bin/dfree\fR
-
+\fBdeny hosts (S)\fR
+Synonym for \fIhosts
+deny\fR.
+.TP
+\fBdfree command (G)\fR
+The \fIdfree command\fR setting should
+only be used on systems where a problem occurs with the internal
+disk space calculations. This has been known to happen with Ultrix,
+but may occur with other operating systems. The symptom that was
+seen was an error of "Abort Retry Ignore" at the end of each
+directory listing.
+
+This setting allows the replacement of the internal routines to
+calculate the total disk space and amount available with an external
+routine. The example below gives a possible script that might fulfill
+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,
+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.
+
+Note: Your script should \fBNOT\fR be setuid or
+setgid and should be owned by (and writeable only by) root!
+
+Default: \fBBy default internal routines for
+determining the disk capacity and remaining space will be used.
+\fR
+
+Example: \fBdfree command = /usr/local/samba/bin/dfree
+\fR
Where the script dfree (which must be made executable) could be:
.nf
-#!/bin/sh
-df $1 | tail -1 | awk '{print $2" "$4}'
+ #!/bin/sh
+ df $1 | tail -1 | awk '{print $2" "$4}'
+
.fi
-
or perhaps (on Sys V based systems):
.nf
-#!/bin/sh
-/usr/bin/df -k $1 | tail -1 | awk '{print $3" "$5}'
+ #!/bin/sh
+ /usr/bin/df -k $1 | tail -1 | awk '{print $3" "$5}'
+
.fi
-
-Note that you may have to replace the command names with full path names on some systems\&.
-
-
+Note that you may have to replace the command names
+with full path names on some systems.
.TP
-directory mask (S)
-This parameter is the octal modes which are used when converting DOS modes to UNIX modes when creating UNIX directories\&.
-
-
-When a directory is created, the necessary permissions are calculated according to the mapping from DOS modes to UNIX permissions, and the resulting UNIX mode is then bit-wise 'AND'ed with this parameter\&. This parameter may be thought of as a bit-wise MASK for the UNIX modes of a directory\&. Any bit \fBnot\fR set here will be removed from the modes set on a directory when it is created\&.
-
-
-The default value of this parameter removes the 'group' and 'other' write bits from the UNIX mode, allowing only the user who owns the directory to modify it\&.
-
-
-Following this Samba will bit-wise 'OR' the UNIX mode created from this parameter with the value of the \fIforce directory mode\fR parameter\&. This parameter is set to 000 by default (i\&.e\&. no extra mode bits are added)\&.
-
-
-Note that this parameter does not apply to permissions set by Windows NT/2000 ACL editors\&. If the administrator wishes to enforce a mask on access control lists also, they need to set the \fIdirectory security mask\fR\&.
+\fBdirectory (S)\fR
+Synonym for \fIpath
+\fR.
+.TP
+\fBdirectory mask (S)\fR
+This parameter is the octal modes which are
+used when converting DOS modes to UNIX modes when creating UNIX
+directories.
+When a directory is created, the necessary permissions are
+calculated according to the mapping from DOS modes to UNIX permissions,
+and the resulting UNIX mode is then bit-wise 'AND'ed with this
+parameter. This parameter may be thought of as a bit-wise MASK for
+the UNIX modes of a directory. Any bit \fBnot\fR set
+here will be removed from the modes set on a directory when it is
+created.
-See the \fIforce directory mode\fR parameter to cause particular mode bits to always be set on created directories\&.
+The default value of this parameter removes the 'group'
+and 'other' write bits from the UNIX mode, allowing only the
+user who owns the directory to modify it.
+Following this Samba will bit-wise 'OR' the UNIX mode
+created from this parameter with the value of the \fIforce directory mode
+\fR parameter. This parameter is set to 000 by
+default (i.e. no extra mode bits are added).
-See also the \fIcreate mode \fR parameter for masking mode bits on created files, and the \fIdirectory security mask\fR parameter\&.
+Note that this parameter does not apply to permissions
+set by Windows NT/2000 ACL editors. If the administrator wishes to enforce
+a mask on access control lists also, they need to set the \fIdirectory security mask\fR.
+See the \fIforce
+directory mode\fR parameter to cause particular mode
+bits to always be set on created directories.
-Also refer to the \fI inherit permissions\fR parameter\&.
+See also the \fIcreate mode
+\fR parameter for masking mode bits on created files,
+and the \fIdirectory
+security mask\fR parameter.
+Also refer to the \fI inherit permissions\fR parameter.
Default: \fBdirectory mask = 0755\fR
-
Example: \fBdirectory mask = 0775\fR
-
-
.TP
-directory mode (S)
-Synonym for \fI directory mask\fR
-
-
+\fBdirectory mode (S)\fR
+Synonym for \fI directory mask\fR
.TP
-directory security mask (S)
-This parameter controls what UNIX permission bits can be modified when a Windows NT client is manipulating the UNIX permission on a directory using the native NT security dialog box\&.
-
-
-This parameter is applied as a mask (AND'ed with) to the changed permission bits, thus preventing any bits not in this mask from being modified\&. Essentially, zero bits in this mask may be treated as a set of bits the user is not allowed to change\&.
+\fBdirectory security mask (S)\fR
+This parameter controls what UNIX permission bits
+can be modified when a Windows NT client is manipulating the UNIX
+permission on a directory using the native NT security dialog
+box.
+This parameter is applied as a mask (AND'ed with) to
+the changed permission bits, thus preventing any bits not in
+this mask from being modified. Essentially, zero bits in this
+mask may be treated as a set of bits the user is not allowed
+to change.
-If not set explicitly this parameter is set to 0777 meaning a user is allowed to modify all the user/group/world permissions on a directory\&.
+If not set explicitly this parameter is set to 0777
+meaning a user is allowed to modify all the user/group/world
+permissions on a directory.
+\fBNote\fR that users who can access the
+Samba server through other means can easily bypass this restriction,
+so it is primarily useful for standalone "appliance" systems.
+Administrators of most normal systems will probably want to leave
+it as the default of 0777.
-\fBNote\fR that users who can access the Samba server through other means can easily bypass this restriction, so it is primarily useful for standalone "appliance" systems\&. Administrators of most normal systems will probably want to leave it as the default of \fB0777\fR\&.
-
-
-See also the \fI force directory security mode\fR, \fIsecurity mask\fR, \fIforce security mode \fR parameters\&.
-
+See also the \fI force directory security mode\fR, \fIsecurity mask\fR,
+\fIforce security mode
+\fR parameters.
Default: \fBdirectory security mask = 0777\fR
-
Example: \fBdirectory security mask = 0700\fR
-
-
.TP
-directory (S)
-Synonym for \fIpath\fR\&.
+\fBdisable netbios (G)\fR
+Enabling this parameter will disable netbios support
+in Samba. Netbios is the only available form of browsing in
+all windows versions except for 2000 and XP.
-
-.TP
-disable netbios (G)
-Enabling this parameter will disable netbios support in Samba\&. Netbios is the only available form of browsing in all windows versions except for 2000 and XP\&.
-
-
-Note that clients that only support netbios won't be able to see your samba server when netbios support is disabled\&.
+Note that clients that only support netbios won't be able to
+see your samba server when netbios support is disabled.
Default: \fBdisable netbios = no\fR
-
Example: \fBdisable netbios = yes\fR
-
-
.TP
-disable spoolss (G)
-Enabling this parameter will disable Samba's support for the SPOOLSS set of MS-RPC's and will yield identical behavior as Samba 2\&.0\&.x\&. Windows NT/2000 clients will downgrade to using Lanman style printing commands\&. Windows 9x/ME will be uneffected by the parameter\&. However, this will also disable the ability to upload printer drivers to a Samba server via the Windows NT Add Printer Wizard or by using the NT printer properties dialog window\&. It will also disable the capability of Windows NT/2000 clients to download print drivers from the Samba host upon demand\&. \fBBe very careful about enabling this parameter\&.\fR
-
+\fBdisable spoolss (G)\fR
+Enabling this parameter will disable Samba's support
+for the SPOOLSS set of MS-RPC's and will yield identical behavior
+as Samba 2.0.x. Windows NT/2000 clients will downgrade to using
+Lanman style printing commands. Windows 9x/ME will be uneffected by
+the parameter. However, this will also disable the ability to upload
+printer drivers to a Samba server via the Windows NT Add Printer
+Wizard or by using the NT printer properties dialog window. It will
+also disable the capability of Windows NT/2000 clients to download
+print drivers from the Samba host upon demand.
+\fBBe very careful about enabling this parameter.\fR
See also use client driver
-
Default : \fBdisable spoolss = no\fR
-
-
.TP
-display charset (G)
-Specifies the charset that samba will use to print messages to stdout and stderr and SWAT will use\&. Should generally be the same as the \fBunix charset\fR\&.
-
+\fBdisplay charset (G)\fR
+Specifies the charset that samba will use
+to print messages to stdout and stderr and SWAT will use.
+Should generally be the same as the \fBunix charset\fR.
Default: \fBdisplay charset = ASCII\fR
-
Example: \fBdisplay charset = UTF8\fR
-
-
.TP
-dns proxy (G)
-Specifies that \fBnmbd\fR(8) when acting as a WINS server and finding that a NetBIOS name has not been registered, should treat the NetBIOS name word-for-word as a DNS name and do a lookup with the DNS server for that name on behalf of the name-querying client\&.
-
-
-Note that the maximum length for a NetBIOS name is 15 characters, so the DNS name (or DNS alias) can likewise only be 15 characters, maximum\&.
-
+\fBdns proxy (G)\fR
+Specifies that nmbd(8)
+when acting as a WINS server and finding that a NetBIOS name has not
+been registered, should treat the NetBIOS name word-for-word as a DNS
+name and do a lookup with the DNS server for that name on behalf of
+the name-querying client.
-\fBnmbd\fR spawns a second copy of itself to do the DNS name lookup requests, as doing a name lookup is a blocking action\&.
+Note that the maximum length for a NetBIOS name is 15
+characters, so the DNS name (or DNS alias) can likewise only be
+15 characters, maximum.
+\fBnmbd\fR spawns a second copy of itself to do the
+DNS name lookup requests, as doing a name lookup is a blocking
+action.
-See also the parameter \fI wins support\fR\&.
-
+See also the parameter \fI wins support\fR.
Default: \fBdns proxy = yes\fR
-
-
.TP
-domain logons (G)
-If set to \fByes\fR, the Samba server will serve Windows 95/98 Domain logons for the \fIworkgroup\fR it is in\&. Samba 2\&.2 has limited capability to act as a domain controller for Windows NT 4 Domains\&. For more details on setting up this feature see the Samba-PDC-HOWTO included in the Samba documentation\&.
-
+\fBdomain logons (G)\fR
+If set to yes, the Samba server will serve
+Windows 95/98 Domain logons for the \fIworkgroup\fR it is in. Samba 2.2
+has limited capability to act as a domain controller for Windows
+NT 4 Domains. For more details on setting up this feature see
+the Samba-PDC-HOWTO included in the \fIhtmldocs/\fR
+directory shipped with the source code.
Default: \fBdomain logons = no\fR
-
-
.TP
-domain master (G)
-Tell \fBsmbd\fR(8) to enable WAN-wide browse list collation\&. Setting this option causes \fBnmbd\fR to claim a special domain specific NetBIOS name that identifies it as a domain master browser for its given \fIworkgroup\fR\&. Local master browsers in the same \fIworkgroup\fR on broadcast-isolated subnets will give this \fBnmbd\fR their local browse lists, and then ask \fBsmbd\fR(8) for a complete copy of the browse list for the whole wide area network\&. Browser clients will then contact their local master browser, and will receive the domain-wide browse list, instead of just the list for their broadcast-isolated subnet\&.
-
-
-Note that Windows NT Primary Domain Controllers expect to be able to claim this \fIworkgroup\fR specific special NetBIOS name that identifies them as domain master browsers for that \fIworkgroup\fR by default (i\&.e\&. there is no way to prevent a Windows NT PDC from attempting to do this)\&. This means that if this parameter is set and \fBnmbd\fR claims the special name for a \fIworkgroup\fR before a Windows NT PDC is able to do so then cross subnet browsing will behave strangely and may fail\&.
-
-
-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 be enabled by default\&.
-
+\fBdomain master (G)\fR
+Tell \fB nmbd(8)\fR to enable WAN-wide browse list
+collation. Setting this option causes \fBnmbd\fR to
+claim a special domain specific NetBIOS name that identifies
+it as a domain master browser for its given \fIworkgroup\fR. Local master browsers
+in the same \fIworkgroup\fR on broadcast-isolated
+subnets will give this \fBnmbd\fR their local browse lists,
+and then ask \fBsmbd(8)\fR
+for a complete copy of the browse list for the whole wide area
+network. Browser clients will then contact their local master browser,
+and will receive the domain-wide browse list, instead of just the list
+for their broadcast-isolated subnet.
+
+Note that Windows NT Primary Domain Controllers expect to be
+able to claim this \fIworkgroup\fR specific special
+NetBIOS name that identifies them as domain master browsers for
+that \fIworkgroup\fR by default (i.e. there is no
+way to prevent a Windows NT PDC from attempting to do this). This
+means that if this parameter is set and \fBnmbd\fR claims
+the special name for a \fIworkgroup\fR before a Windows
+NT PDC is able to do so then cross subnet browsing will behave
+strangely and may fail.
+
+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 be enabled by default.
Default: \fBdomain master = auto\fR
-
-
.TP
-dont descend (S)
-There are certain directories on some systems (e\&.g\&., the \fI/proc\fR tree under Linux) that are either not of interest to clients or are infinitely deep (recursive)\&. This parameter allows you to specify a comma-delimited list of directories that the server should always show as empty\&.
+\fBdont descend (S)\fR
+There are certain directories on some systems
+(e.g., the \fI/proc\fR tree under Linux) that are either not
+of interest to clients or are infinitely deep (recursive). This
+parameter allows you to specify a comma-delimited list of directories
+that the server should always show as empty.
+Note that Samba can be very fussy about the exact format
+of the "dont descend" entries. For example you may need \fI ./proc\fR instead of just \fI/proc\fR.
+Experimentation is the best policy :-)
-Note that Samba can be very fussy about the exact format of the "dont descend" entries\&. For example you may need \fI \&./proc\fR instead of just \fI/proc\fR\&. Experimentation is the best policy :-)
-
-
-Default: \fBnone (i\&.e\&., all directories are OK to descend)\fR
-
+Default: \fBnone (i.e., all directories are OK
+to descend)\fR
Example: \fBdont descend = /proc,/dev\fR
-
-
-.TP
-dos charset (G)
-DOS SMB clients assume the server has the same charset as they do\&. This option specifies which charset Samba should talk to DOS clients\&.
-
-
-The default depends on which charsets you have installed\&. Samba tries to use charset 850 but falls back to ASCII in case it is not available\&. Run \fBtestparm\fR(1) to check the default on your system\&.
-
-
.TP
-dos filemode (S)
-The default behavior in Samba is to provide UNIX-like behavior where only the owner of a file/directory is able to change the permissions on it\&. However, this behavior is often confusing to DOS/Windows users\&. Enabling this parameter allows a user who has write access to the file (by whatever means) to modify the permissions on it\&. Note that a user belonging to the group owning the file will not be allowed to change permissions if the group is only granted read access\&. Ownership of the file/directory is not changed, only the permissions are modified\&.
-
+\fBdos charset (G)\fR
+DOS SMB clients assume the server has
+the same charset as they do. This option specifies which
+charset Samba should talk to DOS clients.
+
+The default depends on which charsets you have instaled.
+Samba tries to use charset 850 but falls back to ASCII in
+case it is not available. Run testparm(1)
+ to check the default on your system.
+.TP
+\fBdos filemode (S)\fR
+The default behavior in Samba is to provide
+UNIX-like behavior where only the owner of a file/directory is
+able to change the permissions on it. However, this behavior
+is often confusing to DOS/Windows users. Enabling this parameter
+allows a user who has write access to the file (by whatever
+means) to modify the permissions on it. Note that a user
+belonging to the group owning the file will not be allowed to
+change permissions if the group is only granted read access.
+Ownership of the file/directory is not changed, only the permissions
+are modified.
Default: \fBdos filemode = no\fR
-
-
.TP
-dos filetime resolution (S)
-Under the DOS and Windows FAT filesystem, the finest granularity on time resolution is two seconds\&. Setting this parameter for a share causes Samba to round the reported time down to the nearest two second boundary when a query call that requires one second resolution is made to \fBsmbd\fR(8)\&.
-
-
-This option is mainly used as a compatibility option for Visual C++ when used against Samba shares\&. If oplocks are enabled on a share, Visual C++ uses two different time reading calls to check if a file has changed since it was last read\&. One of these calls uses a one-second granularity, the other uses a two second granularity\&. As the two second call rounds any odd second down, then if the file has a timestamp of an odd number of seconds then the two timestamps will not match and Visual C++ will keep reporting the file has changed\&. Setting this option causes the two timestamps to match, and Visual C++ is happy\&.
-
+\fBdos filetime resolution (S)\fR
+Under the DOS and Windows FAT filesystem, the finest
+granularity on time resolution is two seconds. Setting this parameter
+for a share causes Samba to round the reported time down to the
+nearest two second boundary when a query call that requires one second
+resolution is made to \fBsmbd(8)\fR
+
+
+This option is mainly used as a compatibility option for Visual
+C++ when used against Samba shares. If oplocks are enabled on a
+share, Visual C++ uses two different time reading calls to check if a
+file has changed since it was last read. One of these calls uses a
+one-second granularity, the other uses a two second granularity. As
+the two second call rounds any odd second down, then if the file has a
+timestamp of an odd number of seconds then the two timestamps will not
+match and Visual C++ will keep reporting the file has changed. Setting
+this option causes the two timestamps to match, and Visual C++ is
+happy.
Default: \fBdos filetime resolution = no\fR
-
-
.TP
-dos filetimes (S)
-Under DOS and Windows, if a user can write to a file they can change the timestamp on it\&. Under POSIX semantics, only the owner of the file or root may change the timestamp\&. By default, Samba runs with POSIX semantics and refuses to change the timestamp on a file if the user \fBsmbd\fR is acting on behalf of is not the file owner\&. Setting this option to \fB yes\fR allows DOS semantics and \fBsmbd\fR(8) will change the file timestamp as DOS requires\&.
-
+\fBdos filetimes (S)\fR
+Under DOS and Windows, if a user can write to a
+file they can change the timestamp on it. Under POSIX semantics,
+only the owner of the file or root may change the timestamp. By
+default, Samba runs with POSIX semantics and refuses to change the
+timestamp on a file if the user \fBsmbd\fR is acting
+on behalf of is not the file owner. Setting this option to yes allows DOS semantics and smbd will change the file
+timestamp as DOS requires.
Default: \fBdos filetimes = no\fR
-
-
.TP
-encrypt passwords (G)
-This boolean controls whether encrypted passwords will be negotiated with the client\&. Note that Windows NT 4\&.0 SP3 and above and also Windows 98 will by default expect encrypted passwords unless a registry entry is changed\&. To use encrypted passwords in Samba see the chapter "User Database" in the Samba HOWTO Collection\&.
-
-
-In order for encrypted passwords to work correctly \fBsmbd\fR(8) must either have access to a local \fBsmbpasswd\fR(5) file (see the \fBsmbpasswd\fR(8) program for information on how to set up and maintain this file), or set the security = [server|domain|ads] parameter which causes \fBsmbd\fR to authenticate against another server\&.
-
+\fBencrypt passwords (G)\fR
+This boolean controls whether encrypted passwords
+will be negotiated with the client. Note that Windows NT 4.0 SP3 and
+above and also Windows 98 will by default expect encrypted passwords
+unless a registry entry is changed. To use encrypted passwords in
+Samba see the file ENCRYPTION.txt in the Samba documentation
+directory \fIdocs/\fR shipped with the source code.
+
+In order for encrypted passwords to work correctly
+\fBsmbd(8)\fR must either
+have access to a local \fIsmbpasswd(5)
+\fR program for information on how to set up
+and maintain this file), or set the security = [server|domain|ads] parameter which
+causes \fBsmbd\fR to authenticate against another
+server.
Default: \fBencrypt passwords = yes\fR
-
-
.TP
-enhanced browsing (G)
-This option enables a couple of enhancements to cross-subnet browse propagation that have been added in Samba but which are not standard in Microsoft implementations\&.
-
-
-The first enhancement to browse propagation consists of a regular wildcard query to a Samba WINS server for all Domain Master Browsers, followed by a browse synchronization with each of the returned DMBs\&. The second enhancement consists of a regular randomised browse synchronization with all currently known DMBs\&.
-
-
-You may wish to disable this option if you have a problem with empty workgroups not disappearing from browse lists\&. Due to the restrictions of the browse protocols these enhancements can cause a empty workgroup to stay around forever which can be annoying\&.
+\fBenhanced browsing (G)\fR
+This option enables a couple of enhancements to
+cross-subnet browse propagation that have been added in Samba
+but which are not standard in Microsoft implementations.
+The first enhancement to browse propagation consists of a regular
+wildcard query to a Samba WINS server for all Domain Master Browsers,
+followed by a browse synchronization with each of the returned
+DMBs. The second enhancement consists of a regular randomised browse
+synchronization with all currently known DMBs.
-In general you should leave this option enabled as it makes cross-subnet browse propagation much more reliable\&.
+You may wish to disable this option if you have a problem with empty
+workgroups not disappearing from browse lists. Due to the restrictions
+of the browse protocols these enhancements can cause a empty workgroup
+to stay around forever which can be annoying.
+In general you should leave this option enabled as it makes
+cross-subnet browse propagation much more reliable.
Default: \fBenhanced browsing = yes\fR
-
-
.TP
-enumports command (G)
-The concept of a "port" is fairly foreign to UNIX hosts\&. Under Windows NT/2000 print servers, a port is associated with a port monitor and generally takes the form of a local port (i\&.e\&. LPT1:, COM1:, FILE:) or a remote port (i\&.e\&. LPD Port Monitor, etc\&.\&.\&.)\&. By default, Samba has only one port defined--\fB"Samba Printer Port"\fR\&. Under Windows NT/2000, all printers must have a valid port name\&. If you wish to have a list of ports displayed (\fBsmbd \fR does not use a port name for anything) other than the default \fB"Samba Printer Port"\fR, you can define \fIenumports command\fR to point to a program which should generate a list of ports, one per line, to standard output\&. This listing will then be used in response to the level 1 and 2 EnumPorts() RPC\&.
-
+\fBenumports command (G)\fR
+The concept of a "port" is fairly foreign
+to UNIX hosts. Under Windows NT/2000 print servers, a port
+is associated with a port monitor and generally takes the form of
+a local port (i.e. LPT1:, COM1:, FILE:) or a remote port
+(i.e. LPD Port Monitor, etc...). By default, Samba has only one
+port defined--"Samba Printer Port". Under
+Windows NT/2000, all printers must have a valid port name.
+If you wish to have a list of ports displayed (\fBsmbd
+\fR does not use a port name for anything) other than
+the default "Samba Printer Port", you
+can define \fIenumports command\fR to point to
+a program which should generate a list of ports, one per line,
+to standard output. This listing will then be used in response
+to the level 1 and 2 EnumPorts() RPC.
Default: \fBno enumports command\fR
-
-Example: \fBenumports command = /usr/bin/listports\fR
-
-
-.TP
-exec (S)
-This is a synonym for \fIpreexec\fR\&.
-
-
-.TP
-fake directory create times (S)
-NTFS and Windows VFAT file systems keep a create time for all files and directories\&. This is not the same as the ctime - status change time - that Unix keeps, so Samba by default reports the earliest of the various times Unix does keep\&. Setting this parameter for a share causes Samba to always report midnight 1-1-1980 as the create time for directories\&.
-
-
-This option is mainly used as a compatibility option for Visual C++ when used against Samba shares\&. Visual C++ generated makefiles have the object directory as a dependency for each object file, and a make rule to create the directory\&. Also, when NMAKE compares timestamps it uses the creation time when examining a directory\&. Thus the object directory will be created if it does not exist, but once it does exist it will always have an earlier timestamp than the object files it contains\&.
-
-
-However, Unix time semantics mean that the create time reported by Samba will be updated whenever a file is created or or deleted in the directory\&. NMAKE finds all object files in the object directory\&. The timestamp of the last one built is then compared to the timestamp of the object directory\&. If the directory's timestamp if newer, then all object files will be rebuilt\&. Enabling this option ensures directories always predate their contents and an NMAKE build will proceed as expected\&.
-
+Example: \fBenumports command = /usr/bin/listports
+\fR
+.TP
+\fBexec (S)\fR
+This is a synonym for \fIpreexec\fR.
+.TP
+\fBfake directory create times (S)\fR
+NTFS and Windows VFAT file systems keep a create
+time for all files and directories. This is not the same as the
+ctime - status change time - that Unix keeps, so Samba by default
+reports the earliest of the various times Unix does keep. Setting
+this parameter for a share causes Samba to always report midnight
+1-1-1980 as the create time for directories.
+
+This option is mainly used as a compatibility option for
+Visual C++ when used against Samba shares. Visual C++ generated
+makefiles have the object directory as a dependency for each object
+file, and a make rule to create the directory. Also, when NMAKE
+compares timestamps it uses the creation time when examining a
+directory. Thus the object directory will be created if it does not
+exist, but once it does exist it will always have an earlier
+timestamp than the object files it contains.
+
+However, Unix time semantics mean that the create time
+reported by Samba will be updated whenever a file is created or
+or deleted in the directory. NMAKE finds all object files in
+the object directory. The timestamp of the last one built is then
+compared to the timestamp of the object directory. If the
+directory's timestamp if newer, then all object files
+will be rebuilt. Enabling this option
+ensures directories always predate their contents and an NMAKE build
+will proceed as expected.
Default: \fBfake directory create times = no\fR
-
-
.TP
-fake oplocks (S)
-Oplocks are the way that SMB clients get permission from a server to locally cache file operations\&. If a server grants an oplock (opportunistic lock) then the client is free to assume that it is the only one accessing the file and it will aggressively cache file data\&. With some oplock types the client may even cache file open/close operations\&. This can give enormous performance benefits\&.
-
-
-When you set \fBfake oplocks = yes\fR, \fBsmbd\fR(8) will always grant oplock requests no matter how many clients are using the file\&.
-
-
-It is generally much better to use the real \fIoplocks\fR support rather than this parameter\&.
-
-
-If you enable this option on all read-only shares or shares that you know will only be accessed from one client at a time such as physically read-only media like CDROMs, you will see a big performance improvement on many operations\&. If you enable this option on shares where multiple clients may be accessing the files read-write at the same time you can get data corruption\&. Use this option carefully!
-
+\fBfake oplocks (S)\fR
+Oplocks are the way that SMB clients get permission
+from a server to locally cache file operations. If a server grants
+an oplock (opportunistic lock) then the client is free to assume
+that it is the only one accessing the file and it will aggressively
+cache file data. With some oplock types the client may even cache
+file open/close operations. This can give enormous performance benefits.
+
+When you set \fBfake oplocks = yes\fR, \fBsmbd(8)\fR will
+always grant oplock requests no matter how many clients are using
+the file.
+
+It is generally much better to use the real \fIoplocks\fR support rather
+than this parameter.
+
+If you enable this option on all read-only shares or
+shares that you know will only be accessed from one client at a
+time such as physically read-only media like CDROMs, you will see
+a big performance improvement on many operations. If you enable
+this option on shares where multiple clients may be accessing the
+files read-write at the same time you can get data corruption. Use
+this option carefully!
Default: \fBfake oplocks = no\fR
-
-
.TP
-follow symlinks (S)
-This parameter allows the Samba administrator to stop \fBsmbd\fR(8) from following symbolic links in a particular share\&. Setting this parameter to \fBno\fR prevents any file or directory that is a symbolic link from being followed (the user will get an error)\&. This option is very useful to stop users from adding a symbolic link to \fI/etc/passwd\fR in their home directory for instance\&. However it will slow filename lookups down slightly\&.
-
-
-This option is enabled (i\&.e\&. \fBsmbd\fR will follow symbolic links) by default\&.
+\fBfollow symlinks (S)\fR
+This parameter allows the Samba administrator
+to stop \fBsmbd(8)\fR
+from following symbolic links in a particular share. Setting this
+parameter to no prevents any file or directory
+that is a symbolic link from being followed (the user will get an
+error). This option is very useful to stop users from adding a
+symbolic link to \fI/etc/passwd\fR in their home
+directory for instance. However it will slow filename lookups
+down slightly.
+This option is enabled (i.e. \fBsmbd\fR will
+follow symbolic links) by default.
Default: \fBfollow symlinks = yes\fR
-
-
.TP
-force create mode (S)
-This parameter specifies a set of UNIX mode bit permissions that will \fBalways\fR be set on a file created by Samba\&. This is done by bitwise 'OR'ing these bits onto the mode bits of a file that is being created or having its permissions changed\&. The default for this parameter is (in octal) 000\&. The modes in this parameter are bitwise 'OR'ed onto the file mode after the mask set in the \fIcreate mask\fR parameter is applied\&.
+\fBforce create mode (S)\fR
+This parameter specifies a set of UNIX mode bit
+permissions that will \fBalways\fR be set on a
+file created by Samba. This is done by bitwise 'OR'ing these bits onto
+the mode bits of a file that is being created or having its
+permissions changed. The default for this parameter is (in octal)
+000. The modes in this parameter are bitwise 'OR'ed onto the file
+mode after the mask set in the \fIcreate mask\fR
+parameter is applied.
+See also the parameter \fIcreate
+mask\fR for details on masking mode bits on files.
-See also the parameter \fIcreate mask\fR for details on masking mode bits on files\&.
-
-
-See also the \fIinherit permissions\fR parameter\&.
-
+See also the \fIinherit
+permissions\fR parameter.
Default: \fBforce create mode = 000\fR
-
Example: \fBforce create mode = 0755\fR
-
-would force all created files to have read and execute permissions set for 'group' and 'other' as well as the read/write/execute bits set for the 'user'\&.
-
-
+would force all created files to have read and execute
+permissions set for 'group' and 'other' as well as the
+read/write/execute bits set for the 'user'.
.TP
-force directory mode (S)
-This parameter specifies a set of UNIX mode bit permissions that will \fBalways\fR be set on a directory created by Samba\&. This is done by bitwise 'OR'ing these bits onto the mode bits of a directory that is being created\&. The default for this parameter is (in octal) 0000 which will not add any extra permission bits to a created directory\&. This operation is done after the mode mask in the parameter \fIdirectory mask\fR is applied\&.
-
-
-See also the parameter \fI directory mask\fR for details on masking mode bits on created directories\&.
+\fBforce directory mode (S)\fR
+This parameter specifies a set of UNIX mode bit
+permissions that will \fBalways\fR be set on a directory
+created by Samba. This is done by bitwise 'OR'ing these bits onto the
+mode bits of a directory that is being created. The default for this
+parameter is (in octal) 0000 which will not add any extra permission
+bits to a created directory. This operation is done after the mode
+mask in the parameter \fIdirectory mask\fR is
+applied.
+See also the parameter \fI directory mask\fR for details on masking mode bits
+on created directories.
-See also the \fI inherit permissions\fR parameter\&.
-
+See also the \fI inherit permissions\fR parameter.
Default: \fBforce directory mode = 000\fR
-
Example: \fBforce directory mode = 0755\fR
-
-would force all created directories to have read and execute permissions set for 'group' and 'other' as well as the read/write/execute bits set for the 'user'\&.
-
-
+would force all created directories to have read and execute
+permissions set for 'group' and 'other' as well as the
+read/write/execute bits set for the 'user'.
.TP
-force directory security mode (S)
-This parameter controls what UNIX permission bits can be modified when a Windows NT client is manipulating the UNIX permission on a directory using the native NT security dialog box\&.
-
-
-This parameter is applied as a mask (OR'ed with) to the changed permission bits, thus forcing any bits in this mask that the user may have modified to be on\&. Essentially, one bits in this mask may be treated as a set of bits that, when modifying security on a directory, the user has always set to be 'on'\&.
-
-
-If not set explicitly this parameter is 000, which allows a user to modify all the user/group/world permissions on a directory without restrictions\&.
+\fBforce directory security mode (S)\fR
+This parameter controls what UNIX permission bits
+can be modified when a Windows NT client is manipulating the UNIX
+permission on a directory using the native NT security dialog box.
+This parameter is applied as a mask (OR'ed with) to the
+changed permission bits, thus forcing any bits in this mask that
+the user may have modified to be on. Essentially, one bits in this
+mask may be treated as a set of bits that, when modifying security
+on a directory, the user has always set to be 'on'.
-\fBNote\fR that users who can access the Samba server through other means can easily bypass this restriction, so it is primarily useful for standalone "appliance" systems\&. Administrators of most normal systems will probably want to leave it set as 0000\&.
+If not set explicitly this parameter is 000, which
+allows a user to modify all the user/group/world permissions on a
+directory without restrictions.
+\fBNote\fR that users who can access the
+Samba server through other means can easily bypass this restriction,
+so it is primarily useful for standalone "appliance" systems.
+Administrators of most normal systems will probably want to leave
+it set as 0000.
-See also the \fI directory security mask\fR, \fIsecurity mask\fR, \fIforce security mode \fR parameters\&.
-
+See also the \fI directory security mask\fR, \fIsecurity mask\fR,
+\fIforce security mode
+\fR parameters.
Default: \fBforce directory security mode = 0\fR
-
Example: \fBforce directory security mode = 700\fR
-
-
.TP
-force group (S)
-This specifies a UNIX group name that will be assigned as the default primary group for all users connecting to this service\&. This is useful for sharing files by ensuring that all access to files on service will use the named group for their permissions checking\&. Thus, by assigning permissions for this group to the files and directories within this service the Samba administrator can restrict or allow sharing of these files\&.
-
-
-In Samba 2\&.0\&.5 and above this parameter has extended functionality in the following way\&. If the group name listed here has a '+' character prepended to it then the current user accessing the share only has the primary group default assigned to this group if they are already assigned as a member of that group\&. This allows an administrator to decide that only users who are already in a particular group will create files with group ownership set to that group\&. This gives a finer granularity of ownership assignment\&. For example, the setting \fIforce group = +sys\fR means that only users who are already in group sys will have their default primary group assigned to sys when accessing this Samba share\&. All other users will retain their ordinary primary group\&.
-
-
-If the \fIforce user\fR parameter is also set the group specified in \fIforce group\fR will override the primary group set in \fIforce user\fR\&.
-
-
-See also \fIforce user\fR\&.
-
+\fBforce group (S)\fR
+This specifies a UNIX group name that will be
+assigned as the default primary group for all users connecting
+to this service. This is useful for sharing files by ensuring
+that all access to files on service will use the named group for
+their permissions checking. Thus, by assigning permissions for this
+group to the files and directories within this service the Samba
+administrator can restrict or allow sharing of these files.
+
+In Samba 2.0.5 and above this parameter has extended
+functionality in the following way. If the group name listed here
+has a '+' character prepended to it then the current user accessing
+the share only has the primary group default assigned to this group
+if they are already assigned as a member of that group. This allows
+an administrator to decide that only users who are already in a
+particular group will create files with group ownership set to that
+group. This gives a finer granularity of ownership assignment. For
+example, the setting \fIforce group = +sys\fR means
+that only users who are already in group sys will have their default
+primary group assigned to sys when accessing this Samba share. All
+other users will retain their ordinary primary group.
+
+If the \fIforce user
+\fR parameter is also set the group specified in
+\fIforce group\fR will override the primary group
+set in \fIforce user\fR.
+
+See also \fIforce
+user\fR.
Default: \fBno forced group\fR
-
Example: \fBforce group = agroup\fR
-
-
.TP
-force security mode (S)
-This parameter controls what UNIX permission bits can be modified when a Windows NT client is manipulating the UNIX permission on a file using the native NT security dialog box\&.
-
-
-This parameter is applied as a mask (OR'ed with) to the changed permission bits, thus forcing any bits in this mask that the user may have modified to be on\&. Essentially, one bits in this mask may be treated as a set of bits that, when modifying security on a file, the user has always set to be 'on'\&.
-
-
-If not set explicitly this parameter is set to 0, and allows a user to modify all the user/group/world permissions on a file, with no restrictions\&.
-
+\fBforce security mode (S)\fR
+This parameter controls what UNIX permission
+bits can be modified when a Windows NT client is manipulating
+the UNIX permission on a file using the native NT security dialog
+box.
-\fBNote\fR that users who can access the Samba server through other means can easily bypass this restriction, so it is primarily useful for standalone "appliance" systems\&. Administrators of most normal systems will probably want to leave this set to 0000\&.
+This parameter is applied as a mask (OR'ed with) to the
+changed permission bits, thus forcing any bits in this mask that
+the user may have modified to be on. Essentially, one bits in this
+mask may be treated as a set of bits that, when modifying security
+on a file, the user has always set to be 'on'.
+If not set explicitly this parameter is set to 0,
+and allows a user to modify all the user/group/world permissions on a file,
+with no restrictions.
-See also the \fI force directory security mode\fR, \fIdirectory security mask\fR, \fI security mask\fR parameters\&.
+\fBNote\fR that users who can access
+the Samba server through other means can easily bypass this restriction,
+so it is primarily useful for standalone "appliance" systems.
+Administrators of most normal systems will probably want to leave
+this set to 0000.
+See also the \fI force directory security mode\fR,
+\fIdirectory security
+mask\fR, \fI security mask\fR parameters.
Default: \fBforce security mode = 0\fR
-
Example: \fBforce security mode = 700\fR
-
-
.TP
-force user (S)
-This specifies a UNIX user name that will be assigned as the default user for all users connecting to this service\&. This is useful for sharing files\&. You should also use it carefully as using it incorrectly can cause security problems\&.
-
-
-This user name only gets used once a connection is established\&. Thus clients still need to connect as a valid user and supply a valid password\&. Once connected, all file operations will be performed as the "forced user", no matter what username the client connected as\&. This can be very useful\&.
-
+\fBforce user (S)\fR
+This specifies a UNIX user name that will be
+assigned as the default user for all users connecting to this service.
+This is useful for sharing files. You should also use it carefully
+as using it incorrectly can cause security problems.
-In Samba 2\&.0\&.5 and above this parameter also causes the primary group of the forced user to be used as the primary group for all file activity\&. Prior to 2\&.0\&.5 the primary group was left as the primary group of the connecting user (this was a bug)\&.
+This user name only gets used once a connection is established.
+Thus clients still need to connect as a valid user and supply a
+valid password. Once connected, all file operations will be performed
+as the "forced user", no matter what username the client connected
+as. This can be very useful.
+In Samba 2.0.5 and above this parameter also causes the
+primary group of the forced user to be used as the primary group
+for all file activity. Prior to 2.0.5 the primary group was left
+as the primary group of the connecting user (this was a bug).
-See also \fIforce group\fR
-
+See also \fIforce group
+\fR
Default: \fBno forced user\fR
-
Example: \fBforce user = auser\fR
-
-
.TP
-fstype (S)
-This parameter allows the administrator to configure the string that specifies the type of filesystem a share is using that is reported by \fBsmbd\fR(8) when a client queries the filesystem type for a share\&. The default type is \fBNTFS\fR for compatibility with Windows NT but this can be changed to other strings such as \fBSamba\fR or \fBFAT \fR if required\&.
-
+\fBfstype (S)\fR
+This parameter allows the administrator to
+configure the string that specifies the type of filesystem a share
+is using that is reported by \fBsmbd(8)
+\fR when a client queries the filesystem type
+for a share. The default type is NTFS for
+compatibility with Windows NT but this can be changed to other
+strings such as Samba or FAT
+if required.
Default: \fBfstype = NTFS\fR
-
Example: \fBfstype = Samba\fR
-
-
.TP
-getwd cache (G)
-This is a tuning option\&. When this is enabled a caching algorithm will be used to reduce the time taken for getwd() calls\&. This can have a significant impact on performance, especially when the \fIwide links\fR parameter is set to \fBno\fR\&.
-
+\fBgetwd cache (G)\fR
+This is a tuning option. When this is enabled a
+caching algorithm will be used to reduce the time taken for getwd()
+calls. This can have a significant impact on performance, especially
+when the \fIwide links\fR
+parameter is set to no.
Default: \fBgetwd cache = yes\fR
-
-
.TP
-group (S)
-Synonym for \fIforce group\fR\&.
-
-
+\fBgroup (S)\fR
+Synonym for \fIforce
+group\fR.
.TP
-guest account (G,S)
-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 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, the specified username overrides this one\&.
-
-
-One some systems the default guest account "nobody" may not be able to print\&. Use another account in this case\&. You should test this by trying to log in as your guest user (perhaps by using the \fBsu -\fR command) and trying to print using the system print command such as \fBlpr(1)\fR or \fB lp(1)\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
+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,
+the specified username overrides this one.
+One some systems the default guest account "nobody" may not
+be able to print. Use another account in this case. You should test
+this by trying to log in as your guest user (perhaps by using the
+\fBsu -\fR command) and trying to print using the
+system print command such as \fBlpr(1)\fR or \fB lp(1)\fR.
-This parameter does not accept % macros, because many parts of the system require this value to be constant for correct operation\&.
-
-
-Default: \fBspecified at compile time, usually "nobody"\fR
+This parameter does not accept % macros, because
+many parts of the system require this value to be
+constant for correct operation.
+Default: \fBspecified at compile time, usually
+"nobody"\fR
Example: \fBguest account = ftp\fR
-
-
.TP
-guest ok (S)
-If this parameter is \fByes\fR for a service, then no password is required to connect to the service\&. Privileges will be those of the \fI guest account\fR\&.
-
-
-This paramater nullifies the benifits of setting \fIrestrict anonymous\fR = 2
-
-
-See the section below on \fI security\fR for more information about this option\&.
+\fBguest ok (S)\fR
+If this parameter is yes for
+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.
Default: \fBguest ok = no\fR
-
-
.TP
-guest only (S)
-If this parameter is \fByes\fR for a service, then only guest connections to the service are permitted\&. This parameter will have no effect if \fIguest ok\fR is not set for the service\&.
-
-
-See the section below on \fI security\fR for more information about this option\&.
+\fBguest only (S)\fR
+If this parameter is yes for
+a service, then only guest connections to the service are permitted.
+This parameter will have no effect if \fIguest ok\fR is not set for the service.
+See the section below on \fI security\fR for more information about this option.
Default: \fBguest only = no\fR
-
-
.TP
-hide dot files (S)
-This is a boolean parameter that controls whether files starting with a dot appear as hidden files\&.
-
+\fBhide dot files (S)\fR
+This is a boolean parameter that controls whether
+files starting with a dot appear as hidden files.
Default: \fBhide dot files = yes\fR
-
-
.TP
-hide files (S)
-This is a list of files or directories that are not visible but are accessible\&. The DOS 'hidden' attribute is applied to any files or directories that match\&.
-
-
-Each entry in the list must be separated by a '/', which allows spaces to be included in the entry\&. '*' and '?' can be used to specify multiple files or directories as in DOS wildcards\&.
-
-
-Each entry must be a Unix path, not a DOS path and must not include the Unix directory separator '/'\&.
+\fBhide files(S)\fR
+This is a list of files or directories that are not
+visible but are accessible. The DOS 'hidden' attribute is applied
+to any files or directories that match.
+Each entry in the list must be separated by a '/',
+which allows spaces to be included in the entry. '*'
+and '?' can be used to specify multiple files or directories
+as in DOS wildcards.
-Note that the case sensitivity option is applicable in hiding files\&.
+Each entry must be a Unix path, not a DOS path and must
+not include the Unix directory separator '/'.
+Note that the case sensitivity option is applicable
+in hiding files.
-Setting this parameter will affect the performance of Samba, as it will be forced to check all files and directories for a match as they are scanned\&.
-
-
-See also \fIhide dot files\fR, \fI veto files\fR and \fIcase sensitive\fR\&.
+Setting this parameter will affect the performance of Samba,
+as it will be forced to check all files and directories for a match
+as they are scanned.
+See also \fIhide
+dot files\fR, \fI veto files\fR and \fIcase sensitive\fR.
Default: \fBno file are hidden\fR
+Example: \fBhide files =
+/.*/DesktopFolderDB/TrashFor%m/resource.frk/\fR
-Example: \fBhide files = /.*/DesktopFolderDB/TrashFor%m/resource.frk/\fR
-
-
-The above example is based on files that the Macintosh SMB client (DAVE) available from Thursby creates for internal use, and also still hides all files beginning with a dot\&.
-
-
+The above example is based on files that the Macintosh
+SMB client (DAVE) available from
+Thursby <URL:http://www.thursby.com> creates for internal use, and also still hides
+all files beginning with a dot.
.TP
-hide local users (G)
-This parameter toggles the hiding of local UNIX users (root, wheel, floppy, etc) from remote clients\&.
-
+\fBhide local users(G)\fR
+This parameter toggles the hiding of local UNIX
+users (root, wheel, floppy, etc) from remote clients.
Default: \fBhide local users = no\fR
-
-
-.TP
-hide special files (S)
-This parameter prevents clients from seeing special files such as sockets, devices and fifo's in directory listings\&.
-
-
-Default: \fBhide special files = no\fR
-
-
.TP
-hide unreadable (S)
-This parameter prevents clients from seeing the existance of files that cannot be read\&. Defaults to off\&.
-
+\fBhide unreadable (G)\fR
+This parameter prevents clients from seeing the
+existance of files that cannot be read. Defaults to off.
Default: \fBhide unreadable = no\fR
-
-
.TP
-hide unwriteable files (S)
-This parameter prevents clients from seeing the existance of files that cannot be written to\&. Defaults to off\&. Note that unwriteable directories are shown as usual\&.
-
+\fBhide unwriteable files (G)\fR
+This parameter prevents clients from seeing
+the existance of files that cannot be written to. Defaults to off.
+Note that unwriteable directories are shown as usual.
Default: \fBhide unwriteable = no\fR
-
-
.TP
-homedir map (G)
-If\fInis homedir \fR is \fByes\fR, and \fBsmbd\fR(8) is also acting as a Win95/98 \fIlogon server\fR then this parameter specifies the NIS (or YP) map from which the server for the user's home directory should be extracted\&. At present, only the Sun auto\&.home map format is understood\&. The form of the map is:
+\fBhide special files (G)\fR
+This parameter prevents clients from seeing
+special files such as sockets, devices and fifo's in directory
+listings.
+Default: \fBhide special files = no\fR
+.TP
+\fBhomedir map (G)\fR
+If\fInis homedir
+\fR is yes, and \fBsmbd(8)\fR is also acting
+as a Win95/98 \fIlogon server\fR then this parameter
+specifies the NIS (or YP) map from which the server for the user's
+home directory should be extracted. At present, only the Sun
+auto.home map format is understood. The form of the map is:
\fBusername server:/some/file/system\fR
+and the program will extract the servername from before
+the first ':'. There should probably be a better parsing system
+that copes with different map formats and also Amd (another
+automounter) maps.
-and the program will extract the servername from before the first ':'\&. There should probably be a better parsing system that copes with different map formats and also Amd (another automounter) maps\&.
-
-
-A working NIS client is required on the system for this option to work\&.
-
-See also \fInis homedir\fR , \fIdomain logons\fR \&.
+\fBNOTE :\fRA working NIS client is required on
+the system for this option to work.
+See also \fInis homedir\fR
+, \fIdomain logons\fR
+\&.
Default: \fBhomedir map = <empty string>\fR
-
Example: \fBhomedir map = amd.homedir\fR
-
-
.TP
-host msdfs (G)
-This boolean parameter is only available if Samba has been configured and compiled with the \fB --with-msdfs\fR option\&. If set to \fByes\fR, Samba will act as a Dfs server, and allow Dfs-aware clients to browse Dfs trees hosted on the server\&.
-
-
-See also the \fI msdfs root\fR share level parameter\&. For more information on setting up a Dfs tree on Samba, refer to msdfs_setup\&.html\&.
+\fBhost msdfs (G)\fR
+This boolean parameter is only available
+if Samba has been configured and compiled with the \fB --with-msdfs\fR option. If set to yes,
+Samba will act as a Dfs server, and allow Dfs-aware clients
+to browse Dfs trees hosted on the server.
+See also the \fI msdfs root\fR share level parameter. For
+more information on setting up a Dfs tree on Samba,
+refer to msdfs_setup.html
Default: \fBhost msdfs = no\fR
-
-
.TP
-hostname lookups (G)
-Specifies whether samba should use (expensive) hostname lookups or use the ip addresses instead\&. An example place where hostname lookups are currently used is when checking the \fBhosts deny\fR and \fBhosts allow\fR\&.
-
+\fBhostname lookups (G)\fR
+Specifies whether samba should use (expensive)
+hostname lookups or use the ip addresses instead. An example place
+where hostname lookups are currently used is when checking
+the \fBhosts deny\fR and \fBhosts allow\fR.
Default: \fBhostname lookups = yes\fR
-
Example: \fBhostname lookups = no\fR
-
-
.TP
-hosts allow (S)
-A synonym for this parameter is \fIallow hosts\fR\&.
-
-
-This parameter is a comma, space, or tab delimited set of hosts which are permitted to access a service\&.
-
-
-If specified in the [global] section then it will apply to all services, regardless of whether the individual service has a different setting\&.
-
+\fBhosts allow (S)\fR
+A synonym for this parameter is \fIallow
+hosts\fR.
-You can specify the hosts by name or IP number\&. For example, you could restrict access to only the hosts on a Class C subnet with something like \fBallow hosts = 150.203.5. \fR\&. The full syntax of the list is described in the man page \fIhosts_access(5)\fR\&. Note that this man page may not be present on your system, so a brief description will be given here also\&.
+This parameter is a comma, space, or tab delimited
+set of hosts which are permitted to access a service.
+If specified in the [global] section then it will
+apply to all services, regardless of whether the individual
+service has a different setting.
-Note that the localhost address 127\&.0\&.0\&.1 will always be allowed access unless specifically denied by a \fIhosts deny\fR option\&.
+You can specify the hosts by name or IP number. For
+example, you could restrict access to only the hosts on a
+Class C subnet with something like \fBallow hosts = 150.203.5.
+\fR. The full syntax of the list is described in the man
+page \fIhosts_access(5)\fR. Note that this man
+page may not be present on your system, so a brief description will
+be given here also.
+Note that the localhost address 127.0.0.1 will always
+be allowed access unless specifically denied by a \fIhosts deny\fR option.
-You can also specify hosts by network/netmask pairs and by netgroup names if your system supports netgroups\&. The \fBEXCEPT\fR keyword can also be used to limit a wildcard list\&. The following examples may provide some help:
-
-
-Example 1: allow all IPs in 150\&.203\&.*\&.*; except one
+You can also specify hosts by network/netmask pairs and
+by netgroup names if your system supports netgroups. The
+\fBEXCEPT\fR keyword can also be used to limit a
+wildcard list. The following examples may provide some help:
+Example 1: allow all IPs in 150.203.*.*; except one
\fBhosts allow = 150.203. EXCEPT 150.203.6.66\fR
-
Example 2: allow hosts that match the given network/netmask
-
\fBhosts allow = 150.203.15.0/255.255.255.0\fR
-
Example 3: allow a couple of hosts
-
\fBhosts allow = lapland, arvidsjaur\fR
-
-Example 4: allow only hosts in NIS netgroup "foonet", but deny access from one particular host
-
+Example 4: allow only hosts in NIS netgroup "foonet", but
+deny access from one particular host
\fBhosts allow = @foonet\fR
-
\fBhosts deny = pirate\fR
+Note that access still requires suitable user-level passwords.
-Note that access still requires suitable user-level passwords\&.
-
-See \fBtestparm\fR(1) for a way of testing your host access to see if it does what you expect\&.
-
-
-Default: \fBnone (i\&.e\&., all hosts permitted access)\fR
-
-
-Example: \fBallow hosts = 150.203.5. myhost.mynet.edu.au\fR
+See \fBtestparm(1)\fR
+ for a way of testing your host access to see if it does
+what you expect.
+Default: \fBnone (i.e., all hosts permitted access)
+\fR
+Example: \fBallow hosts = 150.203.5. myhost.mynet.edu.au
+\fR
.TP
-hosts deny (S)
-The opposite of \fIhosts allow\fR - hosts listed here are \fBNOT\fR permitted access to services unless the specific services have their own lists to override this one\&. Where the lists conflict, the \fIallow\fR list takes precedence\&.
-
-
-Default: \fBnone (i\&.e\&., no hosts specifically excluded)\fR
-
-
-Example: \fBhosts deny = 150.203.4. badhost.mynet.edu.au\fR
+\fBhosts deny (S)\fR
+The opposite of \fIhosts allow\fR
+- hosts listed here are \fBNOT\fR permitted access to
+services unless the specific services have their own lists to override
+this one. Where the lists conflict, the \fIallow\fR
+list takes precedence.
+Default: \fBnone (i.e., no hosts specifically excluded)
+\fR
+Example: \fBhosts deny = 150.203.4. badhost.mynet.edu.au
+\fR
.TP
-hosts equiv (G)
-If this global parameter is a non-null string, it specifies the name of a file to read for the names of hosts and users who will be allowed access without specifying a password\&.
-
+\fBhosts equiv (G)\fR
+If this global parameter is a non-null string,
+it specifies the name of a file to read for the names of hosts
+and users who will be allowed access without specifying a password.
-This is not be confused with \fIhosts allow\fR which is about hosts access to services and is more useful for guest services\&. \fI hosts equiv\fR may be useful for NT clients which will not supply passwords to Samba\&.
+This is not be confused with \fIhosts allow\fR which is about hosts
+access to services and is more useful for guest services. \fI hosts equiv\fR may be useful for NT clients which will
+not supply passwords to Samba.
-
-The use of \fIhosts equiv \fR can be a major security hole\&. This is because you are trusting the PC to supply the correct username\&. It is very easy to get a PC to supply a false username\&. I recommend that the \fIhosts equiv\fR option be only used if you really know what you are doing, or perhaps on a home network where you trust your spouse and kids\&. And only if you \fBreally\fR trust them :-)\&.
+\fBNOTE :\fR The use of \fIhosts equiv
+\fR can be a major security hole. This is because you are
+trusting the PC to supply the correct username. It is very easy to
+get a PC to supply a false username. I recommend that the
+\fIhosts equiv\fR option be only used if you really
+know what you are doing, or perhaps on a home network where you trust
+your spouse and kids. And only if you \fBreally\fR trust
+them :-).
Default: \fBno host equivalences\fR
-
Example: \fBhosts equiv = /etc/hosts.equiv\fR
-
-
.TP
-include (G)
-This allows you to include one config file inside another\&. The file is included literally, as though typed in place\&.
-
-
-It takes the standard substitutions, except \fI%u \fR, \fI%P\fR and \fI%S\fR\&.
+\fBinclude (G)\fR
+This allows you to include one config file
+inside another. The file is included literally, as though typed
+in place.
+It takes the standard substitutions, except \fI%u
+\fR, \fI%P\fR and \fI%S\fR.
Default: \fBno file included\fR
-
-Example: \fBinclude = /usr/local/samba/lib/admin_smb.conf\fR
-
-
+Example: \fBinclude = /usr/local/samba/lib/admin_smb.conf
+\fR
.TP
-inherit acls (S)
-This parameter can be used to ensure that if default acls exist on parent directories, they are always honored when creating a subdirectory\&. The default behavior is to use the mode specified when creating the directory\&. Enabling this option sets the mode to 0777, thus guaranteeing that default directory acls are propagated\&.
-
+\fBinherit acls (S)\fR
+This parameter can be used to ensure
+that if default acls exist on parent directories,
+they are always honored when creating a subdirectory.
+The default behavior is to use the mode specified
+when creating the directory. Enabling this option
+sets the mode to 0777, thus guaranteeing that
+default directory acls are propagated.
Default: \fBinherit acls = no\fR
-
-
.TP
-inherit permissions (S)
-The permissions on new files and directories are normally governed by \fI create mask\fR, \fIdirectory mask\fR, \fIforce create mode\fR and \fIforce directory mode\fR but the boolean inherit permissions parameter overrides this\&.
-
-
-New directories inherit the mode of the parent directory, including bits such as setgid\&.
-
-
-New files inherit their read/write bits from the parent directory\&. Their execute bits continue to be determined by \fImap archive\fR , \fImap hidden\fR and \fImap system\fR as usual\&.
-
-
-Note that the setuid bit is \fBnever\fR set via inheritance (the code explicitly prohibits this)\&.
+\fBinherit permissions (S)\fR
+The permissions on new files and directories
+are normally governed by \fI create mask\fR, \fIdirectory mask\fR, \fIforce create mode\fR
+and \fIforce
+directory mode\fR but the boolean inherit
+permissions parameter overrides this.
+New directories inherit the mode of the parent directory,
+including bits such as setgid.
-This can be particularly useful on large systems with many users, perhaps several thousand, to allow a single [homes] share to be used flexibly by each user\&.
+New files inherit their read/write bits from the parent
+directory. Their execute bits continue to be determined by
+\fImap archive\fR
+, \fImap hidden\fR
+and \fImap system\fR
+as usual.
+Note that the setuid bit is \fBnever\fR set via
+inheritance (the code explicitly prohibits this).
-See also \fIcreate mask \fR, \fI directory mask\fR, \fIforce create mode\fR and \fIforce directory mode\fR \&.
+This can be particularly useful on large systems with
+many users, perhaps several thousand, to allow a single [homes]
+share to be used flexibly by each user.
+See also \fIcreate mask
+\fR, \fI directory mask\fR, \fIforce create mode\fR and \fIforce directory mode\fR
+\&.
Default: \fBinherit permissions = no\fR
-
-
.TP
-interfaces (G)
-This option allows you to override the default network interfaces list that Samba will use for browsing, name registration and other NBT traffic\&. By default Samba will query the kernel for the list of all active interfaces and use any interfaces except 127\&.0\&.0\&.1 that are broadcast capable\&.
-
-
-The option takes a list of interface strings\&. Each string can be in any of the following forms:
-
-
-a network interface name (such as eth0)\&. This may include shell-like wildcards so eth* will match any interface starting with the substring "eth"
-
-an IP address\&. In this case the netmask is determined from the list of interfaces obtained from the kernel
-
-an IP/mask pair\&.
-
-a broadcast/mask pair\&.
-
-The "mask" parameters can either be a bit length (such as 24 for a C class network) or a full netmask in dotted decimal form\&.
+\fBinterfaces (G)\fR
+This option allows you to override the default
+network interfaces list that Samba will use for browsing, name
+registration and other NBT traffic. By default Samba will query
+the kernel for the list of all active interfaces and use any
+interfaces except 127.0.0.1 that are broadcast capable.
+The option takes a list of interface strings. Each string
+can be in any of the following forms:
+.RS
+.TP 0.2i
+\(bu
+a network interface name (such as eth0).
+This may include shell-like wildcards so eth* will match
+any interface starting with the substring "eth"
+.TP 0.2i
+\(bu
+an IP address. In this case the netmask is
+determined from the list of interfaces obtained from the
+kernel
+.TP 0.2i
+\(bu
+an IP/mask pair.
+.TP 0.2i
+\(bu
+a broadcast/mask pair.
+.RE
-The "IP" parameters above can either be a full dotted decimal IP address or a hostname which will be looked up via the OS's normal hostname resolution mechanisms\&.
+The "mask" parameters can either be a bit length (such
+as 24 for a C class network) or a full netmask in dotted
+decimal form.
+The "IP" parameters above can either be a full dotted
+decimal IP address or a hostname which will be looked up via
+the OS's normal hostname resolution mechanisms.
For example, the following line:
+\fBinterfaces = eth0 192.168.2.10/24 192.168.3.10/255.255.255.0
+\fR
-\fBinterfaces = eth0 192.168.2.10/24 192.168.3.10/255.255.255.0\fR
-
-
-would configure three network interfaces corresponding to the eth0 device and IP addresses 192\&.168\&.2\&.10 and 192\&.168\&.3\&.10\&. The netmasks of the latter two interfaces would be set to 255\&.255\&.255\&.0\&.
-
-
-See also \fIbind interfaces only\fR\&.
-
-
-Default: \fBall active interfaces except 127\&.0\&.0\&.1 that are broadcast capable\fR
+would configure three network interfaces corresponding
+to the eth0 device and IP addresses 192.168.2.10 and 192.168.3.10.
+The netmasks of the latter two interfaces would be set to 255.255.255.0.
+See also \fIbind
+interfaces only\fR.
+Default: \fBall active interfaces except 127.0.0.1
+that are broadcast capable\fR
.TP
-invalid users (S)
-This is a list of users that should not be allowed to login to this service\&. This is really a \fBparanoid\fR check to absolutely ensure an improper setting does not breach your security\&.
-
-
-A name starting with a '@' is interpreted as an NIS netgroup first (if your system supports NIS), and then as a UNIX group if the name was not found in the NIS netgroup database\&.
+\fBinvalid users (S)\fR
+This is a list of users that should not be allowed
+to login to this service. This is really a \fBparanoid\fR
+check to absolutely ensure an improper setting does not breach
+your security.
+A name starting with a '@' is interpreted as an NIS
+netgroup first (if your system supports NIS), and then as a UNIX
+group if the name was not found in the NIS netgroup database.
-A name starting with '+' is interpreted only by looking in the UNIX group database\&. A name starting with '&' is interpreted only by looking in the NIS netgroup database (this requires NIS to be working on your system)\&. The characters '+' and '&' may be used at the start of the name in either order so the value \fI+&group\fR means check the UNIX group database, followed by the NIS netgroup database, and the value \fI&+group\fR means check the NIS netgroup database, followed by the UNIX group database (the same as the '@' prefix)\&.
+A name starting with '+' is interpreted only
+by looking in the UNIX group database. A name starting with
+\&'&' is interpreted only by looking in the NIS netgroup database
+(this requires NIS to be working on your system). The characters
+\&'+' and '&' may be used at the start of the name in either order
+so the value \fI+&group\fR means check the
+UNIX group database, followed by the NIS netgroup database, and
+the value \fI&+group\fR means check the NIS
+netgroup database, followed by the UNIX group database (the
+same as the '@' prefix).
+The current servicename is substituted for \fI%S\fR.
+This is useful in the [homes] section.
-The current servicename is substituted for \fI%S\fR\&. This is useful in the [homes] section\&.
-
-
-See also \fIvalid users \fR\&.
-
+See also \fIvalid users
+\fR.
Default: \fBno invalid users\fR
-
-Example: \fBinvalid users = root fred admin @wheel\fR
-
-
+Example: \fBinvalid users = root fred admin @wheel
+\fR
.TP
-keepalive (G)
-The value of the parameter (an integer) represents the number of seconds between \fIkeepalive\fR packets\&. If this parameter is zero, no keepalive packets will be sent\&. Keepalive packets, if sent, allow the server to tell whether a client is still present and responding\&.
-
-
-Keepalives should, in general, not be needed if the socket being used has the SO_KEEPALIVE attribute set on it (see \fIsocket options\fR)\&. Basically you should only use this option if you strike difficulties\&.
+\fBkeepalive (G)\fR
+The value of the parameter (an integer) represents
+the number of seconds between \fIkeepalive\fR
+packets. If this parameter is zero, no keepalive packets will be
+sent. Keepalive packets, if sent, allow the server to tell whether
+a client is still present and responding.
+Keepalives should, in general, not be needed if the socket
+being used has the SO_KEEPALIVE attribute set on it (see \fIsocket options\fR).
+Basically you should only use this option if you strike difficulties.
Default: \fBkeepalive = 300\fR
-
Example: \fBkeepalive = 600\fR
-
-
.TP
-kernel oplocks (G)
-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\&.
-
+\fBkernel oplocks (G)\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.
-Kernel oplocks support allows Samba \fIoplocks \fR to be broken whenever a local UNIX process or NFS operation accesses a file that \fBsmbd\fR(8) has oplocked\&. This allows complete data consistency between SMB/CIFS, NFS and local file access (and is a \fBvery\fR cool feature :-)\&.
+Kernel oplocks support allows Samba \fIoplocks
+\fR to be broken whenever a local UNIX process or NFS operation
+accesses a file that \fBsmbd(8)\fR
+ has oplocked. This allows complete data consistency between
+SMB/CIFS, NFS and local file access (and is a \fBvery\fR
+cool feature :-).
+This parameter defaults to on, but is translated
+to a no-op on systems that no not have the necessary kernel support.
+You should never need to touch this parameter.
-This parameter defaults to \fBon\fR, but is translated to a no-op on systems that no not have the necessary kernel support\&. You should never need to touch this parameter\&.
-
-
-See also the \fIoplocks\fR and \fIlevel2 oplocks \fR parameters\&.
-
+See also the \fIoplocks\fR
+and \fIlevel2 oplocks
+\fR parameters.
Default: \fBkernel oplocks = yes\fR
-
-
.TP
-lanman auth (G)
-This parameter determines whether or not \fBsmbd\fR(8) will attempt to authenticate users using the LANMAN password hash\&. If disabled, only clients which support NT password hashes (e\&.g\&. Windows NT/2000 clients, smbclient, etc\&.\&.\&. but not Windows 95/98 or the MS DOS network client) will be able to connect to the Samba host\&.
-
+\fBlanman auth (G)\fR
+This parameter determines whether or not smbd will
+attempt to authenticate users using the LANMAN password hash.
+If disabled, only clients which support NT password hashes (e.g. Windows
+NT/2000 clients, smbclient, etc... but not Windows 95/98 or the MS DOS
+network client) will be able to connect to the Samba host.
Default : \fBlanman auth = yes\fR
-
-
-.TP
-large readwrite (G)
-This parameter determines whether or not \fBsmbd\fR(8) supports the new 64k streaming read and write varient SMB requests introduced with Windows 2000\&. Note that due to Windows 2000 client redirector bugs this requires Samba to be running on a 64-bit capable operating system such as IRIX, Solaris or a Linux 2\&.4 kernel\&. Can improve performance by 10% with Windows 2000 clients\&. Defaults to on\&. Not as tested as some other Samba code paths\&.
-
-
-Default: \fBlarge readwrite = yes\fR
-
-
-.TP
-ldap admin dn (G)
-The \fIldap admin dn\fR defines the Distinguished Name (DN) name used by Samba to contact the ldap server when retreiving user account information\&. The \fIldap admin dn\fR is used in conjunction with the admin dn password stored in the \fIprivate/secrets\&.tdb\fR file\&. See the \fBsmbpasswd\fR(8) man page for more information on how to accmplish this\&.
-
-
-.TP
-ldap delete dn (G)
-This parameter specifies whether a delete operation in the ldapsam deletes the complete entry or only the attributes specific to Samba\&.
-
-
-Default: \fBldap delete dn = no\fR
-
-
.TP
-ldap filter (G)
-This parameter specifies the RFC 2254 compliant LDAP search filter\&. The default is to match the login name with the \fBuid\fR attribute for all entries matching the \fBsambaAccount\fR objectclass\&. Note that this filter should only return one entry\&.
-
-
-Default: \fBldap filter = (&(uid=%u)(objectclass=sambaAccount))\fR
-
-
-.TP
-ldap machine suffix (G)
-It specifies where machines should be added to the ldap tree\&.
-
-
-Default: \fBnone\fR
-
-
-.TP
-ldap passwd sync (G)
-This option is used to define whether or not Samba should sync the LDAP password with the NT and LM hashes for normal accounts (NOT for workstation, server or domain trusts) on a password change via SAMBA\&.
-
-
-The \fIldap passwd sync\fR can be set to one of three values:
-
-
-\fIYes\fR = Try to update the LDAP, NT and LM passwords and update the pwdLastSet time\&.
-
-\fINo\fR = Update NT and LM passwords and update the pwdLastSet time\&.
-
-\fIOnly\fR = Only update the LDAP password and let the LDAP server do the rest\&.
-
-Default: \fBldap passwd sync = no\fR
-
-
-.TP
-ldap port (G)
-This parameter is only available if Samba has been configure to include the \fB--with-ldapsam\fR option at compile time\&.
-
-
-This option is used to control the tcp port number used to contact the \fIldap server\fR\&. The default is to use the stand LDAPS port 636\&.
-
+\fBlarge readwrite (G)\fR
+This parameter determines whether or not smbd
+supports the new 64k streaming read and write varient SMB requests introduced
+with Windows 2000. Note that due to Windows 2000 client redirector bugs
+this requires Samba to be running on a 64-bit capable operating system such
+as IRIX, Solaris or a Linux 2.4 kernel. Can improve performance by 10% with
+Windows 2000 clients. Defaults to on. Not as tested as some other Samba
+code paths.
+
+Default : \fBlarge readwrite = yes\fR
+.TP
+\fBldap admin dn (G)\fR
+The \fIldap admin dn\fR defines the Distinguished
+Name (DN) name used by Samba to contact the ldap server when retreiving
+user account information. The \fIldap
+admin dn\fR is used in conjunction with the admin dn password
+stored in the \fIprivate/secrets.tdb\fR file. See the
+\fBsmbpasswd(8)\fR man
+page for more information on how to accomplish this.
+.TP
+\fB>ldap del only sam attr (G)\fR
+This parameter specifies whether a delete
+operation in the ldapsam deletes the complete entry or only the attributes
+specific to Samba.
+
+Default : \fBldap delete dn = no\fR
+.TP
+\fB>ldap del only sam attr (G)\fR
+Inverted synonym for \fI ldap delete dn\fR.
+.TP
+\fBldap filter (G)\fR
+This parameter specifies the RFC 2254 compliant LDAP search filter.
+The default is to match the login name with the uid
+attribute for all entries matching the sambaAccount
+objectclass. Note that this filter should only return one entry.
+
+Default : \fBldap filter = (&(uid=%u)(objectclass=sambaAccount))\fR
+.TP
+\fBldap port (G)\fR
+This parameter is only available if Samba has been
+configure to include the \fB--with-ldapsam\fR option
+at compile time.
+
+This option is used to control the tcp port number used to contact
+the \fIldap server\fR.
+The default is to use the stand LDAPS port 636.
See Also: ldap ssl
-
Default : \fBldap port = 636 ; if ldap ssl = on\fR
-
Default : \fBldap port = 389 ; if ldap ssl = off\fR
-
-
.TP
-ldap server (G)
-This parameter is only available if Samba has been configure to include the \fB--with-ldapsam\fR option at compile time\&.
-
-
-This parameter should contain the FQDN of the ldap directory server which should be queried to locate user account information\&.
+\fBldap server (G)\fR
+This parameter is only available if Samba has been
+configure to include the \fB--with-ldapsam\fR option
+at compile time.
+This parameter should contain the FQDN of the ldap directory
+server which should be queried to locate user account information.
Default : \fBldap server = localhost\fR
-
-
.TP
-ldap ssl (G)
-This option is used to define whether or not Samba should use SSL when connecting to the ldap server This is \fBNOT\fR related to Samba's previous SSL support which was enabled by specifying the \fB--with-ssl\fR option to the \fIconfigure\fR script\&.
-
+\fBldap ssl (G)\fR
+This option is used to define whether or not Samba should
+use SSL when connecting to the ldap server
+This is \fBNOT\fR related to
+Samba's previous SSL support which was enabled by specifying the
+\fB--with-ssl\fR option to the \fIconfigure\fR
+script.
The \fIldap ssl\fR can be set to one of three values:
-
-
-\fIOff\fR = Never use SSL when querying the directory\&.
-
-\fIStart_tls\fR = Use the LDAPv3 StartTLS extended operation (RFC2830) for communicating with the directory server\&.
-
-\fIOn\fR = Use SSL on the ldaps port when contacting the \fIldap server\fR\&. Only available when the backwards-compatiblity \fB--with-ldapsam\fR option is specified to configure\&. See \fIpassdb backend\fR
+.RS
+.TP 0.2i
+\(bu
+\fIOff\fR = Never use SSL when querying the directory.
+.TP 0.2i
+\(bu
+\fIStart_tls\fR = Use the LDAPv3 StartTLS extended operation
+(RFC2830) for communicating with the directory server.
+.TP 0.2i
+\(bu
+\fIOn\fR =
+Use SSL on the ldaps port when contacting the
+\fIldap server\fR. Only
+available when the backwards-compatiblity \fB --with-ldapsam\fR option is specified
+to configure. See \fIpassdb backend\fR
+.RE
Default : \fBldap ssl = start_tls\fR
-
-
.TP
-ldap suffix (G)
-Specifies where user and machine accounts are added to the tree\&. Can be overriden by \fBldap user suffix\fR and \fBldap machine suffix\fR\&. It also used as the base dn for all ldap searches\&.
-
-
-Default: \fBnone\fR
-
+\fBldap suffix (G)\fR
+Specifies where user and machine accounts are added to the tree. Can be overriden by \fBldap user suffix\fR and \fBldap machine suffix\fR. It also used as the base dn for all ldap searches.
+Default : \fBnone\fR
.TP
-ldap trust ids (G)
-Normally, Samba validates each entry in the LDAP server against getpwnam()\&. This allows LDAP to be used for Samba with the unix system using NIS (for example) and also ensures that Samba does not present accounts that do not otherwise exist\&.
-
-
-This option is used to disable this functionality, and instead to rely on the presence of the appropriate attributes in LDAP directly, which can result in a significant performance boost in some situations\&. Setting this option to yes effectivly assumes that the local machine is running \fBnss_ldap\fR against the same LDAP server\&.
-
-
-Default: \fBldap trust ids = No\fR
-
+\fBldap user suffix (G)\fR
+It specifies where users are added to the tree.
+Default : \fBnone\fR
.TP
-ldap user suffix (G)
-It specifies where users are added to the tree\&.
-
-
-Default: \fBnone\fR
-
+\fBldap machine suffix (G)\fR
+It specifies where machines should be
+added to the ldap tree.
+Default : \fBnone\fR
.TP
-level2 oplocks (S)
-This parameter controls whether Samba supports level2 (read-only) oplocks on a share\&.
-
-
-Level2, or read-only oplocks allow Windows NT clients that have an oplock on a file to downgrade from a read-write oplock to a read-only oplock once a second client opens the file (instead 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 accesses of files that are not commonly written (such as application \&.EXE files)\&.
-
-
-Once one of the clients which have a read-only oplock writes to the file all clients are notified (no reply is needed or waited for) and told to break their oplocks to "none" and delete any read-ahead caches\&.
-
+\fBldap passwd sync (G)\fR
+This option is used to define whether
+or not Samba should sync the LDAP password with the NT
+and LM hashes for normal accounts (NOT for
+workstation, server or domain trusts) on a password
+change via SAMBA.
-It is recommended that this parameter be turned on to speed access to shared executables\&.
-
-
-For more discussions on level2 oplocks see the CIFS spec\&.
-
-
-Currently, if \fIkernel oplocks\fR are supported then level2 oplocks are not granted (even if this parameter is set to \fByes\fR)\&. Note also, the \fIoplocks\fR parameter must be set to \fByes\fR on this share in order for this parameter to have any effect\&.
+The \fIldap passwd sync\fR can be set to one of three values:
+.RS
+.TP 0.2i
+\(bu
+\fIYes\fR = Try to update the LDAP, NT and LM passwords and update the pwdLastSet time.
+.TP 0.2i
+\(bu
+\fINo\fR = Update NT and LM passwords and update the pwdLastSet time.
+.TP 0.2i
+\(bu
+\fIOnly\fR = Only update the LDAP password and let the LDAP server do the rest.
+.RE
+Default : \fBldap passwd sync = no\fR
+.TP
+\fBldap trust ids (G)\fR
+Normally, Samba validates each entry
+in the LDAP server against getpwnam(). This allows
+LDAP to be used for Samba with the unix system using
+NIS (for example) and also ensures that Samba does not
+present accounts that do not otherwise exist.
-See also the \fIoplocks\fR and \fIkernel oplocks\fR parameters\&.
+This option is used to disable this functionality, and
+instead to rely on the presence of the appropriate
+attributes in LDAP directly, which can result in a
+significant performance boost in some situations.
+Setting this option to yes effectivly assumes
+that the local machine is running \fBnss_ldap\fR against the
+same LDAP server.
+Default: \fBldap trust ids = No\fR
+.TP
+\fBlevel2 oplocks (S)\fR
+This parameter controls whether Samba supports
+level2 (read-only) oplocks on a share.
+
+Level2, or read-only oplocks allow Windows NT clients
+that have an oplock on a file to downgrade from a read-write oplock
+to a read-only oplock once a second client opens the file (instead
+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 accesses of files that are not commonly written (such as
+application .EXE files).
+
+Once one of the clients which have a read-only oplock
+writes to the file all clients are notified (no reply is needed
+or waited for) and told to break their oplocks to "none" and
+delete any read-ahead caches.
+
+It is recommended that this parameter be turned on
+to speed access to shared executables.
+
+For more discussions on level2 oplocks see the CIFS spec.
+
+Currently, if \fIkernel
+oplocks\fR are supported then level2 oplocks are
+not granted (even if this parameter is set to yes).
+Note also, the \fIoplocks\fR
+parameter must be set to yes on this share in order for
+this parameter to have any effect.
+
+See also the \fIoplocks\fR
+and \fIkernel oplocks\fR
+parameters.
Default: \fBlevel2 oplocks = yes\fR
-
-
.TP
-lm announce (G)
-This parameter determines if \fBnmbd\fR(8) will produce Lanman announce broadcasts that are needed by OS/2 clients in order for them to see the Samba server in their browse list\&. This parameter can have three values, \fByes\fR, \fBno\fR, or \fBauto\fR\&. The default is \fBauto\fR\&. If set to \fBno\fR Samba will never produce these broadcasts\&. If set to \fByes\fR Samba will produce Lanman announce broadcasts at a frequency set by the parameter \fIlm interval\fR\&. If set to \fBauto\fR Samba will not send Lanman announce broadcasts by default but will listen for them\&. If it hears such a broadcast on the wire it will then start sending them at a frequency set by the parameter \fIlm interval\fR\&.
-
-
-See also \fIlm interval\fR\&.
-
+\fBlm announce (G)\fR
+This parameter determines if \fBnmbd(8)\fR will produce Lanman announce
+broadcasts that are needed by OS/2 clients in order for them to see
+the Samba server in their browse list. This parameter can have three
+values, yes, no, or
+auto. The default is auto.
+If set to no Samba will never produce these
+broadcasts. If set to yes Samba will produce
+Lanman announce broadcasts at a frequency set by the parameter
+\fIlm interval\fR. If set to auto
+Samba will not send Lanman announce broadcasts by default but will
+listen for them. If it hears such a broadcast on the wire it will
+then start sending them at a frequency set by the parameter
+\fIlm interval\fR.
+
+See also \fIlm interval
+\fR.
Default: \fBlm announce = auto\fR
-
Example: \fBlm announce = yes\fR
-
-
.TP
-lm interval (G)
-If Samba is set to produce Lanman announce broadcasts needed by OS/2 clients (see the \fIlm announce\fR parameter) then this parameter defines the frequency in seconds with which they will be made\&. If this is set to zero then no Lanman announcements will be made despite the setting of the \fIlm announce\fR parameter\&.
-
-
-See also \fIlm announce\fR\&.
+\fBlm interval (G)\fR
+If Samba is set to produce Lanman announce
+broadcasts needed by OS/2 clients (see the \fIlm announce\fR parameter) then this
+parameter defines the frequency in seconds with which they will be
+made. If this is set to zero then no Lanman announcements will be
+made despite the setting of the \fIlm announce\fR
+parameter.
+See also \fIlm
+announce\fR.
Default: \fBlm interval = 60\fR
-
Example: \fBlm interval = 120\fR
-
-
.TP
-load printers (G)
-A boolean variable that controls whether all printers in the printcap will be loaded for browsing by default\&. See the printers section for more details\&.
-
+\fBload printers (G)\fR
+A boolean variable that controls whether all
+printers in the printcap will be loaded for browsing by default.
+See the printers section for
+more details.
Default: \fBload printers = yes\fR
-
-
.TP
-local master (G)
-This option allows \fBnmbd\fR(8) to try and become a local master browser on a subnet\&. If set to \fBno\fR then \fB nmbd\fR will not attempt to become a local master browser on a subnet and will also lose in all browsing elections\&. By default this value is set to \fByes\fR\&. Setting this value to \fByes\fR doesn't mean that Samba will \fBbecome\fR the local master browser on a subnet, just that \fBnmbd\fR will \fBparticipate\fR in elections for local master browser\&.
-
-
-Setting this value to \fBno\fR will cause \fBnmbd\fR \fBnever\fR to become a local master browser\&.
+\fBlocal master (G)\fR
+This option allows \fB nmbd(8)\fR to try and become a local master browser
+on a subnet. If set to no then \fB nmbd\fR will not attempt to become a local master browser
+on a subnet and will also lose in all browsing elections. By
+default this value is set to yes. Setting this value to yes doesn't
+mean that Samba will \fBbecome\fR the local master
+browser on a subnet, just that \fBnmbd\fR will \fB participate\fR in elections for local master browser.
+Setting this value to no will cause \fBnmbd\fR
+\fBnever\fR to become a local master browser.
Default: \fBlocal master = yes\fR
-
-
.TP
-lock directory (G)
-This option specifies the directory where lock files will be placed\&. The lock files are used to implement the \fImax connections\fR option\&.
-
+\fBlock dir (G)\fR
+Synonym for \fI lock directory\fR.
+.TP
+\fBlock directory (G)\fR
+This option specifies the directory where lock
+files will be placed. The lock files are used to implement the
+\fImax connections\fR
+option.
Default: \fBlock directory = ${prefix}/var/locks\fR
-
Example: \fBlock directory = /var/run/samba/locks\fR
-
-
.TP
-lock dir (G)
-Synonym for \fI lock directory\fR\&.
-
-
-.TP
-locking (S)
-This controls whether or not locking will be performed by the server in response to lock requests from the client\&.
-
-
-If \fBlocking = no\fR, all lock and unlock requests will appear to succeed and all lock queries will report that the file in question is available for locking\&.
-
-
-If \fBlocking = yes\fR, real locking will be performed by the server\&.
-
-
-This option \fBmay\fR be useful for read-only filesystems which \fBmay\fR not need locking (such as CDROM drives), although setting this parameter of \fBno\fR is not really recommended even in this case\&.
-
-
-Be careful about disabling locking either globally or in a specific service, as lack of locking may result in data corruption\&. You should never need to set this parameter\&.
-
-
-Default: \fBlocking = yes\fR
-
-
-.TP
-lock spin count (G)
-This parameter controls the number of times that smbd should attempt to gain a byte range lock on the behalf of a client request\&. Experiments have shown that Windows 2k servers do not reply with a failure if the lock could not be immediately granted, but try a few more times in case the lock could later be aquired\&. This behavior is used to support PC database formats such as MS Access and FoxPro\&.
-
+\fBlock spin count (G)\fR
+This parameter controls the number of times
+that smbd should attempt to gain a byte range lock on the
+behalf of a client request. Experiments have shown that
+Windows 2k servers do not reply with a failure if the lock
+could not be immediately granted, but try a few more times
+in case the lock could later be aquired. This behavior
+is used to support PC database formats such as MS Access
+and FoxPro.
Default: \fBlock spin count = 2\fR
-
-
.TP
-lock spin time (G)
-The time in microseconds that smbd should pause before attempting to gain a failed lock\&. See \fIlock spin count\fR for more details\&.
-
+\fBlock spin time (G)\fR
+The time in microseconds that smbd should
+pause before attempting to gain a failed lock. See
+\fIlock spin
+count\fR for more details.
Default: \fBlock spin time = 10\fR
-
-
.TP
-log file (G)
-This option allows you to override the name of the Samba log file (also known as the debug file)\&.
-
+\fBlocking (S)\fR
+This controls whether or not locking will be
+performed by the server in response to lock requests from the
+client.
-This option takes the standard substitutions, allowing you to have separate log files for each user or machine\&.
+If \fBlocking = no\fR, all lock and unlock
+requests will appear to succeed and all lock queries will report
+that the file in question is available for locking.
+If \fBlocking = yes\fR, real locking will be performed
+by the server.
-Example: \fBlog file = /usr/local/samba/var/log.%m\fR
+This option \fBmay\fR be useful for read-only
+filesystems which \fBmay\fR not need locking (such as
+CDROM drives), although setting this parameter of no
+is not really recommended even in this case.
+Be careful about disabling locking either globally or in a
+specific service, as lack of locking may result in data corruption.
+You should never need to set this parameter.
+Default: \fBlocking = yes\fR
.TP
-log level (G)
-The value of the parameter (a astring) allows the debug level (logging level) to be specified in the \fIsmb\&.conf\fR file\&. This parameter has been extended since the 2\&.2\&.x series, now it allow to specify the debug level for multiple debug classes\&. This is to give greater flexibility in the configuration of the system\&.
-
-
-The default will be the log level specified on the command line or level zero if none was specified\&.
-
-
-Example: \fBlog level = 3 passdb:5 auth:10 winbind:2\fR
+\fBlog file (G)\fR
+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
+you to have separate log files for each user or machine.
+Example: \fBlog file = /usr/local/samba/var/log.%m
+\fR
.TP
-logon drive (G)
-This parameter specifies the local path to which the home directory will be connected (see \fIlogon home\fR) and is only used by NT Workstations\&.
+\fBlog level (G)\fR
+The value of the parameter (a astring) allows
+the debug level (logging level) to be specified in the
+\fIsmb.conf\fR file. This parameter has been
+extended since the 2.2.x series, now it allow to specify the debug
+level for multiple debug classes. This is to give greater
+flexibility in the configuration of the system.
+The default will be the log level specified on
+the command line or level zero if none was specified.
-Note that this option is only useful if Samba is set up as a logon server\&.
+Example: \fBlog level = 3 passdb:5 auth:10 winbind:2
+\fR
+.TP
+\fBlogon drive (G)\fR
+This parameter specifies the local path to
+which the home directory will be connected (see \fIlogon home\fR)
+and is only used by NT Workstations.
+Note that this option is only useful if Samba is set up as a
+logon server.
Default: \fBlogon drive = z:\fR
-
Example: \fBlogon drive = h:\fR
-
-
.TP
-logon home (G)
-This parameter specifies the home directory location when a Win95/98 or NT Workstation logs into a Samba PDC\&. It allows you to do
-
+\fBlogon home (G)\fR
+This parameter specifies the home directory
+location when a Win95/98 or NT Workstation logs into a Samba PDC.
+It allows you to do
C:\\> \fBNET USE H: /HOME\fR
+from a command prompt, for example.
-from a command prompt, for example\&.
+This option takes the standard substitutions, allowing
+you to have separate logon scripts for each user or machine.
+This parameter can be used with Win9X workstations to ensure
+that roaming profiles are stored in a subdirectory of the user's
+home directory. This is done in the following way:
-This option takes the standard substitutions, allowing you to have separate logon scripts for each user or machine\&.
+\fBlogon home = \\\\%N\\%U\\profile\fR
+This tells Samba to return the above string, with
+substitutions made when a client requests the info, generally
+in a NetUserGetInfo request. Win9X clients truncate the info to
+\\\\server\\share when a user does \fBnet use /home\fR
+but use the whole string when dealing with profiles.
-This parameter can be used with Win9X workstations to ensure that roaming profiles are stored in a subdirectory of the user's home directory\&. This is done in the following way:
+Note that in prior versions of Samba, the \fIlogon path\fR was returned rather than
+\fIlogon home\fR. This broke \fBnet use
+/home\fR but allowed profiles outside the home directory.
+The current implementation is correct, and can be used for
+profiles if you use the above trick.
+This option is only useful if Samba is set up as a logon
+server.
-\fBlogon home = \\%N\%U\profile\fR
-
-
-This tells Samba to return the above string, with substitutions made when a client requests the info, generally in a NetUserGetInfo request\&. Win9X clients truncate the info to \\\\server\\share when a user does \fBnet use /home\fR but use the whole string when dealing with profiles\&.
-
-
-Note that in prior versions of Samba, the \fIlogon path\fR was returned rather than \fIlogon home\fR\&. This broke \fBnet use /home\fR but allowed profiles outside the home directory\&. The current implementation is correct, and can be used for profiles if you use the above trick\&.
-
-
-This option is only useful if Samba is set up as a logon server\&.
-
-
-Default: \fBlogon home = "\\%N\%U"\fR
-
-
-Example: \fBlogon home = "\\remote_smb_server\%U"\fR
-
+Default: \fBlogon home = "\\\\%N\\%U"\fR
+Example: \fBlogon home = "\\\\remote_smb_server\\%U"\fR
.TP
-logon path (G)
-This parameter specifies the home directory where roaming profiles (NTuser\&.dat etc files for Windows NT) are stored\&. Contrary to previous versions of these manual pages, it has nothing to do with Win 9X roaming profiles\&. To find out how to handle roaming profiles for Win 9X system, see the \fIlogon home\fR parameter\&.
-
+\fBlogon path (G)\fR
+This parameter specifies the home directory
+where roaming profiles (NTuser.dat etc files for Windows NT) are
+stored. Contrary to previous versions of these manual pages, it has
+nothing to do with Win 9X roaming profiles. To find out how to
+handle roaming profiles for Win 9X system, see the \fIlogon home\fR parameter.
-This option takes the standard substitutions, allowing you to have separate logon scripts for each user or machine\&. It also specifies the directory from which the "Application Data", (\fIdesktop\fR, \fIstart menu\fR, \fInetwork neighborhood\fR, \fIprograms\fR and other folders, and their contents, are loaded and displayed on your Windows NT client\&.
+This option takes the standard substitutions, allowing you
+to have separate logon scripts for each user or machine. It also
+specifies the directory from which the "Application Data",
+(\fIdesktop\fR, \fIstart menu\fR,
+\fInetwork neighborhood\fR, \fIprograms\fR
+and other folders, and their contents, are loaded and displayed on
+your Windows NT client.
+The share and the path must be readable by the user for
+the preferences and directories to be loaded onto the Windows NT
+client. The share must be writeable when the user logs in for the first
+time, in order that the Windows NT client can create the NTuser.dat
+and other directories.
-The share and the path must be readable by the user for the preferences and directories to be loaded onto the Windows NT client\&. The share must be writeable when the user logs in for the first time, in order that the Windows NT client can create the NTuser\&.dat and other directories\&.
+Thereafter, the directories and any of the contents can,
+if required, be made read-only. It is not advisable that the
+NTuser.dat file be made read-only - rename it to NTuser.man to
+achieve the desired effect (a \fBMAN\fRdatory
+profile).
+Windows clients can sometimes maintain a connection to
+the [homes] share, even though there is no user logged in.
+Therefore, it is vital that the logon path does not include a
+reference to the homes share (i.e. setting this parameter to
+\\%N\\%U\\profile_path will cause problems).
-Thereafter, the directories and any of the contents can, if required, be made read-only\&. It is not advisable that the NTuser\&.dat file be made read-only - rename it to NTuser\&.man to achieve the desired effect (a \fBMAN\fRdatory profile)\&.
+This option takes the standard substitutions, allowing
+you to have separate logon scripts for each user or machine.
+Note that this option is only useful if Samba is set up
+as a logon server.
-Windows clients can sometimes maintain a connection to the [homes] share, even though there is no user logged in\&. Therefore, it is vital that the logon path does not include a reference to the homes share (i\&.e\&. setting this parameter to \\%N\\%U\\profile_path will cause problems)\&.
-
-
-This option takes the standard substitutions, allowing you to have separate logon scripts for each user or machine\&.
-
-
-Note that this option is only useful if Samba is set up as a logon server\&.
-
-
-Default: \fBlogon path = \\%N\%U\profile\fR
-
-
-Example: \fBlogon path = \\PROFILESERVER\PROFILE\%U\fR
-
+Default: \fBlogon path = \\\\%N\\%U\\profile\fR
+Example: \fBlogon path = \\\\PROFILESERVER\\PROFILE\\%U\fR
.TP
-logon script (G)
-This parameter specifies the batch file (\&.bat) or NT command file (\&.cmd) to be downloaded and run on a machine when a user successfully logs in\&. The file must contain the DOS style CR/LF line endings\&. Using a DOS-style editor to create the file is recommended\&.
-
-
-The script must be a relative path to the [netlogon] service\&. If the [netlogon] service specifies a \fIpath\fR of \fI/usr/local/samba/netlogon\fR, and \fBlogon script = STARTUP.BAT\fR, then the file that will be downloaded is:
-
+\fBlogon script (G)\fR
+This parameter specifies the batch file (.bat) or
+NT command file (.cmd) to be downloaded and run on a machine when
+a user successfully logs in. The file must contain the DOS
+style CR/LF line endings. Using a DOS-style editor to create the
+file is recommended.
-\fI/usr/local/samba/netlogon/STARTUP\&.BAT\fR
+The script must be a relative path to the [netlogon]
+service. If the [netlogon] service specifies a \fIpath\fR of \fI/usr/local/samba/netlogon
+\fR, and \fBlogon script = STARTUP.BAT\fR, then
+the file that will be downloaded is:
+\fI/usr/local/samba/netlogon/STARTUP.BAT\fR
-The contents of the batch file are entirely your choice\&. A suggested command would be to add \fBNET TIME \\SERVER /SET /YES\fR, to force every machine to synchronize clocks with the same time server\&. Another use would be to add \fBNET USE U: \\SERVER\UTILS\fR for commonly used utilities, or \fB NET USE Q: \\SERVER\ISO9001_QA\fR for example\&.
+The contents of the batch file are entirely your choice. A
+suggested command would be to add \fBNET TIME \\\\SERVER /SET
+/YES\fR, to force every machine to synchronize clocks with
+the same time server. Another use would be to add \fBNET USE
+U: \\\\SERVER\\UTILS\fR for commonly used utilities, or \fB NET USE Q: \\\\SERVER\\ISO9001_QA\fR for example.
+Note that it is particularly important not to allow write
+access to the [netlogon] share, or to grant users write permission
+on the batch files in a secure environment, as this would allow
+the batch files to be arbitrarily modified and security to be
+breached.
-Note that it is particularly important not to allow write access to the [netlogon] share, or to grant users write permission on the batch files in a secure environment, as this would allow the batch files to be arbitrarily modified and security to be breached\&.
-
-
-This option takes the standard substitutions, allowing you to have separate logon scripts for each user or machine\&.
-
-
-This option is only useful if Samba is set up as a logon server\&.
-
+This option takes the standard substitutions, allowing you
+to have separate logon scripts for each user or machine.
+
+This option is only useful if Samba is set up as a logon
+server.
Default: \fBno logon script defined\fR
-
-Example: \fBlogon script = scripts\%U.bat\fR
-
-
+Example: \fBlogon script = scripts\\%U.bat\fR
.TP
-lppause command (S)
-This parameter specifies the command to be executed on the server host in order to stop printing or spooling a specific print job\&.
-
-
-This command should be a program or script which takes a printer name and job number to pause the print job\&. One way of implementing this is by using job priorities, where jobs having a too low priority won't be sent to the printer\&.
-
-
-If a \fI%p\fR is given then the printer name is put in its place\&. A \fI%j\fR is replaced with the job number (an integer)\&. On HPUX (see \fIprinting=hpux \fR), if the \fI-p%p\fR option is added to the lpq command, the job will show up with the correct status, i\&.e\&. if the job priority is lower than the set fence priority it will have the PAUSED status, whereas if the priority is equal or higher it will have the SPOOLED or PRINTING status\&.
+\fBlppause command (S)\fR
+This parameter specifies the command to be
+executed on the server host in order to stop printing or spooling
+a specific print job.
+This command should be a program or script which takes
+a printer name and job number to pause the print job. One way
+of implementing this is by using job priorities, where jobs
+having a too low priority won't be sent to the printer.
-Note that it is good practice to include the absolute path in the lppause command as the PATH may not be available to the server\&.
+If a \fI%p\fR is given then the printer name
+is put in its place. A \fI%j\fR is replaced with
+the job number (an integer). On HPUX (see \fIprinting=hpux
+\fR), if the \fI-p%p\fR option is added
+to the lpq command, the job will show up with the correct status, i.e.
+if the job priority is lower than the set fence priority it will
+have the PAUSED status, whereas if the priority is equal or higher it
+will have the SPOOLED or PRINTING status.
+Note that it is good practice to include the absolute path
+in the lppause command as the PATH may not be available to the server.
-See also the \fIprinting \fR parameter\&.
-
-
-Default: Currently no default value is given to this string, unless the value of the \fIprinting\fR parameter is \fBSYSV\fR, in which case the default is :
+See also the \fIprinting
+\fR parameter.
+Default: Currently no default value is given to
+this string, unless the value of the \fIprinting\fR
+parameter is SYSV, in which case the default is :
\fBlp -i %p-%j -H hold\fR
-
-or if the value of the \fIprinting\fR parameter is \fBSOFTQ\fR, then the default is:
-
+or if the value of the \fIprinting\fR parameter
+is SOFTQ, then the default is:
\fBqstat -s -j%j -h\fR
-
-Example for HPUX: \fBlppause command = /usr/bin/lpalt %p-%j -p0\fR
-
-
+Example for HPUX: \fBlppause command = /usr/bin/lpalt
+%p-%j -p0\fR
.TP
-lpq cache time (G)
-This controls how long lpq info will be cached for to prevent the \fBlpq\fR command being called too often\&. A separate cache is kept for each variation of the \fB lpq\fR command used by the system, so if you use different \fBlpq\fR commands for different users then they won't share cache information\&.
-
-
-The cache files are stored in \fI/tmp/lpq\&.xxxx\fR where xxxx is a hash of the \fBlpq\fR command in use\&.
-
-
-The default is 10 seconds, meaning that the cached results of a previous identical \fBlpq\fR command will be used if the cached data is less than 10 seconds old\&. A large value may be advisable if your \fBlpq\fR command is very slow\&.
-
+\fBlpq cache time (G)\fR
+This controls how long lpq info will be cached
+for to prevent the \fBlpq\fR command being called too
+often. A separate cache is kept for each variation of the \fB lpq\fR command used by the system, so if you use different
+\fBlpq\fR commands for different users then they won't
+share cache information.
-A value of 0 will disable caching completely\&.
+The cache files are stored in \fI/tmp/lpq.xxxx\fR
+where xxxx is a hash of the \fBlpq\fR command in use.
+The default is 10 seconds, meaning that the cached results
+of a previous identical \fBlpq\fR command will be used
+if the cached data is less than 10 seconds old. A large value may
+be advisable if your \fBlpq\fR command is very slow.
-See also the \fIprinting\fR parameter\&.
+A value of 0 will disable caching completely.
+See also the \fIprinting
+\fR parameter.
Default: \fBlpq cache time = 10\fR
-
Example: \fBlpq cache time = 30\fR
-
-
.TP
-lpq command (S)
-This parameter specifies the command to be executed on the server host in order to obtain \fBlpq \fR-style printer status information\&.
-
-
-This command should be a program or script which takes a printer name as its only parameter and outputs printer status information\&.
-
+\fBlpq command (S)\fR
+This parameter specifies the command to be
+executed on the server host in order to obtain \fBlpq
+\fR-style printer status information.
-Currently nine styles of printer status information are supported; BSD, AIX, LPRNG, PLP, SYSV, HPUX, QNX, CUPS, and SOFTQ\&. This covers most UNIX systems\&. You control which type is expected using the \fIprinting =\fR option\&.
+This command should be a program or script which
+takes a printer name as its only parameter and outputs printer
+status information.
+Currently nine styles of printer status information
+are supported; BSD, AIX, LPRNG, PLP, SYSV, HPUX, QNX, CUPS, and SOFTQ.
+This covers most UNIX systems. You control which type is expected
+using the \fIprinting =\fR option.
-Some clients (notably Windows for Workgroups) may not correctly send the connection number for the printer they are requesting status information about\&. To get around this, the server reports on the first printer service connected to by the client\&. This only happens if the connection number sent is invalid\&.
+Some clients (notably Windows for Workgroups) may not
+correctly send the connection number for the printer they are
+requesting status information about. To get around this, the
+server reports on the first printer service connected to by the
+client. This only happens if the connection number sent is invalid.
+If a \fI%p\fR is given then the printer name
+is put in its place. Otherwise it is placed at the end of the
+command.
-If a \fI%p\fR is given then the printer name is put in its place\&. Otherwise it is placed at the end of the command\&.
+Note that it is good practice to include the absolute path
+in the \fIlpq command\fR as the \fB$PATH
+\fR may not be available to the server. When compiled with
+the CUPS libraries, no \fIlpq command\fR is
+needed because smbd will make a library call to obtain the
+print queue listing.
+See also the \fIprinting
+\fR parameter.
-Note that it is good practice to include the absolute path in the \fIlpq command\fR as the \fB$PATH \fR may not be available to the server\&. When compiled with the CUPS libraries, no \fIlpq command\fR is needed because smbd will make a library call to obtain the print queue listing\&.
-
-
-See also the \fIprinting \fR parameter\&.
-
-
-Default: \fBdepends on the setting of \fI printing\fR\fR
-
+Default: \fBdepends on the setting of \fI printing\fB\fR
Example: \fBlpq command = /usr/bin/lpq -P%p\fR
-
-
.TP
-lpresume command (S)
-This parameter specifies the command to be executed on the server host in order to restart or continue printing or spooling a specific print job\&.
-
-
-This command should be a program or script which takes a printer name and job number to resume the print job\&. See also the \fIlppause command \fR parameter\&.
-
-
-If a \fI%p\fR is given then the printer name is put in its place\&. A \fI%j\fR is replaced with the job number (an integer)\&.
-
-
-Note that it is good practice to include the absolute path in the \fIlpresume command\fR as the PATH may not be available to the server\&.
+\fBlpresume command (S)\fR
+This parameter specifies the command to be
+executed on the server host in order to restart or continue
+printing or spooling a specific print job.
+This command should be a program or script which takes
+a printer name and job number to resume the print job. See
+also the \fIlppause command
+\fR parameter.
-See also the \fIprinting \fR parameter\&.
+If a \fI%p\fR is given then the printer name
+is put in its place. A \fI%j\fR is replaced with
+the job number (an integer).
+Note that it is good practice to include the absolute path
+in the \fIlpresume command\fR as the PATH may not
+be available to the server.
-Default: Currently no default value is given to this string, unless the value of the \fIprinting\fR parameter is \fBSYSV\fR, in which case the default is :
+See also the \fIprinting
+\fR parameter.
+Default: Currently no default value is given
+to this string, unless the value of the \fIprinting\fR
+parameter is SYSV, in which case the default is :
\fBlp -i %p-%j -H resume\fR
-
-or if the value of the \fIprinting\fR parameter is \fBSOFTQ\fR, then the default is:
-
+or if the value of the \fIprinting\fR parameter
+is SOFTQ, then the default is:
\fBqstat -s -j%j -r\fR
-
-Example for HPUX: \fBlpresume command = /usr/bin/lpalt %p-%j -p2\fR
-
-
+Example for HPUX: \fBlpresume command = /usr/bin/lpalt
+%p-%j -p2\fR
.TP
-lprm command (S)
-This parameter specifies the command to be executed on the server host in order to delete a print job\&.
-
+\fBlprm command (S)\fR
+This parameter specifies the command to be
+executed on the server host in order to delete a print job.
-This command should be a program or script which takes a printer name and job number, and deletes the print job\&.
+This command should be a program or script which takes
+a printer name and job number, and deletes the print job.
+If a \fI%p\fR is given then the printer name
+is put in its place. A \fI%j\fR is replaced with
+the job number (an integer).
-If a \fI%p\fR is given then the printer name is put in its place\&. A \fI%j\fR is replaced with the job number (an integer)\&.
+Note that it is good practice to include the absolute
+path in the \fIlprm command\fR as the PATH may not be
+available to the server.
+See also the \fIprinting
+\fR parameter.
-Note that it is good practice to include the absolute path in the \fIlprm command\fR as the PATH may not be available to the server\&.
-
-
-See also the \fIprinting \fR parameter\&.
-
-
-Default: \fBdepends on the setting of \fIprinting \fR\fR
-
-
-Example 1: \fBlprm command = /usr/bin/lprm -P%p %j\fR
-
-
-Example 2: \fBlprm command = /usr/bin/cancel %p-%j\fR
+Default: \fBdepends on the setting of \fIprinting
+\fB\fR
+Example 1: \fBlprm command = /usr/bin/lprm -P%p %j
+\fR
+Example 2: \fBlprm command = /usr/bin/cancel %p-%j
+\fR
.TP
-machine password timeout (G)
-If a Samba server is a member of a Windows NT Domain (see the security = domain) parameter) then periodically a running smbd(8) process will try and change the MACHINE ACCOUNT PASSWORD stored in the TDB called \fIprivate/secrets\&.tdb \fR\&. This parameter specifies how often this password will be changed, in seconds\&. The default is one week (expressed in seconds), the same as a Windows NT Domain member server\&.
-
-
-See also \fBsmbpasswd\fR(8), and the security = domain) parameter\&.
+\fBmachine password timeout (G)\fR
+If a Samba server is a member of a Windows
+NT Domain (see the security = domain)
+parameter) then periodically a running smbd(8) process will try and change the MACHINE ACCOUNT
+PASSWORD stored in the TDB called \fIprivate/secrets.tdb
+\fR. This parameter specifies how often this password
+will be changed, in seconds. The default is one week (expressed in
+seconds), the same as a Windows NT Domain member server.
+See also \fBsmbpasswd(8)
+\fR and the security = domain) parameter.
Default: \fBmachine password timeout = 604800\fR
-
-
.TP
-magic output (S)
-This parameter specifies the name of a file which will contain output created by a magic script (see the \fImagic script\fR parameter below)\&.
-
-
-Warning: If two clients use the same \fImagic script \fR in the same directory the output file content is undefined\&.
-
+\fBmagic output (S)\fR
+This parameter specifies the name of a file
+which will contain output created by a magic script (see the
+\fImagic script\fR
+parameter below).
-Default: \fBmagic output = <magic script name>.out\fR
+Warning: If two clients use the same \fImagic script
+\fR in the same directory the output file content
+is undefined.
+Default: \fBmagic output = <magic script name>.out
+\fR
Example: \fBmagic output = myfile.txt\fR
-
-
.TP
-magic script (S)
-This parameter specifies the name of a file which, if opened, will be executed by the server when the file is closed\&. This allows a UNIX script to be sent to the Samba host and executed on behalf of the connected user\&.
-
-
-Scripts executed in this way will be deleted upon completion assuming that the user has the appropriate level of privilege and the file permissions allow the deletion\&.
-
-
-If the script generates output, output will be sent to the file specified by the \fI magic output\fR parameter (see above)\&.
-
-
-Note that some shells are unable to interpret scripts containing CR/LF instead of CR as the end-of-line marker\&. Magic scripts must be executable \fBas is\fR on the host, which for some hosts and some shells will require filtering at the DOS end\&.
+\fBmagic script (S)\fR
+This parameter specifies the name of a file which,
+if opened, will be executed by the server when the file is closed.
+This allows a UNIX script to be sent to the Samba host and
+executed on behalf of the connected user.
+Scripts executed in this way will be deleted upon
+completion assuming that the user has the appropriate level
+of privilege and the file permissions allow the deletion.
-Magic scripts are \fBEXPERIMENTAL\fR and should \fBNOT\fR be relied upon\&.
+If the script generates output, output will be sent to
+the file specified by the \fI magic output\fR parameter (see above).
+Note that some shells are unable to interpret scripts
+containing CR/LF instead of CR as
+the end-of-line marker. Magic scripts must be executable
+\fBas is\fR on the host, which for some hosts and
+some shells will require filtering at the DOS end.
-Default: \fBNone\&. Magic scripts disabled\&.\fR
+Magic scripts are \fBEXPERIMENTAL\fR and
+should \fBNOT\fR be relied upon.
+Default: \fBNone. Magic scripts disabled.\fR
Example: \fBmagic script = user.csh\fR
-
-
.TP
-mangle case (S)
-See the section on NAME MANGLING
-
+\fBmangle case (S)\fR
+See the section on NAME MANGLING
Default: \fBmangle case = no\fR
-
-
.TP
-mangled map (S)
-This is for those who want to directly map UNIX file names which cannot be represented on Windows/DOS\&. The mangling of names is not always what is needed\&. In particular you may have documents with file extensions that differ between DOS and UNIX\&. For example, under UNIX it is common to use \fI\&.html\fR for HTML files, whereas under Windows/DOS \fI\&.htm\fR is more commonly used\&.
-
-
-So to map \fIhtml\fR to \fIhtm\fR you would use:
+\fBmangled map (S)\fR
+This is for those who want to directly map UNIX
+file names which cannot be represented on Windows/DOS. The mangling
+of names is not always what is needed. In particular you may have
+documents with file extensions that differ between DOS and UNIX.
+For example, under UNIX it is common to use \fI.html\fR
+for HTML files, whereas under Windows/DOS \fI.htm\fR
+is more commonly used.
+So to map \fIhtml\fR to \fIhtm\fR
+you would use:
\fBmangled map = (*.html *.htm)\fR
-
-One very useful case is to remove the annoying \fI;1 \fR off the ends of filenames on some CDROMs (only visible under some UNIXes)\&. To do this use a map of (*;1 *;)\&.
-
+One very useful case is to remove the annoying \fI;1
+\fR off the ends of filenames on some CDROMs (only visible
+under some UNIXes). To do this use a map of (*;1 *;).
Default: \fBno mangled map\fR
-
Example: \fBmangled map = (*;1 *;)\fR
-
-
.TP
-mangled names (S)
-This controls whether non-DOS names under UNIX should be mapped to DOS-compatible names ("mangled") and made visible, or whether non-DOS names should simply be ignored\&.
-
-
-See the section on NAME MANGLING for details on how to control the mangling process\&.
+\fBmangled names (S)\fR
+This controls whether non-DOS names under UNIX
+should be mapped to DOS-compatible names ("mangled") and made visible,
+or whether non-DOS names should simply be ignored.
+See the section on NAME MANGLING for details on how to control the mangling process.
If mangling is used then the mangling algorithm is as follows:
+.RS
+.TP 0.2i
+\(bu
+The first (up to) five alphanumeric characters
+before the rightmost dot of the filename are preserved, forced
+to upper case, and appear as the first (up to) five characters
+of the mangled name.
+.TP 0.2i
+\(bu
+A tilde "~" is appended to the first part of the mangled
+name, followed by a two-character unique sequence, based on the
+original root name (i.e., the original filename minus its final
+extension). The final extension is included in the hash calculation
+only if it contains any upper case characters or is longer than three
+characters.
+
+Note that the character to use may be specified using
+the \fImangling char\fR
+option, if you don't like '~'.
+.TP 0.2i
+\(bu
+The first three alphanumeric characters of the final
+extension are preserved, forced to upper case and appear as the
+extension of the mangled name. The final extension is defined as that
+part of the original filename after the rightmost dot. If there are no
+dots in the filename, the mangled name will have no extension (except
+in the case of "hidden files" - see below).
+.TP 0.2i
+\(bu
+Files whose UNIX name begins with a dot will be
+presented as DOS hidden files. The mangled name will be created as
+for other filenames, but with the leading dot removed and "___" as
+its extension regardless of actual original extension (that's three
+underscores).
+.RE
+The two-digit hash value consists of upper case
+alphanumeric characters.
-The first (up to) five alphanumeric characters before the rightmost dot of the filename are preserved, forced to upper case, and appear as the first (up to) five characters of the mangled name\&.
-
-A tilde "~" is appended to the first part of the mangled name, followed by a two-character unique sequence, based on the original root name (i\&.e\&., the original filename minus its final extension)\&. The final extension is included in the hash calculation only if it contains any upper case characters or is longer than three characters\&.
-
-
-Note that the character to use may be specified using the \fImangling char\fR option, if you don't like '~'\&.
-
-The first three alphanumeric characters of the final extension are preserved, forced to upper case and appear as the extension of the mangled name\&. The final extension is defined as that part of the original filename after the rightmost dot\&. If there are no dots in the filename, the mangled name will have no extension (except in the case of "hidden files" - see below)\&.
-
-Files whose UNIX name begins with a dot will be presented as DOS hidden files\&. The mangled name will be created as for other filenames, but with the leading dot removed and "___" as its extension regardless of actual original extension (that's three underscores)\&.
-
-The two-digit hash value consists of upper case alphanumeric characters\&.
-
-
-This algorithm can cause name collisions only if files in a directory share the same first five alphanumeric characters\&. The probability of such a clash is 1/1300\&.
-
-
-The name mangling (if enabled) allows a file to be copied between UNIX directories from Windows/DOS while retaining the long UNIX filename\&. UNIX files can be renamed to a new extension from Windows/DOS and will retain the same basename\&. Mangled names do not change between sessions\&.
+This algorithm can cause name collisions only if files
+in a directory share the same first five alphanumeric characters.
+The probability of such a clash is 1/1300.
+The name mangling (if enabled) allows a file to be
+copied between UNIX directories from Windows/DOS while retaining
+the long UNIX filename. UNIX files can be renamed to a new extension
+from Windows/DOS and will retain the same basename. Mangled names
+do not change between sessions.
Default: \fBmangled names = yes\fR
-
-
.TP
-mangling stack (G)
-This parameter controls the number of mangled names that should be cached in the Samba server \fBsmbd\fR(8)\&.
-
-
-This stack is a list of recently mangled base names (extensions are only maintained if they are longer than 3 characters or contains upper case characters)\&.
-
-
-The larger this value, the more likely it is that mangled names can be successfully converted to correct long UNIX names\&. However, large stack sizes will slow most directory accesses\&. Smaller stacks save memory in the server (each stack element costs 256 bytes)\&.
-
-
-It is not possible to absolutely guarantee correct long filenames, so be prepared for some surprises!
-
-
-Default: \fBmangled stack = 50\fR
-
-
-Example: \fBmangled stack = 100\fR
+\fBmangling method (G)\fR
+controls the algorithm used for the generating
+the mangled names. Can take two different values, "hash" and
+"hash2". "hash" is the default and is the algorithm that has been
+used in Samba for many years. "hash2" is a newer and considered
+a better algorithm (generates less collisions) in the names.
+However, many Win32 applications store the mangled names and so
+changing to the new algorithm must not be done
+lightly as these applications may break unless reinstalled.
+Default: \fBmangling method = hash2\fR
+Example: \fBmangling method = hash\fR
.TP
-mangling prefix (G)
-controls the number of prefix characters from the original name used when generating the mangled names\&. A larger value will give a weaker hash and therefore more name collisions\&. The minimum value is 1 and the maximum value is 6\&.
-
+\fBmangle prefix (G)\fR
+controls the number of prefix
+characters from the original name used when generating
+the mangled names. A larger value will give a weaker
+hash and therefore more name collisions. The minimum
+value is 1 and the maximum value is 6.
Default: \fBmangle prefix = 1\fR
-
Example: \fBmangle prefix = 4\fR
-
-
.TP
-mangling char (S)
-This controls what character is used as the \fBmagic\fR character in name mangling\&. The default is a '~' but this may interfere with some software\&. Use this option to set it to whatever you prefer\&.
-
+\fBmangled stack (G)\fR
+This parameter controls the number of mangled names
+that should be cached in the Samba server smbd(8)
-Default: \fBmangling char = ~\fR
+This stack is a list of recently mangled base names
+(extensions are only maintained if they are longer than 3 characters
+or contains upper case characters).
+The larger this value, the more likely it is that mangled
+names can be successfully converted to correct long UNIX names.
+However, large stack sizes will slow most directory accesses. Smaller
+stacks save memory in the server (each stack element costs 256 bytes).
-Example: \fBmangling char = ^\fR
+It is not possible to absolutely guarantee correct long
+filenames, so be prepared for some surprises!
+Default: \fBmangled stack = 50\fR
+Example: \fBmangled stack = 100\fR
.TP
-mangling method (G)
-controls the algorithm used for the generating the mangled names\&. Can take two different values, "hash" and "hash2"\&. "hash" is the default and is the algorithm that has been used in Samba for many years\&. "hash2" is a newer and considered a better algorithm (generates less collisions) in the names\&. However, many Win32 applications store the mangled names and so changing to the new algorithm must not be done lightly as these applications may break unless reinstalled\&.
-
-
-Default: \fBmangling method = hash2\fR
-
-
-Example: \fBmangling method = hash\fR
+\fBmangling char (S)\fR
+This controls what character is used as
+the \fBmagic\fR character in name mangling. The default is a '~'
+but this may interfere with some software. Use this option to set
+it to whatever you prefer.
+Default: \fBmangling char = ~\fR
+Example: \fBmangling char = ^\fR
.TP
-map archive (S)
-This controls whether the DOS archive attribute should be mapped to the UNIX owner execute bit\&. The DOS archive bit is set when a file has been modified since its last backup\&. One motivation for this option it to keep Samba/your PC from making any file it touches from becoming executable under UNIX\&. This can be quite annoying for shared source code, documents, etc\&.\&.\&.
-
-
-Note that this requires the \fIcreate mask\fR parameter to be set such that owner execute bit is not masked out (i\&.e\&. it must include 100)\&. See the parameter \fIcreate mask\fR for details\&.
+\fBmap archive (S)\fR
+This controls whether the DOS archive attribute
+should be mapped to the UNIX owner execute bit. The DOS archive bit
+is set when a file has been modified since its last backup. One
+motivation for this option it to keep Samba/your PC from making
+any file it touches from becoming executable under UNIX. This can
+be quite annoying for shared source code, documents, etc...
+Note that this requires the \fIcreate mask\fR
+parameter to be set such that owner execute bit is not masked out
+(i.e. it must include 100). See the parameter \fIcreate mask\fR for details.
Default: \fBmap archive = yes\fR
-
-
.TP
-map hidden (S)
-This controls whether DOS style hidden files should be mapped to the UNIX world execute bit\&.
-
-
-Note that this requires the \fIcreate mask\fR to be set such that the world execute bit is not masked out (i\&.e\&. it must include 001)\&. See the parameter \fIcreate mask\fR for details\&.
+\fBmap hidden (S)\fR
+This controls whether DOS style hidden files
+should be mapped to the UNIX world execute bit.
+Note that this requires the \fIcreate mask\fR
+to be set such that the world execute bit is not masked out (i.e.
+it must include 001). See the parameter \fIcreate mask\fR for details.
Default: \fBmap hidden = no\fR
-
-
.TP
-map system (S)
-This controls whether DOS style system files should be mapped to the UNIX group execute bit\&.
-
-
-Note that this requires the \fIcreate mask\fR to be set such that the group execute bit is not masked out (i\&.e\&. it must include 010)\&. See the parameter \fIcreate mask\fR for details\&.
+\fBmap system (S)\fR
+This controls whether DOS style system files
+should be mapped to the UNIX group execute bit.
+Note that this requires the \fIcreate mask\fR
+to be set such that the group execute bit is not masked out (i.e.
+it must include 010). See the parameter \fIcreate mask\fR for details.
Default: \fBmap system = no\fR
-
-
.TP
-map to guest (G)
-This parameter is only useful in security modes other than \fIsecurity = share\fR - i\&.e\&. \fBuser\fR, \fBserver\fR, and \fBdomain\fR\&.
-
-
-This parameter can take three different values, which tell \fBsmbd\fR(8) what to do with user login requests that don't match a valid UNIX user in some way\&.
+\fBmap to guest (G)\fR
+This parameter is only useful in security modes other than \fIsecurity = share\fR
+- i.e. user, server,
+and domain.
+This parameter can take three different values, which tell
+smbd(8) what to do with user
+login requests that don't match a valid UNIX user in some way.
The three settings are :
+.RS
+.TP 0.2i
+\(bu
+Never - Means user login
+requests with an invalid password are rejected. This is the
+default.
+.TP 0.2i
+\(bu
+Bad User - Means user
+logins with an invalid password are rejected, unless the username
+does not exist, in which case it is treated as a guest login and
+mapped into the \fI guest account\fR.
+.TP 0.2i
+\(bu
+Bad Password - Means user logins
+with an invalid password are treated as a guest login and mapped
+into the guest account. Note that
+this can cause problems as it means that any user incorrectly typing
+their password will be silently logged on as "guest" - and
+will not know the reason they cannot access files they think
+they should - there will have been no message given to them
+that they got their password wrong. Helpdesk services will
+\fBhate\fR you if you set the \fImap to
+guest\fR parameter this way :-).
+.RE
+Note that this parameter is needed to set up "Guest"
+share services when using \fIsecurity\fR modes other than
+share. This is because in these modes the name of the resource being
+requested is \fBnot\fR sent to the server until after
+the server has successfully authenticated the client so the server
+cannot make authentication decisions at the correct time (connection
+to the share) for "Guest" shares.
-\fBNever\fR - Means user login requests with an invalid password are rejected\&. This is the default\&.
-
-\fBBad User\fR - Means user logins with an invalid password are rejected, unless the username does not exist, in which case it is treated as a guest login and mapped into the \fI guest account\fR\&.
-
-\fBBad Password\fR - Means user logins with an invalid password are treated as a guest login and mapped into the guest account\&. Note that this can cause problems as it means that any user incorrectly typing their password will be silently logged on as "guest" - and will not know the reason they cannot access files they think they should - there will have been no message given to them that they got their password wrong\&. Helpdesk services will \fBhate\fR you if you set the \fImap to guest\fR parameter this way :-)\&.
-
-Note that this parameter is needed to set up "Guest" share services when using \fIsecurity\fR modes other than share\&. This is because in these modes the name of the resource being requested is \fBnot\fR sent to the server until after the server has successfully authenticated the client so the server cannot make authentication decisions at the correct time (connection to the share) for "Guest" shares\&.
-
-
-For people familiar with the older Samba releases, this parameter maps to the old compile-time setting of the \fB GUEST_SESSSETUP\fR value in local\&.h\&.
-
+For people familiar with the older Samba releases, this
+parameter maps to the old compile-time setting of the GUEST_SESSSETUP value in local.h.
Default: \fBmap to guest = Never\fR
-
Example: \fBmap to guest = Bad User\fR
-
-
.TP
-max connections (S)
-This option allows the number of simultaneous connections to a service to be limited\&. If \fImax connections\fR is greater than 0 then connections will be refused if this number of connections to the service are already open\&. A value of zero mean an unlimited number of connections may be made\&.
-
-
-Record lock files are used to implement this feature\&. The lock files will be stored in the directory specified by the \fIlock directory\fR option\&.
+\fBmax connections (S)\fR
+This option allows the number of simultaneous
+connections to a service to be limited. If \fImax connections
+\fR is greater than 0 then connections will be refused if
+this number of connections to the service are already open. A value
+of zero mean an unlimited number of connections may be made.
+Record lock files are used to implement this feature. The
+lock files will be stored in the directory specified by the \fIlock directory\fR
+option.
Default: \fBmax connections = 0\fR
-
Example: \fBmax connections = 10\fR
-
-
.TP
-max disk size (G)
-This option allows you to put an upper limit on the apparent size of disks\&. If you set this option to 100 then all shares will appear to be not larger than 100 MB in size\&.
-
-
-Note that this option does not limit the amount of data you can put on the disk\&. In the above case you could still store much more than 100 MB on the disk, but if a client ever asks for the amount of free disk space or the total disk size then the result will be bounded by the amount specified in \fImax disk size\fR\&.
+\fBmax disk size (G)\fR
+This option allows you to put an upper limit
+on the apparent size of disks. If you set this option to 100
+then all shares will appear to be not larger than 100 MB in
+size.
+Note that this option does not limit the amount of
+data you can put on the disk. In the above case you could still
+store much more than 100 MB on the disk, but if a client ever asks
+for the amount of free disk space or the total disk size then the
+result will be bounded by the amount specified in \fImax
+disk size\fR.
-This option is primarily useful to work around bugs in some pieces of software that can't handle very large disks, particularly disks over 1GB in size\&.
-
-
-A \fImax disk size\fR of 0 means no limit\&.
+This option is primarily useful to work around bugs
+in some pieces of software that can't handle very large disks,
+particularly disks over 1GB in size.
+A \fImax disk size\fR of 0 means no limit.
Default: \fBmax disk size = 0\fR
-
Example: \fBmax disk size = 1000\fR
-
-
.TP
-max log size (G)
-This option (an integer in kilobytes) specifies the max size the log file should grow to\&. Samba periodically checks the size and if it is exceeded it will rename the file, adding a \fI\&.old\fR extension\&.
-
-
-A size of 0 means no limit\&.
+\fBmax log size (G)\fR
+This option (an integer in kilobytes) specifies
+the max size the log file should grow to. Samba periodically checks
+the size and if it is exceeded it will rename the file, adding
+a \fI.old\fR extension.
+A size of 0 means no limit.
Default: \fBmax log size = 5000\fR
-
Example: \fBmax log size = 1000\fR
-
-
.TP
-max mux (G)
-This option controls the maximum number of outstanding simultaneous SMB operations that Samba tells the client it will allow\&. You should never need to set this parameter\&.
-
+\fBmax mux (G)\fR
+This option controls the maximum number of
+outstanding simultaneous SMB operations that Samba tells the client
+it will allow. You should never need to set this parameter.
Default: \fBmax mux = 50\fR
-
-
.TP
-max open files (G)
-This parameter limits the maximum number of open files that one \fBsmbd\fR(8) file serving process may have open for a client at any one time\&. The default for this parameter is set very high (10,000) as Samba uses only one bit per unopened file\&.
-
-
-The limit of the number of open files is usually set by the UNIX per-process file descriptor limit rather than this parameter so you should never need to touch this parameter\&.
+\fBmax open files (G)\fR
+This parameter limits the maximum number of
+open files that one smbd(8) file
+serving process may have open for a client at any one time. The
+default for this parameter is set very high (10,000) as Samba uses
+only one bit per unopened file.
+The limit of the number of open files is usually set
+by the UNIX per-process file descriptor limit rather than
+this parameter so you should never need to touch this parameter.
Default: \fBmax open files = 10000\fR
-
-
.TP
-max print jobs (S)
-This parameter limits the maximum number of jobs allowable in a Samba printer queue at any given moment\&. If this number is exceeded, \fBsmbd\fR(8) will remote "Out of Space" to the client\&. See all \fItotal print jobs\fR\&.
-
+\fBmax print jobs (S)\fR
+This parameter limits the maximum number of
+jobs allowable in a Samba printer queue at any given moment.
+If this number is exceeded, \fB smbd(8)\fR will remote "Out of Space" to the client.
+See all \fItotal
+print jobs\fR.
Default: \fBmax print jobs = 1000\fR
-
Example: \fBmax print jobs = 5000\fR
-
-
.TP
-max protocol (G)
-The value of the parameter (a string) is the highest protocol level that will be supported by the server\&.
-
+\fBmax protocol (G)\fR
+The value of the parameter (a string) is the highest
+protocol level that will be supported by the server.
Possible values are :
+.RS
+.TP 0.2i
+\(bu
+CORE: Earliest version. No
+concept of user names.
+.TP 0.2i
+\(bu
+COREPLUS: Slight improvements on
+CORE for efficiency.
+.TP 0.2i
+\(bu
+LANMAN1: First \fB modern\fR version of the protocol. Long filename
+support.
+.TP 0.2i
+\(bu
+LANMAN2: Updates to Lanman1 protocol.
+.TP 0.2i
+\(bu
+NT1: Current up to date version of
+the protocol. Used by Windows NT. Known as CIFS.
+.RE
+Normally this option should not be set as the automatic
+negotiation phase in the SMB protocol takes care of choosing
+the appropriate protocol.
-\fBCORE\fR: Earliest version\&. No concept of user names\&.
-
-\fBCOREPLUS\fR: Slight improvements on CORE for efficiency\&.
-
-\fBLANMAN1\fR: First \fB modern\fR version of the protocol\&. Long filename support\&.
-
-\fBLANMAN2\fR: Updates to Lanman1 protocol\&.
-
-\fBNT1\fR: Current up to date version of the protocol\&. Used by Windows NT\&. Known as CIFS\&.
-
-Normally this option should not be set as the automatic negotiation phase in the SMB protocol takes care of choosing the appropriate protocol\&.
-
-
-See also \fImin protocol\fR
-
+See also \fImin
+protocol\fR
Default: \fBmax protocol = NT1\fR
-
Example: \fBmax protocol = LANMAN1\fR
-
-
.TP
-max smbd processes (G)
-This parameter limits the maximum number of \fBsmbd\fR(8) processes concurrently running on a system and is intended as a stopgap to prevent degrading service to clients in the event that the server has insufficient resources to handle more than this number of connections\&. Remember that under normal operating conditions, each user will have an \fBsmbd\fR(8) associated with him or her to handle connections to all shares from a given host\&.
-
-
-Default: \fBmax smbd processes = 0\fR ## no limit
+\fBmax smbd processes (G)\fR
+This parameter limits the maximum number of
+\fBsmbd(8)\fR
+processes concurrently running on a system and is intended
+as a stopgap to prevent degrading service to clients in the event
+that the server has insufficient resources to handle more than this
+number of connections. Remember that under normal operating
+conditions, each user will have an smbd associated with him or her
+to handle connections to all shares from a given host.
+Default: \fBmax smbd processes = 0\fR ## no limit
Example: \fBmax smbd processes = 1000\fR
-
-
.TP
-max ttl (G)
-This option tells \fBnmbd\fR(8) what the default 'time to live' of NetBIOS names should be (in seconds) when \fBnmbd\fR is requesting a name using either a broadcast packet or from a WINS server\&. You should never need to change this parameter\&. The default is 3 days\&.
-
+\fBmax ttl (G)\fR
+This option tells nmbd(8)
+what the default 'time to live' of NetBIOS names should be (in seconds)
+when \fBnmbd\fR is requesting a name using either a
+broadcast packet or from a WINS server. You should never need to
+change this parameter. The default is 3 days.
Default: \fBmax ttl = 259200\fR
-
-
.TP
-max wins ttl (G)
-This option tells \fBsmbd\fR(8) when acting as a WINS server ( \fIwins support = yes\fR) what the maximum 'time to live' of NetBIOS names that \fBnmbd\fR will grant will be (in seconds)\&. You should never need to change this parameter\&. The default is 6 days (518400 seconds)\&.
-
-
-See also the \fImin wins ttl\fR parameter\&.
+\fBmax wins ttl (G)\fR
+This option tells nmbd(8)
+ when acting as a WINS server ( \fIwins support = yes\fR) what the maximum
+\&'time to live' of NetBIOS names that \fBnmbd\fR
+will grant will be (in seconds). You should never need to change this
+parameter. The default is 6 days (518400 seconds).
+See also the \fImin
+wins ttl\fR parameter.
Default: \fBmax wins ttl = 518400\fR
-
-
.TP
-max xmit (G)
-This option controls the maximum packet size that will be negotiated by Samba\&. The default is 65535, which is the maximum\&. In some cases you may find you get better performance with a smaller value\&. A value below 2048 is likely to cause problems\&.
-
+\fBmax xmit (G)\fR
+This option controls the maximum packet size
+that will be negotiated by Samba. The default is 65535, which
+is the maximum. In some cases you may find you get better performance
+with a smaller value. A value below 2048 is likely to cause problems.
Default: \fBmax xmit = 65535\fR
-
Example: \fBmax xmit = 8192\fR
-
-
.TP
-message command (G)
-This specifies what command to run when the server receives a WinPopup style message\&.
-
-
-This would normally be a command that would deliver the message somehow\&. How this is to be done is up to your imagination\&.
+\fBmessage command (G)\fR
+This specifies what command to run when the
+server receives a WinPopup style message.
+This would normally be a command that would
+deliver the message somehow. How this is to be done is
+up to your imagination.
An example is:
-
\fBmessage command = csh -c 'xedit %s;rm %s' &\fR
+This delivers the message using \fBxedit\fR, then
+removes it afterwards. \fBNOTE THAT IT IS VERY IMPORTANT
+THAT THIS COMMAND RETURN IMMEDIATELY\fR. That's why I
+have the '&' on the end. If it doesn't return immediately then
+your PCs may freeze when sending messages (they should recover
+after 30 seconds, hopefully).
-This delivers the message using \fBxedit\fR, then removes it afterwards\&. \fBNOTE THAT IT IS VERY IMPORTANT THAT THIS COMMAND RETURN IMMEDIATELY\fR\&. That's why I have the '&' on the end\&. If it doesn't return immediately then your PCs may freeze when sending messages (they should recover after 30 seconds, hopefully)\&.
-
-
-All messages are delivered as the global guest user\&. The command takes the standard substitutions, although \fI %u\fR won't work (\fI%U\fR may be better in this case)\&.
-
-
-Apart from the standard substitutions, some additional ones apply\&. In particular:
-
-
-\fI%s\fR = the filename containing the message\&.
-
-\fI%t\fR = the destination that the message was sent to (probably the server name)\&.
-
-\fI%f\fR = who the message is from\&.
+All messages are delivered as the global guest user.
+The command takes the standard substitutions, although \fI %u\fR won't work (\fI%U\fR may be better
+in this case).
-You could make this command send mail, or whatever else takes your fancy\&. Please let us know of any really interesting ideas you have\&.
+Apart from the standard substitutions, some additional
+ones apply. In particular:
+.RS
+.TP 0.2i
+\(bu
+\fI%s\fR = the filename containing
+the message.
+.TP 0.2i
+\(bu
+\fI%t\fR = the destination that
+the message was sent to (probably the server name).
+.TP 0.2i
+\(bu
+\fI%f\fR = who the message
+is from.
+.RE
+You could make this command send mail, or whatever else
+takes your fancy. Please let us know of any really interesting
+ideas you have.
Here's a way of sending the messages as mail to root:
+\fBmessage command = /bin/mail -s 'message from %f on
+%m' root < %s; rm %s\fR
-\fBmessage command = /bin/mail -s 'message from %f on %m' root < %s; rm %s\fR
-
-
-If you don't have a message command then the message won't be delivered and Samba will tell the sender there was an error\&. Unfortunately WfWg totally ignores the error code and carries on regardless, saying that the message was delivered\&.
-
+If you don't have a message command then the message
+won't be delivered and Samba will tell the sender there was
+an error. Unfortunately WfWg totally ignores the error code
+and carries on regardless, saying that the message was delivered.
If you want to silently delete it then try:
-
\fBmessage command = rm %s\fR
-
Default: \fBno message command\fR
-
-Example: \fBmessage command = csh -c 'xedit %s; rm %s' &\fR
-
-
+Example: \fBmessage command = csh -c 'xedit %s;
+rm %s' &\fR
.TP
-min passwd length (G)
-Synonym for \fImin password length\fR\&.
-
-
+\fBmin passwd length (G)\fR
+Synonym for \fImin password length\fR.
.TP
-min password length (G)
-This option sets the minimum length in characters of a plaintext password that \fBsmbd\fR will accept when performing UNIX password changing\&.
-
-
-See also \fIunix password sync\fR, \fIpasswd program\fR and \fIpasswd chat debug\fR\&.
+\fBmin password length (G)\fR
+This option sets the minimum length in characters
+of a plaintext password that \fBsmbd\fR will accept when performing
+UNIX password changing.
+See also \fIunix
+password sync\fR, \fIpasswd program\fR and \fIpasswd chat debug\fR
+\&.
Default: \fBmin password length = 5\fR
-
-
.TP
-min print space (S)
-This sets the minimum amount of free disk space that must be available before a user will be able to spool a print job\&. It is specified in kilobytes\&. The default is 0, which means a user can always spool a print job\&.
-
-
-See also the \fIprinting \fR parameter\&.
+\fBmin print space (S)\fR
+This sets the minimum amount of free disk
+space that must be available before a user will be able to spool
+a print job. It is specified in kilobytes. The default is 0, which
+means a user can always spool a print job.
+See also the \fIprinting
+\fR parameter.
Default: \fBmin print space = 0\fR
-
Example: \fBmin print space = 2000\fR
-
-
.TP
-min protocol (G)
-The value of the parameter (a string) is the lowest SMB protocol dialect than Samba will support\&. Please refer to the \fImax protocol\fR parameter for a list of valid protocol names and a brief description of each\&. You may also wish to refer to the C source code in \fIsource/smbd/negprot\&.c\fR for a listing of known protocol dialects supported by clients\&.
-
-
-If you are viewing this parameter as a security measure, you should also refer to the \fIlanman auth\fR parameter\&. Otherwise, you should never need to change this parameter\&.
+\fBmin protocol (G)\fR
+The value of the parameter (a string) is the
+lowest SMB protocol dialect than Samba will support. Please refer
+to the \fImax protocol\fR
+parameter for a list of valid protocol names and a brief description
+of each. You may also wish to refer to the C source code in
+\fIsource/smbd/negprot.c\fR for a listing of known protocol
+dialects supported by clients.
+If you are viewing this parameter as a security measure, you should
+also refer to the \fIlanman
+auth\fR parameter. Otherwise, you should never need
+to change this parameter.
Default : \fBmin protocol = CORE\fR
-
-Example : \fBmin protocol = NT1\fR # disable DOS clients
-
-
+Example : \fBmin protocol = NT1\fR # disable DOS
+clients
.TP
-min wins ttl (G)
-This option tells \fBnmbd\fR(8) when acting as a WINS server (\fI wins support = yes\fR) what the minimum 'time to live' of NetBIOS names that \fBnmbd\fR will grant will be (in seconds)\&. You should never need to change this parameter\&. The default is 6 hours (21600 seconds)\&.
-
+\fBmin wins ttl (G)\fR
+This option tells nmbd(8)
+when acting as a WINS server (\fI wins support = yes\fR) what the minimum 'time to live'
+of NetBIOS names that \fBnmbd\fR will grant will be (in
+seconds). You should never need to change this parameter. The default
+is 6 hours (21600 seconds).
Default: \fBmin wins ttl = 21600\fR
-
-
.TP
-msdfs proxy (S)
-This parameter indicates that the share is a stand-in for another CIFS share whose location is specified by the value of the parameter\&. When clients attempt to connect to this share, they are redirected to the proxied share using the SMB-Dfs protocol\&.
-
-
-Only Dfs roots can act as proxy shares\&. Take a look at the \fImsdfs root\fR and \fIhost msdfs\fR options to find out how to set up a Dfs root share\&.
-
-
-Example: \fBmsdfs proxy = \\\\otherserver\\someshare\fR
+\fBmsdfs proxy (S)\fR
+This parameter indicates that the share is a
+stand-in for another CIFS share whose location is specified by
+the value of the parameter. When clients attempt to connect to
+this share, they are redirected to the proxied share using
+the SMB-Dfs protocol.
+Only Dfs roots can act as proxy shares. Take a look at the
+\fImsdfs root\fR
+and
+\fIhost msdfs\fR
+options to find out how to set up a Dfs root share.
+Example: \fBmsdfs proxy = \\otherserver\\someshare\fR
.TP
-msdfs root (S)
-This boolean parameter is only available if Samba is configured and compiled with the \fB --with-msdfs\fR option\&. If set to \fByes\fR, Samba treats the share as a Dfs root and allows clients to browse the distributed file system tree rooted at the share directory\&. Dfs links are specified in the share directory by symbolic links of the form \fImsdfs:serverA\\\\shareA,serverB\\\\shareB\fR and so on\&. For more information on setting up a Dfs tree on Samba, refer to "Hosting a Microsoft Distributed File System tree on Samba" document\&.
-
+\fBmsdfs root (S)\fR
+This boolean parameter is only available if
+Samba is configured and compiled with the \fB --with-msdfs\fR option. If set to yes,
+Samba treats the share as a Dfs root and allows clients to browse
+the distributed file system tree rooted at the share directory.
+Dfs links are specified in the share directory by symbolic
+links of the form \fImsdfs:serverA\\shareA,serverB\\shareB\fR
+and so on. For more information on setting up a Dfs tree
+on Samba, refer to msdfs_setup.html
-See also \fIhost msdfs\fR
+See also \fIhost msdfs
+\fR
Default: \fBmsdfs root = no\fR
-
-
.TP
-name cache timeout (G)
-Specifies the number of seconds it takes before entries in samba's hostname resolve cache time out\&. If the timeout is set to 0\&. the caching is disabled\&.
-
+\fBname cache timeout (G)\fR
+Specifies the number of seconds it takes before
+entries in samba's hostname resolve cache time out. If
+the timeout is set to 0. the caching is disabled.
Default: \fBname cache timeout = 660\fR
-
Example: \fBname cache timeout = 0\fR
-
-
.TP
-name resolve order (G)
-This option is used by the programs in the Samba suite to determine what naming services to use and in what order to resolve host names to IP addresses\&. The option takes a space separated string of name resolution options\&.
-
-
-The options are: "lmhosts", "host", "wins" and "bcast"\&. They cause names to be resolved as follows:
-
-
-\fBlmhosts\fR : Lookup an IP address in the Samba lmhosts file\&. If the line in lmhosts has no name type attached to the NetBIOS name (see the lmhosts(5) for details) then any name type matches for lookup\&.
-
-\fBhost\fR : Do a standard host name to IP address resolution, using the system \fI/etc/hosts \fR, NIS, or DNS lookups\&. This method of name resolution is operating system depended for instance on IRIX or Solaris this may be controlled by the \fI/etc/nsswitch\&.conf\fR file\&. Note that this method is only used if the NetBIOS name type being queried is the 0x20 (server) name type, otherwise it is ignored\&.
-
-\fBwins\fR : Query a name with the IP address listed in the \fI wins server\fR parameter\&. If no WINS server has been specified this method will be ignored\&.
-
-\fBbcast\fR : Do a broadcast on each of the known local interfaces listed in the \fIinterfaces\fR parameter\&. This is the least reliable of the name resolution methods as it depends on the target host being on a locally connected subnet\&.
-
-Default: \fBname resolve order = lmhosts host wins bcast\fR
-
-
-Example: \fBname resolve order = lmhosts bcast host\fR
+\fBname resolve order (G)\fR
+This option is used by the programs in the Samba
+suite to determine what naming services to use and in what order
+to resolve host names to IP addresses. The option takes a space
+separated string of name resolution options.
+The options are :"lmhosts", "host", "wins" and "bcast". They
+cause names to be resolved as follows :
+.RS
+.TP 0.2i
+\(bu
+lmhosts : Lookup an IP
+address in the Samba lmhosts file. If the line in lmhosts has
+no name type attached to the NetBIOS name (see the lmhosts(5) for details) then
+any name type matches for lookup.
+.TP 0.2i
+\(bu
+host : Do a standard host
+name to IP address resolution, using the system \fI/etc/hosts
+\fR, NIS, or DNS lookups. This method of name resolution
+is operating system depended for instance on IRIX or Solaris this
+may be controlled by the \fI/etc/nsswitch.conf\fR
+file. Note that this method is only used if the NetBIOS name
+type being queried is the 0x20 (server) name type, otherwise
+it is ignored.
+.TP 0.2i
+\(bu
+wins : Query a name with
+the IP address listed in the \fI wins server\fR parameter. If no WINS server has
+been specified this method will be ignored.
+.TP 0.2i
+\(bu
+bcast : Do a broadcast on
+each of the known local interfaces listed in the \fIinterfaces\fR
+parameter. This is the least reliable of the name resolution
+methods as it depends on the target host being on a locally
+connected subnet.
+.RE
-This will cause the local lmhosts file to be examined first, followed by a broadcast attempt, followed by a normal system hostname lookup\&.
+Default: \fBname resolve order = lmhosts host wins bcast
+\fR
+Example: \fBname resolve order = lmhosts bcast host
+\fR
+This will cause the local lmhosts file to be examined
+first, followed by a broadcast attempt, followed by a normal
+system hostname lookup.
.TP
-netbios aliases (G)
-This is a list of NetBIOS names that nmbd(8) will advertise as additional names by which the Samba server is known\&. This allows one machine to appear in browse lists under multiple names\&. If a machine is acting as a browse server or logon server none of these names will be advertised as either browse server or logon servers, only the primary name of the machine will be advertised with these capabilities\&.
-
-
-See also \fInetbios name\fR\&.
+\fBnetbios aliases (G)\fR
+This is a list of NetBIOS names that nmbd(8) will advertise as additional
+names by which the Samba server is known. This allows one machine
+to appear in browse lists under multiple names. If a machine is
+acting as a browse server or logon server none
+of these names will be advertised as either browse server or logon
+servers, only the primary name of the machine will be advertised
+with these capabilities.
+See also \fInetbios
+name\fR.
Default: \fBempty string (no additional names)\fR
-
Example: \fBnetbios aliases = TEST TEST1 TEST2\fR
-
-
.TP
-netbios name (G)
-This sets the NetBIOS name by which a Samba server is known\&. By default it is the same as the first component of the host's DNS name\&. If a machine is a browse server or logon server this name (or the first component of the hosts DNS name) will be the name that these services are advertised under\&.
-
-
-See also \fInetbios aliases\fR\&.
+\fBnetbios name (G)\fR
+This sets the NetBIOS name by which a Samba
+server is known. By default it is the same as the first component
+of the host's DNS name. If a machine is a browse server or
+logon server this name (or the first component
+of the hosts DNS name) will be the name that these services are
+advertised under.
+See also \fInetbios
+aliases\fR.
Default: \fBmachine DNS name\fR
-
Example: \fBnetbios name = MYNAME\fR
-
-
.TP
-netbios scope (G)
-This sets the NetBIOS scope that Samba will operate under\&. This should not be set unless every machine on your LAN also sets this value\&.
-
-
-.TP
-nis homedir (G)
-Get the home share server from a NIS map\&. For UNIX systems that use an automounter, the user's home directory will often be mounted on a workstation on demand from a remote server\&.
-
-
-When the Samba logon server is not the actual home directory server, but is mounting the home directories via NFS then two network hops would be required to access the users home directory if the logon server told the client to use itself as the SMB server for home directories (one over SMB and one over NFS)\&. This can be very slow\&.
-
-
-This option allows Samba to return the home share as being on a different server to the logon server and as long as a Samba daemon is running on the home directory server, it will be mounted on the Samba client directly from the directory server\&. When Samba is returning the home share to the client, it will consult the NIS map specified in \fIhomedir map\fR and return the server listed there\&.
-
-
-Note that for this option to work there must be a working NIS system and the Samba server with this option must also be a logon server\&.
-
+\fBnetbios scope (G)\fR
+This sets the NetBIOS scope that Samba will
+operate under. This should not be set unless every machine
+on your LAN also sets this value.
+.TP
+\fBnis homedir (G)\fR
+Get the home share server from a NIS map. For
+UNIX systems that use an automounter, the user's home directory
+will often be mounted on a workstation on demand from a remote
+server.
+
+When the Samba logon server is not the actual home directory
+server, but is mounting the home directories via NFS then two
+network hops would be required to access the users home directory
+if the logon server told the client to use itself as the SMB server
+for home directories (one over SMB and one over NFS). This can
+be very slow.
+
+This option allows Samba to return the home share as
+being on a different server to the logon server and as
+long as a Samba daemon is running on the home directory server,
+it will be mounted on the Samba client directly from the directory
+server. When Samba is returning the home share to the client, it
+will consult the NIS map specified in \fIhomedir map\fR and return the server
+listed there.
+
+Note that for this option to work there must be a working
+NIS system and the Samba server with this option must also
+be a logon server.
Default: \fBnis homedir = no\fR
-
-
.TP
-non unix account range (G)
-The non unix account range parameter specifies the range of 'user ids' that are allocated by the various 'non unix account' passdb backends\&. These backends allow the storage of passwords for users who don't exist in /etc/passwd\&. This is most often used for machine account creation\&. This range of ids should have no existing local or NIS users within it as strange conflicts can occur otherwise\&.
+\fBnon unix account range (G)\fR
+The non unix account range parameter specifies
+the range of 'user ids' that are allocated by the various 'non unix
+account' passdb backends. These backends allow
+the storage of passwords for users who don't exist in /etc/passwd.
+This is most often used for machine account creation.
+This range of ids should have no existing local or NIS users within
+it as strange conflicts can occur otherwise.
+NOTE: These userids never appear on the system and Samba will never
+\&'become' these users. They are used only to ensure that the algorithmic
+RID mapping does not conflict with normal users.
-These userids never appear on the system and Samba will never 'become' these users\&. They are used only to ensure that the algorithmic RID mapping does not conflict with normal users\&.
-
-Default: \fBnon unix account range = <empty string>\fR
-
+Default: \fBnon unix account range = <empty string>
+\fR
Example: \fBnon unix account range = 10000-20000\fR
-
-
.TP
-nt acl support (S)
-This boolean parameter controls whether \fBsmbd\fR(8) will attempt to map UNIX permissions into Windows NT access control lists\&. This parameter was formally a global parameter in releases prior to 2\&.2\&.2\&.
-
+\fBnt acl support (S)\fR
+This boolean parameter controls whether
+smbd(8) will attempt to map
+UNIX permissions into Windows NT access control lists.
+This parameter was formally a global parameter in releases
+prior to 2.2.2.
Default: \fBnt acl support = yes\fR
-
-
-.TP
-ntlm auth (G)
-This parameter determines whether or not \fBsmbd\fR(8) will attempt to authenticate users using the NTLM password hash\&. If disabled, only the lanman password hashes will be used\&.
-
-
-Please note that at least this option or \fBlanman auth\fR should be enabled in order to be able to log in\&.
-
-
-Default : \fBntlm auth = yes\fR
-
-
.TP
-nt pipe support (G)
-This boolean parameter controls whether \fBsmbd\fR(8) will allow Windows NT clients to connect to the NT SMB specific \fBIPC$\fR pipes\&. This is a developer debugging option and can be left alone\&.
-
+\fBnt pipe support (G)\fR
+This boolean parameter controls whether
+smbd(8) will allow Windows NT
+clients to connect to the NT SMB specific IPC$
+pipes. This is a developer debugging option and can be left
+alone.
Default: \fBnt pipe support = yes\fR
-
-
.TP
-nt status support (G)
-This boolean parameter controls whether \fBsmbd\fR(8) will negotiate NT specific status support with Windows NT/2k/XP clients\&. This is a developer debugging option and should be left alone\&. If this option is set to \fBno\fR then Samba offers exactly the same DOS error codes that versions prior to Samba 2\&.2\&.3 reported\&.
-
-
-You should not need to ever disable this parameter\&.
+\fBnt status support (G)\fR
+This boolean parameter controls whether smbd(8) will negotiate NT specific status
+support with Windows NT/2k/XP clients. This is a developer
+debugging option and should be left alone.
+If this option is set to no then Samba offers
+exactly the same DOS error codes that versions prior to Samba 2.2.3
+reported.
+You should not need to ever disable this parameter.
Default: \fBnt status support = yes\fR
-
-
.TP
-null passwords (G)
-Allow or disallow client access to accounts that have null passwords\&.
-
-
-See also \fBsmbpasswd\fR(5)\&.
+\fBnull passwords (G)\fR
+Allow or disallow client access to accounts
+that have null passwords.
+See also smbpasswd (5)
Default: \fBnull passwords = no\fR
-
-
.TP
-obey pam restrictions (G)
-When Samba 3\&.0 is configured to enable PAM support (i\&.e\&. --with-pam), this parameter will control whether or not Samba should obey PAM's account and session management directives\&. The default behavior is to use PAM for clear text authentication only and to ignore any account or session management\&. Note that Samba always ignores PAM for authentication in the case of \fIencrypt passwords = yes\fR\&. The reason is that PAM modules cannot support the challenge/response authentication mechanism needed in the presence of SMB password encryption\&.
-
+\fBobey pam restrictions (G)\fR
+When Samba 2.2 is configured to enable PAM support
+(i.e. --with-pam), this parameter will control whether or not Samba
+should obey PAM's account and session management directives. The
+default behavior is to use PAM for clear text authentication only
+and to ignore any account or session management. Note that Samba
+always ignores PAM for authentication in the case of \fIencrypt passwords = yes\fR
+\&. The reason is that PAM modules cannot support the challenge/response
+authentication mechanism needed in the presence of SMB password encryption.
Default: \fBobey pam restrictions = no\fR
-
-
.TP
-only guest (S)
-A synonym for \fI guest only\fR\&.
-
-
-.TP
-only user (S)
-This is a boolean option that controls whether connections with usernames not in the \fIuser\fR list will be allowed\&. By default this option is disabled so that a client can supply a username to be used by the server\&. Enabling this parameter will force the server to only use the login names from the \fIuser\fR list and is only really useful in share level security\&.
-
-
-Note that this also means Samba won't try to deduce usernames from the service name\&. This can be annoying for the [homes] section\&. To get around this you could use \fBuser = %S\fR which means your \fIuser\fR list will be just the service name, which for home directories is the name of the user\&.
-
-
-See also the \fIuser\fR parameter\&.
-
+\fBonly user (S)\fR
+This is a boolean option that controls whether
+connections with usernames not in the \fIuser\fR
+list will be allowed. By default this option is disabled so that a
+client can supply a username to be used by the server. Enabling
+this parameter will force the server to only use the login
+names from the \fIuser\fR list and is only really
+useful in share level
+security.
+
+Note that this also means Samba won't try to deduce
+usernames from the service name. This can be annoying for
+the [homes] section. To get around this you could use \fBuser =
+%S\fR which means your \fIuser\fR list
+will be just the service name, which for home directories is the
+name of the user.
+
+See also the \fIuser\fR
+parameter.
Default: \fBonly user = no\fR
-
-
.TP
-oplock break wait time (G)
-This is a tuning parameter added due to bugs in both Windows 9x and WinNT\&. If Samba responds to a client too quickly when that client issues an SMB that can cause an oplock break request, then the network client can fail and not respond to the break request\&. This tuning parameter (which is set in milliseconds) is the amount of time Samba will wait before sending an oplock break request to such (broken) clients\&.
-
-
-\fBDO NOT CHANGE THIS PARAMETER UNLESS YOU HAVE READ AND UNDERSTOOD THE SAMBA OPLOCK CODE\fR\&.
+\fBonly guest (S)\fR
+A synonym for \fI guest only\fR.
+.TP
+\fBoplock break wait time (G)\fR
+This is a tuning parameter added due to bugs in
+both Windows 9x and WinNT. If Samba responds to a client too
+quickly when that client issues an SMB that can cause an oplock
+break request, then the network client can fail and not respond
+to the break request. This tuning parameter (which is set in milliseconds)
+is the amount of time Samba will wait before sending an oplock break
+request to such (broken) clients.
+\fBDO NOT CHANGE THIS PARAMETER UNLESS YOU HAVE READ
+AND UNDERSTOOD THE SAMBA OPLOCK CODE\fR.
Default: \fBoplock break wait time = 0\fR
-
-
.TP
-oplock contention limit (S)
-This is a \fBvery\fR advanced \fBsmbd\fR(8) tuning option to improve the efficiency of the granting of oplocks under multiple client contention for the same file\&.
-
-
-In brief it specifies a number, which causes \fBsmbd\fR(8)not to grant an oplock even when requested if the approximate number of clients contending for an oplock on the same file goes over this limit\&. This causes \fBsmbd\fR to behave in a similar way to Windows NT\&.
+\fBoplock contention limit (S)\fR
+This is a \fBvery\fR advanced
+smbd(8) tuning option to
+improve the efficiency of the granting of oplocks under multiple
+client contention for the same file.
+In brief it specifies a number, which causes smbd not to
+grant an oplock even when requested if the approximate number of
+clients contending for an oplock on the same file goes over this
+limit. This causes \fBsmbd\fR to behave in a similar
+way to Windows NT.
-\fBDO NOT CHANGE THIS PARAMETER UNLESS YOU HAVE READ AND UNDERSTOOD THE SAMBA OPLOCK CODE\fR\&.
-
+\fBDO NOT CHANGE THIS PARAMETER UNLESS YOU HAVE READ
+AND UNDERSTOOD THE SAMBA OPLOCK CODE\fR.
Default: \fBoplock contention limit = 2\fR
-
-
.TP
-oplocks (S)
-This boolean option tells \fBsmbd\fR 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 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 directory\&.
-
-
-Oplocks may be selectively turned off on certain files with a share\&. See the \fI veto oplock files\fR parameter\&. On some systems oplocks are recognized by the underlying operating system\&. This allows data synchronization between all access to oplocked files, whether it be via Samba or NFS or a local UNIX process\&. See the \fIkernel oplocks\fR parameter for details\&.
-
-
-See also the \fIkernel oplocks\fR and \fI level2 oplocks\fR parameters\&.
-
+\fBoplocks (S)\fR
+This boolean option tells \fBsmbd\fR 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 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
+directory.
+
+Oplocks may be selectively turned off on certain files with a
+share. See the \fI veto oplock files\fR parameter. On some systems
+oplocks are recognized by the underlying operating system. This
+allows data synchronization between all access to oplocked files,
+whether it be via Samba or NFS or a local UNIX process. See the
+\fIkernel oplocks\fR parameter for details.
+
+See also the \fIkernel
+oplocks\fR and \fI level2 oplocks\fR parameters.
Default: \fBoplocks = yes\fR
-
-
.TP
-os2 driver map (G)
-The parameter is used to define the absolute path to a file containing a mapping of Windows NT printer driver names to OS/2 printer driver names\&. The format is:
-
-
-<nt driver name> = <os2 driver name>\&.<device name>
-
-
-For example, a valid entry using the HP LaserJet 5 printer driver would appear as \fBHP LaserJet 5L = LASERJET.HP LaserJet 5L\fR\&.
-
-
-The need for the file is due to the printer driver namespace problem described in the Samba Printing HOWTO\&. For more details on OS/2 clients, please refer to the OS2-Client-HOWTO containing in the Samba documentation\&.
-
-
-Default: \fBos2 driver map = <empty string>\fR
+\fBntlm auth (G)\fR
+This parameter determines whether or not smbd will
+attempt to authenticate users using the NTLM password hash.
+If disabled, only the lanman password hashes will be used.
+Please note that at least this option or \fBlanman auth\fR should be enabled in order to be able to log in.
+Default : \fBntlm auth = yes\fR
.TP
-os level (G)
-This integer value controls what level Samba advertises itself as for browse elections\&. The value of this parameter determines whether \fBnmbd\fR(8) has a chance of becoming a local master browser for the \fI WORKGROUP\fR in the local broadcast area\&.
-
-
-\fBNote :\fRBy default, Samba will win a local master browsing election over all Microsoft operating systems except a Windows NT 4\&.0/2000 Domain Controller\&. This means that a misconfigured Samba host can effectively isolate a subnet for browsing purposes\&. See \fIBROWSING\&.txt \fR in the Samba \fIdocs/\fR directory for details\&.
+\fBos level (G)\fR
+This integer value controls what level Samba
+advertises itself as for browse elections. The value of this
+parameter determines whether nmbd(8)
+has a chance of becoming a local master browser for the \fI WORKGROUP\fR in the local broadcast area.
+\fBNote :\fRBy default, Samba will win
+a local master browsing election over all Microsoft operating
+systems except a Windows NT 4.0/2000 Domain Controller. This
+means that a misconfigured Samba host can effectively isolate
+a subnet for browsing purposes. See \fIBROWSING.txt
+\fR in the Samba \fIdocs/\fR directory
+for details.
Default: \fBos level = 20\fR
-
Example: \fBos level = 65 \fR
-
-
.TP
-pam password change (G)
-With the addition of better PAM support in Samba 2\&.2, this parameter, it is possible to use PAM's password change control flag for Samba\&. If enabled, then PAM will be used for password changes when requested by an SMB client instead of the program listed in \fIpasswd program\fR\&. It should be possible to enable this without changing your \fIpasswd chat\fR parameter for most setups\&.
-
+\fBos2 driver map (G)\fR
+The parameter is used to define the absolute
+path to a file containing a mapping of Windows NT printer driver
+names to OS/2 printer driver names. The format is:
+
+<nt driver name> = <os2 driver
+name>.<device name>
+
+For example, a valid entry using the HP LaserJet 5
+printer driver would appear as \fBHP LaserJet 5L = LASERJET.HP
+LaserJet 5L\fR.
+
+The need for the file is due to the printer driver namespace
+problem described in the Samba
+Printing HOWTO For more details on OS/2 clients, please
+refer to the OS2-Client-HOWTO
+ containing in the Samba documentation.
+
+Default: \fBos2 driver map = <empty string>
+\fR
+.TP
+\fBpam password change (G)\fR
+With the addition of better PAM support in Samba 2.2,
+this parameter, it is possible to use PAM's password change control
+flag for Samba. If enabled, then PAM will be used for password
+changes when requested by an SMB client instead of the program listed in
+\fIpasswd program\fR.
+It should be possible to enable this without changing your
+\fIpasswd chat\fR
+parameter for most setups.
Default: \fBpam password change = no\fR
-
-
.TP
-panic action (G)
-This is a Samba developer option that allows a system command to be called when either \fBsmbd\fR(8) or \fBsmbd\fR(8) crashes\&. This is usually used to draw attention to the fact that a problem occurred\&.
-
+\fBpanic action (G)\fR
+This is a Samba developer option that allows a
+system command to be called when either smbd(8)
+crashes. This is usually used to draw attention to the fact that
+a problem occurred.
Default: \fBpanic action = <empty string>\fR
-
Example: \fBpanic action = "/bin/sleep 90000"\fR
-
-
.TP
-paranoid server security (G)
-Some version of NT 4\&.x allow non-guest users with a bad passowrd\&. When this option is enabled, samba will not use a broken NT 4\&.x server as password server, but instead complain to the logs and exit\&.
-
-
-Disabling this option prevents Samba from making this check, which involves deliberatly attempting a bad logon to the remote server\&.
-
+\fBparanoid server security (G)\fR
+Some version of NT 4.x allow non-guest
+users with a bad passowrd. When this option is enabled, samba will not
+use a broken NT 4.x server as password server, but instead complain
+to the logs and exit.
Default: \fBparanoid server security = yes\fR
-
-
.TP
-passdb backend (G)
-This option allows the administrator to chose which backends to retrieve and store passwords with\&. This allows (for example) both smbpasswd and tdbsam to be used without a recompile\&. Multiple backends can be specified, separated by spaces\&. The backends will be searched in the order they are specified\&. New users are always added to the first backend specified\&.
+\fBpassdb backend (G)\fR
+This option allows the administrator to chose which backends to retrieve and store passwords with. This allows (for example) both
+smbpasswd and tdbsam to be used without a recompile.
+Multiple backends can be specified, separated by spaces. The backends will be searched in the order they are specified. New users are always added to the first backend specified.
+Experimental backends must still be selected
+(eg --with-tdbsam) at configure time.
+This parameter is in two parts, the backend's name, and a 'location'
+string that has meaning only to that particular backed. These are separated
+by a : character.
-This parameter is in two parts, the backend's name, and a 'location' string that has meaning only to that particular backed\&. These are separated by a : character\&.
+Available backends can include:
+.RS
+.TP 0.2i
+\(bu
+\fBsmbpasswd\fR - The default smbpasswd
+backend. Takes a path to the smbpasswd file as an optional argument.
+.TP 0.2i
+\(bu
+\fBsmbpasswd_nua\fR - The smbpasswd
+backend, but with support for 'not unix accounts'.
+Takes a path to the smbpasswd file as an optional argument.
+See also \fInon unix account range\fR
+.TP 0.2i
+\(bu
+\fBtdbsam\fR - The TDB based password storage
+backend. Takes a path to the TDB as an optional argument (defaults to passdb.tdb
+in the \fIprivate dir\fR directory.
+.TP 0.2i
+\(bu
+\fBtdbsam_nua\fR - The TDB based password storage
+backend, with non unix account support. Takes a path to the TDB as an optional argument (defaults to passdb.tdb
+in the \fIprivate dir\fR directory.
-Available backends can include: .TP 3 \(bu \fBsmbpasswd\fR - The default smbpasswd backend\&. Takes a path to the smbpasswd file as an optional argument\&. .TP \(bu \fBsmbpasswd_nua\fR - The smbpasswd backend, but with support for 'not unix accounts'\&. Takes a path to the smbpasswd file as an optional argument\&. See also \fInon unix account range\fR .TP \(bu \fBtdbsam\fR - The TDB based password storage backend\&. Takes a path to the TDB as an optional argument (defaults to passdb\&.tdb in the \fIprivate dir\fR directory\&. .TP \(bu \fBtdbsam_nua\fR - The TDB based password storage backend, with non unix account support\&. Takes a path to the TDB as an optional argument (defaults to passdb\&.tdb in the \fIprivate dir\fR directory\&. See also \fInon unix account range\fR .TP \(bu \fBldapsam\fR - The LDAP based passdb backend\&. Takes an LDAP URL as an optional argument (defaults to \fBldap://localhost\fR) .TP \(bu \fBldapsam_nua\fR - The LDAP based passdb backend, with non unix account support\&. Takes an LDAP URL as an optional argument (defaults to \fBldap://localhost\fR) Note: In this module, any account without a matching POSIX account is regarded as 'non unix'\&. See also \fInon unix account range\fR LDAP connections should be secured where possible\&. This may be done using either Start-TLS (see \fIldap ssl\fR) or by specifying \fIldaps://\fR in the URL argument\&. .TP \(bu \fBnisplussam\fR - The NIS+ based passdb backend\&. Takes name NIS domain as an optional argument\&. Only works with sun NIS+ servers\&. .LP
+See also \fInon unix account range\fR
+.TP 0.2i
+\(bu
+\fBldapsam\fR - The LDAP based passdb
+backend. Takes an LDAP URL as an optional argument (defaults to
+\fBldap://localhost\fR)
+.TP 0.2i
+\(bu
+\fBldapsam_nua\fR - The LDAP based passdb
+backend, with non unix account support. Takes an LDAP URL as an optional argument (defaults to
+\fBldap://localhost\fR)
+Note: In this module, any account without a matching POSIX account is regarded
+as 'non unix'.
-Default: \fBpassdb backend = smbpasswd unixsam\fR
+See also \fInon unix account
+range\fR
+LDAP connections should be secured where
+possible. This may be done using either
+Start-TLS (see \fIldap ssl\fR) or by
+specifying \fIldaps://\fR in
+the URL argument.
+.TP 0.2i
+\(bu
+\fBnisplussam\fR - The NIS+ based passdb backend. Takes name NIS domain as an optional argument. Only works with sun NIS+ servers.
+.TP 0.2i
+\(bu
+\fBplugin\fR - Allows Samba to load an
+arbitary passdb backend from the .so specified as a compulsary argument.
-Example: \fBpassdb backend = tdbsam:/etc/samba/private/passdb.tdb smbpasswd:/etc/samba/smbpasswd guest\fR
+Any characters after the (optional) second : are passed to the plugin
+for its own processing
+.TP 0.2i
+\(bu
+\fBunixsam\fR - (EXPERIMENTAL) Allows samba to map all (other) available unix users
+This backend uses the standard unix database for retrieving users. Users included
+in this pdb are NOT listed in samba user listings and users included in this pdb won't be
+able to login. The use of this backend is to always be able to display the owner of a file
+on the samba server - even when the user doesn't have a 'real' samba account in one of the
+other passdb backends.
-Example: \fBpassdb backend = ldapsam_nua:ldaps://ldap.example.com guest\fR
+This backend should always be the last backend listed, since it contains all users in
+the unix passdb and might 'override' mappings if specified earlier. It's meant to only return
+accounts for users that aren't covered by the previous backends.
+.RE
+Default: \fBpassdb backend = smbpasswd guest\fR
-Example: \fBpassdb backend = mysql:my_plugin_args tdbsam:/etc/samba/private/passdb.tdb\fR
+Example: \fBpassdb backend = tdbsam:/etc/samba/private/passdb.tdb smbpasswd:/etc/samba/smbpasswd \fR
+Example: \fBpassdb backend = ldapsam_nua:ldaps://ldap.example.com \fR
+Example: \fBpassdb backend = plugin:/usr/local/samba/lib/my_passdb.so:my_plugin_args tdbsam:/etc/samba/private/passdb.tdb\fR
.TP
-passwd chat debug (G)
-This boolean specifies if the passwd chat script parameter is run in \fBdebug\fR mode\&. In this mode the strings passed to and received from the passwd chat are printed in the \fBsmbd\fR(8) log with a \fIdebug level\fR of 100\&. This is a dangerous option as it will allow plaintext passwords to be seen in the \fBsmbd\fR log\&. It is available to help Samba admins debug their \fIpasswd chat\fR scripts when calling the \fIpasswd program\fR and should be turned off after this has been done\&. This option has no effect if the \fIpam password change\fR paramter is set\&. This parameter is off by default\&.
-
-
-See also \fIpasswd chat\fR , \fIpam password change\fR , \fIpasswd program\fR \&.
+\fBpasswd chat (G)\fR
+This string controls the \fB"chat"\fR
+conversation that takes places between smbd and the local password changing
+program to change the user's password. The string describes a
+sequence of response-receive pairs that smbd(8) uses to determine what to send to the
+\fIpasswd program\fR
+and what to expect back. If the expected output is not
+received then the password is not changed.
+
+This chat sequence is often quite site specific, depending
+on what local methods are used for password control (such as NIS
+etc).
+
+Note that this parameter only is only used if the \fIunix
+password sync\fR parameter is set to yes. This
+sequence is then called \fBAS ROOT\fR when the SMB password
+in the smbpasswd file is being changed, without access to the old
+password cleartext. This means that root must be able to reset the user's password
+without knowing the text of the previous password. In the presence of NIS/YP,
+this means that the passwd program must be
+executed on the NIS master.
+
+The string can contain the macro \fI%n\fR which is substituted
+for the new password. The chat sequence can also contain the standard
+macros \\n, \\r, \\t and \\s to give line-feed,
+carriage-return, tab and space. The chat sequence string can also contain
+a '*' which matches any sequence of characters.
+Double quotes can be used to collect strings with spaces
+in them into a single string.
+
+If the send string in any part of the chat sequence
+is a full stop ".", then no string is sent. Similarly,
+if the expect string is a full stop then no string is expected.
+
+If the \fIpam
+password change\fR parameter is set to yes, the chat pairs
+may be matched in any order, and success is determined by the PAM result,
+not any particular output. The \\n macro is ignored for PAM conversions.
+
+See also \fIunix password
+sync\fR, \fI passwd program\fR , \fIpasswd chat debug\fR and \fIpam password change\fR.
+
+Default: \fBpasswd chat = *new*password* %n\\n
+*new*password* %n\\n *changed*\fR
+
+Example: \fBpasswd chat = "*Enter OLD password*" %o\\n
+"*Enter NEW password*" %n\\n "*Reenter NEW password*" %n\\n "*Password
+changed*"\fR
+.TP
+\fBpasswd chat debug (G)\fR
+This boolean specifies if the passwd chat script
+parameter is run in \fBdebug\fR mode. In this mode the
+strings passed to and received from the passwd chat are printed
+in the smbd(8) log with a
+\fIdebug level\fR
+of 100. This is a dangerous option as it will allow plaintext passwords
+to be seen in the \fBsmbd\fR log. It is available to help
+Samba admins debug their \fIpasswd chat\fR scripts
+when calling the \fIpasswd program\fR and should
+be turned off after this has been done. This option has no effect if the
+\fIpam password change\fR
+paramter is set. This parameter is off by default.
+See also \fIpasswd chat\fR
+, \fIpam password change\fR
+, \fIpasswd program\fR
+\&.
Default: \fBpasswd chat debug = no\fR
-
-
-.TP
-passwd chat (G)
-This string controls the \fB"chat"\fR conversation that takes places between \fBsmbd\fR(8) and the local password changing program to change the user's password\&. The string describes a sequence of response-receive pairs that \fBsmbd\fR(8) uses to determine what to send to the \fIpasswd program\fR and what to expect back\&. If the expected output is not received then the password is not changed\&.
-
-
-This chat sequence is often quite site specific, depending on what local methods are used for password control (such as NIS etc)\&.
-
-
-Note that this parameter only is only used if the \fIunix password sync\fR parameter is set to \fByes\fR\&. This sequence is then called \fBAS ROOT\fR when the SMB password in the smbpasswd file is being changed, without access to the old password cleartext\&. This means that root must be able to reset the user's password without knowing the text of the previous password\&. In the presence of NIS/YP, this means that the passwd program must be executed on the NIS master\&.
-
-
-The string can contain the macro \fI%n\fR which is substituted for the new password\&. The chat sequence can also contain the standard macros \fB\\\\n\fR, \fB\\\\r\fR, \fB\\\\t\fR and \fB\\\\s\fR to give line-feed, carriage-return, tab and space\&. The chat sequence string can also contain a '*' which matches any sequence of characters\&. Double quotes can be used to collect strings with spaces in them into a single string\&.
-
-
-If the send string in any part of the chat sequence is a full stop "\&.", then no string is sent\&. Similarly, if the expect string is a full stop then no string is expected\&.
-
-
-If the \fIpam password change\fR parameter is set to \fByes\fR, the chat pairs may be matched in any order, and success is determined by the PAM result, not any particular output\&. The \\n macro is ignored for PAM conversions\&.
-
-
-See also \fIunix password sync\fR, \fI passwd program\fR , \fIpasswd chat debug\fR and \fIpam password change\fR\&.
-
-
-Default: \fBpasswd chat = *new*password* %n\\n *new*password* %n\\n *changed*\fR
-
-
-Example: \fBpasswd chat = "*Enter OLD password*" %o\\n "*Enter NEW password*" %n\\n "*Reenter NEW password*" %n\\n "*Password changed*"\fR
-
-
.TP
-passwd program (G)
-The name of a program that can be used to set UNIX user passwords\&. Any occurrences of \fI%u\fR will be replaced with the user name\&. The user name is checked for existence before calling the password changing program\&.
-
-
-Also note that many passwd programs insist in \fBreasonable \fR passwords, such as a minimum length, or the inclusion of mixed case chars and digits\&. This can pose a problem as some clients (such as Windows for Workgroups) uppercase the password before sending it\&.
-
-
-\fBNote\fR that if the \fIunix password sync\fR parameter is set to \fByes \fR then this program is called \fBAS ROOT\fR before the SMB password in the \fBsmbpasswd\fR(5) file is changed\&. If this UNIX password change fails, then \fBsmbd\fR will fail to change the SMB password also (this is by design)\&.
-
-
-If the \fIunix password sync\fR parameter is set this parameter \fBMUST USE ABSOLUTE PATHS\fR for \fBALL\fR programs called, and must be examined for security implications\&. Note that by default \fIunix password sync\fR is set to \fBno\fR\&.
-
-
-See also \fIunix password sync\fR\&.
-
+\fBpasswd program (G)\fR
+The name of a program that can be used to set
+UNIX user passwords. Any occurrences of \fI%u\fR
+will be replaced with the user name. The user name is checked for
+existence before calling the password changing program.
+
+Also note that many passwd programs insist in \fBreasonable
+\fR passwords, such as a minimum length, or the inclusion
+of mixed case chars and digits. This can pose a problem as some clients
+(such as Windows for Workgroups) uppercase the password before sending
+it.
+
+\fBNote\fR that if the \fIunix
+password sync\fR parameter is set to yes
+then this program is called \fBAS ROOT\fR
+before the SMB password in the smbpasswd(5)
+ file is changed. If this UNIX password change fails, then
+\fBsmbd\fR will fail to change the SMB password also
+(this is by design).
+
+If the \fIunix password sync\fR parameter
+is set this parameter \fBMUST USE ABSOLUTE PATHS\fR
+for \fBALL\fR programs called, and must be examined
+for security implications. Note that by default \fIunix
+password sync\fR is set to no.
+
+See also \fIunix
+password sync\fR.
Default: \fBpasswd program = /bin/passwd\fR
-
Example: \fBpasswd program = /sbin/npasswd %u\fR
-
-
.TP
-password level (G)
-Some client/server combinations have difficulty with mixed-case passwords\&. One offending client is Windows for Workgroups, which for some reason forces passwords to upper case when using the LANMAN1 protocol, but leaves them alone when using COREPLUS! Another problem child is the Windows 95/98 family of operating systems\&. These clients upper case clear text passwords even when NT LM 0\&.12 selected by the protocol negotiation request/response\&.
-
-
-This parameter defines the maximum number of characters that may be upper case in passwords\&.
-
+\fBpassword level (G)\fR
+Some client/server combinations have difficulty
+with mixed-case passwords. One offending client is Windows for
+Workgroups, which for some reason forces passwords to upper
+case when using the LANMAN1 protocol, but leaves them alone when
+using COREPLUS! Another problem child is the Windows 95/98
+family of operating systems. These clients upper case clear
+text passwords even when NT LM 0.12 selected by the protocol
+negotiation request/response.
-For example, say the password given was "FRED"\&. If \fI password level\fR is set to 1, the following combinations would be tried if "FRED" failed:
+This parameter defines the maximum number of characters
+that may be upper case in passwords.
+For example, say the password given was "FRED". If \fI password level\fR is set to 1, the following combinations
+would be tried if "FRED" failed:
"Fred", "fred", "fRed", "frEd","freD"
+If \fIpassword level\fR was set to 2,
+the following combinations would also be tried:
-If \fIpassword level\fR was set to 2, the following combinations would also be tried:
-
-
-"FRed", "FrEd", "FreD", "fREd", "fReD", "frED", \&.\&.
-
-
-And so on\&.
-
-
-The higher value this parameter is set to the more likely it is that a mixed case password will be matched against a single case password\&. However, you should be aware that use of this parameter reduces security and increases the time taken to process a new connection\&.
+"FRed", "FrEd", "FreD", "fREd", "fReD", "frED", ..
+And so on.
-A value of zero will cause only two attempts to be made - the password as is and the password in all-lower case\&.
+The higher value this parameter is set to the more likely
+it is that a mixed case password will be matched against a single
+case password. However, you should be aware that use of this
+parameter reduces security and increases the time taken to
+process a new connection.
+A value of zero will cause only two attempts to be
+made - the password as is and the password in all-lower case.
Default: \fBpassword level = 0\fR
-
Example: \fBpassword level = 4\fR
-
-
.TP
-password server (G)
-By specifying the name of another SMB server (such as a WinNT box) with this option, and using \fBsecurity = domain \fR or \fBsecurity = server\fR you can get Samba to do all its username/password validation via a remote server\&.
-
-
-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 name to the lmhosts file which is stored in the same directory as the \fIsmb\&.conf\fR file\&.
-
-
-The name of the password server is looked up using the parameter \fIname resolve order\fR and so may resolved by any method and order described in that parameter\&.
-
-
-The password server must be a machine capable of using the "LM1\&.2X002" or the "NT LM 0\&.12" protocol, and it must be in user level security mode\&.
-
-
-Using a password server means your UNIX box (running Samba) is only as secure as your password server\&. \fBDO NOT CHOOSE A PASSWORD SERVER THAT YOU DON'T COMPLETELY TRUST\fR\&.
-
-Never point a Samba server at itself for password serving\&. This will cause a loop and could lock up your Samba 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 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 \fBdomain\fR, 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 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 \fR will try each in turn till it finds one that responds\&. This is useful in case your primary server goes down\&.
-
-
-If the \fIpassword server\fR option is set to the character '*', then Samba will attempt to auto-locate the Primary or Backup Domain controllers to authenticate against by doing a query for the name \fBWORKGROUP<1C>\fR and then contacting each server returned in the list of IP addresses from the name resolution source\&.
-
-
-If the list of servers contains both names and the '*' character, the list is treated as a list of preferred domain controllers, but an auto lookup of all remaining DC's will be added to the list as well\&. Samba will not attempt to optimize this list by locating the closest DC\&.
-
-
-If the \fIsecurity\fR parameter is set to \fBserver\fR, then there are different restrictions that \fBsecurity = domain\fR doesn't suffer from:
-
-
-You may list several password servers in the \fIpassword server\fR parameter, however if an \fBsmbd\fR makes a connection to a password server, and then the password server fails, no more users will be able to be authenticated from this \fBsmbd\fR\&. This is a restriction of the SMB/CIFS protocol when in \fBsecurity = server \fR mode and cannot be fixed in Samba\&.
-
-If you are using a Windows NT server as your password server then you will have to ensure that your users are able to login from the Samba server, as when in \fB security = server\fR mode the network logon will appear to come from there rather than from the users workstation\&.
-
-See also the \fIsecurity \fR parameter\&.
+\fBpassword server (G)\fR
+By specifying the name of another SMB server (such
+as a WinNT box) with this option, and using \fBsecurity = domain
+\fR or \fBsecurity = server\fR you can get Samba
+to do all its username/password validation via a remote server.
+
+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
+name to the lmhosts file which is stored in the same directory
+as the \fIsmb.conf\fR file.
+
+The name of the password server is looked up using the
+parameter \fIname
+resolve order\fR and so may resolved
+by any method and order described in that parameter.
+
+The password server must be a machine capable of using
+the "LM1.2X002" or the "NT LM 0.12" protocol, and it must be in
+user level security mode.
+
+\fBNOTE:\fR Using a password server
+means your UNIX box (running Samba) is only as secure as your
+password server. \fBDO NOT CHOOSE A PASSWORD SERVER THAT
+YOU DON'T COMPLETELY TRUST\fR.
+
+Never point a Samba server at itself for password
+serving. This will cause a loop and could lock up your Samba
+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 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 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
+\fR will try each in turn till it finds one that responds. This
+is useful in case your primary server goes down.
+
+If the \fIpassword server\fR option is set
+to the character '*', then Samba will attempt to auto-locate the
+Primary or Backup Domain controllers to authenticate against by
+doing a query for the name WORKGROUP<1C>
+and then contacting each server returned in the list of IP
+addresses from the name resolution source.
+
+If the list of servers contains both names and the '*'
+character, the list is treated as a list of preferred
+domain controllers, but an auto lookup of all remaining DC's
+will be added to the list as well. Samba will not attempt to optimize
+this list by locating the closest DC.
+
+If the \fIsecurity\fR parameter is
+set to server, then there are different
+restrictions that \fBsecurity = domain\fR doesn't
+suffer from:
+.RS
+.TP 0.2i
+\(bu
+You may list several password servers in
+the \fIpassword server\fR parameter, however if an
+\fBsmbd\fR makes a connection to a password server,
+and then the password server fails, no more users will be able
+to be authenticated from this \fBsmbd\fR. This is a
+restriction of the SMB/CIFS protocol when in \fBsecurity = server
+\fR mode and cannot be fixed in Samba.
+.TP 0.2i
+\(bu
+If you are using a Windows NT server as your
+password server then you will have to ensure that your users
+are able to login from the Samba server, as when in \fB security = server\fR mode the network logon will appear to
+come from there rather than from the users workstation.
+.RE
+See also the \fIsecurity
+\fR parameter.
Default: \fBpassword server = <empty string>\fR
-
-Example: \fBpassword server = NT-PDC, NT-BDC1, NT-BDC2, *\fR
-
+Example: \fBpassword server = NT-PDC, NT-BDC1, NT-BDC2, *
+\fR
Example: \fBpassword server = *\fR
-
-
.TP
-path (S)
-This parameter specifies a directory to which the user of the service is to be given access\&. In the case of printable services, this is where print data will spool prior to being submitted to the host for printing\&.
-
-
-For a printable service offering guest access, the service should be readonly and the path should be world-writeable and have the sticky bit set\&. This is not mandatory of course, but you probably won't get the results you expect if you do otherwise\&.
-
-
-Any occurrences of \fI%u\fR in the path will be replaced with the UNIX username that the client is using on this connection\&. Any occurrences of \fI%m\fR will be replaced by the NetBIOS name of the machine they are connecting from\&. These replacements are very useful for setting up pseudo home directories for users\&.
+\fBpath (S)\fR
+This parameter specifies a directory to which
+the user of the service is to be given access. In the case of
+printable services, this is where print data will spool prior to
+being submitted to the host for printing.
+For a printable service offering guest access, the service
+should be readonly and the path should be world-writeable and
+have the sticky bit set. This is not mandatory of course, but
+you probably won't get the results you expect if you do
+otherwise.
-Note that this path will be based on \fIroot dir\fR if one was specified\&.
+Any occurrences of \fI%u\fR in the path
+will be replaced with the UNIX username that the client is using
+on this connection. Any occurrences of \fI%m\fR
+will be replaced by the NetBIOS name of the machine they are
+connecting from. These replacements are very useful for setting
+up pseudo home directories for users.
+Note that this path will be based on \fIroot dir\fR if one was specified.
Default: \fBnone\fR
-
Example: \fBpath = /home/fred\fR
-
-
.TP
-pid directory (G)
-This option specifies the directory where pid files will be placed\&.
-
+\fBpid directory (G)\fR
+This option specifies the directory where pid
+files will be placed.
Default: \fBpid directory = ${prefix}/var/locks\fR
-
Example: \fBpid directory = /var/run/\fR
-
-
.TP
-posix locking (S)
-The \fBsmbd\fR(8) daemon maintains an database of file locks obtained by SMB clients\&. The default behavior is to map this internal database to POSIX locks\&. This means that file locks obtained by SMB clients are consistent with those seen by POSIX compliant applications accessing the files via a non-SMB method (e\&.g\&. NFS or local file access)\&. You should never need to disable this parameter\&.
-
+\fBposix locking (S)\fR
+The \fBsmbd(8)\fR
+daemon maintains an database of file locks obtained by SMB clients.
+The default behavior is to map this internal database to POSIX
+locks. This means that file locks obtained by SMB clients are
+consistent with those seen by POSIX compliant applications accessing
+the files via a non-SMB method (e.g. NFS or local file access).
+You should never need to disable this parameter.
Default: \fBposix locking = yes\fR
-
-
.TP
-postexec (S)
-This option specifies a command to be run whenever the service is disconnected\&. It takes the usual substitutions\&. The command may be run as the root on some systems\&.
-
-
-An interesting example may be to unmount server resources:
+\fBpostexec (S)\fR
+This option specifies a command to be run
+whenever the service is disconnected. It takes the usual
+substitutions. The command may be run as the root on some
+systems.
+An interesting example may be to unmount server
+resources:
\fBpostexec = /etc/umount /cdrom\fR
-
-See also \fIpreexec\fR\&.
-
+See also \fIpreexec\fR
+\&.
Default: \fBnone (no command executed)\fR
-
-Example: \fBpostexec = echo \"%u disconnected from %S from %m (%I)\" >> /tmp/log\fR
-
-
+Example: \fBpostexec = echo \\"%u disconnected from %S
+from %m (%I)\\" >> /tmp/log\fR
.TP
-preexec close (S)
-This boolean option controls whether a non-zero return code from \fIpreexec \fR should close the service being connected to\&.
-
-
-Default: \fBpreexec close = no\fR
+\fBpostscript (S)\fR
+This parameter forces a printer to interpret
+the print files as PostScript. This is done by adding a %!
+to the start of print output.
+This is most useful when you have lots of PCs that persist
+in putting a control-D at the start of print jobs, which then
+confuses your printer.
+Default: \fBpostscript = no\fR
.TP
-preexec (S)
-This option specifies a command to be run whenever the service is connected to\&. It takes the usual substitutions\&.
-
+\fBpreexec (S)\fR
+This option specifies a command to be run whenever
+the service is connected to. It takes the usual substitutions.
-An interesting example is to send the users a welcome message every time they log in\&. Maybe a message of the day? Here is an example:
-
-
-\fBpreexec = csh -c 'echo \"Welcome to %S!\" | /usr/local/samba/bin/smbclient -M %m -I %I' & \fR
+An interesting example is to send the users a welcome
+message every time they log in. Maybe a message of the day? Here
+is an example:
+\fBpreexec = csh -c 'echo \\"Welcome to %S!\\" |
+/usr/local/samba/bin/smbclient -M %m -I %I' & \fR
Of course, this could get annoying after a while :-)
-
-See also \fIpreexec close\fR and \fIpostexec \fR\&.
-
+See also \fIpreexec close
+\fR and \fIpostexec
+\fR.
Default: \fBnone (no command executed)\fR
-
-Example: \fBpreexec = echo \"%u connected to %S from %m (%I)\" >> /tmp/log\fR
-
-
+Example: \fBpreexec = echo \\"%u connected to %S from %m
+(%I)\\" >> /tmp/log\fR
.TP
-prefered master (G)
-Synonym for \fI preferred master\fR for people who cannot spell :-)\&.
-
+\fBpreexec close (S)\fR
+This boolean option controls whether a non-zero
+return code from \fIpreexec
+\fR should close the service being connected to.
+Default: \fBpreexec close = no\fR
.TP
-preferred master (G)
-This boolean parameter controls if \fBnmbd\fR(8) is a preferred master browser for its workgroup\&.
+\fBpreferred master (G)\fR
+This boolean parameter controls if nmbd(8) is a preferred master browser
+for its workgroup.
+If this is set to yes, on startup, \fBnmbd\fR
+will force an election, and it will have a slight advantage in
+winning the election. It is recommended that this parameter is
+used in conjunction with \fB\fI domain master\fB = yes\fR, so that \fB nmbd\fR can guarantee becoming a domain master.
-If this is set to \fByes\fR, on startup, \fBnmbd\fR will force an election, and it will have a slight advantage in winning the election\&. It is recommended that this parameter is used in conjunction with \fB domain master = yes\fR, so that \fBnmbd\fR can guarantee becoming a domain master\&.
-
-
-Use this option with caution, because if there are several hosts (whether Samba servers, Windows 95 or NT) that are preferred master browsers on the same subnet, they will each periodically and continuously attempt to become the local master browser\&. This will result in unnecessary broadcast traffic and reduced browsing capabilities\&.
-
-
-See also \fIos level\fR\&.
+Use this option with caution, because if there are several
+hosts (whether Samba servers, Windows 95 or NT) that are preferred
+master browsers on the same subnet, they will each periodically
+and continuously attempt to become the local master browser.
+This will result in unnecessary broadcast traffic and reduced browsing
+capabilities.
+See also \fIos level\fR
+\&.
Default: \fBpreferred master = auto\fR
-
-
.TP
-preload modules (G)
-This is a list of paths to modules that should be loaded into smbd before a client connects\&. This improves the speed of smbd when reacting to new connections somewhat\&.
-
-
-It is recommended to only use this option on heavy-performance servers\&.
-
-
-Default: \fBpreload modules = \fR
-
-
-Example: \fBpreload modules = /usr/lib/samba/passdb/mysql.so+++ \fR
-
-
+\fBprefered master (G)\fR
+Synonym for \fI preferred master\fR for people who cannot spell :-).
.TP
-preload (G)
-This is a list of services that you want to be automatically added to the browse lists\&. This is most useful for homes and printers services that would otherwise not be visible\&.
-
-
-Note that if you just want all printers in your printcap file loaded then the \fIload printers\fR option is easier\&.
+\fBpreload (G)\fR
+This is a list of services that you want to be
+automatically added to the browse lists. This is most useful
+for homes and printers services that would otherwise not be
+visible.
+Note that if you just want all printers in your
+printcap file loaded then the \fIload printers\fR option is easier.
Default: \fBno preloaded services\fR
-
Example: \fBpreload = fred lp colorlp\fR
-
-
.TP
-preserve case (S)
-This controls if new filenames are created with the case that the client passes, or if they are forced to be the \fIdefault case \fR\&.
-
+\fBpreserve case (S)\fR
+This controls if new filenames are created
+with the case that the client passes, or if they are forced to
+be the \fIdefault case
+\fR.
Default: \fBpreserve case = yes\fR
-
-See the section on NAME MANGLING for a fuller discussion\&.
-
-
-.TP
-printable (S)
-If this parameter is \fByes\fR, then clients may open, write to and submit spool files on the directory specified for the service\&.
-
-
-Note that a printable service will ALWAYS allow writing to the service path (user privileges permitting) via the spooling of print data\&. The \fIread only \fR parameter controls only non-printing access to the resource\&.
-
-
-Default: \fBprintable = no\fR
-
-
+See the section on NAME
+MANGLING for a fuller discussion.
.TP
-printcap name (S)
-This parameter may be used to override the compiled-in default printcap name used by the server (usually \fI /etc/printcap\fR)\&. See the discussion of the [printers] section above for reasons why you might want to do this\&.
+\fBprint command (S)\fR
+After a print job has finished spooling to
+a service, this command will be used via a \fBsystem()\fR
+call to process the spool file. Typically the command specified will
+submit the spool file to the host's printing subsystem, but there
+is no requirement that this be the case. The server will not remove
+the spool file, so whatever command you specify should remove the
+spool file when it has been processed, otherwise you will need to
+manually remove old spool files.
+The print command is simply a text string. It will be used
+verbatim after macro substitutions have been made:
-To use the CUPS printing interface set \fBprintcap name = cups \fR\&. This should be supplemented by an addtional setting printing = cups in the [global] section\&. \fBprintcap name = cups\fR will use the "dummy" printcap created by CUPS, as specified in your CUPS configuration file\&.
+s, %p - the path to the spool
+file name
+%p - the appropriate printer
+name
-On System V systems that use \fBlpstat\fR to list available printers you can use \fBprintcap name = lpstat \fR to automatically obtain lists of available printers\&. This is the default for systems that define SYSV at configure time in Samba (this includes most System V based systems)\&. If \fI printcap name\fR is set to \fBlpstat\fR on these systems then Samba will launch \fBlpstat -v\fR and attempt to parse the output to obtain a printer list\&.
-
-
-A minimal printcap file would look something like this:
-
-
-.nf
-
-print1|My Printer 1
-print2|My Printer 2
-print3|My Printer 3
-print4|My Printer 4
-print5|My Printer 5
-.fi
-
-
-where the '|' separates aliases of a printer\&. The fact that the second alias has a space in it gives a hint to Samba that it's a comment\&.
-
-
-Under AIX the default printcap name is \fI/etc/qconfig\fR\&. Samba will assume the file is in AIX \fIqconfig\fR format if the string \fIqconfig\fR appears in the printcap filename\&.
-
-Default: \fBprintcap name = /etc/printcap\fR
-
-
-Example: \fBprintcap name = /etc/myprintcap\fR
-
-
-.TP
-printcap (G)
-Synonym for \fI printcap name\fR\&.
-
-
-.TP
-print command (S)
-After a print job has finished spooling to a service, this command will be used via a \fBsystem()\fR call to process the spool file\&. Typically the command specified will submit the spool file to the host's printing subsystem, but there is no requirement that this be the case\&. The server will not remove the spool file, so whatever command you specify should remove the spool file when it has been processed, otherwise you will need to manually remove old spool files\&.
-
+%J - the job
+name as transmitted by the client.
-The print command is simply a text string\&. It will be used verbatim after macro substitutions have been made:
+%c - The number of printed pages
+of the spooled job (if known).
+%z - the size of the spooled
+print job (in bytes)
-%s, %p - the path to the spool file name
+The print command \fBMUST\fR contain at least
+one occurrence of \fI%s\fR or \fI%f
+\fR - the \fI%p\fR is optional. At the time
+a job is submitted, if no printer name is supplied the \fI%p
+\fR will be silently removed from the printer command.
+If specified in the [global] section, the print command given
+will be used for any printable service that does not have its own
+print command specified.
-%p - the appropriate printer name
+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 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.
-%J - the job name as transmitted by the client\&.
+You can form quite complex print commands by realizing
+that they are just passed to a shell. For example the following
+will log a print job, print the file, then remove it. Note that
+\&';' is the usual separator for command in shell scripts.
+\fBprint command = echo Printing %s >>
+/tmp/print.log; lpr -P %p %s; rm %s\fR
-%c - The number of printed pages of the spooled job (if known)\&.
-
-
-%z - the size of the spooled print job (in bytes)
-
-
-The print command \fBMUST\fR contain at least one occurrence of \fI%s\fR or \fI%f \fR - the \fI%p\fR is optional\&. At the time a job is submitted, if no printer name is supplied the \fI%p \fR will be silently removed from the printer command\&.
-
-
-If specified in the [global] section, the print command given will be used for any printable service that does not have its own print command specified\&.
-
-
-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 UNIXes from the \fBnobody\fR account\&. If this happens then create an alternative guest account that can print and set the \fIguest account\fR in the [global] section\&.
-
-
-You can form quite complex print commands by realizing that they are just passed to a shell\&. For example the following will log a print job, print the file, then remove it\&. Note that ';' is the usual separator for command in shell scripts\&.
-
-
-\fBprint command = echo Printing %s >> /tmp/print.log; lpr -P %p %s; rm %s\fR
-
-
-You may have to vary this command considerably depending on how you normally print files on your system\&. The default for the parameter varies depending on the setting of the \fIprinting\fR parameter\&.
-
-
-Default: For \fBprinting = BSD, AIX, QNX, LPRNG or PLP :\fR
+You may have to vary this command considerably depending
+on how you normally print files on your system. The default for
+the parameter varies depending on the setting of the \fIprinting\fR parameter.
+Default: For \fBprinting = BSD, AIX, QNX, LPRNG
+or PLP :\fR
\fBprint command = lpr -r -P%p %s\fR
-
For \fBprinting = SYSV or HPUX :\fR
-
\fBprint command = lp -c -d%p %s; rm %s\fR
-
For \fBprinting = SOFTQ :\fR
-
\fBprint command = lp -d%p -s %s; rm %s\fR
+For printing = CUPS : If SAMBA is compiled against
+libcups, then printcap = cups
+uses the CUPS API to
+submit jobs, etc. Otherwise it maps to the System V
+commands with the -oraw option for printing, i.e. it
+uses \fBlp -c -d%p -oraw; rm %s\fR.
+With \fBprinting = cups\fR,
+and if SAMBA is compiled against libcups, any manually
+set print command will be ignored.
+
+Example: \fBprint command = /usr/local/samba/bin/myprintscript
+%p %s\fR
+.TP
+\fBprint ok (S)\fR
+Synonym for \fIprintable\fR.
+.TP
+\fBprintable (S)\fR
+If this parameter is yes, then
+clients may open, write to and submit spool files on the directory
+specified for the service.
+
+Note that a printable service will ALWAYS allow writing
+to the service path (user privileges permitting) via the spooling
+of print data. The \fIread only
+\fR parameter controls only non-printing access to
+the resource.
-For printing = CUPS : If SAMBA is compiled against libcups, then printcap = cups uses the CUPS API to submit jobs, etc\&. Otherwise it maps to the System V commands with the -oraw option for printing, i\&.e\&. it uses \fBlp -c -d%p -oraw; rm %s\fR\&. With \fBprinting = cups\fR, and if SAMBA is compiled against libcups, any manually set print command will be ignored\&.
-
+Default: \fBprintable = no\fR
+.TP
+\fBprintcap (G)\fR
+Synonym for \fI printcap name\fR.
+.TP
+\fBprintcap name (G)\fR
+This parameter may be used to override the
+compiled-in default printcap name used by the server (usually \fI /etc/printcap\fR). See the discussion of the [printers] section above for reasons
+why you might want to do this.
+
+To use the CUPS printing interface set \fBprintcap name = cups
+\fR. This should be supplemented by an addtional setting
+printing = cups in the [global]
+section. \fBprintcap name = cups\fR will use the
+"dummy" printcap created by CUPS, as specified in your CUPS
+configuration file.
+
+On System V systems that use \fBlpstat\fR to
+list available printers you can use \fBprintcap name = lpstat
+\fR to automatically obtain lists of available printers. This
+is the default for systems that define SYSV at configure time in
+Samba (this includes most System V based systems). If \fI printcap name\fR is set to \fBlpstat\fR on
+these systems then Samba will launch \fBlpstat -v\fR and
+attempt to parse the output to obtain a printer list.
-Example: \fBprint command = /usr/local/samba/bin/myprintscript %p %s\fR
+A minimal printcap file would look something like this:
-.TP
-printer admin (S)
-This is a list of users that can do anything to printers via the remote administration interfaces offered by MS-RPC (usually using a NT workstation)\&. Note that the root user always has admin rights\&.
+.nf
+ print1|My Printer 1
+ print2|My Printer 2
+ print3|My Printer 3
+ print4|My Printer 4
+ print5|My Printer 5
+
+.fi
+where the '|' separates aliases of a printer. The fact
+that the second alias has a space in it gives a hint to Samba
+that it's a comment.
-Default: \fBprinter admin = <empty string>\fR
+\fBNOTE\fR: Under AIX the default printcap
+name is \fI/etc/qconfig\fR. Samba will assume the
+file is in AIX \fIqconfig\fR format if the string
+\fIqconfig\fR appears in the printcap filename.
+Default: \fBprintcap name = /etc/printcap\fR
-Example: \fBprinter admin = admin, @staff\fR
+Example: \fBprintcap name = /etc/myprintcap\fR
+.TP
+\fBprinter admin (S)\fR
+This is a list of users that can do anything to
+printers via the remote administration interfaces offered by MS-RPC
+(usually using a NT workstation). Note that the root user always
+has admin rights.
+Default: \fBprinter admin = <empty string>\fR
+Example: \fBprinter admin = admin, @staff\fR
.TP
-printer name (S)
-This parameter specifies the name of the printer to which print jobs spooled through a printable service will be sent\&.
-
+\fBprinter driver (S)\fR
+\fBNote :\fRThis is a deprecated
+parameter and will be removed in the next major release
+following version 2.2. Please see the instructions in
+the Samba 2.2. Printing
+HOWTO 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 Windows NT
+then you can use this to automate the setup of printers on your
+system.
+
+You need to set this parameter to the exact string (case
+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 scroll box after you have chosen the printer manufacturer.
+
+See also \fIprinter
+driver file\fR.
+
+Example: \fBprinter driver = HP LaserJet 4L\fR
+.TP
+\fBprinter driver file (G)\fR
+\fBNote :\fRThis is a deprecated
+parameter and will be removed in the next major release
+following version 2.2. Please see the instructions in
+the Samba 2.2. Printing
+HOWTO for more information
+on the new method of loading printer drivers onto a Samba server.
+
+This parameter tells Samba where the printer driver
+definition file, used when serving drivers to Windows 95 clients, is
+to be found. If this is not set, the default is :
+
+\fISAMBA_INSTALL_DIRECTORY
+/lib/printers.def\fR
+
+This file is created from Windows 95 \fImsprint.inf
+\fR files found on the Windows 95 client system. For more
+details on setting up serving of printer drivers to Windows 95
+clients, see the outdated documentation file in the \fIdocs/\fR
+directory, \fIPRINTER_DRIVER.txt\fR.
+
+See also \fI printer driver location\fR.
+
+Default: \fBNone (set in compile).\fR
+
+Example: \fBprinter driver file =
+/usr/local/samba/printers/drivers.def\fR
+.TP
+\fBprinter driver location (S)\fR
+\fBNote :\fRThis is a deprecated
+parameter and will be removed in the next major release
+following version 2.2. Please see the instructions in
+the Samba 2.2. Printing
+HOWTO for more information
+on the new method of loading printer drivers onto a Samba server.
+
+This parameter tells clients of a particular printer
+share where to find the printer driver files for the automatic
+installation of drivers for Windows 95 machines. If Samba is set up
+to serve printer drivers to Windows 95 machines, this should be set to
+
+\fB\\\\MACHINE\\PRINTER$\fR
+
+Where MACHINE is the NetBIOS name of your Samba server,
+and PRINTER$ is a share you set up for serving printer driver
+files. For more details on setting this up see the outdated documentation
+file in the \fIdocs/\fR directory, \fI PRINTER_DRIVER.txt\fR.
+
+See also \fI printer driver file\fR.
-If specified in the [global] section, the printer name given will be used for any printable service that does not have its own printer name specified\&.
+Default: \fBnone\fR
+Example: \fBprinter driver location = \\\\MACHINE\\PRINTER$
+\fR
+.TP
+\fBprinter name (S)\fR
+This parameter specifies the name of the printer
+to which print jobs spooled through a printable service will be sent.
-Default: \fBnone (but may be \fBlp\fR on many systems)\fR
+If specified in the [global] section, the printer
+name given will be used for any printable service that does
+not have its own printer name specified.
+Default: \fBnone (but may be lp
+on many systems)\fR
Example: \fBprinter name = laserwriter\fR
-
-
.TP
-printer (S)
-Synonym for \fI printer name\fR\&.
-
-
+\fBprinter (S)\fR
+Synonym for \fI printer name\fR.
.TP
-printing (S)
-This parameters controls how printer status information is interpreted on your system\&. It also affects the default values for the \fIprint command\fR, \fIlpq command\fR, \fIlppause command \fR, \fIlpresume command\fR, and \fIlprm command\fR if specified in the [global] section\&.
-
+\fBprinting (S)\fR
+This parameters controls how printer status
+information is interpreted on your system. It also affects the
+default values for the \fIprint command\fR,
+\fIlpq command\fR, \fIlppause command
+\fR, \fIlpresume command\fR, and
+\fIlprm command\fR if specified in the
+[global] section.
-Currently nine printing styles are supported\&. They are \fBBSD\fR, \fBAIX\fR, \fBLPRNG\fR, \fBPLP\fR, \fBSYSV\fR, \fBHPUX\fR, \fBQNX\fR, \fBSOFTQ\fR, and \fBCUPS\fR\&.
-
-
-To see what the defaults are for the other print commands when using the various options use the \fBtestparm\fR(1) program\&.
+Currently nine printing styles are supported. They are
+BSD, AIX,
+LPRNG, PLP,
+SYSV, HPUX,
+QNX, SOFTQ,
+and CUPS.
+To see what the defaults are for the other print
+commands when using the various options use the testparm(1) program.
This option can be set on a per printer basis
-
-See also the discussion in the [printers] section\&.
-
-
+See also the discussion in the [printers] section.
.TP
-print ok (S)
-Synonym for \fIprintable\fR\&.
-
-
-.TP
-private dir (G)
-This parameters defines the directory smbd will use for storing such files as \fIsmbpasswd\fR and \fIsecrets\&.tdb\fR\&.
-
+\fBprivate dir (G)\fR
+This parameters defines the directory
+smbd will use for storing such files as \fIsmbpasswd\fR
+and \fIsecrets.tdb\fR.
Default :\fBprivate dir = ${prefix}/private\fR
-
-
.TP
-protocol (G)
-Synonym for \fImax protocol\fR\&.
-
-
+\fBprotocol (G)\fR
+Synonym for \fImax protocol\fR.
.TP
-public (S)
-Synonym for \fIguest ok\fR\&.
-
-
+\fBpublic (S)\fR
+Synonym for \fIguest
+ok\fR.
.TP
-queuepause command (S)
-This parameter specifies the command to be executed on the server host in order to pause the printer queue\&.
-
+\fBqueuepause command (S)\fR
+This parameter specifies the command to be
+executed on the server host in order to pause the printer queue.
-This command should be a program or script which takes a printer name as its only parameter and stops the printer queue, such that no longer jobs are submitted to the printer\&.
+This command should be a program or script which takes
+a printer name as its only parameter and stops the printer queue,
+such that no longer jobs are submitted to the printer.
+This command is not supported by Windows for Workgroups,
+but can be issued from the Printers window under Windows 95
+and NT.
-This command is not supported by Windows for Workgroups, but can be issued from the Printers window under Windows 95 and NT\&.
+If a \fI%p\fR is given then the printer name
+is put in its place. Otherwise it is placed at the end of the command.
+Note that it is good practice to include the absolute
+path in the command as the PATH may not be available to the
+server.
-If a \fI%p\fR is given then the printer name is put in its place\&. Otherwise it is placed at the end of the command\&.
-
-
-Note that it is good practice to include the absolute path in the command as the PATH may not be available to the server\&.
-
-
-Default: \fBdepends on the setting of \fIprinting\fR\fR
-
+Default: \fBdepends on the setting of \fIprinting
+\fB\fR
Example: \fBqueuepause command = disable %p\fR
-
-
.TP
-queueresume command (S)
-This parameter specifies the command to be executed on the server host in order to resume the printer queue\&. It is the command to undo the behavior that is caused by the previous parameter (\fI queuepause command\fR)\&.
-
-
-This command should be a program or script which takes a printer name as its only parameter and resumes the printer queue, such that queued jobs are resubmitted to the printer\&.
-
-
-This command is not supported by Windows for Workgroups, but can be issued from the Printers window under Windows 95 and NT\&.
-
+\fBqueueresume command (S)\fR
+This parameter specifies the command to be
+executed on the server host in order to resume the printer queue. It
+is the command to undo the behavior that is caused by the
+previous parameter (\fI queuepause command\fR).
-If a \fI%p\fR is given then the printer name is put in its place\&. Otherwise it is placed at the end of the command\&.
+This command should be a program or script which takes
+a printer name as its only parameter and resumes the printer queue,
+such that queued jobs are resubmitted to the printer.
+This command is not supported by Windows for Workgroups,
+but can be issued from the Printers window under Windows 95
+and NT.
-Note that it is good practice to include the absolute path in the command as the PATH may not be available to the server\&.
+If a \fI%p\fR is given then the printer name
+is put in its place. Otherwise it is placed at the end of the
+command.
+Note that it is good practice to include the absolute
+path in the command as the PATH may not be available to the
+server.
-Default: \fBdepends on the setting of \fIprinting\fR\fR
-
-
-Example: \fBqueuepause command = enable %p\fR
-
+Default: \fBdepends on the setting of \fIprinting\fB\fR
+Example: \fBqueuepause command = enable %p
+\fR
.TP
-read bmpx (G)
-This boolean parameter controls whether \fBsmbd\fR(8) will support the "Read Block Multiplex" SMB\&. This is now rarely used and defaults to \fBno\fR\&. You should never need to set this parameter\&.
-
+\fBread bmpx (G)\fR
+This boolean parameter controls whether smbd(8) will support the "Read
+Block Multiplex" SMB. This is now rarely used and defaults to
+no. You should never need to set this
+parameter.
Default: \fBread bmpx = no\fR
-
-
.TP
-read list (S)
-This is a list of users that are given read-only access to a service\&. If the connecting user is in this list then they will not be given write access, no matter what the \fIread only\fR option is set to\&. The list can include group names using the syntax described in the \fI invalid users\fR parameter\&.
-
-
-See also the \fI write list\fR parameter and the \fIinvalid users\fR parameter\&.
+\fBread list (S)\fR
+This is a list of users that are given read-only
+access to a service. If the connecting user is in this list then
+they will not be given write access, no matter what the \fIread only\fR
+option is set to. The list can include group names using the
+syntax described in the \fI invalid users\fR parameter.
+See also the \fI write list\fR parameter and the \fIinvalid users\fR
+parameter.
Default: \fBread list = <empty string>\fR
-
Example: \fBread list = mary, @students\fR
-
-
.TP
-read only (S)
-An inverted synonym is \fIwriteable\fR\&.
-
+\fBread only (S)\fR
+An inverted synonym is \fIwriteable\fR.
-If this parameter is \fByes\fR, then users of a service may not create or modify files in the service's directory\&.
-
-
-Note that a printable service (\fBprintable = yes\fR) will \fBALWAYS\fR allow writing to the directory (user privileges permitting), but only via spooling operations\&.
+If this parameter is yes, then users
+of a service may not create or modify files in the service's
+directory.
+Note that a printable service (\fBprintable = yes\fR)
+will \fBALWAYS\fR allow writing to the directory
+(user privileges permitting), but only via spooling operations.
Default: \fBread only = yes\fR
-
-
.TP
-read raw (G)
-This parameter controls whether or not the server will support the raw read SMB requests when transferring data to clients\&.
-
-
-If enabled, raw reads allow reads of 65535 bytes in one packet\&. This typically provides a major performance benefit\&.
+\fBread raw (G)\fR
+This parameter controls whether or not the server
+will support the raw read SMB requests when transferring data
+to clients.
+If enabled, raw reads allow reads of 65535 bytes in
+one packet. This typically provides a major performance benefit.
-However, some clients either negotiate the allowable block size incorrectly or are incapable of supporting larger block sizes, and for these clients you may need to disable raw reads\&.
-
-
-In general this parameter should be viewed as a system tuning tool and left severely alone\&. See also \fIwrite raw\fR\&.
+However, some clients either negotiate the allowable
+block size incorrectly or are incapable of supporting larger block
+sizes, and for these clients you may need to disable raw reads.
+In general this parameter should be viewed as a system tuning
+tool and left severely alone. See also \fIwrite raw\fR.
Default: \fBread raw = yes\fR
-
-
.TP
-read size (G)
-The option \fIread size\fR affects the overlap of disk reads/writes with network reads/writes\&. If the amount of data being transferred in several of the SMB commands (currently SMBwrite, SMBwriteX and SMBreadbraw) is larger than this value then the server begins writing the data before it has received the whole packet from the network, or in the case of SMBreadbraw, it begins writing to the network before all the data has been read from disk\&.
-
-
-This overlapping works best when the speeds of disk and network access are similar, having very little effect when the speed of one is much greater than the other\&.
-
-
-The default value is 16384, but very little experimentation has been done yet to determine the optimal value, and it is likely that the best value will vary greatly between systems anyway\&. A value over 65536 is pointless and will cause you to allocate memory unnecessarily\&.
-
+\fBread size (G)\fR
+The option \fIread size\fR
+affects the overlap of disk reads/writes with network reads/writes.
+If the amount of data being transferred in several of the SMB
+commands (currently SMBwrite, SMBwriteX and SMBreadbraw) is larger
+than this value then the server begins writing the data before it
+has received the whole packet from the network, or in the case of
+SMBreadbraw, it begins writing to the network before all the data
+has been read from disk.
+
+This overlapping works best when the speeds of disk and
+network access are similar, having very little effect when the
+speed of one is much greater than the other.
+
+The default value is 16384, but very little experimentation
+has been done yet to determine the optimal value, and it is likely
+that the best value will vary greatly between systems anyway.
+A value over 65536 is pointless and will cause you to allocate
+memory unnecessarily.
Default: \fBread size = 16384\fR
-
Example: \fBread size = 8192\fR
-
-
.TP
-realm (G)
-This option specifies the kerberos realm to use\&. The realm is used as the ADS equivalent of the NT4 \fBdomain\fR\&. It is usually set to the DNS name of the kerberos server\&.
-
+\fBrealm (G)\fR
+This option specifies the kerberos realm to use. The realm is
+used as the ADS equivalent of the NT4\fBdomain\fR. It
+is usually set to the DNS name of the kerberos server.
Default: \fBrealm = \fR
-
Example: \fBrealm = mysambabox.mycompany.com\fR
-
-
.TP
-remote announce (G)
-This option allows you to setup \fBnmbd\fR(8)to periodically announce itself to arbitrary IP addresses with an arbitrary workgroup name\&.
-
-
-This is useful if you want your Samba server to appear in a remote workgroup for which the normal browse propagation rules don't work\&. The remote workgroup can be anywhere that you can send IP packets to\&.
+\fBremote announce (G)\fR
+This option allows you to setup nmbd(8) to periodically announce itself
+to arbitrary IP addresses with an arbitrary workgroup name.
+This is useful if you want your Samba server to appear
+in a remote workgroup for which the normal browse propagation
+rules don't work. The remote workgroup can be anywhere that you
+can send IP packets to.
For example:
+\fBremote announce = 192.168.2.255/SERVERS
+192.168.4.255/STAFF\fR
-\fBremote announce = 192.168.2.255/SERVERS 192.168.4.255/STAFF\fR
+the above line would cause \fBnmbd\fR to announce itself
+to the two given IP addresses using the given workgroup names.
+If you leave out the workgroup name then the one given in
+the \fIworkgroup\fR
+parameter is used instead.
+The IP addresses you choose would normally be the broadcast
+addresses of the remote networks, but can also be the IP addresses
+of known browse masters if your network config is that stable.
-the above line would cause \fBnmbd\fR to announce itself to the two given IP addresses using the given workgroup names\&. If you leave out the workgroup name then the one given in the \fIworkgroup\fR parameter is used instead\&.
-
-
-The IP addresses you choose would normally be the broadcast addresses of the remote networks, but can also be the IP addresses of known browse masters if your network config is that stable\&.
-
-
-See the documentation file BROWSING in the \fIdocs/\fR directory\&.
-
-
-Default: \fBremote announce = <empty string>\fR
-
+See the documentation file \fIBROWSING.txt\fR
+in the \fIdocs/\fR directory.
+Default: \fBremote announce = <empty string>
+\fR
.TP
-remote browse sync (G)
-This option allows you to setup \fBnmbd\fR(8) to periodically request synchronization of browse lists with the master browser of a Samba server that is on a remote segment\&. This option will allow you to gain browse lists for multiple workgroups across routed networks\&. This is done in a manner that does not work with any non-Samba servers\&.
-
-
-This is useful if you want your Samba server and all local clients to appear in a remote workgroup for which the normal browse propagation rules don't work\&. The remote workgroup can be anywhere that you can send IP packets to\&.
+\fBremote browse sync (G)\fR
+This option allows you to setup nmbd(8) to periodically request
+synchronization of browse lists with the master browser of a Samba
+server that is on a remote segment. This option will allow you to
+gain browse lists for multiple workgroups across routed networks. This
+is done in a manner that does not work with any non-Samba servers.
+This is useful if you want your Samba server and all local
+clients to appear in a remote workgroup for which the normal browse
+propagation rules don't work. The remote workgroup can be anywhere
+that you can send IP packets to.
For example:
+\fBremote browse sync = 192.168.2.255 192.168.4.255
+\fR
-\fBremote browse sync = 192.168.2.255 192.168.4.255\fR
-
-
-the above line would cause \fBnmbd\fR to request the master browser on the specified subnets or addresses to synchronize their browse lists with the local server\&.
-
-
-The IP addresses you choose would normally be the broadcast addresses of the remote networks, but can also be the IP addresses of known browse masters if your network config is that stable\&. If a machine IP address is given Samba makes NO attempt to validate that the remote machine is available, is listening, nor that it is in fact the browse master on its segment\&.
-
-
-Default: \fBremote browse sync = <empty string>\fR
+the above line would cause \fBnmbd\fR to request
+the master browser on the specified subnets or addresses to
+synchronize their browse lists with the local server.
+The IP addresses you choose would normally be the broadcast
+addresses of the remote networks, but can also be the IP addresses
+of known browse masters if your network config is that stable. If
+a machine IP address is given Samba makes NO attempt to validate
+that the remote machine is available, is listening, nor that it
+is in fact the browse master on its segment.
+Default: \fBremote browse sync = <empty string>
+\fR
.TP
-restrict anonymous (G)
-This is a integer parameter, and mirrors as much as possible the functinality the \fBRestrictAnonymous\fR registry key does on NT/Win2k\&.
-
+\fBrestrict anonymous (G)\fR
+This is a integer parameter, and
+mirrors as much as possible the functinality the
+RestrictAnonymous
+registry key does on NT/Win2k.
Default: \fBrestrict anonymous = 0\fR
-
-
.TP
-root directory (G)
-The server will \fBchroot()\fR (i\&.e\&. Change its root directory) to this directory on startup\&. This is not strictly necessary for secure operation\&. Even without it the server will deny access to files not in one of the service entries\&. It may also check for, and deny access to, soft links to other parts of the filesystem, or attempts to use "\&.\&." in file names to access other directories (depending on the setting of the \fIwide links\fR parameter)\&.
-
-
-Adding a \fIroot directory\fR entry other than "/" adds an extra level of security, but at a price\&. It absolutely ensures that no access is given to files not in the sub-tree specified in the \fIroot directory\fR option, \fBincluding\fR some files needed for complete operation of the server\&. To maintain full operability of the server you will need to mirror some system files into the \fIroot directory\fR tree\&. In particular you will need to mirror \fI/etc/passwd\fR (or a subset of it), and any binaries or configuration files needed for printing (if required)\&. The set of files that must be mirrored is operating system dependent\&.
-
+\fBroot (G)\fR
+Synonym for \fIroot directory"\fR.
+.TP
+\fBroot dir (G)\fR
+Synonym for \fIroot directory"\fR.
+.TP
+\fBroot directory (G)\fR
+The server will \fBchroot()\fR (i.e.
+Change its root directory) to this directory on startup. This is
+not strictly necessary for secure operation. Even without it the
+server will deny access to files not in one of the service entries.
+It may also check for, and deny access to, soft links to other
+parts of the filesystem, or attempts to use ".." in file names
+to access other directories (depending on the setting of the \fIwide links\fR
+parameter).
+
+Adding a \fIroot directory\fR entry other
+than "/" adds an extra level of security, but at a price. It
+absolutely ensures that no access is given to files not in the
+sub-tree specified in the \fIroot directory\fR
+option, \fBincluding\fR some files needed for
+complete operation of the server. To maintain full operability
+of the server you will need to mirror some system files
+into the \fIroot directory\fR tree. In particular
+you will need to mirror \fI/etc/passwd\fR (or a
+subset of it), and any binaries or configuration files needed for
+printing (if required). The set of files that must be mirrored is
+operating system dependent.
Default: \fBroot directory = /\fR
-
Example: \fBroot directory = /homes/smb\fR
-
-
.TP
-root dir (G)
-Synonym for \fIroot directory"\fR\&.
+\fBroot postexec (S)\fR
+This is the same as the \fIpostexec\fR
+parameter except that the command is run as root. This
+is useful for unmounting filesystems
+(such as CDROMs) after a connection is closed.
+See also \fI postexec\fR.
+Default: \fBroot postexec = <empty string>
+\fR
.TP
-root postexec (S)
-This is the same as the \fIpostexec\fR parameter except that the command is run as root\&. This is useful for unmounting filesystems (such as CDROMs) after a connection is closed\&.
-
-
-See also \fI postexec\fR\&.
-
-
-Default: \fBroot postexec = <empty string>\fR
+\fBroot preexec (S)\fR
+This is the same as the \fIpreexec\fR
+parameter except that the command is run as root. This
+is useful for mounting filesystems (such as CDROMs) when a
+connection is opened.
+See also \fI preexec\fR and \fIpreexec close\fR.
+Default: \fBroot preexec = <empty string>
+\fR
.TP
-root preexec close (S)
-This is the same as the \fIpreexec close \fR parameter except that the command is run as root\&.
-
-
-See also \fI preexec\fR and \fIpreexec close\fR\&.
+\fBroot preexec close (S)\fR
+This is the same as the \fIpreexec close
+\fR parameter except that the command is run as root.
+See also \fI preexec\fR and \fIpreexec close\fR.
Default: \fBroot preexec close = no\fR
-
-
-.TP
-root preexec (S)
-This is the same as the \fIpreexec\fR parameter except that the command is run as root\&. This is useful for mounting filesystems (such as CDROMs) when a connection is opened\&.
-
-
-See also \fI preexec\fR and \fIpreexec close\fR\&.
-
-
-Default: \fBroot preexec = <empty string>\fR
-
-
.TP
-root (G)
-Synonym for \fIroot directory"\fR\&.
-
-
-.TP
-security mask (S)
-This parameter controls what UNIX permission bits can be modified when a Windows NT client is manipulating the UNIX permission on a file using the native NT security dialog box\&.
-
-
-This parameter is applied as a mask (AND'ed with) to the changed permission bits, thus preventing any bits not in this mask from being modified\&. Essentially, zero bits in this mask may be treated as a set of bits the user is not allowed to change\&.
-
-
-If not set explicitly this parameter is 0777, allowing a user to modify all the user/group/world permissions on a file\&.
-
-
-\fBNote\fR that users who can access the Samba server through other means can easily bypass this restriction, so it is primarily useful for standalone "appliance" systems\&. Administrators of most normal systems will probably want to leave it set to \fB0777\fR\&.
-
-
-See also the \fIforce directory security mode\fR, \fIdirectory security mask\fR, \fIforce security mode\fR parameters\&.
-
-
-Default: \fBsecurity mask = 0777\fR
-
-
-Example: \fBsecurity mask = 0770\fR
-
-
-.TP
-security (G)
-This option affects how clients respond to Samba and is one of the most important settings in the \fI smb\&.conf\fR file\&.
-
-
-The option sets the "security mode bit" in replies to protocol negotiations with \fBsmbd\fR(8) to turn share level security on or off\&. Clients decide based on this bit whether (and how) to transfer user and password information to the server\&.
-
-
-The default is \fBsecurity = user\fR, as this is the most common setting needed when talking to Windows 98 and Windows NT\&.
-
-
-The alternatives are \fBsecurity = share\fR, \fBsecurity = server\fR or \fBsecurity = domain \fR\&.
-
-
-In versions of Samba prior to 2\&.0\&.0, the default was \fBsecurity = share\fR mainly because that was the only option at one stage\&.
-
-
-There is a bug in WfWg that has relevance to this setting\&. When in user or server level security a WfWg client will totally ignore the password you type in the "connect drive" dialog box\&. This makes it very difficult (if not impossible) to connect to a Samba service as anyone except the user that you are logged into WfWg as\&.
-
-
-If your PCs use usernames that are the same as their usernames on the UNIX machine then you will want to use \fBsecurity = user\fR\&. If you mostly use usernames that don't exist on the UNIX box then use \fBsecurity = share\fR\&.
-
-
-You should also use \fBsecurity = share\fR if you want to mainly setup shares without a password (guest shares)\&. This is commonly used for a shared printer server\&. It is more difficult to setup guest shares with \fBsecurity = user\fR, see the \fImap to guest\fR parameter for details\&.
-
-
-It is possible to use \fBsmbd\fR in a \fB hybrid mode\fR where it is offers both user and share level security under different \fINetBIOS aliases\fR\&.
-
-
-The different settings will now be explained\&.
-
-
-\fBSECURITY = SHARE\fR
-
-
-When clients connect to a share level security server they need not log onto the server with a valid username and password before attempting to connect to a shared resource (although modern clients such as Windows 95/98 and Windows NT will send a logon request with a username but no password when talking to a \fBsecurity = share \fR server)\&. Instead, the clients send authentication information (passwords) on a per-share basis, at the time they attempt to connect to that share\&.
-
-
-Note that \fBsmbd\fR \fBALWAYS\fR uses a valid UNIX user to act on behalf of the client, even in \fBsecurity = share\fR level security\&.
-
-
-As clients are not required to send a username to the server in share level security, \fBsmbd\fR uses several techniques to determine the correct UNIX user to use on behalf of the client\&.
-
-
-A list of possible UNIX usernames to match with the given client password is constructed using the following methods :
-
-
-If the \fIguest only\fR parameter is set, then all the other stages are missed and only the \fIguest account\fR username is checked\&.
-
-Is a username is sent with the share connection request, then this username (after mapping - see \fIusername map\fR), is added as a potential username\&.
-
-If the client did a previous \fBlogon \fR request (the SessionSetup SMB call) then the username sent in this SMB will be added as a potential username\&.
-
-The name of the service the client requested is added as a potential username\&.
-
-The NetBIOS name of the client is added to the list as a potential username\&.
-
-Any users on the \fI user\fR list are added as potential usernames\&.
-
-If the \fIguest only\fR parameter is not set, then this list is then tried with the supplied password\&. The first user for whom the password matches will be used as the UNIX user\&.
-
-
-If the \fIguest only\fR parameter is set, or no username can be determined then if the share is marked as available to the \fIguest account\fR, then this guest user will be used, otherwise access is denied\&.
-
-
-Note that it can be \fBvery\fR confusing in share-level security as to which UNIX username will eventually be used in granting access\&.
-
-
-See also the section NOTE ABOUT USERNAME/PASSWORD VALIDATION\&.
-
-
-\fBSECURITY = USER\fR
-
-
-This is the default security setting in Samba 3\&.0\&. With user-level security a client must first "log-on" with a valid username and password (which can be mapped using the \fIusername map\fR parameter)\&. Encrypted passwords (see the \fIencrypted passwords\fR parameter) can also be used in this security mode\&. Parameters such as \fIuser\fR and \fIguest only\fR if set are then applied and may change the UNIX user to use on this connection, but only after the user has been successfully authenticated\&.
-
-
-\fBNote\fR that the name of the resource being requested is \fBnot\fR sent to the server until after the server has successfully authenticated the client\&. This is why guest shares don't work in user level security without allowing the server to automatically map unknown users into the \fIguest account\fR\&. See the \fImap to guest\fR parameter for details on doing this\&.
-
-
-See also the section NOTE ABOUT USERNAME/PASSWORD VALIDATION\&.
-
-
-\fBSECURITY = DOMAIN\fR
-
-
-This mode will only work correctly if \fBnet\fR(8) has been used to add this machine into a Windows NT Domain\&. It expects the \fIencrypted passwords\fR parameter to be set to \fByes\fR\&. In this mode Samba will try to validate the username/password by passing it to a Windows NT Primary or Backup Domain Controller, in exactly the same way that a Windows NT Server would do\&.
-
-
-\fBNote\fR that a valid UNIX user must still exist as well as the account on the Domain Controller to allow Samba to have a valid UNIX account to map file access to\&.
-
-
-\fBNote\fR that from the client's point of view \fBsecurity = domain\fR is the same as \fBsecurity = user\fR\&. It only affects how the server deals with the authentication, it does not in any way affect what the client sees\&.
-
-
-\fBNote\fR that the name of the resource being requested is \fBnot\fR sent to the server until after the server has successfully authenticated the client\&. This is why guest shares don't work in user level security without allowing the server to automatically map unknown users into the \fIguest account\fR\&. See the \fImap to guest\fR parameter for details on doing this\&.
-
-
-See also the section NOTE ABOUT USERNAME/PASSWORD VALIDATION\&.
-
-
-See also the \fIpassword server\fR parameter and the \fIencrypted passwords\fR parameter\&.
-
-
-\fBSECURITY = SERVER\fR
-
-
-In this mode Samba will try to validate the username/password by passing it to another SMB server, such as an NT box\&. If this fails it will revert to \fBsecurity = user\fR\&. It expects the \fIencrypted passwords\fR parameter to be set to \fByes\fR, unless the remote server does not support them\&. However note that if encrypted passwords have been negotiated then Samba cannot revert back to checking the UNIX password file, it must have a valid \fIsmbpasswd\fR file to check users against\&. See the documentation file in the \fIdocs/\fR directory \fIENCRYPTION\&.txt\fR for details on how to set this up\&.
-
-
-\fBNote\fR this mode of operation has significant pitfalls, due to the fact that is activly initiates a man-in-the-middle attack on the remote SMB server\&. In particular, this mode of operation can cause significant resource consuption on the PDC, as it must maintain an active connection for the duration of the user's session\&. Furthermore, if this connection is lost, there is no way to reestablish it, and futher authenticaions to the Samba server may fail\&. (From a single client, till it disconnects)\&.
-
-
-\fBNote\fR that from the client's point of view \fBsecurity = server\fR is the same as \fBsecurity = user\fR\&. It only affects how the server deals with the authentication, it does not in any way affect what the client sees\&.
-
-
-\fBNote\fR that the name of the resource being requested is \fBnot\fR sent to the server until after the server has successfully authenticated the client\&. This is why guest shares don't work in user level security without allowing the server to automatically map unknown users into the \fIguest account\fR\&. See the \fImap to guest\fR parameter for details on doing this\&.
-
-
-See also the section NOTE ABOUT USERNAME/PASSWORD VALIDATION\&.
-
-
-See also the \fIpassword server\fR parameter and the \fIencrypted passwords\fR parameter\&.
+\fBsecurity (G)\fR
+This option affects how clients respond to
+Samba and is one of the most important settings in the \fI smb.conf\fR file.
+
+The option sets the "security mode bit" in replies to
+protocol negotiations with smbd(8)
+ to turn share level security on or off. Clients decide
+based on this bit whether (and how) to transfer user and password
+information to the server.
+
+The default is \fBsecurity = user\fR, as this is
+the most common setting needed when talking to Windows 98 and
+Windows NT.
+
+The alternatives are \fBsecurity = share\fR,
+\fBsecurity = server\fR or \fBsecurity = domain
+\fR.
+
+In versions of Samba prior to 2.0.0, the default was
+\fBsecurity = share\fR mainly because that was
+the only option at one stage.
+
+There is a bug in WfWg that has relevance to this
+setting. When in user or server level security a WfWg client
+will totally ignore the password you type in the "connect
+drive" dialog box. This makes it very difficult (if not impossible)
+to connect to a Samba service as anyone except the user that
+you are logged into WfWg as.
+
+If your PCs use usernames that are the same as their
+usernames on the UNIX machine then you will want to use
+\fBsecurity = user\fR. If you mostly use usernames
+that don't exist on the UNIX box then use \fBsecurity =
+share\fR.
+
+You should also use \fBsecurity = share\fR if you
+want to mainly setup shares without a password (guest shares). This
+is commonly used for a shared printer server. It is more difficult
+to setup guest shares with \fBsecurity = user\fR, see
+the \fImap to guest\fR
+parameter for details.
+
+It is possible to use \fBsmbd\fR in a \fB hybrid mode\fR where it is offers both user and share
+level security under different \fINetBIOS aliases\fR.
+
+The different settings will now be explained.
+
+\fBSECURITY = SHARE
+\fR
+
+When clients connect to a share level security server they
+need not log onto the server with a valid username and password before
+attempting to connect to a shared resource (although modern clients
+such as Windows 95/98 and Windows NT will send a logon request with
+a username but no password when talking to a \fBsecurity = share
+\fR server). Instead, the clients send authentication information
+(passwords) on a per-share basis, at the time they attempt to connect
+to that share.
+
+Note that \fBsmbd\fR \fBALWAYS\fR
+uses a valid UNIX user to act on behalf of the client, even in
+\fBsecurity = share\fR level security.
+
+As clients are not required to send a username to the server
+in share level security, \fBsmbd\fR uses several
+techniques to determine the correct UNIX user to use on behalf
+of the client.
+
+A list of possible UNIX usernames to match with the given
+client password is constructed using the following methods :
+.RS
+.TP 0.2i
+\(bu
+If the \fIguest
+only\fR parameter is set, then all the other
+stages are missed and only the \fIguest account\fR username is checked.
+.TP 0.2i
+\(bu
+Is a username is sent with the share connection
+request, then this username (after mapping - see \fIusername map\fR),
+is added as a potential username.
+.TP 0.2i
+\(bu
+If the client did a previous \fBlogon
+\fR request (the SessionSetup SMB call) then the
+username sent in this SMB will be added as a potential username.
+.TP 0.2i
+\(bu
+The name of the service the client requested is
+added as a potential username.
+.TP 0.2i
+\(bu
+The NetBIOS name of the client is added to
+the list as a potential username.
+.TP 0.2i
+\(bu
+Any users on the \fI user\fR list are added as potential usernames.
+.RE
+If the \fIguest only\fR parameter is
+not set, then this list is then tried with the supplied password.
+The first user for whom the password matches will be used as the
+UNIX user.
+
+If the \fIguest only\fR parameter is
+set, or no username can be determined then if the share is marked
+as available to the \fIguest account\fR, then this
+guest user will be used, otherwise access is denied.
+
+Note that it can be \fBvery\fR confusing
+in share-level security as to which UNIX username will eventually
+be used in granting access.
+
+See also the section NOTE ABOUT USERNAME/PASSWORD VALIDATION.
+
+\fBSECURITY = USER
+\fR
+
+This is the default security setting in Samba 2.2.
+With user-level security a client must first "log-on" with a
+valid username and password (which can be mapped using the \fIusername map\fR
+parameter). Encrypted passwords (see the \fIencrypted passwords\fR parameter) can also
+be used in this security mode. Parameters such as \fIuser\fR and \fIguest only\fR if set are then applied and
+may change the UNIX user to use on this connection, but only after
+the user has been successfully authenticated.
+
+\fBNote\fR that the name of the resource being
+requested is \fBnot\fR sent to the server until after
+the server has successfully authenticated the client. This is why
+guest shares don't work in user level security without allowing
+the server to automatically map unknown users into the \fIguest account\fR.
+See the \fImap to guest\fR
+parameter for details on doing this.
+
+See also the section NOTE ABOUT USERNAME/PASSWORD VALIDATION.
+
+\fBSECURITY = SERVER
+\fR
+
+In this mode Samba will try to validate the username/password
+by passing it to another SMB server, such as an NT box. If this
+fails it will revert to \fBsecurity = user\fR, but note
+that if encrypted passwords have been negotiated then Samba cannot
+revert back to checking the UNIX password file, it must have a valid
+\fIsmbpasswd\fR file to check users against. See the
+documentation file in the \fIdocs/\fR directory
+\fIENCRYPTION.txt\fR for details on how to set this
+up.
+
+\fBNote\fR that from the client's point of
+view \fBsecurity = server\fR is the same as \fB security = user\fR. It only affects how the server deals
+with the authentication, it does not in any way affect what the
+client sees.
+
+\fBNote\fR that the name of the resource being
+requested is \fBnot\fR sent to the server until after
+the server has successfully authenticated the client. This is why
+guest shares don't work in user level security without allowing
+the server to automatically map unknown users into the \fIguest account\fR.
+See the \fImap to guest\fR
+parameter for details on doing this.
+
+See also the section NOTE ABOUT USERNAME/PASSWORD VALIDATION.
+
+See also the \fIpassword
+server\fR parameter and the \fIencrypted passwords\fR
+parameter.
+
+\fBSECURITY = DOMAIN
+\fR
+
+This mode will only work correctly if smbpasswd(8) has been used to add this
+machine into a Windows NT Domain. It expects the \fIencrypted passwords\fR
+parameter to be set to yes. In this
+mode Samba will try to validate the username/password by passing
+it to a Windows NT Primary or Backup Domain Controller, in exactly
+the same way that a Windows NT Server would do.
+
+\fBNote\fR that a valid UNIX user must still
+exist as well as the account on the Domain Controller to allow
+Samba to have a valid UNIX account to map file access to.
+
+\fBNote\fR that from the client's point
+of view \fBsecurity = domain\fR is the same as \fBsecurity = user
+\fR. It only affects how the server deals with the authentication,
+it does not in any way affect what the client sees.
+
+\fBNote\fR that the name of the resource being
+requested is \fBnot\fR sent to the server until after
+the server has successfully authenticated the client. This is why
+guest shares don't work in user level security without allowing
+the server to automatically map unknown users into the \fIguest account\fR.
+See the \fImap to guest\fR
+parameter for details on doing this.
+
+\fBBUG:\fR There is currently a bug in the
+implementation of \fBsecurity = domain\fR with respect
+to multi-byte character set usernames. The communication with a
+Domain Controller must be done in UNICODE and Samba currently
+does not widen multi-byte user names to UNICODE correctly, thus
+a multi-byte username will not be recognized correctly at the
+Domain Controller. This issue will be addressed in a future release.
+
+See also the section NOTE ABOUT USERNAME/PASSWORD VALIDATION.
+
+See also the \fIpassword
+server\fR parameter and the \fIencrypted passwords\fR
+parameter.
Default: \fBsecurity = USER\fR
-
Example: \fBsecurity = DOMAIN\fR
-
-
.TP
-server schannel (G)
-This controls whether the server offers or even demands the use of the netlogon schannel\&. \fIserver schannel = no\fR does not offer the schannel, \fIserver schannel = auto\fR offers the schannel but does not enforce it, and \fIserver schannel = yes\fR denies access if the client is not able to speak netlogon schannel\&. This is only the case for Windows NT4 before SP4\&.
-
+\fBsecurity mask (S)\fR
+This parameter controls what UNIX permission
+bits can be modified when a Windows NT client is manipulating
+the UNIX permission on a file using the native NT security
+dialog box.
-Please note that with this set to \fIno\fR you will have to apply the WindowsXP requireSignOrSeal-Registry patch found in the docs/Registry subdirectory\&.
+This parameter is applied as a mask (AND'ed with) to
+the changed permission bits, thus preventing any bits not in
+this mask from being modified. Essentially, zero bits in this
+mask may be treated as a set of bits the user is not allowed
+to change.
+If not set explicitly this parameter is 0777, allowing
+a user to modify all the user/group/world permissions on a file.
-Default: \fBserver schannel = auto\fR
+\fBNote\fR that users who can access the
+Samba server through other means can easily bypass this
+restriction, so it is primarily useful for standalone
+"appliance" systems. Administrators of most normal systems will
+probably want to leave it set to 0777.
+See also the \fIforce directory security mode\fR,
+\fIdirectory
+security mask\fR, \fIforce security mode\fR parameters.
-Example: \fBserver schannel = yes\fR
-
+Default: \fBsecurity mask = 0777\fR
+Example: \fBsecurity mask = 0770\fR
.TP
-server string (G)
-This controls what string will show up in the printer comment box in print manager and next to the IPC connection in \fBnet view\fR\&. It can be any string that you wish to show to your users\&.
+\fBserver string (G)\fR
+This controls what string will show up in the
+printer comment box in print manager and next to the IPC connection
+in \fBnet view\fR. It can be any string that you wish
+to show to your users.
+It also sets what will appear in browse lists next
+to the machine name.
-It also sets what will appear in browse lists next to the machine name\&.
-
-
-A \fI%v\fR will be replaced with the Samba version number\&.
-
-
-A \fI%h\fR will be replaced with the hostname\&.
+A \fI%v\fR will be replaced with the Samba
+version number.
+A \fI%h\fR will be replaced with the
+hostname.
Default: \fBserver string = Samba %v\fR
-
-Example: \fBserver string = University of GNUs Samba Server\fR
-
-
+Example: \fBserver string = University of GNUs Samba
+Server\fR
.TP
-set directory (S)
-If \fBset directory = no\fR, then users of the service may not use the setdir command to change directory\&.
-
-
-The \fBsetdir\fR command is only implemented in the Digital Pathworks client\&. See the Pathworks documentation for details\&.
+\fBset directory (S)\fR
+If \fBset directory = no\fR, then
+users of the service may not use the setdir command to change
+directory.
+The \fBsetdir\fR command is only implemented
+in the Digital Pathworks client. See the Pathworks documentation
+for details.
Default: \fBset directory = no\fR
-
-
-.TP
-set primary group script (G)
-Thanks to the Posix subsystem in NT a Windows User has a primary group in addition to the auxiliary groups\&. This script sets the primary group in the unix userdatase when an administrator sets the primary group from the windows user manager or when fetching a SAM with \fBnet rpc vampire\fR\&. \fI%u\fR will be replaced with the user whose primary group is to be set\&. \fI%g\fR will be replaced with the group to set\&.
-
-
-Default: \fBNo default value\fR
-
-
-Example: \fBset primary group script = /usr/sbin/usermod -g '%g' '%u'\fR
-
-
.TP
-share modes (S)
-This enables or disables the honoring of the \fIshare modes\fR during a file open\&. These modes are used by clients to gain exclusive read or write access to a file\&.
-
-
-These open modes are not directly supported by UNIX, so they are simulated using shared memory, or lock files if your UNIX doesn't support shared memory (almost all do)\&.
-
-
-The share modes that are enabled by this option are \fBDENY_DOS\fR, \fBDENY_ALL\fR, \fBDENY_READ\fR, \fBDENY_WRITE\fR, \fBDENY_NONE\fR and \fBDENY_FCB\fR\&.
-
+\fBshare modes (S)\fR
+This enables or disables the honoring of
+the \fIshare modes\fR during a file open. These
+modes are used by clients to gain exclusive read or write access
+to a file.
-This option gives full share compatibility and enabled by default\&.
+These open modes are not directly supported by UNIX, so
+they are simulated using shared memory, or lock files if your
+UNIX doesn't support shared memory (almost all do).
+The share modes that are enabled by this option are
+DENY_DOS, DENY_ALL,
+DENY_READ, DENY_WRITE,
+DENY_NONE and DENY_FCB.
-You should \fBNEVER\fR turn this parameter off as many Windows applications will break if you do so\&.
+This option gives full share compatibility and enabled
+by default.
+You should \fBNEVER\fR turn this parameter
+off as many Windows applications will break if you do so.
Default: \fBshare modes = yes\fR
-
-
.TP
-short preserve case (S)
-This boolean parameter controls if new files which conform to 8\&.3 syntax, that is all in upper case and of suitable length, are created upper case, or if they are forced to be the \fIdefault case \fR\&. This option can be use with \fBpreserve case = yes\fR to permit long filenames to retain their case, while short names are lowered\&.
-
-
-See the section on NAME MANGLING\&.
+\fBshort preserve case (S)\fR
+This boolean parameter controls if new files
+which conform to 8.3 syntax, that is all in upper case and of
+suitable length, are created upper case, or if they are forced
+to be the \fIdefault case
+\fR. This option can be use with \fBpreserve case = yes\fR
+to permit long filenames to retain their case, while short
+names are lowered.
+See the section on NAME MANGLING.
Default: \fBshort preserve case = yes\fR
-
-
.TP
-show add printer wizard (G)
-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 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 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 client makes another open call with a request for 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 privilege on an individual printer\&.
-
-
-See also \fIaddprinter command\fR, \fIdeleteprinter command\fR, \fIprinter admin\fR
-
+\fBshow add printer wizard (G)\fR
+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 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 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 client makes another open call with a request for
+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 privilege on an individual printer.
+
+See also \fIaddprinter
+command\fR, \fIdeleteprinter command\fR, \fIprinter admin\fR
Default :\fBshow add printer wizard = yes\fR
-
-
.TP
-shutdown script (G)
-\fBThis parameter only exists in the HEAD cvs branch\fR This a full path name to a script called by \fBsmbd\fR(8) that should start a shutdown procedure\&.
-
-
-This command will be run as the user connected to the server\&.
-
+\fBshutdown script (G)\fR
+\fBThis parameter only exists in the HEAD cvs branch\fR
+This a full path name to a script called by
+\fBsmbd(8)\fR that
+should start a shutdown procedure.
-%m %t %r %f parameters are expanded:
+This command will be run as the user connected to the
+server.
+%m %t %r %f parameters are expanded
-\fI%m\fR will be substituted with the shutdown message sent to the server\&.
+\fI%m\fR will be substituted with the
+shutdown message sent to the server.
-\fI%t\fR will be substituted with the number of seconds to wait before effectively starting the shutdown procedure\&.
+\fI%t\fR will be substituted with the
+number of seconds to wait before effectively starting the
+shutdown procedure.
-\fI%r\fR will be substituted with the switch \fB-r\fR\&. It means reboot after shutdown for NT\&.
+\fI%r\fR will be substituted with the
+switch \fB-r\fR. It means reboot after shutdown
+for NT.
-\fI%f\fR will be substituted with the switch \fB-f\fR\&. It means force the shutdown even if applications do not respond for NT\&.
-
-Default: \fBNone\fR\&.
+\fI%f\fR will be substituted with the
+switch \fB-f\fR. It means force the shutdown
+even if applications do not respond for NT.
+Default: \fBNone\fR.
Example: \fBabort shutdown script = /usr/local/samba/sbin/shutdown %m %t %r %f\fR
-
Shutdown script example:
-.nf
-#!/bin/bash
+.nf
+ #!/bin/bash
-$time=0
-let "time/60"
-let "time++"
+ $time=0
+ let "time/60"
+ let "time++"
-/sbin/shutdown $3 $4 +$time $1 &
+ /sbin/shutdown $3 $4 +$time $1 &
+
.fi
+Shutdown does not return so we need to launch it in background.
-Shutdown does not return so we need to launch it in background\&.
-
-
-See also \fIabort shutdown script\fR\&.
-
-
+See also \fIabort shutdown script\fR.
.TP
-smb passwd file (G)
-This option sets the path to the encrypted smbpasswd file\&. By default the path to the smbpasswd file is compiled into Samba\&.
-
-
-Default: \fBsmb passwd file = ${prefix}/private/smbpasswd\fR
-
-
-Example: \fBsmb passwd file = /etc/samba/smbpasswd\fR
+\fBsmb passwd file (G)\fR
+This option sets the path to the encrypted
+smbpasswd file. By default the path to the smbpasswd file
+is compiled into Samba.
+Default: \fBsmb passwd file = ${prefix}/private/smbpasswd
+\fR
+Example: \fBsmb passwd file = /etc/samba/smbpasswd
+\fR
.TP
-smb ports (G)
-Specifies which ports the server should listen on for SMB traffic\&.
-
+\fBsmb ports (G)\fR
+Specifies which ports the server should listen on
+for SMB traffic.
Default: \fBsmb ports = 445 139\fR
-
-
.TP
-socket address (G)
-This option allows you to control what address Samba will listen for connections on\&. This is used to support multiple virtual interfaces on the one server, each with a different configuration\&.
-
-
-By default Samba will accept connections on any address\&.
+\fBsocket address (G)\fR
+This option allows you to control what
+address Samba will listen for connections on. This is used to
+support multiple virtual interfaces on the one server, each
+with a different configuration.
+By default Samba will accept connections on any
+address.
Example: \fBsocket address = 192.168.2.20\fR
-
-
.TP
-socket options (G)
-This option allows you to set socket options to be used when talking with the client\&.
-
-
-Socket options are controls on the networking layer of the operating systems which allow the connection to be tuned\&.
-
-
-This option will typically be used to tune your Samba server for optimal performance for your local network\&. There is no way that Samba can know what the optimal parameters are for your net, so you must experiment and choose them yourself\&. We strongly suggest you read the appropriate documentation for your operating system first (perhaps \fBman setsockopt\fR will help)\&.
-
-
-You may find that on some systems Samba will say "Unknown socket option" when you supply an option\&. This means you either incorrectly typed it or you need to add an include file to includes\&.h for your OS\&. If the latter is the case please send the patch to samba-technical@samba\&.org\&.
-
-
-Any of the supported socket options may be combined in any way you like, as long as your OS allows it\&.
-
-
-This is the list of socket options currently settable using this option:
-
-
+\fBsocket options (G)\fR
+This option allows you to set socket options
+to be used when talking with the client.
+
+Socket options are controls on the networking layer
+of the operating systems which allow the connection to be
+tuned.
+
+This option will typically be used to tune your Samba
+server for optimal performance for your local network. There is
+no way that Samba can know what the optimal parameters are for
+your net, so you must experiment and choose them yourself. We
+strongly suggest you read the appropriate documentation for your
+operating system first (perhaps \fBman setsockopt\fR
+will help).
+
+You may find that on some systems Samba will say
+"Unknown socket option" when you supply an option. This means you
+either incorrectly typed it or you need to add an include file
+to includes.h for your OS. If the latter is the case please
+send the patch to samba@samba.org <URL:mailto:samba@samba.org>.
+
+Any of the supported socket options may be combined
+in any way you like, as long as your OS allows it.
+
+This is the list of socket options currently settable
+using this option:
+.RS
+.TP 0.2i
+\(bu
SO_KEEPALIVE
-
+.TP 0.2i
+\(bu
SO_REUSEADDR
-
+.TP 0.2i
+\(bu
SO_BROADCAST
-
+.TP 0.2i
+\(bu
TCP_NODELAY
-
+.TP 0.2i
+\(bu
IPTOS_LOWDELAY
-
+.TP 0.2i
+\(bu
IPTOS_THROUGHPUT
-
+.TP 0.2i
+\(bu
SO_SNDBUF *
-
+.TP 0.2i
+\(bu
SO_RCVBUF *
-
+.TP 0.2i
+\(bu
SO_SNDLOWAT *
-
+.TP 0.2i
+\(bu
SO_RCVLOWAT *
+.RE
-Those marked with a \fB'*'\fR take an integer argument\&. The others can optionally take a 1 or 0 argument to enable or disable the option, by default they will be enabled if you don't specify 1 or 0\&.
-
-
-To specify an argument use the syntax SOME_OPTION = VALUE for example \fBSO_SNDBUF = 8192\fR\&. Note that you must not have any spaces before or after the = sign\&.
-
+Those marked with a \fB'*'\fR take an integer
+argument. The others can optionally take a 1 or 0 argument to enable
+or disable the option, by default they will be enabled if you
+don't specify 1 or 0.
-If you are on a local network then a sensible option might be:
+To specify an argument use the syntax SOME_OPTION = VALUE
+for example \fBSO_SNDBUF = 8192\fR. Note that you must
+not have any spaces before or after the = sign.
+If you are on a local network then a sensible option
+might be
\fBsocket options = IPTOS_LOWDELAY\fR
-
If you have a local network then you could try:
-
\fBsocket options = IPTOS_LOWDELAY TCP_NODELAY\fR
+If you are on a wide area network then perhaps try
+setting IPTOS_THROUGHPUT.
-If you are on a wide area network then perhaps try setting IPTOS_THROUGHPUT\&.
-
-
-Note that several of the options may cause your Samba server to fail completely\&. Use these options with caution!
-
+Note that several of the options may cause your Samba
+server to fail completely. Use these options with caution!
Default: \fBsocket options = TCP_NODELAY\fR
-
Example: \fBsocket options = IPTOS_LOWDELAY\fR
-
-
.TP
-source environment (G)
-This parameter causes Samba to set environment variables as per the content of the file named\&.
-
-
-If the value of this parameter starts with a "|" character then Samba will treat that value as a pipe command to open and will set the environment variables from the output of the pipe\&.
-
+\fBsource environment (G)\fR
+This parameter causes Samba to set environment
+variables as per the content of the file named.
-The contents of the file or the output of the pipe should be formatted as the output of the standard Unix \fBenv(1)\fR command\&. This is of the form:
+If the value of this parameter starts with a "|" character
+then Samba will treat that value as a pipe command to open and
+will set the environment variables from the output of the pipe.
+The contents of the file or the output of the pipe should
+be formatted as the output of the standard Unix \fBenv(1)
+\fR command. This is of the form :
Example environment entry:
-
\fBSAMBA_NETBIOS_NAME = myhostname\fR
-
Default: \fBNo default value\fR
+Examples: \fBsource environment = |/etc/smb.conf.sh
+\fR
-Examples: \fBsource environment = |/etc/smb.conf.sh\fR
-
-
-Example: \fBsource environment = /usr/local/smb_env_vars\fR
-
-
+Example: \fBsource environment =
+/usr/local/smb_env_vars\fR
.TP
-stat cache size (G)
-This parameter determines the number of entries in the \fIstat cache\fR\&. You should never need to change this parameter\&.
-
-
-Default: \fBstat cache size = 50\fR
-
+\fBuse spnego (G)\fR
+This variable controls controls whether samba will try to use Simple and Protected NEGOciation (as specified by rfc2478) with WindowsXP and Windows2000sp2 clients to agree upon an authentication mechanism. As of samba 3.0alpha it must be set to "no" for these clients to join a samba domain controller. It can be set to "yes" to allow samba to participate in an AD domain controlled by a Windows2000 domain controller.
+Default: \fBuse spnego = yes\fR
.TP
-stat cache (G)
-This parameter determines if \fBsmbd\fR(8) will use a cache in order to speed up case insensitive name mappings\&. You should never need to change this parameter\&.
-
+\fBstat cache (G)\fR
+This parameter determines if smbd(8) will use a cache in order to
+speed up case insensitive name mappings. You should never need
+to change this parameter.
Default: \fBstat cache = yes\fR
-
-
.TP
-strict allocate (S)
-This is a boolean that controls the handling of disk space allocation in the server\&. When this is set to \fByes\fR the server will change from UNIX behaviour of not committing real disk storage blocks when a file is extended to the Windows behaviour of actually forcing the disk system to allocate real storage blocks when a file is created or extended to be a given size\&. In UNIX terminology this means that Samba will stop creating sparse files\&. This can be slow on some systems\&.
-
-
-When strict allocate is \fBno\fR the server does sparse disk block allocation when a file is extended\&.
+\fBstat cache size (G)\fR
+This parameter determines the number of
+entries in the \fIstat cache\fR. You should
+never need to change this parameter.
+Default: \fBstat cache size = 50\fR
+.TP
+\fBstrict allocate (S)\fR
+This is a boolean that controls the handling of
+disk space allocation in the server. When this is set to yes
+the server will change from UNIX behaviour of not committing real
+disk storage blocks when a file is extended to the Windows behaviour
+of actually forcing the disk system to allocate real storage blocks
+when a file is created or extended to be a given size. In UNIX
+terminology this means that Samba will stop creating sparse files.
+This can be slow on some systems.
-Setting this to \fByes\fR can help Samba return out of quota messages on systems that are restricting the disk quota of users\&.
+When strict allocate is no the server does sparse
+disk block allocation when a file is extended.
+Setting this to yes can help Samba return
+out of quota messages on systems that are restricting the disk quota
+of users.
Default: \fBstrict allocate = no\fR
-
-
.TP
-strict locking (S)
-This is a boolean that controls the handling of file locking in the server\&. When this is set to \fByes\fR the server will check every read and write access for file locks, and deny access if locks exist\&. This can be slow on some systems\&.
-
-
-When strict locking is \fBno\fR the server does file lock checks only when the client explicitly asks for them\&.
+\fBstrict locking (S)\fR
+This is a boolean that controls the handling of
+file locking in the server. When this is set to yes
+the server will check every read and write access for file locks, and
+deny access if locks exist. This can be slow on some systems.
+When strict locking is no the server does file
+lock checks only when the client explicitly asks for them.
-Well-behaved clients always ask for lock checks when it is important, so in the vast majority of cases \fBstrict locking = no\fR is preferable\&.
-
+Well-behaved clients always ask for lock checks when it
+is important, so in the vast majority of cases \fBstrict
+locking = no\fR is preferable.
Default: \fBstrict locking = no\fR
-
-
.TP
-strict sync (S)
-Many Windows applications (including the Windows 98 explorer shell) seem to confuse flushing buffer contents to disk with doing a sync to disk\&. Under UNIX, a sync call forces the process to be suspended until the kernel has ensured that all outstanding data in kernel disk buffers has been safely stored onto stable storage\&. This is very slow and should only be done rarely\&. Setting this parameter to \fBno\fR (the default) means that \fBsmbd\fR(8) ignores the Windows applications requests for a sync call\&. There is only a possibility of losing data if the operating system itself that Samba is running on crashes, so there is little danger in this default setting\&. In addition, this fixes many performance problems that people have reported with the new Windows98 explorer shell file copies\&.
-
-
-See also the \fIsync always\fR parameter\&.
-
+\fBstrict sync (S)\fR
+Many Windows applications (including the Windows
+98 explorer shell) seem to confuse flushing buffer contents to
+disk with doing a sync to disk. Under UNIX, a sync call forces
+the process to be suspended until the kernel has ensured that
+all outstanding data in kernel disk buffers has been safely stored
+onto stable storage. This is very slow and should only be done
+rarely. Setting this parameter to no (the
+default) means that smbd ignores the Windows applications requests for
+a sync call. There is only a possibility of losing data if the
+operating system itself that Samba is running on crashes, so there is
+little danger in this default setting. In addition, this fixes many
+performance problems that people have reported with the new Windows98
+explorer shell file copies.
+
+See also the \fIsync
+always>\fR parameter.
Default: \fBstrict sync = no\fR
-
-
.TP
-strip dot (G)
-This is a boolean that controls whether to strip trailing dots off UNIX filenames\&. This helps with some CDROMs that have filenames ending in a single dot\&.
-
+\fBstrip dot (G)\fR
+This is a boolean that controls whether to
+strip trailing dots off UNIX filenames. This helps with some
+CDROMs that have filenames ending in a single dot.
Default: \fBstrip dot = no\fR
-
-
.TP
-sync always (S)
-This is a boolean parameter that controls whether writes will always be written to stable storage before the write call returns\&. If this is \fBno\fR then the server will be guided by the client's request in each write call (clients can set a bit indicating that a particular write should be synchronous)\&. If this is \fByes\fR then every write will be followed by a \fBfsync() \fR call to ensure the data is written to disk\&. Note that the \fIstrict sync\fR parameter must be set to \fByes\fR in order for this parameter to have any affect\&.
-
-
-See also the \fIstrict sync\fR parameter\&.
-
+\fBsync always (S)\fR
+This is a boolean parameter that controls
+whether writes will always be written to stable storage before
+the write call returns. If this is no then the server will be
+guided by the client's request in each write call (clients can
+set a bit indicating that a particular write should be synchronous).
+If this is yes then every write will be followed by a \fBfsync()
+\fR call to ensure the data is written to disk. Note that
+the \fIstrict sync\fR parameter must be set to
+yes in order for this parameter to have
+any affect.
+
+See also the \fIstrict
+sync\fR parameter.
Default: \fBsync always = no\fR
-
-
-.TP
-syslog only (G)
-If this parameter is set then Samba debug messages are logged into the system syslog only, and not to the debug log files\&.
-
-
-Default: \fBsyslog only = no\fR
-
-
.TP
-syslog (G)
-This parameter maps how Samba debug messages are logged onto the system syslog logging levels\&. Samba debug level zero maps onto syslog \fBLOG_ERR\fR, debug level one maps onto \fBLOG_WARNING\fR, debug level two maps onto \fBLOG_NOTICE\fR, debug level three maps onto LOG_INFO\&. All higher levels are mapped to \fB LOG_DEBUG\fR\&.
-
-
-This parameter sets the threshold for sending messages to syslog\&. Only messages with debug level less than this value will be sent to syslog\&.
+\fBsyslog (G)\fR
+This parameter maps how Samba debug messages
+are logged onto the system syslog logging levels. Samba debug
+level zero maps onto syslog LOG_ERR, debug
+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 parameter sets the threshold for sending messages
+to syslog. Only messages with debug level less than this value
+will be sent to syslog.
Default: \fBsyslog = 1\fR
-
-
.TP
-template homedir (G)
-When filling out the user information for a Windows NT user, the \fBwinbindd\fR(8) daemon uses this parameter to fill in the home directory for that user\&. If the string \fI%D\fR is present it is substituted with the user's Windows NT domain name\&. If the string \fI%U\fR is present it is substituted with the user's Windows NT user name\&.
+\fBsyslog only (G)\fR
+If this parameter is set then Samba debug
+messages are logged into the system syslog only, and not to
+the debug log files.
+Default: \fBsyslog only = no\fR
+.TP
+\fBtemplate homedir (G)\fR
+When filling out the user information for a Windows NT
+user, the winbindd(8) daemon
+uses this parameter to fill in the home directory for that user.
+If the string \fI%D\fR is present it is substituted
+with the user's Windows NT domain name. If the string \fI%U
+\fR is present it is substituted with the user's Windows
+NT user name.
Default: \fBtemplate homedir = /home/%D/%U\fR
-
-
.TP
-template shell (G)
-When filling out the user information for a Windows NT user, the \fBwinbindd\fR(8) daemon uses this parameter to fill in the login shell for that user\&.
-
+\fBtemplate shell (G)\fR
+When filling out the user information for a Windows NT
+user, the winbindd(8) daemon
+uses this parameter to fill in the login shell for that user.
Default: \fBtemplate shell = /bin/false\fR
-
-
.TP
-time offset (G)
-This parameter is a setting in minutes to add to the normal GMT to local time conversion\&. This is useful if you are serving a lot of PCs that have incorrect daylight saving time handling\&.
-
+\fBtime offset (G)\fR
+This parameter is a setting in minutes to add
+to the normal GMT to local time conversion. This is useful if
+you are serving a lot of PCs that have incorrect daylight
+saving time handling.
Default: \fBtime offset = 0\fR
-
Example: \fBtime offset = 60\fR
-
-
.TP
-time server (G)
-This parameter determines if \fBnmbd\fR(8) advertises itself as a time server to Windows clients\&.
-
+\fBtime server (G)\fR
+This parameter determines if
+nmbd(8) advertises itself as a time server to Windows
+clients.
Default: \fBtime server = no\fR
-
-
.TP
-timestamp logs (G)
-Synonym for \fI debug timestamp\fR\&.
-
-
+\fBtimestamp logs (G)\fR
+Synonym for \fI debug timestamp\fR.
.TP
-total print jobs (G)
-This parameter accepts an integer value which defines a limit on the maximum number of print jobs that will be accepted system wide at any given time\&. If a print job is submitted by a client which will exceed this number, then \fBsmbd\fR(8) will return an error indicating that no space is available on the server\&. The default value of 0 means that no such limit exists\&. This parameter can be used to prevent a server from exceeding its capacity and is designed as a printing throttle\&. See also \fImax print jobs\fR\&.
-
+\fBtotal print jobs (G)\fR
+This parameter accepts an integer value which defines
+a limit on the maximum number of print jobs that will be accepted
+system wide at any given time. If a print job is submitted
+by a client which will exceed this number, then smbd will return an
+error indicating that no space is available on the server. The
+default value of 0 means that no such limit exists. This parameter
+can be used to prevent a server from exceeding its capacity and is
+designed as a printing throttle. See also
+\fImax print jobs\fR.
Default: \fBtotal print jobs = 0\fR
-
Example: \fBtotal print jobs = 5000\fR
-
-
.TP
-unicode (G)
-Specifies whether Samba should try to use unicode on the wire by default\&. Note: This does NOT mean that samba will assume that the unix machine uses unicode!
-
+\fBunicode (G)\fR
+Specifies whether Samba should try
+to use unicode on the wire by default. Note: This does NOT
+mean that samba will assume that the unix machine uses unicode!
Default: \fBunicode = yes\fR
-
-
.TP
-unix charset (G)
-Specifies the charset the unix machine Samba runs on uses\&. Samba needs to know this in order to be able to convert text to the charsets other SMB clients use\&.
-
-
-Default: \fBunix charset = UTF8\fR
-
-
-Example: \fBunix charset = ASCII\fR
+\fBunix charset (G)\fR
+Specifies the charset the unix machine
+Samba runs on uses. Samba needs to know this in order to be able to
+convert text to the charsets other SMB clients use.
+Default: \fBunix charset = ASCII\fR
+Example: \fBunix charset = UTF8\fR
.TP
-unix extensions (G)
-This boolean parameter controls whether Samba implments the CIFS UNIX extensions, as defined by HP\&. These extensions enable Samba to better serve UNIX CIFS clients by supporting features such as symbolic links, hard links, etc\&.\&.\&. These extensions require a similarly enabled client, and are of no current use to Windows clients\&.
-
+\fBunix extensions(G)\fR
+This boolean parameter controls whether Samba
+implments the CIFS UNIX extensions, as defined by HP.
+These extensions enable Samba to better serve UNIX CIFS clients
+by supporting features such as symbolic links, hard links, etc...
+These extensions require a similarly enabled client, and are of
+no current use to Windows clients.
Default: \fBunix extensions = no\fR
-
-
.TP
-unix password sync (G)
-This boolean parameter controls whether Samba attempts to synchronize the UNIX password with the SMB password when the encrypted SMB password in the smbpasswd file is changed\&. If this is set to \fByes\fR the program specified in the \fIpasswd program\fRparameter is called \fBAS ROOT\fR - to allow the new UNIX password to be set without access to the old UNIX password (as the SMB password change code has no access to the old password cleartext, only the new)\&.
-
-
-See also \fIpasswd program\fR, \fI passwd chat\fR\&.
+\fBunix password sync (G)\fR
+This boolean parameter controls whether Samba
+attempts to synchronize the UNIX password with the SMB password
+when the encrypted SMB password in the smbpasswd file is changed.
+If this is set to yes the program specified in the \fIpasswd
+program\fRparameter is called \fBAS ROOT\fR -
+to allow the new UNIX password to be set without access to the
+old UNIX password (as the SMB password change code has no
+access to the old password cleartext, only the new).
+See also \fIpasswd
+program\fR, \fI passwd chat\fR.
Default: \fBunix password sync = no\fR
-
-
.TP
-update encrypted (G)
-This boolean parameter allows a user logging on with a plaintext password to have their encrypted (hashed) password in the smbpasswd file to be updated automatically as they log on\&. This option allows a site to migrate from plaintext password authentication (users authenticate with plaintext password over the wire, and are checked against a UNIX account database) to encrypted password authentication (the SMB challenge/response authentication mechanism) without forcing all users to re-enter their passwords via smbpasswd at the time the change is made\&. This is a convenience option to allow the change over to encrypted passwords to be made over a longer period\&. Once all users have encrypted representations of their passwords in the smbpasswd file this parameter should be set to \fBno\fR\&.
-
-
-In order for this parameter to work correctly the \fIencrypt passwords\fR parameter must be set to \fBno\fR when this parameter is set to \fByes\fR\&.
-
-
-Note that even when this parameter is set a user authenticating to \fBsmbd\fR must still enter a valid password in order to connect correctly, and to update their hashed (smbpasswd) passwords\&.
-
+\fBupdate encrypted (G)\fR
+This boolean parameter allows a user logging
+on with a plaintext password to have their encrypted (hashed)
+password in the smbpasswd file to be updated automatically as
+they log on. This option allows a site to migrate from plaintext
+password authentication (users authenticate with plaintext
+password over the wire, and are checked against a UNIX account
+database) to encrypted password authentication (the SMB
+challenge/response authentication mechanism) without forcing
+all users to re-enter their passwords via smbpasswd at the time the
+change is made. This is a convenience option to allow the change over
+to encrypted passwords to be made over a longer period. Once all users
+have encrypted representations of their passwords in the smbpasswd
+file this parameter should be set to no.
+
+In order for this parameter to work correctly the \fIencrypt passwords\fR
+parameter must be set to no when
+this parameter is set to yes.
+
+Note that even when this parameter is set a user
+authenticating to \fBsmbd\fR must still enter a valid
+password in order to connect correctly, and to update their hashed
+(smbpasswd) passwords.
Default: \fBupdate encrypted = no\fR
-
-
.TP
-use client driver (S)
-This parameter applies only to Windows NT/2000 clients\&. It has no affect on Windows 95/98/ME clients\&. When serving a printer to Windows NT/2000 clients without first installing a valid printer driver on the Samba host, the client will be required to install a local printer driver\&. From this point on, the client will treat the print as a local printer and not a network printer connection\&. This is much the same behavior that will occur when \fBdisable spoolss = yes\fR\&.
-
-
-The differentiating factor is that under normal circumstances, the NT/2000 client will attempt to open the network printer using MS-RPC\&. The problem is that because the client considers the printer to be local, it will attempt to issue the OpenPrinterEx() call requesting access rights associated with the logged on user\&. If the user possesses local administator rights but not root privilegde on the Samba host (often the case), the OpenPrinterEx() call will fail\&. The result is that the client will now display an "Access Denied; Unable to connect" message in the printer queue window (even though jobs may successfully be printed)\&.
-
-
-If this parameter is enabled for a printer, then any attempt to open the printer with the PRINTER_ACCESS_ADMINISTER right is mapped to PRINTER_ACCESS_USE instead\&. Thus allowing the OpenPrinterEx() call to succeed\&. \fBThis parameter MUST not be able enabled on a print share which has valid print driver installed on the Samba server\&.\fR
-
-
-See also \fIdisable spoolss\fR
-
+\fBuse client driver (S)\fR
+This parameter applies only to Windows NT/2000
+clients. It has no affect on Windows 95/98/ME clients. When
+serving a printer to Windows NT/2000 clients without first installing
+a valid printer driver on the Samba host, the client will be required
+to install a local printer driver. From this point on, the client
+will treat the print as a local printer and not a network printer
+connection. This is much the same behavior that will occur
+when \fBdisable spoolss = yes\fR.
+
+The differentiating
+factor is that under normal circumstances, the NT/2000 client will
+attempt to open the network printer using MS-RPC. The problem is that
+because the client considers the printer to be local, it will attempt
+to issue the OpenPrinterEx() call requesting access rights associated
+with the logged on user. If the user possesses local administator rights
+but not root privilegde on the Samba host (often the case), the OpenPrinterEx()
+call will fail. The result is that the client will now display an "Access
+Denied; Unable to connect" message in the printer queue window (even though
+jobs may successfully be printed).
+
+If this parameter is enabled for a printer, then any attempt
+to open the printer with the PRINTER_ACCESS_ADMINISTER right is mapped
+to PRINTER_ACCESS_USE instead. Thus allowing the OpenPrinterEx()
+call to succeed. \fBThis parameter MUST not be able enabled
+on a print share which has valid print driver installed on the Samba
+server.\fR
+
+See also disable spoolss
Default: \fBuse client driver = no\fR
-
-
.TP
-use mmap (G)
-This global parameter determines if the tdb internals of Samba can depend on mmap working correctly on the running system\&. Samba requires a coherent mmap/read-write system memory cache\&. Currently only HPUX does not have such a coherent cache, and so this parameter is set to \fBno\fR by default on HPUX\&. On all other systems this parameter should be left alone\&. This parameter is provided to help the Samba developers track down problems with the tdb internal code\&.
-
+\fBuse mmap (G)\fR
+This global parameter determines if the tdb internals of Samba can
+depend on mmap working correctly on the running system. Samba requires a coherent
+mmap/read-write system memory cache. Currently only HPUX does not have such a
+coherent cache, and so this parameter is set to no by
+default on HPUX. On all other systems this parameter should be left alone. This
+parameter is provided to help the Samba developers track down problems with
+the tdb internal code.
Default: \fBuse mmap = yes\fR
-
-
.TP
-username level (G)
-This option helps Samba to try and 'guess' at the real UNIX username, as many DOS clients send an all-uppercase username\&. By default Samba tries all lowercase, followed by the username with the first letter capitalized, and fails if the 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 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 \fBAstrangeUser \fR\&.
-
+\fBuse rhosts (G)\fR
+If this global parameter is yes, it specifies
+that the UNIX user's \fI.rhosts\fR file in their home directory
+will be read to find the names of hosts and users who will be allowed
+access without specifying a password.
+
+\fBNOTE:\fR The use of \fIuse rhosts
+\fR can be a major security hole. This is because you are
+trusting the PC to supply the correct username. It is very easy to
+get a PC to supply a false username. I recommend that the \fI use rhosts\fR option be only used if you really know what
+you are doing.
+
+Default: \fBuse rhosts = no\fR
+.TP
+\fBuser (S)\fR
+Synonym for \fI username\fR.
+.TP
+\fBusers (S)\fR
+Synonym for \fI username\fR.
+.TP
+\fBusername (S)\fR
+Multiple users may be specified in a comma-delimited
+list, in which case the supplied password will be tested against
+each username in turn (left to right).
+
+The \fIusername\fR line is needed only when
+the PC is unable to supply its own username. This is the case
+for the COREPLUS protocol or where your users have different WfWg
+usernames to UNIX usernames. In both these cases you may also be
+better using the \\\\server\\share%user syntax instead.
+
+The \fIusername\fR line is not a great
+solution in many cases as it means Samba will try to validate
+the supplied password against each of the usernames in the
+\fIusername\fR line in turn. This is slow and
+a bad idea for lots of users in case of duplicate passwords.
+You may get timeouts or security breaches using this parameter
+unwisely.
+
+Samba relies on the underlying UNIX security. This
+parameter does not restrict who can login, it just offers hints
+to the Samba server as to what usernames might correspond to the
+supplied password. Users can login as whoever they please and
+they will be able to do no more damage than if they started a
+telnet session. The daemon runs as the user that they log in as,
+so they cannot do anything that user cannot do.
+
+To restrict a service to a particular set of users you
+can use the \fIvalid users
+\fR parameter.
+
+If any of the usernames begin with a '@' then the name
+will be looked up first in the NIS netgroups list (if Samba
+is compiled with netgroup support), followed by a lookup in
+the UNIX groups database and will expand to a list of all users
+in the group of that name.
+
+If any of the usernames begin with a '+' then the name
+will be looked up only in the UNIX groups database and will
+expand to a list of all users in the group of that name.
+
+If any of the usernames begin with a '&'then the name
+will be looked up only in the NIS netgroups database (if Samba
+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, and some clients may time out during the
+search.
+
+See the section NOTE ABOUT
+USERNAME/PASSWORD VALIDATION for more information on how
+this parameter determines access to the services.
+
+Default: \fBThe guest account if a guest service,
+else <empty string>.\fR
+
+Examples:\fBusername = fred, mary, jack, jane,
+@users, @pcgroup\fR
+.TP
+\fBusername level (G)\fR
+This option helps Samba to try and 'guess' at
+the real UNIX username, as many DOS clients send an all-uppercase
+username. By default Samba tries all lowercase, followed by the
+username with the first letter capitalized, and fails if the
+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 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
+\&.
Default: \fBusername level = 0\fR
-
Example: \fBusername level = 5\fR
-
-
.TP
-username map (G)
-This option allows you to specify a file containing a mapping of usernames from the clients to the server\&. This can be used for several purposes\&. The most common is to map usernames that users use on DOS or Windows machines to those that the UNIX box uses\&. The other is to map multiple users to a single username so that they can more easily share files\&.
-
-
-The map file is parsed line by line\&. Each line should contain a single UNIX username on the left then a '=' followed by a list of usernames on the right\&. The list of usernames on the right may contain names of the form @group in which case they will match any UNIX username in that group\&. The special client name '*' is a wildcard and matches any name\&. Each line of the map file may be up to 1023 characters long\&.
-
-
-The file is processed on each line by taking the supplied username and comparing it with each username on the right hand side of the '=' signs\&. If the supplied name matches any of the names on the right hand side then it is replaced with the name on the left\&. Processing then continues with the next line\&.
-
-
-If any line begins with a '#' or a ';' then it is ignored
-
-
-If any line begins with an '!' then the processing will stop after that line if a mapping was done by the line\&. Otherwise mapping continues with every line being processed\&. Using '!' is most useful when you have a wildcard mapping line later in the file\&.
-
-
-For example to map from the name \fBadmin\fR or \fBadministrator\fR to the UNIX name \fB root\fR you would use:
-
+\fBusername map (G)\fR
+This option allows you to specify a file containing
+a mapping of usernames from the clients to the server. This can be
+used for several purposes. The most common is to map usernames
+that users use on DOS or Windows machines to those that the UNIX
+box uses. The other is to map multiple users to a single username
+so that they can more easily share files.
+
+The map file is parsed line by line. Each line should
+contain a single UNIX username on the left then a '=' followed
+by a list of usernames on the right. The list of usernames on the
+right may contain names of the form @group in which case they
+will match any UNIX username in that group. The special client
+name '*' is a wildcard and matches any name. Each line of the
+map file may be up to 1023 characters long.
+
+The file is processed on each line by taking the
+supplied username and comparing it with each username on the right
+hand side of the '=' signs. If the supplied name matches any of
+the names on the right hand side then it is replaced with the name
+on the left. Processing then continues with the next line.
+
+If any line begins with a '#' or a ';' then it is
+ignored
+
+If any line begins with an '!' then the processing
+will stop after that line if a mapping was done by the line.
+Otherwise mapping continues with every line being processed.
+Using '!' is most useful when you have a wildcard mapping line
+later in the file.
+
+For example to map from the name admin
+or administrator to the UNIX name root you would use:
\fBroot = admin administrator\fR
-
-Or to map anyone in the UNIX group \fBsystem\fR to the UNIX name \fBsys\fR you would use:
-
+Or to map anyone in the UNIX group system
+to the UNIX name sys you would use:
\fBsys = @system\fR
+You can have as many mappings as you like in a username
+map file.
-You can have as many mappings as you like in a username map file\&.
-
-
-If your system supports the NIS NETGROUP option then the netgroup database is checked before the \fI/etc/group \fR database for matching groups\&.
-
-
-You can map Windows usernames that have spaces in them by using double quotes around the name\&. For example:
+If your system supports the NIS NETGROUP option then
+the netgroup database is checked before the \fI/etc/group
+\fR database for matching groups.
+You can map Windows usernames that have spaces in them
+by using double quotes around the name. For example:
\fBtridge = "Andrew Tridgell"\fR
+would map the windows username "Andrew Tridgell" to the
+unix username "tridge".
-would map the windows username "Andrew Tridgell" to the unix username "tridge"\&.
-
-
-The following example would map mary and fred to the unix user sys, and map the rest to guest\&. Note the use of the '!' to tell Samba to stop processing if it gets a match on that line\&.
+The following example would map mary and fred to the
+unix user sys, and map the rest to guest. Note the use of the
+\&'!' to tell Samba to stop processing if it gets a match on
+that line.
.nf
-
-!sys = mary fred
-guest = *
+ !sys = mary fred
+ guest = *
+
.fi
+Note that the remapping is applied to all occurrences
+of usernames. Thus if you connect to \\\\server\\fred and fred is remapped to mary then you
+will actually be connecting to \\\\server\\mary and will need to
+supply a password suitable for mary not
+fred. The only exception to this is the
+username passed to the \fI password server\fR (if you have one). The password
+server will receive whatever username the client supplies without
+modification.
-Note that the remapping is applied to all occurrences of usernames\&. Thus if you connect to \\\\server\\fred and \fB fred\fR is remapped to \fBmary\fR then you will actually be connecting to \\\\server\\mary and will need to supply a password suitable for \fBmary\fR not \fBfred\fR\&. The only exception to this is the username passed to the \fI password server\fR (if you have one)\&. The password server will receive whatever username the client supplies without modification\&.
-
-
-Also note that no reverse mapping is done\&. The main effect this has is with printing\&. Users who have been mapped may have trouble deleting print jobs as PrintManager under WfWg will think they don't own the print job\&.
-
+Also note that no reverse mapping is done. The main effect
+this has is with printing. Users who have been mapped may have
+trouble deleting print jobs as PrintManager under WfWg will think
+they don't own the print job.
Default: \fBno username map\fR
-
-Example: \fBusername map = /usr/local/samba/lib/users.map\fR
-
-
-.TP
-username (S)
-Multiple users may be specified in a comma-delimited list, in which case the supplied password will be tested against each username in turn (left to right)\&.
-
-
-The \fIusername\fR line is needed only when the PC is unable to supply its own username\&. This is the case for the COREPLUS protocol or where your users have different WfWg usernames to UNIX usernames\&. In both these cases you may also be better using the \\\\server\\share%user syntax instead\&.
-
-
-The \fIusername\fR line is not a great solution in many cases as it means Samba will try to validate the supplied password against each of the usernames in the \fIusername\fR line in turn\&. This is slow and a bad idea for lots of users in case of duplicate passwords\&. You may get timeouts or security breaches using this parameter unwisely\&.
-
-
-Samba relies on the underlying UNIX security\&. This parameter does not restrict who can login, it just offers hints to the Samba server as to what usernames might correspond to the supplied password\&. Users can login as whoever they please and they will be able to do no more damage than if they started a telnet session\&. The daemon runs as the user that they log in as, so they cannot do anything that user cannot do\&.
-
-
-To restrict a service to a particular set of users you can use the \fIvalid users \fR parameter\&.
-
-
-If any of the usernames begin with a '@' then the name will be looked up first in the NIS netgroups list (if Samba is compiled with netgroup support), followed by a lookup in the UNIX groups database and will expand to a list of all users in the group of that name\&.
-
-
-If any of the usernames begin with a '+' then the name will be looked up only in the UNIX groups database and will expand to a list of all users in the group of that name\&.
-
-
-If any of the usernames begin with a '&' then the name will be looked up only in the NIS netgroups database (if Samba 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, and some clients may time out during the search\&.
-
-
-See the section NOTE ABOUT USERNAME/PASSWORD VALIDATION for more information on how this parameter determines access to the services\&.
-
-
-Default: \fBThe guest account if a guest service, else <empty string>.\fR
-
-
-Examples:\fBusername = fred, mary, jack, jane, @users, @pcgroup\fR
-
-
-.TP
-users (S)
-Synonym for \fI username\fR\&.
-
-
-.TP
-user (S)
-Synonym for \fIusername\fR\&.
-
-
+Example: \fBusername map = /usr/local/samba/lib/users.map
+\fR
.TP
-use sendfile (S)
-If this parameter is \fByes\fR, and Samba was built with the --with-sendfile-support option, and the underlying operating system supports sendfile system call, then some SMB read calls (mainly ReadAndX and ReadRaw) will use the more efficient sendfile system call for files that are exclusively oplocked\&. This may make more efficient use of the system CPU's and cause Samba to be faster\&. This is off by default as it's effects are unknown as yet\&.
-
+\fBuse sendfile (S)\fR
+If this parameter is yes, and Samba
+was built with the --with-sendfile-support option, and the underlying operating
+system supports sendfile system call, then some SMB read calls (mainly ReadAndX
+and ReadRaw) will use the more efficient sendfile system call for files that
+are exclusively oplocked. This may make more efficient use of the system CPU's
+and cause Samba to be faster. This is off by default as it's effects are unknown
+as yet.
Default: \fBuse sendfile = no\fR
-
-
.TP
-use spnego (G)
-This variable controls controls whether samba will try to use Simple and Protected NEGOciation (as specified by rfc2478) with WindowsXP and Windows2000sp2 clients to agree upon an authentication mechanism\&. Unless further issues are discovered with our SPNEGO implementation, there is no reason this should ever be disabled\&.
+\fButmp (G)\fR
+This boolean parameter is only available if
+Samba has been configured and compiled with the option \fB --with-utmp\fR. If set to yes then Samba will attempt
+to add utmp or utmpx records (depending on the UNIX system) whenever a
+connection is made to a Samba server. Sites may use this to record the
+user connecting to a Samba share.
+Due to the requirements of the utmp record, we
+are required to create a unique identifier for the
+incoming user. Enabling this option creates an n^2
+algorithm to find this number. This may impede
+performance on large installations.
-Default: \fBuse spnego = yes\fR
-
+See also the \fI utmp directory\fR parameter.
+Default: \fButmp = no\fR
.TP
-utmp directory (G)
-This parameter is only available if Samba has been configured and compiled with the option \fB --with-utmp\fR\&. It specifies a directory pathname that is used to store the utmp or utmpx files (depending on the UNIX system) that record user connections to a Samba server\&. See also the \fIutmp\fR parameter\&. By default this is not set, meaning the system will use whatever utmp file the native system is set to use (usually \fI/var/run/utmp\fR on Linux)\&.
-
+\fButmp directory(G)\fR
+This parameter is only available if Samba has
+been configured and compiled with the option \fB --with-utmp\fR. It specifies a directory pathname that is
+used to store the utmp or utmpx files (depending on the UNIX system) that
+record user connections to a Samba server. See also the \fIutmp\fR parameter. By default this is
+not set, meaning the system will use whatever utmp file the
+native system is set to use (usually
+\fI/var/run/utmp\fR on Linux).
Default: \fBno utmp directory\fR
-
Example: \fButmp directory = /var/run/utmp\fR
-
-
.TP
-utmp (G)
-This boolean parameter is only available if Samba has been configured and compiled with the option \fB --with-utmp\fR\&. If set to \fByes\fR then Samba will attempt to add utmp or utmpx records (depending on the UNIX system) whenever a connection is made to a Samba server\&. Sites may use this to record the user connecting to a Samba share\&.
-
-
-Due to the requirements of the utmp record, we are required to create a unique identifier for the incoming user\&. Enabling this option creates an n^2 algorithm to find this number\&. This may impede performance on large installations\&.
-
-
-See also the \fI utmp directory\fR parameter\&.
-
-
-Default: \fButmp = no\fR
+\fBwtmp directory(G)\fR
+This parameter is only available if Samba has
+been configured and compiled with the option \fB --with-utmp\fR. It specifies a directory pathname that is
+used to store the wtmp or wtmpx files (depending on the UNIX system) that
+record user connections to a Samba server. The difference with
+the utmp directory is the fact that user info is kept after a user
+has logged out.
+See also the \fIutmp\fR parameter. By default this is
+not set, meaning the system will use whatever utmp file the
+native system is set to use (usually
+\fI/var/run/wtmp\fR on Linux).
+Default: \fBno wtmp directory\fR
+Example: \fBwtmp directory = /var/log/wtmp\fR
.TP
-valid users (S)
-This is a list of users that should be allowed to login to this service\&. Names starting with '@', '+' and '&' are interpreted using the same rules as described in the \fIinvalid users\fR parameter\&.
+\fBvalid users (S)\fR
+This is a list of users that should be allowed
+to login to this service. Names starting with '@', '+' and '&'
+are interpreted using the same rules as described in the
+\fIinvalid users\fR parameter.
+If this is empty (the default) then any user can login.
+If a username is in both this list and the \fIinvalid
+users\fR list then access is denied for that user.
-If this is empty (the default) then any user can login\&. If a username is in both this list and the \fIinvalid users\fR list then access is denied for that user\&.
+The current servicename is substituted for \fI%S
+\fR. This is useful in the [homes] section.
+See also \fIinvalid users
+\fR
-The current servicename is substituted for \fI%S \fR\&. This is useful in the [homes] section\&.
-
-
-See also \fIinvalid users \fR
-
-
-Default: \fBNo valid users list (anyone can login) \fR
-
+Default: \fBNo valid users list (anyone can login)
+\fR
Example: \fBvalid users = greg, @pcusers\fR
-
-
.TP
-veto files (S)
-This is a list of files and directories that are neither visible nor accessible\&. Each entry in the list must be separated by a '/', which allows spaces to be included in the entry\&. '*' and '?' can be used to specify multiple files or directories as in DOS wildcards\&.
-
-
-Each entry must be a unix path, not a DOS path and must \fBnot\fR include the unix directory separator '/'\&.
-
-
-Note that the \fIcase sensitive\fR option is applicable in vetoing files\&.
-
+\fBveto files(S)\fR
+This is a list of files and directories that
+are neither visible nor accessible. Each entry in the list must
+be separated by a '/', which allows spaces to be included
+in the entry. '*' and '?' can be used to specify multiple files
+or directories as in DOS wildcards.
-One feature of the veto files parameter that it is important to be aware of is Samba's behaviour when trying to delete a directory\&. If a directory that is to be deleted contains nothing but veto files this deletion will \fBfail\fR unless you also set the \fIdelete veto files\fR parameter to \fIyes\fR\&.
+Each entry must be a unix path, not a DOS path and
+must \fBnot\fR include the unix directory
+separator '/'.
+Note that the \fIcase sensitive\fR option
+is applicable in vetoing files.
-Setting this parameter will affect the performance of Samba, as it will be forced to check all files and directories for a match as they are scanned\&.
+One feature of the veto files parameter that it
+is important to be aware of is Samba's behaviour when
+trying to delete a directory. If a directory that is
+to be deleted contains nothing but veto files this
+deletion will \fBfail\fR unless you also set
+the \fIdelete veto files\fR parameter to
+\fIyes\fR.
+Setting this parameter will affect the performance
+of Samba, as it will be forced to check all files and directories
+for a match as they are scanned.
-See also \fIhide files \fR and \fI case sensitive\fR\&.
-
-
-Default: \fBNo files or directories are vetoed\&. \fR
+See also \fIhide files
+\fR and \fI case sensitive\fR.
+Default: \fBNo files or directories are vetoed.
+\fR
Examples:
-.nf
+.nf
; Veto any files containing the word Security,
-; any ending in \&.tmp, and any directory containing the
-; word root\&.
-veto files = /*Security*/*\&.tmp/*root*/
+; any ending in .tmp, and any directory containing the
+; word root.
+veto files = /*Security*/*.tmp/*root*/
; Veto the Apple specific files that a NetAtalk server
-; creates\&.
-veto files = /\&.AppleDouble/\&.bin/\&.AppleDesktop/Network Trash Folder/
+; creates.
+veto files = /.AppleDouble/.bin/.AppleDesktop/Network Trash Folder/
.fi
-
-
.TP
-veto oplock files (S)
-This parameter is only valid when the \fIoplocks\fR parameter is turned on for a share\&. It allows the Samba administrator to selectively turn off the granting of oplocks on selected files that match a wildcarded list, similar to the wildcarded list used in the \fIveto files\fR parameter\&.
-
-
-Default: \fBNo files are vetoed for oplock grants\fR
-
-
-You might want to do this on files that you know will be heavily contended for by clients\&. A good example of this is in the NetBench SMB benchmark program, which causes heavy client contention for files ending in \fI\&.SEM\fR\&. To cause Samba not to grant oplocks on these files you would use the line (either in the [global] section or in the section for the particular NetBench share :
-
-
-Example: \fBveto oplock files = /*.SEM/\fR
-
-
-.TP
-vfs object (S)
-This parameter specifies a shared object files that are used for Samba VFS I/O operations\&. By default, normal disk I/O operations are used but these can be overloaded with one or more VFS objects\&.
-
-
-Default: \fBno value\fR
-
-
-.TP
-vfs options (S)
-This parameter allows parameters to be passed to the vfs layer at initialization time\&. See also \fI vfs object\fR\&.
-
-
-Default: \fBno value\fR
-
-
-.TP
-vfs path (S)
-This parameter specifies the directory to look in for vfs modules\&. The name of every \fBvfs object \fR will be prepended by this directory\&.
-
+\fBveto oplock files (S)\fR
+This parameter is only valid when the \fIoplocks\fR
+parameter is turned on for a share. It allows the Samba administrator
+to selectively turn off the granting of oplocks on selected files that
+match a wildcarded list, similar to the wildcarded list used in the
+\fIveto files\fR
+parameter.
+
+Default: \fBNo files are vetoed for oplock
+grants\fR
+
+You might want to do this on files that you know will
+be heavily contended for by clients. A good example of this
+is in the NetBench SMB benchmark program, which causes heavy
+client contention for files ending in \fI.SEM\fR.
+To cause Samba not to grant oplocks on these files you would use
+the line (either in the [global] section or in the section for
+the particular NetBench share :
+
+Example: \fBveto oplock files = /*.SEM/
+\fR
+.TP
+\fBvfs path (S)\fR
+This parameter specifies the directory
+to look in for vfs modules. The name of every \fBvfs object
+\fR will be prepended by this directory
Default: \fBvfs path = \fR
-
Example: \fBvfs path = /usr/lib/samba/vfs\fR
+.TP
+\fBvfs object (S)\fR
+This parameter specifies a shared object files that
+are used for Samba VFS I/O operations. By default, normal
+disk I/O operations are used but these can be overloaded
+with one or more VFS objects.
-
+Default : \fBno value\fR
.TP
-volume (S)
-This allows you to override the volume label returned for a share\&. Useful for CDROMs with installation programs that insist on a particular volume label\&.
+\fBvfs options (S)\fR
+This parameter allows parameters to be passed
+to the vfs layer at initialization time.
+See also \fI vfs object\fR.
+Default : \fBno value\fR
+.TP
+\fBvolume (S)\fR
+This allows you to override the volume label
+returned for a share. Useful for CDROMs with installation programs
+that insist on a particular volume label.
Default: \fBthe name of the share\fR
-
-
.TP
-wide links (S)
-This parameter controls whether or not links in the UNIX file system may be followed by the server\&. Links that point to areas within the directory tree exported by the server are always allowed; this parameter controls access only to areas that are outside the directory tree being exported\&.
-
-
-Note that setting this parameter can have a negative effect on your server performance due to the extra system calls that Samba has to do in order to perform the link checks\&.
+\fBwide links (S)\fR
+This parameter controls whether or not links
+in the UNIX file system may be followed by the server. Links
+that point to areas within the directory tree exported by the
+server are always allowed; this parameter controls access only
+to areas that are outside the directory tree being exported.
+Note that setting this parameter can have a negative
+effect on your server performance due to the extra system calls
+that Samba has to do in order to perform the link checks.
Default: \fBwide links = yes\fR
-
-
.TP
-winbind cache time (G)
-This parameter specifies the number of seconds the \fBwinbindd\fR(8) daemon will cache user and group information before querying a Windows NT server again\&.
-
+\fBwinbind cache time (G)\fR
+This parameter specifies the number of seconds the
+winbindd(8) daemon will cache
+user and group information before querying a Windows NT server
+again.
Default: \fBwinbind cache type = 15\fR
-
-
-.TP
-winbind enum groups (G)
-On large installations using \fBwinbindd\fR(8) it may be necessary to suppress the enumeration of groups through the \fBsetgrent()\fR, \fBgetgrent()\fR and \fBendgrent()\fR group of system calls\&. If the \fIwinbind enum groups\fR parameter is \fBno\fR, calls to the \fBgetgrent()\fR system call will not return any data\&.
-
-
-\fBWarning:\fR Turning off group enumeration may cause some programs to behave oddly\&.
-
-
-Default: \fBwinbind enum groups = yes \fR
-
-
.TP
-winbind enum users (G)
-On large installations using \fBwinbindd\fR(8) it may be necessary to suppress the enumeration of users through the \fBsetpwent()\fR, \fBgetpwent()\fR and \fBendpwent()\fR group of system calls\&. If the \fIwinbind enum users\fR parameter is \fBno\fR, calls to the \fBgetpwent\fR system call will not return any data\&.
-
-
-\fBWarning:\fR Turning off user enumeration may cause some programs to behave oddly\&. For example, the finger program relies on having access to the full user list when searching for matching usernames\&.
-
+\fBwinbind enum users (G)\fR
+On large installations using
+winbindd(8) it may be
+necessary to suppress the enumeration of users through the
+\fB setpwent()\fR,
+\fBgetpwent()\fR and
+\fBendpwent()\fR group of system calls. If
+the \fIwinbind enum users\fR parameter is
+no, calls to the \fBgetpwent\fR system call
+will not return any data.
+
+\fBWarning:\fR Turning off user
+enumeration may cause some programs to behave oddly. For
+example, the finger program relies on having access to the
+full user list when searching for matching
+usernames.
Default: \fBwinbind enum users = yes \fR
-
-
.TP
-winbind gid (G)
-The winbind gid parameter specifies the range of group ids that are allocated by the \fBwinbindd\fR(8) daemon\&. This range of group ids should have no existing local or NIS groups within it as strange conflicts can occur otherwise\&.
+\fBwinbind enum groups (G)\fR
+On large installations using
+winbindd(8) it may be
+necessary to suppress the enumeration of groups through the
+\fB setgrent()\fR,
+\fBgetgrent()\fR and
+\fBendgrent()\fR group of system calls. If
+the \fIwinbind enum groups\fR parameter is
+no, calls to the \fBgetgrent()\fR system
+call will not return any data.
+\fBWarning:\fR Turning off group
+enumeration may cause some programs to behave oddly.
-Default: \fBwinbind gid = <empty string>\fR
+Default: \fBwinbind enum groups = yes \fR
+.TP
+\fBwinbind gid (G)\fR
+The winbind gid parameter specifies the range of group
+ids that are allocated by the winbindd(8) daemon. This range of group ids should have no
+existing local or NIS groups within it as strange conflicts can
+occur otherwise.
+Default: \fBwinbind gid = <empty string>
+\fR
Example: \fBwinbind gid = 10000-20000\fR
-
-
.TP
-winbind separator (G)
-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 applicable when using the \fIpam_winbind\&.so\fR and \fInss_winbind\&.so\fR modules for UNIX services\&.
-
-
-Please note that setting this parameter to + causes problems with group membership at least on glibc systems, as the character + is used as a special character for NIS in /etc/group\&.
+\fBwinbind separator (G)\fR
+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 applicable when using the \fIpam_winbind.so\fR
+and \fInss_winbind.so\fR modules for UNIX services.
+Please note that setting this parameter to + causes problems
+with group membership at least on glibc systems, as the character +
+is used as a special character for NIS in /etc/group.
-Default: \fBwinbind separator = '\'\fR
-
+Default: \fBwinbind separator = '\\'\fR
Example: \fBwinbind separator = +\fR
-
-
.TP
-winbind uid (G)
-The winbind gid parameter specifies the range of group ids that are allocated by the \fBwinbindd\fR(8) daemon\&. This range of ids should have no existing local or NIS users within it as strange conflicts can occur otherwise\&.
-
-
-Default: \fBwinbind uid = <empty string>\fR
+\fBwinbind uid (G)\fR
+The winbind gid parameter specifies the range of group
+ids that are allocated by the winbindd(8) daemon. This range of ids should have no
+existing local or NIS users within it as strange conflicts can
+occur otherwise.
+Default: \fBwinbind uid = <empty string>
+\fR
Example: \fBwinbind uid = 10000-20000\fR
-
-
.TP
-winbind used default domain (G)
-This parameter specifies whether the \fBwinbindd\fR(8) daemon should operate on users without domain component in their username\&. Users without a domain component are treated as is part of the winbindd server's own domain\&. While this does not benifit Windows users, it makes SSH, FTP and e-mail function in a way much closer to the way they would in a native unix system\&.
-
-
-Default: \fBwinbind use default domain = <no>\fR
-
-
-Example: \fBwinbind use default domain = yes\fR
-
-
+\fBwinbind use default domain\fR
.TP
-wins hook (G)
-When Samba is running as a WINS server this allows you to call an external program for all changes to the WINS database\&. The primary use for this option is to allow the dynamic update of external name resolution databases such as dynamic DNS\&.
-
-
-The wins hook parameter specifies the name of a script or executable that will be called as follows:
-
-
-\fBwins_hook operation name nametype ttl IP_list\fR
-
-
-The first argument is the operation and is one of "add", "delete", or "refresh"\&. In most cases the operation can be ignored as the rest of the parameters provide sufficient information\&. Note that "refresh" may sometimes be called when the name has not previously been added, in that case it should be treated as an add\&.
-
-The second argument is the NetBIOS name\&. If the name is not a legal name then the wins hook is not called\&. Legal names contain only letters, digits, hyphens, underscores and periods\&.
-
-The third argument is the NetBIOS name type as a 2 digit hexadecimal number\&.
-
-The fourth argument is the TTL (time to live) for the name in seconds\&.
-
-The fifth and subsequent arguments are the IP addresses currently registered for that name\&. If this list is empty then the name should be deleted\&.
-
-An example script that calls the BIND dynamic DNS update program \fBnsupdate\fR is provided in the examples directory of the Samba source code\&.
+\fBwinbind use default domain (G)\fR
+This parameter specifies whether the winbindd(8)
+daemon should operate on users without domain component in their username.
+Users without a domain component are treated as is part of the winbindd server's
+own domain. While this does not benifit Windows users, it makes SSH, FTP and e-mail
+function in a way much closer to the way they would in a native unix system.
+Default: \fBwinbind use default domain = <no>
+\fR
+Example: \fBwinbind use default domain = yes\fR
.TP
-wins partner (G)
-A space separated list of partners' IP addresses for WINS replication\&. WINS partners are always defined as push/pull partners as defining only one way WINS replication is unreliable\&. WINS replication is currently experimental and unreliable between samba servers\&.
-
-
-Default: \fBwins partners = \fR
-
+\fBwins hook (G)\fR
+When Samba is running as a WINS server this
+allows you to call an external program for all changes to the
+WINS database. The primary use for this option is to allow the
+dynamic update of external name resolution databases such as
+dynamic DNS.
-Example: \fBwins partners = 192.168.0.1 172.16.1.2\fR
+The wins hook parameter specifies the name of a script
+or executable that will be called as follows:
+\fBwins_hook operation name nametype ttl IP_list
+\fR
+.RS
+.TP 0.2i
+\(bu
+The first argument is the operation and is one
+of "add", "delete", or "refresh". In most cases the operation can
+be ignored as the rest of the parameters provide sufficient
+information. Note that "refresh" may sometimes be called when the
+name has not previously been added, in that case it should be treated
+as an add.
+.TP 0.2i
+\(bu
+The second argument is the NetBIOS name. If the
+name is not a legal name then the wins hook is not called.
+Legal names contain only letters, digits, hyphens, underscores
+and periods.
+.TP 0.2i
+\(bu
+The third argument is the NetBIOS name
+type as a 2 digit hexadecimal number.
+.TP 0.2i
+\(bu
+The fourth argument is the TTL (time to live)
+for the name in seconds.
+.TP 0.2i
+\(bu
+The fifth and subsequent arguments are the IP
+addresses currently registered for that name. If this list is
+empty then the name should be deleted.
+.RE
+An example script that calls the BIND dynamic DNS update
+program \fBnsupdate\fR is provided in the examples
+directory of the Samba source code.
.TP
-wins proxy (G)
-This is a boolean that controls if \fBnmbd\fR(8) will respond to broadcast name queries on behalf of other hosts\&. You may need to set this to \fByes\fR for some older clients\&.
-
+\fBwins proxy (G)\fR
+This is a boolean that controls if nmbd(8) will respond to broadcast name
+queries on behalf of other hosts. You may need to set this
+to yes for some older clients.
Default: \fBwins proxy = no\fR
-
-
.TP
-wins server (G)
-This specifies the IP address (or DNS name: IP address for preference) of the WINS server that \fBnmbd\fR(8) should register with\&. If you have a WINS server on your network then you should set this to the WINS server's IP\&.
-
+\fBwins server (G)\fR
+This specifies the IP address (or DNS name: IP
+address for preference) of the WINS server that nmbd(8) should register with. If you have a WINS server on
+your network then you should set this to the WINS server's IP.
-You should point this at your WINS server if you have a multi-subnetted network\&.
+You should point this at your WINS server if you have a
+multi-subnetted network.
+\fBNOTE\fR. You need to set up Samba to point
+to a WINS server if you have multiple subnets and wish cross-subnet
+browsing to work correctly.
-If you want to work in multiple namespaces, you can give every wins server a 'tag'\&. For each tag, only one (working) server will be queried for a name\&. The tag should be seperated from the ip address by a colon\&.
-
-
-You need to set up Samba to point to a WINS server if you have multiple subnets and wish cross-subnet browsing to work correctly\&.
-
-See the documentation file Browsing in the samba howto collection\&.
-
+See the documentation file \fIBROWSING.txt\fR
+in the docs/ directory of your Samba source distribution.
Default: \fBnot enabled\fR
-
-Example: \fBwins server = mary:192.9.200.1 fred:192.168.3.199 mary:192.168.2.61\fR
-
-
-For this example when querying a certain name, 192\&.19\&.200\&.1 will be asked first and if that doesn't respond 192\&.168\&.2\&.61\&. If either of those doesn't know the name 192\&.168\&.3\&.199 will be queried\&.
-
-
-Example: \fBwins server = 192.9.200.1 192.168.2.61\fR
-
-
+Example: \fBwins server = 192.9.200.1\fR
.TP
-wins support (G)
-This boolean controls if the \fBnmbd\fR(8) process in Samba will act as a WINS server\&. You should not set this to \fByes\fR unless you have a multi-subnetted network and you wish a particular \fBnmbd\fR to be your WINS server\&. Note that you should \fBNEVER\fR set this to \fByes\fR on more than one machine in your network\&.
-
+\fBwins support (G)\fR
+This boolean controls if the
+nmbd(8) process in Samba will act as a WINS server. You should
+not set this to yes unless you have a multi-subnetted network and
+you wish a particular \fBnmbd\fR to be your WINS server.
+Note that you should \fBNEVER\fR set this to yes
+on more than one machine in your network.
Default: \fBwins support = no\fR
-
-
.TP
-workgroup (G)
-This controls what workgroup your server will appear to be in when queried by clients\&. Note that this parameter also controls the Domain name used with the \fBsecurity = domain\fR setting\&.
-
+\fBworkgroup (G)\fR
+This controls what workgroup your server will
+appear to be in when queried by clients. Note that this parameter
+also controls the Domain name used with the \fBsecurity = domain\fR
+setting.
Default: \fBset at compile time to WORKGROUP\fR
-
Example: \fBworkgroup = MYGROUP\fR
-
-
.TP
-writable (S)
-Synonym for \fI writeable\fR for people who can't spell :-)\&.
-
-
-.TP
-writeable (S)
-Inverted synonym for \fIread only\fR\&.
-
-
-.TP
-write cache size (S)
-If this integer parameter is set to non-zero value, Samba will create an in-memory cache for each oplocked file (it does \fBnot\fR do this for non-oplocked files)\&. All writes that the client does not request to be flushed directly to disk will be stored in this cache if possible\&. The cache is flushed onto disk when a write comes in whose offset would not fit into the cache or when the file is closed by the client\&. Reads for the file are also served from this cache if the data is stored within it\&.
-
-
-This cache allows Samba to batch client writes into a more efficient write size for RAID disks (i\&.e\&. writes may be tuned to be the RAID stripe size) and can improve performance on systems where the disk subsystem is a bottleneck but there is free memory for userspace programs\&.
-
-
-The integer parameter specifies the size of this cache (per oplocked file) in bytes\&.
-
+\fBwritable (S)\fR
+Synonym for \fI writeable\fR for people who can't spell :-).
+.TP
+\fBwrite cache size (S)\fR
+If this integer parameter is set to non-zero value,
+Samba will create an in-memory cache for each oplocked file
+(it does \fBnot\fR do this for
+non-oplocked files). All writes that the client does not request
+to be flushed directly to disk will be stored in this cache if possible.
+The cache is flushed onto disk when a write comes in whose offset
+would not fit into the cache or when the file is closed by the client.
+Reads for the file are also served from this cache if the data is stored
+within it.
+
+This cache allows Samba to batch client writes into a more
+efficient write size for RAID disks (i.e. writes may be tuned to
+be the RAID stripe size) and can improve performance on systems
+where the disk subsystem is a bottleneck but there is free
+memory for userspace programs.
+
+The integer parameter specifies the size of this cache
+(per oplocked file) in bytes.
Default: \fBwrite cache size = 0\fR
-
Example: \fBwrite cache size = 262144\fR
-
-for a 256k cache size per file\&.
-
-
+for a 256k cache size per file.
.TP
-write list (S)
-This is a list of users that are given read-write access to a service\&. If the connecting user is in this list then they will be given write access, no matter what the \fIread only\fR option is set to\&. The list can include group names using the @group syntax\&.
-
-
-Note that if a user is in both the read list and the write list then they will be given write access\&.
-
+\fBwrite list (S)\fR
+This is a list of users that are given read-write
+access to a service. If the connecting user is in this list then
+they will be given write access, no matter what the \fIread only\fR
+option is set to. The list can include group names using the
+@group syntax.
-See also the \fIread list \fR option\&.
+Note that if a user is in both the read list and the
+write list then they will be given write access.
+See also the \fIread list
+\fR option.
-Default: \fBwrite list = <empty string>\fR
-
-
-Example: \fBwrite list = admin, root, @staff\fR
-
+Default: \fBwrite list = <empty string>
+\fR
+Example: \fBwrite list = admin, root, @staff
+\fR
.TP
-write ok (S)
-Inverted synonym for \fIread only\fR\&.
+\fBwins partners (G)\fR
+A space separated list of partners' IP addresses for
+WINS replication. WINS partners are always defined as push/pull
+partners as defining only one way WINS replication is unreliable.
+WINS replication is currently experimental and unreliable between
+samba servers.
+Default: \fBwins partners = \fR
+Example: \fBwins partners = 192.168.0.1 172.16.1.2\fR
.TP
-write raw (G)
-This parameter controls whether or not the server will support raw write SMB's when transferring data from clients\&. You should never need to change this parameter\&.
-
+\fBwrite ok (S)\fR
+Inverted synonym for \fI read only\fR.
+.TP
+\fBwrite raw (G)\fR
+This parameter controls whether or not the server
+will support raw write SMB's when transferring data from clients.
+You should never need to change this parameter.
Default: \fBwrite raw = yes\fR
-
-
.TP
-wtmp directory (G)
-This parameter is only available if Samba has been configured and compiled with the option \fB --with-utmp\fR\&. It specifies a directory pathname that is used to store the wtmp or wtmpx files (depending on the UNIX system) that record user connections to a Samba server\&. The difference with the utmp directory is the fact that user info is kept after a user has logged out\&.
-
-
-See also the \fIutmp\fR parameter\&. By default this is not set, meaning the system will use whatever utmp file the native system is set to use (usually \fI/var/run/wtmp\fR on Linux)\&.
-
-
-Default: \fBno wtmp directory\fR
-
-
-Example: \fBwtmp directory = /var/log/wtmp\fR
-
-
+\fBwriteable (S)\fR
+Inverted synonym for \fI read only\fR.
.SH "WARNINGS"
-
.PP
-Although the configuration file permits service names to contain spaces, your client software may not\&. Spaces will be ignored in comparisons anyway, so it shouldn't be a problem - but be aware of the possibility\&.
-
+Although the configuration file permits service names
+to contain spaces, your client software may not. Spaces will
+be ignored in comparisons anyway, so it shouldn't be a
+problem - but be aware of the possibility.
.PP
-On a similar note, many clients - especially DOS clients - limit service names to eight characters\&. \fBsmbd\fR(8) has no such limitation, but attempts to connect from such clients will fail if they truncate the service names\&. For this reason you should probably keep your service names down to eight characters in length\&.
-
+On a similar note, many clients - especially DOS clients -
+limit service names to eight characters. smbd(8)
+ has no such limitation, but attempts to connect from such
+clients will fail if they truncate the service names. For this reason
+you should probably keep your service names down to eight characters
+in length.
.PP
-Use of the [homes] and [printers] special sections make life for an administrator easy, but the various combinations of default attributes can be tricky\&. Take extreme care when designing these sections\&. In particular, ensure that the permissions on spool directories are correct\&.
-
+Use of the [homes] and [printers] special sections make life
+for an administrator easy, but the various combinations of default
+attributes can be tricky. Take extreme care when designing these
+sections. In particular, ensure that the permissions on spool
+directories are correct.
.SH "VERSION"
-
.PP
-This man page is correct for version 3\&.0 of the Samba suite\&.
-
+This man page is correct for version 3.0 of
+the Samba suite.
.SH "SEE ALSO"
-
.PP
-\fBsamba\fR(7), \fBsmbpasswd\fR(8), \fBswat\fR(8), \fBsmbd\fR(8), \fBnmbd\fR(8), \fBsmbclient\fR(1), \fBnmblookup\fR(1), \fBtestparm\fR(1), \fBtestprns\fR(1)\&.
-
+samba(7)
+\fBsmbpasswd(8)\fR
+\fBswat(8)\fR
+\fBsmbd(8)\fR
+\fBnmbd(8)\fR
+\fBsmbclient(1)\fR
+\fBnmblookup(1)\fR
+\fBtestparm(1)\fR
+\fBtestprns(1)\fR
.SH "AUTHOR"
-
.PP
-The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&.
-
+The original Samba software and related utilities
+were created by Andrew Tridgell. Samba is now developed
+by the Samba Team as an Open Source project similar
+to the way the Linux kernel is developed.
.PP
-The original Samba man pages were written by Karl Auer\&. The man page sources were converted to YODL format (another excellent piece of Open Source software, available at ftp://ftp\&.icce\&.rug\&.nl/pub/unix/) and updated for the Samba 2\&.0 release by Jeremy Allison\&. The conversion to DocBook for Samba 2\&.2 was done by Gerald Carter\&. The conversion to DocBook XML 4\&.2 for Samba 3\&.0 was done by Alexander Bokovoy\&.
-
+The original Samba man pages were written by Karl Auer.
+The man page sources were converted to YODL format (another
+excellent piece of Open Source software, available at
+ftp://ftp.icce.rug.nl/pub/unix/ <URL:ftp://ftp.icce.rug.nl/pub/unix/>) and updated for the Samba 2.0
+release by Jeremy Allison. The conversion to DocBook for
+Samba 2.2 was done by Gerald Carter
diff --git a/docs/manpages/smbcacls.1 b/docs/manpages/smbcacls.1
index 9df06dff9b..aaed1ba8f5 100644
--- a/docs/manpages/smbcacls.1
+++ b/docs/manpages/smbcacls.1
@@ -1,135 +1,82 @@
-.\"Generated by db2man.xsl. Don't modify this, modify the source.
-.de Sh \" Subsection
-.br
-.if t .Sp
-.ne 5
-.PP
-\fB\\$1\fR
-.PP
-..
-.de Sp \" Vertical space (when we can't use .PP)
-.if t .sp .5v
-.if n .sp
-..
-.de Ip \" List item
-.br
-.ie \\n(.$>=3 .ne \\$3
-.el .ne 3
-.IP "\\$1" \\$2
-..
-.TH "SMBCACLS" 1 "" "" ""
+.\" This manpage has been automatically generated by docbook2man
+.\" from a DocBook document. This tool can be found at:
+.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
+.\" Please send any bug reports, improvements, comments, patches,
+.\" etc. to Steve Cheng <steve@ggi-project.org>.
+.TH "SMBCACLS" "1" "04 March 2003" "" ""
.SH NAME
smbcacls \- Set or get ACLs on an NT file or directory names
-.SH "SYNOPSIS"
+.SH SYNOPSIS
-.nf
-\fBsmbcacls\fR {//server/share} {filename} [-D acls] [-M acls] [-A acls] [-S acls] [-C name] [-G name] [-n] [-t] [-U username] [-h] [-d]
-
-.fi
+\fBsmbcacls\fR \fB//server/share\fR \fBfilename\fR [ \fB-U username\fR ] [ \fB-A acls\fR ] [ \fB-M acls\fR ] [ \fB-D acls\fR ] [ \fB-S acls\fR ] [ \fB-C name\fR ] [ \fB-G name\fR ] [ \fB-n\fR ] [ \fB-h\fR ]
.SH "DESCRIPTION"
-
.PP
-This tool is part of the \fBSamba\fR(7) suite\&.
-
+This tool is part of the Samba suite.
.PP
-The \fBsmbcacls\fR program manipulates NT Access Control Lists (ACLs) on SMB file shares\&.
-
+The \fBsmbcacls\fR program manipulates NT Access Control
+Lists (ACLs) on SMB file shares.
.SH "OPTIONS"
-
.PP
-The following options are available to the \fBsmbcacls\fR program\&. The format of ACLs is described in the section ACL FORMAT
-
-.TP
--A acls
-Add the ACLs specified to the ACL list\&. Existing access control entries are unchanged\&.
-
-
-.TP
--M acls
-Modify the mask value (permissions) for the ACLs specified on the command line\&. An error will be printed for each ACL specified that was not already present in the ACL list
-
-
-.TP
--D acls
-Delete any ACLs specified on the command line\&. An error will be printed for each ACL specified that was not already present in the ACL list\&.
-
-
-.TP
--S acls
-This command sets the ACLs on the file with only the ones specified on the command line\&. All other ACLs are erased\&. Note that the ACL specified must contain at least a revision, type, owner and group for the call to succeed\&.
-
-
-.TP
--U username
-Specifies a username used to connect to the specified service\&. The username may be of the form "username" in which case the user is prompted to enter in a password and the workgroup specified in the \fBsmb.conf\fR(5) file is used, or "username%password" or "DOMAIN\\username%password" and the password and workgroup names are used as provided\&.
-
-
-.TP
--C name
-The owner of a file or directory can be changed to the name given using the \fI-C\fR option\&. The name can be a sid in the form S-1-x-y-z or a name resolved against the server specified in the first argument\&.
-
-
-This command is a shortcut for -M OWNER:name\&.
-
-
-.TP
--G name
-The group owner of a file or directory can be changed to the name given using the \fI-G\fR option\&. The name can be a sid in the form S-1-x-y-z or a name resolved against the server specified n the first argument\&.
-
-
-This command is a shortcut for -M GROUP:name\&.
-
-
-.TP
--n
-This option displays all ACL information in numeric format\&. The default is to convert SIDs to names and ACE types and masks to a readable string format\&.
-
-
-.TP
--t
-Don't actually do anything, only validate the correctness of the arguments\&.
-
-
-.TP
--h|--help
-Print a summary of command line options\&.
-
-
-.TP
--V
-Prints the version number for \fBsmbd\fR\&.
-
-
-.TP
--s <configuration file>
-The file specified contains the configuration details required by the server\&. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is to provide\&. See \fI smb\&.conf(5)\fR for more information\&. The default configuration file name is determined at compile time\&.
-
-
-.TP
--d|--debug=debuglevel
-\fIdebuglevel\fR is an integer from 0 to 10\&. The default value if this parameter is not specified is zero\&.
-
-
-The higher this value, the more detail will be logged to the log files about the activities of the server\&. At level 0, only critical errors and serious warnings will be logged\&. Level 1 is a reasonable level for day to day running - it generates a small amount of information about operations carried out\&.
-
-
-Levels above 1 will generate considerable amounts of log data, and should only be used when investigating a problem\&. Levels above 3 are designed for use only by developers and generate HUGE amounts of log data, most of which is extremely cryptic\&.
-
-
-Note that specifying this parameter here will override the log level parameter in the \fIsmb\&.conf(5)\fR file\&.
-
-
-.TP
--l|--logfile=logbasename
-File name for log/debug files\&. The extension \fB"\&.client"\fR will be appended\&. The log file is never removed by the client\&.
-
-
+The following options are available to the \fBsmbcacls\fR program.
+The format of ACLs is described in the section ACL FORMAT
+.TP
+\fB-A acls\fR
+Add the ACLs specified to the ACL list. Existing
+access control entries are unchanged.
+.TP
+\fB-M acls\fR
+Modify the mask value (permissions) for the ACLs
+specified on the command line. An error will be printed for each
+ACL specified that was not already present in the ACL list
+.TP
+\fB-D acls\fR
+Delete any ACLs specified on the command line.
+An error will be printed for each ACL specified that was not
+already present in the ACL list.
+.TP
+\fB-S acls\fR
+This command sets the ACLs on the file with
+only the ones specified on the command line. All other ACLs are
+erased. Note that the ACL specified must contain at least a revision,
+type, owner and group for the call to succeed.
+.TP
+\fB-U username\fR
+Specifies a username used to connect to the
+specified service. The username may be of the form "username" in
+which case the user is prompted to enter in a password and the
+workgroup specified in the \fIsmb.conf\fR file is
+used, or "username%password" or "DOMAIN\\username%password" and the
+password and workgroup names are used as provided.
+.TP
+\fB-C name\fR
+The owner of a file or directory can be changed
+to the name given using the \fI-C\fR option.
+The name can be a sid in the form S-1-x-y-z or a name resolved
+against the server specified in the first argument.
+
+This command is a shortcut for -M OWNER:name.
+.TP
+\fB-G name\fR
+The group owner of a file or directory can
+be changed to the name given using the \fI-G\fR
+option. The name can be a sid in the form S-1-x-y-z or a name
+resolved against the server specified n the first argument.
+
+This command is a shortcut for -M GROUP:name.
+.TP
+\fB-n\fR
+This option displays all ACL information in numeric
+format. The default is to convert SIDs to names and ACE types
+and masks to a readable string format.
+.TP
+\fB-h\fR
+Print usage information on the \fBsmbcacls
+\fR program.
.SH "ACL FORMAT"
-
.PP
-The format of an ACL is one or more ACL entries separated by either commas or newlines\&. An ACL entry is one of the following:
-
+The format of an ACL is one or more ACL entries separated by
+either commas or newlines. An ACL entry is one of the following:
.PP
.nf
@@ -138,109 +85,104 @@ REVISION:<revision number>
OWNER:<sid or name>
GROUP:<sid or name>
ACL:<sid or name>:<type>/<flags>/<mask>
+
.fi
-
-
-.PP
-The revision of the ACL specifies the internal Windows NT ACL revision for the security descriptor\&. If not specified it defaults to 1\&. Using values other than 1 may cause strange behaviour\&.
-
.PP
-The owner and group specify the owner and group sids for the object\&. If a SID in the format CWS-1-x-y-z is specified this is used, otherwise the name specified is resolved using the server on which the file or directory resides\&.
-
-.PP
-ACLs specify permissions granted to the SID\&. This SID again can be specified in CWS-1-x-y-z format or as a name in which case it is resolved against the server on which the file or directory resides\&. The type, flags and mask values determine the type of access granted to the SID\&.
-
-.PP
-The type can be either 0 or 1 corresponding to ALLOWED or DENIED access to the SID\&. The flags values are generally zero for file ACLs and either 9 or 2 for directory ACLs\&. Some common flags are:
-
-.TP 3
+The revision of the ACL specifies the internal Windows
+NT ACL revision for the security descriptor.
+If not specified it defaults to 1. Using values other than 1 may
+cause strange behaviour.
+.PP
+The owner and group specify the owner and group sids for the
+object. If a SID in the format CWS-1-x-y-z is specified this is used,
+otherwise the name specified is resolved using the server on which
+the file or directory resides.
+.PP
+ACLs specify permissions granted to the SID. This SID again
+can be specified in CWS-1-x-y-z format or as a name in which case
+it is resolved against the server on which the file or directory
+resides. The type, flags and mask values determine the type of
+access granted to the SID.
+.PP
+The type can be either 0 or 1 corresponding to ALLOWED or
+DENIED access to the SID. The flags values are generally
+zero for file ACLs and either 9 or 2 for directory ACLs. Some
+common flags are:
+.TP 0.2i
\(bu
-\fB#define SEC_ACE_FLAG_OBJECT_INHERIT 0x1\fR
-
-.TP
+#define SEC_ACE_FLAG_OBJECT_INHERIT 0x1
+.TP 0.2i
\(bu
-\fB#define SEC_ACE_FLAG_CONTAINER_INHERIT 0x2\fR
-
-.TP
+#define SEC_ACE_FLAG_CONTAINER_INHERIT 0x2
+.TP 0.2i
\(bu
-\fB#define SEC_ACE_FLAG_NO_PROPAGATE_INHERIT 0x4\fR
-
-.TP
+#define SEC_ACE_FLAG_NO_PROPAGATE_INHERIT 0x4
+.TP 0.2i
\(bu
-\fB#define SEC_ACE_FLAG_INHERIT_ONLY 0x8\fR
-
-.LP
-
+#define SEC_ACE_FLAG_INHERIT_ONLY 0x8
.PP
-At present flags can only be specified as decimal or hexadecimal values\&.
-
+At present flags can only be specified as decimal or
+hexadecimal values.
.PP
-The mask is a value which expresses the access right granted to the SID\&. It can be given as a decimal or hexadecimal value, or by using one of the following text strings which map to the NT file permissions of the same name\&.
-
-.TP 3
+The mask is a value which expresses the access right
+granted to the SID. It can be given as a decimal or hexadecimal value,
+or by using one of the following text strings which map to the NT
+file permissions of the same name.
+.TP 0.2i
\(bu
-\fBR\fR - Allow read access
-
-.TP
+\fBR\fR - Allow read access
+.TP 0.2i
\(bu
\fBW\fR - Allow write access
-
-.TP
+.TP 0.2i
\(bu
\fBX\fR - Execute permission on the object
-
-.TP
+.TP 0.2i
\(bu
\fBD\fR - Delete the object
-
-.TP
+.TP 0.2i
\(bu
\fBP\fR - Change permissions
-
-.TP
+.TP 0.2i
\(bu
\fBO\fR - Take ownership
-
-.LP
-
.PP
The following combined permissions can be specified:
-
-.TP 3
+.TP 0.2i
\(bu
-\fBREAD\fR - Equivalent to 'RX' permissions
-
-.TP
+\fBREAD\fR - Equivalent to 'RX'
+permissions
+.TP 0.2i
\(bu
\fBCHANGE\fR - Equivalent to 'RXWD' permissions
-
-.TP
+.TP 0.2i
\(bu
-\fBFULL\fR - Equivalent to 'RWXDPO' permissions
-
-.LP
-
+\fBFULL\fR - Equivalent to 'RWXDPO'
+permissions
.SH "EXIT STATUS"
-
.PP
-The \fBsmbcacls\fR program sets the exit status depending on the success or otherwise of the operations performed\&. The exit status may be one of the following values\&.
-
+The \fBsmbcacls\fR program sets the exit status
+depending on the success or otherwise of the operations performed.
+The exit status may be one of the following values.
.PP
-If the operation succeeded, smbcacls returns and exit status of 0\&. If \fBsmbcacls\fR couldn't connect to the specified server, or there was an error getting or setting the ACLs, an exit status of 1 is returned\&. If there was an error parsing any command line arguments, an exit status of 2 is returned\&.
-
+If the operation succeeded, smbcacls returns and exit
+status of 0. If \fBsmbcacls\fR couldn't connect to the specified server,
+or there was an error getting or setting the ACLs, an exit status
+of 1 is returned. If there was an error parsing any command line
+arguments, an exit status of 2 is returned.
.SH "VERSION"
-
.PP
-This man page is correct for version 3\&.0 of the Samba suite\&.
-
+This man page is correct for version 2.2 of
+the Samba suite.
.SH "AUTHOR"
-
.PP
-The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&.
-
+The original Samba software and related utilities
+were created by Andrew Tridgell. Samba is now developed
+by the Samba Team as an Open Source project similar
+to the way the Linux kernel is developed.
.PP
-\fBsmbcacls\fR was written by Andrew Tridgell and Tim Potter\&.
-
+\fBsmbcacls\fR was written by Andrew Tridgell
+and Tim Potter.
.PP
-The conversion to DocBook for Samba 2\&.2 was done by Gerald Carter\&. The conversion to DocBook XML 4\&.2 for Samba 3\&.0 was done by Alexander Bokovoy\&.
-
+The conversion to DocBook for Samba 2.2 was done
+by Gerald Carter
diff --git a/docs/manpages/smbclient.1 b/docs/manpages/smbclient.1
index 3f5718a2fa..e5785acaf5 100644
--- a/docs/manpages/smbclient.1
+++ b/docs/manpages/smbclient.1
@@ -1,651 +1,798 @@
-.\"Generated by db2man.xsl. Don't modify this, modify the source.
-.de Sh \" Subsection
-.br
-.if t .Sp
-.ne 5
-.PP
-\fB\\$1\fR
-.PP
-..
-.de Sp \" Vertical space (when we can't use .PP)
-.if t .sp .5v
-.if n .sp
-..
-.de Ip \" List item
-.br
-.ie \\n(.$>=3 .ne \\$3
-.el .ne 3
-.IP "\\$1" \\$2
-..
-.TH "SMBCLIENT" 1 "" "" ""
+.\" This manpage has been automatically generated by docbook2man
+.\" from a DocBook document. This tool can be found at:
+.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
+.\" Please send any bug reports, improvements, comments, patches,
+.\" etc. to Steve Cheng <steve@ggi-project.org>.
+.TH "SMBCLIENT" "1" "04 March 2003" "" ""
.SH NAME
-smbclient \- ftp-like client to access SMB/CIFS resources on servers
-.SH "SYNOPSIS"
+smbclient \- ftp-like client to access SMB/CIFS resources on servers
+.SH SYNOPSIS
-.nf
-\fBsmbclient\fR {servicename} [password] [-b <buffer size>] [-d debuglevel] [-D Directory]
- [-U username] [-W workgroup] [-M <netbios name>] [-m maxprotocol] [-A authfile] [-N] [-l logfile] [-L <netbios name>] [-I destinationIP] [-E] [-c <command string>] [-i scope] [-O <socket options>] [-p port] [-R <name resolve order>] [-s <smb config file>] [-T<c|x>IXFqgbNan] [-k]
-
-.fi
+\fBsmbclient\fR \fBservicename\fR [ \fBpassword\fR ] [ \fB-b <buffer size>\fR ] [ \fB-d debuglevel\fR ] [ \fB-D Directory\fR ] [ \fB-U username\fR ] [ \fB-W workgroup\fR ] [ \fB-M <netbios name>\fR ] [ \fB-m maxprotocol\fR ] [ \fB-A authfile\fR ] [ \fB-N\fR ] [ \fB-l logfile\fR ] [ \fB-L <netbios name>\fR ] [ \fB-I destinationIP\fR ] [ \fB-E\fR ] [ \fB-c <command string>\fR ] [ \fB-i scope\fR ] [ \fB-O <socket options>\fR ] [ \fB-p port\fR ] [ \fB-R <name resolve order>\fR ] [ \fB-s <smb config file>\fR ] [ \fB-T<c|x>IXFqgbNan\fR ]
.SH "DESCRIPTION"
-
.PP
-This tool is part of the \fBSamba\fR(7) suite\&.
-
+This tool is part of the Samba suite.
.PP
-\fBsmbclient\fR is a client that can 'talk' to an SMB/CIFS server\&. It offers an interface similar to that of the ftp program (see \fBftp\fR(1))\&. Operations include things like getting files from the server to the local machine, putting files from the local machine to the server, retrieving directory information from the server and so on\&.
-
+\fBsmbclient\fR is a client that can
+\&'talk' to an SMB/CIFS server. It offers an interface
+similar to that of the ftp program (see \fBftp(1)\fR).
+Operations include things like getting files from the server
+to the local machine, putting files from the local machine to
+the server, retrieving directory information from the server
+and so on.
.SH "OPTIONS"
-
-.TP
-servicename
-servicename is the name of the service you want to use on the server\&. A service name takes the form \fI//server/service\fR where \fIserver \fR is the NetBIOS name of the SMB/CIFS server offering the desired service and \fIservice\fR is the name of the service offered\&. Thus to connect to the service "printer" on the SMB/CIFS server "smbserver", you would use the servicename \fI//smbserver/printer \fR
-
-
-Note that the server name required is NOT necessarily the IP (DNS) host name of the server ! The name required is a NetBIOS server name, which may or may not be the same as the IP hostname of the machine running the server\&.
-
-
-The server name is looked up according to either the \fI-R\fR parameter to \fBsmbclient\fR or using the name resolve order parameter in the \fBsmb.conf\fR(5) file, allowing an administrator to change the order and methods by which server names are looked up\&.
-
-
.TP
-password
-The password required to access the specified service on the specified server\&. If this parameter is supplied, the \fI-N\fR option (suppress password prompt) is assumed\&.
-
-
-There is no default password\&. If no password is supplied on the command line (either by using this parameter or adding a password to the \fI-U\fR option (see below)) and the \fI-N\fR option is not specified, the client will prompt for a password, even if the desired service does not require one\&. (If no password is required, simply press ENTER to provide a null password\&.)
-
-
-Note: Some servers (including OS/2 and Windows for Workgroups) insist on an uppercase password\&. Lowercase or mixed case passwords may be rejected by these servers\&.
-
-
-Be cautious about including passwords in scripts\&.
-
-
-.TP
--R <name resolve order>
-This option is used by the programs in the Samba suite to determine what naming services and in what order to resolve host names to IP addresses\&. The option takes a space-separated string of different name resolution options\&.
-
-
-The options are :"lmhosts", "host", "wins" and "bcast"\&. They cause names to be resolved as follows:
-
-
-\fBlmhosts\fR: Lookup an IP address in the Samba lmhosts file\&. If the line in lmhosts has no name type attached to the NetBIOS name (see the \fBlmhosts\fR(5) for details) then any name type matches for lookup\&.
-
-\fBhost\fR: Do a standard host name to IP address resolution, using the system \fI/etc/hosts \fR, NIS, or DNS lookups\&. This method of name resolution is operating system dependent, for instance on IRIX or Solaris this may be controlled by the \fI/etc/nsswitch\&.conf\fR file)\&. Note that this method is only used if the NetBIOS name type being queried is the 0x20 (server) name type, otherwise it is ignored\&.
-
-\fBwins\fR: Query a name with the IP address listed in the \fIwins server\fR parameter\&. If no WINS server has been specified this method will be ignored\&.
-
-\fBbcast\fR: Do a broadcast on each of the known local interfaces listed in the \fIinterfaces\fR parameter\&. This is the least reliable of the name resolution methods as it depends on the target host being on a locally connected subnet\&.
-
-If this parameter is not set then the name resolve order defined in the \fBsmb.conf\fR(5) file parameter (name resolve order) will be used\&.
-
-
-The default order is lmhosts, host, wins, bcast and without this parameter or any entry in the \fIname resolve order \fR parameter of the \fBsmb.conf\fR(5) file the name resolution methods will be attempted in this order\&.
-
-
-.TP
--M NetBIOS name
-This options allows you to send messages, using the "WinPopup" protocol, to another computer\&. Once a connection is established you then type your message, pressing ^D (control-D) to end\&.
-
-
-If the receiving computer is running WinPopup the user will receive the message and probably a beep\&. If they are not running WinPopup the message will be lost, and no error message will occur\&.
-
-
-The message is also automatically truncated if the message is over 1600 bytes, as this is the limit of the protocol\&.
-
-
-One useful trick is to cat the message through \fBsmbclient\fR\&. For example: \fB cat mymessage.txt | smbclient -M FRED \fR will send the message in the file \fImymessage\&.txt\fR to the machine FRED\&.
-
-
-You may also find the \fI-U\fR and \fI-I\fR options useful, as they allow you to control the FROM and TO parts of the message\&.
-
-
-See the \fImessage command\fR parameter in the \fBsmb.conf\fR(5) for a description of how to handle incoming WinPopup messages in Samba\&.
-
-
-\fBNote\fR: Copy WinPopup into the startup group on your WfWg PCs if you want them to always be able to receive messages\&.
-
-
-.TP
--p port
-This number is the TCP port number that will be used when making connections to the server\&. The standard (well-known) TCP port number for an SMB/CIFS server is 139, which is the default\&.
-
-
-.TP
--l logfilename
-If specified, \fIlogfilename\fR specifies a base filename into which operational data from the running client will be logged\&.
-
-
-The default base name is specified at compile time\&.
-
-
-The base name is used to generate actual log file names\&. For example, if the name specified was "log", the debug file would be \fIlog\&.client\fR\&.
-
-
-The log file generated is never removed by the client\&.
-
-
-.TP
--h|--help
-Print a summary of command line options\&.
-
-
-.TP
--I IP-address
-\fIIP address\fR is the address of the server to connect to\&. It should be specified in standard "a\&.b\&.c\&.d" notation\&.
-
-
-Normally the client would attempt to locate a named SMB/CIFS server by looking it up via the NetBIOS name resolution mechanism described above in the \fIname resolve order\fR parameter above\&. Using this parameter will force the client to assume that the server is on the machine with the specified IP address and the NetBIOS name component of the resource being connected to will be ignored\&.
-
-
-There is no default for this parameter\&. If not supplied, it will be determined automatically by the client as described above\&.
-
-
-.TP
--E
-This parameter causes the client to write messages to the standard error stream (stderr) rather than to the standard output stream\&.
-
-
-By default, the client writes messages to standard output - typically the user's tty\&.
-
-
-.TP
--L
-This option allows you to look at what services are available on a server\&. You use it as \fBsmbclient -L host\fR and a list should appear\&. The \fI-I \fR option may be useful if your NetBIOS names don't match your TCP/IP DNS host names or if you are trying to reach a host on another network\&.
-
-
-.TP
--t terminal code
-This option tells \fBsmbclient\fR how to interpret filenames coming from the remote server\&. Usually Asian language multibyte UNIX implementations use different character sets than SMB/CIFS servers (\fBEUC\fR instead of \fB SJIS\fR for example)\&. Setting this parameter will let \fBsmbclient\fR convert between the UNIX filenames and the SMB filenames correctly\&. This option has not been seriously tested and may have some problems\&.
-
-
-The terminal codes include CWsjis, CWeuc, CWjis7, CWjis8, CWjunet, CWhex, CWcap\&. This is not a complete list, check the Samba source code for the complete list\&.
-
-
-.TP
--b buffersize
-This option changes the transmit/send buffer size when getting or putting a file from/to the server\&. The default is 65520 bytes\&. Setting this value smaller (to 1200 bytes) has been observed to speed up file transfers to and from a Win9x server\&.
-
-
-.TP
--V
-Prints the version number for \fBsmbd\fR\&.
-
-
-.TP
--s <configuration file>
-The file specified contains the configuration details required by the server\&. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is to provide\&. See \fI smb\&.conf(5)\fR for more information\&. The default configuration file name is determined at compile time\&.
-
-
-.TP
--d|--debug=debuglevel
-\fIdebuglevel\fR is an integer from 0 to 10\&. The default value if this parameter is not specified is zero\&.
-
-
-The higher this value, the more detail will be logged to the log files about the activities of the server\&. At level 0, only critical errors and serious warnings will be logged\&. Level 1 is a reasonable level for day to day running - it generates a small amount of information about operations carried out\&.
-
-
-Levels above 1 will generate considerable amounts of log data, and should only be used when investigating a problem\&. Levels above 3 are designed for use only by developers and generate HUGE amounts of log data, most of which is extremely cryptic\&.
-
-
-Note that specifying this parameter here will override the log level parameter in the \fIsmb\&.conf(5)\fR file\&.
-
-
-.TP
--l|--logfile=logbasename
-File name for log/debug files\&. The extension \fB"\&.client"\fR will be appended\&. The log file is never removed by the client\&.
-
-
-.TP
--N
-If specified, this parameter suppresses the normal password prompt from the client to the user\&. This is useful when accessing a service that does not require a password\&.
-
-
-Unless a password is specified on the command line or this parameter is specified, the client will request a password\&.
-
-
-.TP
--k
-Try to authenticate with kerberos\&. Only useful in an Active Directory environment\&.
-
-
-.TP
--A|--authfile=filename
-This option allows you to specify a file from which to read the username and password used in the connection\&. The format of the file is
+\fBservicename\fR
+servicename is the name of the service
+you want to use on the server. A service name takes the form
+\fI//server/service\fR where \fIserver
+\fR is the NetBIOS name of the SMB/CIFS server
+offering the desired service and \fIservice\fR
+is the name of the service offered. Thus to connect to
+the service "printer" on the SMB/CIFS server "smbserver",
+you would use the servicename \fI//smbserver/printer
+\fR
+
+Note that the server name required is NOT necessarily
+the IP (DNS) host name of the server ! The name required is
+a NetBIOS server name, which may or may not be the
+same as the IP hostname of the machine running the server.
+
+The server name is looked up according to either
+the \fI-R\fR parameter to \fBsmbclient\fR or
+using the name resolve order parameter in the \fIsmb.conf\fR file,
+allowing an administrator to change the order and methods
+by which server names are looked up.
+.TP
+\fBpassword\fR
+The password required to access the specified
+service on the specified server. If this parameter is
+supplied, the \fI-N\fR option (suppress
+password prompt) is assumed.
+
+There is no default password. If no password is supplied
+on the command line (either by using this parameter or adding
+a password to the \fI-U\fR option (see
+below)) and the \fI-N\fR option is not
+specified, the client will prompt for a password, even if
+the desired service does not require one. (If no password is
+required, simply press ENTER to provide a null password.)
+
+Note: Some servers (including OS/2 and Windows for
+Workgroups) insist on an uppercase password. Lowercase
+or mixed case passwords may be rejected by these servers.
+
+Be cautious about including passwords in scripts.
+.TP
+\fB-s smb.conf\fR
+Specifies the location of the all important
+\fIsmb.conf\fR file.
+.TP
+\fB-O socket options\fR
+TCP socket options to set on the client
+socket. See the socket options parameter in the \fI smb.conf (5)\fR manpage for the list of valid
+options.
+.TP
+\fB-R <name resolve order>\fR
+This option is used by the programs in the Samba
+suite to determine what naming services and in what order to resolve
+host names to IP addresses. The option takes a space-separated
+string of different name resolution options.
+
+The options are :"lmhosts", "host", "wins" and "bcast". They
+cause names to be resolved as follows :
+.RS
+.TP 0.2i
+\(bu
+lmhosts : Lookup an IP
+address in the Samba lmhosts file. If the line in lmhosts has
+no name type attached to the NetBIOS name (see the lmhosts(5) for details) then
+any name type matches for lookup.
+.TP 0.2i
+\(bu
+host : Do a standard host
+name to IP address resolution, using the system \fI/etc/hosts
+\fR, NIS, or DNS lookups. This method of name resolution
+is operating system dependent, for instance on IRIX or Solaris this
+may be controlled by the \fI/etc/nsswitch.conf\fR
+file). Note that this method is only used if the NetBIOS name
+type being queried is the 0x20 (server) name type, otherwise
+it is ignored.
+.TP 0.2i
+\(bu
+wins : Query a name with
+the IP address listed in the \fIwins server\fR
+parameter. If no WINS server has
+been specified this method will be ignored.
+.TP 0.2i
+\(bu
+bcast : Do a broadcast on
+each of the known local interfaces listed in the
+\fIinterfaces\fR
+parameter. This is the least reliable of the name resolution
+methods as it depends on the target host being on a locally
+connected subnet.
+.RE
+
+If this parameter is not set then the name resolve order
+defined in the \fIsmb.conf\fR file parameter
+(name resolve order) will be used.
+
+The default order is lmhosts, host, wins, bcast and without
+this parameter or any entry in the \fIname resolve order
+\fR parameter of the \fIsmb.conf\fR file the name resolution
+methods will be attempted in this order.
+.TP
+\fB-M NetBIOS name\fR
+This options allows you to send messages, using
+the "WinPopup" protocol, to another computer. Once a connection is
+established you then type your message, pressing ^D (control-D) to
+end.
+
+If the receiving computer is running WinPopup the user will
+receive the message and probably a beep. If they are not running
+WinPopup the message will be lost, and no error message will
+occur.
+
+The message is also automatically truncated if the message
+is over 1600 bytes, as this is the limit of the protocol.
+
+One useful trick is to cat the message through
+\fBsmbclient\fR. For example: \fB cat mymessage.txt | smbclient -M FRED \fR will
+send the message in the file \fImymessage.txt\fR
+to the machine FRED.
+
+You may also find the \fI-U\fR and
+\fI-I\fR options useful, as they allow you to
+control the FROM and TO parts of the message.
+
+See the message command parameter in the \fI smb.conf(5)\fR for a description of how to handle incoming
+WinPopup messages in Samba.
+
+\fBNote\fR: Copy WinPopup into the startup group
+on your WfWg PCs if you want them to always be able to receive
+messages.
+.TP
+\fB-i scope\fR
+This specifies a NetBIOS scope that smbclient will
+use to communicate with when generating NetBIOS names. For details
+on the use of NetBIOS scopes, see \fIrfc1001.txt\fR
+and \fIrfc1002.txt\fR.
+NetBIOS scopes are \fBvery\fR rarely used, only set
+this parameter if you are the system administrator in charge of all
+the NetBIOS systems you communicate with.
+.TP
+\fB-N\fR
+If specified, this parameter suppresses the normal
+password prompt from the client to the user. This is useful when
+accessing a service that does not require a password.
+
+Unless a password is specified on the command line or
+this parameter is specified, the client will request a
+password.
+.TP
+\fB-n NetBIOS name\fR
+By default, the client will use the local
+machine's hostname (in uppercase) as its NetBIOS name. This parameter
+allows you to override the host name and use whatever NetBIOS
+name you wish.
+.TP
+\fB-d debuglevel\fR
+\fIdebuglevel\fR is an integer from 0 to 10, or
+the letter 'A'.
+
+The default value if this parameter is not specified
+is zero.
+
+The higher this value, the more detail will be logged to
+the log files about the activities of the
+client. At level 0, only critical errors and serious warnings will
+be logged. Level 1 is a reasonable level for day to day running -
+it generates a small amount of information about operations
+carried out.
+
+Levels above 1 will generate considerable amounts of log
+data, and should only be used when investigating a problem.
+Levels above 3 are designed for use only by developers and
+generate HUGE amounts of log data, most of which is extremely
+cryptic. If \fIdebuglevel\fR is set to the letter 'A', then \fBall
+\fR debug messages will be printed. This setting
+is for developers only (and people who \fBreally\fR want
+to know how the code works internally).
+
+Note that specifying this parameter here will override
+the log level parameter in the \fIsmb.conf (5)\fR
+file.
+.TP
+\fB-p port\fR
+This number is the TCP port number that will be used
+when making connections to the server. The standard (well-known)
+TCP port number for an SMB/CIFS server is 139, which is the
+default.
+.TP
+\fB-l logfilename\fR
+If specified, \fIlogfilename\fR specifies a base filename
+into which operational data from the running client will be
+logged.
+
+The default base name is specified at compile time.
+
+The base name is used to generate actual log file names.
+For example, if the name specified was "log", the debug file
+would be \fIlog.client\fR.
+
+The log file generated is never removed by the client.
+.TP
+\fB-h\fR
+Print the usage message for the client.
+.TP
+\fB-I IP-address\fR
+\fIIP address\fR is the address of the server to connect to.
+It should be specified in standard "a.b.c.d" notation.
+
+Normally the client would attempt to locate a named
+SMB/CIFS server by looking it up via the NetBIOS name resolution
+mechanism described above in the \fIname resolve order\fR
+parameter above. Using this parameter will force the client
+to assume that the server is on the machine with the specified IP
+address and the NetBIOS name component of the resource being
+connected to will be ignored.
+
+There is no default for this parameter. If not supplied,
+it will be determined automatically by the client as described
+above.
+.TP
+\fB-E\fR
+This parameter causes the client to write messages
+to the standard error stream (stderr) rather than to the standard
+output stream.
+
+By default, the client writes messages to standard output
+- typically the user's tty.
+.TP
+\fB-U username[%pass]\fR
+Sets the SMB username or username and password.
+If %pass is not specified, The user will be prompted. The client
+will first check the \fBUSER\fR environment variable, then the
+\fBLOGNAME\fR variable and if either exists, the
+string is uppercased. Anything in these variables following a '%'
+sign will be treated as the password. If these environment
+variables are not found, the username GUEST
+is used.
+
+If the password is not included in these environment
+variables (using the %pass syntax), \fBsmbclient\fR will look for
+a \fBPASSWD\fR environment variable from which
+to read the password.
+
+A third option is to use a credentials file which
+contains the plaintext of the domain name, username and password. This
+option is mainly provided for scripts where the admin doesn't
+wish to pass the credentials on the command line or via environment
+variables. If this method is used, make certain that the permissions
+on the file restrict access from unwanted users. See the
+\fI-A\fR for more details.
+
+Be cautious about including passwords in scripts or in
+the \fBPASSWD\fR environment variable. Also, on
+many systems the command line of a running process may be seen
+via the \fBps\fR command to be safe always allow
+\fBsmbclient\fR to prompt for a password and type
+it in directly.
+.TP
+\fB-A filename\fR
+This option allows
+you to specify a file from which to read the username, domain name, and
+password used in the connection. The format of the file is
.nf
-
-username = <value>
+username = <value>
password = <value>
-domain = <value>
+domain = <value>
+
.fi
-
-Make certain that the permissions on the file restrict access from unwanted users\&.
-
-
-.TP
--U|--user=username[%password]
-Sets the SMB username or username and password\&.
-
-
-If %password is not specified, the user will be prompted\&. The client will first check the \fBUSER\fR environment variable, then the \fBLOGNAME\fR variable and if either exists, the string is uppercased\&. If these environmental variables are not found, the username \fBGUEST\fR is used\&.
-
-
-A third option is to use a credentials file which contains the plaintext of the username and password\&. This option is mainly provided for scripts where the admin does not wish to pass the credentials on the command line or via environment variables\&. If this method is used, make certain that the permissions on the file restrict access from unwanted users\&. See the \fI-A\fR for more details\&.
-
-
-Be cautious about including passwords in scripts\&. Also, on many systems the command line of a running process may be seen via the \fBps\fR command\&. To be safe always allow \fBrpcclient\fR to prompt for a password and type it in directly\&.
-
-
-.TP
--n <primary NetBIOS name>
-This option allows you to override the NetBIOS name that Samba uses for itself\&. This is identical to setting the \fINetBIOS name\fR parameter in the \fBsmb.conf\fR(5) file\&. However, a command line setting will take precedence over settings in \fBsmb.conf\fR(5)\&.
-
-
-.TP
--i <scope>
-This specifies a NetBIOS scope that \fBnmblookup\fR will use to communicate with when generating NetBIOS names\&. For details on the use of NetBIOS scopes, see rfc1001\&.txt and rfc1002\&.txt\&. NetBIOS scopes are \fBvery\fR rarely used, only set this parameter if you are the system administrator in charge of all the NetBIOS systems you communicate with\&.
-
-
-.TP
--W|--workgroup=domain
-Set the SMB domain of the username\&. This overrides the default domain which is the domain defined in smb\&.conf\&. If the domain specified is the same as the servers NetBIOS name, it causes the client to log on using the servers local SAM (as opposed to the Domain SAM)\&.
-
-
-.TP
--O socket options
-TCP socket options to set on the client socket\&. See the socket options parameter in the \fBsmb.conf\fR(5) manual page for the list of valid options\&.
-
-
-.TP
--T tar options
-smbclient may be used to create \fBtar(1) \fR compatible backups of all the files on an SMB/CIFS share\&. The secondary tar flags that can be given to this option are :
-
-
-\fIc\fR - Create a tar file on UNIX\&. Must be followed by the name of a tar file, tape device or "-" for standard output\&. If using standard output you must turn the log level to its lowest value -d0 to avoid corrupting your tar file\&. This flag is mutually exclusive with the \fIx\fR flag\&.
-
-\fIx\fR - Extract (restore) a local tar file back to a share\&. Unless the -D option is given, the tar files will be restored from the top level of the share\&. Must be followed by the name of the tar file, device or "-" for standard input\&. Mutually exclusive with the \fIc\fR flag\&. Restored files have their creation times (mtime) set to the date saved in the tar file\&. Directories currently do not get their creation dates restored properly\&.
-
-\fII\fR - Include files and directories\&. Is the default behavior when filenames are specified above\&. Causes tar files to be included in an extract or create (and therefore everything else to be excluded)\&. See example below\&. Filename globbing works in one of two ways\&. See r below\&.
-
-\fIX\fR - Exclude files and directories\&. Causes tar files to be excluded from an extract or create\&. See example below\&. Filename globbing works in one of two ways now\&. See \fIr\fR below\&.
-
-\fIb\fR - Blocksize\&. Must be followed by a valid (greater than zero) blocksize\&. Causes tar file to be written out in blocksize*TBLOCK (usually 512 byte) blocks\&.
-
-\fIg\fR - Incremental\&. Only back up files that have the archive bit set\&. Useful only with the \fIc\fR flag\&.
-
-\fIq\fR - Quiet\&. Keeps tar from printing diagnostics as it works\&. This is the same as tarmode quiet\&.
-
-\fIr\fR - Regular expression include or exclude\&. Uses regular expression matching for excluding or excluding files if compiled with HAVE_REGEX_H\&. However this mode can be very slow\&. If not compiled with HAVE_REGEX_H, does a limited wildcard match on '*' and '?'\&.
-
-\fIN\fR - Newer than\&. Must be followed by the name of a file whose date is compared against files found on the share during a create\&. Only files newer than the file specified are backed up to the tar file\&. Useful only with the \fIc\fR flag\&.
-
-\fIa\fR - Set archive bit\&. Causes the archive bit to be reset when a file is backed up\&. Useful with the \fIg\fR and \fIc\fR flags\&.
+If the domain parameter is missing the current workgroup name
+is used instead. Make certain that the permissions on the file restrict
+access from unwanted users.
+.TP
+\fB-L\fR
+This option allows you to look at what services
+are available on a server. You use it as \fBsmbclient -L
+host\fR and a list should appear. The \fI-I
+\fR option may be useful if your NetBIOS names don't
+match your TCP/IP DNS host names or if you are trying to reach a
+host on another network.
+.TP
+\fB-t terminal code\fR
+This option tells \fBsmbclient\fR how to interpret
+filenames coming from the remote server. Usually Asian language
+multibyte UNIX implementations use different character sets than
+SMB/CIFS servers (\fBEUC\fR instead of \fB SJIS\fR for example). Setting this parameter will let
+\fBsmbclient\fR convert between the UNIX filenames and
+the SMB filenames correctly. This option has not been seriously tested
+and may have some problems.
+
+The terminal codes include CWsjis, CWeuc, CWjis7, CWjis8,
+CWjunet, CWhex, CWcap. This is not a complete list, check the Samba
+source code for the complete list.
+.TP
+\fB-b buffersize\fR
+This option changes the transmit/send buffer
+size when getting or putting a file from/to the server. The default
+is 65520 bytes. Setting this value smaller (to 1200 bytes) has been
+observed to speed up file transfers to and from a Win9x server.
+.TP
+\fB-W WORKGROUP\fR
+Override the default workgroup (domain) specified
+in the workgroup parameter of the \fIsmb.conf\fR
+file for this connection. This may be needed to connect to some
+servers.
+.TP
+\fB-T tar options\fR
+smbclient may be used to create \fBtar(1)
+\fR compatible backups of all the files on an SMB/CIFS
+share. The secondary tar flags that can be given to this option
+are :
+.RS
+.TP 0.2i
+\(bu
+\fIc\fR - Create a tar file on UNIX.
+Must be followed by the name of a tar file, tape device
+or "-" for standard output. If using standard output you must
+turn the log level to its lowest value -d0 to avoid corrupting
+your tar file. This flag is mutually exclusive with the
+\fIx\fR flag.
+.TP 0.2i
+\(bu
+\fIx\fR - Extract (restore) a local
+tar file back to a share. Unless the -D option is given, the tar
+files will be restored from the top level of the share. Must be
+followed by the name of the tar file, device or "-" for standard
+input. Mutually exclusive with the \fIc\fR flag.
+Restored files have their creation times (mtime) set to the
+date saved in the tar file. Directories currently do not get
+their creation dates restored properly.
+.TP 0.2i
+\(bu
+\fII\fR - Include files and directories.
+Is the default behavior when filenames are specified above. Causes
+tar files to be included in an extract or create (and therefore
+everything else to be excluded). See example below. Filename globbing
+works in one of two ways. See r below.
+.TP 0.2i
+\(bu
+\fIX\fR - Exclude files and directories.
+Causes tar files to be excluded from an extract or create. See
+example below. Filename globbing works in one of two ways now.
+See \fIr\fR below.
+.TP 0.2i
+\(bu
+\fIb\fR - Blocksize. Must be followed
+by a valid (greater than zero) blocksize. Causes tar file to be
+written out in blocksize*TBLOCK (usually 512 byte) blocks.
+.TP 0.2i
+\(bu
+\fIg\fR - Incremental. Only back up
+files that have the archive bit set. Useful only with the
+\fIc\fR flag.
+.TP 0.2i
+\(bu
+\fIq\fR - Quiet. Keeps tar from printing
+diagnostics as it works. This is the same as tarmode quiet.
+.TP 0.2i
+\(bu
+\fIr\fR - Regular expression include
+or exclude. Uses regular expression matching for
+excluding or excluding files if compiled with HAVE_REGEX_H.
+However this mode can be very slow. If not compiled with
+HAVE_REGEX_H, does a limited wildcard match on '*' and '?'.
+.TP 0.2i
+\(bu
+\fIN\fR - Newer than. Must be followed
+by the name of a file whose date is compared against files found
+on the share during a create. Only files newer than the file
+specified are backed up to the tar file. Useful only with the
+\fIc\fR flag.
+.TP 0.2i
+\(bu
+\fIa\fR - Set archive bit. Causes the
+archive bit to be reset when a file is backed up. Useful with the
+\fIg\fR and \fIc\fR flags.
+.RE
\fBTar Long File Names\fR
-
-\fBsmbclient\fR's tar option now supports long file names both on backup and restore\&. However, the full path name of the file must be less than 1024 bytes\&. Also, when a tar archive is created, \fBsmbclient\fR's tar option places all files in the archive with relative names, not absolute names\&.
-
+\fBsmbclient\fR's tar option now supports long
+file names both on backup and restore. However, the full path
+name of the file must be less than 1024 bytes. Also, when
+a tar archive is created, \fBsmbclient\fR's tar option places all
+files in the archive with relative names, not absolute names.
\fBTar Filenames\fR
-
-All file names can be given as DOS path names (with '\\\\' as the component separator) or as UNIX path names (with '/' as the component separator)\&.
-
+All file names can be given as DOS path names (with '\\'
+as the component separator) or as UNIX path names (with '/' as
+the component separator).
\fBExamples\fR
+Restore from tar file \fIbackup.tar\fR into myshare on mypc
+(no password on share).
-Restore from tar file \fIbackup\&.tar\fR into myshare on mypc (no password on share)\&.
-
-
-\fBsmbclient //mypc/yshare "" -N -Tx backup.tar \fR
-
+\fBsmbclient //mypc/yshare "" -N -Tx backup.tar
+\fR
Restore everything except \fIusers/docs\fR
+\fBsmbclient //mypc/myshare "" -N -TXx backup.tar
+users/docs\fR
-\fBsmbclient //mypc/myshare "" -N -TXx backup.tar users/docs\fR
-
-
-Create a tar file of the files beneath \fI users/docs\fR\&.
-
-
-\fBsmbclient //mypc/myshare "" -N -Tc backup.tar users/docs \fR
-
-
-Create the same tar file as above, but now use a DOS path name\&.
-
-
-\fBsmbclient //mypc/myshare "" -N -tc backup.tar users\edocs \fR
-
+Create a tar file of the files beneath \fI users/docs\fR.
-Create a tar file of all the files and directories in the share\&.
+\fBsmbclient //mypc/myshare "" -N -Tc
+backup.tar users/docs \fR
+Create the same tar file as above, but now use
+a DOS path name.
-\fBsmbclient //mypc/myshare "" -N -Tc backup.tar * \fR
+\fBsmbclient //mypc/myshare "" -N -tc backup.tar
+users\\edocs \fR
+Create a tar file of all the files and directories in
+the share.
+\fBsmbclient //mypc/myshare "" -N -Tc backup.tar *
+\fR
.TP
--D initial directory
-Change to initial directory before starting\&. Probably only of any use with the tar -T option\&.
-
-
+\fB-D initial directory\fR
+Change to initial directory before starting. Probably
+only of any use with the tar -T option.
.TP
--c command string
-command string is a semicolon-separated list of commands to be executed instead of prompting from stdin\&. \fI -N\fR is implied by \fI-c\fR\&.
-
-
-This is particularly useful in scripts and for printing stdin to the server, e\&.g\&. \fB-c 'print -'\fR\&.
-
+\fB-c command string\fR
+command string is a semicolon-separated list of
+commands to be executed instead of prompting from stdin. \fI -N\fR is implied by \fI-c\fR.
+This is particularly useful in scripts and for printing stdin
+to the server, e.g. \fB-c 'print -'\fR.
.SH "OPERATIONS"
-
.PP
-Once the client is running, the user is presented with a prompt :
-
+Once the client is running, the user is presented with
+a prompt :
.PP
-smb:\\>
-
+smb:\\>
.PP
-The backslash ("\\\\") indicates the current working directory on the server, and will change if the current working directory is changed\&.
-
+The backslash ("\\") indicates the current working directory
+on the server, and will change if the current working directory
+is changed.
.PP
-The prompt indicates that the client is ready and waiting to carry out a user command\&. Each command is a single word, optionally followed by parameters specific to that command\&. Command and parameters are space-delimited unless these notes specifically state otherwise\&. All commands are case-insensitive\&. Parameters to commands may or may not be case sensitive, depending on the command\&.
-
+The prompt indicates that the client is ready and waiting to
+carry out a user command. Each command is a single word, optionally
+followed by parameters specific to that command. Command and parameters
+are space-delimited unless these notes specifically
+state otherwise. All commands are case-insensitive. Parameters to
+commands may or may not be case sensitive, depending on the command.
.PP
-You can specify file names which have spaces in them by quoting the name with double quotes, for example "a long file name"\&.
-
+You can specify file names which have spaces in them by quoting
+the name with double quotes, for example "a long file name".
.PP
-Parameters shown in square brackets (e\&.g\&., "[parameter]") are optional\&. If not given, the command will use suitable defaults\&. Parameters shown in angle brackets (e\&.g\&., "<parameter>") are required\&.
-
+Parameters shown in square brackets (e.g., "[parameter]") are
+optional. If not given, the command will use suitable defaults. Parameters
+shown in angle brackets (e.g., "<parameter>") are required.
.PP
-Note that all commands operating on the server are actually performed by issuing a request to the server\&. Thus the behavior may vary from server to server, depending on how the server was implemented\&.
-
+Note that all commands operating on the server are actually
+performed by issuing a request to the server. Thus the behavior may
+vary from server to server, depending on how the server was implemented.
.PP
-The commands available are given here in alphabetical order\&.
-
-.TP
-? [command]
-If \fIcommand\fR is specified, the ? command will display a brief informative message about the specified command\&. If no command is specified, a list of available commands will be displayed\&.
-
-
-.TP
-! [shell command]
-If \fIshell command\fR is specified, the ! command will execute a shell locally and run the specified shell command\&. If no command is specified, a local shell will be run\&.
-
-
-.TP
-altname file
-The client will request that the server return the "alternate" name (the 8\&.3 name) for a file or directory\&.
-
-
-.TP
-cancel jobid0 [jobid1] \&.\&.\&. [jobidN]
-The client will request that the server cancel the printjobs identified by the given numeric print job ids\&.
-
-
-.TP
-chmod file mode in octal
-This command depends on the server supporting the CIFS UNIX extensions and will fail if the server does not\&. The client requests that the server change the UNIX permissions to the given octal mode, in standard UNIX format\&.
-
-
-.TP
-chown file uid gid
-This command depends on the server supporting the CIFS UNIX extensions and will fail if the server does not\&. The client requests that the server change the UNIX user and group ownership to the given decimal values\&. Note there is currently no way to remotely look up the UNIX uid and gid values for a given name\&. This may be addressed in future versions of the CIFS UNIX extensions\&.
-
-
-.TP
-cd [directory name]
-If "directory name" is specified, the current working directory on the server will be changed to the directory specified\&. This operation will fail if for any reason the specified directory is inaccessible\&.
-
-
-If no directory name is specified, the current working directory on the server will be reported\&.
-
-
-.TP
-del <mask>
-The client will request that the server attempt to delete all files matching \fImask\fR from the current working directory on the server\&.
-
-
-.TP
-dir <mask>
-A list of the files matching \fImask\fR in the current working directory on the server will be retrieved from the server and displayed\&.
-
-
-.TP
-exit
-Terminate the connection with the server and exit from the program\&.
-
-
-.TP
-get <remote file name> [local file name]
-Copy the file called \fIremote file name\fR from the server to the machine running the client\&. If specified, name the local copy \fIlocal file name\fR\&. Note that all transfers in \fBsmbclient\fR are binary\&. See also the lowercase command\&.
-
-
-.TP
-help [command]
-See the ? command above\&.
-
-
-.TP
-lcd [directory name]
-If \fIdirectory name\fR is specified, the current working directory on the local machine will be changed to the directory specified\&. This operation will fail if for any reason the specified directory is inaccessible\&.
-
-
-If no directory name is specified, the name of the current working directory on the local machine will be reported\&.
-
-
-.TP
-link source destination
-This command depends on the server supporting the CIFS UNIX extensions and will fail if the server does not\&. The client requests that the server create a hard link between the source and destination files\&. The source file must not exist\&.
-
-
-.TP
-lowercase
-Toggle lowercasing of filenames for the get and mget commands\&.
-
-
-When lowercasing is toggled ON, local filenames are converted to lowercase when using the get and mget commands\&. This is often useful when copying (say) MSDOS files from a server, because lowercase filenames are the norm on UNIX systems\&.
-
-
-.TP
-ls <mask>
-See the dir command above\&.
-
-
-.TP
-mask <mask>
-This command allows the user to set up a mask which will be used during recursive operation of the mget and mput commands\&.
-
-
-The masks specified to the mget and mput commands act as filters for directories rather than files when recursion is toggled ON\&.
-
-
-The mask specified with the mask command is necessary to filter files within those directories\&. For example, if the mask specified in an mget command is "source*" and the mask specified with the mask command is "*\&.c" and recursion is toggled ON, the mget command will retrieve all files matching "*\&.c" in all directories below and including all directories matching "source*" in the current working directory\&.
-
-
-Note that the value for mask defaults to blank (equivalent to "*") and remains so until the mask command is used to change it\&. It retains the most recently specified value indefinitely\&. To avoid unexpected results it would be wise to change the value of mask back to "*" after using the mget or mput commands\&.
-
-
-.TP
-md <directory name>
-See the mkdir command\&.
-
-
-.TP
-mget <mask>
-Copy all files matching \fImask\fR from the server to the machine running the client\&.
-
-
-Note that \fImask\fR is interpreted differently during recursive operation and non-recursive operation - refer to the recurse and mask commands for more information\&. Note that all transfers in \fBsmbclient\fR are binary\&. See also the lowercase command\&.
-
-
-.TP
-mkdir <directory name>
-Create a new directory on the server (user access privileges permitting) with the specified name\&.
-
-
-.TP
-mput <mask>
-Copy all files matching \fImask\fR in the current working directory on the local machine to the current working directory on the server\&.
-
-
-Note that \fImask\fR is interpreted differently during recursive operation and non-recursive operation - refer to the recurse and mask commands for more information\&. Note that all transfers in \fBsmbclient\fR are binary\&.
-
-
-.TP
-print <file name>
-Print the specified file from the local machine through a printable service on the server\&.
-
-
-See also the printmode command\&.
-
-
-.TP
-printmode <graphics or text>
-Set the print mode to suit either binary data (such as graphical information) or text\&. Subsequent print commands will use the currently set print mode\&.
-
-
-.TP
-prompt
-Toggle prompting for filenames during operation of the mget and mput commands\&.
-
-
-When toggled ON, the user will be prompted to confirm the transfer of each file during these commands\&. When toggled OFF, all specified files will be transferred without prompting\&.
-
-
-.TP
-put <local file name> [remote file name]
-Copy the file called \fIlocal file name\fR from the machine running the client to the server\&. If specified, name the remote copy \fIremote file name\fR\&. Note that all transfers in \fBsmbclient\fR are binary\&. See also the lowercase command\&.
-
-
-.TP
-queue
-Displays the print queue, showing the job id, name, size and current status\&.
-
-
-.TP
-quit
-See the exit command\&.
-
-
-.TP
-rd <directory name>
-See the rmdir command\&.
-
-
-.TP
-recurse
-Toggle directory recursion for the commands mget and mput\&.
-
-
-When toggled ON, these commands will process all directories in the source directory (i\&.e\&., the directory they are copying from ) and will recurse into any that match the mask specified to the command\&. Only files that match the mask specified using the mask command will be retrieved\&. See also the mask command\&.
-
-
-When recursion is toggled OFF, only files from the current working directory on the source machine that match the mask specified to the mget or mput commands will be copied, and any mask specified using the mask command will be ignored\&.
-
-
-.TP
-rm <mask>
-Remove all files matching \fImask\fR from the current working directory on the server\&.
-
-
-.TP
-rmdir <directory name>
-Remove the specified directory (user access privileges permitting) from the server\&.
-
-
-.TP
-setmode <filename> <perm=[+|\\-]rsha>
-A version of the DOS attrib command to set file permissions\&. For example:
-
+The commands available are given here in alphabetical order.
+.TP
+\fB? [command]\fR
+If \fIcommand\fR is specified, the ? command will display
+a brief informative message about the specified command. If no
+command is specified, a list of available commands will
+be displayed.
+.TP
+\fB! [shell command]\fR
+If \fIshell command\fR is specified, the !
+command will execute a shell locally and run the specified shell
+command. If no command is specified, a local shell will be run.
+.TP
+\fBaltname file\fR
+The client will request that the server return
+the "alternate" name (the 8.3 name) for a file or directory.
+.TP
+\fBcancel jobid0 [jobid1] ... [jobidN]\fR
+The client will request that the server cancel
+the printjobs identified by the given numeric print job ids.
+.TP
+\fBchmod file mode in octal\fR
+This command depends on the server supporting the CIFS
+UNIX extensions and will fail if the server does not. The client requests that the server
+change the UNIX permissions to the given octal mode, in standard UNIX format.
+.TP
+\fBchown file uid gid\fR
+This command depends on the server supporting the CIFS
+UNIX extensions and will fail if the server does not. The client requests that the server
+change the UNIX user and group ownership to the given decimal values. Note there is
+currently no way to remotely look up the UNIX uid and gid values for a given name.
+This may be addressed in future versions of the CIFS UNIX extensions.
+.TP
+\fBcd [directory name]\fR
+If "directory name" is specified, the current
+working directory on the server will be changed to the directory
+specified. This operation will fail if for any reason the specified
+directory is inaccessible.
+
+If no directory name is specified, the current working
+directory on the server will be reported.
+.TP
+\fBdel <mask>\fR
+The client will request that the server attempt
+to delete all files matching \fImask\fR from the current working
+directory on the server.
+.TP
+\fBdir <mask>\fR
+A list of the files matching \fImask\fR in the current
+working directory on the server will be retrieved from the server
+and displayed.
+.TP
+\fBexit\fR
+Terminate the connection with the server and exit
+from the program.
+.TP
+\fBget <remote file name> [local file name]\fR
+Copy the file called \fIremote file name\fR from
+the server to the machine running the client. If specified, name
+the local copy \fIlocal file name\fR. Note that all transfers in
+\fBsmbclient\fR are binary. See also the
+lowercase command.
+.TP
+\fBhelp [command]\fR
+See the ? command above.
+.TP
+\fBlcd [directory name]\fR
+If \fIdirectory name\fR is specified, the current
+working directory on the local machine will be changed to
+the directory specified. This operation will fail if for any
+reason the specified directory is inaccessible.
+
+If no directory name is specified, the name of the
+current working directory on the local machine will be reported.
+.TP
+\fBlink source destination\fR
+This command depends on the server supporting the CIFS
+UNIX extensions and will fail if the server does not. The client requests that the server
+create a hard link between the source and destination files. The source file
+must not exist.
+.TP
+\fBlowercase\fR
+Toggle lowercasing of filenames for the get and
+mget commands.
+
+When lowercasing is toggled ON, local filenames are converted
+to lowercase when using the get and mget commands. This is
+often useful when copying (say) MSDOS files from a server, because
+lowercase filenames are the norm on UNIX systems.
+.TP
+\fBls <mask>\fR
+See the dir command above.
+.TP
+\fBmask <mask>\fR
+This command allows the user to set up a mask
+which will be used during recursive operation of the mget and
+mput commands.
+
+The masks specified to the mget and mput commands act as
+filters for directories rather than files when recursion is
+toggled ON.
+
+The mask specified with the mask command is necessary
+to filter files within those directories. For example, if the
+mask specified in an mget command is "source*" and the mask
+specified with the mask command is "*.c" and recursion is
+toggled ON, the mget command will retrieve all files matching
+"*.c" in all directories below and including all directories
+matching "source*" in the current working directory.
+
+Note that the value for mask defaults to blank (equivalent
+to "*") and remains so until the mask command is used to change it.
+It retains the most recently specified value indefinitely. To
+avoid unexpected results it would be wise to change the value of
+mask back to "*" after using the mget or mput commands.
+.TP
+\fBmd <directory name>\fR
+See the mkdir command.
+.TP
+\fBmget <mask>\fR
+Copy all files matching \fImask\fR from the server to
+the machine running the client.
+
+Note that \fImask\fR is interpreted differently during recursive
+operation and non-recursive operation - refer to the recurse and
+mask commands for more information. Note that all transfers in
+\fBsmbclient\fR are binary. See also the lowercase command.
+.TP
+\fBmkdir <directory name>\fR
+Create a new directory on the server (user access
+privileges permitting) with the specified name.
+.TP
+\fBmput <mask>\fR
+Copy all files matching \fImask\fR in the current working
+directory on the local machine to the current working directory on
+the server.
+
+Note that \fImask\fR is interpreted differently during recursive
+operation and non-recursive operation - refer to the recurse and mask
+commands for more information. Note that all transfers in \fBsmbclient\fR
+are binary.
+.TP
+\fBprint <file name>\fR
+Print the specified file from the local machine
+through a printable service on the server.
+
+See also the printmode command.
+.TP
+\fBprintmode <graphics or text>\fR
+Set the print mode to suit either binary data
+(such as graphical information) or text. Subsequent print
+commands will use the currently set print mode.
+.TP
+\fBprompt\fR
+Toggle prompting for filenames during operation
+of the mget and mput commands.
+
+When toggled ON, the user will be prompted to confirm
+the transfer of each file during these commands. When toggled
+OFF, all specified files will be transferred without prompting.
+.TP
+\fBput <local file name> [remote file name]\fR
+Copy the file called \fIlocal file name\fR from the
+machine running the client to the server. If specified,
+name the remote copy \fIremote file name\fR. Note that all transfers
+in \fBsmbclient\fR are binary. See also the lowercase command.
+.TP
+\fBqueue\fR
+Displays the print queue, showing the job id,
+name, size and current status.
+.TP
+\fBquit\fR
+See the exit command.
+.TP
+\fBrd <directory name>\fR
+See the rmdir command.
+.TP
+\fBrecurse\fR
+Toggle directory recursion for the commands mget
+and mput.
+
+When toggled ON, these commands will process all directories
+in the source directory (i.e., the directory they are copying
+from ) and will recurse into any that match the mask specified
+to the command. Only files that match the mask specified using
+the mask command will be retrieved. See also the mask command.
+
+When recursion is toggled OFF, only files from the current
+working directory on the source machine that match the mask specified
+to the mget or mput commands will be copied, and any mask specified
+using the mask command will be ignored.
+.TP
+\fBrm <mask>\fR
+Remove all files matching \fImask\fR from the current
+working directory on the server.
+.TP
+\fBrmdir <directory name>\fR
+Remove the specified directory (user access
+privileges permitting) from the server.
+.TP
+\fBsetmode <filename> <perm=[+|\\-]rsha>\fR
+A version of the DOS attrib command to set
+file permissions. For example:
\fBsetmode myfile +r \fR
-
-would make myfile read only\&.
-
-
-.TP
-symlink source destination
-This command depends on the server supporting the CIFS UNIX extensions and will fail if the server does not\&. The client requests that the server create a symbolic hard link between the source and destination files\&. The source file must not exist\&. Note that the server will not create a link to any path that lies outside the currently connected share\&. This is enforced by the Samba server\&.
-
-
-.TP
-tar <c|x>[IXbgNa]
-Performs a tar operation - see the \fI-T \fR command line option above\&. Behavior may be affected by the tarmode command (see below)\&. Using g (incremental) and N (newer) will affect tarmode settings\&. Note that using the "-" option with tar x may not work - use the command line option instead\&.
-
-
-.TP
-blocksize <blocksize>
-Blocksize\&. Must be followed by a valid (greater than zero) blocksize\&. Causes tar file to be written out in \fIblocksize\fR*TBLOCK (usually 512 byte) blocks\&.
-
-
-.TP
-tarmode <full|inc|reset|noreset>
-Changes tar's behavior with regard to archive bits\&. In full mode, tar will back up everything regardless of the archive bit setting (this is the default mode)\&. In incremental mode, tar will only back up files with the archive bit set\&. In reset mode, tar will reset the archive bit on all files it backs up (implies read/write share)\&.
-
-
+would make myfile read only.
+.TP
+\fBsymlink source destination\fR
+This command depends on the server supporting the CIFS
+UNIX extensions and will fail if the server does not. The client requests that the server
+create a symbolic hard link between the source and destination files. The source file
+must not exist. Note that the server will not create a link to any path that lies
+outside the currently connected share. This is enforced by the Samba server.
+.TP
+\fBtar <c|x>[IXbgNa]\fR
+Performs a tar operation - see the \fI-T
+\fR command line option above. Behavior may be affected
+by the tarmode command (see below). Using g (incremental) and N
+(newer) will affect tarmode settings. Note that using the "-" option
+with tar x may not work - use the command line option instead.
+.TP
+\fBblocksize <blocksize>\fR
+Blocksize. Must be followed by a valid (greater
+than zero) blocksize. Causes tar file to be written out in
+\fIblocksize\fR*TBLOCK (usually 512 byte) blocks.
+.TP
+\fBtarmode <full|inc|reset|noreset>\fR
+Changes tar's behavior with regard to archive
+bits. In full mode, tar will back up everything regardless of the
+archive bit setting (this is the default mode). In incremental mode,
+tar will only back up files with the archive bit set. In reset mode,
+tar will reset the archive bit on all files it backs up (implies
+read/write share).
.SH "NOTES"
-
.PP
-Some servers are fussy about the case of supplied usernames, passwords, share names (AKA service names) and machine names\&. If you fail to connect try giving all parameters in uppercase\&.
-
+Some servers are fussy about the case of supplied usernames,
+passwords, share names (AKA service names) and machine names.
+If you fail to connect try giving all parameters in uppercase.
.PP
-It is often necessary to use the -n option when connecting to some types of servers\&. For example OS/2 LanManager insists on a valid NetBIOS name being used, so you need to supply a valid name that would be known to the server\&.
-
+It is often necessary to use the -n option when connecting
+to some types of servers. For example OS/2 LanManager insists
+on a valid NetBIOS name being used, so you need to supply a valid
+name that would be known to the server.
.PP
-smbclient supports long file names where the server supports the LANMAN2 protocol or above\&.
-
+smbclient supports long file names where the server
+supports the LANMAN2 protocol or above.
.SH "ENVIRONMENT VARIABLES"
-
.PP
-The variable \fBUSER\fR may contain the username of the person using the client\&. This information is used only if the protocol level is high enough to support session-level passwords\&.
-
+The variable \fBUSER\fR may contain the
+username of the person using the client. This information is
+used only if the protocol level is high enough to support
+session-level passwords.
.PP
-The variable \fBPASSWD\fR may contain the password of the person using the client\&. This information is used only if the protocol level is high enough to support session-level passwords\&.
-
+The variable \fBPASSWD\fR may contain
+the password of the person using the client. This information is
+used only if the protocol level is high enough to support
+session-level passwords.
.PP
-The variable \fBLIBSMB_PROG\fR may contain the path, executed with system(), which the client should connect to instead of connecting to a server\&. This functionality is primarily intended as a development aid, and works best when using a LMHOSTS file
-
+The variable \fBLIBSMB_PROG\fR may contain
+the path, executed with system(), which the client should connect
+to instead of connecting to a server. This functionality is primarily
+intended as a development aid, and works best when using a LMHOSTS
+file
.SH "INSTALLATION"
-
.PP
-The location of the client program is a matter for individual system administrators\&. The following are thus suggestions only\&.
-
+The location of the client program is a matter for
+individual system administrators. The following are thus
+suggestions only.
.PP
-It is recommended that the smbclient software be installed in the \fI/usr/local/samba/bin/\fR or \fI /usr/samba/bin/\fR directory, this directory readable by all, writeable only by root\&. The client program itself should be executable by all\&. The client should \fBNOT\fR be setuid or setgid!
-
+It is recommended that the smbclient software be installed
+in the \fI/usr/local/samba/bin/\fR or \fI /usr/samba/bin/\fR directory, this directory readable
+by all, writeable only by root. The client program itself should
+be executable by all. The client should \fBNOT\fR be
+setuid or setgid!
.PP
-The client log files should be put in a directory readable and writeable only by the user\&.
-
+The client log files should be put in a directory readable
+and writeable only by the user.
.PP
-To test the client, you will need to know the name of a running SMB/CIFS server\&. It is possible to run \fBsmbd\fR(8) as an ordinary user - running that server as a daemon on a user-accessible port (typically any port number over 1024) would provide a suitable test server\&.
-
+To test the client, you will need to know the name of a
+running SMB/CIFS server. It is possible to run \fBsmbd(8)
+\fR as an ordinary user - running that server as a daemon
+on a user-accessible port (typically any port number over 1024)
+would provide a suitable test server.
.SH "DIAGNOSTICS"
-
.PP
-Most diagnostics issued by the client are logged in a specified log file\&. The log file name is specified at compile time, but may be overridden on the command line\&.
-
+Most diagnostics issued by the client are logged in a
+specified log file. The log file name is specified at compile time,
+but may be overridden on the command line.
.PP
-The number and nature of diagnostics available depends on the debug level used by the client\&. If you have problems, set the debug level to 3 and peruse the log files\&.
-
+The number and nature of diagnostics available depends
+on the debug level used by the client. If you have problems,
+set the debug level to 3 and peruse the log files.
.SH "VERSION"
-
.PP
-This man page is correct for version 2\&.2 of the Samba suite\&.
-
+This man page is correct for version 2.2 of
+the Samba suite.
.SH "AUTHOR"
-
.PP
-The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&.
-
+The original Samba software and related utilities
+were created by Andrew Tridgell. Samba is now developed
+by the Samba Team as an Open Source project similar
+to the way the Linux kernel is developed.
.PP
-The original Samba man pages were written by Karl Auer\&. The man page sources were converted to YODL format (another excellent piece of Open Source software, available at ftp://ftp\&.icce\&.rug\&.nl/pub/unix/) and updated for the Samba 2\&.0 release by Jeremy Allison\&. The conversion to DocBook for Samba 2\&.2 was done by Gerald Carter\&. The conversion to DocBook XML 4\&.2 for Samba 3\&.0 was done by Alexander Bokovoy\&.
-
+The original Samba man pages were written by Karl Auer.
+The man page sources were converted to YODL format (another
+excellent piece of Open Source software, available at
+ftp://ftp.icce.rug.nl/pub/unix/ <URL:ftp://ftp.icce.rug.nl/pub/unix/>) and updated for the Samba 2.0
+release by Jeremy Allison. The conversion to DocBook for
+Samba 2.2 was done by Gerald Carter
diff --git a/docs/manpages/smbcontrol.1 b/docs/manpages/smbcontrol.1
index 44d419f919..d69e0978a4 100644
--- a/docs/manpages/smbcontrol.1
+++ b/docs/manpages/smbcontrol.1
@@ -1,216 +1,151 @@
-.\"Generated by db2man.xsl. Don't modify this, modify the source.
-.de Sh \" Subsection
-.br
-.if t .Sp
-.ne 5
-.PP
-\fB\\$1\fR
-.PP
-..
-.de Sp \" Vertical space (when we can't use .PP)
-.if t .sp .5v
-.if n .sp
-..
-.de Ip \" List item
-.br
-.ie \\n(.$>=3 .ne \\$3
-.el .ne 3
-.IP "\\$1" \\$2
-..
-.TH "SMBCONTROL" 1 "" "" ""
+.\" This manpage has been automatically generated by docbook2man
+.\" from a DocBook document. This tool can be found at:
+.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
+.\" Please send any bug reports, improvements, comments, patches,
+.\" etc. to Steve Cheng <steve@ggi-project.org>.
+.TH "SMBCONTROL" "1" "04 March 2003" "" ""
.SH NAME
smbcontrol \- send messages to smbd, nmbd or winbindd processes
-.SH "SYNOPSIS"
+.SH SYNOPSIS
-.nf
-\fBsmbcontrol\fR [-i] [-s]
-.fi
+\fBsmbcontrol\fR [ \fB-i\fR ]
-.nf
-\fBsmbcontrol\fR [destination] [message-type] [parameter]
-.fi
-.SH "DESCRIPTION"
+\fBsmbcontrol\fR [ \fBdestination\fR ] [ \fBmessage-type\fR ] [ \fBparameter\fR ]
+.SH "DESCRIPTION"
.PP
-This tool is part of the \fBSamba\fR(7) suite\&.
-
+This tool is part of the Samba suite.
.PP
-\fBsmbcontrol\fR is a very small program, which sends messages to a \fBsmbd\fR(8), a \fBnmbd\fR(8), or a \fBwinbindd\fR(8) daemon running on the system\&.
-
+\fBsmbcontrol\fR is a very small program, which
+sends messages to an smbd(8)
+an nmbd(8)
+or a winbindd(8)
+daemon running on the system.
.SH "OPTIONS"
-
-.TP
--h|--help
-Print a summary of command line options\&.
-
-
-.TP
--s <configuration file>
-The file specified contains the configuration details required by the server\&. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is to provide\&. See \fI smb\&.conf(5)\fR for more information\&. The default configuration file name is determined at compile time\&.
-
-
-.TP
--i
-Run interactively\&. Individual commands of the form destination message-type parameters can be entered on STDIN\&. An empty command line or a "q" will quit the program\&.
-
-
-.TP
-destination
-One of \fInmbd\fR, \fIsmbd\fR or a process ID\&.
-
-
-The \fIsmbd\fR destination causes the message to "broadcast" to all smbd daemons\&.
-
-
-The \fInmbd\fR destination causes the message to be sent to the nmbd daemon specified in the \fInmbd\&.pid\fR file\&.
-
-
-If a single process ID is given, the message is sent to only that process\&.
-
-
-.TP
-message-type
-Type of message to send\&. See the section \fBMESSAGE-TYPES\fR for details\&.
-
-
-.TP
-parameters
-any parameters required for the message-type
-
-
-.SH "MESSAGE-TYPES"
-
-.PP
-Available message types are:
-
-.TP
-close-share
-Order smbd to close the client connections to the named share\&. Note that this doesn't affect client connections to any other shares\&. This message-type takes an argument of the share name for which client connections will be closed, or the "*" character which will close all currently open shares\&. This may be useful if you made changes to the access controls on the share\&. This message can only be sent to \fBsmbd\fR\&.
-
-
-.TP
-debug
-Set debug level to the value specified by the parameter\&. This can be sent to any of the destinations\&.
-
-
.TP
-force-election
-This message causes the \fBnmbd\fR daemon to force a new browse master election\&.
-
-
-.TP
-ping
-Send specified number of "ping" messages and wait for the same number of reply "pong" messages\&. This can be sent to any of the destinations\&.
-
-
-.TP
-profile
-Change profile settings of a daemon, based on the parameter\&. The parameter can be "on" to turn on profile stats collection, "off" to turn off profile stats collection, "count" to enable only collection of count stats (time stats are disabled), and "flush" to zero the current profile stats\&. This can be sent to any smbd or nmbd destinations\&.
-
-
-.TP
-debuglevel
-Request debuglevel of a certain daemon and write it to stdout\&. This can be sent to any of the destinations\&.
-
-
-.TP
-profilelevel
-Request profilelevel of a certain daemon and write it to stdout\&. This can be sent to any smbd or nmbd destinations\&.
-
-
-.TP
-printnotify
-Order smbd to send a printer notify message to any Windows NT clients connected to a printer\&. This message-type takes the following arguments:
-
-
-
+\fB-i\fR
+Run interactively. Individual commands
+of the form destination message-type parameters can be entered
+on STDIN. An empty command line or a "q" will quit the
+program.
+.TP
+\fBdestination\fR
+One of \fInmbd\fR
+\fIsmbd\fR or a process ID.
+
+The \fIsmbd\fR destination causes the
+message to "broadcast" to all smbd daemons.
+
+The \fInmbd\fR destination causes the
+message to be sent to the nmbd daemon specified in the
+\fInmbd.pid\fR file.
+
+If a single process ID is given, the message is sent
+to only that process.
+.TP
+\fBmessage-type\fR
+One of: close-share,
+debug,
+force-election, ping
+, profile, debuglevel, profilelevel,
+or printnotify.
+
+The close-share message-type sends a
+message to smbd which will then close the client connections to
+the named share. Note that this doesn't affect client connections
+to any other shares. This message-type takes an argument of the
+share name for which client connections will be closed, or the
+"*" character which will close all currently open shares.
+This may be useful if you made changes to the access controls on the share.
+This message can only be sent to smbd.
+
+The debug message-type allows
+the debug level to be set to the value specified by the
+parameter. This can be sent to any of the destinations.
+
+The force-election message-type can only be
+sent to the nmbd destination. This message
+causes the \fBnmbd\fR daemon to force a new browse
+master election.
+
+The ping message-type sends the
+number of "ping" messages specified by the parameter and waits
+for the same number of reply "pong" messages. This can be sent to
+any of the destinations.
+
+The profile message-type sends a
+message to an smbd to change the profile settings based on the
+parameter. The parameter can be "on" to turn on profile stats
+collection, "off" to turn off profile stats collection, "count"
+to enable only collection of count stats (time stats are
+disabled), and "flush" to zero the current profile stats. This can
+be sent to any smbd or nmbd destinations.
+
+The debuglevel message-type sends
+a "request debug level" message. The current debug level setting
+is returned by a "debuglevel" message. This can be
+sent to any of the destinations.
+
+The profilelevel message-type sends
+a "request profile level" message. The current profile level
+setting is returned by a "profilelevel" message. This can be sent
+to any smbd or nmbd destinations.
+
+The printnotify message-type sends a
+message to smbd which in turn sends a printer notify message to
+any Windows NT clients connected to a printer. This message-type
+takes the following arguments:
.RS
-
.TP
-queuepause printername
-Send a queue pause change notify message to the printer specified\&.
-
-
+\fBqueuepause printername\fR
+Send a queue pause change notify
+message to the printer specified.
.TP
-queueresume printername
-Send a queue resume change notify message for the printer specified\&.
-
-
+\fBqueueresume printername\fR
+Send a queue resume change notify
+message for the printer specified.
.TP
-jobpause printername unixjobid
-Send a job pause change notify message for the printer and unix jobid specified\&.
-
-
+\fBjobpause printername unixjobid\fR
+Send a job pause change notify
+message for the printer and unix jobid
+specified.
.TP
-jobresume printername unixjobid
-Send a job resume change notify message for the printer and unix jobid specified\&.
-
-
+\fBjobresume printername unixjobid\fR
+Send a job resume change notify
+message for the printer and unix jobid
+specified.
.TP
-jobdelete printername unixjobid
-Send a job delete change notify message for the printer and unix jobid specified\&.
-
-
+\fBjobdelete printername unixjobid\fR
+Send a job delete change notify
+message for the printer and unix jobid
+specified.
.RE
-Note that this message only sends notification that an event has occured\&. It doesn't actually cause the event to happen\&.
-
-
-This message can only be sent to \fBsmbd\fR\&.
-
-
-.TP
-samsync
-Order smbd to synchronise sam database from PDC (being BDC)\&. Can only be sent to \fBsmbd\fR\&.
-
-Not working at the moment
-
-
+Note that this message only sends notification that an
+event has occured. It doesn't actually cause the
+event to happen.
+This message can only be sent to smbd.
.TP
-samrepl
-Send sam replication message, with specified serial\&. Can only be sent to \fBsmbd\fR\&. Should not be used manually\&.
-
-
-.TP
-dmalloc-mark
-Set a mark for dmalloc\&. Can be sent to both smbd and nmbd\&. Only available if samba is built with dmalloc support\&.
-
-
-.TP
-dmalloc-log-changed
-Dump the pointers that have changed since the mark set by dmalloc-mark\&. Can be sent to both smbd and nmbd\&. Only available if samba is built with dmalloc support\&.
-
-
-.TP
-shutdown
-Shut down specified daemon\&. Can be sent to both smbd and nmbd\&.
-
-
-.TP
-pool-usage
-Print a human-readable description of all talloc(pool) memory usage by the specified daemon/process\&. Available for both smbd and nmbd\&.
-
-
-.TP
-drvupgrade
-Force clients of printers using specified driver to update their local version of the driver\&. Can only be sent to smbd\&.
-
-
+\fBparameters\fR
+any parameters required for the message-type
.SH "VERSION"
-
.PP
-This man page is correct for version 3\&.0 of the Samba suite\&.
-
+This man page is correct for version 2.2 of
+the Samba suite.
.SH "SEE ALSO"
-
.PP
-\fBnmbd\fR(8) and \fBsmbd\fR(8)\&.
-
+\fBnmbd(8)\fR
+and \fBsmbd(8)\fR
.SH "AUTHOR"
-
.PP
-The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&.
-
+The original Samba software and related utilities
+were created by Andrew Tridgell. Samba is now developed
+by the Samba Team as an Open Source project similar
+to the way the Linux kernel is developed.
.PP
-The original Samba man pages were written by Karl Auer\&. The man page sources were converted to YODL format (another excellent piece of Open Source software, available at ftp://ftp\&.icce\&.rug\&.nl/pub/unix/) and updated for the Samba 2\&.0 release by Jeremy Allison\&. The conversion to DocBook for Samba 2\&.2 was done by Gerald Carter\&. The conversion to DocBook XML 4\&.2 for Samba 3\&.0 was done by Alexander Bokovoy\&.
-
+The original Samba man pages were written by Karl Auer.
+The man page sources were converted to YODL format (another
+excellent piece of Open Source software, available at
+ftp://ftp.icce.rug.nl/pub/unix/ <URL:ftp://ftp.icce.rug.nl/pub/unix/>) and updated for the Samba 2.0
+release by Jeremy Allison. The conversion to DocBook for
+Samba 2.2 was done by Gerald Carter
diff --git a/docs/manpages/smbd.8 b/docs/manpages/smbd.8
index c7c0fac777..106c0a98e3 100644
--- a/docs/manpages/smbd.8
+++ b/docs/manpages/smbd.8
@@ -1,230 +1,316 @@
-.\"Generated by db2man.xsl. Don't modify this, modify the source.
-.de Sh \" Subsection
-.br
-.if t .Sp
-.ne 5
-.PP
-\fB\\$1\fR
-.PP
-..
-.de Sp \" Vertical space (when we can't use .PP)
-.if t .sp .5v
-.if n .sp
-..
-.de Ip \" List item
-.br
-.ie \\n(.$>=3 .ne \\$3
-.el .ne 3
-.IP "\\$1" \\$2
-..
-.TH "SMBD" 8 "" "" ""
+.\" This manpage has been automatically generated by docbook2man
+.\" from a DocBook document. This tool can be found at:
+.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
+.\" Please send any bug reports, improvements, comments, patches,
+.\" etc. to Steve Cheng <steve@ggi-project.org>.
+.TH "SMBD" "8" "04 March 2003" "" ""
.SH NAME
smbd \- server to provide SMB/CIFS services to clients
-.SH "SYNOPSIS"
+.SH SYNOPSIS
-.nf
-\fBsmbd\fR [-D] [-F] [-S] [-i] [-h] [-V] [-b] [-d <debug level>] [-l <log directory>]
- [-p <port number>] [-O <socket option>] [-s <configuration file>]
-.fi
+\fBsmbd\fR [ \fB-D\fR ] [ \fB-F\fR ] [ \fB-S\fR ] [ \fB-i\fR ] [ \fB-h\fR ] [ \fB-V\fR ] [ \fB-b\fR ] [ \fB-d <debug level>\fR ] [ \fB-l <log directory>\fR ] [ \fB-p <port number>\fR ] [ \fB-O <socket option>\fR ] [ \fB-s <configuration file>\fR ]
.SH "DESCRIPTION"
-
.PP
-This program is part of the \fBSamba\fR(7) suite\&.
-
+This program is part of the Samba suite.
.PP
-\fBsmbd\fR is the server daemon that provides filesharing and printing services to Windows clients\&. The server provides filespace and printer services to clients using the SMB (or CIFS) protocol\&. This is compatible with the LanManager protocol, and can service LanManager clients\&. These include MSCLIENT 3\&.0 for DOS, Windows for Workgroups, Windows 95/98/ME, Windows NT, Windows 2000, OS/2, DAVE for Macintosh, and smbfs for Linux\&.
-
+\fBsmbd\fR is the server daemon that
+provides filesharing and printing services to Windows clients.
+The server provides filespace and printer services to
+clients using the SMB (or CIFS) protocol. This is compatible
+with the LanManager protocol, and can service LanManager
+clients. These include MSCLIENT 3.0 for DOS, Windows for
+Workgroups, Windows 95/98/ME, Windows NT, Windows 2000,
+OS/2, DAVE for Macintosh, and smbfs for Linux.
.PP
-An extensive description of the services that the server can provide is given in the man page for the configuration file controlling the attributes of those services (see \fBsmb.conf\fR(5)\&. This man page will not describe the services, but will concentrate on the administrative aspects of running the server\&.
-
+An extensive description of the services that the
+server can provide is given in the man page for the
+configuration file controlling the attributes of those
+services (see \fIsmb.conf(5)
+\fR This man page will not describe the
+services, but will concentrate on the administrative aspects
+of running the server.
.PP
-Please note that there are significant security implications to running this server, and the \fBsmb.conf\fR(5) manual page should be regarded as mandatory reading before proceeding with installation\&.
-
+Please note that there are significant security
+implications to running this server, and the \fIsmb.conf(5)\fR
+manpage should be regarded as mandatory reading before
+proceeding with installation.
.PP
-A session is created whenever a client requests one\&. Each client gets a copy of the server for each session\&. This copy then services all connections made by the client during that session\&. When all connections from its client are closed, the copy of the server for that client terminates\&.
-
+A session is created whenever a client requests one.
+Each client gets a copy of the server for each session. This
+copy then services all connections made by the client during
+that session. When all connections from its client are closed,
+the copy of the server for that client terminates.
.PP
-The configuration file, and any files that it includes, are automatically reloaded every minute, if they change\&. You can force a reload by sending a SIGHUP to the server\&. Reloading the configuration file will not affect connections to any service that is already established\&. Either the user will have to disconnect from the service, or \fBsmbd\fR killed and restarted\&.
-
+The configuration file, and any files that it includes,
+are automatically reloaded every minute, if they change. You
+can force a reload by sending a SIGHUP to the server. Reloading
+the configuration file will not affect connections to any service
+that is already established. Either the user will have to
+disconnect from the service, or \fBsmbd\fR killed and restarted.
.SH "OPTIONS"
-
.TP
--D
-If specified, this parameter causes the server to operate as a daemon\&. That is, it detaches itself and runs in the background, fielding requests on the appropriate port\&. Operating the server as a daemon is the recommended way of running \fBsmbd\fR for servers that provide more than casual use file and print services\&. This switch is assumed if \fBsmbd \fR is executed on the command line of a shell\&.
-
-
+\fB-D\fR
+If specified, this parameter causes
+the server to operate as a daemon. That is, it detaches
+itself and runs in the background, fielding requests
+on the appropriate port. Operating the server as a
+daemon is the recommended way of running \fBsmbd\fR for
+servers that provide more than casual use file and
+print services. This switch is assumed if \fBsmbd
+\fR is executed on the command line of a shell.
.TP
--F
-If specified, this parameter causes the main \fBsmbd\fR process to not daemonize, i\&.e\&. double-fork and disassociate with the terminal\&. Child processes are still created as normal to service each connection request, but the main process does not exit\&. This operation mode is suitable for running \fBsmbd\fR under process supervisors such as \fBsupervise\fR and \fBsvscan\fR from Daniel J\&. Bernstein's \fBdaemontools\fR package, or the AIX process monitor\&.
-
-
+\fB-F\fR
+If specified, this parameter causes
+the main \fBsmbd\fR process to not daemonize,
+i.e. double-fork and disassociate with the terminal.
+Child processes are still created as normal to service
+each connection request, but the main process does not
+exit. This operation mode is suitable for running
+\fBsmbd\fR under process supervisors such
+as \fBsupervise\fR and \fBsvscan\fR
+from Daniel J. Bernstein's \fBdaemontools\fR
+package, or the AIX process monitor.
.TP
--S
-If specified, this parameter causes \fBsmbd\fR to log to standard output rather than a file\&.
-
-
+\fB-S\fR
+If specified, this parameter causes
+\fBsmbd\fR to log to standard output rather
+than a file.
.TP
--i
-If this parameter is specified it causes the server to run "interactively", not as a daemon, even if the server is executed on the command line of a shell\&. Setting this parameter negates the implicit deamon mode when run from the command line\&. \fBsmbd\fR also logs to standard output, as if the \fB-S\fR parameter had been given\&.
-
-
+\fB-i\fR
+If this parameter is specified it causes the
+server to run "interactively", not as a daemon, even if the
+server is executed on the command line of a shell. Setting this
+parameter negates the implicit deamon mode when run from the
+command line. \fBsmbd\fR also logs to standard
+output, as if the \fB-S\fR parameter had been
+given.
.TP
--V
-Prints the version number for \fBsmbd\fR\&.
-
-
+\fB-h\fR
+Prints the help information (usage)
+for \fBsmbd\fR.
.TP
--s <configuration file>
-The file specified contains the configuration details required by the server\&. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is to provide\&. See \fI smb\&.conf(5)\fR for more information\&. The default configuration file name is determined at compile time\&.
-
-
+\fB-V\fR
+Prints the version number for
+\fBsmbd\fR.
.TP
--d|--debug=debuglevel
-\fIdebuglevel\fR is an integer from 0 to 10\&. The default value if this parameter is not specified is zero\&.
-
-
-The higher this value, the more detail will be logged to the log files about the activities of the server\&. At level 0, only critical errors and serious warnings will be logged\&. Level 1 is a reasonable level for day to day running - it generates a small amount of information about operations carried out\&.
-
-
-Levels above 1 will generate considerable amounts of log data, and should only be used when investigating a problem\&. Levels above 3 are designed for use only by developers and generate HUGE amounts of log data, most of which is extremely cryptic\&.
-
-
-Note that specifying this parameter here will override the log level parameter in the \fIsmb\&.conf(5)\fR file\&.
-
-
+\fB-b\fR
+Prints information about how
+Samba was built.
.TP
--l|--logfile=logbasename
-File name for log/debug files\&. The extension \fB"\&.client"\fR will be appended\&. The log file is never removed by the client\&.
-
-
+\fB-d <debug level>\fR
+\fIdebuglevel\fR is an integer
+from 0 to 10. The default value if this parameter is
+not specified is zero.
+
+The higher this value, the more detail will be
+logged to the log files about the activities of the
+server. At level 0, only critical errors and serious
+warnings will be logged. Level 1 is a reasonable level for
+day to day running - it generates a small amount of
+information about operations carried out.
+
+Levels above 1 will generate considerable
+amounts of log data, and should only be used when
+investigating a problem. Levels above 3 are designed for
+use only by developers and generate HUGE amounts of log
+data, most of which is extremely cryptic.
+
+Note that specifying this parameter here will
+override the log
+level file.
.TP
--h|--help
-Print a summary of command line options\&.
-
-
+\fB-l <log directory>\fR
+If specified,
+\fIlog directory\fR
+specifies a log directory into which the "log.smbd" log
+file will be created for informational and debug
+messages from the running server. The log
+file generated is never removed by the server although
+its size may be controlled by the max log size
+option in the \fI smb.conf(5)\fR file. \fBBeware:\fR
+If the directory specified does not exist, \fBsmbd\fR
+will log to the default debug log location defined at compile time.
+
+The default log directory is specified at
+compile time.
.TP
--b
-Prints information about how Samba was built\&.
-
-
+\fB-O <socket options>\fR
+See the socket options
+parameter in the \fIsmb.conf(5)
+\fR file for details.
.TP
--l <log directory>
-If specified, \fIlog directory\fR specifies a log directory into which the "log\&.smbd" log file will be created for informational and debug messages from the running server\&. The log file generated is never removed by the server although its size may be controlled by the \fImax log size\fR option in the \fBsmb.conf\fR(5) file\&. \fBBeware:\fR If the directory specified does not exist, \fBsmbd\fR will log to the default debug log location defined at compile time\&.
-
-
-The default log directory is specified at compile time\&.
-
-
+\fB-p <port number>\fR
+\fIport number\fR is a positive integer
+value. The default value if this parameter is not
+specified is 139.
+
+This number is the port number that will be
+used when making connections to the server from client
+software. The standard (well-known) port number for the
+SMB over TCP is 139, hence the default. If you wish to
+run the server as an ordinary user rather than
+as root, most systems will require you to use a port
+number greater than 1024 - ask your system administrator
+for help if you are in this situation.
+
+In order for the server to be useful by most
+clients, should you configure it on a port other
+than 139, you will require port redirection services
+on port 139, details of which are outlined in rfc1002.txt
+section 4.3.5.
+
+This parameter is not normally specified except
+in the above situation.
.TP
--p <port number>
-\fIport number\fR is a positive integer value\&. The default value if this parameter is not specified is 139\&.
-
-
-This number is the port number that will be used when making connections to the server from client software\&. The standard (well-known) port number for the SMB over TCP is 139, hence the default\&. If you wish to run the server as an ordinary user rather than as root, most systems will require you to use a port number greater than 1024 - ask your system administrator for help if you are in this situation\&.
-
-
-In order for the server to be useful by most clients, should you configure it on a port other than 139, you will require port redirection services on port 139, details of which are outlined in rfc1002\&.txt section 4\&.3\&.5\&.
-
-
-This parameter is not normally specified except in the above situation\&.
-
-
+\fB-s <configuration file>\fR
+The file specified contains the
+configuration details required by the server. The
+information in this file includes server-specific
+information such as what printcap file to use, as well
+as descriptions of all the services that the server is
+to provide. See \fI smb.conf(5)\fR for more information.
+The default configuration file name is determined at
+compile time.
.SH "FILES"
-
.TP
-\fI/etc/inetd\&.conf\fR
-If the server is to be run by the \fBinetd\fR meta-daemon, this file must contain suitable startup information for the meta-daemon\&. See the "How to Install and Test SAMBA" document for details\&.
-
-
+\fB\fI/etc/inetd.conf\fB\fR
+If the server is to be run by the
+\fBinetd\fR meta-daemon, this file
+must contain suitable startup information for the
+meta-daemon. See the UNIX_INSTALL.html
+document for details.
.TP
-\fI/etc/rc\fR
-or whatever initialization script your system uses)\&.
-
-
-If running the server as a daemon at startup, this file will need to contain an appropriate startup sequence for the server\&. See the "How to Install and Test SAMBA" document for details\&.
-
-
+\fB\fI/etc/rc\fB\fR
+or whatever initialization script your
+system uses).
+
+If running the server as a daemon at startup,
+this file will need to contain an appropriate startup
+sequence for the server. See the UNIX_INSTALL.html
+document for details.
.TP
-\fI/etc/services\fR
-If running the server via the meta-daemon \fBinetd\fR, this file must contain a mapping of service name (e\&.g\&., netbios-ssn) to service port (e\&.g\&., 139) and protocol type (e\&.g\&., tcp)\&. See the "How to Install and Test SAMBA" document for details\&.
-
-
+\fB\fI/etc/services\fB\fR
+If running the server via the
+meta-daemon \fBinetd\fR, this file
+must contain a mapping of service name (e.g., netbios-ssn)
+to service port (e.g., 139) and protocol type (e.g., tcp).
+See the UNIX_INSTALL.html
+document for details.
.TP
-\fI/usr/local/samba/lib/smb\&.conf\fR
-This is the default location of the \fBsmb.conf\fR(5) server configuration file\&. Other common places that systems install this file are \fI/usr/samba/lib/smb\&.conf\fR and \fI/etc/samba/smb\&.conf\fR\&.
-
-
-This file describes all the services the server is to make available to clients\&. See \fBsmb.conf\fR(5) for more information\&.
-
-
+\fB\fI/usr/local/samba/lib/smb.conf\fB\fR
+This is the default location of the
+\fIsmb.conf\fR
+server configuration file. Other common places that systems
+install this file are \fI/usr/samba/lib/smb.conf\fR
+and \fI/etc/smb.conf\fR.
+
+This file describes all the services the server
+is to make available to clients. See \fIsmb.conf(5)\fR for more information.
.SH "LIMITATIONS"
-
.PP
-On some systems \fBsmbd\fR cannot change uid back to root after a setuid() call\&. Such systems are called trapdoor uid systems\&. If you have such a system, you will be unable to connect from a client (such as a PC) as two different users at once\&. Attempts to connect the second user will result in access denied or similar\&.
-
+On some systems \fBsmbd\fR cannot change uid back
+to root after a setuid() call. Such systems are called
+trapdoor uid systems. If you have such a system,
+you will be unable to connect from a client (such as a PC) as
+two different users at once. Attempts to connect the
+second user will result in access denied or
+similar.
.SH "ENVIRONMENT VARIABLES"
-
.TP
\fBPRINTER\fR
-If no printer name is specified to printable services, most systems will use the value of this variable (or \fBlp\fR if this variable is not defined) as the name of the printer to use\&. This is not specific to the server, however\&.
-
-
+If no printer name is specified to
+printable services, most systems will use the value of
+this variable (or lp if this variable is
+not defined) as the name of the printer to use. This
+is not specific to the server, however.
.SH "PAM INTERACTION"
-
.PP
-Samba uses PAM for authentication (when presented with a plaintext password), for account checking (is this account disabled?) and for session management\&. The degree too which samba supports PAM is restricted by the limitations of the SMB protocol and the \fIobey pam restricions\fR \fBsmb.conf\fR(5) paramater\&. When this is set, the following restrictions apply:
-
-.TP 3
+Samba uses PAM for authentication (when presented with a plaintext
+password), for account checking (is this account disabled?) and for
+session management. The degree too which samba supports PAM is restricted
+by the limitations of the SMB protocol and the
+obey pam restricions
+smb.conf paramater. When this is set, the following restrictions apply:
+.TP 0.2i
\(bu
-\fBAccount Validation\fR: All accesses to a samba server are checked against PAM to see if the account is vaild, not disabled and is permitted to login at this time\&. This also applies to encrypted logins\&.
-
-.TP
+\fBAccount Validation\fR: All accesses to a
+samba server are checked
+against PAM to see if the account is vaild, not disabled and is permitted to
+login at this time. This also applies to encrypted logins.
+.TP 0.2i
\(bu
-\fBSession Management\fR: When not using share level secuirty, users must pass PAM's session checks before access is granted\&. Note however, that this is bypassed in share level secuirty\&. Note also that some older pam configuration files may need a line added for session support\&.
-
-.LP
-
+\fBSession Management\fR: When not using share
+level secuirty, users must pass PAM's session checks before access
+is granted. Note however, that this is bypassed in share level secuirty.
+Note also that some older pam configuration files may need a line
+added for session support.
.SH "VERSION"
-
.PP
-This man page is correct for version 3\&.0 of the Samba suite\&.
-
+This man page is correct for version 3.0 of
+the Samba suite.
.SH "DIAGNOSTICS"
-
.PP
-Most diagnostics issued by the server are logged in a specified log file\&. The log file name is specified at compile time, but may be overridden on the command line\&.
-
+Most diagnostics issued by the server are logged
+in a specified log file. The log file name is specified
+at compile time, but may be overridden on the command line.
.PP
-The number and nature of diagnostics available depends on the debug level used by the server\&. If you have problems, set the debug level to 3 and peruse the log files\&.
-
+The number and nature of diagnostics available depends
+on the debug level used by the server. If you have problems, set
+the debug level to 3 and peruse the log files.
.PP
-Most messages are reasonably self-explanatory\&. Unfortunately, at the time this man page was created, there are too many diagnostics available in the source code to warrant describing each and every diagnostic\&. At this stage your best bet is still to grep the source code and inspect the conditions that gave rise to the diagnostics you are seeing\&.
-
+Most messages are reasonably self-explanatory. Unfortunately,
+at the time this man page was created, there are too many diagnostics
+available in the source code to warrant describing each and every
+diagnostic. At this stage your best bet is still to grep the
+source code and inspect the conditions that gave rise to the
+diagnostics you are seeing.
.SH "SIGNALS"
-
.PP
-Sending the \fBsmbd\fR a SIGHUP will cause it to reload its \fIsmb\&.conf\fR configuration file within a short period of time\&.
-
+Sending the \fBsmbd\fR a SIGHUP will cause it to
+reload its \fIsmb.conf\fR configuration
+file within a short period of time.
.PP
-To shut down a user's \fBsmbd\fR process it is recommended that \fBSIGKILL (-9)\fR \fBNOT\fR be used, except as a last resort, as this may leave the shared memory area in an inconsistent state\&. The safe way to terminate an \fBsmbd\fR is to send it a SIGTERM (-15) signal and wait for it to die on its own\&.
-
+To shut down a user's \fBsmbd\fR process it is recommended
+that \fBSIGKILL (-9)\fR \fBNOT\fR
+be used, except as a last resort, as this may leave the shared
+memory area in an inconsistent state. The safe way to terminate
+an \fBsmbd\fR is to send it a SIGTERM (-15) signal and wait for
+it to die on its own.
.PP
-The debug log level of \fBsmbd\fR may be raised or lowered using \fBsmbcontrol\fR(1) program (SIGUSR[1|2] signals are no longer used since Samba 2\&.2)\&. This is to allow transient problems to be diagnosed, whilst still running at a normally low log level\&.
-
+The debug log level of \fBsmbd\fR may be raised
+or lowered using \fBsmbcontrol(1)
+\fR program (SIGUSR[1|2] signals are no longer used in
+Samba 2.2). This is to allow transient problems to be diagnosed,
+whilst still running at a normally low log level.
.PP
-Note that as the signal handlers send a debug write, they are not re-entrant in \fBsmbd\fR\&. This you should wait until\fBsmbd\fR is in a state of waiting for an incoming SMB before issuing them\&. It is possible to make the signal handlers safe by un-blocking the signals before the select call and re-blocking them after, however this would affect performance\&.
-
+Note that as the signal handlers send a debug write,
+they are not re-entrant in \fBsmbd\fR. This you should wait until
+\fBsmbd\fR is in a state of waiting for an incoming SMB before
+issuing them. It is possible to make the signal handlers safe
+by un-blocking the signals before the select call and re-blocking
+them after, however this would affect performance.
.SH "SEE ALSO"
-
.PP
-\fBhosts_access\fR(5), \fBinetd\fR(8), \fBnmbd\fR(8), \fBsmb.conf\fR(5), \fBsmbclient\fR(1), \fBtestparm\fR(1), \fBtestprns\fR(1), and the Internet RFC's\fIrfc1001\&.txt\fR, \fIrfc1002\&.txt\fR\&. In addition the CIFS (formerly SMB) specification is available as a link from the Web page http://samba\&.org/cifs/\&.
-
+hosts_access(5), \fBinetd(8)\fR,
+\fBnmbd(8)\fR
+\fIsmb.conf(5)\fR
+ \fBsmbclient(1)
+\fR and the Internet RFC's
+\fIrfc1001.txt\fR, \fIrfc1002.txt\fR.
+In addition the CIFS (formerly SMB) specification is available
+as a link from the Web page
+http://samba.org/cifs/ <URL:http://samba.org/cifs/>.
.SH "AUTHOR"
-
.PP
-The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&.
-
+The original Samba software and related utilities
+were created by Andrew Tridgell. Samba is now developed
+by the Samba Team as an Open Source project similar
+to the way the Linux kernel is developed.
.PP
-The original Samba man pages were written by Karl Auer\&. The man page sources were converted to YODL format (another excellent piece of Open Source software, available at ftp://ftp\&.icce\&.rug\&.nl/pub/unix/) and updated for the Samba 2\&.0 release by Jeremy Allison\&. The conversion to DocBook for Samba 2\&.2 was done by Gerald Carter\&. The conversion to DocBook XML 4\&.2 for Samba 3\&.0 was done by Alexander Bokovoy\&.
-
+The original Samba man pages were written by Karl Auer.
+The man page sources were converted to YODL format (another
+excellent piece of Open Source software, available at
+ftp://ftp.icce.rug.nl/pub/unix/ <URL:ftp://ftp.icce.rug.nl/pub/unix/>) and updated for the Samba 2.0
+release by Jeremy Allison. The conversion to DocBook for
+Samba 2.2 was done by Gerald Carter
diff --git a/docs/manpages/smbmnt.8 b/docs/manpages/smbmnt.8
index 45515c593d..e8e8562a12 100644
--- a/docs/manpages/smbmnt.8
+++ b/docs/manpages/smbmnt.8
@@ -1,91 +1,64 @@
-.\"Generated by db2man.xsl. Don't modify this, modify the source.
-.de Sh \" Subsection
-.br
-.if t .Sp
-.ne 5
-.PP
-\fB\\$1\fR
-.PP
-..
-.de Sp \" Vertical space (when we can't use .PP)
-.if t .sp .5v
-.if n .sp
-..
-.de Ip \" List item
-.br
-.ie \\n(.$>=3 .ne \\$3
-.el .ne 3
-.IP "\\$1" \\$2
-..
-.TH "SMBMNT" 8 "" "" ""
+.\" This manpage has been automatically generated by docbook2man
+.\" from a DocBook document. This tool can be found at:
+.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
+.\" Please send any bug reports, improvements, comments, patches,
+.\" etc. to Steve Cheng <steve@ggi-project.org>.
+.TH "SMBMNT" "8" "04 March 2003" "" ""
.SH NAME
smbmnt \- helper utility for mounting SMB filesystems
-.SH "SYNOPSIS"
+.SH SYNOPSIS
-.nf
-\fBsmbmnt\fR {mount-point} [-s <share>] [-r] [-u <uid>] [-g <gid>] [-f <mask>] [-d <mask>] [-o <options>] [-h]
-
-.fi
+\fBsmbmnt\fR \fBmount-point\fR [ \fB-s <share>\fR ] [ \fB-r\fR ] [ \fB-u <uid>\fR ] [ \fB-g <gid>\fR ] [ \fB-f <mask>\fR ] [ \fB-d <mask>\fR ] [ \fB-o <options>\fR ]
.SH "DESCRIPTION"
-
.PP
-\fBsmbmnt\fR is a helper application used by the smbmount program to do the actual mounting of SMB shares\&.\fBsmbmnt\fR can be installed setuid root if you want normal users to be able to mount their SMB shares\&.
-
+\fBsmbmnt\fR is a helper application used
+by the smbmount program to do the actual mounting of SMB shares.
+\fBsmbmnt\fR can be installed setuid root if you want
+normal users to be able to mount their SMB shares.
.PP
-A setuid smbmnt will only allow mounts on directories owned by the user, and that the user has write permission on\&.
-
+A setuid smbmnt will only allow mounts on directories owned
+by the user, and that the user has write permission on.
.PP
-The \fBsmbmnt\fR program is normally invoked by \fBsmbmount\fR(8)\&. It should not be invoked directly by users\&.
-
+The \fBsmbmnt\fR program is normally invoked
+by \fBsmbmount(8)\fR
+ It should not be invoked directly by users.
.PP
-smbmount searches the normal PATH for smbmnt\&. You must ensure that the smbmnt version in your path matches the smbmount used\&.
-
+smbmount searches the normal PATH for smbmnt. You must ensure
+that the smbmnt version in your path matches the smbmount used.
.SH "OPTIONS"
-
.TP
--r
-mount the filesystem read-only
-
-
+\fB-r\fR
+mount the filesystem read-only
.TP
--u uid
-specify the uid that the files will be owned by
-
-
+\fB-u uid\fR
+specify the uid that the files will
+be owned by
.TP
--g gid
-specify the gid that the files will be owned by
-
-
+\fB-g gid\fR
+specify the gid that the files will be
+owned by
.TP
--f mask
+\fB-f mask\fR
specify the octal file mask applied
-
-
.TP
--d mask
-specify the octal directory mask applied
-
-
-.TP
--o options
-list of options that are passed as-is to smbfs, if this command is run on a 2\&.4 or higher Linux kernel\&.
-
-
+\fB-d mask\fR
+specify the octal directory mask
+applied
.TP
--h|--help
-Print a summary of command line options\&.
-
-
+\fB-o options\fR
+list of options that are passed as-is to smbfs, if this
+command is run on a 2.4 or higher Linux kernel.
.SH "AUTHOR"
-
.PP
-Volker Lendecke, Andrew Tridgell, Michael H\&. Warfield and others\&.
-
+Volker Lendecke, Andrew Tridgell, Michael H. Warfield
+and others.
.PP
-The current maintainer of smbfs and the userspace tools \fBsmbmount\fR, \fBsmbumount\fR, and \fBsmbmnt\fR is Urban Widmark\&. The SAMBA Mailing list is the preferred place to ask questions regarding these programs\&.
-
+The current maintainer of smbfs and the userspace
+tools \fBsmbmount\fR, \fBsmbumount\fR,
+and \fBsmbmnt\fR is Urban Widmark <URL:mailto:urban@teststation.com>.
+The SAMBA Mailing list <URL:mailto:samba@samba.org>
+is the preferred place to ask questions regarding these programs.
.PP
-The conversion of this manpage for Samba 2\&.2 was performed by Gerald Carter\&. The conversion to DocBook XML 4\&.2 for Samba 3\&.0 was done by Alexander Bokovoy\&.
-
+The conversion of this manpage for Samba 2.2 was performed
+by Gerald Carter
diff --git a/docs/manpages/smbmount.8 b/docs/manpages/smbmount.8
index ccb776e7f1..8d7dfd8d22 100644
--- a/docs/manpages/smbmount.8
+++ b/docs/manpages/smbmount.8
@@ -1,214 +1,215 @@
-.\"Generated by db2man.xsl. Don't modify this, modify the source.
-.de Sh \" Subsection
-.br
-.if t .Sp
-.ne 5
-.PP
-\fB\\$1\fR
-.PP
-..
-.de Sp \" Vertical space (when we can't use .PP)
-.if t .sp .5v
-.if n .sp
-..
-.de Ip \" List item
-.br
-.ie \\n(.$>=3 .ne \\$3
-.el .ne 3
-.IP "\\$1" \\$2
-..
-.TH "SMBMOUNT" 8 "" "" ""
+.\" This manpage has been automatically generated by docbook2man
+.\" from a DocBook document. This tool can be found at:
+.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
+.\" Please send any bug reports, improvements, comments, patches,
+.\" etc. to Steve Cheng <steve@ggi-project.org>.
+.TH "SMBMOUNT" "8" "04 March 2003" "" ""
.SH NAME
smbmount \- mount an smbfs filesystem
-.SH "SYNOPSIS"
+.SH SYNOPSIS
-.nf
-\fBsmbmount\fR {service} {mount-point} [-o options]
-.fi
+\fBsmbmount\fR \fBservice\fR \fBmount-point\fR [ \fB-o options\fR ]
.SH "DESCRIPTION"
-
-.PP
-\fBsmbmount\fR mounts a Linux SMB filesystem\&. It is usually invoked as \fBmount.smbfs\fR by the \fBmount\fR(8) command when using the "-t smbfs" option\&. This command only works in Linux, and the kernel must support the smbfs filesystem\&.
-
-.PP
-Options to \fBsmbmount\fR are specified as a comma-separated list of key=value pairs\&. It is possible to send options other than those listed here, assuming that smbfs supports them\&. If you get mount failures, check your kernel log for errors on unknown options\&.
-
-.PP
-\fBsmbmount\fR is a daemon\&. After mounting it keeps running until the mounted smbfs is umounted\&. It will log things that happen when in daemon mode using the "machine name" smbmount, so typically this output will end up in \fIlog\&.smbmount\fR\&. The \fB smbmount\fR process may also be called mount\&.smbfs\&.
-
.PP
-\fBNOTE:\fR \fBsmbmount\fR calls \fBsmbmnt\fR(8) to do the actual mount\&. You must make sure that \fBsmbmnt\fR is in the path so that it can be found\&.
-
+\fBsmbmount\fR mounts a Linux SMB filesystem. It
+is usually invoked as \fBmount.smbfs\fR by
+the \fBmount(8)\fR command when using the
+"-t smbfs" option. This command only works in Linux, and the kernel must
+support the smbfs filesystem.
+.PP
+Options to \fBsmbmount\fR are specified as a comma-separated
+list of key=value pairs. It is possible to send options other
+than those listed here, assuming that smbfs supports them. If
+you get mount failures, check your kernel log for errors on
+unknown options.
+.PP
+\fBsmbmount\fR is a daemon. After mounting it keeps running until
+the mounted smbfs is umounted. It will log things that happen
+when in daemon mode using the "machine name" smbmount, so
+typically this output will end up in \fIlog.smbmount\fR. The
+\fBsmbmount\fR process may also be called mount.smbfs.
+.PP
+\fBNOTE:\fR \fBsmbmount\fR
+calls \fBsmbmnt(8)\fR to do the actual mount. You
+must make sure that \fBsmbmnt\fR is in the path so
+that it can be found.
.SH "OPTIONS"
-
.TP
-username=<arg>
-specifies the username to connect as\&. If this is not given, then the environment variable \fB USER\fR is used\&. This option can also take the form "user%password" or "user/workgroup" or "user/workgroup%password" to allow the password and workgroup to be specified as part of the username\&.
-
-
+\fBusername=<arg>\fR
+specifies the username to connect as. If
+this is not given, then the environment variable \fB USER\fR is used. This option can also take the
+form "user%password" or "user/workgroup" or
+"user/workgroup%password" to allow the password and workgroup
+to be specified as part of the username.
.TP
-password=<arg>
-specifies the SMB password\&. If this option is not given then the environment variable \fBPASSWD\fR is used\&. If it can find no password \fBsmbmount\fR will prompt for a passeword, unless the guest option is given\&.
-
+\fBpassword=<arg>\fR
+specifies the SMB password. If this
+option is not given then the environment variable
+\fBPASSWD\fR is used. If it can find
+no password \fBsmbmount\fR will prompt
+for a passeword, unless the guest option is
+given.
-Note that passwords which contain the argument delimiter character (i\&.e\&. a comma ',') will failed to be parsed correctly on the command line\&. However, the same password defined in the PASSWD environment variable or a credentials file (see below) will be read correctly\&.
+Note that passwords which contain the argument delimiter
+character (i.e. a comma ',') will failed to be parsed correctly
+on the command line. However, the same password defined
+in the PASSWD environment variable or a credentials file (see
+below) will be read correctly.
+.TP
+\fBcredentials=<filename>\fR
+specifies a file that contains a username
+and/or password. The format of the file is:
-.TP
-credentials=<filename>
-specifies a file that contains a username and/or password\&.
-The format of the file is:
.nf
-
-username = <value>
-password = <value>
+ username = <value>
+ password = <value>
+
.fi
-
-This is preferred over having passwords in plaintext in a shared file, such as \fI/etc/fstab\fR\&. Be sure to protect any credentials file properly\&.
-
-
-.TP
-krb
-Use kerberos (Active Directory)\&.
-
-
-.TP
-netbiosname=<arg>
-sets the source NetBIOS name\&. It defaults to the local hostname\&.
-
-
-.TP
-uid=<arg>
-sets the uid that will own all files on the mounted filesystem\&. It may be specified as either a username or a numeric uid\&.
-
-
-.TP
-gid=<arg>
-sets the gid that will own all files on the mounted filesystem\&. It may be specified as either a groupname or a numeric gid\&.
-
-
-.TP
-port=<arg>
-sets the remote SMB port number\&. The default is 139\&.
-
-
-.TP
-fmask=<arg>
-sets the file mask\&. This determines the permissions that remote files have in the local filesystem\&. The default is based on the current umask\&.
-
-
-.TP
-dmask=<arg>
-Sets the directory mask\&. This determines the permissions that remote directories have in the local filesystem\&. The default is based on the current umask\&.
-
-
-.TP
-debug=<arg>
-Sets the debug level\&. This is useful for tracking down SMB connection problems\&. A suggested value to start with is 4\&. If set too high there will be a lot of output, possibly hiding the useful output\&.
-
-
-.TP
-ip=<arg>
-Sets the destination host or IP address\&.
-
-
-.TP
-workgroup=<arg>
-Sets the workgroup on the destination
-
-
-.TP
-sockopt=<arg>
-Sets the TCP socket options\&. See the \fBsmb.conf\fR(5) \fIsocket options\fR option\&.
-
-
-.TP
-scope=<arg>
-Sets the NetBIOS scope
-
-
-.TP
-guest
-Don't prompt for a password
-
-
-.TP
-ro
-mount read-only
-
-
-.TP
-rw
-mount read-write
-
-
-.TP
-iocharset=<arg>
-sets the charset used by the Linux side for codepage to charset translations (NLS)\&. Argument should be the name of a charset, like iso8859-1\&. (Note: only kernel 2\&.4\&.0 or later)
-
-
-.TP
-codepage=<arg>
-sets the codepage the server uses\&. See the iocharset option\&. Example value cp850\&. (Note: only kernel 2\&.4\&.0 or later)
-
-
-.TP
-ttl=<arg>
-sets how long a directory listing is cached in milliseconds (also affects visibility of file size and date changes)\&. A higher value means that changes on the server take longer to be noticed but it can give better performance on large directories, especially over long distances\&. Default is 1000ms but something like 10000ms (10 seconds) is probably more reasonable in many cases\&. (Note: only kernel 2\&.4\&.2 or later)
-
-
+This is preferred over having passwords in plaintext in a
+shared file, such as \fI/etc/fstab\fR. Be sure to protect any
+credentials file properly.
+.TP
+\fBnetbiosname=<arg>\fR
+sets the source NetBIOS name. It defaults
+to the local hostname.
+.TP
+\fBuid=<arg>\fR
+sets the uid that will own all files on
+the mounted filesystem.
+It may be specified as either a username or a numeric uid.
+.TP
+\fBgid=<arg>\fR
+sets the gid that will own all files on
+the mounted filesystem.
+It may be specified as either a groupname or a numeric
+gid.
+.TP
+\fBport=<arg>\fR
+sets the remote SMB port number. The default
+is 139.
+.TP
+\fBfmask=<arg>\fR
+sets the file mask. This determines the
+permissions that remote files have in the local filesystem.
+The default is based on the current umask.
+.TP
+\fBdmask=<arg>\fR
+sets the directory mask. This determines the
+permissions that remote directories have in the local filesystem.
+The default is based on the current umask.
+.TP
+\fBdebug=<arg>\fR
+sets the debug level. This is useful for
+tracking down SMB connection problems. A suggested value to
+start with is 4. If set too high there will be a lot of
+output, possibly hiding the useful output.
+.TP
+\fBip=<arg>\fR
+sets the destination host or IP address.
+.TP
+\fBworkgroup=<arg>\fR
+sets the workgroup on the destination
+.TP
+\fBsockopt=<arg>\fR
+sets the TCP socket options. See the \fIsmb.conf
+\fR \fIsocket options\fR option.
+.TP
+\fBscope=<arg>\fR
+sets the NetBIOS scope
+.TP
+\fBguest\fR
+don't prompt for a password
+.TP
+\fBro\fR
+mount read-only
+.TP
+\fBrw\fR
+mount read-write
+.TP
+\fBiocharset=<arg>\fR
+sets the charset used by the Linux side for codepage
+to charset translations (NLS). Argument should be the
+name of a charset, like iso8859-1. (Note: only kernel
+2.4.0 or later)
+.TP
+\fBcodepage=<arg>\fR
+sets the codepage the server uses. See the iocharset
+option. Example value cp850. (Note: only kernel 2.4.0
+or later)
+.TP
+\fBttl=<arg>\fR
+sets how long a directory listing is cached in milliseconds
+(also affects visibility of file size and date
+changes). A higher value means that changes on the
+server take longer to be noticed but it can give
+better performance on large directories, especially
+over long distances. Default is 1000ms but something
+like 10000ms (10 seconds) is probably more reasonable
+in many cases.
+(Note: only kernel 2.4.2 or later)
.SH "ENVIRONMENT VARIABLES"
-
.PP
-The variable \fBUSER\fR may contain the username of the person using the client\&. This information is used only if the protocol level is high enough to support session-level passwords\&. The variable can be used to set both username and password by using the format username%password\&.
-
+The variable \fBUSER\fR may contain the username of the
+person using the client. This information is used only if the
+protocol level is high enough to support session-level
+passwords. The variable can be used to set both username and
+password by using the format username%password.
.PP
-The variable \fBPASSWD\fR may contain the password of the person using the client\&. This information is used only if the protocol level is high enough to support session-level passwords\&.
-
+The variable \fBPASSWD\fR may contain the password of the
+person using the client. This information is used only if the
+protocol level is high enough to support session-level
+passwords.
.PP
-The variable \fBPASSWD_FILE\fR may contain the pathname of a file to read the password from\&. A single line of input is read and used as the password\&.
-
+The variable \fBPASSWD_FILE\fR may contain the pathname
+of a file to read the password from. A single line of input is
+read and used as the password.
.SH "BUGS"
-
.PP
-Passwords and other options containing , can not be handled\&. For passwords an alternative way of passing them is in a credentials file or in the PASSWD environment\&.
-
+Passwords and other options containing , can not be handled.
+For passwords an alternative way of passing them is in a credentials
+file or in the PASSWD environment.
.PP
-The credentials file does not handle usernames or passwords with leading space\&.
-
+The credentials file does not handle usernames or passwords with
+leading space.
.PP
-One smbfs bug is important enough to mention here, even if it is a bit misplaced:
-
-.TP 3
+One smbfs bug is important enough to mention here, even if it
+is a bit misplaced:
+.TP 0.2i
\(bu
-Mounts sometimes stop working\&. This is usually caused by smbmount terminating\&. Since smbfs needs smbmount to reconnect when the server disconnects, the mount will eventually go dead\&. An umount/mount normally fixes this\&. At least 2 ways to trigger this bug are known\&.
-
-.LP
-
-.PP
-Note that the typical response to a bug report is suggestion to try the latest version first\&. So please try doing that first, and always include which versions you use of relevant software when reporting bugs (minimum: samba, kernel, distribution)
-
+Mounts sometimes stop working. This is usually
+caused by smbmount terminating. Since smbfs needs smbmount to
+reconnect when the server disconnects, the mount will eventually go
+dead. An umount/mount normally fixes this. At least 2 ways to
+trigger this bug are known.
+.PP
+Note that the typical response to a bug report is suggestion
+to try the latest version first. So please try doing that first,
+and always include which versions you use of relevant software
+when reporting bugs (minimum: samba, kernel, distribution)
.SH "SEE ALSO"
-
.PP
-Documentation/filesystems/smbfs\&.txt in the linux kernel source tree may contain additional options and information\&.
-
+Documentation/filesystems/smbfs.txt in the linux kernel
+source tree may contain additional options and information.
.PP
FreeBSD also has a smbfs, but it is not related to smbmount
-
.PP
-For Solaris, HP-UX and others you may want to look at \fBsmbsh\fR(1) or at other solutions, such as Sharity or perhaps replacing the SMB server with a NFS server\&.
-
+For Solaris, HP-UX and others you may want to look at
+\fBsmbsh(1)\fR or at other
+solutions, such as sharity or perhaps replacing the SMB server with
+a NFS server.
.SH "AUTHOR"
-
.PP
-Volker Lendecke, Andrew Tridgell, Michael H\&. Warfield and others\&.
-
+Volker Lendecke, Andrew Tridgell, Michael H. Warfield
+and others.
.PP
-The current maintainer of smbfs and the userspace tools \fBsmbmount\fR, \fBsmbumount\fR, and \fBsmbmnt\fR is Urban Widmark\&. The SAMBA Mailing list is the preferred place to ask questions regarding these programs\&.
-
+The current maintainer of smbfs and the userspace
+tools \fBsmbmount\fR, \fBsmbumount\fR,
+and \fBsmbmnt\fR is Urban Widmark <URL:mailto:urban@teststation.com>.
+The SAMBA Mailing list <URL:mailto:samba@samba.org>
+is the preferred place to ask questions regarding these programs.
.PP
-The conversion of this manpage for Samba 2\&.2 was performed by Gerald Carter\&. The conversion to DocBook XML 4\&.2 for Samba 3\&.0 was done by Alexander Bokovoy\&.
-
+The conversion of this manpage for Samba 2.2 was performed
+by Gerald Carter
diff --git a/docs/manpages/smbpasswd.5 b/docs/manpages/smbpasswd.5
index 75645d4b6a..07b04530c3 100644
--- a/docs/manpages/smbpasswd.5
+++ b/docs/manpages/smbpasswd.5
@@ -1,111 +1,157 @@
-.\"Generated by db2man.xsl. Don't modify this, modify the source.
-.de Sh \" Subsection
-.br
-.if t .Sp
-.ne 5
-.PP
-\fB\\$1\fR
-.PP
-..
-.de Sp \" Vertical space (when we can't use .PP)
-.if t .sp .5v
-.if n .sp
-..
-.de Ip \" List item
-.br
-.ie \\n(.$>=3 .ne \\$3
-.el .ne 3
-.IP "\\$1" \\$2
-..
-.TH "SMBPASSWD" 5 "" "" ""
+.\" This manpage has been automatically generated by docbook2man
+.\" from a DocBook document. This tool can be found at:
+.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
+.\" Please send any bug reports, improvements, comments, patches,
+.\" etc. to Steve Cheng <steve@ggi-project.org>.
+.TH "SMBPASSWD" "5" "04 March 2003" "" ""
.SH NAME
smbpasswd \- The Samba encrypted password file
-.SH "SYNOPSIS"
-
+.SH SYNOPSIS
.PP
\fIsmbpasswd\fR
-
.SH "DESCRIPTION"
-
.PP
-This tool is part of the \fBSamba\fR(7) suite\&.
-
+This tool is part of the Samba suite.
.PP
-smbpasswd is the Samba encrypted password file\&. It contains the username, Unix user id and the SMB hashed passwords of the user, as well as account flag information and the time the password was last changed\&. This file format has been evolving with Samba and has had several different formats in the past\&.
-
+smbpasswd is the Samba encrypted password file. It contains
+the username, Unix user id and the SMB hashed passwords of the
+user, as well as account flag information and the time the
+password was last changed. This file format has been evolving with
+Samba and has had several different formats in the past.
.SH "FILE FORMAT"
-
.PP
-The format of the smbpasswd file used by Samba 2\&.2 is very similar to the familiar Unix \fIpasswd(5)\fR file\&. It is an ASCII file containing one line for each user\&. Each field ithin each line is separated from the next by a colon\&. Any entry beginning with '#' is ignored\&. The smbpasswd file contains the following information for each user:
-
+The format of the smbpasswd file used by Samba 2.2
+is very similar to the familiar Unix \fIpasswd(5)\fR
+file. It is an ASCII file containing one line for each user. Each field
+ithin each line is separated from the next by a colon. Any entry
+beginning with '#' is ignored. The smbpasswd file contains the
+following information for each user:
.TP
-name
-This is the user name\&. It must be a name that already exists in the standard UNIX passwd file\&.
-
-
+\fBname\fR
+This is the user name. It must be a name that
+already exists in the standard UNIX passwd file.
.TP
-uid
-This is the UNIX uid\&. It must match the uid field for the same user entry in the standard UNIX passwd file\&. If this does not match then Samba will refuse to recognize this smbpasswd file entry as being valid for a user\&.
-
-
+\fBuid\fR
+This is the UNIX uid. It must match the uid
+field for the same user entry in the standard UNIX passwd file.
+If this does not match then Samba will refuse to recognize
+this smbpasswd file entry as being valid for a user.
.TP
-Lanman Password Hash
-This is the LANMAN hash of the user's password, encoded as 32 hex digits\&. The LANMAN hash is created by DES encrypting a well known string with the user's password as the DES key\&. This is the same password used by Windows 95/98 machines\&. Note that this password hash is regarded as weak as it is vulnerable to dictionary attacks and if two users choose the same password this entry will be identical (i\&.e\&. the password is not "salted" as the UNIX password is)\&. If the user has a null password this field will contain the characters "NO PASSWORD" as the start of the hex string\&. If the hex string is equal to 32 'X' characters then the user's account is marked as \fBdisabled\fR and the user will not be able to log onto the Samba server\&.
-
-
-\fBWARNING !!\fR Note that, due to the challenge-response nature of the SMB/CIFS authentication protocol, anyone with a knowledge of this password hash will be able to impersonate the user on the network\&. For this reason these hashes are known as \fBplain text equivalents\fR and must \fBNOT\fR be made available to anyone but the root user\&. To protect these passwords the smbpasswd file is placed in a directory with read and traverse access only to the root user and the smbpasswd file itself must be set to be read/write only by root, with no other access\&.
-
-
+\fBLanman Password Hash\fR
+This is the LANMAN hash of the user's password,
+encoded as 32 hex digits. The LANMAN hash is created by DES
+encrypting a well known string with the user's password as the
+DES key. This is the same password used by Windows 95/98 machines.
+Note that this password hash is regarded as weak as it is
+vulnerable to dictionary attacks and if two users choose the
+same password this entry will be identical (i.e. the password
+is not "salted" as the UNIX password is). If the user has a
+null password this field will contain the characters "NO PASSWORD"
+as the start of the hex string. If the hex string is equal to
+32 'X' characters then the user's account is marked as
+disabled and the user will not be able to
+log onto the Samba server.
+
+\fBWARNING !!\fR Note that, due to
+the challenge-response nature of the SMB/CIFS authentication
+protocol, anyone with a knowledge of this password hash will
+be able to impersonate the user on the network. For this
+reason these hashes are known as \fBplain text
+equivalents\fR and must \fBNOT\fR be made
+available to anyone but the root user. To protect these passwords
+the smbpasswd file is placed in a directory with read and
+traverse access only to the root user and the smbpasswd file
+itself must be set to be read/write only by root, with no
+other access.
.TP
-NT Password Hash
-This is the Windows NT hash of the user's password, encoded as 32 hex digits\&. The Windows NT hash is created by taking the user's password as represented in 16-bit, little-endian UNICODE and then applying the MD4 (internet rfc1321) hashing algorithm to it\&.
-
-
-This password hash is considered more secure than the LANMAN Password Hash as it preserves the case of the password and uses a much higher quality hashing algorithm\&. However, it is still the case that if two users choose the same password this entry will be identical (i\&.e\&. the password is not "salted" as the UNIX password is)\&.
-
-
-\fBWARNING !!\fR\&. Note that, due to the challenge-response nature of the SMB/CIFS authentication protocol, anyone with a knowledge of this password hash will be able to impersonate the user on the network\&. For this reason these hashes are known as \fBplain text equivalents\fR and must \fBNOT\fR be made available to anyone but the root user\&. To protect these passwords the smbpasswd file is placed in a directory with read and traverse access only to the root user and the smbpasswd file itself must be set to be read/write only by root, with no other access\&.
-
-
+\fBNT Password Hash\fR
+This is the Windows NT hash of the user's
+password, encoded as 32 hex digits. The Windows NT hash is
+created by taking the user's password as represented in
+16-bit, little-endian UNICODE and then applying the MD4
+(internet rfc1321) hashing algorithm to it.
+
+This password hash is considered more secure than
+the LANMAN Password Hash as it preserves the case of the
+password and uses a much higher quality hashing algorithm.
+However, it is still the case that if two users choose the same
+password this entry will be identical (i.e. the password is
+not "salted" as the UNIX password is).
+
+\fBWARNING !!\fR. Note that, due to
+the challenge-response nature of the SMB/CIFS authentication
+protocol, anyone with a knowledge of this password hash will
+be able to impersonate the user on the network. For this
+reason these hashes are known as \fBplain text
+equivalents\fR and must \fBNOT\fR be made
+available to anyone but the root user. To protect these passwords
+the smbpasswd file is placed in a directory with read and
+traverse access only to the root user and the smbpasswd file
+itself must be set to be read/write only by root, with no
+other access.
.TP
-Account Flags
-This section contains flags that describe the attributes of the users account\&. In the Samba 2\&.2 release this field is bracketed by '[' and ']' characters and is always 13 characters in length (including the '[' and ']' characters)\&. The contents of this field may be any of the following characters:
-
-
-\fBU\fR - This means this is a "User" account, i\&.e\&. an ordinary user\&. Only User and Workstation Trust accounts are currently supported in the smbpasswd file\&.
-
-\fBN\fR - This means the account has no password (the passwords in the fields LANMAN Password Hash and NT Password Hash are ignored)\&. Note that this will only allow users to log on with no password if the \fI null passwords\fR parameter is set in the \fBsmb.conf\fR(5) config file\&.
-
-\fBD\fR - This means the account is disabled and no SMB/CIFS logins will be allowed for this user\&.
-
-\fBW\fR - This means this account is a "Workstation Trust" account\&. This kind of account is used in the Samba PDC code stream to allow Windows NT Workstations and Servers to join a Domain hosted by a Samba PDC\&.
-
-Other flags may be added as the code is extended in future\&. The rest of this field space is filled in with spaces\&.
-
-
+\fBAccount Flags\fR
+This section contains flags that describe
+the attributes of the users account. In the Samba 2.2 release
+this field is bracketed by '[' and ']' characters and is always
+13 characters in length (including the '[' and ']' characters).
+The contents of this field may be any of the characters.
+.RS
+.TP 0.2i
+\(bu
+\fBU\fR - This means
+this is a "User" account, i.e. an ordinary user. Only User
+and Workstation Trust accounts are currently supported
+in the smbpasswd file.
+.TP 0.2i
+\(bu
+\fBN\fR - This means the
+account has no password (the passwords in the fields LANMAN
+Password Hash and NT Password Hash are ignored). Note that this
+will only allow users to log on with no password if the \fI null passwords\fR parameter is set in the \fIsmb.conf(5)
+\fR config file.
+.TP 0.2i
+\(bu
+\fBD\fR - This means the account
+is disabled and no SMB/CIFS logins will be allowed for
+this user.
+.TP 0.2i
+\(bu
+\fBW\fR - This means this account
+is a "Workstation Trust" account. This kind of account is used
+in the Samba PDC code stream to allow Windows NT Workstations
+and Servers to join a Domain hosted by a Samba PDC.
+.RE
+
+Other flags may be added as the code is extended in future.
+The rest of this field space is filled in with spaces.
.TP
-Last Change Time
-This field consists of the time the account was last modified\&. It consists of the characters 'LCT-' (standing for "Last Change Time") followed by a numeric encoding of the UNIX time in seconds since the epoch (1970) that the last change was made\&.
-
-
+\fBLast Change Time\fR
+This field consists of the time the account was
+last modified. It consists of the characters 'LCT-' (standing for
+"Last Change Time") followed by a numeric encoding of the UNIX time
+in seconds since the epoch (1970) that the last change was made.
.PP
-All other colon separated fields are ignored at this time\&.
-
+All other colon separated fields are ignored at this time.
.SH "VERSION"
-
.PP
-This man page is correct for version 3\&.0 of the Samba suite\&.
-
+This man page is correct for version 3.0 of
+the Samba suite.
.SH "SEE ALSO"
-
.PP
-\fBsmbpasswd\fR(8), \fBSamba\fR(7), and the Internet RFC1321 for details on the MD4 algorithm\&.
-
+\fBsmbpasswd(8)\fR
+samba(7) and
+the Internet RFC1321 for details on the MD4 algorithm.
.SH "AUTHOR"
-
.PP
-The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&.
-
+The original Samba software and related utilities
+were created by Andrew Tridgell. Samba is now developed
+by the Samba Team as an Open Source project similar
+to the way the Linux kernel is developed.
.PP
-The original Samba man pages were written by Karl Auer\&. The man page sources were converted to YODL format (another excellent piece of Open Source software, available at ftp://ftp\&.icce\&.rug\&.nl/pub/unix/) and updated for the Samba 2\&.0 release by Jeremy Allison\&. The conversion to DocBook for Samba 2\&.2 was done by Gerald Carter\&. The conversion to DocBook XML 4\&.2 for Samba 3\&.0 was done by Alexander Bokovoy\&.
-
+The original Samba man pages were written by Karl Auer.
+The man page sources were converted to YODL format (another
+excellent piece of Open Source software, available at
+ftp://ftp.icce.rug.nl/pub/unix/ <URL:ftp://ftp.icce.rug.nl/pub/unix/>) and updated for the Samba 2.0
+release by Jeremy Allison. The conversion to DocBook for
+Samba 2.2 was done by Gerald Carter
diff --git a/docs/manpages/smbpasswd.8 b/docs/manpages/smbpasswd.8
index a7973871c4..5c7b16c2e9 100644
--- a/docs/manpages/smbpasswd.8
+++ b/docs/manpages/smbpasswd.8
@@ -1,219 +1,293 @@
-.\"Generated by db2man.xsl. Don't modify this, modify the source.
-.de Sh \" Subsection
-.br
-.if t .Sp
-.ne 5
-.PP
-\fB\\$1\fR
-.PP
-..
-.de Sp \" Vertical space (when we can't use .PP)
-.if t .sp .5v
-.if n .sp
-..
-.de Ip \" List item
-.br
-.ie \\n(.$>=3 .ne \\$3
-.el .ne 3
-.IP "\\$1" \\$2
-..
-.TH "SMBPASSWD" 8 "" "" ""
+.\" This manpage has been automatically generated by docbook2man
+.\" from a DocBook document. This tool can be found at:
+.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
+.\" Please send any bug reports, improvements, comments, patches,
+.\" etc. to Steve Cheng <steve@ggi-project.org>.
+.TH "SMBPASSWD" "8" "04 March 2003" "" ""
.SH NAME
smbpasswd \- change a user's SMB password
-.SH "SYNOPSIS"
+.SH SYNOPSIS
-.nf
-\fBsmbpasswd\fR [-a] [-x] [-d] [-e] [-D debuglevel] [-n] [-r <remote machine>] [-R <name resolve order>] [-m] [-U username[%password]] [-h] [-s] [-w pass] [-i] [-L] [username]
-
-.fi
+\fBsmbpasswd\fR [ \fB-a\fR ] [ \fB-x\fR ] [ \fB-d\fR ] [ \fB-e\fR ] [ \fB-D debuglevel\fR ] [ \fB-n\fR ] [ \fB-r <remote machine>\fR ] [ \fB-R <name resolve order>\fR ] [ \fB-m\fR ] [ \fB-U username[%password]\fR ] [ \fB-h\fR ] [ \fB-s\fR ] [ \fB-w pass\fR ] [ \fB-i\fR ] [ \fB-L\fR ] [ \fBusername\fR ]
.SH "DESCRIPTION"
-
.PP
-This tool is part of the \fBSamba\fR(7) suite\&.
-
+This tool is part of the Samba suite.
.PP
-The smbpasswd program has several different functions, depending on whether it is run by the \fBroot\fR user or not\&. When run as a normal user it allows the user to change the password used for their SMB sessions on any machines that store SMB passwords\&.
-
+The smbpasswd program has several different
+functions, depending on whether it is run by the \fBroot\fR
+user or not. When run as a normal user it allows the user to change
+the password used for their SMB sessions on any machines that store
+SMB passwords.
.PP
-By default (when run with no arguments) it will attempt to change the current user's SMB password on the local machine\&. This is similar to the way the \fBpasswd(1)\fR program works\&. \fB smbpasswd\fR differs from how the passwd program works however in that it is not \fBsetuid root\fR but works in a client-server mode and communicates with a locally running \fBsmbd\fR(8)\&. As a consequence in order for this to succeed the smbd daemon must be running on the local machine\&. On a UNIX machine the encrypted SMB passwords are usually stored in the \fBsmbpasswd\fR(5) file\&.
-
+By default (when run with no arguments) it will attempt to
+change the current user's SMB password on the local machine. This is
+similar to the way the \fBpasswd(1)\fR program works.
+\fBsmbpasswd\fR differs from how the passwd program works
+however in that it is not \fBsetuid root\fR but works in
+a client-server mode and communicates with a locally running
+\fBsmbd(8)\fR. As a consequence in order for this to
+succeed the smbd daemon must be running on the local machine. On a
+UNIX machine the encrypted SMB passwords are usually stored in
+the \fIsmbpasswd(5)\fR file.
.PP
-When run by an ordinary user with no options, smbpasswd will prompt them for their old SMB password and then ask them for their new password twice, to ensure that the new password was typed correctly\&. No passwords will be echoed on the screen whilst being typed\&. If you have a blank SMB password (specified by the string "NO PASSWORD" in the smbpasswd file) then just press the <Enter> key when asked for your old password\&.
-
+When run by an ordinary user with no options, smbpasswd
+will prompt them for their old SMB password and then ask them
+for their new password twice, to ensure that the new password
+was typed correctly. No passwords will be echoed on the screen
+whilst being typed. If you have a blank SMB password (specified by
+the string "NO PASSWORD" in the smbpasswd file) then just press
+the <Enter> key when asked for your old password.
.PP
-smbpasswd can also be used by a normal user to change their SMB password on remote machines, such as Windows NT Primary Domain Controllers\&. See the (\fI-r\fR) and \fI-U\fR options below\&.
-
+smbpasswd can also be used by a normal user to change their
+SMB password on remote machines, such as Windows NT Primary Domain
+Controllers. See the (-r) and -U options below.
.PP
-When run by root, smbpasswd allows new users to be added and deleted in the smbpasswd file, as well as allows changes to the attributes of the user in this file to be made\&. When run by root, \fB smbpasswd\fR accesses the local smbpasswd file directly, thus enabling changes to be made even if smbd is not running\&.
-
+When run by root, smbpasswd allows new users to be added
+and deleted in the smbpasswd file, as well as allows changes to
+the attributes of the user in this file to be made. When run by root,
+\fBsmbpasswd\fR accesses the local smbpasswd file
+directly, thus enabling changes to be made even if smbd is not
+running.
.SH "OPTIONS"
-
.TP
--a
-This option specifies that the username following should be added to the local smbpasswd file, with the new password typed (type <Enter> for the old password)\&. This option is ignored if the username following already exists in the smbpasswd file and it is treated like a regular change password command\&. Note that the default passdb backends require the user to already exist in the system password file (usually \fI/etc/passwd\fR), else the request to add the user will fail\&.
-
-
-This option is only available when running smbpasswd as root\&.
-
-
+\fB-a\fR
+This option specifies that the username
+following should be added to the local smbpasswd file, with the
+new password typed (type <Enter> for the old password). This
+option is ignored if the username following already exists in
+the smbpasswd file and it is treated like a regular change
+password command. Note that the default passdb backends require
+the user to already exist in the system password file (usually
+\fI/etc/passwd\fR), else the request to add the
+user will fail.
+
+This option is only available when running smbpasswd
+as root.
.TP
--x
-This option specifies that the username following should be deleted from the local smbpasswd file\&.
-
-
-This option is only available when running smbpasswd as root\&.
-
+\fB-x\fR
+This option specifies that the username
+following should be deleted from the local smbpasswd file.
+This option is only available when running smbpasswd as
+root.
.TP
--d
-This option specifies that the username following should be \fBdisabled\fR in the local smbpasswd file\&. This is done by writing a \fB'D'\fR flag into the account control space in the smbpasswd file\&. Once this is done all attempts to authenticate via SMB using this username will fail\&.
-
-
-If the smbpasswd file is in the 'old' format (pre-Samba 2\&.0 format) there is no space in the user's password entry to write this information and the command will FAIL\&. See \fBsmbpasswd\fR(5) for details on the 'old' and new password file formats\&.
-
-
-This option is only available when running smbpasswd as root\&.
-
-
+\fB-d\fR
+This option specifies that the username following
+should be disabled in the local smbpasswd
+file. This is done by writing a 'D' flag
+into the account control space in the smbpasswd file. Once this
+is done all attempts to authenticate via SMB using this username
+will fail.
+
+If the smbpasswd file is in the 'old' format (pre-Samba 2.0
+format) there is no space in the user's password entry to write
+this information and the command will FAIL. See \fBsmbpasswd(5)
+\fR for details on the 'old' and new password file formats.
+
+This option is only available when running smbpasswd as
+root.
.TP
--e
-This option specifies that the username following should be \fBenabled\fR in the local smbpasswd file, if the account was previously disabled\&. If the account was not disabled this option has no effect\&. Once the account is enabled then the user will be able to authenticate via SMB once again\&.
-
-
-If the smbpasswd file is in the 'old' format, then \fB smbpasswd\fR will FAIL to enable the account\&. See \fBsmbpasswd\fR(5) for details on the 'old' and new password file formats\&.
-
-
-This option is only available when running smbpasswd as root\&.
-
-
+\fB-e\fR
+This option specifies that the username following
+should be enabled in the local smbpasswd file,
+if the account was previously disabled. If the account was not
+disabled this option has no effect. Once the account is enabled then
+the user will be able to authenticate via SMB once again.
+
+If the smbpasswd file is in the 'old' format, then \fB smbpasswd\fR will FAIL to enable the account.
+See \fBsmbpasswd (5)\fR for
+details on the 'old' and new password file formats.
+
+This option is only available when running smbpasswd as root.
.TP
--D debuglevel
-\fIdebuglevel\fR is an integer from 0 to 10\&. The default value if this parameter is not specified is zero\&.
-
-
-The higher this value, the more detail will be logged to the log files about the activities of smbpasswd\&. At level 0, only critical errors and serious warnings will be logged\&.
-
-
-Levels above 1 will generate considerable amounts of log data, and should only be used when investigating a problem\&. Levels above 3 are designed for use only by developers and generate HUGE amounts of log data, most of which is extremely cryptic\&.
-
-
+\fB-D debuglevel\fR
+\fIdebuglevel\fR is an integer
+from 0 to 10. The default value if this parameter is not specified
+is zero.
+
+The higher this value, the more detail will be logged to the
+log files about the activities of smbpasswd. At level 0, only
+critical errors and serious warnings will be logged.
+
+Levels above 1 will generate considerable amounts of log
+data, and should only be used when investigating a problem. Levels
+above 3 are designed for use only by developers and generate
+HUGE amounts of log data, most of which is extremely cryptic.
.TP
--n
-This option specifies that the username following should have their password set to null (i\&.e\&. a blank password) in the local smbpasswd file\&. This is done by writing the string "NO PASSWORD" as the first part of the first password stored in the smbpasswd file\&.
-
-
-Note that to allow users to logon to a Samba server once the password has been set to "NO PASSWORD" in the smbpasswd file the administrator must set the following parameter in the [global] section of the \fIsmb\&.conf\fR file :
-
+\fB-n\fR
+This option specifies that the username following
+should have their password set to null (i.e. a blank password) in
+the local smbpasswd file. This is done by writing the string "NO
+PASSWORD" as the first part of the first password stored in the
+smbpasswd file.
+
+Note that to allow users to logon to a Samba server once
+the password has been set to "NO PASSWORD" in the smbpasswd
+file the administrator must set the following parameter in the [global]
+section of the \fIsmb.conf\fR file :
\fBnull passwords = yes\fR
-
-This option is only available when running smbpasswd as root\&.
-
-
+This option is only available when running smbpasswd as
+root.
.TP
--r remote machine name
-This option allows a user to specify what machine they wish to change their password on\&. Without this parameter smbpasswd defaults to the local host\&. The \fIremote machine name\fR is the NetBIOS name of the SMB/CIFS server to contact to attempt the password change\&. This name is resolved into an IP address using the standard name resolution mechanism in all programs of the Samba suite\&. See the \fI-R name resolve order\fR parameter for details on changing this resolving mechanism\&.
-
-
-The username whose password is changed is that of the current UNIX logged on user\&. See the \fI-U username\fR parameter for details on changing the password for a different username\&.
-
-
-Note that if changing a Windows NT Domain password the remote machine specified must be the Primary Domain Controller for the domain (Backup Domain Controllers only have a read-only copy of the user account database and will not allow the password change)\&.
-
-
-\fBNote\fR that Windows 95/98 do not have a real password database so it is not possible to change passwords specifying a Win95/98 machine as remote machine target\&.
-
-
+\fB-r remote machine name\fR
+This option allows a user to specify what machine
+they wish to change their password on. Without this parameter
+smbpasswd defaults to the local host. The \fIremote
+machine name\fR is the NetBIOS name of the SMB/CIFS
+server to contact to attempt the password change. This name is
+resolved into an IP address using the standard name resolution
+mechanism in all programs of the Samba suite. See the \fI-R
+name resolve order\fR parameter for details on changing
+this resolving mechanism.
+
+The username whose password is changed is that of the
+current UNIX logged on user. See the \fI-U username\fR
+parameter for details on changing the password for a different
+username.
+
+Note that if changing a Windows NT Domain password the
+remote machine specified must be the Primary Domain Controller for
+the domain (Backup Domain Controllers only have a read-only
+copy of the user account database and will not allow the password
+change).
+
+\fBNote\fR that Windows 95/98 do not have
+a real password database so it is not possible to change passwords
+specifying a Win95/98 machine as remote machine target.
.TP
--R name resolve order
-This option allows the user of smbpasswd to determine what name resolution services to use when looking up the NetBIOS name of the host being connected to\&.
-
-
-The options are :"lmhosts", "host", "wins" and "bcast"\&. They cause names to be resolved as follows:
-
-
-\fBlmhosts\fR: Lookup an IP address in the Samba lmhosts file\&. If the line in lmhosts has no name type attached to the NetBIOS name (see the \fBlmhosts\fR(5) for details) then any name type matches for lookup\&.
-
-\fBhost\fR: Do a standard host name to IP address resolution, using the system \fI/etc/hosts \fR, NIS, or DNS lookups\&. This method of name resolution is operating system depended for instance on IRIX or Solaris this may be controlled by the \fI/etc/nsswitch\&.conf\fR file)\&. Note that this method is only used if the NetBIOS name type being queried is the 0x20 (server) name type, otherwise it is ignored\&.
-
-\fBwins\fR: Query a name with the IP address listed in the \fIwins server\fR parameter\&. If no WINS server has been specified this method will be ignored\&.
-
-\fBbcast\fR: Do a broadcast on each of the known local interfaces listed in the \fIinterfaces\fR parameter\&. This is the least reliable of the name resolution methods as it depends on the target host being on a locally connected subnet\&.
-
-The default order is \fBlmhosts, host, wins, bcast\fR and without this parameter or any entry in the \fBsmb.conf\fR(5) file the name resolution methods will be attempted in this order\&.
-
-
+\fB-R name resolve order\fR
+This option allows the user of smbpasswd to determine
+what name resolution services to use when looking up the NetBIOS
+name of the host being connected to.
+
+The options are :"lmhosts", "host", "wins" and "bcast". They
+cause names to be resolved as follows :
+.RS
+.TP 0.2i
+\(bu
+lmhosts : Lookup an IP
+address in the Samba lmhosts file. If the line in lmhosts has
+no name type attached to the NetBIOS name (see the lmhosts(5) for details) then
+any name type matches for lookup.
+.TP 0.2i
+\(bu
+host : Do a standard host
+name to IP address resolution, using the system \fI/etc/hosts
+\fR, NIS, or DNS lookups. This method of name resolution
+is operating system depended for instance on IRIX or Solaris this
+may be controlled by the \fI/etc/nsswitch.conf\fR
+file). Note that this method is only used if the NetBIOS name
+type being queried is the 0x20 (server) name type, otherwise
+it is ignored.
+.TP 0.2i
+\(bu
+wins : Query a name with
+the IP address listed in the \fIwins server\fR
+parameter. If no WINS server has been specified this method
+will be ignored.
+.TP 0.2i
+\(bu
+bcast : Do a broadcast on
+each of the known local interfaces listed in the
+\fIinterfaces\fR parameter. This is the least
+reliable of the name resolution methods as it depends on the
+target host being on a locally connected subnet.
+.RE
+
+The default order is \fBlmhosts, host, wins, bcast\fR
+and without this parameter or any entry in the
+\fIsmb.conf\fR file the name resolution methods will
+be attempted in this order.
.TP
--m
-This option tells smbpasswd that the account being changed is a MACHINE account\&. Currently this is used when Samba is being used as an NT Primary Domain Controller\&.
-
-
-This option is only available when running smbpasswd as root\&.
-
+\fB-m\fR
+This option tells smbpasswd that the account
+being changed is a MACHINE account. Currently this is used
+when Samba is being used as an NT Primary Domain Controller.
+This option is only available when running smbpasswd as root.
.TP
--U username
-This option may only be used in conjunction with the \fI-r\fR option\&. When changing a password on a remote machine it allows the user to specify the user name on that machine whose password will be changed\&. It is present to allow users who have different user names on different systems to change these passwords\&.
-
-
+\fB-U username\fR
+This option may only be used in conjunction
+with the \fI-r\fR option. When changing
+a password on a remote machine it allows the user to specify
+the user name on that machine whose password will be changed. It
+is present to allow users who have different user names on
+different systems to change these passwords.
.TP
--h
-This option prints the help string for \fB smbpasswd\fR, selecting the correct one for running as root or as an ordinary user\&.
-
-
+\fB-h\fR
+This option prints the help string for \fB smbpasswd\fR, selecting the correct one for running as root
+or as an ordinary user.
.TP
--s
-This option causes smbpasswd to be silent (i\&.e\&. not issue prompts) and to read its old and new passwords from standard input, rather than from \fI/dev/tty\fR (like the \fBpasswd(1)\fR program does)\&. This option is to aid people writing scripts to drive smbpasswd
-
-
+\fB-s\fR
+This option causes smbpasswd to be silent (i.e.
+not issue prompts) and to read its old and new passwords from
+standard input, rather than from \fI/dev/tty\fR
+(like the \fBpasswd(1)\fR program does). This option
+is to aid people writing scripts to drive smbpasswd
.TP
--w password
-This parameter is only available if Samba has been configured to use the experimental \fB--with-ldapsam\fR option\&. The \fI-w\fR switch is used to specify the password to be used with the \fIldap admin dn\fR\&. Note that the password is stored in the \fIsecrets\&.tdb\fR and is keyed off of the admin's DN\&. This means that if the value of \fIldap admin dn\fR ever changes, the password will need to be manually updated as well\&.
-
-
+\fB-w password\fR
+This parameter is only available if Samba
+has been configured to use the experimental
+\fB--with-ldapsam\fR option. The \fI-w\fR
+switch is used to specify the password to be used with the
+\fIldap admin
+dn\fR Note that the password is stored in
+the \fIprivate/secrets.tdb\fR and is keyed off
+of the admin's DN. This means that if the value of \fIldap
+admin dn\fR ever changes, the password will need to be
+manually updated as well.
.TP
--i
-This option tells smbpasswd that the account being changed is an interdomain trust account\&. Currently this is used when Samba is being used as an NT Primary Domain Controller\&. The account contains the info about another trusted domain\&.
-
-
-This option is only available when running smbpasswd as root\&.
-
+\fB-i\fR
+This option tells smbpasswd that the account
+being changed is an interdomain trust account. Currently this is used
+when Samba is being used as an NT Primary Domain Controller.
+The account contains the info about another trusted domain.
+This option is only available when running smbpasswd as root.
.TP
--L
-Run in local mode\&.
-
-
+\fB-L\fR
+Run in local mode.
.TP
-username
-This specifies the username for all of the \fBroot only\fR options to operate on\&. Only root can specify this parameter as only root has the permission needed to modify attributes directly in the local smbpasswd file\&.
-
-
+\fBusername\fR
+This specifies the username for all of the
+\fBroot only\fR options to operate on. Only root
+can specify this parameter as only root has the permission needed
+to modify attributes directly in the local smbpasswd file.
.SH "NOTES"
-
.PP
-Since \fBsmbpasswd\fR works in client-server mode communicating with a local smbd for a non-root user then the smbd daemon must be running for this to work\&. A common problem is to add a restriction to the hosts that may access the \fB smbd\fR running on the local machine by specifying either \fIallow hosts\fR or \fIdeny hosts\fR entry in the \fBsmb.conf\fR(5) file and neglecting to allow "localhost" access to the smbd\&.
-
+Since \fBsmbpasswd\fR works in client-server
+mode communicating with a local smbd for a non-root user then
+the smbd daemon must be running for this to work. A common problem
+is to add a restriction to the hosts that may access the \fB smbd\fR running on the local machine by specifying a
+\fIallow hosts\fR or \fIdeny hosts\fR
+entry in the \fIsmb.conf\fR file and neglecting to
+allow "localhost" access to the smbd.
.PP
-In addition, the smbpasswd command is only useful if Samba has been set up to use encrypted passwords\&. See the document "LanMan and NT Password Encryption in Samba" in the docs directory for details on how to do this\&.
-
+In addition, the smbpasswd command is only useful if Samba
+has been set up to use encrypted passwords. See the file
+\fIENCRYPTION.txt\fR in the docs directory for details
+on how to do this.
.SH "VERSION"
-
.PP
-This man page is correct for version 3\&.0 of the Samba suite\&.
-
+This man page is correct for version 3.0 of
+the Samba suite.
.SH "SEE ALSO"
-
.PP
-\fBsmbpasswd\fR(5), \fBSamba\fR(7)\&.
-
+\fIsmbpasswd(5)\fR
+samba(7)
.SH "AUTHOR"
-
.PP
-The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&.
-
+The original Samba software and related utilities
+were created by Andrew Tridgell. Samba is now developed
+by the Samba Team as an Open Source project similar
+to the way the Linux kernel is developed.
.PP
-The original Samba man pages were written by Karl Auer\&. The man page sources were converted to YODL format (another excellent piece of Open Source software, available at ftp://ftp\&.icce\&.rug\&.nl/pub/unix/) and updated for the Samba 2\&.0 release by Jeremy Allison\&. The conversion to DocBook for Samba 2\&.2 was done by Gerald Carter\&. The conversion to DocBook XML 4\&.2 for Samba 3\&.0 was done by Alexander Bokovoy\&.
-
+The original Samba man pages were written by Karl Auer.
+The man page sources were converted to YODL format (another
+excellent piece of Open Source software, available at
+ftp://ftp.icce.rug.nl/pub/unix/ <URL:ftp://ftp.icce.rug.nl/pub/unix/>) and updated for the Samba 2.0
+release by Jeremy Allison. The conversion to DocBook for
+Samba 2.2 was done by Gerald Carter
diff --git a/docs/manpages/smbsh.1 b/docs/manpages/smbsh.1
index 0e2c4a3a85..06d27090db 100644
--- a/docs/manpages/smbsh.1
+++ b/docs/manpages/smbsh.1
@@ -1,141 +1,170 @@
-.\"Generated by db2man.xsl. Don't modify this, modify the source.
-.de Sh \" Subsection
-.br
-.if t .Sp
-.ne 5
-.PP
-\fB\\$1\fR
-.PP
-..
-.de Sp \" Vertical space (when we can't use .PP)
-.if t .sp .5v
-.if n .sp
-..
-.de Ip \" List item
-.br
-.ie \\n(.$>=3 .ne \\$3
-.el .ne 3
-.IP "\\$1" \\$2
-..
-.TH "SMBSH" 1 "" "" ""
+.\" This manpage has been automatically generated by docbook2man
+.\" from a DocBook document. This tool can be found at:
+.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
+.\" Please send any bug reports, improvements, comments, patches,
+.\" etc. to Steve Cheng <steve@ggi-project.org>.
+.TH "SMBSH" "1" "04 March 2003" "" ""
.SH NAME
-smbsh \- Allows access to Windows NT filesystem using UNIX commands
-.SH "SYNOPSIS"
+smbsh \- Allows access to Windows NT filesystem using UNIX commands
+.SH SYNOPSIS
-.nf
-\fBsmbsh\fR [-W workgroup] [-U username] [-P prefix] [-R <name resolve order>] [-d <debug level>] [-l logfile] [-L libdir]
-
-.fi
+\fBsmbsh\fR [ \fB-W workgroup\fR ] [ \fB-U username\fR ] [ \fB-P prefix\fR ] [ \fB-R <name resolve order>\fR ] [ \fB-d <debug level>\fR ] [ \fB-l logfile\fR ] [ \fB-L libdir\fR ]
.SH "DESCRIPTION"
-
.PP
-This tool is part of the \fBSamba\fR(7) suite\&.
-
+This tool is part of the Samba suite.
.PP
-\fBsmbsh\fR allows you to access an NT filesystem using UNIX commands such as \fBls\fR, \fB egrep\fR, and \fBrcp\fR\&. You must use a shell that is dynamically linked in order for \fBsmbsh\fR to work correctly\&.
-
+\fBsmbsh\fR allows you to access an NT filesystem
+using UNIX commands such as \fBls\fR, \fB egrep\fR, and \fBrcp\fR. You must use a
+shell that is dynamically linked in order for \fBsmbsh\fR
+to work correctly.
.SH "OPTIONS"
-
.TP
--W WORKGROUP
-Override the default workgroup specified in the workgroup parameter of the \fBsmb.conf\fR(5) file for this session\&. This may be needed to connect to some servers\&.
-
-
+\fB-W WORKGROUP\fR
+Override the default workgroup specified in the
+workgroup parameter of the \fIsmb.conf\fR file
+for this session. This may be needed to connect to some
+servers.
.TP
--U username[%pass]
-Sets the SMB username or username and password\&. If this option is not specified, the user will be prompted for both the username and the password\&. If %pass is not specified, the user will be prompted for the password\&.
-
-
+\fB-U username[%pass]\fR
+Sets the SMB username or username and password.
+If this option is not specified, the user will be prompted for
+both the username and the password. If %pass is not specified,
+the user will be prompted for the password.
.TP
--P prefix
-This option allows the user to set the directory prefix for SMB access\&. The default value if this option is not specified is \fBsmb\fR\&.
-
-
+\fB-P prefix\fR
+This option allows
+the user to set the directory prefix for SMB access. The
+default value if this option is not specified is
+\fBsmb\fR.
.TP
--s <configuration file>
-The file specified contains the configuration details required by the server\&. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is to provide\&. See \fI smb\&.conf(5)\fR for more information\&. The default configuration file name is determined at compile time\&.
-
-
+\fB-R <name resolve order>\fR
+This option is used to determine what naming
+services and in what order to resolve
+host names to IP addresses. The option takes a space-separated
+string of different name resolution options.
+
+The options are :"lmhosts", "host", "wins" and "bcast".
+They cause names to be resolved as follows :
+.RS
+.TP 0.2i
+\(bu
+lmhosts :
+Lookup an IP address in the Samba lmhosts file. If the
+line in lmhosts has no name type attached to the
+NetBIOS name
+(see the lmhosts(5)
+for details) then any name type matches for lookup.
+.TP 0.2i
+\(bu
+host :
+Do a standard host name to IP address resolution, using
+the system \fI/etc/hosts\fR, NIS, or DNS
+lookups. This method of name resolution is operating
+system dependent, for instance on IRIX or Solaris this
+may be controlled by the \fI/etc/nsswitch.conf
+\fR file). Note that this method is only used
+if the NetBIOS name type being queried is the 0x20
+(server) name type, otherwise it is ignored.
+.TP 0.2i
+\(bu
+wins :
+Query a name with the IP address listed in the
+\fIwins server\fR parameter. If no
+WINS server has been specified this method will be
+ignored.
+.TP 0.2i
+\(bu
+bcast :
+Do a broadcast on each of the known local interfaces
+listed in the \fIinterfaces\fR
+parameter. This is the least reliable of the name
+resolution methods as it depends on the target host
+being on a locally connected subnet.
+.RE
+
+If this parameter is not set then the name resolve order
+defined in the \fIsmb.conf\fR file parameter
+(name resolve order) will be used.
+
+The default order is lmhosts, host, wins, bcast. Without
+this parameter or any entry in the \fIname resolve order
+\fR parameter of the \fIsmb.conf\fR
+file, the name resolution methods will be attempted in this
+order.
.TP
--d|--debug=debuglevel
-\fIdebuglevel\fR is an integer from 0 to 10\&. The default value if this parameter is not specified is zero\&.
-
-
-The higher this value, the more detail will be logged to the log files about the activities of the server\&. At level 0, only critical errors and serious warnings will be logged\&. Level 1 is a reasonable level for day to day running - it generates a small amount of information about operations carried out\&.
-
-
-Levels above 1 will generate considerable amounts of log data, and should only be used when investigating a problem\&. Levels above 3 are designed for use only by developers and generate HUGE amounts of log data, most of which is extremely cryptic\&.
-
-
-Note that specifying this parameter here will override the log level parameter in the \fIsmb\&.conf(5)\fR file\&.
+\fB-d <debug level>\fR
+debug level is an integer from 0 to 10.
+The default value if this parameter is not specified
+is zero.
+The higher this value, the more detail will be logged
+about the activities of \fBnmblookup\fR. At level
+0, only critical errors and serious warnings will be logged.
.TP
--R <name resolve order>
-This option is used to determine what naming services and in what order to resolve host names to IP addresses\&. The option takes a space-separated string of different name resolution options\&.
-
-
-The options are: "lmhosts", "host", "wins" and "bcast"\&. They cause names to be resolved as follows :
-
-
-\fBlmhosts\fR: Lookup an IP address in the Samba lmhosts file\&. If the line in lmhosts has no name type attached to the NetBIOS name (see the \fBlmhosts\fR(5) for details) then any name type matches for lookup\&.
-
-\fBhost\fR: Do a standard host name to IP address resolution, using the system \fI/etc/hosts\fR, NIS, or DNS lookups\&. This method of name resolution is operating system dependent, for instance on IRIX or Solaris this may be controlled by the \fI/etc/nsswitch\&.conf \fR file)\&. Note that this method is only used if the NetBIOS name type being queried is the 0x20 (server) name type, otherwise it is ignored\&.
-
-\fBwins\fR: Query a name with the IP address listed in the \fIwins server\fR parameter\&. If no WINS server has been specified this method will be ignored\&.
-
-\fBbcast\fR: Do a broadcast on each of the known local interfaces listed in the \fIinterfaces\fR parameter\&. This is the least reliable of the name resolution methods as it depends on the target host being on a locally connected subnet\&.
-
-If this parameter is not set then the name resolve order defined in the \fBsmb.conf\fR(5) file parameter (\fIname resolve order\fR) will be used\&.
-
-
-The default order is lmhosts, host, wins, bcast\&. Without this parameter or any entry in the \fIname resolve order \fR parameter of the \fBsmb.conf\fR(5) file, the name resolution methods will be attempted in this order\&.
-
-
+\fB-l logfilename\fR
+If specified causes all debug messages to be
+written to the file specified by \fIlogfilename
+\fR. If not specified then all messages will be
+written to\fIstderr\fR.
.TP
--L libdir
-This parameter specifies the location of the shared libraries used by \fBsmbsh\fR\&. The default value is specified at compile time\&.
-
-
+\fB-L libdir\fR
+This parameter specifies the location of the
+shared libraries used by \fBsmbsh\fR. The default
+value is specified at compile time.
.SH "EXAMPLES"
-
.PP
-To use the \fBsmbsh\fR command, execute \fB smbsh\fR from the prompt and enter the username and password that authenticates you to the machine running the Windows NT operating system\&.
-.nf
+To use the \fBsmbsh\fR command, execute \fB smbsh\fR from the prompt and enter the username and password
+that authenticates you to the machine running the Windows NT
+operating system.
+.PP
-system% \fBsmbsh\fR
-Username: \fBuser\fR
-Password: \fBXXXXXXX\fR
+.nf
+ system% \fBsmbsh\fR
+ Username: \fBuser\fR
+ Password: \fBXXXXXXX\fR
+
.fi
-
-
.PP
-Any dynamically linked command you execute from this shell will access the \fI/smb\fR directory using the smb protocol\&. For example, the command \fBls /smb \fR will show a list of workgroups\&. The command\fBls /smb/MYGROUP \fR will show all the machines in the workgroup MYGROUP\&. The command\fBls /smb/MYGROUP/<machine-name>\fR will show the share names for that machine\&. You could then, for example, use the \fB cd\fR command to change directories, \fBvi\fR to edit files, and \fBrcp\fR to copy files\&.
-
+Any dynamically linked command you execute from
+this shell will access the \fI/smb\fR directory
+using the smb protocol. For example, the command \fBls /smb
+\fR will show a list of workgroups. The command
+\fBls /smb/MYGROUP \fR will show all the machines in
+the workgroup MYGROUP. The command
+\fBls /smb/MYGROUP/<machine-name>\fR will show the share
+names for that machine. You could then, for example, use the \fB cd\fR command to change directories, \fBvi\fR to
+edit files, and \fBrcp\fR to copy files.
.SH "VERSION"
-
.PP
-This man page is correct for version 3\&.0 of the Samba suite\&.
-
+This man page is correct for version 3.0 of
+the Samba suite.
.SH "BUGS"
-
.PP
-\fBsmbsh\fR works by intercepting the standard libc calls with the dynamically loaded versions in \fI smbwrapper\&.o\fR\&. Not all calls have been "wrapped", so some programs may not function correctly under \fBsmbsh \fR\&.
-
+\fBsmbsh\fR works by intercepting the standard
+libc calls with the dynamically loaded versions in \fI smbwrapper.o\fR. Not all calls have been "wrapped", so
+some programs may not function correctly under \fBsmbsh
+\fR.
.PP
-Programs which are not dynamically linked cannot make use of \fBsmbsh\fR's functionality\&. Most versions of UNIX have a \fBfile\fR command that will describe how a program was linked\&.
-
+Programs which are not dynamically linked cannot make
+use of \fBsmbsh\fR's functionality. Most versions
+of UNIX have a \fBfile\fR command that will
+describe how a program was linked.
.SH "SEE ALSO"
-
.PP
-\fBsmbd\fR(8), \fBsmb.conf\fR(5)
-
+\fBsmbd(8)\fR
+smb.conf(5)
.SH "AUTHOR"
-
.PP
-The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&.
-
+The original Samba software and related utilities
+were created by Andrew Tridgell. Samba is now developed
+by the Samba Team as an Open Source project similar
+to the way the Linux kernel is developed.
.PP
-The original Samba man pages were written by Karl Auer\&. The man page sources were converted to YODL format (another excellent piece of Open Source software, available at ftp://ftp\&.icce\&.rug\&.nl/pub/unix/) and updated for the Samba 2\&.0 release by Jeremy Allison\&. The conversion to DocBook for Samba 2\&.2 was done by Gerald Carter\&. The conversion to DocBook XML 4\&.2 for Samba 3\&.0 was done by Alexander Bokovoy\&.
-
+The original Samba man pages were written by Karl Auer.
+The man page sources were converted to YODL format (another
+excellent piece of Open Source software, available at
+ftp://ftp.icce.rug.nl/pub/unix/ <URL:ftp://ftp.icce.rug.nl/pub/unix/>) and updated for the Samba 2.0
+release by Jeremy Allison. The conversion to DocBook for
+Samba 2.2 was done by Gerald Carter
diff --git a/docs/manpages/smbspool.8 b/docs/manpages/smbspool.8
index a6413547b8..835494b534 100644
--- a/docs/manpages/smbspool.8
+++ b/docs/manpages/smbspool.8
@@ -1,115 +1,101 @@
-.\"Generated by db2man.xsl. Don't modify this, modify the source.
-.de Sh \" Subsection
-.br
-.if t .Sp
-.ne 5
-.PP
-\fB\\$1\fR
-.PP
-..
-.de Sp \" Vertical space (when we can't use .PP)
-.if t .sp .5v
-.if n .sp
-..
-.de Ip \" List item
-.br
-.ie \\n(.$>=3 .ne \\$3
-.el .ne 3
-.IP "\\$1" \\$2
-..
-.TH "SMBSPOOL" 8 "" "" ""
+.\" This manpage has been automatically generated by docbook2man
+.\" from a DocBook document. This tool can be found at:
+.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
+.\" Please send any bug reports, improvements, comments, patches,
+.\" etc. to Steve Cheng <steve@ggi-project.org>.
+.TH "SMBSPOOL" "8" "04 March 2003" "" ""
.SH NAME
smbspool \- send a print file to an SMB printer
-.SH "SYNOPSIS"
+.SH SYNOPSIS
-.nf
-\fBsmbspool\fR {job} {user} {title} {copies} {options} [filename]
-.fi
+\fBsmbspool\fR [ \fBjob\fR ] [ \fBuser\fR ] [ \fBtitle\fR ] [ \fBcopies\fR ] [ \fBoptions\fR ] [ \fBfilename\fR ]
.SH "DESCRIPTION"
-
.PP
-This tool is part of the \fBSamba\fR(7) suite\&.
-
+This tool is part of the Samba suite.
.PP
-smbspool is a very small print spooling program that sends a print file to an SMB printer\&. The command-line arguments are position-dependent for compatibility with the Common UNIX Printing System, but you can use smbspool with any printing system or from a program or script\&.
-
+smbspool is a very small print spooling program that
+sends a print file to an SMB printer. The command-line arguments
+are position-dependent for compatibility with the Common UNIX
+Printing System, but you can use smbspool with any printing system
+or from a program or script.
.PP
\fBDEVICE URI\fR
-
.PP
-smbspool specifies the destination using a Uniform Resource Identifier ("URI") with a method of "smb"\&. This string can take a number of forms:
-
-.TP 3
+smbspool specifies the destination using a Uniform Resource
+Identifier ("URI") with a method of "smb". This string can take
+a number of forms:
+.TP 0.2i
\(bu
smb://server/printer
-
-.TP
+.TP 0.2i
\(bu
smb://workgroup/server/printer
-
-.TP
+.TP 0.2i
\(bu
smb://username:password@server/printer
-
-.TP
+.TP 0.2i
\(bu
smb://username:password@workgroup/server/printer
-
-.LP
-
.PP
-smbspool tries to get the URI from argv[0]\&. If argv[0] contains the name of the program then it looks in the \fB DEVICE_URI\fR environment variable\&.
-
+smbspool tries to get the URI from argv[0]. If argv[0]
+contains the name of the program then it looks in the \fB DEVICE_URI\fR environment variable.
.PP
-Programs using the \fBexec(2)\fR functions can pass the URI in argv[0], while shell scripts must set the\fBDEVICE_URI\fR environment variable prior to running smbspool\&.
-
+Programs using the \fBexec(2)\fR functions can
+pass the URI in argv[0], while shell scripts must set the
+\fBDEVICE_URI\fR environment variable prior to
+running smbspool.
.SH "OPTIONS"
-
-.TP 3
+.TP 0.2i
\(bu
-The job argument (argv[1]) contains the job ID number and is presently not used by smbspool\&.
-
-.TP
+The job argument (argv[1]) contains the
+job ID number and is presently not used by smbspool.
+.TP 0.2i
\(bu
-The user argument (argv[2]) contains the print user's name and is presently not used by smbspool\&.
-
-.TP
+The user argument (argv[2]) contains the
+print user's name and is presently not used by smbspool.
+.TP 0.2i
\(bu
-The title argument (argv[3]) contains the job title string and is passed as the remote file name when sending the print job\&.
-
-.TP
+The title argument (argv[3]) contains the
+job title string and is passed as the remote file name
+when sending the print job.
+.TP 0.2i
\(bu
-The copies argument (argv[4]) contains the number of copies to be printed of the named file\&. If no filename is provided then this argument is not used by smbspool\&.
-
-.TP
+The copies argument (argv[4]) contains
+the number of copies to be printed of the named file. If
+no filename is provided then this argument is not used by
+smbspool.
+.TP 0.2i
\(bu
-The options argument (argv[5]) contains the print options in a single string and is currently not used by smbspool\&.
-
-.TP
+The options argument (argv[5]) contains
+the print options in a single string and is currently
+not used by smbspool.
+.TP 0.2i
\(bu
-The filename argument (argv[6]) contains the name of the file to print\&. If this argument is not specified then the print file is read from the standard input\&.
-
-.LP
-
+The filename argument (argv[6]) contains the
+name of the file to print. If this argument is not specified
+then the print file is read from the standard input.
.SH "VERSION"
-
.PP
-This man page is correct for version 3\&.0 of the Samba suite\&.
-
+This man page is correct for version 2.2 of
+the Samba suite.
.SH "SEE ALSO"
-
.PP
-\fBsmbd\fR(8) and \fBSamba\fR(7)\&.
-
+\fBsmbd(8)\fR
+and samba(7)
.SH "AUTHOR"
-
.PP
-\fBsmbspool\fR was written by Michael Sweet at Easy Software Products\&.
-
+\fBsmbspool\fR was written by Michael Sweet
+at Easy Software Products.
.PP
-The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&.
-
+The original Samba software and related utilities
+were created by Andrew Tridgell. Samba is now developed
+by the Samba Team as an Open Source project similar
+to the way the Linux kernel is developed.
.PP
-The original Samba man pages were written by Karl Auer\&. The man page sources were converted to YODL format (another excellent piece of Open Source software, available at ftp://ftp\&.icce\&.rug\&.nl/pub/unix/) and updated for the Samba 2\&.0 release by Jeremy Allison\&. The conversion to DocBook for Samba 2\&.2 was done by Gerald Carter\&. The conversion to DocBook XML 4\&.2 for Samba 3\&.0 was done by Alexander Bokovoy\&.
-
+The original Samba man pages were written by Karl Auer.
+The man page sources were converted to YODL format (another
+excellent piece of Open Source software, available at
+ftp://ftp.icce.rug.nl/pub/unix/ <URL:ftp://ftp.icce.rug.nl/pub/unix/>) and updated for the Samba 2.0
+release by Jeremy Allison. The conversion to DocBook for
+Samba 2.2 was done by Gerald Carter
diff --git a/docs/manpages/smbstatus.1 b/docs/manpages/smbstatus.1
index 7e349dcd19..9fb96f1c43 100644
--- a/docs/manpages/smbstatus.1
+++ b/docs/manpages/smbstatus.1
@@ -1,131 +1,77 @@
-.\"Generated by db2man.xsl. Don't modify this, modify the source.
-.de Sh \" Subsection
-.br
-.if t .Sp
-.ne 5
-.PP
-\fB\\$1\fR
-.PP
-..
-.de Sp \" Vertical space (when we can't use .PP)
-.if t .sp .5v
-.if n .sp
-..
-.de Ip \" List item
-.br
-.ie \\n(.$>=3 .ne \\$3
-.el .ne 3
-.IP "\\$1" \\$2
-..
-.TH "SMBSTATUS" 1 "" "" ""
+.\" This manpage has been automatically generated by docbook2man
+.\" from a DocBook document. This tool can be found at:
+.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
+.\" Please send any bug reports, improvements, comments, patches,
+.\" etc. to Steve Cheng <steve@ggi-project.org>.
+.TH "SMBSTATUS" "1" "04 March 2003" "" ""
.SH NAME
smbstatus \- report on current Samba connections
-.SH "SYNOPSIS"
+.SH SYNOPSIS
-.nf
-\fBsmbstatus\fR [-P] [-b] [-d <debug level>] [-v] [-L] [-B] [-p] [-S] [-s <configuration
- file>] [-u <username>]
-.fi
+\fBsmbstatus\fR [ \fB-P\fR ] [ \fB-b\fR ] [ \fB-d <debug level>\fR ] [ \fB-v\fR ] [ \fB-L\fR ] [ \fB-B\fR ] [ \fB-p\fR ] [ \fB-S\fR ] [ \fB-s <configuration file>\fR ] [ \fB-u <username>\fR ]
.SH "DESCRIPTION"
-
.PP
-This tool is part of the \fBSamba\fR(7) suite\&.
-
+This tool is part of the Samba suite.
.PP
-\fBsmbstatus\fR is a very simple program to list the current Samba connections\&.
-
+\fBsmbstatus\fR is a very simple program to
+list the current Samba connections.
.SH "OPTIONS"
-
-.TP
--P|--profile
-If samba has been compiled with the profiling option, print only the contents of the profiling shared memory area\&.
-
-
-.TP
--b|--brief
-gives brief output\&.
-
-
.TP
--V
-Prints the version number for \fBsmbd\fR\&.
-
-
-.TP
--s <configuration file>
-The file specified contains the configuration details required by the server\&. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is to provide\&. See \fI smb\&.conf(5)\fR for more information\&. The default configuration file name is determined at compile time\&.
-
-
+\fB-P|--profile\fR
+If samba has been compiled with the
+profiling option, print only the contents of the profiling
+shared memory area.
.TP
--d|--debug=debuglevel
-\fIdebuglevel\fR is an integer from 0 to 10\&. The default value if this parameter is not specified is zero\&.
-
-
-The higher this value, the more detail will be logged to the log files about the activities of the server\&. At level 0, only critical errors and serious warnings will be logged\&. Level 1 is a reasonable level for day to day running - it generates a small amount of information about operations carried out\&.
-
-
-Levels above 1 will generate considerable amounts of log data, and should only be used when investigating a problem\&. Levels above 3 are designed for use only by developers and generate HUGE amounts of log data, most of which is extremely cryptic\&.
-
-
-Note that specifying this parameter here will override the log level parameter in the \fIsmb\&.conf(5)\fR file\&.
-
-
+\fB-b|--brief\fR
+gives brief output.
.TP
--l|--logfile=logbasename
-File name for log/debug files\&. The extension \fB"\&.client"\fR will be appended\&. The log file is never removed by the client\&.
-
-
+\fB-d|--debug=<debuglevel>\fR
+sets debugging to specified level
.TP
--v|--verbose
-gives verbose output\&.
-
-
+\fB-v|--verbose\fR
+gives verbose output.
.TP
--L|--locks
-causes smbstatus to only list locks\&.
-
-
+\fB-L|--locks\fR
+causes smbstatus to only list locks.
.TP
--B|--byterange
-causes smbstatus to include byte range locks\&.
-
-
+\fB-B|--byterange\fR
+causes smbstatus to include byte range locks.
.TP
--p|--processes
-print a list of \fBsmbd\fR(8) processes and exit\&. Useful for scripting\&.
-
-
+\fB-p|--processes\fR
+print a list of \fBsmbd(8)\fR processes and exit.
+Useful for scripting.
.TP
--S|--shares
-causes smbstatus to only list shares\&.
-
-
+\fB-S|--shares\fR
+causes smbstatus to only list shares.
.TP
--h|--help
-Print a summary of command line options\&.
-
-
+\fB-s|--conf=<configuration file>\fR
+The default configuration file name is
+determined at compile time. The file specified contains the
+configuration details required by the server. See \fIsmb.conf(5)\fR
+ for more information.
.TP
--u|--user=<username>
-selects information relevant to \fIusername\fR only\&.
-
-
+\fB-u|--user=<username>\fR
+selects information relevant to
+\fIusername\fR only.
.SH "VERSION"
-
.PP
-This man page is correct for version 3\&.0 of the Samba suite\&.
-
+This man page is correct for version 3.0 of
+the Samba suite.
.SH "SEE ALSO"
-
.PP
-\fBsmbd\fR(8) and \fBsmb.conf\fR(5)\&.
-
+\fBsmbd(8)\fR and
+smb.conf(5)
.SH "AUTHOR"
-
.PP
-The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&.
-
+The original Samba software and related utilities
+were created by Andrew Tridgell. Samba is now developed
+by the Samba Team as an Open Source project similar
+to the way the Linux kernel is developed.
.PP
-The original Samba man pages were written by Karl Auer\&. The man page sources were converted to YODL format (another excellent piece of Open Source software, available at ftp://ftp\&.icce\&.rug\&.nl/pub/unix/) and updated for the Samba 2\&.0 release by Jeremy Allison\&. The conversion to DocBook for Samba 2\&.2 was done by Gerald Carter\&. The conversion to DocBook XML 4\&.2 for Samba 3\&.0 was done by Alexander Bokovoy\&.
-
+The original Samba man pages were written by Karl Auer.
+The man page sources were converted to YODL format (another
+excellent piece of Open Source software, available at
+ftp://ftp.icce.rug.nl/pub/unix/ <URL:ftp://ftp.icce.rug.nl/pub/unix/>) and updated for the Samba 2.0
+release by Jeremy Allison. The conversion to DocBook for
+Samba 2.2 was done by Gerald Carter
diff --git a/docs/manpages/smbtar.1 b/docs/manpages/smbtar.1
index 00d913bdfa..4ed25bbc75 100644
--- a/docs/manpages/smbtar.1
+++ b/docs/manpages/smbtar.1
@@ -1,148 +1,121 @@
-.\"Generated by db2man.xsl. Don't modify this, modify the source.
-.de Sh \" Subsection
-.br
-.if t .Sp
-.ne 5
-.PP
-\fB\\$1\fR
-.PP
-..
-.de Sp \" Vertical space (when we can't use .PP)
-.if t .sp .5v
-.if n .sp
-..
-.de Ip \" List item
-.br
-.ie \\n(.$>=3 .ne \\$3
-.el .ne 3
-.IP "\\$1" \\$2
-..
-.TH "SMBTAR" 1 "" "" ""
+.\" This manpage has been automatically generated by docbook2man
+.\" from a DocBook document. This tool can be found at:
+.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
+.\" Please send any bug reports, improvements, comments, patches,
+.\" etc. to Steve Cheng <steve@ggi-project.org>.
+.TH "SMBTAR" "1" "04 March 2003" "" ""
.SH NAME
-smbtar \- shell script for backing up SMB/CIFS shares directly to UNIX tape drives
-.SH "SYNOPSIS"
+smbtar \- shell script for backing up SMB/CIFS shares directly to UNIX tape drives
+.SH SYNOPSIS
-.nf
-\fBsmbtar\fR [-r] [-i] [-a] [-v] {-s server} [-p password] [-x services] [-X] [-N filename]
- [-b blocksize] [-d directory] [-l loglevel] [-u user] [-t tape] {filenames}
-
-.fi
+\fBsmbtar\fR \fB-s server\fR [ \fB-p password\fR ] [ \fB-x services\fR ] [ \fB-X\fR ] [ \fB-d directory\fR ] [ \fB-u user\fR ] [ \fB-t tape\fR ] [ \fB-t tape\fR ] [ \fB-b blocksize\fR ] [ \fB-N filename\fR ] [ \fB-i\fR ] [ \fB-r\fR ] [ \fB-l loglevel\fR ] [ \fB-v\fR ] \fBfilenames\fR
.SH "DESCRIPTION"
-
.PP
-This tool is part of the \fBSamba\fR(7) suite\&.
-
+This tool is part of the Samba suite.
.PP
-\fBsmbtar\fR is a very small shell script on top of \fBsmbclient\fR(1) which dumps SMB shares directly to tape\&.
-
+\fBsmbtar\fR is a very small shell script on top
+of \fBsmbclient(1)\fR
+which dumps SMB shares directly to tape.
.SH "OPTIONS"
-
.TP
--s server
-The SMB/CIFS server that the share resides upon\&.
-
-
+\fB-s server\fR
+The SMB/CIFS server that the share resides
+upon.
.TP
--x service
-The share name on the server to connect to\&. The default is "backup"\&.
-
-
+\fB-x service\fR
+The share name on the server to connect to.
+The default is "backup".
.TP
--X
-Exclude mode\&. Exclude filenames\&.\&.\&. from tar create or restore\&.
-
-
+\fB-X\fR
+Exclude mode. Exclude filenames... from tar
+create or restore.
.TP
--d directory
-Change to initial \fIdirectory \fR before restoring / backing up files\&.
-
-
-.TP
--v
-Verbose mode\&.
-
-
+\fB-d directory\fR
+Change to initial \fIdirectory
+\fR before restoring / backing up files.
.TP
--p password
-The password to use to access a share\&. Default: none
-
-
+\fB-v\fR
+Verbose mode.
.TP
--u user
-The user id to connect as\&. Default: UNIX login name\&.
-
-
+\fB-p password\fR
+The password to use to access a share.
+Default: none
.TP
--a
-Reset DOS archive bit mode to indicate file has been archived\&.
-
-
+\fB-u user\fR
+The user id to connect as. Default:
+UNIX login name.
.TP
--t tape
-Tape device\&. May be regular file or tape device\&. Default: \fI$TAPE\fR environmental variable; if not set, a file called \fItar\&.out \fR\&.
-
-
+\fB-t tape\fR
+Tape device. May be regular file or tape
+device. Default: \fI$TAPE\fR environmental
+variable; if not set, a file called \fItar.out
+\fR.
.TP
--b blocksize
-Blocking factor\&. Defaults to 20\&. See \fBtar(1)\fR for a fuller explanation\&.
-
-
+\fB-b blocksize\fR
+Blocking factor. Defaults to 20. See
+\fBtar(1)\fR for a fuller explanation.
.TP
--N filename
-Backup only files newer than filename\&. Could be used (for example) on a log file to implement incremental backups\&.
-
-
+\fB-N filename\fR
+Backup only files newer than filename. Could
+be used (for example) on a log file to implement incremental
+backups.
.TP
--i
-Incremental mode; tar files are only backed up if they have the archive bit set\&. The archive bit is reset after each file is read\&.
-
-
+\fB-i\fR
+Incremental mode; tar files are only backed
+up if they have the archive bit set. The archive bit is reset
+after each file is read.
.TP
--r
-Restore\&. Files are restored to the share from the tar file\&.
-
-
+\fB-r\fR
+Restore. Files are restored to the share
+from the tar file.
.TP
--l log level
-Log (debug) level\&. Corresponds to the \fI-d\fR flag of \fBsmbclient\fR(1)\&.
-
-
+\fB-l log level\fR
+Log (debug) level. Corresponds to the
+\fI-d\fR flag of \fBsmbclient(1)
+\fR.
.SH "ENVIRONMENT VARIABLES"
-
.PP
-The \fI$TAPE\fR variable specifies the default tape device to write to\&. May be overridden with the -t option\&.
-
+The \fI$TAPE\fR variable specifies the
+default tape device to write to. May be overridden
+with the -t option.
.SH "BUGS"
-
.PP
-The \fBsmbtar\fR script has different options from ordinary tar and from smbclient's tar command\&.
-
+The \fBsmbtar\fR script has different
+options from ordinary tar and from smbclient's tar command.
.SH "CAVEATS"
-
.PP
-Sites that are more careful about security may not like the way the script handles PC passwords\&. Backup and restore work on entire shares; should work on file lists\&. smbtar works best with GNU tar and may not work well with other versions\&.
-
+Sites that are more careful about security may not like
+the way the script handles PC passwords. Backup and restore work
+on entire shares; should work on file lists. smbtar works best
+with GNU tar and may not work well with other versions.
.SH "DIAGNOSTICS"
-
.PP
-See the \fBDIAGNOSTICS\fR section for the \fBsmbclient\fR(1) command\&.
-
+See the \fBDIAGNOSTICS\fR section for the
+\fBsmbclient(1)\fR
+ command.
.SH "VERSION"
-
.PP
-This man page is correct for version 3\&.0 of the Samba suite\&.
-
+This man page is correct for version 3.0 of
+the Samba suite.
.SH "SEE ALSO"
-
.PP
-\fBsmbd\fR(8), \fBsmbclient\fR(1), \fBsmb.conf\fR(5)\&.
-
+\fBsmbd(8)\fR
+\fBsmbclient(1)\fR
+smb.conf(5)
.SH "AUTHOR"
-
.PP
-The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&.
-
+The original Samba software and related utilities
+were created by Andrew Tridgell. Samba is now developed
+by the Samba Team as an Open Source project similar
+to the way the Linux kernel is developed.
.PP
-Ricky Poulten wrote the tar extension and this man page\&. The \fBsmbtar\fR script was heavily rewritten and improved by Martin Kraemer\&. Many thanks to everyone who suggested extensions, improvements, bug fixes, etc\&. The man page sources were converted to YODL format (another excellent piece of Open Source software, available at ftp://ftp\&.icce\&.rug\&.nl/pub/unix/) and updated for the Samba 2\&.0 release by Jeremy Allison\&. The conversion to DocBook for Samba 2\&.2 was done by Gerald Carter\&. The conversion to DocBook XML 4\&.2 for Samba 3\&.0 was done by Alexander Bokovoy\&.
-
+Ricky Poulten <URL:mailto:poultenr@logica.co.uk>
+wrote the tar extension and this man page. The \fBsmbtar\fR
+script was heavily rewritten and improved by Martin Kraemer <URL:mailto:Martin.Kraemer@mch.sni.de>. Many
+thanks to everyone who suggested extensions, improvements, bug
+fixes, etc. The man page sources were converted to YODL format (another
+excellent piece of Open Source software, available at
+ftp://ftp.icce.rug.nl/pub/unix/ <URL:ftp://ftp.icce.rug.nl/pub/unix/>) and updated for the Samba 2.0
+release by Jeremy Allison. The conversion to DocBook for
+Samba 2.2 was done by Gerald Carter.
diff --git a/docs/manpages/smbumount.8 b/docs/manpages/smbumount.8
index 922cf5db84..4c3688d63f 100644
--- a/docs/manpages/smbumount.8
+++ b/docs/manpages/smbumount.8
@@ -1,56 +1,43 @@
-.\"Generated by db2man.xsl. Don't modify this, modify the source.
-.de Sh \" Subsection
-.br
-.if t .Sp
-.ne 5
-.PP
-\fB\\$1\fR
-.PP
-..
-.de Sp \" Vertical space (when we can't use .PP)
-.if t .sp .5v
-.if n .sp
-..
-.de Ip \" List item
-.br
-.ie \\n(.$>=3 .ne \\$3
-.el .ne 3
-.IP "\\$1" \\$2
-..
-.TH "SMBUMOUNT" 8 "" "" ""
+.\" This manpage has been automatically generated by docbook2man
+.\" from a DocBook document. This tool can be found at:
+.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
+.\" Please send any bug reports, improvements, comments, patches,
+.\" etc. to Steve Cheng <steve@ggi-project.org>.
+.TH "SMBUMOUNT" "8" "04 March 2003" "" ""
.SH NAME
smbumount \- smbfs umount for normal users
-.SH "SYNOPSIS"
+.SH SYNOPSIS
-.nf
-\fBsmbumount\fR {mount-point}
-.fi
+\fBsmbumount\fR \fBmount-point\fR
.SH "DESCRIPTION"
-
.PP
-With this program, normal users can unmount smb-filesystems, provided that it is suid root\&. \fBsmbumount\fR has been written to give normal Linux users more control over their resources\&. It is safe to install this program suid root, because only the user who has mounted a filesystem is allowed to unmount it again\&. For root it is not necessary to use smbumount\&. The normal umount program works perfectly well, but it would certainly be problematic to make umount setuid root\&.
-
+With this program, normal users can unmount smb-filesystems,
+provided that it is suid root. \fBsmbumount\fR has
+been written to give normal Linux users more control over their
+resources. It is safe to install this program suid root, because only
+the user who has mounted a filesystem is allowed to unmount it again.
+For root it is not necessary to use smbumount. The normal umount
+program works perfectly well, but it would certainly be problematic
+to make umount setuid root.
.SH "OPTIONS"
-
.TP
-mount-point
-The directory to unmount\&.
-
-
+\fBmount-point\fR
+The directory to unmount.
.SH "SEE ALSO"
-
.PP
-\fBsmbmount\fR(8)
+\fBsmbmount(8)\fR
.SH "AUTHOR"
-
.PP
-Volker Lendecke, Andrew Tridgell, Michael H\&. Warfield and others\&.
-
+Volker Lendecke, Andrew Tridgell, Michael H. Warfield
+and others.
.PP
-The current maintainer of smbfs and the userspace tools \fBsmbmount\fR, \fBsmbumount\fR, and \fBsmbmnt\fR is Urban Widmark\&. The SAMBA Mailing list is the preferred place to ask questions regarding these programs\&.
-
+The current maintainer of smbfs and the userspace
+tools \fBsmbmount\fR, \fBsmbumount\fR,
+and \fBsmbmnt\fR is Urban Widmark <URL:mailto:urban@teststation.com>.
+The SAMBA Mailing list <URL:mailto:samba@samba.org>
+is the preferred place to ask questions regarding these programs.
.PP
-The conversion of this manpage for Samba 2\&.2 was performed by Gerald Carter\&. The conversion to DocBook XML 4\&.2 for Samba 3\&.0 was done by Alexander Bokovoy\&.
-
+The conversion of this manpage for Samba 2.2 was performed
+by Gerald Carter
diff --git a/docs/manpages/swat.8 b/docs/manpages/swat.8
index 36d855e725..6466a0a79d 100644
--- a/docs/manpages/swat.8
+++ b/docs/manpages/swat.8
@@ -1,184 +1,141 @@
-.\"Generated by db2man.xsl. Don't modify this, modify the source.
-.de Sh \" Subsection
-.br
-.if t .Sp
-.ne 5
-.PP
-\fB\\$1\fR
-.PP
-..
-.de Sp \" Vertical space (when we can't use .PP)
-.if t .sp .5v
-.if n .sp
-..
-.de Ip \" List item
-.br
-.ie \\n(.$>=3 .ne \\$3
-.el .ne 3
-.IP "\\$1" \\$2
-..
-.TH "SWAT" 8 "" "" ""
+.\" This manpage has been automatically generated by docbook2man
+.\" from a DocBook document. This tool can be found at:
+.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
+.\" Please send any bug reports, improvements, comments, patches,
+.\" etc. to Steve Cheng <steve@ggi-project.org>.
+.TH "SWAT" "8" "04 March 2003" "" ""
.SH NAME
swat \- Samba Web Administration Tool
-.SH "SYNOPSIS"
+.SH SYNOPSIS
-.nf
-\fBswat\fR [-s <smb config file>] [-a]
-.fi
+\fBswat\fR [ \fB-s <smb config file>\fR ] [ \fB-a\fR ]
.SH "DESCRIPTION"
-
.PP
-This tool is part of the \fBSamba\fR(7) suite\&.
-
+This tool is part of the Samba suite.
.PP
-\fBswat\fR allows a Samba administrator to configure the complex \fBsmb.conf\fR(5) file via a Web browser\&. In addition, a \fBswat\fR configuration page has help links to all the configurable options in the \fIsmb\&.conf\fR file allowing an administrator to easily look up the effects of any change\&.
-
+\fBswat\fR allows a Samba administrator to
+configure the complex \fI smb.conf(5)\fR file via a Web browser. In addition,
+a \fBswat\fR configuration page has help links
+to all the configurable options in the \fIsmb.conf\fR file allowing an
+administrator to easily look up the effects of any change.
.PP
\fBswat\fR is run from \fBinetd\fR
-
.SH "OPTIONS"
-
-.TP
--s smb configuration file
-The default configuration file path is determined at compile time\&. The file specified contains the configuration details required by the \fBsmbd\fR(8) server\&. This is the file that \fBswat\fR will modify\&. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is to provide\&. See \fIsmb\&.conf\fR for more information\&.
-
-
-.TP
--a
-This option disables authentication and puts \fBswat\fR in demo mode\&. In that mode anyone will be able to modify the \fIsmb\&.conf\fR file\&.
-
-
-\fBWARNING: Do NOT enable this option on a production server\&. \fR
-
-
.TP
--V
-Prints the version number for \fBsmbd\fR\&.
-
-
-.TP
--s <configuration file>
-The file specified contains the configuration details required by the server\&. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is to provide\&. See \fI smb\&.conf(5)\fR for more information\&. The default configuration file name is determined at compile time\&.
-
-
+\fB-s smb configuration file\fR
+The default configuration file path is
+determined at compile time. The file specified contains
+the configuration details required by the \fBsmbd
+\fR server. This is the file that \fBswat\fR will modify.
+The information in this file includes server-specific
+information such as what printcap file to use, as well as
+descriptions of all the services that the server is to provide.
+See \fIsmb.conf\fR for more information.
.TP
--d|--debug=debuglevel
-\fIdebuglevel\fR is an integer from 0 to 10\&. The default value if this parameter is not specified is zero\&.
-
-
-The higher this value, the more detail will be logged to the log files about the activities of the server\&. At level 0, only critical errors and serious warnings will be logged\&. Level 1 is a reasonable level for day to day running - it generates a small amount of information about operations carried out\&.
-
-
-Levels above 1 will generate considerable amounts of log data, and should only be used when investigating a problem\&. Levels above 3 are designed for use only by developers and generate HUGE amounts of log data, most of which is extremely cryptic\&.
-
-
-Note that specifying this parameter here will override the log level parameter in the \fIsmb\&.conf(5)\fR file\&.
-
-
-.TP
--l|--logfile=logbasename
-File name for log/debug files\&. The extension \fB"\&.client"\fR will be appended\&. The log file is never removed by the client\&.
-
-
-.TP
--h|--help
-Print a summary of command line options\&.
-
+\fB-a\fR
+This option disables authentication and puts
+\fBswat\fR in demo mode. In that mode anyone will be able to modify
+the \fIsmb.conf\fR file.
+\fBWARNING: Do NOT enable this option on a production
+server. \fR
.SH "INSTALLATION"
-
-.PP
-Swat is included as binary package with most distributions\&. The package manager in this case takes care of the installation and configuration\&. This section is only for those who have compiled swat from scratch\&.
-
.PP
-After you compile SWAT you need to run \fBmake install \fR to install the \fBswat\fR binary and the various help files and images\&. A default install would put these in:
-
-.TP 3
+After you compile SWAT you need to run \fBmake install
+\fR to install the \fBswat\fR binary
+and the various help files and images. A default install would put
+these in:
+.TP 0.2i
\(bu
/usr/local/samba/bin/swat
-
-.TP
+.TP 0.2i
\(bu
/usr/local/samba/swat/images/*
-
-.TP
+.TP 0.2i
\(bu
/usr/local/samba/swat/help/*
-
-.LP
-
-.SS "Inetd Installation"
-
+.SS "INETD INSTALLATION"
.PP
-You need to edit your \fI/etc/inetd\&.conf \fR and \fI/etc/services\fR to enable SWAT to be launched via \fBinetd\fR\&.
-
+You need to edit your \fI/etc/inetd.conf
+\fR and \fI/etc/services\fR
+to enable SWAT to be launched via \fBinetd\fR.
.PP
-In \fI/etc/services\fR you need to add a line like this:
-
+In \fI/etc/services\fR you need to
+add a line like this:
.PP
-\fBswat 901/tcp\fR
-
+\fBswat 901/tcp\fR
.PP
-Note for NIS/YP and LDAP users - you may need to rebuild the NIS service maps rather than alter your local \fI /etc/services\fR file\&.
-
+Note for NIS/YP users - you may need to rebuild the
+NIS service maps rather than alter your local \fI /etc/services\fR file.
.PP
-the choice of port number isn't really important except that it should be less than 1024 and not currently used (using a number above 1024 presents an obscure security hole depending on the implementation details of your\fBinetd\fR daemon)\&.
-
+the choice of port number isn't really important
+except that it should be less than 1024 and not currently
+used (using a number above 1024 presents an obscure security
+hole depending on the implementation details of your
+\fBinetd\fR daemon).
.PP
-In \fI/etc/inetd\&.conf\fR you should add a line like this:
-
+In \fI/etc/inetd.conf\fR you should
+add a line like this:
.PP
-\fBswat stream tcp nowait.400 root /usr/local/samba/bin/swat swat\fR
-
+\fBswat stream tcp nowait.400 root
+/usr/local/samba/bin/swat swat\fR
.PP
-One you have edited \fI/etc/services\fR and \fI/etc/inetd\&.conf\fR you need to send a HUP signal to inetd\&. To do this use \fBkill -1 PID \fR where PID is the process ID of the inetd daemon\&.
-
-.SH "LAUNCHING"
-
+One you have edited \fI/etc/services\fR
+and \fI/etc/inetd.conf\fR you need to send a
+HUP signal to inetd. To do this use \fBkill -1 PID
+\fR where PID is the process ID of the inetd daemon.
+.SS "LAUNCHING"
.PP
-To launch SWAT just run your favorite web browser and point it at "http://localhost:901/"\&.
-
+To launch SWAT just run your favorite web browser and
+point it at "http://localhost:901/".
.PP
-Note that you can attach to SWAT from any IP connected machine but connecting from a remote machine leaves your connection open to password sniffing as passwords will be sent in the clear over the wire\&.
-
+Note that you can attach to SWAT from any IP connected
+machine but connecting from a remote machine leaves your
+connection open to password sniffing as passwords will be sent
+in the clear over the wire.
.SH "FILES"
-
.TP
-\fI/etc/inetd\&.conf\fR
-This file must contain suitable startup information for the meta-daemon\&.
-
-
+\fB\fI/etc/inetd.conf\fB\fR
+This file must contain suitable startup
+information for the meta-daemon.
.TP
-\fI/etc/services\fR
-This file must contain a mapping of service name (e\&.g\&., swat) to service port (e\&.g\&., 901) and protocol type (e\&.g\&., tcp)\&.
-
-
+\fB\fI/etc/services\fB\fR
+This file must contain a mapping of service name
+(e.g., swat) to service port (e.g., 901) and protocol type
+(e.g., tcp).
.TP
-\fI/usr/local/samba/lib/smb\&.conf\fR
-This is the default location of the \fBsmb.conf\fR(5) server configuration file that swat edits\&. Other common places that systems install this file are \fI /usr/samba/lib/smb\&.conf\fR and \fI/etc/smb\&.conf \fR\&. This file describes all the services the server is to make available to clients\&.
-
-
+\fB\fI/usr/local/samba/lib/smb.conf\fB\fR
+This is the default location of the \fIsmb.conf(5)
+\fR server configuration file that swat edits. Other
+common places that systems install this file are \fI /usr/samba/lib/smb.conf\fR and \fI/etc/smb.conf
+\fR. This file describes all the services the server
+is to make available to clients.
.SH "WARNINGS"
-
.PP
-\fBswat\fR will rewrite your \fBsmb.conf\fR(5) file\&. It will rearrange the entries and delete all comments, \fIinclude=\fR and \fIcopy= \fR options\&. If you have a carefully crafted \fI smb\&.conf\fR then back it up or don't use swat!
-
+\fBswat\fR will rewrite your \fIsmb.conf
+\fR file. It will rearrange the entries and delete all
+comments, \fIinclude=\fR and \fIcopy=
+\fR options. If you have a carefully crafted \fI smb.conf\fR then back it up or don't use swat!
.SH "VERSION"
-
.PP
-This man page is correct for version 3\&.0 of the Samba suite\&.
-
+This man page is correct for version 2.2 of
+the Samba suite.
.SH "SEE ALSO"
-
.PP
-\fBinetd(5)\fR, \fBsmbd\fR(8), \fBsmb.conf\fR(5)
-
+\fBinetd(5)\fR,
+\fBsmbd(8)\fR
+smb.conf(5)
.SH "AUTHOR"
-
-.PP
-The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&.
-
.PP
-The original Samba man pages were written by Karl Auer\&. The man page sources were converted to YODL format (another excellent piece of Open Source software, available at ftp://ftp\&.icce\&.rug\&.nl/pub/unix/) and updated for the Samba 2\&.0 release by Jeremy Allison\&. The conversion to DocBook for Samba 2\&.2 was done by Gerald Carter\&. The conversion to DocBook XML 4\&.2 for Samba 3\&.0 was done by Alexander Bokovoy\&.
-
+The original Samba software and related utilities
+were created by Andrew Tridgell. Samba is now developed
+by the Samba Team as an Open Source project similar
+to the way the Linux kernel is developed.
+.PP
+The original Samba man pages were written by Karl Auer.
+The man page sources were converted to YODL format (another
+excellent piece of Open Source software, available at
+ftp://ftp.icce.rug.nl/pub/unix/ <URL:ftp://ftp.icce.rug.nl/pub/unix/>) and updated for the Samba 2.0
+release by Jeremy Allison. The conversion to DocBook for
+Samba 2.2 was done by Gerald Carter
diff --git a/docs/manpages/testparm.1 b/docs/manpages/testparm.1
index 4a6d788f79..c459eeea70 100644
--- a/docs/manpages/testparm.1
+++ b/docs/manpages/testparm.1
@@ -1,123 +1,110 @@
-.\"Generated by db2man.xsl. Don't modify this, modify the source.
-.de Sh \" Subsection
-.br
-.if t .Sp
-.ne 5
-.PP
-\fB\\$1\fR
-.PP
-..
-.de Sp \" Vertical space (when we can't use .PP)
-.if t .sp .5v
-.if n .sp
-..
-.de Ip \" List item
-.br
-.ie \\n(.$>=3 .ne \\$3
-.el .ne 3
-.IP "\\$1" \\$2
-..
-.TH "TESTPARM" 1 "" "" ""
+.\" This manpage has been automatically generated by docbook2man
+.\" from a DocBook document. This tool can be found at:
+.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
+.\" Please send any bug reports, improvements, comments, patches,
+.\" etc. to Steve Cheng <steve@ggi-project.org>.
+.TH "TESTPARM" "1" "04 March 2003" "" ""
.SH NAME
-testparm \- check an smb.conf configuration file for internal correctness
-.SH "SYNOPSIS"
+testparm \- check an smb.conf configuration file for internal correctness
+.SH SYNOPSIS
-.nf
-\fBtestparm\fR [-s] [-h] [-v] [-L <servername>] [-t <encoding>] {config filename} [hostname
- hostIP]
-.fi
+\fBtestparm\fR [ \fB-s\fR ] [ \fB-h\fR ] [ \fB-v\fR ] [ \fB-L <servername>\fR ] [ \fB-t <encoding>\fR ] \fBconfig filename\fR [ \fBhostname hostIP\fR ]
.SH "DESCRIPTION"
-
.PP
-This tool is part of the \fBSamba\fR(7) suite\&.
-
+This tool is part of the Samba suite.
.PP
-\fBtestparm\fR is a very simple test program to check an \fBsmbd\fR(8) configuration file for internal correctness\&. If this program reports no problems, you can use the configuration file with confidence that \fBsmbd \fR will successfully load the configuration file\&.
-
+\fBtestparm\fR is a very simple test program
+to check an \fBsmbd\fR configuration file for
+internal correctness. If this program reports no problems, you
+can use the configuration file with confidence that \fBsmbd
+\fR will successfully load the configuration file.
.PP
-Note that this is \fBNOT\fR a guarantee that the services specified in the configuration file will be available or will operate as expected\&.
-
+Note that this is \fBNOT\fR a guarantee that
+the services specified in the configuration file will be
+available or will operate as expected.
.PP
-If the optional host name and host IP address are specified on the command line, this test program will run through the service entries reporting whether the specified host has access to each service\&.
-
+If the optional host name and host IP address are
+specified on the command line, this test program will run through
+the service entries reporting whether the specified host
+has access to each service.
.PP
-If \fBtestparm\fR finds an error in the \fI smb\&.conf\fR file it returns an exit code of 1 to the calling program, else it returns an exit code of 0\&. This allows shell scripts to test the output from \fBtestparm\fR\&.
-
+If \fBtestparm\fR finds an error in the \fI smb.conf\fR file it returns an exit code of 1 to the calling
+program, else it returns an exit code of 0. This allows shell scripts
+to test the output from \fBtestparm\fR.
.SH "OPTIONS"
-
-.TP
--s
-Without this option, \fBtestparm\fR will prompt for a carriage return after printing the service names and before dumping the service definitions\&.
-
-
.TP
--h|--help
-Print a summary of command line options\&.
-
-
+\fB-s\fR
+Without this option, \fBtestparm\fR
+will prompt for a carriage return after printing the service
+names and before dumping the service definitions.
.TP
--V
-Prints the version number for \fBsmbd\fR\&.
-
-
+\fB-h\fR
+Print usage message
.TP
--L servername
-Sets the value of the %L macro to \fIservername\fR\&. This is useful for testing include files specified with the %L macro\&.
-
-
+\fB-L servername\fR
+Sets the value of the %L macro to \fIservername\fR.
+This is useful for testing include files specified with the
+%L macro.
.TP
--v
-If this option is specified, testparm will also output all options that were not used in \fBsmb.conf\fR(5) and are thus set to their defaults\&.
-
-
+\fB-v\fR
+If this option is specified, testparm
+will also output all options that were not used in
+\fIsmb.conf\fR and are thus set to
+their defaults.
.TP
--t encoding
-Output data in specified encoding\&.
-
-
+\fB-t encoding\fR
+Output data in specified encoding.
.TP
-configfilename
-This is the name of the configuration file to check\&. If this parameter is not present then the default \fBsmb.conf\fR(5) file will be checked\&.
-
-
+\fBconfigfilename\fR
+This is the name of the configuration file
+to check. If this parameter is not present then the
+default \fIsmb.conf\fR file will be checked.
.TP
-hostname
-If this parameter and the following are specified, then \fBtestparm\fR will examine the \fIhosts allow\fR and \fIhosts deny\fR parameters in the \fBsmb.conf\fR(5) file to determine if the hostname with this IP address would be allowed access to the \fBsmbd\fR server\&. If this parameter is supplied, the hostIP parameter must also be supplied\&.
-
-
+\fBhostname\fR
+If this parameter and the following are
+specified, then \fBtestparm\fR will examine the \fIhosts
+allow\fR and \fIhosts deny\fR
+parameters in the \fIsmb.conf\fR file to
+determine if the hostname with this IP address would be
+allowed access to the \fBsmbd\fR server. If
+this parameter is supplied, the hostIP parameter must also
+be supplied.
.TP
-hostIP
-This is the IP address of the host specified in the previous parameter\&. This address must be supplied if the hostname parameter is supplied\&.
-
-
+\fBhostIP\fR
+This is the IP address of the host specified
+in the previous parameter. This address must be supplied
+if the hostname parameter is supplied.
.SH "FILES"
-
.TP
-\fBsmb.conf\fR(5)
-This is usually the name of the configuration file used by \fBsmbd\fR(8)\&.
-
-
+\fB\fIsmb.conf\fB\fR
+This is usually the name of the configuration
+file used by \fBsmbd\fR.
.SH "DIAGNOSTICS"
-
.PP
-The program will issue a message saying whether the configuration file loaded OK or not\&. This message may be preceded by errors and warnings if the file did not load\&. If the file was loaded OK, the program then dumps all known service details to stdout\&.
-
+The program will issue a message saying whether the
+configuration file loaded OK or not. This message may be preceded by
+errors and warnings if the file did not load. If the file was
+loaded OK, the program then dumps all known service details
+to stdout.
.SH "VERSION"
-
.PP
-This man page is correct for version 3\&.0 of the Samba suite\&.
-
+This man page is correct for version 3.0 of
+the Samba suite.
.SH "SEE ALSO"
-
.PP
-\fBsmb.conf\fR(5), \fBsmbd\fR(8)
-
+\fIsmb.conf(5)\fR
+\fBsmbd(8)\fR
.SH "AUTHOR"
-
.PP
-The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&.
-
+The original Samba software and related utilities
+were created by Andrew Tridgell. Samba is now developed
+by the Samba Team as an Open Source project similar
+to the way the Linux kernel is developed.
.PP
-The original Samba man pages were written by Karl Auer\&. The man page sources were converted to YODL format (another excellent piece of Open Source software, available at ftp://ftp\&.icce\&.rug\&.nl/pub/unix/) and updated for the Samba 2\&.0 release by Jeremy Allison\&. The conversion to DocBook for Samba 2\&.2 was done by Gerald Carter\&. The conversion to DocBook XML 4\&.2 for Samba 3\&.0 was done by Alexander Bokovoy\&.
-
+The original Samba man pages were written by Karl Auer.
+The man page sources were converted to YODL format (another
+excellent piece of Open Source software, available at
+ftp://ftp.icce.rug.nl/pub/unix/ <URL:ftp://ftp.icce.rug.nl/pub/unix/>) and updated for the Samba 2.0
+release by Jeremy Allison. The conversion to DocBook for
+Samba 2.2 was done by Gerald Carter
diff --git a/docs/manpages/testprns.1 b/docs/manpages/testprns.1
index 9f98ea1d59..f70b383f9d 100644
--- a/docs/manpages/testprns.1
+++ b/docs/manpages/testprns.1
@@ -1,96 +1,91 @@
-.\"Generated by db2man.xsl. Don't modify this, modify the source.
-.de Sh \" Subsection
-.br
-.if t .Sp
-.ne 5
-.PP
-\fB\\$1\fR
-.PP
-..
-.de Sp \" Vertical space (when we can't use .PP)
-.if t .sp .5v
-.if n .sp
-..
-.de Ip \" List item
-.br
-.ie \\n(.$>=3 .ne \\$3
-.el .ne 3
-.IP "\\$1" \\$2
-..
-.TH "TESTPRNS" 1 "" "" ""
+.\" This manpage has been automatically generated by docbook2man
+.\" from a DocBook document. This tool can be found at:
+.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
+.\" Please send any bug reports, improvements, comments, patches,
+.\" etc. to Steve Cheng <steve@ggi-project.org>.
+.TH "TESTPRNS" "1" "04 March 2003" "" ""
.SH NAME
testprns \- check printer name for validity with smbd
-.SH "SYNOPSIS"
+.SH SYNOPSIS
-.nf
-\fBtestprns\fR {printername} [printcapname]
-.fi
+\fBtestprns\fR \fBprintername\fR [ \fBprintcapname\fR ]
.SH "DESCRIPTION"
-
.PP
-This tool is part of the \fBSamba\fR(7) suite\&.
-
+This tool is part of the Samba suite.
.PP
-\fBtestprns\fR is a very simple test program to determine whether a given printer name is valid for use in a service to be provided by \fBsmbd\fR(8)\&.
-
+\fBtestprns\fR is a very simple test program
+to determine whether a given printer name is valid for use in
+a service to be provided by \fB smbd(8)\fR
.PP
-"Valid" in this context means "can be found in the printcap specified"\&. This program is very stupid - so stupid in fact that it would be wisest to always specify the printcap file to use\&.
-
+"Valid" in this context means "can be found in the
+printcap specified". This program is very stupid - so stupid in
+fact that it would be wisest to always specify the printcap file
+to use.
.SH "OPTIONS"
-
.TP
-printername
-The printer name to validate\&.
-
-
-Printer names are taken from the first field in each record in the printcap file, single printer names and sets of aliases separated by vertical bars ("|") are recognized\&. Note that no validation or checking of the printcap syntax is done beyond that required to extract the printer name\&. It may be that the print spooling system is more forgiving or less forgiving than \fBtestprns\fR\&. However, if \fBtestprns\fR finds the printer then \fBsmbd\fR(8) should do so as well\&.
-
-
+\fBprintername\fR
+The printer name to validate.
+
+Printer names are taken from the first field in each
+record in the printcap file, single printer names and sets
+of aliases separated by vertical bars ("|") are recognized.
+Note that no validation or checking of the printcap syntax is
+done beyond that required to extract the printer name. It may
+be that the print spooling system is more forgiving or less
+forgiving than \fBtestprns\fR. However, if
+\fBtestprns\fR finds the printer then
+\fBsmbd\fR should do so as well.
.TP
-printcapname
-This is the name of the printcap file within which to search for the given printer name\&.
-
-
-If no printcap name is specified \fBtestprns \fR will attempt to scan the printcap file name specified at compile time\&.
-
+\fBprintcapname\fR
+This is the name of the printcap file within
+which to search for the given printer name.
+If no printcap name is specified \fBtestprns
+\fR will attempt to scan the printcap file name
+specified at compile time.
.SH "FILES"
-
.TP
-\fI/etc/printcap\fR
-This is usually the default printcap file to scan\&. See \fIprintcap (5)\fR\&.
-
-
+\fB\fI/etc/printcap\fB\fR
+This is usually the default printcap
+file to scan. See \fIprintcap (5)\fR.
.SH "DIAGNOSTICS"
-
.PP
-If a printer is found to be valid, the message "Printer name <printername> is valid" will be displayed\&.
-
+If a printer is found to be valid, the message
+"Printer name <printername> is valid" will be
+displayed.
.PP
-If a printer is found to be invalid, the message "Printer name <printername> is not valid" will be displayed\&.
-
+If a printer is found to be invalid, the message
+"Printer name <printername> is not valid" will be
+displayed.
.PP
-All messages that would normally be logged during operation of the Samba daemons are logged by this program to the file \fItest\&.log\fR in the current directory\&. The program runs at debuglevel 3, so quite extensive logging information is written\&. The log should be checked carefully for errors and warnings\&.
-
+All messages that would normally be logged during
+operation of the Samba daemons are logged by this program to the
+file \fItest.log\fR in the current directory. The
+program runs at debuglevel 3, so quite extensive logging
+information is written. The log should be checked carefully
+for errors and warnings.
.PP
-Other messages are self-explanatory\&.
-
+Other messages are self-explanatory.
.SH "VERSION"
-
.PP
-This man page is correct for version 3\&.0 of the Samba suite\&.
-
+This man page is correct for version 2.2 of
+the Samba suite.
.SH "SEE ALSO"
-
.PP
-\fIprintcap(5)\fR,\fBsmbd\fR(8), \fBsmbclient\fR(1)
-
+\fIprintcap(5)\fR,
+\fBsmbd(8)\fR
+\fBsmbclient(1)\fR
.SH "AUTHOR"
-
.PP
-The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&.
-
+The original Samba software and related utilities
+were created by Andrew Tridgell. Samba is now developed
+by the Samba Team as an Open Source project similar
+to the way the Linux kernel is developed.
.PP
-The original Samba man pages were written by Karl Auer\&. The man page sources were converted to YODL format (another excellent piece of Open Source software, available at ftp://ftp\&.icce\&.rug\&.nl/pub/unix/) and updated for the Samba 2\&.0 release by Jeremy Allison\&. The conversion to DocBook for Samba 2\&.2 was done by Gerald Carter\&. The conversion to DocBook XML 4\&.2 for Samba 3\&.0 was done by Alexander Bokovoy\&.
-
+The original Samba man pages were written by Karl Auer.
+The man page sources were converted to YODL format (another
+excellent piece of Open Source software, available at
+ftp://ftp.icce.rug.nl/pub/unix/ <URL:ftp://ftp.icce.rug.nl/pub/unix/>) and updated for the Samba 2.0
+release by Jeremy Allison. The conversion to DocBook for
+Samba 2.2 was done by Gerald Carter
diff --git a/docs/manpages/vfstest.1 b/docs/manpages/vfstest.1
index a6d01fba57..9877e2e461 100644
--- a/docs/manpages/vfstest.1
+++ b/docs/manpages/vfstest.1
@@ -1,271 +1,195 @@
-.\"Generated by db2man.xsl. Don't modify this, modify the source.
-.de Sh \" Subsection
-.br
-.if t .Sp
-.ne 5
-.PP
-\fB\\$1\fR
-.PP
-..
-.de Sp \" Vertical space (when we can't use .PP)
-.if t .sp .5v
-.if n .sp
-..
-.de Ip \" List item
-.br
-.ie \\n(.$>=3 .ne \\$3
-.el .ne 3
-.IP "\\$1" \\$2
-..
-.TH "VFSTEST" 1 "" "" ""
+.\" This manpage has been automatically generated by docbook2man
+.\" from a DocBook document. This tool can be found at:
+.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
+.\" Please send any bug reports, improvements, comments, patches,
+.\" etc. to Steve Cheng <steve@ggi-project.org>.
+.TH "VFSTEST" "1" "04 March 2003" "" ""
.SH NAME
vfstest \- tool for testing samba VFS modules
-.SH "SYNOPSIS"
+.SH SYNOPSIS
-.nf
-\fBvfstest\fR [-d debuglevel] [-c command] [-l logfile] [-h]
-.fi
+\fBvfstest\fR [ \fB-d debuglevel\fR ] [ \fB-c command\fR ] [ \fB-l logfile\fR ] [ \fB-h\fR ]
.SH "DESCRIPTION"
-
.PP
-This tool is part of the \fBSamba\fR(7) suite\&.
-
+This tool is part of the Samba suite.
.PP
-\fBvfstest\fR is a small command line utility that has the ability to test dso samba VFS modules\&. It gives the user the ability to call the various VFS functions manually and supports cascaded VFS modules\&.
-
+\fBvfstest\fR is a small command line
+utility that has the ability to test dso samba VFS modules. It gives the
+user the ability to call the various VFS functions manually and
+supports cascaded VFS modules.
.SH "OPTIONS"
-
-.TP
--c|--command=command
-Execute the specified (colon-separated) commands\&. See below for the commands that are available\&.
-
-
-.TP
--h|--help
-Print a summary of command line options\&.
-
-
.TP
--l|--logfile=logbasename
-File name for log/debug files\&. The extension \fB'\&.client'\fR will be appended\&. The log file is never removed by the client\&.
-
-
-.TP
--V
-Prints the version number for \fBsmbd\fR\&.
-
-
-.TP
--s <configuration file>
-The file specified contains the configuration details required by the server\&. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is to provide\&. See \fI smb\&.conf(5)\fR for more information\&. The default configuration file name is determined at compile time\&.
-
-
-.TP
--d|--debug=debuglevel
-\fIdebuglevel\fR is an integer from 0 to 10\&. The default value if this parameter is not specified is zero\&.
-
-
-The higher this value, the more detail will be logged to the log files about the activities of the server\&. At level 0, only critical errors and serious warnings will be logged\&. Level 1 is a reasonable level for day to day running - it generates a small amount of information about operations carried out\&.
-
-
-Levels above 1 will generate considerable amounts of log data, and should only be used when investigating a problem\&. Levels above 3 are designed for use only by developers and generate HUGE amounts of log data, most of which is extremely cryptic\&.
-
-
-Note that specifying this parameter here will override the log level parameter in the \fIsmb\&.conf(5)\fR file\&.
-
-
-.TP
--l|--logfile=logbasename
-File name for log/debug files\&. The extension \fB"\&.client"\fR will be appended\&. The log file is never removed by the client\&.
-
-
+\fB-c|--command=command\fR
+Execute the specified (colon-separated) commands.
+See below for the commands that are available.
+.TP
+\fB-d|--debug=debuglevel\fR
+\fIdebuglevel\fR is an integer
+from 0 to 10. The default value if this parameter is
+not specified is zero.
+
+The higher this value, the more detail will be
+logged to the log files about the activities of the
+server. At level 0, only critical errors and serious
+warnings will be logged. Level 1 is a reasonable level for
+day to day running - it generates a small amount of
+information about operations carried out.
+
+Levels above 1 will generate considerable
+amounts of log data, and should only be used when
+investigating a problem. Levels above 3 are designed for
+use only by developers and generate HUGE amounts of log
+data, most of which is extremely cryptic.
+
+Note that specifying this parameter here will
+override the log
+level file.
+.TP
+\fB-h|--help\fR
+Print a summary of command line options.
+.TP
+\fB-l|--logfile=logbasename\fR
+File name for log/debug files. The extension
+\&'.client' will be appended. The log file is never removed
+by the client.
.SH "COMMANDS"
-
.PP
\fBVFS COMMANDS\fR
-
-.TP 3
+.TP 0.2i
\(bu
-\fBload <module.so>\fR - Load specified VFS module
-
-.TP
+\fBload <module.so>\fR - Load specified VFS module
+.TP 0.2i
\(bu
\fBpopulate <char> <size>\fR - Populate a data buffer with the specified data
-
-.TP
+.TP 0.2i
\(bu
\fBshowdata [<offset> <len>]\fR - Show data currently in data buffer
-
-.TP
+.TP 0.2i
\(bu
\fBconnect\fR - VFS connect()
-
-.TP
+.TP 0.2i
\(bu
\fBdisconnect\fR - VFS disconnect()
-
-.TP
+.TP 0.2i
\(bu
\fBdisk_free\fR - VFS disk_free()
-
-.TP
+.TP 0.2i
\(bu
\fBopendir\fR - VFS opendir()
-
-.TP
+.TP 0.2i
\(bu
\fBreaddir\fR - VFS readdir()
-
-.TP
+.TP 0.2i
\(bu
\fBmkdir\fR - VFS mkdir()
-
-.TP
+.TP 0.2i
\(bu
\fBrmdir\fR - VFS rmdir()
-
-.TP
+.TP 0.2i
\(bu
\fBclosedir\fR - VFS closedir()
-
-.TP
+.TP 0.2i
\(bu
\fBopen\fR - VFS open()
-
-.TP
+.TP 0.2i
\(bu
\fBclose\fR - VFS close()
-
-.TP
+.TP 0.2i
\(bu
\fBread\fR - VFS read()
-
-.TP
+.TP 0.2i
\(bu
\fBwrite\fR - VFS write()
-
-.TP
+.TP 0.2i
\(bu
\fBlseek\fR - VFS lseek()
-
-.TP
+.TP 0.2i
\(bu
\fBrename\fR - VFS rename()
-
-.TP
+.TP 0.2i
\(bu
\fBfsync\fR - VFS fsync()
-
-.TP
+.TP 0.2i
\(bu
\fBstat\fR - VFS stat()
-
-.TP
+.TP 0.2i
\(bu
\fBfstat\fR - VFS fstat()
-
-.TP
+.TP 0.2i
\(bu
\fBlstat\fR - VFS lstat()
-
-.TP
+.TP 0.2i
\(bu
\fBunlink\fR - VFS unlink()
-
-.TP
+.TP 0.2i
\(bu
\fBchmod\fR - VFS chmod()
-
-.TP
+.TP 0.2i
\(bu
\fBfchmod\fR - VFS fchmod()
-
-.TP
+.TP 0.2i
\(bu
\fBchown\fR - VFS chown()
-
-.TP
+.TP 0.2i
\(bu
\fBfchown\fR - VFS fchown()
-
-.TP
+.TP 0.2i
\(bu
\fBchdir\fR - VFS chdir()
-
-.TP
+.TP 0.2i
\(bu
\fBgetwd\fR - VFS getwd()
-
-.TP
+.TP 0.2i
\(bu
\fButime\fR - VFS utime()
-
-.TP
+.TP 0.2i
\(bu
\fBftruncate\fR - VFS ftruncate()
-
-.TP
+.TP 0.2i
\(bu
\fBlock\fR - VFS lock()
-
-.TP
+.TP 0.2i
\(bu
\fBsymlink\fR - VFS symlink()
-
-.TP
+.TP 0.2i
\(bu
\fBreadlink\fR - VFS readlink()
-
-.TP
+.TP 0.2i
\(bu
\fBlink\fR - VFS link()
-
-.TP
+.TP 0.2i
\(bu
\fBmknod\fR - VFS mknod()
-
-.TP
+.TP 0.2i
\(bu
\fBrealpath\fR - VFS realpath()
-
-.LP
-
.PP
\fBGENERAL COMMANDS\fR
-
-.TP 3
+.TP 0.2i
\(bu
\fBconf <smb.conf>\fR - Load a different configuration file
-
-.TP
+.TP 0.2i
\(bu
\fBhelp [<command>]\fR - Get list of commands or info about specified command
-
-.TP
+.TP 0.2i
\(bu
\fBdebuglevel <level>\fR - Set debug level
-
-.TP
+.TP 0.2i
\(bu
\fBfreemem\fR - Free memory currently in use
-
-.TP
+.TP 0.2i
\(bu
\fBexit\fR - Exit vfstest
-
-.LP
-
.SH "VERSION"
-
.PP
-This man page is correct for version 3\&.0 of the Samba suite\&.
-
+This man page is correct for version 3.0 of the Samba
+suite.
.SH "AUTHOR"
-
.PP
-The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&.
-
+The original Samba software and related utilities
+were created by Andrew Tridgell. Samba is now developed
+by the Samba Team as an Open Source project similar
+to the way the Linux kernel is developed.
.PP
-The vfstest man page was written by Jelmer Vernooij\&.
-
+The vfstest man page was written by Jelmer Vernooij.
diff --git a/docs/manpages/wbinfo.1 b/docs/manpages/wbinfo.1
index 0481489078..3cc35e494d 100644
--- a/docs/manpages/wbinfo.1
+++ b/docs/manpages/wbinfo.1
@@ -1,169 +1,139 @@
-.\"Generated by db2man.xsl. Don't modify this, modify the source.
-.de Sh \" Subsection
-.br
-.if t .Sp
-.ne 5
-.PP
-\fB\\$1\fR
-.PP
-..
-.de Sp \" Vertical space (when we can't use .PP)
-.if t .sp .5v
-.if n .sp
-..
-.de Ip \" List item
-.br
-.ie \\n(.$>=3 .ne \\$3
-.el .ne 3
-.IP "\\$1" \\$2
-..
-.TH "WBINFO" 1 "" "" ""
+.\" This manpage has been automatically generated by docbook2man
+.\" from a DocBook document. This tool can be found at:
+.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
+.\" Please send any bug reports, improvements, comments, patches,
+.\" etc. to Steve Cheng <steve@ggi-project.org>.
+.TH "WBINFO" "1" "04 March 2003" "" ""
.SH NAME
wbinfo \- Query information from winbind daemon
-.SH "SYNOPSIS"
+.SH SYNOPSIS
-.nf
-\fBwbinfo\fR [-u] [-g] [-N netbios-name] [-I ip] [-n name] [-s sid] [-U uid] [-G gid]
- [-S sid] [-Y sid] [-t] [-m] [--sequence] [-r user] [-a user%password]
- [-A user%password] [--get-auth-user] [-p]
-.fi
+\fBwbinfo\fR [ \fB-u\fR ] [ \fB-g\fR ] [ \fB-i ip\fR ] [ \fB-N netbios-name\fR ] [ \fB-n name\fR ] [ \fB-s sid\fR ] [ \fB-U uid\fR ] [ \fB-G gid\fR ] [ \fB-S sid\fR ] [ \fB-Y sid\fR ] [ \fB-t\fR ] [ \fB-m\fR ] [ \fB-r user\fR ] [ \fB-a user%password\fR ] [ \fB-A user%password\fR ] [ \fB-p\fR ]
.SH "DESCRIPTION"
-
.PP
-This tool is part of the \fBSamba\fR(7) suite\&.
-
+This tool is part of the Samba suite.
.PP
-The \fBwbinfo\fR program queries and returns information created and used by the \fBwinbindd\fR(8) daemon\&.
-
+The \fBwbinfo\fR program queries and returns information
+created and used by the \fB winbindd(8)\fR daemon.
.PP
-The \fBwinbindd\fR(8) daemon must be configured and running for the \fBwbinfo\fR program to be able to return information\&.
-
+The \fBwinbindd(8)\fR daemon must be configured
+and running for the \fBwbinfo\fR program to be able
+to return information.
.SH "OPTIONS"
-
-.TP
--u
-This option will list all users available in the Windows NT domain for which the \fBwinbindd\fR(8) daemon is operating in\&. Users in all trusted domains will also be listed\&. Note that this operation does not assign user ids to any users that have not already been seen by \fBwinbindd\fR(8) \&.
-
-
-.TP
--g
-This option will list all groups available in the Windows NT domain for which the \fBSamba\fR(7) daemon is operating in\&. Groups in all trusted domains will also be listed\&. Note that this operation does not assign group ids to any groups that have not already been seen by \fBwinbindd\fR(8)\&.
-
-
-.TP
--N name
-The \fI-N\fR option queries \fBwinbindd\fR(8) to query the WINS server for the IP address associated with the NetBIOS name specified by the \fIname\fR parameter\&.
-
-
-.TP
--I ip
-The \fI-I\fR option queries \fBwinbindd\fR(8) to send a node status request to get the NetBIOS name associated with the IP address specified by the \fIip\fR parameter\&.
-
-
.TP
--n name
-The \fI-n\fR option queries \fBwinbindd\fR(8) for the SID associated with the name specified\&. Domain names can be specified before the user name by using the winbind separator character\&. For example CWDOM1/Administrator refers to the Administrator user in the domain CWDOM1\&. If no domain is specified then the domain used is the one specified in the \fBsmb.conf\fR(5) \fIworkgroup \fR parameter\&.
-
-
-.TP
--s sid
-Use \fI-s\fR to resolve a SID to a name\&. This is the inverse of the \fI-n \fR option above\&. SIDs must be specified as ASCII strings in the traditional Microsoft format\&. For example, S-1-5-21-1455342024-3071081365-2475485837-500\&.
-
-
-.TP
--U uid
-Try to convert a UNIX user id to a Windows NT SID\&. If the uid specified does not refer to one within the winbind uid range then the operation will fail\&.
-
-
-.TP
--G gid
-Try to convert a UNIX group id to a Windows NT SID\&. If the gid specified does not refer to one within the winbind gid range then the operation will fail\&.
-
-
-.TP
--S sid
-Convert a SID to a UNIX user id\&. If the SID does not correspond to a UNIX user mapped by \fBwinbindd\fR(8) then the operation will fail\&.
-
-
-.TP
--Y sid
-Convert a SID to a UNIX group id\&. If the SID does not correspond to a UNIX group mapped by \fBwinbindd\fR(8) then the operation will fail\&.
-
-
-.TP
--t
-Verify that the workstation trust account created when the Samba server is added to the Windows NT domain is working\&.
-
-
-.TP
--m
-Produce a list of domains trusted by the Windows NT server \fBwinbindd\fR(8) contacts when resolving names\&. This list does not include the Windows NT domain the server is a Primary Domain Controller for\&.
-
-
-.TP
---sequence
-Show sequence numbers of all known domains
-
-
-.TP
--r username
-Try to obtain the list of UNIX group ids to which the user belongs\&. This only works for users defined on a Domain Controller\&.
-
-
-.TP
--a username%password
-Attempt to authenticate a user via winbindd\&. This checks both authenticaion methods and reports its results\&.
-
-
-.TP
--A username%password
-Store username and password used by winbindd during session setup to a domain controller\&. This enables winbindd to operate in a Windows 2000 domain with Restrict Anonymous turned on (a\&.k\&.a\&. Permissions compatiable with Windows 2000 servers only)\&.
-
-
-.TP
---get-auth-user
-Print username and password used by winbindd during session setup to a domain controller\&. Username and password can be set using '-A'\&. Only available for root\&.
-
-
-.TP
--p
-Check whether winbindd is still alive\&. Prints out either 'succeeded' or 'failed'\&.
-
-
-.TP
--V
-Prints the version number for \fBsmbd\fR\&.
-
-
-.TP
--h|--help
-Print a summary of command line options\&.
-
-
+\fB-u\fR
+This option will list all users available
+in the Windows NT domain for which the \fBwinbindd(8)
+\fR daemon is operating in. Users in all trusted domains
+will also be listed. Note that this operation does not assign
+user ids to any users that have not already been seen by
+\fBwinbindd(8)\fR.
+.TP
+\fB-g\fR
+This option will list all groups available
+in the Windows NT domain for which the \fBwinbindd(8)
+\fR daemon is operating in. Groups in all trusted domains
+will also be listed. Note that this operation does not assign
+group ids to any groups that have not already been seen by
+\fBwinbindd(8)\fR.
+.TP
+\fB-N name\fR
+The \fI-N\fR option
+queries \fBwinbindd(8)\fR to query the WINS
+server for the IP address associated with the NetBIOS name
+specified by the \fIname\fR parameter.
+.TP
+\fB-I ip\fR
+The \fI-I\fR option
+queries \fBwinbindd(8)\fR to send a node status
+request to get the NetBIOS name associated with the IP address
+specified by the \fIip\fR parameter.
+.TP
+\fB-n name\fR
+The \fI-n\fR option
+queries \fBwinbindd(8)\fR for the SID
+associated with the name specified. Domain names can be specified
+before the user name by using the winbind separator character.
+For example CWDOM1/Administrator refers to the Administrator
+user in the domain CWDOM1. If no domain is specified then the
+domain used is the one specified in the \fIsmb.conf\fR
+\fIworkgroup\fR parameter.
+.TP
+\fB-s sid\fR
+Use \fI-s\fR to resolve
+a SID to a name. This is the inverse of the \fI-n
+\fR option above. SIDs must be specified as ASCII strings
+in the traditional Microsoft format. For example,
+S-1-5-21-1455342024-3071081365-2475485837-500.
+.TP
+\fB-U uid\fR
+Try to convert a UNIX user id to a Windows NT
+SID. If the uid specified does not refer to one within
+the winbind uid range then the operation will fail.
+.TP
+\fB-G gid\fR
+Try to convert a UNIX group id to a Windows
+NT SID. If the gid specified does not refer to one within
+the winbind gid range then the operation will fail.
+.TP
+\fB-S sid\fR
+Convert a SID to a UNIX user id. If the SID
+does not correspond to a UNIX user mapped by \fB winbindd(8)\fR then the operation will fail.
+.TP
+\fB-Y sid\fR
+Convert a SID to a UNIX group id. If the SID
+does not correspond to a UNIX group mapped by \fB winbindd(8)\fR then the operation will fail.
+.TP
+\fB-t\fR
+Verify that the workstation trust account
+created when the Samba server is added to the Windows NT
+domain is working.
+.TP
+\fB-m\fR
+Produce a list of domains trusted by the
+Windows NT server \fBwinbindd(8)\fR contacts
+when resolving names. This list does not include the Windows
+NT domain the server is a Primary Domain Controller for.
+.TP
+\fB-r username\fR
+Try to obtain the list of UNIX group ids
+to which the user belongs. This only works for users
+defined on a Domain Controller.
+.TP
+\fB-a username%password\fR
+Attempt to authenticate a user via winbindd.
+This checks both authenticaion methods and reports its results.
+.TP
+\fB-A username%password\fR
+Store username and password used by winbindd
+during session setup to a domain controller. This enables
+winbindd to operate in a Windows 2000 domain with Restrict
+Anonymous turned on (a.k.a. Permissions compatiable with
+Windows 2000 servers only).
.SH "EXIT STATUS"
-
.PP
-The wbinfo program returns 0 if the operation succeeded, or 1 if the operation failed\&. If the \fBwinbindd\fR(8) daemon is not working \fBwbinfo\fR will always return failure\&.
-
+The wbinfo program returns 0 if the operation
+succeeded, or 1 if the operation failed. If the \fBwinbindd(8)
+\fR daemon is not working \fBwbinfo\fR will always return
+failure.
.SH "VERSION"
-
.PP
-This man page is correct for version 3\&.0 of the Samba suite\&.
-
+This man page is correct for version 3.0 of
+the Samba suite.
.SH "SEE ALSO"
-
.PP
-\fBwinbindd\fR(8)
+\fBwinbindd(8)\fR
.SH "AUTHOR"
-
.PP
-The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&.
-
+The original Samba software and related utilities
+were created by Andrew Tridgell. Samba is now developed
+by the Samba Team as an Open Source project similar
+to the way the Linux kernel is developed.
.PP
-\fBwbinfo\fR and \fBwinbindd\fR were written by Tim Potter\&.
-
+\fBwbinfo\fR and \fBwinbindd\fR
+were written by Tim Potter.
.PP
-The conversion to DocBook for Samba 2\&.2 was done by Gerald Carter\&. The conversion to DocBook XML 4\&.2 for Samba 3\&.0 was done by Alexander Bokovoy\&.
-
+The conversion to DocBook for Samba 2.2 was done
+by Gerald Carter
diff --git a/docs/manpages/winbindd.8 b/docs/manpages/winbindd.8
index 31ed3ba332..696de8537b 100644
--- a/docs/manpages/winbindd.8
+++ b/docs/manpages/winbindd.8
@@ -1,240 +1,242 @@
-.\"Generated by db2man.xsl. Don't modify this, modify the source.
-.de Sh \" Subsection
-.br
-.if t .Sp
-.ne 5
-.PP
-\fB\\$1\fR
-.PP
-..
-.de Sp \" Vertical space (when we can't use .PP)
-.if t .sp .5v
-.if n .sp
-..
-.de Ip \" List item
-.br
-.ie \\n(.$>=3 .ne \\$3
-.el .ne 3
-.IP "\\$1" \\$2
-..
-.TH "WINBINDD" 8 "" "" ""
+.\" This manpage has been automatically generated by docbook2man
+.\" from a DocBook document. This tool can be found at:
+.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
+.\" Please send any bug reports, improvements, comments, patches,
+.\" etc. to Steve Cheng <steve@ggi-project.org>.
+.TH "WINBINDD" "8" "04 March 2003" "" ""
.SH NAME
-winbindd \- Name Service Switch daemon for resolving names from NT servers
-.SH "SYNOPSIS"
+winbindd \- Name Service Switch daemon for resolving names from NT servers
+.SH SYNOPSIS
-.nf
-\fBwinbindd\fR [-F] [-S] [-i] [-B] [-d <debug level>] [-s <smb config file>] [-n]
-.fi
+\fBwinbindd\fR [ \fB-F\fR ] [ \fB-S\fR ] [ \fB-i\fR ] [ \fB-B\fR ] [ \fB-d <debug level>\fR ] [ \fB-s <smb config file>\fR ] [ \fB-n\fR ]
.SH "DESCRIPTION"
-
-.PP
-This program is part of the \fBSamba\fR(7) suite\&.
-
-.PP
-\fBwinbindd\fR is a daemon that provides a service for the Name Service Switch capability that is present in most modern C libraries\&. The Name Service Switch allows user and system information to be obtained from different databases services such as NIS or DNS\&. The exact behaviour can be configured throught the \fI/etc/nsswitch\&.conf\fR file\&. Users and groups are allocated as they are resolved to a range of user and group ids specified by the administrator of the Samba system\&.
-
-.PP
-The service provided by \fBwinbindd\fR is called `winbind' and can be used to resolve user and group information from a Windows NT server\&. The service can also provide authentication services via an associated PAM module\&.
-
.PP
-The \fIpam_winbind\fR module in the 2\&.2\&.2 release only supports the \fIauth\fR and \fIaccount\fR module-types\&. The latter simply performs a getpwnam() to verify that the system can obtain a uid for the user\&. If the \fIlibnss_winbind\fR library has been correctly installed, this should always succeed\&.
-
-.PP
-The following nsswitch databases are implemented by the winbindd service:
-
+This program is part of the Samba suite.
+.PP
+\fBwinbindd\fR is a daemon that provides
+a service for the Name Service Switch capability that is present
+in most modern C libraries. The Name Service Switch allows user
+and system information to be obtained from different databases
+services such as NIS or DNS. The exact behaviour can be configured
+throught the \fI/etc/nsswitch.conf\fR file.
+Users and groups are allocated as they are resolved to a range
+of user and group ids specified by the administrator of the
+Samba system.
+.PP
+The service provided by \fBwinbindd\fR is called `winbind' and
+can be used to resolve user and group information from a
+Windows NT server. The service can also provide authentication
+services via an associated PAM module.
+.PP
+The \fIpam_winbind\fR module in the 2.2.2 release only
+supports the \fIauth\fR and \fIaccount\fR
+module-types. The latter simply
+performs a getpwnam() to verify that the system can obtain a uid for the
+user. If the \fIlibnss_winbind\fR library has been correctly
+installed, this should always succeed.
+.PP
+The following nsswitch databases are implemented by
+the winbindd service:
.TP
-hosts
-User information traditionally stored in the \fIhosts(5)\fR file and used by \fBgethostbyname(3)\fR functions\&. Names are resolved through the WINS server or by broadcast\&.
-
-
+\fBhosts\fR
+User information traditionally stored in
+the \fIhosts(5)\fR file and used by
+\fBgethostbyname(3)\fR functions. Names are
+resolved through the WINS server or by broadcast.
.TP
-passwd
-User information traditionally stored in the \fIpasswd(5)\fR file and used by \fBgetpwent(3)\fR functions\&.
-
-
+\fBpasswd\fR
+User information traditionally stored in
+the \fIpasswd(5)\fR file and used by
+\fBgetpwent(3)\fR functions.
.TP
-group
-Group information traditionally stored in the \fIgroup(5)\fR file and used by \fBgetgrent(3)\fR functions\&.
-
-
+\fBgroup\fR
+Group information traditionally stored in
+the \fIgroup(5)\fR file and used by
+\fBgetgrent(3)\fR functions.
+.PP
+For example, the following simple configuration in the
+\fI/etc/nsswitch.conf\fR file can be used to initially
+resolve user and group information from \fI/etc/passwd
+\fR and \fI/etc/group\fR and then from the
+Windows NT server.
.PP
-For example, the following simple configuration in the\fI/etc/nsswitch\&.conf\fR file can be used to initially resolve user and group information from \fI/etc/passwd \fR and \fI/etc/group\fR and then from the Windows NT server\&.
-.nf
+.nf
passwd: files winbind
group: files winbind
+
.fi
-
-
.PP
-The following simple configuration in the\fI/etc/nsswitch\&.conf\fR file can be used to initially resolve hostnames from \fI/etc/hosts\fR and then from the WINS server\&.
-
+The following simple configuration in the
+\fI/etc/nsswitch.conf\fR file can be used to initially
+resolve hostnames from \fI/etc/hosts\fR and then from the
+WINS server.
.SH "OPTIONS"
-
.TP
--F
-If specified, this parameter causes the main \fBwinbindd\fR process to not daemonize, i\&.e\&. double-fork and disassociate with the terminal\&. Child processes are still created as normal to service each connection request, but the main process does not exit\&. This operation mode is suitable for running \fBwinbindd\fR under process supervisors such as \fBsupervise\fR and \fBsvscan\fR from Daniel J\&. Bernstein's \fBdaemontools\fR package, or the AIX process monitor\&.
-
-
+\fB-F\fR
+If specified, this parameter causes
+the main \fBwinbindd\fR process to not daemonize,
+i.e. double-fork and disassociate with the terminal.
+Child processes are still created as normal to service
+each connection request, but the main process does not
+exit. This operation mode is suitable for running
+\fBwinbindd\fR under process supervisors such
+as \fBsupervise\fR and \fBsvscan\fR
+from Daniel J. Bernstein's \fBdaemontools\fR
+package, or the AIX process monitor.
.TP
--S
-If specified, this parameter causes \fBwinbindd\fR to log to standard output rather than a file\&.
-
-
+\fB-S\fR
+If specified, this parameter causes
+\fBwinbindd\fR to log to standard output rather
+than a file.
.TP
--V
-Prints the version number for \fBsmbd\fR\&.
-
-
+\fB-d debuglevel\fR
+Sets the debuglevel to an integer between
+0 and 100. 0 is for no debugging and 100 is for reams and
+reams. To submit a bug report to the Samba Team, use debug
+level 100 (see BUGS.txt).
.TP
--s <configuration file>
-The file specified contains the configuration details required by the server\&. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is to provide\&. See \fI smb\&.conf(5)\fR for more information\&. The default configuration file name is determined at compile time\&.
-
-
+\fB-i\fR
+Tells \fBwinbindd\fR to not
+become a daemon and detach from the current terminal. This
+option is used by developers when interactive debugging
+of \fBwinbindd\fR is required.
+\fBwinbindd\fR also logs to standard output,
+as if the \fB-S\fR parameter had been given.
.TP
--d|--debug=debuglevel
-\fIdebuglevel\fR is an integer from 0 to 10\&. The default value if this parameter is not specified is zero\&.
-
-
-The higher this value, the more detail will be logged to the log files about the activities of the server\&. At level 0, only critical errors and serious warnings will be logged\&. Level 1 is a reasonable level for day to day running - it generates a small amount of information about operations carried out\&.
-
-
-Levels above 1 will generate considerable amounts of log data, and should only be used when investigating a problem\&. Levels above 3 are designed for use only by developers and generate HUGE amounts of log data, most of which is extremely cryptic\&.
-
-
-Note that specifying this parameter here will override the log level parameter in the \fIsmb\&.conf(5)\fR file\&.
-
-
-.TP
--l|--logfile=logbasename
-File name for log/debug files\&. The extension \fB"\&.client"\fR will be appended\&. The log file is never removed by the client\&.
-
-
-.TP
--h|--help
-Print a summary of command line options\&.
-
-
+\fB-n\fR
+Disable caching. This means winbindd will
+always have to wait for a response from the domain controller
+before it can respond to a client and this thus makes things
+slower. The results will however be more accurate, since
+results from the cache might not be up-to-date. This
+might also temporarily hang winbindd if the DC doesn't respond.
.TP
--i
-Tells \fBwinbindd\fR to not become a daemon and detach from the current terminal\&. This option is used by developers when interactive debugging of \fBwinbindd\fR is required\&. \fBwinbindd\fR also logs to standard output, as if the \fB-S\fR parameter had been given\&.
-
-
+\fB-B\fR
+Dual daemon mode. This means winbindd will run
+as 2 threads. The first will answer all requests from the cache,
+thus making responses to clients faster. The other will
+update the cache for the query that the first has just responded.
+Advantage of this is that responses are accurate and fast.
.TP
--n
-Disable caching\&. This means winbindd will always have to wait for a response from the domain controller before it can respond to a client and this thus makes things slower\&. The results will however be more accurate, since results from the cache might not be up-to-date\&. This might also temporarily hang winbindd if the DC doesn't respond\&.
-
-
-.TP
--B
-Dual daemon mode\&. This means winbindd will run as 2 threads\&. The first will answer all requests from the cache, thus making responses to clients faster\&. The other will update the cache for the query that the first has just responded\&. Advantage of this is that responses stay accurate and are faster\&.
-
-
+\fB-s|--conf=smb.conf\fR
+Specifies the location of the all-important
+\fIsmb.conf\fR file.
.SH "NAME AND ID RESOLUTION"
-
-.PP
-Users and groups on a Windows NT server are assigned a relative id (rid) which is unique for the domain when the user or group is created\&. To convert the Windows NT user or group into a unix user or group, a mapping between rids and unix user and group ids is required\&. This is one of the jobs that \fB winbindd\fR performs\&.
-
-.PP
-As winbindd users and groups are resolved from a server, user and group ids are allocated from a specified range\&. This is done on a first come, first served basis, although all existing users and groups will be mapped as soon as a client performs a user or group enumeration command\&. The allocated unix ids are stored in a database file under the Samba lock directory and will be remembered\&.
-
.PP
-WARNING: The rid to unix id database is the only location where the user and group mappings are stored by winbindd\&. If this file is deleted or corrupted, there is no way for winbindd to determine which user and group ids correspond to Windows NT user and group rids\&.
-
+Users and groups on a Windows NT server are assigned
+a relative id (rid) which is unique for the domain when the
+user or group is created. To convert the Windows NT user or group
+into a unix user or group, a mapping between rids and unix user
+and group ids is required. This is one of the jobs that \fB winbindd\fR performs.
+.PP
+As winbindd users and groups are resolved from a server, user
+and group ids are allocated from a specified range. This
+is done on a first come, first served basis, although all existing
+users and groups will be mapped as soon as a client performs a user
+or group enumeration command. The allocated unix ids are stored
+in a database file under the Samba lock directory and will be
+remembered.
+.PP
+WARNING: The rid to unix id database is the only location
+where the user and group mappings are stored by winbindd. If this
+file is deleted or corrupted, there is no way for winbindd to
+determine which user and group ids correspond to Windows NT user
+and group rids.
.SH "CONFIGURATION"
-
.PP
-Configuration of the \fBwinbindd\fR daemon is done through configuration parameters in the \fBsmb.conf\fR(5) file\&. All parameters should be specified in the [global] section of smb\&.conf\&.
-
-.TP 3
+Configuration of the \fBwinbindd\fR daemon
+is done through configuration parameters in the \fIsmb.conf(5)
+\fR file. All parameters should be specified in the
+[global] section of smb.conf.
+.TP 0.2i
\(bu
\fIwinbind separator\fR
-
-.TP
+.TP 0.2i
\(bu
\fIwinbind uid\fR
-
-.TP
+.TP 0.2i
\(bu
\fIwinbind gid\fR
-
-.TP
+.TP 0.2i
\(bu
\fIwinbind cache time\fR
-
-.TP
+.TP 0.2i
\(bu
\fIwinbind enum users\fR
-
-.TP
+.TP 0.2i
\(bu
\fIwinbind enum groups\fR
-
-.TP
+.TP 0.2i
\(bu
\fItemplate homedir\fR
-
-.TP
+.TP 0.2i
\(bu
\fItemplate shell\fR
-
-.TP
+.TP 0.2i
\(bu
\fIwinbind use default domain\fR
-
-.LP
-
.SH "EXAMPLE SETUP"
-
.PP
-To setup winbindd for user and group lookups plus authentication from a domain controller use something like the following setup\&. This was tested on a RedHat 6\&.2 Linux box\&.
-
+To setup winbindd for user and group lookups plus
+authentication from a domain controller use something like the
+following setup. This was tested on a RedHat 6.2 Linux box.
+.PP
+In \fI/etc/nsswitch.conf\fR put the
+following:
.PP
-In \fI/etc/nsswitch\&.conf\fR put the following:
-.nf
+.nf
passwd: files winbind
group: files winbind
+
.fi
-
-
.PP
-In \fI/etc/pam\&.d/*\fR replace the \fI auth\fR lines with something like this:
-.nf
+In \fI/etc/pam.d/*\fR replace the
+\fIauth\fR lines with something like this:
+.PP
-auth required /lib/security/pam_securetty\&.so
-auth required /lib/security/pam_nologin\&.so
-auth sufficient /lib/security/pam_winbind\&.so
-auth required /lib/security/pam_pwdb\&.so use_first_pass shadow nullok
+.nf
+auth required /lib/security/pam_securetty.so
+auth required /lib/security/pam_nologin.so
+auth sufficient /lib/security/pam_winbind.so
+auth required /lib/security/pam_pwdb.so use_first_pass shadow nullok
+
.fi
-
-
.PP
-Note in particular the use of the \fIsufficient \fR keyword and the \fIuse_first_pass\fR keyword\&.
-
+Note in particular the use of the \fIsufficient\fR
+keyword and the \fIuse_first_pass\fR keyword.
.PP
-Now replace the account lines with this:
-
+Now replace the account lines with this:
.PP
-\fBaccount required /lib/security/pam_winbind.so \fR
-
+\fBaccount required /lib/security/pam_winbind.so
+\fR
.PP
-The next step is to join the domain\&. To do that use the\fBnet\fR program like this:
-
+The next step is to join the domain. To do that use the
+\fBsmbpasswd\fR program like this:
.PP
-\fBnet join -S PDC -U Administrator\fR
-
+\fBsmbpasswd -j DOMAIN -r PDC -U
+Administrator\fR
.PP
-The username after the \fI-U\fR can be any Domain user that has administrator privileges on the machine\&. Substitute the name or IP of your PDC for "PDC"\&.
-
+The username after the \fI-U\fR can be any
+Domain user that has administrator privileges on the machine.
+Substitute your domain name for "DOMAIN" and the name of your PDC
+for "PDC".
.PP
-Next copy \fIlibnss_winbind\&.so\fR to\fI/lib\fR and \fIpam_winbind\&.so \fR to \fI/lib/security\fR\&. A symbolic link needs to be made from \fI/lib/libnss_winbind\&.so\fR to\fI/lib/libnss_winbind\&.so\&.2\fR\&. If you are using an older version of glibc then the target of the link should be\fI/lib/libnss_winbind\&.so\&.1\fR\&.
-
+Next copy \fIlibnss_winbind.so\fR to
+\fI/lib\fR and \fIpam_winbind.so\fR
+to \fI/lib/security\fR. A symbolic link needs to be
+made from \fI/lib/libnss_winbind.so\fR to
+\fI/lib/libnss_winbind.so.2\fR. If you are using an
+older version of glibc then the target of the link should be
+\fI/lib/libnss_winbind.so.1\fR.
+.PP
+Finally, setup a \fIsmb.conf\fR containing directives like the
+following:
.PP
-Finally, setup a \fBsmb.conf\fR(5) containing directives like the following:
-.nf
+.nf
[global]
winbind separator = +
winbind cache time = 10
@@ -245,97 +247,105 @@ Finally, setup a \fBsmb.conf\fR(5) containing directives like the following:
workgroup = DOMAIN
security = domain
password server = *
+
.fi
-
-
.PP
-Now start winbindd and you should find that your user and group database is expanded to include your NT users and groups, and that you can login to your unix box as a domain user, using the DOMAIN+user syntax for the username\&. You may wish to use the commands \fBgetent passwd\fR and \fBgetent group \fR to confirm the correct operation of winbindd\&.
-
+Now start winbindd and you should find that your user and
+group database is expanded to include your NT users and groups,
+and that you can login to your unix box as a domain user, using
+the DOMAIN+user syntax for the username. You may wish to use the
+commands \fBgetent passwd\fR and \fBgetent group
+\fR to confirm the correct operation of winbindd.
.SH "NOTES"
-
.PP
-The following notes are useful when configuring and running \fBwinbindd\fR:
-
+The following notes are useful when configuring and
+running \fBwinbindd\fR:
.PP
-\fBnmbd\fR(8) must be running on the local machine for \fBwinbindd\fR to work\&. \fBwinbindd\fR queries the list of trusted domains for the Windows NT server on startup and when a SIGHUP is received\&. Thus, for a running \fB winbindd\fR to become aware of new trust relationships between servers, it must be sent a SIGHUP signal\&.
-
+\fBnmbd\fR must be running on the local machine
+for \fBwinbindd\fR to work. \fBwinbindd\fR
+queries the list of trusted domains for the Windows NT server
+on startup and when a SIGHUP is received. Thus, for a running \fB winbindd\fR to become aware of new trust relationships between
+servers, it must be sent a SIGHUP signal.
.PP
-PAM is really easy to misconfigure\&. Make sure you know what you are doing when modifying PAM configuration files\&. It is possible to set up PAM such that you can no longer log into your system\&.
-
+Client processes resolving names through the \fBwinbindd\fR
+nsswitch module read an environment variable named \fB $WINBINDD_DOMAIN\fR. If this variable contains a comma separated
+list of Windows NT domain names, then winbindd will only resolve users
+and groups within those Windows NT domains.
.PP
-If more than one UNIX machine is running \fBwinbindd\fR, then in general the user and groups ids allocated by winbindd will not be the same\&. The user and group ids will only be valid for the local machine\&.
-
+PAM is really easy to misconfigure. Make sure you know what
+you are doing when modifying PAM configuration files. It is possible
+to set up PAM such that you can no longer log into your system.
.PP
-If the the Windows NT RID to UNIX user and group id mapping file is damaged or destroyed then the mappings will be lost\&.
-
+If more than one UNIX machine is running \fBwinbindd\fR,
+then in general the user and groups ids allocated by winbindd will not
+be the same. The user and group ids will only be valid for the local
+machine.
+.PP
+If the the Windows NT RID to UNIX user and group id mapping
+file is damaged or destroyed then the mappings will be lost.
.SH "SIGNALS"
-
.PP
-The following signals can be used to manipulate the\fBwinbindd\fR daemon\&.
-
+The following signals can be used to manipulate the
+\fBwinbindd\fR daemon.
.TP
-SIGHUP
-Reload the \fBsmb.conf\fR(5) file and apply any parameter changes to the running version of winbindd\&. This signal also clears any cached user and group information\&. The list of other domains trusted by winbindd is also reloaded\&.
-
-
+\fBSIGHUP\fR
+Reload the \fIsmb.conf(5)\fR
+file and apply any parameter changes to the running
+version of winbindd. This signal also clears any cached
+user and group information. The list of other domains trusted
+by winbindd is also reloaded.
.TP
-SIGUSR1
-The SIGUSR1 signal will cause \fB winbindd\fR to write status information to the winbind log file including information about the number of user and group ids allocated by \fBwinbindd\fR\&.
-
-
-Log files are stored in the filename specified by the log file parameter\&.
-
+\fBSIGUSR1\fR
+The SIGUSR1 signal will cause \fB winbindd\fR to write status information to the winbind
+log file including information about the number of user and
+group ids allocated by \fBwinbindd\fR.
+Log files are stored in the filename specified by the
+log file parameter.
.SH "FILES"
-
.TP
-\fI/etc/nsswitch\&.conf(5)\fR
-Name service switch configuration file\&.
-
-
+\fB\fI/etc/nsswitch.conf(5)\fB\fR
+Name service switch configuration file.
.TP
-/tmp/\&.winbindd/pipe
-The UNIX pipe over which clients communicate with the \fBwinbindd\fR program\&. For security reasons, the winbind client will only attempt to connect to the winbindd daemon if both the \fI/tmp/\&.winbindd\fR directory and \fI/tmp/\&.winbindd/pipe\fR file are owned by root\&.
-
-
+\fB/tmp/.winbindd/pipe\fR
+The UNIX pipe over which clients communicate with
+the \fBwinbindd\fR program. For security reasons, the
+winbind client will only attempt to connect to the winbindd daemon
+if both the \fI/tmp/.winbindd\fR directory
+and \fI/tmp/.winbindd/pipe\fR file are owned by
+root.
.TP
-$LOCKDIR/winbindd_privilaged/pipe
-The UNIX pipe over which 'privilaged' clients communicate with the \fBwinbindd\fR program\&. For security reasons, access to some winbindd functions - like those needed by the \fBntlm_auth\fR utility - is restricted\&. By default, only users in the 'root' group will get this access, however the administrator may change the group permissions on $LOCKDIR/winbindd_privilaged to allow programs like 'squid' to use ntlm_auth\&. Note that the winbind client will only attempt to connect to the winbindd daemon if both the \fI$LOCKDIR/winbindd_privilaged\fR directory and \fI$LOCKDIR/winbindd_privilaged/pipe\fR file are owned by root\&.
-
-
+\fB/lib/libnss_winbind.so.X\fR
+Implementation of name service switch library.
.TP
-/lib/libnss_winbind\&.so\&.X
-Implementation of name service switch library\&.
-
-
+\fB$LOCKDIR/winbindd_idmap.tdb\fR
+Storage for the Windows NT rid to UNIX user/group
+id mapping. The lock directory is specified when Samba is initially
+compiled using the \fI--with-lockdir\fR option.
+This directory is by default \fI/usr/local/samba/var/locks
+\fR.
.TP
-$LOCKDIR/winbindd_idmap\&.tdb
-Storage for the Windows NT rid to UNIX user/group id mapping\&. The lock directory is specified when Samba is initially compiled using the \fI--with-lockdir\fR option\&. This directory is by default \fI/usr/local/samba/var/locks \fR\&.
-
-
-.TP
-$LOCKDIR/winbindd_cache\&.tdb
-Storage for cached user and group information\&.
-
-
+\fB$LOCKDIR/winbindd_cache.tdb\fR
+Storage for cached user and group information.
.SH "VERSION"
-
.PP
-This man page is correct for version 3\&.0 of the Samba suite\&.
-
+This man page is correct for version 3.0 of
+the Samba suite.
.SH "SEE ALSO"
-
.PP
-\fInsswitch\&.conf(5)\fR, \fBSamba\fR(7), \fBwbinfo\fR(8), \fBsmb.conf\fR(5)
-
+\fInsswitch.conf(5)\fR,
+samba(7)
+wbinfo(1)
+smb.conf(5)
.SH "AUTHOR"
-
.PP
-The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&.
-
+The original Samba software and related utilities
+were created by Andrew Tridgell. Samba is now developed
+by the Samba Team as an Open Source project similar
+to the way the Linux kernel is developed.
.PP
-\fBwbinfo\fR and \fBwinbindd\fR were written by Tim Potter\&.
-
+\fBwbinfo\fR and \fBwinbindd\fR
+were written by Tim Potter.
.PP
-The conversion to DocBook for Samba 2\&.2 was done by Gerald Carter\&. The conversion to DocBook XML 4\&.2 for Samba 3\&.0 was done by Alexander Bokovoy\&.
-
+The conversion to DocBook for Samba 2.2 was done
+by Gerald Carter
diff --git a/docs/textdocs/README.jis b/docs/textdocs/README.jis
new file mode 100644
index 0000000000..50ff0cced7
--- /dev/null
+++ b/docs/textdocs/README.jis
@@ -0,0 +1,149 @@
+● samba 日本語対応について
+
+1. 目的
+
+ 日本語対応は、
+
+ (1) MS-Windows 紊如岨侫.ぅ詭をどう瘢雹しても扱う瘢雹必要のあるアプリケ・踉札轡腑鵑舛鹿粡寂蝟赱齠洲痲筵娼んと動作する。例えば、MS-WORD 5 などは、インスト・踉札觧亡岨離侫.ぅ詭を・踉至
+ につけてしまいます。こう瘢雹いった豺腓砲舛磴鵑搬弍任襪茲逅擦砲垢襦鹿粡寂蝟赱齠洲痲筵娼鹿粡寂蝟赱齠洲痲筵娼┣嬶婦ぢは、最近ではほとんどのものが 8 bits のファイル巳苳擦鬟汽檗トしていますが、
+ 中には、これをサポ・踉札箸靴討い覆い發里發△蠅泙后海里茲逅擦弗苳詞合でも、(1)の目的
+ が満足できるよう瘢雹にする。
+
+ を目的としています。そのため、日本語対応は、必要最造靴圓覆辰討蠅泙擦鵝鹿粡寂蝟赱齠洲痲筵娼鹿粡寂蝟赱齠洲痲筵娼日本語対応した samba を利用するためには、コンパイルする時に、必ず、KANJI の定義を追
+ 加してください。このオプションを指定していない豺腓蓮楔譴離侫.ぅ詭を正しく扱
+ う瘢雹ことはできません。(コンパイルについては、王踉撒を参箸靴堂さい)
+
+2. 利用方法
+
+(1) 追加したパラメ・踉札鹿粡寂蝟赱齠洲痲筵娼鹿粡寂蝟赱齠洲痲筵娼鼾皰竢鈕ぢファイルの global セクションに以王踉擦離僖薀瓠タを設定できるよう瘢雹にしました。
+
+ [global]
+ ....
+ coding system = <コ・踉札彪鹿粡寂蝟赱齠洲痲筵娼鹿粡寂蝟赱齠洲痲筵娼ここで指定されたコ・踉札彪呂良紊離侫.ぅ襯轡好謄爐離侫.ぅ詭のコ・踉札匹砲覆蠅泙后鹿粡寂蝟赱齠洲痲筵娼設定できるものは、,里茲逅擦砲覆辰討い泙后鹿粡寂蝟赱齠洲痲筵娼鹿粡寂蝟赱齠洲痲筵娼鼕蜩班瀞瓶羊ぢ漢字コ・踉札鹿粡寂蝟赱齠洲痲筵娼纒禳嫦ぢコ・踉札鹿粡寂蝟赱齠洲痲筵娼蒹砠ぢの ASCII コ・踉札桧奮阿離魁ドを以王踉擦侶薦踉三で表す方阿任后N磴┐弌鹿粡寂蝟赱齠洲痲筵娼 ぢオフィス' という瘢雹巳苳餐阿蓮Ш験佐杭験嵯敢験佐穏験叉硯ぢのよう瘢雹に、':' の後に2桁
+ の16進数を続ける形阿砲覆蠅泙后鹿粡寂蝟赱齠洲痲筵娼 ここで、':' を側苳擦諒源吠儿垢靴燭う苳詞合は、hex の後ろにその文字を指定します。
+ 例えば、@を変わりに使いたい豺腓蓮ц纔是のよう瘢雹に指定します。
+ cap: 7 bits の ASCII コ・踉札桧奮阿離魁ドを以王踉擦侶薦踉三で表す方阿箸い逅仕世任鹿粡寂蝟赱齠洲痲筵娼蒹ぢと同様ですが、CAP (The Columbia AppleTalk Package)と互換性を持つ変換
+ 方阿箸覆辰討い泙后蒹ぢとの違いは0x80以紊離魁ドのみ':80'のよう瘢雹に変換
+ され、その側苳擦喪檀ぢコ・踉札匹埜修気譴泙后鹿粡寂蝟赱齠洲痲筵娼例えば、'オフィス'という瘢雹巳苳餐阿蓮Ш験漂験験尊験悋となります。
+
+ JIS コ・踉札匹砲弔い討蓮焚の表を参箸靴堂さい。
+ ┌───┬────┬────┬────┬────┬────┬─────────┐
+ │指定 │漢字開始│漢字終了│カナ開始│カナ終了│英数開始│備考 │
+ ├───┼────┼────┼────┼────┼────┼─────────┤
+ │jis7 │\E$B │\E(J │0x0e │0x0f │\E(J │jis 7単位符号 │
+ │junet │\E$B │\E(J │\E(I │\E(J │\E(J │7bits コ・踉札│
+ │jis8 │\E$B │\E(J │-- │-- │\E(J │jis 8単位符号 │
+ │j7bb │\E$B │\E(B │0x0e │0x0f │\E(B │ │
+ │j7bj │\E$B │\E(J │0x0e │0x0f │\E(J │jis7と同じ │
+ │j7bh │\E$B │\E(H │0x0e │0x0f │\E(H │ │
+ │j7@b │\E$@ │\E(B │0x0e │0x0f │\E(B │ │
+ │j7@j │\E$@ │\E(J │0x0e │0x0f │\E(J │ │
+ │j7@h │\E$@ │\E(H │0x0e │0x0f │\E(H │ │
+ │j8bb │\E$B │\E(B │-- │-- │\E(B │ │
+ │j8bj │\E$B │\E(J │-- │-- │\E(J │jis8と同じ │
+ │j8bh │\E$B │\E(H │-- │-- │\E(H │ │
+ │j8@b │\E@@ │\E(B │-- │-- │\E(B │ │
+ │j8@j │\E$@ │\E(J │-- │-- │\E(J │ │
+ │j8@h │\E$@ │\E(H │-- │-- │\E(H │ │
+ │jubb │\E$B │\E(B │\E(I │\E(B │\E(B │ │
+ │jubj │\E$B │\E(J │\E(I │\E(J │\E(J │junetと同じ │
+ │jubh │\E$B │\E(H │\E(I │\E(H │\E(H │ │
+ │ju@b │\E$@ │\E(B │\E(I │\E(B │\E(B │ │
+ │ju@j │\E$@ │\E(J │\E(I │\E(J │\E(J │ │
+ │ju@h │\E$@ │\E(H │\E(I │\E(H │\E(H │ │
+ └瘢雹───┴────┴────┴────┴────┴────┴─────────┘
+
+ いずれの豺腓癲△垢任紡減澆靴討い詭前に対しては、漢字の開始終了シ・踉札吋鵐垢蓮焚
+ のものを認韻靴泙后鹿粡寂蝟赱齠洲痲筵娼 ぢ漢字の始まり: \E$B か \E$@
+ 漢字の終り: \E(J か \E(B か \E(H
+
+(2) smbclient のオプション
+
+ クライアントプログラムでも、漢字や王苳嗣を含んだファイルを扱えるよう瘢雹に、,離廛轡腑鹿粡寂蝟赱齠洲痲筵娼を追加しました。
+
+ -t <タ・踉札潺淵襯魁ド系>
+
+ ここで、<タ・踉札潺淵襯魁ド系>に指定できるものは、紊コ・踉札彪と同じものです。
+
+(3) デフォルト
+
+ デフォルトのコ・踉札彪呂蓮▲灰鵐僖ぅ觧坊茲泙蠅泙后鹿粡寂蝟赱齠洲痲筵娼鹿粡寂蝟赱齠洲痲筵娼凱ぢコンパイル時の設定
+
+ Makefile に設定する項目を以王踉擦胞踉雑します。
+
+(1) KANJI フラグ
+
+ コンパイルオプションに -DKANJI=\"コ・踉札彪棧ぢを指定します。このコ・踉札彪呂で指
+ 定するものと同じです。例えば、-DKANJI=\"euc\" をFLAGSM に設定すると UNIX 紊離侫鹿粡寂蝟赱齠洲痲筵娼イル巳苳擦蓮鍍コ・踉札匹砲覆蠅泙后海海濃慊蠅靴織魁ド系は、サ・踉札亠擇咼薀ぅ▲鵐鹿粡寂蝟赱齠洲痲筵娼プログラムのデフォルトに値なります。
+
+ 亜▲廛轡腑鹵罎ぢや " も忘れずに指定して王踉擦気ぁ鹿粡寂蝟赱齠洲痲筵娼鹿粡寂蝟赱齠洲痲筵娼凱ぢ制限事項
+
+(1) 漢字コ・踉札鹿粡寂蝟赱齠洲痲筵娼鼾矮ぢを動作させるホストの UNIX がサポ・踉札箸靴討い覆ご岨魁ドは、利用できないことが
+ あります。変な動作をするよう瘢雹なら hex の指定をするのが良いでしょう瘢雹。
+
+(2) smbclient コマンド
+ シフトコ・踉札匹覆匹隆愀犬如岨箍巳苳擦魎泙鵑瀬侫.ぅ詭の ls の表┐陲譴襪海箸△鹿粡寂蝟赱齠洲痲筵娼ます。
+
+(3) ワイルドカ・踉札匹砲弔い鹿粡寂蝟赱齠洲痲筵娼ちゃんとしたスペックがよくわからなかったのですが、一応、DOS/V の動作と同じ動作を行な
+ う瘢雹よう瘢雹になっています。
+
+(4) ロングファイル巳苳擦砲弔い鹿粡寂蝟赱齠洲痲筵娼怏鈔阯淋では、ロングファイル巳苳擦靴┐泙后蹈鵐哀侫.ぅ詭を 8.3 フォ・踉札泪奪鹿粡寂蝟赱齠洲痲筵娼で扱う瘢雹ために、mangling していますが、この方法は、NT や 95 が行なっている mangling と
+ は異なりますので注意して王踉擦気ぁ鹿粡寂蝟赱齠洲痲筵娼鹿粡寂蝟赱齠洲痲筵娼堪ぢ祿嘉離譽檗トについて
+
+ 日本語のファイル巳苳擦亡悗靴董∧源修嬰陸苳祉害があれば、私にレポ・踉札箸靴督困韻譴亶い鹿粡寂蝟赱齠洲痲筵娼す。ただし、オリジナルからの問題点や遡笋砲弔い討蓮▲螢献淵襪虜遉踉市へ彫苳酸槎笋す腓錣擦鹿粡寂蝟赱齠洲痲筵娼か、もしくはメ・踉札螢鵐哀螢好箸覆匹悒譽檗トするよう瘢雹にして王踉擦気ぁ鹿粡寂蝟赱齠洲痲筵娼鹿粡寂蝟赱齠洲痲筵娼レポ・踉札箸気譴襴苳詞合、利用されている環境(UNIX 及び PC 側瘢雹のOSなど)とできましたら設定ファ
+イルやログなどを添付して頂けると幸いです。
+
+5. その側苳鹿粡寂蝟赱齠洲痲筵娼鹿粡寂蝟赱齠洲痲筵娼コ・踉札品儡垢楼焚の方々が作られたプログラムを利用しています。
+
+ hex 形ぢ大木@大塚・瘢雹筑波 <ohki@gssm.otsuka.tsukuba.ac.jp>氏
+ cap 形ぢ疋田 道郎 (michiro@po.iijnet.or.jp)(michiro@dms.toppan.co.jp)氏
+
+ その側苳察△燭気鵑諒垢蕕い蹐い蹐噺羔畿踉雑いただきありがとう瘢雹ございました。今後ともよ
+ろしくお願い致します。
+
+1994年10月28日 第1版
+1995年 8月16日 第2版
+1995年11月24日 第3版
+1996年 5月13日 第4版
+
+藤田 崇 fujita@ainix.isac.co.jp
+