Bug 19646 - Enhancement: avoid percentage info in log files
Enhancement: avoid percentage info in log files
Status: CLOSED CURRENTRELEASE
Product: Red Hat Linux
Classification: Retired
Component: up2date (Show other bugs)
7.0
i386 Linux
low Severity low
: ---
: ---
Assigned To: Preston Brown
Jay Turner
:
: 25223 (view as bug list)
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2000-10-23 20:10 EDT by Need Real Name
Modified: 2015-01-07 18:42 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2001-03-01 15:49:01 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Need Real Name 2000-10-23 20:10:35 EDT
This is a request for a minor enhancement.

Since I can't at the moment use up2date as normally intended
(see bug 19069, update agent fatal error), I tried:
    update -l >file.log
so I could get a list of packages to update.

The percentage done info that is normally output over and over
to the same line on the console is in the file.
It would be good to suppress the percentage done information
when appropriate and where it would not
interfere with the gui's display of percentage
done (e.g., if output is not a tty).

Also, as another nit to pick, package names are displayed with version
and release numbers in separate columns.  It would be nice if there
was an option to display the package file names to make it easier  to
retrieve them by other methods.
Comment 1 Cristian Gafton 2001-02-19 20:32:59 EST
Assigned QA to jturner
Comment 2 Preston Brown 2001-02-26 18:40:21 EST
*** Bug 25223 has been marked as a duplicate of this bug. ***
Comment 3 Preston Brown 2001-03-01 15:48:57 EST
fixed in CVS.
Comment 4 Jay Turner 2001-03-02 11:09:21 EST
Confirmed resolved in the 3/2/01 CVS code.
Comment 5 Jay Turner 2001-03-02 11:14:13 EST
Confirmed resolved in the 3/2/01 CVS code.

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