The situation is more that File::Find contains far too much argumentation about interacting with Unix filesystems that maybe were true decades ago but certainly are not even true on Unix filesystems nowadays.

IMO, a better approach nowadays would be to always set $dont_use_nlink to a true value and only fall back to that optimization if the user can make certain that the nlink field is valid for this filesystem (which is quite hard to do reliably).

In your case, I would assume that while performance may be critical, correctness still beats performance. So I would compare the two.

In reply to Re: File::Find won't iterate through CIFS share withouth "dont_use_nlink" by Corion
in thread File::Find won't iterate through CIFS share withouth "dont_use_nlink" by reinaldo.gomes

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.