Heri, I assume the overriding of the filename happens after the client does the standard log4j configuration, so log.log is created anyway before you programmatically intervene. You could also programmatically delete log.log.
Suggestion: a (cleaner?) alternative for 'overriding the filename' is to use System Properties in the log4j configuration and set a different value for that System Proprty in each client. dirk > -----Original Message----- > From: Bender Heri [mailto:[EMAIL PROTECTED] > Sent: donderdag 7 april 2005 14:43 > To: [email protected] > Subject: File-Appender: Empty Ghost files > > > 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. > > I am using version 1.2.8 > > TIA > > Heri > > > --------------------------------------------------------------------- > 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]
