comment on

...we're pretty much beyond what split can do...

Mh, we know the format:

use Data::Dump;
use feature qw(say);

my $line =qq(127.0.0.1 - - [22/Apr/2015:13:35:04 +1000] "GET /bin/admi
+n.pl HTTP/1.1" 401 509);
my @bits  = split /\s/, $line;

dd\@bits;

say qq(Host:    $bits[0]);
say qq(Logname: $bits[1]);
say qq(User:    $bits[2]);
say qq(Time:    $bits[3] $bits[4]);
say qq(Request: $bits[5] $bits[6] $bits[7]);
say qq(Status:  $bits[8]);
say qq(Size:    $bits[9]);

__END__

monks>apache.pl
[
  "127.0.0.1",
  "-",
  "-",
  "[22/Apr/2015:13:35:04",
  "+1000]",
  "\"GET",
  "/bin/admin.pl",
  "HTTP/1.1\"",
  401,
  509,
]
Host:    127.0.0.1
Logname: -
User:    -
Time:    [22/Apr/2015:13:35:04 +1000]
Request: "GET /bin/admin.pl HTTP/1.1"
Status:  401
Size:    509
[download]

Regards, Karl

ŤThe Crux of the Biscuit is the Apostropheť

In reply to Re^3: Question about the most efficient way to read Apache log files without All-In-One Modules from CPAN (personal learning exercise) by karlgoethebier
in thread Question about the most efficient way to read Apache log files without All-In-One Modules from CPAN (personal learning exercise) by lulz

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.


Problems? Is your data what you think it is?
	PerlMonks