Date: Wed, 30 Jun 2004 19:13:32 -0700 (PDT) From: Doug White <dwhite@gumbysoft.com> To: Mikhail Teterin <mi+mx@aldan.algebra.com> Cc: stable@FreeBSD.org Subject: Re: the dreaded "Resource temporarily unavailable" in vi Message-ID: <20040630191238.C66769@carver.gumbysoft.com> In-Reply-To: <200406301709.02239@misha-mx.virtual-estates.net> References: <200406301709.02239@misha-mx.virtual-estates.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 30 Jun 2004, Mikhail Teterin wrote: > It just started to happen again. Over and over, I open a file, start > editing, then -- at a random moment -- I get: ": input: Resource > temporarily unavailable" and vi exits.... > > Here is the ktrace/kdump snippet: > > 98705 vi CALL sigaction(0x12,0x280e792c,0) > 98705 vi RET sigaction 0 > 98705 vi CALL read(0,0x8090000,0xff) > 98705 vi RET read -1 errno 35 Resource temporarily unavailable > 98705 vi CALL sigaction(0x12,0x280e7914,0x280e792c) > 98705 vi RET sigaction 0 > > 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. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040630191238.C66769>