| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| |
| |
| | |
Conflicts:
configure.ac
doc/manual.html
|
| |
| |
| |
| |
| | |
This one did not surface yet and the issue was actually found due to
a problem in v4 - but better fix it here, too.
|
| | |
|
| | |
|
| |
| |
| |
| | |
quarter-hour logfile rotation
|
| |
| |
| |
| |
| | |
... one should at least compile before comitting - sorry, been so
eager to push that out.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
It looks like a race was introduced by not locking the message mutex
in msgDestruct(). In theory, I thought, the decrement should be atomic,
but the whole operation may be reordered. Also it has potential for task
switches. If so, that would lead to a too-early destruction and thus
a potential double free - exactly what we have seen from time to time.
So I think this fix addresses the issue.
I have also removed anything that looks like atomic operations are supported
in this version - they are not. This was very late added, found to be
non-portable and pulled from that release.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- 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
|
| |
| |
| |
| |
| |
| |
| | |
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.
|
| | |
|
| |
| |
| |
| | |
(only at non-intrusive places)
|
| |
| |
| |
| | |
properly
|
| | |
|
| |
| |
| |
| | |
quarter-hour logfile rotation
|
| |
| |
| |
| | |
source and its capablity to be delayed without bad side effects)
|
| |
| |
| |
| | |
scheme (like im* and om*)
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- changed the object/interface system to use a new way of calling, giving
up the numerical object ID. This was necessary as we needed more
extensibility for third-party modules (which don't play at all with the
previous fixed object ID). This is stage work for the object loader.
Please note that I needed to change the object (de)serializer, I can't
outrule that I have introduced bugs there.
|
| |
| |
| |
| | |
interface structure
|
| |
| |
| |
| | |
- included expression support in filter module (and it works ;))
|
| |
| |
| |
| | |
type
|
| |
| |
| |
| | |
rsyslog (now) and also much easier to type
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
- cleaned up the stringbuf Construct interface
- did some cleanup on stringbuf calls - we now have much better interfaces
and macros
|
| |
| |
| |
| |
| |
| | |
- addded $ActionQueueDequeueSlowdown config directive
- addded $MainMsgQueueDequeueSlowdown config directive
- bugfix: MsgDup() did not work with new base object data structure
|
| |
| |
| |
| |
| |
| | |
troubles with the framework, also it was somewhat ugly...)
- fixed a memory leak in object destruction (was recently introduced by
object naming, not present in any released version)
|
| |
| |
| |
| | |
know what else it will be good for)
|
| |
| |
| |
| |
| |
| | |
finally in a running state for regular (non disk-assisted) queues, with
a minor nit at shutdown. So I can finally commit the work again to
CVS...
|
| | |
|
| | |
|
| |
| |
| |
| | |
serverity needs to be specified numerically for the time being)
|
| |
| |
| |
| | |
to save source for the weekend)
|
| | |
|
| | |
|
| |
| |
| |
| | |
- changed objSerialize methods to work directly on the stream class
|
| |
| |
| |
| | |
itself)
|
| |
| |
| |
| |
| |
| |
| | |
work and the deserializer needs also to be expanded, but the queue at
least performs well now.
- fixed a race condition that could occur when input modules were
terminated
|
| |
| |
| |
| |
| | |
- defined a property class
- implemented deserializer (needs some more work)
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
activated. If active, locking is employed.
|