From Fedora Project Wiki
< Releases
fp-wiki>ImportUser (Imported from MoinMoin) |
m (syntax changes) |
||
| (One intermediate revision by one other user not shown) | |||
| Line 24: | Line 24: | ||
As you may notice, sysklogd upstream seems dead with no new developments being released. However, there are a lot of new features that people would like to have and are asking for: | As you may notice, sysklogd upstream seems dead with no new developments being released. However, there are a lot of new features that people would like to have and are asking for: | ||
# TCP based network transport for log messages. | |||
# Secure transport over the network. | |||
# A realtime analysis framework for logmessages (e.g. to launch programs on alerts). | |||
# Database backend. | |||
# Rule (pattern) based de-multiplexing of log messages (e.g. logging to different files based on regexp). | |||
# Backward compatibility with existing syslog configuration | |||
rsyslog is the package that comes closest to meet this requirements. It has an active upstream and it is backwards compatible since its forked from the current default daemon. It has a bunch of features that you may want to look at: | rsyslog is the package that comes closest to meet this requirements. It has an active upstream and it is backwards compatible since its forked from the current default daemon. It has a bunch of features that you may want to look at: | ||
| Line 50: | Line 50: | ||
== Test Plan == | == Test Plan == | ||
# Test that introduced rsyslog package replaces sysklogd properly. | |||
# Test all features you want to see in the new rsyslog in F8 and speak up if you miss any. | |||
== Dependencies == | == Dependencies == | ||
Latest revision as of 11:18, 13 January 2009
rsyslog
Replace sysklogd with rsyslog as the default.
Owner
- Name: PeterVrabec
Current status
- Targeted release: Fedora 8
- Last updated: 2007-08-22
- Percentage of completion: 100%
Latest SRPMS/specs can be found at:
Review request
Usage cases/rationale
As you may notice, sysklogd upstream seems dead with no new developments being released. However, there are a lot of new features that people would like to have and are asking for:
- TCP based network transport for log messages.
- Secure transport over the network.
- A realtime analysis framework for logmessages (e.g. to launch programs on alerts).
- Database backend.
- Rule (pattern) based de-multiplexing of log messages (e.g. logging to different files based on regexp).
- Backward compatibility with existing syslog configuration
rsyslog is the package that comes closest to meet this requirements. It has an active upstream and it is backwards compatible since its forked from the current default daemon. It has a bunch of features that you may want to look at:
Why Not Syslog-ng?
- https://www.redhat.com/archives/fedora-devel-list/2007-June/msg02385.html
- Code Complexity
- Performance issues
- Incompatible format
- Dual licensing model where adding features available in the other version might cause friction with upstream.
Scope
testing, bugfixing, implementing new features.
Test Plan
- Test that introduced rsyslog package replaces sysklogd properly.
- Test all features you want to see in the new rsyslog in F8 and speak up if you miss any.
Dependencies
Same dependencies as in sysklogd.