From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from euclid.skiles.gatech.edu (list@euclid.skiles.gatech.edu [130.207.146.50]) by coral.primenet.com.au (8.7.5/8.7.3) with ESMTP id CAA04039 for ; Sun, 25 Aug 1996 02:47:15 +1000 (EST) Received: (from list@localhost) by euclid.skiles.gatech.edu (8.7.3/8.7.3) id MAA02992; Sat, 24 Aug 1996 12:43:01 -0400 (EDT) Resent-Date: Sat, 24 Aug 1996 12:43:01 -0400 (EDT) Date: Sat, 24 Aug 1996 18:41:28 +0200 (MET DST) From: Janos Farkas Reply-To: Janos Farkas To: zsh-workers@math.gatech.edu Subject: 3.0.0: job table full causes fg to fail? Message-ID: X-Mood: in love MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"AefWl2.0.dk.K4p7o"@euclid> Resent-From: zsh-workers@math.gatech.edu X-Mailing-List: archive/latest/2062 X-Loop: zsh-workers@math.gatech.edu Precedence: list Resent-Sender: zsh-workers-request@math.gatech.edu Howdy people! I've just run into a problem, and can't imagine how it could be fixed. It's probably present in earlier versions too. I've been trying to stress my home-net with some concurrent pings, and suddenly.. [iceq] /usr/src 514> ping ancient >/dev/null & [47] 24995 [iceq] /usr/src 514> ping ancient >/dev/null & [48] 24996 [iceq] /usr/src 514> ping ancient >/dev/null & zsh: job table full [iceq] /usr/src 514> ping ancient >/dev/null & zsh: job table full Heh, cool, limits? Hmm.. it's right, I shouldn't have been doing this... So let's get rid of them... I used to fg, and ctrl-c out of it, but: [iceq] /usr/src 514> fg fg: no current job What? Now, how am I supposed to kill 'em? [iceq] /usr/src 515> killall ping zsh: job table full WHAT? :) Hmm... Okay, I don't have a free slot to run killall, but fg shouldn't have been tricking me? [iceq] /usr/src 516> _