RE: Refresh time and Logger shutdown

Whoops, make that appenders, not loggers.  From Gulcu's book:

"... all appenders of any logger explicitly mentioned in the new
configuration will be closed and removed from the logger.  However, loggers
which are not mentioned in the new configuration remain untouched."

Lifetime management of loggers (the thrust of your question I think) is
probably handled by Log4cxx's reference counting scheme, right?

dg

 
-----Original Message-----
From: Grigsby, David [mailto:dgrigsby@xxxxxxxxxxxxx] 
Sent: Tuesday, June 13, 2006 12:14 PM
To: Log4CXX User
Subject: RE: Refresh time and Logger shutdown

For your 2), it is my understanding from Ceki's book that
configurator::configure is supposed to flush, close, and destroy any
existing loggers before creating any new ones specified in the configuration
file.



-----Original Message-----
From: Arunkumar [mailto:aviswanathan@xxxxxxxxxxxxx] 
Sent: Tuesday, June 13, 2006 7:06 AM
To: 'Log4CXX User'
Subject: RE: Refresh time and Logger shutdown

Hi guys, 

I had some questions which I had posted previously and I am posting them
again.

1) In the ConfigureAndWatch(...) function we specify the time interval that
the logger uses to refresh its configuration. Can I specify this interval in
the xml configuration file so that the refresh rate changes dynamically?

2) Lets say I create 20 named logger instances in different sections of the
code. Coming from a C++ mindset, if we create an object we have to clean up
after it. So how do I clean up the 20 named logger instances I created or
does log4cxx take care of the clean up operation. (The LogManager::shutdown
function virtually shuts everything down. For example sending data to the
console using std::cout stopped working after calling it).

Thanks
Arun