From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: emerging squid indefinitely
Date: Wed, 25 Nov 2015 18:53:50 +0200 [thread overview]
Message-ID: <5655E79E.4080403@gmail.com> (raw)
In-Reply-To: <87mvu2co4z.fsf@heimdali.yagibdah.de>
On 25/11/2015 13:30, lee wrote:
> walt <w41ter@gmail.com> writes:
>
>> On Tue, 24 Nov 2015 23:39:01 +0100
>> lee <lee@yagibdah.de> 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
next prev parent reply other threads:[~2015-11-25 16:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-23 15:02 [gentoo-user] emerging squid indefinitely lee
2015-11-23 15:25 ` Alan McKinnon
2015-11-23 21:04 ` lee
2015-11-23 22:12 ` Todd Goodman
2015-11-23 22:28 ` Alan McKinnon
2015-11-24 22:39 ` lee
2015-11-25 0:32 ` [gentoo-user] " walt
2015-11-25 11:30 ` lee
2015-11-25 16:53 ` Alan McKinnon [this message]
2015-11-25 23:33 ` lee
2015-11-26 7:58 ` Alan McKinnon
2015-11-26 0:03 ` walt
2015-11-26 7:57 ` Alan McKinnon
2015-11-26 9:48 ` Peter Humphrey
2015-11-26 11:22 ` waltdnes
2015-11-26 17:35 ` J. Roeleveld
2015-11-26 9:51 ` Neil Bothwick
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5655E79E.4080403@gmail.com \
--to=alan.mckinnon@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox