summaryrefslogtreecommitdiff
path: root/docs/htmldocs/cups-printing.html
diff options
context:
space:
mode:
authorGerald Carter <jerry@samba.org>2003-09-09 03:11:56 +0000
committerGerald Carter <jerry@samba.org>2003-09-09 03:11:56 +0000
commitb968848a1697dfc7216e1802883b5f7e55025111 (patch)
tree05d30dcd1daed7575cba09aa7308747b50ad66f8 /docs/htmldocs/cups-printing.html
parent99bde6889d3d8b7a9e950c86c30e82662e1dacdd (diff)
downloadsamba-b968848a1697dfc7216e1802883b5f7e55025111.tar.gz
samba-b968848a1697dfc7216e1802883b5f7e55025111.tar.bz2
samba-b968848a1697dfc7216e1802883b5f7e55025111.zip
removing files not in 3.0
(This used to be commit d5c32f8881f33667c9bfa067cb7f2113bd55c724)
Diffstat (limited to 'docs/htmldocs/cups-printing.html')
-rw-r--r--docs/htmldocs/cups-printing.html2773
1 files changed, 0 insertions, 2773 deletions
diff --git a/docs/htmldocs/cups-printing.html b/docs/htmldocs/cups-printing.html
deleted file mode 100644
index 8dd4a94f4f..0000000000
--- a/docs/htmldocs/cups-printing.html
+++ /dev/null
@@ -1,2773 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<HTML
-><HEAD
-><TITLE
->CUPS Printing Support</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
-REL="HOME"
-TITLE="SAMBA Project Documentation"
-HREF="samba-howto-collection.html"><LINK
-REL="UP"
-TITLE="Advanced Configuration"
-HREF="optional.html"><LINK
-REL="PREVIOUS"
-TITLE="Printing Support"
-HREF="printing.html"><LINK
-REL="NEXT"
-TITLE="Unified Logons between Windows NT and UNIX using Winbind"
-HREF="winbind.html"></HEAD
-><BODY
-CLASS="CHAPTER"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->SAMBA Project Documentation</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="printing.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
-></TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="winbind.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="CHAPTER"
-><H1
-><A
-NAME="CUPS-PRINTING"
-></A
->Chapter 14. CUPS Printing Support</H1
-><DIV
-CLASS="TOC"
-><DL
-><DT
-><B
->Table of Contents</B
-></DT
-><DT
->14.1. <A
-HREF="cups-printing.html#AEN2034"
->Introduction</A
-></DT
-><DT
->14.2. <A
-HREF="cups-printing.html#AEN2041"
->Configuring <TT
-CLASS="FILENAME"
->smb.conf</TT
-> for CUPS</A
-></DT
-><DT
->14.3. <A
-HREF="cups-printing.html#AEN2061"
->CUPS - RAW Print Through Mode</A
-></DT
-><DT
->14.4. <A
-HREF="cups-printing.html#AEN2118"
->CUPS as a network PostScript RIP -- CUPS drivers working on server, Adobe
-PostScript driver with CUPS-PPDs downloaded to clients</A
-></DT
-><DT
->14.5. <A
-HREF="cups-printing.html#AEN2139"
->Windows Terminal Servers (WTS) as CUPS clients</A
-></DT
-><DT
->14.6. <A
-HREF="cups-printing.html#AEN2143"
->Setting up CUPS for driver download</A
-></DT
-><DT
->14.7. <A
-HREF="cups-printing.html#AEN2156"
->Sources of CUPS drivers / PPDs</A
-></DT
-><DT
->14.8. <A
-HREF="cups-printing.html#AEN2212"
->The CUPS Filter Chains</A
-></DT
-><DT
->14.9. <A
-HREF="cups-printing.html#AEN2251"
->CUPS Print Drivers and Devices</A
-></DT
-><DT
->14.10. <A
-HREF="cups-printing.html#AEN2328"
->Limiting the number of pages users can print</A
-></DT
-><DT
->14.11. <A
-HREF="cups-printing.html#AEN2424"
->Advanced Postscript Printing from MS Windows</A
-></DT
-><DT
->14.12. <A
-HREF="cups-printing.html#AEN2439"
->Auto-Deletion of CUPS spool files</A
-></DT
-></DL
-></DIV
-><DIV
-CLASS="SECT1"
-><H1
-CLASS="SECT1"
-><A
-NAME="AEN2034"
->14.1. Introduction</A
-></H1
-><P
->The Common Unix Print System (CUPS) has become very popular, but to many it is
-a very mystical tool. There is a great deal of uncertainty regarding CUPS and how
-it works. The result is seen in a large number of posting on the samba mailing lists
-expressing frustration when MS Windows printers appear not to work with a CUPS
-backr-end.</P
-><P
->This is a good time to point out how CUPS can be used and what it does. CUPS is more
-than just a print spooling system - it is a complete printer management system that
-complies with HTTP and IPP protocols. It can be managed remotely via a web browser
-and it can print using http and ipp protocols.</P
-><P
->CUPS allows to creation of RAW printers (ie: NO file format translation) as well as
-SMART printers (ie: CUPS does file format conversion as required for the printer). In
-many ways this gives CUPS similar capabilities to the MS Windows print monitoring
-system. Of course, if you are a CUPS advocate, you would agrue that CUPS is better!
-In any case, let us now move on to explore how one may configure CUPS for interfacing
-with MS Windows print clients via Samba.</P
-><P
-><A
-HREF="http://www.cups.org/"
-TARGET="_top"
->CUPS</A
-> is a newcomer in the UNIX printing scene,
-which has convinced many people upon first trial already. However, it has quite a few
-new features, which make it different from other, more traditional printing systems.</P
-></DIV
-><DIV
-CLASS="SECT1"
-><H1
-CLASS="SECT1"
-><A
-NAME="AEN2041"
->14.2. Configuring <TT
-CLASS="FILENAME"
->smb.conf</TT
-> for CUPS</A
-></H1
-><P
->Printing with CUPS in the most basic <TT
-CLASS="FILENAME"
->smb.conf</TT
->
-setup in Samba-3 only needs two settings: <B
-CLASS="COMMAND"
->printing = cups</B
-> and
-<B
-CLASS="COMMAND"
->printcap = cups</B
->. While CUPS itself doesn't need a printcap
-anymore, the <TT
-CLASS="FILENAME"
->cupsd.conf</TT
-> configuration file knows two directives
-(example: <B
-CLASS="COMMAND"
->Printcap /etc/printcap</B
-> and <B
-CLASS="COMMAND"
->PrintcapFormat
-BSD</B
->), which control if such a file should be created for the
-convenience of third party applications. Make sure it is set! For details see
-<B
-CLASS="COMMAND"
->man cupsd.conf</B
-> and other CUPS-related documentation.</P
-><P
->If SAMBA is compiled against libcups, then <B
-CLASS="COMMAND"
->printcap = cups</B
-> uses the
-CUPS API to list printers, submit jobs, etc. Otherwise it maps to the System V commands
-with an additional <VAR
-CLASS="PARAMETER"
->-oraw</VAR
-> option for printing. On a Linux system,
-you can use the <B
-CLASS="COMMAND"
->ldd</B
-> command to find out details (ldd may not be
-present on other OS platforms, or its function may be embodied by a different command):</P
-><P
-><PRE
-CLASS="PROGRAMLISTING"
->transmeta:/home/kurt # ldd `which smbd`
- libssl.so.0.9.6 =&#62; /usr/lib/libssl.so.0.9.6 (0x4002d000)
- libcrypto.so.0.9.6 =&#62; /usr/lib/libcrypto.so.0.9.6 (0x4005a000)
- libcups.so.2 =&#62; /usr/lib/libcups.so.2 (0x40123000)
- libdl.so.2 =&#62; /lib/libdl.so.2 (0x401e8000)
- libnsl.so.1 =&#62; /lib/libnsl.so.1 (0x401ec000)
- libpam.so.0 =&#62; /lib/libpam.so.0 (0x40202000)
- libc.so.6 =&#62; /lib/libc.so.6 (0x4020b000)
- /lib/ld-linux.so.2 =&#62; /lib/ld-linux.so.2 (0x40000000)</PRE
-></P
-><P
->The line "libcups.so.2 =&#62; /usr/lib/libcups.so.2
-(0x40123000)" shows there is CUPS support compiled into this version of
-Samba. If this is the case, and <B
-CLASS="COMMAND"
->printing = cups</B
-> is set, then any
-otherwise manually set print command in <TT
-CLASS="FILENAME"
->smb.conf</TT
-> is ignored.</P
-></DIV
-><DIV
-CLASS="SECT1"
-><H1
-CLASS="SECT1"
-><A
-NAME="AEN2061"
->14.3. CUPS - RAW Print Through Mode</A
-></H1
-><DIV
-CLASS="NOTE"
-><P
-></P
-><TABLE
-CLASS="NOTE"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->When used in raw print through mode is will be necessary to use the printer
-vendor's drivers in each Windows client PC.</P
-></TD
-></TR
-></TABLE
-></DIV
-><P
->When CUPS printers are configured for RAW print-through mode operation it is the
-responsibility of the Samba client to fully render the print job (file) in a format
-that is suitable for direct delivery to the printer. In this case CUPS will NOT
-do any print file format conversion work.</P
-><P
->The CUPS files that need to be correctly set for RAW mode printers to work are:
-
-<P
-></P
-><UL
-><LI
-><P
-><TT
-CLASS="FILENAME"
->/etc/cups/mime.types</TT
-></P
-></LI
-><LI
-><P
-><TT
-CLASS="FILENAME"
->/etc/cups/mime.convs</TT
-></P
-></LI
-></UL
->
-
-Both contain entries that must be uncommented to allow <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->RAW</I
-></SPAN
-> mode
-operation.</P
-><P
->Firstly, to enable CUPS based printing from Samba the following options must be
-enabled in your <TT
-CLASS="FILENAME"
->smb.conf</TT
-> file [globals] section:
-
-<P
-></P
-><UL
-><LI
-><P
->printing = CUPS</P
-></LI
-><LI
-><P
->printcap = CUPS</P
-></LI
-></UL
->
-
-When these parameters are specified the print directives in <TT
-CLASS="FILENAME"
->smb.conf</TT
-> (as well as in
-samba itself) will be ignored because samba will directly interface with CUPS through
-it's application program interface (API) - so long as Samba has been compiled with
-CUPS library (libcups) support. If samba has NOT been compiled with CUPS support then
-printing will use the System V AT&#38;T command set with the <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->-oraw</I
-></SPAN
->
-option automatically passing through.</P
-><P
->Cupsomatic (an enhanced printing utility that is part of some CUPS implementations)
-on the Samba/CUPS server does *not* add any features if a file is really
-printed "raw". However, if you have loaded the driver for the Windows client from
-the CUPS server, using the "cupsaddsmb" utility, and if this driver is one using
-a "Foomatic" PPD, the PJL header in question is already added on the Windows client,
-at the time when the driver initially generated the PostScript data and CUPS in true
-"-oraw" manner doesn't remove this PJL header and passes the file "as is" to its
-printer communication backend.</P
-><DIV
-CLASS="NOTE"
-><P
-></P
-><TABLE
-CLASS="NOTE"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->NOTE: editing in the "mime.convs" and the "mime.types" file does not *enforce*
-"raw" printing, it only *allows* it.</P
-></TD
-></TR
-></TABLE
-></DIV
-><P
->Print files that arrive from MS Windows printing are "auto-typed" by CUPS. This aids
-the process of determining proper treatment while in the print queue system.
-
-<P
-></P
-><UL
-><LI
-><P
-> Files generated by PCL drivers and directed at PCK printers get auto-typed as
- <TT
-CLASS="FILENAME"
->application/octet-stream</TT
->. Unknown file format types also
- get auto-typed with this tag.
- </P
-></LI
-><LI
-><P
-> Files generated by a Postscript driver and directed at a Postscript printer
- are auto-typed depending on the auto-detected most suitable MIME type as:
-
- <P
-></P
-><UL
-><LI
-><P
->* application/postscript</P
-></LI
-><LI
-><P
->* application/vnd.cups-postscript</P
-></LI
-></UL
->
- </P
-></LI
-></UL
-></P
-><P
->"application/postscript" first goes thru the "pstops" filter (where the page counting
-and accounting takes place). The outcome will be of MIME type
-"application/vnd.cups-postscript". The pstopsfilter reads and uses information from
-the PPD and inserts user-provided options into the PostScript file. As a consequence,
-the filtered file could possibly have an unwanted PJL header.</P
-><P
->"application/postscript" will be all files with a ".ps", ".ai", ".eps" suffix or which
-have as their first character string one of "%!" or "&#62;04&#60;%".</P
-><P
->"application/vnd.cups-postscript" will files which contain the string
-"LANGUAGE=POSTSCRIPT" (or similar variations with different capitalization) in the
-first 512 bytes, and also contain the "PJL super escape code" in the first 128 bytes
-("&#62;1B&#60;%-12345X"). Very likely, most PostScript files generated on Windows using a CUPS
-or other PPD, will have to be auto-typed as "vnd.cups-postscript". A file produced
-with a "Generic PostScript driver" will just be tagged "application/postscript".</P
-><P
->Once the file is in "application/vnd.cups-postscript" format, either "pstoraster"
-or "cupsomatic" will take over (depending on the printer configuration, as
-determined by the PPD in use).</P
-><DIV
-CLASS="NOTE"
-><P
-></P
-><TABLE
-CLASS="NOTE"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->A printer queue with *no* PPD associated to it is a "raw" printer and all files
-will go directly there as received by the spooler. The exeptions are file types
-"application/octet-stream" which need "passthrough feature" enabled.
-"Raw" queues don't do any filtering at all, they hand the file directly to the
-CUPS backend. This backend is responsible for the sending of the data to the device
-(as in the "device URI" notation as lpd://, socket://, smb://, ipp://, http://,
-parallel:/, serial:/, usb:/ etc.)</P
-></TD
-></TR
-></TABLE
-></DIV
-><DIV
-CLASS="NOTE"
-><P
-></P
-><TABLE
-CLASS="NOTE"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->"cupsomatic"/Foomatic are *not* native CUPS drivers and they don't ship with CUPS.
-They are a Third Party add-on, developed at Linuxprinting.org. As such, they are
-a brilliant hack to make all models (driven by Ghostscript drivers/filters in
-traditional spoolers) also work via CUPS, with the same (good or bad!) quality
-as in these other spoolers. "cupsomatic" is only a vehicle to execute a ghostscript
-commandline at that stage in the CUPS filtering chain, where "normally" the native
-CUPS "pstoraster" filter would kick in. cupsomatic by-passes pstoraster, "kidnaps"
-the printfile from CUPS away and re-directs it to go through Ghostscipt. CUPS accepts this,
-because the associated CUPS-O-Matic-/Foomatic-PPD specifies:</P
-><PRE
-CLASS="PROGRAMLISTING"
-> *cupsFilter: "application/vnd.cups-postscript 0 cupsomatic"</PRE
-><P
->This line persuades CUPS to hand the file to cupsomatic, once it has successfully
-converted it to the MIME type "application/vnd.cups-postscript". This conversion will not
-happen for Jobs arriving from Windows which are auto-typed "application/octet-stream",
-with the according changes in "/etc/cups/mime.types" in place.</P
-></TD
-></TR
-></TABLE
-></DIV
-><P
->CUPS is widely configurable and flexible, even regarding its filtering mechanism.
-Another workaround in some situations would be to have
-in "/etc/cups/mime.types" entries as follows:</P
-><PRE
-CLASS="PROGRAMLISTING"
-> application/postscript application/vnd.cups-raw 0 -
- application/vnd.cups-postscript application/vnd.cups-raw 0 -</PRE
-><P
->This would prevent all Postscript files from being filtered (rather, they will go
-thru the virtual "nullfilter" denoted with "-"). This could only be useful for
-PS printers. If you want to print PS code on non-PS printers an entry as follows
-could be useful:</P
-><PRE
-CLASS="PROGRAMLISTING"
-> */* application/vnd.cups-raw 0 -</PRE
-><P
->and would effectively send *all* files to the backend without further processing.</P
-><P
->Lastly, you could have the following entry:</P
-><PRE
-CLASS="PROGRAMLISTING"
-> application/vnd.cups-postscript application/vnd.cups-raw 0 my_PJL_stripping_filter</PRE
-><P
->You will need to write a "my_PJL_stripping_filter" (could be a shellscript) that
-parses the PostScript and removes the unwanted PJL. This would need to conform to
-CUPS filter design (mainly, receive and pass the parameters printername, job-id,
-username, jobtitle, copies, print options and possibly the filename). It would
-be installed as world executable into "/usr/lib/cups/filters/" and will be called
-by CUPS if it encounters a MIME type "application/vnd.cups-postscript".</P
-><P
->CUPS can handle "-o job-hold-until=indefinite". This keeps the job in the queue
-"on hold". It will only be printed upon manual release by the printer operator.
-This is a requirement in many "central reproduction departments", where a few
-operators manage the jobs of hundreds of users on some big machine, where no
-user is allowed to have direct access. (The operators often need to load the
-proper paper type before running the 10.000 page job requested by marketing
-for the mailing, etc.).</P
-></DIV
-><DIV
-CLASS="SECT1"
-><H1
-CLASS="SECT1"
-><A
-NAME="AEN2118"
->14.4. CUPS as a network PostScript RIP -- CUPS drivers working on server, Adobe
-PostScript driver with CUPS-PPDs downloaded to clients</A
-></H1
-><P
->CUPS is perfectly able to use PPD files (PostScript
-Printer Descriptions). PPDs can control all print device options. They
-are usually provided by the manufacturer -- if you own a PostSript printer,
-that is. PPD files are always a component of PostScript printer drivers on MS
-Windows or Apple Mac OS systems. They are ASCII files containing
-user-selectable print options, mapped to appropriate PostScript, PCL or PJL
-commands for the target printer. Printer driver GUI dialogs translate these
-options "on-the-fly" into buttons and drop-down lists for the user to
-select.</P
-><P
->CUPS can load, without any conversions, the PPD file from
-any Windows (NT is recommended) PostScript driver and handle the options.
-There is a web browser interface to the print options (select
-http://localhost:631/printers/ and click on one "Configure Printer" button
-to see it), a commandline interface (see <B
-CLASS="COMMAND"
->man lpoptions</B
-> or
-try if you have <B
-CLASS="COMMAND"
->lphelp</B
-> on your system) plus some different GUI frontends on Linux
-UNIX, which can present PPD options to the users. PPD options are normally
-meant to become evaluated by the PostScript RIP on the real PostScript
-printer.</P
-><P
->CUPS doesn't stop at "real" PostScript printers in its
-usage of PPDs. The CUPS developers have extended the PPD concept, to also
-describe available device and driver options for non-PostScript printers
-through CUPS-PPDs.</P
-><P
->This is logical, as CUPS includes a fully featured
-PostScript interpreter (RIP). This RIP is based on Ghostscript. It can
-process all received PostScript (and additionally many other file formats)
-from clients. All CUPS-PPDs geared to non-PostScript printers contain an
-additional line, starting with the keyword <VAR
-CLASS="PARAMETER"
->*cupsFilter</VAR
->.
-This line
-tells the CUPS print system which printer-specific filter to use for the
-interpretation of the accompanying PostScript. Thus CUPS lets all its
-printers appear as PostScript devices to its clients, because it can act as a
-PostScript RIP for those printers, processing the received PostScript code
-into a proper raster print format.</P
-><P
->CUPS-PPDs can also be used on Windows-Clients, on top of a
-PostScript driver (recommended is the Adobe one).</P
-><P
->This feature enables CUPS to do a few tricks no other
-spooler can do:</P
-><P
-></P
-><UL
-><LI
-><P
->act as a networked PostScript RIP (Raster Image Processor), handling
- printfiles from all client platforms in a uniform way;</P
-></LI
-><LI
-><P
->act as a central accounting and billing server, as all files are passed
- through the <B
-CLASS="COMMAND"
->pstops</B
-> Filter and are therefor logged in
- the CUPS <TT
-CLASS="FILENAME"
->page&lowbar;log</TT
->. - <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->NOTE: </I
-></SPAN
->this
- can not happen with "raw" print jobs, which always remain unfiltered
- per definition;</P
-></LI
-><LI
-><P
->enable clients to consolidate on a single PostScript driver, even for
- many different target printers.</P
-></LI
-></UL
-></DIV
-><DIV
-CLASS="SECT1"
-><H1
-CLASS="SECT1"
-><A
-NAME="AEN2139"
->14.5. Windows Terminal Servers (WTS) as CUPS clients</A
-></H1
-><P
->This setup may be of special interest to people
-experiencing major problems in WTS environments. WTS need often a multitude
-of non-PostScript drivers installed to run their clients' variety of
-different printer models. This often imposes the price of much increased
-instability. In many cases, in an attempt to overcome this problem, site
-administrators have resorted to restrict the allowed drivers installed on
-their WTS to one generic PCL- and one PostScript driver. This however
-restricts the clients in the amount of printer options available for them --
-often they can't get out more then simplex prints from one standard paper
-tray, while their devices could do much better, if driven by a different
-driver!</P
-><P
->Using an Adobe PostScript driver, enabled with a CUPS-PPD,
-seems to be a very elegant way to overcome all these shortcomings. The
-PostScript driver is not known to cause major stability problems on WTS (even
-if used with many different PPDs). The clients will be able to (again) chose
-paper trays, duplex printing and other settings. However, there is a certain
-price for this too: a CUPS server acting as a PostScript RIP for its clients
-requires more CPU and RAM than just to act as a "raw spooling" device. Plus,
-this setup is not yet widely tested, although the first feedbacks look very
-promising...</P
-></DIV
-><DIV
-CLASS="SECT1"
-><H1
-CLASS="SECT1"
-><A
-NAME="AEN2143"
->14.6. Setting up CUPS for driver download</A
-></H1
-><P
->The <B
-CLASS="COMMAND"
->cupsadsmb</B
-> utility (shipped with all current
-CUPS versions) makes the sharing of any (or all) installed CUPS printers very
-easy. Prior to using it, you need the following settings in <TT
-CLASS="FILENAME"
->smb.conf</TT
->:</P
-><P
-><PRE
-CLASS="PROGRAMLISTING"
->[global]
- load printers = yes
- printing = cups
- printcap name = cups
-
- [printers]
- comment = All Printers
- path = /var/spool/samba
- browseable = no
- public = yes
- guest ok = yes
- writable = no
- printable = yes
- printer admin = root
-
- [print$]
- comment = Printer Drivers
- path = /etc/samba/drivers
- browseable = yes
- guest ok = no
- read only = yes
- write list = root
- </PRE
-></P
-><P
->For licensing reasons the necessary files of the Adobe
-Postscript driver can not be distributed with either Samba or CUPS. You need
-to download them yourself from the Adobe website. Once extracted, create a
-<TT
-CLASS="FILENAME"
->drivers</TT
-> directory in the CUPS data directory (usually
-<TT
-CLASS="FILENAME"
->/usr/share/cups/</TT
->). Copy the Adobe files using
-UPPERCASE filenames, to this directory as follows:</P
-><P
-><PRE
-CLASS="PROGRAMLISTING"
-> ADFONTS.MFM
- ADOBEPS4.DRV
- ADOBEPS4.HLP
- ADOBEPS5.DLL
- ADOBEPSU.DLL
- ADOBEPSU.HLP
- DEFPRTR2.PPD
- ICONLIB.DLL
- </PRE
-></P
-><P
->Users of the ESP Print Pro software are able to install
-their "Samba Drivers" package for this purpose with no problem.</P
-></DIV
-><DIV
-CLASS="SECT1"
-><H1
-CLASS="SECT1"
-><A
-NAME="AEN2156"
->14.7. Sources of CUPS drivers / PPDs</A
-></H1
-><P
->On the internet you can find now many thousand CUPS-PPD
-files (with their companion filters), in many national languages,
-supporting more than 1.000 non-PostScript models.</P
-><P
-></P
-><UL
-><LI
-><P
-><A
-HREF="http://wwwl.easysw.com/printpro/"
-TARGET="_top"
->ESP PrintPro
- (http://wwwl.easysw.com/printpro/)</A
->
- (commercial, non-Free) is packaged with more than 3.000 PPDs, ready for
- successful usage "out of the box" on Linux, IBM-AIX, HP-UX, Sun-Solaris,
- SGI-IRIX, Compaq Tru64, Digital Unix and some more commercial Unices (it
- is written by the CUPS developers themselves and its sales help finance
- the further development of CUPS, as they feed their creators)</P
-></LI
-><LI
-><P
->the <A
-HREF="http://gimp-print.sourceforge.net/"
-TARGET="_top"
->Gimp-Print-Project
- (http://gimp-print.sourceforge.net/)</A
->
- (GPL, Free Software) provides around 120 PPDs (supporting nearly 300
- printers, many driven to photo quality output), to be used alongside the
- Gimp-Print CUPS filters;</P
-></LI
-><LI
-><P
-><A
-HREF="http://www.turboprint.com/"
-TARGET="_top"
->TurboPrint
- (http://www.turboprint.com/)</A
->
- (Shareware, non-Freee) supports roughly the same amount of printers in
- excellent quality;</P
-></LI
-><LI
-><P
-><A
-HREF="http://www-124.ibm.com/developerworks/oss/linux/projects/omni/"
-TARGET="_top"
->OMNI
- (http://www-124.ibm.com/developerworks/oss/linux/projects/omni/)</A
->
- (LPGL, Free) is a package made by IBM, now containing support for more
- than 400 printers, stemming from the inheritance of IBM OS/2 KnowHow
- ported over to Linux (CUPS support is in a Beta-stage at present);</P
-></LI
-><LI
-><P
-><A
-HREF="http://hpinkjet.sourceforge.net/"
-TARGET="_top"
->HPIJS
- (http://hpinkjet.sourceforge.net/)</A
->
- (BSD-style licnes, Free) supports around 120 of HP's own printers and is
- also providing excellent print quality now;</P
-></LI
-><LI
-><P
-><A
-HREF="http://www.linuxprinting.org/"
-TARGET="_top"
->Foomatic/cupsomatic (http://www.linuxprinting.org/)</A
->
- (LPGL, Free) from Linuxprinting.org are providing PPDs for practically every
- Ghostscript filter known to the world, now usable with CUPS.</P
-></LI
-></UL
-><P
-><SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->NOTE: </I
-></SPAN
->the cupsomatic trick from Linuxprinting.org is
-working different from the other drivers. While the other drivers take the
-generic CUPS raster (produced by CUPS' own pstoraster PostScript RIP) as
-their input, cupsomatic "kidnaps" the PostScript inside CUPS, before
-RIP-ping, deviates it to an external Ghostscript installation (which now
-becomes the RIP) and gives it back to a CUPS backend once Ghostscript is
-finished. -- CUPS versions from 1.1.15 and later will provide their pstoraster
-PostScript RIP function again inside a system-wide Ghostscript
-installation rather than in "their own" pstoraster filter. (This
-CUPS-enabling Ghostscript version may be installed either as a
-patch to GNU or AFPL Ghostscript, or as a complete ESP Ghostscript package).
-However, this will not change the cupsomatic approach of guiding the printjob
-along a different path through the filtering system than the standard CUPS
-way...</P
-><P
->Once you installed a printer inside CUPS with one of the
-recommended methods (the lpadmin command, the web browser interface or one of
-the available GUI wizards), you can use <B
-CLASS="COMMAND"
->cupsaddsmb</B
-> to share the
-printer via Samba. <B
-CLASS="COMMAND"
->cupsaddsmb</B
-> prepares the driver files for
-comfortable client download and installation upon their first contact with
-this printer share.</P
-><DIV
-CLASS="SECT2"
-><H2
-CLASS="SECT2"
-><A
-NAME="AEN2183"
->14.7.1. <B
-CLASS="COMMAND"
->cupsaddsmb</B
-></A
-></H2
-><P
->The <B
-CLASS="COMMAND"
->cupsaddsmb</B
-> command copies the needed files
-for convenient Windows client installations from the previously prepared CUPS
-data directory to your [print$] share. Additionally, the PPD
-associated with this printer is copied from <TT
-CLASS="FILENAME"
->/etc/cups/ppd/</TT
-> to
-[print$].</P
-><P
-><PRE
-CLASS="PROGRAMLISTING"
-><SAMP
-CLASS="PROMPT"
->root# </SAMP
-> <B
-CLASS="COMMAND"
->cupsaddsmb -U root infotec_IS2027</B
->
-Password for root required to access localhost via SAMBA: <KBD
-CLASS="USERINPUT"
->[type in password 'secret']</KBD
-></PRE
-></P
-><P
->To share all printers and drivers, use the <VAR
-CLASS="PARAMETER"
->-a</VAR
->
-parameter instead of a printer name.</P
-><P
->Probably you want to see what's going on. Use the
-<VAR
-CLASS="PARAMETER"
->-v</VAR
-> parameter to get a more verbose output:</P
-><P
->Probably you want to see what's going on. Use the
-<VAR
-CLASS="PARAMETER"
->-v</VAR
-> parameter to get a more verbose output:</P
-><P
-><PRE
-CLASS="PROGRAMLISTING"
->Note: The following line shave been wrapped so that information is not lost.
-
-<SAMP
-CLASS="PROMPT"
->root# </SAMP
-> cupsaddsmb -v -U root infotec_IS2027
- Password for root required to access localhost via SAMBA:
- Running command: smbclient //localhost/print\$ -N -U'root%secret' -c 'mkdir W32X86;put
- /var/spool/cups/tmp/3cd1cc66376c0 W32X86/infotec_IS2027.PPD;put /usr/share/cups/drivers/
- ADOBEPS5.DLL W32X86/ADOBEPS5.DLL;put /usr/share/cups/drivers/ADOBEPSU.DLLr
- W32X86/ADOBEPSU.DLL;put /usr/share/cups/drivers/ADOBEPSU.HLP W32X86/ADOBEPSU.HLP'
- added interface ip=10.160.16.45 bcast=10.160.31.255 nmask=255.255.240.0
- added interface ip=192.168.182.1 bcast=192.168.182.255 nmask=255.255.255.0
- added interface ip=172.16.200.1 bcast=172.16.200.255 nmask=255.255.255.0
- Domain=[TUX-NET] OS=[Unix] Server=[Samba 2.2.3a.200204262025cvs]
- NT_STATUS_OBJECT_NAME_COLLISION making remote directory \W32X86
- putting file /var/spool/cups/tmp/3cd1cc66376c0 as \W32X86/infotec_IS2027.PPD (17394.6 kb/s)
- (average 17395.2 kb/s)
- putting file /usr/share/cups/drivers/ADOBEPS5.DLL as \W32X86/ADOBEPS5.DLL (10877.4 kb/s)
- (average 11343.0 kb/s)
- putting file /usr/share/cups/drivers/ADOBEPSU.DLL as \W32X86/ADOBEPSU.DLL (5095.2 kb/s)
- (average 9260.4 kb/s)
- putting file /usr/share/cups/drivers/ADOBEPSU.HLP as \W32X86/ADOBEPSU.HLP (8828.7 kb/s)
- (average 9247.1 kb/s)
-
- Running command: smbclient //localhost/print\$ -N -U'root%secret' -c 'mkdir WIN40;put
- /var/spool/cups/tmp/3cd1cc66376c0 WIN40/infotec_IS2027.PPD;put
- /usr/share/cups/drivers/ADFONTS.MFM WIN40/ADFONTS.MFM;put
- /usr/share/cups/drivers/ADOBEPS4.DRV WIN40/ADOBEPS4.DRV;put
- /usr/share/cups/drivers/ADOBEPS4.HLP WIN40/ADOBEPS4.HLP;put
- /usr/share/cups/drivers/DEFPRTR2.PPD WIN40/DEFPRTR2.PPD;put
- /usr/share/cups/drivers/ICONLIB.DLL WIN40/ICONLIB.DLL;put
- /usr/share/cups/drivers/PSMON.DLL WIN40/PSMON.DLL;'
- added interface ip=10.160.16.45 bcast=10.160.31.255 nmask=255.255.240.0
- added interface ip=192.168.182.1 bcast=192.168.182.255 nmask=255.255.255.0
- added interface ip=172.16.200.1 bcast=172.16.200.255 nmask=255.255.255.0
- Domain=[TUX-NET] OS=[Unix] Server=[Samba 2.2.3a.200204262025cvs]
- NT_STATUS_OBJECT_NAME_COLLISION making remote directory \WIN40
- putting file /var/spool/cups/tmp/3cd1cc66376c0 as \WIN40/infotec_IS2027.PPD (26091.5 kb/s)
- (average 26092.8 kb/s)
- putting file /usr/share/cups/drivers/ADFONTS.MFM as \WIN40/ADFONTS.MFM (11241.6 kb/s)
- (average 11812.9 kb/s)
- putting file /usr/share/cups/drivers/ADOBEPS4.DRV as \WIN40/ADOBEPS4.DRV (16640.6 kb/s)
- (average 14679.3 kb/s)
- putting file /usr/share/cups/drivers/ADOBEPS4.HLP as \WIN40/ADOBEPS4.HLP (11285.6 kb/s)
- (average 14281.5 kb/s)
- putting file /usr/share/cups/drivers/DEFPRTR2.PPD as \WIN40/DEFPRTR2.PPD (823.5 kb/s)
- (average 12944.0 kb/s)
- putting file /usr/share/cups/drivers/ICONLIB.DLL as \WIN40/ICONLIB.DLL (19226.2 kb/s)
- (average 13169.7 kb/s)
- putting file /usr/share/cups/drivers/PSMON.DLL as \WIN40/PSMON.DLL (18666.1 kb/s)
- (average 13266.7 kb/s)
-
- Running command: rpcclient localhost -N -U'root%secret' -c 'adddriver "Windows NT x86"
- "infotec_IS2027:ADOBEPS5.DLL:infotec_IS2027.PPD:ADOBEPSU.DLL:ADOBEPSU.HLP:NULL:RAW:NULL"'
- cmd = adddriver "Windows NT x86" "infotec_IS2027:ADOBEPS5.DLL:infotec_IS2027.PPD:ADOBEPSU.DLL:
- ADOBEPSU.HLP:NULL:RAW:NULL"
- Printer Driver infotec_IS2027 successfully installed.
-
- Running command: rpcclient localhost -N -U'root%secret' -c 'adddriver "Windows 4.0"
- "infotec_IS2027:ADOBEPS4.DRV:infotec_IS2027.PPD:NULL:ADOBEPS4.HLP:PSMON.DLL:RAW:
- ADFONTS.MFM,DEFPRTR2.PPD,ICONLIB.DLL"'
- cmd = adddriver "Windows 4.0" "infotec_IS2027:ADOBEPS4.DRV:infotec_IS2027.PPD:NULL:
- ADOBEPS4.HLP:PSMON.DLL:RAW:ADFONTS.MFM,DEFPRTR2.PPD,ICONLIB.DLL"
- Printer Driver infotec_IS2027 successfully installed.
-
- Running command: rpcclient localhost -N -U'root%secret'
- -c 'setdriver infotec_IS2027 infotec_IS2027'
- cmd = setdriver infotec_IS2027 infotec_IS2027
- Succesfully set infotec_IS2027 to driver infotec_IS2027.
-
- <SAMP
-CLASS="PROMPT"
->root# </SAMP
-></PRE
-></P
-><P
->If you look closely, you'll discover your root password was transfered unencrypted over
-the wire, so beware! Also, if you look further her, you'll discover error messages like
-<CODE
-CLASS="CONSTANT"
->NT_STATUS_OBJECT_NAME_COLLISION</CODE
-> in between. They occur, because
-the directories <TT
-CLASS="FILENAME"
->WIN40</TT
-> and <TT
-CLASS="FILENAME"
->W32X86</TT
-> already
-existed in the [print$] driver download share (from a previous driver
-installation). They are harmless here.</P
-><P
->Now your printer is prepared for the clients to use. From
-a client, browse to the CUPS/Samba server, open the "Printers"
-share, right-click on this printer and select "Install..." or
-"Connect..." (depending on the Windows version you use). Now their
-should be a new printer in your client's local "Printers" folder,
-named (in my case) "infotec_IS2027 on kdebitshop"</P
-><P
-><SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->NOTE: </I
-></SPAN
->
-<B
-CLASS="COMMAND"
->cupsaddsmb</B
-> will only reliably work i
-with CUPS version 1.1.15 or higher
-and Samba from 2.2.4. If it doesn't work, or if the automatic printer
-driver download to the clients doesn't succeed, you can still manually
-install the CUPS printer PPD on top of the Adobe PostScript driver on
-clients and then point the client's printer queue to the Samba printer
-share for connection, should you desire to use the CUPS networked
-PostScript RIP functions.</P
-></DIV
-></DIV
-><DIV
-CLASS="SECT1"
-><H1
-CLASS="SECT1"
-><A
-NAME="AEN2212"
->14.8. The CUPS Filter Chains</A
-></H1
-><P
->The following diagrams reveal how CUPS handles print jobs.</P
-><PRE
-CLASS="PROGRAMLISTING"
->#########################################################################
-#
-# CUPS in and of itself has this (general) filter chain (CAPITAL
-# letters are FILE-FORMATS or MIME types, other are filters (this is
-# true for pre-1.1.15 of pre-4.3 versions of CUPS and ESP PrintPro):
-#
-# <VAR
-CLASS="REPLACEABLE"
->SOMETHNG</VAR
->-FILEFORMAT
-# |
-# |
-# V
-# <VAR
-CLASS="REPLACEABLE"
->something</VAR
->tops
-# |
-# |
-# V
-# APPLICATION/POSTSCRIPT
-# |
-# |
-# V
-# pstops
-# |
-# |
-# V
-# APPLICATION/VND.CUPS-POSTSCRIPT
-# |
-# |
-# V
-# pstoraster # as shipped with CUPS, independent from any Ghostscipt
-# | # installation on the system
-# | (= "postscipt interpreter")
-# |
-# V
-# APPLICATION/VND.CUPS-RASTER
-# |
-# |
-# V
-# rasterto<VAR
-CLASS="REPLACEABLE"
->something</VAR
-> (f.e. Gimp-Print filters may be plugged in here)
-# | (= "raster driver")
-# |
-# V
-# SOMETHING-DEVICE-SPECIFIC
-# |
-# |
-# V
-# backend
-#
-#
-# ESP PrintPro has some enhanced "rasterto<VAR
-CLASS="REPLACEABLE"
->something</VAR
->" filters as compared to
-# CUPS, and also a somewhat improved "pstoraster" filter.
-#
-# NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to
-# CUPS and ESP PrintPro plug-in where rasterto<VAR
-CLASS="REPLACEABLE"
->something</VAR
-> is noted.
-#
-#########################################################################</PRE
-><PRE
-CLASS="PROGRAMLISTING"
->#########################################################################
-#
-# This is how "cupsomatic" comes into play:
-# =========================================
-#
-# <VAR
-CLASS="REPLACEABLE"
->SOMETHNG</VAR
->-FILEFORMAT
-# |
-# |
-# V
-# <VAR
-CLASS="REPLACEABLE"
->something</VAR
->tops
-# |
-# |
-# V
-# APPLICATION/POSTSCRIPT
-# |
-# |
-# V
-# pstops
-# |
-# |
-# V
-# APPLICATION/VND.CUPS-POSTSCRIPT ----------------+
-# | |
-# | V
-# V cupsomatic
-# pstoraster (constructs complicated
-# | (= "postscipt interpreter") Ghostscript commandline
-# | to let the file be
-# V processed by a
-# APPLICATION/VND.CUPS-RASTER "-sDEVICE=<VAR
-CLASS="REPLACEABLE"
->s.th.</VAR
->"
-# | call...)
-# | |
-# V |
-# rasterto<VAR
-CLASS="REPLACEABLE"
->something</VAR
-> V
-# | (= "raster driver") +-------------------------+
-# | | Ghostscript at work.... |
-# V | |
-# SOMETHING-DEVICE-SPECIFIC *-------------------------+
-# | |
-# | |
-# V |
-# backend &#62;------------------------------------+
-# |
-# |
-# V
-# THE PRINTER
-#
-#
-# Note, that cupsomatic "kidnaps" the printfile after the
-# "APPLICATION/VND.CUPS-POSTSCRPT" stage and deviates it through
-# the CUPS-external, systemwide Ghostscript installation, bypassing the
-# "pstoraster" filter (therefor also bypassing the CUPS-raster-drivers
-# "rasterto<VAR
-CLASS="REPLACEABLE"
->something</VAR
->", and hands the rasterized file directly to the CUPS
-# backend...
-#
-# cupsomatic is not made by the CUPS developers. It is an independent
-# contribution to printing development, made by people from
-# Linuxprinting.org. (see also http://www.cups.org/cups-help.html)
-#
-# NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to
-# CUPS and ESP PrintPro plug-in where rasterto<VAR
-CLASS="REPLACEABLE"
->something</VAR
-> is noted.
-#
-#########################################################################</PRE
-><PRE
-CLASS="PROGRAMLISTING"
->#########################################################################
-#
-# And this is how it works for ESP PrintPro from 4.3:
-# ===================================================
-#
-# <VAR
-CLASS="REPLACEABLE"
->SOMETHNG</VAR
->-FILEFORMAT
-# |
-# |
-# V
-# <VAR
-CLASS="REPLACEABLE"
->something</VAR
->tops
-# |
-# |
-# V
-# APPLICATION/POSTSCRIPT
-# |
-# |
-# V
-# pstops
-# |
-# |
-# V
-# APPLICATION/VND.CUPS-POSTSCRIPT
-# |
-# |
-# V
-# gsrip
-# | (= "postscipt interpreter")
-# |
-# V
-# APPLICATION/VND.CUPS-RASTER
-# |
-# |
-# V
-# rasterto<VAR
-CLASS="REPLACEABLE"
->something</VAR
-> (f.e. Gimp-Print filters may be plugged in here)
-# | (= "raster driver")
-# |
-# V
-# SOMETHING-DEVICE-SPECIFIC
-# |
-# |
-# V
-# backend
-#
-# NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to
-# CUPS and ESP PrintPro plug-in where rasterto<VAR
-CLASS="REPLACEABLE"
->something</VAR
-> is noted.
-#
-#########################################################################</PRE
-><PRE
-CLASS="PROGRAMLISTING"
->#########################################################################
-#
-# This is how "cupsomatic" would come into play with ESP PrintPro:
-# ================================================================
-#
-#
-# <VAR
-CLASS="REPLACEABLE"
->SOMETHNG</VAR
->-FILEFORMAT
-# |
-# |
-# V
-# <VAR
-CLASS="REPLACEABLE"
->something</VAR
->tops
-# |
-# |
-# V
-# APPLICATION/POSTSCRIPT
-# |
-# |
-# V
-# pstops
-# |
-# |
-# V
-# APPLICATION/VND.CUPS-POSTSCRIPT ----------------+
-# | |
-# | V
-# V cupsomatic
-# gsrip (constructs complicated
-# | (= "postscipt interpreter") Ghostscript commandline
-# | to let the file be
-# V processed by a
-# APPLICATION/VND.CUPS-RASTER "-sDEVICE=<VAR
-CLASS="REPLACEABLE"
->s.th.</VAR
->"
-# | call...)
-# | |
-# V |
-# rasterto<VAR
-CLASS="REPLACEABLE"
->something</VAR
-> V
-# | (= "raster driver") +-------------------------+
-# | | Ghostscript at work.... |
-# V | |
-# SOMETHING-DEVICE-SPECIFIC *-------------------------+
-# | |
-# | |
-# V |
-# backend &#62;------------------------------------+
-# |
-# |
-# V
-# THE PRINTER
-#
-# NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to
-# CUPS and ESP PrintPro plug-in where rasterto<VAR
-CLASS="REPLACEABLE"
->something</VAR
-> is noted.
-#
-#########################################################################</PRE
-><PRE
-CLASS="PROGRAMLISTING"
->#########################################################################
-#
-# And this is how it works for CUPS from 1.1.15:
-# ==============================================
-#
-# <VAR
-CLASS="REPLACEABLE"
->SOMETHNG</VAR
->-FILEFORMAT
-# |
-# |
-# V
-# <VAR
-CLASS="REPLACEABLE"
->something</VAR
->tops
-# |
-# |
-# V
-# APPLICATION/POSTSCRIPT
-# |
-# |
-# V
-# pstops
-# |
-# |
-# V
-# APPLICATION/VND.CUPS-POSTSCRIPT-----+
-# |
-# +------------------v------------------------------+
-# | Ghostscript |
-# | at work... |
-# | (with |
-# | "-sDEVICE=cups") |
-# | |
-# | (= "postscipt interpreter") |
-# | |
-# +------------------v------------------------------+
-# |
-# |
-# APPLICATION/VND.CUPS-RASTER &#62;-------+
-# |
-# |
-# V
-# rasterto<VAR
-CLASS="REPLACEABLE"
->something</VAR
->
-# | (= "raster driver")
-# |
-# V
-# SOMETHING-DEVICE-SPECIFIC
-# |
-# |
-# V
-# backend
-#
-#
-# NOTE: since version 1.1.15 CUPS "outsourced" the pstoraster process to
-# Ghostscript. GNU Ghostscript needs to be patched to handle the
-# CUPS requirement; ESP Ghostscript has this builtin. In any case,
-# "gs -h" needs to show up a "cups" device. pstoraster is now a
-# calling an appropriate "gs -sDEVICE=cups..." commandline to do
-# the job. It will output "application/vnd.cup-raster", which will
-# be finally processed by a CUPS raster driver "rasterto<VAR
-CLASS="REPLACEABLE"
->something</VAR
->"
-# Note the difference to "cupsomatic", which will *not* output
-# CUPS-raster, but a final version of the printfile, ready to be
-# sent to the printer. cupsomatic also doesn't use the "cups"
-# devicemode in Ghostscript, but one of the classical devicemodes....
-#
-# NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to
-# CUPS and ESP PrintPro plug-in where rasterto<VAR
-CLASS="REPLACEABLE"
->something</VAR
-> is noted.
-#
-#########################################################################</PRE
-><PRE
-CLASS="PROGRAMLISTING"
->#########################################################################
-#
-# And this is how it works for CUPS from 1.1.15, with cupsomatic included:
-# ========================================================================
-#
-# <VAR
-CLASS="REPLACEABLE"
->SOMETHNG</VAR
->-FILEFORMAT
-# |
-# |
-# V
-# <VAR
-CLASS="REPLACEABLE"
->something</VAR
->tops
-# |
-# |
-# V
-# APPLICATION/POSTSCRIPT
-# |
-# |
-# V
-# pstops
-# |
-# |
-# V
-# APPLICATION/VND.CUPS-POSTSCRIPT-----+
-# |
-# +------------------v------------------------------+
-# | Ghostscript . Ghostscript at work.... |
-# | at work... . (with "-sDEVICE= |
-# | (with . <VAR
-CLASS="REPLACEABLE"
->s.th.</VAR
->" |
-# | "-sDEVICE=cups") . |
-# | . |
-# | (CUPS standard) . (cupsomatic) |
-# | . |
-# | (= "postscript interpreter") |
-# | . |
-# +------------------v--------------v---------------+
-# | |
-# | |
-# APPLICATION/VND.CUPS-RASTER &#62;-------+ |
-# | |
-# | |
-# V |
-# rasterto<VAR
-CLASS="REPLACEABLE"
->something</VAR
-> |
-# | (= "raster driver") |
-# | |
-# V |
-# SOMETHING-DEVICE-SPECIFIC &#62;------------------------+
-# |
-# |
-# V
-# backend
-#
-#
-# NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to
-# CUPS and ESP PrintPro plug-in where rasterto<VAR
-CLASS="REPLACEABLE"
->something</VAR
-> is noted.
-#
-##########################################################################</PRE
-></DIV
-><DIV
-CLASS="SECT1"
-><H1
-CLASS="SECT1"
-><A
-NAME="AEN2251"
->14.9. CUPS Print Drivers and Devices</A
-></H1
-><P
->CUPS ships with good support for HP LaserJet type printers. You can install
-the driver as follows:
-
-<P
-></P
-><UL
-><LI
-><P
-> lpadmin -p laserjet4plus -v parallel:/dev/lp0 -E -m laserjet.ppd
- </P
-></LI
-></UL
->
-
-(The "-m" switch will retrieve the "laserjet.ppd" from the standard repository
-for not-yet-installed-PPDs, which CUPS typically stores in
-<TT
-CLASS="FILENAME"
->/usr/share/cups/model</TT
->. Alternatively, you may use
-"-P /absolute/filesystem/path/to/where/there/is/PPD/your.ppd").</P
-><DIV
-CLASS="SECT2"
-><H2
-CLASS="SECT2"
-><A
-NAME="AEN2258"
->14.9.1. Further printing steps</A
-></H2
-><P
->Always also consult the database on linuxprinting.org for all recommendations
-about which driver is best used for each printer:</P
-><P
-><A
-HREF="http://www.linuxprinting.org/printer_list.cgi"
-TARGET="_top"
->http://www.linuxprinting.org/printer_list.cgi</A
-></P
-><P
->There select your model and click on "Show". You'll arrive at a page listing
-all drivers working with your model. There will always be *one*
-<SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->recommended</I
-></SPAN
-> one. Try this one first. In your case
-("HP LaserJet 4 Plus"), you'll arrive here:</P
-><P
-><A
-HREF="http://www.linuxprinting.org/show_printer.cgi?recnum=75104"
-TARGET="_top"
->http://www.linuxprinting.org/show_printer.cgi?recnum=75104</A
-></P
-><P
->The recommended driver is "ljet4". It has a link to the page for the ljet4
-driver too:</P
-><P
-><A
-HREF="http://www.linuxprinting.org/show_driver.cgi?driver=ljet4"
-TARGET="_top"
->http://www.linuxprinting.org/show_driver.cgi?driver=ljet4</A
-></P
-><P
->On the driver's page, you'll find important and detailed info about how to use
-that driver within the various available spoolers. You can generate a PPD for
-CUPS. The PPD contains all the info about how to use your model and the driver;
-this is, once installed, working transparently for the user -- you'll only
-need to choose resolution, paper size etc. from the web-based menu or from
-the print dialog GUI or from the commandline...</P
-><P
->On the driver's page, choose to use the "PPD-O-Matic" online PPD generator
-program. Select your model and click "Generate PPD file". When you safe the
-appearing ASCII text file, don't use "cut'n'past" (as it could possiblly corrupt
-line endings and tabs), but use "Save as..." in your browser's menu. Save it
-at "/some/path/on/your/filesystem/somewhere/my-name-for-my-printer.ppd"</P
-><P
->Then install the printer:</P
-><P
-><PRE
-CLASS="PROGRAMLISTING"
-> "lpadmin -p laserjet4plus -v parallel:/dev/lp0 -E \
- -P /some/path/on/your/filesystem/somewhere/my-name-for-my-printer.ppd"</PRE
-></P
-><P
->Note, that for all the "Foomatic-PPDs" from Linuxprinting.org, you also need
-a special "CUPS filter" named "cupsomatic". Get the latest version of
-"cupsomatic" from:</P
-><P
-><A
-HREF="http://www.linuxprinting.org/cupsomatic"
-TARGET="_top"
->http://www.linuxprinting.org/cupsomatic</A
-></P
-><P
->This needs to be copied to <TT
-CLASS="FILENAME"
->/usr/lib/cups/filter/cupsomatic</TT
->
-and be made world executable. This filter is needed to read and act upon the
-specially encoded Foomatic comments, embedded in the printfile, which in turn
-are used to construct (transparently for you, the user) the complicated
-ghostscript command line needed for your printer/driver combo.</P
-><P
->You can have a look at all the options for the Ghostscript commandline supported
-by your printer and the ljet4 driver by going to the section "Execution details",
-selecting your model (Laserjet 4 Plus) and clicking on "Show execution details".
-This will bring up this web page:</P
-><P
-><A
-HREF="http://www.linuxprinting.org/execution.cgi?driver=ljet4&printer=75104&.submit=Show+execution+details"
-TARGET="_top"
->http://www.linuxprinting.org/execution.cgi?driver=ljet4&#38;printer=75104&#38;.submit=Show+execution+details</A
-></P
-><P
->The ingenious thing is that the database is kept current. If there
-is a bug fix and an improvement somewhere in the database, you will
-always get the most current and stable and feature-rich driver by following
-the steps described above.</P
-><DIV
-CLASS="NOTE"
-><P
-></P
-><TABLE
-CLASS="NOTE"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->Till Kamppeter from MandrakeSoft is doing an excellent job here that too few
-people are aware of. (So if you use it often, please send him a note showing
-your appreciation).</P
-></TD
-></TR
-></TABLE
-></DIV
-><P
->The latest and greatest improvement now is support for "custom page sizes"
-for all those printers which support it.</P
-><P
->"cupsomatic" is documented here:</P
-><P
-><A
-HREF="http://www.linuxprinting.org/cups-doc.html"
-TARGET="_top"
->http://www.linuxprinting.org/cups-doc.html</A
-></P
-><P
->More printing tutorial info may be found here:</P
-><P
-><A
-HREF="http://www.linuxprinting.org/kpfeifle/LinuxKongress2002/Tutorial/"
-TARGET="_top"
->http://www.linuxprinting.org/kpfeifle/LinuxKongress2002/Tutorial/</A
-></P
-><P
->Note, that *all* the Foomatic drivers listed on Linuxprinting.org (now
-approaching the "all-time high" number of 1.000 for the supported models)
-are using a special filtering chain involving Ghostscript, as described
-in this document.</P
-><P
->Summary - You need:</P
-><P
-><P
-></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
->A "foomatic+<VAR
-CLASS="REPLACEABLE"
->something</VAR
->" PPD is not enough to print with CUPS (but it is *one* important component)</TD
-></TR
-><TR
-><TD
->The "cupsomatic" filter script (Perl) in <TT
-CLASS="FILENAME"
->/usr/lib/cups/filters/</TT
-></TD
-></TR
-><TR
-><TD
->Perl to make cupsomatic run</TD
-></TR
-><TR
-><TD
->Ghostscript (because it is called and controlled by the PPD/cupsomatic combo in a way to fit your printermodel/driver combo.</TD
-></TR
-><TR
-><TD
->Ghostscript *must*, depending on the driver/model, contain support for a certain "device" (as shown by "gs -h")</TD
-></TR
-></TBODY
-></TABLE
-><P
-></P
-></P
-><P
->In the case of the "hpijs" driver, you need a Ghostscript version, which
-has "ijs" amongst its supported devices in "gs -h". In the case of
-"hpijs+foomatic", a valid ghostscript commandline would be reading like this:</P
-><P
-><PRE
-CLASS="PROGRAMLISTING"
-> gs -q -dBATCH -dPARANOIDSAFER -dQUIET -dNOPAUSE -sDEVICE=ijs \
- -sIjsServer=hpijs<VAR
-CLASS="REPLACEABLE"
->PageSize</VAR
-> -dDuplex=<VAR
-CLASS="REPLACEABLE"
->Duplex</VAR
-> <VAR
-CLASS="REPLACEABLE"
->Model</VAR
-> \
- -r<VAR
-CLASS="REPLACEABLE"
->Resolution</VAR
->,PS:MediaPosition=<VAR
-CLASS="REPLACEABLE"
->InputSlot</VAR
-> -dIjsUseOutputFD \
- -sOutputFile=- -</PRE
-></P
-><DIV
-CLASS="NOTE"
-><P
-></P
-><TABLE
-CLASS="NOTE"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->Note, that with CUPS and the "hpijs+foomatic" PPD (plus Perl and cupsomatic)
-you don't need to remember this. You can choose the available print options
-thru a GUI print command (like "glp" from ESP's commercially supported
-PrintPro software, or KDE's "kprinter", or GNOME's "gtklp" or the independent
-"xpp") or the CUPS web interface via human-readable drop-down selection
-menus.</P
-></TD
-></TR
-></TABLE
-></DIV
-><P
->If you use "ESP Ghostscript" (also under the GPL, provided by Easy Software
-Products, the makers of CUPS, downloadable from
-<A
-HREF="http://www.cups.org/software.html"
-TARGET="_top"
->http://www.cups.org/software.html</A
->,
-co-maintained by the developers of linuxprinting.org), you are guaranteed to
-have in use the most uptodate, bug-fixed, enhanced and stable version of a Free
-Ghostscript. It contains support for ~300 devices, whereas plain vanilla
-GNU Ghostscript 7.05 only has ~200.</P
-><P
->If you print only one CUPS test page, from the web interface and when you try to
-print a windows test page, it acts like the job was never sent:
-
-<P
-></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
->Can you print "standard" jobs from the CUPS machine?</TD
-></TR
-><TR
-><TD
->Are the jobs from Windows visible in the Web interface on CUPS (http://localhost:631/)?</TD
-></TR
-><TR
-><TD
-><SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->Most important:</I
-></SPAN
-> What kind of printer driver are you using on the Windows clients?</TD
-></TR
-></TBODY
-></TABLE
-><P
-></P
->
-
-You can try to get a more detailed debugging info by setting "LogLevel debug" in
-<TT
-CLASS="FILENAME"
->/etc/cups/cupsd.conf</TT
->, re-start cupsd and investigate <TT
-CLASS="FILENAME"
->/var/log/cups/error_log</TT
->
-for the whereabouts of your Windows-originating printjobs:</P
-><P
-></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
->what does the "auto-typing" line say? which is the "MIME type" CUPS thinks is arriving from the Windows clients?</TD
-></TR
-><TR
-><TD
->are there "filter" available for this MIME type?</TD
-></TR
-><TR
-><TD
->are there "filter rules" defined in "/etc/cups/mime.convs" for this MIME type?</TD
-></TR
-></TBODY
-></TABLE
-><P
-></P
-></DIV
-></DIV
-><DIV
-CLASS="SECT1"
-><H1
-CLASS="SECT1"
-><A
-NAME="AEN2328"
->14.10. Limiting the number of pages users can print</A
-></H1
-><P
->The feature you want is dependent on the real print subsystem you're using.
-Samba's part is always to receive the job files from the clients (filtered
-*or* unfiltered) and hand it over to this printing subsystem.</P
-><P
->Of course one could "hack" things with one's own scripts.</P
-><P
->But there is CUPS (Common Unix Printing System). CUPS supports "quotas".
-Quotas can be based on sizes of jobs or on the number of pages or both,
-and are spanning any time period you want.</P
-><P
->This is an example command how root would set a print quota in CUPS,
-assuming an existing printer named "quotaprinter":</P
-><PRE
-CLASS="PROGRAMLISTING"
-> lpadmin -p quotaprinter -o job-quota-period=604800 -o job-k-limit=1024 \
- -o job-page-limit=100</PRE
-><P
->This would limit every single user to print 100 pages or 1024 KB of
-data (whichever comes first) within the last 604.800 seconds ( = 1 week).</P
-><P
->For CUPS to count correctly, the printfile needs to pass the CUPS "pstops" filter,
-otherwise it uses a "dummy" count of "1". Some printfiles don't pass it
-(eg: image files) but then those are mostly 1 page jobs anyway. This also means,
-proprietary drivers for the target printer running on the client computers and
-CUPS/Samba then spooling these files as "raw" (i.e. leaving them untouched, not
-filtering them), will be counted as "1-pagers" too!</P
-><P
->You need to send PostScript from the clients (i.e. run a PostScript driver there)
-for having the chance to get accounting done. If the printer is a non-PostScript model,
-you need to let CUPS do the job to convert the file to a print-ready format for the
-target printer. This will be working for currently ~1.000 different printer models, see</P
-><PRE
-CLASS="PROGRAMLISTING"
-> http://www.linuxprinting.org/printer_list.cgi</PRE
-><P
->Before CUPS-1.1.16 your only option was to use the Adobe PostScript
-Driver on the Windows clients. The output of this driver was not always
-passed thru the "pstops" filter on the CUPS/Samba side, and therefor was
-not counted correctly (the reason is that it often --- depending on the
-"PPD" being used --- did write a "PJL"-header in front of the real
-PostScript which made CUPS to skip the pstops and go directy to
-the "pstoraster" stage).</P
-><P
->From CUPS-1.1.16 onward you can use the "CUPS PostScript Driver
-for Windows NT/2K/XP clients" (it is tagged in the download area of
-http://www.cups.org/ as the "cups-samba-1.1.16.tar.gz" package).
-It is *not* working for Win9x/ME clients. But it:</P
-><P
-></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
->it guarantees to not write an PJL-header</TD
-></TR
-><TR
-><TD
->it guarantees to still read and support all PJL-options named in the driver PPD with its own means</TD
-></TR
-><TR
-><TD
->it guarantees the file going thru the "pstops" filter on the CUPS/Samba server</TD
-></TR
-><TR
-><TD
->it guarantees to page-count correctly the printfile</TD
-></TR
-></TBODY
-></TABLE
-><P
-></P
-><P
->You can read more about the setup of this combination in the
-manpage for "cupsaddsmb" (only present with CUPS installed, only
-current with CUPS 1.1.16).</P
-><P
->These are the items CUPS logs in the "page_log" for every single *page* of a job:</P
-><P
-><P
-></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
->Printer name</TD
-></TR
-><TR
-><TD
->User name</TD
-></TR
-><TR
-><TD
->Job ID</TD
-></TR
-><TR
-><TD
->Time of printing</TD
-></TR
-><TR
-><TD
->the page number</TD
-></TR
-><TR
-><TD
->the number of copies</TD
-></TR
-><TR
-><TD
->a billing info string (optional)</TD
-></TR
-></TBODY
-></TABLE
-><P
-></P
-></P
-><P
->Here is an extract of my CUPS server's page_log file to illustrate
-the format and included items:</P
-><P
-><SAMP
-CLASS="COMPUTEROUTPUT"
-> infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 1 2 #marketing
- infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 2 2 #marketing
- infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 3 2 #marketing
- infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 4 2 #marketing
- infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 5 2 #marketing
- infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 6 2 #marketing</SAMP
-></P
-><P
->This was Job ID "40", printed on "infotec_IS2027" by user "kurt", a 6-page job
-printed in 2 copies and billed to "#marketing"...</P
-><P
->What flaws or shortcomings are there?</P
-><P
-></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
->the ones named above</TD
-></TR
-><TR
-><TD
-> CUPS really counts the job pages being *processsed in software*
- (going thru the "RIP") rather than the physical sheets successfully
- leaving the printing device -- if there is a jam while printing
- the 5th sheet out of 1000 and the job is aborted by the printer,
- the "page count" will still show the figure of 1000 for that job
- </TD
-></TR
-><TR
-><TD
-> all quotas are the same for all users (no flexibility to give the
- boss a higher quota than the clerk) no support for groups
- </TD
-></TR
-><TR
-><TD
-> no means to read out the current balance or "used-up" number of current quota
- </TD
-></TR
-><TR
-><TD
-> a user having used up 99 sheets of 100 quota will still be able to send and print a 1.000 sheet job
- </TD
-></TR
-><TR
-><TD
-> a user being denied a job because of a filled-up quota doesn't get a meaningful
- error message from CUPS other than "client-error-not-possible".
- </TD
-></TR
-></TBODY
-></TABLE
-><P
-></P
-><P
->But this is the best system out there currently. And there are
-huge improvements under development:</P
-><P
-></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
->page counting will go into the "backends" (these talk
- directly to the printer and will increase the count in sync with the
- actual printing process -- a jam at the 5th sheet will lead to a stop in the counting)</TD
-></TR
-><TR
-><TD
->quotas will be handled more flexibly</TD
-></TR
-><TR
-><TD
->probably there will be support for users to inquire their "accounts" in advance</TD
-></TR
-><TR
-><TD
->probably there will be support for some other tools around this topic</TD
-></TR
-></TBODY
-></TABLE
-><P
-></P
-><P
->Other than the current stage of the CUPS development, I don't
-know any other ready-to-use tool which you could consider.</P
-><P
->You can download the driver files from
-<A
-HREF="http://www.cups.org/software.html"
-TARGET="_top"
->http://www.cups.org/software.html</A
->.
-It is a separate package from the CUPS base software files, tagged as "CUPS 1.1.16
-Windows NT/2k/XP Printer Driver for SAMBA (tar.gz, 192k)". The filename to
-download is "cups-samba-1.1.16.tar.gz". Upon untar-/unzip-ping it will reveal
-the files:</P
-><P
-> <SAMP
-CLASS="COMPUTEROUTPUT"
-> cups-samba.install
- cups-samba.license
- cups-samba.readme
- cups-samba.remove
- cups-samba.ss
- </SAMP
->
- </P
-><P
->These have been packaged with the ESP meta packager software "EPM". The
-*.install and *.remove files are simple shell script, which untars the
-*.ss (which is nothing else than a tar-archive) and puts its contents
-into <TT
-CLASS="FILENAME"
->/usr/share/cups/drivers/</TT
->. Its contents are 3 files:</P
-><P
-> <SAMP
-CLASS="COMPUTEROUTPUT"
-> cupsdrvr.dll
- cupsui.dll
- cups.hlp
- </SAMP
->
- </P
-><DIV
-CLASS="CAUTION"
-><P
-></P
-><TABLE
-CLASS="CAUTION"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/caution.gif"
-HSPACE="5"
-ALT="Caution"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->Due to a bug one CUPS release puts the <TT
-CLASS="FILENAME"
->cups.hlp</TT
->
-into <TT
-CLASS="FILENAME"
->/usr/share/drivers/</TT
-> instead of
-<TT
-CLASS="FILENAME"
->/usr/share/cups/drivers/</TT
->. To work around this, copy/move
-the file after running the "./cups-samba.install" script manually to the right place:</P
-><P
-> <KBD
-CLASS="USERINPUT"
-> cp /usr/share/drivers/cups.hlp /usr/share/cups/drivers/
- </KBD
->
- </P
-></TD
-></TR
-></TABLE
-></DIV
-><DIV
-CLASS="NOTE"
-><P
-></P
-><TABLE
-CLASS="NOTE"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->This new CUPS PostScript driver is currently binary-only, but free
-no source code is provided (yet). The reason is this: it has
-been developed with the help of the Microsoft Driver Developer Kit (DDK)
-and compiled with Microsoft Visual Studio 6. It is not clear to the driver
-developers if they are allowed to distribute the whole of the source code
-as Free Software. However, they will likely release the "diff" in source
-code under the GPL, so anybody with a license of Visual Studio and a DDK
-will be able to compile for him/herself.</P
-><P
->Once you have run the install script (and possibly manually moved the
-"cups.hlp" file to "/usr/share/cups/drivers/"), the driver is ready to be
-put into Samba's [print$] share (which often maps to "/etc/samba/drivers/"
-and contains a subdir tree with WIN40 and W32X86 branches), by running
-"cupsaddsmb" (see also "man cupsaddsmb" for CUPS 1.1.16). [Don't forget to
-put root into the smbpasswd file by running "smbpasswd" should you run
-this whole procedure for the first time.] Once the driver files are in the
-[print$] share, they are ready to be downloaded and installed by the
-Win NT/2k/XP clients.</P
-></TD
-></TR
-></TABLE
-></DIV
-><DIV
-CLASS="NOTE"
-><P
-></P
-><TABLE
-CLASS="NOTE"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
-> Win 9x/ME clients won't work with this driver. For these you'd
- still need to use the ADOBE*.* drivers as previously.
- </P
-></TD
-></TR
-></TABLE
-></DIV
-><DIV
-CLASS="NOTE"
-><P
-></P
-><TABLE
-CLASS="NOTE"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
-> It is not harming if you've still the ADOBE*.* driver files from
- previous installations in the "/usr/share/cups/drivers/" directory.
- The new cupsaddsmb (from 1.1.16) will automatically use the
- "newest" installed driver (which here then is the CUPS drivers).
- </P
-></TD
-></TR
-></TABLE
-></DIV
-><DIV
-CLASS="NOTE"
-><P
-></P
-><TABLE
-CLASS="NOTE"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
-> Should your Win clients have had the old ADOBE*.* files and the
- Adobe PostScript drivers installed, the download and installation
- of the new CUPS PostScript driver for Windows NT/2k/XP will fail
- at first.
- </P
-><P
-> It is not enough to "delete" the printer (as the driver files
- will still be kept by the clients and re-used if you try to
- re-install the printer). To really get rid of the Adobe driver
- files on the clients, open the "Printers" folder (possibly via
- "Start --&#62; Settings --&#62; Control Panel --&#62; Printers"), right-click
- onto the folder background and select "Server Properties". A
- new dialog opens; select the "Drivers" tab; on the list select
- the driver you want to delete and click on the "Delete" button.
- (This will only work if there is no single printer left which
- uses that particular driver -- you need to "delete" all printers
- using this driver in the "Printers" folder first.)
- </P
-></TD
-></TR
-></TABLE
-></DIV
-><DIV
-CLASS="NOTE"
-><P
-></P
-><TABLE
-CLASS="NOTE"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
-> Once you have successfully downloaded the CUPS PostScript driver
- to a client, you can easily switch all printers to this one
- by proceeding as described elsewhere in the "Samba HOWTO
- Collection" to change a driver for an existing printer.
- </P
-></TD
-></TR
-></TABLE
-></DIV
-><P
->What are the benefits with the "CUPS PostScript driver for Windows NT/2k/XP"
-as compared to the Adobe drivers?</P
-><P
-><P
-></P
-><UL
-><LI
-><P
-> no hassle with the Adobe EULA
- </P
-></LI
-><LI
-><P
-> no hassle with the question "where do I get the ADOBE*.* driver files from?"
- </P
-></LI
-><LI
-><P
-> the Adobe drivers (depending on the printer PPD associated with them)
- often put a PJL header in front of the core PostScript part of the print
- file (thus the file starts with "<VAR
-CLASS="REPLACEABLE"
->1B</VAR
->%-12345X" or "<VAR
-CLASS="REPLACEABLE"
->escape</VAR
->%-12345X"
- instead of "%!PS"). This leads to the CUPS daemon autotyping the
- arriving file as a print-ready file, not requiring a pass thru the
- "pstops" filter (to speak more technical, it is not regarded as the
- generic MIME type "application/postscript", but as the more special
- MIME type "application/cups.vnd-postscript"), which therefore also
- leads to the page accounting in "/var/log/cups/page_log" not receiving
- the exact mumber of pages; instead the dummy page number of "1" is
- logged in a standard setup)
- </P
-></LI
-><LI
-><P
-> the Adobe driver has more options to "mis-configure" the PostScript
- generated by it (like setting it inadvertedly to "Optimize for Speed",
- instead of "Optimize for Portability", which could lead to CUPS being
- unable to process it)
- </P
-></LI
-><LI
-><P
-> the CUPS PostScript driver output sent by Windows clients to the CUPS
- server will be guaranteed to be auto-typed as generic MIME type
- "application/postscript", thusly passing thru the CUPS "pstops" filter
- and logging the correct number of pages in the page_log for accounting
- and quota purposes
- </P
-></LI
-><LI
-><P
-> the CUPS PostScript driver supports the sending of additional print
- options by the Win NT/2k/XP clients, such as naming the CUPS standard
- banner pages (or the custom ones, should they be installed at the time
- of driver download), using the CUPS "page-label" option, setting a
- job-priority and setting the scheduled time of printing (with the option
- to support additional useful IPP job attributes in the future).
- </P
-></LI
-><LI
-><P
-> the CUPS PostScript driver supports the inclusion of the new
- "*cupsJobTicket" comments at the beginnig of the PostScript file (which
- could be used in the future for all sort of beneficial extensions on
- the CUPS side, but which will not disturb any other application as those
- will regard it as a comment and simply ignore it).
- </P
-></LI
-><LI
-><P
-> the CUPS PostScript driver will be the heart of the fully fledged CUPS
- IPP client for Windows NT/2k/XP to be released soon (probably alongside
- the first Beta release for CUPS 1.2).
- </P
-></LI
-></UL
-></P
-></DIV
-><DIV
-CLASS="SECT1"
-><H1
-CLASS="SECT1"
-><A
-NAME="AEN2424"
->14.11. Advanced Postscript Printing from MS Windows</A
-></H1
-><P
->Let the Windows Clients use a PostScript driver to deliver poistscript to
-the samba print server (just like any Linux or Unix Client would also use
-PostScript to send to the server)</P
-><P
->Make the Unix printing subsystem to which Samba sends the job convert the
-incoming PostScript files to the native print format of the target printers
-(would be PCL if you have an HP printer)</P
-><P
->Now if you are afraid that this would just mean using a *Generic* PostScript
-driver for the clients that has no Simplex/Duplex selection, and no paper tray
-choice, but you need them to be able to set up print jobs, with all the bells
-and whistles of your printers:-</P
-><P
-></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
->Not possible with traditional spooling systems</TD
-></TR
-><TR
-><TD
-> But perfectly supported by CUPS (which uses "PPD" files to
- describe how to control the print options for PostScript and
- non-PostScript devices alike...
- </TD
-></TR
-></TBODY
-></TABLE
-><P
-></P
-><P
->CUPS PPDs are working perfectly on Windows clients who use Adobe PostScript
-drivers (or the new CUPS PostScript driver for Windows NT/2K/XP). Clients can use
-them to setup the job to their liking and CUPS will use the received job options
-to make the (PCL-, ESC/P- or PostScript-) printer behave as required.</P
-><P
->If you want to have the additional benefit of page count logging and accounting
-then the CUPS PostScript driver is the best choice (better than the Adobe one).</P
-><P
->If you want to make the drivers downloadable for the clients then "cupsaddsmb" is
-your friend. It will setup the [print$] share on the Samba host to be ready to serve
-the clients for a "point and print" driver installation.</P
-><DIV
-CLASS="WARNING"
-><P
-></P
-><TABLE
-CLASS="WARNING"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/warning.gif"
-HSPACE="5"
-ALT="Warning"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->What strings are attached?</P
-></TD
-></TR
-></TABLE
-></DIV
-><P
->There are some. But, given the sheer CPU power you can buy nowadays,
-these can be overcome easily. The strings:</P
-><P
->Well, if the CUPS/Samba side will have to print to many printers serving many users,
-you probably will need to set up a second server (which can do automatic load balancing
-with the first one, plus a degree of fail-over mechanism). Converting the incoming
-PostScript jobs, "interpreting" them for non-PostScript printers, amounts to the work
-of a "RIP" (Raster Image Processor) done in software. This requires more CPU and RAM
-than for the mere "raw spooling" task your current setup is solving. It all depends
-on the avarage and peak printing load the server should be able to handle.</P
-></DIV
-><DIV
-CLASS="SECT1"
-><H1
-CLASS="SECT1"
-><A
-NAME="AEN2439"
->14.12. Auto-Deletion of CUPS spool files</A
-></H1
-><P
->Samba print files pass thru two "spool" directories. One the incoming directory
-managed by Samba, (set eg: in the <B
-CLASS="COMMAND"
->path = /var/spool/samba</B
-> directive in the [printers]
-section of <TT
-CLASS="FILENAME"
->smb.conf</TT
->). Second is the spool directory of your UNIX print subsystem.
-For CUPS it is normally "/var/spool/cups/", as set by the cupsd.conf directive
-"RequestRoot /var/spool/cups".</P
-><P
->I am not sure, which one of your directories keeps the files. From what you say,
-it is most likely the Samba part.</P
-><P
->For the CUPS part, you may want to consult:</P
-><P
-></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
->http://localhost:631/sam.html#PreserveJobFiles</TD
-></TR
-><TR
-><TD
->http://localhost:631/sam.html#PreserveJobHistory</TD
-></TR
-><TR
-><TD
->http://localhost:631/sam.html#MaxJobs</TD
-></TR
-></TBODY
-></TABLE
-><P
-></P
-><P
->There are the settings described for your CUPS daemon, which could lead to completed
-job files not being deleted.</P
-><P
->"PreserveJobHistory Yes" -- keeps some details of jobs in
-cupsd's mind (well it keeps the "c12345", "c12346" etc. files
-in the CUPS spool directory, which do a similar job as the
-old-fashioned BSD-LPD control files). This is set to "Yes"
-as a default.</P
-><P
->"PreserveJobFiles Yes" -- keeps the job files themselves in
-cupsd's mind (well it keeps the "d12345", "d12346" etc. files
-in the CUPS spool directory...). This is set to "No" as the
-CUPS default.</P
-><P
->"MaxJobs 500" -- this directive controls the maximum number
-of jobs that are kept in memory. Once the number of jobs
-reaches the limit, the oldest completed job is automatically
-purged from the system to make room for the new one. If all
-of the known jobs are still pending or active then the new
-job will be rejected. Setting the maximum to 0 disables this
-functionality. The default setting is 0.</P
-><P
->(There are also additional settings for "MaxJobsPerUser" and
-"MaxJobsPerPrinter"...)</P
-><P
->For everything to work as announced, you need to have three things:</P
-><P
-></P
-><TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
-> a Samba-<SPAN
-CLASS="APPLICATION"
->smbd</SPAN
-> which is compiled against "libcups" (Check on Linux by running <KBD
-CLASS="USERINPUT"
->ldd `which smbd`</KBD
->)
- </TD
-></TR
-><TR
-><TD
-> a Samba-<TT
-CLASS="FILENAME"
->smb.conf</TT
-> setting of <B
-CLASS="COMMAND"
->printing = cups</B
->
- </TD
-></TR
-><TR
-><TD
-> another Samba-<TT
-CLASS="FILENAME"
->smb.conf</TT
-> setting of <B
-CLASS="COMMAND"
->printcap = cups</B
->
- </TD
-></TR
-></TBODY
-></TABLE
-><P
-></P
-><DIV
-CLASS="NOTE"
-><P
-></P
-><TABLE
-CLASS="NOTE"
-WIDTH="100%"
-BORDER="0"
-><TR
-><TD
-WIDTH="25"
-ALIGN="CENTER"
-VALIGN="TOP"
-><IMG
-SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif"
-HSPACE="5"
-ALT="Note"></TD
-><TD
-ALIGN="LEFT"
-VALIGN="TOP"
-><P
->Note, that in this case all other manually set printing-related
-commands (like "print command", "lpq command", "lprm command",
-"lppause command" or "lpresume command") are ignored and they
-should normally have no influence what-so-ever on your printing.</P
-></TD
-></TR
-></TABLE
-></DIV
-><P
->If you want to do things manually, replace the "printing = cups"
-by "printing = bsd". Then your manually set commands may work
-(haven't tested this), and a "print command = lp -d %P %s; rm %s"
-may do what you need.</P
-><P
->You forgot to mention the CUPS version you're using. If you did
-set things up as described in the man pages, then the Samba
-spool files should be deleted. Otherwise it may be a bug. On
-the CUPS side, you can control the behaviour as described
-above.</P
-><P
->If you have more problems, post the output of these commands:</P
-><P
-><KBD
-CLASS="USERINPUT"
-> grep -v ^# /etc/cups/cupsd.conf | grep -v ^$
- grep -v ^# /etc/samba/smb.conf | grep -v ^$ | grep -v "^;"</KBD
-></P
-><P
->(adapt paths as needed). These commands sanitize the files
-and cut out the empty lines and lines with comments, providing
-the "naked settings" in a compact way.</P
-></DIV
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="printing.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="samba-howto-collection.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="winbind.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Printing Support</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="optional.html"
-ACCESSKEY="U"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Unified Logons between Windows NT and UNIX using Winbind</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
-> \ No newline at end of file