This tool expects to find an already enabled *service* inside the given *tree*. The targeted service(s) can also be stopped on the fly when disabling it with the **-S** option. Generally speaking this command is the strict opposite of the [66-enable](66-enable.html) tool.
...
...
@@ -43,6 +43,8 @@ Multiple *services* can be disabled by seperating their names with a space.
-**-F** : forces the *service* to be disabled even if it's already marked disabled. The *service***must** be marked uninitialized —see [66-intree](66-intree.html). The dependency of the *service* is **not** handled except for its associated logger. Also, this option cannot be used for a logger service. This option should only be used when an inconsistent state exist between the actual contents of the compiled service database and the display of the contents of a tree with the [66-intree](66-intree.html) command. For example, if you disable a service and a power failure occur, the service will be marked uninitialized and disabled at the next boot inside your tree. In this case use this option to cleanup your tree.
-**-R** : disable and remove its configuration and logger files. The *service***must** be marked uninitialized —see [66-intree](66-intree.html). The dependency of the *service***is** handled. Also, this option cannot be used for a logger service.
## Dependencies handling
In case of `bundle`, `module` or `'atomic'` services, any dependency chain will be automatically resolved. It is unnecessary to manually define chained sets of dependencies. If FooA has a declared dependency on FooB, FooB will be automatically disabled as well when disabling FooA. This will run recursively until all dependencies are disabled.
