This command enables one ore more services inside a given tree.
66-enable [ -h help ] [ -v verbosity ] [ -l live ] [ -t tree ] [ -f force ] [ -d directory ] [ -I instance ] [ -S start ] service(s)"
This tool expects to find a corresponding frontend service file, by default at /etc/66/service. The default path can be changed at compile time by passing the --with-service-path=DIR option to ./configure. It will run a parser on the frontend service file and write the result to the directory of the given tree—see 66-tree. The service will then be available in the given tree for the next boot depending on the state of the tree. The targeted service(s) can also be started on the fly when enabling it with the -S option.
Multiple services can be enabled by seperating their names with a space.
In case of 'bundle', 'longrun' or 'oneshot' services, the dependencies chain will be automatically resolves except in use of -d option. It is unnecessary to manually define chained sets of dependencies. If FooA have a declared dependency FooB, FooB will be automatically added to the chain at FooA enabling process. This is done recursively.
The directory option -d should only be used in specific use cases like a mixed set of bundle, longrun and oneshot services where some of those depend on each other. The directory option is not limited to these types though. Any available service type can be part of the set.
A good example is a set of services for the boot process. To achieve this specific task a large number of oneshot services is used along with some classic services.
For the parser it can be rather difficult to know which service to start first in a complex set with lots of services depending on others. To help out on this problem it is neccessary to tell the command which service to start before any other when using -d by passing it as the service argument. In most cases, the root node of any dependency chain is a bundle.
This option and its mechanics can be subject to change in future releases of the 66-enable tool.