-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
Sokets and RuntimeDir with correct owner and mode #8635
Comments
Sorry guys, problem was solved by using another dir for socket: and for service: Now it works. Issue can be closed I think. |
Yeah, the I'll close the issue now. |
`SocketUser=` might have inconsistent results if they're inside a path specified by `RuntimeDirectory=` (or any other directory option where directories are chown'ed on startup). Especially in the case of creating a socket-activated service that's reachable for another user (the most common usecase for this option), it feels prudent to document this caveat, considering how frequently these unix domain sockets happen to be created in /run. I just ran into this, and it seems systemd#8635 is at least another documented case.
I just ran into this as well, opened #32503 so hopefully less people will run into it in the future. |
`SocketUser=` might have inconsistent results if they're inside a path specified by `RuntimeDirectory=` (or any other directory option where directories are chown'ed on startup). Especially in the case of creating a socket-activated service that's reachable for another user (the most common usecase for this option), it feels prudent to document this caveat, considering how frequently these unix domain sockets happen to be created in /run. I just ran into this, and it seems systemd#8635 is at least another documented case.
I have an issue with sockets and RuntimeDir.
veronica.socket:
veronica.service:
Now, after reloading
systemctl daemon-reload
, I start socket:note, that RuntimeDir was created with owner root:root
and start service:
You can see, that when I started service, RuntimeDir was deleted and created with owner arthur:admins.
I expect, that when I create socket, RuntimeDir must be created with owner and mode, taken from
veronica.service
, and then when I start service, runtime dir must contain veronica.socket and veronica.pid filesThe text was updated successfully, but these errors were encountered: