fixing BLODA-caused fork failures

[Achim Gratz]

Am 03.10.2013 22:55, schrieb Adam Kellas:
> 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.

In my experience the culprit is most often the "real-time" or 
"behavioral" component of the anti virus program.  Uninstalling the 
virus program is a bad idea and it will certainly draw the ire of 
corporate IT, but you may persuade them to exclude the whole Cygwin 
installation tree from these two functions.  In any case I'd try to get 
a test machine from IT and try if that helps.

 > So we need Cygwin and we're stuck with Forefront, putting us
 > between a rock and a hard place.

AFAIK Forefront uses the same engine on the client as MSE.  MSE has not 
been a problem w.r.t. Cygwin for me, so either the rules used by 
Forefront have been sharpened or the fork problems may not be related to 
it after all.  Do you use other programs that are based on Cygwin, like 
NoMachine NX or other (perhaps in-house) programs that insist on putting 
their DLL at fixed address spaces?


Regards,
Achim.



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