User Tools

Site Tools


devel:blueprints:smsd-retry-backoff

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
devel:blueprints:smsd-retry-backoff [2009/06/04 14:18]
morten clarified some points of the spec
devel:blueprints:smsd-retry-backoff [2009/06/08 12:01] (current)
jorabra Misspelling
Line 10: Line 10:
   * If Y>0, once Y repeated dispatch attempts have been unsuccessful,​ smsd must choose one of the following scenarios:   * If Y>0, once Y repeated dispatch attempts have been unsuccessful,​ smsd must choose one of the following scenarios:
     * 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.     * 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.
-    * If Z is disabled, 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.+    * 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.
   * If Y=0, the daemon must continue its dispatch attempts indefinitely.  ​   * 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.     * 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''​   * Values M, X, Y and Z must be configurable in ''​smsd.conf''​
  
devel/blueprints/smsd-retry-backoff.1244125087.txt.gz ยท Last modified: 2009/06/04 14:18 by morten