From: geoff@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Pull?
Date: Fri, 29 Dec 2006 13:33:17 -0500 [thread overview]
Message-ID: <aac29a257fc3b133044a8dd089f9d2d6@plan9.bell-labs.com> (raw)
In-Reply-To: <20061229051124.20307.qmail@g.galapagos.bx.psu.edu>
[-- Attachment #1: Type: text/plain, Size: 262 bytes --]
It's somewhat specific to our situation, but the idea is that if you
`9fs server' and you know that there's always a specific file in the
server's root,
if (test -e /n/server/known_file)
foo /n/server
will execute foo only if the 9fs really worked.
[-- Attachment #2: Type: message/rfc822, Size: 2653 bytes --]
From: Scott Schwartz <schwartz@bio.cse.psu.edu>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Pull?
Date: 29 Dec 2006 00:11:24 -0500
Date: Fri, 29 Dec 2006 00:11:24 -0500
Message-ID: <20061229051124.20307.qmail@g.galapagos.bx.psu.edu>
| There was a problem locally wherein losing a file server connection
| was making replica/scan think that all the files had vanished. I've
| taken measures to prevent it happening in future,
What sort of measures? I mean, is there a general purpose strategy that
you used, or is this a special case?
next prev parent reply other threads:[~2006-12-29 18:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-22 0:53 Dan Cross
2006-12-22 1:05 ` Paul Lalonde
2006-12-22 15:52 ` Dan Cross
2006-12-22 18:19 ` Axel Belinfante
2006-12-25 17:23 ` Aki Nyrhinen
2006-12-29 1:29 ` Martin Neubauer
2006-12-29 2:00 ` geoff
2006-12-29 5:11 ` Scott Schwartz
2006-12-29 7:48 ` Gabriel Diaz
2006-12-29 18:39 ` geoff
2006-12-29 20:30 ` Dan Cross
2006-12-29 21:35 ` geoff
2006-12-29 18:33 ` geoff [this message]
2006-12-29 14:30 ` Dan Cross
2006-12-29 15:05 ` Christian Grothaus
2006-12-29 17:19 ` Steve Simon
-- strict thread matches above, loose matches on Subject: below --
2003-10-23 23:58 Kris Van Hees
2003-10-24 0:58 ` rob pike, esq.
2003-10-24 0:59 ` mirtchov
2003-10-24 1:35 ` david presotto
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=aac29a257fc3b133044a8dd089f9d2d6@plan9.bell-labs.com \
--to=geoff@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).