On Sat, 8 Nov 2008, John Little wrote:
> Which reminds me, I couldn't get init_and_watch($conf_file, 'HUP') to
> work with threads, which is not surprising, given that perl threads
> and signals don't mix very well.
Can you provide code to reproduce the problem? I'd be happy to track it
down.
--
Mike
> Got it, ... , it'll roll out with the next release (1.20).
Thank you!
> By the way, have you tried using the 'syswrite' option of the file
> appender instead? It prevents overlapping messages as well and it's
> easier to use than the synchronizing appender:
>
>log4perl.appender.Logfil
On Sat, 8 Nov 2008, John Little wrote:
> I've tried using Log4perl in a multi-threaded server script and the
> synchronized appender fails consistently after logging exactly 32768
> lines, with (piped through cat -v): Thread 1 terminated abnormally:
> semop(1343496 [EMAIL PROTECTED]@[EMAIL PROTECT
Mike Schilli said:
> It would be great if you could provide test results / bug reports of
> running Log4perl with Perl threads, though.
>
> That being said, there are synchronization mechanisms for file
> appenders:
>
> http://log4perl.sourceforge.net/d/Log/Log4perl/FAQ.html#23804
I've tried usin
