Nice try. Unfortunately, helpless... Don't you see two instances of mod_perl in common perl libraries? That's just flowers... When I try to make install, for example
# make install Writing /usr/local/lib/perl5/site_perl/5.6.1/sun4-solaris/auto/Apache/Filter/.packli st Appending installation info to /usr/local/lib/perl5/5.6.1/sun4-solaris/perllocal.pod Funny? Not for me... Best regards, Slava ----- Original Message ----- From: "Ged Haywood" <[EMAIL PROTECTED]> To: "Slava Bizyayev" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Friday, April 05, 2002 3:51 PM Subject: Re: sun4-solaris polluted installation > Hi there, > > On Fri, 5 Apr 2002, Slava Bizyayev wrote: > > > I have to (re)install mod_perl enabled Apache on prod server, which > > is polluted with the several previous unsuccessful attempts [snip] > > Actually, I need somebody very experienced with the sun4-solaris > > environment to assist me carefully on this slippery road... > > It's not that difficult. You can build another Apache with mod_perl > and run it on the same machine without having any effect at all on the > existing server, which can continue to run as normal. All you have to > do is to configure the new server to listen to a port other than port > 80 (to which presumably your production server is currently listening) > and you can play with your new server until you get it to do what it > needs to do. > > The details are all in the Guide: > > http://perl.apache.org/guide > > and you might also want to have a look at the Eagle Book: > > "Writing Apache Modules with Perl and C", ISBN 1-56592-567-X > > and/or the Cookbook > > http://www.modperlcookbook.org > > if you haven't already. > > 73, > Ged. > > (PS: GY: OK?) > >
