summaryrefslogtreecommitdiff
path: root/docs/htmldocs/Samba-HOWTO-Collection.html
diff options
context:
space:
mode:
Diffstat (limited to 'docs/htmldocs/Samba-HOWTO-Collection.html')
-rw-r--r--docs/htmldocs/Samba-HOWTO-Collection.html3745
1 files changed, 2856 insertions, 889 deletions
diff --git a/docs/htmldocs/Samba-HOWTO-Collection.html b/docs/htmldocs/Samba-HOWTO-Collection.html
index 3bc4ad32e3..d9125d5aad 100644
--- a/docs/htmldocs/Samba-HOWTO-Collection.html
+++ b/docs/htmldocs/Samba-HOWTO-Collection.html
@@ -236,17 +236,17 @@ HREF="#SERVERTYPE"
><DL
><DT
>4.1. <A
-HREF="#AEN627"
+HREF="#AEN629"
>Stand Alone Server</A
></DT
><DT
>4.2. <A
-HREF="#AEN633"
+HREF="#AEN635"
>Domain Member Server</A
></DT
><DT
>4.3. <A
-HREF="#AEN639"
+HREF="#AEN641"
>Domain Controller</A
></DT
></DL
@@ -254,7 +254,7 @@ HREF="#AEN639"
><DT
>5. <A
HREF="#SECURITYLEVELS"
->User and Share security level (for servers not in a domain)</A
+>Samba as Stand-Alone server (User and Share security level)</A
></DT
><DT
>6. <A
@@ -265,47 +265,47 @@ HREF="#SAMBA-PDC"
><DL
><DT
>6.1. <A
-HREF="#AEN703"
+HREF="#AEN705"
>Prerequisite Reading</A
></DT
><DT
>6.2. <A
-HREF="#AEN708"
+HREF="#AEN710"
>Background</A
></DT
><DT
>6.3. <A
-HREF="#AEN746"
+HREF="#AEN748"
>Configuring the Samba Domain Controller</A
></DT
><DT
>6.4. <A
-HREF="#AEN788"
+HREF="#AEN790"
>Creating Machine Trust Accounts and Joining Clients to the Domain</A
></DT
><DT
>6.5. <A
-HREF="#AEN896"
+HREF="#AEN898"
>Common Problems and Errors</A
></DT
><DT
>6.6. <A
-HREF="#AEN944"
+HREF="#AEN946"
>System Policies and Profiles</A
></DT
><DT
>6.7. <A
-HREF="#AEN988"
+HREF="#AEN990"
>What other help can I get?</A
></DT
><DT
>6.8. <A
-HREF="#AEN1102"
+HREF="#AEN1104"
>Domain Control for Windows 9x/ME</A
></DT
><DT
>6.9. <A
-HREF="#AEN1240"
+HREF="#AEN1242"
>DOMAIN_CONTROL.txt : Windows NT Domain Control &#38; Samba</A
></DT
></DL
@@ -319,27 +319,27 @@ HREF="#SAMBA-BDC"
><DL
><DT
>7.1. <A
-HREF="#AEN1276"
+HREF="#AEN1278"
>Prerequisite Reading</A
></DT
><DT
>7.2. <A
-HREF="#AEN1280"
+HREF="#AEN1282"
>Background</A
></DT
><DT
>7.3. <A
-HREF="#AEN1288"
+HREF="#AEN1290"
>What qualifies a Domain Controller on the network?</A
></DT
><DT
>7.4. <A
-HREF="#AEN1297"
+HREF="#AEN1299"
>Can Samba be a Backup Domain Controller to an NT PDC?</A
></DT
><DT
>7.5. <A
-HREF="#AEN1302"
+HREF="#AEN1304"
>How do I set up a Samba BDC?</A
></DT
></DL
@@ -353,42 +353,42 @@ HREF="#ADS"
><DL
><DT
>8.1. <A
-HREF="#AEN1341"
+HREF="#AEN1343"
>Installing the required packages for Debian</A
></DT
><DT
>8.2. <A
-HREF="#AEN1348"
+HREF="#AEN1350"
>Installing the required packages for RedHat</A
></DT
><DT
>8.3. <A
-HREF="#AEN1358"
+HREF="#AEN1360"
>Compile Samba</A
></DT
><DT
>8.4. <A
-HREF="#AEN1373"
+HREF="#AEN1375"
>Setup your /etc/krb5.conf</A
></DT
><DT
>8.5. <A
-HREF="#AEN1383"
+HREF="#AEN1385"
>Create the computer account</A
></DT
><DT
>8.6. <A
-HREF="#AEN1395"
+HREF="#AEN1397"
>Test your server setup</A
></DT
><DT
>8.7. <A
-HREF="#AEN1400"
+HREF="#AEN1402"
>Testing with smbclient</A
></DT
><DT
>8.8. <A
-HREF="#AEN1403"
+HREF="#AEN1405"
>Notes</A
></DT
></DL
@@ -402,17 +402,17 @@ HREF="#DOMAIN-SECURITY"
><DL
><DT
>9.1. <A
-HREF="#AEN1425"
+HREF="#AEN1427"
>Joining an NT Domain with Samba 3.0</A
></DT
><DT
>9.2. <A
-HREF="#AEN1480"
+HREF="#AEN1482"
>Samba and Windows 2000 Domains</A
></DT
><DT
>9.3. <A
-HREF="#AEN1483"
+HREF="#AEN1485"
>Why is this better than security = server?</A
></DT
></DL
@@ -435,34 +435,34 @@ HREF="#INTEGRATE-MS-NETWORKS"
><DL
><DT
>10.1. <A
-HREF="#AEN1515"
+HREF="#AEN1517"
>Agenda</A
></DT
><DT
>10.2. <A
-HREF="#AEN1537"
+HREF="#AEN1539"
>Name Resolution in a pure Unix/Linux world</A
></DT
><DT
>10.3. <A
-HREF="#AEN1600"
+HREF="#AEN1602"
>Name resolution as used within MS Windows networking</A
></DT
><DT
>10.4. <A
-HREF="#AEN1645"
+HREF="#AEN1647"
>How browsing functions and how to deploy stable and
dependable browsing using Samba</A
></DT
><DT
>10.5. <A
-HREF="#AEN1655"
+HREF="#AEN1657"
>MS Windows security options and how to configure
Samba for seemless integration</A
></DT
><DT
>10.6. <A
-HREF="#AEN1725"
+HREF="#AEN1727"
>Conclusions</A
></DT
></DL
@@ -476,39 +476,39 @@ HREF="#UNIX-PERMISSIONS"
><DL
><DT
>11.1. <A
-HREF="#AEN1746"
+HREF="#AEN1748"
>Viewing and changing UNIX permissions using the NT
security dialogs</A
></DT
><DT
>11.2. <A
-HREF="#AEN1750"
+HREF="#AEN1752"
>How to view file security on a Samba share</A
></DT
><DT
>11.3. <A
-HREF="#AEN1761"
+HREF="#AEN1763"
>Viewing file ownership</A
></DT
><DT
>11.4. <A
-HREF="#AEN1781"
+HREF="#AEN1783"
>Viewing file or directory permissions</A
></DT
><DT
>11.5. <A
-HREF="#AEN1817"
+HREF="#AEN1819"
>Modifying file or directory permissions</A
></DT
><DT
>11.6. <A
-HREF="#AEN1839"
+HREF="#AEN1841"
>Interaction with the standard Samba create mask
parameters</A
></DT
><DT
>11.7. <A
-HREF="#AEN1903"
+HREF="#AEN1905"
>Interaction with the standard Samba file attribute
mapping</A
></DT
@@ -524,17 +524,17 @@ managed authentication</A
><DL
><DT
>12.1. <A
-HREF="#AEN1924"
+HREF="#AEN1926"
>Samba and PAM</A
></DT
><DT
>12.2. <A
-HREF="#AEN1968"
+HREF="#AEN1970"
>Distributed Authentication</A
></DT
><DT
>12.3. <A
-HREF="#AEN1975"
+HREF="#AEN1977"
>PAM Configuration in smb.conf</A
></DT
></DL
@@ -548,7 +548,7 @@ HREF="#MSDFS"
><DL
><DT
>13.1. <A
-HREF="#AEN1995"
+HREF="#AEN1997"
>Instructions</A
></DT
></DL
@@ -562,300 +562,344 @@ HREF="#PRINTING"
><DL
><DT
>14.1. <A
-HREF="#AEN2056"
+HREF="#AEN2058"
>Introduction</A
></DT
><DT
>14.2. <A
-HREF="#AEN2078"
+HREF="#AEN2080"
>Configuration</A
></DT
><DT
>14.3. <A
-HREF="#AEN2186"
+HREF="#AEN2188"
>The Imprints Toolset</A
></DT
><DT
>14.4. <A
-HREF="#AEN2229"
+HREF="#AEN2231"
>Diagnosis</A
></DT
></DL
></DD
><DT
>15. <A
+HREF="#CUPS-PRINTING"
+>CUPS Printing Support</A
+></DT
+><DD
+><DL
+><DT
+>15.1. <A
+HREF="#AEN2343"
+>Introduction</A
+></DT
+><DT
+>15.2. <A
+HREF="#AEN2348"
+>CUPS - RAW Print Through Mode</A
+></DT
+><DT
+>15.3. <A
+HREF="#AEN2403"
+>The CUPS Filter Chains</A
+></DT
+><DT
+>15.4. <A
+HREF="#AEN2442"
+>CUPS Print Drivers and Devices</A
+></DT
+><DT
+>15.5. <A
+HREF="#AEN2519"
+>Limiting the number of pages users can print</A
+></DT
+><DT
+>15.6. <A
+HREF="#AEN2608"
+>Advanced Postscript Printing from MS Windows</A
+></DT
+><DT
+>15.7. <A
+HREF="#AEN2623"
+>Auto-Deletion of CUPS spool files</A
+></DT
+></DL
+></DD
+><DT
+>16. <A
HREF="#WINBIND"
>Unified Logons between Windows NT and UNIX using Winbind</A
></DT
><DD
><DL
><DT
->15.1. <A
-HREF="#AEN2362"
+>16.1. <A
+HREF="#AEN2685"
>Abstract</A
></DT
><DT
->15.2. <A
-HREF="#AEN2366"
+>16.2. <A
+HREF="#AEN2689"
>Introduction</A
></DT
><DT
->15.3. <A
-HREF="#AEN2379"
+>16.3. <A
+HREF="#AEN2702"
>What Winbind Provides</A
></DT
><DT
->15.4. <A
-HREF="#AEN2390"
+>16.4. <A
+HREF="#AEN2713"
>How Winbind Works</A
></DT
><DT
->15.5. <A
-HREF="#AEN2433"
+>16.5. <A
+HREF="#AEN2756"
>Installation and Configuration</A
></DT
><DT
->15.6. <A
-HREF="#AEN2690"
+>16.6. <A
+HREF="#AEN3013"
>Limitations</A
></DT
><DT
->15.7. <A
-HREF="#AEN2700"
+>16.7. <A
+HREF="#AEN3023"
>Conclusion</A
></DT
></DL
></DD
><DT
->16. <A
+>17. <A
HREF="#IMPROVED-BROWSING"
>Improved browsing in samba</A
></DT
><DD
><DL
><DT
->16.1. <A
-HREF="#AEN2710"
+>17.1. <A
+HREF="#AEN3033"
>Overview of browsing</A
></DT
><DT
->16.2. <A
-HREF="#AEN2715"
+>17.2. <A
+HREF="#AEN3038"
>Browsing support in samba</A
></DT
><DT
->16.3. <A
-HREF="#AEN2723"
+>17.3. <A
+HREF="#AEN3046"
>Problem resolution</A
></DT
><DT
->16.4. <A
-HREF="#AEN2732"
+>17.4. <A
+HREF="#AEN3055"
>Browsing across subnets</A
></DT
><DT
->16.5. <A
-HREF="#AEN2772"
+>17.5. <A
+HREF="#AEN3095"
>Setting up a WINS server</A
></DT
><DT
->16.6. <A
-HREF="#AEN2791"
+>17.6. <A
+HREF="#AEN3114"
>Setting up Browsing in a WORKGROUP</A
></DT
><DT
->16.7. <A
-HREF="#AEN2809"
+>17.7. <A
+HREF="#AEN3132"
>Setting up Browsing in a DOMAIN</A
></DT
><DT
->16.8. <A
-HREF="#AEN2819"
+>17.8. <A
+HREF="#AEN3142"
>Forcing samba to be the master</A
></DT
><DT
->16.9. <A
-HREF="#AEN2828"
+>17.9. <A
+HREF="#AEN3151"
>Making samba the domain master</A
></DT
><DT
->16.10. <A
-HREF="#AEN2846"
+>17.10. <A
+HREF="#AEN3169"
>Note about broadcast addresses</A
></DT
><DT
->16.11. <A
-HREF="#AEN2849"
+>17.11. <A
+HREF="#AEN3172"
>Multiple interfaces</A
></DT
></DL
></DD
><DT
->17. <A
+>18. <A
HREF="#VFS"
>Stackable VFS modules</A
></DT
><DD
><DL
><DT
->17.1. <A
-HREF="#AEN2867"
+>18.1. <A
+HREF="#AEN3190"
>Introduction and configuration</A
></DT
><DT
->17.2. <A
-HREF="#AEN2876"
+>18.2. <A
+HREF="#AEN3199"
>Included modules</A
></DT
><DT
->17.3. <A
-HREF="#AEN2930"
+>18.3. <A
+HREF="#AEN3253"
>VFS modules available elsewhere</A
></DT
></DL
></DD
><DT
->18. <A
+>19. <A
HREF="#GROUPMAPPING"
>Group mapping HOWTO</A
></DT
><DT
->19. <A
+>20. <A
HREF="#SPEED"
>Samba performance issues</A
></DT
><DD
><DL
><DT
->19.1. <A
-HREF="#AEN2997"
+>20.1. <A
+HREF="#AEN3320"
>Comparisons</A
></DT
><DT
->19.2. <A
-HREF="#AEN3003"
+>20.2. <A
+HREF="#AEN3326"
>Socket options</A
></DT
><DT
->19.3. <A
-HREF="#AEN3010"
+>20.3. <A
+HREF="#AEN3333"
>Read size</A
></DT
><DT
->19.4. <A
-HREF="#AEN3015"
+>20.4. <A
+HREF="#AEN3338"
>Max xmit</A
></DT
><DT
->19.5. <A
-HREF="#AEN3020"
+>20.5. <A
+HREF="#AEN3343"
>Log level</A
></DT
><DT
->19.6. <A
-HREF="#AEN3023"
+>20.6. <A
+HREF="#AEN3346"
>Read raw</A
></DT
><DT
->19.7. <A
-HREF="#AEN3028"
+>20.7. <A
+HREF="#AEN3351"
>Write raw</A
></DT
><DT
->19.8. <A
-HREF="#AEN3032"
+>20.8. <A
+HREF="#AEN3355"
>Slow Clients</A
></DT
><DT
->19.9. <A
-HREF="#AEN3036"
+>20.9. <A
+HREF="#AEN3359"
>Slow Logins</A
></DT
><DT
->19.10. <A
-HREF="#AEN3039"
+>20.10. <A
+HREF="#AEN3362"
>Client tuning</A
></DT
></DL
></DD
><DT
->20. <A
+>21. <A
HREF="#GROUPPROFILES"
>Creating Group Prolicy Files</A
></DT
><DD
><DL
><DT
->20.1. <A
-HREF="#AEN3087"
+>21.1. <A
+HREF="#AEN3410"
>Windows '9x</A
></DT
><DT
->20.2. <A
-HREF="#AEN3097"
+>21.2. <A
+HREF="#AEN3420"
>Windows NT 4</A
></DT
><DT
->20.3. <A
-HREF="#AEN3135"
+>21.3. <A
+HREF="#AEN3458"
>Windows 2000/XP</A
></DT
></DL
></DD
><DT
->21. <A
+>22. <A
HREF="#SECURING-SAMBA"
>Securing Samba</A
></DT
><DD
><DL
><DT
->21.1. <A
-HREF="#AEN3216"
+>22.1. <A
+HREF="#AEN3539"
>Introduction</A
></DT
><DT
->21.2. <A
-HREF="#AEN3219"
+>22.2. <A
+HREF="#AEN3542"
>Using host based protection</A
></DT
><DT
->21.3. <A
-HREF="#AEN3226"
+>22.3. <A
+HREF="#AEN3549"
>Using interface protection</A
></DT
><DT
->21.4. <A
-HREF="#AEN3235"
+>22.4. <A
+HREF="#AEN3558"
>Using a firewall</A
></DT
><DT
->21.5. <A
-HREF="#AEN3242"
+>22.5. <A
+HREF="#AEN3565"
>Using a IPC$ share deny</A
></DT
><DT
->21.6. <A
-HREF="#AEN3251"
+>22.6. <A
+HREF="#AEN3574"
>Upgrading Samba</A
></DT
></DL
></DD
><DT
->22. <A
+>23. <A
HREF="#UNICODE"
>Unicode/Charsets</A
></DT
><DD
><DL
><DT
->22.1. <A
-HREF="#AEN3265"
+>23.1. <A
+HREF="#AEN3588"
>What are charsets and unicode?</A
></DT
><DT
->22.2. <A
-HREF="#AEN3274"
+>23.2. <A
+HREF="#AEN3597"
>Samba and charsets</A
></DT
></DL
@@ -870,166 +914,166 @@ HREF="#APPENDIXES"
><DD
><DL
><DT
->23. <A
+>24. <A
HREF="#PORTABILITY"
>Portability</A
></DT
><DD
><DL
><DT
->23.1. <A
-HREF="#AEN3303"
+>24.1. <A
+HREF="#AEN3626"
>HPUX</A
></DT
><DT
->23.2. <A
-HREF="#AEN3309"
+>24.2. <A
+HREF="#AEN3632"
>SCO Unix</A
></DT
><DT
->23.3. <A
-HREF="#AEN3313"
+>24.3. <A
+HREF="#AEN3636"
>DNIX</A
></DT
><DT
->23.4. <A
-HREF="#AEN3342"
+>24.4. <A
+HREF="#AEN3665"
>RedHat Linux Rembrandt-II</A
></DT
><DT
->23.5. <A
-HREF="#AEN3348"
+>24.5. <A
+HREF="#AEN3671"
>AIX</A
></DT
></DL
></DD
><DT
->24. <A
+>25. <A
HREF="#OTHER-CLIENTS"
>Samba and other CIFS clients</A
></DT
><DD
><DL
><DT
->24.1. <A
-HREF="#AEN3368"
+>25.1. <A
+HREF="#AEN3691"
>Macintosh clients?</A
></DT
><DT
->24.2. <A
-HREF="#AEN3377"
+>25.2. <A
+HREF="#AEN3700"
>OS2 Client</A
></DT
><DT
->24.3. <A
-HREF="#AEN3417"
+>25.3. <A
+HREF="#AEN3740"
>Windows for Workgroups</A
></DT
><DT
->24.4. <A
-HREF="#AEN3441"
+>25.4. <A
+HREF="#AEN3764"
>Windows '95/'98</A
></DT
><DT
->24.5. <A
-HREF="#AEN3457"
+>25.5. <A
+HREF="#AEN3780"
>Windows 2000 Service Pack 2</A
></DT
></DL
></DD
><DT
->25. <A
+>26. <A
HREF="#COMPILING"
>How to compile SAMBA</A
></DT
><DD
><DL
><DT
->25.1. <A
-HREF="#AEN3484"
+>26.1. <A
+HREF="#AEN3807"
>Access Samba source code via CVS</A
></DT
><DT
->25.2. <A
-HREF="#AEN3527"
+>26.2. <A
+HREF="#AEN3850"
>Accessing the samba sources via rsync and ftp</A
></DT
><DT
->25.3. <A
-HREF="#AEN3533"
+>26.3. <A
+HREF="#AEN3856"
>Building the Binaries</A
></DT
><DT
->25.4. <A
-HREF="#AEN3561"
+>26.4. <A
+HREF="#AEN3884"
>Starting the smbd and nmbd</A
></DT
></DL
></DD
><DT
->26. <A
+>27. <A
HREF="#BUGREPORT"
>Reporting Bugs</A
></DT
><DD
><DL
><DT
->26.1. <A
-HREF="#AEN3623"
+>27.1. <A
+HREF="#AEN3946"
>Introduction</A
></DT
><DT
->26.2. <A
-HREF="#AEN3633"
+>27.2. <A
+HREF="#AEN3956"
>General info</A
></DT
><DT
->26.3. <A
-HREF="#AEN3639"
+>27.3. <A
+HREF="#AEN3962"
>Debug levels</A
></DT
><DT
->26.4. <A
-HREF="#AEN3656"
+>27.4. <A
+HREF="#AEN3979"
>Internal errors</A
></DT
><DT
->26.5. <A
-HREF="#AEN3666"
+>27.5. <A
+HREF="#AEN3989"
>Attaching to a running process</A
></DT
><DT
->26.6. <A
-HREF="#AEN3669"
+>27.6. <A
+HREF="#AEN3992"
>Patches</A
></DT
></DL
></DD
><DT
->27. <A
+>28. <A
HREF="#DIAGNOSIS"
>The samba checklist</A
></DT
><DD
><DL
><DT
->27.1. <A
-HREF="#AEN3692"
+>28.1. <A
+HREF="#AEN4015"
>Introduction</A
></DT
><DT
->27.2. <A
-HREF="#AEN3697"
+>28.2. <A
+HREF="#AEN4020"
>Assumptions</A
></DT
><DT
->27.3. <A
-HREF="#AEN3707"
+>28.3. <A
+HREF="#AEN4030"
>Tests</A
></DT
><DT
->27.4. <A
-HREF="#AEN3817"
+>28.4. <A
+HREF="#AEN4140"
>Still having troubles?</A
></DT
></DL
@@ -3647,24 +3691,24 @@ HREF="#SERVERTYPE"
><DL
><DT
>4.1. <A
-HREF="#AEN627"
+HREF="#AEN629"
>Stand Alone Server</A
></DT
><DT
>4.2. <A
-HREF="#AEN633"
+HREF="#AEN635"
>Domain Member Server</A
></DT
><DT
>4.3. <A
-HREF="#AEN639"
+HREF="#AEN641"
>Domain Controller</A
></DT
><DD
><DL
><DT
>4.3.1. <A
-HREF="#AEN642"
+HREF="#AEN644"
>Domain Controller Types</A
></DT
></DL
@@ -3674,7 +3718,7 @@ HREF="#AEN642"
><DT
>5. <A
HREF="#SECURITYLEVELS"
->User and Share security level (for servers not in a domain)</A
+>Samba as Stand-Alone server (User and Share security level)</A
></DT
><DT
>6. <A
@@ -3685,80 +3729,80 @@ HREF="#SAMBA-PDC"
><DL
><DT
>6.1. <A
-HREF="#AEN703"
+HREF="#AEN705"
>Prerequisite Reading</A
></DT
><DT
>6.2. <A
-HREF="#AEN708"
+HREF="#AEN710"
>Background</A
></DT
><DT
>6.3. <A
-HREF="#AEN746"
+HREF="#AEN748"
>Configuring the Samba Domain Controller</A
></DT
><DT
>6.4. <A
-HREF="#AEN788"
+HREF="#AEN790"
>Creating Machine Trust Accounts and Joining Clients to the Domain</A
></DT
><DD
><DL
><DT
>6.4.1. <A
-HREF="#AEN831"
+HREF="#AEN833"
>Manual Creation of Machine Trust Accounts</A
></DT
><DT
>6.4.2. <A
-HREF="#AEN872"
+HREF="#AEN874"
>"On-the-Fly" Creation of Machine Trust Accounts</A
></DT
><DT
>6.4.3. <A
-HREF="#AEN881"
+HREF="#AEN883"
>Joining the Client to the Domain</A
></DT
></DL
></DD
><DT
>6.5. <A
-HREF="#AEN896"
+HREF="#AEN898"
>Common Problems and Errors</A
></DT
><DT
>6.6. <A
-HREF="#AEN944"
+HREF="#AEN946"
>System Policies and Profiles</A
></DT
><DT
>6.7. <A
-HREF="#AEN988"
+HREF="#AEN990"
>What other help can I get?</A
></DT
><DT
>6.8. <A
-HREF="#AEN1102"
+HREF="#AEN1104"
>Domain Control for Windows 9x/ME</A
></DT
><DD
><DL
><DT
>6.8.1. <A
-HREF="#AEN1128"
+HREF="#AEN1130"
>Configuration Instructions: Network Logons</A
></DT
><DT
>6.8.2. <A
-HREF="#AEN1147"
+HREF="#AEN1149"
>Configuration Instructions: Setting up Roaming User Profiles</A
></DT
></DL
></DD
><DT
>6.9. <A
-HREF="#AEN1240"
+HREF="#AEN1242"
>DOMAIN_CONTROL.txt : Windows NT Domain Control &#38; Samba</A
></DT
></DL
@@ -3772,53 +3816,53 @@ HREF="#SAMBA-BDC"
><DL
><DT
>7.1. <A
-HREF="#AEN1276"
+HREF="#AEN1278"
>Prerequisite Reading</A
></DT
><DT
>7.2. <A
-HREF="#AEN1280"
+HREF="#AEN1282"
>Background</A
></DT
><DT
>7.3. <A
-HREF="#AEN1288"
+HREF="#AEN1290"
>What qualifies a Domain Controller on the network?</A
></DT
><DD
><DL
><DT
>7.3.1. <A
-HREF="#AEN1291"
+HREF="#AEN1293"
>How does a Workstation find its domain controller?</A
></DT
><DT
>7.3.2. <A
-HREF="#AEN1294"
+HREF="#AEN1296"
>When is the PDC needed?</A
></DT
></DL
></DD
><DT
>7.4. <A
-HREF="#AEN1297"
+HREF="#AEN1299"
>Can Samba be a Backup Domain Controller to an NT PDC?</A
></DT
><DT
>7.5. <A
-HREF="#AEN1302"
+HREF="#AEN1304"
>How do I set up a Samba BDC?</A
></DT
><DD
><DL
><DT
>7.5.1. <A
-HREF="#AEN1319"
+HREF="#AEN1321"
>How do I replicate the smbpasswd file?</A
></DT
><DT
>7.5.2. <A
-HREF="#AEN1323"
+HREF="#AEN1325"
>Can I do this all with LDAP?</A
></DT
></DL
@@ -3834,51 +3878,51 @@ HREF="#ADS"
><DL
><DT
>8.1. <A
-HREF="#AEN1341"
+HREF="#AEN1343"
>Installing the required packages for Debian</A
></DT
><DT
>8.2. <A
-HREF="#AEN1348"
+HREF="#AEN1350"
>Installing the required packages for RedHat</A
></DT
><DT
>8.3. <A
-HREF="#AEN1358"
+HREF="#AEN1360"
>Compile Samba</A
></DT
><DT
>8.4. <A
-HREF="#AEN1373"
+HREF="#AEN1375"
>Setup your /etc/krb5.conf</A
></DT
><DT
>8.5. <A
-HREF="#AEN1383"
+HREF="#AEN1385"
>Create the computer account</A
></DT
><DD
><DL
><DT
>8.5.1. <A
-HREF="#AEN1387"
+HREF="#AEN1389"
>Possible errors</A
></DT
></DL
></DD
><DT
>8.6. <A
-HREF="#AEN1395"
+HREF="#AEN1397"
>Test your server setup</A
></DT
><DT
>8.7. <A
-HREF="#AEN1400"
+HREF="#AEN1402"
>Testing with smbclient</A
></DT
><DT
>8.8. <A
-HREF="#AEN1403"
+HREF="#AEN1405"
>Notes</A
></DT
></DL
@@ -3892,17 +3936,17 @@ HREF="#DOMAIN-SECURITY"
><DL
><DT
>9.1. <A
-HREF="#AEN1425"
+HREF="#AEN1427"
>Joining an NT Domain with Samba 3.0</A
></DT
><DT
>9.2. <A
-HREF="#AEN1480"
+HREF="#AEN1482"
>Samba and Windows 2000 Domains</A
></DT
><DT
>9.3. <A
-HREF="#AEN1483"
+HREF="#AEN1485"
>Why is this better than security = server?</A
></DT
></DL
@@ -3945,6 +3989,10 @@ different type of servers:</P
><P
>Backup Domain Controller</P
></LI
+><LI
+><P
+>ADS Domain Controller</P
+></LI
></UL
></LI
></UL
@@ -3957,7 +4005,7 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN627"
+NAME="AEN629"
>4.1. Stand Alone Server</A
></H2
><P
@@ -3995,7 +4043,7 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN633"
+NAME="AEN635"
>4.2. Domain Member Server</A
></H2
><P
@@ -4026,7 +4074,7 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN639"
+NAME="AEN641"
>4.3. Domain Controller</A
></H2
><P
@@ -4038,7 +4086,7 @@ CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
-NAME="AEN642"
+NAME="AEN644"
>4.3.1. Domain Controller Types</A
></H3
><P
@@ -4117,7 +4165,7 @@ CLASS="CHAPTER"
><A
NAME="SECURITYLEVELS"
></A
->Chapter 5. User and Share security level (for servers not in a domain)</H1
+>Chapter 5. Samba as Stand-Alone server (User and Share security level)</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
@@ -4223,7 +4271,7 @@ CLASS="SECT1"
><H2
CLASS="SECT1"
><A
-NAME="AEN703"
+NAME="AEN705"
>6.1. Prerequisite Reading</A
></H2
><P
@@ -4246,7 +4294,7 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN708"
+NAME="AEN710"
>6.2. Background</A
></H2
><P
@@ -4366,7 +4414,7 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN746"
+NAME="AEN748"
>6.3. Configuring the Samba Domain Controller</A
></H2
><P
@@ -4563,7 +4611,7 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN788"
+NAME="AEN790"
>6.4. Creating Machine Trust Accounts and Joining Clients to the Domain</A
></H2
><P
@@ -4749,7 +4797,7 @@ CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
-NAME="AEN831"
+NAME="AEN833"
>6.4.1. Manual Creation of Machine Trust Accounts</A
></H3
><P
@@ -4919,7 +4967,7 @@ CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
-NAME="AEN872"
+NAME="AEN874"
>6.4.2. "On-the-Fly" Creation of Machine Trust Accounts</A
></H3
><P
@@ -4956,7 +5004,7 @@ CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
-NAME="AEN881"
+NAME="AEN883"
>6.4.3. Joining the Client to the Domain</A
></H3
><P
@@ -5024,7 +5072,7 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN896"
+NAME="AEN898"
>6.5. Common Problems and Errors</A
></H2
><P
@@ -5230,7 +5278,7 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN944"
+NAME="AEN946"
>6.6. System Policies and Profiles</A
></H2
><P
@@ -5407,7 +5455,7 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN988"
+NAME="AEN990"
>6.7. What other help can I get?</A
></H2
><P
@@ -5827,7 +5875,7 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN1102"
+NAME="AEN1104"
>6.8. Domain Control for Windows 9x/ME</A
></H2
><DIV
@@ -5961,7 +6009,7 @@ CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
-NAME="AEN1128"
+NAME="AEN1130"
>6.8.1. Configuration Instructions: Network Logons</A
></H3
><P
@@ -6067,7 +6115,7 @@ CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
-NAME="AEN1147"
+NAME="AEN1149"
>6.8.2. Configuration Instructions: Setting up Roaming User Profiles</A
></H3
><DIV
@@ -6120,7 +6168,7 @@ CLASS="SECT3"
><HR><H4
CLASS="SECT3"
><A
-NAME="AEN1155"
+NAME="AEN1157"
>6.8.2.1. Windows NT Configuration</A
></H4
><P
@@ -6171,7 +6219,7 @@ CLASS="SECT3"
><HR><H4
CLASS="SECT3"
><A
-NAME="AEN1163"
+NAME="AEN1165"
>6.8.2.2. Windows 9X Configuration</A
></H4
><P
@@ -6202,7 +6250,7 @@ CLASS="SECT3"
><HR><H4
CLASS="SECT3"
><A
-NAME="AEN1171"
+NAME="AEN1173"
>6.8.2.3. Win9X and WinNT Configuration</A
></H4
><P
@@ -6247,7 +6295,7 @@ CLASS="SECT3"
><HR><H4
CLASS="SECT3"
><A
-NAME="AEN1178"
+NAME="AEN1180"
>6.8.2.4. Windows 9X Profile Setup</A
></H4
><P
@@ -6407,7 +6455,7 @@ CLASS="SECT3"
><HR><H4
CLASS="SECT3"
><A
-NAME="AEN1214"
+NAME="AEN1216"
>6.8.2.5. Windows NT Workstation 4.0</A
></H4
><P
@@ -6521,7 +6569,7 @@ CLASS="SECT3"
><HR><H4
CLASS="SECT3"
><A
-NAME="AEN1227"
+NAME="AEN1229"
>6.8.2.6. Windows NT Server</A
></H4
><P
@@ -6535,7 +6583,7 @@ CLASS="SECT3"
><HR><H4
CLASS="SECT3"
><A
-NAME="AEN1230"
+NAME="AEN1232"
>6.8.2.7. Sharing Profiles between W95 and NT Workstation 4.0</A
></H4
><DIV
@@ -6628,7 +6676,7 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN1240"
+NAME="AEN1242"
>6.9. DOMAIN_CONTROL.txt : Windows NT Domain Control &#38; Samba</A
></H2
><DIV
@@ -6773,7 +6821,7 @@ CLASS="SECT1"
><H2
CLASS="SECT1"
><A
-NAME="AEN1276"
+NAME="AEN1278"
>7.1. Prerequisite Reading</A
></H2
><P
@@ -6790,7 +6838,7 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN1280"
+NAME="AEN1282"
>7.2. Background</A
></H2
><P
@@ -6835,7 +6883,7 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN1288"
+NAME="AEN1290"
>7.3. What qualifies a Domain Controller on the network?</A
></H2
><P
@@ -6852,7 +6900,7 @@ CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
-NAME="AEN1291"
+NAME="AEN1293"
>7.3.1. How does a Workstation find its domain controller?</A
></H3
><P
@@ -6871,7 +6919,7 @@ CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
-NAME="AEN1294"
+NAME="AEN1296"
>7.3.2. When is the PDC needed?</A
></H3
><P
@@ -6887,7 +6935,7 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN1297"
+NAME="AEN1299"
>7.4. Can Samba be a Backup Domain Controller to an NT PDC?</A
></H2
><P
@@ -6910,7 +6958,7 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN1302"
+NAME="AEN1304"
>7.5. How do I set up a Samba BDC?</A
></H2
><P
@@ -6977,7 +7025,7 @@ CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
-NAME="AEN1319"
+NAME="AEN1321"
>7.5.1. How do I replicate the smbpasswd file?</A
></H3
><P
@@ -6998,7 +7046,7 @@ CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
-NAME="AEN1323"
+NAME="AEN1325"
>7.5.2. Can I do this all with LDAP?</A
></H3
><P
@@ -7054,7 +7102,7 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN1341"
+NAME="AEN1343"
>8.1. Installing the required packages for Debian</A
></H2
><P
@@ -7084,7 +7132,7 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN1348"
+NAME="AEN1350"
>8.2. Installing the required packages for RedHat</A
></H2
><P
@@ -7123,7 +7171,7 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN1358"
+NAME="AEN1360"
>8.3. Compile Samba</A
></H2
><P
@@ -7179,7 +7227,7 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN1373"
+NAME="AEN1375"
>8.4. Setup your /etc/krb5.conf</A
></H2
><P
@@ -7218,7 +7266,7 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN1383"
+NAME="AEN1385"
>8.5. Create the computer account</A
></H2
><P
@@ -7233,7 +7281,7 @@ CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
-NAME="AEN1387"
+NAME="AEN1389"
>8.5.1. Possible errors</A
></H3
><P
@@ -7258,7 +7306,7 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN1395"
+NAME="AEN1397"
>8.6. Test your server setup</A
></H2
><P
@@ -7278,7 +7326,7 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN1400"
+NAME="AEN1402"
>8.7. Testing with smbclient</A
></H2
><P
@@ -7291,7 +7339,7 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN1403"
+NAME="AEN1405"
>8.8. Notes</A
></H2
><P
@@ -7314,7 +7362,7 @@ CLASS="SECT1"
><H2
CLASS="SECT1"
><A
-NAME="AEN1425"
+NAME="AEN1427"
>9.1. Joining an NT Domain with Samba 3.0</A
></H2
><P
@@ -7502,7 +7550,7 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN1480"
+NAME="AEN1482"
>9.2. Samba and Windows 2000 Domains</A
></H2
><P
@@ -7516,7 +7564,7 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN1483"
+NAME="AEN1485"
>9.3. Why is this better than security = server?</A
></H2
><P
@@ -7610,7 +7658,7 @@ CLASS="TITLE"
><DIV
CLASS="PARTINTRO"
><A
-NAME="AEN1501"
+NAME="AEN1503"
></A
><H1
>Introduction</H1
@@ -7634,19 +7682,19 @@ HREF="#INTEGRATE-MS-NETWORKS"
><DL
><DT
>10.1. <A
-HREF="#AEN1515"
+HREF="#AEN1517"
>Agenda</A
></DT
><DT
>10.2. <A
-HREF="#AEN1537"
+HREF="#AEN1539"
>Name Resolution in a pure Unix/Linux world</A
></DT
><DD
><DL
><DT
>10.2.1. <A
-HREF="#AEN1553"
+HREF="#AEN1555"
><TT
CLASS="FILENAME"
>/etc/hosts</TT
@@ -7654,7 +7702,7 @@ CLASS="FILENAME"
></DT
><DT
>10.2.2. <A
-HREF="#AEN1569"
+HREF="#AEN1571"
><TT
CLASS="FILENAME"
>/etc/resolv.conf</TT
@@ -7662,7 +7710,7 @@ CLASS="FILENAME"
></DT
><DT
>10.2.3. <A
-HREF="#AEN1580"
+HREF="#AEN1582"
><TT
CLASS="FILENAME"
>/etc/host.conf</TT
@@ -7670,7 +7718,7 @@ CLASS="FILENAME"
></DT
><DT
>10.2.4. <A
-HREF="#AEN1588"
+HREF="#AEN1590"
><TT
CLASS="FILENAME"
>/etc/nsswitch.conf</TT
@@ -7680,47 +7728,47 @@ CLASS="FILENAME"
></DD
><DT
>10.3. <A
-HREF="#AEN1600"
+HREF="#AEN1602"
>Name resolution as used within MS Windows networking</A
></DT
><DD
><DL
><DT
>10.3.1. <A
-HREF="#AEN1612"
+HREF="#AEN1614"
>The NetBIOS Name Cache</A
></DT
><DT
>10.3.2. <A
-HREF="#AEN1617"
+HREF="#AEN1619"
>The LMHOSTS file</A
></DT
><DT
>10.3.3. <A
-HREF="#AEN1625"
+HREF="#AEN1627"
>HOSTS file</A
></DT
><DT
>10.3.4. <A
-HREF="#AEN1630"
+HREF="#AEN1632"
>DNS Lookup</A
></DT
><DT
>10.3.5. <A
-HREF="#AEN1633"
+HREF="#AEN1635"
>WINS Lookup</A
></DT
></DL
></DD
><DT
>10.4. <A
-HREF="#AEN1645"
+HREF="#AEN1647"
>How browsing functions and how to deploy stable and
dependable browsing using Samba</A
></DT
><DT
>10.5. <A
-HREF="#AEN1655"
+HREF="#AEN1657"
>MS Windows security options and how to configure
Samba for seemless integration</A
></DT
@@ -7728,24 +7776,24 @@ Samba for seemless integration</A
><DL
><DT
>10.5.1. <A
-HREF="#AEN1683"
+HREF="#AEN1685"
>Use MS Windows NT as an authentication server</A
></DT
><DT
>10.5.2. <A
-HREF="#AEN1691"
+HREF="#AEN1693"
>Make Samba a member of an MS Windows NT security domain</A
></DT
><DT
>10.5.3. <A
-HREF="#AEN1708"
+HREF="#AEN1710"
>Configure Samba as an authentication server</A
></DT
></DL
></DD
><DT
>10.6. <A
-HREF="#AEN1725"
+HREF="#AEN1727"
>Conclusions</A
></DT
></DL
@@ -7759,53 +7807,53 @@ HREF="#UNIX-PERMISSIONS"
><DL
><DT
>11.1. <A
-HREF="#AEN1746"
+HREF="#AEN1748"
>Viewing and changing UNIX permissions using the NT
security dialogs</A
></DT
><DT
>11.2. <A
-HREF="#AEN1750"
+HREF="#AEN1752"
>How to view file security on a Samba share</A
></DT
><DT
>11.3. <A
-HREF="#AEN1761"
+HREF="#AEN1763"
>Viewing file ownership</A
></DT
><DT
>11.4. <A
-HREF="#AEN1781"
+HREF="#AEN1783"
>Viewing file or directory permissions</A
></DT
><DD
><DL
><DT
>11.4.1. <A
-HREF="#AEN1796"
+HREF="#AEN1798"
>File Permissions</A
></DT
><DT
>11.4.2. <A
-HREF="#AEN1810"
+HREF="#AEN1812"
>Directory Permissions</A
></DT
></DL
></DD
><DT
>11.5. <A
-HREF="#AEN1817"
+HREF="#AEN1819"
>Modifying file or directory permissions</A
></DT
><DT
>11.6. <A
-HREF="#AEN1839"
+HREF="#AEN1841"
>Interaction with the standard Samba create mask
parameters</A
></DT
><DT
>11.7. <A
-HREF="#AEN1903"
+HREF="#AEN1905"
>Interaction with the standard Samba file attribute
mapping</A
></DT
@@ -7821,17 +7869,17 @@ managed authentication</A
><DL
><DT
>12.1. <A
-HREF="#AEN1924"
+HREF="#AEN1926"
>Samba and PAM</A
></DT
><DT
>12.2. <A
-HREF="#AEN1968"
+HREF="#AEN1970"
>Distributed Authentication</A
></DT
><DT
>12.3. <A
-HREF="#AEN1975"
+HREF="#AEN1977"
>PAM Configuration in smb.conf</A
></DT
></DL
@@ -7845,14 +7893,14 @@ HREF="#MSDFS"
><DL
><DT
>13.1. <A
-HREF="#AEN1995"
+HREF="#AEN1997"
>Instructions</A
></DT
><DD
><DL
><DT
>13.1.1. <A
-HREF="#AEN2030"
+HREF="#AEN2032"
>Notes</A
></DT
></DL
@@ -7868,122 +7916,122 @@ HREF="#PRINTING"
><DL
><DT
>14.1. <A
-HREF="#AEN2056"
+HREF="#AEN2058"
>Introduction</A
></DT
><DT
>14.2. <A
-HREF="#AEN2078"
+HREF="#AEN2080"
>Configuration</A
></DT
><DD
><DL
><DT
>14.2.1. <A
-HREF="#AEN2086"
+HREF="#AEN2088"
>Creating [print$]</A
></DT
><DT
>14.2.2. <A
-HREF="#AEN2121"
+HREF="#AEN2123"
>Setting Drivers for Existing Printers</A
></DT
><DT
>14.2.3. <A
-HREF="#AEN2137"
+HREF="#AEN2139"
>Support a large number of printers</A
></DT
><DT
>14.2.4. <A
-HREF="#AEN2148"
+HREF="#AEN2150"
>Adding New Printers via the Windows NT APW</A
></DT
><DT
>14.2.5. <A
-HREF="#AEN2178"
+HREF="#AEN2180"
>Samba and Printer Ports</A
></DT
></DL
></DD
><DT
>14.3. <A
-HREF="#AEN2186"
+HREF="#AEN2188"
>The Imprints Toolset</A
></DT
><DD
><DL
><DT
>14.3.1. <A
-HREF="#AEN2190"
+HREF="#AEN2192"
>What is Imprints?</A
></DT
><DT
>14.3.2. <A
-HREF="#AEN2200"
+HREF="#AEN2202"
>Creating Printer Driver Packages</A
></DT
><DT
>14.3.3. <A
-HREF="#AEN2203"
+HREF="#AEN2205"
>The Imprints server</A
></DT
><DT
>14.3.4. <A
-HREF="#AEN2207"
+HREF="#AEN2209"
>The Installation Client</A
></DT
></DL
></DD
><DT
>14.4. <A
-HREF="#AEN2229"
+HREF="#AEN2231"
>Diagnosis</A
></DT
><DD
><DL
><DT
>14.4.1. <A
-HREF="#AEN2231"
+HREF="#AEN2233"
>Introduction</A
></DT
><DT
>14.4.2. <A
-HREF="#AEN2247"
+HREF="#AEN2249"
>Debugging printer problems</A
></DT
><DT
>14.4.3. <A
-HREF="#AEN2256"
+HREF="#AEN2258"
>What printers do I have?</A
></DT
><DT
>14.4.4. <A
-HREF="#AEN2264"
+HREF="#AEN2266"
>Setting up printcap and print servers</A
></DT
><DT
>14.4.5. <A
-HREF="#AEN2292"
+HREF="#AEN2294"
>Job sent, no output</A
></DT
><DT
>14.4.6. <A
-HREF="#AEN2303"
+HREF="#AEN2305"
>Job sent, strange output</A
></DT
><DT
>14.4.7. <A
-HREF="#AEN2315"
+HREF="#AEN2317"
>Raw PostScript printed</A
></DT
><DT
>14.4.8. <A
-HREF="#AEN2318"
+HREF="#AEN2320"
>Advanced Printing</A
></DT
><DT
>14.4.9. <A
-HREF="#AEN2321"
+HREF="#AEN2323"
>Real debugging</A
></DT
></DL
@@ -7992,234 +8040,287 @@ HREF="#AEN2321"
></DD
><DT
>15. <A
+HREF="#CUPS-PRINTING"
+>CUPS Printing Support</A
+></DT
+><DD
+><DL
+><DT
+>15.1. <A
+HREF="#AEN2343"
+>Introduction</A
+></DT
+><DT
+>15.2. <A
+HREF="#AEN2348"
+>CUPS - RAW Print Through Mode</A
+></DT
+><DT
+>15.3. <A
+HREF="#AEN2403"
+>The CUPS Filter Chains</A
+></DT
+><DT
+>15.4. <A
+HREF="#AEN2442"
+>CUPS Print Drivers and Devices</A
+></DT
+><DD
+><DL
+><DT
+>15.4.1. <A
+HREF="#AEN2449"
+>Further printing steps</A
+></DT
+></DL
+></DD
+><DT
+>15.5. <A
+HREF="#AEN2519"
+>Limiting the number of pages users can print</A
+></DT
+><DT
+>15.6. <A
+HREF="#AEN2608"
+>Advanced Postscript Printing from MS Windows</A
+></DT
+><DT
+>15.7. <A
+HREF="#AEN2623"
+>Auto-Deletion of CUPS spool files</A
+></DT
+></DL
+></DD
+><DT
+>16. <A
HREF="#WINBIND"
>Unified Logons between Windows NT and UNIX using Winbind</A
></DT
><DD
><DL
><DT
->15.1. <A
-HREF="#AEN2362"
+>16.1. <A
+HREF="#AEN2685"
>Abstract</A
></DT
><DT
->15.2. <A
-HREF="#AEN2366"
+>16.2. <A
+HREF="#AEN2689"
>Introduction</A
></DT
><DT
->15.3. <A
-HREF="#AEN2379"
+>16.3. <A
+HREF="#AEN2702"
>What Winbind Provides</A
></DT
><DD
><DL
><DT
->15.3.1. <A
-HREF="#AEN2386"
+>16.3.1. <A
+HREF="#AEN2709"
>Target Uses</A
></DT
></DL
></DD
><DT
->15.4. <A
-HREF="#AEN2390"
+>16.4. <A
+HREF="#AEN2713"
>How Winbind Works</A
></DT
><DD
><DL
><DT
->15.4.1. <A
-HREF="#AEN2395"
+>16.4.1. <A
+HREF="#AEN2718"
>Microsoft Remote Procedure Calls</A
></DT
><DT
->15.4.2. <A
-HREF="#AEN2399"
+>16.4.2. <A
+HREF="#AEN2722"
>Microsoft Active Directory Services</A
></DT
><DT
->15.4.3. <A
-HREF="#AEN2402"
+>16.4.3. <A
+HREF="#AEN2725"
>Name Service Switch</A
></DT
><DT
->15.4.4. <A
-HREF="#AEN2418"
+>16.4.4. <A
+HREF="#AEN2741"
>Pluggable Authentication Modules</A
></DT
><DT
->15.4.5. <A
-HREF="#AEN2426"
+>16.4.5. <A
+HREF="#AEN2749"
>User and Group ID Allocation</A
></DT
><DT
->15.4.6. <A
-HREF="#AEN2430"
+>16.4.6. <A
+HREF="#AEN2753"
>Result Caching</A
></DT
></DL
></DD
><DT
->15.5. <A
-HREF="#AEN2433"
+>16.5. <A
+HREF="#AEN2756"
>Installation and Configuration</A
></DT
><DD
><DL
><DT
->15.5.1. <A
-HREF="#AEN2438"
+>16.5.1. <A
+HREF="#AEN2761"
>Introduction</A
></DT
><DT
->15.5.2. <A
-HREF="#AEN2451"
+>16.5.2. <A
+HREF="#AEN2774"
>Requirements</A
></DT
><DT
->15.5.3. <A
-HREF="#AEN2465"
+>16.5.3. <A
+HREF="#AEN2788"
>Testing Things Out</A
></DT
></DL
></DD
><DT
->15.6. <A
-HREF="#AEN2690"
+>16.6. <A
+HREF="#AEN3013"
>Limitations</A
></DT
><DT
->15.7. <A
-HREF="#AEN2700"
+>16.7. <A
+HREF="#AEN3023"
>Conclusion</A
></DT
></DL
></DD
><DT
->16. <A
+>17. <A
HREF="#IMPROVED-BROWSING"
>Improved browsing in samba</A
></DT
><DD
><DL
><DT
->16.1. <A
-HREF="#AEN2710"
+>17.1. <A
+HREF="#AEN3033"
>Overview of browsing</A
></DT
><DT
->16.2. <A
-HREF="#AEN2715"
+>17.2. <A
+HREF="#AEN3038"
>Browsing support in samba</A
></DT
><DT
->16.3. <A
-HREF="#AEN2723"
+>17.3. <A
+HREF="#AEN3046"
>Problem resolution</A
></DT
><DT
->16.4. <A
-HREF="#AEN2732"
+>17.4. <A
+HREF="#AEN3055"
>Browsing across subnets</A
></DT
><DD
><DL
><DT
->16.4.1. <A
-HREF="#AEN2737"
+>17.4.1. <A
+HREF="#AEN3060"
>How does cross subnet browsing work ?</A
></DT
></DL
></DD
><DT
->16.5. <A
-HREF="#AEN2772"
+>17.5. <A
+HREF="#AEN3095"
>Setting up a WINS server</A
></DT
><DT
->16.6. <A
-HREF="#AEN2791"
+>17.6. <A
+HREF="#AEN3114"
>Setting up Browsing in a WORKGROUP</A
></DT
><DT
->16.7. <A
-HREF="#AEN2809"
+>17.7. <A
+HREF="#AEN3132"
>Setting up Browsing in a DOMAIN</A
></DT
><DT
->16.8. <A
-HREF="#AEN2819"
+>17.8. <A
+HREF="#AEN3142"
>Forcing samba to be the master</A
></DT
><DT
->16.9. <A
-HREF="#AEN2828"
+>17.9. <A
+HREF="#AEN3151"
>Making samba the domain master</A
></DT
><DT
->16.10. <A
-HREF="#AEN2846"
+>17.10. <A
+HREF="#AEN3169"
>Note about broadcast addresses</A
></DT
><DT
->16.11. <A
-HREF="#AEN2849"
+>17.11. <A
+HREF="#AEN3172"
>Multiple interfaces</A
></DT
></DL
></DD
><DT
->17. <A
+>18. <A
HREF="#VFS"
>Stackable VFS modules</A
></DT
><DD
><DL
><DT
->17.1. <A
-HREF="#AEN2867"
+>18.1. <A
+HREF="#AEN3190"
>Introduction and configuration</A
></DT
><DT
->17.2. <A
-HREF="#AEN2876"
+>18.2. <A
+HREF="#AEN3199"
>Included modules</A
></DT
><DD
><DL
><DT
->17.2.1. <A
-HREF="#AEN2878"
+>18.2.1. <A
+HREF="#AEN3201"
>audit</A
></DT
><DT
->17.2.2. <A
-HREF="#AEN2886"
+>18.2.2. <A
+HREF="#AEN3209"
>recycle</A
></DT
><DT
->17.2.3. <A
-HREF="#AEN2923"
+>18.2.3. <A
+HREF="#AEN3246"
>netatalk</A
></DT
></DL
></DD
><DT
->17.3. <A
-HREF="#AEN2930"
+>18.3. <A
+HREF="#AEN3253"
>VFS modules available elsewhere</A
></DT
><DD
><DL
><DT
->17.3.1. <A
-HREF="#AEN2934"
+>18.3.1. <A
+HREF="#AEN3257"
>DatabaseFS</A
></DT
><DT
->17.3.2. <A
-HREF="#AEN2942"
+>18.3.2. <A
+HREF="#AEN3265"
>vscan</A
></DT
></DL
@@ -8227,171 +8328,171 @@ HREF="#AEN2942"
></DL
></DD
><DT
->18. <A
+>19. <A
HREF="#GROUPMAPPING"
>Group mapping HOWTO</A
></DT
><DT
->19. <A
+>20. <A
HREF="#SPEED"
>Samba performance issues</A
></DT
><DD
><DL
><DT
->19.1. <A
-HREF="#AEN2997"
+>20.1. <A
+HREF="#AEN3320"
>Comparisons</A
></DT
><DT
->19.2. <A
-HREF="#AEN3003"
+>20.2. <A
+HREF="#AEN3326"
>Socket options</A
></DT
><DT
->19.3. <A
-HREF="#AEN3010"
+>20.3. <A
+HREF="#AEN3333"
>Read size</A
></DT
><DT
->19.4. <A
-HREF="#AEN3015"
+>20.4. <A
+HREF="#AEN3338"
>Max xmit</A
></DT
><DT
->19.5. <A
-HREF="#AEN3020"
+>20.5. <A
+HREF="#AEN3343"
>Log level</A
></DT
><DT
->19.6. <A
-HREF="#AEN3023"
+>20.6. <A
+HREF="#AEN3346"
>Read raw</A
></DT
><DT
->19.7. <A
-HREF="#AEN3028"
+>20.7. <A
+HREF="#AEN3351"
>Write raw</A
></DT
><DT
->19.8. <A
-HREF="#AEN3032"
+>20.8. <A
+HREF="#AEN3355"
>Slow Clients</A
></DT
><DT
->19.9. <A
-HREF="#AEN3036"
+>20.9. <A
+HREF="#AEN3359"
>Slow Logins</A
></DT
><DT
->19.10. <A
-HREF="#AEN3039"
+>20.10. <A
+HREF="#AEN3362"
>Client tuning</A
></DT
></DL
></DD
><DT
->20. <A
+>21. <A
HREF="#GROUPPROFILES"
>Creating Group Prolicy Files</A
></DT
><DD
><DL
><DT
->20.1. <A
-HREF="#AEN3087"
+>21.1. <A
+HREF="#AEN3410"
>Windows '9x</A
></DT
><DT
->20.2. <A
-HREF="#AEN3097"
+>21.2. <A
+HREF="#AEN3420"
>Windows NT 4</A
></DT
><DD
><DL
><DT
->20.2.1. <A
-HREF="#AEN3120"
+>21.2.1. <A
+HREF="#AEN3443"
>Side bar Notes</A
></DT
><DT
->20.2.2. <A
-HREF="#AEN3124"
+>21.2.2. <A
+HREF="#AEN3447"
>Mandatory profiles</A
></DT
><DT
->20.2.3. <A
-HREF="#AEN3127"
+>21.2.3. <A
+HREF="#AEN3450"
>moveuser.exe</A
></DT
><DT
->20.2.4. <A
-HREF="#AEN3130"
+>21.2.4. <A
+HREF="#AEN3453"
>Get SID</A
></DT
></DL
></DD
><DT
->20.3. <A
-HREF="#AEN3135"
+>21.3. <A
+HREF="#AEN3458"
>Windows 2000/XP</A
></DT
></DL
></DD
><DT
->21. <A
+>22. <A
HREF="#SECURING-SAMBA"
>Securing Samba</A
></DT
><DD
><DL
><DT
->21.1. <A
-HREF="#AEN3216"
+>22.1. <A
+HREF="#AEN3539"
>Introduction</A
></DT
><DT
->21.2. <A
-HREF="#AEN3219"
+>22.2. <A
+HREF="#AEN3542"
>Using host based protection</A
></DT
><DT
->21.3. <A
-HREF="#AEN3226"
+>22.3. <A
+HREF="#AEN3549"
>Using interface protection</A
></DT
><DT
->21.4. <A
-HREF="#AEN3235"
+>22.4. <A
+HREF="#AEN3558"
>Using a firewall</A
></DT
><DT
->21.5. <A
-HREF="#AEN3242"
+>22.5. <A
+HREF="#AEN3565"
>Using a IPC$ share deny</A
></DT
><DT
->21.6. <A
-HREF="#AEN3251"
+>22.6. <A
+HREF="#AEN3574"
>Upgrading Samba</A
></DT
></DL
></DD
><DT
->22. <A
+>23. <A
HREF="#UNICODE"
>Unicode/Charsets</A
></DT
><DD
><DL
><DT
->22.1. <A
-HREF="#AEN3265"
+>23.1. <A
+HREF="#AEN3588"
>What are charsets and unicode?</A
></DT
><DT
->22.2. <A
-HREF="#AEN3274"
+>23.2. <A
+HREF="#AEN3597"
>Samba and charsets</A
></DT
></DL
@@ -8411,7 +8512,7 @@ CLASS="SECT1"
><H2
CLASS="SECT1"
><A
-NAME="AEN1515"
+NAME="AEN1517"
>10.1. Agenda</A
></H2
><P
@@ -8478,7 +8579,7 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN1537"
+NAME="AEN1539"
>10.2. Name Resolution in a pure Unix/Linux world</A
></H2
><P
@@ -8520,7 +8621,7 @@ CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
-NAME="AEN1553"
+NAME="AEN1555"
>10.2.1. <TT
CLASS="FILENAME"
>/etc/hosts</TT
@@ -8601,7 +8702,7 @@ CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
-NAME="AEN1569"
+NAME="AEN1571"
>10.2.2. <TT
CLASS="FILENAME"
>/etc/resolv.conf</TT
@@ -8639,7 +8740,7 @@ CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
-NAME="AEN1580"
+NAME="AEN1582"
>10.2.3. <TT
CLASS="FILENAME"
>/etc/host.conf</TT
@@ -8668,7 +8769,7 @@ CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
-NAME="AEN1588"
+NAME="AEN1590"
>10.2.4. <TT
CLASS="FILENAME"
>/etc/nsswitch.conf</TT
@@ -8737,7 +8838,7 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN1600"
+NAME="AEN1602"
>10.3. Name resolution as used within MS Windows networking</A
></H2
><P
@@ -8822,7 +8923,7 @@ CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
-NAME="AEN1612"
+NAME="AEN1614"
>10.3.1. The NetBIOS Name Cache</A
></H3
><P
@@ -8849,7 +8950,7 @@ CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
-NAME="AEN1617"
+NAME="AEN1619"
>10.3.2. The LMHOSTS file</A
></H3
><P
@@ -8952,7 +9053,7 @@ CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
-NAME="AEN1625"
+NAME="AEN1627"
>10.3.3. HOSTS file</A
></H3
><P
@@ -8974,7 +9075,7 @@ CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
-NAME="AEN1630"
+NAME="AEN1632"
>10.3.4. DNS Lookup</A
></H3
><P
@@ -8994,7 +9095,7 @@ CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
-NAME="AEN1633"
+NAME="AEN1635"
>10.3.5. WINS Lookup</A
></H3
><P
@@ -9035,7 +9136,7 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN1645"
+NAME="AEN1647"
>10.4. How browsing functions and how to deploy stable and
dependable browsing using Samba</A
></H2
@@ -9102,7 +9203,7 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN1655"
+NAME="AEN1657"
>10.5. MS Windows security options and how to configure
Samba for seemless integration</A
></H2
@@ -9229,7 +9330,7 @@ CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
-NAME="AEN1683"
+NAME="AEN1685"
>10.5.1. Use MS Windows NT as an authentication server</A
></H3
><P
@@ -9265,7 +9366,7 @@ CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
-NAME="AEN1691"
+NAME="AEN1693"
>10.5.2. Make Samba a member of an MS Windows NT security domain</A
></H3
><P
@@ -9328,7 +9429,7 @@ CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
-NAME="AEN1708"
+NAME="AEN1710"
>10.5.3. Configure Samba as an authentication server</A
></H3
><P
@@ -9365,7 +9466,7 @@ CLASS="SECT3"
><HR><H4
CLASS="SECT3"
><A
-NAME="AEN1715"
+NAME="AEN1717"
>10.5.3.1. Users</A
></H4
><P
@@ -9388,7 +9489,7 @@ CLASS="SECT3"
><HR><H4
CLASS="SECT3"
><A
-NAME="AEN1720"
+NAME="AEN1722"
>10.5.3.2. MS Windows NT Machine Accounts</A
></H4
><P
@@ -9409,7 +9510,7 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN1725"
+NAME="AEN1727"
>10.6. Conclusions</A
></H2
><P
@@ -9453,7 +9554,7 @@ CLASS="SECT1"
><H2
CLASS="SECT1"
><A
-NAME="AEN1746"
+NAME="AEN1748"
>11.1. Viewing and changing UNIX permissions using the NT
security dialogs</A
></H2
@@ -9472,7 +9573,7 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN1750"
+NAME="AEN1752"
>11.2. How to view file security on a Samba share</A
></H2
><P
@@ -9542,7 +9643,7 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN1761"
+NAME="AEN1763"
>11.3. Viewing file ownership</A
></H2
><P
@@ -9628,7 +9729,7 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN1781"
+NAME="AEN1783"
>11.4. Viewing file or directory permissions</A
></H2
><P
@@ -9682,7 +9783,7 @@ CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
-NAME="AEN1796"
+NAME="AEN1798"
>11.4.1. File Permissions</A
></H3
><P
@@ -9744,7 +9845,7 @@ CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
-NAME="AEN1810"
+NAME="AEN1812"
>11.4.2. Directory Permissions</A
></H3
><P
@@ -9776,7 +9877,7 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN1817"
+NAME="AEN1819"
>11.5. Modifying file or directory permissions</A
></H2
><P
@@ -9872,7 +9973,7 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN1839"
+NAME="AEN1841"
>11.6. Interaction with the standard Samba create mask
parameters</A
></H2
@@ -10093,7 +10194,7 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN1903"
+NAME="AEN1905"
>11.7. Interaction with the standard Samba file attribute
mapping</A
></H2
@@ -10149,7 +10250,7 @@ CLASS="SECT1"
><H2
CLASS="SECT1"
><A
-NAME="AEN1924"
+NAME="AEN1926"
>12.1. Samba and PAM</A
></H2
><P
@@ -10363,7 +10464,7 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN1968"
+NAME="AEN1970"
>12.2. Distributed Authentication</A
></H2
><P
@@ -10396,7 +10497,7 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN1975"
+NAME="AEN1977"
>12.3. PAM Configuration in smb.conf</A
></H2
><P
@@ -10444,7 +10545,7 @@ CLASS="SECT1"
><H2
CLASS="SECT1"
><A
-NAME="AEN1995"
+NAME="AEN1997"
>13.1. Instructions</A
></H2
><P
@@ -10576,7 +10677,7 @@ CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
-NAME="AEN2030"
+NAME="AEN2032"
>13.1.1. Notes</A
></H3
><P
@@ -10617,7 +10718,7 @@ CLASS="SECT1"
><H2
CLASS="SECT1"
><A
-NAME="AEN2056"
+NAME="AEN2058"
>14.1. Introduction</A
></H2
><P
@@ -10700,7 +10801,7 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN2078"
+NAME="AEN2080"
>14.2. Configuration</A
></H2
><DIV
@@ -10762,7 +10863,7 @@ CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
-NAME="AEN2086"
+NAME="AEN2088"
>14.2.1. Creating [print$]</A
></H3
><P
@@ -10979,7 +11080,7 @@ CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
-NAME="AEN2121"
+NAME="AEN2123"
>14.2.2. Setting Drivers for Existing Printers</A
></H3
><P
@@ -11051,7 +11152,7 @@ CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
-NAME="AEN2137"
+NAME="AEN2139"
>14.2.3. Support a large number of printers</A
></H3
><P
@@ -11117,7 +11218,7 @@ CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
-NAME="AEN2148"
+NAME="AEN2150"
>14.2.4. Adding New Printers via the Windows NT APW</A
></H3
><P
@@ -11272,7 +11373,7 @@ CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
-NAME="AEN2178"
+NAME="AEN2180"
>14.2.5. Samba and Printer Ports</A
></H3
><P
@@ -11307,7 +11408,7 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN2186"
+NAME="AEN2188"
>14.3. The Imprints Toolset</A
></H2
><P
@@ -11325,7 +11426,7 @@ CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
-NAME="AEN2190"
+NAME="AEN2192"
>14.3.1. What is Imprints?</A
></H3
><P
@@ -11357,7 +11458,7 @@ CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
-NAME="AEN2200"
+NAME="AEN2202"
>14.3.2. Creating Printer Driver Packages</A
></H3
><P
@@ -11373,7 +11474,7 @@ CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
-NAME="AEN2203"
+NAME="AEN2205"
>14.3.3. The Imprints server</A
></H3
><P
@@ -11397,7 +11498,7 @@ CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
-NAME="AEN2207"
+NAME="AEN2209"
>14.3.4. The Installation Client</A
></H3
><P
@@ -11491,7 +11592,7 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN2229"
+NAME="AEN2231"
>14.4. Diagnosis</A
></H2
><DIV
@@ -11499,7 +11600,7 @@ CLASS="SECT2"
><H3
CLASS="SECT2"
><A
-NAME="AEN2231"
+NAME="AEN2233"
>14.4.1. Introduction</A
></H3
><P
@@ -11574,7 +11675,7 @@ CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
-NAME="AEN2247"
+NAME="AEN2249"
>14.4.2. Debugging printer problems</A
></H3
><P
@@ -11631,7 +11732,7 @@ CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
-NAME="AEN2256"
+NAME="AEN2258"
>14.4.3. What printers do I have?</A
></H3
><P
@@ -11660,7 +11761,7 @@ CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
-NAME="AEN2264"
+NAME="AEN2266"
>14.4.4. Setting up printcap and print servers</A
></H3
><P
@@ -11744,7 +11845,7 @@ CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
-NAME="AEN2292"
+NAME="AEN2294"
>14.4.5. Job sent, no output</A
></H3
><P
@@ -11789,7 +11890,7 @@ CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
-NAME="AEN2303"
+NAME="AEN2305"
>14.4.6. Job sent, strange output</A
></H3
><P
@@ -11835,7 +11936,7 @@ CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
-NAME="AEN2315"
+NAME="AEN2317"
>14.4.7. Raw PostScript printed</A
></H3
><P
@@ -11850,7 +11951,7 @@ CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
-NAME="AEN2318"
+NAME="AEN2320"
>14.4.8. Advanced Printing</A
></H3
><P
@@ -11866,7 +11967,7 @@ CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
-NAME="AEN2321"
+NAME="AEN2323"
>14.4.9. Real debugging</A
></H3
><P
@@ -11879,16 +11980,1882 @@ the bug guns, system tracing. See Tracing.txt in this directory.</P
CLASS="CHAPTER"
><HR><H1
><A
+NAME="CUPS-PRINTING"
+></A
+>Chapter 15. CUPS Printing Support</H1
+><DIV
+CLASS="SECT1"
+><H2
+CLASS="SECT1"
+><A
+NAME="AEN2343"
+>15.1. Introduction</A
+></H2
+><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.
+/para&#62;&#13;</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
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN2348"
+>15.2. CUPS - RAW Print Through Mode</A
+></H2
+><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
+><P
+></P
+></LI
+><LI
+><P
+><TT
+CLASS="FILENAME"
+>/etc/cups/mime.convs</TT
+></P
+><P
+></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 smb.conf 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 smb.conf (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 "&#60;04&#62;%".</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
+("&#60;1B&#62;%-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"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN2403"
+>15.3. The CUPS Filter Chains</A
+></H2
+><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"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN2442"
+>15.4. CUPS Print Drivers and Devices</A
+></H2
+><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"
+><HR><H3
+CLASS="SECT2"
+><A
+NAME="AEN2449"
+>15.4.1. Further printing steps</A
+></H3
+><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
+>&#13;</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
+>&#13;</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"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN2519"
+>15.5. Limiting the number of pages users can print</A
+></H2
+><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
+>&#62;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
+><PRE
+CLASS="PROGRAMLISTING"
+> * Printer name
+ * User name
+ * Job ID
+ * Time of printing
+ * the page number
+ * the number of copies
+ * a billing info string (optional)</PRE
+></P
+><P
+>Here is an extract of my CUPS server's page_log file to illustrate
+the format and included items:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+> 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</PRE
+></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
+><PRE
+CLASS="PROGRAMLISTING"
+> cups-samba.install
+ cups-samba.license
+ cups-samba.readme
+ cups-samba.remove
+ cups-samba.ss</PRE
+></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
+><PRE
+CLASS="PROGRAMLISTING"
+> cupsdrvr.dll
+ cupsui.dll
+ cups.hlp</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
+>ATTENTION: 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
+><PRE
+CLASS="PROGRAMLISTING"
+> cp /usr/share/drivers/cups.hlp /usr/share/cups/drivers/</PRE
+></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
+>NOTE 1: 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
+>NOTE 2: 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
+>NOTE 3: 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"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN2608"
+>15.6. Advanced Postscript Printing from MS Windows</A
+></H2
+><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"
+><HR><H2
+CLASS="SECT1"
+><A
+NAME="AEN2623"
+>15.7. Auto-Deletion of CUPS spool files</A
+></H2
+><P
+>Samba print files pass thru two "spool" directories. One the incoming directory
+managed by Samba, (set eg: in the "path = /var/spool/samba" directive in the [printers]
+section of "smb.conf"). 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
+><PRE
+CLASS="PROGRAMLISTING"
+> http://localhost:631/sam.html#PreserveJobFiles and
+ http://localhost:631/sam.html#PreserveJobHistory and
+ http://localhost:631/sam.html#MaxJobs</PRE
+><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-smbd which is compiled against "libcups" (Check on Linux by running "ldd `which smbd`")
+ </TD
+></TR
+><TR
+><TD
+> a Samba-smb.conf setting of "printing = cups"
+ </TD
+></TR
+><TR
+><TD
+> another Samba-smb.conf setting of "printcap = cups"
+ </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
+><PRE
+CLASS="PROGRAMLISTING"
+> grep -v ^# /etc/cups/cupsd.conf | grep -v ^$
+ grep -v ^# /etc/samba/smb.conf | grep -v ^$ | grep -v "^;"</PRE
+></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="CHAPTER"
+><HR><H1
+><A
NAME="WINBIND"
></A
->Chapter 15. Unified Logons between Windows NT and UNIX using Winbind</H1
+>Chapter 16. Unified Logons between Windows NT and UNIX using Winbind</H1
><DIV
CLASS="SECT1"
><H2
CLASS="SECT1"
><A
-NAME="AEN2362"
->15.1. Abstract</A
+NAME="AEN2685"
+>16.1. Abstract</A
></H2
><P
>Integration of UNIX and Microsoft Windows NT through
@@ -11914,8 +13881,8 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN2366"
->15.2. Introduction</A
+NAME="AEN2689"
+>16.2. Introduction</A
></H2
><P
>It is well known that UNIX and Microsoft Windows NT have
@@ -11968,8 +13935,8 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN2379"
->15.3. What Winbind Provides</A
+NAME="AEN2702"
+>16.3. What Winbind Provides</A
></H2
><P
>Winbind unifies UNIX and Windows NT account management by
@@ -12010,8 +13977,8 @@ CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
-NAME="AEN2386"
->15.3.1. Target Uses</A
+NAME="AEN2709"
+>16.3.1. Target Uses</A
></H3
><P
>Winbind is targeted at organizations that have an
@@ -12034,8 +14001,8 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN2390"
->15.4. How Winbind Works</A
+NAME="AEN2713"
+>16.4. How Winbind Works</A
></H2
><P
>The winbind system is designed around a client/server
@@ -12054,8 +14021,8 @@ CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
-NAME="AEN2395"
->15.4.1. Microsoft Remote Procedure Calls</A
+NAME="AEN2718"
+>16.4.1. Microsoft Remote Procedure Calls</A
></H3
><P
>Over the last few years, efforts have been underway
@@ -12080,8 +14047,8 @@ CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
-NAME="AEN2399"
->15.4.2. Microsoft Active Directory Services</A
+NAME="AEN2722"
+>16.4.2. Microsoft Active Directory Services</A
></H3
><P
> Since late 2001, Samba has gained the ability to
@@ -12099,8 +14066,8 @@ CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
-NAME="AEN2402"
->15.4.3. Name Service Switch</A
+NAME="AEN2725"
+>16.4.3. Name Service Switch</A
></H3
><P
>The Name Service Switch, or NSS, is a feature that is
@@ -12179,8 +14146,8 @@ CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
-NAME="AEN2418"
->15.4.4. Pluggable Authentication Modules</A
+NAME="AEN2741"
+>16.4.4. Pluggable Authentication Modules</A
></H3
><P
>Pluggable Authentication Modules, also known as PAM,
@@ -12228,8 +14195,8 @@ CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
-NAME="AEN2426"
->15.4.5. User and Group ID Allocation</A
+NAME="AEN2749"
+>16.4.5. User and Group ID Allocation</A
></H3
><P
>When a user or group is created under Windows NT
@@ -12254,8 +14221,8 @@ CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
-NAME="AEN2430"
->15.4.6. Result Caching</A
+NAME="AEN2753"
+>16.4.6. Result Caching</A
></H3
><P
>An active system can generate a lot of user and group
@@ -12277,8 +14244,8 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN2433"
->15.5. Installation and Configuration</A
+NAME="AEN2756"
+>16.5. Installation and Configuration</A
></H2
><P
>Many thanks to John Trostel <A
@@ -12296,8 +14263,8 @@ CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
-NAME="AEN2438"
->15.5.1. Introduction</A
+NAME="AEN2761"
+>16.5.1. Introduction</A
></H3
><P
>This HOWTO describes the procedures used to get winbind up and
@@ -12355,8 +14322,8 @@ CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
-NAME="AEN2451"
->15.5.2. Requirements</A
+NAME="AEN2774"
+>16.5.2. Requirements</A
></H3
><P
>If you have a samba configuration file that you are currently
@@ -12425,8 +14392,8 @@ CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
-NAME="AEN2465"
->15.5.3. Testing Things Out</A
+NAME="AEN2788"
+>16.5.3. Testing Things Out</A
></H3
><P
>Before starting, it is probably best to kill off all the SAMBA
@@ -12470,8 +14437,8 @@ CLASS="SECT3"
><HR><H4
CLASS="SECT3"
><A
-NAME="AEN2476"
->15.5.3.1. Configure and compile SAMBA</A
+NAME="AEN2799"
+>16.5.3.1. Configure and compile SAMBA</A
></H4
><P
>The configuration and compilation of SAMBA is pretty straightforward.
@@ -12536,8 +14503,8 @@ CLASS="SECT3"
><HR><H4
CLASS="SECT3"
><A
-NAME="AEN2495"
->15.5.3.2. Configure <TT
+NAME="AEN2818"
+>16.5.3.2. Configure <TT
CLASS="FILENAME"
>nsswitch.conf</TT
> and the
@@ -12641,8 +14608,8 @@ CLASS="SECT3"
><HR><H4
CLASS="SECT3"
><A
-NAME="AEN2528"
->15.5.3.3. Configure smb.conf</A
+NAME="AEN2851"
+>16.5.3.3. Configure smb.conf</A
></H4
><P
>Several parameters are needed in the smb.conf file to control
@@ -12716,8 +14683,8 @@ CLASS="SECT3"
><HR><H4
CLASS="SECT3"
><A
-NAME="AEN2544"
->15.5.3.4. Join the SAMBA server to the PDC domain</A
+NAME="AEN2867"
+>16.5.3.4. Join the SAMBA server to the PDC domain</A
></H4
><P
>Enter the following command to make the SAMBA server join the
@@ -12754,8 +14721,8 @@ CLASS="SECT3"
><HR><H4
CLASS="SECT3"
><A
-NAME="AEN2555"
->15.5.3.5. Start up the winbindd daemon and test it!</A
+NAME="AEN2878"
+>16.5.3.5. Start up the winbindd daemon and test it!</A
></H4
><P
>Eventually, you will want to modify your smb startup script to
@@ -12890,16 +14857,16 @@ CLASS="SECT3"
><HR><H4
CLASS="SECT3"
><A
-NAME="AEN2595"
->15.5.3.6. Fix the init.d startup scripts</A
+NAME="AEN2918"
+>16.5.3.6. Fix the init.d startup scripts</A
></H4
><DIV
CLASS="SECT4"
><H5
CLASS="SECT4"
><A
-NAME="AEN2597"
->15.5.3.6.1. Linux</A
+NAME="AEN2920"
+>16.5.3.6.1. Linux</A
></H5
><P
>The <B
@@ -13008,8 +14975,8 @@ CLASS="SECT4"
><HR><H5
CLASS="SECT4"
><A
-NAME="AEN2617"
->15.5.3.6.2. Solaris</A
+NAME="AEN2940"
+>16.5.3.6.2. Solaris</A
></H5
><P
>On solaris, you need to modify the
@@ -13092,8 +15059,8 @@ CLASS="SECT4"
><HR><H5
CLASS="SECT4"
><A
-NAME="AEN2627"
->15.5.3.6.3. Restarting</A
+NAME="AEN2950"
+>16.5.3.6.3. Restarting</A
></H5
><P
>If you restart the <B
@@ -13116,8 +15083,8 @@ CLASS="SECT3"
><HR><H4
CLASS="SECT3"
><A
-NAME="AEN2633"
->15.5.3.7. Configure Winbind and PAM</A
+NAME="AEN2956"
+>16.5.3.7. Configure Winbind and PAM</A
></H4
><P
>If you have made it this far, you know that winbindd and samba are working
@@ -13174,8 +15141,8 @@ CLASS="SECT4"
><HR><H5
CLASS="SECT4"
><A
-NAME="AEN2650"
->15.5.3.7.1. Linux/FreeBSD-specific PAM configuration</A
+NAME="AEN2973"
+>16.5.3.7.1. Linux/FreeBSD-specific PAM configuration</A
></H5
><P
>The <TT
@@ -13303,8 +15270,8 @@ CLASS="SECT4"
><HR><H5
CLASS="SECT4"
><A
-NAME="AEN2683"
->15.5.3.7.2. Solaris-specific configuration</A
+NAME="AEN3006"
+>16.5.3.7.2. Solaris-specific configuration</A
></H5
><P
>The /etc/pam.conf needs to be changed. I changed this file so that my Domain
@@ -13390,8 +15357,8 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN2690"
->15.6. Limitations</A
+NAME="AEN3013"
+>16.6. Limitations</A
></H2
><P
>Winbind has a number of limitations in its current
@@ -13432,8 +15399,8 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN2700"
->15.7. Conclusion</A
+NAME="AEN3023"
+>16.7. Conclusion</A
></H2
><P
>The winbind system, through the use of the Name Service
@@ -13450,14 +15417,14 @@ CLASS="CHAPTER"
><A
NAME="IMPROVED-BROWSING"
></A
->Chapter 16. Improved browsing in samba</H1
+>Chapter 17. Improved browsing in samba</H1
><DIV
CLASS="SECT1"
><H2
CLASS="SECT1"
><A
-NAME="AEN2710"
->16.1. Overview of browsing</A
+NAME="AEN3033"
+>17.1. Overview of browsing</A
></H2
><P
>SMB networking provides a mechanism by which clients can access a list
@@ -13485,8 +15452,8 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN2715"
->16.2. Browsing support in samba</A
+NAME="AEN3038"
+>17.2. Browsing support in samba</A
></H2
><P
>Samba facilitates browsing. The browsing is supported by nmbd
@@ -13528,8 +15495,8 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN2723"
->16.3. Problem resolution</A
+NAME="AEN3046"
+>17.3. Problem resolution</A
></H2
><P
>If something doesn't work then hopefully the log.nmb file will help
@@ -13575,8 +15542,8 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN2732"
->16.4. Browsing across subnets</A
+NAME="AEN3055"
+>17.4. Browsing across subnets</A
></H2
><P
>Since the release of Samba 1.9.17(alpha1) Samba has been
@@ -13606,8 +15573,8 @@ CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
-NAME="AEN2737"
->16.4.1. How does cross subnet browsing work ?</A
+NAME="AEN3060"
+>17.4.1. How does cross subnet browsing work ?</A
></H3
><P
>Cross subnet browsing is a complicated dance, containing multiple
@@ -13817,8 +15784,8 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN2772"
->16.5. Setting up a WINS server</A
+NAME="AEN3095"
+>17.5. Setting up a WINS server</A
></H2
><P
>Either a Samba machine or a Windows NT Server machine may be set up
@@ -13900,8 +15867,8 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN2791"
->16.6. Setting up Browsing in a WORKGROUP</A
+NAME="AEN3114"
+>17.6. Setting up Browsing in a WORKGROUP</A
></H2
><P
>To set up cross subnet browsing on a network containing machines
@@ -13985,8 +15952,8 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN2809"
->16.7. Setting up Browsing in a DOMAIN</A
+NAME="AEN3132"
+>17.7. Setting up Browsing in a DOMAIN</A
></H2
><P
>If you are adding Samba servers to a Windows NT Domain then
@@ -14036,8 +16003,8 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN2819"
->16.8. Forcing samba to be the master</A
+NAME="AEN3142"
+>17.8. Forcing samba to be the master</A
></H2
><P
>Who becomes the "master browser" is determined by an election process
@@ -14084,8 +16051,8 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN2828"
->16.9. Making samba the domain master</A
+NAME="AEN3151"
+>17.9. Making samba the domain master</A
></H2
><P
>The domain master is responsible for collating the browse lists of
@@ -14157,8 +16124,8 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN2846"
->16.10. Note about broadcast addresses</A
+NAME="AEN3169"
+>17.10. Note about broadcast addresses</A
></H2
><P
>If your network uses a "0" based broadcast address (for example if it
@@ -14171,8 +16138,8 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN2849"
->16.11. Multiple interfaces</A
+NAME="AEN3172"
+>17.11. Multiple interfaces</A
></H2
><P
>Samba now supports machines with multiple network interfaces. If you
@@ -14186,14 +16153,14 @@ CLASS="CHAPTER"
><A
NAME="VFS"
></A
->Chapter 17. Stackable VFS modules</H1
+>Chapter 18. Stackable VFS modules</H1
><DIV
CLASS="SECT1"
><H2
CLASS="SECT1"
><A
-NAME="AEN2867"
->17.1. Introduction and configuration</A
+NAME="AEN3190"
+>18.1. Introduction and configuration</A
></H2
><P
>Since samba 3.0, samba supports stackable VFS(Virtual File System) modules.
@@ -14233,16 +16200,16 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN2876"
->17.2. Included modules</A
+NAME="AEN3199"
+>18.2. Included modules</A
></H2
><DIV
CLASS="SECT2"
><H3
CLASS="SECT2"
><A
-NAME="AEN2878"
->17.2.1. audit</A
+NAME="AEN3201"
+>18.2.1. audit</A
></H3
><P
>A simple module to audit file access to the syslog
@@ -14279,8 +16246,8 @@ CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
-NAME="AEN2886"
->17.2.2. recycle</A
+NAME="AEN3209"
+>18.2.2. recycle</A
></H3
><P
>A recycle-bin like modules. When used any unlink call
@@ -14350,8 +16317,8 @@ CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
-NAME="AEN2923"
->17.2.3. netatalk</A
+NAME="AEN3246"
+>18.2.3. netatalk</A
></H3
><P
>A netatalk module, that will ease co-existence of samba and
@@ -14383,8 +16350,8 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN2930"
->17.3. VFS modules available elsewhere</A
+NAME="AEN3253"
+>18.3. VFS modules available elsewhere</A
></H2
><P
>This section contains a listing of various other VFS modules that
@@ -14399,8 +16366,8 @@ CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
-NAME="AEN2934"
->17.3.1. DatabaseFS</A
+NAME="AEN3257"
+>18.3.1. DatabaseFS</A
></H3
><P
>URL: <A
@@ -14433,8 +16400,8 @@ CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
-NAME="AEN2942"
->17.3.2. vscan</A
+NAME="AEN3265"
+>18.3.2. vscan</A
></H3
><P
>URL: <A
@@ -14457,7 +16424,7 @@ CLASS="CHAPTER"
><A
NAME="GROUPMAPPING"
></A
->Chapter 18. Group mapping HOWTO</H1
+>Chapter 19. Group mapping HOWTO</H1
><P
>
Starting with Samba 3.0 alpha 2, a new group mapping function is available. The
@@ -14558,14 +16525,14 @@ CLASS="CHAPTER"
><A
NAME="SPEED"
></A
->Chapter 19. Samba performance issues</H1
+>Chapter 20. Samba performance issues</H1
><DIV
CLASS="SECT1"
><H2
CLASS="SECT1"
><A
-NAME="AEN2997"
->19.1. Comparisons</A
+NAME="AEN3320"
+>20.1. Comparisons</A
></H2
><P
>The Samba server uses TCP to talk to the client. Thus if you are
@@ -14595,8 +16562,8 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN3003"
->19.2. Socket options</A
+NAME="AEN3326"
+>20.2. Socket options</A
></H2
><P
>There are a number of socket options that can greatly affect the
@@ -14623,8 +16590,8 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN3010"
->19.3. Read size</A
+NAME="AEN3333"
+>20.3. Read size</A
></H2
><P
>The option "read size" affects the overlap of disk reads/writes with
@@ -14649,8 +16616,8 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN3015"
->19.4. Max xmit</A
+NAME="AEN3338"
+>20.4. Max xmit</A
></H2
><P
>At startup the client and server negotiate a "maximum transmit" size,
@@ -14672,8 +16639,8 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN3020"
->19.5. Log level</A
+NAME="AEN3343"
+>20.5. Log level</A
></H2
><P
>If you set the log level (also known as "debug level") higher than 2
@@ -14686,8 +16653,8 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN3023"
->19.6. Read raw</A
+NAME="AEN3346"
+>20.6. Read raw</A
></H2
><P
>The "read raw" operation is designed to be an optimised, low-latency
@@ -14708,8 +16675,8 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN3028"
->19.7. Write raw</A
+NAME="AEN3351"
+>20.7. Write raw</A
></H2
><P
>The "write raw" operation is designed to be an optimised, low-latency
@@ -14725,8 +16692,8 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN3032"
->19.8. Slow Clients</A
+NAME="AEN3355"
+>20.8. Slow Clients</A
></H2
><P
>One person has reported that setting the protocol to COREPLUS rather
@@ -14742,8 +16709,8 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN3036"
->19.9. Slow Logins</A
+NAME="AEN3359"
+>20.9. Slow Logins</A
></H2
><P
>Slow logins are almost always due to the password checking time. Using
@@ -14755,8 +16722,8 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN3039"
->19.10. Client tuning</A
+NAME="AEN3362"
+>20.10. Client tuning</A
></H2
><P
>Often a speed problem can be traced to the client. The client (for
@@ -14863,14 +16830,14 @@ CLASS="CHAPTER"
><A
NAME="GROUPPROFILES"
></A
->Chapter 20. Creating Group Prolicy Files</H1
+>Chapter 21. Creating Group Prolicy Files</H1
><DIV
CLASS="SECT1"
><H2
CLASS="SECT1"
><A
-NAME="AEN3087"
->20.1. Windows '9x</A
+NAME="AEN3410"
+>21.1. Windows '9x</A
></H2
><P
>You need the Win98 Group Policy Editor to
@@ -14912,8 +16879,8 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN3097"
->20.2. Windows NT 4</A
+NAME="AEN3420"
+>21.2. Windows NT 4</A
></H2
><P
>Unfortunately, the Resource Kit info is Win NT4 or 200x specific.</P
@@ -14993,8 +16960,8 @@ CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
-NAME="AEN3120"
->20.2.1. Side bar Notes</A
+NAME="AEN3443"
+>21.2.1. Side bar Notes</A
></H3
><P
>You should obtain the SID of your NT4 domain. You can use smbpasswd to do
@@ -15009,8 +16976,8 @@ CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
-NAME="AEN3124"
->20.2.2. Mandatory profiles</A
+NAME="AEN3447"
+>21.2.2. Mandatory profiles</A
></H3
><P
>The above method can be used to create mandatory profiles also. To convert
@@ -15022,8 +16989,8 @@ CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
-NAME="AEN3127"
->20.2.3. moveuser.exe</A
+NAME="AEN3450"
+>21.2.3. moveuser.exe</A
></H3
><P
>The W2K professional resource kit has moveuser.exe. moveuser.exe changes
@@ -15035,8 +17002,8 @@ CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
-NAME="AEN3130"
->20.2.4. Get SID</A
+NAME="AEN3453"
+>21.2.4. Get SID</A
></H3
><P
>You can identify the SID by using GetSID.exe from the Windows NT Server 4.0
@@ -15058,8 +17025,8 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN3135"
->20.3. Windows 2000/XP</A
+NAME="AEN3458"
+>21.3. Windows 2000/XP</A
></H2
><P
>You must first convert the profile from a local profile to a domain
@@ -15296,14 +17263,14 @@ CLASS="CHAPTER"
><A
NAME="SECURING-SAMBA"
></A
->Chapter 21. Securing Samba</H1
+>Chapter 22. Securing Samba</H1
><DIV
CLASS="SECT1"
><H2
CLASS="SECT1"
><A
-NAME="AEN3216"
->21.1. Introduction</A
+NAME="AEN3539"
+>22.1. Introduction</A
></H2
><P
>This note was attached to the Samba 2.2.8 release notes as it contained an
@@ -15315,8 +17282,8 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN3219"
->21.2. Using host based protection</A
+NAME="AEN3542"
+>22.2. Using host based protection</A
></H2
><P
>In many installations of Samba the greatest threat comes for outside
@@ -15347,8 +17314,8 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN3226"
->21.3. Using interface protection</A
+NAME="AEN3549"
+>22.3. Using interface protection</A
></H2
><P
>By default Samba will accept connections on any network interface that
@@ -15383,8 +17350,8 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN3235"
->21.4. Using a firewall</A
+NAME="AEN3558"
+>22.4. Using a firewall</A
></H2
><P
>Many people use a firewall to deny access to services that they don't
@@ -15413,8 +17380,8 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN3242"
->21.5. Using a IPC$ share deny</A
+NAME="AEN3565"
+>22.5. Using a IPC$ share deny</A
></H2
><P
>If the above methods are not suitable, then you could also place a
@@ -15452,8 +17419,8 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN3251"
->21.6. Upgrading Samba</A
+NAME="AEN3574"
+>22.6. Upgrading Samba</A
></H2
><P
>Please check regularly on http://www.samba.org/ for updates and
@@ -15468,14 +17435,14 @@ CLASS="CHAPTER"
><A
NAME="UNICODE"
></A
->Chapter 22. Unicode/Charsets</H1
+>Chapter 23. Unicode/Charsets</H1
><DIV
CLASS="SECT1"
><H2
CLASS="SECT1"
><A
-NAME="AEN3265"
->22.1. What are charsets and unicode?</A
+NAME="AEN3588"
+>23.1. What are charsets and unicode?</A
></H2
><P
>Computers communicate in numbers. In texts, each number will be
@@ -15524,8 +17491,8 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN3274"
->22.2. Samba and charsets</A
+NAME="AEN3597"
+>23.2. Samba and charsets</A
></H2
><P
>As of samba 3.0, samba can (and will) talk unicode over the wire. Internally,
@@ -15600,42 +17567,42 @@ CLASS="TOC"
>Table of Contents</B
></DT
><DT
->23. <A
+>24. <A
HREF="#PORTABILITY"
>Portability</A
></DT
><DD
><DL
><DT
->23.1. <A
-HREF="#AEN3303"
+>24.1. <A
+HREF="#AEN3626"
>HPUX</A
></DT
><DT
->23.2. <A
-HREF="#AEN3309"
+>24.2. <A
+HREF="#AEN3632"
>SCO Unix</A
></DT
><DT
->23.3. <A
-HREF="#AEN3313"
+>24.3. <A
+HREF="#AEN3636"
>DNIX</A
></DT
><DT
->23.4. <A
-HREF="#AEN3342"
+>24.4. <A
+HREF="#AEN3665"
>RedHat Linux Rembrandt-II</A
></DT
><DT
->23.5. <A
-HREF="#AEN3348"
+>24.5. <A
+HREF="#AEN3671"
>AIX</A
></DT
><DD
><DL
><DT
->23.5.1. <A
-HREF="#AEN3350"
+>24.5.1. <A
+HREF="#AEN3673"
>Sequential Read Ahead</A
></DT
></DL
@@ -15643,147 +17610,147 @@ HREF="#AEN3350"
></DL
></DD
><DT
->24. <A
+>25. <A
HREF="#OTHER-CLIENTS"
>Samba and other CIFS clients</A
></DT
><DD
><DL
><DT
->24.1. <A
-HREF="#AEN3368"
+>25.1. <A
+HREF="#AEN3691"
>Macintosh clients?</A
></DT
><DT
->24.2. <A
-HREF="#AEN3377"
+>25.2. <A
+HREF="#AEN3700"
>OS2 Client</A
></DT
><DD
><DL
><DT
->24.2.1. <A
-HREF="#AEN3379"
+>25.2.1. <A
+HREF="#AEN3702"
>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="#AEN3394"
+>25.2.2. <A
+HREF="#AEN3717"
>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="#AEN3403"
+>25.2.3. <A
+HREF="#AEN3726"
>Are there any other issues when OS/2 (any version)
is used as a client?</A
></DT
><DT
->24.2.4. <A
-HREF="#AEN3407"
+>25.2.4. <A
+HREF="#AEN3730"
>How do I get printer driver download working
for OS/2 clients?</A
></DT
></DL
></DD
><DT
->24.3. <A
-HREF="#AEN3417"
+>25.3. <A
+HREF="#AEN3740"
>Windows for Workgroups</A
></DT
><DD
><DL
><DT
->24.3.1. <A
-HREF="#AEN3419"
+>25.3.1. <A
+HREF="#AEN3742"
>Use latest TCP/IP stack from Microsoft</A
></DT
><DT
->24.3.2. <A
-HREF="#AEN3424"
+>25.3.2. <A
+HREF="#AEN3747"
>Delete .pwl files after password change</A
></DT
><DT
->24.3.3. <A
-HREF="#AEN3429"
+>25.3.3. <A
+HREF="#AEN3752"
>Configure WfW password handling</A
></DT
><DT
->24.3.4. <A
-HREF="#AEN3433"
+>25.3.4. <A
+HREF="#AEN3756"
>Case handling of passwords</A
></DT
><DT
->24.3.5. <A
-HREF="#AEN3438"
+>25.3.5. <A
+HREF="#AEN3761"
>Use TCP/IP as default protocol</A
></DT
></DL
></DD
><DT
->24.4. <A
-HREF="#AEN3441"
+>25.4. <A
+HREF="#AEN3764"
>Windows '95/'98</A
></DT
><DT
->24.5. <A
-HREF="#AEN3457"
+>25.5. <A
+HREF="#AEN3780"
>Windows 2000 Service Pack 2</A
></DT
></DL
></DD
><DT
->25. <A
+>26. <A
HREF="#COMPILING"
>How to compile SAMBA</A
></DT
><DD
><DL
><DT
->25.1. <A
-HREF="#AEN3484"
+>26.1. <A
+HREF="#AEN3807"
>Access Samba source code via CVS</A
></DT
><DD
><DL
><DT
->25.1.1. <A
-HREF="#AEN3486"
+>26.1.1. <A
+HREF="#AEN3809"
>Introduction</A
></DT
><DT
->25.1.2. <A
-HREF="#AEN3491"
+>26.1.2. <A
+HREF="#AEN3814"
>CVS Access to samba.org</A
></DT
></DL
></DD
><DT
->25.2. <A
-HREF="#AEN3527"
+>26.2. <A
+HREF="#AEN3850"
>Accessing the samba sources via rsync and ftp</A
></DT
><DT
->25.3. <A
-HREF="#AEN3533"
+>26.3. <A
+HREF="#AEN3856"
>Building the Binaries</A
></DT
><DT
->25.4. <A
-HREF="#AEN3561"
+>26.4. <A
+HREF="#AEN3884"
>Starting the smbd and nmbd</A
></DT
><DD
><DL
><DT
->25.4.1. <A
-HREF="#AEN3571"
+>26.4.1. <A
+HREF="#AEN3894"
>Starting from inetd.conf</A
></DT
><DT
->25.4.2. <A
-HREF="#AEN3600"
+>26.4.2. <A
+HREF="#AEN3923"
>Alternative: starting it as a daemon</A
></DT
></DL
@@ -15791,128 +17758,128 @@ HREF="#AEN3600"
></DL
></DD
><DT
->26. <A
+>27. <A
HREF="#BUGREPORT"
>Reporting Bugs</A
></DT
><DD
><DL
><DT
->26.1. <A
-HREF="#AEN3623"
+>27.1. <A
+HREF="#AEN3946"
>Introduction</A
></DT
><DT
->26.2. <A
-HREF="#AEN3633"
+>27.2. <A
+HREF="#AEN3956"
>General info</A
></DT
><DT
->26.3. <A
-HREF="#AEN3639"
+>27.3. <A
+HREF="#AEN3962"
>Debug levels</A
></DT
><DT
->26.4. <A
-HREF="#AEN3656"
+>27.4. <A
+HREF="#AEN3979"
>Internal errors</A
></DT
><DT
->26.5. <A
-HREF="#AEN3666"
+>27.5. <A
+HREF="#AEN3989"
>Attaching to a running process</A
></DT
><DT
->26.6. <A
-HREF="#AEN3669"
+>27.6. <A
+HREF="#AEN3992"
>Patches</A
></DT
></DL
></DD
><DT
->27. <A
+>28. <A
HREF="#DIAGNOSIS"
>The samba checklist</A
></DT
><DD
><DL
><DT
->27.1. <A
-HREF="#AEN3692"
+>28.1. <A
+HREF="#AEN4015"
>Introduction</A
></DT
><DT
->27.2. <A
-HREF="#AEN3697"
+>28.2. <A
+HREF="#AEN4020"
>Assumptions</A
></DT
><DT
->27.3. <A
-HREF="#AEN3707"
+>28.3. <A
+HREF="#AEN4030"
>Tests</A
></DT
><DD
><DL
><DT
->27.3.1. <A
-HREF="#AEN3709"
+>28.3.1. <A
+HREF="#AEN4032"
>Test 1</A
></DT
><DT
->27.3.2. <A
-HREF="#AEN3715"
+>28.3.2. <A
+HREF="#AEN4038"
>Test 2</A
></DT
><DT
->27.3.3. <A
-HREF="#AEN3721"
+>28.3.3. <A
+HREF="#AEN4044"
>Test 3</A
></DT
><DT
->27.3.4. <A
-HREF="#AEN3736"
+>28.3.4. <A
+HREF="#AEN4059"
>Test 4</A
></DT
><DT
->27.3.5. <A
-HREF="#AEN3741"
+>28.3.5. <A
+HREF="#AEN4064"
>Test 5</A
></DT
><DT
->27.3.6. <A
-HREF="#AEN3747"
+>28.3.6. <A
+HREF="#AEN4070"
>Test 6</A
></DT
><DT
->27.3.7. <A
-HREF="#AEN3755"
+>28.3.7. <A
+HREF="#AEN4078"
>Test 7</A
></DT
><DT
->27.3.8. <A
-HREF="#AEN3781"
+>28.3.8. <A
+HREF="#AEN4104"
>Test 8</A
></DT
><DT
->27.3.9. <A
-HREF="#AEN3798"
+>28.3.9. <A
+HREF="#AEN4121"
>Test 9</A
></DT
><DT
->27.3.10. <A
-HREF="#AEN3806"
+>28.3.10. <A
+HREF="#AEN4129"
>Test 10</A
></DT
><DT
->27.3.11. <A
-HREF="#AEN3812"
+>28.3.11. <A
+HREF="#AEN4135"
>Test 11</A
></DT
></DL
></DD
><DT
->27.4. <A
-HREF="#AEN3817"
+>28.4. <A
+HREF="#AEN4140"
>Still having troubles?</A
></DT
></DL
@@ -15926,7 +17893,7 @@ CLASS="CHAPTER"
><A
NAME="PORTABILITY"
></A
->Chapter 23. Portability</H1
+>Chapter 24. Portability</H1
><P
>Samba works on a wide range of platforms but the interface all the
platforms provide is not always compatible. This chapter contains
@@ -15936,8 +17903,8 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN3303"
->23.1. HPUX</A
+NAME="AEN3626"
+>24.1. HPUX</A
></H2
><P
>HP's implementation of supplementary groups is, er, non-standard (for
@@ -15966,8 +17933,8 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN3309"
->23.2. SCO Unix</A
+NAME="AEN3632"
+>24.2. SCO Unix</A
></H2
><P
>
@@ -15983,8 +17950,8 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN3313"
->23.3. DNIX</A
+NAME="AEN3636"
+>24.3. DNIX</A
></H2
><P
>DNIX has a problem with seteuid() and setegid(). These routines are
@@ -16090,8 +18057,8 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN3342"
->23.4. RedHat Linux Rembrandt-II</A
+NAME="AEN3665"
+>24.4. RedHat Linux Rembrandt-II</A
></H2
><P
>By default RedHat Rembrandt-II during installation adds an
@@ -16114,16 +18081,16 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN3348"
->23.5. AIX</A
+NAME="AEN3671"
+>24.5. AIX</A
></H2
><DIV
CLASS="SECT2"
><H3
CLASS="SECT2"
><A
-NAME="AEN3350"
->23.5.1. Sequential Read Ahead</A
+NAME="AEN3673"
+>24.5.1. Sequential Read Ahead</A
></H3
><P
>Disabling Sequential Read Ahead using "vmtune -r 0" improves
@@ -16137,7 +18104,7 @@ CLASS="CHAPTER"
><A
NAME="OTHER-CLIENTS"
></A
->Chapter 24. Samba and other CIFS clients</H1
+>Chapter 25. Samba and other CIFS clients</H1
><P
>This chapter contains client-specific information.</P
><DIV
@@ -16145,8 +18112,8 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN3368"
->24.1. Macintosh clients?</A
+NAME="AEN3691"
+>25.1. Macintosh clients?</A
></H2
><P
>Yes. <A
@@ -16191,16 +18158,16 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN3377"
->24.2. OS2 Client</A
+NAME="AEN3700"
+>25.2. OS2 Client</A
></H2
><DIV
CLASS="SECT2"
><H3
CLASS="SECT2"
><A
-NAME="AEN3379"
->24.2.1. How can I configure OS/2 Warp Connect or
+NAME="AEN3702"
+>25.2.1. How can I configure OS/2 Warp Connect or
OS/2 Warp 4 as a client for Samba?</A
></H3
><P
@@ -16258,8 +18225,8 @@ CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
-NAME="AEN3394"
->24.2.2. How can I configure OS/2 Warp 3 (not Connect),
+NAME="AEN3717"
+>25.2.2. How can I configure OS/2 Warp 3 (not Connect),
OS/2 1.2, 1.3 or 2.x for Samba?</A
></H3
><P
@@ -16302,8 +18269,8 @@ CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
-NAME="AEN3403"
->24.2.3. Are there any other issues when OS/2 (any version)
+NAME="AEN3726"
+>25.2.3. Are there any other issues when OS/2 (any version)
is used as a client?</A
></H3
><P
@@ -16324,8 +18291,8 @@ CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
-NAME="AEN3407"
->24.2.4. How do I get printer driver download working
+NAME="AEN3730"
+>25.2.4. How do I get printer driver download working
for OS/2 clients?</A
></H3
><P
@@ -16371,16 +18338,16 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN3417"
->24.3. Windows for Workgroups</A
+NAME="AEN3740"
+>25.3. Windows for Workgroups</A
></H2
><DIV
CLASS="SECT2"
><H3
CLASS="SECT2"
><A
-NAME="AEN3419"
->24.3.1. Use latest TCP/IP stack from Microsoft</A
+NAME="AEN3742"
+>25.3.1. Use latest TCP/IP stack from Microsoft</A
></H3
><P
>Use the latest TCP/IP stack from microsoft if you use Windows
@@ -16401,8 +18368,8 @@ CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
-NAME="AEN3424"
->24.3.2. Delete .pwl files after password change</A
+NAME="AEN3747"
+>25.3.2. Delete .pwl files after password change</A
></H3
><P
>WfWg does a lousy job with passwords. I find that if I change my
@@ -16421,8 +18388,8 @@ CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
-NAME="AEN3429"
->24.3.3. Configure WfW password handling</A
+NAME="AEN3752"
+>25.3.3. Configure WfW password handling</A
></H3
><P
>There is a program call admincfg.exe
@@ -16440,8 +18407,8 @@ CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
-NAME="AEN3433"
->24.3.4. Case handling of passwords</A
+NAME="AEN3756"
+>25.3.4. Case handling of passwords</A
></H3
><P
>Windows for Workgroups uppercases the password before sending it to the server. Unix passwords can be case-sensitive though. Check the <A
@@ -16458,8 +18425,8 @@ CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
-NAME="AEN3438"
->24.3.5. Use TCP/IP as default protocol</A
+NAME="AEN3761"
+>25.3.5. Use TCP/IP as default protocol</A
></H3
><P
>To support print queue reporting you may find
@@ -16474,8 +18441,8 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN3441"
->24.4. Windows '95/'98</A
+NAME="AEN3764"
+>25.4. Windows '95/'98</A
></H2
><P
>When using Windows 95 OEM SR2 the following updates are recommended where Samba
@@ -16522,8 +18489,8 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN3457"
->24.5. Windows 2000 Service Pack 2</A
+NAME="AEN3780"
+>25.5. Windows 2000 Service Pack 2</A
></H2
><P
>
@@ -16606,7 +18573,7 @@ CLASS="CHAPTER"
><A
NAME="COMPILING"
></A
->Chapter 25. How to compile SAMBA</H1
+>Chapter 26. How to compile SAMBA</H1
><P
>You can obtain the samba source from the <A
HREF="http://samba.org/"
@@ -16619,16 +18586,16 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN3484"
->25.1. Access Samba source code via CVS</A
+NAME="AEN3807"
+>26.1. Access Samba source code via CVS</A
></H2
><DIV
CLASS="SECT2"
><H3
CLASS="SECT2"
><A
-NAME="AEN3486"
->25.1.1. Introduction</A
+NAME="AEN3809"
+>26.1.1. Introduction</A
></H3
><P
>Samba is developed in an open environment. Developers use CVS
@@ -16649,8 +18616,8 @@ CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
-NAME="AEN3491"
->25.1.2. CVS Access to samba.org</A
+NAME="AEN3814"
+>26.1.2. CVS Access to samba.org</A
></H3
><P
>The machine samba.org runs a publicly accessible CVS
@@ -16662,8 +18629,8 @@ CLASS="SECT3"
><HR><H4
CLASS="SECT3"
><A
-NAME="AEN3494"
->25.1.2.1. Access via CVSweb</A
+NAME="AEN3817"
+>26.1.2.1. Access via CVSweb</A
></H4
><P
>You can access the source code via your
@@ -16683,8 +18650,8 @@ CLASS="SECT3"
><HR><H4
CLASS="SECT3"
><A
-NAME="AEN3499"
->25.1.2.2. Access via cvs</A
+NAME="AEN3822"
+>26.1.2.2. Access via cvs</A
></H4
><P
>You can also access the source code via a
@@ -16788,8 +18755,8 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN3527"
->25.2. Accessing the samba sources via rsync and ftp</A
+NAME="AEN3850"
+>26.2. Accessing the samba sources via rsync and ftp</A
></H2
><P
> pserver.samba.org also exports unpacked copies of most parts of the CVS tree at <A
@@ -16816,8 +18783,8 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN3533"
->25.3. Building the Binaries</A
+NAME="AEN3856"
+>26.3. Building the Binaries</A
></H2
><P
>To do this, first run the program <B
@@ -16903,8 +18870,8 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN3561"
->25.4. Starting the smbd and nmbd</A
+NAME="AEN3884"
+>26.4. Starting the smbd and nmbd</A
></H2
><P
>You must choose to start smbd and nmbd either
@@ -16943,8 +18910,8 @@ CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
-NAME="AEN3571"
->25.4.1. Starting from inetd.conf</A
+NAME="AEN3894"
+>26.4.1. Starting from inetd.conf</A
></H3
><P
>NOTE; The following will be different if
@@ -17043,8 +19010,8 @@ CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
-NAME="AEN3600"
->25.4.2. Alternative: starting it as a daemon</A
+NAME="AEN3923"
+>26.4.2. Alternative: starting it as a daemon</A
></H3
><P
>To start the server as a daemon you should create
@@ -17102,14 +19069,14 @@ CLASS="CHAPTER"
><A
NAME="BUGREPORT"
></A
->Chapter 26. Reporting Bugs</H1
+>Chapter 27. Reporting Bugs</H1
><DIV
CLASS="SECT1"
><H2
CLASS="SECT1"
><A
-NAME="AEN3623"
->26.1. Introduction</A
+NAME="AEN3946"
+>27.1. Introduction</A
></H2
><P
>The email address for bug reports for stable releases is <A
@@ -17153,8 +19120,8 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN3633"
->26.2. General info</A
+NAME="AEN3956"
+>27.2. General info</A
></H2
><P
>Before submitting a bug report check your config for silly
@@ -17178,8 +19145,8 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN3639"
->26.3. Debug levels</A
+NAME="AEN3962"
+>27.3. Debug levels</A
></H2
><P
>If the bug has anything to do with Samba behaving incorrectly as a
@@ -17248,8 +19215,8 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN3656"
->26.4. Internal errors</A
+NAME="AEN3979"
+>27.4. Internal errors</A
></H2
><P
>If you get a "INTERNAL ERROR" message in your log files it means that
@@ -17292,8 +19259,8 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN3666"
->26.5. Attaching to a running process</A
+NAME="AEN3989"
+>27.5. Attaching to a running process</A
></H2
><P
>Unfortunately some unixes (in particular some recent linux kernels)
@@ -17309,8 +19276,8 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN3669"
->26.6. Patches</A
+NAME="AEN3992"
+>27.6. Patches</A
></H2
><P
>The best sort of bug report is one that includes a fix! If you send us
@@ -17332,14 +19299,14 @@ CLASS="CHAPTER"
><A
NAME="DIAGNOSIS"
></A
->Chapter 27. The samba checklist</H1
+>Chapter 28. The samba checklist</H1
><DIV
CLASS="SECT1"
><H2
CLASS="SECT1"
><A
-NAME="AEN3692"
->27.1. Introduction</A
+NAME="AEN4015"
+>28.1. Introduction</A
></H2
><P
>This file contains a list of tests you can perform to validate your
@@ -17360,8 +19327,8 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN3697"
->27.2. Assumptions</A
+NAME="AEN4020"
+>28.2. Assumptions</A
></H2
><P
>In all of the tests it is assumed you have a Samba server called
@@ -17398,16 +19365,16 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN3707"
->27.3. Tests</A
+NAME="AEN4030"
+>28.3. Tests</A
></H2
><DIV
CLASS="SECT2"
><H3
CLASS="SECT2"
><A
-NAME="AEN3709"
->27.3.1. Test 1</A
+NAME="AEN4032"
+>28.3.1. Test 1</A
></H3
><P
>In the directory in which you store your smb.conf file, run the command
@@ -17428,8 +19395,8 @@ CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
-NAME="AEN3715"
->27.3.2. Test 2</A
+NAME="AEN4038"
+>28.3.2. Test 2</A
></H3
><P
>Run the command "ping BIGSERVER" from the PC and "ping ACLIENT" from
@@ -17454,8 +19421,8 @@ CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
-NAME="AEN3721"
->27.3.3. Test 3</A
+NAME="AEN4044"
+>28.3.3. Test 3</A
></H3
><P
>Run the command "smbclient -L BIGSERVER" on the unix box. You
@@ -17525,8 +19492,8 @@ CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
-NAME="AEN3736"
->27.3.4. Test 4</A
+NAME="AEN4059"
+>28.3.4. Test 4</A
></H3
><P
>Run the command "nmblookup -B BIGSERVER __SAMBA__". You should get the
@@ -17546,8 +19513,8 @@ CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
-NAME="AEN3741"
->27.3.5. Test 5</A
+NAME="AEN4064"
+>28.3.5. Test 5</A
></H3
><P
>run the command <B
@@ -17567,8 +19534,8 @@ CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
-NAME="AEN3747"
->27.3.6. Test 6</A
+NAME="AEN4070"
+>28.3.6. Test 6</A
></H3
><P
>Run the command <B
@@ -17601,8 +19568,8 @@ CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
-NAME="AEN3755"
->27.3.7. Test 7</A
+NAME="AEN4078"
+>28.3.7. Test 7</A
></H3
><P
>Run the command <B
@@ -17690,8 +19657,8 @@ CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
-NAME="AEN3781"
->27.3.8. Test 8</A
+NAME="AEN4104"
+>28.3.8. Test 8</A
></H3
><P
>On the PC type the command <B
@@ -17750,8 +19717,8 @@ CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
-NAME="AEN3798"
->27.3.9. Test 9</A
+NAME="AEN4121"
+>28.3.9. Test 9</A
></H3
><P
>Run the command <B
@@ -17784,8 +19751,8 @@ CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
-NAME="AEN3806"
->27.3.10. Test 10</A
+NAME="AEN4129"
+>28.3.10. Test 10</A
></H3
><P
>Run the command <B
@@ -17810,8 +19777,8 @@ CLASS="SECT2"
><HR><H3
CLASS="SECT2"
><A
-NAME="AEN3812"
->27.3.11. Test 11</A
+NAME="AEN4135"
+>28.3.11. Test 11</A
></H3
><P
>From file manager try to browse the server. Your samba server should
@@ -17838,8 +19805,8 @@ CLASS="SECT1"
><HR><H2
CLASS="SECT1"
><A
-NAME="AEN3817"
->27.4. Still having troubles?</A
+NAME="AEN4140"
+>28.4. Still having troubles?</A
></H2
><P
>Try the mailing list or newsgroup, or use the ethereal utility to
generated by cgit (git 2.34.1) at 2024-07-15 03:01:16 +0000