Subject: Re: another vfork shell regression
To: David Laight <david@l8s.co.uk>
From: Greywolf <greywolf@starwolf.com>
List: current-users
Date: 10/23/2002 13:08:24
On Wed, 23 Oct 2002, David Laight wrote:
#
# The wrong process is aborting when variable assignment fails
# in the vfork path.  So the following command fails to execute
# the second echo (shown here with the correct output).
#
# $ (readonly r; r= /bin/echo a; echo b)
# r: is read only
# b
#
# fix: defer the mklocal() to the child shell.
#
# Also 'jobs' fails in a non-interactive shell.
# In showjobs(), the code that puts the process back into its
# own process group should only be run if the shell is actually
# doing job control - eg if 'mflag' is set.

Is this all recent?  My -current (1.6D) /bin/sh seems to be handling
everything correctly.

Is it the shell or the system semantics which have changed to cause
these problems?

				--*greywolf;
--
NetBSD: Resistance is futile!  You will be supported.