* James Cox ([EMAIL PROTECTED]) wrote : > no! no! leave apachectl to behave as it always has done. could someone > consider vetoing this argument based on backwards compatibility? > > -- James Agreed - why do we need this many layers of indirection? what does it buy us having apachectl call a script that calls httpd? apachectl is supposed to _control_ apache - it reads and defines the environment as necessary, and runs the binary. putting that stuff in a seperate script seems pointless and unfriendly. It also makes problems harder to debug, as it adds another layer where problems can arrise. Cheers, -Thom
- Re: cvs commit: httpd-2.0 STATUS Justin Erenkrantz
- Re: cvs commit: httpd-2.0 STATUS Jeff Trawick
- Re: cvs commit: httpd-2.0 STATUS Cliff Woolley
- Re: cvs commit: httpd-2.0 STATUS Jeff Trawick
- Re: cvs commit: httpd-2.0 STATUS Greg Ames
- Re: cvs commit: httpd-2.0 STATUS Cliff Woolley
- Re: cvs commit: httpd-2.0 STATUS rbb
- Re: cvs commit: httpd-2.0 STATUS Brian Pane
- Re: cvs commit: httpd-2.0 STATUS Thom May
- RE: cvs commit: httpd-2.0 STATUS James Cox
- Re: cvs commit: httpd-2.0 STATUS Thom May
- Re: cvs commit: httpd-2.0 STATUS Jeff Trawick
- Re: cvs commit: httpd-2.0 STATUS Thom May
- Re: cvs commit: httpd-2.0 STATUS Jeff Trawick
- RE: cvs commit: httpd-2.0 STATUS James Cox
- Re: cvs commit: httpd-2.0 STATUS Jeff Trawick
- RE: cvs commit: httpd-2.0 STATUS James Cox
- httpd-2.0.39 won't compile Dev Zero G Ltd
- Re: cvs commit: httpd-2.0 STATUS Greg Ames
- Re: cvs commit: httpd-2.0 STATUS Brian Pane
- Re: cvs commit: httpd-2.0 STATUS Brian Pane