From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC PATCH 0/1] package/sysklogd: proposal to update default syslog.conf
Date: Mon, 1 Feb 2021 09:04:31 +0100 [thread overview]
Message-ID: <20210201090431.48d3508e@windsurf.home> (raw)
In-Reply-To: <87sg6gg1d9.fsf@gmail.com>
On Sun, 31 Jan 2021 23:58:26 +0100
Joachim Wiberg <troglobit@gmail.com> wrote:
> True, no point in having a local copy.
>
> My main question was if there was any specific reason to sticking with
> the old habits of only using /var/log/messages, as BusyBox syslogd does,
> or if every logging package is free to have its own defalts? Within
> reason, of course. I'm just a bit concerned with breaking peoples
> defaults, even though they can just provide their own.
>
> If it's OK to change for sysklogd, I can post a new patch that drops
> the locallay maintained .conf and instead installs the sysklogd one.
I don't have a strong opinion on what should be our default
configuration for sysklogd. Peter, do you have any comments ?
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2021-02-01 8:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-30 13:52 [Buildroot] [RFC PATCH 0/1] package/sysklogd: proposal to update default syslog.conf Joachim Wiberg
2021-01-30 13:52 ` [Buildroot] [RFC PATCH 1/1] package/sysklogd: update default syslog.conf to match upstream Joachim Wiberg
2021-01-31 22:13 ` [Buildroot] [RFC PATCH 0/1] package/sysklogd: proposal to update default syslog.conf Thomas Petazzoni
2021-01-31 22:58 ` Joachim Wiberg
2021-02-01 8:04 ` Thomas Petazzoni [this message]
2021-02-01 9:43 ` Peter Korsgaard
2021-02-01 10:16 ` Joachim Wiberg
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=20210201090431.48d3508e@windsurf.home \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox