On Wed, Oct 21, 2015 at 06:08:06PM +0200, Richard PALO wrote: > In digging around as to why /var/tmp is used so much causing a ruckus on my > rpool.. ... > > some define P_tmpdir (if not already defined) as "/usr/tmp" which, on most > modern systems including solaris is a simply a symlink to "/var/tmp" ... > > Adding now the environment variable TMPDIR=</tmp or something else fast> > everywhere > is not necessary feasible, so I can't help but wonder if it is not time to > change > P_tmpdir to "/tmp".
I think this is quite reasonable. > Furthermore, mktemp also defaults to "/tmp" > > So, what eats me is sometimes it defaults to "/tmp", sometimes to "/var/tmp". > programatically, something as simple as __EXTENSIONS__ or _XOPEN_SOURCE=600 > can give you surprises! > > Also, the gate builds libc with __EXTENSIONS__ so functions such as tmpnam > and tempnam > generate by default "/var/tmp"! > > /usr/bin/mktemp doesn't even peek at P_tmpnam but uses "/tmp" unless TMPDIR > is assigned. > > Naturally, anything that can overuse "/tmp" *needs* to be dealt with such as > huge files that can quickly fill up the tmpfs. Normally those "exceptions" > are > the ones that need intervention by defining TMPDIR. I agree. The common case seems to be that temp files are small enough that /tmp is the right place for them. The few instances of too-big-for-tmpfs people handle already anyway. Jeff, rummaging through /var/tmp to see what sort of treasures are there to be found. -- Humans were created by water to transport it upward. ------------------------------------------- illumos-discuss Archives: https://www.listbox.com/member/archive/182180/=now RSS Feed: https://www.listbox.com/member/archive/rss/182180/21175430-2e6923be Modify Your Subscription: https://www.listbox.com/member/?member_id=21175430&id_secret=21175430-6a77cda4 Powered by Listbox: http://www.listbox.com
