This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Logback: the generic, reliable, fast and flexible logging framework.". The branch, master has been updated via 6a99e92ca4ee3d622090a99b236336ca8ffef3b4 (commit) from ccc56bc6e079569a0bef20a2e639a3333e717ac5 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- http://git.qos.ch/gitweb/?p=logback.git;a=commit;h=6a99e92ca4ee3d622090a99b2... http://github.com/ceki/logback/commit/6a99e92ca4ee3d622090a99b236336ca8ffef3... commit 6a99e92ca4ee3d622090a99b236336ca8ffef3b4 Author: Ceki Gulcu <ceki@qos.ch> Date: Sat May 5 18:58:51 2012 +0200 minor edits diff --git a/logback-site/src/site/pages/reasonsToSwitch.html b/logback-site/src/site/pages/reasonsToSwitch.html index e8db30b..38b073d 100644 --- a/logback-site/src/site/pages/reasonsToSwitch.html +++ b/logback-site/src/site/pages/reasonsToSwitch.html @@ -97,17 +97,46 @@ a separate thread for scanning. This technical subtlety ensures that logback plays well within application servers and more generally within the JEE environment.</p> + + <h3><a name="grace" href="#grace">Graceful recovery from I/O + failures</a></h3> + + <p>Logback's <code>FileAppender</code> and all its sub-classes, + including <code>RollingFileAppender</code>, can gracefully recover + from I/O failures. Thus, if a file server fails temporarily, you + no longer need to restart your application just to get logging + working again. As soon as the file server comes back up, the + relevant logback appender will transparently and quickly recover + from the previous error condition. + </p> + <h3><a name="maxHistory" href="#maxHistory">Automatic removal of + old log archives</a></h3> - <h3><a name="lilith" href="#lilith">Lilith</a></h3> + <p>By setting the <span class="option">maxHistory</span> property + of <a + href="manual/appenders.html#TimeBasedRollingPolicy">TimeBasedRollingPolicy</a> + or <a + href="manual/appenders.html#SizeAndTimeBasedFNATP">SizeAndTimeBasedFNATP</a>, + you can control the maximum number of archived files. If your + rolling policy calls for monthly rollover and you wish to keep one + year's worth of logs, simply set the <span + class="option">maxHistory</span> property to 12. Archived log + files older than 12 months will be automatically removed. + </p> - <p><a href="http://lilith.huxhorn.de/">Lilith</a> is a logging and - access event viewer for logback. It is comparable to log4j's - chainsaw, except that Lilith is designed to handle large amounts of - logging data without flinching.</p> - - <h3><a name="grace" href="#grace">Prudent mode and graceful - recovery</a></h3> + <h3><a name="compression" href="#compression">Automatic + compression of archived log files</a></h3> + + <p><a + href="manual/appenders.html#RollingFileAppender">RollingFileAppender</a> + can automatically compress archived log files during + rollover. Compression always occurs asynchronously so that even + for large log files, your application is not blocked for the + duration of the compression. + </p> + + <h3><a name="prudent" href="#prudent">Prudent mode</a></h3> <p>In <a href="manual/appenders.html#prudent">prudent mode</a>, multiple <code>FileAppender</code> instances running on multiple @@ -116,13 +145,13 @@ <code>RollingFileAppender</code>. </p> - <p>Logback's <code>FileAppender</code> and all its sub-classes, - including <code>RollingFileAppender</code>, can gracefully recover - from I/O failures. Thus, if a file server fails temporarily, you - no longer need to restart your application just to get logging - working again. - </p> + <h3><a name="lilith" href="#lilith">Lilith</a></h3> + <p><a href="http://lilith.huxhorn.de/">Lilith</a> is a logging and + access event viewer for logback. It is comparable to log4j's + chainsaw, except that Lilith is designed to handle large amounts of + logging data without flinching.</p> + <h3><a name="conditional" href="#conditional">Conditional processing of configuration files</a></h3> @@ -182,19 +211,7 @@ according to user sessions, so that the logs generated by each user go into distinct log files, one log file per user. </p> - - <h3><a name="compression" href="#compression">Automatic - compression of archived log files</a></h3> - - <p><a - href="manual/appenders.html#RollingFileAppender">RollingFileAppender</a> - can automatically compress archived log files during - rollover. Compression always occurs asynchronously so that even - for large log files, your application is not blocked for the - duration of the compression. - </p> - <h3><a name="packagingData" href="#packagingData">Stack traces with packaging data</a> </h3> @@ -235,23 +252,6 @@ java.lang.Exception: 99 is invalid their IDE</a>. </p> - - <h3><a name="maxHistory" href="#maxHistory">Automatic removal of - old log archives</a></h3> - - <p>By setting the <span class="option">maxHistory</span> property - of <a - href="manual/appenders.html#TimeBasedRollingPolicy">TimeBasedRollingPolicy</a> - or <a - href="manual/appenders.html#SizeAndTimeBasedFNATP">SizeAndTimeBasedFNATP</a>, - you can control the maximum number of archived files. If your - rolling policy calls for monthly rollover and you wish to keep one - year's worth of logs, simply set the <span - class="option">maxHistory</span> property to 12. Archived log - files older than 12 months will be automatically removed. - </p> - - <h3><a name="logbackAccess" href="#logbackAccess">Logback-access, i.e. HTTP-access logging with brains, is an integral part of logback</a></h3> ----------------------------------------------------------------------- Summary of changes: logback-site/src/site/pages/reasonsToSwitch.html | 86 +++++++++++----------- 1 files changed, 43 insertions(+), 43 deletions(-) hooks/post-receive -- Logback: the generic, reliable, fast and flexible logging framework.