[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug#41688] [PATCH] Add rsyslog
From: |
Katherine Cox-Buday |
Subject: |
[bug#41688] [PATCH] Add rsyslog |
Date: |
Wed, 05 Jan 2022 14:04:46 -0600 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux) |
Ricardo Wurmus <rekado@elephly.net> writes:
> I’ve followed Ludo’s suggestions for the remaining package definitions
> and pushed the result to the “master” branch.
Thank you so much, Ricardo!
It is my fault for letting this sit, but I think we should unbundle the outputs
once more -- even if they must become separate packages.
As you know, rsyslog is meant to forward (egress) and receive (ingress) syslog
logs, and it does so through these plug-ins. For ingress, I don't think this
package is necessarily a problem, but systems that want to forward logs may
have very limited resources (e.g. I have a wifi repeater that forwards logs). I
didn't want to require things like PostgreSQL and MySQL, dependencies required
by ingress, on egress.
A secondary concern is that a package like rsyslog becomes quite sticky since
there are lots and lots of modules, and I imagine the Guix closure becomes
quite big.
> Among the changes:
>
> - fixed and clarified licenses
> - removed per-module outputs
> - removed default configure flags and added a comment about enabling
> optional features
> - enabled tests
> - removed “dev” output
> - used new input style
>
> Now I guess we’ll need an rsyslog service :)
I'm working[1] on it! Although it is frustrating at how little time I have to
dedicate to things like this :(
> Thank you, Katherine, for the patches and your patience!
Likewise, thank you for your contributions and getting this landed. Cheers!
[1] -
https://github.com/kat-co/guix-channels/blob/upstream-staging/upstream/services/rsyslog.scm
--
Katherine
- [bug#41688] [PATCH] Add rsyslog,
Katherine Cox-Buday <=