[asterisk-dev] Asterisk 11 configuration files

Paul Belanger paul.belanger at polybeacon.com
Sun Aug 26 14:35:32 CDT 2012


On 12-08-26 07:18 AM, Tzafrir Cohen wrote:
> On Fri, Aug 24, 2012 at 10:11:16AM -0400, Russell Bryant wrote:
>> On Thu, Aug 23, 2012 at 10:35 PM, Paul Belanger
>> <paul.belanger at polybeacon.com> wrote:
>>> I'm slowly starting to testing Asterisk 11 and noticed something about our
>>> new modules config file names:
>>>
>>> chan_motif.so -> motif.conf
>>>
>>> and
>>>
>>> res_corosync.so -> res_corosync.conf
>>> res_xmpp.so -> xmpp.conf
>>>
>>> When chan_dahdi was rewritten we moved to chan_dahdi.conf. Should we do the
>>> same for chan_motif -> chan_motif.conf?
>>>
>>> Same for res_xmpp, we should move it to res_xmpp.conf.  This would line up
>>> with the majority of resource modules config file names.  Like we did for
>>> res_corosync.conf.
>>>
>>> Thoughts?
>>
>> +1 from me.  I like the module name == config file name convention and
>> think all new modules with config files should follow it.
>
> I must point out I still don't like that new convention and prefer
> 'motif.conf'. Module names are a mostly internal implementation detail. On the
> asterisk CLI, do you have 'chan_motif' or 'motif'?
>
I'm not sure I would refer to it as new, the mixture of config file 
names has been around since Asterisk 0.2.0 (cdr_mysql.conf). With 
Asterisk 1.0.0 we did even more.

-- 
Paul Belanger | PolyBeacon, Inc.
Jabber: paul.belanger at polybeacon.com | IRC: pabelanger (Freenode)
Github: https://github.com/pabelanger | Twitter: 
https://twitter.com/pabelanger



More information about the asterisk-dev mailing list