traverseda
/
cpython
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Merged documentation update from 3.6.

This commit is contained in:
Vinay Sajip 2016-12-31 11:07:35 +00:00
parent 089a062da4 53a21eb479
commit 8e9c42e8e8
1 changed files with 8 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
Doc/library/logging.handlers.rst
View File

@ -282,11 +282,12 @@ module, supports rotation of disk log files.
You can use the *maxBytes* and *backupCount* values to allow the file to
:dfn:`rollover` at a predetermined size. When the size is about to be exceeded,
the file is closed and a new file is silently opened for output. Rollover occurs
whenever the current log file is nearly *maxBytes* in length; if either of
*maxBytes* or *backupCount* is zero, rollover never occurs. If *backupCount*
is non-zero, the system will save old log files by appending the extensions
'.1', '.2' etc., to the filename. For example, with a *backupCount* of 5 and
a base file name of :file:`app.log`, you would get :file:`app.log`,
whenever the current log file is nearly *maxBytes* in length; but if either of
*maxBytes* or *backupCount* is zero, rollover never occurs, so you generally want
to set *backupCount* to at least 1, and have a non-zero *maxBytes*.
When *backupCount* is non-zero, the system will save old log files by appending
the extensions '.1', '.2' etc., to the filename. For example, with a *backupCount*
of 5 and a base file name of :file:`app.log`, you would get :file:`app.log`,
:file:`app.log.1`, :file:`app.log.2`, up to :file:`app.log.5`. The file being
written to is always :file:`app.log`. When this file is filled, it is closed
and renamed to :file:`app.log.1`, and if files :file:`app.log.1`,