From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 4 21:39:07 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DCF4416A41A for ; Fri, 4 Jan 2008 21:39:07 +0000 (UTC) (envelope-from metin@EnderUNIX.org) Received: from istanbul.enderunix.org (freefall.marmara.edu.tr [193.140.143.23]) by mx1.freebsd.org (Postfix) with ESMTP id F1D7213C448 for ; Fri, 4 Jan 2008 21:39:06 +0000 (UTC) (envelope-from metin@EnderUNIX.org) Received: (qmail 44151 invoked by uid 1040); 4 Jan 2008 21:19:36 -0000 Received: from unknown (HELO ?192.168.2.3?) (metin@78.185.157.122) by 0 with ESMTPA; 4 Jan 2008 21:19:35 -0000 Date: Fri, 4 Jan 2008 23:18:48 +0200 From: Metin KAYA X-Mailer: The Bat! (v3.98.4) Professional Organization: EnderUNIX X-Priority: 3 (Normal) Message-ID: <1643154686.20080104231848@EnderUNIX.org> To: "M. Warner Losh" In-Reply-To: <20080104.135421.96120312.imp@bsdimp.com> References: <1571995824.20080103205248@EnderUNIX.org><20080103192245.GB90170@keira.kiwi-computer.com><363446479.20080103213223@EnderUNIX.org> <20080104.135421.96120312.imp@bsdimp.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-SMTP-Filter: SurGATE SMTP Filter Engine Release 1.0.1 http://www.endersys.com X-SurGATE-Result: Clean (Content eval: -4.40 points) Cc: freebsd-hackers@freebsd.org, rick-freebsd@kiwi-computer.com Subject: Re[2]: select X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jan 2008 21:39:07 -0000 > In message: <363446479.20080103213223@EnderUNIX.org> > Metin KAYA writes: > : Yes Rick, I'm asking this "indefinitely" issue. Is there anything > : that handle this NULL situation a signal, or etc.? How does Linux or > : FreeBSD behave? > : : >> On Thu, Jan 03, 2008 at 08:52:48PM +0200, Metin KAYA wrote: : >>> : >>> How select(2) will behave if I give the "utimeout" parameter as : >>> NULL? > : : >> According to the man page: > : : >> If timeout is not a null pointer, it specifies the maximum interval to : >> wait for the selection to complete. System activity can lengthen the : >> interval by an indeterminate amount. > : : >> If timeout is a null pointer, the select blocks indefinitely. > : : >> To effect a poll, the timeout argument should not be a null pointer, but : >> it should point to a zero-valued timeval structure. > : > Indefinitely means "it won't return until there's an error or data" > Warner Thanks a lot Warner. It's a good explanation. -- Metin KAYA EnderUNIX Software Developer Endersys Software Engineer http://www.EnderUNIX.org/metin http://www.Endersys.com/