The enhanced syslogd for Linux and Unix

Edit Package rsyslog

Rsyslog is an enhanced multi-threaded syslogd supporting, among others,
MySQL, syslog/tcp, RFC 3195, permitted sender lists, filtering on any
message part, and fine grain output format control. It is quite
compatible to stock sysklogd and can be used as a drop-in replacement.
Its advanced features make it suitable for enterprise-class, encryption
protected syslog relay chains while at the same time being very easy to
setup for the novice user.

Refresh
Refresh
Source Files
Filename Size Changed
rsyslog-7.2.1.tar.gz 0002696341 2.57 MB
rsyslog.changes 0000035583 34.7 KB
rsyslog.conf.in 0000004444 4.34 KB
rsyslog.d.remote.conf.in 0000003260 3.18 KB
rsyslog.spec 0000018965 18.5 KB
rsyslog.sysconfig 0000001504 1.47 KB
Revision 59 (latest revision is 178)
Stephan Kulow's avatar Stephan Kulow (coolo) accepted request 139692 from Marius Tomaschewski's avatar Marius Tomaschewski (mtomaschewski) (revision 59)
- Update to 7.2.1 (v7-stable), a pure bug-fixing release: 
  - bugfix: ruleset()-object did only support a single statement
  - added -D rsyslogd option to enable config parser debug mode
  - improved syntax error messages by outputting the error token
  - the rsyslog core now suspeneds actions after 10 failures in
    a row. This was former the case after 1,000 failures and could
    cause rsyslog to be spammed/ressources misused.
    See the v6 compatibility doc for more details.
  - ommongodb rate-limits error messages to prevent spamming the
    syslog closes (for v7.2):
    http://bugzilla.adiscon.com/show_bug.cgi?id=366
- Enabled compilation of kmsg, the kernel’s new structured logging
  system modile, mmaudit the message modification module supporting
  Linux audit format and mmjsonparse providing the cee-enhanced
  syslog format support message modification module.

- Update to 7.2.0 (v7-stable) a full structured-logging/CEE enabled
  version which provides following features compared to v5-stable:
  * greatly improved configuration language – the new language is
    much more intuitive than the legacy format. It will also prevent
    some typical mistakes simply be not permitting these invalid
    constructs. Note that legacy format is still fully supported
    (and you can of course do the same mistakes if you use legacy
    format).
  * greatly improved execution engine – with nested if/then/else
    constructs as well as the capability to modify variables during
    processing.
  * full support for structured logging and project lumberjack/CEE.
    this includes everything from being able to create, interpret
    and handle JSON-based structured log messages, including the
Comments 0
openSUSE Build Service is sponsored by