A note about socket files not to be placed in /tmp #511
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
|
您的邮件我已收到，我将会尽快给您回复信息。
|
|
Ideally, under systemd you'd just use a systemd managed .socket that way you don't need to bother with setting up permissions to the socket and the uwsgi service and the nginx service. |
|
@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
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.