Date: Thu, 13 Nov 2003 04:56:42 -0500 (EST) From: der Mouse <mouse@Rodents.Montreal.QC.CA> To: hackers@openbsd.org, tech-kern@NetBSD.org, freebsd-hackers@freebsd.org Subject: Re: kqueue, NOTE_EOF Message-ID: <200311131004.FAA25087@Sparkle.Rodents.Montreal.QC.CA> In-Reply-To: <200311130926.hAD9Q3jv024862@s102-n054.tele2.cz> References: <200311130926.hAD9Q3jv024862@s102-n054.tele2.cz>
next in thread | previous in thread | raw e-mail | index | archive | help
>> I think the difference is in the default behavior. When you're at >> EOF, I know that poll() will give you a read-availability event, so >> you'll read the EOF. Will kqueue? > AFAIK yes for sockets, not for file descriptor (i.e. descriptor open > to a file on filesystem). Would poll() give you read-availability > event when on end of file on filesystem. IMO it should, since a read() wouldn't block. When I tried it (admittedly against a rather old kernel) it does. /~\ The ASCII der Mouse \ / Ribbon Campaign X Against HTML mouse@rodents.montreal.qc.ca / \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200311131004.FAA25087>