Jobs are resent to CUPS Server after reboot

[Michael Sweet]

Udo Hortian wrote:
>> It isn't a bug, but rather a side-effect of how we ensure that all 
>> jobs from a client get printed to the server.
> 
> So this is just normal? Is there no other way to check if the job
> already exists on the server? This would be very glad.

No reliable way (we can see if a given job-uuid is present, but that
isn't 100% since job history could be disabled on the server/printer)

> We don't turn the printer on very often because often prints are not
> time critical. And so things like this happen very often and if you
> sent a job consisting of say 30 pages and it gets printed 5 times
> this is not what I want.

Better to just hold all jobs by default (lpadmin -p printer -o
job-hold-until-default=indefinite) and only release them when the
printer is turned on.

-- 
______________________________________________________________________
Michael Sweet, Easy Software Products           mike at easysw dot com
Internet Printing and Document Software          http://www.easysw.com