Put your foreach loop into a sub (say it's called search_dir, then change your code to this:
chdir("/")||die "Error:$!\n";
opendir(ROOT_DIR,"/")|| die "Error:$!\n";
search_dir("/","/");
sub search_dir{
my ($dir,$fullpath) = @_;
foreach $dir_cont (sort readdir($dir)){
next if $dir_cont =~s/^\.\.?$/;
if (-f $dir_cont){
log_sbit($full_path . $dir_cont) if (-u $dir_cont || -g $dir_cont)
+;
}
elsif (-d $dir_cont && opendir(SUB_DIR,"$dir_cont"){
my $new_full_path = $full_path . $dir_cont;
search_dir($dir_cont,$new_full_path);
}
}
This code is untested. I just added the $full_path so you could keep track of the full path and I put it all into a sub. So far you have the right idea. You just need to put your logic in a routine you can call over and over again. Once you get it right, check out File::Find.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|