![]() > Cygwin cannot affect IE, nor vice versa. ![]() > Another thing that happens is that Internet Explorer stops working - it loads unresponsive and then crashes. > That said, I donât think strace will help here, because I donât think you actually have a Cygwin-specific problem. > Realize that this is not a general problem, so weâre going to be relying on you to do much of the debugging. > The usual way to find out whatâs happening is to run the problem program under strace, then see where the strace output hangs. "ls" goes from under a second to give a listing to 20 or more seconds. > One result is that everything takes many times longer to complete. Have attached that cygcheck file, though the issue comes up with both. It might be because I ran the cygcheck from babun instead of cygwin. > What is preventing you from becoming current? (2.5.1) I see in your message stuff about stuck postinstall scripts, but ipso facto, those are run *after* everything is installed, so that doesnât explain it. Did you read the release notes that strongly recommended that you to move /etc/passwd and /etc/group out of the way? This is especially important in an AD-based organization like yours. > I can see from your cygcheck.out that you are now on 1.7.35. I have a new laptop that I just installed cygwin onīut have not yet set it up so I can run my report script that would test In the end though I renamed my cygwinĭirectory to _cygwin and renamed the branch in the registry as well toĭo a complete reinstall (I did not reinstall babun however) but this did I am not sure but at the time it probably was at least 6 months butĬould have been much longer. > From what version? Or if you cannot be sure, about how long ago was your last update? Impression that if the licensing wasn't GNU it would be a problem even > now I only have a binary of ksh which I have on all my systems.IĪm not sure what is involved in packaging ksh with Cygwin but wouldĭefinitely be interested in finding out. While doing compatibility testing with mksh, itâs hard to know if any given odd behavior is due to an mksh weirdness or if itâs accurately emulating AT&T ksh. It would be nice to have AT&T ksh for Cygwin, if only for reference and comparison purposes. > Incidentally, please consider packaging ksh93u+ (stable) or ksh93v- (beta) for Cygwin. Successful would try it on the 64-bit version. I was compiling under 32-bit Cygwin and if My attempt to do so is what began this unusual behavior (when I used I haven't upgraded yet because I have not been successful in compiling Which version did you come from, and which did you upgrade to?ĭoing a ksh -version gives me: version sh (AT&T Research) 93u+ > I can see from your cygcheck.out that you arenât talking about mksh, the only ksh that ships with Cygwin. > I have been using the same version of ksh for a while > On May 12, 2016, at 8:35 AM, Ben Altman wrote: Next message (by thread): system lags and dysfunctional after cygwin update.Previous message (by thread): system lags and dysfunctional after cygwin update.System lags and dysfunctional after cygwin update Ben Altman May 13 14:02: System lags and dysfunctional after cygwin update
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |