[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Behaviour of tmpnam
From: |
Alexander Klimov |
Subject: |
Behaviour of tmpnam |
Date: |
Sun, 4 Feb 2001 18:24:36 +0200 (IST) |
Hi.
I tried to run `make check' on CVS version and it is failed with
misterious message
with GUILE_LOAD_PATH: /export/home/ask/build/guile-core
ERROR: In procedure mkdir:
ERROR: No space left on device
uname -a:
SunOS iridium 5.6 Generic_105181-20 sun4u sparc SUNW,Ultra-5_10
I know that my /var/tmp is full, and because of this I use
TMPDIR=/tmp and every good program regards this (gcc at least), and it is
exported:
guile> (system "echo $TMPDIR")
/tmp
0
Lets return to our tests. It is looks like one of tests use (tmpnam) and
behaviour of this function is strange:
guile> (tmpnam)
"/var/tmp/aaa4dZFP_"
It is strange, because documentation said: `This function is implemented
with the `tmpnam' function in the system libraries', and documentation of
tmpnam said (tmpnam(3S)):
tempnam() allows the user to control the choice of a direc-
tory. The argument dir points to the name of the directory
in which the file is to be created. If dir is NULL or
points to a string that is not a name for an appropriate
directory, the path-prefix defined as P_tmpdir in the
<stdio.h> header is used. If that directory is not accessi-
ble, /tmp will be used as a last resort. This entire
sequence can be up-staged by providing an environment vari-
able TMPDIR in the user's environment, whose value is the
name of the desired temporary-file directory.
Regards,
ASK
- Behaviour of tmpnam,
Alexander Klimov <=