From: rob@plan9.bell-labs.com rob@plan9.bell-labs.com
Subject: [9fans] Re: bug in aux/listen
Date: Tue, 16 Sep 1997 15:25:49 -0400 [thread overview]
Message-ID: <19970916192549.45nJe6ep4habxLVsm8KKnvQA16HCJlYpmPvUHInQ370@z> (raw)
> 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.
The flag gets set on the segment, not the process. Any process created
with that segment mapped will see the same segment.
-rob
next reply other threads:[~1997-09-16 19:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-09-16 19:25 rob [this message]
-- strict thread matches above, loose matches on Subject: below --
1997-09-16 20:00 G.David
1997-09-16 18:57 G.David
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=19970916192549.45nJe6ep4habxLVsm8KKnvQA16HCJlYpmPvUHInQ370@z \
--to=rob@plan9.bell-labs.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).