Summary: | sys-devel/distcc - sandbox violation in /root/.ssh/sockets/s0rin@8.8.8.8:22 by ssh 8.8.8.8 distccd --inetd --enable-tcp-insecure | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Guillaume Seren <guillaumeseren> |
Component: | Current packages | Assignee: | Gentoo Cluster Team <cluster> |
Status: | UNCONFIRMED --- | ||
Severity: | normal | CC: | cluster |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
build log of app-shells/zsh
portage ssh config |
Description
Guillaume Seren
2019-12-12 23:25:42 UTC
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. |