stop
Stop services for a project, service, or the entire supervisor.Options
| Short | Long | Description |
|---|---|---|
-c | --config | Path to the configuration file. When a supervisor is running, systemg uses it to resolve the target project. Without a supervisor, systemg uses it to locate persisted service state |
-s | --service | Name of a specific service to stop. If not specified, all services are stopped |
-p | --project | Target a stable project id when stopping services |
- | --supervisor | Shut down the resident supervisor and all registered projects |
- | --sys | Opt into privileged system mode. Requires running as root |
- | --log-level | Set logging verbosity for this invocation. Accepts named levels (trace, debug, info, warn, error, off) or numeric values (5-0) |
Examples
Stop the current project
stop is project-scoped. It resolves the current config context
and stops the services for that project.
Stop a project from a config
Stop a registered project
Stop a specific service
Shut down the supervisor
sysg status reports No running supervisor.
What happens
- Services stop in reverse dependency order
- Each service receives
SIGTERM - After 10 seconds,
SIGKILLis sent if needed - The supervisor remains available unless you used
--supervisor
Reloading a manifest after stop
Stopping a project does not freeze its old unit definitions. Runningsysg stop --project <id> followed by sysg start --config <file> reloads the
project from the supplied config, so manifest changes (added or removed
services, changed commands) are applied on the next start. To reload in place
without a stop, use restart --project <id>,
which reuses the project’s stored config path.