Open JP-Ellis opened 2 weeks ago
Did you try ExecStartPost=chmod 775 /var/run/pueue/pueue.socket
in your systemd file?
I had tried that, but I thought it might be better if pueue
itself handled the permissions.
As to why ExecStartPost
did not always work, it was generally because chmod
is executed too fast and the socket may not exist yet. I know this can be fixed by inserting ExecStartPost=sleep 2
before the chmod
command; but thought this solution to be somewhat inelegant.
Let me know what you think of my suggestion of adding another configuration option. I would be happy to contribute the PR myself.
Fair points :D
It's a small change as well, feel free to go ahead :)
A detailed description of the feature you would like to see added.
I would like the ability to configure the socket permissions. For example:
Not sure whether the permissions should be in standard octal notation, the more verbose
rwxr-xr-x
or even as a further dictionary:Explain your usecase of the requested feature
I have a shared
pueued
instance running as a systemd service (happy to share the configuration) which I would ideally like to reach over sockets.The
pueued
daemon by default creates the socket with permissionsrwxr-xr-x
thereby preventing anyone from writing to the socket other than the service user.I would like to spawn this process under a special
pueue:pueue
user and group, and grant users of thepueue
group the ability to write to the socket. This would require setting the socket's permissions torwxrwxr-x
.Alternatives
The current alternative is to manually change the socket permissions after the process is spawned:
This will work so long as the process keeps running, but will of course fail after the process has restarted.
Additional context
No response