[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: bash using unknown tmp - library based? static link on linux? (was
Re: bash using unknown tmp - library based? static link on linux? (was Re: bash not using pipes or /tmp @ boot?)
Wed, 08 Oct 2014 09:52:10 -0400
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
On 10/8/14, 1:17 AM, Linda Walsh wrote:
>>> Yeah... where?
>> Wherever $TMPDIR says to. If $TMPDIR doesn't name a writable directory,
>> bash looks for various system definitions (P_tmpdir), finally defaulting
>> to /tmp or /var/tmp.
> P_tmpdir? in ENV?
No. P_tmpdir is a #define in stdio.h that holds the full pathname of the
compilation environment's preferred temporary directory.
> I don't have TMP or TMPDIR in my env during normal runtime
> and tmp's were put in /tmp...
Then P_tmpdir is probaby "/tmp".
> I don't know where they were going
> @ boot time, as /tmp and /var/tmp were writeable, but still
> TMP/TMPDIR were unset.
Did you verify $TMPDIR?
>> Please. Your assumptions about what is going on make your conclusions
>> shaky at best.
> Um...assumptions were that tmp files weren't getting created
> in standard locations of /tmp or /var/tmp for unknown reasons. Interactively
> and @ run time, it works fine... it's probably some library bash is linking
Since the thing that differs is $TMPDIR, presumably its value when
executing in the boot-time environment, you might want to start with
looking at that.
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU address@hidden http://cnswww.cns.cwru.edu/~chet/