Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Message-ID:	<20001101165236.4513.qmail@web1306.mail.yahoo.com>
Date:	Wed, 1 Nov 2000 08:52:36 -0800 (PST)
From:	Robert Fidler <robert_fidler AT yahoo DOT com>
Subject:	1.1.4, select, and SIGCHLD
To:	cygwin AT sources DOT redhat DOT com
MIME-Version:	1.0

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?

Thanks,
Robert


Robert Fidler
INRANGE Technologies
Fairfax, VA


__________________________________________________
Do You Yahoo!?
From homework help to love advice, Yahoo! Experts has your answer.
http://experts.yahoo.com/

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -