Commit a8be14e9 authored by Eric Vidal's avatar Eric Vidal 💬

update doc

parent b5498454
......@@ -23,7 +23,7 @@
<h2>Interface </h2>
<pre>
66-inservice [ -h ] [ -v verbosity ] [ -c ] [ -o name,intree,status,... ] [ -g ] [ -d depth ] [ -r ] [ -t tree ] [ -p nline ] service
66-inservice [ -h ] [ -v verbosity ] [ -c ] [ -n ] [ -o name,intree,status,... ] [ -g ] [ -d depth ] [ -r ] [ -t tree ] [ -p nline ] <em>service</em>
</pre>
<h2>Options </h2>
......@@ -43,6 +43,9 @@
<li>
<tt>-c&nbsp;</tt>&nbsp;: enable colorization.
</li>
<li>
<tt>-n&nbsp;</tt>&nbsp;: do not display the field name.
</li>
<li>
<tt>-o&nbsp;</tt>&nbsp;: comma separated list of fields to display. If this option is not passed, <tt>66-inservice</tt> will display all fields.
</li>
......@@ -91,6 +94,12 @@
<li>
<tt>depends</tt>&nbsp;: displays the <em>service's</em> dependencies.
</li>
<li>
<tt>optsdepends</tt>&nbsp;: displays the <em>service's</em> optional dependencies.
</li>
<li>
<tt>extdepends</tt>&nbsp;: displays the <em>service's</em> external dependencies.
</li>
<li>
<tt>start</tt>&nbsp;: displays the <em>service's</em> start script.
</li>
......@@ -128,13 +137,15 @@
Live : %%livedir%%/tree/0/boot/servicedirs/00
Depends on : system-hostname mount-run populate-run mount-tmp populate-tmp mount-proc mount-sys
populate-sys mount-dev mount-pts mount-shm populate-dev mount-cgroups
Start script : nothing to display
Stop script : nothing to display
Environment source : environment was not set
Environment file : environment was not set
Log name : logger doesn't exist
Log destination : logger doesn't exist
Log file : logger doesn't exist
Optional depends : None
External depends : None
Start script : None
Stop script : None
Environment source : None
Environment file : None
Log name : None
Log destination : None
Log file : None
</pre>
</p>
<p>
......
......@@ -24,7 +24,7 @@
<h2>Interface </h2>
<pre>
66-intree [ -h ] [ -v verbosity ] [ -l live ] [ -c ] [ -o name,init,enabled,... ] [ -g ] [ -d depth ] [ -r ] tree
66-intree [ -h ] [ -v verbosity ] [ -l live ] [ -c ] [ -n ] [ -o name,init,enabled,... ] [ -g ] [ -d depth ] [ -r ] <em>tree</em>
</pre>
<h2>Options </h2>
......@@ -50,6 +50,9 @@
<li>
<tt>-c&nbsp;</tt>&nbsp;: enable colorization.
</li>
<li>
<tt>-n&nbsp;</tt>&nbsp;: do not display the field name.
</li>
<li>
<tt>-o&nbsp;</tt>&nbsp;: comma separated list of fields to display. If this option is not passed, <tt>66-intree</tt> will display all fields.
</li>
......@@ -76,9 +79,18 @@
<li>
<tt>enabled</tt>&nbsp;: displays a boolean value of the enable state.
</li>
<li>
<tt>start</tt>&nbsp;: displays the list of tree(s) started before.
</li>
<li>
<tt>current</tt>&nbsp;: displays a boolean value of the current state.
</li>
<li>
<tt>allowed</tt>&nbsp;: displays the list of allowed user to use the <em>tree</em>.
</li>
<li>
<tt>symlinks</tt>&nbsp;: displays the target of <em>tree</em>'s symlinks.
</li>
<li>
<tt>contains</tt>&nbsp;: displays the contents of the <em>tree</em>.
</li>
......@@ -89,17 +101,20 @@
<p>The command <tt>66-intree boot</tt>, run as root user, on <em>Obarun's</em> default system displays the following where <em>boot</em>
is the tree used to properly boot the machine:
<pre>
Name : boot
Initialized : yes
Enabled : no
Current : no
Contains : tty12 system-hostname mount-run populate-run mount-tmp populate-tmp mount-proc mount-sys
populate-sys mount-dev mount-pts mount-shm populate-dev mount-cgroups 00 modules-kernel udevd
udevadm devices-crypttab system-hwclock system-random modules-system system-sysctl
system-fontnkey devices-dmraid devices-btrfs devices-lvm devices-zfs system-Devices mount-swap
all-Mount system-fsck mount-fstab all-System mount-rw local-iptables local-ip6tables local-loop
local-sethostname local-time local-authfiles local-tmpfiles local-rc local-dmesg all-Local
all-Runtime All
Name : boot
Initialized : yes
Enabled : no
Starts after : None
Current : no
Allowed : root
Symlinks : svc->source db->source
Contains : tty12 system-hostname mount-run populate-run mount-tmp populate-tmp mount-proc mount-sys
populate-sys mount-dev mount-pts mount-shm populate-dev mount-cgroups 00 modules-kernel udevd
udevadm devices-crypttab system-hwclock system-random modules-system system-sysctl
system-fontnkey devices-dmraid devices-btrfs devices-lvm devices-zfs system-Devices mount-swap
all-Mount system-fsck mount-fstab all-System mount-rw local-iptables local-ip6tables local-loop
local-sethostname local-time local-authfiles local-tmpfiles local-rc local-dmesg all-Local
all-Runtime All
</pre>
</p>
......@@ -112,9 +127,21 @@
<p>
The field <tt><em>Enabled</em></tt> reveals the state of the tree&mdash;see <tt><a href="66-tree.html">66-tree -E</a></tt>.
</p>
<p>
The field <tt><em>Starts after</em></tt> reveals the start process order if the <em>tree</em> is enabled, meaning which <em>tree</em> is started before the current one.
</p>
<p>
The field <tt><em>Current</em></tt> tells you if the <em>tree</em> is the current one or not&mdash;see <tt><a href="66-tree.html">66-tree -c</a></tt>.
</p>
<p>
The field <tt><em>Allowed</em></tt> gives you a list of user(s) allowed to handle the <em>tree</em>&mdash;see <tt><a href="66-tree.html">66-tree -[a|b]</a></tt>.
</p>
<p>
The field <tt><em>Symlinks</em></tt> tells you if the current live state point to the <tt>source</tt> or the <tt>backup</tt> of the <em>tree</em>.
Every use of <tt><a href="66-enable.html">66-enable</a></tt> tool create a automatic backup of the <em>tree</em>
for <tt>classic</tt>,<tt>bundle</tt> or <tt>atomic</tt> service(s). A symlink pointing to <tt>backup</tt> mean that you have enabled a service
without starting it. Right after a boot, each tree should point to <tt>source</tt>.
</p>
<p>
The field <tt><em>Contains</em></tt> gives you a list of all services enabled in the <em>tree</em>.
</p>
......
......@@ -31,7 +31,7 @@
The <em>tree</em> will be handled for the user running the process.
Any <em>tree</em> is completely independent from another. If you
want to know what trees are currently available on the system use
<tt><a href="66-info.html">66-info</a></tt> tool.
<tt><a href="66-intree.html">66-intree</a></tt> tool.
</p>
<h2> Options </h2>
......@@ -75,7 +75,7 @@
<tt>-c&nbsp;</tt>&nbsp;: makes <em>tree</em> the current tree to use by default with other 66 tools. The majority of commands
in the 66 tools suite have a <tt>-t</tt> option to specify the <em>tree</em> to use. By setting
<em>tree</em> as the current one all other 66 tools will use it by default. You can see which
<em>tree</em> is the current one with the <tt><a href="66-info.html">66-info</a></tt> tool.
<em>tree</em> is the current one with the <tt><a href="66-intree.html">66-intree</a></tt> tool.
</li>
<li>
......
<html>
<head>
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<meta http-equiv="Content-Language" content="en" />
<title>The 66 Suite: 66-update</title>
<meta name="Description" content="Detailed documentation for the 66-update command which is part of the 66 software suite" />
<meta name="Keywords" content="66 command 66-update tree supervision format upgrade service" />
<!-- <link rel="stylesheet" type="text/css" href="//skarnet.org/default.css" /> -->
</head>
<body>
<p>
<a href="index.html">66</a><br />
<a href="//obarun.org/">www.obarun.org</a>
</p>
<h1>66-update</h1>
<p>
66-update is a program that is normally used very rarely: when the
66 package is upgraded or downgraded, some services are currently managed,
different tree as declared and the inner format has changed. This program transitions
a complete tree and a live directory using a database with the old 66 format (the one being replaced)
so that it uses a database with the new 66 format and rebuild the tree.
</p>
<p>
The point is to ensure a smooth transition between different versions of 66 without needing a reboot.
</p>
<h2>Interface</h2>
<pre>
66-udpate [ -h ] [ -v <em>verbosity</em> ] [ -c ] [ -l <em>live</em> ] <em>tree</em>
</pre>
<p>
If no tree is given, all trees of the owner of the process will be processed.
</p>
<h2>Options</h2>
<ul>
<li>
<tt><b>-h</b></tt> : print this help.
</li>
<li>
<tt>-v&nbsp;<em>verbosity</em>&nbsp;</tt>: increases/decreases
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 tracing messages.
<tt>4</tt>: Also print debugging messages.
</li>
<li>
<tt><b>&#8209;l&nbsp;<em>live</em></b></tt> : an absolute path. Send the signal to a <em>scandir</em> at <em>live</em>. Default is <tt>%%livedir%%</tt>. The default can also be changed at compile time by passing the <tt>&#8209;&#8209;livedir=<em>live</em></tt> option to <tt>./configure</tt>. Should be available within a writable filesystem - likely a RAM filesystem.
</li>
<li>
<tt>-c&nbsp;</tt>&nbsp;: enable colorization.
</li>
</ul>
<h2>Transition process</h2>
<ul>
<li>
It determines if the tree is already initialized. In such case, it
make a copy of the current database on a temporary directory and
switch the database to it.
</li>
<li>
It saves the current state of the tree (current,enabled,...).
</li>
<li>
It destroys the tree with <tt><a href="66-tree.html">66-tree -R</a></tt> command.
</li>
<li>
It creates the tree with <tt><a href="66-tree.html">66-tree -n(cEa)</a></tt> command,
options depending of the saved state.
</li>
<li>
It enables the service(s) previously declared on the <em>tree</em>.
</li>
<li>
It switch the current database to the newly created by the enable process.
</li>
</ul>
<p>
At the end of the process, the tree and the live state has not changed. Services already is use
are not stopped or restarted during the transition process and match exactly the same state
before and after the process.
</p>
<p>
It try to be safe as possible and exit 111 is a problem occurs. In any case
on upgrade/downgrade time, 66 tools will not work properly if the transition
is not made smoothly even by the sysadmin itself. So, We prefer to cratch instead of
leaving an inconsistent state and let the sysadmin correct the things.
</p>
</body>
</html>
......@@ -16,7 +16,7 @@
<h1>The frontend service file</h1>
<p>
The <a href="https://skarnet.org/software/s6">s6</a> and <a href="https://skarnet.org/software/s6">s6-rc</a> programs each handle and use several kinds of services and different files. It is quite complex to understand and manage the relationship between all those files and services. If you're interested in the details you should read <a href="https://skarnet.org/software/s6/servicedir.html">the documentation for the s6 servicedir</a> and also about <a href="https://wiki.obarun.org/doku.php?id=s6services"><em>classic</em></a>, <a href="https://skarnet.org/software/s6-rc/s6-rc-compile.html"> <em>oneshot</em>, <em>longrun</em> and <em>bundle</em> services</a> on Obarun. The frontend service file of 66 tools allows you to deal with all these different services in a centralized manner in one single place.
The <a href="https://skarnet.org/software/s6">s6</a> and <a href="https://skarnet.org/software/s6">s6-rc</a> programs each handle and use several kinds of services and different files. It is quite complex to understand and manage the relationship between all those files and services. If you're interested in the details you should read <a href="https://skarnet.org/software/s6/servicedir.html">the documentation for the s6 servicedir</a> and also about <a href="https://wiki.obarun.org/doku.php?id=s6services"><em>classic</em></a>, <a href="https://skarnet.org/software/s6-rc/s6-rc-compile.html"> <em>oneshot</em>, <em>longrun</em> (also called <em>atomic</em> services) and <em>bundle</em> services</a> on Obarun. The frontend service file of 66 tools allows you to deal with all these different services in a centralized manner in one single place.
<br>
By default 66 tools expects to find any service files in <tt>%%service_system%%</tt> although this can be changed at compile time by passing the <tt>--with-service-path=<em>DIR</em></tt> option to <tt>./configure.</tt>
</p>
......@@ -37,7 +37,6 @@
<pre> [main]
@type = classic
@name = ntpd
@description = "ntpd daemon"
@user = ( root )
@options = ( log env )
......@@ -290,7 +289,7 @@ MYVALUE</pre>
<h5>Corresponds to the file "<em>dependencies</em>" of s6-rc programs.</h5>
<p>Declare dependencies of the service.</p>
<p><tt>mandatory</tt> : no&#8212;this field has no effect if the
type of the service is "classic"</em>.</p>
type of the service is <em>classic</em>.</p>
<p><tt>syntax</tt> : bracket</p>
<p><tt>valid values</tt> :</p>
<ul>
......@@ -313,7 +312,83 @@ MYVALUE</pre>
to the dependencies of fooA.
</li>
</ul>
</ul>
<li><h4>@optsdepends</h4></li>
<h5>Without equivalent, this key is unique to 66 tools.</h5>
<p>Declare optional dependencies of the service.</p>
<p><tt>mandatory</tt> : no&#8212;this field has no effect if the
type of the service is <em>classic</em> or <em>bundle</em>.</p>
<p><tt>syntax</tt> : bracket</p>
<p><tt>valid values</tt> :</p>
<ul>
<li>The <em>name</em> of any valid service with type
<tt>bundle</tt>, <tt>longrun</tt> or <tt>oneshot</tt>. Services of type <tt>classic</tt>
are not allowed.
A service declared as optional dependencies is not mandatory.
The parser will look at all trees if the corresponding service is
already enabled:
<ul>
<li>If It the case, it warn the user and do nothing.</li>
<li>If not, it tries to find the corresponding frontend file.
<ul>
<li>If the frontend service file is found, it enable it.</li>
<li>If it not found it, it warn the user and do nothing</li>
</ul>
</li>
</ul>
</li>
</ul>
<p>The <em>order is of importance</em> (!). The first service found
will be used and the parse process of the field will be stopped.
So, you can considere @optsdepends field as:
"enable one on this service or none".
</p>
<p>
We talk about enable process here. The start process will not take care
about optional dependencies. If fooA on treeA have an optional dependency fooB which is
declared on treeB, it's the responsability of the sysadmin to start first
treeB then treeA. <tt><a href="66-intree.html">66-intree</a></tt> give you
the order of the start with the field <tt>Start after</tt>.
</p>
<li><h4>@extdepends</h4></li>
<h5>Without equivalent, this key is unique to 66 tools.</h5>
<p>Declare external dependencies of the service.</p>
<p><tt>mandatory</tt> : no&#8212;this field has no effect if the
type of the service is <em>classic</em> or <em>bundle</em>.</p>
<p><tt>syntax</tt> : bracket</p>
<p><tt>valid values</tt> :</p>
<ul>
<li>The <em>name</em> of any valid service with type
<tt>bundle</tt>, <tt>longrun</tt> or <tt>oneshot</tt>. Services of type <tt>classic</tt>
are not allowed.
A service declared as external dependencies is mandatory.
The parser will look at all trees if the corresponding service is
already enabled:
<ul>
<li>If It the case, it warn the user and do nothing.</li>
<li>If not, it tries to find the corresponding frontend file.
<ul>
<li>If the frontend service file is found, it enable it.</li>
<li>If it not found it, the process is stopped and
<a href="66-enable.html">66-enable</a> exit 111.</li>
</ul>
</li>
</ul>
<br>
This process is made for all services declared in the field.
</li>
</ul>
<br>
<p>So, you can considere @extdepends field as:
"enable the service if it not already declared on a tree".
</p>
<p>We talk about enable process here. The start process will not take care
about external dependencies. If fooA on treeA have an external dependency fooB which is
declared on treeB, it's the responsability of the sysadmin to start first
treeB then treeA. <tt><a href="66-intree.html">66-intree</a></tt> give you
the order of the start with the field <tt>Start after</tt>.</p>
<br><hr style="border: 1px dashed #000000">
......@@ -856,7 +931,9 @@ for it in your <tt>@execute</tt> field.</p>
@type = classic,bundle,longrun,oneshot
@name =
@description = ""
@depends = ()
@depends = ()
@optsdepends = ()
@extdepends = ()
@contents = ()
@options = ( log env pipeline )
@flags = ( down nosetsid )
......
......@@ -20,10 +20,10 @@ It is a safe wrapper around *66-start(1)* and *66-stop*(1).
Prints this help.
*-v* _verbosity_
Increases/decreases the verbosity of the command.
- *1* : (Default) Only print error messages.
- *2* : Also print warning messages.
- *3* : Also print tracing messages.
Increases/decreases the verbosity of the command.++
- *1* : (Default) Only print error messages.++
- *2* : Also print warning messages.++
- *3* : Also print tracing messages.++
- *4* : Also print debugging messages.
*-l* _live_
......
......@@ -27,10 +27,10 @@ given _tree_.
Prints this help.
*-v* _verbosity_
Increases/decreases the verbosity of the command.
- *1* : (Default) Only print error messages.
- *2* : Also print warning messages.
- *3* : Also print tracing messages.
Increases/decreases the verbosity of the command.++
- *1* : (Default) Only print error messages.++
- *2* : Also print warning messages.++
- *3* : Also print tracing messages.++
- *4* : Also print debugging messages.
*-l* _live_
......
......@@ -31,10 +31,10 @@ recursively until all dependencies are disabled.
Prints this help.
*-v* _verbosity_
Increases/decreases the verbosity of the command.
- *1* : (Default) Only print error messages.
- *2* : Also print warning messages.
- *3* : Also print tracing messages.
Increases/decreases the verbosity of the command.++
- *1* : (Default) Only print error messages.++
- *2* : Also print warning messages.++
- *3* : Also print tracing messages.++
- *4* : Also print debugging messages.
*-l* _live_
......
......@@ -32,10 +32,10 @@ Multiple _services_ can be enabled by seperating their names with a space.
Prints this help.
*-v* _verbosity_
Increases/decreases the verbosity of the command.
- *1* : (Default) Only print error messages.
- *2* : Also print warning messages.
- *3* : Also print tracing messages.
Increases/decreases the verbosity of the command.++
- *1* : (Default) Only print error messages.++
- *2* : Also print warning messages.++
- *3* : Also print tracing messages.++
- *4* : Also print debugging messages.
*-l* _live_
......
......@@ -25,7 +25,7 @@ It display the contain of the file or replace a _key=value_ pair if requested.
Increases/decreases the verbosity of the command.++
*1* : (Default) Only print error messages.++
*2* : Also print warning messages.++
*3* : Also print tracing messages.
*3* : Also print tracing messages.++
*4* : Also print debugging messages.
*-t* _tree_
......
......@@ -218,6 +218,60 @@ Valid _key_ names:
Corresponds to the file *dependencies* of s6-rc programs.
*@optsdepends*++
Declare optional dependencies of the service.++
_mandatory_: *no*.++
_syntax_: *bracket*++
_valid values_:++
The _name_ of any valid service with type *bundle*, *longrun* or++
*oneshot*. Services of type *classic* are not allowed.
A service declared as optional dependencies is not mandatory.
The parser will look at all trees if the corresponding service is
already enabled:++
If It the case, it warn the user and do nothing.++
If not, it tries to find the corresponding frontend file.++
If the frontend service file is found, it enable it.++
If it not found it, it warn the user and do nothing.
The *order* is of importance. The first service found will be used
and the parse process of the field will be stopped.
So, you can considere *@optsdepends* field as:
"enable one on this service or none".
We talk about enable process here. The start process will not take care
about optional dependencies. If fooA on treeA have an optional dependency fooB which is
declared on treeB, it's the responsability of the sysadmin to start first
treeB then treeA. *66-intree* give you
the order of the start with the field *Start after*.
*@extdepends*++
Declare external dependencies of the service.++
_mandatory_: *no*.++
_syntax_: *bracket*++
_valid values_:++
The _name_ of any valid service with type *bundle*, *longrun* or++
*oneshot*. Services of type *classic* are not allowed.
A service declared as external dependencies is mandatory.
The parser will look at all trees if the corresponding service is
already enabled:++
If It the case, it warn the user and do nothing.++
If not, it tries to find the corresponding frontend file.++
If the frontend service file is found, it enable it.++
If it not found it, the process is stopped and *66-enable* exit 111.
This process is made for all services declared in the field.
So, you can considere @extdepends field as:
"enable the service if it not already declared on a tree".
We talk about enable process here. The start process will not take care
about external dependencies. If fooA on treeA have an external dependency fooB which is
declared on treeB, it's the responsability of the sysadmin to start first
treeB then treeA. *66-intree* give you
the order of the start with the field *Start after*.
*@contents*++
Declare the contents of a bundle service.++
_mandatory_: *yes* for services of type *bundle*; _Optional_ for++
......@@ -706,6 +760,8 @@ This prototype contain all valid *section* with all valid _key_*=*_value_ pair.
@name =
@description = ""
@depends = ()
@optsdepends = ()
@extdepends = ()
@contents = ()
@options = ( log env pipeline )
@flags = ( down nosetsid )
......
......@@ -21,10 +21,10 @@ Administrators should invoke *66-init* only once.
Prints this help.
*-v* _verbosity_
Increases/decreases the verbosity of the command.
- *1* : (Default) Only print error messages.
- *2* : Also print warning messages.
- *3* : Also print tracing messages.
Increases/decreases the verbosity of the command.++
- *1* : (Default) Only print error messages.++
- *2* : Also print warning messages.++
- *3* : Also print tracing messages.++
- *4* : Also print debugging messages.
*-l* _live_
......
......@@ -6,7 +6,7 @@
# SYNOPSYS
66-inservice [ *-h* ] [ *-v* _verbosity_ ] [ *-c* ] [ *-o* _name,intree,enabled,..._ ] [ *-g* ] [ *-d* _depth_ ] [ *-r* ] [ *-t* _tree_ ] [ *-p* _nline_ ] _service_
66-inservice [ *-h* ] [ *-v* _verbosity_ ] [ *-c* ] -[ *-n* ] [ *-o* _name,intree,enabled,..._ ] [ *-g* ] [ *-d* _depth_ ] [ *-r* ] [ *-t* _tree_ ] [ *-p* _nline_ ] _service_
# DESCRIPTION
......@@ -21,12 +21,15 @@
Increases/decreases the verbosity of the command.++
*1* : (Default) Only prints error messages.++
*2* : Also prints warning messages.++
*3* : Also prints tracing messages.
*3* : Also prints tracing messages.++
*4* : Also prints debugging messages.
*-c*
enable colorization.
*-n*
do not display the field name.
*-o*
comma separated list of fields to display. If this option is not passed,
*66-inservice* will display all fields.
......@@ -74,6 +77,12 @@
*depends*
Displays the _service_'s dependencies.
*optsdepends*
Displays the _service_'s optional dependencies.
*extdepends*
Displays the _service_'s external dependencies.
*start*
Displays the _service_'s start script.
......@@ -112,13 +121,15 @@ Depends on : system-hostname mount-run populate-run mount-tmp
populate-tmp mount-proc mount-sys populate-sys
mount-dev mount-pts mount-shm populate-dev
mount-cgroups
Start script : nothing to display
Stop script : nothing to display
Environment source : environment was not set
Environment file : environment was not set
Log name : logger doesn't exist
Log destination : logger doesn't exist
Log file : logger doesn't exist
Optional depends : None
External depends : None
Start script : None
Stop script : None
Environment source : None
Environment file : None
Log name : None
Log destination : None
Log file : None
```
......
......@@ -6,7 +6,7 @@
# SYNOPSYS
66-intree [ *-h* ] [ *-v* _verbosity_ ] [ *-l* _live_ ] [ *-c* ] [ *-o* name,init,enabled,... ] [ *-g* ] [ *-d* _depth_ ] [ *-r* ] _tree_
66-intree [ *-h* ] [ *-v* _verbosity_ ] [ *-l* _live_ ] [ *-c* ] [ *-n* ] [ *-o* name,init,enabled,... ] [ *-g* ] [ *-d* _depth_ ] [ *-r* ] _tree_
# DESCRIPTION
......@@ -21,7 +21,7 @@
Increases/decreases the verbosity of the command.++
*1* : (Default) Only prints error messages.++
*2* : Also prints warning messages.++
*3* : Also prints tracing messages.
*3* : Also prints tracing messages.++
*4* : Also prints debugging messages.
*-l* _live_
......@@ -34,6 +34,9 @@
*-c*
enable colorization.
*-n*
do not display the field name.
*-o*
comma separated list of fields to display. If this option is not passed,
*66-intree* will display all fields.
......@@ -62,9 +65,18 @@
*enabled*
Displays a boolean value of the enable state.
*start*
Displays the list of the tree(s) started before.
*current*
Displays a boolean value of the current state.
*allowed*
Displays the list of allowed user to use the _tree_.
*symlinks*
Displays the target of the _tree_'s symlinks.
*contains*
Displays the contents of the _tree_.
......@@ -75,21 +87,24 @@ displays the following where *boot* is the tree used to properly boot
the machine:
```
Name : boot
Initialized : yes
Enabled : no
Current : no
Contains : tty12 system-hostname mount-run populate-run mount-tmp
populate-tmp mount-proc mount-sys populate-sys mount-dev
mount-pts mount-shm populate-dev mount-cgroups 00
modules-kernel udevd udevadm devices-crypttab
system-hwclock system-random modules-system system-sysctl
system-fontnkey devices-dmraid devices-btrfs devices-lvm
devices-zfs system-Devices mount-swap all-Mount
system-fsck mount-fstab all-System mount-rw local-iptables
local-ip6tables local-loop local-sethostname local-time
local-authfiles local-tmpfiles local-rc local-dmesg all-Local
all-Runtime All
Name : boot
Initialized : yes
Enabled : no
Starts after : None
Allowed : root
Symlinks : svc->source db->source
Current : no
Contains : tty12 system-hostname mount-run populate-run mount-tmp
populate-tmp mount-proc mount-sys populate-sys mount-dev
mount-pts mount-shm populate-dev mount-cgroups 00
modules-kernel udevd udevadm devices-crypttab
system-hwclock system-random modules-system system-sysctl
system-fontnkey devices-dmraid devices-btrfs devices-lvm
devices-zfs system-Devices mount-swap all-Mount
system-fsck mount-fstab all-System mount-rw local-iptables
local-ip6tables local-loop local-sethostname local-time
local-authfiles local-tmpfiles local-rc local-dmesg all-Local
all-Runtime All
```
The field *name* gives you the name of the _tree_.
......@@ -98,9 +113,21 @@ The field *Initialized* tells you if the _tree_ was initialized with "66-init" t
The field *Enabled* reveals the state of the tree -- see "66-tree -E".
The field *Starts after* reveals the start process order if the _tree_ is enabled,
meaning which _tree_ is started before the current one.
The field *Current* tells you if the _tree_ is the current one or not -- see
"66-tree -c".
The field *Allowed* gives you a list of user(s) allowed to handle the
_tree_ -- see "66-tree -[a|b]".
The field *Symlinks* tells you if the current live state point to the
*source* or the *backup* of the _tree_. Every use of "66-enable" tool
create a automatic *backup* of the _tree_ for *classic*,*bundle* or *atomic*
service(s). A symlink pointing to *backup* mean that you have enabled a service
without starting it. Right after a boot, each tree should point to *source*.
The field *Contains* gives you a list of all services enabled in the _tree_.
You can display the contents list as a graph and only these fields using
......
......@@ -22,10 +22,10 @@ An absolute path is expected for _service_ and _destination_.
Prints this help.
*-v* _verbosity_
Increases/decreases the verbosity of the command.
- *1* : (Default) Only print error messages.
- *2* : Also print warning messages.
- *3* : Also print tracing messages.
Increases/decreases the verbosity of the command.++
- *1* : (Default) Only print error messages.++
- *2* : Also print warning messages.++
- *3* : Also print tracing messages.++
- *4* : Also print debugging messages.
*-f*
......