Differences

This shows you the differences between two versions of the page.

--- devel:blueprints:smsd-retry-backoff [2009/03/03 14:46] – created morten
+++ devel:blueprints:smsd-retry-backoff [2009/06/08 12:01] (current) – Misspelling jorabra
@@ Line 8: / Line 8: @@
   * For each completely failed dispatch attempt, the retry delay will increase by a factor X.
-  * Factor X must be configurable in ''smsd.conf''
+  * If Y>0, once Y repeated dispatch attempts have been unsuccessful, smsd must choose one of the following scenarios:
-  * Once Y repeated dispatch attempts have been unsuccessful, smsd will give up and ignore the remaining messages.
+    * If Z is disabled, all queued messages must be marked with //status=ignored//.  A CRITICAL error must be logged, containing details of all the ignored messages.  SMSD must then resume its normal queue-checking loop.
-    * When smsd gives up, this should be logged as a CRITICAL error, and details of the ignored messages should be logged along with it (so the admin can see what they just missed).
+    * If Z is enabled, a CRITICAL error must be logged.  The error message must contain the number of unsent messages, and the age of the oldest mesasge.  The daemon process must then shut down.
-  * The value of Y must be configurable in ''smsd.conf''
+  * If Y=0, the daemon must continue its dispatch attempts indefinitely.
+    * Once the loop delay reaches the value M, exactly _one_ CRITICAL error must be logged, containing the number of unsent messages and the age of the oldest message.  The error message must specify that the daemon will continue to retry dispatch.  The loop delay must never increase above M.
+  * Values M, X, Y and Z must be configurable in ''smsd.conf''