From: Matthew Jordan Date: Thu, 16 Oct 2014 21:13:08 +0000 (+0000) Subject: main/cdr: Use 'time' when rescheduling batched CDRs as opposed to 'size' X-Git-Tag: 12.7.0-rc1~42 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=90bd7988c34936fe6063ef04ab5cb9da0b40ab1a;p=thirdparty%2Fasterisk.git main/cdr: Use 'time' when rescheduling batched CDRs as opposed to 'size' When refactoring CDRs to use the configuration framework, a 'whoops' was introduced where the CDR batch size was used when rescheduling a batch, as opposed to the time duration. This patch corrects that obvious mistake. ASTERISK-24426 #close Reported by: Shane Blaser git-svn-id: https://origsvn.digium.com/svn/asterisk/branches/12@425735 65c4cc65-6c06-0410-ace0-fbb531ad65f3 --- diff --git a/main/cdr.c b/main/cdr.c index f6d6e36d7d..921c789b5e 100644 --- a/main/cdr.c +++ b/main/cdr.c @@ -3520,7 +3520,7 @@ static int submit_scheduled_batch(const void *data) /* manually reschedule from this point in time */ ast_mutex_lock(&cdr_sched_lock); - cdr_sched = ast_sched_add(sched, mod_cfg->general->batch_settings.size * 1000, submit_scheduled_batch, NULL); + cdr_sched = ast_sched_add(sched, mod_cfg->general->batch_settings.time * 1000, submit_scheduled_batch, NULL); ast_mutex_unlock(&cdr_sched_lock); /* returning zero so the scheduler does not automatically reschedule */ return 0;