Hi Richard,
DNF uses three types of locks (metadata, download and rpmdb lock) to
allow more or less parallel execution of DNF commands.
IIRC, the actual issue with kmods has been already resolved in upstream
by switching rpmdb lock to blocking mode.
Regards,
Michal
On 07/16/2015 05:20 PM,
On Thu, Jul 16, 2015 at 1:42 PM, Przemek Klosowski
wrote:
> On 07/16/2015 01:19 PM, Eric Griffith wrote:
>
> I tried to do an install and an update on two different terminals on my
> machine yesterday. The second one didn't yell about an rpmdb lock but it did
> say that it was waiting on a process
On 07/16/2015 01:19 PM, Eric Griffith wrote:
I tried to do an install and an update on two different terminals on
my machine yesterday. The second one didn't yell about an rpmdb lock
but it did say that it was waiting on a process. So unless it broke
from an update last night / this morning t
I tried to do an install and an update on two different terminals on my
machine yesterday. The second one didn't yell about an rpmdb lock but it
did say that it was waiting on a process. So unless it broke from an update
last night / this morning then idk
On Jul 16, 2015 11:20 AM, "Richard Shaw" w
I remember frequently (to my dismay) getting messages from yum saying that
another process had a lock on the RPM database.
Due to a recent rash of issues with the akmods package I have been
investigating why the kmods are not getting installed.
Out of curiosity I tried running two dnf update inst