All contributions to the wiki are of course highly appreciated. Please
help to get the whole thing started. Especially success stories (aka
"what I did with rsyslog and why do I use it") are very valuable.
Rainer Gerhards
Posted by
rgerhards
on
Sunday, August 12, 2007
724
rsyslog 1.18.1 has been released today. Most importantly, the release fixes a potential segfault on HUPing rsyslogd as well as some other fixes. The size of the main message queue can now be configured, which is especially useful in high-volume environments with large traffic bursts. Also, the resume interval for actions can be configured.
Rsyslog now compiles and runs under Debian sid. Performance has been tweaked a bit and a number of minor changes happened. Version 1.18.1 is a recommended update for all users.
Rainer, the main author of rsyslog, has blogged about the threading model for the next major release of rsyslog. We recommend having a look at these two blog entries:
We are currently in the design phase for the next release. That release will make rsyslog even more powerful, with lots of cool features and a very clean code base. As such, feedback on internal things like the threading model is much appreciated right now. So feel free to ponder us with all ideas and questions that come up your mind.
Posted by
rgerhards
on
Tuesday, August 07, 2007
727
Rsyslog 1.18.0 has been released today. It offers a major new feature, to the best of our knowledge unseen in any other syslog server. Backup log destinations can now be configured. For example, rsyslog can be instructed to forward messages to a set of secondary log hosts or database servers if the primary one fails. When the primary is back online, messages are automatically been sent to it again. Backup actions do not necessarily need to be the same as the primary one. So one could also configure forwarding messages and writing them to a log file if the receiver cannot be reached. Other than that, there were a number of bug fixes and some code cleanup. Version 1.18.0 is a recommended update for all users.
rsyslog 1.17.6 has been released. This release concludes the initial effort to create an output module interface. It is now in place. Lots of code have been changed during that effort and we solicit feedback and bug reports. Newly added is the ability to work with include files in the main config file. A few debugging configuration commands have been added. There are also a number of bug fixes. This release is a strongly recommended update for users of 1.17.1 and above. There is no specific need for others, except if they like the new feature or would like to help with testing.
rsyslog 1.17.5 has been released. This release is a major milestone on the path to a clean output module interface. The abstraction of doAction() is now completed. Besides that, the release also contains some bug fixes. The focus of this release is to attract testers, as lots of codes have changed. We appreciate feedback very much. The release also contains some fixes. Users of 1.17.2 and above are advised to update. All others may do so, but it is not strongly recommended.
rsyslog 1.17.4 has been released today. This is part of the ongoing modularization effort. We now have a much cleaner interface between the main syslogd and output modules. The main purpose for release is to allow as much early testing as possible. So we would appreciate any feedback from reality. The release also contains some bug fixes. The update is only recommended to those interested in either testing or the fixes.
Have you noticed it? Syslogd.c is shrinking these days...
Ever since I started to work on this project, syslogd.c kept growing. Rsyslog was forked from sysklogd quite a while ago. I inherited working code, that enabled me to build an enhanced syslogd step by step. However, what I also inherited was a monolithic design. In the early days, that was not really an issue. Sysklogd's syslogd is roughly 2000 lines of code and lots of it is the version history in comments.
I have just released rsyslog 1.17.3. This version is a code cleanup release, implementing more of the future output module interface. It also fixes some minor bugs. The primary reason for release is to gather feedback. Lots of code has been changed, and there is a potential for new bugs. Please test this version and report back any problems you may experience. Installing this release is recommended for people interested in testing, only.
