From mboxrd@z Thu Jan  1 00:00:00 1970
Date: Tue, 16 Sep 1997 13:57:30 -0500
From: G. David Butler gdb@dbSystems.com
Subject: [9fans] Re: bug in aux/listen
Topicbox-Message-UUID: 6647cbf6-eac8-11e9-9e20-41e7f4b1d025
Message-ID: <19970916185730.5MmRE8-456qYK1zexi6LshjRUlSPGVPzoy6lgzNi3Ao@z>

From: forsyth@plan9.cs.york.ac.uk
Date: 	Wed, 12 Jun 1996 08:53:05 -0400
subject: bug in aux/listen

>aux/listen does an rfork sharing memory to create the listener for
>each service.  that also ensures that
>	Subsequent forks by the parent will then
>	propagate the shared data and bss between children.
>	[rfork(2)]
>aux/listen later forks a process to handle each incoming call.
>that doesn't specify RFMEM, but is still sharing memory.

Going through some old stuff and I found this one.  I think you
are miss reading the above line from rfork(2).  I think it is
saying that subsequent forks by the *parent*, if called with RFMEM,
will share data and bss between children of the *parent*.  Subsequent
forks of the children are not affected unless they too do a RFMEM.

I verified this behavour by the code in sysproc.c and segment.c.