> 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-level) directory instead of just one grand total. And you get output as
you go,
not just at the very end (after a long wait/delay).
Also, using ~/* skips things like ~/.gvfs - a directory which is often
problematic.
Nevertheless, it could be argued that -x should cause it to skip (i.e., not
descend
into) any directory which is a mountpoint (as verified/shown by the "mountpoint"
command). Maybe a distinction could be made between:
sshfs_mount
and
sshfs_mount/
I.e., some utilities (e.g., rsync) make that distinction - where the trailing /
tells
it to treat it as a destination rather than as a directory per se (*). I would
argue
that without the trailing /, it should not recurse it if it is a mountpoint and
-x was
supplied.
Anyway, the workaround using --exclude works fine, so I'm not too bothered by
this now.
(*) I was never very clear on this in rsync and it always drove me crazy - I'd
always
get it wrong and end up with an extra directory when I didn't want it or the
stuff
copied to the current directory when I did want the extra level of directory -
until I
finally figured out what the two syntaxes mean.
=================================================================================
Please do not send me replies to my posts on the list.
I always read the replies via the web archive, so CC'ing to me is unnecessary.
Note that they always end up in my Spam file anyway, so it is annoying to have
to
periodically clean that out.
