On Tuesday 13 December 2011 08:09:08 Jim Meyering wrote:
Paul Eggert wrote:
On 12/12/11 14:58, Eric Blake wrote:
Files with multiple links shall be counted and written for only one
entry. The directory entry that is selected in the report is
unspecified.
Yes, that's partly what
On 12/13/11 08:46, Kamil Dudka wrote:
If I understand it correctly, the
old behavior was violating POSIX whereas the current default behavior is
correct. I tried du --count-links with the original reproducer and it seemed
to work fine. So what would be the point in adding a new option?
On 12/13/2011 09:46 AM, Kamil Dudka wrote:
I agree that printing 0 X for these seems inconsistent with the
elision mandated for the second and subsequent encounter of a file,
but I suppose command line arguments are intrinsically different
enough that handling them specially makes sense.
On Tuesday 13 December 2011 18:16:12 Eric Blake wrote:
I think the proposal is to add a new option that forces du to reset its
duplicate inode hash table for each command line argument, to make
behavior more like traditional du, even though it means -s can then
output a larger usage by summing
On 12/13/2011 10:37 AM, Kamil Dudka wrote:
On Tuesday 13 December 2011 18:16:12 Eric Blake wrote:
I think the proposal is to add a new option that forces du to reset its
duplicate inode hash table for each command line argument, to make
behavior more like traditional du, even though it means
On 12/13/11 09:16, Eric Blake wrote:
Or maybe --count-links gains an optional argument, that says how to
count links:
--count-links=none - POSIX behavior (if POSIX requires elision across
command line arguments
--count-links=per-directory - traditional behavior, resetting hash
between
Hi,
the following upstream commit introduces a major change in behavior of du
when multiple arguments are specified:
http://git.savannah.gnu.org/cgit/coreutils.git/commit/?id=efe53cc
... and the issue has landed as a bug in our Bugzilla:
https://bugzilla.redhat.com/747075#c3
Was such a change
On 12/12/2011 05:50 AM, Kamil Dudka wrote:
Hi,
the following upstream commit introduces a major change in behavior of du
when multiple arguments are specified:
http://git.savannah.gnu.org/cgit/coreutils.git/commit/?id=efe53cc
... and the issue has landed as a bug in our Bugzilla:
On 12/12/2011 03:33 PM, Eric Blake wrote:
However, changing the numbers is one thing and missing lines in the output
of du is quite another thing.
Yes, that's the bug I think we introduced - we are mistakenly eliding
lines of output, rather than listing those directories with 0 attributed
On 12/12/11 14:58, Eric Blake wrote:
Files with multiple links shall be counted and written for only one
entry. The directory entry that is selected in the report is unspecified.
Yes, that's partly what motivates the current GNU du behavior:
the idea is to implement this notion consistently
Paul Eggert wrote:
On 12/12/11 14:58, Eric Blake wrote:
Files with multiple links shall be counted and written for only one
entry. The directory entry that is selected in the report is unspecified.
Yes, that's partly what motivates the current GNU du behavior:
the idea is to implement this
11 matches
Mail list logo
