bootchartd: new applet
Usage: bootchartd start [PROG ARGS]|init|stop
Create /var/log/bootchart.tgz with boot chart data
Options:
start: start background logging; with PROG, run PROG, then kill
logging with USR1
stop: send USR1 to all bootchartd processes
init: start background logging; stop when getty/gdm is seen (for init scripts)
Under PID 1: as init, then exec $bootchart_init, /init, /sbin/init
function old new delta
bootchartd_main - 907 +907
dump_procs - 353 +353
packed_usage 26566 26735 +169
dump_file - 91 +91
static.dirs - 23 +23
applet_names 2176 2187 +11
applet_main 1284 1288 +4
applet_nameofs 642 644 +2
------------------------------------------------------------------------------
(add/remove: 5/0 grow/shrink: 4/0 up/down: 1560/0) Total: 1560 bytes
Signed-off-by: Denys Vlasenko <vda.linux@googlemail.com>
diff --git a/init/Config.in b/init/Config.in
index 3d99d47..76d5092 100644
--- a/init/Config.in
+++ b/init/Config.in
@@ -120,4 +120,18 @@
Mesg controls access to your terminal by others. It is typically
used to allow or disallow other users to write to your terminal
+config BOOTCHARTD
+ bool "bootchartd"
+ default n
+ help
+ bootchartd is commonly used to profile the boot process
+ for the purpose of speeding it up. In this case, it is started
+ by the kernel as the init process. This is configured by adding
+ the init=/sbin/bootchartd option to the kernel command line.
+
+ It can also be used to monitor the resource usage of a specific
+ application or the running system in general. In this case,
+ bootchartd is started interactively by running bootchartd start
+ and stopped using bootchartd stop.
+
endmenu