Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Subject:	Re: signals and read blocking - EINTR
In-Reply-To:	From Samuel Thibault at "Nov 1, 2005 12:48:03 pm"
From:	Jim Easton <jim AT cs DOT ualberta DOT ca>
To:	Samuel Thibault <samuel DOT thibault AT ens-lyon DOT org>
Date:	Wed, 2 Nov 2005 01:10:13 -0700 (MST)
CC:	Jim Easton <jim AT cs DOT ualberta DOT ca>, cygwin AT cygwin DOT com
Message-Id:	<S577272AbVKBIKN/20051102081023Z+166@sunkay.cs.ualberta.ca>
X-IsSubscribed:	yes

Hi

Samuel Thibald wrote:
> Mmm, I had a look at posix, at it says "The state of these flags is
> not specified for signal()." So that you indeed need to explicitely
> unset the flag, else the behavior is implementation-dependant (BSD sets
> SA_RESTART and clears SA_RESETHAND for instance).
> 
> Alternatively, siginterrupt() might be useful, but sigaction is
> preferred.
> 
> Regards,
> Samuel

Yes, I will keep that in mind.

There are a couple of other flags that are set on the other
architectures which I haven't investigated yet (read; I don't know
what they do), but it's working now on Cygwin, Solaris, SGI, AIX and
Linux.  (The sun4s need a little tweeking)

Thank you and Chris Faylor for your help - much appreciated.

	Jim


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -