Re: fixing BLODA-caused fork failures

[Christopher Faylor <cgf-use-the-mailinglist-please at cygwin dot com>]

On Thu, Oct 03, 2013 at 04:55:19PM -0400, Adam Kellas wrote:
>My company uses Cygwin and we experience fairly frequent fork
>failures, believed to be BLODA-related. I say "believed to be" because
>in this corporate environment, like many, we cannot uninstall the
>virus scanner even long enough to see what happens without it. The
>presumed culprit in our case is Microsoft Forefront Endpoint
>Protection, by the way.
>
>So we need Cygwin and we're stuck with Forefront, putting us between a
>rock and a hard place. It's clear from the documentation and mailing
>list that the official stance wrt BLODA is "sorry, can't help you" and
>I understand and accept that. I'm looking for the answer to a related
>question: are BLODA-caused fork failures a logically unsolvable
>problem due to the way Windows works or is it just a matter of round
>tuits? In other words, if we were (hypothetically) able to pay someone
>to make MS Forefront and Cygwin play nicely together, would that have
>a chance of success? And would the Cygwin maintainers allow such work
>into the code base or consider it an unfortunate precedent?

It wouldn't be without precedent.  I've done work for companies before
and the work has made it into the code base.  But I can't predict if it
is even possible to make things work better in this case.

Contact me at "me at-sign cgf period cx" and we can discuss the
possibility of at least investigating what's involved.

--
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