Red Hat Bugzilla – Bug 192770
tar produces verbose output, even when verbose is not specified
Last modified: 2007-11-30 17:07:25 EST
Description of problem:
tar produces verbose output, even when -v is not specified.
Version-Release number of selected component (if applicable):
RHEL 4 fastrack channel tar, version tar-1.14-10.RHEL4
Steps to Reproduce:
1. install tar
2. Run a tar backup command like -> tar --newer=./backup.timestamp -czf
3. Note that unchanged files are also listed in the output, with "file is
unchanged; not dumped"
4. This extra output was not in previous versions of tar before this one.
All files are listed in tar output, even unchanged files.
Only changed files should produce output unless -v is specified.
Email communication with Sergey Poznyakoff (tar developer) confirms that this
'feature' of tar was added, then reverted because of its annoyance. It should
now only be available with -v or --verbose.
Email communication with sergey copied below
> A while back, someone posted a bug / feature request for version 1.15.1 to
> disable the "file is unchanged; not dumped" messages that occur when doing a
> backup with --newer, or a switch to revert to the old behavior.
Recent versions print this message only if given the -v (--verbose)
This added output was not in previous versions of tar released in RHEL, nor is
it produced by current vanilla tar source (version 1.15.90). This addded output
is far from desirable and increases the size of backup logs from 3-4K daily to
Created attachment 129846 [details]
Created attachment 129894 [details]
patch of the previous patch
the previous patch seemed to be made from an attempted patch, and not the tar
source. This one should apply cleanly.
*** Bug 205877 has been marked as a duplicate of this bug. ***
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.