[asterisk-bugs] [Asterisk 0013611]: no warning message returned when soxmix is not installed

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=13611 
====================================================================== 
Reported By:                gincantalupo
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   13611
Category:                   Resources/res_monitor
Reproducibility:            always
Severity:                   trivial
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.4.22 
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-10-03 07:40 CDT
Last Modified:              2008-10-06 07:42 CDT
====================================================================== 
Summary:                    no warning message returned when soxmix  is not
installed
Description: 
ast_safe_system() in ast_monitor_stop function does not return -1 if soxmix
is not installed, so no warning message is shown (0 is returned instead).
Not tried with sox.
Asterisk version is 1.4.22 rc5
====================================================================== 

---------------------------------------------------------------------- 
 (0093207) seanbright (manager) - 2008-10-06 07:42
 http://bugs.digium.com/view.php?id=13611#c93207 
---------------------------------------------------------------------- 
The check for sox in the configure script is flawed, as are the
conditionals in res_monitor. While in most cases the build system and
target system are the same, sometimes they are not. So finding sox or
soxmix at configure time is relatively meaningless.  I'm going to leave
this open for now and assign it to myself and see if I can't come up with a
workable solution. Any change to 1.4 at this point will only address the
return value passed back from ast_safe_system.  Hopefully we can have a
more elegant solution in trunk/1.6.2. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-10-06 07:42 seanbright     Note Added: 0093207                          
======================================================================