From edefd1073cc3f7777a90c48bb1ddd851ee7edbb6 Mon Sep 17 00:00:00 2001 From: Liviu Chircu Date: Tue, 15 Oct 2019 18:54:00 +0300 Subject: [PATCH] usrloc docs: Fix misleading info on timer behavior (cherry picked from commit 755defe07c743407be61326c5e3a568e26ffce86) --- modules/usrloc/doc/usrloc_admin.xml | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/modules/usrloc/doc/usrloc_admin.xml b/modules/usrloc/doc/usrloc_admin.xml index 022164b7da6..93f8e930ba6 100644 --- a/modules/usrloc/doc/usrloc_admin.xml +++ b/modules/usrloc/doc/usrloc_admin.xml @@ -691,15 +691,16 @@ modparam("usrloc", "desc_time_order", 1)
<varname>timer_interval</varname> (integer) - Number of seconds between two timer runs. The module uses timer to - delete expired contacts, synchronize with database and other tasks, - that need to be run periodically. + Number of seconds between two timer runs. During each run, the module + will update/delete dirty/expired contacts from memory and/or mirror + these operations to the database, if configured to do so. - In case of crash or restart contacts that are in memory only and - haven't been flushed yet will get lost. If you want minimize the - risk, use a shorter timer interval. + In case of an OpenSIPS shutdown or even a crash, contacts which are in + memory only and have not been flushed yet to disk will NOT get lost! + OpenSIPS will try its best to do a last-minute sync to DB right before + shutting down.