Bug#1084924: The system-log-daemon virtual package

[Ansgar 🙀 <ansgar@debian.org>]

Hi,

On Wed, 2024-12-11 at 11:19 +0000, Matthew Vernon wrote:
> On 11/12/2024 08:13, Ansgar 🙀 wrote:
> 
> > 2. Drop the "Conflicts: system-log-daemon" from providers of
> > system-
> > log-daemon
> 
> > (2.) is also technically correct: different implementations of
> > system-
> > log-daemon can coexists 
> 
> I think systemd is unusual in that it can co-exist with other 
> system-log-daemon providers, so I don't think making this change
> would be wise.

I would expect most can. The admin might have to configure them to use
a different socket.

As a random example I checked syslog-ng. It can be configured to listen
anywhere:
https://syslog-ng.github.io/admin-guide/060_Sources/220_unix-stream_unix-dgram/README#example-using-the-unix-stream-and-unix-dgram-drivers

That the default configuration might not allow multiple service to
start by default is not that much of a problem.

Note that apache2 and nginx don't conflict with each other even though
both provide httpd and bind to port 80 in their default configuration
(thus installing both fails to start at least one of them). system-log-
daemon does the same, but with /dev/log instead of a TCP port.

Ansgar