I've found another small problem with File::Find. If you are on a unix based platform, and you use File::Find on a non-unix partition eg dos, vfat (win9x), is9660 (cdrom) and AFS then File::Find doesn't work properly. You need to add 
$File::Find::dont_use_nlink=1

[download]
Into your program and it will work fine. As I understand it this lowers the efficiency of File::Find because it has to look into each directory to see if there are entries in it rather than just looking at the nlink field in the inode. Non unix filesystems (and AFS ;-) don't set this properly.

This note is based on my experience with File::Find under Linux. It is probably similar under other *nix based systems but since foreign partition mounting is an OS specific thing YMMV.

In reply to RE: File::Find by ncw
in thread File::Find by Corion

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.