Write a script to analyze the raw access logs. Or you could use something like this:
LINK:
<A HREF="/cgi-bin/download.cgi?file=0111111.exe">Norton Definitions</A
+>
download.cgi:
#!/usr/bin/perl -wT
use strict;
use CGI;
use Fcntl qw|:flock|;
my $q = new CGI;
my ($file) = $q->param('file') =~ /^(\w+\.\w+)$/;
open (FILE, "/path/to/logs/$file.txt") or die("Can't open file: $!");
flock (FILE, LOCK_EX) or die("Can't lock file: $!");
my $count = <FILE> + 1;
open (FILE, ">/path/to/logs/$file.txt") or die("Can't open file for wr
+iting: $!");
print FILE $count;
close (FILE);
print "Location: http://site.com/downloads/$file\n\n";
That's just example code. Obviously it wouldn't be great to use for production, but you get the idea.
Joshua
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! —
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.