From: Carlos Santos <casantos@datacom.com.br>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/8] busybox: add logging configuration file
Date: Mon, 9 Jul 2018 00:31:28 -0300 [thread overview]
Message-ID: <20180709033134.22175-3-casantos@datacom.com.br> (raw)
In-Reply-To: <20180709033134.22175-1-casantos@datacom.com.br>
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.
Signed-off-by: Carlos Santos <casantos@datacom.com.br>
---
package/busybox/busybox.mk | 2 ++
package/busybox/etc.default.logging | 13 +++++++++++++
2 files changed, 15 insertions(+)
create mode 100644 package/busybox/etc.default.logging
diff --git a/package/busybox/busybox.mk b/package/busybox/busybox.mk
index 5266f844b6..fac2c394cf 100644
--- a/package/busybox/busybox.mk
+++ b/package/busybox/busybox.mk
@@ -252,6 +252,8 @@ define BUSYBOX_INSTALL_LOGGING_SCRIPT
then \
$(INSTALL) -m 0755 -D package/busybox/S01logging \
$(TARGET_DIR)/etc/init.d/S01logging; \
+ $(INSTALL) -m 0644 -D package/busybox/etc.default.logging \
+ $(TARGET_DIR)/etc/default/logging; \
fi
endef
diff --git a/package/busybox/etc.default.logging b/package/busybox/etc.default.logging
new file mode 100644
index 0000000000..6775622779
--- /dev/null
+++ b/package/busybox/etc.default.logging
@@ -0,0 +1,13 @@
+#
+# /etc/default/logging (busybox version)
+#
+
+# Use SYSLOGD_ARGS to pass additional arguments to syslogd (e.g. for log
+# rotation).
+# SYSLOGD_ARGS="" # (default value)
+
+# Use KLOGD_ARGS to pass additional arguments to klogd.
+# KLOGD_ARGS="" # (default value)
+
+# Uncomment the line below to disable this service
+# ENABLED="no"
--
2.17.1
next prev parent reply other threads:[~2018-07-09 3:31 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 ` Carlos Santos [this message]
2018-07-09 3:31 ` [Buildroot] [PATCH 3/8] rsyslog: " 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
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=20180709033134.22175-3-casantos@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