Guys,
I was configuring James for log rotation, and ran into an odd problem.
Consider the following log configuration:
<file id="smtpserver-target">
<filename>${app.home}/logs/smtpserver</filename>
<format>[...]</format>
<append>true</append>
<rotation type="unique" pattern="-yyyy-MM-dd-hh-mm" suffix=".log">
<or>
<date>dd</date>
<size>10485760</size>
</or>
</rotation>
</file>
I generated the following:
30-Jan-2003 03:37:24 10,485,831 smtpserver-2003-01-30-02-38.log
30-Jan-2003 04:30:00 10,485,847 smtpserver-2003-01-30-03-37.log
30-Jan-2003 05:20:28 10,485,776 smtpserver-2003-01-30-04-30.log
30-Jan-2003 06:09:20 10,485,834 smtpserver-2003-01-30-05-20.log
...
30-Jan-2003 23:35:58 10,485,792 smtpserver-2003-01-30-10-54.log
30-Jan-2003 23:59:58 6,103,668 smtpserver-2003-01-30-11-35.log
---------------------
31-Jan-2003 00:01:00 221,267 smtpserver-2003-01-31-12-00.log
31-Jan-2003 00:02:00 232,622 smtpserver-2003-01-31-12-01.log
31-Jan-2003 00:03:00 214,865 smtpserver-2003-01-31-12-02.log
31-Jan-2003 00:04:00 218,152 smtpserver-2003-01-31-12-03.log
31-Jan-2003 00:05:00 220,814 smtpserver-2003-01-31-12-04.log
Notice how after midnight I start getting per minute logs. Bug or pilot
error? I will reset my test to use just <date> rotation, because I didn't
recall that problem prior to adding the size as well as the date.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
