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

i did something wrong :/...

parent cbfdcd92
......@@ -329,16 +329,16 @@ MYVALUE</pre>
The parser will look at all trees if the corresponding service is
already enabled:
<ul>
+ <li>If enabled, it will warn the user and do nothing.</li>
+ <li>If not, it will try to find the corresponding frontend file.
+ <ul>
+ <li>If the frontend service file is found, it will enable it.</li>
+ <li>If it is not found, it will warn the user and do nothing.</li>
+ </ul>
+ </li>
+ </ul>
+ </li>
+</ul>
<li>If enabled, it will warn the user and do nothing.</li>
<li>If not, it will try to find the corresponding frontend file.
<ul>
<li>If the frontend service file is found, it will enable it.</li>
<li>If it is not found, it will warn the user and do nothing.</li>
</ul>
</li>
</ul>
</li>
</ul>
<p>The <em>order is important</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:
......@@ -346,10 +346,10 @@ MYVALUE</pre>
</p>
<p>
@optsdepends only affects the enable process. The start process will not consider
+ optional dependencies. If fooA on treeA has an optional dependency fooB which is
+ declared on treeB, it's the responsibility of the sysadmin to start first
+ treeB then treeA. <tt><a href="66-intree.html">66-intree</a></tt> can give you
+ the start order with the field <tt>Start after</tt>.
optional dependencies. If fooA on treeA has an optional dependency fooB which is
declared on treeB, it's the responsibility of the sysadmin to start first
treeB then treeA. <tt><a href="66-intree.html">66-intree</a></tt> can give you
the start order with the field <tt>Start after</tt>.
</p>
<li><h4>@extdepends</h4></li>
......@@ -363,32 +363,32 @@ MYVALUE</pre>
<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 an external dependencies is mandatory.
+ The parser will search through all trees whether the corresponding service is
A service declared as an external dependencies is mandatory.
The parser will search through all trees whether the corresponding service is
already enabled:
<ul>
+ <li>If enabled, it will warn the user and do nothing.</li>
+ <li>If not, it will try to find the corresponding frontend file.
+ <ul>
+ <li>If the frontend service file is found, it will enable it.</li>
+ <li>If not, the process is stopped and
+ <a href="66-enable.html">66-enable</a> exits 111.</li>
+ </ul>
+ </li>
+ </ul>
<li>If enabled, it will warn the user and do nothing.</li>
<li>If not, it will try to find the corresponding frontend file.
<ul>
<li>If the frontend service file is found, it will enable it.</li>
<li>If not, the process is stopped and
<a href="66-enable.html">66-enable</a> exits 111.</li>
</ul>
</li>
</ul>
<br>
This process is made for all services declared in the field.
</li>
</ul>
<br>
<p>So, you can consider @extdepends field as:
+ "enable the service if it is not already declared on a tree".
"enable the service if it is not already declared on a tree".
</p>
<p>@extdepends only affects the enable process. The start process will not consider
+ external dependencies. If fooA on treeA has an external dependency fooB which is
+ declared on treeB, it's the responsibility of the sysadmin to start first
+ treeB then treeA. <tt><a href="66-intree.html">66-intree</a></tt> will give you
+ the start order with the field <tt>Start after</tt>.</p>
external dependencies. If fooA on treeA has an external dependency fooB which is
declared on treeB, it's the responsibility of the sysadmin to start first
treeB then treeA. <tt><a href="66-intree.html">66-intree</a></tt> will give you
the start order with the field <tt>Start after</tt>.</p>
<br><hr style="border: 1px dashed #000000">
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment