[asterisk-bugs] [Asterisk 0010847]: executing CLI command from command line have bad verbosity

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=10847 
====================================================================== 
Reported By:                atis
Assigned To:                qwell
====================================================================== 
Project:                    Asterisk
Issue ID:                   10847
Category:                   General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     feedback
Asterisk Version:            1.4.10  
SVN Branch (only for SVN checkouts, not tarball releases): N/A  
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             09-28-2007 13:42 CDT
Last Modified:              10-04-2007 11:29 CDT
====================================================================== 
Summary:                    executing CLI command from command line have bad
verbosity
Description: 
I have asterisk running with -vvvd. When i execute command from command
line with "-rx" i get "Verbosity is at least 3" all the times, and
sometimes i get output of CLI for some period (larger when asterisk is
under load).

I would generally expect the "-rx" to have executed with verbosity 0 and
debug 0. If i would want to add some verbosity i would do "-v" and "-d" as
much as i need.

There is option "-m" that is supposed to mute CLI output, but it doesn't
seems to work.


====================================================================== 

---------------------------------------------------------------------- 
 jamesgolovich - 10-04-07 11:29  
---------------------------------------------------------------------- 
I wish the bug was in my patch, then it would be easy to be fixed.  It only
seems to happen sometimes.  Whats happening is the "logger mute silent"
command is getting missed by the main thread.  I suspect a signal is
hitting the process at the same time the read is going on and its getting
passed up.

I'll look into the solution to that, but I fear it won't be a trivial
issue to fix 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
10-04-07 11:29  jamesgolovich  Note Added: 0071463                          
======================================================================