[Asterisk-Dev] is this a bug?

[Eric Wieling]

Andrew Kohlsmith wrote:

> On January 25, 2005 12:59 pm, Steven Critchfield wrote:
> 
>>Ctrl-c is actually an interupt. Windows users needed easy to remember
>>shortcuts, thats why you are used to ctrl-c.
> 
> 
> Yes but why does ^C only interrupt asterisk when -c (colour) is given?  To me 
> this is a bug.  Asterisk should either always trap these key sequences or 
> always pass them, irrespective of your desire to see coloured console 
> messages.

As you can see -c means CONSOLE, not COLOR.

[root at fs-1 root]# asterisk -rh
Asterisk CVS-v1-0-12/08/04-11:02:07, Copyright (C) 2000-2004, Digium.
Usage: asterisk [OPTIONS]
Valid Options:
    -V              Display version number and exit
    -C <configfile> Use an alternate configuration file
    -G <group>      Run as a group other than the caller
    -U <user>       Run as a user other than the caller
    -c              Provide console CLI
    -d              Enable extra debugging
    -f              Do not fork
    -g              Dump core in case of a crash
    -h              This help screen
    -i              Initializie crypto keys at startup
    -n              Disable console colorization
    -p              Run as pseudo-realtime thread
    -q              Quiet mode (supress output)
    -r              Connect to Asterisk on this machine
    -R              Connect to Asterisk, and attempt to reconnect if 
disconnected
    -t              Record soundfiles in /tmp and move them where they 
belong after they are done.
    -v              Increase verbosity (multiple v's = more verbose)
    -x <cmd>        Execute command <cmd> (only valid with -r)