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>-r </tt> : shows the dependency graph of <em>tree</em> in reverse mode.
</li>
...
...
@@ -103,18 +108,20 @@
</ul>
<h2>Tree output display example</h2>
<p>The command <tt>66-info -T boot</tt> as root user on the <em>Obarun</em> default system displays the following where <em>boot</em>
<p>By default the first service displayed is the first service started, the second one is the second started and so on.</p>
<p>The first line gives you useful information about the <em>tree</em> itself where <tt><em>Name</em></tt> is the name of the tree,
<p>The first line give you the name of the <em>tree</em>, <tt><em>Initialized</em></tt> tells if the <tree>tree</tree> was initialized with <tt><ahref="66-init.html">66-init</a></tt> tool,
<tt><em>Current</em></tt> tells if the <em>tree</em> is the current one or not—see <tt><ahref="66-tree.html">66-tree -c</a></tt> and
<tt><em>Enabled</em></tt> reveals the state of the tree—see <tt><ahref="66-tree.html">66-tree -E</a></tt>.
For each service the first number found between '()' bracket is the corresponding pid of the service, the type of the service is shown next to it. Finally the name of the service is displayed.
...
...
@@ -163,46 +169,51 @@
<p>The command <tt>sudo 66-info -S -d3 00</tt> displays the following where <em>00</em>
is the name of the service:
<pre>
[00]
00
on tree : boot
status : nothing to display
type : bundle
description : mount filesystem and set the hostname
source : /etc/66/service/boot
source : /etc/66/service/boot/
run at : /run/66/tree/0/boot/servicedirs/00
[contents:2]
└─(0,bundle) 00
├─(0,oneshot) filesystem
└─(0,oneshot) hostname
contents
├─(0,oneshot) filesystem
└─(0,oneshot) hostname
</pre>
</p>
<p>Let's take another example, the command sudo <tt>66-info -S -p5 ntpd</tt> displays the following:
2019-03-01 07:28:15.592154500 adjtimex returns frequency of 0.000000ppm
2019-03-01 07:28:15.601109500 ntp engine ready
2019-03-01 07:28:15.770395500 adjtimex adjusted frequency by 16.428986ppm
2019-03-01 07:28:15.770433500 set local clock to Fri Mar 1 07:28:15 +11 2019 (offset 0.000000s)
2019-03-18 06:50:21.749572500 adjtimex returns frequency of 0.000000ppm
2019-03-18 06:50:21.764241500 ntp engine ready
2019-03-18 06:50:21.847440500 adjtimex adjusted frequency by 16.428986ppm
2019-03-18 06:50:21.847479500 set local clock to Mon Mar 18 06:50:21 +11 2019 (offset 0.000000s)
</pre>
<p> In our case :
<ul>
<li>
<tt>[ntpd] </tt> : name of the service.
<tt>ntpd </tt> : name of the service. Main section where general informations is displayed.
</li>
<li>
<tt>on tree </tt> : service enable on tree root.
...
...
@@ -220,13 +231,22 @@
<tt>source </tt> : origin of the frontend service file used to enable the service.
</li>
<li>
<tt>runat </tt> : location of the service into the scandir.
<tt>run at </tt> : location of the service into the scandir.
</li>
<li>
<tt>dependencies</tt> : dependencies informations section. This section will display a graphical tree on the service dependencies.
</li>
<li>
<tt>scripts</tt> : scripts informations section. This will display the command executed at start and stop process.
</li>
<li>
<tt>start script </tt> : command line executed at start process. If a stop section was set an additionnal field called stop script will be displayed with the corresponding command line executed at stop process.
</li>
<li>
<tt>[dependencies:number] </tt> : number of direct dependencies of the service followed by the dependencies graph.
<tt>environment</tt> : environment informations section. Display the environment variables set at <tt>/etc/66/conf/<service_name></tt> or <tt>$HOME/.66/conf/<service_name></tt> depending of the owner of the process.
<tt>-R </tt> : deletes <em>tree</em>. Can not be undone! This will completely remove the given tree
from the system! You will not be able
to retrieve any information of the deleted <em>tree</em> after deleting it.
to retrieve any information of the deleted <em>tree</em> after deleting it. Services currently running on <em>tree</em> will be bringed down before remove it.
</li>
<li>
<tt>-U </tt> : unsupervise <em>tree</em>. Bring down all services contained into the <em>tree</em> and remove the corresponding directory of the service from the scandir.
</li>
<!-- Rather just say "delete" right away. Shortcuts not always need to be explained with the literal word. It may cause the user to not read further and misinterpret the command as not critical. -->
