On Thursday, 20 June 2024 14:27:18 BST Jack wrote: > On 6/20/24 8:46 AM, Peter Humphrey wrote: > > Hello list, > > > > While building a new KDE system (see my post a few minutes ago), I'm > > finding the system stalling because it can't handle all its install jobs. > > I have this set: > > > > $ grep '\-j' /etc/portage/make.conf > > EMERGE_DEFAULT_OPTS="--jobs --load-average=30 [...]" > > I don't know how much it would matter, but are you missing a number > after --jobs?
Without a number of jobs specified in make.conf emerge will not limit the number of packages it tries to build, except it will not start new jobs while there are at least --load-average=30 running already. > > MAKEOPTS="-j16 -l16" > > > > The CPU has 24 threads and 64GB RAM, and lots of swap space, and those > > values have worked well for some time. Now, though, I'm going to have to > > limit the --jobs or the --load-average. > > > > On interrupting one such hang, I found that 32 install jobs had been > > waiting to run; is this limit hard coded? I take it the --load-average is what it says, an average, so it will jump above the specified number if you have not limited the --jobs number. > > I also saw "too many jobs" or > > something, and "could not read job counter". > > > > Is it now bug-report time? You could set up a swapfile, to avoid OOM situations, while you're tweaking the --jobs & --load-average.
signature.asc
Description: This is a digitally signed message part.
