(of course this is a loaded question) some problems with invoking httpd directly with Apache 2.0:
a. from an Apache binary build: busted, since it won't find libapr et al (if you use a Bourne-compatible shell you can source the envvars file and it will work) b. from a build done locally from source: httpd loads fine but any special environment variable settings from envvars are lost; the examples in CVS currently are that on AIX and OS/390 Apache won't be able to get many threads without the envvar override (as above, if you use a Bourne-compatible shell you can source the envvars file and it will work) The apxs and apachectl shell scripts deal with this by sourcing the envvars file (that's why it is there, actually). If httpd were a shell script that sourced the envvars file and ran something else (e.g., httpd.bin) then apxs and apachectl wouldn't have to do any dirty work and direct invocations of httpd would work just as well as apachectl. #!/bin/sh . sbindir/envvars sbindir/httpd.bin $* It is ugly for httpd to be a shell script, but it is also ugly to get different results based on how Apache was built and what OS you're on and so forth. If httpd is to be left as-is on Unix (i.e., maybe it works maybe it doesn't), then perhaps apachectl needs to be pushed as the way to access all httpd functionality. (I loathe this stuff, but is going to be more important as 2.0.x settles in and we have more users of binary builds.) -- Jeff Trawick | [EMAIL PROTECTED] Born in Roswell... married an alien...
