| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
| |
Thanks to lperr for an excellent bug report that helped detect this
problem.
|
|
|
|
|
|
| |
It could cause system hangs under some circumstances.
The devel (3.21.3 and above) will re-enable it and provide
enhanced configurability to overcome the problems if they occur.
|
|
|
|
|
|
| |
Port can be set via new $ActionOmmysqlServerPort config directive
Note: this was a very minor change and thus deemed appropriate to be
done in the stable release.
|
|
|
|
|
|
|
|
| |
Previously was $MainMsgQueueWorkeTimeoutrThreadShutdown, is now
$MainMsgQueueWorkerTimeoutThreadShutdown. Note that the misspelled
directive is not preserved - if the misspelled directive was used
(which I consider highly unlikely), the config file must be changed.
Thanks to lperr for reporting the bug.
|
| |
|
|\
| |
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
ChangeLog
doc/manual.html
doc/rsyslog_conf.html
omfwd.c
|
| |
| |
| |
| |
| | |
New syntax @[addr]:port introduced to enable that. Root problem was IPv6
addresses contain colons. (backport from 3.21.3)
|
| |
| |
| |
| | |
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
| |
| |
| |
| |
| |
| |
| |
| | |
Update the documentation to use the new, preferred $ModLoad syntax:
- no more MySQL
- name of the in/output plugin without the trailing .so
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
- Update the version number and date in the man pages
- s/imklogd/imklog/
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- added a new property replacer option "sp-if-no-1st-sp" to cover
a problem with RFC 3164 based interpreation of tag separation. While
it is a generic approach, it fixes a format problem introduced in
3.18.0, where kernel messages no longer had a space after the tag.
This is done by a modifcation of the default templates.
Please note that this may affect some messages where there intentionally
is no space between the tag and the first character of the message
content. If so, this needs to be worked around via a specific
template. However, we consider this scenario to be quite remote and,
even if it exists, it is not expected that it will actually cause
problems with log parsers (instead, we assume the new default template
behaviour may fix previous problems with log parsers due to the
missing space).
- doc bugfix: property replacer options secpath-replace and
secpath-drop were not documented
|
| | |
|
| |
| |
| |
| | |
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
| |
| |
| |
| | |
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
| |
| |
| |
| | |
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
| |
| |
| |
| |
| |
| |
| | |
the markmessageinterval was not correctly propagated to all places
where it was needed. This resulted in rsyslog using the default
(20 minutes) in some code pathes, what looked to the user like mark
messages were never written.
|
| |
| |
| |
| | |
thanks to Ryo Fujita for pointing out the corrections.
|
| |
| |
| |
| |
| |
| |
| | |
because the LOG_MAKEPRI() C macro has a different meaning there (it
is just a simple addition of faciltity and severity). I have changed
this to use own, consistent, code for PRI calculation. [Backport from
3.19.10]
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
rsyslogd segfaults on freeeBSD 7.0 (an potentially other platforms)
if an action queue is running in any other mode than non-direct. The
same problem can potentially be triggered by some main message queue
settings. In any case, it will manifest during rsylog's startup. It is
unlikely to happen after a successful startup (the only window of
exposure may be a relatively seldom executed action running in queued
mode). This has been corrected. Thank to HKS for point out the problem.
|
| | |
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
ChangeLog
configure.ac
doc/manual.html
|
| | |
| | |
| | |
| | | |
Thanks to Michael Biebl for the information.
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
bugfix for mem leak in disk-based queue modes (backport from devel)
plus an update to the list of distributions where rsyslog packages are
available.
|
| | |
| | |
| | |
| | | |
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
| | |
| | |
| | |
| | | |
this is a backport from 3.19.10
|
| | | |
|
| | |
| | |
| | |
| | | |
These seem to have been lost in some early git days ;)
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
via queued mode (and plain tcp protocol)
|
|\| |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
ChangeLog
configure.ac
doc/manual.html
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
For some actions (e.g. forwarding(, this could also lead
to invalid configuration.
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
a kernel log message
This is an unusual case under Linux, and a frequent one under BSD
|
|\| | |
|
| |\|
| | |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
ChangeLog
configure.ac
|