Therefore, when you install RPM, it creates the so-called rpm database lock, and this lock file prevents another instance of rpm from starting (and by the yum association). I guess this was put in place to ensure that the transaction does not get confused when several packages try to install. Imagine that you have a package that requires an updated version of lib that you are already installing, how it could happen if two processes tried to change these files one by one, as if they would link the library to which reference ones problems may be, etc.?
, RPM , , rpm, , , .
, , , RPM? :
WHERE, RPM , - EPEL , , , , , , , .
, , yum . , , , .
, , . , ? RPM, ( ), , , ( , )?
, , , .