Ah. In none of my code do I pass the locking name around,
it usually is used to serialize specific programs.
All in all not significantly different from what merlyn
did for Highlander - allow only one invocation at a time of an expensive CGI script. Which with this module would be:
use CGI;
use Lock;
local $main::highlander = Get Lock(
lock_file => "highlander",
timeout_limit => 10;
);
unless ($main::highlander) {
my $host = $ENV{REMOTE_HOST};
$host = $ENV{REMOTE_ADDR} unless defined $host;
warn "$0 @ ".(localtime).": highlander abort for $host after 10 se
+conds\n";
print CGI::header(-status => 503,
-retry_after => 30,
-type => 'text/plain'),
"Our server is overloaded. Please try again i
+n a few minutes.\n";
exit 0;
}
# No further logic required for mod_perl!!!
But I will definitely make the fix now that you have shown me
that this really is a security hole and not merely a portability issue
as I had thought.
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.