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 sign
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 b
On Sat, May 09, 2009 at 12:12:28AM -0700, Mike Schilli wrote:
> On Fri, 8 May 2009, Seth Daniel wrote:
>
>> The reason for this is that I have a number of existing programs that
>> use Log4perl for most logging, but some very specific logging does not
>> use Log4perl. I need to be able to use a si
On Fri, 8 May 2009, Seth Daniel wrote:
> The reason for this is that I have a number of existing programs that
> use Log4perl for most logging, but some very specific logging does not
> use Log4perl. I need to be able to use a single signal to tell both
> Log4perl and the other log code to check
Hello,
What I would like to do is prevent Log4perl from setting %SIG and I
would like to be the one to tell Log4perl when to reload the
configuration. I do not want to use time-based delays if at all
possible. So I want my code to do the signal handling and then notify
Log4perl to check its conf
