Hi, I'm really -1 for disabling panics. if some places use panics but could continue then it's a bug and those places should be fixed. panic may _only_ be used if no recovery possible.
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. they should use gw_assert and we have already --disable-asserts configure option. > > 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. why should you use wrapper script's? see userguide for '-d' and '-P' command options. they are available for _all_ kannel binaries. > > Jon -- Thanks, Alex
