From: "Iruata Souza" <iru.muzgo@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] Explanation of binding from ftpfs
Date: Sat, 6 Dec 2008 19:39:29 -0200 [thread overview]
Message-ID: <d1c554290812061339k2e17bcb2xfe9596d37b41cc52@mail.gmail.com> (raw)
In-Reply-To: <cca2e5880812061244m4ea907e5v81b8c4ca2c397b75@mail.gmail.com>
On Sat, Dec 6, 2008 at 6:44 PM, Brad Frank <brad.frank@gmail.com> wrote:
> When I use ftpfs to mount a ftp site and then bind /n/ftp to another
> location. All appears to work fine in /n/ftp and in the other
> location. When I type ns, I can clearly see the pipe bind for ftpfs
> mounted to /n/ftp. When I unmount /n/ftp I can type ls on /n/ftp and
> not see anything there. But if I ls on the other location that I bound
> to /n/ftp, it still can access the ftp server. How is the other
> location able to do this, when I don't see any indication of a pipe
> bind still listed in ns? I do see the ftpfs process running, though.
>
>
the bind shows here, like it should
cpu% ns | tail -3
mount -b '#s/rio.iru.323' /dev
mount -c '#|/data1' /n/ftp
cd /usr/iru
cpu% bind /n/ftp new
cpu% ns | tail -3
mount -c '#|/data1' /n/ftp
mount '#|/data1' /usr/iru/new
cd /usr/iru
cpu% lc /n/ftp | tail -1
pub
cpu% unmount /n/ftp
cpu% ns | tail -3
mount -b '#s/rio.iru.323' /dev
mount '#|/data1' /usr/iru/new
cd /usr/iru
cpu% lc /n/ftp
cpu% lc new | tail -1
pub
cpu% unmount new
cpu% ns | tail -3
mount '#s/rio.iru.323' /mnt/wsys 1
mount -b '#s/rio.iru.323' /dev
cd /usr/iru
i may be mistaken here but it seems that unmount calls cclose which
calls decref and only if the mount is the last reference to the
server, it will be freed.
the behaviour seems ok here, then.
iru
next prev parent reply other threads:[~2008-12-06 21:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-06 20:44 Brad Frank
2008-12-06 21:39 ` Iruata Souza [this message]
2008-12-06 22:17 ` Brad Frank
2008-12-06 22:27 ` Iruata Souza
2008-12-06 22:39 ` erik quanstrom
2008-12-06 22:52 ` Brad Frank
2008-12-06 22:53 ` Brad Frank
2008-12-06 23:06 ` Russ Cox
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=d1c554290812061339k2e17bcb2xfe9596d37b41cc52@mail.gmail.com \
--to=iru.muzgo@gmail.com \
--cc=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).