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 7EE061384B4 for ; Wed, 25 Nov 2015 16:55:09 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 28F1421C085; Wed, 25 Nov 2015 16:55:00 +0000 (UTC) Received: from mail-wm0-f43.google.com (mail-wm0-f43.google.com [74.125.82.43]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 0956821C06C for ; Wed, 25 Nov 2015 16:54:58 +0000 (UTC) Received: by wmuu63 with SMTP id u63so146002272wmu.0 for ; Wed, 25 Nov 2015 08:54:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-type:content-transfer-encoding; bh=YekduosFKqL2uriU9bdhBNs91uVa5Zu5wtwpAnu7MzE=; b=U+ZI1DAx234xEQX8PhhbCG1u5guFZJDmlrpG2fgqierE3xZuEWCFb4jj22kPi85sdz 9gpVGiqH3gNk9MIIQ18aCKJmR6rixs0mjEpLJPT2qeJa2qxbKTU5KtEHL1jOQypMYF5a i3a3KwdB6NfIievyUOhqxarmsjFdW5tzmwCGw0ufwrpRL0gHdLUisnqCJeHUvaWZsVTS CJbLMdu2rprjA7OABph4TeFUrvhWexg7Xx4ppBhP+kCEbR2GleAsaT4cOMKMq6Z8DUn/ xDTmpYbuQsbhuTOiwbdY6vPbJqmXT23pKk2cJnILyD6jfB87j03Zx5B6rLG8mLu4XdzJ d7fw== X-Received: by 10.195.11.101 with SMTP id eh5mr44826100wjd.104.1448470497810; Wed, 25 Nov 2015 08:54:57 -0800 (PST) Received: from [172.20.0.40] ([165.255.112.248]) by smtp.googlemail.com with ESMTPSA id w67sm4355916wmw.17.2015.11.25.08.54.56 for (version=TLSv1/SSLv3 cipher=OTHER); Wed, 25 Nov 2015 08:54:56 -0800 (PST) Subject: Re: [gentoo-user] Re: emerging squid indefinitely To: gentoo-user@lists.gentoo.org References: <87oaekg3nz.fsf@heimdali.yagibdah.de> <56532FE3.1060708@gmail.com> <87d1v0e8be.fsf@heimdali.yagibdah.de> <5653931A.3000701@gmail.com> <87ziy3c9a2.fsf@heimdali.yagibdah.de> <20151124163238.00c00dbb@a6> <87mvu2co4z.fsf@heimdali.yagibdah.de> From: Alan McKinnon X-Enigmail-Draft-Status: N1110 Message-ID: <5655E79E.4080403@gmail.com> Date: Wed, 25 Nov 2015 18:53:50 +0200 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-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 In-Reply-To: <87mvu2co4z.fsf@heimdali.yagibdah.de> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Archives-Salt: d8eae55f-3ac1-45ea-bb68-d5d9d5fb109f X-Archives-Hash: 8b1ce43d19315801bf5d64b17769df35 On 25/11/2015 13:30, lee wrote: > walt writes: > >> On Tue, 24 Nov 2015 23:39:01 +0100 >> lee wrote: >> >>> >>> ... >> >> >>> Well, ok, the file is still locked. >>> >>> 'group-' looks like a backup, and 'group.lock' contains 10563, which >>> is the pid of groupadd. I'd think that's ok. >>> >>> So what all does it take to create a system group? I suppose I could >>> kill groupadd and the emerging might go on, though I wonder what the >>> problem might be and if something else besides making an entry to >>> /etc/group needs to be done. What might require an indefinite delay >>> here? >> >> Any unusual network activity? (DNS lookups that shouldn't be >> happening, etc.) > > There's nothing suspicious in the firewall log and no unexpected DNS > queries. Ignore DNS, it has absolutely nothing to do with creating a group. A common human trait in dealing with problems with unknown causes is to start investigating all manner of weird and entirely unrelated things. I suppose theoretically you might discover some interaction between them in truly bizarre conditions but that's never something you entertain. Much like you don't check the health of your dog when investigating a flat type (protests about dogs biting tyres and getting stomach upsets notwithstanding) > The emerge before this one was apache, which I suppose also creates a > system group, and that worked just fine. > > I'll probably reboot today or tomorrow because I need to have a > differently configured kernel running to be able to do some traffic > shaping. If I do that, I'll probably just kill groupadd and see if the > merging continues. The group is already created so kill groupadd. One of three things will happen: 1. the emerge will continue. Do nothing 2. The emerge will fail with a groupadd error. Restart the emerge 3. Nothing will change. Kill the emerge and restart it If the lockfile persists after killing groupadd, delete it. -- Alan McKinnon alan.mckinnon@gmail.com