[asterisk-bugs] [JIRA] (ASTERISK-27846) Fix OUTPUT directory in ast_coredumper

[Ted G (JIRA)]

Ted G created ASTERISK-27846:
--------------------------------

             Summary: Fix OUTPUT directory in ast_coredumper
                 Key: ASTERISK-27846
                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27846
             Project: Asterisk
          Issue Type: Improvement
      Security Level: None
          Components: Addons/General
    Affects Versions: 15.3.0
            Reporter: Ted G
            Severity: Minor


The OUTPUTDIR functionality seems to be broken in ast_coredumper:

gz/tmp# /var/lib/asterisk/scripts/ast_coredumper
OUTPUTDIR /some/directory doesn't exists or is not a directory

gz/tmp# /var/lib/asterisk/scripts/ast_coredumper /tmp/core
OUTPUTDIR /some/directory doesn't exists or is not a directory

gz/tmp# export OUTPUTDIR=/tmp ; echo $OUTPUTDIR
/tmp

gz/tmp# /var/lib/asterisk/scripts/ast_coredumper /tmp/core
OUTPUTDIR /some/directory doesn't exists or is not a directory

gz/tmp# asterisk -V
Asterisk 15.3.0

Looks like the problem is ast_debug_tools.conf is taking precedence over the environment setting.

[ -f /etc/asterisk/ast_debug_tools.conf ] && source /etc/asterisk/ast_debug_tools.conf
[ -f ~/ast_debug_tools.conf ] && source ~/ast_debug_tools.conf
[ -f ./ast_debug_tools.conf ] && source ./ast_debug_tools.conf

This doesn't seem like the appropriate behavior to me.  The user should be able to change the output directory on the command line and not have to edit a config file every time. Also, it seems like /tmp should be the default directory instead of /some/directory which would probably never exist.



--
This message was sent by Atlassian JIRA
(v6.2#6252)