On 26.03.2016 17:37, Alan McKinnon wrote: > On 26/03/2016 17:46, Dan Johansson wrote: >> On my Raspberry Pi2 (running Gentoo of cause) I have a problem with >> portage, or rather with emerge. When emerging something I get some error >> messages about "shell-init:... permission denied" like this: >> >> ---------------------8<--------------------- Snip... >> ---------------------8<--------------------- >> >> The emerge continues and installs the software OK (as far as I can see). >> I tried to debug emerge (using --debug), but surprise surprise, just >> before the error messages shows there is a "set +x" in the output, hence >> I can not see which command it is that "produces" the error message and >> I can also not see the path/file that is the culprit. >> >> Any suggestions on how to debug this further? >> >> > > > > What user do you run emerge as? > It should be root > > Also check permissions on directories in /var/tmp/portage and all subdirs
User running emerge is root.
This is what my /var/tmp/portage looks like (when no emerge is running)
---------------------8<---------------------
# find /var/tmp/portage/ -type d -exec ls -pald {} +
drwxrwxrwt 5 portage portage 4096 Mar 26 17:53 /var/tmp/portage//
drwxrwxr-x 2 portage portage 4096 Mar 26 17:52 /var/tmp/portage/._unmerge_/
drwxrwsr-x 4 root portage 4096 Mar 24 09:49 /var/tmp/portage/.distcc/
drwxrwsr-x 2 root portage 4096 Mar 26 17:43
/var/tmp/portage/.distcc/lock/
drwxrwsr-x 2 root portage 4096 Mar 26 17:51
/var/tmp/portage/.distcc/state/
---------------------8<---------------------
This looks the same as on my other systems with the exception of the
.distcc (as this is the only system using distcc).
The .distcc is automatically created when emerging and distcc is enabled.
--
Dan Johansson, <http://www.dmj.nu>
***************************************************
This message is printed on 100% recycled electrons!
***************************************************
smime.p7s
Description: S/MIME Cryptographic Signature
