Return-Path: Delivered-To: apmail-modperl-archive@apache.org Received: (qmail 90884 invoked by uid 500); 4 Nov 2001 21:46:09 -0000 Mailing-List: contact modperl-help@apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Delivered-To: mailing list modperl@apache.org Received: (qmail 90873 invoked from network); 4 Nov 2001 21:46:09 -0000 X-Authentication-Warning: mail.montaseri.net: medi owned process doing -bs Date: Sun, 4 Nov 2001 14:35:04 -0800 (PST) From: Medi Montaseri X-Sender: medi@mail.montaseri.net To: modperl@apache.org Subject: mod_perl alias directories Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N I have successfully installed mod_perl and am using it. I have two question. 1- Currently I have designated a /pm directory to contain my mod_perl codes, a collection of classes. I then have instances of these launched from non /pm directory. I did this so that I don't have to be back at cgi-bin perdicament where all my CGIs are in one directory. I never liked that style. But I'm still forced to put my base classes in /pm. Is there a way to instruct HTTP that perl code in any directory should be used as mod_perl similar to ExecCGI. Or perhaps for a better/cleaner approach, any perl code with some extension such as foo.cgi-mp or foo.cmp (Cgi-Mod-Perl). 2- I currently have to restart my HTTP for changes to my mod_perl code take affect. Is there any way so I don't have to do this. I can see that this is not going to work in a large organization where IT handles the production web servers. Thanks -- ------------------------------------------------------------------------- Medi Montaseri medi@CyberShell.com Unix Distributed Systems Engineer HTTP://www.CyberShell.com CyberShell Engineering -------------------------------------------------------------------------