I would put a subroutine into @INC that simply logs all the filenames/module names that get loaded, likely into a text file named after $0 (the currently running program). I'd use a text file to avoid any hassle with the database, just for the case when it is unavailable.
If you can set up $ENV{PERL5OPT} for every user, you can install the hook for every user:
package LogLoadedModules;
use strict;
sub log_loaded_module {
my( $self, $file_to_load ) = @_;
write_to_log_file( $0, $file_to_load );
return; # we didn't find anything
}
# Automatically install the hook in @INC when this
# module is loaded
sub import {
unshift @INC, \&log_loaded_module;
}
1;
Then you can set up @INC for every user by having
export PERL5OPT=-MLogLoadedModules
Update: Fixed unshift line, as corrected by Perlbotics
-
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.
|