96 – sandbox reports access violation if /var/tmp/portage is a symlink

Bug 96 - sandbox reports access violation if /var/tmp/portage is a symlink

Summary: sandbox reports access violation if /var/tmp/portage is a symlink

Status:	RESOLVED FIXED

Alias:	None

Product:	Portage Development
Classification:	Unclassified
Component:	Unclassified (show other bugs)
Hardware:	x86 Linux

Importance:	High normal
Assignee:	Geert Bevin

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2002-01-09 10:40 UTC by Vitaly Kushneriuk
Modified:	2011-10-30 22:17 UTC (History)
CC List:	0 users

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Vitaly Kushneriuk 2002-01-09 10:41:00 UTC

sandbox reports access violation during unpack stage of the ebuild
when /var/tmp/portage is a symlink to other place[X].
To solve the problem I did:

rm -f /var/tmp/portage
mkdir /var/tmp/portage
mount -o bind X /var/tmp/portage

This is just a workaround, I think sandbox should handle this internaly.

Comment 1 Geert Bevin 2002-01-11 14:59:00 UTC

You shouldn't create a symlink, but set the PORTAGE_TMPDIR env var to
/somewhere/place/tmp instead of /var/tmp. The sandbox handles that.