From 786c9dc0c1351cea34e71a91c6bf34a3c62b19d4 Mon Sep 17 00:00:00 2001 From: Denys Vlasenko Date: Thu, 26 Jan 2017 18:31:51 +0100 Subject: [PATCH] sh: fix FEATURE_SH_STANDALONE help text: it does not enable NOFORK Signed-off-by: Denys Vlasenko --- shell/Config.src | 20 ++++---------------- 1 file changed, 4 insertions(+), 16 deletions(-) diff --git a/shell/Config.src b/shell/Config.src index 3545f05dd..6a7e12aa7 100644 --- a/shell/Config.src +++ b/shell/Config.src @@ -121,23 +121,11 @@ config FEATURE_SH_STANDALONE for use as a rescue shell, in the event that you screw up your system. This is implemented by re-execing /proc/self/exe (typically) - with right parameters. Some selected applets ("NOFORK" applets) - can even be executed without creating new process. - Instead, busybox will call _main() internally. + with right parameters. - However, this causes problems in chroot jails without mounted /proc - and with ps/top (command name can be shown as 'exe' for applets - started this way). -# untrue? -# Note that this will *also* cause applets to take precedence -# over shell builtins of the same name. So turning this on will -# eliminate any performance gained by turning on the builtin "echo" -# and "test" commands in ash. -# untrue? -# Note that when using this option, the shell will attempt to directly -# run '/bin/busybox'. If you do not have the busybox binary sitting in -# that exact location with that exact name, this option will not work at -# all. + However, there are drawbacks: it is problematic in chroot jails without + mounted /proc, and ps/top may show command name as 'exe' for applets + started this way. config FEATURE_SH_NOFORK bool "Run 'nofork' applets directly"