> If they are wrapped up in iowait then you need a faster seeking disk
> (e.g. ssd because sas won't give you a significant amount extra)
or need to tune something. You don't necessarily need to change always the
hdw if you have high iowaits. There are many variables around.
>
> "~" means "regex".
> "^" means "start of string".
> "$" means "end of string".
> This location will only match requests that are
> /cgi-bin/R
> or
>
> /cgi-bin/R?something
> and not
>
> /cgi-bin/R/something
>
yep. silly me, I do have a location for all /cgi-bin/R/ calls, like:
>
> Something like (untested by me!)
> location ^~ /cgi-bin/R/ { }
>
yep correct. I do have now on cgi-bin directory a binary file called: R.
I did change my nginx.conf to have a new location definition for the
R calls, like here:
location ~ ^/cgi-bin/R$ {
gzip off;
> So Im on option 1: CGI. The client will be this binary which somehow needs to
> be
> executed for each R script. I placed the Rcgi under cgi.bin directory and
> rename it
> as R.cgi.
>
and I forgot to mention for CGI Im using FcgiWrap:
http://nginx.localdomain.pl/wiki/FcgiWrap
stefan
_
On 11:22 Tue 19 Feb , Harold Sinclair wrote:
> Sounds like you ought to try writing a wrapper script ending in .cgi in the
> cgi dir that grabs the query string and hands the job off to the R
> executable. Not sure if R is required in the cgi-bin directory. You might
> have to enable symlinking
On 08:50 Tue 19 Feb , Harold Sinclair wrote:
> Does the R cgi script filename end in .cgi ? That's what you specify, it
> appears.
No, it does not end with cgi since the R scripts will not be called directly
by nginx.
As I understood I should call the R scripts like:
http://localhost/cgi-bin
Hi,
Anyone here testing, experimenting with R and nginx ?
Im trying to setup nginx to serve R scripts via
CGI using Rserve, FastRWeb modules as described here:
http://jayemerson.blogspot.fi/2011/10/setting-up-fastrwebrserve-on-ubuntu.html
My nginx is configured like:
location ~ ^/cgi-b
