Ticket #433 (new defect) — at Version 2

Opened 13 years ago

Last modified 13 years ago

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:1 Changed 13 years ago by broder

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.

comment:2 Changed 13 years ago by broder

  • Description modified (diff)
Note: See TracTickets for help on using tickets.