I found it (was: Re: 4.4R: if: doesn't get started when getting remote print job)

[Christian Ullrich <chris@xxxxxxxxxxxxx>]

* Christian Ullrich wrote on Thursday, 2002-01-17:

> That was a double success (for me, at least). Firstly, it does
> now print text correctly, second the printer keeps blinking,
> so I'm at last convinced that the job did indeed pass through
> apsfilter.

I found it. Neither FreeBSD nor apsfilter are to blame in any way,
it is LPRng on the client that's causing the trouble, though 
I don't know whether it is the SuSE preconfiguration or some error
on my part. SuSE's support database at least doesn't know anything.

I examined the control files on the client, and found this line:

ldfA538christian.chrullrich.de

Isn't that a nice 'l'? And when I feed "-Ff" into the client-side
lpr, it's an 'f' and the job is printed just fine, even without
Michael's workaround. Now I just need to find out why LPRng 
treats any job as literal.

-- 
Christian Ullrich		     Registrierter Linux-User #125183

"Deliver."