large jobs on slow printer loop forever

[Helge Blischke]

Rainer Hubovsky wrote:
> 
> Thank you for your reply, Helge. To be honest, I have no idea how to "strace
> the lpd backend". Could you point me in the right direction?
As for strace, see the man page for the options. As for the lpd backend,
create a link to the lpd backend the name of which is exactly the
device-uri
(as the lpd backend gets the device-uri from argv[0], and you can hardly
fake this from the shell), and supply the command line options
(job-id, username, title-string, number-of-copies, option-string (may be
""),
and the path of the (a) file to print.
> 
> BTW: is there a way of testing all this without actually printing the jobs,
> because we would waste a lot of paper.
For a test like the one above, switch off the printer when you have
enough
information from strace.
> 
> Thanks a lot.
>   +rainer
> 
> In article <413C511C.480E at srz-berlin.de>, Helge Blischke wrote:
> > The first relevant error message in your log seems to be an "interrupted
> > system call" (4), and
> > the lpd backend then tries to print the file again. The print server
> > then refuses the
> > control file with errno 108 which means (on Linux) "cannot send after
> > transport endpoint
> > shutdown"
> >
> > To do further diagnosis, you should try to strace the lpd backend to see
> > what happens
> > during the backend sending the data file for the first time.
> >
> > Helge

-- 
Helge Blischke
Softwareentwicklung
SRZ Berlin | Firmengruppe besscom
http://www.srz.de
tel: +49 30 75301-360