Anonymous | Login | 2024-12-12 14:25 UTC |
Main | My View | View Issues | Change Log | Docs |
Viewing Issue Simple Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||
ID | Category | Severity | Type | Date Submitted | Last Update | ||
0000165 | [1003.1(2008)/Issue 7] Shell and Utilities | Comment | Enhancement Request | 2009-10-09 12:09 | 2009-10-15 15:45 | ||
Reporter | eblake | View Status | public | ||||
Assigned To | ajosey | ||||||
Priority | normal | Resolution | Rejected | ||||
Status | Resolved | ||||||
Name | Eric Blake | ||||||
Organization | N/A | ||||||
User Reference | ebb.nohup | ||||||
Section | nohup | ||||||
Page Number | 2979 | ||||||
Line Number | 98152 | ||||||
Interp Status | --- | ||||||
Final Accepted Text | |||||||
Summary | 0000165: nohup internal error exit status | ||||||
Description |
Most of the forwarding utilities (env, exec, nice, time, xargs) specify that errors internal to the utility, prior to attempting to locate the child process to execute, shall use an exit status in the range of 1-125. However, nohup and command explicitly require a status of 127, which can be confused with command not found. It would be nice to let implementations consistently use status 125 for internal error (such as failure to parse command-line options). The proposed wording leaves status 127 as a valid status for nohup and command, so as to allow existing implementations to still comply; and alternate would be to restrict to just 1-125 and adjust the Rationale to alert the user to the change. |
||||||
Desired Action |
Change line 81542 (command EXIT STATUS) from: 126 The utility specified by command_name was found but could not be invoked. 127 An error occurred in the command utility or the utility specified by command_name could not be found. to: >0 An error occurred in the command utility 126 The utility specified by command_name was found but could not be invoked. 127 The utility specified by command_name could not be found. At line 81653 (command RATIONALE), add a new paragraph: Older versions of the standard required that failures internal to the command utility resulted in exit status 127; however implementations are encouraged to place the exit status in the range 1-125 for consistency with other forwarding utilities such as env. Change line 98151 (nohup EXIT STATUS) from: 126 The utility specified by utility was found but could not be invoked. 127 An error occurred in the nohup utility or the utility specified by utility could not be found. to: >0 An error occurred in the nohup utility 126 The utility specified by utility was found but could not be invoked. 127 The utility specified by utility could not be found. At line 98198 (nohup RATIONALE), add a new paragraph: Older versions of the standard required that failures internal to the nohup utility resulted in exit status 127; however implementations are encouraged to place the exit status in the range 1-125 for consistency with other forwarding utilities such as env. |
||||||
Tags | No tags attached. | ||||||
Attached Files | |||||||
|
Mantis 1.1.6[^] Copyright © 2000 - 2008 Mantis Group |