diff options
author | Alex Bligh | 2015-07-15 20:01:48 +0200 |
---|---|---|
committer | Karel Zak | 2015-07-29 10:33:25 +0200 |
commit | b6b67955ef31ff4f26a05c2de8bf1679a20d64ba (patch) | |
tree | 4878e8bd86aefc21fda93ce45207f7e96eae1851 /misc-utils/logger.1 | |
parent | sfdisk: add --list-free (diff) | |
download | kernel-qcow2-util-linux-b6b67955ef31ff4f26a05c2de8bf1679a20d64ba.tar.gz kernel-qcow2-util-linux-b6b67955ef31ff4f26a05c2de8bf1679a20d64ba.tar.xz kernel-qcow2-util-linux-b6b67955ef31ff4f26a05c2de8bf1679a20d64ba.zip |
logger: Add support to logger for RFC6587 octet counting
This patch adds support to logger for RFC6587 octet counting.
RFC6587 provides support for two sorts of framing:
1. Octet counting (at RFC6587 s3.4.1)
In essence each frame is preceded by a decimal length and a
space.
2. Non-transparent framing (at RFC6587 s3.4.2), also called
'octet stuffing'
In essence each frame is terminated by a `\n`
Prior to this patch, logger used option 2 (non-transparent framing)
on TCP, and used no framing on UDP. After this patch, the default
behaviour is unchanged, but if the '--octet-count' option is supplied,
option 1 is used for both TCP and UDP. Arguably octet count framing
makes little sense on UDP, but some servers provide it and this
allows testing of those servers.
Signed-off-by: Alex Bligh <alex@alex.org.uk>
Diffstat (limited to 'misc-utils/logger.1')
-rw-r--r-- | misc-utils/logger.1 | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/misc-utils/logger.1 b/misc-utils/logger.1 index bb81295a1..36c923d52 100644 --- a/misc-utils/logger.1 +++ b/misc-utils/logger.1 @@ -179,6 +179,11 @@ The RFC 5424 protocol has been the default for .B logger since version 2.26. .TP +.B \-\-octet\-count +Use the RFC 6587 octet counting framing method for sending messages. When +this option is not used, the default is no framing on UDP, and RFC6587 +non-transparent-framing (also known as octet stuffing) on TCP. +.TP .BR \-s , " \-\-stderr" Output the message to standard error as well as to the system log. .TP |