There is a lock, and I do believe that associated with it is a process-id. So
when another application tries for the same lock, before giving up, the
process-id is checked to see if it exists. If it does not, the lock is deleted
and the new lock is created.
I did find that yum put a lock in a subdirectory of /usr Its been a long time
since I had to clear it manually.
Also check /tmp Sometimes locks are placed there
--- On Fri, 1/23/09, Patrick Dupre <[email protected]> wrote:
From: Patrick Dupre <[email protected]>
Subject: Re: service
To: "Steven R. Ringwald" <[email protected]>
Cc: "Community assistance, encouragement, and advice for using Fedora."
<[email protected]>
Date: Friday, January 23, 2009, 6:06 AM
On Thu, 22 Jan 2009, Steven R. Ringwald wrote:
> On 1/22/2009 6:47 PM, Patrick Dupre wrote:
>> Hello,
>>
>> What is the service/daemon with make that rpm db is regularly locked ?
>
> yum-update ?
>
It is not running !
Another thing, are the lock managed ?
Many times if I make a rpm -qa
and I interrupt it, then their is a lock and I have to restart the machine.
How can I manage thsi.
Thank
-- ---
==========================================================================
Patrick DUPRÉ | |
Department of Chemistry | | Phone: (44)-(0)-1904-434384
The University of York | | Fax: (44)-(0)-1904-432516
Heslington | |
York YO10 5DD United Kingdom | | email: [email protected]
==========================================================================--
fedora-list mailing list
[email protected]
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
--
fedora-list mailing list
[email protected]
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
