| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
This has now been corrected. Required change to the
internal ParseTIMESTAMP3164() interface.
|
|
|
|
|
|
| |
resulting in strange operations.
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
|
|
|
|
|
|
|
|
| |
default discard severity was incorrectly set to 4, which lead
to discard-on-queue-full to be enabled by default. That could cause
message loss where non was expected. The default has now been changed
to the correct value of 8, which disables the functionality. This
problem applied both to the main message queue and the action queues.
Thanks to Raoul Bhatia for pointing out this problem.
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- 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>
|
|
|
|
| |
... and some cleanup
|
|\
| |
| |
| |
| |
| |
| | |
Conflicts:
ChangeLog
plugins/imklog/imklog.c
|
| |
| |
| |
| | |
renamed to OS_BSD
|
| |
| |
| |
| |
| |
| | |
Those with a space in front of the timestamp - at least HP procurve is
known to do that and I won't outrule that others also do it. The
change looks quite unintrusive and so we added it to the parser.
|
| | |
|
|/
|
|
|
|
|
|
|
|
| |
GNU/Hurd does not define it (because it has no limit), and we have taken
care for cases where it is undefined now. However, some very few places
remain where IMHO it currently is not worth fixing the code. If it is
not defined, we have used a generous value of 1K, which is above IETF
RFC's on hostname length at all. The memory consumption is no issue, as
there are only a handful of this buffers allocated *per run* -- that's
also the main reason why we consider it not worth to be fixed any further.
|
|\
| |
| |
| |
| |
| | |
Conflicts:
syslogd.c
|
| |\ |
|
| | |
| | |
| | |
| | | |
varmojfekoj for the patch
|
| | |
| | |
| | |
| | |
| | | |
* reset errno before printing a warning message
* misspelled directive name in code processing legacy options
|
| | | |
|
|\| |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
ChangeLog
configure.ac
doc/rsyslog_ng_comparison.html
doc/status.html
msg.c
rsyslog.conf.5
rsyslog.h
rsyslogd.8
syslogd.c
Conflicts were due to patch being multiple times applied in CVS import.
|
| |\|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
ChangeLog
Makefile.am
configure.ac
doc/status.html
rsyslog.conf.5
syslogd.c
|
| | | |
|
| | |
| | |
| | |
| | | |
This was introduced by an invalid CVS patch.
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
effects on existing envrionments, as sysklogd didn't obey it either
(probably another bug in RFC3164...). We now receive the full size, but
will modify the outputs so that only 32 characters max are used by
default. If you need large tags in the output, you need to provide
custom templates.
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
effects on existing envrionments, as sysklogd didn't obey it either
(probably another bug in RFC3164...). We now receive the full size, but
will modify the outputs so that only 32 characters max are used by
default. If you need large tags in the output, you need to provide
custom templates.
|
| | | |
|
| |/
| |
| |
| | |
during startup)
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
processed before all other options. Inter-option dependencies have been
relieved. Among others, permits to specify intial module load path via
-M only (not the environment) which makes it much easier to work with
non-standard module library locations. Thanks to varmojfekoj for
suggesting this change. Matches bugzilla bug 55.
|
| |
| |
| |
| |
| |
| |
| |
| | |
effects on existing envrionments, as sysklogd didn't obey it either
(probably another bug in RFC3164...). We now receive the full size, but
will modify the outputs so that only 32 characters max are used by
default. If you need large tags in the output, you need to provide
custom templates.
|
| |
| |
| |
| | |
with queues - so things can be configured to be done at off-peak hours
|
| | |
|
|/
|
|
| |
during startup)
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
messages
- added new $ActionForwardDefaultTemplate directive
- added new $ActionGSSForwardDefaultTemplate directive
|
|
|
|
|
| |
- added a buid-in template for previous syslogd file format
- added new $ActionFileDefaultTemplate directive
|
|
|
|
|
|
|
|
|
|
|
| |
default
- implemented backward compatibility commandline option parsing
- bugfix: -t and -g legacy options max number of sessions had a wrong and
much too high value
- automatically generated compatibility config lines are now also logged so
that a user can diagnose problems with them
- added compatibility mode for -a, -o and -p options
- MILESTONE: compatibility mode processing finished
|
| |
|
|
|
|
| |
thanks to mclaughlin77@gmail.com for the patch
|
| |
|
|
|
|
| |
Results in reducing code complexity.
|
|
|
|
| |
prevent unintentional message loss
|
| |
|