Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Date: Thu, 12 Oct 2000 11:27:22 -0400 From: Chet Ramey To: merz@studsys.mscs.mu.edu Subject: Re: idle bash using 95% of system resources? Cc: cygwin@sources.redhat.com, rschulz@teknowledge.com Reply-To: chet@po.CWRU.Edu Message-ID: <1001012152722.AA03379.SM@nike.ins.cwru.edu> Read-Receipt-To: chet@po.CWRU.Edu MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-In-Reply-To: Message from rschulz@teknowledge.com of Wed, 11 Oct 2000 14:46:08 -0700 (id ) > This suggests a work-around until the problem can be found and fixed: > Set the "notify" option in BASH (i.e., issue the command "set > notify"). That way BASH prints jobs status changes when they occur, > instead of waiting for the next time it prints a prompt. This should, of course, be set -o notify The `set notify' will set $1 to "notify". -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ( ``Discere est Dolere'' -- chet) Chet Ramey, CWRU chet@po.CWRU.Edu http://cnswww.cns.cwru.edu/~chet/ -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com