Currently Being ModeratedMar 21, 2013 8:20 PM (in response to htimsknarf)
I have worked with applications that need to have a temporary folder available to write small bits of data to. Many do need this. I would assume some application is running a process to create this folder as part of its routine. It is odd that it is visable. I think I'd let it be. However, if you wanted to follow it up you could try placing a locked folder with an identical name in that path, as a place holder, and then see which application starts giving you problems. I don't really recommend this though.
Currently Being ModeratedMar 25, 2013 11:32 AM (in response to htimsknarf)
The /tmp directory is just what it appears; for temporary file and directory storage. The creation of /tmp files is common practice in applications used on Unix systems such as OS X, and many applications will use those resources.
On OS X, /tmp is an alias for /private/tmp.
$ ls -ale / | grep -i tmp
lrwxr-xr-x@ 1 root wheel 11 Aug 30 2009 tmp -> private/tmp
OS X should clean up the contents of the /tmp directories on restart, too.
There are add-on tools around to clean up this stuff, but I generally don't recommend using those. Mistakes with certain of the shell commands used in the clean-up scripts can be bad, too.
FWIW, if you're down to tens of gigabytes of free storage, your disks are either very undersized or seriously overloaded, and the disks either need to be off-loaded or replaced with larger-capacity disks, or both. Recommendations for freespace vary, but I've seen anywhere from 10% to 30% of the capacity recommended. Operating disks near capacity means the disks and the files tend to fragment.