[asterisk-bugs] [Asterisk 0015953]: [patch] sqlite3 CDRs not working after a reload

Asterisk Bug Tracker noreply at bugs.digium.com
Thu Sep 24 08:57:53 CDT 2009


The following issue has been UPDATED. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15953 
====================================================================== 
Reported By:                frawd
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   15953
Category:                   CDR/cdr_sqlite3_custom
Reproducibility:            have not tried
Severity:                   feature
Priority:                   normal
Status:                     ready for review
Asterisk Version:           SVN 
JIRA:                        
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-09-24 08:03 CDT
Last Modified:              2009-09-24 08:57 CDT
====================================================================== 
Summary:                    [patch] sqlite3 CDRs not working after a reload
Description: 
A module reload calls free_config() which sqlite3_closes the db, preventing
CDRs to be logged there until next full restart.

Unfortunately the sqlite3_open is only done on load.

Patch adds a reload option to free_config to prevent it from closing the
sqlite3 db handler. I only tried it on my backport for 1.4, not on trunk.
====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-09-24 08:57 lmadsen        Description Updated                          
======================================================================




More information about the asterisk-bugs mailing list