Austin Group Defect Tracker

Aardvark Mark IV


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

- Relationships

-  Notes
(0000258)
msbrown (manager)
2009-10-15 15:45

The proposal as stated would cause non-conformance in currently conforming implementations, and by allowing multiple behaviors would make implementations less portable.

If submitter wishes to make refinements to the proposal to correct these perceived deficiencies, it is requested the it be done as an enhancement request for a future revision of the standard.

- Issue History
Date Modified Username Field Change
2009-10-09 12:09 eblake New Issue
2009-10-09 12:09 eblake Status New => Under Review
2009-10-09 12:09 eblake Assigned To => ajosey
2009-10-09 12:09 eblake Name => Eric Blake
2009-10-09 12:09 eblake Organization => N/A
2009-10-09 12:09 eblake User Reference => ebb.nohup
2009-10-09 12:09 eblake Section => nohup
2009-10-09 12:09 eblake Page Number => 2979
2009-10-09 12:09 eblake Line Number => 98152
2009-10-15 15:45 msbrown Interp Status => ---
2009-10-15 15:45 msbrown Note Added: 0000258
2009-10-15 15:45 msbrown Severity Objection => Comment
2009-10-15 15:45 msbrown Type Error => Enhancement Request
2009-10-15 15:45 msbrown Status Under Review => Resolved
2009-10-15 15:45 msbrown Resolution Open => Rejected


Mantis 1.1.6[^]
Copyright © 2000 - 2008 Mantis Group
Powered by Mantis Bugtracker