This looks similar to a non-working setup I tried out.

For some strange reason, I need the old "rp= " and "rm= " entries; if I
substitute "lp=queue@hostname", the filters do not get processed.

This is NOT a definitive reply, just an observation.

But the "lp=remotequeue@remotehostname" and "rp=remotequeue"  &
"rm=remotehostname" entries in the printcap do NOT behave
interchangeably with a bounce queue. 

I admit I am not clear about what the options all do; this is as I said
just an observation.

I defined my queues as 

pr1 -> with filter, no "lp=", & rp=funnelq & rm=localhost entries (so
filtering gets done) -> 

pr2, pr... -> with filter, no "lp=", & rp=funnelq & rm=localhost
entries (so filtering gets done) ->

funnelq -> with no filters, lp=remote@localhost ->

remote -> with no filters, rp=lp and rm=remotehost.

The printouts then have the expected format.

Helmut Neujahr


[EMAIL PROTECTED] schrieb:
> On Sun, 14 Apr 2002, Joel Hammer wrote:
> 
> > This printcap file has entries for about 10 printers. 
> Why don't you configure 
> > a printcap file for just one printer, either manually 
> or with whatever graphical thingee 
> > you are using, then duplicate (manually) the working 
> queue, subsituting 
> > approriately as needed?
> > After you do that, run checkpc -f, and you should be 
> ok. 
> > Joel
> 
> I'm having a similar problem, but I *must* have a single 
> centralized queue 
> for these pre-processed queues to feed into, due to 
> printers that gag if 
> they have multiple incoming jobs at the same time.
> 
> My printcap for these queues:
> 
> .common:sd=/var/spool/lpd/%P
> .kyocera:lpd_bounce:if=/usr/kyocera/kyocera.fpi:tc=.comm
> on 
> ky1|9100:rp=KYO_164182:rm=ky1:tc=.common
> 9101:lp=ky1@localhost:tc=.kyocera
> 9102:lp=ky1@localhost:tc=.kyocera
> 9103:lp=ky1@localhost:tc=.kyocera
> 9104:lp=ky1@localhost:tc=.kyocera
> 9105:lp=ky1@localhost:tc=.kyocera
> 9106:lp=ky1@localhost:tc=.kyocera
> 
> If you pass off a print job to the 910x queues from a 
> remote lpd, it 
> prints just fine, using the filter.  If you print to one 
> of them locally, 
> it will never run the filter, but is passed on to the 
> bounce queue anyway. 
> 
> This hasn't been an issue in the past, but due to trying 
> to stabilize 
> print from our SCO (*gag*) print servers, I'm moving away 
> from their lpd 
> (horribly, horribly broken) to just using rcmd's.
> 
> Anyone have any ideas?  I'm sure I'm overlooking 
> something, but... 
> 
> Note:  I'm using 3.6.26 (long story, but an upgrade won't 
> happen for 
> another couple months, minimum).
> 
> Thanks,
> 
> -- 
> Bradley Hartin - [EMAIL PROTECTED]
> Communications and Network Administrator
> Straus-Frank Company
> 
> 
> 
> --------------------------------------------------------
> --------------------- 
> 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