[asterisk-bugs] [JIRA] (ASTERISK-25042) asterisk.conf options override command-line options.

[Corey Farrell (JIRA)]

Corey Farrell created ASTERISK-25042:
----------------------------------------

             Summary: asterisk.conf options override command-line options.
                 Key: ASTERISK-25042
                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-25042
             Project: Asterisk
          Issue Type: Bug
      Security Level: None
          Components: Core/Configuration
    Affects Versions: 13.3.2, 11.17.1, SVN
            Reporter: Corey Farrell
            Severity: Minor


Command-line parameters are processed before {{asterisk.conf}} is read.  This causes asterisk to go against the expectation that any command-line options will override configured options.

For example, if your {{asterisk.conf}} contains:
{noformat}
[options]
verbose=0
debug=0
{noformat}

Then run {{asterisk -cvvvddd}}, you will see that your verbose and debug are set to 0:
{noformat}
*CLI> core set verbose 3
Console verbose was OFF and is now 3.
*CLI> core set debug 3
Core debug was OFF and is now 3.
{noformat}

A few exceptions exist, but for the most part if you set something in {{asterisk.conf}}, the equivalent command-line option will do nothing.

I'm fairly confident the current behaviour of Asterisk is wrong, but I'm not sure if it's OK to fix in 11/13.  I'm can patch this, I'd just like guidance on what versions it should be applied to.  The possible issue I can see is if an init script uses an unwanted option, and an admin has used {{asterisk.conf}} to override it.



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