If stopping a service would also require a dependent service to stop, a warning
will be issued and the `--force` option will be required.
-Use the "-s" switch to talk the "system" instance of Dinit, rather than a
-personal instance, e.g:
+Use the "-u" switch to talk the "user" instance of Dinit, rather than the system
+instance, e.g:
- dinitctl -s start mysql # start system mysql service
+ dinitctl -u start mysql # start user mysql service
+
+The -u flag is implicitely set when calling dinitctl as a regular user, not when root.
For complete details on the command line, use:
it from changing state either due to a dependency/dependent or a direct
command:
- dinitctl -s start --pin mysql # start mysql service, pin it as "started"
- dinitctl -s stop mysql # issues stop, but doesn't take effect due to pin
- dinitctl -s unpin mysql # release pin; service will now stop
+ dinitctl start --pin mysql # start mysql service, pin it as "started"
+ dinitctl stop mysql # issues stop, but doesn't take effect due to pin
+ dinitctl unpin mysql # release pin; service will now stop
You can pin a service in the stopped state in order to make sure it doesn't
get started accidentally (either via a dependency or directly). You can also
Finally, you can list the state of all loaded services:
- dinitctl -s list
+ dinitctl list
This may result in something like the following:
\fB\-\-help\fR
display this help and exit
.TP
-\fB\-s\fR, \fB\-\-system\fR
-Control the system init process. The default is to control the user process. This option selects
+\fB\-u\fR, \fB\-\-user\fR
+Control the user init process. The default is to control the system process. This option selects
the path to the control socket used to communicate with the \fBdinit\fR daemon process.
.TP
\fB\-\-socket\-path\fR \fIsocket-path\fR, \fB\-p\fR \fIsocket-path\fR