I ran the following code on a w2k system on Friday. It looks like it died on Saturday night about 1/3 way through. Why, I don't know, although the drive I'm running it against is massive. The system had a low virtual memory error when I came in this morning.
I'm writing out to a text file immediately, so I don't know how there was a virtual memory problem. Can anyone else see the issue?
Thanks.
# Finds the owners of files on the share, finds their size, and prints
+ them to globalowners.txt
# 7/27/01
# Prints [owner][file][file size (KB)][acess time code][last file acce
+ss][modify time code][last modified date]
# To effectively sort times, sort by the timecodes.
# Import the text file to excel for best results
use strict;
use Win32::Perms;
use File::Find;
my $dir1='//server/share';
open OUT, ">shareowners.txt";
print OUT "Owner\tFile\tSize(KB)\tAccessTimeCode\tLast Accessed\tModif
+yTimeCode\tLast Modified\n";
find ({wanted => \&wanted, no_chdir=>1}, $dir1);
close OUT;
sub wanted {
if (-f){
my $File = new Win32::Perms("$_")||die;
my $Own=$File->Owner();
my @stat=stat;
my $kbytes = $stat[7]/1024;
my $access = localtime($stat[8]);
my $modify = localtime($stat[9]);
print OUT "$Own\t$\$_\t$kbytes\t$stat[8]\t$access\t$stat[9]\t$
+modify\n";
}
}
-OzzyOsbourne
-
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.
|