Use /tmp instead of /var/tmp
In chunk.c: chunkqueue_get_append_tempfile, you use /var/tmp instead of /tmp to create temporary files by default. Is there a reason for this? As far as I know there's no need for those files to be preserved across reboots, so /tmp appears to be more appropriate to me.
Updated by stbuehler about 11 years ago
- Status changed from New to Fixed
- Resolution set to invalid
Many people mount a ramdisk in /tmp, and this is obviously not where we want to store temporary uploads; /var/tmp should never be a ramdisk (as its content is supposed to be preserverd across reboots), so it is ok.
It would be a good idea of course to have your initscript delete remaining tmp files after a crash.
Updated by jan almost 11 years ago
The reason for using /var/tmp is that it is disk-based in 99% of the times while this is not the case for /tmp. Turning it around will only lead to bug-reports because lighttpd leads to swapping the whole system on large uploads if /tmp is on tmpfs.
The trade is swapping vs. disk-full on reboot.
Updated by gstrauss over 2 years ago
- Description updated (diff)
In lighttpd 1.4.40, you can set
server.upload-dirs = ( "/tmp" ) to change the location used from the default "/var/tmp"
lighttpd 1.4.40 and later also do a better job cleaning up temp files (as long as lighttpd is not killed with kill -9 or kill -KILL)
Also available in: Atom