package/busybox: add missing bits from 1.17.1 update (mostly config stuff), rename...
[openwrt/svn-archive/archive.git] / package / busybox / config / init / Config.in
1 #
2 # For a description of the syntax of this configuration file,
3 # see scripts/kbuild/config-language.txt.
4 #
5
6 menu "Init Utilities"
7
8 config BUSYBOX_CONFIG_BOOTCHARTD
9 bool "bootchartd"
10 default n
11 help
12 bootchartd is commonly used to profile the boot process
13 for the purpose of speeding it up. In this case, it is started
14 by the kernel as the init process. This is configured by adding
15 the init=/sbin/bootchartd option to the kernel command line.
16
17 It can also be used to monitor the resource usage of a specific
18 application or the running system in general. In this case,
19 bootchartd is started interactively by running bootchartd start
20 and stopped using bootchartd stop.
21
22 config BUSYBOX_CONFIG_FEATURE_BOOTCHARTD_BLOATED_HEADER
23 bool "Compatible, bloated header"
24 default n
25 depends on BUSYBOX_CONFIG_BOOTCHARTD
26 help
27 Create extended header file compatible with "big" bootchartd.
28 "Big" bootchartd is a shell script and it dumps some
29 "convenient" info int the header, such as:
30 title = Boot chart for `hostname` (`date`)
31 system.uname = `uname -srvm`
32 system.release = `cat /etc/DISTRO-release`
33 system.cpu = `grep '^model name' /proc/cpuinfo | head -1` ($cpucount)
34 system.kernel.options = `cat /proc/cmdline`
35 This data is not mandatory for bootchart graph generation,
36 and is considered bloat. Nevertheless, this option
37 makes bootchartd applet to dump a subset of it.
38
39 config BUSYBOX_CONFIG_FEATURE_BOOTCHARTD_CONFIG_FILE
40 bool "Support bootchartd.conf"
41 default n
42 depends on BUSYBOX_CONFIG_BOOTCHARTD
43 help
44 Enable reading and parsing of $PWD/bootchartd.conf
45 and /etc/bootchartd.conf files.
46
47 config BUSYBOX_CONFIG_INIT
48 bool "init"
49 default y
50 select BUSYBOX_CONFIG_FEATURE_SYSLOG
51 help
52 init is the first program run when the system boots.
53
54 config BUSYBOX_CONFIG_FEATURE_USE_INITTAB
55 bool "Support reading an inittab file"
56 default y
57 depends on BUSYBOX_CONFIG_INIT
58 help
59 Allow init to read an inittab file when the system boot.
60
61 config BUSYBOX_CONFIG_FEATURE_KILL_REMOVED
62 bool "Support killing processes that have been removed from inittab"
63 default n
64 depends on BUSYBOX_CONFIG_FEATURE_USE_INITTAB
65 help
66 When respawn entries are removed from inittab and a SIGHUP is
67 sent to init, this option will make init kill the processes
68 that have been removed.
69
70 config BUSYBOX_CONFIG_FEATURE_KILL_DELAY
71 int "How long to wait between TERM and KILL (0 - send TERM only)" if FEATURE_KILL_REMOVED
72 range 0 1024
73 default 0
74 depends on BUSYBOX_CONFIG_FEATURE_KILL_REMOVED
75 help
76 With nonzero setting, init sends TERM, forks, child waits N
77 seconds, sends KILL and exits. Setting it too high is unwise
78 (child will hang around for too long and could actually kill
79 the wrong process!)
80
81 config BUSYBOX_CONFIG_FEATURE_INIT_SCTTY
82 bool "Run commands with leading dash with controlling tty"
83 default n
84 depends on BUSYBOX_CONFIG_INIT
85 help
86 If this option is enabled, init will try to give a controlling
87 tty to any command which has leading hyphen (often it's "-/bin/sh").
88 More precisely, init will do "ioctl(STDIN_FILENO, TIOCSCTTY, 0)".
89 If device attached to STDIN_FILENO can be a ctty but is not yet
90 a ctty for other session, it will become this process' ctty.
91 This is not the traditional init behavour, but is often what you want
92 in an embedded system where the console is only accessed during
93 development or for maintenance.
94 NB: using cttyhack applet may work better.
95
96 config BUSYBOX_CONFIG_FEATURE_INIT_SYSLOG
97 bool "Enable init to write to syslog"
98 default y
99 depends on BUSYBOX_CONFIG_INIT
100
101 config BUSYBOX_CONFIG_FEATURE_EXTRA_QUIET
102 bool "Be _extra_ quiet on boot"
103 default n
104 depends on BUSYBOX_CONFIG_INIT
105 help
106 Prevent init from logging some messages to the console during boot.
107
108 config BUSYBOX_CONFIG_FEATURE_INIT_COREDUMPS
109 bool "Support dumping core for child processes (debugging only)"
110 default n
111 depends on BUSYBOX_CONFIG_INIT
112 help
113 If this option is enabled and the file /.init_enable_core
114 exists, then init will call setrlimit() to allow unlimited
115 core file sizes. If this option is disabled, processes
116 will not generate any core files.
117
118 config BUSYBOX_CONFIG_FEATURE_INITRD
119 bool "Support running init from within an initrd (not initramfs)"
120 default n
121 depends on BUSYBOX_CONFIG_INIT
122 help
123 Legacy support for running init under the old-style initrd. Allows
124 the name linuxrc to act as init, and it doesn't assume init is PID 1.
125
126 This does not apply to initramfs, which runs /init as PID 1 and
127 requires no special support.
128
129 config BUSYBOX_CONFIG_HALT
130 bool "poweroff, halt, and reboot"
131 default y
132 help
133 Stop all processes and either halt, reboot, or power off the system.
134
135 config BUSYBOX_CONFIG_FEATURE_CALL_TELINIT
136 bool "Call telinit on shutdown and reboot"
137 default n
138 depends on BUSYBOX_CONFIG_HALT && !BUSYBOX_CONFIG_INIT
139 help
140 Call an external program (normally telinit) to facilitate
141 a switch to a proper runlevel.
142
143 This option is only available if you selected halt and friends,
144 but did not select init.
145
146 config BUSYBOX_CONFIG_TELINIT_PATH
147 string "Path to telinit executable"
148 default "/sbin/telinit"
149 depends on BUSYBOX_CONFIG_FEATURE_CALL_TELINIT
150 help
151 When busybox halt and friends have to call external telinit
152 to facilitate proper shutdown, this path is to be used when
153 locating telinit executable.
154
155 config BUSYBOX_CONFIG_MESG
156 bool "mesg"
157 default y
158 help
159 Mesg controls access to your terminal by others. It is typically
160 used to allow or disallow other users to write to your terminal
161
162 endmenu