X-Git-Url: https://git.rohieb.name/openwrt.git/blobdiff_plain/7d588e1ab6de989156fcf8c9036852eb1808b564..3811f77e30bd1ced9f69708b3dbcf28bf3ba88d1:/package/busybox/config/init/Config.in diff --git a/package/busybox/config/init/Config.in b/package/busybox/config/init/Config.in index b8ad0d664..a84169d46 100644 --- a/package/busybox/config/init/Config.in +++ b/package/busybox/config/init/Config.in @@ -12,14 +12,6 @@ config BUSYBOX_CONFIG_INIT help init is the first program run when the system boots. -config BUSYBOX_CONFIG_DEBUG_INIT - bool "debugging aid" - default n - depends on BUSYBOX_CONFIG_INIT - help - Turn this on to disable all the dangerous - rebooting stuff when debugging. - config BUSYBOX_CONFIG_FEATURE_USE_INITTAB bool "Support reading an inittab file" default y @@ -27,16 +19,44 @@ config BUSYBOX_CONFIG_FEATURE_USE_INITTAB help Allow init to read an inittab file when the system boot. +config BUSYBOX_CONFIG_FEATURE_KILL_REMOVED + bool "Support killing processes that have been removed from inittab" + default n + depends on BUSYBOX_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 BUSYBOX_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 BUSYBOX_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 BUSYBOX_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 BUSYBOX_CONFIG_FEATURE_INIT_SYSLOG + bool "Enable init to write to syslog" + default y + depends on BUSYBOX_CONFIG_INIT config BUSYBOX_CONFIG_FEATURE_EXTRA_QUIET bool "Be _extra_ quiet on boot" @@ -52,17 +72,15 @@ config BUSYBOX_CONFIG_FEATURE_INIT_COREDUMPS help If this option is enabled and the file /.init_enable_core exists, then init will call setrlimit() to allow unlimited - core file sizes. If this option is disabled, processes + core file sizes. If this option is disabled, processes will not generate any core files. - - config BUSYBOX_CONFIG_FEATURE_INITRD bool "Support running init from within an initrd (not initramfs)" default n depends on BUSYBOX_CONFIG_INIT help - Legacy support for running init under the old-style initrd. Allows + Legacy support for running init under the old-style initrd. Allows the name linuxrc to act as init, and it doesn't assume init is PID 1. This does not apply to initramfs, which runs /init as PID 1 and @@ -78,7 +96,7 @@ config BUSYBOX_CONFIG_MESG bool "mesg" default y help - Mesg controls access to your terminal by others. It is typically + Mesg controls access to your terminal by others. It is typically used to allow or disallow other users to write to your terminal endmenu