netbsd-bugs: bin/287: /bin/sh does not set status variable to 126 or 127 when exec fails.

Subject: bin/287: /bin/sh does not set status variable to 126 or 127 when exec fails.
To: None <gnats-admin>
From: J.T. Conklin <jtc>
List: netbsd-bugs
Date: 06/11/1994 10:05:03

>Number:         287
>Category:       bin
>Synopsis:       /bin/sh does not set status variable to 126 or 127 when exec fails.
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    gnats-admin (Utility Bug People)
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Jun 11 10:05:03 1994
>Originator:     J.T. Conklin
>Organization:
Winning Strategies, Inc.
>Release:        NetBSD-current
>Environment:
	
System: NetBSD sun-lamp.cs.berkeley.edu 0.9B NetBSD 0.9B (SUN_LAMP) #1: Mon May 30 11:24:35 PDT 1994 mycroft@sun-lamp.cs.berkeley.edu:/usr/src/sys/arch/i386/compile/SUN_LAMP i386


>Description:
	POSIX.2 says that the shell should set the status variable ($?) to 
	either 126 or 127 when a command was found and could not be invoked
	or cound not be found respectively.

>How-To-Repeat:
	$ some-command-that-doesnt-exist
	$ echo $?

>Fix:
	?
>Audit-Trail:
>Unformatted:


------------------------------------------------------------------------------