karl s. eiringer wrote:
i think this could be a bug - could because the man-page doesn't say much
about if excluding is done before including, but have a look at this
Thank you for your report. I tried to reproduce this with the current
5.2.1 by this method.
address@hidden:~$ mkdir /tmp/foo
address@hidden:~$ cd /tmp/foo
address@hidden:/tmp/foo$ mkdir a b c d
address@hidden:/tmp/foo$ for i in a b c d; do echo foo > $i/afile; done
address@hidden:/tmp/foo$ find . -print
.
./a
./a/afile
./b
./b/afile
./c
./c/afile
./d
./d/afile
address@hidden:/tmp/foo$ du -skc --exclude=b
12 .
12 total
address@hidden:/tmp/foo$ du -skc --exclude=b *
4 a
4 c
4 d
12 total
address@hidden:/tmp/foo$ du -skc --exclude=b* *
4 a
4 c
4 d
12 total
address@hidden:/tmp/foo$ du --version
du (coreutils) 5.2.1
Can you make a small case such as this that illustrates your problem?
That would really help us to narrow this down.
address@hidden:# du -ksc --exclude=original* *
[...]
6897356 original
address@hidden:# du --exclude=original
[...]
1615804 .
address@hidden:#
What version of du are you using?
du --version
Bob