Tell me more ×
Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems.. It's 100% free, no registration required.
up vote 2 down vote favorite

I will have a couple of WSGI applications. They will communicate with nginx using sockets. For that purpose I've created the directory /run/wsgi in which I will place all the socket files that are needed.

My problem is that nginx is not able to access the socket file. I've given ownership of /run/wsgi to www-data to no avail. What would be the correct permissions for the directory?.

I chose the /run directory because the commonly used /tmp does not guarantee persistence of the files (according to the FHS). I'm open to discussion about this decision, though.

My applications will run under Ubuntu Server 3.0.0-30 with SElinux disabled. nginx was installed using apt-get.

share|improve this question
What is OS? If Linux, nothing about SELinux? Is nginx chrooted? – Jiri Xichtkniha Feb 8 at 8:33
Show output of ls -Zld /run{,wsgi} perhaps? – warl0ck Feb 8 at 10:35
/run is for miscelaneous volatile runtime data, it is a tmpfs too. Isn't a bad place for your sockets, mind you, but is guaranteed not to survive reboots. Fedora mounts removable media for user under /run/media/user, perhaps /run/wsgi/sockets/ could be a good place. – vonbrand Feb 8 at 14:48

Know someone who can answer? Share a link to this question via email, Google+, Twitter, or Facebook.

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.