Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 885625

Summary: man cupsctl, typo
Product: Red Hat Enterprise Linux 6 Reporter: Petr Sklenar <psklenar>
Component: man-pages-overridesAssignee: Peter Schiffer <pschiffe>
Status: CLOSED ERRATA QA Contact: Iveta Wiedermann <isenfeld>
Severity: unspecified Docs Contact:
Priority: low    
Version: 6.3CC: ovasik, pschiffe, tlavigne
Target Milestone: rcKeywords: ManPageChange, Patch
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
No documentation needed
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-11-21 22:54:38 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 884649    
Bug Blocks: 875898, 1011076    
Attachments:
Description Flags
cupsctl.8.patch none

Description Petr Sklenar 2012-12-10 09:11:59 UTC
Description of problem:
man cupsctl:
   cupsctl FileDevice=Yes

Version-Release number of selected component (if applicable):
cups-1.4.2-48.el6_3.9.x86_64

How reproducible:
deterministic

Steps to Reproduce:
1. man cupsctl
2, see Examples and:
       Enable printing using the file: pseudo-device:
           cupsctl FileDevice=Yes

Actual results:
that's not right from version cups-1.4.2-48.el6_3.9.x86_64

Expected results:
cupsctl updates only cupsd.conf file, where are not allowed such a directives

Additional info:

Comment 1 Petr Sklenar 2012-12-10 09:15:09 UTC
then I noticed one more typo in the man page:
       Disable printer sharing:
           cupsctl --no-shared-printers

# cupsctl --no-shared-printers
cupsctl: Unknown option "--no-shared-printers"!

<snip uasage message />
    --[no-]share-printers   Turn printer sharing on/off

# cupsctl --no-share-printers
### ^ this works  and its written in the usage message
### ^ /share/shared

Comment 3 Tim Waugh 2012-12-12 12:33:25 UTC
Thanks.  Reported upstream in STR #4223 and STR #4248.

Comment 5 Tim Waugh 2013-03-26 16:43:32 UTC
Current Red Hat Enterprise Linux 6 cupsctl man page says:

Enable printing using the file: pseudo-device (note that this is
forbidden by default):

     cupsctl FileDevice=Yes

Keeping open for the --no-shared-printers typo.

Comment 6 Peter Schiffer 2013-09-18 16:15:39 UTC
Created attachment 799476 [details]
cupsctl.8.patch

Comment 12 errata-xmlrpc 2013-11-21 22:54:38 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2013-1695.html