Wishlist: Better handling of backend error

Hatto von Hatzfeld hatto at usenet.salesianer.de
Mon Nov 7 00:15:11 PST 2005


Michael Sweet wrote:

> Hatto von Hatzfeld wrote:
>> When a "backend did not respond within 30 seconds" the cups server is not
>> reachable, even other printers are unusable, and it is very difficult to
>> figure out what is wrong (cups does not tell which backend has this
>> problem). I suggest that this should be improved.
>> ...
> 
> This message is only displayed on cupsd startup - once the server
> has started, normal processing can continue.
> 
> That said, CUPS 1.2 does away with the probe on startup, and instead
> only probes when a CUPS-Get-Devices request is done.  In addition,
> the probe starts a separate cups-deviced process which does the
> actual probe and allows the cupsd process to continue accepting
> and processing requests while it figures out the available devices.

Then why the following?

~> lpq
lpq: Unable to contact server!
~> lynx http://localhost:631/
(error: no connection to remote host)
~> pstree | grep cups
     ├─cupsd───cupsd───serial

Ciao,
Hatto

-- 
Treffen sich zwei Planeten im Weltall. Sagt der eine: "Du siehst aber
schlecht aus. Fehlt dir was?" Sagt der zweite: "Ach, mir geht's gar
nicht gut. Ich hab' Homo sapiens." Tröstet ihn der andere: "Mach dir
keine Sorgen. Hatte ich auch mal. Das geht schnell vorbei."




More information about the cups mailing list