Re: 4.4R: if: doesn't get started when getting remote print job

[Garance A Drosihn <drosih@xxxxxxx>]

At 2:43 PM +0100 1/17/02, Christian Ullrich wrote:
>* Michael Loßin wrote on Thursday, 2002-01-17:
>  > Now all we have to do is find out why apsfilter does that:
>>
>  > 2) You give the "-b" or "-l" options to lpr -- please tell me
>>     that you don't... :^)
>
>Yes, I don't :-).

>From another message that Christian sent to me, I know that what the
server sees for a control file is as if the original 'lpr' command on
the client machine *did* do a '-l'.  The control file for the print
job indicates that the file should be printed "literally", so both
lpr (or lprNG) and apsfilter are handling the print job the way they
should handle the print job.

So, the question is, "Why are the lprNG-based clients sending the
print job as if -l had been specified".  I do not know lprNG, but I
suspect there is something about the printcap entry on those clients
which is causing that to happen.

-- 
Garance Alistair Drosehn            =   gad@eclipse.acs.rpi.edu
Senior Systems Programmer           or  gad@freebsd.org
Rensselaer Polytechnic Institute    or  drosih@rpi.edu