From: Carlos Santos <casantos@datacom.com.br>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 7/8] rsyslog: update S01logging
Date: Mon, 9 Jul 2018 20:37:02 -0300 (BRT) [thread overview]
Message-ID: <1872705899.2544317.1531179422549.JavaMail.zimbra@datacom.com.br> (raw)
In-Reply-To: <4b21a057-0fa7-6ff5-50c5-a0a23b9bf544@mind.be>
> From: "Arnout Vandecappelle" <arnout@mind.be>
> To: "DATACOM" <casantos@datacom.com.br>, "buildroot" <buildroot@buildroot.org>
> Cc: "ratbert90" <aduskett@gmail.com>
> Sent: Monday, July 9, 2018 7:05:30 PM
> Subject: Re: [Buildroot] [PATCH 7/8] rsyslog: update S01logging
> Note: subject is wrong s/rsyslog/syslog-ng/
OK.
[...]
>> + # shellcheck disable=SC2086 # we need the word splitting
>> + start-stop-daemon -b -S -q -p /var/run/syslog-ng.pid -x /usr/sbin/syslog-ng
>> -- -F $SYSLOG_NG_ARGS && \
>
> Again, better let the daemon take care of backgrounding itself.
>
As explained in the answer about rsyslogd, it prevents hanging the boot by
putting an "-F" in SYSLOG_NG_ARGS (in /etc/default/logging).
--
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-07-09 23:37 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-09 3:31 [Buildroot] [PATCH 0/8] init scripts: rewrite S01logging Carlos Santos
2018-07-09 3:31 ` [Buildroot] [PATCH 1/8] busybox: update S01logging Carlos Santos
2018-07-09 8:33 ` Nicolas Cavallari
2018-07-09 21:23 ` Arnout Vandecappelle
2018-07-09 21:35 ` Arnout Vandecappelle
2018-07-09 3:31 ` [Buildroot] [PATCH 2/8] busybox: add logging configuration file Carlos Santos
2018-07-09 3:31 ` [Buildroot] [PATCH 3/8] rsyslog: update S01logging Carlos Santos
2018-07-09 8:03 ` Nicolas Cavallari
2018-07-09 23:31 ` Carlos Santos
2018-07-10 7:58 ` Arnout Vandecappelle
2018-07-09 21:52 ` Arnout Vandecappelle
2018-07-09 3:31 ` [Buildroot] [PATCH 4/8] rsyslog: add logging configuration file Carlos Santos
2018-07-09 3:31 ` [Buildroot] [PATCH 5/8] sysklogd: update S01logging Carlos Santos
2018-07-09 22:00 ` Arnout Vandecappelle
2018-07-09 3:31 ` [Buildroot] [PATCH 6/8] sysklogd: add logging configuration file Carlos Santos
2018-07-09 22:04 ` Arnout Vandecappelle
2018-07-09 3:31 ` [Buildroot] [PATCH 7/8] rsyslog: update S01logging Carlos Santos
2018-07-09 22:05 ` Arnout Vandecappelle
2018-07-09 23:37 ` Carlos Santos [this message]
2018-07-09 3:31 ` [Buildroot] [PATCH 8/8] syslog-ng: add logging configuration file Carlos Santos
2018-07-09 21:09 ` [Buildroot] [PATCH 0/8] init scripts: rewrite S01logging Arnout Vandecappelle
2018-07-10 21:04 ` Yann E. MORIN
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=1872705899.2544317.1531179422549.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