diff options
| author | Serhiy Storchaka <storchaka@gmail.com> | 2016-03-18 14:37:53 +0200 |
|---|---|---|
| committer | Serhiy Storchaka <storchaka@gmail.com> | 2016-03-18 14:37:53 +0200 |
| commit | ee6471ec9068c40daf252af368e5c8ffd8c65472 (patch) | |
| tree | e9c0283918cd72b845fde90db8165e17ef5052ff | |
| parent | b3fe1c488f885bfde734bd352ac15acb8324dc67 (diff) | |
| parent | 774006232a0923d43c30cf233c5dee210bbb3bcf (diff) | |
| download | cpython-git-ee6471ec9068c40daf252af368e5c8ffd8c65472.tar.gz | |
Fixed a typo.
| -rw-r--r-- | Doc/library/logging.handlers.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Doc/library/logging.handlers.rst b/Doc/library/logging.handlers.rst index 446a070a9d..90efc45d35 100644 --- a/Doc/library/logging.handlers.rst +++ b/Doc/library/logging.handlers.rst @@ -552,7 +552,7 @@ supports sending logging messages to a remote or local Unix syslog. (See: :issue:`12168`.) In earlier versions, the message sent to the syslog daemons was always terminated with a NUL byte, because early versions of these daemons expected a NUL terminated message - even - though it's not in the relevant specification (RF 5424). More recent + though it's not in the relevant specification (RFC 5424). More recent versions of these daemons don't expect the NUL byte but strip it off if it's there, and even more recent daemons (which adhere more closely to RFC 5424) pass the NUL byte on as part of the message. |