Red Hat Bugzilla – Bug 436439
The argument 'group' of builtin 'newgrp' should be optional.
Last modified: 2015-03-04 18:56:38 EST
Description of problem:
The description of builtin "newgrp" is "newgrp [-] group", it shows that
argument "group" is necessary, but actually it is optional. In newgrp(1),
"group" is optional too.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
2.[test@localhost ~]$echo $?
It is executed successfully.
An error message is outputed and the return value is not 0.
Created attachment 297148 [details]
This is a patch fixing the bug.
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated in the
current release, Red Hat is unfortunately unable to address this
request at this time. Red Hat invites you to ask your support
representative to propose this request, if appropriate and relevant,
in the next release of Red Hat Enterprise Linux.
This request was erroneously denied for the current release of
Red Hat Enterprise Linux. The error has been fixed and this
request has been re-proposed for the current release.
Will be proposed to upstream.
Proposed to upstream: http://bugs.gw.com/view.php?id=119
Accepted by upstream (tcsh 6.17.07b).
Bugfix was successfully verified on tcsh617-6.17-5.el5 package.
Group parameter for newgrp builtin is new marked as optional (newgrp [-] [group]).
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
Prior to this update, the tcsh(1) man page inaccurately stated that it is mandatory to use the "group" option when using the "newgrp" built-in command. The corrected statement now says that using "group" is optional.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.