maxjobs setting in cupsd.conf

[Steve Cohen]

> > Steve Cohen wrote:
> > > I am looking at the MaxJobs setting in cupsd.conf. It says:
> > >
> > > "The MaxJobs directive controls the maximum number of jobs that are kept in memory. Once the number of jobs reaches the limit, the oldest completed job is automatically purged from the system to make room for the new one. If all of the known jobs are still pending or active then the new job will be rejected.
> > >
> > > Setting the maximum size to 0 disables this functionality. The default setting is 500."
> > >
> > > So it is saying that it keeps track of both completed and uncompleted jobs, right? If I set MaxJobs to 0 that would mean that it never purges completed jobs. Is that correct? Is there a way to purge completed jobs but disable the maxjobs for queued jobs so it doesn't reject jobs?
> >
> > You can add "PreserveJobHistory No" to automatically purge completed
> > jobs, and then set MaxJobs to 0 to allow an unlimited number of active
> > jobs.
> >
> > --
> > ______________________________________________________________________
> > Michael Sweet, Easy Software Products           mike at easysw dot com
>
>
> Thanks for the response. I see the entry in cupsd.conf now. Wouldn't I want to set PreserveJobFiles and not History? Also, is there a setting for just purging completed jobs and not the canceled or aborted ones?
>
> Steve Cohen



Let me give a bit more information. We are having an issue that when our clients do their printouts they will get "too many active jobs" errors. I am assuming this is because of the MaxJobs setting. I have the printers ErrorPolicy set to retry-jobs but they are telling me that they still have to manually reprint jobs that error (Presumably that is because the jobs aren't placed in the queue due to the "too many jobs" error).

They won't give an upper limit of how many jobs they need to print so I can't just increase MaxJobs so I would like to set it to 0. However, setting MaxJobs to 0 causes completed jobs to stick around and not be purged. I take it that setting PreserveJobFiles to off would purge the jobs when they are completed?

Btw, what is the benefit to leaving the completed jobs around? What functionality do I lose by purging completed jobs?

Thanks,
Steve Cohen