From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <140e7ec30809102246y5da1fa90wb97eebf62788d417@mail.gmail.com>
Date: Thu, 11 Sep 2008 13:46:04 +0800
From: sqweek <sqweek@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
In-Reply-To: <ee9e417a0809100741k4fa77e88o775f9bd7d3c4a1ec@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <20080909134936.GB10171@meep>
	<140e7ec30809092125i30635834kedce2d37dda93061@mail.gmail.com>
	<ee9e417a0809100741k4fa77e88o775f9bd7d3c4a1ec@mail.gmail.com>
Subject: Re: [9fans] Vacfs/9pfuse problems?
Topicbox-Message-UUID: 0f68a326-ead4-11e9-9d60-3106f5b1d025

On Wed, Sep 10, 2008 at 10:41 PM, Russ Cox <rsc@swtch.com> wrote:
> There may be two bugs here.  One happens when you start 9pfuse in
> one terminal and then interrupt a program in that same terminal.

 This looks fine, I can start 9pfuse and then in the same terminal
ctrl-c to my heart's content without killing 9pfuse.

> The second is what happens when any I/O to the 9pfuse server
> gets interrupted, in any terminal.  That one:
>
> I think I fixed this on July 24.
> http://hg.pdos.csail.mit.edu/hg/plan9/rev/18d28bd28f4b

 Yep, seems to be fixed after updating to tip. Thanks!
-sqweek