From: Rainer Gerhards Date: Sat, 7 Mar 2015 11:04:43 +0000 (+0100) Subject: logger man page: update --size doc X-Git-Tag: v2.26.1~21 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=e0610aa83114c1521e52dd099d3180d14dcff34e;p=thirdparty%2Futil-linux.git logger man page: update --size doc now we have strict sizes Signed-off-by: Karel Zak --- 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