[asterisk-dev] asterisk.conf options override command-line options.

Corey Farrell git at cfware.com
Mon May 4 13:55:23 CDT 2015

I've discovered that any option set in asterisk.conf cannot be overridden
using the command-line.  For example, if you have verbose=0 in
asterisk.conf, 'asterisk -cvvvvvvv' will start with verbose 0.  The same
goes for -f / nofork or -F / alwaysfork.

The only way to fix this is to change the behaviour.  My concern for
release branches is that someone could be running an init script that sets
one option, and they are currently overriding it in asterisk.conf.

Should this be fixed in 11 or 13?  Is anyone against fixing it in master?

JIRA Ticket: https://issues.asterisk.org/jira/browse/ASTERISK-25042
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-dev/attachments/20150504/9a494ec6/attachment.html>

More information about the asterisk-dev mailing list