I'm experimenting with using a routing filter to dynamically move
a job around based on its level of authentication.
I've noticed that with LPRng 3.8.20, any postscript file which
goes through this process gets thrown into the queue for
"another_printer" (which I expect) *after* getting processed by ifhp
(which I did not expect). ifhp is not specified in the printcap entry for
"another_printer."
In other words, there is a bunch of pjl at the start and end of my
postscript and I suspect that it has (if necessary) been reencoded with
tbcp.
Is this the way things are supposed to work? It certainly isn't
clear from the LPRng HOWTO.
It appears that I can avoid the ifhp processing if I specify
-Zlanguage=RAW, give lpr the -l command line option, or make the
corresponding modifications to the job's control file from within the
routing script.
/* Sam */
The routing script is essentially:
#!/bin/sh
echo "dest another_printer"
echo "end"
exit 0
My printcap entry looks like the following:
4200t
:af=/var/spool/print/4200t/JOBLOG
:filter=/usr/libexec/filters/ifhp
:ifhp=model=hp4050, sync=|/usr/local/bin/check_printer_status.pl,
waitend=|/usr/local/bin/check_printer_waitend.pl
:lp=192.168.1.1%9100
:mx=0
:router=/home/nobles/route.old
:sd=/var/spool/print/4200t
:sh
:user_is_authuser
-----------------------------------------------------------------------------
YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRNG MAILING LIST
The address you post from MUST be your subscription address
If you need help, send email to [EMAIL PROTECTED] (or lprng-requests
or lprng-digest-requests) with the word 'help' in the body. For the impatient,
to subscribe to a list with name LIST, send mail to [EMAIL PROTECTED]
with: | example:
subscribe LIST <mailaddr> | subscribe lprng-digest [EMAIL PROTECTED]
unsubscribe LIST <mailaddr> | unsubscribe lprng [EMAIL PROTECTED]
If you have major problems, send email to [EMAIL PROTECTED] with the word
LPRNGLIST in the SUBJECT line.
-----------------------------------------------------------------------------