Project

General

Profile

Actions

Bug #1594

closed

Use /tmp instead of /var/tmp

Added by admin over 16 years ago. Updated over 7 years ago.

Status:
Missing Feedback
Priority:
Normal
Category:
core
Target version:
ASK QUESTIONS IN Forums:

Description

Hi,

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.

See also http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=408521


Related issues 1 (0 open1 closed)

Related to Bug #3045: Lighttpd not able to delete temporary chunk files if client closes itself before upload completedMissing FeedbackActions
Actions #1

Updated by stbuehler over 16 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.

Actions #2

Updated by admin about 16 years ago

  • Status changed from Fixed to Need Feedback
  • Resolution deleted (invalid)

so it is ok.

Does the FHS say it's ok?
If people want /tmp to be a ramdisk, shouldn't they make sure to reconfigure daemons not to use it for large files?

Actions #3

Updated by darix about 16 years ago

  • Status changed from Need Feedback to Fixed
  • Resolution set to worksforme

as the debian bug has shown you can configure that already without changing any defaults of lighttpd.

Actions #4

Updated by admin about 16 years ago

Of course you can manually change it. I'm just asking for the default to be changed to the proper location.

Actions #5

Updated by jan about 16 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.

Actions #6

Updated by stbuehler about 16 years ago

  • Status changed from Fixed to Missing Feedback
Actions #7

Updated by gstrauss over 7 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)

Actions #8

Updated by gstrauss 11 months ago

  • Related to Bug #3045: Lighttpd not able to delete temporary chunk files if client closes itself before upload completed added
Actions

Also available in: Atom