Use this documentation with care! It describes
the heavily outdated version 5, which was actively
developed around 2010 and is considered dead by the
rsyslog team for many years now.
This documentation reflects the latest update of the
previously existing (now removed) v5-stable branch. It describes the 5.10.2 version, which was never
released. As such, it contains some content that
does not apply to any released version.
To obtain the doc that properly matches your installed
v5 version, obtain the doc set from your distro. Each
version of rsyslog contained the version that exactly
matches it.
As general advise, it is strongly suggested to
upgrade to the current version supported by the rsyslog
project. The current version can always be found on
the right-hand side info box on the rsyslog web site.
Note that there is no rsyslog community support available
for this heavily outdated version. If you need to stick
with it, please ask your distribution for support.
Community Resources¶
You can also browse the following online resources:
- the rsyslog wiki, a community resource which includes rsyslog configuration examples
- rsyslog online documentation (most current version only)
- rsyslog discussion forum - use this for technical support
- rsyslog video tutorials
- rsyslog change log
- rsyslog FAQ
- syslog device configuration guide (off-site)
- deutsches rsyslog forum (forum in German language)
And don’t forget about the rsyslog mailing list. If you are interested in the “backstage”, you may find Rainer’s blog an interesting read (filter on syslog and rsyslog tags). Or meet Rainer Gerhards at Facebook or Google+. If you would like to use rsyslog source code inside your open source project, you can do that without any restriction as long as your license is GPLv3 compatible. If your license is incompatible to GPLv3, you may even be still permitted to use rsyslog source code. However, then you need to look at the way rsyslog is licensed.
Feedback is always welcome, but if you have a support question, please do not mail Rainer directly (why not?) - use the rsyslog mailing list or rsyslog formum instead.