From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <75959811c030beb33eb82d0460fcd6ca@plan9.escet.urjc.es> To: russcox@gmail.com, 9fans@cse.psu.edu Subject: Re: [9fans] rio snarf From: "Fco. J. Ballesteros" Date: Wed, 27 Oct 2004 19:31:01 +0200 In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="upas-twvfuwqpkvugqgogeufrpaqxgz" Cc: Topicbox-Message-UUID: f7750026-eacd-11e9-9e20-41e7f4b1d025 This is a multi-part message in MIME format. --upas-twvfuwqpkvugqgogeufrpaqxgz Content-Disposition: inline Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Well. We just found that removing snarf from rio fsys makes things work great wrt sharing the snarf buffer across machines. At first, we thought that if was enough to call open(OTRUNC) while copying to the snarf buffer, then we noticed the deadlock with the open("/dev/snarf") in rio, then we tried removing snarf from rio, and, voila. Either I'm crazy because of the lots of coffee I have been drinking, or there is something I'm missing regarding why rio has snarf builtin instead of using a regular file for that. Hope my question was more clear now. cheers --upas-twvfuwqpkvugqgogeufrpaqxgz Content-Type: message/rfc822 Content-Disposition: inline Received: from mail.cse.psu.edu ([130.203.4.6]) by aquamar; Wed Oct 27 19:11:05 MDT 2004 Received: from psuvax1.cse.psu.edu (localhost [127.0.0.1]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id ECD1D63FE8 for ; Wed, 27 Oct 2004 13:10:56 -0400 (EDT) X-Original-To: 9fans@cse.psu.edu Delivered-To: 9fans@cse.psu.edu Received: from localhost (localhost [127.0.0.1]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id 5157D31EA4 for <9fans@cse.psu.edu>; Wed, 27 Oct 2004 13:10:48 -0400 (EDT) Received: from mail.cse.psu.edu ([127.0.0.1]) by localhost (psuvax1 [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 03644-02-39 for <9fans@cse.psu.edu>; Wed, 27 Oct 2004 13:10:46 -0400 (EDT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.198]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id AAED631E9B for <9fans@cse.psu.edu>; Wed, 27 Oct 2004 13:10:46 -0400 (EDT) Received: by wproxy.gmail.com with SMTP id 68so339703wri for <9fans@cse.psu.edu>; Wed, 27 Oct 2004 10:10:46 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=Wk0d5fqeIwM1u4jvryqInpTFXX4xSfgp1snResAdKMZIBdCr7zGp41B07qrt5tE9qbeUvQcbAwcxvjzxApj0kO3zarnYH7kPA1cBXb7pYaPDPatXsML/2aKbaGuYb5gIAfoMT1q59S0AkKztS/bLgUfKUTNGqGDnZH+g6r3wkDo= Received: by 10.38.96.46 with SMTP id t46mr1294121rnb; Wed, 27 Oct 2004 10:10:46 -0700 (PDT) Received: by 10.38.65.22 with HTTP; Wed, 27 Oct 2004 10:10:45 -0700 (PDT) Message-ID: Date: Wed, 27 Oct 2004 13:10:45 -0400 From: Russ Cox To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu> Subject: Re: [9fans] rio snarf In-Reply-To: <5b020b8175c46f4e109c845b719b17d3@plan9.escet.urjc.es> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <5b020b8175c46f4e109c845b719b17d3@plan9.escet.urjc.es> X-Virus-Scanned: by amavisd-new at cse.psu.edu X-BeenThere: 9fans@cse.psu.edu X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Russ Cox , Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu> List-Id: Fans of the OS Plan 9 from Bell Labs <9fans.cse.psu.edu> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: 9fans-bounces+nemo=lsub.org@cse.psu.edu Errors-To: 9fans-bounces+nemo=lsub.org@cse.psu.edu > Any reason why it updates on close rather than truncating on open(OTRUNC)? Surely you have a different question. Russ --upas-twvfuwqpkvugqgogeufrpaqxgz--