And this is the version so far with Find replaced by a local subroutine to avoid the new dichotomy of non-core module versus protection errors - surprisingly, it's less code to write and will also perform quicker than using File::Find. The protection test means there are now functionally a total of four rules (counting the within time interval as a single rule).
#!/usr/bin/perl
use Time::Local;
use strict;
use vars qw ( @times );
use warnings;
my @trees = ( '/home/ftp/pub',
$ENV{ AC_SYSTEM },
$ENV{ AC_WORKDIR } );
local @times = ( timelocal(0,0,15,14,7,105), timelocal(0,0,18,16,7,105
+) );
for ( @trees ) { MyFind( $_ ); }
sub MyFind {
for my $file ( grep !/^\./, glob ( shift() . '/*' ) ) {
if ( -d $file ) {
( -x $file ) and MyFind( $file );
}
else {
my @stat = stat $file;
( $stat[9] > $times[0] ) and ( $stat[9] < $times[1] )
and print "$file\n";
}
}
}
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.