<p><em>file</em> is a text file containing lines of the form <tt>key = value</tt>.Whitespace is permitted before and after <em>key</em>, and before or after <em>value</em>,
<p><em>file</em> is a text file containing lines of the form <tt>key = value</tt>.Whitespace is permitted before and after <em>key</em>, and before or after <em>value</em>,
Quoting is also possible. In this case, the quoting field is treated as one word.
</p>
<p>Empty lines, or lines containing only whitespace, are ignored. Lines beginning with <tt>#</tt> (possibly after some whitespace) are ignored (and typically used for comments). Comments are <strong>not</strong> possible at the end of lines:
starts—see <tt><ahref="66-scandir.html">66-scandir -u</a></tt> option, the already present services start automatically.</p>
<p>If the <em>scandir</em> is running, you should invoke a <tt><ahref="66-scandir.html">66-scandir -s reload</a></tt> command to inform it about the changes.</p>
where, by default, <em>live</em> translates to <tt>/run/66/tree/UID/<em>tree</em></tt> and <em>compiled</em> to <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 on the owner of the process and the <em>prefix</em> of the name of the <em>tree</em>. If it doesn't exist yet <em>live</em>
is created in the process. For these services the <em>scandir</em><strong>must</strong> be running. This tool like any other 66 tool can be invoked with user permissions.</p>