Date: Sat, 12 Apr 1997 21:43:27 -0500 (EST) From: "John S. Dyson" <toor@dyson.iquest.net> To: jb@cimlogic.com.au (John Birrell) Cc: dyson@freefall.freebsd.org, CVS-committers@freefall.freebsd.org, cvs-all@freefall.freebsd.org, cvs-sys@freefall.freebsd.org Subject: Re: cvs commit: src/sys/i386/ibcs2 imgact_coff.c src/sys/i386/i386 pmap.c src/sys/i386/linux imgact_linux.c src/sys/kern imgact Message-ID: <199704130243.VAA03235@dyson.iquest.net> In-Reply-To: <199704130231.MAA05870@freebsd1.cimlogic.com.au> from John Birrell at "Apr 13, 97 12:31:42 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
> > > Implement rfork(!RFPROC !RFMEM), which allows a thread to divorce its memory > > from the other threads of a group. > > > > Implement rfork(!RFPROC RFCFDG), which closes all file descriptors, eliminating > > possible existing shares with other threads/processes. > > > > Implement rfork(!RFPROC RFFDG), which divorces the file descriptors for a > > thread from the rest of the group. > > > > Fix the case where a thread does an exec. It is almost nonsense for a thread > > to modify the other threads address space by an exec, so we > > now automatically divorce the address space before modifying it. > [...] > > Where do these changes leave rfork(!RFPROC RFMEM !RFFDG)??? 8-) > It will divorce memory. It won't modify the file descriptors if both !RFFDG and !RFCFDG. I think that for the bits that I have implemented in the !RFPROC case, it will work as expected. John
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199704130243.VAA03235>