X-Recipient: archive-cygwin@delorie.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:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=RCI7nEbeKxPuUwoU4c7YTPSZXOW4s4N88Z2xXwiziHaLvXPLhgRqJ
	20pO+BuEsa8THFuXfYpbZP9zEaQU5oODrt0xCi0v950kkgT8GykEDzTt3o/nPhWK
	WNbmfTLDoFC4N+x3hdD40IcVGy2ubesItAS2Drt7s1J9GaCyap2iBw=
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:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	 bh=OTWo7fCSXGRbPmIC1hUSa1jiYpI=; b=k2SHEeY4C9CGaoftLNvbr0ZKVR2A
	oTy2SOMl8ESDzcxEIXG/YxBx7bKVL4cUUk/chHw8m6gYYAkGLJo4AnBnFI1XYkKu
	iJ+/K4vuY/FVSdjMwtfF2gvgj9L5swlGdb2zqnrCeyX0jxSEJINvS+lv53gEBvYo
	cGanYsjR4CvdkPc=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: Yes, score=6.2 required=5.0 tests=AWL,BAYES_50,RCVD_IN_PBL,RCVD_IN_RP_RNBL,RCVD_IN_SORBS_DUL,RP_MATCHES_RCVD autolearn=no version=3.3.2
X-HELO: mho-01-ewr.mailhop.org
X-Mail-Handler: Dyn Standard SMTP by Dyn
X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User: U2FsdGVkX1/tLJS8b4mrvCzT9UGB55ba
Date: Thu, 3 Oct 2013 21:00:51 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: fixing BLODA-caused fork failures
Message-ID: <20131004010051.GA4730@ednor.casa.cgf.cx>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <CAJty3ZxPwByrCu6No2-53vc3QiDXX1G8KZd3RC5K8xBEA4k2ww@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAJty3ZxPwByrCu6No2-53vc3QiDXX1G8KZd3RC5K8xBEA4k2ww@mail.gmail.com>
User-Agent: Mutt/1.5.20 (2009-06-14)

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

