Subject: Re: vfork + /bin/sh
To: None <email@example.com>
From: Perry E. Metzger <firstname.lastname@example.org>
Date: 05/14/2000 22:49:21
Jason R Thorpe <email@example.com> writes:
> On Mon, May 15, 2000 at 02:00:17AM +0000, Geoff Wing wrote:
> > I thought we tried that path once (i.e. adding vfork() to sh) and it was
> > backed out for some reason. Maybe I'm totally wrong and am remembering
> > something else - sorry, I can't check the CVS logs until anoncvs comes
> > back up.
> I don't think anyone actually tried it ... sh is kinda scary inside.
We really need to run sh through some serious regression testing
following this change -- the inside is very scary indeed, and prone to
trouble. OTOH, the performance improvement here is very worthwhile.