Thank you all!
++'s around for all great answers!
BBQ : I agree with you, but switching is not an option. Got to deal with the tools you are given sometimes.
$code_or_die: Very informative! I will definitely check out the software.
Fastolfe: Perfect! I think that was exactly what I was looking for. I couldn't use $0 because the difference between 90% of the scripts is the script path (and thats about it) so i tweaked it abit to the following:
package LogScripts;
# use Time::HiRes qw{ time };
use File::Spec::Functions qw(rel2abs);
my $started;
my $path;
BEGIN {
open(F, ">>c:\\scripts.log");
$path = rel2abs($0);
$started = time();
print F localtime(time) . " $ENV{REMOTE_ADDR} - Starting $path\n";
}
END {
my $elapsed = time() - $started;
print F localtime(time) . " $ENV{REMOTE_ADDR} - Stopping $path ($el
+apsed seconds)";
close(F);
}
Once again,
thank you all:) I learned a good deal from everyone.
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.