From: Carlos Santos <casantos@datacom.com.br>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4 1/4] busybox: rewrite logging init script
Date: Tue, 6 Nov 2018 22:31:14 -0200 (BRST) [thread overview]
Message-ID: <611772159.535678.1541550674151.JavaMail.zimbra@datacom.com.br> (raw)
In-Reply-To: <92747f04-1c9a-48d0-9649-228fc490df33@mind.be>
> From: "Arnout Vandecappelle" <arnout@mind.be>
> To: "Matthew Weber" <matthew.weber@rockwellcollins.com>, "DATACOM" <casantos@datacom.com.br>
> Cc: "ratbert90" <aduskett@gmail.com>, "buildroot" <buildroot@buildroot.org>
> Sent: Ter?a-feira, 6 de novembro de 2018 22:14:42
> Subject: Re: [Buildroot] [PATCH v4 1/4] busybox: rewrite logging init script
> On 05/11/18 14:57, Matthew Weber wrote:
>
>> I can see this naming change will cause a number of people to end up
>> debugging their targets as a custom S01logging will be copied over and
>> then the installs of the new files with different names below. Is
>> there any thoughts on making this a visible or obvious change so users
>> don't get caught up?
>
> The best we can doe is to mention it in the release notes.
>
> [snip]
>> What's the impact of someone restarting syslogd without stoping klogd first?
>
> That shouldn't affect klogd, as far as I understand, because klogd uses
> standard syslog().
In the case of a restart the klog messages (all syslog() calls, in fact)
will be sent to the system console for a short period.
--
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-07 0:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-03 18:24 [Buildroot] [PATCH v4 0/4] init scripts: rewrite S01logging Carlos Santos
2018-11-03 18:24 ` [Buildroot] [PATCH v4 1/4] busybox: rewrite logging init script Carlos Santos
2018-11-05 13:57 ` Matthew Weber
2018-11-07 0:14 ` Arnout Vandecappelle
2018-11-07 0:31 ` Carlos Santos [this message]
2018-11-07 0:21 ` Carlos Santos
2018-11-07 0:51 ` Carlos Santos
2018-11-03 18:24 ` [Buildroot] [PATCH v4 2/4] rsyslog: rewrite " Carlos Santos
2018-11-05 13:59 ` Matthew Weber
2018-11-07 0:53 ` Carlos Santos
2018-11-03 18:24 ` [Buildroot] [PATCH v4 3/4] sysklogd: " Carlos Santos
2018-11-05 14:07 ` Matthew Weber
2018-11-07 0:08 ` Arnout Vandecappelle
2018-11-07 0:32 ` Matthew Weber
2018-11-07 0:53 ` Carlos Santos
2018-11-03 18:24 ` [Buildroot] [PATCH v4 4/4] syslog-ng: " Carlos Santos
2018-11-07 0:55 ` Carlos Santos
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=611772159.535678.1541550674151.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