On Tuesday 25 January 2005 13:13, Tom Ivar Helbekkmo wrote: > "Brian West" <[EMAIL PROTECTED]> writes: > > No its not a bug.. it will always do that if you start it with -c > > I beg to differ. An interactive system like this, with a command > line, and command line editing using control characters, should NEVER > crash on a ^C. It would be polite for it to respond to ^C with a > message telling the user to "stop now" to exit the program. Oh, and > even if you insist that it must be ^C killable, it shouldn't be doing > what it does anyway: it's obviously trying to handle the interrupt, > and failing at it, and dying with an ill mem ref. If that's not a > bug, I don't know what is. :-)
Anybody who runs a daemon process in the foreground under an xterm window from Windows should expect Ctrl-C to interrupt their process. Now the fact that the interrupt doesn't generate "pretty" behavior is not germane to the fact that you're running Asterisk in a manner which is highly likely to cause Asterisk to exit when you close the window. You're not running Asterisk in an optimal situation to begin with; so why nitpick Ctrl-C? -- Tilghman _______________________________________________ Asterisk-Dev mailing list [email protected] http://lists.digium.com/mailman/listinfo/asterisk-dev To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
