Return-Path: 
 <log4j-user-return-9792-qmlist-jakarta-archive-log4j-user=nagoya.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-log4j-user-archive@apache.org
Received: (qmail 58811 invoked from network); 28 May 2003 19:04:49 -0000
Received: from exchange.sun.com (192.18.33.10)
  by daedalus.apache.org with SMTP; 28 May 2003 19:04:49 -0000
Received: (qmail 21898 invoked by uid 97); 28 May 2003 19:07:05 -0000
Delivered-To: qmlist-jakarta-archive-log4j-user@nagoya.betaversion.org
Received: (qmail 21891 invoked from network); 28 May 2003 19:07:04 -0000
Received: from daedalus.apache.org (HELO apache.org) (208.185.179.12)
  by nagoya.betaversion.org with SMTP; 28 May 2003 19:07:04 -0000
Received: (qmail 53712 invoked by uid 500); 28 May 2003 19:03:17 -0000
Mailing-List: contact log4j-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:log4j-user-unsubscribe@jakarta.apache.org>
List-Subscribe: <mailto:log4j-user-subscribe@jakarta.apache.org>
List-Help: <mailto:log4j-user-help@jakarta.apache.org>
List-Post: <mailto:log4j-user@jakarta.apache.org>
List-Id: "Log4J Users List" <log4j-user.jakarta.apache.org>
Reply-To: "Log4J Users List" <log4j-user@jakarta.apache.org>
Delivered-To: mailing list log4j-user@jakarta.apache.org
Received: (qmail 53657 invoked from network); 28 May 2003 19:03:17 -0000
Received: from arrowmail2.arrowheadgrp.com (209.242.139.25)
  by daedalus.apache.org with SMTP; 28 May 2003 19:03:17 -0000
Received: by ArrowMail2 with Internet Mail Service (5.5.2653.9)
	id <J2QPGK3L>; Wed, 28 May 2003 12:01:54 -0700
Message-ID: <68DA2C0C613D0E43977EB85E055C8A6501C25C6A@ArrowMail2>
From: Charles Hudak <CHudak@arrowheadgrp.com>
To: "'log4j-user@jakarta.apache.org'" <log4j-user@jakarta.apache.org>,
	"'log4j-dev@jakarta.apache.org'" <log4j-dev@jakarta.apache.org>
Subject: FileAppender
Date: Wed, 28 May 2003 12:01:46 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.9)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

Greetings,

When setting up a file appender, the docs say that if the file doesn't
exist, it is created. This is true, with the following caveat: if one or
more of the directories do not exist, the file is not created. This causes
problems if I want to setup a new server to log to a log directory that
hasn't been created yet. It adds administrative complexity to require the
deployer to know that the directory needs to be created. The code should be
smart enough to do this.

Does anyone know if more recent releases of log4j have fixed this?

If not, can this enhancment be made (or should I make it myself)? All you
really need to do is a File.createDirs() in FileAppender.setFile(...).


Charles Hudak
Software Engineering Manager

Arrowhead General Insurance/YouZoom, Inc.
chudak@arrowheadgrp.com
858.320.6800x6344


---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: log4j-user-help@jakarta.apache.org