From owner-freebsd-hackers@FreeBSD.ORG Mon May 21 07:58:03 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1AA0616A421 for ; Mon, 21 May 2007 07:58:03 +0000 (UTC) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (gate.funkthat.com [69.17.45.168]) by mx1.freebsd.org (Postfix) with ESMTP id EB54E13C46A for ; Mon, 21 May 2007 07:58:02 +0000 (UTC) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (k0zppwk9c8xc713x@localhost.funkthat.com [127.0.0.1]) by hydrogen.funkthat.com (8.13.6/8.13.3) with ESMTP id l4L7vxfJ047497; Mon, 21 May 2007 00:57:59 -0700 (PDT) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.13.6/8.13.3/Submit) id l4L7vw8J047496; Mon, 21 May 2007 00:57:58 -0700 (PDT) (envelope-from jmg) Date: Mon, 21 May 2007 00:57:58 -0700 From: John-Mark Gurney To: Daniel Molina Wegener Message-ID: <20070521075757.GG4602@funkthat.com> Mail-Followup-To: Daniel Molina Wegener , FreeBSD Hackers References: <200705201831.38828.dmw@unete.cl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200705201831.38828.dmw@unete.cl> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 5.4-RELEASE-p6 i386 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html Cc: FreeBSD Hackers Subject: Re: kqueue implementation X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: John-Mark Gurney List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 May 2007 07:58:03 -0000 Daniel Molina Wegener wrote this message on Sun, May 20, 2007 at 18:31 -0400: > I'm coding an application using the kqueue facility, but > I see that I can't handle open and read events. Is planned to > implement these handlings in the future?. Also, which facility > can I use to handle these kind of events? I'm unsure what you mean by open and read events? Do you mean getting an event when another process opens are file? or? As for read, they work fine for sockets, as w/ select, files are always ready to read even though they may block to read from disk... -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not."