Date: Thu, 3 Jan 2008 21:32:23 +0200 From: Metin KAYA <metin@EnderUNIX.org> To: "Rick C. Petty" <rick-freebsd@kiwi-computer.com> Cc: freebsd-hackers@freebsd.org Subject: Re[2]: select Message-ID: <363446479.20080103213223@EnderUNIX.org> In-Reply-To: <20080103192245.GB90170@keira.kiwi-computer.com> References: <1571995824.20080103205248@EnderUNIX.org> <20080103192245.GB90170@keira.kiwi-computer.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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. > -- Rick C. Petty -- Metin KAYA EnderUNIX Software Developer Endersys Software Engineer http://www.EnderUNIX.org/metin http://www.Endersys.com/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?363446479.20080103213223>