1.2.12 Bug Fix Candidates

Since it has been brought up in relation to bug #9150, I would like to open this up to the log4j users. Please review bugs in the log4j bug database, and if there is a bug that you would like considered for fixing in the 1.2.12 release, then enter the phrase "1.2.12 candidate" in the bug comments.

Re: Creating the directory Automatically

If you are only interested in logging to a temporary directory, you could specify the log file as "${java.io.tmpdir}/test.log" which will place the log file in the temporary directory (likely /tmp on 'nix and \Documents and Settings\USERNAME\Temporary Files on Windows). On Jun 17, 2005, at

Re: Creating the directory Automatically

On Jun 17, 2005, at 4:31 PM, Mark Womack wrote: I think we should try to create the directory, not even define an option. If it fails (because it is not allowed), we could catch the exception, then write out an error message and one is no worse off then if we never tried in the first place.

RE: Creating the directory Automatically

+1 -Original Message- From: Mark Womack [mailto:[EMAIL PROTECTED] Sent: Fri 6/17/2005 2:31 PM To: 'Log4J Users List' Cc: Subject:RE: Creating the directory Automatically I think we should try to create the directory, not even define an option. If it fails (because it

RE: Creating the directory Automatically

I think we should try to create the directory, not even define an option. If it fails (because it is not allowed), we could catch the exception, then write out an error message and one is no worse off then if we never tried in the first place. This just seems basic to me. Jake had to write too mu

Re: Creating the directory Automatically

See http://issues.apache.org/bugzilla/show_bug.cgi?id=9150. There appear to be valid reasons why could be undesirable for an appender to create directories if they are not available. However, it may be desirable to provide an option that would allow you to specify that you want the appende

syslog linefeed problem

Hello, I am logging to syslog and am encountering the following effects when the message contains linefeeds: If the logging application runs on Windows, ^M appears in place of the linefeed (0x5e 0x4d). If it runs on Linux the linefeeds are stripped and replaced by blanks. This is the case

RE: configuring a LogFilePatternReceiver in Chainsaw v2

Thanks, now its working. I've got one more: -Original Message- From: Scott Deboy [mailto:[EMAIL PROTECTED] Sent: Thursday, June 16, 2005 9:31 PM To: Log4J Users List Subject: RE: configuring a LogFilePatternReceiver in Chainsaw v2 I'm not sure this is the problem, but you probably need

Re: Creating the directory Automatically

I also had to make a new appender to handle this. On 6/17/05, Lutz Michael <[EMAIL PROTECTED]> wrote: > > one approach is to sub-class the existing appender and write it yourself. > Not optimal ... but it can be done. > > -Original Message- > From: Taranbir I Singh [mailto:[EMAIL PROTECT

RE: Creating the directory Automatically

one approach is to sub-class the existing appender and write it yourself. Not optimal ... but it can be done. -Original Message- From: Taranbir I Singh [mailto:[EMAIL PROTECTED] Sent: Friday, June 17, 2005 3:25 AM To: Log4J Users List Subject: Creating the directory Automatically HI,

Creating the directory Automatically

HI, I have defined the log file as "c:\temp\test.log", if the directory c:\temp is not already existing then its giving me the error... is this possible to create the directory if it is not there automatically? Any Solutions?