summaryrefslogtreecommitdiffstats
path: root/bash-completion
diff options
context:
space:
mode:
authorRainer Gerhards2015-03-06 15:50:34 +0100
committerKarel Zak2015-03-10 11:19:16 +0100
commitf68b8aa7f5dc1fdf403a2ef64b5dd86f3fdbee95 (patch)
tree2060ed192db4d75f2626281ee03dc2055a612ec8 /bash-completion
parentagetty: reload issue on --autologin --login-pause too (diff)
downloadkernel-qcow2-util-linux-f68b8aa7f5dc1fdf403a2ef64b5dd86f3fdbee95.tar.gz
kernel-qcow2-util-linux-f68b8aa7f5dc1fdf403a2ef64b5dd86f3fdbee95.tar.xz
kernel-qcow2-util-linux-f68b8aa7f5dc1fdf403a2ef64b5dd86f3fdbee95.zip
logger: permit to send messages larger than 1024 characters
This is an important capability that has been specified in RFC5424. However, messages larger than 1024 chars are being accepted for years now by at least rsyslog and syslog-ng. This patch adds the option --size to permit setting a new max size, with 1024 being the default. Note that the size limit is only approximative, as we do not take the header size in account (RFC talks about total message length). [[kzak@redhat.com: - add 'S' to getopt_long(), - rename --message-size to --size - add the option to bash-completion] Signed-off-by: Karel Zak <kzak@redhat.com>
Diffstat (limited to 'bash-completion')
-rw-r--r--bash-completion/logger2
1 files changed, 1 insertions, 1 deletions
diff --git a/bash-completion/logger b/bash-completion/logger
index 0a66af309..593a67824 100644
--- a/bash-completion/logger
+++ b/bash-completion/logger
@@ -37,7 +37,7 @@ _logger_module()
esac
case $cur in
-*)
- OPTS="--journald --udp --id --file --help --server --port --priority --rfc3164 --rfc5424 --stderr --tag --socket --version"
+ OPTS="--journald --udp --id --file --help --server --port --priority --rfc3164 --rfc5424 --stderr --tag --size --socket --version"
COMPREPLY=( $(compgen -W "${OPTS[*]}" -- $cur) )
return 0
;;