| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
| |
- added $InputTCPServerAddtlFrameDelimiter config directive, which
enabeles to specify an additional, non-standard message delimiter
for processing plain tcp syslog. This is primarily a fix for the invalid
framing used in Juniper's NetScreen products. Credit to forum user
Arv for suggesting this solution.
- added $InputTCPServerInputName property, which enables a name to be
specified that will be available during message processing in the
inputname property. This is considered useful for logic that treats
messages differently depending on which input received them.
|
|
|
|
| |
Enables to use FQDNs in sender names where the legacy default
|
|
|
|
|
| |
(but could also leave it under some other circumstances...)
Thanks to David Lang and speedfox for reporting this issue.
|
|\
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
ChangeLog
configure.ac
doc/manual.html
plugins/imudp/imudp.c
|
| |\
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
ChangeLog
configure.ac
doc/manual.html
plugins/imudp/imudp.c
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
...tried to send a message to it. This behaviour is operator-configurable.
If enabled, a message was emitted each time. That way an attacker could
effectively fill the disk via this facility. The message is now
emitted only once in a minute (this currently is a hard-coded limit,
if someone comes up with a good reason to make it configurable, we
will probably do that).
|
|\| |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
ChangeLog
configure.ac
doc/manual.html
doc/rsyslog_conf.html
plugins/imudp/imudp.c
runtime/rsyslog.h
|
| |\|
| | |
| | |
| | |
| | | |
Conflicts:
runtime/rsyslog.h
|
| | | |
|
| | |
| | |
| | |
| | | |
...all senders were permitted instead
|
|\| |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
ChangeLog
|
| | | |
|
|\| | |
|
| |\| |
|
| | |\
| | | |
| | | |
| | | |
| | | |
| | | | |
Conflicts:
ChangeLog
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
to v3. Will release as v1.21.2, because some field experience is needed
before it becomes stable v2.
|
| | | | |
|
| | | | |
|
|\| | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Conflicts:
ChangeLog
configure.ac
|
| | | |
| | | |
| | | |
| | | |
| | | | |
plus solving a compile problem for im3195 (which is not used
in practice, thus this did not show up before...)
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This enables us to use more efficient calling conventions and
also helps us keep the on-disk structure of a msg object more
consistent in future releases.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
I tried to work too quick this morning. A side-effect of an
earlier change was that no UDP messages were parsed, which
lead to their loss, because no PRI was set in this case.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Message parsing is now done as part of main message queue worker
processing (was part of the input thread) This should also improve
performance, as potentially more work is done in parallel.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
cleaned up previous code and redid it in a way that makes
it much easier to extend it
also added a new macro DBGPRINTF which is a performance-optimzed
version of dbgprintf
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This enhances performance and, as some have pointed out, is
probably also more consistent with what users expect how
the various output-timestamp related function should work. This
commit needs some more testing.
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
...which enables to work with
less acurate timestamps in favor of performance. This enables querying
of the time only every n-th time if imudp is running in the tight
receive loop (aka receiving messsages at a high rate)
|
|\| | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Conflicts:
ChangeLog
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
...this improves performance and consistency and also fixes
a bug where subsecond time properties generated by imfile, imklog and
internal messages could be slightly inconsistent.
|
| | | | |
|
|/ / /
| | |
| | |
| | | |
removed code not actually needed in imupd
|
|\| | |
|
| |\ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Conflicts:
ChangeLog
configure.ac
doc/manual.html
|
| | | |
| | | |
| | | |
| | | |
| | | | |
It did not properly de-init a variable acting as a linked list head.
That resulted in trying to access freed memory blocks after the HUP.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
removed
thanks to David Lang for his excellent performance analysis
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
- 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.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
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
|
| | | |
| | | |
| | | |
| | | | |
...which fixed the imfile segfault issue.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
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.
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
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).
|