This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Clearing O_NONBLOCK from a pipe may lose data
- From: Thomas Wolff <towo at towo dot net>
- To: cygwin at cygwin dot com
- Date: Tue, 24 Feb 2015 08:16:54 +0100
- Subject: Re: Clearing O_NONBLOCK from a pipe may lose data
- Authentication-results: sourceware.org; auth=none
- References: <20150222220747 dot 789401d2 at tukaani dot org> <20150223105653 dot GG437 at calimero dot vinschen dot de> <20150223122345 dot GM437 at calimero dot vinschen dot de>
Lasse Collin had written.
... the possibility of EINTR is mentioned for specific commands and F_SETFL isn't among them.
A subtle and maybe minor but valid objection.
Am 23.02.2015 um 13:23 schrieb Corinna Vinschen:
On Feb 23 11:56, Corinna Vinschen wrote:
On Feb 22 22:07, Lasse Collin wrote:
Alternative idea: Would there be a significant downside if Cygwin
remembered if non-blocking mode was enabled at some point and close()
would use that flag instead of the current (non)blocking status to
determine if the background thread hack should be used?
No, that should be doable with very minor effort.
That's still an option, of course.
I think that sounds like a solution.
------
Thomas
---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprÃft.
http://www.avast.com
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple