Bug 62939
Summary: | Ghost entries left in local spool for network printers | ||
---|---|---|---|
Product: | [Retired] Red Hat Public Beta | Reporter: | Scott Schmit <i.grok> |
Component: | LPRng | Assignee: | Tim Waugh <twaugh> |
Status: | CLOSED DUPLICATE | QA Contact: | Brock Organ <borgan> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | skipjack-beta2 | CC: | tibbitts |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2002-04-08 22:11:14 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Scott Schmit
2002-04-08 05:49:56 UTC
I'm pretty sure this is expected behaviour. See the CHANGES file at about release 3.8.2. Ok, this explains why I had 1 done job. However, I now have 2 done jobs: Printer: lp@amazonis (dest lp@utopia) Queue: no printable jobs in queue Server: no server active Status: job 'draco@amazonis+5' saved at 01:44:26.742 Rank Owner/ID Class Job Files Size Time done draco@amazonis+557 A 557 m2revise.ps 11520043 01:34:41 done draco@amazonis+5 A 5 wind_dir 310 01:44:26 Printer: lp@utopia Queue: no printable jobs in queue Status: job 'cfA005amazonis' removed at 01:46:29.358 From what I've read in the CHANGES file, the default is 1, which can be overridden at build time or from the lpd.conf file: - /etc/lpd.conf doesn't modify the default value - the spec file for LPRng hasn't passed a --with_done_jobs=N to configure to change from the default of 1. The CHANGES file indicates that in 3.8.9, a bug was found where more done jobs would lie around than the configured max was. However, despite the fact that the jobs were long ago done, they're still there. The version in skipjack beta 2 is 3.8.9-3, so presumably the bug they found has been fixed already. I have 2 done jobs, nevertheless. Ergo, there is still a bug here. If I'm wrong, please explain. |