bug#79096: du: -x doesn't detect sshfs file system

2025-07-25 Thread Stan Marsh
>On 2025-07-25 11:25, Stan Marsh wrote: >> It could be argued that -x should cause it to skip (i.e., not descend >> into) any directory which is a mountpoint >That goes too far; people regularly use commands like 'du -x /mountpoint' to >list >just that file system. Right. That's why I suggested

bug#79096: du: -x doesn't detect sshfs file system

2025-07-25 Thread Paul Eggert
On 2025-07-25 11:25, Stan Marsh wrote: it could be argued that -x should cause it to skip (i.e., not descend into) any directory which is a mountpoint That goes too far; people regularly use commands like 'du -x /mountpoint' to list just that file system. It sounds like we have a feature req

bug#79095: [PATCH] test: removed dead code for unrecognised binary operators

2025-07-25 Thread Paul Eggert
Thanks for checking that. I installed your patch into the master branch on savannah.gnu.org, and am marking this bug report as done. To help make this sort of auditing easier in the future, I installed the attached followup patch too.From 3c40470c5da5cdfdc3dd94d4d820df873898ad43 Mon Sep 17 00:0

bug#79096: du: -x doesn't detect sshfs file system

2025-07-25 Thread Stan Marsh
> When the glob is expanded, $HOME/sshfs_mount ends up being one of the args > to `du' so it seems not surprising that the directory is processed. Yeah, you're probably right, now that I think about it. With "du", I prefer using ~/* instead of just ~ because then you get totals for each (top-lev

bug#79096: du: -x doesn't detect sshfs file system

2025-07-25 Thread Collin Funk
Hi Stan, Haven't gotten a chance to read through the original report yet, but... Stan Marsh writes: > By the way, and just out of curiosity, what method does "du" use to figure > out if > something is a mountpoint (and thus to be skipped if -x was supplied on the > cmd line) ? We have a func

bug#79096: du: -x doesn't detect sshfs file system

2025-07-25 Thread Stan Marsh
> Thanks for reporting it. Can you use 'strace' to find out which system call is > hanging? That would help isolate whether the bug is in 'du' or is in the > kernel. It may have been imprecise of me to say it "hung" - in the sense of hanging on a single system call or operation. Rather, it stopp

bug#79096: du: -x doesn't detect sshfs file system

2025-07-25 Thread Grisha Levit
On Fri, Jul 25, 2025, 12:02 Stan Marsh wrote: > > I used the following command to check disk usage in ~: > > $ du -sxc ~/* > > Unfortunately, this hung when it hit the directory ~/sshfs_mount, which is > sshfs > mounted to my home dir on some other system. > When the glob is expanded, $HOME/ssh

bug#79096: du: -x doesn't detect sshfs file system

2025-07-25 Thread Paul Eggert
Thanks for reporting it. Can you use 'strace' to find out which system call is hanging? That would help isolate whether the bug is in 'du' or is in the kernel. At some point we might ask whether you can reproduce the bug with the latest stable Coreutils

bug#79096: du: -x doesn't detect sshfs file system

2025-07-25 Thread Stan Marsh
My du is: $ du --version du (GNU coreutils) 8.30 Copyright (C) 2018 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later . This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted

bug#79095: [PATCH] test: removed dead code for unrecognised binary operators

2025-07-25 Thread Harry Fellowes
Hello, This is my first patch contribution to GNU coreutils. It removes dead code related to unrecognized binary operators in test.c. The fallback error was unreachable because invalid binary operators are filtered earlier in the logic. I’ve attached the patch file to this email. Please let me k