[Yum-devel] locking

seth vidal skvidal at fedoraproject.org
Thu Feb 21 03:57:12 UTC 2008


Encountered a bug tonight that got me thinking about our locking and
some issues.

1. unless an app locks, explicitly, nothing in our current
infrastructure enforces it to happen.

2. if a user is running on their own cachedir from two different
instances the instances will happily trample over each other and do
'odd' things

3. the same is true for misbehaving root-run apps, too.

With this in mind would it be a good idea to change yum's lock mechanism
such that:

- the global lock means "the rpmdb is locked/transaction in progress"
- each repo cachedir had a lockfile that could be placed to keep that
repository dir from being changed


thoughts?
-sv

 
-- 
I only speak for me.




More information about the Yum-devel mailing list