[Top][All Lists]

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

Funny Bash behavior

From: Derek Robert Price
Subject: Funny Bash behavior
Date: Wed, 17 Mar 2004 11:31:24 -0500
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 Netscape/7.1

Hash: SHA1

Hey all,

I've cc'd the bug-autoconf list as well as the bug-bash list - this
isn't precisely an Autoconf question, but I thought the Autoconf folks
might also have the experience to answer my question:

Running Linux 2.4.20 (actually 2.4.20-28 from RedHat) and bash 2.05b,
the following sort of setup:

touch script
chmod a+x script
cat >script <<EOF
#! /bin/sh
echo "example text"
echo ...
echo "some other text"
echo "some other text"
echo "some other text"
echo "some other text"
echo "some other text"
cat >/dev/null
./script </dev/null

Causes Bash to report about half the time an error that the parser
reached an early EOF while looking for a closing quote and sometimes
errors like "bash: ho: command not found".  If I put a "sleep 1" command
in between the cat and the ./script, I no longer see failures but this
sounds like I am just drawing out the race condition.

I actually can't get the above script to fail as I've described, but I
do have a much longer script that does something very like the above as
an internal step and I get this error very consistently.

Has anyone heard of anything like this before?


- --

Email: address@hidden

Get CVS support at <http://ximbiot.com>!

Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Using GnuPG with Netscape - http://enigmail.mozdev.org


reply via email to

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