public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Olaf Hering <olh@suse.de>
To: linux-kernel@vger.kernel.org
Cc: Olaf Hering <olh@suse.de>
Subject: Re: out of order execution of shell commands
Date: Sat, 9 Oct 2004 22:28:03 +0200	[thread overview]
Message-ID: <20041009202803.GA6298@suse.de> (raw)
In-Reply-To: <20041007204653.GA26820@suse.de>

 On Thu, Oct 07, Olaf Hering wrote:

> 
> we have a weird bug where the open of the shell output redirection
> happens before the mkdir command returns.
> As a result, the redirection will fail. Unexpected data loss.

...
>         for l in `/bin/cat ten`; do
>           /bin/mkdir $h$i/$j/$k/$l
>           /bin/echo $h$i/$j/$k/$l > ./$h$i/$j/$k/$l/DIRNAME || /bin/kill -STOP `/bin/cat /dev/shm/bug42232-pid-*`
>           /bin/dd if=/dev/zero of=$h$i/$j/$k/$l/data bs=1024 count=1 &> /dev/zero
>         done
...

looks like the dd and the mkdir will get the same pid,
and bash can not deal with it.

-- 
USB is for mice, FireWire is for men!

sUse lINUX ag, nÜRNBERG

      reply	other threads:[~2004-10-09 20:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-07 20:46 out of order execution of shell commands Olaf Hering
2004-10-09 20:28 ` Olaf Hering [this message]

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=20041009202803.GA6298@suse.de \
    --to=olh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    /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