On Sun, 28 Dec 2003, bruce wrote:
> basically, we need to be able to install a small apache footprint on a Check out the (dynamic) modules and/or a static compile using hte confoigure API (do a ./configure --help for a list). You can strip it down very very far. > number of servers. we'd like the apache apps to communicate back/forth with > a master app to access any config information. (ie, we don't want the apache > app to read the traditional httpd.conf file) .. > has anyone any knowledge of any app that's modified apache to do this. Using the cmdline -c and -C you can configure apache a little 'on the fky' - note that you can repeat them. Problem is - you still need an empty set of CONFIG_FILE's, such as httpd.conf. So the trick is at Make or configure time is to use the -D overrides of TYPES_CONFIG_FILE, SERVER_CONFI_FILE, etc. and point htem to /dev/null. I've done several in-memory config's for specific projects in the past, occasionally tieing it in to SNMP - but this is rarely waranted - writing out a (temporary) httpd.conf file again-and-again is not that hard. And feel free to moan tha t it is not proper SNMP or BNF parsable :-) Dw
