diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml
index d5c97c0538..7fa9149d07 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -4333,15 +4333,15 @@
to a specific target.
Using Toaster, you can do the following:
- Understand why a task fails or was
- reused from the shared state cache when you thought it
- should have been rebuilt from scratch.
+ See information about the tasks executed
+ and reused during the build.
See what is built (recipes and
packages) and what packages were installed into the final
image.
See performance-related information such
- as size, build time, CPU usage, disk input, and disk
- output.
+ as build time, CPU usage, and disk I/O.
+ Examine error, warning and trace messages
+ to aid in debugging.
@@ -4393,6 +4393,10 @@
$ source toaster start
+
+ The Toaster must be started and running in order
+ for it to collect data.
+
@@ -4446,6 +4450,19 @@
The Toaster database is persistent regardless of whether you
start or stop the service.
+
+
+
+ Toaster's interface shows you a list of builds
+ (successful and unsuccessful) for which it has data.
+ You can click on any build to see related information.
+ This information includes configuration details, information
+ about tasks, all recipes and packages built and their
+ dependencies, packages installed in your final image,
+ execution time, CPU usage and disk I/O per task.
+
+
+