Improve docs about -c/--cleanup

diff --git a/ccache.c b/ccache.c
index 9e424e3f187f3e591eeae0f59cfa00fccfb05a97..3c736b43692f9a1fa8ebb0687cfe5631c7412462 100644 (file)
--- a/ccache.c
+++ b/ccache.c
@@ -55,7 +55,10 @@ static const char USAGE_TEXT[] =
 "    compiler [compiler options]          (via symbolic link)\n"
 "\n"
 "Options:\n"
-"    -c, --cleanup         run a cache cleanup\n"
+"    -c, --cleanup         delete old cached files until the cache limits are\n"
+"                          not exceeded and recalculate file and size counters\n"
+"                          (normally not needed as ccache does this\n"
+"                          automatically)\n"
 "    -C, --clear           clear the cache completely\n"
 "    -F, --max-files=N     set maximum number of files in cache to N (use 0 for\n"
 "                          no limit)\n"

diff --git a/manual.txt b/manual.txt
index 46a5f40106f0fafd09a406192e2037c06327769b..34dffded3ebe50688da53b7e7eb06c94515d2a45 100644 (file)
--- a/manual.txt
+++ b/manual.txt
@@ -91,12 +91,13 @@ refer to the compiler's documentation.
 
 *-c, --cleanup*::
 
-    Clean the cache and recalculate the cache file count and size totals.
-    Normally the -c option should not be necessary as ccache keeps the cache
-    below the specified limits at runtime and keeps statistics up to date on
-    each compile. This option is mostly useful if you manually modify the cache
-    contents or believe that the cache size statistics may be inaccurate.
-
+    Clean up the cache by removing old cached files until the specified file
+    number and cache size limits are not exceeded. This also recalculates the
+    cache file count and size totals. Normally, it's not needed to initiate
+    cleanup manually as ccache keeps the cache below the specified limits at
+    runtime and keeps statistics up to date on each compilation. Forcing a
+    cleanup is mostly useful if you manually modify the cache contents or
+    believe that the cache size statistics may be inaccurate.
 
 *-C, --clear*::