Is creating a regex, like the one discussed above, going to be the most efficient way?
It would be if you used Regexp::Assemble :) The code would look something like
use strict;
use Regexp::Assemble;
my $re = do {
open IN, shift || 'file_of_IPs_sought' or die $!;
my $guts = Regexp::Assemble->new->add(
map {
chomp;
quotemeta($_)
} <IN>
)->as_string;
close IN;
qr/\b$guts\b/
};
open LOGFILE, shift || 'logfile' or die $!;
/$re/ and print while <LOGFILE>;
close LOGFILE;
# update: if this is a pipe...
/$re/ and print while <>;
The expression will probably turn out to be about the same size as the list of IPs. The more they cluster, the smaller the pattern will be. And 500 patterns will barely have Regexp::Assemble breaking a sweat.
- another intruder with the mooring in the heart of the Perl
-
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.
|