Bug 179543 - Allow "yum search" if "yum install" already running
Allow "yum search" if "yum install" already running
Product: Fedora
Classification: Fedora
Component: yum (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jeremy Katz
: FutureFeature
Depends On:
  Show dependency treegraph
Reported: 2006-02-01 03:43 EST by James Hunt
Modified: 2014-01-21 17:53 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-04-19 16:38:30 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description James Hunt 2006-02-01 03:43:16 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.7.12) Gecko/20050922 Fedora/1.0.7-1.1.fc4 Firefox/1.0.7

Description of problem:
If a "yum install" is in progress, and a user attempts to run,
"yum search <keyword>", the search fails with the error:

  Existing lock /var/run/yum.pid: another copy is running. Aborting.

It would be great if yum could be updated to allow a search command to be run whilst an install/update is in progress. The search is effectively a "read-only" operation, so this should be possible to do. The only issue I can think of is how you handle the "status/repo" field in the search output. For example, the lines below are snippets from the output of "yum search python":

python-simpletal.noarch                  4.1-1.fc4              extras
pyorbit.i386                             2.0.1-4                installed

If I was in the process of running, "yum install python-simpletal", and I then ran, "yum search python", if you allowed multiple invocations, it could either disregard the in-progress transaction and simply report python-simpletal as "extras", or if it was really clever, the "yum search python" command could query the in-progress "yum install python-simpletal" transaction, and show the 3rd field as "locked" or maybe even "install-pending" / "update-pending" / "delete-pending", or similar:

python-simpletal.noarch                  4.1-1.fc4              install-pending
pyorbit.i386                             2.0.1-4                installed

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. yum install <package> &
2. yum search <package>

Actual Results:  Existing lock /var/run/yum.pid: another copy is running. Aborting.

Expected Results:  yum could allow the search to return the results as expected.

Additional info:
Comment 1 Seth Vidal 2006-02-10 01:43:14 EST
not really. We need to be sure the sqlite db's aren't being written to at the
same time, so we have to lock at least for the duration of the db create.

I don't see this as terribly onerous, though.

Note You need to log in before you can comment on or make changes to this bug.