From:	cgf AT cygnus DOT com (Christopher G. Faylor)
Subject:	Re: socket/signal problem tracked down - comments?
7 May 1998 13:54:23 GMT :
Message-ID:	<6iseef$iqd$1@cronkite.cygnus.com>
References:	<m0yXJ0K-0011BMC DOT cygnus DOT gnu-win32 AT malasada DOT lava DOT net>
X-Newsreader:	trn 4.0-test63 (15 March 1998)

In article <m0yXJ0K-0011BMC DOT cygnus DOT gnu-win32 AT malasada DOT lava DOT net>,
Tim Newsham <newsham AT lava DOT net> wrote:
>As for immediate fix for the connect() problem -- what is the preferred
>way to block signals while I'm in cygwin winsup code?  Should I do
>normal sigset operations to set the mask, or is there a simpler mechanism
>such as grabbing a semaphore or setting a flag?

block_sig_dispatch() will block signals from being acted on.
allow_sig_dispatch() will turn on signals and act on any signals that
have been queued.
-- 
cgf AT cygnus DOT com             "Everything has a boolean value, if you stand
http://www.cygnus.com/      far enough away from it."  -- Galena Alyson Canada

- Raw text -