Hello there, Didn't see any reply to this.
On Tue, 18 Nov 2003, Tim wrote: > I believe I installed apache 1.3.29 and mod_perl incorrectly using > > $ ./configure --prefix=PREFIX Do you mean you used the literal text "PREFIX"? > Assuming I want to start over, how does one go about wiping them off first? Well I guess you don't have to do very much. The main thing to watch out for when you install something like this on Linux is that your PATH and your filesystem layout don't conspire to get you using the wrong version(s) of packages that you've just installed yourself. The other thing to watch out for is that when you install Apache, if it finds existing configuration files (which would probably be somewhere like /usr/local/apache/conf) it will refuse to overwrite them. Now in your cirumstances you might in fact want it to overwrite them, so you could (logged in as root) start with the command which apachectl to find where the apachectl script is hiding, always assuming that the script is in a directory on your PATH. It might not be. Note that apachectl is not the Apache binary, that's called 'httpd' just to confuse everybody. It's short for "HTTP daemon". apachectl is the program that feeds configuration info. etc. to httpd although you can start httpd with all the switches it needs from the command line or from your own script if you want to. You can use the apachectl script to find the httpd binary then it will start and which configuration files it uses when it runs. Then delete them all, including the script and the binary. If you have a directory /usr/local/apache then if you don't have any configuration files or logs that you need to keep, you can delete the entire apache directory and all contents (but not of course anything else in /usr/local). If you don't have an existing Apache on the machine that you're at all concerned about keeping, just use the 'find' command to find any file called 'httpd' and delete it. If you have an httpd binary somewhere like /usr/sbin or /usr/local/sbin then you can delete that but do NOT delete the directory! Just the httpd. If you're worried about deleting things in case there's some reason they might actually be needed later, just rename them (or the directory they're in, but again not if it's .../sbin) and make a note of what you've done so you can later put it back like it was if you want to. I often rename a file by adding the date it was created to the end of its original name, httpd becomes httpd-2003.11.21 for example and I can have several of them, chosing from amongst them which one I want to run at the time by using a symlink ln -s httpd-2003.11.21 httpd in this case. There's another little wrinkle, in that Apache can be built for static or dynamic mod_perl (and most other modules), so a lot of what's said above applies to the mod_perl module if it's dynamically loaded. My advice is to steer well clear of dynamically loaded mod_perl, if you build mod_perl statically linked into Apache you won't have to worry about having an old version of the module lying around because it won't be used, at least until you forget about it and build mod_perl as a DSO sometime in the distant future. Of course by then you'll be much more conversant with all this stuff and it won't faze you at all. :) Get back to us if you're still not sure about things. 73, Ged. -- Reporting bugs: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html
