There actually seems to two kinds of panic:
a) Configuration errors. In this case, continuation really is impossible.
b) Libs has some sanity checks that cause panic. If we just have a broken
message, we must just ignore message, not panic.
Aarno
On 16.3.2005, at 15:02, Pommnitz, J�rg wrote:
Uhh, isn't a panic supposed to be a condition where there is no recovery? Restarting Kannel might be a better option for production use than a system with an untrustworthy internal state. To propose an alternative: How about auditing all panics to make sure they really represent a condition with no way out opposed to just a programmer too lazy to unwind a complicated code flow?
Regards Joerg
-----Urspr�ngliche Nachricht----- Von: Aarno Syv�nen [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 16. M�rz 2005 14:57 An: Kannel list Betreff: [RFC] --disable-panics configuration option
Hi List,
can we add --disable-panics configuration option ? it would mean that Kannel would log panic level error, but would not exit. This would be very good for production use.
In addition, I think that --with-defaults options other than debug should disable panics too.
Aarno
