rsyslog.git/plugins, branch v4.5.5

added $InputTCPServerNotifyOnConnectionClose config directive

2009-10-01T16:39:21+00:00

Merge branch 'v4-stable' into v4-beta

2009-09-03T13:52:24+00:00

Conflicts:
	ChangeLog
	configure.ac
	doc/manual.html

bugfix: reverse lookup reduction logic in imudp do DNS queries too often

2009-09-03T13:48:57+00:00

A comparison was done between the current and the former source address.
However, this was done on the full sockaddr_storage structure and not
on the host address only. This has now been changed for IPv4 and IPv6.
The end result of this bug could be a higher UDP message loss rate than
necessary (note that UDP message loss can not totally be avoided due
to the UDP spec)

added $InputTCPMaxListeners directive

2009-08-17T15:18:19+00:00

permits to specify how many TCP servers shall be possible (default is 20).

bugfix: message could be truncated after TAG, often when forwarding

2009-07-09T14:32:14+00:00

This was a result of an internal processing error if maximum field
sizes had been specified in the property replacer.
Also did some testbench improvements, including omstdout.

added $klogConsoleLogLevel directive

2009-07-03T09:57:21+00:00

...which permits to set a new console log level while rsyslog is active

now put the new property-based methods to good use

2009-07-01T12:33:19+00:00

... hopefully reducing the number of allocs/frees as well as overall
memory usage in a busy system (plus that these shared properties hopefully
remain in cache longer than its single-instance counterparts...)

RcvFromIP now also a property

2009-07-01T11:28:17+00:00

This sets stage to enable use of the property-interface to speed
up things (mildly), the next step to be done. I have also fixed one
regression of yesterday's changes.

introduced a new way of handling the RcvFrom property

2009-06-30T16:45:41+00:00

... plus a fix for a long-time bug in obj-types.h. That lead to
the object pointer only then to become NULL when the object was
actually destructed, I discovered this issue during
introduction of the pRcvFrom property in msg_t, but it potentially had other
effects, too. I am not sure if some experienced instability resulted from this
bug OR if its fix will cause harm to so-far "correctly" running code. The later
may very well be. Thus I will change it only for the current branch and also
the beta, but not in all old builds. Let's see how things evolve.

finished transition to using inputName property

2009-06-30T13:21:15+00:00

... plus some celanup and adding minor missing functionality
(the rule debug info again tell the property name, not just number).