On Sat, May 09, 2009 at 04:51:47PM -0700, Mike Schilli wrote: > 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).
That's fantastic. Thank you Mike. -- seth /\ sethdaniel.org ------------------------------------------------------------------------------ The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com _______________________________________________ log4perl-devel mailing list log4perl-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/log4perl-devel
