suddenly my portage started acting realy weird, emerge still works somewhat, but as soon as i try to actualy install or update a package the sandbox process starts utilizing the CPU to 100% and eats memory. here's what strace tell's me: [snip] stat64("/usr/portage/x11-themes/povray", 0xbffec4b4) = -1 ENOENT (No such file or directory) stat64("/usr/portage/x11-wm/povray", 0xbffec4b4) = -1 ENOENT (No such file or directory) stat64("/usr/portage/virtual/povray", 0xbffec4b4) = -1 ENOENT (No such file or directory) stat64("/usr/portage/media-gfx/povray", {st_mode=S_IFDIR|0755, st_size=88, ...}) = 0 stat64("/usr/portage/media-gfx/povray", {st_mode=S_IFDIR|0755, st_size=88, ...}) = 0 stat64("/usr/portage/media-gfx/povray", {st_mode=S_IFDIR|0755, st_size=88, ...}) = 0 stat64("/usr/portage/media-gfx/povray", {st_mode=S_IFDIR|0755, st_size=88, ...}) = 0 write(1, "Calculating dependencies \10\\", 28Calculating dependencies \) = 28 stat64("/usr/portage/media-gfx/povray/povray-3.50a.ebuild", {st_mode=S_IFREG|0644, st_size=3384, ...}) = 0 stat64("/var/cache/edb/dep/media-gfx/povray-3.50a", {st_mode=S_IFREG|S_ISGID|0664, st_size=354, ...}) = 0 stat64("/usr/portage/media-gfx/povray/povray-3.50a.ebuild", {st_mode=S_IFREG|0644, st_size=3384, ...}) = 0 open("/var/cache/edb/dep/media-gfx/povray-3.50a", O_RDONLY|O_LARGEFILE) = 3 fstat64(3, {st_mode=S_IFREG|S_ISGID|0664, st_size=354, ...}) = 0 old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x401d9000 read(3, "media-libs/libpng sys-libs/zlib "..., 8192) = 354 read(3, "", 4096) = 0 close(3) = 0 munmap(0x401d9000, 4096) = 0 stat64("/var/db/pkg/media-libs", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0 stat64("/var/db/pkg/sys-libs", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0 stat64("/var/db/pkg/sys-libs", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0 stat64("/var/db/pkg/sys-libs", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0 stat64("/var/db/pkg/sys-libs", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0 stat64("/var/db/pkg/virtual", 0xbffec4b4) = -1 ENOENT (No such file or directory) stat64("/var/db/pkg/virtual", 0xbffebf34) = -1 ENOENT (No such file or directory) stat64("/var/db/pkg/virtual", 0xbffebdd4) = -1 ENOENT (No such file or directory) stat64("/var/db/pkg/x11-base", {st_mode=S_IFDIR|0755, st_size=91, ...}) = 0 stat64("/var/db/pkg/media-libs", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0 stat64("/var/db/pkg/media-libs", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0 stat64("/var/db/pkg/sys-libs", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0 stat64("/var/db/pkg/virtual", 0xbffec4b4) = -1 ENOENT (No such file or directory) stat64("/var/db/pkg/media-libs", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0 write(1, "\10\10 ...done!\n", ...done! ) = 12 write(1, ">>> emerge media-gfx/povray-3.50"..., 39>>> emerge media-gfx/povray-3.50a to / ) = 39 stat64("/usr/portage/media-gfx/povray/povray-3.50a.ebuild", {st_mode=S_IFREG|0644, st_size=3384, ...}) = 0 getcwd("/tmp/temp/portage-2.0.27", 1026) = 25 stat64("/var/tmp/portage/povray-3.50a", {st_mode=S_IFDIR|0755, st_size=31, ...}) = 0 stat64("/var/tmp/portage/povray-3.50a/temp", {st_mode=S_IFDIR|0755, st_size=35, ...}) = 0 open("/usr/src/linux/include/linux/version.h", O_RDONLY|O_LARGEFILE) = 3 fstat64(3, {st_mode=S_IFREG|0644, st_size=138, ...}) = 0 old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x401d9000 read(3, "#define UTS_RELEASE \"2.4.18-wolk"..., 8192) = 138 read(3, "", 4096) = 0 close(3) = 0 munmap(0x401d9000, 4096) = 0 fork() = 10618 wait4(10618, that's all
what version of portage ?
installed portage is 2.0.27, and portage
installed portage is 2.0.27, and portageä-rescue showed the same behaviour for me
it's an easy fix. check your /tmp directory for files called sandboxpid rm those files, and you'll be sorted.
thx seemant, that fixed it
