Date: Mon, 16 Jun 2003 14:39:36 -0400 From: Eric Jacobs <eaja@erols.com> To: freebsd-hackers@freebsd.org Subject: Re: kqueue alternative? Message-ID: <20030616143936.71007de2.eaja@erols.com> In-Reply-To: <20030616171110.GC56734@webserver.get-linux.org> References: <1079.10.0.81.10.1055692530.squirrel@www.mundomateo.com> <Pine.NEB.3.96L.1030615125423.98988D-100000@fledge.watson.org> <Pine.NEB.3.96L.1030615125423.98988D-100000@fledge.watson.org> <E19RrTD-0006yV-00@chiark.greenend.org.uk> <20030616171110.GC56734@webserver.get-linux.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 16 Jun 2003 10:11:10 -0700 Joshua Oreman <oremanj@www.get-linux.org> wrote: > On Mon, Jun 16, 2003 at 11:44:15AM +0100 or thereabouts, Tony Finch seemed to write: > > > > Select doesn't work with files. > > Really? `man 2 select' says nothing about that. It just talks about > 'file descriptors'. Now if it said 'socket descriptors' or 'non-file > file descriptors' I would understand, but I don't think that that statement > is implied by the man page. Is there something I'm missing? A file descriptor that references an ordinary vnode (file or directory) will always be "ready for I/O", because unlike a socket or pipe, it never needs to block in order to tell you if it's at EOF. So, while it works, and is logical, it isn't terribly useful.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030616143936.71007de2.eaja>