From: Carlos Santos <casantos@datacom.com.br>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 2/8] busybox: add logging configuration file
Date: Fri, 2 Nov 2018 17:01:15 -0200 (BRST) [thread overview]
Message-ID: <829805537.4906.1541185275271.JavaMail.zimbra@datacom.com.br> (raw)
In-Reply-To: <14a8b23d-ce2f-2d42-5ed3-c65eb6df0bd8@mind.be>
> From: "Arnout Vandecappelle" <arnout@mind.be>
> To: "DATACOM" <casantos@datacom.com.br>, "buildroot" <buildroot@buildroot.org>
> Cc: "ratbert90" <aduskett@gmail.com>, "Matthew Weber" <matthew.weber@rockwellcollins.com>, "Chris Packham"
> <judge.packham@gmail.com>
> Sent: Domingo, 21 de outubro de 2018 15:27:24
> Subject: Re: [PATCH v3 2/8] busybox: add logging configuration file
> On 07/10/2018 12:45, Carlos Santos wrote:
>> Provide a template to help users to customize syslogd and klogd without
>> editting the startup script.
>>
>> syslogd options worth to configure are remote logging (-R), rotation
>> (-s, -b) and minimal priority level (-l).
>>
>> klogd minimal priority level (-c) can be configured too, preventing
>> non-critical kernel messages from appearing on the console.
>>
>> This file is also useful as an example for init script authors.
>
> We also discussed this, and we agreed in the end that it is not very useful to
> have a default defaults file. It needlessly consumes space on the target, the
> user anyway probably has to consult documentation to know which options to use,
> and there is (usually) only one option that can be set in the file:
> <DAEMON>_ARGS. In addition, we can't expect all package authors to submit
> something that is of such a high quality as this example...
OK, I will drop the default files from the series.
--
Carlos Santos (Casantos) - DATACOM, P&D
?Marched towards the enemy, spear upright, armed with the certainty
that only the ignorant can have.? ? Epitaph of a volunteer
next prev parent reply other threads:[~2018-11-02 19:01 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-07 11:45 [Buildroot] [PATCH v3 0/8] init scripts: rewrite S01logging Carlos Santos
2018-10-07 11:45 ` [Buildroot] [PATCH v3 1/8] busybox: update S01logging Carlos Santos
2018-10-08 15:14 ` Matthew Weber
2018-10-21 18:23 ` Arnout Vandecappelle
2018-10-07 11:45 ` [Buildroot] [PATCH v3 2/8] busybox: add logging configuration file Carlos Santos
2018-10-08 15:23 ` Matthew Weber
2018-10-21 18:27 ` Arnout Vandecappelle
2018-11-02 19:01 ` Carlos Santos [this message]
2018-10-07 11:46 ` [Buildroot] [PATCH v3 3/8] rsyslog: update S01logging Carlos Santos
2018-10-08 15:31 ` Matthew Weber
2018-10-07 11:46 ` [Buildroot] [PATCH v3 4/8] rsyslog: add logging configuration file Carlos Santos
2018-10-08 15:31 ` Matthew Weber
2018-10-07 11:46 ` [Buildroot] [PATCH v3 5/8] sysklogd: update S01logging Carlos Santos
2018-10-07 11:46 ` [Buildroot] [PATCH v3 6/8] sysklogd: add logging configuration file Carlos Santos
2018-10-07 11:46 ` [Buildroot] [PATCH v3 7/8] syslog-ng: update S01logging Carlos Santos
2018-10-07 11:46 ` [Buildroot] [PATCH v3 8/8] syslog-ng: add logging configuration file Carlos Santos
2018-10-11 15:09 ` [Buildroot] [PATCH v3 0/8] init scripts: rewrite S01logging Thomas Petazzoni
2018-10-12 11:50 ` Carlos Santos
2018-10-13 12:55 ` Thomas Petazzoni
2018-11-02 21:13 ` Carlos Santos
2018-11-02 21:25 ` Thomas Petazzoni
2018-11-02 22:30 ` Arnout Vandecappelle
2018-11-03 10:44 ` Thomas Petazzoni
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=829805537.4906.1541185275271.JavaMail.zimbra@datacom.com.br \
--to=casantos@datacom.com.br \
--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