From f6ed3ce7f00f3299c531b46b33ca6749ff7f31f0 Mon Sep 17 00:00:00 2001 From: Aleksey Demakov Date: Tue, 25 Mar 2008 11:23:10 +0000 Subject: switch to busybox-1.10.0 git-svn-id: https://svn.pengutronix.de/svn/ptxdist/trunks/ptxdist-trunk@7862 33e552b5-05e3-0310-8538-816dae2090ed --- config/busybox/init/Config.in | 36 +++++++++++++++++++++++++++++------- 1 file changed, 29 insertions(+), 7 deletions(-) (limited to 'config/busybox/init/Config.in') diff --git a/config/busybox/init/Config.in b/config/busybox/init/Config.in index b385e48c4..85fd8b9ba 100644 --- a/config/busybox/init/Config.in +++ b/config/busybox/init/Config.in @@ -14,7 +14,7 @@ config BB_CONFIG_INIT init is the first program run when the system boots. config BB_CONFIG_DEBUG_INIT - bool "debugging aid" + bool "Debugging aid" default n depends on BB_CONFIG_INIT help @@ -28,16 +28,38 @@ config BB_CONFIG_FEATURE_USE_INITTAB help Allow init to read an inittab file when the system boot. +config BB_CONFIG_FEATURE_KILL_REMOVED + bool "Support killing processes that have been removed from inittab" + default y + depends on BB_CONFIG_FEATURE_USE_INITTAB + help + When respawn entries are removed from inittab and a SIGHUP is + sent to init, this feature will kill the processes that have + been removed. + +config BB_CONFIG_FEATURE_KILL_DELAY + int "How long to wait between TERM and KILL (0 - send TERM only)" if FEATURE_KILL_REMOVED + range 0 1024 + default 0 + help + With nonzero setting, init sends TERM, forks, child waits N + seconds, sends KILL and exits. Setting it too high is unwise + (child will hang around for too long and can actually kill + wrong process!) + config BB_CONFIG_FEATURE_INIT_SCTTY - bool "Support running commands with a controlling-tty" + bool "Run commands with leading dash with controlling tty" default n depends on BB_CONFIG_INIT help - If this option is enabled a command starting with hyphen (-) - is run in its own session (setsid(2)) and possibly with a - controlling tty (TIOCSCTTY). This is not the traditional init - behavour, but is often what you want in an embedded system where - the console is only accessed during development or for maintenance. + If this option is enabled, init will try to give a controlling + tty to any command which has leading hyphen (often it's "-/bin/sh"). + More precisely, init will do "ioctl(STDIN_FILENO, TIOCSCTTY, 0)". + If device attached to STDIN_FILENO can be a ctty but is not yet + a ctty for other session, it will become this process' ctty. + This is not the traditional init behavour, but is often what you want + in an embedded system where the console is only accessed during + development or for maintenance. NB: using cttyhack applet may work better. config BB_CONFIG_FEATURE_INIT_SYSLOG -- cgit v1.2.3