From owner-freebsd-questions@FreeBSD.ORG Mon Jul 14 15:42:32 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9DC4D37B401; Mon, 14 Jul 2003 15:42:32 -0700 (PDT) Received: from pit.databus.com (p70-227.acedsl.com [66.114.70.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id A6F5343FA3; Mon, 14 Jul 2003 15:42:31 -0700 (PDT) (envelope-from barney@pit.databus.com) Received: from pit.databus.com (localhost [127.0.0.1]) by pit.databus.com (8.12.9/8.12.9) with ESMTP id h6EMgNn8083629; Mon, 14 Jul 2003 18:42:23 -0400 (EDT) (envelope-from barney@pit.databus.com) Received: (from barney@localhost) by pit.databus.com (8.12.9/8.12.9/Submit) id h6EMgLxX083628; Mon, 14 Jul 2003 18:42:21 -0400 (EDT) (envelope-from barney) Date: Mon, 14 Jul 2003 18:42:21 -0400 From: Barney Wolff To: Mikhail Teterin Message-ID: <20030714224221.GA83394@pit.databus.com> References: <200307141808.32439@misha-mx.virtual-estates.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200307141808.32439@misha-mx.virtual-estates.net> User-Agent: Mutt/1.4.1i cc: questions@freebsd.org cc: current@freebsd.org Subject: Re: ``Resource temporarily unavailable'' in vi X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Jul 2003 22:42:32 -0000 On Mon, Jul 14, 2003 at 06:08:32PM -0400, Mikhail Teterin wrote: > Every once in a while, a vi-session dies on me with: > > input: Resource temporarily unavailable > > What does it mean, why does it happen, and how can I prevent it? I suspect vi's not handling an EAGAIN error return. I get this on -stable when ripping a cd with grip/cdda2wav. Are you doing something that runs at very high priority when it happens? Judging from the comments in /usr/src/sys/errno.h, it could also be that there is a resource deadlock and vi is not translating the errno correctly. Anyway, pending a fix in vi to handle retryable errors, the workaround is not to do whatever it is that you're doing at the same time. -- Barney Wolff http://www.databus.com/bwresume.pdf I'm available by contract or FT, in the NYC metro area or via the 'Net.