delorie.com/archives/browse.cgi | search |
Mailing-List: | contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm |
Sender: | cygwin-owner AT sourceware DOT cygnus DOT com |
Delivered-To: | mailing list cygwin AT sourceware DOT cygnus DOT com |
From: | N8TM AT aol DOT com |
Message-ID: | <2955d053.248fbb18@aol.com> |
Date: | Wed, 9 Jun 1999 08:42:00 EDT |
Subject: | Re: B20 : Bash Problem, Slowing down after 4 hours running (win98) |
To: | james AT dattrax DOT demon DOT co DOT uk, cygwin AT sourceware DOT cygnus DOT com |
MIME-Version: | 1.0 |
X-Mailer: | AOL 3.0 16-bit for Windows sub 85 |
In a message dated 99-06-09 06:40:37 EDT, james AT dattrax DOT demon DOT co DOT uk writes: << I wrote a script to covert 1000's of filenames to their lowercase equivalent. Worked fine but got slower and slower over time until 4 hours after I'd started it running it was really slow (mouse not moving properly). Nothing else was running at the time. Anyone else experienced this?? >> If you bring up Task Manager (or run ps in another window under W9X) you'll likely see phantom jobs. Kill them off one by one if they don't belong. The snapshot versions of cygwin don't leave as many processes running after completion. -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |