about summary refs log tree commit diff
diff options
context:
space:
mode:
authorLeah Neukirchen <leah@vuxu.org>2024-01-06 23:28:22 +0100
committerLeah Neukirchen <leah@vuxu.org>2024-01-06 23:28:22 +0100
commit5048f1c099a244b54a8695e6d6a394d82c48ea26 (patch)
tree82832b34676e5ece8bebb2f5f705275cde8769cf
parent9c6bc7373e9b1956c9becd6c62e2a397c6d20aa6 (diff)
downloadnitro-5048f1c099a244b54a8695e6d6a394d82c48ea26.tar.gz
nitro-5048f1c099a244b54a8695e6d6a394d82c48ea26.tar.xz
nitro-5048f1c099a244b54a8695e6d6a394d82c48ea26.zip
README.md: mention rc.boot/finish
-rw-r--r--README.md7
1 files changed, 4 insertions, 3 deletions
diff --git a/README.md b/README.md
index b63ba42..69ec6c5 100644
--- a/README.md
+++ b/README.md
@@ -74,9 +74,10 @@ When a service exits, it's being restarted, potentially waiting for
 two seconds if the last restart happened too quickly.
 
 By using `nitroctl Reboot` or `nitroctl Shutdown`, the system can be
-brought down.  nitro will send a SIGTERM signal to all running
-services and waits for up to 7 seconds for the service to exit.
-Otherwise, a SIGKILL is sent.
+brought down.  If it exists, `rc.boot/finish` will be run.  After
+this, nitro will send a SIGTERM signal to all running services and
+waits for up to 7 seconds for the service to exit.  Otherwise, a
+SIGKILL is sent.
 
 Finally, nitro reboots or shuts down the system; or just exits
 when it was used as a container init or unprivileged supervisor.