I got stuck by the a fork()

[Cadwalader]

Hello,

New trouble...at least for me. I got in a freindly little "packet fight" with a friend. I was winning--mind you was winning. To make a long stroty short, he tells me, after I thougt I won, to look at my server. Guess what it said?

Not enough memory to continue
Not enough memory to continue
Not enough memory to continue
Not enough memory to continue
Not enough memory to continue
Not enough memory to continue
Not enough memory to continue
Not enough memory to continue
Not enough memory to continue
Not enough memory to continue
Not enough memory to continue
Not enough memory to continue
Not enough memory to continue
(or something like that, I was too busy soiling my drawers--so to speak--to remember exactly what it said)

He accomplished this with a "fork" script. I didn't dig too far into how it works, or how someone could pull this off. Once I found out that it's done an Apache 1.3.x port 80, I figured it's time to upgrade to 2.0. I think I can pull it off, either with the binary, or the rpm. But the trouble I can already foresee, is that I have to have php and perl support, and it would be nice to have all the other support that I have now for all the bells and whistles.

So the question is, what do I need to do to make sure that I have php/perl/bells_and_whistles support that I have now?

My box is RedHat 7.3/Apache 1.3.26

Pardon me for posting sort of a "blanket" question, but I am kinda new to Linux. I have also read about limiting proc usage and the # of processes that can run at one time. Any suggestions on that?

thanks for being patient with a lamer...;-) Hope I was of some help...
--OR--
Thanks for the help...
--Rich

 

[fluid11]

How is Apache installed on your system? RPM package or from source?


ChrisP

 

[Cadwalader]

Well,

I upgraded it once. That was an RPM. I don't know what came off the disks during the install... Hope I was of some help...
--OR--
Thanks for the help...
--Rich

 

[fluid11]

Backup your configuration (any config files and your website(s)) and upgrade from a new RPM pacakge...

rpm -Uvh apache-x.x.x.rpm


If it goes south, or doesn't include the modules you want, then you can easily either start from scratch by compiling from source or installing an older RPM if you backed everything up. If you installed Apache using an RPM from Red Hat, a newer version from Red Hat will most likely include the same modules.


ChrisP