From owner-freebsd-current@FreeBSD.ORG Tue Jul 15 02:11:49 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 073C037B401 for ; Tue, 15 Jul 2003 02:11:49 -0700 (PDT) Received: from heron.mail.pas.earthlink.net (heron.mail.pas.earthlink.net [207.217.120.189]) by mx1.FreeBSD.org (Postfix) with ESMTP id 77EAF43F75 for ; Tue, 15 Jul 2003 02:11:48 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from user-38lc12t.dialup.mindspring.com ([209.86.4.93] helo=mindspring.com) by heron.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 19cLqJ-0002CM-00; Tue, 15 Jul 2003 02:11:28 -0700 Message-ID: <3F13C4B0.636DC603@mindspring.com> Date: Tue, 15 Jul 2003 02:09:04 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Mark Murray References: <200307150653.h6F6r0gG092242@grimreaper.grondar.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a4114a60be1756f10970be1bc78786fc28350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c cc: Mikhail Teterin cc: current@freebsd.org Subject: Re: ``Resource temporarily unavailable'' in vi X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Jul 2003 09:11:49 -0000 Mark Murray wrote: > Mikhail Teterin writes: > > 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'm seeing this on current. I use bash, and the machine is not > loaded. The heaviest process is spamassassin. There isn't even X running > on the box. One way to track this down, if it's that repeatable for everyone, would be to open another terminal window, get the pid of the program that's going to do this, and then: truss -p | grep "Resource temp" ...or just let it run to completion, and you'll get some context, too, in your scrollback buffer. Knowing what system call is failing would be very helpful toward tracking the problem down. -- Terry