[Linux] Unix Domain Socket permissions prevent regular user from running boinccmd

[chiraag-nataraj]

The setup is the following:

1. cd /var/lib/boinc-client
2. sudo -u boinc /usr/bin/boinc --no_priority_change --gui_rpc_unix_domain
3. boinccmd --unix_domain --get_host_info

This returns can't connect to Unix domain socket. A quick investigation reveals that:

$ ls -lh boinc_socket
srwxr-xr-x 1 boinc boinc 0 Mar 31 17:51 boinc_socket

So nobody but the owner (user boinc) can write to the socket. This seems to be relevant, since running sudo -u boinc boinccmd --unix_domain --get_host_info succeeds. I am in the boinc group:

$ groups
chiraag tty cdrom floppy sudo audio dip video plugdev netdev proc bluetooth lpadmin scanner boinc

I suspect the default umask should be changed when the socket is created.

[update]
Running sudo chmod 775 boinc_socket indeed fixes the problem and boinccmd works as expected.

[chiraag-nataraj]

Is this a problem in my personal config? Could the problem be that boinc is being started through systemd?

[chiraag-nataraj]

Bump. Do you need more information? Is there anything else I can provide to help with debugging?