From owner-freebsd-current Tue Apr 22 11:02:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA29303 for current-outgoing; Tue, 22 Apr 1997 11:02:19 -0700 (PDT) Received: from sovcom.relcom.ru (sovcom.relcom.ru [193.125.152.1]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id LAA29276; Tue, 22 Apr 1997 11:01:51 -0700 (PDT) Received: by sovcom.relcom.ru id AA16007 (5.65.kiae-1 ); Tue, 22 Apr 1997 20:33:40 +0300 Received: by sovcom.KIAE.su (UUMAIL/2.0); Tue, 22 Apr 97 20:33:39 +0300 Received: (from ache@localhost) by nagual.ru (8.8.5/8.8.5) id VAA00448; Tue, 22 Apr 1997 21:27:10 +0400 (MSD) Date: Tue, 22 Apr 1997 21:27:08 +0400 (MSD) From: =?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?= To: "John S. Dyson" Cc: Bruce Evans , current@freebsd.org, dyson@freebsd.org Subject: Re: Recent vfork kernel changes broke csh & tcsh! In-Reply-To: <199704221349.IAA02018@dyson.iquest.net> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 22 Apr 1997, John S. Dyson wrote: > > >> 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. Of course, else what the Subj. talk about? > Well, I am about ready to give up on the vfork thing... There > are bigger fish to fry :-). Can we left vfork at traditional BSD stage and not make it as powerful as rfork is? It seems some programs expect traditional semantics... BTW, alternative way will be fixing such programs to preserve more variables before forking, but it is relatively hard task. I try to see what csh child clobbers, but give up, i.e. can't find what it was. Preserving process list f.e. not helps... -- Andrey A. Chernov http://www.nagual.ru/~ache/