Bug#280718: Status?

[Ryan Lovett]

On Wed, Feb 15, 2006 at 06:47:41PM +0100, Loïc Minier wrote:
>  I do agree that the rate is high (it was probably chosen so that the
>  icon appears promptly after a documents is printed), I don't want to
>  debate that, however running a local cupsys has other advantages, such
>  as queuing of documents in case the main server is down.  I feel it's
>  quite logical to have a local spool of print jobs, just like I feel
>  it's sensible to have a local MTA or a retry mechanism in your MUA.
> 
>  My position is that running a cupsys on each machine is a sensible
>  thing to do for practical advantages, and also works around the central
>  server hammering problem you're having.

You make some good points. One disadvantage as to how this interacts with
the GNOME panel icon is that once the job is sent from a local CUPS server
to the remote CUPS server, the local CUPS server thinks that the job has
been completed since it doesn't either receive the remote server's job
status or republish the status to its own clients. We see this with our
central CUPS server when it sends jobs to workstations with locally
attached (non-network) printers. The central server sends the job to the
CUPS spooler with the USB/Parallel printer and thinks the job is done, even
if the queue with the attached printer is still processing other jobs or
has become funkified. You'd then get reports from users saying "my print
job is not on the queue but my document hasn't printed."

Ryan