There are many solutions. On Windows you could tag each bad file with an Additional Data Stream, that's just the main filename with :something tagged on the end.

Simpler, and more portable, have a directory (called badfiles?), which is otherwise empty, and just create an empty file within it named the same as the bad file. The test to see if the bad file is there is a simple -e.

To avoid using a binary file use the -B test, that is not 100% accurate but works most of the time. If the file is genuinely corrupt then you might want to chmod 000 so no one can use it.

In reply to Re: mark unreadable file so a loop does not read the file again by cdarke
in thread mark unreadable file so a loop does not read the file again by newPerlr

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.