Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Date: Wed, 1 Nov 2000 13:46:21 -0500 From: Christopher Faylor To: cygwin@sources.redhat.com Subject: Re: 1.1.4, select, and SIGCHLD Message-ID: <20001101134621.N14818@redhat.com> Reply-To: cygwin@sources.redhat.com Mail-Followup-To: cygwin@sources.redhat.com References: <20001101165236.4513.qmail@web1306.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.6i In-Reply-To: <20001101165236.4513.qmail@web1306.mail.yahoo.com>; from robert_fidler@yahoo.com on Wed, Nov 01, 2000 at 08:52:36AM -0800 On Wed, Nov 01, 2000 at 08:52:36AM -0800, Robert Fidler wrote: >I am seeing behavior where a daemon process has multiple children die >'simultaneously' and subsequent calls to select() consistently return >-1 immediately with errno set to EINTR. This puts the daemon into a >tight spinloop and it becomes useless. If the child deaths are >sequential, the daemon behaves properly. > >I've seen this behavior on cygwin 1.1.4 and 1.1.5-2. Has anyone else >seen this behavior and is there a fix for it? No, and no. cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com