On Tue, 2010-07-20 at 17:16 -0400, JohnS wrote: > On Tue, 2010-07-20 at 14:30 -0400, James Antill wrote: > > 2. When reading the repodata sqlite DBs I _think_ sqlite takes read-only > > locks on the DB ... against this doesn't really help us, and if we > > haven't turned it off already it's very plausible that we will. > > Should only need row locking? Instead of the whole DB.
We don't alter these DBs, just create them once if we can't download them. So we could turn any locking off, if it's measurable and it isn't off already. > > ...we have plans to change #4 so that it'll work with normal users as > > well as root (ie. use a file based on cachedir). > > That's what I need to have a common NFS builder root for multi machine > access on need. Right, as I said, that will _help_ you ... but I'm less sure it'll solve your problem. For instance I'm pretty sure current code in YumBase.doLock() is not enough for 100% locking over NFS. One change you could try is to change YUM_PID_FILE to /var/cache/yum/yum.pid and see how much that helps you. > > In general for people who want this, I always recommend you read: > > > > http://yum.baseurl.org/wiki/YumMultipleMachineCaching > > Read the above link and thanks for it. Is there any kind a pre release > code for whats in working progress that will build under RHEL 5/CentOS 5 > or patches to the current yum version in them? I've been building the current RHEL-6.0 version of yum in a "RHEL-5 environment" here: http://people.redhat.com/jantill/yum/5-from-6/ ...but note that is not even close to supported, by anyone. Probably the biggest feature for you is that you can set: cachedir=/var/cache/yum/$basearch/$releasever ...so you can have one NFS dir. for both x86 and x86_64 machines (the same locking as RHEL-5 though). _______________________________________________ Yum-devel mailing list Yum-devel@lists.baseurl.org http://lists.baseurl.org/mailman/listinfo/yum-devel
