From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 3 19:53:32 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 003A116A417 for ; Thu, 3 Jan 2008 19:53:31 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id AEBDF13C457 for ; Thu, 3 Jan 2008 19:53:31 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id 1E6C220B1; Thu, 3 Jan 2008 20:53:23 +0100 (CET) X-Spam-Tests: AWL X-Spam-Learn: disabled X-Spam-Score: -0.1/3.0 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on tim.des.no Received: from ds4.des.no (des.no [80.203.243.180]) by smtp.des.no (Postfix) with ESMTP id 8FB99209C; Thu, 3 Jan 2008 20:53:22 +0100 (CET) Received: by ds4.des.no (Postfix, from userid 1001) id 656C3844C3; Thu, 3 Jan 2008 20:53:22 +0100 (CET) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Metin KAYA References: <1571995824.20080103205248@EnderUNIX.org> <20080103192245.GB90170@keira.kiwi-computer.com> <363446479.20080103213223@EnderUNIX.org> Date: Thu, 03 Jan 2008 20:53:22 +0100 In-Reply-To: <363446479.20080103213223@EnderUNIX.org> (Metin KAYA's message of "Thu\, 3 Jan 2008 21\:32\:23 +0200") Message-ID: <86prwid6tp.fsf@ds4.des.no> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.1 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-hackers@freebsd.org, "Rick C. Petty" Subject: Re: 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: Thu, 03 Jan 2008 19:53:32 -0000 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? 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 --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no