Red Hat Bugzilla – Bug 135370
yum search should not check lockfile
Last modified: 2014-01-21 17:50:23 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3)
Description of problem:
A yum search should be possible even if another yum is running.
e.g. tty1 has a yum install running, tty2 should allow a yum search
e.g. tty1 has a yum search running, tty2 should allow a yum search
I think up2date allows this.
search attempts to read from the rpmdb and from the metadata files.
it can't know the state of those files and/or potentially modify the
metadata files (downloading updated files) during that process.
Not sure how to make that work together.
Marking this as WONTFIX
Okay, but up2date lets me.
Originally an FC3-beta bug.
yum-3.2.7-1.fc8 as @ nov07 still exhibits this behaviour.
Competing package managers do not share this issue:
Gentoo emerge can emerge several package/dependancy streams concurrently and
only blocks on a per package level if its an outstanding deps. in its stack and
already beoing processed;
Debian allows apt-cache searches whilst performing apt-get/dpkg operations....
The correct behavoiur could be:
only get write lock when actually required, relinquish afterwards..... allowing
at least 'yum -C search' to work...