Re: red hat mod_perl build problem

[prev] [thread] [next] [Date index for 2005/04/05]

Thanks, Tom, for the worldly advice.

But, here is my situation.

I am a single individual supporting 8+ Oracle research databases at 
Vanderbilt University Medical center using a modperl authorization 
system that I developed under modperl 1 and other perl scripts that 
run under the Registry module which I have been waiting to upgrade 
to version 2 for 2 years. I am supporting Apache in this 
configuration on Windows 2000 and XP and Red Hat Linux. I am also 
the the DBA for our 2 Oracle 9.2 database systems that run on 
matching Sun 450's. And did I mention that I am also the system 
manager for all of the systems that I have just mentioned as well? 
The perl/modperl code that I developed for rapidly developing 
web-based research databases (using metadata) is also in use at the 
Universities of North Carolina and Pennsylvania.

When I put out the message about not being able to build on the 
linux box, I didn't get any response for a couple of days, so I 
figured I was on my own; so I back peddled to the most obvious, 
workable solution.

This is by no means a jab at the modperl support team. They do a 
great job considering the breadth of system types that modperl has 
been ported to. It's just that I did not have the luxury of waiting 
for support that might never have come. I realize that the support 
people are perhaps even busier than I am!

Now that I have an idea of how to proceed, i.e. remove the old 
version of perl from my brand new linux box - completely - and 
install perl 5.8.6 then build apache 2 and modperl 2, maybe I will 
do it. But more likely I have lost my 'window of opportunity' 
because of the backlog of database change requests and new features 
that my clients are screaming for.

Again, I am not criticizing anyone here. It was my decision to go 
with modperl in a production environment and I am prepared to live 
with the consequences.

I sincerely appreciate your advice and counsel.

Thanks,

Tom Caldwell

--On Tuesday, April 05, 2005 8:52 AM +0200 Tom Schindl 
<tomAtLinux@xxx.xx> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi,
>
> I won't do that because when develping code on such an old code
> base
> like 1.99.09 many things have been corrected/changed beside
> security
> holes closed in apache 2, ... . And mod_perl is changing the next
> release will probably shift everything from Apache into the
> Apache2-Namespace, so don't be suprised when working on not yet
> released
> code (and there has never been a final release of mp2) it won't
> work in
> later releases. You should at least work on the latest available
> codebase or even better the svn/cvs-trunk of it. Things have been
> fixed,
> the docs match the real code you use, ... .
>
> Tom
>
> Tom Caldwell schrieb:
>| Thanks for the reply, but I did some more digging and decided
>| that having 2 versions of perl installed (improperly) on my
>| system was probably the culprit. And since red hat provides a
>| version of apache2 and modperl 2 with perl 5.8.0, I decided to
>| just go with that, even though it is 1.5 years old (1.99.09)!
>|
>| Now if I could only get the Oracle client to install I will be
>| back to developing more code!
>|
>| Thanks,
>|
>| Tom
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.0 (GNU/Linux)
> Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
>
> iD8DBQFCUjXEkVPeOFLgZFIRAk4MAKC6JJGTL7n7C6ls++xuUBJ7fDNIngCgjrza
> OrdgzBPm3oI8dzv/gOW9sEI=
> =nItK
> -----END PGP SIGNATURE-----




Tom Caldwell
Vanderbilt University Medical Center