From owner-freebsd-stable@FreeBSD.ORG Thu Jul 1 02:44:01 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AE73B16A4CE for ; Thu, 1 Jul 2004 02:44:01 +0000 (GMT) Received: from tinker.exit.com (tinker.exit.com [206.223.0.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5FC0543D5C for ; Thu, 1 Jul 2004 02:43:57 +0000 (GMT) (envelope-from frank@exit.com) Received: from realtime.exit.com (realtime [206.223.0.5]) by tinker.exit.com (8.12.11/8.12.9) with ESMTP id i612hOXr015814; Wed, 30 Jun 2004 19:43:25 -0700 (PDT) (envelope-from frank@exit.com) Received: from realtime.exit.com (localhost [127.0.0.1]) by realtime.exit.com (8.12.11/8.12.9) with ESMTP id i612hOCv003815; Wed, 30 Jun 2004 19:43:24 -0700 (PDT) (envelope-from frank@realtime.exit.com) Received: (from frank@localhost) by realtime.exit.com (8.12.11/8.12.11/Submit) id i612hOpS003814; Wed, 30 Jun 2004 19:43:24 -0700 (PDT) (envelope-from frank) From: Frank Mayhar Message-Id: <200407010243.i612hOpS003814@realtime.exit.com> In-Reply-To: <20040630191238.C66769@carver.gumbysoft.com> To: Doug White Date: Wed, 30 Jun 2004 19:43:24 -0700 (PDT) X-Copyright0: Copyright 2004 Frank Mayhar. All Rights Reserved. X-Copyright1: Permission granted for electronic reproduction as Usenet News or email only. X-Mailer: ELM [version 2.4ME+ PL99f (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII cc: Mikhail Teterin cc: stable@freebsd.org Subject: Re: the dreaded "Resource temporarily unavailable" in vi X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: frank@exit.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jul 2004 02:44:01 -0000 Doug White wrote: > On Wed, 30 Jun 2004, Mikhail Teterin wrote: > > read(2) is failing? > yes we know. I've debugged this myself and its not clear WHY its > returning EAGAIN. Also hacking vi to handle EAGAIN here is very difficult, > and really it should handle it. One (small) datapoint, I seem to see it much more often when I'm using an ssh session that also has an X application (evolution, mostly) running in the background. I haven't really tested this, I just have the somewhat vague impression that if I avoid "the session with evolution running," I won't run into the problem. FWIW. -- Frank Mayhar frank@exit.com http://www.exit.com/ Exit Consulting http://www.gpsclock.com/ http://www.exit.com/blog/frank/