From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Joachim Wiberg <troglobit@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/sysklogd: bump to version 2.4.2
Date: Mon, 1 Aug 2022 22:37:44 +0200 [thread overview]
Message-ID: <20220801223744.3b670edd@windsurf> (raw)
In-Reply-To: <20220801114320.3729655-1-troglobit@gmail.com>
On Mon, 1 Aug 2022 13:43:20 +0200
Joachim Wiberg <troglobit@gmail.com> wrote:
> Mostly a bugfix release (critical fixes to syslogd below), which also
> includes some features added to the logger tool and libsyslog related
> to logging to remote syslog servers, bypassing the local syslogd.
>
> Critical fixes:
> - Prevent over-read when scanning kermel log messages
> - Prevent kernel log file corruption when messages contain control
> codes, notably '\n', now C-style hex encoding is preserved (\x0a)
> - Forwarding of log messages to remote servers stops after a few
> SIGHUPs have been received (bug introduced in v2.4.0)
>
> Signed-off-by: Joachim Wiberg <troglobit@gmail.com>
> ---
> package/sysklogd/sysklogd.hash | 2 +-
> package/sysklogd/sysklogd.mk | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2022-08-01 20:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-01 11:43 [Buildroot] [PATCH 1/1] package/sysklogd: bump to version 2.4.2 Joachim Wiberg
2022-08-01 20:37 ` Thomas Petazzoni via buildroot [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220801223744.3b670edd@windsurf \
--to=buildroot@buildroot.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=troglobit@gmail.com \
/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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.