Return-Path: 
 <log4net-user-return-4407-apmail-logging-log4net-user-archive=logging.apache.org@logging.apache.org>
Delivered-To: apmail-logging-log4net-user-archive@www.apache.org
Received: (qmail 13695 invoked from network); 7 May 2008 15:04:34 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 7 May 2008 15:04:34 -0000
Received: (qmail 43736 invoked by uid 500); 7 May 2008 15:04:36 -0000
Delivered-To: apmail-logging-log4net-user-archive@logging.apache.org
Received: (qmail 43381 invoked by uid 500); 7 May 2008 15:04:35 -0000
Mailing-List: contact log4net-user-help@logging.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:log4net-user-help@logging.apache.org>
list-unsubscribe: <mailto:log4net-user-unsubscribe@logging.apache.org>
List-Post: <mailto:log4net-user@logging.apache.org>
Reply-To: "Log4NET User" <log4net-user@logging.apache.org>
List-Id: <log4net-user.logging.apache.org>
Delivered-To: mailing list log4net-user@logging.apache.org
Received: (qmail 43370 invoked by uid 99); 7 May 2008 15:04:35 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 07 May 2008 08:04:35 -0700
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
	tests=SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: local policy includes SPF record at
 spf.trusted-forwarder.org)
Received: from [206.190.52.46] (HELO smtp100.biz.mail.re2.yahoo.com)
 (206.190.52.46)
    by apache.org (qpsmtpd/0.29) with SMTP; Wed, 07 May 2008 15:03:49 +0000
Received: (qmail 41683 invoked from network); 7 May 2008 15:03:57 -0000
Received: from unknown (HELO echamberlain)
 (echamberlain@ventripoint.com@63.226.207.211 with login)
  by smtp100.biz.mail.re2.yahoo.com with SMTP; 7 May 2008 15:03:57 -0000
X-YMail-OSG: 
 wN69rpsVM1min8r4E6gPogiSK.vJeD6eUjjCzgV.dMlsvUpdnmzeyB2JxeBN4HsCTQNJPP0_GpFfkuxSr4IzTG.jYJNwXaRLzH054MxEFg--
X-Yahoo-Newman-Property: ymail-3
From: "Eric Chamberlain" <echamberlain@ventripoint.com>
To: "'Log4NET User'" <log4net-user@logging.apache.org>
References: <FFE6362EE00A4C4E83A98981EF88A364050EDC@zeus.roychastain.org>
Subject: RE: Using log4net.Util.PatternString in a PatternLayout
Date: Wed, 7 May 2008 08:03:55 -0700
Message-ID: <00f101c8b053$92d16630$6c00a8c0@ventripoint.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
Thread-Index: AchyT07d9bDHFi2ZTFuA6tlQz4XlXg+A8Ymw
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
In-Reply-To: <FFE6362EE00A4C4E83A98981EF88A364050EDC@zeus.roychastain.org>
X-Virus-Checked: Checked by ClamAV on apache.org

I have just recently had the task of archiving off some log4net-generated
files created by a rolling file appender and have found that they all have
the same creation date.   This appears to be a result of the method used to
roll the files.  Perhaps it's a feature?   In any case, it surprised me.
Fortunately, I could use the last-written timestamp for my purposes.

However, it would be nice to hear if anyone knows if there is a functional
reason why all rolling file appender logs have the creation date of the
first log file....

 
Eric Chamberlain
Software Engineer, VentriPoint, Inc.
 
-----Original Message-----
From: Roy Chastain [mailto:Roy@roychastain.org] 
Sent: Wednesday, May 07, 2008 5:35 AM
To: log4net-user@logging.apache.org
Subject: Using log4net.Util.PatternString in a PatternLayout

I have the following layout defined for a RollingFileAppender  (log4Net
1.2.10)

<layout type="log4net.Layout.PatternLayout">
  <param name="Header" type="log4net.Util.PatternString"
value="%newline**** Trace Opened     Local: %date{yyyy-MM-dd
HH:mm:ss.fff}     UTC: %utcdate{yyyy-MM-dd HH:mm:ss.fff} ****%newline"
/>
  <param name="Footer" type="log4net.Util.PatternString" value="****
Trace Closed %date{yyyy-MM-dd HH:mm:ss.fff} ****%newline" />
  <param name="ConversionPattern" value="%d{dd HH:mm:ss.fff} [%4t]
%P{instance}::%M - %m%n" />
</layout>

The idea is to place the current date and time in the header and footer
of each log file as it rolls over.  Instead each header and footer
receives the same date/time.  (The date/time is the date/time the
original file was opened.)

This action is certainly not what was expected, and I do not believe a
useful implementation.

Can someone say that the result is has expected and, if so, please give
some pointers on how to implement a 'current date/time' for the headers
and footers?

Thanks

------------------------------------------------------------------------
----------
Roy Chastain