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.
DescriptionMason Loring Bliss
2020-12-23 19:32:33 UTC
Description of problem:
lpstat(1) from cups-client needs -h to specify a host to appear in the
command line prior to other arguments. There's nothing indicating this in
the docs or help text.
Version-Release number of selected component (if applicable):
Multiple versions. (E.g., we also see this on Debian.)
How reproducible:
Note that the -h is ignored if it follows -r, but honored if it precedes
-r. In my test case, there is a cupsd running, but it is *not* listening to
port 1234. I'd expect the -h directive to apply regardless of order.
Actual results:
/home/mason$ lpstat -r -h 127.0.0.1:1234
scheduler is running
/home/mason$ lpstat -h 127.0.0.1:1234 -r
scheduler is not running
Expected results:
/home/mason$ lpstat -r -h 127.0.0.1:1234
scheduler is not running
/home/mason$ lpstat -h 127.0.0.1:1234 -r
scheduler is not running
Comment 2Mason Loring Bliss
2021-01-04 20:28:46 UTC
This was noted internally, so we are the customer. It would be better to
break the implicit ordering dependency than to simply document it, if we
have the option to do that.
Ordering behaviour is not set in stone, but there are common opinions:
https://www.gnu.org/software/libc/manual/html_node/Argument-Syntax.html
which says:
"Options may be supplied in any order, or appear multiple times. The
interpretation is left up to the particular application program."
There are probably examples going both ways, but as I look, what I'm
generally seeing is that arguments with positioning requirements are
treated specially, usually without dashes, with ordering for those
arguments specified in man page and usage. Some examples:
cp [OPTION]... [-T] SOURCE DEST
ln [OPTION]... [-T] TARGET LINK_NAME
ls [OPTION]... [FILE]...
bzip2 [ -cdfkqstvzVL123456789 ] [ filenames ... ]
dig [global-queryopt...] [query...]
mount [-fnrsvw] [-t fstype] [-o options] device dir
So, we could do it either way, but we were surprised by the positional
requirement, which means other people have been and will be surprised by it
as well.
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 (cups bug fix and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2022:7716