Date: Thu, 7 Aug 2003 15:32:42 +0300 From: Ruslan Ermilov <ru@freebsd.org> To: Stephen McKay <smckay@internode.on.net> Cc: freebsd-stable@freebsd.org Subject: Re: nvi dying with "Resource temporarily unavailable" Message-ID: <20030807123242.GB5904@sunbay.com> In-Reply-To: <200308071230.h77CUMgj003099@dungeon.home> References: <200308071230.h77CUMgj003099@dungeon.home>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] 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 failures > of nvi. It will suddenly die as a key is pressed, emitting: > > Error: input: Resource temporarily unavailable > > and you are staring at your command prompt. > > 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. > > 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. > > 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). > > Any ideas? > stty sane Cheers, -- Ruslan Ermilov Sysadmin and DBA, ru@sunbay.com Sunbay Software Ltd, ru@FreeBSD.org FreeBSD committer [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE/MkbqUkv4P6juNwoRAv5gAJ420GjjlvHCZMYvP1V08O1dSMVABwCeJVgT bQdNTmaLzFtLXrr85xN9tzA= =BIpM -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030807123242.GB5904>