It makes no difference what file system the file is on. You just need to
ensure that the files are accessible, so take care with uid/gid used to
mount, as well as file ownership. Standard entries in /etc/exports work
from what I remember.
You will have a performance hit to contend with. I usually use lsync
with a backup of rsync and keep the files local.
hth,
Steve
On 12/08/13 19:34, Rakshith wrote:
Hi,
Can anybody tell me what are the things needed by nginx to forward the
request via the NFS mount point?? Changes to the config file as such??
The config file looks like as shown below:
http {
.....
.........
server {
listen *:80 default accept_filter=httpready;
server_name vs0;
root /var/home/diag;
autoindex on;
}
The mount path is as shown above against the root entry.
This config is resulting in an error when i try to send request using Curl
as shown below:
[rakshith@cyclnb15 ~]$ curl -X GET -qvk
http://10.238.62.234:80/vol1_mnt_point/output.dat
< HTTP/1.1 404 Not Found
But the file actually exists:
bash-3.2# pwd
/var/home/diag/vol1_mnt_point
bash-3.2# ls
.snapshot nginx.tar output.dat
Any help on this is greatly appreciated!!!
Thanks,
Rakshith
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,241773,241773#msg-241773
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
