On Thu, Feb 4, 2010 at 9:48 PM, <[email protected]> wrote: > Author: poirier > Date: Fri Feb 5 02:48:34 2010 > New Revision: 906779 > > URL: http://svn.apache.org/viewvc?rev=906779&view=rev > Log: > Be specific about which environment variables can be used in > expansions in the server configuration file. > > Modified: > httpd/httpd/trunk/docs/manual/configuring.xml > > Modified: httpd/httpd/trunk/docs/manual/configuring.xml > URL: > http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/configuring.xml?rev=906779&r1=906778&r2=906779&view=diff > ============================================================================== > --- httpd/httpd/trunk/docs/manual/configuring.xml (original) > +++ httpd/httpd/trunk/docs/manual/configuring.xml Fri Feb 5 02:48:34 2010 > @@ -87,6 +87,12 @@ > unchanged for use by later stages in the config file > processing.)</p> > > + <p>Only environment variables defined before the server is started > + can be used in expansions. Variables defined in the > + configuration file itself, for example with <directive > + module="mod_env">SetEnv</directive>, take effect too late to be > + used for expansions in the configuration file.</p>
I think the "take effect too late..." wording supports the common confusion that OS-level environment variables and those server variables that are set in the environment of sub-processes are essentially the same thing. I don't know what the magic distinguishing words are. Perhaps "OS environment variable," with a link to a new glossary entry, should be used in the appropriate places? The glossary entry for Environment variable describes the difference but doesn't introduce unique terminology for the two types of variables (http://httpd.apache.org/docs/2.2/glossary.html#environmentvariable. Make sense?
