An alternative workaround is to put the socket into a directory that
has the permissions desired. If you can't read the directory, you
can't use a socket in that directory.
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.fr
On Mon, 12.05.14 12:03, Umut Tezduyar Lindskog (u...@tezduyar.com) wrote:
> Hi,
>
> How do we set the user:group of a socket created by .socket file?
>
> We have thought User= and Group= should do the job but that doesn't
> seem to be the case. Is this a missing feature or should we just set
Th
Hi,
How do we set the user:group of a socket created by .socket file?
We have thought User= and Group= should do the job but that doesn't
seem to be the case. Is this a missing feature or should we just set
the permissions by ExecStartPost= on .socket file?
Umut
_