rack-devel archive mirror (unofficial) https://groups.google.com/group/rack-devel
 help / color / mirror / Atom feed
From: Chris Cherry <ctcherry@gmail.com>
To: Rack Development <rack-devel@googlegroups.com>
Subject: Re: Setting tmp dir
Date: Wed, 9 Jun 2010 09:43:08 -0700 (PDT)	[thread overview]
Message-ID: <c8512a9e-6dfc-4d77-a11d-d333b62065f4@t14g2000prm.googlegroups.com> (raw)
In-Reply-To: <AANLkTimcJmeX1uSIpcbGlioMifxLDNutCceI-9xAhSiB@mail.gmail.com>

Wow, that's a bit ridiculous. We shall call this Tmphell!

On Jun 8, 7:00 pm, Randy Fischer <randy.fisc...@gmail.com> wrote:
> Just as an amusing aside - I had to set up a temp variable for mongrel
> once (/var/tmp  & /tmp weren't large enough), so I was prepared for
> this particular Rack issue.
>
> Every package seems to want to specify this a different way.  Currently,
> using sinatra/passenger from apache, I have one virtual host defined
> with the following:
>
>    SetEnv TMPDIR                     /some/big/place
>    PassengerUploadBufferDir     /some/other/big/place
>
> TMPDIR points rack to a place where it can (sigh) make its
> rewindable input.  (I regularly have multi-GB file uploads,
> destined for different filesystem partitions)
>
> PassengerUploadBufferDir points to a place where, somewhat
> at phusion's whim, it will use for storing post data.  But it has
> to be writable by the apache worker process, so I just give
> up and chmod it 1777).
>
> Too Many Buffers!
>
>
>
> > >http://github.com/rack/rack/blob/master/lib/rack/utils.rb#L450
> > > > and I think we could add a class instance variable with accessors to
> > > > adjust it, defaulting to Dir.tmpdir.
> > > > If you want to, you can submit a patch for that, or overwrite
> > > > Dir.tmpdir after requiring tmpdir.
>
> > > > --
> > > > Michael Fellinger
> > > > CTO, The Rubyists, LLC

      reply	other threads:[~2010-06-09 16:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-08 18:14 Setting tmp dir Chris Cherry
2010-06-08 18:21 ` Michael Fellinger
2010-06-08 18:56   ` Randy Fischer
2010-06-08 20:06     ` Chris Cherry
2010-06-09  2:00       ` Randy Fischer
2010-06-09 16:43         ` Chris Cherry [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://groups.google.com/group/rack-devel

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c8512a9e-6dfc-4d77-a11d-d333b62065f4@t14g2000prm.googlegroups.com \
    --to=rack-devel@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).