diff options
author | Rob Landley | 2006-02-08 18:50:17 +0000 |
---|---|---|
committer | Rob Landley | 2006-02-08 18:50:17 +0000 |
commit | 1ab4c3dc25217ea3a21fe5febf4e7af6d0c04427 (patch) | |
tree | c612f4c5bf25f5777364919b0f20f573ec047fd6 /Config.in | |
parent | 32251b482571d6e76a6a58ee060a1911cb4a1ae2 (diff) | |
download | busybox-1ab4c3dc25217ea3a21fe5febf4e7af6d0c04427.zip busybox-1ab4c3dc25217ea3a21fe5febf4e7af6d0c04427.tar.gz |
Help text update and tweak to defconfig to remove two more things that
the "maximum sane configuration" shouldn't have. (Explicit MTAB support in
mount, which you should only need if you have no /proc, and FEATURE_CLEAN_UP,
which exists to humor valgrind and otherwise just bloats the code).
Diffstat (limited to 'Config.in')
-rw-r--r-- | Config.in | 10 |
1 files changed, 6 insertions, 4 deletions
@@ -80,10 +80,12 @@ config CONFIG_FEATURE_CLEAN_UP bool "Clean up all memory before exiting (usually not needed)" default n help - As a size optimization, busybox by default does not cleanup memory - that is dynamically allocated or close files before exiting. This - saves space and is usually not needed since the OS will clean up for - us. Don't enable this unless you have a really good reason to clean + As a size optimization, busybox normally exits without explicitly + freeing dynamically allocated memory or closing files. This saves + space since the OS will clean up for us, but it can confuse debuggers + like valgrind, which report tons of memory and resource leaks. + + Don't enable this unless you have a really good reason to clean things up manually. config CONFIG_FEATURE_SUID |