Re: [log4perl-devel] signal handling and log4perl

[Mike S. <m...@pe...>]

On Sat, 9 May 2009, Seth Daniel wrote:

> I was hoping for a solution that didn't burn two signals.  I'm already
> using the most obvious signals: HUP, USR1, USR2, KILL, QUIT, etc...
> so I'm not exactly overflowing with extra signals. :o)

I see ... in the next version of Log4perl (1.23), you'll be able to call

     Log::Log4perl::Config->watcher->force_next_check();

instead of using a signal:

     http://github.com/mschilli/log4perl/commit/6c8609f1ba064d3f781769cb9e1b45638f3daa75

(will probably go out soon).

-- Mike

Mike Schilli
m...@pe...