[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: job-control warning message that maybe shouldn't be printed
From: |
Chet Ramey |
Subject: |
Re: job-control warning message that maybe shouldn't be printed |
Date: |
Thu, 28 Nov 2013 12:40:34 -0500 |
User-agent: |
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.0.1 |
On 11/28/13, 7:23 AM, Peter Cordes wrote:
> I submitted this on savannah a couple days ago:
> https://savannah.gnu.org/support/?108450
>
> As I said there, the warning message for bash re-using a PID that
> it's tracking for exitted processes in suspended pipelines or w/e has
> an off-by-one error (jobs.c:892).
Thanks for the report. The message is just informational and designed
to reveal the cases in which this happens. I have to say that I didn't
expect anyone to leave a multi-process pipeline suspended for a week
and trigger it. The original motivation for the message was to figure out
how big the pid-reuse problem was after a discussion started by
http://lists.gnu.org/archive/html/bug-bash/2012-07/msg00054.html
That's where you see the Posix requirement that shells save the exit
status of the last CHILD_MAX processes.
Bash does the right thing; it zeroes out the saved pid information.
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU chet@case.edu http://cnswww.cns.cwru.edu/~chet/