| Summary: | ASTERISK-05635: Asterisk crashes if zapata.conf no exist or configured for not instaled hardware | ||
| Reporter: | Radek Kochlewski (falkinhan) | Labels: | |
| Date Opened: | 2005-11-17 17:56:41.000-0600 | Date Closed: | 2011-06-07 14:00:36 |
| Priority: | Critical | Regression? | No |
| Status: | Closed/Complete | Components: | Core/Configuration |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ( 0) no_zapata_conf_full.log ( 1) wrong_zapata_conf_full.log ( 2) zapata.conf | |
| Description: | Asterisk crashes if there is not zapata.conf or zapata is configured for hardware removed from the machine. ****** STEPS TO REPRODUCE ****** delete zapata.conf and restart asterisk ****** ADDITIONAL INFORMATION ****** asterisk is compiled with make dont-optimize and started with -g core dump is nor generated problem is not so big, but I don't like crashes too (asterisk working better then gated) | ||
| Comments: | By: Mark Spencer (markster) 2005-11-17 19:01:41.000-0600 Improper zapata.conf settings mean that Asterisk cannot (and should not) load. This behavior is intended. It doesn't crash, it simply exits cleanly. | ||