diff options
author | Rainer Gerhards <rgerhards@adiscon.com> | 2015-03-07 12:04:43 +0100 |
---|---|---|
committer | Karel Zak <kzak@redhat.com> | 2015-03-10 11:19:33 +0100 |
commit | a43022fdd48c544278fb12a3e4e1df7e6293152a (patch) | |
tree | a56d743384c107b0aa090d9133a82499e9eb73b5 | |
parent | b9ef27f59bffbeaf5397538ea16065d4eb6364c8 (diff) | |
download | util-linux-playground-a43022fdd48c544278fb12a3e4e1df7e6293152a.tar.gz |
logger man page: update --size doc
now we have strict sizes
Signed-off-by: Karel Zak <kzak@redhat.com>
-rw-r--r-- | misc-utils/logger.1 | 11 |
1 files changed, 7 insertions, 4 deletions
diff --git a/misc-utils/logger.1 b/misc-utils/logger.1 index b73f46a9a1..164c5f49c1 100644 --- a/misc-utils/logger.1 +++ b/misc-utils/logger.1 @@ -97,10 +97,13 @@ Most receivers accept larger than 1KiB message over any type of syslog protocol. As such, the \fB\-\-size\fR option affects logger in all cases (not only when \fB\-\-rfc5424\fR was used). -Note: the message size limit is not totally strict. It limits only -the user data, the size of the syslog header is not considered. While -this can lead to some truncation at the receiver level, a consistent limit -based on the user data size is generally wanted. +Note: the message size limit limits the overall message size, including +the syslog header. Header sizes vary depending on options selected and hostname +length. As a rule of thumb, headers are usually not longer than 50 to 80 +characters. When selecting maximum message size, it is important to ensure +that the receiver supports the max size as well, otherwise messages may +become truncated. Again, as a rule of thumb two to four KiB message size +should generally be OK, whereas anything larger should be verified to work. .TP .BR \-n , " \-\-server " \fIserver |