diff options
Diffstat (limited to 'docs/docbook/projdoc/CUPS-printing.sgml')
| -rw-r--r-- | docs/docbook/projdoc/CUPS-printing.sgml | 843 |
1 files changed, 508 insertions, 335 deletions
diff --git a/docs/docbook/projdoc/CUPS-printing.sgml b/docs/docbook/projdoc/CUPS-printing.sgml index bfd23e3c6c..a932127d94 100644 --- a/docs/docbook/projdoc/CUPS-printing.sgml +++ b/docs/docbook/projdoc/CUPS-printing.sgml @@ -64,13 +64,12 @@ do any print file format conversion work. <para> The CUPS files that need to be correctly set for RAW mode printers to work are: -<itemlist> - <listitem><para><filename>/etc/cups/mime.types</filename><para></listitem) - +<itemizedlist> + <listitem><para><filename>/etc/cups/mime.types</filename><para></listitem> <listitem><para><filename>/etc/cups/mime.convs</filename><para></listitem> -</itemlist> +</itemizedlist> -Both contain entries that must be uncommented to allow <empasis>RAW</emphasis> mode +Both contain entries that must be uncommented to allow <emphasis>RAW</emphasis> mode operation. </para> @@ -78,17 +77,17 @@ operation. Firstly, to enable CUPS based printing from Samba the following options must be enabled in your smb.conf file [globals] section: -<itemlist> +<itemizedlist> <listitem><para>printing = CUPS</para></listitem> <listitem><para>printcap = CUPS</para></listitem> -</itemlist> +</itemizedlist> When these parameters are specified the print directives in smb.conf (as well as in samba itself) will be ignored because samba will directly interface with CUPS through it's application program interface (API) - so long as Samba has been compiled with CUPS library (libcups) support. If samba has NOT been compiled with CUPS support then -printing will use the System V AT&T command set with the <emphasis>-oraw</emphasis> +printing will use the System V AT&T command set with the <emphasis>-oraw</emphasis> option automatically passing through. </para> @@ -103,16 +102,14 @@ at the time when the driver initially generated the PostScript data and CUPS in printer communication backend. </para> -<para> -<note>NOTE: editing in the "mime.convs" and the "mime.types" file does not *enforce* -"raw" printing, it only *allows* it.</note> -</para> +<note><para>NOTE: editing in the "mime.convs" and the "mime.types" file does not *enforce* +"raw" printing, it only *allows* it.</para></note> <para> 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. -<itemlist> +<itemizedlist> <listitem><para> Files generated by PCL drivers and directed at PCK printers get auto-typed as <filename>application/octet-stream</filename>. Unknown file format types also @@ -123,12 +120,12 @@ the process of determining proper treatment while in the print queue system. 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: - <itemlist> + <itemizedlist> <listitem><para>* application/postscript</para></listitem> <listitem><para>* application/vnd.cups-postscript</para></listitem> - </itemlist> + </itemizedlist> </para> -</itemlist> +</itemizedlist> </para> @@ -160,7 +157,7 @@ or "cupsomatic" will take over (depending on the printer configuration, as determined by the PPD in use). </para> -<para><note> +<note><para> 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. @@ -168,9 +165,9 @@ will go directly there as received by the spooler. The exeptions are file types 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.) -</note></para> +</para></note> -<para><note> +<note><para> "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 @@ -191,7 +188,7 @@ This line persuades CUPS to hand the file to cupsomatic, once it has successfull 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. -</para> +</para></note> <para> CUPS is widely configurable and flexible, even regarding its filtering mechanism. @@ -262,11 +259,11 @@ The following diagrams reveal how CUPS handles print jobs. # 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): # -# <SOMETHNG>-FILEFORMAT +# <replaceable>SOMETHNG</replaceable>-FILEFORMAT # | # | # V -# <something>tops +# <replaceable>something</replaceable>tops # | # | # V @@ -291,7 +288,7 @@ The following diagrams reveal how CUPS handles print jobs. # | # | # V -# rasterto<something> (f.e. Gimp-Print filters may be plugged in here) +# rasterto<replaceable>something</replaceable> (f.e. Gimp-Print filters may be plugged in here) # | (= "raster driver") # | # V @@ -302,11 +299,11 @@ The following diagrams reveal how CUPS handles print jobs. # backend # # -# ESP PrintPro has some enhanced "rasterto<something>" filters as compared to +# ESP PrintPro has some enhanced "rasterto<replaceable>something</replaceable>" 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<something> is noted. +# CUPS and ESP PrintPro plug-in where rasterto<replaceable>something</replaceable> is noted. # ######################################################################### </programlisting> @@ -317,11 +314,11 @@ The following diagrams reveal how CUPS handles print jobs. # This is how "cupsomatic" comes into play: # ========================================= # -# <SOMETHNG>-FILEFORMAT +# <replaceable>SOMETHNG</replaceable>-FILEFORMAT # | # | # V -# <something>tops +# <replaceable>something</replaceable>tops # | # | # V @@ -341,11 +338,11 @@ The following diagrams reveal how CUPS handles print jobs. # | (= "postscipt interpreter") Ghostscript commandline # | to let the file be # V processed by a -# APPLICATION/VND.CUPS-RASTER "-sDEVICE=<s.th.>" +# APPLICATION/VND.CUPS-RASTER "-sDEVICE=<replaceable>s.th.</replaceable>" # | call...) # | | # V | -# rasterto<something> V +# rasterto<replaceable>something</replaceable> V # | (= "raster driver") +-------------------------+ # | | Ghostscript at work.... | # V | | @@ -353,7 +350,7 @@ The following diagrams reveal how CUPS handles print jobs. # | | # | | # V | -# backend <------------------------------------+ +# backend >------------------------------------+ # | # | # V @@ -364,7 +361,7 @@ The following diagrams reveal how CUPS handles print jobs. # "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<something>", and hands the rasterized file directly to the CUPS +# "rasterto<replaceable>something</replaceable>", and hands the rasterized file directly to the CUPS # backend... # # cupsomatic is not made by the CUPS developers. It is an independent @@ -372,7 +369,7 @@ The following diagrams reveal how CUPS handles print jobs. # 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<something> is noted. +# CUPS and ESP PrintPro plug-in where rasterto<replaceable>something</replaceable> is noted. # ######################################################################### </programlisting> @@ -383,11 +380,11 @@ The following diagrams reveal how CUPS handles print jobs. # And this is how it works for ESP PrintPro from 4.3: # =================================================== # -# <SOMETHNG>-FILEFORMAT +# <replaceable>SOMETHNG</replaceable>-FILEFORMAT # | # | # V -# <something>tops +# <replaceable>something</replaceable>tops # | # | # V @@ -411,7 +408,7 @@ The following diagrams reveal how CUPS handles print jobs. # | # | # V -# rasterto<something> (f.e. Gimp-Print filters may be plugged in here) +# rasterto<replaceable>something</replaceable> (f.e. Gimp-Print filters may be plugged in here) # | (= "raster driver") # | # V @@ -422,7 +419,7 @@ The following diagrams reveal how CUPS handles print jobs. # backend # # NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to -# CUPS and ESP PrintPro plug-in where rasterto<something> is noted. +# CUPS and ESP PrintPro plug-in where rasterto<replaceable>something</replaceable> is noted. # ######################################################################### </programlisting> @@ -434,11 +431,11 @@ The following diagrams reveal how CUPS handles print jobs. # ================================================================ # # -# <SOMETHNG>-FILEFORMAT +# <replaceable>SOMETHNG</replaceable>-FILEFORMAT # | # | # V -# <something>tops +# <replaceable>something</replaceable>tops # | # | # V @@ -458,11 +455,11 @@ The following diagrams reveal how CUPS handles print jobs. # | (= "postscipt interpreter") Ghostscript commandline # | to let the file be # V processed by a -# APPLICATION/VND.CUPS-RASTER "-sDEVICE=<s.th.>" +# APPLICATION/VND.CUPS-RASTER "-sDEVICE=<replaceable>s.th.</replaceable>" # | call...) # | | # V | -# rasterto<something> V +# rasterto<replaceable>something</replaceable> V # | (= "raster driver") +-------------------------+ # | | Ghostscript at work.... | # V | | @@ -470,14 +467,14 @@ The following diagrams reveal how CUPS handles print jobs. # | | # | | # V | -# backend <------------------------------------+ +# backend >------------------------------------+ # | # | # V # THE PRINTER # # NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to -# CUPS and ESP PrintPro plug-in where rasterto<something> is noted. +# CUPS and ESP PrintPro plug-in where rasterto<replaceable>something</replaceable> is noted. # ######################################################################### </programlisting> @@ -488,11 +485,11 @@ The following diagrams reveal how CUPS handles print jobs. # And this is how it works for CUPS from 1.1.15: # ============================================== # -# <SOMETHNG>-FILEFORMAT +# <replaceable>SOMETHNG</replaceable>-FILEFORMAT # | # | # V -# <something>tops +# <replaceable>something</replaceable>tops # | # | # V @@ -517,11 +514,11 @@ The following diagrams reveal how CUPS handles print jobs. # +------------------v------------------------------+ # | # | -# APPLICATION/VND.CUPS-RASTER <-------+ +# APPLICATION/VND.CUPS-RASTER >-------+ # | # | # V -# rasterto<something> +# rasterto<replaceable>something</replaceable> # | (= "raster driver") # | # V @@ -538,14 +535,14 @@ The following diagrams reveal how CUPS handles print jobs. # "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<something>" +# be finally processed by a CUPS raster driver "rasterto<replaceable>something</replaceable>" # 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<something> is noted. +# CUPS and ESP PrintPro plug-in where rasterto<replaceable>something</replaceable> is noted. # ######################################################################### </programlisting> @@ -556,11 +553,11 @@ The following diagrams reveal how CUPS handles print jobs. # And this is how it works for CUPS from 1.1.15, with cupsomatic included: # ======================================================================== # -# <SOMETHNG>-FILEFORMAT +# <replaceable>SOMETHNG</replaceable>-FILEFORMAT # | # | # V -# <something>tops +# <replaceable>something</replaceable>tops # | # | # V @@ -577,7 +574,7 @@ The following diagrams reveal how CUPS handles print jobs. # +------------------v------------------------------+ # | Ghostscript . Ghostscript at work.... | # | at work... . (with "-sDEVICE= | -# | (with . <s.th.>" | +# | (with . <replaceable>s.th.</replaceable>" | # | "-sDEVICE=cups") . | # | . | # | (CUPS standard) . (cupsomatic) | @@ -587,15 +584,15 @@ The following diagrams reveal how CUPS handles print jobs. # +------------------v--------------v---------------+ # | | # | | -# APPLICATION/VND.CUPS-RASTER <-------+ | +# APPLICATION/VND.CUPS-RASTER >-------+ | # | | # | | # V | -# rasterto<something> | +# rasterto<replaceable>something</replaceable> | # | (= "raster driver") | # | | # V | -# SOMETHING-DEVICE-SPECIFIC <------------------------+ +# SOMETHING-DEVICE-SPECIFIC >------------------------+ # | # | # V @@ -603,7 +600,7 @@ The following diagrams reveal how CUPS handles print jobs. # # # NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to -# CUPS and ESP PrintPro plug-in where rasterto<something> is noted. +# CUPS and ESP PrintPro plug-in where rasterto<replaceable>something</replaceable> is noted. # ########################################################################## </programlisting> @@ -618,161 +615,196 @@ The following diagrams reveal how CUPS handles print jobs. CUPS ships with good support for HP LaserJet type printers. You can install the driver as follows: -<itemlist> +<itemizedlist> <listitem><para> lpadmin -p laserjet4plus -v parallel:/dev/lp0 -E -m laserjet.ppd </para></listitem> -</itemlist> +</itemizedlist> (The "-m" switch will retrieve the "laserjet.ppd" from the standard repository for not-yet-installed-PPDs, which CUPS typically stores in -filename>/usr/share/cups/model</filename>. Alternatively, you may use +<filename>/usr/share/cups/model</filename>. Alternatively, you may use "-P /absolute/filesystem/path/to/where/there/is/PPD/your.ppd"). </para> -<para> -<programlisting> -Windows printing involves some more steps.... - -But let me first point out some more general things about printer "drivers" -for Linux/Unix (yes, and for Mac OS X now!), be it you use CUPS or one of -the venerable (I'd even call them "ancient" and "rusty" now...) printing -systems. +<sect2> +<title>Further printing steps</title> -You -- and everybody else, for that matter -- should always also consult the -database on linuxprinting.org for all recommendations about "which driver -is best used for which printer": +<para> +Always also consult the database on linuxprinting.org for all recommendations +about which driver is best used for each printer: +</para> - http://www.linuxprinting.org/printer_list.cgi +<para><ulink url="http://www.linuxprinting.org/printer_list.cgi">http://www.linuxprinting.org/printer_list.cgi</ulink></para> +<para> 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* "recommended" -one. Try this one first. In your case ("HP LaserJet 4 Plus"), you'll arrive -here: +all drivers working with your model. There will always be *one* +<emphasis>recommended</emphasis> one. Try this one first. In your case +("HP LaserJet 4 Plus"), you'll arrive here: +</para> - http://www.linuxprinting.org/show_printer.cgi?recnum=75104 +<para><ulink url="http://www.linuxprinting.org/show_printer.cgi?recnum=75104">http://www.linuxprinting.org/show_printer.cgi?recnum=75104</ulink></para> +<para> The recommended driver is "ljet4". It has a link to the page for the ljet4 driver too: +</para> - http://www.linuxprinting.org/show_driver.cgi?driver=ljet4 +<para><ulink url="http://www.linuxprinting.org/show_driver.cgi?driver=ljet4">http://www.linuxprinting.org/show_driver.cgi?driver=ljet4</ulink> -On the driver's page, you'll find various important and detailed infos about -how to use that driver within various spoolers. You can generate a PPD for +<para> +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... +</para> +<para> 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 will possible corrupt +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" +</para> +<para> Then install the printer: - +</para> +<para><programlisting> "lpadmin -p laserjet4plus -v parallel:/dev/lp0 -E -P /some/path/on/your/filesystem/somewhere/my-name-for-my-printer.ppd" +</programlisting></para> +<para> 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 +"cupsomatic" from: +</para> - http://www.linuxprinting.org/cupsomatic +<para><ulink url="http://www.linuxprinting.org/cupsomatic">http://www.linuxprinting.org/cupsomatic</ulink></para> -This needs to be copied to "/usr/lib/cups/filter/cupsomatic" 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. +<para> +This needs to be copied to <filename>/usr/lib/cups/filter/cupsomatic</filename> +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. +</para> +<para> 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: +</para> - http://www.linuxprinting.org/execution.cgi?driver=ljet4&printer=75104&.submit=Show+execution+details +<para><ulink url="http://www.linuxprinting.org/execution.cgi?driver=ljet4&printer=75104&.submit=Show+execution+details">http://www.linuxprinting.org/execution.cgi?driver=ljet4&printer=75104&.submit=Show+execution+details</ulink></para> -The ingenious thing is this: the database is kept very current. If there +<para> +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... Till Kamppeter from MandrakeSoft is doing an -excellent job here, and too few people still know about it. (So if you use -it often, please send him a note of your appreciation sometime...) +the steps described above. +</para> -(The latest and greatest improvement now is support for "custom page sizes" -for all those printers which support it...) +<note><para> +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).</para></note> +<para> +The latest and greatest improvement now is support for "custom page sizes" +for all those printers which support it. +</para> + +<para> "cupsomatic" is documented here: +</para> - http://www.linuxprinting.org/cups-doc.html +<para><ulink url="http://www.linuxprinting.org/cups-doc.html">http://www.linuxprinting.org/cups-doc.html</ulink></para> +<para> More printing tutorial info may be found here: +</para> - http://www.linuxprinting.org/kpfeifle/LinuxKongress2002/Tutorial/ +<para><ulink url="http://www.linuxprinting.org/kpfeifle/LinuxKongress2002/Tutorial/">http://www.linuxprinting.org/kpfeifle/LinuxKongress2002/Tutorial/</ulink></para> +<para> 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 great detail in the Samba CVS sources (for 2.2.x) in +in this document. +</para> - docs/textdocs/CUPS-PrintingInfo.txt +<para> +Summary - You need: +</para> -To sum it up: +<para> +<simplelist> -* having a "foomatic+<something>" PPD is not enough to print with CUPS - (but it is *one* important component) -* you also need the "cupsomatic" filter script (Perl) in "/usr/lib/cups/filters/" -* you need Perl to make cupsomatic run -* you also need Ghostscript (because it is called and controlled by the - PPD/cupsomatic combo in a way to fit your printermodel/driver combo...) -* your Ghostscript *must*, depending on the driver/model, contain support - for a certain "device" (as shown by "gs -h") + <member>A "foomatic+<replaceable>something</replaceable>" PPD is not enough to print with CUPS (but it is *one* important component)</member> + <member>The "cupsomatic" filter script (Perl) in <filename>/usr/lib/cups/filters/</filename></member> + <member>Perl to make cupsomatic run</member> + <member>Ghostscript (because it is called and controlled by the PPD/cupsomatic combo in a way to fit your printermodel/driver combo.</member> + <member>Ghostscript *must*, depending on the driver/model, contain support for a certain "device" (as shown by "gs -h")</member> +</simplelist> +<para> In the case of the "hpijs" driver, you need a Ghostscript version, which -is showing a "ijs" amongst its supported devices in "gs -h". In the case of +has "ijs" amongst its supported devices in "gs -h". In the case of "hpijs+foomatic", a valid ghostscript commandline would be reading like this: +</para> +<para><programlisting> gs -q -dBATCH -dPARANOIDSAFER -dQUIET -dNOPAUSE -sDEVICE=ijs \ - -sIjsServer=hpijs<PageSize> -dDuplex=<Duplex> <Model> \ - -r<Resolution>,PS:MediaPosition=<InputSlot> -dIjsUseOutputFD \ + -sIjsServer=hpijs<replaceable>PageSize</replaceable> -dDuplex=<replaceable>Duplex</replaceable> <replaceable>Model</replaceable> \ + -r<replaceable>Resolution</replaceable>,PS:MediaPosition=<replaceable>InputSlot</replaceable> -dIjsUseOutputFD \ -sOutputFile=- - +</programlisting></para> +<note><para> 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..... +menus. +</para></note> +<para> If you use "ESP Ghostscript" (also under the GPL, provided by Easy Software -Products, the makers of CUPS, downloadable from http://www.cups.org/software.html, +Products, the makers of CUPS, downloadable from +<ulink url="http://www.cups.org/software.html">http://www.cups.org/software.html</ulink>, 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.... - ->>/ However, I can only print a Cups test page, from the web interface. when I -/>>/ try to print a windows test page, it acts like the job was never sent. -/ - * Can you print "standard" jobs from the CUPS machine? +GNU Ghostscript 7.05 only has ~200. +</para> - * Are the jobs from Windows visible in the Web interface on CUPS - (http://localhost:631/)? +<para> +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: -*Most important:* What kind of printer driver are you using on the Windows clients??? +<simplelist> + <member>Can you print "standard" jobs from the CUPS machine?</member> + <member>Are the jobs from Windows visible in the Web interface on CUPS (http://localhost:631/)?</member> + <member><emphasis>Most important:</emphasis> What kind of printer driver are you using on the Windows clients?</member> +</simplelist> You can try to get a more detailed debugging info by setting "LogLevel debug" in -"/etc/cups/cupsd.conf", re-start cupsd and investigate "/var/log/cups/error_log" +<filename>/etc/cups/cupsd.conf</filename>, re-start cupsd and investigate <filename>/var/log/cups/error_log</filename> for the whereabouts of your Windows-originating printjobs: - - * what does the "auto-typing" line say? which is the "MIME type" CUPS thinks - is arriving from the Windows clients? - * are there "filter" available for this MIME type? - * are there "filter rules" defined in "/etc/cups/mime.convs" for this MIME type? -</programlisting> </para> +<simplelist> + <member>what does the "auto-typing" line say? which is the "MIME type" CUPS thinks is arriving from the Windows clients?</member> + <member>are there "filter" available for this MIME type?</member> + <member>are there "filter rules" defined in "/etc/cups/mime.convs" for this MIME type?</member> +</simplelist> + </sect1> @@ -780,17 +812,22 @@ for the whereabouts of your Windows-originating printjobs: <title>Limiting the number of pages users can print</title> <para> -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. +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. +</para> +<para> Of course one could "hack" things with one's own scripts. +</para> +<para> 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. +</para> +<para> This is an example command how root would set a print quota in CUPS, assuming an existing printer named "quotaprinter": </para> @@ -802,20 +839,22 @@ assuming an existing printer named "quotaprinter": <para> 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). +</para> -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 -- f.e. 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 +<para> +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! +</para> -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 +<para> +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 </para> <programlisting> @@ -830,125 +869,178 @@ 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). +</para> - From CUPS-1.1.16 onward you can use the "CUPS PostScript Driver +<para> +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.... +It is *not* working for Win9x/ME clients. But it: +</para> - ...it guarantees to not write an PJL-header; - ...it guarantees to still read and support all PJL-options named - in the driver PPD with its own means; - ...it guarantees the file going thru the "pstops" filter on the - CUPS/Samba server; - ...it guarantees to page-count correctly the printfile... +<simplelist> + <member>>it guarantees to not write an PJL-header</member> + <member>it guarantees to still read and support all PJL-options named in the driver PPD with its own means</member> + <member>it guarantees the file going thru the "pstops" filter on the CUPS/Samba server</member> + <member>it guarantees to page-count correctly the printfile</member> +</simplelist> +<para> 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). +</para> -These are the items CUPS logs in the "page_log" for every single -*page* of a job: +<para> +These are the items CUPS logs in the "page_log" for every single *page* of a job: +</para> -* Printer name -* User name -* Job ID -* Time of printing -* the page number -* the number of copies -* a billing info string (optional) +<para><programlisting> + * Printer name + * User name + * Job ID + * Time of printing + * the page number + * the number of copies + * a billing info string (optional) +</programlisting></para> +<para> Here is an extract of my CUPS server's page_log file to illustrate the format and included items: +</para> -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 - -This was Job ID "40", printed on "infotec_IS2027" by user "kurt", -a 6-page job printed in 2 copies and billed to "#marketing"... - -Which flaws or shortcomings are there? - - * the ones named above; - * 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; - * all quotas are the same for all users (no flexibility to - give the boss a higher quota than the clerk) - * no support for groups; - * no means to read out the current balance or "used-up" - number of current quota; - * a user having used up 99 sheets of 100 quota will still be - able to send and print a 1.000 sheet job; - * 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". +<para><programlisting> + infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 1 2 #marketing + infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 2 2 #marketing + infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 3 2 #marketing + infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 4 2 #marketing + infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 5 2 #marketing + infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 6 2 #marketing +</programlisting></para> +<para> +This was Job ID "40", printed on "infotec_IS2027" by user "kurt", a 6-page job +printed in 2 copies and billed to "#marketing"... +</para> + +<para> +What flaws or shortcomings are there? +</para> + +<simplelist> + <member>the ones named above</member> + + <member> + 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 + </member> + + <member> + all quotas are the same for all users (no flexibility to give the + boss a higher quota than the clerk) no support for groups + </member> + + <member> + no means to read out the current balance or "used-up" number of current quota + </member> + + <member> + a user having used up 99 sheets of 100 quota will still be able to send and print a 1.000 sheet job + </member> + + <member> + 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". + </member> +</simplelist> + +<para> But this is the best system out there currently. And there are huge improvements under development: +</para> ---> 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...) +<simplelist> + <member>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)</member> ---> quotas will be handled more flexibly; + <member>quotas will be handled more flexibly</member> ---> probably there will be support for users to inquire their - "accounts" in advance; + <member>probably there will be support for users to inquire their "accounts" in advance</member> ---> probably there will be support for some other tools around - this topic... + <member>probably there will be support for some other tools around this topic</member> +</simplelist> +<para> Other than the current stage of the CUPS development, I don't know any other ready-to-use tool which you could consider. </para> <para> -You can download the driver files from http://www.cups.org/software.html. It -is a separate package from the CUPS base software files, tagged as "CUPS 1.1.16 +You can download the driver files from +<ulink url="http://www.cups.org/software.html">http://www.cups.org/software.html</ulink>. +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 +the files: +</para> +<para> +<programlisting> cups-samba.install cups-samba.license cups-samba.readme cups-samba.remove cups-samba.ss +</programlisting> +</para> +<para> 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 "/usr/share/cups/drivers/". Its contents are 3 files: +into <filename>/usr/share/cups/drivers/</filename>. Its contents are 3 files: +</para> +<para> +<programlisting> cupsdrvr.dll cupsui.dll cups.hlp +</programlisting> +</para> -[ ATTENTION: due to a bug the current release puts the "cups.hlp" into - "/usr/share/drivers/" instead of "/usr/share/cups/drivers/". To work - around this, copy/move the file after running the "./cups-samba.install" - script manually to the right place: +<note><para> +ATTENTION: due to a bug one CUPS release puts the <filename>cups.hlp</filename> +into <filename>/usr/share/drivers/</filename> instead of +<filename>/usr/share/cups/drivers/</filename>. To work around this, copy/move +the file after running the "./cups-samba.install" script manually to the right place: +</para> - "cp /usr/share/drivers/cups.hlp /usr/share/cups/drivers/" ] +<para> +<programlisting> + cp /usr/share/drivers/cups.hlp /usr/share/cups/drivers/ +</programlisting> +</para> +</note> -This new CUPS PostScript driver is currently binary-only, but free (as in -free beer); no source code is provided (yet). The reason is this: it has +<note> +<para> +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. +</para> +<para> 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/" @@ -958,145 +1050,186 @@ 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. +</para></note> + +<note><para> NOTE 1: Win 9x/ME clients won't work with this driver. For these you'd - still need to use the ADOBE*.* drivers as previously. +still need to use the ADOBE*.* drivers as previously. +</para></note> +<note><para> NOTE 2: It is not harming if you've still the ADOBE*.* driver files from - previous installations in the "/usr/share/cups/drivers/" directory. - The new cupsaddsmb (from 1.1.16) will automatically use the - "newest" installed driver (which here then is the CUPS drivers). +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). +</para></note> +<note><para> NOTE 3: Should your Win clients have had the old ADOBE*.* files and the - Adobe PostScript drivers installed, the download and installation - of the new CUPS PostScript driver for Windows NT/2k/XP will fail - at first. - 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 --> Settings --> Control Panel --> 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...) - -NOTE 4: 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.... +Adobe PostScript drivers installed, the download and installation +of the new CUPS PostScript driver for Windows NT/2k/XP will fail +at first. +</para> +<para> +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 --> Settings --> Control Panel --> 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.) +</para> +</note> +<note><para> +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. +</para></note> +<para> What are the benefits with the "CUPS PostScript driver for Windows NT/2k/XP" as compared to the Adobe drivers? - 9 -* no hassle with the Adobe EULA; no hassle with the question "where do I - get the ADOBE*.* driver files from?" - -* 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 "<1B>%-12345X" or "<escape>%-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...) - -* 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....) - -* 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... - -* 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). - -* 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). - -* 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). </para> + +<para> +<itemizedlist> + <listitem><para> + no hassle with the Adobe EULA + </para></listitem> + + <listitem><para> + no hassle with the question "where do I get the ADOBE*.* driver files from?" + </para></listitem> + <listitem><para> + 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 "<replaceable>1B</replaceable>%-12345X" or "<replaceable>escape</replaceable>%-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) + </para></listitem> + + <listitem><para> + 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) + </para></listitem> + + <listitem><para> + 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 + </para></listitem> + + <listitem><para> + 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). + </para></listitem> + + <listitem><para> + 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). + </para></listitem> + + <listitem><para> + 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). + </para></listitem> + +</itemizedlist> +</para> </sect1> <sect1> <title>Advanced Postscript Printing from MS Windows</title> <para> -* Let the Windows Clients use a PostScript driver, to produce - PostScript as their print output sent towards the Samba print - server (just like any Linux or Unix Client would also use - PostScript to send to the server...) +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) +</para> -* make the Unix printing subsystem which is underneath Samba - convert the incoming PostScript files to the native print - format of the target printers (would likely be PCL? - I understand you have mainly HP models?) +<para> +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) +</para> -* You're afraid, that this would just mean a *Generic* PostScript - driver for the clients? With no Simplex/Duplex selection, - no paper tray choice? But you need them to be able to set up - their jobs, ringing all the bells and whistles of the printers? +<para> +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:- +</para> - --> Not possible with traditional spooling systems! +<simplelist> + <member>Not possible with traditional spooling systems</member> - --> But perfectly supported by CUPS (which uses "PPD" files to - describe how to control the print options for PostScript and - non-PostScript devices alike... + <member> + But perfectly supported by CUPS (which uses "PPD" files to + describe how to control the print options for PostScript and + non-PostScript devices alike... + </member> +</simplelist> - 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. +<para> +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. +</para> -* You want to have the additional benefit of page count logging - and accounting? In this case the CUPS PostScript driver - is the best choice (better than the Adobe one). +<para> +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). +</para> -* You want to make the drivers downloadable for the clients? - "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... +<para> +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. +</para> -"What strings are attached?", I hear you asking... +<warning> +<para>What strings are attached?</para></warning> -You are right, there are some. But, given the sheer CPU power -you can buy nowadays in German supermarkets, these can be -overcome easily. +<para> +There are some. But, given the sheer CPU power you can buy nowadays, +these can be overcome easily. The strings: +</para> -The strings: Well, if the -CUPS/Samba side will have to print a *lot* onto 40 printers -serving 500 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.... +<para> +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. </para> </sect1> @@ -1105,37 +1238,49 @@ able to handle.... <title>Auto-Deletion of CUPS spool files</title> <para> -Samba print files pass thru 2 -different "spool" directories. Once the incoming directory -managed by Samba, (set f.e. in the "path = /var/spool/samba" -directive in the [printers] section of "smb.conf"). Second is -the spool directory of your UNIX print subsystem. For CUPS it is -normally "/var/spool/cups/", as set by the cupsd.conf directive +Samba print files pass thru two "spool" directories. One the incoming directory +managed by Samba, (set eg: in the "path = /var/spool/samba" directive in the [printers] +section of "smb.conf"). Second is the spool directory of your UNIX print subsystem. +For CUPS it is normally "/var/spool/cups/", as set by the cupsd.conf directive "RequestRoot /var/spool/cups". +</para> -I am not sure, which one of your directories keeps the files. - From what you say, it is most likely the Samba part. +<para> +I am not sure, which one of your directories keeps the files. From what you say, +it is most likely the Samba part. +</para> +<para> For the CUPS part, you may want to consult: +</para> +<programlisting> http://localhost:631/sam.html#PreserveJobFiles and http://localhost:631/sam.html#PreserveJobHistory and http://localhost:631/sam.html#MaxJobs +</programlisting> -There are the settings described for your CUPS daemon, which -could lead to completed job files not being deleted. +<para> +There are the settings described for your CUPS daemon, which could lead to completed +job files not being deleted. +</para> +<para> "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. +</para> +<para> "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. +</para> +<para> "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 @@ -1143,42 +1288,70 @@ 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. +</para> +<para> (There are also additional settings for "MaxJobsPerUser" and "MaxJobsPerPrinter"...) +</para> -For everything to work as announced, you need to have three -things: +<para> +For everything to work as announced, you need to have three things: +</para> + +<simplelist> - * a Samba-smbd which is compiled against "libcups" (Check - on Linux by running "ldd `which smbd`") + <member> + a Samba-smbd which is compiled against "libcups" (Check on Linux by running "ldd `which smbd`") + </member> - * a Samba-smb.conf setting of "printing = cups" + <member> + a Samba-smb.conf setting of "printing = cups" + </member> - * another Samba-smb.conf setting of "printcap = cups" + <member> + another Samba-smb.conf setting of "printcap = cups" + </member> +</simplelist> + +<note><para> 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. +</para></note> +<para> 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. +</para> +<para> 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. +</para> + +<para> If you have more problems, post the output of these commands: +</para> +<para> +<programlisting> grep -v ^# /etc/cups/cupsd.conf | grep -v ^$ grep -v ^# /etc/samba/smb.conf | grep -v ^$ | grep -v "^;" +</programlisting> +</para> +<para> (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. </para> </sect1> +</chapter> |