[cups-devel] [UNKN] STR #4757: Change Default ErrorPolicy to abort-job
"Laura M." <[email protected]>
| Newsgroups | gmane.comp.printing.cups.devel |
|---|---|
| Message-ID | <[email protected]> |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW. [STR New] The default error policy, unless modified by the user in cupsd.conf, is stop-printer. In the default configuration, this means that if there is an error, the local cups printer will automatically be stopped. Resuming the printer requires manual intervention; even if the printer subsequently reports that it is working, users are unable to print unless the resume the printer. This is a little bit counter intuitive; if a user job automatically causes a printer error and stoppage - the generally needs to be resolved by an administrator - why doesn't cups automatically resume when the printer reports good health? Alternatively, why doesn't it simply abort the job? The only use case we might see this being of benefit would be in a large networked printer environment. But in this case, there would be a very limited amount of machines that need to be configured (especially as the client machines would likely only see a "single" virtual printer). This is especially frustrating for two reasons: 1) Cups doesn't recognize a difference between a filter error (or something caused by a malformed pdf) vs an out-of-paper or any other kind of error, instead choosing to stop the printer whenever something might possibly go wrong. Why not abort the job instead? (Holding the job might causes people to print the same thing multiple times, but is an equally valid option). 2) For individual or small network users using a remote printer, this can cause the local cups printer to stop, even though it may work for everyone else. This is, again, a frustrating default to keep. Judging from the number of web results, this seems to be a common problem. Rather than configuring every single computers cupsd.conf file with a new ErrorPolicy directive, can we instead change the internal default to "abort-job" in order to provide a more useful out-of-box experience for more users? Link: https://www.cups.org/str.php?L4757 Version: 2.2-current -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (GNU/Linux) Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJWlokYAAoJENujp6sI12IjjKYQAKPr8qUxxiJJmcB0TODJRqx7 OsaTeT/7lhnZ6DhQz70gyybuIi9V3AHiiRmjwX6vbhqpK+OAvsLqP29yxsxjyup3 85OG+awb5mDvNpUz15VRSa7kgt8hipRi/6jIyWgzUGmEfE0j6lLvru9B7rtGxDJP Y+BVK5Z+4a5Wc6y6OtKdJnos/Q4tgpr72u5Dj+As37YKILQyp1lqijI151lhgjxn G4F1bsFKAPuTAIWLT04vU0v9eKFyR5r4ig4cyokfTfx2dqGXZRbqHWU6dx5gLrSl JMjN1QpuTwnccd0ai0eEBJu+oO0/3t7xwZrPP+utJ+zKc7XR8YT341czsyxvqb3Y RwgMf+VVv+rX+5OdE69Xy8zt6tVR5jPVgWIVzwdkOOvuJWrox30P2aJ5wuuXu9EJ XtrRQ8xkIOVFRdcM4AzRtcI8PwS4M3kM4RpIu1Rr9qfiTaq7PUPKwlEKiMkpNMMD 8nRxscALQVtHJWSHGD/2GSnx7mH3gAmMUopzyfHb6OeUBCg2etaxKy+7u2yP8nYe YXCe6jm5c4VAxxs0U76Tj4x+eBJoK412jZUu0jETYTjMSA6vmN66YhJuX8GyYKFb l19ZYsXmL0mpr9rWS5oJ9YwnZFEosqFsBkO0ZlPQPyLiDAQsyiDI3TgHkFIk0fzk e+xj7JhtTd+kGtMhH4a/ =oQM9 -----END PGP SIGNATURE-----