9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Drawterm session close??
Date: Fri,  8 Mar 2002 20:53:43 -0500	[thread overview]
Message-ID: <6a19626458e13903ed8dcf4a40eab71e@plan9.bell-labs.com> (raw)

> > I'm not sure why the processes are left over.
> > Usually a name space loop, but in this case
> > that would mean rio has fs in its namespace
> > and fs has rio in its namespace, but I don't
> > think you can set things up that way.
> Can you elaborate this point? I have no clue
> what you are referring to.

File servers like rio and fs stick around until
the last references to their file servies go away.
Those references take the form of other processes
that have them mounted or the service files they
post in /srv.  (Actually the ref count is on the
pipe that you are serving 9P over.)

So: if rio has upas/fs mounted, and upas/fs has
rio mounted, then you have a ref count loop and
won't take them down.  You can accomplish an
easier ref count loop by writing a file server
that mounts itself.  This is why file servers
do rfork(RFNOTEG) before entering the service
loop.

It would be helpful to see the stacks of the
processes involved.  You can do

	chmod +rw /proc/pid/ctl
	acid pid
	stk()

to look at them (assuming you are bootes).

Russ


             reply	other threads:[~2002-03-09  1:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-09  1:53 Russ Cox [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-03-08 22:36 Russ Cox
2002-03-09  1:47 ` Ish Rattan
2002-03-08 19:47 Ish Rattan

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=6a19626458e13903ed8dcf4a40eab71e@plan9.bell-labs.com \
    --to=rsc@plan9.bell-labs.com \
    --cc=9fans@cse.psu.edu \
    /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).