summaryrefslogtreecommitdiffstats
path: root/bash-completion/logger
Commit message (Collapse)AuthorAgeFilesLines
* logger: add --skip-empty-lines to prevent logging empty linesRainer Gerhards2015-03-101-1/+1
| | | | | | | | | | | Empty log messages are generally considered useless. This option enables to turn them off when processing files (including stdin). [kzak@redhat.com: - rename --skip-empty-lines to --skip-empty, - add the option to getopt_long(), - add the option to bash-completion] Signed-off-by: Karel Zak <kzak@redhat.com>
* logger: permit to send messages larger than 1024 charactersRainer Gerhards2015-03-101-1/+1
| | | | | | | | | | | | | | | | | | 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>
* docs: add logger protocol notes to manual pageSami Kerola2014-07-281-1/+1
| | | | | | | | Inform about rfc5424 support, how to control what it includes to submission, and that it is the new default when sending syslog messages to remote server without specifying protocol. Signed-off-by: Sami Kerola <kerolasa@iki.fi>
* logger: allow user to send structured journald messagesSami Kerola2014-03-041-2/+2
| | | | | | | | | | | | | This feature is hopefully mostly used to give MESSAGE_ID labels for messages coming from scripts, making search of messages easy. The logger(1) manual page update should give enough information how to use --journald option. [kzak@redhat.com: - add missing #ifdefs - use xalloc.h] Signed-off-by: Sami Kerola <kerolasa@iki.fi> Signed-off-by: Karel Zak <kzak@redhat.com>
* bash-completion: use '\n' as IFS when ask for filenamesKarel Zak2013-09-301-0/+1
| | | | | | | | | | | | The bash completion for more(1) treats the space-separated pieces of filenames as different files. $ touch foo\ bar $ more foo<TAB> bar foo Reported-by: Ángel González <ingenit@zoho.com> Signed-off-by: Karel Zak <kzak@redhat.com>
* bash-completion: Don't offer short options where corresponding long one exists.Ville Skyttä2013-04-081-1/+1
| | | | | | | | | Users who know the short options can just hit the short option instead of tab, and it's not likely that it would be helpful to present a list of single character options to users who don't know them, doing so just unnecessarily trashes the list of suggestions. Signed-off-by: Ville Skyttä <ville.skytta@iki.fi>
* bash-completion: Avoid some unnecessary subshells.Ville Skyttä2013-04-081-1/+1
| | | | Signed-off-by: Ville Skyttä <ville.skytta@iki.fi>
* bash-completion: Don't offer any more completions after help or version.Ville Skyttä2013-04-081-0/+3
| | | | Signed-off-by: Ville Skyttä <ville.skytta@iki.fi>
* bash-completion: rename shell-completion -> bash-completionKarel Zak2013-04-051-0/+43
Signed-off-by: Karel Zak <kzak@redhat.com>
generated by cgit v1.2.3-55-g7522 (git 2.39.0) at 2024-07-03 10:04:04 +0200