Mail Archives: cygwin/2000/08/11/17:45:33
Chris Faylor [cgf AT cygnus DOT com] writes:
> It looks like any process which exits in the background causes the
> same behavior. It doesn't seem to be a problem in the CVS sources
> but I certainly haven't done anything to either cause or fix this.
> Weird.
While I don't have a lot of data myself, it's probably worth
mentioning that I've seen this behavior occasionally for a while, just
to help avoid focusing too much on recent changes. Every so often
I've gotten this back I think at least to 1.1.1, and the bash
distributed with the original 1.1.0 release.
I seem to hit it most often when Ctrl-C'ing out of a running command
involving several commands and pipes, which probably creates the final
exit in the background scenario. But not 100% of the time. When it
happens I sort of find the bash I was using, hit Enter and the problem
goes away. But recreating it upon demand has been very difficult.
Also, in my case I normally can't create the problem at will by just
placing something in the background - my CPU is fine even before I hit
Enter and get the Done message in such cases.
-- David
/-----------------------------------------------------------------------\
\ David Bolen \ E-mail: db3l AT fitlinxx DOT com /
| FitLinxx, Inc. \ Phone: (203) 708-5192 |
/ 860 Canal Street, Stamford, CT 06902 \ Fax: (203) 316-5150 \
\-----------------------------------------------------------------------/
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com
- Raw text -