X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:date:message-id:subject:from:to
	:content-type; q=dns; s=default; b=rr4O/o3uwsGKk54m0C4kE76uj9R64
	EQw1jw484X+u+TqWPp3HP6KMnrtQBd8TOGynjmhJSJ2Z/ZJrjbkSARJdOtkb9msM
	TIvtjdOkENFJdxkFOMEGf/Yc9yk3Vx4pkoWerSTz1OAtwOK96nn6xehAl9VIHPtE
	2qBcEY8rIJWBaw=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:date:message-id:subject:from:to
	:content-type; s=default; bh=DiaSUMlgYbQcPLfYzKG4LFOz2o8=; b=KE8
	OHtSl6S1b4AK2VaiEr4otLpzB8UHKzgEbEW8zcbAPPRmUUIeVWLYFqwF0kxUupt5
	3L2c6OSzi7hbneDZnSukb/XvakYT4fpZwkCWkxjWBEpzr/RF6rPF/v4fwNywHsox
	TpC2BsSBisCd3qXBbZ1GBNsUH20S7S05HkhXTC/w=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
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
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=0.5 required=5.0 tests=AWL,BAYES_05,FREEMAIL_FROM,NO_RELAYS autolearn=ham version=3.3.2
X-HELO:	mail-qe0-f47.google.com
MIME-Version:	1.0
X-Received:	by 10.229.192.6 with SMTP id do6mr12475186qcb.3.1380833719168; Thu, 03 Oct 2013 13:55:19 -0700 (PDT)
Date:	Thu, 3 Oct 2013 16:55:19 -0400
Message-ID:	<CAJty3ZxPwByrCu6No2-53vc3QiDXX1G8KZd3RC5K8xBEA4k2ww@mail.gmail.com>
Subject:	fixing BLODA-caused fork failures
From:	Adam Kellas <adam DOT kellas AT gmail DOT com>
To:	cygwin AT cygwin DOT com

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?

Thanks,
AK

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

- Raw text -