Forum: NGINX Option to disable the path in client_body_temp_path?

Announcement (2017-05-07): is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see and for other Rails- und Ruby-related community platforms.
51d4559d326e8515c726c64ce04acc06?d=identicon&s=25 Ask Bjørn Hansen (Guest)
on 2009-01-23 21:15
(Received via mailing list)

I wanted to add "native" support for nginx in MogileFS and ran into
the "client_body_temp_path must be on the device" problem.

The typical setup for a mogile storage node is to have a root of /var/
mogdata and then mount devices under that as /var/mogdata/dev123/.

The suggested workaround is to setup a location block with a custom
client_body_temp_path in each.

However, in MogileFS devices can come and go at any time, and the
storage/http-related code doesn't know about it - it just gets told
which path to use.

It'd be fixed by having an option to just disable
client_body_temp_path.  Either just write directly to the target or
(better) write to the target directly but with a ".tmp-nginx-" prefix
or ".nginx.tmp" suffux or something like that.   Would a patch for
this be accepted?   (Or Igor, any chance you'd want to cook it up?)

  - ask
This topic is locked and can not be replied to.