From: Bill Ross <photoriot@yahoo.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: Has anyone collected a summary of cygwin vs Windows 7 64 bit outstanding issues?
Date: Wed, 23 May 2012 17:19:00 -0000 [thread overview]
Message-ID: <1337790410.10347.YahooMailNeo@web39303.mail.mud.yahoo.com> (raw)
On 5/23/2012 9:24 AM, Larry W. Virden wrote:
> We are trying to make use of cygwin in several ways
on Windows 7
> 64-bit desktops.
>
> One of the first things we have noticed is that
there are a lot of
> processes sitting on the desktop that appear to be
related to cygwin
> that we didn't see previously on 32 bit XP.
>
> For instance, if we open a bash console, perform an
ssh to another
> machine, do some work, then close the window, the
bash and ssh still
> seem to be listed when we look at the windows 7 task
manager.
I have 64-bit Win7 with cygwin, and after a while this
sort of thing runs out of resources (errno 11) until I reboot (and then starts
up after a few ok runs, as just now):
$ find . -name "*.java" | while read i ; do
> echo %%%% $i >> x
> grep foob $i >> x
> done
375832787 [main] -bash 6020 fork: child -1 - forked
process died unexpectedly, retry 0, exit code -1073741819, errno 11
-bash: fork: retry: Resource temporarily unavailable
-bash: fork: Resource temporarily unavailable
And I think I have noticed lots of bash processes hanging
around, though not in this instance.
$ uname -a
CYGWIN_NT-6.1-WOW64 mybox 1.7.13(0.260/5/3) 2012-04-05
12:43 i686 Cygwin
Bill
--
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
next reply other threads:[~2012-05-23 16:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-23 17:19 Bill Ross [this message]
2012-05-23 17:42 ` Eliot Moss
-- strict thread matches above, loose matches on Subject: below --
2012-05-23 19:13 Bill Ross
2012-05-23 20:11 ` marco atzeri
2012-05-24 11:25 ` Larry W. Virden
2012-05-26 21:35 ` Christopher Faylor
2012-05-23 17:54 Bill Ross
2012-05-23 18:47 ` Larry W. Virden
2012-05-23 13:36 Larry W. Virden
2012-05-23 14:16 ` Eliot Moss
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1337790410.10347.YahooMailNeo@web39303.mail.mud.yahoo.com \
--to=photoriot@yahoo.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).