<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to Configuration</title><link>https://sourceforge.net/p/flom/wiki/Configuration/</link><description>Recent changes to Configuration</description><atom:link href="https://sourceforge.net/p/flom/wiki/Configuration/feed" rel="self"/><language>en</language><lastBuildDate>Thu, 05 Mar 2020 21:03:37 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/flom/wiki/Configuration/feed" rel="self" type="application/rss+xml"/><item><title>Configuration modified by Christian Ferrari</title><link>https://sourceforge.net/p/flom/wiki/Configuration/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v2
+++ v3
@@ -1,3 +1,4 @@
+This page is no more maintained, the current one is at http://www.tiian.org/flom/Configuration.html
 # Flom configuration #
 Flom uses a cascading configuration principle: every parameter is inspected in 5 different locations and the last occurrence overloads the previous ones.
 Every time flom starts, it looks for parameters following this order:
&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Christian Ferrari</dc:creator><pubDate>Thu, 05 Mar 2020 21:03:37 -0000</pubDate><guid>https://sourceforge.net846860993eca2f67416fd067c70ff27c4e6eb209</guid></item><item><title>Configuration modified by Christian Ferrari</title><link>https://sourceforge.net/p/flom/wiki/Configuration/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v1
+++ v2
@@ -4,7 +4,7 @@

 1. hard wired values: they are inside source code and are ever available
 2. system default config file: if you didn't change it at *configure time* (command *configure* before command *make*), the standard location would be **/usr/local/etc/flom.conf**; if you changed installation paths, you should determine where **flom.conf** file must be put
-3. user default config file: file **.flom** searched inside directory described by environment var **HOME** or by **/etc/passwd** content if **$HOME** is not set
+3. user default config file: file **.flom** searched inside directory described by environment var **$HOME** or by **/etc/passwd** content if **$HOME** is not set
 4. user custom config file: a custom file you specify using "-c" ("--config-file") command line argument
 5. specific command line arguments like "-r" ("--resource-name")

&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Christian Ferrari</dc:creator><pubDate>Sat, 04 Jan 2014 12:09:21 -0000</pubDate><guid>https://sourceforge.nete7dc7c74c58a130d55af3597f1e95178ad5152cd</guid></item><item><title>Configuration modified by Christian Ferrari</title><link>https://sourceforge.net/p/flom/wiki/Configuration/</link><description>&lt;div class="markdown_content"&gt;&lt;h1 id="flom-configuration"&gt;Flom configuration&lt;/h1&gt;
&lt;p&gt;Flom uses a cascading configuration principle: every parameter is inspected in 5 different locations and the last occurrence overloads the previous ones.&lt;br /&gt;
Every time flom starts, it looks for parameters following this order:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;hard wired values: they are inside source code and are ever available&lt;/li&gt;
&lt;li&gt;system default config file: if you didn't change it at &lt;em&gt;configure time&lt;/em&gt; (command &lt;em&gt;configure&lt;/em&gt; before command &lt;em&gt;make&lt;/em&gt;), the standard location would be &lt;strong&gt;/usr/local/etc/flom.conf&lt;/strong&gt;; if you changed installation paths, you should determine where &lt;strong&gt;flom.conf&lt;/strong&gt; file must be put&lt;/li&gt;
&lt;li&gt;user default config file: file &lt;strong&gt;.flom&lt;/strong&gt; searched inside directory described by environment var &lt;strong&gt;HOME&lt;/strong&gt; or by &lt;strong&gt;/etc/passwd&lt;/strong&gt; content if &lt;strong&gt;$HOME&lt;/strong&gt; is not set&lt;/li&gt;
&lt;li&gt;user custom config file: a custom file you specify using "-c" ("--config-file") command line argument&lt;/li&gt;
&lt;li&gt;specific command line arguments like "-r" ("--resource-name")&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;System default file, user default config file, user custom config file &lt;strong&gt;must&lt;/strong&gt; adhere to the same syntax; an example file is available at &lt;strong&gt;/usr/local/share/doc/flom/flom.conf&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;Using configuration files is not mandatory, you can specify every parameter using command line arguments; many times it's more convenient to store a set of parameters inside a configuration file and use command line arguments for the remaining parameters.&lt;br /&gt;
The suggestion is to copy &lt;strong&gt;/usr/local/share/doc/flom/flom.conf&lt;/strong&gt; to the desired destination (/usr/local/etc/flom.conf, $HOME/.flom, &lt;em&gt;my_flom_conf_file&lt;/em&gt;) and customize it as necessary.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Christian Ferrari</dc:creator><pubDate>Sat, 04 Jan 2014 12:05:36 -0000</pubDate><guid>https://sourceforge.netbf3e9458f661a619cce1ea0ff1184bef3ab0d8dd</guid></item></channel></rss>