Date: Thu, 3 Jan 2008 22:10:34 +0200 From: Metin KAYA <metin@EnderUNIX.org> To: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@des.no> Cc: freebsd-hackers@freebsd.org, "Rick C. Petty" <rick-freebsd@kiwi-computer.com> Subject: Re[2]: select Message-ID: <172618207.20080103221034@EnderUNIX.org> In-Reply-To: <86prwid6tp.fsf@ds4.des.no> References: <1571995824.20080103205248@EnderUNIX.org><20080103192245.GB90170@keira.kiwi-computer.com><363446479.20080103213223@EnderUNIX.org> <86prwid6tp.fsf@ds4.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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? > Please don't top-post. > Like most other system calls that block "indefinitely", select(2) will > be interrupted by signals. This is *also* documented in the man page > you didn't read: > [EINTR] A signal was delivered before the time limit expired > and before any of the selected events occurred. > See sigaction(2) for details on how to modify the way system calls > behave when a signal is delivered. > DES Thanks. I've read select_tut(2) man page in FC8 but there is no such explanation about EINTR, so don't mind my this mistake. -- 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?172618207.20080103221034>