Well, I am sure wiser Monks will tell you much better ways of doing this, but if you can name it, say, Backup_Data.pm, and make it look like the following:
package Backup_Data;
our %hash_of_att_db
= (
'0x40e00600' => {
'attack_type' => 'backdoor',
'attack_port' => '',
'attack_sig' => 'lib/attackprolib/fice-2000.dmp',
'attack_sig_v6' => 'lib/attackprolib/fice-2000.dmp',
},
'0x40e00500' => {
'attack_type' => 'backdoor',
'attack_port' => '',
'attack_sig' => 'lib/attackprolib/mpnewdump',
'attack_sig_v6' => 'lib/attackprolib/6_bionet.dump',
},
);
1;
(note the first line and the last) then, you could use the file as follows:
use strict;
use warnings;
use lib '/home/phemal'; # wherever Backup_Data.pm is
use Backup_Data;
use Data::Dumper;
print Dumper( \%Backup_Data::hash_of_att_db );
That is to say, our %foo; declared in Backup_Data.pm should now be available to you as %Backup_Data::foo inside your program, which now uses strict. Hope this helps. | [reply]
[d/l]
[select] |
Of course, if you're going to go that route, you could leave off the first and last lines (i.e., don't bother making it a package) and require the file. The required file does still have to be valid perl (such as an assignment statement) and I find it preferable to declare the variables which it sets in the main program rather than in the required file, but this basic technique generally works pretty well for reading in configuration data and the like, provided you can trust the file you're reading in.
| [reply]
[d/l]
[select] |