Change Log :: Changelog for 1.0.3 - 2005-11-14 :: (2521 Reads)
Posted by
rgerhards
on Monday, November 14, 2005 - 05:47 PM
Version 1.0.3 (RGer), 2005-11-14, stable branch
added an additional guard to prevent rsyslogd from aborting when the 2gb file size limit is hit. While a user can configure rsyslogd to handle such situations, it would abort if that was not done AND large file support was not enabled (ok, this is hopefully an unlikely scenario)
fixed a bug that caused additional Unix domain sockets to be incorrectly processed - could lead to message loss in extreme cases
applied some patches available from the sysklogd project to code shared from there
fixed a bug that causes rsyslogd to dump core on termination when one of the selector lines did not receive a message during the run (very unlikely)
fixed an one-too-low memory allocation in the TCP sender. Could result in rsyslogd dumping core.
fixed a bug in the TCP sender that caused the retry logic to fail after an error or receiver overrun
fixed a bug in init() that could lead to dumping core
fixed a bug that could lead to dumping core when no HOSTNAME or no TAG was present in the syslog messag
Only logged in users are allowed to comment.
register/log in
