Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 04 Jan 2008 13:54:21 -0700 (MST)
From:      "M. Warner Losh" <imp@bsdimp.com>
To:        metin@EnderUNIX.org
Cc:        freebsd-hackers@freebsd.org, rick-freebsd@kiwi-computer.com
Subject:   Re: select
Message-ID:  <20080104.135421.96120312.imp@bsdimp.com>
In-Reply-To: <363446479.20080103213223@EnderUNIX.org>
References:  <1571995824.20080103205248@EnderUNIX.org> <20080103192245.GB90170@keira.kiwi-computer.com> <363446479.20080103213223@EnderUNIX.org>

next in thread | previous in thread | raw e-mail | index | archive | help
In message: <363446479.20080103213223@EnderUNIX.org>
            Metin KAYA <metin@EnderUNIX.org> 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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080104.135421.96120312.imp>