> > > > Apache::Registry already looks for changes to your scripts and > reloads > > them as necessary. So you shouldn't need to use both of them. > > Well, I agree it says that, but when I tried using Registry without > Reload, > it didn't seem to work, so I gave up, and used Reload, more-or-less > successfully. >
Registry checks whether your script has changed: - eg cgi-bin/login.pl But if login.pl contains 'use My::Module', it doesn't check for that module, which is why you would need Apache::Reload as well. > So, I would, for instance, have a .pl file which contains > ... > use lib "."; # I believe this is implicit, anyway. > use CCC::MyDBI; > ... This is one of the gotchas I mentioned before: CHDIR. You can't rely on it. Something somewhere (maybe Registry itself) is changing the current dir, so '.' now refers to / rather than to /path/to/your/modules. Change that to : use lib '/path/to/your/modules'; and it should work. Re a virtual server solution - I've been looking for one as well. Here are a few I've found (haven't tried them yet): http://order.1and1.co.uk/xml/order/VpsRoot?__frame=_top&__lf=Static http://www.spry.com/plesk-vps/ http://www.vpslink.com/ Good luck. When you get to grips with these issues, you'll end up loving Perl. Clint
