66-disable

Interface

    66-disable [ -h ] [ -z ] [ -v verbosity ] [ -l live ] [ -t tree ] [ -S ] [ -F ] [ -R ] service(s)

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 tool.

Multiple services can be disabled by seperating their names with a space.

Exit codes

• 0 success
• 100 wrong usage
• 111 system call failed

Options

• -h : prints this help.

• -z : use color.

• -v verbosity : increases/decreases the verbosity of the command.

  • 1 : only print error messages. This is the default.
  • 2 : also print warning messages.
  • 3 : also print tracing messages.
  • 4 : also print debugging messages.

• -l live : changes the supervision directory of service to live. By default this will be /run/66. The default can also be changed at compile time by passing the --livedir=live option to ./configure. An existing absolute path is expected and should be within a writable and executable filesystem - likely a RAM filesystem—see 66-scandir.

• -t : handles the selection of the given tree. This option is mandatory except if a tree was marked as 'current'—see 66-tree.

• -S : stops the service on the fly directly after enabling it. If the state of the service is already up, this option will have no effect unless the -f option is used to reload it.

• -F : forces the service to be disabled even if it's already marked disabled. The service must be marked uninitialized —see 66-intree. 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 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. 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.