| blob | 46ca8e15f7fedb75ba972b7e9e923304f7f6e664 |
1 <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 19. CUPS Printing Support in Samba 3.0</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.60.1"><link rel="home" href="index.html" title="SAMBA Project Documentation"><link rel="up" href="optional.html" title="Part III. Advanced Configuration"><link rel="previous" href="printing.html" title="Chapter 18. Classical Printing Support"><link rel="next" href="VFS.html" title="Chapter 20. 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 19. CUPS Printing Support in Samba 3.0</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="printing.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 19. CUPS Printing Support in Samba 3.0</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><tt class="email"><<a href="mailto:kpfeifle@danka.de">kpfeifle@danka.de</a>></tt></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><tt class="email"><<a href="mailto:CVizitiu@gbif.org">CVizitiu@gbif.org</a>></tt></p></div></div></div></div><div><p class="pubdate"> (3 June 2003) </p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="CUPS-printing.html#id2953785">Introduction</a></dt><dd><dl><dt><a href="CUPS-printing.html#id2953792">Features and Benefits</a></dt><dt><a href="CUPS-printing.html#id2953845">Overview</a></dt></dl></dd><dt><a href="CUPS-printing.html#id2953900">Basic Configuration of CUPS support</a></dt><dd><dl><dt><a href="CUPS-printing.html#id2953979">Linking of smbd with libcups.so</a></dt><dt><a href="CUPS-printing.html#id2954122">Simple smb.conf Settings for CUPS</a></dt><dt><a href="CUPS-printing.html#id2954205">More complex smb.conf Settings for
2 CUPS</a></dt></dl></dd><dt><a href="CUPS-printing.html#id2954322">Advanced Configuration</a></dt><dd><dl><dt><a href="CUPS-printing.html#id2954343">Central spooling vs. "Peer-to-Peer" printing</a></dt><dt><a href="CUPS-printing.html#id2954370">CUPS/Samba as a "spooling-only" Print Server; "raw" printing
3 with Vendor Drivers on Windows Clients</a></dt><dt><a href="CUPS-printing.html#id2954406">Driver Installation Methods on Windows Clients</a></dt><dt><a href="CUPS-printing.html#id2954465">Explicitly enable "raw" printing for
4 application/octet-stream!</a></dt><dt><a href="CUPS-printing.html#id2954626">Three familiar Methods for driver upload plus a new one</a></dt></dl></dd><dt><a href="CUPS-printing.html#id2954719">Using CUPS/Samba in an advanced Way -- intelligent printing
5 with PostScript Driver Download</a></dt><dd><dl><dt><a href="CUPS-printing.html#id2954794">GDI on Windows -- PostScript on Unix</a></dt><dt><a href="CUPS-printing.html#id2954839">Windows Drivers, GDI and EMF</a></dt><dt><a href="CUPS-printing.html#id2954940">Unix Printfile Conversion and GUI Basics</a></dt><dt><a href="CUPS-printing.html#id2955028">PostScript and Ghostscript</a></dt><dt><a href="CUPS-printing.html#id2955125">Ghostscript -- the Software RIP for non-PostScript Printers</a></dt><dt><a href="CUPS-printing.html#id2955238">PostScript Printer Description (PPD) Specification</a></dt><dt><a href="CUPS-printing.html#id2955308">CUPS can use all Windows-formatted Vendor PPDs</a></dt><dt><a href="CUPS-printing.html#id2955397">CUPS also uses PPDs for non-PostScript Printers</a></dt></dl></dd><dt><a href="CUPS-printing.html#id2955420">The CUPS Filtering Architecture</a></dt><dd><dl><dt><a href="CUPS-printing.html#id2955560">MIME types and CUPS Filters</a></dt><dt><a href="CUPS-printing.html#id2955747">MIME type Conversion Rules</a></dt><dt><a href="CUPS-printing.html#id2955864">Filter Requirements</a></dt><dt><a href="CUPS-printing.html#id2956034">Prefilters</a></dt><dt><a href="CUPS-printing.html#id2956120">pstops</a></dt><dt><a href="CUPS-printing.html#id2956222">pstoraster</a></dt><dt><a href="CUPS-printing.html#id2956377">imagetops and imagetoraster</a></dt><dt><a href="CUPS-printing.html#id2956434">rasterto [printers specific]</a></dt><dt><a href="CUPS-printing.html#id2956519">CUPS Backends</a></dt><dt><a href="CUPS-printing.html#id2956831">cupsomatic/Foomatic -- how do they fit into the Picture?</a></dt><dt><a href="CUPS-printing.html#id2956944">The Complete Picture</a></dt><dt><a href="CUPS-printing.html#id2956960">mime.convs</a></dt><dt><a href="CUPS-printing.html#id2957012">"Raw" printing</a></dt><dt><a href="CUPS-printing.html#id2957066">"application/octet-stream" printing</a></dt><dt><a href="CUPS-printing.html#id2957282">PostScript Printer Descriptions (PPDs) for non-PS Printers</a></dt><dt><a href="CUPS-printing.html#id2957510">Difference between cupsomatic/foomatic-rip and
6 native CUPS printing</a></dt><dt><a href="CUPS-printing.html#id2957666">Examples for filtering Chains</a></dt><dt><a href="CUPS-printing.html#id2957897">Sources of CUPS drivers / PPDs</a></dt><dt><a href="CUPS-printing.html#id2958024">Printing with Interface Scripts</a></dt></dl></dd><dt><a href="CUPS-printing.html#id2958100">Network printing (purely Windows)</a></dt><dd><dl><dt><a href="CUPS-printing.html#id2958116">From Windows Clients to an NT Print Server</a></dt><dt><a href="CUPS-printing.html#id2958155">Driver Execution on the Client</a></dt><dt><a href="CUPS-printing.html#id2958227">Driver Execution on the Server</a></dt></dl></dd><dt><a href="CUPS-printing.html#id2958289">Network Printing (Windows clients -- UNIX/Samba Print
7 Servers)</a></dt><dd><dl><dt><a href="CUPS-printing.html#id2958310">From Windows Clients to a CUPS/Samba Print Server</a></dt><dt><a href="CUPS-printing.html#id2958474">Samba receiving Jobfiles and passing them to CUPS</a></dt></dl></dd><dt><a href="CUPS-printing.html#id2958550">Network PostScript RIP: CUPS Filters on Server -- clients use
8 PostScript Driver with CUPS-PPDs</a></dt><dd><dl><dt><a href="CUPS-printing.html#id2958605">PPDs for non-PS Printers on UNIX</a></dt><dt><a href="CUPS-printing.html#id2958646">PPDs for non-PS Printers on Windows</a></dt></dl></dd><dt><a href="CUPS-printing.html#id2958712">Windows Terminal Servers (WTS) as CUPS Clients</a></dt><dd><dl><dt><a href="CUPS-printing.html#id2958729">Printer Drivers running in "Kernel Mode" cause many
9 Problems</a></dt><dt><a href="CUPS-printing.html#id2958763">Workarounds impose Heavy Limitations</a></dt><dt><a href="CUPS-printing.html#id2958784">CUPS: a "Magical Stone"?</a></dt><dt><a href="CUPS-printing.html#id2958811">PostScript Drivers with no major problems -- even in Kernel
10 Mode</a></dt></dl></dd><dt><a href="CUPS-printing.html#id2958865"> Setting up CUPS for driver Download</a></dt><dd><dl><dt><a href="CUPS-printing.html#id2958884">cupsaddsmb: the unknown Utility</a></dt><dt><a href="CUPS-printing.html#id2958976">Prepare your smb.conf for
11 cupsaddsmb</a></dt><dt><a href="CUPS-printing.html#id2959022">CUPS Package of "PostScript Driver for WinNT/2k/XP"</a></dt><dt><a href="CUPS-printing.html#id2959220">Recognize the different Driver Files</a></dt><dt><a href="CUPS-printing.html#id2959278">Acquiring the Adobe Driver Files</a></dt><dt><a href="CUPS-printing.html#id2959310">ESP Print Pro Package of "PostScript Driver for
12 WinNT/2k/XP"</a></dt><dt><a href="CUPS-printing.html#id2959360">Caveats to be considered</a></dt><dt><a href="CUPS-printing.html#id2959582">What are the Benefits of using the "CUPS PostScript Driver for
13 Windows NT/2k/XP" as compared to the Adobe Driver?</a></dt><dt><a href="CUPS-printing.html#id2959764">Run "cupsaddsmb" (quiet Mode)</a></dt><dt><a href="CUPS-printing.html#id2959865">Run "cupsaddsmb" with verbose Output</a></dt><dt><a href="CUPS-printing.html#id2960092">Understanding cupsaddsmb</a></dt><dt><a href="CUPS-printing.html#id2960186">How to recognize if cupsaddsm completed successfully</a></dt><dt><a href="CUPS-printing.html#id2960273">cupsaddsmb with a Samba PDC</a></dt><dt><a href="CUPS-printing.html#id2960308">cupsaddsmb Flowchart</a></dt><dt><a href="CUPS-printing.html#id2960361">Installing the PostScript Driver on a Client</a></dt><dt><a href="CUPS-printing.html#id2960474">Avoiding critical PostScript Driver Settings on the
14 Client</a></dt></dl></dd><dt><a href="CUPS-printing.html#id2960608">Installing PostScript Driver Files manually (using
15 rpcclient)</a></dt><dd><dl><dt><a href="CUPS-printing.html#id2960723">A Check of the rpcclient man Page</a></dt><dt><a href="CUPS-printing.html#id2960836">Understanding the rpcclient man Page</a></dt><dt><a href="CUPS-printing.html#id2960925">Producing an Example by querying a Windows Box</a></dt><dt><a href="CUPS-printing.html#id2961015">What is required for adddriver and setdriver to succeed</a></dt><dt><a href="CUPS-printing.html#id2961177">Manual Commandline Driver Installation in 15 little Steps</a></dt><dt><a href="CUPS-printing.html#id2961830">Troubleshooting revisited</a></dt></dl></dd><dt><a href="CUPS-printing.html#id2961930">The printing *.tdb Files</a></dt><dd><dl><dt><a href="CUPS-printing.html#id2962033">Trivial DataBase Files</a></dt><dt><a href="CUPS-printing.html#id2962103">Binary Format</a></dt><dt><a href="CUPS-printing.html#id2962165">Losing *.tdb Files</a></dt><dt><a href="CUPS-printing.html#id2962224">Using tdbbackup</a></dt></dl></dd><dt><a href="CUPS-printing.html#id2962290">CUPS Print Drivers from Linuxprinting.org</a></dt><dd><dl><dt><a href="CUPS-printing.html#id2962398">foomatic-rip and Foomatic explained</a></dt><dt><a href="CUPS-printing.html#id2963027">foomatic-rip and Foomatic-PPD Download and Installation</a></dt></dl></dd><dt><a href="CUPS-printing.html#id2963488">Page Accounting with CUPS</a></dt><dd><dl><dt><a href="CUPS-printing.html#id2963519">Setting up Quotas</a></dt><dt><a href="CUPS-printing.html#id2963551">Correct and incorrect Accounting</a></dt><dt><a href="CUPS-printing.html#id2963592">Adobe and CUPS PostScript Drivers for Windows Clients</a></dt><dt><a href="CUPS-printing.html#id2963663">The page_log File Syntax</a></dt><dt><a href="CUPS-printing.html#id2963765">Possible Shortcomings</a></dt><dt><a href="CUPS-printing.html#id2963836">Future Developments</a></dt><dt><a href="CUPS-printing.html#id2963884">Other Accounting Tools</a></dt></dl></dd><dt><a href="CUPS-printing.html#id2963899">Additional Material</a></dt><dt><a href="CUPS-printing.html#id2964092">Auto-Deletion or Preservation of CUPS Spool Files</a></dt><dd><dl><dt><a href="CUPS-printing.html#id2964138">CUPS Configuration Settings explained</a></dt><dt><a href="CUPS-printing.html#id2964221">Pre-conditions</a></dt><dt><a href="CUPS-printing.html#id2964281">Manual Configuration</a></dt></dl></dd><dt><a href="CUPS-printing.html#id2964299">When not to use Samba to print to
16 CUPS</a></dt><dt><a href="CUPS-printing.html#id2964316">In Case of Trouble.....</a></dt><dd><dl><dt><a href="CUPS-printing.html#id2964352">Where to find Documentation</a></dt><dt><a href="CUPS-printing.html#id2964364">How to ask for Help</a></dt><dt><a href="CUPS-printing.html#id2964377">Where to find Help</a></dt></dl></dd><dt><a href="CUPS-printing.html#id2964391">Appendix</a></dt><dd><dl><dt><a href="CUPS-printing.html#id2964398">Printing from CUPS to Windows attached
17 Printers</a></dt><dt><a href="CUPS-printing.html#id2964612">More CUPS filtering Chains</a></dt><dt><a href="CUPS-printing.html#id2964919">Trouble Shooting Guidelines to fix typical Samba printing
18 Problems</a></dt><dt><a href="CUPS-printing.html#id2966041">An Overview of the CUPS Printing Processes</a></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2953785"></a>Introduction</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2953792"></a>Features and Benefits</h3></div></div><div></div></div><p>
19 The Common Unix Print System (<a href="http://www.cups.org/" target="_top">CUPS</a>) has become very popular. All
20 big Linux distributions now ship it as their default printing
21 system. But to many it is still a very mystical tool. Normally it
23 which they don't want to look into, as long as it works OK. But once
24 there is a little problem, they are in trouble to find out where to
25 start debugging it. Also, even the most recent and otherwise excellent
26 printed Samba documentation has only limited attention paid to CUPS
27 printing, leaving out important pieces or even writing plain wrong
28 things about it. This demands rectification. But before you dive into
29 this chapter, make sure that you don't forget to refer to the
31 that is relevant for CUPS too.
32 </p><p>
33 CUPS sports quite a few unique and powerful features. While their
34 basic functions may be grasped quite easily, they are also
35 new. Because they are different from other, more traditional printing
36 systems, it is best to try and not apply any prior knowledge about
37 printing upon this new system. Rather try to start understand CUPS
38 from the beginning. This documentation will lead you here to a
39 complete understanding of CUPS, if you study all of the material
40 contained. But lets start with the most basic things first. Maybe this
41 is all you need for now. Then you can skip most of the other
42 paragraphs.
43 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2953845"></a>Overview</h3></div></div><div></div></div><p>
44 CUPS is more than just a print spooling system. It is a complete
45 printer management system that complies with the new IPP
48 standard for network printing. Many of its functions can be managed
49 remotely (or locally) via a web browser (giving you a
50 platform-independent access to the CUPS print server). In addition it
51 has the traditional commandline and several more modern GUI interfaces
52 (GUI interfaces developed by 3rd parties, like KDE's
54 </p><p>
57 file format conversion as required for the printer). In many ways
58 this gives CUPS similar capabilities to the MS Windows print
59 monitoring system. Of course, if you are a CUPS advocate, you would
60 argue that CUPS is better! In any case, let us now move on to
61 explore how one may configure CUPS for interfacing with MS Windows
62 print clients via Samba.
63 </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2953900"></a>Basic Configuration of CUPS support</h2></div></div><div></div></div><p>
66 settings: <i class="parameter"><tt>printing = cups</tt></i> and <i class="parameter"><tt>printcap
67 = cups</tt></i>. CUPS itself doesn't need a printcap file
69 file knows two related directives: they control if such a file should
70 be automatically created and maintained by CUPS for the convenience of
73 BSD</tt></i>). These legacy programs often require the existence of
74 printcap file containing printernames or they will refuse to
75 print. Make sure CUPS is set to generate and maintain a printcap! For
77 documentation, like the wealth of documents on your CUPS server
78 itself: <a href="http://localhost:631/documentation.html" target="_top">http://localhost:631/documentation.html</a>.
79 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2953979"></a>Linking of smbd with libcups.so</h3></div></div><div></div></div><p>
80 Samba has a very special relationship to CUPS. The reason is: Samba
81 can be compiled with CUPS library support. Most recent installations
82 have this support enabled, and per default CUPS linking is compiled
83 into smbd and other Samba binaries. Of course, you can use CUPS even
85 there are some differences in required or supported configuration
86 then.
87 </p><p>
89 cups</tt></i> uses the CUPS API to list printers, submit jobs,
90 query queues, etc. Otherwise it maps to the System V commands with an
93 details (ldd may not be present on other OS platforms, or its function
94 may be embodied by a different command):
96 transmeta:/home/kurt # ldd `which smbd`
100 [....]
101 </pre><p>
104 into this version of Samba. If this is the case, and printing = cups
107 important point to remember!
108 </p><div class="tip" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Tip</h3><p> Should you require -- for any reason -- to set your own
110 sysv</tt></i>. However, you'll loose all the benefits from the
111 close CUPS/Samba integration. You are on your own then to manually
112 configure the rest of the printing system commands (most important:
116 command</tt></i>).</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2954122"></a>Simple <tt class="filename">smb.conf</tt> Settings for CUPS</h3></div></div><div></div></div><p>
117 To summarize, here is the simplest printing-related setup
121 [global]
122 load printers = yes
123 printing = cups
124 printcap name = cups
126 [printers]
127 comment = All Printers
128 path = /var/spool/samba
129 browseable = no
130 public = yes
131 guest ok = yes
132 writable = no
133 printable = yes
134 printer admin = root, @ntadmins
136 </pre><p>
137 This is all you need for basic printing setup for CUPS. It will print
138 all Graphic, Text, PDF and PostScript file submitted from Windows
139 clients. However, most of your Windows users would not know how to
140 send these kind of files to print without opening a GUI
141 application. Windows clients tend to have local printer drivers
142 installed. And the GUI application's print buttons start a printer
143 driver. Your users also very rarely send files from the command
144 line. Unlike UNIX clients, they hardly submit graphic, text or PDF
145 formatted files directly to the spooler. They nearly exclusively print
147 applications native format and the print data stream. If the backend
149 sensible only for the target printer. Read on to learn which problem
150 this may cause and how to avoid it.
151 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2954205"></a>More complex <tt class="filename">smb.conf</tt> Settings for
152 CUPS</h3></div></div><div></div></div><p>
153 Here is a slightly more complex printing-related setup
155 support for all printers, but defines one printer share which is set
156 up differently.
159 [global]
160 printing = cups
161 printcap name = cups
162 load printers = yes
164 [printers]
165 comment = All Printers
166 path = /var/spool/samba
167 public = yes
168 guest ok = yes
169 writable = no
170 printable = yes
171 printer admin = root, @ntadmins
173 [special_printer]
174 comment = A special printer with his own settings
175 path = /var/spool/samba-special
176 printing = sysv
177 printcap = lpstat
181 rm %f
182 public = no
183 guest ok = no
184 writeable = no
185 printable = yes
186 printer admin = kurt
187 hosts deny = 0.0.0.0
190 </pre><p>
191 This special share is only there for my testing purposes. It doesn't
192 even write the print job to a file. It just logs the job parameters
196 guest access is not allowed; the share isn't announced in Network
197 Neighbourhood (so you need to know it is there), and it is only
198 allowing access from three hosts. To prevent CUPS kicking in and
199 taking over the print jobs for that share, we need to set
201 lpstat</tt></i>.
202 </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2954322"></a>Advanced Configuration</h2></div></div><div></div></div><p>
203 Before we dive into all the configuration options, let's clarify a few
205 correctly</em></span>. Often this is not done correctly. Legacy systems
206 or small LANs in business environments often lack a clear design and
207 good housekeeping.
208 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2954343"></a>Central spooling vs. "Peer-to-Peer" printing</h3></div></div><div></div></div><p>
209 Many small office or home networks, as well as badly organized larger
210 environments, allow each client a direct access to available network
211 printers. Generally, this is a bad idea. It often blocks one client's
212 access to the printer when another client's job is printing. It also
213 might freeze the first client's application while it is waiting to get
214 rid of the job. Also, there are frequent complaints about various jobs
215 being printed with their pages mixed with each other. A better concept
217 central system, which responds immediately, takes jobs from multiple
218 concurrent clients at the same time and in turn transfers them to the
219 printer(s) in the correct order.
220 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2954370"></a>CUPS/Samba as a "spooling-only" Print Server; "raw" printing
221 with Vendor Drivers on Windows Clients</h3></div></div><div></div></div><p>
222 Most traditionally configured Unix print servers acting on behalf of
223 Samba's Windows clients represented a really simple setup. Their only
225 Samba. This approach meant that the Windows clients were expected to
226 prepare the print job file in such a way that it became fit to be fed to
227 the printing device. Here a native (vendor-supplied) Windows printer
228 driver for the target device needed to be installed on each and every
229 client.
230 </p><p>
231 Of course you can setup CUPS, Samba and your Windows clients in the
232 same, traditional and simple way. When CUPS printers are configured
233 for RAW print-through mode operation it is the responsibility of the
234 Samba client to fully render the print job (file). The file must be
235 sent in a format that is suitable for direct delivery to the
236 printer. Clients need to run the vendor-provided drivers to do
237 this. In this case CUPS will NOT do any print file format conversion
238 work.
239 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2954406"></a>Driver Installation Methods on Windows Clients</h3></div></div><div></div></div><p>
240 The printer drivers on the Windows clients may be installed
241 in two functionally different ways:
242 </p><div class="itemizedlist"><ul type="disc"><li><p>manually install the drivers locally on each client,
245 type of connection.</p></li><li><p>deposit and prepare the drivers (for later download) on
246 the print server (Samba); this enables the clients to use
248 first time they access the printer; with this method NT/2K/XP
250 type printing calls.</p></li></ul></div><p>
251 The second method is recommended for use over the first.
252 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2954465"></a>Explicitly enable "raw" printing for
253 <span class="emphasis"><em>application/octet-stream</em></span>!</h3></div></div><div></div></div><p>
254 If you use the first option (drivers are installed on the client
255 side), there is one setting to take care of: CUPS needs to be told
257 formats. The CUPS files that need to be correctly set for RAW mode
258 printers to work are:
261 Both contain entries (at the end of the respective files) which must
262 be uncommented to allow RAW mode operation.
264 present:
267 application/octet-stream
269 </pre><p>
271 have this line:
274 application/octet-stream application/vnd.cups-raw 0 -
276 </pre><p>
277 If these two files are not set up correctly for raw Windows client
280 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>editing the <tt class="filename">mime.convs</tt> and the
285 CUPS being a more security-aware printing system than traditional ones
286 does not by default allow a user to send deliberate (possibly binary)
287 data to printing devices. This could be easily abused to launch a
291 allowed to go to the printer. By default, you can only send other
293 try to convert them and passes them to the printer untouched (see next
294 chapter for even more background explanations).
295 </p><p>
296 This is all you need to know to get the CUPS/Samba combo printing
298 locally installed. If you are not interested in background information about
299 more advanced CUPS/Samba printing, simply skip the remaining sections
300 of this chapter.
301 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2954626"></a>Three familiar Methods for driver upload plus a new one</h3></div></div><div></div></div><p>
302 If you want to use the MS-RPC type printing, you must upload the
304 share). For a discussion on how to deposit printer drivers on the
305 Samba host (so that the Windows clients can download and use them via
307 HOWTO Collection. There you will find a description or reference to
308 three methods of preparing the client drivers on the Samba server:
314 method.</p></li></ul></div><p>
315 These 3 methods apply to CUPS all the same. A new and more
316 convenient way to load the Windows drivers into Samba is provided
317 provided if you use CUPS:
318 </p><div class="itemizedlist"><ul type="disc"><li><p>the <span class="emphasis"><em>cupsaddsmb</em></span>
319 utility.</p></li></ul></div><p>
320 cupsaddsmb is discussed in much detail further below. But we will
321 first explore the CUPS filtering system and compare the Windows and
322 UNIX printing architectures.
323 </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2954719"></a>Using CUPS/Samba in an advanced Way -- intelligent printing
324 with PostScript Driver Download</h2></div></div><div></div></div><p>
325 Still reading on? Good. Let's go into more detail then. We now know
328 </p><p>
329 Possibly you need to setup CUPS in a more smart way. The reasons could
330 be manifold:
331 </p><div class="itemizedlist"><ul type="disc"><li><p>Maybe your boss wants to get monthly statistics: Which
332 printer did how many pages? What was the average data size of a job?
333 What was the average print run per day? What are the typical hourly
334 peaks in printing? Which departments prints how
335 much?</p></li><li><p>Maybe you are asked to setup a print quota system:
336 users should not be able to print more jobs, once they have surpassed
337 a given limit per period?</p></li><li><p>Maybe your previous network printing setup is a mess
338 and shall be re-organized from a clean beginning?</p></li><li><p>Maybe you have experiencing too many "Blue Screens",
339 originating from poorly debugged printer drivers running in NT "kernel
341 These goals cannot be achieved by a raw print server. To build a
342 server meeting these requirements, you'll first need to learn about
343 how CUPS works and how you can enable its features.
344 </p><p>
345 What follows is the comparison of some fundamental concepts for
346 Windows and Unix printing; then is the time for a description of the
347 CUPS filtering system, how it works and how you can tweak it.
348 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2954794"></a>GDI on Windows -- PostScript on Unix</h3></div></div><div></div></div><p>
349 Network printing is one of the most complicated and error-prone
350 day-to-day tasks any user or an administrator may encounter. This is
351 true for all OS platforms. And there are reasons for this.
352 </p><p>
353 You can't expect for most file formats to just throw them towards
354 printers and they get printed. There needs to be a file format
355 conversion in between. The problem is: there is no common standard for
356 print file formats across all manufacturers and printer types. While
362 unacceptable license fees for using printer-embedded PostScript
363 interpreters, etc.).
364 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2954839"></a>Windows Drivers, GDI and EMF</h3></div></div><div></div></div><p>
365 In Windows OS, the format conversion job is done by the printer
366 drivers. On MS Windows OS platforms all application programmers have
368 Interface</em></span>), as part and parcel of the OS itself, to base
369 themselves on. This GDI core is used as one common unified ground, for
370 all Windows programs, to draw pictures, fonts and documents
372 paper</em></span> (=print). Therefore printer driver developers can
373 standardize on a well-defined GDI output for their own driver
375 relatively easy, because the on-screen graphic primitives, as well as
376 the on-paper drawn objects, come from one common source. This source,
378 MetaFile</em></span>). The EMF is processed by the printer driver and
379 converted to the printer-specific file format.
380 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
381 To the GDI foundation in MS Windows, Apple has chosen to
382 put paper and screen output on a common foundation for their
383 (BSD-Unix-based, did you know??) Mac OS X and Darwin Operating
386 </p></div><p>
388 </p><div class="figure"><a name="id2954904"></a><p class="title"><b>Figure 19.1. Windows Printing to a local Printer</b></p><div class="mediaobject"><img src="projdoc/imagefiles/1small.png" alt="Windows Printing to a local Printer"></div></div><p>
389 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2954940"></a>Unix Printfile Conversion and GUI Basics</h3></div></div><div></div></div><p>
390 In Unix and Linux, there is no comparable layer built into the OS
391 kernel(s) or the X (screen display) server. Every application is
392 responsible for itself to create its print output. Fortunately, most
393 use PostScript. That gives at least some common ground. Unfortunately,
394 there are many different levels of quality for this PostScript. And
395 worse: there is a huge difference (and no common root) in the way how
396 the same document is displayed on screen and how it is presented on
397 paper. WYSIWYG is more difficult to achieve. This goes back to the
399 designing the UNIX foundations and protocols for Graphical User
401 also, as some had demanded at the time, and restricted itself to
403 under development, attempting to build printing support into the X
404 framework, including a PostScript and a PCL driver, but it is not yet
405 ready for prime time.) You can see this unfavorable inheritance up to
407 system; there are separate ones for fonts used for X display and fonts
408 to be used on paper.
411 but its specifications have been published to the full. Its strength
412 lies in its powerful abilities to describe graphical objects (fonts,
413 shapes, patterns, lines, curves, dots...), their attributes (color,
414 linewidth...) and the way to manipulate (scale, distort, rotate,
415 shift...) them. Because of its open specification, anybody with the
416 skill can start writing his own implementation of a PostScript
417 interpreter and use it to display PostScript files on screen or on
418 paper. Most graphical output devices are based on the concept of
420 plotters). Of course, you can look at a PostScript file in its textual
421 form and you will be reading its PostScript code, the language
422 instructions which need to be interpreted by a rasterizer. Rasterizers
423 produce pixel images, which may be displayed on screen by a viewer
424 program or on paper by a printer.
425 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2955028"></a>PostScript and Ghostscript</h3></div></div><div></div></div><p>
426 So, Unix is lacking a common ground for printing on paper and
427 displaying on screen. Despite this unfavorable legacy for Unix, basic
428 printing is fairly easy: if you have PostScript printers at your
429 disposal! The reason is: these devices have a built-in PostScript
431 Processor</em></span> (RIP), (which makes them more expensive than
432 other types of printers); throw PostScript towards them, and they will
433 spit out your printed pages. Their RIP is doing all the hard work of
434 converting the PostScript drawing commands into a bitmap picture as
435 you see it on paper, in a resolution as done by your printer. This is
436 no different to PostScript printing of a file from a Windows origin.
437 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>Traditional Unix programs and printing systems -- while
438 using PostScript -- are largely not PPD-aware. PPDs are "PostScript
439 Printer Description" files. They enable you to specify and control all
440 options a printer supports: duplexing, stapling, punching... Therefore
441 Unix users for a long time couldn't choose many of the supported
442 device and job options, unlike Windows or Apple users. But now there
443 is CUPS.... ;-)
444 </p></div><p>
445 </p><div class="figure"><a name="id2955075"></a><p class="title"><b>Figure 19.2. Printing to a Postscript Printer</b></p><div class="mediaobject"><img src="projdoc/imagefiles/2small.png" alt="Printing to a Postscript Printer"></div></div><p>
446 </p><p>
447 However, there are other types of printers out there. These don't know
449 Language</em></span> (PDL, often proprietary). To print to them is much
450 more demanding. Since your Unix applications mostly produce
451 PostScript, and since these devices don't understand PostScript, you
452 need to convert the printfiles to a format suitable for your printer
453 on the host, before you can send it away.
454 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2955125"></a>Ghostscript -- the Software RIP for non-PostScript Printers</h3></div></div><div></div></div><p>
456 the traditional (and quite powerful) PostScript interpreter used on
457 Unix platforms. It is a RIP in software, capable to do a
459 spectrum of hardware devices as well as software file formats.
460 Ghostscript technology and drivers is what enables PostScript printing
461 to non-PostScript hardware.
462 </p><p>
463 </p><div class="figure"><a name="id2955155"></a><p class="title"><b>Figure 19.3. Ghostscript as a RIP for non-postscript printers</b></p><div class="mediaobject"><img src="projdoc/imagefiles/3small.png" alt="Ghostscript as a RIP for non-postscript printers"></div></div><p>
464 </p><div class="tip" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Tip</h3><p>
466 Ghostscript version. If you specify e.g. a parameter of
468 line, you are asking Ghostscript to convert the input into a PNG
470 single parameter to tell Ghostscript how exactly it should render the
471 input. New Ghostscript versions are released at fairly regular
472 intervals, now by artofcode LLC. They are initially put under the
474 AFPL version appears. GNU Ghostscript is probably the version
475 installed on most Samba systems. But it has got some
476 deficiencies. Therefore ESP Ghostscript was developed as an
477 enhancement over GNU Ghostscript, with lots of bug-fixes, additional
478 devices and improvements. It is jointly maintained by developers from
479 CUPS, Gimp-Print, MandrakeSoft, SuSE, RedHat and Debian. It includes
481 </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2955238"></a>PostScript Printer Description (PPD) Specification</h3></div></div><div></div></div><p>
483 Language</em></span> (PDL) to represent the page layout in a
485 always ending up to be output on a hardware with device-specific
486 features. To take care of all the differences in hardware, and to
487 allow for innovations, Adobe has specified a syntax and file format
489 files. Every PostScript printer ships with one of these files.
490 </p><p>
491 PPDs contain all information about general and special features of the
492 given printer model: Which different resolutions can it handle? Does
493 it have a Duplexing Unit? How many paper trays are there? What media
494 types and sizes does it take? For each item it also names the special
495 command string to be sent to the printer (mostly inside the PostScript
496 file) in order to enable it.
497 </p><p>
498 Information from these PPDs is meant to be taken into account by the
499 printer drivers. Therefore, installed as part of the Windows
500 PostScript driver for a given printer is the printer's PPD. Where it
501 makes sense, the PPD features are presented in the drivers' UI dialogs
502 to display to the user as choice of print options. In the end, the
503 user selections are somehow written (in the form of special
504 PostScript, PJL, JCL or vendor-dependent commands) into the PostScript
505 file created by the driver.
506 </p><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p>
507 A PostScript file that was created to contain device-specific commands
508 for achieving a certain print job output (e.g. duplexed, stapled and
509 punched) on a specific target machine, may not print as expected, or
510 may not be printable at all on other models; it also may not be fit
511 for further processing by software (e.g. by a PDF distilling program).
512 </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2955308"></a>CUPS can use all Windows-formatted Vendor PPDs</h3></div></div><div></div></div><p>
513 CUPS can handle all spec-compliant PPDs as supplied by the
514 manufacturers for their PostScript models. Even if a
515 Unix/Linux-illiterate vendor might not have mentioned our favorite
516 OS in his manuals and brochures -- you can safely trust this:
518 can use it unchanged in CUPS</em></span> and thus access the full
519 power of your printer just like a Windows NT user could!
520 </p><div class="tip" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Tip</h3><p>
521 To check the spec compliance of any PPD online, go to <a href="http://www.cups.org/testppd.php" target="_top">http://www.cups.org/testppd.php</a>
522 and upload your PPD. You will see the results displayed
523 immediately. CUPS in all versions after 1.1.19 has a much more strict
524 internal PPD parsing and checking code enabled; in case of printing
525 trouble this online resource should be one of your first pitstops.
526 </p></div><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p>
528 <span class="emphasis"><em>Foomatic</em></span> or <span class="emphasis"><em>cupsomatic</em></span>
529 PPDs from Linuxprinting.org. With these devices the original
530 vendor-provided PPDs are always the first choice!
531 </p></div><div class="tip" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Tip</h3><p>
532 If you are looking for an original vendor-provided PPD of a specific
533 device, and you know that an NT4 box (or any other Windows box) on
534 your LAN has the PostScript driver installed, just use
536 access the Windows directory where all printer driver files are
538 the PPD you are seeking.
539 </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2955397"></a>CUPS also uses PPDs for non-PostScript Printers</h3></div></div><div></div></div><p>
540 CUPS also uses specially crafted PPDs to handle non-PostScript
541 printers. These PPDs are usually not available from the vendors (and
542 no, you can't just take the PPD of a Postscript printer with the same
543 model name and hope it works for the non-PostScript version too). To
544 understand how these PPDs work for non-PS printers we first need to
545 dive deeply into the CUPS filtering and file format conversion
546 architecture. Stay tuned.
547 </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2955420"></a>The CUPS Filtering Architecture</h2></div></div><div></div></div><p>
548 The core of the CUPS filtering system is based on
550 uses some other filters of its own. You (or your OS vendor) may have
551 plugged in even more filters. CUPS handles all data file formats under
553 printfile is subjected to an initial
555 MIME type. A given MIME type implies zero or more possible filtering
556 chains relevant to the selected target printer. This section discusses
557 how MIME types recognition and conversion rules interact. They are
558 used by CUPS to automatically setup a working filtering chain for any
559 given input data format.
560 </p><p>
562 a bitmap, this is done in 2 stages:
563 </p><div class="itemizedlist"><ul type="disc"><li><p>the first stage uses a Ghostscript device named "cups"
564 (this is since version 1.1.15) and produces a generic raster format
567 the generic CUPS raster to a device specific raster.</p></li></ul></div><p>
573 Ghostscript</em></span> and re-compile or use <a href="http://www.cups.org/ghostscript.php" target="_top">ESP Ghostscript</a>. The
574 superior alternative is ESP Ghostscript: it supports not just CUPS,
575 but 300 other devices too (while GNU Ghostscript supports only about
576 180). Because of this broad output device support, ESP Ghostscript is
577 the first choice for non-CUPS spoolers too. It is now recommended by
578 Linuxprinting.org for all spoolers.
579 </p><p>
581 rendering paths. One of the most common ones is provided by the
582 <span class="emphasis"><em>Foomatic/cupsomatic</em></span> concept, from <a href="http://www.linuxprinting.org/" target="_top">Linuxprinting.org</a>. This
583 uses the classical Ghostscript approach, doing everything in one
585 others. However, even for Foomatic/cupsomatic usage, best results and
586 broadest printer model support is provided by ESP Ghostscript (more
587 about cupsomatic/Foomatic, particularly the new version called now
589 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2955560"></a>MIME types and CUPS Filters</h3></div></div><div></div></div><p>
592 in the same directory) upon startup. These files contain the MIME
593 type recognition rules which are applied when CUPS runs its
594 auto-typing routines. The rule syntax is explained in the man page
597 like this:
600 application/pdf pdf string(0,%PDF)
602 </pre><p>
603 This means: if a filename has either a
606 beginning of the file itself (offset 0 from the start), then it is
608 Another rule is this:
613 </pre><p>
614 Its meaning: if the filename has one of the suffixes
617 strings <span class="emphasis"><em>%!</em></span> or <span class="emphasis"><em><04>%!</em></span>, it
618 is a generic PostScript file
620 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
621 There is a very important difference between two similar MIME type in
625 independent (job options for the file are still outside the PS file
626 content, embedded in commandline or environment variables by CUPS),
628 options inserted into the PostScript data itself (were
629 applicable). The transformation of the generic PostScript
630 (application/postscript) to the device-specific version
631 (application/vnd.cups-postscript) is the responsibility of the
633 contained in the PPD to do the transformation.
634 </p></div><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p>
635 Don't confuse the other mime.types file your system might be using
637 </p></div><p>
638 CUPS can handle ASCII text, HP-GL, PDF, PostScript, DVI and a
639 lot of image formats (GIF. PNG, TIFF, JPEG, Photo-CD, SUN-Raster,
640 PNM, PBM, SGI-RGB and some more) and their associated MIME types
641 with its filters.
642 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2955747"></a>MIME type Conversion Rules</h3></div></div><div></div></div><p>
645 suffix in the same directory) upon startup. These files contain
646 lines naming an input MIME type, an output MIME type, a format
647 conversion filter which can produce the output from the input type
648 and virtual costs associated with this conversion. One example line
649 reads like this:
652 application/pdf application/postscript 33 pdftops
654 </pre><p>
658 cost of this operation is 33 CUPS-$. The next filter is more
659 expensive, costing 66 CUPS-$:
662 application/vnd.hp-HPGL application/postscript 66 hpgltops
664 </pre><p>
666 plotter files to PostScript.
669 application/octet-stream
671 </pre><p>
672 Here are two more examples:
675 application/x-shell application/postscript 33 texttops
676 text/plain application/postscript 33 texttops
678 </pre><p>
681 this differentiation is needed for the syntax highlighting feature of
683 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2955864"></a>Filter Requirements</h3></div></div><div></div></div><p>
684 There are many more combinations named in mime.convs. However, you
685 are not limited to use the ones pre-defined there. You can plug in any
686 filter you like into the CUPS framework. It must meet, or must be made
687 to meet some minimal requirements. If you find (or write) a cool
688 conversion filter of some kind, make sure it complies to what CUPS
691 inside CUPS!
692 </p><div class="tip" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Tip</h3><p>
697 </p><div class="variablelist"><dl><dt><span class="term">Printer</span></dt><dd><p>The name of the printer queue (normally this is the
698 name of the filter being run)</p></dd><dt><span class="term">job</span></dt><dd><p>The numeric job ID for the job being
699 printed</p></dd><dt><span class="term">Printer</span></dt><dd><p>The string from the originating-user-name
700 attribute</p></dd><dt><span class="term">Printer</span></dt><dd><p>The string from the job-name attribute</p></dd><dt><span class="term">Printer</span></dt><dd><p>The numeric value from the number-copies
701 attribute</p></dd><dt><span class="term">Printer</span></dt><dd><p>The job options</p></dd><dt><span class="term">Printer</span></dt><dd><p>(Optionally) The print request file (if missing,
703 cases it is very easy to write a simple wrapper script around existing
704 filters to make them work with CUPS.</p></dd></dl></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2956034"></a>Prefilters</h3></div></div><div></div></div><p>
705 As was said, PostScript is the central file format to any Unix based
706 printing system. From PostScript, CUPS generates raster data to feed
707 non-PostScript printers.
708 </p><p>
709 But what is happening if you send one of the supported non-PS formats
711 generate PostScript first. There are pre-filters to create PS from
712 ASCII text, PDF, DVI or HP-GL. The outcome of these filters is always
714 any device-specific print options are not yet embedded into the
715 PostScript by CUPS, and that the next filter to be called is
716 pstops). Another pre-filter is running on all supported image formats,
720 print options already embedded into the file.
721 </p><p>
722 </p><div class="figure"><a name="id2956084"></a><p class="title"><b>Figure 19.4. Prefiltering in CUPS to form Postscript</b></p><div class="mediaobject"><img src="projdoc/imagefiles/4small.png" alt="Prefiltering in CUPS to form Postscript"></div></div><p>
723 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2956120"></a>pstops</h3></div></div><div></div></div><p>
727 above that this filter inserts all device-specific print options
728 (commands to the printer to ask for the duplexing of output, or
729 stapling an punching it, etc.) into the PostScript file.
730 </p><p>
731 </p><div class="figure"><a name="id2956149"></a><p class="title"><b>Figure 19.5. Adding Device-specific Print Options</b></p><div class="mediaobject"><img src="projdoc/imagefiles/5small.png" alt="Adding Device-specific Print Options"></div></div><p>
732 </p><p>
733 This is not all: other tasks performed by it are:
735 selecting the range of pages to be printed (if you choose to
737 ones)
738 </p></li><li><p>
739 putting 2 or more logical pages on one sheet of paper (the
741 </p></li><li><p>counting the pages of the job to insert the accounting
743 </p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2956222"></a>pstoraster</h3></div></div><div></div></div><p>
745 system. It is responsible for the first stage of the rasterization
746 process. Its input is of MIME type application/vnd.cups-postscript;
747 its output is application/vnd.cups-raster. This output format is not
748 yet meant to be printable. Its aim is to serve as a general purpose
750 that are able to generate device-specific printer data.
751 </p><p>
752 </p><div class="figure"><a name="id2956251"></a><p class="title"><b>Figure 19.6. Postscript to intermediate Raster format</b></p><div class="mediaobject"><img src="projdoc/imagefiles/6small.png" alt="Postscript to intermediate Raster format"></div></div><p>
753 </p><p>
754 CUPS raster is a generic raster format with powerful features. It is
755 able to include per-page information, color profiles and more to be
756 used by the following downstream raster drivers. Its MIME type is
757 registered with IANA and its specification is of course completely
758 open. It is designed to make it very easy and inexpensive for
759 manufacturers to develop Linux and Unix raster drivers for their
760 printer models, should they choose to do so. CUPS always takes care
761 for the first stage of rasterization so these vendors don't need to care
762 about Ghostscript complications (in fact, there is currently more
763 than one vendor financing the development of CUPS raster drivers).
764 </p><p>
765 </p><div class="figure"><a name="id2956304"></a><p class="title"><b>Figure 19.7. CUPS-raster production using Ghostscript</b></p><div class="mediaobject"><img src="projdoc/imagefiles/7small.png" alt="CUPS-raster production using Ghostscript"></div></div><p>
766 </p><p>
767 CUPS versions before version 1.1.15 were shipping a binary (or source
769 from GNU Ghostscript 5.50, and could be installed besides and in
770 addition to any GNU or AFPL Ghostscript package without conflicting.
771 </p><p>
772 From version 1.1.15, this has changed. The functions for this has been
773 integrated back into Ghostscript (now based on GNU Ghostscript version
776 parameter. If your Ghostscript doesn't show a success on asking for
778 print. Update your Ghostscript then!
779 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2956377"></a>imagetops and imagetoraster</h3></div></div><div></div></div><p>
780 Above in the section about prefilters, we mentioned the prefilter
781 that generates PostScript from image formats. The imagetoraster
782 filter is used to convert directly from image to raster, without the
783 intermediate PostScript stage. It is used more often than the above
784 mentioned prefilters. Here is a summarizing flowchart of image file
785 filtering:
786 </p><p>
787 </p><div class="figure"><a name="id2956398"></a><p class="title"><b>Figure 19.8. Image format to CUPS-raster format conversion</b></p><div class="mediaobject"><img src="projdoc/imagefiles/8small.png" alt="Image format to CUPS-raster format conversion"></div></div><p>
788 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2956434"></a>rasterto [printers specific]</h3></div></div><div></div></div><p>
789 CUPS ships with quite some different raster drivers processing CUPS
790 raster. On my system I find in /usr/lib/cups/filter/ these:
792 rastertopcl, rastertoturboprint, rastertoapdk, rastertodymo,
793 rastertoescp, rastertohp</tt></i> and
795 than this; some of these are installed by commercial add-ons to CUPS
798 development projects (such as Gimp-Print) wanting to cooperate as
799 closely as possible with CUPS.
800 </p><p>
801 </p><div class="figure"><a name="id2956484"></a><p class="title"><b>Figure 19.9. Raster to Printer Specific formats</b></p><div class="mediaobject"><img src="projdoc/imagefiles/9small.png" alt="Raster to Printer Specific formats"></div></div><p>
802 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2956519"></a>CUPS Backends</h3></div></div><div></div></div><p>
804 are special programs that send the print-ready file to the final
805 device. There is a separate backend program for any transfer
808 associated with it. The device URI is the way to encode the backend
809 used to send the job to its destination. Network device-URIs are using
810 two slashes in their syntax, local device URIs only one, as you can
811 see from the following list. Keep in mind that local interface names
812 may vary much from my examples, if your OS is not Linux:
814 This backend sends printfiles to USB-connected printers. An
815 example for the CUPS device-URI to use is:
818 This backend sends printfiles to serially connected printers.
819 An example for the CUPS device-URI to use is:
822 This backend sends printfiles to printers connected to the
823 parallel port. An example for the CUPS device-URI to use is:
826 This backend sends printfiles to printers attached to the
827 SCSI interface. An example for the CUPS device-URI to use is:
830 This backend sends printfiles to LPR/LPD connected network
831 printers. An example for the CUPS device-URI to use is:
834 This backend sends printfiles to AppSocket (a.k.a. "HP
835 JetDirect") connected network printers. An example for the CUPS
836 device-URI to use is:
839 This backend sends printfiles to IPP connected network
840 printers (or to other CUPS servers). Examples for CUPS device-URIs
841 to use are:
843 (for many HP printers) or
846 This backend sends printfiles to HTTP connected printers.
847 (The http:// CUPS backend is only a symlink to the ipp:// backend.)
848 Examples for the CUPS device-URIs to use are:
850 (for many HP printers) or
853 This backend sends printfiles to printers shared by a Windows
854 host. An example for CUPS device-URIs to use are:
856 Or
858 or
860 or
862 The smb:// backend is a symlink to the Samba utility
864 symlink is not present in your CUPS backend directory, have your
866 /usr/lib/cups/backend/smb</b>.
867 </p></dd></dl></div><p>
868 It is easy to write your own backends as Shell or Perl scripts, if you
869 need any modification or extension to the CUPS print system. One
873 fact I have the system-wide default printer set up to be connected to
875 without specifying a printer, or scripts and programs which don't name
876 a printer. The system-wide default deletes the job and sends a polite
877 mail back to the $USER asking him to always specify a correct
878 printername).
879 </p><p>
880 Not all of the mentioned backends may be present on your system or
881 usable (depending on your hardware configuration). One test for all
884 all available backends:
887 lpinfo -v
889 </pre></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2956831"></a>cupsomatic/Foomatic -- how do they fit into the Picture?</h3></div></div><div></div></div><p>
891 installations. You must be clear about the fact that these were not
893 CUPS. They utilize the traditional Ghostscript devices to render jobs
894 for CUPS. When troubleshooting, you should know about the
895 difference. Here the whole rendering process is done in one stage,
898 Printer & Driver Database at Linuxprinting.org.
899 </p><p>
900 You can recognize these PPDs from the line calling the
906 </pre><p>
907 This line you may find amongst the first 40 or so lines of the PPD
908 file. If you have such a PPD installed, the printer shows up in the
910 the driver description. cupsomatic is a Perl script that runs
911 Ghostscript, with all the complicated commandline options
912 auto-constructed from the selected PPD and commandline options give to
913 the printjob.
914 </p><p>
915 However, cupsomatic is now deprecated. Its PPDs (especially the first
916 generation of them, still in heavy use out there) are not meeting the
917 Adobe specifications. You might also suffer difficulties when you try
919 and more powerful successor is now in a very stable Beta-version
921 foomatic-rip as a filter with CUPS, you need the new-type PPDs. These
922 have a similar, but different line:
927 </pre><p>
928 The PPD generating engine at Linuxprinting.org has been revamped.
929 The new PPDs comply to the Adobe spec. On top, they also provide a
930 new way to specify different quality levels (hi-res photo, normal
931 color, grayscale, draft...) with a single click (whereas before you
932 could have required 5 or more different selections (media type,
933 resolution, inktype, dithering algorithm...). There is support for
934 custom-size media built in. There is support to switch
935 print-options from page to page, in the middle of a job. And the
936 best thing is: the new foomatic-rip now works seamlessly with all
937 legacy spoolers too (like LPRng, BSD-LPD, PDQ, PPR etc.), providing
938 for them access to use PPDs for their printing!
939 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2956944"></a>The Complete Picture</h3></div></div><div></div></div><p>
940 If you want to see an overview over all the filters and how they
941 relate to each other, the complete picture of the puzzle is at the end
942 of this document.
943 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2956960"></a><tt class="filename">mime.convs</tt></h3></div></div><div></div></div><p>
944 CUPS auto-constructs all possible filtering chain paths for any given
945 MIME type, and every printer installed. But how does it decide in
946 favor or against a specific alternative? (There may often be cases,
947 where there is a choice of two or more possible filtering chains for
948 the same target printer). Simple: you may have noticed the figures in
949 the 3rd column of the mime.convs file. They represent virtual costs
950 assigned to this filter. Every possible filtering chain will sum up to
952 </p><div class="tip" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Tip</h3><p>
955 run concurrently than will consume a total of 1000 virtual filter
956 cost. This is a very efficient way to limit the load of any CUPS
959 approximately 5 jobs maximum at a time.
960 </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2957012"></a>"Raw" printing</h3></div></div><div></div></div><p>
963 without bothering if the printer is able to digest it. Users need to
964 take care themselves that they send sensible data formats only. Raw
966 on the command line. You can also set up raw-only queues by simply not
967 associating any PPD with it. This command:
972 </pre><p>
978 </p><p>
980 if it can't find a PPD associated with the queue. However, CUPS will
981 only send known MIME types (as defined in its own mime.types file) and
982 refuse others.
983 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2957066"></a>"application/octet-stream" printing</h3></div></div><div></div></div><p>
984 Any MIME type with no rule in the
987 sent. Because CUPS refuses to print unknown MIME types per default,
988 you will probably have experienced the fact that printjobs originating
989 from Windows clients were not printed. You may have found an error
990 message in your CUPS logs like:
993 Unable to convert file 0 to printable format for job
995 </pre><p>
997 these two files:
998 </p><div class="itemizedlist"><ul type="disc"><li><p><tt class="filename">/etc/cups/mime.convs</tt></p></li><li><p><tt class="filename">/etc/cups/mime.types</tt></p></li></ul></div><p>
999 Both contain entries (at the end of the respective files) which must
1000 be uncommented to allow RAW mode operation for
1002 make sure this line is present:
1005 application/octet-stream
1007 </pre><p>
1008 This line (with no specific auto-typing rule set) makes all files
1009 not otherwise auto-typed a member of application/octet-stream. In
1011 line:
1014 application/octet-stream application/vnd.cups-raw 0 -
1016 </pre><p>
1021 always a green light to the CUPS scheduler to now hand the file over
1023 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> Editing the <tt class="filename">mime.convs</tt> and the
1028 CUPS being a more security-aware printing system than traditional ones
1029 does not by default allow one to send deliberate (possibly binary)
1030 data to printing devices. (This could be easily abused to launch a
1031 Denial of Service attack on your printer(s), causing at least the loss
1035 <span class="emphasis"><em>can</em></span> send data "raw", the MIME type for these must
1036 be one that is known to CUPS and an allowed one. The file
1038 recognizes MIME types. The file
1040 conversion filter(s) may be applied to which MIME types.
1041 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2957282"></a>PostScript Printer Descriptions (PPDs) for non-PS Printers</h3></div></div><div></div></div><p>
1042 Originally PPDs were meant to be used for PostScript printers
1043 only. Here, they help to send device-specific commands and settings
1044 to the RIP which processes the jobfile. CUPS has extended this
1045 scope for PPDs to cover non-PostScript printers too. This was not
1046 very difficult, because it is a standardized file format. In a way
1047 it was logical too: CUPS handles PostScript and uses a PostScript
1048 RIP (=Ghostscript) to process the jobfiles. The only difference is:
1049 a PostScript printer has the RIP built-in, for other types of
1050 printers the Ghostscript RIP runs on the host computer.
1051 </p><p>
1052 PPDs for a non-PS printer have a few lines that are unique to
1053 CUPS. The most important one looks similar to this:
1056 *cupsFilter: application/vnd.cups-raster 66 rastertoprinter
1058 </pre><p>
1059 It is the last piece in the CUPS filtering puzzle. This line tells the
1062 file. Therefore CUPS should auto-construct a filtering chain, which
1063 delivers as its last output the specified MIME type. This is then
1066 filter), the file should go to the backend, which sends it to the
1067 output device.
1068 </p><p>
1069 CUPS by default ships only a few generic PPDs, but they are good for
1070 several hundred printer models. You may not be able to control
1071 different paper trays, or you may get larger margins than your
1072 specific model supports):
1073 </p><div class="variablelist"><dl><dt><span class="term">deskjet.ppd</span></dt><dd><p>older HP inkjet printers and compatible
1074 </p></dd><dt><span class="term">deskjet2.ppd</span></dt><dd><p>newer HP inkjet printers and compatible
1076 </p></dd><dt><span class="term">epson9.ppd</span></dt><dd><p>Epson 24pin impact printers and compatible
1077 </p></dd><dt><span class="term">epson24.ppd</span></dt><dd><p>Epson 24pin impact printers and compatible
1078 </p></dd><dt><span class="term">okidata9.ppd</span></dt><dd><p>Okidata 9pin impact printers and compatible
1079 </p></dd><dt><span class="term">okidat24.ppd</span></dt><dd><p>Okidata 24pin impact printers and compatible
1080 </p></dd><dt><span class="term">stcolor.ppd</span></dt><dd><p>older Epson Stylus Color printers
1081 </p></dd><dt><span class="term">stcolor2.ppd</span></dt><dd><p>newer Epson Stylus Color printers
1082 </p></dd><dt><span class="term">stphoto.ppd</span></dt><dd><p>older Epson Stylus Photo printers
1083 </p></dd><dt><span class="term">stphoto2.ppd</span></dt><dd><p>newer Epson Stylus Photo printers
1084 </p></dd><dt><span class="term">laserjet.ppd</span></dt><dd><p>all PCL printers. Further below is a discussion
1085 of several other driver/PPD-packages suitable fur use with CUPS.
1086 </p></dd></dl></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2957510"></a>Difference between <span class="emphasis"><em>cupsomatic/foomatic-rip</em></span> and
1087 <span class="emphasis"><em>native CUPS</em></span> printing</h3></div></div><div></div></div><p>
1088 Native CUPS rasterization works in two steps.
1091 device from ESP Ghostscript 7.05.x as its tool
1092 </p></li><li><p>
1094 device-specific filters; there are several vendors who provide good
1095 quality filters for this step, some are Free Software, some are
1096 Shareware/Non-Free, some are proprietary.</p></li></ul></div><p>
1097 Often this produces better quality (and has several more
1098 advantages) than other methods.
1099 </p><p>
1100 </p><div class="figure"><a name="id2957561"></a><p class="title"><b>Figure 19.10. cupsomatic/foomatic processing versus Native CUPS</b></p><div class="mediaobject"><img src="projdoc/imagefiles/10small.png" alt="cupsomatic/foomatic processing versus Native CUPS"></div></div><p>
1101 </p><p>
1104 developers. It is an independent contribution to printing development,
1105 made by people from Linuxprinting.org (see also <a href="http://www.cups.org/cups-help.html" target="_top">http://www.cups.org/cups-help.html</a>).
1106 cupsomatic is no longer developed and maintained and is no longer
1107 supported. It has now been replaced by
1109 of the old cupsomatic idea, but very much improved and generalized to
1110 other (non-CUPS) spoolers. An upgrade to foomatic-rip is strongly
1111 advised, especially if you are upgrading to a recent version of CUPS
1112 too.
1113 </p><p>
1114 Both the cupsomatic (old) and the foomatic-rip (new) methods from
1115 Linuxprinting.org use the traditional Ghostscript print file
1116 processing, doing everything in a single step. It therefore relies on
1117 all the other devices built-in into Ghostscript. The quality is as
1118 good (or bad) as Ghostscript rendering is in other spoolers. The
1119 advantage is that this method supports many printer models not
1120 supported (yet) by the more modern CUPS method.
1121 </p><p>
1122 Of course, you can use both methods side by side on one system (and
1123 even for one printer, if you set up different queues), and find out
1124 which works best for you.
1125 </p><p>
1128 deviates it through the CUPS-external, system wide Ghostscript
1130 (and thus also bypasses the CUPS-raster-drivers
1132 cupsomatic hands the rendered file directly to the CUPS backend. The
1133 flowchart above illustrates the difference between native CUPS
1134 rendering and the Foomatic/cupsomatic method.
1135 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2957666"></a>Examples for filtering Chains</h3></div></div><div></div></div><p>
1136 Here are a few examples of commonly occurring filtering chains to
1137 illustrate the workings of CUPS.
1138 </p><p>
1139 Assume you want to print a PDF file to a HP JetDirect-connected
1142 </p><div class="itemizedlist"><ul type="disc"><li><p>your print options (page selection as required, 2-up,
1143 duplex) are passed to CUPS on the commandline;</p></li><li><p>the (complete) PDF file is sent to CUPS and autotyped as
1144 <span class="emphasis"><em>application/pdf</em></span>;</p></li><li><p>the file therefore first must pass the
1147 would still show all pages of the original PDF);</p></li><li><p>the file then passes the <span class="emphasis"><em>pstops</em></span>
1148 filter which applies the commandline options: it selects the pages
1151 PPD) into the new PostScript file; the file now is of PostScript MIME
1152 type
1153 <span class="emphasis"><em>application/vnd.cups-postscript</em></span>;</p></li><li><p>the file goes to the <span class="emphasis"><em>socket</em></span>
1154 backend, which transfers the job to the printers.</p></li></ul></div><p>
1155 The resulting filter chain therefore is:
1158 </pre><p>
1159 Assume your want to print the same filter to an USB-connected
1160 Epson Stylus Photo printer, installed with the CUPS
1162 are nearly the same:
1163 </p><div class="itemizedlist"><ul type="disc"><li><p>your print options (page selection as required, 2-up,
1164 duplex) are passed to CUPS on the commandline;</p></li><li><p>the (complete) PDF file is sent to CUPS and autotyped as
1165 <span class="emphasis"><em>application/pdf</em></span>;</p></li><li><p>the file therefore first must pass the
1168 would still show all pages of the original PDF);</p></li><li><p>the file then passes the "pstops" filter which applies
1172 don't support duplex printing at all -- this option will be ignored
1173 then) into the new PostScript file; the file now is of PostScript
1174 MIME type
1175 <span class="emphasis"><em>application/vnd.cups-postscript</em></span>;</p></li><li><p>the file then passes the
1177 <span class="emphasis"><em>application/cups-raster</em></span>;</p></li><li><p>finally, the <span class="emphasis"><em>rastertoepson</em></span> filter
1178 does its work (as is indicated in the printer's PPD), creating the
1179 printer-specific raster data and embedding any user-selected
1180 print-options into the print data stream;</p></li><li><p>the file goes to the <span class="emphasis"><em>usb</em></span> backend,
1181 which transfers the job to the printers.</p></li></ul></div><p>
1182 The resulting filter chain therefore is:
1185 </pre></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2957897"></a>Sources of CUPS drivers / PPDs</h3></div></div><div></div></div><p>
1186 On the internet you can find now many thousand CUPS-PPD files
1187 (with their companion filters), in many national languages,
1188 supporting more than 1000 non-PostScript models.
1189 </p><div class="itemizedlist"><ul type="disc"><li><p><a href="http://wwwl.easysw.com/printpro/" target="_top">ESP
1190 PrintPro (http://wwwl.easysw.com/printpro/)</a> (commercial,
1191 non-Free) is packaged with more than 3000 PPDs, ready for
1193 HP-UX, Sun-Solaris, SGI-IRIX, Compaq Tru64, Digital Unix and some
1194 more commercial Unices (it is written by the CUPS developers
1195 themselves and its sales help finance the further development of
1196 CUPS, as they feed their creators).</p></li><li><p>the <a href="http://gimp-print.sourceforge.net/" target="_top">Gimp-Print-Project
1197 (http://gimp-print.sourceforge.net/)</a> (GPL, Free Software)
1199 to photo quality output), to be used alongside the Gimp-Print CUPS
1201 (http://www.turboprint.com/)</a> (Shareware, non-Free) supports
1202 roughly the same amount of printers in excellent
1203 quality;</p></li><li><p><a href="http://www-124.ibm.com/developerworks/oss/linux/projects/omni/" target="_top">OMNI
1205 (LPGL, Free) is a package made by IBM, now containing support for more
1207 ported over to Linux (CUPS support is in a Beta-stage at
1209 (http://hpinkjet.sourceforge.net/)</a> (BSD-style licenses, Free)
1210 supports around 150 of HP's own printers and is also providing
1211 excellent print quality now (currently available only via the Foomatic
1212 path);</p></li><li><p><a href="http://www.linuxprinting.org/" target="_top">Foomatic/cupsomatic
1213 (http://www.linuxprinting.org/)</a> (LPGL, Free) from
1214 Linuxprinting.org are providing PPDs for practically every Ghostscript
1215 filter known to the world (including Omni, Gimp-Print and
1216 HPIJS).</p></li></ul></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
1217 The cupsomatic/Foomatic trick from Linuxprinting.org works
1218 differently from the other drivers. This is explained elsewhere in this
1219 document.
1220 </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2958024"></a>Printing with Interface Scripts</h3></div></div><div></div></div><p>
1222 System V AT&T printing systems. These are often used for PCL
1223 printers, from applications that generate PCL print jobs. Interface
1224 scripts are specific to printer models. They have a similar role as
1225 PPDs for PostScript printers. Interface scripts may inject the Escape
1226 sequences as required into the print data stream, if the user has
1227 chosen to select a certain paper tray, or print landscape, or use A3
1228 paper, etc. Interfaces scripts are practically unknown in the Linux
1229 realm. On HP-UX platforms they are more often used. You can use any
1230 working interface script on CUPS too. Just install the printer with
1236 </pre><p>
1238 with CUPS they provide the most easy way to plug in your own
1239 custom-written filtering script or program into one specific print
1240 queue (some information about the traditional usage of interface scripts is
1241 to be found at <a href="http://playground.sun.com/printing/documentation/interface.html" target="_top">http://playground.sun.com/printing/documentation/interface.html</a>).
1242 </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2958100"></a>Network printing (purely Windows)</h2></div></div><div></div></div><p>
1243 Network printing covers a lot of ground. To understand what exactly
1244 goes on with Samba when it is printing on behalf of its Windows
1246 with a Windows NT print server.
1247 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2958116"></a>From Windows Clients to an NT Print Server</h3></div></div><div></div></div><p>
1248 Windows clients printing to an NT-based print server have two
1249 options. They may
1250 </p><div class="itemizedlist"><ul type="disc"><li><p>execute the driver locally and render the GDI output
1251 (EMF) into the printer specific format on their own,
1252 or</p></li><li><p>send the GDI output (EMF) to the server, where the
1253 driver is executed to render the printer specific
1254 output.</p></li></ul></div><p>
1255 Both print paths are shown in the flowcharts below.
1256 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2958155"></a>Driver Execution on the Client</h3></div></div><div></div></div><p>
1258 meaning it shouldn't touch the jobfile and try to convert it in any
1259 way. This is what traditional Unix-based print server can do too; and
1260 at a better performance and more reliably than NT print server. This
1261 is what most Samba administrators probably are familiar with. One
1263 be used even if no driver(s) for Unix are available it is sufficient
1264 to have the Windows client drivers available and installed on the
1265 clients.
1266 </p><p>
1267 </p><div class="figure"><a name="id2958191"></a><p class="title"><b>Figure 19.11. Print Driver execution on the Client</b></p><div class="mediaobject"><img src="projdoc/imagefiles/11small.png" alt="Print Driver execution on the Client"></div></div><p>
1268 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2958227"></a>Driver Execution on the Server</h3></div></div><div></div></div><p>
1269 The other path executes the printer driver on the server. The clients
1270 transfers print files in EMF format to the server. The server uses the
1271 PostScript, PCL, ESC/P or other driver to convert the EMF file into
1272 the printer-specific language. It is not possible for Unix to do the
1273 same. Currently there is no program or method to convert a Windows
1274 client's GDI output on a Unix server into something a printer could
1275 understand.
1276 </p><p>
1277 </p><div class="figure"><a name="id2958249"></a><p class="title"><b>Figure 19.12. Print Driver execution on the Server</b></p><div class="mediaobject"><img src="projdoc/imagefiles/12small.png" alt="Print Driver execution on the Server"></div></div><p>
1278 </p><p>
1279 However, there is something similar possible with CUPS. Read on...
1280 </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2958289"></a>Network Printing (Windows clients -- UNIX/Samba Print
1281 Servers)</h2></div></div><div></div></div><p>
1283 program code on their platform, the picture is somewhat
1284 different. However, this doesn't limit your options all that
1285 much. In the contrary, you may have a way here to implement printing
1286 features which are not possible otherwise.
1287 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2958310"></a>From Windows Clients to a CUPS/Samba Print Server</h3></div></div><div></div></div><p>
1288 Here is a simple recipe showing how you can take advantage of CUPS
1289 powerful features for the benefit of your Windows network printing
1290 clients:
1291 </p><div class="itemizedlist"><ul type="disc"><li><p>Let the Windows clients send PostScript to the CUPS
1292 server.</p></li><li><p>Let the CUPS server render the PostScript into device
1293 specific raster format.</p></li></ul></div><p>
1294 This requires the clients to use a PostScript driver (even if the
1295 printer is a non-PostScript model. It also requires that you have a
1297 </p><p>
1298 Firstly, to enable CUPS based printing through Samba the
1300 section:
1301 </p><div class="itemizedlist"><ul type="disc"><li><p><i class="parameter"><tt>printing = CUPS</tt></i></p></li><li><p><i class="parameter"><tt>printcap = CUPS</tt></i></p></li></ul></div><p>
1302 When these parameters are specified, all manually set print directives
1303 (like <i class="parameter"><tt>print command =...</tt></i>, or <i class="parameter"><tt>lppause
1305 in samba itself) will be ignored. Instead, Samba will directly
1306 interface with CUPS through it's application program interface (API) -
1307 as long as Samba has been compiled with CUPS library (libcups)
1308 support. If Samba has NOT been compiled with CUPS support, and if no
1309 other print commands are set up, then printing will use the
1311 option automatically passing through (if you want your own defined
1312 print commands to work with a Samba that has CUPS support compiled in,
1314 </p><p>
1315 </p><div class="figure"><a name="id2958439"></a><p class="title"><b>Figure 19.13. Printing via CUPS/samba server</b></p><div class="mediaobject"><img src="projdoc/imagefiles/13small.png" alt="Printing via CUPS/samba server"></div></div><p>
1316 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2958474"></a>Samba receiving Jobfiles and passing them to CUPS</h3></div></div><div></div></div><p>
1322 spool space and passes it into the spool directory of CUPS (the CUPS
1325 /var/spool/cups</tt></i>). CUPS checks the access rights of its
1326 spool dir and resets it to healthy values with every re-start. We have
1327 seen quite some people who had used a common spooling space for Samba
1329 </p><p>
1330 A Windows user authenticates only to Samba (by whatever means is
1331 configured). If Samba runs on the same host as CUPS, you only need to
1333 need to make sure the Samba host gets access to printing on CUPS.
1334 </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2958550"></a>Network PostScript RIP: CUPS Filters on Server -- clients use
1335 PostScript Driver with CUPS-PPDs</h2></div></div><div></div></div><p>
1336 PPDs can control all print device options. They are usually provided
1337 by the manufacturer; if you own a PostScript printer, that is. PPD
1338 files (PostScript Printer Descriptions) are always a component of
1339 PostScript printer drivers on MS Windows or Apple Mac OS systems. They
1340 are ASCII files containing user-selectable print options, mapped to
1341 appropriate PostScript, PCL or PJL commands for the target
1342 printer. Printer driver GUI dialogs translate these options
1344 </p><p>
1345 CUPS can load, without any conversions, the PPD file from any Windows
1346 (NT is recommended) PostScript driver and handle the options. There is
1347 a web browser interface to the print options (select <a href="http://localhost:631/printers/" target="_top">http://localhost:631/printers/</a>
1350 or see if you have lphelp on your system). There are also some
1351 different GUI frontends on Linux/UNIX, which can present PPD options
1352 to users. PPD options are normally meant to be evaluated by the
1353 PostScript RIP on the real PostScript printer.
1354 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2958605"></a>PPDs for non-PS Printers on UNIX</h3></div></div><div></div></div><p>
1356 of PPDs. The CUPS developers have extended the scope of the PPD
1357 concept, to also describe available device and driver options for
1358 non-PostScript printers through CUPS-PPDs.
1359 </p><p>
1360 This is logical, as CUPS includes a fully featured PostScript
1361 interpreter (RIP). This RIP is based on Ghostscript. It can process
1362 all received PostScript (and additionally many other file formats)
1363 from clients. All CUPS-PPDs geared to non-PostScript printers contain
1364 an additional line, starting with the keyword
1366 system which printer-specific filter to use for the interpretation of
1367 the supplied PostScript. Thus CUPS lets all its printers appear as
1368 PostScript devices to its clients, because it can act as a PostScript
1369 RIP for those printers, processing the received PostScript code into a
1370 proper raster print format.
1371 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2958646"></a>PPDs for non-PS Printers on Windows</h3></div></div><div></div></div><p>
1372 CUPS-PPDs can also be used on Windows-Clients, on top of a
1375 limitations). This feature enables CUPS to do a few tricks no other
1376 spooler can do:
1377 </p><div class="itemizedlist"><ul type="disc"><li><p>act as a networked PostScript RIP (Raster Image
1378 Processor), handling printfiles from all client platforms in a uniform
1379 way;</p></li><li><p>act as a central accounting and billing server, since
1380 all files are passed through the pstops filter and are therefore
1382 <span class="emphasis"><em>NOTE:</em></span> this can not happen with "raw" print jobs,
1383 which always remain unfiltered per definition;</p></li><li><p>enable clients to consolidate on a single PostScript
1384 driver, even for many different target printers.</p></li></ul></div><p>
1385 Using CUPS PPDs on Windows clients enables these to control
1386 all print job settings just as a UNIX client can do too.
1387 </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2958712"></a>Windows Terminal Servers (WTS) as CUPS Clients</h2></div></div><div></div></div><p>
1388 This setup may be of special interest to people experiencing major
1389 problems in WTS environments. WTS need often a multitude of
1390 non-PostScript drivers installed to run their clients' variety of
1391 different printer models. This often imposes the price of much
1392 increased instability.
1393 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2958729"></a>Printer Drivers running in "Kernel Mode" cause many
1394 Problems</h3></div></div><div></div></div><p>
1395 The reason is that in Win NT printer drivers run in "Kernel
1396 Mode", this introduces a high risk for the stability of the system
1397 if the driver is not really stable and well-tested. And there are a
1398 lot of bad drivers out there! Especially notorious is the example
1399 of the PCL printer driver that had an additional sound module
1400 running, to notify users via soundcard of their finished jobs. Do I
1401 need to say that this one was also reliably causing "Blue Screens
1402 of Death" on a regular basis?
1403 </p><p>
1404 PostScript drivers generally are very well tested. They are not known
1405 to cause any problems, even though they run in Kernel Mode too. This
1406 might be because there have so far only been 2 different PostScript
1407 drivers the ones from Adobe and the one from Microsoft. Both are
1408 very well tested and are as stable as you ever can imagine on
1409 Windows. The CUPS driver is derived from the Microsoft one.
1410 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2958763"></a>Workarounds impose Heavy Limitations</h3></div></div><div></div></div><p>
1411 In many cases, in an attempt to work around this problem, site
1412 administrators have resorted to restrict the allowed drivers installed
1413 on their WTS to one generic PCL- and one PostScript driver. This
1414 however restricts the clients in the amount of printer options
1415 available for them; often they can't get out more than simplex
1416 prints from one standard paper tray, while their devices could do much
1417 better, if driven by a different driver! )
1418 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2958784"></a>CUPS: a "Magical Stone"?</h3></div></div><div></div></div><p>
1419 Using a PostScript driver, enabled with a CUPS-PPD, seems to be a very
1420 elegant way to overcome all these shortcomings. There are, depending
1421 on the version of Windows OS you use, up to 3 different PostScript
1422 drivers available: Adobe, Microsoft and CUPS PostScript drivers. None
1423 of them is known to cause major stability problems on WTS (even if
1424 used with many different PPDs). The clients will be able to (again)
1425 chose paper trays, duplex printing and other settings. However, there
1426 is a certain price for this too: a CUPS server acting as a PostScript
1427 RIP for its clients requires more CPU and RAM than when just acting as
1429 although the first feedbacks look very promising.
1430 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2958811"></a>PostScript Drivers with no major problems -- even in Kernel
1431 Mode</h3></div></div><div></div></div><p>
1432 More recent printer drivers on W2K and XP don't run in Kernel mode
1433 (unlike Win NT) any more. However, both operating systems can still
1434 use the NT drivers, running in Kernel mode (you can roughly tell which
1435 is which as the drivers in subdirectory "2" of "W32X86" are "old"
1436 ones). As was said before, the Adobe as well as the Microsoft
1437 PostScript drivers are not known to cause any stability problems. The
1438 CUPS driver is derived from the Microsoft one. There is a simple
1439 reason for this: The MS DDK (Device Development Kit) for Win NT (which
1440 used to be available at no cost to licensees of Visual Studio)
1441 includes the source code of the Microsoft driver, and licensees of
1442 Visual Studio are allowed to use and modify it for their own driver
1443 development efforts. This is what the CUPS people have done. The
1444 license doesn't allow them to publish the whole of the source code.
1447 </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2958865"></a> Setting up CUPS for driver Download</h2></div></div><div></div></div><p>
1448 As we have said before: all previously known methods to prepare client
1450 convenience of Windows workstations are working with CUPS too. These
1451 methods were described in the previous chapter. In reality, this is a
1452 pure Samba business, and only relates to the Samba/Win client
1453 relationship.
1454 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2958884"></a><span class="emphasis"><em>cupsaddsmb</em></span>: the unknown Utility</h3></div></div><div></div></div><p>
1455 The cupsaddsmb utility (shipped with all current CUPS versions) is an
1456 alternative method to transfer printer drivers into the Samba
1458 clients expect drivers deposited and setup for download and
1459 installation. It makes the sharing of any (or all) installed CUPS
1460 printers very easy. cupsaddsmb can use the Adobe PostScript driver as
1465 named in its man page.
1466 </p><p>
1467 The CUPS printer driver is available from the CUPS download site. Its
1469 is preferred over the Adobe drivers since it has a number of
1470 advantages:
1472 accounting;</p></li><li><p>it supports banner pages, and page labels on all
1473 printers;</p></li><li><p>it supports the setting of a number of job IPP
1474 attributes (such as job-priority, page-label and
1475 job-billing)</p></li></ul></div><p>
1476 However, currently only Windows NT, 2000, and XP are supported by the
1477 CUPS drivers. You will need to get the respective part of Adobe driver
1479 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2958976"></a>Prepare your <tt class="filename">smb.conf</tt> for
1480 cupsaddsmb</h3></div></div><div></div></div><p>
1481 Prior to running cupsaddsmb, you need the following settings in
1485 [global]
1486 load printers = yes
1487 printing = cups
1488 printcap name = cups
1490 [printers]
1491 comment = All Printers
1492 path = /var/spool/samba
1493 browseable = no
1494 public = yes
1495 guest ok = yes # setting depends on your requirements
1496 writable = no
1497 printable = yes
1498 printer admin = root
1500 [print$]
1501 comment = Printer Drivers
1502 path = /etc/samba/drivers
1503 browseable = yes
1504 guest ok = no
1505 read only = yes
1506 write list = root
1508 </pre></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2959022"></a>CUPS Package of "PostScript Driver for WinNT/2k/XP"</h3></div></div><div></div></div><p>
1509 CUPS users may get the exactly same packages from<a href="http://www.cups.org/software.html" target="_top"><span class="emphasis"><em>http://www.cups.org/software.html</em></span></a>.
1510 It is a separate package from the CUPS base software files, tagged as
1514 it will reveal these files:
1517 # tar xvzf cups-samba-1.1.19.tar.gz
1519 cups-samba.install
1520 cups-samba.license
1521 cups-samba.readme
1522 cups-samba.remove
1523 cups-samba.ss
1525 </pre><p>
1526 These have been packaged with the ESP meta packager software
1531 too). Then it puts the content into
1533 files:
1536 # tar tv cups-samba.ss
1538 cupsdrvr.dll
1539 cupsui.dll
1540 cups.hlp
1542 </pre><p>
1544 handle:
1547 # ./cups-samba.install
1549 [....]
1550 Installing software...
1551 Updating file permissions...
1552 Running post-install commands...
1553 Installation is complete.
1555 </pre><p>
1556 The script should automatically put the driver files into the
1558 </p><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p>
1559 Due to a bug, one recent CUPS release puts the
1563 copy/move the file (after running the
1565 right place.
1568 cp /usr/share/drivers/cups.hlp /usr/share/cups/drivers/
1570 </pre><p>
1571 This new CUPS PostScript driver is currently binary-only, but free of
1572 charge. No complete source code is provided (yet). The reason is this:
1574 Developer Kit</em></span> (DDK) and compiled with Microsoft Visual
1575 Studio 6. Driver developers are not allowed to distribute the whole of
1576 the source code as Free Software. However, CUPS developers released
1578 Visual Studio and a DDK will be able to compile for him/herself.
1579 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2959220"></a>Recognize the different Driver Files</h3></div></div><div></div></div><p>
1581 the Windows NT/2000/XP client:
1584 [Windows NT, 2000, and XP are supported by:]
1585 cups.hlp
1586 cupsdrvr.dll
1587 cupsui.dll
1589 </pre><p>
1591 the Windows NT/2000/XP clients. The set of files is different for the
1592 different platforms.
1596 ADFONTS.MFM
1597 ADOBEPS4.DRV
1598 ADOBEPS4.HLP
1599 DEFPRTR2.PPD
1600 ICONLIB.DLL
1601 PSMON.DLL
1603 [Windows NT, 2000, and XP are supported by:]
1604 ADOBEPS5.DLL
1605 ADOBEPSU.DLL
1606 ADOBEPSU.HLP
1608 </pre><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
1609 If both, the Adobe driver files and the CUPS driver files for the
1610 support of WinNT/2k/XP are present in , the Adobe ones will be ignored
1611 and the CUPS ones will be used. If you prefer -- for whatever reason
1612 -- to use Adobe-only drivers, move away the 3 CUPS driver files. The
1613 Win95/98/ME clients use the Adobe drivers in any case.
1614 </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2959278"></a>Acquiring the Adobe Driver Files</h3></div></div><div></div></div><p>
1615 Acquiring the Adobe driver files seems to be unexpectedly difficult
1616 for many users. They are not available on the Adobe website as single
1617 files and the self-extracting and/or self-installing Windows-exe is
1618 not easy to locate either. Probably you need to use the included
1619 native installer and run the installation process on one client
1620 once. This will install the drivers (and one Generic PostScript
1621 printer) locally on the client. When they are installed, share the
1622 Generic PostScript printer. After this, the client's
1624 where you can get them with smbclient from the CUPS host. A more
1625 detailed description about this is in the next (the CUPS printing)
1626 chapter.
1627 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2959310"></a>ESP Print Pro Package of "PostScript Driver for
1629 Users of the ESP Print Pro software are able to install their "Samba
1630 Drivers" package for this purpose with no problem. Retrieve the driver
1631 files from the normal download area of the ESP Print Pro software
1632 at<a href="http://www.easysw.com/software.html" target="_top">http://www.easysw.com/software.html</a>.
1635 area and download the package. Once installed, you can prepare any
1636 driver by simply highlighting the printer in the Printer Manager GUI
1638 course you need to have prepared Samba beforehand too to handle the
1640 share, etc. The ESP Print Pro package includes the CUPS driver files
1642 client family.
1643 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2959360"></a>Caveats to be considered</h3></div></div><div></div></div><p>
1644 Once you have run the install script (and possibly manually
1647 ready to be put into Samba's <i class="parameter"><tt>[print$]</tt></i> share (which often maps to
1652 CUPS since release 1.1.16).
1653 </p><div class="tip" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Tip</h3><p>
1654 You may need to put root into the smbpasswd file by running
1656 should run this whole procedure for the first time, and are not
1657 working in an environment where everything is configured for
1659 </p></div><p>
1661 and are initialized, they are ready to be downloaded and installed by
1662 the Win NT/2k/XP clients.
1663 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
1665 Win 9x/ME clients won't work with the CUPS PostScript driver. For
1667 drivers as previously.
1668 </p></li><li><p>
1669 It is not harmful if you still have the
1674 </p></li><li><p>
1676 files for the Adobe PostScript driver installed, the download and
1677 installation of the new CUPS PostScript driver for Windows NT/2k/XP
1678 will fail at first. You need to wipe the old driver from the clients
1680 will still be kept by the clients and re-used if you try to re-install
1681 the printer. To really get rid of the Adobe driver files on the
1685 Properties</em></span>. When the new dialog opens, select the
1688 button. This will only work if there is not one single printer left
1691 Administrator privileges to do this.
1692 </p></li><li><p>
1693 Once you have successfully downloaded the CUPS PostScript driver to a
1694 client, you can easily switch all printers to this one by proceeding
1699 </p></li></ol></div><p>
1700 </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2959582"></a>What are the Benefits of using the "CUPS PostScript Driver for
1702 You are interested in a comparison between the CUPS and the Adobe
1703 PostScript drivers? For our purposes these are the most important
1704 items which weigh in favor of the CUPS ones:
1705 </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
1706 get the ADOBE*.* driver files from?</span>”</p></li><li><p>the Adobe drivers (on request of the printer PPD
1707 associated with them) often put a PJL header in front of the main
1708 PostScript part of the print file. Thus the printfile starts with
1712 CUPS daemon auto-typing the incoming file as a print-ready file,
1714 technically, it is not regarded as the generic MIME type
1716 the more special MIME type
1718 which therefore also leads to the page accounting in
1720 receiving the exact number of pages; instead the dummy page number
1721 of "1" is logged in a standard setup)</p></li><li><p>the Adobe driver has more options to "mis-configure" the
1722 PostScript generated by it (like setting it inadvertently to
1725 could lead to CUPS being unable to process it)</p></li><li><p>the CUPS PostScript driver output sent by Windows
1726 clients to the CUPS server will be guaranteed to be auto-typed always
1730 accounting and quota purposes</p></li><li><p>the CUPS PostScript driver supports the sending of
1731 additional standard (IPP) print options by Win NT/2k/XP clients. Such
1732 additional print options are: naming the CUPS standard
1734 installed at the time of driver download), using the CUPS
1736 <span class="emphasis"><em>job-priority</em></span> and setting the <span class="emphasis"><em>scheduled
1737 time of printing</em></span> (with the option to support additional
1738 useful IPP job attributes in the future).</p></li><li><p>the CUPS PostScript driver supports the inclusion of
1740 beginning of the PostScript file (which could be used in the future
1741 for all sort of beneficial extensions on the CUPS side, but which will
1742 not disturb any other applications as they will regard it as a comment
1743 and simply ignore it).</p></li><li><p>the CUPS PostScript driver will be the heart of the
1744 fully fledged CUPS IPP client for Windows NT/2K/XP to be released soon
1745 (probably alongside the first Beta release for CUPS
1746 1.2).</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2959764"></a>Run "cupsaddsmb" (quiet Mode)</h3></div></div><div></div></div><p>
1747 The cupsaddsmb command copies the needed files into your
1749 associated with this printer is copied from
1752 Windows client installations via Point'n'Print. Before we can run the
1753 command successfully, we need to be sure that we can authenticate
1754 towards Samba. If you have a small network you are probably using user
1756 root has already a Samba account. Otherwise, create it now, using
1760 # smbpasswd -a root
1761 New SMB password: [type in password 'secret']
1762 Retype new SMB password: [type in password 'secret']
1764 </pre><p>
1765 Here is an example of a successfully run cupsaddsmb command.
1768 # cupsaddsmb -U root infotec_IS2027
1769 Password for root required to access localhost via SAMBA: [type in password 'secret']
1771 </pre><p>
1775 obvious that it only works for queues with a CUPS driver associated.
1776 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2959865"></a>Run "cupsaddsmb" with verbose Output</h3></div></div><div></div></div><p>
1777 Probably you want to see what's going on. Use the
1780 a line indicate that I inserted an artificial line break plus some
1781 indentation here:
1782 </p><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p>
1783 You will see the root password for the Samba account printed on
1784 screen. If you use remote access, the password will go over the wire
1785 unencrypted!
1788 # cupsaddsmb -U root -v infotec_2105
1789 Password for root required to access localhost via SAMBA:
1790 Running command: smbclient //localhost/print\$ -N -U'root%secret' -c 'mkdir W32X86;put \
1791 /var/spool/cups/tmp/3e98bf2d333b5 W32X86/infotec_2105.ppd;put \
1792 /usr/share/cups/drivers/cupsdrvr.dll W32X86/cupsdrvr.dll;put \
1793 /usr/share/cups/drivers/cupsui.dll W32X86/cupsui.dll;put \
1794 /usr/share/cups/drivers/cups.hlp W32X86/cups.hlp'
1796 Domain=[CUPS-PRINT] OS=[Unix] Server=[Samba 2.2.7a]
1797 NT_STATUS_OBJECT_NAME_COLLISION making remote directory \W32X86
1799 (average 2328.8 kb/s)
1800 putting file /usr/share/cups/drivers/cupsdrvr.dll as \W32X86/cupsdrvr.dll (9374.3 kb/s) \
1801 (average 5206.6 kb/s)
1802 putting file /usr/share/cups/drivers/cupsui.dll as \W32X86/cupsui.dll (8107.2 kb/s) \
1803 (average 5984.1 kb/s)
1804 putting file /usr/share/cups/drivers/cups.hlp as \W32X86/cups.hlp (3475.0 kb/s) \
1805 (average 5884.7 kb/s)
1807 Running command: rpcclient localhost -N -U'root%secret' -c 'adddriver "Windows NT x86" \
1808 "infotec_2105:cupsdrvr.dll:infotec_2105.ppd:cupsui.dll:cups.hlp:NULL: \
1809 RAW:NULL"'
1810 cmd = adddriver "Windows NT x86" "infotec_2105:cupsdrvr.dll:infotec_2105.ppd:cupsui.dll: \
1811 cups.hlp:NULL:RAW:NULL"
1812 Printer Driver infotec_2105 successfully installed.
1814 Running command: smbclient //localhost/print\$ -N -U'root%secret' -c 'mkdir WIN40;put \
1815 /var/spool/cups/tmp/3e98bf2d333b5 WIN40/infotec_2105.PPD; put \
1816 /usr/share/cups/drivers/ADFONTS.MFM WIN40/ADFONTS.MFM;put \
1817 /usr/share/cups/drivers/ADOBEPS4.DRV WIN40/ADOBEPS4.DRV;put \
1818 /usr/share/cups/drivers/ADOBEPS4.HLP WIN40/ADOBEPS4.HLP;put \
1819 /usr/share/cups/drivers/DEFPRTR2.PPD WIN40/DEFPRTR2.PPD;put \
1820 /usr/share/cups/drivers/ICONLIB.DLL
1821 WIN40/ICONLIB.DLL;put /usr/share/cups/drivers/PSMON.DLL WIN40/PSMON.DLL;'
1823 Domain=[CUPS-PRINT] OS=[Unix] Server=[Samba 2.2.7a]
1824 NT_STATUS_OBJECT_NAME_COLLISION making remote directory \WIN40
1826 (average 2328.8 kb/s)
1827 putting file /usr/share/cups/drivers/ADFONTS.MFM as \WIN40/ADFONTS.MFM (9368.0 kb/s) \
1828 (average 6469.6 kb/s)
1829 putting file /usr/share/cups/drivers/ADOBEPS4.DRV as \WIN40/ADOBEPS4.DRV (9958.2 kb/s) \
1830 (average 8404.3 kb/s)
1831 putting file /usr/share/cups/drivers/ADOBEPS4.HLP as \WIN40/ADOBEPS4.HLP (8341.5 kb/s) \
1832 (average 8398.6 kb/s)
1833 putting file /usr/share/cups/drivers/DEFPRTR2.PPD as \WIN40/DEFPRTR2.PPD (2195.9 kb/s) \
1834 (average 8254.3 kb/s)
1835 putting file /usr/share/cups/drivers/ICONLIB.DLL as \WIN40/ICONLIB.DLL (8239.9 kb/s) \
1836 (average 8253.6 kb/s)
1837 putting file /usr/share/cups/drivers/PSMON.DLL as \WIN40/PSMON.DLL (6222.2 kb/s) \
1838 (average 8188.5 kb/s)
1840 Running command: rpcclient localhost -N -U'root%secret' -c 'adddriver "Windows 4.0" \
1841 "infotec_2105:ADOBEPS4.DRV:infotec_2105.PPD:NULL:ADOBEPS4.HLP: \
1842 PSMON.DLL:RAW:ADOBEPS4.DRV,infotec_2105.PPD,ADOBEPS4.HLP,PSMON.DLL, \
1843 ADFONTS.MFM,DEFPRTR2.PPD,ICONLIB.DLL"'
1844 cmd = adddriver "Windows 4.0" "infotec_2105:ADOBEPS4.DRV:infotec_2105.PPD:NULL: \
1845 ADOBEPS4.HLP:PSMON.DLL:RAW:ADOBEPS4.DRV,infotec_2105.PPD,ADOBEPS4.HLP, \
1846 PSMON.DLL,ADFONTS.MFM,DEFPRTR2.PPD,ICONLIB.DLL"
1847 Printer Driver infotec_2105 successfully installed.
1849 Running command: rpcclient localhost -N -U'root%secret' \
1850 -c 'setdriver infotec_2105 infotec_2105'
1851 cmd = setdriver infotec_2105 infotec_2105
1852 Successfully set infotec_2105 to driver infotec_2105.
1854 </pre><p>
1855 If you look closely, you'll discover your root password was transfered
1856 unencrypted over the wire, so beware! Also, if you look further her,
1857 you'll discover error messages like NT_STATUS_OBJECT_NAME_COLLISION in
1858 between. They occur, because the directories WIN40 and W32X86 already
1860 (from a previous driver installation). They are harmless here.
1861 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2960092"></a>Understanding cupsaddsmb</h3></div></div><div></div></div><p>
1862 What has happened? What did cupsaddsmb do? There are five stages of
1863 the procedure
1865 driver files and the PPD file for the named printer;</p></li><li><p>store the files temporarily in the local
1866 TEMPDIR (as defined in
1867 <tt class="filename">cupsd.conf</tt>);</p></li><li><p>connect via smbclient to the Samba server's
1870 directories;</p></li><li><p>connect via rpcclient to the Samba server and
1872 parameters;</p></li><li><p>connect via rpcclient to the Samba server a second
1874 Note, that you can run the cupsaddsmb utility with parameters to
1875 specify one remote host as Samba host and a second remote host as CUPS
1876 host. Especially if you want to get a deeper understanding, it is a
1877 good idea try it and see more clearly what is going on (though in real
1878 life most people will have their CUPS and Samba servers run on the
1879 same host):
1882 # cupsaddsmb -H sambaserver -h cupsserver -v printername
1884 </pre></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2960186"></a>How to recognize if cupsaddsm completed successfully</h3></div></div><div></div></div><p>
1886 successfully in all fields. You need as a minimum these 3 messages
1887 amongst the output:
1888 </p><div class="orderedlist"><ol type="1"><li><p><span class="emphasis"><em>Printer Driver infotec_2105 successfully
1890 architecture...)</p></li><li><p><span class="emphasis"><em>Printer Driver infotec_2105 successfully
1891 installed.</em></span> # (for the WIN40 == Win9x/ME
1892 architecture...)</p></li><li><p><span class="emphasis"><em>Successfully set [printerXPZ] to driver
1893 [printerXYZ].</em></span></p></li></ol></div><p>
1894 These messages probably not easily recognized in the general
1897 printer drivers for download), you might miss if individual printers
1898 drivers had problems to install properly. Here a redirection of the
1899 output will help you analyze the results in retrospective.
1900 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
1901 It is impossible to see any diagnostic output if you don't run
1902 cupsaddsmb in verbose mode. Therefore we strongly recommend to not
1903 use the default quiet mode. It will hide any problems from you which
1904 might occur.
1905 </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2960273"></a>cupsaddsmb with a Samba PDC</h3></div></div><div></div></div><p>
1906 You can't get the standard cupsaddsmb command to run on a Samba PDC?
1907 You are asked for the password credential all over again and again and
1908 the command just will not take off at all? Try one of these
1909 variations:
1912 # cupsaddsmb -U DOMAINNAME\\root -v printername
1913 # cupsaddsmb -H SAMBA-PDC -U DOMAINNAME\\root -v printername
1914 # cupsaddsmb -H SAMBA-PDC -U DOMAINNAME\\root -h cups-server -v printername
1916 </pre><p>
1917 (Note the two backslashes: the first one is required to
1919 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2960308"></a>cupsaddsmb Flowchart</h3></div></div><div></div></div><p>
1920 Here is a chart about the procedures, commandflows and
1923 </p><p>
1924 </p><div class="figure"><a name="id2960326"></a><p class="title"><b>Figure 19.14. cupsaddsmb flowchart</b></p><div class="mediaobject"><img src="projdoc/imagefiles/1small.png" alt="cupsaddsmb flowchart"></div></div><p>
1925 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2960361"></a>Installing the PostScript Driver on a Client</h3></div></div><div></div></div><p>
1926 After cupsaddsmb completed, your driver is prepared for the clients to
1927 use. Here are the steps you must perform to download and install it
1929 server;
1930 </p><div class="itemizedlist"><ul type="disc"><li><p>open the <span class="emphasis"><em>Printers</em></span>
1931 share of Samba in Network Neighbourhood;</p></li><li><p>right-click on the printer in
1932 question;</p></li><li><p>from the opening context-menu select
1935 use).</p></li></ul></div><p>
1936 After a few seconds, there should be a new printer in your
1940 kde-bitshop"). If you want to test it and send your first job from
1941 an application like Winword, the new printer will appears in a
1943 dropdown list of available printers.
1944 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
1945 cupsaddsmb will only reliably work with CUPS version 1.1.15 or higher
1946 and Samba from 2.2.4. If it doesn't work, or if the automatic printer
1947 driver download to the clients doesn't succeed, you can still manually
1948 install the CUPS printer PPD on top of the Adobe PostScript driver on
1949 clients. Then point the client's printer queue to the Samba printer
1950 share for a UNC type of connection:
1953 net use lpt1: \\sambaserver\printershare /user:ntadmin
1955 </pre><p>
1956 should you desire to use the CUPS networked PostScript RIP
1958 with the required privileges to access the printershare) This would
1959 set up the printer connection in the traditional
1961 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2960474"></a>Avoiding critical PostScript Driver Settings on the
1962 Client</h3></div></div><div></div></div><p>
1963 Soooo: printing works, but there are still problems. Most jobs print
1964 well, some don't print at all. Some jobs have problems with fonts,
1965 which don't look very good. Some jobs print fast, and some are
1966 dead-slow. Many of these problems can be greatly reduced or even
1967 completely eliminated if you follow a few guidelines. Remember, if
1968 your print device is not PostScript-enabled, you are treating your
1969 Ghostscript installation on your CUPS host with the output your client
1970 driver settings produce. Treat it well:
1971 </p><div class="itemizedlist"><ul type="disc"><li><p>Avoid the <span class="emphasis"><em>PostScript Output Option: Optimize
1973 Portability</em></span> instead (Adobe PostScript
1976 YES</em></span> (CUPS PostScript Driver)</p></li><li><p>Recommended is the <span class="emphasis"><em>True Type Font
1977 Downloading Option: Native True Type</em></span> over
1978 <span class="emphasis"><em>Automatic</em></span> and <span class="emphasis"><em>Outline</em></span>; you
1980 PostScript Driver)</p></li><li><p>Choose <span class="emphasis"><em>True Type Font: Download as Softfont
1982 Font</em></span> (for exotic fonts you may need to change it back to
1983 get a printout at all) (Adobe)</p></li><li><p>Sometimes you can choose <span class="emphasis"><em>PostScript Language
1986 handles Level 3 PostScript very well) (Adobe).</p></li><li><p>Say <span class="emphasis"><em>Yes</em></span> to <span class="emphasis"><em>PostScript
1987 Error Handler</em></span> (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="id2960608"></a>Installing PostScript Driver Files manually (using
1988 rpcclient)</h2></div></div><div></div></div><p>
1989 Of course you can run all the commands which are embedded into the
1990 cupsaddsmb convenience utility yourself, one by one, and hereby upload
1991 and prepare the driver files for future client downloads.
1992 </p><div class="orderedlist"><ol type="1"><li><p>prepare Samba (a CUPS printqueue with the name of the
1993 printer should be there. We are providing the driver
1994 now);</p></li><li><p>copy all files to
1995 <i class="parameter"><tt>[print$]:</tt></i></p></li><li><p>run <b class="command">rpcclient adddriver</b>
1996 (for each client architecture you want to support):</p></li><li><p>run <b class="command">rpcclient
1997 setdriver.</b></p></li></ol></div><p>
1999 to get a first idea. Look at all the printing related
2003 the most interesting ones. rpcclient implements an important part of
2004 the MS-RPC protocol. You can use it to query (and command) a Win NT
2005 (or 2K/XP) PC too. MS-RPC is used by Windows clients, amongst other
2007 mimic this too.
2008 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2960723"></a>A Check of the rpcclient man Page</h3></div></div><div></div></div><p>
2009 First let's have a little check of the rpcclient man page. Here are
2010 two relevant passages:
2011 </p><p>
2013 AddPrinterDriver() RPC to install the printer driver information on
2014 the server. Note that the driver files should already exist in the
2020 Long Printer Name:\
2021 Driver File Name:\
2022 Data File Name:\
2023 Config File Name:\
2024 Help File Name:\
2025 Language Monitor Name:\
2026 Default Data Type:\
2027 Comma Separated list of Files
2028 </pre><p>Any empty fields should be enter as the string "NULL". </p><p>Samba does not need to support the concept of Print Monitors
2029 since these only apply to local printers whose driver can make use of
2031 On a remote NT print server, the Print Monitor for a driver must
2032 already be installed prior to adding the driver or else the RPC will
2033 fail
2034 </p><p>
2037 printer driver associated with an installed printer. The printer
2038 driver must already be correctly installed on the print server.
2039 </p><p> See also the enumprinters and enumdrivers commands for
2040 obtaining a list of installed printers and drivers.
2041 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2960836"></a>Understanding the rpcclient man Page</h3></div></div><div></div></div><p>
2043 page, since you have to deal with some parameters containing
2044 spaces. Here is a better description for it. We have line-broken the
2046 command in one line without the linebreaks:
2050 "LongPrinterName:DriverFile:DataFile:ConfigFile:HelpFile:\
2051 LanguageMonitorFile:DataType:ListOfFiles,Comma-separated"
2053 </pre><p>
2055 keyword, does in reality consist of 8 colon-separated fields. The
2056 last field may take multiple (in some, very insane, cases, even
2057 20 different additional files. This might sound confusing at first.
2060 anything you want, as long as you use this name later in the
2062 practical reasons, many name the driver the same as the
2063 printer.
2064 </p><p>
2065 True: it isn't simple at all. I hear you asking:
2067 File", "Data File", "Config File", "Help File" and "Language
2069 want to have a look at how a Windows NT box with a shared printer
2070 presents the files to us. Remember, that this whole procedure has
2071 to be developed by the Samba Team by overhearing the traffic caused
2072 by Windows computers on the wire. We may as well turn to a Windows
2073 box now, and access it from a UNIX workstation. We will query it
2075 try to understand the man page more clearly which we've read just
2076 now.
2077 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2960925"></a>Producing an Example by querying a Windows Box</h3></div></div><div></div></div><p>
2080 subcommand (in level 3 verbosity) against it. Just sit down at UNIX or
2081 Linux workstation with the Samba utilities installed. Then type the
2082 following command:
2085 rpcclient -U'USERNAME%PASSWORD' NT-SERVER-NAME -c 'getdriver printername 3'
2087 </pre><p>
2088 From the result it should become clear which is which. Here is an
2089 example from my installation:
2092 # rpcclient -U'Danka%xxxx' W2KSERVER -c'getdriver "DANKA InfoStream Virtual Printer" 3'
2095 [Windows NT x86]
2096 Printer Driver Info 3:
2097 Version: [2]
2098 Driver Name: [DANKA InfoStream]
2099 Architecture: [Windows NT x86]
2100 Driver Path: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\PSCRIPT.DLL]
2101 Datafile: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\INFOSTRM.PPD]
2102 Configfile: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\PSCRPTUI.DLL]
2103 Helpfile: [C:\WINNT\System32\spool\DRIVERS\W32X86\2\PSCRIPT.HLP]
2105 Dependentfiles: []
2106 Dependentfiles: []
2107 Dependentfiles: []
2108 Dependentfiles: []
2109 Dependentfiles: []
2110 Dependentfiles: []
2111 Dependentfiles: []
2113 Monitorname: []
2114 Defaultdatatype: []
2116 </pre><p>
2117 Some printer drivers list additional files under the label
2120 PostScript drivers we don't need any (nor would we for the Adobe
2122 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2961015"></a>What is required for adddriver and setdriver to succeed</h3></div></div><div></div></div><p>
2123 From the manpage (and from the quoted output
2125 need to have certain conditions in order to make the manual uploading
2126 and initializing of the driver files succeed. The two rpcclient
2129 pre-conditions to complete successfully:
2130 </p><div class="itemizedlist"><ul type="disc"><li><p>you are connected as "printer admin", or root (note,
2131 that this is <span class="emphasis"><em>not</em></span> the "Printer Operators" group in
2144 subdirectories;</p></li><li><p>the printer you are going to setup for the Windows
2145 clients, needs to be installed in CUPS already;</p></li><li><p>the CUPS printer must be known to Samba, otherwise the
2147 NT_STATUS_UNSUCCESSFUL error. To check if the printer is known by
2149 rpcclient. A long-standing bug prevented a proper update of the
2150 printer list until every smbd process had received a SIGHUP or was
2151 restarted. Remember this in case you've created the CUPS printer just
2152 shortly ago and encounter problems: try restarting
2153 Samba.</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2961177"></a>Manual Commandline Driver Installation in 15 little Steps</h3></div></div><div></div></div><p>
2154 We are going to install a printer driver now by manually executing all
2155 required commands. As this may seem a rather complicated process at
2156 first, we go through the procedure step by step, explaining every
2157 single action item as it comes up.
2158 </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2961194"></a>First Step: Install the Printer on CUPS</h4></div></div><div></div></div><pre class="screen">
2162 </pre><p>
2164 to the CUPS system. The printer is accessed via a socket
2165 (a.k.a. JetDirect or Direct TCP/IP) connection. You need to be root
2166 for this step
2167 </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2961224"></a>Second Step (optional): Check if the Printer is recognized by
2170 # rpcclient -Uroot%xxxx -c 'enumprinters' localhost | grep -C2 mysmbtstprn
2172 flags:[0x800000]
2173 name:[\\kde-bitshop\mysmbtstprn]
2174 description:[\\kde-bitshop\mysmbtstprn,,mysmbtstprn]
2175 comment:[mysmbtstprn]
2177 </pre><p>
2178 This should show the printer in the list. If not, stop and re-start
2180 `pidof smbd`</b>. Check again. Troubleshoot and repeat until
2183 already. You need to know root's Samba password (as set by the
2185 following steps. Alternatively you can authenticate as one of the
2188 </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2961288"></a>Third Step (optional): Check if Samba knows a Driver for the
2191 # rpcclient -Uroot%xxxx -c 'getprinter mysmbtstprn 2' localhost | grep driver
2192 drivername:[]
2194 # rpcclient -Uroot%xxxx -c 'getprinter mysmbtstprn 2' localhost | grep -C4 driv
2195 servername:[\\kde-bitshop]
2196 printername:[\\kde-bitshop\mysmbtstprn]
2197 sharename:[mysmbtstprn]
2198 portname:[Samba Printer Port]
2199 drivername:[]
2200 comment:[mysmbtstprn]
2201 location:[]
2202 sepfile:[]
2203 printprocessor:[winprint]
2205 # rpcclient -U root%xxxx -c 'getdriver mysmbtstprn' localhost
2206 result was WERR_UNKNOWN_PRINTER_DRIVER
2208 </pre><p>
2209 Neither method of the three commands shown above should show a driver.
2210 This step was done for the purpose of demonstrating this condition. An
2211 attempt to connect to the printer at this stage will prompt the
2212 message along the lines: "The server has not the required printer
2213 driver installed".
2214 </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2961326"></a>Fourth Step: Put all required Driver Files into Samba's
2217 # smbclient //localhost/print\$ -U 'root%xxxx' \
2218 -c 'cd W32X86; \
2219 put /etc/cups/ppd/mysmbtstprn.ppd mysmbtstprn.PPD; \
2220 put /usr/share/cups/drivers/cupsui.dll cupsui.dll; \
2221 put /usr/share/cups/drivers/cupsdrvr.dll cupsdrvr.dll; \
2222 put /usr/share/cups/drivers/cups.hlp cups.hlp'
2224 </pre><p>
2225 (Note that this command should be entered in one long single
2228 for the next one to succeed. It makes the driver files physically
2230 would still not be able to install them, because Samba does not yet
2231 treat them as driver files. A client asking for the driver would still
2233 </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2961377"></a>Fifth Step: Verify where the Driver Files are now</h4></div></div><div></div></div><pre class="screen">
2235 # ls -l /etc/samba/drivers/W32X86/
2236 total 669
2244 </pre><p>
2247 </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2961415"></a>Sixth Step: Tell Samba that these are
2252 cupsdrvr.dll:mysmbtstprn.PPD: \
2254 localhost
2256 Printer Driver mydrivername successfully installed.
2258 </pre><p>
2259 Note that your cannot repeat this step if it fails. It could fail even
2260 as a result of a simple typo. It will most likely have moved a part of
2262 need to go back to the fourth step and repeat it, before you can try
2263 this one again. In this step you need to choose a name for your
2264 driver. It is normally a good idea to use the same name as is used for
2265 the printername; however, in big installations you may use this driver
2266 for a number of printers which have obviously different names. So the
2267 name of the driver is not fixed.
2268 </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2961469"></a>Seventh Step: Verify where the Driver Files are now</h4></div></div><div></div></div><pre class="screen">
2270 # ls -l /etc/samba/drivers/W32X86/
2271 total 1
2276 # ls -l /etc/samba/drivers/W32X86/2
2277 total 5039
2278 [....]
2284 </pre><p>
2285 Notice how step 6 did also move the driver files to the appropriate
2286 subdirectory. Compare with the situation after step 5.
2287 </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2961503"></a>Eighth Step (optional): Verify if Samba now recognizes the
2290 # rpcclient -Uroot%xxxx -c 'enumdrivers 3' localhost | grep -B2 -A5 mydrivername
2292 Printer Driver Info 3:
2293 Version: [2]
2294 Driver Name: [mydrivername]
2295 Architecture: [Windows NT x86]
2296 Driver Path: [\\kde-bitshop\print$\W32X86\2\cupsdrvr.dll]
2297 Datafile: [\\kde-bitshop\print$\W32X86\2\mysmbtstprn.PPD]
2298 Configfile: [\\kde-bitshop\print$\W32X86\2\cupsui.dll]
2299 Helpfile: [\\kde-bitshop\print$\W32X86\2\cups.hlp]
2301 </pre><p>
2302 Remember, this command greps for the name you did choose for the
2303 driver in step Six. This command must succeed before you can proceed.
2304 </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2961536"></a>Ninth Step: Tell Samba which Printer should use these Driver
2307 # rpcclient -Uroot%xxxx -c 'setdriver mysmbtstprn mydrivername' localhost
2309 Successfully set mysmbtstprn to driver mydrivername
2311 </pre><p>
2312 Since you can bind any printername (=printqueue) to any driver, this
2313 is a very convenient way to setup many queues which use the same
2314 driver. You don't need to repeat all the previous steps for the
2315 setdriver command to succeed. The only pre-conditions are:
2318 </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2961586"></a>Tenth Step (optional): Verify if Samba has this Association
2321 # rpcclient -Uroot%xxxx -c 'getprinter mysmbtstprn 2' localhost | grep driver
2322 drivername:[mydrivername]
2324 # rpcclient -Uroot%xxxx -c 'getprinter mysmbtstprn 2' localhost | grep -C4 driv
2325 servername:[\\kde-bitshop]
2326 printername:[\\kde-bitshop\mysmbtstprn]
2327 sharename:[mysmbtstprn]
2328 portname:[Done]
2329 drivername:[mydrivername]
2330 comment:[mysmbtstprn]
2331 location:[]
2332 sepfile:[]
2333 printprocessor:[winprint]
2335 # rpcclient -U root%xxxx -c 'getdriver mysmbtstprn' localhost
2336 [Windows NT x86]
2337 Printer Driver Info 3:
2338 Version: [2]
2339 Driver Name: [mydrivername]
2340 Architecture: [Windows NT x86]
2341 Driver Path: [\\kde-bitshop\print$\W32X86\2\cupsdrvr.dll]
2342 Datafile: [\\kde-bitshop\print$\W32X86\2\mysmbtstprn.PPD]
2343 Configfile: [\\kde-bitshop\print$\W32X86\2\cupsui.dll]
2344 Helpfile: [\\kde-bitshop\print$\W32X86\2\cups.hlp]
2345 Monitorname: []
2346 Defaultdatatype: [RAW]
2347 Monitorname: []
2348 Defaultdatatype: [RAW]
2350 # rpcclient -Uroot%xxxx -c 'enumprinters' localhost | grep mysmbtstprn
2351 name:[\\kde-bitshop\mysmbtstprn]
2352 description:[\\kde-bitshop\mysmbtstprn,mydrivername,mysmbtstprn]
2353 comment:[mysmbtstprn]
2355 </pre><p>
2357 every single of these commands show the driver is installed. Even
2360 </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2961666"></a>Eleventh Step (optional): Tickle the Driver into a correct
2361 Device Mode</h4></div></div><div></div></div><p>
2362 You certainly know how to install the driver on the client. In case
2363 you are not particularly familiar with Windows, here is a short
2364 recipe: browse the Network Neighbourhood, go to the Samba server, look
2365 for the shares. You should see all shared Samba printers.
2366 Double-click on the one in question. The driver should get
2367 installed, and the network connection set up. An alternative way is to
2372 </p><p>
2373 It is important that you execute this step as a Samba printer admin
2375 to do this on Windows XP. It uses a commandline, which you may type
2379 C:\> runas /netonly /user:root "rundll32 printui.dll,PrintUIEntry /in /n \\sambacupsserver\mysmbtstprn"
2381 </pre><p>
2384 back.
2385 </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2961731"></a>Twelfth Step: Install the Printer on a Client
2390 </pre><p>
2391 If it doesn't work it could be a permission problem with the
2393 </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2961764"></a>Thirteenth Step (optional): Print a Test Page</h4></div></div><div></div></div><pre class="screen">
2397 </pre><p>
2398 Then hit [TAB] 5 times, [ENTER] twice, [TAB] once and [ENTER] again
2399 and march to the printer.
2400 </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2961790"></a>Fourteenth Step (recommended): Study the Test Page</h4></div></div><div></div></div><p>
2401 Hmmm.... just kidding! By now you know everything about printer
2402 installations and you don't need to read a word. Just put it in a
2403 frame and bolt it to the wall with the heading "MY FIRST
2404 RPCCLIENT-INSTALLED PRINTER" - why not just throw it away!
2405 </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2961808"></a>Fifteenth Step (obligatory): Enjoy. Jump. Celebrate your
2410 </pre></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2961830"></a>Troubleshooting revisited</h3></div></div><div></div></div><p>
2411 The setdriver command will fail, if in Samba's mind the queue is not
2412 already there. You had promising messages about the:
2415 Printer Driver ABC successfully installed.
2417 </pre><p>
2419 a disappointing message like this one beneath?
2422 result was NT_STATUS_UNSUCCESSFUL
2424 </pre><p>
2428 bug in most recent versions of Samba prevents the proper update of
2429 the queuelist. The recognition of newly installed CUPS printers
2430 fails unless you re-start Samba or send a HUP to all smbd
2431 processes. To verify if this is the reason why Samba doesn't
2433 the printer:
2436 # rpcclient transmeta -N -U'root%secret' -c 'enumprinters 0'| grep ir85wm
2437 printername:[ir85wm]
2439 </pre><p>
2440 An alternative command could be this:
2443 # rpcclient transmeta -N -U'root%secret' -c 'getprinter ir85wm'
2444 cmd = getprinter ir85wm
2445 flags:[0x800000]
2446 name:[\\transmeta\ir85wm]
2447 description:[\\transmeta\ir85wm,ir85wm,DPD]
2448 comment:[CUPS PostScript-Treiber for WinNT/2K/XP]
2450 </pre><p>
2451 BTW, you can use these commands, plus a few more, of course,
2452 to install drivers on remote Windows NT print servers too!
2453 </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2961930"></a>The printing <tt class="filename">*.tdb</tt> Files</h2></div></div><div></div></div><p>
2454 Some mystery is associated with the series of files with a
2455 tdb-suffix appearing in every Samba installation. They are
2468 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2962033"></a>Trivial DataBase Files</h3></div></div><div></div></div><p>
2469 A Windows NT (Print) Server keeps track of all information needed to serve
2470 its duty toward its clients by storing entries in the Windows
2472 Administrator or user configuration settings are saved by writing into
2473 the Registry. Samba and Unix obviously don't have such a kind of
2474 Registry. Samba instead keeps track of all client related information in a
2481 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2962103"></a>Binary Format</h3></div></div><div></div></div><p>
2484 ASCII configuration files are a good and proofed tradition on UNIX."
2485 -- The reason for this design decision by the Samba Team is mainly
2486 performance. Samba needs to be fast; it runs a separate
2488 environments many thousand of them. Some of these smbds might need to
2490 same time</em></span>. The file format of Samba's
2493 same time. This wouldn't be possible with pure ASCII files.
2494 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2962165"></a>Losing <tt class="filename">*.tdb</tt> Files</h3></div></div><div></div></div><p>
2496 consistent over all write and read accesses. However, it may happen
2499 progress could do the damage as well as a power interruption,
2500 etc.). In cases of trouble, a deletion of the old printing-related
2502 re-create all print related setup after that. Or you have made a
2504 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2962224"></a>Using <span class="emphasis"><em>tdbbackup</em></span></h3></div></div><div></div></div><p>
2505 Samba ships with a little utility which helps the root user of your
2507 with no argument, it prints a little usage message:
2510 # tdbbackup
2513 Version:3.0a
2514 -h this help message
2515 -s suffix set the backup suffix
2516 -v verify mode (restore if corrupt)
2518 </pre><p>
2519 Here is how I backed up my printing.tdb file:
2522 # ls
2523 . browse.dat locking.tdb ntdrivers.tdb printing.tdb share_info.tdb
2524 .. connections.tdb messages.tdb ntforms.tdb printing.tdbkp unexpected.tdb
2525 brlock.tdb gmon.out namelist.debug ntprinters.tdb sessionid.tdb
2527 kde-bitshop:/var/lock/samba # tdbbackup -s .bak printing.tdb
2528 printing.tdb : 135 records
2530 kde-bitshop:/var/lock/samba # ls -l printing.tdb*
2534 </pre></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2962290"></a>CUPS Print Drivers from Linuxprinting.org</h2></div></div><div></div></div><p>
2535 CUPS ships with good support for HP LaserJet type printers. You can
2536 install the generic driver as follows:
2539 lpadmin -p laserjet4plus -v parallel:/dev/lp0 -E -m laserjet.ppd
2541 </pre><p>
2544 not-yet-installed-PPDs, which CUPS typically stores in
2547 </p><p>
2548 The generic laserjet.ppd however does not support every special option
2549 for every LaserJet-compatible model. It constitutes a sort of "least
2550 denominator" of all the models. If for some reason it is ruled out to
2551 you to pay for the commercially available ESP Print Pro drivers, your
2552 first move should be to consult the database on <a href="http://www.linuxprinting.org/printer_list.cgi" target="_top">http://www.linuxprinting.org/printer_list.cgi</a>.
2553 Linuxprinting.org has excellent recommendations about which driver is
2554 best used for each printer. Its database is kept current by the
2555 tireless work of Till Kamppeter from MandrakeSoft, who is also the
2556 principal author of the foomatic-rip utility.
2557 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
2560 cupsomatic. cupsomatic is no longer maintained. Here is the new URL
2561 to the Foomatic-3.0 database:<a href="http://www.linuxprinting.org/driver_list.cgi" target="_top">http://www.linuxprinting.org/driver_list.cgi</a>.
2562 If you upgrade to foomatic-rip, don't forget to also upgrade to the
2563 new-style PPDs for your foomatic-driven printers. foomatic-rip will
2564 not work with PPDs generated for the old cupsomatic. The new-style
2565 PPDs are 100% compliant to the Adobe PPD specification. They are
2566 intended to be used by Samba and the cupsaddsmb utility also, to
2567 provide the driver files for the Windows clients also!
2568 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2962398"></a>foomatic-rip and Foomatic explained</h3></div></div><div></div></div><p>
2569 Nowadays most Linux distros rely on the utilities of Linuxprinting.org
2570 to create their printing related software (which, BTW, works on all
2571 UNIXes and on Mac OS X or Darwin too). It is not known as well as it
2572 should be, that it also has a very end-user friendly interface which
2573 allows for an easy update of drivers and PPDs, for all supported
2574 models, all spoolers, all operating systems and all package formats
2575 (because there is none). Its history goes back a few years.
2576 </p><p>
2577 Recently Foomatic has achieved the astonishing milestone of <a href="http://www.linuxprinting.org/printer_list.cgi?make=Anyone" target="_top">1000
2578 listed</a> printer models. Linuxprinting.org keeps all the
2579 important facts about printer drivers, supported models and which
2580 options are available for the various driver/printer combinations in
2582 database. Currently there are <a href="http://www.linuxprinting.org/driver_list.cgi" target="_top">245 drivers</a>
2583 in the database: many drivers support various models, and many models
2584 may be driven by different drivers; it's your choice!
2585 </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2962453"></a>690 "perfect" Printers</h4></div></div><div></div></div><p>
2587 "mostly", 96 "partially" and 46 are "Paperweights". Keeping in mind
2588 that most of these are non-PostScript models (PostScript printers are
2589 automatically supported supported by CUPS to perfection, by using
2590 their own manufacturer-provided Windows-PPD...), and that a
2592 doesn't also scan and copy and fax under GNU/Linux: then this is a
2593 truly astonishing achievement. Three years ago the number was not
2595 anywhere near the quality it is today!
2596 </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2962477"></a>How the "Printing HOWTO" started it all</h4></div></div><div></div></div><p>
2598 started it all. The roots of today's Linuxprinting.org are in the
2600 HOWTO</a> which he authored. As a side-project to this document,
2601 which served many Linux users and admins to guide their first steps in
2602 this complicated and delicate setup (to a scientist, printing is
2603 "applying a structured deposition of distinct patterns of ink or toner
2605 build in a little Postgres database with information about the
2606 hardware and driver zoo that made up Linux printing of the time. This
2607 database became the core component of today's Foomatic collection of
2608 tools and data. In the meantime it has moved to an XML representation
2609 of the data.
2610 </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2962522"></a>Foomatic's strange Name</h4></div></div><div></div></div><p>
2612 2000, CUPS was far less popular than today, and most systems used LPD,
2614 (good for a few hundred different printer models). These didn't
2615 support many device-specific options. CUPS also shipped with its own
2617 Ghostscript). On the other hand, CUPS provided brilliant support for
2620 Description files). Plus, CUPS was designed to be easily extensible.
2621 </p><p>
2622 Grant already had in his database a respectable compilation
2624 they run with. His idea, to generate PPDs from the database info
2625 and use them to make standard Ghostscript filters work within CUPS,
2626 proved to work very well. It also "killed several birds with one
2627 stone":
2628 </p><div class="itemizedlist"><ul type="disc"><li><p>It made all current and future Ghostscript filter
2629 developments available for CUPS;</p></li><li><p>It made available a lot of additional printer models
2631 printing was the only one available);</p></li><li><p>It gave all the advanced CUPS options (web interface,
2632 GUI driver configurations) to users wanting (or needing) to use
2633 Ghostscript filters.</p></li></ul></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2962589"></a>cupsomatic, pdqomatic, lpdomatic, directomatic</h4></div></div><div></div></div><p>
2634 CUPS worked through a quickly-hacked up filter script named <a href="http://www.linuxprinting.org/download.cgi?filename=cupsomatic&show=0" target="_top">cupsomatic</a>.
2635 cupsomatic ran the printfile through Ghostscript, constructing
2636 automatically the rather complicated command line needed. It just
2637 required to be copied into the CUPS system to make it work. To
2639 process, it needs a CUPS-PPD. This PPD is generated directly from the
2640 contents of the database. For CUPS and the respective printer/filter
2642 generation. After that was working, Grant implemented within a few
2643 days a similar thing for two other spoolers. Names chosen for the
2644 config-generator scripts were <a href="http://www.linuxprinting.org/download.cgi?filename=lpdomatic&show=0" target="_top">PDQ-O-Matic</a>
2645 (for PDQ) and <a href="http://www.linuxprinting.org/download.cgi?filename=lpdomatic&show=0" target="_top">LPD-O-Matic</a>
2646 (for - you guessed it - LPD); the configuration here didn't use PPDs
2647 but other spooler-specific files.
2648 </p><p>
2649 From late summer of that year, <a href="http://www.linuxprinting.org/till/" target="_top">Till Kamppeter</a>
2650 started to put work into the database. Till had been newly employed by
2652 convert their printing system over to CUPS, after they had seen his
2653 <a href="http://www.fltk.org/" target="_top">FLTK</a>-based <a href="http://cups.sourceforge.net/xpp/" target="_top">XPP</a> (a GUI frontend to
2654 the CUPS lp-command). He added a huge amount of new information and new
2655 printers. He also developed the support for other spoolers, like
2659 lpdomatic) and "spoolerless" printing (<a href="http://www.linuxprinting.org/download.cgi?filename=directomatic&show=0" target="_top">directomatic</a>)....
2660 </p><p>
2663 Foomatic up to versions 2.0.x required (ugly) Perl data structures
2664 attached the Linuxprinting.org PPDs for CUPS. It had a different
2666 configuration files..
2667 </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2962725"></a>7.13.1.5.The <span class="emphasis"><em>Grand Unification</em></span>
2668 achieved...</h4></div></div><div></div></div><p>
2669 This all has changed in Foomatic versions 2.9 (Beta) and released as
2671 scripts: it is called the <a href="http://www.linuxprinting.org/foomatic2.9/download.cgi?filename=foomatic-rip&show=0" target="_top">foomatic-rip</a>.
2672 This single script is the unification of the previously different
2673 spooler-specific *omatic scripts. foomatic-rip is used by all the
2674 different spoolers alike. Because foomatic-rip can read PPDs (both the
2675 original PostScript printer PPDs and the Linuxprinting.org-generated
2676 ones), all of a sudden all supported spoolers can have the power of
2678 their system.... For users there is improved media type and source
2679 support; paper sizes and trays are easier to configure.
2680 </p><p>
2681 Also, the New Generation of Linuxprinting.org PPDs doesn't contain
2682 Perl data structures any more. If you are a distro maintainer and have
2683 used the previous version of Foomatic, you may want to give the new
2684 one a spin: but don't forget to generate a new-version set of PPDs,
2685 via the new <a href="http://www.linuxprinting.org/download/foomatic/foomatic-db-engine-3.0.0beta1.tar.gz" target="_top">foomatic-db-engine</a>!
2686 Individual users just need to generate a single new PPD specific to
2687 their model by <a href="http://www.linuxprinting.org/kpfeifle/LinuxKongress2002/Tutorial/II.Foomatic-User/II.tutorial-handout-foomatic-user.html" target="_top">following
2688 the steps</a> outlined in the Foomatic tutorial or further
2689 below. This new development is truly amazing.
2690 </p><p>
2691 foomatic-rip is a very clever wrapper around the need to run
2692 Ghostscript with a different syntax, different options, different
2693 device selections and/or different filters for each different printer
2694 or different spooler. At the same time it can read the PPD associated
2695 with a print queue and modify the print job according to the user
2696 selections. Together with this comes the 100% compliance of the new
2697 Foomatic PPDs with the Adobe spec. Some really innovative features of
2698 the Foomatic concept will surprise users: it will support custom paper
2699 sizes for many printers; and it will support printing on media drawn
2700 from different paper trays within the same job (in both cases: even
2701 where there is no support for this from Windows-based vendor printer
2702 drivers).
2703 </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2962810"></a>Driver Development outside</h4></div></div><div></div></div><p>
2704 Most driver development itself does not happen within
2705 Linuxprinting.org. Drivers are written by independent maintainers.
2706 Linuxprinting.org just pools all the information, and stores it in its
2707 database. In addition, it also provides the Foomatic glue to integrate
2708 the many drivers into any modern (or legacy) printing system known to
2709 the world.
2710 </p><p>
2711 Speaking of the different driver development groups: most of
2712 the work is currently done in three projects. These are:
2713 </p><div class="itemizedlist"><ul type="disc"><li><p><a href="http://www-124.ibm.com/developerworks/oss/linux/projects/omni/" target="_top">Omni</a>
2714 -- a Free Software project by IBM which tries to convert their printer
2715 driver knowledge from good-ol' OS/2 times into a modern, modular,
2716 universal driver architecture for Linux/Unix (still Beta). This
2717 currently supports 437 models.</p></li><li><p><a href="http://hpinkjet.sf.net/" target="_top">HPIJS</a> --
2718 a Free Software project by HP to provide the support for their own
2719 range of models (very mature, printing in most cases is perfect and
2720 provides true photo quality). This currently supports 369
2721 models.</p></li><li><p><a href="http://gimp-print.sf.net/" target="_top">Gimp-Print</a> -- a Free software
2722 effort, started by Michael Sweet (also lead developer for CUPS), now
2723 directed by Robert Krawitz, which has achieved an amazing level of
2724 photo print quality (many Epson users swear that its quality is
2725 better than the vendor drivers provided by Epson for the Microsoft
2726 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="id2962892"></a>Forums, Downloads, Tutorials, Howtos -- also for Mac OS X and
2727 commercial Unix</h4></div></div><div></div></div><p>
2729 drivers. Look for printer information and <a href="http://www.linuxprinting.org//kpfeifle/LinuxKongress2002/Tutorial/" target="_top">tutorials</a>
2730 or solve printing problems in its popular <a href="http://www.linuxprinting.org/newsportal/" target="_top">forums</a>. But
2731 it's not just for GNU/Linux: users and admins of <a href="http://www.linuxprinting.org/macosx/" target="_top">commercial UNIX
2732 systems</a> are also going there, and the relatively new <a href="http://www.linuxprinting.org/newsportal/thread.php3?name=linuxprinting.macosx.general" target="_top">Mac
2733 OS X forum</a> has turned out to be one of the most frequented
2734 fora after only a few weeks.
2735 </p><p>
2736 Linuxprinting.org and the Foomatic driver wrappers around Ghostscript
2737 are now a standard toolchain for printing on all the important
2738 distros. Most of them also have CUPS underneath. While in recent years
2739 most printer data had been added by Till (who works at Mandrake), many
2740 additional contributions came from engineers with SuSE, RedHat,
2741 Connectiva, Debian and others. Vendor-neutrality is an important goal
2742 of the Foomatic project.
2743 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
2744 Till Kamppeter from MandrakeSoft is doing an excellent job in his
2745 spare time to maintain Linuxprinting.org and Foomatic. So if you use
2746 it often, please send him a note showing your appreciation.
2747 </p></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2962963"></a>Foomatic Database generated PPDs</h4></div></div><div></div></div><p>
2748 The Foomatic database is an amazing piece of ingenuity in itself. Not
2749 only does it keep the printer and driver information, but it is
2751 its internal XML-based datasets. While these PPDs are modelled to the
2753 Linuxprinting.org/Foomatic-PPDs don't normally drive PostScript
2754 printers: they are used to describe all the bells and whistles you
2755 could ring or blow on an Epson Stylus inkjet, or a HP Photosmart or
2758 keyword: it tells the CUPS daemon how to proceed with the PostScript
2759 print file (old-style Foomatic-PPDs named the
2762 script calls Ghostscript on the host system (the recommended variant
2763 is ESP Ghostscript) to do the rendering work. foomatic-rip knows which
2764 filter or internal device setting it should ask from Ghostscript to
2765 convert the PostScript printjob into a raster format ready for the
2766 target device. This usage of PPDs to describe the options of non-PS
2767 printers was the invention of the CUPS developers. The rest is easy:
2768 GUI tools (like KDE's marvellous <a href="http://printing.kde.org/overview/kprinter.phtml" target="_top">"kprinter"</a>,
2769 or the GNOME <a href="http://gtklp.sourceforge.net/" target="_top">"gtklp"</a>, "xpp" and the CUPS
2770 web interface) read the PPD too and use this information to present
2771 the available settings to the user as an intuitive menu selection.
2772 </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2963027"></a>foomatic-rip and Foomatic-PPD Download and Installation</h3></div></div><div></div></div><p>
2774 compatible printer in CUPS (note that recent distributions of SuSE,
2775 UnitedLinux and Mandrake may ship with a complete package of
2776 Foomatic-PPDs plus the foomatic-rip utility. going directly to
2777 Linuxprinting.org ensures you to get the latest driver/PPD files):
2778 </p><div class="itemizedlist"><ul type="disc"><li><p>Surf to <a href="http://www.linuxprinting.org/printer_list.cgi" target="_top">http://www.linuxprinting.org/printer_list.cgi</a>
2779 </p></li><li><p>Check the complete list of printers in the database:
2780 <a href="http://www.linuxprinting.org/printer_list.cgi?make=Anyone" target="_top">http://www.linuxprinting.org/printer_list.cgi?make=Anyone</a>
2781 </p></li><li><p>There select your model and click on the
2782 link.</p></li><li><p>You'll arrive at a page listing all drivers working
2783 with this model (for all printers, there will always be
2786 <a href="http://www.linuxprinting.org/show_printer.cgi?recnum=HP-LaserJet_4_Plus" target="_top">http://www.linuxprinting.org/show_printer.cgi?recnum=HP-LaserJet_4_Plus</a>
2787 </p></li><li><p>The recommended driver is "ljet4".</p></li><li><p>There are several links provided here. You should
2788 visit them all, if you are not familiar with the Linuxprinting.org
2790 <a href="http://www.linuxprinting.org/show_driver.cgi?driver=ljet4" target="_top">http://www.linuxprinting.org/show_driver.cgi?driver=ljet4</a>
2791 On the driver's page, you'll find important and detailed information
2792 about how to use that driver within the various available
2793 spoolers.</p></li><li><p>Another link may lead you to the homepage of the
2794 driver author or the driver.</p></li><li><p>Important links are the ones which provide hints with
2795 setup instructions for CUPS (<a href="http://www.linuxprinting.org/cups-doc.html" target="_top">http://www.linuxprinting.org/cups-doc.html</a>),
2796 PDQ (<a href="http://www.linuxprinting.org/pdq-doc.html" target="_top">http://www.linuxprinting.org/pdq-doc.html</a>),
2797 LPD, LPRng and GNUlpr (<a href="http://www.linuxprinting.org/lpd-doc.html" target="_top">http://www.linuxprinting.org/lpd-doc.html</a>)
2798 as well as PPR (<a href="http://www.linuxprinting.org/ppr-doc.html" target="_top">http://www.linuxprinting.org/ppr-doc.html)</a>
2799 or "spooler-less" printing (<a href="http://www.linuxprinting.org/direct-doc.html" target="_top">http://www.linuxprinting.org/direct-doc.html</a>
2800 ).</p></li><li><p>You can view the PPD in your browser through this
2801 link: <a href="http://www.linuxprinting.org/ppd-o-matic.cgi?driver=ljet4&printer=HP-LaserJet_4_Plus&show=1" target="_top">http://www.linuxprinting.org/ppd-o-matic.cgi?driver=ljet4&printer=HP-LaserJet_4_Plus&show=1</a>
2802 </p></li><li><p>You can also (most importantly)
2803 generate and download the PPD: <a href="http://www.linuxprinting.org/ppd-o-matic.cgi?driver=ljet4&printer=HP-LaserJet_4_Plus&show=0" target="_top">http://www.linuxprinting.org/ppd-o-matic.cgi?driver=ljet4&printer=HP-LaserJet_4_Plus&show=0</a>
2804 </p></li><li><p>The PPD contains all the information needed to use our
2805 model and the driver; this is, once installed, working transparently
2806 for the user. Later you'll only need to choose resolution, paper size
2807 etc. from the web-based menu, or from the print dialog GUI, or from
2808 the commandline.</p></li><li><p>Should you have ended up on the driver's page (<a href="http://www.linuxprinting.org/show_driver.cgi?driver=ljet4" target="_top">http://www.linuxprinting.org/show_driver.cgi?driver=ljet4</a>),
2811 "display PPD file" and click on "Generate PPD file".</p></li><li><p>If you save the PPD file from the browser view, please
2813 and tabs, which makes the PPD likely to fail its duty), but use "Save
2815 from the web page directly).</p></li><li><p>Another very interesting part on each driver page is
2817 select your printer model and click that button, you will get
2818 displayed a complete Ghostscript command line, enumerating all options
2819 available for that driver/printermodel combo. This is a great way to
2821 for all experienced users who need to re-construct a good command line
2822 for that damn printing script, but can't remember the exact
2823 syntax. ;-)</p></li><li><p>Some time during your visit to Linuxprinting.org, save
2824 the PPD to a suitable place on your harddisk, say
2826 your printers with the help of the CUPS web interface, save the PPD to
2828 cupsd).</p></li><li><p>Then install the printer with a suitable commandline,
2829 e.g.:
2832 lpadmin -p laserjet4plus -v parallel:/dev/lp0 -E -P path/to/my-printer.ppd
2836 "foomatic-rip".Get the latest version of "foomatic-rip" from: <a href="http://www.linuxprinting.org/foomatic2.9/download.cgi?filename=foomatic-rip&show=0" target="_top">http://www.linuxprinting.org/foomatic2.9/download.cgi?filename=foomatic-rip&show=0</a>
2837 </p></li><li><p>The foomatic-rip Perlscript itself also makes some
2838 interesting reading (<a href="http://www.linuxprinting.org/foomatic2.9/download.cgi?filename=foomatic-rip&show=1" target="_top">http://www.linuxprinting.org/foomatic2.9/download.cgi?filename=foomatic-rip&show=1</a>),
2839 because it is very well documented by Till's inline comments (even
2840 non-Perl hackers will learn quite a bit about printing by reading
2841 it... ;-)</p></li><li><p>Save foomatic-rip either directly in
2843 your $PATH (and don't forget to make it world-executable). Again,
2845 "Save as..." menu item in your browser.</p></li><li><p>If you save foomatic-rip in your $PATH, create a symlink:
2847 foomatic-rip`</b>. For CUPS to discover this new
2848 available filter at startup, you need to re-start
2849 cupsd.</p></li></ul></div><p>
2850 Once you print to a printqueue set up with the Foomatic-PPD, CUPS will
2851 insert the appropriate commands and comments into the resulting
2852 PostScript jobfile. foomatic-rip is able to read and act upon
2853 these. foomatic-rip uses some specially encoded Foomatic comments,
2854 embedded in the jobfile. These in turn are used to construct
2855 (transparently for you, the user) the complicated ghostscript command
2856 line telling for the printer driver how exactly the resulting raster
2857 data should look like and which printer commands to embed into the
2858 data stream.
2859 </p><p>
2860 You need:
2861 </p><div class="itemizedlist"><ul type="disc"><li><p>A "foomatic+something" PPD -- but it this not enough
2864 /usr/lib/cups/filters/</p></li><li><p>Perl to make foomatic-rip run</p></li><li><p>Ghostscript (because it is doing the main work,
2865 controlled by the PPD/foomatic-rip combo) to produce the raster data
2866 fit for your printermodel's consumption</p></li><li><p>Ghostscript <span class="emphasis"><em>must</em></span> (depending on
2870 produced for cupsomatic don't work with
2871 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="id2963488"></a>Page Accounting with CUPS</h2></div></div><div></div></div><p>
2873 (that is, Windows clients) should not be able to print beyond a
2874 certain amount of pages or data volume per day, week or month. This
2875 feature is dependent on the real print subsystem you're using.
2876 Samba's part is always to receive the job files from the clients
2878 printing subsystem.
2879 </p><p>
2882 jobs or on the number of pages or both, and are spanning any time
2883 period you want.
2884 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2963519"></a>Setting up Quotas</h3></div></div><div></div></div><p>
2885 This is an example command how root would set a print quota in CUPS,
2891 </pre><p>
2894 week).
2895 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2963551"></a>Correct and incorrect Accounting</h3></div></div><div></div></div><p>
2896 For CUPS to count correctly, the printfile needs to pass the CUPS
2898 printfiles don't pass it (eg: image files) but then those are mostly 1
2899 page jobs anyway. This also means that proprietary drivers for the
2900 target printer running on the client computers and CUPS/Samba, which
2903 </p><p>
2904 You need to send PostScript from the clients (i.e. run a PostScript
2905 driver there) to have the chance to get accounting done. If the
2906 printer is a non-PostScript model, you need to let CUPS do the job to
2907 convert the file to a print-ready format for the target printer. This
2909 see <a href="http://www.linuxprinting.org/printer_list.cgi" target="_top">http://www.linuxprinting.org/printer_list.cgi</a>).
2910 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2963592"></a>Adobe and CUPS PostScript Drivers for Windows Clients</h3></div></div><div></div></div><p>
2911 Before CUPS-1.1.16 your only option was to use the Adobe PostScript
2912 Driver on the Windows clients. The output of this driver was not
2914 therefore was not counted correctly (the reason is that it often,
2916 the real PostScript which caused CUPS to skip pstops and go directly
2918 </p><p>
2923 </p><div class="itemizedlist"><ul type="disc"><li><p>to not write an PJL-header</p></li><li><p>to still read and support all PJL-options named in the
2924 driver PPD with its own means</p></li><li><p> that the file will pass through the "pstops" filter
2925 on the CUPS/Samba server</p></li><li><p>to page-count correctly the
2926 printfile</p></li></ul></div><p>
2927 You can read more about the setup of this combination in the manpage
2929 current from CUPS 1.1.16).
2930 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2963663"></a>The page_log File Syntax</h3></div></div><div></div></div><p>
2933 </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>the page number</p></li><li><p>the number of copies</p></li><li><p>a billing information string
2934 (optional)</p></li><li><p>the host which sent the job (included since version
2936 Here is an extract of my CUPS server's page_log file to illustrate the
2937 format and included items:
2946 </pre><p>
2947 This was job ID "401", printed on "infotec_IS2027" by user "kurt", a
2952 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2963765"></a>Possible Shortcomings</h3></div></div><div></div></div><p>
2953 What flaws or shortcomings are there with this quota system?
2954 </p><div class="itemizedlist"><ul type="disc"><li><p>the ones named above (wrongly logged job in case of
2955 printer hardware failure, etc.)</p></li><li><p>in reality, CUPS counts the job pages that are being
2958 printing device. Thus if there is a jam while printing the 5th sheet out
2960 still show the figure of 1000 for that job</p></li><li><p>all quotas are the same for all users (no flexibility
2961 to give the boss a higher quota than the clerk) no support for
2962 groups</p></li><li><p>no means to read out the current balance or the
2963 "used-up" number of current quota</p></li><li><p>a user having used up 99 sheets of 100 quota will
2964 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
2965 doesn't get a meaningful error message from CUPS other than
2966 "client-error-not-possible".</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2963836"></a>Future Developments</h3></div></div><div></div></div><p>
2967 This is the best system currently available, and there are huge
2968 improvements under development for CUPS 1.2:
2969 </p><div class="itemizedlist"><ul type="disc"><li><p>page counting will go into the "backends" (these talk
2970 directly to the printer and will increase the count in sync with the
2971 actual printing process: thus a jam at the 5th sheet will lead to a
2972 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
2973 their "accounts" in advance</p></li><li><p>probably there will be support for some other tools
2974 around this topic</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2963884"></a>Other Accounting Tools</h3></div></div><div></div></div><p>
2975 PrintAnalyzer, pyKota, printbill, LogReport.
2976 </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2963899"></a>Additional Material</h2></div></div><div></div></div><p>
2981 filtering at all, they hand the file directly to the CUPS backend.
2982 This backend is responsible for the sending of the data to the device
2984 smb://, ipp://, http://, parallel:/, serial:/, usb:/</tt> etc.)
2985 </p><p>
2986 "cupsomatic"/Foomatic are <span class="emphasis"><em>not</em></span> native CUPS drivers
2987 and they don't ship with CUPS. They are a Third Party add-on,
2988 developed at Linuxprinting.org. As such, they are a brilliant hack to
2989 make all models (driven by Ghostscript drivers/filters in traditional
2990 spoolers) also work via CUPS, with the same (good or bad!) quality as
2992 ghostscript commandline at that stage in the CUPS filtering chain,
2995 away and re-directs it to go through Ghostscript. CUPS accepts this,
2996 because the associated CUPS-O-Matic-/Foomatic-PPD specifies:
3001 </pre><p>
3002 This line persuades CUPS to hand the file to cupsomatic, once it has
3003 successfully converted it to the MIME type
3005 Jobs arriving from Windows which are auto-typed
3008 </p><p>
3009 CUPS is widely configurable and flexible, even regarding its filtering
3010 mechanism. Another workaround in some situations would be to have in
3014 application/postscript application/vnd.cups-raw 0 -
3015 application/vnd.cups-postscript application/vnd.cups-raw 0 -
3017 </pre><p>
3018 This would prevent all Postscript files from being filtered (rather,
3021 want to print PS code on non-PS printers (provided they support ASCII
3022 text printing) an entry as follows could be useful:
3025 */* application/vnd.cups-raw 0 -
3027 </pre><p>
3029 backend without further processing.
3030 </p><p>
3031 Lastly, you could have the following entry:
3034 application/vnd.cups-postscript application/vnd.cups-raw 0 my_PJL_stripping_filter
3036 </pre><p>
3038 (could be a shellscript) that parses the PostScript and removes the
3039 unwanted PJL. This would need to conform to CUPS filter design
3040 (mainly, receive and pass the parameters printername, job-id,
3041 username, jobtitle, copies, print options and possibly the
3042 filename). It would be installed as world executable into
3045 </p><p>
3048 upon manual release by the printer operator. This is a requirement in
3050 the jobs of hundreds of users on some big machine, where no user is
3051 allowed to have direct access (such as when the operators often need
3053 requested by marketing for the mailing, etc.).
3054 </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2964092"></a>Auto-Deletion or Preservation of CUPS Spool Files</h2></div></div><div></div></div><p>
3057 /var/spool/samba</em></span> directive in the
3060 your UNIX print subsystem. For CUPS it is normally
3063 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2964138"></a>CUPS Configuration Settings explained</h3></div></div><div></div></div><p>
3064 Some important parameter settings in the CUPS configuration file
3066 </p><div class="variablelist"><dl><dt><span class="term">PreserveJobHistory Yes</span></dt><dd><p>
3067 This keeps some details of jobs in cupsd's mind (well it keeps the
3069 similar job as the old-fashioned BSD-LPD control files). This is set
3072 This keeps the job files themselves in cupsd's mind
3075 default.
3076 </p></dd><dt><span class="term"><span class="emphasis"><em>"MaxJobs 500"</em></span></span></dt><dd><p>
3077 This directive controls the maximum number of jobs
3078 that are kept in memory. Once the number of jobs reaches the limit,
3079 the oldest completed job is automatically purged from the system to
3080 make room for the new one. If all of the known jobs are still
3081 pending or active then the new job will be rejected. Setting the
3082 maximum to 0 disables this functionality. The default setting is
3083 0.
3084 </p></dd></dl></div><p>
3087 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2964221"></a>Pre-conditions</h3></div></div><div></div></div><p>
3088 For everything to work as announced, you need to have three
3089 things:
3090 </p><div class="itemizedlist"><ul type="disc"><li><p>a Samba-smbd which is compiled against "libcups" (Check
3091 on Linux by running "ldd `which smbd`")</p></li><li><p>a Samba-<tt class="filename">smb.conf</tt> setting of
3092 "printing = cups"</p></li><li><p>another Samba-<tt class="filename">smb.conf</tt> setting of
3093 "printcap = cups"</p></li></ul></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
3094 In this case all other manually set printing-related commands (like
3095 "print command", "lpq command", "lprm command", "lppause command" or
3097 influence what-so-ever on your printing.
3098 </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2964281"></a>Manual Configuration</h3></div></div><div></div></div><p>
3099 If you want to do things manually, replace the "printing =
3102 may do what you need.
3103 </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2964299"></a>When <span class="emphasis"><em>not</em></span> to use Samba to print to
3104 CUPS</h2></div></div><div></div></div><p>
3105 [TO BE DONE]
3106 </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2964316"></a>In Case of Trouble.....</h2></div></div><div></div></div><p>
3107 If you have more problems, post the output of these commands
3108 to the CUPS or Samba mailing lists (choose the one which seems more
3109 relevant to your problem):
3112 grep -v ^# /etc/cups/cupsd.conf | grep -v ^$
3115 </pre><p>
3116 (adapt paths as needed). These commands leave out the empty
3118 compact way. Don't forget to name the CUPS and Samba versions you
3119 are using! This saves bandwidth and makes for easier readability
3120 for experts (and you are expecting experts to read them, right?
3121 ;-)
3122 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2964352"></a>Where to find Documentation</h3></div></div><div></div></div><p>
3123 [TO BE DONE]
3124 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2964364"></a>How to ask for Help</h3></div></div><div></div></div><p>
3125 [TO BE DONE]
3126 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2964377"></a>Where to find Help</h3></div></div><div></div></div><p>
3127 [TO BE DONE]
3128 </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2964391"></a>Appendix</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2964398"></a>Printing <span class="emphasis"><em>from</em></span> CUPS to Windows attached
3129 Printers</h3></div></div><div></div></div><p>
3130 From time to time the question arises, how you can print
3134 cable, but this doesn't matter to Samba. From here only an SMB
3135 connection needs to be opened to the Windows host. Of course, this
3138 servers. To talk to Windows shared printers you need to use the
3140 is in the CUPS backend directory. This resides usually in
3143 which file must exist and be executable:
3146 # ls -l /usr/lib/cups/backend/
3147 total 253
3163 # ls -l `which smbspool`
3166 </pre><p>
3167 If this symlink doesn't exist, create it:
3170 # ln -s `which smbspool` /usr/lib/cups/backend/smb
3172 </pre><p>
3173 smbspool has been written by Mike Sweet from the CUPS folks. It is
3174 included and ships with Samba. It may also be used with print
3175 subsystems other than CUPS, to spool jobs to Windows printer shares. To
3177 it. Essentially this means to convert the print data on the CUPS/Samba
3178 host to a format that the printer can digest (the Windows host is
3179 unable to convert any files you may send). This also means you should
3180 be able to print to the printer if it were hooked directly at your
3181 Samba/CUPS host. For troubleshooting purposes, this is what you
3182 should do, to determine if that part of the process chain is in
3183 order. Then proceed to fix the network connection/authentication to
3184 the Windows host, etc.
3185 </p><p>
3186 To install a printer with the smb backend on CUPS, use this command:
3189 # lpadmin -p winprinter -v smb://WINDOWSNETBIOSNAME/printersharename -P /path/to/PPD
3191 </pre><p>
3193 the print data for the target model. For PostScript printers just use
3194 the PPD that would be used with the Windows NT PostScript driver. But
3195 what can you do if the printer is only accessible with a password? Or
3196 if the printer's host is part of another workgroup? This is provided
3197 for: you can include the required parameters as part of the
3201 smb://WORKGROUP/WINDOWSNETBIOSNAME/printersharename
3202 smb://username:password@WORKGROUP/WINDOWSNETBIOSNAME/printersharename
3203 smb://username:password@WINDOWSNETBIOSNAME/printersharename
3205 </pre><p>
3206 Note that the device-URI will be visible in the process list of the
3208 command on Linux), even if the username and passwords are sanitized
3209 before they get written into the log files. So this is an inherently
3210 insecure option. However it is the only one. Don't use it if you want
3211 to protect your passwords. Better share the printer in a way that
3212 doesn't require a password! Printing will only work if you have a
3213 working netbios name resolution up and running. Note that this is a
3214 feature of CUPS and you don't necessarily need to have smbd running
3215 (but who wants that? :-).
3216 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2964612"></a>More CUPS filtering Chains</h3></div></div><div></div></div><p>
3217 The following diagrams reveal how CUPS handles print jobs.
3219 #########################################################################
3220 #
3221 # CUPS in and of itself has this (general) filter chain (CAPITAL
3222 # letters are FILE-FORMATS or MIME types, other are filters (this is
3224 #
3225 # SOMETHNG-FILEFORMAT
3226 # |
3227 # V
3228 # somethingtops
3229 # |
3230 # V
3231 # APPLICATION/POSTSCRIPT
3232 # |
3233 # V
3234 # pstops
3235 # |
3236 # V
3237 # APPLICATION/VND.CUPS-POSTSCRIPT
3238 # |
3239 # V
3240 # pstoraster # as shipped with CUPS, independent from any Ghostscipt
3241 # | # installation on the system
3243 # V
3244 # APPLICATION/VND.CUPS-RASTER
3245 # |
3246 # V
3247 # rastertosomething (e.g. Gimp-Print filters may be plugged in here)
3249 # V
3250 # SOMETHING-DEVICE-SPECIFIC
3251 # |
3252 # V
3253 # backend
3254 #
3255 #
3258 #
3259 # NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to
3260 # CUPS and ESP PrintPro plug-in where rastertosomething is noted.
3261 #
3262 #########################################################################
3264 #########################################################################
3265 #
3267 # =========================================
3268 #
3269 # SOMETHNG-FILEFORMAT
3270 # |
3271 # V
3272 # somethingtops
3273 # |
3274 # V
3275 # APPLICATION/POSTSCRIPT
3276 # |
3277 # V
3278 # pstops
3279 # |
3280 # V
3281 # APPLICATION/VND.CUPS-POSTSCRIPT ----------------+
3282 # | V
3283 # V cupsomatic
3284 # pstoraster (constructs complicated
3286 # | to let the file be
3287 # V processed by a
3289 # | call...)
3290 # V |
3291 # rastertosomething V
3293 # | | Ghostscript at work.... |
3294 # V | |
3295 # SOMETHING-DEVICE-SPECIFIC *-------------------------+
3296 # | |
3297 # V |
3298 # backend <------------------------------------+
3299 # |
3300 # V
3301 # THE PRINTER
3302 #
3303 #
3306 # the CUPS-external, systemwide Ghostscript installation, bypassing the
3309 # backend...
3310 #
3311 # cupsomatic is not made by the CUPS developers. It is an independent
3312 # contribution to printing development, made by people from
3313 # Linuxprinting.org. (see also http://www.cups.org/cups-help.html)
3314 #
3315 # NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to
3316 # CUPS and ESP PrintPro plug-in where rastertosomething is noted.
3317 #
3318 #########################################################################
3320 #########################################################################
3321 #
3322 # And this is how it works for ESP PrintPro from 4.3:
3323 # ===================================================
3324 #
3325 # SOMETHNG-FILEFORMAT
3326 # |
3327 # V
3328 # somethingtops
3329 # |
3330 # V
3331 # APPLICATION/POSTSCRIPT
3332 # |
3333 # V
3334 # pstops
3335 # |
3336 # V
3337 # APPLICATION/VND.CUPS-POSTSCRIPT
3338 # |
3339 # V
3340 # gsrip
3342 # V
3343 # APPLICATION/VND.CUPS-RASTER
3344 # |
3345 # V
3346 # rastertosomething (e.g. Gimp-Print filters may be plugged in here)
3348 # V
3349 # SOMETHING-DEVICE-SPECIFIC
3350 # |
3351 # V
3352 # backend
3353 #
3354 # NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to
3355 # CUPS and ESP PrintPro plug-in where rastertosomething is noted.
3356 #
3357 #########################################################################
3359 #########################################################################
3360 #
3362 # ================================================================
3363 #
3364 #
3365 # SOMETHNG-FILEFORMAT
3366 # |
3367 # V
3368 # somethingtops
3369 # |
3370 # V
3371 # APPLICATION/POSTSCRIPT
3372 # |
3373 # V
3374 # pstops
3375 # |
3376 # V
3377 # APPLICATION/VND.CUPS-POSTSCRIPT ----------------+
3378 # | V
3379 # V cupsomatic
3380 # gsrip (constructs complicated
3382 # | to let the file be
3383 # V processed by a
3385 # | call...)
3386 # V |
3387 # rastertosomething V
3389 # | | Ghostscript at work.... |
3390 # V | |
3391 # SOMETHING-DEVICE-SPECIFIC *-------------------------+
3392 # | |
3393 # V |
3394 # backend <------------------------------------+
3395 # |
3396 # V
3397 # THE PRINTER
3398 #
3399 # NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to
3400 # CUPS and ESP PrintPro plug-in where rastertosomething is noted.
3401 #
3402 #########################################################################
3404 #########################################################################
3405 #
3406 # And this is how it works for CUPS from 1.1.15:
3407 # ==============================================
3408 #
3409 # SOMETHNG-FILEFORMAT
3410 # |
3411 # V
3412 # somethingtops
3413 # |
3414 # V
3415 # APPLICATION/POSTSCRIPT
3416 # |
3417 # V
3418 # pstops
3419 # |
3420 # V
3421 # APPLICATION/VND.CUPS-POSTSCRIPT-----+
3422 # +------------------v------------------------------+
3423 # | Ghostscript |
3424 # | at work... |
3425 # | (with |
3427 # | |
3429 # | |
3430 # +------------------v------------------------------+
3431 # |
3432 # APPLICATION/VND.CUPS-RASTER >-------+
3433 # |
3434 # V
3435 # rastertosomething
3437 # V
3438 # SOMETHING-DEVICE-SPECIFIC
3439 # |
3440 # V
3441 # backend
3442 #
3443 #
3445 # Ghostscript. GNU Ghostscript needs to be patched to handle the
3446 # CUPS requirement; ESP Ghostscript has this builtin. In any case,
3451 # Note the difference to "cupsomatic", which will <span class="emphasis"><em>not</em></span> output
3452 # CUPS-raster, but a final version of the printfile, ready to be
3454 # devicemode in Ghostscript, but one of the classical devicemodes....
3455 #
3456 # NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to
3457 # CUPS and ESP PrintPro plug-in where rastertosomething is noted.
3458 #
3459 #########################################################################
3461 #########################################################################
3462 #
3463 # And this is how it works for CUPS from 1.1.15, with cupsomatic included:
3464 # ========================================================================
3465 #
3466 # SOMETHNG-FILEFORMAT
3467 # |
3468 # V
3469 # somethingtops
3470 # |
3471 # V
3472 # APPLICATION/POSTSCRIPT
3473 # |
3474 # V
3475 # pstops
3476 # |
3477 # V
3478 # APPLICATION/VND.CUPS-POSTSCRIPT-----+
3479 # +------------------v------------------------------+
3480 # | Ghostscript . Ghostscript at work.... |
3481 # | at work... . (with "-sDEVICE= |
3482 # | (with . s.th." |
3484 # | . |
3485 # | (CUPS standard) . (cupsomatic) |
3486 # | . |
3488 # | . |
3489 # +------------------v--------------v---------------+
3490 # | |
3491 # APPLICATION/VND.CUPS-RASTER >-------+ |
3492 # | |
3493 # V |
3494 # rastertosomething |
3496 # V |
3497 # SOMETHING-DEVICE-SPECIFIC >------------------------+
3498 # |
3499 # V
3500 # backend
3501 #
3502 #
3503 # NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to
3504 # CUPS and ESP PrintPro plug-in where rastertosomething is noted.
3505 #
3506 ##########################################################################
3507 </pre></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2964919"></a>Trouble Shooting Guidelines to fix typical Samba printing
3508 Problems</h3></div></div><div></div></div><p>
3509 This is a short description of how to debug printing problems
3510 with Samba. This describes how to debug problems with printing from
3511 a SMB client to a Samba server, not the other way around.
3512 </p><div class="variablelist"><dl><dt><span class="term">Win9x client can't install driver</span></dt><dd><p>For Win9x clients require the printer names to be 8
3514 won't get transferred when you want to download them from
3515 Samba.</p></dd><dt><span class="term">testparm</span></dt><dd><p>Run <b class="command">testparm</b>: It will tell you if
3520 this.</p></dd><dt><span class="term">"cupsaddsmb" keeps asking for a root password in a
3521 neverending loop</span></dt><dd><p>Have you <i class="parameter"><tt>security = user</tt></i>? Have
3523 You can do 2 things: open another terminal and execute
3525 continue with entering the password into the first terminal. Or break
3526 out of the loop by hitting ENTER twice (without trying to type a
3527 password).</p></dd><dt><span class="term">"cupsaddsmb" gives "No PPD file for printer..."
3528 message (but I swear there is one!)</span></dt><dd><div class="itemizedlist"><ul type="disc"><li><p>Have you enabled printer sharing on CUPS? This means:
3532 the host you run "cupsaddsmb" from? It <span class="emphasis"><em>could</em></span> be
3533 an issue if you use cupsaddsmb remotely, or if you use it with a
3535 sambaserver -h cupsserver -v printername</b>.
3536 </p></li><li><p>Is your
3539 set to a valid value and is it writeable?
3540 </p></li></ul></div></dd><dt><span class="term">I can't connect client to Samba printer.</span></dt><dd><p>Use <b class="command">smbstatus</b> to check which user
3541 you are from Samba's point of view. Do you have the privileges to
3546 guest = bad user</tt></i>), Windows Explorer will not accept an
3547 attempt to connect again as a different user. There won't be any byte
3548 transfered on the wire to Samba, but still you'll see a stupid error
3549 message which makes you think that Samba has denied access. Use
3551 PIDs. You still can't re-connect and get the dreaded
3553 machine</tt> message, as soon as you are trying? And you
3555 indicating a renewed connection attempt? Shut all Explorer Windows.
3556 This makes Windows forget what it has cached in its memory as
3557 established connections. Then re-connect as the right user. Best
3563 printer in question and select
3564 <span class="emphasis"><em>Connect...</em></span></p></dd><dt><span class="term">Avoid being connected to the Samba server as the
3565 "wrong" user</span></dt><dd><p>You see per <b class="command">smbstatus</b> that you are
3568 user</tt></i>, which silently connects you under the guest account,
3569 when you gave (maybe by accident) an incorrect username. Remove
3572 NT/2K/XP clients gives problems</span></dt><dd><p>First delete all "old" Adobe-using printers. Then
3575 tab "Drivers" and delete here).</p></dd><dt><span class="term">I can't use "cupsaddsmb"on a Samba server which is
3578 printername</em></span> (note the two backslashes: the first one is
3579 required to "escape" the second one).</p></dd><dt><span class="term">I deleted a printer on Win2K; but I still see
3580 its driver</span></dt><dd><p>Deleting a printer on the client won't delete the
3581 driver too (to verify, right-click on the white background of the
3584 install a printer with the same name. If you want to update to a new
3585 driver, delete the old ones first. Deletion is only possible if no
3586 other printer uses the same driver.</p></dd><dt><span class="term">Win2K/XP "Local Security
3587 Policies"</span></dt><dd><p><span class="emphasis"><em>Local Security Policies</em></span> may not
3589 may not allow the installation of printer drivers at
3591 printers for all local users"</span></dt><dd><p>Windows XP handles SMB printers on a "per-user" basis.
3592 This means every user needs to install the printer himself. To have a
3593 printer available for everybody, you might want to use the built-in
3594 IPP client capabilities of WinXP. Add a printer with the print path of
3597 automatically install printers for all
3602 XP).</p></dd><dt><span class="term">WinXP-SP1</span></dt><dd><p>WinXP-SP1 introduced a <span class="emphasis"><em>Point and Print
3603 Restriction Policy</em></span> (this restriction doesn't apply to
3607 Printers</em></span>. The policy is automatically set to
3608 <span class="emphasis"><em>Enabled</em></span> and the <span class="emphasis"><em>Users can only Point
3609 and Print to machines in their Forest</em></span> . You probably need
3610 to change it to <span class="emphasis"><em>Disabled</em></span> or <span class="emphasis"><em>Users can
3611 only Point and Print to these servers</em></span> in order to make
3612 driver downloads from Samba possible.</p></dd><dt><span class="term">I can't set and save default print options for all
3613 users on Win2K/XP</span></dt><dd><p>How are you doing it? I bet the wrong way (it is not
3614 very easy to find out, though). There are 3 different ways to bring
3618 Administrator or Print Administrator to do this for all users. Here
3619 is how I do in on XP:
3622 </p><div class="orderedlist"><ol type="1"><li><p>Open the <span class="emphasis"><em>Printers</em></span>
3623 folder.</p></li><li><p>Right-click on the printer
3626 Preferences...</em></span></p></li><li><p>Look at this dialog closely and remember what it looks
3627 like.</p></li></ol></div><p>
3630 </p><div class="orderedlist"><ol type="1"><li><p>Open the <span class="emphasis"><em>Printers</em></span>
3632 cupshost</em></span>) and select in the context menu
3633 <span class="emphasis"><em>Properties</em></span></p></li><li><p>Click on the <span class="emphasis"><em>General</em></span>
3635 Preferences...</em></span></p></li><li><p>A new dialog opens. Keep this dialog open and go back
3636 to the parent dialog.</p></li></ol></div><p>
3641 </p><div class="orderedlist"><ol type="1"><li><p>Click on the <span class="emphasis"><em>Advanced</em></span>
3643 in as a user with enough privileges).</p></li><li><p>Click on the <span class="emphasis"><em>Printing
3646 button.</p></li><li><p>A new dialog opens. Compare this one to the other,
3648 </p></li></ol></div><p>
3649 Do you see any difference? I don't either... However, only the last
3651 permanently and be the defaults for new users. If you want all clients
3655 downloads the driver (the clients can later set their own
3657 procedures <span class="emphasis"><em>A.</em></span> or <span class="emphasis"><em>B.</em></span>
3659 settings on Windows clients?</span></dt><dd><p>Don't use <span class="emphasis"><em>Optimize for
3661 Portability</em></span> instead (Adobe PS Driver) Don't use
3664 Yes</em></span> (Microsoft PS Driver and CUPS PS Driver for
3665 WinNT/2K/XP) If there are problems with fonts: use
3667 printer</em></span> (Adobe PS Driver). For
3670 Level 2, if you are having trouble with a non-PS printer, and if
3671 there is a choice.</p></dd><dt><span class="term">I can't make <b class="command">cupsaddsmb</b> work
3672 with newly installed printer</span></dt><dd><p>Symptom: the last command of
3675 NT_STATUS_UNSUCCESSFUL then possibly the printer was not yet
3678 hostname -c 'enumprinters'</b>? Restart smbd (or send a
3683 reboot</span></dt><dd><p>Have you by accident set the CUPS spool directory to
3693 sanitize permissions to its spool directory with each restart, and
3694 printing will not work reliably.</p></dd><dt><span class="term">My printers work fine: just the printer named "lp"
3695 intermittently swallows jobs and spits out completely different
3697 is the traditional Unix name for the default printer. CUPS may be set
3699 group all printers with the same name to a pool of devices, and
3700 loadbalancing the jobs across them in a round-robin fashion. Chances
3702 receive his jobs and send your own to his device unwittingly. To have
3705 then, giving you a better control over what may happen in a large
3706 networked environment.</p></dd><dt><span class="term">How do I "watch" my Samba server?</span></dt><dd><p>You can use <b class="command">tail -f
3707 /var/log/samba/log.smbd</b> (you may need a different path) to
3709 debuglevel</b> tells you which verbosity goes into the
3713 more than 3 initially; or you'll drown in an ocean of
3715 access from WinXP Prof works flawlessly</span></dt><dd><p>You have our condolences! WinXP home has been
3716 completely neutered by Microsoft as compared to WinXP Prof: you can
3717 not log into a WinNT domain. It cannot join a Win NT domain as a
3718 member server. While it is possible to access domain resources, users
3720 each time they connect to a resource. Logon scripts and roaming
3721 profiles are not supported. It can serve file and print shares; but
3725 I need for "cupsaddsmb"?</span></dt><dd><p>Use <b class="command">smbclient</b> to connect to any
3727 //windowsbox/print\$ -U guest</b>. You can navigate to the
3731 files from the Adobe website.</p></dd></dl></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2966041"></a>An Overview of the CUPS Printing Processes</h3></div></div><div></div></div><p>
3732 </p><div class="figure"><a name="id2966052"></a><p class="title"><b>Figure 19.15. CUPS Printing Overview</b></p><div class="mediaobject"><img src="projdoc/imagefiles/a_small.png" alt="CUPS Printing Overview"></div></div><p>
3733 </p></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="printing.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="optional.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="VFS.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 18. 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 20. Stackable VFS modules</td></tr></table></div></body></html>