This is the mail archive of the
cygwin@sourceware.cygnus.com
mailing list for the Cygwin project.
Re: call_handler, interrupt_now and interruptible
- To: Heribert Dahms <heribert_dahms at icon-gmbh dot de>
- Subject: Re: call_handler, interrupt_now and interruptible
- From: "'Chris Faylor'" <cgf at cygnus dot com>
- Date: Fri, 4 Feb 2000 18:26:03 -0500
- Cc: "Fifer, Eric" <EFifer at sanwaint dot com>, "'Ray Easton'" <ray dot easton at wcom dot com>, cygwin at sourceware dot cygnus dot com
- References: <99B82AA9708ED0119B55006097125A002DE8F5@ifk63.mach.uni-karlsruhe.de>
On Fri, Feb 04, 2000 at 10:45:14PM +0100, Heribert Dahms wrote:
>I guess this breaks now my code, which basically does a select() until
>a socket becomes readable, starts a loop preparing a timeout with
>alarm(60) for the following blocking fgets(), which is normally reset
>using alarm(0) after each line, but is supposed to be interrupted in
>case of a bad behaving client?
Why have you reached this conclusion? Have you actually
noticed this behavior? The changes that I made should not
have eliminated functionality in anything but DLLs and
that is only temporary.
If this is just supposition, then try the cygwin DLL. There
is no need to speculate about things breaking if you haven't
actually checked the code in question.
cgf
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com