Hi,
Just a small remark about a similar case with glusterfs-client also providing its own fusermount command: $ ls -lt /usr/bin/fusermount-glusterfs -rwxr-xr-x 1 root root 34976 24 mai 10:48 /usr/bin/fusermount-glusterfs* (no setuid here) There is a closed upstream issue: https://github.com/gluster/glusterfs/issues/3145 that links to an interesting discussion: https://github.com/gluster/glusterfs/discussions/2212 Do you think that your issue could be shared with glusterfs-client to find a common approach/policy? (There is no issue at glusterfs-client yet.) Thanks, Patrice
