From: Will Moore <will.moore@beraninstruments.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Allow build of dropbear without wtmp and lastlog support to stop it from generating system log error messages
Date: Tue, 25 Oct 2011 10:36:42 +0100 [thread overview]
Message-ID: <1319535402-2358-1-git-send-email-will.moore@beraninstruments.com> (raw)
Signed-off-by: Will Moore <will.moore@beraninstruments.com>
---
package/dropbear/Config.in | 16 ++++++++++++++++
package/dropbear/dropbear.mk | 8 ++++++++
2 files changed, 24 insertions(+), 0 deletions(-)
diff --git a/package/dropbear/Config.in b/package/dropbear/Config.in
index c30228f..58fed4a 100644
--- a/package/dropbear/Config.in
+++ b/package/dropbear/Config.in
@@ -23,3 +23,19 @@ config BR2_PACKAGE_DROPBEAR_SMALL
Tradeoffs are slower hashes and ciphers, and disabling of the
blowfish cipher and zlib.
+
+config BR2_PACKAGE_DROPBEAR_DISABLE_WTMP
+ bool "disable logging of dropbear access to wtmp"
+ depends on BR2_PACKAGE_DROPBEAR
+ help
+ Disable logging of dropbear access to wtmp. Buildroot does not generate
+ wtmp by default and so by disabling dropbear's use of wtmp this
+ prevents warnings in the system log.
+
+config BR2_PACKAGE_DROPBEAR_DISABLE_LASTLOG
+ bool "disable logging of dropbear access to lastlog"
+ depends on BR2_PACKAGE_DROPBEAR
+ help
+ Disable logging of dropbear access to lastlog. Buildroot does not
+ generate lastlog by default and so by disabling dropbear's use of
+ lastlog this prevents warnings in the system log.
diff --git a/package/dropbear/dropbear.mk b/package/dropbear/dropbear.mk
index e9da42d..0c9c5fc 100644
--- a/package/dropbear/dropbear.mk
+++ b/package/dropbear/dropbear.mk
@@ -46,6 +46,14 @@ DROPBEAR_POST_EXTRACT_HOOKS += DROPBEAR_BUILD_FEATURED
DROPBEAR_DEPENDENCIES += zlib
endif
+ifeq ($(BR2_PACKAGE_DROPBEAR_DISABLE_WTMP),y)
+DROPBEAR_CONF_OPT += --disable-wtmp
+endif
+
+ifeq ($(BR2_PACKAGE_DROPBEAR_DISABLE_LASTLOG),y)
+DROPBEAR_CONF_OPT += --disable-lastlog
+endif
+
define DROPBEAR_INSTALL_TARGET_CMDS
$(INSTALL) -m 755 $(@D)/dropbearmulti $(TARGET_DIR)/usr/sbin/dropbear
for f in $(DROPBEAR_TARGET_BINS); do \
--
1.7.0.4
next reply other threads:[~2011-10-25 9:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-25 9:36 Will Moore [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-10-25 12:22 [Buildroot] [PATCH] Allow build of dropbear without wtmp and lastlog support to stop it from generating system log error messages Will Moore
2011-10-26 9:28 ` Peter Korsgaard
2011-10-24 12:24 Will Moore
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=1319535402-2358-1-git-send-email-will.moore@beraninstruments.com \
--to=will.moore@beraninstruments.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