| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
removed
thanks to David Lang for his excellent performance analysis
|
|\
| |
| |
| |
| |
| |
| | |
Conflicts:
runtime/rsyslog.h
tools/syslogd.c
|
| |\
| | |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
runtime/datetime.h
runtime/rsyslog.h
|
| | |\
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Conflicts:
ChangeLog
syslogd.c
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
this caused a very minor issue with re-formatting a RFC3164 date when the
message was invalidly formatted and had a colon immediately after the date.
This was in the code for some years (even v1 had it) and I think it never
had any effect at all in practice. Though, it should be fixed - but definitely
nothing to worry about.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
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.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Queue full is now -2074 and -2025 is unique again.
(did cause no real problem
except for troubleshooting)
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
- added message property "inputname", which contains the name of the
input (module) that generated it. Presence is depending on suport in
each input module (else it is blank).
- added system property "$myhostname", which contains the name of the
local host as it knows itself.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Multiple immediately successive field delimiters are treated as
a single one.
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
| | | | |
|
| | | | |
|
|\| | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Conflicts:
ChangeLog
action.c
configure.ac
doc/manual.html
|
| |\| |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Conflicts:
ChangeLog
configure.ac
doc/manual.html
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
file parser.
Could lead to invalid sizes, constraints etc for e.g. queue files
and any other object whose size was specified
in base-10 entities. Did not apply to binary entities.
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
(until the previous time was reached again). There are still some
side-effects when time is rolled back (A time rollback is really a bad
thing to do, ideally the OS should issue pseudo time (like NetWare did)
when the user tries to roll back time).
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
| | | |
| | | |
| | | |
| | | |
| | | | |
The limit can now be set via $MaxMessageSize global config
directive (finally gotten rid of MAXLINE ;))
|
|\| | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Conflicts:
ChangeLog
|
| | | | |
|
| |\| |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Conflicts:
ChangeLog
configure.ac
doc/rsyslog_ng_comparison.html
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Thanks to lperr for an excellent bug report that helped detect this
problem.
|
| | | | |
|
| | | | |
|
| | | | |
|
|\| | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Conflicts:
plugins/imuxsock/imuxsock.c
|
| |\| |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Conflicts:
ChangeLog
configure.ac
doc/manual.html
plugins/imuxsock/imuxsock.c
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
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.
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This also lead to the addition of two new config directives:
$ActionExecOnlyEveryNthTime and $ActionExecOnlyEveryNthTimeTimeout
This feature is useful, for example, for alerting: it permits you to
send an alert only after at least n occurences of a specific message
have been seen by rsyslogd. This protectes against false positives
due to waiting for additional confirmation.
|
|\| | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Conflicts:
doc/rsyslog_conf.html
|
| |\| |
| | | |
| | | |
| | | |
| | | |
| | | | |
Conflicts:
omfwd.c
|
| | |\|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
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)
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
New syntax @[addr]:port introduced to enable that. Root problem was IPv6
addresses contain colons.
Also somewhat enhanced debugging messages.
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This is done by specifying $ActionMailTo multiple times. Note that this introduces a
small incompatibility to previous config file syntax: the recipient
list is now reset for each action (we honestly believe that will
not cause any problem - apologies if it does).
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
It permits to override the hostname being used on a local unix socket.
This is useful for differentiating "hosts" running in several jails.
Feature was suggested by David Darville, thanks for the suggestion.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
I disabled some make check checks for make distcheck. I need
to add some addtl support for make distcheck environment to
rsyslogd and I don't like to hold 3.21.1 just for that any
longer.
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
- bugfix: no error was reported if the target of a $IncludeConfig
could not be accessed.
- added testbed for common config errors
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
- enhanced config file checking - no active actions are detected
- added -N rsyslogd command line option for a config validation run
(which does not execute actual syslogd code and does not interfere
with a running instance)
- somewhat improved emergency configuration. It is now also selected
if the config contains no active actions
- rsyslogd error messages are now reported to stderr by default. can be
turned off by the new "$ErrorMessagesToStderr off" directive
Thanks to HKS for suggesting these new features.
|
|\| | | |
|