bugfix: zero-length strings were not supported in object
deserializer
properties are now case-insensitive everywhere (script, filters,
templates)
added the capability to specify a processing (actually dequeue)
timeframe with queues - so things can be configured to be done
at off-peak hours
We have removed the 32 character size limit (from RFC3164) on the
tag. This had bad 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.
changed command line processing. -v, -M, -c options are now parsed
and 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.
bugfix: some messages were emited without hostname
Plus a number of bugfixes that were applied to v3-stable and beta
branches (not mentioned here in detail).
Posted by
rgerhards
on
Tuesday, April 08, 2008
299
An interim version was accidentally released to the web. It was named 3.14.0.
To avoid confusion, we have not assigned this version number to any
official release. If you happen to use 3.14.0, please update to 3.14.1.
Version 3.14.1 (rgerhards), 2008-04-04 V3 STABLE
bugfix: some messages were emited without hostname
bugfix: rsyslogd was no longer build by default; man pages are
only installed if corresponding option is selected. Thanks to
Michael Biebl for pointing these problems out.
bugfix: zero-length strings were not supported in object
deserializer
disabled atomic operations for this stable build as it caused
platform problems
bugfix: memory leaks in script engine
bugfix: $hostname and $fromhost in RainerScript did not work
bugfix: some memory leak when queue is runing in disk mode
man pages improved thanks to varmofekoj and Peter Vrabec
We have removed the 32 character size limit (from RFC3164) on the
tag. This had bad 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.
Posted by
rgerhards
on
Wednesday, April 02, 2008
386
There is just a single, yet important new feature:
major new feature: imrelp/omrelp support reliable delivery of syslog
messages via the RELP protocol and librelp (http://www.librelp.com).
Plain tcp syslog, so far the best reliability solution, can lose
messages when something goes wrong or a peer goes down. With RELP,
this can no longer happen. See imrelp.html for more details.
And, no, this feature is not related to April, 1st. Really. Trust me ;)
Posted by
rgerhards
on
Tuesday, April 01, 2008
429
bugfix: accidently set debug option in 3.12.5 reset to production
This option prevented dlclose() to be called. It had no real bad effects,
as the modules were otherwise correctly deinitialized and dlopen()
supports multiple opens of the same module without any memory footprint.
Greatly enhanced rsyslogd's file write performance by disabling
file syncing capability of output modules by default. This
feature is usually not required, not useful and an extreme performance
hit (both to rsyslogd as well as the system at large). Unfortunately,
most users enable it by default, because it was most intuitive to enable
it in plain old sysklogd syslog.conf format. There is now the
$ActionFileEnableSync config setting which must be enabled in order to
support syncing. By default it is off. So even if the old-format config
lines request syncing, it is not done unless explicitely enabled. I am
sure this is a very useful change and not a risk at all. I need to think
if I undo it under compatibility mode, but currently this does not
happen (I fear a lot of lazy users will run rsyslogd in compatibility
mode, again bringing up this performance problem...).
added flow control options to other input sources
added $HHOUR and $QHOUR system properties - can be used for half- and
quarter-hour logfile rotation
changed queue's discard severities default value to 8 (do not discard)
to prevent unintentional message loss
removed a no-longer needed callback from the output module
interface. Results in reduced code complexity.
bugfix/doc: removed no longer supported -h option from man page
bugfix: imklog leaked several hundered KB on each HUP. Thanks to
varmojfekoj for the patch
bugfix: potential segfault on module unload. Thanks to varmojfekoj for
the patch
bugfix: fixed some minor memory leaks
bugfix: fixed some slightly invalid memory accesses
bugfix: internally generated messages had "FROMHOST" property not set
Posted by
rgerhards
on
Tuesday, March 25, 2008
252
added advanced flow control for congestion cases (mode depending on message
source and its capablity to be delayed without bad side effects)
bugfix: $ModDir should not be reset on $ResetConfig - this can cause a lot
of confusion and there is no real good reason to do so. Also conflicts with
the new -M option and environment setting.
bugfix: TCP and GSSAPI framing mode variable was uninitialized, leading to
wrong framing (caused, among others, interop problems)
bugfix: TCP (and GSSAPI) octet-counted frame did not work correctly in all
situations. If the header was split across two packet reads, it was invalidly
processed, causing loss or modification of messages.
bugfix: memory leak in imfile
bugfix: duplicate public symbol in omfwd and omgssapi could lead to
segfault. thanks to varmojfekoj for the patch.
bugfix: rsyslogd aborted on sigup - thanks to varmojfekoj for the patch
some more internal cleanup ;)
begun relp modules, but these are not functional yet
Posted by
rgerhards
on
Tuesday, March 18, 2008
310
added -M rsyslogd option (allows to specify module directory location)
converted net.c into a loadable library plugin
bugfix: debug module now survives unload of loadable module when
printing out function call data
bugfix: not properly initialized data could cause several segfaults if
there were errors in the config file - thanks to varmojfekoj for the patch
bugfix: rsyslogd segfaulted when imfile read an empty line - thanks
to Johnny Tan for an excellent bug report
implemented dynamic module unload capability (not visible to end user)
some more internal cleanup
bugfix: imgssapi segfaulted under some conditions; this fix is actually
not just a fix but a change in the object model. Thanks to varmojfekoj
for providing the bug report, an initial fix and lots of good discussion
that lead to where we finally ended up.
Posted by
rgerhards
on
Thursday, March 13, 2008
303
bugfix: setting for $EscapeCopntrolCharactersOnReceive was not
properly initialized
bugfix: resolved potential segfault condition on HUP (extremely
unlikely to happen in practice), for details see tracker:
http://bugzilla.adiscon.com/show_bug.cgi?id=38
improved the man pages a bit - thanks to Michael Biebl for the patch
bugfix: not properly initialized data could cause several segfaults if
there were errors in the config file - thanks to varmojfekoj for the patch
Posted by
rgerhards
on
Wednesday, March 12, 2008
255