Commit d906dc88 authored by mobinmob's avatar mobinmob

frontend.html doc fixes

parent 02df3326
......@@ -328,28 +328,28 @@ MYVALUE</pre>
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
<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:
"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>.
@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>.
</p>
<li><h4>@extdepends</h4></li>
......@@ -366,29 +366,29 @@ MYVALUE</pre>
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>
<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 considere @extdepends field as:
<p>So, you can consider @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>
<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>
<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