Bug 103653
Summary: | up2date loops forever | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 3 | Reporter: | Mark Post <mark.post> |
Component: | up2date | Assignee: | Adrian Likins <alikins> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Steve Salevan <ssalevan> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.0 | CC: | nitind |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | 3U9 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-06-21 15:58:16 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Mark Post
2003-09-03 15:39:13 UTC
*** This bug has been marked as a duplicate of 102966 *** this is not a dup of 102966 as best I can tell >The sequence of steps I took is:
>/usr/sbin/up2date-nox -l
>I took the list of updates, and put them into a file, then
>cat rpmlist | xargs /usr/sbin/up2date-nox -f -d
This tells up2date to download (and _not_ install) the
package specified, and its deps. So no packages are ever
installed, and the rpm database is not changed.
So every time you run it, it downloads any new
packages it needs (it will display a progress
bar indicating it is getting already downloaded
packages, but will zip to 100%).
This doesnt look like a bug to me. Am I
missing something?
Yes, you are. :) I did _not_ reissue the up2date command. The problem is that up2date restarts itself, and does the whole thing, over and over and over again. It will never stop unless a cntl-c is issued. While this was going on, I fired up top to see what kind of system resources it was using: 96% of one of my two processors, or about 48% of my entire system. ah, I see. First guess is that the commandline "-d" is overriding the stuff to install up2date, and just installs it instead. That would cause looping like you mention. Fix is probabaly to disable the auto up2date up2date in cases where -d is installed (current policy is basically to only install the new up2date if doing something that would install packages [aka, `up2date foobar` or `update -u`]. I'll take a look and try to get this into 3.9.24 or so. I'll update the report when I build a version with a fix. should be fixed in 3.9.24 Looks good on both 4U5 and 3U9. This bug is CLOSED, CURRENTRELEASE. |