Hi there, On Wed, 4 Sep 2002, Jon Harris wrote:
> I inherited a very happy cobalt raq3 with 2 sites using embedded Perl > which work very well. There are about 20 sites on the box. I needed to > get PHP running on the same box, so I made the module, added it into the > httpd.conf and PHP was working fine - Except that it broke the perl sites. ( Disclaimer: I don't use PHP. :) Check out the mod_perl List archives, a number of people are doing this kind of thing and there was a thread very recently about it. You may perhaps find you need to compile a new Apache (static linking instead of DSO), but it's no big deal. But I'd first check those archives, and maybe make sure that I'd used the same compiler for the PHP module build as was used for Apache and mod_perl. It's worth checking the options used as well, things like large file support can cause problems if they're not the same for each build. I don't know if there are any issues with the versions of the various bits of software you're using, there might be. Perl 5.005 is getting a little long in the tooth now, and you didn't say which Apache 1.3 you have, there are lots of them... I wouldn't expect the problem to be related to EmbPerl but you never know. There's an EmbPerl site, check out the mod_perl home page for the address, but Gerald Richter reads the posts here too. And yes, it sometimes does matter what order you do things in - you might find that the order of loading modules is important - but I don't know of any particular problem with the modules you mentioned. You could make a completely new Apache just to test things and run it as a separate server, not listening to port 80 but to some other port. There are lots of useful pointers to doing things like this in the Guide, the mod_perl home page will lead you there too. 73, Ged.
