summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorFabien Marotte <fabienx.marotte@intel.com>2010-08-18 15:56:45 +0200
committerSamuel Ortiz <sameo@linux.intel.com>2010-08-18 15:57:41 +0200
commit6029951606b0cf55194593082d4e5e1fe69763a6 (patch)
tree2baafac98e3260d7a56ae20049a6fea67ef4740c /doc
parent4b48dd39d9c1f219e7791b59ca113bc229c25c55 (diff)
downloadconnman-6029951606b0cf55194593082d4e5e1fe69763a6.tar.gz
connman-6029951606b0cf55194593082d4e5e1fe69763a6.tar.bz2
connman-6029951606b0cf55194593082d4e5e1fe69763a6.zip
Add configuration file naming rules to documentation
In case the user provides configuration files to connman, the file name must respect some rules.
Diffstat (limited to 'doc')
-rw-r--r--doc/config-format.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/config-format.txt b/doc/config-format.txt
index 94248960..9e9eee6d 100644
--- a/doc/config-format.txt
+++ b/doc/config-format.txt
@@ -3,8 +3,8 @@ Connman configuration file format
Connman uses configuration files to provision existing services. Connman will
be looking for its configuration files at STORAGEDIR which by default points
-to /var/lib/connman/. Configuration file names should follow the *.config
-pattern.
+to /var/lib/connman/. Configuration file names must not include other
+characters than letters or numbers and must have a .config suffix.
Those configuration files are text files with a simple format and we typically
have one file per provisioned network.