Zsh Mailing List Archive Messages sorted by: Reverse Date, Date, Thread, Author

Re: Bug#593426: zsh: Status of background jobs not updated

X-seq: zsh-workers 28171
From: Clint Adams <schizo@xxxxxxxxxx>
To: Victor Villa <victormvm+debian@xxxxxxxxx>, 593426@xxxxxxxxxxxxxxx
Subject: Re: Bug#593426: zsh: Status of background jobs not updated
Date: Wed, 18 Aug 2010 18:29:59 +0000
Cc: zsh-workers@xxxxxxx
In-reply-to: <20100818025148.13456.14691.reportbug@xxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:zsh-workers-help@zsh.org>
List-id: Zsh Workers List <zsh-workers.zsh.org>
List-post: <mailto:zsh-workers@zsh.org>
Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
References: <20100818025148.13456.14691.reportbug@xxxxxxxxxxxxxxxxxxxxx>

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.

Follow-Ups:
- Re: Bug#593426: zsh: Status of background jobs not updated
  - From: Peter Stephenson

Messages sorted by: Reverse Date, Date, Thread, Author