| 1 |
On 26/11/2015 01:33, lee wrote: |
| 2 |
> Alan McKinnon <alan.mckinnon@×××××.com> writes: |
| 3 |
> |
| 4 |
>> On 25/11/2015 13:30, lee wrote: |
| 5 |
>>> walt <w41ter@×××××.com> writes: |
| 6 |
>>> |
| 7 |
>>>> On Tue, 24 Nov 2015 23:39:01 +0100 |
| 8 |
>>>> lee <lee@××××××××.de> wrote: |
| 9 |
>>>> |
| 10 |
>>>>> |
| 11 |
>>>>> ... |
| 12 |
>>>> |
| 13 |
>>>> |
| 14 |
>>>>> Well, ok, the file is still locked. |
| 15 |
>>>>> |
| 16 |
>>>>> 'group-' looks like a backup, and 'group.lock' contains 10563, which |
| 17 |
>>>>> is the pid of groupadd. I'd think that's ok. |
| 18 |
>>>>> |
| 19 |
>>>>> So what all does it take to create a system group? I suppose I could |
| 20 |
>>>>> kill groupadd and the emerging might go on, though I wonder what the |
| 21 |
>>>>> problem might be and if something else besides making an entry to |
| 22 |
>>>>> /etc/group needs to be done. What might require an indefinite delay |
| 23 |
>>>>> here? |
| 24 |
>>>> |
| 25 |
>> [...] |
| 26 |
>>> I'll probably reboot today or tomorrow because I need to have a |
| 27 |
>>> differently configured kernel running to be able to do some traffic |
| 28 |
>>> shaping. If I do that, I'll probably just kill groupadd and see if the |
| 29 |
>>> merging continues. |
| 30 |
>> |
| 31 |
>> The group is already created so kill groupadd. One of three things will |
| 32 |
>> happen: |
| 33 |
>> |
| 34 |
>> 1. the emerge will continue. Do nothing |
| 35 |
>> 2. The emerge will fail with a groupadd error. Restart the emerge |
| 36 |
>> 3. Nothing will change. Kill the emerge and restart it |
| 37 |
>> |
| 38 |
>> If the lockfile persists after killing groupadd, delete it. |
| 39 |
> |
| 40 |
> Well, yes ... I just would like to know what the problem might be. |
| 41 |
> |
| 42 |
|
| 43 |
I doubt you'll ever find out. Something went wrong, a process hung and |
| 44 |
it's likely a once off. Deal with it, move on. |
Archives