Yes. --disable-panics should be only a stopgap. One truly must know what messages are causing the panics. It actually can be just an error of the phone .
On 16.3.2005, at 17:52, Jonathan Houser wrote:
Aarno,
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.
I would like it if a panic just wrote the appropriate lines to the log (for debugging) and kept on running. The panic's I've seen were for things that pertained to a WDP message from some phone on the WAP gateway. If that one phone doesn't get his fetch handled, oh well, we should log that we had a problem and keep on running. So I like the idea you've proposed. It'd allow everyone to work through issues without having a wrapper script work overtime.
Jon
