configs: Move sample config files into a subdirectory of configs

This moves all samples configs from configs/ to configs/samples. This allows
for additional sets of sample configuration files to be added in the future.

Review: https://reviewboard.asterisk.org/r/3804/


git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@418870 65c4cc65-6c06-0410-ace0-fbb531ad65f3

1 files changed, 0 insertions, 31 deletions

diff --git a/configs/res_config_sqlite3.conf.sample b/configs/res_config_sqlite3.conf.sample
deleted file mode 100644
index 5416c809e..000000000
--- a/configs/res_config_sqlite3.conf.sample
+++ /dev/null
@@ -1,31 +0,0 @@
-; Define a realtime database name to use in extconfig.conf
-;
-;[asterisk]
-;dbfile => /var/lib/asterisk/realtime.sqlite3
-;
-; debug - Turn on debugging information
-;debug=yes
-;
-; requirements - At startup, each realtime family will make requirements
-;   on the backend.  There are several strategies for handling requirements:
-;     warn        - Warn if the required column does not exist.
-;     createclose - Create columns as close to the requirements as possible.
-;     createchar  - Create char columns only
-;
-;requirements=warn
-;
-; batch - SQLite 3 write performance can be greatly improved by wrapping
-;   multiple writes in transactions. This option specifies the duration in
-;   milliseconds of auto-generated transactions. Any changes made during an
-;   unfinished transaction will be immediately available to the same database
-;   connection, but any external connections could see a delay up to the value
-;   of this setting. It is also possible that if asterisk crashes, any changes
-;   made during this time could be lost. Due to the nearly 100x performance
-;   benefit, the default is 100 ms. Set to 0 to disable batching.
-;
-;   PLEASE NOTE: If you need to write to the database from another connection
-;   you will need to set batch=0 as the transactions will cause the database
-;   to lock for writing.
-;
-;batch=1000
-