On Sunday, November 10, 2002, at 11:32 AM, John Delacour wrote:
At 8:18 am -0600 10/11/02, Puneet Kishor wrote:PS. I've installed Apache2 and mod-perl after again installing Perl 5.8.0 ŕ la Morbus. Where do I put my CGI executables? I obviously need to configure Apache somehow.put it anywhere... it doesn't matter as long as you have the path set in httpd.conf. Or, better yet, just leave it where it is... probably under apache2/cgi-bin. Keep in mind, "CGI Executables" is just Apple's ungainly name for "cgi-bin". In other words, take what you have under your old "CGI Executables" and move it under cgi-bin, make sure that directory has execute permissions for the user under which apache2 runs, and set the correct settings in httpd.conf, namely ExecCGI+ under the cgi-bin <Directory> segment.Thanks. I've got things working after a fashion but only by having the directory at /cgi-bin/ -- in fact I've put an alias there to a folder in my sites folder, but the effect is the same. The main thing is that in spite of two installs of Apache2 by the Morbus method and by using httpd-2.0.43.tar.gz, I still have Apache 1.3.7 serving everything. Various attempt I've made to change jd.conf have all resulted in web sharing refusing to start. I really haven't a clue what I'm doing. I'm able to test my cgis now, but the set-up is clearly unsatisfactory and I can find very little guidance on the web.
go to your web-sharing doo-hickey in the Systems Prefs and turn off web-sharing. That way the Apple apache WILL NOT be in the picture at all. Out, kaput.
Now, you have to either start your custom apache2 manually, or set-up a start-up script. Depending on where you have installed apache2 (lets assume /usr/local/apache2) you will find a script called apachectl in the bin folder (/usr/local/apache2/bin/apachectl). Run apachectl --help and you will see its options. Typically you use "apachectl start" or "apachectl restart" or "apachectl graceful". Make sure you run the apachectl that is installed under your new apache2. Apache2 is not likely to be in the path, so it may get steamrolled by an earlier apachectl somewhere in the path. You can either modify your path so the apache2/bin comes first, or you can run the correct apachectl directly. Once you get it going the way you want it, you can figure out how to create a start-up script that you can either call by adding it to your login items in the System Prefs, or figuring out where the start-up scripts go (there might be something like init.d in Jagwyre, but I am not sure).
When you refer to jd.conf, that is just your user conf file, and is usually called by inclusion in the apache's httpd.conf file. You can add the same statement in your new apache2's httpd.conf so your jd.conf is called from within that.
Check the apache docs... it is quite well explained actually.
Hth.
