From: Joachim Wiberg <troglobit@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC PATCH 0/1] package/sysklogd: proposal to update default syslog.conf
Date: Sun, 31 Jan 2021 23:58:26 +0100 [thread overview]
Message-ID: <87sg6gg1d9.fsf@gmail.com> (raw)
In-Reply-To: <20210131231346.6bce24e3@windsurf.home>
On Sun, Jan 31, 2021 at 23:13, Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:
> On Sat, 30 Jan 2021 14:52:02 +0100 Joachim Wiberg <troglobit@gmail.com> wrote:
>> The updated file changes the default log file from messages to syslog,
>> as is common on most modern systems today. The messages remains but
>> only for less critical messages. The update also adds more examples
>> for how to enable remote logging as well as different new log formats.
> Well, if the syslog.conf that we have in package/sysklogd/ is exactly
> the one contained in the sysklogd sources, then what is the point of
> having a copy in package/sysklogd/ ? We could just as well install the
> configuration file provided by upstream.
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.
Best regards
/Joachim
next prev parent reply other threads:[~2021-01-31 22:58 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 [this message]
2021-02-01 8:04 ` Thomas Petazzoni
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=87sg6gg1d9.fsf@gmail.com \
--to=troglobit@gmail.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