> I would say: this is pretty impossible! Nobody imposes any known set of
> config options to the underlying implemntation so the implementation
> cannot
> do any "sanity" checks beside basic type-checking.
> You can pretty much say:
>
> ns_section milly/vanilly
> ns_param fate 1
But the point is: At a certain stage the server has finished reading all
configuration options. You would be able to detect that
ns_section milly/vanilly
is a section you have no knowledge of or no use for:
"unknown config section"
This is of course only true when it is really not used, e.g. at a later point
in time by an "external" TCL module.
If, during startup, a configuration value is requested for the first time, the
value OR the default value is set. This knowledge is buried in the C call:
nsconf.shutdowntimeout =
Ns_ConfigIntRange(path, "shutdowntimeout", 20, 0, INT_MAX);
A list of all options, btw., is created then the server logs debug notices.
As it is possible to list all options of all sections (from C and TCL), at the
end I can detect config options that I did not request and set during
startup.
Therefor I can lookup if the options belong to other sections or if the
options are unknown in a section or totally unknown.
This should be possible! The question is, if it makes sense, as only options
are detected that are requested and set during startup and TCL module ones
will be missing.
Bernd.
