Sean Bright
authored
There has been an open issue against cdr_syslog (ASTERISK~14441) about a race condition for 7.5 years that has never been addressed. Because this module is effectively unmaintained and currently broken, there is no sense in keeping it around. If logging CDRs to syslog is a desirable feature, it would probably be better to write the logs directly to the syslog server via socket instead of using the facilities provided by openlog/syslog/closelog. Doing so would address the race condition referenced in the associated issue. Change-Id: Ic77b94cd97f355a9cf5b1d3f3444964a6e0ba5dc
| Name | Last commit | Last update |
|---|---|---|
| .. | ||
| Makefile | ||
| cdr_adaptive_odbc.c | ||
| cdr_beanstalkd.c | ||
| cdr_csv.c | ||
| cdr_custom.c | ||
| cdr_manager.c | ||
| cdr_odbc.c | ||
| cdr_pgsql.c | ||
| cdr_radius.c | ||
| cdr_sqlite.c | ||
| cdr_sqlite3_custom.c | ||
| cdr_syslog.c | ||
| cdr_tds.c | ||