[asterisk-bugs] [Asterisk 0013844]: CLI non-responsive

Thu Nov 13 10:03:23 CST 2008

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=13844 
====================================================================== 
Reported By:                qualleyiv
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   13844
Category:                   General
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.6.0.1 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2008-11-06 00:04 CST
Last Modified:              2008-11-13 10:03 CST
====================================================================== 
Summary:                    CLI non-responsive
Description: 
I just moved from the latest 1.4 build to 1.6.0.1. For some reason, the
command line interface doesn't seem to respond to any commands other than
quit. For example if I type: "Core set verbose 20" all I get is: 

mail*CLI>
====================================================================== 

---------------------------------------------------------------------- 
 (0094848) qualleyiv (reporter) - 2008-11-13 10:03
 http://bugs.digium.com/view.php?id=13844#c94848 
---------------------------------------------------------------------- 
Sure, I'm on Mac OS X Server 10.5.5, PowerPC. Sorry for not responding
sooner, I wanted to check a couple of things first, but now I'm pretty sure
I've ironed out all of the stuff that I thought might be a problem. Just
FYI, one thing I tried was this: previously, I was launching Asterisk with
Launchd using the -pg option. I noticed that this threw this error: "Mac OS
X detected. Use '/sbin/launchd -d' to launch with the nofork option."

I'm certainly no expert on Launchd (who is, after all) but as far as I can
gather, that command won't actually work, instead, I tried changing my
Launchd Plist file to use the -fp option (not sure that the -p option
really does anything on my system, but from what I gather the -f option
would be equivalent to nofork). I really don't know. If I'm wrong please
correct me. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-11-13 10:03 qualleyiv      Note Added: 0094848                          
======================================================================