| View previous topic :: View next topic |
| Author |
Message |
toralf
Developer
Joined: 01 Feb 2004
Posts: 3922
Location: Hamburg
|
 Posted: Thu Aug 27, 2015 8:08 pm Post subject: [solved] sandbox issues |
 |
|
At my tinderbox I get often sandbox issues of this kind: | Code: | cat /var/log/sandbox/sandbox-27294.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: mkdir
S: deny
P: ././var/cache/fonts/tfm
A: /var/cache/fonts/tfm
R: /var/cache/fonts/tfm
C: mkdir ././var/cache/fonts/tfm
|
This is not related to a particular package (althought the last time it appeared with sci-chemistry/gromacs : bug 558724
Any hint about the root cause ?
Last edited by toralf on Sat Nov 28, 2015 9:05 am; edited 1 time in total |
|
| Back to top |
|
 |
SpaceToast
n00b
Joined: 16 Oct 2015
Posts: 19
|
| Posted: Fri Oct 16, 2015 8:01 pm Post subject: |
|
|
How exactly are you running your tinderbox?
Is it in a chroot?
It looks like it's being denied creating a /var/cache/* directory due to not being root (portage typically has userprivs and usersandbox both enabled), which can misbehave in chroots and/or other similar situations.
Try running this with FEATURES=-usersandbox. |
|
| Back to top |
|
|
Hu
Moderator
Joined: 06 Mar 2007
Posts: 21633
|
| Posted: Sat Oct 17, 2015 12:47 am Post subject: |
|
|
Sandbox errors can, of course, be suppressed by not using the sandbox. However, I think toralf wants to know how to track and prevent the situation that is causing the disallowed access.
The double leading ./ looks to me like layers of some variable that should have pointed under $D, but instead expanded to ./. If you get an environment file for the failure, you could check for variables that are assigned the value of ./. |
|
| Back to top |
|
|
|
Portage & Programming
