Don't hit Ctrl-C!

If I type ? in the CLI, Ctrl-C is not listed as a command.
*CLI>
!           abort       add         ael         agent       agi         cdr
database    debug       dnsmgr      dont        dump        dundi       
extensions
feature     group       help        iax2        include     indication  init
load        local       logger      meetme      mgcp        mixmonitor  moh
no          pri         realtime    reload      remove      restart     rtp
set         show        sip         skinny      soft        stop        unload
zap

The funny thing is that neither is exit.

Type exit when exiting asterisk CLI, and it will close out properly.







-- 
-- 
Steven

http://www.glimasoutheast.org



"Todd- Asterisk" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED]
> short version:  me too
>
> long version:  The same thing happens on my asterisk boxes - both  built with 
> the latest trixbox image...  perhaps that's a 
> factor?  My  history is always "restart now", although I typically connect 
> and run  "sip show peers".  I haven't typed "restart 
> now" in a long time, but  that is the first thing when I hit up-arrrow upon 
> connecting....
>
> I have had history written to when I type 'exit' at the console  instead of 
> ctrl-c.   I haven't tested though as the school bus 
> just  arrived....  ;)
>    Todd
>
>
> On Dec 11, 2006, at 3:35 PM, Douglas Garstang wrote:
>
>>> -----Original Message-----
>>> From: Aaron Daniel [mailto:[EMAIL PROTECTED]
>>> Sent: Monday, December 11, 2006 12:57 PM
>>> To: asterisk-users@lists.digium.com
>>> Subject: Re: [asterisk-users] CLI History
>>>
>>>
>>> On Mon, 2006-12-11 at 11:17 -0800, Carla Schroder wrote:
>>>> On Monday 11 December 2006 9:31 am, Douglas Garstang wrote:
>>>>> What's wrong with the Asterisk CLI history? When I exit
>>> the CLI, and
>>>>> re-enter, the last command in the history always defaults
>>> to 'stop now'.
>>>>> This is very bad, and it's caused accidental shutdowns
>>> more than once.
>>>>>
>>>>> Connected to Asterisk 1.2.9.1 currently running on hera
>>> (pid = 17399)
>>>>> Verbosity is at least 3
>>>>> hera*CLI> A
>>>>> No such command 'A' (type 'help' for help)
>>>>> hera*CLI> B
>>>>> No such command 'B' (type 'help' for help)
>>>>> hera*CLI> C
>>>>> No such command 'C' (type 'help' for help)
>>>>> hera*CLI> D
>>>>> No such command 'D' (type 'help' for help)
>>>>> hera*CLI> E
>>>>> No such command 'E' (type 'help' for help)
>>>>> hera*CLI>
>>>>> [10:[EMAIL PROTECTED](pbx3):~]# asterisk -trv
>>>>> Asterisk 1.2.9.1, Copyright (C) 1999 - 2006 Digium, Inc.
>>> and others.
>>>>> Created by Mark Spencer <[EMAIL PROTECTED]>
>>>>> Asterisk comes with ABSOLUTELY NO WARRANTY; type 'show
>>> warranty' for
>>>>> details. This is free software, with components licensed
>>> under the GNU
>>>>> General Public License version 2 and other licenses; you
>>> are welcome to
>>>>> redistribute it under certain conditions. Type 'show
>>> license' for details.
>>>>>
>>> ==============================================================
>>> ===========
>>>>> Connected to Asterisk 1.2.9.1 currently running on hera
>>> (pid = 17399)
>>>>> Verbosity is at least 3
>>>>> hera*CLI> stop now <-- I pressed the UP arrow upon
>>> re-entering the console!
>>>>>
>>>>
>>>>  I'm a bit confused by your example. What are A,B,C, etc?
>>> To exit the Asterisk
>>>> console, I type 'exit'. Asterisk continues to run, as it
>>> should. To re-enter
>>>> the console I use asterisk -rvvv.
>>>>
>>> He was demonstrating how the CLI history shows stop now as the last
>>> command (which um... it's a history?  you're last command is gonna be
>>> the um... last command you ran... i.e. "stop now").
>>
>> For crying out loud, why is this so hard to understand? It isn't  rocket 
>> science. I said that when I exit the CLI and re-enter, 
>> no  matter what my previous set of commands was, when I hit the UP  arrow 
>> key, it was always 'stop now'. 'Stop now' WAS NOT MY 
>> PREVIOUS  COMMAND.
>>
>> For the person that suggested maybe unknown commands are not added  to the 
>> history...
>>
>> hera*CLI> show channels
>> Channel              Location             State   Application(Data)
>> 0 active channels
>> 0 active calls
>> hera*CLI> sip show channels
>> Peer             User/ANR    Call ID      Seq (Tx/Rx)  Form   Hold     Last 
>> Message
>> 0 active SIP channels
>> hera*CLI>
>> (I Pressed Ctrl-c here)
>>
>> [13:[EMAIL PROTECTED](pbx3):~]# asterisk -trv
>> Asterisk 1.2.9.1, Copyright (C) 1999 - 2006 Digium, Inc. and others.
>> Created by Mark Spencer <[EMAIL PROTECTED]>
>> Asterisk comes with ABSOLUTELY NO WARRANTY; type 'show warranty'  for 
>> details.
>> This is free software, with components licensed under the GNU  General Public
>> License version 2 and other licenses; you are welcome to  redistribute it 
>> under
>> certain conditions. Type 'show license' for details.
>> ====================================================================== ===
>> Connected to Asterisk 1.2.9.1 currently running on hera (pid = 18149)
>> Verbosity is at least 3
>> hera*CLI> stop now (I pressed the up arrow key here)
>>
>> As you can see, my previous commands where 'show channels' and 'sip  show 
>> channels'. When I exited the CLI and re-entered and 
>> pressed  ctrl-c, the commands in the history where not 'show channels and  
>> 'sip show channels' but 'stop now' instead.
>>
>> Doug.
>>
>>
>> _______________________________________________
>> --Bandwidth and Colocation provided by Easynews.com --
>>
>> asterisk-users mailing list
>> To UNSUBSCRIBE or update options visit:
>>    http://lists.digium.com/mailman/listinfo/asterisk-users
>>
>
> _______________________________________________
> --Bandwidth and Colocation provided by Easynews.com --
>
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-users
> 



_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Reply via email to