Here is the way simplified code. File::Find won't open a directory over 260 characters (it looks like an O/S limitation - thanks, everyone). I've tried putting if length statements into Wanted, but by then it is too late. I've tried wrapping the find function in an eval, but then it's too early.

What I want it to do is if it hits a directory over 255 characters, do a next or something. I want it to stick its head in the sand, and clap its hands over its little PERL ears and ignore the error.

Any ideas?

use File::Find;

$dir1="//server01/x\$/users/userguy";
print "finding media files on $dir1\.\.\.\n";
find(\&wanted, $dir1);
sub wanted {
    if (!("$File::Find::dir"=~/}/)&&(/mp3$|avi$|exe$|mpg$|wav$|zip$/i)
+){
        print "$File::Find::dir/$_\n";
        }
    
}

[download]

In reply to Clarification on the problem by OzzyOsbourne
in thread Is there a depth limitation to File::find by OzzyOsbourne

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.