[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [jobs doesnt report status correctly on kill -CONT

From: Chet Ramey
Subject: Re: [jobs doesnt report status correctly on kill -CONT
Date: Tue, 10 Apr 2001 09:01:04 -0400

> Machine Type: i586-mandrake-linux-gnu
> Bash Version: 2.04
> Patch Level: 12
> Release Status: release
> Description:
> There seems to be a problem with the 'jobs' command. It doesnt report the
> status of a job correctly when you send a background job a SIGSTOP signal,
> followed by a SIGCONT signal using the kill command. If I start a job in the
> background, using the '&' at the end, and then issue a kill -STOP followed
> by a kill -CONT, 'jobs' *still* reports the job as being stopped, even
> though in reality it is actually running again.

I can't reproduce this on FreeBSD-4.2 with the just-released bash-2.05
using job identifiers:

nike.ins.cwru.edu(3)$ ls -alR / >/dev/null 2>&1 &
[1] 61036
nike.ins.cwru.edu(3)$ kill -STOP %1
nike.ins.cwru.edu(3)$ jobs
[1]+  Stopped                 /bin/ls -F -alR / >/dev/null 2>&1
nike.ins.cwru.edu(3)$ kill -CONT %1
nike.ins.cwru.edu(3)$ jobs
[1]+  Running                 /bin/ls -F -alR / >/dev/null 2>&1 &

or on Red Hat 7.0 with the same bash version:

caleb.ins.cwru.edu(3)$ ls -alR / >/dev/null 2>&1 &
[1] 24443
caleb.ins.cwru.edu(3)$ kill -STOP %1
caleb.ins.cwru.edu(3)$ jobs
[1]+  Stopped                 /bin/ls -F -alR / >/dev/null 2>&1
caleb.ins.cwru.edu(3)$ kill -CONT %1
caleb.ins.cwru.edu(3)$ jobs
[1]+  Running                 /bin/ls -F -alR / >/dev/null 2>&1 &

but I can reproduce it using pids.  My advice is to use job ids until
I can figure out what the problem is.


``The lyf so short, the craft so long to lerne.'' - Chaucer
( ``Discere est Dolere'' -- chet)

Chet Ramey, CWRU    address@hidden    http://cnswww.cns.cwru.edu/~chet/

reply via email to

[Prev in Thread] Current Thread [Next in Thread]