add note on how you can't replace the sqlite3 database file while powerdns is running...

diff --git a/docs/backends/generic-sqlite3.rst b/docs/backends/generic-sqlite3.rst
index d04e4f3272e9d651c9ca301696f5e7d4c2b6ac4d..d3904921da97d8105b814313306e405256b55268 100644 (file)
--- a/docs/backends/generic-sqlite3.rst
+++ b/docs/backends/generic-sqlite3.rst
@@ -13,7 +13,7 @@ Generic SQLite 3 backend
 
 .. warning::
   When importing large amounts of data, be sure to run
-  ``analyze;`` afterwards as SQLite3 has a tendency to use sub-optimal
+  ``analyze;`` afterwards as SQLite3 has a tendency to use very sub-optimal
   indexes otherwise.
 
 This backend retrieves all data from a SQLite database, which is an
@@ -40,6 +40,12 @@ with data. The default setup conforms to the following schema:
 This schema contains all elements needed for master, slave and
 superslave operation.
 
+.. warning::
+  It is not possible to replace the sqlite3 database file while PowerDNS is
+  running. Specifically, using ``rsync`` to distribute sqlite3 databases
+  does not work without stopping PowerDNS first and restarting it after the
+  change.
+
 After you have created the database you probably want to fill it with
 data. If you have a BIND zone file it's as easy as:
 ``zone2sql --named-conf=/path/to/named.conf --gsqlite | sqlite3 powerdns.sqlite3``,