I guess you should look at the lineprinter.scr filter. This filter must
send the job to standard out. Perhaps the filter is sending the output
to a file. 

Then, I believe you really need to make your lineprinter queue a bounce
queue.

Here is what I have for a bounce queue. A bounce queue, as I understand it,
or at least as I am using the term here, is a queue which filters the job,
but then sends the job elsewhere for actual printing. I believe what you are
doing is better suited to just sending an unfiltered file to the remote
machine.

This queue works. It takes a postscript file, converts it to a binary file, and
then sends it to a raw queue on another machine.  The local machine is
jhammer6 and the remote machine is hammer2

PostScript:\
        [EMAIL PROTECTED]:\
         [EMAIL PROTECTED]:\
         sh:sd=/var/spool/lpd/pre-filtered-z53:mx#0:\
        :if=/usr/local/lexmark/z53/z53.sh
        :sh:
 
A trick is that you make lp the queue itself. A nuisance is that the
queue on the remote machine is named lp. This doesn't confuse lprng but
it can confuse humans.

Joel

On Fri, May 30, 2003 at 12:57:51PM -0500, Barton Wold wrote:
> I am trying to set up a "virtual" printer for when print jobs are sent
> to, it takes that job and runs a script to add some custom headers and
> convert it to postscript, then forwards this job to be printed out on a
> different printer.  My printcap entry looks like this:
> 
> lineprinter:\
>     :lp=frenv52%9100:\
>    
> :filter=/export/Spool/lprng/libexec/filters/lineprinter/lineprinter.scr:\
>     :sd=/export/Spool/lprng/spool/lpd/%P:\
>     :af=/export/Spool/lprng/spool/lpd/%P/acct:\
>     :lf=/export/Spool/lprng/spool/lpd/%P/log:\
> 
> frenv52:\
>     :lp=/dev/null:\
>     :ifhp=model=hp5000, dev=frenv52%9100,appsocket:\
>     :filter=/export/Spool/lprng/libexec/filters/ifhp:\
>     :sd=/export/Spool/lprng/spool/lpd/%P:\
> 
> Where lineprinter is the "virtual" printer (that is, it doesn't
> physically exist) that takes a job, runs the lineprinter.scr script that
> creates a postscript document and sends it to the actual printer,
> frenv52.
> 
> When I send this print job, it does create the postscript file but
> doesn't actually print.  I run a 'snoop' from the print server to the
> actual printer (frenv52) and see network traffic going to it, so it
> looks like it works, except that nothing gets printed out.
> 
> If anyone has suggestions, I would greatly appreaciate it.  Thanks.
> 
> Barton Wold
> United Defense L.P.
> [EMAIL PROTECTED]
> 
> 
> -----------------------------------------------------------------------------
> 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.
> -----------------------------------------------------------------------------

-----------------------------------------------------------------------------
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.
-----------------------------------------------------------------------------

Reply via email to