It depends on the directory and use, but y, not a common situation. Thanks
-----Original Message----- From: Pádraig Brady <pixelb...@gmail.com> On Behalf Of Pádraig Brady Sent: Monday, January 9, 2023 1:47 PM To: SCOTT FIELDS <scott.fie...@kyndryl.com>; coreutils@gnu.org Subject: [EXTERNAL] Re: Feature Request: 'du' command allow filter by user name On 09/01/2023 18:45, SCOTT FIELDS wrote: > -----Original Message----- >> From: Pádraig Brady <p...@draigbradin.com> >> Sent: Monday, January 9, 2023 12:39 PM >> To: SCOTT FIELDS <scott.fie...@kyndryl.com>; coreutils@gnu.org >> Subject: [EXTERNAL] Re: Feature Request: 'du' command allow filter by >> user name >> >> On 09/01/2023 16:12, SCOTT FIELDS wrote: >>> Though not incredibly difficult to script, it would be useful to have 'du' >>> allow a filter by 'user'. >>> >>> AKA, >>> >>> 'du -user <user> <path>' to show only the files and usage for the specified >>> user. >> >> du isn't special in its filtering requirements here, and we can pipe >> robustly from the standard file filter like: >> >> find -type f -user $USER -print0 | >> du --files0-from=- >> >> So I don't think this would be appropriate to add to du. > > The problem is that doesn't provide you a summary, since it gives you usage > for each file. > > And sorry, I didn't include that as a use case, including '-s' option. Fair enough. Though that use case is unusual. I.e. directories with multiple users. Even then, since the invocation is per user, you can use the `--total | tail -n1` option to get a single usage for the user, albeit not summarized per specified directory. cheers, Pádraig.
