On Tuesday 25 January 2005 12:39, Andrew Kohlsmith wrote: > On January 25, 2005 12:57 pm, Brian West wrote: > > No its not a bug.. it will always do that if you start it with -c > > It's not a bug that enabling colour will "allow" asterisk to die with > ^C, ^S?? If it's not a bug then why does ^C, ^S, etc. not cause * to > die? > > i.e. why does enabling colour enable these particular crashes? This > doesn't seem to be the kind of "undocumented feature" that is > conducive to a good environment. :-)
c is for console, not for color (see the output of 'asterisk -h'). As the process is running in the foreground, Ctrl-C naturally interrupts the foreground process. Note that if you start asterisk in the background (i.e. without the -c option or with a startup script), then connect to it with -r or -R, Ctrl-C will not exit the main asterisk process, but only the remote console. Here ends the -user lesson on the -dev list. -- 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
