From: Kris Maglione <maglione.k@gmail.com>
To: Herbert Xu <herbert@gondor.apana.org.au>, dash@vger.kernel.org
Subject: Re: Job control bug in revision 3800d4934391b,
Date: Fri, 28 May 2010 11:34:23 -0400 [thread overview]
Message-ID: <20100528153423.GA3885@jg.home> (raw)
In-Reply-To: <20100528045316.GA18560@gondor.apana.org.au>
On Fri, May 28, 2010 at 02:53:16PM +1000, Herbert Xu wrote:
>Kris Maglione <maglione.k@gmail.com> wrote:
>>
>> I'm not sure how to describe this bug, but it's affected one of my
>> scripts, and those of several of my users. Basically, we've had loops
>> dieing when backgrounded programs exit. This is the simplest test case
>> I can come up with:
>>
>> #!/bin/dash
>> {
>> echo foo
>> sleep 1
>> echo foo
>> echo done>/dev/tty
>> } | while read p; do
>> ( echo good & ) &
>> done
>> echo done
>>
>>
>> In versions prior to 3800d4934391b, the output would
>> "good\ndone\ndone\ngood" (or some permutation thereof depending on
>> system load), but from 3800d4934391b on, it's "good\ndone".
>
>This should be fixed by the patch that I posted yesterday.
I should have mentioned that I tested it with every revision
upto and including that one (especially as it looked promising).
I definitely still have this problem as of
207e4c2a322fe: [JOBS] Fix wait regression where it does not wait for all jobs master
Thanks,
--
Kris Maglione
Real Programmers don't believe in schedules. Planners make up
schedules. Managers "firm up" schedules. Frightened coders strive to
meet schedules. Real Programmers ignore schedules.
next prev parent reply other threads:[~2010-05-28 15:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-28 0:21 Job control bug in revision 3800d4934391b, Kris Maglione
2010-05-28 4:53 ` Herbert Xu
2010-05-28 15:34 ` Kris Maglione [this message]
2010-05-28 22:43 ` Herbert Xu
2010-05-28 23:01 ` Kris Maglione
2010-05-28 23:10 ` Herbert Xu
2010-05-28 23:40 ` Herbert Xu
2010-05-29 0:00 ` Kris Maglione
2010-05-28 23:09 ` Jilles Tjoelker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100528153423.GA3885@jg.home \
--to=maglione.k@gmail.com \
--cc=dash@vger.kernel.org \
--cc=herbert@gondor.apana.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox