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

[Christian Ullrich <chris@xxxxxxxxxxxxx>]

* Michael Loßin wrote on Thursday, 2002-01-17:

> On 16-Jan-02 Christian Ullrich wrote:
> > * Christian Ullrich wrote on Wednesday, 2002-01-16:
> > 
> [...]
> > 6. I added the above line "filter_stderr_to_status_file" to
> > /etc/lpd.conf.
> >    This file had not existed before. I restarted lpd.
> 
> Argh... By mentioning "/etc/lpd.conf" I meant "whatever the
> correct config file for LPRng is"... I just hope it *really*
> is /etc/lpd.conf (you should at least see /etc/lpd.conf.sample
> if the path is correct).

I haven't got any file called lpd.conf or lpd.conf.sample. But
I removed LPRng yesterday on request by Garance Drosihn.

> > 9. More stairs. Does someone know any skyscrapers in lack of stairs?
> > 
> > 10. status still empty, status.ascii 4947 bytes. See below.
> 
> I'm afraid /etc/lpd.conf was not the correct path... Otherwise
> "status" would consists of the pure apsfilter error log
> messages (just "+ WIDTH_POINTS=595" etc. instead of all the
> date/time stuff).
> Maybe it's "/usr/local/etc/lpd.conf" on your machine.

That doesn't exist either, but it is mentioned in the LPRng port's
packing list, so I presume it has been deleted as well.

> > -- 8< -- /var/spool/lpd/ascii/status.ascii -- >8 --
> > 
> [...]
> > IF filter 'apsfilter' filter msg - '+ print_raw' at
> > 2002-01-16-19:54:30.360 ## A=chris@christian+454 number=454
> > process=82735
> 
> There it is... "print_raw" is called, so there will be no
> automatic file conversion.
> 
> Now all we have to do is find out why apsfilter does that:
> 
> 1) There's a "METHOD=raw" setting in one of the configuration
>    files -- not likely, given that you created the "ascii"
>    queue the way you described.

/etc/apsfilter/ascii/apsfilterrc contains "METHOD=ascii".

> 2) You give the "-b" or "-l" options to lpr -- please tell me
>    that you don't... :^)

Yes, I don't :-).

> 3) The spooler includes "-c" as one option for the input
>    filter, thus overriding the METHOD=... default (this is what
>    I guess). Unfortunately, the log does not include the argument
>    parsing section, but let's just suppose this to be true.

That's it. I saved the apsfilter commandline to a file, and that
file reads as follows (print job from client):

-c -w132 -l66 -i0 -n chris -h christian.chrullrich.de /var/spool/lpd/ascii/acct

(print job from server:)

-w132 -l66 -i0 -n chris -h ser1.chrullrich.de /var/spool/lpd/ascii/acct

Well, at least we've managed to locate the problem. Now I can work
around it by disabling the "-c" option in apsfilter, but I'm sure that
will break when I use a "raw" configuration, won't it?

-- 
Christian Ullrich		     Registrierter Linux-User #125183

"Deliver."