mirror of
https://github.com/troglobit/finit.git
synced 2026-10-01 13:33:09 +07:00
Joachim Nilsson
260335a19f
The generic term for a non-running service is blocked, but a service may be blocked for several different reasons. When a user stops a service with `initctl stop` the intuitive expected output from `initctl show` is "stopped" not "blocked". When the user later restarts the service with `initctl start` it may of course be blocked due to wrong runlevel or a missing condition. As can be expected from the service's configuration. The rest of the patch refactors the internal API names a bit to reflect this change. Signed-off-by: Joachim Nilsson <troglobit@gmail.com>
1.2 KiB
1.2 KiB
Finit Services
State Machine
A service is bound to a state machine that is in one of six (6) states.
For runs and tasks there is an additional end state called DONE,
not shown in the diagram for brevity. Services start in the HALTED
state.
The current state depends on the two following conditions:
-
E: Service enabled. In order forEto be satisfied, the service must be allowed to run in the current runlevel and not be stopped.A service may be stopped, or blocked, for several reasons:
- The user has manually stopped the service using
initctl stop JOB - The program exits immediately. I.e. keeps crashing (make sure to use the 'run this service in the foreground' command line option)
- The binary is missing in the filesystem
- The user has manually stopped the service using
-
C: Service conditions are satisfied:on(+): The condition is asserted.off(-): The condition is deasserted.flux(~): The conditions state is unknown.
For a detailed description of conditions, and how to debug them, see the Finit Conditions document.