在nginx 1.10.2和uwsgi 2.0.14的centos 7上
当我configurationuwsgi在/ var / tmp / uwsgi或/ tmp中打开一个套接字时，我从nginx发出一条消息，说它找不到套接字文件：
2017/06/07 16:54:53 [crit] 2642#0: *7 connect() to unix:///tmp/mywebsite.socket failed (2: No such file or directory) while connecting to upstream, client: 108.162.245.185, server: _, request: "GET /share/3years/music/guitarists/django_reinhardt HTTP/1.1", upstream: "uwsgi://unix:///tmp/mywebsite.socket:", host: "mywebsite.com" 2017/06/07 17:22:11 [crit] 1327#0: *2 connect() to unix:///var/tmp/uwsgi/mywebsite.socket failed (2: No such file or directory) while connecting to upstream, client: 5.158.200.123, server: _, request: "GET / HTTP/1.1", upstream: "uwsgi://unix:///var/tmp/uwsgi/mywebsite.socket:", host: "mywebsite.com" 如果我使用“unix：///var/uwsgi/mywebsite.socket”（不带'/ tmp /'），则完全没有问题。 在三种情况下，目录是在1777年，套接字文件权限给读取/写入访问nginx用户和nginx套接字path匹配configuration文件中的uwsgi套接字path。 SELinux被禁用。
那么为什么我不能使用/ var / tmp或/ tmp为nginx / uwsgi创build一个套接字：很多例子都说可能？