From: "Russ Cox" <rsc@swtch.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] Vacfs/9pfuse problems?
Date: Wed, 10 Sep 2008 07:41:57 -0700 [thread overview]
Message-ID: <ee9e417a0809100741k4fa77e88o775f9bd7d3c4a1ec@mail.gmail.com> (raw)
In-Reply-To: <140e7ec30809092125i30635834kedce2d37dda93061@mail.gmail.com>
There may be two bugs here. One happens when you start 9pfuse in
one terminal and then interrupt a program in that same terminal.
Perhaps the shell sends the interrupt to the backgrounded 9pfuse
or 9p server too. If so, there is an rfork(RFNOTEG) missing somewhere.
The second is what happens when any I/O to the 9pfuse server
gets interrupted, in any terminal. That one:
> I see the same 9pfuse behaviour mounting ircfs or u9fs at work. If I
> interrupt some I/O, I lose the mount.
> Haven't seen the find problem, 9pfuse -D might be instructive there.
I think I fixed this on July 24.
http://hg.pdos.csail.mit.edu/hg/plan9/rev/18d28bd28f4b
Russ
next prev parent reply other threads:[~2008-09-10 14:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-09 13:49 Venkatesh Srinivas
2008-09-10 4:25 ` sqweek
2008-09-10 14:41 ` Russ Cox [this message]
2008-09-11 5:46 ` sqweek
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=ee9e417a0809100741k4fa77e88o775f9bd7d3c4a1ec@mail.gmail.com \
--to=rsc@swtch.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).