From: G. David Butler gdb@dbSystems.com
Subject: [9fans] Re: bug in aux/listen
Date: Tue, 16 Sep 1997 13:57:30 -0500 [thread overview]
Message-ID: <19970916185730.5MmRE8-456qYK1zexi6LshjRUlSPGVPzoy6lgzNi3Ao@z> (raw)
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.
next reply other threads:[~1997-09-16 18:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-09-16 18:57 G.David [this message]
1997-09-16 19:25 rob
1997-09-16 20:00 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=19970916185730.5MmRE8-456qYK1zexi6LshjRUlSPGVPzoy6lgzNi3Ao@z \
--to=9fans@9fans.net \
/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).