Cups daemon dies on some time of inactivity

Michael Sweet mike at easysw.com
Wed Sep 1 06:30:47 PDT 2004


Juergen Schroeder wrote:
> ...
> (gdb) where
> #0  0xff0b3218 in strlen () from /usr/lib/libc.so.1
> #1  0xff0cf560 in strdup () from /usr/lib/libc.so.1
> #2  0x0003bad0 in SetPrinterAttrs ()
> #3  0x00017390 in AddPrinterToClass ()
> (gdb) 
> 
> Hmm,  I  have two identical printers on two cups-servers (ortsleihe1 and
> ortsleihe2) which should build the class ortsleihe,  but  ortsleihe1  is
> normaly  allways  off.  It  should  only switched on on a failure on the
> other one.

Hmm, can you recompile with debug enabled (--enable-debug when you
run the configure script)?  There are two main places where this could
crash, and it looks like it might be the printer URI or name is not set
prior to calling SetPrinterAttrs()?

> (But I don't get the described failover feature to work. I want that the
> printing defaults to one and the other printer should only  be  used  if
> the default fails.)

There is currently no way to set this behavior short of hardwiring the
printer connections (either via lpadmin or client.conf)


> BTW the main BUG could be solved independently from this error analysis:
> 
> "lpr -r -Ppqueue file"
> 
> should remove the file only if the printing had been successfully!

That wouldn't be consistent with the Berkeley implementation (imagine
an application using the same print file name calling lpr multiple
times and having the file mysteriously disappear in the middle of
writing the print file...)

-- 
______________________________________________________________________
Michael Sweet, Easy Software Products           mike at easysw dot com
Printing Software for UNIX                       http://www.easysw.com




More information about the cups mailing list