F13-Question: Cannot start a new yum immediately after an old "yum update" ends

[Richard Shaw]

On Sat, Apr 3, 2010 at 1:59 AM, David Timms <dtimms at iinet.net.au> wrote:
> On 03/04/10 18:28, Robert G. (Doc) Savage wrote:
>>
>> On Sat, 2010-04-03 at 09:02 +0200, Joachim Backes wrote:
>>> What does the program "yumBackend.py" do? It seems it prevents a new yum
>>> from running:
> ...
>>> Sometimes it needs more than 1 min until yum runs again.
>>
>> I see this behavior in F12 too. I believe it's normal for yum to spend
>> some housekeeping time in background before finally releasing its
>> lockfile. Depending on the number and size of packages to be downloaded
>> and updated, there could be a fair amount of cache cleanup and writing
>> to rpm databases.
> I remember that as yum finishes, it triggers PackageKit to try to check
> for updates. This means it has to find and retrieve the small repo
> current info files from a mirror, for all the repos you have available.
> It can take a little while, when there is slow mirrors etc.
>
> Would it make sense for this triggering of PackageKit check to be held
> of for say 5 minutes after the end of a yum command, so that the user
> finds an immediately responsive yum sub-system ?

I agree, unless there is some technical reason that PackageKit needs
to be called immediately following a yum command it would be great if
it waited a while.

Richard