Yes, I meant the default initialization. The most things initialized there are ok. I override only the filenames by taking the root file name and the extension from the default initialization and supplying it with app specific informations and a new path.
Heri > -----Original Message----- > From: Ceki G�lc� [mailto:[EMAIL PROTECTED] > Sent: Thursday, April 07, 2005 6:42 PM > To: Log4J Users List; [email protected] > Subject: Re: File-Appender: Empty Ghost files > > > At 02:42 PM 4/7/2005, Bender Heri wrote: > >Hi all > > > >I have a server application which can serve multiple > clients. The logging > >occurs in files separated by client. (BTW: This is accomplished by > >supplying a own RepositorySelector which uses certain values in MDC). > > > >Therefore the file name within the configurtion file > >(DailyRollingFileAppender) only denotes the (root-) file > name which is > >overridden in code while initializing the loggers. > > > >The problem is now, that the LogManager on it's own > initialization creates > >the file which is declared within the configuration file (<param > >name="file" value="log.log"/>). This file is never used > afterwards. I > >would like to avoid the creation of this file. > > What do you mean by LogManager has its own initialization? > You mean default > initialization? If the default initialization is not needed > than why do you > go through with it? > > >I am using version 1.2.8 > > > >TIA > > > >Heri > > -- > Ceki G�lc� > > The complete log4j manual: http://www.qos.ch/log4j/ > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
