Dale, thanks for the explanation.
For the record though, there are a number of cases where we can know
that there is no point searching the children of a directory. We
already have optimizations in place for some obvious ones (for example
-maxdepth) but I'd certainly welcome patches for addition
"PenguinWhispererThe ." writes:
> So while someone might think -not -iwholename excludes that directory that
> is looping it will still traverse it.
> Why is find still traversing if a directory is excluded?
> Is this for corner-cases? Can someone give an example of those?
>
> I understand there i
Good day to you all,
A user experienced something in find that makes me wonder why find is
behaving like this(maybe it's actually a "feature", something that in
corner-cases is useful).
It happens when excluding a directory with the ! parameter (-not).
So find -L /src/tree/ -not -iwholename *excl
