Ticket #433 (closed defect: fixed)
syslog-config needs to use rsyslog
Reported by: | broder | Owned by: | |
---|---|---|---|
Priority: | blocker | Milestone: | Karmic Deploy (Canceled) |
Component: | -- | Keywords: | karmic |
Cc: | Fixed in version: | ||
Upstream bug: |
Description (last modified by broder) (diff)
It looks like rsyslog has finally replaced sysklogd. Since ubuntu-minimal depends on rsyslog, this isn't something we can work around.
rsyslog is available in every release we support, except for Etch, so we'll need to do something clever to create a package that configures sysklogd for older releases and rsyslog for newer ones.
I don't know if "older releases" should just be Etch, or anything pre-Karmic, or what.
See also, http://www.ubuntu.com/getubuntu/releasenotes/910#Syslog%20upgrade and http://www.debian.org/releases/stable/amd64/release-notes/ch-whats-new.en.html#system-changes
Change History
comment:3 Changed 15 years ago by broder
- Status changed from new to proposed
It took a few tries, but this should have been fixed in r24240, r24241, r24242, r24243, r24244, and r24246, and is currently in -proposed.
Debian uses package priority to determine what should be installed by default on a system, and in this case, Ubuntu matched that usage (in addition to using metapackages), so I was able to determine whether rsyslog or sysklogd was the default based on which had an priority of important. Specifically, I created a debathena-syslog metapackage that depends on whatever package has priority: important and provides: system-log-daemon.
As far as I know, rsyslog was the default for >=lenny, and >=karmic. We should use rsyslog on those releases.
Especially since sysklogd is still available in Debian, we can't make the determination of which syslog package to use based on the apt repository. I think we want to do this by making a debathena-syslog metapackage that explicitly tests lsb_release or whatever to actually determine what release it's running on, then use that as a build-dep.