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

[Christian Ullrich <chris@xxxxxxxxxxxxx>]

* Michael Loßin wrote on Wednesday, 2002-01-16:

> On 16-Jan-02 Christian Ullrich wrote:
> > * Andreas Klemm schrieb am Mittwoch, 2002-01-16:
> > 
> >> Another idea ... additionally.
> >> use set -x in apsfilter shellscript and see in the printers logfile,
> >> if apsfilter gets called an how, to make sure what happens or not
> >> ...
> > 
> > I did that. As I'm currently some 30 km away from the printer, I 
> > can't see what it produced, but now I know at least that apsfilter
> > was indeed called. In the directory /var/spool/lpd/ascii, two files
> > have been created: "lpq" and "lpq.0". The first one contains only:
> > 

[output deleted]

> 
> Are you sure that output is not from some printing attempt
> before?

Yes. Before starting the job, I checked that these files were not
present. After printing, they were, and the timestamps in the files
match the system clock. The only other explanation would be that 
LPRng or something else stores output of older jobs elsewhere and
copies it to the spooldir at random.

> Please perform the following steps:
>   - add "filter_stderr_to_status_file" to /etc/lpd.conf
>     and restart LPRng
>   - remove (or clear) "/var/spool/lpd/ascii/status" and
>     "/var/spool/lpd/ascii/status.ascii"
>   - print again (with "set -x" in apsfilter)
>   - post those two status files on this list

I'll do that later, when I can look at what's coming out of the 
printer.

-- 
Christian Ullrich		     Registrierter Linux-User #125183

"Deliver."