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;
[download]

Then you can set up @INC for every user by having

export PERL5OPT=-MLogLoadedModules
[download]

Update: Fixed unshift line, as corrected by Perlbotics

---

---

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! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

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:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.