in reply to CGI reading and writing to data files

Well that depends on the underlying filesystem and what user you're running the webserver as. For me (linux ext3, nobody), /tmp does in a pinch but be careful - some systems clean out /tmp on a periodic basis. For long term storage I normally need to work with the system admins to set up a directory that the user nobody has write permissions and has enough disk space to meet my reqs.

-derby
  • Comment on Re: CGI reading and writing to data files

Replies are listed 'Best First'.
Re^2: CGI reading and writing to data files
by varian (Chaplain) on Jun 11, 2007 at 13:44 UTC
    For *nix operating systems the Filesystem Hierarchy Standard provides widely accepted guidelines to help you select the right directory for where to store files.
    /tmp is considered volatile so once you close a file it can be removed by the system, e.g. upon reboot
    /var/tmp is less volatile, you are supposed to remove any temporary files yourselves whenever you feel they are not needed anymore.