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 3ABF658973 for ; Sun, 17 Jan 2016 20:01:14 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 6D8AB21C0D7; Sun, 17 Jan 2016 20:01:11 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id D020821C02D for ; Sun, 17 Jan 2016 20:01:10 +0000 (UTC) Received: from [192.168.0.17] (ip68-5-185-102.oc.oc.cox.net [68.5.185.102]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: zmedico) by smtp.gentoo.org (Postfix) with ESMTPSA id 19E24340564 for ; Sun, 17 Jan 2016 20:01:10 +0000 (UTC) Subject: Re: [gentoo-portage-dev] dead emerge processes and/or lockfiles To: gentoo-portage-dev@lists.gentoo.org References: <20160117090635.6b77890d.dolsen@gentoo.org> From: Zac Medico Message-ID: <569BF303.3060408@gentoo.org> Date: Sun, 17 Jan 2016 12:01:07 -0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.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: <20160117090635.6b77890d.dolsen@gentoo.org> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Archives-Salt: 3b642f8d-51dd-43cd-b01a-cd423fe62d6d X-Archives-Hash: 089d06633e76949ab66cb353f14cc55c 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. -- Thanks, Zac