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 -s can then
>> output a larger usage by summing the first column than what you would
>> get by the default behavior, when encountering command line arguments
>> that are a duplicate with an inode already traversed earlier in the
>> command line.  --count-links isn't quite right, because you still want
>> to elide links within a single directory of the command-line argument.
>> 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 command line arguments
>> --count-links == --count-links=all -> count every file on every encounter
> 
> What would be the difference between the 'per-directory' variant and invoking 
> du multiple times, giving it one argument at a time?

Fewer forks.

-- 
Eric Blake   ebl...@redhat.com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to