Date: Thu, 13 Jan 2000 09:27:46 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Gisle Vanem <gvanem AT eunet DOT no>
cc: djgpp AT delorie DOT com
Subject: Re: bash and /tmp
In-Reply-To: <016b01bf5d0a$ca55a5d0$293f8589@gv015029.bgo.nera.no>
Message-ID: <Pine.SUN.3.91.1000113092706.9693F-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
Errors-To: dj-admin AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Wed, 12 Jan 2000, Gisle Vanem wrote:

> Any script that takes a file from stdin. Without a /tmp directory, 
> bash complains:
> 
>     bash  ./cmplhelp.sh < pine.hlp > helptext.c
>     ./cmplhelp.sh: pipe error: No such file or directory (ENOENT)

I'm guessing that your TMPDIR either is not set or points to an
invalid directory.  See section 6.11 of the FAQ.

FWIW, I don't have a /tmp directory (deliberately, so scripts which
depend on it don't get away uncaught), and I have yet to see a single
problem like that.

> With a /tmp directory everything is okay.

/tmp is probably the last resort, when TMPDIR and some other
variables aren't set.  You should never get to that point in a
well-set DJGPP installation (because djgpp.env sets TMPDIR).