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] question about union dirs
Date: Fri, 20 Sep 2002 13:10:00 -0400	[thread overview]
Message-ID: <b5eab453d32a0cad4141ac917ddf2b7d@plan9.bell-labs.com> (raw)

> In the TCP case, suppose this search is the first
> operation since the disconnection occurred (no prior
> outstanding tcp transmissions).  Does the search block
> until TCP gives up (13 or so minutes later), or is
> the "hungup" condition somehow marked sooner?

Yes, it blocks, but TCP should give up after 30 seconds.

> Can the user (of say rc) discover this?  For example,
> suppose I expect to be getting /bin/foo from the
> disconnected service.  If I quietly get a different
> /bin/foo from something further down the union, I might
> be baffled.

If the user knew what the mount number for
that connection was, ls -l would show different
numbers.  For example:

g% ls -l /n/kfs/adm/users
--rw-rw-r-- M 25 adm adm 140 Aug 28 08:37 /n/kfs/adm/users
g% ls -l /n/emelie/adm/users
--rw-rw-r-- M 57 adm adm 10458 Jul 19 11:08 /n/emelie/adm/users
g% ls -l /n/kfs/adm/users
--rw-rw-r-- M 57 adm adm 10458 Jul 19 11:08 /n/kfs/adm/users
g% ls -l /n/kfs/adm|grep users
--rw-rw-r-- M 57 adm      adm   10458 Jul 19 11:08 /n/kfs/adm/users
--rw-rw-r-- M 25 adm      adm     140 Aug 28 08:37 /n/kfs/adm/users
g%

The 'M 25' says that this file is coming from the
mount device (it's a 9P service rather than a kernel
device) instance number 25.  Each mount gets a
different instance number.

Russ



             reply	other threads:[~2002-09-20 17:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-20 17:10 Russ Cox [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-09-20 16:38 vic
2002-09-20 16:15 Russ Cox
2002-09-20 15:32 vic

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=b5eab453d32a0cad4141ac917ddf2b7d@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).