1 |
On 01/17/2016 15:01, Zac Medico wrote: |
2 |
> On 01/17/2016 09:06 AM, Brian Dolbec wrote: |
3 |
>> |
4 |
>> I've read in several forum posts lately about emerge not running and |
5 |
>> the problem comes down to dead emerge processes and remaining lockfiles. |
6 |
>> |
7 |
>> Perhaps we should make an emaint module to search for and fix these. |
8 |
>> It should be easy enough. |
9 |
> |
10 |
> It would be nicer if we fixed whatever issue(s) cause the emerge |
11 |
> processes to hang up. How would the emaint module distinguish a "good" |
12 |
> emerge process from a "bad" one? I suppose you could strace it to see if |
13 |
> it has any activity. |
14 |
> |
15 |
|
16 |
I've been playing around with Gentoo/FreeBSD and have been noticing that emerge |
17 |
is leaving orphaned processes behind on that platform. Seems to be |
18 |
ecompressdir getting hung up. emerge itself just moves on, but after I |
19 |
accumulated ~5 of those stuck ecompressdir processes in a single run, I kill |
20 |
-9'ed them all. Didn't see side-effects similar to what's described in the |
21 |
original post, but the way to detect this issue might be to look for orphaned |
22 |
children processes lacking a parent PID, then reap them. |
23 |
|
24 |
--J |