- verbose mode for debugging. WARNING: This will create a file in /tmp that contains the debugging information. This opens a security loophole and should not be used in production.
- quiet mode - minimal information output
- -P <printer>
- <printer> is the configured printer which should be used for this job.
- --ppd <ppdfile>
- The PPD file <ppdfile> should be applied for processing this job.
- -o <option>=<value>
- Option settings for this job.
- The file(s) to be printed.
foomatic-rip will print from standard input unless at least one file to be printed is specified on the command line. If your printer PPD file is stored as /etc/direct/<printer>.ppd or ~/.foomatic/direct/<printer>.ppd you can use it by simply specifying "-P <printer>".
Put a line
*FoomaticRIPPostPipe: "| <command>"
into the PPD file, right after *PPD-Adobe: "4.3", where <command> is a command into which you want to re-direct the output data. Due to the restrictions of PPD files <, >, and " are not allowed in the <command>, replace them as follows:
Character Replacement ---------------------
This way you can print directly to your printer, use
*FoomaticRIPPostPipe: "| cat > /dev/lp0"
*FoomaticRIPPostPipe: "| cat > /dev/usb/lp0"
for local parallel or USB printers. To make normal users able to print this way add them to the group lp and make sure that the appropriate printer device file /dev/... is group-writable for the lp group.
for a TCP/Socket/JetDirect printer with the host name printer listening on port 9100 you need this:
*FoomaticRIPPostPipe: "| /usr/bin/nc -w 1 printer 9100"
Note the "-w 1" in the "nc" command line, it makes "nc" exiting immediately after the data is transferred to the printer.
*FoomaticRIPPostPipe: "| rlpr -Plp@printserver"
directs your jobs to the LPD printer queue lp on the machine named printserver.
See also http://www.openprinting.org/direct-doc.html
None so far.
Please send bug reports to the OpenPrinting bug tracker:
Use "OpenPrinting" as the product and "cups-filters" as the component.