Since a while emerge gets more and more problems with autofs. This is a regression as over the years there was never a problem with emerge in combination with autofs. emerge does access autofs mounts when it starts up, but only then. While emerge is running, if autofs does unmount a mount point in between, emerge does not really try to access the mountpoint in a way that causes autofs to mount the mountpoint again. This behaviour causes: 1. ebuilds will suddenly fail as emerge wants to copy files from the mount point and simply insists that the files don't exist. 2. ebuilds are silently corrupted as emerge does never try to access e.g. /etc/portage/patches when the autofs mount point is not mounted, emerge just pretends that there isn't any patch. To reproduce try to replace /etc/autofs/patches with a soft link pointing to a autofs mount point and see what happens during an ebuild when the mount point is not manually mounted in advance. Please do test emerge with autofs and fix the erratic behaviour. And while at it please find out why emerge takes more than 20 minutes to start up when there are more than a few entries in /etc/portage/package.use, and, yes, more than a few entries are perfectly legal. If this behaviour is desired, please add proper statements to the emerge man page, e.g. that 1. emerge will not support autofs any longer 2. emerge will consume unreasonable amounts of cpu time if /etc/portage/package.use is actually used. Sorry, I'm really frustrated with emerge being the central tool of Gentoo and getting more and more broken with every new release.
(In reply to Andreas Steinmetz from comment #0) > 1. emerge will not support autofs any longer There's never been any explicit autofs support, but per bug 679158 comment #18 you should try with FEATURES="-mount-sandbox -pid-sandbox" and let us know if that helps. > 2. emerge will consume unreasonable amounts of cpu time if > /etc/portage/package.use is actually used. That sounds like a performance issue in the config.setcpv method, which had some recent changes related to bug 373209 and bug 663278.
i have same issues. this bug report and solution was very helpful and working. tnx
