Rsyslog 1.17.2 has been released. This is primarily a code cleanup release. Output modules have mostly been moved to their own .c/.h files. For those of you modifying the sources, please note that patch targets most probably have been totally moved around. Please use the new version as basis for future patches. As a side-note, modularization is far from being finished. I expect to shuffle lots of code the next few days.
Some bugs were fixed. The system() call is now replaced with a more decent function. Added the $ModLoad MySQL and $DropTrailingLFOnReception config directives. This is a recommended update for all users.
rsyslog 1.17.1 has just been released. It is a cleanup and bug fixing release. IPv6 scopes are now correctly supported in $AllowedSenders. The capability to continue trying to write log files if the file system is full has been added. The binaries are now again named correctly. A few minor memory leaks on HUP have been fixed. Code cleanup and modularization continued. This is a recommended update for all users.
We are working for a while now with the Fedora project to provide rsyslog in the best possible way on that platform. One of the results are RPM packages, which are a great aid to many users.
There has been some discussion on rsyslog replacing stock sysklogd in Fedora 8. You may find this link here an interesting read:
Of course, we appreciate this effort. We now hope that lots of folks will look at rsyslog, test it and tell us about their experience. That process will most likely help us create an even better syslogd.
I thought I spread this news, as the rsyslog project will take up much more momentum. Plus, Fedora users will soon enjoy the benefits of a feature-rich, modern syslogd implementation.
Posted by
rgerhards
on
Wednesday, July 18, 2007
904
I am pleased to announce the availability of release 1.17.0.
This release offers a number of exciting new features. Directories can now be automatically generated for dynamic file names. Also, the owner and group can be set for created files and directories. Regular expressions are now supported in filters and $AllowedSenders does now fully support IPv6 addresses as well as domain wildcards. Also, control character replacement is now a user-configurable option (restoring backwards compatibility to sysklogd). There are a number of new config file directives.
The rsyslog project is looking for testers speaking Chinese, Japanese or other languages with non-western scripts. Rsyslog aims not only at providing a high-performance, rock-solid syslogd, it also would like to offer out of the box truly international support.
In order to reach these goals, we would like to conduct some testing on non-western scripts. Being illiterate ourselfs in this area, we are looking for some folks from that region that would be willing to contribute some time to testing. If you are interested, please contact me at rgerhards@adiscon.com.
News are posted to and questions may be asked at this forum thread:
Currently a lot of work is going on with rsyslog. Thus, we already have another *major* feature introduced: rsyslog has now the capability to generate output file names based on templates. This feature was often discussed and is now implemented in a very high-performance way.
What does this mean?
If you would like to split log files based on the originator host, you can now do that with just one selector line. All you need to define is a template that has the host property in it and assign that template to the file action. A sample would be:
Besides this major enhancement, control for output file permissions have been increased and some minor things be added/changed. Please see the change log for details.
I just released rsyslog 1.14.2. This version fixes all known nits with IPv6. 1.14.2 is the first version fully backwards-compatible with the 1.13.x series, so it now is an update I can generally recommend.
This release also includes some cosmetic changes, including somewhat improved documentation.
The rsyslog project is looking for folks interested in testing the recently implemented IPv6 support in rsyslog. Our own expertise and lab environment for IPv6 is seriously limited. We would like to see some serious testing, making sure that rsyslog is as reliable as possible.
We would especially interested in folks with live IPv6 installations.
No programming skills are needed, but testers should be familiar with syslogd operations and, obviously, IPv6 networks.
If you are interested, please contact me at rgerhards@adiscon.com.
Thanks,
Rainer Gerhards
Posted by
rgerhards
on
Saturday, June 30, 2007
433
Rsyslog 1.14.1 has been released. Peter Vrabec sent me a patch for TCP IPv6, so I have immediately integrated it. Thanks to Peter, IPv6 support is now complete in rsyslog. There are still some nits (which can be seen in the bug tracking system), but the implementation is pretty complete now. The nits will be addressed in the next days.
I am happy to announce that rsyslog 1.14.0 has been released today. Thanks to Peter Vrabec of Red Hat, this release now contains IPv6 support. Currently, IPv6 is only supported for UDP. There are also a few nits that need to be ironed out. However, the code is reasonably complete, so I decided to release it now. It is too good to stay hidden until IPv6 TCP is implemented. I would really appreciate any implementation reports, comments and such from IPv6 environments. I have very limited testing capabilities and so I am pretty much depending on the user base.
IPv6 and removal of the nits will be focus of the upcoming next releases. If you run rsyslog on an important production box, I recommend waiting for the next release before you upgrade.
Besides IPv6, there were some minor cleanups and a fix to the Red Hat init script - see changelog.
