Description of problem: Manpage says that "Without an argument (allowed in only a shell script),", but it is allowed via pipe. Version-Release number of selected component (if applicable): tcsh-6.15.00 How reproducible: Steps to Reproduce: 1.[test@localhost ~]$ nohup nohup: Can't from terminal. 2.[test@localhost ~]$ echo 'nohup' | tcsh -l Actual results: An error message is outputed. Expected results: Nothing is outputed Additional info:
Created attachment 297725 [details] This is a patch fixing the bug.
I made a mistake. "Actual results:" should be "Nothing is outputed.". "Expected results:" should be "An error message is outputed.".
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.
Created attachment 473878 [details] Simple patch to fix 'nohup' section of man page Will be proposed to upstream.
Proposed to upstream: http://bugs.gw.com/view.php?id=119
Accepted by upstream (tcsh 6.17.07b).
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. New Contents: The tcsh(1) man page inaccurately stated that the "hup" and "nohup" built-in commands, when used without an argument, can be used only within a shell script. The man page has been corrected: it now states that the hup and nohup built-in commands can be used when running the shell non-interactively.
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. http://rhn.redhat.com/errata/RHBA-2011-1072.html