You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@logging.apache.org by rg...@apache.org on 2019/06/16 21:32:56 UTC
[logging-log4j2] branch release-2.x updated: Clarify Default
Rollover Strategy
This is an automated email from the ASF dual-hosted git repository.
rgoers pushed a commit to branch release-2.x
in repository https://gitbox.apache.org/repos/asf/logging-log4j2.git
The following commit(s) were added to refs/heads/release-2.x by this push:
new 1e5ae05 Clarify Default Rollover Strategy
1e5ae05 is described below
commit 1e5ae05f6513ca7957e134f34f2832daa1dccf7b
Author: Ralph Goers <rg...@apache.org>
AuthorDate: Sun Jun 16 14:32:45 2019 -0700
Clarify Default Rollover Strategy
---
src/site/xdoc/manual/appenders.xml | 45 +++++++++++++++++++-------------------
1 file changed, 23 insertions(+), 22 deletions(-)
diff --git a/src/site/xdoc/manual/appenders.xml b/src/site/xdoc/manual/appenders.xml
index 6bc8280..dadebfb 100644
--- a/src/site/xdoc/manual/appenders.xml
+++ b/src/site/xdoc/manual/appenders.xml
@@ -3304,9 +3304,10 @@ public class JpaLogEntity extends AbstractLogEventWrapperEntity {
The pattern may also contain lookup references that can be resolved at runtime such as is shown in the example
below.
</p>
- <p>The default rollover strategy supports three variations for incrementing the counter. The first is
- the "fixed window" strategy. To illustrate how it works, suppose that the min attribute is set to 1,
- the max attribute is set to 3, the file name is "foo.log", and the file name pattern is "foo-%i.log".
+ <p>The default rollover strategy supports three variations for incrementing
+ the counter. To illustrate how it works, suppose that the min attribute
+ is set to 1, the max attribute is set to 3, the file name is "foo.log",
+ and the file name pattern is "foo-%i.log".
</p>
<table>
@@ -3332,28 +3333,28 @@ public class JpaLogEntity extends AbstractLogEventWrapperEntity {
<tr>
<td>2</td>
<td>foo.log</td>
- <td>foo-1.log, foo-2.log</td>
- <td>During the second rollover foo-1.log is renamed to foo-2.log and foo.log is renamed to
- foo-1.log. A new foo.log file is created and starts being written to.</td>
+ <td>foo-2.log, foo-1.log</td>
+ <td>During the second rollover foo.log is renamed to foo-2.log. A new foo.log file is created and
+ starts being written to.</td>
</tr>
<tr>
<td>3</td>
<td>foo.log</td>
- <td>foo-1.log, foo-2.log, foo-3.log</td>
- <td>During the third rollover foo-2.log is renamed to foo-3.log, foo-1.log is renamed to foo-2.log and
- foo.log is renamed to foo-1.log. A new foo.log file is created and starts being written to.</td>
+ <td>foo-3.log, foo-2.log, foo-1.log</td>
+ <td>During the third rollover foo.log is renamed to foo-3.log. A new foo.log file is created and
+ starts being written to.</td>
</tr>
<tr>
<td>4</td>
<td>foo.log</td>
- <td>foo-1.log, foo-2.log, foo-3.log</td>
- <td>In the fourth and subsequent rollovers, foo-3.log is deleted, foo-2.log is renamed to foo-3.log,
- foo-1.log is renamed to foo-2.log and foo.log is renamed to foo-1.log. A new foo.log file is
- created and starts being written to.</td>
+ <td>foo-3.log, foo-2.log, foo-1.log</td>
+ <td>In the fourth and subsequent rollovers, foo-1.log is deleted, foo-2.log is renamed to
+ foo-1.log, foo-3.log is renamed to foo-2.log and foo.log is renamed to
+ foo-3.log. A new foo.log file is created and starts being written to.</td>
</tr>
</table>
- <p>By way of contrast, when the fileIndex attribute is set to "max" but all the other settings
- are the same the following actions will be performed.
+ <p>By way of contrast, when the fileIndex attribute is set to "min" but all the other settings are the
+ same the "fixed window" strategy will be performed.
</p>
<table>
<tr>
@@ -3379,23 +3380,23 @@ public class JpaLogEntity extends AbstractLogEventWrapperEntity {
<td>2</td>
<td>foo.log</td>
<td>foo-1.log, foo-2.log</td>
- <td>During the second rollover foo.log is renamed to foo-2.log. A new foo.log file is created
- and starts being written to.</td>
+ <td>During the second rollover foo-1.log is renamed to foo-2.log and foo.log is renamed to
+ foo-1.log. A new foo.log file is created and starts being written to.</td>
</tr>
<tr>
<td>3</td>
<td>foo.log</td>
<td>foo-1.log, foo-2.log, foo-3.log</td>
- <td>During the third rollover foo.log is renamed to foo-3.log. A new foo.log file is created and
- starts being written to.</td>
+ <td>During the third rollover foo-2.log is renamed to foo-3.log, foo-1.log is renamed to foo-2.log and
+ foo.log is renamed to foo-1.log. A new foo.log file is created and starts being written to.</td>
</tr>
<tr>
<td>4</td>
<td>foo.log</td>
<td>foo-1.log, foo-2.log, foo-3.log</td>
- <td>In the fourth and subsequent rollovers, foo-1.log is deleted, foo-2.log is renamed to foo-1.log,
- foo-3.log is renamed to foo-2.log and foo.log is renamed to foo-3.log. A new foo.log file is
- created and starts being written to.</td>
+ <td>In the fourth and subsequent rollovers, foo-3.log is deleted, foo-2.log is renamed to
+ foo-3.log, foo-1.log is renamed to foo-2.log and foo.log is renamed to
+ foo-1.log. A new foo.log file is created and starts being written to.</td>
</tr>
</table>
<p>