[RFE] STR #1903: Add support for STATE:paused from filters tostop queue

Dmitry Sharov dsharov at mackiev.com
Thu Apr 5 06:22:14 PDT 2007


> Dmitry Sharov wrote:
> >> [STR Closed w/Resolution]
> >>
> >> Fixed in Subversion repository.
> >>
> >> Link: http://www.cups.org/str.php?L1903
> >> Version: 1.3-feature
> >> Fix Version: 1.3-current (r6429)
> >
> > While queue state is changed to stopped, current job is not stopped explicitly.
> > Probably this is not an intended behavior for this feature.
>
> The job should be stopped, but the filters and backend may not stop
> immediately while they do job cleanup...
>
I'm observing the following.
After reporting 'STATE: +paused', current job retains 'processing' state.
Filter chain does not receive a TERM signal.
If the entire filter chain exits with 0 exit status, job is dismissed from the print queue job list as completed.
If at least one filter of the filter chain exits with non-zero status then job is stopped but contents of printer-state-message is replaced with '<filter> failed', so ther is no way to preserve previously reported printer-state-message.




More information about the cups-devel mailing list