|
How long it takes to rebuild a rpm database ? just cca ?
Because I just ended Up with the same problem with yum stucked. I needed to SIGHUP him and deleted "__db.*" files to unlock access to him once more. On my next try I get stucked again. I have done the same thing as before to try to solve it with addition I deleted the whole YUM cache directory { with back-up ofcoarse } and a tryed to install package I desired once again .. and now it is almost 1hour 30min and yum takes still 98% CPU and ended up with
#yum install mplayer
~~output ommited~~
.
.
.
~~output ommited~~
Added 5985 new packages, deleted 0 old in 228.78 sek.
Resolving Dependencies
--> populating transaction ...
---> Downloading Header for mplayer
mplayer-1.0-0.28.pre8.fc5 |=============================| 29kB 00:02
---> package set to to be updated
--> Runnung Transaction test
{{ srr for this non copy paste reply but for a good reason I am unable to copy paste the terminal output. }}
and this I see for about an hour and a half ... what is happening? .. I am thinking that rpm database is corrupted but shoud I leave yum running for a while? or SIGHUP and start rebuilding rpm database?
|
