[asterisk-bugs] [Asterisk 0018134]: Missing error message from System() app, if sh binary is missing

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=18134 
====================================================================== 
Reported By:                Bernd
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   18134
Category:                   Applications/app_system
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     ready for testing
Asterisk Version:           1.6.2.13 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-10-13 10:09 CDT
Last Modified:              2010-10-14 06:45 CDT
====================================================================== 
Summary:                    Missing error message from System() app, if sh
binary is missing
Description: 
Asterisk was run in a change root using chroot. The System() calls from the
dialplan ended with $SYSTEMSTATUS = APPERROR. No error message about a
missing sh binary was given, making it hard to debug the error.
This problem should appear not only when using chroot, but everytime the
sh binary could not be found (for some reason).
====================================================================== 

---------------------------------------------------------------------- 
 (0128011) davidw (reporter) - 2010-10-14 06:45
 https://issues.asterisk.org/view.php?id=18134#c128011 
---------------------------------------------------------------------- 
Firstly, it seems to me, especially given that the standard libc equivalent
doesn't do anything very special in this case, that this is a feature
request, not a bug.

Secondly, ast_log is being run in a new process, and a different address
space.  I think that will mean that any interlocking that prevents log
messages getting interleaved will not be effective.  There may be other
weird race conditions, e.g. during log rolling. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-10-14 06:45 davidw         Note Added: 0128011                          
======================================================================