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.
-
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.
|