Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

A note about socket files not to be placed in /tmp #511

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

gamboz
Copy link

@gamboz gamboz commented Sep 16, 2022

I've lost some time configuring apache-uwsgi interaction via unix domain sockets because I had the socket created by uwsgi in /tmp, but apache did not see it because it was launched by systemd with PrivateTemp=true.

So I'm proposing to add a note for who might have the same issue.

I've lost some time configuring apache-uwsgi interaction via unix domain sockets because I had the socket created by uwsgi in /tmp, but apache did not see it because it was launched by systemd with PrivateTemp=true.

So I'm proposing to add a note for who might have the same issue.
@IamPecker
Copy link

IamPecker commented Sep 16, 2022 via email

@gdamjan
Copy link
Contributor

gdamjan commented Nov 1, 2022

Ideally, under systemd you'd just use a systemd managed .socket
https://www.freedesktop.org/software/systemd/man/systemd.socket.html

that way you don't need to bother with setting up permissions to the socket and the uwsgi service and the nginx service.

@gamboz
Copy link
Author

gamboz commented Nov 1, 2022

@gdamjan yes. My point was only to remind ignorant people (like me) about this systemd behavior :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants