For my use case, yes.
Just build configuration using 'global' templates with configuration
snippets and this just simplify the things.
One of the forward action as example:
root@syslog:/etc/rsyslog-global/host/lin/forwards# ls -la 11*
lrwxrwxrwx 1 root root 51 Sep 19 14:13
Is there any sense to not use brackets always?
On 19/09/2019 17:36, Peter Viskup via rsyslog wrote:
Want to be sure the following configurations are the same
if $hostname contains "text" then {
action(type="omfwd" .)
}
and without curly brackets
if $hostname contains "text" then
On Thu, 19 Sep 2019, Peter Viskup via rsyslog wrote:
Want to be sure the following configurations are the same
if $hostname contains "text" then {
action(type="omfwd" .)
}
and without curly brackets
if $hostname contains "text" then
action(type="omfwd" ..)
The first option with
Want to be sure the following configurations are the same
if $hostname contains "text" then {
action(type="omfwd" .)
}
and without curly brackets
if $hostname contains "text" then
action(type="omfwd" ..)
The first option with brackets has to be used in case of more actions
4 matches
Mail list logo
