Re: keeping include: from overriding directives in the config

Neal Richter wrote:

> Interesting idea.
> 
> One solution to this would be to build a quick PHP script that would 
> allow users to manipulate the setting you want them
>  to then save them in the htdig.conf  file.

but then PHP (IE usually "nobody" (pronounced *everybody*) has to have 
write access to it which means anyone can change anything they want)

Something that important needs done by a real language with less 
security exploits, IMHO

> At one time someone build a PHP wrapper for configuring htdig.. this 
> would be a good starting point.  I can't seem to find the code.. yet.

No need for any sort of special editor or interface, just in the config 
file they do not have write access to does it need to be A or B:

a) if htdig uses the first instance of it then I need to specify it first:

   whatever: they shouldn't be able to change this
   include: their/file


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?


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
ht://Dig general mailing list: <[email protected]>
ht://Dig FAQ: http://htdig.sourceforge.net/FAQ.html
List information (subscribe/unsubscribe, etc.)
https://lists.sourceforge.net/lists/listinfo/htdig-general