| Commit message (Collapse) | Author | Age | Files | Lines |
|\ |
|
| | |
|
| |
| |
| |
| |
| | |
The problem occured when using the -f (dynafiles) option,
and caused some tests to fail.
|
|\|
| |
| |
| |
| | |
Conflicts:
plugins/imrelp/imrelp.c
|
| | |
|
| |
| |
| |
| |
| |
| | |
Thanks to Andreas Stieger from Novell/SUSE for alerting us.
This function was introduced as part of the new config system,
but never was actually used (aka "not needed").
|
| |
| |
| |
| |
| |
| |
| |
| | |
The method introduced by the previous commit caused issues in v7 as it
was too generic. Most importantly, it permitted simple words (like "stop")
to (invalidly) be detected as pri filters. Now, the grammar is close
to the initial one, and each pri filter must at least have a comma or
a period inside it, which does not conflict with simple words.
|
| |
| |
| |
| |
| |
| | |
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=358
This happend to filters of the style "local0,local1.*", where the
multiple facilities were comma-separated.
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
modified: runtime/rsconf.c
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
This most importantly could happen due to configuration errors.
|
|\| |
|
| | |
|
| |
| |
| |
| |
| |
| | |
This could lead to various problems, like if-filters not working.
Note this is a regression from yesterdays escape fix, so there exist
no released version with this problem.
|
| | |
|
| | |
|
| | |
|
|\|
| |
| |
| |
| | |
Conflicts:
runtime/rule.c
|
| |
| |
| |
| |
| |
| | |
...if action chaining (& operator) was used
http://bugzilla.adiscon.com/show_bug.cgi?id=355
Thanks to pilou@gmx.com for the bug report
|
| |
| |
| |
| |
| |
| |
| | |
Only \' was supported. Now the usual set is supported. Note that v5
used \x as escape where x was any character (e.g. "\n" meant "n" and NOT
LF). This also means there is some incompatibility to v5 for well-know
sequences. Better break it now than later.
|
| | |
|
|\|
| |
| |
| |
| | |
Conflicts:
ChangeLog
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
SCM_CREDENTIALS is not a socket option; its value is usually
0x2 which on most archs corresponds to socket option
SO_REUSEADDR, but on mips-arch there is no socket option
with value 0x2 and SO_REUSEADDR = 0x4, so the call will fail
with ENOPROTOOPT 'Protocol not available'; skip it.
There does not seem any other special setsockopt call is
needed anyway, besides the above.
In addition Jonny Törnbom commented:
SCM_CREDENTIALS is a control message type, not a socket option, so using
setsockopt(...SCM_CREDENTIALS...) is potentially dangerous and wrong and
should be deleted from the code. (SCM_CREDENTIALS is used in conjuction
with SO_PASSCRED which is the socket option to use.)
|
|\| |
|
| | |
|
| | |
|
| |
| |
| |
| | |
Interface needed to be changed in lower stream classes. Syslog TCP Sending is now resumed properly.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
During config file processing, Omusrmsg often incorrectly returned a
warning status, even when no warning was present (caused by
uninitialized variable). Also, the core handled warning messages
incorrectly, and treated them as errors. As a result, omusrmsg
(most often) could not properly be loaded. Note that this only
occurs with legacy config action syntax. This was a regression
caused by an incorrect merge in to the 6.3.x codebase.
Thanks to Stefano Mason for alerting us of this bug.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
%$!all-json% will return a {}-wrapped object if there are are any
events, or when there is an attached (empty) pMsg->event, but an empty
string if nothing is attached. Let it return an empty object "{}" in
that case for consistency. In particular, this allows
$template MongoTemplate,"{%hostname:::jsonf:sys%, %$!all-json:2:$:%"
to always result in a valid JSON.
Signed-off-by: Miloslav Trmač <mitr@redhat.com>
|
| |
| |
| |
| |
| |
| |
| | |
JSON fields are "name":value, not "name"=value. Therefore change the
jsonf flag to use a colon.
Signed-off-by: Miloslav Trmač <mitr@redhat.com>
|
| |
| |
| |
| |
| |
| | |
It does nothing, at is just confusing.
Signed-off-by: Miloslav Trmač <mitr@redhat.com>
|
| |
| |
| |
| | |
Signed-off-by: Miloslav Trmač <mitr@redhat.com>
|
| | |
|
|\|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
ChangeLog
action.c
configure.ac
doc/manual.html
runtime/ruleset.c
template.h
threads.c
tools/syslogd.c
|
| |\
| | |
| | |
| | |
| | | |
Conflicts:
template.c
|
| | |
| | |
| | |
| | |
| | | |
see template.c file header for details
Note that this functionality was almost never used in practice
|
| | | |
|
| |\|
| | |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
ChangeLog
configure.ac
doc/manual.html
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
Thanks to Andre Lorbach for mentioning this.
|
| |\|
| | |
| | |
| | |
| | | |
Conflicts:
runtime/ruleset.c
|
| | |
| | |
| | |
| | |
| | |
| | | |
This lead to queue file corruption. While the root cause is a config
error, it is a bug that this important and hard to find config error
was not detected by rsyslog.
|