Description of problem:
Yumex and yum can run at once because Yumex doesn't create a PID file - This
shouldn't be allowed, as running the two at once can cause issues.
Version-Release number of selected component (if applicable):
All, but currently testing the 1.1.0 branch
Steps to Reproduce:
1. Tell yum to do something
2. Run yumex
3. They will both run
Both run without errors
Yumex should create a lock and also check for existing ones, so only one is run
The behaviour required is already in yum; Running 2 'yum's at once gives an
error - Maybe just a simple 'import' and a function call is requried?
Thanks, that has totally slipped my mind, i have added some calls
to YumBase.doLock & YumBase.doUnLock and added some error catching if yum
alreasdy is locked.
Will be availible in yumex 1.1.2
Hmmm... This doesn't have to do anything yumex, but have you been noticing many
segfaults in FC6T2? I'm using development rawhide, and I'm getting quite a few
segfautls that end up corrupting the RPM DB, so I have to remove the stale locks
and --rebuilddb. Although, I think the segfaults comes from the RPM process, not
Im running FC6T2 + Updates from Rawhide, I dont have got any segfaults yet.
Hmmm... I'm just ran yumex 1.1.3 from development, then did 'yum update -y' and
there was no lock messages from either yumex or yum.
I have just retested i start yumex and i starts load yum metadata.
i run the following command:
#sudo yum install banshee
I get the following message from yum:
Existing lock /var/run/yum.pid: another copy is running. Aborting.
I have tried the other way around and then i get this message when yum starts to
Yum is locked by another application
Yumex first set the lock when it starts to load metadata, so i yumex is started
without loading metadata, you will not get an error before the metadata download
is run, by pressing the 'Refresh' button in the Repo view.
Just re-rested, it works... I must have been doing something wrong before.