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.freedesktop.org/mailman/listinfo/systemd-devel
- [systemd-devel] User and Group permissions for .soc... Umut Tezduyar Lindskog
- Re: [systemd-devel] User and Group permissions... Lennart Poettering
- Re: [systemd-devel] User and Group permiss... David Timothy Strauss