The dinitctl enable command will currently wait for the named service to start and issue a 'started' message, but only if the service hasn't already started (in which case it outputs nothing).
The dinitctl disable command on the other hand doesn't wait for the service to stop. This is inconsistent. (It does print a warning if the service won't stop, i.e. target state is not 'stopped').
In both cases there is a minor race, internally: after the enable/disable is issued, a separate status command is issued to determine target state. However the state may have changed between the two commands.
The
dinitctl enablecommand will currently wait for the named service to start and issue a 'started' message, but only if the service hasn't already started (in which case it outputs nothing).The
dinitctl disablecommand on the other hand doesn't wait for the service to stop. This is inconsistent. (It does print a warning if the service won't stop, i.e. target state is not 'stopped').In both cases there is a minor race, internally: after the enable/disable is issued, a separate status command is issued to determine target state. However the state may have changed between the two commands.