As for finding bug reports, try here:
https://github.com/apple/cups/issues?utf8=%E2%9C%93&q=is%3Aissue+lpstat+

CUPS is a weird beast, because it's literally communicating on a
client-server basis, which means that the CUPS server is literally
saying that those jobs exist in some form or fashion, even if they
cannot be canceled.  My suspicion is that they're not cancelable
because they're in a canceled state, waiting for some timeout.  In
which case, it's probably a fault either in the client for not
interpreting those jobs as effectively gone, or in the server, for
failing to indicate that status.

The source is also perusable in that repository, although its location
is not entirely obvious.  You'd think it's a core command, but it's
not.  No, it's part of the System V integration:
https://github.com/apple/cups/blob/master/systemv/lpstat.c
This might also be why the bug persisted.

On Thu, Nov 7, 2019 at 10:16 AM Howard White <[email protected]> wrote:
>
> My Google foo does not register one bar on the meter...
>
> So I may be the only sysadmin on the planet that looks at lpstat -o.  We
> have customers that print, a lot.  I am seeing vestigial print jobs
> listed in lpstat -o such that if one tries to cancel <jobnum>, the
> message "cancel-job failed:  Job #<jobnum> does not exist!"  They just
> had to put the exclamation point on the end there to thumb the systems
> nose at the operator; "You ninny!"  If I subsequently type cancel -a,
> they all go away and the list is empty.
>
> I have started running the Nagios test check_cups_queue which relies on
> the same command information and is similarly distracted by the
> vestigial print jobs.
>
> I have seen this behavior on CentOS 6 and 7.  Anybody got any leads on
> how I might find a bug listing?  Hell, I haven't been able to find how
> to check for what version of CUPS is installed.
>
> So Happy It's Thursday...
>
> Howard
>
> --
> --
> You received this message because you are subscribed to the Google Groups 
> "NLUG" group.
> To post to this group, send email to [email protected]
> To unsubscribe from this group, send email to 
> [email protected]
> For more options, visit this group at 
> http://groups.google.com/group/nlug-talk?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups 
> "NLUG" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected].
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/nlug-talk/1d73c981-c0ac-c711-91c4-6b22c3c0a790%40vcch.com.



-- 
Tilghman

-- 
-- 
You received this message because you are subscribed to the Google Groups 
"NLUG" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/nlug-talk?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"NLUG" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/nlug-talk/CAHPkZcUkLh%3DMZQecsLevUonOUeECQMPMeNnvWj8Gr95CFQvS_g%40mail.gmail.com.

Reply via email to