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 1351720 - documentation inconsistency on arping
Summary: documentation inconsistency on arping
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: iputils
Version: 6.8
Hardware: Unspecified
OS: Linux
low
low
Target Milestone: rc
: ---
Assignee: Jan Synacek
QA Contact: Tomas Dolezal
URL:
Whiteboard:
Depends On:
Blocks: 1269194 1356047 1359260
TreeView+ depends on / blocked
 
Reported: 2016-06-30 16:07 UTC by João Avelino Bellomo Filho
Modified: 2019-11-14 08:34 UTC (History)
2 users (show)

Fixed In Version: iputils-20071127-23.el6
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-03-21 09:29:44 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1351704 0 unspecified CLOSED documentation inconsistency on arping 2021-02-22 00:41:40 UTC
Red Hat Product Errata RHBA-2017:0604 0 normal SHIPPED_LIVE iputils bug fix update 2017-03-21 12:26:37 UTC

Internal Links: 1351704

Description João Avelino Bellomo Filho 2016-06-30 16:07:55 UTC
Description of problem:

The arping man page shows it requires the '-I' option, but the help page shows that option as optional.

Whenever the command is executed without '-I' option it works without error.

Version-Release number of selected component (if applicable):

iputils-20071127-21.el6

How reproducible:


Steps to Reproduce:
1. Show the arping help page:

$ arping -h

2. Open the arping man page:

$ man arping

3. Execute the arping command without '-I' option:

arping 192.168.1.1

Actual results:

The first step shows the help page where the '-I' option is shown as optional, between brackets:

Usage: arping [-fqbDUAV] [-c count] [-w timeout] [-I device] [-s source] destination

The second step shows the man page where th '-I' option is shown as required, without brackets:

 arping  [-AbDfhqUV]  [-c  count] [-w deadline] [-s source] -I interface
       destination

The third step works well.

Expected results:

The help page should show the same information. If the '-I' is not required that should be shown on both page.

Additional info:

On RHEL7 the behavior of arping requires the '-I' option.

Comment 2 João Avelino Bellomo Filho 2016-06-30 16:27:53 UTC
The sources from iputils shows that the arping command detect if the 'device' variable is null, before to show an error message about the '-I' be required:

[arping.c]
...
468     if (device == NULL) {
469         fprintf(stderr, "arping: device (option -I) is required\n");
470         usage();
471     }
...

But, the 'device' variable is initialized as 'eth0':
[arping.c]
...
 40 char *device="eth0";
...

So, the correct behaviour should be the '-I' option required. Seems the but is not only related to the documentation.

Comment 14 errata-xmlrpc 2017-03-21 09:29:44 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.

https://rhn.redhat.com/errata/RHBA-2017-0604.html


Note You need to log in before you can comment on or make changes to this bug.