From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23693 invoked by alias); 18 Aug 2010 18:36:39 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 28171 Received: (qmail 12093 invoked from network); 18 Aug 2010 18:36:35 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham version=3.3.1 Received-SPF: none (ns1.primenet.com.au: domain at debian.org does not designate permitted sender hosts) Date: Wed, 18 Aug 2010 18:29:59 +0000 From: Clint Adams To: Victor Villa , 593426@bugs.debian.org Cc: zsh-workers@zsh.org Subject: Re: Bug#593426: zsh: Status of background jobs not updated Message-ID: <20100818182959.GA29785@scru.org> References: <20100818025148.13456.14691.reportbug@salamander.skynet.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100818025148.13456.14691.reportbug@salamander.skynet.lan> User-Agent: Mutt/1.5.18 (2008-05-17) On Wed, Aug 18, 2010 at 02:51:48PM +1200, Victor Villa wrote: > After running a process in the background (by putting "&" at the end of the command line) the output of "jobs" correctly shows > the process as "running". If I send the process a STOP signal with "kill -STOP", the process stops and "jobs" shows the > process as "suspended (signal)". The problem is that after sending a CONT signal to the process (with kill -CONT), > "jobs" still shows the process as suspended, even though the process resumes (if it's a media file I can hear it > playing, for example. > > The processes I used to test this were "ping -i 4 -f localhost" and mpg321. I tried the same using bash and the status > are correctly updated. I tried also "/bin/kill" but the same thing happens. Your job table isn't being updated when you send the STOP/CONT signals externally.