Subject: | max_dives does not work correctly |
Hello, I assume max_dives should limit the depth of diving into
subdirectotry like 1/2/3/4/5/6/..deeper..
It this is your intention, It does not do like that.
Ive got a very flag but very large dir with ca 350000 folders and it
stops scanning it early.
I think the bug is the line
if (scalar keys %{ $this->{'traversed'} } >= $maxd) {
and around. Because it only counts the number of parent dirs found.
But if this is what it should do, why cant I disable maxdive? Or just
return what found so far. Maybe a limitation by time makes more sense.
best regards.