NetBSD Problem Report #287

From gnats  Sat Jun 11 10:01:55 1994
Received: (from jtc@localhost) by sun-lamp.cs.berkeley.edu (8.6.9/8.6.9) id KAA23602; Sat, 11 Jun 1994 10:01:55 -0700
Message-Id: <[email protected]>
Date: Sat, 11 Jun 1994 10:01:55 -0700
From: "J.T. Conklin" <jtc>
Reply-To: [email protected]
To: [email protected]
Subject: /bin/sh does not set status variable to 126 or 127 when exec fails.
X-Send-Pr-Version: 3.2

>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:    jtc
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Jun 11 10:05:03 +0000 1994
>Closed-Date:    Wed Oct 16 14:36:06 +0000 1996
>Last-Modified:  Wed Oct 16 14:36:32 +0000 1996
>Originator:     J.T. Conklin
>Release:        NetBSD-current
>Organization:
Winning Strategies, Inc.
>Environment:

System: NetBSD sun-lamp.cs.berkeley.edu 0.9B NetBSD 0.9B (SUN_LAMP) #1: Mon May 30 11:24:35 PDT 1994 [email protected]:/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:
	?
>Release-Note:
>Audit-Trail:

Responsible-Changed-From-To: gnats-admin->jtc
Responsible-Changed-By: jtc
Responsible-Changed-When: Sat Jun 18 07:33:15 1994
Responsible-Changed-Why:
Working on fix.

State-Changed-From-To: open->closed 
State-Changed-By: christos 
State-Changed-When: Wed Oct 16 10:36:06 EDT 1996 
State-Changed-Why:  
Fixed. 
>Unformatted:

Home	PR Database Search