Having a quick peek at
the source for
Log::Log4perl::Appender::File it would appear that it will not be thread-safe due to its lack of file locking. But if you're using the
Log::Log4perl::Appender::DBI layer you should be fine as
DBI is thread-safe (in theory, at least).
As for a solution, I'd say just override the specific logging methods e.g
sub Log::Log4perl::Appender::File::log {
my($self, %params) = @_;
my $fh = $self->{fh};
flock( $fh => LOCK_EX );
print $fh $params{message};
flock( $fh => LOCK_UN );
if ($self->{autoflush}) {
my $oldfh = select $self->{fh};
$| = 1;
select $oldfh;
}
}
Or perhaps create just a wrapper function/method that does the
flocking before and after the call to the logging function.
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.