It seems to me you are looking for one of us to give you an answer when you haven't done enough research yourself. You've said you've looked around for scripts that do this, how about you look up some code that does something along these lines? Do some experimenting, trial and error, show us what code you've come up with. At the very least, show us you have made some real effort.

Get acquainted with google and learn how to use the right terms and combinations. Google Text Searching demonstrates some simple yet powerful ways of homing in on what you need. Google Suggest supplies the most common terms people have used previously, this helps greatly if you are unfamiliar with terms, have a little trouble remembering terms, etc. Google Code Search searches for code and Perlmonk's Super Search is every perl programmer's database of information. The key to getting by in any product, be it a programming language, software application, hardware device, etc, etc is to use the right manual, find out what books or manuals are autoritative, buy them, download them, etc and start by scanning the index for what you need.

Think about it for a second, if a file changes, just what exactly about the file changes?? How does your operating system know a file has changed? Quite obviously, more data is added to a file and therefore it's size has to change. This is a great thing to compare.

When a file changes, the OS must keep a record of when changes were made inorder to help you know how old a file is. Therefore, modification times must have changed. Another thing to compare incase the filesize hasn't.

I don't mean to come across as condascending with this lecture, but the best help you can get is the help you give yourself.


perl -e '$,=$",$_=(split/\W/,$^X)[y[eval]]]+--$_],print+just,another,split,hack'er

In reply to Re: Filesystem Scan by Firefly258
in thread Filesystem Scan by smist

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.