On Sun, May 06, 2012 at 10:05:00PM +0200, Rob Burgers wrote: >Corinna wrote: >>If Cygwin behaves different than Linux then that's not really intended. >>However, this only goes as far as Cygwin processes are affected. We >>can't (and don't) make any such guarantee for native, non-Cygwin >>processes. > >Okay, may be we should review our starting point. Still one thing >puzzles me: Despite the fact that no such guarantee can be made, it >worked fine upto the 1.7.9/1.7.10 kernel releases. If anything can be >done to 'repair' it, this would be appreciated a lot (even if it were >done via a registry-key).
This is probably related to: http://cygwin.com/ml/cygwin/2012-05/msg00081.html It is not likely to change. -- 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
