Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 19 Apr 1996 10:17:24 -0400 (EDT)
From:      Sujal Patel <smpatel@umiacs.umd.edu>
To:        Lars Gerhard Kuehl <lars@elbe.desy.de>
Cc:        current@FreeBSD.ORG
Subject:   Re: Changes for vfork()
Message-ID:  <Pine.NEB.3.92.960419101637.1260D-100000@xi.dorm.umd.edu>
In-Reply-To: <9604191322.AA07511@elbe.desy.de>

next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 19 Apr 1996, Lars Gerhard Kuehl wrote:

> The current vfork() already doesn't allow the child to alter the parent's
> address space and sometimes it's very desirable (or at least convenient)
> if one can rely on the parent being suspended until the child calls
> execve() or _exit().

Convenient perhaps, but this is by no means correct (or desirable).  If
you really want to alter the parent's address space, you should fork with
rfork (RFPROC|RFMEM)


Sujal




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.92.960419101637.1260D-100000>