On Thu, Dec 17, 2020 at 04:21:17PM +0100, Andras Korn wrote:
Hi,it's entirely valid and possible to run socklog to handle locally generated logs and e.g. syslog-ng to handle remote syslog clients.The new Conflicts: in the socklog package makes this unnecessarily hard in an attempt to prevent people from shooting themselves in the foot.Please also see #506173 and #893882.At the extreme, there could be a socklog-bin package that only provides the binaries with no configuration, no automatic service startup; and a socklog package which retains the Conflicts and Depends on socklog-bin.Thanks!
Hi Andras, Thanks for the friendly feedback, much appreciated!When the socklog package got removed from Debian and I adopted it, it was suggested to merge the old socklog and socklog-run packages into one. I thought it made sense, i.e. socklog as single system/kernel log daemon running under runit, that's also how I use it.
In hindsight that was too restrictive indeed, and it looks like splitting the standalone binary from the runit system/kernel log daemon bits, as it used to be in fact, shoud make everyone happy.
The biggest risk is that I mess up the transition, but I'll give it a try, fingers crossed :)
Cheers, -- Mathieu Mirmont <m...@parad0x.org>
signature.asc
Description: PGP signature
