From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv3] syslog-ng: New package
Date: Sun, 18 Oct 2015 17:38:45 +0200 [thread overview]
Message-ID: <20151018173845.62e62bd9@free-electrons.com> (raw)
In-Reply-To: <1444811658-16549-1-git-send-email-judge.packham@gmail.com>
Dear Chris Packham,
On Wed, 14 Oct 2015 21:34:18 +1300, Chris Packham wrote:
> syslog-ng is an enhanced log daemon, supporting a wide range of input
> and output methods: syslog, unstructured text, queueing, SQL & NoSQL.
>
> Signed-off-by: Chris Packham <judge.packham@gmail.com>
> ---
> Changes since v1:
> - add hash file
> - use simplified logging configuration for buildroot
> - don't install man pages
Applied with a number of changes:
[Thomas:
- Rewrap Config.in.help text
- Pass --pidfile option when starting syslog-ng so that its PID file
is created in /var/run/syslog-ng.pid, which allows
start-stop-daemon to actually stop syslog-ng. Without this,
S01logging was not able to stop syslog-ng.
- Pass the executable path at stop time in S01logging, so that
start-stop-daemon can check we're not incorrectly stopping
something completely different.
- Add busybox as a dependency of syslog-ng if busybox is enabled,
since we want to override Busybox's S01logging init script.
- Simplify the python condition, since python and python3 are
mutually exclusive.
- Rewrap the comment above SYSLOG_NG_FIXUP_CONFIG.]
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2015-10-18 15:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-14 7:41 [Buildroot] [PATCHv2] syslog-ng: New package Chris Packham
2015-10-14 7:50 ` Thomas Petazzoni
2015-10-14 7:58 ` Chris Packham
2015-10-14 8:01 ` Thomas Petazzoni
2015-10-14 8:34 ` [Buildroot] [PATCHv3] " Chris Packham
2015-10-18 15:38 ` Thomas Petazzoni [this message]
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=20151018173845.62e62bd9@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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