Beefy Boxes and Bandwidth Generously Provided by pair Networks
Clear questions and runnable code
get the best and fastest answer

Re: File::Find seems grossly inefficient for performing simple file tasks

by RichardK (Parson)
on Apr 26, 2013 at 12:11 UTC ( #1030810=note: print w/replies, xml ) Need Help??

in reply to File::Find seems grossly inefficient for performing simple file tasks

Did you mean programmer efficiency?

File::Find::Rule has a nicer interface and is easier to use (IMHO).

So your query could look something like this :-

use File::Find::Rule; my $uid = getpwnam('web'); my @files = File::Find::Rule->file->name('*.iso')->uid($uid)->in('/'); unlink $_ for @files;

There are methods for the stat tests, ctime,size etc, so you can add more stages as you need them. I'm not sure what 'find -cmin' actually does so I didn't attempt that bit.

  • Comment on Re: File::Find seems grossly inefficient for performing simple file tasks
  • Download Code

Replies are listed 'Best First'.
Re^2: File::Find seems grossly inefficient for performing simple file tasks
by taint (Chaplain) on Apr 26, 2013 at 14:09 UTC
    Greetings RichardK, and thank you for your reply.
    Yes. This is exactly the sort of return I had anticipated (as you provided).
    With the exceprion of:
    which should have read:
    as ./iso/ was a reference I used to a directory.
    As to find(1); -cmin refers to:
    -cmin n True if the difference between the time of last change of file status information and the time find was started, rounded up to the next full minute, is n minutes.
    referring to *BSD UNIX' version of FIND(1).

    Which is actually the most important part of my reason for trying this;
    I need to clobber (perldoc -f unlink) symlinks (perldoc -f symlink) older than 11 minutes. Unfortunately, Perls find2perl only provides:

    -atime N True if last-access time of file matches N (measured in days) (see bel +ow). -ctime N True if last-changed time of file's inode matches N (measured in days, + see below). -mtime N True if last-modified time of file matches N (measured in days, see be +low). -newer FILE True if last-modified time of file matches N. # # # See below: # # # 1. * N is prefixed with a +: match values greater than N 2. * N is prefixed with a -: match values less than N 3. * N is not prefixed with either + or -: match only values equal t +o N
    NOTE: (measured in days, see below), which is different than the find the system provides.
    As the system' find provides minutes. While I'm sure it must be possible to feed the string some math to make it more granular, I'm not clever enough to figure out how. :(

    Thank you again, for taking the time to respond.


    #!/usr/bin/perl -Tw
    use perl::always;
    my $perl_version = "5.12.4";
    print $perl_version;

      I read that find man page too and I'm still not sure exactly what it does!

      But, I'd interpret that to mean -cmin 7 is changed exactly 7 minutes ago ( which seems a bit odd ).

      Anyway, back to the point :), if you look at stat you'll see that atime,mtime,ctime are in seconds since the epoch and the pod for File::Find::Rule says :-

      stat tests The following "stat" based methods are provided: "dev", "in +o", "mode", "nlink", "uid","gid", "rdev", "size", "atime", "mtime", "ctime", "blksize", and "blocks". See "stat" in perlfunc for details. Each of these can take a number of targets, which will foll +ow Number::Compare semantics. $rule->size( 7 ); # exactly 7 $rule->size( ">7Ki" ); # larger than 7 * 1024 * 1024 by +tes $rule->size( ">=7" ) ->size( "<=90" ); # between 7 and 90, inclusive $rule->size( 7, 9, 42 ); # 7, 9 or 42

      So, you can write a mtime rule to do whatever you need.

      I'm guessing mtime but these things are a specific to your OS and file system so you'll have to play around a bit to see what works for you.

        Greetings RichardK, and thanks for taking the time to respond!
        Yes. I know what you mean. The 7 bit wasn't crystal clear to me, either. :P
        I'm guessing (as my OS is concerned) ctime -- Creation-time, will probably be my best choice of targets. As I'm looking for any symlink with a creation-time more than 11 minutes ago. I suppose I could create something that grabs, and holds "current time", and break out the "minutes" portion, then capture the ctime of those files searched for -- also breaking out the minutes portion; comparing >=11 minutes && rm, or something.
        I don't know. Guess I've got some more reading to do.

        Thanks again for your reply!


        #!/usr/bin/perl -Tw
        use perl::always;
        my $perl_version = "5.12.4";
        print $perl_version;

        a bit late but perhaps useful to someone.

        Implicit in the description of the -cmin flag is the *nix find's default "-" and "+" syntax.

        So, you are right that -cmin 7 means files that changed exactly 7 minutes ago. If you want "more than 7 minutes ago" use --cmin +7; "less than 7 minutes ago" use --cmin -7.

        if you want "less than or equal to 7 minutes ago", use --cmin -8.

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://1030810]
choroba tries to solve Pascal's triangle at
[choroba]: so far so good, 51 :-)
[LanX]: do you know the story of the triangle player?

How do I use this? | Other CB clients
Other Users?
Others browsing the Monastery: (6)
As of 2017-10-21 19:28 GMT
Find Nodes?
    Voting Booth?
    My fridge is mostly full of:

    Results (270 votes). Check out past polls.