From owner-freebsd-stable@FreeBSD.ORG Thu Aug 7 05:32:56 2003 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 3671137B401 for ; Thu, 7 Aug 2003 05:32:56 -0700 (PDT) Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id 75C2343F3F for ; Thu, 7 Aug 2003 05:32:48 -0700 (PDT) (envelope-from ru@sunbay.com) Received: from whale.sunbay.crimea.ua (ru@localhost [127.0.0.1]) h77CWgfr006877 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 7 Aug 2003 15:32:42 +0300 (EEST) (envelope-from ru@sunbay.com) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.12.9/8.12.8/Submit) id h77CWgAj006876; Thu, 7 Aug 2003 15:32:42 +0300 (EEST) (envelope-from ru) Date: Thu, 7 Aug 2003 15:32:42 +0300 From: Ruslan Ermilov To: Stephen McKay Message-ID: <20030807123242.GB5904@sunbay.com> References: <200308071230.h77CUMgj003099@dungeon.home> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="eJnRUKwClWJh1Khz" Content-Disposition: inline In-Reply-To: <200308071230.h77CUMgj003099@dungeon.home> User-Agent: Mutt/1.5.4i cc: freebsd-stable@freebsd.org Subject: Re: nvi dying with "Resource temporarily unavailable" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Aug 2003 12:32:56 -0000 --eJnRUKwClWJh1Khz Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Aug 07, 2003 at 10:30:22PM +1000, Stephen McKay wrote: > Since I upgraded to FreeBSD 4.8 (from 4.5) I've noticed occasional failur= es > of nvi. It will suddenly die as a key is pressed, emitting: >=20 > Error: input: Resource temporarily unavailable >=20 > and you are staring at your command prompt. >=20 > I googled for this message and found that people here and there have been > complaining of this since about FreeBSD 4.2, but that absolutely none of > them have received a reply. >=20 > What's going on here? Down in the bowels of nvi a read of the pty returns > EAGAIN and that is treated as fatal. This should only occur with read() = if > the input is non-blocking, and as far as I can tell it isn't. >=20 > So, is this a nvi bug (read() returning EAGAIN should be non-fatal)? Is > this a pty bug (read() incorrectly returning EAGAIN)? Perhaps it could be > even an xterm bug? (Since I also upgraded to the XFree86 4.x series when= I > upgraded to FreeBSD 4.8 and maybe those other folks were early adopters). >=20 > Any ideas? >=20 stty sane Cheers, --=20 Ruslan Ermilov Sysadmin and DBA, ru@sunbay.com Sunbay Software Ltd, ru@FreeBSD.org FreeBSD committer --eJnRUKwClWJh1Khz Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE/MkbqUkv4P6juNwoRAv5gAJ420GjjlvHCZMYvP1V08O1dSMVABwCeJVgT bQdNTmaLzFtLXrr85xN9tzA= =BIpM -----END PGP SIGNATURE----- --eJnRUKwClWJh1Khz--