Re: [htdig] keeping include: from overriding directives in the config

[JupiterHost.Net <ml...@ju...>]

>> b) if htdig uses the last instance of it then I need to specify it last
>> to override anything they put in:
>>
>>   include: their/file
>>   whatever: they shouldn't be able to change this
>>
>> Which way would make it so that even if they specified "whatever:" it 
>> woudl still use the "whatever:" in the main config that they do not 
>> have access to?
>>
>>
> 
>  From the definition of "include" at <http://www.htdig.org/confindex.html>
> 
> "The last definition of an attribute is the one that applies, so after 
> including a file, any of its definitions can be overridden with 
> subsequent definitions. This can be useful when setting up many 
> configurations that are mostly the same, so all the common attributes 
> can be maintained in a single configuration file. The include directives 
> can be nested, but watch out for nesting loops."
> 
> So, according to that, anything you do not want the user to be able to 
> change would need to be after the include statement, which would be 
> option "B" above.

Excellent! Exactly what I'd been looking for :) although that text isn't 
at that url for me, weird??

> This paragraph does bring up the interesting point of what could happen 
> if the user adds an include that references the main config file:
> 
> common.conf -> include: user.conf
> user.conf -> include: common.conf
> 
> I don't know exactly how that would manifest itself, but I imagine it 
> wouldn't be a good thing.

Good point, I'll have to consider that as well. At least a big fiery 
warning that says:
  You will 100% guaranteed break your config if you include: the 
configuration file that uses this file.

Thanks again Kurt!