diff options
author | Vinay Sajip <vinay_sajip@yahoo.co.uk> | 2015-01-23 21:19:53 (GMT) |
---|---|---|
committer | Vinay Sajip <vinay_sajip@yahoo.co.uk> | 2015-01-23 21:19:53 (GMT) |
commit | 06140f2e04eb23f88e2b9d13bd5388fe29addbaa (patch) | |
tree | 68ca5748bed8dd90640ae77839885aa4aaba0795 /Doc/library/logging.handlers.rst | |
parent | ecb5de3d5e50f72c5f12aa49d912fd60f5f4a6af (diff) | |
parent | ff37cfe9cc7cf0d02d27e7ce8511774c01f7dfe1 (diff) | |
download | cpython-06140f2e04eb23f88e2b9d13bd5388fe29addbaa.zip cpython-06140f2e04eb23f88e2b9d13bd5388fe29addbaa.tar.gz cpython-06140f2e04eb23f88e2b9d13bd5388fe29addbaa.tar.bz2 |
Closes #23305: Merged documentation fix from 3.4.
Diffstat (limited to 'Doc/library/logging.handlers.rst')
-rw-r--r-- | Doc/library/logging.handlers.rst | 19 |
1 files changed, 10 insertions, 9 deletions
diff --git a/Doc/library/logging.handlers.rst b/Doc/library/logging.handlers.rst index d313704..48c57cf 100644 --- a/Doc/library/logging.handlers.rst +++ b/Doc/library/logging.handlers.rst @@ -269,15 +269,16 @@ 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 *maxBytes* 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`, :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`, :file:`app.log.2`, etc. exist, then they are renamed to - :file:`app.log.2`, :file:`app.log.3` etc. respectively. + 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`, + :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`, + :file:`app.log.2`, etc. exist, then they are renamed to :file:`app.log.2`, + :file:`app.log.3` etc. respectively. .. method:: doRollover() |