This tool expects to find an already enabled service inside the given <em>tree</em>. The targeted service(s) can also be stopped on the fly when disabling it with the <tt>-S</tt> option.
Generally speaking this command is strictly the reverse of the <tt><ahref="66-enable.html">66-enable</a></tt> tool.
</p>
<p>Multiple <em>services</em> can be disabled by seperating their names with a space.</p>
<h2> Options </h2>
<ul>
<li><tt>-h </tt> : prints this help. </li>
the verbosity of the command. <tt>1(Default)</tt>: Only print
error messages. <tt>2</tt>: Also print warning messages.
<tt>3</tt>: Also print debugging messages.
</li>
<li>
<tt>-l <em>live</em></tt> : changes the supervision directory of <em>service</em> to <em>live</em>. By default this will be <tt>/run/66</tt>. The default can
also be changed at compile time by passing the <tt>--livedir=<em>live</em></tt>
option to <tt>./configure</tt>. An existing absolute path is expected and
should be within a writable filesystem - likely a RAM filesystem—see <tt><ahref="66-scandir.html">66-scandir</a></tt>.
</li>
<li>
<tt>-t <em>tree</em></tt> : disables the <em>service</em> from
the given <em>tree</em>. This option is mandatory
except if a tree was marked as 'current'—see <ahref="66-tree.html"><tt>66-tree</tt></a>.
</li>
<li>
<tt>-S </tt> : stops the <em>service</em> on the fly directly after disabling it. If the state of the <em>service</em> is already down, this option
will have no effect.
</li>
</ul>
<h2id="dependencies">Dependencies handling</h2>
<p>In case of <tt><em>'bundle'</em></tt>, <tt><em>'longrun'</em></tt> or <tt><em>'oneshot'</em></tt> services, the dependencies chain will be automatically resolves.
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 disabling process.
the verbosity of the command. <tt>1(Default)</tt>: Only print
error messages. <tt>2</tt>: Also print warning messages.
<tt>3</tt>: Also print debugging messages.
</li>
<li>
<tt>-l <em>live</em></tt> : changes the <em>scandir</em> directory location to <em>live</em>. By default this will be <tt>/run/66</tt>. The default can
also be changed at compile time by passing the <tt>--livedir=<em>live</em></tt>
option to <tt>./configure</tt>. An existing absolute path is expected and
should be within a writable filesystem - likely a RAM filesystem—see <tt><ahref="66-scandir.html">66-scandir</a></tt>.
</li>
<li>
<tt>-c </tt> : only initiate "classic" service from <em>tree</em>
at <em>live</em> location.
</li>
<li>
<tt>-d </tt> : only initiate a service database from <em>tree</em>
at <em>live</em> location.
</li>
<li>
<tt>-B </tt> : initiate "classic" and service database from <em>tree</em>
at <em>live</em> location.
</li>
</ul>
<h2>Initiatlization process</h2>
<h3>Classic service</h3>
<p>The tool will make a verbatim copy of all classic service files and directories of the <em>tree</em> inside a <em>scandir</em> directory at <em>live</em> location.
By default, <em>/run/66/scandir/UID</em> is created if it not exist yet where <em>UID</em> is the uid of the current owner of the process. The <em>scandir</em> is <strong>not</strong>
necessary running. For instance, this is usefull at boot time to initiate an earlier service before starting the <em>scandir</em>. When the <em>scandir</em>
starts—see <tt><ahref="66-scandir.html">66-scandir -u</a></tt> option, the already presents services starts automatically.</p>
<p>If the <em>scandir</em> is running, you should invoke a <tt>66-scandir -s reload</tt> command to prevents the <em>scandir</em> about the changes.</p>
<h3>Bundle,longrun,oneshot service</h3>
<p>The tool will invoke an <tt><ahref="https://skarnet.org/software/s6-rc/s6-rc-init.html">s6-rc-init -l <em>live</em> -c <em>compiled</em> - p <em>prefix</em></a></tt> command
where by default <em>live</em> is <tt>/run/66/tree/UID/<em>tree</em></tt>, <em>compiled</em> is <tt>/var/lib/66/system/<em>tree</em>/servicedirs/db/<em>tree</em></tt> or
<tt>$HOME/.66/system/<em>tree</em>/servicedirs/db/<em>tree</em></tt> depending of the owner of the process and <em>prefix</em> the name of <em>tree</em>. The <em>live</em>
is created if it doesn't exist yet. The <em>scandir</em><strong>must</strong> be running. In contrary of <tt>s6-rc-init</tt> behaviour, this tool like any other 66 tool can be invoked with
