Hide Forgot
Description of problem: umount -h option not supported Version-Release number of selected component (if applicable): [root@dhcp-13-188 ~]# umount.nfs -h umount.nfs: -h: not found [root@dhcp-13-188 ~]# umount.nfs -h umount.nfs: -h: not found [root@dhcp-13-188 ~]# rpm -q nfs-utils nfs-utils-1.2.3-36.el6.x86_64 [root@dhcp-13-188 ~]# lsb_release -sr 6.4 How reproducible: always Steps to Reproduce: 1. umount -h 2. 3. Actual results: [root@dhcp-13-188 ~]# umount.nfs -h umount.nfs: -h: not found Expected results: usage: umount.nfs dir [-fvnrlh] options: -f force unmount -v verbose -n Do not update /etc/mtab -r remount -l lazy unmount -h print this help Additional info:
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.
Also the USAGE should be print to user when using this command with wrong option, for example: Actual results: [root@hp-dl580g7-04 ~]# umount.nfs -xxx umount.nfs: -xxx: not found [root@hp-dl580g7-04 ~]# Expected results: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ how it actually works in rhel7.1 [root@intel-s3e36-01 ~]# umount.nfs -xxx umount.nfs: invalid option -- 'x' usage: umount.nfs dir [-fvnrlh] options: -f force unmount -v verbose -n Do not update /etc/mtab -r remount -l lazy unmount -h print this help [root@intel-s3e36-01 ~]#
Setting low priority on this, since it is not something that would normally be an issue for most users. We should look at doing this upstream, if it has not been done already, but I'm not sure that we necessarily need to do this in RHEL6.
(In reply to Yongcheng Yang from comment #3) > Also the USAGE should be print to user when using this command with wrong > option, for example: > > Actual results: > [root@hp-dl580g7-04 ~]# umount.nfs -xxx > umount.nfs: -xxx: not found > > [root@hp-dl580g7-04 ~]# > > Expected results: > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ how it actually works in rhel7.1 > [root@intel-s3e36-01 ~]# umount.nfs -xxx > umount.nfs: invalid option -- 'x' > usage: umount.nfs dir [-fvnrlh] > options: > -f force unmount > -v verbose > -n Do not update /etc/mtab > -r remount > -l lazy unmount > -h print this help > > [root@intel-s3e36-01 ~]# Well this is just the way RHEL6 works. Unlike RHEL7, RHEL6 assumes the given first give argument is the directory to unmount. If the argument does not start with '/' a "not found" error is issued. The correct error code is used so I think we are fine.