Skip to main content

Module stop

Module stop 

Source
Expand description

Stopping the containers no QCode owns any more.

This is the whole work of the background service, and the one a closing QCode does itself when the service is not installed. It runs once nothing can be using the containers: the caller makes sure of that before calling it. What it does is spelled out as engine commands and run through a runner it is handed, so every decision — what is listed, what is stopped, what stays listed — is checked in tests with no engine anywhere near them.

Structs§

Stopping
What stopping did, container by container.

Enums§

Reaped
What came of looking at the list of QCode’s containers.

Functions§

reap
Reads the list at path, stops what stop_orphans says to, and writes back what stays listed.
stop_commands
The commands that stop the containers of registered that listing shows as up in engine, one entry per container with its name and what is run for it, in that order.
stop_orphans
Stops every container of registry that is running, when on_close says to, and answers what came of it.