From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id D9BB258973 for ; Mon, 18 Jan 2016 12:37:58 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 1FCD521C016; Mon, 18 Jan 2016 12:37:57 +0000 (UTC) Received: from resqmta-ch2-01v.sys.comcast.net (resqmta-ch2-01v.sys.comcast.net [69.252.207.33]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id A177B21C010 for ; Mon, 18 Jan 2016 12:37:56 +0000 (UTC) Received: from resomta-ch2-10v.sys.comcast.net ([69.252.207.106]) by resqmta-ch2-01v.sys.comcast.net with comcast id 7Qdj1s0092JGN3p01Qdvx6; Mon, 18 Jan 2016 12:37:55 +0000 Received: from [192.168.1.13] ([76.106.83.43]) by resomta-ch2-10v.sys.comcast.net with comcast id 7Qdu1s00N0w5D3801QdupE; Mon, 18 Jan 2016 12:37:55 +0000 Subject: Re: [gentoo-portage-dev] dead emerge processes and/or lockfiles To: gentoo-portage-dev@lists.gentoo.org References: <20160117090635.6b77890d.dolsen@gentoo.org> <569BF303.3060408@gentoo.org> From: Joshua Kinard Message-ID: <569CDC87.9000902@gentoo.org> Date: Mon, 18 Jan 2016 07:37:27 -0500 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:42.0) Gecko/20100101 Thunderbird/42.0 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-portage-dev@lists.gentoo.org Reply-to: gentoo-portage-dev@lists.gentoo.org MIME-Version: 1.0 In-Reply-To: <569BF303.3060408@gentoo.org> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1453120675; bh=JlbaUMRSX/4JkHGcTC0VhD2Bc+miQ0YnjKrA48kEciU=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=jv8aWIjtgUEbdhP/DZQcZQOv5WajnRFyH3ToITUzRVLn1ZWCyUtM+15ecpahSYyBx bW3IpbluElbAucQyTviL4fk2LCyyLnynStusR6v+TwCuEjq7Fw8PznElI9EnB5hkLI o3Ig7GpavKT7Rwp/xnP67xTCSQIlMYHDl1ERP3VvSYbX1aC9rY7j6nCQB39nS8V/ok 2Hn2cdndi0wENvhnuNfiVQpBa4rRmnb+0QNnFXgHEW9osBau9tmFuAEqT3A+TZ9Omn kQJtYbHUIbaEyyZiq4KklSx5pUK7wm3uZoS/PwalQsZz0aZGDRS6GH1zUnoVL9dhef iUCXrK89fW43g== X-Archives-Salt: 87a14c6f-6c3d-4a6c-8c17-f828584e71bf X-Archives-Hash: 851a2d00233c9e8c9cc997d6785a6c54 On 01/17/2016 15:01, Zac Medico wrote: > On 01/17/2016 09:06 AM, Brian Dolbec wrote: >> >> I've read in several forum posts lately about emerge not running and >> the problem comes down to dead emerge processes and remaining lockfiles. >> >> Perhaps we should make an emaint module to search for and fix these. >> It should be easy enough. > > It would be nicer if we fixed whatever issue(s) cause the emerge > processes to hang up. How would the emaint module distinguish a "good" > emerge process from a "bad" one? I suppose you could strace it to see if > it has any activity. > I've been playing around with Gentoo/FreeBSD and have been noticing that emerge is leaving orphaned processes behind on that platform. Seems to be ecompressdir getting hung up. emerge itself just moves on, but after I accumulated ~5 of those stuck ecompressdir processes in a single run, I kill -9'ed them all. Didn't see side-effects similar to what's described in the original post, but the way to detect this issue might be to look for orphaned children processes lacking a parent PID, then reap them. --J