Hey, I use distcc for a while, basically I use it with a ssh user just like explained in the wiki page https://wiki.gentoo.org/wiki/Distcc Since a few weeks, I get a new error on some packages like app-shells/zsh, I find a workaround by adding a package.env that disable the sandbox FEATURES. The error appends at the end of the build, like: ``` * --------------------------- ACCESS VIOLATION SUMMARY --------------------------- * LOG FILE: "/var/log/sandbox/sandbox-4.log" * VERSION 1.0 FORMAT: F - Function called FORMAT: S - Access Status FORMAT: P - Path as passed to function FORMAT: A - Absolute Path (not canonical) FORMAT: R - Canonical Path FORMAT: C - Command Line F: link S: deny P: /root/.ssh/sockets/s0rin@8.8.8.8:22 A: /root/.ssh/sockets/s0rin@8.8.8.8:22 R: /root/.ssh/sockets/s0rin@8.8.8.8:22 C: ssh 8.8.8.8 distccd --inetd --enable-tcp-insecure F: unlink S: deny P: /root/.ssh/sockets/s0rin@8.8.8.8:22.Wm89C0VoE6x625sd A: /root/.ssh/sockets/s0rin@8.8.8.8:22.Wm89C0VoE6x625sd R: /root/.ssh/sockets/s0rin@8.8.8.8:22.Wm89C0VoE6x625sd C: ssh 8.8.8.8 distccd --inetd --enable-tcp-insecure * -------------------------------------------------------------------------------- ``` Maybe there is a better way to fix this ?
Looks like a local (mis)configuration problem. Who is s0rin?
Ahah, those are fake information to not show real information. So this error appends during the install phase, but yes maybe it is a missconfiguration, please check the log I attached.
Created attachment 599326 [details] build log of app-shells/zsh
I also attached a anonymized version of the portage ssh config file, but it is very simple.
Created attachment 599328 [details] portage ssh config
Hum maybe I did not express my issue clearly, sorry. My objective is to be able to share cpu power from several build machine, ideally each machine get pull some help from at least 1 other to build/upgrade faster. Before I used a nodistcc, for the packages that didn't worked with distcc, like gcc, and many others, but what I am trying to do is trim that list down. So this error is coming from many of those package, and I am wondering if there is a way, configuration or disabling some FEATURE, to get rid of this specific error (link / unlink). If a package can be build with distcc maybe we should change the ebuild of those, to avoid that kind of error, and maybe be changed by the maintainer if the cause of the error is no more.