Hide Forgot
+++ This bug was initially created as a clone of Bug #1003536 +++ Description of problem: if rpc.mountd specify options: "-N 2 -N 3 -N 4", should output more readable info to user Version-Release number of selected component (if applicable): all version from RHEL5.9 RHEL5.10 RHEL6.x RHEL7.0 How reproducible: y Steps to Reproduce: 1. 2. 3. Actual results: [root@dell-pr7610-01 ~]# rpc.mountd -N 2 -N 3 -N 4 Usage: rpc.mountd [-F|--foreground] [-h|--help] [-v|--version] [-d kind|--debug kind] [-o num|--descriptors num] [-f exports-file|--exports-file=file] [-p|--port port] [-V version|--nfs-version version] [-N version|--no-nfs-version version] [-n|--no-tcp] [-H ha-callout-prog] [-s|--state-directory-path path] [-g|--manage-gids] [-t num|--num-threads=num] Expected results: should output info to notify user, why error: example: your can not disable all version of mountd Additional info: --- Additional comment from Yin.JianHong on 2013-09-02 06:01:49 EDT --- [root@dell-pr7610-01 ~]# rpc.mountd --no-nfs-version 2 --no-nfs-version 3 --no-nfs-version 4 Usage: rpc.mountd [-F|--foreground] [-h|--help] [-v|--version] [-d kind|--debug kind] [-o num|--descriptors num] [-f exports-file|--exports-file=file] [-p|--port port] [-V version|--nfs-version version] [-N version|--no-nfs-version version] [-n|--no-tcp] [-H ha-callout-prog] [-s|--state-directory-path path] [-g|--manage-gids] [-t num|--num-threads=num]
This request was not resolved in time for the current release. Red Hat invites you to ask your support representative to propose this request, if still desired, for consideration in the next release of Red Hat Enterprise Linux.
commit 6ec0d58fbff7c1a814a21cf8c7fe0ef5106a04c1 Author: Steve Dickson <steved> Date: Wed Jan 20 14:16:08 2016 -0500 mountd: print an error message when no versions are specified Signed-off-by: Steve Dickson <steved>
Move to VERIFIED according to comment 8. Will continue to run the automatic case in the future 7.3 test round.
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-2016-2383.html