- Timestamp:
- May 27, 2009, 9:08:03 AM (16 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
branches/samba-3.2.x/docs/htmldocs/Samba3-HOWTO/CUPS-printing.html
r226 r231 1 <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 22. CUPS Printing Support</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.7 3.1"><link rel="start" href="index.html" title="The Official Samba 3.2.x HOWTO and Reference Guide"><link rel="up" href="optional.html" title="Part III. Advanced Configuration"><link rel="prev" href="classicalprinting.html" title="Chapter 21. Classical Printing Support"><link rel="next" href="VFS.html" title="Chapter 23. Stackable VFS modules"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 22. CUPS Printing Support</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="classicalprinting.html">Prev</a> </td><th width="60%" align="center">Part III. Advanced Configuration</th><td width="20%" align="right"> <a accesskey="n" href="VFS.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="CUPS-printing"></a>Chapter 22. CUPS Printing Support</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Kurt</span> <span class="surname">Pfeifle</span></h3><div class="affiliation"><span class="orgname">Danka Deutschland GmbH <br></span><div class="address"><p><code class="email"><<a class="email" href="mailto:kpfeifle@danka.de">kpfeifle@danka.de</a>></code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Ciprian</span> <span class="surname">Vizitiu</span></h3><span class="contrib">drawings</span> <div class="affiliation"><div class="address"><p><code class="email"><<a class="email" href="mailto:CVizitiu@gbif.org">CVizitiu@gbif.org</a>></code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><span class="contrib">drawings</span> <div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><code class="email"><<a class="email" href="mailto:jelmer@samba.org">jelmer@samba.org</a>></code></p></div></div></div></div><div><p class="pubdate"> (27 Jan 2004) </p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="CUPS-printing.html#id2625955">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2625960">Features and Benefits</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2626020">Overview</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2626139">Basic CUPS Support Configuration</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2626254">Linking smbd with libcups.so</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2626501">Simple <code class="filename">smb.conf</code> Settings for CUPS</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2626746">More Complex CUPS <code class="filename">smb.conf</code> Settings</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2627122">Advanced Configuration</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2627140">Central Spooling vs. “<span class="quote">Peer-to-Peer</span>” Printing</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2627190">Raw Print Serving: Vendor Drivers on Windows Clients</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2627425">Installation of Windows Client Drivers</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#cups-raw">Explicitly Enable “<span class="quote">raw</span>” Printing for <span class="emphasis"><em>application/octet-stream</em></span></a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2627712">Driver Upload Methods</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2627834">Advanced Intelligent Printing with PostScript Driver Download</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#gdipost">GDI on Windows, PostScript on UNIX</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2628025">Windows Drivers, GDI, and EMF</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2628203">UNIX Printfile Conversion and GUI Basics</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#post-and-ghost">PostScript and Ghostscript</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2628562">Ghostscript: The Software RIP for Non-PostScript Printers</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2628716">PostScript Printer Description (PPD) Specification</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2628799">Using Windows-Formatted Vendor PPDs</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2628918">CUPS Also Uses PPDs for Non-PostScript Printers</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2628958">The CUPS Filtering Architecture</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2629194">MIME Types and CUPS Filters</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2629622">MIME Type Conversion Rules</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2629829">Filtering Overview</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2629986">Prefilters</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2630173">pstops</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2630341">pstoraster</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2630611">imagetops and imagetoraster</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2630695">rasterto [printers specific]</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2630915">CUPS Backends</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2631254">The Role of <em class="parameter"><code>cupsomatic/foomatic</code></em></a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2631489">The Complete Picture</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2631502"><code class="filename">mime.convs</code></a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2631571">“<span class="quote">Raw</span>” Printing</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2631679">application/octet-stream Printing</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2631958">PostScript Printer Descriptions for Non-PostScript Printers</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2632241"><span class="emphasis"><em>cupsomatic/foomatic-rip</em></span> Versus <span class="emphasis"><em>Native CUPS</em></span> Printing</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2632578">Examples for Filtering Chains</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2633006">Sources of CUPS Drivers/PPDs</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2633129">Printing with Interface Scripts</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2633224">Network Printing (Purely Windows)</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2633241">From Windows Clients to an NT Print Server</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2633303">Driver Execution on the Client</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2633375">Driver Execution on the Server</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2633480">Network Printing (Windows Clients and UNIX/Samba Print2 Servers)</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id26 33498">From Windows Clients to a CUPS/Samba Print Server</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2633689">Samba Receiving Job-Files and Passing Them to CUPS</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2633768">Network PostScript RIP</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2633858">PPDs for Non-PS Printers on UNIX</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2633902">PPDs for Non-PS Printers on Windows</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2633970">Windows Terminal Servers (WTS) as CUPS Clients</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2633985">Printer Drivers Running in “<span class="quote">Kernel Mode</span>”Cause Many3 Problems</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id26 34023">Workarounds Impose Heavy Limitations</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2634041">CUPS: A “<span class="quote">Magical Stone</span>”?</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2634084">PostScript Drivers with No Major Problems, Even in Kernel4 Mode</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id26 34171">Configuring CUPS for Driver Download</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2634194"><span class="emphasis"><em>cupsaddsmb</em></span>: The Unknown Utility</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2634292">Prepare Your <code class="filename">smb.conf</code> for <code class="literal">cupsaddsmb</code></a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2634572">CUPS “<span class="quote">PostScript Driver for Windows NT/200x/XP</span>”</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2634811">Recognizing Different Driver Files</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2634930">Acquiring the Adobe Driver Files</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2634955">ESP Print Pro PostScript Driver for Windows NT/200x/XP</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2635017">Caveats to Be Considered</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2635317">Windows CUPS PostScript Driver Versus Adobe Driver</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2635535">Run cupsaddsmb (Quiet Mode)</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2635675">Run cupsaddsmb with Verbose Output</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2635867">Understanding cupsaddsmb</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2636011">How to Recognize If cupsaddsmb Completed Successfully</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2636133">cupsaddsmb with a Samba PDC</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2636214">cupsaddsmb Flowchart</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2636295">Installing the PostScript Driver on a Client</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#cups-avoidps1">Avoiding Critical PostScript Driver Settings on the Client</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2636530">Installing PostScript Driver Files Manually Using rpcclient</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2636704">A Check of the rpcclient man Page</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2636876">Understanding the rpcclient man Page</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2636981">Producing an Example by Querying a Windows Box</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2637113">Requirements for adddriver and setdriver to Succeed</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2637337">Manual Driver Installation in 15 Steps</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2638296">Troubleshooting Revisited</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2638439">The Printing <code class="filename">*.tdb</code> Files</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2638642">Trivial Database Files</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2638709">Binary Format</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2638775">Losing <code class="filename">*.tdb</code> Files</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2638826">Using <code class="literal">tdbbackup</code></a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2638946">CUPS Print Drivers from Linuxprinting.org</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2639121">foomatic-rip and Foomatic Explained</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2639948">foomatic-rip and Foomatic PPD Download and Installation</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2640421">Page Accounting with CUPS</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2640456">Setting Up Quotas</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2640510">Correct and Incorrect Accounting</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2640551">Adobe and CUPS PostScript Drivers for Windows Clients</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2640692">The page_log File Syntax</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2640836">Possible Shortcomings</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2640902">Future Developments</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2640942">Other Accounting Tools</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2640956">Additional Material</a></span></dt><dt><span class="sect1"><a href="CUPS-printing.html#id2641173">Autodeletion or Preservation of CUPS Spool Files</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2641249">CUPS Configuration Settings Explained</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2641334">Preconditions</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2641472">Manual Configuration</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2641520">Printing from CUPS to Windows-Attached Printers</a></span></dt><dt><span class="sect1"><a href="CUPS-printing.html#id2641816">More CUPS Filtering Chains</a></span></dt><dt><span class="sect1"><a href="CUPS-printing.html#id2641927">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2641933">Windows 9x/Me Client Can't Install Driver</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#root-ask-loop">“<span class="quote">cupsaddsmb</span>” Keeps Asking for Root Password in Never-ending Loop</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2642010">“<span class="quote">cupsaddsmb</span>” or “<span class="quote">rpcclient addriver</span>” Emit Error</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2642048">“<span class="quote">cupsaddsmb</span>” Errors</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2642122">Client Can't Connect to Samba Printer</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2642146">New Account Reconnection from Windows 200x/XP Troubles</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2642237">Avoid Being Connected to the Samba Server as the Wrong User</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2642289">Upgrading to CUPS Drivers from Adobe Drivers</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2642326">Can't Use “<span class="quote">cupsaddsmb</span>” on Samba Server, Which Is a PDC</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2642362">Deleted Windows 200x Printer Driver Is Still Shown</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2642397">Windows 200x/XP Local Security Policies</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2642430">Administrator Cannot Install Printers for All Local Users</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2642471">Print Change, Notify Functions on NT Clients</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2642496">Windows XP SP1</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2642543">Print Options for All Users Can't Be Set on Windows 200x/XP</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2642826">Most Common Blunders in Driver Settings on Windows Clients</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2642881"><code class="literal">cupsaddsmb</code> Does Not Work with Newly Installed Printer</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2642931">Permissions on <code class="filename">/var/spool/samba/</code> Get Reset After Each Reboot</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2643029">Print Queue Called “<span class="quote">lp</span>” Mishandles Print Jobs</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2643098">Location of Adobe PostScript Driver Files for “<span class="quote">cupsaddsmb</span>”</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2643152">Overview of the CUPS Printing Processes</a></span></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2625955"></a>Introduction</h2></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2625960"></a>Features and Benefits</h3></div></div></div><p>5 <a class="indexterm" name="id26 25968"></a>1 <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 22. CUPS Printing Support</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.2.x HOWTO and Reference Guide"><link rel="up" href="optional.html" title="Part III. Advanced Configuration"><link rel="prev" href="classicalprinting.html" title="Chapter 21. Classical Printing Support"><link rel="next" href="VFS.html" title="Chapter 23. Stackable VFS modules"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 22. CUPS Printing Support</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="classicalprinting.html">Prev</a> </td><th width="60%" align="center">Part III. Advanced Configuration</th><td width="20%" align="right"> <a accesskey="n" href="VFS.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="CUPS-printing"></a>Chapter 22. CUPS Printing Support</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Kurt</span> <span class="orgname">Danka Deutschland GmbH </span> <span class="surname">Pfeifle</span></h3><div class="affiliation"><span class="orgname">Danka Deutschland GmbH <br></span><div class="address"><p><code class="email"><<a class="email" href="mailto:kpfeifle@danka.de">kpfeifle@danka.de</a>></code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Ciprian</span> <span class="surname">Vizitiu</span></h3><span class="contrib">drawings</span> <div class="affiliation"><div class="address"><p><code class="email"><<a class="email" href="mailto:CVizitiu@gbif.org">CVizitiu@gbif.org</a>></code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="orgname">The Samba Team</span> <span class="surname">Vernooij</span></h3><span class="contrib">drawings</span> <div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><code class="email"><<a class="email" href="mailto:jelmer@samba.org">jelmer@samba.org</a>></code></p></div></div></div></div><div><p class="pubdate"> (27 Jan 2004) </p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="CUPS-printing.html#id2632918">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2632924">Features and Benefits</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2632984">Overview</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2633103">Basic CUPS Support Configuration</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2633218">Linking smbd with libcups.so</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2633467">Simple smb.conf Settings for CUPS</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2633711">More Complex CUPS smb.conf Settings</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2634088">Advanced Configuration</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2634106">Central Spooling vs. Peer-to-Peer Printing</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2634156">Raw Print Serving: Vendor Drivers on Windows Clients</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2634391">Installation of Windows Client Drivers</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#cups-raw">Explicitly Enable raw Printing for application/octet-stream</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2634678">Driver Upload Methods</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2634800">Advanced Intelligent Printing with PostScript Driver Download</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#gdipost">GDI on Windows, PostScript on UNIX</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2634992">Windows Drivers, GDI, and EMF</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2635170">UNIX Printfile Conversion and GUI Basics</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#post-and-ghost">PostScript and Ghostscript</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2635529">Ghostscript: The Software RIP for Non-PostScript Printers</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2635683">PostScript Printer Description (PPD) Specification</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2635766">Using Windows-Formatted Vendor PPDs</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2635886">CUPS Also Uses PPDs for Non-PostScript Printers</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2635925">The CUPS Filtering Architecture</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2636161">MIME Types and CUPS Filters</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2636590">MIME Type Conversion Rules</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2636798">Filtering Overview</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2636955">Prefilters</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2637143">pstops</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2637311">pstoraster</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2637580">imagetops and imagetoraster</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2637665">rasterto [printers specific]</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2637884">CUPS Backends</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2638223">The Role of cupsomatic/foomatic</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2638458">The Complete Picture</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2638471">mime.convs</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2638540">Raw Printing</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2638648">application/octet-stream Printing</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2638927">PostScript Printer Descriptions for Non-PostScript Printers</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2639210">cupsomatic/foomatic-rip Versus Native CUPS Printing</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2639547">Examples for Filtering Chains</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2639975">Sources of CUPS Drivers/PPDs</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2640098">Printing with Interface Scripts</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2640193">Network Printing (Purely Windows)</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2640209">From Windows Clients to an NT Print Server</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2640271">Driver Execution on the Client</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2640343">Driver Execution on the Server</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2640448">Network Printing (Windows Clients and UNIX/Samba Print 2 Servers)</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2640466">From Windows Clients to a CUPS/Samba Print Server</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2640656">Samba Receiving Job-Files and Passing Them to CUPS</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2640735">Network PostScript RIP</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2640826">PPDs for Non-PS Printers on UNIX</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2640870">PPDs for Non-PS Printers on Windows</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2640938">Windows Terminal Servers (WTS) as CUPS Clients</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2640953">Printer Drivers Running in Kernel Mode Cause Many 3 Problems</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2640991">Workarounds Impose Heavy Limitations</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2641009">CUPS: A Magical Stone?</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2641052">PostScript Drivers with No Major Problems, Even in Kernel 4 Mode</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2641139">Configuring CUPS for Driver Download</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2641162">cupsaddsmb: The Unknown Utility</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2641260">Prepare Your smb.conf for cupsaddsmb</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2641541">CUPS PostScript Driver for Windows NT/200x/XP</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2641780">Recognizing Different Driver Files</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2641899">Acquiring the Adobe Driver Files</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2641924">ESP Print Pro PostScript Driver for Windows NT/200x/XP</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2641987">Caveats to Be Considered</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2642286">Windows CUPS PostScript Driver Versus Adobe Driver</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2642504">Run cupsaddsmb (Quiet Mode)</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2642644">Run cupsaddsmb with Verbose Output</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2642836">Understanding cupsaddsmb</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2642980">How to Recognize If cupsaddsmb Completed Successfully</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2643102">cupsaddsmb with a Samba PDC</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2643183">cupsaddsmb Flowchart</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2643264">Installing the PostScript Driver on a Client</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#cups-avoidps1">Avoiding Critical PostScript Driver Settings on the Client</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2643499">Installing PostScript Driver Files Manually Using rpcclient</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2643673">A Check of the rpcclient man Page</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2643845">Understanding the rpcclient man Page</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2643950">Producing an Example by Querying a Windows Box</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2644082">Requirements for adddriver and setdriver to Succeed</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2644307">Manual Driver Installation in 15 Steps</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2645265">Troubleshooting Revisited</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2645408">The Printing *.tdb Files</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2645611">Trivial Database Files</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2645679">Binary Format</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2645745">Losing *.tdb Files</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2645796">Using tdbbackup</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2645915">CUPS Print Drivers from Linuxprinting.org</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2646091">foomatic-rip and Foomatic Explained</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2646918">foomatic-rip and Foomatic PPD Download and Installation</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2647391">Page Accounting with CUPS</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2647427">Setting Up Quotas</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2647481">Correct and Incorrect Accounting</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2647521">Adobe and CUPS PostScript Drivers for Windows Clients</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2647662">The page_log File Syntax</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2647807">Possible Shortcomings</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2647873">Future Developments</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2647913">Other Accounting Tools</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2647927">Additional Material</a></span></dt><dt><span class="sect1"><a href="CUPS-printing.html#id2648144">Autodeletion or Preservation of CUPS Spool Files</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2648220">CUPS Configuration Settings Explained</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2648305">Preconditions</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2648444">Manual Configuration</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2648491">Printing from CUPS to Windows-Attached Printers</a></span></dt><dt><span class="sect1"><a href="CUPS-printing.html#id2648787">More CUPS Filtering Chains</a></span></dt><dt><span class="sect1"><a href="CUPS-printing.html#id2648899">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="CUPS-printing.html#id2648904">Windows 9x/Me Client Can't Install Driver</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#root-ask-loop">cupsaddsmb Keeps Asking for Root Password in Never-ending Loop</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2648981">cupsaddsmb or rpcclient addriver Emit Error</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649019">cupsaddsmb Errors</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649093">Client Can't Connect to Samba Printer</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649118">New Account Reconnection from Windows 200x/XP Troubles</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649209">Avoid Being Connected to the Samba Server as the Wrong User</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649260">Upgrading to CUPS Drivers from Adobe Drivers</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649298">Can't Use cupsaddsmb on Samba Server, Which Is a PDC</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649333">Deleted Windows 200x Printer Driver Is Still Shown</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649368">Windows 200x/XP Local Security Policies</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649401">Administrator Cannot Install Printers for All Local Users</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649442">Print Change, Notify Functions on NT Clients</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649468">Windows XP SP1</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649514">Print Options for All Users Can't Be Set on Windows 200x/XP</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649797">Most Common Blunders in Driver Settings on Windows Clients</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649853">cupsaddsmb Does Not Work with Newly Installed Printer</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2649902">Permissions on /var/spool/samba/ Get Reset After Each Reboot</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2650001">Print Queue Called lp Mishandles Print Jobs</a></span></dt><dt><span class="sect2"><a href="CUPS-printing.html#id2650070">Location of Adobe PostScript Driver Files for cupsaddsmb</a></span></dt></dl></dd><dt><span class="sect1"><a href="CUPS-printing.html#id2650124">Overview of the CUPS Printing Processes</a></span></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2632918"></a>Introduction</h2></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2632924"></a>Features and Benefits</h3></div></div></div><p> 5 <a class="indexterm" name="id2632932"></a> 6 6 The Common UNIX Print System (<a class="ulink" href="http://www.cups.org/" target="_top">CUPS</a>) 7 7 has become quite popular. All major Linux distributions now ship it as their default printing … … 12 12 that is also relevant to CUPS. 13 13 </p><p> 14 <a class="indexterm" name="id26 26003"></a>14 <a class="indexterm" name="id2632967"></a> 15 15 CUPS sports quite a few unique and powerful features. While its basic functions may be grasped quite 16 16 easily, they are also new. Because it is different from other, more traditional printing systems, it is best … … 18 18 the beginning. This documentation will lead you to a complete understanding of CUPS. Let's start with the most 19 19 basic things first. 20 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id26 26020"></a>Overview</h3></div></div></div><p>21 <a class="indexterm" name="id26 26028"></a>22 <a class="indexterm" name="id26 26035"></a>23 <a class="indexterm" name="id26 26042"></a>24 <a class="indexterm" name="id26 26049"></a>25 <a class="indexterm" name="id26 26056"></a>26 <a class="indexterm" name="id26 26065"></a>27 <a class="indexterm" name="id26 26075"></a>28 <a class="indexterm" name="id26 26081"></a>20 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2632984"></a>Overview</h3></div></div></div><p> 21 <a class="indexterm" name="id2632991"></a> 22 <a class="indexterm" name="id2632998"></a> 23 <a class="indexterm" name="id2633005"></a> 24 <a class="indexterm" name="id2633012"></a> 25 <a class="indexterm" name="id2633019"></a> 26 <a class="indexterm" name="id2633029"></a> 27 <a class="indexterm" name="id2633038"></a> 28 <a class="indexterm" name="id2633045"></a> 29 29 CUPS is more than just a print spooling system. It is a complete printer management system that 30 30 complies with the new Internet Printing Protocol (IPP). IPP is an industry and Internet Engineering Task Force … … 34 34 like KDE's overwhelming <a class="ulink" href="http://printing.kde.org/" target="_top">KDEPrint</a>). 35 35 </p><p> 36 <a class="indexterm" name="id26 26107"></a>37 <a class="indexterm" name="id26 26114"></a>36 <a class="indexterm" name="id2633071"></a> 37 <a class="indexterm" name="id2633078"></a> 38 38 CUPS allows creation of <span class="emphasis"><em>raw</em></span> printers (i.e., no print file format translation) as 39 39 well as <span class="emphasis"><em>smart</em></span> printers (i.e., CUPS does file format conversion as required for the … … 41 41 course, if you are a CUPS advocate, you would argue that CUPS is better! In any case, let us now explore how 42 42 to configure CUPS for interfacing with MS Windows print clients via Samba. 43 </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id26 26139"></a>Basic CUPS Support Configuration</h2></div></div></div><p>44 <a class="indexterm" name="id26 26147"></a>45 <a class="indexterm" name="id26 26154"></a>46 <a class="indexterm" name="id26 26160"></a>47 <a class="indexterm" name="id26 26167"></a>48 <a class="indexterm" name="id26 26174"></a>43 </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2633103"></a>Basic CUPS Support Configuration</h2></div></div></div><p> 44 <a class="indexterm" name="id2633111"></a> 45 <a class="indexterm" name="id2633118"></a> 46 <a class="indexterm" name="id2633124"></a> 47 <a class="indexterm" name="id2633131"></a> 48 <a class="indexterm" name="id2633138"></a> 49 49 Printing with CUPS in the most basic <code class="filename">smb.conf</code> setup in Samba-3.0 (as was true for 2.2.x) requires just two 50 parameters: <a class="link" href="smb.conf.5.html#PRINTING" >printing = cups</a> and <a class="link" href="smb.conf.5.html#PRINTCAP">printcap = cups</a>. CUPS does not need a printcap file. However, the50 parameters: <a class="link" href="smb.conf.5.html#PRINTING" target="_top">printing = cups</a> and <a class="link" href="smb.conf.5.html#PRINTCAP" target="_top">printcap = cups</a>. CUPS does not need a printcap file. However, the 51 51 <code class="filename">cupsd.conf</code> configuration file knows of two related directives that control how such a 52 52 file will be automatically created and maintained by CUPS for the convenience of third-party applications … … 56 56 cupsd.conf</code> and other CUPS-related documentation, like the wealth of documents regarding the CUPS 57 57 server itself available from the <a class="ulink" href="http://localhost:631/documentation.html" target="_top">CUPS</a> web site. 58 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id26 26254"></a>Linking smbd with libcups.so</h3></div></div></div><p>59 <a class="indexterm" name="id26 26262"></a>58 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2633218"></a>Linking smbd with libcups.so</h3></div></div></div><p> 59 <a class="indexterm" name="id2633226"></a> 60 60 Samba has a special relationship to CUPS. Samba can be compiled with CUPS library support. 61 61 Most recent installations have this support enabled. By default, CUPS linking is compiled … … 64 64 there are some differences in required or supported configuration. 65 65 </p><p> 66 <a class="indexterm" name="id26 26288"></a>67 <a class="indexterm" name="id26 26294"></a>68 When Samba is compiled and linked with <code class="filename">libcups</code>, <a class="link" href="smb.conf.5.html#PRINTCAP" >printcap = cups</a>66 <a class="indexterm" name="id2633251"></a> 67 <a class="indexterm" name="id2633258"></a> 68 When Samba is compiled and linked with <code class="filename">libcups</code>, <a class="link" href="smb.conf.5.html#PRINTCAP" target="_top">printcap = cups</a> 69 69 uses the CUPS API to list printers, submit jobs, query queues, and so on. Otherwise it maps to the System V 70 70 commands with an additional <code class="literal">-oraw</code> option for printing. On a Linux … … 80 80 </pre><p> 81 81 </p><p> 82 <a class="indexterm" name="id26 26365"></a>82 <a class="indexterm" name="id2633329"></a> 83 83 The line <code class="computeroutput">libcups.so.2 => /usr/lib/libcups.so.2 (0x40123000)</code> shows 84 84 there is CUPS support compiled into this version of Samba. If this is the case, and printing = cups … … 86 86 This is an important point to remember! 87 87 </p><div class="tip" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Tip</h3><p> Should it be necessary, for any reason, to set your own print commands, you can do this by setting 88 <a class="link" href="smb.conf.5.html#PRINTING" >printing = sysv</a>. However, you will lose all the benefits88 <a class="link" href="smb.conf.5.html#PRINTING" target="_top">printing = sysv</a>. However, you will lose all the benefits 89 89 of tight CUPS-Samba integration. When you do this, you must manually configure the printing system commands 90 90 (most important: 91 <a class="link" href="smb.conf.5.html#PRINTCOMMAND" >print command</a>; other commands are92 <a class="link" href="smb.conf.5.html#LPPAUSECOMMAND" >lppause command</a>,93 <a class="link" href="smb.conf.5.html#LPRESUMECOMMAND" >lpresume command</a>,94 <a class="link" href="smb.conf.5.html#LPQCOMMAND" >lpq command</a>,95 <a class="link" href="smb.conf.5.html#LPRMCOMMAND" >lprm command</a>,96 <a class="link" href="smb.conf.5.html#QUEUEPAUSECOMMAND" >queuepause command</a> and97 <a class="link" href="smb.conf.5.html#QUEUERESUMECOMMAND" >queue resume command</a>).98 </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id26 26501"></a>Simple <code class="filename">smb.conf</code> Settings for CUPS</h3></div></div></div><p>91 <a class="link" href="smb.conf.5.html#PRINTCOMMAND" target="_top">print command</a>; other commands are 92 <a class="link" href="smb.conf.5.html#LPPAUSECOMMAND" target="_top">lppause command</a>, 93 <a class="link" href="smb.conf.5.html#LPRESUMECOMMAND" target="_top">lpresume command</a>, 94 <a class="link" href="smb.conf.5.html#LPQCOMMAND" target="_top">lpq command</a>, 95 <a class="link" href="smb.conf.5.html#LPRMCOMMAND" target="_top">lprm command</a>, 96 <a class="link" href="smb.conf.5.html#QUEUEPAUSECOMMAND" target="_top">queuepause command</a> and 97 <a class="link" href="smb.conf.5.html#QUEUERESUMECOMMAND" target="_top">queue resume command</a>). 98 </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2633467"></a>Simple <code class="filename">smb.conf</code> Settings for CUPS</h3></div></div></div><p> 99 99 To summarize, <a class="link" href="CUPS-printing.html#cups-exam-simple" title="Example 22.1. Simplest Printing-Related smb.conf">the Simplest Printing-Related 100 100 <code class="filename">smb.conf</code> file</a> shows the simplest printing-related setup for <code class="filename">smb.conf</code> to 101 101 enable basic CUPS support: 102 </p><div class="example"><a name="cups-exam-simple"></a><p class="title"><b>Example 22.1. Simplest Printing-Related smb.conf</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id26 26561"></a><em class="parameter"><code>load printers = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2626573"></a><em class="parameter"><code>printing = cups</code></em></td></tr><tr><td><a class="indexterm" name="id2626584"></a><em class="parameter"><code>printcap name = cups</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[printers]</code></em></td></tr><tr><td><a class="indexterm" name="id2626605"></a><em class="parameter"><code>comment = All Printers</code></em></td></tr><tr><td><a class="indexterm" name="id2626617"></a><em class="parameter"><code>path = /var/spool/samba</code></em></td></tr><tr><td><a class="indexterm" name="id2626628"></a><em class="parameter"><code>browseable = no</code></em></td></tr><tr><td><a class="indexterm" name="id2626640"></a><em class="parameter"><code>guest ok = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2626652"></a><em class="parameter"><code>writable = no</code></em></td></tr><tr><td><a class="indexterm" name="id2626663"></a><em class="parameter"><code>printable = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2626675"></a><em class="parameter"><code>printer admin = root, @ntadmins, @smbprintadm</code></em></td></tr></table></div></div><br class="example-break"><p>103 <a class="indexterm" name="id26 26690"></a>104 <a class="indexterm" name="id26 26697"></a>105 <a class="indexterm" name="id26 26704"></a>102 </p><div class="example"><a name="cups-exam-simple"></a><p class="title"><b>Example 22.1. Simplest Printing-Related smb.conf</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2633527"></a><em class="parameter"><code>load printers = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2633538"></a><em class="parameter"><code>printing = cups</code></em></td></tr><tr><td><a class="indexterm" name="id2633550"></a><em class="parameter"><code>printcap name = cups</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[printers]</code></em></td></tr><tr><td><a class="indexterm" name="id2633571"></a><em class="parameter"><code>comment = All Printers</code></em></td></tr><tr><td><a class="indexterm" name="id2633583"></a><em class="parameter"><code>path = /var/spool/samba</code></em></td></tr><tr><td><a class="indexterm" name="id2633594"></a><em class="parameter"><code>browseable = no</code></em></td></tr><tr><td><a class="indexterm" name="id2633606"></a><em class="parameter"><code>guest ok = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2633618"></a><em class="parameter"><code>writable = no</code></em></td></tr><tr><td><a class="indexterm" name="id2633629"></a><em class="parameter"><code>printable = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2633641"></a><em class="parameter"><code>printer admin = root, @ntadmins, @smbprintadm</code></em></td></tr></table></div></div><br class="example-break"><p> 103 <a class="indexterm" name="id2633656"></a> 104 <a class="indexterm" name="id2633663"></a> 105 <a class="indexterm" name="id2633670"></a> 106 106 This is all you need for basic printing setup for CUPS. It will print all graphic, text, PDF, and PostScript 107 107 files submitted from Windows clients. However, most of your Windows users would not know how to send these … … 113 113 PostScript device, the print data stream is “<span class="quote">binary,</span>” sensible only for the target printer. Read 114 114 on to learn what problem this may cause and how to avoid it. 115 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id26 26746"></a>More Complex CUPS <code class="filename">smb.conf</code> Settings</h3></div></div></div><p>115 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2633711"></a>More Complex CUPS <code class="filename">smb.conf</code> Settings</h3></div></div></div><p> 116 116 <a class="link" href="CUPS-printing.html#overridesettings" title="Example 22.2. Overriding Global CUPS Settings for One Printer">The Overriding Global CUPS Settings for One Printer example</a> 117 117 is a slightly more complex printing-related setup for <code class="filename">smb.conf</code>. It enables general CUPS printing 118 118 support for all printers, but defines one printer share, which is set up differently. 119 </p><div class="example"><a name="overridesettings"></a><p class="title"><b>Example 22.2. Overriding Global CUPS Settings for One Printer</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id26 26803"></a><em class="parameter"><code>printing = cups</code></em></td></tr><tr><td><a class="indexterm" name="id2626814"></a><em class="parameter"><code>printcap name = cups</code></em></td></tr><tr><td><a class="indexterm" name="id2626826"></a><em class="parameter"><code>load printers = yes</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[printers]</code></em></td></tr><tr><td><a class="indexterm" name="id2626847"></a><em class="parameter"><code>comment = All Printers</code></em></td></tr><tr><td><a class="indexterm" name="id2626858"></a><em class="parameter"><code>path = /var/spool/samba</code></em></td></tr><tr><td><a class="indexterm" name="id2626870"></a><em class="parameter"><code>guest ok = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2626882"></a><em class="parameter"><code>writable = no</code></em></td></tr><tr><td><a class="indexterm" name="id2626893"></a><em class="parameter"><code>printable = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2626905"></a><em class="parameter"><code>printer admin = root, @ntadmins, @smbprintadm</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[special_printer]</code></em></td></tr><tr><td><a class="indexterm" name="id2626926"></a><em class="parameter"><code>comment = A special printer with his own settings</code></em></td></tr><tr><td><a class="indexterm" name="id2626938"></a><em class="parameter"><code>path = /var/spool/samba-special</code></em></td></tr><tr><td><a class="indexterm" name="id2626950"></a><em class="parameter"><code>printing = sysv</code></em></td></tr><tr><td><a class="indexterm" name="id2626962"></a><em class="parameter"><code>printcap = lpstat</code></em></td></tr><tr><td><a class="indexterm" name="id2626973"></a><em class="parameter"><code>print command = echo "NEW: `date`: printfile %f" >> /tmp/smbprn.log ; echo " `date`: p-%p s-%s f-%f" >> /tmp/smbprn.log ; echo " `date`: j-%j J-%J z-%z c-%c" >> /tmp/smbprn.log ; rm %f </code></em></td></tr><tr><td><a class="indexterm" name="id2626990"></a><em class="parameter"><code>guest ok = no</code></em></td></tr><tr><td><a class="indexterm" name="id2627002"></a><em class="parameter"><code>writable = no</code></em></td></tr><tr><td><a class="indexterm" name="id2627013"></a><em class="parameter"><code>printable = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2627025"></a><em class="parameter"><code>printer admin = kurt</code></em></td></tr><tr><td><a class="indexterm" name="id2627037"></a><em class="parameter"><code>hosts deny = 0.0.0.0</code></em></td></tr><tr><td><a class="indexterm" name="id2627048"></a><em class="parameter"><code>hosts allow = turbo_xp, 10.160.50.23, 10.160.51.60</code></em></td></tr></table></div></div><br class="example-break"><p>119 </p><div class="example"><a name="overridesettings"></a><p class="title"><b>Example 22.2. Overriding Global CUPS Settings for One Printer</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2633768"></a><em class="parameter"><code>printing = cups</code></em></td></tr><tr><td><a class="indexterm" name="id2633779"></a><em class="parameter"><code>printcap name = cups</code></em></td></tr><tr><td><a class="indexterm" name="id2633791"></a><em class="parameter"><code>load printers = yes</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[printers]</code></em></td></tr><tr><td><a class="indexterm" name="id2633812"></a><em class="parameter"><code>comment = All Printers</code></em></td></tr><tr><td><a class="indexterm" name="id2633824"></a><em class="parameter"><code>path = /var/spool/samba</code></em></td></tr><tr><td><a class="indexterm" name="id2633835"></a><em class="parameter"><code>guest ok = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2633847"></a><em class="parameter"><code>writable = no</code></em></td></tr><tr><td><a class="indexterm" name="id2633858"></a><em class="parameter"><code>printable = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2633870"></a><em class="parameter"><code>printer admin = root, @ntadmins, @smbprintadm</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[special_printer]</code></em></td></tr><tr><td><a class="indexterm" name="id2633891"></a><em class="parameter"><code>comment = A special printer with his own settings</code></em></td></tr><tr><td><a class="indexterm" name="id2633904"></a><em class="parameter"><code>path = /var/spool/samba-special</code></em></td></tr><tr><td><a class="indexterm" name="id2633915"></a><em class="parameter"><code>printing = sysv</code></em></td></tr><tr><td><a class="indexterm" name="id2633927"></a><em class="parameter"><code>printcap = lpstat</code></em></td></tr><tr><td><a class="indexterm" name="id2633939"></a><em class="parameter"><code>print command = echo "NEW: `date`: printfile %f" >> /tmp/smbprn.log ; echo " `date`: p-%p s-%s f-%f" >> /tmp/smbprn.log ; echo " `date`: j-%j J-%J z-%z c-%c" >> /tmp/smbprn.log ; rm %f </code></em></td></tr><tr><td><a class="indexterm" name="id2633955"></a><em class="parameter"><code>guest ok = no</code></em></td></tr><tr><td><a class="indexterm" name="id2633967"></a><em class="parameter"><code>writable = no</code></em></td></tr><tr><td><a class="indexterm" name="id2633978"></a><em class="parameter"><code>printable = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2633990"></a><em class="parameter"><code>printer admin = kurt</code></em></td></tr><tr><td><a class="indexterm" name="id2634002"></a><em class="parameter"><code>hosts deny = 0.0.0.0</code></em></td></tr><tr><td><a class="indexterm" name="id2634014"></a><em class="parameter"><code>hosts allow = turbo_xp, 10.160.50.23, 10.160.51.60</code></em></td></tr></table></div></div><br class="example-break"><p> 120 120 This special share is only for testing purposes. It does not write the print job to a file. It just logs the job parameters 121 121 known to Samba into the <code class="filename">/tmp/smbprn.log</code> file and deletes the job-file. Moreover, the 122 <a class="link" href="smb.conf.5.html#PRINTERADMIN" >printer admin</a> of this share is “<span class="quote">kurt</span>” (not the “<span class="quote">@ntadmins</span>” group),122 <a class="link" href="smb.conf.5.html#PRINTERADMIN" target="_top">printer admin</a> of this share is “<span class="quote">kurt</span>” (not the “<span class="quote">@ntadmins</span>” group), 123 123 guest access is not allowed, the share isn't published to the Network Neighborhood (so you need to know it is there), and it 124 124 allows access from only three hosts. To prevent CUPS from kicking in and taking over the print jobs for that share, we need to set 125 <a class="link" href="smb.conf.5.html#PRINTING" >printing = sysv</a> and <a class="link" href="smb.conf.5.html#PRINTCAP">printcap = lpstat</a>.126 </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id26 27122"></a>Advanced Configuration</h2></div></div></div><p>125 <a class="link" href="smb.conf.5.html#PRINTING" target="_top">printing = sysv</a> and <a class="link" href="smb.conf.5.html#PRINTCAP" target="_top">printcap = lpstat</a>. 126 </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2634088"></a>Advanced Configuration</h2></div></div></div><p> 127 127 Before we delve into all the configuration options, let us clarify a few points. <span class="emphasis"><em>Network printing 128 128 needs to be organized and set up correctly</em></span>. This frequently doesn't happen. Legacy systems or small 129 129 business LAN environments often lack design and good housekeeping. 130 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id26 27140"></a>Central Spooling vs. “<span class="quote">Peer-to-Peer</span>” Printing</h3></div></div></div><p>131 <a class="indexterm" name="id26 27151"></a>132 <a class="indexterm" name="id26 27158"></a>133 <a class="indexterm" name="id26 27167"></a>130 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2634106"></a>Central Spooling vs. “<span class="quote">Peer-to-Peer</span>” Printing</h3></div></div></div><p> 131 <a class="indexterm" name="id2634117"></a> 132 <a class="indexterm" name="id2634124"></a> 133 <a class="indexterm" name="id2634133"></a> 134 134 Many small office or home networks, as well as badly organized larger environments, allow each client a direct 135 135 access to available network printers. This is generally a bad idea. It often blocks one client's access to the … … 139 139 central system, which responds immediately, takes jobs from multiple concurrent clients, and transfers them to 140 140 the printer(s) in the correct order. 141 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id26 27190"></a>Raw Print Serving: Vendor Drivers on Windows Clients</h3></div></div></div><p>142 <a class="indexterm" name="id26 27199"></a>143 <a class="indexterm" name="id26 27205"></a>141 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2634156"></a>Raw Print Serving: Vendor Drivers on Windows Clients</h3></div></div></div><p> 142 <a class="indexterm" name="id2634165"></a> 143 <a class="indexterm" name="id2634171"></a> 144 144 Most traditionally configured UNIX print servers acting on behalf of 145 145 Samba's Windows clients represented a really simple setup. Their only … … 150 150 be installed on each and every client for the target device. 151 151 </p><p> 152 <a class="indexterm" name="id26 27227"></a>153 <a class="indexterm" name="id26 27234"></a>152 <a class="indexterm" name="id2634193"></a> 153 <a class="indexterm" name="id2634200"></a> 154 154 It is possible to configure CUPS, Samba, and your Windows clients in the 155 155 same traditional and simple way. When CUPS printers are configured … … 165 165 attached to the Windows client. You then redirect output to a raw network 166 166 print queue. This procedure may be followed to achieve this: 167 </p><div class="procedure"><a name="id26 27258"></a><p class="title"><b>Procedure 22.1. Configuration Steps for Raw CUPS Printing Support</b></p><ol type="1"><li><p>168 <a class="indexterm" name="id26 27270"></a>167 </p><div class="procedure"><a name="id2634224"></a><p class="title"><b>Procedure 22.1. Configuration Steps for Raw CUPS Printing Support</b></p><ol type="1"><li><p> 168 <a class="indexterm" name="id2634236"></a> 169 169 Edit <code class="filename">/etc/cups/mime.types</code> to uncomment the line 170 170 near the end of the file that has: … … 173 173 </pre><p> 174 174 </p></li><li><p> 175 <a class="indexterm" name="id26 27297"></a>175 <a class="indexterm" name="id2634263"></a> 176 176 Do the same for the file <code class="filename">/etc/cups/mime.convs</code>. 177 177 </p></li><li><p> … … 182 182 </p></li><li><p> 183 183 In the <code class="filename">smb.conf</code> file <code class="constant">[printers]</code> section add 184 <a class="link" href="smb.conf.5.html#USECLIENTDRIVER" >use client driver = Yes</a>,184 <a class="link" href="smb.conf.5.html#USECLIENTDRIVER" target="_top">use client driver = Yes</a>, 185 185 and in the <code class="constant">[global]</code> section add 186 <a class="link" href="smb.conf.5.html#PRINTING" >printing = CUPS</a>, plus187 <a class="link" href="smb.conf.5.html#PRINTCAP" >printcap = CUPS</a>.186 <a class="link" href="smb.conf.5.html#PRINTING" target="_top">printing = CUPS</a>, plus 187 <a class="link" href="smb.conf.5.html#PRINTCAP" target="_top">printcap = CUPS</a>. 188 188 </p></li><li><p> 189 189 Install the printer as if it is a local printer, that is, Printing to <code class="constant">LPT1:</code>. … … 194 194 Here, the name <code class="constant">raw_q</code> is the name you gave the print 195 195 queue in the CUPS environment. 196 </p></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id26 27425"></a>Installation of Windows Client Drivers</h3></div></div></div><p>196 </p></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2634391"></a>Installation of Windows Client Drivers</h3></div></div></div><p> 197 197 The printer drivers on the Windows clients may be installed 198 198 in two functionally different ways: … … 201 201 printing and uses a <code class="filename">\\sambaserver\printershare</code> 202 202 type of connection.</p></li><li><p> 203 <a class="indexterm" name="id26 27455"></a>203 <a class="indexterm" name="id2634421"></a> 204 204 Deposit and prepare the drivers (for later download) on 205 205 the print server (Samba); this enables the clients to use … … 212 212 are used accidentally. 213 213 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="cups-raw"></a>Explicitly Enable “<span class="quote">raw</span>” Printing for <span class="emphasis"><em>application/octet-stream</em></span></h3></div></div></div><p> 214 <a class="indexterm" name="id26 27501"></a>215 <a class="indexterm" name="id26 27508"></a>216 <a class="indexterm" name="id26 27515"></a>214 <a class="indexterm" name="id2634467"></a> 215 <a class="indexterm" name="id2634474"></a> 216 <a class="indexterm" name="id2634481"></a> 217 217 If you use the first option (drivers are installed on the client 218 218 side), there is one setting to take care of: CUPS needs to be told … … 226 226 application/octet-stream 227 227 </pre><p> 228 <a class="indexterm" name="id26 27570"></a>229 <a class="indexterm" name="id26 27577"></a>228 <a class="indexterm" name="id2634536"></a> 229 <a class="indexterm" name="id2634543"></a> 230 230 In <code class="filename">/etc/cups/mime.convs</code>, have this line: 231 <a class="indexterm" name="id26 27590"></a>231 <a class="indexterm" name="id2634556"></a> 232 232 </p><pre class="programlisting"> 233 233 application/octet-stream application/vnd.cups-raw 0 - … … 240 240 not <span class="emphasis"><em>enforce</em></span> “<span class="quote">raw</span>” printing, it only <span class="emphasis"><em>allows</em></span> it. 241 241 </p></div><p><b>Background. </b> 242 <a class="indexterm" name="id26 27654"></a>243 <a class="indexterm" name="id26 27661"></a>242 <a class="indexterm" name="id2634620"></a> 243 <a class="indexterm" name="id2634627"></a> 244 244 That CUPS is a more security-aware printing system than traditional ones does not by default allow a user to 245 245 send deliberate (possibly binary) data to printing devices. This could be easily abused to launch a … … 255 255 more advanced CUPS/Samba printing, simply skip the remaining sections 256 256 of this chapter. 257 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id26 27712"></a>Driver Upload Methods</h3></div></div></div><p>257 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2634678"></a>Driver Upload Methods</h3></div></div></div><p> 258 258 This section describes three familiar methods, plus one new one, by which 259 259 printer drivers may be uploaded. 260 260 </p><p> 261 <a class="indexterm" name="id26 27726"></a>261 <a class="indexterm" name="id2634692"></a> 262 262 If you want to use the MS-RPC-type printing, you must upload the 263 263 drivers onto the Samba server first (<em class="parameter"><code>[print$]</code></em> … … 268 268 three methods of preparing the client drivers on the Samba server: 269 269 </p><div class="itemizedlist"><ul type="disc"><li><p> 270 <a class="indexterm" name="id26 27763"></a>270 <a class="indexterm" name="id2634729"></a> 271 271 The GUI, “<span class="quote">Add Printer Wizard</span>” <span class="emphasis"><em>upload-from-a-Windows-client</em></span> method. 272 272 </p></li><li><p> 273 273 The command line, “<span class="quote">smbclient/rpcclient</span>” upload-from-a-UNIX-workstation method. 274 274 </p></li><li><p> 275 <a class="indexterm" name="id26 27791"></a>275 <a class="indexterm" name="id2634757"></a> 276 276 The Imprints tool set method. 277 277 </p></li></ul></div><p> 278 <a class="indexterm" name="id26 27803"></a>278 <a class="indexterm" name="id2634769"></a> 279 279 These three methods apply to CUPS all the same. The <code class="literal">cupsaddsmb</code> utility is a new and more 280 280 convenient way to load the Windows drivers into Samba and is provided if you use CUPS. … … 282 282 <code class="literal">cupsaddsmb</code> is discussed in much detail later in this chapter. But we first 283 283 explore the CUPS filtering system and compare the Windows and UNIX printing architectures. 284 </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id26 27834"></a>Advanced Intelligent Printing with PostScript Driver Download</h2></div></div></div><p>285 <a class="indexterm" name="id26 27842"></a>284 </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2634800"></a>Advanced Intelligent Printing with PostScript Driver Download</h2></div></div></div><p> 285 <a class="indexterm" name="id2634808"></a> 286 286 We now know how to set up a “<span class="quote">dump</span>” print server, that is, a server that spools 287 287 print jobs “<span class="quote">raw</span>”, leaving the print data untouched. 288 288 </p><p> 289 289 You might need to set up CUPS in a smarter way. The reasons could be manifold: 290 </p><a class="indexterm" name="id26 27866"></a><a class="indexterm" name="id2627873"></a><a class="indexterm" name="id2627880"></a><div class="itemizedlist"><ul type="disc"><li><p>Maybe your boss wants to get monthly statistics: Which290 </p><a class="indexterm" name="id2634832"></a><a class="indexterm" name="id2634839"></a><a class="indexterm" name="id2634846"></a><div class="itemizedlist"><ul type="disc"><li><p>Maybe your boss wants to get monthly statistics: Which 291 291 printer did how many pages? What was the average data size of a job? 292 292 What was the average print run per day? What are the typical hourly … … 304 304 CUPS filtering system, how it works, and how you can tweak it. 305 305 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="gdipost"></a>GDI on Windows, PostScript on UNIX</h3></div></div></div><p> 306 <a class="indexterm" name="id26 27950"></a>307 <a class="indexterm" name="id26 27956"></a>306 <a class="indexterm" name="id2634915"></a> 307 <a class="indexterm" name="id2634922"></a> 308 308 Network printing is one of the most complicated and error-prone 309 309 day-to-day tasks any user or administrator may encounter. This is 310 310 true for all OS platforms, and there are reasons it is so. 311 311 </p><p> 312 <a class="indexterm" name="id26 27970"></a>313 <a class="indexterm" name="id26 27976"></a>314 <a class="indexterm" name="id26 27983"></a>315 <a class="indexterm" name="id26 27990"></a>316 <a class="indexterm" name="id26 27996"></a>312 <a class="indexterm" name="id2634935"></a> 313 <a class="indexterm" name="id2634942"></a> 314 <a class="indexterm" name="id2634949"></a> 315 <a class="indexterm" name="id2634956"></a> 316 <a class="indexterm" name="id2634963"></a> 317 317 You can't expect to throw just any file format at a printer and have it get printed. A file format conversion 318 318 must take place. The problem is that there is no common standard for print file formats across all … … 321 321 used page description languages (PDLs), there are still many manufacturers who “<span class="quote">roll their own</span>” 322 322 (their reasons may be unacceptable license fees for using printer-embedded PostScript interpreters, and so on). 323 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id26 28025"></a>Windows Drivers, GDI, and EMF</h3></div></div></div><p>324 <a class="indexterm" name="id26 28033"></a>325 <a class="indexterm" name="id26 28040"></a>326 <a class="indexterm" name="id26 28046"></a>327 <a class="indexterm" name="id26 28053"></a>323 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2634992"></a>Windows Drivers, GDI, and EMF</h3></div></div></div><p> 324 <a class="indexterm" name="id2635000"></a> 325 <a class="indexterm" name="id2635006"></a> 326 <a class="indexterm" name="id2635013"></a> 327 <a class="indexterm" name="id2635020"></a> 328 328 In Windows OS, the format conversion job is done by the printer drivers. On MS Windows OS platforms all 329 329 application programmers have at their disposal a built-in API, the graphical device interface (GDI), as part … … 336 336 driver and converted to the printer-specific file format. 337 337 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> 338 <a class="indexterm" name="id26 28089"></a>339 <a class="indexterm" name="id26 28095"></a>340 <a class="indexterm" name="id26 28102"></a>338 <a class="indexterm" name="id2635055"></a> 339 <a class="indexterm" name="id2635062"></a> 340 <a class="indexterm" name="id2635069"></a> 341 341 To the GDI foundation in MS Windows, Apple has chosen to put paper and screen output on a common foundation 342 for its (BSD-UNIX-based, did you know?) Mac OS X and Darwin operating <a class="indexterm" name="id26 28112"></a> <a class="indexterm" name="id2628119"></a>343 <a class="indexterm" name="id26 28126"></a> <a class="indexterm" name="id2628132"></a> systems.342 for its (BSD-UNIX-based, did you know?) Mac OS X and Darwin operating <a class="indexterm" name="id2635079"></a> <a class="indexterm" name="id2635086"></a> 343 <a class="indexterm" name="id2635093"></a> <a class="indexterm" name="id2635099"></a> systems. 344 344 Apple's <span class="emphasis"><em>core graphic engine</em></span> uses a <span class="emphasis"><em>PDF</em></span> derivative for all display work. 345 345 </p></div><p> 346 346 The example in <a class="link" href="CUPS-printing.html#1small" title="Figure 22.1. Windows Printing to a Local Printer.">Windows Printing to a Local Printer</a> illustrates local Windows 347 347 printing. 348 </p><div class="figure"><a name="1small"></a><p class="title"><b>Figure 22.1. Windows Printing to a Local Printer.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/1small.png" alt="Windows Printing to a Local Printer."></div></div></div><br class="figure-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id26 28203"></a>UNIX Printfile Conversion and GUI Basics</h3></div></div></div><p>349 <a class="indexterm" name="id26 28211"></a>350 <a class="indexterm" name="id26 28218"></a>351 <a class="indexterm" name="id26 28225"></a>352 <a class="indexterm" name="id26 28232"></a>348 </p><div class="figure"><a name="1small"></a><p class="title"><b>Figure 22.1. Windows Printing to a Local Printer.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/1small.png" alt="Windows Printing to a Local Printer."></div></div></div><br class="figure-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2635170"></a>UNIX Printfile Conversion and GUI Basics</h3></div></div></div><p> 349 <a class="indexterm" name="id2635179"></a> 350 <a class="indexterm" name="id2635186"></a> 351 <a class="indexterm" name="id2635192"></a> 352 <a class="indexterm" name="id2635199"></a> 353 353 In UNIX and Linux, there is no comparable layer built into the OS kernel(s) or the X (screen display) server. 354 354 Every application is responsible for itself to create its print output. Fortunately, most use PostScript and … … 364 364 your system; there are separate ones for fonts used for X display and fonts to be used on paper. 365 365 </p><p><b>Background. </b> 366 <a class="indexterm" name="id26 28282"></a>367 <a class="indexterm" name="id26 28289"></a>368 <a class="indexterm" name="id26 28295"></a>369 <a class="indexterm" name="id26 28302"></a>370 <a class="indexterm" name="id26 28309"></a>371 <a class="indexterm" name="id26 28316"></a>372 <a class="indexterm" name="id26 28323"></a>373 <a class="indexterm" name="id26 28329"></a>374 <a class="indexterm" name="id26 28336"></a>375 <a class="indexterm" name="id26 28343"></a>366 <a class="indexterm" name="id2635249"></a> 367 <a class="indexterm" name="id2635256"></a> 368 <a class="indexterm" name="id2635263"></a> 369 <a class="indexterm" name="id2635269"></a> 370 <a class="indexterm" name="id2635276"></a> 371 <a class="indexterm" name="id2635283"></a> 372 <a class="indexterm" name="id2635290"></a> 373 <a class="indexterm" name="id2635297"></a> 374 <a class="indexterm" name="id2635304"></a> 375 <a class="indexterm" name="id2635310"></a> 376 376 The PostScript programming language is an “<span class="quote">invention</span>” by Adobe, but its specifications have been 377 377 published extensively. Its strength lies in its powerful abilities to describe graphical objects (fonts, … … 385 385 program or on paper by a printer. 386 386 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="post-and-ghost"></a>PostScript and Ghostscript</h3></div></div></div><p> 387 <a class="indexterm" name="id26 28393"></a>388 <a class="indexterm" name="id26 28400"></a>389 <a class="indexterm" name="id26 28409"></a>390 <a class="indexterm" name="id26 28418"></a>391 <a class="indexterm" name="id26 28425"></a>387 <a class="indexterm" name="id2635360"></a> 388 <a class="indexterm" name="id2635367"></a> 389 <a class="indexterm" name="id2635376"></a> 390 <a class="indexterm" name="id2635385"></a> 391 <a class="indexterm" name="id2635392"></a> 392 392 So UNIX is lacking a common ground for printing on paper and displaying on screen. Despite this unfavorable 393 393 legacy for UNIX, basic printing is fairly easy if you have PostScript printers at your disposal. The reason is … … 398 398 different than PostScript printing a file from a Windows origin. 399 399 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> 400 <a class="indexterm" name="id26 28454"></a>401 <a class="indexterm" name="id26 28461"></a>402 <a class="indexterm" name="id26 28467"></a>400 <a class="indexterm" name="id2635421"></a> 401 <a class="indexterm" name="id2635428"></a> 402 <a class="indexterm" name="id2635435"></a> 403 403 Traditional UNIX programs and printing systems while using PostScript are largely not 404 404 PPD-aware. PPDs are “<span class="quote">PostScript Printer Description</span>” files. They enable you to specify and … … 407 407 there is CUPS. as illustrated in <a class="link" href="CUPS-printing.html#2small" title="Figure 22.2. Printing to a PostScript Printer.">Printing to a PostScript Printer</a>. 408 408 </p></div><div class="figure"><a name="2small"></a><p class="title"><b>Figure 22.2. Printing to a PostScript Printer.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/2small.png" alt="Printing to a PostScript Printer."></div></div></div><br class="figure-break"><p> 409 <a class="indexterm" name="id26 28546"></a>409 <a class="indexterm" name="id2635513"></a> 410 410 However, there are other types of printers out there. These do not know how to print PostScript. They use 411 411 their own PDL, often proprietary. To print to them is much more demanding. Since your UNIX applications mostly 412 412 produce PostScript, and since these devices do not understand PostScript, you need to convert the print files 413 413 to a format suitable for your printer on the host before you can send it away. 414 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id26 28562"></a>Ghostscript: The Software RIP for Non-PostScript Printers</h3></div></div></div><p>415 <a class="indexterm" name="id26 28570"></a>414 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2635529"></a>Ghostscript: The Software RIP for Non-PostScript Printers</h3></div></div></div><p> 415 <a class="indexterm" name="id2635538"></a> 416 416 Here is where Ghostscript kicks in. Ghostscript is the traditional (and quite powerful) PostScript interpreter 417 417 used on UNIX platforms. It is a RIP in software, capable of doing a <span class="emphasis"><em>lot</em></span> of file format … … 420 420 <a class="link" href="CUPS-printing.html#3small" title="Figure 22.3. Ghostscript as a RIP for Non-PostScript Printers.">Ghostscript as a RIP for Non-PostScript Printers</a>. 421 421 </p><div class="figure"><a name="3small"></a><p class="title"><b>Figure 22.3. Ghostscript as a RIP for Non-PostScript Printers.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/3small.png" alt="Ghostscript as a RIP for Non-PostScript Printers."></div></div></div><br class="figure-break"><div class="tip" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Tip</h3><p> 422 <a class="indexterm" name="id26 28641"></a>423 <a class="indexterm" name="id26 28648"></a>424 <a class="indexterm" name="id26 28654"></a>422 <a class="indexterm" name="id2635609"></a> 423 <a class="indexterm" name="id2635615"></a> 424 <a class="indexterm" name="id2635622"></a> 425 425 Use the “<span class="quote">gs -h</span>” command to check for all built-in “<span class="quote">devices</span>” on your Ghostscript 426 426 version. If you specify a parameter of <em class="parameter"><code>-sDEVICE=png256</code></em> on your Ghostscript command … … 430 430 initially put under the “<span class="quote">AFPL</span>” license, but re-released under the GNU GPL as soon as the next 431 431 AFPL version appears. GNU Ghostscript is probably the version installed on most Samba systems. But it has some 432 deficiencies. <a class="indexterm" name="id26 28693"></a> Therefore, ESP Ghostscript was developed as an enhancement over GNU Ghostscript,432 deficiencies. <a class="indexterm" name="id2635660"></a> Therefore, ESP Ghostscript was developed as an enhancement over GNU Ghostscript, 433 433 with lots of bug-fixes, additional devices, and improvements. It is jointly maintained by developers from 434 434 CUPS, Gutenprint, MandrakeSoft, SuSE, Red Hat, and Debian. It includes the “<span class="quote">cups</span>” device 435 435 (essential to print to non-PS printers from CUPS). 436 </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id26 28716"></a>PostScript Printer Description (PPD) Specification</h3></div></div></div><p>437 <a class="indexterm" name="id26 28724"></a>438 <a class="indexterm" name="id26 28731"></a>439 <a class="indexterm" name="id26 28737"></a>436 </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2635683"></a>PostScript Printer Description (PPD) Specification</h3></div></div></div><p> 437 <a class="indexterm" name="id2635692"></a> 438 <a class="indexterm" name="id2635698"></a> 439 <a class="indexterm" name="id2635705"></a> 440 440 While PostScript in essence is a PDL to represent the page layout in a device-independent way, real-world 441 441 print jobs are always ending up being output on hardware with device-specific features. To take care of all … … 459 459 file created by the driver. 460 460 </p><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p> 461 <a class="indexterm" name="id26 28777"></a>462 <a class="indexterm" name="id26 28784"></a>461 <a class="indexterm" name="id2635745"></a> 462 <a class="indexterm" name="id2635751"></a> 463 463 A PostScript file that was created to contain device-specific commands 464 464 for achieving a certain print job output (e.g., duplexed, stapled, and … … 466 466 may not be printable at all on other models; it also may not be fit 467 467 for further processing by software (e.g., by a PDF distilling program). 468 </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id26 28799"></a>Using Windows-Formatted Vendor PPDs</h3></div></div></div><p>469 <a class="indexterm" name="id26 28807"></a>470 <a class="indexterm" name="id26 28814"></a>471 <a class="indexterm" name="id26 28820"></a>468 </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2635766"></a>Using Windows-Formatted Vendor PPDs</h3></div></div></div><p> 469 <a class="indexterm" name="id2635774"></a> 470 <a class="indexterm" name="id2635781"></a> 471 <a class="indexterm" name="id2635788"></a> 472 472 CUPS can handle all spec-compliant PPDs as supplied by the manufacturers for their PostScript models. Even if 473 473 a vendor does not mention our favorite OS in his or her manuals and brochures, you can safely trust this: … … 480 480 first pit stops. 481 481 </p></div><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p> 482 <a class="indexterm" name="id26 28860"></a>483 <a class="indexterm" name="id26 28867"></a>482 <a class="indexterm" name="id2635828"></a> 483 <a class="indexterm" name="id2635834"></a> 484 484 For real PostScript printers, <span class="emphasis"><em>do not</em></span> use the <span class="emphasis"><em>Foomatic</em></span> or 485 485 <span class="emphasis"><em>cupsomatic</em></span> PPDs from Linuxprinting.org. With these devices, the original vendor-provided 486 486 PPDs are always the first choice. 487 487 </p></div><div class="tip" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Tip</h3><p> 488 <a class="indexterm" name="id26 28892"></a>488 <a class="indexterm" name="id2635859"></a> 489 489 If you are looking for an original vendor-provided PPD of a specific device, and you know that an NT4 box (or 490 490 any other Windows box) on your LAN has the PostScript driver installed, just use <code class="literal">smbclient 491 491 //NT4-box/print\$ -U username</code> to access the Windows directory where all printer driver files are 492 492 stored. First look in the <code class="filename">W32X86/2</code> subdirectory for the PPD you are seeking. 493 </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id26 28918"></a>CUPS Also Uses PPDs for Non-PostScript Printers</h3></div></div></div><p>494 <a class="indexterm" name="id26 28927"></a>495 <a class="indexterm" name="id26 28934"></a>496 <a class="indexterm" name="id26 28940"></a>493 </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2635886"></a>CUPS Also Uses PPDs for Non-PostScript Printers</h3></div></div></div><p> 494 <a class="indexterm" name="id2635894"></a> 495 <a class="indexterm" name="id2635901"></a> 496 <a class="indexterm" name="id2635908"></a> 497 497 CUPS also uses specially crafted PPDs to handle non-PostScript printers. These PPDs are usually not available 498 498 from the vendors (and no, you can't just take the PPD of a PostScript printer with the same model name and 499 499 hope it works for the non-PostScript version too). To understand how these PPDs work for non-PS printers, we 500 500 first need to dive deeply into the CUPS filtering and file format conversion architecture. Stay tuned. 501 </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id26 28958"></a>The CUPS Filtering Architecture</h2></div></div></div><p>502 <a class="indexterm" name="id26 28966"></a>503 <a class="indexterm" name="id26 28973"></a>504 <a class="indexterm" name="id26 28980"></a>505 <a class="indexterm" name="id26 28986"></a>506 <a class="indexterm" name="id26 28993"></a>501 </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2635925"></a>The CUPS Filtering Architecture</h2></div></div></div><p> 502 <a class="indexterm" name="id2635934"></a> 503 <a class="indexterm" name="id2635940"></a> 504 <a class="indexterm" name="id2635947"></a> 505 <a class="indexterm" name="id2635954"></a> 506 <a class="indexterm" name="id2635961"></a> 507 507 The core of the CUPS filtering system is based on Ghostscript. In addition to Ghostscript, CUPS uses some 508 508 other filters of its own. You (or your OS vendor) may have plugged in even more filters. CUPS handles all data … … 515 515 If CUPS rasterizes a PostScript file natively to a bitmap, this is done in two stages: 516 516 </p><div class="itemizedlist"><ul type="disc"><li><p> 517 <a class="indexterm" name="id26 29023"></a>518 <a class="indexterm" name="id26 29030"></a>517 <a class="indexterm" name="id2635991"></a> 518 <a class="indexterm" name="id2635998"></a> 519 519 The first stage uses a Ghostscript device named “<span class="quote">cups</span>” 520 520 (this is since version 1.1.15) and produces a generic raster format 521 521 called “<span class="quote">CUPS raster</span>”. 522 522 </p></li><li><p> 523 <a class="indexterm" name="id26 29050"></a>523 <a class="indexterm" name="id2636018"></a> 524 524 The second stage uses a “<span class="quote">raster driver</span>” that converts 525 525 the generic CUPS raster to a device-specific raster. 526 526 </p></li></ul></div><p> 527 <a class="indexterm" name="id26 29067"></a>528 <a class="indexterm" name="id26 29074"></a>529 <a class="indexterm" name="id26 29081"></a>527 <a class="indexterm" name="id2636035"></a> 528 <a class="indexterm" name="id2636042"></a> 529 <a class="indexterm" name="id2636048"></a> 530 530 Make sure your Ghostscript version has the “<span class="quote">cups</span>” device compiled in (check with <code class="literal">gs -h | 531 531 grep cups</code>). Otherwise you may encounter the dreaded <code class="computeroutput">Unable to convert file 532 532 0</code> in your CUPS error_log file. To have “<span class="quote">cups</span>” as a device in your Ghostscript, 533 533 you either need to patch GNU Ghostscript and recompile or use 534 <a class="indexterm" name="id26 29112"></a><a class="ulink" href="http://www.cups.org/ghostscript.php" target="_top">ESP Ghostscript</a>. The superior alternative is ESP534 <a class="indexterm" name="id2636079"></a><a class="ulink" href="http://www.cups.org/ghostscript.php" target="_top">ESP Ghostscript</a>. The superior alternative is ESP 535 535 Ghostscript. It supports not just CUPS, but 300 other devices (while GNU Ghostscript supports only about 180). 536 536 Because of this broad output device support, ESP Ghostscript is the first choice for non-CUPS spoolers, too. 537 537 It is now recommended by Linuxprinting.org for all spoolers. 538 538 </p><p> 539 <a class="indexterm" name="id26 29134"></a>540 <a class="indexterm" name="id26 29141"></a>541 <a class="indexterm" name="id26 29148"></a>542 <a class="indexterm" name="id26 29155"></a>539 <a class="indexterm" name="id2636102"></a> 540 <a class="indexterm" name="id2636109"></a> 541 <a class="indexterm" name="id2636115"></a> 542 <a class="indexterm" name="id2636122"></a> 543 543 CUPS printers may be set up to use external rendering paths. One of the most common is provided by the 544 544 Foomatic/cupsomatic concept from <a class="ulink" href="http://www.linuxprinting.org/" target="_top">Linuxprinting.org</a>. This 545 545 uses the classical Ghostscript approach, doing everything in one step. It does not use the 546 546 “<span class="quote">cups</span>” device, but one of the many others. However, even for Foomatic/cupsomatic usage, best 547 results and <a class="indexterm" name="id26 29177"></a> broadest printer547 results and <a class="indexterm" name="id2636145"></a> broadest printer 548 548 model support is provided by ESP Ghostscript (more about Foomatic/cupsomatic, particularly the new version 549 549 called now <span class="emphasis"><em>foomatic-rip</em></span>, follows). 550 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id26 29194"></a>MIME Types and CUPS Filters</h3></div></div></div><p>551 <a class="indexterm" name="id26 29202"></a>552 <a class="indexterm" name="id26 29211"></a>553 <a class="indexterm" name="id26 29218"></a>554 <a class="indexterm" name="id26 29224"></a>555 <a class="indexterm" name="id26 29231"></a>550 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2636161"></a>MIME Types and CUPS Filters</h3></div></div></div><p> 551 <a class="indexterm" name="id2636169"></a> 552 <a class="indexterm" name="id2636178"></a> 553 <a class="indexterm" name="id2636185"></a> 554 <a class="indexterm" name="id2636192"></a> 555 <a class="indexterm" name="id2636199"></a> 556 556 CUPS reads the file <code class="filename">/etc/cups/mime.types</code> (and all other files carrying a 557 557 <code class="filename">*.types</code> suffix in the same directory) upon startup. These files contain the MIME type … … 559 559 man page for <code class="filename">mime.types</code> and in the comments section of the 560 560 <code class="filename">mime.types</code> file itself. A simple rule reads like this: 561 <a class="indexterm" name="id26 29268"></a>561 <a class="indexterm" name="id2636236"></a> 562 562 </p><pre class="programlisting"> 563 563 application/pdf pdf string(0,%PDF) 564 564 </pre><p> 565 <a class="indexterm" name="id26 29281"></a>566 <a class="indexterm" name="id26 29288"></a>565 <a class="indexterm" name="id2636249"></a> 566 <a class="indexterm" name="id2636256"></a> 567 567 This means if a filename has a <code class="filename">.pdf</code> suffix or if the magic string 568 568 <span class="emphasis"><em>%PDF</em></span> is right at the beginning of the file itself (offset 0 from the start), then it is a … … 571 571 application/postscript ai eps ps string(0,%!) string(0,<04>%!) 572 572 </pre><p> 573 <a class="indexterm" name="id26 29321"></a>574 <a class="indexterm" name="id26 29328"></a>575 <a class="indexterm" name="id26 29335"></a>576 <a class="indexterm" name="id26 29342"></a>577 <a class="indexterm" name="id26 29348"></a>578 <a class="indexterm" name="id26 29355"></a>573 <a class="indexterm" name="id2636289"></a> 574 <a class="indexterm" name="id2636296"></a> 575 <a class="indexterm" name="id2636303"></a> 576 <a class="indexterm" name="id2636310"></a> 577 <a class="indexterm" name="id2636316"></a> 578 <a class="indexterm" name="id2636323"></a> 579 579 If the filename has one of the suffixes <code class="filename">.ai</code>, <code class="filename">.eps</code>, 580 580 <code class="filename">.ps</code>, or if the file itself starts with one of the strings <span class="emphasis"><em>%!</em></span> or … … 582 582 (<em class="parameter"><code>application/postscript</code></em>). 583 583 </p><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p> 584 <a class="indexterm" name="id26 29399"></a>584 <a class="indexterm" name="id2636368"></a> 585 585 Don't confuse the other mime.types files your system might be using 586 586 with the one in the <code class="filename">/etc/cups/</code> directory. 587 587 </p></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> 588 <a class="indexterm" name="id26 29418"></a>589 <a class="indexterm" name="id26 29425"></a>590 <a class="indexterm" name="id26 29432"></a>591 <a class="indexterm" name="id26 29439"></a>592 <a class="indexterm" name="id26 29445"></a>588 <a class="indexterm" name="id2636386"></a> 589 <a class="indexterm" name="id2636394"></a> 590 <a class="indexterm" name="id2636400"></a> 591 <a class="indexterm" name="id2636407"></a> 592 <a class="indexterm" name="id2636414"></a> 593 593 There is an important difference between two similar MIME types in CUPS: one is 594 594 <em class="parameter"><code>application/postscript</code></em>, the other is … … 601 601 <em class="parameter"><code>pstops</code></em> filter. pstops uses information contained in the PPD to do the transformation. 602 602 </p></div><p> 603 <a class="indexterm" name="id26 29508"></a>604 <a class="indexterm" name="id26 29515"></a>605 <a class="indexterm" name="id26 29521"></a>606 <a class="indexterm" name="id26 29528"></a>607 <a class="indexterm" name="id26 29535"></a>608 <a class="indexterm" name="id26 29541"></a>609 <a class="indexterm" name="id26 29548"></a>610 <a class="indexterm" name="id26 29554"></a>611 <a class="indexterm" name="id26 29561"></a>612 <a class="indexterm" name="id26 29568"></a>613 <a class="indexterm" name="id26 29575"></a>614 <a class="indexterm" name="id26 29582"></a>615 <a class="indexterm" name="id26 29588"></a>616 <a class="indexterm" name="id26 29595"></a>617 <a class="indexterm" name="id26 29602"></a>618 <a class="indexterm" name="id26 29609"></a>603 <a class="indexterm" name="id2636476"></a> 604 <a class="indexterm" name="id2636483"></a> 605 <a class="indexterm" name="id2636490"></a> 606 <a class="indexterm" name="id2636496"></a> 607 <a class="indexterm" name="id2636503"></a> 608 <a class="indexterm" name="id2636510"></a> 609 <a class="indexterm" name="id2636516"></a> 610 <a class="indexterm" name="id2636523"></a> 611 <a class="indexterm" name="id2636530"></a> 612 <a class="indexterm" name="id2636536"></a> 613 <a class="indexterm" name="id2636543"></a> 614 <a class="indexterm" name="id2636550"></a> 615 <a class="indexterm" name="id2636557"></a> 616 <a class="indexterm" name="id2636564"></a> 617 <a class="indexterm" name="id2636571"></a> 618 <a class="indexterm" name="id2636577"></a> 619 619 CUPS can handle ASCII text, HP-GL, PDF, PostScript, DVI, and 620 620 many image formats (GIF, PNG, TIFF, JPEG, Photo-CD, SUN-Raster, 621 621 PNM, PBM, SGI-RGB, and more) and their associated MIME types 622 622 with its filters. 623 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id26 29622"></a>MIME Type Conversion Rules</h3></div></div></div><p>624 <a class="indexterm" name="id26 29630"></a>625 <a class="indexterm" name="id26 29636"></a>626 <a class="indexterm" name="id26 29643"></a>627 <a class="indexterm" name="id26 29650"></a>628 <a class="indexterm" name="id26 29657"></a>623 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2636590"></a>MIME Type Conversion Rules</h3></div></div></div><p> 624 <a class="indexterm" name="id2636598"></a> 625 <a class="indexterm" name="id2636605"></a> 626 <a class="indexterm" name="id2636612"></a> 627 <a class="indexterm" name="id2636619"></a> 628 <a class="indexterm" name="id2636626"></a> 629 629 CUPS reads the file <code class="filename">/etc/cups/mime.convs</code> 630 630 (and all other files named with a <code class="filename">*.convs</code> … … 637 637 application/pdf application/postscript 33 pdftops 638 638 </pre><p> 639 <a class="indexterm" name="id26 29689"></a>639 <a class="indexterm" name="id2636658"></a> 640 640 This means that the <em class="parameter"><code>pdftops</code></em> filter will take 641 641 <em class="parameter"><code>application/pdf</code></em> as input and produce … … 643 643 cost of this operation is 33 CUPS-$. The next filter is more 644 644 expensive, costing 66 CUPS-$: 645 <a class="indexterm" name="id26 29717"></a>645 <a class="indexterm" name="id2636686"></a> 646 646 </p><pre class="programlisting"> 647 647 application/vnd.hp-HPGL application/postscript 66 hpgltops 648 648 </pre><p> 649 <a class="indexterm" name="id26 29730"></a>649 <a class="indexterm" name="id2636699"></a> 650 650 This is the <em class="parameter"><code>hpgltops</code></em>, which processes HP-GL 651 651 plotter files to PostScript. 652 <a class="indexterm" name="id26 29744"></a>652 <a class="indexterm" name="id2636713"></a> 653 653 </p><pre class="programlisting"> 654 654 application/octet-stream 655 655 </pre><p> 656 656 Here are two more examples: 657 <a class="indexterm" name="id26 29758"></a>658 <a class="indexterm" name="id26 29765"></a>659 <a class="indexterm" name="id26 29772"></a>660 <a class="indexterm" name="id26 29779"></a>657 <a class="indexterm" name="id2636727"></a> 658 <a class="indexterm" name="id2636734"></a> 659 <a class="indexterm" name="id2636741"></a> 660 <a class="indexterm" name="id2636748"></a> 661 661 </p><pre class="programlisting"> 662 662 application/x-shell application/postscript 33 texttops 663 663 text/plain application/postscript 33 texttops 664 664 </pre><p> 665 <a class="indexterm" name="id26 29794"></a>665 <a class="indexterm" name="id2636762"></a> 666 666 The last two examples name the <em class="parameter"><code>texttops</code></em> filter to work on 667 667 <em class="parameter"><code>text/plain</code></em> as well as on <em class="parameter"><code>application/x-shell</code></em>. (Hint: This 668 668 differentiation is needed for the syntax highlighting feature of <em class="parameter"><code>texttops</code></em>). 669 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id26 29829"></a>Filtering Overview</h3></div></div></div><p>670 <a class="indexterm" name="id26 29837"></a>669 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2636798"></a>Filtering Overview</h3></div></div></div><p> 670 <a class="indexterm" name="id2636806"></a> 671 671 There are many more combinations named in <code class="filename">mime.convs</code>. However, you are not limited to use 672 672 the ones predefined there. You can plug in any filter you like to the CUPS framework. It must meet, or must be … … 674 674 sure it complies with what CUPS needs and put in the right lines in <code class="filename">mime.types</code> and 675 675 <code class="filename">mime.convs</code>; then it will work seamlessly inside CUPS. 676 </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id26 29870"></a>Filter Requirements</h4></div></div></div><p>676 </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2636838"></a>Filter Requirements</h4></div></div></div><p> 677 677 The “<span class="quote">CUPS requirements</span>” for filters are simple. Take filenames or <code class="filename">stdin</code> as 678 678 input and write to <code class="filename">stdout</code>. They should take these arguments: … … 693 693 fed through <code class="filename">stdin</code>). In most cases, it is easy to 694 694 write a simple wrapper script around existing filters to make them work with CUPS. 695 </p></dd></dl></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id26 29986"></a>Prefilters</h3></div></div></div><p>696 <a class="indexterm" name="id26 29994"></a>697 <a class="indexterm" name="id263 0001"></a>698 <a class="indexterm" name="id263 0008"></a>695 </p></dd></dl></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2636955"></a>Prefilters</h3></div></div></div><p> 696 <a class="indexterm" name="id2636963"></a> 697 <a class="indexterm" name="id2636970"></a> 698 <a class="indexterm" name="id2636977"></a> 699 699 As previously stated, PostScript is the central file format to any UNIX-based 700 700 printing system. From PostScript, CUPS generates raster data to feed 701 701 non-PostScript printers. 702 702 </p><p> 703 <a class="indexterm" name="id263 0021"></a>704 <a class="indexterm" name="id263 0028"></a>705 <a class="indexterm" name="id263 0034"></a>706 <a class="indexterm" name="id263 0041"></a>707 <a class="indexterm" name="id263 0048"></a>708 <a class="indexterm" name="id263 0054"></a>709 <a class="indexterm" name="id263 0061"></a>710 <a class="indexterm" name="id263 0068"></a>711 <a class="indexterm" name="id263 0075"></a>712 <a class="indexterm" name="id263 0082"></a>703 <a class="indexterm" name="id2636990"></a> 704 <a class="indexterm" name="id2636997"></a> 705 <a class="indexterm" name="id2637004"></a> 706 <a class="indexterm" name="id2637010"></a> 707 <a class="indexterm" name="id2637017"></a> 708 <a class="indexterm" name="id2637023"></a> 709 <a class="indexterm" name="id2637030"></a> 710 <a class="indexterm" name="id2637037"></a> 711 <a class="indexterm" name="id2637044"></a> 712 <a class="indexterm" name="id2637051"></a> 713 713 But what happens if you send one of the supported non-PS formats to print? Then CUPS runs 714 714 “<span class="quote">prefilters</span>” on these input formats to generate PostScript first. There are prefilters to create … … 720 720 the print options already embedded into the file. This is shown in <a class="link" href="CUPS-printing.html#4small" title="Figure 22.4. Prefiltering in CUPS to Form PostScript.">Prefiltering in 721 721 CUPS to Form PostScript</a>. 722 </p><div class="figure"><a name="4small"></a><p class="title"><b>Figure 22.4. Prefiltering in CUPS to Form PostScript.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/4small.png" width="135" alt="Prefiltering in CUPS to Form PostScript."></div></div></div><br class="figure-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id263 0173"></a>pstops</h3></div></div></div><p>723 <a class="indexterm" name="id263 0181"></a>724 <a class="indexterm" name="id263 0188"></a>725 <a class="indexterm" name="id263 0195"></a>726 <a class="indexterm" name="id263 0202"></a>727 <a class="indexterm" name="id263 0209"></a>728 <a class="indexterm" name="id263 0216"></a>729 <a class="indexterm" name="id263 0223"></a>722 </p><div class="figure"><a name="4small"></a><p class="title"><b>Figure 22.4. Prefiltering in CUPS to Form PostScript.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/4small.png" width="135" alt="Prefiltering in CUPS to Form PostScript."></div></div></div><br class="figure-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2637143"></a>pstops</h3></div></div></div><p> 723 <a class="indexterm" name="id2637151"></a> 724 <a class="indexterm" name="id2637158"></a> 725 <a class="indexterm" name="id2637165"></a> 726 <a class="indexterm" name="id2637172"></a> 727 <a class="indexterm" name="id2637179"></a> 728 <a class="indexterm" name="id2637186"></a> 729 <a class="indexterm" name="id2637193"></a> 730 730 <span class="emphasis"><em>pstops</em></span> is a filter that is used to convert <em class="parameter"><code>application/postscript</code></em> to 731 731 <em class="parameter"><code>application/vnd.cups-postscript</code></em>. As stated earlier, this filter inserts all … … 743 743 </p></li><li><p>Counting the pages of the job to insert the accounting 744 744 information into the <code class="filename">/var/log/cups/page_log</code>. 745 </p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id263 0341"></a>pstoraster</h3></div></div></div><p>746 <a class="indexterm" name="id263 0349"></a>747 <a class="indexterm" name="id263 0356"></a>748 <a class="indexterm" name="id263 0362"></a>745 </p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2637311"></a>pstoraster</h3></div></div></div><p> 746 <a class="indexterm" name="id2637319"></a> 747 <a class="indexterm" name="id2637326"></a> 748 <a class="indexterm" name="id2637332"></a> 749 749 <em class="parameter"><code>pstoraster</code></em> is at the core of the CUPS filtering system. It is responsible for the first 750 750 stage of the rasterization process. Its input is of MIME type application/vnd.cups-postscript; its output is … … 754 754 Intermediate Raster Format diagram</a>. 755 755 </p><div class="figure"><a name="cups-raster"></a><p class="title"><b>Figure 22.6. PostScript to Intermediate Raster Format.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/6small.png" width="135" alt="PostScript to Intermediate Raster Format."></div></div></div><br class="figure-break"><p> 756 <a class="indexterm" name="id263 0439"></a>757 <a class="indexterm" name="id263 0446"></a>758 <a class="indexterm" name="id263 0452"></a>759 <a class="indexterm" name="id263 0459"></a>756 <a class="indexterm" name="id2637408"></a> 757 <a class="indexterm" name="id2637415"></a> 758 <a class="indexterm" name="id2637422"></a> 759 <a class="indexterm" name="id2637429"></a> 760 760 CUPS raster is a generic raster format with powerful features. It is able to include per-page information, 761 761 color profiles, and more, to be used by the downstream raster drivers. Its MIME type is registered with IANA … … 767 767 Ghostscript illustration</a>. 768 768 </p><div class="figure"><a name="cups-raster2"></a><p class="title"><b>Figure 22.7. CUPS-Raster Production Using Ghostscript.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/7small.png" alt="CUPS-Raster Production Using Ghostscript."></div></div></div><br class="figure-break"><p> 769 <a class="indexterm" name="id263 0532"></a>770 <a class="indexterm" name="id263 0539"></a>771 <a class="indexterm" name="id263 0546"></a>772 <a class="indexterm" name="id263 0552"></a>769 <a class="indexterm" name="id2637501"></a> 770 <a class="indexterm" name="id2637508"></a> 771 <a class="indexterm" name="id2637515"></a> 772 <a class="indexterm" name="id2637522"></a> 773 773 CUPS versions before version 1.1.15 shipped a binary (or source code) standalone filter, named 774 774 <em class="parameter"><code>pstoraster</code></em>. <em class="parameter"><code>pstoraster</code></em>, which was derived from GNU Ghostscript … … 781 781 If your Ghostscript fails when this command is executed: <code class="literal">gs -h |grep cups</code>, you might not 782 782 be able to print, update your Ghostscript. 783 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id263 0611"></a>imagetops and imagetoraster</h3></div></div></div><p>784 <a class="indexterm" name="id263 0619"></a>785 <a class="indexterm" name="id263 0626"></a>783 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2637580"></a>imagetops and imagetoraster</h3></div></div></div><p> 784 <a class="indexterm" name="id2637588"></a> 785 <a class="indexterm" name="id2637595"></a> 786 786 In the section about prefilters, we mentioned the prefilter 787 787 that generates PostScript from image formats. The <em class="parameter"><code>imagetoraster</code></em> … … 790 790 mentioned prefilters. We summarize in a flowchart the image file 791 791 filtering in <a class="link" href="CUPS-printing.html#small8" title="Figure 22.8. Image Format to CUPS-Raster Format Conversion.">the Image Format to CUPS-Raster Format Conversion illustration</a>. 792 </p><div class="figure"><a name="small8"></a><p class="title"><b>Figure 22.8. Image Format to CUPS-Raster Format Conversion.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/8small.png" alt="Image Format to CUPS-Raster Format Conversion."></div></div></div><br class="figure-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id263 0695"></a>rasterto [printers specific]</h3></div></div></div><p>793 <a class="indexterm" name="id263 0704"></a>794 <a class="indexterm" name="id263 0710"></a>795 <a class="indexterm" name="id263 0717"></a>796 <a class="indexterm" name="id263 0724"></a>797 <a class="indexterm" name="id263 0731"></a>798 <a class="indexterm" name="id263 0738"></a>799 <a class="indexterm" name="id263 0745"></a>800 <a class="indexterm" name="id263 0752"></a>801 <a class="indexterm" name="id263 0759"></a>802 <a class="indexterm" name="id263 0766"></a>803 <a class="indexterm" name="id263 0772"></a>792 </p><div class="figure"><a name="small8"></a><p class="title"><b>Figure 22.8. Image Format to CUPS-Raster Format Conversion.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/8small.png" alt="Image Format to CUPS-Raster Format Conversion."></div></div></div><br class="figure-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2637665"></a>rasterto [printers specific]</h3></div></div></div><p> 793 <a class="indexterm" name="id2637673"></a> 794 <a class="indexterm" name="id2637680"></a> 795 <a class="indexterm" name="id2637687"></a> 796 <a class="indexterm" name="id2637694"></a> 797 <a class="indexterm" name="id2637701"></a> 798 <a class="indexterm" name="id2637708"></a> 799 <a class="indexterm" name="id2637714"></a> 800 <a class="indexterm" name="id2637721"></a> 801 <a class="indexterm" name="id2637728"></a> 802 <a class="indexterm" name="id2637735"></a> 803 <a class="indexterm" name="id2637742"></a> 804 804 CUPS ships with quite a variety of raster drivers for processing CUPS raster. On my system, I find in 805 805 /usr/lib/cups/filter/ the following: <em class="parameter"><code>rastertoalps</code></em>, <em class="parameter"><code>rastertobj</code></em>, … … 812 812 wanting to cooperate as closely as possible with CUPS. See <a class="link" href="CUPS-printing.html#small9" title="Figure 22.9. Raster to Printer-Specific Formats.">the Raster to 813 813 Printer-Specific Formats illustration</a>. 814 </p><div class="figure"><a name="small9"></a><p class="title"><b>Figure 22.9. Raster to Printer-Specific Formats.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/9small.png" alt="Raster to Printer-Specific Formats."></div></div></div><br class="figure-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id263 0915"></a>CUPS Backends</h3></div></div></div><p>815 <a class="indexterm" name="id263 0923"></a>816 <a class="indexterm" name="id263 0930"></a>814 </p><div class="figure"><a name="small9"></a><p class="title"><b>Figure 22.9. Raster to Printer-Specific Formats.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/9small.png" alt="Raster to Printer-Specific Formats."></div></div></div><br class="figure-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2637884"></a>CUPS Backends</h3></div></div></div><p> 815 <a class="indexterm" name="id2637892"></a> 816 <a class="indexterm" name="id2637899"></a> 817 817 The last part of any CUPS filtering chain is a backend. Backends 818 818 are special programs that send the print-ready file to the final … … 888 888 printer name.) 889 889 </p><p> 890 <a class="indexterm" name="id263 1210"></a>891 <a class="indexterm" name="id263 1217"></a>890 <a class="indexterm" name="id2638179"></a> 891 <a class="indexterm" name="id2638185"></a> 892 892 Not all of the mentioned backends may be present on your system or 893 893 usable (depending on your hardware configuration). One test for all … … 897 897 </p><pre class="screen"> 898 898 <code class="prompt">$ </code><strong class="userinput"><code>lpinfo -v</code></strong> 899 </pre></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id263 1254"></a>The Role of <em class="parameter"><code>cupsomatic/foomatic</code></em></h3></div></div></div><p>900 <a class="indexterm" name="id263 1266"></a>901 <a class="indexterm" name="id263 1273"></a>902 <a class="indexterm" name="id263 1280"></a>903 <a class="indexterm" name="id263 1287"></a>904 <a class="indexterm" name="id263 1294"></a>899 </pre></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2638223"></a>The Role of <em class="parameter"><code>cupsomatic/foomatic</code></em></h3></div></div></div><p> 900 <a class="indexterm" name="id2638235"></a> 901 <a class="indexterm" name="id2638242"></a> 902 <a class="indexterm" name="id2638249"></a> 903 <a class="indexterm" name="id2638256"></a> 904 <a class="indexterm" name="id2638263"></a> 905 905 <em class="parameter"><code>cupsomatic</code></em> filters may be the most widely used on CUPS 906 906 installations. You must be clear that these were not … … 926 926 the print job. 927 927 </p><p> 928 <a class="indexterm" name="id263 1360"></a>929 <a class="indexterm" name="id263 1367"></a>930 <a class="indexterm" name="id263 1374"></a>931 <a class="indexterm" name="id263 1381"></a>932 <a class="indexterm" name="id263 1388"></a>933 <a class="indexterm" name="id263 1395"></a>934 <a class="indexterm" name="id263 1402"></a>935 <a class="indexterm" name="id263 1408"></a>936 <a class="indexterm" name="id263 1415"></a>937 <a class="indexterm" name="id263 1422"></a>938 <a class="indexterm" name="id263 1429"></a>928 <a class="indexterm" name="id2638329"></a> 929 <a class="indexterm" name="id2638336"></a> 930 <a class="indexterm" name="id2638343"></a> 931 <a class="indexterm" name="id2638350"></a> 932 <a class="indexterm" name="id2638357"></a> 933 <a class="indexterm" name="id2638364"></a> 934 <a class="indexterm" name="id2638370"></a> 935 <a class="indexterm" name="id2638377"></a> 936 <a class="indexterm" name="id2638384"></a> 937 <a class="indexterm" name="id2638391"></a> 938 <a class="indexterm" name="id2638398"></a> 939 939 However, <em class="parameter"><code>cupsomatic</code></em> is now deprecated. Its PPDs (especially the first 940 940 generation of them, still in heavy use out there) are not meeting the … … 958 958 legacy spoolers too (like LPRng, BSD-LPD, PDQ, PPR, and so on), providing 959 959 for them access to use PPDs for their printing. 960 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id263 1489"></a>The Complete Picture</h3></div></div></div><p>960 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2638458"></a>The Complete Picture</h3></div></div></div><p> 961 961 If you want to see an overview of all the filters and how they 962 962 relate to each other, the complete picture of the puzzle is at the end 963 963 of this chapter. 964 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id263 1502"></a><code class="filename">mime.convs</code></h3></div></div></div><p>964 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2638471"></a><code class="filename">mime.convs</code></h3></div></div></div><p> 965 965 CUPS autoconstructs all possible filtering chain paths for any given 966 966 MIME type and every printer installed. But how does it decide in … … 972 972 a total “<span class="quote">filter cost.</span>” CUPS decides for the most “<span class="quote">inexpensive</span>” route. 973 973 </p><div class="tip" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Tip</h3><p> 974 <a class="indexterm" name="id263 1534"></a>975 <a class="indexterm" name="id263 1540"></a>974 <a class="indexterm" name="id2638502"></a> 975 <a class="indexterm" name="id2638509"></a> 976 976 Setting <em class="parameter"><code>FilterLimit 1000</code></em> in 977 977 <code class="filename">cupsd.conf</code> will not allow more filters to … … 981 981 200 allows roughly one job at a time, while a FilterLimit of 1000 allows 982 982 approximately five jobs maximum at a time. 983 </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id263 1571"></a>“<span class="quote">Raw</span>” Printing</h3></div></div></div><p>984 <a class="indexterm" name="id263 1581"></a>985 <a class="indexterm" name="id263 1587"></a>986 <a class="indexterm" name="id263 1594"></a>983 </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2638540"></a>“<span class="quote">Raw</span>” Printing</h3></div></div></div><p> 984 <a class="indexterm" name="id2638549"></a> 985 <a class="indexterm" name="id2638556"></a> 986 <a class="indexterm" name="id2638563"></a> 987 987 You can tell CUPS to print (nearly) any file “<span class="quote">raw</span>”. “<span class="quote">Raw</span>” means it will not be 988 988 filtered. CUPS will send the file to the printer “<span class="quote">as is</span>” without bothering if the printer is able … … 1002 1002 only send known MIME types (as defined in its own mime.types file) and 1003 1003 refuse others. 1004 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id263 1679"></a>application/octet-stream Printing</h3></div></div></div><p>1005 <a class="indexterm" name="id263 1687"></a>1006 <a class="indexterm" name="id263 1694"></a>1004 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2638648"></a>application/octet-stream Printing</h3></div></div></div><p> 1005 <a class="indexterm" name="id2638656"></a> 1006 <a class="indexterm" name="id2638663"></a> 1007 1007 Any MIME type with no rule in the <code class="filename">/etc/cups/mime.types</code> file is regarded as unknown 1008 1008 or <em class="parameter"><code>application/octet-stream</code></em> and will not be … … 1017 1017 these two files: 1018 1018 </p><div class="itemizedlist"><ul type="disc"><li><p><code class="filename">/etc/cups/mime.convs</code></p></li><li><p><code class="filename">/etc/cups/mime.types</code></p></li></ul></div><p> 1019 <a class="indexterm" name="id263 1760"></a>1019 <a class="indexterm" name="id2638728"></a> 1020 1020 Both contain entries (at the end of the respective files) that must be uncommented to allow raw mode 1021 1021 operation for <em class="parameter"><code>application/octet-stream</code></em>. In <code class="filename">/etc/cups/mime.types</code> 1022 1022 make sure this line is present: 1023 <a class="indexterm" name="id263 1781"></a>1023 <a class="indexterm" name="id2638750"></a> 1024 1024 </p><pre class="programlisting"> 1025 1025 application/octet-stream … … 1032 1032 application/octet-stream application/vnd.cups-raw 0 - 1033 1033 </pre><p> 1034 <a class="indexterm" name="id263 1816"></a>1034 <a class="indexterm" name="id2638785"></a> 1035 1035 This line tells CUPS to use the <span class="emphasis"><em>Null Filter</em></span> 1036 1036 (denoted as “<span class="quote">-</span>”, doing nothing at all) on … … 1043 1043 <span class="emphasis"><em>enforce</em></span> “<span class="quote">raw</span>” printing, it only <span class="emphasis"><em>allows</em></span> it. 1044 1044 </p></div><p><b>Background. </b> 1045 <a class="indexterm" name="id263 1883"></a>1046 <a class="indexterm" name="id263 1890"></a>1047 <a class="indexterm" name="id263 1897"></a>1048 <a class="indexterm" name="id263 1904"></a>1045 <a class="indexterm" name="id2638852"></a> 1046 <a class="indexterm" name="id2638859"></a> 1047 <a class="indexterm" name="id2638865"></a> 1048 <a class="indexterm" name="id2638872"></a> 1049 1049 That CUPS is a more security-aware printing system than traditional ones 1050 1050 does not by default allow one to send deliberate (possibly binary) … … 1058 1058 recognizes MIME types. The file <code class="filename">/etc/cups/mime.convs</code> decides which file 1059 1059 conversion filter(s) may be applied to which MIME types. 1060 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id263 1958"></a>PostScript Printer Descriptions for Non-PostScript Printers</h3></div></div></div><p>1061 <a class="indexterm" name="id263 1966"></a>1062 <a class="indexterm" name="id263 1973"></a>1063 <a class="indexterm" name="id263 1980"></a>1064 <a class="indexterm" name="id263 1987"></a>1065 <a class="indexterm" name="id263 1993"></a>1066 <a class="indexterm" name="id263 2000"></a>1060 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2638927"></a>PostScript Printer Descriptions for Non-PostScript Printers</h3></div></div></div><p> 1061 <a class="indexterm" name="id2638935"></a> 1062 <a class="indexterm" name="id2638942"></a> 1063 <a class="indexterm" name="id2638949"></a> 1064 <a class="indexterm" name="id2638956"></a> 1065 <a class="indexterm" name="id2638962"></a> 1066 <a class="indexterm" name="id2638969"></a> 1067 1067 Originally PPDs were meant to be used for PostScript printers 1068 1068 only. Here, they help to send device-specific commands and settings … … 1077 1077 PPDs for a non-PostScript printer have a few lines that are unique to 1078 1078 CUPS. The most important one looks similar to this: 1079 <a class="indexterm" name="id263 2023"></a>1079 <a class="indexterm" name="id2638991"></a> 1080 1080 </p><pre class="programlisting"> 1081 1081 *cupsFilter: application/vnd.cups-raster 66 rastertoprinter … … 1095 1095 different paper trays, or you may get larger margins than your 1096 1096 specific model supports. See Table 21.1<a class="link" href="CUPS-printing.html#cups-ppds" title="Table 22.1. PPDs Shipped with CUPS">“PPDs Shipped with CUPS”</a> for summary information. 1097 </p><div class="table"><a name="cups-ppds"></a><p class="title"><b>Table 22.1. PPDs Shipped with CUPS</b></p><div class="table-contents"><table summary="PPDs Shipped with CUPS" border="1"><colgroup><col align="left"><col align="justify"></colgroup><thead><tr><th align="left">PPD file</th><th align="justify">Printer type</th></tr></thead><tbody><tr><td align="left">deskjet.ppd</td><td align="justify">older HP inkjet printers and compatible</td></tr><tr><td align="left">deskjet2.ppd</td><td align="justify">newer HP inkjet printers and compatible </td></tr><tr><td align="left">dymo.ppd</td><td align="justify">label printers </td></tr><tr><td align="left">epson9.ppd</td><td align="justify">Epson 24-pin impact printers and compatible </td></tr><tr><td align="left">epson24.ppd</td><td align="justify">Epson 24-pin impact printers and compatible </td></tr><tr><td align="left">okidata9.ppd</td><td align="justify">Okidata 9-pin impact printers and compatible </td></tr><tr><td align="left">okidat24.ppd</td><td align="justify">Okidata 24-pin impact printers and compatible </td></tr><tr><td align="left">stcolor.ppd</td><td align="justify">older Epson Stylus Color printers </td></tr><tr><td align="left">stcolor2.ppd</td><td align="justify">newer Epson Stylus Color printers </td></tr><tr><td align="left">stphoto.ppd</td><td align="justify">older Epson Stylus Photo printers </td></tr><tr><td align="left">stphoto2.ppd</td><td align="justify">newer Epson Stylus Photo printers </td></tr><tr><td align="left">laserjet.ppd</td><td align="justify">all PCL printers </td></tr></tbody></table></div></div><br class="table-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id263 2241"></a><span class="emphasis"><em>cupsomatic/foomatic-rip</em></span> Versus <span class="emphasis"><em>Native CUPS</em></span> Printing</h3></div></div></div><p>1098 <a class="indexterm" name="id263 2255"></a>1099 <a class="indexterm" name="id263 2262"></a>1097 </p><div class="table"><a name="cups-ppds"></a><p class="title"><b>Table 22.1. PPDs Shipped with CUPS</b></p><div class="table-contents"><table summary="PPDs Shipped with CUPS" border="1"><colgroup><col align="left"><col align="justify"></colgroup><thead><tr><th align="left">PPD file</th><th align="justify">Printer type</th></tr></thead><tbody><tr><td align="left">deskjet.ppd</td><td align="justify">older HP inkjet printers and compatible</td></tr><tr><td align="left">deskjet2.ppd</td><td align="justify">newer HP inkjet printers and compatible </td></tr><tr><td align="left">dymo.ppd</td><td align="justify">label printers </td></tr><tr><td align="left">epson9.ppd</td><td align="justify">Epson 24-pin impact printers and compatible </td></tr><tr><td align="left">epson24.ppd</td><td align="justify">Epson 24-pin impact printers and compatible </td></tr><tr><td align="left">okidata9.ppd</td><td align="justify">Okidata 9-pin impact printers and compatible </td></tr><tr><td align="left">okidat24.ppd</td><td align="justify">Okidata 24-pin impact printers and compatible </td></tr><tr><td align="left">stcolor.ppd</td><td align="justify">older Epson Stylus Color printers </td></tr><tr><td align="left">stcolor2.ppd</td><td align="justify">newer Epson Stylus Color printers </td></tr><tr><td align="left">stphoto.ppd</td><td align="justify">older Epson Stylus Photo printers </td></tr><tr><td align="left">stphoto2.ppd</td><td align="justify">newer Epson Stylus Photo printers </td></tr><tr><td align="left">laserjet.ppd</td><td align="justify">all PCL printers </td></tr></tbody></table></div></div><br class="table-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2639210"></a><span class="emphasis"><em>cupsomatic/foomatic-rip</em></span> Versus <span class="emphasis"><em>Native CUPS</em></span> Printing</h3></div></div></div><p> 1098 <a class="indexterm" name="id2639224"></a> 1099 <a class="indexterm" name="id2639231"></a> 1100 1100 Native CUPS rasterization works in two steps: 1101 1101 </p><div class="itemizedlist"><ul type="disc"><li><p> 1102 <a class="indexterm" name="id263 2276"></a>1102 <a class="indexterm" name="id2639245"></a> 1103 1103 First is the <em class="parameter"><code>pstoraster</code></em> step. It uses the special CUPS 1104 <a class="indexterm" name="id263 2290"></a>1104 <a class="indexterm" name="id2639259"></a> 1105 1105 device from ESP Ghostscript 7.05.x as its tool. 1106 1106 </p></li><li><p> … … 1117 1117 way. Note that <em class="parameter"><code>cupsomatic</code></em> is <span class="emphasis"><em>not</em></span> made by the CUPS 1118 1118 developers. It is an independent contribution to printing development, 1119 made by people from Linuxprinting.org.<sup>[<a name="id263 2393" href="#ftn.id2632393" class="footnote">6</a>]</sup>1119 made by people from Linuxprinting.org.<sup>[<a name="id2639362" href="#ftn.id2639362" class="footnote">6</a>]</sup> 1120 1120 <em class="parameter"><code>cupsomatic</code></em> is no longer developed, maintained, or supported. It now been 1121 1121 replaced by <em class="parameter"><code>foomatic-rip</code></em>. <em class="parameter"><code>foomatic-rip</code></em> is a complete rewrite … … 1125 1125 too. 1126 1126 </p><p> 1127 <a class="indexterm" name="id263 2442"></a>1128 <a class="indexterm" name="id263 2449"></a>1127 <a class="indexterm" name="id2639411"></a> 1128 <a class="indexterm" name="id2639418"></a> 1129 1129 Like the old <em class="parameter"><code>cupsomatic</code></em> method, the <em class="parameter"><code>foomatic-rip</code></em> (new) method 1130 1130 from Linuxprinting.org uses the traditional Ghostscript print file processing, doing everything in a single … … 1136 1136 different queues) and find out which works best for you. 1137 1137 </p><p> 1138 <a class="indexterm" name="id263 2484"></a>1139 <a class="indexterm" name="id263 2491"></a>1140 <a class="indexterm" name="id263 2498"></a>1141 <a class="indexterm" name="id263 2505"></a>1142 <a class="indexterm" name="id263 2512"></a>1143 <a class="indexterm" name="id263 2519"></a>1138 <a class="indexterm" name="id2639453"></a> 1139 <a class="indexterm" name="id2639460"></a> 1140 <a class="indexterm" name="id2639467"></a> 1141 <a class="indexterm" name="id2639474"></a> 1142 <a class="indexterm" name="id2639481"></a> 1143 <a class="indexterm" name="id2639488"></a> 1144 1144 <em class="parameter"><code>cupsomatic</code></em> kidnaps the print file after the 1145 1145 <em class="parameter"><code>application/vnd.cups-postscript</code></em> stage and deviates it through the CUPS-external, … … 1150 1150 CUPS</a>, illustrates the difference between native CUPS rendering and the 1151 1151 <em class="parameter"><code>Foomatic/cupsomatic</code></em> method. 1152 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id263 2578"></a>Examples for Filtering Chains</h3></div></div></div><p>1152 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2639547"></a>Examples for Filtering Chains</h3></div></div></div><p> 1153 1153 Here are a few examples of commonly occurring filtering chains to 1154 1154 illustrate the workings of CUPS. 1155 1155 </p><p> 1156 <a class="indexterm" name="id263 2591"></a>1157 <a class="indexterm" name="id263 2598"></a>1158 <a class="indexterm" name="id263 2605"></a>1159 <a class="indexterm" name="id263 2612"></a>1156 <a class="indexterm" name="id2639560"></a> 1157 <a class="indexterm" name="id2639567"></a> 1158 <a class="indexterm" name="id2639574"></a> 1159 <a class="indexterm" name="id2639581"></a> 1160 1160 Assume you want to print a PDF file to an HP JetDirect-connected 1161 1161 PostScript printer, but you want to print pages 3-5, 7, and 11-13 … … 1176 1176 The resulting filter chain, therefore, is as shown in <a class="link" href="CUPS-printing.html#pdftosocket" title="Figure 22.11. PDF to Socket Chain.">the PDF to socket chain 1177 1177 illustration</a>. 1178 </p><a class="indexterm" name="id263 2722"></a><div class="figure"><a name="pdftosocket"></a><p class="title"><b>Figure 22.11. PDF to Socket Chain.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/pdftosocket.png" alt="PDF to Socket Chain."></div></div></div><br class="figure-break"><p>1179 <a class="indexterm" name="id263 2772"></a>1180 <a class="indexterm" name="id263 2779"></a>1181 <a class="indexterm" name="id263 2786"></a>1178 </p><a class="indexterm" name="id2639692"></a><div class="figure"><a name="pdftosocket"></a><p class="title"><b>Figure 22.11. PDF to Socket Chain.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/pdftosocket.png" alt="PDF to Socket Chain."></div></div></div><br class="figure-break"><p> 1179 <a class="indexterm" name="id2639742"></a> 1180 <a class="indexterm" name="id2639749"></a> 1181 <a class="indexterm" name="id2639756"></a> 1182 1182 Assume you want to print the same filter to an USB-connected Epson Stylus Photo Printer installed with the CUPS 1183 1183 <code class="filename">stphoto2.ppd</code>. The first few filtering stages are nearly the same: … … 1189 1189 <em class="parameter"><code>application/pdf</code></em>. 1190 1190 </p></li><li><p> 1191 <a class="indexterm" name="id263 2826"></a>1192 <a class="indexterm" name="id263 2833"></a>1191 <a class="indexterm" name="id2639796"></a> 1192 <a class="indexterm" name="id2639802"></a> 1193 1193 The file must first pass the <em class="parameter"><code>pdftops</code></em> prefilter, which produces PostScript 1194 1194 MIME type <em class="parameter"><code>application/postscript</code></em> (a preview here would still show all 1195 1195 pages of the original PDF). 1196 1196 </p></li><li><p> 1197 <a class="indexterm" name="id263 2859"></a>1198 <a class="indexterm" name="id263 2866"></a>1197 <a class="indexterm" name="id2639828"></a> 1198 <a class="indexterm" name="id2639835"></a> 1199 1199 The file then passes the “<span class="quote">pstops</span>” filter that applies 1200 1200 the command line options: it selects the pages 2-5, 7, and 11-13, … … 1208 1208 <em class="parameter"><code>application/cups-raster</code></em>. 1209 1209 </p></li><li><p> 1210 <a class="indexterm" name="id263 2921"></a>1210 <a class="indexterm" name="id2639890"></a> 1211 1211 Finally, the <em class="parameter"><code>rastertoepson</code></em> filter 1212 1212 does its work (as indicated in the printer's PPD), creating the … … 1218 1218 The resulting filter chain therefore is as shown in <a class="link" href="CUPS-printing.html#pdftoepsonusb" title="Figure 22.12. PDF to USB Chain.">the PDF to USB Chain 1219 1219 illustration</a>. 1220 </p><div class="figure"><a name="pdftoepsonusb"></a><p class="title"><b>Figure 22.12. PDF to USB Chain.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/pdftoepsonusb.png" alt="PDF to USB Chain."></div></div></div><br class="figure-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id263 3006"></a>Sources of CUPS Drivers/PPDs</h3></div></div></div><p>1220 </p><div class="figure"><a name="pdftoepsonusb"></a><p class="title"><b>Figure 22.12. PDF to USB Chain.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/pdftoepsonusb.png" alt="PDF to USB Chain."></div></div></div><br class="figure-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2639975"></a>Sources of CUPS Drivers/PPDs</h3></div></div></div><p> 1221 1221 On the Internet you can now find many thousands of CUPS-PPD files 1222 1222 (with their companion filters), in many national languages 1223 1223 supporting more than 1,000 non-PostScript models. 1224 </p><div class="itemizedlist"><a class="indexterm" name="id263 3021"></a><a class="indexterm" name="id2633030"></a><ul type="disc"><li><p>1224 </p><div class="itemizedlist"><a class="indexterm" name="id2639989"></a><a class="indexterm" name="id2639998"></a><ul type="disc"><li><p> 1225 1225 <a class="ulink" href="http://www.easysw.com/printpro/" target="_top">ESP PrintPro</a> 1226 1226 (commercial, non-free) is packaged with more than 3,000 PPDs, ready for … … 1250 1250 (LPGL, free) from Linuxprinting.org provide PPDs for practically every Ghostscript 1251 1251 filter known to the world (including Omni, Gutenprint, and HPIJS). 1252 </p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id26 33129"></a>Printing with Interface Scripts</h3></div></div></div><p>1253 <a class="indexterm" name="id26 33137"></a>1254 <a class="indexterm" name="id26 33144"></a>1252 </p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2640098"></a>Printing with Interface Scripts</h3></div></div></div><p> 1253 <a class="indexterm" name="id2640106"></a> 1254 <a class="indexterm" name="id2640113"></a> 1255 1255 CUPS also supports the use of “<span class="quote">interface scripts</span>” as known from 1256 1256 System V AT&T printing systems. These are often used for PCL … … 1274 1274 <a class="ulink" href="http://playground.sun.com/printing/documentation/interface.html" target="_top"> 1275 1275 http://playground.sun.com/printing/documentation/interface.html</a>). 1276 </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id26 33224"></a>Network Printing (Purely Windows)</h2></div></div></div><p>1276 </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2640193"></a>Network Printing (Purely Windows)</h2></div></div></div><p> 1277 1277 Network printing covers a lot of ground. To understand what exactly 1278 1278 goes on with Samba when it is printing on behalf of its Windows 1279 1279 clients, let's first look at a “<span class="quote">purely Windows</span>” setup: Windows clients 1280 1280 with a Windows NT print server. 1281 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id26 33241"></a>From Windows Clients to an NT Print Server</h3></div></div></div><p>1281 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2640209"></a>From Windows Clients to an NT Print Server</h3></div></div></div><p> 1282 1282 Windows clients printing to an NT-based print server have two 1283 1283 options. They may: 1284 <a class="indexterm" name="id26 33250"></a>1285 <a class="indexterm" name="id26 33257"></a>1284 <a class="indexterm" name="id2640219"></a> 1285 <a class="indexterm" name="id2640226"></a> 1286 1286 </p><div class="itemizedlist"><ul type="disc"><li><p>Execute the driver locally and render the GDI output 1287 1287 (EMF) into the printer-specific format on their own. … … 1292 1292 Print Driver Execution on the Client</a>, and 1293 1293 <a class="link" href="CUPS-printing.html#small12" title="Figure 22.14. Print Driver Execution on the Server.">Print Driver Execution on the Server</a>. 1294 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id26 33303"></a>Driver Execution on the Client</h3></div></div></div><p>1294 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2640271"></a>Driver Execution on the Client</h3></div></div></div><p> 1295 1295 In the first case, the print server must spool the file as raw, meaning it shouldn't touch the job file and try 1296 1296 to convert it in any way. This is what a traditional UNIX-based print server can do too, and at a better … … 1300 1300 installed on the clients. This is illustrated in <a class="link" href="CUPS-printing.html#small11" title="Figure 22.13. Print Driver Execution on the Client.">the Print Driver Execution on the 1301 1301 Client diagram</a>. 1302 </p><div class="figure"><a name="small11"></a><p class="title"><b>Figure 22.13. Print Driver Execution on the Client.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/11small.png" alt="Print Driver Execution on the Client."></div></div></div><br class="figure-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id26 33375"></a>Driver Execution on the Server</h3></div></div></div><p>1303 <a class="indexterm" name="id26 33383"></a>1304 <a class="indexterm" name="id26 33390"></a>1305 <a class="indexterm" name="id26 33396"></a>1306 <a class="indexterm" name="id26 33403"></a>1307 <a class="indexterm" name="id26 33409"></a>1302 </p><div class="figure"><a name="small11"></a><p class="title"><b>Figure 22.13. Print Driver Execution on the Client.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/11small.png" alt="Print Driver Execution on the Client."></div></div></div><br class="figure-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2640343"></a>Driver Execution on the Server</h3></div></div></div><p> 1303 <a class="indexterm" name="id2640351"></a> 1304 <a class="indexterm" name="id2640358"></a> 1305 <a class="indexterm" name="id2640364"></a> 1306 <a class="indexterm" name="id2640371"></a> 1307 <a class="indexterm" name="id2640377"></a> 1308 1308 The other path executes the printer driver on the server. The client transfers print files in EMF format to 1309 1309 the server. The server uses the PostScript, PCL, ESC/P, or other driver to convert the EMF file into the … … 1313 1313 </p><div class="figure"><a name="small12"></a><p class="title"><b>Figure 22.14. Print Driver Execution on the Server.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/12small.png" alt="Print Driver Execution on the Server."></div></div></div><br class="figure-break"><p> 1314 1314 However, something similar is possible with CUPS, so read on. 1315 </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id26 33480"></a>Network Printing (Windows Clients and UNIX/Samba Print1315 </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2640448"></a>Network Printing (Windows Clients and UNIX/Samba Print 1316 1316 Servers)</h2></div></div></div><p> 1317 1317 Since UNIX print servers <span class="emphasis"><em>cannot</em></span> execute the Win32 … … 1320 1320 much. On the contrary, you may have a way here to implement printing 1321 1321 features that are not possible otherwise. 1322 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id26 33498"></a>From Windows Clients to a CUPS/Samba Print Server</h3></div></div></div><p>1322 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2640466"></a>From Windows Clients to a CUPS/Samba Print Server</h3></div></div></div><p> 1323 1323 Here is a simple recipe showing how you can take advantage of CUPS's 1324 1324 powerful features for the benefit of your Windows network printing … … 1332 1332 First, to enable CUPS-based printing through Samba, the following options should be set in your <code class="filename">smb.conf</code> 1333 1333 file <em class="parameter"><code>[global]</code></em> section: 1334 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id26 33552"></a><em class="parameter"><code>printing = cups</code></em></td></tr><tr><td><a class="indexterm" name="id2633564"></a><em class="parameter"><code>printcap = cups</code></em></td></tr></table><p>1335 When these parameters are specified, all manually set print directives (like <a class="link" href="smb.conf.5.html#PRINTCOMMAND" >print command</a> or <a class="link" href="smb.conf.5.html#LPPAUSECOMMAND">lppause command</a>) in <code class="filename">smb.conf</code> (as well as in Samba itself) will be1334 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2640520"></a><em class="parameter"><code>printing = cups</code></em></td></tr><tr><td><a class="indexterm" name="id2640532"></a><em class="parameter"><code>printcap = cups</code></em></td></tr></table><p> 1335 When these parameters are specified, all manually set print directives (like <a class="link" href="smb.conf.5.html#PRINTCOMMAND" target="_top">print command</a> or <a class="link" href="smb.conf.5.html#LPPAUSECOMMAND" target="_top">lppause command</a>) in <code class="filename">smb.conf</code> (as well as in Samba itself) will be 1336 1336 ignored. Instead, Samba will directly interface with CUPS through its application program interface (API), as 1337 1337 long as Samba has been compiled with CUPS library (libcups) support. If Samba has not been compiled with CUPS 1338 1338 support, and if no other print commands are set up, then printing will use the <span class="emphasis"><em>System V</em></span> 1339 1339 AT&T command set, with the -oraw option automatically passing through (if you want your own defined print 1340 commands to work with a Samba server that has CUPS support compiled in, simply use <a class="link" href="smb.conf.5.html#CLASSICALPRINTING" >classicalprinting = sysv</a>). This is illustrated in <a class="link" href="CUPS-printing.html#13small" title="Figure 22.15. Printing via CUPS/Samba Server.">the Printing via1340 commands to work with a Samba server that has CUPS support compiled in, simply use <a class="link" href="smb.conf.5.html#CLASSICALPRINTING" target="_top">classicalprinting = sysv</a>). This is illustrated in <a class="link" href="CUPS-printing.html#13small" title="Figure 22.15. Printing via CUPS/Samba Server.">the Printing via 1341 1341 CUPS/Samba Server diagram</a>. 1342 </p><div class="figure"><a name="13small"></a><p class="title"><b>Figure 22.15. Printing via CUPS/Samba Server.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/13small.png" alt="Printing via CUPS/Samba Server."></div></div></div><br class="figure-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id26 33689"></a>Samba Receiving Job-Files and Passing Them to CUPS</h3></div></div></div><p>1343 Samba <span class="emphasis"><em>must</em></span> use its own spool directory (it is set by a line similar to <a class="link" href="smb.conf.5.html#PATH" >path = /var/spool/samba</a>, in the <em class="parameter"><code>[printers]</code></em> or <em class="parameter"><code>[printername]</code></em> section of <code class="filename">smb.conf</code>). Samba receives the job in its own spool space and passes it1342 </p><div class="figure"><a name="13small"></a><p class="title"><b>Figure 22.15. Printing via CUPS/Samba Server.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/13small.png" alt="Printing via CUPS/Samba Server."></div></div></div><br class="figure-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2640656"></a>Samba Receiving Job-Files and Passing Them to CUPS</h3></div></div></div><p> 1343 Samba <span class="emphasis"><em>must</em></span> use its own spool directory (it is set by a line similar to <a class="link" href="smb.conf.5.html#PATH" target="_top">path = /var/spool/samba</a>, in the <em class="parameter"><code>[printers]</code></em> or <em class="parameter"><code>[printername]</code></em> section of <code class="filename">smb.conf</code>). Samba receives the job in its own spool space and passes it 1344 1344 into the spool directory of CUPS (the CUPS spool directory is set by the <em class="parameter"><code>RequestRoot</code></em> 1345 1345 directive in a line that defaults to <em class="parameter"><code>RequestRoot /var/spool/cups</code></em>). CUPS checks the … … 1352 1352 allow “<span class="quote">localhost</span>” to print. If it runs on different machines, you 1353 1353 need to make sure the Samba host gets access to printing on CUPS. 1354 </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id26 33768"></a>Network PostScript RIP</h2></div></div></div><p>1354 </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2640735"></a>Network PostScript RIP</h2></div></div></div><p> 1355 1355 This section discusses the use of CUPS filters on the server configuration where 1356 1356 clients make use of a PostScript driver with CUPS-PPDs. 1357 1357 </p><p> 1358 <a class="indexterm" name="id26 33785"></a>1359 <a class="indexterm" name="id26 33791"></a>1360 <a class="indexterm" name="id26 33798"></a>1358 <a class="indexterm" name="id2640752"></a> 1359 <a class="indexterm" name="id2640759"></a> 1360 <a class="indexterm" name="id2640765"></a> 1361 1361 PPDs can control all print device options. They are usually provided by the manufacturer if you own 1362 1362 a PostScript printer, that is. PPD files are always a component of PostScript printer drivers on MS Windows or … … 1371 1371 different GUI front-ends on Linux/UNIX, which can present PPD options to users. PPD options are normally meant 1372 1372 to be evaluated by the PostScript RIP on the real PostScript printer. 1373 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id26 33858"></a>PPDs for Non-PS Printers on UNIX</h3></div></div></div><p>1374 <a class="indexterm" name="id26 33866"></a>1373 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2640826"></a>PPDs for Non-PS Printers on UNIX</h3></div></div></div><p> 1374 <a class="indexterm" name="id2640834"></a> 1375 1375 CUPS does not limit itself to “<span class="quote">real</span>” PostScript printers in its use of PPDs. The CUPS developers 1376 1376 have extended the scope of the PPD concept to also describe available device and driver options for … … 1384 1384 devices to its clients, because it can act as a PostScript RIP for those printers, processing the received 1385 1385 PostScript code into a proper raster print format. 1386 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id26 33902"></a>PPDs for Non-PS Printers on Windows</h3></div></div></div><p>1387 <a class="indexterm" name="id26 33910"></a>1386 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2640870"></a>PPDs for Non-PS Printers on Windows</h3></div></div></div><p> 1387 <a class="indexterm" name="id2640878"></a> 1388 1388 CUPS-PPDs can also be used on Windows clients, on top of a “<span class="quote">core</span>” PostScript driver (now 1389 1389 recommended is the CUPS PostScript Driver for Windows NT/200x/XP; you can also use the Adobe one, with … … 1399 1399 </p></li></ul></div><p> 1400 1400 Using CUPS PPDs on Windows clients enables them to control all print job settings just as a UNIX client can do. 1401 </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id26 33970"></a>Windows Terminal Servers (WTS) as CUPS Clients</h2></div></div></div><p>1401 </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2640938"></a>Windows Terminal Servers (WTS) as CUPS Clients</h2></div></div></div><p> 1402 1402 This setup may be of special interest to people experiencing major problems in WTS environments. WTS often 1403 1403 need a multitude of non-PostScript drivers installed to run their clients' variety of different printer 1404 1404 models. This often imposes the price of much increased instability. 1405 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id26 33985"></a>Printer Drivers Running in “<span class="quote">Kernel Mode</span>” Cause Many1405 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2640953"></a>Printer Drivers Running in “<span class="quote">Kernel Mode</span>” Cause Many 1406 1406 Problems</h3></div></div></div><p> 1407 1407 Windows NT printer drivers, which run in “<span class="quote">kernel mode</span>”, introduce a high risk for the stability … … 1415 1415 one from Adobe and the one from Microsoft. Both are well-tested and are as stable as you can imagine on 1416 1416 Windows. The CUPS driver is derived from the Microsoft one. 1417 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id26 34023"></a>Workarounds Impose Heavy Limitations</h3></div></div></div><p>1417 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2640991"></a>Workarounds Impose Heavy Limitations</h3></div></div></div><p> 1418 1418 In an attempt to work around problems, site administrators have resorted to restricting the 1419 1419 allowed drivers installed on their WTS to one generic PCL and one PostScript driver. This, however, restricts 1420 1420 the number of printer options available for clients to use. Often they can't get out more than simplex 1421 1421 prints from one standard paper tray, while their devices could do much better if driven by a different driver! 1422 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id26 34041"></a>CUPS: A “<span class="quote">Magical Stone</span>”?</h3></div></div></div><p>1423 <a class="indexterm" name="id26 34052"></a>1424 <a class="indexterm" name="id26 34059"></a>1422 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2641009"></a>CUPS: A “<span class="quote">Magical Stone</span>”?</h3></div></div></div><p> 1423 <a class="indexterm" name="id2641020"></a> 1424 <a class="indexterm" name="id2641027"></a> 1425 1425 Using a PostScript driver, enabled with a CUPS-PPD, seems to be a very elegant way to overcome all these 1426 1426 shortcomings. There are, depending on the version of Windows OS you use, up to three different PostScript … … 1431 1431 “<span class="quote">raw spooling</span>” device. Plus, this setup is not yet widely tested, although the first feedbacks 1432 1432 look very promising. 1433 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id26 34084"></a>PostScript Drivers with No Major Problems, Even in Kernel1433 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2641052"></a>PostScript Drivers with No Major Problems, Even in Kernel 1434 1434 Mode</h3></div></div></div><p> 1435 <a class="indexterm" name="id26 34092"></a>1436 <a class="indexterm" name="id26 34099"></a>1437 <a class="indexterm" name="id26 34106"></a>1438 <a class="indexterm" name="id26 34113"></a>1439 <a class="indexterm" name="id26 34120"></a>1440 <a class="indexterm" name="id26 34127"></a>1435 <a class="indexterm" name="id2641060"></a> 1436 <a class="indexterm" name="id2641067"></a> 1437 <a class="indexterm" name="id2641074"></a> 1438 <a class="indexterm" name="id2641081"></a> 1439 <a class="indexterm" name="id2641088"></a> 1440 <a class="indexterm" name="id2641095"></a> 1441 1441 More recent printer drivers on W200x and XP no longer run in kernel mode (unlike Windows NT). However, both 1442 1442 operating systems can still use the NT drivers, running in kernel mode (you can roughly tell which is which as … … 1450 1450 the GPL, and if you are the owner of an “<span class="quote">MS DDK for Windows NT,</span>” you can check the driver 1451 1451 yourself. 1452 </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id26 34171"></a>Configuring CUPS for Driver Download</h2></div></div></div><p>1452 </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2641139"></a>Configuring CUPS for Driver Download</h2></div></div></div><p> 1453 1453 As we have said before, all previously known methods to prepare client printer drivers on the Samba server for 1454 1454 download and Point'n'Print convenience of Windows workstations are working with CUPS, too. These methods were 1455 1455 described in <a class="link" href="classicalprinting.html" title="Chapter 21. Classical Printing Support">Classical Printing</a>. In reality, this is a pure Samba 1456 1456 business and relates only to the Samba-Windows client relationship. 1457 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id26 34194"></a><span class="emphasis"><em>cupsaddsmb</em></span>: The Unknown Utility</h3></div></div></div><p>1458 <a class="indexterm" name="id26 34204"></a>1457 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2641162"></a><span class="emphasis"><em>cupsaddsmb</em></span>: The Unknown Utility</h3></div></div></div><p> 1458 <a class="indexterm" name="id2641172"></a> 1459 1459 The <em class="parameter"><code>cupsaddsmb</code></em> utility (shipped with all current CUPS versions) is an alternative 1460 1460 method to transfer printer drivers into the Samba <em class="parameter"><code>[print$]</code></em> share. Remember, this … … 1473 1473 CUPS drivers. You will also need to get the respective part of the Adobe driver 1474 1474 if you need to support Windows 95, 98, and Me clients. 1475 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id26 34292"></a>Prepare Your <code class="filename">smb.conf</code> for <code class="literal">cupsaddsmb</code></h3></div></div></div><p>1475 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2641260"></a>Prepare Your <code class="filename">smb.conf</code> for <code class="literal">cupsaddsmb</code></h3></div></div></div><p> 1476 1476 Prior to running <code class="literal">cupsaddsmb</code>, you need the settings in 1477 1477 <code class="filename">smb.conf</code> as shown in <a class="link" href="CUPS-printing.html#cupsadd-ex" title="Example 22.3. smb.conf for cupsaddsmb Usage">the <code class="filename">smb.conf</code> for cupsaddsmb Usage</a>. 1478 </p><div class="example"><a name="cupsadd-ex"></a><p class="title"><b>Example 22.3. smb.conf for cupsaddsmb Usage</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id26 34361"></a><em class="parameter"><code>load printers = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2634373"></a><em class="parameter"><code>printing = cups</code></em></td></tr><tr><td><a class="indexterm" name="id2634384"></a><em class="parameter"><code>printcap name = cups</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[printers]</code></em></td></tr><tr><td><a class="indexterm" name="id2634405"></a><em class="parameter"><code>comment = All Printers</code></em></td></tr><tr><td><a class="indexterm" name="id2634417"></a><em class="parameter"><code>path = /var/spool/samba</code></em></td></tr><tr><td><a class="indexterm" name="id2634428"></a><em class="parameter"><code>browseable = no</code></em></td></tr><tr><td># setting depends on your requirements</td></tr><tr><td><a class="indexterm" name="id2634444"></a><em class="parameter"><code>guest ok = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2634456"></a><em class="parameter"><code>writable = no</code></em></td></tr><tr><td><a class="indexterm" name="id2634467"></a><em class="parameter"><code>printable = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2634479"></a><em class="parameter"><code>printer admin = root</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[print$]</code></em></td></tr><tr><td><a class="indexterm" name="id2634500"></a><em class="parameter"><code>comment = Printer Drivers</code></em></td></tr><tr><td><a class="indexterm" name="id2634511"></a><em class="parameter"><code>path = /etc/samba/drivers</code></em></td></tr><tr><td><a class="indexterm" name="id2634523"></a><em class="parameter"><code>browseable = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2634535"></a><em class="parameter"><code>guest ok = no</code></em></td></tr><tr><td><a class="indexterm" name="id2634546"></a><em class="parameter"><code>read only = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2634558"></a><em class="parameter"><code>write list = root, @smbprintadm</code></em></td></tr></table></div></div><br class="example-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2634572"></a>CUPS “<span class="quote">PostScript Driver for Windows NT/200x/XP</span>”</h3></div></div></div><p>1479 <a class="indexterm" name="id26 34583"></a>1478 </p><div class="example"><a name="cupsadd-ex"></a><p class="title"><b>Example 22.3. smb.conf for cupsaddsmb Usage</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2641329"></a><em class="parameter"><code>load printers = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2641341"></a><em class="parameter"><code>printing = cups</code></em></td></tr><tr><td><a class="indexterm" name="id2641353"></a><em class="parameter"><code>printcap name = cups</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[printers]</code></em></td></tr><tr><td><a class="indexterm" name="id2641373"></a><em class="parameter"><code>comment = All Printers</code></em></td></tr><tr><td><a class="indexterm" name="id2641385"></a><em class="parameter"><code>path = /var/spool/samba</code></em></td></tr><tr><td><a class="indexterm" name="id2641397"></a><em class="parameter"><code>browseable = no</code></em></td></tr><tr><td># setting depends on your requirements</td></tr><tr><td><a class="indexterm" name="id2641412"></a><em class="parameter"><code>guest ok = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2641424"></a><em class="parameter"><code>writable = no</code></em></td></tr><tr><td><a class="indexterm" name="id2641436"></a><em class="parameter"><code>printable = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2641447"></a><em class="parameter"><code>printer admin = root</code></em></td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[print$]</code></em></td></tr><tr><td><a class="indexterm" name="id2641468"></a><em class="parameter"><code>comment = Printer Drivers</code></em></td></tr><tr><td><a class="indexterm" name="id2641480"></a><em class="parameter"><code>path = /etc/samba/drivers</code></em></td></tr><tr><td><a class="indexterm" name="id2641492"></a><em class="parameter"><code>browseable = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2641504"></a><em class="parameter"><code>guest ok = no</code></em></td></tr><tr><td><a class="indexterm" name="id2641515"></a><em class="parameter"><code>read only = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2641527"></a><em class="parameter"><code>write list = root, @smbprintadm</code></em></td></tr></table></div></div><br class="example-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2641541"></a>CUPS “<span class="quote">PostScript Driver for Windows NT/200x/XP</span>”</h3></div></div></div><p> 1479 <a class="indexterm" name="id2641551"></a> 1480 1480 CUPS users may get the exact same package from <a class="ulink" href="http://www.cups.org/software.html" target="_top">http://www.cups.org/software.html</a>. It is a separate package 1481 1481 from the CUPS-based software files, tagged as CUPS 1.1.x Windows NT/200x/XP Printer Driver for Samba (tar.gz, … … 1490 1490 cups-samba.ss 1491 1491 </pre><p> 1492 <a class="indexterm" name="id26 34629"></a>1493 <a class="indexterm" name="id26 34638"></a>1492 <a class="indexterm" name="id2641598"></a> 1493 <a class="indexterm" name="id2641607"></a> 1494 1494 These have been packaged with the ESP meta-packager software EPM. The <code class="filename">*.install</code> and 1495 1495 <code class="filename">*.remove</code> files are simple shell scripts, which untar the <code class="filename">*.ss</code> (the … … 1523 1523 the correct place. 1524 1524 </p></div><p> 1525 <a class="indexterm" name="id26 34790"></a>1525 <a class="indexterm" name="id2641759"></a> 1526 1526 This new CUPS PostScript driver is currently binary only, but free of charge. No complete source code is 1527 1527 provided (yet). The reason is that it has been developed with the help of the Microsoft DDK and compiled with … … 1529 1529 free software. However, CUPS developers released the “<span class="quote">diff</span>” in source code under the GPL, so 1530 1530 anybody with a license for Visual Studio and a DDK will be able to compile for himself or herself. 1531 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id26 34811"></a>Recognizing Different Driver Files</h3></div></div></div><p>1531 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2641780"></a>Recognizing Different Driver Files</h3></div></div></div><p> 1532 1532 The CUPS drivers do not support the older Windows 95/98/Me, but only the Windows NT/2000/XP client. 1533 1533 </p><p>Windows NT, 2000, and XP are supported by:</p><div class="itemizedlist"><ul type="disc"><li><p>cups.hlp</p></li><li><p>cupsdrvr.dll</p></li><li><p>cupsui.dll</p></li></ul></div><p> … … 1536 1536 different platforms. 1537 1537 </p><p>Windows 95, 98, and ME are supported by:</p><div class="itemizedlist"><ul type="disc"><li><p>ADFONTS.MFM</p></li><li><p>ADOBEPS4.DRV</p></li><li><p>ADOBEPS4.HLP</p></li><li><p>DEFPRTR2.PPD</p></li><li><p>ICONLIB.DLL</p></li><li><p>PSMON.DLL</p></li></ul></div><p>Windows NT, 2000, and XP are supported by:</p><div class="itemizedlist"><ul type="disc"><li><p>ADOBEPS5.DLL</p></li><li><p>ADOBEPSU.DLL</p></li><li><p>ADOBEPSU.HLP</p></li></ul></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> 1538 <a class="indexterm" name="id26 34908"></a>1538 <a class="indexterm" name="id2641878"></a> 1539 1539 If both the Adobe driver files and the CUPS driver files for the support of Windows NT/200x/XP are presently 1540 1540 installed on the server, the Adobe files will be ignored and the CUPS files will be used. If you prefer 1541 1541 for whatever reason to use Adobe-only drivers, move away the three CUPS driver files. 1542 1542 The Windows 9x/Me clients use the Adobe drivers in any case. 1543 </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id26 34930"></a>Acquiring the Adobe Driver Files</h3></div></div></div><p>1543 </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2641899"></a>Acquiring the Adobe Driver Files</h3></div></div></div><p> 1544 1544 Acquiring the Adobe driver files seems to be unexpectedly difficult for many users. They are not available on 1545 1545 the Adobe Web site as single files, and the self-extracting and/or self-installing Windows-.exe is not easy to … … 1547 1547 client once. This will install the drivers (and one generic PostScript printer) locally on the client. When 1548 1548 they are installed, share the generic PostScript printer. After this, the client's <em class="parameter"><code>[print$]</code></em> share holds the Adobe files, which you can get with smbclient from the CUPS host. 1549 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id26 34955"></a>ESP Print Pro PostScript Driver for Windows NT/200x/XP</h3></div></div></div><p>1550 <a class="indexterm" name="id26 34964"></a>1549 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2641924"></a>ESP Print Pro PostScript Driver for Windows NT/200x/XP</h3></div></div></div><p> 1550 <a class="indexterm" name="id2641933"></a> 1551 1551 Users of the ESP Print Pro software are able to install the ESP print drivers package as an alternative to the 1552 1552 Adobe PostScript drivers. To do so, retrieve the driver files from the normal download area of the ESP Print … … 1558 1558 the <em class="parameter"><code>[print$]</code></em> share, and so on. The ESP Print Pro package includes the CUPS driver 1559 1559 files as well as a (licensed) set of Adobe drivers for the Windows 95/98/Me client family. 1560 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id26 35017"></a>Caveats to Be Considered</h3></div></div></div><p>1561 <a class="indexterm" name="id26 35025"></a>1562 <a class="indexterm" name="id26 35032"></a>1563 <a class="indexterm" name="id26 35039"></a>1564 <a class="indexterm" name="id26 35046"></a>1560 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2641987"></a>Caveats to Be Considered</h3></div></div></div><p> 1561 <a class="indexterm" name="id2641995"></a> 1562 <a class="indexterm" name="id2642001"></a> 1563 <a class="indexterm" name="id2642008"></a> 1564 <a class="indexterm" name="id2642015"></a> 1565 1565 Once you have run the install script (and possibly manually moved the <code class="filename">cups.hlp</code> file to 1566 1566 <code class="filename">/usr/share/cups/drivers/</code>), the driver is ready to be put into Samba's <em class="parameter"><code>[print$]</code></em> share (which often maps to <code class="filename">/etc/samba/drivers/</code> and contains a … … 1569 1569 1.1.16). 1570 1570 </p><div class="tip" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Tip</h3><p> 1571 <a class="indexterm" name="id26 35105"></a>1572 <a class="indexterm" name="id26 35112"></a>1571 <a class="indexterm" name="id2642074"></a> 1572 <a class="indexterm" name="id2642081"></a> 1573 1573 You may need to put root into the smbpasswd file by running <code class="literal">smbpasswd</code>; this is especially 1574 1574 important if you should run this whole procedure for the first time and are not working in an environment … … 1585 1585 1.1.16) will automatically prefer its own drivers if it finds both. 1586 1586 </p></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> 1587 <a class="indexterm" name="id26 35187"></a>1588 <a class="indexterm" name="id26 35194"></a>1587 <a class="indexterm" name="id2642156"></a> 1588 <a class="indexterm" name="id2642163"></a> 1589 1589 Should your Windows clients have had the old <code class="filename">ADOBE*.*</code> files for the Adobe PostScript 1590 1590 driver installed, the download and installation of the new CUPS PostScript driver for Windows NT/200x/XP will … … 1600 1600 privileges to do this. 1601 1601 </p></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> 1602 <a class="indexterm" name="id26 35269"></a>1603 <a class="indexterm" name="id26 35279"></a>1602 <a class="indexterm" name="id2642239"></a> 1603 <a class="indexterm" name="id2642248"></a> 1604 1604 Once you have successfully downloaded the CUPS PostScript driver to a client, you can easily switch all 1605 1605 printers to this one by proceeding as described in <a class="link" href="classicalprinting.html" title="Chapter 21. Classical Printing Support">Classical Printing … … 1607 1607 Properties</span> dialog, or use <code class="literal">rpcclient</code> with the <code class="literal">setdriver</code> 1608 1608 subcommand. 1609 </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id26 35317"></a>Windows CUPS PostScript Driver Versus Adobe Driver</h3></div></div></div><p>1609 </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2642286"></a>Windows CUPS PostScript Driver Versus Adobe Driver</h3></div></div></div><p> 1610 1610 Are you interested in a comparison between the CUPS and the Adobe PostScript drivers? For our purposes, these 1611 1611 are the most important items that weigh in favor of CUPS: 1612 1612 </p><div class="itemizedlist"><ul type="disc"><li><p>No hassle with the Adobe EULA.</p></li><li><p>No hassle with the question, “<span class="quote">Where do I 1613 1613 get the ADOBE*.* driver files?</span>”</p></li><li><p> 1614 <a class="indexterm" name="id26 35348"></a>1614 <a class="indexterm" name="id2642317"></a> 1615 1615 The Adobe drivers (on request of the printer PPD associated with them) often put a PJL header in front of the 1616 1616 main PostScript part of the print file. Thus, the print file starts with <em class="parameter"><code><1B … … 1618 1618 <em class="parameter"><code>%!PS</code></em>. This leads to the CUPS daemon autotyping the incoming file as a print-ready file, 1619 1619 not initiating a pass through the <em class="parameter"><code>pstops</code></em> filter (to speak more technically, it is not 1620 regarded as the generic MIME-type <a class="indexterm" name="id26 35386"></a>1620 regarded as the generic MIME-type <a class="indexterm" name="id2642355"></a> 1621 1621 <em class="parameter"><code>application/postscript</code></em>, but as the more special MIME type 1622 <a class="indexterm" name="id26 35400"></a>1622 <a class="indexterm" name="id2642369"></a> 1623 1623 <em class="parameter"><code>application/cups.vnd-postscript</code></em>), which therefore also leads to the page accounting in 1624 1624 <em class="parameter"><code>/var/log/cups/page_log</code></em> not receiving the exact number of pages; instead the dummy page 1625 1625 number of “<span class="quote">1</span>” is logged in a standard setup). 1626 1626 </p></li><li><p>The Adobe driver has more options to misconfigure the 1627 <a class="indexterm" name="id26 35431"></a>1627 <a class="indexterm" name="id2642400"></a> 1628 1628 PostScript generated by it (like setting it inadvertently to 1629 1629 <span class="guilabel">Optimize for Speed</span> instead of 1630 1630 <span class="guilabel">Optimize for Portability</span>, which 1631 1631 could lead to CUPS being unable to process it).</p></li><li><p>The CUPS PostScript driver output sent by Windows 1632 <a class="indexterm" name="id26 35458"></a>1632 <a class="indexterm" name="id2642427"></a> 1633 1633 clients to the CUPS server is guaranteed to autotype 1634 1634 as the generic MIME type <em class="parameter"><code>application/postscript</code></em>, … … 1636 1636 correct number of pages in the <code class="filename">page_log</code> for 1637 1637 accounting and quota purposes.</p></li><li><p> 1638 <a class="indexterm" name="id26 35490"></a>1638 <a class="indexterm" name="id2642460"></a> 1639 1639 The CUPS PostScript driver supports the sending of additional standard (IPP) print options by Windows 1640 1640 NT/200x/XP clients. Such additional print options are naming the CUPS standard <span class="emphasis"><em>banner … … 1649 1649 and simply ignore it).</p></li><li><p>The CUPS PostScript driver will be the heart of the 1650 1650 fully fledged CUPS IPP client for Windows NT/200x/XP to be released soon 1651 (probably alongside the first beta release for CUPS 1.2).</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id26 35535"></a>Run cupsaddsmb (Quiet Mode)</h3></div></div></div><p>1652 <a class="indexterm" name="id26 35543"></a>1653 <a class="indexterm" name="id26 35550"></a>1651 (probably alongside the first beta release for CUPS 1.2).</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2642504"></a>Run cupsaddsmb (Quiet Mode)</h3></div></div></div><p> 1652 <a class="indexterm" name="id2642512"></a> 1653 <a class="indexterm" name="id2642519"></a> 1654 1654 The <code class="literal">cupsaddsmb</code> command copies the needed files into your <em class="parameter"><code>[print$]</code></em> 1655 1655 share. Additionally, the PPD associated with this printer is copied from <code class="filename">/etc/cups/ppd/</code> 1656 1656 to <em class="parameter"><code>[print$]</code></em>. There the files wait for convenient Windows client installations via 1657 1657 Point'n'Print. Before we can run the command successfully, we need to be sure that we can authenticate toward 1658 Samba. If you have a small network, you are probably using user-level security (<a class="link" href="smb.conf.5.html#SECURITY" >security = user</a>).1658 Samba. If you have a small network, you are probably using user-level security (<a class="link" href="smb.conf.5.html#SECURITY" target="_top">security = user</a>). 1659 1659 </p><p> 1660 1660 Here is an example of a successfully run <code class="literal">cupsaddsmb</code> command: 1661 <a class="indexterm" name="id26 35608"></a>1662 <a class="indexterm" name="id26 35615"></a>1661 <a class="indexterm" name="id2642577"></a> 1662 <a class="indexterm" name="id2642584"></a> 1663 1663 </p><pre class="screen"> 1664 1664 <code class="prompt">root# </code><strong class="userinput"><code>cupsaddsmb -U root infotec_IS2027</code></strong> 1665 1665 Password for root required to access localhost via Samba: <strong class="userinput"><code>['secret']</code></strong> 1666 1666 </pre><p> 1667 <a class="indexterm" name="id26 35647"></a>1667 <a class="indexterm" name="id2642616"></a> 1668 1668 To share <span class="emphasis"><em>all</em></span> printers and drivers, use the 1669 1669 <code class="option">-a</code> parameter instead of a printer name. Since 1670 1670 <code class="literal">cupsaddsmb</code> “<span class="quote">exports</span>” the printer drivers to Samba, it should be 1671 1671 obvious that it only works for queues with a CUPS driver associated. 1672 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id26 35675"></a>Run cupsaddsmb with Verbose Output</h3></div></div></div><p>1673 <a class="indexterm" name="id26 35683"></a>1672 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2642644"></a>Run cupsaddsmb with Verbose Output</h3></div></div></div><p> 1673 <a class="indexterm" name="id2642653"></a> 1674 1674 Probably you want to see what's going on. Use the 1675 1675 <code class="option">-v</code> parameter to get a more verbose output. The … … 1677 1677 a line indicate that I inserted an artificial line break plus some 1678 1678 indentation here: 1679 <a class="indexterm" name="id26 35701"></a>1680 <a class="indexterm" name="id26 35710"></a>1679 <a class="indexterm" name="id2642670"></a> 1680 <a class="indexterm" name="id2642680"></a> 1681 1681 </p><pre class="screen"> 1682 1682 <code class="prompt">root# </code><strong class="userinput"><code>cupsaddsmb -U root -v infotec_2105</code></strong> … … 1747 1747 This will occur when the directories WIN40 and W32X86 already existed in the <em class="parameter"><code>[print$]</code></em> 1748 1748 driver download share (from a previous driver installation). These are harmless warning messages. 1749 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id26 35867"></a>Understanding cupsaddsmb</h3></div></div></div><p>1750 <a class="indexterm" name="id26 35875"></a>1749 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2642836"></a>Understanding cupsaddsmb</h3></div></div></div><p> 1750 <a class="indexterm" name="id2642844"></a> 1751 1751 What has happened? What did <code class="literal">cupsaddsmb</code> do? There are five stages of the procedure: 1752 1752 </p><div class="orderedlist"><ol type="1"><li><p> 1753 <a class="indexterm" name="id26 35900"></a>1753 <a class="indexterm" name="id2642869"></a> 1754 1754 Call the CUPS server via IPP and request the driver files and the PPD file for the named printer.</p></li><li><p>Store the files temporarily in the local TEMPDIR (as defined in <code class="filename">cupsd.conf</code>).</p></li><li><p>Connect via smbclient to the Samba server's <em class="parameter"><code>[print$]</code></em> share and put the files into the 1755 1755 share's WIN40 (for Windows 9x/Me) and W32X86 (for Windows NT/200x/XP) subdirectories.</p></li><li><p> 1756 <a class="indexterm" name="id26 35937"></a>1756 <a class="indexterm" name="id2642906"></a> 1757 1757 Connect via rpcclient to the Samba server and execute the <code class="literal">adddriver</code> command with the correct parameters. 1758 1758 </p></li><li><p> 1759 <a class="indexterm" name="id26 35958"></a>1759 <a class="indexterm" name="id2642927"></a> 1760 1760 Connect via rpcclient to the Samba server a second time and execute the <code class="literal">setdriver</code> command.</p></li></ol></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> 1761 1761 You can run the <code class="literal">cupsaddsmb</code> utility with parameters to specify one remote host as Samba host … … 1766 1766 <code class="prompt">root# </code><strong class="userinput"><code>cupsaddsmb -H sambaserver -h cupsserver -v printer</code></strong> 1767 1767 </pre><p> 1768 </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id26 36011"></a>How to Recognize If cupsaddsmb Completed Successfully</h3></div></div></div><p>1768 </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2642980"></a>How to Recognize If cupsaddsmb Completed Successfully</h3></div></div></div><p> 1769 1769 You <span class="emphasis"><em>must</em></span> always check if the utility completed 1770 1770 successfully in all fields. You need at minimum these three messages … … 1788 1788 result was WERR_ACCESS_DENIED 1789 1789 </pre><p> 1790 it means that you might have set <a class="link" href="smb.conf.5.html#USECLIENTDRIVER" >use client driver = yes</a> for this printer.1790 it means that you might have set <a class="link" href="smb.conf.5.html#USECLIENTDRIVER" target="_top">use client driver = yes</a> for this printer. 1791 1791 Setting it to “<span class="quote">no</span>” will solve the problem. Refer to the <code class="filename">smb.conf</code> man page for explanation of 1792 1792 the <em class="parameter"><code>use client driver</code></em>. … … 1795 1795 Therefore, we strongly recommend against use of the default quiet mode. It will hide any problems from you that 1796 1796 might occur. 1797 </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id26 36133"></a>cupsaddsmb with a Samba PDC</h3></div></div></div><p>1798 <a class="indexterm" name="id26 36141"></a>1799 <a class="indexterm" name="id26 36148"></a>1797 </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2643102"></a>cupsaddsmb with a Samba PDC</h3></div></div></div><p> 1798 <a class="indexterm" name="id2643110"></a> 1799 <a class="indexterm" name="id2643117"></a> 1800 1800 Can't get the standard <code class="literal">cupsaddsmb</code> command to run on a Samba PDC? Are you asked for the 1801 1801 password credential again and again, and the command just will not take off at all? Try one of these … … 1807 1807 </pre><p> 1808 1808 (Note the two backslashes: the first one is required to “<span class="quote">escape</span>” the second one). 1809 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id26 36214"></a>cupsaddsmb Flowchart</h3></div></div></div><p>1810 <a class="indexterm" name="id26 36222"></a>1811 <a class="indexterm" name="id26 36229"></a>1809 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2643183"></a>cupsaddsmb Flowchart</h3></div></div></div><p> 1810 <a class="indexterm" name="id2643191"></a> 1811 <a class="indexterm" name="id2643198"></a> 1812 1812 <a class="link" href="CUPS-printing.html#small14" title="Figure 22.16. cupsaddsmb Flowchart.">The cupsaddsmb Flowchart</a> shows a chart about the procedures, command flows, and 1813 1813 data flows of the <code class="literal">cupaddsmb</code> command. Note again: cupsaddsmb is 1814 1814 not intended to, and does not work with, raw print queues! 1815 </p><div class="figure"><a name="small14"></a><p class="title"><b>Figure 22.16. cupsaddsmb Flowchart.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/14small.png" alt="cupsaddsmb Flowchart."></div></div></div><br class="figure-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id26 36295"></a>Installing the PostScript Driver on a Client</h3></div></div></div><p>1816 <a class="indexterm" name="id26 36303"></a>1817 <a class="indexterm" name="id26 36310"></a>1815 </p><div class="figure"><a name="small14"></a><p class="title"><b>Figure 22.16. cupsaddsmb Flowchart.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/14small.png" alt="cupsaddsmb Flowchart."></div></div></div><br class="figure-break"></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2643264"></a>Installing the PostScript Driver on a Client</h3></div></div></div><p> 1816 <a class="indexterm" name="id2643273"></a> 1817 <a class="indexterm" name="id2643280"></a> 1818 1818 After <code class="literal">cupsaddsmb</code> is completed, your driver is prepared for the clients to use. Here are the 1819 1819 steps you must perform to download and install it via Point'n'Print. From a Windows client, browse to the 1820 1820 CUPS/Samba server: 1821 1821 </p><div class="itemizedlist"><ul type="disc"><li><p> 1822 <a class="indexterm" name="id26 36333"></a>1822 <a class="indexterm" name="id2643302"></a> 1823 1823 Open the <span class="guilabel">Printers</span> share of Samba in Network Neighborhood.</p></li><li><p>Right-click on the printer in question.</p></li><li><p>From the opening context menu select 1824 1824 <span class="guimenuitem">Install...</span> or … … 1831 1831 <code class="filename">\\SambaServer\PrinterName</code> entry in the drop-down list of available printers. 1832 1832 </p><p> 1833 <a class="indexterm" name="id26 36403"></a>1834 <a class="indexterm" name="id26 36409"></a>1835 <a class="indexterm" name="id26 36416"></a>1833 <a class="indexterm" name="id2643372"></a> 1834 <a class="indexterm" name="id2643378"></a> 1835 <a class="indexterm" name="id2643385"></a> 1836 1836 <code class="literal">cupsaddsmb</code> will only reliably work with CUPS version 1.1.15 or higher and with Samba 1837 1837 version 2.2.4, or later. If it does not work, or if the automatic printer driver download to the clients does … … 1862 1862 instead of 3 (the latest ESP Ghostscript package handles Level 3 PostScript very well; Adobe). 1863 1863 </p></li><li><p> 1864 Say Yes to PostScript Error Handler (Adobe).</p></li></ul></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id26 36530"></a>Installing PostScript Driver Files Manually Using rpcclient</h2></div></div></div><p>1864 Say Yes to PostScript Error Handler (Adobe).</p></li></ul></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2643499"></a>Installing PostScript Driver Files Manually Using rpcclient</h2></div></div></div><p> 1865 1865 Of course, you can run all the commands that are embedded into the 1866 1866 cupsaddsmb convenience utility yourself, one by one, and upload … … 1868 1868 </p><div class="orderedlist"><ol type="1"><li><p>Prepare Samba (a CUPS print queue with the name of the 1869 1869 printer should be there. We are providing the driver now).</p></li><li><p>Copy all files to <em class="parameter"><code>[print$]</code></em>.</p></li><li><p> 1870 <a class="indexterm" name="id26 36569"></a>1870 <a class="indexterm" name="id2643538"></a> 1871 1871 Run <code class="literal">rpcclient adddriver</code> 1872 1872 (for each client architecture you want to support).</p></li><li><p> 1873 <a class="indexterm" name="id26 36590"></a>1873 <a class="indexterm" name="id2643559"></a> 1874 1874 Run <code class="literal">rpcclient setdriver.</code></p></li></ol></div><p> 1875 <a class="indexterm" name="id26 36608"></a>1876 <a class="indexterm" name="id26 36618"></a>1877 <a class="indexterm" name="id26 36627"></a>1878 <a class="indexterm" name="id26 36636"></a>1879 <a class="indexterm" name="id26 36645"></a>1875 <a class="indexterm" name="id2643578"></a> 1876 <a class="indexterm" name="id2643587"></a> 1877 <a class="indexterm" name="id2643596"></a> 1878 <a class="indexterm" name="id2643605"></a> 1879 <a class="indexterm" name="id2643615"></a> 1880 1880 We are going to do this now. First, read the man page on <em class="parameter"><code>rpcclient</code></em> to get a first idea. 1881 1881 Look at all the printing-related subcommands: <code class="literal">enumprinters</code>, <code class="literal">enumdrivers</code>, … … 1884 1884 You can use it to query (and command) a Windows NT (or 200x/XP) PC, too. MS-RPC is used by Windows clients, 1885 1885 among other things, to benefit from the Point'n'Print features. Samba can now mimic this as well. 1886 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id26 36704"></a>A Check of the rpcclient man Page</h3></div></div></div><p>1886 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2643673"></a>A Check of the rpcclient man Page</h3></div></div></div><p> 1887 1887 First let's check the <em class="parameter"><code>rpcclient</code></em> man page. Here are two relevant passages: 1888 1888 </p><p> 1889 <a class="indexterm" name="id26 36722"></a>1890 <a class="indexterm" name="id26 36729"></a>1891 <a class="indexterm" name="id26 36736"></a>1889 <a class="indexterm" name="id2643692"></a> 1890 <a class="indexterm" name="id2643698"></a> 1891 <a class="indexterm" name="id2643705"></a> 1892 1892 <code class="literal">adddriver <arch> <config></code> Execute an <code class="literal">AddPrinterDriver()</code> RPC 1893 1893 to install the printer driver information on the server. The driver files should already exist in the … … 1912 1912 RPC will fail. 1913 1913 </p><p> 1914 <a class="indexterm" name="id26 36814"></a>1915 <a class="indexterm" name="id26 36821"></a>1914 <a class="indexterm" name="id2643783"></a> 1915 <a class="indexterm" name="id2643790"></a> 1916 1916 <code class="literal">setdriver <printername> <drivername></code> Execute a <code class="literal">SetPrinter()</code> 1917 1917 command to update the printer driver associated with an installed printer. The printer driver must already be 1918 1918 correctly installed on the print server. 1919 1919 </p><p> 1920 <a class="indexterm" name="id26 36846"></a>1921 <a class="indexterm" name="id26 36853"></a>1920 <a class="indexterm" name="id2643816"></a> 1921 <a class="indexterm" name="id2643822"></a> 1922 1922 See also the <code class="literal">enumprinters</code> and <code class="literal">enumdrivers</code> commands to 1923 1923 obtain a list of installed printers and drivers. 1924 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id26 36876"></a>Understanding the rpcclient man Page</h3></div></div></div><p>1925 <a class="indexterm" name="id26 36884"></a>1924 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2643845"></a>Understanding the rpcclient man Page</h3></div></div></div><p> 1925 <a class="indexterm" name="id2643853"></a> 1926 1926 The <span class="emphasis"><em>exact</em></span> format isn't made too clear by the man page, since you have to deal with some 1927 1927 parameters containing spaces. Here is a better description for it. We have line-broken the command and … … 1947 1947 access it from a UNIX workstation. We will query it with <code class="literal">rpcclient</code> to see what it tells us 1948 1948 and try to understand the man page more clearly. 1949 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id26 36981"></a>Producing an Example by Querying a Windows Box</h3></div></div></div><p>1950 <a class="indexterm" name="id26 36989"></a>1951 <a class="indexterm" name="id26 36998"></a>1949 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2643950"></a>Producing an Example by Querying a Windows Box</h3></div></div></div><p> 1950 <a class="indexterm" name="id2643958"></a> 1951 <a class="indexterm" name="id2643967"></a> 1952 1952 We could run <code class="literal">rpcclient</code> with a <code class="literal">getdriver</code> or a 1953 1953 <code class="literal">getprinter</code> subcommand (in level 3 verbosity) against it. Just sit down at a UNIX or Linux … … 1957 1957 </pre><p> 1958 1958 From the result it should become clear which is which. Here is an example from my installation: 1959 <a class="indexterm" name="id26 37049"></a>1959 <a class="indexterm" name="id2644018"></a> 1960 1960 </p><pre class="screen"> 1961 1961 <code class="prompt">root# </code><strong class="userinput"><code>rpcclient -U'Danka%xxxx' W200xSERVER \ … … 1988 1988 drivers, we do not need any (nor would we for the Adobe PostScript driver); therefore, the field will get a 1989 1989 “<span class="quote">NULL</span>” entry. 1990 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id26 37113"></a>Requirements for adddriver and setdriver to Succeed</h3></div></div></div><p>1991 <a class="indexterm" name="id26 37121"></a>1992 <a class="indexterm" name="id26 37130"></a>1993 <a class="indexterm" name="id26 37137"></a>1990 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2644082"></a>Requirements for adddriver and setdriver to Succeed</h3></div></div></div><p> 1991 <a class="indexterm" name="id2644090"></a> 1992 <a class="indexterm" name="id2644100"></a> 1993 <a class="indexterm" name="id2644106"></a> 1994 1994 From the man page (and from the quoted output of <code class="literal">cupsaddsmb</code> above) it becomes clear that 1995 1995 you need to have certain conditions in order to make the manual uploading and initializing of the driver files 1996 1996 succeed. The two <code class="literal">rpcclient</code> subcommands (<code class="literal">adddriver</code> and 1997 1997 <code class="literal">setdriver</code>) need to encounter the following preconditions to complete successfully: 1998 </p><div class="itemizedlist"><ul type="disc"><li><p>You are connected as <a class="link" href="smb.conf.5.html#PRINTERADMIN" >printer admin</a> or root (this is1998 </p><div class="itemizedlist"><ul type="disc"><li><p>You are connected as <a class="link" href="smb.conf.5.html#PRINTERADMIN" target="_top">printer admin</a> or root (this is 1999 1999 <span class="emphasis"><em>not</em></span> the “<span class="quote">Printer Operators</span>” group in NT, but the <span class="emphasis"><em>printer 2000 2000 admin</em></span> group as defined in the <em class="parameter"><code>[global]</code></em> section of <code class="filename">smb.conf</code>). … … 2008 2008 subdirectories.</p></li><li><p>The printer you are going to set up for the Windows 2009 2009 clients needs to be installed in CUPS already.</p></li><li><p> 2010 <a class="indexterm" name="id26 37290"></a>2011 <a class="indexterm" name="id26 37300"></a>2010 <a class="indexterm" name="id2644260"></a> 2011 <a class="indexterm" name="id2644269"></a> 2012 2012 The CUPS printer must be known to Samba; otherwise the <code class="literal">setdriver</code> subcommand fails with an 2013 2013 NT_STATUS_UNSUCCESSFUL error. To check if the printer is known by Samba, you may use the … … 2015 2015 proper update of the printer list until every smbd process had received a SIGHUP or was restarted. Remember 2016 2016 this in case you've created the CUPS printer just recently and encounter problems: try restarting Samba. 2017 </p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id26 37337"></a>Manual Driver Installation in 15 Steps</h3></div></div></div><p>2017 </p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2644307"></a>Manual Driver Installation in 15 Steps</h3></div></div></div><p> 2018 2018 We are going to install a printer driver now by manually executing all 2019 2019 required commands. Because this may seem a rather complicated process at 2020 2020 first, we go through the procedure step by step, explaining every 2021 2021 single action item as it comes up. 2022 </p><div class="procedure"><a name="id26 37351"></a><p class="title"><b>Procedure 22.2. Manual Driver Installation</b></p><ol type="1"><li><p class="title"><b>Install the printer on CUPS.</b></p><pre class="screen">2022 </p><div class="procedure"><a name="id2644320"></a><p class="title"><b>Procedure 22.2. Manual Driver Installation</b></p><ol type="1"><li><p class="title"><b>Install the printer on CUPS.</b></p><pre class="screen"> 2023 2023 <code class="prompt">root# </code><strong class="userinput"><code>lpadmin -p mysmbtstprn -v socket://10.160.51.131:9100 -E \ 2024 2024 -P canonIR85.ppd</code></strong> … … 2029 2029 for this step. 2030 2030 </p></li><li><p class="title"><b>(Optional.) Check if the printer is recognized by Samba.</b></p><p> 2031 <a class="indexterm" name="id26 37408"></a>2031 <a class="indexterm" name="id2644377"></a> 2032 2032 </p><pre class="screen"> 2033 2033 <code class="prompt">root# </code><strong class="userinput"><code>rpcclient -Uroot%xxxx -c 'enumprinters' localhost \ … … 2049 2049 list</span>” as defined in <code class="filename">smb.conf</code> for <em class="parameter"><code>[print$]</code></em>. 2050 2050 </p></li><li><p class="title"><b>(Optional.) Check if Samba knows a driver for the printer.</b></p><p> 2051 <a class="indexterm" name="id26 37505"></a>2052 <a class="indexterm" name="id26 37515"></a>2051 <a class="indexterm" name="id2644475"></a> 2052 <a class="indexterm" name="id2644484"></a> 2053 2053 </p><pre class="screen"> 2054 2054 <code class="prompt">root# </code><strong class="userinput"><code>rpcclient -Uroot%xxxx -c 'getprinter mysmbtstprn 2'\ … … 2106 2106 <em class="parameter"><code>[print$]</code></em>. 2107 2107 </p></li><li><p class="title"><b>Tell Samba that these are driver files (<code class="literal">adddriver</code>).</b></p><p> 2108 <a class="indexterm" name="id26 37703"></a>2108 <a class="indexterm" name="id2644672"></a> 2109 2109 </p><pre class="screen"> 2110 2110 <code class="prompt">root# </code><strong class="userinput"><code>rpcclient -Uroot%xxxx -c 'adddriver "Windows NT x86" \ … … 2137 2137 subdirectory. Compare this with the situation after step 5. 2138 2138 </p></li><li><p class="title"><b>(Optional.) Verify if Samba now recognizes the driver.</b></p><p> 2139 <a class="indexterm" name="id26 37811"></a>2139 <a class="indexterm" name="id2644780"></a> 2140 2140 </p><pre class="screen"> 2141 2141 <code class="prompt">root# </code><strong class="userinput"><code>rpcclient -Uroot%xxxx -c 'enumdrivers 3' \ … … 2153 2153 driver in step 6. This command must succeed before you can proceed. 2154 2154 </p></li><li><p class="title"><b>Tell Samba which printer should use these driver files (<code class="literal">setdriver</code>).</b></p><p> 2155 <a class="indexterm" name="id26 37866"></a>2155 <a class="indexterm" name="id2644835"></a> 2156 2156 </p><pre class="screen"> 2157 2157 <code class="prompt">root# </code><strong class="userinput"><code>rpcclient -Uroot%xxxx -c 'setdriver mysmbtstprn mydrivername' \ … … 2164 2164 <code class="literal">enumprinters</code> must find the printer. 2165 2165 </p></li><li><p class="title"><b>(Optional) Verify if Samba has recognized this association.</b></p><p> 2166 <a class="indexterm" name="id26 37925"></a>2167 <a class="indexterm" name="id26 37934"></a>2168 <a class="indexterm" name="id26 37943"></a>2166 <a class="indexterm" name="id2644894"></a> 2167 <a class="indexterm" name="id2644903"></a> 2168 <a class="indexterm" name="id2644913"></a> 2169 2169 </p><pre class="screen"> 2170 2170 <code class="prompt">root# </code><strong class="userinput"><code>rpcclient -Uroot%xxxx -c 'getprinter mysmbtstprn 2' localhost \ … … 2206 2206 2207 2207 </pre><p> 2208 <a class="indexterm" name="id26 38021"></a>2208 <a class="indexterm" name="id2644990"></a> 2209 2209 Compare these results with the ones from steps 2 and 3. Every one of these commands show the driver is installed. Even 2210 2210 the <code class="literal">enumprinters</code> command now lists the driver … … 2212 2212 </p></li><li><p class="title"><b>(Optional.) Tickle the driver into a correct 2213 2213 device mode.</b></p><p> 2214 <a class="indexterm" name="id26 38056"></a>2214 <a class="indexterm" name="id2645025"></a> 2215 2215 You certainly know how to install the driver on the client. In case 2216 2216 you are not particularly familiar with Windows, here is a short … … 2235 2235 <span class="guilabel">landscape</span></em></span>), click on <span class="guibutton">Apply</span>, and change the setting back. 2236 2236 </p></li><li><p class="title"><b>Install the printer on a client (Point'n'Print).</b></p><p> 2237 <a class="indexterm" name="id26 38174"></a>2237 <a class="indexterm" name="id2645144"></a> 2238 2238 </p><pre class="screen"> 2239 2239 <code class="prompt">C:\> </code><strong class="userinput"><code>rundll32 printui.dll,PrintUIEntry /in /n "\\sambaserver\mysmbtstprn"</code></strong> 2240 2240 </pre><p> 2241 2241 If it does not work, it could be a permissions problem with the <em class="parameter"><code>[print$]</code></em> share. 2242 </p></li><li><p class="title"><b>(Optional) Print a test page.</b></p><a class="indexterm" name="id26 38216"></a><pre class="screen">2242 </p></li><li><p class="title"><b>(Optional) Print a test page.</b></p><a class="indexterm" name="id2645185"></a><pre class="screen"> 2243 2243 <code class="prompt">C:\> </code><strong class="userinput"><code>rundll32 printui.dll,PrintUIEntry /p /n "\\sambaserver\mysmbtstprn"</code></strong> 2244 2244 </pre><p> … … 2250 2250 </p></li><li><p class="title"><b>(Obligatory.) Enjoy. Jump. Celebrate your success.</b></p><pre class="screen"> 2251 2251 <code class="prompt">root# </code><strong class="userinput"><code>echo "Cheeeeerioooooo! Success..." >> /var/log/samba/log.smbd</code></strong> 2252 </pre></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id26 38296"></a>Troubleshooting Revisited</h3></div></div></div><p>2253 <a class="indexterm" name="id26 38304"></a>2252 </pre></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2645265"></a>Troubleshooting Revisited</h3></div></div></div><p> 2253 <a class="indexterm" name="id2645273"></a> 2254 2254 The setdriver command will fail if in Samba's mind the queue is not 2255 2255 already there. A successful installation displys the promising message that the: … … 2262 2262 result was NT_STATUS_UNSUCCESSFUL 2263 2263 </code></p><p> 2264 <a class="indexterm" name="id26 38336"></a>2265 <a class="indexterm" name="id26 38343"></a>2264 <a class="indexterm" name="id2645305"></a> 2265 <a class="indexterm" name="id2645312"></a> 2266 2266 It is not good enough that you can see the queue in CUPS, using the <code class="literal">lpstat -p ir85wm</code> 2267 2267 command. A bug in most recent versions of Samba prevents the proper update of the queue list. The recognition … … 2269 2269 if this is the reason why Samba does not execute the <code class="literal">setdriver</code> command successfully, check 2270 2270 if Samba “<span class="quote">sees</span>” the printer: 2271 <a class="indexterm" name="id26 38372"></a>2271 <a class="indexterm" name="id2645341"></a> 2272 2272 </p><pre class="screen"> 2273 2273 <code class="prompt">root# </code><strong class="userinput"><code>rpcclient transmeta -N -U'root%xxxx' -c 'enumprinters 0'|grep ir85wm</code></strong> … … 2275 2275 </pre><p> 2276 2276 An alternate command could be this: 2277 <a class="indexterm" name="id26 38402"></a>2277 <a class="indexterm" name="id2645371"></a> 2278 2278 </p><pre class="screen"> 2279 2279 <code class="prompt">root# </code><strong class="userinput"><code>rpcclient transmeta -N -U'root%secret' -c 'getprinter ir85wm' </code></strong> … … 2285 2285 </pre><p> 2286 2286 By the way, you can use these commands, plus a few more, of course, to install drivers on remote Windows NT print servers too! 2287 </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id26 38439"></a>The Printing <code class="filename">*.tdb</code> Files</h2></div></div></div><p>2288 <a class="indexterm" name="id26 38453"></a>2289 <a class="indexterm" name="id26 38460"></a>2290 <a class="indexterm" name="id26 38469"></a>2291 <a class="indexterm" name="id26 38478"></a>2292 <a class="indexterm" name="id26 38487"></a>2293 <a class="indexterm" name="id26 38496"></a>2294 <a class="indexterm" name="id26 38505"></a>2295 <a class="indexterm" name="id26 38514"></a>2296 <a class="indexterm" name="id26 38523"></a>2297 <a class="indexterm" name="id26 38532"></a>2298 <a class="indexterm" name="id26 38541"></a>2299 <a class="indexterm" name="id26 38550"></a>2300 <a class="indexterm" name="id26 38559"></a>2287 </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2645408"></a>The Printing <code class="filename">*.tdb</code> Files</h2></div></div></div><p> 2288 <a class="indexterm" name="id2645422"></a> 2289 <a class="indexterm" name="id2645429"></a> 2290 <a class="indexterm" name="id2645438"></a> 2291 <a class="indexterm" name="id2645447"></a> 2292 <a class="indexterm" name="id2645456"></a> 2293 <a class="indexterm" name="id2645465"></a> 2294 <a class="indexterm" name="id2645474"></a> 2295 <a class="indexterm" name="id2645483"></a> 2296 <a class="indexterm" name="id2645492"></a> 2297 <a class="indexterm" name="id2645501"></a> 2298 <a class="indexterm" name="id2645510"></a> 2299 <a class="indexterm" name="id2645519"></a> 2300 <a class="indexterm" name="id2645528"></a> 2301 2301 Some mystery is associated with the series of files with a tdb suffix appearing in every Samba installation. 2302 2302 They are <code class="filename">connections.tdb</code>, <code class="filename">printing.tdb</code>, … … 2305 2305 <code class="filename">messages.tdb</code> , <code class="filename">ntprinters.tdb</code>, <code class="filename">sessionid.tdb</code>, 2306 2306 and <code class="filename">secrets.tdb</code>. What is their purpose? 2307 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id26 38642"></a>Trivial Database Files</h3></div></div></div><p>2308 <a class="indexterm" name="id26 38650"></a>2307 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2645611"></a>Trivial Database Files</h3></div></div></div><p> 2308 <a class="indexterm" name="id2645619"></a> 2309 2309 A Windows NT (print) server keeps track of all information needed to serve its duty toward its clients by 2310 2310 storing entries in the Windows registry. Client queries are answered by reading from the registry, … … 2315 2315 <code class="filename">ntprinters.tdb</code>, <code class="filename">printing.tdb</code>,<code class="filename">ntforms.tdb</code>, and 2316 2316 <code class="filename">ntdrivers.tdb</code>. 2317 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id26 38709"></a>Binary Format</h3></div></div></div><p>2317 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2645679"></a>Binary Format</h3></div></div></div><p> 2318 2318 <code class="filename">*.tdb</code> files are not human readable. They are written in a binary format. “<span class="quote">Why not 2319 2319 ASCII?</span>”, you may ask. “<span class="quote">After all, ASCII configuration files are a good and proven tradition on … … 2324 2324 <code class="filename">*.tdb</code> files allows for this provision. Many smbd processes may write to the same 2325 2325 <code class="filename">*.tdb</code> file at the same time. This wouldn't be possible with pure ASCII files. 2326 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id26 38775"></a>Losing <code class="filename">*.tdb</code> Files</h3></div></div></div><p>2326 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2645745"></a>Losing <code class="filename">*.tdb</code> Files</h3></div></div></div><p> 2327 2327 It is very important that all <code class="filename">*.tdb</code> files remain consistent over all write and read 2328 2328 accesses. However, it may happen that these files <span class="emphasis"><em>do</em></span> get corrupted. (A <code class="literal">kill -9 … … 2331 2331 only option. After that, you need to re-create all print-related setups unless you have made a backup of the 2332 2332 <code class="filename">*.tdb</code> files in time. 2333 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id26 38826"></a>Using <code class="literal">tdbbackup</code></h3></div></div></div><p>2334 <a class="indexterm" name="id26 38838"></a>2335 <a class="indexterm" name="id26 38850"></a>2333 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2645796"></a>Using <code class="literal">tdbbackup</code></h3></div></div></div><p> 2334 <a class="indexterm" name="id2645808"></a> 2335 <a class="indexterm" name="id2645819"></a> 2336 2336 Samba ships with a little utility that helps the root user of your system to backup your 2337 2337 <code class="filename">*.tdb</code> files. If you run it with no argument, it prints a usage message: … … 2360 2360 -rw------- 1 root root 40960 May 2 03:44 printing.tdb.bak 2361 2361 2362 </pre></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id26 38946"></a>CUPS Print Drivers from Linuxprinting.org</h2></div></div></div><p>2363 <a class="indexterm" name="id26 38954"></a>2362 </pre></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2645915"></a>CUPS Print Drivers from Linuxprinting.org</h2></div></div></div><p> 2363 <a class="indexterm" name="id2645924"></a> 2364 2364 CUPS ships with good support for HP LaserJet-type printers. You can install the generic driver as follows: 2365 <a class="indexterm" name="id26 38963"></a>2365 <a class="indexterm" name="id2645933"></a> 2366 2366 </p><pre class="screen"> 2367 2367 <code class="prompt">root# </code><strong class="userinput"><code>lpadmin -p laserjet4plus -v parallel:/dev/lp0 -E -m laserjet.ppd</code></strong> … … 2379 2379 <code class="literal">foomatic-rip</code> utility. 2380 2380 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> 2381 <a class="indexterm" name="id26 39052"></a>2382 <a class="indexterm" name="id26 39059"></a>2383 <a class="indexterm" name="id26 39066"></a>2381 <a class="indexterm" name="id2646022"></a> 2382 <a class="indexterm" name="id2646029"></a> 2383 <a class="indexterm" name="id2646036"></a> 2384 2384 The former <code class="literal">cupsomatic</code> concept is now being replaced by the new successor, a much more 2385 2385 powerful <code class="literal">foomatic-rip</code>. <code class="literal">cupsomatic</code> is no longer maintained. Here is the … … 2390 2390 are also intended to be used by Samba and the cupsaddsmb utility, to provide the driver files for the Windows 2391 2391 clients! 2392 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id26 39121"></a>foomatic-rip and Foomatic Explained</h3></div></div></div><p>2393 <a class="indexterm" name="id26 39129"></a>2394 <a class="indexterm" name="id26 39136"></a>2392 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2646091"></a>foomatic-rip and Foomatic Explained</h3></div></div></div><p> 2393 <a class="indexterm" name="id2646099"></a> 2394 <a class="indexterm" name="id2646106"></a> 2395 2395 Nowadays, most Linux distributions rely on the utilities from the <a class="ulink" href="http://www.linuxprinting.org/" target="_top">Linuxprinting.org</a> to create their printing-related software 2396 2396 (which, by the way, works on all UNIXes and on Mac OS X and Darwin, too). The utilities from this sire have a … … 2403 2403 available for the various driver/printer combinations in its <a class="ulink" href="http://www.linuxprinting.org/foomatic.html" target="_top">Foomatic</a> database. Currently there are <a class="ulink" href="http://www.linuxprinting.org/driver_list.cgi" target="_top">245 drivers</a> in the database. Many drivers support 2404 2404 various models, and many models may be driven by different drivers its your choice! 2405 </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id26 39190"></a>690 “<span class="quote">Perfect</span>” Printers</h4></div></div></div><p>2406 <a class="indexterm" name="id26 39202"></a>2405 </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2646160"></a>690 “<span class="quote">Perfect</span>” Printers</h4></div></div></div><p> 2406 <a class="indexterm" name="id2646172"></a> 2407 2407 At present, there are 690 devices dubbed as working perfectly: 181 are <span class="emphasis"><em>mostly</em></span> perfect, 96 2408 2408 are <span class="emphasis"><em>partially</em></span> perfect, and 46 are paperweights. Keeping in mind that most of these are … … 2412 2412 achievement! Three years ago the number was not more than 500, and Linux or UNIX printing at the time wasn't 2413 2413 anywhere near the quality it is today. 2414 </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id26 39231"></a>How the Printing HOWTO Started It All</h4></div></div></div><p>2414 </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2646201"></a>How the Printing HOWTO Started It All</h4></div></div></div><p> 2415 2415 A few years ago <a class="ulink" href="http://www2.picante.com/" target="_top">Grant Taylor</a> started it all. The 2416 2416 roots of today's Linuxprinting.org are in the first <a class="ulink" href="http://www.linuxprinting.org/foomatic2.9/howto/" target="_top">Linux Printing HOWTO</a> that he authored. As a … … 2421 2421 This database became the core component of today's Foomatic collection of tools and data. In the meantime, it 2422 2422 has moved to an XML representation of the data. 2423 </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id26 39269"></a>Foomatic's Strange Name</h4></div></div></div><p>2424 <a class="indexterm" name="id26 39277"></a>2423 </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2646239"></a>Foomatic's Strange Name</h4></div></div></div><p> 2424 <a class="indexterm" name="id2646247"></a> 2425 2425 “<span class="quote">Why the funny name?</span>” you ask. When it really took off, around spring 2000, CUPS was far less 2426 2426 popular than today, and most systems used LPD, LPRng, or even PDQ to print. CUPS shipped with a few generic … … 2440 2440 printing was the only one available).</p></li><li><p>It gave all the advanced CUPS options (Web interface, 2441 2441 GUI driver configurations) to users wanting (or needing) to use 2442 Ghostscript filters.</p></li></ul></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id26 39350"></a>cupsomatic, pdqomatic, lpdomatic, directomatic</h4></div></div></div><p>2443 <a class="indexterm" name="id26 39358"></a>2444 <a class="indexterm" name="id26 39365"></a>2445 <a class="indexterm" name="id26 39372"></a>2442 Ghostscript filters.</p></li></ul></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2646320"></a>cupsomatic, pdqomatic, lpdomatic, directomatic</h4></div></div></div><p> 2443 <a class="indexterm" name="id2646328"></a> 2444 <a class="indexterm" name="id2646335"></a> 2445 <a class="indexterm" name="id2646342"></a> 2446 2446 CUPS worked through a quickly hacked-up filter script named <a class="ulink" href="http://www.linuxprinting.org/download.cgi?filename=cupsomatic&show=0" target="_top">cupsomatic</a>. cupsomatic 2447 2447 ran the printfile through Ghostscript, constructing automatically the rather complicated command line needed. … … 2464 2464 structures attached to Linuxprinting.org PPDs for CUPS. It had a different “<span class="quote">*omatic</span>” script for 2465 2465 every spooler, as well as different printer configuration files. 2466 </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id26 39506"></a>The <span class="emphasis"><em>Grand Unification</em></span> Achieved</h4></div></div></div><p>2467 <a class="indexterm" name="id26 39517"></a>2466 </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2646476"></a>The <span class="emphasis"><em>Grand Unification</em></span> Achieved</h4></div></div></div><p> 2467 <a class="indexterm" name="id2646487"></a> 2468 2468 This has all changed in Foomatic versions 2.9 (beta) and released as “<span class="quote">stable</span>” 3.0. It has now 2469 2469 achieved the convergence of all *omatic scripts and is called the <a class="ulink" href="http://www.linuxprinting.org/foomatic2.9/download.cgi?filename=foomatic-rip&show=0" target="_top">foomatic-rip</a>. … … 2474 2474 there is improved media type and source support paper sizes and trays are easier to configure. 2475 2475 </p><p> 2476 <a class="indexterm" name="id26 39553"></a>2477 <a class="indexterm" name="id26 39559"></a>2478 <a class="indexterm" name="id26 39566"></a>2476 <a class="indexterm" name="id2646523"></a> 2477 <a class="indexterm" name="id2646529"></a> 2478 <a class="indexterm" name="id2646536"></a> 2479 2479 Also, the new generation of Linuxprinting.org PPDs no longer contains Perl data structures. If you are a 2480 2480 distro maintainer and have used the previous version of Foomatic, you may want to give the new one a spin, but … … 2483 2483 the steps</a> outlined in the Foomatic tutorial or in this chapter. This new development is truly amazing. 2484 2484 </p><p> 2485 <a class="indexterm" name="id26 39599"></a>2486 <a class="indexterm" name="id26 39606"></a>2487 <a class="indexterm" name="id26 39613"></a>2485 <a class="indexterm" name="id2646569"></a> 2486 <a class="indexterm" name="id2646576"></a> 2487 <a class="indexterm" name="id2646583"></a> 2488 2488 foomatic-rip is a very clever wrapper around the need to run Ghostscript with a different syntax, options, 2489 2489 device selections, and/or filters for each different printer or spooler. At the same time, it can read the PPD … … 2493 2493 printing on media drawn from different paper trays within the same job (in both cases, even where there is no 2494 2494 support for this from Windows-based vendor printer drivers). 2495 </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id26 39634"></a>Driver Development Outside</h4></div></div></div><p>2496 <a class="indexterm" name="id26 39642"></a>2495 </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2646604"></a>Driver Development Outside</h4></div></div></div><p> 2496 <a class="indexterm" name="id2646612"></a> 2497 2497 Most driver development itself does not happen within Linuxprinting.org. Drivers are written by independent 2498 2498 maintainers. Linuxprinting.org just pools all the information and stores it in its database. In addition, it … … 2502 2502 Speaking of the different driver development groups, most of the work is currently done in three projects: 2503 2503 </p><div class="itemizedlist"><ul type="disc"><li><p> 2504 <a class="indexterm" name="id26 39666"></a>2504 <a class="indexterm" name="id2646636"></a> 2505 2505 <a class="ulink" href="http://www-124.ibm.com/developerworks/oss/linux/projects/omni/" target="_top">Omni</a> 2506 2506 a free software project by IBM that tries to convert its printer … … 2508 2508 universal driver architecture for Linux/UNIX (still beta). This 2509 2509 currently supports 437 models.</p></li><li><p> 2510 <a class="indexterm" name="id26 39691"></a>2510 <a class="indexterm" name="id2646661"></a> 2511 2511 <a class="ulink" href="http://hpinkjet.sf.net/" target="_top">HPIJS</a> 2512 2512 a free software project by HP to provide the support for its own … … 2514 2514 provides true photo quality). This currently supports 369 2515 2515 models.</p></li><li><p> 2516 <a class="indexterm" name="id26 39714"></a>2516 <a class="indexterm" name="id2646684"></a> 2517 2517 <a class="ulink" href="http://gimp-print.sourceforge.net/" target="_top">Gutenprint</a> a free software 2518 2518 effort, started by Michael Sweet (also lead developer for CUPS), now … … 2520 2520 photo print quality (many Epson users swear that its quality is 2521 2521 better than the vendor drivers provided by Epson for the Microsoft 2522 platforms). This currently supports 522 models.</p></li></ul></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id26 39738"></a>Forums, Downloads, Tutorials, Howtos (Also for Mac OS X and Commercial UNIX)</h4></div></div></div><p>2522 platforms). This currently supports 522 models.</p></li></ul></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2646708"></a>Forums, Downloads, Tutorials, Howtos (Also for Mac OS X and Commercial UNIX)</h4></div></div></div><p> 2523 2523 Linuxprinting.org today is the one-stop shop to download printer drivers. Look for printer information and 2524 2524 <a class="ulink" href="http://www.linuxprinting.org//kpfeifle/LinuxKongress2002/Tutorial/" target="_top">tutorials</a> or solve … … 2529 2529 forum</a> has turned out to be one of the most frequented forums after only a few weeks. 2530 2530 </p><p> 2531 <a class="indexterm" name="id26 39783"></a>2532 <a class="indexterm" name="id26 39790"></a>2533 <a class="indexterm" name="id26 39797"></a>2531 <a class="indexterm" name="id2646753"></a> 2532 <a class="indexterm" name="id2646760"></a> 2533 <a class="indexterm" name="id2646767"></a> 2534 2534 Linuxprinting.org and the Foomatic driver wrappers around Ghostscript are now a standard tool-chain for 2535 2535 printing on all the important distros. Most of them also have CUPS underneath. While in recent years most … … 2540 2540 Till Kamppeter from Mandrakesoft is doing an excellent job in his spare time to maintain Linuxprinting.org and 2541 2541 Foomatic. So if you use it often, please send him a note showing your appreciation. 2542 </p></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id26 39821"></a>Foomatic Database-Generated PPDs</h4></div></div></div><p>2543 <a class="indexterm" name="id26 39830"></a>2544 <a class="indexterm" name="id26 39836"></a>2545 <a class="indexterm" name="id26 39843"></a>2546 <a class="indexterm" name="id26 39850"></a>2547 <a class="indexterm" name="id26 39857"></a>2548 <a class="indexterm" name="id26 39864"></a>2549 <a class="indexterm" name="id26 39871"></a>2550 <a class="indexterm" name="id26 39878"></a>2551 <a class="indexterm" name="id26 39885"></a>2542 </p></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2646791"></a>Foomatic Database-Generated PPDs</h4></div></div></div><p> 2543 <a class="indexterm" name="id2646800"></a> 2544 <a class="indexterm" name="id2646806"></a> 2545 <a class="indexterm" name="id2646813"></a> 2546 <a class="indexterm" name="id2646820"></a> 2547 <a class="indexterm" name="id2646827"></a> 2548 <a class="indexterm" name="id2646834"></a> 2549 <a class="indexterm" name="id2646840"></a> 2550 <a class="indexterm" name="id2646847"></a> 2551 <a class="indexterm" name="id2646854"></a> 2552 2552 The Foomatic database is an amazing piece of ingenuity in itself. Not only does it keep the printer and driver 2553 2553 information, but it is organized in a way that it can generate PPD files on the fly from its internal … … 2564 2564 developers. The rest is easy. GUI tools (like KDE's marvelous <a class="ulink" href="http://printing.kde.org/overview/kprinter.phtml" target="_top">kprinter</a> or the GNOME <a class="ulink" href="http://gtklp.sourceforge.net/" target="_top">gtklp</a> xpp and the CUPS Web interface) read the PPD as well and use 2565 2565 this information to present the available settings to the user as an intuitive menu selection. 2566 </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id26 39948"></a>foomatic-rip and Foomatic PPD Download and Installation</h3></div></div></div><p>2566 </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2646918"></a>foomatic-rip and Foomatic PPD Download and Installation</h3></div></div></div><p> 2567 2567 Here are the steps to install a foomatic-rip-driven LaserJet 4 Plus-compatible 2568 2568 printer in CUPS (note that recent distributions of SuSE, UnitedLinux and … … 2657 2657 the driver/model) contain support for a certain device representing 2658 2658 the selected driver for your model (as shown by <code class="literal">gs -h</code>).</p></li><li><p>foomatic-rip needs a new version of PPDs (PPD versions 2659 produced for cupsomatic do not work with foomatic-rip).</p></li></ul></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id264 0421"></a>Page Accounting with CUPS</h2></div></div></div><p>2660 <a class="indexterm" name="id264 0429"></a>2659 produced for cupsomatic do not work with foomatic-rip).</p></li></ul></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2647391"></a>Page Accounting with CUPS</h2></div></div></div><p> 2660 <a class="indexterm" name="id2647399"></a> 2661 2661 Often there are questions regarding print quotas where Samba users (that is, Windows clients) should not be 2662 2662 able to print beyond a certain number of pages or data volume per day, week, or month. This feature is … … 2666 2666 Of course one could hack things with one's own scripts. But then there is CUPS. CUPS supports quotas that can 2667 2667 be based on the size of jobs or on the number of pages or both, and can span any time period you want. 2668 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id264 0456"></a>Setting Up Quotas</h3></div></div></div><p>2669 <a class="indexterm" name="id264 0464"></a>2668 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2647427"></a>Setting Up Quotas</h3></div></div></div><p> 2669 <a class="indexterm" name="id2647434"></a> 2670 2670 This is an example command of how root would set a print quota in CUPS, assuming an existing printer named 2671 2671 “<span class="quote">quotaprinter</span>”: 2672 <a class="indexterm" name="id264 0479"></a>2672 <a class="indexterm" name="id2647449"></a> 2673 2673 </p><pre class="screen"> 2674 2674 <code class="prompt">root# </code><strong class="userinput"><code>lpadmin -p quotaprinter -o job-quota-period=604800 \ … … 2677 2677 This would limit every single user to print no more than 100 pages or 1024 KB of 2678 2678 data (whichever comes first) within the last 604,800 seconds ( = 1 week). 2679 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id264 0510"></a>Correct and Incorrect Accounting</h3></div></div></div><p>2679 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2647481"></a>Correct and Incorrect Accounting</h3></div></div></div><p> 2680 2680 For CUPS to count correctly, the printfile needs to pass the CUPS pstops filter; otherwise it uses a dummy 2681 2681 count of “<span class="quote">one</span>”. Some print files do not pass it (e.g., image files), but then those are mostly … … 2688 2688 to a print-ready format for the target printer. This is currently working for about a thousand different 2689 2689 printer models. Linuxprinting.org has a driver <a class="ulink" href="http://www.linuxprinting.org/printer_list.cgi" target="_top">list</a>. 2690 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id264 0551"></a>Adobe and CUPS PostScript Drivers for Windows Clients</h3></div></div></div><p>2691 <a class="indexterm" name="id264 0560"></a>2692 <a class="indexterm" name="id264 0566"></a>2693 <a class="indexterm" name="id264 0573"></a>2694 <a class="indexterm" name="id264 0580"></a>2695 <a class="indexterm" name="id264 0587"></a>2690 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2647521"></a>Adobe and CUPS PostScript Drivers for Windows Clients</h3></div></div></div><p> 2691 <a class="indexterm" name="id2647530"></a> 2692 <a class="indexterm" name="id2647537"></a> 2693 <a class="indexterm" name="id2647544"></a> 2694 <a class="indexterm" name="id2647550"></a> 2695 <a class="indexterm" name="id2647557"></a> 2696 2696 Before CUPS 1.1.16, your only option was to use the Adobe PostScript driver on the Windows clients. The output 2697 2697 of this driver was not always passed through the <code class="literal">pstops</code> filter on the CUPS/Samba side, and … … 2704 2704 <code class="filename">cups-samba-1.1.16.tar.gz</code> package). It does <span class="emphasis"><em>not</em></span> work for Windows 2705 2705 9x/Me clients, but it guarantees: 2706 </p><div class="itemizedlist"><ul type="disc"><li><p> <a class="indexterm" name="id264 0647"></a> To not write a PJL-header.</p></li><li><p>To still read and support all PJL-options named in the2706 </p><div class="itemizedlist"><ul type="disc"><li><p> <a class="indexterm" name="id2647617"></a> To not write a PJL-header.</p></li><li><p>To still read and support all PJL-options named in the 2707 2707 driver PPD with its own means.</p></li><li><p>That the file will pass through the <code class="literal">pstops</code> filter 2708 2708 on the CUPS/Samba server.</p></li><li><p>To page-count correctly the print file.</p></li></ul></div><p> 2709 2709 You can read more about the setup of this combination in the man page for <code class="literal">cupsaddsmb</code> (which 2710 2710 is only present with CUPS installed, and only current from CUPS 1.1.16). 2711 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id264 0692"></a>The page_log File Syntax</h3></div></div></div><p>2712 <a class="indexterm" name="id264 0700"></a>2711 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2647662"></a>The page_log File Syntax</h3></div></div></div><p> 2712 <a class="indexterm" name="id2647670"></a> 2713 2713 These are the items CUPS logs in the <code class="filename">page_log</code> for every page of a job: 2714 2714 </p><div class="itemizedlist"><ul type="disc"><li><p>Printer name</p></li><li><p>User name</p></li><li><p>Job ID</p></li><li><p>Time of printing</p></li><li><p>Page number</p></li><li><p>Number of copies</p></li><li><p>A billing information string (optional)</p></li><li><p>The host that sent the job (included since version 1.1.19)</p></li></ul></div><p> … … 2728 2728 from IP address <code class="constant">10.160.51.33</code>, printed from one page 440 copies, and 2729 2729 is set to be billed to <em class="parameter"><code>finance-dep</code></em>. 2730 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id264 0836"></a>Possible Shortcomings</h3></div></div></div><p>2730 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2647807"></a>Possible Shortcomings</h3></div></div></div><p> 2731 2731 What flaws or shortcomings are there with this quota system? 2732 2732 </p><div class="itemizedlist"><ul type="disc"><li><p>The ones named above (wrongly logged job in case of … … 2742 2742 still be able to send and print a 1,000 sheet job.</p></li><li><p>A user being denied a job because of a filled-up quota 2743 2743 does not get a meaningful error message from CUPS other than 2744 “<span class="quote">client-error-not-possible</span>”.</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id264 0902"></a>Future Developments</h3></div></div></div><p>2744 “<span class="quote">client-error-not-possible</span>”.</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2647873"></a>Future Developments</h3></div></div></div><p> 2745 2745 This is the best system currently available, and there are huge 2746 2746 improvements under development for CUPS 1.2: … … 2750 2750 stop in the counting).</p></li><li><p>Quotas will be handled more flexibly.</p></li><li><p>Probably there will be support for users to inquire 2751 2751 about their accounts in advance.</p></li><li><p>Probably there will be support for some other tools 2752 around this topic.</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id264 0942"></a>Other Accounting Tools</h3></div></div></div><p>2752 around this topic.</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2647913"></a>Other Accounting Tools</h3></div></div></div><p> 2753 2753 Other accounting tools that can be used includes: PrintAnalyzer, pyKota, printbill, LogReport. 2754 2754 For more information regarding these tools you can try a Google search. 2755 </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id264 0956"></a>Additional Material</h2></div></div></div><p>2755 </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2647927"></a>Additional Material</h2></div></div></div><p> 2756 2756 A printer queue with <span class="emphasis"><em>no</em></span> PPD associated to it is a 2757 2757 “<span class="quote">raw</span>” printer, and all files will go directly there as received by the … … 2832 2832 to load the proper paper type before running the 10,000 page job 2833 2833 requested by marketing for the mailing, and so on). 2834 </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id264 1173"></a>Autodeletion or Preservation of CUPS Spool Files</h2></div></div></div><p>2835 <a class="indexterm" name="id264 1181"></a>2836 <a class="indexterm" name="id264 1188"></a>2837 <a class="indexterm" name="id264 1195"></a>2834 </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2648144"></a>Autodeletion or Preservation of CUPS Spool Files</h2></div></div></div><p> 2835 <a class="indexterm" name="id2648152"></a> 2836 <a class="indexterm" name="id2648159"></a> 2837 <a class="indexterm" name="id2648166"></a> 2838 2838 Samba print files pass through two spool directories. One is the incoming directory managed by Samba (set in 2839 the <a class="link" href="smb.conf.5.html#PATH" >path = /var/spool/samba</a> directive in the <em class="parameter"><code>[printers]</code></em> section of <code class="filename">smb.conf</code>). The other is the spool directory of your UNIX print subsystem. For2839 the <a class="link" href="smb.conf.5.html#PATH" target="_top">path = /var/spool/samba</a> directive in the <em class="parameter"><code>[printers]</code></em> section of <code class="filename">smb.conf</code>). The other is the spool directory of your UNIX print subsystem. For 2840 2840 CUPS it is normally <code class="filename">/var/spool/cups/</code>, as set by the <code class="filename">cupsd.conf</code> 2841 2841 directive <code class="filename">RequestRoot /var/spool/cups</code>. 2842 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id264 1249"></a>CUPS Configuration Settings Explained</h3></div></div></div><p>2842 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2648220"></a>CUPS Configuration Settings Explained</h3></div></div></div><p> 2843 2843 Some important parameter settings in the CUPS configuration file 2844 2844 <code class="filename">cupsd.conf</code> are: … … 2864 2864 (There are also additional settings for <em class="parameter"><code>MaxJobsPerUser</code></em> and 2865 2865 <em class="parameter"><code>MaxJobsPerPrinter</code></em>.) 2866 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id264 1334"></a>Preconditions</h3></div></div></div><p>2866 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2648305"></a>Preconditions</h3></div></div></div><p> 2867 2867 For everything to work as it should, you need to have three things: 2868 2868 </p><div class="itemizedlist"><ul type="disc"><li><p>A Samba smbd that is compiled against <code class="filename">libcups</code> (check 2869 2869 on Linux by running <strong class="userinput"><code>ldd `which smbd'</code></strong>).</p></li><li><p>A Samba-<code class="filename">smb.conf</code> setting of 2870 <a class="link" href="smb.conf.5.html#PRINTING" >printing = cups</a>.</p></li><li><p>Another Samba <code class="filename">smb.conf</code> setting of2871 <a class="link" href="smb.conf.5.html#PRINTCAP" >printcap = cups</a>.</p></li></ul></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>2870 <a class="link" href="smb.conf.5.html#PRINTING" target="_top">printing = cups</a>.</p></li><li><p>Another Samba <code class="filename">smb.conf</code> setting of 2871 <a class="link" href="smb.conf.5.html#PRINTCAP" target="_top">printcap = cups</a>.</p></li></ul></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> 2872 2872 In this case, all other manually set printing-related commands (like 2873 <a class="link" href="smb.conf.5.html#PRINTCOMMAND" >print command</a>,2874 <a class="link" href="smb.conf.5.html#LPQCOMMAND" >lpq command</a>,2875 <a class="link" href="smb.conf.5.html#LPRMCOMMAND" >lprm command</a>,2876 <a class="link" href="smb.conf.5.html#LPPAUSECOMMAND" >lppause command</a>, and2877 <a class="link" href="smb.conf.5.html#LPRESUMECOMMAND" >lpresume command</a>) are ignored, and they should normally have no2873 <a class="link" href="smb.conf.5.html#PRINTCOMMAND" target="_top">print command</a>, 2874 <a class="link" href="smb.conf.5.html#LPQCOMMAND" target="_top">lpq command</a>, 2875 <a class="link" href="smb.conf.5.html#LPRMCOMMAND" target="_top">lprm command</a>, 2876 <a class="link" href="smb.conf.5.html#LPPAUSECOMMAND" target="_top">lppause command</a>, and 2877 <a class="link" href="smb.conf.5.html#LPRESUMECOMMAND" target="_top">lpresume command</a>) are ignored, and they should normally have no 2878 2878 influence whatsoever on your printing. 2879 </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id264 1472"></a>Manual Configuration</h3></div></div></div><p>2880 If you want to do things manually, replace the <a class="link" href="smb.conf.5.html#PRINTING" >printing = cups</a>2881 by <a class="link" href="smb.conf.5.html#PRINTING" >printing = bsd</a>. Then your manually set commands may work2882 (I haven't tested this), and a <a class="link" href="smb.conf.5.html#PRINTCOMMAND" >print command = lp -d %P %s; rm %s</a>2879 </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2648444"></a>Manual Configuration</h3></div></div></div><p> 2880 If you want to do things manually, replace the <a class="link" href="smb.conf.5.html#PRINTING" target="_top">printing = cups</a> 2881 by <a class="link" href="smb.conf.5.html#PRINTING" target="_top">printing = bsd</a>. Then your manually set commands may work 2882 (I haven't tested this), and a <a class="link" href="smb.conf.5.html#PRINTCOMMAND" target="_top">print command = lp -d %P %s; rm %s</a> 2883 2883 may do what you need. 2884 </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id264 1520"></a>Printing from CUPS to Windows-Attached Printers</h2></div></div></div><p>2885 <a class="indexterm" name="id264 1529"></a>2886 <a class="indexterm" name="id264 1535"></a>2884 </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2648491"></a>Printing from CUPS to Windows-Attached Printers</h2></div></div></div><p> 2885 <a class="indexterm" name="id2648500"></a> 2886 <a class="indexterm" name="id2648506"></a> 2887 2887 From time to time the question arises, how can you print <span class="emphasis"><em>to</em></span> a Windows-attached printer 2888 2888 <span class="emphasis"><em>from</em></span> Samba? Normally the local connection from Windows host to printer would be done by … … 2919 2919 <code class="prompt">root# </code><strong class="userinput"><code>ln -s `which smbspool` /usr/lib/cups/backend/smb</code></strong> 2920 2920 </pre><p> 2921 <a class="indexterm" name="id264 1665"></a>2922 <a class="indexterm" name="id264 1671"></a>2921 <a class="indexterm" name="id2648636"></a> 2922 <a class="indexterm" name="id2648643"></a> 2923 2923 <code class="literal">smbspool</code> was written by Mike Sweet from the CUPS folks. It is included and ships with 2924 2924 Samba. It may also be used with print subsystems other than CUPS, to spool jobs to Windows printer shares. To … … 2935 2935 -P /path/to/PPD</code></strong> 2936 2936 </pre><p> 2937 <a class="indexterm" name="id264 1732"></a>2938 <a class="indexterm" name="id264 1739"></a>2939 <a class="indexterm" name="id264 1745"></a>2937 <a class="indexterm" name="id2648703"></a> 2938 <a class="indexterm" name="id2648710"></a> 2939 <a class="indexterm" name="id2648717"></a> 2940 2940 The PPD must be able to direct CUPS to generate the print data for the target model. For PostScript printers, 2941 2941 just use the PPD that would be used with the Windows NT PostScript driver. But what can you do if the printer … … 2950 2950 feature of CUPS and you do not necessarily need to have smbd running. 2951 2951 2952 </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id264 1816"></a>More CUPS Filtering Chains</h2></div></div></div><p>2952 </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2648787"></a>More CUPS Filtering Chains</h2></div></div></div><p> 2953 2953 The diagrams in <a class="link" href="CUPS-printing.html#cups1" title="Figure 22.17. Filtering Chain 1.">Filtering Chain 1</a> and <a class="link" href="CUPS-printing.html#cups2" title="Figure 22.18. Filtering Chain with cupsomatic">Filtering Chain with 2954 2954 cupsomatic</a> show how CUPS handles print jobs. 2955 </p><div class="figure"><a name="cups1"></a><p class="title"><b>Figure 22.17. Filtering Chain 1.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/cups1.png" alt="Filtering Chain 1."></div></div></div><br class="figure-break"><div class="figure"><a name="cups2"></a><p class="title"><b>Figure 22.18. Filtering Chain with cupsomatic</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/cups2.png" width="243" alt="Filtering Chain with cupsomatic"></div></div></div><br class="figure-break"></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id264 1927"></a>Common Errors</h2></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2641933"></a>Windows 9x/Me Client Can't Install Driver</h3></div></div></div><p>For Windows 9x/Me, clients require the printer names to be eight2955 </p><div class="figure"><a name="cups1"></a><p class="title"><b>Figure 22.17. Filtering Chain 1.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/cups1.png" alt="Filtering Chain 1."></div></div></div><br class="figure-break"><div class="figure"><a name="cups2"></a><p class="title"><b>Figure 22.18. Filtering Chain with cupsomatic</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/cups2.png" width="243" alt="Filtering Chain with cupsomatic"></div></div></div><br class="figure-break"></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2648899"></a>Common Errors</h2></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2648904"></a>Windows 9x/Me Client Can't Install Driver</h3></div></div></div><p>For Windows 9x/Me, clients require the printer names to be eight 2956 2956 characters (or “<span class="quote">8 plus 3 chars suffix</span>”) max; otherwise, the driver files 2957 will not get transferred when you want to download them from Samba.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="root-ask-loop"></a>“<span class="quote">cupsaddsmb</span>” Keeps Asking for Root Password in Never-ending Loop</h3></div></div></div><p>Have you set <a class="link" href="smb.conf.5.html#SECURITY" >security = user</a>? Have2957 will not get transferred when you want to download them from Samba.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="root-ask-loop"></a>“<span class="quote">cupsaddsmb</span>” Keeps Asking for Root Password in Never-ending Loop</h3></div></div></div><p>Have you set <a class="link" href="smb.conf.5.html#SECURITY" target="_top">security = user</a>? Have 2958 2958 you used <code class="literal">smbpasswd</code> to give root a Samba account? 2959 2959 You can do two things: open another terminal and execute … … 2964 2964 If the error is “<span class="quote">Tree connect failed: NT_STATUS_BAD_NETWORK_NAME</span>”, 2965 2965 you may have forgotten to create the <code class="filename">/etc/samba/drivers</code> directory. 2966 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id264 2010"></a>“<span class="quote">cupsaddsmb</span>” or “<span class="quote">rpcclient addriver</span>” Emit Error</h3></div></div></div><p>2966 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2648981"></a>“<span class="quote">cupsaddsmb</span>” or “<span class="quote">rpcclient addriver</span>” Emit Error</h3></div></div></div><p> 2967 2967 If <code class="literal">cupsaddsmb</code>, or <code class="literal">rpcclient addriver</code> emit the error message 2968 WERR_BAD_PASSWORD, refer to <a class="link" href="CUPS-printing.html#root-ask-loop" title=" “cupsaddsmb”Keeps Asking for Root Password in Never-ending Loop">the previous common error</a>.2969 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id264 2048"></a>“<span class="quote">cupsaddsmb</span>” Errors</h3></div></div></div><p>2968 WERR_BAD_PASSWORD, refer to <a class="link" href="CUPS-printing.html#root-ask-loop" title="cupsaddsmb Keeps Asking for Root Password in Never-ending Loop">the previous common error</a>. 2969 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2649019"></a>“<span class="quote">cupsaddsmb</span>” Errors</h3></div></div></div><p> 2970 2970 The use of “<span class="quote">cupsaddsmb</span>” gives “<span class="quote">No PPD file for printer...</span>” 2971 2971 message while PPD file is present. What might the problem be? … … 2978 2978 </p><p>Is your <em class="parameter"><code>TempDir</code></em> directive in 2979 2979 <code class="filename">cupsd.conf</code> set to a valid value, and is it writable? 2980 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id264 2122"></a>Client Can't Connect to Samba Printer</h3></div></div></div><p>Use <code class="literal">smbstatus</code> to check which user2980 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2649093"></a>Client Can't Connect to Samba Printer</h3></div></div></div><p>Use <code class="literal">smbstatus</code> to check which user 2981 2981 you are from Samba's point of view. Do you have the privileges to 2982 2982 write into the <em class="parameter"><code>[print$]</code></em> 2983 share?</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id264 2146"></a>New Account Reconnection from Windows 200x/XP Troubles</h3></div></div></div><p>2983 share?</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2649118"></a>New Account Reconnection from Windows 200x/XP Troubles</h3></div></div></div><p> 2984 2984 Once you are connected as the wrong user (for example, as <code class="constant">nobody</code>, which often occurs if 2985 you have <a class="link" href="smb.conf.5.html#MAPTOGUEST" >map to guest = bad user</a>), Windows Explorer will not accept an2985 you have <a class="link" href="smb.conf.5.html#MAPTOGUEST" target="_top">map to guest = bad user</a>), Windows Explorer will not accept an 2986 2986 attempt to connect again as a different user. There will not be any bytes transferred on the wire to Samba, 2987 2987 but still you'll see a stupid error message that makes you think Samba has denied access. Use … … 2996 2996 the <span class="guilabel">Network Neighborhood</span>), right-click on the printer in question, and select 2997 2997 <span class="guibutton">Connect....</span>. 2998 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id264 2237"></a>Avoid Being Connected to the Samba Server as the Wrong User</h3></div></div></div><p>2999 <a class="indexterm" name="id264 2246"></a>2998 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2649209"></a>Avoid Being Connected to the Samba Server as the Wrong User</h3></div></div></div><p> 2999 <a class="indexterm" name="id2649217"></a> 3000 3000 You see per <code class="literal">smbstatus</code> that you are connected as user nobody, but you want to be root or 3001 printer admin. This is probably due to <a class="link" href="smb.conf.5.html#MAPTOGUEST" >map to guest = bad user</a>, which3001 printer admin. This is probably due to <a class="link" href="smb.conf.5.html#MAPTOGUEST" target="_top">map to guest = bad user</a>, which 3002 3002 silently connected you under the guest account when you gave (maybe by accident) an incorrect username. Remove 3003 <a class="link" href="smb.conf.5.html#MAPTOGUEST" >map to guest</a> if you want to prevent this.3004 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id264 2289"></a>Upgrading to CUPS Drivers from Adobe Drivers</h3></div></div></div><p>3003 <a class="link" href="smb.conf.5.html#MAPTOGUEST" target="_top">map to guest</a> if you want to prevent this. 3004 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2649260"></a>Upgrading to CUPS Drivers from Adobe Drivers</h3></div></div></div><p> 3005 3005 This information came from a mailing list posting regarding problems experienced when 3006 3006 upgrading from Adobe drivers to CUPS drivers on Microsoft Windows NT/200x/XP clients. 3007 3007 </p><p>First delete all old Adobe-using printers. Then delete all old Adobe drivers. (On Windows 200x/XP, right-click in 3008 3008 the background of <span class="guilabel">Printers</span> folder, select <span class="guimenuitem">Server Properties...</span>, select 3009 tab <span class="guilabel">Drivers</span>, and delete here).</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id264 2326"></a>Can't Use “<span class="quote">cupsaddsmb</span>” on Samba Server, Which Is a PDC</h3></div></div></div><p>Do you use the “<span class="quote">naked</span>” root user name? Try to do it3009 tab <span class="guilabel">Drivers</span>, and delete here).</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2649298"></a>Can't Use “<span class="quote">cupsaddsmb</span>” on Samba Server, Which Is a PDC</h3></div></div></div><p>Do you use the “<span class="quote">naked</span>” root user name? Try to do it 3010 3010 this way: <strong class="userinput"><code>cupsaddsmb -U <em class="replaceable"><code>DOMAINNAME</code></em>\\root -v 3011 3011 <em class="replaceable"><code>printername</code></em></code></strong>> (note the two backslashes: the first one is 3012 required to “<span class="quote">escape</span>” the second one).</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id264 2362"></a>Deleted Windows 200x Printer Driver Is Still Shown</h3></div></div></div><p>Deleting a printer on the client will not delete the3012 required to “<span class="quote">escape</span>” the second one).</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2649333"></a>Deleted Windows 200x Printer Driver Is Still Shown</h3></div></div></div><p>Deleting a printer on the client will not delete the 3013 3013 driver too (to verify, right-click on the white background of the 3014 3014 <span class="guilabel">Printers</span> folder, select <span class="guimenuitem">Server Properties</span> and click on the … … 3016 3016 install a printer with the same name. If you want to update to a new 3017 3017 driver, delete the old ones first. Deletion is only possible if no 3018 other printer uses the same driver.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id264 2397"></a>Windows 200x/XP Local Security Policies</h3></div></div></div><a class="indexterm" name="id2642403"></a><a class="indexterm" name="id2642410"></a><p>Local security policies may not allow the installation of unsigned drivers “<span class="quote">local3019 security policies</span>” may not allow the installation of printer drivers at all.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id264 2430"></a>Administrator Cannot Install Printers for All Local Users</h3></div></div></div><p>3020 <a class="indexterm" name="id264 2438"></a>3021 <a class="indexterm" name="id264 2445"></a>3018 other printer uses the same driver.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2649368"></a>Windows 200x/XP Local Security Policies</h3></div></div></div><a class="indexterm" name="id2649374"></a><a class="indexterm" name="id2649381"></a><p>Local security policies may not allow the installation of unsigned drivers “<span class="quote">local 3019 security policies</span>” may not allow the installation of printer drivers at all.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2649401"></a>Administrator Cannot Install Printers for All Local Users</h3></div></div></div><p> 3020 <a class="indexterm" name="id2649410"></a> 3021 <a class="indexterm" name="id2649417"></a> 3022 3022 Windows XP handles SMB printers on a “<span class="quote">per-user</span>” basis. 3023 3023 This means every user needs to install the printer himself or herself. To have a printer available for … … 3025 3025 path of <em class="parameter"><code>http://cupsserver:631/printers/printername</code></em>. We're still looking into this one. 3026 3026 Maybe a logon script could automatically install printers for all users. 3027 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id264 2471"></a>Print Change, Notify Functions on NT Clients</h3></div></div></div><p>For print change, notify functions on NT++ clients. These need to run the <code class="literal">Server</code>3028 service first (renamed to <code class="literal">File & Print Sharing for MS Networks</code> in XP).</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id264 2496"></a>Windows XP SP1</h3></div></div></div><p>Windows XP SP1 introduced a Point and Print Restriction Policy (this restriction does not apply to3027 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2649442"></a>Print Change, Notify Functions on NT Clients</h3></div></div></div><p>For print change, notify functions on NT++ clients. These need to run the <code class="literal">Server</code> 3028 service first (renamed to <code class="literal">File & Print Sharing for MS Networks</code> in XP).</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2649468"></a>Windows XP SP1</h3></div></div></div><p>Windows XP SP1 introduced a Point and Print Restriction Policy (this restriction does not apply to 3029 3029 “<span class="quote">Administrator</span>” or “<span class="quote">Power User</span>” groups of users). In Group Policy Object Editor, go 3030 3030 to <span class="guimenu">User Configuration -> Administrative Templates -> Control Panel -> Printers</span>. The policy … … 3033 3033 <code class="constant">Users can only Point and Print to these servers</code> to make driver downloads from Samba 3034 3034 possible. 3035 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id264 2543"></a>Print Options for All Users Can't Be Set on Windows 200x/XP</h3></div></div></div><p>How are you doing it? I bet the wrong way (it is not easy to find out, though). There are three3035 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2649514"></a>Print Options for All Users Can't Be Set on Windows 200x/XP</h3></div></div></div><p>How are you doing it? I bet the wrong way (it is not easy to find out, though). There are three 3036 3036 different ways to bring you to a dialog that <span class="emphasis"><em>seems</em></span> to set everything. All three dialogs 3037 3037 <span class="emphasis"><em>look</em></span> the same, yet only one of them does what you intend. You need to be Administrator or … … 3063 3063 “<span class="quote">C.1. to C.6.</span>”, will save any settings permanently and be the defaults for new users. If you want 3064 3064 all clients to get the same defaults, you need to conduct these steps <span class="emphasis"><em>as Administrator</em></span> 3065 (<a class="link" href="smb.conf.5.html#PRINTERADMIN" >printer admin</a> in <code class="filename">smb.conf</code>) <span class="emphasis"><em>before</em></span> a client downloads the3065 (<a class="link" href="smb.conf.5.html#PRINTERADMIN" target="_top">printer admin</a> in <code class="filename">smb.conf</code>) <span class="emphasis"><em>before</em></span> a client downloads the 3066 3066 driver (the clients can later set their own <span class="emphasis"><em>per-user defaults</em></span> by following the procedures 3067 3067 <span class="emphasis"><em>A</em></span> or <span class="emphasis"><em>B</em></span>). 3068 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id264 2826"></a>Most Common Blunders in Driver Settings on Windows Clients</h3></div></div></div><p>3068 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2649797"></a>Most Common Blunders in Driver Settings on Windows Clients</h3></div></div></div><p> 3069 3069 Don't use <em class="parameter"><code>Optimize for Speed</code></em>, but use <em class="parameter"><code>Optimize for Portability</code></em> 3070 3070 instead (Adobe PS Driver). Don't use <em class="parameter"><code>Page Independence: No</code></em>. Always settle with … … 3073 3073 Driver). For <span class="guilabel">TrueType Download Options</span> choose <code class="constant">Outline</code>. Use 3074 3074 PostScript Level 2 if you are having trouble with a non-PS printer and if there is a choice. 3075 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id264 2881"></a><code class="literal">cupsaddsmb</code> Does Not Work with Newly Installed Printer</h3></div></div></div><p>3075 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2649853"></a><code class="literal">cupsaddsmb</code> Does Not Work with Newly Installed Printer</h3></div></div></div><p> 3076 3076 Symptom: The last command of <code class="literal">cupsaddsmb</code> does not complete successfully. If the <code class="literal">cmd 3077 3077 = setdriver printername printername</code> result was NT_STATUS_UNSUCCESSFUL, then possibly the printer was … … 3079 3079 hostname -c `enumprinters'</code>? Restart smbd (or send a <code class="literal">kill -HUP</code> to all processes 3080 3080 listed by <code class="literal">smbstatus</code>, and try again. 3081 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id264 2931"></a>Permissions on <code class="filename">/var/spool/samba/</code> Get Reset After Each Reboot</h3></div></div></div><p>3081 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2649902"></a>Permissions on <code class="filename">/var/spool/samba/</code> Get Reset After Each Reboot</h3></div></div></div><p> 3082 3082 Have you ever by accident set the CUPS spool directory to the same location (<em class="parameter"><code>RequestRoot 3083 3083 /var/spool/samba/</code></em> in <code class="filename">cupsd.conf</code> or the other way round: 3084 <code class="filename">/var/spool/cups/</code> is set as <a class="link" href="smb.conf.5.html#PATH" >path</a>> in the <em class="parameter"><code>[printers]</code></em> section)? These <em class="parameter"><code>must</code></em> be different. Set <em class="parameter"><code>RequestRoot3085 /var/spool/cups/</code></em> in <code class="filename">cupsd.conf</code> and <a class="link" href="smb.conf.5.html#PATH" >path =3084 <code class="filename">/var/spool/cups/</code> is set as <a class="link" href="smb.conf.5.html#PATH" target="_top">path</a>> in the <em class="parameter"><code>[printers]</code></em> section)? These <em class="parameter"><code>must</code></em> be different. Set <em class="parameter"><code>RequestRoot 3085 /var/spool/cups/</code></em> in <code class="filename">cupsd.conf</code> and <a class="link" href="smb.conf.5.html#PATH" target="_top">path = 3086 3086 /var/spool/samba</a> in the <em class="parameter"><code>[printers]</code></em> section of <code class="filename">smb.conf</code>. Otherwise, 3087 3087 cupsd will sanitize permissions to its spool directory with each restart and printing will not work reliably. 3088 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id26 43029"></a>Print Queue Called “<span class="quote">lp</span>” Mishandles Print Jobs</h3></div></div></div><p>3088 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2650001"></a>Print Queue Called “<span class="quote">lp</span>” Mishandles Print Jobs</h3></div></div></div><p> 3089 3089 In this case a print queue called “<span class="quote">lp</span>” intermittently swallows jobs and 3090 3090 spits out completely different ones from what was sent. 3091 3091 </p><p> 3092 <a class="indexterm" name="id26 43049"></a>3093 <a class="indexterm" name="id26 43056"></a>3094 <a class="indexterm" name="id26 43063"></a>3092 <a class="indexterm" name="id2650021"></a> 3093 <a class="indexterm" name="id2650028"></a> 3094 <a class="indexterm" name="id2650035"></a> 3095 3095 It is a bad idea to name any printer “<span class="quote">lp</span>”. This is the traditional UNIX name for the default 3096 3096 printer. CUPS may be set up to do an automatic creation of Implicit Classes. This means, to group all printers … … 3101 3101 <em class="replaceable"><code>printername@cupshost</code></em>, which gives you better control over what may happen in a 3102 3102 large networked environment. 3103 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id26 43098"></a>Location of Adobe PostScript Driver Files for “<span class="quote">cupsaddsmb</span>”</h3></div></div></div><p>3103 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2650070"></a>Location of Adobe PostScript Driver Files for “<span class="quote">cupsaddsmb</span>”</h3></div></div></div><p> 3104 3104 Use <code class="literal">smbclient</code> to connect to any Windows box with a shared PostScript printer: 3105 3105 <code class="literal">smbclient //windowsbox/print\$ -U guest</code>. You can navigate to the … … 3107 3107 <code class="filename">WIN40/0</code> to do the same. Another option is to download the <code class="filename">*.exe</code> 3108 3108 packaged files from the Adobe Web site. 3109 </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id26 43152"></a>Overview of the CUPS Printing Processes</h2></div></div></div><p>3109 </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2650124"></a>Overview of the CUPS Printing Processes</h2></div></div></div><p> 3110 3110 A complete overview of the CUPS printing processes can be found in <a class="link" href="CUPS-printing.html#a_small" title="Figure 22.19. CUPS Printing Overview.">the CUPS 3111 3111 Printing Overview diagram</a>. 3112 </p><div class="figure"><a name="a_small"></a><p class="title"><b>Figure 22.19. CUPS Printing Overview.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/a_small.png" width="243" alt="CUPS Printing Overview."></div></div></div><br class="figure-break"></div><div class="footnotes"><br><hr width="100" align="left"><div class="footnote"><p><sup>[<a name="ftn.id263 2393" href="#id2632393" class="para">6</a>] </sup>See also <a class="ulink" href="http://www.cups.org/cups-help.html" target="_top">http://www.cups.org/cups-help.html</a></p></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="classicalprinting.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="optional.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="VFS.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 21. Classical Printing Support </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 23. Stackable VFS modules</td></tr></table></div></body></html>3112 </p><div class="figure"><a name="a_small"></a><p class="title"><b>Figure 22.19. CUPS Printing Overview.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/a_small.png" width="243" alt="CUPS Printing Overview."></div></div></div><br class="figure-break"></div><div class="footnotes"><br><hr width="100" align="left"><div class="footnote"><p><sup>[<a name="ftn.id2639362" href="#id2639362" class="para">6</a>] </sup>See also <a class="ulink" href="http://www.cups.org/cups-help.html" target="_top">http://www.cups.org/cups-help.html</a></p></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="classicalprinting.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="optional.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="VFS.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 21. Classical Printing Support </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 23. Stackable VFS modules</td></tr></table></div></body></html>
Note:
See TracChangeset
for help on using the changeset viewer.
