Jeff Trawick wrote: > Justin Erenkrantz <[EMAIL PROTECTED]> writes: > > >>On Fri, Dec 14, 2001 at 01:18:54PM -0500, Jeff Trawick wrote: >> >>>Hmmm... I don't see them as analogous. >>> >>>This script is for use by apachectl to pick up environment variable >>>settings required for httpd to work. On most platforms, this would >>>just have LIBPATH/LD_LIBRARY_PATH/whatever. On some platforms this >>>would have settings which affect pthreads or heap management or >>>whatever. >>> >>I guess what I'm suggesting is to generalize this so that it has >>a whole bunch of variables - rather than just this one. I can >>definitely see how this would make writing scripts around httpd-2.0 >>that much easier. This script could tell you which port httpd is >>configured to run on, etc, etc, etc (currently apachectl has a >>separate port number setting for status than in the config value). >>Almost like apxs -q but more standardized. >> > > What your talking about sounds cool, but not for this. This file is > for settings that admins can edit/tune as necessary. If tweaking > these settings requires that you go into the guts of some general > mechanism for querying the way Apache was built then that is no better > than having to edit stuff embedded in apachectl. > > I would think that apr-config and httpd-config are not for settings > that admins might need to tune so that apr httpd works correctly. >
On this not I'd like to add a $HTTPARGS which gets passed to the server at start/restart this way you can set all the -DXXXX in it, and not modify the apachectl script. ..I
