As suggested, I did a "set CYGWIN=detect_bloda" before running cygwin.bat, but
that didn't produce any output.
It seems as if the shells are the most vulnerable. Quite often, working in vi, I get thrown out, with
"You have running jobs". After a "^Jtty sane^J" and "fg", I can terminate vi
al
On 21/06/2012 1:49 PM, James Johnston wrote:
-Original Message-
Sent: Thursday, June 21, 2012 15:55
Subject: Re: Cygwin unstable as hell on Windows7 64bit
On 21/06/2012 11:34 AM, Gerard H. Pille wrote:
I checked the BLODA, but with only the following programs left
running, Cygwin is
James Johnston wrote on 2012-06-21:
> It would be nice if there was a list of ways for checking for BLODA. While
> there is a long list of BLODA already there, it's possible there could be a
> new
> dodgy app not on the list. In that case, some things to check for would be
> helpful. There is
> -Original Message-
> Sent: Thursday, June 21, 2012 15:55
> Subject: Re: Cygwin unstable as hell on Windows7 64bit
>
> On 21/06/2012 11:34 AM, Gerard H. Pille wrote:
> > I checked the BLODA, but with only the following programs left
> > running, Cyg
On 21/06/2012 11:34 AM, Gerard H. Pille wrote:
I checked the BLODA, but with only the following programs left
running, Cygwin is still getting killed:
$ ps -efW
A task list isn't terribly useful:
- It doesn't include system tasks (winlogon.exe and a pile of
svchost.exe being prominently abs
I checked the BLODA, but with only the following programs left running, Cygwin
is still getting killed:
$ ps -efW
UID PIDPPID TTYSTIME COMMAND
gpille55085540 cons017:31:22 /usr/bin/ps
gpille5540 1 cons017:31:18 /usr/local/bin/ksh
039
On 19/06/2012 6:55 AM, Fedin Pavel wrote:
On 19.06.2012 14:50, Gerard H. Pille wrote:
Since my system was replaced by one running Windows 7 on an Intel
Core I5, I may call myself lucky if I can work for an hour.
Works fine here. May be your hardware is flaky ? RAM for example...
Cygwin loads up
On 6/19/2012 6:55 AM, Fedin Pavel wrote:> On 19.06.2012 14:50, Gerard H. Pille
wrote:
>> Since my system was replaced by one running Windows 7 on an Intel Core I5, I
may call myself lucky
>> if I can work for an hour.
> Works fine here. May be your hardware is flaky ? RAM for example... Cygwin
On 19.06.2012 14:50, Gerard H. Pille wrote:
Since my system was replaced by one running Windows 7 on an Intel Core
I5, I may call myself lucky if I can work for an hour.
Works fine here. May be your hardware is flaky ? RAM for example...
Cygwin loads up the system quite well, especially upon for
9 matches
Mail list logo
