On 2014-06-24 12:03, jdd wrote:
Le 24/06/2014 11:58, Dylan a écrit :
And how does one go about configuring mktemp() on a per-application, or worse per-project, basis?
kdenlive do not write work files in /tmp!
Mozilla does. Click on a pdf or another large file, click on view, not download. It goes into /tmp. Some tools I have used to create an iso, use /tmp. For instance, k3b, I just looked: the default destination is "/tmp/kde-cer/". That can be about 4.7 GB per disk. You can change the default, yes, but that is the default. YaST backup uses /tmp to first create a compressed copy of what it is going to backup - and if you tell it to backup home, it can be terabytes.
But you do generalise from the specific case of hosted (possibly virtual) servers where (A) storage capacity is likely charged on a per [M|G]B basis (either explicitly or as part of the package cost); and (B) the installation is less likely to include e.g. GUI DEs or office/productivity suites...
not at all.
I speak mostly of setting a dvd in the reader and clic install, all default
But most serious users customize the defaults. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)