From: "Ludovic Courtès" <ludo@gnu.org>
To: Jean-Baptiste Note <jean-baptiste.note@m4x.org>
Cc: 70677-done@debbugs.gnu.org
Subject: bug#70677: [PATCH 0/2] Improve syslog service flexibility
Date: Mon, 23 Dec 2024 18:13:59 +0100 [thread overview]
Message-ID: <874j2u9vag.fsf@gnu.org> (raw)
In-Reply-To: <cover.1714490986.git.jean-baptiste.note@m4x.org> (Jean-Baptiste Note's message of "Tue, 30 Apr 2024 15:34:21 +0000")
Hi,
Jean-Baptiste Note <jean-baptiste.note@m4x.org> skribis:
> While setting up centralized logging in a guix environment, I had to add flags
> to the running syslog on the central server (udp networking, for instance).
>
> Further, I had to use rsyslog instead of syslog.
>
> The following set of patches enable both of these to be done. The patches are
> independent conceptually but touch around the same pieces of code, so they're
> presented as a set.
>
> Jean-Baptiste Note (2):
> services: syslog: Add extra-options argument to syslog service.
> services: syslog: Adjust service for rsyslog compatibility.
Finally applied.
Sorry that it took so many months for no good reason!
Ludo’.
next prev parent reply other threads:[~2024-12-23 17:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-30 15:34 [bug#70677] [PATCH 0/2] Improve syslog service flexibility Jean-Baptiste Note
2024-04-30 15:36 ` [bug#70677] [PATCH 1/2] services: syslog: Add extra-options argument to syslog service Jean-Baptiste Note
2024-04-30 15:36 ` [bug#70677] [PATCH 2/2] services: syslog: Adjust service for rsyslog compatibility Jean-Baptiste Note
2024-12-23 17:13 ` Ludovic Courtès [this message]
2024-12-23 22:34 ` [bug#70677] [PATCH 0/2] Improve syslog service flexibility Jean-Baptiste Note
2024-12-25 17:14 ` [bug#75091] [PATCH] services: syslog: fix configuration file argument 45mg
2024-12-25 21:49 ` bug#75091: " Ludovic Courtès
2024-12-26 11:30 ` [bug#70677] [PATCH 0/2] Improve syslog service flexibility Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874j2u9vag.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=70677-done@debbugs.gnu.org \
--cc=jean-baptiste.note@m4x.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).