[Dnsmasq-discuss] extension of configuration files

Michael Rack dnsmasq.list at michaelrack.de
Sun Jul 5 17:15:06 BST 2009

I think, there is a really easy solution:

conf-dir should expect a expression at the end. Or a new attribute have 
to be added like "include".

In Apache you can say

	include /etc/httpd/conf.d/*.conf

now i am very flexible to include as many patterns as i need.


Am 05.07.2009 17:41, schrieb Simon Kelley:
> Rance Hall wrote:
>> On Sun, Jul 5, 2009 at 7:56 AM, Helmut Hullen<Hullen at t-online.de>  wrote:
>>> Hallo, RevRagnarok,
>>> Du meintest am 05.07.09 zum Thema Re: [Dnsmasq-discuss] extension of configuration files:
>>>>> Could dnsmasq exclude *.new files from reading? Some other programs
>>>>> do so.
>>>> By extension, it should probably just ignore everything not *.conf,
>>>> since other package managers use other methods, e.g. .rpmnew and
>>>> .rpmold.
>>> Sounds reasonable.
>>> Please keep the traffic in the mailing list!
>>> Viele Gruesse!
>>> Helmut
>>> _______________________________________________
>>> Dnsmasq-discuss mailing list
>>> Dnsmasq-discuss at lists.thekelleys.org.uk
>>> http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
>> I think this is a great idea but I don't think it belongs in dnsmasq
>> proper.  I think it makes the code base bigger for no real feature
>> gain.  This is something that could be handled  in an init script
>> stanza prior to actually launching dnsmasq.
>> set a variable for the main config file
>> parse it looking for config_dir
>> if found, check contents for updated scripts (test will be different
>> for each distro I suspect)
>> mv the updated files to config_dir.update
>> start dnsmasq the normal way
>> If you did this in the init script then it would be much more flexible
>> for per distro variations.
>> Personally, I've never seen a distro actually populate the config_dir
>> usually its commented out of the  main config file
>> Its ultimately up to Simon, but I've seen other comments from him that
>> indicate code size is important for him as he knows that dnsmasq is
>> used in embedded devices.  I don't see embedded devices benefiting
>> from this change.
> I'd be in a stronger position to refuse to do this if the code didn't
> already weed out filenames which look like .file and file~ and #file#.
> I'm an emacs user and those last two are emacs droppings. I guess the
> problem is knowing _which_ files should be ignored ( how many
> conventions are there?) and not ignoring files which someone, somewhere,
> thinks are perfectly OK and should be used.
> Cheers,
> Simon.
> _______________________________________________
> Dnsmasq-discuss mailing list
> Dnsmasq-discuss at lists.thekelleys.org.uk
> http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss

More information about the Dnsmasq-discuss mailing list