From owner-freebsd-current  Tue Apr 22 06:55:07 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id GAA15907
          for current-outgoing; Tue, 22 Apr 1997 06:55:07 -0700 (PDT)
Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA15902;
          Tue, 22 Apr 1997 06:55:02 -0700 (PDT)
Received: (from root@localhost) by dyson.iquest.net (8.8.4/8.6.9) id IAA02018; Tue, 22 Apr 1997 08:49:23 -0500 (EST)
From: "John S. Dyson" <toor@dyson.iquest.net>
Message-Id: <199704221349.IAA02018@dyson.iquest.net>
Subject: Re: Recent vfork kernel changes broke csh & tcsh!
In-Reply-To: <199704221236.WAA18843@godzilla.zeta.org.au> from Bruce Evans at "Apr 22, 97 10:36:08 pm"
To: bde@zeta.org.au (Bruce Evans)
Date: Tue, 22 Apr 1997 08:49:23 -0500 (EST)
Cc: ache@nagual.ru, current@FreeBSD.ORG, dyson@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL31 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> >> Both csh and tcsh affected in the similar way.
> >
> >I forgot to mention that I am shure it is vfork problem because it
> >disappearse when I change vfork to fork in csh or tcsh.
> 
> It wasn't completely clear that you have to start from csh or tcsh
> to see the bug.
> 
Well, I am about ready to give up on the vfork thing...  There
are bigger fish to fry :-).

John