From: Carlos Santos <casantos@datacom.com.br>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 6/8] sysklogd: add logging configuration file
Date: Mon, 9 Jul 2018 00:31:32 -0300 [thread overview]
Message-ID: <20180709033134.22175-7-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. Also warn about options that must not be
used.
syslogd options worth to configure are mark interval (-m), remote log
support (-r) and domain list (-s).
Give example of how to configure klogd re-initialization signal.
Signed-off-by: Carlos Santos <casantos@datacom.com.br>
---
package/sysklogd/etc.default.logging | 25 +++++++++++++++++++++++++
package/sysklogd/sysklogd.mk | 2 ++
2 files changed, 27 insertions(+)
create mode 100644 package/sysklogd/etc.default.logging
diff --git a/package/sysklogd/etc.default.logging b/package/sysklogd/etc.default.logging
new file mode 100644
index 0000000000..d6e4410028
--- /dev/null
+++ b/package/sysklogd/etc.default.logging
@@ -0,0 +1,25 @@
+#
+# /etc/default/logging (sysklog version)
+#
+
+# Use SYSLOGD_ARGS to pass additional arguments to syslogd.
+# - Do NOT use "-v", since it will break the startup script.
+# - Do NOT use "-d", since debugging does not work when running in background.
+# SYSLOGD_ARGS="-m 0" # (default value)
+
+# Use KLOGD_ARGS to pass additional arguments to klogd.
+# - Do NOT use "-o" nor "-v", since they will break the startup script.
+# - Do NOT use "-d", since debugging does not work when running in background.
+# KLOGD_ARGS="-m 0" # (default value)
+
+# Use KLOGD_RELOAD to select the "S01logging reload" behavior.
+# - "USR1" will cause the kernel module symbols to be reloaded.
+# - "USR2" will cause both the static kernel symbols and the kernel module
+# symbols to be reloaded.
+# - "0" will do nothing.
+# - Do not use any other value here. Use kill(1) for fine-grained control of
+# klogd, as documented in its manual page.
+# KLOGD_RELOAD="0" # (default value)
+
+# Uncomment the line below to disable this service
+# ENABLED="no"
diff --git a/package/sysklogd/sysklogd.mk b/package/sysklogd/sysklogd.mk
index c4f064c10b..b7e67ffee3 100644
--- a/package/sysklogd/sysklogd.mk
+++ b/package/sysklogd/sysklogd.mk
@@ -25,6 +25,8 @@ endef
define SYSKLOGD_INSTALL_INIT_SYSV
$(INSTALL) -m 755 -D package/sysklogd/S01logging \
$(TARGET_DIR)/etc/init.d/S01logging
+ $(INSTALL) -m 0644 -D package/sysklogd/etc.default.logging \
+ $(TARGET_DIR)/etc/default/logging
endef
define SYSKLOGD_INSTALL_INIT_SYSTEMD
--
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 ` [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 ` Carlos Santos [this message]
2018-07-09 22:04 ` [Buildroot] [PATCH 6/8] sysklogd: add logging configuration file 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-7-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